Reason:
The extended spooling facility has been started and is waiting for the initialization options to be entered by the operator. xxxxxxxx identifies the CA Spool release and level. CA Spool enters and remains in the wait state until the operator enters the options.
Action:
Enter initialization options from the OS reply command.
Reason:
One or more of the options entered were invalid. CA Spool re-issues message ESF000 and waits for new options.
Action:
Respond with valid options to message ESF000.
Reason:
Severe initialization problems occurred which made it impossible to start CA Spool. Determine the cause from previously issued error messages. CA Spool terminates processing.
Action:
Correct any problems, if possible, or contact the systems programmer.
Reason:
A required DD statement with ddname xxxxxxxx was missing in the CA Spool procedure. CA Spool terminates processing.
Action:
Add the required DD statement to the CA Spool procedure and then restart CA Spool.
Reason:
CA Spool was unable to open the file described by the DD statement with DDname xxxxxxxx. CA Spool terminates processing.
Action:
Correct errors in file description, then restart CA Spool.
Reason:
The parameter statement displayed preceding this message is in error.
CA Spool sets an error flag and scans the remaining parameter statements. If the error was found in a NODE definition, processing will continue. Otherwise, processing will be terminated
Action:
Correct the invalid parameter statement, then restart the system.
Reason:
Data set yyyyyy on volume xxxxxx was specified more than once as a spool volume in the initialization parameter data set. CA Spool terminates processing.
Action:
Correct the initialization parameter statements, then restart the system.
Reason:
The volume with volume serial number xxxxxx was requested as a spool volume, but the volume is not mounted. CA Spool terminates processing.
Action:
Mount the volume and correct the initialization parameter statements.
Reason:
The initialization parameters specified a spool or checkpoint data set yyyyyyyy on volume xxxxxx, but the data set was not found on the volume. CA Spool terminates processing.
Action:
Allocate a spool or checkpoint data set on the volume and start CA Spool with the format option, or correct the initialization parameters, then restart CA Spool.
Reason:
CA Spool issued an OBTAIN SVC to get the extended information for the spool data set on volume xxxxxx, but the OBTAIN SVC detected an I/O error in the VTOC. CA Spool terminates processing.
Action:
If this is not a hardware failure, contact the systems programmer.
Reason:
CA Spool issued an OBTAIN SVC which returned an error code of 16. CA Spool terminates processing.
Action:
Contact your systems programmer.
Reason:
The checkpoint data set on volume xxxxxx was allocated without any space definition and is not usable by CA Spool. CA Spool terminates processing.
Action:
Allocate a new checkpoint data set with a valid space definition, and format start CA Spool.
Reason:
Spool data set yyyyyyyy on volume xxxxxx was allocated without any space definition and is thus not usable by CA Spool. CA Spool terminates processing.
Action:
Allocate a new spool data set with a valid space definition, and format start
CA Spool.
This message has two possible returns:
Reason:
CA Spool was not able to dynamically allocate the checkpoint data set on volume xxxxxx. The return code from dynamic allocation was yy. CA Spool terminates processing.
Action:
If the cause of the error is not obvious, then contact the systems programmer.
Reason:
CA Spool was not able to dynamically allocate the spool data set zzzzzzzzzz on volume xxxxxx. The return code from dynamic allocation was yy. CA Spool terminates processing.
Action:
If the cause of the error is not obvious, then contact the systems programmer.
Reason:
CA Spool was unable to open spool data set zzzzzzzzzz on volume xxxxxx with the allocated DDname yyyyyyyy. CA Spool terminates processing.
Action:
Contact your systems programmer.
Reason:
The BUFSIZE parameter was too low for the spool data set yyyyyyyy on volume xxxxxxxx. CA Spool terminates processing.
Action:
Change the BUFSIZE value to allow a maximum of 8 spool records per track, and then format start CA Spool.
Reason:
CA Spool was started with the SCAN initialization option, and after successful validation of all the initialization parameters, it terminates with this message. CA Spool terminates processing.
Action:
None.
Reason:
CA Spool was unable to use the SVC routine specified in SVCCODE-initialization parameter. CA Spool terminates processing.
The return code can have the following values:
Action:
Contact your systems programmer.
Reason:
CA Spool was unable to locate the security-exit corresponding to the specification in the SECUEXT initialization parameter. CA Spool terminates processing.
Action:
Contact your systems programmer.
Reason:
The parameter statement shown in this message file was in error. This message is followed by error message ESF005. CA Spool will set an error flag, scan the remaining parameter statements, and terminate processing.
Action:
Correct the invalid parameter statement and then restart CA Spool.
Reason:
During initialization CA Spool detected an incomplete definition of user ID xxxxxxxx. The parameter-statement validation continues and CA Spool terminates after checking all of the parameters.
Action:
Correct the definition for the user and then restart.
Reason:
CA Spool was unable to allocate the parameter-deck file. Documentation of the return code and the error/info code can be found in either the MVS Job Management manual or the MVS/XA System Macros and Facilities manual. The processing continues.
Action:
Contact your systems programmer.
Reason:
CA Spool was unable to de-allocate the parameter-deck file. Documentation of the return code and the error/info code can be found in either the MVS Job Management guide or the MVS/XA System Macros and Facilities guide. Processing continues.
Action:
Contact your systems programmer.
Reason:
A refresh of ECSA modules ESFSSSM, ESFUSO, and ESFUSS has been performed at CA Spool startup.
Action:
None.
Reason:
CA Spool has successfully completed a warm start using the CHKPTDSx checkpoint data set. Processing continues.
Action:
None.
Reason:
A format start has been requested, or a reinitialization has been performed and one or more spool data sets have been added, and CA Spool is now formatting spool data set yyyyyyyyyy on volume xxxxxx. Processing continues.
Action:
None.
Reason:
A format start has been requested or a re-initialization has been performed, and one or more spool data sets has been added. CA Spool has completed the formatting spool data set yyyyyyyyyy on volume xxxxxx. Processing continues.
Action:
None.
Reason:
An I/O error was detected while CA Spool was formatting spool data set yyyyyyyyyy on volume xxxxxx. CA Spool terminates processing.
Action:
Correct the hardware problem, then restart with the Format option.
Reason:
During initialization CA Spool was neither able to locate the requested module xxxxxxx in the link-pack area nor to load the module in to the common system area. CA Spool terminates processing.
The return code can have the following values:
Action:
Contact your systems programmer.
Reason:
During initialization CA Spool found that its subsystem interface was not in the dormant state. CA Spool terminates processing.
Action:
Another CA Spool task was probably executing. If not, contact your systems programmer, or IPL the entire MVS system.
Reason:
CA Spool was unable to allocate the SSCT subsystem-control block. CA Spool terminates processing.
Action:
Try to start CA Spool again a bit later since the problem might be due to storage contention. If this does not help, then IPL the entire MVS system.
Reason:
CA Spool was unable to allocate the SSVT subsystem-control block. CA Spool terminates processing.
Action:
Same as for message ESF028.
Reason:
CA Spool was unable to allocate the command-message-buffer pool. CA Spool terminates processing.
Action:
Start CA Spool again. If this does not solve the problem, then you may either decrease the NUMCMBS value in the initialization parameters or IPL the entire MVS system.
Reason:
CA Spool was unable to allocate the ESF address-space vector table (ESF-ASVT). CA Spool terminates processing.
Action:
Try to start CA Spool again later, or IPL the entire MVS system.
Reason:
A CA Spool ASVT already existed in storage, but the control block identifier was not valid. CA Spool terminates processing.
Action:
IPL the entire MVS system, or contact your systems programmer.
Reason:
During CA Spool initialization, it was found that file xxxxxx was left open for output processing. The file is permanently closed. Processing continues.
Action:
None.
Reason:
During CA Spool initialization, it was found that file xxxxxx was left open for input processing. The file is permanently closed. Processing continues.
Action:
None.
Reason:
During CA Spool initialization, it was found that file xxxxxx was left in the process of being printed on network node yyyyyyyy.
The file is interrupted, and print processing will continue from the file's last checkpoint. Processing continues.
Action:
None.
Reason:
During initialization CA Spool received a non-zero return code from an IDENTIFY-macro instruction, TASKINIT initialization or CBGET storage allocation, attempting to identify the module xxxxxxx. The OS system returned a completion code of yy. CA Spool terminates processing.
Action:
Restart CA Spool, and contact your systems programmer.
Reason:
During initialization CA Spool received a non-zero return code from an ATTACH-macro instruction attempting to attach the module xxxxxxx. The OS system returned a completion code of yy. CA Spool terminates processing.
Action:
Restart CA Spool, and contact systems programmer.
Reason:
During initialization CA Spool found that file xxxxxx with destination yyyyyyyy was marked as active. The file is re-queued for processing.
Action:
None.
Reason:
During initialization CA Spool detected an unexpected end-of-file condition on the parameter data set. CA Spool is terminated.
Action:
Correct the parameter data set, then restart CA Spool.
Reason:
During initialization CA Spool detected an incomplete definition of network node xxxxxxxx. The parameter-statement validation will continue, and CA Spool will terminate after checking all the parameters.
Action:
Correct the definition for the network node, then restart CA Spool.
Reason:
The internal trace option (specified by the TRACE initialization parameter) has been activated, and xxxxx trace-table entries have been allocated. Processing continues.
Action:
None.
Reason:
During initialization CA Spool was unable to locate the separator exit specified in the SEPAEXIT sub-parameter of a NODE definition. CA Spool is terminated.
Action:
Correct the definition of the printer NODE, then restart CA Spool.
Reason:
During initialization of the CID-definition pool, CA Spool detected that the CID name xxxxxxxx is a duplicate name. CA Spool is terminated.
Action:
Correct the definition of the CID and then restart CA Spool.
Reason:
During initialization CA Spool was unable to allocate storage in CSA subpool 241 for the communication-interface-block pool. CA Spool is terminated.
Action:
Reduce the number of communication channels or ports defined and then restart CA Spool.
Reason:
A message has been issued, which must be examined by the ESFMSG0 exit, but no exit could be found. Processing continues.
Action:
Contact your systems programmer.
Reason:
CA Spool was unable to allocate storage for a new SAST table. CA Spool terminates processing.
Action:
Same as for message ESF028.
Reason:
During initialization CA Spool was unable to allocate storage in CSA subpool 241 for the functional subsystem interface-block pool. CA Spool is terminated.
Action:
Reduce the number of functional subsystems defined and then restart
CA Spool.
Reason:
No checkpoint data set was specified in the CA Spool initialization parameters. CA Spool terminates processing.
Action:
Add a CHKPTDS definition and then restart CA Spool.
Reason:
CA Spool was unable to start using the primary CKPT data set, but an alternate CHKPT data set was specified, the alternate dataset will be used to retry the CA Spool startup.
Action:
Contact your systems programmer.
Reason:
The system-parameter table as defined by parameter statements S1 through S7 is invalid for one of the following reasons:
Action:
Analyze parameter statements S1 through S7 and correct the problem. Start CA Spool again.
Reason:
CA Spool initialization processing has determined (by examining the checkpoint data set lock record) that another system has control of the CHKPTDSx checkpoint data set lock and has not relinquished the control.
CA Spool initialization processing cannot continue until it has exclusive control of the checkpoint data set lock. Initialization processing attempts to obtain the checkpoint data set lock after each second for the next 30 seconds. If CA Spool cannot obtain the lock, message ESF052 is issued. If CA Spool obtains the lock, initialization processing continues.
Action:
None.
Reason:
CA Spool initialization processing was not able to obtain control of the CHKPTDSx checkpoint data set. Either another system in the complex has abnormally terminated without releasing the checkpoint data set lock, or an I/O error occurred while CA Spool was attempting to obtain the lock.
If you are performing a cold start and using a new checkpoint data set or if you are performing a configuration-wide warm start, this message can be issued as part of normal processing and does not indicate an error condition.
If the operator replies Y, CA Spool initialization processing continues without the checkpoint data set lock. If the operator replies N, CA Spool terminates.
Action:
If this is a cold start using a new checkpoint data set or a configuration-wide warm start (no other systems in the multi-access-spool complex are running), reply Y. If this is not a cold start using a new checkpoint data set or a configuration-wide warm start, reply N and notify the systems programmer.
Reason:
The operator has made a valid request to change the fundamental CHKPTDSx checkpoint record. The operator is asked to confirm his intent to change the record. CA Spool waits for the operator to reply.
Action:
Reply Y if the checkpoint record is to be changed (this includes the creation of a new checkpoint data set); otherwise reply N.
Reason:
The CHKPTDSx checkpoint record is invalid for one of the following reasons:
Action:
Ensure that the system being started is the same as, or is compatible with, the last one run. If major incompatibilities in the CA Spool parameter values are discovered, cold start the system.
Reason:
Analysis indicates that at least one system in the complex is not dormant. Message ESF056 follows requesting operator response.
Action:
See message ESF056.
Reason:
Analysis determined that the complex is not dormant. The operator must determine if it is safe to continue. This message is preceded by message ESF055. CA Spool waits for operator reply.
Action:
Evaluate the complex environment and enter the appropriate reply. If N is entered, processing is terminated.
Reason:
CA Spool initialization has determined, through analysis of the checkpoint record, that the documented complex members are not currently active. Since a system can remain active between a failure and a restart without recording checkpoint records, the analysis must be confirmed by the operator. CA Spool waits for the operator to reply.
Action:
Determine whether all systems documented in the message text are inactive. You must reply Y if all documented systems are inactive. CA Spool will then perform a cold start or a warm start, depending on what was specified previously in response to message ESF000 (SPECIFY OPTIONS).
Reply N if one or more of the documented systems are active. CA Spool will then attempt to perform a warm start, regardless of the start specified previously.
An incorrect reply might cause CA Spool processing to terminate abnormally.
Reason:
Same as message ESF050, but the error was detected when CA Spool validated the CHKPTDSx checkpoint record during warm-start processing.
CA Spool terminates processing.
Action:
Same as message ESF050.
Reason:
CA Spool is being initialized. Text indicates whether the initialization includes all of the systems in the multi-access-spool complex or only the system with ID xxxx, and the type of initialization (cold or warm). Processing continues.
Action:
None.
Reason:
The operator is attempting to perform a warm start for CA Spool on this system. System xxxx has already issued an ESYS command to restart
CA Spool on this system. CA Spool initialization terminates.
Action:
Wait for the completion of restart on system xxxx, and then perform a warm start for CA Spool on this system.
Reason:
CA Spool failed to access the CHKPTDSx checkpoint record correctly. This could happen in the event of a hardware malfunction or the parameters in the device-attribute table do not match the device characteristics. This message is also issued if the checkpoint data set is too small to contain the required data. CA Spool terminates processing.
Action:
Check the device-attribute table to ensure that the values describe the device appropriately. Contact your systems programmer to find out if the checkpoint data set must be expanded.
Reason:
During warm start, CA Spool detected that one or more spool data sets have changed position or size. Message ESF063 displays the expected locations of the spool data sets.
Action:
See message ESF063.
Reason:
The expected positions of the spool data sets are listed by message ESF063. Location and size of the spool data sets must not be changed if system is to be warm started. All systems in a MAS complex must define the same spool data sets. CA Spool terminates processing.
Action:
Correct the SPOOL parameter statements and then restart.
Reason:
During warm start processing, CA Spool has detected an open file count below zero. CA Spool waits for the operator to reply.
Action:
If Y, CA Spool resets the open file count to zero and continues the initialization processing. If N, CA Spool terminates with a disastrous error code CH06 (see message ESF499).
Reason:
A BUILDQ warm start could not be performed because at least one system in the complex was not dormant. CA Spool terminates processing.
Action:
Ensure that the entire complex is dormant before starting a system with the BUILDQ option.
Reason:
During initialization CA Spool received a non-zero return code from a LOAD macro instruction attempting to load the module xxxxxxx. CA Spool terminates processing.
Action:
Contact your systems programmer.
Reason:
Dynamic LPA services failed to load module cccccccc with return code 99 and reason code 88888888.
For documentation of the CSVDYLPA return codes and reason codes, see the IBM z/OS MVS Authorized Assembler Services Reference manual.
Action:
Inform your system programmer.
Processing continues.
Reason:
During initialization, a LOADEXIT parameter aaaaaaa was found. A load was attempted for user exit nnnnnnnn. The status of the attempted load is reported.
Action:
If the load failed, a module with the name nnnnnnnn was not found in the CA Spool STEPLIB or link-library list. Make the module available to the CA Spool task and restart.
Reason:
During initialization CA Spool finds that module xxxxxxxx was not at the same level as the CA Spool system. CA Spool continues processing.
rAction:
Contact your systems programmer.
Reason:
CA Spool has issued a read (with RESERVE) operation to the checkpoint data set. Warning interval (in seconds) on WARNTIM parameter elapsed, but read operation has not completed. Another system in the MAS may have terminated while holding a read (with RESERVE) operation on checkpoint data set.
CA Spool issues this message every time the warning interval specified on WARNTIM expires until the read operation completes.
Action:
Ensure that other systems in the complex are operational. If the failed system cannot be restarted, the read (with RESERVE) must be cleared by pressing SYSTEM RESET on the failed system. Message ESF071 may be issued.
Reason:
CA Spool has successfully accessed the checkpoint data set. It has determined (by examining the checkpoint data set lock record) that system xxxx has control of the checkpoint data set lock and has not relinquished that control.
CA Spool cannot continue processing until it has exclusive control of the checkpoint data set lock. This message is repeated approximately every 30 seconds until the other system relinquishes control of the checkpoint data set lock.
Action:
If system xxxx has failed, issue an ESYS,RESET=xxxx to remove CA Spool control of checkpoint data set lock from system xxxx.
Reason:
A CA Spool system in a MAS configuration has detected that the status of a member (xxxx) in the complex has been altered. Processing continues.
Action:
If the status is reported as Appears Dormant, this message will be issued frequently, even during slow processing periods. Consider using automation software to take an action to bring attention when ESF072 message issues an Appears Dormant in the text.
EMAS/MAS members in a dormant status must be investigated immediately. An EMAS/MAS member becomes dormant when it ends and the CA Spool estate routine does not get control to alert the other members of its status change. This is likely due to a complete failure of the system where the now dormant members was running.
Confirm that the dormant member is no longer active and enter an ESYS, sysid command on each of the other member regions to reset the dormant member to member status.
Reason:
All available spool space has been allocated. This message will appear at approximately 30-second intervals until the condition is corrected.
CA Spool rejects all requests for direct access space until a purge function completes and the associated direct access space becomes available.
Action:
Determine which files are awaiting output (DF command), then initiate output processing for those files. If no output is queued (all files printed), then purge the files which have been printed (PD command).
Reason:
During initialization CA Spool was unable to obtain control over the specified subsystem name (see SUBID parameter). See message ESF077, which will follow this message.
Action:
Check that no CA Spool job using the same subsystem name is active.
Reason:
During initialization CA Spool was unable to obtain control over the specified SID/CHKPT names. See message ESF077, which will follow this message.
Action:
Check that no CA Spool system using the same checkpoint data set and system identification is active.
Reason:
During initialization CA Spool found that its subsystem interface was not in the dormant state. If the previous CA Spool job is no longer active, initialization continues. Otherwise, message ESF077 is issued.
Action:
Check that no CA Spool system using the same subsystem identification is active.
Reason:
See the messages ESF074, ESF075, or ESF076, which precede this. CA Spool waits for the operator to reply.
Action:
Reply Y if CA Spool is allowed to use this subsystem identification; otherwise, reply N.
Reason:
File queue utilization has passed the value specified in the TGWARN-initialization parameter. The value xxx displays the current percentage of the file queue in use. The size of the file queue is specified in NUMFQES. Processing continues.
Action:
None.
Reason:
CA Spool was unable to locate the printer user exit corresponding to the specification in the USEREXNO initialization parameter. CA Spool terminates processing.
Action:
Report this message to your systems programmer.
Reason:
CA Spool SVC was called from an unauthorized caller or with invalid parameters. The CA Spool SVC just returns to the caller.
Action:
Contact your systems programmer.
Reason:
USERID statements are not allowed in the parameters when SECUEXT=SAF is specified. User IDs are specified in SAFUID statements, or in the external security system. CA Spool stops during initialization.
Action:
Contact your systems programmer.
Reason:
A GETMAIN for a security parameter list failed. The request which is to be checked is denied access.
Action:
Increase the REGION parameter in the procedure.
Reason:
An DESTID statement with the same QUSERID, QDEST, QCLASS and QOWNER specifications as an earlier DESTID statement has been detected. CA Spool is terminated or REINIT is terminated.
Action:
Report this message to your systems programmer.
Reason:
A logical error has occurred. CA Spool is terminated or REINIT is terminated.
Action:
Report this message to your systems programmer. Take particular note of the code displayed in the message.
Reason:
A logical error has occurred during activation or deactivation of the SYSOUT Allocation Intercept support. If an RC=08 is returned, CA Spool is terminated.
Action:
Report this message to your systems programmer. Take note of the code displayed in the message.
Reason:
The label xxxxxxxx is specified on a SAFUID statement, but there is no SAFAT statement with that label.
Action:
Correct the error, then restart or reinitialize ESF.
Reason:
This message is displayed as an information message from the CA Spool checkpoint processor when the spool utilization has passed the value specified by the TGWARN initialization parameter. xxx specifies the current percentage of spool space in use.
Action:
Contact your systems programmer.
Reason:
CA Spool was unable to reserve the specified CPF Command Prefix Character. The CPF service returned completion code 99 and reason code 88. CA Spool terminates processing.
Action:
Investigate the return code and reason code received and take appropriate action. CPF return codes can be found in SYS1.MACLIB(CPF).
Reason:
CA Spool has abnormally terminated, but termination is delayed because communication channel xxxxxxxx opened by job jjjjjjjj has not been closed. User program has been notified through its CEND ECB or EXIT routine.
CA Spool enters wait state until the channel is closed.
Action:
Take the action necessary to terminate the job specified.
Reason:
Free of virtual storage failed. CA Spool terminates ESF999 disastrous error FREM.
Action:
Try to restart, report the problem to the systems programmer.
Reason:
Allocation of virtual storage failed. Terminates with ESF999 disastrous error GETM.
Action:
Try to restart, report problem to the systems programmer.
Reason:
The BUFSIZE parameter was too low for the spool data set yyyyyyyy on volume xxxxxxxx. CA Spool terminates processing.
Action:
Check SYSLOG for more details on what caused the problem.
Reason:
SPOOLDS-spool data set definitions removed since system last started.
CA Spool terminates processing.
Action:
Correct the errors in the spool data set definitions.
Reason:
SPOOLDS-spool data set definitions changed since system last started.
CA Spool terminates processing.
Action:
Correct the errors in the spool data set definitions.
Reason:
Allocated data set yyyyyyyy on volume xxxxxxxx could not be used. CA Spool terminates processing.
Action:
Correct the spool data set allocation.
Reason:
Checkpoint data set size insufficient for current spool data set and file queue configuration. CA Spool terminates processing.
Action:
Reduce the spool data set configuration if a new spool data set is being added by REINIT processing or increase the size of checkpoint data set if a cold or format start is being performed.
Reason:
An ESFFORM subtask has abended. If the problem occurs during startup,
CA Spool terminates. If the problem occurs during REINIT, CA Spool continues.
Action:
Contact your systems programmer.
Reason:
During initialization CA Spool was unable to change to unique CA Spool storage-protection key. This key must be established. CA Spool terminates processing.
Action:
Contact your systems programmer.
Reason:
CA Spool was unable to create an ESTAE environment during initialization. This environment must be established. CA Spool terminates processing.
Action:
Contact your systems programmer.
|
Copyright © 2011 CA.
All rights reserved.
|
|