This document lists the ESY console messages, together with their explanation and the action required.
All console messages prefixed with ESY4 are used in separate ESY utilities only.
| Message | Explanation | Action | ||||||
|---|---|---|---|---|---|---|---|---|
| ESY0001I Parameters for this run:. | A subset of the startup parameters will be displayed on the console after this message. | No action required. | ||||||
| ESY0002I :1:. | A startup parameter keyword and value pair is displayed. | No action required. | ||||||
| ESY0003I ENTIRE SYSTEM SERVER :1: is ready (V: :2:). | Node :1: is ready for work now. :2: contains the version number of Entire System Server. | No action required. | ||||||
| ESY0004I Single-user ENTIRE SYSTEM SERVER started. | Single user mode (TSO/batch) started. | No action required. | ||||||
| ESY0005I ENTIRE SYSTEM SERVER :1: stopped. | Node :1: has been stopped. | No action required. | ||||||
| ESY0006I Single-user ENTIRE SYSTEM SERVER stopped. | Single user mode (TSO/batch) stopped. | No action required. | ||||||
| ESY0007I Inactive user :1: ESYID :2: has been purged. | Elapsed NONACT time for user :1:. All resources of this user are freed. | No action required. | ||||||
| ESY0008W - ONLY VIEW COMMUNICATE-STD AVAILABLE | Only view COMMUNICATE-STD available. | |||||||
| ESY0012I - VTAM OPERATOR ACB IS NOW OPEN | The VTAM ACB defined in the VTAMACB sysparm was opened successfully. | No action required. | ||||||
| ESY0013I :1:. | Display Entire System Server user(s) as reponse to operator command USERS. | No action required. | ||||||
| ESY0014I - NO VSAM FILES ARE OPEN | No VSAM files are open or DDNAME specified to free does not exist. | No action required. | ||||||
| ESY0015I - :1: | Variable text for display of VSAM files. | No action required. | ||||||
| ESY0016I - VSAM FILE :1: WILL BE FREED | This is a response to the operator command VSAMFREE :1:. The VSAM file with DDNAME :1: will be de-allocated. | No action required. | ||||||
| ESY0017I Requested user(s) not found. | The operator requested to display/cancel a user who is not active. | No action required. | ||||||
| ESY0018I - :1: CANCELLED | User :1: was cancelled due to operator request. | No action required. | ||||||
| ESY0019I - :1: | Variable text for display of active tape drives. | No action required. | ||||||
| ESY0020I - NO TAPES ALLOCATED | This is a response to operator command TAPES/TAPEFREE xxx. No tape drives are allocated to Entire System Server users. | No action required. | ||||||
| ESY0021I - TAPE UNIT :1: HAS BEEN FREED | This is a response to operator command TAPEFREE xxx. The tape drive at address xxx has been de-allocated. | No action required. | ||||||
| ESY0022I - TAPE UNIT :1: N O T FREED | This is a response to operator command TAPEFREE xxx. The attempt to de-allocate the tape drive at address xxx failed. | No action required. | ||||||
| ESY0023W - MODULE NOT LOADED. | The specified module could not be LOADED. | No action required. | ||||||
| ESY0024I - MODULE RELOADED | The specified module was successfully reloaded. | No action required. | ||||||
| ESY0026I - VTAM PRINTER ACB IS NOW OPEN | The VTAM ACB defined in the SPOOLACB sysparm was opened successfully. | No action required. | ||||||
| ESY0030E - No CLOG dataset found, logging disabled | No command logging data set(s) CLOG or CLOGR1/CLOGR2 was found, although LOGGING=YES had been requested. | Specify DD statement(s) for command logging data set(s) in your JCL. | ||||||
| ESY0031I - Command logging enabled | Command logging has been enabled in response to a LOGGING=YES command. | No action required. | ||||||
| ESY0032I - Command logging disabled | Command logging has been disabled in response to a LOGGING=NO command. | No action required. | ||||||
| ESY0037I - Command logging file full, logging disabled | Command logging has been disabled due to an out-of-space condition of the CLOG data set. | No action required. | ||||||
| ESY0038I - Command logging file full, DSN=<command.log.data.set.name>, logging switched to next logging file | Command logging has been switched to the alternate logging file after an out-of-space condition on one of the dual logging data sets. | No action required. | ||||||
| ESY0040I - :1: | This message is issued by the EVENTS operator command. It has various formats that will be interpreted by technical support. | No action required. | ||||||
| ESY0050W - ENTIRE SYSTEM SERVER IS N O T APF-AUTHORIZED | The load libraries are not defined as APF-authorized. Certain functions will not be available. | No action required. | ||||||
| ESY0054W - NATURAL SUB-TASK MODULE :1: NOT AVAILABLE | The Natural module :1: was not found and could not be loaded. It was specified in the startup parameter 'NATMOD='. Natural subtasking has been stopped. | Check startup parameter NATMOD and the load libraries. | ||||||
| ESY0055W - CANNOT LOCATE SUBSYSTEM MODULE :1: | Subsystem module SUBSxxxx not found. The names of the subsystems are specified in the startup parameter 'SUBSYS='. Subsystem cannot be started properly. | Check startup parameter SUBSYS and the load libraries. | ||||||
| ESY0058W - "IDENTIFY" TO POWER FAILED. RS=:1: | POWER interface initialization failed with code :1:. | Contact your systems programmer. | ||||||
| ESY0059W - LOAD FOR MODULE :1: FAILED | Module :1: was not found. If it is critical, run will terminate. Otherwise, it will continue. | Check your STEPLIB-concatenation. | ||||||
| ESY0061W - NATURAL subtask ended :1: | Normal or abnormal termination of a Natural subtask. One of the
following codes is shown:
Note |
Examine the code and if necessary, Contact Customer support. | ||||||
| ESY0063W - SUB-TASK ABENDED. USER N O T POSTED | An error occurred during abend processing. | contact Software GmbH. | ||||||
| ESY0064W - CPU TIMEOUT FOR USER :1: VIEW :2: (EP=:3: PSW=:4:) | A CPU loop was detected. See the startup parameter 'LOOP='. The subtask has been cancelled with user abend 1234. | No action required. | ||||||
| ESY0066W - APF AUTHORIZATION REQUIRED TO WRITE SMF RECORDS | Entire System Server is running without authorization and therefore cannot write SMF records. | Contact your systems programmer. | ||||||
| ESY0067W - SMF IS NOT ACTIVE IN SYSTEM OR NO USER RECORDS ALLOWED | Entire System Server cannot write SMF records due to system settings. | Contact your systems programmer. | ||||||
| ESY0068W - RETURN CODE :1: WRITING AN SMF RECORD | Entire System Server cannot write SMF records. | Contact your systems programmer. | ||||||
| ESY0069W - OPEN FOR VTAM OPERATOR FAILED WITH ERROR :1: |
An attempt to open the VTAM ACB whose name was specified in the startup parameter 'VTAMACB=' has failed. Common errors are: 088 - Application name is already active. 090 - The application was not defined or is not active. Every minute, another attempt will be made. If the open is successful, the message ESY0012I will appear. |
Contact your VTAM systems programmer. | ||||||
| ESY0070I - CA SYSTEM ADAPTER DETECTED | During initialisation, the Computer Associates System Adapter was found to be active. |
None. CA-Dynam/D API DYNACC. PHASE is accessible in the libraries specified in the LIBDEF PHASE SEARCH JCS statement. |
||||||
| ESY0071W - MESSAGE QUEUE LENGTH EXCEEDED - MESSAGES LOST | The VTAM incore message buffer has been filled. The startup parameter 'VTAMQLEN=' determines its length. The default is 100 (k). | Change value of VTAMQLEN and restart Entire System Server. | ||||||
| ESY0072W - OPEN FOR VTAM PRINTER ACB FAILED (ERROR=:1:) | An attempt to open the VTAM ACB whose name was specified in the startup parameter 'SPOOLACB=' has failed. Common errors are: 088 - Application name is already active. 090 - The application was not defined or is not active. Every minute, another attempt will be made. If the open is successful, the message ESY0012I will appear. | Contact your VTAM systems programmer. | ||||||
| ESY0073W Invalid command. | An invalid operator command was entered. | Correct it. | ||||||
| ESY0074W - NATURAL-SUB-TASK - SYSOUT ALLOCATION FAILED | An attempt to allocate a sysout dataset to contain output from Natural programs failed. | Please check job control of Entire System Server. | ||||||
| ESY0076W - NATURAL SUBTASK PARAMETER ERROR | A parameter passed to the NATURAL-SUB-TASK was in error. | Correct parameter error and retry. | ||||||
| ESY0077W - CANNOT LOAD NATURAL MODULE | The specified NATURAL-SUB-TASK module could not be loaded. | Check startup parameter NATMOD and the load libraries. | ||||||
| ESY0078W - GETMAIN ERROR | Storage requested via GETMAIN/GETVIS failed. | Run Entire System Server in a task with more memory. | ||||||
| ESY0079W - SECURITY CLASS OPERCMDS NOT DEFINED | The security class OPERCMDS is not defined to your external security system (RACF/ACF2/TSS etc). | Contact your systems programmer. | ||||||
| ESY0081W User :1: has requested termination. | FUNCTION = 'XEND' in view NATPROC-USERS was issued. Entire System Server will terminate now. | No action required. | ||||||
| ESY0082W - VTAM PRINTER "SETLOGON START" FAILED | A VTAM printer 'SETLOGON START' failed. | Verify your VTAM definitions. | ||||||
| ESY0096E - Review Installation Error: RAOSLOCL not found | The Review local mode interface module could not be loaded by Entire System Server. | Verify that the Review load library is included in the STEPLIB concatenation for Entire System Server. | ||||||
| ESY0098E - Review Installation Error: calls from address space <jobname> could not be processed by Review. | A command log extension received from address space <jobname> was incomplete. | Verify that the requesting address space is running Natural with profile parameter ADAPRM=ON. | ||||||
| ESY0100E Bad parm card: :1:. | An invalid startup parameter was detected. | Correct parameter card. | ||||||
| ESY0104E - ERROR(S) DETECTED DURING ENTIRE SYSTEM SERVER STARTUP | See previous error messages. | Correct your environment settings and restart Entire System Server. | ||||||
| ESY0105E - VTAM OPERATOR SUB-TASK HAS ABENDED | contact Software GmbH. | |||||||
| ESY0107E - SMF WRITER SUB-TASK HAS ABENDED | contact Software GmbH. | |||||||
| ESY0108E - WORK FILE OPEN SUB-TASK HAS ABENDED | contact Software GmbH. | |||||||
| ESY0109E - VTAM PRINTER SUB-TASK HAS ABENDED | contact Software GmbH. | |||||||
| ESY0111E - IDENTIFY FOR MODULE :1: FAILED WITH CODE :2: - TERMINATING | Macro 'IDENTIFY' failed. The job is terminated. | Contact your systems programmer. | ||||||
| ESY0112E Single-user ENTIRE SYSTEM SERVER is abending because of initialization errors. | Errors occurred during requesting of work area or loading of modules. Load library is not assigned or is not accessible. | Check your job control. | ||||||
| ESY0119E - FILETABLE PARM ERROR (DYNAMIC!STATIC) | Invalid FILETABLE parameter detected. Possible values are DYNAMIC or STATIC. | Correct parameter card and restart the Entire System Server. | ||||||
| ESY0120E - VSAMLABELS PARM ERROR (YES!NO) | The value specified for the VSAMLABELS system parameter was in error. Valid values are YES and NO. | Correct parameter card. | ||||||
| ESY0121E - PRODID DEFINE ERROR (:1:) | The PRODID DEFINE function completed with return code :1:. | |||||||
| ESY0122E - PRODID AUTHORIZATION ERROR (:1:) | The PRODID AUTHORIZE function completed with return code :1:. | |||||||
| ESY0123I - PARAMETERS BPDIRS AND BPSIZE ARE IGNORED | These ESY sysparms were detected. They are no longer required and will be ignored. | Remove these parameter cards. | ||||||
| ESY0125E - READCONS SUB-TASK HAS ABENDED | The MCS extended console subtask has abended. | |||||||
| ESY0126E - USE START-UP-PARAMETER ":1:" | The specified ESY system parameter is no longer valid and should be replaced with :1:. | Correct ESY sysparms. | ||||||
| ESY0135E - APPC server not found or abended. APPC session was deallocated | The APPC/MVS transaction program initiated by the SYSTEM-COMMAND view processor could not be started. | Verify your APPC-related startup parameters and your APPC/MVS resource definitions. If problem persists, Contact Customer support. | ||||||
| ESY0136E - startup parameter APPC-<keyword> = <value> is invalid | One of the startup parameters APPC-TPNAME, APPC-LUNAME or APPC-MODENAME contains an invalid value. | Verify your APPC-related startup parameters and your APPC/MVS resource definitions. If problem persists, Contact Customer support. | ||||||
| ESY0137E - APPC server error XCOMTP46 <service> done RC=<rc> | The APPC/MVS transaction program initiated by the SYSTEM-COMMAND view processor received an error return code from an APPC/MVS callable service. Possible services names are ATBCFMD, ATBEES3, ATBEXAI, ATBGETC, ATBRCVW and ATBSEND. | Contact Customer support. | ||||||
| ESY0150I - :1: activated (:1:,:2:) | The MCS extended console :1: has been successfully activated with return code :2: and reason code :3:. | |||||||
| ESY0151I - Store=:1: Len=:2: Slots=:3: | The MCS extended console has allocated an internal console table with storage address=:1:, length=:2: and slots=:3:. This is a follow up message to ESY0150I. | |||||||
| ESY0152I - :1: deactivated (:1:,:2:) | The MCS extended console :1: has been successfully deactivated with return code :2: and reason code :3:. | |||||||
| ESY0153E - :1: :2: (:3:,:4:) | The MCS extended console read routine for console :1: function :2: has detected an error with return code :3: and reason code :4:. | |||||||
| ESY0154W - :1: Console Table lock limit reached | The internal console table could not be locked after multiple attempts. | Retry request. If problem persists, contact your system programmer. | ||||||
| ESY0155W - :1: READCONS task termination forced | The MCS extended console read routine for console :1: has been forced into termination. | |||||||
| ESY0176W - INSTALL ERROR COMPBTCH NOT LINKED | The Com-plete batch routine 'COMPBTCH' has not been linked to the ESY 'SEND-MESSAGE' view processor (XCOMV019). | Inform your system programmer. | ||||||
| ESY0179W - RSP :1: FROM COM-PLETE BATCH SUPPORT | The Com-plete batch support routine 'COMPBTCH' has returned the response code :1: (SEND-MESSAGE view processor). | No action required. | ||||||
| ESY0182W - ATTACH FOR CONSOLE READ TASK FAILED | The MCS extended console read task could not be attached. | Inform your system programmer. | ||||||
| ESY0183W - READCONS SUBTASK RE-ATTACH LIMIT REACHED | The MCS extended console read task could not be attached because the retry limit had been reached. | Inform your system programmer. | ||||||
| ESY0188I - OVERWRITING OLD NPRSTUB2 VECTOR ENTRY | Entire System Server found an NPRSTUB2 vector from a prior run; this generally means that the prior run ended abnormally. | No action required. | ||||||
| ESY0189I - ESY0189W GETVIS FOR NPRSTUB2 VECTOR FAILED | Entire System Server was unable to get SVA for installing NPRSTUB2. | Check SVA settings. Message ESY0890W will also be issued. | ||||||
| ESY0190W - NPRSTUB2 NOT FOUND IN SDL, NO EXTERNAL TRACING MONITORING AVAILABLE. | Module NPRSTUB2 was not found in SVA. | Check if NPRSTUB2 was loaded into SDL at IPL if you plan to use ESYTRACE to monitor this Entire System Server session. Otherwise, no action required. | ||||||
| ESY0192I - NPRSTUB2 FOUND IN SVA AT XXXXXXXX | Module NPRSTUB2 was found in SVA at address XXXXXXXX. | No action required. | ||||||
| ESY0198E DBID :1: inactive, restart ESY if ready. | Adabas Nucleus :1: is not ready yet. The Natural subtask environment cannot be started since all databases defined in startup parameter SYNCDB are active. Entire System Server terminates abnormally. | Restart Entire System Server after all depending Adabas nuclei are active. | ||||||
| ESY0199W ADALNK RC :1: calling DBID :2:. | Adabas call has returned a non-zero return code. | No action required. | ||||||
| ESY0200I <task> <status> <monitor information> | The message provides status information for the monitor subtask(s) of ESM product(s) running in the Entire System Server address space in response to a STATUS <product> command. | No action required. | ||||||
| ESY0275E PRODUCT :1: - error :2: during shutdown. | The requested SAT product :1: cannot be stopped. Check the error code :2:. | Correct error if possible. | ||||||
| ESY0298E Entry in table not found. | The requested console message was not found in the text table. | Please contact Software GmbH. | ||||||
| ESY0299E Error in WTO-routine. | An unrecoverable error occurred in console message handler. | Please contact Software GmbH. | ||||||
| ESY0305E Invalid value for NUMTASK, SERVER-MIN, SERVER-MAX. |
The values specified for the startup parameters mentioned above are not consistent. Please see the section Startup Parameters and the subsection Dynamic Server Management for Entire System Server in the Entire System Server Administration documentation for a detailed description of these startup parameters and the dependencies between each other. |
Correct startup parameter and restart Entire System Server. | ||||||
| ESY0306I SERVER task starting. | This message is issued before the Dynamic Server Management tries to create another server [sub]task. | No action required. | ||||||
| ESY0307I SERVER task :1: active. | This message is issued after Dynamic Server Management has successfully created another server [sub]task. | No action required. | ||||||
| ESY0308I :1:. | Display Entire System Server servers(s) as reponse to operator command SERVERS. | No action required. | ||||||
| ESY0309I Dynamic SERVER management enabled. | Dynamic Server Management (DSM) is creating the DSM environment now after detecting start parameter/operator command 'SERVER-DYN=YES'. | No action required. | ||||||
| ESY0310I Dynamic SERVER management disabled. | Dynamic Server Management (DSM) is deleting the DSM environment now after detecting start parameter/operator command 'SERVER-DYN=NO. | No action required. | ||||||
| ESY0311I SERVER task :1: stopping. | This message is issued before Dynamic Server Management will stop the server [sub]task. | No action required. | ||||||
| ESY0312I SERVER task :1: stopped. | This message is issued from the server [sub]task after receiving the stop request from the Dynamic Server Management. The termination processing is running now. | No action required. | ||||||
| ESY0313W Invalid value. | The operator command handler has detected an invalid value for a valid operator command. | Please read the description of the operator command and use a correct value. | ||||||
| ESY0315I Command SHUTDOWN ALL not issued yet to stop NATURAL-SUB-TASKING. | This message is a response to operator command 'START ALL' if Natural subtasks are still active and operator command 'SHUTDOWN ALL' has not been issued yet. | Issue operator command 'SHUTDOWN ALL' to stop all running Natural subtasks and repeat command 'START ALL' afterwards. | ||||||
| ESY0318I NATURAL-SUB-TASKING still active. Command rejected. | This message is a response to operator command 'START ALL' if Natural subtasks are still active. Operator command 'SHUTDOWN ALL' has been issued but not finished yet. | Retry command later. | ||||||
| ESY0403E Number of message table entries invalid. | The supplied number of message table entries is greater than maximum. | Redefine value in ESYCONS startup JCL (range 1 - 65535). | ||||||
| ESY0404W Default number of message table entries used. | No value has been specified for number of message table entries. | Default value 92 is used. | ||||||
| ESY0501E ESY NOT APF AUTHORIZED | Entire System Server needs to run from a authorized Steplib, otherwise it stops. | Ask your system programmer to add all load-libs of this STC-JCL to APF authorized list. | ||||||
| ESY0512E - Unable to locate common area. XCOMJESC initialization failed. | The Common JES Interface could not locate Entire System Server's common area. | Contact Customer support. | ||||||
| ESY0513I SSI request 85 processed to action.HASP250 job-name action -- (JOB KEY WAS job-key) | A subsystem interface (SSI) JES request 85 to modify a
job was successfully processed. Possible actions are:
HOLD, RELEASE, PURGE,
CANCEL, CHANGE.
|
No action required. | ||||||
| ESY0515I - Initialization sequence error for XCOMJESC. | A repeated initialization request was issued to the Common JES Interface. | Contact Customer support. | ||||||
| ESY0519I - Subsystem ........ is not supported by XCOMJESC. | Entire System Server is running under a subsystem that is neither JES2 nor JES3. The Common JES Interface cannot access spool data. | Start Entire System Server under a supported subsystem (JES2 or JES3). | ||||||
| ESY0520I - SSI request .. failed with RC .. and SSOBRETN .. | A subsystem interface (SSI) request failed. | Contact Customer support. | ||||||
| ESY0523E - Unable to determine nodename. XCOMJESC initialization failed. | The Common JES Interface could not determine the JES node name. | Contact Customer support. | ||||||
| ESY0554I - Job Entry Subsystem is ........ ........, nodename ........ | The Common JES Interface has successfully initialized. | Verify the JES common name, version and node name to make sure Entire System Server is running under the correct subsystem. | ||||||
| ESY0556W - Support for ........ ........ is not implemented. | The Common JES Interface does not support the current version of JES2 or JES3. | Contact Customer support to obtain a fix adding support for the current version of JES2 or JES3. | ||||||
| ESY0563I - $CBIO failed, RC .., MTTR ........, for ........ ........ | A request failed to read a control block from JES2 spool for the specified job id / job name. | Contact Customer support. | ||||||
| ESY0567I - IATXBKIO failed, RC .., SPADR ............, for .... of ........ ........ | A request failed to read a control block from JES3 spool for the specified job id / job name. | Contact Customer support. | ||||||
| ESY0571I - SSI request 71 failed, RC .., SSOBRETN .., SSJIRETN ... | A request failed to the JES job information service. | Contact Customer support. | ||||||
| ESY0578E - Unable to obtain common area. XCOMJESC initialization failed. | The common JES interface could not obtain storage for its common constant parameter area. | Contact Customer support. | ||||||
| ESY0579I - SSI request 79 failed with RT .. and SSS2REAS .. | A request failed to the SYSOUT API interface. | Contact Customer support. | ||||||
| ESY0580I - SSI request 80 failed with RT .. and STATREAS .. | A request failed to the Extended Status interface. | Contact Customer support. | ||||||
| ESY0585I: A subsystem interface (SSI) JES request 85 failed. | A subsystem interface (SSI) JES request 85 failed. | No action required. | ||||||
| ESY0599I - Error (un)allocating SYSOUT dataset, RC .., reason ....DSN............................................ | An error occurred during allocation or unallocation of a SYSOUT dataset. | Contact Customer support. | ||||||
| ESY0870I - TRACE ESTAE/STXIT environment initialized | The ESTAE/STXIT environment was created. | No action required. | ||||||
| ESY0871I - TRACE dump dataset opened | The trace save dataset was opened successfully. | No action required. | ||||||
| ESY0872W - TRACE dump dataset open failed, RC=### | An error occurred when trying to open the trace save dataset. RC is the return code from the OPEN macro. | Determine the reason from the return code and correct the error. Entire System Server will still run, but will not save TRACE data. | ||||||
| ESY0873W - TRACE ESTAE/STXIT environment creation failed, RC=### | Creation of the ESTAE/STXIT environment failed. RC is the return code. | Contact our support. | ||||||
| ESY0874I - TRACE ESTAE/STXIT environment deleted | The ESTAE/STXIT environment was deleted. | No action required. | ||||||
| ESY0875I - TRACE dump dataset closed | The trace save dataset was closed successfully. | No action required. | ||||||
| ESY0876W - TRACE dump dataset close failed, RC=### | An error occurred when trying to close the trace save dataset. RC is the return code from the CLOSE macro. | Determine the reason from the return code and correct the error. Entire System Server will still run, but will not save TRACE data | ||||||
| ESY0877I - TRACE ESTAE/STXIT environment entered | An event occurred that caused the ESTAE/STXIT environment to be entered | No action required. | ||||||
| ESY0878W - No DLBL or unable to access SYS021 | The DLBL TRACSAV was not found or SYS021 was not assigned in the JCS. | Check JCS and correct the error. | ||||||
| ESY0879W - TRACE data will not be saved in case of abend | Due to a preceding error, trace data will not be saved. | Check for messages issued earlier. | ||||||
| ESY0880I - NPR not authorized, TRACE not available | Entire System Server must be APF authorized for TRACE to be functional. | Determine why Entire System Server is not APF authorized, and correct the error if necessary. | ||||||
| ESY0881I - TRACE storage created - #####K - XXXXXXXX | Trace storage was obtained. Size and location are given. | No action required. | ||||||
| ESY0882W - TRACE requested but length is 0 | TRACE-LEN was given as 0. | Check startup parameters. | ||||||
| ESY0883E - TRACE storage creation failed, R15=###, R0=### | Entire System Server was unable to obtain trace storage. R15 and R0 are the return and reason codes. | Determine the reasons for the error and correct it. Tracing will not be done. | ||||||
| ESY0884W - TRACE storage deletion failed, R15=###, R0=### | Entire System Server was unable to delete trace storage. R15 and R0 are the return and reason codes. | Determine the reasons for the error and correct it. | ||||||
| ESY0885I - TRACE storage deleted | Trace storage was deleted. | No action required. | ||||||
| ESY0886E - TRACSAV EOX entered, file closed | The EOX exit was entered while trying to write trace save data. | Contact our support. | ||||||
| ESY0887E - TRACSAV ERROPT entered, file may be incomplete | The ERROPT exit was entered while trying to write trace save data. | Contact our support. | ||||||
| ESY0888W - Invalid CHANGE or TRAP value | An invalid parameter was passed via the TRACE CHANGE or TRAP operator command. | Correct the error and reissue the command. | ||||||
| ESY0889E - No TRACE area found. Command ignored. | This message is issued when the TRACE=Y or TRAP nn operator command is entered and TRACE=NO was specified in the startup parameters. | To use the TRACE or TRAP operator commands, specify either TRACE=PREP or TRACE=YES in the startup parameters. | ||||||
| ESY0890W - ESYTRACE program will not be able to access TRACE data | Due to a prior error, real-time monitoring via the ESYTRACE program will be impossible. | Check for messages issued earlier. | ||||||
| ESY0891W - Unable to create name/token, RET=### | Entire System Server was unable to create a NAME/TOKEN pair. RET is the return code from NAME/TOKEN services. | Contact our support. | ||||||
| ESY0892W - Unable to delete name/token, RET=### | Entire System Server was unable to delete a NAME/TOKEN pair. RET is the return code from NAME/TOKEN services. | Contact our support. | ||||||
| ESY0893W - ALESERV EXTRACTH failed, RET=### | Entire System Server was unable to get the home address space ALE. | Contact our support. | ||||||
| ESY0894W - NPRSTUB2 vector invalid | Data in the NPRSTUB2 vector was found to be incorrect. | Contact our support. | ||||||
| ESY0895W - XCOMSTUB vector invalid | Data in the NPRSTUB2 vector was found to be incorrect. | Contact our support. | ||||||
| ESY0898W - TRACE dump dataset creation requested, but it cannot be serviced | An event occurred where TRACE data would be saved to disk, but a prior error prevents saving. | Check for messages issued earlier. | ||||||
| ESY0899I - TRACE storage dumped to dataset | Trace data was successfully written to disk. | No action required. | ||||||
| ESY0999E - Mailer error: :1:. | Unrecoverable error occurred during E-Mail processing. | See also output file for detailed error description. Consult your Network Administrator. | ||||||
| ESY1030I - :member: IEWLCNVT failure, R15=:2:, R0=:3:ESY1030I dsname | (2-line message) When processing the noted load module or program object, IEWLCNVT indicated that the directory data was invalid with the specified return (R15) and reason (R0) codes. The calling program is not notified by a value in ERROR-CODE/TEXT, however USER-DATA-LENGTH will be zero and USER-DATA will be blank. | Use AMBLIST or other methods to check on the validity of the directory data. | ||||||
| ESY1600E - License file not assigned. | Logical assignment LICENSE is missing. | Assign the license file to logical unit LICENSE (DD/ASSGN/ADD-FILE-LINK). | ||||||
| ESY1601E - Module LICMAIN cannot be found. | The license check module is loaded dynamically. However, it was not possible to find the license check module. | The MLC load library is not concatenated to the STEPLIB chain. | ||||||
| ESY1602E - Load for module LICMAIN failed. | The license check module is loaded dynamically. However, it was not possible to load the license check module. | The MLC load library is not concatenated to the STEPLIB chain. | ||||||
| ESY1603E - Time conversion failed. | Macro STCKCONV did return an
error.
|
Contact Customer support. | ||||||
| ESY1604E - License buffer exceeded. | The size of the license buffer is set to 32K. The buffer is not large enough to contain all license data. | Contact Customer support. | ||||||
| ESY1605E - Bad license file format or I/O error. | The file attributes do not match the attributes listed in the documentation. | Refer to section <link>. | ||||||
| ESY1606I - License check completed. | The license file was successfully checked and is finished. | No action required. | ||||||
| ESY1607E :1:. | Error messages generated by LICMAIN are reported here. | Consult the error text :1: and take appropriate action. | ||||||
| ESY1608I - Preceding License Key Errors are ignored. | One or more errors occurred during the license check. | These errors are deliberately ignored. | ||||||
| ESY1609E - License key error. | An error occurred while processing the Entire System Server License file. Additional error text will provide more information. | Consult the additional error text and take appropriate action. | ||||||
| ESY1610I - Emergency license key in use. | The Entire System Server is running with an emergency license key. | Get a valid license file. | ||||||
| ESY3001E - UNABLE TO ACQUIRE STORAGE FOR FILEID TABLE | Storage for the internal label management table could not be obtained. | Check partition size and if necessary decrease NUMLIBS parameter. | ||||||
| ESY3004E - FILEID TABLE INITIALIZATION ERROR | An error has occurred during initialization of the file ID table. | This message should be preceded by other error messages. Investigate the reasons for those messages and if necessary contact Software GmbH customer support. All files will be dynamically allocated. | ||||||
| ESY3005E - NO STORAGE FOR WORKAREA - GETVIS ERROR | Storage for an internal work area could not be obtained. | Check partition size. | ||||||
| ESY3006E - NO STORAGE FOR LIBRARY WORKAREA - GETVIS ERROR | Storage for an internal control block related to Librarian access could not be obtained | Check partition size. | ||||||
| ESY3007E - UNEXPECTED RETURN CODE FROM NATPLIBR | Return code from Entire System Server's Librarian interface was not recognized. | Contact Customer support. A PDUMP will be written to SYSLST. | ||||||
| ESY3008E - UNABLE TO LOCK FILETABLE | Entire System Server was unable to obtain the lock so the internal label management table could be updated. | This generally will occur due to a prior abend of a user task. Check for other messages. Contact Customer support if necessary. | ||||||
| ESY3011E - INCORE FILETABLE FULL (XXXX ENTRIES) | Internal label management table was filled during initialization. No more new files can be accessed. | Increase NUMLIBS parameter and restart Entire System Server. | ||||||
| ESY3012E- LABEL WORKTABLE FULL (XXXX ENTRIES) | Internal label management table is full. No more new files can be accessed. | Increase NUMLIBS parameter and restart Entire System Server. | ||||||
| ESY3013E - LABEL PROCESSING ERROR - RETURN CODE=XXX | The LABEL macro returned an unknown return code. It is followed by message ESY3014E. | Contact Customer support. | ||||||
| ESY3014E - REASON CODE=XXXX | The reason code for the preceding ESY3013E message. | Contact Customer support. | ||||||
| ESY3020E - INITIALIZATION STARTED FOR FILEID TABLE | This message appears during initialization, and indicates that Entire System Server's internal label management table is being built. |
No action required. Note |
||||||
| ESY3022E - FILEID TABLE INITIALIZED (XXXX FREE ENTRIES) | This message appears after internal label management table initialization is complete. | No action required. If the number of free entries approaches 0, then the number should be increased. |
||||||
| ESY3053E - NATNUMSUB too high - reduce | The value for NATNUMSUB is too large, not providing enough subtasks for user tasks. | Reduce NATNUMSUB. | ||||||
| ESY4001I - Operator typed in: :1:. | Message confirming operator input. | No action required. | ||||||
| ESY4004E - No option specified. | ESY utilities are argument driven. The parameter handler has not found any program arguments or options. The utility will stop immediately. | Provide arguments to the program to make it work. | ||||||
| ESY4005E - Text for DATA-ID exceed OUTPUT. | In ESYTRACE only: DATA-ID (hard coded text string) does not fit into output area. ESYTRACE terminates abnormally. | Please contact Software GmbH. | ||||||
| ESY4006E - NAME/TOKEN retrieve failed, RC=:1:. | ESYTRACE was unable to retrieve the required NAME/TOKEN pair. See RC for more details. | Contact our support. | ||||||
| ESY4007E - Bad argument value for :1:. | The specified value is invalid (e. g. NODE not numeric). | Correct argument value. | ||||||
| ESY4008E - No output target specified. | In ESYTRACE only: Option '--NTROUT' has been specified to disable output to file. Option '--DISPL' has not been specified. ESYTRACE cannot create output data at all and terminates immediately. At least one output target has to be defined to run ESYTRACE correctly. | Add option value. | ||||||
| ESY4009E - Invalid option specified. | ESY utilities are argument driven. The parameter handler has detected an invalid option which cannot be processed. The utility will stop immediately. | Correct option value. | ||||||
| ESY4012E - NPRSTUB2 not valid. | ESYTRACE was unable to find the required stub module or the node-specific data entry. | Check whether the correct node number has been specified, if the Entire System Server with the requested node ID has been started and is running with activated trace. | ||||||
| ESY4018E - Version mismatch - file is Vnnn, program is Vnnn. | During initialization of ESYTRACE, the program discovered that either the input file or the monitor mode target node was at a different level. | Verify that ESYTRACE is being executed from the same library as the target Entire System Server node. |
