The Acrobat PDF Format

Transcription

1 Messages

2 This manual applies to ThruPut Manager Version 7 Release 1.0 PTF level 7109 and to all further releases until otherwise indicated. This material contains proprietary information on ThruPut Manager. Use of this manual is subject to the terms of the user s software license agreement for ThruPut Manager. The complete list of manuals relevant to this release is available from the Customer Center on from where any of the manuals may be downloaded. ThruPut Manager is a registered trademark of MVS Solutions Inc. TM/Service Level Manager, TM/Production Control Services, TM/Drive Booking Services, TM/Dataset Contention Services, TM/Job Binding Services, TM/User Control Services, and TM/JES3 Compatibility Services are trademarks of MVS Solutions Inc. Other trademarks and registered trademarks used in this document are the property of their respective owners and are to be regarded as appearing with the appropriate or symbol to 2017 MVS Solutions Inc. All rights reserved. The Acrobat PDF Format This set of manuals has been formatted to make it suitable for soft copy as well as hard copy formats. If reading the manual online, note that: Entries in the Table of Contents are hot-linked and can be used for document navigation. Other cross-references appear in blue type and are also hot-linked for easy navigation. For best results, turn on the Bookmarks feature in your Acrobat PDF reader.

3 Summary of Changes V7R (April 2017) V7R (February 2017) V7R (May 2016) V7R (November 2015) V7R (July 2015) V7R (July 2014) The following messages have been added or substantially changed: DTM1252I, DTM1254I, DTM1255I, DTM1259I, DTM3233I, DTM4472I, DTM8182E, DTM8183E, DTM8184I, DTM8185E, DTM8213I, DTM8219I, DTM8233I. The following messages have been added or substantially changed: DTM2347E, DTM2348E, DTM2349E, DTM2350E, DTM2351E, DTM2352E, DTM3237I, DTM6072I, DTM6073A, DTM6074I, DTM7110I, DTM8160I, DTM8233I. The following messages have been added or substantially changed: DTM0220I, DTM0563I, DTM0564I, DTM1253I, DTM4458I, DTM7127I, DTM8155I, DTM8156I, DTM8161I, DTM8162I, DTM8219I, DTM8226I, DTM8511I, DTM8512I, DTM8513I. The following messages have been added or substantially changed: DTM1464I, DTM6025I, DTM6070I, DTM6108I, DTM3236E, DTM7592I, DTM8508I, DTM8509I, DTM8510I. The following messages have been added or substantially changed: DTM1254I, DTM1260I, DTM1450I, DTM14661I, DTM3236E, DTM3504I, DTM7273I, DTM7592I, DTM8015W, DTM8179I, DTM8180E, DTM8219I, DTM8226I, DTM8406E, DTM8407E, DTM8409E, DTM8410E, DTM8411E, DTM8412E, DTM8413W, DTM8414W, DTM8505I, DTM8506I, DTM8507I, DTM8508I, HASP373. This is a base manual for ThruPut Manager Version 7 Release 1.0.

4 ThruPut Manager About this Manual This manual documents the messages issued by ThruPut Manager and the Job Action Language (JAL) Processor.

5 Messages Introduction This section explains the format used to describe ThruPut Manager messages. Manual Format To simplify locating messages every page header includes the first message identification number on that page. The footer includes the last message identification number on that page. Message Description Format ThruPut Manager messages use this format: DTMnnnns TEXT Where: DTM nnnn s identifies this as a ThruPut Manager message. is a four digit message number. is an action indicator as follows: A Immediate action required. E Eventual action required. I Information message. Messages are described in numeric sequence. The following information is provided for each message: An explanation of why the message occurred. The action that the system takes. The suggested operator and Programmer Responses. Messages are shown in upper case, while data which can vary in the message is shown in lower case: DTM0008I TMSS TASK task-name WILL NOT SIGNAL SUCCESSFUL START In some messages, certain text might not appear under some circumstances. This text is shown in brackets: Introduction 1

6 ThruPut Manager Internal Diagnostic Messages DTM0062I AUTHORITY INSUFFICIENT FOR command-name [keyword] COMMAND Several messages are intended to provide diagnostic information that is only meaningful to ThruPut Manager Customer Support. These messages are documented by including their message numbers, but the text of the message and any further explanation is not shown. If such a message is issued, do the following: Note the message number and text of the message. Assemble any relevant documentation, such as other messages, dumps, and copies of affected JCL or datasets. Call ThruPut Manager Customer Support. 2 Introduction

7 Messages Message IDs $HASP373 DTM0000I DTM0001I DTM0002I jobname STARTED - TM INIT - SLM ccenter type - SYS sys or jobname STARTED - TM INIT - SLM JOBCLASS class - SYS sys or jobname STARTED - TM INIT - ON_DEMAND JOB - SYS sys When SLM is installed, the $HASP373 message is altered to reflect the SLM service that is given to the job. THRUPUT MANAGER version release.modification-number TMTptfno (C) COPYRIGHT 1985, 2007 MVS SOLUTIONS INC. ALL RIGHTS RESERVED This message is issued when TMSS starts initialization, documenting that ThruPut Manager is a copyrighted, proprietary program of MVS Solutions Inc. and that all rights are reserved by MVS Solutions Inc. System Action: TMSS continues initialization processing. Programmer Response: Include this information when reporting any problem to ThruPut Manager Customer Support. INVALID PARAMETER SPECIFIED ON PARM= HAS BEEN IGNORED During initialization, TMSS found that the parameter field of its EXEC statement contains an invalid value for one of its subparameters. System Action: TMSS assumes a default value for the affected subparameter. Operator Response: If the default is not suitable, restart TMSS specifying the subparameter correctly. INVALID PARAMETER SPECIFIED ON PARM= NEAR invalid text HAS BEEN IGNORED During initialization, TMSS found a syntax error or an unknown subparameter in the parameter field of its EXEC statement. System Action: TMSS ignores the invalid parameter and continues to scan for more subparameters. Operator Response: Correct the invalid subparameter and restart TMSS. Message IDs 3

