|
|
|
Common Parameter List (mapped by UXPARM macro in CAI.CBTDMAC)
Contains the parameter list, in the following format:
Contains the address of the parameter list of the GCMDSTXT routine.
Contains the address of the communication word of the GCMDSTXT routine. During its initialization call, the routine sets the contents of the word. The contents are passed unchanged for all subsequent calls to this routine.
Contains the full word of flags used to pass status information to the routine.
Contains the global communication word.
Contains the address of the standard save area.
Contains the return address for CA MIM.
Contains the entry point address for the GCMDSTXT routine. All other registers are undefined.
GCMDSTXT Exit-specific Parameter List (mapped by GCMWTOXP macro in CAI.CBTDMAC)
(Fullword reserved for pre-Version 4.1 and above user exit compatibility)
Fullword containing the address of the message text. Modifiable by the user exit.
One-byte unsigned integer containing the length of the message text. The GCMDSTXT cannot change the length of the message text. If you remove text, then replace it with blanks.
(Seven bytes reserved)
Eight-byte job name or CMS user ID of message issuer.
Twelve-byte message name (that is, IEF233A), left justified, padded on right with blanks.
Two bytes containing the z/OS MCS flags for this message.
Two bytes containing the z/OS descriptor codes for this message.
Sixteen bytes containing the z/OS route codes for this message.
(One byte reserved)
(One byte reserved)
One byte containing the following flag bits:
B'10000000'-WTO imported from a z/OS system
B'01000000'-Message imported from a z/VM system
B'00111111'-(reserved)
(Five bytes reserved)
Four-byte message ID of this message on the originating system. This is provided for message identification and tracking only. Do not issue the DOM SVC in the GCMDSTXT exit, as it causes unpredictable results. The GCMDSTXT can issue a return code to instruct CA MIC to DOM (delete) the message.
Eight-byte system name of the originating system, if available. Otherwise, this field contains X'00's.
Eight-byte sysplex name of which the originating system is a member, if applicable. Otherwise, this field contains X'00's.
One byte containing the following flag bits:
B'10000000'-four-byte console ID present at offset +X'58'
B'01111111'-(reserved)
(3 bytes reserved)
Note: The fields at offsets +X'58' and +X'5C' refer to the destination console, if any, on the system where the message originated; most likely an external system. This may be defined as another console on this system, or it may be undefined. If, however, both this system and the originating system are members of the same sysplex, then these fields refer to the same console on both systems.
Fullword containing the four-byte console ID.
Eight-bytes containing the console name to which this message was destined on the originating system, if message was console directed. Otherwise, this field contains X'00's.
Eight-byte CART. X'00's if unavailable or not specified by the command issuer.
Note: The fields at offsets +X'6C', +X'70', and +X'78' refer to the cross-system command source, if any. These fields are non-zero only if this message is a response to a cross-system command issued from this system.
Fullword containing the four-byte console ID.
Eight-byte command source name. Can be console name, TSO user ID, or INSTREAM depending on command source type.
One-byte unsigned integer containing the command source type defined as:
0 Real MCS console
4 Extended MCS (EMCS) console with migration ID
8 Extended MCS (EMCS) console
12 Subsystem console
16 Product (N/A)
20 TSO user
24 INSTREAM (JCL converter)
28 INTERNAL (no console)
(Seven bytes reserved)
Four bytes containing Extended Request Flags for message (see GCMWTOXP mapping macro).
Four bytes containing the Extended Message Modification Bytes for requesting to change message color, highlighting, and intensity (see GCMWTOXP mapping macro).
(Eight bytes reserved)
Eight-byte eye catcher containing GCMWTOXP.
Eight-byte eye catcher containing GCMDSTXT.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |