Accept_Test
The Accept_Test service specifies that the caller is ready to test the TP registered by a previous call to Register_Test. The Accept_Test service causes the caller to wait for the next inbound allocate request to arrive for that TP on behalf of that caller, and for the APPC test environment to be set up in the caller's address space.
Requirements
| Authorization: | Supervisor state or problem state, any PSW key |
| Dispatchable unit mode: | Task mode |
| Cross memory mode: | Any PASN, any HASN, any SASN |
| AMODE: | 31-bit |
| ASC mode: | Primary or access register (AR) |
| Interrupt status: | Enabled for I/O and external interrupts |
| Locks: | Unlocked |
| Control parameters: | All parameters must be addressable by the caller and in the primary address space. |
Format
CALL ATBTEA1 ( TP_ID,
Return_Code
);Parameters
- TP_ID
- Returned parameter
- Type: Character string
- Char Set: N/A
- Length: 8 bytes
The TP_ID is a token that represents the instance of the transaction program that was initiated for testing. To deallocate and clean up the conversation after the test is finished, supply this TP_ID on a call to the Cleanup_TP service.
- Return_code
- Returned parameter
- Type: Integer
- Char Set: N/A
- Length: 4 bytes
- Decimal Value
- Description
- 0
- Accept_Test completed successfully.
- 4
- The request was rejected because there was no Register_Test request active for the caller's address space.
- 8
- APPC/MVS is not available.
- 12
- The test request failed a RACF SECLABEL check.
- 16
- APPC/MVS service failure.
- 20
- The user was not authorized to execute the requested TP.
- 24
- The test request was canceled by the Unregister_Test service.
- 28
- There is an existing APPC conversation in the address space or conversation resources were not all cleaned up by previous conversations.
Restrictions
Transaction programs that call the Accept_Test 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.