• Associated with a DU native context associated with a task in the current home address space, or
• A private context owned by a PKM 8–15 problem state resource manager registered in the home address space.

Register

Contents

0-1

Used as work registers by the system

2-13

Unchanged

14

Used as a work register by the system

15

Return code

Register

Contents

0-1

Used as work registers by the system

2-13

Unchanged

14-15

Used as work registers by the system

return_code

Returned parameter

• Character Set: N/A
• Length: 4 bytes

Contains the return code from the Set_Side_Information service.

,ur_interest_token

Supplied parameter

• Type: Character string
• Character Set: No restriction
• Length: 16 bytes

For ATRSUSI callers, specifies a token that uniquely identifies your resource manager's interest in the UR whose side information you want to set. Your resource manager received the token from one of the following services: Express_UR_Interest, Retain_Interest.

,ur_or_uri_token

Supplied parameter

• Type: Character string
• Character Set: No restriction
• Length: 16 bytes

For ATRSUSI2 callers, specifies a token that uniquely identifies either the UR, or your resource manager's interest in the UR, whose side information you want to set:

• UR token: The token for the UR.
• UR interest token: The UR interest token that identifies your resource manager's interest in the UR.

Your resource manager received the token from one of the following services: Express_UR_Interest, Retrieve_Interest_Data, Retain_Interest, Create_Cascaded_UR, or Retrieve_UR_Data.

Because you may pass two different types of tokens through this parameter, passing an invalid token can generate either a ATR_URI_TOKEN_INV or a ATR_UR_TOKEN_INV return code. For example, passing an invalid UR token might result in an ATR_URI_TOKEN_INV return code. Even though a UR token was passed, if it is invalid, then RRS may not understand what sort of token it was supposed to be. For this reason, IBM® recommends callers check both return codes, even when they know what type of token they intend to pass.

,element_count

Supplied parameter

• Type: Integer
• Length: 4 bytes

Specifies the number of elements in the array for the side_info_id parameter. Specify a hexadecimal value from X'1' to X'8'

,side_info_id

Supplied parameter

• Type: Integer
• Length: 4 bytes

Specifies one or more identifiers that set the side information. When you specify two or more identifiers, place the identifiers in an array. For a UR in local transaction mode, the only identifier you can specify is ATR_DRIVE_COMPLETION. The possible identifiers are:

Constant in: Hexadecimal (Decimal) Equate Symbol	Identifier
0 (0) ATR_HEURISTIC_MIX	Heuristic-mixed condition A heuristic commit occurred while the UR state was in_backout, a heuristic reset occurred while the UR state was in_commit, or a resource manager of distributed resources informed RRS of a heuristic-mixed condition. When this information is initially set through a call to Set_Side_Information, RRS will harden (or reharden) the UR state immediately (before control returns to the caller), which will make the information available on restart.
1 (1) ATR_BACKOUT_REQUIRED	Backout required When this identifier is initially set, RRS will force the current UR to back out when a syncpoint occurs. If a UR state has passed beyond in_prepare, RRS ignores this identifier.
10 (16) ATR_BREAK_TREE	Break tree When this identifier is initially set, RRS will reset the logical unit of work identifier (LUWID) for the next UR.
11 (17) ATR_DRIVE_BACKOUT	Backout of next UR When this identifier is initially set, RRS will, if any resource manger has called Retain_Interest for the next UR, complete backout for the next UR before returning control to the application program. This processing ensures that the next UR will be backed out.
12 (18) ATR_RESYNC_IN_PROGRESS	Resync in progress A resync in progress condition has occurred. If the UR state is before in_end when this identifier is initially set, RRS will harden (or reharden) the UR state at the next state change, which will make the information available on restart.
13 (19) ATR_NEW_LUWID_PSH_UNACCEPTABLE	New LUWID PSH unacceptable A communication resource manager cannot accept a new LUWID presentation header (PSH). RRS takes no action when this identifier is set.
14 (20) ATR_DRIVE_COMPLETION	Invoke completion exit(s) When this identifier is set, RRS will invoke any defined COMPLETION exit routines when the UR is complete. If the UR state is before in_end when this identifier is initially set, RRS will harden (or reharden) the UR state, including this identifier, at the next logging point.
21 (33) ATR_APPL_COMPLETE	This identifier indicates completion of an individual UR in a cascaded UR family. Setting this identifier informs RRS that the application executing for this UR is complete. RRS will not commit a cascaded UR family until RRS is informed that all of the individual cascaded URs in the family are complete. Note: You cannot specify ATR_APPL_COMPLETE and ATR_RESET_APPL_COMPLETE on the same call to Set_Side_Information.
22 (34) ATR_RESET_APPL_COMPLETE	Application processing is not complete When this identifier is used, RRS resets the ATR_APPL_COMPLETE identifier. RRS will not commit a cascaded UR family until RRS is informed that all of the individual cascaded URs in the family are complete. Note: You cannot specify ATR_APPL_COMPLETE and ATR_RESET_APPL_COMPLETE on the same call to Set_Side_Information.

⋮
URI_TOKEN = UR_INTEREST_TOKEN
COUNT = 1
ID = ATR_BACKOUT_REQUIRED
CALL ATRSUSI(RC,URI_TOKEN,COUNT,ID)
IF RC = ATR_OK THEN
⋮