IEANTDL — Delete a name/token pair

Environment

The requirements for the caller are:

Environmental factor	Requirement
Minimum authorization:	Problem state with any PSW key Note: Problem-state programs with PSW key 8 - 15 cannot delete: System-level pairs Name/token pairs created by supervisor-state or PSW key 0-7 programs.
Dispatchable unit mode:	Task or SRB Note: SRB-mode callers cannot delete a task-level pair.
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:	No locks held
Control parameters:	The parameter list and all parameters must reside in the caller's primary address space.

Programming requirements

Before you use name/token services, you can optionally include the IEANTASM macro to invoke name/token services equate (EQU) statements. IEANTASM provides the following constants for use in your program:

* 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

Restrictions

Do not use the IEANTDL 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.

Input register information

Before issuing the IEANTDL 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.

Output register information

When control returns to the caller, the general purpose registers (GPRs) contain:

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

When control returns to the caller, the access registers (ARs) contain:

Register: Contents
0-1: Used as work registers by the system
2-13: Unchanged
14-15: Used as work registers by the system

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.

Performance implications

None.

Syntax

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

Syntax	Description
CALL IEANTDL	,(level ,user_name ,return_code)

Link edit your program with a linkage-assist routine (also called a stub) in SYS1.CSSLIB unless you use one of the following techniques as an alternative to CALL IEANTDL:

1.   LOAD EP=IEANTDL
     Save the entry point address
     (...)
     Put the saved entry point address into R15
     CALL (15),(...)

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

This second technique requires AMODE=31, and, before the CALL is issued, verification that the IEANTDL service is supported by the system (in the CVT, both the CVTOSEXT and the CVTOS390 bits are set on).

Parameters

The parameters are explained as follows:

level

Specifies a fullword that contains an integer indicating the level of the name/token pair you wish to delete:

1: Task
2: Home address space
3: Primary address space
4: System.

,user_name

Specifies the 16-byte area containing the name of the name/token pair to be deleted.

,return_code

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

ABEND codes

The caller might encounter abend X'AC7' with a reason code of either X'00030000' or X'00030001'. See z/OS MVS System Codes for an explanation and responses for these codes.

Return and reason codes

When IEANTDL 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 an action that you need to take.

Table 1. Return Codes for the IEANTDL Macro
Hexadecimal Return Code	Meaning and Action
00	Meaning: The operation was successful. Action: None.
04	Meaning: The request is rejected because the system could not find the requested name/token pair. Action: Check the `user_name` you specified.
08	Meaning: The request is rejected because the caller is in 24-bit addressing mode. Action: Change your program to 31-bit addressing mode.
10	Meaning: An unauthorized caller attempted to delete a system-level pair or a name/token pair that was created by an authorized program. Action: Check which level of name/token pair you are deleting.
14	Meaning: An SRB-mode caller attempted to delete a task-level name/token pair. Action: Change the program to task mode or check the value you set for the level parameter.
18	Meaning: The caller held locks. Action: Release all locks before issuing IEANTDL.
1C	Meaning: The caller specified an incorrect `level`. Action: Respecify the correct `level`. Valid options are 1, 2, 3, or 4.
20	Meaning: The caller specified an incorrect `user_name`. Action: Respecify the correct `user_name`.
28	Meaning: The caller was in AR ASC mode and AR1 was not zero. Action: Change your program to primary mode or set AR1 to zero.
40	Meaning: A system error occurred while handling the request. Action: Retry the request.

Example

For a complete example of creating, retrieving, and deleting a task-level name/token pair, see the IEANTCR callable service.