Filter
Top Products
RESPONSE and REASON values for ACQUIRE_PROGRAM:
RESPONSE REASON
OK None
EXCEPTION NO_STORAGE
PROGRAM_NOT_DEFINED
PROGRAM_NOT_FOUND
DISASTER None
INVALID None
KERNERROR None
PURGED None
Note:
1. For more detail, refer to the explanation of RESPONSE and REASON in
“Making an XPI call” on page 308.
2. A REASON of ‘NO_STORAGE’ with a RESPONSE of ‘EXCEPTION’
means that there was insufficient storage to satisfy this request, and
SUSPEND(NO) was specified.
3. A REASON of ‘PROGRAM_NOT_FOUND’ is returned if the program has
not been included in the library concatenation, or if the link-edit failed. In
such a case, the program is marked as “not executable”; it must be
re-linked before it can be successfully acquired.
The RELEASE_PROGRAM call
RELEASE_PROGRAM decrements the use count of a currently loaded program by
one.
If the program has been defined with the RELOAD attribute, the storage occupied
by this copy of the program is released.
You should issue the ACQUIRE_PROGRAM and RELEASE_PROGRAM requests
for a single program during the same execution of the exit program. If you do not
want to do this, you should acquire the program once during CICS initialization, and
leave it resident until CICS termination.
RELEASE_PROGRAM
DFHLDLDX [CALL,]
[CLEAR,]
[IN,
FUNCTION(RELEASE_PROGRAM),
ENTRY_POINT(pointer),
{PROGRAM_NAME(name8 | string | ’string’)|
PROGRAM_TOKEN(name4)},]
[OUT,
RESPONSE(name1 | *),
REASON(name1 | *)]
This command is threadsafe.
ENTRY_POINT(pointer)
specifies the address of the entry point of this copy of the named program.
PROGRAM_NAME(name8 | string | "string")
specifies the name of the program to be released.
358 Customization Guide