Use the IKJEFFDF macro to map the parameter list for IKJEFF18.
This mapping macro, which is provided in SYS1.MACLIB, has the following
syntax:
IKJEFFDF [DFDSECT={YES} ]
[ {NO } ]
[,DFDSEC2={YES} ]
[ {NO } ]
- DFDSECT=YES | NO
- Use the DFDSECT=YES option to map the DFDSECTD DSECT, instead
of obtaining storage. DFDSECT=NO is the default.
- DFDSEC2=YES | NO
- Use the DFDSEC2=YES option to map the DFDSECT2 DSECT, instead
of obtaining storage. DFDSEC2=NO is the default.
The IKJEFFDF macro generates the following six-word parameter list:
Table 1. The parameter list
(DFDSECTD DSECT)Offset dec(Hex) |
Field name |
Contents or meaning |
---|
0(0) |
DFS99RBP or DFDAPLP |
Address of the failing SVC 99 request block or
address of the failing DAIR parameter list. |
4(4) |
DFRCP |
Address of a fullword containing either the SVC
99 or DAIR return code. |
8(8) |
DFJEFF02 |
Address of a fullword. The fullword contains
the entry point address of IKJEFF02 (message issuer routine). If
the entry point address of IKJEFF02 is unknown, the fullword must
contain zeros. |
12(C) |
DFIDP |
Address of a two-byte area containing: - Byte 1
- Switches
- Bit 0:
- 0 - PUTLINE issued
- Bit 0:
- 1 - WTP issued
- Bit 1:
- 1 - Caller wants message extracted only.
- Bit 2:
- 1 - Caller wants message extracted as well as issued using PUTLINE
or write-to-programmer (WTP).
- Byte 2
- Caller identification number
X'01' - DAIR X'32' - SVC 99 X'33' - SVC 99 invoked by the FREE command
|
16(10) |
DFCPPLP |
Address of the CPPL. This is needed only when
IKJEFF18 is called with an SVC 99 error and the user is not requesting
a write-to-programmer message. |
20(14) |
DFBUFP |
Address of DFBUFS buffer if bit 2 (DFBUFSW) or
bit 3 (DFBUFS2) of DFIDP is on. This is required when the message
is to be extracted and returned to the caller. If the DFBUFSW is
on, the message(s) will only be extracted. If DFBUFS2 is on, the
message(s) will be issued as well as extracted and returned to the
caller. It will be possible to extract the first-level and one second-level
message. |
DFDSECT2, which is described in Table 2,
defines a storage area supplied by the caller. DAIRFAIL will return
the requested informational message(s) in the associated buffers.
It is not necessary to initialize these buffers. On return from
DAIRFAIL, the buffers will contain the extracted message(s).
Table 2. The
parameter list (DFDSECT2 DSECT)Offset dec(Hex) |
Field name |
Contents or meaning |
---|
0(0) |
DFBUFS or DFBUFL1 |
A 2-byte field that will contain the total length
of the first-level message, plus 4 bytes for length and offset fields. |
2(2) |
DFBUF01 |
A 2-byte field containing the offset field. It
will be set to zero when a message is extracted. |
4(4) |
DFBUFT1 |
A 251-byte buffer that will contain the text of
the first-level message extracted. If the message is greater than
251 bytes, the message will be truncated. |
256(100) |
DFBUFL2 |
A 2-byte field containing the total length of
the first second-level message plus four bytes. If there is no second-level
message, this field will contain HEX zeros. |
258(102) |
DFBUF02 |
A 2-byte field containing the offset. It will
be set to zero when a message is extracted. |
260(104) |
DFBUFT2 |
A 251-byte field that will contain the text of
the first second-level message extracted. If the message is greater
than 251 bytes, the message will be truncated. |
If the high-order bit of the caller identification area (pointed
to by DFIDP) is on, a write-to-programmer message will be issued instead
of a PUTLINE. When the write-to-programmer feature is used, the address
of the CPPL (DFCPPLP) need not be specified.