When the IXLFCOMP macro returns control to your program:
- GPR 15 (and retcode if you coded RETCODE) contains a return
code.
- If the return code is not zero, GPR 0 (and rsncode if you
coded RSNCODE) contains a reason code, if applicable.
You could receive any of the return codes and reason codes issued
by IXLFCOMP, in addition to those described for IXLLIST and IXLCACHE.
The return and reason codes that pertain to the IXLFCOMP request
are listed in Table 1. Otherwise,
the return and reason codes pertain to the prior IXLLIST and IXLCACHE
request that has completed. Refer to those services for the return
and reason code information.
The answer area is not valid if you issue an IXLFCOMP OPTYPE=COMPLETE
request and get back RC=IXLRETCODEPARMERROR with RSN=IXLRSNCODENOSUSPENDISABLE.
The equate symbols associated with each IXLFCOMP return code are
as follows:
- 4
- IXLRETCODEWARNING
- 8
- IXLRETCODEPARMERROR
For the reason codes shown below, xxxx denotes
information that is not part of the reason code.
Table 1. Return and Reason
Codes for the IXLFCOMP MacroHexadecimal Return Code |
Hexadecimal Reason Code |
Equate Symbol
Meaning and Action
|
---|
4 |
xxxx0413 |
Equate symbol: IXLRSNCODEREQNOTCOMP Meaning: The
request identified by REQTOKEN has not completed. The IXLLIST or IXLCACHE
answer area is not valid.
Action: Issue the IXLFCOMP
macro again, with OPTYPE=TEST to determine when the list or cache
request will complete (with the answer area filled in) or with OPTYPE=COMPLETE
to wait for the list or cache request to complete.
|
8 |
xxxx0801 |
Equate Symbol: IXLRSNCODEBADPARMLIST Meaning: Program
error. The parameter list for this request is not addressable. The
answer area (ANSAREA) fields are not valid.
Action: Verify
that: - The parameter list address is uncorrupted.
- The parameter list is addressable in the caller's primary address
space.
- If you are issuing this macro while disabled, the parameter list
resides in either page-fixed or DREF storage.
- If you are issuing this macro in AR-mode and you specified the
parameter list address using explicit register notation, the corresponding
access register was updated appropriately.
- If you are issuing this macro in AR-mode, SYSSTATE ASCENV=AR must
be issued before issuing this macro.
|
8 |
xxxx0804 |
Equate Symbol: IXLRSNCODEBADVERSIONNUM (or IXLRSNCODEBADVERSION#)
Meaning: The version number in the macro parameter list
is not compatible with the level of XES currently being used. The
answer area (ANSAREA) fields are not valid.
Action: - Verify that your program did not overlay the parameter list storage.
- Verify that your program was assembled with the correct macro
library for the release of MVS™ on
which your program is running.
|
8 |
xxxx0831 |
Equate symbol: IXLRSNCODEBADREQTOKEN Meaning: Program
error. You specified an asynchronous request token that was not valid.
Your IXLFCOMP request failed. The IXLLIST or IXLCACHE answer area
is not valid.
Action: Ensure that the request token
passed on the IXLFCOMP request is the same one that you got back from
IXLLIST or IXLCACHE on a SYNCTOKEN or ASYNCTOKEN request. Verify that
if the IXLLIST or IXLCACHE request was a SYNCTOKEN request, that it
was in fact processed asynchronously. If the request was processed
synchronously, the request token is not meaningful and there is no
reason to use the IXLFCOMP macro. Verify that you are not re-issuing
the IXLFCOMP macro using the same request token after observing the
completion of the request. Once you observe completion of a request,
the request token is no longer valid, and any subsequent IXLFCOMP
requests will complete with this reason code.
|
8 |
xxxx0851 |
Equate symbol: IXLRSNCODENOSUSPENDISABLE Meaning: Program
error. A request specifying OPTYPE=COMPLETE failed because the prior
IXLLIST or IXLCACHE request has not completed, and the caller is disabled
and cannot be suspended.
Action: Release the CPU lock
to become enabled and reissue the request.
|
10 |
xxxx10xx |
Equate symbol: IXLRETCODECOMPERROR Meaning: XES
processing failure. The state of the involved structure and the disposition
of the request are unpredictable.
Action: Contact the IBM® Support Center.
|