Requirements

Format

CALL ATBSCA2(
        Notify_type,
        Conversation_id,
        User_accounting_data_length,
        User_accounting_data,
        Reason_code,
        Return_code
       );

Parameters

Notify_type

Supplied parameter

• Type: Structure
• Char Set: N/A
• Length: 4-8 bytes

Specifies the type of processing and notification (synchronous or asynchronous) requested for this service. The possible types are:

• None

  No notification is requested. The service is performed synchronously, and control is returned to the caller when processing is complete. All returned parameters are set on return to the caller. To specify no notification, set the parameter value to a four-byte structure containing binary zeros.

• ECB

  Programs can request asynchronous processing by specifying an ECB to be posted when processing completes. To specify an ECB, set the parameter to an eight-byte structure containing a fullword binary one (X'00000001') followed by the address of a fullword area to be used as the ECB. The ECB must reside in the home address space.

  When you specify an ECB, control is returned before processing is complete, with only the return code set. If the asynchronous request was accepted, the return code is set to 0 to indicate that the service is being processed asynchronously. Other returned parameters are filled in during asynchronous processing, and the specified ECB is posted when all returned parameters are set. The completion code field in the ECB contains the return code for the service. The reason code, if any, is set in the caller's Reason_code parameter.

Conversation_id

Supplied parameter

• Type: Character string
• Char Set: No restriction
• Length: 8 bytes

Conversation_id, sometimes called the resource identifier, identifies a conversation to the system.

User_accounting_data_length

Supplied parameter

• Type: Integer
• Char Set: N/A
• Length: 32 bits
• Range: 0-255

User_accounting_data_length specifies the length of data contained in the User_accounting_data parameter.

If zero is specified for this parameter, any previously written user accounting data is removed from this conversation's accounting record.

User_accounting_data

Supplied parameter

• Type: Character string
• Char Set: No restriction
• Length: 0-255 bytes

User_accounting_data specifies user-defined data to be placed in the SMF accounting record for this conversation.

Reason_code

Returned parameter

• Type: Integer
• Length: 32 bits

Reason_code contains additional information about the result of the call when the return_code parameter contains a nonzero value other than atbcts_appc_not_available.

Table 1 lists the valid reason codes.

Return_code

Returned parameter

• Type: Integer
• Length: 32 bits

Return_code specifies the result of the call. If the return_code parameter contains zero or 64 (decimal), there is no reason code. For other return codes, check the reason_code parameter for additional information about the result of the call.

The following table lists the possible return and reason codes, their symbolic equates, and their meanings, for the Set_Conversation_Accounting_Information service.

Table 1. Return and Reason Codes for Set_Conversation_Accounting_Information

Return Code (Decimal)	Reason Code (Decimal)	Symbolic and Meaning
0	—	atbcts_ok The service completed as requested.
8	All	atbcts_parameter_error A user-supplied parameter was found to be in error. For example, a parameter contains characters not in the required character set. See the reason_code parameter to determine which parameter is in error.
8	18	atbcts_inval_notify_type The specified notify type is not valid.
8	22	atbcts_inval_conversation_id The specified conversation identifier does not represent an active conversation for this address space.
8	35	atbcts_inval_acct_data_length The specified accounting data field length is outside the allowable range.
16	All	atbcts_request_unsuccessful The service was unsuccessful. The cause is most likely a parameter error other than a syntax error, or an environmental error. For example, a syntactically valid LU name was specified, but the LU is not defined to APPC/MVS. An example of an environmental error is that the caller called the service while holding locks. See the Reason_code parameter for the specific cause of the error, and to determine whether the error can be corrected and the service reissued.
16	8	atbcts_cannot_hold_locks The caller held one or more locks when calling the service.
16	40	atbcts_conv_inaccessible The specified conversation is currently in use by another process.
32	All	atbcts_service_failure APPC/MVS service failure. Record the return and reason code, and give them to your systems programmer, who should contact the appropriate IBM support personnel.
32	16	atbcts_appc_service_failure The service failed because of an APPC failure. APPC provides symptom records for this type of error. For more information, see the appendix that explains return and reason codes in z/OS MVS Programming: Writing Servers for APPC/MVS.
64	—	atbcts_appc_not_available APPC/MVS is not currently active. Call the service again after APPC is available.

Restrictions

Transaction programs that call the Set_Conversation_Accounting_Information service while in task mode should not have any enabled unlocked task (EUT) functional recovery routines (FRRs) established. For more information about EUT FRRs, see the section on providing recovery in z/OS MVS Programming: Authorized Assembler Services Guide.