8 ThruPut Manager DTM0003I DTM0004I DTM0005A DTM0006I DTM0007A [TMSS PCS] TERMINATING DUE TO INITIALIZATION PARAMETER ERRORS TMSS or PCS is terminating as a result of incorrect parameters in its EXEC statement, as described in previously issued messages. System Action: TMSS or PCS terminates with a return code of 24. Operator Response: Correct the problem and restart TMSS or PCS. [TMSS PCS] TASK task-name HAS EXCEEDED TASK ERROR THRESHOLD A TMSS or PCS task has terminated abnormally enough times to exceed its automatic error retry threshold. Message DTM0016E indicates the abnormal termination completion code(s). System Action: If the task can be reinstated, message DTM0005A is issued, asking operator permission to reattach the failing task. Operator Response: See DTM0005A. REPLY Y TO REATTACH, N TO TERMINATE This message accompanies DTM0004I and requests operator intervention to reinstate a TMSS or PCS task. If the task in question is critical to continued TMSS or PCS operation and is not reinstated, TMSS or PCS shuts down immediately. System Action: TMSS or PCS waits for a reply. Operator Response: To re-attach the task, reply Y. If you do not want the task reinstated, reply N to terminate the task. THRUPUT MANAGER JOB ANALYZER(S) STILL ACTIVE The operator tried to stop TMSS, and TMSS discovered that there are still one or more active Job Analyzers in the system. TMSS cannot stop while the Job Analyzer is still actively processing jobs. System Action: Message DTM0007A is issued, asking for operator permission to continue the shutdown process. Operator Response: Halt or drain all initiators that are set to Job Analysis classes. REPLY Y TO CONTINUE TERMINATION, N TO WAIT This message accompanies DTM0006I and requests operator intervention to continue TMSS shutdown. System Action: TMSS waits for a reply. Operator Response: Reply Y to this message only if you are sure that the Job Analyzer is not active. 4 Message IDs

9 Messages A reply of N causes TMSS to continue waiting for the Job Analyzer to complete processing. If the Job Analyzer is still active after five minutes have elapsed, this message is issued again. DTM0008I DTM0009A DTM0010I DTM0010E [TMSS PCS] TASK task-name WILL NOT SIGNAL SUCCESSFUL START A TMSS or PCS task did not indicate a successful start after five minutes have elapsed. This message can appear if a TMSS or PCS task is delayed in its initialization phase (e.g., the task in question has itself asked for operator intervention). System Action: Message DTM0009A is issued, asking permission to restart the task. Operator Response: See message DTM0009A. REPLY Y TO RETRY, N TO WAIT This message accompanies DTM0008I and asks for operator intervention to reinstate a TMSS or PCS task that has failed to initialize successfully. System Action: TMSS or PCS waits for a reply. Operator Response: If you are certain that the task will never successfully start, reply Y to cause TMSS or PCS to detach and reattach the task. This can cause an SVC dump when the task is detached. If you reply N, TMSS or PCS waits five minutes for the task to start. If the task still has not indicated a successful start, TMSS or PCS issues DTM0008I again. SUBSYSTEM: subsys-name DOES NOT SUPPORT THRUPUT MANAGER. [TMSS PCS] UNABLE TO CONTINUE TMSS or PCS was started under a job entry subsystem that does not have the necessary ThruPut Manager support installed and activated. System Action: ThruPut Manager terminates immediately with a return code of 20. Operator Response: Inform personnel responsible for ThruPut Manager support. Programmer Response: Ensure that the ThruPut Manager JES2 exits have been properly installed. SUBSYSTEM: subsys-name DOES NOT SUPPORT THRUPUT MANAGER. [TMSS PCS] UNABLE TO CONTINUE TMSS or PCS was started under a job entry subsystem that does not have the necessary ThruPut Manager support installed and activated. System Action: ThruPut Manager terminates immediately with a return code of 20. Operator Response: Inform personnel responsible for ThruPut Manager support. Programmer Response: Ensure that the ThruPut Manager JES2 exits have been properly installed. Message IDs 5

10 ThruPut Manager DTM0011I [TMSS PCS] ALREADY ACTIVE FOR SUBSYSTEM: subsys-name DUPLICATE [TMSS PCS] NOT STARTED TMSS or PCS has already been started for this subsystem. System Action: TMSS or PCS terminates immediately with a return code of 16. Operator Response: Start TMSS or PCS under the correct subsystem. DTM0012I DTM0013I DTM0014I DTM0015I REQUEST TO FORMAT cf-area IGNORED. COMPONENT IS status cf-area: is an area of the control file associated with a ThruPut Manager application. status: indicates the status of the component, either NOT ENABLED or NOT INSTALLED. System Action: The format request is ignored. Operator Response: Ensure that the correct component was specified. [TMSS PCS] STARTUP DENIED BY INSTALLATION EXIT Your installation exit denied TMSS or PCS startup. System Action: TMSS or PCS terminates immediately with the return code set by your installation exit. Operator Response: Contact personnel responsible for ThruPut Manager support to determine why startup was denied. Programmer Response: Installation exit 10 has denied startup. See your installation s documentation for exit 10. [TMSS PCS] UNABLE TO CONTINUE WITHOUT SUPPORT SERVICES INTERFACE TMSS or PCS is shutting down because its Support Services Interface, a critical component, has terminated. System Action: TMSS or PCS initiates shutdown processing and terminates with a return code of 32. Operator Response: Inform personnel responsible for ThruPut Manager support. Programmer Response: See DTM0016E. [TMSS PCS] UNABLE TO CONTINUE WITHOUT OPERATOR SERVICES TMSS or PCS is shutting down because Operator Services, a critical component, has terminated. System Action: TMSS or PCS initiates shutdown processing and terminates with a return code of 32. Operator Response: Inform personnel responsible for ThruPut Manager support. Programmer Response: See message DTM0016E. 6 Message IDs

