Message IDs


Number

Description

$HASP373

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


Explanation: When SLM is installed, the $HASP373 message is altered to reflect the SLM service that is given to the job.

 System action: None

Operator response: None

Programmer response: None

DTM0000I

ThruPut Manager version release.modification-number

TMTptfno

(C) COPYRIGHT 1985, 2018 COMPUWARE CORPORATION ALL RIGHTS RESERVED


Explanation: This message is issued when TMSS starts initialization, documenting that ThruPut Manager is a copyrighted, proprietary program of Compuware Corporation and that all rights are reserved by Compuware Corporation.

 System action: TMSS continues initialization processing.

Operator response: None

Programmer response: Include this information when reporting any problem to BMC Support.

DTM0001I

INVALID PARAMETER SPECIFIED ON PARM= HAS BEEN IGNORED

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

Programmer response: None

DTM0002I

INVALID PARAMETER SPECIFIED ON PARM= NEAR ‘invalid’ text HAS BEEN IGNORED


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

Programmer response: None

DTM0003I

[TMSS | PCS] TERMINATING DUE TO INITIALIZATION PARAMETER ERRORS
Explanation:  MSS 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.

Programmer response: None

DTM0004I

[TMSS |PCS] TASK task-name HAS EXCEEDED TASK ERROR THRESHOLD
Explanation:  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.

Programmer response: None

DTM0005A

REPLY ‘Y’ TO REATTACH, ‘N’ TO TERMINATE
Explanation:  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.

Programmer response: None

DTM0006I

ThruPut Manager JOB ANALYZER(S) STILL ACTIVE
Explanation:  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.

Programmer response: None

DTM0007A

REPLY ‘Y’ TO CONTINUE TERMINATION, ‘N’ TO WAIT
Explanation:  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. 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.

Programmer response: None

DTM0008I

[TMSS | PCS] TASK task-name WILL NOT SIGNAL SUCCESSFUL START
Explanation:  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: None

Programmer response: None

DTM0009A

REPLY ‘Y’ TO RETRY, ‘N’ TO WAIT
Explanation:  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.

Programmer response: None

DTM0010I

SUBSYSTEM: subsys-name DOES NOT SUPPORT ThruPut Manager.
[TMSS | PCS] UNABLE TO CONTINUE
Explanation:  TMSS or PCS was started under a job entry subsystem that does not have the necessary support installed and activated.

System action : ThruPut Manager terminates immediately with a return code of 20.

Operator response: Inform personnel responsible for support.

Programmer response: Ensure that the ThruPut Manager JES2 exits have been properly installed.

DTM0010E

SUBSYSTEM: subsys-name DOES NOT SUPPORT ThruPut Manager.
[TMSS | PCS] UNABLE TO CONTINUE
Explanation:  TMSS or PCS was started under a job entry subsystem that does not have the necessary support installed and activated.

System action : ThruPut Manager terminates immediately with a return code of 20.

Operator response: Inform personnel responsible for support.

Programmer response: Ensure that the ThruPut Manager JES2 exits have been properly installed.

DTM0011I

[TMSS | PCS] ALREADY ACTIVE FOR SUBSYSTEM: subsys-name DUPLICATE [TMSS | PCS] NOT STARTED
Explanation:  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.

Programmer response: None

DTM0012I

REQUEST TO FORMAT cf-area IGNORED. COMPONENT IS status
Explanation:  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.

Programmer response: None

DTM0013I

[TMSS | PCS] STARTUP DENIED BY INSTALLATION EXIT
Explanation:  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 support to determine why startup was denied.

Programmer response: Installation exit 10 has denied startup. See your installation’s documentation for exit 10.

DTM0014I

[TMSS | PCS] UNABLE TO CONTINUE WITHOUT SUPPORT SERVICES INTERFACE
Explanation:  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 support.

Programmer response: See DTM0016E.

DTM0015I

[TMSS | PCS] UNABLE TO CONTINUE WITHOUT OPERATOR SERVICES

Explanation: 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 support.

Programmer response: See message DTM0016E.

DTM0016E

[TMSS | PCS] TASK: task-name HAS ABENDED, CODE=code

Explanation:

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, otherwise notify personnel responsible for support.

Programmer response: Record the abend code. If calling BMC Support for help, have it ready along with the SVC dump and a system log covering the events leading up the error.

DTM0017E

[TMSS | PCS] TASK: task-name HAS ABNORMALLY TERMINATED DURING STARTUP

Explanation: A TMSS or PCS task terminated abnormally during startup processing. Message DTM0016E indicates the nature of the abend. See DTM for a list of task names.

System action: Message DTM0018A is issued asking permission to retry the task startup.

Operator response: See message DTM0018A.

Programmer response: None.

DTM0018A

REPLY ‘Y’ TO REATTACH, ‘N’ TO TERMINATE


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

Programmer response: None.

DTM0019I

[TMSS | PCS] TASK: task-name TERMINATED DURING STARTUP

Explanation: A TMSS or PCS task terminated normally during startup processing.

System action: The task is marked unavailable, and TMSS or PCS continues initialization processing.

Operator response: Notify personnel responsible for support.

Programmer response: Determine why the task cannot start.

DTM0020I

[TMSS | PCS] TASK: task-name TERMINATED NORMALLY

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

Operator response: To reactivate the task, TMSS or PCS must be stopped and restarted. Notify personnel responsible for support.

Programmer response: Determine why the task cannot start.

DTM0021I

[TMSS | PCS] MUST BE APF AUTHORIZED

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

Operator response: Notify personnel responsible for support.

Programmer response: Install TMSS or PCS with APF authorization.

DTM0022I

type LOAD FAILED. TMSS TERMINATING

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

Operator response: Notify personnel responsible for support.

Programmer response: See previous messages indicating the reason for the failure.

DTM0023I

[TMSS | PCS] INITIALIZATION COMPLETE

Explanation: TMSS or PCS has completed its initialization process and is now ready.

System action: None.

Operator response: None.

Programmer response: None.

DTM0024I

*** WARNING *** table-name LOAD FAILED. TMSS INITIALIZATION CONTINUING

Explanation: The named table has failed to load.

System action: Processing continues.

Operator response: Notify personnel responsible for support.

Programmer response: See previous messages indicating the reason for the failure.

DTM0026I

TMSS UNABLE TO CONTINUE WITHOUT VIF SERVICES

Explanation: TMSS requires the VIF processor, but it is not available.

 System action  : TMSS terminates with the return code set to 32.

Operator response: Notify personnel responsible for support.

Programmer response: See previous messages indicating the reason for the failure.

DTM0027I

INCOMPATIBLE TM JES2 EXITS DETECTED -[vvrr | SIZE| PTF | VER]

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

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.

Operator response: Notify personnel responsible for support.

Programmer response: Ensure that JES2 is loading the correct level of the TM JES2 exits, then warm-start JES2.

DTM0028I

[TMSS | PCS] INITIALIZATION TERMINATED. ThruPut Manager OPERATING IN EMERGENCY BYPASS MODE (EBM)

Explanation: An attempt was made to start the TM STC while operating in Emergency Bypass Mode (EBM).

System action: The TM STC terminates.

Operator response: None.

Programmer response: None.

DTM0029I

TMSS UNABLE TO CONTINUE WITHOUT CF SERVICES

Explanation: The Control File (CF) Manager subtask has failed to initialize.

System action: The TM STC terminates.

Operator response: Notify personnel responsible for support.

Programmer response: Determine why the Control File Manager subtask is failing.

DTM0030I

service FAILED. REASON CODE=reason, RETURN CODE=return

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

Programmer response: None.

DTM0031I

HSC NOT AVAILABLE, START HSC AND REPLY ‘Y’

DTM0031A

OR REPLY ‘N’ TO CONTINUE WITHOUT STORAGETEK SUPPORT

Explanation: 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 support.

Programmer response: Determine why the HSC service is failing and correct.

DTM0033I

UNABLE TO COMMUNICATE WITH CA 7 (CAnn)

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

Programmer response: None.

DTM0035I

HOSTNAME name COULD NOT BE RESOLVED

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

DTM0036I

HOSTNAME name ADDED
or
IP ipaddress ADDED

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

System action: None.

Operator response: None.

Programmer response: None.

DTM0037I

HOSTNAME name IS ALREADY IN LIST OF AVAILABLE CONNECTIONS
or
IP ipaddress IS ALREADY IN LIST OF AVAILABLE CONNECTIONS

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

System action: None.

Operator response: None.

Programmer response: None.

DTM0038I

[PCS] TCPIP DISPLAY
Port number is port
Sysplex Jesplex Port IP HOSTNAME
sysplexname jesplexname port nnn.nnn.nnn.nnn name

or

TM TCPIP DISPLAY
Port number is port
Sysplex Jesplex Port IP HOSTNAME
sysplexname jesplexname port nnn.nnn.nnn.nnn

Explanation:
port: indicates the port number used in forming TCPIP connections.
Sysplex is the sysplex name.
Jesplex is the JES2 node name.
IP is the IP address of the target system on the name Sysplex,Jesplax.
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.

System action: None.

Operator response: None.

Programmer response: None.

DTM0039I

OPTION ‘JTSOLD’ IS NO LONGER SUPPORTED

Explanation: 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 support.

DTM0042I

TM TCPIP ADD IP specified without TM TCPIP SET PORT. Default PORT(n) assumed

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

System action: None.

Operator response: None.

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.

DTM0043I

CA 7 EXPLORER FAILED. RETURN CODE n

Explanation: PCS CA 7 examination routine failed.

System action: None.

Operator response: None.

Programmer response: Report this message to support.

DTM0044I

”APPLCTN,NAME=name” WAS NOT SPECIFIED FOR CA7n

Explanation: The mentioned name was not specified in the CA 7n initialization deck.

System action: None.

Operator response: None.

Programmer response: Add “APPLCTN,NAME=name” to CA7n’s initialization deck and ensure that the routine is available to CA 7n (linklist). Restart CA7n.

DTM0045I

LOAD FAILED FOR sassxxnn. R15=x. R1=y

Explanation: PCS was unable to LOAD the CA 7 Exit routine.

System action: None.

Operator response: None.

Programmer response: Ensure the ThruPut Manager version of the CA7 Exits is available.

DTM0046I

ENTRY POINT FOR SASSXXnn IS NOT DTMC7xx

Explanation: The specified CA 7 Exit routine is NOT the supplied ThruPut Manager version.

System action: None.

Operator response: None.

Programmer response: Ensure the ThruPut Manager version of the CA7 Exits is available.

DTM0047I

z/OS x.xx not supported by ThruPut Manager AE. Requires y.yy or higher

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

System action: None.

Operator response: None.

Programmer response: None.

DTM0048E

UNABLE TO VALIDATE COMPUWARE TM LICENSE. PROCESSING CONTINUES.

Explanation: An attempt was made to validate the existence of a TM license. The License Management System's response indicates that there is a environment error preventing LMS from operating properly, such as NO LMS subsystem being active.

System action: In the first implementation of the interface to the License Management System for TM, TM will continue to run and operate as usual. In subsequent versions TM will be not be allowed to continue running until the problem is corrected.

Operator response: They should start the LMS subsystem if that is the reported the problem. When it is running they can again start TM.

Programmer response: If the LMS system is not running, they should start the LMS subsystem.

DTM0050E

UNABLE TO VALIDATE COMPUWARE TM LICENSE.

Explanation: An attempt was made to find a valid TM license. The License Management system's response indicates that there is no valid license in the LMS file for the current version of TM.

 System action: TM will be allowed to run for 24 hours after the error is first detected. License checking will be retried every half hour during this time.

Operator response: If it is simply that ECC is not up, start it. Otherwise, report the problem.

Programmer response: The problem with licensing must be resolved as soon as possible. Associated messages will point to the reason for failure.

DTM0051I

SNAME=ssssssssss CODE=cc

Explanation: ThruPut Manager is about to check for a valid license for the product represented by the product name and product code specified.
ssssssssss: is the 10-character product name of the licensed software.
cc: is the two-character product code.

System action: ThruPut Manager will check for a valid license.

Operator response: No action required.

Programmer response: No action required.

DTM0052I

LICENSE VERIFICATION DELAYED 5 MINUTES, LMS NOT YET ACTIVE

Explanation: When TM was brought up, the License Management System (LMS) was not available. This message only occurs outside the 24-hour grace period, typically at IPL time. The assumption is made that the ThruPut Manager task was started before the Compuware Enterprise Common Components were fully up. TM needs to have access to LMS. The further assumption is that within 5 minutes the ECC will be up and license verification can be done.

System action: The system will function normally and ThruPut Manager will run normally. Within 6 minutes another attempt at license verification is made. If successful, the normal TM processing continues. See DTM0054E for action when NOT successful.

User response: No action necessary

Programmer response: No action necessary.

DTM0053I

ip_or_hostname has been removed from list of connections
ip_or_hostname is not in list of connections

Explanation: Issued in response to the TM TCPIP DELETE command. The first form of the message indicates that the IP or HOSTNAME was removed from the list. The second form of the message indicates that the IP or HOSTNAME was not defined.

System action: If successful, any connection to the IP or HOSTNAME is closed. If not defined, the command is terminated.

Operator response: If the command failed, ensure that the IP or HOSTNAME was specified correctly.

Programmer response: None.

DTM0054E

PLEASE RESOLVE ISSUE ASAP.
TM WILL CONTINUE RUNNING
TM LICENSE CHECK WILL RETRY IN 30 MINS.
IF ISSUE NOT RESOLVED, TM WILL BE SHUT DOWN IN hh HRS, mm MINS

Explanation: ThruPut Manager was unable to verify a valid Compuware license. TM has created a 24-hour window to allow resolution of the problem before being forcibly shut down. A new license check will be attempted in 30 minutes.

LMCHKOUT may issue messages. For example:

LMS001E COMPUWARE LICENSE MANAGEMENT NOT AVAILABLE ON TEST1
LMS003E NO LICENSE MANAGEMENT SUBSYSTEM IS ACTIVE

System action: TM will continue to run while re-attempting a license validation every 30 minutes. If 24 hours elapse BEFORE a successful license checkout, then ThruPut Manager will be brought down.

Operator response: Support needs to be informed of the issue so that it can be fixed as soon as possible. ThruPut Manager will operate normally so no action needs to be taken by operations immediately.

Programmer response: The specific reason for the failure needs to be determined from the associated error messages and the problem needs to be fixed.

DTM0055I 

LICENSE VALIDATION SUCCESSFUL. TM PROCESSING CONTINUES

Explanation: A valid ThruPut Manager license was found. Processing will continue.

System action: TM will run as it normally does.

Operator response: None.

Programmer response: None.

DTM0056I

TM LICENSE CHECKOUT RETURNED RC=xx REASON=xxx

Explanation: Unless LMCHKOUT has a return code of zero, this message is always produced. Subsequent messages will indicate if there is an issue. This message is just to document result of LMCHKOUT.

System action: The system is only affected depending on the follow-up to this informative message. If action is required, subsequent messages will make it obvious.

User response: No response until further messages.

Programmer response: Look up the return and reason code in license documentation. Further messages should clarify as well.

DTM0057E

LMCHKOUT (LMS) NOT RESPONDING. TM WILL BE ENABLED.

Explanation: Compuware LMS system was called to verify the license identified by parameters to LMCHKOUT. After a period of time, LMCHKOUT has not responded, indicating a problem.

System action: ThruPut Manager will be allowed to continue initializing and running normally. If LMCHKOUT finally returns, then processing continues normally, and the license will be checked out. If LMCHKOUT does not return, a 24-hour wait will take place. After that period ThruPut Manager will no longer be allowed to run until the problem has been fixed.

User response: Report the problem. Recycling TM may or may not fix the problem. It could be done once to see.

Programmer response: The problem must be analyzed and fixed. It should never happen. There is a wait somewhere along the logic path.

DTM0058E

ThruPut Manager  LICENSE NOT FOUND

Explanation: No license was found for the requested product.

System action: 24 hours are given to get and install the correct license file. The ThruPut Manager started task will run during this time. After 24 hours, TM will be shut down.

User response: Report the problem to Compuware and ensure the license can be obtained.

Programmer response: No action required.

DTM0059E

License Management Verification Failed - LMS Not Active

Explanation: The return codes from LMCHKOUT indicate that LMS is not currently active and the license verification process cannot be done.

System action: ThruPut Manager will be allowed to run while LMS is not active. After 24 hours, it will be brought down.

User response: The LMS subsystem of ECC must be deployed as soon as possible.

Programmer response: The LMS subsystem of ECC must be deployed as soon as possible. Ensure there is no problem bringing it up.

DTM0060I

INVALID COMMAND NAME SYNTAX

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

Programmer response: None.

DTM0061I

UNKNOWN COMMAND: text

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

Programmer response: None.

DTM0062I

AUTHORITY INSUFFICIENT FOR function-name command-name COMMAND

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

Programmer response: None.

DTM0063I

COMMAND KEYWORD IS INVALID: keyword

Explanation: The TMSS command just entered has an invalid keyword.

System action: The command is not processed.

Operator response: Re-enter correctly.

Programmer response: None.

DTM0064I

COMMAND KEYWORD(S) OMITTED

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

Programmer response: None.

DTM0065I

NULL COMMAND IGNORED

Explanation: The ThruPut Manager communications character was entered without any data.

System action: The character is ignored.

Operator response: None.

Programmer response: None.

DTM0067I

LICENSE ISSUES RESOLVED PROCESSING CONTINUES

Explanation: During the 24-hour window started due to a license failure, the problem was resolved. This message is issued on the next license check after the resolution.

System action: The license interface program will process normally and the 24-hour recovery window is closed.

User response: None.

Programmer response: None.

DTM0068E

License Management Severe error RC=nn REASON=mm

Explanation: The License Management system returned a return code greater than 8. The reason code is mm. The codes can be found in Enterprise Common Components Messages and Codes space.

System action: The 24-hour recovery window is opened. The problem must be resolved in that time or ThruPut Manager will be halted.

User response: Attempt to fix the issue through Compuware.

Programmer response: Relay the issue to BMC Support.

DTM0069I

Thruput Manager COMMAND REJECTED BY INSTALLATION EXIT

Explanation: 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 support to determine why the command was rejected.

Programmer response: Examine your installation’s documentation for exit 12.

DTM0070I

INVALID COMMAND SYNTAX: UNBALANCED QUOTES

Explanation: A TMSS command contains an odd number of quotes.

System action: The command is not processed.

Operator response: Re-enter correctly.

Programmer response: None.

DTM0071I

INVALID COMMAND SYNTAX: UNBALANCED QUOTES

Explanation: A TMSS command contains an odd number of quotes.

System action: The command is not processed.

Operator response: Re-enter correctly.

Programmer response: None.

DTM0072I

INVALID COMMAND SYNTAX: EQUAL SIGN NOT PRECEDED BY KEYWORD

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

Programmer response: None.

DTM0073I

INVALID COMMAND SYNTAX: TOO MANY LEVELS OF PARENTHESES

Explanation: A TMSS command contained too many levels of nested parentheses.

System action: The command is not processed.

Operator response: Re-enter correctly.

Programmer response: None.

DTM0074I

INVALID COMMAND SYNTAX: UNBALANCED PARENTHESES

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

Programmer response: None.

DTM0075I

INVALID COMMAND SYNTAX: A KEYWORD IS LONGER THAN 31 CHARACTERS

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

Programmer response: None.

DTM0081I

INVALID SYNTAX IN L= KEYWORD

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

Programmer response: None.

DTM0083I

INVALID MESSAGE ROUTING KEYWORD

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

Programmer response: None.

DTM0084I

INVALID CONSOLE identifier

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

Programmer response: None.

DTM0085I

CONSOLE identifier IS UNAVAILABLE

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

Programmer response: None.

DTM0087I

INVALID OR NON-EXISTENT AREA ID: area-id

Explanation: A TMSS command included the location keyword (L=). This area does not exist on the console that was to receive the command response.

System action: The command is not processed.

Operator response: Re-enter correctly.

Programmer response: None.

DTM0088I

COMMAND nnnn = ‘the-command-text-(72 bytes)’

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

Operator response: None.

Programmer response: None.

DTM0089I

‘function’ FUNCTION NOT INSTALLED
or
‘function command’ COMMAND NOT INSTALLED

Explanation: The function or command has not been installed.

System action: The command is ignored.

Operator response: Notify personnel responsible for support.

Programmer response: Ensure that the missing component is properly installed.

DTM0090I

UNKNOWN FUNCTION: text

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

Programmer response: None.

DTM0091I

‘function-name’ FUNCTION COMMAND IS INVALID: ‘command-name’

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

Programmer response: None.

DTM0092I

‘function-name’ FUNCTION COMMAND NOT SPECIFIED

Explanation: A ThruPut Manager function was entered without an accompanying command.

System action: The command is not processed.

Operator response: Re-enter correctly.

Programmer response: None.

DTM0093I

‘function-name’ ‘command-name’ INVALID KEYWORD: ‘keyword’

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

Programmer response: None.

DTM0094I

‘function-name’ ‘command-name’ REQUIRED KEYWORD NOT SPECIFIED

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

Programmer response: None.

DTM0095I

‘function-name’ ‘command-name’ MUTUALLY EXCLUSIVE KEYWORDS SPECIFIED

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

Programmer response: None.

DTM0096I

‘function-name’ ‘command-name’ VALUE NOT NUMERIC: invalid-value

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

Programmer response: None.

DTM0097I

‘function-name’ ‘command-name’ VALUE OUT OF RANGE: invalid-value

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

Programmer response: None.

DTM0098I

‘function-name’ ‘command-name’ REQUIRES VALUE

Explanation: The specified ThruPut Manager command requires a value that was not entered.

System action: The command is not processed.

Operator response: Re-enter correctly.

P rogrammer response: None.

DTM0099I

‘function-name’ ‘command-name’ INVALID VALUE: invalid-value


Explanation: The value entered for the specified ThruPut Manager command is not valid.

System action: The command is not processed.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0101I

THE CPS PROCESSOR HAS BEEN SHUT DOWN

Explanation: The CPS processor terminated normally

System action: None.

Operator response: None.

Programmer response: None.

DTM0102I

THE CPS SPOOL FILE IS dsname ON volser

Explanation: This message shows the name and location of the CPS SPOOL File.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM0103I

CPS SPOOL DATASET NAME ‘dsname’ NOT FOUND IN CATALOG


Explanation: The data set is not cataloged, or the required catalog is not available.

System action: Message DTM0120A is issued.

Operator Response: Notify personnel responsible for support. See DTM0120A.

Programmer Response: Change the FILE SPOOL initialization statement or catalog the specified data set.

DTM0104I

CPS SPOOL DATASET IS NOT ON A DIRECT ACCESS DEVICE


Explanation: The data set specified for the CPS SPOOL File is not on a direct access device.

System action: Message DTM0120A is issued.

Operator Response: Notify personnel responsible for support. See DTM0120A.

Programmer Response: Change the FILE SPOOL initialization statement or reallocate the data set on a direct access device.

DTM0105I

MULTI-VOLUME DATASET NOT SUPPORTED FOR CPS SPOOL


Explanation: The data set specified for the CPS SPOOL File is cataloged on more than one volume.

System action: Message DTM0120A is issued.

Operator Response: Notify personnel responsible for support. See DTM0120A.

Programmer Response: Change the FILE SPOOL initialization statement or reallocate the data set so that it is contained in a single direct access volume.

DTM0106I

CPS SPOOL DATASET HAS UNSUPPORTED DSORG


Explanation: The data set specified for the CPS SPOOL File has a data set organization other than PS, DA, or undefined.

System action: Message DTM0120A is issued.

Operator Response: Notify personnel responsible for support. See DTM0120A.

Programmer Response: Change the FILE SPOOL initialization statement or reallocate the data set.

DTM0107I

UNABLE TO READ CPS SPOOL CONTROL RECORD


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

Operator Response: Notify personnel responsible for support. See DTM0113A.

Programmer Response: See accompanying message DTM0130I.

DTM0108I

NO CPS SPOOL CONTROL RECORD FOUND


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

Operator Response: Notify personnel responsible for support. See DTM0113A.

Programmer Response: If this error occurs at any time other than during a COLD start, notify BMC Support. Have a hex dump of the CPS SPOOL File available.

DTM0109I

INVALID CPS SPOOL CONTROL RECORD, CODE = nn


Explanation: 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 support.

Programmer Response: If this condition cannot be attributed to a system failure, report this problem to BMC Support. Before formatting the damaged CPS SPOOL File, save a copy of the contents for analysis.

DTM0110I

CPS SPOOL FORMATTING IS INCOMPLETE


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

Operator Response: Notify personnel responsible for support. See DTM0113A.

Programmer Response: None.

DTM0111I

CPS SPOOL IS NOT COMPATIBLE WITH THIS RELEASE OF Thruput Manager


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

Operator Response: Notify personnel responsible for support. 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.

DTM0113A

IS A SPOOL COLD START AUTHORIZED? REPLY ‘Y’ OR ‘N’


Explanation: 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’.

Programmer Response: None.

DTM0114I

THE CPS SPOOL IS BEING FORMATTED


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

Operator Response: None.

Programmer Response: None.

DTM0115I

I/O ERROR DURING CPS SPOOL FORMATTING jobname,stepname,devno, devtyp,ddname,op,err,bbcchhr,BSAM


Explanation: 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 see to MVS System Messages, message number IEA000I.

System action: Message DTM0120A is issued.

Operator Response: Notify personnel responsible for support. See DTM0120A.

Programmer Response: Allocate a new data set for the CPS SPOOL File.

DTM0116I

THE CPS SPOOL HAS BEEN FORMATTED


Explanation: The CPS SPOOL File was successfully formatted in response to a COLD start request.

System action: Begins to spool CPS output.

Operator Response: None.

Programmer Response: None.

DTM0117I

CPS SPOOL COLD START AUTHORIZATION DENIED BY OPERATOR


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

Programmer Response: None.

DTM0118I

UNABLE TO WRITE CPS SPOOL CONTROL RECORD


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

Operator Response: Notify personnel responsible for support. See DTM0120A.

Programmer Response: Allocate a new data set for the CPS SPOOL File.

DTM0119A

DO YOU WISH TO DO A SPOOL WARM START INSTEAD? REPLY ‘Y’ OR ‘N’


Explanation: 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’.

Programmer Response: None.

DTM0120A

DO YOU WISH TO CONTINUE WITHOUT A SPOOL? REPLY ‘Y’ OR ‘N’


Explanation: 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’.

Programmer Response: None.

DTM0121I

CPS SPOOL FORMAT CHANGED; SPOOL PROCESSOR TERMINATING


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

Operator Response: Notify personnel responsible for support.

Programmer Response: Make the TMSS initialization parameters consistent for all systems.

DTM0122I

CPS SPOOL CONTROL RECORD DAMAGED; SPOOL PROCESSOR TERMINATING


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

Operator Response: Notify personnel responsible for support.

Programmer Response: If this error occurs at any time other than during a COLD start, notify BMC Support. Have a hex dump of the CPS SPOOL File available.

DTM0123I

CPS SPOOL HAS BEEN COLD STARTED BY ANOTHER TMSS


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

Operator Response: None.

Programmer Response: None.

DTM0124I

TOO MANY SYSTEMS USING THIS CPS SPOOL; SPOOL PROCESSOR TERMINATING


Explanation: During initialization, the SPOOL processor found that there are already 16 TMSSs using this CPS SPOOL File.

System action: The SPOOL processor shuts down.

Operator Response: Notify personnel responsible for support.

Programmer Response: Reduce the number of SPOOL processors.

DTM0125I

CPS WRITER ‘writer-name’ ALREADY DEFINED IN ANOTHER TMSS


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

Operator Response: Notify personnel responsible for support.

Programmer Response: Change the CPS WRITER initialization statements to ensure that each CPS Writer has a unique name

DTM0126I

CPS WRITER ‘writer-name’ NOT DEFINED BECAUSE THE DESTINATION LIST IS FULL


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

Operator Response: Notify personnel responsible for support.

Programmer Response: Reduce the number of destinations.

DTM0127I

CPS WRITER ‘writer-name’ NOT DEFINED BECAUSE THE CPS SPOOL CONTROL RECORD IS FULL


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

Operator Response: Notify personnel responsible for support.

Programmer Response: Reduce the number of CPS Writers.

DTM0128I

CPS WRITER ‘writer-name’ NOT DEFINED BECAUSE THE CPS WRITER LIST IS FULL


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

Operator Response: Notify personnel responsible for support.

Programmer Response: Reduce the number of CPS Writers.

DTM0129I

CPS WRITER ‘writer-name’ NOT DEFINED DUE TO PREVIOUS ERROR


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

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous message(s) documenting the problem.

DTM0130I

CPS SPOOL I/O ERROR jobname,stepname,devno,devtyp,ddname,op,err,bbcchhr,BSAM


Explanation: 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 see 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.

Operator Response: Notify personnel responsible for support.

Programmer Response: Diagnose and correct the I/O error.

DTM0131I

UNABLE TO WRITE CPS SPOOL CONTROL RECORD: SPOOL PROCESSOR TERMINATING


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

Operator Response: Notify personnel responsible for support.

Programmer Response: Allocate a new data set for the CPS SPOOL File.

DTM0132I

UNABLE TO READ RECORD FOR JOB jobname jobnumber FROM CPS SPOOL


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

Operator Response: Notify personnel responsible for support.

Programmer Response: See accompanying message DTM0130I.

DTM0140I

CPS REQUEST IGNORED FOR jobname jobnumber DESTINATION ‘destination-name’;
DESTINATION LIST IS FULL


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

Operator Response: Notify personnel responsible for support.

Programmer Response: Reduce the number of destinations.

DTM0141I

UNABLE TO OBTAIN SPACE IN CPS SPOOL FOR JOB jobname jobnumber


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

System action: Message DTM0142A is issued.

Operator Response: Notify personnel responsible for support. See DTM0142A.

Programmer Response: Allocate a larger CPS SPOOL File.

DTM0142A

REPLY ‘I’ TO IGNORE, ‘C’ TO CANCEL, OR ‘R’ TO RETRY


Explanation: 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

Programmer Response: None.

DTM0143I

JOB jobname jobnumber, DESTINATION ‘destination-name’ IS UNKNOWN


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

Operator Response: Notify personnel responsible for support. See DTM0144A.

Programmer Response: Assign the destination to a CPS Writer, or change the DAL or JAL so that this destination is not requested.

DTM0144A

REPLY ‘I’ TO IGNORE, OR ‘W=’ CPS WRITER NAME


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

Programmer Response: None.

DTM0145I

NVALID CPS WRITER NAME: ‘writer-name’; RESPECIFY


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

Programmer Response: None.

DTM0146I

UNABLE TO SPOOL REQUEST FOR JOB jobname jobnumber TO DESTINATION ‘destination-name’


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

Operator Response: Notify personnel responsible for support. See DTM0147A.

Programmer Response: Reduce the number of destinations.

DTM0147A

REPLY ‘I’ TO IGNORE, ‘C’ TO CANCEL, OR ‘D=’ FOR REPLACEMENT DESTINATION


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

Programmer Response: None.

DTM0148I

INVALID DESTINATION: ‘destination-name’; RESPECIFY


Explanation: In response to message DTM0147A, D=dest was specified, but destination-name 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.

Programmer Response: None.

DTM0149I

MVL FOR JOB jobname jobnumber NOT QUEUED TO CVL
ACCUMULATOR accumulator-name, VIF NOT AVAILABLE


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

Operator Response: Notify personnel responsible for support.

Programmer Response: Determine why the VIF is not available.

DTM0151I

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


Explanation: 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 support personnel.

Programmer Response: Look for and correct the system problem that has caused SYSOUT to begin to fail.

DTM0152I

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


Explanation: 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 support personnel.

Programmer Response: Look for and correct the system problem that has caused SYSOUT to begin to fail.

DTM0153I

JVL JOB jobnumber jobname DEST(name) IS UNAVAILABLE, USING SYSOUT $DEFAULT
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


Explanation: 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 support personnel.

Programmer Response: Determine why an unavailable name was requested and correct. If necessary, add a definition to the TMSS initialization parameters.

DTM0154I

JOB jobnumber jobname type VOLUME INFORMATION LOST, VIF FULL

*** Version 3 Mode Only ***


Explanation:

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.

DTM0190I

ALLOCATION FAILURE


Explanation: TMSS tried to allocate a data set 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 support.

Programmer Response: Correct the indicated errors.

DTM0220I

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


Explanation: 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.
  • ONREQUEST or ONREQ displays installation information that was formatted by JAL to be displayed only when requested.
  • TAPES or T displays all mountable volumes required by the job.

‘TM INFORMATION NOT AVAILABLE’ occurs when information is requested for a job that has not been processed by ThruPut Manager Job Analyzer. It applies to jobs that are submitted in classes that are exempted from ThruPut Manager processing. It can also occur for jobs that were in the system before ThruPut Manager was activated. If it occurs under other circumstances, you should notify personnel responsible for support.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0221I

NO ON_DEMAND CLASS DEFINED


Explanation: A /JOB DEMAND command was issued but an ON_DEMAND class has not been defined. The command cannot be processed unless an ON_DEMAND class has been defined.

System action: None.

Operator Response: Use the /TM CLASS command to define an ON_DEMAND class and then re-enter the /JOB DEMAND command.

Programmer Response: None.

DTM0222I

JOB jobid INELIGIBLE, reason


Explanation: A /JOB DEMAND command was issued but the specified job was not eligible to be modified for the reason in the message.
reason: Here is the list of possible reasons with the
Explanation:


    • not BATCH job – job specified is an STC or a TSU.
    • wrong queue – job specified is not on the execution queue.
    • already running – job specified is in execution.
    • SLM job, use SLM START – SLM jobs cannot be modified, however, the SLM START command may be used to expedite a job.

System action: None.

Operator Response: Re-enter the command with the correct job name or number. In the SLM job case, enter the SLM START command.

Programmer Response: None.

DTM0251I

NO JOB NAME/NUMBER SPECIFIED


Explanation: A command was entered without a job number.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0252I

JOB NUMBER IS INVALID: jobnumber


Explanation: A command was entered with an invalid job number.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0253I

UNIDENTIFIED KEYWORD: keyword


Explanation: A command was entered, but the data shown as keyword is not recognized for the command.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0254I

DESTINATION IS INVALID: destination-name


Explanation: A command was entered, but the destination supplied by the DEST keyword is invalid.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0255I

THE SPOOL PROCESSOR IS UNAVAILABLE


Explanation: A command was entered but cannot be processed because the SPOOL processor has terminated.

System action: Processing of the command is terminated.

Operator Response: None.

Programmer Response: None.

DTM0256I

CPS SPOOL CONTROL RECORD DAMAGE DETECTED


Explanation: A command was entered but cannot be processed because the SPOOL processor detected a damaged CPS SPOOL Control Record.

System action: Processing of the command is terminated.

Operator Response: Notify personnel responsible for support.

Programmer Response: See accompanying message DTM0130I.

DTM0257I

DESTINATION LIST IS FULL


Explanation: A command was entered but cannot be processed because the maximum number of destinations have been defined already.

System action: Processing of the command is terminated.

Operator Response: Re-enter the command with the DEST keyword specifying a destination that is already defined. Use the command CPS DISPLAY DEST to display the defined destinations.

Programmer Response: Reduce the number of CPS destinations.

DTM0258I

NO SPACE IN CPS SPOOL CONTROL RECORD


Explanation: A command was entered but cannot be processed because there is no space in the CPS SPOOL Control Record for its destination.

System action: Processing of the command is terminated.

Operator Response: Re-enter the command with the DEST keyword specifying a destination that is already defined. Use the command CPS DISPLAY to display the defined destinations.

Programmer Response: Increase size of the CPS SPOOL File.

DTM0259I

NO SPACE IN CPS SPOOL FILE


Explanation: A command was entered but cannot be processed because there is no room in the CPS SPOOL File.

System action: Processing of the command is terminated.

Operator Response: Notify personnel responsible for support.

Programmer Response: Increase size of the CPS SPOOL File.

DTM0262I

THE SPOOL PROCESSOR IS NOT AVAILABLE


Explanation: A command was entered, but cannot be completed because the SPOOL processor has terminated.

System action: Processing of the command is terminated.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the error.

DTM0263I

NO CPS WRITER IS PROCESSING DEST(destination-name)


Explanation: A command was entered but cannot be processed because there is no CPS Writer processing destination destination-name and the SPOOL processor is operating without a CPS SPOOL File.

System action: Processing of the command is terminated.

Operator Response: None.

Programmer Response: None.

DTM0264I

JVL WAS NEVER GENERATED FOR JOB jobnumber


Explanation: A JVL REGENERATE command was entered, but no JVL was created for this job.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0265I

INVALID JOBNAME: ‘jobname’


Explanation: A JOB DISPLAY jobname command was entered, but the name is invalid.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0266I

JOB: ‘jobname’ NOT FOUND
or
NO JVLS FOUND
or
NO JVL WORK TO DO
or
NO MATCHING JVLS


Explanation: If a JOB DISPLAY jobname command was entered, there was no job with that name in the system. If a JVL command was entered:


    • NO JVLS FOUND indicates that there are no JVLs in the system.
    • NO JVL WORK TO DO is the response to a JVL DISPLAY NOTDONE when all JVLs in the system have been DONE.
    • NO MATCHING JVLS indicates that there are JVLs in the system but none match the criteria specified in the JVL DISPLAY command.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0267I

INTERFACE ERROR ENCOUNTERED. R1 = x’error codes’
- COMMAND ABORTED -


Explanation: This is an internal diagnostic message.

DTM0268I

DUPLICATE JOBS WITH JOBNAME: ‘jobname’ DETECTED
Jjobnum     Jjobnum     Jjobnum     Jjobnum     Jjobnum
Jjobnum     Jjobnum     Jjobnum     Jjobnum     Jjobnum     [MORE...]
or
MULTIPLE MATCHING JVLS
    JOB          NAME      SUBMIT     NODE     VOL      PVR
====== =======  ======  =====   ====   ==== jobnum     jobname   hh:mm:ss   node-id    nnn      nnn


Explanation: A JOB DISPLAY or JVL DISPLAY jobname was entered but more than one job with that name was found.

For JOB DISPLAY, up to 10 job numbers are displayed. If there are more than 10 jobs with the same name the text MORE... appears on the right bottom line.

System action: None.

Operator Response: Re-enter the command using a specific job number.

Programmer Response: None.

DTM0269I

INFORMATION FOR type: jobnumber jobname NOT AVAILABLE


Explanation:
type: is either JVL or JOB.
For JVL, a JVL DISPLAY jobnumber command was entered, but there was no corresponding JVL.
For JOB, a JOB DISPLAY jobname command was entered, but there was no Job Information collected.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0270I

JVL REGENERATED FOR JOB jobnumber jobname AND SENT TO
DESTINATION destination-name


Explanation: A JVL has been regenerated.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0271I

JVL SUMMARY - type
    JOB         NAME           SUBMIT         NODE       VOL  PVR
====== ======== ======== ======== === ===
jobnum      jobname       hh:mm:ss       node-id     nnn  nnn


Explanation:
type: is the type of JVL summary requested, and can be ALL or TO BE DONE.
This is the response to a JVL DISPLAY command that does not identify a specific JVL.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0272I

COMMAND REJECTED. THIS FORM REQUIRES A VOLUME INFORMATION FILE


Explanation: Certain JVL command formats require a Volume Information File:

  • JVL DISPLAY with no parameters.
  • JVL DISPLAY with ALL or NOTDONE parameters.
  • Any JVL command with the NODE parameter.
  • Any JVL command with the SUBMITTED parameter.

System action: The command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Check to see why the VIF is not active. The VIF is required for JSS.

DTM0273I

COMMAND REJECTED. NAME PATTERN REQUIRES A VOLUME INFORMATION FILE


Explanation: Certain JVL command formats require a Volume Information File:

  • JVL DISPLAY with no parameters.
  • JVL DISPLAY with ALL or NOTDONE parameters.
  • Any JVL command with the NODE parameter.
  • Any JVL command with the SUBMITTED parameter.

System action: The command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Check to see why the VIF is not active. The VIF is required for JSS.

DTM0300I

SYSPARM I/O ERROR:
jobname,stepname,devno,devtyp,SYSPARM,op,err,bbcchhr,BSAM


Explanation: An I/O error was detected while reading SYSPARM.
The format of this message conforms with the MVS standard error message. For a complete explanation see to MVS System Messages, message number IEA000I.

System action: TMSS initialization processing is terminated, and TMSS terminates with return code 24.

Operator Response: Notify personnel responsible for support.

Programmer Response: Diagnose and correct the I/O error.

DTM0301I

SYSPARM OPEN ERROR, SYSTEM ABEND abend-code reason


Explanation: A system abend was detected while opening the SYSPARM data set.

System action: TMSS initialization processing is terminated, and TMSS terminates with return code 24.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the indicated error.

DTM0302I

UNABLE TO OPEN SYSPARM, DEFAULTS USED


Explanation: The data set specified by the SYSPARM DD statement cannot be opened.

System action: Default settings are used for all initialization options.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the error.

DTM0303I

SYSPARM ERROR, NUMBER OF CONTINUATION RECORDS EXCEEDED THE MAXIMUM ALLOWED,
STATEMENT IGNORED


Explanation: The number of records a single control statement can span is 50. A single control statement has exceeded this limit, and is ignored.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TMSS initialization statement in error.

DTM0304I

SYSPARM ERROR, RECORD=up-to-72-characters-of-text


Explanation: A syntax error was detected. The input record shown in up-to-72-characters-of-text has one of the following:

  • unbalanced apostrophes coded.
  • number of nested parentheses exceeded the allowed maximum of 16.
  • unbalanced parentheses coded.
  • a non-comment character string is longer than the allowed maximum of 64 characters.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TMSS initialization statement in error.

DTM0305I

SYSPARM ERROR, A KEYWORD EXPECTED BUT ‘text’ WAS FOUND


Explanation: a syntax error was detected. TMSS expected to encounter an option keyword but found text. Text displays up to 20 characters of the data found.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TMSS initialization statement in error.

DTM0306I

SYSPARM ERROR, FOR KEYWORD ‘keyword’ A ‘(‘ EXPECTED BUT ‘text’ WAS FOUND


Explanation: a syntax error was detected. TMSS expected to find a left parenthesis signaling that the data for keyword is to follow, but text was found.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TMSS initialization statement in error.

DTM0307I

SYSPARM ERROR, FOR KEYWORD ‘keyword’ A ‘)’ EXPECTED BUT ‘text’ WAS FOUND


Explanation: A syntax error was detected. TMSS expected to find a right parenthesis signaling that the end of data for option keyword is reached but text was found.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TMSS initialization statement in error.

DTM0308I

SYSPARM ERROR, FOR KEYWORD ‘keyword’ EXTRANEOUS DATA ‘text’ IGNORED


Explanation: A syntax error was detected. TMSS has encountered extraneous data for keyword. The extraneous data is ignored.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the keyword in error.

DTM0309I

SYSPARM ERROR, FOR KEYWORD ‘keyword’ type CODED IS INVALID


Explanation:
type: is the type of data expected.
A syntax error was detected. Invalid data was coded for keyword.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the keyword in error.

DTM0310I

*** WARNING *** function FUNCTION NOT INSTALLED.
[TMSS | PCS] INITIALIZATION CONTINUING


Explanation: There was an attempt to perform an initialization function for a ThruPut Manager Option that is not installed.

System action: ThruPut Manager initialization continues.

Operator Response: Notify personnel responsible for support.

Programmer Response: Ensure that the missing function has been installed properly.

DTM0311I

SYSPARM ERROR, EXPECTED CONTINUATION STATEMENT NOT ENCOUNTERED


Explanation: An error was detected in the input control statements. End-of-file was detected before the continuation of a continued statement.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the statement in error.

DTM0314I

Thruput Manager SYSPARM PROCESSING COMPLETE - COMPLETION CODE=code


Explanation: The TMSS initialization options were processed with highest return code code.

System action: If code is zero, all options were processed successfully.
If code is not zero, syntax errors or specification errors were detected and TMSS processing is terminated with return code 24.

Operator Response: If code is not zero, notify personnel responsible for support.

Programmer Response: Correct the errors documented by previous messages.

DTM0315I

UNKNOWN FUNCTION: function


Explanation: During initialization processing, TMSS encountered a statement which did not begin with a ThruPut Manager function identifier.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the statement in error.

DTM0316I

‘function-name’ FUNCTION REQUEST IS INVALID: request


Explanation: During initialization processing, TMSS encountered a statement which began with a valid ThruPut Manager function, but could not recognize the request as valid for that function.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the statement in error.

DTM0317I

‘function-name’ FUNCTION REQUEST NOT SPECIFIED


Explanation: During initialization processing, TMSS encountered a statement which began with a valid ThruPut Manager function, but no request for services was specified.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the statement in error.

DTM0318I

‘function-name’ ‘request’ INVALID KEYWORD: keyword


Explanation: During initialization, TMSS could not recognize a keyword for the indicated request for services from a ThruPut Manager function.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the statement in error.

DTM0319I

‘function-name’ ‘request’ REQUIRED KEYWORD NOT SPECIFIED


Explanation: During initialization, TMSS encountered a statement which did not include a required keyword.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the statement in error.

DTM0320I

STATEMENT ERROR ON LINE nn [THROUGH nn]


Explanation: During initialization, TMSS found errors for the initialization statement at line nn of the SYSPARM input, or the continued statement which occupies the range of lines nn through nn.

System action: TMSS terminates with a return code of 24.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the statement in error.

DTM0321I

INVALID text DETECTED - data
or
UNEXPECTED ‘statement’ STATEMENT ENCOUNTERED


Explanation: statement: is the misplaced statement.
text: is the part of the statement which contains the error.
data: is the data in error.
A syntax error was detected while parsing the TM EXIT initialization statement or the TM EXIT operator command. The data indicated by data was invalid or an out-of-place statement has been detected.

System action: If processing a TM EXIT initialization statement, this error causes TMSS to terminate. If processing a TM EXIT command, the command is terminated.

Operator Response: If entering a command, re-enter correctly. If the message is caused by a TM EXIT initialization statement, notify personnel responsible for support.

Programmer Response: Correct the TM EXIT initialization statement.

DTM0322I

MODULE module-name NOT FOUND


Explanation: An error was detected while processing the TM EXIT initialization statement. If the installation exit gets passed control from the Job Analyzer, the module must reside in either LPA or the LNKLST; otherwise, the module must reside in LPA, the LNKLST, or in STEPLIB or JOBLIB.

System action: This error causes TMSS to terminate.

Operator Response: Notify personnel responsible for support.

Programmer Response: Ensure that the module module-name resides in the correct library.

DTM0322I

‘ENDFOR’ STATEMENT MISSING


Explanation: While in a FOR group the EOF has occurred before finding an ENDFOR statement.

System action: TMSS terminates with a return code of 4.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the statement in error.

DTM0323I

STATEMENT ‘function-name’ NOT VALID WITHIN ‘FOR’ GROUP


Explanation: A TMSS initialization statement that is not allowed within a FOR group has been encountered.

System action: TMSS terminates with a return code of 8.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the statement in error.

DTM0324I

text MISSING


Explanation: A syntax error was detected while parsing the TM EXIT initialization statement or the TM EXIT operator command.

System action: If processing a TM EXIT initialization statement, this error causes TMSS to terminate. If processing a TM EXIT command, the command is terminated.

Operator Response: If entering a command, re-enter correctly. If the message is caused by a TM EXIT initialization statement, notify personnel responsible for support.

Programmer Response: Correct the TM EXIT initialization statement.

DTM0325I

EXIT exit-number NOT DEFINED


Explanation: An error was detected while processing the TM EXIT operator command. The exit exit-number was not modified since it was not defined by a TM EXIT initialization statement.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0326I

EXIT exit-number NOT MODIFIED; EXIT PERMANENTLY ACTIVE


Explanation: An error was detected while processing the TM EXIT operator command. The INACTIVE keyword was rejected for exit exit-number because the exit was marked permanently active by the TMSS initialization statement that defined it.

System action: Processing of the command is terminated.

Operator Response: None.

Programmer Response: None.

DTM0327I

EXIT exit-number status, TRACE mode


Explanation: This message is issued after a TM EXIT operator command was successfully processed.

System action: The status of installation exit exit-number was set as indicated in the message.

Operator Response: None.

Programmer Response: None.

DTM0328I

EXIT exit-number DEFINED MORE THAN ONCE


Explanation: An error was detected while processing the TM EXIT initialization statements. More than one TM EXIT statement was found in SYSPARM for installation exit number exit-number.

System action: This error causes TMSS to terminate.

Operator Response: Notify personnel responsible for support.

Programmer Response: Remove the duplicate TM EXIT statement.

DTM0329I

CONFLICTING KEYWORDS


Explanation: An error was detected while processing the TM EXIT initialization statement or the TM EXIT operator command. More than one of the options ACTIVE, INACTIVE, or PERMANENT were specified, or both ON and OFF were specified.

System action: If processing a TM EXIT initialization statement, this error causes TMSS to terminate. If processing a TM EXIT command, the command is terminated.

Operator Response: If entering a command, re-enter correctly. If the message is caused by a TM EXIT initialization statement, notify personnel responsible for support.

Programmer Response: Correct the TM EXIT initialization statement.

DTM0330I

TM EXIT DISPLAY
EXIT —-STATUS—- -MODULE- TRACE LEN ——————PARM DATA——————
 nn          status          module     state  nnn    data
status: is the current status of the exit, and is one of ACTIVATED, ACTIVATED(P) (permanently activated), DEACTIVATED, or NO ROUTINE.
state: is the current state of tracing, and is either ON or OFF.


Explanation: A TM EXIT DISPLAY command was entered.

System action: Displays a table showing data for each exit.

Operator Response: None.

Programmer Response: None.

DTM0337I

A ‘FILE CF’ INITIALIZATION STATEMENT IS MISSING


Explanation: The Control File is mandatory, but the FILE CF initialization statement was not found.

System action: TMSS terminates with a condition code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Allocate a Control File and include a FILE CF initialization statement.

DTM0338I

RSS REQUIRES A ‘FILE VIF’ INITIALIZATION STATEMENT


Explanation: RSS has been ENABLED, but the FILE VIF initialization statement was not found.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Provide the FILE VIF initialization statement, or disable RSS by using the OPTIONS keyword of the TMPARM JES2 initialization statement, then re-cycle JES2.

DTM0339I

RSS REQUIRES THAT JSS BE ENABLED


Explanation: RSS has been installed and enabled, but either JSS has not been enabled or TM MODE JSSV3 has been specified.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Contact personnel responsible for support.

Programmer Response: Correct the TMSS initialization control statement in error.

DTM0340I

TM TRACE - NO FUNCTION SPECIFIED


Explanation: A syntax error was detected while parsing the TM TRACE initialization statement. For this statement, a keyword must be specified to indicate which function to perform.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TM TRACE initialization statement.

DTM0341I

TM TRACE - EXPECTED KEYWORDS NOT FOUND FOR FUNCTION ‘function-requested’


Explanation: A syntax error was detected while parsing the TM TRACE initialization statement. One or more keywords are expected for function-requested.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TM TRACE initialization statement.

DTM0342I

TM TRACE - EXPECTED A KEYWORD FOR ‘function-requested’ BUT ‘text’ WAS FOUND


Explanation: A syntax error was detected while parsing the TM TRACE initialization statement. Keywords are expected for function-requested but text is invalid.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TM TRACE initialization statement.

DTM0343I

TM TRACE - FOR KEYWORD ‘keyword’ A ‘(‘ EXPECTED BUT ‘text’ WAS FOUND


Explanation: A syntax error was detected while parsing the TM TRACE initialization statement. TMSS expected to find a left parenthesis signaling that the data for keyword keyword is to follow but text was found.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TM TRACE initialization statement.

DTM0344I

TM TRACE - FOR KEYWORD ‘keyword’ A ‘)’ EXPECTED BUT ‘text’ WAS FOUND


Explanation: A syntax error was detected while parsing the TM TRACE initialization statement. TMSS expected to find a right parenthesis signaling that the end of data for keyword keyword was reached, but text was found.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TM TRACE initialization statement.

DTM0345I

TM TRACE - ‘text’ CODED IS INVALID FOR KEYWORD ‘keyword’


Explanation: A syntax error was detected while parsing the TM TRACE initialization statement. TMSS expected to find valid data for keyword, but the parameter coded was invalid.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TM TRACE initialization statement.

DTM0346I

TM TRACE - KEYWORD ‘keyword’ SPECIFIED IS INVALID
FOR ‘function-requested’


Explanation: A syntax error was detected in the TM TRACE initialization statement. Certain keywords only apply to certain functions. keyword is a recognized keyword for the TM TRACE statement, but is invalid for the function function-requested.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TM TRACE initialization statement.

DTM0347I

TM TRACE - FOR FUNCTION ‘function-requested’ EXPECTED KEYWORD ‘keyword’
WAS NOT FOUND


Explanation: A syntax error was detected while parsing the TM TRACE initialization statement. Some functions have mandatory keywords. TMSS did not find the keyword keyword for function-requested.

System action: TMSS terminates processing of the initialization statement. TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TM TRACE initialization statement.

DTM0350I

application REQUIRES THAT THE CONTROL FILE BE IN V6 MODE.
APPLICATION DISABLED


Explanation:
application: is the application serving one of the ThruPut Manager options, and can be one of:

  • DBS for Drive Booking Services.
  • SLM for System Level Manager.

This message is issued during initialization of the ThruPut Manager Started Task or as a result of a “TM OPT ENABLE application” command. It indicates that the named application (DBS or SLM) requires that the Control File be in V6 Mode.

System action: Processing continues.

Operator Response: Notify personnel responsible for support.

Programmer Response: Convert the Control File to Version 6.

DTM0351I

A FILE ‘filename’ initialization statement is required


Explanation:
filename: indicates the name of the missing file.
The specified FILE statement was not included in the TMSS or PCS Initializations Statements.

System action: The ThruPut Manager started task (TMSS or PCS) terminates.

Operator Response: Contact System Programmer.

Programmer Response: Add the required statement to the TMSS or PCS Initialization Statements.

DTM0352I

Unable to OPEN dsname


Explanation:
During OPEN of ThruPut Manager file an open error occurred. This would typically be do to a S913 security error. Accompanying error messages will be in the log.

System action: Access to the file is denied.

Operator Response: Contact System Programmer.

Programmer Response: None.

DTM0400I

FUNCTION NOT SPECIFIED


Explanation: A syntax error was detected in the TM TRACE command. For this command, a keyword must be specified to indicate which function to perform.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0401I

EXPECTED KEYWORDS NOT FOUND FOR FUNCTION ‘function-requested’


Explanation: A syntax error was detected in the TM TRACE command. For this command, one or more keywords are expected for function-requested.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0402I

INVALID KEYWORD ‘text’ FOUND


Explanation: A syntax error was detected in the TM TRACE command. For this command, a number of keywords are expected, but text is invalid.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0403I

EXPECTED A ‘(‘ FOR KEYWORD ‘keyword’ BUT ‘text’ WAS FOUND


Explanation: A syntax error was detected in the TM TRACE command. TMSS expected to find a left parenthesis signaling that the data for keyword is to follow, but text was found.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0404I

EXPECTED A ‘)’ FOR KEYWORD ‘keyword’ BUT ‘text’ WAS FOUND


Explanation: A syntax error was detected in the TM TRACE command. TMSS expected to find a right parenthesis signaling that the end of data for keyword is reached, but text was found.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0405I

‘text’ CODED IS INVALID FOR KEYWORD ‘keyword’


Explanation: A syntax error was detected in the TM TRACE command. TMSS expected to find valid data for keyword, but the parameter coded was invalid.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0406I

KEYWORD ‘keyword’ SPECIFIED IS INVALID FOR FUNCTION ‘function-requested’


Explanation: A syntax error was detected in the TM TRACE command. Certain keywords only apply to certain functions. While keyword is one of the recognized keywords for the TM TRACE command, it is invalid for function-requested.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0407I

EXPECTED KEYWORD ‘keyword’ FOR ADD WAS NOT FOUND


Explanation: A syntax error detected in the TM TRACE command. For ADD, keywords JOBNAME and ID are mandatory. The TM TRACE command processor did not encounter keyword for the ADD function.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0412I

TRACE DISPLAY
global options status
jobname options status


Explanation: This display is issued in response to a TM TRACE command, and reflects the current status of the trace options.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0460I

UNIDENTIFIED KEYWORD: data


Explanation: The data shown could not be identified as a keyword of the CPS DISPLAY command.

System action: The command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0461I

SPOOL PROCESSOR IS NOT AVAILABLE


Explanation: The SPOOL processor is not available to process the command.

System action: The command is terminated.

Operator Response: None.

Programmer Response: None.

DTM0462I

CPS SPOOL CONTROL RECORD DAMAGE DETECTED


Explanation: The SPOOL processor detected damage in the CPS SPOOL File Control Record and could not process the command.

System action: The command is terminated.

Operator Response: Notify personnel responsible for support.

Programmer Response: See accompanying message DTM0130I.

DTM0463I

option1-name OPTION SPECIFIED WHEN option2-name WAS ALREADY SPECIFIED


Explanation: Mutually exclusive options option1-name and option2-name2 were specified.

System action: The command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0464I

THE SPOOL PROCESSOR IS OPERATING WITHOUT A SPOOL FILE


Explanation: The SPOOL processor is operating without a CPS SPOOL File and a CPS DISPLAY command was issued.

System action: The command is terminated.

Operator Response: None.

Programmer Response: None.

DTM0465I

CPS SPOOL FILE STATUS
DATASET NAME: dsname
SYSTEMS:                                 ss
CPS WRITERS:                         ww
DESTINATIONS:                      ddd
RECORDS QUEUED:                 rrr
I/O ERRORS:                             ee
AVAILABLE SPACE:                   aa    PERCENT


Explanation:
dsname: is the name of the CPS SPOOL File.
ss: is the number of systems sharing this CPS SPOOL File. To display their names and status, use the CPS DISPLAY SYSTEMS command.
ww: is the number of CPS Writers defined. To display their names and status, use the CPS DISPLAY WRITER command.
ddd: is the number of destinations defined. To display them, use the CPS DISPLAY DESTS command.
rrr: is the number of records queued in the file. To display their destinations, use the CPS DISPLAY RECORDS command.
ee: is the number of slots in the CPS SPOOL File that have been flagged unusable because of I/O errors.
aa: is the percentage of the space in the file that is available for additional records.

This message is issued in response to the CPS DISPLAY command without additional keywords. It displays general information about the contents of the CPS SPOOL File.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0466I

THERE ARE NO DESTINATIONS CURRENTLY ASSIGNED


Explanation: This message is issued in response to the CPS DISPLAY DESTS command. It indicates that there are no destinations known to the SPOOL processor at this time. A destination must be assigned to a CPS Writer or used in a CPS SPOOL record for the SPOOL processor to be aware of its existence.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0467I

THERE ARE NO RECORDS SPOOLED


Explanation: This message is issued in response to the CPS DISPLAY RECORDS command. It indicates that there are no records in the CPS SPOOL File.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0468I

UNIDENTIFIED KEYWORD: data


Explanation: The data shown could not be identified as a keyword of the CPS DISPLAY WRITER command.

System action: The command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0469I

SPOOL PROCESSOR IS NOT AVAILABLE


Explanation: The SPOOL processor is not available to process the command.

System action: The command is terminated.

Operator Response: None.

Programmer Response: None.

DTM0470I

CPS SPOOL CONTROL RECORD DAMAGE DETECTED


Explanation: The SPOOL processor detected damage in the CPS SPOOL Control Record and could not process the command.

System action: The command is terminated.

Operator Response: Notify personnel responsible for support.

Programmer Response: See accompanying message DTM0130I.

DTM0471I

INVALID CPS WRITER NAME: writer-name


Explanation: The CPS Writer name specified in a CPS DISPLAY WRITER command is invalid for one of the following reasons:

  • its length exceeds 8 characters,
  • the name contains characters which are not alphanumeric.

System action: The command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0472I

CPS WRITER writer-name NOT DEFINED


Explanation: The CPS Writer name specified in a CPS DISPLAY WRITER command is not defined.

System action: The command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0473I

REQUIRED PARAMETER SYSTEM ID NOT SPECIFIED


Explanation: The required system identifier was not specified in a CPS SPOOL command.

System action: The command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0474I

INVALID SYSTEM ID: SMF-sys-id


Explanation: The system identifier supplied in a CPS SPOOL command had invalid syntax.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0475I

INVALID SUBSYSTEM ID: subsys-id


Explanation: The subsystem identifier specified in a CPS SPOOL command had invalid syntax.

System action: The command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0476I

SPOOL PROCESSOR IS NOT AVAILABLE


Explanation: The SPOOL processor is not available to process the command.

System action: The command is terminated.

Operator Response: None.

Programmer Response: None.

DTM0477I

CPS SPOOL CONTROL RECORD DAMAGE DETECTED


Explanation: The SPOOL processor detected damage in the CPS SPOOL Control Record and could not process the command.

System action: The command is terminated.

Operator Response: Notify personnel responsible for support.

Programmer Response: See accompanying message DTM0130I.

DTM0478I

SYSTEM SMF-sys-id IS BEING USED BY MORE THAN ONE SUBSYSTEM.
SPECIFY SUBSYSTEM ID


Explanation: A CPS SPOOL command specified only a system identifier, but there is more than one subsystem active on the specified system.

System action: The command is terminated.

Operator Response: Re-enter specifying a subsystem identifier.

Programmer Response: None.

DTM0479I

SYSTEM SMF-sys-id NOT DEFINED


Explanation: The system identifier specified in a CPS SPOOL command is not known to the SPOOL processor.

System action: The command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0480I

SYSTEM SMF-sys-id SUBSYSTEM subsys-id NOT DEFINED


Explanation:
SMF-sys-id: is an SMF system identifier.sub
subsys-id: is a JES2 subsystem identifier.

The system-subsystem combination specified in a CPS SPOOL is not known to the SPOOL processor.

System action: The command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0481A

SYSTEM SMF-sys-id SUBSYSTEM subsys-id IS ACTIVE. SPECIFY ‘Y’ TO CONTINUE
OR ‘N’ TO TERMINATE EXECUTION OF COMMAND


Explanation: The system-subsystem combination specified in a CPS SPOOL command is marked active. Operator confirmation is required to continue.

System action: The command waits for the operator to reply.

Operator Response: Reply ‘Y’ to continue, ‘N’ to abort.

Programmer Response: None.

DTM0482I

SYSTEM SMF-sys-id SUBSYSTEM subsys-id action-taken


Explanation: The system-subsystem combination specified in a CPS SPOOL command was successfully reset or purged.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0483I

action-requested OF HOME SYSTEM NOT ALLOWED


Explanation: The operator attempted to reset or purge the system on which the CPS SPOOL command was issued.

System action: The command is terminated.

Operator Response: None.

Programmer Response: None.

DTM0484I

action TERMINATED BY OPERATOR


Explanation: The operator replied ‘N’ to message DTM0481A.

System action: The command is terminated.

Operator Response: None.

Programmer Response: None.

DTM0485I

UNIDENTIFIED KEYWORD: data


Explanation: The data shown could not be identified as a keyword of the CPS SPOOL command.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0490I

SPOOL PROCESSOR STATUS
SYSTEM     SUBSYSTEM     STATUS     WRITER     COUNT
sysid             subsys-id        status                               ww


Explanation:
sys: is the SMF system identifier of the system on which that TMSS runs.
subsys-id: is subsystem name of the JES2 under which that TMSS runs.
status: is one of the following:

  • ACTIVE indicates that TMSS and its SPOOL processor are active, or if not, that they did not terminate normally.
  • INACTIVE indicates that TMSS or its SPOOL processor is currently inactive.

ww: is the number of CPS Writers defined under that TMSS.
The CPS DISPLAY SYSTEMS command was issued. The status line is repeated once for each TMSS that is sharing the CPS SPOOL File.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0491I

CPS DESTINATIONS
DESTINATION      WRITER      COUNT      RECORD      COUNT
dest                                                ww                                  rrr


Explanation:
dest: is a CPS destination.
ww: is the number of CPS Writers to which this destination is assigned.
rrr: is the number of records with this destination in the CPS SPOOL File.

This message is issued in response to the CPS DISPLAY DESTS command. The status line is repeated once for each destination known to the SPOOL processor.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0492I

SPOOLED CPS RECORDS
DESTINATION      WRITER      COUNT      RECORD     COUNT
dest                                                ww                                 rrr


Explanation:
dest: is a CPS destination.
ww: is the number of CPS Writers to which this destination is assigned.
rrr: is the number of records with this destination in the CPS SPOOL File.

This message is issued in response to the CPS DISPLAY RECORDS command. The last line is repeated once for each destination that has records in the CPS SPOOL File.

System action: None.

Operator Response: None.

Programmer Response: None

DTM0551I

INVALID KEYWORD: keyword


Explanation: TMSS could not recognize a keyword for the entered command.

System action: Command processing is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0552I

INVALID VOLSER: volser


Explanation: The volume serial number entered is not valid.

System action: Command processing is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0553I

REQUIRED KEYWORD MISSING


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

Programmer Response: None.

DTM0554I

MUTUALLY EXCLUSIVE KEYWORDS SPECIFIED


Explanation: At least two of the keywords for the entered ThruPut Manager command are mutually exclusive.

System action: Command processing is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0555I

INVALID ‘VOLUME’ KEYWORD SYNTAX


Explanation: The syntax for the ‘VOLUME’ keyword of the entered command is not valid.

System action: The command is not processed.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0556I

VOLSER ‘volser’ MARKED AS type


Explanation: This message is issued in response to the VOL ADD command. It indicates that the volume was given the indicated special attribute.

System action: The volume was added to the indicated list of special volumes.

Operator Response: None.

Programmer Response: None.

DTM0557I

VOLSER ‘volser’ ALREADY MARKED AS type


Explanation: A command was entered to add the volume to the indicated list, but the volume was already in the list.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0558I

VOLSER ‘volser’ MARKED AS new-type. WAS MARKED AS old-type


Explanation: A command was entered to move a volume from one special list to another.

System action: The volume is moved as indicated.

Operator Response: None.

Programmer Response: None.

DTM0559I

ENTRY FOR [VOLSER] ‘volser’ NOT FOUND


Explanation: A command was entered specifying the indicated volume, but the volume was not found in any special status list.

System action: The volume is moved as indicated.

Operator Response: None.

Programmer Response: None.

DTM0560I

ENTRY FOR [VOLSER] ‘volser’ DELETED. WAS MARKED AS type


Explanation: A command was entered removing the volume from the indicated special status list.

System action: The volume is deleted from the list.

Operator Response: None.

Programmer Response: None.

DTM0561I

NO VOLSER ENTRIES FOUND


Explanation: A VOL DISPLAY command was entered, but there were no volumes found in any special status list.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0562I

VOLUME DISPLAY
PREFIX     VOLSER     STATUS
prefix         volser        status


Explanation:
prefix: is a prefix that indicates a generic group of volumes that have been defined with the VOL SET initialization statement or the VOL ADD command using the ‘*’ wildcard character.
status: is one of MIGRATE, RESIDENT, RETIRED, UNAVAILABLE, or *NOT FOUND*.
A VOLUME DISPLAY command was entered.

S ystem Action: Displays a status report for the requested volumes.

Operator Response: None.

Programmer Response: None.

DTM0563I

‘module’ NOT ALLOWED IN LPA. REFRESH LLA.


Explanation: This message is a response to ADS REINSTALL command. The ADS REINSTALL command attempted to load a module into LPA and was failed to prevent the need to IPL to get out of this situation.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0564I

task’ RESTARTED.


Explanation:
‘task’: can be HSMR, JBMW, MONS, SSI, TMOS and VVS.

This message is a feedback from command processing. The ADS command issued a REINSTALL for a task that does not issue messages when it restarts.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0666E

Thruput Manager ERROR DETECTED [recovery-action]
IN MODULE: module time date level
text
GPR      0 - 3      value0      value1      value2      value3
GPR      4 - 7      value4      value5      value6      value7
GPR      8 - 11     value8      value9      value10     value11
GPR      12 - 15   value12     value13    value14     value15


Explanation:
‘value0’ through ‘value15’: show the contents of all general purpose registers at the time of the error.

A component of ThruPut Manager has found an error condition preventing further processing. If recovery action was possible it is indicated.

System action: The ThruPut Manager component that detected the error terminates with a User 0666 Abend. An SVC dump might be taken as a result of the abend.

Operator Response: Notify personnel responsible for support.

Programmer Response: Report this problem to BMC Support. Have the module level information and register contents available, and the SVC dump if there is one.

DTM0750I

VOLUME ‘volser’ PULLED FOR CVL $ACCUMn, CYCLE cycle-number


Explanation: The volume was “pulled” as a result of the CVL indicated in message.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0751I

VOLUME volser PULLED details
or
VOLUME volser NOT FILED, REQUIRED BY JOBjobnumber jobname
or
VOLUME volser NOT FILED, REQUIRED BY CVL $ACCUMn CYCLE nnn


Explanation: If the command entered was JSS DISPLAY VOLUMES:

Details: describe how the volume was pulled, and can be one of:

  • FOR CVL $ACCUMn CYCLE nnn
  • FOR JOB jobnumber AT hh:mm ON day
  • BY OPERATOR AT hh:mm ON day

System action: The volume is not FILED.

Operator Response: None.

Programmer Response: None.

If the command entered was JSS FILE, the specified volume is still required by another job in the system.

System action: The volume is not FILED.

Operator Response: Do not remove the volume from the tape drive area until you are sure no more mounts will be issued.

Programmer Response: None.

DTM0754I

EVENT event IS status


Explanation: This message is issued in response to the JAL EVENT DISPLAY command. It shows the status of the event displayed (i.e. ON or OFF).

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0755I

NO OPERATOR CONTROLLED EVENTS


Explanation: This message is issued in response to the JAL EVENT DISPLAY command. It indicates that there are no events to display.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0756I

VOLUME volser status


Explanation: status: can be either FILED or PULLED. This message is issued in response to the JSS FILE or JSS PULL command.

System action: The volume is removed from or added to the VIF.

Operator Response: None.

Programmer Response: None.

DTM0757I

REQUIRED PARAMETER parameter MISSING


Explanation: An operator command was issued with a required parameter not supplied.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0758I

UNIDENTIFIED KEYWORD text


Explanation: text is the invalid keyword. An unidentified keyword was entered.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0759I

VOLUME volser ALREADY status


Explanation: status: can be either FILED or PULLED. This message is issued in response to a JSS FILE command for a volume that has already been FILED, or a JSS PULL command for a volume that is already PULLED.

System action: None.

Operator Response: Ensure that the correct volume serial number was entered.

Programmer Response: None.

DTM0760I

EVENT event-name ALREADY status


Explanation: A JAL EVENT operator command specified an event which was already in the requested state.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM0761I

EVENT event-name SET status


Explanation: This message is issued in response to the JAL EVENT operator command.

System action: The state of the event was changed as indicated.

Operator Response: None.

Programmer Response: None.

DTM0762I

type EVENT DISPLAY
--------- EVENT ---------      STATUS
event-name                           status


Explanation:
status: is the current status of the event, and can be one of ON, OFF, or NOT DEFINED. A DAL/JAL DISPLAY EVENT command was entered.

System action: Displays a table of events and their current status.

Operator Response: None.

Programmer Response: None.

DTM0763I

JSS VOLUME DISPLAY
VOLSER     PULLED     STATUS      ----------------- COMMENTS -----------------
volser         pulled        status       comments                                       typ nnnnn


Explanation:
volser: represents the volume serial number.
pulled: is either YES or NO, indicating whether the volume has been pulled.
status: if the volume is PULLED, indicates whether the volume is still REQUIRED by at least one job, or is FILEABLE. If the volume was PULLED using the JSS PULL command without the FILEABLE keyword, the status is JSS-FILE, indicating that it must be FILED using the JSS FILE command.
comments: can be NOT PULLED (self-explanatory) or NOT ENTERED, indicating the volume is required in an automated library but has not yet been entered, or if the volume is PULLED, indicates which job, CVL, RVL, or JSS PULL command requested the volume.

  • If the volume was PULLED by a job, the date and time are shown.
  • If the volume was requested by a CVL, the accumulator and cycle number are shown.
  • If the volume was requested by an RVL, the robot in which the volume is to be ENTERED or is PREFERRED is shown.
  • If the job was PULLED by a JSS PULL command, the date and time are shown.

typ: indicates the type of volume list, and is either JVL or CVL.
nnnnn: is an identifier for the volume list.

This display results from the JSS DISPLAY VOLUMES command.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0770I

LENGTH OF PARAMETER parameter EXCEEDED MAXIMUM


Explanation: An operator command exceeded the maximum length allowed for parameter’. (E.g., 7 characters specified for a volser when only 6 are allowed).

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0771I

COMMAND IGNORED BECAUSE OF EXCESSIVE PARAMETERS


Explanation: Too many parameters were specified for an operator command.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0773I

string NOT ALLOWED IN SYSPARM


Explanation: The indicated statement or keyword was supplied in the TMSS SYSPARM data set, but it is only legal from an operator console.

System action: The statement is ignored and TMSS initialization processing continues.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TMSS initialization statement.

DTM0774I

VOLUME volser FAILED BY INSTALLATION EXIT


Explanation: This message is issued in response to the JSS PULL or JSS FILE command. It indicates that installation exit 16 or 17 would not allow the function to be performed.

System action: The command is not performed for the volume specified.

Operator Response: Check with personnel responsible for support to determine why the command was denied.

Programmer Response: Consult your internal documentation for installation exits 16 and 17.

DTM0775I

VOLUME volser FAILED VIF IS FULL


Explanation: This message is issued in response to the JSS PULL command. It indicates that the function could not be performed because the volume could not be added to the VIF.

System action: The command is not performed.

Operator Response: Generate an FVL and return some volumes to the library. Use the FVL DONE command to free space in the VIF.

Programmer Response: Analyze the situation. If the problem occurs frequently, expand the VIF.

DTM0776I

VIF PROCESSOR IS UNAVAILABLE


Explanation: A command was entered that required the VIF processor, but the VIF processor is not available.

System action: The command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Determine why the VIF processor is not available. The VIF is required for JSS.

DTM0777I

VIF PROCESSOR ERROR[, VIF IS FULL]


Explanation: A command could not be performed because of a VIF processor error while handling the request.

System action: The command is not performed.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the error.

DTM0778I

nnnn VOLUMES FILED


Explanation: This message is issued in response to the JSS FILE command. It indicates the number of volumes which were filed.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0779I

keyword KEYWORD ALREADY SPECIFIED


Explanation: The indicated keyword was specified more than once.

System action: The command is not performed.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0780I

keyword MISSING ‘data’


Explanation: The indicated keyword was missing the data shown by data.

System action: The command is not performed.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0781I

VOLUME volser NO LONGER MARKED status


Explanation: The volume was found on the volume status queue and that its previous status was removed. (e.g. a volume was previously marked UNAVAILABLE and the command marked it as AVAILABLE).

System action: The previous status of the volume is altered.

Operator Response: None.

Programmer Response: None.

DTM0782I

VOLUME volser NOT FOUND IN ANY STATUS QUEUE


Explanation: The volume was not found in the volume status queue or the VIF.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0783I

DATA KEYWORD NOT ALLOWED WITH status


Explanation: The DATA keyword of the command is not supported with the indicated status.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0784I

type TRACE DISPLAY
type TRACING ‘text-for-global-trace’
‘text-for-job-specific-trace’


Explanation:
type: is either DAL or JAL.
This message is generated as a result of a DAL TRACE or JAL TRACE command. The second line of text indicates whether or not a request to trace ALL jobs is in effect. The second line of text indicates whether or not job specific tracing has been requested. If so, further lines of text are generated showing the jobs to be traced.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0785I

INVALID JOBNAME: text


Explanation: The jobname entered for a JAL TRACE command is not valid.

System action: The command is ignored.

Operator Response: Re-enter command with a valid jobname.

Programmer Response: None.

DTM0786I

INVALID STEP#: stepnum


Explanation: The step number entered for a DAL TRACE command is not valid.

System action: The command is ignored.

Operator Response: Re-enter command with a valid step number.

Programmer Response: None.

DTM0800I

THE VOLUME INFORMATION FILE IS FULL


Explanation: This message is entered when all entries in the VIF have been used. The number of entries is specified using the FILE VIF initialization statement.

System action: No volumes can be added to the VIF until volumes have been removed. This message is issued periodically as long as the VIF remains full. When the VIF is no longer full, the message is deleted.

Operator Response: Create and FVL and service it.

Programmer Response: None.

DTM0801I

UNABLE TO ALLOCATE VOLUME INFORMATION FILE


Explanation: During VIF initialization, dynamic allocation of the data set named in the TMSS initialization statement FILE VIF was unsuccessful. The accompanying message DTM0190I has further information.

System action: The VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: See message DTM0190I.

DTM0802I

THE VIF DATASET IS NOT ON A DIRECT ACCESS DEVICE


Explanation: The data set named in the TMSS initialization statement FILE VIF was found on a non-DASD device.

System action: VIF initialization is abandoned and the VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Allocate the VIF properly.

DTM0803I

THE VOLUME INFORMATION FILE IS dsname ON volser


Explanation: This message shows the name and location of the VIF.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0804I

VIF DATASET HAS ILLEGAL DSORG


Explanation: The data set named in message DTM0803I has a data set organization other than direct (DA) or undefined (U).

System action: The VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Allocate the VIF properly.

DTM0805A

IS A VIF COLD START AUTHORIZED? REPLY ‘Y’ OR ‘N’


Explanation: A VIF cold start was requested or found necessary. TMSS checks to be sure the VIF should be formatted.

System action: The VIF processor waits for a reply.

Operator Response: Reply ‘Y’ to continue with a format of the VIF. Reply ‘N’ to prevent a VIF format from occurring. DTM0822A is issued.

Programmer Response: None.

DTM0806I

VIF COLD START AUTHORIZATION DENIED BY OPERATOR


Explanation: The operator replied ‘N’ to message DTM0805A.

System action: The COLD start attempt is abandoned. If a WARM start can be done, TMSS offers that option.

Operator Response: None.

Programmer Response: None.

DTM0807I

VIF I/O ERROR

jobname,stepname,devno,devtyp,ddname,op,err,bbcchhr,EXCP


Explanation: An I/O error occurred during VIF processing. The format of this message conforms with the MVS standard error message. For a complete explanation see to MVS System Messages, message number IEA000I.

System action: If the I/O error occurred during WARM start processing, a COLD start is attempted; otherwise, the VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Diagnose and correct the I/O error.

DTM0808I

THE VOLUME INFORMATION FILE IS BEING FORMATTED


Explanation: A VIF COLD start was authorized and is proceeding. A WARM start is no longer possible with this VIF until it has been reformatted successfully.

System action: The VIF is formatted.

Operator Response: None.

Programmer Response: None.

DTM0809I

THE VOLUME INFORMATION FILE HAS BEEN FORMATTED


Explanation: The VIF was successfully formatted in response to a COLD start request. The VIF can now be WARM started during subsequent TMSS initializations.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0810I

VIF INITIALIZATION WAS UNSUCCESSFUL


Explanation: The VIF processor could not be initialized. The reason for this is indicated in an accompanying message.

System action: The VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: See accompanying message(s).

DTM0812I

LOCATE FOR VIF DATASET dsname FAILED, RETURN CODE=rc


Explanation: A catalog LOCATE for the VIF data set named by dsname failed with the return code rc.

System action: The VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Ensure that the VIF has been cataloged properly.

DTM0813I

NO VALID CONTROL RECORD FOUND IN VIF


Explanation: During WARM start processing, the VIF processor found that the data set named in message DTM0803I did not contain a valid VIF Control Record.

System action: The VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Determine why the VIF Control Record is not valid.

DTM0814I

VIF CONTROL RECORD IS INCOMPATIBLE WITH THIS LEVEL OF Thruput Manager


Explanation: The data set named in message DTM0803I was used as a VIF with a previous level of ThruPut Manager, but it is not compatible with this level.

System action: The VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Use the correct level of ThruPut Manager.

DTM0815I

THE VIF HAS NOT BEEN COMPLETELY FORMATTED.


Explanation: The data set named in message DTM0803I was partially formatted in a previous COLD start attempt that did not complete.

System action: The VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Format the VIF properly.

DTM0816I

THE CURRENT VIF FORMAT IS NOT COMPATIBLE WITH THE ‘VIF’ INITIALIZATION STMT.


Explanation: The VIF record format does not match the current ThruPut Manager initialization parameters.

System action: The VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the FILE VIF initialization statement.

DTM0817I

THE VIF PROCESSOR HAS BEEN SHUT DOWN


Explanation: The VIF processor terminated normally.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0818I

THE VIF DATASET MUST BE ALLOCATED IN ONE EXTENT


Explanation: The data set named in message DTM0803I is allocated in multiple extents.

System action: The VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Allocate the VIF in a single extent.

DTM0819I

FORMATTING OF VIF DATASET REQUIRES ANOTHER EXTENT


Explanation: Formatting of the data set named in message DTM0803I requires another extent for space.

System action: The VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Allocate enough space in a single extent to hold the VIF.

DTM0820I

THE VIF DATASET HAS BEEN MOVED TO AN UNLIKE DEVICE


Explanation: The VIF data set has been moved to an unlike device (e.g. IBM 3350 to IBM 3380).

System action: Issues message DTM0805A.

Operator Response: Reply to DTM0805A. Notify personnel responsible for support.

Programmer Response: Make sure the VIF resides on the same type of device used when it was originally formatted.

DTM0821I

VIF PROCESSOR TERMINATING DUE TO I/O ERROR


Explanation: An I/O error was encountered after the VIF processor was activated. This message is preceded by message DTM0807I.

System action: The VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: See message DTM0807I.

DTM0822A

DO YOU WISH TO DO A VIF WARM START INSTEAD? REPLY ‘Y’ OR ‘N’


Explanation: The operator replied ‘N’ to DTM0805A requesting permission to format the VIF.

System action: The VIF processor waits for a reply.

Operator Response: If a WARM start is desired, reply ‘Y’. The VIF processor tries to use the existing VIF. If you do not want the VIF processor to continue, reply ‘N’.

Programmer Response: None.

DTM0823I

VIF TIME STAMP VALIDATION FAILED


Explanation: During WARM start processing, the VIF processor found that the time stamps contained within the VIF data set were invalid

.System action: Issues message DTM0805A.

Operator Response: Reply to DTM0805A.

Programmer Response: None.

DTM0824I

VIF PROCESSOR TERMINATING DUE TO TIME STAMP MISMATCH


Explanation: The time stamps contained within the VIF data set did not match.

System action: The VIF processor terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Re-format the VIF.

DTM0825A

OK TO CONVERT VIF TO V4.1 FORMAT? REPLY ‘Y’ OR ‘N’


Explanation: JSS Version 4 is starting, but the VIF was created under Version 3 and has never been used by Version 4.

System action: Awaits operator response. If permission is granted, the VIF is formatted for Version 4, otherwise JSS continues without a VIF.

Operator Response: Reply ‘Y’ to format the VIF. All existing data will be lost and it will no longer be possible to use this VIF with Version 3 or Version 3 Compatibility mode. Reply ‘N’ to continue without a VIF, then notify personnel responsible for support, since JSS V4 requires a VIF.

Programmer Response: If the desired version of JSS is Version 4, arrange to format the VIF. JSS V4 requires a VIF. If the desired version of JSS is Version 3, determine why Version 4 was being started.

DTM0826I

VIF VERSION 4.1 CONVERSION AUTHORIZATION DENIED BY OPERATOR


Explanation: The operator replied ‘N’ to DTM0825A.

System action: The VIF is not altered. JSS continues without a VIF.

Operator Response: Notify personnel responsible for support.

Programmer Response: If the desired version of JSS is Version 4, arrange to format the VIF. JSS V4 requires a VIF. If the desired version of JSS is Version 3, determine why Version 4 was being started.

DTM0827I

VIF CONVERTED TO VERSION 4.1 FORMAT


Explanation: The operator replied ‘Y’ to message DTM0825A.

System action: JSS starts up in Version 4 mode.

Operator Response: None.

Programmer Response: None.

DTM0830I

THE VOLUME INFORMATION FILE IS nn% FULL


Explanation: This message is issued when the VIF utilization is at 85%, 90%, 95%, 97%,...

System action: This is a warning message. When the VIF becomes full, no new jobs can be processed. When the VIF usage falls below 85%, this message is deleted and message DTM0831I is issued.

Operator Response: Generate an FVL and return some volumes to the library. Use the FVL DONE command to free space in the VIF.

Programmer Response: Analyze the situation. If the problem occurs frequently, expand the VIF.

DTM0831I

VIF CAPACITY SHORTAGE RELIEVED


Explanation: This message is issued after DTM0830I. It indicates that the VIF usage is below 85%.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM0832I

VIF INITIALIZATION COMPLETE


Explanation: VIF cold start processing has completed.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0835I

VIF PROCESSOR WAS UNABLE TO OBTAIN EXCLUSIVE CONTROL OF VIF FOR COLD START PROCESSING


Explanation: During a VIF cold start, the VIF processor could not gain exclusive control of the VIF because another ThruPut Manager is sharing the file.

System action: The VIF processor terminates with a return code of 24.

Operator Response: If a cold start is required, ensure that all ThruPut Manager sharing the VIF are shut down.

Programmer Response: None.

DTM0836I

VOLUME volser HAS BEEN action, REQUIRED location


Explanation:
action: can be either EJECTED or ENTERED.
location: is the desired location, and can be either INSIDE ROBOT or OUTSIDE OF ROBOT.

This message is issued when a volume is moved from its desired location.

System action: Makes the message non-deletable, and deletes the message automatically when the volume is returned to its desired location, or the requesting job completes execution or is cancelled.

Operator Response: Return the volume to its desired location.

Programmer Response: None.

DTM0837I

n1 JOBS WAITING FOR n2 VOLUMES TO BE action
or
n1 JOBS WAITING FOR n2 VOLUMES TO BE ENTERED,
n3 JOBS WAITING FOR n4 VOLUMES TO BE EJECTED


Explanation:
action: is the action to be taken, and can be either ENTERED or EJECTED.

The JSS OPTIONS RSS_ALERT initialization statement has indicated that RSS Alerts are to be issued during ATTENDED mode, and ThruPut Manager has detected that there are volumes to be entered or ejected from an automated library unit.

System action: This message is made non-deletable and is refreshed once per minute as long as there are volumes requiring action. The message is deleted automatically when there are no volumes to be entered or ejected.

Operator Response: Use the RVL GEN command to determine which volumes require action.

Programmer Response: None.

DTM0838I

n1 JOBS WAITING FOR n2 VOLUMES TO BE action
or
n1 JOBS WAITING FOR n2 VOLUMES TO BE ENTERED,
n3 JOBS WAITING FOR n4 VOLUMES TO BE EJECTED


Explanation:
action: is the action to be taken, and can be either ENTERED or EJECTED.

The JSS OPTIONS RSS_ALERT_UNATTENDED initialization statement has indicated that RSS Alerts are to be issued during UNATTENDED mode, and ThruPut Manager has detected that there are volumes to be entered or ejected from an automated library unit.

System action: This message is made non-deletable and is refreshed once per minute as long as there are volumes requiring action. The message is deleted automatically when there are no volumes to be entered or ejected.

Operator Response: Use the RVL GEN command to determine which volumes require action.

Programmer Response: None.

DTM0875I

INVALID VIF DATASET NAME: dsname


Explanation: During initialization, TMSS found that the data set name specified on the FILE VIF initialization statement was invalid.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Specify the name of the VIF data set correctly.

DTM0876I

REQUIRED VIF DATASET NAME NOT SPECIFIED


Explanation: The FILE VIF initialization statement did not include a data set name.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Include a data set name on the FILE VIF initialization statement.

DTM0877I

INVALID SYNTAX IN THE ‘keyword’ KEYWORD ON THE FILE VIF STATEMENT


Explanation: During initialization, TMSS detected a syntax error in the indicated keyword of the FILE VIF initialization statement.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the keyword in error.

DTM0878I

INVALID FILE VIF STATEMENT KEYWORD SYNTAX: text


Explanation:
text: is up to 20 characters of the text in error.

During initialization, TMSS found invalid characters in the FILE VIF statement where a keyword was expected.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the FILE VIF initialization statement.

DTM0879I

INVALID FILE VIF STATEMENT KEYWORD: keyword


Explanation: During initialization, TMSS encountered an unknown keyword or abbreviation.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the FILE VIF initialization statement.

DTM0880I

THE keyword KEYWORD VALUE ON THE FILE VIF STATEMENT
IS NOT NUMERIC: value


Explanation: During initialization, TMSS encountered a non-numeric value where a numeric value is required.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the FILE VIF initialization statement.

DTM0881I

THE keyword KEYWORD VALUE ON THE FILE VIF STATEMENT IS OUT OF RANGE: value


Explanation: During initialization, TMSS found that the value specified for keyword was not within the allowed range.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the FILE VIF initialization statement.

DTM0882I

THE keyword KEYWORD ON THE FILE VIF STATEMENT HAS BEEN SPECIFIED MORE THAN ONCE


Explanation: During initialization, TMSS found that the indicated keyword was specified more than once.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Remove the duplicate keyword.

DTM0900I

INVALID CPS SPOOL FILE DATASET NAME: dsname


Explanation: During initialization, TMSS found that the data set name specified on the FILE SPOOL initialization statement was invalid.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Specify the name of the CPS Spool File correctly.

DTM0901I

REQUIRED CPS SPOOL FILE DATASET NAME NOT SPECIFIED


Explanation: The FILE SPOOL initialization statement did not include a data set name.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Include a data set name on the FILE SPOOL initialization statement.

DTM0902I

CPS WRITER NAME IS TOO LONG: writer-name


Explanation: In a CPS WRITER initialization statement or CPS WRITER command, the name entered is too long to be a valid CPS Writer name.

System action: If the error was in an operator command, the command is not processed. If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.Operator Response: If the error was in an operator command, re-enter the command correctly. If the error was in a TMSS initialization statement, notify personnel responsible for support.Programmer Response: Correct the CPS WRITER initialization statement.

DTM0903I

CPS WRITER NAME IS INVALID: writer-name


Explanation: In a CPS WRITER initialization statement or CPS WRITER command, the CPS Writer name contains invalid characters.

System action: If the error was in an operator command, the command is not processed. If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly. If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0904I

NO CPS WRITER NAME SPECIFIED


Explanation: No name was entered on a CPS WRITER initialization statement or CPS WRITER command.

System action: If the error was in an operator command, the command is not processed. If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly. If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0905I

INVALID KEYWORD SYNTAX: keyword


Explanation: In a CPS WRITER initialization statement or CPS WRITER command, invalid characters were found where a keyword was expected.

System action: If the error was in an operator command, the command is not processed. If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly. If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0906I

INVALID KEYWORD: keyword


Explanation: In a CPS WRITER initialization statement or CPS WRITER command, an unknown keyword or abbreviation was specified.

System action: If the error was in an operator command, the command is not processed. If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly. If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0907I

START AND STOP ARE MUTUALLY EXCLUSIVE KEYWORDS


Explanation: In a CPS WRITER initialization statement or CPS WRITER command, both START and STOP were specified. Only one of these keywords is permitted.

System action: If the error was in an operator command, the command is not processed. If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly. If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0908I

CONSOLE nn IS NOT DEFINED


Explanation: In a CPS WRITER initialization statement or CPS WRITER command, the CONSOLE keyword was specified with an MVS console number that was not defined when the system was generated.

System action: If the error was in an operator command, the command is not processed. If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly. If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0909I

THE keyword KEYWORD HAS BEEN SPECIFIED MORE THAN ONCE


Explanation: In a CPS WRITER initialization statement or CPS WRITER command, the same keyword has been specified more than once.

System action: If the error was in an operator command, the command is not processed. If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly. If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0910I

THE keyword KEYWORD VALUE IS NOT NUMERIC: value


Explanation: In an MVL WRITER initialization statement or MVL WRITER command, a keyword that requires a numeric value has been entered with a non-numeric value.

System action: If the error was in an operator command, the command is not processed.If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly.If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the MVL WRITER initialization statement.

DTM0911I

THE keyword KEYWORD VALUE IS OUT OF RANGE: value


Explanation: In an MVL WRITER initialization statement or MVL WRITER command, a keyword that requires a numeric value was entered with a value that is too low or too high.

System action: If the error was in an operator command, the command is not processed.If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly.If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the MVL WRITER initialization statement.

DTM0913I

DEST, ADEST, AND RDEST ARE MUTUALLY EXCLUSIVE KEYWORDS


Explanation: In a CPS WRITER command, more than one of the DEST, ADEST, or RDEST keywords were entered. Only one of these keywords is permitted.

System action: The command is not processed.

Operator Response: Re-enter the command correctly.If you need to remove and add destination codes for a CPS Writer use the DEST keyword, or enter two commands, one with RDEST and the other with ADEST.

Programmer Response: None.

DTM0914I

INVALID DESTINATION: destination-name


Explanation: In a CPS WRITER initialization statement or CPS WRITER command, an invalid value was entered for one of its destinations.

System action: If the error was in an operator command, the command is not processed.If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly.If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0915I

TOO MANY DESTINATIONS SPECIFIED


Explanation: More than the maximum number of destinations was entered for a CPS WRITER initialization statement or CPS WRITER command.

System action: If the error was in an operator command, the command is not processed.If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly.If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0916I

DESTINATION ‘destination-name’ HAS BEEN SPECIFIED MORE THAN ONCE


Explanation: A destination has been specified more than once for a CPS WRITER initialization statement or CPS WRITER command.

System action: If the error was in an operator command, the command is not processed.If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly.If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0917I

INVALID SYNTAX IN THE keyword KEYWORD


Explanation: A syntax error was detected following a keyword for a CPS WRITER initialization statement or CPS WRITER command.

System action: If the error was in an operator command, the command is not processed.If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly.If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0918I

INVALID CONSOLE IDENTIFIER


Explanation: An invalid console UCM identifier or console name was specified in the CONSOLE keyword of the CPS WRITER initialization statement or CPS WRITER command.

System action: If the error was in an operator command, the command is not processed.If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly.If the error was in an initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0920I

DUPLICATE CPS WRITER NAME: writer-name


Explanation: In a CPS WRITER initialization statement, the CPS Writer name is the same as one specified on an earlier CPS WRITER statement.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statements.

DTM0921I

PVFFLAG AND PVFAUTOREL ARE MUTUALLY EXCLUSIVE KEYWORDS
*** Version 3 Mode Only ***


Explanation: Both the PVFFLAG and PVFAUTOREL keywords were included on the same CPS WRITER initialization statement or CPS WRITER operator command.

System action: If the error was in an operator command, the command is not processed.If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly.If the error was in a TMSS initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0922I

PVFFLAG AND PVFNONE ARE MUTUALLY EXCLUSIVE KEYWORDS
*** Version 3 Mode Only ***


Explanation: Both the PVFFLAG and PVFNONE keywords were included on the same CPS WRITER initialization statement or CPS WRITER operator command.

System action: If the error was in an operator command, the command is not processed.If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly.If the error was in a TMSS initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0923I

PVFAUTOREL AND PVFNONE ARE MUTUALLY EXCLUSIVE KEYWORDS
*** Version 3 Mode Only ***


Explanation: Both the PVFAUTOREL and PVFNONE keywords were included on the same CPS WRITER initialization statement or CPS WRITER operator command.

System action: If the error was in an operator command, the command is not processed.If the error was in an initialization statement, TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: If the error was in an operator command, re-enter the command correctly.If the error was in a TMSS initialization statement, notify personnel responsible for support.

Programmer Response: Correct the CPS WRITER initialization statement.

DTM0930I

SPOOL PROCESSOR IS NOT AVAILABLE


Explanation: A command cannot be completed because the SPOOL processor has terminated.

System action: Processing of the command is terminated.

Operator Response: None.

Programmer Response: None.

DTM0931I

CPS WRITER CHANGE FAILED; CPS SPOOL CONTROL RECORD DAMAGED


Explanation: The SPOOL processor detected damage to the CPS Spool File Control Record while processing a command.

System action: Processing of the command is terminated.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the error.

DTM0932I

CPS WRITER ‘writer-name’ IS NOT DEFINED


Explanation: A command has been entered for a CPS writer that is not defined.

System action: Processing of the command is terminated.

Operator Response: Re-enter the command correctly.

Programmer Response: None.

DTM0933I

CPS WRITER CHANGE FAILED; TOO MANY DESTINATIONS DEFINED


Explanation: A command has been entered to give new destinations to a CPS Writer. The addition of these destinations would have caused the number of defined destinations to exceed 128, the maximum number allowed.

System action: Processing of the command is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM0934I

CPS WRITER CHANGE FAILED; NO SPACE IN CPS SPOOL CONTROL RECORD


Explanation: A CPS WRITER command has been entered with the DATA keyword or with new destinations for a CPS Writer. The addition of these destinations or the user exit data would have caused the CPS SPOOL File Control Record to exceed its maximum size.

System action: Processing of the command is terminated.

Operator Response: Notify personnel responsible for support.

Programmer Response: Reduce the number of destinations.

DTM0935I

CPS WRITER ‘writer-name’ DOES NOT HAVE THE SPECIFIED DESTINATION


Explanation: A command has been entered with the RDEST keyword to remove destinations from a CPS Writer. At least one of the specified destinations is not currently assigned to this CPS Writer.

System action: Processing of the command is terminated.

Operator Response: Re-enter the command correctly.

Programmer Response: None.

DTM0940I

CPS WRITER writer-name
SYSTEM: sys subsys                STATUS: status
CONSOLE:                                   cn
ROUTE CODE:                              rt
PAGE LENGTH:                            pl
TOP MARGIN:                             tm
BOTTOM MARGIN:                     bm
PACING FACTOR:                        nnnnn
EXIT DATA:                                  ‘exit data’
DESTINATION(S):                        dest dest dest dest
                                                   dest dest dest dest


Explanation:
sys: is SMF system identifier of the system on which the TMSS that owns this CPS Writer is running.
subsys: is subsystem name of the JES2 under which the TMSS that owns this CPS Writer is running.
status: is one of the following:

  • DRAINED indicates that the CPS Writer has been stopped using the CPS WRITER command with the STOP keyword.
  • T MSS INACTIVE indicates that the TMSS that owns this CPS Writer is not active.
  • CONSOLE OFFLINE indicates that this CPS Writer routes Volume Lists to a specific MVS console, but that console is unavailable.
  • AVAILABLE indicates that this CPS Writer is available to write Volume Lists.
  • EXTENDED ROUTE CODE N/A indicates that the TMSS for the CPS Writer is executing on a pre MVS/XA 2.2 system. Extended route codes are not valid.

cn: is the MVS console number or the ESA console name to which Volume Lists are written.
rt: is the MVS route code to which Volume Lists are written if the console number is zero.
pl: is the page length of Volume Lists produced by this CPS Writer.
tm: is the number of blank lines that are written at the top of each Volume List page produced by this
CPS Writer.
bm: is the number of blank lines that are written at the bottom of each Volume List page produced by
this CPS Writer.
nnnnn: is the pacing factor for this CPS Writer. This should be the average number of milliseconds
required for the physical Volume List printer to print one line of a Volume List.
exit data: is a string of 0 to 32 characters of user exit data supplied by the DATA keyword of the CPS
WRITER command.
dest: is a destination that is assigned to this CPS Writer. As many lines are displayed as necessary to list
all of the destinations for this CPS Writer.

This message is issued in response to the CPS DISPLAY WRITER command for a specific CPS Writer.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0941I

CPS WRITER STATUS
WRITER      SYSTEM      SUBSYSTEM       STATUS
wname       sys               subsys                status


Explanation:
wname: is the name of the CPS Writer being displayed.
sys: is SMF system identifier of the system on which the TMSS that owns this CPS Writer is running.
subsys: is subsystem name of the JES2 under which the TMSS that owns this CPS Writer is running.
status: is one of the following:

  • DRAINED indicates that the Writer has been stopped using the CPS WRITER command with the DRAIN keyword.
  • TMSS INACTIVE indicates that the TMSS that owns this CPS Writer is not active.
  • CONSOLE OFFLINE indicates that this CPS Writer routes JVLs and CVLs to a specific MVS console, but that console is unavailable.
  • AVAILABLE indicates that this CPS Writer is available to write JVLs or CVLs.
  • EXTENDED ROUTE CODE N/A Indicates that the TMSS for the CPS Writer is executing on a pre MVS/XA 2.2 system. Extended route codes are not valid.

A CPS DISPLAY WRITER command has been entered without an CPS Writer name, indicating that a summary display of all CPS Writers is required. The last line is repeated once for each CPS Writer.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM0947I

MVL WRITER DEFINITIONS NOT SUPPORTED IN JSS V4 MODE (USE CPS)


Explanation: An MVL WRITER statement was encountered, but JSS is running in Version 4 mode.

System action: TMSS initialization fails with a return code of 4.

Operator Response: Notify personnel responsible for support.

Programmer Response: Convert MVL WRITER statements to CPS WRITER statements.

DTM0948I

CPS WRITER DEFINITIONS NOT SUPPORTED IN JSS V3 MODE (USE MVL)


Explanation: A CPS WRITER statement was encountered, but JSS is running in Version 3 mode.

System action: TMSS initialization fails with a return code of 4.

Operator Response: Notify personnel responsible for support.

Programmer Response: Convert CPS WRITER statements to MVL WRITER statements.

DTM0949I

THERE ARE NO CPS WRITERS DEFINED


Explanation: A CPS DISPLAY WRITER command was entered, but there are no CPS Writers defined.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM1000I

JOB jobname HAS CAUSED AN ERROR IN THE JOB ANALYZER, AND WILL BE HELD


Explanation: This message is issued when a job causes an error in the Job Analyzer.

System action: The job is requeued for execution in the same ThruPut Manager Job Analysis Class in which it was being processed, but it is held.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the error.

DTM1101I

[procname] stepname ddname[+nnn] - INVALID PARAMETERS SPECIFIED FOR JOBCAT OR STEPCAT


Explanation: A JCL parameter was specified on a JOBCAT or STEPCAT DD statement that would have been valid on another DD statement, but cannot be specified for a private catalog:

  • SYSOUT, *, DATA, QNAME, or DUMMY.
  • NEW, MOD, PASS, CATLG, DELETE, or UNCATLG in the DISP parameter.
  • AFF, DEFER, or a unit name subparameter in the UNIT parameter.
  • SER or REF in the VOLUME parameter.
  • A relative generation number in the DSNAME parameter.

This would cause message IEF493I to be issued at execution time.

System action: The job is failed with a JCL error after JCL Analysis is complete.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM1102I

[procname] stepname - PGM=*.DD - REFERENCED STEP WILL NOT BE EXECUTED, OR DATASET TYPE INVALID


Explanation: In an EXEC statement, the PGM parameter refers to a DD statement in a previous step of the job. One of the following has occurred:

• The referenced DD statement is in a step that will never be executed because it precedes the step named in the RESTART parameter on the JOB statement.
• The referenced DD statement specified a data set that is not direct access or VIO. Instead, it specified a subsystem data set (SYSOUT, DD *, etc.), a DUMMY data set, or a UNIT type that includes no direct access devices.

This would cause message IEF221I to be issued at execution time.

System action: The job is failed with a JCL error after JCL Analysis is complete.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM1103I

[procname] stepname ddname[+nnn] - GDG GROUP NAME EXCEEDS 35 CHARACTERS


Explanation: In a DD statement, the DSNAME parameter contained a relative generation number, but the GDG group name (the part of the data set name preceding the generation number) was longer than 35 characters, making it impossible to retrieve the full data set name from the catalog.

This would cause message IEF219I to be issued at execution time.

System action: The job is failed with a JCL error after JCL Analysis is complete.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM1104I

[procname] stepname ddname[+nnn] - RELATIVE GENERATION NUMBER CONTAINS SYNTAX ERROR


Explanation: In a DD statement, the DSNAME parameter contained a relative generation number with invalid syntax. A valid generation number is no more than 4 characters long, is all numeric (except for a leading sign), must have a sign if it is not zero, and is not less than -255 or greater than +255.

This would cause message IEF366I to be issued at execution time.

System action: The job is failed with a JCL error after JCL Analysis is complete.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM1105I

[procname] stepname ddname[+nnn] - VOLUME FIELD REFERENCES STEP THAT WILL NOT BE EXECUTED


Explanation: In a DD statement, the REF subparameter of the VOLUME parameter refers to a DD statement in a previous step of the job. The referenced DD statement is in a step that will never be executed because it precedes the step named in the RESTART parameter on the JOB statement.
This would cause message IEF372I to be issued at execution time.

System action: The job is failed with a JCL error after JCL Analysis is complete.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM1106I

[procname] stepname ddname[+nnn] - ‘UNIT=AFF’ INVALID FOR NEW DASD DATASET


Explanation: In a DD statement, DISP=NEW is specified (or assumed by default) and one of the following has occurred:

  • UNIT=AFF is specified.
  • The REF subparameter of the VOLUME parameter refers to a DD statement in the same step, in which UNIT=AFF was specified.

In addition, the DD statement referenced by the UNIT=AFF parameter specifies a unit name that includes only direct access devices”.

This would cause message IEF318I to be issued at execution time.

System action: The job is failed with a JCL error after JCL Analysis is complete.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM1107I

[procname] stepname ddname[+nnn] - UNIT FIELD SPECIFIES INCORRECT DEVICE NAME - devnam


Explanation: In a DD statement, the unit name subparameter devnam in the UNIT parameter was not defined when the system was generated. This would cause message IEF210I to be issued at execution time.

System action: The job is failed with a JCL error after JCL Analysis is complete.

Operator Response: None.

Programmer Response: Correct and rerun. Installations using DASD poolers should consider using the TM UNIT initialization statement. See the System Programming Guide: Base Product for details.

DTM1108I

[procname] stepname ddname[+nnn] - NO UNIT SPECIFIED AND TM ‘DEFAULT’ NOT AVAILABLE


Explanation: In a DD statement, DISP=NEW was specified (or assumed by default), but no unit type was supplied. A unit type can be supplied by the unit name or the AFF subparameter of the UNIT parameter, or by the REF subparameter of the VOLUME parameter. This would cause message IEF210I to be issued at execution time.

System action: The job is failed with a JCL error after JCL Analysis is complete.

Operator Response: None.

Programmer Response: Correct and rerun. This error can be avoided by setting a default with the TM UNIT SET initialization statement or the TM UNIT SET operator command.

DTM1109I

[procname] stepname ddname[+nnn] - VOLUME SEQUENCE NUMBER EXCEEDS NUMBER OF VOLUME SERIALS


Explanation: In a DD statement, in the VOLUME parameter the volume sequence number subparameter was specified and the SER subparameter was specified with one or more volume serial numbers. The volume sequence number was greater than the number of volume serial numbers. This would cause message IEF194I to be issued at execution time.

System action: The job is failed with a JCL error after JCL Analysis is complete.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM1110I

[procname] stepname ddname[+nnn] - MAXIMUM NUMBER OF DEVICES FOR DD EXCEEDED


Explanation: In a DD statement, P was specified in the unit count subparameter of the UNIT parameter, requesting enough units to mount all the volumes of the data set, and one of the following has occurred:

  • the volume count subparameter of the VOLUME parameter was specified and its value is greater than 59.
  • the SER subparameter of the VOLUME parameter was specified with more than 59 volume serial numbers.

This would cause message IEF195I to be issued at execution time.

System action: The job is failed with a JCL error after JCL Analysis is complete.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM1111I

[procname] stepname ddname[+nnn] - DISP FIELD INCOMPATIBLE WITH DSNAME


Explanation: In a DD statement, a relative generation number was specified and its value was zero or negative, indicating that an existing generation of a GDG is to be retrieved. DISP=NEW was also specified or assumed by default. This would cause message IEF286I to be issued at execution time.

System action: The job is failed with a JCL error after JCL Analysis is complete.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM1112I

jobname [procname] stepname ddname[+nnn] - CATALOG ERROR DURING LOCATE RC=return-code RS=reason-code FOR dsname


Explanation: A serious error discovered by MVS Catalog Management prevented a catalog search from being completed. Catalog damage is the likely cause of this error. See to message IDC3009I in the IBM Message Library: System Messages. Other system messages might also result from the condition causing this error.

System action: Processing of this job is suspended immediately and the job is requeued and held in the JES2 class from which it was selected.

Operator Response: Notify personnel responsible for support. When the catalog damage has been diagnosed and corrected, this job can be released to be reprocessed.

Programmer Response: See message IDC3009I in the IBM Message Library: System Messages. Check also for previous messages indicating the nature of the error.

DTM1113I

[procname] stepname ddname[+nnn] - VOLUME volser NOT FOUND


Explanation: The Job Analyzer encountered a DASD volume that is supposed to be ONLINE but it was not found.

System action: The job is failed with a JCL error after JCL Analysis is completed.

Operator Response: None.

Programmer Response: None.

DTM1114I 

[procname] stepname ddname[+nnn] - VOLUME volser HAS BEEN ‘RETIRED’


Explanation: The Job Analyzer encountered a DASD volume that is supposed to be ONLINE but it has been flagged as ‘RETIRED’.

System action: The job is failed with a JCL error after JCL Analysis is completed.

Operator Response: None.

Programmer Response: None.

DTM1115I

[procname] stepname ddname[+nnn] - DSN REFERENCED WITHIN SCOPE OF JOBCAT/STEPCAT


Explanation: An SMS-managed data set has been referenced in a step in the scope of either a JOBCAT or STEPCAT. This would cause message IGD04002I to be issued at execution time.

System action: The job is failed with a JCL error after JCL Analysis is complete.

Operator Response: None.

Programmer Response: See to the explanation of message IGD04002I in the IBM Message Library: System Messages.

DTM1116I

jobname [procname] stepname ddname[+nnn] - UNABLE TO ACCESS LOCKED CATALOG catalog FOR dsname


Explanation: During Job Analysis, a catalog request issued to obtain information for the specified data set failed because the catalog was locked.

System action: The job is requeued to the Job Analysis class and it is held.

Operator Response: Notify personnel responsible for support. When the catalog has been unlocked, the job will be released automatically.

Programmer Response: Use IDCAMS to UNLOCK the catalog.

DTM1117I

dd - UNABLE TO ALTER SYSOUT ATTRIBUTES, nnn OUTPUT REFERENCES


Explanation: During Job Analysis, the maximum number of output references was reached for the named DD statement.

System action: SOS DAL for the job is bypassed.

Operator Response: None.

Programmer Response: Reduce the number of references.

DTM1118I

JES3 JECL ignored due to 'INPUTDEF JES3JECL=PROCESS'


Explanation: JES3 JECL statements were detected when the JES2 INPUTDEF option is set to JES3JECL=PROCESS.

System action: ThruPut Manager will ignore the JES3 JECL statements.

Operator Response: None.

Programmer Response: To allow ThruPut Manager to process the JES3 JECL statements issue '$TINPUTDEF,JES3JECL=IGNORE'.

DTM1151I

CATALOG dsname IS ON VOLUME volser WHICH IS NOT AVAILABLE


Explanation: The Job Analyzer encountered a catalog in a DASD volume that is supposed to be ONLINE but has been flagged as ‘NOT AVAILABLE’.

System action: The job is failed with a JCL error after JCL Analysis is completed.

Operator Response: None.

Programmer Response: None.

DTM1152I

CATALOG dsname IS ON VOLUME volser WHICH HAS BEEN RETIRED


Explanation: The Job Analyzer encountered a catalog in a DASD volume that is supposed to be ONLINE but has been flagged as ‘RETIRED’.

System action: The job is failed with a JCL error after JCL Analysis is completed.

Operator Response: None.

Programmer Response: None.

DTM1153I

CATALOG MANAGEMENT NOT RESPONDING, CATALOG BEING SEARCHED IS name ON VOLUME volser


Explanation: ThruPut Manager is waiting for a response from catalog management. This warning message is issued up to four times within the timeout period.

System action: Job analysis continues until four warnings have been issued. After the fourth warning, analysis of the job is aborted. See DTM1154I.

Operator Response: Determine why catalog management is not responding. Check for a reserve on the catalog volume that has been issued from another system.

Programmer Response: None.

DTM1154I

CATALOG MANAGEMENT NOT RESPONDING, ANALYSIS OF JOB jobname
REQUEUED FOR ANALYSIS, PRIORITY prio


Explanation: The timeout period set by TM CATALOG SET has expired. Analysis of the job has been terminated because ThruPut Manager cannot obtain catalog information. The name and volume serial number of the unavailable catalog are shown in the previously issued DTM1153I messages.

System action: The job is requeued in the ThruPut Manager Analysis Class with the indicated priority.

Operator Response: If necessary, correct the problem as documented in the previously issued DTM1153I messages.

Programmer Response: None.

DTM1155I

TM CATALOG OPTIONS
TIMEOUT RQ_PRIORITY
       time                  prio


Explanation:
time: is the number of minutes before the job is terminated and requeued, or DISABLED, indicating that NO_TIMEOUT has been specified by TM CATALOG SET.
prio: is the priority at which the job is requeued to the Job Analysis Class, or N/A, indicating that NO_TIMEOUT has been specified by TM CATALOG SET.

This message is issued in response to a TM CATALOG command.

System action: Processing continues, using the values as displayed.

Operator Response: None.

Programmer Response: None.

DTM1156I


Explanation: This is an internal diagnostic message.

DTM1157I


Explanation: This is an internal diagnostic message.

DTM1250I

JOB ‘jobname’ - held to prevent looping


Explanation: A job has been placed in MHS_TM hold because it would otherwise be requeued to the Job Analysis Class or the class in which it was just analyzed. This would cause the job to be selected again and again by the Analyzer creating an endless loop.

System action: The job is placed in MHS_TM hold.

Operator Response: Notify personnel responsible for support.

Programmer Response: Examine JAL to determine why the class is not set properly.

DTM1251I

CAPACITY EXCEEDED

summary display of area usage


Explanation: The area available to store JECL and JAL/DAL requests has been exceeded. The job probably contains a large number of JECL statements. Review the summary displayed indicating the ThruPut Manager components that store information in this area and the number of JECL and JAL/DAL requests. Two different types of information are displayed, depending on which limits are exceeded.

An example of one of the types:JBS JECL JAL/DAL BIND 1 2 ACTIVATE 0 0 DEACTIVATE 0 0 MESSAGE 0 0 JLS JECL JAL/DAL LIMIT 0 4 JCS JECL JAL/DAL AFTER 0 0 BATCH 0 1 BEFORE 0 0 JTS JECL JAL/DAL RELEASE 0 4 DCS JECL JAL/DAL DCS 0 51 OTH JECL JAL/DAL INTERNAL 0 0 An example of the other type: 49 JECL STATEMENTS 0 OTHER COMPONENTS 100 INFORM CHANGE CHARACTERS 0 INFORM DISPLAY CHARACTERS 41 INFORM DATA CHARACTERS

System action: The job is failed and queued for JES2 output processing.

Operator Response: None

Programmer Response: Review the situation to see the cause of the problem. It is likely that there are an excessive number of JECL statements in the job or too many JAL/DAL requests were made. For example, DCS SERVICE requests for too many individual data sets. Correct the situation and rerun the job.

DTM1252I

Job name - attempted to requeue to type Job Class x
or
Job name - unable to requeue to type Job Class x,
using DEFAULT(y)


Explanation:
type: is Production_Services, General_Services or On_Demand
x: is the “attempted” requeue SLM jobclass
y: is the DEFAULT class

The job has been placed in TM hold because JAL assigned a job class that is being managed by SLM, but did not specify that the job is SLM-managed.

System action: Requeues the job in the Primary Analysis class and places it in MHS hold.

Operator Response: None.

Programmer Response: Correct the JAL.

DTM1253I

JOB jobname - held due to unknown SLM Control Center ‘cc’ Type ‘type’, reason


Explanation:
jobname: is the name of the job
cc: is the SLM Control Center specified
type: is the SLM Type specified
reason: is text explaining why the SLM Control Center and Type is not valid
Note: A Control Center and Type form a Service Group. For example, if Control Center is PROD and Type is ACCOUNT, the Service Group would be PROD ACCOUNT.

System action: The job is requeued to the Analysis Class and held.

Operator Response: None.

Programmer Response: None.

DTM1254I

JOB jobname - held due to undefined SLM type Job Class


Explanation:
type: can be one of:

  • Production_Services
  • General_Services

This message is issued when a job is requeued to a SLM jobclass and that class (Production_Services or General_Services) has not been defined.

System action: The job is requeued to the analysis class and MHS held.

Operator Response: None.

Programmer Response: None.

DTM1255I

Job jobname — held due to invalid requeue class x
or
Job jobname — held because of attempt to requeue to
type class which is set to NONE
or
Job jobname — attempted to use type services but Job
Class is set to NONE


Explanation:
jobname: is the name of affected job.
x: requeue jobclass
type: is Production_Services, General_Services or ON_DEMAND

The job has been requeued to a jobclass that is not valid or to an ON_DEMAND class which is set to NONE.

System action: The job is requeued to the analysis class and MHS_TM hold is applied.

Operator Response: When the problem has been corrected, all affected jobs can be released by using the ThruPut Manager command “MHS_TM RELEASE JOBS BAD_CLASS”.

Programmer Response: In the case of an invalid requeue class, either correct the JAL to specify a valid class or define the class to JES2 using JES2 command “$ADDJOBCLASS(x)”. In the case of an SLM class set to NONE, use ThruPut Manager command “TM CLASS SET” to set the indicated SLM class.

DTM1256I

JOB jobname - Held due to undefined DBS Installation Pool x


Explanation:
x: DBS Installation Pool name
The job has been assigned a DBS Installation Pool which is not defined.

System action: Requeues the job in the Primary Analysis class and places the job in MHS hold.

Operator Response: None.

Programmer Response: Correct the JAL.

DTM1257I

Job name - undefined Production Profile(name)


Explanation: This message is when a non-Scheduled PCS job is assigned to a PCS PRODUCTION PROFILE that does not exist.

System action: The job is assigned to the default PROFILE group.

Operator Response: None.

Programmer Response: None.

DTM1259I

Job name - unable to verify Production Service Group (name), defaults used.


Explanation: This message is when a Production_Services job is assigned to a Production Service Group and SLM is currently not active, thus the profile can not be validated.

System action: The job is assigned to the default Production Services Group.

Operator Response: None.

Programmer Response: None.

DTM1260I

*MAIN CLASS=’classname’ is not a valid Job Class -
Class ignored
or
using DEFAULT Class


Explanation: This message is issued when a job has a JES3 *MAIN statement with a CLASS= parameter and the CLASS is not recognized as a valid class. The CLASS cannot be used since it is not a valid class.

System action: The job will be processed normally but JES3 support will ignore the CLASS= parameter.

Operator Response: When the problem has been corrected, all affected jobs can be released by using the ThruPut Manager command “MHS_TM RELEASE JOBS BAD_CLASS”.

Programmer Response: Determine if the CLASS was supposed to be valid.

DTM1353I

UNABLE TO WRITE JVL FOR JOB jobname BECAUSE SPOOL PROCESSOR HAS TERMINATED


Explanation: The Job Analyzer attempted to write a JVL for a job. It was unable to do so because the SPOOL processor has terminated, and has not been restarted, or the operator has denied TMSS permission to restart it. The operator can produce a JVL by using the JVL REGENERATE command when the SPOOL processor has been restarted.

System action: Writing of a JVL is bypassed and Job Analyzer processing continues.

Operator Response: None.

Programmer Response: None.

DTM1354I

JOB ANALYSIS FOR JOB jobname CANCELLED BY OPERATOR


Explanation: The Job Analyzer attempted to write a JVL for a job. It was unable to do so because of reasons indicated in previous messages from the SPOOL processor, and the operator replied CANCEL to one of those messages.

System action: The Job Analyzer terminates with a system 222 abend. The job being processed is requeued for Job Analyzer processing. The initiator is drained.

Operator Response: Restart the initiator when you are ready to resume Job Analyzer processing.

Programmer Response: None.

DTM1355I

UNABLE TO WRITE JVL FOR JOB jobname BECAUSE CPS WRITER TASK HAS TERMINATED


Explanation: The Job Analyzer attempted to write a JVL for a job. It was unable to do so because the CPS Writer task has terminated.

System action: Writing of a JVL is bypassed and Job Analyzer processing continues.

Operator Response: Notify personnel responsible for support. You can produce a JVL by issuing the JVL REGENERATE command, after TMSS the CPS Writer task has been restarted.

Programmer Response: See previous messages indicating the nature of the error.

DTM1356I

CPS WRITER TASK ABENDED WHILE PROCESSING REQUEST FOR JOB jobname


Explanation: The Job Analyzer attempted to write a JVL for a job. The CPS Writer task abended while processing this JVL request.

System action: Writing of a JVL is bypassed and Job Analyzer processing continues.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the error.

DTM1357I

UNABLE TO SPOOL JVL FOR JOB jobname BECAUSE OF CPS SPOOL CONTROL RECORD DAMAGE


Explanation: The Job Analyzer attempted to write a JVL for a job. It was unable to do so because the SPOOL processor was terminating due to damage in the CPS SPOOL File Control Record.

System action: Writing of a JVL is bypassed and Job Analyzer processing continues.

Operator Response: You can produce a JVL by issuing the JVL REGENERATE command, after the SPOOL processor has been restarted.

Programmer Response: See previous messages indicating the nature of the error.

DTM1450I

Unable to requeue Job jobname, component-name Services Unavailable


Explanation: This message is issued when a Job Analyzer attempts to requeue a job but the named component is unavailable (e.g., has abended).

System action: Issues message DTM1451A requesting operator intervention.

Operator Response: See message DTM1451A.

Programmer Response: None.

DTM1451A

Reply ‘RETRY’ to retry, or ‘STOP’ to terminate this Job Analyzer


Explanation: This message is issued together with message DTM1450I and requires an operator response.

System action: Waits for a valid reply.

Operator Response: If the reply is ‘RETRY’, the requeue is retried. If the reply is ‘STOP’, the Job Analyzer terminates and the job is requeued for Job Analyzer processing.

Programmer Response: None.

DTM1452I

Requeue for jobname, not acknowledged by component-name


Explanation: This message is issued when a job is requeued by a Job Analyzer, but the named component did not respond within the defined time.

System action: Issues message DTM1453A requesting operator intervention.

Operator Response: See message DTM1453A.

Programmer Response: None.

DTM1453A

Reply ‘RETRY’ to retry, or ‘STOP’ to terminate this Job Analyzer


Explanation: This message is issued together with message DTM1452I and requires an operator response.

System action: Waits for a valid reply.

Operator Response: If the operator replies ‘RETRY’, the Job Analyzer tries the requeue again. If the operator replies ‘STOP’, the Job Analyzer terminates, and the job is requeued for Job Analyzer processing.

Programmer Response: None.

DTM1454I

ERROR OCCURRED DURING REQUEUE OF jobname


Explanation: JES2 indicated that there was an error in the requeue of a job.

System action: The Job Analyzer terminates with a system 222 abend. The job being processed is requeued for Job Analyzer processing.

Operator Response: Notify personnel responsible for support. If errors persist for this job, hold it or bypass ThruPut Manager processing.

Programmer Response: See previous messages indicating the nature of the error.

DTM1455I

yyyy.ddd hh:mm:ss [JAL-label] JOB jobname failed, reason [sched-environment]


Explanation: A job has been failed by the Job Analyzer.
JAL-label: is a 1- to 20-character string specified by the SET LABEL statement in JAL.
reason: indicates why the job has failed, and can be one of:

  • JCL ERROR: A JCL error was found that would have prevented successful execution of the job.
  • JOB ACTION LANGUAGE Stmt# nnn: Your JAL requested that the job be failed. It appended with JAL statement number to indicate where the EXIT FAIL/FLUSH or RETURN FAIL/FLUSH exists.
  • DETAIL ACTION LANGUAGE Stmt# nnn: Your DAL requested that the job be failed. It appended with DAL statement number to indicate where the EXIT FAIL/FLUSH or RETURN FAIL/FLUSH exists.
  • INSTALLATION EXIT: One of your installation exits requested that the job be failed.
  • INVALID REQ CLASS: Attempting to requeue the job to an invalid class.
  • INVALID AFFINITY: SET SYSAFF(xx) where xx is not defined as a JES2 system.
  • JECL ERROR: Syntax error processing a TM JECL statement. Note that while you might not have coded any JECL statements in your job, your installation might have “inserted” JECL statements for your job in JAL.
  • BAD SCHENV: The scheduling environment name from a JAL SET statement is invalid and is displayed.

System action: The job is failed and queued for output processing by JES2.

Operator Response: None.

Programmer Response: None.

DTM1456I

TYPRUN=SCAN processing completed


Explanation: This message is a confirmation that ThruPut Manager has completed TYPRUN=SCAN processing for a job.

System action: The job is queued for output.

Operator Response: None.

Programmer Response: None.

DTM1457I

Unable to communicate with pcs (ca7id). reason


Explanation: During the analysis of a PCS job, an error occurred while attempting to communicate with the PCS control region.
reason: indicates why communication has failed. It can be one of:

  • SLM IS DISABLED
  • TMSS NOT AVAILABLE
  • UNABLE TO REACH SLM SERVER
  • UNABLE TO REACH PCS CONTROL REGION
  • CODE=X’nnnnnnnn’

System action: The job will be requeued and processed using default timing information.

Operator Response: If communication failed with CODE=X’nnnnnnnn’, contact a System Programmer responsible for the support.

Programmer Response: If communication failed with CODE=X’nnnnnnnn’, contact MVS Solution support.

DTM1458I

yyyy.ddd hh:mm:ss JOB jobname requeued TO class="c"


Explanation: The job was requeued using defaults.

System action: The job is requeued for execution in the indicated class.

Operator Response: None.

Programmer Response: None.

DTM1459I

Job jobname requeued to CLASS x
or
Job jobname requeued for analysis HELD
or
Job jobname requeued for Deferred Analysis x HELD


Explanation:
x: jobclass
The job was requeued to default, analysis or deferred class. If the job is held, this is indicated also.

System action: The job was requeued to an execution class, the primary analysis class or a deferred analysis class.

Operator Response: None.

Programmer Response: None.

DTM1460I

Job jobname requeued to class x [HELD]
or
Job jobname requeued for Analysis HELD
or
Job jobname requeued for Deferred Analysis ‘x’ HELD


Explanation:
x: jobclass. The job was requeued to an execution class, the primary analysis class or a deferred analysis class. If the job is held, this is indicated also.

System action: The job is requeued for execution.

Operator Response: None.

Programmer Response: None.

DTM1461I

[JAL-label] JOB jobname FAILED, reason


Explanation: A job has been failed by the ThruPut Manager Job Analyzer.
JAL-label: is a 1-20 character string specified by the SET LABEL statement in JAL.
reason: indicates why the job has failed, and can be one of:


    • JCL ERROR: A JCL error was found that would have prevented successful execution of the job.
    • JOB ACTION LANGUAGE Stmt# nnn: Your JAL requested that the job be failed. It appended with JAL statement number to indicate where the EXIT FAIL/FLUSH or RETURN FAIL/FLUSH exists.
    • DETAIL ACTION LANGUAGE Stmt# nnn: Your DAL requested that the job be failed. It appended with DAL statement number to indicate where the EXIT FAIL/FLUSH or RETURN FAIL/FLUSH exists.
    • FAILED BY SOFTWARE ACCESS CONTROL: Conditions specified in the SAC table caused the job to fail.
    • INSTALLATION EXIT: One of your installation exits requested that the job be failed.
    • INVALID REQ CLASS: Attempting to requeue the job to an invalid class.
    • INVALID AFFINITY: SET SYSAFF(xx) where xx is not defined as a JES2 system.
    • JECL ERROR: Syntax error processing a TM JECL statement. Note that while you might not have coded any JECL statements in your job, your installation might have “inserted” JECL statements for your job in JAL.

System action: The job is failed and queued for output processing by JES2.

Operator Response: None.

Programmer Response: None.

DTM1462I

Job jobname held because of reason


Explanation:
reason: can be one of the following:

  • UNAVAILABLE VOLUMES
  • CATALOG ERROR
  • UNAVAILABLE CATALOG
  • DAL/JAL PROCESSING ERROR

System action: The job is requeued to the job analysis class, and it is held.

Operator Response: For an unavailable volume situation, this message is preceded by message DTM1466I showing the volume or volumes required by the job. If the job is held for unavailable resources (volumes or catalog), it is released automatically when the resource becomes available. For other circumstances, release the job with an operator command when the problem has been corrected.
If the error occurred during DAL/JAL Processing, do not release the job. Notify personnel responsible for support.

Programmer Response: For DAL/JAL errors, see if there are any other previous error messages indicating the reasons for the problem. If you cannot determine the cause of the problem, refresh the DAL/JAL and release the job. If the problem persists, contact BMC Support personnel.

DTM1463I

Job jobname cancelled during job analysis


Explanation: The job was cancelled by the operator or JES2 during Job Analyzer processing. This message appears both in the job’s system messages data set and on the operator’s console.

System action: The job is failed and queued for output.

Operator Response: None.

Programmer Response: None.

DTM1464I

Job jobname requires n Tape Recalls. JAL|SLM Limit is m


Explanation:
n: the number of TAPE recalls for the specified job.
m: the number of TAPE recalls allowed by JAL or the SLM Policy.

A job requires more TAPE recalls than has been allowed by the JAL “JSS RECALL LIMIT” keyword or by the maximum number of TAPE recalls allowed in the SLM Policy.

System action: The number of recalls is reduced to the specified limit. Any recalls that are required over the limit will be performed at step initiation.

Operator Response: None.

Programmer Response: None.

DTM1465I

[JAL-label] Job jobname requeued back to Job Analyzer, TM-HELD


Explanation: The operator responded ‘HOLD’ to DTM3800A message. The named job was being processed by the Job Analyzer when the error occurred. A Control File related function could not be performed.

System action: The job is placed in TM-HOLD. The next time a Control File reconciliation takes place, the job will be released.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the error and take corrective action. The Application can be restarted with the ‘TM OPT ENABLE option-name’ command. This causes the Control File Manager to request a reconciliation, which in turn will trigger the release of the job.

DTM1466I

[procname] stepname ddname [+nnn] Volume volser Required by Job jobname is Unavailable


Explanation: The volume indicated in the message text by volser is unavailable. This message is repeated for each unavailable volume required by the job.

System action: The job is requeued back to ‘AWAITING EXECUTION’ and is held by MHS_VOL.

Operator Response: When the volume or volumes become available the job should be released with a MHS_VOL RELEASE command.

Programmer Response: Determine why the volume or volumes are unavailable. This situation occurs when the drive where the volume is mounted is offline, or the volume has been added to the ThruPut Manager volume list with the ‘VOLUME ADD’ command.

DTM1467I

Job Profile Capture Processing Complete


Explanation: A capture of the job profile was requested with the ThruPut Manager JECL statement /*TM PROFILE CAPTURE. This message confirms that capture processing completed successfully.

System action: The job is queued for output.

Operator Response: None.

Programmer Response: None.

DTM1468I

Reverting To PCS Monitor Mode - reason


Explanation: The job is only to be monitored by PCS for the reasons described below.
reason: is one of the following:


    • INVALID SLM-PCS CLASS – SLM-PCS class has not been defined
    • SLM DISABLED – SLM is not currently available to process the job

System action: None.

Operator Response: None.

Programmer Response: None.

DTM1510I

UNABLE TO CAPTURE JOB PROFILE DUE TO ENQ ERROR.
ENQ RC=return-code


Explanation: The resources required to capture the job’s profile could not be serialized. The ENQ was attempted three times at intervals of two seconds. return-code is the result of the last ENQ attempt.

System action: The job is queued for output.

Operator Response: None.

Programmer Response: Determine the reason for the ENQ failure and correct.

DTM1511I

UNABLE TO CAPTURE JOB PROFILE DUE TO UNAVAILABLE RESOURCES


Explanation: The resources required to capture the job’s profile could not be obtained.

System action: The job is failed.

Operator Response: None.

Programmer Response: Re-run the job. This was probably caused by two simultaneous capture attempts.

DTM1512I

UNABLE TO CAPTURE JOB PROFILE. JOB PROFILE MEMORY IS FULL.


Explanation: The memory allocated for job profiles has been filled. No more job profiles can be captured until memory becomes available.

System action: The job is failed.

Operator Response: None.

Programmer Response: Use the JAL Test Facility to remove some captured jobs and free job profile memory.

DTM1513I

UNABLE TO CAPTURE JOB PROFILE DUE TO control-block GETMAIN ERROR. RC=return-code


Explanation: A GETMAIN error occurred while attempting to obtain storage for control-block.

System action: The job is failed.

Operator Response: None.

Programmer Response: Determine why the GETMAIN failed.

DTM1514I

UNABLE TO CAPTURE JOB PROFILE. JOB PROFILE CAPTURE QUEUE IS FULL.


Explanation: The queue holding job profiles has been filled. No more job profiles can be captured until jobs are removed from the queue.

System action: The job is failed.

Operator Response: None.

Programmer Response: Use the JAL Test Facility to remove some captured jobs and free queue entries.

DTM1521I

SMF RECORD NUMBER TO BE USED NOT PROVIDED VIA TM EXIT 09 CONTROL STATEMENT


Explanation: The SMF record number was not specified with the DATA keyword of the TM EXIT 09 control statement. This message is issued once for each job analyzed.

System action: Job Analyzer performance monitoring is not initiated.

Operator Response: Notify personnel responsible for support.

Programmer Response: Add the SMF record number in the DATA parameter of the TM EXIT 09 control statement, then re-start TMSS.

DTM1522I

INVALID SYNTAX FOR SMF RECORD NUMBER TO BE USED.
SPECIFY DATA(SMF=nnn) ON TM EXIT 09 CONTROL STATEMENT


Explanation: There was a syntax error in the specification of the SMF record number to be used. This message will be issued once for each job analyzed.

System action: Job Analyzer performance monitoring is not initiated.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the SMF record number in the DATA parameter of the TM EXIT 09 initialization statement, then re-start TMSS.

DTM1523I

INVALID SMF RECORD NUMBER PROVIDED ON TM EXIT 09 CONTROL STATEMENT

SPECIFY A NUMERIC IN THE RANGE 128 THRU 255


Explanation: The SMF record number specified was not a valid user SMF record. This message will be issued once for each job analyzed.

System action: Job Analyzer performance monitoring is not initiated.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the SMF record number in the DATA parameter of the TM EXIT 09 control statement, then re-start TMSS.

DTM1524I

SMF RECORDING FOR RECORD NUMBER nnn IS NOT ACTIVE


Explanation: The SMF record number specified on the TM SMF initialization statement is not being recorded. This message is issued once for each job analyzed.

System action: Job Analyzer performance monitoring is not initiated.Operator Response: Notify personnel responsible for support.

Programmer Response: Change the SMF record number in the TM SMF initialization statement to one that is being recorded, then re-start TMSS. Alternately, modify the SMF options to record the specified number.
If SMF data is being collected by the Job Analyzer, this message is produced for every job that is analyzed. Until the problem is corrected, you can turn off attempts by the Job Analyzer to record SMF data by issuing a TM SMF DISABLE ANALYZER operator command.

DTM1525I

CURRENT LEVEL OF Thruput Manager DOES NOT SUPPORT PERFORMANCE MONITOR


Explanation: Performance monitoring is not supported by versions of ThruPut Manager earlier than Version 4 Release 1. This message will be issued once for each job analyzed.

System action: Job Analyzer performance monitoring is not initiated.

Operator Response: Notify personnel responsible for support.

Programmer Response: Upgrade ThruPut Manager to at least Version 4 Release 1, or do not attempt performance monitoring.

DTM1526I

INVALID SYNTAX FOR SMF TABLE DATA. SPECIFY DATA(‘SMF=nnn[,t[,s...s]]’) ON TM EXIT 09 CONTROL STATEMENT


Explanation: The DATA keyword on the TM EXIT 09 statement has been specified incorrectly.

System action: None of the requested SMF data is written.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the erroneous TM EXIT statement.

DTM1527I

SMF TABLE DATA NOT FOUND. ENSURE TABLE IS LOADED AND ENABLED, VERIFY SUB-TABLE NAME.


Explanation: The table specifying the data to be added to the SMF record cannot be found.

System action: None of the requested SMF data is written.

Operator Response: Notify personnel responsible for support.

Programmer Response: Check to make sure the table has been loaded and that the subtable name on the TM SMF initialization statement is correct.

This message is produced for every job that is analyzed. Until the problem is corrected, you can turn off attempts by the Job Analyzer to record SMF data by issuing a TM SMF DISABLE ANALYZER operator command.

DTM1528I

AT LEAST ONE SMF DATA FIELD IN THE SPECIFIED FIELD IS INVALID. VERIFY TABLE CONTENTS.


Explanation: One of the fields in the table specifying the data to be added to the SMF record is incorrect.

System action: The invalid SMF data is not written.

Operator Response: Notify personnel responsible for support.

Programmer Response: Verify that all entries in the table specify valid Descriptor names.
This message is produced for every job that is analyzed. Until the problem is corrected, you can turn off attempts by the Job Analyzer to record SMF data by issuing a TM SMF DISABLE ANALYZER operator command.

DTM1529I

TM SMF RECORDING IS NOT ENABLED

or

TM SMF RECORD TYPE nnn

PRODUCED        STATUS        FURTHER

       BY                                INFORMATION

function                           status                information


Explanation:

nnn: Is the SMF record type specified by the TM SMF initialization statement.

function: Is the ThruPut Manager function that is producing the SMF record, and is one of:

  • ANALYZER
  • DCS

status: Indicates whether SMF recording for the named function is active, and is one of:

  • DISABLED
  • ENABLED

information: Is any additional information available from the ThruPut Manager function.

This message is issued in response to a TM SMF DISPLAY operator command.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM1530I

JOB ANALYZER SMF RECORDING SELECTED. DUPLICATE SMF RECORDS WILL BE GENERATED.


Explanation: The TM SMF initialization statement has requested SMF recording by the Job Analyzer, but SMF data collection is also active in ThruPut Manager User Exit 9.

System action: Duplicate SMF records are written.

Operator Response: Notify personnel responsible for support.
This message is produced once for every job analyzed. To stop duplicate records from being written until the problem is corrected, either issue the TM SMF DISABLE ANALYZER command or disable Exit 9 with the TM EXIT command.

Programmer Response: Remove the SMF data collection function from User Exit 9.

DTM1531I

TM CPU NORMALIZATION IS NOT ENABLED ON THIS SYSTEM

or

TM FACTOR DISPLAY

     NORMALIZATION

FACTOR      VALUE

n                   ff.ff


Explanation:

n: Is a digit from the range 1-8, identifying the set of normalizing factors.

ff.ff: Is a factor, where 00.00 < ff.ff < 99.99.

This message is issued in response to the TM FACTOR command.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM1900I

ERRONEOUS INVOCATION OF DTMSYSMI
RETURN ADDR=X’hhhhhhh’, ACB ADDR=X’hhhhhhhh’


Explanation: The intercept routine to suppress messages has been invoked even though we have not activated it.

System action: The message is discarded.

Operator Response: Notify personnel responsible for support.

Programmer Response: Using the return address provided in the message, determine the routine calling DTMSYSMI. Contact the vendor responsible for the module.

DTM2000I


Explanation: This is an internal diagnostic message.

DTM2001I


Explanation: This is an internal diagnostic message.

DTM2002I


Explanation: This is an internal diagnostic message.

DTM2003I


Explanation: This is an internal diagnostic message.

DTM2004I


Explanation: This is an internal diagnostic message.

DTM2006I


Explanation: This is an internal diagnostic message.

DTM2007I


Explanation: This is an internal diagnostic message.

DTM2050I


Explanation: This is an internal diagnostic message.

DTM2051I


Explanation: This is an internal diagnostic message.

DTM2052I


Explanation: This is an internal diagnostic message.

DTM2053I


Explanation: This is an internal diagnostic message.

DTM2100I


Explanation: This is an internal diagnostic message.

DTM2101I


Explanation: This is an internal diagnostic message.

DTM2102I


Explanation: This is an internal diagnostic message.

DTM2103I


Explanation: This is an internal diagnostic message.

DTM2104I


Explanation: This is an internal diagnostic message.

DTM2105I


Explanation: This is an internal diagnostic message.

DTM2106I


Explanation: This is an internal diagnostic message.

DTM2107I


Explanation: This is an internal diagnostic message.

DTM2108I


Explanation: This is an internal diagnostic message.

DTM2110I


Explanation: This is an internal diagnostic message.

DTM2111I


Explanation: This is an internal diagnostic message.

DTM2112I

Thruput Manager MODULE module-name IS NOT CORRECTLY INSTALLED


Explanation: This module must be fetched from a Link List library. The ThruPut Manager module was installed in the MVS Link Pack Area (LPA, MLPA, or FLPA), or the module could not be obtained from the Link List libraries.

System action: The Job Analyzer abends with U2112 and an SVC dump with the title ‘ThruPut Manager DTMOMX08 ABEND U2112’.

Operator Response: Notify personnel responsible for support.

Programmer Response: Install the module correctly.

DTM2113I


Explanation: This is an internal diagnostic message.

DTM2114I


Explanation: This is an internal diagnostic message.

DTM2222I


Explanation: This is an internal diagnostic message.

DTM2224I

ThruPut Manager VERSION ver RELEASE rel PTF ptfno


Explanation: During startup, ThruPut Manager displays this message to space the version, release, and PTF levels.

System action: Initialization continues.

Operator Response: None.

Programmer Response: None.

DTM2225I

ThruPut Manager ANALYSIS CLASS - class


Explanation: During initialization, ThruPut Manager has determined that the listed class is to be used for Job Analysis.

System action: Initialization continues.

Operator Response: None.

Programmer Response: None.

DTM2226I

ThruPut Manager DEFERRED CLASSES - class-list


Explanation: During initialization, ThruPut Manager has determined that the listed classes are to be used to defer jobs for later Job Analysis.

System action: Initialization continues.

Operator Response: None.

Programmer Response: None.

DTM2227I

ThruPut Manager SELECT CLASSES - class-list


Explanation: During initialization, ThruPut Manager has determined that jobs submitted in the listed classes are to be selected for Job Analysis.

System action: Initialization continues.

Operator Response: None.

Programmer Response: None.

DTM2228I

NO ThruPut Manager DEFERRED CLASSES SPECIFIED


Explanation: ThruPut Manager initialization did not find any classes specified for Deferred Analysis.

System action: Initialization continues.

Operator Response: None.

Programmer Response: None.

DTM2229I

NO ThruPut Manager SELECT CLASSES SPECIFIED


Explanation: ThruPut Manager initialization did not find any classes specified from which to select jobs for Job Analysis.

System action: Initialization continues.

Operator Response: None.

Programmer Response: None.

DTM2230I

JOB WILL BE CONVERTED AND ANALYZED ON - smf-id


Explanation: The AFFINITY keyword of the TMPARM statement has specified that jobs will be converted and analyzed on the identified system.

System action: Initialization continues.

Operator Response: None.

Programmer Response: None.

DTM2232I

CPU NORMALIZATION FACTOR n: nn.nn


Explanation:
n: Identifies the set of factors,
nn.nn: Is the factor that was applied.
This message spaces the normalization factor specified by the FACTORn keyword of TMPARM.

System action: Initialization continues.

Operator Response: None.

Programmer Response: None.

DTM2233I

CPU NORMALIZATION INACTIVE


Explanation: ThruPut Manager initialization did not find a CPU normalization factor.

System action: Initialization continues.

Operator Response: None.

Programmer Response: None.

DTM2234I

COMMUNICATIONS CHARACTER - char


Explanation: The character char was specified as the character which must be used as the initial character in a ThruPut Manager command. If no communications character is specified, this is indicated by the word NONE.

System action: Uses the specified character to recognize ThruPut Manager commands.

Operator Response: Start ThruPut Manager commands with char. For NONE, use the MVS MODIFY command interface.

Programmer Response: None.

DTM2235I

OPTION option INSTALLED, status


Explanation:
option: is a ThruPut Manager component, and can be one of:

  • ACF2
  • DCS
  • DJC
  • JBS
  • JCS
  • JTS
  • JLS
  • MELLON
  • MHS
  • RSS
  • UHS

status: is the current status of the component, and can be either ENABLED or DISABLED.
The specified ThruPut Manager component is installed, and has been given the specified status as a result of processing the TMPARM initialization statement.

System action: Initialization continues.

Operator Response: Check components for correct status.

Programmer Response: If the status is not as desired, correct the TMPARM initialization statement.

DTM2236I

EXPECTED END OF COMMENT NOT FOUND


Explanation: During initialization, ThruPut Manager encountered the characters ‘/*’ beginning a comment, but did not find the characters ‘*/’ ending the comment.

System action: Message DTM2261A is issued.

Operator Response: See DTM2261A. Notify personnel responsible for support.

Programmer Response: Correct the comment.

DTM2237I

DUPLICATE ThruPut Manager INITIALIZATION STATEMENTS ENCOUNTERED. THE LAST
STATEMENT WILL BE PROCESSED.


Explanation: During initialization, ThruPut Manager found more than one JES2 initialization statement TMPARM.

System action: ThruPut Manager processes the last TMPARM statement encountered and ignores previous TMPARM statements.

Operator Response: Notify personnel responsible for support.

Programmer Response: Remove any duplicate TMPARM statements.

DTM2238I

NO ThruPut Manager INITIALIZATION HAS BEEN DETECTED


Explanation: ThruPut Manager did not find a TMPARM JES2 initialization statement.

System action: Message DTM2261A is issued.

Operator Response: See message DTM2261A.

Programmer Response: None.

DTM2239I

ThruPut Manager DISABLED BY OPERATOR


Explanation: The operator replied ‘DISABLE’ in response to DTM2261A or DTM2262A.

System action: All ThruPut Manager functions are disabled. ThruPut Manager continues in Emergency Bypass Mode.

Operator Response: None.

Programmer Response: None.

DTM2240I

type CLASS(ES) IGNORED. ALREADY DEFINED. CLASS - class-list


Explanation:
type: can be either DEFERRED, SELECT, or EXEMPT. The listed classes have already been defined.

System action: ThruPut Manager ignores the attempted re-definition and continues initialization.

Operator Response: Notify personnel responsible for support.

Programmer Response: Remove the conflicting definitions.

DTM2241I

JOBS REQUESTING /*SETUP WILL BE PROCESSED


Explanation: This message indicates that jobs requesting /*SETUP services will be processed by ThruPut Manager.

System action: Initialization continues.

Operator Response: None.

Programmer Response: None.

DTM2242I

JOBS REQUESTING TYPRUN=SCAN WILL BE PROCESSED


Explanation: This message indicates that jobs requesting TYPRUN=SCAN will be processed by ThruPut Manager.

System action: Initialization continues.

Operator Response: None.

Programmer Response: None.

DTM2243I

JOBS REQUESTING TYPRUN=HOLD WILL BE PROCESSED


Explanation: This message indicates that jobs requesting TYPRUN=HOLD will be processed by ThruPut Manager.

System action: Initialization continues.

Operator Response: None

Programmer Response: None.

DTM2244I

REQUIRED JES2 EXIT (nn) DOES NOT REFERENCE MODULE DTMJ2Xnn


Explanation: The JES2 EXIT control statement for exit point nn does not refer to the required ThruPut Manager JES2 module.

System action: The JES2 ThruPut Manager initialization process enters Emergency Bypass Mode (EBM).

Operator Response: Notify personnel responsible for support.

Programmer Response: Include the ThruPut Manager module in the JES2 EXIT statement.

DTM2245I

REQUIRED JES2 EXIT (nn) IS DISABLED, ThruPut Manager MAY MALFUNCTION


Explanation: The JES2 EXIT control statement for exit point nn specifies DISABLE. ThruPut Manager needs this exit point to be enabled.

System action: The JES2 ThruPut Manager initialization process enters Emergency Bypass Mode (EBM).

Operator Response: Notify personnel responsible for support.

Programmer Response: Enable exit point.

DTM2247I

ADD$EXIT routine failure


Explanation: An unexpected error occurred when attempting to dynamically add ThruPut Manager's JES2 exits.

System action: ThruPut Manager stops its dynamic exit processing.

Operator Response: Notify personnel responsible for ThruPut Manager support.

Programmer Response: Contact ThruPut Manager support. If you have all ThruPut Manager exits specified in your JES2 initialization deck, ThruPut Manager will continue to operate without issue. Otherwise, unexpected behavior is possible depending on where the error occurred, as some ThruPut Manager exits may be missing.

DTM2247A

ThruPut Manager MUST BE IN Z/OS MODE PRIOR TO STARTING JES2 AT THE Z/OS V1R2 LEVEL. ENTER THE $MJ,ZOS COMMAND ON AN OLDER VERSION OF JES2


Explanation: JES2 initialization has failed because the conversion to TM z/OS has not yet been performed or not all the systems in the JESplex are running TM V5 R2.

System action: JES2 is not started.

Operator Response: Notify personnel responsible for support.

Programmer Response: Run the command $MJ,ZOS,CHECK to ensure all systems in the JESplex are z/OS READY and perform the conversion.

DTM2248E

**WARNING** CLASS HAS CHANGED. ANALYSIS CLASS IS NOW ‘class’


Explanation: During startup, ThruPut Manager encountered a value for the ANALYSIS keyword of the TMPARM initialization statement that did not match the value in the JES2 checkpoint.

System action: The Analysis Class is set to the value from the JES2 checkpoint and startup continues.

Operator Response: Notify personnel responsible for support.

Programmer Response: Change the TMPARM statement so that the ANALYSIS keyword matches the value on other JES2 systems in the JESplex.

DTM2250I

ERROR IN ThruPut Manager INITIALIZATION STATEMENT - text


Explanation: During initialization, ThruPut Manager encountered an error in an initialization statement.

System action: Message DTM2261A is issued.

Operator Response: See DTM2261A. Notify personnel responsible for support.

Programmer Response: Correct the initialization statement.

DTM2251I

ERROR DETECTED IN ‘keyword’ KEYWORD - text


Explanation: During initialization, ThruPut Manager has encountered an error in a keyword of the JES2 initialization statement TMPARM.

System action: If the error can be corrected, ThruPut Manager issues DTM2260A. If the error cannot be corrected, message DTM2261A is issued.

Operator Response: Notify personnel responsible for support. See DTM2260A or DTM2261A.

Programmer Response: Correct the keyword in error.

DTM2260A

SPECIFY ‘keyword’ VALUE OR ‘LIST’ FOR EMERGENCY OPTIONS


Explanation: During ThruPut Manager initialization, a correctable error was detected in a keyword.

System action: ThruPut Manager waits for an operator response.

Operator Response: Notify personnel responsible for support. To correct the error and attempt to continue initialization, enter the correct value for the keyword in error. To abort initialization and get a list of emergency options, enter ‘LIST’.

Programmer Response: Correct the keyword in error.

DTM2261A

SPECIFY ‘DEFAULTS’ TO REQUEST ThruPut Manager DEFAULTS
SPECIFY ‘DISABLE’ TO DISABLE ThruPut Manager
SPECIFY ‘ABEND’ TO ABEND JES2


Explanation: During ThruPut Manager initialization, errors have been detected in the JES2 initialization statement TMPARM, or no TMPARM statement was found.

System action: Message DTM2263A is issued, asking for an operator response.

Operator Response: Enter ‘DEFAULTS’ to continue initialization using ThruPut Manager defaults. Message DTM2264A is issued.

Enter ‘DISABLE’ to enter Emergency Bypass Mode. Messages DTM2239I and DTM2280I are issued.

Enter ‘ABEND’ to cause a JES2 abend. JES2 prompts for termination options. Message DTM0666E is issued.

Programmer Response: None.

DTM2262A

SPECIFY ‘DISABLE’ TO DISABLE ThruPut Manager
SPECIFY ‘ABEND’ TO ABEND JES2


Explanation: The operator has responded ‘LIST’ to message DTM2260A.

System action: Message DTM2263A is issued, asking for an operator response.

Operator Response: Enter ‘DISABLE’ to enter Emergency Bypass Mode. ThruPut Manager issues messages DTM2239I and DTM2280I, then enters Emergency Bypass Mode.
Enter ‘ABEND’ to cause a JES2 abend. ThruPut Manager causes the JES2 main task to abend, and JES2 prompts for termination options. Message DTM0666E is issued.

Programmer Response: None.

DTM2263A

SPECIFY ONE OF THE OPTIONS LISTED ABOVE


Explanation: This message follows any of the messages DTM2261A, DTM2262A, or DTM2264A.

System action: ThruPut Manager waits for an operator response.

Operator Response: See the previous DTM2261A, DTM2262A, or DTM2264A message.

Programmer Response: None.

DTM2264A

SPECIFY ‘NONE’ TO EXEMPT ALL CLASSES FROM PROCESSING

SPECIFY ‘ALL’ TO SELECT ALL CLASSES FOR PROCESSING


Explanation: The operator has responded ‘DEFAULTS’ to message DTM2261A. ThruPut Manager offers the opportunity to select all classes for Job Analysis, or not to select any classes.

System action: Message DTM2263A is issued, asking for an operator response.

Operator Response: Enter ‘ALL’ to have all classes selected for Job Analysis.

Enter ‘NONE’ to select no classes for Job Analysis.

Programmer Response: None.

DTM2265I

REPLY SPECIFIED IS INVALID


Explanation: The response to the previous operator prompt was invalid.

System action: The prompt is re-issued.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM2270I

FOLLOWING INVALID KEYWORD IGNORED: text


Explanation: During initialization, text was encountered that could not be recognized as a valid keyword or comment.

System action: The text is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TMPARM statement.

DTM2280I

******************* WARNING WARNING **********************
*** ThruPut Manager ENTERING EMERGENCY BYPASS MODE ***
*** ALL FUNCTIONS WILL BE DISABLED DUE TO: ***
*** text-explaining-reason ***
******************************************************************


Explanation:
text: describes the reason Emergency Bypass Mode was entered.
The operator entered ‘DISABLE’ in response to DTM2261A, DTM2262A, or DTM2281A.

System action: All ThruPut Manager functions are disabled.

Operator Response: None.

Programmer Response: None.

DTM2281A

REPLY ‘ABEND’ TO ABEND JES2 OR ‘DISABLE’ TO ENTER EMERGENCY BYPASS MODE


Explanation: ThruPut Manager has detected an internal error.

System action: ThruPut Manager waits for an operator response.

Operator Response: Notify personnel responsible for support.
Enter ‘DISABLE’ to enter Emergency Bypass Mode.
Enter ‘ABEND’ to cause a JES2 abend. JES2 prompts for termination options.

Programmer Response: See previous DTM0666E message.

DTM2300I

ThruPut Manager MODULE module-name ABENDED


Explanation: An abend has occurred in the named module.

System action: After an SVC dump is taken, processing resumes.

Operator Response: Notify personnel responsible for support.

Programmer Response: Review installation process.

DTM2301I

ThruPut Manager USER EXIT exit-name ABENDED


Explanation: An abend has occurred in the named module.

System action: After an SVC dump is taken, processing resumes.

Operator Response: Notify personnel responsible for support.

Programmer Response: Review installation process.

DTM2302I

**WARNING** JES2 CONTROL BLOCKS ARE INCOMPATIBLE WITH ThruPut Manager
OFFSET TABLE


Explanation: The JES2 control blocks do not match the offset tables that were assembled during the ThruPut Manager install.

System action: The system issues message DTM2303I followed by DTM2304I with further details.

Operator Response: Notify personnel responsible for support.

Programmer Response: Review installation process.

DTM2303I

**WARNING** ENSURE THAT MODULE module-name WAS ASSEMBLED WITH THE CORRECT
JES2 MACRO LIBRARY


Explanation: This message follows DTM2302I, after the system has detected that the JES2 control blocks do not match the offset tables that were assembled during the ThruPut Manager install. This problem normally occurs for one of the following reasons:

  • The JES2 macro library used during the installation of ThruPut Manager does not reflect the level of maintenance of your JES2 running system.
  • You have added some maintenance to your JES2 system and have not reassembled the ThruPut Manager JES2 source modules.
  • You have a third party software product that updates JES2 control blocks and your installation of ThruPut Manager does not reflect the updates.
  • Your installation modifies JES2 control blocks and the macro library used to install ThruPut Manager does not reflect the modifications.

System action: The system issues message DTM2304I with further details.

Operator Response: Notify personnel responsible for support.

Programmer Response: Review installation process.

DTM2304I

JES2 control-block-name INVALID, RELEASE=VnRn.n JES2 PLVL/SLVL=nn/nn TM PLVL/SLVL=nn/nn, ASSEMBLED ON date AT time


Explanation: The acronym of the JES2 control block is displayed (e.g. HCT).

System action: The system issues message DTM2280I requesting Emergency Bypass Mode (EBM).

Operator Response: Notify personnel responsible for support.

Programmer Response: Review installation process. See if any JES2 maintenance or other product installs have taken place after the date and time specified.

DTM2305I

ThruPut Manager parameters missing or invalid,
correct then enter $T LOADMOD(DTMJ2MV6),REFRESH


Explanation: The default TMPARM statement in DTMJ2MV6 is invalid. The reason is that a ADD LOADMOD(DTMJ2MV6) command was entered and the default TMPARM statement within is invalid.

System action: The $ADD for DTMJ2MV6 will complete but ThruPut Manager will not initialize.

Operator Response: Enter $T LOADMOD(DTMJ2MV6),REFRESH command once the error has been corrected.

Programmer Response: Correct the TMPARM statement, reassemble and relink the module.

DTM2306I

MODULE DTMJ2SV6 is not in common storage, restart JES2 after correcting the LOAD statement


Explanation: DTMJ2SV6 was not loaded into common storage. Either the LOAD statement in the JES2 initialization parameters failed to specify CSA or LPA or a $ADD LOADMOD command was issued that did not specify STORAGE=CSA.

System action: Normal processing will continue.

Operator Response: Enter $DEL LOADMOD(DTMJ2SV6) and reenter the $ADD LAODMOD(DTMJ2SV6),STORAGE=CSA.

Programmer Response: Correct the LOAD statement and restart JES2.

DTM2310I

ThruPut Manager NOW IN Z/OS MODE


Explanation: The $MJ,ZOS command was entered and ThruPut Manager is converted to TM z/OS mode.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM2311I

ALL SYSTEMS MUST BE AT TTM5200 LEVEL. (JES2)


Explanation: The $MJ,ZOS,CHECK command was entered on a TM V5 R1 system.

System action: Processing continues.

Operator Response: Notify personnel responsible for support.

Programmer Response: Entering the command TM D LEVEL confirms the TM release in affect.

DTM2312I

ALREADY IN OS/390 MODE


Explanation: The command $MJ,OS/390 was entered however, the conversion has already been done.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM2313I

NOW IN OS/390 MODE


Explanation: The command $MJ,OS/390 was entered and ThruPut Manager is converted to TM OS/390 mode.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM2314I

ALREADY IN Z/OS MODE


Explanation: The $MJ,ZOS command was entered however, the conversion has already been done.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM2315I

Z/OS IS ACTIVE IN THIS JESPLEX


Explanation: The command $MJ,OS390 was entered on a z/OS JESplex system.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM2316I

JESplex-system-name(s) Z/OS READY


Explanation: A $MJ,ZOS,CHECK command was entered and verifies that all systems in the JESplex are z/OS READY.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM2317E

JESplex-system-name(s) NOT Z/OS READY


Explanation: A $MJ,ZOS,CHECK command was entered and verifies that all systems in the JESplex are NOT z/OS READY.

System action: Processing continues..

Operator Response: Notify support Personnel.

Programmer Response: Entering a TM D LEVEL command confirms the TM release in affect.

DTM2318I

Z/OS MODE CONVERSION WILL SUCCEED


Explanation: A $MJ,ZOS,CHECK command was entered and verifies that all systems in the JESplex are z/OS READY and the TM interface with JES2 is ready for conversion to z/OS with a $MJ,ZOS command.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM2320I

NO DEADLINE DATA FOUND


Explanation: In response to the $MJ,DEADLINE command, no data has been defined.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM2321I

DEADLINE ACTIVE, NEXT TIMER hh:mm


Explanation: In response to the $MJ,DEADLINE command, Deadline processing is active and the next timer will expire at hh:mm.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM2322I

DEADLINE=X,(prty1,time1,prty2,time2)


Explanation: In response to the $MJ,DEADLINE command, Deadline algorithm X has the listed values.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM2323I

JOB12345,NAME1234 AWAITING EXECUTION,HELD class="X",PRTY=XX,
DEADINE=(tttt,x,date)


Explanation: In response to the $MJ,DEADLINE command, the job is listed with Deadline characteristics.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM2330I

INVALID JOB NUMBER


Explanation: A $DMJnnnnnnn command was entered with a JES2 job number having more than 7 digits.

System action: The command is ignored.

Operator Response: Re-enter the command with a correct JES2 job number.

Programmer Response: None.

DTM2331I

INVALID SYNTAX


Explanation: A $DMJnnnnnnn command was entered with invalid syntax.

System action: The command is ignored.

Operator Response: Re-enter the command with a correct syntax.

Programmer Response: None.

DTM2332I

JOB NOT FOUND


Explanation: A $DMJnnnnnnn command was entered but the job could not be found.

System action: The command is ignored.

Operator Response: Re-enter the command specifying an existing job.

Programmer Response: None.

DTM2333I

BUFFER SHORTAGE


Explanation: A $DMJnnnnnnn command was entered but there was a shortage of memory in the JES2 address space.

System action: The command is ignored.

Operator Response: Re-enter the command later. If the condition persists, notify your systems programmer.

Programmer Response: If the problem persists, increase the JES2 region size.

DTM2334I

SPOOL CONTROL BLOCK ERROR


Explanation: A $DMJnnnnnnn command was entered but there was an error accessing the control block for the specified job.

System action: The command is ignored.

Operator Response: Re-enter the command later. If the condition persists, notify your systems programmer.

Programmer Response: Check the system log for spool I/O error messages.

DTM2335I

SYSTEM ERROR


Explanation: A $DMJnnnnnnn command was entered but there was an internal system error.

System action: The command is ignored.

Operator Response: Re-enter the command later. If the condition persists, notify your systems programmer.

Programmer Response: An error occurred while attempting to create a subtask to process the $LOGMSG service. Determine why the JES2 general subtask service is malfunctioning.

DTM2336E

COMMAND REJECTED, CANNOT SET AN SLM CLASS


Explanation: A $TJnnnnn command was entered with the C= operand and the new class was an SLM class, but changing a job to an SLM class is not allowed.

System action: None.

Operator Response: If the job is to be managed by SLM it must be resubmitted with the appropriate changes such that the analyzer reclasses it for SLM processing.

Programmer Response: None.

DTM2337E

COMMAND REJECTED, CANNOT CHANGE AN SLM CLASS


Explanation: A $TJnnnnn command was entered with the C= operand and the job was currently in an SLM class. Changing a job from an SLM class is not allowed unless the target class is an analysis class.

System action: None.

Operator Response: If the job is no longer to be managed by SLM, it must be resubmitted with the appropriate changes such that the analyzer reclasses it for non SLM processing.

Programmer Response: None.

DTM2338E

COMMAND REJECTED, USE JOB DEMAND COMMAND


Explanation: A $TJnnnnn command was entered with the C= operand and the new class was the ON_DEMAND class. Changing a job to the ON_DEMAND class is not allowed.

System action: None.

Operator Response: If the job is to be changed to the ON_DEMAND class, use the ThruPut Manager JOB command. The syntax is: /JOB DEMAND nnnnnnn or ‘name’.

Programmer Response: None.

DTM2339E

COMMAND FAILED, NO TMPARM STATEMENT FOUND


Explanation: A $MJ TMPARM command was entered pointing at a data set that does not contain a TMPARM statement. A TMPARM statement must exist for the command to be processed.

System action: None.

Operator Response: Reenter the $MJ TMPARM command pointing at the correct data set that contains a valid TMPARM statement.

Programmer Response: Edit the data set to contain a TMPARM statement.

DTM2340E

COMMAND FAILED, ALLOCATION OR OPEN ERROR


Explanation: A $MJ TMPARM command was entered and the data set failed to allocate or OPEN correctly. Most likely the data set name or member name was incorrectly entered.

System action: None.

Operator Response: Reenter the $MJ TMPARM command pointing at the correct data set and/or member.

Programmer Response: None.

DTM2341E

COMMAND FAILED, TMPARM INVALID


Explanation: A $MJ TMPARM command was entered and the TMPARM statement contains at least one error.

System action: None.

Operator Response: Reenter the $MJ TMPARM command pointing at the correct data set and/or member once the TMPARM statement has been corrected.

Programmer Response: Edit the data set to correct the TMPARM statement.

DTM2342I

TMPARM STATEMENT VALIDATION SUCCESSFUL


Explanation: A $MJ TMPARM command was entered with the CHECK keyword and the TMPARM contains no errors. The command will successfully apply the TMPARM changes if it is entered without the CHECK keyword.

System action: None.

Operator Response: Reenter the $MJ TMPARM command without the CHECK keyword if the changes are to be applied.

Programmer Response: None.

DTM2343E

COMMAND FAILED, INVALID PARAMETER


Explanation: A $MJ TMPARM command was entered with an unrecognized parameter following the data set name.The only valid parameter is the word CHECK which requests verification of the TMPARM without applying any changes at this time.

System action: None.

Operator Response: Reenter the $MJ TMPARM with either no additional parameters or with the CHECK parameter.

Programmer Response: None.

DTM2344E

- $TEXIT command
Disabling ThruPut Manager JES2 exits may have
catastrophic results, COMMAND REJECTED.
Use the FORCE keyword with caution.


Explanation: A $TEXIT command was entered attempting to disable one of ThruPut Manager JES2 Exits and the command has been rejected.

System action: None.

Operator Response: To really disable the Exit, the command can be entered again with the FORCE keyword appended. However, we strongly recommend against doing so.

Programmer Response: None.

DTM2345E

- $TEXIT command
**WARNING** Execution stopped on this system while
critical ThruPut Manager exits are disabled.


Explanation: A $TEXIT command was entered with the FORCE keyword to disable a critical ThruPut Manager JES2 Exit. As a result, the $PXEQ has been issued while any of Exit 08, Exit 14 or Exit 49 are disabled.

System action: None.

Operator Response: Re-enable the critical Exit(s). All of Exits 8, 14, 49 must be enabled for ThruPut Manager to function correctly.

Programmer Response: None.

DTM2346E

- $TEXIT command
**WARNING** Disabling ThruPut Manager JES2 exits
may cause unpredictable results.


Explanation: A $TEXIT command was entered with the FORCE keyword to disable one or more ThruPut Manager JES2 Exits. As a result, ThruPut Manager may not function correctly until the Exit(s) is/are re-enabled.

System action: None.

Operator Response: Re-enable the Exit(s). All of Exits 4,5,8,10,14,19,24,49,51 and 54 must be enabled for ThruPut Manager to function correctly.

Programmer Response: None.

DTM2347E

Class in use by ThruPut Manager: jobclass


Explanation:
jobclass: 8-character job class.
A $DEL command was entered with a JOBCLASS operand specifying a class currently in use by ThruPut Manager. A class presently being used by ThruPut Manager cannot be deleted.

System action: None.

Operator Response: None.

Programmer Response: The rejection can be defeated by temporarily disabling JES2 Exit 05.

DTM2348E

Command rejected, cannot start an SLM job


Explanation: A $SJnnnnn command was entered specifying an SLM job to be started. Starting a job in an SLM class is not allowed.

System action: None.

Operator Response: If the job must be started, use SLM START, or if allowable at the time issue a $PXEQ request to JES2 then issue a $SJnnnnn request to start the job.

Programmer Response: None.

DTM2349E

Block not found


Explanation: A $MJ,D{JQE=|CAT=|JCK|CTB=|JQT=|LIM=|DLN=} command is unable to locate the requested checkpoint block. A checkpoint block could not be found.

System action: None.

Operator Response: Check if a valid control block was requested..

Programmer Response: None.

DTM2350E

Job not found


Explanation: A $MJ,D{JQE=|JQT=} command is unable to locate the requested job. A job could not be found.

System action: None.

Operator Response: Check if a valid job id was requested.

Programmer Response: None.

DTM2351E

TMCT CTBL not found: x


Explanation:
x: indicates the expected position of the missing class table on the chain from the TMCT.
A $MJ,D{CAT=|CTB=} command is unable locate a class table chained from the TMCT.

A TM CAT or a CTBL is being displayed from the checkpoint and the corresponding TMCT anchored from the TMCT is missing.

System action: None.

Operator Response: Report the problem to the systems programmer that is responsible for support at your site.

Programmer Response: The checkpoint CTBL class tables must be synchronized with the CTBL class tables anchored from the TMCT. Contact the support team to report the problem.

DTM2352E

Empty class table


Explanation: A $MJ,D{CAT=|CTB=} command has accessed a CTBL class table from the checkpoint containing a length field of zero.

A TM CAT or a CTBL is being displayed from the checkpoint and the accessed class table contains a length field of zero.

System action: None.

Operator Response: Report the problem to the systems programmer that is responsible for support at your site.

Programmer Response: This is a validation check that should not be failing. Contact the support team to report the problem.

DTM2353E

TMCT CTBL mismatch at {+0000 x'00'|table end


Explanation: A TM CAT or a CTBL is being displayed from the checkpoint and the accessed class table is not equal to the corresponding CTBL class table chained from the TMCT.

A $MJ,D{CAT=|CTB=} command has accessed a CTBL class table from the checkpoint that is not equal to the corresponding CTBL class table chained from the TMCT.

"+0000" represents the offset into the class table of the first mismatched byte. "X'00'" is the contents of the first mismatched byte in the class table on the TMCT class table chain. "table end" if the class tables are not the same length, but equivalent for the length of the shorter table.

System action: None.

Operator Response: Report the problem to the systems programmer that is responsible for support at your site.

Programmer Response: Contact the support team to report the problem.

DTM2356I

$ACTIVATE rejected. ThruPut Manager requires nnnnnnn free BERTs, vvvvvvv available


Explanation: Operator has issued a $ACTIVATE,LEVEL=Z22 command while in z11 checkpoint mode. ThruPut Manager has determined that there are not enough free BERTs for ThruPut Manager to complete its processing required for the $ACTIVATE. ThruPut Manager requires approximately 1 extra BERT per job in the execution queues or executing when going from JES2 z11 checkpoint mode to z22 checkpoint mode. Before allowing a $ACTIVATE to continue, ThruPut Manager counts the jobs in the execution queues for all ThruPut Manager selectable job classes and adds 20% to determine the number of free BERTs required. On z/OS 2.3 and higher, it also allows for the number of BERTs reserved for the emergency subsystem.

In the message text:

nnnnnnn - The number of free BERTs required

vvvvvvv - The number of free BERTs available

System action: The $ACTIVATE command is not executed.

Operator Response: Report the problem to the systems programmer that is responsible for JES2 support at your site.

Programmer Response: Use $DCKPTSPACE to display the current number of free BERTs. Increase the number of BERTs or delete unwanted jobs (in any JES2 queue - not just execution).

DTM2550E

PID is invalid: ppp, expected to be a number in range 0-255


Explanation: Specified PID does not represent a valid number in range 0-255. ppp is the invalid specified value.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2551E

Module name is loo long: mmmm


Explanation: Specified modules name is too long, expected to not exceed 8 characters. mmm represents the specified module name.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2552E

Module name is not defined: mmmm


Explanation: Specified module name has no definition in the GTRACE definition table. Check the module name for correctness. mmmm represents the specified module name.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2553E

SID is invalid: sss, expected to be a number in range 0-255


Explanation: Specified SID does not represent a valid number in range 0-255. sss is the invalid specified value.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2554E

GTRACE was NOT initialized on this system.


Explanation: GTRACE has not been initialized by the time the ADS GTRACE command was issued.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2555E

GTRACE suppression table does not exist


Explanation: Although some GTRACE initialization occurred, it was not completed. Report this message to support.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2556I

GTRACE PID=ppp, SID=sss is SUPPRESSED
or
DTM2556I: GTRACE PID=ppp, SID=sss is NOT suppressed


Explanation: Displays the status of the GTRACE entry for a specific PID and SID based on the contents of the GTRACE suppression table. Note, that whether the suppression table is enabled or disabled is not taken into account when the status is displayed.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2557I

GTRACE PID=pp (mmm), SID=ss is SUPPRESSED
or
DTM2557I: GTRACE PID=pp (mmm), SID=ss is NOT suppressed


Explanation: Displays the status of the GTRACE entry for a specific PID (corresponding to the displayed module name) and SID based on the contents of the GTRACE suppression table. Note, that whether the suppression table is enabled or disabled is not taken into account when the status is displayed.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2558W

GTRACE PID=nn, SID=mm already was SUPPRESSED


Explanation: ADS GTRACE SUPTABLE ADD commands was issued for the specified PID and SID, but this GTRACE entry was already in the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2559W

GTRACE PID=ppp (mmmm), SID=sss already was SUPPRESSED


Explanation: ADS GTRACE SUPTABLE ADD commands was issued for the specified PID (corresponding to the displayed module name) and SID, but this GTRACE entry was already in the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2560I

GTRACE PID=ppp, SID=sss is now SUPPRESSED


Explanation: The GTRACE entry with the displayed PID and SID was successfully added to the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2561I

GTRACE PID=pp (mm), SID=ss is now SUPPRESSED


Explanation: The GTRACE entry with the displayed PID (corresponding to the displayed module name) and SID was successfully added to the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2562W

GTRACE PID=ppp, SID=sss already was NOT suppressed


Explanation: ADS GTRACE SUPTABLE REMOVE commands was issued for the specified PID and SID, but this GTRACE entry already was NOT in the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2563W

GTRACE PID=ppp (mmmm), SID=sss already was NOT suppressed


Explanation: ADS GTRACE SUPTABLE REMOVE commands was issued for the specified PID (corresponding to the displayed module name) and SID, but this GTRACE entry already was NOT in the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2564I

GTRACE PID=ppp, SID=sss is now NOT suppressed


Explanation: The GTRACE entry with the displayed PID and SID was successfully removed from the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2565I

GTRACE PID=p (m), SID=s is now NOT suppressed


Explanation: The GTRACE entry with the displayed PID (corresponding to the displayed module name) and SID was successfully removed from the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2566I

GTRACE PID=ppp has suppressed SIDs: xxxxx


Explanation: A list of SIDs that belong to the specified PID and exist in the suppression table are displayed. The list may contain individual SIDs separated by comma and/or SID ranges. For example:
1,3,10-19,127-128,130
Dots at the end of the list indicate that not all currently suppressed SIDs are displayed.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2567I

GTRACE PID=ppp (mmmm) has suppressed SIDs: xxxxxx


Explanation: A list of SIDs that belong to the specified PID (corresponding to the displayed module name) and exist in the suppression table are displayed. The list may contain individual SIDs separated by comma and/or SID ranges. For example:

1,3,10-19,127-128,130

Dots at the end of the list indicate that not all currently suppressed SIDs are displayed.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2568I

GTRACE PID=ppp has NO suppressed SIDs


Explanation: Specified PID has no SIDs defined in the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2569I

GTRACE PID=ppp (mmmm) has NO suppressed SIDs


Explanation: Specified PID (corresponding to the displayed module name) has no SIDs defined in the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2570I

GTRACE PID=ppp has ALL SIDs SUPPRESSED


Explanation: All SIDs for the specified PID are in the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2571I

GTRACE PID=ppp (mmmm) has ALL SIDs SUPPRESSED


Explanation: All SIDs for the specified PID (corresponding to the displayed module name) are in the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2572W

GTRACE PID=ppp already has ALL SIDs SUPPRESSED


Explanation: ADS GTRACE SUPTABLE ADD was issued for ALL SIDs of the specified module, however, all SIDs of this module are already in the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2573W

GTRACE PID=ppp (mmmm) already has ALL SIDs SUPPRESSED


Explanation: ADS GTRACE SUPTABLE ADD was issued for ALL SIDs of the specified module (the name of which is displayed in the message), however, all SIDs of this module are already in the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2574I

GTRACE PID=ppp has now ALL SIDs SUPPRESSED


Explanation: ALL SIDs for the specified PID were successfully added to the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2575I

GTRACE PID=pp (mm) has now ALL SIDs SUPPRESSED


Explanation: ALL SIDs for the specified PID (corresponding to the displayed module name) were successfully added to the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2576W

GTRACE PID=ppp already has NO SIDs suppressed


Explanation: ADS GTRACE SUPTABLE REMOVE commands was issued for ALL SIDs of the specified PID, however, no SIDs of this module exist in the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2577W

GTRACE PID=ppp (mmmm) already has NO SIDs suppressed


Explanation: ADS GTRACE SUPTABLE REMOVE commands was issued for ALL SIDs of the specified PID (corresponding to the displayed module name), however, no SIDs of this module exist in the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2578I

GTRACE PID=ppp has now NO SIDs suppressed


Explanation: ALL SIDs for the specified PID were successfully removed from the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2579I

GTRACE PID=pp (mm) has now NO SIDs suppressed


Explanation: ALL SIDs for the specified PID (corresponding to the displayed module name) were successfully removed from the suppression table.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2580I

GTRACE status: ssssssssss
Main Buffer size: mmm Mb
# of buffer wrap-ups: www
Moving edge at: ggg / 1000
Suppression Table: uuuuuuuuuu
FRR status: ffffffffff
# of reported errors: eee
V.1 code stopped: pppppppp


Explanation:
ssssssssss - is one of: ACTIVE | INACTIVE
mmm - is a size of the main trace buffer rounded to the nearest Mb
www - This number shows how many times the trace buffer has been wrapped up since its initialization
ggg - is a number between 0 and 1000 that shows position of the logical data edge in the trace buffer. As the buffer fills in, this number grows up to its maximum and then resets to zero when a wrap up occurs. Useful for making sure that the trace data is accumulating in the buffer
uuuuuuuuuu - is one of: ENABLED | DISABLED
ffffffffff - is one of: in USE | NOT used
eee - is a number of times an error in GTRACE occurred
pppppppp - is one of:
Yes - Old trace buffer is NOT used by the new code
No - Old trace buffer is USED by the new code
Pending - Old trace buffer is USED by the new code, but this is going to be stopped after
some time (automatically)

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2581I

GTRACE SUPPRESSION table is now ENABLED


Explanation: GTRACE suppression table was successfully enabled. All GTRACE entries added to this table will be suppressed (not logged in the main trace buffer).

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2582W

GTRACE SUPPRESSION table is already ENABLED


Explanation: ADS GTRACE SUPTABLE ENABLE command was issued, however, the suppression table has been already in the ENABLED state.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2583I

GTRACE SUPPRESSION table is now DISABLED


Explanation: GTRACE suppression table was successfully disabled. The table will be completely ignored and all GTARCE entries will be logged in the main trace buffer.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2584W

GTRACE SUPPRESSION table is already DISABLED


Explanation: ADS GTRACE SUPTABLE DISABLE command was issued, however, the suppression table has been already in the DISABLED state.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2585I

GTRACE is now ACTIVE


Explanation: GTRACE was successfully activated.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2586W

GTRACE is already ACTIVE


Explanation: ADS GTRACE ACTIVATE command was issued, however, GTRACE was already in the ACTIVE state.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2587I

GTRACE is now NOT active


Explanation: GTRACE was successfully deactivated.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2588W

GTRACE is already NOT active


Explanation: ADS GTRACE DEACTIVATE command was issued, however, GTRACE was already in the INACTIVE state.

System action: None.

Operator Response: None required.

Programmer Response: None required.

DTM2589E

GTRACE DISABLED DUE TO ERRORS


Explanation: An error occurred in the DTMG2TRC module. Due to GTRACE recovery area being not available, the details of the error are unknown.

System action: None.

Operator Response: Report this message to support.

Programmer Response: None required.

DTM2590E

GTRACE DISABLED DUE TO ERRORS '
DSECT DTMG2TRC 9999/99/99 hh:mm LOC AT aaaaaaaa
PSW pppppppp pppppppp ABEND Ssss/Uuuu
GPR 0-1 xxxxxxxx_xxxxxxxx xxxxxxxx_xxxxxxxx
GPR 2-3 xxxxxxxx_xxxxxxxx xxxxxxxx_xxxxxxxx
GPR 4-5 xxxxxxxx_xxxxxxxx xxxxxxxx_xxxxxxxx
GPR 6-7 xxxxxxxx_xxxxxxxx xxxxxxxx_xxxxxxxx
GPR 8-9 xxxxxxxx_xxxxxxxx xxxxxxxx_xxxxxxxx
GPR 10-11 xxxxxxxx_xxxxxxxx xxxxxxxx_xxxxxxxx
GPR 12-13 xxxxxxxx_xxxxxxxx xxxxxxxx_xxxxxxxx
GPR 14-15 xxxxxxxx_xxxxxxxx xxxxxxxx_xxxxxxxx


Explanation: An error occurred in the DTMG2TRC module. The details of the error are reported in the message.

System action: None.

Operator Response: Report this message to support.

Programmer Response: None required.

DTM2591E

ERROR ALLOCATING STORAGE, DTMG2INI FAILS.


Explanation: An error occurred during initialization of GTRACE (version 2). The code was unable to obtain working storage from the subpool 230. GTRACE initialization failed.

System action: None.

Operator Response: Report this message to support.

Programmer Response: None required.

DTM2592E

ERROR DURING GETCOMMON REQUEST, GTRACE IS DISABLED.


Explanation: An error occurred during initialization of GTRACE (version 2). The code was unable to allocate a common 64-bit object. GTRACE initialization failed.

System action: None.

Operator Response: Report this message to support.

Programmer Response: None required.

DTM2593E

ERROR ALLOCATING STORAGE, GTRACE RECOVERY AREA.


Explanation: An error occurred during initialization of GTRACE (version 2). The code was unable to allocate a recovery area. GTRACE initialization continues.

System action: None.

Operator Response: Report this message to support.

Programmer Response: None required.

DTM2700E

MODULE module-name DISABLED DUE TO ERRORS


Explanation: A module which has been abending has exceeded its error threshold.

System action: The module is marked disabled and no further attempts are made to reinstate it.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the problem.

DTM2701I

ABEND abend-code OCCURRED WHILE MODULE module WAS IN CONTROL


Explanation: One of the ThruPut Manager system exit routines has abended.

S ystem Action: Processing continues, but one or more of the exit’s functions might not have been performed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Collect diagnostic material (register contents, SVC dump) and call BMC Support.

DTM2725I


Explanation:  This is an internal diagnostic message.

DTM2726I

LEVEL Vn Rn.n OF DTMPRTNn IS INCOMPATIBLE WITH Vn Rn.n SOFTWARE


Explanation: This is likely to be the result of a software installation error.

System action: The initialization process will attempt to enter Emergency Bypass Mode (EBM).

Operator Response: Notify personnel responsible for support.

Programmer Response: Review the installation process.

DTM3150I


Explanation: This is an internal diagnostic message.

DTM3151I


Explanation: This is an internal diagnostic message.

DTM3152I


Explanation: This is an internal diagnostic message.

DTM3200I

INVALID RETURN CODE, X’rc’ FROM ThruPut Manager INSTALLATION EXIT nn


Explanation: An installation exit has returned an invalid return code upon completion of its processing. The return code value returned by the installation exit in register 15 is not one of 0, 4, 8, or 12.

System action: The ThruPut Manager component detecting the error terminates with a User 3200 Abend code. This results in an SVC Dump being taken.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the installation exit causing the error.

DTM3225I

INVALID KEYWORD: keyword


Explanation: TMSS could not recognize a keyword for the entered command.

System action: Command processing is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3226I

INVALID VOLSER: volser


Explanation: The volume serial number entered is not valid.

System action: Command processing is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3227I

INVALID ‘keyword’ KEYWORD SYNTAX


Explanation: A command was entered which did not have the correct syntax for keyword.

System action: Command processing is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3228I

MUTUALLY EXCLUSIVE KEYWORDS SPECIFIED


Explanation: At least two of the keywords for the entered ThruPut Manager command are mutually exclusive.

System action: Command processing is terminated.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3229I

REQUIRED KEYWORD MISSING


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

Programmer Response: None.

DTM3230I

INVALID CLASS: class


Explanation: A TM CLASS command was entered, but the indicated class is not valid in the context in which it was entered.

System action: The command is not processed.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3231I

UNABLE TO SERIALIZE ‘TM’ ‘CLASS TABLE’ RESOURCE


Explanation: A TM CLASS command was entered, but could not be processed because the resource needed was in use.

System action: The command is not processed.

Operator Response: Try again later.

Programmer Response: None.

DTM3232I

type CLASS ‘class’ CANNOT BE action


Explanation: A TM CLASS command was entered requesting a change to a class which cannot be altered.

System action: The command is not processed.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3233I

TM CLASS LIST
Analysis analysis-class
Deferred deferred-class list
Selectable select-class list
Exempt exempt-class
On_Demand on_demand-class
Production_Services production_services-class
General_Services general_services-class
Default default-class


Explanation:
analysis-class: is a job class reserved for ThruPut Manager Job Analysis.
deferred-class list: is a list of the Deferred Analysis Classes. This list can be replaced by the text None if no job classes being specified.
selectable-class list: is a list of the job classes being selected for Job Analysis. This list can be replaced by the word All if all job classes being specified or None if no job classes being specified.
exempt-class: is a job class assigned to the jobs to be exempt from ThruPut Manager Job Analysis. Jobs managed by DCS are exception, and are managed by ThruPut Manager even if they exempt. This list can be replaced by the word All if all job classes being specified or None if no job classes being specified.
on_demand-class: is a job class being associated with DEMAND. The On_Demand line can be replaced by the text None if no job class being specified.
production_services-class: is a job class being selected for Production Services jobs running under SLM management. If a job class has not been specified, None is displayed.
general_services-class: is a job class being selected for General Services SLM jobs. If a job class has not been specified, None is displayed.
default-class: is a job class to be used in situations where an invalid job class has been specified either in JCL or JAL. If a default job class has been specified, it will be used in cases where an invalid job class is encountered, instead of failing the job. If a default job class has not been specified None is displayed.
The TM CLASS DISPLAY command has been successfully processed.

System action: System displays the list of job classes currently in use.

Operator Response: None.

Programmer Response: None.

DTM3234E

Class ’x’ still has unprocessed jobs! Consider the “SLM FALLBACK” Command


Explanation: The TM CLASS SET command has been used to set an SLM class to ‘NONE’, but there are still unprocessed jobs in that class queue.

System action: None.

Operator Response: Either wait until the class queue is empty or consider using the SLM FALLBACK command to requeue the jobs.

Programmer Response: None.

DTM3235I

HRecalls will be performed under ‘ssss’ security environment


Explanation:
ssss: is the security environment used. It is one of the following:

  • TM – indicates the security environment associated with the ThruPut Manager started task. This is the default.
  • USER – indicates the security environment associated with the batch job which triggered the recalls.

This message is issued in response to the “JSS RECALL” command and indicates the environment under which DFSMShsm recalls are processed. The recalls affected are those initiated implicitly as a result of the job being managed by SLM or explicitly as a result of a “JSS RECALL MAX_WAIT” JAL directive It does not affect those initiated as a result of a “JSS RECALL DELAY_FOR” JAL directive. DELAY_FOR recalls are always performed under the security environment associated with the batch job which triggered the recalls.

System action: DFSMShsm recalls will be performed under the specified security environment.

Operator Response: None.

Programmer Response: None.

DTM3236E

Class update request failed, JES2 is not responding. Retry the request later.


Explanation: A TM CLASS command has been used to update the class attributes. JES2 has not responded for 30 seconds so the request is aborted.

System action: None.

Operator Response: Investigate why JES2 is unresponsive, once JES2 appears to be responding, try the TM CLASS command again.

Programmer Response: None.

DTM3237I

Class Table Synchronized - Class(c) Flags(xxxx)


Explanation: A TM CLASS command has been issued and the display process is validating the internal class table. The class specified ("c") contains flags (hexadecimal "xxxx") indicating it belongs to another TM class or does not belong to the TM class as indicated in the display.

System action: The Class Table entry is in the process of being updated. There has been a delay in the Class Table entry update. The Class Table entry should synchronize within a few seconds.

Operator Response: If the Class Table entry does not eventually synchronize, contact BMC Support for further diagnostics and assistance in correcting the Class Table entry.

Programmer Response: None.

DTM3238E

Excessive number of classes specified


Explanation: A TM CLASS command has been issued and the class list is too long to be processed.

System action: The TM CLASS command is not executed.

Operator Response: Enter a shorter class list by splitting it into two or more TM CLASS commands.

Programmer Response: None.

DTM3239E

TM CLASS command failed validation


Explanation: An invalid TM CLASS command has been issued.

System action: The TM CLASS command is not executed.

Operator Response: Remove any classes from the following class exception list and reissue the TM CLASS command.

Programmer Response: None.

DTM3300I

‘TM BATCH’ IMBEDDED IN DATASET dsname, COMMAND IGNORED


Explanation: A TM BATCH command was found within the command input stream to a TM BATCH command or initialization statement.

System action: The command is ignored. This prevents possible recursive calls.

Operator Response: The command should be removed from the input stream.

Programmer Response: None.

DTM3301I

NO COMMANDS QUEUED FROM DATASET dsname


Explanation: The data set specified in the TM BATCH command is empty, or contains only comment statements.

System action: The TM BATCH command is ignored.

Operator Response: None.

Programmer Response: Ensure that the correct data set name was provided.

DTM3302I

nnnnn COMMANDS QUEUED FROM DATASET dsname


Explanation: All the commands found in the input stream to a TM BATCH command or initialization statement have been queued for processing.

System action: The command terminates normally.

Operator Response: None.

Programmer Response: None.

DTM3500I

support SERVICES UNAVAILABLE


Explanation: This message is issued when an initiator selecting the Job Analysis Class is started , but TMSS is not active. The Job Analyzer cannot proceed until TMSS becomes active.

System action: No jobs are selected for analysis until TMSS is started.

Operator Response: Start TMSS.

Programmer Response: None.

DTM3501A

REPLY ‘RETRY’ TO RETRY, OR ‘STOP’ TO TERMINATE THIS JOB ANALYZER


Explanation: If your installation has chosen not to use JES2 Exit 14, this message is issued with message DTM3500I.

System action: The Job Analyzer waits for a reply from the operator. If TMSS becomes active before the operator has replied, this message is deleted and a reply is not required.

Operator Response: To repeat the check for TMSS being active, enter ‘RETRY’.

To force the Job Analyzer to abend, enter ‘STOP’. The Job Analyzer abends with a system 222 abend code, causing the Job Analyzer to drain and the job being processed to be requeued for analysis.

Programmer Response: None.

DTM3502I

**WARNING** SLM CLASS IN USE BY JES2 OR WLM


Explanation: A JES2 or WLM initiator attempted to select an SLM-managed job.

System action: The job is not selected.

Operator Response: None.

Programmer Response: Check to ensure that initiators are defined for either exclusive SLM or exclusive JES2/WLM use.

DTM3503E

Job selection delayed.
To start job selection enter $MJ,START after confirming class definitions with the TM CLASS ADD or DELETE commands.
See class definition below (DTM3233I).


Explanation: The selection classes need to be confirmed before job selection processing can continue. The first time ThruPut Manager is started in a JESPlex it needs to delay processing until the correct list of classes it is to process has been confirmed. Related message is DTM3233I.

System action: All batch jobs will wait during conversion until the class list has been confirmed.

Operator Response: Use the TM CLASS D command to display the selectable classes, if they are correct enter $MJ,START. If they need adjustment use TM CLASS ADD or DEL.
NOTE: The TM CLASS D command is issued automatically whenever this message is issued so the response follows immediately.

Programmer Response: None.

DTM3504I

Invalid class xxx replaced by DEFAULT class yyy


Explanation: A job was submitted with a multi-character class that has not been defined to JES2. If the ThruPut Manager DEFAULT class has been defined, it will replace any invalid class found at job submission time.

System action: The job will be processed as if it had been submitted with class yyy, the DEFAULT class.

Operator Response: Not applicable, the message only appears in the jobs message log.

Programmer Response: None.

DTM3550I

REQUEST FOR support SERVICES NOT ACKNOWLEDGED


Explanation: TMSS has not completed processing of a request passed to it prior to the expiration of a predefined time limit.

System action: Message DTM3551A is issued requesting operator intervention.

Operator Response: See message DTM3551A.

Programmer Response: None.

DTM3551A

REPLY ‘RETRY’ TO RETRY, ‘WAIT’ TO WAIT, OR ‘CANCEL’ TO TERMINATE THIS REQUEST


Explanation: This message follows message DTM3550I.

System action: The component that issued the request to TMSS waits for the operator to reply.

Operator Response: Reply ‘RETRY’ to have the request tried again.
Reply ‘WAIT’ to continue to wait (5 minutes) for TMSS to process the request.
Reply ‘CANCEL’ to terminate the requestor with a System 222 abend.

Programmer Response: None.

DTM3700I

INVALID ACCUMULATOR IDENTIFIER: text


Explanation: The command expected to find the positional parameter $ACCUMn (where n is a single digit from 1 to 9), but found text instead.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3701I

REQUIRED ACCUMULATOR IDENTIFIER NOT SPECIFIED


Explanation: The command could not find the required positional parameter $ACCUMn (where n is a single digit from 1 to 9).

System action: The command is ignored.

Operator Response: Include an accumulator identifier with the command.

Programmer Response: None.

DTM3702I

INVALID SYNTAX IN THE keyword KEYWORD


Explanation: The command detected a syntax error in the indicated keyword.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3703I

INVALID POSITIONAL PARAMETER: text


Explanation: The command expected to find a positional parameter, but found text instead.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3704I

INVALID KEYWORD: text


Explanation: the command expected to find a valid keyword, but found text instead.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3705I

INVALID DESTINATION: destination-name


Explanation: A command was entered with an invalid value for its destination.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3706I

INVALID JOB NUMBER: value


Explanation: A command was entered but the job number was invalid.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3707I

TOO MANY JOB NUMBERS SPECIFIED IN JOB LIST


Explanation: More than 100 job numbers were specified in the EXCLUDE keyword of the CVL JOBRELEASE command, or on the NOROLL keyword on the CVL GENERATE command.

System action: The command is ignored.

Operator Response: Specify fewer job numbers when entering the command.

Programmer Response: None.

DTM3708I

THE keyword KEYWORD HAS BEEN SPECIFIED MORE THAN ONCE


Explanation: A keyword has been specified more than once in a single command.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3709I

THE keyword KEYWORD VALUE IS NOT NUMERIC: text


Explanation: The keyword requires numeric data, but non-numeric data was found.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3710I

THE keyword KEYWORD VALUE IS OUT OF RANGE: value


Explanation: The keyword requires a numeric value, but was entered with a value that is too low or too high.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3711I

JOB NUMBER ‘jobnum’ HAS BEEN SPECIFIED MORE THAN ONCE


Explanation: A command included the same job number more than once.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM3712I

REQUIRED KEYWORD keyword MISSING


Explanation: A keyword required to use the command was not included.

System action: The command is ignored.

Operator Response: Re-enter specifying the omitted keyword.

Programmer Response: None.

DTM3713I

UNABLE TO PERFORM FUNCTION BECAUSE VIF PROCESSOR IS UNAVAILABLE


Explanation: The command could not be performed because the VIF processor is not available.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM3714I

UNABLE TO PERFORM FUNCTION BECAUSE OF VIF PROCESSOR ERROR


Explanation: The command could not be performed because of a VIF processor error while handling the request.

S ystem Action: The command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the error.

DTM3715I

CONSOLIDATED VOLUME LIST (CVL) DISPLAY
$ACCUMn
DESTINATION: dest RETAIN: nnn
CURRENT CVLN: nnn PRESENT: nnn
CVLN cycle# FOR $ACCUMn
START: yyyy.ddd hh.mm.ss
*** CURRENT ***
HELD JOBS: nnnnn VOLUMES: nnnnn JOBS: nnnnn
CVLN cycle# FOR $ACCUMn
START: yyyy.ddd hh.mm.ss (FORMATTED)
STOP: yyyy.ddd hh.mm.ss (JOBRLSE ISSUED) (JOBS EXCLUDED)
HELD JOBS: nnnnn VOLUMES: nnnnn JOBS: nnnnn

*** Version 3 Mode Only ***


Explanation: This message is issued in response to a CVL DISPLAY command. For each accumulator, the first two lines show the status of the accumulator settings. These are followed by a status display for each consolidation cycle that is currently associated with the accumulator.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM3715I

CONSOLIDATED VOLUME LIST (CVL) DISPLAY
$ACCUMn
DEST: dest RETAIN: nnn PRESENT: nnn
CYCLE cycle# FOR $ACCUMn
*** status ***
STARTED: yyyy.ddd hh.mm.ss
STOPPED: yyyy.ddd hh.mm.ss
JOBS: nnnnn VOLUMES: nnnnn

*** Version 4 Mode Only ***


Explanation:
status: represents the current status of the cycle, and can be:

  • ACCUMULATING, indicating that this cycle is still accumulating volumes.
  • OUTSTANDING, indicating that the CVL for this cycle has been printed but no volumes have been PULLED yet.
  • OUTSTANDING – VOLUMES TO DO, indicating that the CVL for this cycle has been printed and some volumes have been PULLED, but some volumes remain to be PULLED.
  • NOT OUTSTANDING, indicating that this CVL has been printed and a DONE has been issued, but it depends on volumes listed on other Volume Lists that have not yet been PULLED.
  • DONE, indicating that the CVL for this cycle has been printed and has been DONE.

This message is issued in response to a CVL DISPLAY command. For each accumulator, the first line shows the status of the accumulator settings. This is followed by a status display for each consolidation cycle that is currently associated with the accumulator.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM3716I


Explanation: This is an internal diagnostic message.

DTM3717I

$ACCUMn CYCLE cycle# DOES NOT EXIST


Explanation: The consolidation cycle number does not exist.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM3718I

NO PREVIOUS CYCLE EXISTS FOR $ACCUMn


Explanation: A CVL REGENERATE command was issued without specifying a consolidation cycle number. The default is to regenerate the current cycle minus one, but this cycle does not exit.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM3719I

FUNCTION NOT ALLOWED FOR AN ACTIVE CYCLE


Explanation: A CVL JOBRELEASE or CVL REGENERATE command was entered, but the specified consolidation cycle is still active.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM3720I

NO ROOM IN VOLUME FILE TO CREATE A NEW CVL CYCLE


Explanation: The VIF does not have enough space left to create another consolidation cycle.

System action: The command is ignored.

Operator Response: Generate and FVL and return some volumes to the library. Use the FVL DONE command to free space in the VIF.

Programmer Response: None.

DTM3721I

CVL FOR $ACCUMn CYCLE cycle# GENERATED AND SENT TO DESTINATION ‘destination-name’
or
CVL FOR $ACCUMn CYCLE cycle# NOT PRINTED, DESTINATION UNAVAILABLE


Explanation: A CVL GENERATE command was entered.

System action: If the specified destination is available, the current consolidation cycle is closed and the CVL becomes eligible for printing by a CPS Writer selecting the destination destination-name. The consolidation cycle number is incremented by one and a new cycle is started.
If the specified destination is not available, the current consolidation cycle continues and no CVL is generated.

Operator Response: None.

Programmer Response: None.

DTM3722I

$ACCUMn CYCLE cycle# HAS BEEN DELETED


Explanation: A CVL DELETE command was entered.

System action: The specified consolidation cycle associated with accumulator $ACCUMn is deleted.

Operator Response: None.

Programmer Response: None.

DTM3723I

ALL CYCLE(S) FOR $ACCUMn HAVE BEEN DELETED


Explanation: a command was entered requesting the deletion of all consolidation cycles for the specified accumulator.

System action: All consolidation cycles for accumulator $ACCUMn are deleted, and a new consolidation cycle is started using the identifier 1.

Operator Response: None.

Programmer Response: None.

DTM3724I

FOLLOWING JOBS EXCLUDED BUT NOT FOUND IN $ACCUMn CYCLE cycle#:

job#1 job#2 ...

TOTAL NUMBER OF JOB(S): total


Explanation: A command was entered which excluded the listed jobs, but the jobs were not found in the accumulator and consolidation cycle specified.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM3725I

JOBRLSE SUMMARY FOR $ACCUMn CYCLE cycle#

NUMBER OF JOBS RELEASED: nnnn

NUMBER OF JOBS EXCLUDED: nnnn

THIS CYCLE HAS [NOT] BEEN DELETED


Explanation: A CVL JOBRELEASE command was entered. This message summarizes the actions taken on the specified accumulator and consolidation cycle.

System action: The indicated number of jobs have been released or excluded, respectively. If all jobs for the CVL have been released, it is deleted.

Operator Response: None.

Programmer Response: None.

DTM3726I

WRITER TASK TERMINATED WHILE GENERATING CVL FOR $ACCUMn CYCLE cycle#


Explanation: The CPS Writer task has terminated while processing the indicated accumulator and consolidation cycle.

System action: The CPS Writer terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the error.

DTM3727I 

WRITER TASK ABENDED WHILE GENERATING CVL FOR $ACCUMn CYCLE cycle#


Explanation: The CPS Writer task has abended while processing the indicated accumulator and consolidation cycle.

System action: The CPS Writer abends.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the error.

DTM3728I

UNABLE TO SPOOL CVL FOR $ACCUMn CYCLE cycle# BECAUSE OF CPS SPOOL CONTROL RECORD DAMAGE


Explanation: The CVL processor detected CPS SPOOL Control Record damage while attempting to spool a CVL.

System action: The CVL is not spooled.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the error.

DTM3729I

CVL FOR $ACCUMn CYCLE cycle# CANCELLED BY OPERATOR


Explanation: The CVL processor was unable to complete the indicated CVL due to errors indicated by previous messages, and the operator replied CANCEL to one of these messages.

System action: Processing of the indicated CVL is terminated.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages indicating the nature of the error.

DTM3730I

CVL FOR $ACCUMn CYCLE cycle# REPRINTED AND SENT TO
DESTINATION ‘destination-name’


Explanation:
$ACCUMn identifies the accumulator.
cycle#: identifies the consolidation cycle.
‘destination_name’: is a CVL destination.
A CVL REGENERATE command was entered.

System action: The indicated CVL is recreated and made eligible for printing by a CPS Writer selecting destination destination-name.

Operator Response: None.

Programmer Response: None.

DTM3731I

nnn VOLUMES PULLED FOR $ACCUMn CYCLE cycle-number


Explanation: This message is issued in response to a CVL DONE command. It indicates the number of volumes that were marked PULLED.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM3732I

‘EXCLUDED ONLY’ CVL FOR $ACCUMn CYCLE nnn SENT TO
DESTINATION destination-name


Explanation: This message is issued in response to a CVL REGENERATE command with the EXCLUDED keyword.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM3733I

NO VOLUMES ACCUMULATED FOR $ACCUMn CYCLE nnn


Explanation: A CVL GEN or CVL REGEN command was issued but there are no volumes accumulated.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM3734I

ALL JOBS FOR CVL $ACCUMn CYCLE nnn HAVE BEEN RELEASED


Explanation: A CVL REGEN command with the EXCLUDED keyword was issued but all jobs for that CVL cycle have been released.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM3735I

nnn ENTRIES HAVE BEEN ROLLED FROM $ACCUMn
CYCLE nnn INTO CYCLE nnn


Explanation: This message is issued in response to a CVL ROLL command.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM3736I

REQUIRED POSITIONAL PARAMETER MISSING


Explanation: A command or initialization statement is missing a required parameter.

System action: If the attempt was made with an operator command, the command is ignored. If the attempt was made with an initialization statement, TMSS terminates with a return code of 8.

Operator Response: If the message results from a command, re-enter and specify the missing parameter. If the message results from TMSS initialization processing, notify support personnel.

Programmer Response: Add the missing parameter to the initialization statement.

DTM3737I

$ACCUMn CYCLE nnn CANNOT BE GENERATED UNTIL RETAINED CYCLE IS DONE


Explanation: A CVL GENERATE command was entered, but could not be generated because the number of active CVLs is equal to or exceeds the RETAIN count for the specified accumulator.

System action: The command is ignored.

Operator Response: Complete work on an outstanding CVL and indicate that it is DONE, then re-enter the CVL GENERATE command.

Programmer Response: Consider increasing the RETAIN count for this accumulator.

DTM3771I

JOB ANALYZER SERVICE, TYPRUN=type, BYPASSED,

DUE TO OPERATOR INTERVENTION


Explanation: A job that specified TYPRUN=HOLD or TYPRUN=SCAN has bypassed the Job Analyzer because the job class was modified from an analysis class to an execution class via a JES2 operator command.

System action: For a TYPRUN=SCAN the job is terminated. No JCL verification was performed because the Analyzer was bypassed. For a TYPRUN=HOLD the job is Held. Again no JCL verification is performed because the Analyzer has been bypassed.

Operator Response: None.

Programmer Response: None.

DTM3772I

ThruPut Manager SERVICES BYPASSED DUE TO
OPERATOR INTERVENTION


Explanation: A job has bypassed the Job Analyzer because the job class was modified from an analysis class to an execution class via a JES2 operator command.

System action: No ThruPut Manager Services are available to the job.

Operator Response: None.

Programmer Response: None.

DTM3773I

ThruPut Manager SERVICES NOT AVAILABLE FOR THIS JOB


Explanation: A job has been selected for execution but ThruPut Manager cannot manage the job because one of its critical control blocks is missing. This can occur if the job was read in on a system that does not have ThruPut Manager installed, or on which JES2 Exit 7 has been disabled.

System action: No ThruPut Manager Services are available to the job. The job is allowed to execute as though ThruPut Manager had not been installed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Install ThruPut Manager on all systems in the MAS complex, or ensure that JES2 Exit 7 is enabled.

DTM3774I

ThruPut Manager services bypassed, job submitted in XBM class


Explanation: A job has bypassed the Job Analyzer because it was submitted in a class with an XBM procedure. ThruPut Manager does not process these jobs.

System action: Any Thruput Manager services which the job requires (e.g. JBS, JCS, JLS) are not available.

Operator Response: None.

Programmer Response: None.

DTM3800A

jobname, function FATAL ERROR DURING where-name
REPLY ‘RETRY’, ‘CANCEL’, ‘DUMP’, ‘HOLD’ OR ‘IGNORE’


Explanation: During the processing phase indicated, a Thruput Manager function request resulted in a fatal error.

System action: Waits for the operator to indicate how to proceed.

Operator Response: Notify personnel responsible for support.
Reply ‘RETRY’ to attempt the request again.
Reply ‘CANCEL’ to cause the job or Analyzer to terminate with a 222 abend.
Reply ‘DUMP’ to cause the job or Analyzer to terminate with a 222 abend and a dump.
Reply ‘HOLD’ to cause the job or Analyzer to terminate with a 222 abend and the job will be held.
Reply ‘IGNORE’ to allow the processing to continue to the next stage.

Programmer Response: See previous message(s) documenting the nature of the error.

DTM3801I

ERROR IN ‘detailed-explanation-on-where-the-error-occurred’,
‘detailed-explanation-on-what-the-error-is’


Explanation: Support Services has detected an error. Extensive information on where the error occurred and what the error was is provided. This error has occurred within Support Services.

System action: Issues action message DTM3800A requesting operator’s action.

Operator Response: Notify personnel responsible for support.

Programmer Response: From the information provided see if the error is caused by your installation configuration. If error persists contact BMC Support.

DTM3802I

ERROR DETECTED BY, ‘detailed-explanation-on-where-the-error-occurred’,
‘detailed-explanation-on-what-the-error-is’


Explanation: Support Services has detected an error. Extensive information on where the error occurred and what the error was is provided. The error, while detected by Support Services, is outside it.

System action: Issues message DTM3800A requesting operator’s action.

Operator Response: Notify personnel responsible for support.

Programmer Response: From the information provided see if the error is caused by your installation configuration. If error persists contact BMC Support.

DTM3803I

ABEND,’code’, ‘detailed-explanation-on-what-the-error-is’


Explanation: An ABEND has occurred in Support Services. A detailed explanation on what cause the error is included with the message.

System action: Issues message DTM3800A requesting operator’s action.

Operator Response: Notify personnel responsible for support.

Programmer Response: From the information provided see if the error is caused by your installation configuration. If error persists contact BMC Support.

DTM3804I

SOS ERROR PROCESSING ‘keyword’ KEYWORD


Explanation: A request to alter the specified keyword failed.

System action: Issues a DTM0666E message and creates a dump.

Operator Response: Notify personnel responsible for support.

Programmer Response: Analyze the DTM0666E message and accompanying dump for cause of the error.

DTM3806I

UN/STORAGETEK ‘xxx’ COMMAND TIMED OUT


Explanation: The Sun/StorageTek UUI command failed to complete within a reasonable time.

System action: None.

Operator Response: None.

Programmer Response: Investigate reason for command failure.

DTM3807I

SUN/STORAGETEK SMC DOES NOT HAVE ANY DEFINED TAPEPLEX


Explanation: TM issues a “SMC TAPEPLEX LIST” command to determine if HSC is currently ACTIVE. It receives a response indicating that TAPEPLEX= has not been specified in the SMC parameters. This specification is required for TM’s interface to communicate with the STK software.

System action: None.

Operator Response: Restart SMC with a TAPEPLEX defined.

Programmer Response: None.

DTM3808A

Start ‘aaa’ or Reply ‘N’ to continue without Sun/StorageTek Support


Explanation:
aaa: SMC or HSC
The SMC and/or HSC services required for StorageTek support has either failed or was not started.

System action: If the reply is ‘N’, TMSS continues without StorageTek support.

Operator Response: Note that this message will automatically be deleted when SMC and/or HSC has been started and is fully initialized.

Programmer Response: Determine why the SMC and/or HSC service has not been started and correct.

DTM3809I

Sun/StorageTek HSC is inactive for TapePlex ‘ttt’


Explanation: ttt: TapePlex that is currently inactive.
The HSC service is inactive for the specified TapePlex.

System action: Processing will continue. Volume requests for the specified TapePlex will be handled as MANUAL.

Operator Response: Start HSC service for this TapePlex.

Programmer Response: None.

DTM3810I

title-message-for-error
hexadecimal display of data area


Explanation: A JES2 interface error has occurred.

System action: The control block area is displayed.

Operator Response: Notify personnel responsible for support.

Programmer Response: From the information provided see if the error is caused by your installation configuration. If error persists contact BMC Support.

DTM3851I

TM UNIT DISPLAY
UNIT HANDLED-AS
unitname substitute


Explanation: A TM UNIT DISPLAY command was entered.

System action: Displays a list showing the current mapping of unit names as specified by previous TM UNIT HANDLE initialization statements or commands.

Operator Response: None.

Programmer Response: None.

DTM3852I

UNIT unitname IS NO LONGER BEING HANDLED


Explanation: A TM UNIT DELETE command was entered.

System action: References to the specified unit name are no longer mapped to a different unit name.

Operator Response: None.

Programmer Response: None.

DTM3853I

UNIT unitname IS NOT BEING HANDLED


Explanation: A TM UNIT DELETE command was entered that specified a unit name that was not currently mapped to another unit name.

System action: The command is ignored.

Operator Response: Ensure that the correct unit name was entered.

Programmer Response: None.

DTM3854I

UNIT unitname WAS BEING HANDLED AS old-name,
WILL BE HANDLED AS new-name


Explanation: A TM UNIT HANDLE command was entered specifying a substitute unit name that differs from the previous mapping.

System action: The specified unit name will now be mapped to the new substitute.

Operator Response: None.

Programmer Response: None.

DTM3855I

UNIT unitname WILL BE HANDLED AS substitute


Explanation: A TM UNIT HANDLE command was entered that specified a substitute unit name for a unit name that was not previously being mapped.

System action: The specified unit name will now be mapped to the substitute.

Operator Response: None.

Programmer Response: None.

DTM3856I

DEFAULT UNIT SET TO unitname [PREVIOUSLY SET TO old-name]


Explanation: A TM UNIT SET DEFAULT command was entered. If there already was a default for the specified unit name, the old default unit name is also displayed.

System action: Uses the specified unit name as the default for new allocations that do not specify a unit name.

Operator Response: None.

Programmer Response: None.

DTM3857I

UNIT unitname IS ALREADY BEING USED AS A type UNIT


Explanation:
type: can be one of AUTOMATED, MANUAL, MAPPING, or MIXED.
A TMSS initialization statement or a TM UNIT command attempted to use a unit name that is already in use.

System action: If the attempt was made with an operator command, the command is ignored. If the attempt was made with an initialization statement, TMSS terminates with a return code of 8.

Operator Response: If the message results from a command, ensure that the correct unit name was entered. If the message results from TMSS initialization processing, notify support personnel.

Programmer Response: Check the TM ACS, TM ATL, and TM UNIT HANDLE initialization statements for duplicate unit names.

DTM3858I

DEFAULT UNIT OF unitname DELETED


Explanation: This message is issued in response to the TM UNIT DELETE DEFAULT command. After this command, there is no longer a Thruput Manager default unit name.

System action: Removes the default unit name.

Operator Response: None.

Programmer Response: None.

DTM3859I

NO DEFAULT UNIT CURRENTLY SET


Explanation: An attempt was made to delete the default TM UNIT, but there was no default in effect.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM3860I

type UNIT NAME unitname NOT DEFINED IN EDT
source IGNORED.


Explanation:
type: is ‘AS’ if the attempt was to define a substitute unit name, or ‘DEFAULT’ if the attempt was to define a default unit name.
source: is COMMAND if the attempt was made with an operator command, or STATEMENT if the attempt was made with an initialization statement.
A TM UNIT command or initialization statement referred to a unit name that could not be found in the Eligible Device Table (i.e., not defined to the system).

System action: If the attempt was made with the TM UNIT operator command, the command is ignored.
If the attempt was made with a TM UNIT initialization statement, TMSS initialization statement, TMSS terminates once all initialization statements have been processed.

Operator Response: If the attempt was made with a command, ensure that the correct unit name was entered. If the attempt was made with an initialization statement, notify support personnel.

Programmer Response: Check that the correct unit name is specified in the TMSS initialization statement.

DTM3861I

TM VTFM unittype UNIT NAME unitname error


Explanation:
unittype: is the unit type, and is either ESOTERIC or GENERIC.
unitname: Is the unitname being defined.
error: Is a description of the error.

The unitname described in the message is invalid.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the unitname.

DTM3862I

CA-VTAPE API MODULE ‘SVTSAPI’ IS NOT AVAILABLE


Explanation: The CA-Vtape API module SVTSAPI failed to load during TMSS initialization.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Ensure the CA-Vtape API module is installed in a linklisted data set.

DTM3863I

UNABLE TO LOAD CA-VTAPE API MODULE. ‘SVTSAPI’,
R1=X’scc’, R15=X’rs’


Explanation:
scc: is the system completion code for the abend.
rs: is the reason code associated with the system completion code.

During analysis of a job, the load for the CA-Vtape APIL module SVTSAPI failed. Thruput Manager can no longer determine whether a volume is a CA-Vtape virtual volume.

System action: Analysis of the job continues. Any CA-Vtape virtual volumes are treated as real volumes. The Job Analyzer continues to attempt calls to SVTSAPI without further error messages. The message is deleted if a call succeeds.

Operator Response: Notify personnel responsible for support.

Programmer Response: Ensure the CA-Vtape API module is installed in a linklisted data set.

DTM3864I

CA-VTAPE INTERFACE IS NOT AVAILABLE, SVTS NOT ACTIVE
or
CA-VTAPE INTERFACE IS NOT AVAILABLE, SVTS CSA MODULE NOT LOADED


Explanation: During analysis of a job, a call to the CA-Vtape API module SVTSAPI indicated that the interface was not available.

System action: Analysis of the job continues. Any CA-Vtape virtual volumes are treated as real volumes. The Job Analyzer continues to attempt calls to SVTSAPI without further error messages. The message is deleted if a call succeeds.

Operator Response: Notify personnel responsible for support.

Programmer Response: If the message indicates SVTS is not active, ensure that the SVTS subsystem is started. If the message indicates that the SVTS CSA module is not loaded, ensure that the SVTS subsystem has completed initialization, otherwise notify personnel responsible for CA-Vtape support.

DTM3865I

proc.step.ddname.+concat - “JCL ALTER UNITNAME” IGNORED


Explanation: A TM DAL request attempted to alter the UNITNAME for an existing cataloged data set to one that is not the same as the catalog device type (i.e. TAPE -> DASD or VTS).

System action: The request is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TM DAL that is making the invalid request.

DTM3866I

UNABLE TO LOAD STK VTCS PGMI ‘SWSPGMI’,
R1=X’scc’, R15=X’rs’


Explanation:
scc: indicates the system completion code for the abend that would have been issued if it had not been trapped.
rs: indicates the reason code associated with the system completion code.

During the analysis of a job, a load of the StorageTek VTCS Program Interface (PGMI) module, SWSPGMI, failed. Without the STK VTCS PGMI, it is not possible for the Job Analyzer to determine if a StorageTek Virtual Tape Volume (VTV) is “RESIDENT”. In addition, if the VTV is not “RESIDENT”, it cannot be RECALLed.

System action: Analysis of the job continues. Virtual tape volumes that are not resident are not recalled. Real tape volumes that are not resident are recalled.

Operator Response: Notify personnel responsible for support.

Programmer Response: Ensure that the StorageTek VTCS PGMI is installed and in a linklisted data set.

DTM3867I

sms-info “JCL ALTER” IGNORED.


Explanation: A TM DAL request attempted to alter SMS parameters, but the customization option for this support was not specified on the JES2 initialization statement TMPARM.

System action: The request is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the TM DAL that is making the invalid request or contact BMC Support for help in enabling this feature.

DTM3868I

nnnn - JCL type //ddname DD DSN=dsname


Explanation:
nnnn: is the JCL statement number.
type: is the operation performed, and can be:

  • ADD
  • DELETE
  • REPLACE

ddname: is the name of the affected DD statement.
dsname: is the data set name.
This message is written to SYSMSGS when a JCL ADD, JCL DELETE, or JCL REPLACE statement is executed in TM DAL.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM3869I

CA 7 Interface Routine (DTMCA7UI) has not been installed


Explanation: If CA-7 is installed, Thruput Manager job analyzer checks if DTMCA7UI has been linked into the analyzer. If it is not this message is issued every 25 jobs. The value of the $CA7(YES/NO) descriptor will be "NO" even if the job was submitted by CA 7.

System action: DAL/JAL descriptor $CA7 is set to "NO".

Operator Response: Notify personnel responsible for support.

Programmer Response: Ensure that the DTMCA7UI routine has been assembled and linked together with the job analyzer (should be TTM7105 - check with support).

DTM3870I

GDGBIAS=JOB | STEP


Explanation: JAL requested that the GDGBIAS value be set for this job. This indicates the job's new GDGBIAS value.

System action: None

Operator Response: None

Programmer Response: NoneTo remove the display of this message the "JCL SET DO_NOT_LOG_ALTERS" statement may be used.

DTM4450I

type ‘EXIT’ STATEMENT WAS NOT ENCOUNTERED


Explanation:
type: is either DAL or JAL.
The Job Analyzer completed processing without encountering an ‘EXIT’ statement.

System action: For JAL, the job is requeued as if EXIT REQUEUE was encountered. For DAL, processing continues as if an EXIT CONTINUE has been encountered.

Operator Response: None.

Programmer Response: Ensure that an ‘EXIT’ statement is coded at all possible exits from DAL/JAL.

DTM4451I

type INTERNAL TEXT AND JOB ANALYZER ARE INCOMPATIBLE.
JOB REQUEUED AND HELD
(Vn Rn.n.nn/Vn Rn.n.nn)


Explanation:
type: is either DAL or JAL.
Vn Rn.n.nn: Is the version, release, and PTF level. The first version is the Language Processor version, the second is the current system level.

Thruput Manager detected that the Action Language was compiled using an incompatible version of the Language Processor.

System action: The job is requeued and held using the class with which it was submitted.

Operator Response: None.

Programmer Response: Ensure that the Language Processor and the Job Analyzer are at the same release level.

DTM4452I

INTERNAL ERROR ENCOUNTERED WHILE PROCESSING STATEMENT nn


Explanation: Possible corrupted Action Language. The Job Analyzer encountered an unrecognizable text unit at statement nn while evaluating the specified job.

Programmer Response: Re-process the DAL/JAL.

System action: Job evaluation continues. If applicable, the Property for the statement is set to false. At the end of job analysis the message DTM1461I reflecting a JAL execution error is issued. The job is failed and queued for JES2 output processing.

Operator Response: None.

Programmer Response: Correct Action Language using the information provided in the message.

DTM4453I


Explanation: This is an internal diagnostic message.

DTM4454I


Explanation: This is an internal diagnostic message.

DTM4455I


Explanation: This is an internal diagnostic message.

DTM4456I


Explanation: This is an internal diagnostic message.

DTM4458I

"SLM SET QUICKJOB" Ignored. reason


Explanation:
reason: is either

  • Job not SLM Managed.
  • Job is PCS Managed.

JAL requested SLM SET QUICKJOB but the request was ignored.
Either the job is not SLM managed or the job is being managed by PCS. In both cases, these jobs can not be processed as Quick Jobs.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4459I

INVALID console ‘id’ DETECTED DURING type
PROCESSING OF STATEMENT nn


Explanation:
console: is either CONSOLE_NAME or UCMID.
type: is either DAL or JAL.
While processing the Action Language statement WTO, the Job Analyzer determined that the UCM ID or console name specified on the statement MSGDEF is undefined or invalid, or that the console is unavailable.

System action: The Job Analyzer continues processing. No message is issued from the Action Language.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the Action Language.

DTM4460I

ERROR DETECTED DURING type PROCESSING OF STATEMENT nn -
statement/keyword: information error-reason - character-string


Explanation:
type: is either DAL or JAL.
nn: represents the Action Language statement number to help you identify the statement that caused the error.
statement/keyword: Indicates the statement or keyword in error.
information: explanation of the error.
error-reason: the cause of the error.
character-string: the first 16 characters of the data causing the error (if applicable).

The Action Language evaluator encountered invalid data at the statement indicated.

System action: Job evaluation continues. If applicable, the Property for the statement is set to false. At the end of job analysis the message DTM1461I reflecting a JAL execution error is issued. The job is failed and queued for JES2 output processing.

Operator Response: None.

Programmer Response: Correct the Action Language.

DTM4461I

INVALID ROUTE CODE SPECIFIED. DEFAULT ROUTE CODE ASSUMED


Explanation: During Job Analysis an invalid route code was detected for a WTO that was requested in DAL/JAL. The keyword ROUTCDE(nnn) in a MSGDEF statement specified a route code that is not supported on the executing system. For example, ROUTCDE(120) executing on a pre MVS/XA 2.2 system.

System action: Default route code is assumed.

Operator Response: None.

Programmer Response: Review route code assignments.

DTM4462I

MORE THAN XX ADD keyword STATEMENTS PROCESSED. CONDITION

ENCOUNTERED AT STATEMENT nn


Explanation: The number of Agents that can be added in JAL has been exceeded.

System action: Job evaluation continues. If applicable, the Property for the statement is set to false. At the end of job analysis the message DTM1461I reflecting a JAL execution error is issued. The job is failed and queued for JES2 output processing.

perator Response: None.

Programmer Response: Correct JAL logic so the maximum allowable number of Agents is not exceeded.

DTM4463I

ERROR AT STATEMENT nn. INVALID name: SYMBOL=%symbol
LENGTH=nn, ‘value’


Explanation: Invalid character string in a PATTERNDEF or STRINGDEF. The contents named by the symbol do not conform to Action Language usage rules.
value: The contents of the character-string.

System action: Job evaluation continues. If applicable, the Property for the statement is set to false. At the end of job analysis the message DTM1461I reflecting a JAL execution error is issued. The job is failed and queued for JES2 output processing.

Operator Response: None.

Programmer Response: Correct Action Language using the information provided in the message.

DTM4464I

INVALID JOBNAME TRACING PATTERN: ‘pattern’ TRACING NOT ACTIVE


Explanation: An invalid pattern was detected while parsing a jobname pattern for selective Action Language tracing.

System action: Job evaluation continues. DAL/JAL tracing is not activated for this job.

Operator Response: None.

Programmer Response: It is likely that storage has been overlaid. Review the trace command.

DTM4465I

*** WARNING *** DAL ‘ALTER DISP1’ NOT ALLOWED FOR: DSN=dsname,AT: DDN=ddname


Explanation: An attempt was made to alter the disposition of a NEW data set.

System action: The request is ignored.

Operator Response: None.

Programmer Response: Correct the DAL.

DTM4466I

ERROR AT STATEMENT nn table-name(subtable-name). INVALID
PATTERN: ‘pattern’


Explanation: The named table-subtable contains a pattern that is not valid for the Descriptor to which the table entry is being compared.

System action: The pattern is ignored, job evaluation continues. DAL/JAL tracing is not activated for this job.

Operator Response: None.

Programmer Response: Review the table entry and change it to conform to valid pattern formats as documented in the DAL/JAL User Guide.

DTM4467I

type [dal-type] version release.level date time trace-type dataset[(member)]


Explanation:
type: is either DAL or JAL.
dal-type: is the type of DAL, DCS or RSS. This only appears for DAL traces.
trace-type: is either TRACE or AUTO-TRACE, depending on how the trace was initiated.
data set[(member)]: identifies the data set from which the DAL or JAL was loaded.
Issued in response to a DAL/JAL trace request, or as a result of auto tracing.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM4468I

ERROR AT STATEMENT statement#,
DBS POOL ‘poolname’ NOT DEFINED


Explanation: The Drive Pool requested by the DAL statement DBS RESERVE is not defined.

System action: The job is requeued and held in the class in which it was submitted.

Operator Response: Notify personnel responsible for support.

Programmer Response: Ensure that the DAL statement DBS RESERVE specifies a valid Drive Pool.

DTM4469I

CA-7 MESSAGE ERROR. WTCA7 RC=nnn


Explanation: A DAL/JAL WTCA7 command was being processed, and the ICOM SVC return code was greater than 4.

System action: Processing continues.

Operator Response: None.

Programmer Response: Ensure that the CA-7 ICOM task is available and active.

DTM4470I

ERROR AT STATEMENT nn. INVALID SYSTEM AFFINITY: affinity


Explanation: An attempt was made to set the job’s affinity to an invalid value.

System action: The request is ignored. JAL will fail the job.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4471I

“JSS ALLOW SWITCH” IGNORED, reason


Explanation:
reason: is the reason why the switch is ignored, and is one of:

  • GROUP NAME NOT ASSIGNED
  • MANUAL UNITS REQUESTED
  • JOB ALREADY AUTOMATED

System action: The switch request is ignored.

Operator Response: None.

Programmer Response: Check to ensure that Group is assigned, and that no manual units are requested through JSS tables, RSS DAL, or JCL.

DTM4472I

Invalid Requeue Class (jclassx) Using Default (jclass)
or
Attempting to requeue to (jclassy) but jobclass is set to NONE.


Explanation: j
classx: is the 1-8 character class name.
jclassy: is one of the following:

  • Production_Services
  • General_Services
  • On_Demand

The default job class is being used in substitution for a deleted or inactive requeue class.

System action: If a Default job class has been specified, it will be used in cases where an invalid class is encountered, instead of failing the job.

Operator Response: None.

Programmer Response: Change “SET CLASS” in JAL to a valid jobclass.

DTM4474I

THE FOLLOWING SYSOUT DD STATEMENTS HAVE BEEN ALTERED: nn,nn,...


Explanation: SOS ALTER requests have been issued for the listed JCL statement numbers.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4476I

*** ERROR *** “CONTINUE” IS THE ONLY VALID “RETURN” OPERAND ON A REDRIVE


Explanation: A RETURN statement was encountered in an SOS DAL that was executed as a result of a previous RETURN REDRIVE.

System action: DAL processing is terminated with an abend code 666.

Operator Response: None.

Programmer Response: Determine why SOS DAL attempted to repeat the REDRIVE and correct.

DTM4477I

SLM SET MANAGED(YES) IGNORED, description.


Explanation: The informational message to indicate JAL request will not be performed. The reason that the job is being ignored for processing by SLM is ONE of the following:
description: reason that the job is being ignored for processing by SLM.
It is one of the following:

  • JOB WAS REQUEUED TO DEMAND CLASS – Jobs requeued to DEMAND class will not be SLM Managed.
  • CLASS(x) PRIORITY(nn) NOT IN POLICY – A FastPath Service Group for the specified class and optional priority was not found.
  • REQUEUE CLASS IS reqclass – A non-single digit jobclass was requested. Only one character job classes are managed in a job class Service Group (FastPath).

System action: None.

Operator Response: None.

Programmer Response: Do not request SLM SET MANAGED(YES) for these reasons.

DTM4480I

JAL "SLM SET CAPACITY_LEVEL" IS NO LONGER SUPPORTED.


Explanation: The JAL statement to set the capacity level for non-SLM jobs has been withdrawn. Remove it from your JAL and reprocess.

System action: The “SLM SET CAPACITY_LEVEL” is ignored. JAL processing continues.

Operator Response: None.

Programmer Response: Remove statements from JAL and reprocess.

DTM4500I

type ALLOCATION ERROR, DSNAME=dsname


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

A dynamic allocation error was detected during allocation of the data set dsname specified in the Action Language or TBL LOAD initialization statement. Message DTM0190I describes the allocation error.

System action: TMSS terminates with a return code of 28.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous message DTM0190I.

DTM4501I

type OPEN ERROR; DSNAME=dsname MEMBER=member-name


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

The data set dsname and member member-name specified in the Action Language or TBL LOAD initialization statement could not be opened.

System action: TMSS terminates with a return code of 28.

Operator Response: Notify personnel responsible for support.

Programmer Response: See accompanying message DTM4505I.

DTM4502I

type RECFM NOT FIXED; DSNAME=dsname


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

The record format of the specified data set dsname is not the required RECFM=F.

System action: TMSS terminates with a return code of 28.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the RECFM of the data set.

DTM4503I

type RECORD SIZE NOT 80; DSNAME=dsname


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

The record size of the specified data set dsname is not the required LRECL=80.

System action: TMSS terminates with a return code of 28.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the LRECL of the data set.

DTM4504I

type NOT FOUND; DSNAME=dsname MEMBER=member-name


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

The member-name was not found in the specified PDS dsname.

System action: TMSS terminates with a return code of 28.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the Action Language or TBL LOAD initialization statement.

DTM4505I

type I/O ERROR: jobname,stepname,devno,devtyp,ddname,op,err,bbcchhr,BSAM


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

An I/O error was detected while reading the Action Language or table.
The format of this message conforms with the MVS standard error message. For a complete explanation see to MVS System Messages, message number IEA000I.

System action: TMSS terminates with a return code of 28.

Operator Response: Notify personnel responsible for support.

Programmer Response: Diagnose and correct the I/O error.

DTM4506I

NOT RECOGNIZED AS type: DSNAME=dsname [MEMBER=member-name]


Explanation:
type: is either DAL or JAL.
An invalid data set was detected.

System action: TMSS terminates with a return code of 28.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the LOAD initialization statement.

DTM4507I

type INPUT HAS BEEN MODIFIED; DSNAME=dsname [MEMBER=member-name]


Explanation:
type: is either DAL or JAL.
An invalid data set was detected. The Action Language internal text has been altered since it was created.

System action: TMSS terminates with a return code of 28.

Operator Response: Notify personnel responsible for support.

Programmer Response: Recreate the Action Language internal text.

DTM4508I

[MEMBER=member-name] type RECORD COUNT INVALID; DSNAME=dsname


Explanation:
type: is either DAL or JAL.
An invalid data set was detected. The number of records read is not what was expected.

System action: TMSS terminates with a return code of 28.

Operator Response: Notify personnel responsible for support.

Programmer Response: Recreate the Action Language internal text.

DTM4509I

type JAL LEVEL INCOMPATIBLE; DSNAME=dsname [MEMBER=member-name,]
LEVEL=Vm.Rnnn PTF=TMTvvrr


Explanation:
type: is either DAL or JAL.

The software level of the Action Language to be loaded is not compatible with the current Thruput Manager. The internal text was created by release ‘Vm.Rnnn’ of the Action Language Processor. The DAL and JAL contain keywords that require the specified PTF version or later.

System action: TMSS terminates with a return code of 28.

Operator Response: Notify personnel responsible for support.

Programmer Response: Use the correct Language Processor.

DTM4510I

type LOADED:
[TYPE=dal-type] DESCRIPTION=’description’
DSNAME=dataset [MEMBER=member]
GENERATED ON DATE=date TIME=time
BY LANGUAGE PROCESSOR version release.level - #Vptf-level


Explanation:
type: is either DAL or JAL.
dal-type: is the type of DAL, DCS or RSS.
description: is the description coded on the PROCEDURE statement.

Issued in response to a DAL REFRESH, DAL LOAD or JAL REFRESH operator command.
Note: TYPE=dal_type displayed only for DAL REFRESH or DAL LOAD command output.

System action: The named DAL or JAL is refreshed.

Operator Response: None.

Programmer Response: None.

DTM4511I

type DATA SET ‘dsname’ IS NOT PHYSICALLY SEQUENTIAL


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

dsname: is the name of the data set which is supposed to contain a table or output from the Language Processor.
A LOAD initialization statement or REFRESH command was entered without specifying a member name, but the data set is not physical sequential.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM4512I

type DATA SET ‘dsname’ IS NOT PARTITIONED


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

dsname: is the name of the data set which is supposed to contain a table or output from the Language Processor.


Explanation: A LOAD initialization statement or REFRESH command was entered which included a member name, but the data set is not partitioned.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM4513I

TABLE n LOADED:
DSNAME=dataset-name [MEMBER=member-name]


Explanation: The table specified by the TBL LOAD initialization statement or the TBL REFRESH command was successfully processed.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4514I

TABLE n LOADED. TABLE IS EMPTY
DSNAME=dataset-name [MEMBER=member-name]


Explanation: The table specified by the TBL LOAD initialization statement or the TBL REFRESH command was found to be empty or contain comment entries.

System action: None.

Operator Response: None.

Programmer Response: Review situation and correct if necessary.

DTM4515I

*** ERROR *** TABLE n RECORD nnn INVALID. ‘data’


Explanation: The table numbered n contains an invalid entry. The entry in error is indicated by its sequential number nnn. This could be caused by one of the following reasons:

  • A SUBTABLE identification entry was in error.
  • An entry representing a pattern was in error.
  • The pattern entry was not preceded by a SUBTABLE entry.

System action: The table is not loaded. Processing continues.

Operator Response: Notify support personnel.

Programmer Response: Correct table entry. Issue a TBL REFRESH command to load the table.

DTM4516I

dsname(membername) IS NOT A ‘dal-type’ DAL


Explanation: dal-type: is the type of DAL, and is one of DCS, RSS, SOS, or TM.
While loading the requested DAL, Thruput Manager has detected that the DAL is not of the expected type.

System action: The DAL is not loaded.

Operator Response: Notify support personnel.

Programmer Response: Verify the type of DAL in the data set that is being loaded.

DTM4517I

Command ABENDED SD37. Re-allocate Output Data Set.


Explanation: A JBS DEFINE ... TODSN command filed to complete. The TODSN was too small for the amount of data to be written.

System action: None.

Operator Response: None.

Programmer Response: Re-allocate the TODSN with more space and try the command again.

DTM4518I

TMSS not authorized to dataset dataset.name


Explanation:  Data set dataset.name is specified on a ThruPut Manager command. The task initiated by ThruPut Manager is not authorized to open it.

System action:  The command is not processed.

Operator Response:  Ensure to specify the correct data set name in the command.

Programmer Response:  An ICH408I message should immediately precede the DTM4518 message indicating what level of access TMSS requires. If applicable, grant the access.

DTM4550I

NO STATEMENTS WERE FLAGGED


Explanation: The Action Language statements contained no errors.

System action: Normal Termination.

Operator Response: None.

Programmer Response: None.

DTM4551I

NUMBER OF ERRORS DETECTED - nnnn HIGHEST SEVERITY CODE - scode


Explanation: The Language Processor detected syntax error(s) in the Action Language statement(s). The severity code reflects the Language Processor’s return code at termination.

System action: No internal text was created.

Operator Response: None.

Programmer Response: Correct the errors and rerun.

DTM4552I

WARNING MESSAGES ISSUED - RETURN CODE - nn


Explanation: During Action Language processing, some warning messages were issued.

S ystem Action: Processing continues.

Operator Response: None.

Programmer Response: Investigate the warnings and correct if necessary.

DTM4553I

OVERRIDING PARAMETERS - parameters


Explanation: When the Language Processor was invoked, the listed parameters were specified.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4554I

ERROR(S) DETECTED IN ABOVE PARAMETER LIST


Explanation: The parameters listed in message DTM4553I contain an error.

System action: The Language Processor terminates.

Operator Response: None.

Programmer Response: Correct the parameter list and re-run.

DTM4555I

NO EXECUTABLE type SUPPLIED


Explanation:
type: is either DAL or JAL.
The Language Processor processed the input Action Language statements successfully; however, all the input statements were comments and/or blank, or the input file was a null file.

System action: Action Language internal text is a “null” program. The Language Processor terminates with a return code of 4.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4556I

type INTERNAL TEXT NOT CREATED DUE TO ERROR(S)


Explanation:
type: is either DAL or JAL.
One or more errors were detected in the input statements.

System action: Internal text was not created, and the Language Processor terminates with a return code of 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4557I

type JAL INTERNAL TEXT REQUIRES nnnn BYTES OF STORAGE


Explanation: type: is either DAL or JAL.
This message indicates the size of the internal text.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4558I

type CREATED ON: DATE=date TIME=time


Explanation:
type: is either DAL or JAL.
date: is the date on which the internal text was created.
time: is the time at which the internal text was created.
The time and date are used as an identifier and are displayed as part of the DAL/JAL display command. This lets you verify that the active Action Language corresponds to a given DAL/JAL listing.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4559I

NULL ddname DD STATEMENT


Explanation: The ddname DD statement was coded as DUMMY or DSN=NULLFILE.
ddname: can be JALTEXT, DALTEXT, or INTERTXT.

System action: The internal text was not written.

Operator Response: None.

Programmer Response: If this was not intended, correct and rerun.

DTM4560I

ddname DATASET NAME - dsname


Explanation: If internal text is created, it is written to the identified file.
ddname: can be JALTEXT, DALTEXT, or INTERTXT.

System action: Any internal text is written to the file dsname.

Operator Response: None.

Programmer Response: None.

DTM4561I

NUMBER OF RECORDS READ FROM ddname - nnnn


Explanation:
ddname: Can be either SYSIN or SYSLIB.
nnnn: Number of statements read from the indicated ddname.
This message documents the number of input statements.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4562I

NUMBER OF RECORDS WRITTEN TO SYSPRINT - nnnn TO ddname - (iiii,ssss)


Explanation: This message documents the number of records written by the Language Processor:
ddname: can be JALTEXT, DALTEXT, or INTERTXT.
iiii: represents the number of executable internal text records.
ssss: represents the number of source text statements written.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4563I

PROCEDURE IDENTIFIER IS: type[, TYPE IS dal-type]


Explanation:
type: is either DAL or JAL.
dal-type: is the type of DAL, DCS or RSS.
DAL or JAL processing has completed, and this message identifies the type of internal text created by the Language Processor.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM4564I

*** WARNING *** OLD [DAL | JAL] COMMAND SYNTAX IS BEING USED


Explanation: An old version of a DAL or JAL statement or keyword has been detected.

System action: DAL/JAL processing continues normally.

Operator Response: None.

Programmer Response: Change the syntax to the new format, as specified in the Syntax Change Report.

DTM4565I

*** WARNING *** JBS BINDING AGENT(s) NOT DEFINED


Explanation: The JAL contains JBS ADD or JBS REPLACE statements that specify a Binding Agent that is not currently defined on the system running the Language Processor.

S ystem Action: Processing continues.

Operator Response: None.

Programmer Response: Examine JBS Binding Agent Cross Reference Report.

DTM4566I

*** WARNING *** JBS IS NOT AVAILABLE


Explanation: The JAL contains JBS ADD or JBS REPLACE statements, but they could not be verified because JBS is not active on the system running the Language Processor.

System action: Processing continues.

Operator Response: None.

Programmer Response: Ensure that JBS is active.

DTM4567I

UNABLE TO WRITE INTERNAL TEXT OVER PREVIOUS type


Explanation:
type: is the type of internal text, and is one of JAL, DCS DAL, or RSS DAL.
The Language Processor is about to write internal text to the output file, but has encountered valid DAL/JAL internal text of a different type.

System action: The Language Processor terminates with a return code of 8.

Operator Response: None.

Programmer Response: Verify that the output data set is as intended. If you want to overwrite the previous internal text, add PARM=OVERWRITE the EXEC statement before re-running.

DTM4570I

*** ERROR *** EXPECTED CONTINUATION STATEMENT NOT ENCOUNTERED


Explanation: An error was detected in the statements. End-of-file was detected instead of the expected continuation of the previous statement.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4571I

*** ERROR *** MAXIMUM NUMBER OF CONTINUATION STATEMENTS EXCEEDED - STATEMENT IGNORED


Explanation: The Language Processor limits the number of records a single statement can span to 50. A single statement has exceeded this limit, and was ignored without further syntax checking.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4572I

*** ERROR *** UNBALANCED APOSTROPHES DETECTED


Explanation: A statement has an odd number of apostrophes. If apostrophes are used, there must be an even number of them on a single statement.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4573I

*** ERROR *** TOO MANY NESTED LEVELS OF PARENTHESES


Explanation: The Language Processor limits the number of levels of parentheses that can be nested within a Boolean expression to 16. This nesting limit was exceeded.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4574I

*** ERROR *** TOO MANY RIGHT PARENTHESES


Explanation: The number of right parentheses ‘)’ on a statement exceeds the number of left parentheses ‘(‘. The number of right parentheses must always match the number of left parentheses.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4575I

*** ERROR *** TOO FEW RIGHT PARENTHESES


Explanation: The number of right parentheses ‘)’ on a statement is fewer than the number of left parentheses ‘(‘. The number of right parentheses must always match the number of left parentheses.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4576I

*** ERROR *** MAXIMUM LENGTH OF A CHARACTER STRING HAS BEEN EXCEEDED


Explanation: The Language Processor limits the number of characters in a single or quoted string to 255. This limit was exceeded.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4580I

*** ERROR *** statement-type ‘text1’ ENCOUNTERED WHEN ‘text2’ EXPECTED


Explanation: A syntax error was detected. The Language Processor found text1 when text2 was expected. statement-type is omitted for some errors.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4581I

*** ERROR *** UNKNOWN type ‘string’ ENCOUNTERED


Explanation: The Language Processor failed to recognize the element it was processing.

System action: Processing of the element is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4582I

*** ERROR *** INVALID type ‘string’ ENCOUNTERED


Explanation: The Language Processor found an invalid element.

System action: Processing of the element is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4583I

*** ERROR *** INVALID VALUE IN ‘element’


Explanation: The value specified for an element contains characters that are invalid, such as alphabetics where only numerics are allowed, or special characters not enclosed in quotes.

S ystem Action: Processing of the element is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4590I

*** ERROR *** ‘statement-type’ STATEMENT PREVIOUSLY ENCOUNTERED


Explanation: A statement of a type that must not be duplicated was encountered more than once.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4591I

*** ERROR *** MISPLACED ‘statement-type’ STATEMENT


Explanation: A statement was placed incorrectly in the input file.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4592I

*** ERROR *** ‘ENDIF’ STATEMENT MISSING


Explanation: The Language Processor found an IF statement but reached the end of the input file before finding a matching ENDIF.

System action: Processing of input terminates and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4593I

*** ERROR *** ‘IF’ STATEMENT MISSING


Explanation: The Language Processor encountered a part of an IF construction (such as an ENDIF) without a prior IF statement.

System action: Processing of input continues but the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4594I

** WARNING ** ‘statement-type’ STATEMENT FOLLOWS A TERMINATION STATEMENT


Explanation: The indicated type of JAL/DAL statement can never be executed since it immediately follows an EXIT/RETURN or END statement.

System action: Processing of DAL/JAL input continues and the return code is set to 4.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4595I

*** ERROR *** ‘IF’ CONSTRUCT ERROR DETECTED WITH ‘statement-type’ STATEMENT


Explanation: The indicated statement type has been found out of place in an IF construct. For example, an OTHERWISE statement precedes an ORIF.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4596I

*** ERROR *** TOO MANY NESTED LEVELS OF ‘IF’


Explanation: The Language Processor found more than five levels of nested IF statements.

System action: Processing of input continues. The offending IF statements are analyzed but the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4597I

*** ERROR *** PROCEDURE STATEMENT WAS NOT FIRST EXECUTABLE STATEMENT


Explanation: The PROCEDURE Action Language statement, if specified, was not the first language statement to be processed.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Move the PROCEDURE STATEMENT to the start of the Action Language source text.

DTM4598I

*** WARNING *** ENCOUNTERED 2 OR MORE CONSECUTIVE SERVICE LEVELS THAT WERE THE SAME


Explanation: The DCS SERVICE statement specified consecutive service level terms that were the same. (e.g. DCS SERVICE(...,CLAIM(5),CLAIM(1),...)).

System action: Processing of the statement continues and the return code is set to 4.

Operator Response: None.

Programmer Response: Remove or combine the redundant service level terms.

DTM4599I

*** ERROR *** LAST SERVICE LEVEL TERM SPECIFIES AN INTERVAL
WHEN ONE IS NOT EXPECTED


Explanation: The DCS statement specified a list of service levels terms. The last term was specified with an interval value. This is not allowable.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4600I

*** ERROR *** RANGE VALUE ‘string’ IS NON-NUMERIC


Explanation: A numeric range value was expected when a non-numeric string was found.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4601I

*** ERROR *** RANGE VALUE ‘range’ IS OUT OF SEQUENCE


Explanation: The range value specified was not greater than the previously defined range for that resource, or the first operand appears to be a range value and it is not 0.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4602I

*** ERROR *** INVALID SYMBOL ‘name’


Explanation: One of the rules for defining a Property name was violated. For PATTERNDEF/STRINGDEF the first character must be a ‘%’. For all other symbols the first character must be alphabetic or national. The rest of the name must be alphabetic, numeric, national, and/or underscore characters. If the characters used in the name are valid then the length exceeded the maximum.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4603I

*** ERROR *** ‘name’ PREVIOUSLY DEFINED


Explanation: The symbol name was previously defined. Each name must be unique.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4604I

*** ERROR *** STATEMENT INCOMPLETE


Explanation: A syntax error in a statement was detected. The end-of-statement was found before an ending symbol was encountered.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4605I

*** ERROR *** ‘name’ IS A RESERVED WORD


Explanation: The Property name or “strid” being defined is a reserved word.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4607I

*** ERROR *** RANGE VALUE ‘range’ EXCEEDS MAXIMUM


Explanation: The range value exceeds the maximum allowed for that Descriptor. Note that the maximum values vary from Descriptor to Descriptor.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4608I

*** ERROR *** SYNTAX ERROR


Explanation: A syntax error was detected in a statement. Either a comma is missing or was found unexpectedly.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4609I

*** ERROR *** ‘MAX’ ENCOUNTERED BEFORE THE END OF THE STATEMENT


Explanation: The MAX symbol, indicating the end of Descriptor statement, was found before the end of the statement. If MAX is specified, it must be the last symbol on the statement (excluding comments).

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4610I

*** ERROR *** INVALID CPU RANGE VALUE SYNTAX


Explanation: A range value specified on the CPU Descriptor statement has a syntax error. CPU range values can be specified as mmmmmm or mmmmmm:ss, where mmmmmm is in minutes and ss is in seconds.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4611I

*** ERROR *** MINUTE VALUE OF ‘mmmmmm’ EXCEEDS MAXIMUM


Explanation: The maximum minute range value on a CPU resource control statement was exceeded. A CPU range value must not exceed 357912:00.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4612I

*** ERROR *** SECOND VALUE OF ‘ss’ EXCEEDS MAXIMUM


Explanation: The maximum seconds range value on a CPU resource control statement was exceeded. ss must not be greater than 59 seconds.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4613I

*** ERROR *** CPU TIME RANGE VALUE ‘mmmmmm:ss’ EXCEEDS MAXIMUM


Explanation: The maximum range value specified in a CPU Descriptor statement was exceeded. A CPU resource range value must not exceed 357912 minutes and 00 seconds (i.e. 357912:00).

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4614I

*** ERROR *** RANGE VALUE “value” IS INVALID


Explanation: A $JCL_EXPDT Range statement contained an invalid date value.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun. The syntax of the date value is CCYY/DDD, where CCYY is the year (up to 2155) and DDD is the day of the year (up to 366).

DTM4615I

*** ERROR *** PREFIX RANGE DESCRIPTOR ‘descriptor’ CONTAINS AN INVALID SUFFIX


Explanation: A $UNIT_ACSnn, $UNIT_ATLnn, $VOL_ACSnn, OR $VOL_ATLnn Descriptor contains an invalid or missing value nn identifying the ACS or ATL unit.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4620I

** ERROR *** REQUIRED ‘xxxx’ MISSING


Explanation: A syntax error was detected.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4621I

*** ERROR *** ‘term’ IS NOT VALID IN AN EXPRESSION


Explanation: The term specified is not valid in an expression.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4622I

*** ERROR *** INVALID MESSAGE LENGTH


Explanation: A MSGDEF, DCS_ALERTDEF, DCS_NAGDEF, or JOB_DATADEF statement was encountered in which the total quoted string length exceeds the maximum allowed. MSGDEF, DCS_ALERTDEF, and DCS_NAGDEF statements are limited to 121 characters, and JOB_DATADEF statements are limited to 60 characters.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4623I

*** ERROR *** UNARY OPERATOR ‘¬’ ENCOUNTERED WHEN BINARY OPERATOR EXPECTED


Explanation: A syntax error was detected while parsing a Boolean expression where a NOT ‘¬’ operator was encountered after a term. Only a binary operator (i.e. an OR ‘|’ or an AND ‘&’) or a right parenthesis can follow a term within an expression.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4624I

*** ERROR *** ‘text1’ ENCOUNTERED WHEN ‘text2’ EXPECTED


Explanation: A syntax error in a Boolean expression was detected. The Language Processor expected to find what is described by text2 but text1 was found instead.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4625I

*** ERROR *** UNEXPECTED QUOTED STRING ‘string’ ENCOUNTERED


Explanation: While parsing a Boolean expression, the quoted string indicated by string was encountered. Terms within a Boolean expression must not be specified within quotes.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4626I

*** ERROR *** UNEXPECTED ‘char’ ENCOUNTERED


Explanation: char: is the character in error, either a comma (,) or colon (;).
A syntax error was detected while parsing a Boolean expression. Either a comma or a colon, as indicated by character, was found but not expected. Unless the comma or colon is contained within apostrophes and is part of an identifying pattern, it is invalid.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4627I

*** ERROR *** ‘symbol’ NOT PREVIOUSLY DEFINED


Explanation: The statement specifies a symbol that has not been defined.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4628I

*** ERROR *** NUMERIC VALUE OF ‘range’ IS OUT OF RANGE


Explanation: A maximum for a Descriptor was exceeded.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4629I

*** ERROR *** HIGH RANGE IS NOT GREATER THAN LOW RANGE


Explanation: High range must be greater than the previous range value, i.e. all range values must be specified in ascending values.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4630I

*** ERROR *** ‘keyword’ KEYWORD PREVIOUSLY ENCOUNTERED


Explanation: The same keyword was specified more than once for a given statement.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4631I

*** ERROR *** FIELD NUMBER ‘field#’ IS INVALID


Explanation: The maximum value for an accounting field number for the ACCTFLD Descriptor was exceeded. The maximum value for the accounting field number is 62.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4632I

*** ERROR *** MUTUALLY EXCLUSIVE KEYWORDS SPECIFIED


Explanation: A statement was coded with one or more mutually exclusive keywords.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4633I

*** ERROR *** VERSION INCOMPATIBILITY WITH STATEMENT nn


Explanation: The Language Processor has already determined that the DAL or JAL being processed is from a different version than that indicated by the flagged statement. Statement nn is the statement that conflicts.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Make all statements conform to the same version.

DTM4634I

*** ERROR *** symbol MAY ONLY BE USED IN THE DEFINITION SECTION


Explanation:
symbol: is a DAL/JAL descriptor that cannot appear in the logic section.

A DAL/JAL symbol was used in the logic section, but is only eligible to be used in an EVALUATE expression or a message definition.System action: The statement is not processed, and the return code is set to 8.Operator Response: None.Programmer Response: If you need to test this descriptor, code it in an expression in an EVALUATE expression.

DTM4635I

*** ERROR *** INVALID ‘descriptor’ INSERT ‘text’


Explanation: The insert for a MSGDEF, JOB_DATADEF, DCS_ALERTDEF, or DCS_NAGDEF is not a Descriptor or a Property name.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: None.

DTM4636I

*** ERROR *** INVALID MESSAGE LENGTH


Explanation: The definition of a MSGDEF or JOB_DATADEF statement contains too many elements to process successfully. The maximum number varies depending on the types of elements used.

System action: Processing of the statement is halted and the return code is set to 8

Operator Response: None.

Programmer Response: Reduce the complexity of the definition statement.

DTM4637I

*** ERROR *** INVALID ‘descriptor’ PARAMETER ‘parameter’
LENGTH=nn


Explanation: The Language Processor has detected an invalid parameter for the named Descriptor. The length is given in case there unprintable characters or the insert is truncated.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4638I

*** ERROR *** MISSING ‘parameter’ PARAMETER


Explanation: Required parameter is missing for the named Descriptor.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4639I

*** ERROR *** TOO MANY ELEMENTS IN list LIST


Explanation: A parameter list contains more than the allowed number of elements.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4640I

*** ERROR *** INVALID PATTERN FOR ‘descriptor’
LENGTH=nn PATTERN=’pattern’


Explanation: The pattern is invalid for this expression.

System action: Processing of the statement is terminated and return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4641I

*** ERROR *** PATTERN IDENTIFIER ‘patid’ NOT ACCEPTED
FOR ‘descriptor-name’


Explanation: Pattern id cannot be specified with this Descriptor.

System action: Processing of the statement is terminated and return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4642I

*** ERROR *** INVALID PATTERN. LENGTH=nn PATTERN=’pattern’


Explanation: Invalid pattern.

System action: Processing of the statement is terminated and return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4643I

*** ERROR *** ‘keyword’ KEYWORD MUTUALLY EXCLUSIVE
WITH ‘keyword’ KEYWORD ON STATEMENT nn


Explanation: Self-explanatory.

System action: Processing of the statement is terminated and return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4644I

*** ERROR *** ‘verb/keyword’ STATEMENT/KEYWORD NOT SUPPORTED


Explanation: Self-explanatory.

System action: Processing of the statement is terminated and return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4645I

** WARNING ** ‘parameter’ CHARACTER STRING TOO LONG. LENGTH
TRUNCATED to nn CHARACTERS\
Explanation: The default length attribute of a Descriptor is not correct for the built-in function because:

  • The length is greater than allowed.
  • The length plus the starting position results in a string that is out of range for the Descriptor.

System action: Return code is set to 4 and processing continues.

Operator Response: None.

Programmer Response: Analyze the situation. If required correct and rerun.

DTM4646I

*** ERROR *** ‘symbol’ IS NOT A VALID description SYMBOL


Explanation: A PATTERNDEF symbol is specified when a STRINGDEF symbol was expected, or vice-versa.

System action: Processing of the statement is terminated and return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4647I

*** ERROR *** TOO MANY ‘keyword’ KEYWORDS SPECIFIED


Explanation: A DCS_ALERTDEF statement contained more than the maximum number of allowable HEADER or FOOTER keywords.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4648I

*** ERROR *** KEYWORD keyword IS OUT OF NUMERIC RANGE


Explanation: A JOB STORE directive attempted to store data for a line numbered greater than 10.

System action: Processing of the statement is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4649I

*** WARNING *** ‘END’ STATEMENT MISSING


Explanation: Self-explanatory.

System action: Processing continues.

Operator Response: None.

Programmer Response: Ensure that the DAL/JAL is complete and that an END statement is the last executable statement.

DTM4650I

*** ERROR *** symbol NOT SUPPORTED IN THIS TYPE OF DAL


Explanation:
symbol: is a DAL/JAL descriptor that cannot be used in the type of DAL being processed.
A DAL/JAL descriptor was coded for DAL, but is not supported in the type of DAL being analyzed.

System action: The statement is not processed, and the return code is set to 8.

Operator Response: None.

Programmer Response: Remove the offending descriptor.

DTM4651I

*** ERROR *** MESSAGES CAN CONTAIN ONLY ONE “$LIST” DESCRIPTOR


Explanation: A MSGDEF statement contains more than one type of $LIST_descriptor Display Variable.

System action: The statement is not processed, and the return code is set to 8.

Operator Response: None.

Programmer Response: Modify the MSGDEF statement so that only one type of $LIST_descriptor Display Variable is used.

DTM4652I

*** ERROR *** MISSING “.AIF” STATEMENT


Explanation: The .AENDIF statement was encountered without a preceding .AIF statement.

System action: The statement is not processed, and the return code is set to 8.

Operator Response: None.

Programmer Response: Insert the missing .AIF statement or remove the extra .AENDIF statement.

DTM4653I

*** ERROR *** MISSING “.AENDIF” STATEMENT


Explanation: The .AIF statement was encountered, but the end of the DAL or JAL source was found without a encountering the matching .AENDIF statement.

System action: Processing is terminated and the return code is set to 8.

Operator Response: None.

Programmer Response: Insert the missing .AENDIF statement or remove the extra .AIF statement.

DTM4654I

*** ERROR *** MISSING/INVALID “.AIF” OPERAND


Explanation: The .AIF statement was encountered but the operand designating the type of Action Language was either missing or invalid.

System action: The statement is not processed, and the return code is set to 8.

Operator Response: None.

Programmer Response: Add or correct the operand designating the type of Action Language.

DTM4655I

*** ERROR *** NESTED “.AIF” STATEMENT


Explanation: The .AIF statement was encountered but a second .AIF statement was found without an intervening .AENDIF statement.

System action: The statement is not processed, and the return code is set to 8.

Operator Response: None.

Programmer Response: Insert the missing .AENDIF statement or remove the extra .AIF statement.

DTM4680I

SRCOUT DATASET NAME - dsname


Explanation: This message documents the data set and member name (if there is one) described by the SRCOUT DD statement.

System action: Any Action Language source text is written to the file dsname.

Operator Response: None.

Programmer Response: None.

DTM4681I

NUMBER OF SOURCE RECORDS READ FROM INTERTXT - (iiii,ssss)


Explanation: This message documents the number of records read in from the INTERTXT data set.
iiii: Number of internal text records read
ssss: Number of source text records read

System action: None

Operator Response: None.

Programmer Response: None.

DTM4682I

NUMBER OF RECORDS WRITTEN TO SYSPRINT - nnnn TO SRCOUT - nnnn


Explanation: This message documents the number of records written by the Action Language source rebuild facility.

System action: None

Operator Response: None.

Programmer Response: None.

DTM4683I

ddname DD STATEMENT MISSING


Explanation: ddname: can be JALTEXT, DALTEXT, SRCOUT or SYSPRINT.
This is a warning message indicating that one of the DD statements expected by the Language Processor was not present or was specified as a nullfile.

System action: Processing continues.

Operator Response: None.

Programmer Response: If desired, add the missing DD statement.

DTM4684I

INVALID INTERNAL TEXT HEADER ENCOUNTERED


Explanation: The Source Rebuild Facility detected an invalid internal text header record.

System action: Processing is halted and the return code is set to 8.

Programmer Response: Recreate the DAL or JAL internal text.

DTM4685I

INTERNAL TEXT DATASET DOES NOT CONTAIN SOURCE TEXT


Explanation: The ‘REBUILD’ parameter was specified on the Language Processor EXEC statement but the internal text data set does not contain the source text.

System action: Processing is halted and the return code is set to 8.

Programmer Response: Probable cause is that the Action Language was originally processed by the Language Processor with an EXEC parameter of ‘NOSOURCE’; which causes the source to be excluded from the internal text data set. Remove the ‘NOSOURCE’ parameter and reprocess the Action Language.

DTM4686I

INPUT SOURCE TEXT HAS BEEN MODIFIED


Explanation: An invalid internal text data set was detected. The source text, contained within the invalid internal text data set, was altered.

System action: Processing is halted and the return code is set to 8.

Programmer Response: Recreate the DAL or JAL internal text data set.

DTM4687I

HIGHEST SEVERITY CODE - nn


Explanation: The severity code reflects the Source Rebuild Facility’s return code at termination.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4694I

*** ERROR *** COPY CODE NOT FOUND - membername


Explanation: The membername specified on a COPY directive was not found in the PDS defined by the SYSLIB DD statement.

System action: Processing is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Ensure that the SYSLIB DD statement points to the correct PDS, and that the desired member resides in the PDS.

DTM4695I

*** ERROR *** ‘COPY’ STATEMENT NOT ALLOWED WITHIN COPY MEMBER


Explanation: The member specified by a COPY directive includes a COPY directive.

System action: Processing is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Remove the COPY directive from the member specified by the COPY directive.

DTM4696I

*** ERROR *** LENGTH OF EXPRESSION EXCEEDED INTERNAL LIMIT


Explanation: The Language Processor encountered an expression that could not be analyzed because it overflowed internal work areas.

System action: Processing of the expression is halted and the return code is set to 8.

Operator Response: None.

Programmer Response: Correct and rerun.

DTM4697E

*** ERROR *** UNABLE TO OBTAIN REQUIRED STORAGE - RC=X’rcode’


Explanation: A non-zero return code was received from a GETMAIN.

System action: The Language Processor terminates with a User 666 abend.

Operator Response: None.

Programmer Response: Increase the size of the region used to run the Language Processor.

DTM4698I

*** I/O ERROR *** jobname,stepname,devno,devtyp,ddname,op,err,bbcchhr,BSAM


Explanation: An I/O error was detected while processing the file identified in the error message.The format of this message conforms with the MVS standard error message. For a complete explanation see to MVS System Messages, message number IEA000I.

System action: Processing terminates with a return code of 16.

Operator Response: None.

Programmer Response: Correct the problem indicated by the err field and rerun.

DTM4699I


Explanation: This is an internal diagnostic message.

DTM4700I

INVALID type DATASET NAME: dsname


Explanation: type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

During initialization, TMSS found that the data set name specified on the LOAD initialization statement was invalid.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Specify the name of the data set correctly.

DTM4701I

REQUIRED type DATASET NAME NOT SPECIFIED


Explanation: type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

The LOAD initialization statement did not include a data set name.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Include a data set name on the LOAD initialization statement.

DTM4702I

INVALID type MEMBER NAME: text


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

During initialization, TMSS found that the member name included on the LOAD initialization statement was not a valid member name.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Specify the member name correctly.

DTM4703I

RIGHT PARENTHESIS EXPECTED AFTER MEMBER NAME


Explanation: During initialization, TMSS encountered a member name for the DAL, JAL, or TABLEn data set, but did not find a closing parenthesis.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Specify the member name correctly.

DTM4704I

EXPECTED type MEMBER NAME NOT SPECIFIED


Explanation:
type: is the type of data that was being processed, and can be:
• DAL for Detail Action Language.
• JAL for Job Action Language.
• TABLEn identifying a specific table.
During initialization, TMSS found that the data set was partitioned, but the LOAD initialization statement did not specify a member name.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Specify the member name correctly.

DTM4705I

INVALID KEYWORD: ‘keyword’


Explanation: Unknown keyword detected on an initialization statement.

System action: Message DTM0320I is issued.

Operator Response: See message DTM0320I.

Programmer Response: None.

DTM4706I

INVALID KEYWORD ‘keyword’ SYNTAX


Explanation: Invalid keyword syntax on an initialization statement.

System action: Message DTM0320I is issued.

Operator Response: See message DTM0320I.

Programmer Response: None.

DTM4707I

KEYWORD keyword1 CONFLICTS WITH KEYWORD keyword2


Explanation: Incompatible keywords have been specified on an initialization statement.

System action: Message DTM0320I is issued.

Operator Response: See message DTM0320I.

Programmer Response: None.

DTM4725I

RIGHT PARENTHESIS EXPECTED AFTER MEMBER NAME


Explanation: A REFRESH command was entered specifying a member name for the data set, but a closing parenthesis was not found.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM4726I

INVALID type DATASET NAME: dsname


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

The REFRESH command was entered, but the data set name specified was invalid.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM4727I

INVALID type MEMBER NAME: text


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

A REFRESH command was entered, but the member name included was not a valid member name.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None

DTM4728I

INVALID OPERAND: text


Explanation: The command could not recognize the operand text.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM4729I

INVALID POSITIONAL PARAMETER: text


Explanation: The command could not recognize the positional parameter text.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM4730I

type DISPLAY
[TYPE=dal-type] DESCRIPTION=’description’
DSNAME=dataset [MEMBER=member]
GENERATED ON DATE=date TIME=time
BY LANGUAGE PROCESSOR version release.level - #Vptf-level(lowest-level)
[LOADED] [REFRESHED] ON DATE=yyyy.ddd TIME=hh:mm:ss


Explanation:
type: is either DAL, JAL or SECONDARY JAL.
dal-type: is the type of DAL, DCS or RSS.
description: is the description coded on the PROCEDURE statement.
ptf-level: is the current PTF level for Thruput Manager.
lowest-level: is the lowest PTF level at which this JAL can load properly.
Issued in response to a DAL DISPLAY or JAL DISPLAY operator command.
Note: TYPE=dal_type displayed only for DAL DISPLAY command output.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4731I

type NOT REFRESHED. DATASET NAME NOT SPECIFIED


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

The REFRESH command was entered, but no data set name was specified.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM4732I

type NOT REFRESHED


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

The REFRESH command was entered, but the active DAL, JAL, or table was not refreshed due to previous errors.

System action: The command is ignored.

Operator Response: See previous messages documenting the error.

Programmer Response: None.

DTM4733I

type REFRESHED


Explanation:
type: is the type of data that was being processed, and can be:

  • DAL for Detail Action Language.
  • JAL for Job Action Language.
  • TABLEn identifying a specific table.

The REFRESH command was entered and processing completed successfully.

System action: The DAL, JAL, or table is replaced with the DAL, JAL, or table specified in the command.

Operator Response: None.

Programmer Response: None.

DTM4734I

EVENT ‘event-name’ HAS BEEN DELETED


Explanation: The JAL REFRESH command was entered. The new JAL does not contain the indicated event, which was present in the old version of the JAL.

System action: The indicated event has been deleted.

Operator Response: None.

Programmer Response: None.

DTM4735I

EVENT ‘event-name’ newstate PREVIOUSLY oldstate


Explanation: The JAL REFRESH command was entered. The new JAL contains the indicated event, but its status has been altered as indicated.

System action: The indicated event has been altered as shown.

Operator Response: None.

Programmer Response: None.

DTM4736I

language-type NOT LOADED


Explanation:
language-type: can be either JAL or DAL.
A DISPLAY command for the specified language type was entered, but the DAL or JAL was not loaded.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM4737I

INVALID TABLE NUMBER: n


Explanation: The function or command did not specify a table number from the range 1 to 9.

System action: The function or command is ignored.

Operator Response: If the error resulted from a TBL command, re-enter the command with a valid table number.
If the error occurred during TMSS initialization, notify support personnel.

Programmer Response: Correct the TMSS initialization parameters. The table can be loaded with the TBL REFRESH command without restarting TMSS.

DTM4738I

TABLE n: ALL SUBTABLES action
or
TABLE n: SUBTABLE: subtable-name action


Explanation: A command to enable/disable tables has completed execution.

System action: The indicated table has been enabled/disabled as shown.

Operator Response: None.

Programmer Response: None.

DTM4739I

TABLE n: action FAILED text NOT FOUND


Explanation: A command to enable/disable tables failed because the table was empty or the subtable was not found.

System action: The command is ignored.

Operator Response: Reissue command with correct parameters.

Programmer Response: None.

DTM4740I

TABLE DISPLAY:
data


Explanation: A command to display the status of tables has been issued. The information represented by data varies depending on the command options.
Some examples.
A request to display a specific table:
/TBL DISPLAY 1
 
The response:

DTM4740I TABLE DISPLAY TABLE 1: DSN=ACI001.TM.TABLES MEMBER=ACCOUNTS SUBTABLE=DEV1 SUBTABLE=DEV2 SUBTABLE=DEV3 SUBTABLE=DEV4 *DISABLED

A request to display all tables:

/TBL DISPLAY ALL
The response: DTM4740I TABLE DISPLAY TABLE 1: DSN=ACI001.TM.TABLES MEMBER=ACCOUNTS SUBTABLE=DEV1 SUBTABLE=DEV2 SUBTABLE=DEV3 SUBTABLE=DEV4 *DISABLED TABLE 2: NOT DEFINED TABLE 3: NOT DEFINED TABLE 4: NOT DEFINED TABLE 5: NOT DEFINED TABLE 6: NOT DEFINED TABLE 7: NOT DEFINED TABLE 8: NOT DEFINED TABLE 9: NOT DEFINED

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM4741I

JAL DOES NOT CONTAIN ANY BINDING AGENTS


Explanation: A JAL VERIFY AGENTS command was issued, but the specified or default JAL does not contain any JBS ADD BIND statements.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4742I


Explanation: This is an internal diagnostic message.

DTM4743I

JAL VERIFY AGENT DISPLAY
DSNAME=dsname MEMBER=member
--BINDING AGENT-- --STATUS---
agent status
... ...
JBS AGENTS: nn, DEFINED: nn, NOT-DEFINED: nn


Explanation: A JAL VERIFY AGENTS command was issued.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4744I

JAL VERIFICATION COMPLETE - ALL JBS AGENTS DEFINED


Explanation: All the agents in the JAL are defined.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM4750I

JOB CPU LIMITED TO mmmmmm:ss


Explanation: This message is issued when the system starts to execute a job that the Job Analyzer found eligible for the CPUCAP feature of the JAL statement SET.

System action: The job being executed is limited to the indicated CPU time limit.

Operator Response: None.

Programmer Response: None.

DTM4751I

JOB/STEP CPU LIMITS NORMALIZED WITH A FACTOR OF nn.nn


Explanation: This message is issued when the system starts to execute a job on a system that is eligible for CPU normalization.

System action: The requested CPU times (at both job and step levels) for the job being executed have been normalized by the indicated factor.

Operator Response: None.

Programmer Response: None.

DTM4752I

PERFORMANCE GROUP SET TO nnn


Explanation: Via JAL, the performance group for this job has been set to the specified number.

System action: The performance group is set as if the job would have requested it.

Operator Response: None.

Programmer Response: None.

DTM4753I

PERFORMANCE GROUP NUMBER nnn IS INVALID


Explanation: An attempt to set the performance group as requested in JAL has been rejected by the system.

System action: No further action is taken.

Operator Response: Note the message and inform your system support group. The job’s performance group is the default for that class of work.

Programmer Response: Identify the cause of the error. The performance group for the job can be reset with an operator command. This may be needed if the job is a long running job and it is executing in the wrong performance group.

DTM4754I

STMT nnn MODIFIED: new-keyword

or

STMT nnn BYPASSED DUE TO CHECKPOINT RESTART


Explanation:

nnn: is the number of the modified JCL statement.

new-keyword: is the text that was substituted on the DD statement.

A JCL ALTER statement for the specified DD statement was encountered in DAL. The statement was modified as shown, unless it described a checkpoint restart data set. In this case, the alteration is ignored.

S ystem Action: Processing continues with the changed value.

Operator Response: None.

Programmer Response: None.

DTM4755I

JES2 Exits may be disabled due to JCTXMASK


Explanation: The JES2 JCTXMASK field has been altered by an installation exit. This may disable Thruput Manager functionality.

System action: None.

Operator Response: None.

Programmer Response: Update JES2 exit routines to pass user flags rather than disabling the entire exit point.

DTM6000I

LOCATE FOR CONTROL FILE dsname FAILED, RETURN CODE=rc


Explanation:
dsname: is the name of the Control File.
rc: is the return code (in hexadecimal).

A LOCATE was issued for the Control File, but LOCATE failed with the indicated return code.

System action: The Control File Manager terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Make sure the Control File is properly allocated and cataloged.

DTM6001I

THE CONTROL FILE dsname DOES NOT RESIDE ON A DIRECT ACCESS DEVICE


Explanation:
dsname: is the name of the Control File.
The Control File was found on a non-DASD device.

System action: The Control File Manager terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Make sure the Control File is properly allocated and cataloged.

DTM6002I

THE CONTROL FILE dsname MUST NOT BE MULTI-VOLUME


Explanation:
dsname: is the name of the Control File.
The Control File was found to be a multi-volume file.

System action: The Control File Manager terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Make sure the Control File is properly allocated and cataloged.

DTM6003I

UNABLE TO ALLOCATE THE CONTROL FILE


Explanation: The Control File could not be allocated properly.

System action: The Control File Manager terminates.

Operator Response: Critical Situation! Notify personnel responsible for support immediately.

Programmer Response: Determine why the data set could not be allocated.

DTM6004I

THE CONTROL FILE MUST BE ALLOCATED AS CONTIGUOUS SPACE


Explanation: The Control File was found to occupy more than a single extent.

System action: The Control File Manager terminates.

Operator Response: Critical Situation! Notify personnel responsible for support immediately.

Programmer Response: Allocate the Control File in a single extent.

DTM6005I

THE CONTROL FILE HAS NOT BEEN FORMATTED


Explanation: The Control File was not properly formatted.

System action: Requests permission to COLD start the file.

Operator Response: No action required with this message.

Programmer Response: None.

DTM6006I

THE CONTROL FILE IS NOT IN VERSION 6 MODE, CONVERSION REQUIRED


Explanation: A version conflict between the Control File Manager and the Control File was encountered.

System action: Control File Manager continues initialization.

Operator Response: None.

Programmer Response: Convert the Control File to Version 6. Ensure that ALL systems sharing the Control File are at the V6 level.

DTM6007A

IS A CONTROL FILE COLD START AUTHORIZED? REPLY ‘Y’ OR ‘N’


Explanation: The Control File is about to be formatted, and a confirmation is requested.

System action: Waits for an operator response.

Operator Response: The contents of the Control File are highly critical. Before proceeding with a reformat make sure that is the desired action. Reply ‘Y’ to continue with a format of the Control File.
Reply ‘N’ to prevent the Control File from being formatted.

Programmer Response: None.

DTM6008I

CONTROL FILE COLD START AUTHORIZATION DENIED BY OPERATOR


Explanation: The operator replied ‘N’ to message DTM6007A.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6009I

NOT ENOUGH SPACE ALLOCATED FOR 64 CYLINDER CONTROL FILE


Explanation: TM needs to format the CF as 64 cylinders yet the file is allocated to be fewer cylinders. This only occurs in a cold start since the file does not grow dynamically.

System action: Message DTM6034I follows and the Control File Manager terminates.

Operator Response: Notify personnel responsible for support.

Programmer Response: Allocate 64 cylinders for the Control File. See to the “FILE Section” in the System Programming Guide: Base Product.

DTM6010I

THE CONTROL FILE CONTROL RECORD IS INVALID


Explanation: The Control File contains an invalid Control Record.

System action: The Control File Manager terminates.

Operator Response: This is a critical situation. Notify personnel responsible for support immediately.

Programmer Response: Determine why the Control Record was invalid.

DTM6011I

THE CONTROL FILE cf-dsname IS NOT COMPATIBLE WITH THIS RELEASE OF
ThruPut Manager


Explanation: The Control File and the Thruput Manager are not at the same level.

System action: The Control File Manager terminates.

Operator Response: Ensure that the correct level of Thruput Manager is being started.

Programmer Response: None.

DTM6012I

THE CONTROL FILE COMPONENT HAS BEEN ACTIVATED


Explanation: The Control File is available for processing.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6013I

CONTROL FILE MANAGER SHUTDOWN COMPLETE


Explanation: The Control File Manager is no longer available for processing.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6014E

THE CONTROL FILE IS IN VERSION 4 MODE, VERSION 3 MODE REQUESTED.


Explanation: The Control File is at the Version 4 level, but the CFV3 parameter was specified on the TM MODE initialization statement.

System action: The Control File Manager terminates.Operator Response: Notify personnel responsible for support.

Programmer Response: Remove the CFV3 parameter or cold start the Control File.

DTM6015I

SYSTEM sys-id ON NODE node-name MAY BE DOWN


Explanation:
sys-id: is a system identifier.
node-name: is a JES2 node name.
The named system has not updated the Control File within the limit specified by the JES2 initialization parameter SYNCTOL.

System action: If Thruput Manager on the indicated system is not active, the Control File Manager attempts to reconcile the Control File. This message is re-issued periodically until a $EMEMBER(member) has been issued for the failed system or the failed system is restarted.

Operator Response: If the message persists after a $EMEMBER(member) has been issued or the failed system has been restarted, then Thruput Manager is active but not processing the Control File. Determine what is wrong with Thruput Manager on the indicated system.

Programmer Response: None.

DTM6016I

THE CONTROL FILE IS dsname ON volser


Explanation: This message confirms that the Control File Manager has located the Control File.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6017I

CONTROL FILE FORMAT WRITE ERROR DETECTED


Explanation: During a format of the Control File, a WRITE error was detected. This, normally, is some type of device error.

System action: The Control File Manager terminates.

Operator Response: This could be a critical situation. Notify personnel responsible for support.

Programmer Response: Determine the causes. Allocate the file on another device.

DTM6018I

WARNING - component-name NOT ENABLED


Explanation:
component-name: is the affected Thruput Manager component.
The indicated component has not been activated by the Control File Manager.

System action: Initialization continues.

Operator Response: This could be critical depending on the component. Contact personnel responsible for support immediately.

Programmer Response: Determine why the indicated component has not been activated.

DTM6019I

component-name COMPONENT ATTACH FAILED


Explanation:
component-name: is the affected Thruput Manager component.
The Control File Manager could not ATTACH a component.

System action: This could be critical depending on the component. Control File Manager continues processing, but requests for the indicated component are ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Determine why the ATTACH failed.

DTM6020I

task-id text


Explanation:
task-id: JES2 job ID.
text: is an explanation of the discrepancy between the Control File and the JES2 information.
The Control File Manager has encountered a discrepancy between the information in the Control File and the information from JES2 for the indicated job.

System action: The Control File Manager attempts to reconcile the discrepancy.

Operator Response: If no previous system failure has occurred notify personnel responsible for support.

Programmer Response: Determine if the discrepancy has resulted from a system failure. If this is not the cause, contact BMC Support.

DTM6021I

component-name COMPONENT IS NOT RESPONDING


Explanation:
component-name: is the affected Thruput Manager component.
The Control File Manager has not received a response from the indicated component.

System action: The component is shut down then the Control File Manager continues processing.

Operator Response: This could be critical depending on the component. Notify personnel responsible for support immediately.

Programmer Response: Determine why the affected component is not responding.

DTM6022I

component-name COMPONENT SUCCESSFULLY RECOVERED


Explanation:
component-name: is the affected Thruput Manager component.
The indicated component has failed and the Control File Manager has recovered successfully.

System action: None.

Operator Response: This message is associated with message DTM6023I.

Programmer Response: This message is associated with message DTM6023I.

DTM6023I

component-name COMPONENT RECOVERY IN PROGRESS


Explanation:
component-name: is the affected Thruput Manager component.
The indicated component has failed and the Control File Manager is attempting recovery.

System action: The request that caused the failure is rejected.

Operator Response: Notify personnel responsible for support.

Programmer Response: Determine why the component is failing.

DTM6024I

component-name LOAD FAILED FOR COMPONENT MODULE module-name -
FUNCTION WILL NOT BE SUPPORTED


Explanation:
component-name: is the affected Thruput Manager component.
module: is the module that could not be loaded.

System action: The request that caused the failure is rejected.

Operator Response: This could be critical depending on the component. Notify personnel responsible for support immediately.

Programmer Response: Determine why the component is failing.

DTM6025I

XAM I/O ERROR
jobname,stepname,devno,devtyp,ddname,op,err,bbcchhr,BSAM


Explanation: An I/O error was detected while reading the Automation File, the Application Management Database, or the Control File.
The format of this message conforms with the MVS standard error message. For a complete explanation see to MVS System Messages, message number IEA000I.
See accompanying messages for information on the affected file.

System action: Affected function terminates.

Operator Response: This could be critical depending on the component. Notify personnel responsible for support.

Programmer Response: Diagnose and correct the I/O error.

DTM6026I

CONTROL FILE LOCKOUT

or

Control File Lockout, held by jobname on sysname


Explanation: The Control File Manager could not get exclusive use of the Control File. In the second form of the message, jobname indicates the name of the job which currently holds the Control File and sysname indicates the name of the system where the job is executing.

System action: No further Control File processing occurs until the file becomes available.

Operator Response: Ensure that all systems sharing the Control File in the MAS complex are running properly. If all systems seem to be in order, notify personnel responsible for support.

Programmer Response: Determine why the Control File is unavailable.

DTM6027I

FORMATTING ThruPut Manager CONTROL FILE dsname ON VOLUME volser


Explanation:
dsname: is the name of the Control File.
volser: is the serial number of the volume containing the Control File.
This message documents the location of the Control File that is being formatted.

System action: Formats the Control File.

Operator Response: None.

Programmer Response: None.

DTM6028I

ThruPut Manager IS RECONCILING application-name -
ON sys-id ON node-name


Explanation:
sys-id: is a system identifier.
node-name: is a JES2 node name.
This message is issued whenever the Control File Manager is started, and at certain other times.

System action: The status of the jobs contained in the Control File is synchronized with the status of the jobs as understood by JES2.

Operator Response: None.

Programmer Response: None.

DTM6029I

RECONCILIATION OF application-name - ON sys-id ON node-name IS COMPLETE


Explanation:
application-name: The name of the application. This is shown only when a given application is being reconciled.
sys-id: is a system identifier.
node-name: is a JES2 node name.
This message is issued after the Control File Manager completes synchronization of the Control File with JES2.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6030I

CRITICAL RESOURCE SHORTAGE


Explanation: The Control File Manager has exceeded Control File limits.

System action: Requests for Control Manager services are rejected until the shortage is alleviated.

Operator Response: If the problem persists, notify personnel responsible for support.

Programmer Response: Notify BMC Support personnel.

DTM6031I

CONTROL FILE MANAGER SHUTDOWN IN PROGRESS


Explanation: The Control File Manager is terminating as a result of a request to shut down.

System action: Terminates the Control File Manager.

Operator Response: None.

Programmer Response: None.

DTM6032I

CONTROL FILE MANAGER IS TERMINATING


Explanation: The Control File Manager is terminating as a result of an abnormal condition.

System action: Terminates the Control File Manager.

Operator Response: Notify personnel responsible for support.

Programmer Response: See previous messages documenting the nature of the error.

DTM6033I

RECONCILIATION OF sys-id ON node-name CANNOT BE PERFORMED BY THIS ThruPut Manager


Explanation:
sys-id: is a system identifier.
node: is a JES2 node name.
A request to reconcile the Control File Manager was issued from a system that is not part of the MAS complex sharing the Control File.

System action: The request is ignored.

Operator Response: Enter the request from an eligible system.

Programmer Response: None.

DTM6034I

CONTROL FILE dsname ON VOLUME volser FORMAT FAILED RC=nn


Explanation:
dsname: is the name of the Control File.
volser: is the volume serial number of the volume containing the control data set.
nn: Indicates the cause of the failure.

An attempt was made to format the Control File, but there was an error. This situation can be caused by one of three reasons:

  • Insufficient space. If that is the case this message is preceded by message DTM6009I.
  • The address space has insufficient storage. The return code value is 8.
  • Internal Logic. The return code is not 8 and message DTM6009I did not precede this message.

System action: The format attempt is terminated.

Operator Response: Notify personnel responsible for support.

Programmer Response: Take the appropriate action depending on the error:

  • For insufficient space: Reallocate a larger file.
  • For insufficient memory: Increase the memory for Thruput Manager address space.
  • Internal error: Notify BMC Support personnel.

DTM6035I

ThruPut Manager CONTROL FILE dsname ON VOLUME volser FORMATTED


Explanation:

dsname: is the name of the Control File.

volser: is the volume serial number of the volume containing the control data set.

The indicated file has been formatted as a Control File.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6036I

component-name COMPONENT RECORD IS BEING FORMATTED


Explanation:
component-name: is the affected Thruput Manager component.
This message is issued whenever a Thruput Manager component is started for the first time using the Control File Manager, or whenever the Control File is formatted.

System action: The component’s Control File record is formatted.

Operator Response: None.

Programmer Response: None.

DTM6037I

component-name COMPONENT RECORD SUCCESSFULLY FORMATTED


Explanation:
component-name: is the affected Thruput Manager component.
The indicated component has successfully formatted its record in the Control File.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6038A

THE CONTROL FILE IS IN VERSION 3 MODE, CONFIRM CONVERSION TO VERSION 4 MODE. REPLY ‘Y’ OR ‘N’


Explanation: The Control File has not been converted, and the CFV3 parameter has not been specified.

System action: If the operator grants permission, the Control File will be converted. If permission is denied, the Control File is not converted and processing continues in Version 3 mode.

Operator Response: Reply ‘Y’ to convert the Control File. Reply ‘N’ to continue with a Version 3 Control File. Do not reply ‘Y’ unless you are sure that all systems sharing the Control File are at the 4.1 level.

Programmer Response: Ensure that ALL systems sharing the Control File are at the 4.1 level before allowing the Control File to be converted.

DTM6039A

SPECIFY ‘C’ TO CREATE A NEW NODE,
‘R’ TO RENAME AN EXISTING NODE, ‘T’ TO TERMINATE
THE CONTROL FILE MANAGER


Explanation: This message follows message DTM6044I where a list of existing node ids in the Control File is shown. The id of the node for the starting system is also shown. Here the operator is prompted for one of three actions:

  • If the node is new, then reply ‘C’.
  • If the node is not new, but it appears new because one of the elements used to form the node id has been altered, then reply ‘R’.
  • If the situation is unexpected, then the appropriate action may be to terminate the Control File Manager by replying ‘T’.

NOTE: The node id is formed from the following elements:

  • JES2 node name
  • Spool data set name
  • Spool volume prefix

If you have altered any of the above elements for your system, message DTM6044I will be generated since no matching node id will be found.

System action: The system takes one of the following actions:

  • If the reply is ‘C’, then a new node id is added to the control file. This new “node” is empty of Thruput Manager jobs, since it has just been created.
  • If the reply is ‘R’, then the operator is prompted for the node to be renamed via message DTM6045A. Once a node is given to be renamed, the Control File Manager will then reconcile the jobs (if any) present in the Control File for the node just renamed with the jobs present (if any) in the JES2 spool file.
  • If the reply is ‘T’, then the Control File Manager terminates.

Operator Response: If the node is truly new, reply ‘C’. If it appears new to Thruput Manager because one of the elements comprising the node id has been changed, then reply ‘R’. Only under exceptional circumstances you should reply ‘T’.
NOTE:To restart this component you must restart TMSS. If you run without the Control File Manager the services of critical components such as JBS, or JCS are not available.
Unless you were previously notified of the change by your technical support group, you should inform them of the occurrence of this message and the option you selected.

Programmer Response: Ensure that the response was appropriate.

DTM6040I

component-name COMPONENT SHUTDOWN IN PROGRESS


Explanation:
component-name: is the affected Thruput Manager component.
As a result of an operator command, the Control File Manager has issued a shutdown request for the indicated component.

System action: The component is terminated.

Operator Response: None.

Programmer Response: None.

DTM6041I

component-name COMPONENT SHUTDOWN COMPLETE


Explanation:

component-name: is the affected ThruPut Manager component.The indicated component has been terminated normally.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6042I

component-name COMPONENT SUBTASK ABENDED


Explanation:
component-name: is the affected ThruPut Manager component.
The indicated component has terminated abnormally.

System action: Continues processing, but requests for this component are rejected.

Operator Response: This could be a critical situation. Notify personnel responsible for support immediately.

Programmer Response: See previous messages documenting the nature of the error.

DTM6043I

JES2 IS NOT RESPONDING - additional-information

Explanation: The Control File Manager has requested a service from JES2, and the interval allowed for JES2 to
respond has expired.

System action: Notifies the component making the request that an error has occurred.

Operator Response: Notify personnel responsible for support.

Programmer Response: Determine why JES2 cannot service the Control File Manager requests.

DTM6044I

NODE NOT FOUND IN CONTROL FILE. NODE
IDENTIFICATION IS
‘node-name/dsname-of-spool/JES2-volser-prefix’
EXISTING NODES ARE
nn IS ‘node-name/dsname-of-spool/JES2-volserprefix’
[active]
TIME OF LAST CONTROL FILE UPDATE: mmm dd.ccyy AT
hh:mm
TIME OF LAST JES2 COLD START: mmm dd.ccyy AT
hh:mm

Explanation: No matching node has been found in the Control File. This occurs the first time a node is “seen” by the Control File Manager, or when you have altered any of the elements used to form a node identification.

System action: If there are less than 16 node ids in the Control File message DTM6039A follows, giving the operator the opportunity to create a new node or reuse and existing one that is not active. If the Control File has already reached the maximum of 16 nodes, then message DTM6045A follows, giving the operator the opportunity to reuse and existing one.

Operator Response: None.

Programmer Response: None.

DTM6045A

ENTER THE NUMBER OF THE NODE TO BE RENAMED, OR
‘T’ TO TERMINATE THE
CONTROL FILE MANAGER

Explanation: This message follows:

  • Message DTM6039A when there are less than 16 nodes already defined to the Control File Manager and the
    operator has chosen to rename an existing node.
  • Message DTM6044I when more nodes cannot be defined because the limit of 16 has already been reached.

The operator is prompted for one of two actions:

  • A node number of the form nn to be renamed.
  • ‘T’ to terminate the Control File Manager.

System action: If a replacement node number is given, the new node replaces the old inactive node and
processing continues. If the reply is ‘T’ processing is terminated.

Operator Response: Either choose a node to be replaced from the list provided with message DTM6044I or
type ‘T’ to terminate processing.

Programmer Response: None.

DTM6046I

application-name ON SYSTEM smfid/sysid ON NODE
node-name
MAY STILL BE ACTIVE


Explanation: A request to cold start the named application has been made and the application may be active
on another system.

System action: Message DTM6045A is issued requesting permission to cold-start the named application.

Operator Response: None.

Programmer Response: None.

DTM6047I

SYSTEM smfid/sysid ON NODE node-name
MAY STILL BE ACTIVE


Explanation: A request to cold start the Control File has been made but a system may still be active.

System action: Message DTM6007A is issued requesting permission to cold-start the Control File.

Operator Response: None.

Programmer Response: None.

DTM6048A

IS FORMATTING OF THE ‘application-name’
COMPONENT AUTHORIZED?
REPLY ‘Y’ OR ‘N’


Explanation: A request has been made to cold start the named application. Operator’s permission is requested.

System action: If the reply is ‘Y’, the Control File Manager reformats the Control File area associated with the named application. If the reply is ‘N’ the request is cancelled and message DTM6049I is issued.

Operator Response: Give appropriate response.

Programmer Response: None.

DTM6049I

FORMATTING OF THE ‘application-name’ COMPONENT
DENIED BY OPERATOR


Explanation: The operator responded ‘N’ to message DTM6048A.

System action: Processing of the request is terminated.

Operator Response: None.

Programmer Response: None.

DTM6050I

‘application-name’ HAS BEEN INACTIVATED DUE TO
ERRORS

Explanation: The named application is no longer operational because of the errors encountered.

System action: The system stops processing requests for the named application.

Operator Response: Notify personnel responsible for support.

Programmer Response: Analyze the situation. See messages preceding this one.

DTM6051I

‘application-name’ FAILED DURING ‘function-name’
PROCESSING,
COMPONENT NOW INACTIVE

Explanation: The named application failed processing a function request.

System action: Processing continues, but Control File requests for that component are rejected.

Operator Response: Notify personnel responsible for support.

Programmer Response: Make sure that the indicated component is started properly.

DTM6052I

THE CONTROL FILE’S CONTROL RECORD IS nn% FULL
or
THE application CF AREA IS nn% FULL
application: is the application whose Control File area is
approaching full capacity, e.g. JBS, DCS, RSS, etc.

Explanation: This message is issued when the control record utilization is at 85%, 90%, 95%, 97%,...

System action: This is a warning message. When the Control File control record or an application’s area in the Control File becomes full, no new jobs can be processed. When usage falls below 85%, this message is deleted and message DTM6053I is issued.

Operator Response: Normally this is caused by some unusual load conditions. If there are jobs that can be deleted from the system, purge them and see if this relieves the shortage. Notify personnel responsible for support.

Programmer Response: Analyze the situation. If no unusual load conditions are present, contact BMC Support.

DTM6053I

CRITICAL CONTROL FILE STORAGE SHORTAGE RELIEVED
or
CRITICAL SHORTAGE IN THE application CF AREA
RELIEVED
application: is the application whose Control File area is
approaching full capacity, e.g. JBS, DCS, RSS, etc.

Explanation: This message is issued after DTM6052I. It indicates that the control record usage, or that of an
application’s area in the Control File, has fallen below 85%.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM6054I

THE CONTROL FILE RESIDES ON VOLUME volser WHICH
IS NOT
CURRENTLY ‘ONLINE’

Explanation: The Control File Manager has determined the volume where the Control File resides is not online. The volume serial number shown is from the catalog entry for the Control File. The name of the Control File is specified in the FILE CF initialization statement.

System action: Message DTM6032I is issued indicating that the Control File Manager cannot continue processing. TMSS initialization continues but the functions provided by the Control File Manager are not
available (JBS, JLS, JCS, ...). This is a critical situation that should be corrected as soon as possible. NOTE: To restart the Control File Manager component you must restart TMSS.

Operator Response: If the volume should be online, determine why it is not online and correct the situation as soon as possible. If the data set that the Control File Manager is attempting to access is incorrect notify your technical support personnel.

Programmer Response: Modify the FILE CF initialization statement to point to the correct Control File.

DTM6055A

NODE SPECIFIED IS MARKED ACTIVE. REPLY ‘Y’ TO
CONTINUE WITH RENAME, OR ‘N’ TO SPECIFY
ALTERNATE NODE OR TERMINATE

Explanation: This message follows DTM6045A. The node specified to be renamed is marked active. When ThruPut Manager terminates normally for all systems in a particular JES2 node, then the node is marked
inactive. In situations where ThruPut Manager termination process does not complete (e. g. the system is reset before termination is completed) the node will still show as active.

System action: If the reply is ‘Y’ the node is renamed. If the reply is ‘N’ the prompting process starts again with message DTM6045A.

Operator Response: If the node is truly inactive, then you can reply ‘Y’. Otherwise reply ‘N’ so you can choose an alternate node or terminate the process.

Programmer Response: None.

DTM6056I

CFM IN DIAGNOSTIC MODE, JES2 NOT RESPONDING


Explanation: The Control File Manager has not received a response from JES2 for one minute. Control File Manager cannot continue.

System action: CFM releases the Control File, enters diagnostic mode, and monitors the JES2 interface until a response is received.

Operator Response: Check JES2 status. Enter a simple JES2 command such as $DA. If JES2 does not respond, check for error messages.

Programmer Response: Determine why JES2 is not responding. This is a possible CKPT problem or extended ENQ contention. DDR SWAP for a tape can affect JES2 if a $SPRTn command is pending.

DTM6057I

CFM DIAGNOSTIC MODE COMPLETE, JES2 RESPONDING


Explanation: The Control File Manager has returned to normal operating mode from diagnostic mode.

System action: CFM reserves the Control File and performs a reconciliation. Processing continues.

Operator Response: None.

Programmer Response: Determine why JES2 was not responding. This is a possible CKPT problem or extended ENQ contention. DDR SWAP for a tape can affect JES2 if a $SPRTn command is pending.

DTM6058A

IS FORMATTING OF THE AMBIENT NODE AUTHORIZED? REPLY ‘Y’ OR ‘N’


Explanation: Thruput Manager is being started with the CF=FORMAT(NODE) parameter and authorization is required before the information relating to the ambient node is formatted.

System action: Awaits operator response.

Operator Response: Reply Y to allow the node to be formatted, or N to cancel the request.

Programmer Response: None.

DTM6059I

WARNING - CONTROL FILE CONTAINS ONE OR MORE OUT OF RANGE NODE ENTRIES


Explanation: This is an internal diagnostic message.

DTM6060I

THE CONTROL FILE IS IN version MODE


Explanation: This message indicates which version of the Control File is in use. The control file structure reflects a previous version of Thruput Manager.
version: Is the version of the Control File.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6061I

JHE DATA SPACE CANNOT BE UPDATED. ALL JHDV ARE IN-USE


Explanation: Job Hold Information (JHDV) cannot be updated because there are no free JHDVs. Functions which depend on the currency of the JHDV (e.g. SLM) might not work properly.

System action: Message is deleted when one or more of the JHDV are released.

Operator Response: Notify personnel responsible for support.

Programmer Response: Report this problem to BMC Support.

DTM6070I

component initialization failed, reason


Explanation: Initialization of the specified component failed.

—component: is the component for which initialization failed.

Control File indicates initialization of the Thruput Manager Control File.

reason indicates why initialization failed.Other system(s) using XCF_Notepad indicates that one or more Thruput Manager started tasks in the JES2 MAS are currently using XCF_Notepad.

—XCF_Notepad indicates that initialization of the Thruput Manager XCF_Notepad failed.

reason indicates why initialization failed.

Only supported at z/OSV2R1 or higher indicates that the operating system must be a minimum of z/OSV2R1.

TM/AE is not installed indicates that TM/AE is required.

CFRM policy does not support Notepad indicates that the Coupling Facility Resource Manager (CFRM) policy does not have definitions for the necessary structures.

Insufficient space in structure indicates that a new Notepad could not be created because there was no coupling facility structure suitable for it.

IBM Notepad Services are not available indicates that Notepad Services are not availble. Thruput Manager will continue, using the Control File.

SAF authorization failed indicates that the Security Authorization Facility has denied access to resource “IXCNOTE.$$TM.JES2”.

System action: Thruput Manager initialization continues.

Operator Response: Inform person responsible for support.

Programmer Response: TM AE is required for XCF_Notepad support. Otherwise, see XCF_Notepad install guide for help in defining the necessary Coupling Facility structures.

DTM6071I

CIXCNOTE Request=request, Reqtype=reqtype failed,R15=rc, R0=rs, XCF_Notepad paused


Explanation: Indicates potential problem with Notepad facility.
The IXCNOTE request failed with the indicated return code, reason code.
In the message text:
request: indicates the associated IXCNOTE REQUEST.
reqtype: indicates the associated IXCNOTE REQTYPE.
rc: indicates the associated IXCNOTE return code.
rs: indicates the associated IXCNOTE reason code.

System action: The XCF_Notepad is paused until such time as the problem is resolved.

Operator Response: None.

Programmer Response: None.

DTM6072I

I/O error on Control File cfname, continuing with XCF_Notepad only


Explanation:
cfname: indicates the data set name of the Control File.
Indicates that there is a problem with the Control File. While writing data to the Control File, an I/O error was detected. Since the data is simultaneously being written to the XCF_Notepad, the Thruput Manager started task continues processing.

System action: Data is no longer written to the Control File.

Operator Response: Notify personnel responsible for support.

Programmer Response: None.

DTM6073A

Do you wish to attempt to rebuild the Control File from the XCF_Notepad? Reply "Y" or"N"


Explanation: Prompt to affirm rebuild of the Control File from the XCF_Notepad. During Control File Manager initialization, an unformatted Control File was detected (see related message DTM6005I). Since the XCF_Notepad is acting as backup to the Control File, it can be used to rebuild the Control File.

System action: Wait for operator reply.

Operator Response: Reply "Y" to rebuild the Control File from the XCF_Notepad. If the operator replies "N", he will be prompted to confirm a Cold Start of the Control File with message DTM6007A.

Programmer Response: None.

DTM6074I

Control File rebuild from the XCF_Notepad was successful


Explanation: During Control File Manager initialization, an unformatted Control File was detected (see related messages DTM6005I and DTM6073A). Since the XCF_Notepad is acting as backup to the Control File, it was used to rebuild the Control File.

System action: Control File Manager initialization continues.

Operator Response: None.

Programmer Response: None.

DTM6075I

I/O error on Control File “dsname”, recycling to switch to Alternate


Explanation: An I/O error was detected while writing to the Thruput Manager Control File indicated in the message by “dsname”. Since an Alternate was provided by a “FILE CF” initialization statement, it has been automatically put into use.

System action: The Control File task was recycled. Other Thruput Manager(s) in the same Jesplex are notified of the switch so that they may recycle as well.

Operator Response: None.

Programmer Response: One of the following must eventually be done:

  • Delete and re-allocate the data set which had the write error. Restart all Thruput Manager stc(s) in the Jesplex.
  • Update the Thruput Manager “FILE CF” initialization statement to use the data set name provided as the Alternate. Otherwise, a restart of the Thruput Manager started task will use the data set which had the write error.

DTM6076I

Locate for Alternate Control File altcfname failed. Return code=rc


Explanation: A "FILE CF" initialization statement specified an Alternate Control File. During initialization of the Thruput Manager started task, it attempted to obtain catalog information for the Alternate Control File but the CAMLST LOCATE failed. In the message text:
altcfnam indicates the data set name of the Alternate Control File
rc indicates the CAMLST LOCATE return code

System action: The Thruput Manager started task terminates.

Operator Response: None.

Programmer Response: Ensure that the name of the Alternate Control File was specified correctly and that it is cataloged in an OS catalog.

DTM6077I

I/O error on Control File “dsname”, recycling to switch to Duplex


Explanation: An I/O error was detected while writing to the Thruput Manager Control File indicated in the message by “dsname”. As a duplex CF was provided by a “FILE CF” initialization statement, it has been automatically put into use.

System action: The Control File task was recycled. Other Thruput Managers using the same Control File are notified of the switch, so that they may recycle as well.

Operator response: None.

Programmer response: Perform one of the following tasks:

  • Delete and re-allocate the data set which had the write error. Restart all Thruput Manager stcs in the Jesplex.
  • Update the Thruput Manager “FILE CF” initialization statement to use the data set name provided as the Duplex. Otherwise, a restart of the Thruput Manager started task will use the data set which had the write error.

DTM6078I

DUMP SUPPRESSED BY DAE


Explanation:  ThruPut Manager detected an application not responding and attempted to take a system dump. DAE detected that this dump had already been taken and it was suppressed.

System action: None

Operator response: None .

Programmer response:   None

DTM6100I

INVALID CF DATASET NAME: dsname


Explanation: During initialization, TMSS found that the data set name specified on the FILE CF initialization statement was invalid.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Specify the name of the CF data set correctly.

DTM6101I

REQUIRED CF DATASET NAME NOT SPECIFIED


Explanation: The FILE CF initialization statement did not include a data set name.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Include a data set name on the FILE CF initialization statement.

DTM6102I

INVALID SYNTAX IN THE ‘keyword’ KEYWORD ON THE CF STATEMENT


Explanation: During initialization, TMSS detected a syntax error in the indicated keyword of the FILE CF initialization statement.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the keyword in error.

DTM6103I

INVALID CF STATEMENT KEYWORD SYNTAX: text


Explanation:
text: is up to 20 characters of the text in error. During initialization, TMSS found invalid characters in the FILE CF statement where a keyword was expected.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the FILE CF initialization statement.

DTM6104I

INVALID CF STATEMENT KEYWORD: keyword


Explanation: During initialization, TMSS encountered an unknown keyword or abbreviation.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the FILE CF initialization statement.

DTM6105I

THE keyword KEYWORD VALUE ON THE CF STATEMENT IS NOT NUMERIC: value


Explanation: During initialization, TMSS encountered a non-numeric value where a numeric value is required.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the FILE CF initialization statement.

DTM6106I

THE keyword KEYWORD VALUE ON THE CF STATEMENT IS OUT OF RANGE: value


Explanation: During initialization, TMSS found that the value specified for keyword was not within the allowed range.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the FILE CF initialization statement.

DTM6107I

THE keyword KEYWORD ON THE FILE CF STATEMENT HAS BEEN SPECIFIED MORE THAN ONCE


Explanation: During initialization, TMSS found that the indicated keyword was specified more than once.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Remove the duplicate keyword.

DTM6108I

CONTROL FILE OPTIONS:
DSN=dsname ON volser
[DUPLEX=duplexdsname - duplexstatus] 
MINDORM MAXDORM MINHOLD MAXHOLD RHOLD [XCF_NOTEPAD]
nnnn nnnnn nnnnn nnnn state [notestate]
[NOTEPAD=notepadname]
[DESCRIPTION=notepaddescription]


Explanation:

  • duplexstatus: indicates whether the duplex is active, inactive or was active but has terminated on this system.
  • state: reflects whether JBS and JLS jobs are held by removing their affinity, and is either ON or OFF.
  • notestate: is only displayed with TM/AE. It reflects whether the XCF_NOTEPAD has been selected and, is either ON or OFF.
  • notepadname: is only displayed with TM AE when the XCF_NOTEPAD has been selected. It displays the name of the Notepad and is typically $$TM.JES2.ccyyddd.hhmmssth where ccyyddd.hhmmssth is the date and time of the last cold-start of JES2.
  • notepaddescription: is only displayed with TM AE when the XCF_NOTEPAD has been selected. It displays the 32 character descriptive text associated with the Notepad when it was created. This display is issued in response to a CFM DISPLAY or CFM SET command, and shows the current settings for the Control File parameters.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6109I

Explanation: This is a display of CFM statistics intended for diagnostic purposes.

DTM6112I

NODE node NOT DEFINED IN CONTROL FILE


Explanation:

node: is either the node name or node number, as specified in the command.

A CFM DISPLAY NODE or CFM DELETE NODE command was entered, but the specified node is not defined in the Control File.

System action: The command is ignored.

Operator Response: Check that the correct node name or number was entered.

Programmer Response: None.

DTM6113I

CONTROL FILE NODE DISPLAY
NN NAME ACTIVE SPOOL DSNAME AND VOLUME PREFIX
== ==== ====== ==============================
nn name status spool-dsname, spool-prefix


Explanation:
nn: is the number assigned by ThruPut Manager to the node.
name: is the JES2 node name.
status: indicates the status of the node, and is one of:

  • NO indicating the node is currently marked INACTIVE.
  • YES indicating that the node is currently marked ACTIVE.
  • ??? indicating that the node is marked ACTIVE but has not been updated in the previous 24 hours, indicating that the actual status is probably INACTIVE.

This is the display produced by entering the CFM DISPLAY NODE command.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6114A

SPECIFY “Y” TO CONFIRM DELETE OF NODE nn name/spool-dsname/spool-prefix, status


Explanation:
nn: is the number assigned by Thruput Manager to the node.
name: is the JES2 node name.
status: indicates the status of the node, and is one of:

  • NO indicating the node is currently marked INACTIVE.
  • YES indicating that the node is currently marked ACTIVE.
  • ??? indicating that the node is marked ACTIVE but has not been updated in the previous 24 hours, indicating that the actual status is probably INACTIVE.

A CFM DELETE NODE command was entered, and a confirmation of the request is required.

System action: Awaits operator response.

Operator Response: Reply Y to delete the node, or N to deny the request.

Programmer Response: None.

DTM6115I

DELETE OF NODE nn COMPLETE
or
DELETE OF NODE nn BYPASSED AT OPERATOR REQUEST


Explanation:
nn: is the node number that was entered in the CFM DELETE NODE command.
This confirms the action taken after a response to DTM6114A.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6116E

RESOURCEHOLD NOT POSSIBLE, JES2 NOT IN OS/390 R4 MODE


Explanation: A CFM SET RESOURCEHOLD(ON) command was issued, but at least one of the systems in the JES2 node is not at the level needed to support RESOURCEHOLD.

S ystem Action: The command is ignored.

Operator Response: None.

Programmer Response: Ensure all systems in the JES2 node are running OS/390 R4 mode before attempting to use RESOURCEHOLD.

DTM6117E

RESOURCEHOLD NOT POSSIBLE, SUPPORT NOT ON ALL IMAGES


Explanation: A CFM SET RESOURCEHOLD(ON) command was issued, but at least one of the Thruput Manager images sharing the Control File is not at the level needed to support RESOURCEHOLD.

System action: The command is ignored.

Operator Response: None.

Programmer Response: Ensure all Thruput Manager images sharing the Control File are running at the correct level before attempting to use RESOURCEHOLD.

DTM6118I

‘MINHOLD’ AND ‘MAXHOLD’ CANNOT BOTH BE SPECIFIED


Explanation: The CFM SET command has been entered specifying both the MINHOLD and the MAXHOLD keyword, only one is allowed.

System action: The command is ignored.

Operator Response: Reenter the command specifying either MINHOLD or MAXHOLD.

Programmer Response: Determine which Control File strategy to use. The MAXHOLD strategy should only be used on “quiet” systems. MAXHOLD strategy allows a “quiet” system to participate in the CFPLEX with minimal impact on the other systems while still remaining responsive if occasional Control File activity is required.

DTM6119I

Redriving dislays using live information from JES2


Explanation: This message is issued as part of the batch “TM Display LEVEL” command (DTMTMLVn) when Thruput Manager has been installed on the system. It indicates that the displays that follow use Thruput Manager system information. If the information presented differs from the information presented in the preceding displays, additional commands may be required to activate the Thruput Manager maintenance.

System action: None.

Operator Response: None.

Programmer Response: The “TM Display Level” information includes Thruput Manager PTF and APAR information. Verify that the information presented is as expected. Following this are displays of the two Thruput Manager JES2 source modules. These are normally assembled each time Thruput Manager maintenance is applied. Verify that the information presented is as expected.

DTM6300A

UNKNOWN JECL STATEMENT text


Explanation:
text: is up to ten characters of the statement that could not be recognized.
The text shown was encountered during analysis of a JECL statement, but could not be recognized.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the statement in error.

DTM6301A

statement-type JECL STATEMENT, UNKNOWN KEYWORD keyword


Explanation:
statement-type: is the type of JECL statement.
keyword: is the keyword that could not be recognized.

While analyzing the JECL statement statement-type, keyword was encountered but could not be recognized.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the statement in error.

DTM6302A

statement-type JECL STATEMENT, SYNTAX ERROR [IN KEYWORD] text


Explanation:
statement-type: is the type of JECL statement.
text: is up to ten characters of the keyword or text in error.
While analyzing the JECL statement statement-type, a syntax error was encountered. text identifies the keyword in error, or indicates the text that was being analyzed if no keyword was recognized.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the statement in error.

DTM6306A

statement-type JECL STATEMENT, EXTRANEOUS DATA text


Explanation:
statement-type: is the type of JECL statement.
text: is the extraneous data which was found.
While analyzing the JECL statement statement-type, the extraneous data text was encountered.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the statement in error.

DTM6307E

statement-type USER JECL STATEMENT IGNORED, EXIT 19 IS DISABLED


Explanation:
statement-type: is the type of JECL statement.
A user JECL statement was encountered and was to be passed to Thruput Manager exit 19, but this exit is not enabled.

System action: The statement is ignored.

Operator Response: None.

Programmer Response: Enable exit 19 or remove the statement.

DTM6309A

EXCESSIVE NUMBER OF statement-type JECL STATEMENTS


Explanation:
statement-type: is the type of JECL statement.
Too many statement-type JECL statements were encountered.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Reduce the number of statement-type JECL statements. For a description of the maximum number of JECL statements allowed per particular function see to the System Programming Guide: Base Product.

DTM6310A

JECL STATEMENT, KEYWORD keyword1 CONFLICTS WITH KEYWORD keyword2


Explanation: Mutually exclusive keywords have been coded in a JECL statement.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Review keywords coded in the JECL statement.

DTM6312I


Explanation: This is an internal diagnostic message.

DTM6330A

statement-type JECL STATEMENT, STEP REFERENCE name NOT FOUND


Explanation:

statement-type: is the type of JECL statement.

name: is the stepname which was not found.

A statement-type JECL statement referenced the stepname name, but it could not be found in the job’s JCL.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the statement in error.

DTM6331A

statement-type JECL/JAL STATEMENT, AGENT NAME name UNDEFINED


Explanation:

statement-type: is the type of JAL or JECL statement.

name: is the name of the undefined Agent.

The statement-type JAL or JECL statement referenced the Agent name, but this Agent is not defined.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JCL error.

Operator Response: None.

Programmer Response: Correct the statement in error, or determine why the Agent is not defined.

DTM6332A

statement-type JECL STATEMENT, AGENT NAME name INELIGIBLE


Explanation:
statement-type: is either ACTIVATE or DEACTIVATE.
A JECL statement attempted to perform an action that is not permitted for the specified agent. This can result from an attempt to activate or deactivate an agent that was defined as “OPER only”, or from an attempt to specify the COND keyword for an agent that in not defined as PERMANENT,UNIQUE.

System action: The job is failed with a JECL error during analysis, or during initiation if it is a started task.

Operator Response: None.

Programmer Response: Remove the OPER restriction, or remove the COND keyword.

DTM6333A

statement-type JECL STATEMENT, agent-name MISSING


Explanation:
statement-type: is the type of JECL statement.
While analyzing the JECL statement ‘type’, a required Agent name was not found.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the statement in error.

DTM6334A

statement-type JECL STATEMENT, KEYWORD keyword STEPNAME MISSING


Explanation:
statement-type: is the type of JECL statement.
While analyzing the JECL statement statement-type, the required stepname could not be found for keyword.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the statement in error.

DTM6335A

statement-type JECL STATEMENT, element name INVALID FORMAT


Explanation:
statement-type: is the type of JECL statement.
element: is the element whose format is invalid, and can be either STEPNAME or AGENT.
name: is the name of element whose format is invalid.
While analyzing the JECL statement statement-type, an invalid format was found for the name of an Agent or a stepname.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the statement in error.

DTM6336A

statement-type JECL STATEMENT keyword MISSING


Explanation: A required keyword is missing.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the statement in error.

DTM6337A

‘BIND’ STATEMENT AGENT agent: CATEGORY CAUSED FAILURE


Explanation: The named Agent caused the job to be failed because of an Incompatibility Category. See related message DTM6341I.

System action: The job is failed with a JCL error.

Operator Response: None.

Programmer Response: Remove the Agent causing the incompatibility.

DTM6338A

statement-type JECL STATEMENT, DUPLICATE AGENT NAME name


Explanation:
statement-type: is the JECL statement type.
name: is the name of the duplicated Agent.
While analyzing the JECL statement statement-type, the Agent name was encountered, but this name had already been specified.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Remove the duplicate Agent name.

DTM6339I

statement-type JECL STATEMENT, KEYWORD keyword NODE NAME MISSING


Explanation: The Node name is missing in an JBS ACTIVATE statement with the XMIT keyword.

System action: The statement is not processed. The job is terminated.

Operator Response: None.

Programmer Response: Correct the JECL statement.

DTM6340I

statement-type JECL STATEMENT, NODE NAME node-name INVALID


Explanation: The node name with the XMIT keyword is invalid.

System action: The statement is not processed. The job is terminated.

Operator Response: None.

Programmer Response: Correct node name.

DTM6341I

JOB FAILED DUE TO INCOMPATIBLE AGENTS


Explanation: The job attempted to BIND to two or more Agents that have been defined as incompatible. See related message DTM6337A for more information.

System action: The statement is not processed. The job is terminated.

Operator Response: None.

Programmer Response: Correct the incompatibility.

DTM6342I

WARNING JOB BINDS TO INCOMPATIBLE AGENTS


Explanation: The job is attempting to bind to two or more Agents that have been defined as incompatible but with the WARN attribute. See related message DTM6344I for more information.

System action: The job is allowed to continue.

Operator Response: None.

Programmer Response: Resolve the incompatibility. Usually a WARN status is intended to change to FAIL at a later date.

DTM6343I

NOTE SOME BIND AGENTS DELETED BY CATEGORY RESTRICTIONS


Explanation: The job attempted to bind to two or more Agents that have been defined as incompatible, but the $$DELETE keyword was coded resulting in the deletion of the incompatible BIND statement. See related message DTM6345I for more information.

System action: The job is allowed to continue.

Operator Response: None.

Programmer Response: None.

DTM6344I

‘BIND’ JECL STATEMENT AGENT agent: CATEGORY WARNING


Explanation: The named Agent caused the job to be warned because of an Incompatibility Category. See related message DTM6341I.

System action: The job is allowed to continue.

Operator Response: None.

Programmer Response: Resolve the incompatibility. Usually a WARN status is intended to change to FAIL at a later date.

DTM6345I

‘BIND’ JECL STATEMENT AGENT agent: BIND DELETED


Explanation: The job attempted to bind to two or more Agents that have been defined as incompatible, but the $$DELETE keyword was coded resulting in the deletion of the named incompatible Agent. See related message DTM6343I.

System action: The job is allowed to continue.

Operator Response: None.

Programmer Response: None.

DTM6347I

JOB REQUEUED AND HELD DUE TO UNDEFINED ENVIRONMENTS


Explanation: During verification of a new JBS Environment definition, it was determined that the job is requesting one or more Environments that are no longer defined.

System action: The job is requeued in the primary Job Analysis Class and placed in MHS_TM hold with the category description ENVIRONMENT.

Operator Response: None.

Programmer Response: If the missing JBS Environment was intentionally removed and will not be added back, release the job. This will cause it to fail with a JECL error and message DTM6331A.
If the missing JBS Environment was accidentally removed, replace the Environment definition and load the corrected definition file. MHS will detect the Environment and automatically release the job.

DTM6348I

MHS_TM HOLD CANNOT BE DONE. MHS NOT ACTIVE


Explanation: The job tried to request a JBS Environment that does not exist, and the JAL has requested that it be requeued in the MHS_TM hold category ENVIRONMENT, but MHS is currently not active.

System action: The job is failed with a JECL error.

Operator Response: Notify personnel responsible for support.

Programmer Response: Determine why MHS is not active and correct.

DTM6349I

application TRACE WRITTEN TO SYSOUT applicationTtime


Explanation: This is an internal diagnostic message.

DTM6350I

task-name STARTED TASK FAILED, JECL ERROR


Explanation: A started task using the DD SUBSYS interface has provided an invalid JECL equivalent statement that is in error.

System action: The started task is terminated.

Operator Response: Inform the support group.

Programmer Response: Correct the DD SUBSYS statement.

DTM6351A

task-name STARTED TASK FAILED type-of-request CONSTRAINT


Explanation: Either a BIND request or ACTIVATE request create an invalid situation. For a BIND request either the Agent is not active or it is active in another machine. For an ACTIVATE request, an invalid situation such as trying to activate a UNIQUE Binding Agent that is already active.

System action: The started task is terminated.

Operator Response: Review your procedures to see if you are activating the task correctly. If that is the case, inform the support group.

Programmer Response: Determine the cause of the conflict.

DTM6352I

application-id task-name REFERENCES JBS/JLS AGENT agent-name-list


Explanation: This message follows DTM6351A and provides a list of all the Agents referenced by the started task.

System action: The started task is not allowed to continue initiation.

Operator Response: Review your procedures to see which Agent may be causing the problem.

Programmer Response: Depending on problem, the started task DD SUBSYS statements may have to be altered.

DTM6353I

jobname QUEUED FOR RE-EXECUTION BY application-id


Explanation: The system has selected a job that cannot be allowed to run because of dependencies indicated by application-id.

System action: The job is requeued and placed in TM HOLD.

Operator Response: None.

Programmer Response: None.

DTM6354A

‘statement-type’ JECL STATEMENT, INVALID element PATTERN


Explanation: A DCS JECL statement specified a string pattern that was invalid.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the DCS JECL statement.

DTM6355A

DUPLICATE DCS ‘statement-type’ JECL STATEMENTS ID=nn ENCOUNTERED
LAST ONE ACCEPTED


Explanation: A DCS JECL statement was specified more than once.

System action: This is a warning message only. JECL analysis continues.

Operator Response: None.

Programmer Response: Remove the duplicate statement.

DTM6356A

DCS ‘statement-type’ JECL STATEMENT ID=nn NOT MATCHED WITH

ANY DCS ‘statement-type’ STATEMENT


Explanation: A DCS JECL statement was specified with a link id value that could not be matched with its associated DCS JECL statement. for example a DCS SERVICE statement could not be matched with a DCS FORDSN statement with the same id value specified in the SID keyword.

System action: After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the DCS JECL statements.

DTM6357A

DCS ALERT JECL STATEMENT NOT SPECIFIED


Explanation: DCS JECL ALERT1/H2/F1/F2 statements were specified without the required DCS ALERT statement.

System action: After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the DCS JECL statements.

DTM6358A

‘statement-type’ JECL STATEMENT, INVALID text SPECIFIED


Explanation: A DCS JECL statement specified invalid text.

System action: Analysis of this statement is terminated. After all JECL statements have been analyzed, the job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct the DCS JECL statement.

DTM6359E

SERVICE JECL STATEMENT ID=nn SPECIFIES 2 OR MORE
CONSECUTIVE SERVICE LEVELS THAT ARE THE SAME


Explanation: This is a warning message only. It indicates that the SERVICE statement contains two consecutive terms in the list that specify the same service level. e. g.: (...CLAIM(5),CLAIM(1)...).

System action: Analysis of this statement continues. The job is NOT failed.

Operator Response: None.

Programmer Response: Combine the two terms into one. E. G.: (...CLAIM(6)...).

DTM6360I

ERROR IN STATEMENT nn: ’operand’ OPERAND REQUIRED


Explanation: An operand required by a keyword in a SAC table definition is missing.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct syntax and restart TMSS or re-issue the command.

DTM6361I

ERROR IN STATEMENT nn: INVALID [KEYWORD | OPERAND] text


Explanation: A SAC table keyword or operand is either invalid or unrecognized.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct syntax and restart TMSS or re-issue the command.

DTM6362I

ERROR IN STATEMENT nn: DUPLICATE [KEYWORD | OPERAND] ENTRY FOUND text


Explanation: A SAC table keyword or operand has been specified more than once.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Remove the duplicate and restart TMSS or re-issue the command.

DTM6363I

SAC TABLE IS EMPTY dsname(member)


Explanation: The SAC table definition indicated by a TBL LOAD initialization statement or a TBL REFRESH command is either empty or contains only comments.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Specify a data set or member that includes a SAC table definition, and restart TMSS or re-issue the command.

DTM6364I

ERROR IN STATEMENT nn: CONTINUATION NOT FOUND


Explanation: End-of-File was detected instead of the expected continuation of the previous SAC table definition statement.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the error and restart TMSS or re-issue the command.

DTM6365I

ERROR IN STATEMENT nn: STATEMENT EXCEEDS nnn BYTES


Explanation: A SAC table definition statement exceeds the maximum number of bytes allowed for that statement type.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the error and restart TMSS or re-issue the command.

DTM6366I

ERROR IN STATEMENT nn: END OF COMMENT NOT FOUND


Explanation: In a SAC table definition the characters ‘/*’ were encountered, beginning a comment, but the closing characters ‘*/” were not found.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the error and restart TMSS or re-issue the command.

DTM6367I

ERROR IN STATEMENT nn: REQUIRED KEYWORD MISSING - keyword


Explanation: A SAC table definition statement is missing a required keyword.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the error and restart TMSS or re-issue the command.

DTM6368I

ERROR IN STATEMENT nn: MUTUALLY EXCLUSIVE - keyword


Explanation: A SAC table definition statement has specified mutually exclusive keywords.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the error and restart TMSS or re-issue the command.

DTM6369I

SAC TABLE DISPLAY:
SAC TABLE NOT DEFINED
or
SAC TABLE DISPLAY:
DSN=dsname [MEMBER=member] [*DISABLED]


Explanation: This message is issued in response to a TBL DISPLAY SAC command.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM6370I

SAC TABLE action


Explanation:
action: can be one of ENABLED or DISABLED.
This message is issued in response to a TBL ENABLE SAC or a TBL DISABLE SAC command.

System action: Processing continues.

Operator Response: None.

Programmer Response: None.

DTM6371I

SAC TABLE [LOAD | REFRESH] FAILED. TABLE NOT FOUND


Explanation: The specified SAC table could not be found.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the error and restart TMSS or re-issue the command.

DTM6372I

SAC TABLE NOT REFRESHED. DATASET NAME NOT SPECIFIED


Explanation: A TBL REFRESH SAC command was issued, but no data set name was specified, and there was no SAC table loaded during TMSS initialization.

System action: The command is ignored.

Operator Response: Specify a data set name for the SAC table definition. If the SAC table should have been loaded at TMSS initialization, notify personnel responsible for support.

Programmer Response: Correct the error and restart TMSS.

DTM6373I

program REQUIRES JBS AGENT agent TO BE ACTIVE


Explanation: A program, TSO command, or ISPF panel is defined in the SAC table as requiring the indicated JBS Binding Agent. This message is issued in place of an installation-defined message when Thruput Manager is unavailable. It is preceded by messages explaining the reason for the unavailability and is followed by DTM6374I.

System action: Issues message DTM6374I.

Operator Response: Notify personnel responsible for support.

Programmer Response: Determine why Thruput Manager is unavailable and correct.

DTM6374I

ACCESS TO ‘product’ HAS BEEN DENIED


Explanation:
product: is the 1-24 product name specified in the SAC table definition.
This message is preceded by DTM6373I, and indicates the installation-specified product name for the requested program, TSO command, or ISPF panel.

System action: The request is denied.

Operator Response: Notify personnel responsible for support.

Programmer Response: Determine why Thruput Manager is unavailable and correct.

DTM6375I

ERROR IN STATEMENT nn: DUPLICATE ‘keyword’ KEYWORD FOUND


Explanation: While loading the SAC table, a duplicate keyword was encountered.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the error and restart TMSS or re-issue the command.

DTM6376I

ERROR IN STATEMENT nn: PARSE ERROR


Explanation: While loading the SAC table, a syntax error was encountered.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the error and restart TMSS or re-issue the command.

DTM6377I

ERROR IN STATEMENT nn: NESTED ‘FOR’ STATEMENT


Explanation: While loading the SAC table, a FOR statement was encountered before the ENDFOR statement for a previous FOR statement.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the error and restart TMSS or re-issue the command.

DTM6378I

ERROR IN STATEMENT nn: MISSING ‘FOR’ STATEMENT


Explanation: While loading the SAC table, an ENDFOR statement was encountered but no previous FOR statement has been found.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the error and restart TMSS or re-issue the command.

DTM6379I

ERROR IN STATEMENT nn: MISSING ‘ENDFOR’ STATEMENT


Explanation: While loading the SAC table, a FOR statement was encountered, but no matching ENDFOR was found.

System action: If the error occurs during TMSS initialization, TMSS terminates with a return code of 28. If the error occurs during a TBL REFRESH operator command, the command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the error and restart TMSS or re-issue the command.

DTM6400E

application-id command-name COMMAND, TOO MANY PARAMETERS


Explanation: Too many parameters were entered for the indicated command.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6401E

application-id command-name COMMAND, name INVALID AGENT NAME


Explanation: An invalid Agent name was entered for the indicated command.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6402E

application-id command-name COMMAND, AGENT NAME MISSING


Explanation: The indicated command requires an Agent name, but none was found.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6403E

application-id command-name COMMAND, keyword INVALID KEYWORD


Explanation: An invalid keyword was entered for the indicated command.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6404E

application-id command-name COMMAND, INVALID LIMIT


Explanation: A Limit has been specified that is not numeric or exceeds 999.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6405E

application-id command-name COMMAND, INVALID SYSTEM ID


Explanation: An invalid system identifier was entered for the indicated command. It normally indicates that the sysid is not known to JES2.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6406E

application-id DISPLAY COMMAND, JOB PARAMETER INVALID


Explanation: The JOB keyword for the indicated command was invalid.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6407E

application-id DISPLAY COMMAND, JOB PARAMETER MISSING


Explanation: The JOB keyword was required for the indicated command, but was not found.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6408E

task-id NOT KNOWN TO application-id


Explanation:
task-id: is a unique identifier formed by combining the type of task (e.g. JOB, STC, or TSU) with the JES2 job number.
application-id: is the name of the application (e.g. JBS, JLS, JCS,...).
The indicated task is not known to application.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6409E

application-id command-name COMMAND FAILED, AGENT name NOT DEFINED


Explanation: The indicated Agent has not been defined.

System action: The command is ignored.

Operator Response: Re-enter correctly or define the Agent.

Programmer Response: None.

DTM6410I

application-id command-name COMMAND SUCCESSFUL


Explanation: The indicated command was processed successfully.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6411E

application-id command-name COMMAND FAILED, AGENT NOT ACTIVE


Explanation: The indicated command could not be processed because the specified Agent is not active.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6412I

application-id command-name COMMAND FAILED, UNSUPPORTED FUNCTION


Explanation: The indicated command requested a function that is not currently supported.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6413E

application-id command-name COMMAND FAILED, CONTROL AREA FULL


Explanation: There is no more room in the application area of the Control File.

System action: The command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: Consider enlarging the Control File.

DTM6414E

application-id command-name COMMAND FAILED, XMIT AGENT ALREADY ACTIVE


Explanation: The indicated command attempted to activate an Agent that has already been activated with the XMIT keyword.

System action: The command is ignored.

Operator Response: Deactivate the XMIT Agent and re-enter.

Programmer Response: None.

DTM6415E

application-id command-name COMMAND FAILED, AGENT IN USE


Explanation: The indicated command was rejected because the Agent was in use.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6416E

application-id command-name COMMAND FAILED, MEMORY SHORTAGE


Explanation: There is insufficient memory in the TMSS address space.

System action: The command is ignored.

Operator Response: Notify personnel responsible for support.

Programmer Response: If this error persists, enlarge the TMSS region.

DTM6417E

application-id command-name COMMAND FOUND NOTHING TO DISPLAY


Explanation: The indicated command found nothing eligible for the requested display.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6418E

application-id command-name COMMAND FAILED, AGENT IS NOT PERMANENT


Explanation: The command entered applies only to PERMANENT Agents.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6419E

application-id command-name COMMAND FAILED, INVALID SYSTEM AFFINITY


Explanation: The indicated command specified an invalid system affinity.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6420I

application-id DISPLAY
text

This display can have several formats, depending on the command entered.
A display of JBS Agents without details:

/JBS D AGENTS



    • has this form:
      DTM6420I JBS DISPLAY
      BIND.AGENT1 - INACTIVE
      BIND.AGENT2 - ACTIVE ON S001
      XMIT.APPLIC1 - ACTIVE ON S001,S002,S003.S004.S007,S010+

      A plus sign (+) following the list of systems indicates that the Agent is active on additional systems. To get the complete list of systems, display the Agent specifying the DETAILS keyword:

      /JBS DISPLAY AGENT XMIT.APPLIC1 DETAILS

    • The resulting display looks like this:

      DTM6420I JBS DISPLAY
      XMIT.APPLIC1 -STATUS=(RESERVED,ACTIVE)
      SCOPE=(PERM,XMIT,MULTIPLE)
      ACTIVE ON S001,S002,S003.S004.S007,S010
      - S011,S012,S014
      TRANSMIT to TORONTO
      LAST ACTION: MAY 5, 2009 13:16 BY SDSFP2T1
      DEACTIVATED ON S008

    • If an Agent has been activated globally, but also has been activated on specific systems, the GLOBAL indicator in a display for that Agent is precede by an asterisk (*). The system(s) on which it has been activated specifically are shown in the SUSPENDED ACTIVATE line that follows. For example, the command:

      /JBS D AGENT BIND.AGENT3

      generates a display with full details for the Agent:

      DTM6420I JBS DISPLAY
      BIND.AGENT3 -STATUS=(ACTIVE,*GLOBAL)
      SCOPE=(PERM,UNIQUE,GLOBAL)
      * SUSPENDED ACTIVATE ON S001,S003
      LAST ACTION: MAY 17, 2009 17:32 BY SDSFP2T1
      ACTIVATED ON S003

      If this Agent is deactivated globally, these suspended activates will no longer be suspended and will become effective.

      The command:
      /JBS DISPLAY

      requests a status display for the facility, which shows:

      DTM6420I JBS DISPLAY
      Control Area Size = 237344 Bytes
      Amount Used = 1224 Bytes (0.5 %)
      Binding Agents = 5
      Active Binding Agents = 2
      Controlled Jobs = 5
      Held Jobs = 3
      Application Version = 11
      Control File Version = 11
      Control File ID = JB31

      A display of JBS for jobs generates a display such as:
      DTM6420I JBS DISPLAY
      JOB00001 TESTJOB HELD FOR BIND SYS=ANY
      JOB00002 ANYJOB AWAITING EXEC SYS=ANY
      JOB00003 ANOTHER AWAITING EXEC SYS=ANY
      JOB00004 PRODJOB AWAITING EXEC SYS=S001,S003,S004,S007,S010+

    • A plus sign (+) following the list of systems indicates that there are additional system affinities for the job. A complete list of affinities is displayed when a JBS DISPLAY command is issued for the specific job.

      The JBS DISPLAY command can also show information about Incompatibility Categories:

      /JBS DISPLAY CATEGORY

      When no specific Category is requested, all Categories are displayed in a table format:
      DTM6420I JBS DISPLAY
      CATEGORY Compatibility Matrix
      —NAME— # 0 1 2 3 4 5 6 7 8 9
      CLASSA 1 . . . . * . * . .
      CLASSB 2 . . . * . * . . .
      PROD 3 . . W . . . . . .
      TEST 4 . F . F . F . . .
      DB2 5 . . W . . . . . .
      DB2TEST 6 . F . F . F . . .
      7 . . . . . . . . .
      8 . . . . . . . . .
      9 . . . . . . . . .

    • This display is read by row, as follows:

      —Each row describes a Category.
      —Each column describes the Incompatibilities that have been defined.
      The incompatibilities defined for the Category are shown by a character:

      - ‘F’       indicates that the job is failed.
      - ‘W’ indicates that a warning is placed in the job’s system log.
      - ‘.’ indicates that there is no incompatibility.
      - ‘*’ indicates an incompatibility, but the command that defined it did not define the
      Category represented by this row. Here the ‘*’ in row 1 column 4 indicates that
      the JBS DEFINE command was issued for Category 4, not Category 1.

      A display request for a single Incompatibility Category such as:

      /JBS DISPLAY CATEGORY 3

      shows only the line describing the requested Category:
      DTM6420I JBS DISPLAY
      CATEGORY Compatibility Matrix
      —NAME— # 0 1 2 3 4 5 6 7 8 9
      PROD 3 . . W . . . . . .

      The JBS DISPLAY command can be used to display information about the Resource Elements used with Environment Agents:

      /JBS DISPLAY RESOURCES

      This displays information about all the Resource Elements that are currently defined:
      DTM6420I JBS DISPLAY
      SHIFT -Reset on SYS1,SYS2
      States: PROD OVERNITE<SYS3,SYS4>
      WEEKEND
      SYSTEM.STATUS -States: NORMAL<SYS3,SYS4> MAINT
      TEST<SYS1,SYS2>
      IMS -Reset on SYS1,SYS2
      States: AVAILABLE<SYS3>,
      STOPPED<SYS4>

    • In this display, all Resource Elements are shown, along with their potential states and the current state for each system in the JES2 node.

      For JLS, a display command such:

      /JLS DISPLAY AGENTS

      shows the following:
      DTM6420I JLS DISPLAY
      COMPILER.* - LIMIT=3 SET BY OPERATOR
      COMPILER.CLASSH - LIMIT=3/5 REF=1 ACT=0
      BACKUP.DASD - LIMIT=2/2 REF=1 ACT=1

      In the above example, a JLS SET LIMIT command has been issued that affects any Limiting Agent with a first qualifier name of COMPILER. The display for the affected Agents shows the LIMIT value in the form of ss/ll, where ss represents the current value from the JLS SET command and ll represents the JAL LIMIT value. REF shows the number of jobs referencing the Limit, and ACT displays the total weight of Limits in currently executing jobs.

      A display command such as:

      /JLS DISPLAY JOBS

      shows the following:
      DTM6420I JLS DISPLAY JOB00002 FAKEJOB1 AWAITING EXEC JOB00005 FAKEJOB2 HELD FOR LIMIT

      System level Limiting Agents are identified in a job display by the initial character ‘+’ (plus sign). For example:

      /JLS DISPLAY JOB 52599

    • might result in this display:

      DTM6420I JLS DISPLAY
      JOB52599 BKUPDB01 AWAITING EXEC
      +AUTO.T3480 + LIMIT 4/4 REF=1 ACT=0 WEIGHT=1

    • In this example, the ‘+’ beginning the Limiting Agent name indicates a system level Limiting Agent. The ‘+’ preceding LIMIT indicates that this Limiting Agent is exceeded for this system, therefore the job will not be selected for execution even though it is not held. You can confirm this by displaying the Limiting Agent:

      /JLS D AGENT +AUTO.T3480

      The resulting display resembles this:

      DTM6420I JLS DISPLAY
      +AUTO.T3480 - LIMIT=4/4 REF=1 ACT=0
      - LIMIT=0 FOR ALL ACTIVE SYSTEMS
      JOB52599 BKUPDB01 AWAITING EXEC WEIGHT=001

    • If the Limit is set higher than 0, but the job is not running because the Limit has currently been exceeded on all systems in the JESplex, the ‘+’ is replaced by ‘*’ (asterisk):
      /JLS DISPLAY JOB 52599

      results in this display:

      DTM6420I JLS DISPLAY
      JOB52599 BKUPDB01 HELD FOR LIMIT
      +AUTO.T3480 * LIMIT=1/1 REF=2 ACT=1 WEIGHT=1

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6421I

JLS RECONCILE INITIATED


Explanation: A JLS RECONCILE FORCE command was entered.

System action: The JES2 values for Agent limits and possible counts will be checked against actual values and adjusted if necessary.

Operator Response: None.

Programmer Response: None, unless this is required frequently. In that case, contact BMC Support.

DTM6422I

JLS RECONCILE COMPLETE


Explanation: A JLS RECONCILE FORCE command was entered, or a JLS RECONCILE AGENTS was entered, or a general reconcile was triggered.

System action: The JES2 values for Agent limits and possible counts have been checked against actual values and adjusted if necessary.

Operator Response: None.

Programmer Response: None.

DTM6423I

Restore complete. nn JLS SET commands issued.


Explanation: JLS RESTORE FROMDSN() command was completed successfully. During its execution, a number of JLS SET commands have been issued to define JLS agents. The exact number of issued commands is displayed as 'nn'. The issued commands can be found in the data set specified in the JLS RESTORE command.

System action: JLS agents have been restored according to the information contained in the data set specified in the FROMDSN parameter of the JLS RESTORE command.

Operator Response: None.

Programmer Response: None.

DTM6430E

application-id command-name FAILED, AGENT ALREADY DEFINED


Explanation: The indicated command attempted to define an Agent that was already defined.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6431E

application-id command-name COMMAND INVALID XMIT NODE NAME


Explanation: An invalid node name was specified.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6432E

application-id command-name COMMAND FAILED, MULTIPLE NJE NODES


Explanation: An invalid node name was specified.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6433E

application-id command-name COMMAND FAILED, AGENT NOT AUTHORIZED FOR XMIT


Explanation: The Agent specified was not defined with the XMIT attribute.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6434E

application-id node-name COMMAND, dsname INVALID DATASET NAME


Explanation: The specified data set name is invalid.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6435E

application-id node-name COMMAND, dsname DATASET NAME MISSING


Explanation: A data set name is required with this command and it was not specified.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6436E

application-id node-name COMMAND, keyword CONFLICTING KEYWORD


Explanation: Mutually exclusive keywords have been specified.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6438I

JLS RESET COMMAND COMPLETE, nnnn AGENTS RESET


Explanation: A JLS RESET command has completed.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6441E

application command RESPONSE SUPPRESSED, EXCESSIVE SIZE, USE L= OPERAND


Explanation: The response to the command (usually a DISPLAY) is too long.

System action: The command response is suppressed.

Operator Response: Re-enter the command using the L= operand.

Programmer Response: None.

DTM6445E

JBS REDEFINE COMMAND, category-name INVALID CATEGORY NAME


Explanation: The category name cannot be more than 8 characters.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

The following command examples result in the same error:
/JBS REDEFINE AGENTONE CATEGORY(123456789)
/JBS REDEFINE 1 NAME(XYZABCDEFG)

DTM6446E

JBS DEFINE COMMAND, ERROR IN LIST OF INCOMPATIBILITIES


Explanation: The category number(s) can be followed by the action code F/W/N for Fail/Warn/None. From the example, “A” is not a valid code.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

The following command example results in this error:
/JBS DEFINE 1 INCOMPAT(7W,4A)

DTM6447E

JBS [RE]DEFINE COMMAND FAILED, CATEGORY NOT DEFINED


Explanation: An undefined category results when the category name has not been assigned to a category number.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

The following command example results in this error:
/JBS REDEFINE AGENTONE CATEGORY(ZXY)

DTM6450E

JBS DEFINE COMMAND, keyword NOT VALID FOR ‘JOBRELATED’ AGENT


Explanation: Mutually exclusive keywords entered for the agent.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.
The following command example results in this error:
/JBS DEFINE AGENTONE JOB OPER

DTM6451I

JBS SET COMMAND, INVALID RESOURCE NAME


Explanation: A JBS SET command was issued with an invalid or missing Resource name.

System action: The command is ignored.

Operator Response: Enter the command with a valid Resource name.

Programmer Response: None.

DTM6453E

JBS SET COMMAND FAILED, RESOURCE NAME MISSING


Explanation: A JBS SET command was issued without a Resource name.

System action: The command is ignored.

Operator Response: Enter the command with a valid Resource name.

Programmer Response: None.

DTM6454E

JBS SET COMMAND FAILED, STATE NAME MISSIN

G
Explanation: A JBS SET command was issued without a State name.

System action: The command is ignored.

O perator Response: Enter the command with a valid State name.

Programmer Response: None.

DTM6455E

JBS command COMMAND FAILED. RESOURCE NOT FOUND


Explanation: A JBS SET, JBS RESET, or JBS DISPLAY command was issued specifying a Resource name that does not exist.

System action: The command is ignored.

Operator Response: Enter the command with a valid Resource name.

Programmer Response: None.

DTM6456E

JBS SET COMMAND FAILED. STATE NOT FOUND


Explanation: A JBS SET command was issued specifying a State name that does not exist.

System action: The command is ignored.

Operator Response: Enter the command with a valid State name.

Programmer Response: None.

DTM6460E

SET STATEMENT: RESOURCE resource NOT FOUND


Explanation: A /*JBS SET JECL statement specified a Resource name that does not exist.

System action: The job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct JECL to specify an existing Resource name, or load an Environment definition that includes the named Resource.

DTM6461E

SET STATEMENT: RESOURCE resource STATE state NOT FOUND


Explanation: A /*JBS SET JECL statement specified a State name that does not exist.

System action: The job is failed with a JECL error.

Operator Response: None.

Programmer Response: Correct JECL to specify an existing State name, or load an Environment definition that includes the named State.

DTM6471E

JBS SET COMMAND, INVALID STATE NAME


Explanation: A JBS SET operator command specified a state name entered that was invalid in format or length.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6500I

TM OPTION action COMMAND, ‘option-name’
INVALID OPTION NAME


Explanation: The option name is not recognized.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6501I

TM OPTION action COMMAND, REQUIRED OPTION NAME MISSING


Explanation: The option name has not been included in the command text.

System action: The command is ignored.

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6502I

TM OPTIONS DISPLAY
OPTION STATE STATUS
option state status


Explanation:
state: can be either NOT-INSTALLED, ENABLED, or DISABLED.
status: can either be N/A, ACTIVE, or INACTIVE. If the status is inactive because of an abend, it is shown as *INACTIVE*.

This is the output in response to a TM OPTIONS DISPLAY command.

NOTE: If any of the Thruput Manager routines abends three times, the module will be disabled and DISABLED DUE TO ERRORS will appear as the last line of the message.

System action: The status for each Thruput Manager option is listed.

Operator Response: None.

Programmer Response: None.

DTM6503I

NO OPTIONAL COMPONENTS INSTALLED


Explanation: Only the base Thruput Manager is installed.

System action: Command is ignored.

Operator Response: None.

Programmer Response: None.

DTM6504I

TM OPTION action COMMAND, TOO MANY PARAMETERS


Explanation: Self-explanatory.

System action: Command is ignored.

Operator Response: Re-issue command with the correct syntax.

Programmer Response: None.

DTM6505A

DISABLING ‘application’ IN A PRODUCTION ENVIRONMENT COULD HAVE UNDESIRABLE CONSEQUENCES. REPLY ‘Y’ OR ‘N’


Explanation: A TM OPTIONS DISABLE command was issued for the specified Thruput Manager service.

System action: Thruput Manager waits for a reply.

Operator Response: Reply Y to disable the component. Since disabling a conponent can have serious consequences, ensure that this is really the desired action.

Reply N to continue without disabling.

Programmer Response: None.

DTM6563I

TM LEVEL DISPLAY
SYSNAME=sysname JES2 NODE=nodename
TM VverRrel AT PTF ptf-level, Z/OS Ros-release, JES2 Z/OS jes2-release
[COMPONENT]
[component]
... ...
[NO] APAR(S) APPLIED[: apar, apar, ...]
[CUSTOM OPTIONS: option, option, ...]

or

PCS LEVEL DISPLAY
SYSNAME=sysname JES2 NODE=nodename CA7=ca7name rreliase(service_pack)
TM VverRrel AT PTF ptf-level, Z/OS Ros-release, JES2 Z/OSjes2-release
[NO] APAR(S) APPLIED[: apar, apar, ...]


Explanation: This message is the response to one of the following commands: TM DISPLAY LEVEL or PCS DISPLAY LEVEL. The display for TM DISPLAY LEVEL command shows system information, the software levels for Thruput Manager, z/OS and JES2 release information, as well as optional Thruput Manager components, APARs and Custom Options if any.

The display for PCS DISPLAY LEVEL command shows system information, CA 7 name, CA 7 release and service pack information, the softwate level for Thruput Manager, z/OS and JES2 release information, as well as APARs applied if any.

NOTE: If any of the Thruput Manager routines abends three times, the module will be disabled and DISABLED DUE TO ERRORS will appear as the last line of the message.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6564I

ERROR condition SPS NAME ‘SPS-name’


Explanation:
condition: can be either ALLOCATING or OPENING.

An error occurred while attempting to allocate or open the SPS SYSOUT data set associated with the name sps-name. Message '''''''''''''''''''''nnnnnnnnnnnnnnnnnnzzzzzzzzzqq follows.System action: The command is terminated.

Operator Response: Notify personnel responsible for support.

Programmer Response: Examine the accompanying message DTM0190I to determine the cause of the problem.

DTM6565I

command OUTPUT SENT TO DDNAME ‘ddname’
or
command OUTPUT SENT TO SPS NAME ‘sps-name’


Explanation:
sps-name: is the SPS name to which the output was directed.
This message indicates where the output from the specified command was sent. If the output was held, the DDNAME is shown, otherwise the SPS name is displayed.System action: The output is handled as indicated.

Operator Response: None.

Programmer Response: None.

DTM6568I

INVALID JES2 MODULE, INCORRECT VERSION/RELEASE (MIT).


Explanation: A TM ADS REINSTALL operator command was issued, but the JES2 module was not compatible with the running JES2.

System action: The command is ignored.

Operator Response: None.

Programmer Response: Re-assemble the Thruput Manager JES2 source component with the correct JES2 macro libraries.

DTM6572I


Explanation: This is an internal diagnostic message.

DTM6573I

JSS DISPLAY HSMQ
JOBID JOBNAME DATA SET BEING RECALLED TIME
jobno jobname datasetname time
...
or
JSS DISPLAY HSMQ
DATA SET BEING RECALLED TIME JOB# JOBNAME
datasetname time jobno jobname
...


Explanation:
time: is the time that the HSM recall was initiated.
A JSS DISPLAY HSMQ command was issued. If the JOBS keyword was specified, or if there was no keyword, the display is ordered by job number. If the DSNS keyword was specified, the display is ordered by data set name.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6574I

NO type AWAITING DATA SET RECALL


Explanation:
type: is the type of display requested, and is either JOBS or DSNS.
A JSS DISPLAY HSMQ command was issued, but there are no jobs or data sets awaiting HSM recall.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6575I


Explanation: This is an internal diagnostic message.

DTM6576I


Explanation: This is an internal diagnostic message.

DTM6577I


Explanation: This is an internal diagnostic message.

DTM6578I


Explanation: This is an internal diagnostic message.

DTM6579I

TM PARMS DISPLAY
JES2 INITIALIZATION PARAMETERS:
TMPARM ANALYSIS=9,AFFINITY=*,...
TMSS EXECUTION PARAMETERS:
VIF=,SPOOL=,CF=,CMF=
TMSS INITIALIZATION PARAMETERS:
DSN=SYS1.JESB.PARMLIB(TMSS00) VOL=SYSA02
...
*** END OF PARMS DISPLAY ***


Explanation: This display is issued in response to a TM DISPLAY PARMS operator command.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6580I

aname IS NOT A VALID ENTRY POINT FOR pname
or
pname IS NOT A VALID ENTRY POINT


Explanation:
aname: is the alternate entry point in error.}
pname: is the primary entry point of the module.
An error occurred during the loading of a module while processing the TM DISPLAY LEVEL operator command.

System action: If possible, processing of the command continues.

Operator Response: None.

Programmer Response: This message has two forms.The first is used when the module is being loaded by its alias name. The second is used when the module is loaded by its real name.

  • For the first form of the message, ensure that the alternate entry point described in the message is actually an alias for the primary entry point. This can be determined by using the ISPF Utilities option against the Thruput Manager execution library. The alternate entry point should have the same TTR and size as the primary entry point.
    If this is not true, it is likely that the primary entry point was copied from an SMP/E target library to an execution library without copying its corresponding alias.
  • For the second form of the message, ensure that the first csect of the load module is DTMCSMAP. This should always be true because DTMCSMAP is ORDERed during link-edit processing. Exceptions are the JES2 modules DTMJ2MVn and DTMJ2SVn ( n is the TM version) where DTMCSMAP is ORDERed as the second csect of the load module.

DTM6581I

JTS OPTIONS
AM PM NIGHT DEFTIME MAXDAYS max old
hhmm hhmm hhmm hhmm ddd


Explanation:
max: indicates how jobs that exceed MAXDAYS are to be handled, and is one of:

  • MAXFAIL, indicating jobs exceeding MAXDAYS should be failed.
  • MAXWARN, indicating jobs exceeding MAXDAYS should be allowed to continue with a warning.

old: indicates how jobs that specify a RELEASE date that has passed, and is one of:

  • OLDFAIL, indicating jobs specifying a past date should be failed.
  • OLDWARN, indicating that jobs specifying a past date should be allowed to continue with a warning.

This is the display issued in response to a JTS DISPLAY OPTIONS operator command.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6582I

Time requested not in trace. Reason Code: n


Explanation: An ADS FORMAT GTRACE or SLMTRACE command was entered with the TIME parameter and the time entered was not within the range currently available in the DataSpace.
n: internal reason code for message
DTM6589I Current PCS mode: Managed/Monitored
Number of BP jobs remaining being Monitored: xxxxxx
Number of Adhoc jobs remaining being Monitored: xxxxxx


Explanation: PCS current Monitoring mode is displayed as well as the number of jobs that remain unaffected by switching to this mode (if any).

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6584I

DCS TRACE SIZE IS 010K LINES.


Explanation: An ADS SET TMYDCSTS command was entered. The message displays (new) DCS trace size.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6585E

INVALID DCS TRACE SIZE, EXPECTED: 'nnnK'.


Explanation: An ADS SET TMYDCSTS XXXX command was entered but the specified trace size was invalid. The size is expected to be in the form nnnK, where nnn are digits.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6590I

Current PCS mode: Monitoring Only
Number of BP jobs remaining being Managed: xxxxxx
Number of Adhoc jobs remaining being Managed: xxxxxx


Explanation: PCS current Monitoring mode is displayed as well as the number of jobs that remain unaffected by switching to this mode (if any).

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6591E

INVALID VERBOSE LEVEL. EXPECTED: 1 DIGIT


Explanation: PCS SET command had an invalid verbose level value. Expected is a one-digit number from 0 to 9.

System action: None.

Operator Response: Re-issue the command with the correct verbose level.

Programmer Response: None.

DTM6592I

<field-name> LEVEL IS <value>


Explanation: The message is issued in response to the PCS SET { ERROR | TRACE } command and reports a current verbose level value set for the field specified as <field-name>.
<value>: level value determines what PCS events are going to trigger DTMERROR messages (if ERROR field name is specified) or spinning the trace (if TRACE field name is specified). All events with significance value below the specified verbose level will be ignored.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6593I

<field-name> LEVEL ALREADY SET TO <value>


Explanation: The PCS SET command was issued to change the verbose level of the specified field. However, this field has been already set to the desired level earlier. The command has been ignored.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6594I

<field-name> LEVEL UPDATED TO <value>


Explanation: The PCS SET command issued to set the verbose level of the specified field to the specified value was completed successfully.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6595I

PCS event detected. Module: <module-name> Label: <label>


Explanation: One of the predefined events was detected in the PCS Control Region. This message is used for debugging purposes only and can be ignored under normal circumstances.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6596I

ERROR LEVEL IS <value1>
TRACE LEVEL IS <value2>


Explanation: The message is issued in response to the PCS SET DISPLAY command and reports current verbose level value set for the ERROR field and the TRACE field.
Level value determines what PCS events are going to trigger DTMERROR messages (ERROR LEVEL) or spinning the trace (TRACE LEVEL). All events with significance value below the specified verbose level will be ignored.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6597E

PCS MONITOR command failed. Ref.code is EEE


Explanation: Unexpected error occurred during an attempt to execute PCS MONITOR command.

System action: None.

Operator Response: Report this message to support.

Programmer Response: None.

DTM6598W

PCS is already in Monitoring Only mode.


Explanation: PCS MONITOR ONLY command was issued but PCS is already in the Monitoring Only mode.

System action: A request to switch to the Monitoring Only mode is ignored because PCS is already in this mode.

Operator Response: None.

Programmer Response: None.

DTM6599W

PCS is already in Managing/Monitoring mode.


Explanation: PCS MONITOR MANAGE command was issued but PCS is already in the Managing/Monitoring mode.

System action: A request to switch to the Managing/Monitoring mode is ignored because PCS is already in this mode.

Operator Response: None.

Programmer Response: None.

DTM6600I

AGENT agent-name {ACTIVATED | DEACTIVATED} BY jobname(JOBjobnumber)


Explanation: A JBS Binding Agent with the LOG attribute has just been activated or deactivated.

System action: The Binding Agent status is changed as indicated.

Operator Response: None.

Programmer Response: None.

DTM6601E

**WARNING** AGENT agent-name IS NOT ACTIVE


Explanation: A JBS Binding Agent with the WARN attribute is inactive and has just caused a job entering the system to be placed in hold.

System action: The job is held.

Operator Response: Once the Agent is activated, release the job. The job is indicated by an accompanying DTM1460I message.

Programmer Response: None.

DTM6603I

THE CONTROL FILE HAS BEEN CORRUPTED.
THE UTILITY DTMCFMUn SHOULD BE USED ASAP TO ANALYZE AND
REPAIR THE CONTROL FILE. THE JBS/JLS APPLICATIONS WILL
ATTEMPT TO CONTINUE PROCESSING USING THE DAMAGED FILE.


Explanation: During reconciliation, Thruput Manager has detected that the Control File is damaged.

System action: Thruput Manager attempts to continue.

Operator Response: Notify personnel responsible for support.

Programmer Response: Obtain a dump of the damaged Control File, then use the Control File Utility to analyze and repair the File. If necessary, perform a cold start.

DTM6604E

CONTROL FILE DAMAGE
CONTROL FILE FOR JBS/JLS WAS DAMAGED
REPAIR WAS IMPOSSIBLE. A DIAGNOSTIC REPORT WAS CREATED.
THE APPLICATION HAS BEEN STARTED WITH A COLD FORMAT.
PLEASE SEND THE SYSOUT - xxxxxxx - TO COMPUWARE CORPORATION SUPPORT ASAP.


Explanation: JBS/JLS has detected that the Control File is corrupt and cannot be repaired. Thruput Manager cannot continue without formatting the JBS portion of the Control File.

System action: Thruput Manager automatically formats the JBS portion of the Control File.

Operator Response: Notify personnel responsible for support.

Programmer Response: Forward the diagnostic SYSOUT File to Compuware Corporation.

DTM6605E

CONTROL FILE DAMAGE
THE CONTROL FILE FOR JBS/JLS WAS DAMAGED AND HAS BEEN REPAIRED.
PLEASE SEND THE SYSOUT DATASET (xxxxxxxx) TO MVS SOLUTIONS ASAP.


Explanation: JBS/JLS has detected that the Control File is corrupt and has taken action to repair the damage. Since the damage might not have been completely repaired, the consequences of proceeding are not predictable.

System action: Thruput Manager continues, using the repaired Control File.

Operator Response: Notify personnel responsible for support. Watch carefully for other malfunctions.

Programmer Response: Forward the diagnostic SYSOUT File to MVS Solutions.

DTM6606I

** JBS/JLS SOFTWARE LEVEL=nn, CID VERSION LEVEL=mm


Explanation: The JBS software level is lower than the level recorded in the Control File.

System action: Processing continues.

Operator Response: Notify personnel responsible for support. Watch carefully for malfunctions.

Programmer Response: Determine the reason for the warning. Ensure that it is acceptable to run a lower level of JBS.

DTM6607I

** JBS VERSION CHANGED FROM VERSION nn TO VERSION mm


Explanation: The JBS software level is higher than the level recorded in the Control File.

System action: The JBS software level recorded in the Control File is changed to match the level that is running.

Operator Response: None.

Programmer Response: None.

DTM6608E

application MAIN TASK DTMJBSV3 ABENDING Sccc


Explanation: This is an internal diagnostic message.

DTM6609E

application DIAGNOSTIC TRACE WRITTEN TO applicationTtime


Explanation: This is an internal diagnostic message.

DTM6705A

NET/GROUP JECL STATEMENTS ARE MUTUALLY EXCLUSIVE
Explanation: A job has included both the NET and GROUP statements.

System action: The job is failed with a JCL error.

Operator Response: None.

Programmer Response: Remove one of the conflicting statements.

DTM6706A

‘’GROUP’’ JECL STATEMENT, DUPLICATE DJC JOBNAME


Explanation: A job was submitted for a DJC Group, but the Group already contains a job with the same jobname.

System action: The job is failed with a JCL error.

Operator Response: None.

Programmer Response: Use a different jobname.

DTM6707A

DJC JECL STATEMENT, NO GROUP STATEMENT


Explanation: A job included a DJC JECL statement, but did not include a /*DJC GROUP statement.

System action: The job is failed with a JCL error.

Operator Response: None.

Programmer Response: Add a /*DJC GROUP JECL statement or remove all DJC JECL statements.

DTM6708A

GROUP ID INVALID


Explanation: A DJC JECL statement has specified a DJC Group name with incorrect syntax.

System action: The job is failed with a JCL error.

Operator Response: None.

Programmer Response: Correct the syntax for the DJC Group name.

DTM6709A

DJC EXCESSIVE NUMBER OF GROUP JECL STATEMENTS


Explanation: A job contains more than one /*DJC GROUP JECL statements.

System action: The job is failed with a JCL error.

Operator Response: None.

Programmer Response: Remove the extra /*DJC GROUP statements.

DTM6710A

DJC GROUP MUST BE COMPLETED BEFORE NEW GROUP LOADED


Explanation: After DJC CLOSE was issued for a DJC Group that was loading, a job was submitted for that Group.

System action: The job is failed with a JCL error.

Operator Response: None.

Programmer Response: Re-submit after the active DJC Group has completed. The loading DJC Group will have become active, allowing a new loading Group to be created.

DTM6713E

DJC HOLD - jobname HAD ‘RELEASE FORCE’ NEGATED


Explanation: A DJC HOLD command was issued for a job that had previously been released from DJC hold by using the FORCE keyword.

System action: The job is placed in DJC hold.

Operator Response: None.

Programmer Response: None.

DTM6714E

DJC RELEASE - jobnumber NOT RELEASED - NOT USER HELD

Explanation: A DJC RELEASE command was issued for a job that was not held by a DJC HOLD command.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM6715E

DJC SET INVALID HISTORY COUNT

Explanation: A DJC SET command was entered, but the HISTORY_COUNT parameter was invalid.

System action: The command is ignored

Operator Response: Re-enter correctly.

Programmer Response: None.

DTM6717E

DJC command-name COMMAND IGNORED - SPECIFIED GROUP IS NOT ACTIVE


Explanation: The command was entered specifying the name of an existing DJC Group, but the Group is no longer active (is now a history Group).

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM6718I

DJC RELEASE - jobname WAS NOT BEING HELD - COMMAND IGNORED


Explanation: A DJC RELEASE command was entered for a job that was not being held by DJC.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM6719

DJC HOLD - jobname WAS ALREADY HELD - COMMAND IGNORED


Explanation: A DJC HOLD command was entered for a job that was already held by DJC.

System action: The command is ignored.

Operator Response: None.

Programmer Response: None.

DTM6720A

DJC GROUP PASSWORD FAILURE


Explanation: The Group specified by the job is password protected, but the job’s DJC GROUP JECL statement did not provide a password, or the password provided was incorrect.

System action: The job is failed with a JECL error.

Operator Response: None.

Programmer Response: Re-submit specifying the correct password.

DTM6722E

DJC command-name FAILED, GROUP NOT ACTIVE


Explanation: The command specified a DJC Group that is not active.

System action: The command is ignored.

Operator Response: Make sure the DJC Group name is entered correctly.

Programmer Response: None.

DTM6723E

DJC command-name SYNTAX ERROR


Explanation: The command specified invalid syntax.

System action: The command is ignored.

Operator Response: Re-enter with correct syntax.

Programmer Response: None.

DTM6725E

DJC command-name FAILED, GROUP NOT FOUND


Explanation: The command specified a DJC Group that does not exist.

System action: The command is ignored.

Operator Response: Make sure the DJC Group name is entered correctly.

Programmer Response: None.

DTM6726E

DJC command-name COMMAND FAILED, GROUP STATEMENT MISSING


Explanation: The command was entered for a job that did not contain a DJC GROUP statement.

System action: The command is ignored.

Operator Response: Specify a job belonging to a DJC Group.

Programmer Response: None.

DTM6727E

DJC command-name COMMAND FAILED, EVENT NAME INVALID


Explanation: The command specified a DJC Event name that is invalid.

System action: The command is ignored.

Operator Response: Re-enter with a valid DJC Event name.

Programmer Response: None.

DTM6728E

DJC command-name COMMAND FAILED, EVENT NAME MISSING


Explanation: The command did not specify a DJC Event name, but one is required.

System action: The command is ignored.

Operator Response: Re-enter with a valid DJC Event name.

Programmer Response: None.

DTM6729E

DJC command-name COMMAND, GROUP NAME MISSING


Explanation: The command did not specify a DJC Group name, but one is required.

System action: The command is ignored.

Operator Response: Re-enter with a valid DJC Group name.

Programmer Response: None.

DTM6730E

DJC command-name COMMAND, GROUP NAME INVALID


Explanation: The command specified an invalid DJC Group name.

System action: The command is ignored.

Operator Response: Re-enter with a valid DJC Group name.

Programmer Response: None.

DTM6731E

DJC CLOSE COMMAND, INVALID KEYWORD


Explanation: The DJC CLOSE command was entered, but one of the keywords was invalid.

System action: The command is ignored.

Operator Response: Re-enter with correct syntax.

Programmer Response: None.

DTM6734E

DJC command-name INVALID KEEP VALUE


Explanation: The command specified an invalid value for the KEEP keyword.

System action: The command is ignored.

Operator Response: Re-enter with a valid value for KEEP.

Programmer Response: None.

DTM6735E

nn HISTORY GENERATIONS WERE PURGED


Explanation: A DJC DELETE command was entered, causing the indicated number of history generations to be purged.

System action: Purges the oldest nn history generations.

Operator Response: None.

Programmer Response: None.

DTM6738E

DJC command-name INVALID SET VALUE


Explanation: The command specified an invalid value for the SET keyword.

System action: The command is ignored.

Operator Response: Re-enter with a valid value for SET.

Programmer Response: None.

DTM6739E

DJC command-name INVALID HISTORY_DAYS


Explanation: The command specified an invalid value for the HISTORY_DAYS keyword.

System action: The command is ignored.

Operator Response: Re-enter with a valid value for HISTORY_DAYS.

Programmer Response: None.

DTM6746I

NET-ID=net-id, JOB jobname (jobnumber) HELD


Explanation: The job was part of a net that has been flushed, and is therefore placed in JES2 hold.

System action: The job is held.

Operator Response: Release or purge the job, as appropriate.

Programmer Response: None.

DTM6748I

NET-ID=net-id NET status
status: describes the status of the net, and is one of:
• IS BEING FLUSHED
• CANCELLED
• HAS COMPLETED


Explanation: This is a general status message.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6749I

NET-ID=net-id TOT=jobs COMP=completed PEND=eligible MISSC=missing
jobs: is the total number of jobs for the net.
completed: is the number of jobs that have completed.
eligible: is the number of jobs that have abended and are eligible for resubmission.
missing: is Y or N, depending on whether or not there are missing successor jobs or subnetworks.


Explanation: This message is part of a net status display.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6750I

NET net-id HAS COMPLETED


Explanation: A JES3-compatible net has completed processing.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6751I

DJC PROCESSING HAS COMPLETED


Explanation: DJC has finished processing all JES3-compatible nets.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM6801I

‘BATCH’ JECL STATEMENT, INVALID BATCH NAME


Explanation: The BATCH name provided is invalid.

System action: Analysis of this statement is terminated. The job is failed with a JCL error.

Operator Response: None.

Programmer Response: Correct the statement in error.

DTM6802A

statement-type JECL STATEMENT, JOB ‘jobname’, INVALID REFERENCE


Explanation: In a BEFORE or AFTER JECL statement the job refers to itself.

System action: Analysis of this statement is terminated. The job is failed with a JCL error.

Operator Response: None.

Programmer Response: Correct the statement in error.

DTM6803A

REQUIRED BATCH ID MISSING (OR INVALID)


Explanation: No BATCH ID has been provided in JAL for this job but it includes B&A JECL statements.

System action: The job is failed with a JCL error.

Operator Response: None.

Programmer Response: Either correct JAL so it provides a BATCH ID for the job, or remove the BEFORE or AFTER JECL statements.

DTM6820E

JCS DISPLAY COMMAND, name INVALID BATCH NAME


Explanation: The name provided in the command is invalid.

System action: The command is terminated.

Operator Response: Re-enter command with a valid BATCH ID name.

Programmer Response: Not applicable.

DTM6821E

JCS DISPLAY COMMAND, name BATCH NAME MISSING


Explanation: No BATCH ID name was provided with the command.

System action: The command is terminated.

Operator Response: Re-enter command with a valid BATCH ID name.

Programmer Response: Not applicable.

DTM6822E

JCS DISPLAY COMMAND FAILED, BATCH NOT ACTIVE


Explanation: No BATCH with that name currently in the system.

System action: The command is terminated.

Operator Response: Re-enter command with a valid BATCH name.

Programmer Response: Not applicable.

DTM6824E

command COMMAND FAILED, DUPLICATE JOB NAME


Explanation: There is more than one job with the same name.

System action: The command is terminated.

Operator Response: Re-enter command with a JES2 job number.

Programmer Response: None.

DTM6990E

job-name JBS API MESSAGE text INVALID SYNTAX


Explanation: The text found in an API message is incorrect.

System action: The request cannot be serviced.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the API message.

DTM6991E

job-name JBS API ID=nnnn OUT OF RANGE (1-999)


Explanation: The ID number provided in the API message is incorrect.

System action: The request cannot be serviced.

Operator Response: Notify personnel responsible for support.

Programmer Response: Correct the API ID.

DTM6992E

job-name JBS API ID=nn NOT AUTHORIZED


Explanation: There is no matching ‘API= nn’ in a JBS ACTIVATE or DEACTIVATE statement with this job.

System action: The request cannot be serviced.

Operator Response: Notify personnel responsible for support.

Programmer Response: Use proper ID or, if missing, insert the required JECL statement in the Job.

DTM6999A


Explanation: Reserved for the JBS API.

DTM7100I

INVALID DCS LOG FILE DATASET NAME: dsname


Explanation: During initialization TMSS found that the data set name specified on the FILE DCSLOG initialization statement was invalid.

System action: TMSS terminates with a return code of 24 once all initialization statements have been processed.

Operator Response: Notify personnel responsible for support.

Programmer Response: Specify the name of the DCSLOG File correctly.

DTM7102I

MULTIPLE NAME PATTERNS SPECIFIED


Explanation: An operator command specified more than one job, data set or owner name pattern.

System action: The command is ignored.

Operator Response: Re-enter the command with correct syntax.

Programmer Response: None.

DTM7103I

INVALID item NAME


Explanation: An operator command specified an invalid job, data set or owner name pattern.

System action: The command is ignored.

Operator Response: Re-enter the command with correct syntax.

Programmer Response: None.

DTM7104I

INVALID KEYWORD COMBINATION: keyword1, keyword2


Explanation: An operator command specified two keywords which are mutually exclusive.

System action: The command is ignored.

Operator Response: Re-enter the command with correct syntax.

Programmer Response: None.

DTM7105I

EXTRANEOUS DATA AFTER token, IGNORED


Explanation: An operator command contained extraneous characters.

System action: The command is processed, but any characters after token are ignored.

Operator Response: None.

Programmer Response: None.

DTM7108I

PLEASE FREE DATA SET name hh:mm:ss


Explanation: This message is sent to TSO users holding a data set required by a DCS-managed batch job. The frequency and number of messages sent depends on installation DCS initialization parameters, DAL and job JECL.

System action: None.

User Response: Free the data set if possible, otherwise notify operations personnel of the conflict, according to installation procedures.

Programmer Response: None.

DTM7109I

THIS DATA SET IS REQUIRED BY JOBjobnumber jobname


Explanation: This message accompanies message DTM7108I, unless overridden by DAL or JECL.

System action: None.

User Response: See the description of DTM7108I, above.

Programmer Response: None.

DTM7110I

JOBjobnumber jobname IN DCS state (nnn)
[NODE CLAIMING LIMIT REACHED]
REQ SERVICE DSNAME
req service dsname
Held xxx by name on system sysid
+++ nn additional Holders not displayed +++
+++ No Holders were returned by GRS(GQSCAN)


Explanation:
state: HOLD or WAIT.
nnn: The number of unavailable data sets.
xxx: SHR/EXC
name: JOB/TSO USER name.
sysid: System ID.

This message is issued by DCS when a job has encountered data set contention. If the job is attempting to claim but cannot because the limit has been reached, the message indicates this.

NOTE 1: If more than 6 holders are found, only 5 are displayed and the last line will be -
+++ nn additional Holders not displayed +++



    • NOTE 2: The following record indicates an error -
      +++ No Holders were returned by GRS(GQSCAN)

    • IBM's GQSCAN service is not returning a holder for the indicated data set. This should not happen under normal circumstances, but could happen if the user has mods which internally alter the enqueue name. For example, if an IBM enq exit has been utilized to manipulate the data set names then it is possible that GQSCAN will not return the users that are ENQed on the data set so the DTM7110I message will not include the 'Held by' messages. Instead the message will get "+++No Holders were returned by GRS(GQSCAN)" appended.

System action: If state is ‘HOLD’, the job is cancelled, requeued and placed in DCS HOLD status until the data sets become available. If state is ‘WAIT’, the job will wait in the initiator until the data sets are available, or until a DCS service-related time expires, at which time the job will be cancelled and requeued. If the job cannot claim because the limit has been reached, it is placed in DCS HOLD.

Operator Response: None.

Programmer Response: None.

DTM7111I

state FOR name usage service [nnn]


Explanation:state: HOLDING or WAITING.

usage: SHR or EXC, for ‘shared’ or ‘exclusive’.
service: ST, CO or CL for ‘standby’, ‘contend’, ‘claim’.
nnn: Appears only if service will be modified. Number of minutes after which service will be modified.

Accompanies message DTM7110I. One DTM7111I message is issued for each unavailable data set.

System action: See description of message DTM7110I.

Operator Response: None.

Programmer Response: None.

DTM7112I

JOBjobnumber name RUNNING, ALL DATA SETS AVAILABLE


Explanation: Issued for a job that was waiting in an initiator for data sets. If the message is issued on behalf of a started task, ‘JOB’ is replaced with ‘STC’.

System action: The job is allowed to begin execution.

Operator Response: None.

Programmer Response: None.

DTM7113I

JOBjobnumber name DATA SETS AUTOFREED


Explanation: Issued by DCS when data sets have been AUTOFREEd from a submitting TSO user causing data set contention with his own job.

System action: If the job was attempting to initiate in the same system as the submitting address space, the job is allowed to begin execution without further messages. If the job was selected for execution in a different system from the submitting address space, the job is released, and message DTM7115I is issued.

Operator Response: None.

Programmer Response: None.

DTM7114I

JOBjobnumber jobname RELEASE PENDING


Explanation: A DCS operator RELEASE command has been issued for a job on another JES2 node.

System action: DCS-to-DCS multi-system communication will take place, and the job will be released within a few seconds.

Operator Response: None.

Programmer Response: None.

DTM7115I

JOBjobnumber jobname RELEASED BY DCS, reason


Explanation:
reason: Is one of the following:

  • ALL DATA SETS AVAILABLE
  • OPERATOR REQUEST
  • DCS RESTART
  • JES2 CANCELLED
  • CONTROL FILE FULL
  • DCS SHUTDOWN IN PROGRESS

Issued when DCS releases a job.

System action: The job is released from DCS hold. If the job is not also held for other TM reasons, it will be released from JES2 hold, and will be eligible for initiation.

Operator Response: None.

Programmer Response: None.

DTM7116I

JOBjobnumber jobname RELEASE ERROR nnn, reason
Explanation: Internal error, reason for release as in DTM7115I.System action: The job is not released.Operator Response: Notify personnel responsible for support.Programmer Response: Trace the job’s history in the system log. Report the problem to MVS Solutions.

DTM7117I

JOBjobnumber jobname RECONCILIATION ERROR, KNOWN TO DCS BUT NOT HELD


Explanation: Internal error. DCS records indicated that this job had been held. However, it is not currently held.

System action: DCS discards its records for the job.

Operator Response: Notify personnel responsible for support.

Programmer Response: Trace the job’s history in the system log. Report the problem to MVS Solutions.

DTM7118I

JOBjobnumber jobname DCS MONITORING STOPPED


Explanation: This message is issued when DCS can not locate the job it was monitoring. For example, the job was canceled on another system.

System action: DCS discards its records for the job.

Operator Response: Notify personnel responsible for support.

Programmer Response: Trace the job’s history in the system log.

DTM7119I

DATA SET RESERVATION BYPASSED FOR JOB jobnumber DUE TO ITS USE OF reason


Explanation:
reason: Indicates why data set reservation was bypassed and is one of:

  • NON-CONFORMING GENERATION DATASETS.
    A data set is non-conforming if a step deletes a generation and a subsequent step refers to the deleted generation or an older generation.
    See the IBM space MVS JCL User’s Guide for a detailed explanation.
  • JOBCAT/STEPCAT. DCS data set reservation does not support the use of JOBCAT or STEPCAT.

System action: Job execution continues normally.

Operator Response: None.

Programmer Response: None.

DTM7120I

DCS DISPLAY - display-title status-message


Explanation:
display-title: is one of the following:
• JOB(S)
• DATA SET(S), followed by the data set name and enqueue scope:
— G for Global
— L for Local
• HOLDER(S)

status-message can show one or more of the following for each display-title:
• NO HOLDER DATA (TIMED OUT) FOR MEMBER system-id node-id
• JOB/STC/TSU number and name, ON system-name NODE node-name
• JOB/STC/TSU number and name IN DCS HOLD/WAIT FOR x(number) DATA SET(S), SINCE hh:mm
• JOB/STC/TSU number and name DATA SETS AVAILABLE - AWAITING EXECUTION (mm MIN)

A multi-line response to DCS operator DISPLAY commands which shows the display-title followed by the Job number and name, STC or Started Task number name, or TSU or TSO User-id number and name, and the requested status. The DISPLAY commands can be stacked e.g., /DCS D J D H.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM7121I

item(S) NOT KNOWN TO DCS


Explanation:
item: It is one of the following:

  • JOB
  • DATA SET
  • DATA SET HOLDER

Issued after a DCS operator DISPLAY item command if there were no items matching the specified pattern.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM7122I

NO JOB(S) MANAGED BY DCS


Explanation: Issued after a DCS operator display command if there are no jobs currently managed by DCS.

System action: None.

Operator Response: None.

Programmer Response: None.

DTM7123I

DCS MULTI-SYSTEM DATA COLLECTION BUSY, TRY LATER


Explanation: A DCS operator DISPLAY command requesting owner information has been issued. Data must be collected from multiple systems, which takes several seconds. A similar command has already been issued, and is not yet complete. Only one such command can be outstanding for a given DCS.

System action: This command is ignored.

Operator Response: Wait for the completion of the earlier command.

Programmer Response: None.

DTM7124I

DCS MULTI-SYSTEM DATA COLLECTION REQUIRED, STANDBY ...


Explanation: A DCS operator DISPLAY command requesting owner information has been issued. Data must be collected from multiple systems, which takes several seconds.

System action: DCS-to-DCS cross-system communication will take place, to collect the command response data.

Operator Response: Wait for command completion.

Programmer Response: None.

DTM7125E

DCS MULTI-SYSTEM DATA COLLECTION INCOMPLETE, CONTROL FILE FULL


Explanation: A DCS operator DISPLAY command requesting owner information has been issued. Data must be collected from multiple systems, which requires space in the Control File. There was insufficient space available to collect all of the command response data.

System action: The command response is displayed, with incomplete data set ownership data.

Operator Response: Investigate the reasons for a full control File, using DCS display commands. It is unlikely that the control File will fill under normal operating conditions. If you suspect a system malfunction, notify personnel responsible for support.

Programmer Response: If a system malfunction is suspected, report the circumstances to MVS Solutions.

DTM7126E

DCS MULTI-SYSTEM DATA COLLECTION INCOMPLETE, SYSTEM(S) NOT RESPONDING


Explanation: A DCS operator DISPLAY command requesting owner information has been issued. Data must be collected from multiple systems, which takes several seconds. The maximum time allotted for this operation has been exceeded.

System action: The command response is displayed, with incomplete data set ownership data.

Operator Response: The most likely cause of the problem is a system failure in the complex. Verify that all systems and all DCS tasks in the complex are running normally. If they are, notify personnel responsible for support.

Programmer Response: If this problem occurs during normal operations, it may be necessary to override the default CMDTIME DCS initialization parameter. This should be discussed with MVS Solutions.

DTM7127I

DCS IS RUNNING WITHOUT XCF SUPPORT
ADD “DCS SET XCF(YES)” TO THE TMSS INIT PARMS


Explanation: This is an informational message.

DCS originally communicated through the Control File among DCS instances in the same CFPlex (sharing the same Control File). The changes were implemented so that XCF could be used rather than the Control File to communicate from one DCS instance to another. It is an improvement in the mechanism since the instances needed to be in the same XCFPlex and not necessarily sharing the same Control File. In addition, the XCF method is more efficient.

Using XCF for DCS is optional. However it is HIGHLY recommended that the XCF method be used.

This is requested by adding DCS SET XCF(YES) statement in the TM PARMS.

System action: The DCS application continues to run in non-XCF mode. Nagging and alerts on systems that do not share the Thruput Manager Control File may be affected since the Control File cannot be used to pass information.

Operator Response: None.

Programmer Response: Follow the recommendation.

DTM7128E

Level mismatch found

LMOD--------CSECT----- EXPECTED-------ACTUAL

lmodname  csectnm    expected info   actual info


Explanation: This message is issued when ThruPut Manager detects that a module is not at the correct PTF level. This can occur when the PTF installation is incomplete. In the message text;

  • lmodname indicates the load module name.
  • csectnm indicates the csect name.
  • expected info indicates the expected level information. This includes the development number and assembly date and time.
  • actual info indicates the actual level information. This includes the development number and the assembly date and time.

The lmodname information is repeated when there are multiple mismatches.

This message can be issued after an ADS REINSTALL command, after an TM DISPLAY LEVEL command, and during initialization of the ThruPut Manager started task.

System action: None             

Operator Response: Contact System Programmer

Programmer Response: Ensure that the PTF installation is complete. This usually includes an LLA refresh followed by “ADS REINSTALL JES2EXITS” command, an “ADS REINSTALL COMMON” command, and a restart of the ThruPut started task.

DTM7130I

TM Recovery Values

Component  Maximum Retrys Number of Retrys Time to reset         

compname   maximum             retrys                     time


Explanation: This message is issued in response to ThruPut Manager command "TM RCV DISPLAY|MODIFY". In the message text;

  • compname indicates the name of the ThruPut Manager component.
  • maximum indicates the maximum number of times the component will be recovered.
  • retrys indicates the number of times the component has been recovered.
  • time indicates the time, in minutes, which must take place between component recoveries before the number of component failures is reset to zero.

System action: None

Operator response: None.

Programmer response: None.

User response: None

DTM7131I

Control file duplex subtask has failed too many times and is shut down

Explanation: The TMSS subtask handling the regular duplexing of the control file has failed many times within an allowed time period (default 3 times in 60 minutes).

System action: The duplex subtask is shutdown. If eligible to run on another system using the same control file, duplexing will be attempted on that system.

Operator response: None.

Programmer response: Open a case with BMC Support and provide any available dumps/system log.

DTM7132I

CONTROL FILE DUPLEX ACTIVE ON ssss 

Explanation:

ssss is the JESplex member name

The Control File Duplex function is active on the indicated system. The contents of the Control File are being regularly copied to the Duplex Control File data set.

System action:  None. Processing continues.      

Operator Response:  None.

Programmer Response: None      

DTM7133E

CONTROL FILE DUPLEX TERMINATED ON ssss 

Explanation: 

ssss is the JESplex member name

The Control File Duplex function has abnormally terminated on the indicated system. 

System action: Retry will be attempted until at least 3 previous attempts have failed within 60 minutes. Another member of the JESplex may be able to assume the Duplexing function.      

Operator Response:  Inform personnel responsible for support.

Programmer Response: Contact BMC support.     

DTM7134E

CONTROL FILE DUPLEX INITIALIZATION FAILED ON ssss 

Explanation:

ssss is the JESplex member name

The Control File Duplex function has failed to initialize on the indicated system. 

System action: Retry will be attempted until at least 3 previous attempts have failed within 60 minutes. Another member of the JESplex may be able to assume the Duplexing function.      

Operator Response:  Inform personnel responsible for support.

Programmer Response: Check to ensure that the Duplex Control File data set has been correctly allocated and cataloged and correct if not. Otherwise, contact BMC support.    

DTM7135I

DCS AUTOFREEING DATA SETS TO RUN YOUR JOB jobname (JOBjobnumber)


Explanation: This message is written to a TSO user’s screen when DCS is about to AUTOFREE data sets.

System action: DCS will issue message DTM7137I for each data set that it frees.

Operator Response: None

Programmer Response: None

User Response: If you need the data sets to be used later in your session, reallocate them when the batch job terminates.

DTM7136I

DATA SET WILL BE REPOSSESSED IN n MINUTES


Explanation: A warning issued to a TSO user when DCS is preparing to repossess a data set. This message accompanies DTM7108I and DTM7109I.

System action: One minute after the third warning, DCS will repossess the data set. This results in message DTM7138I being issued if the data set is open, and one or more DTM7137I messages.

Operator response: None

Programmer Response: None

User Response: If the data set is open, terminate the command or application which is using it (otherwise the repossessing process will abend it). Free the data set.

DTM7137I

FREED DATASET(dataset-name)
or
FREED FILE(file-name)


Explanation: Written to a TSO user when DCS has repossessed a data set. Follows DTM7136I repossession message or DTM7135I AUTOFREE notification.

System action: None.

Operator response: None.

Programmer Response: None.

User Response: If you need the data sets to be used later in your session, reallocate them when the repossessing batch job terminates.

DTM7138I

DCS ABENDING program-name TO FREE DATASET name


Explanation: Written to a TSO user when DCS is about to repossess the named data set. The running task program-name has the data set open. DCS terminates the task immediately, with an abnormal end.

System action: The task is abended with a U0666 completion code. Followed possibly by a system ABEND message depending on the task terminated.

Operator response: None.

Programmer Response: None.

User Response: If you need the data sets to be used later in your session, reallocate them when the repossessing batch job terminates.

DTM7139I

dsname REPOSSESSED FROM holder FOR requestor


Explanation: The named data set has been repossessed.

System action: The data set is made available to the requestor.

Operator response: None.

Programmer Response: None.

DTM7141I

HOLDER holder, DATA SET dsname, ERROR explanation


Explanation: This message indicates that the auto-free of a data set did not occur. This could be the result of normal system operation, or it could be an error.

System action: The repossession attempt is failed. The job remains in CLAIM service.

Operator response: Normally, this is an informative message. If it occurs frequently, notify personnel responsible for support.

Programmer Response: Determine whether the message is actually signaling an error condition.

DTM7142I

DCS LOAD error, reason


Explanation: This message is issued in response to a “DCS LOAD” command and indicates that an error occurred. In the message text;

reason: indicates the reason why the DCS LOAD failed.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7150I

THE file-type IS ON VOLUME volume
DSNAME: dsname


Explanation:

file-type: It is one of the following:

  • PCS COLLECTION FILE
  • PCS/SMF COLLECTION FILE
  • SLM COLLECTION FILE
  • DCS CMF FILE
    Identifies the type and name of the file specified in the TMSS FILE initialization statement and the volume located in the catalog entry for that filename.

System action: TMSS allocates the specified File.

Operator response: None.

Programmer Response: None.

DTM7151A

DO YOU WISH TO CONTINUE WITHOUT DCS CMF RECORDING? REPLY ‘Y’ OR ‘N’
*** Version 3 Mode Only ***


Explanation: TMSS is unable to use the CMF File. Preceding messages will indicate the reason. You may continue to run DCS without recording CMF data. If you reply ‘N’ DCS will terminate but other Thruput Manager functions will continue unaffected. When DCS is not active data set contention handling reverts to the “standard” MVS facilities.

System action: If the answer is ‘Y’, DCS continues but CMF recording is not enabled. If the answer is ‘N’, DCS terminates.

Operator response: Follow your installation procedures for a reply.

Programmer Response: From previous messages determine what caused the error and take corrective action.

DTM7151I

PROCEEDING WITHOUT DCS CMF RECORDING
*** Version 4 Mode Only ***


Explanation: TMSS is unable to use the CMF File. Preceding messages will indicate the reason. Thruput Manager continues to run but without recording CMF data. Other Thruput Manager functions, including DCS, are unaffected.

System action: DCS continues but CMF recording is not enabled.

Operator response: Notify personnel responsible for support.

Programmer Response: From previous messages, determine what caused the error and take corrective action.

DTM7152A

IS A DCS CMF FILE COLD START AUTHORIZED? REPLY ‘Y’ OR ‘N’


Explanation: The system has detected that the CMF File has never been formatted or a COLD start request has been made in the TMSS JCL procedure.

System action: Wait for reply.

Operator response: Confirm that the File name is correct and the cold start is expected. If so reply ‘Y’. Otherwise, notify personnel responsible for support.

Programmer Response: None.

DTM7153I

THE DCS CMF FILE IS BEING FORMATTED


Explanation: Follows a reply ‘Y’ to DTM7152A.

System action: The system initializes the File for CMF recording.

Operator response: None.

Programmer Response: None.

DTM7154I

THE DCS CMF FILE HAS BEEN FORMATTED (nnnn BLOCKS, nnn TRACKS)


Explanation: Follows DTM7153I. Indicates completion of the formatting operation.

System action: CMF recording is now active.

Operator response: None.

Programmer Response: None.

DTM7155I

Continuing with xxxxxxxxx Collection recording DISABLED


Explanation:
xxxxxxxxx: is one of the following

  • Experience
  • SLM
  • Experience SMF

This message is issued if the response to DTM7152A is NO.

System action: Processing will continue normally, but there will be no collection data written for the specified type of data.

Operator response: None.

Programmer Response: None.

DTM7156I

Group group.name has been unloaded


Explanation: This message is issued in response to a “DCS UNLOAD” command and indicates that the unload was successful. In the message text:
group.name: indicates the Fencing group specified by the operator.

System action: CMF recording is terminated and the operator is given the option to terminate DCS.

Operator response: Follow your installation procedures to handle permanent I/O errors.

Programmer Response: None.

DTM7157I

PERMANENT I/O ERROR ON DCS CMF FILE


Explanation: A permanent I/O error has occurred.

System action: CMF recording is terminated and the operator is given the option to terminate DCS.

Operator response: Follow your installation procedures to handle permanent I/O errors.

Programmer Response: None.

DTM7158I

DCS UNABLE TO RECORD TO CMF FILE


Explanation: DCS is unable to use the specified CMF File.

System action: More information is provided with message DTM7159I. CMF recording is terminated and the operator is given the option to terminate DCS.

Operator response: Notify personnel responsible for support.

Programmer Response: Correct the problem indicated by message DTM7159I. In most cases this means correcting the name specified in the TMSS initialization statement ‘FILE CMF’. In some other cases the File may have to be reallocated.

DTM7159I

DCS CMF DATA SET NAME NOT SPECIFIED
or
DCS CMF DATA SET NAME name NOT FOUND
or
MULTI-VOLUME DATA SET NOT SUPPORTED FOR DCS CMF
or
DCS CMF DATA SET IN NOT IN A DIRECT ACCESS DEVICE
or
DCS CMF DATA SET name IS NOT ON CATALOGED VOLUME
or
DCS CMF DATA SET HAS UNSUPPORTED DSORG
or
DCS CMF OPEN ERROR error-number
or
DCS CMF DATA SET name HAS INVALID CATALOGED DEVICE
or
DCS CMF DATA SET FORMAT FAILURE


Explanation: A problem has occurred with the DCS CMF File. This message accompanies DTM7158I.

System action: See the description of DTM7158I.

Operator response: See the description of DTM7158I.

Programmer Response: See the description of DTM7158I.

DTM7160E

DCS UNABLE TO OPEN TRACE DATA SET, SYSOUT ALLOCATION ERROR nn mmm
or
DCS UNABLE TO OPEN TRACE DATA SET, SYSOUT OPEN ERROR
or
DCS UNABLE TO OPEN TRACE DATA SET, INTERNAL OPEN FAILURE


Explanation: DCS attempted to write its internal trace data to a dynamically allocated SYSOUT data set, but was unable to either allocate the data set, or subsequently open it.

System action: The trace dump is bypassed, and DCS continues operation.

Operator response: Notify personnel responsible for support.

Programmer Response: In the case of an allocation error, analyze the return code (provided by DAIR). In the case of an open error, there is probably some memory overlay within the Thruput Manager address space. Restart TMSS. Contact BMC Support.

DTM7161I

DCS TRACE DUMPED, mmmm RECORDS


Explanation: Issued after DCS TRACE DUMP command processing has completed.

System action: The external trace File is closed, and is available for browsing or printing. Internal tracing resumes.

Operator response: None.

Programmer Response: None.

DTM7165I

JOBjobnumber jobname SERVICE MODIFIED TO service


Explanation: This message is issued in response to a MODIFY SERVICE command.

System action: The service is modified for all the data sets associated with the job.

Operator response: Notify personnel responsible for support.

Programmer Response: Trace the job’s history in the system log. Report the problem to MVS Solutions.

DTM7168E

ERROR - DCS SYSTEM system NOT IN XCF MODE


Explanation: The ambient system is running DCS using XCF support, but has received notification that another system in DCS complex is not running DCS in XCF mode.

System action: Continues processing. DCS information about the data set holders on the non-XCF system is not available.

Operator response: Use the DCS D COMPLEX command to determine which systems are using XCF support for DCS, and which are not. Notify personnel responsible for support.

Programmer Response: Ensure that either all systems are running DCS in XCF mode, or that all systems are not running DCS in XCF mode.

DTM7169E

ERROR - DCS SYSTEM system IS IN XCF MODE


Explanation: The named system is running DCS in XCF mode, but the issuing system is not running DCS in XCF mode.

System action: None.

Operator response: Notify personnel responsible for support.

Programmer Response: Ensure that all systems are running DCS in the same mode, either with or without XCF support.

DTM7170I

This is an internal diagnostic message. This message is accompanied by DTM7141I.

DTM7171I

WARNING - DCS CONTROL FILE NEAR FULL (reason)


Explanation:
reason: It is one of the following:

  • JOBS
  • DATA SETS
  • SPACE

Issued when DCS assumes control of a job in contention, and the DCS control File is more than 99 per cent full.
The capacity limits are:
JOBS 1024
DATA SETS 4096
SPACE approximately 140K

System action: None.

Operator response: Investigate the reasons for the large number of jobs and/or data sets in contention.

Programmer Response: If the number of jobs and data sets managed by DCS is relatively small (say, less than 100), the capacity problem may result from pathologically complex JAL/DAL or JECL. Investigate that possibility.

DTM7172I

DCS CONTROL FILE FULL (reason)


Explanation: Issued when DCS takes responsibility for a job in contention, and the DCS control File is full.

System action: Jobs are released by DCS, oldest first, until sufficient resources are freed to manage the newly-arrived job in contention.

Operator response: See the description of message DTM7171I.

Programmer Response: See the description of message DTM7171I.

DTM7173I

JOBjobnumber jobname ABANDONED BY DCS, DCS CAPACITY EXCEEDED


Explanation: Follows message DTM7172, if DCS was unable to free resources sufficient to manage the newly-arrived job in contention.

System action: DCS will not manage the job. The job will wait for its data sets in the initiator, with status displayed by standard MVS messages IEF861I, IEF863I, and IEF099I.

Operator response: See the description of message DTM7171II.

Programmer Response: See the description of message DTM7171I.

DTM7174E

CRITICAL DCS/XCF COMPONENT NOT FUNCTIONING


Explanation: DCS on the issuing system attempted to communicate with other DCS systems, but the DCS/XCF application has been disabled or has failed.

System action: The system attempts to continue processing, but DCS information about data set holders on other systems is not available.

Operator response: Notify personnel responsible for support.

Programmer Response: Determine why the DCS/XCF application is not running and correct.

DTM7175I

JOB jobnumber jobname DCS DATA SET LIMIT EXCEEDED, CONTINUING


Explanation: This job has more than 256 data sets unavailable because of enqueue conflict.

System action: The job will be managed by DCS, but only the first 256 data sets will be monitored for availability.

Operator response: This is a pathological job. It should be investigated with the personnel responsible for support.

Programmer Response: See Operator response.

DTM7176E

ERROR - DCS SYSTEM JOINING IS NOT IN XCF MODE - system


Explanation: The ambient system is running DCS using XCF support, but has received notification that another system is starting up and is not running DCS in XCF mode.

System action: Continues processing. DCS information about the data set holders on the non-XCF system is not available.

Operator response: Use the DCS D COMPLEX command to determine which systems are using XCF support for DCS, and which are not. Notify personnel responsible for support.

Programmer Response: Ensure that either all systems are running DCS in XCF mode, or that all systems are not running DCS in XCF mode.

DTM7177E

ERROR - DCS SYSTEM JOINING IS IN XCF MODE - system


Explanation: The ambient system is not running DCS using XCF support, but has received notification that another system is starting up and is running DCS in XCF mode.

System action: Continues processing. DCS information about the data set holders on the XCF system is not available.

Operator response: None.

Programmer Response: None.

DTM7178E

DCS MONITOR SUBTASK TERMINATION nnn, DCS TERMINATING


Explanation: The monitoring subtask of DCS has abnormally terminated, either through abend or controlled termination (on purpose) because of environmental problems.

System action: The DCS application will be reinstated automatically. All jobs being managed by the failing DCS will be released during DCS reinstatement.

Operator response: Notify personnel responsible for support.

Programmer Response: Contact BMC Support. The system log and the DCS trace data set are the most useful pieces of information for problem diagnosis.

DTM7179I

DCS WARNING - MONITOR NOT RESPONDING


Explanation: A situation analogous to that triggering message DTM7178E. In this case the problem is more likely a loop or perpetual wait in the monitoring subtask.

System action: TMSS will detect that DCS is not responding and will terminate it.

Operator response: Notify personnel responsible for support.

Programmer Response: Contact BMC Support. The system log and the DCS trace data set are the most useful pieces of information for problem diagnosis.

DTM7180I

PARAMETER STATEMENT SYNTAX ERROR


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator. A parameter has been found is SYSIN that is not of the form keyword=value.

System action: The report program terminates with a return code 8.

User Response: Correct the statement and rerun.

DTM7181I

DUPLICATE PARAMETER SPECIFICATION


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator. The previous SYSIN parameter has been specified twice.

System action: The report program terminates with a return code 8.

User Response: Eliminate the statement duplication and rerun.

DTM7182I

INVALID PARAMETER KEYWORD


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator. The keyword to the left of the ‘=’ in the preceding SYSIN statement is invalid.

System action: The report program terminates with a return code 8.

User Response: Correct the statement and rerun.

DTM7183I

INVALID PARAMETER VALUE


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator. The keyword to the right of the ‘=’ in the preceding SYSIN statement is invalid.

System action: The report program terminates with a return code 8.

User Response: Correct the statement and rerun.

DTM7184I

report_type REPORT SUPPRESSED, DD STATEMENT MISSING


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator. The report_type is JOB or DATASET. A DD statement for the alternate report was present.

System action: The report program continues and will produce the alternate report. When the program terminates a return code of 4 is generated, unless errors are subsequently found.

User Response: If the specified report is required, add the corresponding DD statement and rerun (For the JOB report the DD statement name is DCSRJRPT; for the DATASET report the DD statement name is DCSRDRPT).

DTM7185I

NO REPORT DD STATEMENT SPECIFIED


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator.

System action: The report program terminates with return code 8. No reports are produced.

User Response: Add the required DD statement and rerun (For the JOB report the DD statement name is DCSRJRPT; for the DATASET report the DD statement name is DCSRDRPT).

DTM7186I

INSUFFICIENT MEMORY AVAILABLE


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator. There is insufficient virtual storage to produce the reports.

System action: The report program terminates with return code 8.

User Response: Increase the job region size, or reduce the amount of input data.

DTM7187I

MAXIMUM NUMBER OF items EXCEEDED


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator. “items” is one of JOBS, DATASETS, or HOLDERS. Certain program tables have overflowed.

System action: The report program terminates with return code 8.

User Response: Reduce the amount of input data.

DTM7188I

UNABLE TO OPEN file_type FILE


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator. “File-type” is one of INPUT, JOB REPORT, or DATASET REPORT.

System action: The report program terminates with return code 8.

User Response: Correct the associated DD statement—DCSRIN for INPUT, DCSRJRPT for JOB REPORT, or DCSRDRPT for DATASET REPORT. Rerun job.

DTM7189I

FAILURE READING INPUT FILE RECORD NUMBER number


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator. An I/O error has occurred.

System action: The report program terminates with return code 8.

User Response: Recover the DCSRIN File. Rerun job.

DTM7190I

INVALID DATA IN INPUT RECORD NUMBER number REASON: reason E


Explanation:
reason: Is one of the following:

  1. Invalid record cut time
  2. Duplicate sequence number
  3. Invalid reader on time
  4. Job id and name inconsistent
  5. Invalid record length

This message is written to SYSPRINT by the DTMDCSR report generator. A non-CMF record has been found in the DCSRIN input File.

System action: The report program terminates with return code 8.

User Response: Analyze the DCSRIN File. It is probably not a valid CMF File. Correct the JCL or the File and rerun.

DTM7191I

SEQUENCE ERROR AT INPUT RECORD NUMBER number


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator. The report program requires that its input data be sorted. The input is not in the required sort order.

System action: The report program terminates with return code 8.

User Response: Sort the input data correctly and rerun.

DTM7192I

FAILURE WRITING file_type REPORT FILE RECORD NUMBER number


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator. “file_type” is JOB or DATASET. An I/O error has occurred during a write operation.

System action: The report program terminates with return code 8.

User Response: Perform installation procedures addressing output I/O errors. Rerun job.

DTM7193I

DCS REPORT PROGRAM PROCESSING report - RETURN CODE code


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator, at the end of a run. Return code 0 indicates success. Return code 4 indicates warning, but reports were produced. Return codes greater than 4 indicate severe errors and no reports produced.

System action: The report program terminates with return code code.

User Response: If the return code is not 0, previous warning or error messages have been written to SYSPRINT. Analyze these, and rerun with corrections, if necessary.

DTM7194I

DCS REPORT PROGRAM PROCESSING ABORTED - RETURN CODE code


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator, at the end of a run. Return code 0 indicates success. A severe error has caused the report program to terminate prematurely.

System action: The report program terminates with return code code.

User Response: Previous warning or error messages have been written to SYSPRINT. Analyze these, and rerun with corrections, if necessary.

DTM7195I

INTERNAL ERROR - REASON CODE code


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator.

System action: The report program terminates with return code 12.

User Response: Previous warning or error messages may have been written to SYSPRINT. If so analyze these, and rerun with corrections. Report the problem to personnel responsible for support.

DTM7197I

NO CONTENTION OCCURRENCES IDENTIFIED


Explanation: This message is written to SYSPRINT by the DTMDCSR report generator. The report program has not been able to identify any contention incidents.

System action: The report program terminates with return code 12.

User Response: Probable input error. Check the input File to make sure that it has not been damaged, and that the period covered is long enough to include some contention incidents.

DTM7200I

JOB job-id NOT KNOWN TO MHS


Explanation:
job-id: is either the job name or JES2 job number, depending on which of these was entered on the command.
An MHS_hr DISPLAY or MHS_hr RELEASE command was entered, but the job name or job number specified is not know to the MHS Control File application. hr indicates the MHS hold category, such as OPER or TM.

System action: The command is ignored.

Operator response: Check to ensure that the correct job name or job number was entered.

Programmer Response: None.

DTM7201I

JOB job-id NOT HELD AS REQUESTED
or
NO JOBS HELD AS REQUESTED


Explanation:
job-id: is either the job name or JES2 job number, depending on which of these was entered on the command.
An MHS_hr DISPLAY or MHS_hr RELEASE command was entered, but the job or jobs are not associated with the MHS ID specified by the command. hr indicates the MHS hold category, such as OPER or TM.

System action: The command is ignored.

Operator response: Check to ensure that the correct job name or job number was entered.

Programmer Response: None.

DTM7202I

MHS data WRITTEN TO SYSOUT ddname


Explanation:

data: Indicates the data that was requested, and is one of:

TRACE – the MHS internal trace.

CID – the MHS Control File data.

ddname: Indicates the dynamically allocated DD name used to allocate the SYSOUT data set.

This is the response to an MHS SPIN command.

System action: Processing continues.

Operator response: None.

Programmer Response: None.

DTM7203I

JOB job-id HELD AS REQUESTED


Explanation:

job-id: is either the job name or JES2 job number, depending on which of these was entered on the command.

An MHS_hr HOLD command was entered, and the job has been held with the ID and notes specified. hr indicates the MHS hold category, such as OPER or TM.

System action: Processing continues.

Operator response: None.

Programmer Response: None.

DTM7204I

JOB job-id ALREADY HELD AS REQUESTED


Explanation:

job-id: is either the job name or JES2 job number, depending on which of these was entered on the command.

An MHS_hr HOLD command was entered, but the job has already been held. hr indicates the MHS hold category, such as OPER or TM.

System action: Processing continues.

Operator response: None.

Programmer Response: None.

DTM7205I

REQUESTED HOLD REMOVED FROM JOB job-id, nn MHS_hr HOLD(S) STILL APPLIED
or
REQUESTED HOLD REMOVED FROM JOB job-id, NO LONGER HELD BY MHS_hr

E xplanation:
job-id: is either the job name or JES2 job number, depending on which of these was entered on the command.
hr: indicates the MHS hold category, such as OPER or TM.
An MHS_hr RELEASE command was entered. If the job is still held by MHS_hr for other MHS IDs, nn indicates the number of MHS_hr holds still in effect.

System action: The specified MHS_hr hold is removed.

Operator response: None.

Programmer Response: None.

DTM7206I

MHS_hr DISPLAY
JOBID JOBNAME NUMBER OF MATCHING
MHS_hr HOLDS
jobno jobname nn
or
MHS_OPER DISPLAY
JOBID JOBNAME ID HOLDTIME JSYS CONSOLE NOTES
jobno jobname mhs-id hh:mm/yyyy.ddd sys console notes
or
MHS_TM DISPLAY
JOBID JOBNAME JSYS
jobno jobname sys
reason
Explanation:
hr: Indicates the MHS hold category, such as OPER or TM.
nn: Is the number of MHS_hr holds that match the MHS ID specified. If MHS ID was not specified, this is the total of all MHS_hr holds applied to the job.
mhs-id: Is the MHS ID specified when the MHS_hr hold was applied. If no MHS ID was specified, the default MHS ID value NONE is shown.
hh:mm/yyyy.ddd: Is the time and Julian date.
sys: Identifies the JES2 system on which the MHS_hr HOLD command was originally entered.
console: Identifies the console at which the MHS_hr HOLD was entered.
notes: Is 1-16 characters of text entered at the time the hold was applied.
reason: Explains the reason that Thruput Manager has applied the MHS_TM hold.

An MHS_hr DISPLAY command was entered. The first form of the message is displayed when the command requests information about all jobs (MHS_hr DISPLAY JOBS). The second form is displayed when the command requests information about a specific job (MHS_OPER DISPLAY job-id) or detailed information for all jobs (MHS_OPER DISPLAY JOBS). The third form s displayed when the command requests information about a specific job (MHS_TM DISPLAY job-id) or detailed information for all jobs (MHS_TM DISPLAY JOBS DETAILS).System action: None.Operator response: None.Programmer Response: None.

DTM7207I

MHS hr SUMMARY
LAST MHS COLD START : day-of-week month day, year AT hh:mm
LAST MHS WARM START : day-of-week month day, year AT hh:mm
CONTROL FILE UTILIZATION : used/total (nn.nn%)
MHS_hr HELD JOBS : nnnnn


Explanation:

hr: Indicates the MHS hold category, such as OPER or TM.
An MHS_hr DISPLAY SUMMARY command was entered.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7208I

JOB job-id NOT HELD, reason
job-id: is either the job name or JES2 job number, depending on which of these was entered on the command.

The MHS_OPER HOLD command was entered, but the job was not held.

System action: Processing continues.

Operator response: None.

Programmer Response: None.

DTM7210I

MHS DISPLAY
JOB# JOBNAME REASON
jes2# jobname why-job-is-held


Explanation: The MHS DISPLAY JOB or MHS DISPLAY JOBS command was entered. If a job is held for multiple reasons, there is a line displayed for each reason. For more detailed information, use the DISPLAY command that corresponds to the reason(s).

System action: Processing continues.

Operator response: None.

Programmer Response: None.

DTM7211I

NO JOBS MANAGED BY MHS


Explanation: The MHS DISPLAY command was entered, but no jobs are currently being managed by MHS.

System action: Processing continues.

Operator response: None.

Programmer Response: None.

DTM7212I

LAST MHS COLD START : day-of-week month day, year AT hh:mm
LAST MHS WARM START : day-of-week month day, year AT hh:mm
CONTROL FILE UTILIZATION : used/total (nn.nn%)
JOBS HELD OR MANAGED BY MHS : nnnnn
FOR reason1 : nnnnn
...
FOR reasonn : nnnnn


Explanation: The MHS DISPLAY SUMMARY command was entered. There is a count of jobs held or delayed by MHS for each reason. For more detailed information, use the DISPLAY command that corresponds to the reason(s).

System action: Processing continues.

Operator response: None.

Programmer Response: None.

DTM7213I

JOB jobname IS EXEMPT FROM MHS_VOL PROCESSING


Explanation: The job has been made EXEMPT from MHS_VOL processing by an MHS_VOL RELEASE command.

System action: Volume look-up at job initiation is bypassed, and the job is not delayed by MHS.

Operator response: None.

Programmer Response: None.

DTM7214I

JOB JOBjobnumber jobname RELEASED FROM MHS_VOL HOLD, reason


Explanation:
reason: Is one of the following explanations:

  • ALL VOLUMES AVAILABLE – all volumes required by the job are available on the system where the MHS_VOL delay was applied.
  • TM STARTUP – all jobs that had MHS_VOL delay applied by the system where Thruput Manager is initializing are now eligible to be selected.
  • TM SHUTDOWN – all jobs that had MHS_VOL delay applied by the system where Thruput Manager is terminating are now eligible to be selected.

Jobs that have had MHS_VOL delay applied are being made eligible for selection automatically.

System action: Restores the system affinity for the identified job.

Operator response: None.

Programmer Response: None.

DTM7215A

MHS CONTROL FILE DAMAGED, COLD START NECESSARY


Explanation: During initialization of the MHS Control File application, it was determined that the MHS Control File data was invalid.

System action: The MHS application is placed in an ‘ENABLED, *INACTIVE*’ state. The MHS Control File data is spun to SYSOUT for debugging purposes.

Operator response: Notify personnel responsible for support.

Programmer Response: Forward the MHS Control File SYSOUT data to MVS Solutions, then restart Thruput Manager specifying ‘CF=FORMAT(MHS)’.

DTM7216A

MHS CONTROL FILE VERSION MISMATCH, COLD START NECESSARY


Explanation: During initialization of the MHS Control File application, it was determined that the version and release of the MHS Control File is not supported by this level of the MHS application.

System action: The MHS application is placed in an ‘ENABLED, *INACTIVE*’ state. The MHS Control File data is spun to SYSOUT for debugging purposes.

Operator response: Notify personnel responsible for support.

Programmer Response: Forward the MHS Control File SYSOUT data to MVS Solutions, then restart Thruput Manager specifying ‘CF=FORMAT(MHS)’.

DTM7250I

XCFM data WRITTEN TO SYSOUT ddname


Explanation: This is a response to the XCFM SPIN command. The requested data has been written to the indicated DD name.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7251I

XCF MANAGED RESPONSE COLLECTION NOT SUPPORTED. ThruPut Manager XCF SERVICES SUBTASK TERMINATING.


Explanation: The XCF Services Subtask requires “XCF managed Response Collection” to communicate using the Cross System Coupling Facility (XCF). The system on which Thruput Manager is running does not support this feature.

System action: Terminates the XCF Services Subtask

Operator response: Notify systems programmer.

Programmer Response: Determine why the required support is not available.

DTM7252I

component LOAD FAILED FOR COMPONENT MODULE module - FUNCTION WILL NOT BE SUPPORTED


Explanation: The XCF Services Subtask could not load a required module.

System action: None.

Operator response: Notify personnel responsible for support.

Programmer Response: Determine why the required module could not be loaded.

DTM7253I

component SUBTASK HAS TERMINATED


Explanation: One of the components supported by the XCF Services Subtask has terminated unexpectedly.

System action: Stops processing requests for the component.

Operator response: Notify personnel responsible for support.

Programmer Response: Collect all available information concerning this problem and determine the cause.

DTM7254I

component HAS BEEN INACTIVATED DUE TO ERRORS


Explanation: The named component has encountered multiple failures and is no longer operational.

System action: Stops processing requests for the component.

Operator response: Notify personnel responsible for support.

Programmer Response: Collect all available information concerning this problem and determine the cause.

DTM7255I

component RECOVERY status


Explanation:
status: Is the recovery status and is one of:

  • ‘in progress’ indicating that recovery is proceeding.
  • ‘successful’ indicating that recovery has completed successfully.
  • ‘failed’ indicating that recovery has not been successful.

System action: None if recovery is successful, otherwise stops processing requests for the component.

Operator response: Notify personnel responsible for support.

Programmer Response: Collect all available information concerning this problem and determine the cause.

DTM7256I

component IS NOT RESPONDING


Explanation: The named component has not responded to a request from the XCF Services Subtask.

System action: The component is terminated but the XCF Services Subtask continues processing.

Operator response: Notify personnel responsible for support.

Programmer Response: Collect all available information concerning this problem and determine the cause.

DTM7257I

component FAILED DURING function PROCESSING, COMPONENT NOW INACTIVE


Explanation: The named component has failed while processing a request from the XCF Services Subtask.

System action: Stops processing requests for the component.

Operator response: Notify personnel responsible for support.

Programmer Response: Collect all available information concerning this problem and determine the cause.

DTM7258I

SYSPLEX COUPLE DATA SET LIMIT REACHED, reason.
ThruPut Manager XCF SERVICES SUBTASK TERMINATING.


Explanation:
reason: Indicates which limit has been reached, and is one of:

  • NO MORE GROUPS ALLOWED
  • NO MORE MEMBERS ALLOWED IN GROUP

These limits are defined in the Sysplex Couple Dataset.
The XCF Services Subtask attempted to place its XCF member in the active state, associating it with an XCF group by issuing an IXCJOIN, but this was not possible because an XCF limit has been reached. This is accompanied by IBM message IXC700E.

System action: The XCF Services Subtask terminates.

Operator response: Notify personnel responsible for support.

Programmer Response: See to documentation of IBM message IXC700E for a description of action to be taken.

DTM7259I

sysplex_service ERROR. RC=X’return_code’, RS=X’reason_code’


Explanation: The named XCF service returned an unexpected return code and reason code.

System action: The XCF Services Subtask terminates.

Operator response: Notify personnel responsible for support.

Programmer Response: Examine the return code and reason code to determine the cause of the failure.

DTM7260I

sysplex_service ERROR. RC=X’return_code’, RS=X’reason_code’


Explanation: The named XCF service returned an unexpected return code and reason code.

System action: The XCF Services Subtask continues processing.

Operator response: None.

Programmer Response: None.

DTM7261I

ThruPut Manager XCF SERVICES SUBTASK action COMPLETE


Explanation:
action: Is the completed action, and is one of:

  • INITIALIZATION
  • SHUTDOWN

This message is informational only.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7262I

MEMBER member IS NOT DEFINED


Explanation: The XCFM DISPLAY MEMBER member was entered, but the indicated member is not defined to the XCF Services Subtask.

System action: The XCF Services Subtask continues processing.

Operator response: Ensure that the member name was specified correctly. Use the Thruput Manager command XCFM DISPLAY MEMBERS ALL to obtain a list of all members defined to the XCF Services Subtask.

Programmer Response: None.

DTM7263I

XCFM MEMBER DISPLAY
NAME STATUS CFPLEX JESPLEX
membername status cfplex jesplex
CONTROL FILE=control-File name
JES2 NODE=nodename
SPOOL=spool-File name
or
NAME STATUS CFPLEX JESPLEX
membername status cfplex jesplex
membername status cfplex jesplex
... ... ... ...


Explanation:
membername: Is the internally assigned member name for the system in the XCF group.
status: Is the XCF status of the member, and is one of:

  • ACTIVE
  • INACTIVE

cfplex: Indicates whether the member is sharing the Control File with other systems in the XCF group, and is one of:

  • YES
  • NO
  • --- (when the ambient member is displayed)

jesplex: Indicates whether the member is sharing the MAS with other systems in the XCF group, and is one of:

  • YES
  • NO
  • --- (when the ambient member is displayed)

The XCFM DISPLAY MEMBER or XCFM DISPLAY MEMBERS command was entered.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7264I

XCFM TASK DISPLAY
MEMBER membername
TASK NAME STATUS STATE
subtask status X’info’
MESSAGES SENT : nnnnn
MESSAGES RECEIVED : nnnnn
AVAILABLE ON MEMBER membername ,STATE=X’info’
MESSAGES SENT : nnnnn
MESSAGES RECEIVED : nnnnn


Explanation:

System action: membername: Is the internally assigned member name for the system in the XCF group.
subtask: Is the XCFM subtask name.
status: Is the XCF status of the member, and is one of:

  • ACTIVE
  • INACTIVE

info: Is a two-byte hexadecimal representation of status bits for the subtask.
The XCFM TASK DISPLAY command was entered. If the subtask name was not specified, only the status of XCFM subtasks on the current system is displayed. If the subtask name is specified, additional lines display counts showing the communications with the same XCFM subtask running under other Thruput Manager.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7265I

DIAGNOSTIC TRACE FOR XCF APPLICATION WAS SPUN TO DDNAME ddname


Explanation: This message is issued to signal the automatic tracing of an XCF application (DCS, PCSM or PCSX). Automatic tracing is being performed either due to an abend in the application or the detection of an unusual event.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7266I

TMSS UNABLE TO CONTINUE WITHOUT taskname SERVICES


Explanation: The XCF Services Subtask indicated in the message text has failed repeatedly and recovery has proved unsuccessful. See messages DTM7253I and DTM7254I.

System action: Since the specified subtask is considered critical to the proper functioning of Thruput Manager, the TMSS started task is terminated.

Operator response: Notify personnel responsible for support.

Programmer Response: Collect all available information concerning this problem and determine the cause.

DTM7267I

ThruPut Manager XCF SERVICES SUBTASK WAITING FOR IXCMGO COMPLETION


Explanation: The XCF Services Subtask is waiting to be notified of IXCMSGO (MSGACCESS=ASYNC) completion.

System action: This message is issued every 30 seconds until notification of IXCMSGO completion.

Operator response: Notify personnel responsible for support.

Programmer Response: If message continues, restart TMSS on the affected system.

DTM7268I

TIME REQUESTED IS OUT OF RANGE


Explanation: An SLM SPIN TRACE command was issued that contains the TIME() keyword. The TIME requested for an SLM trace is outside of the actual range of trace data currently available. The message will not be issued if there is ANY data available in the range.

System action: The SLM SPIN TRACE command is ignored since it is not possible to accommodate the request.

Operator response: None.

Programmer Response: None.

DTM7269I

SPIN OF TRACE SCHEDULED


Explanation: This message indicates that the TRACE has been queued to be spun by a service. Related message is DTM8214I.

System action: The trace should be spun by the service routine very shortly after the message.

Operator response: None.

Programmer Response: None.

DTM7271E

JESPLEX member jsid is not sharing the same Control File (CF).
ThruPut Manager processing may be affected.
Local CF is localCFname
jsid CF is jsidCFname


Explanation:
jsid: is the JES2 member name which is not sharing the same Control File as the system issuing the DTM7271E message.
localCFname: is the name of the Control File on the system issuing the DTM7271E message.
jsidCFname: is the name of the other JES2 system’s Control File.
This message is a warning of likely future problem.


Explanation: The JES2 member, indicated in the message text by jsid, is a member of the same JES2 complex (JESplex) but does not share the Thruput Manager Control File (CF). Related message is DTM6016I.

System action: None.

Operator response: None.

Programmer Response: Correct “FILE CF” TM initialization statement and re-start the corresponding TM started task.

DTM7272I

Diagnostic trace for XCF services subtask was spun to ddname ddname


Explanation: The XCF services subtask detected an unexpected event and spins its internal trace to aid in debugging the potential problem. Related message is DTM7260I.

System action: None.

Operator response: None.

Programmer Response: Forward trace to MVS Solutions Support.

DTM7273I

Plex information was not received from member memname, retrying Plexinfo request.


Explanation: During Thruput Manager started task initialization (TM stc, TM/PCS stc), the started tasks exchange messages via XCF, describing vital information. The message indicates that this did not occur with the member described in the message.

System action: The XCF internal trace is spun (see message DTM7272I).

Operator response: None.

Programmer Response: Forward trace to MVS Solutions Support.

DTM7274E

IP ip-address connected to Sysplex syspname, Jesplex jespname, does not match TM TCPIP definitions


Explanation: TMSS has initiated a connection to another JESplex and received a response indicating that the remote JESplex is not the one defined using either the TM TCPIP ADD statement or command for the indicated IP address.
ip-address the IP address to which the connection was made
syspname the Sysplex name returned from the remote JESplex
jespname the JESplex name returned from the remote JESplex

System action: The TCP/IP connection is closed.

Operator response: Inform the personnel at your installation responsible for the support.

Programmer Response: Correct/supply the definition for the indicated IP address. To correct, use the TM TCPIP DELETE command to remove the definition which had the error. Use the TM TCPIP ADD command to supply the correct definition. If the definition came from a TM TCPIP initialization statement, correct it as well.

DTM7275E

IP ip-address connected to Sysplex syspname, Jesplex jespname, does not match TM TCPIP definitions


Explanation: TMSS has received a connection from another JESplex that indicates that the remote JESplex is not the one defined using either the TM TCPIP ADD statement or command for the indicated IP address.
ip-address the IP address to which the connection was made
syspname the Sysplex name supplied by the remote JESplex
jespname the JESplex name supplied by the remote JESplex

System action: The TCP/IP connection is closed.

Operator response: Inform the personnel at your installation responsible for the support.

Programmer Response: Correct/supply the definition for the indicated IP address. To correct, use the TM TCPIP DELETE command to remove the definition which had the error. Use the TM TCPIP ADD command to supply the correct definition. If the definition came from a TM TCPIP initialization statement, correct it as well.

DTM7276I

Unable to connect to Sysplex syspname, Jesplex jespname, using Port portno, IP n.n.n.n, reason


Explanation: This message indicates a potential error in a TM TCPIP definition. In the message text:
syspname indicates the Sysplex name specified by the TM TCPIP definition.
jespname indicates the Jesplex name specified by the TM TCPIP definition.
portno indicates the port number specified by the TM TCPIP definition.
n.n.n.n indicates the IP address specified by the TM TCPIP definition.
reason indicates the reason Thruput Manager was unable to connect and is one of the following:

  • Timeout indicates a response was not received within the time allotted by Thruput Manager. Timeout might indicate that there is no error in the TM TCPIP definition and that the system corresponding to the IP address is not active
  • ErrNo=n indicates the TCP/IP error number returned by CONNECT service. Its meaning can be determined from IBM space IP Sockets Application Programming Interface Guide and Reference, Appendix B "Socket Call Error Return Codes". An error number of 61 likely indicates that the Thruput Manager started task is not active on the system corresponding to the IP addressSystem action: If there is another TM TCPIP definition(s) to the named Sysplex, Jesplex, it will be used.

Operator response: None.

Programmer Response: This might be a normal situation where the system corresponding to the IP address is down or the Thruput Manager started task is down on that system. If neither is the case, verify that the IP address specified is correct.

DTM7277I

XCFM Connection Display
Member Sysplex Jesplex GRS Name IP Connection
memname sname jname gname n.n.n.n type


Explanation: This message is issued in response to Thruput Manager command "XCFM DISPLAY CONNECTIONS". In the message text
memname indicates the internally assigned member name
sname indicates the Sysplex name
jname indicates the Jesplex name
gname indicates the GRS name of the system
n.n.n.n indicates the IP address of the system
type indicates the connection type and is either "Client" or "Server"

System action: None

Operator response: None

Programmer Response: None

DTM7278I

TCPIP TYPE=ezasmisvc failed, failrsn


Explanation: This message is issued when Thruput Manager TCP/IP initialization fails. In the message text
ezasmisvc is the EZASMI macro service being called.
failrsn indicates the reason for the failure. The failure reason may be text, for known failures, or "ErrNo=n" for undetermined failures. "ErrNo=n" indicates the TCP/IP error number returned by the service called. Its meaning can be determined from the IBM space IP Sockets Application Programming Interface Guide and Reference, Appendix B Socket Call Error Return Codes.

System action: This message will be deleted when TCP/IP initialization is successful.

Operator response: None

Programmer Response: Correct the error associated with the failure reason.

DTM7300I

HOLD_UNTIL JECL STATEMENT, REQUESTED A HISTORICAL DATE - yyyy.ddd


Explanation: The date indicated in JTS is past.

System action: This message can either be followed by a warning or the is job failed, depending on the installation options.

Operator response: None.

Programmer Response: If it resulted in a job failure, then correct the statement so that the date represents a future date.

DTM7301I

HOLD_UNTIL JECL STATEMENT, REQUESTED A TIME EARLIER TODAY - hh:mm


Explanation: The time indicated in JTS is past.

System action: None. This message is a warning.

Operator response: None.

Programmer Response: None.

DTM7302I

HOLD_UNTIL JECL STATEMENT, REQUESTED A DATE MORE THAN nnn DAYS AHEAD -yyyy.ddd


Explanation: The DATE indicated in JTS exceeds the maximum allowed.

System action: This can be a warning, or the job can be failed, depending on installation options.

Operator response: None.

Programmer Response: Correct the statement so that the date is within the value nnn.

DTM7330E

application command COMMAND FAILED, DUPLICATE JOB NAME


Explanation: There are, at least, two jobs with the same name.

System action: No further action is taken by the command processor.

Operator response: Identify the job by job number.

Programmer Response: None.

DTM7331I

application command COMMAND FAILED, JOB NOT ELIGIBLE


Explanation: The job is not awaiting execution.

System action: No further action is taken by the command processor.

Operator response: Verify that the job name or number was correct.

Programmer Response: None.

DTM7332E

JTS RESET, INVALID DATE SYNTAX


Explanation: Incorrect DATE syntax, or the date specified is beyond the maximum number of days specified by MAXDAYS on the JTS OPTIONS initialization statement.

System action: No further action is taken by the command processor.

Operator response: Reenter with a valid DATE parameter.

Programmer Response: None.

DTM7333E

JTS RESET, INVALID TIME SYNTAX


Explanation: Incorrect TIME syntax.

System action: No further action is taken by the command processor.

Operator response: Reenter with correct TIME parameter.

Programmer Response: None.

DTM7400I

AUTOMATION FILE DOES NOT DESCRIBE THE AMBIENT JES2 NODE
DEFINED: defnode,defspds,defspvp
AMBIENT: ambnode,ambspds,ambspvp


Explanation: defnode: is the name of the JES2 node provided in the DBS definition.defspds: is the name of the JES2 spool data set provided in the DBS definition.
defspvp: is the JES2 spool volume prefix provided in the DBS definition.
ambnode: is the name of the JES2 node provided by JES2PARM.
ambspds: is the name of the JES2 spool data set provided by JES2PARM.
ambspvp: is the JES2 spool volume prefix provided by JES2PARM.
The scope ofthe Automation File is the JES2 node, but the Automation File being loaded does not describe the
ambient (i.e. local) JES2 node.

System action: Further validation of the new Automation File stops and the load fails.

Operator response: Notify personnel responsible for support.

Programmer Response: Ensure that the JES2 node information in the Automation File is correct.

DTM7401I

AUTOMATION FILE INCLUDES MEMBER jes2name WHICH IS NOT DEFINED TO JES2


Explanation: The scope of the Automation File is the JES2 node, but the Automation File being loaded includes information for a system that is not defined to JES2.

System action: The invalid system is ignored and validation of the Automation File continues.

Operator response: Notify personnel responsible for support.

Programmer Response: Verify the JES2 system name displayed in the message text, ensuring that the name was specified correctly.

DTM7402I

pool
DEFINED COUNT=ddd,ADJUSTED COUNT=aaa
JES2 MEMBER DEVICE COUNT ALTERED FOR THIS POOL
The following line appears only if the installation has chosen to use DBS Work Groups
JES2 MEMBER WORK GROUP COUNTS ALTERED FOR THIS POOL
The following line appears only if the installation has a Write To Operator(WTO) message associated with the named pool:
installation.message


Explanation:
pool: is the DBS Drive Pool that is affected.
ddd: is the number of devices defined to the Pool by your installation.
aaa: is the number of devices successfully verified by DBS.
installation.message: is a message defined by your installation.

During load of the Automation File, one or more device numbers provided by the installation failed verification. As a result, device counts for this system have been adjusted. This message is issued only if the number of devices successfully verified is less than the number defined for this system.

System action: The Drive Pool counts are adjusted as shown and validation of the DBS Configuration continues.

Operator response: Notify personnel responsible for support.

Programmer Response: See the related message DTM7404I to determine which devices were defined incorrectly.

DTM7403I

pool
DEFINED COUNT=ddd,ADJUSTED COUNT=aaa
JESPLEX DEVICE COUNT ALTERED FOR THIS POOL


Explanation:
pool: is the DBS Drive Pool that is affected.
ddd: is the number of devices defined to the Pool by your installation.
aaa: is the number of devices successfully verified by DBS.
During load of a DBS Configuration, one or more device numbers provided by the installation failed verification. As a result, device counts for the JESPLEX have been adjusted. This message is issued only if the number of devices successfully verified is less than the number defined for the JESPLEX.

System action: The Drive Pool counts are adjusted as shown and validation of the DBS definition continues.

Operator response: Notify personnel responsible for support.

Programmer Response: See the related message DTM7404I to determine which devices wee defined incorrectly.

DTM7404I

pool
DEVICE NUMBER device FAILED VERIFICATION, reason


Explanation:
pool: is the DBS Drive Pool that is affected.
device: is the device number that failed verification.
reason: explains why the device failed verification and is one the following:

  • NOT DEFINED — the indicated device number is not defined.
  • NOT DEFINED AS TAPE — the indicated device number is not defined as a tape device.
  • NOT SPECIFIED TYPE OF TAPE — the indicated device number is not defined as the specified type of tape.
  • NOT INCLUDED IN ESOTERIC — the indicated device number is not within the scope of the esoteric unit name.
  • ESOTERIC NOT DEFINED — the esoteric unit name to which the indicated device number belongs, is not defined.
  • VENDOR INFO UNAVAILABLE — the expected vendor (e.g. IBM, StorageTek, C/A, EMC) information is not available.
  • NOT INCLUDED IN NAMED LIBRARY — the indicated device number is not included in the named IBM Library.
  • NOT VTFM VIRTUAL DEVICE — the indicated device number is not a EMC VTFM virtual device. This is determined by using information provided by the installation through the TM VTFM initialization statement.
  • NOT SPECIFIED STK DEVICE TYPE — the indicated device number is not the specified StorageTek device type. This is determined by using the SLSXCAL interface to query the StorageTek software.
  • NOT INCLUDED IN NAMED ACS — the indicated device number is not included in the named StorageTek ACS. This is determined by using the SLSXCAL interface to query the StorageTek software.
  • NOT STK ACS DEVICE — the indicated device number is not attached to a StorageTek ACS. This is determined by using the SLSXCAL interface to query the StorageTek software.
  • NOT DEFINED TO JES2 MEMBER — the indicated device number is defined to DBS at the JESplex level but not at the JES2 member level. It is defined as tape in the ambient system’s I/O definition (IODF).
  • DEVICE IS BOXED — the device UCB has the flag UCBBOX on indicating that the device has been BOXED. A VARY xxxx,OFFLINE,FORCE will cause this condition.
  • NO PATHS AVAILABLE TO DEVICE — indicates that the UCB bit UCBNOPTH OR UCBNOCON is on and there is no path allowing the device to be accessed at the moment.
  • DEVICE WAS VARIED UNAVAILABLE

During load of a new DBS Configuration, the device number provided by the installation failed verification.
NOTE: Verification is performed using the I/O configuration of the system where the DBS Configuration is being loaded.

System action: The Drive Pool counts are adjusted as shown in accompanying messages DTM7402I, and DTM7403I and validation of the DBS Configuration continues.

Operator response: Notify personnel responsible for support.

Programmer Response: See the related message DTM7402I or DTM7403I. Take appropriate action to define the device correctly.

DTM7405I

pool
internal.error.description


Explanation: Verification of the DBS Configuration found an internal error

System action: Validation of the DBS Configuration continues, but the Configuration is not loaded.

Operator response: Notify personnel responsible for support.

Programmer Response: Collect the complete message text and call support.

DTM7406I

pool
user.error.description


Explanation:
user.error.description: is a description of the error, and is one of:

  • POOL NOT MANAGED. NO DEVICES ASSOCIATED WITH ESOTERIC — This error is specific to an Installation Pool and indicates that the Esoteric unit name specified has no devices associated with it on the system where the DBS Configuration is being loaded.
  • POOL NOT MANAGED. ESOTERIC NOT DEFINED — This error is specific to an Installation Pool and indicates that the Esoteric unit name specified is not defined on the system where the /DBS Configuration is being loaded.
  • POOL NOT MANAGED. ESOTERIC HAS UNSUPPORTED DEVICES — This error is specific to an Installation Pool and indicates that the Esoteric unit name specified has unsupported devices associated with it. DBS only supports tape devices.

Verification of the DBS Configuration found an error in the DBS definition. The error is specific to the system on which the Configuration is being loaded.

System action: The affected Pool is ignored and validation of the DBS Configuration continues.

Operator response: Notify personnel responsible for support.

Programmer Response: Determine the cause of the error and correct.

DTM7407I

ACTIVATE result. [info]


Explanation:
result: indicates the success or failure of the command and is either COMPLETE or FAILED.
info: If COMPLETE, is either blank or contains WARNING MESSAGE(S) ISSUED. In either case, the specified Policy was successfully activated. See related messages DTM7401I, DTM7403I, and/or DTM7404I for more information.

If FAILED, contains one of the following: BASE POLICY IS ALREADY IN EFFECT — the command DBS ACTIVATE **BASE** was issued, but the base Policy is already in effect.

  • SPECIFIED POLICY DOES NOT EXIST IN ACTIVE CONFIGURATION — The Policy name specified on the DBS ACTIVATE command does not exist in the active DBS Configuration.
  • NO CONFIGURATION CURRENTLY LOADED — The initial DBS Configuration has not been loaded.
  • CONFIGURATION IS NOT BASED ON RUNNING CONFIGURATION — This is a timing issue related to simultaneous use of the DBS dialog and the DBS ACTIVATE command. Try the command again, if desired.
  • After a JESPLEX change, you must activate the BASE policy — If a JES2 system is added, deleted, or removed from the JESPLEX configuration via the “TM Automation Services” dialog, the DBS Base policy must be re-activated before any other policy can be activated.

A DBS ACTIVATE command was issued. This message describes the results.

System action: If the response is COMPLETE, DBS uses the Policy specified in the command. If FAILED, the command is ignored.

Operator response: If the response is FAILED, notify personnel responsible for support.

Programmer Response: Check any warning messages issued in response to the command.

DTM7408I

VERIFY result. [info]


Explanation:
result: indicates the success or failure of the command and is either COMPLETE or FAILED.
info: If COMPLETE, is either blank or contains WARNING MESSAGE(S) ISSUED. See related messages DTM7401I, DTM7403I, and/or DTM7407I for information regarding any warning messages issued.

If FAILED, contains one of the following: ERROR MESSAGE(S) ISSUED — See related messages DTM7401I, DTM7403I, and/or DTM7404I for more information.

  • SPECIFIED DATA SET WAS NOT INITIALIZED BY DBS — The data set name specified on the DBS VERIFY command was not initialized by the DBS dialog.
  • SPECIFIED DATA SET DOES NOT HAVE NEXT CONFIGUR ATION — The Automation File specified by the command does not have a NEXT Configuration to be verified.

A DBS VERIFY command was issued. This message describes the result.

System action: None.

Operator response: None.

Programmer Response: Check any warning messages.

DTM7409I

ALTER result. [info]


Explanation:
result: indicates the success or failure of the command and is either COMPLETE or FAILED.

info: If FAILED, contains JOB NOT KNOWN TO DBS.

A DBS ALTER command was issued. This message describes the results.

System action: If COMPLETE, the DBS priority for the job is altered as specified. If FAILED, the command is ignored.

Operator response: If FAILED, ensure that the correct job number was specified.

Programmer Response: None.

DTM7410I

DBS DEVICE DISPLAY
NUMBER DBS STATUS REASON
nnnn status reason


Explanation:
nnnn: is the device number in hexadecimal.
status: is the DBS status of the device: AVAILABLE indicates that DBS treats the device as available for allocation requests.

  • UNAVAILABLE indicates that DBS treats the device as unavailable for allocation requests. The text in the REASON column will explain the specific reason.
  • NOT DEFINED indicates that the device has not been defined to DBS.

reason: is an explanation for exclusion of this allocation from DBS pool counts:

  • NOT DEFINED TO DBS
  • NOT DEFINED AS TAPE
  • NOT SPECIFIED IN CORRECT POOL
  • VENDOR INFO UNAVAILABLE
  • NOT INCLUDED IN ESOTERIC
  • ESOTERIC NOT DEFINED
  • NOT INCLUDED IN NAMED LIBRARY
  • NOT VTFM VIRTUAL DEVICE
  • NOT SPECIFIED STK DEVICE TYPE
  • NOT INCLUDED IN NAMED ACS
  • NOT STK ACS DEVICE
  • DEVICE IS BOXED
  • NO PATHS AVAILABLE TO DEVICE
  • NOT DEFINED TO JES2 MEMBER
  • OPERATOR DBS SET COMMAND
  • DEVICE NOT IN SYSTEM CONFIG
  • DEVICE NOT IN DBS CONFIG
  • DEVICE VARIED UNAVAILABLE

A DBS DISPLAY DEVICE or DBS SET DEVICE command was issued. This message describes the result of the command.

System action: If the command was DBS SET DEVICE, the device status is set as shown in the response

.Operator response: If the DBS status is NOT DEFINED and the correct device number was specified, notify personnel responsible for support so that the DBS Configuration can be updated to include the specified device.

Programmer Response: If the DBS status is NOT DEFINED and the correct device number was specified, update the TM.DBS Configuration to include the device.

DTM7411I

REEVALUATE COMPLETE


Explanation: A DBS REEVALUATE command was issued. This message describes the results of the command.

System action: None.

Operator response: See the related messages DTM7402I, DTM7404I, and/or DTM7406I for more information.

Programmer Response: See the related messages DTM7402I, DTM7404I, and/or DTM7406I for more information.

DTM7412I

DBS SUMMARY DISPLAY
Control Area Size = nn,nnn,nnn Bytes
Amount Used = nn,nnn,nnn Bytes (nn %)
Job Count = nnnnnn
Last Cold Start = day mmm dd, yyyy hh:mm:ss
Configuration Name = configname 


    • Description = description
      Node Name = nodename
      Spool DSN = spool.dsn
      Spool Volume Prefix = prefix
      BASE Install = day mmm dd, yyyy hh:mm:ss
      Last Install Type = type
      Last Install = day mmm dd, yyyy hh:mm:ss
      Last Modification = day mmm dd, yyyy hh:mm:ss 
    • by TSO Userid = userid
      Install Dataset = install.dsn 
    • on Volser = volser
      Policy Name = WEEKDAY
      Verified Devices = nnnn
      SMF Recording = [ENABLED Type nnn | DISABLED]


Explanation: A DBS DISPLAY SUMMARY command was issued.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7413I

DBS Installation complete for Config/Policy - WG=[YES | NO]


Explanation: This message is produced when a DBS Configuration is installed. This can happen as a result of ‘Activating’ a Policy or base Configuration either explicitly (command) or implicitly (recycle of the application).

System action: None.

Operator response: None.

Programmer Response: None.

DTM7414I

Transition from Previous DBS Policy is Complete


Explanation: When a DBS Policy is activated there could be jobs already executing that would not have been executing if they were submitted after the new Policy was activated. These jobs are said to be in transition. They could be allowed to go into step execution even though the pools cannot accommodate them. This message is issued when there are no such jobs still executing (i.e. all jobs executing are accommodated in the current pools definition).

System action: None.

Operator response: None.

Programmer Response: None.

DTM7415I

DBS Entering Policy Transition Mode


Explanation: When a DBS Policy is activated there could be jobs already executing that would not have been executing if they were submitted after the new Policy was activated. These jobs are said to be in transition.They could be allowed to go into step execution even though the pools cannot accommodate them. This message is issued only if there are any such jobs in the system when the activation takes place.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7416I

DBS DRIVE POOL COUNT EXCEEDED: REQUIRED - nnn, MAXIMUM OF - nnn


Explanation: This message is sent to SYSLOG when a job requests more devices from a Drive Pool than are available. See the accompanying message DTM7417I for the name of the affected Drive Pool.

System action: The job is cancelled with a JECL error, unless the JAL statement DBS HOLD UNAVAILABLE_UNITS(YES) has been issued. In that case, the job is held.

Operator response: None.

Programmer Response: None.

DTM7417I

DRIVE POOL NAME:
poolname


Explanation: This message accompanies DTM7416I, naming the Drive Pool for which the request exceeds resources.

System action: See DTM7416I.

Operator response: None.

Programmer Response: None.

DTM7418I

INVALID DBS WORKGROUP ASSIGNED BY JAL - invalid,
DEFAULT ASSUMED


Explanation: JAL attempted to assign an invalid Work Group to the job, so the default Work Group is assigned instead.

System action: Assign the default Work Group to the job.

Operator response: Notify personnel responsible for support.

Programmer Response: Check JAL for invalid Work Group names.

DTM7419I

WARNING: AUTOMATION FILE NAME MISMATCH
TM PARMS DSNAME=tm.dsname VOLSER=tmvol
DBS DSNAME=dbs.dsname VOLSER=dbsvol


Explanation:
tm.dsname: is the data set name specified by the FILE AF Thruput Manager initialization statement.
tmvol: is the volume serial number specified by the FILE AF Thruput Manager initialization statement.
dbs.dsname: is the data set name specified by the active DBS Configuration.
dbsvol: is the volume serial number specified by the active DBS Configuration.
This is a warning that the name and volume serial number specified on the FILE AF statement does not match the name and volume serial number contained in the active DBS Configuration.

System action: None.

Operator response: Notify personnel responsible for support.

Programmer Response: Resolve the conflict.

DTM7420I

jobname IN DBS STEP WAIT
COUNT IND POOLNAME
nnn ind poolname


Explanation:
jobname: is the name of the job experiencing the shortage.
nnn: is the number of devices required for this step as determine by Job Analysis.
ind: is an indicator showing at which level the shortage is occurring, and is one of:
J — the JESPLEX level,

  • S the system level.
  • W the Work Group level.

poolname: is the Drive Pool that is having the shortage.
The job step has been put in a wait state prior to allocation because DBS has determined that one or more Drive Pools that are required by the step do not have sufficient devices to provide the required devices.
The message is issued after the step has waited 1 minute. The message is repeated once every 5 minutes after that. As soon as all the device requirements are available the job is released.

System action: Holds the job until the shortage is relieved, then releases the job.

Operator response: The job can be removed from the wait state and forced through to allocation without regard to the availability of devices by using the DBS ALTER command with the NO_DELAY_AT_JOB_SELECTION keyword.

Programmer Response: None.

DTM7421A

stcname - DBS DETECTED INSUFFICIENT DEVICES AVAILABLE


Explanation: This message applies only to started tasks. DBS has determined that the STC requires more devices than are currently available. Allowing the STC to proceed could result in an allocation problem. This message is accompanied by DTM7422A.

System action: Issues message DTM7422A and waits for a response.

Operator response: See related message DTM7422A.

Programmer Response: None.

DTM7422A

REPLY ‘WAIT’,’IGNORE’,’CANCEL’,’RETRY

’
Explanation: This message follows DTM7421A. Allowing the STC to proceed could result in an allocation problem.

System action: Depends on the response:

  • WAIT—the STC enters a wait state until the required device(s) are available.
  • IGNORE—the STC continues into allocation.
  • CANCEL—the STC is cancelled.
  • RETRY—DBS retries to see if the required device(s) are now available.
  • If a reply is not entered within two minutes, DBS deletes the WTOR and re-checks the device availability.

Operator response: Enter a reply as requested.

Programmer Response: None.

DTM7423I

‘RESERVE’ JECL STATEMENT, INVALID OR UNMANAGED POOL IGNORED - poolname


Explanation: A //*+DBS RESERVE JECL statement specified a Pool Name that is not valid ot is not managed.

System action: The JECL statement is ignored.

Operator response: None.

Programmer Response: Check the //*+DBS RESERVE JECL statement for typographical errors, or remove the request for the invalid or unmanaged Drive Pool.

DTM7424I

NOTE **** DBS Activated in PASSIVE MODE


Explanation: A DBS Policy was activated and Passive mode was selected.

System action: Processing continues. DBS continues to evaluate jobs using the Configuration and Policy that was activated, but does not prevent any job or step from beginning execution. Monitors, displays, and reports still reflect activity as though DBS were operating in normal mode.

Operator response: None.

Programmer Response: None.

DTM7425W

NOTE ** Job jobname(jobno) will be MHS held if Configuration is activated


Explanation: This warning message is issued when an attempt is made to activate the NEXT Configuration, but DBS detects that at least one Drive Pool does not contain enough devices to meet the job’s requirements.

System action: If the Configuration is activated, the specified job is placed in MHS_TM hold for DBS.

Operator response: None.

Programmer Response: Check the Configuration for omitted devices.

DTM7426W

WARNING: ALLOCATED [SHARED] DBS DEVICE device-number error-text


Explanation:
device-number: is the device number in hexadecimal.
error-text: is one of the following:

  • NOT DEFINED
  • NOT DEFINED AS TAPE
  • NOT SPECIFIED IN CORRECT POOL
  • VEDOR INFO UNAVAILABLE
  • NOT INCLUDED IN ESOTERIC
  • ESOTERIC NOT DEFINED
  • NOT INCLUDED IN NAMED LIBRARY
  • NOT VTFM VIRTUAL DEVICE
  • NOT SPECIFIED STK DEVICE TYPE
  • NOT INCLUDED IN NAMED ACS
  • NOT STK ACS DEVICE
  • DEVICE IS BOXED
  • NO PATHS AVAILABLE TO DEVICE
  • NOT DEFINED TO JES2 MEMBER
  • OPERATOR DBS SET COMMAND
  • DEVICE NOT IN SYSTEM CONFIG

The message is a WARNING. It is issued the first time that the the operating system allocates a DEVICE to a job, and the DEVICE is known to DBS but has an error on this system. The possible errors are specified by the error-text above.

NOTE: The system remembers that the message has been issued for the specified device. The message is issued only once. The message is not remembered by the system after DBS (or TM) recycle.

System action: Processing continues. The allocated device may not be affecting the DBS pool counts as it should because of the error.

Operator response: Notify personnel responsible for support.

Programmer Response: If there a reason that the designated device should not be getting this message, restart DBS and check if the device is still in error.

DTM7427I

VVS STAGING WAITING FOR POOL poolname


Explanation: Virtual Volume Staging is waiting for a device in the DBS pool poolname. The job step has been put in a wait state prior to allocation because DBS has determined that one or more Drive Pools that are required by the step do not have sufficient devices to provide the required devices.
The message is issued after the step has waited 1 minute. The message is repeated once every 5 minutes after that. As soon as all the device requirements are available the job is released.

System action: Holds the job until the shortage is relieved, then releases the job.

Operator response: The job can be removed from the wait state and forced through to allocation without regard to the availability of devices by using the DBS ALTER command with the NO_DELAY_AT_JOB_SELECTION keyword.

Programmer Response: None.

DTM7428I

poolname
DEVICE NUMBER nnnn reason


Explanation: Indicates that the condition that caused the device to be unusable by DBS no longer exists. This message is issued by DBS when a device that was previously BOXED, VARIED UNAVAILABLE or had NO PATH changes state to NOT BOXED, NOT VARIED UNAVAILABLE or to having a PATH AVAILABLE. DBS detects these conditions by sampling the devices at specified intervals.

System action: The device becomes available to the DBS pool in which it was defined.

Operator response: None.

Programmer Response: None.

DTM7430W

n jobs held by MHS for DBS Device Pools
n: number of jobs


Explanation: Jobs that cannot run because they require more devices than the number of devices assigned to DBS.

System action: DBS has put jobs in MHS hold.

Operator response: Verify if the proper DBS Policy is in effect.

Programmer Response: None.

DTM7433I

NO DBS CONFIGURATION IS CURRENTLY INSTALLED


Explanation: This message is produced at DBS start up if there is no active DBS Configuration/Policy.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7500I

JSS TABLE LOADED: DSNAME=dsname [MEMBER=member]


Explanation: Issued in response to a TBL REFRESH JSS command. This message indicates that the named table was loaded successfully.

System action: The JSS table is loaded.

Operator response: None.

Programmer Response: None.

DTM7501I

** EMPTY ** JSS TABLE LOADED: DSNAME=dsname [MEMBER=member]


Explanation: The table specified by the TBL REFRESH JSS command or the TBL LOAD JSS initialization statement was either empty or contained only blank or commented statements.

System action: Processing continues.

Operator response: Notify personnel responsible for support.

Programmer Response: Ensure that the correct table is being loaded. If it is, determine why the table is empty.

DTM7502I

*** ERROR *** JSS TABLE RECORD nn INVALID. [‘record’]


Explanation:
record: If present, this is the contents of the record in error.
The error is one of the following:

  • A syntax error on a RSS_PREFER or RSS_EXCLUDE identification statement.
  • A volume serial number pattern contains invalid characters.
  • A volume serial number pattern is longer than 6 characters.
  • The Job Analyzer found an invalid volume serial number pattern.

S ystem Action: The JSS table is not loaded.

Operator response: Notify personnel responsible for support.

Programmer Response: Correct the statement in error and re-load the table.

DTM7503I

*** ERROR *** MULTIPLE RSS_EXCLUDE IDENTIFICATION STATEMENTS FOUND IN JSS TABLE


Explanation: An attempt was made to load a JSS table containing more than one EXCLUDE identification statement.

System action: The JSS table is not loaded.

Operator response: Notify personnel responsible for support.

Programmer Response: Remove the extraneous EXCLUDE statements and re-load the table.

DTM7504I

*** ERROR *** RSS_EXCLUDE IDENTIFICATION STMT FOUND AFTER A RSS_PREFER IDENTIFICATION STMT


Explanation: An attempt was made to load a JSS table containing an RSS_EXCLUDE identification statement following a RSS_PREFER identification statement.

System action: The JSS table is not loaded.

Operator response: Notify personnel responsible for support.

Programmer Response: Rearrange the JSS table so that the RSS_EXCLUDE statement precedes the RSS_PREFER statement. Remove any extraneous RSS_EXCLUDE statements. Re-load the table.

DTM7506I

JSS TABLE DISPLAY:
JSS TABLE NOT LOADED DUE TO ERRORS
or
JSS TABLE NOT DEFINED
or
JSS TABLE DISPLAY:
DSN=dsname [MEMBER=member] [*DISABLED]
[RSS_EXCLUDE] [*EMPTY]
[RSS_PREFER preference] [*EMPTY]
...


Explanation:
preference: is the preference given to volumes listed in that portion of the table, and is one of:
• ACS(acs-id) indicating a particular StorageTek Automated Cartridge System unit.
• ATL(atl-id) indicating a particular Memorex Automated Tape Library unit.
• CAP(cap-id) indicating a specific Cartridge Access Port within a StorageTek Automated Cartridge System unit.
• LIBRARY(name) indicating a particular IBM Automated Tape Library Dataserver unit.

This message is issued in response to a TBL DISPLAY JSS command.

System action: Processing continues.

Operator response: None.

Programmer Response: None.

DTM7507I

JSS TABLE action


Explanation:

action: can be one of ENABLED, DISABLED, or NOT REFRESHED.

This message is issued in response to a TBL ENABLE JSS, a TBL DISABLE JSS, or a TBL REFRESH JSS command.

System action: Processing continues.

Operator response: None.

Programmer Response: None.

DTM7508I

JSS TABLE action FAILED. TABLE NOT FOUND


Explanation:
action: can be one of ENABLED or DISABLED.
A TBL ENABLE JSS or TBL DISABLE JSS command was entered, but the JSS table could not be found.

System action: The command is ignored.

Operator response: Notify personnel responsible for support.

Programmer Response: Determine why the JSS table was not loaded successfully.

DTM7509I

JSS TABLE NOT REFRESHED, DATASET NAME NOT SPECIFIED


Explanation: A TBL REFRESH JSS command was entered without a data set name for the table.

System action: The command is ignored.

Operator response: Re-enter the command with a data set name for the JSS table.

Programmer Response: None.

DTM7510I

JSS MODE IS mode


Explanation:
mode: can be either ATTENDED or UNATTENDED.
This message is issued in response to a JSS MODE DISPLAY command.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7511I

JSS MODE IS ALREADY mode


Explanation:
mode: can be either ATTENDED or UNATTENDED.
This message is issued in response to a JSS MODE ATTENDED or JSS MODE UNATTENDED command. It indicates that JSS is already operating in the requested mode.

System action: The command is ignored.

Operator response: Ensure that the correct mode was requested.

Programmer Response: None.

DTM7512I

JSS MODE HAS BEEN SWITCHED TO mode


Explanation:
mode: can be either ATTENDED or UNATTENDED.
This message is issued in response to a JSS MODE ATTENDED or JSS MODE UNATTENDED command. It indicates that JSS has been switched to the requested mode.

System action: Switches to the requested mode.

Operator response: None.

Programmer Response: None.

DTM7515I

RSS status, AUTOMATED LIBRARY SYSTEM NOT DEFINED


Explanation:
status: can be either DISABLED (during initialization) or NOT ENABLED (by TM OPT command).
Issued if RSS is installed but no automated library was defined by a TM ACS, TM ATL, or TM ATLDS initialization statement. This message appears during initialization and in response to an attempt to ENABLE or RECYCLE RSS.

System action: If issued in response to a command, the command is ignored.

Operator response: Notify personnel responsible for support.

Programmer Response: Add an appropriate initialization statement that defines your automated library.

DTM7517I

JOB jobnumber jobname JSS JOB RECONCILIATION ERROR


Explanation: During JSS Control File reconciliation, the specified job was recorded as held by JSS, but was not recorded as held by the Control File Manager on behalf of JSS.

System action: If the job is awaiting JES2 execution, it is held by JSS, otherwise JSS marks the job as not held. If the job has completed execution, JSS removes its record of the job from the Control File (the job is no longer managed by JSS).

Operator response: None.

Programmer Response: None.

DTM7518I

JOB jobnumber jobname CF JOB RECONCILIATION ERROR


Explanation: During JSS Control File reconciliation, the specified job was recorded as held by the Control File Manager on behalf of JSS, but was not recorded as held by JSS itself.

System action: JSS releases the Control File JSS hold. The job is abandoned by JSS (JSS has no information with which to manage the job).

Operator response: Notify support personnel.

Programmer Response: Collect all available information concerning this problem and contact BMC Support.

DTM7519I

VVS RECONCILATION COMPLETE


Explanation: This message is issued in response to the JSS RECONCILE VVS command and indicates when reconciliation is done.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7520I

JSS DISPLAY JOBS
or
JSS DISPLAY PARAMETERS
or
JSS DISPLAY STATISTICS


Explanation: These messages are the first lines (“control” lines) of the responses to the corresponding JSS DISPLAY commands. The lines following this message depend on the command entered.

Here is a typical response from a JSS DISPLAY JOBS command:

DTM7520I JSS JOBS
JOB NAME HOLDS CVL VOLS MIN MAX HSM
====== ======== ======== ===== ==== ======= ======= =======
J00100 JSSQA100 V O 1038 1 1/5 16/20
J00101 JSSQA101 V H 1 12/15
J00102 JSSQA102 2 0



    • In this response:
      • HOLDS are:
      —A for ALS hold (UNAVAILABLE robotics unit).
      —H for HSM hold.
      —R for RVL hold.
      —U for UNATTENDED hold.
      —V for VOLUME hold.
      • HT indicates the time that has elapsed since JSS held the job. If JSS is not holding the job, this column is blank.
      • VOLS is the count of mountable volumes required by the job.
      • PVR is the count of volumes required by the job that were listed on Volume Lists not created by the job. If the job is not eligible for PVR release, this column is blank. If all required volumes from other Volume Lists have been PULLED, or the job did not require volumes from other Volume Lists, this column contains zero.
      • MIN is the number of minutes left in a minimum VOLUME hold time that was specified in JAL, separated by a slash from the number of minutes originally specified.
      • MAX is the number of minutes left in a maximum VOLUME hold time that was specified in JAL, separated by a slash from the number of minutes originally specified.
      • HSM is the number of minutes left in an HSM hold time that was specified in JAL, separated by a slash from the number of minutes originally specified.

      Here is a sample response from a display for a specific job:

      DTM7520I  JSS JOB01686 TESTJOB ANALYZED 15:30:30 Mon May 15, 2005
      JOB OPTIONS MIN_HOLD(7),MAX_HOLD(10),HSM(5),PVR,LIST(NEW)
      PULL LIST JVL DEST(LIBRARY), WRITTEN
      QUALIFIERS MANUAL CONSTRAINT
      HELD AT 15:30:31 Mon May 15, 2005
      NOW HELD FOR UNAVAIL. ALS*, ROBOTICS, VOLUMES, HSM, UNATTENDED
      VOLUMES ENTER ENTERED EJECT EJECTED PULL DUPS PULLED
      ====== ====== ====== ====== ====== ====== ======|
      RV1002 RV2394* TC3101
      • ENTER lists volumes that are requested inside the automated library.
      • ENTERED lists volumes that were requested and have been entered into the automated library. The ‘*’ following the ENTERED volume serial number indicates that the volume is in an UNAVAILABLE robotics unit.
      • EJECT lists volumes that have been requested to be removed from the automated library.
      • EJECTED lists volumes that have been requested to be removed and have already been removed from the automated library.
      • PULL lists manual volumes that have been listed on a Volume List.
      • DUPS lists volumes that appear on another Volume List.
      • PULLED lists manual volumes that have been listed on a Volume List and have been indicated as PULLED.

      Here is a typical response from a JSS DISPLAY PARMS command:
      DTM7520I  JSS PARAMETERS JSS OPTIONS : CF, PVR
      VIF STATUS : ACTIVE
      VIF DATASET : THRUPUT.MANAGER.VIF
      VIF AUTO-FILE AFTER: 48 HRS
      SPOOL DATASET : NOT IN USE

      Here is a typical response from a JSS DISPLAY STATISTICS command:
      DTM7520I  JSS STATISTICS LAST JSS COLD START: Wed Aug 17, 2010
      LAST JSS START : Thu Aug 25, 2010 19:30:38
      THIS JES2 NODE : CENTRAL
      THIS JES2 SYSTEM : HQ1
      JOBS NOW COLD-START
      MANAGED 21 120246
      HELD 18 120229
      CONTROL FILE UTILIZATION 384 / 284820 (0.1 %)
      VOLUMES REQUIRED, NOT PULLED 10
      VOLUMES REQUIRED, PULLED 23
      FILEABLE VOLUMES 15
      OTHER VOLUMES 0
      VIF UTILIZATION 48 / 6000 (0.8 %)
      VOLUMES PULLED BY OPERATOR 0

System action: None.

Operator response: None.

Programmer Response: None.

DTM7521I

JOB MANAGED BY JSS, BUT NOT HELD BY JSS
or
NO MATCHING JOBS HELD BY JSS


Explanation: Issued in response to various job-related JSS commands. The message indicates that the specified job is not held by JSS; however, the specified job is being managed by JSS, otherwise the response would be message DTM7522I.

System action: The command is ignored.

Operator response: Make sure the job name or job number was entered correctly.

Programmer Response: None.

DTM7522I  

JOB NOT MANAGED BY JSS

or
NO MATCHING JOBS HELD BY JSS


Explanation: Issued in response to various job-related JSS commands. The message indicates that the specified job is not managed by JSS.

System action: The command is ignored.

Operator response: Make sure the job name or job number was entered correctly.

Programmer Response: None.

DTM7523I

NO JOBS MANAGED BY JSS
or
NO JOBS MANAGED BY JSS ON MATCHING NODES


Explanation: Issued in response to various job-related JSS commands. It is a stronger form of DTM7522I. Not only is the job not found, but there are no jobs to find anyway.
The three variations are provided to give richer feedback than a simple “not found”. They support the obvious inferences.

The second variation is used in the case that:
• The command did not specify a node, and therefore the scope defaulted to “this node” and
• There are no jobs managed by JSS on this node, and
• There are jobs managed by JSS on other nodes.

The third variation is used in the case that:
• The command specified a node name, and
• There are no jobs managed by JSS on nodes matching the specified node name, and
• There are jobs managed by JSS on other nodes.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7524I

NODE NOT KNOWN TO JSS
or
NO MATCHING NODES KNOWN TO JSS


Explanation: Issued in response to various job-related JSS commands, where NODE(nodename) is specified, but the node name is not recorded in the JSS Control File. That is, no node by that name has “joined” the Control File complex (since the last CFM cold start).

System action: None.

Operator response: You might have mistyped the node name. Try again.

Programmer Response: None.

DTM7525I

ROBOTIC RECONCILIATION IN PROGRESS


Explanation: This message is displayed at Thruput Manager initialization, and whenever a JSS RECONCILE ALL command is entered. Thruput Manager is querying the robotic library’s database to determine the status volumes in the VIF.

System action: The status of volumes in the VIF is synchronized with the status of the volumes in the robotics library database.

Operator response: None.

Programmer Response: None.

DTM7526I

ROBOTIC RECONCILIATION COMPLETE


Explanation: This message is issued when Thruput Manager completes synchronization of the VIF with the robotics library database.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7527I

CATALOG ERROR DURING JSS UNATTENDED PROCESSING.
RC IS rc, RS IS IGGOCLaa - rs, DSN=dsname


Explanation:aa: identifies the module in which the error occurred.

rs: is the associated reason code.

A catalog error occurred at job initiation while JSS was in UNATTENDED node.

System action: The affected job is placed in HOLD for UNATTENDED, and will be released when the system is returned to ATTENDED mode.

Operator response: None.

Programmer Response: See to message IDC3009I in the IBM Message Library: System Messages for further information explaining the error and reason codes.

DTM7528I

jobname QUEUED FOR RE-EXECUTION BY JSS UNATTENDED PROCESSING, reason


Explanation:
reason: is the reason why the job has been requeued, and can be one of:
• MANUAL CONSTRAINT(S)
• CATALOG ERROR(S)
• REQUIRES REEL TYPE TAPE(S)
• REQUIRES MANUAL CARTRIDGE(S)
• NOT ALL VOLUME(S) IN ROBOT
• ROBOT INTERFACE ERROR

This message is issued when it is determined that a job cannot run in UNATTENDED mode.

System action: The affected job is placed in HOLD for UNATTENDED, and will be released when the system is returned to ATTENDED mode.

Operator response: None.

Programmer Response: None.

DTM7529I

JSS UNATTENDED PROCESSING FOR JOB jobname BYPASSED DUE TO USE OF JOBCAT/STEPCAT


Explanation: At job initiation during UNATTENDED mode, Thruput Manager has detected a job using JOBCAT or STEPCAT.

System action: The job is allowed to proceed into execution.

Operator response: None.

Programmer Response: None.

DTM7530I

JOB jobnumber jobname HELD BY JSS


Explanation: The specified job has been held by the JSS application. The job was not previously in JSS hold. This message can be issued in response to an operator JSS HOLD command, or in response to an internally-generated hold for VOLUME or HSM, generated by the TMSS Job Analyzer.

System action: The job is unavailable for JES2 execution until the JSS hold is removed by operator command, or by JSS automatically as a result of time limit expiry (HSM or MAX_HOLD) or PVR.

Operator response: If you need to know the details of the job’s JSS status, for example hold categories, use the JSS DISPLAY command.

Programmer Response: None.

DTM7531I

nnn JOBS HELD BY JSS


Explanation: nnn jobs have been held by the JSS application. The jobs were not previously in JSS hold. This message can be issued in response to an operator JSS HOLD command, or in response to an internally-generated hold for VOLUME or HSM, generated by the TMSS Job Analyzer.

System action: The jobs are unavailable for JES2 execution until the JSS hold is removed by operator command, or by JSS automatically as a result of time limit expiry (HSM or MAX_HOLD) or PVR.

Operator response: If you need to know the details of a job’s JSS status, for example hold categories, use the JSS DISPLAY command.

Programmer Response: None.

DTM7536I

JSS INTERNAL ERROR error-id HOLDING JOB jobnumber jobname


Explanation: JSS was unable to successfully perform hold processing. There is a system problem, either with TMSS or JES2.

System action: The job is removed from the JSS control File, and is no longer under the management of JSS.

Operator response: Issue the TM JOB DISPLAY command to determine the job’s status within TMSS. Issue the JES2 $DJ command to determine the job’s status within JES2. Take whatever actions are appropriate to run the job. Notify Thruput Manager technical support of the problem.

Programmer Response: Determine whether the problem is caused by JES2 or TMSS. If TMSS is failing, report this problem to BMC Support.

DTM7537I

JOB jobname REQUIRES
VOLUME DSNAME
volume dsname


Explanation: This message is preceded by message DTM7528I, and lists the required volumes and their associated data set names.

System action: The affected job is placed in HOLD for UNATTENDED, and will be released when the system is returned to ATTENDED mode.

Operator response: None.

Programmer Response: None.

DTM7540I

JOBjobnumber jobname RELEASED BY JSS


Explanation: The specified job has been released by the JSS application. This message may be issued in response to an operator JSS RELEASE command, or in response to an internally-generated PVR release.

System action: If there are no other Control File application holds (e.g. JBS), and there is no JES2 operator hold ($HJ) outstanding, the job will be available for JES2 execution.

Operator response: None.

Programmer Response: None.

DTM7541I

nnn JOBS RELEASED BY JSS


Explanation: nnn jobs have been released by the JSS application. This message may be issued in response to an operator JSS RELEASE command, or in response to an internally-generated PVR release.

System action: If there are no other Control File application holds (e.g. JBS), and there is no JES2 operator hold ($HJ) outstanding, the jobs will be available for JES2 execution.

Operator response: None.

Programmer Response: None.

DTM7542I

category HOLD[S] REMOVED FROM JOBjobnumber jobname


Explanation:
category: is the JSS hold category, and can be one of:
• HSM, indicating the job was in hold awaiting completion of an HSM recall.
• VOLUME, indicating the job was awaiting volumes, or that MIN_HOLD has expired.
• OPERATOR, indicating the job was held by a JSS HOLD command.
This message can be issued in response to an operator JSS RELEASE command, or in response to an internally-generated PVR release. The message indicates that the job was in JSS hold for category and at least one other category.

System action: The job remains in JSS hold for one or more other categories. When the job is released for those categories, it will be JSS released.

Operator response: If you want this job to run, determine the other JSS categories for which it is held, using the JSS DISPLAY command, then JSS RELEASE the job for those categories. Alternatively, use the ALL operand of the JSS RELEASE command.

Programmer Response: None.

DTM7543I

category HOLD[S] REMOVED FROM nnn JOBS


Explanation:
category: is the JSS hold category, and can be one of:
• HSM, indicating the job was in hold awaiting completion of an HSM recall.
• VOLUME, indicating the job was awaiting volumes, or that MIN_HOLD has expired.
• OPERATOR, indicating the job was held by a JSS HOLD command.
This message can be issued in response to an operator JSS RELEASE command, or in response to an internally-generated PVR release. The message indicates that the jobs were in JSS hold for category and at least one other category.

System action: The jobs remain in JSS hold for one or more other categories. When the jobs are released for those categories, they will be JSS released.

Operator response: If you want a job to run, determine the other JSS categories for which it is held, using the JSS DISPLAY command, then JSS RELEASE the job for those categories. Alternatively, use the ALL operand of the JSS RELEASE command.

Programmer Response: None.

DTM7544I

JOBjobnumber jobname NOT HELD FOR SPECIFIED CATEGORIES


Explanation: This message is issued in response to a RELEASE command. The job was not held by JSS for the specified category or categories.

System action: None.

Operator response: Use JSS DISPLAY to determine which categories the job is being held for.

Programmer Response: None.

DTM7544I

nnn MATCHING JOBS NOT HELD FOR SPECIFIED CATEGORIES


Explanation: This message is issued in response to a RELEASE command. nnn jobs are not held by JSS for the specified category or categories.

System action: None.

Operator response: Use JSS DISPLAY to determine which categories the jobs are being held for.

Programmer Response: None.

DTM7546I

JSS INTERNAL ERROR error-id RELEASING JOB jobnumber jobname


Explanation: JSS was unable to successfully perform release processing. There is a system problem, either with TMSS or JES2.

System action: The job is removed from the JSS Control File, and is no longer under the management of JSS.

Operator response: Issue the Thruput Manager JOB DISPLAY command to determine the job’s status within TMSS. Issue the JES2 $DJ command to determine the job’s status within JES2. Take whatever actions are appropriate to run the job. Notify support personnel about the problem.

Programmer Response: Determine whether the problem is caused by JES2 or TMSS. If TMSS is failing, report this problem to BMC Support.

DTM7547I

volume-list-id DONE


Explanation: A CVL DONE, FVL DONE, or JVL DONE command was entered without an EXCLUDE list.

System action: All volumes on a CVL or JVL are indicated as PULLED or were already PULLED. All volumes on an FVL are indicated as FILED.

Operator response: None.

Programmer Response: None.

DTM7548I

volume-list-id NON-EXCLUDED VOLUMES DONE


Explanation: A CVL DONE, FVL DONE, or JVL DONE command was entered with an EXCLUDE list.

System action: For a CVL or JVL, the volumes not excluded are indicated as PULLED. For an FVL, the volumes not excluded are indicated as FILED.

Operator response: When the volumes in the EXCLUDE list are available, re-issue the DONE for this Volume List.

Programmer Response: None.

DTM7550I

volume-list-id NOT OUTSTANDING


Explanation: A CVL DONE or JVL DONE was issued for a Volume List that is not outstanding, or a CVL DONE is issued and the volumes on the CVL are already on a prior Volume List.

System action: The command is ignored.

Operator response: Make sure the Volume List has been produced and is serviced before re-issuing the DONE. Check any flagged volumes to determine whether they are outstanding on a previous JVL or CVL.

Programmer Response: None.

DTM7551I

volume-list-id NOT DONE, INVALID VOLUME EXCLUSION LIST


Explanation: The CVL DONE, FVL DONE, or JVL DONE command specified an EXCLUDE list that contained improper delimiters or improper list entries. Entries must be volume serial numbers or line entry numbers as they appeared on the Volume List.

System action: The command is ignored.

Operator response: Re-enter the list correctly.

Programmer Response: None.

DTM7552I

volume-list-id NOT DONE, TOO MANY VOLUMES IN VOLUME EXCLUSION LIST


Explanation: The CVL DONE, FVL DONE, or JVL DONE command specified an EXCLUDE list with more than 100 entries.

System action: The command is ignored.

Operator response: Reduce the size of the list.

Programmer Response: None.

DTM7553I

EXCLUSION LIST ENTRIES DO NOT MATCH volume-list-type


Explanation: The CVL DONE, FVL DONE, or JVL DONE command specified an EXCLUDE list with one or more entries which did not match any volume on the Volume List.

System action: The command is ignored.

Operator response: Re-enter the list correctly.

Programmer Response: None.

DTM7554I

volume-list-id NOT DONE
ALL VOLUMES WERE EXCLUDED


Explanation: A CVL DONE, FVL DONE, or JVL DONE command was entered with an EXCLUDE list, but all volumes on the Volume List were in the EXCLUDE list.

System action: The command is ignored.

Operator response: None.

Programmer Response: None.

DTM7555I

ADD FAILED, PGM=progname ALREADY SPECIFIED


Explanation: A JSS ADD command or the TMSS initialization statement JSS BYPASS has already specified this program name.

System action: The attempt to ADD the specified program is ignored.

Operator response: None.

Programmer Response: None.

DTM7556I

REMOVE FAILED, PGM=progname NOT FOUND


Explanation: A JSS REMOVE command was issued, but the specified program name was not found in the program list.

System action: The attempt to REMOVE the specified program is ignored.

Operator response: None.

Programmer Response: None.

DTM7557I

JSS ’function’ COMPLETE


Explanation:
function: is the type of JSS command issued, and is one of:
• ADD
• REMOVE
• SET

This is the response when the command was completed successfully.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7558I

NO JSS PROGRAM_NAMES FOUND


Explanation: A JSS DISPLAY PROGRAM_NAMES command was issued, but no program names have been added by JSS ADD or the TMSS initialization statement JSS BYPASS.

System action: The command is ignored.

Operator response: None.

Programmer Response: None.

DTM7559I

JSS PROGRAM_NAMES DISPLAY:
name1 name2 name3 name4 name5
nameN
DELETE_RECALLS(opt) TAPE_ALLOCATION(opt)


Explanation:
nameN: is a program name.
opt: indicates whether the option is active or not, and can be YES or number

This is the response to a JSS DISPLAY PROGRAM_NAMES command. Up to 5 names are displayed on a line.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7560I

FVL STATUS
VOLUMES NOT REQUIRED (FILEABLE) nn
VOLUMES REQUIRED AND PULLED (KEEP) nn
VOLUMES REQUIRED nn
VIF UTILIZATION nn.n %
DEFAULT FVL DESTINATION dest
DEFAULT FVL VOLUME LIST type


Explanation:
type: is the type of FVL being produced by default, and can be:
• FILEABLE, listing all fileable volumes.
• REQUIRED, listing all volumes required by jobs.
• ALL, listing all volumes.

This is the response to an FVL DISPLAY command.

System action: None.

O perator Response: None.

Programmer Response: None.

DTM7561I

FVL SETTINGS
DESTINATION fvl-destination
VOLUMES DISPLAYED fvl-type


Explanation:
fvl-type: is type of FVL that will be generated, and can be one of:
• FILEABLE, indicating that only FILEABLE volumes will be listed.
• REQUIRED, indicating that only REQUIRED volumes will be listed.
• ALL, indicating that all volumes will be listed.

Issued in response to an FVL DISPLAY or FVL SET command.

System action: If FVL SET was issued, the new FVL parameters are now in effect.

Operator response: None.

Programmer Response: None.

DTM7562I

FVL [RE]GENERATED AND SENT TO DESTINATION name


Explanation: Issued in response to an FVL GENERATE or FVL REGENERATE command.

System action: Queues an FVL to the named destination.

Operator response: Service the FVL once it has been printed.

Programmer Response: None.

DTM7563I

NO FILEABLE VOLUMES


Explanation: Issued in response to an FVL GENERATE command when the resulting list would be empty. For example, an FVL GENERATE FILEABLE command is issued when there are no fileable volumes.

System action: The request is ignored.

Operator response: None.

Programmer Response: None.

DTM7564I

COMMAND REJECTED.
SERVICE OUTSTANDING FVLS.


Explanation: Issued in response to an FVL GENERATE when there are already two outstanding FVLs. Only two FVLs can be active simultaneously.

System action: The command is ignored.

Operator response: You must service at least one of the outstanding FVLs and enter the appropriate FVL DONE command before you can generate another FVL.

Programmer Response: None.

DTM7565I

FVL nnn VOLUMES FILED


Explanation: Issued in response to an FVL DONE command.

System action: Indicates volumes as FILED, as listed on the FVL.

Operator response: None.

Programmer Response: None.

DTM7566I

FVL nnn CANCELLED


Explanation: Issued in response to an FVL CANCEL command.

System action: The outstanding FVL is cancelled, and any volumes listed on it that have not been DONE are made eligible for the next FVL.

Operator response: None.

Programmer Response: None.

DTM7567I

INVALID FVL NUMBER


Explanation: An FVL DONE was issued but the FVL number specified was not valid.

System action: The command is ignored.

Operator response: Re-enter using the correct number.

Programmer Response: None.

DTM7568I

FVL nnn NOT OUTSTANDING


Explanation: Issued in response to an FVL CANCEL, FVL DONE, or FVL REGENERATE command for an FVL number that is not active.

System action: The command is ignored.

Operator response: Check the FVL number.

Programmer Response: None.

DTM7590I

COMMAND REJECTED, reason


Explanation:
reason: is a self-explanatory reason why the command was rejected:
• JSS NOT RESPONDING
• JSS OPERATING IN NOPVR MODE
• TM OPERATING IN V3 COMPATIBILITY MODE
• JSS TM OPTION NOT ACTIVE
• REQUIRES JSS CF OPTION
• ONLY SUPPORTED IN V3 COMPATIBILITY MODE
• OBSOLETE FORM – USE ‘JSS’ INSTEAD OF ‘PVF’
• OBSOLETE FORM – USE ‘CVL DONE’
• SYSOUT KEYWORD NOT SUPPORTED IN V3 MODE
• RSS TM OPTION NOT INSTALLED
• RSS TM OPTION NOT ACTIVE

A command was entered but is not supported in the current JSS operating mode, or when JSS is not active.

System action: The command is ignored.

Operator response: Make sure JSS was started and is in the correct mode. If JSS or RSS has been disabled by a TM OPT DISABLE command, restart it with the TM OPT ENABLE command.

Programmer Response: None.

DTM7570I

robot-id [AVAILABLE | UNAVAILABLE]


Explanation: Issued in response to the JSS ALS_STATUS command, indicating the command was successful.

System action: Jobs with automated volumes inside the robot are held when the robot is indicated as UNAVAILABLE, and released when it is specified as AVAILABLE.

Operator response: None.

Programmer Response: None.

DTM7571I

robot-id ALREADY [AVAILABLE | UNAVAILABLE]


Explanation: Issued in response to the JSS ALS_STATUS command, indicating that the requested action has already been performed.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7572I

NO UNAVAILABLE ALS ROBOTS DEFINED


Explanation: Issued in response to a JSS ALS_STATUS command, indicating that there are no UNAVAILABLE robots.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7573I

MAXIMUM NUMBER OF UNAVAILABLE ALS ROBOTS DEFINED


Explanation: Issued in response to a JSS ALS_STATUS command, indicating that the maximum number (62) of UNAVAILABLE robots has already been defined.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7574I

UNAVAILABLE ALS ROBOTS:
robot-id-list


Explanation: Issued in response to a JSS ALS_STATUS DISPLAY command, listing the robots that are currently defined as UNAVAILABLE.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7592I

Required ‘FILE VIF’ Statement missing


Explanation: The Volume Information File is mandatory, but the FILE VIF initialization statement was not found.

System action: TMSS terminates with a condition code of 24 once all initialization statements have been processed.

Operator response: Notify personnel responsible for support.

Programmer Response: Allocate a Volume Information File and include a FILE VIF initialization statement.

DTM7593I

JSS INTERFACE ERROR error-id


Explanation: A system component attempted to communicate with JSS, and the communication failed.

System action: JSS did not perform the requested service.

Operator response: Notify support personnel.

Programmer Response: Determine why the Thruput Manager component is not responding. If necessary, report this problem to BMC Support.

DTM7594I

JSS SERVICE ABENDED


Explanation: JSS abended while servicing a request from another Thruput Manager component.

System action: JSS does not complete the requested service. JSS attempts to restart, but if more than three failures are detected, JSS is disabled.

Operator response: Notify support personnel.

Programmer Response: Collect all available information concerning this problem and contact BMC Support.

DTM7595I

COMMAND REJECTED, reason

Explanation:
reason: is the reason the command is rejected, and is one of:
• VIF NOT ACTIVE, indicating that the TMSS initialization parameters did not include a FILE VIF statement.
• VIF NOT RESPONDING, indicating that the VIF service did not respond.
• REQUIRES A VIF FORMATTED UNDER V4, indicating that an FVL command was issued, but the VIF in use is in Version 3 format.

A command that requires information from the VIF was entered, but was rejected for the stated reason.

System action: The command is ignored.

Operator response: If the VIF should be active but is not, notify support personnel.

Programmer Response: If the VIF is not active, check the TMSS initialization statements for a missing or incorrect FILE VIF statement.
If the VIF is not responding, check for a possible DASD lockout on the VIF, or for a VIF processor abend or loop.
If FVL support is desired, arrange to cold-start the VIF while running in Version 4 mode.

DTM7596I

VIF INTERFACE ERROR error-id

Explanation: A system component attempted to communicate with the VIF processor, and the communication failed.

System action: The VIF processor did not perform the requested service.

Operator response: Notify support personnel.

Programmer Response: Determine why the VIF processor is not responding. If necessary, report this problem to BMC Support.

DTM7597I

VIF SERVICE ABENDED


Explanation: The VIF processor abended while performing a service request from another Thruput Manager component.

System action: The requested service was not performed. JSS attempts to restart the VIF processor, but if more than three failures are detected, the VIF processor is disabled.

Operator response: Notify support personnel.

Programmer Response: Collect all available information concerning this problem and contact BMC Support.

DTM7598I

WRITER INTERFACE ERROR error-id


Explanation: A system error was returned by a CPS Writer using Spooling services.

System action: The requested service was not performed.

Operator response: Notify support personnel.

Programmer Response: Collect all available information concerning this problem and contact BMC Support.

DTM7599I

WRITER SERVICE ABENDED


Explanation: A CPS Writer abended while attempting to service a request from another Thruput Manager component.

System action: The requested service was not performed. JSS attempts to restart the Writer, but if more than three failures are detected, the Writer is disabled.

Operator response: Notify support personnel.

Programmer Response: Collect all available information concerning this problem and contact BMC Support.

DTM7600I

SPS SYSOUT DEFINITIONS
NAME M CL H FORM DEST
name m cl h forms destination


Explanation:
name: The name for this definition of SPS characteristics.
m: is either blank or an asterisk (*), used to indicate that this definition has more parameters that can be displayed with a specific SPS DISPLAY command for this name.
cl: is the SYSOUT class.
forms: is the name of special forms, if any.
destination: is the JES2 destination.

This is the response to a non-specific SPS DISPLAY command.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7601I

DEFINITION FOR SYSOUT name
CLASS : sysout-class
FORM : forms
BOTTOMMARGIN : nnn
LEFTMARGIN : nnn
PAGELENGTH : nnn
TOPMARGIN : nnn


Explanation: This is the response to an SPS DISPLAY command that specifies a specific name.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7611I

SYSOUT name DEFINED


Explanation:
name: is the 1-8 character name assigned to a SYSOUT destination.
Response to an SPS DEFINE name.

System action: The SPS SYSOUT destination is assigned the new characteristics.

Operator response: None

.Programmer Response: None.

DTM7612I

SYSOUT name NOT FOUND


Explanation:
name: is the 1-8 character name assigned to a SYSOUT destination.
An SPS DISPLAY name or SPS REMOVE name command was entered, but name is not a defined SYSOUT destination.

System action: The command is ignored.

Operator response: Use SPS DISPLAY to see the currently defined names.

Programmer Response: None.

DTM7614I

SYSOUT name ALREADY DEFINED


Explanation:
name: is the 1-8 character name assigned to a SYSOUT destination.
An SPS DEFINE name was entered, but a SYSOUT destination with that name has already been defined.

System action: The command is ignored.

Operator response: To change a SYSOUT destination that is already defined, use SPS REMOVE followed by SPS DEFINE.

Programmer Response: None.

DTM7615I

SYSOUT name CANNOT BE ALLOCATED


Explanation:
name: is the 1-8 character name assigned to a SYSOUT destination.
A TMSS SPS DEFINE initialization statement or the command SPS DEFINE has attempted to create an invalid SYSOUT definition.

System action: The specified set of characteristics is not allocated. Message DTM7620I or DTM0190I follows, providing more detail on the problem.

Operator response: If the problem is occurring during initialization, notify support personnel. If the problem is occurring during command processing, re-issue the command with correct parameters.

Programmer Response: Correct the SPS DEFINE initialization statement.

DTM7616I

SYSOUT name REMOVED


Explanation:
name: is the 1-8 character name assigned to a SYSOUT destination.
Response to an SPS REMOVE name command.

System action: The SYSOUT destination is removed from the system.

Operator response: None.

Programmer Response: None.

DTM7617I

SYSOUT $DEFAULT CANNOT BE REMOVED


Explanation: Response to an attempt to remove the $DEFAULT definition which is not permitted.

System action: The command is ignored.

Operator response: None.

Programmer Response: None.

DTM7618I

NO SYSOUT NAME SPECIFIED


Explanation: SPS DEFINE and SPS REMOVE require that a positional parameter name follow the command verb. No such name was found.

System action: The command is ignored.

Operator response: Specify a valid name in the command. Names can be 1-8 alphabetic, numeric, or national characters.

Programmer Response: None.

DTM7619I

SYSOUT CLASS MUST BE SPECIFIED


Explanation: SPS DEFINE requires that a SYSOUT class be specified.

System action: The command is ignored.

Operator response: Specify a valid SYSOUT class.

Programmer Response: None.

DTM7620I

VALUE SPECIFIED FOR ‘keyword’ PARAMETER IS INVALID

E xplanation: An SPS DEFINE specified a keyword with an invalid value.

System action: The command is ignored.

Operator response: Re-enter the command with correct parameters.

Programmer Response: None.

DTM7621I

SYSOUT NAME IS INVALID


Explanation: An SPS DEFINE command was issued using an invalid SYSOUT name.

System action: The command is ignored.

Operator response: Re-enter with a valid SYSOUT name.

Programmer Response: None.

DTM7721I

RVL STATISTICS
ROBOT VOLUMES
===== =======
ENTER address volumes
EJECT address volumes


Explanation:
address: can be an ACS/CAP address, an ATL unit address or name, an ATLDS library name, ANY_ROBOT (meaning any robotics unit), or ALL_VOLUMES (meaning all volumes required in robotics units, regardless of preference).
volumes: is the number of volumes awaiting action.
This message is issued in response to an RVL DISPLAY STATISTICS command.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7722I

RVL SETTINGS
DESTINATION NODE
=========== ====
ENTER destination node
EJECT destination node


Explanation: This message is issued in response to an RVL SET or RVL DISPLAY SETTINGS command.

System action: If the RVL SET command was entered, the new RVL settings become effective.

Operator response: None.

Programmer Response: None.

DTM7730I

type RVL IS EMPTY, NO VOLUMES TO action


Explanation:
type: is the type of preferencing for the RVL that was requested, and can be one of:
• ACS(acs-id)
• ALL_VOLUMES
• ANY_ROBOT
• ATL(atl-id)
• CAP(cap-id)
• LIBRARY(atlds-id)
action: can be either ENTER or EJECT.
This message is issued in response to an RVL GENERATE command when there are no volumes of the type requested.

System action: Processing continues.

Operator response: None.

Programmer Response: None.

DTM7731I

ROBOTICS UNIT NOT DETECTED ON THIS SYSTEM


Explanation: An RVL SET or RVL DISPLAY SETTINGS command was entered, but the type of unit specified in the command cannot be found on the system where the command was entered.

System action: The command is ignored.

Operator response: Re-enter the command specifying the correct unit type, or re-enter on the correct system.

Programmer Response: None.

DTM7732I

NO ROBOTICS UNIT DETECTED ON THIS SYSTEM


Explanation: An RVL SET or RVL DISPLAY SETTINGS command was entered, but the no robotics unit can be found on the system where the command was entered.

System action: The command is ignored.

Operator response: Re-enter the command on the correct system.

Programmer Response: None.

DTM7735I

RVL nnn GENERATED AND SENT TO DESTINATION destination


Explanation: This message is issued in response to an RVL GENERATE command.

System action: The RVL numbered nnn is queued for the indicated destination.

Operator response: Service the RVL when it has been printed.

Programmer Response: None.

DTM7806I

DATA SET RESERVATION UNSUCCESSFUL FOR dsname
or
DATA SET RESERVATION REQUEST CANCELLED FOR dsname


Explanation: The Thruput Manager subsystem allocation exit was unable to obtain the appropriate data set ENQ, or the operator replied NO to the message DTM7808A.

System action: The job is failed with a JCL error.

Operator response: None.

Programmer Response: To allow jobs to wait for the requested resource, specify SDSN_WAIT WAIT_ALLOC(YES) in the ALLOCxx member of SYS1.PARMLIB.

DTM7807I

DATA SET dsname UNAVAILABLE TO jobname


Explanation: The Thruput Manager subsystem allocation exit was unable to obtain the appropriate data set ENQ. This message is followed by DTM7808A.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7808A

jobname stepname WAITING FOR DATA SET. TO CANCEL WAIT REPLY “NO”


Explanation: The Thruput Manager subsystem allocation exit was unable to obtain the appropriate data set ENQ. This message is preceded by DTM7807I.

System action: Waits for the data set to become available or until the operator replies number

Operator response: Reply NO to prevent the job from waiting.

Programmer Response: None.

DTM7809I

dsname disp, DDNAME=ddname(+nnn)


Explanation:
dsname: Is the name of the data set.
disp: Is the disposition of the data set.
ddname(+nnn): Is the DD name. If the data set was part of a concatenation, +nnn is the number of the DD statement relative to the start of the concatenation.

The Thruput Manager subsystem unallocation exit generates this message during disposition of a DFSMS-managed data set or a DFSMSHSM migrated data set.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7810I

dsname, service ERROR, errdesc


Explanation:
dsname: Is the name of the data set.
service: Is the service being performed (e.g. ARCHDEL for a DFSMSHSM migrated data set).
errdesc: Is a description of the error. If the error is unknown, the description provides the contents of general registers 15 and 0 on return from the named service.


Explanation: The Thruput Manager subsystem unallocation exit has encountered an error during the disposition processing of the named data set.

System action: No further disposition processing is performed for this data set.

Operator response: None.

Programmer Response: Use the related messages in the job’s SYSMSGS data set to diagnose the error. Determine whether the job should be resubmitted.

DTM7811I

dsname disp
VOL SER NOS= volser1,volser2,...volserN


Explanation: The Thruput Manager subsystem unallocation exit has performed disposition processing for the named data set.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7812I

GDG ROLL IN ERROR - RETURN CODE rc REASON CODE rs MODULE modname


Explanation: The Thruput Manager subsystem unallocation exit has encountered a catalog error while attempting to roll a generation data set (GDS) into a generation data group (GDG).

System action: The roll fails. The GDS is retained but remains in a deferred roll-in state. It can be referred to by its absolute generation name, contained in DTM7809I, which follows this message.

Operator response: None.

Programmer Response: See to IBM message IDC3009I for an explanation of the return code and reason code. See the IBM space DFSMS/MVS Managing Catalogs for information on how to roll in a GDS which is in deferred roll-in state.

DTM7813I

jobname (procstep) stepname
dsname NOT disp


Explanation:
jobname: Is the name of the job.
procstep: Is the name of the step in the procedure.
stepname: Is the name of the job step.
dsname: Is the name of the data set that could not be (re)cataloged.
disp: Is the data set’s disposition, and can be one of:
• CATLGD if an attempt was made to catalog an uncataloged data set.
• RECATLGD if an attempt was made to recatalog a cataloged data set.
The ThruPut Manager  subsystem unallocation exit encountered a catalog error during data set disposition processing as a result of:
• Inability to catalog an old uncataloged data set for which a disposition of catalog was specified.
• Inability to recatalog an old cataloged data set for which the volume list was extended and a disposition of catalog was specified.
• Inability to roll a SMS-managed generation data set (GDS) into a generation data group (GDG) base.

System action: Depends on installation options. The job fails at end of step if CATLG_ERR FAILJOB(YES) is specified in ALLOCxx in SYS1.PARMLIB.

Operator response: Notify your systems programmer.

Programmer Response: Use the related messages in the job’s SYSMSGS data set to diagnose the error. Determine whether the job should be resubmitted.

DTM7814I

jobname (procstep) stepname - JOB FAILED - TIME=hh.mm.ss
CATALOG DISPOSITION ERROR


Explanation: The system installation default specifies CATLG_ERR FAILJOB(YES) in ALLOCxx in SYS1.PARMLIB, and one of the following errors occurred during data set disposition processing at step termination:
• Inability to catalog an old uncataloged data set for which a disposition of catalog was specified.
• Inability to recatalog an old cataloged data set for which the volume list was extended and a disposition of catalog was specified.
• Inability to roll a SMS-managed generation data set (GDS) into a generation data group (GDG) base.

System action: The job is terminated at the end of the step that encountered the error.

Operator response: Notify your systems programmer.

Programmer Response: Use the related messages in the job’s SYSMSGS data set to diagnose the error. Determine whether the job should be resubmitted.

DTM7815I

jobname (procstep) stepname - JOB ENDED BECAUSE OF CATALOG ERROR


Explanation: The system installation default specifies CATLG_ERR FAILJOB(YES) in ALLOCxx in SYS1.PARMLIB, and one of the following errors occurred during data set disposition processing at step termination:
• Inability to catalog an old uncataloged data set for which a disposition of catalog was specified.
• Inability to recatalog an old cataloged data set for which the volume list was extended and a disposition of catalog was specified.
• Inability to roll a SMS-managed generation data set (GDS) into a generation data group (GDG) base.

System action: The job is terminated at the end of the step that encountered the error.

Operator response: Notify your systems programer.

Programmer Response: Use the related messages in the job’s SYSMSGS data set to diagnose the error. Determine whether the job should be resubmitted.

DTM7816I

STAGING FAILED FOR VOL=volser UNIT=unitname, NO DEVICE AVAILABLE.


Explanation: This message is issued when the staging process for a virtual volume fails.

reason: An attempt to mount the volser on a unit of the specified device type failed.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7817I

DTMVVSS6 MUST BE APF AUTHORIZED


Explanation: The LOAD module DTMVVSS6 must be linked authorized and reside in an APF authorized library (preferably linklist). If Thruput Manager is installed correctly this should not occur.

System action: None.

Operator response: None.

Programmer Response: Check that DTMVVSS6 resides in an APF authorized library.

DTM7818I

NO JOBS AWAITING VIRTUAL VOLUMES STAGING


Explanation: This message is issued in response to the JSS D VVSQ command. It indicates that no volumes await staging or the specified jobname/volser does not match anything on the request queue on the system on which the command was entered.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7819I

JSS DISPLAY VVSQ
JOBID JOBNAME VOLUME UNIT LIBRARY STATUS
jobno jobname volume unit library status
...
or
JSS DISPLAY VVSQ
VOLUME UNIT LIBRARY JOBID JOBNAME STATUS
volume unit library jobno jobname status
...


Explanation:
status: is either QUEUED AT followed by the time that VVS received the request for volume staging
or
INITIATED AT followed by the time that the stage request began.
This message is issued in response to a JSS DISPLAY VVSQ command. If the JOBS keyword was specified, or if there was no keyword, the display is ordered by job number. If the VOLUME keyword was specified, the display is ordered by volume.

System action: None.

Operator response: None.

Programmer Response: None.

DTM7822I

START FAILED FOR VVS PROCEDURE ‘TMVVS’ - PAUSING STAGE PROCESSING


Explanation: This message indicates that the staging address space failed to start within a reasonable amount of time. Possibly a JCL-ERROR occurred (procedure not found) or the TMVVS address space failed to signal that it is initialized within 1 minute.

The START is attempted 3 times before the above error message is issued.

System action: JSS Staging is held until a “JSS RESUME VVS” is issued.

Operator response: Notify System Programmer.

Programmer Response: Examine system to see if it is overloaded or any other reason that the TMVVS would fail to start.

DTM7823I

jobname (procstep) stepname ddname(+nnn) - WARNING: VOLUME NOT RETRIEVED FROM CATALOG


Explanation: In the message text:
jobname: the name of the job
procstep: the name of the step in the procedure
stepname: is the name of the job step
ddname: the DD name. If the DD was part of a concatenation,
+nnn: is the number of the DD relative to the start of the concatenation.
This indicates that data set disposition specified “DISP=(x,UNCATLG)” where unit and volume serial(s) were specified on the corresponding DD statement. As a result, this message is issued when MVS parmlib member ALLOCxx specifies “SYSTEM VERIFY_UNCAT(MSGTRACK)”. This identifies a potential error, because it is possible that the data set in the catalog was not the same data set that was actually allocated by the job.

System action: The data set is uncatalogued.

Operator response: None.

Programmer Response: Correct JCL.

DTM8000I

DATA SPACE SERVICES TASK INITIALIZED


Explanation: The Thruput Manager Data Space Services task has successfully initialized and will now accept requests to create or delete data spaces.

System action: The Data Space Services task now waits for requests to create or delete data spaces from other Thruput Manager modules.

Operator response: None.

Programmer Response: None.

DTM8001I

DATA SPACE SERVICES SHUTDOWN COMPLETE


Explanation: The Thruput Manager Data Space Services task has terminated as a result of a shutdown request.

System action: Thruput Manager shutdown continues.

Operator response: None.

Programmer Response: None.

DTM8010I

TRACE SPUN TO DESTINATION destination


Explanation: A formatted trace listing has been spun to the indicated destination by Thruput Manager Data Space Services. This is issued in response to the Thruput Manager Operator command XMD SPIN destination.

System action: None.

Operator response: None.

Programmer Response: Forward the trace listing to BMC Support.

DTM8011I

TRACE NOT SPUN. RC=code


Explanation: An XMD SPIN operator command was issued, but an error occurred while attempting to spin a formatted trace listing from Thruput Manager Data Space Services. The Thruput Manager return code is supplied.

System action: The XMD command terminates.

Operator response: Inform personnel responsible for support.

Programmer Response: Contact BMC Support.

DTM8012I

XDC ESTAE ACTIVATED


Explanation: This is an internal diagnostic message.

DTM8013I

XDC NOT ACTIVATED. SYSTEM CODE=system code


Explanation: This is an internal diagnostic message.

DTM8014I

INVALID OR INACTIVE DATA SPACE NAME


Explanation: This is an internal diagnostic message.

DTM8015W

EXTENDED TRACE DATASPACE COULD NOT BE OBTAINED BY JES


Explanation: The data space name supplied has either not been created since the last system IPL or the data space does not currently exist.

System action: The trace will fall back to use above the line storage rather than a dataspace.

Operator response: None

Programmer Response: None.

DTM8100I

SLM TASK INITIALIZED


Explanation: The Thruput Manager Service Level Manager task has completed initialization. The SLM task will now accept requests, and will attempt to read the current active SLM policy. The SLM task will attempt to become the SLM Server once TM has completely initialized if there is no SLM Server active in the JESPLEX.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8101I

SLM TASK SHUTDOWN COMPLETE


Explanation: Thruput Manager Service Level Manager task has terminated as a result of an operator shutdown request for the Service Level Manager task or all of Thruput Manager.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8102I

SLM SERVER FUNCTION ACTIVE ON member


Explanation: The Service Level Manager task on the indicated member of the JESPLEX has assumed the role of SLM Server. No SLM Server currently existed in the JESPLEX either because this is the only active instance of SLM in the JESPLEX or the instance of SLM that was the SLM Server has terminated.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8103I

SLM SERVICE MODE IS service-mode


Explanation: This message is issued in the response to the SLM ACTIVATE MODE or SLM DEACTIVATE MODE command.

System action: Processes jobs using the displayed Service Mode.

Operator response: None.

Programmer Response: None.

DTM8105I

SLM QUIESCED - WLM NOT IN GOAL MODE


Explanation: The Service Level Manager task on the member of the JESPLEX where the message was issued has determined that WLM is not operating in goal mode.

System action: Quiesces processing on the JESPLEX member where the message is issued.

Operator response: None.

Programmer Response: None.

DTM8107I

SLM policy policy-name activated on member


Explanation: A new Service Level Manager policy has been activated successfully by the SLM Server for the JESPLEX. SLM is responding to a Policy activation request from either the SLM ACTIVATE operator command or from the SLM Definition Services dialog.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8108I

SLM policy policy-name activated on  member with warnings


Explanation: A new Service Level Manager policy has been activated successfully by the SLM Server for the JESPLEX. There were warning messages but activation did occur. SLM is responding to a Policy activation request from either the SLM ACTIVATE operator command or from the SLM Definition Services dialog.

System action: None.

Operator response: Notify personnel responsible for support.

Programmer Response: Review warning messages for any necessary action.

DTM8109I

SLM UNABLE TO OBTAIN DATA SPACE LOCK


Explanation: Service Level Manager was unable to obtain a lock on an SLM data space used to track address space usage in order to initialize the internal data structures.

System action: SLM will automatically retry the lock attempt every 30 seconds.

Operator response: Notify personnel responsible for support.

Programmer Response: Check whether another address space which has failed to relinquish the lock. The MVS command ‘D GRS’ can be used to identify the source of the lock contention. The lock is implemented using ENQ with a qname of DTMjjjj where ‘jjjj’ is the JES2 subsystem name, typically ‘JES2’, and the rname is SMIQCPU.

DTM8110I

SLM QUIESCED - NO VALID SLM POLICY


Explanation: There is no valid SLM Policy in the TM Control File. Service Level Manager is unable to function fully. Either this is a new installation of SLM, or there has been a cold start of the TM Control File, or there are validation errors in the current SLM Policy caused by significant changes to the current WLM Policy.

System action: SLM does not allow selection of SLM-managed jobs.

Operator response: Notify personnel responsible for support.

Programmer Response: Check for any validation errors and correct any problems; otherwise create and activate a valid SLM policy using the SLM Definition Services dialog.

DTM8111I

SERVICE CLASS service-class NOT IN ACTIVE WLM POLICY


Explanation: The indicated Service Class is specified in the SLM Policy being validated but is not defined in the active WLM Policy.
This condition is determined during SLM Policy validation when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: None.

Operator response: Notify personnel responsible for support.

Programmer Response: Activate a valid SLM Policy that does not specify the indicated Service Class name, or implement a WLM Policy that contains a definition for the indicated Service Class.

DTM8112I

SERVICE CLASS NOT SPECIFIED FOR BATCH IMPORTANCE n


Explanation:
n: Is the Batch Importance level (1-5).
The SLM Policy must specify a WLM Service Class for every General Services Batch Importance level.
This condition is determined during SLM policy validation.
SLM Policy validation occurs when loading a policy at SLM initialization, activation of a new WLM policy, or as a result of either a validation or activation request from the TM ‘SLM’ command or the SLM Definition Services dialog.

System action: This error message will be issued on the console or by the SLM Definition Services dialog. The current action (validation, activation or policy load at initialization) will fail with an error.

Operator response: Notify personnel responsible for support.

Programmer Response: Activate a valid SLM policy that does specify a Service Class for the indicated Batch Importance level.

DTM8113I

SERVICE CLASS service-class GOAL TYPE IS NOT VELOCITY OR DISCRETIONARY


Explanation: The indicated WLM Service Class is defined in the active WLM policy as having a goal type other than velocity or discretionary.
This condition is determined during SLM Policy validation when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: The warning message will be issued on the console or by the SLM Definition Services dialog. If the current action is validation or activation, the action fails with an error. If the current action is a Policy load at initialization or after the activation of a WLM Policy, the load continues with a warning.

Operator response: Notify personnel responsible for support.

Programmer Response: Activate a valid SLM Policy that does not specify the indicated Service Class name, or implement a WLM Policy that contains a definition for the indicated Service Class that has an execution velocity goal or specifies discretionary.

DTM8114I

SERVICE CLASS service-class GOAL TYPE IS NOT DISCRETIONARY


Explanation: The indicated WLM Service Class is defined in the active WLM Policy as having a goal type other than discretionary. WLM Service Classes for use by SLM discretionary batch jobs should have a goal type of discretionary.
This condition is determined during SLM Policy validation when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: The validation or activation continues with a warning.

Operator response: Notify personnel responsible for support.

Programmer Response: Activate a valid SLM Policy that does not specify the indicated Service Class name, or implement a WLM Policy that contains a definition for the indicated Service Class that has a discretionary goal.

DTM8115I

NO SERVICE CLASSES SPECIFIED FOR PCS - USING SERVICE CLASSES FOR GENERAL
SERVICES


Explanation: The SLM Policy does not have a WLM Service Class defined for any PCS Production Importance Level. SLM will use the WLM Service Classes specified for General Services Batch Importance 1-5 for PCS and substitute if necessary for PCS “PREMIUM”.
This condition is determined during SLM policy validation.
SLM Policy validation occurs when loading a policy at SLM initialization, activation of a new WLM policy, or as a result of either a validation or activation request from the TM ‘SLM’ command or the SLM Definition Services dialog.

System action: The warning message will be issued on the console or by the SLM Definition Services dialog.

Operator response: Notify personnel responsible for support.

Programmer Response: Activate a valid SLM policy that specifies the Service Classes for use by PCS.

DTM8116I

SERVICE CLASS NOT SPECIFIED FOR PRODUCTION IMPORTANCE n


Explanation:
n: Is the PCS Production Importance level (1-5).
The SLM Policy does not have a WLM Service Class specified for the indicated PCS Production Importance level.
If PCS is installed, the SLM Policy must specify a WLM Service Class for every PCS Production Importance level. This condition is determined during SLM policy validation.
SLM Policy validation occurs when loading a policy at SLM initialization, activation of a new WLM policy, or as a result of either a validation or activation request from the TM ‘SLM’ command or the SLM Definition Services dialog.

System action: The warning message will be issued on the console or by the SLM Definition Services dialog. The current action (validation, activation or policy load at initiatlization) will fail with an error.

Operator response: Notify personnel responsible for support.

Programmer Response: Activate a valid SLM policy that does specify a ServiceClass for the indicated Production Importance level.

DTM8117I

SERVICE CLASS NOT SPECIFIED FOR PCS PREMIUM


Explanation: If PCS is installed, the SLM Policy must specify a WLM Service Class for PCS BEST.
This condition is determined during SLM policy validation.
SLM Policy validation occurs when loading a policy at SLM initialization, activation of a new WLM policy, or as a result of either a validation or activation request from the TM ‘SLM’ command or the SLM Definition Services dialog.

System action: The warning message will be issued on the console or by the SLM Definition Services dialog. The current action (validation, activation or policy load at initialization) will fail with an error.

Operator response: Notify personnel responsible for support.

Programmer Response: Activate a valid SLM policy that does specify a Service Class for the indicated PCS Service Class.

DTM8118I

ACTIVE SERVICE GROUP MISSING. CONTROL CENTER=center WORK TYPE=type


Explanation: While processing a validation or activation request for an SLM Policy, SLM determined that the indicated Service Group was not defined in the Policy. At least one job in the SLM execution queue is currently assigned to that Service Group.
This condition is determined during SLM Policy validation whe activatning a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog

System action: The validation or activation continues with a warning.

Operator response: Notify personnel responsible for support.

Programmer Response: Define the indicated Control Center and Work Type in the proposed SLM Policy, or cancel the jobs assigned to the Service Group or wait for the jobs to complete execution.

DTM8119I

SERVICE CLASSES service-class1/service-class2 RELATIVE VELOCITIES INCORRECT


Explanation: The indicated WLM Service Classes as defined in the active WLM Policy do not have the relationship between their velocity goals expected by SLM. These relationships are based on the assignment of WLM Service Classes to SLM Service Classes in the active SLM Policy. SLM expects that the velocity goals have a relationship that reflects their relative importance as defined to SLM. The service class with the greater importance is expected to have a higher velocity goal.
This condition is determined during SLM Policy validation when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.
This is only a warning message that may indicate an unintended error in defining either the SLM Policy or the WLM Policy.


Explanation:

System action: The validation or activation continues with a warning.

Operator response: Notify personnel responsible for support.

Programmer Response: Review the WLM Policy and the Service Class assignments defined in the SLM Policy and correct any unintended errors. Since this is only a warning, if there are no errors, no further action is required.

DTM8120I

SERVICE CLASSES service-class1/service-class2 RELATIVE IMPORTANCE LEVELS
INCORRECT


Explanation: The indicated WLM Service Classes as defined in the active WLM Policy do not have the relationship between their WLM Importance levels expected by SLM. These relationships are based on the assignment of WLM Service Classes to SLM service classes in the SLM Policy. SLM expects that the Importance levels have a relationship that reflects their relative importance as defined to SLM.
This condition is determined during SLM Policy validation when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.
This is only a warning message that may indicate an unintended error in defining either the SLM Policy or the WLM Policy.

System action: The validation or activation continues with a warning.

Operator response: Notify personnel responsible for support.

Programmer Response: Review the WLM Policy and the Service Class assignments defined in the SLM Policy and correct any unintended errors. Since this is only a warning, if there are no errors, no further action is required.

DTM8121I

SERVICE CLASS service-class NOT ASSIGNED TO RESOURCE GROUP


Explanation: The indicated WLM Service Class is defined in the SLM Policy as being for discretionary workload but is not assigned to a resource group as required by SLM.
This condition is determined during SLM Policy validation when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: The validation or activation continues with a warning.

Operator response: Notify personnel responsible for support.

Programmer Response: Activate a valid WLM policy that has assigns the Service Class to a Resource Group with the attributes required by SLM.

DTM8122I

SERVICE CLASS service-class RESOURCE GROUP resource-group HAS NO MAXIMUM


Explanation: The indicated WLM Service Class is defined in the SLM Policy as being for discretionary workload but is assigned to a Resource Group that does not have a maximum. SLM requires that WLM Service Classes designated for discretionary workload be assigned to a Resource Group with a defined maximum.

This condition is determined during SLM Policy validation when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: The validation or activation continues with a warning.

Operator response: Notify personnel responsible for support.

Programmer Response: Activate a valid WLM policy that has assigns the Service Class to a Resource Group with the attributes required by SLM.

DTM8123I

SERVICE CLASS service-class RESOURCE GROUP resource-group HAS NO MINIMUM


Explanation: The indicated WLM Service Class is defined in the SLM Policy as being for discretionary workload but is assigned to a Resource Group that does not have a minimum. SLM requires that WLM Service Class designated for ’DISCRETIONARY 1’ workload be assigned to a Resource Group with a defined minimum.

This condition is determined during SLM Policy validation whe activatning a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: The validation or activation continues with a warning.

Operator response: Notify personnel responsible for support

.Programmer Response: Activate a valid WLM policy that has assigns the Service Class to a Resource Group with the attributes required by SLM.

DTM8124I

SERVICE CLASS service-class RESOURCE GROUP resource-group HAS MINIMUM


Explanation: The indicated WLM Service Class is defined in the SLM Policy as being for discretionary workload but is assigned to a Resource Group that has a defined minimum. SLM requires that WLM Service Class designated for ’DISCRETIONARY 2’ workload be assigned to a Resource Group with no defined minimum.

This condition is determined during SLM Policy validation when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: The validation or activation continues with a warning.

Operator response: Notify personnel responsible for support.

Programmer Response: Activate a valid WLM policy that has assigns the Service Class to a Resource Group with the attributes required by SLM.

DTM8125I

SLM POLICY CONTAINS NO VALID SERVICE CLASS


Explanation: None of the WLM Service Classes designated in the SLM Policy are defined in the current WLM Policy.

This condition is determined during SLM Policy validation when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: If an alternative WLM Service Class can be found by SLM by searching the WLM Classification Rules for ‘JES’, the validation or activation continues with a warning.

Operator response: Notify personnel responsible for support.

Programmer Response: Define an SLM Policy that uses existing WLM Service Classes, or define the required Service Classes in the WLM Policy.

DTM8126I

SLM policy policy-name does not contain local JESplex member name member-name


Explanation: The local JESPLEX member name is not defined in the JESPLEX Configuration of the TM Automation File in which the SLM Policy was created.

This condition is determined during SLM Policy validation when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: If displayed on the console during Policy activation, the message is non-deletable (descriptor code 2). If the current action is validation or activation, the action fails with an error. If the current action is a Policy ACTIVATE at initialization or after the activation of a WLM Policy, the ACTIVATE continues with a warning.

Operator response: Notify personnel responsible for support.

Programmer Response: Use the SLM Definition Services Dialog to update the JESPLEX Configuration with the member name.

DTM8127I

SLM policy policy-name activated on member


Explanation: The indicated SLM Policy has been activated by SLM on the indicated member of the JESPLEX. SLM has activated the Policy at initialization or as a result of successful activation of a new SLM Policy on another member of the JESPlex, or activation of a new WLM Policy.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8128I

SLM policy policy-name activated on member with warnings


Explanation: The indicated SLM Policy has been activated by SLM on the indicated member of the JESPLEX. SLM has activated the Policy at initialization or as a result of successful activation of a new SLM Policy on another member of the JESPLEX, or activation of a new WLM Policy. There were non-critical errors for which warning messages have been issued.

System action: None.

Operator response: Notify personnel responsible for support.

Programmer Response: Review previous warning(s) and correct.

DTM8129I

SLM policy policy-name not activated on member due to errors


Explanation: An attempt to ACTIVATE the indicated SLM Policy on the indicated member of the JESPLEX failed due to errors. SLM tried to ACTIVATE the Policy at initialization or as a result of successful activation of a new SLM Policy on another member of the JESPLEX, or activation of a new WLM Policy but critical errors were found during validation.

System action: The Policy ACTIVATE is aborted.

Operator response: Notify personnel responsible for support.

Programmer Response: Review previous error message(s) and correct.

DTM8130I

SLM policy policy-name validated ‘validation-result’


Explanation:
validation-result: is the result of validation, and is one of:

  • Successfully
  • With warnings
  • With errors

SLM has just completed SLM Policy validation. The result of the validation is indicated in the message. If there were warnings or errors, explanatory messages are displayed on the console prior to this message.
SLM Policy validation occurs when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: SLM Policy ACTIVATE continues unless errors are found. Errors cause an SLM Policy ACTIVATE to be terminated.

Operator response: If there were errors or warnings, notify personnel responsible for support.

Programmer Response: If there were errors or warnings, review previous messages and correct.

DTM8131I

NO TYPES DEFINED


Explanation: The SLM Policy being validated has no Types defined.
This condition is determined during SLM Policy validation when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: The validation or activation request fails with an error.

Operator response: Notify personnel responsible for support.

Programmer Response: Use the SLM Definition Services Dialog to add the appropriate Control Center and Type definitions to the SLM Policy, then activate.

DTM8132I

SERVICE CLASS service-class WILL BE USED FOR ALL SLM MANAGED BATCH


Explanation: The indicated WLM Service Class will be assigned to all SLM-managed batch jobs when they are selected for execution. SLM Policy validation has determined that none of WLM Service Classes designated in the SLM Policy are defined in the active WLM Policy.
This condition is determined during SLM Policy validation when activating a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: The validation or activation continues with a warning.

Operator response: Notify personnel responsible for support.

Programmer Response: Activate a valid WLM Policy that defines the Service Classes specified in the SLM Policy.

DTM8133I

NO ACCEPTABLE WLM SERVICE CLASS AVAILABLE FOR SLM USE


Explanation: SLM has been unable to determine a WLM Service Class that is suitable for use by SLM batch jobs. None of WLM Service Classes designated in the SLM Policy are defined in the active WLM Policy, and SLM has been unable to find any suitable alternate Service Class by searching the WLM Classification Rules.
This condition is determined during SLM Policy validation whenactivat ing a Policy at SLM initialization, or as a result of a validation request from the SLM VALIDATE command, or an activation request from the SLM ACTIVATE command, or an activation or validation request from the SLM Definition Services dialog.

System action: The validation or activation request fails with an error.

Operator response: Notify personnel responsible for support.

Programmer Response: Activate a valid WLM Policy that defines the Service Classes specified in the SLM Policy.

DTM8135I

UNABLE TO OBTAIN JES2 CONTROL BLOCK INFORMATION. SLM TASK IS TERMINATING.


Explanation: During SLM initialization, one or more requests forJES2 control block fields and other JES2 related information failed.

System action: The Thruput Manager SLM subtask terminates.

Operator response: Notify personnel responsible for support.

Programmer Response: This is a potential Thruput Manager installation error. Review your installation, and correct any errors. If no errors are found, report this problem to BMC Support.

DTM8136I

DELAYED ACTIVATION OF SLM POLICY policy-name FAILED
RC=return-code REAS=reason-code


Explanation: A request to activate an SLM Policy was delayed due to temporary inability to access the Thruput Manager Control File. When the request was finally serviced, it terminated due to an error.

System action: The indicated Policy is not activated.

Operator response: Notify personnel responsible for support.

Programmer Response: Investigate Control File access problems. There are probably other messages issued indicating Control File access errors. If you are unable to resolve the problem, contact BMC Support.

DTM8137I

SLM POLICY I/O SUBTASK subtask-status


Explanation:
subtask-status: Is the status of the SLM Policy I/O subtask, and can be:
• STARTED, which occurs only at SLM initialization.
• FAILED, indicating that the subtask has terminated with an abend.
• RESTARTED, indicating that SLM has restarted the subtask
The state of the SLM Policy I/O subtask has changed.

System action: If the status is STARTED or RESTARTED, processing continues.
If the status is FAILED and the failures are less than 60 seconds apart, SLM restarts the Policy I/O subtask up to 3 times. The retry counter is reset when a failure occurs more than 60 seconds after the previous failure.

Operator response: If the status is FAILED or RESTARTED, notify personnel responsible for support.

Programmer Response: Collect diagnostic material and call BMC Support.

DTM8138I

AUTOMATION FILE MISMATCH DETECTED BY SLM


Explanation: An attempt to perform SLM Policy I/O has checked the current active DBS and SLM policies and determined that they originated from different Automation Files.

System action: None.

Operator response: Notify personnel responsible for support.

Programmer Response: Collect diagnostic material and call BMC Support.

DTM8139I

NO ACTIVE SLM POLICY IN CONTROL FILE


Explanation: SLM has attempted to read the current active SLM Policy from the Thruput Manager Control File and discovered that there is no active SLM Policy. This message is expected when SLM is first started after installation or when the Control File is cold started.

System action: SLM quiesces and no SLM-managed batch jobs will be selected for execution.

Operator response: Notify personnel responsible for support.

Programmer Response: Create and activate a valid SLM Policy.

DTM8140I

RECALL OF DATA SET dsname FAILED RC=nn.[jobid jobname HELD BY MHS_TM]


Explanation:
nn: Is the return code from the recall request.
For further information regarding this return code, see IBM message corresponding to the DFSMShsm return code (i.e. see IBM message ARC11nnI where ‘nn’ is the return code displayed in the message.
This message is non-deletable.The recall of a migrated data set failed. As a result, the job will be released from JSS hold, HSM category (if there are no other data sets requiring recall) and will be held by MHS_TM, HSM_FAIL category if the job is not PCS managed. PCS managed jobs are not held.
For the PCS managed jobs the part of the message referring to hold is not displayed.

System action: The non PCS job is held by MHS_TM. The PCS managed job is not held.

Operator response: Notify personnel responsible for support.

Programmer Response: Determine and correct the error. If possible, recall the data set by command and then release the affected job(s) by using the “MHS_TM RELEASE JOBS HSM_FAIL(dsname)” command.

DTM8141I

SLM SELECT DISPLAY
SELECT: operator-constraints
NOTES: operator annotation
or
NO OPERATOR CONSTRAINTS APPLIED


Explanation: This message is issued in the response to the SLM SELECT command. The first form of the message is displayed when the operator has put constraints on SLM job selection for the ambient member. The second form is displayed when there are no operator constraints on the ambient member.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8142I

TM INITIATOR INFORMATION
ANALYZERS=nnn MIN=nnn MAX=nnn
RECYCLETIME=nnn
RECYCLEJOBS=nnnn
MAXIMUM=nnnn
SLM MAXIMUM=nnnn
STARTED=nnnn
HALTED=nnnn
DRAINED=nnnn
--Type-- Busy Started 5Min 10Min 20Min 30Min 1Hour --ago--
Common nnnn nnnn nnnn nnnn nnnn nnnn nnnn
Analyzers nnnn nnnn nnnn nnnn nnnn nnnn nnnn
ON_DEMAND nnnn nnnn nnnn nnnn nnnn nnnn nnnn


Explanation: This message is issued in the response to the TM INITS command. It shows the current values for the modifiable fields: ANALYZERS, MIN, MAX, RECYCLETIME, RECYCLEJOBS. It also shows the counts for the various types of TM dynamic initiators currently deployed and their history for the past hour.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8143I

SLM Policy activate reset mode from old-mode to new-mode


Explanation: A successful SLM Policy activation occurred when the SLM Service Mode was set to a Service Mode other than the default mode for the new policy. The activation of the new SLM Policy causes the mode to be reset to the default Service Mode for that policy. This message is displayed only on the member of the JESplex on which the SLM Server is active; however, the mode change applies to the entire JESplex.

System action: The SLM Service Mode is reset for the entire JESplex.

Operator response: None.

Programmer Response: None.

DTM8144I

SLM ACTIVITY DATA RESET DUE TO POLICY CHANGE


Explanation: Activation of a new SLM Policy has made previous SLM Activity Data incomplete or incompatible. A change has been made to the number of members in the JESPlex as defined to SLM, or the name of a JESplex member has changed, or one of the related internal constants in the SLM Policy has been changed. SLM Activity Data has been reset.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8145I

UNABLE TO CREATE SLM ACTIVITY DATA SPACE


Explanation: SLM encountered an error when requesting creation of the SLM Activity Data Space. SLM Activity Data is used by SLM Display Services System Display panels. This information will not be available while this condition exists.

System action: The request is ignored.

Operator response: Notify personnel responsible for support.

Programmer Response: Issue the SLM SPIN TRACE command to create a SYSOUT file containing SLM trace information, then contact BMC Support.

DTM8146I

SLM FALLBACK COMPLETE, nnnnnn JOBS REQUEUED


Explanation: The SLM FALLBACK command was issued, and as a result of successful completion, the number of jobs indicated have been requeued to their original classes and priorities.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8147I

SLM FALLBACK FAILED


Explanation: The SLM FALLBACK command was issued, but did not complete successfully.

System action: Stops attempting to requeue jobs.

Operator response: Notify personnel responsible for support.

Programmer Response: Collect diagnostic material and call BMC Support.

DTM8150I

SLM UNABLE TO CONTACT PCS INSTANCE xxxx
DB:databasename N:nnnn


Explanation:
xxxx: is the name of the CA 7 Instance supported by PCS.
databasename: is the CA-7 database name.
nnnn: is the count of failures to this Instance and database name since the previous DTM8150I message for the same Instance and database name.
SLM has been unable to contact an instance of PCS. A failure occurred when SLM attempted to forward a message to PCS. SLM marks the message non-deletable. The message is only reissued for a subsequent failure if it has been at least 30 seconds since the last failure, in which case the previous message will be deleted. If SLM successfully contacts the indicated PCS Instance, any outstanding DTM8150I message for that Instance and database name will be deleted.

System action: None.

Operator response: Verify whether the PCS Instance name is valid. If valid, determine the system running that Instance of CA 7 and ensure that PCS is started on that system. If the named Instance is invalid, notify the person(s)responsible for support at your installation.

Programmer Response: None.

DTM8151I

jobname (JOB jobnumber) HAS INVALID PCS TIMES. DEFAULTS USED


Explanation: In order to ensure that PCS jobs are not delayed, when an invalid time for Target or Acceptable is detected by SLM, SLM has calculated new times based on internal constants in the active SLM policy which allows the job to be processed.

System action: None.

Operator response: Notify the person(s) responsible for support at your installation.

Programmer Response: None.

DTM8152I

SLM RECORDING TO target


Explanation:
target: Indicates the recording method used for SLM data, and is one of:
• FILE, indicating that SLM is recording to the SLM Collection File defined in the Thruput Manager initialization parameters.
• SMF, indicating that SLM is recordiing to the SMF file for each member of the JESplex.
• FILE AND SMF, indicating that SLM is recording to the SLM Collection File defined in the Thruput Manager initialization parameters and to the SMF file for each member of the JESplex.
This message documents the file or files used to record data for the SLM Reporter.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8153I

SLM RECORDING OPTION INCONSISTENT. FILE NOT SPECIFIED IN INITIALIZATION STATEMENTS.


Explanation: The SLM Policy being loaded, activated, or validated has the recording option set to indicate that SLM should record to the SLM Collection File, but the Thruput Manager initialization statements do not contain a FILE statement for the SLM Collection File.

System action: If the Policy is being activated or validated, the activation or validation fails. If the Policy is already active, and is being loaded at SLM initialization, the Policy load continues. SLM reverts to using SMF for recording.

Operator response: Notify personnel responsible for support.

Programmer Response: Ensure the recording option in the SLM Policy and the Thruput Manager initialization statements are consistent.

DTM8154I

SLM POLICY name IS INCOMPATIBLE WITH THE ACTIVE SLM LEVEL.


Explanation: The SLM Policy being loaded, activated or validated was created by a level of the SLM Definition Services dialog that is higher than the level of SLM that is active on the system on which the message is issued.
name: is the name of the SLM Policy.

System action: If the Policy is being activated or validated, then the activation or validation fails. If the Policy is already active, and is being loaded at SLM initialization, the Policy load fails.

Operator response: Notify personnel responsible for support.

Programmer Response: This problem may occur when running different levels of Thruput Manager in the same JESPlex. Ensure that the lowest level of SLM Definition Services dialog is used to create and update profiles until all members of a JESPlex are running the same level of SLM.

DTM8155I

Active Production Service Group missing: name


Explanation: While processing a validation or activation request for an SLM Policy, SLM determined that the indicated Production Service Group was not defined in the policy. At least one job in the SLM execution queue is currently assigned to that group.name: is the name of the Production Service Group.

System action: The warning message will be issued on the console by the SLM Definition Services dialog. The validation or activation will return an error.

Operator response: Notify personnel responsible for ThruPut Manager support.

Programmer Response: None.

DTM8156I

jobname (JOBnnnnnn) HAS INVALID PRODUCTION SERVICE TYPE/GROUP. DEFAULTS USED.

Explanation: SLM has found a Production job that has an invalid PCS service type (production importance) or Production Service Group name. SLM has used default values to calculate the target and acceptable queue times for the job.

System action: SLM uses default values to calculate target and acceptable queue times for the indicated job.

Operator response: Notify personnel responsible for ThruPut Manager support.

Programmer Response: None.

DTM8155I

ACTIVE PRODUCTION SERVICE GROUP MISSING: name.


Explanation: While processing a validation or activation request for an SLM Policy, SLM determined that the indicated Production Service Group was not defined in the policy. At least one job in the SLM execution queue is currently assigned to that group.
name: is the name of the Production Service Group.

System action: The warning message will be issued on the console by the SLM Definition Services dialog. The validation or activation will return an error.

Operator response: Notify personnel responsible for support.

Programmer Response: None.

DTM8156I

jobname (JOBnnnnnn) HAS INVALID PRODUCTION SERVICE TYPE/GROUP. DEFAULTS USED.


Explanation: SLM has found a Production job that has an invalid PCS Service type (production importance) or Production Service Group name. SLM has used default values to calculate the target and acceptable queue times for the job.

System action: SLM uses default values to calculate target and acceptable queue times for the indicated job.

Operator response: Notify personnel responsible for support.

Programmer Response: None.

DTM8160I

SLM POLICY name INCOMPATIBLE WITH MEMBERS: member-list.


Explanation: The SLM Policy being activated or validated was created by a level of the SLM Definition Services dialog that is higher than the level of SLM that is active on one or more members of the JESplex.
name: is the name of the SLM Policy.
member-list: is a list of the JESplex members up to a maximum of 14 members. If there are more than 14 members the list ends with the string '...'. .

System action: The SLM Policy activation or validation fails.

Operator response: Notify personnel responsible for support.

Programmer Response: This problem may occur when running different levels of Thruput Manager in the same JESplex. Ensure that the lowest level of SLM Definition Services dialog is used to create and update profiles until all members of a JESplex are running the same level of SLM.

DTM8161I

memname AT CAPACITY LEVEL n (limitid) USAGE IS ddddd


Explanation:memname: Is the local JESplex member name.n: Is the Capacity Level number.limitid: Is the limit or condition that was used in determining the Capacity Level


    • DEFINED CAPACITY -Defined Capacity for the LPAR as set in HMC.
    • POLICY LIMIT- Limit for LPAR set in the SLM Policy.
    • GROUP grpname - LPAR Group Capacity limit where

grpname: is the Group Name.


    • SET setname - LPAR Set limit where

setname: is the LPAR Set name.


    • MPX setname - Multiplex LPAR Set limit where

setname: is the Multiplex LPAR Set name


    • GROUP LEAD TIME - WLM estimated time to cap LPAR Group is less than configured lead time.
    • LPAR LEAD TIME - WLM estimated time to cap LPAR is less than configured lead time.
    • PERM CAPACITY - Rolling MSU consumption as a percentage of CPC Permanent Capacity.
    • CPC BUSY - Rolling average CPC busy.
    • MVS BUSY - Rolling average MVS busy.
    • MINIMUM - Minimum Capacity Level set by operator.
    • R4HA - Generic R4HA set after policy change for cases where reason was SET or MPX but LPAR Set may no longer be defined.

ddddd: Is one of the following:


    • INCREASING
    • DECREASING

SLM Capacity Management has just completed calculating the Capacity Level for the local JESplex member and is issuing this message to inform the operator that the Capacity Level or reason for Capacity Level has changed together with an indicator as to whether usage is increasing or decreasing, and the limit or condition used in calculating the Capacity Level. If just the reason has changed and the Capacity Level has not changed, then the message just shows the Capacity Level and reason without any indication of usage increasing or decreasing.

System action: SLM processing continues. Any constraints defined in the current SLM Policy for the indicated Capacity Level will now be in force.

Operator response: None.

Programmer Response: None.

DTM8162I

memname HAS REACHED FULL CAPACITY


Explanation:
memname: Is the local JESplex member name.
Automated Capacity Management has just completed calculating the R4HA for the local LPAR, and any relevant LPAR Group, and has determined that the R4HA now exceeds the corresponding limit. The LPAR may now be subject to soft capping by WLM and PR/SM.

System action: SLM processing continues. Any constraints defined in the current SLM Policy for Capacity Level 1 will now be in force.

Operator response: None.

Programmer Response: None.

DTM8163I

memname CAPACITY CONSTRAINTS RELIEVED


Explanation:
memname: Is the local JESplex member name.
SLM Capacity Management has just completed calculating the Capacity Level for the local JESplex member and is issuing this message to inform the operator that the usage has fallen to a point where no Capacity Level is assigned to the LPAR.

System action: SLM processing continues. No Capacity Management constraints defined in the current SLM Policy are being applied.

Operator response: None.

Programmer Response: None.

DTM8164I

SERVICE CLASS NOT SPECIFIED FOR DISCRETIONARY n


Explanation:
n: Is 1 or 2.
The SLM Policy does not have a WLM Service Class specified for the indicated Discretionary Services Service Class.
If a Discretionary Services class has been specified using the ‘TM CLASS SET DISCRETIONARY’ command, the SLM Policy must specify Service Classes for both Discretionary 1 and 2.
This condition is determined during SLM policy validation.
SLM Policy validation occurs when loading a policy at SLM initialization, activation of a new WLM policy, or as a result of either a validation or activation request from the ‘TM SLM’ command or the SLM Definition Services dialog.

System action: This message will be issued on the console or by the SLM Definition Services dialog. If the current action is validation or activation, it will fail with an error. If the current action is policy load at initialization, it will be treated as a warning and the policy load will continue.

Operator response: Notify the person responsible for support.

Programmer Response: Activate a valid SLM policy that does specify a Service Class for the indicated Discretionary Services Service Class.

DTM8165I

NO SLM SERVICES CONFIGURED


Explanation: SLM Policy validation or activation has determined that the current Policy does not have any SLM Services configured and is therefore considered incomplete and in error. At least one of General Services, PCS or Capacity Management must be configured.

System action: This message will be issued on the console or by the SLM Definition Services dialog. The validation, activation or load of the Policy will fail with a severe error.

Operator response: Notify personnel responsible for support.

Programmer Response: None.

DTM8166I

GENERAL SERVICES NOT CONFIGURED BUT THERE ARE JOBS ON THE QUEUE


Explanation: SLM policy validation/activation has determined that the Policy being validated/activated does not have General Services configured. However, it has detected queued or executing General Services jobs. The Policy cannot be loaded until these jobs are no longer queued or executing as they would not be processed correctly.

System action: This message will be issued on the console or by the SLM Definition Services dialog. The validation, activation or load of the policy will fail with a severe error.

Operator response: Notify personnel responsible for support.

Programmer Response: None.

DTM8167I

PCS NOT CONFIGURED BUT THERE ARE JOBS ON THE QUEUE


Explanation: SLM Policy validation/activation has determined that the policy being validated/activated does not have PCS configured. However, it has detected queued or executing PCS jobs. The Policy cannot be loaded until these jobs are no longer queued or executing as they would not be processed correctly.

System action: This message will be issued on the console or by the SLM Definition Services dialog. The validation, activation or load of the policy will fail with a severe error.

Operator response: Notify personnel responsible for support.

Programmer Response: None.

DTM8168I

DISCRETIONARY SERVICES NOT CONFIGURED BUT THERE ARE JOBS ON THE QUEUE


Explanation: SLM policy validation/activation has determined that the Policy being validated/activated does not have Discretionary Services configured. However, it has detected queued or executing Discretionary Services jobs. The Policy cannot be loaded until these jobs are no longer queued or executing as they would not be processed correctly.

System action: This message will be issued on the console or by the SLM Definition Services dialog. The validation, activation or load of the policy will fail with a severe error.

Operator response: Notify personnel responsible for support.

Programmer Response: None.

DTM8169I

SUBSTITUTIONS MADE FOR SERVICE CLASSES NOT SPECIFIED IN WLM POLICY


Explanation: To allow Policy load to continue, SLM has made substitutions for Service Classes that are not defined in the active WLM Policy. Where possible SLM will use other Service Classes specified in the SLM Policy that are defined in the active WLM Policy.

System action: This message will be issued on the console.

Operator response: Notify personnel responsible for support.

Programmer Response: None.

DTM8172E

INITIATORS CONSTRAINED ON name DUE TO resource SHORTAGE


Explanation:

name: Is the local JESplex member name

resource: Identifies the resource:

              SQA

              CRITICAL SQA

              CRITICAL ADDRESS SPACE ID

Deployment of ThruPut Manager initiators is constrained on the indicated system due to a shortage of a z/OS resource.

SLM has detected a shortage of one of the following system resources:

  • SQA: virtual system queue area below the 16 MB line
  • Address Space Id: Available address space ids that can be assigned to batch jobs as limited by the MAXUSER parameter in the IEASYSxx member of PARMLIB.

NOTE: This message does NOT indicate a problem in ThruPut Manager.  ThruPut Manager is ensuring that datacenter personnel are aware of this z/OS related resource shortage, and that as a result, both z/OS and ThruPut Manager will be taking certain actions while the shortage exists.  For SQA shortages you should also see one or both of the following z/OS messages: IRA100E, IRA101E.  For Address Space Id shortages, you may see the z/OS message IEA602I..

System action: 

When any one of the above shortage types is initially detected, all ThruPut Manager halted initiators are drained immediately.  While any shortage exists, no ThruPut Manager initiators will be started.  This includes On Demand service initiators. 

Dynamic analyzer initiators will be reduced to the minimum value.  If the minimum is set to zero, then the value of the number of analyzers per 100 jobs in the queue will be used.  See the TM INITS command documentation or help for further details.

As initiators are trimmed by SLM, they will be drained instead of halted (halted is the normal action) to help reduce consumption of the indicated resource.

This message will be repeated every 60 seconds for warnings and 30 seconds for critical shortages.  These interval values may be changed in the SLM Policy.  In the SLM Dialog, select Configure JESPLEX Characteristics-> Customize > Miscellaneous Custom Options

Operator response: Notify system support personnel.

Programmer Response: For SQA shortages, look in the system log for message IRA100E and/or IRA101E which will have been issued by WLM when the shortage or critical shortage began.  For Address Space Id shortages, you may see one or more IEA602I messages.  Follow the IBM recommended response for the corresponding message.

For address space id shortages, consider increasing MAXUSER and related parameters in the IEASYSxx PARMLIB member.  You may also find z/OS message IEA602I in the system log.

DTM8173I

resource SHORTAGE RELIEVED ON name


Explanation:

resource: Identifies the resource as follows:

SQA

AUXILIARY STORAGE

PAGEABLE STORAGE

ADDRESS SPACE ID

name: Is the local JESplex member name

SLM previously issued either a DTM8172E or DTM8191E message due to a shortage of the indicated system resource.  That resource shortage no longer exists

System action: Normal SLM operation resumes. SLM deletes the previously issued DTM8172E message.

Operator response: Notify system support personnel.

Programmer Response: None.

DTM8174I

SLM RECYCLING DUE TO reason


Explanation:
reason: Is the reason for SLM recycling. It can be one of the following:
• SERVER PREFERENCE – SLM has determined that there is another instance of SLM
in the JESplex that has a higher server preference as supplied in the active SLM policy.
The current instance of SLM is recycling to give up the server role and allow the other
instance of SLM to become server.
• OPERATOR COMMAND – The operator has issued the command TM OPT RECYCLE SLM.
This is an informational message.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8177E

SLM on memname1 has detected incomplete handshake with SLM on memname2


Explanation:
memname1: is the name of JESplex member that detected the incomplete handshake.
memname2: is the name of the JESplex member that has not responded as expected.
SLM on one member of the JESplex has not fully established communications via XCF with SLM on another member of the JESplex.

System action: SLM may not function properly on the indicated member (memname2). Various symptoms may be exhibited. If the handshake is completed, or SLM terminates on the indicated JESplex member, the message will be deleted.

Operator response: Inform the person(s) responsible for support at your installation.

Programmer Response: If the message persists, restart SLM on the indicated JESplex member using the command TM OPT RECYCLE SLM. Contact support.

DTM8178I

SLM on memname attempting resync with SLM Server


Explanation:
memname: is the name of JESplex member.
SLM on the indicated member of the JESplex has not received an update from the SLM Server for an excessive period of time. SLM is attempting to reestablish communications with the SLM Server.
SLM on a non-Server expects to receive frequent updates from the SLM Server. If updates are not received, it can significantly affect or even prevent the selection of SLM managed jobs. Therefore an attempt is made to reestablish communications in case of a dropped or out of sequence message.

System action: SLM may not function properly on the indicated JESplex member. Various symptoms may be exhibited.

Operator response: Inform the person(s) responsible for support at your installation.

Programmer Response: If the message persists, restart SLM on the indicated member using the command TM OPT RECYCLE SLM. Contactsupport.

DTM8179I

SLM has detected nnnn jobs with duplicate name jobname


Explanation:
jobname: is the job name
nnnn: is the number of jobs with the indicated name
When JES2 duplicate job name checking is active, having an excessive number of jobs with the same name may cause system performance issues. Since these issues may be difficult to diagnose, SLM checks for this condition in order to provide additional information to operations personnel.

System action: Performance degradation may be noticeable.

Operator response: If system performance degradation is noticed, take actions to reduce the number of duplicate jobs.

Programmer Response: If system performance degradation is noticed, take actions to reduce the number of duplicate jobs.

DTM8180E

SLM detected job initiation delay. ASID=xxxx Job=jjjjjjjj


Explanation:
xxxx: is the ASID of the address space
jjjjjjjj: is the JES2 job-id of the job
As part of its system performance analysis every 10 seconds, SLM checks on the status of the Thruput Manager initiators used to run SLM managed jobs. If SLM detects that a job has been selected but has not been initiated for five seconds, it issues a non-deletable message to alert operations personnel. The assumption is that there is a significant system performance problem affecting job initiation. The five-second time value can be changed in the SLM policy if desired. In the SLM dialog, select Configure JESPLEX Characteristics>Customize>Miscellaneous Custom Options.

System action: SLM will not activate any further Thruput Manager initiators while the condition exists. SLM will delete the message once the condition clears.

Operator response: If condition persists alert the appropriate personnel to investigate the cause of poor system performance as until this condition is cleared SLM will not add initiators and work will be delayed in the queue.

Programmer Response: Investigate the cause of slow job initiation after selection.

DTM8181E

SLM detected possible initiator hang. ASID=xxxx Job=jjjjjjjj


Explanation:
xxxx: is the ASID of the address space
jjjjjjjj: is the JES2 job-id of the job
SLM has detected a serious delay in initiating a batch job that has been selected. This may indicate that an initiator is hung.
As part of its system performance analysis every 10 seconds, SLM checks on the status of the Thruput Manager initiators used to run SLM managed jobs. If SLM detects that a job has been selected but has not been initiated for a considerable time, it issues a non-deletable message to alert operations personnel of a possible initiator hang condition.

System action: SLM continues to function normally and will start additional initiators as warranted. SLM will delete the message once the condition clears.

Operator response: Alert the appropriate personnel to investigate the apparent initiator hang.

Programmer Response: Investigate the indicated address space. It may be necessary to terminate the indicated address space.

DTM8182E

Maximum initiator limit in SLM Policy reached on jmemN


Explanation:
jmemN: is the JESplex member on which the maximum has been reached.
The number of active initiators for General Services and Production Services has reached the maximum specified in the active SLM Policy on the indicated member of the JESplex.

System action: SLM will not add any further initiators. This may cause batch jobs to queue more than normal. This message will be issued every time the limit is reached but not more frequently than once per minute.

Operator response: Alert the appropriate personnel to investigate whether more initiators are required and make SLM Policy adjustments if so.

Programmer Response: If more initiators are warranted, update the SLM Policy to allow for more initiators on the indicated JESplex member.

DTM8183E

Maximum initiator limit in SLM Policy reached on jmemN


Explanation:
jmemN: is the JESplex member on which the condition has occurred.
All Thruput Manager initiators are being used to support General Services, Production Services, Thruput Manager analyzers and On Demand jobs.

System action: SLM cannot add any further initiators. This may cause batch jobs to queue more than normal. This message will be issued every time the condition occurs but not more frequently than once per minute.

Operator response: Alert the appropriate personnel to investigate whether more initiators are required.

Programmer Response: If more initiators are warranted, update the TMPARMS JES2 initialization statement to increase the number of Thruput Manager initiators. ReIPL or use the $MJ command to activate. Contact support for more information if required.

DTM8184I

SLM Policy name has no initiator maximum for xxxxxx - ON DEMAND class defined


Explanation:
name: is the SLM Policy name.
xxxxxx: is either "member nnnn" where nnnn is the JESplex member with no limit, or "all members" when there is no default maximum and no specific maximums have been specified for individual members.
The named SLM Policy does not have a maximum specified for General Services and Production Services initiators for the indicated JESplex member. There is an ON DEMAND class defined.
ON DEMAND jobs also use Thruput Manager initiators. A maximum limit for SLM initiators may be appropriate in order to ensure there are enough initiators available for use by ON DEMAND.
This message is issued during the loading, validation and activation of an SLM Policy.

System action: Policy loading, validation or activation continues.

Operator response: Alert the appropriate personnel.

Programmer Response: Evaluate current initiator usage and determine if a maximum limit on SLM initiators is warranted. Update the SLM Policy if required.

DTM8185E

SLM Policy name at higher level than SLM on member memname


Explanation:
name: is the SLM Policy name
memname: is the JESplex member on which the condition has occurred.
The named SLM Policy was created or last saved by a maintenance or release level of Thruput Manager higher than that on the indicated JESplex member which is currently loading the policy.
A newer level of SLM was used to create or update the active SLM policy, possibly when the indicated member was not active. This message is issued during SLM Policy load.

System action: Policy loading continues.

Operator response: Alert the appropriate personnel.

Programmer Response: Plan to upgrade Thruput Manager on the indicated member in the near future as policy updates will not be possible if the indicated member becomes SLM Server.

DTM8186E

SLM unable to start. DTMJ2SV7 is downlevel.


Explanation: SLM has detected that the DTMJ2SV7 module that is loaded does not support the current level of SLM.

System action: SLM terminates.

Operator response: Alert the appropriate personnel.

Programmer Response: Ensure that the updated DTMJ2SV7 module is loaded before starting Thruput Manager.

DTM8187E

SLM policy could not be loaded on memname. Not authorized to access Automation File.


Explanation:
memname: is the JESplex member on which the error occurred.
Thruput Manager is currently not authorized to access the Automation File and therefore cannot load the current active SLM Policy.

System action: SLM retries the policy load periodically. SLM processing is quiesced. No jobs will be selected.

Operator response: Alert the appropriate personnel.

Programmer Response: Authorize Thruput Manager to access the Automation File and restart Thruput Manager.

DTM8188I

JES2 not up. Unable to verify all required Service Groups defined in policy.

Explanation: When an SLM policy is being activated or validated and there is no current active SLM policy, SLM needs information on jobs currently in the JES2 queues to ensure that all Service Groups in use by those jobs (if any) have been defined in the new SLM policy. SLM is unable to get that information because JES2 is not currently up.

System action: Activation/validation of the SLM policy is terminated.

Operator response: Inform the person responsible for ThruPut Manager and/or JES2 at your installation.

Programmer Response: Investigate the reason JES2 is not active.

DTM8189I

Unable to obtain JES2 checkpoint version during policy activation/validation.


Explanation: When an SLM policy is being activated or validated and there is no current active SLM policy, SLM needs information on jobs currently in the JES2 queues to ensure that all Service Groups in use by those jobs (if any) have been defined in the new SLM policy. An error is being returned when SLM attempts to get that information from JES2. The most likely scenario is that JES2 is not up or not fully initialized.

System action: Activation/validation of the SLM policy is terminated.

Operator response: Inform the person responsible for ThruPut Manager and/or JES2 at your installation.

Programmer Response: Check if JES2 is fully up and functional. If there are no apparent JES2 problems, open a case with ThruPut Manager support.

DTM8190I

MINCAPLVL ignored. ACM is not enabled.


Explanation: An SLM SELECT command is attempting to change the minimum Capacity Level but ACM is not enabled in the active SLM Policy and therefore this operation is not currently valid.

System action: The SLM SELECT command is not processed.

Operator response: Do not issue SLM SELECT MINCAPLVL if your installation does not have Automated Capacity Management (ACM) enabled in the active SLM  Policy.

Programmer Response: None

DTM8191E

SLM JOB SELECTION HALTED ON member DUE TO resource SHORTAGE


Explanation:

member: Is the local JESplex member name

resource: Identifies the resource as follows:

AUXILIARY STORAGE

PAGEABLE STORAGE

If the resource usage has reached a z/OS internal threshold value, the resource description will be prefaced with "CRITICAL".

Selection of SLM managed jobs has stopped on the indicated system and deployment of ThruPut Manager initiators is constrained due to a shortage of a z/OS Resource.

SLM has detected a shortage of one of the following system resources:

  1. Auxiliary Storage: Available slots in the auxiliary storage paging space in paging data sets and storage-class memory.
  2. Pageable Storage: Pageable storage frames.

NOTE: This message does NOT indicate a problem in ThruPut Manager.  ThruPut Manager is ensuring that datacenter personnel are aware of this z/OS related resource shortage, and that as a result, both z/OS and ThruPut Manager will be taking certain actions while the shortage exists.  For Auxiliary Storage shortages you should see one or both of the following z/OS messages: IRA200E, IRA201E.  For Pageable Storage shortages, you should see one or both of the following z/OS messages: IRA400E, IRA401E.

System action:  When either of the above shortage types is initially detected, all ThruPut Manager halted initiators are drained immediately. 

SLM will not approve job selection while either of these two shortages exist.  This is in keeping with the z/OS response to these shortages: z/OS prevents initiators from selecting jobs.

While any shortage exists, no ThruPut Manager initiators will be started.  This includes On Demand service initiators.

Dynamic analyzer initiators are reduced to the minimum value.  If the minimum is set to zero, then the value of the number of analyzers per 100 jobs in the queue will be used.  See the TM INITS command documentation or help for further details.

As initiators are trimmed by SLM, they are drained instead of halted (halted is the normal action) to help reduce consumption of the indicated resource.

This message will be repeated every 60 seconds for warnings and 30 seconds for critical shortages.  These interval values may be changed in the SLM Policy.  In the SLM Dialog, select Configure JESPLEX Characteristics-> Customize > Miscellaneous Custom Options

Operator response:  Notify system support personnel.

Programmer response: Look in the system log for messages IRA200E, IRA201E, IRA400E or IRA401E which will have been issued by WLM when the shortage or critical shortage began.  Follow the IBM recommended response for the corresponding message.

DTM8192I

Performance Focus focusname references disabled Service Mode modename


Explanation: 

focusname: Name of the Performance Focus Definition

modename: Name of the disabled Service Mode

A Performance Focus Definition has a Service Mode specified that is not enabled for at least one General Services Control Center or Work Type.

SLM policy validation has rejected the SLM Policy since using this Performance Focus Definition may not have the desired results.  This error likely indicates an oversight when defining the SLM Policy.

System action: Policy validation or activation failed with an error.

Operator response: Notify system support personnel.

Programmer Response: Correct the SLM policy by either specifying an enabled Service Mode for the Performance Focus Definition or enabling the indicated Service Mode.

DTM8193E

TFP-HW corridor incorrectly specified in active SLM policy for cpcname tttt ss-sssss


Explanation:

cpcname is the name for the CPC assigned in the SLM Policy

type is the 4 digit IBM type of the CPC

ss-sssss is the serial number of the CPC

The IBM Tailored Fit Pricing Hardware Consumption Solution corridor size specified for the local CPC in the active SLM Policy is incorrect.   

During its performance analysis performed every 10 seconds, ThruPut Manager verifies that the corridor size specified for the local CPC is reasonable.  If the Temporary Capacity of the CPC as reported by  z/OS is less than Permanent Capacity plus the corridor size (specified in the SLM Policy), then the corridor size cannot be correct.  While the condition persists, this message is issued approximately every 5 minutes.                                                    

System action:  None. Processing continues. SLM defaults to Purchased Capacity = Permanent Capacity for use by the ACM Purchased Capacity Limit Type.      

Operator response:  Notify the person responsible for support.

Programmer Response:  Correct the corridor size specified in the SLM Policy and activate the new policy.

DTM8194I

TFP-HW corridor incorrectly specified for cpcname tttt ss-sssss


Explanation:

cpcname is the name for the CPC assigned in the SLM Policy

type is the 4-digit IBM type of the CPC

ss-sssss is the serial number of the CPC

SLM Policy validation has determined that the IBM Tailored Fit Pricing Hardware Consumption Solution corridor size specified for the indicated CPC in the SLM Policy is incorrect.                                                            

During SLM Policy validation, if specified, the TFP-HW corridor size is validated for each CPC configured under the ACM Purchased Capacity Limit Type.  The Temporary Capacity for the CPC as reported by z/OS must not be less than the Permanent Capacity plus the corridor size specified in the SLM policy being validated.                                             

System action:  This is a warning message only.  Policy validation continues as part of policy load, policy validation or policy activation.                                      

Operator response:  Notify the person responsible for support.

Programmer Response:  Correct the corridor size specified in the SLM Policy and activate the new policy.

DTM8200I

SLM POLICY DISPLAY
NAME=policy-name
DESCRIPTION=’policy-descripion’
AUTOMATION FILE=dataset-name,VOL=volser
CREATED ON ccyy.ddd AT hh:mm:ss BY userid
MODIFIED ON ccyy.ddd AT hh:mm:ss BY userid


Explanation: This message is issued in response to the SLM DISPLAY POLICY operator command.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8201I

SLM policy policy-name policy-status


Explanation:
policy-name: is the name of the ACTIVE SLM Policy.
policy-status: is the result of the command and is one of:
• activated
• failed activation
• activated with warnings
• activation timed out
• activation delayed
• validated
• failed validation
• validated with warnings
This message is issued in response to the SLM ACTIVATE or SLM VALIDATE command.

System action: As described by the message text.

Operator response: None.

Programmer Response: If the Policy is not activated or validated, see to accompanying messages, correct errors, and re-issue the command.

DTM8202I

SLM policy policy-name not found


Explanation: This message is issued in response to the SLM ACTIVATE, SLM DISPLAY, or SLM VALIDATE operator command, and indicates that the specified Policy does not exist in the Automation File from which the current ACTIVE Policy was activated.

System action: None.

Operator response: Ensure the Policy name was entered correctly.

Programmer Response: None.

DTM8203I

NO “ACTIVE” SLM POLICY FOUND


Explanation: This message is issued in response to the SLM DISPLAY or SLM VALIDATE operator command, and indicates that currently there is no ACTIVE SLM Policy.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8204I

SLM IS NOT IN SPECIFIED SERVICE MODE


Explanation: This message is issued in the response to the SLM DEACTIVATE MODE command and indicates that the current SLM Service Mode does not match the Service Mode entered on the command.

System action: Processing continues using the current SLM Service Mode.

Operator response: Re-enter specifying the correct SLM Service Mode.

Programmer Response: None.

DTM8205I

NO “ACTIVE” AUTOMATION FILE COMPONENT


Explanation: This message is issued in response to the SLM ACTIVATE or SLM VALIDATE operator command, and indicates that SLM is not currently active.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8206I

AF SIGNATURE MISMATCH
APP SIGNATURE RC DSN
DBS time-stamp ret-code dsname
SLM time-stamp ret-code dsname
Explanation: This message can result from any SLM or DBS operator command, and indicates that the components within the Automation File have gotten out of synchronization.

System action: None.

Operator response: Notify personnel responsible for support.

Programmer Response: Re-format the SLM and DBS Control File sections and reactivate the Policy/Configuration.

DTM8207I

AF JESPLEX MISMATCH
NODE SPOOL DSN VOL
TM nodename dsname volser
AF nodename dsname volser
Explanation: This message can result from any SLM or DBS operator command, and indicates that the JESplex information in the Automation File and for the current member have gotten out of synchronization.

System action: None.

Operator response: Notify personnel responsible for support.

Programmer Response: Re-format the SLM and DBS Control File sections and reactivate the Policy/Configuration.

DTM8208I

NO CATALOGED AUTOMATION FILE DATA SET
Explanation: This message can result from any SLM or DBS operator command, and indicates that the Automation File as defined in the Control File is not cataloged.

System action: None.

Operator response: Notify personnel responsible for support.

Programmer Response: Catalog the Automation File or correct the definition of the Automation File in the Control File.

DTM8209I


Explanation: This is an internal diagnostic message.

DTM8210I


Explanation: This is an internal diagnostic message.

DTM8211I


Explanation: This is an internal diagnostic message.

DTM8212I

[DBS | SLM] IS DISABLED.


Explanation: This message can result from any DBS or SLM command, and indicates that the specified application is currently disabled.

System action: The command is ignored.

Operator response: None.

Programmer Response: None.

DTM8213I

SLM SUMMARY
POLICY : policy-name
SERVICE MODE : service-mode
SLM SERVER ON MEMBER : jes2-member
GS OPERATOR CONSTRAINTS : gs-constraints
BATCH SERVICE: : batch-service
PCS OPERATOR CONSTRAINTS : pcsop-constraints
PCS SELECTION OPTION : pcs-select
CAPACITY MANAGEMENT : cmgtstatusMINIMUM ACM CAPACITY LEVEL: minstatus
ONLINE PERFORMANCE PROTECTION : oppstatus


Explanation:
policy-name: is the name of the ACTIVE SLM Policy.
service-mode: is the current SLM Service Mode, and can be one of:
• STANDARD
• PRIME
• PRIME_EAST
• PRIME_WEST
• NON_PRIME
• WEEKEND
• INSTALLATION1
• INSTALLATION2
jes2-member: is the name of the JES2 member on which the SLM Server is active.
gs-constraints: displays any operator modifications to the criteria used to select SLM-managed jobs.
batch-service: is the SLM Service Level that batch work is currently receiving.
pcsop-constraints: indicates any Operator modifications of the criteria used to select PCS jobs.
pcs-select: is the current PCS Job Selection Mode, and can be one of:
• PREFER
• PREEMPTminstatus: is the status of any minimum ACM Capacity Level that has been set  by the operator using the SLM SELECT command, either the value of the minimum (1-5) or "NOT SET"cmgtstatus: is the Capacity Management status:
• CONFIGURED
• NOT CONFIGURED
oppstatus: is the status of Online Performance Protection:
• CONFIGURED
• CONSTRAINED
• NOT CONFIGURED
This message is the response to the SLM DISPLAY SUMMARY command.

System action: None

Operator response: None.

Programmer Response: None.

DTM8214I

SLM TRACE WRITTEN TO SYSOUT ddname


Explanation: SLM trace data has been written to the indicated SYSOUT data set.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8215I

Start Initiated for JOBnnnnn
Explanation: The SLM START command was issued for the indicated job.

System action: The job is selected for immediate execution .

Operator response: None.

Programmer Response: None.

DTM8216I

Jobid not eligible
Explanation: The SLM START or ABANDON command was issued for the indicated job, but the job was either not awaiting execution or was not managed by SLM.

System action: The command is ignored.

Operator response: Possible input error. Check and if necessary, re-enter.

Programmer Response: None.

DTM8217E

JOBnnnnn Delayed! See DTM0220I.
Explanation: The SLM START command was issued for the specified job, but the request was rejected because the job is delayed by a Thruput Manager application.

System action: The job is placed at the top of it’s class queue and is flagged as “Important”.

Operator response: Examine the DTM0220I response. Consider using the TM ABANDON command to free the job from multiple applications.

Programmer Response: None.

DTM8218I

Command failed, JES2 Interface Error
Explanation: The SLM START or ABANDON command was issued and an internal error caused the request to fail. This can occur if JES2 is currently not active.

System action: The command is ignored.

Operator response: Re-enter the command once JES2 is operating normally.

Programmer Response: None.

DTM8219I

SLM JESplex Status
Member: nnnn   State: state
cpc-name Type: uuuu Serial: vv-vvvvv PCpcty: purch
Logical Processors Active: aa Parked: pp Q: ww.ww%
Averages  MVS: mvsb* [CPC: | CPCz:]: cpcb*  PCpcty: pcap* CPC MSU: msu*
Capacity Management at yyyy.ddd hh:mm:ss Sync: s
SLM Capacity Level: l  Minimum: m* 
xxxx * 4h Avg: bbbb Int: cccc Lmt:llll Cap: dd%
Avg jobs limited by Service Class. GS: kkk.k PS: mmm.m
Avg jobs limited by Service Class: tttt.t
gggg * 4h Avg: bbbb Int: cccc Lmt:llll Shr: jjjj
ssss * 4h Avg: bbbb Int: cccc Lmt:llll
*MPX* * 4h Avg: bbbb Int: cccc
-Mobl 4h Avg: bbbb Int: cccc
-CatA 4h Avg: bbbb Int: cccc
-TRGs 4h Avg: bbbb Int: cccc
Constraints:
Color (color)
System Resources (WLM)
MaxInits
Operator(GS,None)
QuickOnly)
SelPt=selpt)
Operator(PS,None)
QuickOnly)
CPU(GS)
OPP
...
Explanation:

System Resources (WLM): WLM is reporting that system resources are contrained on this member. SLM will have issued message DTM8172E. See the documentation for DTM8172E for further information.
name: Is the JESplex member name.
state: Is the state of the JESplex member, and can be:

  • SLM Server active—SLM is active on the member and is the SLM JESplex Server.
  • SLM Active—SLM is active on the JESplex member.
  • SLM *Inactive*—JESplex member is active but SLM is not running.
  • Member Inactive—JESplex member is not active.
  • SLM Active on SE—SLM is active on the member but the member is running TM Standard Edition.

cpc-name: The text ‘CPC’ or the name of the CPC as configured in the active SLM Policy of the CPC on which the member resides.

uuuu: The 4 digit IBM CPC type.

vv-vvvvv: The serial number of the CPC.

purch: The current Purchased Capacity of the CPC.

aa: The number of active logical processors on the LPAR on which the member is running.

pp: The number of parked logical processors on the LPAR on which the member is running.

ww.ww: The percentage of time that the LPAR is queued to be dispatched on a physical processor.

mvsb: Rolling average of MVS busy %

cpcb: Rolling average of CPC busy %.  If preceded by "CPC:" this is the average CP busy.  If preceded by "CPCz:" this is the combined average of CP and zIIP busy.

pcap: Rolling average CPC MSU consumption as a percentage of CPC Permanent Capacity

msu: Rolling average CPC MSU consumption

yyyy.ddd hh:mm:ss: Date/time of last Capacity Management analysis

s: Y or N – indicates whether Capacity Management Analysis is synchronized with IBM LPAR Group Analysis (only present if LPAR is a member of an LPAR Group).

l: Current SLM Capacity Level if set. Otherwise this line is not displayed.

m: Current minimum Capacity Level if set by operator, otherwise is not displayed.

xxxx: Is the LPAR name.
*: An asterisk is used to indicate which ACM Limit Type (e.g., LPAR Set, Defined Capacity, CPC Busy, Permanent Capacity %) was used to determine the Capacity Level because its usage was the most significant when compared to its limit or, if an exclamation point (!), the estimated time to cap is below the configured capping lead time.
bbbb: Is the 4-hour average usage in MSU/hr.
cccc: Is the usage in last 5 minute interval in MSU/hr.
dd: Is the percent time LPAR capped in last 5 minute interval.
kkk.k: Average number of General Services jobs in the ACM Service Class(es) in the last 5-minute interval. Only displayed if different ACM Service Classes specified in the SLM policy for General Services and PS. Otherwise only the line with the total is displayed.
mmm.m: Average number of PS jobs in the ACM Service Class(es) in the last 5 minute interval. Only displayed if different ACM Service Classes specified in the SLM policy for General Services and PS. Otherwise only the line with the total is displayed.
tttt.t: Average number of SLM managed jobs in the ACM Service Class(es) in the last 5-minute interval. Only displayed if installation has only General Services or PS defined or if the same ACM Service Classes are specified for use by both General Services and PS jobs.
gggg: Is the LPAR Group name.
llll: Is the limit for LPAR, LPAR Group, or LPAR Set in MSU/hr. If a Multiplex LPAR Set limit is followed by an asterisk (*), this is an override value substituted due to inconsistencies in the Multiplex limit as specified in the SLM Policies in different JESplexes. The limit from the most recently updated policy is used.
jjjj: Is the LPAR share in MSU/hr.
sssss: Is the LPAR Set name. If the LPAR Set is a Multiplex LPAR Set, there will be a second line immediately below with '*Multiplex*' as the name containing the Multiplex LPAR Set aggregate statistics.
*MPX* LPAR Set is defined as Multiplex. Average, interval usage and limit are for the multiplex.
-Mobl Multiplex wide average and interval usage for workload in the LPAR Set classified by WLM as MOBILE. Line is only displayed when mobile usage is present and the SLM Policy specifies mobile usage should be discounted.
-CatA Multiplex wide average and interval usage for workload in the LPAR Set classified by WLM as CATEGORYA. Line is only displayed when category A usage is present and the SLM Policy specifies category A usage should be discounted.
-TRGs Multiplex wide average and interval usage for workload in the LPAR Set classified by WLM into Tenant Resource Groups. Line is only displayed when usage is present.
color: The current SLM color for this JESplex member, indicating how well the member is running is running this particular type of workload. Color ranges from green (running well),  to blue, yellow, orange, and finally to red (experiencing problems).
CPU: If present, indicates that the JESplex member has reached the maximum CPU workload specified in the active SLM Policy. This applies only to General Services.
OPP: If present, indicates that Online Performance Protection constraints are currently active on the JESplex member.
MaxInits: If present. indicates that the JESplex member has reached the maximum number of initiators specified for this type of workload in the active SLM Policy.
Operator: If present, indicates that an SLM SELECT operator command has been used to restrict job selection for this member of the JESplex.
System Resources (WLM): WLM is reporting that system resources are constrained on this member. SLM will have issued message DTM8172E. See the documentation for DTM8172E for further information.
This message is issued in response to a SLM D JESPLEX operator command. Capacity Management must be enabled in order for the LPAR and LPAR Group usage to be displayed. The lines are repeated for each member displayed.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8220I

SLM Service Group Status
Control Center: ccenter
JESPlex Constraints: Jobs
Constraints by JESPlex Member:
name CPU Jobs ACMjobs
Type: type
JESPlex Constraints: AgeLmt Jobs
Constraints by JESPlex Member:
name Color(color) CPU Jobs SelPt ACMjobs
...
Explanation:
ccenter: Is the Control Center name.
name: Is the JESplex member name.
CPU: Indicates that the JESplex member has reached the maximum CPU workload for the Service Group specified in the active SLM Policy.
Jobs: Indicates that SLM has reached the maximum number of executing jobs in the JESPlex for the Control Center as specified in the active SLM Policy.
ACMJobs: Indicates that SLM reached maximum number of executing jobs on this JESplex member for the current ACM Capacity Level as specified for the Control Center in the active SLM Policy.
None: Indicates that there are no constraints at present.
type: Is the Type.
AgeLmt: Indicates that the current SLM job selection point is higher than the aging limit specified for the Service Group in the active SLM Policy.
Jobs: Indicates that the JESplex member has reached the maximum number of executing jobs for the Service Group or Type as specified in the active SLM Policy.
name: Is the JESplex member name.
color: The current SLM color for this JESplex member, indicating how well the member is running this particular type of workload. Color ranges from green (running well) to red (experiencing problems).
CPU: Indicates that the JESplex member has reached the maximum CPU workload for the Service Group or Type specified in the active SLM Policy.
SelPt: Indicates that work for the Service Group will not be selected on the JESplex member because the current SLM selection point is lower than that specified for the Service Group in the active SLM Policy.
ACMJobs : Reached maximum number of executing jobs on this JESplex member for the current ACM Capacity Level as specified for the Service Group in the active SLM Policy.
None: Indicates that there are no constraints at present.
This message is issued in response to the SLM DISPLAY SG command.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8221I

No active SLM Policy
Explanation: There is no active SLM Policy therefore the current command cannot be completed.

System action: The command is ignored.

Operator response: Notify personnel responsible for support.

Programmer Response: Implement and activate an SLM Policy.

DTM8222I

Member name is not defined to SLM
Explanation: The member name specified on a SLM D JPX command is not defined in the active SLM Policy.

System action: The command is ignored.

Operator response: Re-enter the command with a valid JESplex member name.

Programmer Response: None.

DTM8223I

ccenter type is not a valid Service Group name
Explanation: The Service Group name specified on an SLM D SG command is not defined in the active SLM Policy.

System action: The command is ignored.

Operator response: Re-enter the command with a valid Service Group name.

Programmer Response: None.

DTM8224I

Invalid member name
Explanation: A JESplex member name of greater than 4 characters was supplied on a SLM D JPX command.

System action: The command is ignored.

Operator response: Re-enter the command with a valid JESplex member name.

Programmer Response: None.

DTM8225I

Invalid Service Group name
Explanation: A Service Group name with either or both the CONTROL CENTER and TYPE missing, or with either or both longer than 8 characters, was specified on a SLM D SG command.

System action: The command is ignored.

Operator response: Re-enter the command with a valid Service Group name.

Programmer Response: None.

DTM8226I

Jjobnumber is not managed by SLM
or
Job jobname is not managed by SLM
or
SLM Job Display
text


Explanation: This message is the response to the SLM DISPLAY JOB jobnumber/’jobname’ command.
text: This message can have several formats, depending on the Workload Type.

For General Services:

SLM Job Display
Jjobnumber jobname jobstatus
Time System Reason job was not selected
time system reason
Workload Type : General Services
Control Center:
Type :
Batch Service :
Trend :
Service Mode :
Job Service :
Estimated Time to Selection:
Effective Queue Time :
Total Delay Time :
Currently Delayed By :

For Production Control Services (PCS):

SLM Job Display
jobnumber jobname jobstatus
Workload Type : Production Control Services
Job Scheduler :
PCS Group Name :
Production Importance :
Due out time :
Expected elapsed time :
Slack time :
Total Delay Time :
Currently Delayed By : For a job that has completed execution, sections of the Job Summary report associated with the job are presented. For information on the contents of the Job Summary report, refer to the ThruPut Manager AE Usage Guide.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8227I

Invalid service class name
Explanation: Service Class name supplied on the SLM D SC command is greater than 8 characters.

System action: The command is ignored.

Operator response: Re-enter the command with a valid Service Class name.

Programmer Response: None.

DTM8228I

No SLM multiplex data available
Explanation: The SLM D MULTIPLEX command has been issued and no Multiplex information is available for any LPAR Set. The most likely reason for this message is that no Multiplex LPAR Sets have been defined in the active SLM Policy.

System action: The command is ignored.

Operator response: If unexpected, inform the person at your installation responsible for Thruput Manager.

Programmer Response: Check LPAR Set definitions in the active SLM Policy.

DTM8230I

PCS Information
CA 7 Instance : cainstance
Automation Dataset(AMD): amdfilename
Battle Plan Dataset: bpfile
Experience Dataset: expfile1
Experience (Alternate): expfile2
Collection (Experience): expcollect
Battle Plan is currently Active
Explanation:
cainstance: The CA7 instance associated with the current PCS.
amdfilename: The name of the Automation File.
bpfile: The name of the Battle Plan File.
expfile1, expfile2: The names of the Experience Files.
expcollect: The name of Experience Collection File
This message is the response to PCS D INFO command and provides the information about current PCS Region.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8231E

JOBnnnnn FORCE only valid after first attempting command without FORCE
Explanation: The SLM START command was issued for the specified job with the FORCE keyword without first attempting the command without FORCE.

System action: The request is ignored.

Operator response: Re-enter the command without the FORCE keyword.

Programmer Response: None.

DTM8232I

SLM Display QBYCLASS

Count     Jobclass

n             class

No SLM managed jobs awaiting execution.

No SLM managed GS|PS jobs awaiting execution.


Explanation: This message is issued in response to the “SLM Display QBYCLASS” command. In the message text;

  • n is the number of jobs that would have been assigned to that JES2 jobclass.
  • class is the JES2 joblcass that would have been assigned to the job had it not been managed by SLM.

The second and third forms of the message are generated when there are no SLM managed jobs of the selected type(s) awaiting execution.

System action: None             

Operator response: None

Programmer Response: None

DTM8233I

SLM Service Class Display
nnnnnnnn c PI:pppp Dly:dddf ADly:eee U:uuu
ACPU:aaaa AS:sss.s P:x
Dist: xxxxx xxxxx xxxxx xxxxx


Explanation:
nnnnnnnn: Is the Service class name.

x: Is the number of periods defined for Service Class.

pppp: Is one of the following:

• Most recent Performance Index as calculated by SLM
• N/A if none available (no active jobs).

ddd: Is one of the following

• Most recent Delay percentage as calculated by SLM
• N/A if none available (no active jobs)

f: Is the indicator appended to the delay percentage following the % sign. It can be one of the following

• Value is “u” if the delay is determined by SLM to be unusual in nature.
• Value is “i” if the delay is determined by SLM to be unusual and there are very few jobs running in the Service Class and therefore the delay is ignored in SLM calculations related to the Service Class.
• Value is blank in all other cases.

eee: Most recent Adjusted Delay percentage as calculated by SLM or "N/A" if none available (no active jobs). If specified in the active SLM Policy, SLM adjusts the Total Delay percentage to take into account the effect of the time that the LPAR is queued to be dispatched on a physical processor.

uuu: Most recent WLM Unknown Delay percentage as calculated by SLM  or "N/A" if none available (no active jobs).

aaaa: Is the available CPU as percentage at the importance level of the Service Class as calculated by SLM.

c: Is the single letter indicated the SLM Color assigned to the Service Class based on current performance. Green indicates the best performance, Red the worst performance.

• Green
• Blue
• Yellow
• Orange
• Red

xxxx: This information is only present for multi-period Service Classes. It shows the percentage workload distribution as calculated by SLM for each period. A maximum of four period distributions are calculated and displayed.

sss.s: Is the average number of address spaces in the last 10 second analysis interval as reported by WLM.

This message is issued in response to a SLM D SC operator command. Lines repeat for each Service Class displayed.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8234I

nnnnnnnn is not a defined GS/PCS service class
Explanation:
nnnnnnnn: Is the Service Class name.
Service Class name supplied on the SLM D SC command has not been defined in the active SLM Policy as a service class for use by General Services or Production Control Services.

System action: The command is terminated.

Operator response: None.

Programmer Response: None.

DTM8235I

No active service classes
Explanation: User has issued a SLM D SC command requesting information on active service classes only (the default). None of the service classes defined in the active SLM Policy for use by General Services or Production Control Services currently have active jobs on the system on which the command was issued.

System action: The command is terminated.

Operator response: None.

Programmer Response: None.

DTM8240I

xxx Invalid application name
Explanation: The TM ABANDON command was issued and one of the application IDs in the abandon list was invalid. Valid application names are: ALL, DBS, DCS, DJC, JBS, JCS, JLS, JSS, JTS, MHS, SLM.
xxx: text that indicates an invalid application name.

System action: The command is ignored.

Operator response: Re-enter the command with the correct name(s).

Programmer Response: None.

DTM8241I

JOBnnnnn is not managed by any applicable applications
Explanation: The TM ABANDON command was issued using an abandon list of (ALL) but the specified job was not managed by any of the following applications: DBS, DCS, DJC, JBS, JCS, JLS, J SS, JTS, MHS.

System action: The command is ignored.

Operator response: Use the JOB command to determine why the job is not running.

Programmer Response: None.

DTM8245I

SLM will manage DCS Service. Overrides will be ignored


Explanation: This message is the response to the SLM SET DCS command. The SLM SET DCS command has been issued and the option to allow DCS/SLM to control service class was used – DCS(SLM_DEFAULTS).

System action: None.

Operator response: None.

Programmer Response: None.

DTM8246I

SLM will allow DCS JAL/JECL overrides to be used
Explanation: This message is the response to the SLM SET DCS command. The SLM SET DCS command has been issued and the option to allow JAL/JECL overrides was chosen – DCS(JECL_JAL_OVERRIDES).

System action: None.

Operator response: None.

Programmer Response: None.

DTM8248E

SLM SET default override command failed, JES2 is not responding. Retry command later.
Explanation: An SLM SET command has been used to specify default override indicator Y/N. JES2 has not responded for 30 seconds so the request is aborted.

System action: The SLM SET command is not executed.

Operator response: Investigate why JES2 is unresponsive, once JES2 appears to be responding, try the SLM SET command again.

Programmer Response: None.

DTM8251I

Battle Plan for Production Cycle cycle-name is being Activated. Incomplete Job Trees from the old BP will be dropped if:
(N) they already have been carried forward tt times
(T) more than hh hours elapsed since the initial Job completion time
Explanation: When during Activation of a new BP some Job Trees from the old BP are going to be dropped the DTM8260I message is going to be issued for each such a Job Tree. The DTM8251I message is issued once per a group of the DTM8260I messages, before the first one. It displays the Battle Plan Activation parameters that will be used to decide whether an Incomplete Job Tree from the old BP is going to be carried forward to the new BP or to be dropped. Since either both parameters or only one of them can be specified, it is possible that the message contains only (N) or only (T) condition.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8252I

Starter Job detection is NOT performed.
or
Starter Job detection is done Automatically.
or
Starter Job detection is done Manually.
Explanation: This message is issued when Scheduled Job method of building Job Trees is used. It indicates how the Starter Job detection was performed:
• ‘NOT performed’ – means that the option is turned off;
• ‘done Automatically’ – means that all Scheduled NON-EXECutable jobs are considered to be Starter Jobs;
• ‘done Manually’ – means that the Starter Job List is used to determine what jobs are Starter jobs. The list is maintained manually by user.
The message is not issued using WTO. It goes to the Battle Plan log only and can be viewed using PCS Dialog.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8253I

Battle Plan for Production Cycle cccccccc has been closed due to Activation of a new Battle Plan using incompatible Job Tree building method.
Explanation: When one Battle Plan was built using the Application method for building Job Trees and another one was built using the Scheduled Job method they cannot be Activated one after another. Instead, the currently Active BP has to be closed first and then the second BP can be activated. When Auto-activation is performed and PCS detected that the currently active BP and the one being activated are not compatible, it closes the currently Active BP automatically before Activating the new one. When it happens it issues the message to the operator’s console.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8254I

Job Trees are created using Scheduled Job Method.
or
Job Trees are created using Application Method.
Explanation: This message informs which method of building Job Trees (Scheduled Job or Application) was used during building of the Battle Plan.
The message is not issued using WTO. It goes to the Battle Plan log and can be viewed using PCS Dialog.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8255I

Battle Plan Creation Failed due to lack of available
data collected from CA 7. Will continue to RETRY until hh:mm
Explanation: Indicates that there is not enough CA 7 data to Auto-create or re-create a Battle Plan. This is most likely due to the fact that the PCS Data Collection utility has not been run for a long period of time. Regular attempts will be made to determine if the data became available and if yes, to create and activate a new Battle Plan Automatically. The attempts will be made up to the time indicated in the message. No further messages will be issues until either a successful Activation of the new Battle Plan or until the attempt period expires.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8256I

PCS Data Collection Utility Ended. Return Code: nnn
Explanation:
nnn: A return code.
This message indicates a data collection error. The PCS Data Collection Utility ended with a non-zero return code.

System action: None.

Operator response: None.

Programmer Response: Check JOBLOG/SYSMSGS for error messages.

DTM8257I

Battle Plan Creation Failed. PCS Data Collection Utility is currently running. Will continue to RETRY until hh:mm
Explanation: Indicates that the AMD data set that you are processing is currently being updated by the “Data Collection” utility.
Regular attempts will be made to determine if the utility completed and if yes, to create and activate a new Battle Plan Automatically. The attempts will be made up to the time indicated in the message. No futher messages will be issues until either a successful activation of the new Battle Plan or until the attempt period expires.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8258I

AMD dataset datasetname is almost full. One BP was deleted to free some space
Explanation: This message informs that the Active AMD data set has lack of free space and PCS deleted one of the Battle Plans located in the AMD to free some space.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8259I

AMD dataset datasetname is almost full. nnn BPs were deleted to free some space.
Explanation:
nnn: The number of deleted Battle Plans.
This message informs that the Active AMD data set has lack of free space and PCS deleted the specified number of Battle Plans located in the AMD to free some space.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8260I

Job Tree xxxxxxxxx_xxx scheduled for date time will be dropped when the new BP is activated (reason(s)).
Explanation:
xxxxxxxxx_xxx: The Job Tree name.
date: The scheduled date.
time: The scheduled time.
reason(s): There are two possible reasons:
• (N) – The incomplete Job Tree has already been carried forward the maximum allowed number of times.
• (T) – The incomplete Job Tree Life Span has been exceeded.
This message informs that the Job Tree is not going to be carried forward to the new Battle Plan being activated for reason(s) indicated in the parenthesis.
The maximum values that are currently in effect are displayed in the corresponding message DTM8251I which precedes the group of DTM8260I messages.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8268I

The Job Tree xxxxxxxxx_xxx expected ending time (eeeeee)
extends beyond { Appl. | BP } Production Cycle (cccccc).
Explanation:
xxxxxxxxx_xxx: The Job Tree name.
eeeeee: The ending time.
cccccc: The Cycle time.
A Job Tree extends beyond the Cycle boundary and needs a specific Acceptable time to be entered. The message specifies whether Application (Appl.) or Battle Plan (Battle Plan) Cycle is involved.

System action: None.

Operator response: Edit the Battle Plan and enter the appropriate Acceptable time for the Job Tree in question.

Programmer Response: None.

DTM8269I

Battle Plan for Production Cycle cycle-name starting on date at time Created Successfully.
Explanation:
cycle-name: The Production Cycle name.
date: The starting date.
time: The starting time.
This message indicates that the Battle Plan for the specified Production Cycle has been created successfully.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8270I

Battle Plan for Production Cycle cycle-name missed Automatic Activation due to lack of available data collected from CA 7.
Explanation:
cycle-name: The Production Cycle name.
This message indicates that a

PCS XTASK Table has been REFRESHED and is ACTIVE.


Explanation: This message is displayed in response to the
PCS XTASK REFRESH
command when PCS XTASK table has been refreshed and is currently in the active state.

PCS XTASK Table contains information from the CA 7 External Task filter. It is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

Battle Plan was expected to be activated automatically at certain time but there was not enough data to build the Battle Plan.

System action: None.

Operator response: Run PCS Data Collection utility which collects CA 7 data. After successfully running the utility you will be able to create the Battle Plan and activate it manually.

Programmer Response: None.

DTM8271I

Battle Plan for Production Cycle cycle-name was Closed by userid.
Explanation:
cycle-name: The Production Cycle name.
userid: The user id.

This message indicates that the Battle Plan for the specified Production Cycle was closed by user.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8272I

Battle Plan for Production Cycle cycle-name is Complete and has been Closed.
Explanation:
cycle-name: The Production Cycle name.
This message indicates that the Battle Plan for the specified Production Cycle has been closed automatically.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8273I

Battle Plan for Production Cycle cycle-name started on date at time Activated by userid.
Explanation:
cycle-name: The Production Cycle name.
date: The starting date.
time: The starting time.
userid: The user id.
This message indicates that the Battle Plan for the specified Production Cycle has been activated by the specified user.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8274I

Battle Plan for Production Cycle cycle-name starting on date at time Activated Automatically.
Explanation:
cycle-name: The Production Cycle name.
date: The starting date.
time: The starting time.

This message indicates that the Battle Plan for the specified Production Cycle has been activated automatically.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8291I

Battle Plan for Production Cycle has been Closed due to a long inactivity period.
Explanation:
cycle-name: The Production Cycle name.
The last activity event recorded in the Battle Plan File happened long time ago thus the reconciliation is not possible and the Battle Plan is Closed. This situation could occur if PCS was restarted after it had been
DOWN for more than a threshold period.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8294I

The PCS Experience File is Ready for Access
dsname: filename
Explanation:
filename: PCS Job Experience File name.
The PCS Job Experience file has been successfully opened by the PCS Region and is available for information requests.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8295E

PCS Experience File: reason
dsname: filename
Explanation:
filename: PCS Job Experience File name.
reason: Here is the list of possible reasons:
• Error return from IDENTIFY(xx)
• Error return from ACCESS(xx)
•Data set Size too small
• Error return from CREATE(xx)
• Error return from MAP(xx)
• File format error
• Error return from DYNALLOC(xx)

PCS has not been able to successfully access the PCS JOB EXPERIENCE FILE. The Job Experience File is a VSAM linear data set and several components might fail when allocating and initiating access to the file using IBM Data-in-Virtual operations.

System action: PCS will not be able to function until the problem is fixed. DTM0190I message will be issued if the error is caused during data set allocation.

Operator response: None.

Programmer Response: Try to solve the issue with the Job Experience File. If it is a simple matter such as the data set name is not spelled correctly then fix the problem by altering the name in PCS Initialization Statements. Ensure that the Job Experience File was allocated and initialized as outlined in documentation. Contact support if there does not appear to be a resolution.

DTM8296I

PCS Experience File Last Updated mmm dd,yyyy
DSNAME: dsname
or
PCS Experience File(1) Currently Contains No Data
DSNAME: dsname1
PCS Experience File(2) Last Updated mmm dd,yyyy
DSNAME: dsname2
The PCS REGION WILL USE EXPERIENCE FILE,
DSNAME: dsname2
Explanation: This message is produced during TM initialization for the PCS region. It is an informative message that describes the PCS EXPERIENCE file that is in use. If two EXPERIENCE files were specified in TM PARMS then the one with the most recently updated data will be chosen and the message will reflect this.

System action: The PCS region will use the EXPERIENCE file named in the message.

Operator response: None.

Programmer Response: None.

DTM8298I

Battle Plan for Production Cycle cycle missed Automatic Activation because the Battle Plan could not be made ready for activation by the expected time.
Explanation: Informs that a Battle Plan was expected to be activated automatically at certain time but something prevented it to be ready for this activation.

System action: None.

Operator response: This condition should be reported to MVS Solutions support. Obtaining the trace is highly recommended. As a work-around solution the manual activation of the BP is recommended.

Programmer Response: None.

DTM8299I

Fatal error on SLM request. Command terminated. Error: cccccccc
Explanation:
cccccccc: Is the error code received.
As part of command processing, the command sent a request to SLM. This request failed with a fatal error. As a result the processing of the command was terminated.

System action: The command is terminated.

Operator response: Notify the person responsible for support.

Programmer Response: Report this problem to BMC Support.

DTM8300I

DATA COLLECTION SUBTASK INITIALIZED
Explanation: The SLM data collection task has started normally.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8302E

DTMPRX17 Fatal Error (error)
Explanation: DTMPRX17 encountered an unrecoverable error and cannot function properly.
error: gives specific details regarding the error.

System action: None.

Operator response: None

Programmer Response: None.

DTM8303E

SLM COLLECTION : percentage PERCENT USED SINCE THE LAST DATA EXTRACTION
Explanation: This message describes in percentage how much of the SLM Collection File has been written since data were last extracted. Values for percentage are 80, 90, and 100.

System action: At the 80% and 90% levels, data collection continues. At 100%, data collection continues but the oldest unextracted data is overwritten.

Operator response: Dependent on installation procedures. A data extraction task might need to be started.

Programmer Response: None.

DTM8304E

SLM COLLECTION: FILE HAS WRAPPED SINCE LAST DATA EXTRACTION DATA COULD BE LOST
Explanation: The SLM Collection File has wrapped around but no data have been extracted.

System action: Data collection continues but the oldest unextracted data is overwritten.

Operator response: Dependent on installation procedures. A data extraction task might need to be started.

Programmer Response: Review procedures. To avoid this situation, implement an automated extraction task at the 80% or 90% warning.

DTM8403I

No Active Battle Plan for CA7n
Explanation: PCS for the specified instance of CA 7 does not have an active Battle Plan.

System action: The message is issued every 15 minutes or until a Battle Plan is activated.

Operator response: None.

Programmer Response: Activate a Battle Plan.

DTM8404I

Max. # of Adhoc Jobs reached
Explanation: The number of Adhoc Jobs that were either Completed or Canceled during the current Active Battle Plan lifetime reached the maximum. No more Completed or Cancelled Adhoc job information will be recorded in the Battle Plan.

System action: For an Active Battle Plan the message is issued only once.

Operator response: None.

Programmer Response: None.

DTM8406E

CA 7 LRLOG command failed during reconciliation.
Some jobs could be lost or could have incorrect status.
Original CA 7 error message is:
original CA 7error message
Explanation: The reason for this message is an error during execution of the CA 7 LRLOG command. The message indicates that this command failed with the CA 7 error message
PCS reconciliation is a process of synchronizing internal PCS job data with the job data known to a CA 7 instance. It is used either during Activation of a new Battle Plan or during PCS restart.
What makes this synchronization possible is a number of CA 7 commands issued by PCS to collect various data. One of these commands is LRLOG.

System action: PCS continues execution, however, job status for some job(s) can be incorrect. The impact is usually minimal in the case of Activation of a new Battle Plan. If TMPCS was restarted the incorrect status could affect hundreds of jobs.

Operator response: None.

Programmer Response: Contact MVS Solutions Support.

DTM8407E

AMD Data Set is being either reinitialized or
re-linked to a different CA 7 / Job Database name.
AMD Data Set: dataset-name
Explanation: An involved procedure being performed on the AMD data set is not over yet.
PCS Dialog either performs Re-initialization or replaces CA 7 identity stored in the AMD data set (CA 7 Instance name and/or CA 7 Job Database name).
No other component can use the data set until the operation completes.

System action: Control Region starting task terminates.

Operator response: Check with the user of the PCS Dialog what changes to the AMD data set were performed. If the data set has been re-initialized, the Control Region needs to be restarted with the BPF=COLD option. New Production Cycles, Battle Plans and Defaults/Options have to be created in the re-initialized AMD data set before it can be used. If CA 7 Identity was replaced in the AMD data set, the Control Region starting task can be started again.

Programmer Response: None.

DTM8409E

AMD Data Set referenced from the Active BP has
invalid format: dataset-name.
Explanation: PCS data in the specified AMD data set either do not exist or are corrupted. It is not possible to use this AMD data set.

System action: Control Region starting task terminates.

Operator response: It is possible that the AMD data set was renamed or deleted and some other data set was given the same name. It is also possible that the AMD data set was corrupted by another job. Investigate and, if necessary, restore the data set from the most recent backup. You can also start the Control Region starting task with the Battle Plan File parameter set to COLD and use another AMD data set.

Programmer Response: None.

DTM8410E

Error occurred during an attempt to read the AMD Data Set referenced from the Active BP: dataset-name.
Explanation: An error occurred during an attempt to read PCS Data from the specified AMD data set.

System action: Control Region starting task terminates.

Operator response: It is possible that the AMD data set was renamed or deleted and some other data set was given the same name. It is also possible that the AMD data set was corrupted by another job.
Investigate and, if necessary, restore the data set from the most recent backup. You can also start the Control Region starting task with the Battle Plan File parameter set to COLD and use another AMD data set.

Programmer Response: None.

DTM8411E

AMD Data Set referenced from the Active BP File is intended to be used with CA 7 Instance / Database which is different from the one(s) the Control Region is working with.
Control Region communicates with instname1 using t1:
database_name1
AMD Data Set is intended to be used with instname2
using t2:
database-name2
Explanation:
instname1, instname2: CA 7 Instance names.
t1, t2: It can be either ‘Scheduler Job Data Set’ or ‘CA 7 Logical Database’.
database-name1, database-name2: Corresponding database names.
When an AMD data set is initialized for working with a specific CA 7 Instance, this CA 7 Instance identity is saved in the AMD.
The identity consists of CA 7 Instance Name, Type of the database it is using and the database name.During the Control region WARM start, the identity of the CA Instance the Control Region is communicating with and the identity saved in the AMD data set are compared to make sure that the correct AMD data set is used with the correct CA 7 instance.
If the identity data do not match this error message is issued and the Control Region wouldn’t be initialized.

System action: Control Region starting task terminates.

Operator response: There are several possibilities.
The most likely ones are:
1. You converted your CA 7 Job database from Release 11 to 12 and as a result the database name has changed.
2. You renamed a VSAM file (CA 7 Release 11) or changed the logical Database name (Release 12).

If either 1 or 2 is correct, run the PCS Dialog, specify the CA 7 Instance name and the AMD data set name and select ‘Adjust AMD data set accordingly’ option on the “CA 7 Job Database Name Mismatch” panel. The Dialog will replace the CA 7 identity saved in the AMD data set with the correct one.
ALWAYS make sure that you are working with the correct AMD data set!

Programmer Response: None.

DTM8412E

AMD Data Set referenced from the Active BP is busy: dataset-name.
Explanation: During an attempt to Read from or Write to the AMD data set it was detected that some Active I/O operations performed by another PCS component are still in progress. After several such attempts the same condition persists.

System action: Control Region starting task terminates.

Operator response: Try to start the Control Region again.

Programmer Response: Usually, the I/O competition between different PCS components does not present a problem as a sophisticated algorithm is used to resolve all such collisions. Report this message to support along with SYSLOG entries for investigation.

DTM8413W

Cannot find valid version identification in user exit ___
Explanation: SASSVRSN is not found within 1st 256 bytes of installation exit routine.
The installation uses an exit point that is also used by Set TMPCS. For coexistence the installation must call their exit SASSX$nn. With CA 7 r12 the installation exit must have a current SASSVRSN macro assembled into the 1st 256 bytes of its exit. The exit routine must be re-assembled with each new release of CA 7 so that the exit release number matches the CA 7 release. This message is issued when no valid version information is found within the 1st 256 bytes of the exit routine.

System action: Calls to the installation exit are disabled.

Operator response: None.

Programmer Response: Re-assemble the installation exit with the appropriate SASSVRSN macro.

DTM8414W

Incorrect version identification found in user exit ___
Explanation: The installation uses an exit point that is also used by Set TMPCS. For coexistence the installation must call their exit SASSX$nn. With CA 7 r12 the installation exit must have a current SASSVRSN macro assembled into the 1st 256 bytes of their exit. The exit routine must be re-assembled with each new release of CA 7 so that the exit release number matches the CA 7 release. This message is issued when valid version information is found within the 1st 256 bytes of the exit routine but it is not for this version of CA 7.

System action: Calls to the installation exit are disabled.

Operator response: None.

Programmer Response: Re-assemble the installation exit with the appropriate SASSVRSN macro.

DTM8415W

Lack of Resolved data in the WTL might impact precision of the Battle Plan predictions.
Explanation: When a Battle Plan gets created it uses data collected by the PCS Data Collection utility and saved in the WTL section of the AMD data set. The collected data is later used by either PCS Dialog or PCS Control Region to build a new Battle Plan. The amount of data collected by the utility depends on the run-time parameters.

When a Battle Plan is being created PCS might use not only the data covering this Battle Plan's active time period but also the data covering the time period of the NEXT Battle Plan. This message indicates that it was not enough data to fully cover the NEXT Battle Plan jobs. Although it is not a critical situation, but using the NEXT Battle Plan job data is highly recommended.

System action: None.

Operator response: None.

Programmer Response: Review the parameters passed to the DTM4CST7 load module in the PCS Data Collection job. Consider to increase the value of the DAYS= parameter.

DTM8416W

Job Instance XXXXXXXXXXXX is on Demand Job List but Application YYYYYYYY is neither Managed nor Monitored.
Explanation: When a Battle Plan gets created it creates both "regular" PCS Job Instances that are expected to run during this Battle Plan active time period as well as Demand Jobs that are possibly could run in this Battle Plan. These Demand Jobs are controlled by a Demand Job List. The message is issued because of the contradiction: a Job was specified in the Demand Job List (and as such should be included in the Battle Plan) but it belongs to an Application that is neither Managed nor Monitored (which means PCS should ignore it).

System action: None.

Operator response: None.

Programmer Response: Either remove the Job Instance from the Demand Job List or change the Managed / Monitored status of the appropriate Application.

DTM8417I

PCS is running in the Managing/Monitoring mode.
Explanation: This message indicates that PCS will manage CA 7 jobs that belong to the Managed Applications and will monitor CA 7 Jobs that belong to the Monitored Applications. This is the normal running mode for PCS.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8418I

PCS is running in the Monitoring Only mode.
Explanation: This message indicates that PCS will monitor both CA 7 jobs that belong to the Managed and Monitored Applications. No CA 7 jobs will be managed. This is not a normal running mode for PCS. It is usually used when an attempt to use the regular Managing/Monitoring mode was not successful due to incorrectly set Defaults/Options.

System action: None.

Operator response: None.

Programmer Response: Remember to return PCS in the Managed/Monitored mode when the problem is resolved.

DTM8419I

PCS Monitoring Mode has been changed by TSO User XXXXX.
Explanation: This message indicates that PCS Monitoring Mode has been changed due to a request sent from the PCS Dialog. The Dialog is an ISPF application running under TSO User id specified in the message. This message is followed by either DTM8420I or DTM8421I.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8420I

PCS is now running in the Managing/Monitoring mode.
Number of Managed BP jobs remaining being Monitored: nnnnnn
Number of Managed Adhoc jobs remaining being Monitored: mmmmmm
Explanation: This message indicates that PCS switched to the Managing / Monitoring mode where it is going to manage the CA 7 jobs that belong to the Managed Applications and to monitor the CA 7 Jobs that belong to the Monitored Applications. This is the normal running mode for PCS. Due to the fact, that some CA 7 jobs might have been already submitted while PCS was in the Monitoring Only mode, these jobs will remain being monitored only. The number of such jobs at the moment of processing the switching request is displayed in the message. The Battle Plan jobs and the Adhoc jobs are counted separately.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8421I

PCS is now running in the Monitoring Only mode.
Number of BP jobs remaining being Managed: nnnnnn
Number of Adhoc jobs remaining being Managed: mmmmmm
Explanation: This message indicates that PCS will switch to the Monitoring Only mode where it will monitor both jobs that belong to the Managed Applications and jobs that belong to the Monitored Applications. No jobs are supposed to be managed in this mode. Due to the fact, that some CA 7 jobs might have been already submitted while PCS was in the Managing/Monitoring mode, these jobs will remain being managed. The number of such jobs at the moment of processing the switching request is displayed in the message. The Battle Plan jobs and the Adhoc jobs are counted separately.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8422I

PCS Monitoring Mode has been changed by operator command
Explanation: This message indicates that PCS Monitoring Mode has been changed due to a request sent using an operator command.
This message is followed by either DTM8420I or DTM8421I.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8423E

PCS Control Region cannot create a Battle Plan due to version mismatch. Upgrade PCS Data Collection Utility and re-run it for CA 7 Instance CA73, AMD data set:
XXXXXXXX.XXXXXXXX.XXXXXXXX.XXXXXXXX.XXXXXXXX
Explanation: Working Time Line data collected by the PCS Data Collection utility is used during creation of a new Battle Plan. It was detected that the version of the data is not compatible with the version of the PCS Control region code. The data needs to be re-collected by a newer version of the PCS Data Collection Utility.

System action: A new Battle Plan wil not be created.

Operator response: None.

Programmer Response: If the error occurred after upgrading TM to a higher version than one of the following occurred:
• PCS Data Collection utility was not upgraded properly (possibly the Data Collection job has a STEPLIB DD pointing to the wrong load library where the old version of the Data Collection utility is located);
• PCS Data Collection utility was upgraded correctly but did not have a chance to collect CA 7 data yet (run the utility and make sure that it did not report any errors)

DTM8424E

PCS Control Region cannot create a Battle Plan due to version mismatch. Upgrade PCS Control Region and restart it.
Explanation: Working Time Line data collected by the PCS Data Collection utility are used during creation of a new Battle Plan. It was detected that the version of the data is not compatible with the version of the PCS Control region code. PCS Control Region needs to be upgraded to a newer version to be able to handle the Working Time Line data.

System action: A new Battle Plan won't be created.

Operator response: None.

Programmer Response: If the error occurred after upgrading TM to a higher version then, most likely, PCS Control region was not upgraded properly. Check the Control region starting procedure for a STEPLIB DD pointing to the wrong load library where the old version of the Control region code is located).

DTM8425E

PCS XTASK command failed. Ref.code is XXXX
Explanation: This message is displayed in response to the PCS XTASK command (with any additional operands) in the event of an unexpected communication error. The specific error type depends on the displayed code that can have one of the following values:
0008 - Communication buffer was detected to be too small.
0012 - Incompatible version of data layout.
0016 - Wrong response type received for the request.
0020 - Unexpected number of response records.
0024 - FSBR Code is not zero.

System action: Operator's command is ignored.

Operator response: Report this incident to support.

Programmer Response: None.

DTM8426I

PCS XTASK Table is ACTIVE.
Explanation: This message is displayed in response to the
PCS XTASK
or
PCS XTASK DISPLAY
command when PCS XTASK table is in the active state.
PCS XTASK Table contains information from the CA 7 External Task filter. It is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8427I

PCS XTASK Table is NOT in the active state.
Reason: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Explanation: This message is displayed in response to the
PCS XTASK
or
PCS XTASK DISPLAY
command when PCS XTASK table is NOT in the active state.
The message also indicates the exact reason:
No CA 7 External Task filter
the CA 7 External Task filter is not defined.
No CA 7 Subsystem
CA 7 seems not to be installed on this system.
No CA 7 Instance
CA 7 Instance was not defined properly.
Unexpected Data Encountered
the CA 7 External Task filter was found but it contains inconsistent data.
Unexpected Error Occurred
Unexpected error occurred during attempt to locate the CA 7 External Task filter.
CA 7 Ext.Task Filter is too LARGE
the CA 7 External Task filter was found but its size is greater than the allowed maximum.
PCS Table was DISABLED by operator
PCS XTASK Table was disabled by the command:
PCS XTASK DISABLE
PCS XTASK Table contains information from the CA 7 External Task filter. It is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8428I

PCS XTASK Table has been REFRESHED and is ACTIVE.
Explanation: This message is displayed in response to the
PCS XTASK REFRESH
command when PCS XTASK table has been refreshed and is currently in the active state.

PCS XTASK Table contains information from the CA 7 External Task filter. It is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8429I

PCS XTASK Table has been REFRESHED but is NOT active.
Reason: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
Explanation:
This message is displayed in response to the
PCS XTASK REFRESH
command when PCS XTASK table has been refreshed but it is NOT in the active state.
The message also indicates the exact reason:

No CA 7 External Task Filter
the CA 7 External Task filter is not defined.
No CA 7 Subsystem
CA 7 seems not to be installed on this system.
No CA 7 Instance
CA 7 Instance was not defined properly.
Unexpected Data Encountered
the CA 7 External Task filter was found but it contains inconsistent data.
Unexpected Error Occurred
Unexpected error occurred during attempt to locate the CA 7 External Task filter.
CA 7 Ext.Task Filter is too LARGE
the CA 7 External Task filter was found but its size is greater than the allowed maximum.
PCS Table was DISABLED by operator
PCS XTASK Table was disabled by the command:
PCS XTASK DISABLE

PCS XTASK Table contains information from the CA 7 External Task filter. It is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8430I

PCS XTASK Table is DISABLED, has to be ENABLED first.
Explanation: This message is displayed in response to the
PCS XTASK REFRESH
command when PCS XTASK Table cannot be refreshed due to the fact that it previously was disabled. Instead of using PCS XTASK REFRESH, an operator has to use PCS XTASK ENABLE.

PCS XTASK Table contains information from the CA 7 External Task filter. It is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: Issue the PCS XTASK ENABLE command.

Programmer Response: None.

DTM8431I

Active PCS XTASK Table is now DISABLED.
Explanation: This message is displayed in response to the
PCS XTASK DISABLE
command when PCS XTASK table has been successfully disabled. Disabled PCS XTASK Table cannot be used to recognize any External Task jobs.

PCS XTASK Table contains information from the CA 7 External Task filter. It is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8432I

PCS XTASK Table is NOT active and cannot be disabled.
Explanation: This message is displayed in response to the
PCS XTASK DISABLE
command when PCS XTASK table cannot be disabled due to the fact that it is not active. Only active PCS XTASK Table can be disabled.
PCS XTASK Table contains information from the CA 7 External Task filter. It is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8433I

PCS XTASK Table has been already DISABLED.
Explanation: This message is displayed in response to the
PCS XTASK DISABLE
command when PCS XTASK table is already in the DISABLED state.
PCS XTASK Table contains information from the CA 7 External Task filter. It is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8434I

Disabled PCS XTASK Table was ENABLED and is now Active.
Explanation: This message is displayed in response to the
PCS XTASK ENABLE
command when PCS XTASK table has been successfully enabled and now is Active. Active PCS XTASK Table can be used to recognize External Task jobs.
PCS XTASK Table contains information from the CA 7 External Task filter. It is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8435I

PCS XTASK Table is NOT in the disabled state.
Explanation: This message is displayed in response to the
PCS XTASK ENABLE
command when PCS XTASK table cannot be enabled due to the fact that the table is currently is NOT in the disabled state.
PCS XTASK Table contains information from the CA 7 External Task filter. It is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8436I

Disabled PCS XTASK Table was ENABLED but remains NOT Active.
Reason: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
Explanation: This message is displayed in response to the
PCS XTASK ENABLE
command when the disabled state of the PCS XTASK Table was cleared but an attempt to activate the table was not successful. The message also indicates the exact reason:
No CA 7 External Task Filter
the CA 7 External Task filter is not defined.
No CA 7 Subsystem
CA 7 seems not to be installed on this system.
No CA 7 Instance
CA 7 Instance was not defined properly.
Unexpected Data Encountered
the CA 7 External Task filter was found but it contains inconsistent data.
Unexpected Error Occurred
Unexpected error occurred during attempt to locate the CA 7 External Task filter.
CA 7 Ext.Task Filter is too LARGE
the CA 7 External Task filter was found but its size is greater than the allowed maximum.
PCS XTASK Table contains information from the CA 7 External Task filter. It is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8437I

PCS XTASK Table is ACTIVE.
It contains the following job name patterns:
XXXXXXXX XXXXXXXX XXXXXXXX 


    • . . .
      XXXXXXXX XXXXXXXX XXXXXXXX
      Explanation: This message is displayed in response to the
      PCS XTASK DISPLAY DETAILS
      command when PCS XTASK Table is in the active state and is not empty. It lists all job name patterns the table contains.
      PCS XTASK Table is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8438I

PCS XTASK Table is ACTIVE but contains no job name patterns.
Explanation: This message is displayed in response to the
PCS XTASK DISPLAY DETAILS
command when PCS XTASK Table is active but contains no job name patterns.
PCS XTASK Table is used to properly handle the jobs controlled by CA 7 External Task Tracking.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8500I

SLM has resumed control of jjjjjjjj. Service class: ssssssss
Explanation:
jjjjjjjj: Job name or JES2 job id (‘J’ or ‘JOB’ followed by the job number).
ssssssss: Service class name assigned by SLM.
This message is the response to a SLM RESUME JOB command. It shows that SLM has successfully resumed control of the service class assignment for the indicated job.

System action: The command has completed successfully.

Operator response: None.

Programmer Response: None.

DTM8501I

jjjjjjjj not executing
Explanation:
jjjjjjjj: Job name or JES2 job id (‘J’ or ‘JOB’ followed by the job number).
This message is the response to a SLM RESUME JOB command. User has issued the command for a job that is not executing. SLM RESUME JOB only applies to executing jobs.

System action: The command is terminated.

Operator response: Ensure the correct job name or job number was specified on the SLM RESUME JOB command.

Programmer Response: None

DTM8502I

Service class for jjjjjjjj already controlled by SLM
Explanation:
jjjjjjjj: Job name or JES2 job id (‘J’ or ‘JOB’ followed by the job number).
This message is the response to a SLM RESUME JOB command. SLM already controls service class assignment for that job, so the SLM RESUME JOB command is unnecessary.

System action: The command is terminated.

Operator response: Ensure the correct job name or job number was specified on the SLM RESUME JOB command.

Programmer Response: None.

DTM8503I

WLM returned error resetting service class. RC=retcode Reason=rsncode
Explanation:
retcode: Return code from WLM.
rsncode: Reason code from WLM.

This message is the response to a SLM RESUME JOB command. WLM returned an error when SLM attempted to change the service class for the job.

System action: The command is terminated.

Operator response: Notify the persons responsible for support.

Programmer Response: Obtain system log showing the command and message and forward to support.

DTM8504I

More than one job named jjjjjjjj is executing - use job number
Explanation:
jjjjjjjj: Job name.
This message is the response to a SLM RESUME JOB command. More than one SLM managed job with the supplied job name is executing in the JESplex.

System action: The command is terminated.

Operator response: Reissue the SLM RESUME JOB command with the job number of the specific job.

Programmer Response: None.

DTM8505I

CPC not found in JESplex. Type:tttt Serial:ss-sssss
Explanation:
tttt: is the 4 digit IBM type of the CPC.
ss-ssss: is the serial number of CPC.
The indicated CPC could not be detected by SLM in the JESplex.
The indicated CPC is defined in the SLM policy being loaded, validated or activated and SLM cannot find it in the JESplex. This can be due to the following:
1. The type and/or serial number have been specified incorrectly.
2. There is no member of the JESplex active on that CPC at the present time.
3. SLM is not active on any member of the JESplex on that CPC at the present time.
4. Thruput Manager on the members of the JESplex on that CPC is at a level lower than version 7.1 PTF TMT7104.

System action: Policy validation/activation continues with a warning.

Operator response: Inform the person(s) in your installation responsible for support.

Programmer Response: Check to see which of the reasons listed above apply and correct if necessary. Contact support if none appear to apply.

DTM8506I

LPAR nnnnnnnn not found for CPC tttt ss-sssss
Explanation:
nnnnnnnn: is the LPAR name.
tttt: is the 4 digit IBM type of the CPC.
ss-ssss: is the serial number of CPC.
The indicated LPAR could not found by SLM on the indicated CPC.
The indicated LPAR is defined in the SLM policy being validated, activated or loaded as being on the indicated CPC. SLM has no record of it being on that CPC. This can be due to the following:
1. The LPAR name is incorrect.
2. The LPAR is not a z/OS LPAR.
3. There is no active SLM policy.
Note that when there is no active SLM policy, SLM does not have full information on the z/OS eligible LPARs on the CPCs in the JESplex. In this case, verify that the indicated LPAR name and CPC type and serial number are correct. If correct, then once the SLM policy is activated, SLM will use the LPAR definition and therefore no further action is required.

System action: The loading, validation or activation of the SLM Policy continues with a warning. The LPAR definition is ignored unless this is due to validation being performed when there is no active SLM policy.

Operator response: Inform the person(s) in your installation responsible for support.

Programmer Response: Check to see which of the reasons listed above apply and correct if necessary. Contact support if none appear to apply.

DTM8507I

LPAR Set nnnnnnnn has LPAR names that cannot be validated
Explanation: nnnnnnnn: is the LPAR set name.
The indicated LPAR Set has been defined with one or more LPAR names that cannot be validated as existing and z/OS eligible by SLM.
The indicated LPAR Set is defined in the SLM policy being validated, activated or loaded with one or more LPARs that cannot be validated by SLM as either existing or z/OS eligible.
There will be one or more DTM8506I messages issued for any LPARs that cannot be validated.

System action: The loading, validation or activation of the SLM Policy continues with a warning. The LPAR Set will still be considered valid providing it contains at least one valid LPAR.

Operator response: Inform the person(s) in your installation responsible for support.

Programmer Response: Look for DTM8506I messages and correct the definitions for the indicated LPARs.

DTM8508I

SLM CPC Status
nnnnnnnn Type: tttt Serial: vv-vvvvv
LPARS
llllllll 4h Avg: aaaa.aa Intvl: iiii.ii
LPAR Sets
ssssssss k 4h Avg: aaaa.aa Intvl: iiii.ii Lmt: mmmm
Explanation:
nnnnnnnn: The text ‘CPC’ or the name of the CPC as configured in the active SLM Policy.
tttt: 4 digit IBM CPC type.
vv-vvvvv: CPC serial number.
llllllll: LPAR name defined in the active SLM Policy.
Note: there is one line per LPAR.
ssssssss: LPAR Set name defined in the active SLM Policy.
Note: there is one line per LPAR Set for the CPC on which the command is entered.
k: Set to either ‘*’ or blank. ‘*’ indicates that this usage in this particular LPAR Set was used by ACM to determine the current Capacity Level.
aaaa.aa: 4-hour average usage in MSU/hr for the LPAR or LPAR Set.
iiii.ii: Usage in last 5 minute interval in MSU/hr for the LPAR or LPAR Set.
mmmm: Limit for LPAR Set in MSU/hr. If followed by an asterisk (*), the limit is an override value substituted due to inconsistencies in the Multiplex limit as specified in the SLM Policies in different JESplexes. The limit from the most recently updated policy is used.
Response to command SLM DISPLAY CPC.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8509I

SLM FALLBACK ignored - another is active in JESplex
Explanation: SLM FALLBACK command is ignored as another SLM FALLBACK is already executing in the JESplex.

System action: SLM FALLBACK command is ignored.

Operator response: It is only necessary to issue the SLM FALLBACK command on one member of the JESplex.

Programmer Response: None.

DTM8510I

SLM FALLBACK ENQ serialization failed. RC=retcode RS=reason
retcode: Return code.
reason: Reason code
Explanation: SLM FALLBACK serialization request was failed by z/OS.

System action: SLM FALLBACK command is ignored.

Operator response: Inform person responsible for Thruput Manager at your installation.

Programmer Response: Contact support.

DTM8511I

memname IS NO LONGER AT FULL CAPACITY
Explanation: memname: JESplex member name.
The indicated JESplex member is no longer at full capacity.
The rolling 4-hour average for the indicated JESplex member no longer exceeds any Defined Capacity limit or if a member of an LPAR Group, the LPAR Group no longer is over its limit.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8512I

PCS Service Classes required for PCS Groups
Explanation: The SLM Policy being validated has PCS Groups defined but no PCS Service Classes configured.
This condition is determined during SLM policy validation as a result of either a validation or activation request from the SLM command or the SLM Definition Services dialog.

System action: The error message will be issued on the console or displayed by the SLM Definition Services dialog. The validation or activation request fails with an error.

Operator response: Notify the person responsible for support.

Programmer Response: None.

DTM8513I

jobname (jobid) Quick Job: criteria
jobname: Job name of the PCS job.
jobid: JES2 job id of the PCS Job.
criteria: One of the following:

Elapsed (esttime, timelmt)
CPU (estcpu, cpulmt)
Elapsed (esttime, timelmt) CPU(estcpu, cpulmt)

where:
esttime: Estimated elapsed time for the job.
timelmt: Quick Job limit for estimated time from active SLM Policy.
estcpu: Estimated CPU Service Units for the job.
cpulmt: Quick Job limit for CPU Service Units from active SLM Policy.
Explanation: This informational message is issued when SLM first recognizes a PCS job and determines that it is to be treated as a Quick Job.
The indicated PCS job has been determined by SLM to be a Quick Job based on the estimated elapsed time and/or CPU service units provided by PCS and the limits set in the active SLM Policy.

System action: This message is written to the SYSLOG only.

Operator response: None.

Programmer Response: None.

DTM8514I

DTM8514I SLM Multiplex ACM Status
nnnnnnnn ------------- Avg: hhhh Int: iiii Lmt: llll
cpc-name tttt vv-vvvvv Avg: hhhh Int: iiii
sysplexn jesplexn Avg: hhhh Int: iiii ACM
Avg: hhhh Int: iiii Update
s Avg: hhhh Int: iiii ACM
s Avg: hhhh Int: iiii Update
Cksm: kkkkkkkk LPARs: pp Lmt: qqqq
Explanation: Response to SLM DISPLAY MULTIPLEX command.
nnnnnnnn: Multiplex LPAR Set name
hhhh: 4-hour rolling average usage in MSU/hr
iiii: Usage in the last 5 minute interval in MSU/hr
llll: Multiplex limit for the LPAR Set
cpc-name: The text 'CPC' or the name of the CPC as configured in the active SLM Policy
tttt: The 4 digit IBM CPC type
vv-vvvvv: The serial number of the CPC
sysplexn: Sysplex name
jesplexn: JESplex name
kkkkkkkk: Checksum of the LPAR names in the Multiplex LPAR Set as defined on the indicated Sysplex/JESplex and CPC
pp: Number of LPARs as defined for the Multiplex LPAR Set on the indicated Sysplex/JESplex and CPC
qqqq: Limit for Multiplex LPAR Set as defined on the indicated Sysplex/JESplex and CPC
s: Set to 'M' to indicate the average and interval usage numbers are for work classified by WLM as MOBILE.
Set to 'A' to indicate the average and interval usage numbers are for work classified by WLM as CATEGORYA.
Set to 'T' to indicate the average and interval usage numbers are for work classified by WLM as belonging to Tenant Resource Groups
Lines are only present if there is usage and the SLM Policy specifies that mobile and/or category A load should be discounted.

Lines/groups repeat for each sysplex/JESplex, CPC and Multiplex LPAR Set.
There are normally 2 lines for every sysplex/JESplex. The first displays the statistics at the time the last ACM calculation cycle was run on the member where the command was issued ('ACM') and the second displays the most up to date usage statistics ('Update'). If the LONG parameter has been specified on the command, there is a third line that displays the checksum of the LPAR names, number of LPARs defined, and the defined limit for the LPAR Set.

If the SHORT parameter has been supplied, no Sysplex/JESplex detail is present.
If the SETS parameter has been supplied, only the line for each LPAR Set is displayed.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8515I

ACM has removed CPC tttt vv-vvvvv from Multiplex information
Explanation:
tttt: 4 digit IBM CPC type
vv-vvvv: CPC serial number
No updates have been received from the CPC for at least 4 hours. ACM assumes that the CPC may have been either taken out of service or upgraded, and therefore has deleted references to that CPC from the multiplex information kept by ACM. Should the CPC come back online and provide updates, the CPC and any appropriate sysplex/JESplex information for one or more LPAR Sets will be added back to the multiplex information kept by ACM.

System action: The multiplex information regarding Multiplex LPAR Set usage on the indicated CPC has been removed.

Operator response: If unexpected, notify the person at your installation responsible for support.

Programmer Response: Verify that the CPC was offline/down for 4 hours or more.

DTM8516I

LPAR Set nnnnnnnn has inconsistent Multiplex definitions
Explanation: The indicated LPAR Set has been defined in the SLM policy for two or more CPCs and is not consistently defined as a Multiplex LPAR Set and/or has inconsistent values specified for the Multiplex limit.

nnnnnnnnn: LPAR Set name
While a Multiplex LPAR Set only needs to be defined on those CPCs on which it applies, where it is defined it must be defined as a Multiplex LPAR Set and have the same Multiplex limit.
There will be one DTM8516I message issued for each incorrectly defined Multiplex LPAR Set.

System action: The loading, validation or activation of the SLM Policy is terminated.

Operator response: Notify the person responsible for Thruput Manager at your installation.

Programmer Response: Correct the definition of the indicated Multiplex LPAR Set in the SLM Policy.

DTM8517E

Inconsistent LPARs for LPAR Set nnnnnnnn on CPC tttt ss-sssss
Explanation: The indicated LPAR Set has inconsistent LPAR members defined for the indicated CPC in the SLM Policies for the JESplexes in the multiplex.

nnnnnnnn: LPAR Set name

tttt: 4 digit IBM CPC type

ss-sssss: CPC serial number

ACM has detected than an LPAR Set has not been defined consistently in the multiplex. This may be due to a user error when defining one or more SLM Policies. The specific error is that the list of LPAR names belonging to the LPAR Set on the indicated CPC differs between one or more SLM Policies.
It may also occur when an intentional change has been made to the definition in one JESplex but the corresponding changes on other JESplexes have not been made.
When definitions are inconsistent, ACM uses the results of calculations using the most recently updated policy This allows SLM Policy changes to be made at a reasonable rate. They do not have to be made simultaneously.
While the inconsistency exists, this message will be issued every 15 minutes on all systems in the multiplex that have the same Multiplex LPAR Set defined in the SLM Policy and are on the indicated CPC.

System action: ACM calculations continue.

Operator response: Notify the person responsible for Thruput Manager at your installation.

Programmer Response: Correct the definitions for the indicated LPAR Set on all applicable JESplexes.

DTM8518E

Inconsistent Multiplex Limits for LPAR Set nnnnnnnn
Explanation: The indicated LPAR Set has inconsistent Multiplex limit values defined in the SLM Policies for the JESplexes in the multiplex.

nnnnnnnn: LPAR Set name

ACM has detected than an LPAR Set has not been defined consistently in the multiplex. This may be due to a user error when defining one or more SLM Policies. The specific error is that the Multiplex limit specified for the LPAR Set differs between one or more SLM Policies.
It may also occur when an intentional change has been made to the definition in one JESplex but the corresponding changes on other JESplexes have not been made.
When definitions are inconsistent, ACM uses the limit specified in the most recently updated policy. This allows SLM Policy changes to be made at a reasonable rate. They do not have to be made simultaneously.
While the inconsistency exists, this message will be issued every 15 minutes on all systems in the multiplex that have the same Multiplex LPAR Set defined in the SLM Policy.

System action: ACM calculations continue using the Multiplex limit from the most recently updated SLM Policy.

Operator response: Notify the person responsible for Thruput Manager at your installation.

Programmer Response: Correct the definitions for the indicated LPAR Set on all applicable JESplexes.

DTM8519I

ACM removed JESplex sysplexn jesplexn LPAR Set lpsetnam CPC tttt ss-sssss from multiplex
Explanation: The indicated JESplex entry for the named LPAR Set and CPC has been removed from the multiplex information kept by Automated Capacity Management (ACM).

sysplexn: Sysplex name

jesplexn: JESplex name

lpsetnam: LPAR Set name

tttt: 4 digit IBM CPC type

ss-sssss: CPC serial number

On the system where the message is issued, ACM has detected that the indicated LPAR Set is no longer defined as a Multiplex LPAR Set or at all for the indicated CPC in the active SLM policy for the indicated JESplex or the JESplex has not provided an update in at least 4 hours.
ACM has automatically removed the corresponding entry from the multiplex information kept by ACM on the system where the message is issued and it will no longer be used in calculations.

System action: The usage information for the LPAR Set for the CPC and JESplex has been removed from the multiplex information kept by ACM on the system where this message is issued so that it will no longer be used in ACM calculations.

Operator response: Inform the person responsible for Thruput Manager at your installation.

Programmer Response: Verify that the SLM Policy change was made. Notify BMC Customer Support if otherwise.

DTM8521I

SLM Multiplex Nodes
sysplexn jesplexn Update: uuuu Server: ssss
Last update: yyyy.ddd hh:mm:ss
memberlist
Explanation: Response to SLM D MULTIPLEX NODES command. Shows information about connections to other JESplexes in the multiplex.

sysplexn Sysplex name

jesplexn JESplex name

uuuu Name of JESplex member to which the current system is connected in order to send multiplex information updates
ssss Member name of SLM server. Note: this is not displayed for JESplexes outside of the Sysplex on which the command was issued.
yyyy.ddd hh:mm:ss Date and time that the last update was received from the indicated Sysplex/JESplex
memberlist List of members recognized for the indicated Sysplex/JESplex. Only displayed if the LONG parameter is supplied on the command. If a member does not support Multiplex LPAR Sets outside of the Sysplex, an asterisk follows the member name. NOTE: not all members may be present in the list as it is only necessary for a member to have a TCPIP connection to one member in a remote JESplex.
Line/groups repeat for each Sysplex/JESplex which is currently connected to the system on which the command was issued. This can be further controlled by the REMOTE and LOCAL parameters.

System action: None

Operator response: None

Programmer Response: None

DTM8522I

No remote JESplexes are currently connected
Explanation: Response to SLM D MULTIPLEX NODES REMOTE command when currently there are no remote JESplexes connected.

System action: The command is terminated.

Operator response: None

Programmer Response: None

DTM8523I

Invalid or missing LPAR Set name
Explanation: Response to SLM D MULTIPLEX SET command. The required LPAR Set name is either invalid or was not entered.

System action: The command is terminated.

Operator response: Reenter the command with a valid LPAR Set name.

Programmer Response: None

DTM8524E

ACM on mmmm has no outbound connection to sysplexn jesplexn
Explanation: ACM is receiving messages from the indicated remote JESplex. Since the remote JESplex is clearly active, ACM expects to be able to connect with that JESplex but is unable to do so.

mmmm JESplex member name where the message was issued

sysplexn Sysplex name of the remote JESplex

jesplexn JESplex name of the remote JESplex

System action: None. Processing continues although the remote JESplex may be missing ACM related information from the JESplex where the message was issued. This may lead to incomplete rolling 4-hour average totals for one or more CPCs.

Operator response: Notify the personnel responsible for support in your installation.

Programmer Response: Check that the TM TCPIP statements in the Thruput Manager parameters are correct for the indicated JESplex and that no communications errors or component failures have occurred.

DTM8525E

CPC not defined in SLM Policy: tttt ss-sssss
Explanation: Multiplex LPAR Sets have been defined but the local CPC has not been defined in the active SLM Policy. This probably indicates an oversight or entry error, possibly after a processor upgrade.

tttt 4 digit IBM CPC type

ss-sssss CPC serial number

System action: None. Processing continues.

Operator response: Notify the personnel responsible for support in your installation.

Programmer Response: Determine if this is an error and/or oversight. If so, copy the active SLM Policy, update an existing CPC definition or define the CPC, its LPARs and any required LPAR Sets. Activate the new policy.

DTM8526I

SLM event – Sysplex: sysplexn JESplex: jesplexn Member: mmmm


Explanation: SLM has been notified that an outbound connection to the indicated remote JESplex member has been established or disconnected.

event the text “connected” or “disconnected”

sysplexn remote sysplex name

jesplexn remote JESplex name

mmmm remote JESplex member name

System action: None. Processing continues

Operator response: None

Programmer Response: None

DTM8527I

jobname (jobid) Service Class reset mapped from oldname to newname
Explanation: SLM has been notified that the Service Class for the indicated executing job has been reset by operator command or another software component such as a job scheduling package. As per the current active SLM Policy, the Service Class reset has been mapped to the indicated Service Class.

jobname jobname of the job being reset

jobid JES2 jobid of the job being reset

oldname Service class name on the reset

newname Name of the service class that has now been assigned to the job as a result of the mapping.

System action: None. Processing continues.

Operator response: None

Programmer Response: None

DTM8528I

Invalid period number specified for monitored service class sclsname
Explanation: In the SLM Policy currently being validated, the indicated Service Class is specified to be monitored by Online Performance Protection. The period number specified in the policy exceeds the number defined for the Service Class in the active WLM Policy.
sclsname Service class name

System action: If the current action is policy validation or activation, the action fails. If the current action is a policy load at SLM initialization or after the activation of a WLM Policy, the load continues with a warning.

Operator response: Notify the person responsible for support.

Programmer Response: Activate a valid SLM Policy that corrects the period number for the Service Class.

DTM8529I

Online Performance Protection constraints active
Explanation: Online Performance Protection (OPP) has been configured in the active SLM Policy and the configured constraints have been activated due to the current performance of one or more of the monitored service classes.
This condition is determined during SLM performance analysis which is executed every 10 seconds.

The calculated performance index (PI) of a least one of the monitored Service Classes specified in the active SLM Policy, has reached the High PI threshold set in the policy and therefore any specified constraints actions have begun.

System action: The OPP constraints specified in the active SLM Policy have been activated

Operator response: None.

Programmer Response: None.

DTM8530I

Online Performance Protection constraints ended
Explanation: Online Performance Protection (OPP) has been configured in the active SLM Policy and the configured constraints have been deactivated due to the current performance of one or more of the monitored service classes.
This condition is determined during SLM performance analysis which is executed every 10 seconds.

The calculated performance index (PI) of the monitored Service Classes specified in the active SLM Policy, that previously reached the High PI threshold set in the policy, are now at or below the low PI value, and therefore any specified constraints actions have ended.

System action: The OPP constraints specified in the active SLM Policy have been ended.

Operator response: None.

Programmer Response: None.

DTM8531I

OPP Status
Constraints: constraints
Updated: updatetime
Changed: changetime
Disabled: disabled

Monitored Service Classes
sclsname PI:pp.p High PI:qq.q at hightime extended
Explanation: Response to SLM DISPLAY OPP (SLM D OPP) command

constraints: "Active" or "Inactive"“
updatetime: Date and time of last analysis
changetime: Date and time OPP constraints started or ended
disabled: "All", "General Services" or "Production Services" Indicates if operator has disabled OPP for all or a subset of SLM workload using the "SLM OPP" command. This line is only present if operator disable is active.
sclsname: Service Class name
pp.p: Most recent PI calculated for Service Class
qq.q: Most recent PI value that was greater than or equal to the "High PI" value for the Service Class. Only displayed if constraints are currently active due to this Service Class.
hightime: Most recent date and time the PI was greater than or equal to the "High PI" value for the Service Class. Only displayed if constraints are current active due to this Service Class.
extended: "Extended" or blank. Indicates if OPP constraints have been extended as a result of the minimum duration for constraints set in the active SLM Policy.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8532I

Online Performance Protection is not configured
Explanation: Response to SLM DISPLAY OPP (SLM D OPP) and SLM OPP commands. Online Performance Protection has not been enabled in the active SLM Policy.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8533I

OPP constraints disabled by operator: dddddddd
Explanation: Response to SLM OPP command. Shows the state of operator overrides of Online Performance Protection after the command has executed.
dddddddd: One of the following: "None", "All", "General Services" or "Production Services"

System action: None.

Operator response: None.

Programmer Response: None.

DTM8534E

Corrupt policy. Active Performance Focus name invalid or not defined.
Explanation: The focus definition designated as active in the SLM policy is not defined in the policy. It is likely that data in the SLM policy has been corrupted.

System action: The policy fails validation with a severe error. If this occurs during a policy activation or load, that operation is terminated.

Operator response: Inform the person responsible for Thruput Manager at your installation.

Programmer Response: Open a Thruput Manager case with Customer Support.

DTM8535I

Policy load changed Active Performance Focus to focname
Explanation: Load of an SLM policy activated the Performance Focus Definition configured in that policy as active. That Focus Definition has a different name than the one that was previously active. This is intended to alert the operator particularly in the case that previously the active focus had been altered by operator command.

focname: Name of the new active Performance Focus Definition

System action: None. Policy load continues.

Operator response: None.

Programmer Response: None.

DTM8536I

Focus name not defined in active SLM Policy
Explanation: The Performance Focus name specified on a SLM ACTIVATE FOCUS command is not defined in the currently active SLM Policy.

System action: The command is terminated with no action.

Operator response: Correct the focus name and reissue the command.

Programmer Response: None.

DTM8537I

Performance Focus focname activated

Service Mode switch from old-mode to new-mode


Explanation: In response to a SLM ACTIVATE FOCUS command, the Active Performance Focus has been set to the indicated name.  If the option to switch Service Mode is enabled, the Service Mode has also been changed as indicated.

focname: Name of the active Performance Focus Definition

old-mode: Name of the previous Service Mode

new-mode: Name of the new Service Mode name

System action: The SLM ACTIVATE FOCUS command completes normally.

Operator response: None.

Programmer Response: None.

DTM8538I

Active Performance Focus is focname
Explanation: A Performance Focus Definition has been activated as a result of either a new policy load or activation, or the SLM ACTIVATE FOCUS command. The message is issued on each member of the JESplex as the change is recognized.

focname: Name of the active Performance Focus DefinitionSystem action: None.

Operator response: None.

Programmer Response: None.

DTM8539I

Not all SLM instances in JESplex support Performance Focus


Explanation: Issued in response to an SLM ACTIVATE FOCUS command when SLM detects that not all the members of the JESplex are running a level of Thruput Manager that supports SLM Performance Focus Definitions.

To avoid inconsistent SLM performance parameters in a JESplex, all members of the JESplex must support SLM Performance Focus Definitions in order to allow the operator to switch definitions.

System action: The SLM ACTIVATE FOCUS command is rejected.

Operator response: Inform the person responsible for Thruput Manager at your installation.

Programmer Response: Upgrade all instances of Thruput Manager in the JESplex to a level that supports SLM Performance Focus Definitions.

DTM8540I

SLM CPU MF monitoring active


Explanation: SLM is using HIS to obtain various CPU MF hardware performance metrics.

System action: None.

Operator response: None.

Programmer Response: None.

DTM8541I

SLM CPU MF initialization failure. Reason=rsncode


Explanation: SLM has been unable to initialize and use the interface for obtaining CPU MF metrics.

rsncode: Reason code

System action: SLM monitoring of CPU MF is terminated. All other SLM functions will continue to operate normally.

Operator response: Inform the person responsible for Thruput Manager at your installation.

Programmer Response: Open a Thruput Manager case with Customer Support. Report the message and the reason code.

DTM8542I

SLM CPU MF subtask terminated: compcode


Explanation: 
Explanation: The SLM CPU MF subtask that manages the interface to HIS has abended with the indicated completion code.

compcode: Completion code in the form Snnn or Unnnn

System action: SLM will attempt to reinitialize the subtask. If three successive failures occur within a minute of each other, SLM will stop attempting recovery and CPU MF monitoring will be left inactive.

Operator response: Inform the person responsible for Thruput Manager at your installation.

Programmer Response: Open a Thruput Manager case with Customer Support. Provide details of the failure, the system log and any system dump that was taken.

DTM8543I

SLM CPU MF subtask timed out


Explanation: The SLM CPU MF subtask did not initialize or respond to a sampling request within a reasonable time.

System action: If initialization has timed out, no retry is attempted and SLM CPU MF monitoring is terminated.

If the time out occurred while processing a sampling request, the subtask will be terminated and SLM will then attempt to reinitialize the subtask unless there have been three failures within one minute of each other, in which case no retry will be attempted.

Operator response: Inform the person responsible for Thruput Manager at your installation.

Programmer Response: Open a Thruput Manager case with Customer Support.

DTM8544I

SLM CPU MF monitoring not available


Explanation: Due to initialization failure or excessive failures of the SLM CPU MF subtask, SLM CPU MF monitoring is not being performed and will not be reattempted until SLM or ThruPut Manager  is recycled or the LPAR is reIPLed.

System action: No CPU MF metrics will be monitored. All other SLM functions will continue to operate normally.

Operator response: Inform the person responsible for Thruput Manager at your installation.

Programmer Response: If messages DTM8546I or DTM8547I are also issued, then either HIS is not started or the LPAR is not configured adequately for SLM CPU MF monitoring. Consider starting HIS or reconfiguring the LPAR to meet the SLM requirements. If neither of those messages have been issued, open a Thruput Manager case with Customer Support.

DTM8545I

SLM CPU MF calculation error. RC=retcode Reason=rsncode
Explanation: SLM has encountered an error while calculating CPU MF related metrics.
retcode: Return code
rsncode: Reason code

System action: SLM CPU MF monitoring is discontinued. All other SLM functions will continue to operate normally.

Operator response: Inform the person responsible for Thruput Manager at your installation.

Programmer Response: Open a Thruput Manager case with Customer Support. Include the return code and reason code in your report.

DTM8546I

HIS started task not active
Explanation: SLM CPU MF has attempted to connect to HIS but the HIS started task is not active.

System action: SLM CPU MF monitoring is not available. All other SLM functions will continue to operate normally.

Operator response: Inform the person responsible for Thruput Manager at your installation.

Programmer Response: Start HIS at IPL.

DTM8547I

LPAR not configured to collect required data
Explanation: SLM CPU MF has determined that the LPAR is not configured to access all the data required for its calculations.

System action: SLM CPU MF monitoring is not available. All other SLM functions will continue to operate normally.

Operator response: Inform the person responsible for Thruput Manager at your installation.

Programmer Response: Configure the LPAR using the HMC/Support Element to have access to the Basic, Extended and Program counter sets.

DTM8548I

CPC not supported by SLM CPU MF Monitoring


Explanation: SLM does not support the CPC type for CPU MF metrics.
Calculations of CPU MF metrics vary by CPC type. Currently SLM CPU MF supports the following CPC types: EC12, z13, z14, z15.

System action: SLM CPU MF monitoring is not available. All other SLM functions will continue to operate normally.

Operator response: Inform the person responsible for Thruput Manager at your installation.

Programmer Response: Open a Thruput Manager case with Customer Support.

DTM8549I

SLM CPU MF monitoring suspended


Explanation: SLM has detected that HIS is down and has suspended CPU MF monitoring.

System action: No SLM CPU MF monitoring will be performed. All other SLM functions will continue to operate normally.

Operator response: Restart HIS or inform the person responsible for Thruput Manager at your installation.

Programmer Response: Restart HIS. SLM CPU MF monitoring will resume automatically after HIS has initialized.

DTM8550I

SLM CPU MF monitoring resumed


Explanation: SLM CPU MF monitoring has resumed after being suspended due to HIS being unavailable. SLM has detected that HIS has been restarted.

System action: SLM CPU MF monitoring is active.

Operator response: None.

Programmer Response: None.

DTM8551I

jobid jobname is late and has been accelerated
Explanation: SLM has detected that based on data provided by the Job Scheduler that submitted the job, the job is now considered to be late.  To speed up the job, it has been assigned the service class that is associated with the next more important Production Importance than the one for the job.

jobid:  JES2 job id of affected job

jobname:  Job name of affected job

System action: The service class of the job is changed.

Operator response: None.

Programmer Response: None.

DTM8552I

jobid jobname not accelerated due to configuration


Explanation: SLM has detected that based on data provided by the Job Scheduler that submitted the job, the job is now considered to be late.  However, the service class assigned in the SLM Policy to the next more important Production Importance is the same as the one already assigned to the job. 

jobid:  JES2 job id of affected job

jobname: Job name of affected job

System action: None

Operator response: None.

Programmer Response: None.

DTM8553I

Performance Focus switched Service Mode from old-mode to new-mode


Explanation:

old-mode:  Name of previous Service Mode

new-mode: Name of new Service Mode

An SLM ACTIVATE FOCUS command activated a Performance Focus Definition that is defined as being associated with a different Service Mode than that was previously active and the option to change mode when focus changes is enabled.

System action: The new Service Mode is activated.

Operator response: None

Programmer Response: None

DTM8556I

SLM Display IBYCLASS

Inits           Jobclass

n                class

No JES2 initiators started.  


Explanation: This message is issued in response to the “SLM Display IBYCLASS” command. In the message text;

  • n is the number of JES2 initiators that have been assigned the displayed jobclass.
  • class is the associated JES2 joblcass.

The second form of the message is generated when there are no started JES2 initiators to analyze.

System action: None             

Operator response: None

Programmer Response: None

DTM8554I

Service Mode change rejected – use Performance Focus


Explanation:

The command to activate/deactivate Service Mode has been rejected.  The option to automatically set the Service Mode when activating a Performance Focus Definition is enabled.  Service Mode can only be changed by activating a Performance Focus Definition.

System action:  The command is rejected.

Operator response:  Use Performance Focus Definition changes as per your installation standards.

Programmer Response:  None

DTM8555I

Use original service class QAFF option ignored.


Explanation:

During policy validation or activation, SLM has determined that the SLM policy AE Migration Option to use the current JES2 QAFF as set by the $TSRVCLASS command for the original service class for the job has been enabled by the installation.  However, no WLM batch service classes of which JES2 is currently aware have been marked “PERMANENT” using the JES2 command $TSRVCLASS.

Since JES2 only allows QAFF to be set for permanent service classes, SLM ignores the AE Migration Option and issues this warning message.

System action:  Policy validation or activation continues.

Operator response:  Notify the person responsible for support.

Programmer Response:  Disable the specific AE Migration Option if not needed.             

DTM8596I

SLM request had XCF error. Feedback=nnnn


Explanation:
nnnn: Thruput Manager XCF feedback code.
An SLM request issued as a result of an operator command has encountered an error in transmission between JESplex members.

System action: The command is terminated.

Operator response: Notify the persons responsible for support.

Programmer Response: Obtain system log showing the command and message and obtain a SLM trace for the system on which the error occurred. Contact support.

DTM8597I

SLM request had unexpected error. RC=retcode Reason=rsncode


Explanation: retcode: Return code.rsncode: Reason code. This message indicates that an SLM request issued as a result of an operator command has encountered an unexpected error.

System action: The command is terminated.

Operator response: Notify the persons responsible for support.

Programmer Response: Obtain system log showing the command and message and obtain SLM trace for the system on which the error occurred. Contact support.

DTM8598I

No active WLM policy.
Explanation: An SLM operator command was issued that requires that there be an active WLM policy, but there is no active WLM policy in the SYSPLEX.

System action: The command is terminated.

Operator response: Notify the persons responsible for support.

Programmer Response: Ensure there is an active WLM policy in the SYSPLEX.

DTM8599I

SLM function ‘name’ not available on all JESplex members
Explanation:
‘name’: the name of the SLM command function.
This message indicates that the SLM function is not supported JESplex wide. The specified function of the SLM operator command requires that it must be supported on all JESplex members in order to be accepted on any member.

System action: The command is terminated.

Operator response: Notify the persons responsible for support.

Programmer Response: This indicates that Thruput Manager is at different release or PTF levels in the JESplex. When Thruput Manager is upgraded on all members, the indicated function of the SLM operator command will be available.

DTM8601E

DTMGUTP7 (XXXXXXXX): No 2-nd CSRT table
Explanation: IBM .provided CSRT tables for a number of services including XML parsing. The required table was not found. No secondary CSRT table found. XXXXXXXX is a TCB address of the HCI subtask issued this message.

System action: The request is terminated.

Operator response: Notify the persons responsible for support.

Programmer Response: None.

DTM8602E

DTMGUTP7 (XXXXXXXX): OBTAIN TMPSTOR FAILED: YYYYYYYY/ZZZZZZZZ
Explanation: DTMGUTP7 obtains some persistent storage when it is called for the first time in each subtask. This message indicates that an attempt to obtain this storage using the STORAGE macro failed.

XXXXXXXX is a TCB address of the HCI subtask issued this message.
YYYYYYYY is a hexadecimal representation of the size of the storage that was attempted to be obtained.
ZZZZZZZZ is a return code from the STORAGE macro.

System action: The request is terminated.

Operator response: None.

Programmer Response: Check that the HCI address space has enough available 31-bit storage.

DTM8603E

DTMGUTP7 ABEND TCCC,PSW=XXXXXXXXXXXXXXXX:

ENTRY POINT ADDRESS: YYYYYYYY
GR00-03 ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
GR04-07 ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
GR08-11 ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
GR12-15 ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
Explanation: An abend occurred during execution of the DTMGUTP code or the code called from DTMGUTP. Abend details are specified in the message. Dump is suppressed.
To obtain a dump use the operator SLIP command.

T: Abend type: S - system, U - user
CCC: Abend code (hexadecimal)
XXXXXXXXXXXXXXXX: is PSW at the time of abend
YYYYYYYY: is an address of the entry point in the DTMGUTP7 load module (DTMGUTP CSECT)
ZZZZZZZZ: General register contents

System action: The request is terminated.

Operator response: Notify the persons responsible for support.

Programmer Response: None.

DTM8604E

DTMGUTP7 (XXXXXXXX) GXL1YYY RC=ZZZZZZZZ
Explanation: A call to the IBM XML parsing service failed.
XXXXXXXX is a TCB address of the HCI subtask issued this message.
YYY is a postfix identifying which IBM service was called.
ZZZZZZZZ is a return code from the service.

System action: The request is terminated.

Operator response: Notify the persons responsible for support.

Programmer Response: None.

DTM8800E

Incompatible z/OS version

At least z/OS 2.3 is required to run TM/BCPii subtask


Explanation: This message is issued by the TM/BCPii subtask during its initialization. The subtask requires at least z/OS Version 2.3. Initialization fails.

System action: TM/BCPii subtask functionality is disabled on this LPAR.

Operator response: None.

Programmer Response: Make sure that TM LPAR weight configuration does not allow control functions to be performed on this LPAR.

DTM8801E

TM A/S is NOT authorized to use BCPii API        

Ensure that TM A/S has at least READ access to the security    

product profile:                       

HWI.APPLNAME.HWISERV

in the FACILITY class.
Explanation: This message is issued by TM/BCPii subtask during its initialization. The subtask requires access to BCPii API to function properly. Access to this API must be authorized in the Security Product (for example, RACF) by allowing at least READ access in the profile.

HWI.APPLNAME.HWISERV

which is part of the FACILITY class. TM/BCPii subtask functionality is disabled on this LPAR.

Operator response: None.

Programmer Response: Make sure that the TM starting task has proper authorization to access BCPii API. After the problem is resolved, recycle SLM to reinitialize the TM/BCPii subtask.

DTM8802E

TM A/S cannot load BCPii API load modules. Check that the HWICSS load module (SYS1.CSSLIB) is available in the TM starting task
Explanation: This message is issued by the TM/BCPii subtask during its initialization. The TM/BCPii subtask was unable to load the BCPii API load modules. TM/BCPii subtask functionality is disabled on this LPAR.

Operator response: None.

Programmer Response: Make sure that SYS1.CSSLIB contains load module HWICSS and the library is available to the TM starting task (either as part of LINKLIST or as specified in the starting task's STEPLIB).
After the problem is resolved, recycle SLM to reinitialize the TM/BCPii subtask.

DTM8803E

BCPii Address Space is DOWN. It must be started for TM/BCPii subtask to run:


    • S HWISTART


Explanation: This message is issued by the TM/BCPii subtask during its initialization. The subtask requires that the BCPii address space is running. TM/BCPii waits until the BCPii address space is started by the following command.

S HWISTART

Operator response: None.

Programmer Response: Make sure that BCPii is properly configured and start BCPii A/S. After the problem is resolved, recycle SLM to reinitialize the TM/BCPii subtask.

DTM8804E

TM/BCPii sub-task terminated due to an unexpected error encountered during initialization


Explanation: This message is issued by the TM/BCPii subtask during its initialization. TM/BCPii subtask detected an unexpected error and shut down. 

Operator response: Report this message to BMC Support.

Programmer Response: The TM/BCPii starting task output should have a trace with details of the unexpected error. Send the trace to BMC Support.

DTM8805E

TM/BCPii functionality is DISABLED


Explanation: This message is issued by the TM/BCPii subtask during its initialization. TM/BCPii sub-task shut down because of errors during initialization. 

For more information about the specific error, see the preceding DTM88xxE messages. 

Operator response: None

Programmer Response: Inspect previously reported DTM88xxE errors.

DTM8806E

TM A/S is NOT authorized to obtain BCPii info  from local CPC. Ensure that TM A/S has at least UPDATE access to the security product profile:

HWI.TARGET.<netid.nau>

in the FACILITY class


Explanation: This message is issued by the TM/BCPii subtask during its initialization. The subtask detected that it is not authorized to issue BCPii requests to obtain information from the local CPC. 

Operator response: To grant this access, add at least UPDATE access to the security product (such as RACF) profile HWI.TARGET.netid.nau  in the FACILITY class, where netid.nau represents the 3- to 17-character SNA name of the local CPC. Specify the SNMP community name in the APPLDATA field. This name should match with the corresponding name defined in SE. For more information about configuring BCPii services, see IBM documentation.

Programmer Response: Authorize the TM starting task to access local CPC. After the problem is fixed recycle SLM to reinitialize the TM/BCPii subtask.

DTM8807E

TM A/S is NOT authorized to update local LPAR BCPii info. Ensure that TM A/S has UPDATE access to the security product profile:

HWI.TARGET.<netid.nau.image>

in the FACILITY class.


Explanation: This message is issued by the TM/BCPii subtask during its initialization. The subtask detected that it is not authorized to issue BCPii requests to update weights of the local LPAR. To grant proper authorization to the TM starting task, add the UPDATE access to the security product (for example, RACF) profile:       HWI.TARGET.netid.nau.image       in the FACILITY class, where      netid.nau      represents the 3- to 17-character SNA name of the local CPC and image represents the 1- to 8-character LPAR name. For information about configuring BCPii services, see IBM documentation.     

Operator response: None.     

Programmer Response: Authorize TM starting task to access local LPAR. After the problem is resolved, recycle SLM to reinitialize the TM/BCPii subtask.

DTM8808E

M A/S is NOT authorized to use BCPii requests to access local CPC. SNMP Community Name in the APPLDATA field of the security product profile:                                   

HWI.TARGET.<netid.nau>     

does not match the name defined in the SE


Explanation: This message is issued by the TM/BCPii subtask during its initialization. The subtask detected that it is unable to issue BCPii requests to the local CPC or any of its LPARS because of a configuration error. The SNMP community name specified as a value of the APPLDATA field in the security product (such as RACF) profile.      

HWI.TARGET.<netid.nau>           

in the FACILITY class does not match the corresponding name defined in SE. In this message netid.nau represents the 3- to 17- character SNA name of the local CPC. For information about configuring BCPii services, see IBM documentation.     

Operator response: None.     

Programmer Response: Make sure that the two names are in uppercase and match exactly. After the problem is fixed, recycle SLM to reinitialize the TM/BCPii subtask.

DTM8809I

TM/BCPii sub-task is shutting down                                     


Explanation: The TM/BCPii subtask is shutting down. If this happens because of  an error, one of the previous DTM88xxE messages contains additional information about it.     

Operator response: None.     

Programmer Response: Make sure there was no DTM88xxE messages. If found, follow the messages description.

DTM8810W

It appears that TM A/S is NOT authorized to obtain information about a number of LPARs. It is recommended to add READ access to the security product profile:                 

HWI.TARGET.<netid.nau>.*  

in the FACILITY class                  


Explanation: This message is issued by the TM/BCPii subtask when it detects a lack of authorization configured in the security product (such as RACF).      

<netid.nau>                                        

represents the 3- to 17-character SNA name of a CPC. For information about configuring BCPii services, see IBM documentation.     

Operator response: None.     

Programmer Response: We recommend to add READ access to the profile:                                            

HWI.TARGET.<netid.nau>.*                                

or                                                         

HWI.TARGET.**                                           

in the FACILITY class of the security product.

DTM8811E

TM A/S is NOT authorized to obtain BCPii info from the specified CPC. Ensure that TM A/S has at least UPDATE access to the security product profile:

HWI.TARGET.<netid.nau>

in the FACILITY class                          


Explanation: This message is issued by the TM/BCPii subtask during its initialization. The subtask detected that it is not authorized to issue BCPii requests to obtain information from the specified CPC. To grant this access add at least UPDATE access to the security product (such as RACF) profile

HWI.TARGET.<netid.nau>                                 

in the FACILITY class, where                               

<netid.nau>                                              

represents the 3- to 17-character SNA name of the CPC. Also, remember to specify the SNMP community name in the APPLDATA field. This name should match the corresponding name defined in SE. For information about configuring BCPii services, see IBM documentation.   

Operator response: None.   

Programmer Response: Authorize TM starting task to access the specified CPC. After the problem is fixed, recycle SLM to reinitialize the TM/BCPii subtask.

DTM8812E

TM A/S is NOT authorized to use BCPii requests to access the specified CPC. SNMP Community Name in the APPLDATA field of the security product profile:                           

HWI.TARGET.<netid.nau>               

does not match the name defined in the SE


Explanation: This message is issued by the TM/BCPii subtask during its initialization. The subtask detected that it is unable to issue BCPii requests to the specified CPC or any of its LPARS because of a configuration error. The SNMP community name specified as a value of the APPLDATA field in the security product (such as RACF) profile               

 HWI.TARGET.<netid.nau>                            

 in the FACILITY class does not match the corresponding name defined in SE. In this message                    

  <netid.nau>                                        

 represents the 3- to 17-character SNA name of the CPC. For information about configuring BCPii services, see IBM documentation.

 Operator response: None.

 Programmer Response: Make sure that the two names are in uppercase and match exactly. After the problem is fixed, recycle SLM to reinitialize the TM/BCPii subtask.

DTM9002I

HSC {‘SLSXCAL’ | ‘LMSACCESS’} INTERFACE ERROR
R15=X’return-code’,RC=x’reason-code’
FOR VOLUME volser


Explanation: The error has occurred as a result of an interface call to StorageTek’s 4400 ACS cartridge database (SLSXCAL) or Memorex 5400 ATL (LMSACCES). The return code and the reason are documented in the StorageTek manual.

System action: The volume is treated as a manual cartridge. The Job Analyzer continues to make calls to the ACS program interface or LMS program Interface (when required) without generating further error messages. The message is deleted after a successful call.

Operator response: Notify personnel responsible for support.

Programmer Response: Determine the problem with the ACS or LMS programming interface and correct it.

DTM9003I

UNABLE TO LOAD HSC MODULE {‘SLSXCAL’ | ‘LMSACCES’},
R15=x’return-code-from-load’


Explanation: Attempted to LOAD the ACS or LMS interface module and the LOAD failed.

System action: The volume is treated as a manual cartridge. The Job Analyzer continues to make calls to the ACS/LMS program interface (when required). The message is deleted after a successful call.

Operator response: Notify personnel responsible for support.

Programmer Response: Determine the problem with the ACS/LMS programming interface and correct it.

DTM9004I

INVALID UNIT NAME unit-name


Explanation: The UNITNAME specified in the TM ACS or TM ATL initialization statements or a command is syntactically invalid.

System action: If the error was found in a statement then TMSS terminates with a return code of 8 once all the initialization statements have been processed. If the error is found in a command, then the command processing is terminated.

Operator response: If the error occurred in a command, re-enter it correctly. Otherwise, notify support personnel.

Programmer Response: Correct statement with a valid UNITNAME.

DTM9005I

INVALID ‘UNIT NAME’ KEYWORD SYNTAX


Explanation: The UNITNAME specified in the TM ACS or TM ATL initialization statements or a command is syntactically invalid.

System action: If the error was found in a statement then TMSS terminates with a return code of 8 once all the initialization statements have been processed. If the error is found in a command, then the command processing is terminated.

Operator response: If the error occurred in a command, re-enter it correctly. Otherwise, notify support personnel.

Programmer Response: Correct statement with a valid UNITNAME.

DTM9006I

STORAGETEK’S 4400 ACS INTERFACE
MODULE ‘SLSXCAL’ NOT AVAILABLE
or
MEMOREX’S ATL INTERFACE MODULE ‘LMSACCES’ NOT AVAILABLE


Explanation: Attempted to LOAD the ACS/LMS interface module at TMSS initialization time and the LOAD failed.

System action: TMSS terminates with a return code of 8 once all the initialization statements have been processed.

Operator response: Notify personnel responsible for support.

Programmer Response: Determine the problem and correct it. Note that message(s) prefixed with IDs of ‘CSV’ normally precede this message.

DTM9007I

UNIT NAME unitname ALREADY BEING HANDLED AS unitname


Explanation: The unit name was already used in a previous TM UNIT statement.

System action: TMSS terminates with a return code of 8 once all the initialization statements have been processed.

Operator response: Notify personnel responsible for support.

Programmer Response: Determine the problem and correct it.

DTM9008I

STORAGETEK’S 4400 HOST SOFTWARE COMPONENT (HSC) INACTIVE
or
MEMOREX’S ATL LIBRARY MANAGEMENT SYSTEM (LMS) INACTIVE


Explanation: The error has occurred as a result of an interface call to S’torageTeks 4400 ACS cartridge database or Memorex’s LMS. The interface has been disabled since TMSS started.

System action: The volume is treated as a manual cartridge. The Job Analyzer continues to make calls to the ACS/LMS program interface (when required) without generating further error messages. The message is deleted after a successful call.

Operator response: Notify personnel responsible for support.

Programmer Response: Determine the problem with the ACS/LMS programming interface and correct it.

DTM9009I

THE INSTALLED LEVEL OF DFP DOES NOT SUPPORT THE PROGRAMMING INTERFACE TO THE TAPE CONFIGURATION DATABASE (TCDB)


Explanation: A TM ATLDS STORGRP initialization statement was encountered, indicating that IBM 3495 support is to be enabled, but the current level of DFP does not support the required interface.

System action: TMSS terminates with a return code of 8 once all initialization statements have been processed.

Operator response: Notify personnel responsible for support.

Programmer Response: Either remove the TM ATLDS initialization statement, or install the correct level of DFP.

DTM9010I

LCS INTERFACE ERROR RC=X’return-code’, REAS=X’reason-code’, FOR VOLSER volser


Explanation: An error occurred while interfacing with the Library Control System (LCS) External Services in an attempt to determine whether a tape cartridge mount will be satisfied by the IBM 3495 Automated Tape Library Dataserver.

System action: The volume is treated as a manual cartridge. The Job Analyzer continues to interface with the LCS without generating further error messages. The message is deleted after the next successful call.

Operator response: Notify personnel responsible for support.

Programmer Response: Analyze the return codes to determine the reason for the failure.

DTM9011I

group-type_STORGRP group-name ALREADY IN USE BY group-type_STORGRP. SPECIFICATION IGNORED


Explanation: group-type: is the type of SMS storage group specified, and can be one of ATLDS, TAPE, or VTS. A TM SMS initialization statement has specified an SMS storage group-name that is already in use because it was specified on an earlier TM SMS initialization statement.

System action: The statement is ignored.

Operator response: Notify personnel responsible for support.

Programmer Response: Ensure that the correct storage group name was specified and remove all duplicates.

DTMHZ010I

Thruput Manager JES2 Exits.


Explanation: The following is a list of Thruput Manager JES2 exits and their status. Exits flagged as "E" are not in the required state.

System action: None

Operator response: None

Programmer Response: Install/enable the required exit.

DTMHZ012E

Error Encountered processing Thruput Manager JES2 Exits.


Explanation: The required exit modules are NOT correctly installed or active.

System action: None

Operator response: Notify personnel responsible for support.

Programmer Response: Check the exits identified with "E".

DTMHZ013E

JCTXMASK was altered: ________________.


Explanation: The JCTXMASK is being used to control which JES2 exits may be called. This may prevent Thruput Manager from processing correctly.

System action: None

Operator response: Notify personnel responsible for support.

Programmer Response: Change installation exit to NOT use JCTXMASK to control exit processing.

DTMHZ020I

Thruput Manager Class List.


Explanation: The following is a list of the JES2 job classes used by Thruput Manager.

System action: None

Operator response: None

Programmer Response: None

DTMHZ022E

Error Encountered processing Thruput Manager Job Classes.


Explanation: A required job class is missing.

System action: None

Operator response: Notify personnel responsible for support.

Programmer Response: Use the TM CLASS operator command to ensure all classes are correctly defined.

DTMHZ023E

No ACTIVE Analyzer initiator.


Explanation: There is currently not an initiator defined and active with the Analysis job class.

System action: None

Operator response: Notify personnel responsible for support.

Programmer Response: Notify personnel responsible for support.

DTMHZ030I

The Thruput Manager started task (____) is active.


Explanation: The named Thruput Manager started task is currently active.

System action: None

Operator response: None

Programmer Response: None

DTMHZ032E

The Thruput Manager started task (____) is not active.


Explanation: The named Thruput Manager started task is currently NOT active.

System action: None

Operator response: Start the Thruput Manager started task.

Programmer Response: None

DTMHZ035E

Unable to obtain JES2 Service Class name, RC=nnn


Explanation: The ??_TMSS_ACTIVE check could not determine the JES2 WLM Service Class name.

System action: None

Operator response: None.

Programmer Response: Check that JES2 is started.

DTMHZ037E

JES2 and TMSS Service Class is not the same


Explanation: The WLM Service Class for JES2 and the Thruput Manager started task are not the same.

System action: None

Operator response: None.

Programmer Response: Ensure that these two tasks run in the same WLM Service Class.

DTMHZ039E

JES2 Parameter: MASDEF HOLD=___ value is too large


Explanation: The JES2 MASDEF HOLD= value is greater than 5 seconds.

System action: None

Operator response: None.

Programmer Response: Set the MASDEF HOLD= value to less than 5 seconds.

DTMHZ040I

Thruput Manager Options Information.


Explanation: The following is the list of components and their status.

System action: None

Operator response: None

Programmer Response: None

DTMHZ042E

Error Encountered processing Thruput Manager Options.


Explanation: The following is the list of components and their status. Components flagged as "E" are not enabled or active as they should be.

System action: None

Operator response: Notify personnel responsible for support.

Programmer Response: Determine why the "E" component is not enabled and active. If necessary, recycle the component.

DTMHZ050I

Thruput Manager SMF Exit Information.


Explanation: The following is a list of the Thruput Managerexit points and their module names.

System action: None

Operator response: None

Programmer Response: None

DTMHZ053E

Error Encountered processing Thruput Manager SMF exits.


Explanation: The following is a list of the Thruput Manager exit points and their module names.

System action: None

Operator response: None

Programmer Response: None

DTMHZ054E

Thruput Manager SMF Vector Table is missing or in error.


Explanation: The following is a list of the Thruput Manager exit points and their module names. Entries flagged with "E" are disabled due to errors.

System action: The required exit point will not be called.

Operator response: Notify personnel responsible for support.

Programmer Response: Notify BMC Support of this issue for further diagnosis.

DTMHZ055E

Command Prefix prefix is not registered to ThruPut Manager on system


Explanation: The ThruPut Manager COMCHAR is not registered to ThruPut Manager.

System action: None

Operator response: Notify personnel responsible for support.

Programmer Response: Issue the "D OPDATA" command to determine the command prefix conflict.

DTMHZ060I

Non-Standard Thruput Manager setting encountered.


Explanation: The following are options that have been enabled but are not the norm for standard operation.

System action: None

Operator response: None

Operator response: Examine the following settings. If they have been enabled due to direction from BMC Support ignore this alert. If not, the option should be reversed.

DTMHZ063E

Non-Standard settings are in effect.


Explanation: This message is an exception alert for DTMHZ060I.

System action: None

Operator response: Notify personnel responsible for support.

Programmer Response: See DTMHZ060I.

DTMHZ064I

SName=________ Code=__ license will expire in __ days.


Explanation: The license for Thruput Manager will expire in more than 7 days.

System action: None

Operator response: None

Programmer Response: None

DTMHZ065E

SName=________ Code=__ license will expire in __ days.


Explanation: The license for Thruput Manager will expire in less than 7 days.

System action: None

Operator response: None

Programmer Response: Contact BMC Support to obtain a new license.

DTMHZ066E

1 Job is MHS_TM held.
Or
n Jobs are MHS_TM held.


Explanation: There are jobs that are MHS_TM held. Issue the MHS_TM DISPLAY JOBS DETAILS command to see these jobs and possibly release them with the MHS_TM RELEASE command if the Hold reasons have been resolved.

System action: None

Operator response: None

Programmer Response: None.

DTMHZ068I

Unable to validate license at this time. (RC=n RS=n)


Explanation: The Health Check routine could not validate the license.

System action: None.

Operator response: None.

Programmer Response: Ensure that LMS has been started. If it is active, notify support.

DTMHZ069E

At least one ThruPut Manager load module is not at the maintenance level expected for your PTF level. Issue TM D LEVEL to see which modules are incorrect.


Explanation: A previous check found mis-leveled ThruPut Manager modules on your system.

Operator response: None.

Programmer Response: See DTM7128E.

DTMHZ070I

ThruPut Manager dynamically inserted # of its JES2 exits during JES2 initialization
Explanation: ThruPut Manager detected that it dynamically inserted some, but not all, of its JES2 exits during JES2 initialization.

System action: None.

Operator response: None.

Programmer Response: If your site is specifying all its ThruPut Manager exits in your JES2 initialization deck, look to see which ones are missing (recent PTFs may include comments about newly added exits). Otherwise, this may be ignored.

DTMSTRB00

Unable to LOAD module STRBGM50


Explanation: The module is not accessible to the Thruput Manager task.

System action: None.

Operator response: Notify personnel responsible for support.

Programmer Response: Make the module accessible by having it in a linklist or by having a Steplib with the Thruput Manager started task (not recommended).

DTMSTRB02

/*STROBE card too many parameters specified


Explanation: Self-explanatory.

System action: None.

Operator response: None.

Programmer Response: Specify fewer parameters.

DTMU001

INPUT FILE (DTMRMCF), OPEN FAILED


Explanation: The Control File Utility could not open the Control File.

System action: The Control File Utility terminates.

Operator response: None.

Programmer Response: Probable missing DTMRMCF DD statement. Check to ensure that the DTMRMCF DD statement describing the Control File was present.

DTMU002

INPUT FILE (DTMRMCF), INFO REQUEST FAILED


Explanation: The Control File Utility attempted to obtain information about the File described by the DTMRMCF DD statement, but the request was failed.

System action: The Control File Utility terminates.

Operator response: None.

Programmer Response: Check to ensure that the DTMRMCF DD statement is actually describing a valid Control File.

DTMU003

INPUT FILE (DTMRMCF), INVALID CID LIST


Explanation: The Control File Utility has determined that the File described by the DTMRMCF DD statement is a Control File, but the File contains invalid data.

System action: The Control File Utility terminates.

Operator response: None.

Programmer Response: Probable internal damage to the Control File. Contact BMC Support.

DTMU004

INPUT FILE (DTMRMCF), NO RM CNTL CID


Explanation: The Control File Utility has determined that the File described by the DTMRMCF DD statement is a Control File, but the File contains invalid data.

System action: The Control File Utility terminates.

Operator response: None.

Programmer Response: Probable internal damage to the Control File. Contact BMC Support.

DTMU005

INPUT FILE (DTMRMCF), READ ERROR XAM RC=X’rc’ XAM text


Explanation:

rc: Is an internal return code.
text: Is a brief description of the error.
The Control File Utility was not able to read data from the input Control File.

System action: The Control File Utility continues.

Operator response: None.

Programmer Response: If you are recovering a damaged Control File, this message could be normal, but it does indicate that data has been lost. If the error is unexpected, contact BMC Support.

DTMU010

COPY/CONVERSION SUCCESSFUL


Explanation: The Control File Utility has completed normally.

System action: None.

Operator response: None.

Programmer Response: None.

DTMU011

OUTPUT FILE (NEWRMCF), OPEN FAILED


Explanation: The Control File Utility could not open the output File.

System action: The Control File Utility terminates.

Operator response: None.

Programmer Response: Probable missing NEWRMCF DD statement. Check to ensure that the NEWRMCF DD statement describing the new Control File was present.

DTMU012

OUTPUT FILE (NEWRMCF), INFO REQUEST FAILED


Explanation: The Control File Utility attempted to obtain information about the File described by the NEWRMCF DD statement, but the request was failed.

System action: The Control File Utility terminates.

Operator response: None.

Programmer Response: Check to ensure that the NEWRMCF DD statement is actually describing a valid Control File.

DTMU013

OUTPUT FILE (NEWRMCF), INVALID CID LIST


Explanation: The Control File Utility has determined that the File described by the NEWRMCF DD statement is a Control File, but the File contains invalid data.

System action: The Control File Utility terminates.

Operator response: None.

Programmer Response: Probable internal damage to the Control File. Contact BMC Support.

DTMU014

OUTPUT FILE (NEWRMCF), WRITE ERROR XAM RC=X’rc’ XAM text


Explanation:
rc: Is an internal return code.
text: Is a brief description of the error.

System action: The Control File Utility continues.

Operator response: None.

Programmer Response: Re-allocate the new Control File and re-try the operation.

DTMU015

OUTPUT FILE (NEWRMCF), INITIALIZE FAILED


Explanation: The Control File Utility could not initialize the new Control File successfully.

System action: The Control File Utility terminates.

Operator response: None.

Programmer Response: This could result from a write error, insufficient DASD space to write the complete File as requested, or insufficient memory for the Control File Utility to create the necessary buffers. Re-allocate the new Control File and re-try the operation, increasing the region size for the job if necessary.

DTMU018

OUTPUT FILE TOO SMALL, USE 64 CYLINDERS


Explanation: The space allocated for the new Control File was insufficient to create the File.

System action: The Control File Utility terminates.

Operator response: None.

Programmer Response: Increase the space allocated for the Control File.

DTMU021

DUMP FILE (DTMDUMP), OPEN FAILED


Explanation: The Control File Utility could not open the dump data set.

System action: The Control File Utility terminates.

Operator response: None.

Programmer Response: Probable missing DTMDUMP DD statement. Check to ensure that the DTMDUMP DD statement describing the dump data set was present.

DTMU022

DUMP SUCCESSFUL


Explanation: The Control File Utility has completed normally.

System action: None.

Operator response: None.

Programmer Response: None.

DTMU026

ANALYZE - ERRORS IN CID


Explanation: The Control File Utility has found that there are errors in the Control File.

System action: None.

Operator response: None.

Programmer Response: Obtain a dump of the Control File, then run the REPAIR function of the Control File Utility.

DTMU027

REPAIR UNSUCCESSFUL


Explanation: The Control File Utility was unable to complete repairs.

System action: None.

Operator response: None.

Programmer Response: Cold start the Control File.

DTMU028

ANALYZE FUNCTION COMPLETED SUCCESSFULLY


Explanation: The Control File Utility has completed analysis of the Control File.

System action: None.

Operator response: None.

Programmer Response: Review the analysis report.

DTMU029

REPAIR FUNCTION COMPLETED SUCCESSFULLY


Explanation: The Control File Utility has completed repairing the Control File.

System action: None.

Operator response: None.

Programmer Response: Review the analysis report for possible job information loss.

DTMU037

PRE-V6 CONTROL FILE NEEDS V5 UTILITY


Explanation: An attempt was made to use the Version 6 Control File Utility with a version 5 Control File.

System action: The Control File Utility terminates.

Operator response: None.

Programmer Response: Use the Version 5 Control File Utility.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*