IBM SH19-4480-01 - Manual - manualsarea.com

Page 3 - TME 10 Operations Planning and Control; IBM; Messages and Codes; Version 2 Release 2

TME 10 Operations Planning and Control IBM Messages and Codes Version 2 Release 2 SH19-4480-01

Page 5 - Contents; iii

Contents Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii How This ...

Page 6 - iv

Chapter 18. EQQOnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 229 Chapter 19. EQQPnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 231 Chapter 20. EQQQnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 235 Chapter 21. EQQRMnn Messages . . . . . . . . . . . . . . ...

Page 7 - Notices

Notices References in this publication to IBM products, programs, or services do not implythat 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 orimply that only IBM’s product, program, or service...

Page 8 - Trademarks

Trademarks The following terms are trademarks of Tivoli Systems or IBM Corporation in theUnited States or other countries or both: Microsoft, Windows, Windows NT, and the Windows logo are trademarks orregistered trademarks of Microsoft Corporation. UNIX is a registered trademark in the United States...

Page 9 - Preface; How This Book Is Organized; vii

Preface This book describes messages issued by TME 10 Operations Planning and Control(TME 10 OPC), program number 5697-OPC. This book documents the messagesissued by these features: The TME 10 OPC controller The TME 10 OPC tracker The Tracker Agent for OS/2 enabler The Tracker Agent for OS/4...

Page 10 - TME 10 OPC Publications; Task; tuning the OPC installation.; viii

TME 10 OPC Publications This book is part of an extensive TME 10 OPC library. These books can help youuse TME 10 OPC more effectively: Task Publication Ordernumber Evaluating TME 10 OPC General Fact Sheet GH19-4370 Evaluating Tracker Agents Tracker Agent Features Fact Sheet GH19-4371 Planning TME 10...

Page 11 - TME 10 OPC Online Books; Updates to books between releases are provided in softcopy only.; Online Message Facility; These books describe IBM products that are related to TME 10 OPC:; Short Title; ix

TME 10 OPC Online Books All the books in the TME 10 OPC library, except the licensed publications, areavailable in displayable softcopy form on CD-ROM in the following SoftcopyCollection Kits: | MVS, SK2T-0710 | OS/390, SK2T-6700 TME 10 OPC Messages and Codes is also available as part of Online ...

Page 13 - Summary of TME 10 OPC Version 2 Release 2 Enhancements; Instrumentation for TME 10 Global Enterprise Manager; xi

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 competitiv...

Page 14 - xii

Page 15 - xiii

| 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...

Page 16 - Version 2 Release 1.0 Summary; xiv

| 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 QUEUELEN keyword of the JTOPTS | statement | STATIM Sets a new value for the STATIM keyword of the JTOP...

Page 17 - xv

Tracker agents New Tracker Agents are provided to control the workload on: | Digital OpenVMS Pyramid MIPS ABI Shared parm library in Sysplex environment MVS controllers and trackers can share common controller and trackerinitialization statements and started task JCLs, making it easier to instal...

Page 18 - Keyword; xvi

Batch command interface tool A batch command interface tool is supplied to perform most of the actionssupported 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 OPCVersion 2. The foll...

Page 19 - Changes to programming interfaces; The Programming Interface is extended as follows:; New and changed installation exits; TME 10 OPC Messages and Codes for the complete message; Table 3. Changes to Installation Exits; Exit name; Sample job tracking log write exit.; xvii

The MODIFY command has been extended to accept stop and start of theserver started tasks: F ssname, P=SERVS ssname, P=SERV Changes to programming interfaces The Programming Interface is extended as follows: UPDATE is supported for calendars, periods, workstations, and allworkstations closed. BROWSE ...

Page 20 - xviii

Page 21 - Chapter 1. Introduction; Message Format; EQQ; Where Messages Are Presented

Chapter 1. Introduction This manual explains all the error, warning, and information messages, as well asthe user abend codes and reason codes, that TME 10 OPC issues. The messages are listed in alphanumeric order by message identifier. To help youfind messages, the range of messages on a particular...

Page 22 - Introduction; HH; Is the hour, starting from midnight, in the range 00–23.; MM; Is the minute of the current hour, in the range 00–59.; SS; Is the second of the current minute, in the range 00–59.; msgnum; Is the message text in uppercase.; IS BEING STARTED; Data Entry Errors

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 a2-digit day-of-month number. For example, 02/03 meansFebruary 3. HH.MM.SS Is the current time-of-day: HH Is the hou...

Page 23 - Chapter 2. EQQATnn Messages; LU; SEND RECORDS WERE TRANSMITTED, RCV RECORDS WERE RECEIVED

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 ROUTOPTSinitialization statement defines one or more APPC destinations. System action: TME 10 OPC normal proc...

Page 24 - System action: The APPC tracker task terminates.; RC; EQQAT10E SEND TO DESTINATION:

EQQAT06E EQQAT11E EQQAT06E THE APPC TRACKER TASK RECEIVED UNRECOGNIZED DATA FROM DESTINATION: LU Explanation: Data received from a partner APPC program is not valid. System action: The APPC tracker task will free all resources allocated to this APPC conversation. The partnerprogram sending incorre...

Page 29 - Chapter 3. EQQAnnn Messages

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 toaccess it. Or, you do not have access authority to at least one of the following...

Page 30 - MOD

EQQA010E EQQA017E EQQA010E INVALID PARAMETER INPUT TO MODULE MOD Explanation: This message indicates a programming error. System action: The system waits for you to respond. User response: Contact your system programmer. System programmer response: Contact your IBM representative. EQQA011I THE APP...

Page 31 - OP HAS AN EXTERNAL PRED WS EWS, WHICH IS NOT FOUND; description database.; OCHCACT OR OCHCPEND

EQQA018E EQQA103E EQQA018E OP OP HAS AN EXTERNAL PRED WS EWS, WHICH IS NOT FOUND Explanation: Operation op has an external predecessor workstation (ews) that does not exist in the workstation description database. System action: The system waits for you to respond. User response: Enter correct dat...

Page 33 - The deadline time must be later than the input arrival time.

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...

Page 34 - Valid deadline WTO options are Y for Yes, and N for No.

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 savingthe application description as it is. System action: The times specified for the operation are accepted....

Page 36 - Valid job option characters are Y for yes, and N for no.

EQQA211E EQQA223E EQQA211E THE PRINT OPTION CHARACTER IS INVALID Explanation: Data entry error; see “Data Entry Errors” on page 2. Valid print option characters are A for always, and C for conditionally. EQQA212E WHEN TIME DEPENDENT = YES, SUPPRESS IF LATE MUST BE SPECIFIED Explanation: Data entry...

Page 37 - WRKOFF IS GREATER THAN PERIOD INTERVAL WRKINT

EQQA226E EQQA238E EQQA226E THE OPERATION NUMBER MUST BE SPECIFIED Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQA228E THE SPECIFIED SPECIAL RESOURCE HELD OPTION IS INVALID Explanation: Data entry error; see “Data Entry Errors” on page 2. Valid special resource held options a...

