These messages can be printed by the Job Entry Subsystem when a job is submitted or when output is printed:
| Message | Description |
|---|---|
| JES000002E JCL parser not available. | |
| JES000003Ennnnn duplicates an existing job number. | The job # specified during submission duplicates an already existing job #. You need to reset your job # mechanism. |
| JES000011E Batch Spool File Error; Status <operation> <file status>. | This error occurs while trying to access the spool and an unexpected file status was encountered. The operation is the action being performed, such as read or write. The file status is the file status returned from the operation. The file status is returned as 2 digits or as 9/nnn. Look up the file status error returned and take the appropriate remedial action. |
| JES000012I Batch Input Spool has been cold-started. | There was no casspool.dat file located in the same directory as the System catalog that this server is configured to use. A new one has been created. |
| JES000013I Jnnnnnnn requeued for restart at xxxxxx. | The job nnnnnnn has been queued for restart at the step (and where applicable the procstep) specified by xxxxxx. |
| JES000014E Jnnnnnnn not restarted. Job, Step or Procstep xxxxxx restart information not found. | The job nnnnnnn cannot be restarted because it does not contain the specified step (and where applicable the procstep) specified by xxxxxx. |
| JES000015I Jnnnnnnn does not exist for restart. | The job specified does not exist. This may be because the job has been deleted by another user or by the spool housekeeping process. |
| JES000016E Jnnnnnnn not executed. Undefined JES error, FEP-RC: (RC). | An attempt was made to restart a job that was not run with restart in effect, or files associated with the job have been deleted. |
| JES000017E Jnnnnnnn restart not allowed at Step/Procstep xxxxxx. | This error is displayed when the job or the step specified is non-restartable. |
| JES000018E Jnnnnnnn restart information could not be loaded. | There is no restart data available. This may be because the environment variable ES_JES_RESTART was not set to Y when the job was first run. |
| JES000019E Unable to allocate job number for job. | A job number could not be allocated for this job. Check the range of available job numbers. See also the JCLCM0164A message. |
| JES000020W Allocated job number percentage znn exceeds warning level nn. | The number of allocated job numbers, expressed as a percentage of all possible job numbers, exceeds the percentage defined in SPLJNO.dat as the warning level. Consider running spool housekeeping to free some job numbers. |
| JES000024I Batch Printer: xxxxxx | The printer named ‘xxxxxx’ has been initialized. |
| JES000025E Printer not found: xxxxxx | The printer named ‘xxxxxx’ was not located while enumerating through the printers defined on this machine. |
| JES000025I Printer not found: xxxxxx | The printer named ‘xxxxxx’ cannot be found but a printer exit is defined. The printer exit will handle the condition. |
| JES000026O Exit Module: xxxxxxxx | The batch printer specified in the previous JES000024I message is using a printer exit named ‘xxxxxxxx’ |
| JES000027E Printer assignment failed. RC = nnnnn | A failure occurred while trying to set the default printer for the batch printer SEP. A printer matching the specified name was found, but the setting as default printer for this SEP failed. |
| JES000028E Load failed for exit Module: xxxxxxxx | A printer was found which matches the specified printer name, but the exit routine specified for this batch printer (xxxxxxxx) was not found. |
| JES000029I xxxxxx on yyyyyy |
An information message relating to batch printers - yyyyyy = printer name. When issued during printer initialization, it indicates which printer device is being searched for by this batch printing SEP, or that the printer device is available (xxxxxx = "Locating" or "Available"). When issued while a document is being printed, it indicates which printer device is being used (xxxxxx = "<document name> on"). |
| JES000030E xxxxxx | While trying to print the document listed in the previous JES000029I message the spool tried to access the cataloged entry for this sysout dataset. There was a failure upon accessing the catalog specified by the message message |
| JES000031E Printer open failed. RC = nnnnn | A failure occurred in either the API call PC_PRINTER_OPEN or the API call PC_PRINTER_SET_FONT that occurs when a batch SEP tries to drive sysout output through to the defined printer. The failure return code is nnnnn |
| JES000032E Printer write failed. RC = nnnnn | A failure occurred while trying to write to the printer device attached to the batch printing SEP. The return code is documented in the API documentation for PC_PRINTER_WRITE |
| JES000033E Printer error accessing spool data: xxxxxx | A failure occurred while trying to access the physical dataset associated with sysout entry. The file status code of the failure is indicated by the message message. |
| JES000034E Jnnnnnnn - TIME parameter exceeds 65533 seconds after applying class multiplier (xxxxxx). | |
| JES000035E Jnnnnnnn - TIME parameter exceeds 65533 seconds after applying class multiplier (xxxxxx) | |
| JES000036E nnnnn xxxxxx | |
| JES000040I SSTM environment established successfully. nnnnn | The SSTM process has been initialised. The string xxxxx contains the subsystem type (CICS/IMS) and job number. |
| JES000041E SSTM initialization failure nnnnn | Initialisation of the SSTM process failed. The string xxxxx contains the failure type and the return code. |
| JES000042I SSTM not enabled: nnnnn | The JCL file specified for SSTM could not be found. The string xxxxx contains the subsystem type (CICS/IMS) |
| JES000050E JCL parsing error: RC = nnnnn. | While attempting to compile a piece of JCL for future execution, a failure occurred. The return code for the failure is documented by nnnnn |
| JES000051I Job Entry Subsystem (JES) services initialized. | The JES services for the process have been initialized |
| JES000052E Job Entry Subsystem (JES) initialization failed. Environment improperly configured. xxxxxxxx | When a server is started, JES performs some validation checks to ensure that databases can be properly allocated. These fail
messages indicate that this Initial Validation Process detected an error. The error indicates that the IVP was unable to allocate
and test DSN on the system catalog. The likely causes are:
|
| JES000053E JES validation - Catalog Open failed - RC = <return code> | |
| JES000054E JES validation - Allocate file failed - RC = <return code> | |
| JES000055E JES validation - MFALLOC_PROP undefined or invalid : <return code> | |
| JES000056E JES validation - MVSJOBNO check failed - reason = <return code> | |
| JES000057E JES validation - MFJCLCFG failed - RC = <return code> Reason = <reason code> | |
| JES000058E JES validation - Product requires new spool control files. Run spool conversion utility, splconv, to create them. | The region has been started with a casspool.dat file, but without a SPLJOB.dat file. The SPLCONV conversion program should be run to create SPLJOB.dat (and the other SPL* files) from the existing casspool.dat records. |
| JES000120S Failed to get SPLJOB record lock. FS: <file status>, Job# <job number>, Loc: <source location> | This error, together with JES000121S is generated by the spool module when it fails to obtain the required lock on a record. The number of times the module retries to obtain the lock can be adjusted via the environment variable: CASSPOOL_LOCK_RETRY_COUNT. |
| JES000121S Failed to get SPLJOB record. FS: <file status>, Job# <job number>, Loc: <source location> | This error, together with JES000120S is generated by the spool module when it fails to obtain the required lock on a record. The number of times the module retries to obtain the lock can be adjusted via the environment variable: CASSPOOL_LOCK_RETRY_COUNT. |
| JES000122S Failed to get SPLDSN record lock. FS: <file status>, Job# <job number>, DD# <DD number>, Loc: <source location> |
This error, together with JES000124S is generated by the spool module when it fails to obtain the required lock on a SPLDSN record. |
| JES000123S Too many SYSOUT records for Job number <job number> | The SPLDSN DD sequence number exceeds the maximum possible number. |
| JES000124S Failed to get SPLDSN record. FS: <file status>, Job# <job number>, DD# <DD number>, Loc: <source location> |
This error, together with JES000122S is generated by the spool module when it fails to obtain the required lock on a SPLDSN record. |
| JES000125S Failed to update SPLJOB record. FS: <file status>, Job# <job number>, Loc: <source location> | An error was encountered while attempting to rewrite an existing SPLJOB record. |
| JES000126S Failed to update SPLDSN record. FS: <file status>, Job# <job number>, DD# <DD number>, Loc: <source location> | An error was encountered while attempting to rewrite an existing SPLDSN record. |
| JES000127I Attempting to get SPLJOB record lock. FS: <file status>, Job# <job number>, Loc: <source location>, Tries: <retry count> | A locked record was encountered on SPLJOB. This message will be issued after every 50 unsuccessful attempts to lock the record. |
| JES000128I Attempting to get SPLDSN record lock. FS: <file status>, Job# <job number>, DD# <DD number>, OUT# <OUTPUT number>, Loc: <source location>, Tries: <retry count> | A locked record was encountered on SPLDSN. This message will be issued after every 50 unsuccessful attempts to lock the record. |
| JES000129S Failed to write SPLJOB record. FS: <file status>, Job# <job number>, Loc: <source location> | An error was encountered while attempting to write a new SPLJOB record. |
| JES000131E Unrecoverable file error FS: <file status>, Work suspended until operator input received | A fatal error was detected on a file operation. For example, the file name SPLJOB, and file status code are displayed in the message text. |
| JES000132S Failed to write SPLDSN record. FS: <file status>, Job# <job number>, Loc: <source location>, DD# <DD number>, OUT# <OUTPUT number>, Loc: <source location> | An error was encountered while attempting to write a new SPLDSN record. |
| JES000140E Printer Exit reported error printing <dataset information>. RC = <return code>. | Where:
The following is an example error message: JES000140E Printer Exit reported error printing SYSAD:MCDPP302:01005:STEP01::SYSUT2:000001:000000:A. RC = +000000009 |
| JES000222E Jnnnnnnn canceled by operator | Job # job-number was canceled via the casout command -k option or via the ESMAC Spool view function |
| JES000913E Jnnnnnnn User xxxxxx has an invalid password or no longer has auth to exec JCL. | Jnnnnnnn represents the job number, and User xxxxxx represents the user. |
| JES000914E Jnnnnnnn User xxxxxx is not a surrogate of User zzzzzz. | Jnnnnnnn represents the job number, and User xxxxxx represents the user. |
| JES000915E Jnnnnnnn User xxxxxx does not have authority to submit job zzzzzz. | Jnnnnnnn represents the job number, and User xxxxxx represents the user. |
| JES000916E Jnnnnnnn User xxxxxx has insufficient authority to create job log. | Jnnnnnnn represents the job number, and User
xxxxxx represents the user.
In order for a job log to be created, a relevant PHYSFILE rule must exist to allow this user access to the required directory. See Resource Classes for JES Security for more information. |