Reason:
FSS interface received a non-zero return code from an FSIREQ order. Documented in the PSF - Diagnosis Guide and Reference for MVS manual. Processing continues.
Action:
None.
Reason:
FSS interface has received a non-zero return code from an FSIREQ order. Documented in the PSF - Diagnosis Guide and Reference for MVS manual. Processing continues.
Action:
None.
Reason:
A call to one of the CA Spool interface routines ESFOPEN, ESFWRIT, ESFCLOS, ESFNETC received a non-blank status code. Processing continues.
Action:
Contact your systems programmer.
Reason:
An FSIREQ GETREC request with a DSID that does not match the current open CA Spool file was received. The call is rejected with an indication of a logical error.
Action:
Contact your systems programmer.
Reason:
A FSIREQ GETREC request was received before any GETDS was received. The call is rejected.
Action:
Contact your systems programmer.
Reason:
A FSIREQ SEND request with a non-zero response code was received. Processing continues.
Action:
Contact your systems programmer.
Reason:
ESFORDER subtask received a non-zero return code from ESTAE. Processing continues without an error-recovery environment.
Action:
Contact your systems programmer.
Reason:
An unsupported FSIREQ was invoked. Processing continues.
Action:
Contact your systems programmer.
Reason:
A call to one of the CA Spool FSS interfaces was issued in an address space that did not match the current address space. This is probably due to an abnormal termination of the CA Spool address space. An S0C1 abend is provoked.
Action:
Contact your systems programmer.
Reason:
The ESFORDER subtask abended. Processing continues, but it is no longer possible to issue orders to the FSS.
Action:
Contact your systems programmer.
|
Copyright © 2011 CA.
All rights reserved.
|
|