11 Messages DTM0016E DTM0017E DTM0018A DTM0019I DTM0020I [TMSS PCS] TASK: task-name HAS ABENDED, CODE=code code: is the system (Snnn) or user (Unnnn) completion code. A TMSS or PCS task terminated abnormally. When the task abends, an SVC dump indicating the exact nature of the problem is generated. System Action: If the task s automatic retry count has not been exceeded, the task is reinstated automatically. If the retry count has been exceeded, TMSS or PCS requests operator permission to reattach the task. Operator Response: If issued, see DTM0005A, otherwise notify personnel responsible for ThruPut Manager support. Programmer Response: Record the abend code. If calling ThruPut Manager Customer Support for help, have it ready along with the SVC dump and a system log covering the events leading up the error. [TMSS PCS] TASK: task-name HAS ABNORMALLY TERMINATED DURING STARTUP A TMSS or PCS task terminated abnormally during startup processing. Message DTM0016E indicates the nature of the abend. See DTM0004I for a list of task names. System Action: Message DTM0018A is issued asking permission to retry the task startup. Operator Response: See message DTM0018A. REPLY Y TO REATTACH, N TO TERMINATE This message accompanies messages DTM0017E or DTM0019I and requests permission to reinstate a TMSS or PCS task that has encountered an error during startup. System Action: TMSS or PCS waits for a reply. Operator Response: Reply Y to cause the task to be reinstated. Reply N to cause the task to be terminated. If the task is critical to continued TMSS or PCS operation and is not reinstated, TMSS or PCS shuts down immediately. [TMSS PCS] TASK: task-name TERMINATED DURING STARTUP A TMSS or PCS task terminated normally during startup processing. System Action: The task is marked unavailable, and TMSS or PCS continues initialization processing. Programmer Response: Determine why the task cannot start. [TMSS PCS] TASK: task-name TERMINATED NORMALLY A TMSS or PCS task terminated normally after it had been successfully started). System Action: TMSS or PCS does not attempt to reinstate the task. Message IDs 7

12 ThruPut Manager Operator Response: To reactivate the task, TMSS or PCS must be stopped and restarted. Notify personnel responsible for ThruPut Manager support. Programmer Response: Determine why the task cannot start. DTM0021I DTM0022I DTM0023I DTM0024I DTM0026I DTM0027I [TMSS PCS] MUST BE APF AUTHORIZED During initialization, TMSS or PCS determined that it was not APF authorized. System Action: TMSS or PCS terminates with the return code set to 36. Programmer Response: Install TMSS or PCS with APF authorization. type LOAD FAILED. TMSS TERMINATING type: is either DAL or JAL. TMSS could not load the Action Language specified on the initialization statement. System Action: TMSS terminates with the return code set to 28. Programmer Response: See previous messages indicating the reason for the failure. [TMSS PCS] INITIALIZATION COMPLETE TMSS or PCS has completed its initialization process and is now ready. *** WARNING *** table-name LOAD FAILED. TMSS INITIALIZATION CONTINUING The named table has failed to load. System Action: Processing continues. Programmer Response: See previous messages indicating the reason for the failure. TMSS UNABLE TO CONTINUE WITHOUT VIF SERVICES TMSS requires the VIF processor, but it is not available. System Action: TMSS terminates with the return code set to 32. Programmer Response: See previous messages indicating the reason for the failure. INCOMPATIBLE TM JES2 EXITS DETECTED -[vvrr SIZE PTF VER] vvrr: indicates the version (vv) and release (rr) of the TM JES2 exits. SIZE: indicates that the offset table is too small for the current PTF. 8 Message IDs

13 PTF: indicates that the offset table is for an older PTF. VER: the offset table version is lower than the minimum for the current PTF. Messages During TMSS or PCS initialization, it was determined that the TM JES2 exits for the JES2 subsystem under which TMSS or PCS was started are not compatible with this level of TMSS or the size of the offset table. System Action: TMSS or PCS terminates with the return code set to 36. Programmer Response: Ensure that JES2 is loading the correct level of the TM JES2 exits, then warm-start JES2. DTM0028I DTM0029I DTM0030I [TMSS PCS] INITIALIZATION TERMINATED. THRUPUT MANAGER OPERATING IN EMERGENCY BYPASS MODE (EBM) An attempt was made to start the TM STC while operating in Emergency Bypass Mode (EBM). System Action: The TM STC terminates. TMSS UNABLE TO CONTINUE WITHOUT CF SERVICES The Control File (CF) Manager sub-task has failed to initialize. System Action: The TM STC terminates. Programmer Response: Determine why the Control File Manager sub-task is failing. service FAILED. REASON CODE=reason, RETURN CODE=return service: is the failing service, and is one of: LOAD EP=SLSXCAL SLSXREQ QDRIVES reason: is the reason code. return: is the return code. The indicated service failed. This message is accompanied by DTM0031A. System Action: Issues DTM0031A and waits for a response. Operator Response: See message DTM0031A. Message IDs 9

14 ThruPut Manager DTM0031I DTM0031A DTM0033I DTM0035I DTM0036I HSC NOT AVAILABLE, START HSC AND REPLY Y OR REPLY N TO CONTINUE WITHOUT STORAGETEK SUPPORT This message is preceded by DTM0030I. The HSC service required for StorageTek support has either failed or was not started. System Action: If the reply is N, TMSS continues without StorageTek support. If the reply is Y, TMSS will attempt to obtain drive information from HSC again. Operator Response: Start HSC and reply Y. Note that this message will automatically be deleted when HSC has been started and is fully initialized. If the service still does not start correctly, notify personnel responsible for ThruPut Manager support. Programmer Response: Determine why the HSC service is failing and correct. UNABLE TO COMMUNICATE WITH CA 7 (CAnn) This message is issued during initialization of the PCS started task. It indicates that PCS is unable to communicate with the specified CA 7 Instance. This may be because: the CCI interface is not yet available, or the CA 7 Instance is not yet available. System Action: PCS waits for communication with the specific CA 7 Instance to be available. Operator Response: If specified CA 7 Instance has not been started, start it now. HOSTNAME name COULD NOT BE RESOLVED The HOSTNAME specified on the TM TCPIP initialization statement or command could not be resolved. ThruPut Manager uses IBM Communication Services GETHOSTBYNAME service to obtain the IP address associated with the specified HOSTNAME. System Action: ThruPut Manager will periodically attempt to resolve the specified HOSTNAME. Operator Response: Contact System Programmer. Programmer Response: Update TCPIP Host information. HOSTNAME name ADDED or IP ipaddress ADDED name: indicates the HOSTNAME ipaddress: indicates IP address This message is issued in response to the TM TCPIP ADD command. It indicates that the specified HOSTNAME or IP address has been added to the list of TCPIP connections available to ThruPut Manager. 10 Message IDs