Page 38 - A stands for active, P for pending.

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. EQQA241E THE MAXIMUM 4 ACTIVE VERSIONS ALRE...

Page 39 - OP MAY HAVE ONLY ONE CPU PREDECESSOR; op) can have only one CPU internal predecessor.

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...

Page 40 - OP MUST HAVE THE SAME JOBNAME AS A CPU SUCCESSOR; op) must have the same job name as any of its CPU successors.; OP MUST HAVE THE SAME JOBNAME AS THE CPU PREDECESSOR; op) must have the same job name as its CPU predecessor.

EQQA255E EQQA265E EQQA255E JOB SETUP OP OP MUST HAVE THE SAME JOBNAME AS A CPU SUCCESSOR Explanation: The job setup operation number ( op) must have the same job name as any of its CPU successors. System action: The system waits for you to respond. User response: Enter a valid CPU successor job na...

Page 42 - A valid batch job type is T for trial run, or U for updating run.

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....

Page 43 - CNR IS NOT SUPPORTED

EQQA287E EQQA299I EQQA287E THE CONVERSION NUMBER CNR IS NOT SUPPORTED Explanation: This message indicates a programming error. System action: The system waits for you to respond. User response: Contact your system programmer. System programmer response: Contact your IBM representative. EQQA288E TH...

Page 45 - OP MUST HAVE A CPU PREDECESSOR; op) must have a CPU predecessor operation.

EQQA309E EQQA400E EQQA309E PRINT OPERATION OP MUST HAVE A CPU PREDECESSOR Explanation: The print operation (operation number op) must have a CPU predecessor operation. System action: The system waits for you to respond. User response: Enter a CPU operation number as the predecessor number. EQQA310...

Page 51 - Chapter 4. EQQCnnn Messages; TIME IN AROPTS STATEMENT IS NOT VALID; TIME must be a 4-digit decimal number in the format HHMM, where HH is

EQQC001I EQQC006E Chapter 4. EQQCnnn Messages EQQC001I THE AUTOMATIC RECOVERY SUBTASK HAS STARTED Explanation: The automatic job recovery subtask has been successfully initialized. System action: Automatic job recovery processing is started. User response: None. EQQC002E THE AUTOMATIC RECOVERY INI...

Page 52 - SERVICE INACTIVE; SERVICE was down.; FILE FILE; FILE is the name of the VSAM file that could not be opened.

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 torestart. System action: Automatic job recovery resumes normal processing but one or more req...

Page 53 - EQQC014W AUTOMATIC RECOVERY REQUEST FAILED DUE TO I/O ERROR; TME 10 OPC Diagnosis Guide and; EQQC022I AUTOMATIC RECOVERY ACTION POSTPONED FOR OPERATION

EQQC013W EQQC022I EQQC013W AUTOMATIC RECOVERY REQUEST FAILED, CANNOT ALLOCATE BUFFERS Explanation: A storage allocation error prevented automatic job recovery from checking whether or not recoveryshould be performed for the job that ended in error. This message may be followed by message EQQC045I ...

Page 55 - EQQC044I AUTO RECOVERY OF APPL; ADID DATE; EQQC045I AUTO RECOVERY INFO; operation; User response: Look up the meaning of reason code; RS in the list given in message EQQC047E. Review the

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 thatended in error, a RECOVER statement with a syntactical error was found. This message is followed...

Page 58 - SIZE; EQQC500E THE JCL LIBRARY, DDNAME EQQPRLIB, COULD NOT BE OPENED

EQQC061E EQQC500E EQQC061E AUTOMATIC RECOVERY FAILED, I/O ERROR Explanation: Automatic job recovery failed for the job that ended in error because an I/O error occurred. The I/Oerror occurred while the automatic job recovery subtask was determining whether recovery should be performed, orwhile the...

Page 61 - Chapter 5. EQQCLnnn Messages

Page 62 - EQQCL0GI

Page 63 - with the specified selection parameters.; appl in CP; appl in the OPC current plan.

Page 65 - EQQCL0XI

Page 66 - EQQCL1CI

EQQCL15I EQQCL1CI | EQQCL15I Internal successor released: OPNO( s_opnum) APPL(appl) | Explanation: OCL released the internal successor operation number s_opnum in the occurrence appl. | System action: Processing continues. | User response: None. | EQQCL16I External successor found for operation op...

Page 67 - EQQCL1DI

EQQCL1DI EQQCL44W | EQQCL1DI External predecessor deleted: PREAPPL( preappl) PREIA(iadt) | Explanation: OCL deleted an external predecessor definition. preappl is the predecessor occurrence ID, and iadt its | input arrival date and time. | System action: Processing continues. | User response: None...

Page 68 - EQQCL4CW

EQQCL45W EQQCL4CW | EQQCL45W Occurrence not found in the LTP: APPL( appl) IA(iadt) | Explanation: OCL attempted to modify or list the application occurrence appl, which does not exist in the long term | plan. iadt is the input arrival date and time used to search for the occurrence. | System actio...

Page 71 - EQQCL4SW; deadline; appl with IA iadt

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 corre...

Page 74 - library) or in the INIT instruction.

EQQCL5IE EQQCL5PE | EQQCL5IE APPL and GROUP are mutually exclusive keywords | Explanation: APPL and GROUP keywords were specified in the same ADD instruction. | System action: OCL terminates. | User response: Correct the instruction, then resubmit the job. | EQQCL5JE OPC subsystem id must be suppl...

Page 75 - wsname not found in the OPC database; wsname is not defined in the OPC Workstation database.; opnum in occurrence appl

EQQCLQE EQQCL5XE | EQQCLQE Workstation wsname not found in the OPC database | Explanation: Workstation wsname is not defined in the OPC Workstation database. | System action: OCL terminates. | User response: Correct the instruction, then resubmit the job. | EQQCL5RE Jobname must be specified for w...

Page 76 - EQQCL5YE; preopnum to operation opnum; or from the long term plan. A problem occurred.; opnum from the occurrence appl, but a problem occurred.

EQQCL5YE EQQCL65E | EQQCL5YE Not possible to define internal pred. preopnum to operation opnum | Explanation: OCL tried to define an internal predecessor to operation opnum, but a problem occurred. | System action: OCL terminates. | User response: Contact your IBM representative. | EQQCL5ZE Not po...

Page 77 - EQQCL6DE; month must be included between 01 and 12; day must be in the range

Page 78 - cmd command; s_opnum is the successor; opnum of occurrence appl; opnum in the occurrence appl, but a problem occurred.

Page 79 - specified in the initialization parameter DEFOPNO.

EQQCL6ME EQQCL6SE | EQQCL6ME Specify the OPNO() keyword or specify the default operation number | Explanation: The OPNO keyword is not specified. OCL tried to use the default operation number, which is not | specified in the initialization parameter DEFOPNO. | System action: OCL terminates. | User...

