PGLU gate, LINK_URM function
The LINK_URM function of the PGLU gate is used by CICS internal modules to link to a user-replaceable program.
Input Parameters
- PROGRAM_NAME
- is the name of the program resource to be defined.
- SYSTEM_AUTOINSTALL
- defines whether CICS is to autoinstall the program if there is no associated PROGRAM resource definition.
- Values for the parameter are:
- NO
- YES
- CALLER_THREADSAFE
- Optional Parameter
- indicates that the caller of the user-replaceable program is threadsafe, and so execution can continue on any TCB on return from the program: there is no need for PGLU to issue change_mode.
- Values for the parameter are:
- NO
- YES
- COMMAREA
- Optional Parameter
- is the optional communications area to be made available to the linked program.
- LPA_ELIGIBLE
- Optional Parameter
- defines whether or not the program can be loaded into the link pack area (LPA).
- Values for the parameter are:
- NO
- YES
- CHANNEL_TOKEN
- Optional Parameter
- a token representing a channel to be made available to the linked program.
- SYSTEM_EXIT
- Optional Parameter
- indicates that the linked program is to be treated as a system exit.
- Values for the parameter are:
- NO
- YES - the default value is YES.
Output Parameters
- REASON
- The following values are returned when RESPONSE is EXCEPTION:
- AMODE_ERROR
- AUTOINSTALL_FAILED
- AUTOINSTALL_INVALID_DATA
- AUTOINSTALL_MODEL_NOT_DEF
- AUTOINSTALL_URM_FAILED
- AUTOSTART_DISABLED
- DESTRUCTIVE_OVERLAP
- INVALID_COMMAREA_ADDR
- INVALID_COMMAREA_LEN
- JVM_PROFILE_NOT_FOUND
- JVM_PROFILE_NOT_VALID
- JVMPOOL_DISABLED
- PROGRAM_NOT_DEFINED
- PROGRAM_NOT_ENABLED
- PROGRAM_NOT_LOADABLE
- REMOTE_PROGRAM
- SECOND_H8_PROGRAM
- SECOND_JVM_PROGRAM
- SYSTEM_PROPERTIES_NOT_FND
- URM_ABEND
- USER_CLASS_NOT_FOUND
- The following values are returned when RESPONSE is INVALID:
- INVALID_FUNCTION
- ABEND_CODE
- is the four-character abend code to be issued if CICS drives the system default, which is to abend the transaction.
- RESPONSE
- Indicates whether the domain call was successful. For more information, see RESPONSE parameter on domain interfaces.