Use the IEAINTKN macro to build an incident token. You can pass the token to other routines to identify related pieces of problem data.
Normally you will not need to use an IEAINTKN macro because the system generates an incident token when an SVC dump is requested and an incident token is not provided. For example, the system provides an incident token when it processes an SDUMPX macro without an INTOKEN parameter.
The requirements for the caller are:
Environmental factor | Requirement |
---|---|
Minimum authorization: | Problem state with PSW key 8-15 |
Dispatchable unit mode: | Task or SRB |
Cross memory mode: | Any PASN, any HASN, any SASN |
AMODE: | 24- or 31- bit |
ASC mode: | Primary or access register (AR) |
Interrupt Status: | Enabled or disabled for I/O and external interrupts |
Locks: | The caller may hold locks, but is not required to hold any. |
None.
Before issuing the IEAINTKN macro, 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.
The standard form of the IEAINTKN macro is written as follows:
Syntax | Description |
---|---|
name | name: Symbol. Begin name in column 1. |
␢ | One or more blanks must precede IEAINTKN. |
IEAINTKN | |
␢ | One or more blanks must follow IEAINTKN. |
,TOKEN=inctoken addr | inctoken addr: RX-type address or register (2) - (12). |
The parameters are explained as follows:
None.
None.
IEAINTKN TOKEN=MYTOKEN
.
.
.
DS 0D Align parameter on double word boundary
MYTOKEN DS CL32 Incident token
CVT , CVT mapping