Page 80 - EQQCL6TE; input arrival date and time.

EQQCL6TE EQQCL70E | EQQCL6TE Can't have a dependency on itself: PREAPPL( p_appl) PREIA(iadt) | Explanation: In the long term plan, an occurrence cannot have a predecessor with the same occurrence ID and | input arrival date and time. | System action: OCL terminates. | User response: Correct the in...

Page 81 - opnum as a predecessor of s_opnum; internal successor to be released by the RELOP instruction.

EQQCL71E EQQCL78E | EQQCL71E OPNO() and EXCLOP() are mutually exclusive keywords | Explanation: OPNO and EXCLOP are mutually exclusive keywords. | System action: OCL terminates. | User response: Correct the instruction, then resubmit the job. | EQQCL72E Can't release the successor of operation opn...

Page 82 - EQQCL7GE; cal

EQQCL79E EQQCL7GE | EQQCL79E Can't delete the special resource: res_name OPNO(opnum) | Explanation: OCL tried to delete the special resource res_name from the operation opnum. | System action: OCL terminates. | User response: Contact your IBM representative. | EQQCL7AE Occurrence ID must be suppli...

Page 83 - parameter

EQQCL7HE EQQCL7KE | EQQCL7HE Not possible to write the message on dataset: dsname(WTOIN) | Explanation: OCL tried to the message text of the WTOR in the member WTOIN of dataset dsname. | System action: OCL terminates. | User response: Contact your IBM representative. | EQQCL7IE Invalid parameter: ...

Page 85 - Chapter 6. EQQDnnn Messages

EQQD001E EQQD011E Chapter 6. EQQDnnn Messages EQQD001E INVALID VALUE SPECIFIED FOR REPORT SELECTION Explanation: Data entry error; see “Data Entry Errors” on page 2. If you want a report, you must specify a Y; if you do not want a report, you must specify an N. EQQD002E START AND END DATES MUST NO...

