Register

The Register_Test service requests that a TP be initiated for testing purposes in the caller's address space instead of in an APPC initiator. The service directs APPC/MVS to initiate the TP in the caller's address space when the next inbound allocate request for that TP, on behalf of that caller, arrives. The caller must set the appropriate environment for the TP, and must call the Accept_Test service when it is ready to receive and run the TP. The caller can include its own interactive debugging facilities to help test and diagnose the TP.

This service does not support multi-trans TPs.

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

Figure 1. Invocation of the Register_Test Callable Service

CALL ATBTER1  ( TP_Name_Length,
                TP_Name,
                LU_Name_Length,
                LU_Name,
                Return_Code
              );

Parameters

TP_Name_Length

Supplied parameter

Type: Integer
Char Set: N/A
Length: 4 bytes

Specifies the length of the data contained in the TP_Name parameter.

TP_Name

Supplied parameter

Type: Character
Char Set: 00640
Length: 1-64 bytes

The name of the TP to be tested.

LU_Name_Length

Supplied parameter

Type: Integer
Char Set: N/A
Length: 4 bytes

Specifies the length of the data contained in the LU_Name parameter.

LU_Name

Supplied parameter

Type: Character string
Char Set: Type A
Length: 8 bytes

Specifies the LU where the TP to be registered resides. To specify the base LU for the transaction scheduler associated with the caller, supply all blanks. The LU must be associated with a transaction scheduler (that is, you cannot specify a NOSCHED LU).

Return_code

Returned parameter

Type: Integer
Char Set: N/A
Length: 4 bytes

Decimal Value: Description
0: Register_Test completed successfully.
4: The request was rejected because a previous test request is active for the caller's address space. Only one test request is permitted per address space at any given time.
8: APPC/MVS is not available.
12: The TP name was either not specified or was invalid.
16: APPC/MVS service failure.
20: The user was not authorized to modify or create a user-level TP profile.
24: The LU name was not valid.
28: There is an existing APPC conversation in the address space or conversation resources were not all cleaned up by previous conversations.
32: There was an error in creating a user level TP profile.
36: APPC test enablement services are unavailable.
40: The LU specified was undefined or was not associated with the scheduler of this address space, or the specified LU name contains characters that are not defined to APPC/MVS.
44: LU_name was blank to request the base LU, but no base LU is defined.
48: An error occurred while Register_Test was trying to add or modify a TP profile for testing purposes.
50: The specified LU (or the default base LU, if no LU name was specified) was not associated with any scheduler.

Restrictions

Transaction programs that call the Register_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.