15 Messages DTM0037I DTM0038I DTM0039I HOSTNAME name IS ALREADY IN LIST OF AVAILABLE CONNECTIONS or IP ipaddress IS ALREADY IN LIST OF AVAILABLE CONNECTIONS name: indicates the host name. ipaddress: indicates the IP address. This message is issued in response to the TM TCPIP ADD. It indicates that the specified HOSTNAME or IP address is already in the list of TCPIP connections available to ThruPut Manager. Programmer Action: None. [TM PCS] TCPIP DISPLAY PORT NUMBER IS port IP HOSTNAME nnn.nnn.nnn.nnn name port: indicates the port number used in forming TCPIP connections. nnn.nnn.nnn.nnn: indicates the IP address. If connection was specified by HOSTNAME and the hostname could not be resolved (DTM0035I), Not resolved is displayed. name: indicates the HOSTNAME. If the connection was specified by IP address, Not specified is displayed. This message is issued in response to the TM TCPIP DISPLAY or PCS TCPIP DISPLAY command. It indicates a port number used by ThruPut Manager in forming TCPIP connections. Subsequently, it lists the available TCPIP connections. Programmer Action: None. OPTION JTSOLD IS NO LONGER SUPPORTED JTSOLD option is not supposed to be installed. This option is not longer supported. System Action: If JTSOLD is installed, TMSS will terminate. Operator Response: Notify a System Programmer responsible for ThruPut Manager installation. Programmer Response: Contact ThruPut Manager support. Message IDs 11

16 ThruPut Manager DTM0042I DTM0043I DTM0044I DTM0045I DTM0046I TM TCPIP ADD IP specified without TM TCPIP SET PORT. Default PORT(n) assumed n : port number This message is issued in response to the TM TCPIP ADD IP command or initialization statement. It indicates the default port number used by ThruPut Manager in forming TCPIP connections. Programmer Response: If the default ThruPut Manager port should not be used, add a TM TCPIP SET PORT(n) initialization statement and restart the ThruPut Manager started task or PCS Control Region, whichever is appropriate. CA 7 EXPLORER FAILED. RETURN CODE n PCS CA 7 examination routine failed. Programmer Response: Report this message to ThruPut Manager support. APPLCTN,NAME=name WAS NOT SPECIFIED FOR CA7n The mentioned name was not specified in the CA 7n initialization deck. Programmer Response: Add APPLCTN,NAME=name to CA7n s initialization deck and ensure that the routine is available to CA 7n (linklist). Restart CA7n. LOAD FAILED FOR sassxxnn. R15=x. R1=y PCS was unable to LOAD the CA 7 Exit routine. Programmer Response: Ensure the ThruPut Manager version of the CA7 Exits is available. ENTRY POINT FOR SASSXXnn IS NOT DTMC7xx The specified CA 7 Exit routine is NOT the supplied ThruPut Manager version. Programmer Response: Ensure the ThruPut Manager version of the CA7 Exits is available. 12 Message IDs

17 Messages DTM0047I DTM0060I DTM0061I DTM0062I DTM0063I DTM0064I z/os x.xx not supported by ThruPut Manager AE. Requires y.yy or higher This message is issued during ThruPut Manager AE initialization. It indicates that the installed level of z/os is below that required to run ThruPut Manager AE. INVALID COMMAND NAME SYNTAX A command issued using the TMSS sub-system command character is enclosed in quotes or parentheses, or begins with a punctuation mark. System Action: The command is not processed. Operator Response: Re-enter correctly. UNKNOWN COMMAND: text The TMSS sub-system command character was not followed by the name of a valid TMSS command. System Action: The invalid text is ignored. Operator Response: Enter a valid command. AUTHORITY INSUFFICIENT FOR function-name command-name COMMAND The console at which the specified TMSS command was issued does not have sufficient authority. TMISPF uses extended console authority, and requires OPER/INFO authority for display commands and OPER/SYSTEM for update/alter type commands. System Action: The command is not processed. Operator Response: Issue the command from a console with proper authority. COMMAND KEYWORD IS INVALID: keyword The TMSS command just entered has an invalid keyword. System Action: The command is not processed. Operator Response: Re-enter correctly. COMMAND KEYWORD(S) OMITTED The entered TMSS command requires at least one keyword and none were entered. System Action: The command is not processed. Operator Response: Re-enter correctly. Message IDs 13

18 ThruPut Manager DTM0065I DTM0069I DTM0071I DTM0072I DTM0073I DTM0074I NULL COMMAND IGNORED The ThruPut Manager communications character was entered without any data. System Action: The character is ignored. THRUPUT MANAGER COMMAND REJECTED BY INSTALLATION EXIT A TMSS command was entered and there is an active ThruPut Manager installation exit 12. The exit rejected the command. System Action: The command is not processed. Operator Response: Contact personnel responsible for ThruPut Manager support to determine why the command was rejected. Programmer Response: Examine your installation s documentation for exit 12. INVALID COMMAND SYNTAX: UNBALANCED QUOTES A TMSS command contains an odd number of quotes. System Action: The command is not processed. Operator Response: Re-enter correctly. INVALID COMMAND SYNTAX: EQUAL SIGN NOT PRECEDED BY KEYWORD A TMSS command contained an equal sign (=) that was not preceded by a keyword and was not enclosed in quotes. System Action: The command is not processed. Operator Response: Re-enter correctly. INVALID COMMAND SYNTAX: TOO MANY LEVELS OF PARENTHESES A TMSS command contained too many levels of nested parentheses. System Action: The command is not processed. Operator Response: Re-enter correctly. INVALID COMMAND SYNTAX: UNBALANCED PARENTHESES A TMSS command did not contain an equal number of left and right parentheses, excluding any which were enclosed in quotes. System Action: The command is not processed. Operator Response: Re-enter correctly. 14 Message IDs