Page 92 - SYSOUT request (request type

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 DELAYEDSYS...

Page 93 - given in hexadecimal.; ABCODE OPENING A SYSOUT DATA SET FOR JOBNAME(JOBNUM) IN

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 isspecified for JOBLOGRETRIE...

Page 97 - Chapter 7. EQQEXnn Messages

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 theinterface to the operation-initiation exit, EQQUX009, which is used to start operati...

Page 98 - TO BE LOST; User response: Contact your system programmer.; REQUEST; Problem determination: Review the TME 10 OPC message log dataset.

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 leastone queue element has been lost. System action: MVS/ESA recovery/termina...

Page 99 - Chapter 8. EQQEnnn Messages; NUMBER OF EVENTS SINCE THE PREVIOUS MESSAGE IS:

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 QUEUE LENGTH STATISTICS FOLLOW:TOTAL Q1 Q2 Q5 Q10 Q20 Q50 Q100 >100 CALLS Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q8 | Exp...

Page 109 - The status of the successor operation is already complete.

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 workstationthat conflicts with the information already ...

Page 110 - DDNAME; BECAUSE NO MATCHING OPERATION COULD BE FOUND IN CURRENT PLAN:; EXITREC

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 jobfrom hold. System action: The hold status of the current job is not changed. The Event Manager co...

Page 111 - MATCHING OPERATION WAS FOUND IN THE CURRENT PLAN:; System action: The Event Manager continues normal processing.; EVNTHDR EVENT RECORD: EXITREC

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 plandataset matches the operat...

Page 118 - WORKSTATION; EQQE096E THE STATUS KEYWORD MUST BE SPECIFIED

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. AnOPSTAT event definition statement specified a new stat...

Page 119 - OPERATION STATUS IS SS:; ALTERNATE WORKSTATION

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. AnOPSTAT event definition...

Page 121 - Chapter 9. EQQFnnn Messages; MEMBER IS DEFINED AS A DESTINATION IN ROUTOPTS BUT IS STARTED AS A; DQE

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 p...

Page 125 - Chapter 10. EQQGnnn Messages

EQQG001I EQQG004E Chapter 10. EQQGnnn Messages EQQG001I SUBTASK SUBTASK HAS STARTED Explanation: The subtask SUBTASK has been successfully initialized. System action: Processing for the subtask indicated is started. User response: None. EQQG002E INITIALIZATION OF SUBTASK SUBTASK FAILED. REASON COD...

Page 131 - Chapter 11. EQQHnnn Messages

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 ofthe ALERT init...

Page 132 - H21001 cannot have that many values.; H21101 SPECIFIED OR A KEYWORD IS MISSPELLED; H21101 is not valid for the keyword, or the keyword is misspelled.

EQQH206W EQQH214E EQQH206W A MISSING END OF COMMENT IS ASSUMED AT THE END OF THE STATEMENT Explanation: A start of comment delimiter (/*) has been detected, without a corresponding end of comment (*/). System action: TME 10 OPC assumes the comment ends after the control statement. User response: A...

Page 133 - H21901 is missing from the 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...

Page 135 - H40201 HAS NO ORIGIN WITHIN RULE VALIDITY.; H40201 has no origin within rule validity period.

EQQH308W EQQH502E EQQH308W DUPLICATE VALUE(S) H30801 IGNORED. Explanation: You have specified duplicate values. Only one of the values will be used. System action: Duplicate value removed. User response: Check the specified values, and correct them if necessary. EQQH309E THE SAVED RULE VALUE HAS B...

Page 137 - up to 5 error messages for an invalid rule.; XRSEL OR LEAVE BLANK

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 setto 'VALID RULE' if the parser returns 04 or lower, 'INVALID RULE' for all other return codes. The return code value ...

Page 139 - When the interval is calculated:; System action: The request is rejected.

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 outsidethe limits of the internal calendar When the interval is calculated: The start date of the interval i...

Page 141 - Chapter 12. EQQICnn Messages

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 ofOPC. This message documents the numb...

Page 143 - AD HAS AN INVALID INPUT ARRIVAL IA FOR AN; ST

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 invalidinput arrival date in one of its occurrence data. System actio...

Page 144 - FILE

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 theinput file. System programmer r...

Page 151 - Chapter 13. EQQJnnn Messages

EQQJ001I EQQJ010I Chapter 13. EQQJnnn Messages EQQJ001I ETT ACTIVATION/DEACTIVATION REQUEST WAS NOT CONFIRMED Explanation: You chose not to confirm the original request, and so it was ignored by TME 10 OPC. System action: None. User response: None. EQQJ002W ETT ACTIVATION REQUEST IGNORED SINCE ETT...

Page 152 - OCHCJOB OR OCHCRES

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 10OPC subsystem. System action: None. User response: You should exit from this panel, and then enter ...

Page 153 - ochcno or leave the field blank.; OCHCYES OR OCHCNO

EQQJ023E EQQJ029E EQQJ023E JOB NAME REPLACEMENT INFO MUST BE OCHCYES OR OCHCNO Explanation: ochcyes and ochcno are the national characters for 'Y' (yes) and 'N' (no). System action: The system waits for you to respond. User response: Enter correct data. EQQJ024E JOB NAME REPLACEMENT INFO MUST BE O...

Page 161 - COMP

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 sub...

Page 165 - LINE OF SCTN EXCEEDS LIMITS

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 ...

Page 166 - MEMBER IN ANY INPUT DATA SET; MEMBER; LINE OF SCTN; The variable name does not start with a

EQQJ578E EQQJ582E EQQJ578E THE EQQUX002 EXIT COULD NOT FIND JOB MEMBER IN ANY INPUT DATA SET Explanation: TME 10 OPC was attempting to submit a job to JES for a ready operation on a computer workstation.However, no JCL for this operation is saved in the JCL repository dataset, and the joblib I/O e...

Page 171 - APPL, JOBNAME IS MEMBER; Keep status R or extended status RE; TID ALREADY EXISTS

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 forstorage failed. System action: The operation st...

Page 172 - CHR IN POSITION POS IS INVALID

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 ...

Page 175 - Chapter 14. EQQKnnn Messages; The valid-to date must be later than the valid-from date.

EQQK000E EQQK022E Chapter 14. EQQKnnn Messages EQQK000E VALID-TO SPECIFICATION PRECEDES VALID-FROM SPECIFICATION Explanation: Data entry error; see “Data Entry Errors” on page 2. The valid-to date must be later than the valid-from date. EQQK001E OI ALREADY EXISTS IN OI DATA BASE Explanation: You h...

Page 176 - or because no lines existed in the OI record you attempted to store.

EQQK023W EQQK031E EQQK023W THE OPERATOR INSTRUCTION CONTAINS NO TEXT Explanation: The OI you selected does not contain any text. System action: The system waits for you to respond. User response: If this OI should contain text, use the OI dialog to add the desired text. | EQQK024W IT IS NOT POSSIB...

Page 177 - The operation number must be numeric.

EQQK032E EQQK043E EQQK032E THE NAME DOES NOT START WITH AN ALPHABETIC CHARACTER Explanation: Data entry error; see “Data Entry Errors” on page 2. | EQQK033E THE OPERATION NUMBER MUST BE IN THE RANGE 1 - 255 Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQK034E THE NAME CONTAIN...

Page 179 - AD has no operation WS OP.; System action: The system waits for you to respond.

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 forthe corresponding operation. The validation failed because the application description AD has no operation WS...

Page 181 - Chapter 15. EQQLnnn Messages

EQQL000E EQQL006I Chapter 15. EQQLnnn Messages EQQL000E YOU ARE NOT AUTHORIZED TO ACCESS THE LTP DATA SET Explanation: You have attempted to access the LTP dataset but you are not authorized to do so. Or, you do nothave access authority to at least one of the following TME 10 OPC resources that ar...

Page 183 - LISTITEM DEFINED FOR THIS OCCURRENCE

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 andend. System action: The system waits for you to respond. User response: Check the displayed LTP start...

Page 184 - Make a trial plan, but no LTP exists.

EQQL310E EQQL464E EQQL310E THE LTP DATA SET IS EMPTY - NO HEADER FOUND Explanation: You have attempted to do one of the following: Submit an LTP batch job, but there is no header record in the LTP dataset Make a trial plan, but no LTP exists. System action: The system waits for you to respond....

Page 187 - These are possible explanations:

EQQL504E EQQL512E EQQL504E APPLICATION DEPAID NOT FOUND Explanation: The application ( DEPAID) specified in the LTP occurrence was not found in the application description database. The application might have been deleted from the application description database or the user does nothave access to...

Page 188 - panel by typing the row command RG, or from the; panel by erasing the group definition ID field.; LTPPNEND, LTPPNENT; LTPCHIAD, LTPCHIAT is outside the occurrence time limit.

EQQL513E EQQL567I EQQL513E THE VARIABLE TABLE NAME CONTAINS AN INVALID CHARACTER Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQL514E YOU ARE NOT AUTHORIZED TO READ THE JCL VARIABLE TABLE DATA BASE Explanation: You have attempted to refer to a JCL variable table. To do this, ...

Page 191 - Chapter 16. EQQMnnn Messages

EQQM000E EQQM011I Chapter 16. EQQMnnn Messages EQQM000E YOU DO NOT HAVE AUTHORITY TO ACCESS THE CURRENT PLAN Explanation: To use the function you selected, you must have access authority to the current plan. System action: The request is rejected and the system waits for you to respond. User respo...

Page 194 - MAAID MAIMD MAIMT IGNORED WHILE CREATING NEW PLAN

EQQM027E EQQM033E EQQM027E REQUEST FAILED BECAUSE OF SUBSYSTEM ERROR. REASON: XSSRS Explanation: The modify current plan request failed because of an error in the TME 10 OPC subsystem. System action: The modify current plan function is terminated; no updates are made. Message EQQM xssrsE is writte...

Page 196 - WSID, HAS BEEN SET TO STAT STATUS

EQQM063E EQQM100W EQQM063E THE ALTERNATE WS NAME IS NOT FOUND IN THE DATA BASE Explanation: The alternate workstation is not defined in the workstation database. System action: The status of the workstation does not change. Reroute is not performed to an alternate WS. User response: Correct the na...

Page 197 - MPLENDI; MOJBN MUST BE SAME IN JOB SETUP, PROCESS, AND PRINT

EQQM104E EQQM115E EQQM104E NO APPLICATIONS MET THE SELECTION CRITERIA Explanation: No applications were found in the application description database, which met the selection criteria thatyou specified. System action: The system waits for you to respond. User response: Change the selection criteri...

Page 200 - EQQM161E MODIFY CP REQUEST FAILED, INSUFFICIENT STORAGE. REASON:; RS; MONUM DEFINES TOO MANY RESOURCES, FIRST MAXRES USED

EQQM161E EQQM171E EQQM161E MODIFY CP REQUEST FAILED, INSUFFICIENT STORAGE. REASON: RS Explanation: A request to create or modify an occurrence in the current plan failed due to storage allocation failure.The reason code provides debugging information for IBM personnel. System action: If this is a ...

Page 201 - AD

EQQM172E EQQM204E EQQM172E MAXIMUM NUMBER OF OCCURRENCES EXISTS, FAILED TO ADD AD | Explanation: No more occurrences can be added to the Current Plan because the maximum number of | occurrences—32767 or the number specified in the MAXOCCNUM option of the JTOPTS statement—has been | reached. System...

Page 203 - MOONU

EQQM219E EQQM226E EQQM219E OPERATION NUMBER MUST NOT BE CHANGED FROM MOONU Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQM220E DEPENDENCY TYPE MUST BE P-PREDECESSOR OR S-SUCCESSOR Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQM221E NO OPERATIONS IN CUR...

Page 211 - OCHCDFR ,OCHCYES OR OCHCNO; GO

EQQM331E EQQM337E EQQM331E THE ONLY VALID VALUES ARE OCHCDFR ,OCHCYES OR OCHCNO Explanation: You have entered an incorrect action for the catalog management function. System action: The system waits for you to respond. User response: Enter correct value and press enter. EQQM332I THE CATALOG MANAGE...

Page 215 - STEPNAME PROC STEP PROCNAME

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 withinthe group. If th...

Page 218 - OCHCNO SO GDG CANNOT BE RESOLVED

EQQM381I EQQM387W EQQM381I OPC/ESA HAS FOUND NO INCONSISTENCIES IN THE JCL FOR A RESTART Explanation: TME 10 OPC has investigated the JCL for restart, and has found no errors. The operation may berestarted. System action: None. User response: Leave the panel with END command to save the JCL and in...

Page 219 - for the status of datasets used in this step is recommended.

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 rec...

Page 220 - CANCEL; EQQM398W NO STEPS HAVE BEEN SELECTED FOR THIS STEP RESTART

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 butthe joblog is created on a non-MVS platform. System action: The panel will be redisplayed with...

Page 222 - of occurrences was created.; USER NOT AUTHORIZED TO ACCESS RESOURCE: RESOURCE; RESOURCE, but the user making the

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 EQQJBLIBfile. System action: Processing continues. User response: Verify if the job needs to be changed before ...

Page 225 - OPER SPECIAL RESOURCE: SPR; EQQM925E PRINT OPERATION HAS NO PREDECESSOR 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 reasoncodes ( RS) indicate why: 921 The last i...

Page 227 - WSNAME) that is not defined to

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 dialoguser. Prob...

