As parameters of the SWAREQ macro, you specify the function code and the pointer to the EPAL. The EPAL input data and the EPAL output data for each function code is summarized in the following block:
| SWAREQ Function | EPAL Size | EPAL Input Fields | EPAL Output Fields |
|---|---|---|---|
| Read Locate | 16 and 28 | SVA | Block pointer, block length, block ID |
| Write Locate | 16 | SVA, block pointer, block ID | None |
When you write a program that invokes SWAREQ, you must provide
the field definitions in the EPA. You might also need to provide
the SWA block definitions. When you assemble the program, the following
mapping macros provide the definitions that you need:
- IEFZB505 — EPAL data area
- IEFJESCT — JES control block
- CVT — communications vector table
- IEFQMIDS — SWA block ID definitions
When you specify UNAUTH=YES, you must observe the following rules:
- Your code must be running in 31–bit mode.
- Your function code must specify Read Locate.
- The EPAL that you provide must be an extended EPAL. To provide an extended EPAL, use the LOCEPAX=YES parameter of the IEFZB505 mapping macro. Note that the longer 28 byte EPAL is generated with LOCEPAX=YES.
- If the job for which you are invoking SWAREQ is not the current
job, you must pass the queue manager parameter area (QMPA) address
that is associated with the job you are interested in. In this case,
obtain the QMPA address from the active JSCB of whatever job you are
interested in, and place this address in the EPAL that SWAREQ refers
to by its input parameter.
Data is retrieved from
the current primary address space.