SET ASSOCIATION USERCORRDATA
Overwrite the user correlator data of the originating task.
Syntax
Activate security checks on commands by specifying the XCMD system initialization parameter and by ensuring that command security checking is active for the transaction (either by specifying CMDSEC(YES) on the TRANSACTION resource definition or by specifying ALWAYS on the CMDSEC system initialization parameter).
Conditions: INVREQ, NOTAUTH
NOHANDLE, RESP, and
RESP2 are common options that can be added to all EXEC CICS
commands to process error conditions. They are not explicitly included in the command syntax diagram
and option descriptions. For information about these common options and EXEC CICS
command syntax, see EXEC CICS command format and programming considerations.
This command is threadsafe.
Description
The originating task can invoke a global user exit program that obtains user correlator data (for example, from HTTP headers or MQ messages) and then issues SET ASSOCIATION USERCORRDATA to overwrite the USERCORRDATA field of the originating task.
The task issuing SET ASSOCIATION USERCORRDATA must have the same task number as that of the originating task; otherwise, an INVREQ response with a RESP2 value of 1 is issued.
The SET ASSOCIATION USERCORRDATA command is not audited.
Options
- USERCORRDATA(data-value)
- Specifies the user correlator data to overwrite the USERCORRDATA field of the originating
task.CAUTION:The USERCORRDATA field is limited to 64 bytes. If the specified data value exceeds the limit, it is truncated to 64 bytes when copied to the USERCORRDATA field, but no messages are issued to indicate that truncation has occurred. Therefore, it's the user's responsibility to ensure the integrity of the user correlator data.
Conditions
- INVREQ
- RESP2 values:
- 1
- The issuing task is not the originating task. Only the originating task is allowed to issue SET ASSOCIATION USERCORRDATA.
- NOTAUTH
- RESP2 values:
- 100
- The user associated with the issuing task is not authorized to use this command.