Page 228 - WSNAME) that is not defined to the; EQQM936E NORMAL MODE MANAGER WILL RESTART FROM CHECKPOINT; APPL; EQQM950E INPUT ARRIVAL NOT WITHIN CURRENT PLAN, ENDS; CPE REQUEST; System action: The request is terminated with an error return code.

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 systemactivated for step-level restart and where the required joblogs will be retrieved at the time of your request. TME 10OPC has...

Page 229 - ADID to the

EQQM951E EQQM954E EQQM951E FAILED TO ADD APPLICATION ADID REASON: CANNOT READ CURRENT PLAN RECORD Explanation: A request to create an occurrence on the current plan failed due to an I/O error. System action: The request is terminated and the processing continues with the next request. Problem dete...

Page 232 - MTD; EQQM991E ERROR DURING MCP UPDATE.; MODULE

EQQM976W EQQM991E occurrences, and then try to add the occurrence again. If your current plan regularly contains a large number ofoccurrences, you should consider shortening the length of the Current Plan in future daily planning runs. EQQM976W ONE OR MORE OF THE EXTERNAL DEPENDENCIES OF OPER OPER...

Page 233 - Chapter 17. EQQNnnn Messages; EQQN001I REFRESH IS COMPLETE. CURRENT PLAN IS NO LONGER AVAILABLE; OPRINDEX; EQQN003E VSAM ABENDED WHILE ATTEMPTING TO CLOSE DDNAME

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 bepropagated to all active subtasks. The Normal Mode Manager will start its own te...

Page 238 - EQQN024W VSAM LSR BUFFER DELETE FAILED FOR VSAM FILE; VRPRC; FROM CHECKPOINT. THE DATA SET HAS BEEN TRUNCATED

EQQN023I EQQN026W EQQN023I VSAM LSR BUFFERS HAVE BEEN SUCCESSFULLY DELETED FOR VSAM FILE DDNAME Explanation: TME 10 OPC successfully deleted the buffer pool for the file indicated in the message. System action: None. User response: None. EQQN024W VSAM LSR BUFFER DELETE FAILED FOR VSAM FILE DDNAME ...

Page 244 - DDNAME, IS NOT OPEN

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 werefound while processing input NOERROR statements. System action: The NOERROR table is not changed. TME 10 OPC con...

Page 245 - MAXJT, CURRENT JOB TRACKING LOG IS CURJT

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 DUALkeywords of the JTOPTS initialization statement is not defined. System action: The Normal M...

Page 246 - SYNMSG

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 logcan no longer be used. System action: The Nor...

Page 248 - MODULE, COULD NOT BE LOADED

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 ...

Page 249 - Chapter 18. EQQOnnn Messages; APP

EQQO001I EQQO006E Chapter 18. EQQOnnn Messages EQQO001I APPC TASK INITIALIZATION IS COMPLETE Explanation: The APPC task has completed initialization processing. System action: Processing continues. Operator response: None. EQQO002E APPC TASK ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT APP ...

Page 250 - EQQO008E THE APPC TASK IGNORED THE FOLLOWING INBOUND APPC BUFFER; Explanation: An invalid buffer was received.

EQQO007E EQQO011E EQQO007E THE APPC TASK IGNORED THE FOLLOWING ELEMENT ON THE APPC QUEUE DQE Explanation: An invalid allocate request, or outbound reply was found on the APPC queue. System action: Processing continues. System programmer response: If the element was an allocate request from a user ...

Page 251 - Chapter 19. EQQPnnn Messages; NAME IS ALREADY ACTIVE, IT CANNOT START AGAIN; ELEM

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 startedby the TME 10 OPC subsystem if APPC(YES) is specified in the OPCOPTS initialization statement. System...

Page 254 - EQQP015E FAILED TO SET UP COMMUNICATION WITH SERVER; LU shows the LU name of the

EQQP015E EQQP015E EQQP015E FAILED TO SET UP COMMUNICATION WITH SERVER LU, RC RC Explanation: An APPC/MVS Allocate request issued for server communication failed. LU shows the LU name of the server. RC shows the return code of the Allocate request. System action: The user cannot start the TME 10 OP...

Page 255 - Chapter 20. EQQQnnn Messages; OCHCYES OR A ochcno; ochcyes or a ochcno.

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–...

Page 257 - OCHCYES, ochcno or left blank

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. EQQ...

Page 263 - Chapter 21. EQQRMnn Messages

EQQRM01I EQQRM07W Chapter 21. EQQRMnn Messages EQQRM01I RODM SUBTASK INITIALIZATION IS COMPLETE Explanation: The RODM subtask has completed initialization processing. System action: Processing continues. Operator response: None. EQQRM02E RODM SUBTASK ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELE...

Page 267 - API to add a notify subscription for a RODM class.

EQQRM29W EQQRM29W | EQQRM29W SUBSCRIBE FOR RODM CLASS NAME FAILED. RC IS RC, REASON IS RSN OPC/ESA WILL | RETRY EVERY 3 MINUTES | Explanation: A nonzero return code was returned by a RODM system when the RODM subtask called the RODM | API to add a notify subscription for a RODM class. | System act...