19 Messages DTM0075I DTM0081I DTM0083I DTM0084I DTM0085I DTM0087I INVALID COMMAND SYNTAX: A KEYWORD IS LONGER THAN 31 CHARACTERS A TMSS command contained either a character string enclosed in quotes that was more than 31 characters in length, or a string of more than 31 characters unbroken by blanks or delimiters (,, (, ), =, /*, &,, or : ). System Action: The command is not processed. Operator Response: Re-enter correctly. INVALID SYNTAX IN L= KEYWORD A TMSS command contained the location keyword (L=), and the value on the right of the equal sign was enclosed in quotes or started with a delimiter ( &,,, :, (, or = ). System Action: The command is not processed. Operator Response: Re-enter correctly. INVALID MESSAGE ROUTING KEYWORD A TMSS command contained the location keyword (L=) and the form of the value on the right of the equal sign was invalid. System Action: The command is not processed. Operator Response: Re-enter correctly. INVALID CONSOLE identifier A TMSS command contained the location keyword (L=), and the specified console id or name is currently invalid. System Action: The command is not processed. Operator Response: Re-enter correctly. CONSOLE identifier IS UNAVAILABLE A TMSS command contained the location keyword (L=). The requested console is not currently active as an MVS console. System Action: The command is not processed. Operator Response: Re-enter correctly. INVALID OR NON-EXISTENT AREA ID: area-id A TMSS command included the location keyword (L=). This area does not exist on the console that was to receive the command response. Message IDs 15

20 ThruPut Manager System Action: The command is not processed. Operator Response: Re-enter correctly. DTM0088I DTM0089I DTM0090I DTM0091I DTM0092I COMMAND nnnn = the-command-text-(72 bytes) This is an informational message as a result of a TM BATCH command or initialization statement. System Action: The command shown is passed to the command processor. function FUNCTION NOT INSTALLED or function command COMMAND NOT INSTALLED The function or command has not been installed. System Action: The command is ignored. Programmer Response: Ensure that the missing component is properly installed. UNKNOWN FUNCTION: text The characters immediately following the ThruPut Manager communications character did not specify a ThruPut Manager function. The text found is displayed. System Action: The command is not processed. Operator Response: Re-enter correctly. function-name FUNCTION COMMAND IS INVALID: command-name TMSS could not recognize the entered command as belonging to the specified ThruPut Manager function. System Action: The command is not processed. Operator Response: Re-enter correctly. function-name FUNCTION COMMAND NOT SPECIFIED A ThruPut Manager function was entered without an accompanying command. System Action: The command is not processed. Operator Response: Re-enter correctly. 16 Message IDs

21 Messages DTM0093I DTM0094I DTM0095I DTM0096I DTM0097I DTM0098I function-name command-name INVALID KEYWORD: keyword TMSS could not recognize the keyword as belonging to the ThruPut Manager function and command that were entered. System Action: The command is not processed. Operator Response: Re-enter correctly. function-name command-name REQUIRED KEYWORD NOT SPECIFIED A required keyword is missing for the entered ThruPut Manager function and command. System Action: The command is not processed. Operator Response: Re-enter correctly. function-name command-name MUTUALLY EXCLUSIVE KEYWORDS SPECIFIED Mutually exclusive keywords were specified for the ThruPut Manager command that was entered. System Action: The command is not processed. Operator Response: Re-enter correctly. function-name command-name VALUE NOT NUMERIC: invalid-value A value entered for the specified ThruPut Manager command was expected to be numeric, but was not. System Action: The command is not processed. Operator Response: Re-enter correctly. function-name command-name VALUE OUT OF RANGE: invalid-value A value entered for the specified ThruPut Manager command was beyond the range allowed. System Action: The command is not processed. Operator Response: Re-enter correctly. function-name command-name REQUIRES VALUE The specified ThruPut Manager command requires a value that was not entered. System Action: The command is not processed. Operator Response: Re-enter correctly. Message IDs 17

22 ThruPut Manager DTM0099I DTM0101I DTM0102I DTM0103I DTM0104I DTM0105I function-name command-name INVALID VALUE: invalid-value The value entered for the specified ThruPut Manager command is not valid. System Action: The command is not processed. Operator Response: Re-enter correctly. THE CPS PROCESSOR HAS BEEN SHUT DOWN The CPS processor terminated normally. THE CPS SPOOL FILE IS dsname ON volser This message shows the name and location of the CPS SPOOL File. System Action: Processing continues. CPS SPOOL DATASET NAME dsname NOT FOUND IN CATALOG The dataset is not cataloged, or the required catalog is not available. System Action: Message DTM0120A is issued. See DTM0120A. Programmer Response: Change the FILE SPOOL initialization statement or catalog the specified dataset. CPS SPOOL DATASET IS NOT ON A DIRECT ACCESS DEVICE The dataset specified for the CPS SPOOL File is not on a direct access device. System Action: Message DTM0120A is issued. See DTM0120A. Programmer Response: Change the FILE SPOOL initialization statement or reallocate the dataset on a direct access device. MULTI-VOLUME DATASET NOT SUPPORTED FOR CPS SPOOL The dataset specified for the CPS SPOOL File is cataloged on more than one volume. System Action: Message DTM0120A is issued. See DTM0120A. 18 Message IDs

23 Messages Programmer Response: Change the FILE SPOOL initialization statement or reallocate the dataset so that it is contained in a single direct access volume. DTM0106I DTM0107I DTM0108I DTM0109I CPS SPOOL DATASET HAS UNSUPPORTED DSORG The dataset specified for the CPS SPOOL File has a dataset organization other than PS, DA, or undefined. System Action: Message DTM0120A is issued. See DTM0120A. Programmer Response: Change the FILE SPOOL initialization statement or reallocate the dataset. UNABLE TO READ CPS SPOOL CONTROL RECORD An I/O error reading the CPS SPOOL Control Record prevented a CPS SPOOL File WARM start. System Action: If the operator allows it, a COLD start is attempted. Message DTM0113A is issued. See DTM0113A. Programmer Response: See accompanying message DTM0130I. NO CPS SPOOL CONTROL RECORD FOUND A CPS SPOOL File WARM start is not possible because the first record in the CPS SPOOL File is not a CPS SPOOL Control Record. System Action: If the operator allows it, a COLD start is attempted. Message DTM0113A is issued. See DTM0113A. Programmer Response: If this error occurs at any time other than during a COLD start, notify ThruPut Manager Customer Support. Have a hex dump of the CPS SPOOL File available. INVALID CPS SPOOL CONTROL RECORD, CODE = nn A CPS SPOOL File WARM start is not possible because the CPS SPOOL Control is damaged. This could result from a system failure which occurred when the CPS SPOOL Control Record was last written. System Action: If the operator allows it, a COLD start is attempted. Message DTM0113A is issued. Operator Response: If this condition is expected, (i.e., caused by a system failure), reply Y to the DTM0113A message. If the condition is unexpected, reply N to the DTM0113A message and notify personnel responsible for ThruPut Manager support. Message IDs 19

24 ThruPut Manager Programmer Response: If this condition cannot be attributed to a system failure, report this problem to ThruPut Manager Customer Support. Before formatting the damaged CPS SPOOL File, save a copy of the contents for analysis. DTM0110I DTM0111I DTM0113A DTM0114I CPS SPOOL FORMATTING IS INCOMPLETE A CPS SPOOL File WARM start is not possible because the previous attempt to COLD start it did not complete successfully. System Action: If the operator allows it, another COLD start is attempted. Message DTM0113A is issued. See DTM0113A. CPS SPOOL IS NOT COMPATIBLE WITH THIS RELEASE OF THRUPUT MANAGER A CPS SPOOL File WARM start is not possible because the CPS SPOOL File was last formatted by a later release of ThruPut Manager, or by an earlier release whose CPS SPOOL File format is not supported by this release. System Action: If the operator allows it, a COLD start is attempted. Message DTM0113A is issued. See DTM0113A. Programmer Response: A new release of ThruPut Manager can support a CPS SPOOL File formatted under the previous release, but not vice-versa. If you must COLD start a CPS SPOOL File that is being shared by systems running different releases of ThruPut Manager, do so on the system running the oldest release. IS A SPOOL COLD START AUTHORIZED? REPLY Y OR N A CPS SPOOL File COLD start was requested or found to be necessary. It does not proceed unless the operator authorizes it. System Action: The SPOOL processor waits for a reply. Operator Response: If the COLD start should proceed, reply Y to this message, otherwise reply N. THE CPS SPOOL IS BEING FORMATTED A CPS SPOOL File COLD start was authorized and is proceeding. A WARM start is no longer possible with this CPS SPOOL File until it has been formatted successfully. System Action: The CPS SPOOL File is formatted. 20 Message IDs

25 Messages DTM0115I DTM0116I DTM0117I DTM0118I DTM0119A I/O ERROR DURING CPS SPOOL FORMATTING jobname,stepname,devno, devtyp,ddname,op,err,bbcchhr,bsam An I/O error occurred while the CPS SPOOL File was being formatted. The format of this message conforms with the MVS standard error message. For a complete explanation refer to MVS System Messages, message number IEA000I. System Action: Message DTM0120A is issued. See DTM0120A. Programmer Response: Allocate a new dataset for the CPS SPOOL File. THE CPS SPOOL HAS BEEN FORMATTED The CPS SPOOL File was successfully formatted in response to a COLD start request. System Action: Begins to spool CPS output. CPS SPOOL COLD START AUTHORIZATION DENIED BY OPERATOR The operator replied N to message DTM0113A. System Action: The COLD start attempt is abandoned. If a WARM start can be done, TMSS offers that option. See DTM0119A. Operator Response: If issued, see DTM0119A. UNABLE TO WRITE CPS SPOOL CONTROL RECORD An I/O error prevented the CPS SPOOL Control Record from being written to complete a COLD start. System Action: The COLD start attempt is abandoned. Message DTM0120A is issued. See DTM0120A. Programmer Response: Allocate a new dataset for the CPS SPOOL File. DO YOU WISH TO DO A SPOOL WARM START INSTEAD? REPLY Y OR N A CPS SPOOL File COLD start attempt was disallowed by the operator, but a WARM start is still possible. System Action: The SPOOL processor waits for a reply. Operator Response: If the WARM start should proceed, reply Y to this message, otherwise reply N. Message IDs 21

26 ThruPut Manager DTM0120A DTM0121I DTM0122I DTM0123I DTM0124I DO YOU WISH TO CONTINUE WITHOUT A SPOOL? REPLY Y OR N The CPS SPOOL File cannot be used due to errors reported in previous messages. The SPOOL processor can operate without it, but cannot provide these features: JVL, CVL, and ALERT request queuing. Printing of JVLs, CVLs, and ALERTs on a system other than the one that produced them. Checkpointing of CPS Writer parameters. System Action: The SPOOL processor waits for a reply. Operator Response: If the SPOOL processor should proceed without a CPS SPOOL File, reply Y to this message, otherwise reply N. CPS SPOOL FORMAT CHANGED; SPOOL PROCESSOR TERMINATING The SPOOL processor has detected that another TMSS sharing the same SPOOL File has just cold-started it with different parameters (JOB and VOL parameters on the TM USER statement) from this TMSS. System Action: The SPOOL processor in this TMSS shuts down. Any requests being processed at this time will report failure due to SPOOL File damage. Programmer Response: Make the TMSS initialization parameters consistent for all systems. CPS SPOOL CONTROL RECORD DAMAGED; SPOOL PROCESSOR TERMINATING The SPOOL processor detected damage to the CPS SPOOL Control Record. This can result from an I/O error during a write (message DTM0130I is issued), or a system failure on another system sharing this CPS SPOOL File. System Action: The SPOOL processor in this TMSS shuts down. Any requests being processed are failed due to CPS SPOOL Control Record damage. Programmer Response: If this error occurs at any time other than during a COLD start, notify ThruPut Manager Customer Support. Have a hex dump of the CPS SPOOL File available. CPS SPOOL HAS BEEN COLD STARTED BY ANOTHER TMSS The SPOOL processor detected that the CPS SPOOL File was formatted (COLD started) by a TMSS which shares the file. System Action: The SPOOL processor continues operating, but any records that were in the CPS SPOOL File are lost. TOO MANY SYSTEMS USING THIS CPS SPOOL; SPOOL PROCESSOR TERMINATING During initialization, the SPOOL processor found that there are already 16 TMSSs using this CPS SPOOL File. 22 Message IDs

27 Messages System Action: The SPOOL processor shuts down. Programmer Response: Reduce the number of SPOOL processors. DTM0125I DTM0126I DTM0127I DTM0128I DTM0129I CPS WRITER writer-name ALREADY DEFINED IN ANOTHER TMSS During initialization, the SPOOL processor found that the requested CPS Writer name is already in use by a TMSS running on another system or under a different subsystem. System Action: The SPOOL processor continues, but the indicated CPS Writer is not defined under this TMSS. Programmer Response: Change the CPS WRITER initialization statements to ensure that each CPS Writer has a unique name. CPS WRITER writer-name NOT DEFINED BECAUSE THE DESTINATION LIST IS FULL During initialization, the SPOOL processor found that defining this CPS Writer would cause more than 128 destinations to be defined. System Action: The SPOOL processor continues, but the indicated CPS Writer is not defined. Programmer Response: Reduce the number of destinations. CPS WRITER writer-name NOT DEFINED BECAUSE THE CPS SPOOL CONTROL RECORD IS FULL During initialization, the SPOOL processor could not find sufficient space in the CPS SPOOL Control Record to define this CPS Writer. System Action: The SPOOL processor continues, but the indicated CPS Writer is not defined. Programmer Response: Reduce the number of CPS Writers. CPS WRITER writer-name NOT DEFINED BECAUSE THE CPS WRITER LIST IS FULL During initialization, the SPOOL processor found that there were already 64 CPS Writers defined in the CPS SPOOL Control Record. System Action: The SPOOL processor continues, but the indicated CPS Writer is not defined. Programmer Response: Reduce the number of CPS Writers. CPS WRITER writer-name NOT DEFINED DUE TO PREVIOUS ERROR During initialization, the SPOOL processor encountered an error defining a new CPS Writer under this TMSS. This error was reported in a previous message. Any new CPS Writers specified after the offending one are also left undefined. System Action: The SPOOL processor continues, but the indicated CPS Writer is not defined. Message IDs 23

28 ThruPut Manager Programmer Response: See previous message(s) documenting the problem. DTM0130I DTM0131I DTM0132I DTM0140I DTM0141I CPS SPOOL I/O ERROR jobname,stepname,devno,devtyp,ddname,op,err,bbcchhr,bsam An I/O error occurred during an access to the CPS SPOOL File. The format of this message conforms with the MVS standard error message. For a complete explanation refer to MVS System Messages, message number IEA000I. System Action: If the error occurred reading or writing the CPS SPOOL Control Record, the SPOOL processor shuts down; otherwise, the bad record in the CPS SPOOL File is marked unusable and the SPOOL processor continues. Programmer Response: Diagnose and correct the I/O error. UNABLE TO WRITE CPS SPOOL CONTROL RECORD: SPOOL PROCESSOR TERMINATING An I/O error prevented the CPS SPOOL Control Record from being written successfully. System Action: The SPOOL processor in this TMSS shuts down. Any requests being processed are failed due to CPS SPOOL Control Record damage. Programmer Response: Allocate a new dataset for the CPS SPOOL File. UNABLE TO READ RECORD FOR JOB jobname jobnumber FROM CPS SPOOL An I/O error prevented the records for a job from being read from the CPS SPOOL File. A job name-number of *UNKNOWN ***** indicates that not enough of the records could be read to identify the job. System Action: The request for this job is lost. Programmer Response: See accompanying message DTM0130I. CPS REQUEST IGNORED FOR jobname jobnumber DESTINATION destination-name ; DESTINATION LIST IS FULL The SPOOL processor is operating without a CPS SPOOL File. An output request was received from the Job Analyzer for a destination that was not previously referenced. The maximum number of destinations are already defined and all are assigned to CPS Writers. System Action: The request for this job is discarded. Programmer Response: Reduce the number of destinations. UNABLE TO OBTAIN SPACE IN CPS SPOOL FOR JOB jobname jobnumber An output request was received from a Job Analyzer while the CPS SPOOL File was full. When this message is issued, TMSS has already waited about 2 minutes, but sufficient space has not become available. 24 Message IDs

29 System Action: Message DTM0142A is issued. Messages See DTM0142A. Programmer Response: Allocate a larger CPS SPOOL File. DTM0142A DTM0143I DTM0144A DTM0145I REPLY I TO IGNORE, C TO CANCEL, OR R TO RETRY This message follows message DTM0141I. System Action: Waits for the operator to reply. If space becomes available while the reply is outstanding, these messages are cancelled and the records are written into the Spool File. Operator Response: Reply I to ignore the request. The job is scheduled for execution. Reply C to cancel the Job Analyzer. The job is requeued for Job Analysis and the initiator is drained. Reply R to cause the SPOOL processor to try again to obtain space in the CPS SPOOL File. If it is unsuccessful, these messages are issued again after about 2 minutes. JOB jobname jobnumber, DESTINATION destination-name IS UNKNOWN The SPOOL processor is operating without a CPS SPOOL File. A request was received from the Job Analyzer for a destination that was not previously referenced and is not assigned to a CPS Writer. System Action: Message DTM0144A is issued. See DTM0144A. Programmer Response: Assign the destination to a CPS Writer, or change the DAL or JAL so that this destination is not requested. REPLY I TO IGNORE, OR W= CPS WRITER NAME This message follows message DTM0143I. System Action: TMSS waits for the operator to reply. Operator Response: Reply I to ignore the request. All subsequent requests for this destination are also ignored. Reply W=name (where name is a CPS Writer name) to assign the new destination to this CPS Writer. If this CPS Writer is active, the output request is written, otherwise the request is ignored. INVALID CPS WRITER NAME: writer-name ; RESPECIFY In response to message DTM0144A, W=name was specified, but writer-name is not the name of a defined CPS Writer. System Action: Message DTM0144A is issued again. Operator Response: Reply correctly to message DTM0144A. Message IDs 25

30 ThruPut Manager DTM0146I DTM0147A DTM0148I DTM0149I UNABLE TO SPOOL REQUEST FOR JOB jobname jobnumber TO DESTINATION destination-name A request was received from the Job Analyzer for a destination that has no records queued and is not assigned to a CPS Writer. The maximum number of destinations has already been recorded in the CPS SPOOL File, and the new destination cannot be accommodated. System Action: Message DTM0147A is issued. See DTM0147A. Programmer Response: Reduce the number of destinations. REPLY I TO IGNORE, C TO CANCEL, OR D= FOR REPLACEMENT DESTINATION This message follows message DTM0146I. System Action: TMSS waits for the operator to reply. Operator Response: Reply I to ignore the request. The job is scheduled for execution. Reply C to cancel the Job Analyzer. The job is requeued for Job Analysis and the initiator is drained. Reply D=dest (where dest is an existing destination) to schedule this request for the specified destination. INVALID DESTINATION: destination-name ; RESPECIFY In response to message DTM0147A, D=dest was specified, but destinationname is not a valid destination. A valid destination consists of 1 to 8 alphabetic, numeric, or national characters. System Action: Message DTM0147A is issued again. Operator Response: Reply correctly to message DTM0147A. MVL FOR JOB jobname jobnumber NOT QUEUED TO CVL ACCUMULATOR accumulator-name, VIF NOT AVAILABLE Job Analysis resulted in a Volume List for the indicated job, but it could not be queued for the named CVL accumulator because the VIF is not available. System Action: The job is requeued, but the Volume List for it is not available. Programmer Response: Determine why the VIF is not available. 26 Message IDs

31 Messages DTM0151I DTM0152I DTM0153I JOB jobnumber jobname DEST(name) JVL SYSOUT ALLOCATION FAILURE or $ACCUMn CYCLE mmm DESTname) CVL SYSOUT ALLOCATION FAILURE or DCS ALERT JOBjobnumber jobname DEST(name) SYSOUT ALLOCATION FAILURE A TMSS task that writes SPS output was unable to allocate a SYSOUT file. This indicates a system problem of some sort, since destination names are tested for allocation suitability at TMSS startup, or whenever they are modified by operator commands. System Action: Message DTM0190I is issued, providing further error details. The output is not produced. Operator Response: Try to regenerate the output using a different destination name. Notify ThruPut Manager support personnel. Programmer Response: Look for and correct the system problem that has caused SYSOUT to begin to fail. JOB jobnumber jobname DEST(name) JVL SYSOUT OPEN FAILURE or $ACCUMn CYCLE mmm DEST(name) CVL SYSOUT OPEN FAILURE or DCS ALERT JOB jobnumber jobname DEST(name) SYSOUT OPEN FAILURE The TMSS task which writes SPS output was unable to open a SYSOUT file. This indicates a system problem of some sort, probably with JES2. System Action: The output is not produced. Operator Response: Try to regenerate the output using a different destination name. Notify ThruPut Manager support personnel. Programmer Response: Look for and correct the system problem that has caused SYSOUT to begin to fail. JVL JOB jobnumber jobname DEST(name) IS UNAVAILABLE, USING SYSOUT $DE- FAULT or CVL $ACCUMn DEST(name) IS UNAVAILABLE, USING SYSOUT $DEFAULT or FVL nnn DEST(name IS UNAVAILABLE, USING SYSOUT $DEFAULT or DCS ALERT JOB jobnumber jobname DEST(name) IS UNAVAILABLE, USING SYSOUT $DEFAULT The TM Job Analyzer has sent a request to the TMSS task which writes SPS output. The latter has determined that the destination name (requested in DAL, JAL, or through an operator command) is unavailable. System Action: The output is written to a sysout file with the default characteristics SYSOUT=A, HOLD=YES. Operator Response: If the destination is unavailable because it is not defined, it can be defined using SPS DEFINE. If it is defined but unavailable, notify ThruPut Manager support personnel. Message IDs 27

32 ThruPut Manager Programmer Response: Determine why an unavailable name was requested and correct. If necessary, add a definition to the TMSS initialization parameters. DTM0154I DTM0190I DTM0220I JOB jobnumber jobname type VOLUME INFORMATION LOST, VIF FULL *** Version 3 Mode Only *** type: is the type of information that is lost, and can be either CVL or PVF. The CPS Writer subsystem attempted to add job volume request information to the VIF for a CVL or for PVF. Some or all of the information could not be added because the VIF was full. System Action: The job s JAL requests for holding and classing are honored. For CVLs, some or all volumes for the job will not appear on the CVL. For PVF, some volumes will not be marked PULLED and some subsequent jobs might therefore not be auto-released. Operator Response: File some volumes to free up VIF space, then re-analyze the affected jobs in order to get complete VIF information. Programmer Response: If the condition persists, increase the size of the VIF. ALLOCATION FAILURE explanation TMSS tried to allocate a dataset dynamically. The allocation attempt failed for reasons indicated in the second and subsequent lines of this message. System Action: For DAL/JAL errors, TMSS terminates. Operator Response: If possible, correct the error; otherwise, notify personnel responsible for ThruPut Manager support. Programmer Response: Correct the indicated errors. JOB DISPLAY jobnumber jobname jobstatus Class : Priority: Sysaff : Managed: application Time System Reason job was not selected time system reason or TM INFORMATION NOT AVAILABLE A JOB DISPLAY command was entered. The first part of the response is always as above. The remainder of the display varies according to the characteristics of the job and the options requested in the command. DASD or D displays all resident DASD volumes required by the job. 28 Message IDs