Benutzeranleitung / Produktwartung SH19-4480-01 des Produzenten IBM
Zur Seite of 514
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.
Contents Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Preface . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 18. EQQOnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 229 Chapter 19. EQQPnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 231 Chapter 20. EQQQnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 235 Chapter 21.
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: Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation.
Preface This book describes messages issued by TME 10 Operations Planning and Control (TME 10 OPC), program number 5697-OPC. This book documents the messages issued by these features: The TME 10 O.
TME 10 OPC Publications This book is part of an extensive TME 10 OPC library. These books can help you use TME 10 OPC more effectively: Task Publication Order number Evaluating TME 10 OPC General Fact.
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: | .
Short Title Publication Order Number MVS/ESA Codes MVS/ESA System Codes GC28-1664 MVS/ESA SP5 System Codes GC28-1486 MVS/ESA Messages MVS/ESA System Messages, Volume 1 (ABA-ASA) GC28-1656 MVS/ESA Syst.
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.
| 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.
| 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.
| HB Issues a heartbeat message for an OPC controller or for all | trackers connected to that controller | JCLDBG Activates or deactivates the JCL debugging trace | QUELEN Sets a new value for the QUE.
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 .
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 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.
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.
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.
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.
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.
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 pe.
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.
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.
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.
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.
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.
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.
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.
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 Free days excluded. 1 Run on the closest workday before the free day.
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.
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.
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.
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.
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.
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.
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.
EQQA309E EQQA400E EQQA309E PRINT OPERATION OP MUST HAVE A CPU PREDECESSOR Explanation: The print operation (operation number o p ) 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
EQQC048W EQQC049E 31 Failing operation record could not be read. 32 Invalid stepname or no step with that name. 33 More than one step in JS record with the given name. 34 JS dataset in use. Recovery test canceled. 35 JS dataset member in use. Recovery test canceled.
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.
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.
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.
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.
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.
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 .
EQQCL0XI EQQCL14I | EQQCL0XI Default operation number is used: defopno | Explanation: OCL will use defopno as the default operation number. | System action: Processing continues.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
EQQCL71E EQQCL78E | EQQCL71E OPNO() and EXCLOP() are mutually exclusive keywords | Explanation: OPNO and EXCLOP are mutually exclusive keywords. | 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
EQQD140E EQQD144I EQQD140E THE JOBLOG RETURNED BY EXITNAME FOR JOBNAME JOBNUM IN APPLICATION APPL I S 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.
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.
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.
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.
EQQE000I EQQE001E Chapter 8. EQQEnnn Messages EQQE000I TOTAL NUMBER OF EVENTS PROCESSED BY THE EVENT MANAGER TASK IS: NUMEV NUMBER OF EVENTS SINCE THE PREVIOUS MESSAGE IS: NEWEV EVENT MANAGER QUEU.
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 t.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
EQQG010I EQQG010I TOTTIME The total time, in seconds, used to process this request. NEWTIME The total time, in seconds, used to process this request since the last message. TOTAVG The average time, in seconds, used to process a request of this type.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 .
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.
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.
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.
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.
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.
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 specif.
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 co.
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 .
EQQIC37E EQQIC38W | EQQIC37E CURRENT PLAN RECORD OF TYPE RECID FOR APPLICATION AD WITH INPUT ARRIVAL IA I S | 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
EQQJ599E EQQJ611E | EQQJ599E NUMERIC MUST BE SPECIFIED FOR RANGE/LIST VERIFICATION | Explanation: Data entry error; see “Data Entry Errors” on page 2.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 W S OP .
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.
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.
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.
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.
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.
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.
EQQL504E EQQL512E EQQL504E APPLICATION DEPAID NOT FOUND Explanation: The application ( DEPAID ) specified in the LTP occurrence was not found in the application description database.
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.
EQQL568I EQQL706E EQQL568I LTPCHDD , LTPCHDT DEADLINE PAST OCCURRENCE TIME LIMIT Explanation: The operation deadline LTPCHDD, LTPCHDT is outside the occurrence time limit.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 .
EQQM916E EQQM920E EQQM916E REQUEST TO ADD SPECIAL RESOURCE THAT ALREADY EXISTS OPERATION : APPL , OPER SPECIAL RESOURCE: SPR Explanation: A modify-current-plan request to add a special resource failed because the the requested special resource already exists in the operation.
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 The last internal dependency cannot be deleted.
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.
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.
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.
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.
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.
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.
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.
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.
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 FUN.
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.
EQQN011E EQQN016I System programmer response: Scratch and reallocate the job tracking log data set at a suitable moment when TME 10 OPC is stopped.
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.
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.
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.
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.
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 .
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.
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.
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.
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.
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.
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.
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.
EQQO001I EQQO006E Chapter 18. EQQOnnn Messages EQQO001I APPC TASK INITIALIZATION IS COMPLETE Explanation: The APPC task has completed initialization 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.
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.
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.
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 .
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.
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.
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.
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.
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.
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.
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.
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.
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.
EQQRM01I EQQRM07W Chapter 21. EQQRMnn Messages EQQRM01I RODM SUBTASK INITIALIZATION IS COMPLETE Explanation: The RODM subtask has completed initialization processing.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 .
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
EQQW512E EQQW517E EQQW512E WS ANALYZER WAS UNABLE TO READ OR UPDATE CURRENT PLAN OPERATION RECORD WITH KEY (HEXADECIMAL): F0F3 OPRINDEX Explanation: The workstation analyzer encountered a VSAM error when reading or updating the current plan dataset.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 ' .
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 IEFSSN xx 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.
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.
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.
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.
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.
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.
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.
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.
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.
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 i s not valid. The periods in an entry must be separated by at least one and no more than eight non-blank characters.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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 SSCM.
EQQZ175E EQQZ179E EQQZ175E INCONSISTENT DEFINITION OF JOBLOGRETRIEVAL KEYWORD Explanation: You have made an inconsistent definition of JOBLOGRETRIEVAL in JOBOPTS.
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.
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.
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 One of the following values: | CONTROLLER If the subsystem is an OPC controller.
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.
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.
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 ' ).
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.
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.
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.
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.
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.
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.
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.
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.
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 For current plan reports not required 1 For current plan reports required.
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.
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.
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 For Extending Current Plan Period — Trial C For Replanning Current Plan Period — Trial F For Producing Daily Plan — Trial.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
EQQ1458I EQQ2010E EQQ1458I DAILY PLANNING REPORT USER EXIT IS ACTIVE FOR THIS PRINTOUT Explanation: The exit for daily planning print is activated.
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.
EQQ2016E EQQ2018W EQQ2016E OPERATION OPERNR IN APPLICATION APPLID IS TOO LARGE TO BE SAVED IN THE NEW CURRENT PLAN DATA SET. THE FAILING OPERATION CONTAINS PREDNR DEPENDENCIES AND SPECNR SPECIAL R.
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.
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.
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.
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.
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 code Meaning (reason for failure) 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.
Reason code Meaning (reason for failure) 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.
Reason code Meaning (reason for failure) 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.
Reason code Meaning (reason for failure) 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.
Reason code Meaning (reason for failure) 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.
00 4 4 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 �.
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.
.
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.
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.
Cut or Fold Along Line Cut or Fold Along Line Help us help you ! SH19-4480-01 IBM Fold and Tape Please do not staple Fold and Tape PLACE POSTAGE STAMP HERE TME 10 OPC Information Development Rome Tivoli Laboratory IBM Italia S.
.
IBM Program Number: 5697-OPC Printed in Denmark by IBM Danmark A/S SH19-448ð-ð1.
Ein wichtiger Punkt beim Kauf des Geräts IBM SH19-4480-01 (oder sogar vor seinem Kauf) ist das durchlesen seiner Bedienungsanleitung. Dies sollten wir wegen ein paar einfacher Gründe machen:
Wenn Sie IBM SH19-4480-01 noch nicht gekauft haben, ist jetzt ein guter Moment, um sich mit den grundliegenden Daten des Produkts bekannt zu machen. Schauen Sie zuerst die ersten Seiten der Anleitung durch, die Sie oben finden. Dort finden Sie die wichtigsten technischen Daten für IBM SH19-4480-01 - auf diese Weise prüfen Sie, ob das Gerät Ihren Wünschen entspricht. Wenn Sie tiefer in die Benutzeranleitung von IBM SH19-4480-01 reinschauen, lernen Sie alle zugänglichen Produktfunktionen kennen, sowie erhalten Informationen über die Nutzung. Die Informationen, die Sie über IBM SH19-4480-01 erhalten, werden Ihnen bestimmt bei der Kaufentscheidung helfen.
Wenn Sie aber schon IBM SH19-4480-01 besitzen, und noch keine Gelegenheit dazu hatten, die Bedienungsanleitung zu lesen, sollten Sie es aufgrund der oben beschriebenen Gründe machen. Sie erfahren dann, ob Sie die zugänglichen Funktionen richtig genutzt haben, aber auch, ob Sie keine Fehler begangen haben, die den Nutzungszeitraum von IBM SH19-4480-01 verkürzen könnten.
Jedoch ist die eine der wichtigsten Rollen, die eine Bedienungsanleitung für den Nutzer spielt, die Hilfe bei der Lösung von Problemen mit IBM SH19-4480-01. Sie finden dort fast immer Troubleshooting, also die am häufigsten auftauchenden Störungen und Mängel bei IBM SH19-4480-01 gemeinsam mit Hinweisen bezüglich der Arten ihrer Lösung. Sogar wenn es Ihnen nicht gelingen sollte das Problem alleine zu bewältigen, die Anleitung zeigt Ihnen die weitere Vorgehensweise – den Kontakt zur Kundenberatung oder dem naheliegenden Service.