Page 269 - Chapter 22. EQQRnnn Messages; ERC£ TERMINATED; ERC processing is terminated.; ERC£ HAS BEEN REQUESTED TO STOP; ERC restart processing continues.

EQQR000E EQQR013E Chapter 22. EQQRnnn Messages EQQR000E YOU ARE NOT AUTHORIZED TO ACCESS THE READY LIST Explanation: You have attempted to access the ready list but you are not authorized to access it. System action: The requested access to the ready list is rejected. User response: Contact your s...

Page 274 - JSADID JSIAD JSIAT JSOPNUM); JSADID JSIAD JSIAT JSOPNUM. The

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 meanscancel the request. System action: The status is not changed. User response: None. EQQR300E PRIORITY MUST BE A NUMBE...

Page 277 - An error type is required when setting the status to

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 bedone. The error code OSEQ indicates that a job began to execute before all the predecesso...

Page 283 - Chapter 23. EQQSUnn Messages

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 termina...

Page 284 - USER, WHOSE AUTHORITY COULD NOT BE DETERMINED; NNNN

EQQSU07E EQQSU12I EQQSU07E THE SUBMIT TASK ABENDED WHILE PROCESSING THE FOLLOWING REQUEST: REQUEST Explanation: An abend prevented the submit task from processing a queue element. System action: MVS recovery/termination is requested to generate a dump. The submit task attempts to continuenormal pr...

Page 287 - Chapter 24. EQQSnnn Messages

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 r...

Page 288 - OCHCYES AND OCHCNO

EQQS100E EQQS107E EQQS100E THE ONLY VALID VALUES ARE OCHCYES AND OCHCNO Explanation: An attempt was made to specify an invalid value in the AVAIL column. System action: The system waits for you to respond. User response: Enter a correct value in the AVAIL column. EQQS101E YOU ARE NOT AUTHORIZED TO...

Page 289 - STT

EQQS300E EQQS309E EQQS300E PRIORITY MUST BE A NUMBER FROM 1 - 9 Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQS301E THE MCP ADDED INDICATOR MUST BE OCHCYES OR OCHCNO Explanation: Data entry error; see “Data Entry Errors” on page 2. ochcyes is the national language character ...

Page 290 - been changed after the list data was displayed.

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 theselection criteria or you were not authorized to access those that were found. System action: None. User response: N...

Page 291 - Chapter 25. EQQTTnn Messages

EQQTT01I EQQTT05E Chapter 25. EQQTTnn Messages EQQTT01I THE TCP/IP COMMUNICATION TASK HAS STARTED Explanation: The TCP/IP communication task has successfully completed initialization. System action: The TCP/IP communication task processing continues. User response: None. EQQTT02I THE TCP/IP COMMUN...

Page 292 - REQUESTS TO BE LOST

EQQTT06E EQQTT09E EQQTT06E A SEVERE ERROR IN THE TCP/IP COMMUNICATION TASK HAS CAUSED ONE OR MORE REQUESTS TO BE LOST Explanation: The TCP/IP communication task encountered an error processing elements on the TATQ. As a result,at least one queue element has been lost. System action: MVS/ESA recove...

Page 294 - EQQTT17E TCP KEYWORD VALUE,; DEST has not responded to a submit

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 aftera restart. Attempts are made ev...

Page 295 - Chapter 26. EQQTnnn Messages; CALENDAR IS BEING UPDATED BY ANOTHER USER

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 ...

Page 296 - CALENDAR NOT CREATED - MAXIMUM NUMBER EXCEEDED

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 accor...

Page 297 - PERIOD IS BEING UPDATED BY ANOTHER USER; PERIOD because it is being updated by another user.

EQQT025E EQQT106I EQQT025E WORK DAY END TIME MUST BE SPECIFIED Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQT026E SPECIFY A VALID DAY OR DATE IN USER DEFINED FORMAT Explanation: A valid week day or specific date must be given in the user specified format. EQQT030E END DATE ...

Page 298 - PERIOD NOT CREATED - ALREADY EXISTS

EQQT108E EQQT121E EQQT108E PERIOD PERIOD NOT CREATED - ALREADY EXISTS Explanation: The calendar period PERIOD you specified could not be created because it already exists in the calendar database. System action: The system waits for you to respond. User response: Enter a unique period name. If you...

Page 301 - Chapter 27. EQQUnnn Messages; UUFUNC; UUFUNC OF UUUSUBS IS HANDLED

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 t...

Page 303 - Chapter 28. EQQVnnn Messages

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 duplicateof an already specified name. These names are the application names of potential ...

Page 309 - LU' SESSION PARAMETERS

EQQV038E EQQV043E EQQV038E DESTINATION LU INCONSISTENTLY SPECIFIED Explanation: A destination that runs TME 10 OPC NCF has been specified on the ROUTOPTS initializationstatement OPCAV1R2 keyword. System action: NCF processing continues. System programmer response: Correct the ROUTOPTS initializati...

Page 310 - EQQV044E OPNDST FAILURE WHEN CONFIRMING SESSION WITH TRACKER '

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 aremote tracker failed. The most likely reason for the failure is that there is no active route back to the trac...

Page 311 - Chapter 29. EQQWLnn Messages

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. Thismessage may also be caused by a system failure or by a workstation becoming available aga...

Page 315 - Chapter 30. EQQWnnn Messages

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 toaccess it. Or, you do not have access authority to at least one of the following ...

Page 317 - System action: The event writer attempts to continue processing.

EQQW014E EQQW017E EQQW014E THE JCC TASK ABENDED WHILE PROCESSING THE FOLLOWING EXIT RECORD: EXITREC Explanation: An abend prevented the JCC from processing all SYSOUT datasets for a batch job. System action: MVS recovery/termination is requested to generate a dump. The JCC attempts to continue nor...

