TME 10 Operations Planning and Control IBM Messages and Codes Version 2 Release 2 SH19-4480-01
TME 10 Operations Planning and Control IBM Messages and Codes Version 2 Release 2 SH19-4480-01
Note Before using this information and the product it supports, be sure to read the general information under “Notices” on page v. ISO 9001 Certification This product was developed using an ISO 9001 certified quality system. Certification has been awarded by the Italian quality system certification group, CSQ (Certification No. CISQ/CSQ 9150.IBM7).
Contents Notices . Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface . . . . . . . . . . . . How This Book Is Organized TME 10 OPC Publications . TME 10 OPC Online Books Online Message Facility . Books About Related Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 18. EQQOnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 229 Chapter 19. EQQPnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 231 Chapter 20. EQQQnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 235 Chapter 21. EQQRMnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 243 Chapter 22. EQQRnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 249 Chapter 23. EQQSUnn Messages . . . . . . . . . . . . . . . . . . . . . . . .
Notices References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM’s product, program, or service may be used.
Trademarks The following terms are trademarks of Tivoli Systems or IBM Corporation in the United States or other countries or both: ACF/VTAM AS/400 DATABASE 2 DFSMShsm GDDM IBM LoadLeveler MVS/SP OPC OS/390 PS/2 RS/6000 System/390 TME VTAM AIX BookManager DB2 DFSORT Hiperbatch IBMLink MVS/DFP MVS/XA Operating System/2 OS/400 RACF SAA Systems Application Architecture TME 10 Workplace Shell AIX/6000 CICS DFSMS/MVS Extended Services for OS/2 Hiperspace IMS MVS/ESA NetView OS/2 Personal System/2 RISC System/6
Preface This book describes messages issued by TME 10 Operations Planning and Control (TME 10 OPC), program number 5697-OPC.
TME 10 OPC Publications This book is part of an extensive TME 10 OPC library.
TME 10 OPC Online Books All the books in the TME 10 OPC library, except the licensed publications, are available in displayable softcopy form on CD-ROM in the following Softcopy Collection Kits: | | MVS, SK2T-0710 OS/390, SK2T-6700 TME 10 OPC Messages and Codes is also available as part of Online Library Productivity Edition Messages and Codes Collection, SK2T-2068.
Short Title Publication Order Number MVS/ESA Codes MVS/ESA System Codes GC28-1664 MVS/ESA SP5 System Codes GC28-1486 MVS/ESA System Messages, Volume 1 (ABA-ASA) GC28-1656 MVS/ESA System Messages, Volume 2 (ASB-ERB) GC28-1657 MVS/ESA System Messages, Volume 3 (GFSA-IEB) GC28-1658 MVS/ESA System Messages, Volume 4 (IEC-IFD) GC28-1659 MVS/ESA System Messages, Volume 5 (IGD-IZP) GC28-1660 MVS/ESA SP5 System Messages, Volume 1 (ABA-ASA) GC28-1480 MVS/ESA SP5 System Messages, Volume 2 (ASB-ERB
Summary of TME 10 OPC Version 2 Release 2 Enhancements | | | | | | | | | | | | | Instrumentation for TME 10 Global Enterprise Manager TME 10 Global Enterprise Manager (GEM) is the industry's first solution for unifying the management of cross-platform business applications that run businesses and make them competitive. TME 10 GEM helps you to manage strategic applications from a unique business systems perspective, focusing your IT resources on keeping these systems working properly and productively.
| | Windows NT HP–UX | | | | | | TCP/IP communication improvements The TCP/IP communication component that enables the controller to communicate with the TCP/IP connected tracker agents has been restructured to use the standard TCP/IP C–Socket interface. This change enables TME 10 OPC for the latest OS/390 releases and provides for the use of the standard TCP/IP features, such as the KEEPALIVE option.
| | | | | | | | OPC Control Language tool The OPC Control Language (OCL) tool enables you to access and manipulate TME 10 OPC data by using a REXX-like language. Several macro-functions are made available that perform, in a single action, what would require several invocations of the OPC Program Interface functions. The OCL tool acts as an extension to the REXX language processor. Therefore, normal REXX statements can be coded together with OCL statements. This tool runs in a batch TSO session.
| | | | | | | | | | HB JCLDBG QUELEN STATIM STATUS WSASTA | | | Issues a heartbeat message for an OPC controller or for all trackers connected to that controller Activates or deactivates the JCL debugging trace Sets a new value for the QUEUELEN keyword of the JTOPTS statement Sets a new value for the STATIM keyword of the JTOPTS statement Returns status information about the OPC controller and the tracker agents connected to it.
Tracker agents New Tracker Agents are provided to control the workload on: | Digital OpenVMS Pyramid MIPS ABI Shared parm library in Sysplex environment MVS controllers and trackers can share common controller and tracker initialization statements and started task JCLs, making it easier to install many OPC subsystems inside an MVS/ESA sysplex environment.
Batch command interface tool A batch command interface tool is supplied to perform most of the actions supported by the PIF interface by means of a batch command interface. New and changed initialization statements Initialization statements have been added and changed in TME 10 OPC Version 2. The following sections summarize the differences.
The MODIFY command has been extended to accept stop and start of the server started tasks: F ssname, P=SERV S ssname, P=SERV Changes to programming interfaces The Programming Interface is extended as follows: UPDATE is supported for calendars, periods, workstations, and all workstations closed. BROWSE and UPDATE are supported for ETT and special resources.
xviii TME 10 OPC Messages and Codes
Chapter 1. Introduction This manual explains all the error, warning, and information messages, as well as the user abend codes and reason codes, that TME 10 OPC issues. The messages are listed in alphanumeric order by message identifier. To help you find messages, the range of messages on a particular page is shown at the top of the page.
Introduction The format of a TME 10 OPC message printed in the message log dataset is: mm/dd HH.MM.SS msgnum TEXT where: mm/dd Is the current date, given as a 2-digit month number and a 2-digit day-of-month number. For example, 02/03 means February 3. HH.MM.SS Is the current time-of-day: HH Is the hour, starting from midnight, in the range 00–23. MM Is the minute of the current hour, in the range 00–59. SS Is the second of the current minute, in the range 00–59.
EQQAT00I EQQAT05I Chapter 2. EQQATnn Messages EQQAT00I THE APPC TRACKER TASK HAS STARTED Explanation: The APPC tracker task has started successfully. TME 10 OPC will start this task if the ROUTOPTS initialization statement defines one or more APPC destinations. System action: TME 10 OPC normal processing continues. System programmer response: None. EQQAT01I THE APPC TRACKER TASK HAS ENDED Explanation: The APPC tracker task has been requested to stop and is ending normally.
EQQAT06E EQQAT11E EQQAT06E THE APPC TRACKER TASK RECEIVED UNRECOGNIZED DATA FROM DESTINATION: LU Explanation: Data received from a partner APPC program is not valid. System action: The APPC tracker task will free all resources allocated to this APPC conversation. The partner program sending incorrect data will get a failing return code from the APPC service routine.
EQQAT12E EQQAT21E EQQAT12E RECEIVE AND WAIT FROM DESTINATION: LU FAILED WITH RETCODE RC IMMEDIATELY Explanation: The APPC tracker task received an immediate nonzero return code from the APPC receive and wait service routine. System action: The APPC tracker task will terminate this APPC conversation and free all allocated resources. System programmer response: Verify that the partner program on the remote destination is at a supported maintenance level.
EQQAT22E EQQAT30E EQQAT22E THE PERIOD IN THE ADDR VALUE, VALUE, IS INCORRECTLY PLACED Explanation: The ADDR keyword of the APPCROUT initialization statement must specify a value containing one period, and that period cannot be placed more than eight characters after the beginning of the value or more than eight characters before the end of the value. System action: Processing of the current APPCROUT statement terminates with a nonzero return code. This will cause TME 10 OPC initialization to fail.
EQQAT31E EQQAT34E EQQAT31E APPC KEYWORD VALUE, VAL2, MUST CONTAIN EXACTLY ONE PERIOD Explanation: A network address specified as a value of the APPC keyword of the ROUTOPTS statement is incorrect. The network address is required and must be specified as netid.netlu where the netid and netlu names cannot contain periods. System action: Processing of the APPC keyword continues. Message EQQAT34E will be issued when all destinations have been processed.
8 TME 10 OPC Messages and Codes
EQQA000E EQQA009I Chapter 3. EQQAnnn Messages EQQA000E YOU ARE NOT AUTHORIZED TO ACCESS THE AD DATABASE Explanation: You have attempted to access the application description (AD) database, but you are not authorized to access it. Or, you do not have access authority to at least one of the following TME 10 OPC resources that are used together with the AD database: the calendar database, the workstation description database, or in some cases, the long-term plan dataset.
EQQA010E EQQA017E EQQA010E INVALID PARAMETER INPUT TO MODULE MOD Explanation: This message indicates a programming error. System action: The system waits for you to respond. User response: Contact your system programmer. System programmer response: Contact your IBM representative. EQQA011I THE APPLICATION IS CREATED Explanation: The application has been created and saved in the application description database. System action: None. User response: None.
EQQA018E EQQA103E EQQA018E OP OP HAS AN EXTERNAL PRED WS EWS, WHICH IS NOT FOUND Explanation: Operation op has an external predecessor workstation (ews) that does not exist in the workstation description database. System action: The system waits for you to respond. User response: Enter correct data. EQQA021I NO SPECIAL RESOURCES FOUND FOR THIS OPERATION Explanation: You have attempted to display the special resources of an operation for which no special resources have been defined. System action: None.
EQQA104E EQQA116E EQQA104E THE PERIOD NAME DOES NOT EXIST IN THE CALENDAR Explanation: The period name you specified is not defined in the calendar database. System action: The system waits for you to respond. User response: Enter an existing period name, or use the Calendar dialog to define the period name. EQQA105E YOU ARE NOT AUTHORIZED TO READ THE JCL VARIABLE TABLE DATA BASE Explanation: You have attempted to refer to a JCL variable table.
EQQA117E EQQA124I EQQA117E 24.00 IS NOT ALLOWED AS INPUT ARRIVAL TIME Explanation: Data entry error; see “Data Entry Errors” on page 2. Valid input arrival times are 00.00 through 23.59. EQQA118E 00.00 IS NOT ALLOWED AS DEADLINE TIME Explanation: Data entry error; see “Data Entry Errors” on page 2. Valid deadline times are 00.01 through 24.00.
EQQA125I EQQA202E EQQA125I NO APPLICATION INPUT ARRIVAL TIME SPECIFIED YET Explanation: No application input arrival time is specified for this application. This does not prevent you from saving the application description as it is. System action: The times specified for the operation are accepted. The system waits for you to respond. User response: Enter END to save the application description, or make the deadline times consistent.
EQQA203E EQQA210E EQQA203E THE FREE DAY RULE SPECIFICATION IS INVALID Explanation: Data entry error; see “Data Entry Errors” on page 2. A valid free day rule specification is any of the following: E 1 2 3 4 Free days excluded. Run on the closest workday before the free day. Run on the closest workday after the free day. Run on the free day. Do not run at all. EQQA204E YOU HAVE ENTERED AN INVALID VALUE IN THE CATALOG MANAGEMENT FIELD.
EQQA211E EQQA223E EQQA211E THE PRINT OPTION CHARACTER IS INVALID Explanation: Data entry error; see “Data Entry Errors” on page 2. Valid print option characters are A for always, and C for conditionally. EQQA212E WHEN TIME DEPENDENT = YES, SUPPRESS IF LATE MUST BE SPECIFIED Explanation: Data entry error; see “Data Entry Errors” on page 2. The SUPPRESS IF LATE option must be specified when the TIME DEPENDENT option is specified as YES.
EQQA226E EQQA238E EQQA226E THE OPERATION NUMBER MUST BE SPECIFIED Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQA228E THE SPECIFIED SPECIAL RESOURCE HELD OPTION IS INVALID Explanation: Data entry error; see “Data Entry Errors” on page 2. Valid special resource held options are S for shared, and X for exclusive.
EQQA239E EQQA247E EQQA239E ENTER THE STATUS, A OR P Explanation: Data entry error; see “Data Entry Errors” on page 2. A stands for active, P for pending. EQQA240E SPECIFY A VALID-FROM DATE Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA248E EQQA254E EQQA248E THE PREDECESSOR TABLE CONTAINS DUPLICATE PREDECESSORS Explanation: The list of predecessors cannot contain duplicate predecessors. System action: The system waits for you to respond. User response: Use the row command D to delete the duplicate predecessors, or change the duplicates. EQQA249E THE SPECIAL RESOURCE TABLE CONTAINS DUPLICATE RESOURCES Explanation: The list of special resources cannot contain duplicate resources. System action: The system waits for you to respond.
EQQA255E EQQA265E EQQA255E JOB SETUP OP OP MUST HAVE THE SAME JOBNAME AS A CPU SUCCESSOR Explanation: The job setup operation number (op) must have the same job name as any of its CPU successors. System action: The system waits for you to respond. User response: Enter a valid CPU successor job name. EQQA256E PRINT OP OP MUST HAVE THE SAME JOBNAME AS THE CPU PREDECESSOR Explanation: The print operation number (op) must have the same job name as its CPU predecessor.
EQQA266E EQQA278E EQQA266E YOU ARE NOT AUTHORIZED TO READ THE OI DATA BASE Explanation: You have attempted to read the operator instruction database, but you are not authorized to read it. System action: The system waits for you to respond. User response: Contact your security administrator if you require access to the OI database.
EQQA279E EQQA286E EQQA279E THE TABLE OF UPDATES CONTAINS DUPLICATE UPDATES Explanation: The table of pending updates cannot contain duplicate updates. System action: The system waits for you to respond. User response: Use the row command D to delete the duplicate updates, or change the duplicates. EQQA280E THE TABLE CONTAINS DUPLICATE ROWS Explanation: The table cannot contain duplicate rows. System action: The system waits for you to respond.
EQQA287E EQQA299I EQQA287E THE CONVERSION NUMBER CNR IS NOT SUPPORTED Explanation: This message indicates a programming error. System action: The system waits for you to respond. User response: Contact your system programmer. System programmer response: Contact your IBM representative. EQQA288E THE RESCALE FACTOR IS NOT SPECIFIED Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA300E EQQA308E | EQQA300E VALID DATA IS A NUMBER 1 - 255 | Explanation: Data entry error; “Data Entry Errors” on page 2. EQQA301E THERE MUST BE AT LEAST ONE OPERATION IN AN APPLICATION Explanation: The application has no operations. You must specify at least one operation. System action: The system waits for you to respond. User response: Specify one or more operations for the application.
EQQA309E EQQA400E EQQA309E PRINT OPERATION OP MUST HAVE A CPU PREDECESSOR Explanation: The print operation (operation number op) must have a CPU predecessor operation. System action: The system waits for you to respond. User response: Enter a CPU operation number as the predecessor number. EQQA310E FIELD FORMAT SPECIFIED AS DBCS BUT INPUT NOT BRACKETED DBCS Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA401E EQQA409I EQQA401E NO MATCHING JOB DESCRIPTION FOUND Explanation: The job that you selected from a list does not have a matching job description. The job may have been deleted or modified after the list of job entries was generated. System action: The request is rejected. User response: Return to the job selection criteria panel and press Enter to generate a fresh list of jobs.
EQQA410E EQQA500E EQQA410E THE JOB DIALOG CANNOT BE USED WHEN DBCS IS DEFINED FOR APPLID Explanation: You have tried to enter the job description dialog but DBCS bracketed input has been defined for application IDs in your installation. The application ID of job descriptions must be the same as the job name. Job names cannot be entered in DBCS bracketed format. System action: The panel is redisplayed with this error message. User response: Use the application description dialog instead.
EQQA501W EQQA507I EQQA501W GROUP DEFINITION APPLGRID COULD NOT BE FOUND IN AD FILE Explanation: The current application description references an application group definition that cannot be found in the AD database. Either you entered the wrong name or the application group has not yet been created or you are not authorized to reference it. If you want to, and if you are authorized, you can save the current application description while it references an application group that does not exist.
EQQA508E EQQA515E EQQA508E RUN CYCLES ARE NOT ALLOWED FOR A JOB DESCRIPTION IN A GROUP Explanation: A job description that references a group definition for run cycle information cannot itself contain run cycles. System action: The system waits for you to respond. User response: Either erase the data in the group definition ID field or delete the run cycles for this job description.
EQQA516E EQQA523E EQQA516E NO RUN CYCLES FOR AN APPLICATION IN A GROUP Explanation: An application that references a group definition for run cycle information cannot itself contain run cycles. System action: The request is rejected. User response: None. EQQA520E THE RULE ON WHICH THE RUN CYCLE IS BASED MUST BE DEFINED Explanation: A rule-based run cycle (type R or E) was inserted or replicated in the run cycle table, but no rule definition was specified. System action: The request is rejected.
EQQC001I EQQC006E Chapter 4. EQQCnnn Messages EQQC001I THE AUTOMATIC RECOVERY SUBTASK HAS STARTED Explanation: The automatic job recovery subtask has been successfully initialized. System action: Automatic job recovery processing is started. User response: None. EQQC002E THE AUTOMATIC RECOVERY INITIALIZATION FAILED Explanation: The automatic job recovery subtask was not initialized because there is an error in the AROPTS initialization statement.
EQQC007E EQQC012W EQQC007E AN ABEND OCCURRED IN THE AUTOMATIC RECOVERY SUBTASK, IT IS RESTARTED Explanation: An error has caused the automatic job recovery subtask to end abnormally, but it has been able to restart. System action: Automatic job recovery resumes normal processing but one or more requests for service may have been rejected. Problem determination: At abend, a dump is written to the SYSxDUMP dataset.
EQQC013W EQQC022I EQQC013W AUTOMATIC RECOVERY REQUEST FAILED, CANNOT ALLOCATE BUFFERS Explanation: A storage allocation error prevented automatic job recovery from checking whether or not recovery should be performed for the job that ended in error. This message may be followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery. System action: No recovery attempt is made and the job remains ended in error.
EQQC023W EQQC027W EQQC023W NO AUTOMATIC RECOVERY TEST BECAUSE NO JCL RECORD FOR THE OPERATION Explanation: The JCL record could not be read. This prevented automatic job recovery from determining whether or not recovery should be performed for the job that ended in error. This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery. System action: No recovery attempt is made and the job remains ended in error.
EQQC028W EQQC045I EQQC028W NO AUTOMATIC RECOVERY TEST BECAUSE ERROR IN RECOVER STATEMENT Explanation: While automatic job recovery was checking whether or not recovery should be performed for a job that ended in error, a RECOVER statement with a syntactical error was found. This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery. System action: No recovery attempt is made and the job remains ended in error.
EQQC046W EQQC047E EQQC046W AUTO RECOVERY WARNING RS, APPL ADID DATE H.M, OP WSN OP JN JID Explanation: Automatic job recovery was attempted for the job identified as application ADID DATE H. M, operation WSN OP, where DATE H. M is the occurrence input arrival time. A problem was encountered that inhibited automatic job recovery. RS is a reason code that stands for a certain error and/or action related to automatic job recovery. Message EQQC047E has a list of the reason codes and their meanings.
EQQC048W EQQC049E 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 50 51 52 Failing operation record could not be read. Invalid stepname or no step with that name. More than one step in JS record with the given name. JS dataset in use. Recovery test canceled. JS dataset member in use. Recovery test canceled. OP record has been changed. Recovery test canceled. Invalid range. No occurrence exists for the specified application. Recovery actions taken. No JS record.
EQQC061E EQQC500E EQQC061E AUTOMATIC RECOVERY FAILED, I/O ERROR Explanation: Automatic job recovery failed for the job that ended in error because an I/O error occurred. The I/O error occurred while the automatic job recovery subtask was determining whether recovery should be performed, or while the recovery actions were being activated or implemented.
EQQC501E EQQC501E EQQC501E LOGICAL RECORD LENGTH FOR THE JCL LIBRARY, DDNAME EQQPRLIB, IS NOT VALID Explanation: Automatic job recovery could not read a procedure specified in the ADDPROC parameter of the RECOVER statement because the logical record length is not 80 bytes. This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery. System action: No recovery attempt is made and the job remains ended in error.
40 TME 10 OPC Messages and Codes
EQQCL00I EQQCL08I | Chapter 5. EQQCLnnn Messages | EQQCL00I Processing: instruction | Explanation: OCL is processing the instruction instruction | System action: Processing continues. | User response: None. | EQQCL02 x instr instruction executed: RC=return_code | Explanation: This message reports the return code (return_code) of the instruction. x can be one of the following: | I | W | E Information (RC=0) Warning (RC=4) Error (RC=8) | System action: Processing continues. | User response: None.
EQQCL09I EQQCL0GI | EQQCL09I The operation was completed: OPNO(opnum) APPL(appl) IA(iadt) | Explanation: OCL completed the operation opnum within the occurrence appl with the input arrival date and time | iadt. | System action: Processing continues. | User response: None. | EQQCL0AI The occurrence was added: APPL(appl) IA(iadt) | Explanation: OCL added a new occurrence in the OPC current plan or long term plan. appl is the occurrence ID | and iadt is the input arrival date and time.
EQQCL0HI EQQCL0OI | EQQCL0HI Occurrence found in LTP: APPL(appl) IA(iadt) | Explanation: OCL found an occurrence in the long term plan that matches | with the specified selection parameters. | System action: Processing continues. | User response: None. | EQQCL0II Date is valid | Explanation: The input date is valid. | System action: OCL calculates about 210 variables, based on the input date. | User response: None.
EQQCL0PI EQQCL0WI | EQQCL0PI cmd command was issued | Explanation: OCL issued command cmd, which can be SRSTAT, OPSTAT, or WSSTAT. | System action: Processing continues. | User response: None. | EQQCL0QI Operation opnum was successfully modified | Explanation: OCL modified the operation opnum. | System action: Processing continues. | User response: None. | EQQCL0RI Deleting the special resource from operation opnum | Explanation: OCL is deleting the special resource definition from operation opnum.
EQQCL0XI EQQCL14I | EQQCL0XI Default operation number is used: defopno | Explanation: OCL will use defopno as the default operation number. | System action: Processing continues. | User response: None. | EQQCL0YI Predecessor added to operation opnum: PREOPNO(preopnum) PREAPPL(preappl) | Explanation: OCL added a new predecessor to operation opnum. preopnum is the predecessor operation, and | preappl is the predecessor application ID. | System action: Processing continues. | User response: None.
EQQCL15I EQQCL1CI | EQQCL15I Internal successor released: OPNO(s_opnum) APPL(appl) | Explanation: OCL released the internal successor operation number s_opnum in the occurrence appl. | System action: Processing continues. | User response: None. | EQQCL16I External successor found for operation opnum: OPNO(s_opnum) APPL(appl) | Explanation: OCL found an external successor for operation opnum. s_opnum is the successor operation number; | appl is the successor occurrence ID.
EQQCL1DI EQQCL44W | EQQCL1DI External predecessor deleted: PREAPPL(preappl) PREIA(iadt) | Explanation: OCL deleted an external predecessor definition. preappl is the predecessor occurrence ID, and iadt its | input arrival date and time. | System action: Processing continues. | User response: None. | EQQCL1EI Special resource found for operation opnum: res_name | Explanation: OCL found a special resource defined to operation opnum. res_name is the name of the special | resource.
EQQCL45W EQQCL4CW | EQQCL45W Occurrence not found in the LTP: APPL(appl) IA(iadt) | Explanation: OCL attempted to modify or list the application occurrence appl, which does not exist in the long term | plan. iadt is the input arrival date and time used to search for the occurrence. | System action: OCL processing continues. | User response: Verify that the selection parameters are correct.
EQQCL4DW EQQCL4JW | EQQCL4DW External predecessor(s) found, status cannot be changed | Explanation: OCL tried to set an operation to Ready status, but external predecessors are defined. OCL will delete | the dependency definitions and will try to set the operation Ready again. | System action: OCL processing continues. | User response: None. | EQQCL4EW Occurrence appl is still in Waiting status | Explanation: OCL tried to force the application occurrence to start, but it is still in Waiting status.
EQQCL4KW EQQCL4RW | EQQCL4KW No external successor found for the occurrence appl | Explanation: OCL tried to release the external successors of the occurrence appl, but no successor was found for | the occurrence. | System action: OCL processing continues. | User response: None. | EQQCL4LW Operation opnum not found: APPL(appl) IA(iadt) | Explanation: OCL tried to change operation opnum that is not present in the current plan. | System action: OCL processing continues.
EQQCL4SW EQQCL51E | EQQCL4SW Operation deadline precedes operation input arrival - accepted: deadline | Explanation: The operation deadline precedes the operation input arrival but is accepted. | System action: OCL processing continues. | User response: Verify that the specified keywords are correct. | EQQCL4TW Operation Input Arrival precedes occurrence - accepted: iadt | Explanation: The operation input arrival precedes the occurrence input arrival but is accepted.
EQQCL52E EQQCL59E | EQQCL52E Not possible to read the SYSIN card | Explanation: OCL was not able to read the SYSIN DD card. | System action: OCL terminates. | User response: Verify the dataset specified in the EQQOCL.SYSIN DD card. | EQQCL53E Invalid syntax: instruction | Explanation: An invalid instruction was specified in the OCL SYSIN. | System action: OCL terminates | User response: Correct the instruction, then resubmit the job.
EQQCL5AE EQQCL5HE | EQQCL5AE Predecessor can't be equal to the operation to be added | Explanation: OCL was requested to add a new operation in an application occurrence, but the operation number is | equal to its internal predecessor operation number. | System action: OCL terminates. | User response: If you have specified the DEFOPNO initialization parameter, OCL will use it as a default | predecessor operation number. You cannot add an operation with a number equal to DEFOPNO.
EQQCL5IE EQQCL5PE | EQQCL5IE APPL and GROUP are mutually exclusive keywords | Explanation: APPL and GROUP keywords were specified in the same ADD instruction. | System action: OCL terminates. | User response: Correct the instruction, then resubmit the job. | EQQCL5JE OPC subsystem id must be supplied | Explanation: The OPC subsystem ID was not specified. | System action: OCL terminates.
EQQCLQE EQQCL5XE | EQQCLQE Workstation wsname not found in the OPC database | Explanation: Workstation wsname is not defined in the OPC Workstation database. | System action: OCL terminates. | User response: Correct the instruction, then resubmit the job. | EQQCL5RE Jobname must be specified for workstation wsname | Explanation: Workstation wsname requires the jobname (job-setup, computer, or printer) | System action: OCL terminates. | User response: Correct the instruction, then resubmit the job.
EQQCL5YE EQQCL65E | EQQCL5YE Not possible to define internal pred. preopnum to operation opnum | Explanation: OCL tried to define an internal predecessor to operation opnum, but a problem occurred. | System action: OCL terminates. | User response: Contact your IBM representative. | EQQCL5ZE Not possible to remove the occurrence from the application group | Explanation: OCL tried to remove an occurrence from the application group before deleting it from the current plan | or from the long term plan.
EQQCL66E EQQCL6DE | EQQCL66E Date not valid: it's not in the YYYYMMDD format | Explanation: The date supplied is not in the YYYYMMDD format. | System action: OCL terminates. | User response: Correct the date, then resubmit the job. | EQQCL67E Year year must be included between 1996 and 2999 | Explanation: The date specified in the CHKDATE instruction is outside the valid range 1996–2999. | System action: OCL terminates. | User response: Correct the date, then resubmit the job.
EQQCL6EE EQQCL6LE | EQQCL6EE Not possible to issue the WTO | Explanation: OCL tried to invoke the IPOWTO program, but a problem occurred. | System action: OCL terminates. | User response: Make sure that the IPOWTO program is available to OCL, then resumbit the job. | EQQCL6FE Invalid cmd command | Explanation: cmd can be only SRSTAT, OPSTAT, or WSSTAT. | System action: OCL terminates. | User response: Correct the instruction, then resubmit the job.
EQQCL6ME EQQCL6SE | EQQCL6ME Specify the OPNO() keyword or specify the default operation number | Explanation: The OPNO keyword is not specified. OCL tried to use the default operation number, which is not | specified in the initialization parameter DEFOPNO. | System action: OCL terminates. | User response: Specify the OPNO keyword or the default operation number in the initialization parameter | DEFOPNO.
EQQCL6TE EQQCL70E | EQQCL6TE Can't have a dependency on itself: PREAPPL(p_appl) PREIA(iadt) | Explanation: In the long term plan, an occurrence cannot have a predecessor with the same occurrence ID and | input arrival date and time. | System action: OCL terminates. | User response: Correct the instruction, then resubmit the job.
EQQCL71E EQQCL78E | EQQCL71E OPNO() and EXCLOP() are mutually exclusive keywords | Explanation: OPNO and EXCLOP are mutually exclusive keywords. | System action: OCL terminates. | User response: Correct the instruction, then resubmit the job. | EQQCL72E Can't release the successor of operation opnum: APPL(s_appl) OPNO(s_opnum) | Explanation: OCL tried to release an external successor of operation opnum, but a problem occurred. | System action: OCL terminates.
EQQCL79E EQQCL7GE | EQQCL79E Can't delete the special resource: res_name OPNO(opnum) | Explanation: OCL tried to delete the special resource res_name from the operation opnum. | System action: OCL terminates. | User response: Contact your IBM representative. | EQQCL7AE Occurrence ID must be supplied | Explanation: APPL is a required keyword. | System action: OCL terminates. | User response: Correct the instruction, then resubmit the job.
EQQCL7HE EQQCL7KE | EQQCL7HE Not possible to write the message on dataset: dsname(WTOIN) | Explanation: OCL tried to the message text of the WTOR in the member WTOIN of dataset dsname. | System action: OCL terminates. | User response: Contact your IBM representative. | EQQCL7IE Invalid parameter: parameter | Explanation: An invalid parameter was specified in the MODOP instruction. | System action: OCL terminates. | User response: Correct the instruction, then resubmit the job.
64 TME 10 OPC Messages and Codes
EQQD001E EQQD011E Chapter 6. EQQDnnn Messages EQQD001E INVALID VALUE SPECIFIED FOR REPORT SELECTION Explanation: Data entry error; see “Data Entry Errors” on page 2. If you want a report, you must specify a Y; if you do not want a report, you must specify an N. EQQD002E START AND END DATES MUST NOT BE THE SAME Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQD012E EQQD020E EQQD012E END DATE OR EXTENSION LENGTH MUST BE FILLED IN Explanation: Data entry error; see “Data Entry Errors” on page 2. To extend a plan period, you must specify either an end date and time or an extension length. EQQD013E A START DATE MUST BE SPECIFIED Explanation: Data entry error; see “Data Entry Errors” on page 2. You must specify a start date because no current plan exists.
EQQD100E EQQD105E EQQD100E CATALOG MANAGEMENT TASK HAS IGNORED AN INVALID QUEUE ELEMENT: DQE Explanation: A queue element did not contain the correct eye catcher or version number. System action: The catalog management task does not process the invalid element, but continues normal processing. User response: Contact your system programmer. System programmer response: Save the OPC/ESA message log containing this message, then contact your IBM representative.
EQQD107E EQQD112I EQQD107E OPC/ESA IS NOT AUTHORIZED TO DELETE DATASET DSNAME IN CATALOG CAT. Explanation: An attempt was made to scratch this dataset, but OPC/ESA is not authorized to do so. System action: OPC/ESA will set error status for the catalog management action of this dataset. Also, the catalog management status for this operation will be set to error. User response: Contact your systems programmer.
EQQD114E EQQD119I EQQD114E OPC/ESA COULD NOT DELETE MIGRATED DATASET DSN. APPLICATION IS AD, INPUT ARRIVAL IS IA, OPERATION NUMBER IS OPNO, AND JOBNAME IS JNM. Explanation: When OPC/ESA tried to locate the dataset, it resided on logical volume MIGRAT. OPC/ESA has tried to recall the dataset and waited the time given in the CHSMWAIT keyword. As the dataset has not been recalled within the time given, the catalog management status for the dataset and the operation will be set to error.
EQQD120I EQQD126I EQQD120I OPC HAS PROCESSED KEYWORD CATACT IN THE OPCOPTS STATEMENT. THE KEYWORD IS IGNORED, BECAUSE OPC HAS BEEN DEFINED AS A TRACKER SYSTEM. Explanation: The CATACT keyword is a controller keyword. When you define it for a tracker system it is ignored. System action: The keyword is ignored. System programmer response: If you do not want this message to be issued, remove the keyword from the OPCOPTS statement and restart the system.
EQQD128I EQQD132E EQQD128I THE CATALOG MANAGEMENT EXIT LOAD MODULE MODULE COULD NOT BE LOADED. Explanation: The catalog management subtask could not load the EQQUX008 exit. System action: The catalog management exit will not be used. User response: Contact your system programmer. System programmer response: If the exit should be called by OPC/ESA, make sure that the exit load module is stored in a library that can be reached by OPC/ESA.
EQQD133I EQQD135E EQQD133I THE JOBLOG FOR JNM JID FOR OPERATION OPN IN APPLICATION APPL WITH IA IA SCHEDULED ON WORKSTATION WSNAME DOES NOT CONTAIN ALL DATASETS REQUIRED BY THE OPC/ESA CATALOG MANAGEMENT FUNCTION Explanation: A joblog-retrieval request has been issued to a tracker where DELAYEDSYSOUT or DELAYED is specified for JOBLOGRETRIEVAL. The Catalog Management task has determined that the joblog for the current job does not contain all joblog datasets required by TME 10 OPC.
EQQD136E EQQD139E EQQD136E CM ALLOCATION OF A SYSOUT DATA SET FAILED FOR JNM(JID) IN APPLICATION ADID. DYNAMIC ALLOCATION ERROR CODE: RETC, INFORMATION REASON CODE: RSNC Explanation: A joblog-retrieval request has been issued to a tracker where DELAYEDSYSOUT or DELAYED is specified for JOBLOGRETRIEVAL. The Catalog Management task could not allocate a SYSOUT dataset for the job JOBNAME(JOBNUM). The dynamic allocation error and information reason codes are given in hexadecimal.
EQQD140E EQQD144I EQQD140E THE JOBLOG RETURNED BY EXITNAME FOR JOBNAME JOBNUM IN APPLICATION APPL IS INCOMPLETE. FOLLOWING DATA NOT FOUND: DDNAME1, DDNAME2 Explanation: A joblog-retrieval request has been issued to a tracker where DELAYEDEXIT or DELAYED is specified for JOBLOGRETRIEVAL. The Catalog Management makes a basic validity check of what is passed back from the joblog-retrieval exit.
EQQD145E EQQD147E EQQD145E OBJECT OBJ COULD NOT BE CREATED. REASON FOLLOWS: Explanation: The initialization program tried to create a table, index or an alias in the history database but failed. The reason is described in message EQQD142, which follows this message. System action: Processing is terminated. User response: Contact your system programmer. System programmer response: Check message EQQD142.
76 TME 10 OPC Messages and Codes
EQQEX01I EQQEX05E Chapter 7. EQQEXnn Messages EQQEX01I THE EXTERNAL ROUTER TASK HAS BEEN STARTED Explanation: The external router task has successfully completed initialization. The external router task handles the interface to the operation-initiation exit, EQQUX009, which is used to start operations at user-defined destinations. System action: The external router task processing continues. User response: None.
EQQEX06E EQQEX08E EQQEX06E A SEVERE ERROR IN THE EXTERNAL ROUTER TASK HAS CAUSED ONE OR MORE REQUESTS TO BE LOST Explanation: The external router task encountered an error processing elements on the EXAQ. As a result, at least one queue element has been lost. System action: MVS/ESA recovery/termination is requested to generate a dump. The external router task attempts to continue normal processing.
EQQE000I EQQE001E Chapter 8.
EQQE002E EQQE003E EQQE002E ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG FIRST OPERATION NOT ON CPU WS, JOBNAME CANNOT BE REPLACED Explanation: ETT was triggered by an event but could not add the associated application since the first operation (ie the operation with the lowest operation number) was not a CPU-operation and ETT's Job Name Replace option was specified. System action: The associated application was not added by ETT, but ETT processing continues normally.
EQQE004I EQQE005I EQQE004I CP ENQ LOCK STATISTICS SINCE PREVIOUS MESSAGE FOLLOW: NAME NEXCL NSHRD THELD TWAIT AHELD AWAIT | Explanation: This message is issued if the CP ENQ LOCK statistics are active. This can be done either by | specifying the STATMSG(CPLOCK) keyword in the JTOPTS initialization statement, or by using the modify command, | /F subsys,CPQSTA=ON. | Once activated, this messages is regularly issued by the event manager subtask, until it is deactivated.
EQQE006I EQQE007I EQQE006I EVENT MANAGER EVENT TYPE STATISTICS FOLLOW: TYPE NTOT NNEW TTOT TNEW TAVG NAVG NSUS | Explanation: This message is issued if the EVENTS statistics are active. This can be done either by specifying the | STATMSG(EVENTS) keyword in the JTOPTS initialization statement, or by using the modify command, /F | subsys,EVESTA=ON. | Once activated, this messages is regularly issued by the event manager subtask, until it is deactivated.
EQQE008I EQQE008I | EQQE008I READY OPERATIONS QUEUE LENGTH STATISTICS FOLLOW: | Q10 Q100 Q1000 Q5000 Q10000 >10000 | R1 R2 R3 R4 R5 R6 | OPERATIONS READY AND FOUND WAITING FOR SPECIAL RESOURCES: | Q10 Q100 Q1000 Q5000 Q10000 >10000 | S1 S2 S3 S4 S5 S6 | OPERATIONS READY TO SELECT A WINNER: | Q10 Q100 Q1000 Q5000 Q10000 >10000 | Q1 Q2 Q3 Q4 Q5 Q6 | Explanation: This message is issued if the WSA statistics are active.
EQQE009I EQQE012E | EQQE009I READY QUEUE LAST VALUE V1 | NEW READY OPERATIONS V2 | NEW STARTED OPERATIONS V3 | NEW COMPLETED OPERATIONS V4 | SELECT WINNER CALLS V5 | ACCESS JS CALLS V6 | ACCESS JOBLIB CALLS V7 | USER EXIT 001 CALLS V8 | USER EXIT 002 CALLS V9 | Explanation: This message is issued together with message EQQE008I. See the explanation for EQQE008I for | details about when it is used.
EQQE013E EQQE018I EQQE013E ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG ERROR DETECTED BY MODIFY CURRENT PLAN INTERFACE Explanation: TME 10 OPC was unable to add the application because the modify current plan interface detected an error. System action: The associated application was not added by ETT, but ETT processing continues normally. Problem determination: Check the TME 10 OPC message log data for EQQMxxx messages (that is, the MCP messages) preceding this message.
EQQE019I EQQE025I EQQE019I JOBNAME(JOBNUM) WAS NOT SUBMITTED BY OPC/ESA AND TRACK(OPCASUB) OR TRACK(JOBOPT) IS ACTIVE, BUT THE JOB WILL BE TRACKED ANYWAY BECAUSE IT BELONGS TO AN APPLICATION THAT WAS ADDED BY ETT Explanation: ETT has a job on its list of jobs to be tracked, but the specified job has not been submitted by TME 10 OPC. System action: TME 10 OPC will track the job because it belongs to an application that was added by ETT. User response: None.
EQQE026I EQQE036I EQQE026I APPLICATION APPL ENDED IN ERROR EC. OPER = OPERNUM, PRTY = PRI, IA = IA Explanation: This message is issued when an operation on a general type work station has ended in error and the ALERTS initialization statement specifies TYPE(ERROROPER). System action: Normal TME 10 OPC processing continues. User response: Perform error recovery actions for the operation specified.
EQQE037I EQQE042I EQQE037I JOB JOBNAME(JNUM), IN APPLICATION APPL, IS LATE, WORK STATION = WSID, IA = ARRTIME Explanation: This message is issued when a job has reached its latest start time but has not yet started. System action: Normal TME 10 OPC processing continues. User response: Investigate what is keeping the job from starting and take appropriate actions to enable it to start.
EQQE043W EQQE045E EQQE043W JOB START OR JOB END EVENT RECEIVED FOR JOBNAME(JOBNUM) IS NOT CONSISTENT WITH CURRENT OPC/ESA STATUS OF THIS JOB Explanation: The Event Manager has received an event for a job on an automatically reporting computer workstation that conflicts with the information already collected for this operation. For example, a job complete event can only occur for a job that has started to execute. System action: The status of the operation is not changed.
EQQE046W EQQE049W EQQE046W THE EVENT MANAGER WAS UNABLE TO RELEASE JOBNAME(JOBNUM) FROM HOLD Explanation: The Event Manager was unable to communicate successfully with JES while trying to release a job from hold. System action: The hold status of the current job is not changed. The Event Manager continues normal operation with the next queued event. System programmer response: Check that JES is executing normally. Operator response: Check that the job is still held by JES.
EQQE055W EQQE058W EQQE055W THE EVENT MANAGER HAS IGNORED THE FOLLOWING SUBMIT EVENT RECORD BECAUSE NO MATCHING OPERATION WAS FOUND IN THE CURRENT PLAN: EXITREC Explanation: The Event Manager’s work queue contains an incorrect submit event. No operation in the current plan dataset matches the operation defined by the event record. This submit event record is created for work being scheduled on one of the systems in this Controller's OPC configuration by another Controller having the same name.
EQQE059W EQQE066E EQQE059W THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE WORK STATION WSNAME IS NOT AN AUTOMATICALLY REPORTING WORK STATION: EXITREC Explanation: An invalid user-defined event record has been found on the Event Manager’s work queue. Workstations referenced by user-defined event records must be automatically reporting workstations. The current workstation does not have this attribute.
EQQE067E EQQE071E EQQE067E A SUBSYSTEM REQUEST ERROR (R15 = R15) OCCURRED. NO EVENT IS CREATED Explanation: An error occurred when attempting to send an event to an TME 10 OPC subsystem. System action: The event will not be created. The EQQEVPGM program continues processing the next event creation statement. User response: If R15 is 4 then the SUBSYS keyword does not define an TME 10 OPC system.
EQQE072E EQQE075E EQQE072E YOU ARE NOT AUTHORIZED TO UPDATE SPECIAL RESOURCES FOR SUBSYSTEM SUBSYS Explanation: In order to change a special resource for an TME 10 OPC subsystem, update authority to the SR resource is necessary. You do not have this authority. System action: If you specified SUBSYSTEM(MSTR) in the command, no event is created for this subsystem. However, EQQEVPGM tries to create an event for the next active TME 10 OPC subsystem in this MVS system.
EQQE076E EQQE080E EQQE076E THE INPUT ARRIVAL TIME SPECIFIED BY THE IA KEYWORD IS NOT VALID Explanation: The IA keyword contains an invalid input arrival value. The value must be specified in the format YYMMDDHHMM where: YYMMDD HHMM Is the input arrival date: YY Is year and must specified as 72 to 99 for years 1972 to 1999 or 00 to 71 for years 2000 to 2071. MM Is the month number and must be in the range 01 to 12. DD Is the day number and must be in the range 01 to 31.
EQQE081E EQQE086E EQQE081E R15 RETURN CODE R15 WAS RETURNED BY THE TSO SERVICE FACILITY. RETURN CODE RC, REASON CODE RSN WERE ALSO RETURNED Explanation: This message is issued when an TME 10 OPC TSO command has failed due to an error when communicating with the TME 10 OPC subsystem. System action: The TME 10 OPC service requested has not been executed. User response: Contact your systems programmer. System programmer response: If the failing command contains an error, correct it and retry.
EQQE087E EQQE091E EQQE087E YOU ARE NOT AUTHORIZED TO REQUEST A BACKUP OF THE RESDS RESOURCE DATASET SPECIFIED FOR SUBSYSTEM SUBSYS Explanation: In order to request a backup of an TME 10 OPC resource dataset, update authority to the BKP fixed resource is required. You do not have this authority. System action: The request is ignored. User response: If authority is required contact your security administrator.
EQQE092E EQQE096E EQQE092E THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE CURRENT OPERATION STATUS IS NOT STARTED: EXITREC Explanation: An invalid user-defined event record has been found on the Event Manager's work queue. An OPSTAT event definition statement specified a new status of SQ or SS, but the current operation status is not started (S). System action: The incorrect event record is returned to the Event Manager's free queue without any further processing.
EQQE097E EQQE101E EQQE097E THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE SPECIFIED TOKEN VALUE DOES NOT MATCH ANY OPERATION IN THE CURRENT PLAN: EXITREC Explanation: An invalid user-defined event record has been found on the Event Manager's work queue. An OPSTAT event definition statement defined a TOKEN value that does not match any operation in the current plan. The operation cannot be identified by OPC/ESA.
EQQE102W EQQE104E EQQE102W PULSE LOST FROM TRACKER SUBS AT DESTINATION DEST Explanation: This message indicates that handshake processing, the frequency for which is determined by the PULSE keyword of the ROUTOPTS statement, has terminated for the indicated Tracker system. When handshake processing is in use, each connected Tracker system sends an identification (ID) event to the controller at the specified interval.
EQQF000E EQQF004E Chapter 9. EQQFnnn Messages EQQF000E DATA ROUTER TASK HAS IGNORED AN INVALID QUEUE ELEMENT: DQE Explanation: A queue element did not contain the correct eye catcher or version number. System action: The data router task does not process the invalid element, but continues normal processing. User response: Contact your system programmer. System programmer response: Save the TME 10 OPC message log and contact your IBM representative.
EQQF005E EQQF008I EQQF005E DATA ROUTER TASK QUEUE POINTERS ARE DESTROYED, RTRQ IS LOST Explanation: The data router task abended while processing elements on RTRQ because the queue chaining is invalid. System action: MVS recovery/termination is requested to generate a dump. All elements on RTRQ are skipped, but the data router task attempts to continue normal processing.
EQQF009I EQQF012I EQQF009I ADAPTIVE PACING ON EVENT INFLOW MODE Explanation: The MODE can be ACTIVATED or DEACTIVATED. ACTIVATED The data router has detected that the maximum number of queue elements on the event manager queue (MGRQ) were already in use when the data router task attempted to add incoming events to the MGRQ. The data router task has posted each locally attached event reader task and event writer task (when EWSEQNO(n)), to stop reading from the event datasets or adding to the DRTQ.
EQQF013I EQQF015I EQQF013I EXIT EQQUX009 IS NOT LOADED OR HAS BEEN DISABLED Explanation: User exit EQQUX009 has not been loaded, or has abended previously. The operations scheduled to run on a workstation which specifies a user-defined destination will not be routed. System action: The operation status is set according to what is specified in the SUBFAILACTION keyword on the JTOPTS initialization parameter.
EQQG001I EQQG004E Chapter 10. EQQGnnn Messages EQQG001I SUBTASK SUBTASK HAS STARTED Explanation: The subtask SUBTASK has been successfully initialized. System action: Processing for the subtask indicated is started. User response: None. EQQG002E INITIALIZATION OF SUBTASK SUBTASK FAILED. REASON CODE: RS Explanation: The subtask indicated could not acquire all the resources needed for normal operation.
EQQG005E EQQG010I EQQG005E VALIDATION FAILED FOR FILE: FILE, REASON: REASON, OFFSET: POS Explanation: The record that was to be written to the TME 10 OPC database was rejected because it was incorrect. System action: No update to the database is made. Problem determination: FILE gives the database on which the update was attempted; REASON indicates the reason for the failure; and POS indicates the failing position in hexadecimal form within the record.
EQQG010I EQQG010I TOTTIME NEWTIME TOTAVG NEWAVG The The The The total time, in seconds, used to process this request. total time, in seconds, used to process this request since the last message. average time, in seconds, used to process a request of this type. average time, in seconds, used to process a request of this type since the last message.
EQQG011I EQQG013I EQQG011I TYPE NUMRQ NEWRQ TTOT TNEW TAVG NAVG | Explanation: This message is issued if the GENERAL SERVICE task statistics are active. This can be done either | by specifying the STATMSG(GENSERV) keyword in the JTOPTS initialization statement, or with the modify command, | /F subsys,GENSTA=ON. | This message is issued every n minutes if any requests have been processed, where n is the value specified in the | JTOPTS keyword STATIM if it has a nonzero value, or the default of 30.
EQQG014W EQQG107I EQQG014W REQUEST TERMINATED BECAUSE TIME LIMIT IS EXCEEDED Explanation: A general service request has terminated because the requesting process; a PIF program or a dialog user, did not respond within 10 minutes. System action: Processing continues. User response: None.
EQQG109E EQQG109E EQQG109E NET LOADER MODULE COULD NOT BE LOADED Explanation: When requesting a graph, TME 10 OPC could not load the net building routine. System action: The graph request is ignored. Processing continues. User response: Contact your system programmer. System programmer response: Make sure that the ISPLLIB libraries are updated to contain the graph net building routines. The name of the routine can be seen in the ISPF log. See message EQQX009.
EQQH001E EQQH205E Chapter 11. EQQHnnn Messages EQQH001E THE NETVIEW INTERFACE MODULE CNMNETV COULD NOT BE LOADED Explanation: CNMNETV was not found in the library search path. System action: TME 10 OPC continues, but the generic alert functions as requested in the GENALERT keyword of the ALERT initialization statement are disabled. Instead, TME 10 OPC will generate WTO messages for the error conditions specified in the GENALERT keyword.
EQQH206W EQQH214E EQQH206W A MISSING END OF COMMENT IS ASSUMED AT THE END OF THE STATEMENT Explanation: A start of comment delimiter (/*) has been detected, without a corresponding end of comment (*/). System action: TME 10 OPC assumes the comment ends after the control statement. User response: Add an end of comment (*/) and rerun if required. EQQH207W A MISSING END QUOTE IS ASSUMED AT THE END OF THE STATEMENT Explanation: The quote for this character string is not closed.
EQQH215E EQQH222E EQQH215E TOO MANY LEFT PARENTHESES ARE INSERTED IN THE PARMSTRING Explanation: Too many left parentheses are provided. System action: Processing of the statement ends. User response: Remove the extra left parentheses and rerun. EQQH216E A LEFT PARENTHESIS IS MISSING BEFORE H21601 Explanation: A left parenthesis is omitted. System action: Processing of the statement ends. User response: Add the missing left parentheses and rerun.
EQQH223E EQQH306W EQQH223E THE EMPTY QUOTED STRING IS INVALID FOR THE KEYWORD H22301 Explanation: No values for keyword H22301 are specified. System action: Processing of the statement ends. User response: Correct the string and rerun. EQQH224E REQUIRED KEYWORD(S) MISSING IN COMMAND H22401 Explanation: One or more required keywords were not found in the statement H22401. System action: Processing of the statement ends. User response: Correct the statement and rerun.
EQQH308W EQQH502E EQQH308W DUPLICATE VALUE(S) H30801 IGNORED. Explanation: You have specified duplicate values. Only one of the values will be used. System action: Duplicate value removed. User response: Check the specified values, and correct them if necessary. EQQH309E THE SAVED RULE VALUE HAS BEEN DESTROYED, PLEASE REENTER THE INFO Explanation: The rule value saved on the AD data base is not valid can not be used. System action: The rule is invalid and must be reentered before use.
EQQH503E EQQH511E EQQH503E THE USER PERIOD H50301 DOES NOT EXIST Explanation: Invalid user period specified. The name of TME 10 OPC predefined cycles is preceded by two unprintable characters. System action: The rule is invalid and will not be saved. User response: Correct the period specification and rerun. EQQH504E THE CALENDAR H50401 DOES NOT EXIST Explanation: Invalid calendar H50401 specified. System action: The rule is invalid and will not be saved.
EQQH700I EQQH706E EQQH700I HIGHEST RETURN CODE FROM PARSER IS H70001 Explanation: This information message is displayed after parsing a date generating rule. The short message is set to 'VALID RULE' if the parser returns 04 or lower, 'INVALID RULE' for all other return codes. The return code value is shown in H70001. This message is followed by one or more information or warning messages for a valid rule, and by up to 5 error messages for an invalid rule.
EQQH707E EQQH711E EQQH707E THE ENTRY IS INVALID, ENTER A NUMBER IN THE RANGE 0 TO 999 Explanation: You have entered an invalid number in the field, it must be in the range 0 to 999. System action: The request is rejected. User response: Change the number to a valid value. EQQH708E H70801 TOGETHER WITH SPECIFIC H70801 SELECTION(S) IS AMBIGUOUS Explanation: Message variable H70801 is DAY, WEEK or MONTH.
EQQH712E EQQH712E EQQH712E UNABLE TO GENERATE DATES FOR THE INTERVAL IVLFROM IVLTO Explanation: GENDAYS is not able to generate dates for the rule because the entire requested interval is outside the limits of the internal calendar When the interval is calculated: The start date of the interval is the later of the run cycle in-effect date and the AD valid-from date. The end date of the interval is the earlier of the run cycle out-of-effect date and the AD valid-to date.
120 TME 10 OPC Messages and Codes
EQQIC00I EQQIC03E Chapter 12. EQQICnn Messages EQQIC00I FILE FILE HAS BEEN CONVERTED NCOPY RECORDS COPIED, NUPD RECORDS UPDATED, NSKIP RECORDS SKIPPED Explanation: An OPC VSAM file has been successfully built from the corresponding file in a different release of OPC. This message documents the number of records copied without change, the number of modified records, and the number of records in the input file that were not used.
EQQIC04E EQQIC08I EQQIC04E EQQICTOP TERMINATED BECAUSE OF UNRECOVERABLE ERRORS Explanation: A severe error occurred during the execution of the file migration program. System action: The migration program ends. Problem determination: Review the message log and the dump dataset. System programmer response: If you cannot determine the cause of the error, contact your IBM representative.
EQQIC09E EQQIC14E EQQIC09E APPLICATION INDEX RECORD FOR AD HAS AN INVALID INPUT ARRIVAL IA FOR AN OCCURRENCE IN STATUS ST Explanation: A current plan application index record CPLREC05, identified in the message text, contains an invalid input arrival date in one of its occurrence data. System action: The migration program continues processing by reading the next CONVERT statement from the input file. No valid Current Plan is created.
EQQIC15E EQQIC20W EQQIC15E A PARAMETER IS REQUIRED FOR THE TOREL KEYWORD Explanation: The TOREL keyword in the current CONVERT statement does not specify a value. System action: The migration program continues processing by reading the next CONVERT statement from the input file. System programmer response: Add a file name value to the TOREL keyword of the current CONVERT statement, and resubmit the file migration batch job.
EQQIC21W EQQIC25W EQQIC21W INPUT APPLICATION APPL CONTAINS A DATE LATER THAN 1999-12-31 AND CANNOT BE CONVERTED Explanation: An application description in the input AD file is not valid 1999-12-31 or earlier, or it contains a run cycle that is not valid 1999-12-31 or earlier, or it has been updated after 1999-12-31, so it cannot be converted for fallback to a release that does not support dates later than 1999-12-31. System action: The current input record is skipped.
EQQIC26W EQQIC29E EQQIC26W INPUT ALL WORKSTATION CLOSED WAC HAS A DATE LATER THAN 1999-12-31 AND CANNOT BE CONVERTED Explanation: An all workstation closed record in the input WS file has a specific date later than 1999-12-31, or the record has been updated after 1999-12-31, so it cannot be converted for for fallback to a release that does not support dates later than 1999-12-31. System action: The current input record is skipped.
EQQIC30E EQQIC31E EQQIC30E INPUT CURRENT PLAN HAS A DATE LATER THAN 1999-12-31. CURRENT PLAN CANNOT BE CONVERTED Explanation: One or more of the following dates in current plan header record or common information is later than 1999-12-31, so the current plan cannot be converted for fallback to a release that does not support dates later than 1999-12-31.
EQQIC32W EQQIC36E EQQIC32W JCL DATASET RECORD FOR APPLICATION APPL WITH INPUT ARRIVAL IA AND OPERATION NUMBER OP£ CONTAINS A DATE LATER THAN 1999-12-31 AND CANNOT BE CONVERTED Explanation: A JCL dataset record in the input file has an occurrence input arrival date later than 1999-12-31 or the record has been updated after 1999-12-31, so it cannot be converted for fallback to a release that does not support dates later than 1999-12-31. System action: The current input record is skipped.
EQQIC37E EQQIC38W | EQQIC37E CURRENT PLAN RECORD OF TYPE RECID FOR APPLICATION AD WITH INPUT ARRIVAL IA IS | NOT VALID, TOO HIGH OCCURRENCE NUMBER, CANNOT BE CONVERTED | Explanation: The occurrence number in one of the records in the input file is higher than the range supported by the | TME 10 OPC release you are migrating to.
130 TME 10 OPC Messages and Codes
EQQJ001I EQQJ010I Chapter 13. EQQJnnn Messages EQQJ001I ETT ACTIVATION/DEACTIVATION REQUEST WAS NOT CONFIRMED Explanation: You chose not to confirm the original request, and so it was ignored by TME 10 OPC. System action: None. User response: None. EQQJ002W ETT ACTIVATION REQUEST IGNORED SINCE ETT ALREADY ACTIVE Explanation: The ETT function was already active when you requested activation of the function. System action: None. User response: None.
EQQJ011E EQQJ022E EQQJ011E YOUR CHANGES DID NOT UPDATE THE ETT DATABASE DUE TO ERRORS Explanation: Your modifications to the ETT table did not update the table dataset due to some error in the TME 10 OPC subsystem. System action: None. User response: You should exit from this panel, and then enter it again to determine which modifications updated the ETT database. Reenter those modifications that did not take effect. If the errors persist, then contact your system programmer.
EQQJ023E EQQJ029E EQQJ023E JOB NAME REPLACEMENT INFO MUST BE OCHCYES OR OCHCNO Explanation: ochcyes and ochcno are the national characters for 'Y' (yes) and 'N' (no). System action: The system waits for you to respond. User response: Enter correct data. EQQJ024E JOB NAME REPLACEMENT INFO MUST BE OCHCNO OR BLANK FOR RESOURCE EVENT Explanation: You have specified the event to be a resource event. You cannot replace job name information for resource events.
EQQJ500E EQQJ505E EQQJ500E INVALID STRING IN DIRECTIVE AT LINE LINE OF SCTN Explanation: The predicate for any keyword other than COMP must: Consist of alphanumeric characters Begin with an alphabetic character. System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code OJCV. Otherwise, the status is not changed. User response: Correct the tailoring directive.
EQQJ506E EQQJ510E EQQJ506E RECURSIVE SUBSTITUTION AT LINE LINE OF SCTN Explanation: The value of a variable depends on the values of other variables, which in turn depend on its value. No value can be determined for this variable. System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code OJCV. Otherwise, the status is not changed.
EQQJ511E EQQJ516E EQQJ511E JOB JOBNAME IN APPLICATION APPL CONTAINS AN OPC/ESA CONTROL STATEMENT THAT IS NOT RECOGNIZED Explanation: OPC/ESA was unable to submit the job identified because it contains an incorrectly coded //*%OPC statement and JCL variable scanning is active for this job. System action: Status for current operation is set to ended-in-error with error code OJCV. User response: Locate the JCL for this job and correct the //*%OPC statement. Use the OPC/ESA dialog to rerun the operation.
EQQJ517E EQQJ522E EQQJ517E INVALID VALUE VAL SUPPLIED BY USER EXIT USRX FOR VARIABLE VAR IN TABLE TAB FOR APPLICATION ADID, OCCURRENCE IA IS IAD, IAT, OPERATION NUMBER IS OPNO Explanation: The value that the user supplied for the variable violates the verification rules in the variable definition. System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code OJCV. Otherwise, the status is not changed.
EQQJ523E EQQJ530E EQQJ523E A VALIDATION PATTERN IS REQUIRED FOR PICT VERIFICATION Explanation: Because you asked for PICT verification, you must enter a validation pattern. System action: The system waits for you to respond. User response: Enter the correct value. EQQJ524E Y/N MUST BE ENTERED IN NUMERIC FIELD FOR LIST/RANGE Explanation: Because you asked for RANGE verification, you must enter Y (yes) or N (no) in the numeric field. System action: The system waits for you to respond.
EQQJ531E EQQJ535E EQQJ531E OPC/ESA WAS UNABLE TO LOAD VARIABLE SUBSTITUTION EXIT USRX TABLE NAME IS TAB, VARIABLE NAME IS VAR, APPLICATION IS ADID, OCCURRENCE IA = IAD, IAT, OPERATION NUMBER IS OPNO Explanation: A variable substitution exit that was referred to could not be loaded by TME 10 OPC. System action: The current operation status is set to ended-in-error, with error code OJCV.
EQQJ536E EQQJ541E EQQJ536E POSITIONAL OVERLAP VARIABLE VAR LINE LINE OF SCTN Explanation: The tabular variable (?-variable) cannot be assigned the positions specified in the prefix or by default because part or all of the receiving string is already occupied. For more information, refer to TME 10 OPC Planning and Scheduling the Workload. System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code OJCV. Otherwise, the status is not changed.
EQQJ542E EQQJ547E EQQJ542E COMP EXPRESSION BEGINNING AT LINE LINE OF SCTN EXCEEDS 1024 BYTES Explanation: The total length of all fields of a COMP expression, including COMP= and all continuations of the right side of the expression on subsequent JCL lines, cannot exceed 1024 characters after substitution. System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code OJCV. Otherwise, the status is not changed. User response: Correct the JCL.
EQQJ548W EQQJ561E EQQJ548W VARIABLE VAR IN TABLE TABLE COULD NOT BE UPDATED. REASON IS RSN Explanation: A SAVEVAR directive with ERRORACT=CONT was found during variable substitution. TME 10 OPC tries to update the default value as requested in the SETVAR directive, but it was not possible for one of the following reasons: HELDLOCK NOTFOUND BADVNAME Could not get ENQ lock necessary to access the variable.
EQQJ562E EQQJ566E EQQJ562E OPC/ESA WAS UNABLE TO ALLOCATE STORAGE TO PROCESS MEMBER MEMBER OF DDNAME Explanation: TME 10 OPC was attempting to build a VSAM dataset record to be inserted in the JCL repository dataset, but it was unable to do so because of insufficient virtual storage. System action: The operation remains in ready status. TME 10 OPC is unable to submit the job to JES. User response: Submit the job manually. System programmer response: Stop TME 10 OPC and then restart in a larger region.
EQQJ567E EQQJ571E EQQJ567E THE JCL FOR APPLICATION AD COULD NOT BE INSERTED IN THE JS REPOSITORY PHYSICAL RECORD SIZE IS TOO SMALL Explanation: The physical record length specified for the JS repository is too small. System action: The current operation remains in ready status. Problem determination: Check the VSAM definitions for EQQJS1DS and EQQJS2DS. User response: Contact your system programmer. System programmer response: Increase the physical record length for EQQJS1DS and EQQJS2DS.
EQQJ572E EQQJ577E EQQJ572E COMP EXPRESSION CONTAINS MULTIPLE VALUES FOR 'EXPRESSION2' Explanation: A COMP expression with operators GT, GE, LT, or LE only allows one value for expression2. System action: If the error occurs during job submit, the current operation status is set to ended-in-error with error code OJCV. Otherwise, the status is not changed. User response: Correct the JCL for the operation and make sure the COMP keyword is correct.
EQQJ578E EQQJ582E EQQJ578E THE EQQUX002 EXIT COULD NOT FIND JOB MEMBER IN ANY INPUT DATA SET Explanation: TME 10 OPC was attempting to submit a job to JES for a ready operation on a computer workstation. However, no JCL for this operation is saved in the JCL repository dataset, and the joblib I/O exit could not find the job in any input dataset. System action: The operation remains in ready status. TME 10 OPC assumes that some other function will submit the job to JES.
EQQJ583E EQQJ586W EQQJ583E JOB MEMBER IN APPLICATION APPL IS TOO LARGE TO BE SAVED ON THE JS DATA SET Explanation: A job that is about to be submitted to JES is too large to be saved in the JCL repository dataset. System action: The job will be submitted but the JCL repository data will not be updated. Problem determination: Use the IDCAMS LISTCAT function to determine the maximum size of records in the dataset defined by the EQQJSDS DD statement.
EQQJ587W EQQJ598E EQQJ587W VARIABLE VAR IN SAVEVAR DIRECTIVE NOT REFERRED IN JCL JOBNAME IS: JNM Explanation: During variable substitution of a job, a SAVEVAR directive was found requesting update of the default value of a variable. This variable was however not referred to anywhere in the JCL. System action: This is a warning. Processing continues. User response: Either delete the variable name from the SAVEVAR directive, or make sure you have a corresponding reference to the variable in the JCL.
EQQJ599E EQQJ611E | EQQJ599E NUMERIC MUST BE SPECIFIED FOR RANGE/LIST VERIFICATION | Explanation: Data entry error; see “Data Entry Errors” on page 2. | Because you asked for RANGE or LIST verification, you must set the Numeric field to Yes. EQQJ604I A DEPENDENCY HAS BEEN MODIFIED Explanation: The dependency you modified has been inserted into the database. System action: None. User response: None.
EQQJ612E EQQJ617E EQQJ612E THE JCL IMBED EXIT USRX COULD NOT FIND JOB MEMBER IN ANY INPUT DATA SET Explanation: The exit gave a return code indicating that the JCL could not be found in the exit’s input datasets. System action: The current operation status is set to ended-in-error, with error code OJCV. Problem determination: Check that all DD statements needed by the exit have been correctly defined. System programmer response: Correct all errors and then restart TME 10 OPC.
EQQJ618E EQQJ707I EQQJ618E OPC/ESA COULD NOT ALLOCATE STORAGE ENOUGH FOR RECORD READ FROM JS DATA SET. APPLICATION IS: APPL, JOBNAME IS MEMBER Explanation: TME 10 OPC tried to allocate storage for a record read from the JS dataset, but the request for storage failed. System action: The operation status depends on the SUBFAILACTION keyword in the JTOPTS initialization statement.
EQQJ708I EQQJ801E EQQJ708I THE JCL VARIABLE TABLE HAS BEEN REPLACED IN THE DATA BASE Explanation: The JCL variable table has been modified and successfully replaced in the database. User response: None. System action: None. EQQJ712E THE VARIABLE TO BE DELETED HAS DEPENDENCIES Explanation: Another variable is dependent on this variable. System action: None. User response: To delete this variable, first remove the dependency.
EQQJ802E EQQJ813E EQQJ802E NUMERIC CAN ONLY BE SPECIFIED FOR RANGE/LIST VERIFICATION Explanation: You specified a valid numeric field type, but did not specify RANGE or LIST verification. System action: The system waits for you to respond. User response: Correct the error and try again. EQQJ805E INVALID VERIFICATION TYPE Explanation: Data entry error; see “Data Entry Errors” on page 2. Valid types are ALPHA, NUM, ENUM, HEX, BIT, PICT, NAME, DSNAME, RANGE and LIST.
EQQJ814E EQQJ819E EQQJ814E OWNER ID IS MISSING Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQJ815E SUBSTITUTION EXIT NAME CONTAINS AN INVALID CHARACTER Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQJ816E THE MAXIMUM NUMBER OF DEPENDENCIES IS 360 Explanation: You tried to define more than 360 dependencies. System action: The system waits for you to respond. User response: Type over the incorrect value, and press Enter.
EQQK000E EQQK022E Chapter 14. EQQKnnn Messages EQQK000E VALID-TO SPECIFICATION PRECEDES VALID-FROM SPECIFICATION Explanation: Data entry error; see “Data Entry Errors” on page 2. The valid-to date must be later than the valid-from date. EQQK001E OI ALREADY EXISTS IN OI DATA BASE Explanation: You have attempted to create an OI that already exists in the OI database. System action: The system waits for you to respond. User response: Exit and then use the modify function instead of the create function.
EQQK023W EQQK031E EQQK023W THE OPERATOR INSTRUCTION CONTAINS NO TEXT Explanation: The OI you selected does not contain any text. System action: The system waits for you to respond. User response: If this OI should contain text, use the OI dialog to add the desired text. | EQQK024W IT IS NOT POSSIBLE TO SAVE AN OPERATOR INSTRUCTION WITHOUT TEXT | Explanation: An operator instruction must have at least one line of text. | System action: The system waits for you to respond.
EQQK032E EQQK043E EQQK032E THE NAME DOES NOT START WITH AN ALPHABETIC CHARACTER Explanation: Data entry error; see “Data Entry Errors” on page 2. | EQQK033E THE OPERATION NUMBER MUST BE IN THE RANGE 1 - 255 Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQK034E THE NAME CONTAINS INVALID CHARACTER(S) Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQK044I EQQK456E EQQK044I NO OPERATOR INSTRUCTION MATCHED YOUR SELECTION CRITERIA Explanation: No OIs matched the selection criteria you specified. System action: None. User response: None. EQQK050E A REMOVAL DATE FOR PURGING OLD TEMPORARY OIS MUST BE SPECIFIED Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQK051I PRESS ENTER TO CREATE REMOVAL JCL, OR END TO CANCEL Explanation: You have requested to create JCL for a job to remove operator instructions.
EQQK457E EQQK457E EQQK457E APPLICATION DESCRIPTION AD HAS NO OPERATION WS OP Explanation: When attempting to create or modify an OI, the OI data is checked for validity. A check is made for the corresponding operation. The validation failed because the application description AD has no operation WS OP. System action: The system waits for you to respond. User response: Correct the operation number and save the OI. Chapter 14.
160 TME 10 OPC Messages and Codes
EQQL000E EQQL006I Chapter 15. EQQLnnn Messages EQQL000E YOU ARE NOT AUTHORIZED TO ACCESS THE LTP DATA SET Explanation: You have attempted to access the LTP dataset but you are not authorized to do so. Or, you do not have access authority to at least one of the following TME 10 OPC resources that are used together with the LTP dataset: the application description database, the calendar database, or the workstation description database. System action: The system waits for you to respond.
EQQL007I EQQL018E EQQL007I THE OCCURRENCE IS CREATED Explanation: A LTP record for the occurrence has been added to the LTP dataset. System action: None. User response: None. EQQL008E THE DEPENDENCY IS ALREADY DELETED Explanation: You have tried to delete a dependency that has already been deleted. System action: Request rejected. User response: None. EQQL010E EITHER AN END DATE OR AN EXTENSION LENGTH MUST BE SPECIFIED Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL019E EQQL102I EQQL019E THE PRINT INTERVAL MUST BE WITHIN THE RANGE OF THE LTP Explanation: You have specified a print end date or print start date that is outside the range of the LTP start and end. System action: The system waits for you to respond. User response: Check the displayed LTP start and end dates, and then reenter a valid print interval.
EQQL310E EQQL464E EQQL310E THE LTP DATA SET IS EMPTY - NO HEADER FOUND Explanation: You have attempted to do one of the following: Submit an LTP batch job, but there is no header record in the LTP dataset Make a trial plan, but no LTP exists. System action: The system waits for you to respond. User response: Select the background job that creates a new LTP, and then try again. EQQL311E AN APPLICATION ID IS REQUIRED Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL465E EQQL472E EQQL465E DEPENDENCY LTPDERR NOT FOUND Explanation: The specified dependency (ltpderr) could not be found in the LTP dataset. System action: The system waits for you to respond. User response: Check that the specified dependency is correctly defined. EQQL466E OCCURRENCE HAS SUCCESSOR IN CURRENT PLAN, CANNOT BE MOVED Explanation: The run date and run time of the occurrence cannot be changed, because the occurrence has a successor that is part of the current plan.
EQQL473E EQQL499E EQQL473E MORE DEPENDENCIES DEFINED FOR LTPDERR THAN WILL FIT IN ONE RECORD Explanation: You have defined too many dependencies for the current LTP occurrence. The maximum number of dependencies possible depends on the maximum record size in the LTP VSAM file. If the default maximum record size is used, the maximum number of dependencies is 3574. System action: The LTP dialog waits for you to respond.
EQQL504E EQQL512E EQQL504E APPLICATION DEPAID NOT FOUND Explanation: The application (DEPAID) specified in the LTP occurrence was not found in the application description database. The application might have been deleted from the application description database or the user does not have access to read the application description for the dependent application. System action: The system waits for you to respond. User response: Check why the application description cannot be found.
EQQL513E EQQL567I EQQL513E THE VARIABLE TABLE NAME CONTAINS AN INVALID CHARACTER Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQL514E YOU ARE NOT AUTHORIZED TO READ THE JCL VARIABLE TABLE DATA BASE Explanation: You have attempted to refer to a JCL variable table. To do this, you need read authority to the JCL variable table database. System action: The system waits for you to respond.
EQQL568I EQQL706E EQQL568I LTPCHDD, LTPCHDT DEADLINE PAST OCCURRENCE TIME LIMIT Explanation: The operation deadline LTPCHDD, LTPCHDT is outside the occurrence time limit. System action: None. User response: None. EQQL570I THE INPUT ARRIVAL SPECIFIED IS LATER THAN THE DEADLINE Explanation: The operation input arrival date and time are later than the application deadline. System action: The system waits for you to respond.
170 TME 10 OPC Messages and Codes
EQQM000E EQQM011I Chapter 16. EQQMnnn Messages EQQM000E YOU DO NOT HAVE AUTHORITY TO ACCESS THE CURRENT PLAN Explanation: To use the function you selected, you must have access authority to the current plan. System action: The request is rejected and the system waits for you to respond. User response: Contact your security administrator if you require access to the current plan.
EQQM012I EQQM019E EQQM012I OCCURRENCE DELETED FROM THE CURRENT PLAN Explanation: The occurrence you specified was deleted from the current plan. System action: None. User response: None. EQQM013I THE OCCURRENCE IS SET TO RERUN Explanation: In the current plan, the status of the occurrence specified was changed to “rerun.” System action: None. User response: None. EQQM014I THE OCCURRENCE IS SET TO WAITING Explanation: In the current plan, the status of the occurrence specified was changed to “waiting.
EQQM020E EQQM026E EQQM020E VALID STATUSES ARE W, S, C, E, AND U, IN ANY COMBINATION Explanation: In the Modify Current Plan dialog, you entered an invalid status for selecting occurrences in the current plan. System action: The panel is redisplayed and the system waits for you to respond. User response: Correct the invalid values. EQQM021I THE OPERATION WAS RESET TO READY Explanation: In the current plan, the status of the operation specified was reset to “ready.” System action: None.
EQQM027E EQQM033E EQQM027E REQUEST FAILED BECAUSE OF SUBSYSTEM ERROR. REASON: XSSRS Explanation: The modify current plan request failed because of an error in the TME 10 OPC subsystem. System action: The modify current plan function is terminated; no updates are made. Message EQQMxssrsE is written to the message log, where xssrs is the reason code displayed by this message. User response: See the message indicated by the reason code.
EQQM034E EQQM062E EQQM034E THE JCL FOR THIS OPERATION IS BEING EDITED BY ANOTHER USER Explanation: You tried to rerun an operation, but the JCL for this operation is being edited by another user. System action: The system waits for you to respond. User response: Try again later. EQQM035E ONE OF THE WS REFERENCED BY OPERATIONS IN THIS OCC. IS NOT IN CP Explanation: TME 10 OPC was validating an occurrence to be added.
EQQM063E EQQM100W EQQM063E THE ALTERNATE WS NAME IS NOT FOUND IN THE DATA BASE Explanation: The alternate workstation is not defined in the workstation database. System action: The status of the workstation does not change. Reroute is not performed to an alternate WS. User response: Correct the name specified for alternate WS, or update the workstation description database with this workstation name.
EQQM104E EQQM115E EQQM104E NO APPLICATIONS MET THE SELECTION CRITERIA Explanation: No applications were found in the application description database, which met the selection criteria that you specified. System action: The system waits for you to respond. User response: Change the selection criteria. EQQM106E DEP OPTION MUST BE ONE OF OCHCYES, ochpred, ochsucc, ochgrp or ochcno Explanation: You have entered a value for the dependency resolution attribute that is not recognized by the MCP dialog.
EQQM117E EQQM150E EQQM117E WORK STATION MOWSN IS NOT FOUND IN THE CP, OR ACCESS WAS REVOKED Explanation: The workstation specified (mowsn) does not exist in the current plan, or you are not authorized to access this workstation. System action: The system waits for you to respond. User response: Change the occurrence so that it uses only workstations that are in the current plan. If you are not authorized to access this workstation, contact your security administrator.
EQQM151E EQQM155E EQQM151E CURRENT PLAN READ ERROR, AD NOT ADDED TO CURRENT PLAN Explanation: A request to create an occurrence in the current plan failed due to an I/O error. System action: If this is a request to the program interface function, the request is rejected and control is returned with the return code set to error. Problem determination: The message log of the TME 10 OPC subsystem contains the I/O error message.
EQQM161E EQQM171E EQQM161E MODIFY CP REQUEST FAILED, INSUFFICIENT STORAGE. REASON: RS Explanation: A request to create or modify an occurrence in the current plan failed due to storage allocation failure. The reason code provides debugging information for IBM personnel. System action: If this is a request to the program interface function, the request is rejected and control is returned with the return code set to error.
EQQM172E EQQM204E EQQM172E MAXIMUM NUMBER OF OCCURRENCES EXISTS, FAILED TO ADD AD | Explanation: No more occurrences can be added to the Current Plan because the maximum number of | occurrences—32767 or the number specified in the MAXOCCNUM option of the JTOPTS statement—has been | reached. System action: The request is rejected. Problem determination: If you use ETT, PIF, or Automatic Recovery, check that these functions are working correctly.
EQQM205E EQQM218E EQQM205E NUMBER OF SERVERS MUST BE BETWEEN 1 - 99 Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQM206E NUMBER OF WORK STATION RESOURCES MUST BE BETWEEN 0 - 99 Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQM207E THE NEW STATUS MUST BE R-READY, S-STARTED, OR C-COMPLETED Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM219E EQQM226E EQQM219E OPERATION NUMBER MUST NOT BE CHANGED FROM MOONU Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQM220E DEPENDENCY TYPE MUST BE P-PREDECESSOR OR S-SUCCESSOR Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQM221E NO OPERATIONS IN CURRENT PLAN MATCH THE SEARCH ARGUMENT Explanation: In the current plan, there are no operations that meet your selection criteria. System action: The system waits for you to respond.
EQQM227W EQQM237E EQQM227W A SUCCESSOR DEPENDENCY COULD NOT BE ADDED Explanation: A dependency to a potential successor operation could not be added because the successor operation has already started. System action: If this message is issued when the DEP command has been entered, then unresolved successors are indicated by a missing (blank) input arrival time. If this message is issued when trying to add an occurrence to the plan and the RESOLVE REQUIRED indicator is Y, then the occurrence is not added.
EQQM238E EQQM246E EQQM238E YOU ARE NOT AUTHORIZED TO READ THE JCL VARIABLE TABLE DATA BASE Explanation: You have attempted to access a JCL variable table. To do this, you need at least read authority to the JCL variable table database. System action: The system waits for you to respond. User response: Contact your security administrator if you need to refer to JCL variable table names.
EQQM250E EQQM257I EQQM250E CURRENT OPERATION STATUS MUST BE A, *, R, W, C, OR E TO BE HELD Explanation: Only operations in status A, W, R, *, C, or E can be manually held. System action: The request is ignored. User response: None. EQQM251I OPERATION IS ALREADY MANUALLY HELD BY DIALOG Explanation: The operation has already been set to MANUAL HOLD by an TME 10 OPC dialog user. System action: The request is ignored. User response: None.
EQQM258I EQQM265E EQQM258I OPERATION HAS BEEN NOPED Explanation: The operation has been recognized as no-oped by TME 10 OPC The operation will not be executed, and dependent operations may be started as a result. System action: The operation is indicated as no-oped. User response: None. EQQM259I OPERATION NOP HAS BEEN RESET Explanation: An operation has been successfully reset from its NOP indication at an TME 10 OPC dialog user's request. System action: The operation's NOP indication is removed.
EQQM266E EQQM313E EQQM266E THERE IS NO ACTIVE WORKSTATION FOR THIS OPERATION Explanation: The operation is scheduled on a workstation that is inactive. If alternate workstations are specified, these are also inactive. System action: The request is ignored. User response: Issue the EXECUTE command when the workstation, or an alternate workstation, becomes active again.
EQQM314E EQQM322E EQQM314E VALUE FOR PARALLEL SERVERS MUST BE 0 - 99 Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQM315I INTERVAL PREVIEW Explanation: Table result is merged from modified and planned intervals. The table is built from the modified and planned intervals according to the workstation. System action: Processing continues. User response: The END command will cause the displayed table to be used. ENTER will cause the table to be displayed without this message.
EQQM323W EQQM330I EQQM323W CATALOG MANAGEMENT IS PENDING FOR THE CURRENT OPERATION Explanation: You have tried to perform automatic recovery for this operation when there is a deferred catalog management action defined for this operation. System action: The system waits for you to respond User response: Make sure that the action is either performed or discarded before you try to perform automatic recovery for the operation EQQM324E CATALOG MANAGEMENT is in progress for oper OP in appl AD.
EQQM331E EQQM337E EQQM331E THE ONLY VALID VALUES ARE OCHCDFR ,OCHCYES OR OCHCNO Explanation: You have entered an incorrect action for the catalog management function. System action: The system waits for you to respond. User response: Enter correct value and press enter. EQQM332I THE CATALOG MANAGEMENT FUNCTION IS NO LONGER ACTIVE Explanation: The catalog management function has been deactivated after the time that dataset information was collected for this operation.
EQQM338I EQQM343E EQQM338I OPC/ESA HAS FOUND NO INCONSISTENCIES IN THE JCL FOR A RESTART Explanation: TME 10 OPC has investigated the JCL for restart and has found no errors. The operation may be restarted. System action: None. User response: Leave the panel with END command to save the JCL and initiate catalog management actions for the operation, cancel the restart using the CANCEL command.
EQQM344W EQQM351I EQQM344W THE APPLICATION IS A MEMBER OF A GROUP. CONSIDER ADDING THE OTHER MEMBERS Explanation: The application is a member of an application group. This message is issued as a reminder in case you should also add the other members of the same group to the current plan. System action: Normal processing continues. User response: If applicable, create occurrences in the current plan for the other applications in the same group. EQQM345E ONE OR MORE OCCURRENCES ARE IN USE.
EQQM352E EQQM357E EQQM352E SOME ADDED OCCURRENCES COULD NOT BE RELEASED Explanation: One or more of the applications added to the plan could not be released. Error is displayed in the list to indicate the failing occurrence. System action: The system waits for you to respond. User response: See MLOG for possible error information. The occurrence can be deleted from the list with the row command.
EQQM358W EQQM366I EQQM358W DEP LOOP DETECTED, NOT ALL DEPS RESOLVED WITHIN THE GROUP Explanation: One or more dependency loops has been found in the occurrence group. System action: In each loop, the external dependencies for one of the operations has not fully been resolved within the group. If there are other occurrences, external to the group, in the current plan that matches these dependency definitions, the dependencies have been resolved to those occurrences.
EQQM368E EQQM374W EQQM368E IF STATEMENT REFERS BACK TO STEP PRIOR TO RESTART STEP Explanation: Restarting this job could result in unpredictable results as the IF statement refers to a step prior to a restart step. JCL error. System action: None. User response: Verify that the step being referred to is correct and amend the JCL accordingly.
EQQM375I EQQM380W EQQM375I OPC WILL ATTEMPT TO DELETE THIS DATASET Explanation: TME 10 OPC will attempt to delete this dataset before this job is restarted. System action: None. User response: None. EQQM376I OPC WILL ATTEMPT TO UNCATALOG THIS DATASET Explanation: TME 10 OPC will attempt to uncatalog this dataset before this job is restarted. System action: None. User response: None.
EQQM381I EQQM387W EQQM381I OPC/ESA HAS FOUND NO INCONSISTENCIES IN THE JCL FOR A RESTART Explanation: TME 10 OPC has investigated the JCL for restart, and has found no errors. The operation may be restarted. System action: None. User response: Leave the panel with END command to save the JCL and initiate catalog management for the operation, cancel the restart using the CANCEL command, or edit the JCL using JCL primary command.
EQQM388W EQQM392E | EQQM388W VERIFY JCL FOR POSSIBLE INCONSISTENCIES | Explanation: One of the following situations has occurred: | | At least one step staus of FLUSH was detected. Restarting from this step may be possible; however verification for the status of datasets used in this step is recommended. | | At least one IEF377I message was found in the joblog. This means that in the previous run the job successfully allocated the data set, but did not manage to catalog it. | System action: None.
EQQM393E EQQM398W EQQM393E CATALOG MANAGEMENT IS ONLY ALLOWED FOR OPERATIONS RUNNING ON MVS Explanation: You have tried to make a catalog management step-level restart request, a joblog has been found but the joblog is created on a non-MVS platform. System action: The panel will be redisplayed with this error message. User response: You will not be able to perform catalog management for this job.
EQQM399W EQQM403E EQQM399W CM ACTION SPECIFIED FOR THIS JOB IS OCHCNO Explanation: The job to be rerun contains GDG datasets but catalog management action for the operation is none. The absolute GDG value is missing therefore missing and the GDG dataset cannot be resolved. System action: The JCL is presented to the user with the GDG dataset specification unchanged. User response: Change the DD statement manually.
EQQM404I EQQM910E EQQM404I THE JOB FOR THIS OPERATION MIGHT NOT BE THE ORIGINAL JOB Explanation: No job for this operation was found in the history database. This job was copied from the EQQJBLIB file. System action: Processing continues. User response: Verify if the job needs to be changed before it is submitted. EQQM405W THE HISTORY FUNCTION IS NOT ACTIVE Explanation: You tried to retrieve operations from the history database but the history function is not active on your TME 10 OPC subsystem.
EQQM911E EQQM915E EQQM911E INVALID DEPENDENCY INFO FOR: APPL, OPER, PRED: PRED Explanation: A modify-current-plan request failed because dependency data has been changed during the dialog session. The request was attempted for application APPL and operation number OPER. The number of the predecessor operation is PRED. System action: The request is rejected, and message EQQM025E is issued to the dialog user.
EQQM916E EQQM920E EQQM916E REQUEST TO ADD SPECIAL RESOURCE THAT ALREADY EXISTS OPERATION SPECIAL RESOURCE: SPR : APPL, OPER Explanation: A modify-current-plan request to add a special resource failed because the the requested special resource already exists in the operation. The application ID and operation number are listed together with the special resource name. System action: The request is rejected and message EQQM025E is displayed to the dialog user.
EQQM921E EQQM925E EQQM921E DELETE OF INTERNAL PREDECESSOR CONNECTION FAILED, REASON: RS APPLICATION: APPL, IA, OPERATION: OPER, DEPENDENCY: PREOP Explanation: A request for current plan modification would result in an invalid occurrence. The following reason codes (RS) indicate why: 921 922 923 The last internal dependency cannot be deleted. The delete would have resulted in a split into two networks. The predecessor specification is not found.
EQQM926E EQQM929W EQQM926E PRINT OPERATION HAS MORE THAN 1 PREDECESSOR OPERATION: APPL, IA, OPER Explanation: A modify-current-plan request would have caused a print operation to have more than one predecessor. The application ID, input arrival date and time, and operation number are listed. The operation number is given in hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log. System action: The request is rejected, and message EQQM025E is issued to the dialog user.
EQQM930E EQQM933E EQQM930E CP MAY BE DESTROYED DUE TO ERRORS DURING MCP UPDATE Explanation: An error occurred while updating the current plan, causing it to be partially updated. System action: Processing is terminated for the current request, and message EQQM025E is issued to the dialog user. Problem determination: Previous error messages in the TME 10 OPC message log contain additional information about this error. System programmer response: See message EQQM936E.
EQQM934E EQQM950E EQQM934E JOBLOG FOR JOBN (JID) CANCELLED. REISSUE REQUEST Explanation: You have made a catalog management or a browse-joblog request on an TME 10 OPC system activated for step-level restart and where the required joblogs will be retrieved at the time of your request. TME 10 OPC has initiated the retrieval request but error return codes were issued by internal TME 10 OPC functions.
EQQM951E EQQM954E EQQM951E FAILED TO ADD APPLICATION ADID REASON: CANNOT READ CURRENT PLAN RECORD Explanation: A request to create an occurrence on the current plan failed due to an I/O error. System action: The request is terminated and the processing continues with the next request. Problem determination: The message log contains the I/O error message. User response: Resubmit the job when the problem causing the I/O error has been corrected.
EQQM955E EQQM971E EQQM955E FAILED TO ADD APPLICATION ADID CAN NOT READ THE APPLICATION DESCRIPTION FILE Explanation: The TME 10 OPC subsystem has received a request to add an occurrence of application ADID to the current plan. The application description file was not open. System action: The request to add the current plan occurrence is rejected. Problem determination: The message log should contain a previous message giving the reason why the file is not open.
EQQM972E EQQM975E EQQM972E MCP WAS UNABLE TO ADD APPLICATION APPL BECAUSE AN MCP CONTROL BLOCK (MT0) COULD NOT CONTAIN ALL SUCCESSOR DEPENDENCIES TO APPLICATION SUCC Explanation: The MCP service processor was unable to add any more successor dependencies to the MT0 block that is used to define MCP processing. The maximum size of an MT0 block is 32768 bytes. System action: MCP abandons the attempt to add current occurrence.
EQQM976W EQQM991E occurrences, and then try to add the occurrence again. If your current plan regularly contains a large number of occurrences, you should consider shortening the length of the Current Plan in future daily planning runs. EQQM976W ONE OR MORE OF THE EXTERNAL DEPENDENCIES OF OPER OPER IN APPLICATION ADID WERE NOT RESOLVED WITHIN THE GROUP Explanation: A dependency loops in an occurrence group has been detected and eliminated.
EQQN000I EQQN003E Chapter 17. EQQNnnn Messages EQQN000I THE NORMAL MODE MANAGER TASK HAS BEEN REQUESTED TO TERMINATE Explanation: The Normal Mode Manager has been requested to terminate processing. This request will be propagated to all active subtasks. The Normal Mode Manager will start its own termination when all subtasks have ended. System action: The Normal Mode Manager waits for all subtasks to end.
EQQN004E EQQN006E EQQN004E VSAM PHYSICAL I/O ERROR. DETAILED INFORMATION FOLLOWS: ACTIVE TASK IS TASK. LOAD MODULE IS MODULE I/O REQUEST IS FROM MODID AT OFFSET +OFFSET REQUESTED FUNCTION IS FUNC ON LOGICAL FILE FILE, DDNAME DDNAME VSAM RETURN CODE IS 12, REASON CODE IS RSN, KEY IS KEY VSAM MESSAGE: SYNAD Explanation: A TME 10 OPC subtask or batch job encountered an I/O error when accessing a VSAM dataset.
EQQN007E EQQN010E EQQN007E THE FOLLOWING INVALID RECORD WAS ENCOUNTERED WHEN THE NORMAL MODE MANAGER WAS PROCESSING THE JOB TRACKING LOG DATA SET DURING RESTART FROM CHECKPOINT: EVENT HEADER: EVNTHDR EVENT RECORD: EXITREC Explanation: An invalid job tracking event record has been found in the job tracking log dataset. The NMM could not determine the origin of the event. Each event must come from one of 16 possible event datasets on each TME 10 OPC node.
EQQN011E EQQN016I System programmer response: Scratch and reallocate the job tracking log data set at a suitable moment when TME 10 OPC is stopped. EQQN011E A SEVERE ERROR, SYSTEM ABEND ABEND, OCCURRED WHILE ATTEMPTING TO UPDATE CURRENT JOB TRACKING LOG DATA SET Explanation: An abend occurred when an TME 10 OPC function attempted to write a record to the current job tracking log dataset. If the abend code is SB37 or SD37, then the current job tracking log dataset is too small.
EQQN017I EQQN022I EQQN017I THE JCL REPOSITORY DATA SET WILL BE COPIED Explanation: A TME 10 OPC subtask has started to copy the JCL repository dataset because the current one has reached its maximum size, or because a backup has been requested using the BACKUP TSO command for the JS resource. System action: TME 10 OPC processing continues. User response: None.
EQQN023I EQQN026W EQQN023I VSAM LSR BUFFERS HAVE BEEN SUCCESSFULLY DELETED FOR VSAM FILE DDNAME Explanation: TME 10 OPC successfully deleted the buffer pool for the file indicated in the message. System action: None. User response: None. EQQN024W VSAM LSR BUFFER DELETE FAILED FOR VSAM FILE DDNAME RETURN CODE FROM DLVRP WAS VRPRC Explanation: TME 10 OPC could not delete the buffer pool for the file indicated in the message. System action: None.
EQQN027E EQQN031E EQQN027E The Normal Mode Manager is terminating unexpectedly. NMMSTAT is NMMSTAT Explanation: The Normal Mode Manager is in the process of terminating unexpectedly. The reason for the termination is documented by NMMSTAT, which can have the following values: E A S An I/O error has occurred Virtual storage is exhausted Termination requested by another TME 10 OPC function. System action: NMM will terminate all related subtasks.
EQQN032E EQQN038E EQQN032E UNABLE TO OPEN OPC/ESA VSAM FILE FILE, VSAM RC = RC, REASON = RSN Explanation: The TME 10 OPC subsystem or a TME 10 OPC batch job could not open a VSAM dataset. System action: The messages that follow this message in the message log identify the action taken by the subsystem or the batch job. Problem determination: Use the VSAM return code and reason code to determine the cause of the error.
EQQN043E EQQN047W EQQN043E UNSUCCESSFUL VSAM I/O REQUEST. DETAILED INFORMATION FOLLOWS: ACTIVE TASK IS TASK. LOAD MODULE IS MODULE I/O REQUEST IS FROM MODID AT OFFSET +OFFSET REQUESTED FUNCTION IS FUNC ON LOGICAL FILE FILE, DDNAME DDNAME VSAM RETURN CODE IS 8, REASON CODE IS RSN, KEY IS KEY HEXADECIMAL ZONES HEXKEYZ HEXADECIMAL DIGITS HEXKEYD Explanation: A TME 10 OPC subtask encountered an unexpected error when accessing a VSAM dataset.
EQQN049I EQQN052W EQQN049I EXCLUSIVE CONTROL VSAM ERROR, RETCODE 8, REASON CODE 0020, WAS CAUSED BY A RESOURCE CONFLICT WITH OPC/ESA SUBTASK TASK Explanation: This message contains additional information for a preceding EQQN043E message. It identifies the TME 10 OPC subtask that has exclusive control of a VSAM control interval that the current TME 10 OPC subtask needs. System action: TME 10 OPC processing continues.
EQQN053W EQQN070E EQQN053W OCCURRENCE occid WITH IA iadate iatime MAY CONTAIN HELD OPERATIONS. Explanation: An MCP multiple add request did not complete normally. TME 10 OPC has cancelled the wait for the completing modify request. Operations within the reported occurrence may be in held status and must be released manually. System action: The wait for the modify request has been cancelled. User response: Respond as for message EQQX146.
EQQN071E EQQN083E EQQN071E AN ATTEMPT TO UPDATE THE NOERROR TABLE HAS FAILED Explanation: A modify command was entered requesting the noerror table to be updated. One or more errors were found while processing input NOERROR statements. System action: The NOERROR table is not changed. TME 10 OPC continues normal processing. User response: Review earlier error messages in the message log that describe initialization statement processing errors. Correct all identified errors and reenter the modify command.
EQQN084E EQQN087E EQQN084E DD STATEMENT IS MISSING FOR A JOB TRACKING LOG DATASET, DDNAME DDNAME Explanation: A DD statement needed to support currently specified (or defaulted) values of the JTLOGS and DUAL keywords of the JTOPTS initialization statement is not defined. System action: The Normal Mode Manager subtask terminates. TME 10 OPC administrator response: Contact your system programmer.
EQQN088E EQQN092E EQQN088E NMM WAS UNABLE TO SWITCH TO NEXT JOB TRACKING LOG DATA SET, DDNAME DDNAME, BECAUSE IT HAS NOT YET BEEN ARCHIVED. Explanation: TME 10 OPC was unable to use the next job tracking log in a situation where current job tracking log can no longer be used. System action: The Normal Mode Manager subtask is stopped and the current plan is no longer available.
EQQN093E EQQN101E EQQN093E AN SEVERE ERROR, SYSTEM ABEND ABEND, OCCURRED WHILE ATTEMPTING TO UPDATE THE JOB TRACKING LOG ARCHIVE DATA SET. THE ARCHIVER TASK IS ENDING. Explanation: An abend occurred when the JT log archiver task tried to write a log record to the job tracking archive log data set. If the abend code is SB37 or SD37, then the archive dataset is too small. System action: The JT log archiver task ends.
EQQN102W EQQN108E EQQN102W AN OPC/ESA USER EXIT LOAD MODULE, MODULE, COULD NOT BE LOADED Explanation: TME 10 OPC could not locate an exit load module. System action: This exit will not be used by TME 10 OPC. Problem determination: Check if the module named in this message should be used by TME 10 OPC. Also check that the module exists in a library that the subsystem started task can reach. System programmer response: Correct the error, and restart the TME 10 OPC subsystem.
EQQO001I EQQO006E Chapter 18. EQQOnnn Messages EQQO001I APPC TASK INITIALIZATION IS COMPLETE Explanation: The APPC task has completed initialization processing. System action: Processing continues. Operator response: None. EQQO002E APPC TASK ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT APP Explanation: An abend prevented the APPC task from processing a queue element. System action: MVS recovery/termination is requested to generate a dump. The APPC task attempts to continue normal processing.
EQQO007E EQQO011E EQQO007E THE APPC TASK IGNORED THE FOLLOWING ELEMENT ON THE APPC QUEUE DQE Explanation: An invalid allocate request, or outbound reply was found on the APPC queue. System action: Processing continues. System programmer response: If the element was an allocate request from a user written TP, verify the code in the TP, otherwise contact your IBM representative. EQQO008E THE APPC TASK IGNORED THE FOLLOWING INBOUND APPC BUFFER APP Explanation: An invalid buffer was received.
EQQPH00I EQQPH06E Chapter 19. EQQPnnn Messages EQQPH00I SERVER TASK HAS STARTED Explanation: The Server task has started successfully. This task is started by the Server Started task. It is started by the TME 10 OPC subsystem if APPC(YES) is specified in the OPCOPTS initialization statement. System action: TME 10 OPC continues processing. EQQPH01I SERVER TASK ENDED Explanation: The Server task has been requested to stop and is ending normally. System action: TME 10 OPC continues processing.
EQQPH10E EQQPH13E EQQPH10E COMMUNICATION WITH USER USER AT LU LU FAILED, APPC/MVS SERVICE VERB REQUESTED IN STATE STATE RETURN_CODE RC, STATUS_RECEIVED SR, DATA_RECEIVED DR Explanation: The APPC/MVS communication between a dialog user or program interface application and the TME 10 OPC server failed. An APPC/MVS service request issued by the server ended with a nonzero return code. System action: The server deallocates the APPC/MVS conversation.
EQQP010E EQQP014E EQQP010E VERB in state STATE failed with RC RC, SR SR, DR DR Explanation: An APPC/MVS service request issued for server communication failed. The verb VERB was issued when the conversation was in state STATE. APPC/MVS returned: Return_Code RC, Status_Received SR and Data_Received DR. System action: The request is rejected. User response: Check that the proper LU name is specified. For the dialog the LU name is set via the OPTIONS menu.
EQQP015E EQQP015E EQQP015E FAILED TO SET UP COMMUNICATION WITH SERVER LU, RC RC Explanation: An APPC/MVS Allocate request issued for server communication failed. LU shows the LU name of the server. RC shows the return code of the Allocate request. System action: The user cannot start the TME 10 OPC dialog. The INIT request of program interface application gets return code 8. User response: Check that the proper LU name is specified and LU is active as well.
EQQQ002E EQQQ010E Chapter 20. EQQQnnn Messages EQQQ002E THE SPECIAL RESOURCE GROUP IS INVALID Explanation: You have entered a group ID that contains invalid characters. System action: The request is rejected. User response: Change the group ID so that is contains any character in the range A–Z, 0–9 or national characters. EQQQ004E THE ENTRY IS INVALID, ENTER EITHER A OCHCYES OR A ochcno Explanation: You have entered an invalid character in the field. It must be either a ochcyes or a ochcno.
EQQQ011E EQQQ018W EQQQ011E THE TO TIME MUST BE GREATER THAN THE FROM TIME Explanation: You have entered an invalid combination of to and from times. System action: The request is rejected. User response: Ensure that the to time is greater than the from time. EQQQ012E 24.00 IS NOT ALLOWED AS TO TIME Explanation: Data entry error; see “Data Entry Errors” on page 2. Valid to times are 00.00 through 23.59.
EQQQ019E EQQQ028I EQQQ019E THE ENTRY IS INVALID, ENTER A VALUE IN THE RANGE -999999 TO 999999 Explanation: You have entered an invalid deviation in the field. It must be in the range -999999 to 999999. System action: The request is rejected. User response: Change the quantity to a valid value. EQQQ021E 00.00 IS NOT ALLOWED AS FROM TIME Explanation: Data entry error; see “Data Entry Errors” on page 2. Valid from times are 00.01 through 24.00.
EQQQ029I EQQQ036E EQQQ029I WS CONNECT LIST NOT DEFINED FOR THIS INTERVAL, DEFAULTS WILL BE USED Explanation: You have attempted to access the list of connected workstations in an interval for which no list has been defined. The default connected workstations defined for this special resource will be used instead. System action: The request is rejected. User response: Define a list of connected workstations for this interval if the default list should not be used.
EQQQ038E EQQQ501E EQQQ038E A SPECIAL RESOURCE WITH THIS NAME ALREADY EXISTS Explanation: You have attempted to create a special resource which already exists. System action: The request is rejected. User response: Change the special resource name to something unique. EQQQ039E YOU ARE NOT AUTHORIZED TO ACCESS THE RD Explanation: You have attempted to access the special resource description (RD) database, but you are not authorized to access it. System action: The request is rejected.
EQQQ502I EQQQ505E EQQQ502I SPECIAL RESOURCE DATASPACE HAS BEEN CREATED. SIZE PAGES ARE USED FOR NUM SPECIAL RESOURCE RECORDS Explanation: A data space has been successfully created for special resource records. SIZE shows the number of pages (each 4096 bytes) used to create the data space. NUM shows the maximum number of special resource records that the data space can contain. TME 10 OPC uses a minimum of 20 pages. System action: Normal processing continues.
EQQQ506I EQQQ510W EQQQ506I SPECIAL RESOURCE DATASPACE HAS BEEN EXTENDED SIZE PAGES ARE USED FOR NUM SPECIAL RESOURCE RECORDS Explanation: A data space for special resource records has been successfully extended. SIZE shows the number of pages (each 4096 bytes) the data space was extended to. NUM shows the maximum number of special resource records that the data space can contain. System action: Normal processing continues. TME 10 OPC will use the data space when accessing special resources.
EQQQ511W EQQQ515W EQQQ511W RESOURCE: RESNAME IS TOO LARGE. THE LAST INTERVAL USED STARTS AT DATE TIME Explanation: This message is issued to the message log when a special resource is too large to fit into the CX file. System action: The special resource record is truncated to fit into the CX file. The start time of the last interval used in the record is displayed in the message.
EQQRM01I EQQRM07W Chapter 21. EQQRMnn Messages EQQRM01I RODM SUBTASK INITIALIZATION IS COMPLETE Explanation: The RODM subtask has completed initialization processing. System action: Processing continues. Operator response: None. EQQRM02E RODM SUBTASK ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT DQE Explanation: An abend prevented the RODM subtask from processing a queue element. System action: MVS recovery/termination is requested to generate a dump.
EQQRM09E EQQRM16I EQQRM09E RODM SUBTASK QUEUE POINTERS ARE DESTROYED, RODQ IS LOST Explanation: The RODM subtask abended while processing elements on APPQ because the queue chaining is invalid. System action: MVS recovery/termination is requested to generate a dump. The RODM subtask restarts, and resumes normal processing. Problem determination: Review the TME 10 OPC message log dataset (EQQMLOG), the diagnostic dataset (EQQDUMP), and the system dump dataset to determine the cause of the problem.
EQQRM17W EQQRM22W EQQRM17W CONNECTION LOST TO RODM SUBSYSTEM: NAME Explanation: TME 10 OPC has lost the connection to a RODM subsystem. System action: Processing continues. The status for all resources being monitored by the named RODM subsystem will be set to inactive, and the values of the corresponding TME 10 OPC resource fields will be set according to the RODMLOST values in the RODMOPTS statements. Attempts to reconnect to this RODM subsystem will be initiated every 5 minutes. User response: None.
EQQRM23W EQQRM28W EQQRM23W A SPECIAL RESOURCE DEVIATION COULD NOT BE DETERMINED FROM A RODM OBJECT. RESOURCE NAME IS NAME Explanation: A RODMOPTS statement specifies that a special resource deviation quantity should be updated by a field in a RODM object. However, the value of the field is not within the valid range of special resource deviations. The valid range is -999999 – 999999. System action: The special resource quantity is not changed. The RODM subtask continues normal processing.
EQQRM29W EQQRM29W | EQQRM29W SUBSCRIBE FOR RODM CLASS NAME FAILED. RC IS RC, REASON IS RSN OPC/ESA WILL | RETRY EVERY 3 MINUTES | Explanation: A nonzero return code was returned by a RODM system when the RODM subtask called the RODM | API to add a notify subscription for a RODM class. | System action: The RODM subtask continues normally. TME 10 OPC will try again after three minutes to add the | notify subscription for the RODM object. | System programmer response: None. Chapter 21.
248 TME 10 OPC Messages and Codes
EQQR000E EQQR013E Chapter 22. EQQRnnn Messages EQQR000E YOU ARE NOT AUTHORIZED TO ACCESS THE READY LIST Explanation: You have attempted to access the ready list but you are not authorized to access it. System action: The requested access to the ready list is rejected. User response: Contact your security administrator if you require access to the ready list.
EQQR014W EQQR023E EQQR014W ERDR ERC£ NO VALID HEADER IN EVENT DATA SET WITH DDNAME DDN Explanation: Event reader ERC encountered a header record that contained invalid information, for example, the track capacity and the total number of records in the dataset were missing. The most probable reason for this message is that a new event dataset has been created and it is being formatted by the event writer before usage.
EQQR024E EQQR029E EQQR024E ERDR ERC£ TERMINATION DUE TO INITIALIZATION FAILURE Explanation: Event reader ERC has encountered initialization errors. System action: Event reader ERC processing is terminated. Problem determination: This message is preceded by other messages in the TME 10 OPC message log. They indicate the exact reason for the failure. System programmer response: Stop the event readers using the MODIFY command. Correct the error, if any, and then restart the event readers.
EQQR101E EQQR108W EQQR101E THE LAYOUT RLLAYOUT CANNOT BE ADDED TO THE LAYOUT TABLE Explanation: The ready list layout table already contains the layout you tried to add. System action: The ready list layout table is not updated. User response: You can change the layout name and repeat the request. EQQR102I THE LAYOUT RLLAYOUT HAS BEEN ADDED TO THE LAYOUT TABLE Explanation: The layout has been successfully added to the ready list layout table and saved.
EQQR109E EQQR201I EQQR109E THE LAYOUT RLLAYOUT CANNOT BE FOUND IN THE LAYOUT TABLE Explanation: The layout rllayout does not exist. System action: The system waits for you to respond. User response: Select one of the layouts in the list or create a new one. EQQR110E THE LAYOUT ID MUST BE SPECIFIED Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQR111E SELECT AN ITEM BY SPECIFYING SELECT OR A NUMBER 01-99 Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQR202I EQQR403E EQQR202I SET STATUS REQUEST CANCELLED BY USER EXIT Explanation: The active exit for this ready list layout has returned a 9 in the status field URNSTAT, which means cancel the request. System action: The status is not changed. User response: None. EQQR300E PRIORITY MUST BE A NUMBER 1 - 9 Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQR302E SELECT THE WORK STATION TO DISPLAY A READY LIST Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQR404E EQQR617E | EQQR404E STORAGE PROBLEMS OCCURRED | Explanation: In an MCP dialog JCL edit session the Controller returned data that could not be retrieved and | displayed, because not enough storage had been preallocated to receive it. | Problem determination: This message indicates that, in the ISPF environment, there is not enough main storage to | receive and display the JCL modified and returned from the controller.
EQQR618W EQQR626E EQQR618W REQUEST TO SET THE STATUS TO ERROR IS IGNORED Explanation: You have attempted to set an operation in the current plan to ended-in-error status but the operation is already set to that status. System action: The request is ignored. User response: None. EQQR619W REQUEST TO SET THE STATUS TO COMPLETE IS IGNORED Explanation: You have attempted to set an operation in the current plan to “complete” status but the operation has already completed. System action: The request is ignored.
EQQR627E EQQR651E EQQR627E RESET OF OSEQ OPERATION MUST BE DONE USING MODIFY CURRENT PLAN DIALOG Explanation: You attempted to reset an operation with error code OSEQ from the Ready List dialog. This cannot be done. The error code OSEQ indicates that a job began to execute before all the predecessors to the operation were complete. System action: The ready list is displayed. User response: Reset can be done when all predecessors to the OSEQ operation are complete.
EQQR652E EQQR658E EQQR652E A DUPLICATE TABLE NAME WAS ENCOUNTERED IN THE SAME JCL LINE Explanation: The same table name was encountered twice in an OPC SEARCH directive. System action: None. Problem determination: Investigate the TME 10 OPC message log. Look for message EQQJ501. User response: Contact your system programmer. System programmer response: Check the OPC directive in the JCL for this operation.
EQQR659E EQQR665E EQQR659E A SUBSTITUTION CAUSED A STRUCTURAL CHANGE IN AN OPC DIRECTIVE Explanation: Variable substitution has caused at least one of these changes: An OPC directive has been created. The type of an OPC directive has changed. The keywords of an OPC directive have changed. An OPC directive has changed to another line type. System action: The system waits for you to respond. User response: Use the S row command to see if there is any help for the current variable.
EQQR666E EQQR671E EQQR666E AN ABEND HAS OCCURRED IN A SUBSTITUTION USER EXIT Explanation: The user module caused an ABEND, from which TME 10 OPC recovered. System action: The system waits for you to respond. User response: Contact your system programmer. System programmer response: Check the TME 10 OPC message log and look for message EQQJ515. EQQR667E AN UNRECOVERABLE ABEND HAS OCCURRED IN A SUBSTITUTION USER EXIT Explanation: The user module caused an ABEND, from which TME 10 OPC could not recover.
EQQR672E EQQR675E EQQR672E A USER EXIT DEFINED WILL NOT BE CALLED. IT IS NOT EXECUTABLE Explanation: An exit is referred to in variable substitution or JCL tailoring. TME 10 OPC has previously discovered an abend in this exit and marked it as not executable. This exit will not be called again. System action: The system waits for you to respond. User response: Contact your system programmer. System programmer response: Correct the exit, and restart TME 10 OPC to use the exit again.
262 TME 10 OPC Messages and Codes
EQQSU01I EQQSU06E Chapter 23. EQQSUnn Messages EQQSU01I THE SUBMIT TASK HAS STARTED Explanation: The submit task has successfully completed initialization. System action: Submit task processing starts. User response: None. EQQSU02I THE SUBMIT TASK HAS ENDED Explanation: The submit task has terminated processing normally. An operator has stopped the submit task, or the TME 10 OPC subsystem has stopped. System action: The submit task processing terminates. User response: None.
EQQSU07E EQQSU12I EQQSU07E THE SUBMIT TASK ABENDED WHILE PROCESSING THE FOLLOWING REQUEST: REQUEST Explanation: An abend prevented the submit task from processing a queue element. System action: MVS recovery/termination is requested to generate a dump. The submit task attempts to continue normal processing. Problem determination: Review the TME 10 OPC message log dataset and the dump dataset to determine the cause of the problem.
EQQSU13E EQQSU21E EQQSU13E THE OPC/ESA STARTED TASK FILE, DDNAME=EQQSTC, COULD NOT BE OPENED FOR OUTPUT Explanation: The submit task was unable to open the started task temporary proclib dataset. This file is defined by the DD statement EQQSTC in the JCL procedure used to start the TME 10 OPC subsystem. System action: If the error is discovered during the start of TME 10 OPC, the submit task issues message EQQSU04 and terminates.
EQQSU22E EQQSU24W EQQSU22E UNABLE TO ACCESS THE EQQEVDS FILE FOR REQUEST TYPE DQETYPE ON WORKSTATION WSNAME Explanation: The submit task was unable to execute a submit checkpoint request for the reason stated. Request type can be one of: J0 J1 J2 WTO Request for submit checkpoint sequence number Job submit checkpoint request STC start checkpoint request Message checkpoint request System action: The submit task continues normal processing.
EQQS000E EQQS005E Chapter 24. EQQSnnn Messages EQQS000E YOU DO NOT HAVE AUTHORITY TO ACCESS THE QUERY CP DIALOG Explanation: You have attempted to access the Query Current Plan dialog, but you are not authorized to access it. System action: The request is rejected and the system waits for you to respond. User response: Contact your security administrator to get access to the Query Current Plan dialog.
EQQS100E EQQS107E EQQS100E THE ONLY VALID VALUES ARE OCHCYES AND OCHCNO Explanation: An attempt was made to specify an invalid value in the AVAIL column. System action: The system waits for you to respond. User response: Enter a correct value in the AVAIL column. EQQS101E YOU ARE NOT AUTHORIZED TO MODIFY SPECIAL RESOURCES Explanation: To display an TME 10 OPC panel where special resources can be modified, you need update authority to the SR resource. You do not have this authority.
EQQS300E EQQS309E EQQS300E PRIORITY MUST BE A NUMBER FROM 1 - 9 Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQS301E THE MCP ADDED INDICATOR MUST BE OCHCYES OR OCHCNO Explanation: Data entry error; see “Data Entry Errors” on page 2. ochcyes is the national language character for 'Y' (yes); ochcno is the national language character for 'N' (no). EQQS302E THE RERUN INDICATOR MUST BE OCHCYES OR OCHCNO Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQS400I EQQS402E EQQS400I NO ENTRIES WERE SELECTED FOR THE LIST Explanation: A request for a list of records resulted in an empty list. Either there were no records that matched the selection criteria or you were not authorized to access those that were found. System action: None. User response: None. EQQS401I NO OPEN INTERVAL SPECIFIED IN THE WORK STATION DEFINITION Explanation: The workstation description in the current plan has no open interval. System action: None. User response: None.
EQQTT01I EQQTT05E Chapter 25. EQQTTnn Messages EQQTT01I THE TCP/IP COMMUNICATION TASK HAS STARTED Explanation: The TCP/IP communication task has successfully completed initialization. System action: The TCP/IP communication task processing continues. User response: None.
EQQTT06E EQQTT09E EQQTT06E A SEVERE ERROR IN THE TCP/IP COMMUNICATION TASK HAS CAUSED ONE OR MORE REQUESTS TO BE LOST Explanation: The TCP/IP communication task encountered an error processing elements on the TATQ. As a result, at least one queue element has been lost. System action: MVS/ESA recovery/termination is requested to generate a dump. The TCP/IP communication task attempts to continue normal processing.
EQQTT10E EQQTT14I EQQTT10E THE TCP/IP COMMUNICATION TASK ENCOUNTERED AN ERROR WHILE PROCESSING A REQUEST REQUEST Explanation: An error was encountered when the TA communication task attempted a REQUEST TCP/IP socket call. System action: If any of INIT, BIND, GHID, or LSTN request the TA task will terminate. Any other request type will cause the TA task to close the session with the corresponding tracker. The session will then be reestablished.
EQQTT15I EQQTT19W EQQTT15I THE TCP/IP COMMUNICATION TASK HAS BEEN UNABLE TO ESTABLISH A CONNECTION TO THE TCP/IP ADDRESS SPACE FOR THE LAST 200 SECONDS Explanation: The TCP/IP communication task is attempting to establish a connection to the TCP/IP started task after a restart. Attempts are made every 20th second. The message is issued every 10th attempt. System action: The TCP/IP communication task processing continues. User response: None.
EQQT002E EQQT015I Chapter 26. EQQTnnn Messages EQQT002E END DATE FOR PRINTOUT MUST BE SPECIFIED Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQT003W ENTER END AGAIN TO LEAVE OR PRESS ENTER TO PRINT Explanation: Enter END again to leave without initiating a printout, or press ENTER to initiate the printout. System action: The system waits for you to respond. User response: Enter END again or press ENTER.
EQQT016E EQQT024E EQQT016E CALENDAR ID IS NOT SPECIFIED Explanation: A calendar ID must be given. System action: None. User response: Enter the calendar ID you need. EQQT017I A CALENDAR HAS BEEN UPDATED Explanation: This confirms that a calendar has been updated, and the database was updated accordingly. System action: None. User response: None. EQQT018E CALENDAR CALENDAR NOT CREATED - MAXIMUM NUMBER EXCEEDED Explanation: The maximum number of calendars, 32768, has been exceeded.
EQQT025E EQQT106I EQQT025E WORK DAY END TIME MUST BE SPECIFIED Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQT026E SPECIFY A VALID DAY OR DATE IN USER DEFINED FORMAT Explanation: A valid week day or specific date must be given in the user specified format. EQQT030E END DATE MUST BE LESS THAN FOUR YEARS FROM CURRENT DATE Explanation: You specified a time span, from current date to end date, that exceeded four years. System action: The system waits for you to respond.
EQQT108E EQQT121E EQQT108E PERIOD PERIOD NOT CREATED - ALREADY EXISTS Explanation: The calendar period PERIOD you specified could not be created because it already exists in the calendar database. System action: The system waits for you to respond. User response: Enter a unique period name. If you want to create versions of an already existing period, you should use the copy function. EQQT110E LIST OF ORIGIN DATES CONTAINS DUPLICATES Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQT122E EQQT307E EQQT122E NON-CYCLIC PERIOD INTERVAL END DATE MUST NOT PRECEDE ORIGIN DATE Explanation: The interval end date is prior to the associated origin date. System action: The request is rejected. User response: Change the interval end date, or the interval origin date, so that the interval end date is later than the interval origin date.
280 TME 10 OPC Messages and Codes
EQQU000E EQQU044I Chapter 27. EQQUnnn Messages EQQU000E YOU ARE NOT AUTHORIZED TO USE FUNCTION UUFUNC Explanation: You have attempted to use function uufunc but you are not authorized to do so. System action: The request is rejected. User response: Contact your security administrator if you want to use uufunc. EQQU005I THE REQUEST TO UUFUNC OF UUUSUBS IS HANDLED Explanation: This confirms that your request has been processed. System action: The requested action is carried out. User response: None.
282 TME 10 OPC Messages and Codes
EQQV000E EQQV005E Chapter 28. EQQVnnn Messages EQQV000E DUPLICATE NAMES IN THE ROUTOPTS SNA DESTINATIONS Explanation: At least one name in the SNA keyword destination list in the ROUTOPTS init statement is a duplicate of an already specified name. These names are the application names of potential session partners and must be unique. System action: NCF processing is terminated. System programmer response: Correct the name(s) in error and then restart the subsystem.
EQQV006I EQQV012E EQQV006I NCF APPLICATION ENDED Explanation: NCF processing has completed and control is returned to the TME 10 OPC subsystem. System action: NCF processing is terminated. User response: None. EQQV007E INITIALIZATION FAILED - SNA DESTINATION NOT SPECIFIED IN ROUTOPTS Explanation: In a controller system, NCF initialization processing failed because no partner application IDs were specified in the SNA keyword in the ROUTOPTS statement. System action: NCF processing is terminated.
EQQV013E EQQV016E EQQV013E ACB EXLST BUILD PROCESSING FAILED - R15 = R15 R00 = R00 Explanation: The GENCB macro request issued to generate a ACB EXLST block did not complete normally. System action: NCF processing is terminated. Problem determination: Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this MVS/ESA system.
EQQV017E EQQV022E EQQV017E NAMEREQ REQUEST FAILURE - LU/APPLICATION NODE NOT ACTIVE Explanation: The VTAM NAMEREQ request failed to complete successfully because the LU-name NODE was not active. System action: NCF processing is terminated. System programmer response: Investigate why NODE suddenly became inactive. Restart NCF when NODE is active again. EQQV018E NAMEREQ REQUEST FAILURE - VTAM ERROR, OR NCP/VTAM .
EQQV023E EQQV028W EQQV023E LOGON REQUEST FOR LU/APPLICATION LU THAT IS ACTIVE - CLSDST ISSUED Explanation: A session establishment attempt is made from a remote NCF application that is already in session with the TME 10 OPC host NCF application. This message is only issued for a NCF application at an TME 10 OPC host. System action: The request for a session is turned down, and NCF processing continues.
EQQV029I EQQV037I EQQV029I VTAM TERMINATION, OR NCF DEACTIVATION, STOPPED SESSION SETUP ATTEMPTS Explanation: Session initiation attempts were stopped because VTAM is terminating, or the NCF application was deactivated. System action: NCF continues termination processing. User response: None. EQQV031I SUBSYSTEM STOP REQUEST TERMINATED SESSION SETUP ATTEMPTS Explanation: A remote NCF application was in the process of initiating a session when the subsystem was stopped.
EQQV038E EQQV043E EQQV038E DESTINATION LU INCONSISTENTLY SPECIFIED Explanation: A destination that runs TME 10 OPC NCF has been specified on the ROUTOPTS initialization statement OPCAV1R2 keyword. System action: NCF processing continues. System programmer response: Correct the ROUTOPTS initialization statement keyword OPCAV1R2 and restart TME 10 OPC.
EQQV044E EQQV045E EQQV044E OPNDST FAILURE WHEN CONFIRMING SESSION WITH TRACKER 'LU' Explanation: The OPNDST macro issued to confirm session establishment between the NCF controller and a remote tracker failed. The most likely reason for the failure is that there is no active route back to the tracker from the controller node, or that the VTAM environment of the tracker requesting the session is going down.
EQQWL10W EQQWL15I Chapter 29. EQQWLnn Messages EQQWL10W WORK STATION WSID, HAS BEEN SET TO STAT STATUS Explanation: The status of a workstation has changed. An authorized user may have changed the status. This message may also be caused by a system failure or by a workstation becoming available again. System action: The status of the workstation is changed. This may effect the ongoing work.
EQQWL21W EQQWL30E EQQWL21W EVENT EVENT IGNORED FOR WORK STATION WSID Explanation: An event has been received that is not possible because of the status of the workstation. You cannot change the status of a workstation to the status that it already has. For example, if a workstation already has failed status, a failure event will produce this message. System action: The event is ignored. The workstation status does not change. User response: Verify that the TME 10 OPC status of the workstation is correct.
EQQWL31E EQQWL40W EQQWL31E REROUTE ATTEMPT OF OPERATION NAMED OP, WITH APPL IA APPL FAILED Explanation: Rerouting could not be performed for this operation. Either reroute parameters are incorrect, or an offline or failure situation caused TME 10 OPC to try to reroute an operation that is not reroutable. System action: The operation remains in the current status. If the workstation that this operation uses is not active, the operation is not started.
294 TME 10 OPC Messages and Codes
EQQW000E EQQW006E Chapter 30. EQQWnnn Messages EQQW000E NO AUTHORITY TO ACCESS THE WORK STATION DESCRIPTION Explanation: You have attempted to access the workstation description database, but you are not authorized to access it. Or, you do not have access authority to at least one of the following TME 10 OPC resources that are used together with the workstation description database: the application description database, the calendar database, or the operator instruction database.
EQQW007E EQQW013E EQQW007E UNABLE TO READ WORK STATION DESCRIPTION RECORD Explanation: The workstation description record could not be read because it may have been deleted by another user, or an error in the workstation description database made it impossible to read the record. System action: The system waits for you to respond. User response: Go back to the previous panel and try again. If the error persists, contact your system programmer. System programmer response: Contact your IBM representative.
EQQW014E EQQW017E EQQW014E THE JCC TASK ABENDED WHILE PROCESSING THE FOLLOWING EXIT RECORD: EXITREC Explanation: An abend prevented the JCC from processing all SYSOUT datasets for a batch job. System action: MVS recovery/termination is requested to generate a dump. The JCC attempts to continue normal operation with the next ending job. The current job is put on the ended-in-error list with an error code of JCCE.
EQQW018E EQQW023E EQQW018E SYSOUT CLASS CLASS IS ALREADY BEING PROCESSED BY ANOTHER JCC TASK Explanation: A JCC task has been requested to process SYSOUT datasets in a SYSOUT class that is already being processed by another JCC subtask on the same MVS system. The SYSOUT class can only be processed by one JCC subtask at a time. System action: JCC initialization is terminated. Problem determination: The JCC subtask is started when either JCCTASK(YES) or CATMLVL(step) is defined in the OPCOPTS statement.
EQQW024E EQQW027E EQQW024E THE EVENT WRITER ABENDED WHILE PROCESSING THE FOLLOWING EXIT RECORD: EXITREC Explanation: An abend prevented the event writer from writing an event record to the event dataset. System action: MVS recovery/termination is requested to generate a dump. The event writer attempts to continue normal operation with the next event queued. Problem determination: Review the SYSLOG dataset, the TME 10 OPC message log, and the dump dataset to determine the cause of the error.
EQQW028E EQQW032E EQQW028E JOB COMPLETION CHECKER INITIALIZATION FAILED Explanation: The JCC could not acquire all resources required for normal operation. The most likely cause of this error is that the JCC message library could not be opened or that the library is incorrectly defined. It is also possible that there was an error in the JCCOPTS statement. System action: JCC processing is terminated. Message EQQZ045W is issued.
EQQW033W EQQW038I EQQW033W JOB JOBNAME(JOBNUM) WILL NOT BE RELEASED. REPEATED RETRIES HAVE FAILED Explanation: The event writer has received a release command on a submit/release dataset and was not able to release job JOBNAME(JOBNUM) from hold status. System action: No more attempts to release the job are made. The event writer processing continues. Operator response: Determine the current status of the job. If necessary, release the job manually.
EQQW039E EQQW044E EQQW039E JCC FOUND BAD HEXADECIMAL VALUE BETWEEN COLUMNS BCOL AND ECOL IN MEMBER MEMBER IN THE EQQJCLIB MESSAGE TABLE FILE. INCORRECT RECORD FOLLOWS: MSGREC Explanation: A message table record contains invalid information and cannot be used. System action: The JCC will not use the incorrect message library member. If the member name is EQQGJCCT, message EQQW063E is issued. In all other cases, the JCC continues processing.
EQQW045W EQQW049E EQQW045W JCL BATCH WITH FIRST JOB JOBNAME WILL NOT BE SUBMITTED BECAUSE SUBMIT RECORDS WERE RECEIVED IN INCORRECT ORDER BY THE EVENT WRITER Explanation: The event writer found job submit records in a submit/release dataset that could not be processed because the records were not in sequence. System action: The event writer continues reading the submit/release dataset. Problem determination: Check that only one TME 10 OPC system is updating this submit/release dataset.
EQQW051E EQQW055I EQQW051E JOB JOBNAME COULD NOT BE SUBMITTED. REASON: AUTHORITY FOR RUSER USER, SUPPLIED BY USER EXIT EQQUX001, COULD NOT BE DETERMINED Explanation: A user ID was supplied by the submit exit, EQQUX001, and the job was then sent using the submit/release dataset to the DRVP macro. The buffer pool was successfully built. System action: The job is not submitted and normal TME 10 OPC processing continues.
EQQW056I EQQW063E EQQW056I JOBNAME JOBNUM HAS NO HELD SYSOUT IN CLASS CLASS Explanation: The CATMCLAS keyword specifies the SYSOUT class CLASS, but job JOBNAME with job ID JOBNUM created nonheld output in this class. System action: The job is tracked as normal, but the joblog cannot be sent to the controller. Problem determination: If the joblog output for the job is a held SYSOUT class, ensure the most current EQQSSCMC lmod is active (see the SSCMNAME parameter).
EQQW064E EQQW069E EQQW064E THE JOB COMPLETION CHECKER WAS UNABLE TO BUILD THE JOB MESSAGE TABLE FOR JOB JOBNAME(JOBNUM) Explanation: An error occurred while processing the JCC message table for the specified job. The job message table is defined by member JOBNAME in the library defined by the EQQJCLIB DD statement. System action: An incident record is written to the JCC incident log and the job is flagged as having encountered a JCC error.
EQQW070I EQQW074E EQQW070I THE EW CANNOT REPOSITION AT RESTART POSITION: CYC REC Explanation: An event writer is started in event reader mode (with an EWSEQNO). The event writer cannot position on the event dataset with the event dataset position that it has received. The restart position was probably overwritten when the event dataset wrapped around. System action: The event writer continues processing as normal. TME 10 OPC administrator response: The event dataset may be too small.
EQQW075W EQQW101E EQQW075W THE HEADER RECORD IN FILE DDNAME IS INCOMPATIBLE WITH THE DEVICE TYPE Explanation: The information in the header record does not match the calculated records per tracks value. This is normally caused by moving the dataset to a different device type. Note: This message may be issued if you have reallocated the data set using a method that does not put an end of file at the beginning of the data set. It can then be ignored. System action: The dataset is reformatted.
EQQW102E EQQW111E EQQW102E WORK STATION REPORTING ATTRIBUTE INVALID OR NOT DEFINED Explanation: Data entry error; see “Data Entry Errors” on page 2. Valid workstation reporting attributes are: A Automatic. Reporting is done by a user program for both start and completion of an operation (for example, a computer workstation). S Manual start and completion. The workstation operator reports when work is started and when it is completed (for example, a data entry workstation). C Manual completion only.
EQQW112E EQQW206E EQQW112E A PLANNING ATTRIBUTE IS REQUIRED, SPECIFY EITHER Y OR N Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQW113E A CONTROL ATTRIBUTE IS REQUIRED, SPECIFY EITHER Y OR N Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQW114E WORK STATION OPEN INTERVAL INVALID OR NOT DEFINED Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW207E EQQW215E EQQW207E CAPACITY OF PARALLEL SERVERS INVALID OR NOT DEFINED Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQW208E RESOURCE CAPACITY IS NOT DEFINED OR IT IS INVALID Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQW209E THE STANDARD DAY CANNOT BE CLOSED Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW216E EQQW306E | EQQW216E ACCESS METHOD CAN BE SET ONLY IF WORKSTATION TYPE IS 'COMPUTER' | Explanation: You specifed an access method name. Access method is supported only for "Computer" workstations. | System action: Processing continues. TME 10 OPC waits for your next input. | User response: Supply a valid workstation type. | EQQW217E PORT NUMBER MUST BE NUMERIC AND IN THE RANGE 0-32760 | Explanation: You specified a port number value that was not numeric or was greater than 32760.
EQQW307E EQQW405E EQQW307E SPECIFIED FROM-TIME LATER THAN TO-TIME Explanation: Data entry error; see “Data Entry Errors” on page 2. User response: Specify a to-time that is later than the from-time. EQQW308E DUPLICATE WORK STATION CLOSED DATES EXIST IN TABLE Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW406E EQQW503I EQQW406E STARTED TASK OPTION INVALID OR NOT DEFINED Explanation: Data entry error; see “Data Entry Errors” on page 2. The option can be Y (yes) or N (no). EQQW407E WTO OPTION INVALID OR NOT DEFINED Explanation: Data entry error; see “Data Entry Errors” on page 2. The option can be Y (yes) or N (no). EQQW500E THE OPC/ESA JCL LIBRARY, DDNAME EQQJBLIB, COULD NOT BE OPENED Explanation: TME 10 OPC could not open the JCL library (ddname EQQJBLIB) to read a member.
EQQW505I EQQW511E EQQW505I THE WORK STATION ANALYZER TASK HAS STARTED Explanation: The initialization of the workstation analyzer has completed and the workstation analyzer is about to start processing. System action: TME 10 OPC processing continues. System programmer response: None.
EQQW512E EQQW517E EQQW512E WS ANALYZER WAS UNABLE TO READ OR UPDATE CURRENT PLAN OPERATION RECORD WITH KEY (HEXADECIMAL): F0F3OPRINDEX Explanation: The workstation analyzer encountered a VSAM error when reading or updating the current plan dataset. System action: The workstation analyzer continues normal processing with the next ready operation. Problem determination: Review earlier messages in the TME 10 OPC message log and SYSLOG datasets to determine the exact cause of this error.
EQQW518E EQQW522E EQQW518E THE EQQUX002 EXIT COULD NOT FIND JOB MEMBER IN ANY INPUT DATA SET Explanation: The workstation analyzer was attempting to submit a job to JES for a ready operation on a computer workstation. However, no JCL for this operation is saved in the JCL repository dataset, and the joblib I/O exit could not find the job in any input dataset. System action: The operation remains in ready status. TME 10 OPC assumes that some other function will submit the job to JES.
EQQW523E EQQW529E EQQW523E JOB MEMBER IN APPLICATION APPL IS TOO LARGE TO BE SAVED ON THE JS DATA SET Explanation: A job that is about to be submitted to JES is too large to be saved in the JCL repository dataset. System action: The job will be submitted but the JCL repository data will not be updated. Problem determination: Use the IDCAMS LISTCAT function to determine the maximum size of records in the dataset defined by the EQQJSxDS DD statement. Use dialog option 6.
EQQW532E EQQW750W EQQW532E THE WSA TASK IS TERMINATING DUE TO A SEVERE ERROR. REFER TO THE SYSMDUMP DATA SET FOR MORE INFORMATION Explanation: The Work Station Analyzer subtask has encountered a second severe error. System action: The Work Station Analyzer subtask terminates and a dump of the TME 10 OPC subsystem address space is generated. User response: Refer to the SYSMDUMP dataset to determine the cause of the error.
EQQW751E EQQW755W EQQW751E THE SUBMITTOR TASK GOT RC IN RETURN CODE FROM THE MGCR MACRO WHEN THE STC STCNAME WAS ABOUT TO BE STARTED Explanation: The submittor task cannot start this STC. The MGCR macro (SVC34) failed with the indicated return code in register 15. System action: The corresponding operation is set to ended-in-error with error code OSUB. System programmer response: Contact your IBM representative.
EQQW756W EQQW759W EQQW756W THE OPC/ESA STARTED TASK FILE, DDNAME = EQQSTC, IS NOT EMPTY Explanation: EQQSTC, the started task temporary proclib file, is not empty. System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs. Problem determination: Save the MLOG from the TME 10 OPC subsystem. Save the JCL from the failing job or started task. Run the AMASPZAP utility specifying ABSDUMP ALL on the dataset, and save the output.
EQQW760E EQQW762E EQQW760E AN I/O ERROR OCCURRED ON THE EQQSTC DATA SET WHEN THE SUBMITTOR TASK WAS WRITING THE JCL FOR STC STCNAME. THE SYNAD ERROR MESSAGE WAS: SYNMSG Explanation: The submittor task encountered an input/output error writing to EQQSTC, the started task temporary proclib file. A SYNAD error routine was given control and issued an error message. System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
EQQW763E EQQW766W EQQW763E AN ABEND OCCURRED WHEN THE SUBMITTOR TASK WAS STOWING THE MEMBER FOR STC STCNAME ON THE EQQSTC DATA SET. THE ABEND CODE WAS: ABCODE Explanation: The submittor task got an ABEND when stowing on EQQSTC, the started task temporary proclib file. An ABEND exit routine was given control and issued an ABEND code. System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs. The corresponding operation is set to status E.
EQQW767W EQQW770E EQQW767W THE EVENT CREATION ROUTINE DETECTED THAT THE IATUX29 WAS GENERATED AGAINST A JES3 LEVEL THAT DOES NOT MATCH THE CURRENT EXECUTING JES3 LEVEL Explanation: The level of the JES3 macros used to generate the TME 10 OPC IATUX29 does not match the level of the active JES3 system. System action: The event creation routine continues to create event records. The event records may contain invalid tracking information, causing the corresponding operation status to be inaccurate.
EQQW771W EQQW777W EQQW771W THE JCL FOR STC JOBNAME WILL NOT BE SUBMITTED BECAUSE SUBMIT RECORD IS TOO OLD Explanation: Started task JCL records in a submit/release dataset are older than the limit defined by the SKIPTIME and SKIPDATE keywords in the EWTROPTS statement. System action: The old records are not processed. The event writer continues to read the submit/release dataset. Operator response: Restart the corresponding operation, if necessary.
EQQW778W EQQW779I EQQW778W EQQEVDS DDNAME IS NOT PRESENT OR SPECIFIES DD DUMMY Explanation: The submittor task could not find the EQQEVDS DDNAME in the JCL for the TME 10 OPC address space, or the DDNAME specifies DD DUMMY. System action: The submittor task will not checkpoint submit requests, but will continue to submit jobs. System programmer response: It is not mandatory to run a TME 10 OPC address space with the EQQEVDS data set, i.e. when EWTRTASK(NO) is specified.
EQQX000E EQQX011E Chapter 31. EQQXnnn Messages EQQX000E XROW IS NOT A VALID ROW COMMAND Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX001E ZCMD IS NOT A VALID PRIMARY COMMAND Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX002E A ROW CANNOT BE SELECTED INSIDE A BLOCK THAT IS TO BE DELETED Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX012E EQQX023E EQQX012E Y MAY BE SET ONLY ONCE AND ONLY IN YY Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX013E MONTH MUST BE SPECIFIED AS MM IN THE DATE FORMAT Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX014E M MAY BE SET ONLY ONCE AND ONLY IN MM Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX015E DAY MUST BE SPECIFIED AS DD OR DDD IN THE DATE FORMAT Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX024E EQQX038E EQQX024E MONTH MUST BE 01 - 12 Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX025E DAY IS NOT COMPATIBLE WITH MONTH AND YEAR Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX026E HOUR MUST BE 00 - 24 Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX027E MINUTE MUST BE 00 - 59 Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX039E EQQX049E EQQX039E HILITE ATTRIBUTE MUST BE ONE OF THOSE LISTED ON THE PANEL Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX040I THE JOB HAS BEEN SUBMITTED FOR SUBFUNC Explanation: The job has been submitted. System action: Normal processing continues. User response: None. EQQX041E THE NAME SPECIFIED FOR THE SYSOUT DATA SET IS INVALID Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX100E EQQX114E EQQX100E ONLY ONE ROW COMMAND CAN BE SPECIFIED ON THIS PANEL Explanation: It is not allowed to specify more than one row command on this panel. System action: The system waits for you to respond. User response: Enter the RESET command to remove all row commands, and then enter one row command.
EQQX115E EQQX118E EQQX115E TSO SERVICE FACILITY RC: XSSRC, RSNC: XSSRS, ABEND: XSSAB Explanation: The TSO Service facility, IKJEFTSR, which is used for communication between the dialog and the TME 10 OPC subsystem, gave an error return code. The field RC gives the IKJEFTSR return code (XSSRC): 8 Confirms that the requested function is terminated as a result of the user pressing ATTN (attention).
EQQX119E EQQX124E EQQX119E LOGOFF REQUEST REJECTED, USER IS NOT LOGGED ON Explanation: You have attempted to disconnect a session from TME 10 OPC, but you were not connected. System action: None. User response: You can determine why you are logged off in the TME 10 OPC message log. (TME 10 OPC has been stopped and restarted since you logged on.
EQQX125E EQQX133E EQQX125E YOU ARE ALREADY CONNECTED TO OPC/ESA Explanation: You have attempted to connect your session to TME 10 OPC again but you are already connected to TME 10 OPC. System action: The system waits for you to respond. User response: Log off from TSO and then log on again. If the problem persists, contact your system programmer. System programmer response: Ensure that the correct load module library is accessed and that the dataset contains the correct version of the TME 10 OPC modules.
EQQX134E EQQX139E EQQX134E REQUESTED SERVICE IS CURRENTLY NOT AVAILABLE Explanation: Your request to use the general service function could not be granted because the general service subtask is not active. System action: The request is rejected. User response: Contact your system programmer. System programmer response: Review the TME 10 OPC message log to determine why the general service subtask is not active.
EQQX140E EQQX144E EQQX140E REMAINING STORAGE NOT ENOUGH TO OPEN LOGICAL VSAM FILE Explanation: Your request to use the general service function failed because the remaining storage is not enough to open a logical VSAM file. System action: The request is rejected. User response: Try again. If the error persists, contact your system programmer. System programmer response: Allocate a larger region to the TME 10 OPC subsystem and then restart the subsystem.
EQQX145E EQQX153E EQQX145E THE SUBSYSTEM PROGRAM IS NOT OF THE CORRECT RELEASE Explanation: The dialog or TME 10 OPC batch program is from a later release of TME 10 OPC than the TME 10 OPC subsystem. TME 10 OPC checks that the subsystem name specified in your dialog or in the SUBSYS parameter of the BATCHOPTS batch initialization statement (or its default) matches the name of one of your TME 10 OPC subsystems.
EQQX161E EQQX198E EQQX161E AN INTERNAL OPC/ESA CONTROL BLOCK IS IN ERROR Explanation: An internal TME 10 OPC control block is in error. System action: The system waits for you to respond. User response: Contact your system programmer. System programmer response: Ensure that the correct load module library is accessed and that the dataset contains the correct version of the TME 10 OPC modules.
EQQX220E EQQX259E EQQX220E THE INPUT ENTERED IS TOO LONG Explanation: Data entry error; see “Data Entry Errors” on page 2. The longest value accepted is HH.MM, where: HH MM The hour, in the range 00–24 The minute EQQX226E HOUR PART OF DURATION MUST BE A NUMBER BETWEEN 0 AND 99 Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX227E OPERATION DURATION MUST BE GREATER THAN 00.00 Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX260E EQQX264E EQQX260E AN INTERNAL CONTROL BLOCK IS IN ERROR: REASON CODE XSSRS Explanation: Validation checking of the data received as input to a routine has detected a damaged control block. Reason code XSSRS provides debugging information. Reason code 102 is given when the dialog code is of an earlier release than the TME 10 OPC subsystem code. System action: The request is rejected.
EQQX265E EQQX268W EQQX265E ATTEMPT TO READ A RECORD FAILED, REASON CODE XSSRS Explanation: The attempt to read a record failed. Reason code XSSRS provides debugging information for IBM personnel. System action: The request is rejected. User response: Contact your system programmer. System programmer response: Review the TME 10 OPC message log and look for I/O error messages issued at the time of the request. Correct all errors and then restart the TME 10 OPC subsystem.
EQQX269E EQQX300E EQQX269E THE LTP DATA SET IS BEING USED BY A BATCH FUNCTION, TRY LATER Explanation: You cannot access the long-term plan dataset because it is being used by a batch function. System action: The request is rejected. User response: Try again later. EQQX270E THE JS DATA SET IS IN USE, TRY LATER Explanation: You have requested a function that requires access to the JCL repository file, but this file is not available at the moment. System action: The request is rejected.
EQQX301E EQQX304E EQQX301E THE DB RECORD VERSION VERS IS INVALID Explanation: The version of the record is invalid. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Contact your system programmer. System programmer response: Review the TME 10 OPC message log to determine the cause of the error.
EQQX305E EQQX309E EQQX305E THE RUN CYCLE POINTER IS INVALID Explanation: The pointer to the next run cycle is invalid. All run cycles must be before the first operation in the application description record. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Contact your system programmer.
EQQX310E EQQX313E EQQX310E OFFSET TO NEXT OPERATION IN RECORD IS INVALID Explanation: The offset to next operation in the application description record is invalid. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Contact your system programmer.
EQQX314E EQQX317E EQQX314E AUTHORIZATION GROUP AUTHGR IS INVALID Explanation: Authorization group field contains invalid characters. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Enter a valid authorization group name and if the error occurred in batch, resubmit the job.
EQQX318E EQQX321E EQQX318E APPLICATION PRIORITY PRIO IS INVALID OR MISSING Explanation: No or an invalid application priority was entered. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Enter a valid application priority and if the error occurred in batch, resubmit the job.
EQQX322E EQQX325E EQQX322E OFFSET TO FIRST RUN CYCLE IS INVALID IN AD AD Explanation: The offset to the first run cycle is invalid in the indicated application description record. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Contact your system programmer.
EQQX326E EQQX329E EQQX326E THE CALENDAR CALID DOES NOT EXIST Explanation: The calendar ID entered does not exist in the calendar database. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job.
EQQX330E EQQX333E EQQX330E A POSITIVE RUN DAY OFFSET IS NOT BLANK OR NUMERIC 1 - 999 Explanation: The positive run day offset entered is not blank or a number from 1 to 999. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Enter a valid offset and if the error occurred in batch, resubmit the job.
EQQX334E EQQX337E EQQX334E INVALID RELATIVE DEADLINE DAY DLINER, MUST BE NUMERIC 0 - 99 Explanation: The relative deadline day entered is not a number from 0 to 99. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Enter a valid relative day and if the error occurred in batch, resubmit the job.
EQQX338E EQQX341E EQQX338E INVALID OPERATION NUMBER OP IN AD AD Explanation: The indicated operation number is invalid in the indicated application description. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Enter a valid operation number and if the error occurred in batch, resubmit the job.
EQQX342E EQQX345E EQQX342E ERROR TRACKING INDICATOR OF WS OP IS INVALID, AEC, MUST BE Y or N Explanation: The error tracking indicator is not Y (yes) or N (no). System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Enter a valid value and if the error occurred in batch, resubmit the job.
EQQX346E EQQX349E EQQX346E DEADLINE DAY OF WS OP IS INVALID, DLINER, MUST BE 0 - 99 Explanation: The relative deadline day of the indicated operation is invalid. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Enter a valid day and if the error occurred in batch, resubmit the job.
EQQX350E EQQX353E EQQX350E NUMBER OF INTERNAL PREDECESSORS NOINPR INVALID IN WS OP Explanation: The number of internal predecessors is invalid in the operation part of the application description record for the indicated operation. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Contact your system programmer.
EQQX354E EQQX357E EQQX354E WORK STATION PREIWS IS INVALID AS A PREDECESSOR TO WS OP Explanation: The indicated internal predecessor workstation could not be found in the workstation description database. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Check the entered data and correct the error.
EQQX358E EQQX361E EQQX358E INVALID AD PREAD IN THE PREDECESSOR FOR WS OP Explanation: The indicated external predecessor application description could not be found in the AD database. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Check the entered data and correct the error.
EQQX362E EQQX365E EQQX362E SPECIAL RESOURCE NAME IS BLANK IN OPERATION WS OP Explanation: The special resource name for the indicated operation is blank. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Enter a special resource name and if the error occurred in batch, resubmit the job.
EQQX366E EQQX369E EQQX366E A PREDECESSOR TO OPERATION WS OP DOES NOT EXIST Explanation: One predecessor for the indicated operation could not be found in the application description record. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error.
EQQX370E EQQX373E EQQX370E JOB SETUP OPERATION WS OP HAS NOT A PROCESSOR SUCCESSOR Explanation: The job setup operation indicated does not have a processor successor. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job.
EQQX374E EQQX377E EQQX374E WS OP HAS A PREDECESSOR WITH A DIFFERENT JOBNAME Explanation: The indicated print operation has a predecessor with a different job name. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Correct the job name and if the error occurred in batch, resubmit the job.
EQQX378E EQQX381E EQQX378E APPLICATION DESCRIPTION AD HAS NO WS WORK STATION Explanation: The indicated workstation does not exist in the indicated application description. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Check the entered data and correct the error.
EQQX382E EQQX385E EQQX382E APPLICATION ID AD IS NOT BRACKETED DBCS Explanation: The application identification field is specified to be in DBCS format, which means that it should start with a shift-out (X'0E') character and end with a shift-in (X'0F') character. Either shift-out or shift-in or both are missing. System action: The data is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information.
EQQX386E EQQX389E EQQX386E OWNER ID OWNER CONTAINS UNPAIRED SHIFT-OUT / SHIFT-IN CHAR Explanation: The owner identification field contains one or more superfluous shift-out or shift-in characters. System action: The data is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the failing record and the position of the error. User response: Correct the data and reenter. If the error occurred in batch, resubmit the job.
EQQX390E EQQX393E EQQX390E THE APPLICATION ID WAS NOT SPECIFIED Explanation: No data has been entered in the application identification field. System action: An empty field is not accepted. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the failing record and the position of the error. User response: Correct the data and reenter. If the error occurred in batch, resubmit the job.
EQQX394E EQQX397E EQQX394E ALL SPECIAL RESOURCES IN AN OPERATION MUST BE UNIQUE Explanation: A special resource must have a unique name in an operation. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Check for misspellings or delete the duplicate entry. If the error occurred in batch, resubmit the job.
EQQX398E EQQX401E EQQX398E DUPLICATE POSITIVE RUN DAY OFFSETS WERE FOUND IN A RUN CYCLE Explanation: All positive run day offsets must be unique in a run cycle. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Delete the duplicates and if the error occurred in batch, resubmit the job.
EQQX402E EQQX405E EQQX402E WORK DAY END TIME IS INVALID OR MISSING Explanation: Work day end time must be a value of '0000' to '2400' where the first two characters represent the hour, and the last two characters represent the minutes. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Correct the time and retry.
EQQX406E EQQX409E EQQX406E A WEEK DAY IN CALENDAR IS INVALID Explanation: For a week day, the second character in the variable section is blank. The first character has a value of 1 to 7 which corresponds with Monday to Sunday. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Correct the day and retry.
EQQX410E EQQX413E EQQX410E SPECIFIC DATES IN CALENDAR ARE NOT IN ASCENDING ORDER Explanation: Specific dates are not correctly sorted. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Correct the sequence and retry. If you cannot find a valid reason for the error, contact your system programmer.
EQQX414E EQQX419E EQQX414E START TIME IS MISSING FOR WS OP Explanation: An operation input arrival time must be specified if the operation is time dependent. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the record and the position of the error. User response: Enter a start time and if the error occurred in batch, resubmit the job.
EQQX420E EQQX424E EQQX420E REQUEST TYPE REQ IS NOT SUPPORTED Explanation: An internal parameter list, consisting of a sequence of control blocks, is validated and found to have an invalid request type. System action: If this is a request to the program interface function, the request is rejected and control is returned with the return code set to error. Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks.
EQQX425E EQQX429E EQQX425E THE REQUEST CONTAINS INCONSISTENT APPLICATION IDS, AD and RAD Explanation: In the program interface request an application description is given by the data area parameter. The ID of an application is also given by the arguments parameters. The data area application description ID differs from the ID given by the arguments. System action: If this is a request to the program interface function, the request is rejected and control is returned with the return code set to error.
EQQX430E EQQX434E EQQX430E THE PREDECESSOR APPLICATION ID IS REQUIRED BUT NOT AVAILABLE Explanation: The predecessor application ID is a required parameter in the request. It is not specified. System action: If this is a request to the program interface function, the request is rejected and control is returned with the return code set to error. Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks validated when the error was detected.
EQQX435E EQQX440E EQQX435E ROW COMMAND IS NOT VALID FOR A PENDING APPLICATION Explanation: Calculate and Print run days (A) row command is valid only for application versions that are active. System action: Request is rejected. User response: Use these row commands against only active applications. EQQX436E NO RUNCYCLE OFFSETS HAVE BEEN DEFINED FOR RUNCYCLE PERIOD = RUNPER Explanation: An attempt was made to save an invalid application description record.
EQQX441E EQQX446E EQQX441E THE NAME OF THE ETT TRIGGER IS BLANK Explanation: The error is detected when you try to validate the record before writing it to the data base. System action: The request to write the record is rejected. Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further information. Current record is printed in the diagnostic file and the position of the invalid field in the record is given.
EQQX447E EQQX455E EQQX447E RESERVED FIELDS IN PERIOD RECORD MUST BE BLANK Explanation: The error is detected when you try to validate the record before writing it to the data base. System action: The request to write the record is rejected. Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further information. Current record is printed in the diagnostic file and the position of the invalid field in the record is given.
EQQX462E EQQX467E EQQX462E FIELD HIPERBATCH IS INVALID, MUST BE Y OR N System action: The request to write the record is rejected. Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further information. Current resource description is printed in the diagnostic file and the position of the invalid resource specification in the record is given. User response: Enter a valid Hiperbatch value. If the error occurred in batch, resubmit the job.
EQQX468E EQQX474E EQQX468E FIELD AVAIL IS INVALID IN INTERVAL IVLID. IT MUST BE Y, N OR BLANK Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC controller for further information. Current resource description is printed in the diagnostic file and the position of the invalid resource specification in the record is given. IVLID identifies the interval by the week day number (1–7), the standard day number (8) or a date, followed by the interval start time.
EQQX475E EQQX502E EQQX475E FIELD FROM TIME NOT EARLIER THAN TO TIME IN INTERVAL IVLID Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further information. Current resource description is printed in the diagnostic file and the position of the invalid resource specification in the record is given. IVLID identifies the interval by the week day number (1–7), the standard day number (8) or a date, followed by the interval start time.
EQQX503E EQQX604E EQQX503E INVALID DBCS-CHARACTER(S) IN GRPDEF Explanation: The group definition ID field contains out-of-range DBCS characters. With the exception of DBCS blank, X'4040', each byte must be in the range X'41' to X'FE'. System action: The data is rejected. Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file contains a copy of the failing record and the position of the error. User response: Specify a valid group definition ID.
EQQX605E EQQX612E EQQX605E SELECT ONE AND ONLY ONE OF THE LU NAME LINES Explanation: Only one of the entries in the subsystem name table can be selected by a / in the first column. System action: The system waits for you to respond. User response: If you are logged on to TSO on the MVS where the TME 10 OPC Controller is running, select the row with the Controller subsystem name and no Server LU name.
EQQX614E EQQX617E EQQX614E REQUEST FAILED, SEVERE ERROR AT SERVER LU Explanation: An error occurred at the Server preventing it from completing a service. System action: The dialog or program interface application cannot continue. System programmer response: Check the message log of the Server for a message explaining the error at the Server. User response: Check that the proper LU name is specified. For the dialog the LU name is set via the OPTIONS menu.
384 TME 10 OPC Messages and Codes
EQQY001I EQQY007W Chapter 32. EQQYnnn Messages EQQY001I STATEMENTS FOR AD AD PROCESSED SUCCESSFULLY Explanation: The statements for creating an application description have been received. Syntax checking has revealed no error. System action: Processing continues. User response: None. EQQY002I STATEMENTS FOR OI TO AD PROCESSED SUCCESSFULLY Explanation: The statements for creating an OI have been received. Syntax checking has revealed no error. System action: Processing continues. User response: None.
EQQY008W EQQY020W EQQY008W STATEMENT STM IS BYPASSED DUE TO PARSER DETECTED ERROR Explanation: The statement parser has detected an error in statement STM. System action: Processing continues. The creation of the current record is abandoned, and the remaining statements for the same record are bypassed. Problem determination: The parser-detected error is given by the preceding message. User response: Correct the error described by the previous message and rerun.
EQQY021E EQQY035E EQQY021E SUBSYS SUBS IS SPECIFIED IN OPTIONS STATEMENT, IT IS SET TO YSUBS IN THE INIT STATEMENT OF THE EQQYPARM FILE Explanation: Two different subsystem names are specified. System action: The record being created is considered in error and is not created. The following statements are scanned and validated. User response: Remove or change the SUBSYS parameter of the SYSIN file OPTIONS statement, or change the SUBSYS parameter of the EQQYPARM file INIT statement.
EQQY050E EQQY050E EQQY050E VALIDATION FAILED FOR: BLOCK, REASON: REASON, OFFSET: POS Explanation: The control block BLOCK, contains an error at offset: POS. System action: If this is a request to the program interface function, the request is rejected and control is returned with the return code set to error. Problem determination: The diagnostics file (ddname EQQDUMP) contains a dump of the failing control block.
EQQY106E EQQY108E 881 The dependency type is invalid; it must be S or P. 882 The dependency operation number is invalid; it must be 1–99. 883 The dependency application ID is invalid; the format is EBCDIC. 884 The dependency application ID is invalid; the format is DBCS. 885 The dependency input arrival date is not a valid date or is missing; it is required in an external dependency request.
EQQY109E EQQY201E EQQY109E KEYWORD KEY HAS AN UNAMBIGUOUS VALUE VAL Explanation: The value of the keyword KEY is abbreviated so that it matches more than one of the valid values. System action: The record being created is considered in error and is not created. The following statements adding details to the record are scanned for valid data types. User response: Correct the input file and resubmit the job. For more information about the keyword, refer to TME 10 OPC Planning and Scheduling the Workload.
EQQY202E EQQY209E EQQY202E TOO MANY VERSIONS, AD WITH KEY KEY IS NOT ADDED Explanation: When applications with the same application ID but different valid-from dates are specified, only four different dates can be specified. System action: The new application description is rejected. User response: Choose the versions you want and update accordingly.
EQQY211E EQQY223E EQQY211E TOO MANY SIGN START DAYS ENTERED, AT MOST NUM ARE ACCEPTED Explanation: The application can only be selected NUM times for one run cycle. System action: The application description is rejected. User response: Correct the input file and resubmit the job. If you need to select more days, repeat the run cycle the necessary number of times.
EQQY224E EQQY228E EQQY224E FAILED TO UPDATE KEY TO BE VALID UP TO VTO. REASON CODE RS Explanation: A new application description overlaps the validity period of an existing application description. You tried to adjust the validity of the existing version to the day before the new version becomes valid, but this update failed. There are two possible reasons as given by RS: The read of the application description to be updated, failed. The update write failed.
EQQY229E EQQY236E EQQY229E SETUP FOR OPERATION: POP IN APPLICATION: PID NOT COMPLETE Explanation: A SELECT JCLPREP was done without completion of the listed operation. System action: None. User response: Correct the error and resubmit the job. operation in the application matches the specification given in the message text. A blank means that no value is specified. System action: The application description is rejected. User response: Correct the input file and resubmit the job.
EQQY237E EQQY301E EQQY237E PROMPT VARIABLES HAVE NOT BEEN SET Explanation: You tried to perform an INSERT of JCLPREP. At least one of the required prompt variables has not been set. System action: The update of JCL variable values is rejected. User response: Check your program to see if it processes correctly. EQQY238E A GROUP DEFINITION CANNOT HAVE SPECIAL RESOURCES. KEY OF THE RECORD IS: KEY Explanation: A group definition cannot contain special resources.
EQQY302E EQQY702E EQQY302E LOGICAL RECORD SIZE OF OI MEMBER DATA SET, DDNAME EQQOIPDS, IS NOT VALID Explanation: The EQQOIPDS dataset must have a logical record length of 80. System action: No operator instructions are created for OISTART statements with the MEMBER keyword specified. User response: Convert the EQQOIPDS dataset to record length 80 and resubmit the job.
EQQY703E EQQY708E EQQY703E ONLY ONE OF THE ARGUMENTS FIRST, NEXT, PREV AND LAST IS ACCEPTED Explanation: The ARGN parameter can contain only one of the codes mentioned in the message text. System action: The request is rejected. User response: Check that there is a blank entry indicating end of the ARGN parameter. Correct the request and resubmit the job.
EQQY709E EQQY716E EQQY709E AN ABEND OCCURRED IN THE PROGRAM INTERFACE FUNCTION, IT IS RESTARTED Explanation: A serious error caused the program interface function to end in error. System action: The program interface function resumes normal processing. Problem determination: Review the dump dataset to determine the cause of the problem. User response: See message EQQG004E. EQQY711E THE RESOURCE RES IS NOT SUPPORTED FOR REQUEST REQ Explanation: The combination of RES and REQ is not supported.
EQQY717E EQQY725E EQQY717E NO COMMON SECTION HEADER RESOURCE HRES IN REQ STATEMENT Explanation: The REQ request requires that the record header contains a resource for the common section of a record. System action: The request is rejected. User response: Check the record header. Correct the request and resubmit the job. EQQY718E COMMON SECTION HEADER RESOURCE HRES TWICE IN REQ STATEMENT Explanation: The HRES resource may only appear once in the buffer header. System action: The request is rejected.
EQQY726E EQQY733E EQQY726E REQUEST REQ TO RESOURCE RES WITH KEY KEY FAILED. THE CURRENT PLAN RECORD IS HELD FOR UPDATE BY SOMEONE ELSE Explanation: The request could not be handled as the record was already being updated by another dialog or program interface user. System action: Processing continues. Problem determination: Check the data defined in the message using the TME 10 OPC dialog. User response: Perform the update using the dialog or rerun the program interface program.
EQQY738E EQQY821E EQQY738E A REQ RES REQUEST IS RECEIVED, NO WORK STATION IS IDENTIFIED. Explanation: The program interface was called to modify details of a current plan work station open time interval data. No current plan work station was identified. System action: The request is rejected. User response: Identify the workstation by a MODIFY CPWS request before requesting to modify the open time interval data. EQQY801E FAILED TO WRITE REC RECORD WITH KEY: KEY Explanation: A write failed.
EQQY822E EQQY827E EQQY822E CURRENT PLAN OCCURRENCE TO BE MODIFIED DOES NOT EXIST APPLICATION ID: ID, INPUT ARRIVAL TIME: IA Explanation: Current plan occurrence to be modified does not exist. System action: Processing continues. User response: Check the program interface call identifying the occurrence to be modified. Modify the ARGN/ARGP parameter by adding the application ID and input arrival date and time of the correct current plan occurrence.
EQQY830I EQQY834E EQQY830I THE REQUEST IS REQUEST RESOURCE, OCCURRENCE LTOC Explanation: A long-term-plan program-interface request is identified by: The request type One of the long-term-plan resources The key of the occurrence that is being inserted, deleted, or updated. System action: None. User response: None. EQQY832W UNRESOLVED DEPENDENCY Explanation: There are two possibilities: You were adding an occurrence to the long-term plan, using automatic dependency resolution.
EQQY835E EQQY905E EQQY835E FAILED TO DELETE DEPENDENCY LTPDERR Explanation: There are two possibilities: You were deleting an occurrence from the long-term plan. You were deleting a predecessor from a long-term-plan occurrence. The occurrence could not be deleted because of an I/O error. System action: None. Problem determination: This message is followed by message EQQY830I, which identifies the deleted or updated long-term-plan occurrence.
EQQZ000I EQQZ006I Chapter 33. EQQZnnn Messages EQQZ000I A STOP OPC/ESA COMMAND HAS BEEN RECEIVED Explanation: The TME 10 OPC started task has received an operator stop command. System action: TME 10 OPC posts all active subtasks for termination and terminates when all subtasks have terminated. EQQZ001E JES IS NOT ACTIVE. OPC/ESA CANNOT START Explanation: The TME 10 OPC subsystem could not start because no primary JES subsystem is active. System action: The subsystem program, EQQMAJOR, terminates.
EQQZ007E EQQZ012E EQQZ007E OPC/ESA JOBNAME JOBNAME IS NOT A VALID SUBSYSTEM NAME Explanation: The TME 10 OPC subsystem task module, EQQMAJOR, has been incorrectly invoked. System action: The EQQMAJOR program is terminated. System programmer response: Change the name of the TME 10 OPC subsystem started task to one of the subsystem names defined in SYS1.PARMLIB, then reissue the start command. | EQQZ008E THE OPC/ESA INITIALIZATION PROGRAM, EQQINITC, HAS NOT BEEN SUCCESSFULLY | EXECUTED.
EQQZ013I EQQZ019E EQQZ013I NOW PROCESSING PARAMETER LIBRARY MEMBER MEMBER Explanation: An TME 10 OPC subtask has started processing the parameter library member MEMBER. System action: TME 10 OPC processing continues. System programmer response: None. EQQZ014I MAXIMUM RETURN CODE FOR PARAMETER MEMBER MEMBER IS: MAXCC Explanation: An TME 10 OPC subtask has finished processing the parameter library member MEMBER.
EQQZ022W EQQZ029E EQQZ022W THE SSCM LOAD MODULE SPECIFIED, SSCM, COULD NOT BE LOADED Explanation: The module name specified in the SSCMNAME parameter of the OPCOPTS initialization statement could not be found. System action: Initialization continues, using the EQQSSCMC module defined by IEFSSNxx for TME 10 OPC event generation.
EQQZ030E EQQZ034I EQQZ030E OPC/ESA WAS UNABLE TO OPEN THE MESSAGE LOG DATA SET Explanation: TME 10 OPC cannot open its message log dataset. System action: The subsystem program, EQQMAJOR, terminates. Problem determination: Check that the EQQMLOG DD statement exists and is correctly coded. Verify that the subsystem started task is authorized to update the message log dataset. System programmer response: Correct the errors, and reissue the start command.
EQQZ035E EQQZ038E EQQZ035E MAXIMUM QUEUE SIZE (MAXNUM) WAS REACHED ON THE QNAME QUEUE. NUMLOST EVENTS HAVE BEEN LOST Explanation: An TME 10 OPC queue has reached its maximum size and a number of events could not be added. The most likely reason for this error is that TME 10 OPC has been inactive (not started) for some time and more job tracking events have occurred than could fit into the ECSA buffers available to this TME 10 OPC subsystem.
EQQZ039E EQQZ044E EQQZ039E DATA SET CONFLICT. THE DATA SET DEFINED BY DDNAME DDNAME IS USED BY ANOTHER OPC/ESA SYSTEM. DSNAME IS DSNAME Explanation: You tried to start an TME 10 OPC subsystem using an output dataset that is being used by another TME 10 OPC subsystem. System action: The subsystem terminates. System programmer response: Change the definition of the DD statement, and restart the TME 10 OPC subsystem.
EQQZ045W EQQZ051E EQQZ045W OPC/ESA SUBTASK SUBTASK ENDED UNEXPECTEDLY Explanation: An TME 10 OPC subtask ended without having been requested to terminate. System action: TME 10 OPC processing continues. Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact reason for this message. Check if a dump has been created on any dump dataset allocated to the TME 10 OPC started task.
EQQZ052E EQQZ061E EQQZ052E THE OPC/ESA PARAMETER LIBRARY FILE, DDNAME = EQQPARM, COULD NOT BE OPENED Explanation: TME 10 OPC could not open the parameter library file, ddname EQQPARM, which is a required input dataset for TME 10 OPC. System action: TME 10 OPC is terminated. Message EQQZ054E is issued. System programmer response: Check that ddname EQQPARM is correctly specified and that the TME 10 OPC started task is authorized to open the dataset for input. Correct all errors, then restart TME 10 OPC.
EQQZ062W EQQZ068E EQQZ062W THE OPC/ESA START/STOP USER EXIT MODULE COULD NOT BE LOADED Explanation: TME 10 OPC could not locate the subsystem start/stop exit load module EQQUX000. System action: The subsystem start/stop exit will not be used by TME 10 OPC. System programmer response: If the subsystem start/stop exit is meant to be used, make sure that the EQQUX000 load module is present in a library that can be reached by TME 10 OPC. Then, restart the TME 10 OPC started task.
EQQZ070E EQQZ075W EQQZ070E THE SSCMNAME KEYWORD SPECIFIES AN OPTION THAT IS NOT RECOGNIZED Explanation: The SSCMNAME keyword on the OPCOPTS initialization statement specifies a load option that is not supported. System action: TME 10 OPC initialization fails. System programmer response: Change the SSCMNAME option to one of the supported values, TEMPORARY or PERMANENT, or remove the currently specified value to let the option default, and then restart TME 10 OPC.
EQQZ076E EQQZ084E EQQZ076E DB2SYSTEM KEYWORD NOT SPECIFIED Explanation: The OPCOPTS or the BATCHOPTS initialization statement defines OPERHISTORY(YES) but the statement does not specify the DB2SYSTEM keyword. System action: TME 10 OPC is terminated. System programmer response: Edit the OPCOPTS or BATCHOPTS statement and either remove the OPERHISTORY keyword or specify the name of a DB2 system in the DB2SYSTEM keyword.
EQQZ085I EQQZ091W EQQZ085I OPC/ESA SUBTASK SUBTASK IS BEING STARTED Explanation: The TME 10 OPC subsystem has successfully attached the subtask SUBTASK. System action: TME 10 OPC continues processing. The subtask issues its own start message if the startup process is successful. User response: None. EQQZ086I NO ACTIVE OPC/ESA SUBTASKS. OPC/ESA IS ENDING Explanation: All TME 10 OPC subtasks have terminated. The TME 10 OPC address space is about to enter its own termination process.
EQQZ092W EQQZ100E EQQZ092W PERIODS ARE NOT PLACED CORRECTLY IN THE NOERROR VALUE, VALUE Explanation: A NOERROR statement, or the NOERROR keyword of JTOPTS, contains an error. Entry VALUE is not valid. The periods in an entry must be separated by at least one and no more than eight non-blank characters. System action: The normal mode manager (NMM) terminates. System programmer response: Correct the entry and restart the NMM subtask or the TME 10 OPC address space.
EQQZ101E EQQZ110E EQQZ101E THE GMTOFFSET VALUE MUST BE IN THE RANGE -1439 TO +1439. Explanation: The GMTOFFSET keyword specifies a value that is outside the range of valid values. System action: TME 10 OPC considers current initialization statement to be incorrectly coded. This will cause TME 10 OPC initialization to fail. System programmer response: Correct the GMTOFFSET value and restart TME 10 OPC.
EQQZ111E EQQZ115E EQQZ111E AN SNA CONNECTION HAS BEEN SPECIFIED IN THE OPT STATEMENT, BUT NCFTASK(YES) IS NOT SPECIFIED IN OPCOPTS Explanation: An SNA connection cannot be established between the controller and a tracker, because the OPCOPTS init statement does not contain NCFTASK(YES). The SNA connection is defined by the SNA keywords in the controller ROUTOPTS statement and the HOSTCON keyword of the tracker TRROPTS statement. System action: TME 10 OPC initialization terminates.
EQQZ116E EQQZ119E EQQZ116E AN XCF OR APPC CONNECTION HAS BEEN REQUESTED BUT THE LEVEL OF THE MVS/ESA SYSTEM DOES NOT SUPPORT THIS Explanation: If the XCF keyword of a ROUTOPTS initialization statement or the HOSTCON keyword of a TRROPTS initialization statement requests an XCF destination, your system must be at least MVS/ESA SP 4.1. If the APPC keyword of a ROUTOPTS initialization statement requests an APPC destination, your system must be at least MVS/ESA SP 4.2.2.
EQQZ120E EQQZ124E EQQZ120E CF FUNCTION FUNCTION FAILED WITH RETURN CODE=RETCODE AND REASON CODE RESCODE Explanation: This message lists the service requested, the failed function, the return code, and the reason code. System action: Depending on what kind of service failed, TME 10 OPC may either continue processing without the requested service, or terminate. Problem determination: Review the message log (EQQMLOG) and look for preceding error messages relating to the problem.
EQQZ125E EQQZ129I EQQZ125E OPC/ESA CANNOT CONTINUE PROCESSING DUE TO FULL QUEUE: QNAME THE SUBSYSTEM IS TERMINATING Explanation: One of TME 10 OPC internal queues is full. The subsystem was cancelled by the task that added the last element. System action: The TME 10 OPC subsystem terminates. Problem determination: Check the TME 10 OPC MLOG for EQQZ106W messages indicating which queue is full.
EQQZ130W EQQZ135E EQQZ130W XCF FUNCTION MSGO HAS FAILED DUE TO SIGNALLING FACILITY BUSY Explanation: An XCF transmission was not successfully sent. System action: The system will try to send it again. If the data queue element has not been successfully transmitted within 5 minutes, it will be discarded. Problem determination: This message can indicate that insufficient message-buffer space has been allocated in the transport class, for the TME 10 OPC user.
EQQZ140E EQQZ147E EQQZ140E YEAR, MONTH, AND DAY MUST ALL BE TWO-DIGIT NUMBERS Explanation: A nonnumeric date value has been specified. System action: Processing continues. System programmer response: Reenter a numeric date value. EQQZ141E YEAR MUST BE 00 - 99 Explanation: The year value is not valid. Year must be specified as 72 to 99 for years 1972 to 1999, or 00 to 71 for years 2000 to 2071. System action: Processing continues.
EQQZ148E EQQZ161E EQQZ148E HOUR MUST BE IN THE RANGE 0 TO 23 Explanation: A time value has been specified where the hour number is not valid. System action: Processing continues. System programmer response: Reenter the time value and specify an hour number in the range 0 through 23. EQQZ149E MINUTE MUST BE IN THE RANGE 0 TO 59 Explanation: A time value has been specified where the minute number is not valid. System action: Processing continues.
EQQZ162W EQQZ165I EQQZ162W UNABLE TO FIND MEMBER EQQDSLST IN EQQJCLIB Explanation: TME 10 OPC could not find the member EQQDSLST in the dataset referenced by the EQQJCLIB ddname. This message can be issued: During initialization of the Event Writer task. When processing a modify command with the NEWDSLST option. System action: If the message was issued when processing a modify command, the previously built dataset selection table remains in effect.
EQQZ170E EQQZ174W EQQZ170E TME 10 OPC CODE LEVEL VERIFICATION FAILED CODE LEVEL OF THE SSX CONTROL BLOCK IS SSXLEV CODE LEVEL OF THE EQQMAJOR MODULE IS MCALEV CODE LEVEL OF THE SSCM MODULE IS SSCMLEV Explanation: TME 10 OPC initialization has determined that the SSX control block, the EQQMAJOR module and the EQQSSCMx load module are on different service levels. This is not supported. System action: TME 10 OPC initialization fails.
EQQZ175E EQQZ179E EQQZ175E INCONSISTENT DEFINITION OF JOBLOGRETRIEVAL KEYWORD Explanation: You have made an inconsistent definition of JOBLOGRETRIEVAL in JOBOPTS. Check the following conditions: OPCHOST(NO) must be specified on OPCOPTS CATMGT(YES) must be specified on OPCOPTS If you have specified JOBLOGRETRIEVAL(DELAYED) or (DELAYEDEXIT), you must have a EXITS statement with CALL010(YES) or LOAD010(nnnnnnnn). System action: TME 10 OPC is terminated.
EQQZ180E EQQZ186I EQQZ180E INCONSISTENT DEFINITION OF EXIT STATEMENT AND JOBLOGRETRIEVAL KEYWORD Explanation: You have specified the JOBLOGRETRIEVAL keyword with value DELAYED or DELAYEDEXIT. The value implies the use of a user exit, UX010, that has not been defined to TME 10 OPC. System action: TME 10 OPC is terminated. System programmer response: Correct the inconsistent definitions and restart TME 10 OPC.
EQQZ187E EQQZ192E EQQZ187E CHECKPOINT DATASET WAS NOT INITIALIZED Explanation: During the startup with OPCOPTS OPCHOST(PLEX) was found that the checkpoint dataset is not initialized. This is not supported. System action: TME 10 OPC stop processing. System programmer response: Start one TME 10 OPC controller with OPCOPTS OPCHOST(YES) to initialize the checkpoint dataset with the correct FMID and service level for a Sysplex Controller configuration.
EQQZ200I EQQZ202I | EQQZ200I OPC/ESA OPCTYPE SUBSYSTEM NAME HEARTBEAT | Explanation: This message is sent by OPC at startup or as result of an OPC "heartbeat" command, to state that | OPC is active and running. | OPCTYPE | | | | SUBSYSTEM NAME One of the following values: CONTROLLER If the subsystem is an OPC controller. STANDBY If the subsystem is a stand-by controller. TRACKER If the subsystem is an OPC MVS tracker. The name of the OPC subsystem.
EQQZ203I EQQZ204I | EQQZ203I TRACKER TYPE TRACKER TRACKER NAME : TRACKER ADDRESS TRACKER STATUS | Explanation: Provides information about the status of a tracker connected to an OPC controller. | | | | | | | | | | | | | TRACKER TYPE TRACKER NAME TRACKER ADDRESS TRACKER STATUS The type of tracker. It can be one of the following values: SNA XCF DASD TCP USER APPC HOME The name of the OPC destination associated with that tracker. The TCP/IP or SNA address associated with that tracker.
EQQZ205I EQQZ207I | EQQZ205I TRACKER TYPE TRACKER TRACKER NAME : TRACKER ADDRESS NOT FOUND | Explanation: This message is sent by OPC as result of a STATUS,TRK OPC command, when the tracker name (or | tracker address) is not defined to the Controller in the ROUTOPTS initialization statements.
EQQZ208I EQQZ210I | EQQZ208I OPC DATASET NAME LAST-RC= LAST RETURN CODE | Explanation: Provides the return code of the last I/O operation on the specified DDNAME. | OPC DATASET NAME | LAST RETURN CODE | | | | | The DD name of an OPC dataset One of the following values: NORMAL WARNING SEVERE CRITICAL UNKNOWN | System action: Depending on the return code value and on the DDNAME specified, OPC could stop some of its | subtasks.
436 TME 10 OPC Messages and Codes
EQQ0014E EQQ0020E Chapter 34. EQQnnnn Messages EQQ0014E DBCS FORMAT SPECIFIED BUT ADID NOT VALID BRACKETED DBCS: NAME Explanation: The application ID NAME is specified to be in DBCS format, that is, it must start with a shift-out character (X'0E') and end with a shift-in character (X'0F'). Either the shift-out or the shift-in character, or both, are missing. System action: Processing is terminated. User response: Correct the error and resubmit the job.
EQQ0021E EQQ0027I EQQ0021E INVALID MONTH IN DATE : DATE Explanation: The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the dialog. The month is invalid in DATE. System action: The job is terminated. User response: Correct the error and resubmit the job, or submit the job using the TME 10 OPC dialog.
EQQ0100E EQQ0183W EQQ0100E APPLICATION DESCRIPTION DATA SET IN USE, TRY LATER Explanation: You have attempted to access the application description dataset, but it is being used by another user. System action: The job is terminated. User response: Try again later. EQQ0105W APPLICATION DESCRIPTION ADID NOT FOUND Explanation: You have attempted to read the application description ADID but this application description ID does not exist in the application description database.
EQQ0196E EQQ0303E EQQ0196E ERRORS ENCOUNTERED WHILE SORTING Explanation: Errors were encountered from the sort program. System action: The job is terminated. User response: Contact your system programmer. System programmer response: Check the sort program messages to determine the cause of the error. Correct the errors and then resubmit the job. EQQ0300E LTP DATA SET IN USE - TRY LATER Explanation: The long-term plan dataset is being used by another TME 10 OPC function.
EQQ0304E EQQ0308E EQQ0304E STATUS OF OLDCP UNKNOWN, CP BACKUP DID NOT COMPLETE NORMALLY Explanation: The last backup of the active current plan to the backup current plan failed. The current plan input to daily planning could therefore be incomplete or out-of-date. System action: The daily plan batch process terminates. Problem determination: Review the controller message log (EQQMLOG), to determine why the current plan backup process failed.
EQQ0309E EQQ0313E EQQ0309E APPL **************** ******** **.** INVOLVED IN DEPENDENCY LOOP Explanation: This message is issued together with message EQQ0308E. It lists the applications involved in a dependency loop. System action: No new current plan is produced; however, a printed plan is produced. The job is terminated. User response: Same as for message EQQ0308E.
EQQ0314E EQQ0318E EQQ0314E WRONG OLD CURRENT PLAN SELECTED AS INPUT Explanation: The old current plan dataset used as input when extending or replanning the current plan period is not the correct dataset. The dataset may have been restored from a backup copy. System action: The daily planning program is terminated. User response: Ensure the daily planning batch JCL is referring to the same current plan and long-term plan datasets as the controller subsystem.
EQQ0319E EQQ0323W EQQ0319E WRONG LTP DATA SET SELECTED AS INPUT Explanation: The long-term plan dataset used as input when extending or re-planning the current plan period is not the correct dataset. The dataset may have been restored from a backup copy. System action: The daily planning program is terminated. User response: Ensure the daily planning batch JCL is referring to the same current plan and long-term plan datasets as the controller subsystem.
EQQ0324W EQQ0327W EQQ0324W DAILY OP PLAN REPORT OPTION MUST BE 0 OR 1 - SET TO 1 Explanation: The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the dialog. The daily operation plan report options are: 0 1 For daily operating plan report not required For daily operating plan report required. System action: The value is set to 1 and the daily planning program continues processing.
EQQ0328W EQQ0332W EQQ0328W CURRENT PLAN REPORT OPTION MUST BE 0 OR 1 - SET TO 1 Explanation: The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the dialog. The current plan report options are: 0 1 For current plan reports not required For current plan reports required. System action: The value is set to 1 and the daily planning program continues processing.
EQQ0333W EQQ0337W EQQ0333W NO DEFAULT SUCC OP FOUND IN APPL **************** ******** **.** Explanation: No default successor operation, as defined in the installation options, has been found for the application APPL. System action: The daily planning program continues processing. User response: Use the application description dialog to verify and correct the dependency, and/or use the Modify Current Plan dialog to add the dependency to the current plan. Or, contact your system programmer.
EQQ0338W EQQ0343W EQQ0338W PRED OP ******** TO PRINT OP ******** NOT ON A CPU WS Explanation: An automatic printer workstation operation has a predecessor on a workstation which is not an automatic computer workstation. This is not allowed. System action: The application in the long-term plan dataset is marked “deleted” when the current plan period is extended. The application is not included in the new current plan or in the printed plans. The daily planning program continues processing.
EQQ0344E EQQ0349I EQQ0344E INVALID TRIAL TYPE Explanation: The daily planning trial type was not correctly specified. You can specify only one of the following options: N C F For Extending Current Plan Period — Trial For Replanning Current Plan Period — Trial For Producing Daily Plan — Trial. System action: The daily planning program is terminated. User response: Change the parameter value for the trial type in the SYSIN statement for the daily planning program.
EQQ0350E EQQ0354W EQQ0350E PERIOD START LATER THAN LAST BACKUP TIME Explanation: Reporting can only be requested for time periods less recent than the last old current plan. The old current plan is a backup copy of the current plan and is updated either after every certain number of events (specified at installation time) or during daily planning. System action: The daily planning program is terminated.
EQQ0355W EQQ0384E EQQ0355W PREDECESSOR ******** **************** **.** FOR ******** **************** **.** MISSING Explanation: A predecessor could not be found as expected. It is probably caused by an error in the LTP and/or OCP. System action: The job continues User response: Check the flagged occurrences and contact your system programmer. System programmer response: Collect documentation and contact IBM Service representative.
EQQ0384E EQQ0384E LIST OF OPERATIONS CONTAINED IN LOOP FOLLOWS: This message follows the loop error condition message above, and is a loop contents header message. The message is always followed by a set of messages, each containing identification of one operation in the loop. LOOP: OP OPID JOBN IN APPL APPLID IA IADATE IATIME This message follows the loop contents header message, and the message contains operation and application identification of one operation contained in the loop.
EQQ0386I EQQ0389I The dependency is selected according to the minimal impact criteria, that is, removal of this dependency causes the least distortion to the present NET. System action: No new current plan is created, TME 10 OPC continues normal processing. Reporting continues. Problem determination: Information only. The Daily Plan program has terminated due to the loop condition.
EQQ0398E EQQ0420E EQQ0398E UNSUCCESSFUL PUT SYNAD1 Explanation: An error occurred while writing to an intermediate work file or the track log file used by daily planning. The SYNAD routine extracted the following information: job name, stepname, unit address, device type, ddname, operation, error description, phys-DA, and access method. System action: The daily planning program is terminated. A new current plan and reports may have been produced.
EQQ0421E EQQ0452W EQQ0421E CALENDAR CALNAME NOT FOUND IN DATA BASE Explanation: This message is issued from a batch job; the submit request is terminated. User response: Specify the ID of an existing calendar. EQQ0422E PRINT END DATE NOT SPECIFIED Explanation: This message is issued from a batch job; the submit request is terminated. User response: Specify an end date for the calendar/period print program.
EQQ0453W EQQ0461W EQQ0453W NO OCCURRENCES FOUND FOR PRINT PERIOD STARTDAT - ENDDAT Explanation: There are no occurrences in the long-term plan for the print period specified when requesting a print out of the long-term plan. System action: No occurrences are listed and the job is terminated. User response: Check that the print period is correct.
EQQ0500E EQQ0506W EQQ0500E END DATE PRIOR TO CURRENT DATE Explanation: An end date specified for a create or extend run of the long-term plan, should be later than or the same as the current date. System action: The job is terminated. User response: Specify a valid date. EQQ0501E INVALID REPORT TYPE TYPE Explanation: The report type specified for a long-term plan print request is invalid. Valid report types are F for full report, and D for dependencies only. System action: The job is terminated.
EQQ0508W EQQ0513W EQQ0508W APPLICATION ADID REFERS TO UNDEFINED CALENDAR CALID DEFAULT CALENDAR DEFCAL NOT FOUND. ALL DAYS TREATED AS WORKDAYS Explanation: This message is issued from an LTP batch program. The calendar specified in the application description could not be found in the database nor could the calendar specified in the BATCHOPT parameter CALENDAR. The calendar called DEFAULT will be used instead. If there is no DEFAULT calendar, all days are treated as workdays.
EQQ0515E EQQ0520W EQQ0515E INVALID INPUT LONG TERM PLAN DATA SET. A NEW LTP IS NOT CREATED. THE BACKUP LTP DATA SET IS VALID BUT THE INPUT LTP IS NOT Explanation: The long-term plan batch program has found that the input LTP file does not contain a valid long-term plan but the long-term plan backup file is valid. The most likely cause of this message is that the previous execution of the LTP batch program failed before the new LTP file was successfully built.
EQQ0521E EQQ0528W EQQ0521E SORT FAILURE FOR WORK DATA SET: DDN Explanation: Sort was invoked to sort on a long-term plan dataset but returned RC=16. System action: The job is terminated. User response: Make the SORT program diagnostic messages on SYSOUT available to your system programmer. System programmer response: Investigate the reason for the incorrect sort and then rerun the job.
EQQ0531I EQQ0537I EQQ0531I GENERATED DUP OMITTED: ADID DATE TIME RCTEXT01 RCDATA01 Explanation: A unique occurrence consists of application description ID, run date, and input arrival time. When generating occurrences, duplicates have resulted. RCTEXT01 is 'NORMAL RUNCYCLE:' for offset-based runcycles, and 'REGULAR RULE:' for rule-based runcycles. RCDATA01 is PNAM SIGN OFFS for offset-based runcycles, and PNAM for rule-based runcycles. System action: One occurrence is selected; the others are bypassed.
EQQ0540E EQQ0546W EQQ0540E SPECIFIED PRINTOUT PERIOD GREATER THAN 4 YEARS Explanation: You are requesting a printout of the long-term plan dataset for a period of more than four years, but the long-term plan may have a span of up to four years only. System action: The job is terminated. User response: Request a printout for a period less than four years.
EQQ0547W EQQ0554W EQQ0547W THE SUCCESSOR SUC WITH RUNDAY SUCDAY AND INPUT ARRIVAL STIME, FOR APPLICATION AD IN THE LONG TERM PLAN COULD NOT BE FOUND. THE APPLICATION AD WITH RUNDAY RUNDAY AND INPUT ARRIVAL RTIME MAY HAVE TO BE MANUALLY COMPLETED OR DELETED Explanation: The actual occurrence has been deleted from the long-term plan, probably by a non-TME 10 OPC function. System action: A new current plan is created, but the daily plan program ends with a return code of 4.
EQQ0555W EQQ0561W EQQ0555W WS ID WSID NOT FOUND WITHIN ANY APPLICATION Explanation: When printing an “operations using particular work stations” report during an application description PRINT, the specified workstation name does not appear in any application description. System action: The job continues processing. User response: Specify the correct workstation name and then resubmit the job.
EQQ0562E EQQ0589W EQQ0562E INVALID COMBINATION OF INPUT PARAMETERS Explanation: It is not possible to select input type 3 when report type 3 or 4 has been chosen. System action: The job is terminated. User response: Check the input parameters and then resubmit the job. EQQ0563E INVALID NUMBER OF ITEMS IN INPUT PARAMETERS Explanation: The number of items is greater than 12 or does not equal the number of items in the list. System action: The job is terminated.
EQQ0590W EQQ0600E EQQ0590W OCCURRENCE OCCAD OCCDAY OCCTIME HAS TOO MANY SUCCESSORS. CURRENT SUCCESSOR APPLICATION IS DEPAD DEPDAY DEPTIME. NSUC SUCCESSOR DEPENDENCIES COULD NOT BE CREATED Explanation: An occurrence has been found which has too many successors to be saved in the LTP dependency work file defined by DD-statement EQQLDDS. System action: The LTP batch job continues processing.
EQQ0601E EQQ0615W EQQ0601E THE EXTENSION LENGTH SHOULD BE A NUMERIC VALUE FROM 0001 TO 1461 Explanation: The extension length must not be longer than 4 years, that is 1461 days. System action: LTP batch processing ends. User response: Update the extension length on the SYSIN statement and resubmit the job. EQQ0602E AN EXTENSION LENGTH AND A START DATE CANNOT BE ENTERED TOGETHER Explanation: You must specify either an extension length, or a start date and an end date.
EQQ0616W EQQ0820E EQQ0616W RESOURCE RESNAME IS RETAINED IN CURRENT PLAN, EVEN THOUGH NO DEFINTION EXIST IN TAB DATASET Explanation: This message is issued by the DP batch programs to the Daily Planning report dataset, whenever a resource is kept in the current plan (or NCP). The resource definition does no longer exist in the RD file, but operations are still using this resource in not yet expired availability intervals. System action: Daily Planning continues normally.
EQQ0821E EQQ0836E EQQ0821E PROGRAM INTERFACE INITIALIZATION REQUEST TO SUBSYSTEM SUBSYS FAILED Explanation: Initialization request to subsystem SUBSYS using the program interface failed. TME 10 OPC tried to use PIF to retrieve or update operator instructions because the job does not allocate the EQQOIDS file. System action: The job ends. User response: Check that the correct subsystem name is specified in the SUBSYS parameter of the BATCHOPT statement.
EQQ0837W EQQ0845W EQQ0837W FIRST INPUT RECORD NOT HEADER RECORD Explanation: The first record encountered while creating operator instructions from a sequential input file is not a header record. System action: The job continues processing. All records up to the first valid header record are bypassed. User response: Correct your input and then resubmit the job so that the bypassed instructions will also be created, or use the Operator Instruction dialog to create the instructions.
EQQ0846W EQQ0937W EQQ0846W BOTH DATE AND TIME MUST BE SPECIFIED. INSTR.: NAME NUMBER Explanation: Either the date or the time was omitted; both are required. System action: The job continues processing but the instruction is not created; all records up to the next valid header statement are bypassed. User response: Correct your input. EQQ0847W EMPTY OPERATOR INSTRUCTION IN SEQ INPUT FILE Explanation: The operator instruction has no instruction text.
EQQ0953E EQQ0958E EQQ0953E OCCURRENCE ANAME AT ATIME VSAM KEY: OPKEY HAS AN INVALID OPERATION Explanation: An operation record was detected with a zero operation number. System action: Daily plan is stopped with a return code 12. User response: Contact your system programmer. System programmer response: This is an TME 10 OPC error. Create an APAR tape, and use IDCAMS to delete the operation with the given VSAM key. Then contact your IBM representative.
EQQ0959E EQQ1457E EQQ0959E FUNC FAILED FOR FILE MSG: SYNADMSG CALLING MODULE IS MODULE Explanation: A batch program attempted to do the function FUNC against the file FILE but the attempt failed. The I/O request is from module MODULE. System action: The job is terminated. Problem determination: The SYNAD routine collects information such as jobname, stepname, unit address, device type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this information.
EQQ1458I EQQ2010E EQQ1458I DAILY PLANNING REPORT USER EXIT IS ACTIVE FOR THIS PRINTOUT Explanation: The exit for daily planning print is activated. System action: The job continues processing. User response: None. EQQ1459I DAILY PLANNING REPORT USER EXIT IS NOT ACTIVE FOR THIS PRINTOUT Explanation: The exit for daily planning print is not activated. System action: The job continues processing.
EQQ2011W EQQ2015W EQQ2011W A PREDECESSOR TO APPLICATION APPLIADATE IATIME WAS NOT FOUND Explanation: The Daily Plan program was unable to find a predecessor to the occurrence defined by this message. System action: Daily Planning takes the action defined by the VALEACTION keyword of the BATCHOPT statement. Problem determination: Refer to data in the diagnostic file, EQQDUMP, to determine the cause of the error.
EQQ2016E EQQ2018W EQQ2016E OPERATION OPERNRIN APPLICATION APPLIDIS TOO LARGE TO BE SAVED IN THE NEW CURRENT PLAN DATA SET. THE FAILING OPERATION CONTAINS PREDNRDEPENDENCIES AND SPECNRSPECIAL RESOURCES Explanation: The Daily Plan program was unable to create an operation record because it would be too large for the output data set defined by the EQQNCPDS DD-statement. System action: The Daily Plan program terminates processing.
EQQ2019E EQQ9986E EQQ2019E ADID: AD, WS: WS, OP: OP, JOBNAME: JOB, IA: IA HAS AN INVALID DEPENDENCY TO OPERATION ADID: AD, WS: WS, OP: OP, JOBNAME: JOB, IA: IA. Explanation: The Daily Planning program found an invalid external dependency in an operation. System action: The Daily Planning program ends with return code 08 without creating a new current plan. User response: Use the modify current plan dialog to validate the external dependencies in the operation indicated first in this message.
EQQ9987W EQQ9989E | EQQ9987W OPERHISTORY IS NO BUT RELATED PARAMETERS ARE SPECIFIED: IGNORED | Explanation: The BATCHOPTS statement specifies the DB2SYSTEM, CONTROLLERTOKEN, DB2AVAIL, or | RETAINOPER parameters, either without specifying the OPERHISTORY keyword or with OPERHISTORY set to NO. System action: The daily plan program is terminated. | System programmer response: Check whether the history function is intentionally disabled or whether the | OPERHISTORY keyword was omitted.
1102 1121 Chapter 35. Abend Codes This chapter lists the TME 10 OPC abend codes in numeric order. 1102 Explanation: Undefined feedback from VTAM, or a serious error after a VTAM request that makes continued processing impossible. (Note: Message EQQV015E is issued only if request parameter list (RPL) feedback is available.) Problem determination: See message EQQV015E, which precedes this abend, for diagnostic information.
1124 3999 1124 Explanation: Invalid action code. (Internal NCF error.) System programmer response: Contact your IBM representative. 2001 Explanation: Problem accessing the special resource dataspace during daily planning, and the VALEACTION keyword of BATCHOPT specifies ABEND. System programmer response: Take a copy of the old current-plan file, the EQQCXDS file, and the EQQRDDS file, and contact your IBM representative. 3900 Explanation: Not enough storage available to continue execution.
Chapter 36. Reason Codes The following table lists the reason codes that can appear in message EQQG005E or EQQ0170W. For more information about a reason code, refer to the related message. Note: In the diagnostic file (with DD name EQQDUMP), dates are represented either in real date format, or in the internal TME 10 OPC format. Reason Meaning (reason for failure) code Related message 000 The record size exceeds the maximum record size for the application description database.
Reason Meaning (reason for failure) code Related message 113 The calendar description identifier referred to by the application description record does not exist in the database. EQQX326 114 The owner ID contains lower case characters. EQQX397 115 An application or job description which specifies a group definition cannot contain a run cycle. EQQA516 116 Priority cannot be specified for a group definition. EQQA510 117 Group definitions cannot contain operations.
Reason Meaning (reason for failure) code Related message 311 The operation deadline time is invalid. EQQX347 312 The workstation resource 1 usage is invalid. EQQX348 313 The workstation resource 2 usage is invalid. EQQX348 314 The parallel processing count is invalid. EQQX349 315 The number of internal predecessors is invalid; it is not compatible with the actual number of predecessors in the record.
Reason Meaning (reason for failure) code Related message 604 Resource quantity is not in the range 1-999999. EQQX438 605 The on-error value is not valid. EQQX429 700 Duplicate operations exist in the application description record. EQQX365 701 A predecessor does not exist. EQQX366 702 There is a loop in the application network. EQQX367 703 All operations in the application do not belong to the same network. EQQX368 704 A job setup, processor, or print operation lacks a job name.
Reason Meaning (reason for failure) code Related message 852 The DBCS part of the field application ID is blank. EQQX384 853 Check if the routine has encountered a superfluous shift-out or shift-in character within the DBCS part of the field application ID. EQQX385 854 The Field application ID contains either invalid DBCS characters, that is, out of the range X'41' - X'FE', or an odd number of blanks (X'40'), in the trailing part of the DBCS part of the field.
Reason Meaning (reason for failure) code Related message 1033 The predecessor input arrival time is missing. EQQX429 1034 The predecessor input arrival time is invalid. EQQX333 1035 The predecessor application ID is missing. EQQX430 1036 The DBCS predecessor application ID is invalid. EQQX382 1037 The predecessor application ID is invalid. EQQX302 1038 An occurrence is dependent on itself. EQQX434 1039 The input arrival date is later than the deadline.
00 44 Chapter 37. TME 10 OPC Batch Program Codes and Messages This chapter describes the TME 10 OPC batch program codes and messages: Completion codes that are returned by batch job EQQPDLF Write-to-operator (WTO) messages that are generated by batch job EQQPURGE EQQPDLF Batch Program Condition Codes EQQPDLF returns one of the following codes upon completion. 00 RETAINED OBJECT FOUND AND DELETED Explanation: The DLF object has been purged from Hiperspace. System action: EQQPDLF terminates.
EQQPURGE EQQPURGE EQQPURGE Batch Program WTO Messages If EQQPURGE receives invalid input, one of the following WTO's is written to the operator console. EQQPURGE PARAMETER CARD SPECIFIES AN INVALID NAME Explanation: The object name passed to EQQPURGE is either of length 0 or longer than 44 characters. System action: The JCL from the JCLIN dataset is neither substituted nor written to the internal reader. User response: Verify that EQQPROC has been started by TME 10 OPC.
Communicating Your Comments to IBM TME 10 Operations Planning and Control Messages and Codes Version 2 Release 2 Publication No. SH19-4480-01 If you especially like or dislike anything about this book, please use one of the methods listed below to send your comments to IBM. Whichever method you choose, make sure you send your name, address, and telephone number if you would like a reply.
Help us help you! TME 10 Operations Planning and Control Messages and Codes Version 2 Release 2 Publication No. SH19-4480-01 We hope you find this publication useful, readable and technically accurate, but only you can tell us! Your comments and suggestions will help us improve our technical publications. Please take a few minutes to let us know what you think by completing this form.
Help us help you! SH19-4480-01 Fold and Tape IBM Please do not staple Cut or Fold Along Line Fold and Tape PLACE POSTAGE STAMP HERE TME 10 OPC Information Development Rome Tivoli Laboratory IBM Italia S.p.A.
IBM Program Number: 5697-OPC Printed in Denmark by IBM Danmark A/S SH19-448ð-ð1
