IEAN4RT — Retrieve the token from a name/token pair

The requirements for the caller are:

* Name/Token Level Constants
*
IEANT_TASK_LEVEL             EQU     1
IEANT_HOME_LEVEL             EQU     2
IEANT_PRIMARY_LEVEL          EQU     3
IEANT_SYSTEM_LEVEL           EQU     4
IEANT_TASKAUTH_LEVEL         EQU     11
IEANT_HOMEAUTH_LEVEL         EQU     12
IEANT_PRIMARYAUTH_LEVEL      EQU     13
*
* Name/Token Persistence Constants
*
IEANT_NOPERSIST              EQU     0
IEANT_PERSIST                EQU     1
*
* Name/Token Return Code Constants
*
IEANT_OK                     EQU     0
IEANT_DUP_NAME               EQU     4
IEANT_NOT_FOUND              EQU     4
IEANT_24BITMODE              EQU     8
IEANT_NOT_AUTH               EQU     16
IEANT_SRB_MODE               EQU     20
IEANT_LOCK_HELD              EQU     24
IEANT_LEVEL_INVALID          EQU     28
IEANT_NAME_INVALID           EQU     32
IEANT_PERSIST_INVALID        EQU     36
IEANT_AR_INVALID             EQU     40
IEANT_UNEXPECTED_ERR         EQU     64

To obtain the name of the logrec data set or the name of the logrec log stream, you can include the IFBNTASM macro, as well as the IEANTASM macro, in your program. See Example 2 for the list of definitions IFBNTASM provides.

• Do not use the IEAN4RT callable service in a RESMGR resource manager routine unless one of the following is true:
  • The name/token pair is a system-level persistent name/token pair.
  • The resource manager is running for a daughter task of the task that owns the name/token pair.
  • The resource manager is running for the task that owns the name/token pair and that resource manager was established for a specific address space and a specific task.
• Do not call the IEAN4RT callable service with user_name and user_token parameters being the same storage locations.

Before issuing the IEAN4RT callable service, the caller does not have to place any information into any register unless using it in register notation for a particular parameter, or using it as a base register.

Some callers depend on register contents remaining the same before and after issuing a service. If the system changes the contents of registers on which the caller depends, the caller must save them before issuing the service, and restore them after the system returns control.

None.

Write the call as shown on the syntax diagram. You must code all parameters on the CALL statement in the order shown.

1.   LOAD EP=IEAN4RT
     Save the 8-byte entry point address with bit 63 changed to 0
     (...)
     Put the saved entry point address with bit 63 changed to 0 into 64-bit R15
     CALL (15),(...)

2.   LLGT  15,X'10'
     L     15,X'220'(15,0)
     L     15,X'14'(15,0)
     L     15,X'80'(15,0)
     CALL  (15),(...)

Both of these alternate techniques require verification that the IEAN4RT service is available (in the CVT, bit CVTZOS_V1R11 is on indicating that the program is running on z/OS V1R11 or a later release).

The parameters are explained as follows:

level

Specifies a fullword that contains an integer indicating the level of the name/token pair from which you want to retrieve the token:

1

Task

2

Home address space

3

Primary address space

4

System

11

Task with authorization check

12

Home address space with authorization check

13

Primary address space with authorization check.

Note: Levels 11, 12, and 13 indicate that the IEAN4RT callable service should determine if the name/token pair being retrieved was created by an authorized program.

,user_name

Specifies the 16-byte area containing the name of the requested name/token pair.

,user_token

Specifies the 16-byte area to contain the token of the requested name/token pair.

,return_code

Specifies a fullword to contain the return code from the IEAN4RT service.

None.

When IEAN4RT returns control to your program, GPR 15 and return_code contain a return code. The following table identifies return codes in hexadecimal, tells what each means, and recommends as action that you need to take.