Page 318 - CLASS IS ALREADY BEING PROCESSED BY ANOTHER JCC TASK; information request is either a status request (request type

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 beingprocessed by another JCC subtask on the same MVS system. The SYSOUT class can only be processed ...

Page 320 - BCOL AND ECOL IN MEMBER MEMBER IN; MSGREC

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 thiserror is that the JCC message library could not be opened or that the library is incorrectly defined. It is also ...

Page 321 - JOBNAME(JOBNUM) WILL NOT BE RELEASED. REPEATED RETRIES HAVE FAILED; DSNAME; ABCODE OPENING A SYSOUT DATA SET FOR JOBNAME(JOBNUM) DDNAME:

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 torelease job JOBNAME(JOBNUM) from hold status. System action: No more attempts to release the...

Page 324 - DDNAME has been allocated with an invalid logical record; JOBNAME JOBNUM DOES NOT CONTAIN ALL DATASETS REQUIRED BY THE

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 thesubmit/release dataset to the DRVP macro. Th...

Page 325 - JOBNAME JOBNUM HAS NO HELD SYSOUT IN CLASS CLASS; CLASS, but job JOBNAME with job ID; SKIPLIM IS NOT VALID

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...

Page 328 - DDNAME IS INCOMPATIBLE WITH THE DEVICE TYPE

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 isnormally caused by moving the dataset to a different device type. Note: This message may...

Page 331 - value, first set the access method name.

EQQW207E EQQW215E EQQW207E CAPACITY OF PARALLEL SERVERS INVALID OR NOT DEFINED Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQW208E RESOURCE CAPACITY IS NOT DEFINED OR IT IS INVALID Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQW209E THE STANDARD DAY CA...

Page 336 - DDNAME COULD NOT BE OPENED; MEMBER FOR EQQUX002 EXIT

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 plandataset. System action: The workstation analyzer continues...

Page 338 - TME 10 OPC Customization and Tuning for instructions.; MEMBER IN APPLICATION APPL SPECIFIES JOB NAME CURNAME. THE; CURNAME

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 upd...

Page 339 - OPNO; STCNAME IS DEFINED AS A SUBSYSTEM THAT IS NOT MANAGED BY JES. OPC/ESA; emin the SYS1.PARMLIB dataset to see if the STC

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 ...

Page 346 - TME 10 OPC Customization and Tuning contains

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 addressspace, or the DDNAME specifies DD DUMMY. System action: The submittor task will not checkpoint submit requests, but ...

Page 347 - Chapter 31. EQQXnnn Messages

EQQX000E EQQX011E Chapter 31. EQQXnnn Messages EQQX000E XROW IS NOT A VALID ROW COMMAND Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX001E ZCMD IS NOT A VALID PRIMARY COMMAND Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX002E A ROW CANNOT BE SELECTED...

Page 350 - SUBFUNC

EQQX039E EQQX049E EQQX039E HILITE ATTRIBUTE MUST BE ONE OF THOSE LISTED ON THE PANEL Explanation: Data entry error; see “Data Entry Errors” on page 2. EQQX040I THE JOB HAS BEEN SUBMITTED FOR SUBFUNC Explanation: The job has been submitted. System action: Normal processing continues. User response:...

Page 353 - XOPCNM has been restarted you are no longer connected to it.

EQQX119E EQQX124E EQQX119E LOGOFF REQUEST REJECTED, USER IS NOT LOGGED ON Explanation: You have attempted to disconnect a session from TME 10 OPC, but you were not connected. System action: None. User response: You can determine why you are logged off in the TME 10 OPC message log. (TME 10 OPC has...

Page 354 - REQUEST RESOURCE MEMBER

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 toTME 10 OPC. System action: The system waits for you to respond. User response: Log off from TSO and then log on again. If the ...

Page 355 - a record management request.

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 servicesubtask is not active. System action: The request is rejected. User response: Contact your system programmer. System...

Page 356 - DB RECORD AT OFFSET OFFS, REASON CODE: XSSRS

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 toopen a logical VSAM file. System action: The request is rejected. User response: Try again. If the er...

Page 358 - RESOURCE NOT RECOGNIZED; RESOURCE is unknown to

EQQX161E EQQX198E EQQX161E AN INTERNAL OPC/ESA CONTROL BLOCK IS IN ERROR Explanation: An internal TME 10 OPC control block is in error. System action: The system waits for you to respond. User response: Contact your system programmer. System programmer response: Ensure that the correct load module...

Page 359 - OP DEADLINE EARLIER THAN OPERATION INPUT ARRIVAL

EQQX220E EQQX259E EQQX220E THE INPUT ENTERED IS TOO LONG Explanation: Data entry error; see “Data Entry Errors” on page 2. The longest value accepted is HH.MM, where: HH The hour, in the range 00–24 MM The minute EQQX226E HOUR PART OF DURATION MUST BE A NUMBER BETWEEN 0 AND 99 Explanation: Data en...

Page 362 - TME 10 OPC Installation Guide.

EQQX269E EQQX300E EQQX269E THE LTP DATA SET IS BEING USED BY A BATCH FUNCTION, TRY LATER Explanation: You cannot access the long-term plan dataset because it is being used by a batch function. System action: The request is rejected. User response: Try again later. EQQX270E THE JS DATA SET IS IN US...

Page 368 - CALID IN AD AD

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 d...

Page 370 - FDRULE IS INVALID; Normal offset-based run cycles; IAT IS INVALID

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 ...

Page 371 - DLINET IS INVALID; WS DOES NOT EXIST

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) ...

Page 374 - WS OP DEADLINE TIME IS INVALID

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...

Page 379 - WS OP DOES NOT EXIST; WS OP

EQQX366E EQQX369E EQQX366E A PREDECESSOR TO OPERATION WS OP DOES NOT EXIST Explanation: One predecessor for the indicated operation could not be found in the application description record. System action: The request to write the record is rejected. Problem determination: Look in the diagnostic fi...

Page 384 - , each byte must be in the range X; System action: The data is rejected.

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 ...

Page 386 - OWNER CONTAINS LOWER CASE CHARACTERS

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 ...

Page 387 - CALID IS INVALID

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 ...

Page 394 - AEC specifies an updating function that is not supported.; IAD IAT AD CANNOT HAVE A DEPENDENCY ON ITSELF

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 contro...

Page 395 - RUNPER

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...

Page 403 - EQQX614E REQUEST FAILED, SEVERE ERROR AT SERVER; EQQX615E FAILED TO SET UP COMMUNICATION WITH SERVER; LU shows the LU name of; EQQX617E SECURITY ENVIRONMENT CREATED HAS FAILED, SAF RC

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...

Page 405 - Chapter 32. EQQYnnn Messages

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 hasrevealed no error. System action: Processing continues. User response: None. EQQY002I STATE...

Page 407 - VADRN IN APPLICATION VADID; VADRN contains an error. Messages that precede this

EQQY021E EQQY035E EQQY021E SUBSYS SUBS IS SPECIFIED IN OPTIONS STATEMENT, IT IS SET TO YSUBS IN THE INIT STATEMENT OF THE EQQYPARM FILE Explanation: Two different subsystem names are specified. System action: The record being created is considered in error and is not created. The following stateme...

Page 425 - Chapter 33. EQQZnnn Messages; JOBNAME. NAME MUST BE 4 CHARACTERS OR LESS; SUBTASK; SUBTASK IS BEING STARTED

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 haveterminated. EQQZ...

Page 431 - DDNAME IS USED BY ANOTHER

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 anotherTME 10 OPC subsystem. System action: The subsystem te...

Page 432 - SUBTASK ENDED UNEXPECTEDLY

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 e...

Page 433 - DISP, IS NOT RECOGNIZED

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 inputdataset for TME 10 OPC. System action: TME 10 OPC is terminated. Message EQQZ054E is issu...

Page 434 - NJENODE FOR JOBS HELD ON THIS NODE; CMDCHAR; CARD FURTHER STATEMENT PROCESSING STOPPED

EQQZ062W EQQZ068E EQQZ062W THE OPC/ESA START/STOP USER EXIT MODULE COULD NOT BE LOADED Explanation: TME 10 OPC could not locate the subsystem start/stop exit load module EQQUX000. System action: The subsystem start/stop exit will not be used by TME 10 OPC. System programmer response: If the subsys...

Page 435 - issuing JES

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 notsupported. System action: TME 10 OPC initialization fails. System programmer response: Change the ...

Page 441 - focal point service for networked

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 TRROPTSinitialization statement requests an XCF destination, your sys...

Page 446 - During initialization of the Event Writer task.

EQQZ148E EQQZ161E EQQZ148E HOUR MUST BE IN THE RANGE 0 TO 23 Explanation: A time value has been specified where the hour number is not valid. System action: Processing continues. System programmer response: Reenter the time value and specify an hour number in the range 0 through 23. EQQZ149E MINUT...

Page 450 - PARMREC

EQQZ180E EQQZ186I EQQZ180E INCONSISTENT DEFINITION OF EXIT STATEMENT AND JOBLOGRETRIEVAL KEYWORD Explanation: You have specified the JOBLOGRETRIEVAL keyword with value DELAYED or DELAYEDEXIT. Thevalue implies the use of a user exit, UX010, that has not been defined to TME 10 OPC. System action: TM...

Page 453 - HEARTBEAT

EQQZ203I EQQZ204I | EQQZ203I TRACKER TYPE TRACKER TRACKER NAME : TRACKER ADDRESS TRACKER STATUS | Explanation: Provides information about the status of a tracker connected to an OPC controller. | TRACKER TYPE The type of tracker. It can be one of the following values: | SNA | XCF | DASD | TCP | US...

Page 457 - Chapter 34. EQQnnnn Messages

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 ' )....

Page 460 - SDATE STIME - EDATE ETIME is outside the current range of the

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 err...

Page 461 - OPERATION for the application description APPL does not; EQQ0308E NO FIRST AND/OR LAST OPERATION IN APPLICATION NETWORK

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 todaily planning could therefore be incomplete or out-of-date. System action: The daily plan bat...

Page 462 - SUBSYS NOT ACTIVE OR NOT REACHED

EQQ0309E EQQ0313E EQQ0309E APPL **************** ******** **.** INVOLVED IN DEPENDENCY LOOP Explanation: This message is issued together with message EQQ0308E. It lists the applications involved in adependency loop. System action: No new current plan is produced; however, a printed plan is produce...

Page 467 - APPL. This message is; WRONG WS NAME

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 theapplication APPL. System action: The daily planning program continues processing. User response: Us...

Page 469 - SDATE STIME EARLIER THAN CURRENT PLAN END

EQQ0344E EQQ0349I EQQ0344E INVALID TRIAL TYPE Explanation: The daily planning trial type was not correctly specified. You can specify only one of the followingoptions: N For Extending Current Plan Period — Trial C For Replanning Current Plan Period — Trial F For Producing Daily Plan — Trial. Syste...

Page 470 - Is already completed or deleted; System action: The daily planning program continues processing.

EQQ0350E EQQ0354W EQQ0350E PERIOD START LATER THAN LAST BACKUP TIME Explanation: Reporting can only be requested for time periods less recent than the last old current plan. The oldcurrent plan is a backup copy of the current plan and is updated either after every certain number of events (specifi...

Page 471 - DLATEXT; DEPENDENCY LOOP FOUND IN AN APPLICATION NETWORK

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/orOCP. System action: The job continues User response: Check the flagged oc...

Page 472 - The variable; SUGGESTED DEPENDENCIES CAUSING LOOP ARE:

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. Themessage is always followed by a set of messages, each containing identification of one operation in the loop. LOOP: OP OPID JOB...

Page 475 - WSID; ADID DATE TIME TO ADIX DATX TIMX

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 j...

Page 477 - ADID DOES NOT EXIST IN THE AD DATA BASE

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 thesame as the current date. System action: The job is terminated. User response: Specify a valid date. EQQ0501E INVALID REPORT TYP...

Page 479 - RULE; EQQ0519W BACKUP OF THE LONG TERM PLAN DATA SET FAILED; Specific application not found

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-termplan but the long-term plan backup...

Page 488 - specified in the special resource database.; RESNAME DEFAULT WERE RESET

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 aresource is kept in the current plan (or NCP). The resource definition...

Page 493 - FUNC FAILED FOR FILE MSG: SYNADMSG CALLING MODULE IS MODULE; FUNC against the file FILE but the attempt failed. The

EQQ0959E EQQ1457E EQQ0959E FUNC FAILED FOR FILE MSG: SYNADMSG CALLING MODULE IS MODULE Explanation: A batch program attempted to do the function FUNC against the file FILE but the attempt failed. The I/O request is from module MODULE. System action: The job is terminated. Problem determination: Th...

Page 495 - WSNAME; EQQ2015W AN INTERNAL PREDECESSOR IN APPLICATION

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 s...

Page 496 - RSN

EQQ2016E EQQ2018W EQQ2016E OPERATION OPERNRIN APPLICATION APPLIDIS TOO LARGE TO BE SAVED IN THE NEW CURRENT PLAN DATA SET. THE FAILING OPERATION CONTAINS PREDNRDEPENDENCIES AND SPECNRSPECIAL RESOURCES Explanation: The Daily Plan program was unable to create an operation record because it would be ...

Page 498 - has been stopped, or has abended, or the specified name is incorrect.; MODNAME LOAD FAILED; MODNAME failed to load during the daily planning batch run.; System action: The daily planning batch job is stopped.

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. Syste...

Page 499 - Chapter 35. Abend Codes; This chapter lists the TME 10 OPC abend codes in numeric order.

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 continuedprocessing impossible. (Note: Message EQQV015E is issued only if request parameter list (RPL...

Page 501 - Chapter 36. Reason Codes

Chapter 36. Reason Codes The following table lists the reason codes that can appear in message EQQG005E or EQQ0170W. Formore 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 ...

Page 507 - Completion codes that are returned by batch job EQQPDLF; EQQPDLF Batch Program Condition Codes; EQQPDLF returns one of the following codes upon completion.

00 44 Chapter 37. TME 10 OPC Batch Program Codes andMessages This chapter describes the TME 10 OPC batch program codes and messages: Completion codes that are returned by batch job EQQPDLF Write-to-operator (WTO) messages that are generated by batch job EQQPURGE EQQPDLF Batch Program Condition...

Page 508 - EQQPURGE Batch Program WTO Messages

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 charact...

Page 510 - Communicating Your Comments to IBM; If you prefer to send comments electronically, use this network ID:

Communicating Your Comments to IBM TME 10 Operations Planning and ControlMessages and CodesVersion 2 Release 2 Publication No. SH19-4480-01 If you especially like or dislike anything about this book, please use one of the methodslisted below to send your comments to IBM. Whichever method you choose,...

IBM SH19-4480-01 - Manual

Table of Contents:

Summary

Other IBM Models