Filter
Top Products
348 Appendix C
Configuring an Invokable TP Using snaptpinstall
File Format for snaptpinstall
If you use NON-QUEUED, more than one copy of the TP
can be running at a time. If the TP writes to files on the
Windows computer, you need to ensure that different
copies of the TP do not overwrite each other's files. To
do this, use one of the following methods:
• Ensure that the TP appends data to an existing file
instead of creating the file (so that all copies of the
TP append data to the same file)
• Design the TP to generate file names at run-time,
based on the process ID with which the TP is
running (so that each copy of the TP writes to a
different file).
This line is optional. If it is not included, or if an
invalid value is specified, the default is QUEUED.
TIMEOUT
The maximum length of time, in seconds, that a
Receive_Allocate call issued by the TP should block if
there is no incoming Allocate request pending. If no
incoming Allocate is received in this time, the call fails
with a return code indicating “State check - Allocate
not pending.”
A timeout value of 0 indicates that the call always fails
unless an incoming Allocate is already pending when
the call is issued. A timeout value of −1 indicates that
the call waits indefinitely for an incoming Allocate and
does not time out.
This line is optional. If it is not included, or if an
invalid value (a non-numeric value) is specified, the
default is −1 (infinite).
Do not specify this parameter if the TYPE parameter
is set to NON-QUEUED. SNAplus2 uses a timeout value
of 0 for nonqueued TPs, because the TP is always
started in response to an incoming Allocate and so
there is always one pending.
For UNIX USERID
Specify the user ID that SNAplus2 uses to start the TP.
The TP is started in the home directory associated with
this user ID. This home directory is also the default
path for trace files and any other files accessed by the