ESP Workload Manager Messages and Codes

ESP Workload Manager

Version 5.4

Messages and Codes

ESP-5.4-MC-03

Third Edition (April 2005)

This edition applies to Version 5 Release 4 of ESP Workload Manager. The software and related manuals are protected by copyright law.

Trademark Notice

Cybermation and ESP Workload Manager are registered trademarks of Cybermation, Inc.

ESP Encore is a registered trademark of Cybermation Inc.

IBM, z/OS, and AS/400 are registered trademarks of IBM.

All other brand and product names are trademarks or registered trademarks of their respective companies.

ESP Workload Manager Documentation© 2005 Cybermation Inc. All rights reserved.

No portion of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without the express written permission of

Cybermation International Distribution SRLwww.cybermation.com

U.S. Government Users. RESTRICTED RIGHTS - Use, duplication or disclosure restricted by the GSA ADP Schedule Contract with Cybermation USA, Inc., a subsidiary of Cybermation International Distribution SRL.

ESP-5.4-MC-03 1

Messages and Codes

Note: If you find an explanation incomplete and need help in resolving a problem, please call Cybermation Customer Support and Services.

2 ESP-5.4-MC-03

0001E UNBALANCED PARENTHESES Explanation: A command or expression contained unbalanced parentheses. Either too

many opening parentheses or too many closing parentheses were detected.

System Action: The command is not executed. User Response: Correct the command and retry.

0002E INVALID STRING Explanation: A string was not properly enclosed within single quotation marks. System Action: The command containing the string is not executed. User Response: Ensure the string is enclosed within single quotation marks.

0003E Data set is not opened Explanation: The data set could not be opened. System Action: The utility function was not performed. User Response: Check the preceding message for more information on this error. If

there is no preceding message, this indicates that the data set has not been specified or opened.

0004E INVALID STATEMENT SYNTAX Explanation: The reverse Polish statement contains a syntax error. System Action: The statement is not evaluated. User Response: Correct the statement and try again.

0005E OPERATOR OUT OF SEQUENCE Explanation: An infix operator must follow a value. System Action: The statement is not evaluated. User Response: Correct the statement and try again.

0006E INCOMPATIBLE DECLARE OPTIONS SPECIFIED Explanation: A DCL statement is incomplete. No variable names have been specified. System Action: The requested function is not completed. User Response: Correct the DCL statement and try again.

0007E INVALID VARIABLE NAME xxxx Explanation: In a DCL statement, variable names must begin with an alphabetic or

national character, with the remainder of the name alphanumeric or national.

System Action: The requested function is not completed. User Response: Correct the DCL statement and try again.

0008E UNDEFINED DATA TYPE xxxx Explanation: The only valid data types are CHAR, BIN, FIXED, BOOLEAN and NOSTRIP. System Action: The statement is not evaluated. User Response: Correct the statement and try again.

Messages and Codes

ESP-5.4-MC-03 3

0009E CONFLICTING VARIABLE TYPES Explanation: The statement should only contain one data type keyword. System Action: The statement is not evaluated. User Response: Correct the statement and try again.

0010E SYNTAX ERROR IN EXPRESSION Explanation: The expression contains too few arguments. System Action: The expression is not evaluated. User Response: Correct the expression and try again.

0011E OPERATOR USE INCONSISTENT WITH DATA TYPE Explanation: An operator is being applied to arguments of the wrong type. System Action: The expression is not evaluated. User Response: Correct the expression and try again.

0012E INVALID EXPRESSION Explanation: The C-language expression is syntactically incorrect. System Action: The requested function is not completed. User Response: Correct the expression and try again.

0013E VARIABLE xxxx NOT DEFINED Explanation: The variable must first appear in a declarative statement or on the

left-hand side of an assignment statement. System Action: The statement is not executed. User Response: Add a variable declaration or assignment statement and try again.

0014E INTERMEDIATE STRING LENGTH EXCEEDS MAXIMUM Explanation: During an addition operation, the combined string length exceeds 2048

characters. System Action: The requested function is not completed. User Response: Correct the program and try again.

0015E SYNTAX ERROR IN EXPRESSION Explanation: The expression contains too few arguments. System Action: The expression is not evaluated. User Response: Correct the expression and try again.

0016E OPERATOR USE INCONSISTENT WITH DATA TYPE Explanation: An operator is being applied to arguments of the wrong type. System Action: The expression is not evaluated. User Response: Correct the expression and try again.

0017E INVALID EXPRESSION Explanation: The C-language expression is syntactically incorrect. System Action: The requested function is not completed. User Response: Correct the expression and try again.

4 ESP-5.4-MC-03

0018E VARIABLE xxxx NOT DEFINED Explanation: The variable must first appear in a declarative statement or on the

left-hand side of an assignment statement. System Action: The statement is not executed. User Response: Add a variable declaration or assignment statement and try again.

0019E INVALID SUBFIELD FOR xxxx Explanation: The parenthesized part of the data type is incompatible with that data

type. System Action: The statement is not executed. User Response: Correct the variable declaration and try again.

0020E LABEL xxxx NOT FOUND Explanation: A JUMPTO command was entered but specified a label that was not found

before the end of current file. System Action: An error condition is signalled. User Response: Insert a label at the appropriate location, or correct the label

specification.

0021E 'ELSE' STATEMENT FOUND OUT OF CONTEXT Explanation: An 'ELSE' statement was found without a matching 'IF...THEN' construct.

Sometimes this error can be caused by a syntax error in the 'IF..THEN' construct.

System Action: The command is ignored. User Response: Check the nesting levels of the 'IF-THEN-ELSE' logic.

0022E NO THEN STATEMENT FOUND Explanation: An IF statement was found that did not have a matching 'THEN' clause. System Action: The IF statement is not executed. The input stack is flushed. User Response: You need to specify a THEN clause on the same logical input line as

the IF statement.

0023E INVALID LOGICAL EXPRESSION Explanation: An IF statement encountered an invalid logical expression. System Action: The statement is not executed. The input stack is flushed. User Response: A logical expression must consist of an expression that returns an

integer result, or must contain a relational operator.

0024E INVALID VARIABLE NAME Explanation: A variable name did not conform to the appropriate syntax. The first

character should be alphabetic or a national character. subsequent characters may also contain numeric digits.

System Action: The expression is not evaluated. User Response: Specify a correct variable name.

0025E ENDDO HAS NO MATCHING DO STATEMENT Explanation: An 'ENDDO' statement was found without a matching 'DO' statement.

Messages and Codes

ESP-5.4-MC-03 5

'DO' and 'ENDDO' statements must come in matching pairs. They can be nested to any depth.

System Action: An error condition is raised. User Response: Check the source for nested 'DO' and 'ENDDO' statements. You will

find it easier to locate errors if you indent nested DO..ENDDO statements.

0026E MISSING 'ENDDO' STATEMENT Explanation: There is a 'DO' statement without matching 'ENDDO'. 'DO' and 'ENDDO'

must come in matching pairs. They can be nested to any depth. System Action: An error condition is raised. User Response: Check the source to match 'DO' and 'ENDDO' statements. You may find it

easier to locate errors if you indent nested DO...ENDDO statements.

0027E xxxx Explanation: An error has occurred which prevents the proc from being executed. System Action: The requested function is terminated. User Response: Refer to the previous message for further information regarding this

error.

0028E INVALID DATE PARAMETER ON FUNCTION CALL Explanation: A single character-string parameter is required. System Action: The requested function is not completed. User Response: Correct the statement and try again.

0029E INVALID DATE PARAMETER ON FUNCTION CALL Explanation: Invalid parameter on call of DAYS_TO function. System Action: The requested function is not completed. User Response: Correct the parameter and try again.

0030E INVALID READVAL SOURCE STRING Explanation: The READVAL statement had in invalid source string specified. The

source string should be a literal string or character variable. System Action: The READVAL statement is not processed. User Response: Correct the input string.

0031E INVALID READVAL KEYWORD SPECIFIED Explanation: The READVAL statement had an unrecognized keyword specified. System Action: The statement is not processed. User Response: Correct or remove the invalid keyword.

0032E INVALID READVAL POSITIONAL COUNT Explanation: The POS keyword of the READVAL statement had an invalid operand.

Valid operands are numeric strings or integer or Boolean variables. System Action: The statement is not processed. User Response: Correct the specification, using a valid type.

6 ESP-5.4-MC-03

0033E INVALID READVAL TARGET VARIABLE Explanation: A target variable name passed to the READVAL statement did not conform

variable name convention. The name should consist of an alphanumeric string, the first character of which is alphabetic, national or the underscore.

System Action: The READVAL statement is not processed. User Response: Correct the target variable name.

0034E INVALID PARAMETERS PASSED TO PROMPT FUNCTION Explanation: The PROMPT function had invalid parameters specified. Valid

parameters are an optional message ID and a character string. The message ID can consist of an integer variable or numeric expression. The message ID can consist of a literal or character variable.

System Action: The statement containing the PROMPT function is not executed. User Response: Correct the function parameters.

0035E INVALID OR INCOMPLETE ASSIGNMENT STATEMENT OR EXPRESSION

Explanation: An assignment statement or expression was not properly formed, or was missing an assignment operator. This error can also arise if a blank or comma is not present between a command name and its operands. For example, if 'MEMBER (MEM1)' was entered as 'MEMBER(MEM1)', the command would be taken as a function call, leading to an incomplete assignment statement.

System Action: The command is not executed. User Response: Correct the statement. Either complete the assignment statement, or

place a blank after the command name.

0036E INVALID DATE PARAMETER ON FUNCTION CALL Explanation: Invalid parameter on call of DAYS_BETWEEN function. System Action: The requested function is not completed. User Response: Correct the parameter and try again.

0037E INVALID PARAMETER PASSED TO ACTIVE FUNCTION Explanation: A single character-string parameter is required. System Action: A single character string parameter is required. The string may not be

more than 8 characters long. User Response: Correct the statement and try again.

0038E INVALID PARAMETER PASSED TO SQRT FUNCTION Explanation: A single double-precision parameter is required. System Action: The requested function is not completed. User Response: Correct the statement and try again.

0039E INVALID PARAMETER PASSED TO TAPES FUNCTION Explanation: A character string of length two is required. The first character

must be T, C, or R, while the second must be T, A, or O.

Messages and Codes

ESP-5.4-MC-03 7

System Action: The requested function is not completed. User Response: Correct the statement and try again.

0040E Unable to open the input or output data set Explanation: The GENFLOW command could not open the input and/or output data sets. System Action: The command is ignored. User Response: Reenter the command with the correct parameters. Enter the GENFLOW

command, ensuring data set names and attributes are correct.

0041E INVALID DATE PARAMETER ON FUNCTION CALL Explanation: Invalid parameter on call of DAYS_TO function. System Action: The requested function is not completed. User Response: Correct the parameter and try again.

0042E INVALID DATE PARAMETER ON FUNCTION CALL Explanation: Invalid parameter on call of DAYS_BETWEEN function. System Action: The requested function is not completed. User Response: Correct the parameter and try again.

0043E INVALID JOBNAME Explanation: The job name is too long in the LOCASCB function. System Action: The requested function is not completed. User Response: Correct the job name and try again.

0044E INVALID PARAMETERS PASSED TO JOBONQ FUNCTION Explanation: Job name missing or too long, or too many parameters to the JOBONQ or

JOBONCSF function. System Action: The requested function is not completed. User Response: Correct the parameters and try again.

0045E SUBSYSTEM REQUEST ERROR CODE nn ENCOUNTERED BY JOBONQ FUNCTION

Explanation: Subsystem or JES error in JOBONQ or JOBONCSF function. System Action: The requested function is not completed. User Response: Ensure that the ESP subsystem is functioning properly.

0046E IRXINIT ERROR CODE nn, REASON CODE nn Explanation: The IRXINIT initialization module has failed. System Action: The REXX interface is not available via ESP. User Response: Ensure that the IRXINIT module is available in the link list or a

STEPLIB library.

0047E IRXTERM ERROR CODE nn Explanation: The IRXTERM initialization module has failed. System Action: User Response: Ensure that the IRXTERM module is available in the link list or a

STEPLIB library.

8 ESP-5.4-MC-03

0048I INVALID SELECTION LIST SPECIFIED Explanation: The selection list in the SELECT parameter is not valid. System Action: User Response: Correct the SELECT parameter and try again.

0049E INVALID SYMBOL ON LEFT HAND SIDE OF ASSIGNMENT Explanation: The symbol on the left hand side of this assignment statement cannot

be changed. This is a variable which can only be given a value by ESP itself.

System Action: User Response: Define a new user variable and initialize it with the value of the

variable formerly on the left hand side. This user variable can now be modified with assignment statements.

0050E Expression contains divide by zero Explanation: A Clang expression containing a division operand and an Integer

variable divisor was encountered. The value of the divisor variable was zero.

System Action: The Event containing the statement is terminated. This message is preceded by a message indicating an error in the Event.

User Response: Determine why the divisor variable value was zero. Correct the problem and trigger the Event again.

0051E Command is not valid with SAF Explanation: You have attempted to perform a command such as LISTUSER which is not

valid in the SAF environment. These command(s) are only applicable to a non-SAF ESP environment.

System Action: The request is denied. User Response: Do not request non-SAF commands in a SAF environment.

0052E Invalid Request Block passed to xxxx Explanation: An invalid request block was passed from an ESP module to the

workload object object-oriented interface layer service module. System Action: The request is rejected. User Response: This is caused by an internal logic error. Notify Cybermation support.

0053E InfoServ is not installed Explanation: During ESP initialization, it was determined the InfoServ product was

not installed. System Action: Processing continues. User Response: If InfoServ is supposed to be installed, contact your system support.

0054E Invalid Agent Message format Explanation: A workload object message was passed to the ESP API. The message

did not have the correct header format. System Action: The message is ignored. User Response: If this message comes from a MGRMSG command or AGENTMSG command,

Messages and Codes

ESP-5.4-MC-03 9

correct the message header. The message may also come from a script or program on a non-MVS computer. This would have to be corrected.

0055E Agent definition not found for xxxx Explanation: A AGENTMSG command specified an incorrect agent name. System Action: The request is ignored. User Response: correct the agent name.

0056E Agent definition not found for xxxx Explanation: An AGENTMSG command was issued. However, no agents have been defined. System Action: The command is ignored. User Response: The agent definition file needs to be loaded. (LOADAGDF command or

initialization statement)

0057E Agent name xxxx is too long Explanation: The agent name specified in an AGENTMSG command exceeded 16

characters. The maximum length allowed for the name is 16 characters.

System Action: The request is rejected. User Response: Correct the agent name and reissue the command.

0058E Invalid request code passed to xxxx Explanation: An invalid request code was passed from an ESP module to the

workload object object-oriented interface layer service module. System Action: The request is rejected. User Response: This is caused by an internal logic error. Notify Cybermation support.

0060W No response received from subsystem Explanation: An operator command was issued to the subsystem. The subsystem did

not respond to the command. System Action: The command is ignored. User Response: Contact your system support personnel.

0061E Command ignored, should be less than 116 characters Explanation: An operator command was issued which the subsystem tried to execute.

The command was 116 or more characters in length. System Action: The command is not executed. User Response: Reduce the length of the command string.

0062I Command accepted by subsystem Explanation: An operator command was issued to the subsystem. The command was

accepted by the subsystem for execution. System Action: The subsystem will attempt to execute the command. User Response: None.

0063W Data set is not sequential or a member of a PDS Explanation: The SCAN command specified a partitioned data set. A sequential data

set or member of a PDS is required.

10 ESP-5.4-MC-03

System Action: The SCAN command is terminated. User Response: Enter the SCAN command specifying a sequential data set or member of a

PDS.

0064E Subsystem request error code nn nn encountered by RETSCBD function Explanation: A subsystem error occurred in the RETSCBD function. 'nn nn' are the

subsystem return and reason codes. System Action: The RETSCBD function is not completed. User Response: Ensure that the ESP subsystem is functioning properly.

0065E Invalid parameters passed to RETSCBD function Explanation: Invalid parameters were passed to the RETSCBD function. System Action: The RETSCBD function is not completed. User Response: Correct the parameters and re-issue the function.

0066E Subsystem request error code nn encountered by RETSCBD function Explanation: A subsystem error occurred in the RETSCBD function. 'nn' is the

subsystem return code. System Action: The RETSCBD function is not completed. User Response: Ensure that the ESP subsystem is functioning properly.

0067E Subsystem request error code nn nn encountered by JOBONCSF function Explanation: A subsystem error or JES occurred in the JOBONCSF function. 'nn nn'

are the subsystem return and reason codes. System Action: The JOBONCSF function is not completed. User Response: Ensure that the ESP subsystem is functioning properly.

0068E Invalid parameters passed to JOBONCSF function Explanation: Invalid parameters were passed to the JOBONCSF function. The job name

was or too long, or too many parameters to the JOBONCSF function. System Action: The JOBONCSF function is not completed. User Response: Correct the parameters and re-issue the function.

0069E Subsystem request error code nn encountered by JOBONCSF function Explanation: A subsystem error occurred in the JOBONCSF function. 'nn' is the

subsystem return code. System Action: The JOBONCSF function is not completed. User Response: Ensure that the ESP subsystem is functioning properly.

0070I xxxx Explanation: An error occurred allocating the output data set for the CYBESUTS

utility. The message text describes the error. System Action: The utility is terminated. User Response: Correct the error and execute the utility again.

0071I Scoreboard report generated Explanation: The CYBESUTS utility has successfully dumped the scoreboard to the

data set specified.

Messages and Codes

ESP-5.4-MC-03 11

System Action: None. User Response: None.

0072I No scoreboard active Explanation: The CYBESUTS utility attempted to dump the scoreboard. No scoreboard

was found for the specified subsystem. System Action: The CYBESUTS utility is terminated. User Response: Ensure the specified subsystem is active and re-execute the utility.

0073W APPLID SPECIFIED FOR JOB xxxx{.yyy} WHICH IS NOT EXTERNAL, IGNORED

Explanation: The APPLID keyword was specified on a JOB statement. However, the job was not identified as an external or manual submit job. In this case, the application identifier is taken from the APPL statement.

System Action: The APPLID keyword is ignored. User Response: Remove the APPLID keyword. One Event can only define a single

application

0074E INVALID MEMBER NAME xxxx Explanation: A job refers to an invalid member name on a POSTREQ, PREREQ, COREQ or

RELEASE statement. System Action: The entire ESPPROC is aborted. User Response: Correct the statement in error and trigger the Event.

0075E Possible loop in predecessor/successor relationships Explanation: During execution or simulation of an Event, a loop was detected in the

predecessor/successor relationships of some of the jobs. System Action: The Event execution or simulation is suspended. User Response: Correct the job linkages.

0076E ILLEGAL INPUT FILE Explanation: The data set specified in the MODEL command was not a Scheduled

Activity data set. System Action: The command processing is terminated. User Response: Re-specify the command with a data set that is a Scheduled Activity

data set.

0077E Insufficient space in Appl record to insert job xxxx into Appl yyyy Explanation: System Action: User Response:

0078E Insufficient space in Appl record to update job xxxx in Appl yyyy Explanation: System Action: User Response:

12 ESP-5.4-MC-03

0079W Job xxxx already exists in Appl yyyy Explanation: An attempt was made to insert a job into an active application.

However, the specified job was an already active member of the specified application.

System Action: The request is denied. User Response: Ensure the job name was correctly specified. If you need another copy

of the same job, use a unique qualifier.

0080W Job xxxx already exists in Appl yyyy Explanation: An attempt was made to insert a job into an active application.




0081E Unable to locate job xxxx for update in Appl yyyy Explanation: The ESP subsystem was unable to locate Job "xxxx" in Application

"yyyy". One explanation is that multiple jobs were contained within one JCL member targeted by an IJ command.

System Action: Processing continues. User Response: If the above explanation is true, none is required. However, it is

recommended that a member which is targeted by the IJ command contain only one job. Otherwise, contact your system support.

0082E Unable to locate job xxxx for update in Appl yyyy Explanation: The ESP subsystem was unable to locate Job "xxxx" in Application




0083W Requested generation of Appl xxxx not found Explanation: A user requested action on a job within an Application. The requested

Application did not exist. System Action: The command is aborted. User Response: Use the LISTAPPL command to confirm the existence of the specified

Application.

0084S Unable to initialize subsystem Explanation: An error occurred while trying to build the subsystem interface. This

is probably an internal logic error. System Action: Processing terminates. User Response: Notify your software support personnel.

Messages and Codes

ESP-5.4-MC-03 13

0085S Unable to getmain storage for the vector table Explanation: ESP was unable to obtain common area storage for the subsystem vector

table. System Action: Processing terminates. User Response: This problem is due to a shortage of common storage. The subsystem

may be restarted after the shortage is relieved.

0086S Insufficient CSA to load module xxxx Explanation: A shortage of common storage area (CSA) prevented the loading of a

module necessary for subsystem processing. System Action: This message is followed by another message indicating the action

taken. User Response: Respond to the message that follows.

0087S Unable to load module xxxx Explanation: An error occurred while trying to load a module necessary for subsystem

processing. System Action: This message is followed by another message indicating the action

taken. User Response: Respond to the message that follows.

0088E Error scanning command, RC=nn Explanation: A problem was encountered while parsing the command line. System Action: The command is ignored. The user is prompted for a new command. User Response: System routine IKJPARS returned error code nn.

When nn=12: invalid parameters passed to parse from CP. nn=16: No space available. nn=20: Validity check routine termination. nn=24: An error in input parameters was detected in the IKJPARS2 load module. nn=28: A line drop condition was detected and IKJPTGT (PUTGET I/O service routine) or IKJPUTL (PUTLINE I/O service routine) set return codes of 24 and 32 respectively. If the problem persists, notify your support personnel.

0089E xxxx is not a partitioned data set Explanation: A non-partitioned data set was specified as input to the OBJCHECK

command. System Action: The command is terminated. User Response: Specify a partitioned data set as input to the OBJCHECK command.

0090E xxxx is not a fixed length 80 byte record data set Explanation: A data set with invalid DCB attributes was specified as input to the

OBJCHECK command. The input data set must be RECFM=F, LRECL=80. System Action: The command is terminated. User Response: Specify a data set with proper DCB attributes as input to the OBJCHECK

command.

14 ESP-5.4-MC-03

0091W Node xxxx not found Explanation: In a CPU statement, the value of the NODE parameter specified an

undefined node name. System Action: The CPU is not defined. User Response: Add a definition for the node.

0092E Invalid Request Block passed to xxxx Explanation: An invalid request block was passed from an ESP module to the

workload object object-oriented interface layer. System Action: The request is rejected. User Response: This is caused by an internal logic error. Notify Cybermation support.

0093E Invalid request code passed to xxxx Explanation: An invalid request code was passed from an ESP module to the


0094E Invalid Parameters passed to xxxx Explanation: Invalid parameters were passed from an ESP module to the


0095E Inconsistent parameters passed to xxxx (nn) Explanation: System Action: User Response:

0096E Module directory passed to xxxx is invalid Explanation: System Action: User Response:

0097E Unable to load workload object package xxxx Explanation: System Action: User Response:

0098E Module xxxx does not contain a valid workload object package Explanation: System Action: User Response:

0099C Workload Object Module Display Explanation:

Messages and Codes

ESP-5.4-MC-03 15

System Action: User Response:

0101W INVALID COMMAND, xxxx Explanation: An undefined command name was entered as an ESP command. System Action: The command is ignored. The TSO user is prompted for a new command. User Response: A TSO user should reenter the command with the correct name. A batch

user should correct the command for the next execution.

0102I OK Explanation: A conversational command with no specific response has completed.

This is a confirmation that the command has completed successfully. System Action: None. User Response:

0103E ERROR SCANNING COMMAND, RC=nn Explanation: A problem was encountered while parsing the command line. System Action: The command is ignored. The user is prompted for a new command. User Response: System routine IKJPARS returned error code nn.


0104E COMMAND xxxx NOT FOUND Explanation: This is not a valid TSO command. System Action: User Response: Correct the command and try again.

0105S ERROR OBTAINING A COMMAND, RC=nn Explanation: A problem was encountered while trying to retrieve a command input

line. This is normally caused by an internal logic error. System Action: This message is followed by message 0106S and command processing is

terminated. User Response: Notify your support personnel.

0106S COMMAND PROCESSING TERMINATED Explanation: A previous error caused the command processor to terminate. System Action: Command processing is terminated. User Response: Notify your support personnel.

0107E COMMAND SUPPRESSED BY INSTALLATION EXIT Explanation: A user specified command was rejected by the installation command

16 ESP-5.4-MC-03

authorization exit. System Action: The command is not executed. User Response: You may have entered parameters that the installation systems

programmers have decided to suppress. If you are unsure, notify your installation's system programming team.

0108W nn Out of extent slots encountered in data set xxxx, File recovered Explanation: The slot file access method encountered slots which were

allocated but not physically on the file. The access method recovered the file. Applicable only to APPL/TRACK and EXH files.

System Action: Processing continues with the successfully recovered file. User Response: None required.

0109W The number of successors is limited to 50 in JES3 dependent job control

network. Explanation: Up to 50 successors for a job can be specified in JES3 dependent job

control network. System Action: Simulation continues. User Response: Limit the number of successors.

0111W INVALID ITERATION FACTOR Explanation: The TEST command was entered with an invalid iteration factor. A

valid iteration factor consists of an all numeric field. System Action: The command is ignored. User Response: Reenter the command with a valid iteration factor.

0112C JSS TEST Explanation: The TEST command results are being displayed. System Action: User Response:

0113C SDB DISPLAY Explanation: A request was made to list the storage used by a Cybermation product.

This is the first line of a multiple line display detailing the storage usage by the Cybermation Product.

System Action: Processing continues. User Response: None.

0114I Agent Receiver for xxxx is now terminated Explanation: An Agent communications receiver has been shutdown down at the

request of an operator or user. System Action: The Receiver terminates. User Response: None.

0115E GDTTITEE is xxxx Explanation:

Messages and Codes

ESP-5.4-MC-03 17


0116W Unexpected Data Received return code nn encountered by Agent Receiver

xxxx Explanation: System Action: User Response:

0117W Unexpected Status Received nn encountered by Agent Receiver xxxx Explanation: System Action: User Response:

0119E User security token extract failed Explanation: ESP was attempting to extract a user security token for use in

authorization checking. The extract of the user security token failed.

System Action: The request is terminated. User Response: Notify your system support personnel.

0120E xxxx SUBSYSTEM ERROR CODE nn Explanation: A request was made to the ESP subsystem, but an error occurred. The

return code from the subsystem was "nn". System Action: The request is ignored. User Response: Notify your software support personnel, indicating the request you

made and the resultant return code "nn".

0121E xxxx SUBSYSTEM NOT FOUND Explanation: The ESP subsystem named "xxxx" has not been started since the most

recent IPL. System Action: None. Certain command functions require the ESP subsystem to be up

and running. These commands will fail. User Response: Wait for the subsystem to initialize.

0122E xxxx SUBSYSTEM NOT ACTIVE Explanation: The ESP subsystem, named "xxxx" was not active at the time the command

was issued. System Action: None. Certain command functions require the ESP subsystem to be up

and running. These commands will fail. User Response: Wait for the subsystem to be restarted.

0123E xxxx REQUEST ALREADY PENDING FOR THIS ADDRESS SPACE Explanation: The ESP subsystem, named "xxxx" can only handle one request at a time

from any one address space. Concurrent requests, from multiple tasks in an address space, were made.

System Action: The second request is ignored.

18 ESP-5.4-MC-03

User Response: Do not issue concurrent requests from multiple subtasks.

0124E INSUFFICIENT STORAGE AVAILABLE FOR xxxx SUBSYSTEM REQUEST

Explanation: A main storage shortage prevented normal subsystem request execution to proceed.

System Action: The request is terminated. User Response: This is usually a temporary problem. Retry the command.

0125E LOGIC ERROR, BAD PARAMETERS PASSED TO xxxx SUBSYSTEM Explanation: An internal logic error has occurred in subsystem "xxxx". System Action: The request is terminated. User Response: Notify your software support personnel, indicating the request you

made.

0126E SUBSYSTEM REQUEST ESTAE FAILURE Explanation: The subsystem request processor was unable to establish a recovery

environment. This is normally due to a storage problem. System Action: The request is terminated. User Response: Retry the command. If the problem persists, notify your system support

personnel.

0127E SUBSYSTEM FAILURE Explanation: The ESP subsystem had a failure while your request was pending. System Action: The request is terminated. User Response: Wait for the subsystem to be restarted, then retry your command.

0128E ERROR OCCURRED IN SUBSYSTEM REQUEST PROCESSOR Explanation: The ESP subsystem request processor intercepted an abend. System Action: The request is terminated. A dump is produced. User Response: Report the problem to your system support personnel.

0129E USERID OR PASSWORD NOT SPECIFIED Explanation: A request was made to ESP from a batch job. ESP was unable to

determine the userid, as this was not specified on the JOB card. In addition, the USER command was not entered in the input stream, so ESP was unable to verify the ID of the user making the request.

System Action: The request is rejected. User Response: Identify the request by using the USER/PASSWORD keywords on the job

card, or by using the USER command in the input stream.

0130W UNABLE TO LOCATE xxxx VECTOR TABLE Explanation: The ESP subsystem vector table has not been built. This is due to the

fact that the subsystem has not been initialized. System Action: Certain commands which require the subsystem will not execute. User Response: Wait for the subsystem to be started.

Messages and Codes

ESP-5.4-MC-03 19

0131C Pre-V5.4 TRAKFILE

**********************************************************

* Please run CYBESUT4 utility to upgrade TRAKFILE *

* Sample JCL on ASEPSAME(CYBESS36) or ASEPSAME(CYBESS37) *

* Then restart ESP/WM with upgraded TRAKFILE *

********************************************************** Explanation: ESP/WM has been upgraded to V5.4 or higher without a corresponding

upgrade to the TRAKFILE. The TRAKFILE upgrade is required in order for ESP/WM to support the tracking of jobs with JES numbers up to a maximum of 999999, as supported by JES2 and JES3 in z/OS V1R2 or higher.

System Action: The ESP/WM subsystem terminates. User Response: Run utility CYBESUT4 to create an upgraded version of the TRAKFILE.

ASEPSAME(CYBESS36) contains sample JCL for a TRAKFILE upgrade that renames the old TRAKFILE, creates a new TRAKFILE with the old TRAKFILE's original name, and then formats the new TRAKFILE with the data from the old TRAKFILE. ASEPSAME(CYBESS37) contains sample JCL for a TRAKFILE upgrade that formats the new TRAKFILE with the data from the old TRAKFILE. The new TRAKFILE must have been created prior to this job. Once the TRAKFILE has been upgraded, restart the ESP/WM subsystem.

0132W YOU ATTEMPTED TO SET AN ATTRIBUTE TO WHICH YOU ARE NOT AUTHORIZED

Explanation: During a define or alter of a user or group, you specified a security attribute to which you were not authorized.

System Action: The security attribute is not set. User Response: Ensure you have the valid authority for the request.

0133E SUBSYSTEM REQUEST ERROR CODE nn-nn Explanation: The subsystem request processor handling a ESP request could not

complete a request. The resultant return code from the request was "nn-nn".

System Action: The request is not completed. User Response: Notify your software support personnel, indicating the request you

made and the resultant return codes "nn-nn".

0134E User ID / Password not verified. [ User ID = *] Explanation: The USER command was entered with an invalid password for the

20 ESP-5.4-MC-03

the specified user ID, or the user ID could not be verified by the security system. When the User ID = * is part of the message, an invalid authentication request has been received.

System Action: The request is rejected. User Response: A. Specify the correct user ID and password.

B. For USER ID = *. Review the access specifications for the security product you are using: - Some user IDs were not defined. - Access privileges of defined user IDs were not sufficient. - Cybermation API product users: Review the access privileges of the programs that are using Cybermation API product.

0135E YOU ARE NOT DEFINED TO xxxx Explanation: Your userid has not been defined to the ESP subsystem. System Action: Your userid will not be permitted to define or delete Events. User Response: Request the ESP administrator to define your userid to the system.

0136E SUBSYSTEM xxxx IS NOT AN ESP SUBSYSTEM Explanation: An attempt was made to locate an ESP subsystem with the name indicated

by 'xxxx'. Although a subsystem was located with that name, it did not belong to an ESP subsystem.

System Action: Processing continues as if ESP is inactive. Certain commands that require the subsystem to be active will not execute.

User Response: If you wish to use commands that require the subsystem, wait until the subsystem is initialized.

0137E SUBSYSTEM xxxx IS NOT A COMPATIBLE ESP SUBSYSTEM Explanation: An attempt was made to locate an ESP subsystem with the name indicated

by 'xxxx'. Although a subsystem was located with that name, it was that of a subsystem at an incompatible release level with the TSO command processor.

System Action: Processing continues as if ESP is inactive. Certain commands that require the subsystem to be active will not execute.

User Response: This may occur when a new release of ESP is installed and either the subsystem or the TSO command processor are not upgraded simultaneously. Notify your software support personnel.

0138E REQUEST REJECTED BY INSTALLATION USER VERIFICATION EXIT

Explanation: A request was made to ESP from a batch job. The installation user verification processor denied access to the request.

System Action: The request is denied. User Response: Notify your installation support personnel.

0139E ABEND OCCURRED IN INSTALLATION USER VERIFICATION EXIT Explanation: A request was made to ESP from a batch job. The installation user

verification processor was invoked, but an abend occurred while it was

Messages and Codes

ESP-5.4-MC-03 21

processing. System Action: The request is not processed. User Response: Notify your installation support personnel.

0140E xxxx IS NOT AUTHORIZED {IN THE UPDT|BY SAF} Explanation: Either the event prefix specification (normally equivalent

to a security user ID) xxxx is not defined in the User Profile Definition Table, or the user ID xxxx is not authorized by SAF to perform this action.

System Action: The request is denied. User Response: Notify your installation security administrator.

0141I ENDDEF STATEMENT GENERATED Explanation: An EVENT statement was entered when a previous definition had not been

terminated by an ENDDEF statement. System Action: An ENDDEF is automatically assumed and the previous EVENT definition

completed. User Response: None.

0142E NO EVENT IDENTIFIER SPECIFIED Explanation: An EVENT statement is entered but no identifier was specified in the

label field or as an operand. System Action: The EVENT definition will be flagged as in error. User Response: Respecify the EVENT statement.

0143E ERROR PROCESSING EVENT xxxx.yyyy, SUBSYSTEM ERROR CODE nn

Explanation: An error occurred processing an EVENT. System Action: The processing request is not completed. User Response: Notify your support personnel.

0144E EVENT DATASET FOR GROUP xxxx SUSPENDED Explanation: An attempt was made to define or display an EVENT while the database

containing the EVENT definitions for that group was unavailable to ESP.

System Action: The request is not performed. User Response: Notify your support personnel.

0145E EVENT xxxx.yyyy NOT DEFINED Explanation: You attempted to display or modify an EVENT that has not been defined

to ESP. System Action: The request is not performed. User Response: Ensure that you enter the correct EVENT name.

0146E xxxx IS NOT AUTHORIZED IN THE UPDT OR BY SAF Explanation: Either the event prefix specification (normally equivalent

to a security user ID) xxxx is not defined in the User Profile Definition Table, or the user ID xxxx is not authorized by SAF

22 ESP-5.4-MC-03

to perform this action. System Action: The request is denied. User Response: Notify your installation security administrator.

0147E EVENT xxxx.yyyy ALREADY DEFINED Explanation: An EVENT was defined with the 'ADD' option while a similarly named

EVENT was previously defined. System Action: If the EVENT was defined interactively, i.e. directly from a terminal

while in prompt mode, this message is followed by message 186A. In other cases, the define request is ignored.

User Response: Respond to message 186A.

0148E I/O ERROR PROCESSING EVENT xxxx.yyyy Explanation: An I/O error occurred while processing an EVENT on behalf of a user. System Action: The request is terminated. User Response: Notify your support personnel.

0149E EVENT xxxx.yyyy IS HELD OR SUSPENDED Explanation: A trigger request was made to an EVENT while that EVENT was held or

suspended. System Action: The trigger request is not processed.

If the event was held, ESP will store a pending TDR in the event definition.

User Response: If the event was held, ensure that the EVENT is released before reissuing the trigger, or, release the event, and the pending TDR(s) will be processed.

0150E EVENT DEFINITION SIZE EXCEEDED Explanation: The EVENT definition contained too many statements. System Action: The EVENT definition is terminated. User Response: Redefine your EVENT to contain less definition statements. If

necessary, break it down into multiple EVENTs.

0151E EVENT DEFINITION IGNORED DUE TO PREVIOUS ERRORS Explanation: A previous error occurred while in an EVENT definition. This message

is issued after another error message has already been issued, when an EVENT is not being defined interactively.

System Action: The EVENT definition is ignored. User Response: Correct and reenter the EVENT definition.

0152E NO ACTION ELEMENTS DEFINED, EVENT DEFINITION IGNORED Explanation: An EVENT definition was entered which contained only schedule type

elements. No action statements were included. System Action: The EVENT definition is ignored. User Response: Redefine the EVENT with valid action statements.

Messages and Codes

ESP-5.4-MC-03 23

0153W WARNING, NO SCHEDULE ELEMENTS DEFINED, DIRECT TRIGGER REQUIRED

Explanation: An EVENT was defined which contained only action elements. No schedule or data set triggering elements were defined. In order for the EVENT to execute, a trigger command will have to be issued. This is not an error situation.

System Action: None. User Response: None needed, unless the schedule elements were accidentally omitted.

0154I EVENT xxxx WILL EXECUTE AT yyyy ON zzzz Explanation: An EVENT has just been defined. This message indicates the first

scheduled execution of the EVENT. System Action: None. User Response: None.

0155E xxxx Explanation: The SUBMIT command encountered an error while opening a data set for

verification purposes during the definition of an Event. The message text fully describes the error.

System Action: Processing for that data set is terminated. The Event definition is flagged as in error.

User Response: The response depends on the error encountered.

0156W DATA SET xxxx IS NOT PARTITIONED, LEVEL KEYWORD IGNORED Explanation: A SUBMIT command in an EVENT definition specified the 'LEVEL' keyword

for a non-partitioned data set. System Action: The 'LEVEL' keyword is ignored. User Response: Ensure that the correct data set name was specified.

0157E INVALID DAY OF WEEK xxxx Explanation: An ON statement contained an invalid day of the week. System Action: The ON statement is ignored. User Response: Correct the statement.

0158E INVALID ON UNIT ACTION TYPE xxxx Explanation: An ON statement in an Event definition specified an invalid action.

The valid actions are IGNORE, ADVANCE and DELAY. System Action: The ON statement is ignored. User Response: Correct the statement.

0159E INVALID ON UNIT COUNT nn Explanation: An ON statement in an EVENT definition contained an invalid

ADVANCE/DELAY count. The maximum count allowed is 31. System Action: The ON statement is ignored. User Response: Correct the statement.

24 ESP-5.4-MC-03

0160E ERROR PROCESSING USER/GROUP ENTRY, SUBSYSTEM ERROR CODE nn

Explanation: A subsystem error was encountered when defining or altering a GROUP or USER entry.

System Action: The request is terminated. User Response: Notify your support personnel, indicating the message number and

return code.

0161E ENTRY NOT FOUND Explanation: A GROUP or USER entry specified on an alter or display command was not

found. System Action: The request is ignored. User Response: Ensure the GROUP or USER entry is correctly entered.

0162E Not authorized for requested function Explanation: You attempted to perform a DEFINE, DELETE or ALTER request on a GROUP

or USER entry to which you are not authorized. System Action: The request is denied. User Response: Ensure that you have the correct authority for the functions you need

to perform.

0163E ENTRY ALREADY DEFINED Explanation: An attempt was made to define an already existing USER or GROUP. System Action: The request is ignored. User Response: Ensure that the command was entered correctly.

0164E I/O ERROR ON USER DEFINITION DATASET Explanation: An I/O error occurred while storing or retrieving an entry in the user

definition database. System Action: The request is not processed. This message will be accompanied with a

more descriptive message issued to the system consoles and to the system log.

User Response: Notify your support personnel.

0165E INVALID PASSWORD SPECIFIED Explanation: An invalid current password was specified when changing the password

or accessing ESP through a batch job. System Action: The access to ESP is denied. User Response: Ensure a correct current password is specified.

0166I PASSWORD SUCCESSFULLY ALTERED Explanation: The ESP password for a USER was successfully altered by use of the

PASSWORD command. System Action: None. User Response: None.

Messages and Codes

ESP-5.4-MC-03 25

0167I Mgr Message Received Explanation: System Action: User Response:

0168I xxxx Explanation: System Action: User Response:

0169W SPECIAL DAY xxxx NOT DEFINED IN CALENDAR(S) yyyy zzzz Explanation: A LISTSPEC command was entered, requesting a display of a particular

special day entry. No special days were found with that name. System Action: None. User Response: Ensure that the name is entered correctly.

0170I NO SPECIAL DAYS DEFINED Explanation: A LISTSPEC command was entered, to display the special days. No

special days had been defined. System Action: None. User Response: None.

0171E INVALID EVENT ID, xxxx Explanation: An EVENT identifier was entered which did not conform to the EVENT

naming standard. An EVENT consists of two parts, a prefix and a descriptive name. The prefix is optional and defaults to the current group prefix. If specified, it is separated from the second part of the name by a period. The second part of the name is called the descriptive portion. The prefix consists of between 1-8 alphanumeric characters, the first of which must be alphabetic. The descriptive portion can be up to 16 alphanumeric characters in length. The first character must be alphabetic. In addition, the descriptive portion may contain the underscore character '_'.

System Action: The EVENT name is not accepted. User Response: Enter a valid EVENT name.

0172E EVENT ID PREFIX MISSING, xxxx Explanation: An EVENT name was specified without a prefix. A group prefix was not

set so a default could not be supplied. System Action: The EVENT name is not accepted. User Response: Enter a fully qualified EVENT name.

0173E xxxx not authorized Explanation: The ESP command "xxxx" was not APF authorized. APF authorization is

required when an SVC is not available for subsystem request processing.

System Action: No requests can be performed which require the assistance of the ESP

26 ESP-5.4-MC-03

subsystem. User Response: Ensure that an SVC is available or that the ESP command is APF

authorized.

0174E INVALID END TIME AND DATE SPECIFIED Explanation: When defining a holiday, an end time and date was specified that was

earlier than the start time and date. System Action: The command is ignored. User Response: Respecify the command.

0175E You do not have authority to set the requested {USER|OWNER} field Explanation: A user made an attempt to define an EVENT with the USER or OWNER

keyword specified. The request was not permitted by the security system.

System Action: The EVENT definition request is denied. User Response: Specify a valid USER or OWNER field value. For the USER keyword you

must have READ authority to the RACID.uuuu resource, where "uuuu" is the value of the USER field. For the OWNER keyword you must have READ authority to the SETOWNER.oooo resource, where "oooo" is the value of the OWNER field.

0176W Resfile commands not available from a proxy ESP/WM Explanation: A resource management related command was issued from a proxy ESP/WM

subsystem. System Action: The command is not executed. User Response: Issue this command from a master ESP/WM subsystem.

0177W Resource facility is not initialized Explanation: A resource manager related command was issued to a system where the

resource manager was not initialized. System Action: The command is not executed. User Response: The resource manager needs to be initialized. In the ESP master

system initialization parameter data set, specify the RESFILE parameter. ESP will need to be restarted.

0178E INVALID LOGICAL EXPRESSION Explanation: An IF statement encountered an invalid logical expression. System Action: The statement is not executed. The input stack is flushed. User Response: A logical expression must consist of an expression that returns an

integer result, or must contain a relational operator.

0179W Data set xxxx is partitioned and no members were specified Explanation: A INVOKE statement specified a partitioned data set. The INVOKE

statement must specify a PDS member name. System Action: The statement is ignored. User Response: Specify a member name.

Messages and Codes

ESP-5.4-MC-03 27

0180W STATEMENT INVALID, xxxx ON yyyy HAS ALREADY PASSED Explanation: A SCHEDULE statement specified a date and time that had already

passed, and cycling the definition 64 times did not produce a date and time in the future.

System Action: The schedule statement is ignored. User Response: Respecify the time and date.

0181E MEMBER NAME AND LEVEL OPTION MUTUALLY EXCLUSIVE Explanation: A SUBMIT command specified a member of a PDS as well as the LEVEL

option. They are mutually exclusive. System Action: The SUBMIT statement is ignored. User Response: Respecify the SUBMIT statement. If you wish to use a specific member

as well as the LEVEL option, define two SUBMIT statements.

0182W NO ENTRIES FOUND LEVEL xxxx Explanation: A LIST command was unable to find any EVENTs with the requested high

level string. System Action: None. User Response: Respecify the command with the correct high level string.

0183W NO ACTION STATEMENTS SPECIFIED YET Explanation: An EVENT was defined that contained SCHEDULE statements but no action

statements. Without action statements, an EVENT is meaningless. System Action: If this statement was entered in interactive mode, this message is

followed by message 184I. Otherwise, the EVENT definition is ignored. User Response: Specify one or more action statements.

0184I CONTINUE EVENT DEFINITION WITH AN ACTION STATEMENT OR ENTER 'CANCEL'

Explanation: An EVENT was defined with no actions. This message is issued after message 183W.

System Action: The previous ENDDEF statement is ignored. User Response: If you wish to terminate the EVENT definition, enter 'CANCEL'.

Otherwise you should enter one or more action statements.

0185W EVENT xxxx.yyyy ALREADY EXISTS Explanation: An EVENT definition was entered without the REPLACE option. An EVENT

already exists with that name. System Action: This message is followed by message 186A. User Response: Respond to message 186A.

0186A ENTER NEW NAME, 'REPLACE' OR 'CANCEL' Explanation: An EVENT definition was entered without the REPLACE option. An EVENT

already exists with that name. This message follows message 185W. System Action: The user is prompted for an option. User Response: You may cancel the current definition by entering CANCEL, you may

replace the previous version by entering REPLACE or you may specify a

28 ESP-5.4-MC-03

new name.

0187W USER SUBCOMMAND ONLY VALID IN BATCH Explanation: A USER subcommand was entered from a TSO terminal session. It can

only be issued in a batch environment. System Action: The command is ignored. User Response: You can only use your own userid in a TSO session. The USER command

is therefore unnecessary.

0188E MISSING PASSWORD Explanation: A USER subcommand was specified, but a password omitted. System Action: The command is ignored. ESP will not allow access to the requested

userid. User Response: Specify the correct password.

0189W DATA SET xxxx IS PARTITIONED AND NO MEMBERS WERE SPECIFIED

Explanation: A SUBMIT statement specified a partitioned data set. Neither a LEVEL option or member name were specified.

System Action: The statement is ignored. User Response: Specify a member name or use the LEVEL option.

0191E ABEND code OCCURRED ON data set_name Explanation: The operating system detected an error while processing the named

data set. System Action: Processing for the command is terminated. User Response: Determine the nature of the abend using the abend code shown in

conjunction with any other system messages which may have been issued. Take the appropriate corrective action and re-issue the command.

0192W DATA SET TRIGGER OPTION NOT CURRENTLY ENABLED Explanation: A DSTRIG statement was entered in an EVENT definition. However, the

installation did not enable the data set triggering option. System Action: Data set triggering action will not take effect until the installation

activates data set triggering. User Response: Request your system programmer to specify data set triggering.

0193E GENERIC DATA SET ENTRY MUST BE AT LEAST 8 BYTES LONG Explanation: A DSTRIG statement referred to a data set name by high level generic

string. The minimum generic string length is 8 characters. System Action: The statement is ignored. User Response: Specify at least 8 characters. If the data set name is less than 8

characters long, you will have to specify the name in full.

0194W GENERIC SPECIFICATION NOT ALLOWED ON EVENT NAME PREFIX

Explanation: A LIST LEVEL command specified a level name with asterisks or a hyphen

Messages and Codes

ESP-5.4-MC-03 29

in the event name prefix field. System Action: The command is not executed. User Response: You cannot specify a generic group level.

0195E INCOMPATIBLE DATA SET TYPE SPECIFIED FOR xxxx Explanation: A SUBMIT, PANSUB, or LIBSUB specified an incompatible data set

type. SUBMIT only supports OS or VSAM data sets; PANSUB supports CA-Panvalet data sets; and LIBSUB supports CA-Librarian data sets.

System Action: The command is not executed. User Response: Specify the appropriate command for the data set type.

0196E ACCESS TO ESP SUBSYSTEM DENIED BY SECURITY SYSTEM Explanation: Your userid is not defined as having access to the ESP online system.

You need to be permitted to the ESP online resource with at least the READ access attribute.

System Action: The online session with ESP is denied. User Response: If you require access to ESP, request permission from your security

administrator. If you think you already have access to ESP, check that you attempted to access ESP with the correct userid.

0197E xxxx COMMAND NOT SUPPORTED WITH SAF BASED SECURITY Explanation: A command was issued which was not supported when ESP resources are

controlled by SAF based security. System Action: The command is suppressed. User Response: The command you requested is not supported with SAF. The function you

requested is probably available through a host security based facility.

0198E Invalid template parameters Explanation: System Action: User Response:

0199I EVENT DEFINED, WILL REQUIRE DATA SET TRIGGER Explanation: An Event was defined which contained no explicit time schedule. System Action: None. The Event will only execute as result of a direct trigger or a

data set trigger. User Response: None needed.

0200W UNABLE TO QUEUE DIRECTLY TO SYSTEM xxxx Explanation: An Event was defined or triggered to execute on another system. The

QUEUE data set was unavailable so the local ESP system was unable to queue it to the requested system.

System Action: In the case of a define, if the target system exists, the Event will be added to the schedule at the next database scan.

User Response: Ensure the correct system id was specified. If not, redefine the Event with the correct system id, or use the ALTEVENT command.

30 ESP-5.4-MC-03

0201W SYSTEM xxxx NOT MEMBER OF SHARED QUEUE Explanation: An Event was defined or triggered to execute on another system. The

designated system was not sharing the QUEUE data set. The local ESP system was unable to queue it to the requested system.



0202W Job xxxx(yyyy) overdue in P-Node zzzz Explanation: A job has missed its due out time as specified in the job tracking

definition. xxxx specifies the job name. yyyy specifies the job identifier. zzzz specifies the P-node.

System Action: The DUEOUT installation exit will be invoked. User Response: If necessary, take any needed action to ensure that the job is

processed as soon as possible. This could include increasing the job's priority or resetting its performance group. Installation standards will determine the correct response. You may obtain more information about the due out times by use of the LJ command.

0203E NOT AUTHORIZED FOR HISTORY FILE ACCESS Explanation: A user requested history file data. However, the user entry specified

no history file access string. System Action: The history file access is denied. User Response: If you need access to the history file, request authorization from

your ESP administrator.

0204W NO SYSTEMS FOUND MATCHING xxxx Explanation: An Event was defined with an execution system ID containing wildcard

characters. No systems were found matching the required ID. System Action: The Event will not be picked up for scheduling by any system, but will

need a trigger or data set trigger. User Response: If you made an error in specification, alter or redefine the Event.

0205E NOT AUTHORIZED TO MODIFY CALENDAR xxxx Explanation: You attempted to modify a calendar to which you are not authorized. System Action: The request is denied. User Response: Ensure that you specified the correct calendar. If you require access

to this calendar, request authorization from your ESP administrator.

0206E INSUFFICIENT SPACE LEFT IN CALENDAR xxxx Explanation: During the process of defining a HOLIDAY or SPECIAL DAY ESP could not

allocate enough space in the CALENDAR. System Action: The request is not processed. User Response: Space may be obtained in the CALENDAR by deleting old, unused entries

Messages and Codes

ESP-5.4-MC-03 31

(HOLIDAYs and SPECIAL DAYS). If this is not possible the CALENDAR should be split.

0207E HOLIDAY xxxx NOT FOUND Explanation: A HOLIDAY specified by a user, during CALENDAR processing was not

found. System Action: The request is not processed. User Response: Ensure the holiday name is specified correctly.

0208E SPECIAL DAY ENTRY FOR xxxx NOT FOUND Explanation: A SPECIAL DAY specified by a user, during CALENDAR processing was not

found. System Action: The request is not processed. User Response: Ensure the special day is specified correctly.

0209W EVENT FILE SUSPENDED Explanation: A request was made to access an event file which is currently in

suspended status. System Action: Processing continues. User Response: Contact your ESP administrator to have the event file reopened or

issue the EVENTSET operator command with the OPEN option if you are authorized.

0210E LIBRARY ACCESS DENIED TO USER Explanation: An Event containing a non-supported command was being defined by a non-valid

userid. System Action: The command is ignored. User Response: You must redefine the Event from a valid userid.

0211E INVALID RECORD TYPE DETECTED ON USER DEFINITION DATASET

Explanation: A record in the USERDEF data set contains an invalid type indicator. System Action: The user entry retrieval request will fail. User Response: Notify your software support personnel.

0212E NOT AUTHORIZED TO DELETE/ALTER CALENDAR xxxx Explanation: You attempted to delete or alter a calendar to which you are not

authorized. System Action: The request is denied. User Response: Ensure that you specified the correct calendar. If you require access


0213W NOT AUTHORIZED FOR CALENDAR DEFINE Explanation: You attempted to define a calendar to which you are not authorized. System Action: The request is denied. User Response: Ensure that you specified the correct calendar. If you require access


32 ESP-5.4-MC-03

0214E CALENDAR xxxx ALREADY DEFINED Explanation: An attempt was made to define an already existing CALENDAR. System Action: The request is ignored. User Response: Depends on the cause of the problem. Ensure that the command was

entered correctly.

0215E CALENDAR xxxx NOT DEFINED Explanation: The CALENDAR requested by a user was not found. System Action: The CALENDAR is not processed. User Response: Ensure the calendar name is specified correctly.

0216E USER/GROUP xxxx NOT FOUND Explanation: A GROUP or USER entry specified during CALENDAR processing was not

found. System Action: The request is ignored. User Response: Ensure the GROUP or USER entry is correctly entered.

0217E Command xxxx invalid in Agent Definition Table Explanation: A User Profile Definition Table contained an invalid command. System Action: The User Profile Definition Table is not loaded. User Response: Correct the table and reissue the LOADUPDT command.

0218E xxxx Explanation: A LOADUPDT command encountered an error allocating or opening a User

Profile Definition Table. The preceding message will have described the error.

System Action: The User Profile Definition Table is not loaded. User Response: Ensure the table name was specified correctly and reissue the LOADUPDT

command.

0219E Above error occurred opening Agent Definition Table Explanation: A LOADUPDT command encountered an error allocating or opening a User

Profile Definition Table. The preceding message will have described the error.


command.

0220E DATA SET xxxx IS NOT PARTITIONED Explanation: The COPYJCL parameter specified a non-partitioned data set for the JCL

to be copied to. System Action: The COPYJCL statement is not accepted. User Response: Specify the name of an OS partitioned data set.

0221E COPYJCL DATA SET MUST BE AN OS PARTITIONED DATA SET Explanation: The COPYJCL parameter specified a Librarian or Panvalet

data set as an output data set. Only OS partitioned data sets are

Messages and Codes

ESP-5.4-MC-03 33

supported. System Action: The COPYJCL statement is not accepted. User Response: Specify the name of an OS partitioned data set.

0222I DEFAULT USERID ASSIGNED Explanation: An undefined user accessed the ESP command. A default user had been

defined and the user assigned the attributes of this ID. System Action: The user is permitted access to the system as defined by the default

user ID. User Response: None.

0223E Above error occurred reading Agent Definition Table Explanation: An error occurred while reading in a User Profile Definition Table.

The error is described in a preceding message. System Action: The User Profile Definition Table is not loaded. User Response: After the error is corrected, reissue the LOADUPDT command.

0224E Invalid command syntax detected in line nn of Agent Definition Table Explanation: A User Profile Definition Table contained a statement with invalid

syntax. System Action: The User Profile Definition Table is not loaded. User Response: Correct the table definition and reissue the LOADUPDT command.

0225E Above error occurred on line nn of the Agent Definition data set Explanation: An error was detected in an Agent Definition data set statement. The

error is described in a preceding message. This message indicates the line number containing the error.

System Action: The Agent Definition data set is not loaded. User Response: Correct the error and reissue the LOADAGDF command.

0226W No Distributed Managers defined Explanation: A DMANAGER LIST command was entered to list the current Distributed

Manager topology. There are no known Distributed Managers. System Action: Processing continues. User Response: None.

0227C DM Display Explanation: The current Distributed Manager topology is displayed in response to a

DMANAGER LIST command. System Action: Processing continues. User Response: None.

0228I Workload Object Module Directory not created Explanation: The WOBDEF DISPLAY command was entered to display active workload

object modules. There are no workload object modules currently active.


34 ESP-5.4-MC-03

0229E AGENTRCV xxxx parameter invalid for TCP/IP receiver yyyy Explanation: A parameter valid only for APPC agent receivers was specified in an

"AGENTRCV" command for a TCP/IP receiver. System Action: Processing continues. User Response: None.

0230W SIGNAL xxxx HAS EVENTS PENDING, CANNOT DELETE Explanation: A delete was issued for a signal. The signal had Events waiting for

the signal to be posted. The signal could not therefore be deleted. System Action: The signal is not deleted. User Response: You should not delete a signal that is referenced by an Event. Prior

to deleting the signal, remove all references to it from active Events.

0231W SIGNAL xxxx NOT DEFINED Explanation: A signal name was specified in a delete, alter or display command.

However, the signal could not be found. System Action: The signal is not processed. User Response: Check the spelling of the signal name.

0232W SIGNAL xxxx ALREADY DEFINED Explanation: A signal define command was issued, specifying a name that was already

in use. System Action: The signal is not defined. User Response: Use a unique name. If you wish to redefine the signal, delete it

first.

0233W YOU DO NOT HAVE SUFFICIENT ACCESS TO SIGNAL xxxx Explanation: You are not authorized to perform the requested action against the

named signal(s). System Action: The request is not executed. User Response: None.

0234W GENERATION NUMBER nn NOT PRESENT FOR SIGNAL xxxx Explanation: A SIGPOST command was issued for a particular generation of a signal.

However, the generation requested did not exist. System Action: The SIGPOST is bypassed. User Response: Specify the correct generation number. Use the LISTSIG command to

display the current signal generation count.

0235W SIGNAL xxxx GENERATION nn ALREADY POSTED Explanation: A SIGPOST command was issued against a signal that was already posted. System Action: The SIGPOST is ignored. User Response: Ensure correct generation number was specified.

0236E INSUFFICIENT CHECKPOINT SPACE TO QUEUE REQUEST Explanation: A SIGPOST or SIGCYCLE request could not proceed as there was

Messages and Codes

ESP-5.4-MC-03 35

insufficient space in the checkpoint to queue the request. System Action: The request is ignored. User Response: Retry a little later.

0237W SIGNAL PROCESSOR SUSPENDED DUE TO PRIOR REQUEST Explanation: A SIGSTAT SUSPEND command had been issued. System Action: The signal processor ignores all signal posts and signal waits until

signal processing is RESUMEd. User Response: When signal processing is required, issue the SIGNAL RESUME command.

0238W SIGNAL PROCESSOR QUIESCED DUE TO PRIOR REQUEST Explanation: A SIGSTAT QUIESCE command had been issued. System Action: Signal processing is quiesced, meaning any requests are deferred until

signal processing is RESTARTed. User Response: When you wish to restart signal processing, issue the SIGSTAT RESTART

operator command.

0239E ABOVE ERROR OCCURRED PROCESSING xxxx REQUEST OR SIGNAL yyyy

Explanation: An I/O error on an Event data set occurred while processing a signal post or signal cycle request. This message would have been preceded by an message describing the type of I/O error.

System Action: The request cannot complete. User Response: Depends on the nature of the I/O error.

0240E INVALID SIGNAL REQUEST, CODE xxxx, ENCOUNTERED FOR SIGNAL yyyy

Explanation: A signal request was passed to the signal manager. The request code is displayed in hex.

System Action: The signal request is ignored. User Response: This is probably due to an internal logic error. Notify your software

support personnel.

0241E INVALID SIGNAL NAME xxxx Explanation: An invalid signal name was specified for a SIGWAIT request. System Action: The SIGWAIT is not processed. User Response: Respecify the SIGWAIT. The name should consist of an optional group

name and period, followed by a descriptive name. The group name and period should consist of alphanumeric characters, the first of which should be alphabetic. The maximum length of the group name is 8 characters, while the descriptive name can be up to 16 characters in length.

0242E GENERIC SPECIFICATION NOT ALLOWED IN GROUP NAME FOR SIGCYCLE

Explanation: A SIGCYCLE command was entered with asterisks or hyphens in the group name. This is not allowed. An explicit group name should be specified.

System Action: The SIGPOST is suppressed.

36 ESP-5.4-MC-03

User Response: Respecify the SIGCYCLE with an explicit group name. To cycle several groups of signals, use a SIGCYCLE for each group.

0243E SIGNAL xxxx NOT FOUND Explanation: A SIGPOST or SIGCYCLE was issued by an Event. However, the signal was

not found. System Action: The SIGPOST or SIGCYCLE request is ignored. User Response: The signal should be defined, or the Event changed to identify the

correct signal.

0244E INVALID SIGNAL NAME xxxx Explanation: An invalid signal name was specified for a signal define, delete

alter, display or cycle command. System Action: The command is not processed. User Response: Respecify the signal name. The name should consist of an optional

group name and period, followed by a descriptive name. The group name and period should consist of alphanumeric characters, the first of which should be alphabetic. The maximum length of the group name is 8 characters, while the descriptive name can be up to 16 characters in length. you may use wildcard characters for the descriptive name of a signal in a display or cycle command.

0245E GENERIC SPECIFICATION NOT PERMITTED IN GROUP NAME Explanation: A LISTSIG command was entered and a signal name specified with a '-'

or '*' in the group name. This is not permitted. System Action: The command is not processed. User Response: Reissue the command with an explicit group name. To display several

groups, issue the command once for each group.

0246E INVALID SIGNAL NAME xxxx Explanation: A Signal name was specified incorrectly in a SIGPOST or SIGCYCLE

statement within an Event. The signal name should conform to the same convention as an Event name. Wildcards are allowed in the descriptive portion of the signal name with the SIGCYCLE but not the SIGPOST.

System Action: The Event is not executed. User Response: Correct the spelling of the signal name. The Event will need to be

re-triggered manually.

0247W NO MATCHING EVENTS FOUND Explanation: A signal display request was issued. However, no matching entries were

found. Either no matching names were found, or matching names were found but other requested characteristics were not.

System Action: No entries are displayed. User Response: None.

0248E INSUFFICIENT SPACE TO ENTER PENDING ELEMENT FOR EVENT Explanation: An Event requested a SIGWAIT. However, there was insufficient space in

the signal definition block to store the cross relation information. System Action: The Event is not processed.

Messages and Codes

ESP-5.4-MC-03 37

User Response: The Event should be manually triggered with the FORCE option.

0249E INSUFFICIENT SPACE TO ENTER SIGWAIT ELEMENT FOR EVENT Explanation: An Event requested a SIGWAIT. However, there was insufficient space in

the Event definition block to store the cross relation information. System Action: The Event is not processed. User Response: The Event should be manually triggered with the FORCE option.

0250W SIGNAL xxxx GEN nn NOT FOUND FOR EVENT yyyy, ASSUMED POSTED

Explanation: An Event requested a SIGWAIT for a signal that was no longer defined, or did not contain enough generations.

System Action: The signal is assumed to be posted. User Response: You may wish to redefine the signal or redefine the Event.

0251E INSUFFICIENT SPACE TO ENTER SIGWAIT ELEMENT FOR EVENT xxxx

Explanation: Insufficient space was available in an Event definition block to queue a SIGWAIT request.

System Action: The Event is not processed. User Response: The Event has to be triggered manually. To prevent a recurrence of

this problem, the Event should be edited to reduce its size, or the Event database record length increased.

0252E ABOVE ERROR OCCURRED READING SIGNAL xxxx FOR EVENT yyyy Explanation: An I/O error, documented by the preceding message, occurred while

accessing a signal definition block for an Event. System Action: The Event is not processed. User Response: The Event has to be triggered manually.

0253E FORCE OPTION INVALID, EVENT xxxx HAS NO PENDING EXECUTIONS

Explanation: A trigger command with the FORCE option was used on an Event. However, the Event had no executions pending.

System Action: The trigger command is ignored. User Response: The FORCE option should only be used to force the execution of an

Event that has signals pending.

0254E EVENT xxxx IS NOT PENDING AT SPECIFIED TIME Explanation: A trigger command was specified with the FORCE option for an Event.

Although the Event had an execution pending one or more signals, none of the pending execution or executions matched the user specified time.

System Action: The trigger command is ignored. User Response: Respecify the trigger with the correct time. To force the oldest or

only pending execution, you can omit the time specification.

38 ESP-5.4-MC-03

0256E xxxx Explanation: A severe error occurred while allocating the COPYJCL library. System Action: User Response: CATALOG return codes can be found in the IBM Message manual under the

heading 'IDC3009'.

0257E SIGPNNM STATEMENT MUST BE PRECEDED BY SIGPEND Explanation: An Event was being saved. However, a SIGPNNM statement was found

without a preceding SIGPEND. The SIGPEND statement is necessary to establish the time at which the signal became pending.

System Action: The Event is not stored. In interactive mode, the user is prompted to correct the errors. In non-interactive mode, the definition is cancelled.

User Response: This is probably due to an accidental delete of the SIGPEND during an edit of an Event. The SIGPEND statement should be restored.

0258E INSUFFICIENT CHECKPOINT SPACE TO QUEUE CYCLE/POST REQUEST FOR EVENT xxxx, SIGNAL yyyy

Explanation: An Event performed a SIGPOST/SIGCYCLE request. However, insufficient checkpoint space remained for the request to be queued.

System Action: The request is not processed. User Response: The SIGPOST/SIGCYCLE will have to be done manually.

0259E UNDEFINED HISTORY FILE Explanation: A history file was specified as input to a report. However, the

specified history file has not been defined to ESP. System Action: The report is not produced. User Response: Specify the name of a valid ESP history file. See your ESP

administrator for information about history files. If you wish access to all ESP history files, simply omit the HISTFILE statement.

0260C Agent Display Explanation: System Action: User Response:

0261W No Agents defined Explanation: System Action: User Response:

0262C Agent Receiver display Explanation: System Action: User Response:

Messages and Codes

ESP-5.4-MC-03 39

0263I OK Explanation: System Action: User Response:

0264I OK Explanation: System Action: User Response:

0265I Agent Receiver xxxx halted Explanation: System Action: User Response:

0266I Agent receiver xxxx shutdown requested Explanation: An "AGENTRCV DELETE" command was issued for agent receiver "xxxx". System Action: Agent receiver "xxxx" is shutdown and deleted. User Response: None.

0267I Agent Receiver xxxx restarted Explanation: System Action: User Response:

0268E Missing agent receiver name Explanation: An "AGENTRCV" command that did not specify the "NAME" parameter was

issued. System Action: Processing continues. User Response: To list all agent receivers, enter the following command:

AGENTRCV or AGENTRCV LIST or AGENTRCV DISPLAY Then reissue the original "AGENTRCV" command specifying a valid agent receiver.

0269E Agent xxxx already defined Explanation: An "AGENTRCV NAME(xxxx) DEFINE" command was issued for an agent

receiver "xxxx" that already exists. System Action: Processing continues. User Response: None.

0270E Agent receiver xxxx not defined Explanation: An "AGENTRCV NAME(xxxx)" or "AGENTRCV AGENTRECEIVER(xxxx)"

command specified an agent receiver "xxxx" that does not exist.

System Action: Processing continues.

40 ESP-5.4-MC-03

User Response: To list all agent receivers, enter the following command: AGENTRCV or AGENTRCV LIST or AGENTRCV DISPLAY Then reissue the original "AGENTRCV" command specifying a valid agent receiver.

0271E PORT, SYMDEST or LU/TPNAME/LOGMODE missing for Agent Receiver xxxx

Explanation: An "AGENTRCV" command was issued with a required TCP/IP or APPC parameter(s) missing.

System Action: Processing continues. User Response: Issue the "AGENTRCV" command with the required TCP/IP (PORT) or APPC

(LU and TPNAME or SYMDEST) parameter(s) specified.

0272W Requested generation of Appl <application_name> not found Explanation: The generation specified in APPLJOB command could not be found. System Action: APPLJOB command rejected. User Response: Re-issue AJ command with valid generation number.

0273E INVALID OPERATION CODE SPECIFIED TO XI005 Explanation: An internal ESP error has occurred. System Action: The operation code is ignored. User Response: Please contact Cybermation for further assistance.

0274E ERROR OPENING DATA SET xxxx, OPEN ERROR CODE nn Explanation: An error during OPEN prevented the access to a VSAM data set. System Action: A message will follow describing the action taken. User Response: Look up the error code in the VSAM Programmer's Guide.

0275E PUT UPDATE PERFORMED OUT OF CONTEXT Explanation: A PUT for update was performed without a preceding get for update.

This is probably a logic error. System Action: The update request is ignored. User Response: Notify your software support personnel.

0276E VSAM xxxx ERROR CODE nn ON DATA SET yyyy Explanation: A logical error occurred while processing a request on a VSAM data set. System Action: Depends on the data set. A message will follow indicating the action

taken. User Response: Look up the error code in the VSAM Programmer's Guide.

0277E INSUFFICIENT SPACE TO ADD DATA TO DATA SET xxxx (gggggg) Explanation: A VSAM request failed due to insufficient space. 'gggggg' is function

being performed. System Action: The output or update request is not processed. This message will be

followed by another message indicating the action taken. User Response: The data set may need to be reorganized, or loaded into a larger

Messages and Codes

ESP-5.4-MC-03 41

data set.

0278E RECORD KEY 'xxxx' NOT FOUND IN DATA SET yyyy (gggggg) Explanation: This error occurred while processing a request on a VSAM data set.

'gggggg' is function being performed. System Action: The request is terminated. User Response: Check any following messages to get more information.

0279E RECORD KEY X'xxxx' NOT FOUND IN DATA SET yyyy (gggggg) Explanation: This error occurred while processing a request on a VSAM data set.

'gggggg' is function being performed. System Action: The request is terminated. User Response: Check any following messages to get more information.

0280E I/O ERROR ON xxxx(gggggg),yyyyzzzzaaaabbbbccccddddeeeeffff Explanation: A physical error occurred while processing a request on a VSAM data

set. 'gggggg' is function being performed. System Action: Depends on the data set. A message will follow indicating the action

taken. User Response: Take action based on the succeeding messages.

0281I Delay interval set to nn minute(s) Explanation: A DELAYINT command was issued. The response lists the amount of time

in minutes an Event will be delayed if contention is encountered or a data set is migrated. If the data set is offline, the delay interval is twice the value displayed.


0282E Not authorized to set security ID xxxx Explanation: While defining or updating an Event, a request was made to use userid

"xxxx" as the userid under which workload from the Event should be processed. The userid attempting to define or modify the Event does not have sufficient authority to assign userid "xxxx" as the security ID.

System Action: Event definition or modification is terminated without the Event being defined or updated.

User Response: If SAF processing is active, ensure the userid trying to define or modify the Event has READ access to the resource "prefix.RACID.xxxx". If SAF processing is inactive, the user must have the SPECIAL attribute.

0283E Not authorized to Event owner xxxx Explanation: While defining or updating an Event, a request was made to use userid

"xxxx" as the owner of the Event. The userid attempting to define or modify the Event does not have sufficient authority to assign userid "xxxx" as the owner.

System Action: Event definition or modification is terminated without the Event being defined or updated.

42 ESP-5.4-MC-03

User Response: If SAF processing is active, ensure the userid trying to define or modify the Event has READ access to the resource "prefix.SETOWNER.xxxx". If SAF processing is inactive, the user must have the SPECIAL or ANY attribute.

0284E Generic DSNAME invalid when member specified Explanation: ESP encountered a DSNAME application statement for a DSTRIG workload

object that specifies a generic data set name and a PDS member name. System Action: Generation of the application fails. User Response: Specify a discreet data set name or remove the PDS member name from

the DSNAME application statement.

0285E Generic DSNAME invalid when member specified Explanation: ESP encountered a DSTRIG event command that specifies a generic data

set name and a PDS member name. System Action: The ESP event is suppressed. User Response: Specify a discreet data set name or remove the PDS member name from

the DSTRIG event command.

0286E DSNAME member invalid for implicit data set trigger Explanation: ESP encountered a DSTRIG event command that specifies a data set name

that includes a PDS member name. A PDS member name is not permitted for an implicit data set trigger.

System Action: The ESP event is suppressed. User Response: Remove the PDS member name from the data set name specification of the

DSTRIG event command.

0287W xxxx not enabled, not authorized for CPU Explanation: ESP Workload Manager optional feature xxxx is installed but is not

authorized for the local CPU. System Action: The optional feature is not enabled. User Response: If the optional feature should be authorized for the local CPE, then

contact Cybermation support. If the optional feature is not meant to be authorized, then this message can be ignored.

0288I xxx Checkpointed and yyy uncheckpointed messages flushed Explanation: The indicated number of messages were flushed from one or more agent

queues as the result of an AGENT FLUSH command. System Action: None. User Response: None.

0289E Agent MPL level must range from 1 to 50 Explanation: The valid range of values that can be specified on the AGENTMPL

command is from 1 to 50. System Action: The command is not processed. User Response: Specify a valid number on the AGENTMPL command.

Messages and Codes

ESP-5.4-MC-03 43

0290E ALESERV ADD failed, RC=X'nnnn' Explanation: The user has requested a CSF function. The ALESERV function required

to establish the environment necessary to process the CSF function failed with return code 'nnnn'.

System Action: The request is ignored. User Response: Re-issue the CSF request. If the problem persists, contact

Cybermation.

0291E Filter interpreter load failed, RC=X'nnnn' Explanation: The user has requested a CSF function. The filter interpreter

(CYBXPI04) required to process the request could not be loaded. The load failed with return code 'nnnn'.

System Action: The request is ignored. User Response: Correct the problem indicated by the return code 'nnnn'. The return

codes are identical to those return codes for a system abend 806.

0292E The scoreboard is not active Explanation: The user has requested a CSF function. The scoreboard is not

currently active. System Action: The request is ignored. User Response: Ensure the ESP subsystem specified is active and that the scoreboard

facility is available.

0293E Scoreboard request not valid from a proxy subsystem Explanation: The user has requested a CSF function from a proxy subsystem. System Action: The request is ignored. User Response: Re-issue the request from a master system. Scoreboard API requests

can only be made from the master system in a master/proxy complex.

0294E ALESERV DELETE failed, RC=X'nnnn' Explanation: The user has requested a CSF function. The ALESERV function required

to delete the environment after processing the CSF function failed with return code 'nnnn'. Future CSF requests may encounter problems.

System Action: Processing continues. User Response: Re-issue the CSF request. If the problem persists, contact

Cybermation.

0295E Error retrieving scoreboard data, CMPC=X'sssuuu' Explanation: The user has requested a CSF function to retrieve data. The function

encountered an abend. If non-zero, 'sss' is the system abend code encountered. Otherwise, 'uuu' is the user abend encountered.

System Action: The requested is terminated. A record of the error is made in the system's recording data set (LOGREC).

User Response: Re-issue the CSF request. If the problem persists, contact Cybermation.

44 ESP-5.4-MC-03

0296E Error retrieving device list for xxxx, RC=X'yyyy', SC=X'zzzz' Explanation: A RESDEF statement specified "DEVICE(xxxx)". While attempting to

retrieve the UCB addresses associated with the device "xxxx", the EDTINFO service failed with return code "yyyy" and reason code "zzzz".

System Action: The device "xxxx" is not added to the definition for the associated RESDEF.

User Response: Contact your system programmer and provide the return code and reason code.

0297E Error retrieving UCB X'xxxx', RC=X'yyyy', SC=X'zzzz' Explanation: A RESDEF statement specified "DEVICE". While attempting to retrieve

the UCB associated with the device "xxxx", the UCBLOOK service failed with return code "yyyy" and reason code "zzzz".

System Action: The device at address "xxxx" is considered unavailable during allocation of the associated Resource.

User Response: Contact your system programmer and provide the return code and reason code.

0298I Agent MPL is set to nn, current usage is nn Explanation: The agent maximum MultiProcessing Level is currently set to nn.

The highest number used so far is nn. System Action: None. User Response: None.

0299W Agent xxx could not be quiesced, no checkpoint space Explanation: A request was issued by the user to quiesce agent xxx. No space

was available on the checkpoint. System Action: The agent is not quiesced. User Response: Investigate why no space is available on the checkpoint.

0300I nn Agents quiesced|restarted Explanation: nn Agents were quiesced or restarted as the result of an

AGENT xxx QUIESCE|RESTART command. System Action: None. User Response: None.

0301E Invalid string/value xxxx Explanation: A filter statement contained a term that was invalid. Valid terms

are variable names, a numeric value or a character literal string. System Action: The statement cannot be compiled. User Response: Correct the string. A variable name consists of an alphabetic character

followed by zero or more alphanumerics. A numeric value consists of 1 or more decimal digits. A character literal string consists of one or more characters enclosed within a pair of single or double quotes.

0302E Variable name xxxx not found Explanation: A filter statement contained a variable name that did not correspond

Messages and Codes

ESP-5.4-MC-03 45

to a valid field name. System Action: The statement cannot be compiled. User Response: Correct the string. The field name may be misspelled, or you may have

omitted to put a literal value in quotes.

0303E Invalid subfield value xxxx Explanation: A filter statement contained a term consisting of a variable followed

by a substring specifier. The substring specifier was invalid. System Action: The statement cannot be compiled. User Response: Correct the substring field.

0304E Too many subfields in specified, xxxxyyyy Explanation: A variable in a filter statement has a substring specifier that has

more than 2 subfields. System Action: The statement cannot be compiled. User Response: Correct the subfield. You have probably forgotten a closing

parenthesis.

0305E Invalid expression syntax in filter statement Explanation: An unrecognized term was encountered in a filter statement.

A filter statement can contain the name of field variables, decimal values or string literals with optional relational operators.

System Action: The filter statement cannot be compiled. User Response: Correct the filter expression.

0307S INSUFFICIENT SPACE TO REBUILD THE QUEUE DATASET Explanation: The QUEUE data set was being rebuilt, probably due to the install of a

new release of ESP. Insufficient space exists in the queue data set to perform the rebuild function. This may be due to the new control blocks being larger than before.

System Action: ESP follows this message with a 0097 user abend. User Response: Notify your software support personnel. ESP can be restarted with the

QFORM parameter. This will destroy the ESP job queue information, but will allow the new release to continue execution. Alternatively, because the queue data set has not been written back, the prior release of ESP could be restarted.

0308W QUEUE DATASET xxxx IS CORRECTLY FORMATTED Explanation: A format start was requested using a queue data set that was correctly

formatted. Since it is correctly formatted, a warm start may be possible. ESP is confirming that a format start is really required, and not inadvertently specified.

System Action: ESP follows by issuing message 309A. User Response: Respond to message 309A.

0309A CONFIRM REQUEST FOR QUEUE DATASET FORMAT, REPLY 'Y' OR 'N'

Explanation: ESP is requesting confirmation that a format of the queue is really required.

46 ESP-5.4-MC-03

System Action: ESP waits for the reply. If a Y is entered, ESP proceeds with to format the queue data set. If the reply is N, ESP proceeds with a warm start.

User Response: If you wish to proceed with the format start, enter Y. Otherwise enter N and ESP will attempt a warm start.

0310I WARM QUEUE START WILL BE ATTEMPTED Explanation: ESP is attempting a warm queue data set start after the operator

entered a reply of N to the message 309A. System Action: None. User Response: ESP will attempt a warm queue data set start.

0312W INVALID QUEUE DATASET FORMAT ON xxxx Explanation: A warm queue start was requested. However, the queue data set does not

have a valid format. System Action: This messages followed by message 313. User Response: If you wish to proceed with the format start, enter Y. Otherwise

enter N and ESP will terminate.

0313A ENTER 'Y' TO PROCEED WITH QUEUE FORMAT OR REPLY 'N' Explanation: This message requests confirmation that you wish to proceed with the

formatting of the queue data set. System Action: ESP waits for your response. If you answer Y, the format is performed.

Otherwise, a warm start is attempted. User Response: Enter Y if you wish to proceed with the format.

0314E xxxx Explanation: An error occurred processing the queue data set. The text of the

message fully describes the problem. System Action: This message is followed by message 0317S. User Response: Respond to the message that follows.

0315W INVALID RESPONSE Explanation: An invalid response was given to message 0309A. System Action: The prompt is reissued. User Response: Respond to the reprompt.

0317S QUEUE DATASET UNUSABLE Explanation: This message follows another message describing an error on the

queue data set. System Action: Processing terminates. User Response: The previous message described an error condition. After the problem

is corrected, ESP can be restarted.

0320S QUEUE DATASET NOT DEFINED Explanation: A queue data set was not specified on an ESP startup. System Action: Processing terminates. User Response: Define a queue data set by use of the QUEUE parameter in the ESPPARM

Messages and Codes

ESP-5.4-MC-03 47

file.

0321E DSNAME member invalid for implicit data set trigger Explanation: ESP encountered a DSNAME application statement for a DSTRIG workload

object that specifies a data set name that includes a PDS member name. A PDS member name is not permitted for an implicit data set trigger.

System Action: Generation of the application fails. User Response: Remove the PDS member name from the data set name specification of the

DSNAME application statement.

0323W QUEUE DATASET IS DOWNLEVEL, FORMAT REQUIRED Explanation: A WARM start was attempted when bringing up a new release of ESP. The

new release uses a queue of slightly different format, and therefore a format start is required.

System Action: This message is followed by message 313. User Response: Respond to message 313.

0324E MANAGER already defined Explanation: During the processing of a LOADAGDF command, multiple MANAGER

statements were encountered. Only one MANAGER statement is allowed when defining the Distributed Manager and Agent topology.

System Action: The LOADAGDF statement is terminated. The new topology is not implemented.

User Response: Remove the extra MANAGER statement and re-enter the LOADAGDF command.

0325E No xxxx type MANAGER defined{, DM=yyyy|, Agent=zzzz} Explanation: During the processing of a LOADAGDF command,

a Distributed Manager named 'yyyy' or an Agent name 'zzzz' of communication type 'xxxx' (where 'xxxx' can be APPC or TCP/IP) was encountered. There is no MANAGER statement which defines a Central Manager communication type of 'xxxx'.


User Response: Add the appropriate communication type to the MANAGER statement and re-enter the LOADAGDF command.

0326E Duplicate node name encountered: nnnn Explanation: During the processing of a LOADAGDF command, a duplicate ESP node

name was encountered. ESP nodes are: central manager, distributed managers and agents. Each node must have a unique name.

System Action: The LOADAGDF command is terminated. The new topology is not implemented.

User Response: Correct the duplicate name and re-enter the LOADAGDF command.

0327E Comm type APPC or TCPIP must be specified, {DM=xxxx|AGENT=yyyy} Explanation: During the processing of a LOADAGDF command, a Distributed Manager

named 'xxxx' or Agent name 'yyyy' was encountered without a communication type. Every Distributed Manager and Agent must specify a communication type of APPC or TCPIP.

48 ESP-5.4-MC-03


User Response: Add the communication type to the appropriate statement and re-enter the LOADAGDF command.

0328E xxxx must be specified for yyyy{, DM=zzzz|, Agent=aaaa} Explanation: During the processing of a LOADAGDF command, a Distributed Manager

named 'zzzz' or Agent name 'aaaa' was encountered which contained an incomplete definition. Keyword 'yyyy' demands keyword 'xxxx' also be specified in the definition.


User Response: Correct the definition and re-enter the LOADAGDF command.

0329E xxxx cannot be specified with yyyy{, DM=zzzz|, Agent=aaaa} Explanation: During the processing of a LOADAGDF command, a Distributed Manager

named 'zzzz' or Agent name 'aaaa' was encountered which contained an inconsistent definition. Keyword 'yyyy' demands keyword 'xxxx' not specified in the definition.


User Response: Correct the definition and re-enter the LOADAGDF command.

0330W TRACK MODEL xxxx NOT FOUND FOR JOB yyyy(nn) Explanation: A job tracking model specified for a job was not located. System Action: No tracking or history recording will be performed for that job. User Response: The job model may have been accidentally deleted. The job model should

be redefined.

0331E JOB INDEX ERROR CAUSING POSSIBLE LOSS OF TRACKING DATA FOR JOB xxxx(nn)

Explanation: An I/O error on the job index data set, described by a preceding message, has occurred.

System Action: No tracking or history recording will be performed for the indicated job.

User Response: Notify your software support personnel. If the errors persist, quiesce the tracking option with the JOBTRACK QUIESCE command until the error on the job index data set is corrected.

0332E TRAKFILE error causing possible loss of tracking data for job xxxx(yyyy)

Explanation: An I/O error on the job tracking file, described by a preceding message, has occurred. xxxx specifies the job name. yyyy specifies the job identifier.

System Action: Some tracking data may be lost for the specified job. Processing continues.

User Response: Notify your software support personnel. If the errors persist, quiesce

Messages and Codes

ESP-5.4-MC-03 49

the tracking option with the TRACKING NOSTORE command until the error on the tracking file is corrected.

0333E P-NODE xxxx NOT FOUND FOR JOB yyyy Explanation: A job was to be posted to a p-node but the required p-node definition

could not be found. System Action: The job will not be posted to the p-node and will skip to the next

one, if any, or marked complete. User Response: Notify your software support personnel. The p-node may have been

deleted by accident, or the job model definition may be out of date.

0334E ERROR OCCURRED READING P-NODE ENTRY FOR JOB xxxx Explanation: A job was to be posted to a P-node but the required P-node definition

could not be read in. An I/O error occurred on the job index. This I/O error is described by a preceding message.

System Action: Some display commands may not reflect the job as waiting on the P-node.

User Response: Notify your software support personnel.

0335E INSUFFICIENT CHECKPOINT SPACE TO POST JOB xxxx Explanation: A job was to be posted to a P-node but insufficient checkpoint space

was available to queue the request. System Action: Some display commands may not reflect the job as waiting on the

P-node. User Response: Notify your software support personnel.

0336E INSUFFICIENT QUEUE SPACE TO QUEUE JOB xxxx TO P-NODE yyyy Explanation: A job was to be posted to a P-node but insufficient queue data set

space was available to build a queue entry. System Action: Some display commands may not reflect the job as waiting on the

P-node. User Response: Notify your software support personnel.

0337E ERROR OCCURRED READING/WRITING STEP RECORD FOR JOB xxxx

Explanation: A job tracking record was being updated at step termination time when an I/O error occurred on the track file. The error will have been described by a preceding message.

System Action: The step information for the job will not be updated. However, if no other I/O error occur, the job summary data should still be correct.


0338E ERROR OCCURRED READING/WRITING END RECORD FOR JOB xxxx

Explanation: A job tracking record was being updated at job termination time when an I/O error occurred on the track file. The error will have been described by a preceding message.

System Action: The tracking information for the job will not be updated.

50 ESP-5.4-MC-03


0339E ERROR OCCURRED FREEING TRACKFILE SLOTS FOR JOB xxxx Explanation: The tracking data set slots occupied by a job were being marked as

available at job completion time when an I/O error occurred on the track file. The error will have been described by a preceding message.

System Action: The trackfile slots may not be marked as available. User Response: Notify your software support personnel.

0340E ERROR OCCURRED UPDATING P-NODE DATA FOR JOB xxxx Explanation: A job tracking record's P-node data was being updated at job

termination time or at job purge when an I/O error occurred on the track file. The error will have been described by a preceding message.

System Action: The tracking information for the job will not be updated. User Response: Notify your software support personnel.

0341E JOB xxxx NOT DESTINED FOR P-NODE yyyy Explanation: A job was posted to a p-node that was not defined in its job model. System Action: The job is not posted to the p-node. Some tracking data for the job

may be invalid. User Response: Notify your software support personnel. This would in most cases

indicate a logic error.

0342W Job xxxx(yyyy) not being tracked Explanation: A post command was issued specifying a job number that did not belong

to a job being tracked by ESP. xxxx specifies the job name. yyyy specifies the job identifier.

System Action: The post request is not processed. User Response: Specify the correct job number.

0343W P-NODE xxxx NOT FOUND Explanation: A DFPNODE command was issued specifying a P-node that was not found on

the queue data set. System Action: The command is not processed. User Response: Specify the correct P-node name.

0344W Job xxxx(yyyy) not queued to P-Node zzzz Explanation: A POST command was issued against a job for a p-node to which it was

not currently queued. xxxx specifies the job name. yyyy specifies the job identifier. zzzz specifies the P-Node.

System Action: The POST request is not processed.

Messages and Codes

ESP-5.4-MC-03 51

User Response: Specify the correct P-node name. If the job is destined for the P-node, but not currently queued to it, you can use the FORCE keyword.

0345W Job xxxx(yyyy) not destined for P-Node zzzz Explanation: A POST command was issued against a job for a P-node which was not in

the job's model definition. xxxx specifies the job name. yyyy specifies the job identifier. zzzz specifies the P-node.

System Action: The POST request is not processed. User Response: Specify the correct P-node name.

0346W nn JOBS QUEUED TO xxxx, USE JOB NUMBER Explanation: A post command was issued using a job name rather than a job number.

However, more than 1 job with the same name was queued to that p-node. System Action: The post request is not processed. User Response: Respecify the command using a job number rather than job name.

0347W INSUFFICIENT CHECKPOINT SPACE TO QUEUE POST REQUEST Explanation: A post command was issued for a job, but the checkpoint data set was

full and the request could not be queued. System Action: The post request is not processed. User Response: Reissue the command a little later.

0349E USER xxxx NOT AUTHORIZED FOR JOB POST FUNCTION Explanation: A post command was issued by a user that did not have the scheduler

attribute, was not given controlling authority of a p-node and did not have a job authorization table entry.

System Action: The post request is not processed. User Response: Consult your installation ESP administrator.

0350E INVALID REQUEST CODE DETECTED Explanation: The job tracking request processor was passed an invalid request code.

This would normally only happen due to a logic error. System Action: The request is not processed. User Response: Notify your software support personnel.

0351W NO SPACE LEFT IN PREFIX BLOCK Explanation: A DEFTJ command was issued to define a tracked job prefix entry, but

no space was left in the prefix block. System Action: The request is not processed. User Response: Notify your software support personnel. Some unused job prefixes could

be deleted, or the maximum record length on the job index should be increased.

52 ESP-5.4-MC-03

0352E AGENTRCV keyword xxxx specification missing Explanation: An AGENTRCV keyword parameter was specified without a value enclosed

in parentheses. System Action: Processing continues. User Response: Re-enter the AGENTRCV command specifying "xxxx(yyyy)" instead of

"xxxx".

0353W TRACKING FACILITY NOT ACTIVE Explanation: A user or operator entered a command that was part of the tracking

facility. The tracking facility was not active. System Action: The request is not processed. User Response: The tracking facility may be inactive because the appropriate

parameters were not specified in the initialization parameter file, or due to an error during initialization. If you are in doubt, ask your installation support personnel.

0354E AGENTRCV SET specification(s) missing Explanation: An "AGENTRCV SET" command was issued without specifying what to set. System Action: Processing continues. User Response: Specify something to set in the "AGENTRCV SET" command. For example:

"PORT(nnnn)" for a TCP/IP receiver, "LU(xxxx) TPNAME(yyyy)" or "SYMDEST(xxxx)" for an APPC receiver.

0355E INVALID P-NODE BLOCK GENERATED Explanation: A DEFPN command built a p-node block which did not pass the request

processor validity check. System Action: The request is not processed. User Response: Notify your software support personnel. This is likely a logic error.

0356W NOT AUTHORIZED TO P-NODE xxxx Explanation: A DFPNODE or POST command specified a P-NODE to whom the user or

console was not authorized. System Action: The request is denied. User Response: The console or user should be added to the authorized list for the

p-node through the DEFPN command.

0357W NO SPACE IN USERDEF ENTRY FOR DEFAULT PNODE Explanation: A DFPNODE command was used to set a default p-node for a user or

system console. However, there was insufficient space to add the information.

System Action: The request is not processed. User Response: The logical record length on the USERDEF data set should be increased.

0358W xxxx NOT DEFINED TO ESP Explanation: The console or TSO user issuing a request to ESP was not defined in

the user definition data set. System Action: The request is not processed.

Messages and Codes

ESP-5.4-MC-03 53

User Response: Request that your userid or console be defined by your installation ESP administrator.

0359W JOB NOT ON TRACK FILE Explanation: A job display request was issued by a user or system console operator.

However, the job requested was no longer on the tracking file as the space was reallocated to another job.

System Action: The request is not processed. User Response: None.

0360W JOB xxxx ANCESTOR nn NOT ON INDEX FILE Explanation: A job display request was issued by a user or system console operator,

specifying a job name and optional ancestor number was not found in the index file. This may be because the ancestor number is greater than the maximum index count for the job, or that the job was not tracked by ESP.

System Action: The request is not processed. User Response: None.

0361W JOB xxxx NOT BEING TRACKED Explanation: A job display request was issued by a user or system console operator,

specifying a job name rather than job number. The job could not be found in the index file, as it was not being tracked by ESP.

System Action: The request is not processed. User Response: If you wish the job to be tracked, enter a tracking definition for the

job.

0362E HISTFILE xxxx NOT FOUND OR IS CLOSED FOR JOB yyyy(nn) Explanation: At the completion of a job, ESP attempted to write a history file

record. However, the history file with the I.D. hhhhh could not be found, or was currently closed.

System Action: The history record is not written. Historical information is still available on the tracking file.

User Response: Check that the history file identified in the message is defined to ESP. You can use the LISTHIST operator command to find the current status of all history files currently defined. If the history file is defined, but is currently closed, use the OPEN option of the HISTFILE command to reopen it.

0363E Above error occurred writing HISTFILE record for job xxxx(nnn) Explanation: An I/O error occurred when the tracking manager attempted to write

the history record for the named job. This message is preceded by a message describing the actual error.

System Action: Processing continues, but the history information is lost. User Response: Investigate the cause of the error, and take appropriate action.

0364E UNABLE TO RECEIVE INTER SYSTEM TRACKING DATA, READ ERROR nn

Explanation: An error occurred when trying to receive inter system tracking data

54 ESP-5.4-MC-03

via NJE. The return code from the sysout interface was nn. System Action: The NJE receiver shuts down. User Response: Probable system error.

0365E Wrong Job in JTR: Expected xxxx(nn), found yyyy(mm) Explanation: The tracking manager read a JTR from the tracking file, expecting

it to be for job xxxx with job number nn. But the job name in the record did not match.

System Action: The conditon is treated as an I/O error. Processing of the XME is discontinued

User Response: None.

0366E Invalid Request Block passed to xxxx Explanation: During internal processing, an invalid request block was passed to DM

formatting services. System Action: The current action is terminated. The current action is typically the

generation of an Application or the insertion of an object into an Application.

User Response: This is an internal processing logic error. Please contact Cybermation technical support.

0367E Inconsistent parameters passed to xxxx (nn) Explanation: During internal processing, invalid of missing parameters were passed

to DM formatting services. "nn" is a code which indicates the source of the inconsistency.

System Action: The current action is terminated. The current action is typically the generation of an Application or the insertion of an object into an Application.


0368E Invalid request code passed to xxxx, RQ=nn Explanation: During internal processing, an invalid request code was passed

to DM formatting services. "nn" is the invalid code. System Action: The current action is terminated. The current action is typically the

generation of an Application or the insertion of an object into an Application.


0369E xxxx parameter invalid for AGENTRCV yyyy Explanation: An "AGENTRCV" command was issued with an invalid parameter. System Action: Processing continues. User Response: Issue the "AGENTRCV" without the invalid parameter.

0370E INSUFFICIENT QUEUE SPACE FOR SYSTEM ID RECORD Explanation: During initialization, a system identification record was to be placed

in the QUEUE data set. However, the queue data set had insufficient space.

Messages and Codes

ESP-5.4-MC-03 55

System Action: The system identification record is not built. One will be built on a subsequent subsystem restart if space becomes available. Meanwhile, other systems sharing the QUEUE data set will be unaware of the current system's existence.

User Response: Restart ESP after a short interval.

0371E INSUFFICIENT CHECKPOINT SPACE TO QUEUE EVENT xxxx.yyyy Explanation: Another ESP subsystem requested an Event be queued to the current

subsystem, but insufficient checkpoint space was available. System Action: The Event is not added to the schedule. It will be picked up at the

next schedule scan. User Response: Notify your software support personnel.

0372E EVENT DATASET ID xxxx NOT FOUND FOR EVENT yyyy.zzzz Explanation: Another ESP subsystem requested an Event be queued to the current

subsystem, but the requested Event data set was not found in the target system.

System Action: The Event is not added to the schedule. User Response: Notify your software support personnel. The Event data set definitions

for shared systems must be identical.

0373W P-NODE xxxx NOT DELETED, QUEUE NOT EMPTY Explanation: A DELPN command was issued to delete a P-NODE definition. However,

there were one or more jobs queued to the p-node. System Action: The p-node is not deleted. User Response: Respecify the command once the jobs have been posted out of the

p-node.

0374W YOU ARE NOT AUTHORIZED FOR THE REQUESTED FUNCTION Explanation: A user attempted to define, alter or delete a track model, P-node or

job definition. The user did not have access authority to the specified entry, or there was a syntax error in job definition.

System Action: The request is denied. User Response: To define a track model, job or P-node, your userid must have the

Scheduler authority. To delete or alter an existing definition, your userid must match the ownership string of the entry. Also, check your job definition entry for syntax errors and correct them, if needed.

0375W QUEUE DATASET NOT OPEN Explanation: An LSYS command was issued. However, the QUEUE data set, which

contains the system information, was not open. System Action: The requested data is not displayed. User Response: The QUEUE data set must be defined in the initialization parameter

file.

0376E INVALID P-NODE NAME xxxx Explanation: A DEFTM command was issued which contained an invalid P-node name. System Action: The track model is not defined or replaced.

56 ESP-5.4-MC-03

User Response: Reenter the command specifying a correct P-node name.

0377E INVALID P-NODE/DUE OUT TIME SYNTAX xxxx Explanation: A DEFTM command was issued which contained an invalid P-node name or

due out time specification. System Action: The track model is not defined or replaced. User Response: Reenter the command specifying a correct P-node name and optional due

out time.

0378I Agent receiver xxxx listening on port nn Explanation: An agent receiver is waiting on the specified TCP port for incoming

client connection requests. System Action: Processing continues. User Response: None.

0379I Halting agent receiver xxxx due to TCP/IP error Explanation: An agent receiver TCP/IP error occurred. System Action: The agent receiver is halted. User Response: Correct the problem that caused the TCP/IP error.

Then restart the agent receiver with the following command: AGENTRCV RESTART AGENT(xxxx)

0380E INVALID SYMBOL TABLE RECORD GENERATED Explanation: In response to a DEFSYML command, an invalid control block was

generated. System Action: The DEFSYML command is not processed. User Response: This is most likely a logic error. Notify your software support

personnel.

0381W SYMLIB xxxx ALREADY EXISTS Explanation: A SYMLIB was defined with the same name as an already existing SYMLIB.

The REPLACE option was not specified. System Action: The new SYMLIB definition is not accepted. User Response: If you wish to replace the definition, use the REPLACE option.

0382W SYMLIB xxxx NOT FOUND Explanation: The specified SYMLIB definition was not found in response to a display

or delete command. System Action: The SYMLIB definition is not displayed or deleted. User Response: Re-enter the command specifying the correct name.

0383E SYMLIB xxxx DEFINITION TOO LARGE Explanation: The specified SYMLIB definition contained too many elements, and would

not fit in a database record. System Action: The SYMLIB definition is not added. User Response: The MAXLRECL initialization parameter should be increased to

accommodate larger records.

Messages and Codes

ESP-5.4-MC-03 57

0384E SUBSYSTEM REQUEST ERROR CODE nn FOR JOB STATUS Explanation: A STATUS request to the Job Entry Subsystem failed during the course

of a job queue verification scan. System Action: The verification scan is aborted. It will be retried later. User Response: If this problem persists, it could be due to a logic error in the

program, or an error in the job entry subsystem.

0385I WAITING FOR JOB ENTRY SUBSYSTEM RESTART Explanation: The job entry subsystem was down when the queue verification processor

issued a status subsystem request. System Action: The queue verification processor waits 5 minutes and retries. User Response: Ensure the job entry subsystem is restarted.

0386I QUEUE UPDATE PROCESSOR WAITING FOR CHECKPOINT SPACE Explanation: The job queue update processor needed space for an internal post

element. However, the checkpoint was full. System Action: The queue update processor waits 2 minutes and retries. User Response: None

0387I JOB xxxx(yyyy) AUTOPOSTED FROM INPUT Explanation: At initialization or as the result of a QUPDATE command, ESP detected

that the job queue status of the identified job had not been updated, and that a mismatch existed between the JES status and the ESP status. In this case, the job is on the ESP input queue but not on the JES input queue. This could happen at any time where ESP had not received an explicit notification of job start, job end or purge. This situation can arise when jobs are active when the system is brought down or crashes, or if ESP is down for an extended period.

System Action: The job is moved to the appropriate queue. The job is posted with a post id of 'SYSTEM!' to indicate that the post was not a normal post and that some data might be missing or inaccurate (e.g. time on queue etc.).


0388E JOB INDEX DATASET REQUIRED FOR SCHEDULED ACTIVITY DATABASE UPDATE

Explanation: A scheduled activity database update run was requested. However, a jobindex data set was not available.

System Action: The jobindex data set is required for the scheduled activity database update.

User Response: Ensure a jobindex data set is available. Check the ESP initialization parameter data set.

0389E AGENTRCV xxxx invalid at initialization time Explanation: An AGENTRCV command was entered with an option that is invalid while

ESP is initializing. System Action: ESP issues a prompt to the operator console for either a new command,

"CANCEL" to terminate ESP, or "END" to ignore the command and continue

58 ESP-5.4-MC-03

processing. User Response: Respond to the above console prompt.

Remove erroneous "AGENTRCV xxxx" command from ESPPARM data set.

0390E DATASET xxxx PARTITIONED BUT NO MEMBER SPECIFIED Explanation: A member name must be specified with this partitioned data set. System Action: The requested function was not completed. User Response: Add a member name and try again.

0391E GENERIC DATA SET ENTRY MUST BE AT LEAST 8 BYTES LONG Explanation: The generic data set entry in the DSNAME statement is too short. System Action: The statement is rejected. User Response: Be more specific in specifying generic data set names

0392E ERROR LINKING TO <cmd_name> Explanation: A CALLRTN command was issued in line mode and the link was

unsuccessful. System Action: The command is ignored. User Response: Check the validity of all parms in CALLRTN command and correct them.

If the problem persists call Cybermation support.

0393W INVALID COMMAND <cmd_name> Explanation: An invalid command was received from API. System Action: The command is ignored. User Response: Correct the request that caused the error.

0394W INVALID COMMAND NAME SYNTAX Explanation: The syntax of the command received from API is invalid. System Action: The command is rejected. User Response: Correct the request that caused the message.

0395S ERROR OBTAINING A COMMAND, RC=nn Explanation: An API related problem was found while validating a command. System Action: The command is ignored. This message is followed by 0396S. User Response: See message 0396S.

0396S COMMAND PROCESSING TERMINATED Explanation: This message follows a 0395S message. System Action: The API server is terminating. User Response: Check if all necessary tasks are up and running. If some are down -

find out why and start them.

0397I DATA SET <dsn> UNALLOCATED Explanation: This is an information message to the user UNALLOC command. System Action: Processing continues. User Response: Not required.

Messages and Codes

ESP-5.4-MC-03 59

0398E xxxxx Explanation: Freeing asked by command UNALLOC failed. System Action: Processing continues. User Response: Check whether the data set name was correctly specified in the

command.

0399S SCHEDULE FILE <DSN> UNUSABLE Explanation: Schedule file could not be opened. System Action: Scoreboard display aborted. User Response: Check the status of schedule file. It must be a KSDS VSAM data set.

0400E ERROR LINKING TO xxxx Explanation: The CALLRTN service could not find this command name. System Action: No command was invoked by CALLRTN. User Response: Correct the parameter to CALLRTN and try again.

0401W INVALID COMMAND, xxxx Explanation: An unrecognized command was entered from a operator's console. System Action: The command is ignored. User Response: Reenter the correct command name.

0402W INVALID COMMAND NAME SYNTAX Explanation: A command was issued which did not conform to the syntax for command

names. System Action: The command is ignored. User Response: Reenter the correct command name.

0403E Agent receiver xxxx not TCP/IP, PORT invalid Explanation: The "PORT" parameter was specified in an "AGENTRCV" command for an

APPC agent receiver. System Action: Processing continues. User Response: None.

0404E Agent receiver xxxx must be halted to set port Explanation: An "AGENTRCV SET PORT" command was issued for an active TCP/IP agent

receiver. System Action: Processing continues. User Response: Issue the following "AGENTRCV" commands to halt, set the port and

restart TCP/IP agent receiver "xxxx". AGENTRCV HALT AGENT(xxxx) AGENTRCV SET AGENT(xxxx) PORT(nnnn) AGENTRCV RESTART AGENT(xxxx)

0405S ERROR OBTAINING A COMMAND, RC=nn Explanation: The console command processor encountered an error in command

processing. System Action: This message is followed by message 406.

60 ESP-5.4-MC-03

User Response: See message 406.

0406S COMMAND PROCESSING TERMINATED Explanation: A severe error has caused the console communications processor to

terminate. System Action: ESP continues to operate without the operator communication facility. User Response: Notify your software support personnel. Use the STOP command to shut

ESP down, as the modify interface will not work.

0407W YOU ARE NOT AUTHORIZED FOR OPERATOR COMMANDS Explanation: A user attempted to issue an operator command to which he or she was

not authorized. System Action: The command is ignored. User Response: Authorization for operator commands is the responsibility of the

installation ESP administrator.

0408W YOU ARE NOT AUTHORIZED TO THE xxxx COMMAND Explanation: Use of this command requires OPER authority. System Action: The command is not executed. User Response: Ask the ESP System Administrator to authorize you to use this command.

0409E REEXEC MAXIMUM VALUE HAS BEEN REACHED, Explanation: A specified maximum of REEXECs has been reached. System Action: REEXEC request ignored. User Response: None.

0410E QUEUE update not allowed from a proxy subsystem Explanation: A cleanup of the QUEUE data set was attempted from a proxy subsystem. System Action: Request ignored. User Response: Any update of the QUEUE data set can be done only from a master

subsystem.

0411W Generation <gen> of <appl> NOT FOUND

REQUESTED GENERATION OF APPL <appl> NOT FOUND Explanation: Requested generation <gen> of application <appl> not found. System Action: Processing continues User Response: Check for errors in appl.gen specification.

0412W REQUESTED GENERATION OF APPL <appl> NOT FOUND Explanation: Appl.gen specified in APPLJOB command not found. System Action: The command is ignored. User Response: Specify a valid appl.gen.

0413E JOB <jobname> NOT FOUND IN APPL <appl> Explanation: Job <jobname> does not exist in application <appl>. System Action: The APPLJOB command is ignored. User Response: Use a valid job name and application name in the APPLJOB command.

Messages and Codes

ESP-5.4-MC-03 61

0414E JOB <jobname> IS NOT A MEMBER OF AN APPLICATION Explanation: Job <jobname> is not a member (part) of the application. System Action: The command is ignored. User Response: Use a valid job name in the APPLJOB command.

0415W Workload Object <name{.qual}> in appl <appl.gen> started at <ttt> Explanation: The named workload object started at time <ttt>. System Action: Processing continues. User Response: None (if the workload object is supposed to start).

0416W Workload Object <name{.qual}> in appl <appl.gen> ended at <ttt> Explanation: The named workload object ended at time <ttt>. System Action: Processing continues. User Response: None (if the workload object is supposed to end).

0417W Workload Object <name{.qual}> in appl <appl.gen> failed at <ttt>, Exitcode=cc

Explanation: The named workload object failed at time <ttt> with Completion Code=cc.

System Action: Processing continues. User Response: None (if the workload object is supposed to fail).

0418I CONTROL TRANSACTION HANDLER TERMINATED Explanation: Module that handles control transactions and delegates all other types

to the appropriate handling modules has terminated. System Action: TP Server cleanup completes, User Response: None.

0419I TP SERVER CONTROL TRANSACTION ACTIVE Explanation: This message is issued after the TP Server initialization has

completed. System Action: System is ready to send and receive transactions. User Response: None.

0420W EVENT DATASET CONTAINING xxxx.yyyy IS SUSPENDED Explanation: A request was made to read an Event definition. However, the data set

was currently suspended. System Action: The Event retrieval fails. User Response: If the Event data set is useable, issue the EVENTSET command to reopen

it.

0421E AN INVALID TRANSACTION FUNCTION WAS RECEIVED Explanation: TP Server received an invalid transaction code. System Action: Transaction ignored. User Response: Check if all systems to be connected have valid parms.

62 ESP-5.4-MC-03

0422I CONTROL TRANSACTION TERMINATING Explanation: TP Server is stopping due to previous error(s). System Action: TP Server will stop. User Response: If problem persist contact Cybermation support.

0423S CONTROL TRANSACTION RECEIVE FAILED - xxx Explanation: Invalid control transaction received. The beginning of the received

data is presented in hexadecimal format xxx. System Action: This message is followed by message 0422. User Response: See message 0422.

0424I LU 6.2 TRANSMISSION SERVER SHUTDOWN COMPLETE Explanation: TP Server has stopped successfully. System Action: None. User Response: None.

0425W INVALID JOBNAME SPECIFICATION <jobsp> Explanation: An invalid job specification appeared in command from Workstation. System Action: The command is ignored. User Response: Correct the job specification. It must take one of the following

forms: nnnn - JES job number jobname - 1-8 bytes alphanumeric job name job.qual - 1-8 bytes alphanumeric job name followed by 1-8 bytes alphanumeric qualifier subapplid- 1-8 bytes alphanumeric subapplication identifier

0426E INVALID JOBNAME SPECIFICATION <jobsp> Explanation: An invalid job specification appeared in command from console. System Action: The command is ignored. User Response: Correct the job specification. It must take one of the following

forms: nnnn - JES job number jobname - 1-8 bytes alphanumeric job name job.qual - 1-8 bytes alphanumeric job name followed by 1-8 bytes alphanumeric qualifier subapplid- 1-8 bytes alphanumeric subapplication identifier

0427E No jobs were eligible out of the <nn> jobs in Subappl <subapplname> Explanation: Out of <nn> jobs in subapplication <subapplname> no one was eligible

for requested action entered from console. System Action: The command is ignored. User Response: Check subapplication for presence of jobs qualified for the action.

0428W INVALID APPLICATION SPECIFICATION <appl> Explanation: An invalid application name appeared in command from Workstation. System Action: The command is ignored.

Messages and Codes

ESP-5.4-MC-03 63

User Response: Correct the application name.

0429E INVALID APPLICATION SPECIFICATION <appl> Explanation: An invalid application name appeared in command from console. System Action: The command is ignored. User Response: Correct the application name.

0430E DATASET NAME NECESSARY FOR AN HISTFILE DEFINE Explanation: A HISTFILE command was issued to define a history data set. The

data set name was omitted. System Action: The HISTFILE command is not processed. User Response: Respecify the command.

0431E HISTFILE xxxx NOT DEFINED Explanation: A HISTFILE command was issued for other than a define request. The

specified history data set could not be found. System Action: The HISTFILE command is not processed. User Response: Respecify the command.

0432E HISTFILE xxxx ALREADY DEFINED Explanation: A HISTFILE command was entered to define a new history data set. The

data set logical identifier matched that of an already existing data set.

System Action: The command is not processed. User Response: If this is for a new definition, ensure you use a unique identifier.

0433? HISTFILE xxxx OPEN, PERFORM CLOSE FIRST Explanation: A HISTFILE command was issued to delete a history data set that was

currently open. The history data set must be closed before a delete can be performed.

System Action: The request is ignored. User Response: Use the CLOSE option of the HISTFILE command to close the data set,

then issue the delete.

0434E ERROR SCANNING COMMAND, RC=nnn Explanation: Error occurred while scanning command received from Workstation. System Action: The command is ignored. User Response: Depending on RC=nn different actions could be considered.

When nn=12: invalid command structure. Transmission error is likely, Check init parms. Try again. nn=16: No space available. nn=20: Validity check routine termination. nn=24: An error in input parameters was detected in the IKJPARS2 load module. nn=28: A line drop condition was detected and IKJPTGT (PUTGET I/O service routine) or IKJPUTL (PUTLINE I/O service routine) set return codes of 24 and 32 respectively.

64 ESP-5.4-MC-03

0435W HISTFILE xxxx ALREADY OPEN Explanation: A HISTFILE command was issued to open a history data set which was

already open. System Action: The command is ignored. User Response: Ensure that the correct data set identifier was specified.

0436W HISTFILE xxxx ALREADY CLOSED Explanation: A HISTFILE command was issued to close a history data set which was

already closed. System Action: The command is ignored. User Response: Ensure that the correct data set identifier was specified.

0437A CONFIRM REQUEST TO DELETE HISTFILE xxxx, REPLY Y OR N Explanation: A HISTFILE command was issued to delete a history data set. System Action: ESP waits for a reply. User Response: Reply Y if you wish to continue with the delete request, otherwise

reply N to cancel the request.

0438I DELETE REQUEST CANCELLED Explanation: This message is issued if a reply of N was given to message 0437A. System Action: The delete request is not performed. User Response: None.

0439I HISTFILE xxxx DELETED Explanation: This message indicates that a history data set has been deleted

after a reply of Y to message 437A. System Action: None. This confirms data set deletion. User Response: None.

0441E HISTFILE WITH DSN xxxx ALREADY DEFINED Explanation: A HISTFILE command was issued to define a history data set. However, a

data set is already defined with the same dsname. System Action: The request is ignored. User Response: Ensure that you specify the correct name. If you wish to alter a

definition, use the SET option of the HISTFILE command.

0442I TRACKING OPTIONS: {NO}COLLECT, {NO}STORE, {NO}LOG Explanation: The job tracking options are displayed in response to the TRACKING

command. The following options are possible. COLLECT Job tracking data is collected from SMF and transmitted to ESP. NOCOLLECT Job tracking data is not being collected. STORE Job tracking data is stored in the job tracking file. NOSTORE Job tracking data is not being stored in the tracking file. If

Messages and Codes

ESP-5.4-MC-03 65

job tracking data is being collected, it will be temporarily kept in the checkpoint until the STORE option is again turned on. LOG Job tracking data is logged into the system log. NOLOG Job tracking data is not being logged in the system log.

System Action: Processing continues. User Response: None needed, unless you want to change an option. You should not let

the COLLECT option be on for too long with NOSTORE, or the checkpoint data set could fill up.

0443W JOB TRACKING FACILITY NOT INITIALIZED Explanation: The COLLECT or STORE option was specified on a TRACKING command.

However, the job tracking facility has not been initialized. This could be because some of the initialization parameters needed for job tracking were not specified in the parameter data set.

System Action: The request is not processed. User Response: Ensure that all the initialization parameters for the job tracking

facility are specified correctly.

0444W xxxxx Explanation: API Server received invalid data. System Action: Line ignored. User Response: None.

0450E EXIT FUNCTION REQUIRED FOR DEFINE REQUEST Explanation: An EXIT command or initialization statement specified a define

request, but no exit function type. System Action: The entire command or statement is ignored. The console operator may

be prompted to reenter the entire initialization statement. User Response: Respecify the command or initialization statement.

0451E INVALID EXIT FUNCTION xxxx Explanation: An EXIT command or initialization statement specified an invalid user

exit function type. System Action: The entire command or statement is ignored. The console operator may

be prompted to reenter the entire initialization statement. User Response: Respecify the command or initialization statement using the correct

function name.

0452W DUPLICATE MODULE/EXIT SPECIFIED, xxxx/yyyy, IGNORED Explanation: An EXIT command or initialization statement specified a that a module

be invoked for an exit. However, the same exit was specified more than once for the one module.

System Action: The duplicate module/exit entry is ignored. User Response: Ensure that the duplicate entry is removed from the initialization

file.

66 ESP-5.4-MC-03

0453E MODULE xxxx, EXIT nn, GAVE INVALID RETURN CODE OF nn Explanation: A user exit module, with the name mmm being called with an exit

function number of nn gave a non-supported return code. System Action: A return code of 0 is assumed. The exit is flagged as in error and not

reinvoked until reactivated by the EXIT command. User Response: Notify your software support personnel. This is a user error.

0454I DATA SET xxxx UNALLOCATED Explanation: A data set was unallocated as a result of the UNALLOC command being

issued. System Action: The data set is unallocated. User Response: None

0455E xxxx Explanation: A data set unallocation request was made by use of the UNALLOC

command. The unallocation request failed. The reason is described by the message text.

System Action: The data set is not unallocated. User Response: Check the message text for the cause.

0456C XMITMDL DISPLAY Explanation: This is the control line for a multi-line display of the nodes to

which tracking data represented by tracking models is to be sent. System Action: None. User Response: None.

0457I NO TRACKING MODELS DEFINED FOR CROSS NODE TRANSMISSION

Explanation: The LIST option of the XMITMDL was requested, but no tracking models were defined for inter-nodal communication.

System Action: None User Response: Use the ADD option of the XMITMDL command to add inter-nodal tracking

definitions.

0458W PROGRAM NAME xxxx NOT DEFINED IN JOB TRACKING PROGRAM EXCLUSION LIST

Explanation: A JTPEXCL command was requesting the deletion of a program entry. The name was not found in the list.

System Action: The name is not removed. If the command specified multiple entries, processing continues.

User Response: Ensure the program name was correctly specified. To obtain a display of the current exclusion list, issue the JTPEXCL command without any operands.

0459C JTPE DISPLAY Explanation: This line is displayed in response to the JTPEXCL command issued with

no operands.

Messages and Codes

ESP-5.4-MC-03 67

System Action: This line is followed by a listing of the program names in the job tracking exclusion list. The job tracking exclusion list is a list of programs whose steps are to be ignored when setting job conditions codes and job monitoring.


0460W JOB TRACKING EXCLUSION LIST IS EMPTY Explanation: No job names are excluded from the job tracking function. System Action: User Response:

0461I OK Explanation: API Server normal end of action. System Action: Processing continues. User Response: None.

0462E ERROR LOADING MODULE xxxx Explanation: The module could not be found by the MVS LOAD macro. System Action: User Response: Ensure that the module name is correct and that it can be found in the

link list or in a STEPLIB library.

0463W FUNCTION NOT SUPPORTED YET Explanation: The ENABLE, DISABLE, RELOAD, and DISPLAY functions are not supported

on this release of ESP. System Action: User Response:

0464E MISSING MODULE NAME Explanation: There is no MODULE parameter in the DEFINE or EXIT statement. System Action: The statement is ignored. User Response: Add a MODULE parameter and try again.

0465E MODULE mmmm, EXIT nn, ABENDED xxxx, SUSPENDED Explanation: A user exit module, with the name mmmm being called with an exit

function number of nn gave a non-supported return code. System Action: A return code of 0 is assumed. The exit is flagged as in error and not

reinvoked until reactivated by the EXIT command. User Response: Notify your software support personnel. This is a user error.

0466E Unable to read JFCB for DD xxxxxxxx, R15=n Explanation: While processing an allocation request by DDNAME, an error was returned

by RDJFCB. The DDNAME and RDJFCB return code are displayed. System Action: The allocation request fails. User Response: This is most likely an internal ESP error. Contact Cybermation.

0467E Literal value out of range Explanation: A value has been supplied that is either too large or too small to

68 ESP-5.4-MC-03

fit in an integer field. System Action: Processing of the procedure is stopped. User Response: You should supply a value in the range 2,147,483,647 to -2,147,483,648.

0468I ESP Workstation Server release <rel> STATUS Explanation: This is a display of requested information. System Action: This message is followed by message 0472. User Response: None.

0469I xxx xxx xxx ... Explanation: This is a trace data used for diagnostic purposes. System Action: Processing continues. User Response: None.

0470I ES056: xxxxxxxxxxxxx Explanation: This is tracing information from the Workload Object Interface Layer. System Action: Processing continues. User Response: None.

0471I ES056: xxxxxxxxxxxxx Explanation: This is a tracing information from Multi-Platform Agent Message

Router. System Action: Processing continues. User Response: None.

0472? <nnn> Client connections have been made, currently <mmm> are/is active Explanation: Continuation to message 0468: display of requested information. System Action: Processing continues. User Response: None.

0473I Command was xxxxxxxxx Explanation: This message is issued for debugging purposes only in development

versions of the workstation server. It is not issued by production versions.

System Action: None User Response: None

0474I ES078: xxxxxxxxxxxxx Explanation: This is a tracing information from DM Application Format Services. System Action: Processing continues. User Response: None.

0475I xxxx Explanation: Open/allocation file error. This message is issued when

synchronization is requested but the data set can not be found. System Action: CALLRTN command ignored. User Response: Correct the trigger Data Set Name and re-issue the command.

Messages and Codes

ESP-5.4-MC-03 69

0481W YOU ARE NOT AUTHORIZED FOR OPERATOR COMMANDS Explanation: You must have OPER authority to issue commands that require OPER

authority. System Action: The command is rejected. User Response: Ask ESP Administrator to grant you OPER authority.

0482E Unable to queue directly to system xxxx Explanation: The last pending signal for an event has been posted, and the event is

to be queued for execution to a system other than the one on which the signal was posted. The QUEUE data set is not available to the current system, so the event cannot be queued as required.

System Action: The event is not queued for execution. This message is followed by message 0395W, which gives the name of the event.

User Response: Make sure that the QUEUE file is available to all systems which share the same event data set. If necessary, enter a TRIGGER command to trigger the event manually.

0483E System xxxx not a member of shared QUEUE Explanation: An event has become eligible for execution when the last pending

signal for which it was waiting is posted. The event's definition specifies that it should be executed on a different system than that on which the signal was posted, but the specified system is not sharing the same QUEUE data set as the current system.


User Response: Make sure that the QUEUE file is shared by the system specified in the event definition for execution of the event. If required, enter a TRIGGER command to trigger the event manually.

0484E Insufficient CKPT space to queue event for execution Explanation: The last pending signal for an event has been posted, and the event is

to be queued for execution on the system on which the signal was posted. However, insufficient space was available in the system's checkpoint data set to build the required control blocks.


User Response: Investigate the cause of the shortage of checkpoint space. When this has been alleviated, enter a TRIGGER command to trigger the event manually.

0485E Insufficient QUEUE file space to queue event for execution Explanation: The last pending signal for an event has been posted, and the event is

to be queued for execution on a system other than that on which the signal was posted. However, insufficient space is available in the QUEUE data set to build the required control blocks.


User Response: Investigate the cause of the shortage of Queue file space. When this

70 ESP-5.4-MC-03

has been alleviated, enter a TRIGGER command to trigger the event manually on the specified system.

0486W Event xxxx.yyyy not executed Explanation: Due to a problem detailed in a previous message, it was not possible

to queue an event for execution when all its pending signals became satisfied.

System Action: The event has not been queued for execution. User Response: Correct the problem reported in the preceding message. If necessary,

enter a TRIGGER command to trigger the event manually.

0487W CYBESODT ABOVE ERROR OCCURRED DELETING TRIGGER INDEX FOR xxxx.yyyy APPL aaa.nnn

Explanation: This message, which will have been preceded by an I/O error message, indicates that the I/O error was a result of attempting to delete a data set trigger entry in the INDEX data set during the deletion of an Event.

System Action: The Event is deleted, however, the data set trigger entry may still remain.

User Response: The data set trigger entry can be deleted by redefining an Event with the same name and data set trigger requests, then deleting it. If the problem persists, notify your software support personnel.

0488E Invalid FROM or UNTIL date/time in TEMPLIB Explanation: A '//* FROM' or '//* UNTIL' statement in a TEMPLIB member contained

an illegal date/time specification. System Action: The job is not submitted, either from the TEMPLIB member or from any

corresponding JCLLIB member. User Response: Correct the date/time specification in error. Resubmit the job from

the appropriate source.

0489E SYMLIB record length too large Explanation: During event execution, a record with a length greater than the

maximum allowed was read from a symbol library. The maximum allowed total size including any sequence number is 252 bytes.

System Action: Execution of the event is suppressed. User Response: Copy the symbol library to a data set with a legal maximum record

length, and re-trigger the event.

0490E SYMLIB record length too large Explanation: During event execution, a record with actual data longer than the

maximum allowed was encountered in a symbol library. The maximum length excluding any sequence number is 244 bytes.

System Action: Execution of the event is suppressed. This message will be preceded by messages 560W, 561I and 535I.

User Response: Copy the symbol library to a data set with a legal maximum record length, and re-trigger the event.

Messages and Codes

ESP-5.4-MC-03 71

0491E COPYJCL not reserved: DDname=xxxx, DSname=yyyy Explanation: The COPYJCL data set yyyy was allocated successfully and assigned

DD name xxxx. However while reserving the data set, the DD name could not be located. The problem may be an internal one.

System Action: The copy is skipped. Processing continues. User Response: None. This message is preceded by other errors that must be corrected.

0492E COPYJCL not released: DDname=xxxx, DSname=yyyy; DEQ cccc Explanation: The data set yyyy was used for copying JCL. After the copy was

completed or terminated the DD name xxxx could not be located. The result of DEQ (cccc) may be "successful" - the data set was owned by ESP task and dequeued or "unsuccessful" - the ESP task did not own the COPYJCL data set. The problem may be an internal one.

System Action: An attempt was made to DEQueue the data set. Processing continues. User Response: None. This message is preceded by other errors that must be corrected.

0493I JOB TERMINATED BY CCCHK STOP REQUEST Explanation: As a result of a matching CCCHK statement with the STOP option,

ESP has terminated the execution of the job. This message appears in the log and messages for the job in question.

System Action: ESP Workload Manager terminates the execution of the job. User Response: None.

0494E Job jjjjjjjj has an illegal RESTART keyword Explanation: The named job contained a RESTART= operand on the JCL JOB statement.

However, it also requested ESP Encore, which depends upon an ESP- inserted step being executed as the first step of the job. These conditions are incompatible, as the RESTART will cause MVS to bypass the ESP-inserted step.

System Action: The job is flushed from the internal reader. User Response: Either:

1. Remove the RESTART= operand from the JCL JOB statement of the job in question, or 2. Change the ESP procedure to not request Encore for the job in question. Then resubmit the job via CSF or AJ RESUB.

0495E SHADOW start parameter specifies xxxx, must be within range 0-31 Explanation: The JCL EXEC PARM or START command parameter specified the

SHADOW(xxxx) operand, where xxxx is not a valid shadow image number (value within the range 0-31).

System Action: ESP terminates. User Response: Correct the JCL EXEC PARM or START command parameter to specify a

shadow image number xxxx within the range 0-31, and restart ESP. Note that the ESP master and each ESP shadow manager in an XCF group should have a unique shadow image number.

72 ESP-5.4-MC-03

0496E SHADOW requested, SYSPLEX not specified, terminating Explanation: ESP is shadow enabled, i.e. the JCL EXEC PARM operand or START command

parameter specified the SHADOW and/or PRIMARY or SECONDARY keywords. In addition, the ESP High Availability Option is installed. However, a SYSPLEX statement was not specified in the ESPPARM initialization file.

System Action: ESP terminates. User Response: If ESP is to run shadow enabled, add a SYSPLEX statement to the

ESPPARM file. If ESP is not to run shadow enabled, i.e. not as a shadow enabled ESP master nor as a Shadow Manager, then omit the SHADOW and/or PRIMARY or SECONDARY keywords from the JCL EXEC PARM operand or START command parameter.

0497E TRACKOPT MASTER|PROXY option only valid during ESP/WM initialization

Explanation: Response to TRACKOPT MASTER or TRACKOPT PROXY issued as an ESP/WM operator command. ESP/WM cannot be set to a master or a proxy after initialization.

System Action: None. Processing continues. User Response: None.

0498I ESP SHUTDOWN IN PROGRESS, SUBSYS xxxx Explanation: A shutdown command was issued to ESP or a P or STOP command was

received. System Action: ESP continues with the shutdown. User Response: None.

0499I ESP RELEASE xxxx INITIALIZED, SUBSYS yyyy Explanation: ESP has completed its initialization. System Action: Processing continues. User Response: None.

0500E INVALID RECORD TYPE KEY ON USERDEF DATASET FOR ENTRY xxxx

Explanation: A record in the USERDEF data set contains an invalid type indicator. System Action: The user entry retrieval request will fail. User Response: Notify your software support personnel.

0501E EVENT DATASET ID xxxx, REQUIRED FOR EVENT yyyy.zzzz, NOT FOUND

Explanation: The Event data set required to access the specified Event was not defined to ESP.

System Action: The Event access fails. If the Event was scheduled for execution, it is ignored.

User Response: Notify your software support personnel. This may be expected after an Event data set has been deleted.

Messages and Codes

ESP-5.4-MC-03 73

0502E Tracking transmitter name missing Explanation: An ISCXMTR statement was encountered with the transmitter name

operand missing. System Action: The ISCXMTR statement is ignored. User Response: Correct the ISCXMTR statement to specify a valid transmitter name.

0505W Node xxxx already defined for tracking model yyyy, ignored Explanation: An XMITMDL statement NODE keyword operand specified an inter-system

tracking node that has been defined in a previous XMITMDL statement for the tracking model specified by the MODEL keyword operand.

System Action: The previously defined node is ignored. Otherwise the XMITMDL statement is processed normally.

User Response: An "XMITMDL LIST" command can be issued to determine if all inter-system tracking models have been correctly defined. If not, "XMITMDL DELETE" and "XMITMDL ADD" commands can be issued to correct them.

0506E Prefixing must be 0, 1 or 2 Explanation: Valid values for the PREFIXING keyword on the AGENT statement are

0 (No prefixing), 1 (Prefixing) or 2 (Enhanced prefixing). System Action: Processing of the AGENTDEF file ends. User Response: Correct the PREFIXING specification.

0507E Missing or invalid agent name in prefix: xxxxxx Explanation: The agent message receiver received a message with a type 2 prefix,

but the prefix did not contain a valid agent name. System Action: The current message is ignored. User Response: This could be caused by an agent name mismatch between the AGENTDEF

and AgentParm files.

0508E Encryption type incompatible with agent xxxxx Explanation: The encryption type in the message header does not match the

encryption type specified in the AGENTDEF file for the agent. System Action: The current message is ignored. User Response: This could be caused by a mismatch of the encryption type between

the AGENTDEF and AgentParm files.

0509E Only encrypted messages can be accepted by receiver xxxxxxxx Explanation: The agent receiver has been configured to receive only encrypted

messages. System Action: The current message is discarded. User Response: If non-encrypted messages should be received normally, remove the

ENCRYPT keyword from the AGENTRCV command in ESPPARM.

0510E DATASET NAME NECESSARY FOR AN EVENTSET DEFINE Explanation: An EVENTSET command was issued to define an Event data set. However,

the data set name was omitted.

74 ESP-5.4-MC-03

System Action: The EVENTSET command is not processed. User Response: Respecify the command.

0511E EVENTSET xxxx NOT DEFINED Explanation: An EVENTSET command was issued for other than a define request. The

specified Event data set could not be found. System Action: The EVENTSET command is not processed. User Response: Respecify the command.

0512E EVENTSET xxxx ALREADY DEFINED Explanation: An EVENTSET command was entered to define a new Event data set.

However, the data set logical identifier matched that of an already existing data set.

System Action: The command is not processed. User Response: If this is for a new definition, ensure you use a unique identifier.

0513W EVENTSET xxxx OPEN, PERFORM CLOSE FIRST Explanation: An EVENTSET command was issued to delete an Event data set that was

currently open. The Event data set must be closed before a delete can be performed.

System Action: The request is ignored. User Response: Use the CLOSE option of the EVENTSET command to close the data set,

then issue the delete.

0514I JCL RESTART ADAPTED BY ESP/WM Explanation: The job contained a RESTART= operand on the JCL JOB statement.

However, it also requested one of the ESP features which depend upon an ESP-inserted step being executed as the first step of the job. ESP/WM has removed the RESTART= operand in order to allow the inserted step to execute. Steps after the inserted step, but prior to the one where the restart is requested, have had COND=(0,LE) applied in order to cause them to be skipped without being executed.

System Action: The job continues. User Response: None.

0515W EVENTSET xxxx ALREADY OPEN Explanation: An EVENTSET command was issued to open an already open Event data set. System Action: The command is ignored. User Response: Ensure that the correct data set identifier was specified.

0516W EVENTSET xxxx ALREADY CLOSED Explanation: An EVENTSET command was issued to close an already closed Event

data set. System Action: The command is ignored. User Response: Ensure that the correct data set identifier was specified.

Messages and Codes

ESP-5.4-MC-03 75

0517A CONFIRM REQUEST TO DELETE EVENTSET xxxx, REPLY Y OR N Explanation: An EVENTSET command was issued to delete an Event data set. System Action: ESP waits for a reply. User Response: Reply Y if you wish to continue with the delete request, otherwise

reply N to cancel the request.

0518I DELETE REQUEST CANCELLED Explanation: This message is issued if a reply of N was given to message 517. System Action: The delete request is not performed. User Response: None.

0519I EVENTSET xxxx DELETED Explanation: This message indicates that an Event data set has been deleted after a

reply of Y to message 517. System Action: None. This confirms data set deletion. User Response: None.

0520E EVENTSET WITH DSN xxxx ALREADY DEFINED Explanation: An EVENTSET command was issued to define an Event data set. However, a

data set is already defined with the same dsname. System Action: The request is ignored. User Response: Ensure that you specify the correct name. If you wish to alter a

definition, use the SET option of the EVENTSET command.

0521I EVENT DATA SET xxxx SUSPENDED Explanation: An EVENTSET command was issued with the CLOSE option. System Action: The specified Event data set is closed and unallocated. It is

considered to be suspended from use until it is reopened. User Response: None.

0522E ERROR OCCURRED READING xxxx.yyyy EVENT DEFINITION Explanation: An I/O error occurred reading an Event definition. System Action: This message is followed by message 523. User Response: Wait for and examine message 523.

0523W xxxx Explanation: This message describes the error encountered while reading and Event

definition. System Action: This message is followed by a message indicating the action that ESP

will take. User Response: Note any message that follows.

0524W EVENT xxxx.yyyy DEFERRED Explanation: This message is issued after an error prevented the normal schedule of

an Event. A preceding message would have described the error condition.

System Action: The Event execution is deferred until the error condition previously

76 ESP-5.4-MC-03

described is corrected. User Response: Notify your software support personnel of the error condition.

0525I VS COMMAND NOT AUTHORIZED IN EVENT xxxx.yyyy Explanation: AN Event specified a VS command when the group or user defining it did

not have the OPER authority. System Action: The VS command is not executed. User Response: None.

0526E xxxx Explanation: An I/O error occurred opening an OS, CA-Librarian or

CA-Panvalet data set for a SUBMIT command in the execution of an Event.

System Action: This message was preceded by message 0528E. The Event execution will be bypassed.


0527W Event xxxx.yyyy delayed nn minute(s) due to contention on aaaa Explanation: The data set 'aaaa' required for the submission of JCL during the

execution of an Event could not be allocated as another job or TSO user had allocated it exclusively.

System Action: The Event execution is delayed by 'nn' minutes as specified by the DELAYINT command.

User Response: If this condition persists, determine the user having the data set allocated, and request they free it.

0528E ERROR OCCURRED PROCESSING EVENT xxxx.yyyy Explanation: This message indicates that some error has occurred during the

execution of an Event. System Action: This message is followed by another message describing the actual

error. User Response: Respond to the next message.

0529E ERROR OCCURRED UPDATING xxxx.yyyy Explanation: An I/O error occurred while trying to write back an updated Event

definition. System Action: This message will be followed by a message describing the error. User Response: Respond to the next message.

0530E NO SPACE LEFT IN CHECKPOINT Explanation: The EVENTSET command could not obtain space in the checkpoint to hold

the Event data set definition. System Action: The EVENTSET request is not processed. User Response: Use the LISTCKPT command to determine the amount of space remaining in

the checkpoint.

0531W Event xxxx.yyyy delayed nn minute(s) due to migrated data set aaaa Explanation: The data set 'aaaa' required for the submission of JCL during the

Messages and Codes

ESP-5.4-MC-03 77

execution of an Event could not be allocated as it was migrated by HSM or an equivalent product.

System Action: The Event execution is delayed by 'nn' minutes as specified by the DELAYINT command. A recall is initiated for the specified data set.

User Response: If this condition persists, determine why the data set has not been recalled.

0532W EVENT xxxx.yyyy SUSPENDED Explanation: An error occurred while computing the next scheduled execution time of

an Event. System Action: The Event is suspended. User Response: This message is preceded by messages describing the error. The

corrective action depends on the error.

0533W GROUP 'xxxx' NOT DEFINED Explanation: ESP attempted to execute an Event. However, the high level index of

the Event name did not correspond to an existing user or group. System Action: This message is followed by a message indicating the action that ESP

will take. User Response: The GROUP or USER entry to which the Event belongs may have been

deleted.

0534W ERROR ON JCL FOR EVENT Explanation: An error was detected in the JCL for a job being submitted or scanned. System Action: This message is followed by message 561, identifying the data set and

line number that the error occurred on. This is in turn followed by message 535 displaying the text containing the error. The message group is then followed by a message describing the error. The job being submitted at the time of error will be deleted, and will need resubmission.

User Response: Take action according to the messages that follow.

0535I xxxx Explanation: This message follows message 0534W. It displays the JCL image

containing the error. This message is followed by another message describing the error.

System Action: None. User Response: Correct the error indicated by the message.

0536W INVALID EVENT ID ON INCLUDE STATEMENT Explanation: A %INCLUDE statement contained an invalid Event name as an operand of

the EVENT keyword. System Action: This message is followed by message 544. User Response: Correct the EVENT name.

0537I Attempting to recall data set nn Explanation: While processing, an attempt was made to allocate data set "nn". It

was determined that data set "nn" had been migrated. System Action: An attempt is made to recall data set "nn". Any additional actions are

78 ESP-5.4-MC-03

indicated in messages following this message. User Response: If necessary, retry the function using data set "nn" after it has been

recalled.

0538I Migrated data set function is not available Explanation: During the allocation of a data set, it was determined that MVS dynamic

allocation does not support the identification of migrated data sets. System Action: All future allocations do try to identify migrated data sets. User Response: None.

0539W ERROR ON DAY OF WEEK FIELD Explanation: A JCL image statement described by previous messages contained an

invalid day of week name. System Action: This message is followed by message 544. User Response: Correct the day of week name.

0540E INSUFFICIENT CHECKPOINT SPACE TO QUEUE EVENT xxxx Explanation: During a DEFINE or TRIGGER, ESP attempted to put an Event on the

schedule queue. However, insufficient space remained on the checkpoint.

System Action: The Event is not scheduled for execution. User Response: The Event should be triggered when more checkpoint space becomes

available.

0541E EVENT DATASET ID xxxx NOT FOUND Explanation: An Event data set needed to store or retrieve an Event could not be

found. System Action: The storage or retrieval request fails. User Response: This may arise for two reasons. A user or group may have been defined

to a non-existent Event data set, or the Event data set may have been deleted. The user or group definition should be altered to reference an existing Event data set.

0542W INVALID INCLUDE STATEMENT SYNTAX Explanation: A %INCLUDE statement had a syntax error. System Action: This message is preceded by messages 534 and 535, and will be followed

be message 544. User Response: See description for message 544.

0543W INVALID TIME SYNTAX ON INCLUDE STATEMENT Explanation: A %INCLUDE statement had a syntax error in the time specification of

the TO or FROM keywords. System Action: This message is preceded by messages 534 and 535, and will be followed

be message 544. User Response: See description for message 544.

0544W JOB xxxx DELETED, WILL NEED RESUBMISSION Explanation: An error, described by a preceding message, was found in the JCL of a

Messages and Codes

ESP-5.4-MC-03 79

job being submitted or scanned. System Action: If a job was being submitted as result of an Event execution, it will

be deleted and require resubmission. User Response: Correct the error and resubmit the job if necessary.

0545E Error in xxxx, RC=nn Explanation: An error occurred while processing in routine "xxxx". This will

typically be a CPIC routine. The return code from the function is "nn".

System Action: The current transaction is terminated. User Response: Notify your software support personnel. Make note of the function

name and return code. If the routine is a CPIC routine, determine whether the return code may be valid for your environment.

0546E INSUFFICIENT CHECKPOINT SPACE TO QUEUE EVENT FOR DELAYED EXECUTION

Explanation: An Event was scheduled for delayed execution as the result of a data set contention. However, insufficient checkpoint space was available to requeue it.

System Action: The Event is not rescheduled. User Response: The Event will have to be manually rescheduled, or triggered, once

some space is freed up in the checkpoint.

0547W EVENT xxxx.yyyy NOT EXECUTED Explanation: An error prevented an Event from being retrieved. This message will

have been preceded by a message describing the error. System Action: The scheduled execution of the Event will by bypassed. User Response: Notify your system support personnel.

0548W SWITCH TO SUBMISSION SUBTASK FAILED, MAIN TASK USED Explanation: ESP was unable to switch to a subtask while performing the execution

of an Event. System Action: ESP will execute the Event at the main task level. This can cause ESP

to take slightly longer to respond to user or operator requests, as they are serialized with submission processing.

User Response: If this message is repeated often, notify your software support personnel.

0549W xxxx Explanation: An I/O error occurred while writing the JCL to the internal reader or

to a data set. This message describes the actual error. It is preceded by message 534 indicating the Event and data set being processed.

System Action: No more JCL is written to the internal reader or user requested data set for this Event.


0550E xxxx Explanation: An I/O error occurred opening a data set for the COPYJCL function. System Action: This message was preceded by message 528. The COPYJCL function

80 ESP-5.4-MC-03

will not be executed. User Response: The message text will describe the error. If it is necessary to

recreate the JCL submitted by the Event execution, use the SCAN subcommand of the ESP TSO command.

0551W ERROR COPYING JCL FOR EVENT xxxx.yyyy Explanation: An I/O error occurred while copying JCL to an output data set as

result of a COPYJCL request. System Action: The COPYJCL function is not completed. This message is followed by

message 552, describing the error. User Response: Take action according to the message that follows.

0552W xxxx Explanation: An I/O error occurred writing JCL TO a data set for the COPYJCL

function. System Action: This message was preceded by message 551. The COPYJCL function will

not be completed. User Response: The message text will describe the error. If it is necessary to

recreate the JCL submitted by the Event execution, use the SCAN subcommand of the ESP TSO command.

0553W EVENT xxxx.yyyy BYPASSED, CLASS zzzz SUSPENDED Explanation: The execution of an Event was bypassed because the class to which the

Event belonged was suspended. An Event class is suspended by the CLASS operator command.

System Action: The Event is not executed. The Event will only be eligible for execution once its class is taken out of the suspended state.

User Response: None. This was requested by an operator command.

0554W EVENT xxxx.yyyy HELD, CLASS zzzz Explanation: The execution of an Event was delayed because the class to which the

Event belonged was in the hold state. System Action: The Event will remain on the hold queue until the class is released by

use of the RELEASE option of the CLASS operator command. At that point, the Event will be considered overdue, and action will be taken according to the overdue count specified in the Event definition.

User Response: None. This was requested by an operator command.

0555E RACINIT FOR USER xxxx FAILED, ERROR CODE nn Explanation: While executing an Event, ESP attempted to initialize the user's

environment. The RACF initialization request failed. System Action: The Event is not executed. User Response: Check the error code with the error codes associated with the

installations security facility. This error is commonly caused by a userid being in "REVOKED" status.

0556I VS COMMAND SUPPRESSED BY USER EXIT IN EVENT xxxx.yyyy Explanation: A VS command requested in an Event or ESP Procedure was rejected by

the installation command exit.

Messages and Codes

ESP-5.4-MC-03 81

System Action: The VS command is suppressed. User Response: Check with your installation system programming team.

0557E RECORD LENGTH OF DATA SET xxxx EXCEEDS MAXIMUM LENGTH OF 136

Explanation: The specified data set has a record length greater than the maximum allowed. For JCL and symbolic variable libraries, the maximum data length allowed is 132 or a maximum record length of 136.

System Action: JCL submission is bypassed but the remainder of the event is executed. User Response: Alter the data set name on the INVOKE statement or redefine the SYMLIB

definition(s) by specifying a data set name with a record length of less than 136.

0558W Event xxxx.yyyy delayed nn minute(s), data set aaaa is offline Explanation: An Event attempted to access a data set on an offline volume. System Action: The Event execution is delayed by 'nn' minutes as specified by the

DELAYINT command, assuming the overdue count is non-zero. User Response: None. If the volume is no longer in use, edit the Event to point to

the new volume.

0559E UNBALANCED PARENTHESES FOR IF KEYWORD OF INCLUDE STATEMENT

Explanation: The IF keyword of the %INCLUDE or %EXCLUDE statement had an unequal number of left and right parentheses.

System Action: The Event is not processed. User Response: Check the number of parentheses. Probably the closing parenthesis was

omitted.

0560W ERROR ON SYMBOL LIBRARY SCAN FOR EVENT Explanation: An error was detected during the symbol library scan for an Event. System Action: This message is followed by message 561, identifying the data set and

line number that the error occurred on. This is in turn followed by message 535 displaying the text containing the error. The message group is then followed by a message describing the error.

User Response: Look at the messages that follow. Look at the messages that follow.

0561I DATA SET xxxx LINE nn Explanation: This message follows message 534 or 560. It identifies the data set

and line number containing the error. System Action: This message is followed by message 535, which displays the actual

line of data causing the error. User Response: Look at the messages that follow. Look at the messages that follow.

0562I JOB xxxx DELETED BY INSTALLATION EXIT Explanation: The installation exit requested deletion of the job. System Action: The job is deleted. User Response: The job may requires resubmission.

82 ESP-5.4-MC-03

0563W xxxx NOT FOUND FOR EVENT yyyy.zzzz Explanation: During SADGEN (Scheduled Activity Data GENeration), an entry was not

located in the ESP USERDEF or INDEX data set. The entry type and record name is displayed in the message.

System Action: The Event simulation will be attempted without the information in the record. This may be due to a missing SYMLIB or CALENDAR entry, for example.

User Response: The Event needs to be updated to specify the correct entry name, or the entry that the Event requires needs to be defined.

0564E Event xxxx.yyyy terminated due to msg limit excession Explanation: An Event attempted to write more than the installation or Event

defined limit. The execution of the Event was terminated as a result of this. The message limits can be specified via the MSGLIMIT statement in the ESP Procedure. The installation default can be specified as an initialization statement.

System Action: The Event execution is terminated. No jobs will be submitted or commands executed.

User Response: If the Event needs to issue more messages than the current message limit, specify a higher value on the MSGLIMIT statement in the ESP Procedure.

0565E SCANTIME VALID ONLY ON DEFINE Explanation: The scan time has already been established for this event set. It

can not be changed, because that would require purging all TDRs for this event set from the checkpoint and performing a new scan. This would destroy the effect of any TRIGGER commands which have been executed, but whose effect is not yet complete.

System Action: The EVENTSET command is ignored. User Response: If you absolutely must change the time, and understand the impact,

then: 1. Issue EVENTSET xxxx CLOSE 2. Issue EVENTSET xxxx DELETE (this can only be done from a console modify command) 3. Issue EVENTSET xxxx DEFINE DSNAME(dsn) SCANTIME(when) including SHR, JOURNAL, and BACKUPDSN(x) as appropriate

0566E AFM invalid, xxxx Explanation: An invalid Automated Framework Message (AFM) was encountered. xxxx

displays up to the 1st 64 bytes of the AFM in error. System Action: The AFM is not sent. Processing continues. User Response: If the AFM was generated by a user, correct it and re-enter it into

the ESP subsystem. If the AFM was generated internally by ESP, call Cybermation support.

0567E AFM destination name xxxx is too long Explanation: The length of destination name xxxx (3rd positional operand) of an

Automated Framework Message (AFM) exceeds the maximum (100 bytes).

Messages and Codes

ESP-5.4-MC-03 83

System Action: The AFM is not sent. Processing continues. User Response: If the AFM was generated by a user, correct it and re-enter it into

the ESP subsystem. If the AFM was generated internally by ESP, call Cybermation support.

0568E AFM destination xxxx not defined Explanation: Destination name xxxx (3rd positional operand) of an Automated

Framework Message (AFM) is not defined to ESP, i.e. it does not specify a valid Cybermation network node (typically an AGENT or DMANAGER).

System Action: The AFM is not sent. Processing continues. User Response: Ensure that the destination name xxxx was correctly specified (defined

in the ESP AGENTDEF file if an AGENT or DMANAGER).

0569W Shadow manager not joined to XCF group, terminating Explanation: This ESP was specified to be a Shadow, but the join to the XCF group

failed. XCF communications is essential for the Shadow function. System Action: The subsystem does not initialize User Response: Investigate and correct the XCF problem.

0570S QUEUE DATASET CONTROL INFORMATION HAS BEEN CORRUPTED

Explanation: The Queue data set has been corrupted, perhaps due to a logic error within the software. The corruption was detected in the in-storage copy of the data set before the data was written out.

System Action: The subsystem will take a dump and terminate. The in-storage copy is not written out.

User Response: The subsystem can be restarted. An 110x abend on restart may indicate that the queue data set itself had been corrupted. If so, you will have to use the QFORM start parameter to cause the queue data set to be reformatted.

0571W PLEASE RESTART THE SUBSYSTEM AFTER THE FOLLOWING ABEND

Explanation: This message follows message 570, after a corruption to the in-storage copy of the queue data set has been detected.

System Action: The subsystem will abend to prevent writing the corrupted data out to the data set.

User Response: This message will be followed by message 572. Follow the instructions to the next message.

0572W IF ABENDS PERSIST, RESTART WITH THE QFORM OPTION Explanation: System Action: User Response:

0573E QUEUE DATASET INFORMATION RECOVERED AFTER ERROR Explanation: ESP detected a corruption in the queue data set prior to a write.

84 ESP-5.4-MC-03

However, the information was recovered from the previous write. System Action: A system dump is taken. Processing continues. User Response: The dump should be sent to Cybermation for analysis.

0574E QUEUE DATASET REFORMATTED Explanation: An severe corruption of the QUEUE data set caused it to be

reformatted. System Action: A system dump will have been taken prior to this message being issued.

Processing continues. User Response: Please forward the dump to Cybermation for analysis.

0575E Event xxxx.yyyy not found, needed for zzzz{.aaaa} in Appl bbbb.nn Explanation: An Event was deleted while an active application still needed it.

When the Application manager requested the execution of the Event, the Event could not be found by the Event manager.

System Action: The action requested by the Application manager could not be performed. The job or task in the application will not be processed.

User Response: The Event will need to be redefined, and the job resubmitted via CSF or the AJ command.

0576E Overlength message received by Agent Receiver xxxx Explanation: Agent Receiver xxxx has received a message which is too large

to fit in the message buffer. System Action: The message is discarded, and a negative acknowledgement is

returned to the transmitting agent. User Response: Check the agent's communications log to determine the message

in question, then modify the generator of this message to restrict it to a valid size.

0579E ESP not SHADOW enabled, SHADGOAL invalid Explanation: A SHADGOAL initialization parameter was encountered, but SHADOW(n)

had not been specified. This ESP is not SHADOW enabled. System Action: The subsystem does not initialize. User Response: Specify SHADOW(n) as a start parameter, or remove SHADGOAL from the

ESPPARM

0580W INDEX DATASET FULL FOR PREFIX xxxx Explanation: A data set trigger index entry could not be created as the index

data set had too many entries for that prefix. It is possible to have approximately 32000 data set trigger entries for each group of data sets having the first 8 characters of their names equal.

System Action: The data set triggering for the Event being defined will not be activated.

User Response: Too many data set trigger entries have been defined for data sets with that high level index. Use another high level index or delete some unused events which reference the same data set triggering high level index.

Messages and Codes

ESP-5.4-MC-03 85

0581W ABOVE ERROR OCCURRED DELETING TRIGGER INDEX FOR xxxx.yyyy

Explanation: This message, which will have been preceded by an I/O error message, indicates that the I/O error was a result of attempting to delete a data set trigger entry in the INDEX data set during the deletion of an Event.

System Action: The Event is deleted, however, the data set trigger entry may still remain.

User Response: The data set trigger entry can be deleted by redefining an Event with the same name and data set trigger requests, then deleting it. If the problem persists, notify your software support personnel.

0582W DATA SET TRIGGERING SUSPENDED DUE TO PRIOR REQUEST Explanation: This message is issued when ESP is warm started and detects that

data set triggering was suspended prior to the previous shutdown. System Action: Data set triggering is suspended until explicitly enabled through the

DSTRST command. User Response: If you wish data set triggering to be resumed, use the DSTRST command

with the RESUME option.

0583W EVENT EXECUTION SUSPENDED DUE TO PRIOR REQUEST Explanation: This message is issued when ESP is warm started and detects that it

was in the quiesced state prior to the previous shutdown, or if the QUIESCE option is specified at start-up.

System Action: Event execution will be suspended, until explicitly enabled through the RESTART command.

User Response: If you wish to restart Event execution, use the RESTART command.

0584E INDEX DATASET ERROR, DATASET TRIGGERING NOT FULLY INITIALIZED

Explanation: An I/O error on the INDEX data set caused an incomplete initialization of the data set triggering facility.

System Action: Not all data set triggers will be recognized. User Response: Correct the I/O on the INDEX data set.

0585E INDEX DATA SET ERROR CAUSING SUSPENSION OF DATA SET TRIGGERING

Explanation: While processing a data set trigger, an I/O error occurred on the INDEX data set. This message will have been preceded by an I/O error message.

System Action: Data set triggering will be suspended until resumed using the DSTRIG command.

User Response: Notify your software support personnel. When the problem with the INDEX data set is corrected, resume data set triggering with the DSTRIG command.

86 ESP-5.4-MC-03

0586E ESP/WM not set to master or proxy, reply M for master or P for proxy Explanation: An ESP workload manager subsystem has not been set to a master or a

proxy. System Action: The operator is prompted to specify whether the ESP workload manager

subsystem must be set to a master or a proxy. User Response: Reply M or P, as appropriate, to this message.

In addition, add one of the following to the ESPPARM initialization file - TRACKOPT MASTER to set the ESP workload manager subsystem to a master ESP/WM. TRACKOPT PROXY to set the ESP workload manager to a proxy ESP/WM.

0587E GROUP PREFIX xxxx NOT AUTHORIZED FOR SYMTAB yyyy Explanation: An Event requested a symbol table to which it was not permitted

access. System Action: The symbol data sets specified by the symbol table will not be read. User Response: The access to symbol tables is controlled by the ESP administrator.

0588I EVENT xxxx.yyyy AUTODELETED Explanation: An Event specified the autodelete option. During execution, all input

members were found to be deleted or, if from a CA-Panvalet library, disabled.

System Action: The specified Event is deleted. User Response: None.

0589E ERROR OCCURRED DURING AUTODELETE OF EVENT xxxx.yyyy Explanation: An I/O error occurred while attempting to delete an Event during

autodelete processing. This message will have been preceded by a message describing the actual error.

System Action: The Event may not be deleted. User Response: The Event may need to be deleted manually.

0590E JOB AUTH TABLE xxxx NOT FOUND FOR USER yyyy Explanation: ESP tried to read a job authorization table to verify a user's access

to a job. The authorization table entry specified for the user could not be found/.

System Action: The request is not processed. User Response: Notify your installation ESP support personnel.

0591E I/O ERROR RETRIEVING JOB AUTH TABLE xxxx FOR USER yyyy Explanation: An I/O error occurred while ESP tried to read a job authorization

table to verify a user's access to a job. System Action: The request is not processed. User Response: Notify your installation ESP support personnel.

0592E EVENT EXECUTION CANCELLED BY INSTALLATION EXIT Explanation: The execution of an Event was cancelled by the installation defined

Messages and Codes

ESP-5.4-MC-03 87

event execution exit. System Action: The processing for the Event is bypassed. User Response: Check with the installation support team.

0593E INVALID REQUEST CODE xxxx IN TDR, REQUEST BYPASSED Explanation: An invalid request code was found in a TDR (Time Driven Request)

element. System Action: The TDR is bypassed. User Response: This is probably due to an I/O error or a logic error in the program.

Notify your software support personnel.

0594E NO EVENT DATASETS DEFINED Explanation: No Event data sets were found to exist when a request was made to the

ESP subsystem. System Action: The request is denied. User Response: Ensure that at least one Event data set is defined to ESP.

0595E TRACKOPT PROXY invalid for shadow enabled ESP/WM Explanation: Response to TRACKOPT PROXY command.

The current ESP/WM is shadow enabled. A shadow enabled ESP/WM cannot be set to a proxy ESP/WM.

System Action: The command fails. User Response: If the ESP/WM is intended to be a proxy, then remove the SHADOW,

PRIMARY and/or SECONDARY keywords from the ESP/WM JCL EXEC PARM operand. If the ESP/WM is not intended to be a proxy, and the TRACKOPT PROXY command is in the ESPPARM initialization file, then either delete it or change it to TRACKOPT MASTER.

0596E AGENTRCV {NO}PREFIXING obsolete, TCP/IP data prefixing auto-detected

Explanation: An AGENTRCV command was issued specifying obsolete keyword NOPREFIXING or PREFIXING. Agent receivers (ESP 5.2 or later) are capable of detecting whether or not the agents that connect to them are using TCP/IP data prefixing. Therefore it is no longer valid to specify that an agent receiver handle only prefixed data or only non-prefixed data, since they are capable of handling both.

System Action: Processing continues. User Response: If the AGENTRCV command was specified in a file, remove the NOPREFIXNG

or PREFIXING operand. Otherwise none.

0597W Manager address not available Explanation: Response to MGRADDR command.

The manager address is required to process the command normally, but is not available because an AGENTDEF file with a "MANAGER TCPIP" statement has not been processed by a LOADAGDF command.

System Action: Processing continues. User Response: If required, issue a LOADAGDF command to process an AGENTDEF file that

includes a "MANAGER TCPIP" command.

88 ESP-5.4-MC-03

Then re-issue the MGRADDR command.

0598E PORT only valid for MGRADDR AGENT option Explanation: Response to MGRADDR command.

The PORT keyword is not valid unless the MGRADDR command included the AGENT keyword.

System Action: Processing continues. User Response: If required, re-issue the MGRADDR command with compatible operands.

0599W NO MORE xxxx DATES DEFINED Explanation: No more special days were defined past the last used day. System Action: If the date was not a holiday, the schedule element cannot be cycled

any more. If the date was a HOLIDAY, the date criteria is ignored. User Response: Extend the special day definition.

0600E INCOMPLETE DATE/TIME SPECIFICATION Explanation: A date and time specification did not contain sufficient information

to complete the definition. System Action: The date and time is flagged as in error. User Response: Respecify the date and time.

0601E NO MORE xxxx DATES DEFINED Explanation: No more special days were defined past the last used day. System Action: If the date was not a holiday, the schedule element cannot be cycled

any more. If the date was a HOLIDAY, the date criteria is ignored. User Response: Extend the special day definition.

0602E DATE xxxx NO LONGER DEFINED Explanation: An Event definition contained reference to a special day that was no

longer defined. System Action: The schedule element cannot be cycled any more. User Response: Redefine the Event so as to avoid the special day, or define the

special day.

0603E SYSTEM CLOCK NON-OPERATIONAL Explanation: The system clock is not operational. System Action: Depends on which component detected the error. User Response: ESP should be brought down and restarted when the CPU clock is

restored.

0604E INVALID DATE/TIME SPECIFICATION Explanation: An invalid parameter was detected on the date/time specification. For

example, 84.367 is invalid as no year can have 376 days. System Action: The specification is flagged as in error. User Response: Respecify the date and or time.

0605E INCONSISTENT DATE PARAMETERS Explanation: Inconsistent parameters were detected on the date/time specification.

Messages and Codes

ESP-5.4-MC-03 89

For example, 30FEB1984 is inconsistent, as February contains 29 days in 1984.

System Action: The specification is flagged as in error. User Response: Respecify the date and or time.

0606E NO DATE SPECIFIED Explanation: No data recognizable as a date or time were specified where expected. System Action: The specification is flagged as in error. User Response: Respecify the date and or time.

0607E SYNTAX ERROR STARTING AT 'xxxx' Explanation: An unrecognizable parameter was detected in a date/time specification. System Action: The specification is flagged as in error. User Response: Respecify the date and or time.

0608E INVALID CONVERSION REQUEST Explanation: This is probably an internal logic error. System Action: The time conversion request is denied. User Response: Notify your software support personnel.

0609E PARAMETER STARTING 'xxxx' NOT VALID IN SPECIFIED CONTEXT Explanation: A keyword or parameter was entered in a time schedule specification.

However, the keyword or parameter was not contextually valid. System Action: The time schedule element is treated as an error. User Response: Re-enter the time schedule correctly. The parameters might need to be

specified in a different order.

0610E SCHEDULE STATEMENT INCOMPLETE Explanation: PARAMETER SPECIFICATION IN A TIME OR SCHEDULE STATEMENT

ENDED PREMATURELY.

System Action: THE SPECIFICATION IS IGNORED. User Response: RETYPE THE SCHEDULE STATEMENT IN FULL.

0611E INTERNAL FORMAT ERROR IN TIME ELEMENT Explanation: The time conversion routine found an error in a time schedule element.

This could be due to an internal logic error or to the corruption of a disk resident time element due to an I/O error.

System Action: The time conversion request is not processed. User Response: Notify your software support personnel.

0612E NO MORE COMPLETE xxxx PERIODS DEFINED Explanation: A schedule specification was made referring to or requiring the last

period within another period. No more complete "xxxx" periods were found. A complete period is a period which ends on or before the end of the bounding period.

System Action: The schedule cannot be computed any further. User Response: Check the period definitions.

90 ESP-5.4-MC-03

0613E INVALID SCHEDULE TERM USAGE Explanation: A multiple schedule request was made with a schedule specification

that did not include an explicit or implicit iteration algorithm. System Action: The schedule request is not processed. User Response: You should include enough information to provide an iteration

algorithm.

0614E SPECIFIED INTERVAL INVALID IN CURRENT CONTEXT Explanation: An interval was specified when using special days or days within

periods. This function is not currently supported. System Action: The schedule request is not processed. User Response: Correct the schedule specification.

0615E REQUESTED OPTION NOT SUPPORTED IN CURRENT CONFIGURATION

Explanation: You requested a time or schedule option that is only supported with the extended scheduling option installed.

System Action: The request cannot be completed. User Response: Respecify the schedule or time statement omitting the unsupported

parameters. If this is inconvenient, install the extended scheduling option.

0616E Auxiliary address space initialization failed Explanation: During the initialization of an auxiliary address space, an

unexpected error occured during processing of the required STEPLIB data sets. Register 2 indicates the type of error. If register 2 is positive, then a dynamic allocation error occured. A message should appear in the system log describing the error. Register 2 is the SVC 99 return code. Register 3 contains the SVC 99 verb in bits 8-15, and register 4 contains the error code in bits 0-15 and the information code in bits 16-31. If register 2 is negative, then the OPEN failed.

System Action: The auxiliary address space does not initialize, but abends instead. User Response: Contact Cybermation technical support. Have the registers at the

time of the error available.

0617I Invalid environment for CYBSS007-Valid only in a system address space Explanation: The auxiliary address space bootstrap module was executed, but the

environment was not a system address space. System Action: The module issues ABENDU0913. No other action is taken. User Response: Do not attempt to execute CYBSS007 yourself.

0618W Duplicate auxiliary address space Explanation: During the initialization of an auxiliary address space, it was found

that an auxiliary address space was already active for the subsystem. This should not occur, as a check is made prior to issuing the start request.

System Action: The duplicate auxiliary address space does not initialize, but abends

Messages and Codes

ESP-5.4-MC-03 91

instead. User Response: None.

0619E The length of the following command exceeds 32763 characters: Explanation: A command was encountered that exceeds 32763 characters, the maximum

allowed. System Action: The requested command is rejected, processing stops. User Response: Divide the long command into several shorter commands.

0620E DATA SET xxxx NOT CATALOGUED Explanation: A reference was made to a data set that was not in the catalog. This

could also occur when a generation number was specified for a catalogued data set that was not a GDG.

System Action: The allocation of the data set fails. User Response: Ensure the correct data set name is specified.

0621E CATALOG ERROR CODE nn FOR DATA SET xxxx Explanation: An error code was given by catalog management routines after an

attempted LOCATE for a data set. System Action: The allocation of the data set fails. User Response: Error codes are documented in the manual System Messages and Codes.

0622E NO DATA SET/DDNAME SPECIFIED FOR FREE REQUEST Explanation: The data set allocation/unallocation routine was passed invalid

parameters. This would probably be due to an internal logic error. System Action: The allocation/unallocation will not be performed. User Response: Notify the software support group.

0623E DATA SET xxxx IS NOT A MEMBER OF A GENERATION GROUP Explanation: A generation number was specified for a data set that was not part of a

generation data group. System Action: The condition is treated as data set not found. User Response: Ensure the correct data set was specified. A generation data group base

should be defined.

0624E Unable to open data set xxxx Explanation: The data set could not be opened. This message will normally be

preceded by one or more messages detailing the reasons. System Action: The requested function could not be completed. User Response: Rectify the cause of the failure.

0625E I/O ERROR ON xxxx,yyyyzzzz,aaaa Explanation: An I/O error occurred while attempting to access this data set. System Action: The requested function is not completed. User Response: Try again. If the problem persists, ask your ESP System Administrator

to repair this data set.

92 ESP-5.4-MC-03

0626E xxxx Explanation: An error occurred while processing a slotted data set. System Action: The requested I/O service was not performed. User Response:

0627E ERROR LOADING MODULE xxxx FOR yyyy COMMAND Explanation: A command processor module "xxxx" was invoked to process the command

identified by "yyyy". The module could not be loaded. System Action: The command is aborted. User Response: Ensure that the specified module is placed in an accessible library.

The error could also be caused if an invalid module name was entered into a command lookup table.

0628W INVALID COMMAND NAME SYNTAX Explanation: This command name has invalid syntax. System Action: The command was not executed. User Response: Correct the command and try again.

0629E Result exceeds maximum value of 50000 Explanation: The result of calling DAYS_BETWEEN with a restrictor is greater than

the maximum allowed value of 50000. System Action: The request is abandoned, and no value is returned. User Response: Ensure that such calls to this function produce results in the

allowed range.

0630E Result exceeds maximum value of 50000 Explanation: The result of calling the REXX built-in function DAYSBETW is greater

than the maximum allowed value of 50000. System Action: The request is abandoned, and no value is returned. User Response: Ensure that such calls to this function produce results in the

allowed range.

0631W Data set xxxx is unformatted Explanation: The specified data set had not been previously formatted. This

might be expected the first time the data set is used. System Action: This message will normally be followed by another indicating

what action would be taken. User Response: Note the message that follows.

0632C MGRADDR Command Options Explanation: Response to MGRADDR HELP command.

The MGRADDR command options are displayed. System Action: Processing continues. User Response: None.

0633E Invalid record header encountered, Slot nn, data set xxxx Explanation: A record on the specified data set contained invalid data. The

Messages and Codes

ESP-5.4-MC-03 93

slot number of the record is displayed. System Action: The operation requiring the record in question will fail. This

message will be followed by one indicating what processing will take place.

User Response: Note the message that follows.

0634E Attempt made to write too long a record to data set xxxx, Size=nnnn, Maximum=mmmm

Explanation: An attempt was made to store a record exceeding the maximum supported. This is normally due to a logic error.

System Action: This message will be followed by one indicating what processing was occurring at the time.

User Response: Note the message that follows. Notify your software support personnel.

0635E Record too large for input buffer, data set xxxx, Slot nn Explanation: An attempt was made to read a record whose length exceeds the

input buffer length. This may be due to a logic error. System Action: This message will be followed by one indicating what processing

was occurring at the time. User Response: Note the message that follows. Notify your software support

personnel.

0636E ATTEMPT MADE TO FREE AN INVALID SLOT NUMBER Explanation: An attempt was made to free a slot from the track file. The slot

number was out of the range of the data set. This could be due to a logic error, or if a record on the file had become corrupted.

System Action: This message will be followed by one indicating what processing was occurring at the time.

User Response: Note the message that follows. Notify your software support personnel.

0637E Insufficient free slots in data set xxxx Explanation: An attempt was made to add a record or to extend an existing

record in the data set identified in the message. System Action: The update or add request fails. This message will be followed

by another message giving some more information on the type of data lost.

User Response: Check the description for the message that follows.

0638E Attempt made to write to slot 0, data set xxxx Explanation: While writing a (new or updated) record to a slot file, one of

the slots belonging to the record has slot number 0. This is illegal, since slot 0 is the file control record for the file. Such a situation should not arise, and is probably due to a logic error.

System Action: The record in question is not written, and the processing in progress is abandoned.

User Response: Contact Cybermation Technical Support.

94 ESP-5.4-MC-03

0639E INVALID DAB OPERATION, DATA SET IS NOT OPEN Explanation: An internal logic error has occurred. An attempt has been made to

access a VSAM data set, but the data set is not currently open. System Action: The operation is not performed. This message is returned to the

caller as an I/O error. User Response: Please contact Cybermation for further assistance.

0640E INVALID FRB OPERATION, DATA SET IS NOT OPEN Explanation: An internal logic error has occurred. An attempt has been made to

access a slotted data set, but the data set is not currently open. System Action: The operation is not performed. This message is returned to the

caller as an I/O error. User Response: Please contact Cybermation for further assistance.

0641E IEFSSREQ SSVI function SSOBRETN=nn, Subsystem=xxxx Explanation: A request to obtain version information from MVS subsystem xxxx failed

with an unexpected SSOB return code nn. System Action: Processing continues. User Response: Should never happen. If it does, attempt to determine the cause of the

problem and, if possible, correct it. If ESP/WM issued this message during initialization, it should be recycled after the problem is corrected.

0642E IEFSSREQ error return code nn, Subsystem=xxxx Explanation: A request to obtain version information from MVS subsystem xxxx failed

with an unexpected return code nn. System Action: Processing continues. User Response: Should never happen. If it does, attempt to determine the cause of the


0643E Subsystem xxxx {does not support SSI function yyyy|not active|not defined to MVS}

Explanation: A request to obtain version information from MVS subsystem xxxx failed for the reason specified in the message.

System Action: Processing continues. User Response: Should never happen. If it does, attempt to determine the cause of the


0644E Subsystem xxxx does not support JES_NODE|JES_MEMBER_NAME keyword

Explanation: A request to obtain the JES node name or the JES member name from MVS subsystem xxxx failed.

System Action: Processing continues, but without knowledge of the requested JES node

Messages and Codes

ESP-5.4-MC-03 95

name or JES member name. User Response: If MVS subsystem xxxx is a Job Entry Subsystem (JES2 or JES3) this

should never happen. If it does, try to determine the cause and, if possible, correct it. If ESP/WM issued this message during initialization, it should be recycled after the problem is corrected.

0646E Null token passed to event service Explanation: A null input parameter instead of an address was passed to the event

wait/post CPE service. If this ever occurs it will most likely be during ESP/WM initializtion.

System Action: The requesting task terminates abnormally with code U1203. User Response: Internal logic error. Should never happen.

Contact Cybermation support.

0647E Event token xxxxxxxx at yyyyyyyy invalid Explanation: Input parameter xxxxxxxx at location yyyyyyyy passed to the event

wait/post CPE service is invalid. If this ever occurs it will most likely be during ESP/WM initializtion.

System Action: The requesting task terminates abnormally with code U1203. User Response: Internal logic error. Should never happen.


0648E ERROR OCCURRED OPENING TRACE DATA SET Explanation: The trace data set could not be opened. System Action: The trace function is not activated. User Response: Check the previous message for further information regarding this

error.

0649E INVALID ROSCOE LIBRARY MEMBER NAME, xxxx Explanation: ROSCOE library member names must be a prefix followed by a name. The

prefix is at most three characters, while the name is at most eight. They are separated by a period.

System Action: The requested function was not completed. User Response: Correct the member name and try again.

0650I TRACE PROCESSING INITIALIZED Explanation: The trace requested by a TRCINIT command has been successfully

initialized. System Action: Tracing will be enabled. User Response: None.

0651E INSUFFICIENT VIRTUAL STORAGE FOR TRACE BUFFERS Explanation: The TRACEDEF command or initialization statement was specified. The

specified or default trace buffer size and count exceeded available virtual storage.

System Action: The TRACEDEF command is not processed. User Response: Specify a smaller buffer count, or increase the virtual region size

for the subsystem.

96 ESP-5.4-MC-03

0652E ERROR OCCURRED ALLOCATING/OPENING TRACE DATA SET Explanation: A trace data set could not be allocated. System Action: The trace function is not activated. User Response: Check the previous message for further information regarding this

error.

0653E ERROR ATTACHING TRACE SUBTASK Explanation: The TRCINIT function could not be started. System Action: The trace function is not activated. User Response:

0654E TRACE ALREADY INITIALIZED Explanation: The trace data set is already initialized. System Action: The requested function is not completed. User Response: Use TRACE REUSE to reuse the trace data set.

0655W TRACE NOT CURRENTLY INITIALIZED Explanation: The trace function is not available, since it wasn't defined in the ESP

initialization parameters. System Action: The requested function is not completed. User Response: Add a TRACEDEF statement to the ESP initialization parameters.

0656E INVALID TRACE ID ELEMENT/RANGE SPECIFIED Explanation: The SET or RESET parameter was invalid. System Action: The command was not executed. User Response: Correct the SET or RESET parameter and try again.

0657I TRACE RECORDING ON DATA SET xxxx Explanation: The trace function has been activated. System Action: User Response:

0658I DATA SET xxxx FULL Explanation: The trace data set is full. System Action: ESP has attempted to switch trace data sets. User Response:

0659C TRACE STATUS Explanation: The status of the trace data sets is being displayed. System Action: User Response:

0660S UNABLE TO ATTACH A SUBTASK, MONITOR ENDED Explanation: ESP is unable to initialize itself in the ROSCOE environment. System Action: ESP is not available. User Response: Check the status of the ROSCOE system. A storage shortage might be

causing this problem. If the problem persists, please contact

Messages and Codes

ESP-5.4-MC-03 97

Cybermation for further assistance.

0661S MONITOR SUBTASK ABEND Sxxxx, Uyyyy Explanation: ESP has abended under the ROSCOE subtask. System Action: ESP is no longer available to ROSCOE users. User Response: Check the status of the ROSCOE system. A storage shortage might be

causing this problem. If the problem persists, please contact Cybermation for further assistance.

0662E TCBTOKEN error, Return=<rc>, DataSpace=<name> Explanation: A request to obtain the job step TCB token failed while attempting to

a create data space. <name> specifies the name of the data space. <rc> specifies the error return code of the job step TCB token obtain request.

System Action: The data space is not created. User Response: Should never happen. Contact Cybermation support.

0663E ALESERV ADD error, Return=<rc>, DataSpace=<name> Explanation: A request to add a data space to the address space access list failed.

<name> specifies the name of the data space. <rc> specifies the error return code of the request to add the data space to the address space access list.

System Action: The data space is created but cannot be accessed. User Response: Should never happen. Contact Cybermation support.

0664S xDspace Create|Delete|Extend|Release|Load|Out, CBID=X'<hexid>'(<ident>) invalid, must be X'C4E2C4C1|E2E2E2C1'(DSDA|SSSA)

Explanation: A data space request has been issued with an invalid input parameter identifier. <hexid> specifies the invalid parameter identifier in hexadecimal. <ident> specifies the invalid parameter identifier in EBCDIC.

System Action: The data space request fails. User Response: Internal logic error. Should never happen.


0665E DspServ Create|Delete|Extend|Release|Load|Out error, Return=<rc>, Reason=X'<reason>', Name=<name>, Blocks={+}<number>{, Maximum=<maxnum>}

Explanation: A data space request error has occurred. <name> specifies the data space name. <rc> specifies the data space space request (DSPSERV) error return code. <reason> specifies the data space space request (DSPSERV) error reason code. <number> specifies the data space 4K unit size or the requested 4K unit extension count if preceded by a plus (+) sign. <maxnum> specifies the maximum permissible 4K unit data space size.

98 ESP-5.4-MC-03

System Action: The data space request fails. User Response: If error message does not give sufficient information to correct the

problem, and it persists, then contact Cybermation support.

0666S xHspace Create|Delete|Extend|Release|SRead|SWrite, CBID=X'<hexid>' (<ident>) invalid, must be X'C8E2C4C1|C8E2D9C1|E2E2E2C1'(HSDA|HSRA|SSSA)

Explanation: A hiperspace request has been issued with an invalid input parameter. <hexid> specifies the invalid parameter identifier in hexadecimal. <ident> specifies the invalid parameter identifier in EBCDIC.

System Action: The hiperspace request fails. User Response: Internal logic error. Should never happen.


0667E DspServ|HspServ Create|Delete|Extend|Release|SRead|SWrite error, Return=<rc>, Reason=X'<reason>', Name=<name>, Blocks={+}<number>{, Maximum=<maxnum>}

Explanation: A hiperspace request error has occurred. <name> specifies the hiperspace name. <rc> specifies the hiperspace space request (DSPSERV) error return code. <reason> specifies the hiperspace space request (DSPSERV) error reason code. <number> specifies the hiperspace 4K unit size or the requested 4K unit extension count if preceded by a plus (+) sign. <maxnum> specifies the maximum permissible 4K unit hiperspace size.

System Action: The hiperspace request fails. User Response: If error message does not give sufficient information to correct the

problem, and it persists, then contact Cybermation support.

0668E <name> error{, Invalid FSQE at <address>}, <reason> Explanation: Verification of a space object indicated that it is incorrectly

formatted. If <name> specifies NETQUEUE under ESP/WM, it either means that the NETQUEUE command in the LOADNET initialization file specified a linear data set that was not the Network Delivery Services (NDS) message queue data set, or that the Network Delivery Services (NDS) message queue data set is corrupted. If the message specifies an invalid FSQE address, then the space object is corrupted. <name> specifies the space object name. If it specifies NETQUEUE, then it represents the Network Delivery Services (NDS) message queue data set. <address> specifies an FSQE (space object free area) address. <reason> specifies the reason the space object is incorrectly formatted.

System Action: If the space object represents a Network Delivery Services (NDS) data set (<name> = NETQUEUE), then this message is followed by message 3352E and action message prompt 3354A.

User Response: For the NETQUEUE space object of an ESP/WM subsystem, if the data set specified in the NETQUEUE command in the LOADNET initialization file

Messages and Codes

ESP-5.4-MC-03 99

is not a Network Delivery Service (NDS) message queue data set, then reply P to message action prompt 3354A to shutdown ESP/WM. Then correct the NETQUEUE command and restart ESP/WM. For the NETQUEUE space object of an ESP/WM subsystem, if the Network Delivery Service (NDS) message queue data set is corrupted and it cannot be repaired with a zap, then reply F to message action prompt 3354A to request a cold reformat of the data set. Caution: Do not reply F to message action prompt 3354A if the NETQUEUE command in the LOADNET initialization file specifies a linear data set that is NOT the Network Delivery Services (NDS) message queue data set because the data sets's contents will be lost.

0669W Time RetCode=<rc>, <name> space object format date and time unavailable Explanation: While formatting space object <name>, an attempt to determine the

current date and time failed with error return code <rc>. <name> specifies the space object name. If it specifies NETQUEUE, then it represents the Network Delivery Services (NDS) message queue data set. <rc> specifies the error return code of the TIME macro request.

System Action: Space object <name> is formatted with its format time field containing zeros. Space object display requests such as the NETWORK QUEUE DISPLAY SPACE command for the Network Delivery Services (NDS) message queue data set will show the format date as 0000/00/00 and the format time as 00:00:00.

User Response: None. Should never happen.

0670C <name> Space Object Explanation: Response to space object <name> display request.

If <name> SPECIFIES NETQUEUE (the Network Delivery Services message queue data set, then response to NETWORK QUEUE DISPLAY SPACE command. <name> specifies the space object name. If it specifies NETQUEUE, then it represents the Network Delivery Services (NDS) message queue data set.

System Action: The specified space object's attributes and space usage data are displayed.


0671S xSpace Get|Free|Extend{, {Name=<name>|Address=<freeaddr>}}, Length=<length>{, Invalid FSQE at <fsqeaddr>|<reason>}

Explanation: A severe error in a space object has been detected. <name> specifies the space object name. <freeaddr> specifies the space object area free request address. <length> specifies the space object area API request length. <fsqeaddr> specifies an FSQE (space object free area) address. <reason> specifies the reason for the space object error.

System Action: The task is abnormally terminated with code U1111. User Response: Contact Cybermation support.

100 ESP-5.4-MC-03

A reformat may be required if the space object is a data set (for example the Network Delivery Services (NDS) message queue data set if <name> specifies NETQUEUE) and the reason for the error is a data corruption.

0672I BufSize=aaaa{K|M}, AsBufNo=bb{, HsBufNo=cc, HsName=dddddddd}, Used=ee

Explanation: Response to LISTHBSF or LHSBH command to display HiperSpace Buffer Swap Facility (HBSF) status. HBSF is used by ESP/WM to process subsystem request commands from ESP/WM clients. aaaa specifies the HBSF buffer size in kilobyte (K) or megabyte (M) units. bb specifies the current HBSF address space buffer number. cc specifies the hiperspace buffer count. dddddddd specifies the hiperspace name. ee specifies the number of HBSF buffers currently in use.


0673E xHbsf Create|Delete|GetSize|GetBuf|FreeBuf|RelBuf|Display, <reason> Explanation: A HiperSpace Buffer Swap Facility (HBSF) request failed.

HBSF is used by ESP/WM to process subsystem request commands from ESP/WM clients. <reason> specifies the reason for the HBSF failure.

System Action: Processing continues but the ESP/WM subsystem request cannot be serviced.

User Response: If the problem persists, contact Cybermation support.

0674S xHbsf Create|Delete|GetSize|GetBuf|FreeBuf|RelBuf|Display, <reason> Explanation: A HiperSpace Buffer Swap Facility (HBSF) request failed.

HBSF is used by ESP/WM to process subsystem request commands from ESP/WM clients. <reason> is the reason for the HBSF failure.

System Action: The task is abnormally terminated with code U1112. User Response: Contact Cybermation support.

0675I Update successful Explanation: New or modified encryption key has been stored successfully. System Action: N/A. User Response: None required.

The key will be available for agent communications next time the agent definitions are loaded.

0676E <keyword> must be specified Explanation: CRYPTKEY command was entered without a keyword that is required. System Action: Command is rejected. User Response: Reenter the command with all necessary parameters.

Messages and Codes

ESP-5.4-MC-03 101

0677W No entries found to match your criteria Explanation: CRYPTKEY LIST command found no keys matching the request. System Action: User Response: Not required.

0678E Error retrieving encryption key named <kkkk> Explanation: Agent definition file refers to a key named <kkkk>, which was not

found in key repository. System Action: New agent definitions are not loaded. User Response: Veryfy the spelling of key name in agent definition file or define

the required key using CRYPTKEY command. Once the problem is corrected, issue LOADAGDF command again.

0679E Key name is mutually exclusive with explicit key Explanation: A statement in agent definition file specifies both an encryption key

and a key name to use for lookup in key repository. The two are mutually exclusive.

System Action: New agent definitions are not loaded. User Response: Correct the statement by removing either the explicit key or the key

name. Reenter the LOADAGDF command.

0680E UNABLE TO LOAD ISPF INTERFACE MODULE Explanation: The ISPLINK module could not be loaded. System Action: The ISPF interface cannot be supported. User Response: Ensure that your LOGON procedure specifies a STEPLIB library that

contains the ISPLINK module.

0681E ERROR WITH ISPF INTERFACE Explanation: An unknown error occurred inside the ISPF interface module. System Action: The ISPF interface cannot be supported. User Response: Logon to TSO again and retry.

0682E UNABLE TO LOAD ISPEXEC MODULE Explanation: The ISPEXEC module could not be loaded. System Action: The ISPF interface cannot be supported. User Response: Ensure that your LOGON procedure specifies a STEPLIB library that

contains the ISPEXEC module.

0683E SEVERE ERROR FROM ISPF INTERFACE Explanation: A return code of 20 was returned by the ISPF interface module. System Action: The ISPF interface cannot be initialized. User Response: Logon to TSO again and retry.

0684W No matching entries found Explanation: A request to list encryption keys found no entries that fit

the selection criteria. System Action:

102 ESP-5.4-MC-03

User Response: Not required.

0685E Duplicate key entry Explanation: An attempt was made to define an encryption key with a name that

already exists in the repository. System Action: The request is denied. User Response: Either use a different name or change the request from DEFINE to

UPDATE.

0686E Key does not match, update refused Explanation: An attempt was made to modify an encryption key, but the supplied old

key was wrong. To update a key, the user either needs the PASSWORD UPDATE authority or must provide the correct old key.

System Action: The request is denied. User Response: Correct the command and retry.

0687E You are not authorized to update key entries Explanation: A request to modify an encryption key was denied by security system.

To update a key, the user either needs the PASSWORD UPDATE authority or must provide the correct old key.

System Action: The request is denied. User Response: Either provide the correct old key or ask the system administrator

for assistance.

0688E Specified key entry not found Explanation: A request to modify or delete an encryption key, but the key entry was

not found in the repository. System Action: User Response:

0689E Above error occurred during CKDE initialization Explanation: An error occurred during initialization of key repository service.

A preceding message explains the error. System Action: Key repository service will not be available. User Response: The error described by the preceding message must be corrected.

0690E Insufficient checkpoint/queue file space for event execution request Explanation: The system attempted to queue an event execution request either for a

TRIGGER command or because a new event with scheduled execution was created. The request could not be queued because the file specified in the message was full.

System Action: The event execution request is not queued. User Response: Trigger the event again when space becomes available in the file.

The checkpoint and queue file contain mainly transient information that should be processed quickly by event initiators or tracking manager. A full file may indicate a problem with one of these components (halted tracking or event execution).

Messages and Codes

ESP-5.4-MC-03 103

0691W Processing of <n> events ended abnormally in the previous session Explanation: During a warm start, ESP/WM found a list of events whose processing

began but did not complete during the previous run. The number of entries on the list is <n>.

System Action: The individual entries will be described by ESP692I messages. User Response: Review the ESP692I messages and verify whether the individual events

have to be reprocessed.

0692I Event <event data> Explanation: The event described in this message was executing when ESP/WM abended.

Depending on the timing of the abend, the target actions, such as submission of a job or building of an application, may be completed or not. The <event data> may be not available if the ESP checkpoint was full when the event's processing started. In this case the audit log has to be examined to find the event description.

System Action: None. User Response: Examine the results of the interrupted event execution and re-trigger

the event (or resubmit the affected job) if necessary.

0693E Explanation: A cell size in the queue of XMCs does not correspond to a known

cell size - must be one of: JOBSTART, STEPEND or JOBEND. System Action: TCELL command will be ignored. User Response: Report problem to Level 2 Support.

0694E Invalid TIMEREF adjustment: <adjustment string> Explanation: The value of TIMEREF parameter of a TIMEZONE statement is invalid. System Action: Message ESP802A prompts operator to correct the error. User Response: Respond to message ESP802A.

0695E STRING STARTING 'xxxxx' HAS MULTIPLE RANGES AND ONE ORDINAL EXCEEDS 31

Explanation: A time schedule specification contains multiple ranges and at least one ordinal value is greater than 31 (e.g. 32ND, 40TH). Larger ordinals are allowed as long as only one range is specified within a particular level of a SCHEDULE statement (where 'level' is one of DAY, MONTH, YEAR,etc.)

System Action: The time schedule element is treated as an error. User Response: Split up the SCHEDULE statement into one or more statements containing

one range each for a given level.

0696A CCCHK aa bb cc dd CC=ee=X'ff' Reply: C=Fail/Continue, S=Fail/Stop, O=OK/Continue

Explanation: A job step terminated and its completion code matched the conditions specified in a CCCHK statement that specifies ASK. aa, bb, ... ff represent:

104 ESP-5.4-MC-03

aa FAIL | OK (specified in the matching CCCHK statement; the default is OK) bb job name cc job number dd stepname ee decimal completion code ff hexadecimal completion code

System Action: An operator is prompted for an action. User Response: Reply C, S, or O.

0697E Allocation of CCCHK ASK work area failed; S=Fail/Stop assumed. Explanation: A job step terminated and its completion code matched the

conditions specified in a CCCHK statement that specifies ASK, however a subroutine of the ESP Workload Manager's SMF intercept was unable to allocate a required temporary work area. The most likely cause would be a shortage of private-area virtual memory.

System Action: ESP Workload Manager terminates the execution of the job. User Response: None.

0699E CANNOT GO BEYOND DECEMBER 31, 2040. Explanation: A date was calculated which was past December 31, 2040. This date is

last date supported. System Action: The current function is terminated. User Response: Change the date calculation so the result will not be beyond the last

supported date.

0701E DOs exceed ENDDOs in application Explanation: DOs exceed ENDDOs in application System Action: The command is ignored. User Response: Correct the CLANG statements as appropriate

0702E Too many DO statements Explanation: More than 255 nested DO statements System Action: The command is ignored. User Response: Correct the CLANG statements as appropriate

0703E ELSE not preceded by IF at same level Explanation: ELSE not preceded by IF at same DO/ENDDO level System Action: The command is ignored. User Response: Correct the CLANG statements as appropriate

0704E Too many ENDDO statements Explanation: More ENDDO statements than DO statements in application System Action: The command is ignored. User Response: Correct the CLANG statements as appropriate

705I Current message prefix is <prefix> Explanation: This message is displayed when "oper msgprfx" command without operands

Messages and Codes

ESP-5.4-MC-03 105

is issued by TSO users. System Action: System just displays the current message prefix and does no changes. User Response: User can change the message prefix by supplying it as an operand to

the command, ex. "oper msgprfx MyPrefix"

0706I DATE ADVANCED nnxxxx TO yyyy Explanation: A date/time specification included both a day of week and a day of the

month, where the day of the month did not correspond to the day of the week.

System Action: The date is advanced to the next date corresponding to the day of week. User Response: Ensure that this is what you intended, otherwise respecify the date.

0707E Insufficient CSA to load time zone table Explanation: ESP could not obtain enough storage in CSA to load the time zone table. System Action: The time zone table. Processing continues without it. User Response: The subsystem can be stopped and restarted when the CSA shortage is

relieved.

0710S ASCRE for auxiliary failed, return code n, reason code m Explanation: CPE attempted to start the auxiliary address space by invoking

the MVS ASCRE service. The IBM service failed unexpectedly. System Action: The subsystem continues initialization without an auxiliary

address space. Certain functions will not be available. User Response: Probable system error. Investigate the reason for the ASCRE error

and contact IBM or Cybermation for technical support, as appropriate.

0720W UNABLE TO ALLOCATE xxxx, S99 ERROR CODE X'yyyy', INFO CODE X'zzzz'

Explanation: An error occurred during a dynamic allocation request. System Action: This message is followed by another message indicating the action

taken. User Response: Take note of the following message.

0721W UNABLE TO ALLOCATE xxxx, VOLUME OFFLINE Explanation: An error occurred during a dynamic allocation request due to a

required volume being offline. System Action: This message is followed by another message indicating the action

taken. User Response: Take note of the succeeding message.

0722W DATASET xxxx NOT CATALOGUED Explanation: An error occurred during a dynamic allocation request due to a data

set not being catalogued. System Action: This message is followed by another message indicating the action


106 ESP-5.4-MC-03

0723W UNABLE TO GET EXCLUSIVE ALLOCATION TO DATASET xxxx Explanation: A data set that is needed exclusively was already allocated to another

user. System Action: This message is followed by another message indicating the action


0724W UNABLE TO GET SHARED ALLOCATION TO DATASET xxxx Explanation: A data set that is needed for shared access is allocated exclusively

to another user. System Action: This message is followed by another message indicating the action


0725W DATASET xxxx NOT ON {CATALOGUED VOLUME | VOLUME yyyy} Explanation: A data set was not found on the volume as catalogued or explicitly

specified. System Action: This message is followed by another message indicating

the action taken. User Response: Take note of the succeeding message.

0727W UNABLE TO FREE xxxx, S99 ERROR CODE X'yyyy', INFO CODE X'zzzz'Explanation: An error occurred while performing a dynamic unallocation. System Action: This message is followed by another message indicating the action


0728E UNABLE TO PERFORM TASK SWITCH Explanation: ESP tried to switch to a subtask to perform an allocation request.

The task switch failed. System Action: This message is followed by another message indicating the action


0729E UNABLE TO REVERT TO MAIN TASK Explanation: After an allocation was performed on a subtask, the routine was unable

to rejoin the main task. System Action: This message is followed by another message indicating the action


0730I Manager address xxxx, Home IP address yyyy Explanation: Response to MGRADDR, MGRADDR DISPLAY or MGRADDR LIST command.

The manager address xxxx and home IP address are displayed. If the AGENTDEF file has a "MANAGER TCPIP(xxxx)" statement, then xxxx is the manager address. If the AGENTDEF file has a "MANAGER TCPIP" statement, then the manager

Messages and Codes

ESP-5.4-MC-03 107

manager address is the home IP address. AGENTDEF file commands are processed by the LOADAGDF command.


0731I STARTING BACKUP OF HISTFILE xxxx Explanation: A scan of an History data set has begun. This is as response to a

BKUPHIST command or through the normal schedule. System Action: If a backup data set is allocated, a sequential copy of the History

data set will be made. If this is a scheduled scan, the schedule will be built.

User Response: None

0732I Manager address xxxx{:yyyy} notify scheduled to zzzz agent{s} Explanation: Response to MGRADDR AGENT command.

The central manager host name or IP address xxxx (and port yyyy if specified) was scheduled to be sent to a total of zzzz agents. Only agents that are reachable on the network will actually receive the manager address.


0733I HISTFILE BACKUP ENDED FOR xxxx, nn RECORDS BACKED UP Explanation: A BACKUP or SCAN of an History data set has completed. System Action: Processing continues. User Response: None.

0734S DATASET NOW SUSPENDED Explanation: An error has occurred which resulted in the suspension of the History

data set. System Action: This message will have been preceded by another message describing the

error. The History data set will not be accessed until the HISTFILE command is issued.

User Response: Once the problem with the History data set is corrected, the data set can be reactivated through the HISTFILE OPEN command.

0735E ERROR OPENING BACKUP DATASET xxxx Explanation: An error occurred while opening a backup data set for output, during a

History data set backup. System Action: The backup copy will not be taken. The schedule building function will

proceed. User Response: The message will describe the error condition. After the problem is

diagnosed and corrected, the BKUPEVS command should be issued to take a backup.

0736E ERROR WRITING TO BACKUP xxxx Explanation: An error occurred while writing to the backup data set during an

History data set backup or scan. System Action: The backup operation will be suspended. If a SCAN was also being

108 ESP-5.4-MC-03

performed, it will continue. User Response: The message will describe the error condition. After the problem is


0737E ERROR CLOSING BACKUP DATASET, xxxx Explanation: An error occurred while closing the backup data set for a History

file. System Action: Processing continues. User Response: The message will describe the error condition. After the problem is


0739E HISTFILE xxxx BACKUP BYPASSED DUE TO SUSPENDED STATE Explanation: A scheduled SCAN or BACKUP of the History data set was attempted while

the data set was in the suspended state. System Action: The SCAN or BACKUP is deferred until the data set is reopened. User Response: When the problem with the data set is corrected, reopen the data set

with the HISTFILE command.

0740I STARTING BACKUP OF JOB INDEX Explanation: A backup of the Job Index data set has begun. System Action: The Job Index data set is backed up. User Response: None.

0742E BACKUP OF JOB INDEX DATASET ENDED WITH ERRORS Explanation: A previous error has caused termination of the Job Index data set

backup. This message will have been preceded by another message describing the error.

System Action: The backup is terminated. Other processing continues. User Response: Notify your system support personnel. The backup can be performed

again after the problem has been corrected.

0743I JOB INDEX DATASET BACKUP ENDED, nn RECORDS BACKED UP Explanation: A backup of the user definition data set has completed successfully. System Action: Processing continues. User Response: None.

0744E ERROR CLOSING JOB INDEX BACKUP DATASET, xxxx Explanation: An error occurred while closing the backup data set. The backup may

not be usable. System Action: Processing continues. User Response: The message text more fully describes the error. If the error is

correctable, the backup can be may be executed again.

0745E ERROR OPENING JOB INDEX BACKUP DATASET xxxx Explanation: An error occurred while opening a backup data set for the Job Index

data set.

Messages and Codes

ESP-5.4-MC-03 109

System Action: The backup is not performed. User Response: Notify your system support personnel. Once the problem is resolved,

the backup should be executed again.

0746E ERROR WRITING TO JOB INDEX BACKUP xxxx Explanation: An error occurred while writing to the backup data set for the Job

Index data set. System Action: The backup is not completed. User Response: Notify your system support personnel. Once the problem is resolved,

the backup should be executed again.

0747E JOB INDEX DATASET BACKUP TIME WILL HAVE TO BE RESET Explanation: An error occurred when trying to compute the next time for a scheduled

backup. This message is preceded by a message describing the error. System Action: The next backup will not be placed in the schedule. User Response: Use the BKUPUSER command to set the scheduled backup time.

0748E NO BACKUP DATASET SPECIFIED FOR JOB INDEX DATASET Explanation: ESP attempted to take a backup of the Job Index data set. A backup

data set was not specified in the initialization parameters. System Action: The backup is not performed. User Response: The backup data set should be placed in the ESPPARM data set and ESP

restarted.

0749W FTP SMF119 not available on OS/390. SMF118 used. Explanation: The Communication Server that handles FTP on the host can be configured

to generate either SMF records 118 or SMF records 119 on z/OS. However, OS/390 only allows generation of SMF118 records. The OS/390 operating system has been detected, yet the request is for SMF119 records. The ESP Workload Manager will listen for SMF 118 records.

System Action: The default SMF 118 records will be "listened to" User Response: No action is required. To avoid seeing this message in the future,

please correct the initialization parameter.

0750W DATASET xxxx WAS IN THE SUSPENDED STATE Explanation: During a warm start, ESP found a data set that was previously in the

suspended state. System Action: The Event data set remains suspended. User Response: In order to activate the data set, use the EVENTSET command with the

OPEN keyword.

0751S DATASET xxxx NOW PLACED IN SUSPENDED STATE Explanation: An error occurred on an Event data set, causing it to be suspended.

This message will have been preceded by another message describing the error.

System Action: The Event data set will not be used. User Response: When the error has been corrected, use the EVENTSET OPEN command to

reactivate use of the data set.

110 ESP-5.4-MC-03

0752W EVENT DATASET xxxx EMPTY, WILL FORMAT Explanation: An uninitialized Event data set was opened. System Action: The data set will be formatted. User Response: None.

0753W EVENT DATASET xxxx HAS INCORRECT KEYLENGTH Explanation: An Event data set was defined with the wrong keylength. See the ESP

installation reference manual for the correct keylength. System Action: The data set is suspended. User Response: The Event data set should be redefined or modified through the ALTER

command of the IDCAMS utility.

0754W EVENT DATASET xxxx HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED

Explanation: The specified event data set had no valid control record. System Action: A control record will be added. User Response: None

0756S DATASET xxxx NOW PLACED IN SUSPENDED STATE Explanation: An error occurred on a history data set, causing it to be suspended.

This message will have been preceded by another message describing the error.

System Action: The history data set will not be used. User Response: When the error has been corrected, use the HISTFILE OPEN command to

reactivate use of the data set.

0757W HISTORY DATASET xxxx EMPTY, WILL FORMAT Explanation: An uninitialized history data set was opened. System Action: The data set will be formatted. User Response: None.

0758W HISTORY DATASET xxxx HAS INCORRECT KEYLENGTH Explanation: A history data set was defined with the wrong keylength. See the ESP

installation reference manual for the correct keylength. System Action: The data set is suspended. User Response: The history data set should be redefined or modified through the ALTER

command of the IDCAMS utility.

0759W HISTFILE xxxx HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED

Explanation: A history file was found to contain no control record. The control record is necessary to store backup information.

System Action: A control record will be built and written to the data set. User Response: None

Messages and Codes

ESP-5.4-MC-03 111

0760A SYSTEM CLOCK(S) INOPERATIVE, REPLY WHEN OPERATIONAL AGAIN OR CANCEL

ESP Explanation: ESP found the system clocks to be inoperative. System Action: ESP waits for a reply. User Response: Reply to this message when the clocks are operational again. If the

system needs to be brought down, you can cancel ESP.

0761W EVENT DATASET xxxx DOWNLEVEL, USE CONVERT UTILITY Explanation: An event data set was found to be created by an incompatible release

of ESP. System Action: The Event data set is put in the suspended state. User Response: Use the CONVERT command of the ESP utility processor.

0762E xxxx incompatible with yyyy Explanation: ESP encountered a DSTRIG event command that specifies at least two

incompatible operands xxxx and yyyy. System Action: The ESP event is suppressed. User Response: Correct the DSTRIG event command so that it does not specify any

incompatible operands. Then re-trigger the ESP event.

0763E xxxx incompatible with yyyy Explanation: ESP encountered a DSNAME application statement for a DSTRIG workload

object that specifies at least two incompatible operands xxxx and yyyy.

System Action: The ESP application is not built. User Response: Correct the DSNAME application statement so that it does not specify

any incompatible operands. Then re-trigger the event that invokes the ESP application.

0764E FTP trigger host name look up failed for {event uuuu.eeee|application aaaa.gggg}

Explanation: ESP encountered an FTP data set trigger definition that specified a TCP/IP host name (via the HOST operand of the DSTRIG event command or the DSNAME application statement) that could not be resolved into an IP address. This message is preceded by an error message 2215 that specifies the host name that could not be resolved to an IP address. aaaa specifies an ESP application name. eeee specifies an ESP event name. gggg specifies an ESP application generation number. uuuu specifies an ESP event userid.

System Action: The data set trigger is ignored. User Response: Correct the DSTRIG event command or the DSNAME application statement

so that it specifies a HOST operand that is either a host name that can resolve to an IP address or is an IP address itself.

112 ESP-5.4-MC-03

0765E EDTINFO RtnUnit, DevType=xxxx, RtnCode=yy, RsnCode=zz Explanation: In order to set the %ESPTRUNIT symbolic variable ESP attempted

unsuccessfully to determine the unit name of a data set that caused an event to be triggered. xxxx is the hexadecimal value of the data set's device type field. yy is the hexadecimal return code of the EDTINFO service request issued to obtain the unit name. zz is the hexadecimal reason code of the EDTINFO service request to issued to obtain the unit name.

System Action: The %ESPTRUNIT symbolic variable is set to value *UNKNOWN. User Response: Should not happen. If the problem persists call Cybermation support.

0766W Invalid FTP SMF# specified: xxx. SMF118 used. Explanation: The Communication Server that handles FTP on the host can be configured

to generate either SMF records 118 or SMF records 119. ESP Workload Manager needs to be told what records are being generated, so it can "listen" for them and initiate actions, such as file triggers. The default is to listen for SMF records 118. The value received from an initialization parameter, or a command has been neither 118, nor 119. The value received is listed in the message.

System Action: The default SMF 118 records will be "listened to" User Response: No action is required if the default value is acceptable. To avoid

seeing this message in the future, please correct the initialization parameter.

0767A PAUSE now in effect, Reply 'GO' to resume Explanation: As a result of the operator's request, ESP has temporarily halted

processing. This ESP has control of the shared data sets, including the queue file.

System Action: ESP waits for the operator to reply 'GO' to the WTOR. User Response: When ready to proceed, reply 'GO' to the WTOR.

0768I PAUSE completed, processing resuming Explanation: A reply of 'GO' has been received, and ESP has resumed normal

processing. System Action: None. User Response: None.

0769I PAUSE request must be issued from a console Explanation: A pause command was issued from a source other than an MVS MODIFY

command. System Action: The system ignores the command. User Response: None.

0770W NO BACKUP DEFINED FOR EVENTSET xxxx Explanation: A BKUPEVS command was entered for an event set for which no

backup data set has been defined System Action: The BKUPEVS command is ignored.

Messages and Codes

ESP-5.4-MC-03 113

User Response: Ensure that the EVENTSET has an associated backup data set before issuing the BKUPEVS command.

0771I STARTING BACKUP/SCAN OF EVENTSET xxxx Explanation: A scan of an Event data set has begun. This is as response to a

BKUPEVS command or through the normal schedule. System Action: If a backup data set is allocated, a sequential copy of the Event

data set will be made. If this is a scheduled scan, the schedule will be built.

User Response: None

0773I EVENTSET SCAN/BACKUP ENDED FOR xxxx, nn RECORDS BACKED UP

Explanation: A BACKUP or SCAN of an Event data set has completed. System Action: Processing continues. User Response: None.

0774S DATASET NOW SUSPENDED Explanation: An error has occurred which resulted in the suspension of the Event

data set. System Action: This message will have been preceded by another message describing the

error. The Event data set will not be accessed until the EVENTSET command is issued.

User Response: Once the problem with the Event data set is corrected, the data set can be reactivated through the EVENTSET OPEN command.

0775E ERROR OPENING BACKUP DATASET xxxx Explanation: An error occurred while opening a backup data set for output, during

an Event data set backup. System Action: The backup copy will not be taken. The schedule building function will

proceed. User Response: The message will describe the error condition. After the problem is


0776E ERROR WRITING TO BACKUP xxxx Explanation: An error occurred while writing to the backup data set during an Event

data set backup or scan. System Action: The backup operation will be suspended. If a SCAN was also being

performed, it will continue. User Response: The message will describe the error condition. After the problem is


0777E ERROR CLOSING BACKUP DATASET, xxxx Explanation: An error occurred while closing the backup data set for an Event file. System Action: Processing continues. User Response: The message will describe the error condition. After the problem is

diagnosed and corrected, the BKUPEVS command should be issued to take

114 ESP-5.4-MC-03

a backup.

0778E NO MORE SPACE IN CHECKPOINT FOR A SUBMISSION REQUEST ELEMENT

Explanation: During an Event data set scan to produce a schedule, insufficient checkpoint space was available to build a schedule element.

System Action: The schedule will not be completely built. User Response: Notify your system support personnel. After some space becomes

available in the checkpoint, issue the EVENTSET command with the BUILDSCHED keyword to rebuild the schedule.

0779E EVENTSET xxxx BACKUP/SCAN BYPASSED DUE TO SUSPENDED STATE

Explanation: A scheduled SCAN or BACKUP of the Event data set was attempted while the data set was in the suspended state.

System Action: The SCAN or BACKUP is deferred until the data set is reopened. User Response: When the problem with the data set is corrected, reopen the data set

with the EVENTSET command.

0780I STARTING BACKUP OF USERDEF Explanation: A backup of the user definition data set has begun. System Action: The userdef data set is backed up. User Response: None.

0782E BACKUP OF USERDEF ENDED WITH ERRORS Explanation: A previous error has caused termination of the user definition data

set backup. This message will have been preceded by another message describing the error.

System Action: The backup is terminated. Other processing continues. User Response: Notify your system support personnel. The backup can be done again

after the problem has been corrected.

0783I USERDEF BACKUP ENDED, nn RECORDS BACKED UP Explanation: A backup of the user definition data set has completed successfully. System Action: Processing continues. User Response: None.

0784E ERROR CLOSING BACKUP DATASET, xxxx Explanation: An error occurred whilst closing the backup data set. The backup may


correctable, the backup can be taken again.

0785E ERROR OPENING BACKUP DATASET xxxx Explanation: An error occurred while opening a backup data set for the user

definition data set. System Action: The backup is not performed.

Messages and Codes

ESP-5.4-MC-03 115

User Response: Notify your system support personnel. Once the problem is resolved, the backup should be retaken.

0786E ERROR WRITING TO BACKUP xxxx Explanation: An error occurred while writing to the backup data set for the user

definition data set. System Action: The backup is not completed. User Response: Notify your system support personnel. Once the problem is resolved,

the backup should be retaken.

0787E USERDEF BACKUP TIME WILL HAVE TO BE RESET Explanation: An error occurred when trying to compute the next time for a scheduled

backup. This message would have been preceded by a message describing the error.

System Action: The next backup will not be placed in the schedule. User Response: Use the BKUPUSER command to set the scheduled backup time.

0788E NO BACKUP DATASET SPECIFIED FOR USERDEF Explanation: ESP attempted to take a backup of the USERDEF data set. However, a

backup data set was not specified in the initialization parameters. System Action: The backup is not performed. User Response: The backup data set should be placed in the ESPPARM data set and ESP

restarted.

0790I STARTING BACKUP OF INDEX Explanation: A backup of the user definition data set has begun. System Action: The userdef data set is backed up. User Response: None.

0792E BACKUP OF INDEX DATASET ENDED WITH ERRORS Explanation: A previous error has caused termination of the Index data set backup.

This message is preceded by another message describing the error. System Action: The backup is terminated. Other processing continues. User Response: Notify your system support personnel. The backup can be performed

again after the problem has been corrected.

0793I INDEX DATASET BACKUP ENDED, nn RECORDS BACKED UP Explanation: A backup of the Index data set has completed successfully. System Action: Processing continues. User Response: None.

0794E ERROR CLOSING INDEX BACKUP DATASET, xxxx Explanation: An error occurred while closing the backup data set. The backup may


correctable, the backup can be performed again.

116 ESP-5.4-MC-03

0795E ERROR OPENING INDEX BACKUP DATASET xxxx Explanation: An error occurred while opening a backup data set for the Index data

set. System Action: The backup is not performed. User Response: Notify your system support personnel. Once the problem is resolved,

the backup should be performed again.

0796E ERROR WRITING TO INDEX BACKUP xxxx Explanation: An error occurred while writing to the backup data set for the Index

data set. System Action: The backup is not completed. User Response: Notify your system support personnel. Once the problem is resolved,

the backup should be performed again.

0797E INDEX DATASET BACKUP TIME WILL HAVE TO BE RESET Explanation: An error occurred when trying to compute the next time for a scheduled

backup. This message is preceded by a message describing the error. System Action: The next backup will not be placed in the schedule. User Response: Use the BKUPUSER command to set the scheduled backup time.

0798E NO BACKUP DATASET SPECIFIED FOR INDEX DATASET Explanation: ESP attempted to take a backup of the Index data set. A backup data

set was not specified in the initialization parameters. System Action: The backup is not performed. User Response: The backup data set should be placed in the ESPPARM data set and ESP

restarted.

0800W PARAMETER ERROR ON EXEC CARD Explanation: An invalid initialization option was specified on the EXEC card

parameter of the ESP procedure. System Action: ESP continues with

message 803. User Response: Reply to the prompt that follows.

0801W PARAMETER ERROR ON START COMMAND Explanation: An invalid initialization option was specified on the START command

for ESP. System Action: Processing continues with message 803. User Response: Reply to the prompt that follows.

0802A REENTER ENTIRE STATEMENT, 'CANCEL' OR 'END' Explanation: This message follows an error in an initialization option on the EXEC

card, START command or in a parameter statement. It is preceded by a message indicating the cause of the error.

System Action: ESP waits for a response. If CANCEL is specified, ESP terminates. If END is specified, ESP ignores the parameter statement, EXEC or START option in error.

Messages and Codes

ESP-5.4-MC-03 117

User Response: Reenter the correct parameters. If you are not sure what they are supposed to be, reply CANCEL, and ESP will terminate. ESP can then be restarted when the correct parameters are found.

0803W xxxx Explanation: ESP is displaying the initialization option on the EXEC card or START

command, or the parameter statement which had an error. System Action: This message is followed by message 802. User Response: Reply to the message that follows.

0804W PARAMETER ERROR ON FOLLOWING STATEMENT FROM xxxx FILE

Explanation: A parameter error was encountered on one of the parameter input files. "xxxx" is the DD name of the file containing the statement in error.

System Action: This message is followed by message 803. User Response: Reply to the message 802 prompt that follows.

0805W FOLLOWING STATEMENT FROM xxxx HAS AN INVALID SYNTAX Explanation: A syntax error was encountered on a parameter statement from a

parameter file. "xxxx" is the DD name of the file containing the statement in error.


0806W FOLLOWING STATEMENT FROM xxxx HAS AN UNDEFINED PARAMETER

Explanation: An undefined parameter was encountered on a statement from a parameter library. "xxxx" is the DD name of the file containing the statement in error.


0807E xxxx Explanation: An I/O error was encountered reading the ESPPARM file. This could

include a file not allocated condition or an actual I/O error. The text of the message fully describes the error.

System Action: Processing is terminated. User Response: Correct the problem and restart ESP.

0808W CHECKPOINT DATA SET xxxx IS CORRECTLY FORMATTED Explanation: A cold start was requested using a checkpoint data set that was

correctly formatted. Since it is correctly formatted, a warm start may be possible. ESP is confirming that a cold start is really required, and not inadvertently specified.

System Action: ESP follows by issuing message 809. User Response: Respond to message 809.

118 ESP-5.4-MC-03

0809A CONFIRM REQUEST FOR COLD START, ENTER 'Y' OR 'N' Explanation: ESP is requesting confirmation that a cold start is really required. System Action: ESP waits for the reply. If a Y is entered, ESP proceeds with a cold

start. If the reply is N, ESP proceeds with a warm start. User Response: If you wish to proceed with the cold start, enter Y. Otherwise enter

N and ESP will attempt a warm start.

0810I WARM START WILL BE ATTEMPTED Explanation: ESP is attempting a warm start after the operator entered a reply of N

to the message 809A. System Action: A warm start is attempted. User Response: None.

0812W INVALID CHECKPOINT FORMAT ON xxxx Explanation: A warm start was requested. However, the checkpoint data set does not

have a valid format. System Action: This messages followed by message 813. User Response: If you wish to proceed with the cold start, enter Y. Otherwise enter

N and ESP will terminate.

0813A ENTER 'Y' TO PROCEED WITH COLD START OR REPLY 'N' Explanation: This message requests confirmation that you wish to proceed with a

cold start. System Action: ESP waits for your response. If you answer Y, the cold start is

performed. Otherwise, a warm start is attempted. User Response: Enter Y if you wish to proceed with a cold start.

0814E xxxx Explanation: An error occurred processing a checkpoint data set. The text of the

message fully describes the problem. System Action: This message is followed by message 0817S. User Response: Respond to message 0817S.

0815W INVALID RESPONSE Explanation: An invalid response was given to message 0898A. System Action: The prompt is reissued. User Response: Respond to the prompt.

0816W CHECKPOINT xxxx LAST USED BY SYSTEM yyyy AT zzzz ON aaaabbbbcccc

Explanation: A cold-start or warm-start was being performed and ESP detected that the checkpoint data set was correctly formatted but the system ID was that of another system. The date of last use is displayed to help you assess whether the checkpoint is still in use.

System Action: This message is followed by message 813A. User Response: Respond to message 813A. You will not be able to perform a warm start

unless the system ID matches that in the checkpoint.

Messages and Codes

ESP-5.4-MC-03 119

0817S CHECKPOINT UNUSABLE Explanation: This message follows another message describing an error on the

checkpoint data set. System Action: Processing terminates. User Response: The previous message described an error condition. After the problem

is corrected, ESP can be restarted.

0818S NO CHECKPOINT DATA SET SPECIFIED IN ESPPARM Explanation: No checkpoint data set was defined in the ESPPARM file. System Action: Processing terminates. User Response: Enter the CKPT parameter in the ESPPARM file and restart ESP.

0820S CHECKPOINT DATA SET NOT DEFINED Explanation: A checkpoint data set was not specified on an ESP startup. System Action: Processing terminates. User Response: Define a checkpoint data set by use of the CKPT parameter in the

ESPPARM file.

0821S USER DEFINITION DATA SET NOT DEFINED Explanation: The user definition data set (USERDEF) was not defined in the ESPPARM

data set. The data set is required for ESP to operate. System Action: Processing terminates. User Response: Enter a USERDEF statement in the ESPPARM file to define the user

definition data set. Then restart ESP.

0823W CHECKPOINT DATA SET IS DOWNLEVEL, COLD START REQUIRED

Explanation: A WARM start was attempted when bringing up a new release of ESP. The new release uses a checkpoint of different format, and therefore a cold start is required.

System Action: This message is followed by message 813. User Response: Respond to message 813.

0824S USER DEFINITION DATA SET xxxx UNUSABLE Explanation: An error, described by a preceding message, has caused the user

definition data set to be unusable. System Action: Processing terminates. User Response: The preceding message documents the error. After the error is

corrected, ESP can be restarted.

0826E INCORRECT KEY LENGTH SPECIFIED FOR USER DEFINITION DATASET

Explanation: The ESPPARM data set specified a User Definition data set which had an incorrect keylength.

System Action: Processing terminates. User Response: Ensure the correct data set name was specified. If the name was

correct, redefine the data set with the correct characteristics, or

120 ESP-5.4-MC-03

use the ALTER command of the IDCAMS utility to modify the key length attribute.

0827I USER DEFINITION DATA SET EMPTY, WILL FORMAT Explanation: An empty User Definition data set was detected. This is expected the

first the data set is used. System Action: The data set is formatted and continues processing. User Response: None, unless the User Definition data set is not supposed to be empty.

0828E INVALID JOURNAL SMF RECORD NUMBER SPECIFIED Explanation: An SMF record number was specified that was not within the range

128-255. System Action: The operator is prompted to reenter the correct number. User Response: Respond to the message that follows. If you are unsure of the correct

number, notify your software support staff.

0829E INVALID MINDORM VALUE nn Explanation: The MINDORM value cannot be less than 10 nor greater than 100,000. System Action: User Response: Correct the MINDORM value.

0831E INVALID SVC NUMBER SPECIFIED Explanation: An SVC number was specified in the ESPPARM data set. However, the

number was not in the range 200-255. System Action: The operator is prompted to supply the correct parameter. User Response: Respond to the message that follows.

0832E ERROR OCCURRED DURING COMMAND PARAMETER SCAN Explanation: An error occurred during the parameter scan of a statement from the

ESPPARM file. This is probably due to an internal logic error. System Action: Processing terminates. User Response: Notify your software support personnel.

0833E INVALID MAXDORM VALUE nn Explanation: The MAXDORM value cannot be less than 100 nor greater than 100,000. System Action: User Response: Correct the MAXDORM value.

0834E INVALID MINHOLD VALUE nn Explanation: The MINHOLD value cannot be less than 10 nor greater than 100,000. System Action: User Response: Correct the MINHOLD value.

0835I USER DEFINITION DATA SET HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED

Explanation: The User Definition data set contained no control record. A control record is always the first record in the data set.

System Action: A control record will be built and written out.

Messages and Codes

ESP-5.4-MC-03 121


0836E APPLJOB LIST specified with incompatible operand(s) Explanation: An APPLJOB or AJ command that specified or defaulted to the LIST

function specified at least operand that is mutually exclusive with the LIST function.

System Action: The APPLJOB or AJ command is ignored. User Response: If required, re-issue the APPLJOB or AJ command with compatible

operands.

0837C APPLJOB LIST Explanation: An APPLJOB or AJ LIST command. System Action: The status of the specified job in the specified ESP/WM application

is displayed. User Response: None.

0838? ENTER INITIALIZATION PARAMETER OR 'END' Explanation: In response to the PROMPT keyword on the start command, ESP is

prompting the operator to enter an initialization parameter from the console.

System Action: ESP waits for a response, then processes the parameter. User Response: Enter an initialization parameter. Anything valid in the ESPPARM

data set can be specified here. When all parameters are defined, type END terminate the prompt and to continue with normal processing.

0839E INVALID MAXLRECL VALUE nn, VALID RANGE 4000-32760 Explanation: A MAXLRECL parameter on the ESPPARM data set specified a value outside

of the range 4000-32760. System Action: The operator is prompted to reenter the correct value. User Response: Respond to the message that follows. Specify a number between 4000

and 32760. If in doubt, specify the maximum. This value should be at least as large as the largest record of any ESP database.

0840S UNABLE TO INITIALIZE SUBSYSTEM Explanation: An error occurred while trying to build the subsystem interface. This

is probably an internal logic error. System Action: Processing terminates. User Response: Notify your software support personnel.

0841S ERROR WRITING CHECKPOINT Explanation: ESP encountered an error while writing to the checkpoint. System Action: Processing terminates. User Response: Investigate and correct the problem. Then restart ESP.

0842S CANNOT PURGE START WITH AUXILIARY ACTIVE Explanation: An attempt has been made to PURGE start ESP Workload Manager.

However, the ESP Workload Manager auxiliary address space is currently operational.

122 ESP-5.4-MC-03

System Action: ESP Workload Manager terminates. User Response: You must either start ESP Workload Manager without the PURGE

option, or else terminate the auxiliary address space prior to performing the PURGE start.

0843S INSUFFICIENT CSA TO ENABLE DATA SET TRIGGERING Explanation: ESP could not obtain enough storage in CSA to fully initialize data

set triggering. The storage may reside above the 16Mb line. System Action: The data set triggering facility is not fully initialized. Processing

continues without it. User Response: ESP can be stopped and restarted when the CSA shortage is relieved.

0845W Insufficient CSA storage for tracking cell Explanation: During cross memory cell initialization, CSA storage could not be

obtained for the cross memory elements (XMEs). System Action: Processing continues. The ability to track information may be limited

or disabled. User Response: Provide additional CSA by terminating unnecessary tasks using CSA or

increase CSA size.

0846W INSUFFICIENT CSA FOR DATASET TRIGGER DESCRIPTOR Explanation: ESP was unable to obtain common storage for a data set trigger

descriptor. A data set trigger descriptor is required to intercept the creation of data sets. The storage may reside above the 16Mb line.

System Action: Some or all data set triggers will not be intercepted. User Response: ESP can be stopped and restarted once the CSA shortage is relieved.

0847W INSUFFICIENT CSA STORAGE FOR TRIGGER EXCLUSION ENTRY xxxx

Explanation: ESP was unable to obtain common storage for a data set trigger exclusion entry, requested by the DSTREXCL initialization parameter. The storage may reside above the 16Mb line.

System Action: Some data set triggers, originating from the specified program, will not be suppressed.

User Response: ESP can be stopped and restarted once the CSA shortage is relieved.

0848S ERROR ATTACHING COMMAND TASK, RC=nn Explanation: An error occurred while attempting to attach the command processor

task. System Action: Processing terminates. User Response: Notify your software support personnel. This is normally caused by a

lack of virtual storage. Increase the region size and restart ESP.

0849S ERROR OCCURRED READING QUEUE DATA SET Explanation: An error occurred while attempting to read the QUEUE data set. This

message will have been preceded by a message describing the error. System Action: Processing terminates. User Response: Notify your software support personnel. The preceding message will

have described the error. Restart ESP when the problem is corrected.

Messages and Codes

ESP-5.4-MC-03 123

0850S ESP IS ALREADY ACTIVE FOR SYSTEM ID xxxx Explanation: ESP was started while another copy of the program was executing with

the same system ID. System Action: Processing terminates. User Response: This is a probably due to an operator error, when more than one ESP

task is started.

0851E UNABLE TO LOAD ACF2 MUSASS INITIALIZATION EXIT Explanation: An error occurred while trying to load the module specified by the

ACF2EXIT parameter. System Action: The operator is prompted to reenter the parameter statement. User Response: Respond to the prompt message that follows. Notify your software

support personnel.

0852E JOB INDEX AND TRACKFILE BOTH NEEDED FOR TRACKING OPTION

Explanation: Either the job index or job tracking files were specified in the initialization parameters. Both are required for the tracking option to work.

System Action: Processing terminates. User Response: Update the initialization parameter data set to define both data sets.

Restart ESP.

0853E QUEUE DATA SET NEEDED FOR TRACKING OPTION Explanation: The job tracking function was requested by the inclusion of the track

file and job index data sets in the initialization parameters. The queue data set was not defined.

System Action: Processing terminates. User Response: The queue data set should be defined by adding the QUEUE parameter to

the initialization parameter data set.

0854E xxxx Explanation: An error occurred while performing I/O to or opening the track file.

The message text describes the error. System Action: This message is followed by message 0855S. User Response: Take action based on message 0855S.

0855S TRACK FILE DATASET xxxx UNUSABLE Explanation: An error, described by a preceding message, has prevented ESP from

using the job tracking file. System Action: Processing terminates. User Response: Notify your software support personnel. After the error has been


0856E TRACK FILE DATASET IS TOO SMALL Explanation: The job tracking file was found to be too small. At least 450 slots

are needed for normal processing, a slot being a 1024 byte block. On a

124 ESP-5.4-MC-03

3350 device, each cylinder can contain 450 slots. System Action: Processing terminates. User Response: Notify your software support personnel. The data set should be

reallocated with room for at least 450 slots. ESP can then be restarted.

0857S STARTUP TERMINATED BY INSTALLATION ACF2 EXIT Explanation: The installation ACF2 interface initialization exit encountered an

error and requested shutdown. System Action: Processing terminates. User Response: Notify your software support personnel.

0860S INDEX DATA SET xxxx UNUSABLE Explanation: An error, described by a preceding message, has prevented ESP from

accessing the index data set. System Action: Processing terminates. User Response: Notify your software support personnel. After the error has been


0861E INCORRECT KEY LENGTH SPECIFIED FOR INDEX DATA SET Explanation: The ESPPARM data set specified an index data set data set which had an

incorrect keylength. System Action: Processing terminates. User Response: Ensure the correct data set name was specified. If the name was

correct, redefine the data set with the correct characteristics, or use the ALTER command of the IDCAMS utility to modify the key length attribute.

0862I INDEX DATA SET HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED

Explanation: The ESP index data set contained no control record. A control record is always the first record in the data set.

System Action: A control record will be built and written out. User Response: None.

0863I INDEX DATA SET EMPTY, WILL FORMAT Explanation: An empty ESP index data set was detected. This is expected the first

time the data set is used. System Action: ESP formats the data set and continues processing. User Response: None, unless the index data set is not supposed to empty.

0864S INDEX DATA SET DOWNLEVEL, USE CONVERT UTILITY Explanation: The index data set was found to be created by an incompatible release

of ESP. System Action: The data set cannot be used, and so processing terminates. User Response: Use the convert subcommand of the UTIL processor of the ESP TSO

command, then restart the subsystem.

Messages and Codes

ESP-5.4-MC-03 125

0866E INVALID DSTRIG CELL COUNT nn{ 10 USED} Explanation: A DSTRIG parameter with a cell count outside of the range 1-1000 was

specified. System Action: The operator is prompted to reenter the parameter. User Response: Respond to the message that follows.

0867S INDEX DATA SET NOT DEFINED Explanation: No INDEX statement was found in the ESPPARM data set. ESP does not

know the index data set name. System Action: Processing terminates. User Response: Notify your software support personnel. The INDEX statement should be

inserted into the ESPPARM file to describe the name and other characteristics if the ESP index data set.

0868E INVALID DSTRIG EXPANSION LIMIT nn{ 50 USED} Explanation: A DSTRIG parameter with a cell expansion limit outside of the range

0-1000 was specified. System Action: The default of 50 is used. User Response: Notify your software support personnel, who will then correct the

initialization parameters.

0869E TCELL type specification missing Explanation: A TCELL command did not specify the JOBSTART, STEPEND or JOBEND

keyword operand. System Action: The operator is prompted to re-enter the command. User Response: Respond to the message that follows and correct the erroneous TCELL

command in the ESPPARM initialization file.

0870E TCELL initial count nnn invalid Explanation: A TCELL command with an initial count nnn outside the range 0-100 was

specified. System Action: The operator is prompted to re-enter the command. User Response: Respond to the message that follows and correct the erroneous TCELL


0871E TCELL expansion limit nnn invalid Explanation: A TCELL command with an expansion count nnn outside the range 0-5000

was specified. System Action: The operator is prompted to re-enter the command. User Response: Respond to the message that follows and correct the erroneous TCELL


0872E INVALID DAY OF WEEK NAME xxxx Explanation: An invalid day of week name was specified for the WORKDAYS keyword

during a DEFCAL or ALTCAL command. The valid days are SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY and SATURDAY. The names

126 ESP-5.4-MC-03

may be abbreviated down to the first 3 characters. System Action: The command is not processed. User Response: Enter a valid day, or list of days.

0873E INVALID DAY OF WEEK NAME xxxx Explanation: An invalid day of week name was specified for the WEEKSTART keyword

during a DEFCAL or ALTCAL command. The valid days are SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY and SATURDAY. The names may be abbreviated down to the first 3 characters.

System Action: The command is not processed. User Response: Enter a valid day, or list of days.

0874S ERROR PROCESSING CHECKPOINT DATA SET Explanation: The checkpoint data set had an invalid format or a permanent I/O error

occurred reading the data set. System Action: The scheduled activity report generation process is terminated. User Response: Ensure a valid checkpoint data set name is specified in the ESP parm

file.

0875E INVALID APPLBUF VALUE nnnn, VALID RANGE 16376-4177912 Explanation: An invalid value was given for the APPLBUF parameter. This parameter

defines the size of the largest logical record to be stored in any application file. A valid value is anything in the range 16376 to 4177912. The value should be an integral multiple of 4096 less 8.

System Action: The operator is prompted to supply a correct value. The default is 131064 (128K-8).

User Response: Supply a correct value to the prompt message that follows.

0876E Error reading/writing TRAKFILE while tracking RESET jjj command Explanation: A job tracking record was being updated by a RESET command processing

when an I/O error occurred on the track file. The error will have been described by a preceding message.

System Action: The RESET information for the job will not be updated. However, if no other I/O error occurs, the job summary data should still be correct.


0880S JOB INDEX DATASET xxxx UNUSABLE Explanation: An error, described by a preceding message, has prevented ESP from

accessing the job index data set. System Action: Processing terminates. User Response: Notify your software support personnel. After the error has been


0881E INCORRECT KEY LENGTH SPECIFIED FOR JOB INDEX DATASET Explanation: The ESPPARM data set specified a job index data set which had an


Messages and Codes

ESP-5.4-MC-03 127


0882I JOB INDEX DATASET HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED

Explanation: The ESP job index data set contained no control record. A control record is always the first record in the data set.


0883I JOB INDEX DATASET EMPTY, WILL FORMAT Explanation: An empty ESP job index data set was detected. This is expected the

first time the data set is used. System Action: ESP formats the data set and continues processing. User Response: None, unless the job index data set is not supposed to empty.

0885W TRACK FILE xxxx UNFORMATTED Explanation: The Job Tracking file was found to be unformatted. This is expected

the first time the data set is used. System Action: ESP follows with message 886. User Response: Respond to message 886.

0886A REPLY 'Y' TO FORMAT THE TRACK FILE, OR REPLY 'N' Explanation: The Job Tracking file was found to be unformatted. Before proceeding

to format it, ESP requests permission from the operator. System Action: ESP waits for the reply. User Response: If you wish the tracking file to be formatted, reply Y, otherwise

reply N and ESP will terminate. The tracking file should only need to be formatted once, or after it has been newly created. If this is not the first time the data set is used, call your software support personnel.

0887E CORRECT THE ABOVE PROBLEM AND RESTART ESP Explanation: This message is issued after an error has occurred that prevents to

further execution of ESP. This message would have been preceded by another describing the error.

System Action: ESP terminates. User Response: After the problem has been corrected, you may restart ESP.

0888I STARTING TO FORMAT THE TRACK FILE Explanation: The formatting run of the job tracking file has begun. You may expect

this to take an appreciable amount of time. System Action: The tracking file is formatted. User Response: None. Be patient.

0889I TRACK FILE FORMAT COMPLETE Explanation: The formatting run of the job tracking file has been completed.

128 ESP-5.4-MC-03


0890S ESP INITIALIZATION DENIED BY INSTALLATION STARTUP EXIT Explanation: The installation STARTUP exit gave a non-zero return code, requesting

ESP to terminate. System Action: ESP terminates. User Response: Notify your software support personnel.

0891W ESP LAST ACTIVE AT xxxx ON yyyy Explanation: ESP is being restarted, and the current date and time differ by more

than a user defined threshold from the time that ESP was last active. System Action: This message is followed by message 892. User Response: Check the times specified on this message and the following message.

0892W IT IS NOW xxxx ON yyyy Explanation: ESP is displaying the current system time and date. This message

follows message 891. System Action: This message is followed by message 893. User Response: Check to ensure the time as displayed by ESP is the correct time and

date. Respond to the message that follows.

0893A CONFIRM DATE AND REPLY 'Y' TO CONTINUE, 'N' TO TERMINATE OR 'Q' TO QUIESCE

Explanation: This message follows messages 891 and 892. See above. System Action: ESP awaits a response. If the response is 'Y', ESP continues. A

response of 'N' causes ESP to terminate. User Response: If the current date and time is correct, reply 'Y'. If the date or

time is incorrect, reply 'N' to terminate ESP then schedule an IPL to correct the time. ESP may then be restarted.

0894S ESP TERMINATING DUE TO INCORRECT CLOCK SETTING Explanation: This message follows a response of 'N' to message 893. System Action: ESP terminates. User Response: ESP should be restarted after the clocks are reset.

0895E UNABLE TO LOAD USER-VERIFY EXIT ROUTINE Explanation: ESP attempted to but was unable to load the user verification exit

routine. System Action: This message is followed by a prompt message. User Response: Respond to the message that follows.

0896E MODULE xxxx NOT IN COMMON STORAGE Explanation: The User verification exit routine was loaded but found not to be in

common storage. System Action: This message is followed by a prompt message. User Response: Notify your system programmer who should ensure that the exit routine

is placed in the LPA or MLPA. ESP can be initialized without the exit

Messages and Codes

ESP-5.4-MC-03 129

by responding 'END' to the prompt message that follows this one.

0897W LOCAL TIME xxxx ON yyyy zzzzaaaa bbbb Explanation: The GMTCHECK parameter was specified in the initialization parameter

deck. A discrepancy was found between the Local and GMT time. Message 1945W follows for GMT.

System Action: This message is followed by message 1945W and 0898A. User Response: Respond to message 0898A.

0898A REPLY 'Y' TO PROCEED OR REPLY 'N' TO TERMINATE Explanation: The GMTCHECK parameter was specified in the initialization parameter

deck. A discrepancy was found between the Local and GMT time. This message is preceded by two message 897, displaying the Local and GMT time settings. The difference in the clock settings may have been due to the resetting of the local clock without also resetting the GMT clock.

System Action: ESP waits for a reply. User Response: If you meant to offset the local time from GMT time, reply 'Y' to

allow ESP to continue. To reset the TOD clock, reply 'N' to terminate ESP. Then schedule an IPL as soon as possible, as the TOD clock can only be reset at IPL time. A power on reset may be necessary to force a TOD clock prompt at the next IPL.

0899W WARNING, ERRORS MAY OCCUR DUE TO TOD CLOCK INCONSISTENCY

Explanation: The GMTCHECK parameter was specified in the initialization parameter deck. A discrepancy was found between the Local and GMT time. In response to message 989, the operator had replied 'Y'.

System Action: Processing continues. User Response: Ensure that you meant to have Local time differ from GMT time. The

presence of the GMTCHECK parameter in the initialization deck presumes that the installation normally expects local and GMT times to be the same. If in doubt, notify your systems programmer.

0900I xxxx Explanation: This message is an informational message relating to a command or

parameter statement that is being scanned. It can also provide warning or error information about the item being scanned.

System Action: Processing continues. User Response: If this is informational, no response is required. If this describes a

warning or error condition, then the user should correct the command or statement and re-process it.

0901A xxxx Explanation: This is a prompt message which requests a user to enter or reenter a

parameter. System Action: The system waits for the response. User Response: Enter the missing parameter or reenter an incorrectly specified

parameter.

130 ESP-5.4-MC-03

0902E LOGIC ERROR IN MESSAGE I/O REQUEST Explanation: The message module was called with in invalid message type or

destination routing. This is probably a logic error in the program. System Action: The message is not written. User Response: Notify your software support personnel.

0904E PRINT FILE xxxx NOT FOUND Explanation: An ENDPRINT command was issued to a print file that was not currently

defined. The file had either never been defined, or was already closed.

System Action: The command is not processed. User Response: Ensure the correct file name is specified.

0905I REQUIRED ENTRY NOT FOUND Explanation: The specified command name was not found. System Action: The command's CLE was not dumped. User Response: Correct the command name and try again.

0906E xxxx Explanation: This message is an error message relating to a command or parameter

statement that is being scanned. System Action: Processing continues. User Response: Check parameters for validity, correct the error and retry.

0907I OK Explanation: The requested HISTFILE operation has completed successfully. System Action: User Response:

0908E ATTACH ERROR nn Explanation: An error occurred while attaching the command. System Action: The command was not executed. User Response: Try again later.

0909W INVALID COMMAND NAME SYNTAX Explanation: The syntax of this command is incorrect. System Action: The command was not executed. User Response: Correct the command and try again.

0910S XTLOCK request logic error Explanation: An invalid thread locking request was made within a Cybermation

product. System Action: Task is abended with code U0901. User Response: Internal logic error. Call Cybermation Technical Support.

0911W WARNING, LICENCE PERIOD EXPIRES IN nn xxxx Explanation: The license period for ESP is coming close to expiry.

Messages and Codes

ESP-5.4-MC-03 131

System Action: Processing continues. ESP will not execute after days unless the appropriate authorization codes are applied.

User Response: Contact Cybermation to obtain authorization codes for your site.

0912S xxxx Explanation: An error occurred while writing an output message to a data set. The

text of the message fully describes the error. System Action: Depends on which data set the error occurred on. User Response: This depends on the error.

0913S UNABLE TO OPEN FILE xxxx, PROCESSING TERMINATED Explanation: An I/O error occurred while trying to open the primary output file.

This is probably due to a missing DD statement. System Action: Processing terminates. User Response: Correct the problem and retry.

0914E xxxx Explanation: An error occurred trying to close an input or output data set. The

text of the message describes the error. System Action: This depends on how critical the data set is. User Response: Retry after the problem is corrected.

0915E xxxx Explanation: An error occurred attempting to retrieve a command or parameter

statement from a disk data set. The text of the message describes the error.

System Action: This depends on how critical the data set is to continued operation. User Response: Retry after the problem is corrected.

0916E UNEXPECTED END OF DATA ON FILE xxxx Explanation: The last statement in an input file indicated that a continuation line

followed. System Action: This depends on how critical the data set is to continued operation. User Response: Retry after the problem is corrected.

0917E xxxx DD STATEMENT MISSING Explanation: A Print command specified output to a preallocated file. However, the

file was not preallocated. System Action: The print file request is ignored. User Response: Preallocate the file, or correct the file name.

0918E PRINT ID MISSING OR INVALID ON DEFPRINT COMMAND Explanation: A DEFPRINT command was issued, but the print ID was omitted or

invalid. A print ID should be from 1 to 8 alphanumeric characters. System Action: The DEFPRINT command is not processed. User Response: Ensure a valid print ID is specified.

132 ESP-5.4-MC-03

0919E PRINT FILE xxxx NOT FOUND Explanation: A SETPRINT command was issued to a print file that was not currently

defined. The file had either never been defined, or was already closed.

System Action: The command is not processed. User Response: Ensure the correct file name is specified.

0920W COMMAND INVALID IN BATCH Explanation: An implicit EXEC, a HELP or a TSO command was specified outside of the

TSO environment. System Action: The command is ignored. User Response: Only specify the command in a TSO environment.

0921E ENDTEMPL statement missing Explanation: There is a syntax error in a TEMPLATE definition. An ENDTEMPL

statement necessary to terminate the definition was not found. System Action: The appl is not done. User Response: Add the ENDTEMPL statement to the end of the TEMPLATE definition.

0922E TEMPLATE nesting limit of n exceeded. TEMPLATE ignored Explanation: The depth of a TEMPLATE invocation exceeds n. There is probably

a line in a template which invokes itself. System Action: Execution of current ESP procedure is terminated. User Response: Check for recursive invocation and correct procedure. If there is

no recursive invocation redesign templates to reduce the depth to acceptable level.

0923C SVC Display Explanation: A request was made to display information from SVC table. This is the

first line of a multiple line display. System Action: Processing continues. User Response: None.

0924I DASD DISPLAY Explanation: A request was made to display information about DASD devices. This

is the first line of a multiple line display detailing the storage device information.


0925E GQSCAN RC=8. Request terminated Explanation: Data returned by GQSCAN macro could not be placed in the buffer

obtained by calling GETMAIN macro (program asks for 4M, but continues processing with at least 128K)

System Action: Command is not executed. User Response: Increase Region Size or be more specific in the request or use keyword

SEGMENTED, which allows the program to accept the data portion after

Messages and Codes

ESP-5.4-MC-03 133

portion. Warning. You may be flooded with the output when the request is too generic. Note. When SORT option is used together with SEGMENTED option the sorting is performed within each portion

0926S GQSCAN RC=nn. Request can not be processed Explanation: MVS (nn=12) or CPE (nn=16) error was encountered while processing the

request. System/CPE tables/queues may be corrupted. System Action: Command is not executed. User Response: You may retry the request one or more times. If it won't help, then

recycle will.

0927E GQSCAN RC=20. Request could not be processed. Try later Explanation: The limit for the number of concurrent resource requests has been

reached (this limit is system defined). System Action: Command is not executed. User Response: Retry the request one or more times. If the problem persists your

system programmer might be able to tune the system so that the limit is no longer exceeded.

0928C DSVC HELP Explanation: Response to DSVC HELP command. System Action: DSVC command options are displayed. User Response: None.

0929W xxxxxx Explanation: The message xxxxx explains the actions taken or the result achieved

while processing the request. System Action: Execution continues/completes. User Response: Analyze the results of the request and if not satisfied reissue

another request with different parms.

930E Space obtained for WASIZE not enough to hold all data Explanation: The work area SIZE defined by user (or defaulted to) is not big

enough to accommodate all the data passed from system macro VSMLIST. The default value for SIZE is 65535.

System Action: Command is not executed. User Response: Increase the SIZE specification, and reexecute the request. To

double the size of the work area, for instance, specify: CALLRTN CYBUT005 SIZE(131072)

0931S Error in Virtual Storage Management data areas Explanation: MVS system error. An error encountered while scanning VSM data areas. System Action: Command is not executed.

134 ESP-5.4-MC-03

User Response: Notify system support personnel that there might be an error in VSM's control structures. For more info see Auth Assembler Services Reference for macro VSMLIST. This messages is issued for Return Code = 8.

0932S Invalid Return Code from system macro VSMLIST. RC=n Explanation: System macro VSMLIST returned invalid RC. System Action: Command is not executed. User Response: Notify system support personnel. Anything is possible including

corruption of system linkage table.

0933C Susystem Interface Display Explanation: A request was made to display subsystem interface information. This is

is the first line of a multiple line display. System Action: Processing continues. User Response: None.

0934C DSUBSYS HELP Explanation: Response to DSUBSYS HELP command. System Action: DSUBSYS command options are displayed. User Response: None.

0939S Data set xxxxxx has been overwritten Explanation: The checkpoint I/O routine detected an error in the master record of

the named shared checkpoint data set. On a re-read of the master record, the format timestamp was unequal to the value read previously. This can occur if a shared file is formatted while it is in use by another subsystem.

System Action: Processing terminates. ABEND1106 is issued to abnormally terminate processing.

User Response: Shut down any subsystems using this data set which may still be up. Then, restart one of them, specifying QFORM to ensure the data set contains no damage. Then, restart the other subsystems normally. QFORM must be requested once only, and only on the first subsystem to be started.

0940S ABOVE ERROR OCCURRED READING PRIMARY CHECKPOINT Explanation: An error occurred reading the primary checkpoint data set. A preceding

message would describe the exact error. System Action: Processing terminates. User Response: Take action according to the preceding message.

0941S ABOVE ERROR OCCURRED WRITING PRIMARY CHECKPOINT Explanation: An error occurred writing the primary checkpoint data set. A preceding

message would describe the exact error.

System Action: Processing terminates. User Response: Take action according to the preceding message.

Messages and Codes

ESP-5.4-MC-03 135

0942I TERMINATING Explanation: There has been a severe error while writing the primary checkpoint

file. System Action: ESP is shutting down. User Response: Check the preceding messages for more information on this error.

0943E WILL ATTEMPT REFORMAT Explanation: A severe error has occurred on the alternate checkpoint file. System Action: ESP is attempting to reformat the alternate checkpoint file. User Response:

0944E REFORMAT FAILED, TERMINATING Explanation: There has been an uncorrectable error on the alternate checkpoint file. System Action: ESP is shutting down. User Response: Check the preceding messages for more information on this error.

0945I TERMINATING Explanation: There has been a severe error while reading from the primary

checkpoint file. System Action: ESP is shutting down. User Response: Check the preceding messages for more information on this error.

0946S ERROR OCCURRED PROCESSING ALTERNATE CHECKPOINT Explanation: A severe error has occurred on the alternate checkpoint file. System Action: ESP is attempting to reformat the alternate checkpoint file. User Response:

0947S Serialization-control error on XXXXXX. Explanation: The Queue File XXXXXX is found to be overridden by other system.

This was caused by the failure of serialization setting. System Action: The ESP system is shut down. User Response: Solve the serialization problem, and re-start the ESP system.

Three most likely reasons for the problem are: 1.The initialization parameter RSVLOGIC was not set to be the same for all the systems accessing the same Queue File. 2.The serialization system (i.e. GRS or MIM) doesn't work for all the systems accessing the same Queue File. 3.The queue name(QNAME) used by RSVLOGIC is incorrectly defined to the serialization system, i.e., excluded from GRS, but not included in MIM.

0948I REFORMAT OF DUPLEX SUCCESSFUL Explanation: The alternate checkpoint file has been successfully reformatted. System Action: User Response:

136 ESP-5.4-MC-03

0949W WAITING FOR {I/O COMPLETION|RESERVE} ON DATA SET xxxx Explanation: ESP is waiting for access to a data set. System Action: ESP will issue this message periodically until access has been granted. User Response:

0950E INVALID TIMEZONE ADJUSTMENT xxxx Explanation: The TIMEZONE parameter has an invalid time adjustment specification.

The format should be HH or HH.MM optionally followed by an 'E' or 'W'. System Action: The operator is prompted to supply the correct value. User Response: Reenter the statement at the prompt.

0951E INVALID TIMEZONE CODE, nn SHOULD BE 0-63 Explanation: A TIMEZONE statement specified an invalid code for a timezone name.

The code should be in the range 0 to 63 inclusive. System Action: The operator is prompted to reenter the parameter statement. User Response: Respond to the prompt that follows. The initialization parameter

library should also be updated.

0952E TIMEZONE CODE nn NOT VALID FOR ZONE NAME xxxx Explanation: A TIMEZONE statement specified an invalid code id and timezone name

combination. Certain codes are reserved for certain timezones. These include: 0-LOCAL, 1-UTC, 2-GMT, 3-Z.

System Action: The operator is prompted to reenter the statement. User Response: Use a valid combination. If defining a new zone, use a non-reserved

code id.

0953S ESP SUBSYSTEM CANNOT BE RUN IN BATCH AT INSTALLATION REQUEST

Explanation: The ESP subsystem was being invoked as a batch job. However, the RUNMODE NOBATCH option was specified in the initialization parameter data set.

System Action: The ESP job terminates. User Response: This is a probable user error, by invoking the ESP started task

procedure instead of the command interface module.

0954S TP SERVER INITIALIZATION FAILED, ERROR CODE nn Explanation: The initialization for the VTAM LU 6.2 communication server task

failed. The errors would be described on preceding messages. System Action: The ESP subsystem terminates. User Response: Check preceding messages to find out the nature of the error. It may

be due to initialization parameter errors, such as invalid LU name. After the error has been corrected, restart ESP.

0955W Console xxxx {not found|invalid} Explanation: A CONSOLE command specified either a console that was not found or an

invalid console name. xxxx must be one of the following -

Messages and Codes

ESP-5.4-MC-03 137

A valid 2-8 character console name. An 8 character hexadecimal console ID (1st character must be within range 0-9). A single decimal digit console ID. 1-8 zeros. The following console names may not specified - HC, INSTREAM, OPERLOG, SYSIORES, SYSLOG, UNKNOWN.

System Action: The CONSOLE command is terminated. User Response: Correct CONSOLE specification xxxx and try again.

0956W EMCS console xxxx specification invalid, CNID=yyyy{, System=zzzz} Explanation: A CONSOLE command specified an extended MCS console xxxx.

xxxx must specify a real console. System Action: The CONSOLE command is terminated. User Response: Correct CONSOLE specification xxxx to specify a real console and try

again.

0957W Console xxxx inactive, CNID=yyyy Explanation: A CONSOLE command specified an inactive console xxxx.

yyyy is the console ID of console xxxx. System Action: The CONSOLE command is terminated. User Response: Correct CONSOLE specification xxxx to specify an active console and

try again.

0958W Request only valid from a console Explanation: An asterisk can only be used in a CONSOLE command entered at a console. System Action: The requested function is not completed. User Response: Remove this CONSOLE command from the ESP initialization parameters, or

replace the asterisk by a valid console name.

0959I Primary console is cccc, CNID=iiii{, System=ssss}{, Unit=uuuu} Explanation: This is the description of the primary system console.

cccc specifies the name of the console. ssss specifies the console ID. iiii specifies the name of the system that the console is active on. uuuu specifies the device number of the console.


0960W {Command xxxx|STOP command} rejected, source invalid|unknown Explanation: A MODIFY,xxxx or STOP system command was issued from an invalid or

unknown source. ESP Workload Manager only accepts MODIFY or STOP system commands from a console or TSO address space.

System Action: The MODIFY or STOP command is not processed. User Response: If authorized, re-issue the MODIFY or STOP system command from a

console or TSO address space.

0962E UNABLE TO SET RESERVE QNAME, RESERVE IS ACTIVE Explanation: The QNAME cannot be changed if a RESERVE is presently active.

138 ESP-5.4-MC-03

System Action: The QNAME was not changed. User Response: Try again later.

0965C DDB DISPLAY Explanation: The LISTDDB command displays ESP maintenance levels, shipping dates,

and authorization codes. System Action: User Response:

0966E AUTHORITY CODE OFFSET OUT OF RANGE - 1 TO 32 ALLOWED Explanation: The OFFSET parameter is out of range. Only offset from 1 to 32 are

allowed. System Action: The LISTDDB command is terminated. User Response: Correct the OFFSET and try again.

0967E INVALID DIAGNOSTIC DATA BLOCK Explanation: The Diagnostic Data Block has been damaged. System Action: The LISTDDB command is terminated. User Response: Restore a valid Diagnostic Data Block module to the ESP load library.

0968E PRODUCT xxxx NOT FOUND Explanation: The specified PRODUCT name could not be found in the DDB descriptor. System Action: The LISTDDB command is terminated. User Response: Specify a product name of 'ESP'.

0970I RESERVE LOGIC NOT INITIALIZED Explanation: A RSVLOGIC command was issued with the list option specified, or with

no parameters. However, the RSVLOGIC command had not been used previously to initialize the environment. No reserve/enqueue will be done.

System Action: There is nothing to display. The reserve/enqueue logic is dormant. User Response: If you want reserve/enqueue logic to be performed, use the RSVLOGIC

command to initialize it.

0971S INVALID TOKEN PASSED TO RELEASE/DEQ ROUTINE Explanation: The RELEASE/DEQ routine was passed an invalid token. This is probably

due to an internal logic error. System Action: Since the release or deq could not be performed, the program abends to

release the reserve or cross systems enq. User Response: The resulting dump should be sent to Cybermation technical support. The

subsystem can be restarted.

0972E UNABLE TO UPDATE RSVLOGIC, DATABASE IS CURRENTLY LOCKED

Explanation: The RSVLOGIC method cannot be changed while the database is locked. System Action: The requested function is not performed. User Response: Try the RSVLOGIC command later.

Messages and Codes

ESP-5.4-MC-03 139

0973S POSSIBLE LOSS OF INTEGRITY AS DATABASES ARE NOT ON SAME VOLUME

Explanation: A module required exclusive use of a database. However, a reserve was already outstanding for another database on another volume.

System Action: A second reserve is not performed, as this may cause a deadly embrace. The second database therefore will not have integrity ensured by reserve. This message is only issued once and is normally non-roll deletable.

User Response: The databases should all be placed on the same physical volume if serialization is performed by RESERVE/RELEASE. If this is not possible, the RSVLOGIC initialization statement should specify ENQ/DEQ serialization with GRS active.

0974C RSVLOGIC STATUS Explanation: This command describes the reserve logic now in use by ESP. System Action: User Response:

0975W INVALID MESSAGE ID RANGE, nn:nn Explanation: The first number must be no larger than the second. System Action: User Response: Correct the range and try again.

0976W MESSAGE ID OUTSIDE OF PERMITTED RANGE Explanation: The valid range of message ID's is from 100 to 3500. System Action: User Response: Correct the message ID range and try again.

0977E INVALID MESSAGE TYPE NAME xxxx Explanation: The message type must be INFOR, WARNING, ERROR or SEVERE. System Action: The message was not defined. User Response: Correct the message type and try again.

0979S PUTGET ERROR CODE nn Explanation: The CPE message handler attempted to obtain the next input line

from a TSO user via the PUTGET service routine, but the PUTGET failed with return code nn. PUTGET errors are documented in the IBM publication "TSO/E Programming Services."

System Action: The operation fails. User Response: Investigate the failure of the IBM TSO service routine.

0980S PARM=xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx Explanation: This message follows message 0979 to further explain the PUTLINE

error. The contents of the IOPL are displayed in hex. System Action: See message 0979. User Response: See message 0979.

140 ESP-5.4-MC-03

0990E UNABLE TO LOAD SORT PROGRAM Explanation: The requested sort program could not be found. System Action: The SORT function was not performed. User Response: Specify the correct sort program in the ESP initialization parameters

via the 'SORT pgm' statement, and restart ESP.

0991E ERROR OCCURRED DURING SORT Explanation: The sort program did not complete. System Action: The sort operation was not performed. User Response: Check the console log for further sort error messages, or try a

different sort program.

0999W UNABLE TO OBTAIN SUFFICIENT CSA FOR xxxx Explanation: There is insufficient CSA storage in the MVS system. The required

storage may reside above the 16Mb line. System Action: The command was not executed. User Response: An IPL is required to restore CSA levels.

1001E xxxx INVALID IN A JOBDOC ENTRY Explanation: A statement was encountered in a job documentation entry that is only

valid in an ESPPROC member. System Action: The entire Event is suppressed. User Response: Correct the statement or move it into the calling ESPPROC.

1002E xxxx INVALID OUTSIDE OF A JOBDOC ENTRY Explanation: A statement was encountered in an ESPPROC that is only valid in a job

documentation entry. System Action: The entire Event is suppressed. User Response: Correct the statement or move it into a job documentation entry.

1003E xxxx INVALID OUTSIDE OF A JOB ENTRY Explanation: A statement was found in an ESPPROC that is only valid within the

scope of a JOB statement. System Action: The ESPPROC and the entire Event that called it is suppressed. User Response: Correct the placing of the statement.

1004E P-NODE NAME MISSING OR INVALID Explanation: A PNODE or DUEOUT statement was encountered in a jobdoc or ESPPROC but

the P-node name was omitted, or did not conform to the naming standard.

System Action: The ESPPROC and entire Event that called it is aborted. User Response: A P-node name should consist of 1-16 alphameric characters, including

the underscore character. The first character should be alphabetic.

1005E INCONSISTENT xxxx PARAMETERS Explanation: The parameters on a COREQ, PREREQ, RELEASE, POSTREQ or RESOURCE

statement were not consistent. For example, the ADD or DROP keywords

Messages and Codes

ESP-5.4-MC-03 141

may have been combined incorrectly. System Action: The ESPPROC and the entire Event calling it is aborted. User Response: Correct the specification.

1006E INVALID KEYWORD xxxx Explanation: An invalid keyword was specified on a COREQ, PREREQ, RELEASE, POSTREQ

or RESOURCE statement. System Action: The ESPPROC and entire Event that called it is aborted. User Response: Correct the statement in error.

1007I xxxx Explanation: An error occurred processing a statement in an ESPPROC or while

reading a JOBDOC member. The error will have been described in a preceding message. This message is displaying the contents of the statement in error.

System Action: The action will be based upon the error. User Response: See the description of the preceding message.

1008E INVALID PARAMETER ON CCFAIL STATEMENT Explanation: A CCFAIL statement did not have the correct format. System Action: The ESPPROC is terminated. User Response: Correct the CCFAIL statement in error and trigger the Event again.

1009E INVALID PARAMETER xxxx Explanation: A CCFAIL statement in an ESPPROC or JOBDOC entry had invalid data. System Action: The entire ESPPROC is aborted. User Response: Correct the error, and trigger the Event again.

1010E INVALID PARAMETERS PASSED TO "SELECTED" FUNCTION Explanation: The 'SELECTED' function in an ESP Procedure was passed an invalid

job name or names. The name must be a character variable or literal value, with a length not exceeding 8 characters.

System Action: The entire ESPPROC is aborted. User Response: Correct the job name specification.

1011E JOB xxxx HAS INVALID REFERENCE TO ITSELF Explanation: A job refers to itself on a POSTREQ, PREREQ, COREQ or RELEASE

statement. This is invalid. System Action: The entire ESPPROC is aborted. User Response: Correct the statement in error and trigger the Event.

1012E NET ID REQUIRED BUT NOT SPECIFIED FOR JOB xxxx Explanation: A job specification requested job dependency functions, but no

jobnet ID was specified or defaulted to. Possibly, it was intended to define an application, but the APPL statement was omitted.

System Action: The entire ESPPROC is aborted. User Response: Specify a jobnet ID for the job, and trigger the Event. If an

142 ESP-5.4-MC-03

application is desired, provide an APPL statement prior to the first job.

1013E INVALID RESOURCE NAME xxxx Explanation: A RESOURCE statement specified an invalid resource name or quantity.

A valid name is up to 44 characters in length, beginning with an alphabetic character. It may contain imbedded periods, or hyphens, so any MVS data set name is valid. Each qualifier must begin with an alphabetic character, and be no more than 8 characters long. A resource quantity must be followed by a resource name if specified.

System Action: The ESPPROC is terminated. User Response: Correct the RESOURCE statement in error and reschedule the ESPPROC.

1014E INVALID SYSTEM ID SPECIFIED Explanation: The 'SYSACTIVE', 'SYSEXIST' or 'SYSLREAD' functions were passed an

invalid system ID. The system ID should be a character variable or literal string with a data length of 8 characters or less.

System Action: The ESPPROC containing the error is terminated. User Response: Correct the specification and reschedule the ESPPROC.

1015E xxxx EXCEEDS MAXIMUM ALLOWABLE NUMBER OF RESOURCES Explanation: A RESOURCE statement specified a number of resources greater than the

maximum allowable of 8 megabytes (-/+ 8388607). System Action: The ESPPROC is terminated. User Response: Correct the RESOURCE statement in error and reschedule the ESPPROC.

1016E INVALID JOBNAME/QUALIFIER Explanation: An invalid job name or job name qualifier combination was entered. The

job name and qualifier may not exceed 8 characters each and must be separated by a period.

System Action: The Event is suppressed. User Response: Correct the ESPPROC and trigger the Event again.

1017E INVALID PARAMETERS PASSED TO JOBONQ FUNCTION Explanation: The job name and prefix parameters must be no longer than eight

characters. They must begin with an alphabetic or national character, and the remaining characters must be alphanumeric. The third parameter must be either E, I, O, H, or U.

System Action: The JOBONQ function was not performed. User Response: Correct the parameters and try again.

1018E SUBSYSTEM REQUEST ERROR CODE nn ENCOUNTERED BY JOBONQ FUNCTION

Explanation: A serious error has occurred with either JES or the ESP subsystem. System Action: The JOBONQ function was not performed. User Response: Check the status of JES and the ESP subsystem.

Messages and Codes

ESP-5.4-MC-03 143

1019E RESOURCES ARE NOT ALLOWED WITH LINKS Explanation: A link has been defined, and its definition contains a RESOURCE

statement. This is invalid. System Action: The RESOURCE statement is ignored. If the event was triggered, then

processing is stopped. If the event was simulated, then it proceeds. User Response: Remove the RESOURCE statement.

1020E ABANDON STATEMENT PARAMETERS OMITTED OR INVALID Explanation: An ABANDON statement in an ESPPROC or job documentation member

contained an invalid parameter. System Action: The Event is failed. User Response: Correct the ABANDON statement. Check the command reference manual for

the correct syntax.

1021W JOB xxxx.qqqq IN APPL aaaa.nn, LATE SUBMIT TIME EXCEEDED Explanation: A job has missed its late submit time. The late submit time was

specified in the definition of the job. System Action: The job is considered overdue. User Response: You should display the application to find out what the job is

waiting on.

1022W JOB xxxx.qqqq IN APPL aaaa.nn, LATE END TIME EXCEEDED Explanation: A job has missed its late end time. The late end time was specified

in the definition of the job. System Action: The job is considered overdue. User Response: The job's performance group or priority should be raised if this is

a critical job.

1023I Auditlog data set spun with nn records to sysout class xxxx Explanation: A SPINLOG command was executed, resulting in the Auditlog data set

being closed and spun off to JES. This message indicates how many records were contained that data set.

System Action: A new data set is allocated and processing continues. User Response: The spun data set is available for viewing, or can be printed or

collected by a sysout archival program.

1024E Above error occurred while trying to open a new Auditlog data set, Auditlog will be unavailable

Explanation: A SPINLOG command was executed, resulting in the closing and deallocation of an Auditlog data set. On attempting to allocate and open a new one, an error occurred. The error is described by the previous message.

System Action: The Auditlog data set will not be available, and audit information may be lost until ESP is restarted.

User Response: ESP should be restarted. If the error persists, comment out the AUDITLOG initialization statement and place an AUDITLOG DD statement in the ESP started task procedure until the problem can be resolved.

144 ESP-5.4-MC-03

1025W Dynamic sysout auditlog not initialized, use AUDITLOG initialization parameter

Explanation: The SPINLOG command was issued. This command is only available if the AUDITLOG initialization parameter is used.

System Action: The command is not executed. User Response: Add the AUDITLOG initialization statement to the ESP parameter data

set and restart ESP. The AUDITLOG statement has the following syntax: AUDITLOG c <FORM(ffff)> <EXTWTR(xxxxxxxx)> <AUDCOUNT(nnnnnnnn)> where c is a one character sysout class ffff is an optional sysout form name, of up to 4 characters xxxxxxxx is an optional external writer name, of up to 8 characters nnnnnnnn is an optional maximal number of records written to the AUDITLOG data set before it is spun

1026E ERROR SENDING JOB TRACKING DATA TO xxxx - FDBK = X'yyyy' Explanation: The ESP inter-system job tracking manager attempted to send tracking

data to another node using the TP server but failed, resulting in feedback code yyyy.

System Action: The transaction remains on the checkpoint until a successful send can be carried out.

User Response: Issue a TPAPPL xxxx DISPLAY to see if the VTAM sessions are still active. If the feedback codes do not indicate an immediate solution, contact Cybermation support.

1027E ISCDEF STATEMENT INCOMPATIBLE WITH ISCOPT LU62 Explanation: In the ESP initialization parameters, the LU 6.2 TP server was chosen

as the method of inter-system communication via the ISCOPT statement. The statement ISCDEF is valid only for the NJE method.

System Action: The statement is rejected. User Response: Specify either ISCOPT NJE or remove the statement in question.

1028E UNABLE TO START INTERSYSTEM JOB TRACKING, FDBK = X'xxxx' Explanation: The inter-system tracking receiver component of ESP attempted to

register its transaction name INTER_SYSTEM_JOB_TRACKING) with the TP server, but was unable to do so, resulting in the feedback code xxxx.

System Action: The transaction handler is not registered with the TP server. Any transactions directed toward the name xxxx are retained on the originating checkpoint.

User Response: If the problem cannot be determined from the feedback code, contact Cybermation support.

1029E UNABLE TO RECEIVE INTER SYSTEM TRACKING DATA, FDBK = X'xxxx'

Explanation: The inter-system tracking receiver component of ESP attempted to issue a receive to the TP server but was unable to do so, resulting in the

Messages and Codes

ESP-5.4-MC-03 145

feedback code xxxx. System Action: ESP will not obtain the tracking data; it will be stored on local

checkpoint until a receive can be properly completed. User Response: If the problem cannot be determined from the feedback code, contact

Cybermation support.

1030E UNABLE TO STOP ISC TRACKING RECEIVER, FDBK = X'xxxx' Explanation: During shutdown processing, ESP attempted to instruct the TP server to

begin cleanup for its intersystem job tracking transaction handler. The stop failed with a TP feedback code of xxxx.

System Action: ESP shutdown processing continues. The TP server's cleanup processing should complete the stop request.

User Response: If ESP shuts down successfully, there is not a problem. Otherwise, contact Cybermation support.

1031I INTER-SYSTEM TRACKING RECEIVER IS STOPPED Explanation: ESP has successfully stopped the receiver for inter-system job

tracking data. System Action: None. User Response: None.

1032E UNABLE TO START INFOSERV_JOB_TRACKING PROCESSOR, FDBK = X'xxxx'

Explanation: The Infoserv job tracking response processor component of ESP attempted to register its transaction name (INFOSERV_JOB_TRACKING) with the TP server, but was unable to do so, resulting in the feedback code xxxx.

System Action: The transaction handler is not registered with the TP server. Any transactions directed toward the name INFOSERV_JOB_TRACKING are retained on the originating checkpoint.


1033E UNABLE TO RECEIVE INFOSERV JOB TRACKING RESPONSE DATA, FDBK = X'xxxx'

Explanation: The Infoserv job tracking response processor component of ESP attempted to receive data from the TP server but was unable to do so, resulting in the feedback code xxxx.

System Action: ESP will not obtain the response data; it will be stored on the local checkpoint until a receive can be properly completed.


1034E UNABLE TO STOP INFOSERV_JOB_TRACKING PROCESSOR, FDBK = X'xxxx'

Explanation: Due to a previous error condition, ESP attempted to shutdown its INFOSERV_JOB_TRACKING transaction handler. The stop failed with a TP feedback code of xxxx.

System Action: Processing continues. The TP server's cleanup processing should

146 ESP-5.4-MC-03

complete the stop request. User Response: Contact Cybermation support to report the error.

1035I INFOSERV_JOB_TRACKING PROCESSOR IS STOPPED Explanation: ESP has successfully stopped the receiver for inter-system job

tracking data. System Action: Processing continues. User Response: None.

1036E ERROR CODE nn PROCESSING INFOSERV RESPONSE BUFFER Explanation: The Infoserv job tracking response processor component of ESP

encountered an error while processing a response from INFOSERV. This is an internal error condition.

System Action: The response is not processed. Processing continues. User Response: Report the error code to Cybermation support.

1037E INSUFFICIENT SPACE IN xxxx APPL RECORD FOR INFO/SYSTEM UPDATE TO JOB yyyy

Explanation: When ESP attempted to update a job for which an information management record was created, insufficient space was available to update the APPL descriptor record.

System Action: The job will not be updated with the information management record number.

User Response: It may be possible to increase the maximum size of an ATR. Enlarge the APPLBUF parameter in the startup parameters. If it is necessary to expand APPLBUF beyond 4 megabytes, please contact Cybermation support for further information.

1038W Insufficient space in xxxx APPL record for status message insertion for JOB yyyy

Explanation: A job in an application had a change of state. However, insufficient space was available in the application's database record (ATR) to insert the status message string.

System Action: The scoreboard may not properly display the object's true state. User Response: It may be possible to increase the maximum size of an ATR. Enlarge

the APPLBUF parameter in the startup parameters. If it is necessary to expand APPLBUF beyond 4 megabytes, please contact Cybermation support for further information.

1039E Unknown alert ID: xxxx Explanation: The application requested an alert named xxxx. However, no such

alert is defined in the system. System Action: The alert request is ignored. Processing of the application

continues. User Response: Either correct the alert name, or define the alert.

1040E QUEUE update not allowed from a proxy subsystem Explanation: A cleanup of the QUEUE data set was attempted from a proxy subsystem.

Messages and Codes

ESP-5.4-MC-03 147

System Action: Request ignored. User Response: Any update of the QUEUE data set can be done only from the master

subsystem of an ESP Workload Manager master/proxy complex.

1041W MULTIPLE NET RELEASES NOT PERMITTED FOR JES3 Explanation: The NETREL parameter of a DJCDATA statement specifies more than

one job which is not permitted in the JES3 environment. System Action: The event is not executed. User Response: Re-enter the event specifying only one job per NETREL request on

the DJCDATA statement.

1042E Insufficient checkpoint space to queue type 9 XME Explanation: The Application Manager has modified a job's LATESTART or LATEEND time

after the job was readied, and is attempting to inform the Tracking Manager of this action. However, there is not enough checkpoint space available to build the necessary control block.

System Action: The Tracking Manager is not notified of the reset time(s), with the result that this data will not be reflected on the job history file. This message is followed by message 1043E, which gives details of the affected job.

User Response: Investigate and remedy the reason for the shortage of checkpoint space. Be aware that this job's modified overdue times will not be propagated to the job history file.

1043E Error occurred for job jjjj in appl aaaa.ggg Explanation: This message is preceded by message 1042E. It indicates that the

error noted in the previous message was encountered while processing job 'jjjj' in generation 'ggg' of application 'aaaa'.

System Action: See the description of the preceding message. User Response: Follow the instructions for the preceding message.

1044E Job jjjjÕ(nnn)þ in appl aaaa.ggg not being tracked Explanation: The Application Manager has modified a job's LATESTART or LATEEND time

after the job was readied, and is attempting to inform the Tracking Manager of this action. However, the Tracking Manager has no knowledge of this job. This is an extremely unlikely situation, which may indicate a timing problem between these two modules.

System Action: The modified time(s) will not be reflected on the job history file. User Response: Be aware that this job's modified overdue time(s) will not be

propagated to the job history file. Contact Cybermation technical support for further assistance.

1045E Error occurred updating job jjjjÕ(nnn)þ in appl aaaa.ggg Explanation: This message is issued when an error occurs while attempting to update

a job's tracking record. It indicates the job name, job number (if available), and the application name and generation affected. It is preceded by another message giving details of the exact error encountered.

System Action: See the description of the preceding message.

148 ESP-5.4-MC-03

User Response: Follow the instructions for the preceding message.

1046W Application manager is waiting for checkpoint space. Explanation:

Application manager could not obtain space from checkpoint area. It will wait for space shortage to be relieved and then retry.

System Action: Processing continues, with some functions delayed.

User Response: Checkpoint should be made bigger to prevent processing delays.

1047E Insufficient space in xxx APPL record to store event parms for yyy Explanation: When ESP attempted to update an Application to store the filename

returned by the File_Trigger workload object named yyy, insufficient space was available to update the Application descriptor record.

System Action: The Application will not be updated. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


1048W Command rejected, High Performance Option not enabled Explanation: An APPLJOB or AJ command or equivalent CSF line command was issued

that requires that the High Performance Option (HPO) be enabled. System Action: The command is not processed. User Response: None.

1050E NOT AUTHORIZED FOR REXXON STATEMENT Explanation: A REXXON statement was encountered in an ESP procedure. SAF security

is in effect, and the RACID associated with the Event did not have read access to the REXXON resource.

System Action: The REXX code is not processed. The Event is not executed. User Response: If you need access to the REXX facility, request read access to the

REXXON resource from your administrator.

1051E Not authorized for ABSORB statement Explanation: You do not have authorization to use the ABSORB function. System Action: The application is not generated. User Response: Remove the ABSORB statement. Or, have your security administrator

grant read access to the profile prefix.RESABSORB.

1052E Invalid resource quantity at offset nn in RELRES list Explanation: The resource quantity in the RELRES list is not numeric. System Action: The status of the resource is not altered. The remainder of the

RELRES list is ignored. User Response: Correct the RELRES statement.

1053E Resource name expected at offset nn in RELRES list Explanation: The resource name was missing from the RELRES list.

Messages and Codes

ESP-5.4-MC-03 149

System Action: The resource status is not altered. The remainder of the RELRES list is ignored.

User Response: Correct the RELRES statement.

1054E Command invalid outside of job entry Explanation: An StepEnd statement was encountered, but it was not within a job. System Action: The statement is rejected. An event error results. User Response: Reposition or remove the statement.

1057I Procedure cache status Explanation: This message is displayed on the console in response to PCACHE

command. It serves as a header for subsequent messages that provide details about procedure caching.

System Action: N/A User Response: N/A

1058I Critical path calculation is ssss Explanation: This message is a response to CRITPATH operator command. It displays

the status of dynamic critical path processing by ESP/WM. This setting does not affect the calculation of critical path by LISTAPPL command. The possible values of ssss are: ON - path calculated for applications that don't suppress it, ENABLED - path calculated for applications that request it, DISABLED - critical path is not calculated.


1101W Data set type not specified Explanation: The RESTORE command did not specify the data set type to be restored. System Action: The command is ignored. User Response: Re-enter the command specifying a data set type of EVENT, HISTFILE,

JOBINDEX or INDEX.

1102I Restore to new VSAM data set xxxx in progress Explanation: Restore processing is now in progress. The data set specified in the

NEWDSNAME parameter will contain the new and updated version of the data set being restored.


1103I Restore of VSAM data set xxxx in progress Explanation: Restore processing is now in progress. The original data set will be

restored to its current version. System Action: Processing continues. User Response: None.

1104E Error allocating new VSAM data set xxxx Explanation: An error occurred while allocating the specified data set for output

150 ESP-5.4-MC-03

during restore processing. System Action: Restore processing is terminated. User Response: The preceding message will describe the error condition. Reissue the

RESTORE command after the problem is diagnosed and corrected.

1105E Error allocating VSAM data set xxxx Explanation: An error occurred while allocating the specified data set for output

during restore processing. System Action: Restore processing is terminated. User Response: The preceding message will describe the error condition. Reissue the

RESTORE command after the problem is diagnosed and corrected.

1106I Record in error was from SMF JOURNAL data set Explanation: An error occurred while writing a JOURNAL record to the output data

set during restore processing. System Action: Restore processing is terminated. User Response: The preceding message will describe the error condition. Message

ESP1108I will follow describing which record key was being processed when the error occurred. Reissue the RESTORE command after the problem is diagnosed and corrected. If unable to diagnose problem, notify your support personnel.

1107I Record in error was from BACKUP data set xxxx Explanation: An error occurred while writing to the output data set during restore

processing. The record in error is from the specified BACKUP data set.

System Action: Restore processing is terminated. User Response: The preceding message will describe the error condition. Message

ESP1108I will follow describing which record key was being processed when the error occurred. Reissue the RESTORE command after the problem is diagnosed and corrected. If unable to diagnose problem, notify your support personnel.

1108I Key at time of error: xxxx Explanation: An error occurred while writing to the output data set during restore

processing. The message shows the VSAM key of the record being processed at the time the error occurred.

System Action: Restore processing is terminated. User Response: The preceding messages will describe the error condition. Reissue the

RESTORE command after the problem is corrected. If unable to diagnose problem, notify your support personnel.

1109I nn records restored from BACKUP data set Explanation: The count represents the total number of records restored from the

BACKUP data set for which no corresponding updates were found in the JOURNAL file.


Messages and Codes

ESP-5.4-MC-03 151

1110I nn updates restored from JOURNAL data set Explanation: The count represents the total number of records restored from the SMF

entries in the JOURNAL data set. The journal records contain the most current entries for the file being restored.


1111I Restore of VSAM data set xxxx ended successfully Explanation: The RESTORE command issued for the specified data set was successfully

executed. The restored VSAM data set (or optional NEWDATASET) now contains the most recent updates since the last backup.


1112I nn records written to VSAM data set Explanation: The count represents the total number of records written to the VSAM

data set during restore processing. This message is followed by message ESP1113.


1113E Restore of VSAM data set xxxx terminated due to errors Explanation: The RESTORE operation failed due to I/O errors on the VSAM data set.

This message is preceded by message ESP1112. System Action: The VSAM data set will have been partially rewritten. User Response: Check the preceding messages for more information on the cause of the

error.

1114E VSAM control record not found in BACKUP data set xxxx Explanation: The BACKUP data set has been damaged or has not been written to. System Action: The RESTORE operation is terminated. User Response: Retry the RESTORE operation after locating a valid BACKUP data set.

1115E Error occurred processing BACKUP data set xxxx Explanation: The BACKUP data set has been damaged. System Action: The RESTORE operation is terminated. User Response: Retry the RESTORE operation after locating an undamaged BACKUP data

set.

1116E Error occurred processing SORT data set Explanation: An I/O error occurred while processing the SORT input data set. System Action: The sort operation is terminated. User Response: Check the previous message for further information.

1117E Invalid SMF record ID nn, must be in range 1-255 Explanation: The SMF record number in the SMFID parameter was out of range. System Action: The journal sort was not performed.

152 ESP-5.4-MC-03

User Response: Correct the SMFID parameter and try again.

1118E Error occurred during sort processing Explanation: An I/O error occurred while processing the SORT output data set. System Action: The sort operation is terminated. User Response: Check the previous message for further information.

1119E Error occurred processing JOURNAL data set Explanation: An I/O error occurred while attempting to sort the JOURNAL data set. System Action: The sort operation is terminated. User Response: Check the previous message for further information.

1120W APPL FILE xxxx UNFORMATTED Explanation: The specified APPL file was found to be unformatted. This is expected

the first time the data set is used. System Action: ESP follows with message 1121. User Response: Respond to message 1121.

1121A REPLY 'Y' TO FORMAT THE APPL FILE, OR REPLY 'N' Explanation: The APPL file was found to be unformatted. Before proceeding to format

it, ESP requests permission from the operator. System Action: ESP waits for the reply. User Response: If you wish the APPL file to be formatted, reply Y, otherwise reply N

and ESP will terminate. The APPL file should only need to be formatted once, or after it has been newly created. If this is not the first time the data set is used, call your software support personnel.

1122W INVALID RESPONSE Explanation: An invalid response was given to a prompt message. The prompt is

expecting a 'Y' or 'N'. System Action: The prompt is reissued. User Response: Respond to the reprompt.

1123E CORRECT THE ABOVE PROBLEM AND RESTART ESP Explanation: This message is issued after an error has occurred that prevents to



1124I STARTING TO FORMAT THE APPL FILE xxxx Explanation: The formatting run of the APPL file has begun. You may expect this to

take an appreciable amount of time. System Action: The APPL file is formatted. User Response: None. Be patient.

1125I APPL FILE FORMAT COMPLETE Explanation: The formatting run of the APPL file has been completed.

Messages and Codes

ESP-5.4-MC-03 153


1126E APPL FILE DATASET IS TOO SMALL Explanation: The APPL file data set is too small for effective processing. System Action: The APPL file cannot be used. User Response: Allocate a larger file and restart ESP. The file should be at least 10

cylinders in size.

1127E xxxx Explanation: An error occurred reading or writing an APPL file. System Action: This message is followed by another message indicating what action is

to be taken. User Response: Note the message that follows.

1128S APPL FILE DATASET xxxx UNUSABLE Explanation: An error occurred processing an APPL file. This message would have

been preceded by a message indicating the nature of the error. System Action: The data set cannot be used, and ESP will terminate. User Response: The APPL file data set may need to be restored from a backup.

1129W JOB xxxx ALREADY EXISTS IN APPL yyyy Explanation: An attempt was made to insert a job into an active application.




1130E APPLFILE xxxx NOT FOUND FOR EVENT yyyy Explanation: An Event required to retrieve an application file record. However,

the required APPLFILE was not found. System Action: The Event is not processed. The job that was to be submitted will not

be submitted. User Response: Ensure that the APPLFILE definition is in the initialization parameter

data set.

1131E I/O ERROR OCCURRED READING APPL RECORD FOR EVENT xxxx Explanation: An I/O error occurred reading an APPL file record. This message will

have been preceded by a message describing the nature of the error. System Action: The Event is not processed. User Response: The APPLFILE may need to be restored. Notify your software support

personnel.

1132W The QUEUE data set is temporarily full. nn bytes are being used for tracking purposes

Explanation: An ESP subsystem, executing with the job tracking processor in proxy mode, tried to queue a tracking record to the master tracking

154 ESP-5.4-MC-03

processor. However, either the queue data set is full, or the threshold for tracking data has been reached.

System Action: The tracking information is retained in the proxy processor checkpoint data set and a retry is attempted later.

User Response: Ensure that the master tracking processor is active.

1133W The ESP MASTER system is either not tracking or is temporarily busy. Explanation: This message follows message 1132. See the documentation of that

message for more information. System Action: See message 1132. User Response: Ensure the master tracking system is active. If not, the TRACKOPT

command can be used to make this a master system.

1134E INSUFFICIENT SPACE TO BUILD DESCRIPTOR FOR APPL xxxx, EVENT yyyy

Explanation: During the execution of an Event using an ESP APPL, insufficient space was available to build the APPL descriptor record.

System Action: The APPLICATION is not built. User Response: The APPL record size may have to be increased, or the number of jobs

in the application reduces. The application may have to be split into two or more applications.

1135E APPL FILE xxxx NOT FOUND FOR EVENT yyyy Explanation: An APPL file could not be found during application processing for an

Event. System Action: The APPL is not built. User Response: Ensure that the Event group or userid entry is assigned to a valid

APPL file.

1136E I/O ERROR OCCURRED BUILDING INDEX ENTRY FOR APPL xxxx, EVENT yyyy

Explanation: An I/O error occurred on the job index file while building an index entry for an application. The name of the application and the name of the Event generating it are identified in the message.

System Action: The application record is not stored. User Response: The nature of the error is described in the message preceding this

one. Depending on the error, the jobindex data set may need to be reorganized or restored from a backup and journal. After the problem is corrected, the Event will have to be retriggered manually to rebuild the application.

1137E I/O ERROR OCCURRED WRITING APPLICATION RECORD FOR APPL xxxx, EVENT yyyy

Explanation: An I/O error occurred on an APPL file while writing the application tracking record. The name of the application and the name of the Event generating it are identified in the message.

System Action: The application record is not stored. User Response: The nature of the error is described in the message preceding this

one. Depending on the error, the APPL file may need to be restored

Messages and Codes

ESP-5.4-MC-03 155

restored from a backup. After the problem is corrected, the Event will have to be retriggered manually to rebuild the application.

1138E INSUFFICIENT CHECKPOINT SPACE TO QUEUE ACTIVATION REQUEST FOR APPL xxxx, EVENT y

Explanation: An application was just built during the execution of an Event. However, insufficient checkpoint space was available to queue an activation request to the application manager.

System Action: A special flag is set to cause the application manager to search for all unactivated applications. This may cause ESP to pause for a few seconds.

User Response: If this message is repeated, check into the availability of checkpoint space by use of the LISTCKPT command. Checkpoint space can be exhausted if the tracking mode is 'NOSTORE' or the current processor is a proxy processor and the master processor is not active.

1139E APPLICATION PROCESSING IS NOT ACTIVE Explanation: A user issued a command related to the application processing function

of ESP. That function is not active. System Action: The command is not processed. User Response: The application processing function must be activated. This requires

the tracking facility as well as at least one APPLFILE data set.

1140E APPLFILE xxxx NOT FOUND Explanation: An APPLFILE, required by an application processing command was not

found. System Action: The command is not processed. User Response: This may be due to the omission of an APPLFILE statement in the

initialization parameter data set.

1141W APPLICATION xxxx NOT DEFINED Explanation: An APPLICATION requested by a user was not found. System Action: The APPLICATION is not processed. User Response: Ensure the application name is specified correctly.

1142W NO MATCHING APPLICATIONS DEFINED OR NOT AUTHORIZED Explanation: A user requested the retrieval of one or more applications. However,

no matching applications were found. System Action: The request is not processed. User Response: Ensure the name is correctly specified, and that you have proper

authority to the application.

1144E APPLFILE xxxx IS CLOSED Explanation: An application record retrieval failed because the required APPLFILE

was closed. System Action: The record is not retrieved. User Response: Determine the reason the file was closed. Retry when the file becomes

available.

156 ESP-5.4-MC-03

1145E YOUR AUTHORITY IS INSUFFICIENT FOR ACCESS, OR APPLICATION xxxx NOT FOUND

Explanation: A requested application record could not be retrieved for one of two reasons. It is either not defined, or the user requesting it did not have the appropriate authority to access it. The application must belong to the user, or to a group to which the user is connected with sufficient access.

System Action: The record is not retrieved. User Response: Ensure the application name was specified correctly or grant the user

sufficient access to the application record.

1146E INSUFFICIENT CHECKPOINT SPACE TO QUEUE REQUEST Explanation: An application processing command was issued which required the

service of the application manager. However, insufficient space was available in the checkpoint data set to queue the request.

System Action: The request is not queued. User Response: Retry the command a little later.

1147E REQUIRED GENERATION OF APPLICATION xxxx NOT FOUND Explanation: A particular absolute or relative generation of an application was

requested. However, that generation was no longer available. System Action: The request is not processed. User Response: Ensure you have specified the correct application name and generation

number.

1148E APPLFILE xxxx NOT FOUND FOR APPLICATION yyyy GEN nn Explanation: During ESP initialization, the application manager was performing a

scan of incomplete applications. An application was found whose APPLFILE could not be located.

System Action: The application is not queued for processing. User Response: Either the APPLFILE definition was omitted from the initialization

parms, or the application index record is in error. To correct the former, add the APPLFILE statement to the parameter data set and restart ESP. If the application is in error, use the APPL command to mark it complete.

1149E APPL MANAGER ENCOUNTERED ABOVE ERROR WHILE SCANNING THE JOBINDEX FILE

Explanation: During ESP initialization, the application manager encountered an I/O error while scanning the JOBINDEX file for incomplete applications. The error is described by a preceding message.

System Action: One or more applications may not be processed by the application manager.

User Response: When the error with the jobindex data set is corrected, ESP can be restarted to pick up all the applications.

Messages and Codes

ESP-5.4-MC-03 157

1150I nn Applications are active Explanation: After ESP initialization, the Application Manager determines the

number of currently active Applications. The number of active Applications is "nn".

System Action: The Applications are processed by ESP as needed. User Response: None.

1151E INVALID FILE RECORD FOUND FOR APPL xxxx, GENERATION nn, SLOT nn

Explanation: The application manager was processing an application that was marked incomplete in the jobindex file. However, the APPLFILE record for the application was invalid, or did not correspond to the jobindex entry.

System Action: The application is not picked up for processing. User Response: The application may need to be purged. This error could also be caused

by a bad copy of the APPLFILE. If the APPLFILE is restored, a restart of ESP will pick up the application again.

1152E ABOVE I/O ERROR OCCURRED READING APPL xxxx, GENERATION nn, SLOT nn

Explanation: An I/O error occurred reading an APPLFILE record for an active application. The error is described in a preceding message.

System Action: The application can not be processed. User Response: If the I/O error is corrected, a restart of ESP will cause the

application to be picked up again.

1153W APPLICATION MANAGER QUIESCED DUE TO PRIOR REQUEST Explanation: The application manager is quiescing due to a prior operator command. System Action: Processing of applications will be deferred until a restart request is

given. User Response: None.

1154W APPLICATION MANAGER UNABLE TO ESTABLISH TIMER Explanation: An error in timer management prevented the application manager from

establishing a time interval. System Action: The application manager may not be as responsive as normal. It will

still perform fully, but will only be spurred into action by a direct request, or when an application managed job starts or terminates.


1155E INVALID ACTION CODE xxxx IN APPLICATION JOB QUEUE ELEMENT

Explanation: An application job queue element had an invalid time action code. System Action: The timed action is ignored. User Response: This is due to a logic error. Notify your software support personnel.

158 ESP-5.4-MC-03

1156E INSUFFICIENT CHECKPOINT SPACE TO QUEUE JOB xxxx IN APPL yyyy FOR SUBMISSION

Explanation: The application processor could not obtain enough checkpoint space to queue a job submission request.

System Action: The job is not queued for submission. It will be selected a little later.

User Response: The checkpoint space situation should be monitored.

1157E INSUFFICIENT CHECKPOINT SPACE TO NOTIFY APPL MANAGER OF JOB STATUS FOR JOB xxxx,

Explanation: The tracking processor could not notify the application manager of the change of job status for a job.

System Action: The application manager may not be notified of job completion. User Response: The job may have to be manually posted.

1158E ABOVE I/O ERROR OCCURRED WRITING APPL xxxx, GENERATION nn

Explanation: The application manager encountered an error while updating an APPLFILE entry for an application. The nature of the error is described in the preceding message.

System Action: Some application information may be lost. User Response: The remedial action depends on the error. Physical damage to the

data set may require the restoration of the data set.

1159I APPLICATION xxxx GENERATION nn IS NOW COMPLETE Explanation: An application has just completed processing. All jobs have completed

or have been forced complete. System Action: The application space on the APPLFILE is marked as being free. If

another generation of the application is waiting, it will now be activated.


1160E ERROR OCCURRED READING INDEX ENTRY FOR APPL xxxx.nn Explanation: The application manager was attempting to update the entry in the

jobindex data set for an application. However, an error occurred. The error is described in a preceding message.

System Action: The index entry is not updated. User Response: The remedial action will depend on the exact nature of the error.


1161E ERROR OCCURRED UPDATING INDEX ENTRY FOR APPL xxxx.nn Explanation: The application manager was attempting to update the entry in the

jobindex data set for an application. However, an error occurred during the write. The error is described in a preceding message.

System Action: The index entry is not updated. User Response: The remedial action will depend on the exact nature of the error.


Messages and Codes

ESP-5.4-MC-03 159

1162E INVALID REQUEST CODE xxxx PASSED TO APPLICATION MANAGER

Explanation: The application manager was issued a request that was invalid. System Action: The request is ignored. User Response: This is probably due to a logic error. It could also happen if an

older release of ESP is brought up using a checkpoint data set used by a newer release of ESP.

1163E UNABLE TO LOCATE JOB xxxx FOR RESUBMIT IN APPL yyyy Explanation: The application manager was given a request to resubmit a job, but

could not find it in the application record. System Action: The resubmit request is not processed. User Response: This is probable an internal logic error. Please notify your software

support personnel.

1164W REQUESTED GENERATION OF APPL xxxx NOT FOUND Explanation: A user requested action on a job within an Application. The requested

Application did not exist. System Action: The command is aborted. User Response: Use the LISTAPPL command to confirm the existence of the specified

Application.

1165E JOB xxxx NOT FOUND IN APPL yyyy Explanation: An application job manipulation command identified a job that was not

found for the requested application. System Action: The command is not processed. User Response: Issue the LISTAPPL command to verify the job name. If the job has a

qualifier ensure the qualifier is specified correctly.

1166E INSUFFICIENT CHECKPOINT SPACE TO ISSUE REQUEST TO APPLICATION MANAGER

Explanation: An application modification request could not complete as there was insufficient space to queue the request.

System Action: The request is not processed. User Response: Try the command again later.

1167E JOB xxxx IS NOT A MEMBER OF AN APPLICATION Explanation: An application manipulation command was issued for a job that is not

part of an application. System Action: The command is not processed. User Response: Ensure that the job name/number is specified correctly.

1168E Application request not valid from a proxy subsystem Explanation: An application processing related request was made to ESP. However,

the request is only valid from a master ESP subsystem, and not a proxy subsystem.

160 ESP-5.4-MC-03

System Action: The request is ignored. User Response: Reissue the command from the master ESP address space.

1169E APPL xxxx GENERATION nn IS NOW SUSPENDED Explanation: An I/O error had previously occurred reading a record for an

application. A message describing this error will have preceded this message.

System Action: The application cannot be processed, so will be suspended by the application manager.

User Response: If the I/O error is a hard I/O error, the application will need to be rebuilt by manual trigger. Otherwise, the application can be resumed by using the APPL command.

1170C APPLICATION TRAKFILE DISPLAY Explanation: This is the control line preceding a display of application file(s) in

response to a LISTAPTF command. System Action: The display follows. User Response: None

1171W APPLID STATEMENT ONLY ALLOWED ONCE Explanation: An APPLID or APPL statement was encountered more than one time in an

ESP procedure. It should only be specified once, as an ESP Procedure can only define a single application at a time.

System Action: The second and subsequent APPL statements are ignored. User Response: Ensure that only one APPL statement is executed.

1172W APPLID SPECIFIED FOR JOB xxxx WHICH IS NOT EXTERNAL, IGNORED

Explanation: The APPLID keyword was specified on a JOB statement. However, the job was not identified as an external or manual submit job. In this case, the application identifier is taken from the APPL statement.

System Action: The APPLID keyword is ignored. User Response: Remove the APPLID keyword. One Event can only define a single

application.

1173E INVALID SCOPE TIME xxxx Explanation: The SCOPE keyword on a job statement had invalid syntax. The form

should be HH or HH.MM, optionally prefixed with a plus or minus sign, where HH and MM are numbers in the range 0-59.

System Action: The JOB statement is flagged as in error. The Event is not processed. User Response: Correct the statement, using the above guidelines.

1174E DATA SET xxxx IS NOT PARTITIONED Explanation: An LSAR command with the TAPEPULL keyword was specified. However, the

output data set was not a partitioned data set. System Action: The tape pull data set cannot be created. User Response: Allocate a partitioned data set and reissue the command.

Messages and Codes

ESP-5.4-MC-03 161

1175I JOB TRACKING DEFINITION TABLE LOADED Explanation: A LOADJTDT command was successfully executed. System Action: The new job tracking definition table is now active. User Response: None.

1176E COMMAND xxxx INVALID IN JOB TRACKING DEFINITION TABLE Explanation: A Job Tracking Definition Table contained an invalid command. System Action: The Job Tracking Definition Table is not loaded. User Response: Correct the table and reissue the LOADJTDT command.

1177E ABOVE ERROR OCCURRED OPENING JOB TRACKING DEFINITION TABLE

Explanation: A LOADJTDT command encountered an error allocating or opening a Job Tracking Definition Table. The preceding message will have described the error.

System Action: The Job Tracking Definition Table is not loaded. User Response: Ensure the table name was specified correctly and reissue the LOADJTDT

command.

1178E ABOVE ERROR OCCURRED READING JOB TRACKING DEFINITION TABLE

Explanation: An error occurred while reading in a Job Tracking Definition Table. The error is described in a preceding message.

System Action: The Job Tracking Definition Table is not loaded. User Response: After the error is corrected, reissue the LOADJTDT command.

1179E INVALID COMMAND SYNTAX DETECTED IN LINE nn OF JOB TRACKING DEFINITION TABLE

Explanation: A Job Tracking Definition Table contained a statement with invalid syntax.

System Action: The Job Tracking Definition Table is not loaded. User Response: Correct the table definition and reissue the LOADJTDT command.

1180E ABOVE ERROR OCCURRED ON LINE nn OF JOB TRACKING DEFINITION TABLE

Explanation: An error was detected in a Job Tracking Definition Table statement. The error is described in a preceding message. This message indicates the line number containing the error.

System Action: The Job Tracking Definition Table is not loaded. User Response: Correct the error and reissue the LOADJTDT command.

1181E INVALID MODEL SPECIFICATION xxxx Explanation: An invalid model specification was entered in a TRACKDEF entry in a

Job Tracking Definition Table. System Action: The Job Tracking Definition Table is not built. User Response: Correct the error and reissue the LOADJTDT command. The model

specification should be in the form xxxx(i:j) or xxxx(i) where xxxx is

162 ESP-5.4-MC-03

JOBNAME, NAME, RACID, PGMR, ACCOUNT1, ACCOUNT2, ACCOUNT3 or ACCOUNT4. The bounds i and j should not be greater than 20 for PGMR or 8 for the other parameters. The model name being constructed should not exceed 8 characters.

1182E MODEL SPECIFICATION EXCEEDS 8 CHARACTERS Explanation: A model name was being constructed in a TRACKDEF entry in a Job

Tracking Definition Table. The combination of parameters caused a name of more than 8 characters to be constructed.

System Action: The Job Tracking Definition Table is not loaded. User Response: Correct the error and reissue the LOADJTDT command.

1183E INVALID WILDCARD RANGE, xxxx Explanation: A WILDCARD statement in a Job Tracking Definition Table had an invalid

character range. System Action: The Job Tracking Definition Table is not loaded. User Response: Correct the error and reissue the LOADJTDT command.

1184E TOO MANY WILDCARDS DEFINED, LIMIT IS 60 Explanation: A Job Tracking Definition Table was being loaded. The table contained

more than 60 WILDCARD statements. System Action: The Job Tracking Definition Table is not loaded. User Response: Correct the error and reissue the LOADJTDT command.

1185E xxxx Explanation: An error occurred allocating or opening a Job Tracking Definition

Table. The message text is self describing. System Action: The Job Tracking Definition Table is not loaded. This message is

followed by message 1177E. User Response: Take action according to the following message.

1186E ERROR OCCURRED READING INDEX ENTRY FOR JOB xxxx FOR PRED REQ IN APPL

yyyy.nn Explanation: An error occurred reading a job index data set entry for a job

identified as an external or manual job in an application. The SCOPE parameter had been specified for the job.

System Action: This message would have been preceded by a message indicating the nature of the error. The external or manual job is not marked as complete.

User Response: If the external job is complete, it will have to be manually marked complete in the application.

1187E SADLINK ENTRY xxxx NOT FOUND Explanation: A SADLINK entry specified on a SADLOAD or SADLINK command. However,

no entry with a matching name could be found.

Messages and Codes

ESP-5.4-MC-03 163

System Action: The command is not processed. User Response: Ensure that the name is correctly spelled out. If the name is correct,

the SADLINK DEFINE may not have been executed properly.

1188E YOU ARE NOT AUTHORIZED TO LOAD SADLINK xxxx Explanation: A SADLOAD command was issued by a user who was not authorized to

perform the function. The SADLINK element belonged to a group to which the user did not have update authority.

System Action: The command is suppressed. User Response: The command should be issued by a user who has update authority to the

group owning the SADLINK.

1189E ABOVE ERROR OCCURRED LOADLINK SADLINK xxxx Explanation: An error occurred at initialization time when a sadlink entry was

being built. This message would have been preceded by another message indicating the nature of the error.

System Action: The SADLINK is not loaded. User Response: After the error identified by the previous message has been corrected,

issue the SADLOAD command.

1190E MAXIMUM OF 2 NOTIFY STATEMENTS PER ESP PROCEDURE/JOB DEFINITION EXCEEDED

Explanation: More than 2 notify statements were encountered in an ESP Procedure. The limit is two.

System Action: The extra notify statement is ignored. User Response: Refrain from using more than two notify statements. You can combine

several notify requests onto one statement.

1191E INVALID COMPLETION CONDITION xxxx Explanation: A RELEASE, AFTER, POSTREQ or PREREQ statement contained a job

completion condition other than 'N', 'U', or 'A'. System Action: The procedure is aborted. User Response: Correct the completion condition.

1192I xxxx Explanation: This message is issued on the request of a NOTIFY statement in an ESP

Procedure. The message text indicates that ESP has submitted a job into the system. The message text can include the application name or jobnet ID.



Procedure. The message text indicates that an ESP submitted job has started to execute. The message text can include the application name or jobnet ID.


164 ESP-5.4-MC-03


Procedure. The message text indicates that an ESP submitted job has ended execution. The message text includes the completion code and can also include the application name or jobnet ID.


1195W xxxx Explanation: This message is issued on the request of a NOTIFY statement in an ESP

Procedure. The message text indicates that an ESP submitted job has failed during execution. The message text includes the completion code and can also include the application name or jobnet ID.

System Action: Processing continues. Successor jobs waiting for normal completion will not be released.

User Response: You may need to resubmit the job. If you do not resubmit the job, you may need to mark the job complete, or manually release successor jobs.

1196I JOB TRACKING DEFINITION TABLE ACTIVE, LOADED FROM xxxx(yyyy)

Explanation: In response to a LOADJTDT statement or command, a job tracking definition table was loaded from the specified data set and made active.

System Action: The job tracking definition table will be used to control job tracking.

User Response: None. This message is used for documentation.

1197E POSSIBLE LOOP IN PREDECESSOR/SUCCESSOR RELATIONSHIPS Explanation: During execution or simulation of an Event, a loop was detected in the

predecessor/successor relationships of some of the jobs. System Action: The Event execution or simulation is suspended. User Response: Correct the job linkages.

1198I NJE TIME TOLERANCE FACTOR SET TO nn, nn Explanation: The message is in response to the NJETOL operator command. It displays

the synchronization tolerance for accepting job reader on time from another NJE node. The numbers are in 1/100 of a second. When a tracking record is received from another node, a match is made against reader on time - n1, and reader on time + n2

System Action: None. User Response: None

1199E JOB xxxx ALREADY EXISTS IN APPL yyyy Explanation: An attempt was made to insert a job into an active application.


System Action: The request is denied. User Response: Ensure the job name was correctly specified. If you need another

Messages and Codes

ESP-5.4-MC-03 165

copy of the same job, use a unique qualifier.

1200E MODELING IS ACTIVE - RECURSIVE MODEL CALL NOT ALLOWED Explanation: A MODEL command was issued while model processing is already active.

The model processor may not be called recursively. System Action: The command is ignored. User Response: MODEL commands can be issued if desired or the ENDMODEL command should

be issued to terminate model processing.

1201E ERROR SCANNING MODEL COMMAND, RC=nn Explanation: A problem was encountered while parsing a MODEL command. System Action: The command is ignored. The user is prompted for a new command. User Response: System routine IKJPARS returned error code nn.


1202E INVALID MODEL START TIME SPECIFIED Explanation: A MODEL command had a syntax error in the time specification of the

START keyword. Any valid schedule statement may be specified. If the statement contains separators then it must be enclosed in quotes.

System Action: The command is ignored. User Response: Correct the syntax error and reenter the MODEL command.

1203E ERROR OCCURRED OPENING SCHEDULED ACTIVITY DATA SET xxxx

Explanation: An error occurred when attempting to open the scheduled activity data set for input. The previous messages will describe the error condition.

System Action: MODEL processing is terminated. User Response: Ensure the data set is in the correct format and that no I/O errors

exist. After the problem is diagnosed and corrected, reissue the MODEL command.

1204I NO RECORDS FOUND FOR xxxx REPORTING PERIOD Explanation: This message is issued at model end time to inform the user that no

records were found in the requested reporting period for the specified report name. Ensure the reporting period on your MREPORT was correctly specified.


166 ESP-5.4-MC-03

1205W MODELING NOT ACTIVE Explanation: An attempt was made to enter a MODELING command when the MODEL

processor not active. System Action: The command is ignored. User Response: Issue the MODEL subcommand of ESP to begin a model definition. You

may enter any model command after the MODEL--> prompt. Use the ENDMODEL subcommand when you wish to terminate model definition mode.

1206E ZERO MAXIMUM INITIATORS NOT ALLOWED Explanation: A MAXINITS command was entered but the maximum number of initiators

specified was 0. System Action: The command is ignored. User Response: Specify a maximum number of initiators available on all CPUs in the

range 1-999.

1207E DEFAULT PRIORITY NUMBER OUT OF RANGE Explanation: The default job priority specified was not in the range 1-15. System Action: The command is ignored. User Response: Specify a default job priority in the range 1-15 to be assigned to all

jobs without a priority in their JCL.

1208E NO INITIATOR ACTION SPECIFIED Explanation: An INIT command was entered but no action was specified. System Action: The command is ignored. User Response: Reenter the INIT command and specify the action you want performed on

the initiator (i.e. START, SET, STOP).

1209E NO INITIATOR CLASS(ES) SPECIFIED Explanation: An INIT command was entered but no initiator class(es) were specified. System Action: The command is ignored. User Response: Reenter the INIT command and use the CLASS keyword to assign one or

more execution classes to this initiator (or group of initiators).

1210E INVALID TIME SPECIFIED Explanation: A TIME command specified invalid schedule criteria. System Action: The command is ignored. User Response: Review the schedule criteria and correct any errors. If the schedule

statement contains separators, then it must be enclosed in quotes.

1211E CONFLICTING KEYWORDS - CPU NUMBER SPECIFIED FOR GLOBAL RESOURCE

Explanation: A RESOURCE command was entered which specified a CPU number for a global resource. When a resource is defined as global, it is available across all CPUs.

System Action: The command is ignored. User Response: Reenter the RESOURCE command without the CPU keyword if you are

Messages and Codes

ESP-5.4-MC-03 167

defining a global resource.

1212E RESOURCE CONFLICT - SCOPE MUST BE SAME AS PREVIOUSLY DEFINED

Explanation: A RESOURCE command was entered to alter or set a previously defined resource but the wrong resource scope was specified. If the resource was previously defined as local, you must identify it as local on any subsequent RESOURCE commands; the same applies to global resources. If you wish to change the resource from a local to a global one (and vice versa), you must delete and redefine the resource.

System Action: The command is ignored. User Response: Reenter the RESOURCE command and specify the correct scope.

1213E CPU NUMBER REQUIRED FOR LOCAL RESOURCE Explanation: A RESOURCE command was entered to add or alter a local resource but no

CPU keyword was specified. If you are defining a new local resource, you must specify the CPU number to which the resource will be added to. If you are altering (or setting) an existing local resource, you must indicate on which CPU the resource was originally defined.

System Action: The command is ignored. User Response: Reenter the RESOURCE command and specify which CPU the resource exists

on or is being defined to.

1214E ZERO MANUAL TASK SERVERS NOT ALLOWED Explanation: A MAXINITS command was entered and the SERVERS keyword requested no

manual task server initiators. A minimum of 1 server initiator is required internally for model processing. If not specified, the default is 20.

System Action: The command is ignored. User Response: Reenter the MAXINITS command and specify one or more server

initiators.

1215E ERROR ALLOCATING PRINT FILE FOR xxxx Explanation: An MREPORT command specified a logical report name that was not

previously defined or was closed by an ENDPRINT command. The previous message(s) describe the error condition.

System Action: The command is ignored. User Response: Issue a DEFPRINT command to define the logical report name to which

output will be diverted. Ensure no ENDPRINT command was issued before the MREPORT command.

1216E INVALID FROM PERIOD Explanation: The FROM keyword of the MREPORT command contained an invalid time

statement. Any valid schedule statement may be used but if it contains separators, the whole statement must be enclosed in quotes.

System Action: The command is ignored. User Response: Reenter the MREPORT command with the correct report time criteria. if

you have difficulty in resolving the error with your schedule statement, contact you support personnel for assistance or remove the

168 ESP-5.4-MC-03

FROM keyword from your MREPORT command (allow default).

1217I nn JOBS READ FROM SCHEDULED ACTIVITY DATASET Explanation: This is the total number of jobs in the scheduled activity file with

submit times in the range specified by the START keyword of the MODEL command. Only these jobs will be used to generate the model.


1218E ERROR READING SCHEDULED ACTIVITY FILE Explanation: An error occurred while reading a record from the scheduled activity

file. The previous message will describe the error. System Action: Model processing is terminated. User Response: Retry model processing after the problem is diagnosed and corrected.

1219I NO REPORTS REQUESTED - MODEL PROCESSING TERMINATED Explanation: The ENDMODEL command detected that no modeling reports were requested. System Action: Model processing is terminated. User Response: Modeling reports can be obtained by entering an MREPORT command. I

you wish to obtain reports, restart the modeling process and request the reports you would like via the MREPORT command.

1220W INITIATOR nn NOT DEFINED Explanation: An INIT command requested processing of an initiator number which was

not initially defined to the model processor. An initiator must fall within the range specified by the MAXINITS command.

System Action: Processing continues. User Response: Examine the MAXINITS command to see if the initiator you are trying to

process falls within the specified range. The highest initiator number you may specify is the number defined by MAXINITS.

1221W INITIATOR nn ALREADY ACTIVE Explanation: An INIT START command was issued for an initiator that was already

active. Check the previous model statements to determine where the initiator was started.

System Action: Processing continues. User Response: None. There is no need to start an active initiator.

1222W INITIATOR nn IN DRAINED STATUS Explanation: An INIT SET command was issued against a drained initiator. Only

started initiators may be altered by an INIT SET command. System Action: Processing continues. User Response: Issue an INIT START command to activate the initiator with the desired

options.

1223E RESOURCE xxxx NOT DEFINED Explanation: A RESOURCE command was issued to alter, delete or model a resource

which was not previously defined to the model processor.

Messages and Codes

ESP-5.4-MC-03 169

System Action: The command is ignored. User Response: Correct the RESOURCE name or define the resource to the model

processor using a RESOURCE ADD command.

1224E MAXIMUM NUMBER OF RESOURCES EXCEEDED Explanation: A RESOURCE command attempted to add to or set the count of a resource

to more than 1000 megs. System Action: The command is ignored. User Response: Reenter the command and ensure the maximum allowable number of

resources is not exceeded.

1225E NO EXECUTION CLASS FOUND FOR JOB xxxx Explanation: This is an internal error condition occurring at job end. It may

affect model processing and should be reported. System Action: Processing continues. User Response: Report the message to your support personnel.

1226E PROCESSING TERMINATED FOR MODEL REPORT xxxx Explanation: An error was detected while processing the specified logical report

name or insufficient data was available to print the report. The previous message(s) will describe the reason or error condition.

System Action: The current report is terminated but processing continues. User Response: Restart the modelling process after the problem is diagnosed and

corrected.

1227E NO RESOURCES FOUND FOR REPORT xxxx Explanation: A resource utilization by system report (RR1) was requested but no

resources were defined to the model processor to report on. System Action: The current report is terminated but processing continues. User Response: Define some resources to the model processor via the RESOURCE command

or do not request this report.

1228E INSUFFICIENT DATA WIDTH ON REPORT xxxx Explanation: The data width for the specified logical report name is insufficient.

Each model report has a minimum data width it requires to print the report data.

System Action: The current report is terminated but processing continues. User Response: Review the modelling documentation to determine the minimum required

data width for this report.

1229E INVALID ADJUSTMENT PERCENTAGE FACTOR Explanation: An ADJUST command specified an adjustment percentage factor of less

than -99%. This would result in a zero or negative execution or CPU time.

System Action: The command is ignored. User Response: Reenter the command specifying an execution or CPU adjustment

percentage factor of greater than -100%.

170 ESP-5.4-MC-03

1230E ERROR ALLOCATING REPORT FORMAT WORKFILE DURING REPORT xxxx

PROCESSING Explanation: An error was encountered when attempting to dynamically allocate a

workfile on SYSDA to process the specified logical report name. The preceding message(s) will describe the error.

System Action: Processing is terminated for this report. User Response: Restart the report after diagnosing and correcting the error. If the

problem persists, contact your support personnel.

1231E ERROR OPENING REPORT FORMAT WORKFILE DURING REPORT xxxx PROCESSING

Explanation: An error was encountered opening the temporary work file used in the report formatting routine to process the specified logical report name. The preceding message(s) will describe the error.



1232E ERROR WRITING TO REPORT FORMAT WORKFILE DURING REPORT xxxx

PROCESSING Explanation: An error occurred when writing a record to the temporary work file

used in the report formatting routine to process the specified logical report name. The preceding message(s) will describe the error.



1233E BUFFER LENGTH ERROR DURING REPORT xxxx PROCESSING Explanation: This is an internal error condition which occurred while processing

the specified logical report name. System Action: Processing is terminated for this report. User Response: Contact your support personnel to report the problem.

1234E ERROR READING REPORT FORMAT WORKFILE DURING REPORT xxxx PROCESSING

Explanation: An error was encountered while reading a record from the temporary work file used in the report formatting routine to process the specified logical report name. The preceding message(s) will describe the error.



Messages and Codes

ESP-5.4-MC-03 171

1235E CPU NUMBER OUT OF RANGE Explanation: The INIT statement specified a CPU number of 8 or 9. The maximum CPU

number allowed is 7. System Action: The INIT statement is ignored. User Response: Correct the INIT statement and re-issue the request.

1236E Mailbox <box name> is not defined Explanation: A message was addressed to a mailbox that is not defined in

notification list. System Action: The message is discarded. User Response: Either add the mailbox definition to the notification list or

change the message source (event definition or a NOTIFY statement) to point to an existing mailbox.

1237E Error opening a SYSOUT file for batch SMTP Explanation: The preceding message describes the error. System Action: Sending of the email message is aborted. User Response:

1238I Notification list loaded/tested, (no) errors found Explanation: This is a response to a LOADNL command used to load or test

a notification list. System Action: User Response:

1239I Notification list active, loaded from <data set name> Explanation: A new notification list has been loaded from the indicated source as

a result of a LOADNL command. System Action: User Response:

1240I MODEL PROCESSING COMPLETE Explanation: This is an informational message issued when all MODEL processing has

been completed. Any requested reports will be printed if data was available.

System Action: MODEL generation mode is terminated. Processing continues. User Response: None.

1241E ERROR OPENING SCHEDULED ACTIVITY DATASET FOR UPDATE Explanation: An error occurred when attempting to open the scheduled activity

data set for update. The previous messages will describe the error condition.

System Action: MODEL processing is terminated. User Response: Ensure the data set is in the correct format and that no I/O errors

exist. After the problem is diagnosed and corrected, retry MODEL processing.

172 ESP-5.4-MC-03

1242I MODEL PROCESSING BEGINS AT xxxx ON yyyy Explanation: This is an informational message issued at MODEL start time. Any jobs

in the scheduled activity data set with a start time prior to this WILL NOT be included in the MODEL processing.

System Action: MODEL generation begins. Processing continues. User Response: None.

1243E Missing Agent Definition Table Data Set Name Explanation: A LOADAGDF command was issued, but it did not contain the name of

the data set to be loaded. The name of a previously loaded data set was not available to use as a default.

System Action: The LOADAGDF command is not executed. User Response: Reissue the command, specifying a data set name and optionally a

member name.

1244E Unable to locate Job xxxx for update in Appl yyyy.nnn Explanation: As a result of a minimum or maximum run time being specified

for an application object, the application's ATR needs to be updated. The job's definition could not be located in the ATR in order to perform the update.

System Action: The attempted update is abandoned. User Response: Contact Cybermation Product Support Services.

1245E Missing data set name for notification list Explanation: A LOADNL command was entered without a data set name, and no

prior name is known to ESP/WM. System Action: The command is not executed. User Response: Reenter the command with data set name on it.

1246E Above error occurred opening notification list Explanation: The data set name specified on a LOADNL command could not be opened.

The preceding message describes the error. System Action: The command is aborted. User Response:

1247E Above error occurred reading notification list Explanation: The preceding message describes the error that was encountered

while reading the file specified on a LOADNL command. System Action: The notification list remains unchanged. User Response:

1248E Invalid command syntax detected in line <number> of notification list Explanation: An erroneous statement was found in notification list. System Action: The notification list remains unchanged. User Response:

Messages and Codes

ESP-5.4-MC-03 173

1249E Command <cmdname> invalid in notification list Explanation: The indicated statement is not allowed in notification list. System Action: The notification list remains unchanged. User Response:

1250E UNABLE TO TRANSMIT JOB TRACKING DATA TO xxxx, DESTINATION NOT DEFINED

Explanation: ESP was attempting to transmit tracking data to a destination defined by an XMITMDL statement. The destination was not defined via a TPAPPL statement.

System Action: The tracking data are not transmitted. User Response: Correct the XMITMDL statement, or add a TPAPPL definition.

1251I ESP CHKPT THRESHOLD EXCEEDED, WAITING FOR CHKPT SPACE FOR INTER SYSTEM DATA

Explanation: ESP is waiting for space to become available on the checkpoint file. System Action: User Response:

1253E You are not permitted to issue verb xxxx to Agent yyyy Explanation: You have attempted to issue a message to an ESP Agent on an outboard

machine. You are not authorized for the required verb specified in the message to the agent identified in the message.

System Action: The request is not processed. User Response: If you have not made an error, and need to issue the request, obtain

appropriate authorization. You will need READ access to the resource AGENTMSG.vvvv.aaaa where vvvv is the verb and aaaa is the name of the Agent.

1254W Cache could not be activated for dddd. Macro mmm RC=rrr Reason=sss Explanation: Cache initialization failed for access to data set dddd. Error occurred

when executing system macro mmm, which produced return code rrr and reason code sss.

System Action: Cache will not be used for the specified data set. User Response: Check if your installation's policies allow for creation of data spaces

of the size specified on CACHE parameter for the file in question and see MVS documentation for explanation of the return and reason codes.

1255W {APPLFILE | TRAKFILE} cache size of nnn specified. mmm will be used. Explanation: The CACHE operand on APPLFILE or TRAKFILE statement was specified

with a value of nnn which is invalid. ESP substituted the value of mmm.

System Action: A cache will be created with size of mmm megabytes. User Response: To avoid this message, specify a cache size within 0-2000 range.

174 ESP-5.4-MC-03

1256E Slot number nnnn invalid (XX op) Explanation: An invalid slot number was found while processing a slot file I/O

request. The slot number exceeded the maximum slot number for the data set.

System Action: The operation is not performed. This message is returned to the caller as an I/O error.

User Response: This error can occur if a JobIndex file is not synchronized with the appl file or the job tracking file. It can also occur following an EXTEND of either file if a LISTJOB or LISTAPPL command is issued for an object which is complete and which was not copied to the new file. In any other situation, please contact Cybermation for further assistance, reporting the value of XX.

1258W NetNode xxxx already defined for tracking model yyyy, ignored Explanation: An "XMITMDL ADD MODEL(xxxx)" command specified "NETNODE(yyyy)".

Network node yyyy was already defined for inter-nodal job tracking model xxxx.

System Action: The previously defined network node specification is ignored. Otherwise the "XMITMDL ADD" command is processed normally.

User Response: An "XMITMDL LIST" command can be issued to determine if all inter-nodal tracking models have been correctly defined. If not, "XMITMDL DELETE" and "XMITMDL ADD" commands can be issued to correct them.

1259E MODEL, NODE and/or NETNODE invalid with XMITMDL LIST Explanation: An "XMITMDL LIST" command was specified with at least one MODEL, NODE

and/or NETNODE keyword operand. The MODEL, NODE and NETNODE operands are mutually exclusive with the LIST operand. Note that if neither ADD, DELETE, nor LIST was specified on the XMITMDL command, it defaults to LIST.

System Action: The XMITMDL command is ignored. User Response: If the intention was to issue an "XMITMDL ADD" command or an

"XMITMDL DELETE" command, then re-issue it with the correct specifications. If the intention was to issue an "XMITMDL LIST" command, then re-issue it without any MODEL, NODE and/or NETNODE keyword operands.

1260E VSMLOC error, RC=xx, CSA, Address=yyyy, Length=zzzz Explanation: The ESP explicit data set trigger notification utility program,

CYBESDT1, attempted unsuccessfully to verify the validity of the specified ESP subsystem's communication area in CSA. xx specifies the address verification service (VSMLOC) return code. yyyy specifies the address of the ESP CSA communication area. zzzz specifies the hexadecimal length the ESP CSA communication area.

System Action: Program CYBESDT1 terminates with an error return code. User Response: Should never happen. Call Cybermation support.

Messages and Codes

ESP-5.4-MC-03 175

1261E GDG invalid, Dsname=xxxx Explanation: The ESP explicit data set trigger notification utility program,

CYBESDT1, was executed specifying data set name xxxx, where xxxx is the name of a Generation Data Group (GDG).

System Action: Program CYBESDT1 terminates with an error return code. User Response: Re-execute program CYBESDT1 specifying DSNAME(yyyy) or DATASET(yyyy),

where yyyy is the name of a data set that is not a GDG.

1262E CYB1262E Data set xxxx not found in catalog Explanation: The ESP explicit data set trigger notification utility program,

CYBESDT1, was executed specifying data set name xxxx. A catalog search to locate the volume of data set xxxx failed.

System Action: Program CYBESDT1 terminates with an error return code. User Response: If data set xxxx exists but is not cataloged, re-execute program

CYBESDT1 specifying the VOLSER(yyyy) or VOLUME(yyyy) input parameter, where yyyy specifies the serial number of the volume that data set xxxx resides on. If data set xxxx does not exist, re-execute program CYBESDT1 specifying DSNAME(zzzz) or DATASET(zzzz), where zzzz is the name of a data set that does exist.

1263E OBTAIN error, {rrrr|RC=cc, Dsname=dddd, Volser=vvvv} Explanation: The ESP explicit data set trigger notification utility program,

CYBESDT1, received an error issuing a format 1 DSCB OBTAIN to determine if data set dddd resides on volume vvvv. rrrr specifies the reason for the OBTAIN error, and can be one of the following - {Cataloged d|D}ata set dddd volume vvvv not mounted {Cataloged d|D}ata set dddd not on volume vvvv I/O error or invalid format 1 DSCB, Dsname=dddd, Volser=vvvv Invalid work area pointer, Dsname=dddd, Volser=vvvv cc specifies the OBTAIN error return code if the error reason is unknown. dddd specifies the input data set name. vvvv specifies the input volume serial number.

System Action: Program CYBESDT1 terminates with an error return code. User Response: Attempt to determine the cause of the problem according to the error

message text, and re-execute program CYBESDT1 with the correct data set and (optionally) volume specifications.

1264E RACROUTE REQUEST=AUTH error, RC=8{, Return=X'yy'}{, reason=X'zz'}, {Dsname|Alias}=dddd

Explanation: The ESP explicit data set trigger notification utility program, CYBESDT1, issued a SAF (RACROUTE) authorization request to determine if the owning user has update access to data set dddd specified in the start up parameter. The authorization request failed with a SAF return

176 ESP-5.4-MC-03

code of xx. yy specifies the RACF or installation return code. zz specifies the RACF or installation reason code. The SAF check protects against attempts to set an ESP explicit data set trigger by a user who does not have update access to the data set.

System Action: Program CYBESDT1 terminates with an error return code. User Response: If the user should be permitted update access to data set dddd, then

add the permission to the security subsystem. Then re-execute program CYBESDT1 to set an ESP explicit trigger for data set dddd.

1265E SMFTWTM error, RC=xx Explanation: The ESP explicit data set trigger notification utility program,

CYBESDT1, attempted unsuccessfully to write a user SMF type 132 subtype 1 ESP explicit data set trigger record. xxxx specifies the reason for the SMFWTM (SMF write) error, and can be one of the following - SMF type 132-1 record length less than 18 bytes SMF not active or ended abnormally SMF type 132-1 record suppressed by IEFU83, IEFU84 or IEFU85 exit SMF type 132-1 record not being recorded SMF could not establish recovery Caller not in primary ASC mode or incorrect ASID encountered yy specifies the SMFWTM error return code if the error reason is unknown.

System Action: Program CYBESDT1 terminates with an error return code. User Response: Attempt to determine the cause of the SMFWTM failure and correct it.

1266I Explicit data set trigger for xxxx sent to yyyy Explanation: The ESP explicit data set trigger notification utility program,

CYBESDT1, sent an explicit data set notification for data set xxxx to ESP subsystem yyyy.

System Action: If a matching explicit data set trigger definition exists for data set xxxx, then ESP subsystem yyyy performs the action specified by the explicit data set trigger, else no action is taken.


1267E Subsystem xxxx not {found|{an|a tracking} ESP} Explanation: The ESP explicit data set trigger notification utility program,

CYBESDT1, verifying the specified subsystem xxxx, determined that it either does not exist, is not an ESP, or is not a tracking ESP. A tracking ESP is one whose ESPPARM initialization file does not contain the following statement - SMFINT OFF Note that if subsystem xxxx is not found but is a valid tracking ESP, then xxxx has not executed at least once since the system was IPL'd.

Messages and Codes

ESP-5.4-MC-03 177

System Action: Program CYBESDT1 terminates with an error return code. User Response: If the specified subsystem was not found, but is a valid tracking ESP,

then start the ESP before re-executing program CYBESDT1. Otherwise re-execute program CYBESDT1 specifying a tracking ESP in the SUBSYSTEM or SSID start-up parameter.

1268E CSI error, xxxx Explanation: The ESP explicit data set trigger notification utility program,

CYBESDT1, received an error while searching the catalog to determine the serial number of the volume that the specified data set resides on. xxxx specifies the reason for the CSI (Catalog Interface Search) error.

System Action: Program CYBESDT1 terminates with an error return code. User Response: Attempt to determine the cause of the problem according to the error

message text, and re-execute program CYBESDT1 with the correct data set specification.

1269W APPLICATION STATEMENT MISSING Explanation: A SUBAPPL statement was found in an ESP procedure, however, no

preceeding APPL statement exists. System Action: Processing continues

The SUBAPPL statement without the APPL statement is ignored. The jobs that are not part of an application do not appear on the scoreboard.

User Response: Either insert an APPL statement, or remove the SUBAPPL statement from the ESP procedure.

1270E THE SCOREBOARD IS NOT ACTIVE Explanation: A scoreboard related request was made to the ESP subsystem. However,

the scoreboard was not active. System Action: The request is not processed. User Response: Activate the scoreboard.

1271E ABOVE ERROR OCCURRED LOADING SCOREBOARD FROM SCHEDULE FILE

Explanation: An I/O error occurred while the scoreboard was being loaded from the schedule file. The nature of the I/O error is described in the preceding message.

System Action: The scoreboard load will terminate. User Response: This depends on the I/O error encountered. When the data set is

restored, you can shutdown ESP and restart it to reload the scoreboard.

1272I nn ENTRIES ADDED TO SCOREBOARD Explanation: This message is issued when a LOADSCHF command has completed loading

the schedfile/scoreboard from a scheduled activity data set. System Action: Processing continues.

178 ESP-5.4-MC-03


1273C Control Block Addresses: Explanation: In response to a DCBADDR command, the addresses of various ESP control

blocks were listed. System Action: None. User Response: None.

1274C DSTRIG exclude list: Explanation: In response to a LDTREL command, the Data Set Trigger Exclude List

entries have been listed. The entries follow this message. System Action: None. User Response: None.

1275W The TRACK_MANUAL option has been withdrawn Explanation: The TRACK_MANUAL or NOTRACK_MANUAL keyword was specified as an

option within an ESP Procedure. This option has been withdrawn starting with release 4.3.0.

System Action: The keyword is ignored. User Response: You should remove the keyword from the OPTIONS statement in the

procedure. Jobs that are manually submitted should be identified with the MANUAL keyword.

1276I Subappl xxxx now complete in Appl yyyy.nn Explanation: A Subappl of an ESP Application has been completed, and the

NOTIFY_SUBAPPL_COMPLETE option has been requested in the application definition.

System Action: None. This is an informational message requested by the user. User Response: None.

1277W DFPNODE NOT AVAILABLE WHEN SAF SECURITY ACTIVE Explanation: A DFPNODE command was issued, to set or display the default PNODE for

a console or user. The default PNODE is used by the POST command. When SAF security is active, this function is not available, as the console or user does not have an ESP USERDEF entry.

System Action: The command is ignored. User Response: You will have to explicitly specify the PNODE name on a POST command.

1278W PNODE NAME MISSING Explanation: A post command was issued without a PNODE name. When SAF security is

active, a default PNODE name cannot be defined, and therefore it is needed on each POST command.

System Action: The command is ignored. User Response: Specify the name of the PNODE from which you want to post the job.

1279W JOB xxxx IN APPL zzzz LATE START TIME EXCEEDED Explanation: A job has missed its late start time. The late start time was defined

Messages and Codes

ESP-5.4-MC-03 179

by the user defining the job to the system. System Action: The job is considered overdue. User Response: You should investigate why JES has not started the job yet.

1280I No DSTRIG exclude entries are defined Explanation: A LDTREL command was entered to list the Data Set Trigger Exclude List

entries. It was determined no such entries exist. System Action: None. User Response: None.

1281I DSTRIG exclude entry xxxx {not} deleted Explanation: A request was made to delete an entry from the Data Set Trigger

Exclude List. The result of the request is indicated in the message.

System Action: The Data Set Trigger Exclude List entry is processed as indicated in the message text.


1291E Above error occurred on line <number> of notification list Explanation: This message describes the location of an error in the notification

list being read by a LOADNL command. System Action: The notification list remains unchanged. User Response:

1292E Wildcards are not allowed in mailbox name Explanation: A mailbox name in a notification list contains wildcard characters. System Action: The notification list remains unchanged. User Response:

1293E Mailbox <name> already exists Explanation: A duplicate mailbox name was found in a notification list. System Action: The notification list remains unchanged. User Response:

1294E Subscription out of order: no mailbox defined Explanation: A statement defining a mailbox subscriber was found before the first

mailbox definition. Subscribers must follow the definition of the mailbox to which they subscribe.

System Action: The notification list remains unchanged. User Response:

1295I No matching mailboxes found Explanation: A MAILBOX command found no mailboxes matching the name provided in

the command. System Action: User Response:

180 ESP-5.4-MC-03

1296C Mailbox display Explanation: This is a heading of a multiline console message issued in response

to MAILBOX operator command. System Action: User Response:

1300I CYBERMATION INFOSERV RELEASE xxxxx INITIALIZATION COMPLETE

Explanation: Infoserv has completed its initialization. System Action: Processing continues. User Response: None.

1301I CYBERMATION INFOSERV SHUTDOWN IN PROGRESS Explanation: A SHUTDOWN or STOP command was issued to Infoserv or the required

TPSERVER resources were not available. System Action: Infoserv continues with the shutdown. User Response: None.

1302I SHUTDOWN COMMAND ACCEPTED Explanation: This response is given to the SHUTDOWN command. System Action: Infoserv begins shutdown procedure. User Response: None.

1303S INFOSERV IS ALREADY ACTIVE FOR SYSTEM ID xxxx Explanation: Infoserv was started while another copy of the program was executing

with the same system ID. This is probably due to an error, when more then one Infoserv task is started on the same system.

System Action: Processing terminates. User Response: Correct the request if it was meant for another SYSID.

1304E ERROR occurred DURING COMMAND PARAMETER SCAN Explanation: An error occurred during the parameter scan of a statement from the

IFSPARM file. This is probably due to an internal logic error. System Action: Processing terminates. User Response: Correct the logic and/or statement.

1305A ENTER INITIALIZATION PARAMETER OR 'END' Explanation: In response to the PROMPT keyword on the start command Infoserv is

prompting the operator to enter an initialization parameter from the console.

System Action: Infoserv waits for response, then processes the parameter. User Response: Enter an initialization parameter. Anything valid in the IFSPARM

data set can be specified here. When all parameters are defined type END to terminate the prompt and to continue with normal processing.

1306A REENTER ENTIRE STATEMENT, 'CANCEL' OR 'END' Explanation: This message follows an error on a start command or parameter

Messages and Codes

ESP-5.4-MC-03 181

statement. It is preceded by a message indicating the cause of the error.

System Action: Infoserv waits for response. If CANCEL is specified, Infoserv terminate. If END is specified, Infoserv ignores the parameter statements or start command.

User Response: reenter the correct parameters. If you are not sure what they are supposed to be, reply CANCEL and Infoserv will terminate. Infoserv can then be restarted when the correct parameters are known.

1307E ERROR OPENING INFOSERV PRINT DATASET Explanation: An error occurred when attempting to open the data set specified by the

IFSPRINT DD name. The previous message(s) will describe the error condition.

System Action: Infoserv initialization terminates. User Response: Ensure the data set is defined and that no I/O errors exist. After the

problem is diagnosed and corrected restart Infoserv.

1308E xxxxxxxx Explanation: An I/O error was encountered reading the IFSPARM file. This could

include a "file not allocated" condition or an actual I/O error. The text of the message fully describes the error.

System Action: Processing is terminated. User Response: Correct the problem indicated by xxxxxxx and restart Infoserv.

1309W PARAMETER ERROR ON EXEC CARD Explanation: There is a syntax error on the EXEC card parameter of the Infoserv

procedure. System Action: System prompts operator to correct the parameter statement. User Response: Reply to the prompt with correct parameter.

1310E ERROR SCANNING COMMAND, RC=nn Explanation: An error occurred while parsing an INFOSERV command. This may be an

internal logic error. System routine IKJPARS returned an error code nn.

System Action: The command is ignored. User Response: The following RC may appear in this message:


1311S ERROR ATTACHING xxx RC=nn Explanation: An error occurred while attempting to attach a module for the xxxx

function. This is an internal logic error.

182 ESP-5.4-MC-03

System Action: Infoserv is terminated. User Response: Contact your support personnel.

1312E ERROR CODE nn, REASON CODE mm LOADING INFO/SYSTEM SERVER ROUTINE BLGYSRVR

Explanation: An error occurred during execution of a LOAD macro used to bring the Information/System server module (BLGYSRVR) into the Infoserv address space. This module allows communication between Infoserv and Info/System and must be available in the system libraries, of via a STEPLIB or JOBLIB DD cards. This type of error is usually due to a "module not found" condition or an error with the data set directory. The "MVS System Codes" manual will provide additional details on the error and reason code.

System Action: Infoserv will be shutdown. User Response: Correct the error and restart Infoserv. If problem persist contact

your support personnel.

1313W UNABLE TO PROCESS INFOSERV REQUEST xxxx Explanation: Infoserv is unable to process an incoming request. This could occur

because the receiving client is in a suspended state. An explanation will be provided by additional message(s).

System Action: The request is not processed. User Response: Take the appropriate corrective actions if required or ignore the

message if no problem exist.

1314I CLIENT xxxx SUSPENDED Explanation: The Infoserv client xxxx is currently in a suspended state and is

unable to process any requests. The user may have requested that the client be suspended or Infoserv may have suspended the client as a result error threshold being reached.

System Action: Processing continues. Requests for this client will not be processed. User Response: The client can be restarted (if desired) using the CLIENT command with

the RESTART keyword.

1315E PROBLEM CREATE/UPDATE NOT REQUESTED Explanation: A request was received for Infoserv but the sender did not specify

whether an Info/Management record should be created or updated. System Action: The request is ignored. Processing continues. User Response: Ensure the PROBLEM_CREATE or PROBLEM_UPDATE keyword is specified on

the INFOSERV command. If this does not correct the problem, restart Infoserv with the trace option and contact Cybermation support after the message is issued again.

1316W CLIENT xxxx NOT DEFINED TO INFOSERV Explanation: Infoserv received a request from an unknown client xxxx. All clients

must be predefined before Infoserv can accept any requests. System Action: The request is ignored. Processing continues. User Response: Use the CLIDEF command to define the client to Infoserv or specify it

in IFSPARM initialization parm data set.

Messages and Codes

ESP-5.4-MC-03 183

1317E INFOSERV REQUEST xxxxx FROM CLIENT yyyyyy TERMINATED. Explanation: Infoserv encountered an error while processing a request. The previous

message will explain the error. System Action: The request is rejected. Processing continues. User Response: Correct the problem indicated by previous Infoserv messages or suspend

the client until problem can be corrected.

1318E ALL REQUIRED FIELDS NOT SPECIFIED - PLEASE RE-ENTER COMMAND

Explanation: An Infoserv command was entered but not all the required keywords were specified.

System Action: The command is ignored. Processing continues. User Response: Check the command syntax in the Infoserv Command Reference and reenter

the command.

1319E CLIENT xxxx ALREADY DEFINED. Explanation: An attempt was made to define a client xxxx to Infoserv which already

exists. System Action: The command is ignored processing continues. User Response: Use the CLIENT command to display all clients currently defined to

Infoserv.

1320E ERROR CODE nn LINKING TO yyyyy Explanation: An error occurred while linking to the Info/System server module

(BLGYSRVR). This module allows communications between Infoserv and Info/System and must be available in the system libraries, or via STEPLIB or JOBLIB. This type of error is usually due to a module not found condition or an error with the data set directory. The "MVS System Codes" manual will provide additional details on the abend code nn.

System Action: The current Infoserv transaction is terminated. User Response: Shutdown Infoserv, correct the error indicated by the abend code and

restart. If problem persist, contact your support personnel.

1321I INFORMATION/MANAGEMENT RECORD xxxxx CREATED Explanation: Infoserv has successfully created the specified record number in

Information/management database. System Action: Processing continues. User Response: None.

1322E INFO/SYSTEM ERROR PROCESSING REQUEST xxxx FROM CLIENT yyyyy

Explanation: Infoserv detected an Info/System error while processing a request. The request number xxxx is the transaction number from the TP Server used by Infoserv to identify the request. The client yyyyy is the client name used by the transaction server to process the request. Additional details on the error can be found in the Infoserv log data set.

184 ESP-5.4-MC-03

System Action: Processing continues if the error is not serious. If the error will cause further problems, the transaction is terminated and message 1317E will follow.

User Response: Issue a DUMPLOG command to print the Infoserv log. Browse the log around the time the error occurred and find the error messages related to the transaction number xxxx. Info/System API return and reason codes can be found in IBM's "Information/Family Application Programming Interface" manual. If the error will affect other requests to the same client, you may wish to suspend the client until the problem is corrected using CLIENT yyyyy SUSPEND command.

1323I INFO/SYSTEM API RETURN CODE nn - REASON CODE X'mmmm' Explanation: Infoserv detected an Info/System error while processing a request. System Action: The request may be terminated depending on the severity of the error.

For a warning reason code (X'0004') processing will continue. Reason cod greater than 4 will cause the request to be terminated.

User Response: Issue the DUMPLOG command to view the most current entries in the Infoserv log data set. Depending on the type of error, additional diagnostic information may be available in the log. Info/System API return and reason codes can be found in IBM's Information/Family Application Programming Interface" manual.

1324W ERROR THRESHOLD OF nn HAS BEEN REACHED FOR CLIENT xxxx Explanation: System Action: User Response:

1325W CLIENT xxxx SUSPENDED Explanation: The specified client was suspended by Infoserv because of the

previously described condition. System Action: Processing continues but future requests to this client will be

rejected until it is restarted. User Response: The Infoserv log data set will provide additional details.

1326E TP SERVER TRANSACTION RECEIVE FAILED Explanation: Infoserv encountered problems while attempting to receive a

transaction from the TP Server. System Action: An error message from TP Server will follow. User Response: None.

1327E TP SERVER FEEDBACK ERROR CODE xxxx Explanation: An error was encountered with the TP Server. System Action: Depending on error code other supporting messages will be present. User Response: Refer to the TP Server documentation.

1328I Unable to save transaction for retry due to above error Explanation: Infoserv detected an error in Info/System, retried the transaction 3

times but unsuccessfully. Then Infoserv tried to save the transaction to complete it after restart, however Infoserv could not save it.

Messages and Codes

ESP-5.4-MC-03 185

System Action: The error will cause the Infoserv to abend with U1310. User Response: Additional information on the nature of the error could be found in

error messages issued prior to that.

1329I Unable to save restore transaction for retry due to above error Explanation: Infoserv tried to open file which contains the saved transaction with

no success. System Action: The saved transaction will not be processed. User Response: Ensure that file IFSSAVE1 is correctly defined to Infoserv.

1330I Reprocessing transaction from recovery file Explanation: The saved transaction was successfully recovered from IFSSAVE1 file. System Action: Infoserv will try to process the transaction. User Response: None.

1331E INFOCOMM FUNCTION AMBIGUOUS - RE-ENTER Explanation: The specified INFOCOMM function is ambiguous and can not be

interpreted. System Action: The command is ignored. Processing continues. User Response: Reissue the INFOCOMM command and specify the full function name.

1332E NO FUNCTION SPECIFIED ON INFOCOMM COMMAND Explanation: The INFOCOMM command requires a function such as DEFINE, DISPLAY or

DELETE and none was specified. System Action: The command is ignored. Processing continues. User Response: Re-issue the INFOCOMM command and specify the desired function.

1333I SERVER xxxx DEFINED TO yyyyy Explanation: In response to INFOCOMM DEFINE command the specified transaction

server xxxx has been defined to your application yyyyy. Infoserv requests may now be routed to this server via the Infoserv command.


1334E ALL REQUIRED DATA NOT SUPPLIED ON INFOCOMM COMMANDExplanation: You have not supplied all the required parameters on the INFOCOMM

command. If DEFINE was requested then a server ID, a client name and a TP application name are required.

System Action: The command is ignored. Processing continues. User Response: Refer to the Command Reference. Correct the command and reissue it.

1335E SERVER xxx ALREADY DEFINED Explanation: In response to INFOCOMM DEFINE command an attempt was made to define

the specified server xxx but it already exists. System Action: Command ignored. Processing continues. User Response: Use the INFOCOMM DISPLAY command to list all servers currently defined

to your application.

186 ESP-5.4-MC-03

1336E SERVER xxxx NOT DEFINED TO INFOSERV Explanation: In response to INFOCOMM command, an attempt was made to display or

delete the specified server xxxx but it does not exist. System Action: Command ignored. Processing continues. User Response: Use the INFOCOMM DISPLAY command to list all servers currently defined

to your application.

1337I SERVER xxxx NO LONGER ACTIVE Explanation: In response to an INFOCOMM DELETE command, the specified transaction

server has been removed from your application. System Action: Processing continues. User Response: None.

1338E MISSING SERVER ID Explanation: An INFOCOMM DELETE command was entered but no server ID was specified. System Action: The command is ignored. Processing continues. User Response: Reenter the command specifying the server identifier you wish to

delete.

1339I APPLICATION NAME xxxx NOT DEFINED - IMPLICIT START WILL BE ATTEMPTED

Explanation: In response to an INFOCOMM DEFINE command, your application attempted to send Infoserv data to the specified TP application xxxx but found it was not defined as a TP server application.

System Action: Your application will implicitly direct the TP server to define a connection with xxxx. If the start is successful, the connection will be in deferred state, causing the Infoserv data to be queued to the TP server checkpoint.

User Response: Ensure that the TP application name on the INFOCOMM command is correct. If it is, the transaction will be released when Infoserv initiates a connection. If not, the TP application name of the remote Infoserv may need to be changed.

1340E UNABLE TO START APPLICATION xxxx - FDBK = X'zzzz' Explanation: An implicit start was attempted by your application for a remote TP

application named xxxx. Message 1339 should have been issued previously. This start failed for the reason indicated in the feedback code zzzz.

System Action: The transaction that was to be sent to TP application xxxx is lost. User Response: If the feedback code can not be interpreted issue a TPAPPL xxxx START

DEFER command to cause the transaction to be queued. If This fails contact Cybermation support.

1341E INVALID SERVER ID Explanation: The server identifier specified on the Infoserv command exceeds 25

characters in length. System Action: The command is ignored. Processing continues. User Response: Correct the server identifier and reissue the command.

Messages and Codes

ESP-5.4-MC-03 187

1342E SERVER ID xxxx NOT DEFINED Explanation: The transaction server identifier xxxx specified on the Infoserv

command has not been defined to your application. System Action: The command is ignored, Processing continues. User Response: Use the INFOCOMM DEFINE command to define the transaction server to

your application and reissue the command.

1343E INCORREECT FUNCTION OR FUNCTION NOT SPECIFIED Explanation: An INFOSERV command was issued but no function was requested or a

function type is not a valid one. System Action: The command is ignored. Processing continues. User Response: Correct the function type and reissue the command

1344E ALIAS xxxx EXCEEDS MAXIMUM ALLOWABLE LENGTH Explanation: The Info/System alias name specified on Infoserv command exceeds 32

characters. This is the maximum alias length supported by the Info/System API as of release 4.2.2.

System Action: The command is ignored. Processing continues. User Response: Correct the alias name and reissue the command.

1345E ERROR PARSING INFOSERV COMMAND Explanation: A syntax error was detected when processing the Infoserv command. System Action: The command is ignored. Processing continues. User Response: Check the syntax in the Command Reference, correct it and reissue the

command.

1346W TP APPLICATION xxxx IS DEFERRED Explanation: An Infoserv command was issued resulting in the transmission of an

Infoserv request to the TP application xxxx; however the application is in the deferred state.

System Action: The Infoserv request will be queued to the TP server checkpoint until the TP application is reactivated.

User Response: Determine why the TP application is in deferred state and use the TPAPPL START command to reactivate it if necessary.

1347E RESPONSE ROUTER xxxx NOT DEFINED Explanation: The router name specified on the Infoserv command is not a valid one

or is currently not supported. System Action: The command is ignored. Processing continues User Response: Issue the INFOROUT command to list the available routers, correct the

command and reissue.

1348E ERROR PROCESSING MODULE xxxx FOR ROUTER yyyy Explanation: An error occurred while attempting to process the module associated

with the specified router on your Infoserv command. System Action: The command is ignored. Processing continues.

188 ESP-5.4-MC-03

User Response: Issue the INFOROUT command to obtain the name of the router processor module. Ensure the module is available in your application's libraries or in the system libraries. If unable to diagnose the problem contact Cybermation support.

1349E MISSING PARMS IN ROUTER DATA Explanation: The router name specified on an INFOSERV command did not contain all

the required parms. The parms required depend on the type of router specified.

System Action: The command is ignored. Processing continues. User Response: Refer to the documentation for an explanation of the required parms.

When the parms are corrected, reissue the command if required.

1350E ERROR LOADING xxxx ROUTER MODULE Explanation: An error occurred during execution of a LOAD macro for the indicated

module. This type of error is usually due to a module not found condition or an error with the data set directory.

System Action: The INFOSERV command is not processed. User Response: Ensure the module is available in a system library, or via a STEPLIB

or JOBLIB statements. Reissue the INFOSERV command if necessary. If problem persists, contact your support personnel.

1351E PARM ERROR PROCESSING ROUTER MODULE xxxx Explanation: One or more router parms specified on an INFOSERV command were not

valid. System Action: The command is ignored. Processing continues. User Response: Refer to the INFOSERV command in the Command Reference for more

details on the router parms. When the parms are corrected reissue the command if required.

1352W PARAMETER ERROR ON START COMMAND Explanation: While starting Infoserv encountered an invalid parameter. System Action: Messages 1369W and 1306A follow. User Response: Refer to the message 1306A.

1353E INVALID xxxx IN ROUTEWR DATA Explanation: The ROUTER keyword in an INFOSERV command requested the JOBTRACK

function but the xxxx passed in the router parms is invalid. System Action: The INFOSERV command is not processed. User Response: Correct the xxxx in the router parms and reissue the INFOSERV command

if necessary.

1354E INFORMATION/MANAGEMENT RECORD IDENTIFIER NOT SPECIFIED

Explanation: The PROBLEM_UPDATE function was specified on the INFOSERV command but no Information/Management identifier was received.

System Action: The INFOSERV command is not processed. User Response: Specify the Information/Management record identifier you wish to

update using the RECORD keyword and reissue the INFOSERV command if

Messages and Codes

ESP-5.4-MC-03 189

necessary.

1355E INVALID INFORMATION/MANAGEMENT RECORD IDENTIFIER Explanation: The Information/Management record identifier specified on the INFOSERV

command is invalid or is longer that 8 characters. The format of the record identifier is 1 alphabetic or national character followed by up to 7 alphanumeric characters.

System Action: The INFOSERV command is not processed. User Response: Correct the record identified and reissue the INFOSERV command if

necessary.

1356E CHECK IN FAILED FOR INFO/MANAGEMENT RECORD xxxx Explanation: After the updating the indicated Information/Management record

Infoserv attempted to remove the checkout indicator to free up the record but failed. The previous messages will contain the return code from the Info/System API.

System Action: The Information/Management record is left in checkout status and can no longer be accessed.

User Response: Contact your Info/System data base administrator to have the record checked in. Determine the cause of the problem using the Info/System API return code to prevent future occurrences.

1357I INFO/MANAGEMENT RECORD xxxx HAS BEEN UPDATED Explanation: In response to an INFOSERV PROBLEM_UPDATE command, the indicated

Information/ Management record with identifier xxxx has been updated with the data specified in the command.


1358W ERROR PROCESSING TEXT DATA FOR INFOSERV REQUEST Explanation: An error was detected while processing the text data specified on an

INFOSERV request. System Action: The request will be sent to Infoserv but the text data will not be

processed. User Response: Check the text data specified on the INFOSERV command to ensure it is

in the correct format (enclosed within backslashes) or that the data is not null.

1359E INFOSERV COMMAND EXCEEDES MAXIMUM LENGTH Explanation: An INFOSERV command was entered which exceeds the maximum length of

4096 bytes. System Action: The command is not processed. User Response: Review the command to ensure an error does not exist with one of the

data fields, especially the freeform text data which may have caused more than 4K of data to be generated.

1360W NO DATA IN xxx FIELD IN INFOSERV REQUEST TO yyyyy Explanation: An INFOSERV request was sent to client yyyyy but the data field in the

request named xxx did not contain any data.

190 ESP-5.4-MC-03

System Action: Processing continues. If the data field is a required one Info/System will issue an error message and the request will not be processed.

User Response: Check the specified data field and ensure a value was specified. If a symbolic variable was specified, ensure that a value is being generated (i.e. send a test message using that variable).

1361E INFOSERV T001 INITIALIZATION HAS FAILED - PLEASE RESTART IT

Explanation: Transaction T001 which initializes the Info/System failed. System Action: Infoserv is terminated. User Response: The trace data will help to identify the problem.

1362I InfoServ request xxx saved Explanation: Infoserv detected an error in Info/System, retried 3 times to

reprocess the request but unsuccessfully. System Action: The error will cause the Infoserv to abend with U1310. After

restarting the Infoserv there will be an attempt to process this request.


1363I InfoServ request xxx discarded Explanation: Infoserv detected an error in Info/System, retried 3 times to

reprocess this request but unsuccessfully. System Action: The request xxx can not be processed and therefore is discarded.

Depending on Usermod 19 the error will cause the Infoserv to abend with U1310 (Usermod 19 is OFF) or ignore the error and continue.


1364E ATTEMPT TO UPDATE A CLOSED TRANSACTION Explanation: An attempt was made to update a closed transaction. System Action: None. User Response: None.

1365E INVALID KEYWORD xxxx Explanation: An excessive keyword xxxx was detected while processing INFOSERV

command. System Action: Command is not processed. User Response: Correct the command and reissue it if necessary.

1366W PARAMETER ERROR ON FOLLOWING STATEMENT FROM xxx FILE Explanation: An error was detected was processing statements from xxx file. System Action: The messages 1369W and 1306A follow. User Response: Refer to the message 1306A.

1367W FOLLOWING STATEMENT FROM xxx HAS AN INVALID SYNTAX Explanation: An error was detected was processing statements from xxx file. System Action: The messages 1369W and 1306A follow. User Response: Refer to the message 1306A.

Messages and Codes

ESP-5.4-MC-03 191

1368W FOLLOWING STATEMENT FROM xxx HAS AN UNDEFINED PARAMETER

Explanation: An error was detected was processing statements from xxx file. System Action: The messages 1369W and 1306A follow. User Response: Refer to the message 1306A.

1369W xxxxx Explanation: This message displays the erroneous statement. It follows the message

that describes the nature of the error System Action: The message 1306A follows User Response: Refer to the message 1306A.

1370I OK Explanation: This message is issued in response to a conversationally entered

command that was processed successfully. System Action: The processing continues. User Response: None.

1371W MAXERRS COMMAND NOT AVAILABLE Explanation: MAXERRS command is not available in current release. System Action: The command ignored. Processing continues. User Response: Use CLIDEF or CLIENT command to set or alter maximum errors value.

1372C Usermod Status Explanation: This is a header for Usermod Status Display. System Action: Infoserv displays the status. User Response: None.

1373I OK Explanation: This message is in response to the CELLTRC command entered from the

console. The message means that the command was processed successfully by Infoserv.


1374I OK Explanation: This is a response to OKSWAP/DONTSWAP command from the console was

processed successfully. System Action: Processing continues. User Response: None.

1375I ALREDY QUIESCED Explanation: A QUIESCED command was entered from system console to Infoserv which

already was in quiesced status. System Action: The command ignored. Processing continues. User Response: None.

192 ESP-5.4-MC-03

1376I QUIESCING Explanation: A QUIESCED command was entered from system console to Infoserv which

was in active status. System Action: Infoserv processes the command. User Response: None.

1377I RESTARTING Explanation: A RESTART command was entered from system console to Infoserv which

was in quiesced status. System Action: Infoserv processes the command. User Response: None.

1378I NOT QUIESCED Explanation: A RESTART command was entered from system console to Infoserv which

already was in active status. System Action: The command ignored. Processing continues. User Response: None.

1379W INVALID COMMAND Explanation: An invalid command was entered from the system console. System Action: The command is ignored. Processing continues. User Response: Correct the command and reissue it if necessary.

1380W INVALID COMMAND NAME SYNTAX Explanation: There is an syntax error in the command entered from the system

console. System Action: The command is ignored. Processing continues. User Response: Correct the command and reissue it if necessary.

1381S ERROR OBTAINING A COMMAND, RC=nn Explanation: An error was detected while receiving command from system console. System Action: A message 1382S follows. User Response: See message 1382S.

1382S COMMAND PROCESSING TERMINATED Explanation: This message follows message 1381S. System Action: The Infoserv is terminating. User Response: Check if all necessary tasks are up and running. if some are down -

find out why and start them.

1383? CYBERMATION INFOSERV RELEASE xx.xx STATUS Explanation: This is the header for the information requested by STATUS command. System Action: Infoserv displays its current processing status. User Response: None.

1384W ERROR COUNT RESET FOR CLIENT xxxx Explanation: This message is issued in response to CLIENT xxxx RESTART command if

Messages and Codes

ESP-5.4-MC-03 193

the client xxxx was suspended because error threshold was reached. System Action: Message 1385W follows. User Response: None.

1385W CLIENT xxxx NOW ACTIVE Explanation: This message is issued in response to CLIENT xxxx RESTART command. System Action: The processing continues. User Response: None.

1386I ERROR THRESHOLD IS SET TO nn FOR CLIENT xxxx Explanation: This message appears when parameter MAXERRS(nn) was included in CLIDEF

or CLIENT command. System Action: Processing continues. User Response: None.

1387? INFOSERV CLIENT DISPLAY Explanation: This message starts the display of information about the client. The

display was requested by CLIENT command. System Action: Information display follows. User Response: None.

1388? INFOSERV CLIENT DISPLAY Explanation: This message starts the display of information about all Infoserv

clients. The display was requested by CLIENT command but no client name was specified.

System Action: Information display follows. User Response: None.

1389W ERROR SCANNING CLIENT COMMAND Explanation: An error in system routine IKJPARS was detected while parsing CLIENT

command. System Action: The command ignored. Processing continues. User Response: Check the syntax of the CLIENT command and reissue the command. If

problem persists, notify your support personnel.

1390W CLIENT xxxx NOT DEFINED TO INFOSERV Explanation: The client name xxxx, that was specified in CLIENT command in not

known to Infoserv. System Action: The command is ignored. Processing continues. User Response: Verify the client name. Use CLIENT command with no parameters to get

the full list of the client names defined to Infoserv.

1391I INFOSERV LOG HAS BEEN DUMPED Explanation: The message above appears after the Infoserv log has been dumped to

the print data set. System Action: Processing continues. User Response: None.

194 ESP-5.4-MC-03

1392E UNABLE TO CLOSE INFOSERV PRINT DATASET Explanation: A DUMPLOG command was issued but there is no print data set defined to

Infoserv. System Action: The command is ignored. Processing continues. User Response: Include IFSPRINT card in Infoserv's starting procedure.

1393E ERROR OPENING INFOSERV PRINT DATASET Explanation: A DUMPLOG command was issued but Infoserv could not open the IFSPRINT

data set. System Action: The command is ignored. Processing continues. User Response: Check whether IFSPRINT card in Infoserv's starting procedure defines a

proper file and correct the situation.

1394I CLIENT xxxx SUSPENDED Explanation: A request was received for client xxxx which is in suspended status. System Action: The request is ignored. Processing continues. User Response: Check why the client xxxx is in suspended status and restart it, if

necessary.

1395W INFOSERV REQUEST xxxx FROM CLIENT yyyyy WILL BE RETRIED Explanation: While processing request xxxx from client yyyyy Infoserv detected an

error in Info/System. System Action: The request will be retried up to 3 times. User Response: None.

1396W NO RESPONSE REQUESTED FOR THIS TRANSACTION Explanation: Information/Management record was created/updated but no response was

requested for this transaction. System Action: Response is not built and not sent. Processing continues. User Response: None.

1397E TP SERVER FEEDBACK ERROR CODE xxxxxxxx Explanation: While processing a transaction a TP Server error was encountered. System Action: This message follows another which describes in more detail the actual

error. System action depends on where the error occurred and is determined by previous message.

User Response: Check the previous message. Ensure TP Server is up and alive.

1398I Unable to journal transaction due to above error. Explanation: The error journal (file IFSSAVE2) could not be opened. System Action: Journalling is bypassed. User Response: Ensure that IFSSAVE2 card exists in Infoserv's starting procedure, if

needed.

1399E INVALID CLIENT xxxx FOR PRIVILEGE CLASS ccc Explanation: Client xxxx was trying to create/update Info/System record but is not

in the privilege class ccc.

Messages and Codes

ESP-5.4-MC-03 195

System Action: The request is ignored. Processing continues. User Response: Add client xxxx to the privilege class ccc, if required.

1400E CHECKPOINT GETMAIN ERROR - X'xxxx' Explanation: An error was encountered during GETMAIN in checkpoint processing.

A bad return code was received from a call to GETMAIN. The return code from GETMAIN is displayed in the message. The meaning of this return code can be found in the IBM manual: Application Development Reference: Services for Assembler Language Programs (GC28-1642).

System Action: The ESP subsystem will attempt to shut down. It is possible that the memory shortage will impair its ability to do an orderly shutdown. In that case it may be necessary for the operator to cancel the ESP subsystem.

User Response: Ensure there is enough REGION specified for the ESP subsystem. Increase the REGION specification on the EXEC card and restart ESP.

1401I OPEN_LU REQUEST RECEIVED Explanation: System Action: User Response:

1402I A NON-CPE CONVERSATION WAS STARTED Explanation: System Action: User Response:

1403E xxxx Explanation: System Action: User Response:

1404W UNABLE TO CLOSE ACB - ERROR = X'xxxx' Explanation: System Action: User Response:

1405W CNOS FAILURE WITH xxxx Explanation: System Action: User Response:


1407I CYBERMATION TP SERVER STARTED FOR xxxx Explanation:

196 ESP-5.4-MC-03


1408W at SND99998 with TPPD=0 Explanation: System Action: User Response:

1409W at SND99999 with TPRE=0 Explanation: System Action: User Response:

1410W SEND IS DEALLOCATING A CONV Explanation: System Action: User Response:

1411E SEND TO xxxx FAILED - Explanation: System Action: User Response:


1413W TRANSACTION xxxx NOT DEFINED TO THIS APPLICATION Explanation: System Action: User Response:

1414W TP Application xxxx not defined Explanation: System Action: User Response:

1415I CHECKPOINT MANAGER SHUTDOWN COMPLETE Explanation: System Action: User Response:

1416I CHECKPOINT AREA SIZE = Explanation: System Action: User Response:

Messages and Codes

ESP-5.4-MC-03 197

1417I DATA SET IS EMPTY - CLEAR PROCESSING INITIATED Explanation: System Action: User Response:

1418E CHECKPOINT CONTAINS INVALID DATA - Explanation: System Action: User Response:

1419I TP SERVER CHECKPOINT FORMAT COMPLETE Explanation: System Action: User Response:

1420I APPLICATION xxxx NOT ACTIVE - CONNECTION DEFERRED Explanation: The inter-system tracking command component attempted to connect to

the destination application but the destination application was not active. This message should be preceded by a message with the following text: RECEIVE FROM lu_name FAILED RCPR=xxxx RCSC=yyyy where "xxxx" and "yyyy" are VTAM diagnostic codes. The meaning of these codes can be found in the IBM manual entitled "VTAM Programming for LU 6.2" in the Appendix labelled "Return Codes". "xxxx" corresponds to the field RPL6RCPR and "yyyy" corresponds to the field RPL6RCSC.

System Action: The command is not executed. User Response: Insure that the destination application is active before issuing the

command.


1422I Application xxxx Explanation: System Action: User Response:

1423I TP SERVER LU OPENED SUCCESSFULLY Explanation: System Action: User Response:

198 ESP-5.4-MC-03

1424I TP CHECKPOINT DATA SET NAME IS xxxx Explanation: System Action: User Response:

1425W TP SERVER LU already active Explanation: System Action: User Response:

1426W TP SERVER feedback code xxxx Explanation: System Action: User Response:

1427I APPLICATION STATUS DISPLAY Explanation: This is a heading for TP Server status display. It is followed by

messages detailing Server's current state. APPLICATION NAME: name specified in LOCAPPL statement STATE: initializing, normal or stopping VTAM LU NAME: server's LU name DEFAULT LOGON MODE: logon mode from LOCAPPL statement APPLICATIONS: list of all partners known to the server. Applications that are not connected (because of a request to defer the connection or for any other reason) are shown with (D) after a name. LOCAL TRANSACTIONS: This lists clients listening for incoming data. ------------ CHECKPOINT INFORMATION ---- CHECKPOINT DSNAME: data set name of TP Server's checkpoint CHECKPOINT SIZE: space allocated to the data set CHECKPOINT USED: actual amount of data in checkpoint QUEUED APPLICATIONS: list of partners to whom outbound message queues exist

System Action: Processing continues. User Response: None required.

1428E COMMAND PROCESSING ERROR - TP FEEDBACK = X'xxxx' Explanation: System Action: User Response:

1429I TP SERVER IS NOT ACTIVE Explanation: System Action: User Response:

Messages and Codes

ESP-5.4-MC-03 199

1430I TIMEOUT DEBUG TEST MODE SET Explanation: System Action: User Response:

1431I LOST I/O TIME INTERVAL SET Explanation: System Action: User Response:

1432I Automatic retry for appl xxxx not active Explanation: System Action: User Response:

1433I Automatic retry for appl xxxx currently set to nnyyyy Explanation: System Action: User Response:

1434W TP Application xxxx not defined Explanation: System Action: User Response:

1435I NO TRANSACTIONS HELD Explanation: System Action: User Response:


1437I THE SERVER IS NOT ACTIVE Explanation: System Action: User Response:

1438E DIV IDENTIFY ERROR RETCODE = xxxx REASON = zzzz Explanation: The TP Server issued a DIV IDENTIFY request, but the return code

from the operating system indicated an error occurred. The return code is shown as four hexadecimal digits, and the reason code is also shown as four hexadecimal digits.

System Action: The TP Server terminates. User Response: Using the appropriate IBM manual, which will have a title like

200 ESP-5.4-MC-03

Assembler Services Reference, investigate the meaning of the DIV error and reason codes. The reason code should uniquely identify the problem, and indicate a response. The codes are documented with the DIV macro instruction. Then, respond as indicated by IBM for the particular situation.

1439I APPC SENSE DATA - xxxx Explanation: System Action: User Response:

1440I CONVERSATION ADDED Explanation: System Action: User Response:

1441I CONVERSATION DELETED Explanation: System Action: User Response:

1442W LU xxxx IS NOT ACTIVE Explanation: System Action: User Response:

1443E SETLOGON FAILED Explanation: System Action: User Response:

1444E GETMAIN FOR BELOW THE LINE STORAGE FAILED Explanation: System Action: User Response:

1445E TRANSACTION DOES NOT EXIST Explanation: System Action: User Response:

1446E TPALIAS COMMAND FAILED - TPAR FEEDBACK = X'xxxx' Explanation: System Action: User Response:

1447E A TRANSACTION AND APPLICATION NAME MUST BE PROVIDED Explanation:

Messages and Codes

ESP-5.4-MC-03 201


1448E UNABLE TO LOAD MODULE xxxx Explanation: System Action: User Response:

1449E UNABLE TO LOAD MODULE xxxx Explanation: System Action: User Response:

1450I APPLICATION xxxx Explanation: System Action: User Response:

1451I APPLICATION xxxx Explanation: System Action: User Response:

1452E APPLICATION START FAILED - TP SERVER IS STOPPING Explanation: System Action: User Response:

1453I xxxx INCOMING DATA PACKETS PURGED FROM TP CHECKPOINT Explanation: System Action: User Response:

1454W VTAM IS NOT ACTIVE Explanation: System Action: User Response:

1455I TP SERVER AWAITING CHECKPOINT INITIALIZATION Explanation: System Action: User Response:

1456S THE TP SERVER CHECKPOINT IS FULL Explanation: System Action: User Response:

202 ESP-5.4-MC-03


1458W TP SERVER LU OPEN FAILED Explanation: System Action: User Response:

1459I RESUMED TRANSACTION ERROR OCCURRED, FEEDBACK CODE = xxxx

Explanation: An error has occurred while resuming checkpointed transactions. System Action: None. User Response: None.

1460E DIV ACCESS ERROR RETCODE = xxxx REASON = zzzz Explanation: The TP Server issued a DIV ACCESS request, but the return code



Assembler Services Reference, investigate the meaning of the DIV error and reason codes. The reason code should uniquely ACCESS the problem, and indicate a response. The codes are documented with the DIV macro instruction. Then, respond as indicated by IBM for the particular situation.

1461E CKPT ALLOCATION ERROR - X'xxxx' Explanation: System Action: User Response:

1462E DIV MAP ERROR RETCODE = xxxx REASON = zzzz Explanation: The TP Server issued a DIV MAP request, but the return code



Assembler Services Reference, investigate the meaning of the DIV error and reason codes. The reason code should uniquely MAP the problem, and indicate a response. The codes are documented with the DIV macro instruction. Then, respond as indicated by IBM for the particular situation.

Messages and Codes

ESP-5.4-MC-03 203

1463E DIV UNMAP ERROR RETCODE = xxxx REASON = zzzz Explanation: The TP Server issued a DIV UNMAP request, but the return code



Assembler Services Reference, investigate the meaning of the DIV error and reason codes. The reason code should uniquely UNMAP the problem, and indicate a response. The codes are documented with the DIV macro instruction. Then, respond as indicated by IBM for the particular situation.

1464E DIV SAVE ERROR RETCODE = xxxx REASON = zzzz Explanation: The TP Server issued a DIV SAVE request, but the return code



Assembler Services Reference, investigate the meaning of the DIV error and reason codes. The reason code should uniquely SAVE the problem, and indicate a response. The codes are documented with the DIV macro instruction. Then, respond as indicated by IBM for the particular situation.

1465I CONNECTION WITH APPLICATION xxxx HAS BEEN REMOVED Explanation: System Action: User Response:

1466I nn TRANSACTION(S) RELEASED FOR xxxx Explanation: The TPSERVER has established a connection with a partner and some

messages that have been queued to that partner have been scheduled for transmission.

System Action: The messages are scheduled to be sent to the partner. User Response: None.

1467I xxxx TRANSACTIONS DELETED FOR yyyy Explanation: System Action: User Response:

1468E UNABLE TO OPEN ACB - ERROR = X'xxxx' Explanation: System Action: User Response:

204 ESP-5.4-MC-03

1469S TP SERVER CHECKPOINT nn PERCENT FULL Explanation: System Action: User Response:

1470W TP SERVER CHECKPOINT nn PERCENT FULL Explanation: System Action: User Response:

1471I TP SERVER CHECKPOINT nn PERCENT FULL Explanation: System Action: User Response:

1472E DIV SAVE ERROR RETCODE = xxxx Explanation: System Action: User Response:

1473S AN ABEND Sxxxx HAS occurred IN CYBTP004 Explanation: System Action: User Response:

1474I THE SERVER IS NOT ACTIVE - COMMAND NOT EXECUTED Explanation: System Action: User Response:

1475C APPLICATION STATUS DISPLAY Explanation: System Action: User Response:

1476I NO TRANSACTIONS HELD Explanation: System Action: User Response:

1477I TP SERVER INITIALIZATION IN PROGRESS Explanation: System Action: User Response:

Messages and Codes

ESP-5.4-MC-03 205

1478S THE LOCAPPL STATEMENT IS REQUIRED BUT WAS NOT SPECIFIED

Explanation: System Action: User Response:

1479S THE TPCKPT STATEMENT IS REQUIRED BUT WAS NOT SPECIFIED


1480S A TP SERVER IS ALREADY ACTIVE FOR APPLICATION xxxx Explanation: System Action: User Response:

1481W INVALID STARTUP PARAMETER SPECIFIED Explanation: System Action: User Response:

1482E THE SERVER IS NOT ACTIVE - COMMAND NOT EXECUTED Explanation: The inter-system tracking command component of ESP attempted to process

a command, but the TP server component was not active. System Action: The command is not executed. User Response: Recycle the ESP subsystem. If the problem persists, contact

Cybermation.

1483I xxxx Async mode is {On|Off} Explanation: System Action: User Response:

1484E MAXIMUM CONVERSATIONS ALLOCATED Explanation: System Action: User Response:

1485E CANNOT DELETE THE LAST OUTGOING CONVERSATION Explanation: System Action: User Response:

1486E TP SERVER ABEND Sxxxx IN CYBTP001 Explanation: System Action:

206 ESP-5.4-MC-03

User Response:

1487I xxxx ACTIVE CONVERSATIONAL TRANSACTIONS TERMINATED Explanation: System Action: User Response:

1488I xxxx INCOMING DATA PACKETS RELEASED FOR APPLICATION yyyy


1489E ERROR OCCURRED DURING COMMAND PARAMETER SCAN Explanation: System Action: User Response:

1490C ENTER INITIALIZATION PARAMETER OR 'END' Explanation: System Action: User Response:

1491E xxxx Explanation: System Action: User Response:

1492W FOLLOWING STATEMENT FROM xxxx HAS AN INVALID SYNTAX Explanation: System Action: User Response:

1493W FOLLOWING STATEMENT FROM xxxx HAS AN UNDEFINED PARAMETER


1494W PARAMETER ERROR ON FOLLOWING STATEMENT FROM xxxx FILE


1495W xxxx Explanation:

Messages and Codes

ESP-5.4-MC-03 207


1496A REENTER ENTIRE STATEMENT, 'CANCEL' OR 'END' Explanation: System Action: User Response:

1497I nn of mm TRANSACTION(S) RELEASED FOR yyyy Explanation: The TPSERVER has established a connection with a partner, and some

messages that have been queued to that partner have been scheduled for transmission. Due to internal pacing requirements, a subset of the queued messages have been scheduled.

System Action: The messages are scheduled to be sent to the partner. When they have been successfully sent, another batch will be scheduled.


1498W TP I/O to application xxxx has been outstanding for nn minutes Explanation: The TPTIME command/statement has been used to set a TP Server I/O

timeout warning message. An I/O request to the named application has exceeded the specified threshold.

System Action: The message will be repeated at the installation specified interval until the I/O is complete.

User Response: If this message is repeated, check the state of the VTAM connection to the specified LU.

1499S UNABLE TO OPEN ACB - ERROR = X'xx' Explanation: The TpServer encountered an error when attempting to open the ACB

for the partner logical unit. "xx" is the VTAM OPEN error code as found in the manual entitled "VTAM Programming"

System Action: ESP terminates. User Response: Taker the proper VTAM corrective action as indicated by the error code

and re-start ESP.

1514E ESPCOM is not active Explanation: ESP made a request to its outbound communication server, ESPCOM,

but ESPCOM has not been properly initialized. ESPCOM initializes when a COMMQ statement is encountered in ESPPARM.

System Action: The request is ignored. An additional message will be issued that describes the request.

User Response: If a COMMQ statement is present in ESPPARM, look in the ESP start up messages for a message describing a possible error. Enter the correct COMMQ statement in ESPPARM and restart ESP.

1515E Invalid format of SEND request Explanation: This is an internal error. System Action: The request is ignored. An additional message will be issued that

describes the request. User Response: Report the error to ESP technical support.

208 ESP-5.4-MC-03

1516E CommQ file is full Explanation: The CommQ file is used by ESP outbound communication server, ESPCOM,

to store messages until they are successfully sent. It must be big enough to accommodate possible traffic delays due to network problems or inactive recipients. If the file is too small, it can fill up.

System Action: ESPCOM will attempt to allocate additional disk space for the CommQ file. This can succeed only if a secondary allocation amount was specified for the data set. If additional allocation fails, messages may be lost.

User Response: Allocate a bigger CommQ file and copy the contents of the old file into the new one using the REPRO function of IDCAMS. Then restart ESP with the new CommQ file.

1517E ESPCOM display Explanation: This message is a heading for ESPCOM status information that

follows it. The information is displayed as a result of F ESP,ESPCOM LIST command.

System Action: Processing continues. User Response:

1518E Destination name is missing for QUIESCE/RESTART/FLUSH request Explanation: The User entered an ESPCOM command with one of the above keywords but

without a destination name. The destination name is required. System Action: The command is ignored. User Response: Reenter the command with a destination name in it.

(generics accepted).

1519I Quiesce requested for nnnn destinations Explanation: The user entered an ESPCOM QUIESCE command with a node name that

matches nnnn destinations. System Action: Outbound communications with all matching nodes will be suspended. User Response:

1520I Restart requested for nnnn destinations Explanation: The user entered an ESPCOM RESTART command with a node name that

matches nnnn destinations. System Action: Outbound communications with all matching nodes will be resumed. User Response:

1521I Queue flush requested for nnnn destinations Explanation: The user entered an ESPCOM FLUSH command with a node name that matches

nnnn destinations. System Action: Outbound message queues will be flushed (all messages discarded)

for all matching nodes. User Response:

Messages and Codes

ESP-5.4-MC-03 209

1522E Unable to quiesce communications with dddd: CommQ file is full Explanation: The user entered an ESPCOM QUIESCE command for destination dddd. The

command could not be executed due to lack of space in the CommQ file. System Action: Communication with dddd is not quiesced. User Response: Allocate a bigger CommQ file and copy contents of the old CommQ file

into the new one using the REPRO function of IDCAMS. Then restart ESP.

1523E Number of active destinations is at the limit: nnnn. Some destinations are quiesced.

Explanation: This version of ESPCOM has a limit of nnnn destinations active concurrently. ESPCOM has messages bound for more than nnnn destinations.

System Action: Communications with destinations in excess of nnnn are quiesced. User Response: You can rearrange the active and quiesced parts by quiescing some

destinations and restarting others.

1524I (TCP/IP | APPC) connection with dddd has been waiting for nnnn minutes Explanation: ESPCOM has a communication operation with node named dddd,

such as SEND or CONNECT, that has been pending for nnnn minutes. It indicates a possible problem with the network or network services (TCP/IP or VTAM).

System Action: User Response: Look for error messages from underlying network services. If the

problem persists, consult the network specialist.

1525I nnnn messages flushed from dddd queue Explanation: The user entered an ESPCOM FLUSH command that resulted in nnnn

messages having been flushed (discarded) from the queue bound for destination dddd.

System Action: The affected messages are discarded. User Response: None.

1526E Unable to encrypt a message for dddd. Sender quiesced. Explanation: ESPCOM encountered an error trying to encrypt a message for

destination dddd. A preceding message explains the error. System Action: Communication with destination dddd is quiesced. User Response: It is probably an internal error. Report it to ESP technical support.

1527E CommQ ssss error. R15=aaaaaaaa R0=bbbbbbbb Explanation: ESPCOM encountered an error in operation ssss on the CommQ file.

R15 and R0 contain the return and reason code from the operation. System Action: If the error occurs during ESPCOM initialization, ESPCOM will not

be initialized. During normal operation, the error will result in failure to save data or to expand the data set.

User Response: For initialization time errors, or for OPEN error, ensure that the COMMQ statement specifies a properly allocated linear data set with SHAREOPTIONS(2,3), and that no other job is updating the

210 ESP-5.4-MC-03

data set.

1528E CommQ data set has invalid format Explanation: ESPCOM found that the CommQ file is not empty and its format is

incorrect. System Action: ESPCOM is not initialized. User Response: Either provide the correct data set, or start ESP with the COMQFORMAT

parameter to format the present data set.

1529I CommQ file is full. Space allocated: aaaa, used: uuuu bytes Explanation: ESPCOM attempted to store a record in the CommQ file but there is not

enough space available. System Action: ESPCOM will attempt to expand the data set using secondary space

allocation. User Response: None.

1530E CommQ expansion limit reached Explanation: ESPCOM needs to store a record in the CommQ file, but there is not

sufficient space, and the file cannot be expanded because that would exceed the expansion limit of 4M in a single ESP session.

System Action: The CommQ file will not be expanded. User Response: Simply restarting ESP will provide a new 4M expansion window, but it

is better to allocate a bigger CommQ file, copy the contents of the old file into it, and restart ESP with the new file.

1531I An attempt to expand CommQ file failed Explanation: ESPCOM's attempt to expand the CommQ file failed. This message may

be accompanied by other messages describing the failure. System Action: The ESPCOM request that required the CommQ space will fail. User Response: Allocate a bigger CommQ file, copy the contents of the old file into

it using the REPRO function of IDCAMS, and restart ESP with the new file.

1532I CommQ file has been expanded. Space allocated: aaaa, used: uuuu bytes. Explanation: The CommQ file has filled up and was successfully expanded. System Action: Processing continues. User Response: None.

1533I CommQ file usage is down to nn% Explanation: The CommQ file had filled to a level that warrants user attention, and

now the usage has gone down to the value shown. System Action: Processing continues. User Response: None.

1534W CommQ file is nn% full Explanation: System Action: Processing continues. User Response:

Messages and Codes

ESP-5.4-MC-03 211

1535E Unable to send a message to Distributed Manager Explanation: Due to a problem described by a previous message, ESP failed to

send a message to a Distributed Manager. System Action: The message will be lost. User Response: Correct the underlying problem indicated by a previous message.

1536E Incompatible requests for resource rrrr in aggregate aaaa.qqqq Explanation: System Action: User Response:

1537E Error obtaining local IP address. RC=cccc Explanation: While processing a LOADAGDF command, ESP encountered a MANAGER

statement indicating that ESP is to use TCP/IP. ESP attempted to determine its own IP address and failed. A preceding message describes the error.

System Action: Processing continues, but this error will cause a failure on a subsequent statement that specifies TCP/IP agent.

User Response: Correct the underlying TCP/IP problem.

1538W Agent/DM receiver not defined for port pppp Explanation: While processing a LOADAGDF command, ESP encountered a MANAGER

statement that specifies a port pppp for inbound communications but no agent receiver is defined for that port.

System Action: Processing continues. User Response: Either correct the port number or define an agent receiver for

port pppp.

1539E Insertion not allowed: application contains DM-controlled objects Explanation: The user attempted to insert a job into a generated application

that contains workload objects controlled by a Distributed Manager. In the present version, Distributed Manager does not allow insertions into a generated application.

System Action: The insertion request is ignored. User Response: None.

1540E Unable to send agent message Explanation: ESP encountered an error attempting to send a message to an agent.

A preceding message describes the error. System Action: The message may be lost. User Response: Correct the underlying communication problem.

1541I Command forwarded to the owning manager, mmmm Explanation: The user issued a command to change status of a workload object

that is controlled by a Distributed Manager named mmmm. ESP forwarded the command to mmmm.

System Action: The owning manager will execute the command.

212 ESP-5.4-MC-03


1542E Internal error: invalid message type tttt in call from mmmm Explanation: ESPCOM was passed an unexpected message type tttt in a call from

module mmmm. System Action: Processing continues. User Response: Report the error to Cybermation technical support.

1543E Internal error: duplicate listener for msgtype tttt in mmmm Explanation: ESPCOM was passed an unexpected request for message type tttt in a

call from module mmmm. System Action: Processing continues. User Response: Report the error to Cybermation technical support.

1544I Message to dddd has been sent successfully Explanation: ESPCOM has succeeded in sending a message with which it encountered

errors in previous attempts. dddd is the destination name. System Action: Processing continues. User Response:

1545E Error connecting to dddd Explanation: ESPCOM encountered an error on an attempt to connect to dddd. A

preceding message contains detailed information about the failure. System Action: ESPCOM will set a timer and retry the operation later. The error

message will not be repeated on subsequent attempts to connect. Instead, a message indicating success will be issued when processing is complete.

User Response: Ensure that the correspondent named dddd is active and ESP uses its correct address and the network is functioning properly.

1546E Error sending a message to dddd Explanation: ESPCOM encountered an error on an attempt to send a message to dddd.

A preceding message contains detailed information about the failure. System Action: ESPCOM will set a timer and retry the operation later. A message

indicating success will be issued when processing is complete. User Response: Ensure that the correspondent named dddd is active and the network is

functioning properly.

1547W Invalid message received by Agent Receiver rrrr from aaaa:pppp Explanation: An ESP Agent Receiver received a message with unexpected format.

aaaa:pppp is the sender's TCP/IP address and port. If the sender is an ESP node, inconsistent configuration is a possible reason.

System Action: The message is discarded. User Response: If the message comes from an ESP node, ensure that the node parameters

are correctly described in ESP agent definition table.

1548W Invalid feedback message received from pppp Explanation: ESP received invalid feedback on a message it sent to a partner

Messages and Codes

ESP-5.4-MC-03 213

named pppp. The error may result from incorrect description of the partner in ESP agent definition table.

System Action: ESP will retry the communication. User Response: If the error persists, correct either agent definition table or

partner parameters so that they are consistent with each other.

1549W Message rejected by pppp Explanation: ESP received a negative acknowledgment on a message it sent to a

partner named pppp. The error may result from incorrect description of the partner in ESP agent definition table.

System Action: ESP will retry the communication. User Response: If the error persists, correct either agent definition table or

partner parameters so that they are consistent with each other.

1550E Real agent definition not found for virtual agent aaaa Explanation: A virtual agent was defined without a prior definition of a real

agent. A virtual agent definition must be immediately preceded by the definition of a real agent or of another virtual agent.

System Action: The entire agent definition is rejected. If an older definition was loaded earlier in the ESP session, it will remain in force.

User Response: Correct the error and load the agent definition again.

1551E Too many aliases for aaaa. Maximum allowed is mmmm Explanation: The number of virtual agents, or aliases, for real agent aaaa

exceeds the allowed maximum of mmmm. System Action: The entire agent definition is rejected. If an older definition

was loaded earlier in the ESP session, it will remain in force. User Response: Correct the error and load the agent definition again.

1553E No workload object modules found Explanation: ESP could not find the workload object module directory while

processing the WOBCMD command. System Action: The command will not be executed. User Response: Ensure that the workload object type on which you wish to operate

is properly defined to ESP with a WOBDEF statement.

1554E Undefined workload object type Explanation: A WOBCMD command was issued for a workload object type that is

unknown to ESP. System Action: The command will not be executed. User Response: Ensure that the workload object type on which you wish to operate

is properly defined to ESP with a WOBDEF statement.

1555E Job not found Explanation: A WOBCMD command was issued for a job that could not be found

within the specified application. System Action: The command will not be executed. User Response: Reissue the command with the correct job name and qualifier.

214 ESP-5.4-MC-03

1556E Not a WOBDEF-controlled object type Explanation: A WOBCMD command was issued for a job that is not associated with a

WOBDEF-defined object type (TASKs, LINKs and MVS jobs do not have WOBDEF controlled definitions).

System Action: The command will not be executed. User Response: None.

1557E Unable to find password matching xxxx, yyyy, zzzz Explanation: A user ID was specified which required a password. ESP was unable

to find a password entry which matched user xxxx, workload object type yyyy and agent name zzzz.

System Action: Processing ends for this job. User Response: Define a password to match the parameters above using the ESP

PASSWORD command. Then retry the operation.

1558E No space in ATR to store data for jjjj/aaaa Explanation: There was insufficient space in the ATR to store data for a

SAP_Job jjjj in application aaaa. System Action: The application is not built. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


1559W Invalid nnnn: tttt. Ignored. A numeric up to 8 digits expected. Explanation: The value tttt for the ESP environment variable nnnn is invalid. The

value should be a numeric string no longer than 8 digits. System Action: ESP will use a default value. User Response: Set a correct value using ESP's SET operator command.

1560E Invalid variable name Explanation: A SET command had operands, but they did not begin with a valid

variable name, delimited by an assignment operater ('='). A valid name consists of up to 256 alphanumeric characters. Case is not significant. The national characters, and the underscore, are also acceptable.

System Action: The command is ignored. User Response: Not required.

1561I ESP Environment Variables Explanation: This is the heading for the list of ESP environment variables. System Action: Variables are listed after this message. User Response: Not required.

1562E User xxxx denied access to agent yyyy Explanation: User xxxx is not authorized to submit jobs to agent yyyy. "xxxx"

is the user id under which the event executes for this job,

Messages and Codes

ESP-5.4-MC-03 215

normally the event prefix, but it may be a triggering user, or may be overridden by an installation EVENTSAF exit.

System Action: The job enters the SUBERROR state. User Response: In order to submit jobs to agent yyyy, user xxxx must have read

access to SAF profile AGENT.yyyy. Once this has been established, resubmit the job.

1563E SAP_Job xxxx in Appl yyyy, SAPJOBNAME statement missing Explanation: ESP detected that a JOBCOPY statement was specified in a SAP_JOB,

but a SAPJOBNAME was not. SAPJOBNAME statement is mandatory in a SAP_JOB that has JOBCOPY statement.

System Action: The execution of the object fails, and a "submit error" status results.

User Response: Specify the JOBCOPY statement. Then resubmit the job.


is the user id under which the event executes for this job, normally the event prefix, but it may be a triggering user, or may be overridden by an installation EVENTSAF exit.

System Action: The application is not built. User Response: In order to submit jobs to agent yyyy, user xxxx must have read

access to SAF profile AGENT.yyyy. Once this has been established, retrigger the event.

1565E Destination name xxxxxxxx does not exist Explanation: Destination xxxxxxxx referenced in an ESPCOM command does not exist. System Action: The command is ignored. User Response: Correct the destination name, and reissue the command.

1566E ???_Job xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Provide the Agent name. Then resubmit the job.

1567E Invalid Agent name wwww in Appl yyyy Explanation: The agent named wwww was not defined when the workload object was

readied. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Either correct the Agent name, or define the Agent. Then resubmit

the job.

1568E Unable to find password matching xxxx, yyyy, zzzz, RC=n Explanation: A user ID was specified which required a password. ESP was unable


System Action: Processing ends for this job.

216 ESP-5.4-MC-03

User Response: Define a password to match the parameters above using the ESP PASSWORD command. Then resubmit the job.

1570E Wild cards are not allowed for exclusive ENQUEUE: nnnn Explanation: An ENQUEUE statement requested exclusive control over resource named

nnnn, but nnnn contains wild card characters. Wild cards are allowed only for shared enqueues.

System Action: The building of an application is aborted. User Response: Correct the statement.

1571C Enqueue Display Explanation: This message is a header for ESP's response to the ENQUEUE command. System Action: The display follows. User Response: None.

1572I No matching Enqueues found Explanation: This message is displayed in response to an ENQUEUE command when ESP

has no enqueues matching the name on the command. System Action: None. User Response: None.

1573I EnqSelf mode is (NOT)ALWAYS Explanation: This message is a response to ENQSELF command and shows the current

setting, which can be either ALWAYS or NOTALWAYS. System Action: None. User Response: None.

1574E APPLINS: job definition statements missing Explanation: An APPLINS command was entered in line mode without job definition

statements. System Action: The command is rejected. User Response: Either supply the statements in the APPLINS command,or issue the

command in ISPF full screen mode where ESP can open an edit session for you to enter job definition statements.

1575E Insufficient space to insert jobs in appl aaaa.nnnn Explanation: The application record into which you are trying to insert a job

is close to its maximum size and cannot be extended enough to accommodate the new job definition. aaaa is the application name. nnnn is the application generation number.

System Action: The command is rejected. User Response: None. Hoever, it may be possible to increase the application

buffer size to provide headroom in the future generations.

1576E Insert request error: job jjjj already exists in appl aaaa.nnnn Explanation: An attempt was made to insert job jjjj into generation nnnn of

application aaaa. A job with this name already exists in that application.

Messages and Codes

ESP-5.4-MC-03 217

System Action: The command is rejected. User Response: None.

1577W Insert request does not contain job definitions Explanation: The statements provided in the APPLINS command do not define a

job. System Action: The command is rejected. User Response: Supply a valid job definition.

1578E Application aaaa.nnnn is already complete Explanation: An attempt was made to insert a job into generation nnnn of

application aaaa, but this application is already complete. System Action: The command is rejected. User Response: None.

1579E Circular reference in scheduling criteria Explanation: Selection criteria for a job are defined with references to other jobs,

and the reference chain leads back to the originating job. System Action: Application is not generated. User Response: Correct the job definition.

1580E Variable name is too long: exceeds nnnn bytes Explanation: The name of the variable that appears on a SETVAR statement is too long.

nnnn is the maximum length allowed for the name. System Action: Application is not generated. User Response: Correct the job definition.

1581E Variable value is too long: exceeds nnnn bytes Explanation: The string representing the value specified on a SETVAR statement

exceeds the maximum length allowed (nnnn bytes). System Action: Application is not generated. User Response: Correct the job definition.

1582E Extraneous data: dddd Explanation: A SETVAR statement contains unexpected data following the required

parameters. System Action: Application is not generated. User Response: Correct the job definition.

1583E Invalid keyword, wwww Explanation: WOBCMD command contains an unrecognized keyword wwww. System Action: The command is rejected. User Response: Correct and reenter the command.

1584E WOBCMD is not supported for tttt Explanation: WOBCMD command was entered against a workload object of type tttt,

which does not support the command. This can result from either misspelling the object type of from entering the command against a

218 ESP-5.4-MC-03

wrong object. System Action: The command is rejected. User Response: Correct and reenter the command.

1585W Job jjj, Appl aaa.ggg: No active CPU/NODE defined to resource manager Explanation: Job named jjj in generation ggg of application aaa has been given to

resource manager for resource allocation, but resource manager has no active CPU defined. Resource allocation cannot proceed.

System Action: The job remains waiting for resources. User Response: Define the active CPUs and verify their resource counts.

1586S xxxx Explanation: An error occurred while writing a record to scoreboard dump data set.

The text of the message fully describes the error. System Action: The CYBESUTS utility is terminated. User Response: This depends on the error.

1588E <function> <message> Explanation: An error was encountered in the CPI-C service named in <function>.

The detailed error information is provided in <message>. System Action: The operation fails. User Response: Analyze the error description and correct the problem.

The message may be truncated in some environments. In order to see the full message, try the same operation in a different environment. For example, if the message is truncated in an ISPF panel, it can be seen in full in TSO line mode.










Messages and Codes

ESP-5.4-MC-03 219

the job.

1592E No space in ATR to store data for object xxxxx Explanation: There was no free space in the ATR to store the data. System Action: The application is not built. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


1593E ???_Job xxxx in Appl yyyy, missing External Scheduler name Explanation: There was no External Scheduler name to identify where the work

was to run. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Provide the External Scheduler name. Then resubmit the job.

1594E ERROR OCCURRED READING INDEX ENTRY FOR JOB xxxx Explanation: An error occurred reading a job index data set entry for a job

identified as an external scheduler job in an application. The SCHEDULED parameter had been specified for the job.

System Action: This message would have been preceded by a message indicating the nature of the error. The external scheduler job is not marked as complete.

User Response: If the external scheduler job is complete, it will have to be manually marked complete in the application.

1595E Agent name xxxxxxxx does not exist Explanation: Agent xxxxxxxx referenced in an AGENT or MGRADDR command does not exist. System Action: The command is ignored. User Response: Correct the agent name, and reissue the command.

1596E External Scheduler yyyy already defined Explanation: During the processing of a LOADAGDF command, multiple EXTSCHED

statements were encountered. Only one EXTSCHED statement is allowed when defining the Manager and Agent topology.


User Response: Remove the extra EXTSCHED statement and re-enter the LOADAGDF command.

1597E Agent or CommChan yyyy not defined Explanation: An External Scheduler was defined without a prior definition of an

agent or a CommChan. An External Scheduler definition must be immediately preceded by the definition of an agent or a CommChan.

System Action: The entire agent definition is rejected. If an older definition was loaded earlier in the ESP session, it will remain in force.

User Response: Correct the error and load the agent definition again.

220 ESP-5.4-MC-03

1598E Format of TP checkpoint is obsolete. Explanation: At current maintenance level, TP Server requires checkpoint file

with modified format. System Action:

TP Server stops. User Response: If you wish to use the contents of current checkpoint file,

return to previous level of TP Server. Otherwise, start TP Server with PARM=TPFORM.

1599W Application aaaa start failed: LU uuuu assigned to bbbb Explanation: An attempt has been made to start application aaaa with LU name

uuuu. TP server already knows application bbbb to be using the named LU. Two applications cannot share an LU name.

System Action: The TPAPPL START command is aborted. User Response: Correct either application or LU name and reissue the command.

1600I RE-OPENING INFOSERV LOG DATASET xxxx AS NEW Explanation: A space shortage occurred (x37 abend) when Infoserv attempted to write

data to the log data set. System Action: The log data set is closed and reopened as new. The previous log

information is lost. User Response: None. If you require a larger amount of log data to be kept, shutdown

Infoserv, delete and allocate the log data set with more primary space (or larger extents) and restart Infoserv.

1601E UNABLE TO OPEN INFOSERV PRINT DATASET Explanation: An error occurred when attempting to reopen the Infoserv log data set

following the space abend. The previous message(s) will describe the error condition.

System Action: Logging is cancelled. User Response: Correct IFSPRINT card in Infoserv starting procedure and restart

Infoserv, if needed.

1602I OK Explanation: This message is issued in response to a conversationally entered

command INFOCOMM that was processed successfully. System Action: The processing continues. User Response: None.

1603E INVALID INFOCOMM FUNCTION Explanation: The specified INFOCOMM function is invalid and can not be interpreted. System Action: The command is ignored. Processing continues. User Response: Reissue the INFOCOMM command and specify the correct function name.

1604? SERVER DEFINITION DISPLAY Explanation: This message precedes the server status display requested by INFOCOMM

Messages and Codes

ESP-5.4-MC-03 221

DISPLAY command. System Action: Infoserv displays information on all (if server_id is omitted) or

specified by server_id server. User Response: None.

1605E SERVER xxx NOT DEFINED TO INFOSERV Explanation: An unknown server_id was specified in INFOCOMM command. System Action: The command is ignored. Processing continues. User Response: Specify correct server_id in INFOCOMM command. Use INFOCOMM DISPLAY

command to obtain a list of currently defined servers.

1606I OK Explanation: This message is issued in response to a convercationally entered

command INFOSERV that was processed successfully. System Action: The processing continues. User Response: None.

1607E TP SERVER FEEDBACK ERROR CODE xxxxxxxx Explanation: While processing an INFOSERV request a TP Server error was

encountered. System Action: The request is not processed. User Response: Ensure TP Server named in INFOSERV command is up and alive.

1608? INFOSERV RESPONSE ROUTER DISPLAY Explanation: This message precedes the router status display requested by INFOCOMM

DISPLAY command. System Action: Infoserv displays information on all (if server_id is omitted) or

specified by server_id server. User Response: None.

1609E GQM initialization failed, RC=X'nn' Explanation: Initialization of the GQM interface has failed. System Action: Infoserv continues without GQM capability. TPServer operations

will be unaffected. User Response: Contact Cybermation Technical Support.

1610E Communications not initialized. Explanation: Neither TP server nor GQM was initialized successfully. Infoserv

is either not configured to use communications, or additional messages are issued to explain the problem.

System Action: Infoserv stops. User Response: Correct the problem which is preventing proper start up.

1611E GQM error. Function=fff RC=rc Explanation: Unexpected return code rc was received from GQM when executing

the function fff. System Action: Processing continues. User Response: Report this code and your GQM configuration to Cybermation.

222 ESP-5.4-MC-03

1612E Infoserv request failed: unexpected return code from GQM. Function=ffff RC=rc

Explanation: Unexpected return code rc has been received from GQM when sending an Infoserv request.

System Action: Processing continues. User Response: Report this code and your GQM configuration to Cybermation.

1614E NAME SAME AS SPECIAL DAY IN xxxxxx CALENDAR: yyyyyyyy Explanation: A DEFHOL command has been issued for a day with the same name as a

special day in the same calendar or SYSTEM calendar. System Action: The command is not processed. User Response: Issue a LISTCAL command to show the special days defined in the

calendar in question or in SYSTEM.

1615E NAME SAME AS HOLIDAY IN xxxxxx CALENDAR: yyyyyyy Explanation: A DEFSPEC command has been issued for a day with the same name as a

holiday in the same calendar or SYSTEM calendar. System Action: The command is not processed. User Response: Issue a LISTCAL command to show the holidays defined in the

calendar in question or in SYSTEM.

1616E DATE AND TIME ALREADY SPECIFIED FOR SPECIAL DAY xxxxxxxx Explanation: A DEFSPEC command has been issued with the same special day name, date

and time as an already existing entry in the same calendar. System Action: The command is not processed. User Response: Issue a LISTSPEC command to show the dates and times defined for

the special day in question.

1617E Variable table tttt, User uuuuuuuu, access to event xxxx.yyyy not authorized

Explanation: VSET, VPUT, or VINCR command tried to trigger an event xxxx.yyyy defined for a variable in global variable table tttt. Either the event prefix specification (normally equivalent to a security user ID) xxxx is defined in the User Profile Definition Table, or the user ID uuuuuuuu is not authorized by SAF to perform this action. Note, if there are multiple variable triggers defined for the same variable in the global variable table, this message will be displayed only for the first variable trigger ID, that failed auhorization check, the others will be checked, but the error message, in case if failure, will not be issued.

System Action: The trigger is denied. User Response: Notify your installation security administrator.

1618E String too long Explanation: Global variable processing encountered a string longer than the

maximum of 255 characters. System Action: The command is rejected. User Response:

Messages and Codes

ESP-5.4-MC-03 223

1619E Trigger iiii already exists in table tttt Explanation: VTRDEF command was entered for table tttt with trigger id iiii, but

the table already contains a trigger with this id. System Action: The command is rejected. User Response: Use VTRDEF command with REPLACE option to create a new trigger with

existing id. To create a trigger with a different id, either select an id that does not exist or omit it, and ESP will assign a unique id.

1620E Variable table update request not valid from ESP proxy subsystem Explanation: A request was made to update a variable table under a proxy subsystem.

However, proxies have read-only access to variable tables. System Action: The request is rejected. User Response: Issue the request to the master ESP subsystem.

1621E Invalid global variable table access request xxxx Explanation: System Action: The request is rejected. User Response:

1622E Insufficient space in variable table xxxx for request Explanation: The named variable table is full. System Action: The request is rejected. User Response:

1623E Variable table xxxx not defined or access not authorized Explanation: System Action: The request is rejected. User Response:

1624E Global Variable Table xxxx already defined Explanation: System Action: The request is rejected. User Response:

1625E Global Variable Table xxxx not defined Explanation: System Action: The request is rejected. User Response:

1626E Variable xxxx not found Explanation: System Action: The request is rejected. User Response:

1627E No matches found or access not authorized Explanation: A generic VTLIST command returned no entries matching your query.

Either matching entries do not exist or you are not authorized to

224 ESP-5.4-MC-03

view them. System Action: User Response:

1628I Global Variable Table xxxx deleted Explanation: The variable table named xxxx has been successfully deleted. System Action: None User Response: None

1629E Error performing global variable processing on Table xxxx Explanation: System Action: The request is rejected. User Response:

1630E Variable xxxx error code n Explanation: System Action: The request is rejected. User Response:

1631E Variable xxxx Not authorized for requested access Explanation: System Action: The request is rejected. User Response:

1632E Variable xxxx not found on Table yyyyyy. Explanation: Specified variable is not found in table. System Action: The request is rejected. User Response:

1633E Variable xxxx not updated, old value mismatch Explanation: The variable was not updated because the old value specified in the

request did not match the current value of the variable. System Action: The request is rejected. User Response: Change the old value, making other changes as appropriate. Then

reissue the command.

1634E Variable xxxx locked Explanation: System Action: The request is rejected. User Response:

1635E Variable xxxx lock expired Explanation: System Action: The request is rejected. User Response:

1636E Variable xxxx not updated, table full Explanation:

Messages and Codes

ESP-5.4-MC-03 225

System Action: The request is rejected. User Response:

1637E Variable xxxx not numeric Explanation: System Action: The request is rejected. User Response:

1638E Variable xxxx function nn not supported Explanation: System Action: The request is rejected. User Response:

1639E Variable xxxx not defined Explanation: System Action: The request is rejected. User Response:

1640E Error retrieving REXX variable xxxx Explanation: System Action: The request is rejected. User Response:

1641E Variable xxxx not defined Explanation: System Action: The request is rejected. User Response:

1642E Error setting REXX variable xxxx Explanation: System Action: The request is rejected. User Response:

1643I Trigger defined/replaced in table xxxx ID yyyy Explanation: System Action: User Response:

1644E Trigger ID yyyy deleted in table xxxx Explanation: System Action: The request is rejected.

1645E Variable Trigger xxxx not found Explanation: A VTRDEL command was issued to delete the Variable Trigger named

xxxx. However, there is no such trigger in the specified Global Variable Table.

System Action: The request is rejected.

226 ESP-5.4-MC-03

User Response: Specify a valid trigger name.

1646E HOLIDAY WITH SAME NAME AND START DATE AND TIME ALREADY EXISTS: xxxxxx

Explanation: User is trying to specify a holiday with same name and start date and time as existing one in specified calendar.

System Action: The command is ignored. User Response: Determine cause of error, and reissue corrected command.



1648E Insufficient checkpoint space for global variable table trigger request Explanation: A change to a variable satisfied the conditions for a variable

trigger, but the ESP checkpoint did not have sufficient free space to hold the data describing the required action.

System Action: The event is not triggered. User Response: Investigate and correct the checkpoint-full condition.

1649E Unsupported encryption type Explanation: Support for the requested encryption algorithm is not installed. System Action: The request fails. User Response: Either use an available encryption algorithm or install the missing

component. DES encryption is always available.

1650E Invalid parameter passed to encrypt/decrypt routine Explanation: The encryption/decryption service routine detected a missing or

invalid parameter. System Action: The current action is aborted. User Response: This is most likely a code defect. Contact Cybermation support.

1651E Invalid length passed to encrypt/decrypt routine Explanation: The encryption/decryption service routine was passed an invalid

buffer length. System Action: The current action is aborted. User Response: This is most likely a code defect. Contact Cybermation support.

Messages and Codes

ESP-5.4-MC-03 227

1652E Error openong DD xxxxxxxx Explanation: An error occurred while opening the file associalted with DD name

xxxxxxxx. System Action: Processing ends. User Response: Check for other ESP or system messages explaining the error.

1653E xxxxxxxx record length invalid Explanation: The record length of the indicated file is invalid.

When using file level encryption, the output file record length must be equal to the input file record length rounded up to the next multiple of 8. When using file level decryption, the input file record length must be a multiple of 8.

System Action: Processing ends. User Response: Correct the error.

1680E DIV object allocate error, Dsname=<dsname> Explanation: An attempt to dynamically allocate a data set to be used as a Data

In Virtual (DIV) object failed. This message is normally preceded by message IKJ56228I explaining the reason for the dynamic allocation failure. <dsname> specifies the name of the data set.

System Action: The data set is not initilized as a Data In Virtual (DIV) object. If the data set to be allocated was the object of a NETQUEUE <dsname> command in the ESP/WM LOADNET initialization file, action message 3328A is issued to prompt for an END response to ignore the NETQUEUE <dsname> command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command.

User Response: If the data set to be allocated was the object of a NETQUEUE <dsname> command in the ESP/WM LOADNET initialization file, then either reply CANCEL to action message prompt 3328A to terminate ESP/WM, or re-enter the NETQUEUE <dsname> command specifying a valid existing Network Delivery Service (NDS) message queue data set (NETQUEUE data set). Then correct the NETQUEUE <command> in the LOADNET initialization file to specify a valid existing Network Delivery Service (NDS) message queue data set, and restart ESP/WM if it was terminated.

1681E Requested DIV object not allocated, DDname=<ddname> Explanation: A request to initialize a Data In Virtual (DIV) object failed because

the specified file was not allocated. <ddname> specifies the DD name of the file.

System Action: The file is not initialized as a Data In Virtual (DIV) object. User Response: None. Does not occur under ESP/WM.

1682E DIV object not found in catalog, Dsname=<dsname> Explanation: A request to initialize a Data In Virtual (DIV) object failed because

an entry in the catalog for the specified data set could not be found. <dsname> specifies the name of the data set.

228 ESP-5.4-MC-03

System Action: The data set is not initilized as a Data In Virtual (DIV) object. User Response: Should never happen. Contact Cybermation support.

1683E DIV object not VSAM linear data set, Dsname=<dsname> Explanation: A request to initialize a Data In Virtual (DIV) object failed because

the specified data set is not a VSAM linear data set. <dsname> specifies the name of the data set.

System Action: The data set is not initilized as a Data In Virtual (DIV) object. If the data set to be allocated was the object of a NETQUEUE <dsname> command in the ESP/WM LOADNET initialization file, action message 3328A is issued to prompt for an END response to ignore the NETQUEUE <dsname> command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command.

User Response: If the DIV object to be initialized was the object of a NETQUEUE <dsname> command in the ESP/WM LOADNET initialization file, then either reply CANCEL to action message prompt 3328A to terminate ESP/WM, or re-enter the NETQUEUE <dsname> command specifying a valid existing Network Delivery Service (NDS) message queue data set (NETQUEUE data set). Then correct the NETQUEUE <command> in the LOADNET initialization file to specify a valid existing Network Delivery Service (NDS) message queue data set (NETQUEUE data set), and restart ESP/WM if it was terminated. The NETQUEUE data set must be a VSAM linear data set.

1684W xDiv Init|Open|Close|Extend|Save, <description> Explanation: An internal Data In Virtual (DIV) object API request has been issued.

An existing condition prevented the request from being serviced. <description> describes the condition that prevented the Data In Virtual (DIV) object API request from being serviced.

System Action: The Data In Virtual (DIV) object API request is not processed. User Response: Attempt to diagnose the condition that prevented the Data In Virtual

(DIV) object API request from being serviced and correct it if possible.

1685E xDiv Init|Open|Close|Extend|Save, <description> Explanation: An internal Data In Virtual (DIV) object API request has reulted in an

error condition. <description> describes the error condition.

System Action: The Data In Virtual (DIV) object API request is not processed. User Response: Attempt to diagnose the problem from the error description and correct

it if possible. If unable to, contact Cybermation support.

1686S xDiv Init|Open|Close|Extend|Save, <description> Explanation: An internal Data In Virtual (DIV) object API request has reulted in a

severe error condition. <description> describes the error condition.

System Action: The Data In Virtual (DIV) object API request is not processed. User Response: Attempt to diagnose the problem from the error description and correct


Messages and Codes

ESP-5.4-MC-03 229

1687E DIV core request failed, Size=<bytes> Explanation: A request for address space virtual storage to accomodate a Data In

Virtual (DIV) object failed. <bytes> specifies the size in byte units of the address space vitrual storage request.

System Action: The Data In Virtual (DIV) object is not created as requested. User Response: If possible, either increase the amount of virtual storage available

to the address space by increasing the REGION operand in the JCL JOB or EXEC statement, or decrease the size of the Data In Virtual (DIV) object. If unable to resolve the problem, contact Cybermation support.

1688E xDiv Save|Extend|Close rejected, Div object closed, Dsname=<dsname> {, Dspace=<dspname>}

Explanation: An internal API request for a Data In Virtual (DIV) object could not be serviced because the Data In Virtual (DIV) object has been closed. <dsname> specifies the data set name of the Data In Virtual (DIV) object. <dspname> specifies the data space name of the Data In Virtual (DIV) object.

System Action: The Data In Virtual (DIV) API request is not serviced. User Response: Should never happen. Contact Cybermation support.

1689E Div Identify|Access|Map|Save|Unidentify, Return=<rc>, Reason=<reason>, Dsname=<dsname>{, Dspace=<dspname>}

Explanation: A Data In Virtual (DIV) request error has occurred. <rc> specifies the Data In Virtual (DIV) error return code. <reason> specifies the Data In Virtual (DIV) error reason code. <dsname> specifies the data set name of the Data In Virtual (DIV) object. <dspname> specifies the data space name of the Data In Virtual (DIV) object.

System Action: The Data In Virtual (DIV) request is not serviced. User Response: If possible, diagnose and correct the Data In Virtual (DIV) error.

If unable to do so, contact Cybermation support.

1700W JOB xxxx IN APPL aaaa IS NOW IN MANUAL HOLD WAITING RELEASE

Explanation: A Job, identified by jjjj, in the specified application is now ready for submission, but is currently in manual hold. This message indicates that the job needs to be released from manual hold in order to execute.

System Action: None. User Response: When the job is eligible to be submitted, use the AJ command (or A

option of the CSF) to remove the job from manual hold.

1701I USER PROFILE DEFINITION TABLE LOADED Explanation: In response to a LOADUPDT statement or command, the user profile

definition table has been loaded.

230 ESP-5.4-MC-03

System Action: The data in the user profile definition table will be used. User Response: None

1702I USER PROFILE DEFINITION TABLE ACTIVE, LOADED FROM xxxx(yyyy)

Explanation: This message identifies the active user profile definition table. System Action: None User Response: None

1703I SAF Options: Explanation: ESP is listing the SAF security option settings. System Action: None. User Response: None.

1704E User profile data set not specified, needed when SAF security has been requested

Explanation: The ESP initialization statements included a SAFCLASS statement, requesting that host based SAF security be used for ESP internal security. However, this requires that a user profile data set be defined. This was not performed.

System Action: The ESP subsystem will not initialize. User Response: Code a LOADUPDT statement in the initialization data set. A sample

user profile member supplied in the ESP sample library. Once this is done, restart the ESP subsystem.

1705E Command xxxx not available within REXXON/REXXOFF Explanation: A restricted statement was entered within a REXXON/REXXOFF pair. The

command "xxxx" cannot be executed from a REXX environment. The following commands cannot be entered within REXXON/REXXOFF. ACF2EXIT, ALTCKPT, ALTQUEUE, APPLBUF, APPLFILE, AUDITLOG, AUTHSTR, CKPT, EXHFILE, GMTCHECK, INDEX, ISCOPT, JOBINDEX, MAXLRECL, QTRACE, QUEUE, RESFILE, RUNMODE, SAFCLASS, SCHDFILE, SMFINT, SMFREC, STRACE, SUBSYS SVC, SYSID, TIMECHK, TIMEZONE, TRAKFILE, USERDEF

System Action: The ESP subsystem is not initialized. User Response: Remove the "xxxx" command from the initialization statements or move

the statement out of the REXXON/REXXOFF pair. If you wish to execute the statement with variable data, where the variable data is generated by the REXX code, you can pass the variable to a CLANG variable, then include the statement after the REXXOFF, using the CLANG variable. For example, if a REXX function called PLEXNAME() returned a SYSPLEX ID which you wanted to substitute into the QUEUE file name, you could code the following.

Messages and Codes

ESP-5.4-MC-03 231

REXXON "PLEXNM='"PLEXNAME()"'" REXXOFF QUEUE %PLEXNM..ESP.QUEUE

1706I Agent Definition Table loaded Explanation: In response to a LOADAGDF statement or command, the multi-platform

agent definition table has been loaded. System Action: The data in the multi-platform agent table will be used. User Response: None

1707I Agent Definition Table active, loaded from xxxx(yyyy) Explanation: This message identifies the active multi-platform agent definition

table. System Action: None User Response: None

1708I SAF Class: Explanation: ESP is listing the SAF class and resource options. System Action: None. User Response: None.

1709W Duplicate definitions for time zone xxxx Explanation: A TIMEZONE parameter was encountered whose name is the same as that

of a previously processed TIMEZONE parameter. System Action: The TIMEZONE is processed. However, when processing, ESP will use the

instance of this name whose zone number is lowest, and ignore any duplicates with higher zone numbers.

User Response: Correct or remove the line in the ESPPARM data set.

1710I Backing out to xxxx Explanation: In response to a BACKOUT command, ESP is performing processing

required to allow an ESP version xxxx system to execute using the same data sets as the current version of ESP.

System Action: The backout processing is performed. After the processing is completed, ESP will perform SHUTDOWN processing and terminate.

User Response: Start ESP version xxxx.

1711E Not authorized to Event Initiator Class nnn Explanation: A request was made to assign a non-zero Event initiator class to

an Event. The user making the request does not have at least READ access to the resource EVENTINITCLASS.nnn, where nnn is the three digit Event initiator class.

System Action: The request is failed and the Event definition is not saved. User Response: Remove the non-zero Event initiator class from the request or obtain

READ access to the resource.

232 ESP-5.4-MC-03

1712E Invalid EICLASS value specified Explanation: During Event definition, an attempt was made to assign a non-zero

Event initiator class to an Event using the EICLASS keyword. The EICLASS value was outside the support range of 0 to 255.

System Action: The Event definition is not saved. User Response: Correct the EICLASS value.

1713I Event class nn deleted, xx TDR(s) moved to class 0 Explanation: In response to an EICLASS DELETE command, nn Time Driven Requests

(TDRs) scheduled to execute Event initiator class xx were rescheduled to execute in Event initiator class 0.

System Action: The TDRs will be executed in Event initiator class 0 at the scheduled time.


1714I Event multiprogramming level for class nn set to xx Explanation: In response to an EICLASS SET command, the maximum number of Event

initiators available for use by class nn was set to xx. System Action: Processing continues. User Response: None.

1715C Event Initiator Display Explanation: In response to an EICLASS DISPLAY command, the Event initiator status

is displayed. For each defined Event initiator class a count of the currently defined, maximum allowed and currently active Event initiators is displayed. For each Event initiator a count of Events and jobs processed by that Event initiator is displayed as well as the current status of the Event initiator. Finally, the number of free Event initiators is displayed. A free Event initiator is one which was assigned to an Event initiator class which has been deleted.


1716E Invalid CLASS value nnn specified Explanation: An EICLASS command was issued with a CLASS value nnn. nnn is

outside the acceptable range of 0 to 255 for SET and DISPLAY operations or outside the acceptable range of 1 to 255 for DELETE operations.

System Action: The EICLASS command is rejected. User Response: Correct the CLASS value and retry the command.

1717E Invalid MPL value nn specified Explanation: An EICLASS SET command was entered with an MPL value of nn. nn is

outside the acceptable range of 1 to 16. System Action: The EICLASS command is rejected. User Response: Correct the MPL value and retry the command.

Messages and Codes

ESP-5.4-MC-03 233

1718E xxxx value required for SET or DELETE Explanation: An EICLASS SET or DELETE command was entered without a required

keyword xxxx. System Action: The EICLASS command is rejected. User Response: Supply the missing keyword xxxx and retry the command.

1722E Expedite policy name xxxx invalid Explanation: An EXPEDITE command specifies an invalid expedite policy name. An

expedite policy name must be 1-8 alpha-numeric, national ($ # @) or underscore (_) characters. In addition, for the LIST option, it may contain imbedded asterisk (*) and/or a terminating hyphen (-) wild card character(s).

System Action: Processing continues. User Response: Re-enter the EXPEDITE command specifying a valid expedite policy name.

1723C EXPEDITE Command Options Explanation: Response to EXPEDITE HELP command. System Action: Displays EXPEDITE command options. User Response: None.

1724C EXPEDITE {xxxx }LIST Explanation: Response to "EXPEDITE" or "EXPEDITE xxxx LIST" command. xxxx

specifies an expedite policy name which may include imbedded asterisks and/or a terminating hyphen as wild card characters.

System Action: Lists the requested expedite policies and there respective criteria and action specifications. If xxxx is omitted, all expedite policies are listed.


1725I {No expedite policies|xxxx expedite polic{y|ies} not} defined Explanation: Response to "EXPEDITE" or "EXPEDITE xxxx LIST" command. xxxx

specifies an expedite policy name which may include imbedded asterisks and/or a terminating hyphen as wild card characters. No expedite policies meeting the command input criteria are defined.


1726E Expedite policy xxxx already exists, cannot be added Explanation: Response to EXPEDITE xxxx ADD command. xxxx specifies an expedite

policy that already exists, and therefore cannot be added. System Action: Processing continues. User Response: If the criteria and/or action specifications of expedite policy xxxx

need to be altered, then issue the "OPER EXPEDITE xxxx ALTER" command. Then, if the change(s) need to be permanent, modify the "EXPEDITE xxxx ADD" command in the ESPPARM initialization file, if it exists.

234 ESP-5.4-MC-03

1727I Expedite policy xxxx {added|altered|deleted} Explanation: Response to EXPEDITE xxxx ADD, ALTER or DELETE command. xxxx

specifies an expedite policy name. The requested EXPEDITE command completed successfully.


1728W Expedite policy xxxx specifies no {criteria{ nor actions}|actions} Explanation: Response to "EXPEDITE xxxx ADD" or "EXPEDITE xxx ALTER" command.

Expedite policy xxxx is correctly defined, but it specifies no criteria (OVERDUE or CRITICAL_PATH keywords) and/or no actions (CLASS, PRIORITY, START, SRVCLASS or PERFORM keywords). If expedite policy xxxx specifies no actions, then any associated ESP application job cannot be expedited. If expedite policy xxxx specifies no criteria, but at least one action, then any associated ESP can be expedited, but only manually (via the "XP" CSF line command or the "AJ yyyy EXPEDITE" command, where yyyy specifies the job name), provided the expedite action(s) apply to the job's current state (submitted or executing).

System Action: Processing continues. User Response: Add any required criteria and/or actions to expedite policy xxxx with

the "OPER EXPEDITE xxxx ALTER" command.

1729E Expedite policy xxxx not defined Explanation: Response to "EXPEDITE xxxx ALTER" or "EXPEDITE xxxx DELETE" command. System Action: Processing continues. User Response: If necessary, re-enter the EXPEDITE command specifying an existing

expedite policy. To list all expedite policies, enter the command: OPER EXPEDITE

1730C JES2RLSE Command Options Explanation: Response to JES2RLSE HELP command. System Action: Displays JES2RLSE command options. User Response: None.

1731I JES2 release specified as {earlier than V2R4|V2R4 or later} Explanation: Response to JES2RLSE or JESRLSE LIST command.

If the JES2 release is specified as earlier than V2R4, then ESP will issue JES2 commands using the old pre-V2R4 syntax. If the JES2 release is specified as V2R4 or later, then ESP will issue JES2 commands using the new V2R4 and later syntax.


1732E EXPEDITE LIST option cannot specify criteria and/or actions. Explanation: Response to EXPEDITE or EXPEDITE LIST command.

An EXPEDITE command that defaults to or specifies the LIST option

Messages and Codes

ESP-5.4-MC-03 235

has specified one of the following keyword operands: OVERDUE, NOOVERDUE, CRITICAL_PATH, NOCRITICAL_PATH, ANY, ALL, ESP_PRIORITY, NOESP_PRIORITY, CLASS, NOCLASS, PRIORITY, NOPRIORITY, START, NOSTART, SRVCLASS, NOSRVCLASS, PERFORM or NOPERFORM. All of these operands are incompatible with the LIST option.

System Action: Processing continues. User Response: If the LIST option was intended, then re-enter the EXPEDITE command

without any criteria and/or action specification(s). If the ADD or ALTER option was intended, then re-enter the EXPEDITE command specifying ADD or ALTER, with the requested criteria and/or action specification(s).

1733E EXPEDITE ALTER option must specify at least one criterion or action Explanation: Response to EXPEDITE ALTER command. An EXPEDITE command that

specifies the ALTER option must, but does not specify at least of the following keyword operands: OVERDUE, NOOVERDUE, CRITICAL_PATH, NOCRITICAL_PATH, ANY, ALL, ESP_PRIORITY, NOESP_PRIORITY, CLASS, NOCLASS, PRIORITY, NOPRIORITY, START, NOSTART, SRVCLASS, NOSRVCLASS, PERFORM or NOPERFORM. All of these operands are incompatible with the LIST option.

System Action: Processing continues. User Response: Re-enter the EXPEDITE ALTER command specifying at least one criterion

or action.

1734E INVALID COMMAND PARAMETER ENTERED Explanation: The TP Server command has an invalid format or invalid parameter. System Action: The TP Server command is not processed. User Response: Correct the command and try again.

1735E TP INITIALIZATION TERMINATED Explanation: The LOCAPPL command has an invalid format or invalid parameter. System Action: The LOCAPPL command is not processed. User Response: Correct the command and try again.

1736E INVALID CHECKPOINT DATASET NAME ENTERED Explanation: The TPCKPT command has an invalid CHECKPOINT data set name. System Action: The TPCKPT command is not processed. User Response: Correct the command and try again.

1737I THE CHECKPOINT MANAGER IS ALREADY STARTED Explanation: A TPCKPT command has already been processed. System Action: The TPCKPT command is ignored. User Response: None.

1738E APPLICATION xxxx DOES NOT EXIST Explanation: The TPAPPL command has an invalid application name.

236 ESP-5.4-MC-03

System Action: The TPAPPL command is not processed. User Response: Correct the command and try again.

1739E ABEND CODE = xxxx Explanation: The TPATTACH command cannot attach a module. This message follows

message 1448 and displays the appropriate LOAD error code. System Action: The TPATTACH command is not processed. User Response: Please contact CYBERMATION for further assistance.

1740E TPTEST ERROR FROM TP SERVER = xxxx Explanation: The TPTEST command cannot send a test transaction to a partner

application. System Action: The TPTEST command is not processed. User Response: Please contact CYBERMATION for further assistance.

1741I THE DEFAULT LOGON MODE IS xxxx Explanation: The TPSTATS command displayed the default logon mode. System Action: None. User Response: None.

1790E TAPETRAK command invalid for non-tracking ESP/WM Explanation: A TAPETRAK command has been issued to an ESP/WM subsystem that is not

tracking jobs, i.e. an ESP/WM subsystem that specifies "SMFINT ON" in its ESPPARM initialization file statement, or defaults to "SMFINT ON".

System Action: Processing continues. User Response: If the TAPETRAK command is specified in the ESPPARM initialization

file of the non-tracking ESP/WM subsystem, then remove it.

1791C TAPETRAK HELP Explanation: Response to TAPETRAK HELP command. System Action: Processing continues. User Response: None.

1792E LIST and {NO}EXCLUDE mutually exclusive Explanation: A TAPETRAK command has been issued with the incompatible operands

LIST and EXCLUDE or NOEXCLUDE. System Action: Processing continues. User Response: Re-issue the TAPETRAK command with compatible operands.

To display TAPETRAK command options, enter: TAPETRAK HELP

1793E Specified TAPETRAK option(s) only permissible from a console Explanation: A TAPETRAK command has been issued from a device that is not a

console, but specifies one or more of the following operands - ALL, REAL, NOVIRTUAL, EXCLUDE, NOEXCLUDE These operands may only be specified in the ESPPARM initialization file or from a console device.


Messages and Codes

ESP-5.4-MC-03 237

User Response: Re-issue TAPETRAK command from a console if authorized to do so.

1794C TAPETRAK Tape Tracking: Real {No}Virtual {Exclude: nnnn{-nnnn} {nnnn{-nnnn}} ...}

Explanation: Response to successful TAPETRAK command execution. Displays current tape tracking status. nnnn specify tape device numbers.


1795E RESOURCE NAME CAN NOT CONTAIN WILD CARD CHARACTERS ON THIS OPERATION

Explanation: Wild card characters (asterisk and dash) are not allowed with the ADD operand.

System Action: The processing of this command is aborted. User Response: Correct the command and retry it.

1796W 'n' jobs are missing from resfile, details in audit log Explanation: ESP WM found a discrepancy between application file and resource file:

n jobs are missing from resfile although their application records show them as waiting for resources or holding resources. This can be caused by a preceding system crash or by a resform. The individual jobs are listed in the audit log.

System Action: The reference to resource file is removed from application records for affected jobs.

User Response: Review the job list. Jobs whose records were lost while they were waiting for resource will need a resubmission.

1799W The execution frequency of event XXXX.XXXX is higher than allowed by the THRESH operand.

Explanation: When generating the scheduled activity data set, the SADGEN job encountered an event with two successive runs that are closer to each other than the threshold specified on THRESH operand.

System Action: The specific event was not reported in the SADGEN data set. User Response: Decrease the THRESH operand value to include more scheduled

instances of the event in the SADGEN data set.

1800I ABOVE ERROR OCCURRED ON FOLLOWING STATEMENT Explanation: The statement which follows appears in the ESP proc being executed. System Action: User Response: Check the previous message for an explanation of the error.

1801I n RECORDS WRITTEN TO SAD FILE Explanation: The specified number of records were written to the SAD file as the

result of the SADGEN request. System Action: Processing continues. User Response: None required.

238 ESP-5.4-MC-03

1802I UNABLE TO ALLOCATE WORK FILE Explanation: There is insufficient space to allocate work files. System Action: User Response: Wait until there is sufficient space available and then retry.

1803E INSUFFICIENT BUFFER STORAGE Explanation: There is insufficient memory available to complete the operation. System Action: The requested operation is not performed. User Response: If this problem persists, recycle the ESP subsystem.

1804C JOBINFO FOR xxxx Explanation: This is the JOBINFO listing. System Action: User Response:

1806E UNABLE TO PROCESS INPUT FILE Explanation: The data set specified in the LSAR command could not be processed.

This could be caused by the specification of an undefined file or an I/O error on the file.

System Action: The command is not processed. User Response: Re-specify the command with a data set that can be processed.

Consult any previous messages at the terminal or on the system messages of the batch job to determine the exact nature of the error.

1807E ILLEGAL INPUT FILE Explanation: The data set specified in the MODEL command was not a scheduled

activity data set. System Action: The command processing is terminated. User Response: Re-specify the command with a data set that is a scheduled activity

data set.

1808I APPLFILE slot number recovered from index, retrying I/O Explanation: System Action: User Response:

1809I Slot number is valid, unable to read above APPL Explanation: System Action: User Response:

1810I Error still occurred after second read with refreshed slot number Explanation: System Action: User Response:

Messages and Codes

ESP-5.4-MC-03 239

1811I Unable to locate index entry for this APPL generation Explanation: System Action: User Response:

1812E INSUFFICIENT SPACE IN APPL RECORD TO INSERT JOB xxxx INTO APPL yyyy

Explanation: The application record does not have enough free space to insert the new job.

System Action: The job is not inserted. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


1813E UNABLE TO LOCATE JOB xxxx FOR UPDATE IN APPL yyyy Explanation: The ESP subsystem was unable to locate Job "xxxx" in Application




1814W UNABLE TO LOCATE APPL xxxx.nn SLOT yyyy FOR APPL PROCESSING REQUEST

Explanation: An application command (such as AJ) has been issued for an application which is no longer active.

System Action: The command is ignored. User Response: This message should only be received when special diagnostic material

has been supplied by Cybermation. When you receive this message, please contact Cybermation Technical support. If this message was received as the result of an incorrect application name and/or generation number being entered, then re-issue the command with the correct information.

1815W APPLICATION MANAGER HAS FOUND A DUPLICATE SLOT CONDITION


1816W EXISTING APPL xxxx.nn SLOT yyyy Explanation: System Action: User Response:

240 ESP-5.4-MC-03

1817W NEW APPL xxxx.nn SLOT yyyy Explanation: System Action: User Response:

1818W NO ENTRIES FOUND TO MATCH YOUR SELECTION CRITERIA Explanation: No jobs matched the LISTAPPL command criteria. System Action: User Response:

1819E INVALID JOBNAME SPECIFICATION xxxx Explanation: The parameters to the AJ command were invalid. System Action: The AJ command was not processed. User Response: Correct the parameters and try again.

1820E APPLICATION NAME MISSING Explanation: The application name is missing from the AJ command. System Action: The AJ command is not executed. User Response: Add an application name and try again.

1821W NO FUNCTION SPECIFIED, COMMAND IGNORED Explanation: No function name (e.g., COMPLETE, HOLD, etc) was specified on the AJ

command. System Action: The AJ command was not executed. User Response: Add a function name and try again.

1822E No jobs were eligible out of the nn jobs in Subappl xxxx Explanation: No job names were found that matched the job specification in the AJ

command. System Action: The AJ command is ignored. User Response: Re-issue the AJ command with a valid job specification.

1823W NO RESET TIMES SPECIFIED, COMMAND IGNORED Explanation: In an AJ RESET command, neither EARLYSUB, LATESUB, LATEEND nor

DROPEXEC were specified. System Action: The AJ command was not executed. User Response: Correct the command and try again.

1824E INVALID APPLICATION SPECIFICATION xxxx Explanation: The application name in the LISTAPPL command must be no longer than

eight characters, and may contain the '*' or '-' wildcard characters. It may be followed by a period and a relative generation number.

System Action: The LISTAPPL command was not executed. User Response: Correct the application name and try again.

1825E INVALID REQUEST CODE ISSUED TO CYBES037 Explanation: An internal ESP error has occurred.

Messages and Codes

ESP-5.4-MC-03 241

System Action: The SADLINK was not completed. User Response: Please contact Cybermation for further assistance.

1826E INVALID REQUEST CODE ISSUED TO CYBES038 Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

1827E INVALID SCBUR REQUEST CODE DETECTED Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

1828E INCORRECT KEY LENGTH SPECIFIED FOR SCHEDULE FILE Explanation: The ESPPARM data set specified a Schedule data set which had an



1829I SCHEDULE FILE DATA SET HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED

Explanation: The Schedule data set contained no control record. A control record is always the first record in the data set.


1834I SCHEDULE FILE DATA SET EMPTY, WILL FORMAT Explanation: An empty Schedule data set was detected. This is expected the first

time the data set is used. System Action: ESP formats the data set and continues processing. User Response: None, unless the Schedule data set is not supposed to be empty.

1839E REQUIRED SCOREBOARD ENTRY NOT FOUND Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

1840E SCHEDFILE RECORD NOT FOUND Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

1842E Scoreboard request not valid from a proxy subsystem Explanation: The user has requested a CSF function from a proxy subsystem. System Action: The request is ignored.

242 ESP-5.4-MC-03

User Response: Scoreboard API requests can only be made from a proxy subsystem in a a master/proxy complex if the proxy subsystem acts as a gateway to the master subsystem through the XCF ROUTING service.

1849W NO PARAMETERS, COMMAND IGNORED Explanation: A command was entered with no parameters when parameters were

expected. System Action: The command is ignored. User Response: Reenter the command with the correct parameters.

1850E ERROR SCANNING COMMAND, RC=nn Explanation: A problem was encountered while parsing the command line. System Action: The command is ignored. The user is prompted for a new command. User Response: If the problem persists, notify your support personnel.

1851W xxxx SUBSYSTEM NOT ACTIVE Explanation: A request was made to the ESP subsystem while it was not active. System Action: The request is not processed. User Response: Wait for the subsystem to be restarted.

1852E ERROR SCANNING MODEL COMMAND, RC=nn Explanation: A problem was encountered while parsing a MODEL command. System Action: The command is ignored. The user is prompted for a new command. User Response: System routine IKJPARS returned error code nn.


1853W MODELLING NOT ACTIVE Explanation: An attempt was made to enter a MODELLING command when the MODEL



1854W MODELLING NOT ACTIVE Explanation: An attempt was made to enter a MODELLING command when the MODEL



Messages and Codes

ESP-5.4-MC-03 243


When nn=12: invalid parameters passed to parse from CP. nn=16: No space available. nn=20: Validity check routine termination. nn=24: An error in input parameters was detected in the IKJPARS2 load module. nn=28: A line drop condition was detected and IKJPTGT (PUTGET I/O service routine) or IKJPUTL (PUTLINE I/O service routine) set return codes of 24 and 32 respectively.

If the problem persists, notify your support personnel.

1856I File already exists Explanation: A Putfile command was entered with the subparameter Putnew that specifies for Pu

to check for the existence of the dsname in the Putfile command and if found iss message without overwriting existing data.

System Action: The pds dataset member is not overwritten. User Response: If it is desired to overwrite an exising member then reissue the Putfile command

but without the Putnew parameter.

1859E APPLICATION PROCESSING IS NOT ACTIVE Explanation: A user issued a command related to the application processing function

of ESP. That function is not active. System Action: The command is not processed. User Response: The application processing function must be activated. This requires

the tracking facility as well as at least one APPLFILE data set.

1860E APPLFILE xxxx IS CLOSED Explanation: An application record retrieval failed because the required APPLFILE

was closed. System Action: The record is not retrieved. User Response: Determine the reason the file was closed. Retry when the file becomes

available.

1861E YOUR AUTHORITY IS INSUFFICIENT FOR ACCESS, OR APPLICATION xxxx NOT FOUND

Explanation: A requested application record could not be retrieved for one of two reasons. It is either not defined, or the user requesting it did not have the appropriate authority to access it. The application must belong to the user, or to a group to which the user is connected with sufficient access.

System Action: The record is not retrieved. User Response: Ensure the application name was specified correctly or grant the user

sufficient access to the application record.

244 ESP-5.4-MC-03


1863E xxxx NOT VALID WITHIN AN EVENT DEFINITION Explanation: A subcommand was entered that is not valid within an EVENT definition. System Action: The subcommand is ignored. User Response: Terminate the EVENT definition before reentering the subcommand.

1864E xxxx NOT VALID OUTSIDE OF AN EVENT DEFINITION Explanation: A subcommand was entered that is only valid within an EVENT

definition. System Action: The subcommand is ignored. User Response: Specify the subcommand within an EVENT definition.






1868E Error scanning command, RC=nn Explanation: A problem was encountered while parsing the GENFLOW command line. System Action: The command is ignored. The user is prompted for a new command. User Response: System routine IKJPARS returned error code nn.


Messages and Codes

ESP-5.4-MC-03 245


1870E COMMAND xxxx INVALID IN USER PROFILE DEFINITION TABLE Explanation: A User Profile Definition Table contained an invalid command. System Action: The User Profile Definition Table is not loaded. User Response: Correct the table and reissue the LOADUPDT command.

1871E xxxx Explanation: An error occurred allocating or opening a User Profile Definition

Table. The message text is self describing. System Action: The User Profile Definition Table is not loaded. This message is

followed by message 1872E. User Response: Take action according to the following message.

1872E ABOVE ERROR OCCURRED OPENING USER PROFILE DEFINITION TABLE

Explanation: A LOADUPDT command encountered an error allocating or opening a User Profile Definition Table. The preceding message will have described the error.


command.

1873E INVALID COMMAND SYNTAX DETECTED IN LINE nn OF USER PROFILE DEFINITION TABLE

Explanation: A User Profile Definition Table contained a statement with invalid syntax.

System Action: The User Profile Definition Table is not loaded. User Response: Correct the table definition and reissue the LOADUPDT command.

1874E ABOVE ERROR OCCURRED ON LINE nn OF USER PROFILE DEFINITION TABLE

Explanation: An error was detected in a User Profile Definition Table statement. The error is described in a preceding message. This message indicates the line number containing the error.

System Action: The User Profile Definition Table is not loaded. User Response: Correct the error and reissue the LOADUPDT command.

1875E INVALID WILDCARD RANGE, xxxx Explanation: A WILDCARD statement in a User Profile Definition Table had an invalid

character range. System Action: The User Profile Definition Table is not loaded. User Response: Correct the error and reissue the LOADUPDT command.

1876E TOO MANY WILDCARDS DEFINED, LIMIT IS 60 Explanation: A User Profile Definition Table was being loaded. The table contained

more than 60 WILDCARD statements. System Action: The User Profile Definition Table is not loaded.

246 ESP-5.4-MC-03

User Response: Correct the error and reissue the LOADUPDT command.

1877E INVALID MODEL SPECIFICATION xxxx Explanation: An invalid model specification was entered in a PROFILE entry in a

User Profile Definition Table. System Action: The User Profile Definition Table is not built. User Response: Correct the error and reissue the LOADUPDT command.

1878E MODEL SPECIFICATION EXCEEDS 8 CHARACTERS Explanation: A model name was being constructed in a PROFILE entry in a User

Profile Definition Table. The combination of parameters caused a name of more than 8 characters to be constructed.

System Action: The User Profile Definition Table is not loaded. User Response: Correct the error and reissue the LOADUPDT command.

1879E ABOVE ERROR OCCURRED READING USER PROFILE DEFINITION TABLE

Explanation: An error occurred while reading in a User Profile Definition Table. The error is described in a preceding message.

System Action: The User Profile Definition Table is not loaded. User Response: After the error is corrected, reissue the LOADUPDT command.

1880E INSUFFICIENT CHECKPOINT SPACE TO QUEUE JOB xxxx IN APPL yyyy FOR SUBMISSION

Explanation: The application processor could not obtain enough checkpoint space to queue a job submission request.

System Action: The job is not queued for submission. It will be selected a little later.

User Response: The checkpoint space situation should be monitored.

1881E Invalid request code issued to Resource Manager Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

1882E Invalid Resource Manager Anchor Block address passed to Resource Manager Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

1883E Insufficient access authority for requested function Explanation: You are not authorized to define or manage resources. System Action: The command is ignored. User Response:

1884E No Resfile data set name specified Explanation: No RESFILE command was found in the ESP initialization parameters. System Action: Resource management is not activated.

Messages and Codes

ESP-5.4-MC-03 247

User Response: Add a RESFILE command to the ESP initialization parameters.

1885E Resfile DIV Identify error nn Explanation: An error was encountered while opening the RESFILE data set. System Action: ESP resource management is not available. User Response: The error number in the message is the two-byte reason code found in

register zero. These reason codes are listed in the IBM manual which describes the DIV macro.

1886E Resfile DIV Access error nn Explanation: An error was encountered while accessing the RESFILE data set. System Action: ESP resource management is not available. User Response: The error number in the message is the two-byte reason code found in


1887E Resfile DIV Map error nn Explanation: An error was encountered while mapping the RESFILE data set. System Action: ESP resource management is not available. User Response: The error number in the message is the two-byte reason code found in


1888E Insufficient Extended Private Area to Map the Resfile Explanation: There is not enough memory to enable ESP's resource management

feature. System Action: Resource management is not activated. User Response: Recycle ESP with a larger region size.

1889E Resfile data set xxxx contains invalid data Explanation: The file named in the RESFILE initialization parameter is not a

valid resource file. System Action: Resource management is not activated. User Response: Correct the RESFILE command in the ESP initialization parameters to

point to a valid resource file, and then recycle. Alternatively recycle ESP with the RESFORM option to format the named data set.

1890I Resfile data set xxxx will be formatted Explanation: The file named in the RESFILE initialization parameter will be

formatted as a new resource file. System Action: The Resource file is formatted. User Response: None.

1891E Resfile DIV Save error nn Explanation: A data-in-virtual save operation onto the RESFILE has failed. System Action: User Response: Refer to the IBM DIV documentation for an explanation of this DIV

error code.

248 ESP-5.4-MC-03

1892E Resfile DIV UnIdentify error nn Explanation: A data-in-virtual unidentify operation onto the RESFILE has failed. System Action: User Response: Refer to the IBM DIV documentation for an explanation of this DIV

error code.

1893E Resfile DIV UnAccess error nn Explanation: A data-in-virtual unaccess operation onto the RESFILE has failed. System Action: User Response: Refer to the IBM DIV documentation for an explanation of this DIV

error code.

1894E Resfile DIV UnMap error nn Explanation: A data-in-virtual unmap operation onto the RESFILE has failed. System Action: User Response: Refer to the IBM DIV documentation for an explanation of this DIV

error code.

1896W Node xxxx not found Explanation: In a RESOURCE statement, the value of the NODE parameter specified an

undefined node name. System Action: The resource is not defined. User Response: Add a definition for the node.

1897I CPU xxxx not found Explanation: In a RESOURCE statement, the value of the CPU parameter specified an

undefined CPU name. System Action: The resource is not defined. User Response: Add a definition for the CPU.

1898I Resource xxxx not found Explanation: The RESOURCE DELETE statement specifies a resource which has not yet

been defined. System Action: User Response: Correct the RESOURCE statement, or remove it.

1899I CPU xxxx not defined on Node yyyy Explanation: In a RESOURCE statement, the value of the CPU parameter specified a

CPU which is not on the specified NODE. System Action: The resource is not defined. User Response: Change the RESOURCE statement to refer to the proper CPU or the proper

NODE.

1900S Resource file full Explanation: There is not sufficient free space in the rsource file to process

the current resource request System Action: The resource manager terminates with ABENDU4001.

Messages and Codes

ESP-5.4-MC-03 249

User Response: Increase the SIZE value on the RESFILE init parameter and restart with RESFORM. Ensure that the space allocation for the linear VSAM object is large enough to hold the requested size.

1901E The maximum of nn Resources has been reached Explanation: Too many resources have been defined. System Action: The resource was not defined. User Response: Increase the maximum possible number of resources by changing the

RESFILE command in the ESP initialization parameters. The MAXRES parameter on this command specified the maximum number of resources that can be defined.

1902E Resource xxxx already defined Explanation: A RESOURCE ADD statement names a resource that has already been

defined. System Action: The resource is not redefined. User Response: Remove either one of the RESOURCE ADD statements for this resource.

1903I Resource xxxx defined Explanation: The resource named in the RESOURCE ADD statement has been successfully

defined. System Action: User Response:

1904C Resource Display Explanation: Following this message will be the result of a RESOURCE LIST command. System Action: User Response:

1905I No matching Resources found Explanation: A RESOURCE LIST command was issued, but no matching resource names

were found in the resource file. System Action: The command is ignored. User Response: Re-issue the RESDEF LIST command with a valid resource name

specification.

1906I No Resources defined Explanation: A RESOURCE LIST command was issued, but no resources have been defined

in this resource file. System Action: User Response: Restart ESP with a different resource file, or define some resources

in this resource file.

1907W Resource xxxx not deleted, it is in use Explanation: A resource cannot be deleted while some job is waiting for it. System Action: The resource was not deleted. User Response: Wait until no jobs are waiting for this resource, and then delete it.

250 ESP-5.4-MC-03

1908I Resource xxxx updated Explanation: The resource definition has been updated as a result of a RESOURCE SET

command. System Action: User Response:

1909I Node xxxx defined Explanation: A new node has been successfully defined. System Action: User Response:

1910I Node xxxx deleted Explanation: A Node definition was successfully removed from the Resfile after a

NODE xxxx DELETE command was issued. System Action: None. The request was successful. User Response: None.

1911I Node xxxx modified Explanation: The node definition has been modified as a result of a NODE SET


1912C Node Display Explanation: A display of the definition of this node will follow. System Action: User Response:

1913I Resource xxxx deleted Explanation: A resource has been deleted as a result of a RESOURCE DELETE command. System Action: The resource has been deleted. User Response: None.

1914W No matching Nodes found Explanation: There are no nodes whose name matches the specification given in the

NODE LIST command. System Action: None. User Response: Correct the node name specification and try again.

1915W Node xxxx not defined Explanation: The node specified in a NODE SET or NODE DELETE command has not been

defined. System Action: None. User Response: Correct the node name and try again.

1916E Node xxxx already defined Explanation: The node name specified in a NODE ADD command has already been

Messages and Codes

ESP-5.4-MC-03 251

defined. System Action: The node was not redefined. User Response: Correct the node name and try again.

1917I CPU xxxx defined Explanation: The CPU ADD statement has successfully defined a CPU. System Action: User Response:

1918I CPU xxxx deleted Explanation: A CPU delete request was successful in removing all references to a

CPU from the Resfile. System Action: None. The request was successful. User Response: None.

1919I CPU xxxx modified Explanation: The CPU SET command has successfully changed the definition of this

CPU. System Action: User Response:

1920C CPU Display Explanation: Following this message is a display of the definition of a CPU. System Action: User Response:

1921I No matching CPUs found Explanation: A CPU DISPLAY command was entered, but no CPUs were found that match

the specification. System Action: No CPUs were displayed. User Response: Correct the CPU name specification and try again.

1922E The maximum of nn has been reached Explanation: Too many CPUs have been defined. System Action: The CPU was not defined. User Response: Increase the maximum possible number of CPUs by changing the RESFILE

command in the ESP initialization parameters. The MAXCPU parameter on this command specified the maximum number of CPUs that can be defined.

1923W CPU xxxx not defined Explanation: The CPU specified in a CPU SET or CPU DELETE command has not been

defined. System Action: None. User Response: Correct the CPU name and try again.

1924E CPU xxxx already defined Explanation: A CPU ADD statement names a CPU that has already been defined.

252 ESP-5.4-MC-03

System Action: None. User Response: Remove either one of the CPU ADD statements for this CPU.

1925W No Nodes defined Explanation: In a CPU ADD command, no NODE parameter was specified, and no nodes

have yet been defined. System Action: The CPU was not defined. User Response: Define at least one node before this CPU definition.

1926W Node xxxx not found for job yyyy Explanation: System Action: User Response:

1927W CPU xxxx not found for job yyyy Explanation: System Action: User Response:

1928W Resource xxxx not found for job yyyy Explanation: System Action: User Response:

1929W No UCBs found for unit name xxxx Explanation: The DEVICE parameter of a RESOURCE ADD statement specified a unit name

with which no UCBs are associated. System Action: User Response: Correct the unit name with the RESOURCE SET DEVICE(...) statement and

try again.

1933E Resource name xxxx is invalid Explanation: The resource name in the RESOURCE ADD command is not valid. A valid

name is up to 44 characters in length, beginning with an alphabetic character. It may contain imbedded periods, or hyphens, so any MVS data set name is valid. Each qualifier must begin with an alphabetic character, and be no more than 8 characters long.

System Action: The command is rejected. User Response: Specify a valid name.

1934I ABOVE ERROR OCCURRED ON FOLLOWING STATEMENT Explanation: The following statement in the ESP procedure was in error. System Action: The statement was not processed. User Response: Check the previous message for further information.

1935I xxxx Explanation: An error has been detected while processing this statement. System Action: The statement was not processed.

Messages and Codes

ESP-5.4-MC-03 253

User Response: Check the previous messages for further information.

1936E Cannot change available count for renewable resource xxxx. Explanation: A RESDEF SET command was issued to change the available count

for a renewable resource. However, this count cannot be changed for this kind of resource, unless USERMOD 75 is activated.

System Action: The resource is not updated. Any other parameters on the command are ignored.

User Response: None

1939E Error scanning command, RC=nn Explanation: A problem was encountered while parsing the command line. System Action: The command is ignored. The user is prompted for a new command. User Response: System routine IKJPARS returned error code nn.



1940E DATA SET TRIGGERING NOT RESTARTED, RESYNCH IN PROGRESS

Explanation: The operator issued a DSTRST RESTART command, but a data set trigger resynchronize operation initiated by CYBESUDI is in progress.

System Action: The command is not executed. User Response: Wait for the resynch to complete, then reissue your request. If you

are absolutely certain that there is not a resynch in progress, reissue the command, specifying UDIRESET to cause the resynch indicator to be turned off.

1941I No entries found to match your selection criteria Explanation: No applications were found that matched the specification on the

GENPROJ command. System Action: The GENPROJ command was not executed. User Response: Correct the Application specification and re-issue the command.

1942I Application xxxx.nn no longer on APPLFILE Explanation: The GENPROJ command refers to an Application which is no longer

available on the APPLFILE. System Action: The GENPROJ command was not executed. User Response: Correct the Application specification and re-issue the command.

1943W Invalid Application specification xxxx Explanation: The Application name specified to the GENPROJ command was not valid.

The application name must be no longer than eight characters, and may

254 ESP-5.4-MC-03

contain the '*' or '-' wildcard characters. It may followed by a period and a relative generation number.

System Action: The GENPROJ command is terminated with no further processing. User Response: Correct the application name and try again.

1944W Requested generation of Application xxxx not found Explanation: The GENPROJ command requested a specific generation of an Application.

The Application generation did not exist. System Action: The GENPROJ command was not executed. User Response: Use the LISTAPPL command to confirm the existence of the specified

Application and generation.

1945W GMT TIME xxxx ON yyyy zzzzaaaa bbbb Explanation: The GMTCHECK parameter was specified in the initialization parameter

deck. A discrepancy was found between the Local and GMT time. Message 0897W precedes this message for local time.

System Action: This message is followed by message 0898A. User Response: Respond to message 0898A.



1949E JOB INDEX AND TRACKFILE BOTH NEEDED FOR APPLFILE OPTION

Explanation: Either the job index or job tracking files were specified in the initialization parameters. Both are required for the Applfile option to work.

System Action: Processing terminates. User Response: Update the initialization parameter data set to define both data sets.

Restart ESP.

1950E QUEUE DATA SET NEEDED FOR APPLFILE OPTION Explanation: The Applfile function was requested by the inclusion of the track file

and job index data sets in the initialization parameters. The queue data set was not defined.

System Action: Processing terminates. User Response: The queue data set should be defined by adding the QUEUE parameter to

the initialization parameter data set.

1951I xxxx Explanation: In debug mode, the subsystem initialization module is being invoked

Messages and Codes

ESP-5.4-MC-03 255

directly by ESP. System Action: User Response:

1952E SUBSYSTEM ID xxxx IN USE BY ANOTHER SUBSYSTEM Explanation: The subsystem ID is being used by some system other than ESP. System Action: ESP will not start. User Response: Choose a different subsystem ID for ESP, and then restart it.

1953I QUEUE DATA SET HAS BEEN DAMAGED AT OP REQ Explanation: The queue data set has been purposely corrupted by the @CRPTQUE


1954I THERE ARE NO FREE ELEMENTS IN QUEUE Explanation: The @CRPTQUE command was issued, but there are no queue elements to be

corrupted. System Action: User Response:

1955W xxxx Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

1956I OK Explanation: The previously entered command has completed successfully. System Action: User Response:

1957I SHUTDOWN COMMAND ACCEPTED Explanation: A SHUTDOWN command has been entered, and ESP is commencing shutdown

processing. System Action: User Response:

1958I ALREADY QUIESCED Explanation: A QUIESCE command was entered, but ESP is already quiesced. System Action: User Response:

1959I QUIESCING Explanation: ESP is entering quiesce mode. System Action: User Response:

256 ESP-5.4-MC-03

1960I RESTARTING Explanation: ESP is resuming normal operation, after having been quiesced. System Action: User Response:

1961W NOT QUIESCED Explanation: A RESTART command was entered, but ESP was not quiesced. System Action: The command is not executed. User Response: None.

1962I DATA SET TRIGGERING RESUMED Explanation: A RESUME DSTRIG command was just entered. System Action: ESP has resumed data set triggering. User Response:

1963I DATA SET TRIGGERING NOT SUSPENDED Explanation: A RESUME DSTRIG command was just entered, but data set triggering had

not been suspended. System Action: User Response:

1964I DATA SET TRIGGERING ALREADY SUSPENDED Explanation: The DSTRST command specified SUSPEND, but data set triggering is

already suspended. System Action: User Response:

1965I DATA SET TRIGGERING SUSPENDED Explanation: Data set triggering is temporarily suspended, until a DSTRST RESUME

command is issued. Until that time, all data set triggers will be ignored.

System Action: Data set triggering is suspended. User Response: To resume data set triggering, issue the DSTRST RESUME command.

1966I DATA SET TRIGGERING RESTARTED Explanation: Data set triggering is restarted, and all triggers that had been

detected since the quiesce will now be processed. System Action: Data set triggering is restarted. User Response:

1967I DATA SET TRIGGERING NOT QUIESCED Explanation: The DSTRST command specified RESTART, but data set triggering is not

quiesced. System Action: User Response:

Messages and Codes

ESP-5.4-MC-03 257

1968I DATA SET TRIGGERING ALREADY QUIESCED Explanation: The DSTRST command specified QUIESCE, but data set triggering is

already quiesced. System Action: User Response:

1969I DATA SET TRIGGERING QUIESCED Explanation: Data set triggering is now quiesced, and all data set triggers that

are detected will be saved until triggering is restarted. System Action: Data set triggering is quiesced. User Response: To restart data set triggering, and process all triggers that have

been detected since this quiesce, issue the DSTRST RESTART command.

1970I DATA SET TRIGGER LOGGING DEACTIVATED Explanation: Data set triggers are no longer being written to the system log. System Action: Data set trigger logging is deactivated. User Response: To resume logging of data set triggers, issue the DSTRST LOG command.

1971I DATA SET TRIGGER LOGGING NOT ACTIVE Explanation: The DSTRST command specified NOLOG, but logging of data set triggers

is not active. System Action: User Response:

1972I DATA SET TRIGGER LOGGING ALREADY ACTIVE Explanation: The DSTRST command specified LOG, but logging of data set triggers is

already active. System Action: User Response:

1973I DATA SET TRIGGER LOGGING ACTIVATED Explanation: Data set triggers are now being logged. Whenever a data set is closed

and an event is triggered, a message will be placed in the system log naming the data set and the event.

System Action: Data set triggers are now being logged. User Response: To stop logging of data set triggers, issue the DSTRST NOLOG command.

1974I DATA SET TRIGGERING {SUSPENDED|ACTIVE}{ (QUIESCED)}, {NO}LOG

Explanation: This message is in response to a DSTRST command without operands. It displays the current status of data set triggering.


1975I QUPDATE REQUEST QUEUED Explanation: The QUPDATE command has been accepted. System Action: ESP will do a JES status and update the P-Node queue information.

258 ESP-5.4-MC-03


1976I QUPDATE REQUEST ALREADY QUEUE Explanation: A QUPDATE command is already in progress. System Action: User Response:

1977I ESP release xxxx status Explanation: This message introduces the display of ESP processing status. System Action: User Response: The messages that follow will describe ESP's processing status.

1978I EVENT SCHEDULING {QUIESCED|ACTIVE} Explanation: This message indicates the status of ESP's event scheduling function. System Action: User Response:

1979I DATA SET TRIGGERING {SUSPENDED|ACTIVE} {(QUIESCED)} {(RESYNCHING)}

Explanation: This message indicates the status of ESP's data set triggering function.


1980I EVENTSET xxxx IS IN SUSPENDED STATE Explanation: This event has been suspended with the SUSPEND command. System Action: User Response: This event may be resumed by issuing the RESUME command.

1981I ROSCOE PROC NAME NOT SET Explanation: In response to a ROSCOE command without operands, this message

indicates that the ROSCOE proc name has not yet been established. System Action: User Response: Specify the name of a ROSCOE proc with the ROSCOE command.

1982I ROSCOE PROC SET TO xxxx Explanation: In response to a ROSCOE command without operands, this message

indicates the name of the ROSCOE proc. System Action: User Response:

1983C DEFAULT USER Explanation: This message introduces the response to the LDFLTU command. System Action: User Response:

1984W NO DEFAULT USER DEFINED Explanation: In response to a LDFLTU command, this message indicates that no

Messages and Codes

ESP-5.4-MC-03 259

default user has been defined. System Action: User Response:

1985C TRACKMODEL BUFFER DISPLAY Explanation: This message introduces the response to the LISTJTML command. System Action: User Response:

1986W Dependency loop found at xxxx releasing yyyy in appl aaaa Explanation: The Application Manager found that the dependency between xxxx and

yyyy is part of a successor loop where predecessor ultimately depends on the successor. xxxx and yyyy are qualified work load object names, and aaaa is the application name and generation number.

System Action: Calculation of advanced due-out times, critical path and anticipated ending times will not be done for the affected application. If the application's dependency structure is modified, e.g. by inserting a job or by forcing a job complete, calculation of advanced due-out times and anticipated ending times will be attempted again. Critical path calculation will be permanently disabled for this generation.

User Response: Correct the dependency loop.

1988W Owner zzzz of Event xxxx.yyyy no longer defined to ESP. Execution continues Explanation: ESP is executing an Event owned by a Userid that has been deleted

from ESP's User Definition File. System Action: Execution continues. User Response: Either reinstate the Userid or update the Event. After updating the

event become the new owner.

1989E xxxx Explanation: This error occurred while trying to validate the user that was

associated with a time-delayed event. System Action: User Response:

1990E EVENT xxxx.yyyy NOT EXECUTED DUE TO ABOVE I/O ERROR Explanation: A time-delayed event was not executed because errors were encountered

while attempting to validate the user id associated with this event. System Action: The event was not executed. User Response: Refer to the previous ESP1989 message for further information on this

error.

1991W EVENT ALTERATION SUPPRESSED BY INSTALLATION EXIT Explanation: The installation ESP exit has prevented this event from being altered. System Action: The event is not altered. User Response:

260 ESP-5.4-MC-03

1992I INSUFFICIENT DATA SPACE TO UPDATE EVENT xxxx.yyyy Explanation: No further alterations can be made to this event, as its record in the

event file is now full. System Action: The event was not altered. User Response:

1993E EVENTSET ID xxxx NOT FOUND Explanation: The ALTEVENT command specified an invalid EVENTSET name. System Action: The event was not altered. User Response: Correct the EVENTSET parameter and try again.

1994W UNABLE TO QUEUE DIRECTLY TO SYSTEM xxxx Explanation: An Event was defined or triggered to execute on another system. The

QUEUE data set was unavailable so the local ESP system was unable to queue it to the requested system.



1995W SYSTEM xxxx NOT MEMBER OF SHARED QUEUE Explanation: An Event was defined or triggered to execute on another system. The

designated system was not sharing the QUEUE data set. The local ESP system was unable to queue it to the requested system.



1996W EVENT DEFINITION SUPPRESSED BY INSTALLATION EXIT Explanation: System Action: User Response:

1997W EVENT DATASET WITH ID xxxx NOT FOUND Explanation: The DEFERRED parameter in a LISTSCH command specified an event data

set that is not defined to ESP. System Action: No entries are listed. User Response: Correct the DEFERRED parameter and try again.

1998W THERE ARE NO EVENTS ON THE OVERDUE QUEUE Explanation: A LISTSCH OVERDUE command was issued, but there are no overdue events. System Action: User Response:

1999W NO EVENTS HELD IN CLASS xxxx Explanation: A LISTSCH HELD command was issued, but there are no held events on the

Messages and Codes

ESP-5.4-MC-03 261

specified hold class. System Action: User Response:

2000E DUPLICATE ISCDEF COMMAND ISSUED Explanation: More than one ISCDEF command appeared in the initialization stream. System Action: Each ISCDEF except the first is ignored. User Response: Remove the extraneous ISCDEF command(s).

2001E ISCDEF STATEMENT MUST PRECEDE ISCXMTR Explanation: An ISCXMTR statement was encountered for an NJE job tracking

transmitter, but no ISCDEF statement had been processed. System Action: The ISCXMTR statement is ignored. User Response: Ensure that the ISCDEF statement precedes any ISCXMTR statement that

defines an NJE job tracking transmitter.

2002E INVALID FUNCTION CODE PASSED TO CYBIS000 Explanation: An internal logic error has occurred. System Action: The Inter-System communication process is not started. User Response: Contact Cybermation for assistance.

2003E SUBSYSTEM FUNCTION ERROR CODE xx, SYSOUT RECEIVER TERMINATING

Explanation: ESP received an unexpected subsystem error code from JES. System Action: The receive portion of this ISC terminates. User Response: Contact Cybermation for assistance.

2004E SUBSYSTEM REQUEST ERROR CODE xx, SYSOUT RECEIVER TERMINATING

Explanation: ESP received an unexpected return code from JES. System Action: The receive portion of this ISC terminates. User Response: Contact Cybermation for assistance.

2005E ERROR ENCOUNTERED BY SYSTEM RECEIVER Explanation: A synchronous I/O error occurred reading an ISC data set from JES.

Message 2006E will follow describing the actual error. System Action: Processing of this transmission terminates. ISC waits for the next

input file. User Response: Contact Cybermation for assistance.

2006E <variable text describing the I/O error> Explanation: A synchronous I/O error occurred reading an ISC data set from JES. System Action: Processing of this transmission terminates. ISC waits for the next


262 ESP-5.4-MC-03

2007E INVALID TRANSACTION RECORD ENCOUNTERED BY SYSOUT RECEIVER

Explanation: ISC received a record from JES which does not have the correct header information in it.

System Action: Processing of this transmission terminates. ISC waits for the next input file.

User Response: Contact Cybermation for assistance.

2008E ON DATA SET xxxxxxxx Explanation: This message provides the name of the data set being processed when

the error causing message 2007E to be issued was detected. System Action: Processing of this transmission terminates. ISC waits for the next


2009E CHAR=cccc

HEX=xxxx Explanation: Inter System Communication module received bad transmission. Character

format is cccc, hex - xxxx. System Action: Processing of this transmission terminates. ISC waits for the next

receiving. User Response: If problem persists contact Cybermation support for assistance.

2010E DATASET xxxx IS NOT SEQUENTIAL Explanation: An LSAR command without the TAPEPULL keyword was specified. However,

the output data set was not a sequential data set. System Action: The SAD data set cannot be created. User Response: Allocate a sequential data set and reissue the command.

2011E WILDCARDS NOT ALLOWED IN SUBAPPL Explanation: A LAP command with the SUBAPPL keyword was specified. However, the

SUBAPPL parameter value contained wildcard characters. System Action: The command is ignored. User Response: Re-issue the corrected command.

2012E MANUAL JOB CANNOT BE QUALIFIED Explanation: A JOB statement within an application specified a qualified job name

with the MANUAL parameter. Manual jobs cannot be qualified. System Action: The application is not processed. User Response: Remove the qualification from the manual job.

2013E {DE}SELECTED SUBAPPL xxxx NOT DEFINED Explanation: The selected or deselected sub-application was not defined in the ESP

procedure with a SUBAPPL statement. System Action: The ESP procedure will not run.

Messages and Codes

ESP-5.4-MC-03 263

User Response: Either define the sub-application with a SUBAPPL statement, or delete the erroneous {DE}SELECT statement.

2014E SUCCESSOR LOOP DETECTED: xxxxyyyy Explanation: In an application, a job (JOBA) specified JOBB as a pre-requisite.

JOBB specified JOBA as a pre-requisite which creates a loop situation. System Action: The application is not processed. User Response: Correct the dependencies and re-run the application.

2015W OWNER is valid only for links and tasks, ignored Explanation: OWNER was specified for a workload object other than a link or a

task. The user cannot assign ownership of mainframe or agent-run jobs.

System Action: The erroneous keyword is ignored. Processing continues. User Response: Correct the job definition by removing the OWNER keyword.

2016I nn jobs will be selected for rerun: j1, j2,.... Explanation: This is a response to RerunM command. It shows jobs that match the

root job list and are not currently waiting to be readied. System Action: N/A User Response: Review the job list. If it is followed by a prompt, reply to it.

2017E Parm string too long, up to nnn bytes allowed Explanation: The rerun parameter string coded in RerunM command exceeds the

allowed limit. System Action: RerunM command is aborted. User Response: Reenter the command with correct parm string.

2018E Application <name.gen> is already complete Explanation: RerunM command was entered for a completed application.

Jobs in completed applications cannot be resubmitted. System Action: RerunM command is aborted. User Response: N/A.

2019I nn jobs selected for rerun Explanation: This is a response from ESP subsystem after it processed RerunM command.

The number of jobs is reported back to the user. System Action: N/A. User Response: N/A.

2020E ERROR ALLOCATING SYSOUT DATA SET FOR SYSOUT TRANSMITTER xxxxxxxx

Explanation: ESP was unable to dynamically allocate a SYSOUT data set to write inter-system tracking data to be sent to ISC node 'xxxxxxxx'. The message from dynamic allocation precedes this message.

System Action: The ISC transmitter terminates. User Response: Contact Cybermation for assistance.

264 ESP-5.4-MC-03

2021E <variable message text> Explanation: This message provides details of the open error causing message

2022E to be issued. System Action: The ISC transmitter terminates. User Response: Contact Cybermation for assistance.

2022E ERROR OCCURRED OPENING DATA SET FOR SYSOUT TRANSMITTER xxxxxxxx

Explanation: ESP was unable to open a SYSOUT data set to write inter-system tracking data to be sent to ISC node 'xxxxxxxx'. Message 2021E describing the error precedes this message.

System Action: The ISC transmitter terminates. User Response: Contact Cybermation for assistance.

2023E Insufficient storage for rerun parameters Explanation: RerunM command could not modify the application record: there was not

enough room for rerun parameters. System Action: RerunM command is aborted. User Response: The limit on the application record size is determined by the value of

APPLBUF parameter when an application is generated. This error may mean that your installation needs a larger APPLBUF. For the current application, rerunning individual jobs may succeed even if RerunM fails.

2024E Request denied: insufficient authority Explanation: The request to application manager failed an authorization check. System Action: The request is denied. User Response: Ask the security administrator for help.

2029I SYSOUT TRANSMITTER xxxxxxxx HAS SPUN A DATA SET WITH nnn RECORDS

Explanation: The ISC transmitter has created a data set to be sent to ISC node 'xxxxxxxx'. There are 'nnn' transaction records in the data set. This message is produced if the SPINMSG option is specified on the ISCXMTR statement.


2067W LONGNAME is invalid for this job type, ignored Explanation: LONGNAME was specified for a workload object other than an agent-run

job. System Action: The erroneous keyword is ignored. Processing continues. User Response: Correct the job definition by removing the LONGNAME keyword.

2068W Job xxxxxxxx, value specified by SCOPE parameter is higher than maximum allowed, set to maximum of 546 hours.

Explanation: User specified a SCOPE parameter value in the JOB/JOBATTR statement

Messages and Codes

ESP-5.4-MC-03 265

which exceeds the maximum that could be accommodated by ESP control blocks.

System Action: The value in the SCOPE parameter is set to 546 hours. Processing continues.

User Response: Correct the value in the SCOPE parameter as needed.

2100C INET Command Options Explanation: Response to an "INET HELP" command.

Lists all valid "INET" command options. System Action: Processing continues. User Response: None.

2101E INET command missing Explanation: An "INET" command was issued without any parameters. System Action: Processing continues. User Response: Enter an "INET" command with valid parameters.

Or enter "INET HELP", "INET H" or "INET ?" for a list of "INET" command options.

2102E INET xxxx command invalid Explanation: The parameter immediately following "INET" in an "INET" command is

invalid. System Action: Processing continues. User Response: Enter an "INET" command with valid parameters.


2103E INET xxxx object missing Explanation: An "INET xxxx" command was entered that required at least one

additional parameter. System Action: Processing continues. User Response: Enter the "INET xxxx" command with valid parameters.


2104E INET xxxx object yyyy invalid Explanation: Parameter 'yyyy' in the command "INET xxxx yyyy" is invalid for the

command "INET xxxx". System Action: Processing continues. User Response: Enter an "INET xxxx" command with valid parameters.


2105E INET xxxx not an initialization command Explanation: An "INET" command was issued while a Cybermation product's TCP/IP

component was still initializing. The command cannot be processed until TCP/IP initialization is complete. Note that some "INET" commands can be issued during TCP/IP initialization while others cannot.

266 ESP-5.4-MC-03

System Action: Processing continues. User Response: Remove the "INET" command from the initialization parameters.

2106I TCP/IP={IBM({HPNS|IUCV}), Job=xxxxxxxx|Interlink(TCPaccess), API=yyyy, DNR=zzzz}

Explanation: Response to an "INET DISPLAY TCPIP" command. Displays the current TCP/IP stack (IBM's HPNS, IBM's IUCV or Interlink Software's TCPaccess) and its job name if IBM or its API and DNR subsystem names if Interlink Software.


2107E INET SET HOST_CACHE TTL interval missing Explanation: Response to "INET SET HOST_CACHE" or "INET T HC" command. The

command entered did not contain the required TTL (Time To Live) interval in seconds.

System Action: The command is ignored and processing continues. User Response: Re-enter the "INET SET HOST_CACHE" or "INET T HC" command specifying

a valid TTL (Time To Live) interval in seconds, i.e. a number within the range 0-99999999. For example: INET SET HOST_CACHE TTL(3600)

2108C Host Cache Explanation: Response to an "INET DISPLAY HOST_CACHE" command.

Displays TCP/IP host cache host names and corresponding IP addresses. System Action: Processing continues. User Response: None.

2109I Host cache empty, TTL (time to live) = 30 seconds. Explanation: Response to an "INET DISPLAY HOST_CACHE", "INET D HC",

"INET FLUSH HOST_CACHE" or "INET FL HC" command. System Action: None if processing "INET DISPLAY HOST_CACHE" or "INET D DC" command.

Host cache is flushed (deleted) if processing "INET FLUSH HOST_CACHE" or "INET FL HC" command.


2110I Host cache flushed Explanation: Response to an "INET FLUSH HOST_CACHE" command. System Action: Processing continues. User Response: None.

2124I Host cache time to live interval set to nnnn seconds Explanation: Response to "INET SET HOST_CACHE" or "INET T HC" command. The TTL

(Time To Live) interval has been set to the indicated value. System Action: None. User Response: None.

Messages and Codes

ESP-5.4-MC-03 267

2125E INET QUERY HOST object missing Explanation: Response to "INET QUERY HOST" or "INET Q H" command. The command

entered did not contain the name of the host whose IP address was being requested.

System Action: The command is ignored and processing continues. User Response: Re-enter the "INET QUERY HOST" or "INET Q H" command specifying a

valid TCP/IP host name.

2126E INET QUERY HOST object xxxx invalid Explanation: Response to "INET QUERY HOST" or "INET Q H" command.

The command entered contained an improper TCP/IP host name. System Action: The command is ignored and processing continues. User Response: Re-enter the "INET QUERY HOST" or "INET Q H" command specifying a

valid TCP/IP host name.

2127I Host xxxx not found Explanation: Response to "INET QUERY HOST" or "INET Q H" command. The host name

could not be resolved to an IP address. System Action: None. User Response: None.

2128I Host xxxx, Address nnn.nnn.nnn.nnn Explanation: Response to "INET QUERY HOST" or "INET Q H" command. The host name

was resolved to the indicated IP address. System Action: None. User Response: None.

2131E INET PURGE TASK object missing Explanation: An "INET PURGE TASK" command was issued without specifying the task ID. System Action: Processing continues. User Response: To display all the current TCP/IP task IDs, enter the command

"INET DISPLAY ACTIVE". If a task's TCP/IP sockets are to be purged, enter the command "INET PURGE TASK xxxx" where "xxxx" is the task ID. *** Warning **** "INET PURGE TASK" should be used with caution.

2132E INET PURGE TASK object xxxx invalid Explanation: Parameter 'xxxx' in the command "INET PURGE TASK xxxx' specifies an

invalid task ID. System Action: Processing continues. User Response: To display all the current TCP/IP task IDs, enter the command

"INET DISPLAY ACTIVE". If a task's TCP/IP sockets are to be purged, enter the command "INET PURGE TASK xxxx" where "xxxx" is the task ID. *** Warning ****

268 ESP-5.4-MC-03

"INET PURGE TASK" should be used with caution.

2133I Default TCP close option set to {reset|shutdown} Explanation: Response to "INET DISPLAY CLOSE", "INET D CL", "INET SET CLOSE" or

"INET T CL" command. The current default TCP close option is displayed.


2134E INET SET CLOSE option (SHUTDOWN|RESET) missing Explanation: Response to the "INET SET CLOSE" or "INET T CL" command, which sets

the default TCP close option to SHUTDOWN (graceful close) or RESET (hard close).

System Action: None. Processing continues. User Response: To display the current default TCP close option, enter one of the

following commands - INET DISPLAY CLOSE INET D CL If required, enter one of the following commands - INET SET CLOSE SHUTDOWN INET T CL S INET SET CLOSE RESET INET T CL R

2135E TCP/IP not initialized Explanation: An "INET" command was issued while a Cybermation product's TCP/IP

component was still initializing. The command cannot be processed until TCP/IP initialization is complete.

System Action: Processing continues. User Response: Wait for TCP/IP initialization to complete and re-issue the command.

2136S TCP/IP InitCall issued under subtask Explanation: A TCP/IP initialization call was issued in a Cybermation product under

a subtask. System Action: Task is abended with code U2910. User Response: Internal logic error. Call Cybermation Technical Support.

2137W TCP/IP stack set to HPNS, requested IUCV is obsolete Explanation: A Cybermation product request to set its TCP/IP stack to IUCV was

issued. Under ESP/WM, the TCPIP command in the ESPPARM initialization file specifies IUCV. Under ESP/WSS, the TCPIP command in the WSSPARM initialization file specifies IUCV, or the start-up parameters specify TCPIUCV. IUCV has been obsolete since V3R1 of IBM's TCP/IP and is therefore no longer supported by Cybermation.

System Action: The Cybermation product sets its TCP/IP stack to IBM's HPNS instead of IUCV.

Messages and Codes

ESP-5.4-MC-03 269

User Response: Under ESP/WM, the TCPIP command in the ESPPARM initialization file should be changed to specify IBM or HPNS instead of IUCV, or removed in order to default to IBM/HPNS. Under ESP/WSS, the TCPIP command in the WSSPARM initialization file should be changed to specify IBM or HPNS instead of IUCV, or removed so as to default to IBM/HPNS. Under ESP/WSS, the TCPIUCV parameter should be changed to TCPIBM or TCPHPNS, or removed in order to default to IBM/HPNS.

2138E INET SET BIND option (REUSEADDR|NOREUSEADDR) missing Explanation: Response to the "INET SET BIND" or "INET T B" command, which sets the

TCP bind option to REUSEADDR or NOREUSEADDR. Setting the TCP bind option to NOREUSEADDR will cause a TCP bind to fail with an "Address already in use" condition if TCP connections using the local port are active.

System Action: None. Processing continues. User Response: To display the current default TCP bind option, enter one of the

following commands - INET DISPLAY BIND INET D B Then, if required, enter one of the following commands - INET SET BIND REUSEADDR INET T B R INET SET BIND NOREUSEADDR INET T B N

2139I TCP bind option set to {no }reuse address Explanation: Response to "INET DISPLAY BIND", "INET D B", "INET SET BIND" or

"INET T B" command. The current TCP bind option is displayed.


2140C TCP/IP Activity Explanation: Response to "INET DISPLAY ACTIVE" command.

Displays socket ID, task ID, local port, remote port and remote IP address of each active TCP/IP socket. The TCP/IP stack is IBM's IUCV.


2141I No TCP/IP activity Explanation: Response to "INET DISPLAY ACTIVE" command.

The TCP/IP stack is IBM's IUCV. System Action: Processing continues. User Response: None.

270 ESP-5.4-MC-03

2142E INET PURGE ID not supported under IBM IUCV TCP/IP Explanation: Response to "INET PURGE ID" command.

An individual pending socket function cannot be purged under IBM's IUCV TCP/IP.


2143E INET PURGE TASK object xxxxxx not found Explanation: Response to an "INET PURGE TASK xxxxxx" command.

The specified task "xxxxxx" does not exist or does not have any active TCP/IP sockets. The TCP/IP stack is IBM's IUCV.

System Action: Processing continues. User Response: To display all the current TCP/IP task IDs, enter the command

"INET DISPLAY ACTIVE". If a task's TCP/IP sockets are to be purged, enter the command "INET PURGE TASK xxxx" where "xxxx" is the task ID. *** Warning **** "INET PURGE TASK" should be used with caution.

2144I INET PURGE TASK xxxxxx complete Explanation: Response to an "INET PURGE TASK xxxxxx" command.

All active sockets for the specified task have been purged. The TCP/IP stack is IBM's IUCV.


*** Warning **** "INET PURGE TASK" should be used with caution.

2145E Invalid port number xxxx Explanation: An invalid port number was passed to the TCP/IP component of a

Cybermation product. This is normally the result of an incorrect user port number parameter specification. The TCP/IP stack is IBM's IUCV.

System Action: The TCP/IP function terminates. User Response: Correct the TCP/IP port number parameter.

2146E Invalid port number length nn Explanation: The length of a port number passed to the TCP/IP component of a

Cybermation product exceeds 5 characters. This is normally the result incorrect user port number parameter specification. The TCP/IP stack is IBM's IUCV.


Messages and Codes

ESP-5.4-MC-03 271


Displays socket ID, task ID, local port, remote port and remote IP address of each active TCP/IP socket. The TCP/IP stack is Interlink Software's TCPaccess.



The TCP/IP stack is Interlink Software's TCPaccess. System Action: Processing continues. User Response: None.

2152E INET PURGE ID object nn not found Explanation: Response to an "INET PURGE ID nn" command.

The specified TCP/IP socket does not exist. The TCP/IP stack is Interlink Software's TCPaccess.

System Action: Processing continues. User Response: To display all the current TCP/IP sockets, enter the command

"INET DISPLAY ACTIVE". If a TCP/IP socket is to be purged, enter the command "INET PURGE ID nn" where "nn" is the socket ID. *** Warning **** "INET PURGE ID" should be used with caution.

2153I INET PURGE ID nn complete Explanation: Response to an "INET PURGE ID nn" command.

The TCP/IP socket with ID nn has been purged. The TCP/IP stack is Interlink Software's TCPaccess.


*** Warning **** "INET PURGE ID" should be used with caution.


The specified task "xxxxxx" does not exist or does not have any active TCP/IP sockets. The TCP/IP stack is Interlink Software's TCPaccess.

System Action: Processing continues. User Response: To display all the current TCP/IP task IDs, enter the command

"INET DISPLAY ACTIVE". If a task's TCP/IP sockets are to be purged, enter the command "INET PURGE TASK xxxx" where "xxxx" is the task ID.

272 ESP-5.4-MC-03



All active sockets for the specified task have been purged. The TCP/IP stack is Interlink Software's TCPaccess.



2156W nn second time out closing connection to raddr:rport, sent data may be lost Explanation: A Cybermation product was attempting to close a TCP connection with

remote partner raddr:rport in an orderly manner. However, the remote partner failed to respond within the time out period of nn seconds. The TCP/IP stack is Interlink Software's TCPaccess.

System Action: The TCP connection is forcibly closed. Any sent data not yet delivered to the connection partner is lost.

User Response: Attempt to determine the reason for the remote connection partner's failure to respond to the local Cybermation product's attempt to close the connection in an orderly manner. This problem usually does not result in lost data, and is therefore, in most cases, not serious.

2157E STIMERM error closing connection to raddr:rport, sent data may be lost Explanation: A Cybermation product was attempting to close a TCP connection with

remote partner raddr:rport in an orderly manner. However, an error occured in the system STIMERM service. The TCP/IP stack is Sterling Software's Solve:TCPaccess.

System Action: The TCP connection is forcibly closed. Any sent data not yet delivered to the connection partner is lost.


2160I Listening on port nnnn, QLen=nn Explanation: A Cybermation product TCP/IP server is listening for incoming

connection requests on the specified port. The TCP/IP stack is IBM's IUCV.


2161I Connected to server raddr:rport Explanation: A Cybermation product TCP/IP client has connected to a remote server.

The TCP/IP stack is IBM's IUCV. System Action: Processing continues. User Response: None.

Messages and Codes

ESP-5.4-MC-03 273

2162I Connected to client raddr:rport Explanation: A Cybermation product TCP/IP server has accepted a connection request

from a remote client. The TCP/IP stack is IBM's IUCV.


2164W nn second time out on receive from raddr:rport Explanation: A Cybermation product TCP/IP receive has timed out.

The TCP/IP stack is IBM's IUCV. System Action: The TCP/IP socket is closed. User Response: None.

2165E function{(n)}{, {*:lport}{->|<-}{raddr:rport}}, error, Sock=nn, ID=nn, Task=xxxxxx

Explanation: A TCP/IP socket function error has occurred. There are numerous causes of such errors. The TCP/IP stack is IBM's IUCV.

System Action: The TCP/IP socket is closed. User Response: Attempt to determine the cause of the error, and correct it. If the

problem is serious, call Cybermation Technical Support.

2166W function{(n)}{, {*:lport}{->|<-}{raddr:rport}}, info, Sock=nn, ID=nn, Task=xxxxxx

Explanation: An unusual TCP/IP socket function event has occurred. The TCP/IP stack is IBM's IUCV.


2167E XTCP xxxx, TIRA token yyyyyyyy invalid Explanation: A Cybermation product has requested a TCP/IP service for a socket that

either no longer exists, or never existed. The TCP/IP stack is IBM's IUCV.

System Action: Processing continues. User Response: If xxxx=CLOSE, the error is not serious and may be ignored.

If xxxx is anything else, there is an internal logic error. In this event, call Cybermation Technical Support.

2168S TCP/IP InitCall issued after initialization has completed Explanation: A TCP/IP initialization call was issued in a Cybermation product after

TCP/IP initialization completed. The TCP/IP stack is IBM's IUCV.

System Action: Task is abended with code U2911 User Response: Internal logic error. Call Cybermation Technical Support.


connection requests on the specified port. The TCP/IP stack is

274 ESP-5.4-MC-03

Interlink Software's TCPaccess. System Action: Processing continues. User Response: None.


The TCP/IP stack is Interlink Software's TCPaccess. System Action: Processing continues. User Response: None.


from a remote client. The TCP/IP stack is Interlink Software's TCPaccess.


2173W nn second time out on connect to raddr:rport Explanation: A time out occurred while a Cybermation product TCP/IP client was

attempting to connect to a remote host. The TCP/IP stack is Interlink Software's TCPaccess.

System Action: Application dependant. User Response: Identify the reason why the remote host is unreachable and correct it.

2174W nn second time out on receive from raddr:rport Explanation: A Cybermation product TCP/IP receive has timed out.

The TCP/IP stack is Interlink Software's TCPaccess. System Action: The TCP/IP socket is closed. User Response: None.

2175E DNRfunc, DNRarg, SSID=xxxx, error, DPLRTNCD=yyyyyyyy, Task=zzzzzz Explanation: A TCP/IP DNR (Domain Name Resolver) function error has occurred in a

Cybermation product. The function is usually "Get Host by Name". The TCP/IP stack is Interlink Software's TCPaccess.

System Action: Application dependant. User Response: Ensure that TCPaccess is up and running, and correctly configured to

handle the DNR request.

2176E {AOPEN|ACLOSE}, SSID=xxxx, error, APCBDGNC=yyyy, Task=zzzzzz Explanation: An error occurred in a Cybermation product attempting to connect to

(AOPEN) or disconnect from (ACLOSE) TCP/IP. The TCP/IP stack is Interlink Software's TCPaccess.

System Action: The Cybermation product TCP/IP application terminates. User Response: Ensure that TCPaccess is up and running and the Cybermation product is

correctly configured to access it.

Messages and Codes

ESP-5.4-MC-03 275

2177E APIfunc{(n)}{, {*:lport}{->|<-}{raddr:rport}}{, Qlen=nn}, RC=nn, error, TPLRTNCD=xxxxxxxx, ID=nn, Task=yyyyyy

Explanation: A TCP/IP API function error has occurred. There are numerous causes of such errors. The TCP/IP stack is Interlink Software's TCPaccess.

System Action: The TCP/IP socket (endpoint) is closed. User Response: Attempt to determine the cause of the error, and correct it. If the


2178W APIfunc{(n)}{, {*:lport}{->|<-}{raddr:rport}}{, Qlen=nn}, RC=nn, info, TPLRTNCD=xxxxxxxx, ID=nn, Task=yyyyyy

Explanation: An unusual TCP/IP socket function event has occurred. The TCP/IP stack is IBM's Interlink Software's TCPaccess.



either no longer exists, or never existed. The TCP/IP stack is Interlink Software's TCPaccess.



2181S Invalid DNRA, ID=xxxxxxxx Explanation: An invalid DNRA (Domain Name Request Area) was used by a Cybermation

product to request a TCP/IP service. The TCP/IP stack is IBM's IUCV.

System Action: Task is abended with code U2912. User Response: Internal logic error. Call Cybermation Technical Support.

2182S TCP/IP DNR request xx invalid Explanation: An invalid TCP/IP DNR (Domain Name Resolver) request was made by a

Cybermation product. The TCP/IP stack is IBM's IUCV.


2183S Invalid TIRA, ID=xxxxxxxx Explanation: An invalid TIRA (TCP/IP Request Area) was used by a Cybermation product

to request a TCP/IP service. The TCP/IP stack is IBM's IUCV.


276 ESP-5.4-MC-03

2184S TCP/IP API request xx invalid Explanation: An invalid TCP/IP request was made by a Cybermation product.

The TCP/IP stack is IBM's IUCV. System Action: Task is abended with code U2915. User Response: Internal logic error. Call Cybermation Technical Support.

2185S CPE TCP/IP does not currently support xxxx Explanation: A Cybermation product requested a TCP/IP function that is not currently

supported. The TCP/IP stack is IBM's IUCV.



TCP/IP initialization completed. The TCP/IP stack is Interlink Software's TCPaccess.

System Action: Task is abended with code U2911 User Response: Internal logic error. Call Cybermation Technical Support.


product to request a TCP/IP service. The TCP/IP stack is Interlink Software's TCPaccess.



Cybermation product. The TCP/IP stack is Interlink Software's TCPaccess.



to request a TCP/IP service. The TCP/IP stack is Interlink Software's TCPaccess.



The TCP/IP stack is Interlink Software's TCPaccess. System Action: Task is abended with code U2915. User Response: Internal logic error. Call Cybermation Technical Support.

Messages and Codes

ESP-5.4-MC-03 277

2195S CPE TCP/IP does not currently support xxxx The TCP/IP stack is Interlink Software's TCPaccess.



Displays socket ID, task ID, local port, remote port and remote IP address of each active TCP/IP socket. The TCP/IP stack is IBM's HPNS.



The TCP/IP stack is IBM's HPNS. System Action: Processing continues. User Response: None.

2202E INET PURGE ID object nn not found Explanation: Response to an "INET PURGE ID nn" command.

The specified TCP/IP socket does not exist. The TCP/IP stack is IBM's HPNS.



2203I INET PURGE ID nn complete Explanation: Response to an "INET PURGE ID nn" command.

The TCP/IP socket with ID nn has been purged. The TCP/IP stack is IBM's HPNS.


*** Warning **** "INET PURGE ID" should be used with caution.


The specified task "xxxxxx" does not exist or does not have any active TCP/IP sockets. The TCP/IP stack is IBM's HPNS.


278 ESP-5.4-MC-03

User Response: To display all the current TCP/IP task IDs, enter the command "INET DISPLAY ACTIVE". If a task's TCP/IP sockets are to be purged, enter the command "INET PURGE TASK xxxx" where "xxxx" is the task ID. *** Warning **** "INET PURGE TASK" should be used with caution.


All active sockets for the specified task have been purged. The TCP/IP stack is IBM's HPNS.



2206E Invalid port number xxxx Explanation: An invalid port number was passed to the TCP/IP component of a

Cybermation product. This is normally the result of an incorrect user port number parameter specification. The TCP/IP stack is IBM's HPNS.


2207E Invalid port number length nn Explanation: The length of a port number passed to the TCP/IP component of a

Cybermation product exceeds 5 characters. This is normally the result incorrect user port number parameter specification. The TCP/IP stack is IBM's HPNS.



connection requests on the specified port. The TCP/IP stack is IBM's HPNS.



The TCP/IP stack is IBM's HPNS. System Action: Processing continues. User Response: None.


Messages and Codes

ESP-5.4-MC-03 279

from a remote client. The TCP/IP stack is IBM's HPNS.


2213W nn second time out on connect to raddr:rport Explanation: A time out ocurred while a Cybermation product TCP/IP client was

attempting to connect to a remote host. The TCP/IP stack is IBM's HPNS.

System Action: Application dependant. User Response: Identify the reason why the remote host is unreachable and correct it.

2214W nn second time out on {send to|receive from} raddr:rport Explanation: A Cybermation product TCP/IP send or receive has timed out after nn

seconds. The TCP/IP stack is IBM's HPNS.

System Action: The TCP/IP socket is closed. User Response: None.

2215E function{(n)}{, {*:lport}{->|<-}{raddr:rport}}, error, Sock=nn, ID=nn, Task=xxxxxx

Explanation: A TCP/IP socket function error has occurred. There are numerous causes of such errors. The TCP/IP stack is IBM's HPNS.

System Action: The TCP/IP socket is closed. User Response: Attempt to determine the cause of the error, and correct it. If the


2216W function{(n)}{, {*:lport}{->|<-}{raddr:rport}}, info, Sock=nn, ID=nn, Task=xxxxxx

Explanation: An unusual TCP/IP socket function event has occurred. The TCP/IP stack is IBM's HPNS.



either no longer exists, or never existed. The TCP/IP stack is IBM's HPNS.




TCP/IP initialization completed. The TCP/IP stack is IBM's HPNS.

System Action: Task is abended with code U2911

280 ESP-5.4-MC-03

User Response: Internal logic error. Call Cybermation Technical Support.


product to request a TCP/IP service. The TCP/IP stack is IBM's HPNS.



Cybermation product. The TCP/IP stack is IBM's HPNS.



to request a TCP/IP service. The TCP/IP stack is IBM's HPNS.



The TCP/IP stack is IBM's HPNS. System Action: Task is abended with code U2915. User Response: Internal logic error. Call Cybermation Technical Support.

2225S CPE TCP/IP does not currently support xxxx Explanation: A Cybermation product requested a TCP/IP function that is not currently

supported. The TCP/IP stack is IBM's HPNS.


2226E INET PURGE ID nn cancelled because the owner is freeing the socket Explanation: Response to an "INET PURGE ID nn" command.

The task that owns the socket is already freeing the socket. The TCP/IP stack is IBM's HPNS.



Messages and Codes

ESP-5.4-MC-03 281

2227E INET PURGE ID nn cancelled to allow the owner to self-purge Explanation: Response to an "INET PURGE ID nn" command.

The task that owns the socket is able to purge the socket itself, so it will be allowed to do so. The TCP/IP stack is IBM's HPNS.



2228E INET PURGE ID nn/INET PURGE TASK xxxxxx cancelled due to requeue failure

Explanation: Response to an "INET PURGE ID nn" command or to an "INET PURGE TASK xxxxxx" command. The task that owns the socket(s) is terminating or has already terminated, so it has closed or will close all its socket(s). The TCP/IP stack is IBM's HPNS.


"INET DISPLAY ACTIVE". If a TCP/IP socket is to be purged, enter the command "INET PURGE ID nn" where "nn" is the socket ID. *** Warning **** "INET PURGE ID" and "INET PURGE TASK" should be used with caution.

2240E ESP/WSS xxx.xxx.xxx:yyyy mode message not followed by change direction Explanation: This message is issued by a mainframe ESP work station client

connected to an ESP work station server via TCP/IP. xxx.xxx.xxx is the IP address of the ESP work station server. yyyyy is the TCP port number of the ESP work station server. When an ESP work station server sends a mode message ("09 800000 -->") to an ESP work station client, it always follows with a change of direction message ("99 000000"). This problem should therefore never occur.

System Action: The TCP/IP connection to the ESP work station server partner is closed.

User Response: Call Cybermation support.

2241E XWSS PUT request invalid, multi-line message not fully received Explanation: This message is issued by a mainframe ESP work station client

connected to an ESP work station server via TCP/IP.

282 ESP-5.4-MC-03

This is a Cybermation internal error that should never occur.



2242E XWSS GET request invalid in send mode Explanation: This message is issued by a mainframe ESP work station client

connected to an ESP work station server via TCP/IP. This is a Cybermation internal error that should never occur.



2243E XWSS GET DATALEN=wwww too small for xxxx byte message from yyy.yyy.yyy:zzzzz

Explanation: wwww is the input buffer length for a message receive request from the TCP/IP connection partner. xxxx is the message length received from the TCP/IP connection partner. yyy.yyy.yyy is the IP address of the TCP/IP connection partner. zzzzz is the TCP port number of the TCP/IP connection partner. If the local ESP work station client is connected to an ESP work station server, this is a Cybermation internal error. Otherwise the connection is invalid, and a protocol error has occured.

System Action: The TCP/IP connection is closed. User Response: Ensure that connection partner yyy.yyy.yyy:zzzzz is a valid ESP

work station server. If it is, call Cybermation support.

2244W ESP/WSS xxx.xxx.xxx:yyyy connection closed Explanation: This message is issued by a mainframe ESP work station client

connected to an ESP work station server via TCP/IP. xxx.xxx.xxx is the IP address of the ESP work station server host. yyyyy is the TCP port number of the ESP work station server. The connection has been closed.

System Action: The mainframe ESP work station client terminates. User Response: None.

2245E Received data length wwww from xxx.xxx.xxx:yyyyy exceeds maximum zzzz Explanation: wwww is the length of the message received from the TCP/IP

connection partner. xxx.xxx.xxx is the IP address of the TCP/IP connection partner. yyyyy is the TCP port number of the TCP/IP connection partner. zzzz is the maximum permissible length of a message that the local ESP work station client can accept from its TCP/IP connection partner.

Messages and Codes

ESP-5.4-MC-03 283

If the local ESP work station client is connected to an ESP work station server, this is a Cybermation internal error. Otherwise the connection is invalid, and a protocol error has occured.

System Action: The TCP/IP connection is closed. User Response: Ensure that connection partner xxx.xxx.xxx:yyyyy is a valid ESP


2246E Invalid ESP/WSS message received from xxx.xxx.xxx:yyyyy Explanation: xxx.xxx.xxx is the IP address of the TCP/IP connection partner.

yyyyy is the TCP port number of the TCP/IP connection partner. If the local ESP work station client is connected to an ESP work station server, this is a Cybermation internal error. Otherwise the connection is invalid, and a protocol error has occured.

System Action: The TCP/IP connection is closed. User Response: Ensure that connection partner xxx.xxx.xxx:yyyyy is a valid ESP


2250I Cybermation TCP/IP Diagnostic Utility Explanation: Introductory identification message when the Cybermation TCP/IP

diagnostic utility CYBTCPIP is activated. System Action: CYBTCPIP initialization continues. User Response: None.

2251W SINGLE_TASK option invalid for IUCV, ignored Explanation: The Cybermation TCP/IP diagnostic utility CYBTCPIP was invoked

specifying incompatible start parameters IUCV and SINGLE_TASK. SINGLE_TASK is ignored because the IUCV TCP/IP stack does not support multiple concurrent TCP/IP sockets on the same MVS task.

System Action: CYBTCPIP defaults to MULTI_TASK. Each TCP/IP socket runs under its own MVS task.

User Response: When running CYBTCPIP using the IUCV TCP/IP stack, do not specify the SINGLE_TASK start parameter.

2251I Primary home IP address xxxx Explanation: When the Cybermation TCP/IP diagnostic utility CYBTCPIP is activated,

it displays the primary home IP address xxxx of the TCP/IP stack it uses to service its connections.

System Action: CYBTCPIP initialization continues. User Response: None.

2253E Invalid command syntax, File=xxxx, Line=yyyy Explanation: The Cybermation TCP/IP diagnostic utility CYBTCPIP encountered a

syntax error in the command on line yyyy of the file allocated to ddname xxxx.

System Action: Processing continues. User Response: Correct the command on line xxxx of file yyyy.

284 ESP-5.4-MC-03

2254E Command xxxx not found, File=yyyy, Line=zzzz Explanation: The Cybermation TCP/IP diagnostic utility CYBTCPIP encountered a

command xxxx that it does not recognize as valid, in line zzzz of the file allocated to ddname yyyy.

System Action: Processing continues. User Response: Correct the command on line zzzz of file yyyy.

2255W xxxx Explanation: Message xxxx is usually "FILE TCPPARM NOT ALLOCATED".

An attempt by the Cybermation TCP/IP diagnostic utility CYBTCPIP to open the TCPPARM file failed because there was no DD statement for it in the job's JCL. This message is only issued if CYBTCPIP runs as a started task or as a batch job.

System Action: Processing continues. User Response: If a TCPPARM file to read commands during CYBTCPIP initialization is

required, then add a TCPPARM DD statement to the job's JCL.

2256E xxxx Explanation: An attempt by the Cybermation TCP/IP diagnostic utility CYBTCPIP to

open the TCPPARM file failed. Message xxxx should explain the reason for the failure.

System Action: Processing continues. User Response: Determine the problem from message xxxx and correct it.

2257I For command options, enter HELP or H Explanation: Issued by the Cybermation TCP/IP diagnostic utility CYBTCPIP when

activated as a TSO command. System Action: Processing continues. User Response: Entering HELP or H will display all the CYBTCPIP command options.

2258E Command get error, RC=xxxx, terminating Explanation: The Cybermation TCP/IP diagnostic utility CYBTCPIP encountered an

error attempting to get an input command interactively. System Action: The CYBTCPIP job or TSO command terminates. User Response: Rerun the CYBTCPIP job or TSO command. If the problem persists, call


2259E Invalid command syntax Explanation: The Cybermation TCP/IP diagnostic utility CYBTCPIP encountered a

syntax error in the input command entered interactively. System Action: Processing continues. User Response: Reenter the command correctly.

2260E Command xxxx not found Explanation: The Cybermation TCP/IP diagnostic utility CYBTCPIP encountered a

Messages and Codes

ESP-5.4-MC-03 285

command xxxx, entered interactively, that it does not recognize as valid.

System Action: Processing continues. User Response: Reenter the command correctly.

2261C CYBTCPIP Command Options Explanation: Response to the Cybermation TCP/IP diagnostic utility CYBTCPIP's HELP

or H command. Lists all the commands supported by the Cybermation TCP/IP diagnostic utility CYBTCPIP.


2262I No active TCP servers Explanation: Response to the Cybermation TCP/IP diagnostic utility CYBTCPIP's

DISPLAY SERVERS or D S command. No CYBTCPIP TCP servers are currently active.


2263C CYBTCPIP TCP Server Connections Explanation: Response to the Cybermation TCP/IP diagnostic utility CYBTCPIP's

DISPLAY SERVERS or D S command. All currently active CYBTCPIP TCP servers are displayed.


2264I No active TCP clients Explanation: Response to the Cybermation TCP/IP diagnostic utility CYBTCPIP's

DISPLAY <CLIENTS> or D <C> command. No CYBTCPIP TCP clients started by the CYBTCPIP CONNECT or CO command are currently active.


2265C CYBTCPIP TCP Clients Explanation: Response to the Cybermation TCP/IP diagnostic utility CYBTCPIP's

DISPLAY <CLIENTS> or D <C> command. All currently active CYBTCPIP TCP clients started by the CYBTCPIP CONNECT or CO command are displayed.


2266I Client xxxx connecting to host yyyy:zzzz Explanation: Response to the Cybermation TCP/IP diagnostic utility CYBTCPIP's

CONNECT, CONN, CON or CO command. A CYBTCPIP client has been created. It has been assigned client number xxxx and is connecting to the server on host xxxx listening on TCP port zzzz. The symbolic variable %CLIENT is set to xxxx.

286 ESP-5.4-MC-03

xxxx becomes the current client, and the CYBTCPIP commands SEND, SE, >>, RECEIVE, RECV, RE, <<, SENDRECV, SR, ><, CLOSE and CL commands can be issued to client xxxx without explicitly specifying xxxx until another CYBTCPIP client is created with the CONNECT, CONN, CON or CO command.

System Action: A message follows indicating whether or not the attempt to connect to the specified server succeeded.


2267I Client xxxx connection local_ip:local_port<>remote_host:remote_port set to current

Explanation: Response to the Cybermation TCP/IP diagnostic utility CYBTCPIP's SET xxxx or T xxxx command. The symbolic variable %CLIENT is set to xxxx. Subsequent CYBTCPIP SEND, SE, >>, RECEIVE, RECV, RE, <<, SENDRECV, SR, ><, CLOSE and CL commands that do not explicitly specify a client will be scheduled to client xxxx.


2268I Client xxxx connection local_ip:local_port<>remote_host:remote_port established

Explanation: A request to connect a CYBTCPIP client to the server listening on TCP port remote_port of host remote_host has succeeded. The client has been assigned number xxxx.

System Action: Processing continues. User Response: CYBTCPIP client commands SEND, SE, >>, RECEIVE, RECV, RE, <<,

SENDRECV, SR, ><, CLOSE and CL commands can be issued to client xxxx. These commands do not have to explicitly specify xxxx until another CYBTCPIP client is created with the CONNECT, CONN, CON or CO command.

2269I Client xxxx connection local_ip:local_port<>remote_host:remote_port {closed|purged}

Explanation: A CYBTCPIP client's connection to the TCP server on port remote_port of host remote_host has terminated. The connection is closed in response to a CYBTCPIP CLOSE or CL command. The connection is purged in response to an INET PURGE ID, INET PG ID, INET PURGE TASK or INET PG TA command.


2270I Connecting to xxxx service yyyy:zzzz Explanation: Response to the Cybermation TCP/IP diagnostic utility CYBTCPIP's

DAYTIME, DISCARD or ECHO command. xxxx is the TCP service that the client is attempting to connect to, i.e. daytime, discard or echo. yyyy is the host name or IP address of the target server's host. zzzz is the TCP port that the target server is listening on. If not explicitly specified in the command, the default is 13 for DAYTIME,

Messages and Codes

ESP-5.4-MC-03 287

9 for DISCARD and 7 for ECHO. System Action: If the attempt to connect to the specified daytime server succeeds:

The DAYTIME client issues receive and close. The DISCARD client issues send and close. The ECHO client issues send, receive and close. All sent and received data is displayed. If the attempt to connect to the specified server fails, an error error message is displayed.


2271I local_ip:local_port->remote_ip:remote_port The quick brown fox jumps over the lazy dog

Explanation: "The quick brown fox jumps over the lazy dog" is sent to the connected server on remote_host:remote_port by the Cybermation TCP/IP diagnostic utility CYBTCPIP's DISCARD and ECHO command TCP clients.

System Action: After sending the above message:

The DISCARD client closes the connection. The ECHO client receives an expected echoed response, displays it, and closes the connection.


2272W Connection local_ip:local_port<>remote_host:remote port prematurely closed by peer

Explanation: The Cybermation TCP/IP diagnostic utility CYBTCPIP's DAYTIME or ECHO command TCP client issued a receive expecting data. Instead the server on remote_host:remote_port closed the connection. Perhaps the DAYTIME or ECHO TCP client is not connected to a daytime or echo TCP server respectively.

System Action: The DAYTIME or ECHO command TCP client terminates. User Response: None.

2273I xxxx TCP daemon started on port yyyy Explanation: Response to the Cybermation TCP/IP diagnostic utility CYBTCPIP's

DAYTIMED, DISCARDD, ECHOD, LISTEN or LI command. A CYBTCPIP server has (daemon) has been started. xxxx is the service that the TCP server is providing, and is either daytime, discard or echo. yyyy is the TCP port that the CYBTCPIP server will listen on. If not explicitly specified in the command, the default is 13 for DAYTIMED, 9 for DISCARDD and 7 for ECHOD. A TCP port must be specified on the LISTEN or LI commands. The LISTEN and LI commands start a CYBTCPIP DISCARD server.

System Action: The CYBTCPIP server attempts to perform the TCP service it provides. When a TCP client connects to a CYBTCPIP server: The daytime server sends a day and time message to the client and closes the connection. The discard server receives data from the client until the client closes the connection.

288 ESP-5.4-MC-03

The echo server receives data from the client and sends it right back in identical format until the client closes the connection.


2274I xxxx TCP server connection local_ip:local_port<>remote_ip:remote:port established

Explanation: A Cybermation TCP/IP diagnostic utility CYBTCPIP server (daemon) has received and accepted a connection request from a remote TCP client. xxxx is the service that the TCP server is providing, and is either daytime, discard or echo.

System Action: The CYBTCPIP server attempts to perform the TCP service it provides. The daytime server sends a day and time message to the client and closes the connection. The discard server receives data from the client until the client closes the connection. The echo server receives data from the client and sends it right back in identical format until the client closes the connection.


2275I xxxx TCP server connection local_ip:local_port<>remote_ip:remote_port terminated

Explanation: A Cybermation TCP/IP diagnostic utility CYBTCPIP TCP server connection to a remote client has terminated. xxxx is the TCP service and is either Discard or Echo.


2276W No CYBTCPIP daemon listening on port xxxx Explanation: Response to the Cybermation TCP/IP diagnostic utility CYBTCPIP's

STOP xxxx command. An attempt was made to stop a CYBTCPIP server (daemon) listening on TCP port xxxx. However, no such server is active.

System Action: Processing continues. User Response: To display the active TCP servers under CYBTCPIP, enter the command:

DISPLAY SERVERS or D S.

2277I xxxx CYBTCPIP daemon on port yyyy stopped Explanation: Response to the Cybermation TCP/IP diagnostic utility CYBTCPIP's

STOP yyyy command. xxxx is the service that the TCP server is providing, and is either daytime, discard or echo. yyyy is the TCP port that the CYBTCPIP server (daemon) was listening on.

System Action: The specified CYBTCPIP TCP server terminates. User Response: None.

2278W Client not specified, current client not set Explanation: Response to Cybermation TCP/IP diagnostic utility CYBTCPIP's SEND, SE,

>>, RECEIVE, RECV, RE, >>, SENDRECV, ><, CLOSE or CL command.

Messages and Codes

ESP-5.4-MC-03 289

The CYBTCPIP client related command was issued without specifying the client number and no default client currently exists. When a CYBTCPIP client is created, it becomes the default client. A CYBTCPIP client can also be set to the default with the SET xxxx or the T xxxx command, where xxxx is the client number. If only one CYBTCPIP client exists, it is the default. When the default CYBTCPIP terminates and there is more than one client remaining, none are set to the default.

System Action: None. User Response: Re-issue the CYBTCPIP client command explicitly specifying the client

number. Or make the target CYBTCPIP client current with the SET xxxx or the T xxxx command, where xxxx is the client's number. Then re-issue the CYBTCPIP client command. To display the current active CYBTCPIP clients, enter the command: DISPLAY CLIENTS or D C or D.

2279E Client xxxx not found Explanation: Response to Cybermation TCP/IP diagnostic utility CYBTCPIP's SEND, SE,

>>, RECEIVE, RECV, RE, >>, SENDRECV, ><, CLOSE or CL command. The CYBTCPIP client related command was issued specifying number xxxx of a client that does not exist.

System Action: None. User Response: To display the current active CYBTCPIP clients, enter the command:

DISPLAY CLIENTS or D C or D. Then, if necessary, re-issue the CYBTCPIP client command specifying an active client.

2280W TCP daemon already active on port xxxx Explanation: Response to Cybermation TCP/IP diagnostic utility CYBTCPIP's DAYTIMED,

DISCARDD, ECHOD, LISTEN or LI command. An attempt to start a Cybermation TCP/IP diagnostic utility CYBTCPIP server (daemon) via the DAYTIMED, ECHOD, LISTEN or LI command failed because another CYBTCPIP server is already listening on the specified or default port xxxx.

System Action: The started CYBTCPIP server terminates. User Response: To display the current active CYBTCPIP servers, enter the command:

DISPLAY SERVERS or D S. This only displays CYBTCPIP servers, not every TCP/IP server in the system. Then, if necessary, re-issue the CYBTCPIP server command specifying an unused port.

2281W TCP daemon on port xxxx not found, closing connection Explanation: A TCP client has connected to a Cybermation TCP/IP diagnostic utility

CYBTCPIP server. The server has created a new task to handle the connection, but by the time this task begins execution, the original server (daemon) task has terminated. This occurrence should be extremely rare.

System Action: The connection is closed and the task terminates.

290 ESP-5.4-MC-03


2282I xxxx scheduled to client yyyy connection to remte_host:remote_port Explanation: Response to a Cybermation TCP/IP diagnostic utility CYBTCPIP client

command, i.e. SEND, SE, >>, RECEIVE, RECV, RE, <<, SENDRECV, SR, ><, CLOSE or CL. xxxx is the TCP request to be performed, and is one of the following: Send (for SEND, SE or >>), Receive (for RECEIVE, RECV, RE or <<), Send/receive (for SENDRECV, SR or ><), Close (for CLOSE or CL). yyyy is the CYBTCPIP client number.

System Action: The specified CYBTCPIP client command TCP request is performed. User Response: None.

2283I local_ip:local_port->remote_host:remote_port xxxx Explanation: A Cybermation TCP/IP diagnostic utility CYBTCPIP client or server has

sent data xxxx to its TCP connection partner. System Action: Processing continues. User Response: None.

2284I local_ip:local_port<-remote_host:remote_port xxxx Explanation: A Cybermation TCP/IP diagnostic utility CYBTCPIP client or server has

received data xxxx from its TCP connection partner. System Action: Processing continues. User Response: None.

2285I local_ip:local_port<-remote_host:remote_port xxxx Explanation: A Cybermation TCP/IP diagnostic utility CYBTCPIP client or server has

received data from its TCP connection partner. xxxx is either the hexadecimal zone or hexadecimal numeric half of each byte of the received data.

System Action: This message always appears in pairs. The 1st displays the hexadecimal zone of each byte of received data. The 2nd displays the hexadecimal numeric of each byte of received data.


2290W ESPLMI must execute in a foreground TSO environment Explanation: An attempt was made to execute the TSO ESP Line Mode Interface in a

non-TSO environment. System Action: The ESP Line Mode Interface terminates. User Response: None.

2291I Cybermation ESP Line Mode Interface Explanation: Introductory message when ESP Line Mode Interface is invoked. System Action: The ESP Line Mode Interface attempts to logon to the specified

ESP work station server. User Response: None.

Messages and Codes

ESP-5.4-MC-03 291

2292E Command get error, RC=xxxx, terminating Explanation: The Cybermation ESP Line Mode Interface utility encountered an error

attempting to get an input command interactively. System Action: The ESP Line Mode Interface terminates. User Response: Rerun the ESP Line Mode Interface. If the problem persists, call


2300E USER xxxx NOT AUTHORIZED FOR ESP OPERATOR COMMANDS Explanation: An operator command was issued, but the issuer does not have the

authority to issue such commands. System Action: The command is ignored. User Response:

2301E xxxx Explanation: This message describes an I/O error encountered while processing the

ESP audit log. System Action: User Response: The audit log may need to be recreated.

2302W DATA SET xxxx FOR COPYJCL FUNCTION IS NOT PARTITIONED Explanation: The COPYJCL library must be a partitioned data set. The job will be

saved in a member named with the job name or the job id. System Action: The job was not saved. User Response: Specify a partitioned data set in the COPYJCL statement.

2303I OK Explanation: An EVENTSET command was accepted and processed by the ESP subsystem. System Action: None. User Response: None.

2304I nn {entry | entries} flushed from Deferred queue Explanation: In response to an EVENTSET FLUSH command, this message indicates the

number overdue requests which were flushed from the Deferred queue. The requests flushed are logged in the Auditlog.


2305I DELETE REQUEST MUST BE ISSUED FROM A CONSOLE Explanation: An EVENTSET command was issued to delete an Event data set. The

command was not issued by a console. System Action: The delete request is not processed. User Response: Issue the command from a system console.

2307I EVENT TRIGGERED Explanation: The TRIGGER command has successfully triggered the event. System Action: The event has been triggered. User Response:

292 ESP-5.4-MC-03

2308W EVENT IS IN THE HELD STATE Explanation: The TRIGGER command would not trigger the event since the hold count

is greater than zero. System Action: The event was not triggered. User Response:

2309W EVENT IS IN THE SUSPENDED STATE Explanation: The TRIGGER command would not trigger the event since the suspend

count is greater than zero. System Action: The event was not triggered. User Response:

2310W INSUFFICIENT CHECKPOINT SPACE FOR A REQUEST ELEMENT There is no checkpoint file space in which to record another scheduling of this event.

System Action: The event was not triggered. User Response: Wait until several other time-delayed events have been triggered, and

then try again.

2311W EVENT xxxx NOT FOUND Explanation: This event could not be found in the event data set. System Action: User Response: Correct the event name and try again.

2312W EVENTSET xxxx NOT FOUND Explanation: The BKUPEVS command specified an event data set which is not defined

to ESP. System Action: No event data set was backed up. User Response: Correct the event data set name and try again.

2313I OK Explanation: In response to a DFLTUSER NONE command, this message indicates that a

userid has become unauthorized. System Action: User Response:

2314E NO SPACE LEFT IN CHECKPOINT Explanation: The DFLTUSER command could not obtain space in the checkpoint to hold

the default user definition. System Action: The DFLTUSER request is not processed. User Response: Use the LISTCKPT command to determine the amount of space remaining in

the checkpoint.

2315E UNABLE TO QUEUE DIRECTLY TO SYSTEM <sysid> Explanation: The operator issued a TRIGGER command to trigger an EVENT on another

system but the Queue Data Set can not be found. System Action: The command is ignored.

Messages and Codes

ESP-5.4-MC-03 293

User Response: Check the <sysid>.

2316E SYSTEM <sysid> NOT A MEMBER OF SHARED QUEUE Explanation: The operator issued a TRIGGER command to trigger an EVENT on another

system, but the named <sysid> is not a member of shared queue. System Action: The command is ignored. User Response: Check the <sysid>.

2317C EVENT DATASET STATUS Explanation: This message introduces the response to the LISTEVS command System Action: The status of event databases will be displayed. User Response:

2318W EVENTSET xxxx NOT FOUND Explanation: The LISTEVS command specified an event database, but that database has

not been defined to ESP. System Action: User Response: Correct the event database name and try again.

2319W NO EVENT DATASETS DEFINED Explanation: A LISTEVS command specified no operands, but no event databases have

been defined to ESP. System Action: User Response:

2320C CHECKPOINT DATASET STATUS Explanation: In response to a LISTCKPT command, this message introduces a display

of information describing the checkpoint data set. System Action: Processing continues. User Response: None.

2321I NEXT USERDEF BACKUP AT xxxx ON yyyy Explanation: In response to a BKUPUDEF command, this message confirms that a backup

will take place at a scheduled time. System Action: User Response:

2322E NO CHECKPOINT SPACE AVAILABLE Explanation: A BKUPUDEF command was issued, but there is no space in the checkpoint

file in which to schedule a backup. System Action: No backups were scheduled. User Response: Either issue a BKUPUDEF command with no operands to cause an immediate

backup, or wait until several scheduled events have been triggered and try the command again.

2323E ERROR SCANNING COMMAND, RC=nn Explanation: A problem was encountered while parsing the command line. System Action: The command is ignored. The user is prompted for a new command.

294 ESP-5.4-MC-03

User Response: System routine IKJPARS returned error code nn. When nn=12: invalid parameters passed to parse from CP. nn=16: No space available. nn=20: Validity check routine termination. nn=24: An error in input parameters was detected in the IKJPARS2 load module. nn=28: A line drop condition was detected and IKJPTGT (PUTGET I/O service routine) or IKJPUTL (PUTLINE I/O service routine) set return codes of 24 and 32 respectively.



2325I ESP COMMAND ENDED Explanation: This command confirms that the ESP session has ended, as a result of

an END command being issued from a terminal. System Action: The ESP session has ended. User Response:

2326C EVENT LIST Explanation: This message introduces the display of one or more events specified in

a LIST command. System Action: User Response:

2328W xxxx Explanation: An I/O error occurred while opening or reading from the data set being

scanned by a SCAN statement. System Action: The data set was not completely scanned. User Response: Correct the input data set or specify a different data set, and try

again.

2329W xxxx Explanation: An I/O error occurred while opening or writing to the data set

specified in the PRINT parameter of a SCAN command. System Action: The data set was not completely written to. User Response: Correct the data set or specify a different data set and try again.

2330E Access to xxxx denied by security system Explanation: The user attempted to enter UTIL mode or was in UTIL mode and

attempted to enter a UTIL mode subcommand. xxxx is the command the user attempted to access. Access to the requested command was denied by the security system.

System Action: The command or subcommand is ignored. User Response: Obtain access to the required command resource and re-enter the

command.

Messages and Codes

ESP-5.4-MC-03 295

2331W No record in buffer Explanation: A command was issued which operates on an individual record. A target

record has not yet been selected. System Action: The command is ignored. User Response: Select a record as the target of the command and reenter the command.

2332E INDEX data set unload ended with errors Explanation: During a CONVERT command, an attempt was made to unload the INDEX

data set. The attempt ended with one or more errors. System Action: None. User Response: Scan any previous messages to determine what caused the error.

Correct the error and reissue the CONVERT command.

2333I Conversion run ended successfully Explanation: The CONVERT command has successfully updated all data sets to the

current level. System Action: None. User Response: None.

2334I Starting to unload EVENT data set xxxx Explanation: The CONVERT command is starting to process the EVENT data set xxxx. System Action: Processing continues. User Response: None.

2335W APPLFILE or TRAKFILE keyword omitted Explanation: An EXTEND command was issued which did not contain an APPLFILE or

TRAKFILE keyword. System Action: The command is terminated. User Response: Re-enter the EXTEND command specifying one of the required keywords.

2336E Above error occurred during COPY function Explanation: An error occurred during the COPY command. The previous message

details the error. System Action: The COPY command is terminated. User Response: Determine what cause the error and re-issue the COPY command.

2337I nn slots added to data set, nn slots total Explanation: The EXTEND utility has successfully added mm SLOTS to the specified

slotfile, which now has a total of nn SLOTS. System Action: None. User Response: The resulting slotfile may be allocated for use, if desired.

2338I nn records read from SMF JOURNAL data set Explanation: During processing of the RESTORE command, nn records were read from

the SMF JOURNAL data set. System Action: None. User Response: None.

296 ESP-5.4-MC-03

2339I nn journal updates found for xxxx Explanation: During processing of the RESTORE command, nn records from the SMF

JOURNAL data set provided updates. System Action: None. User Response: None.

2340W DATA SET TRIGGERING QUIESCED DUE TO PRIOR REQUEST Explanation: This message is issued when ESP is warm started and detects that

data set triggering was quiesced prior to the previous shutdown. System Action: Data set triggering is quiesced until explicitly enabled through the

DSTRST command. User Response: To restart data set triggering, use the DSTRST RESTART command.

2341I NEXT INDEX DATASET BACKUP AT xxxx ON yyyy Explanation: This message confirms the success of the BKUPINDX command. System Action: A backup of the index file has been scheduled. User Response:

2342I NO INDEX BACKUP TIME SET Explanation: In response to a BKUPINDX ? command, this message indicates that no

backup of the index file is scheduled. System Action: User Response: To schedule a backup, use the BKUPINDX command with schedule criteria.

To perform an immediate backup, use the BKUPINDX command with no operands.

2343E NO CHECKPOINT SPACE AVAILABLE Explanation: There is no checkpoint file space available with which to schedule a

backup of the index file. System Action: User Response: Either issue a BKUPINDX command with no operands to cause an immediate

backup, or wait until several scheduled events have been triggered and try the command again.

2344W INVALID RECORD FORMAT ON INDEX DATASET Explanation: System Action: User Response:


When nn=12: invalid parameters passed to parse from CP. nn=16: No space available. nn=20: Validity check routine termination. nn=24: An error in input parameters was detected in the

Messages and Codes

ESP-5.4-MC-03 297

IKJPARS2 load module. nn=28: A line drop condition was detected and IKJPTGT (PUTGET I/O service routine) or IKJPUTL (PUTLINE I/O service routine) set return codes of 24 and 32 respectively. If the problem persists, notify your support personnel.



2347I OK Explanation: The command was successful. System Action: The requested action has been taken. User Response:

2348W INVALID JOBNAME/NUMBER xxxx Explanation: The LJ command specified a job identifier that was syntactically

incorrect. System Action: No job information was listed. User Response: The operand to LJ must be either a job number (without a 'J' prefix),

a job name, or a job name followed by a parenthesized job number. Examples are 'LJ 6635', 'LJ JOBNAME', and 'LJ JOBNAME(J6635)'. A valid job number is within the range 1 through 65534, inclusive.

2349I SPECIFIED JOB NOT FOUND Explanation: The LJ command specified a job that either was not found in ESP, or

for which the user is not authorized. System Action: User Response: Correct the job name or number and try again.

2350C ABENDED JOB LIST Explanation: This message introduces a list of all abended jobs in response to a

DAB command with no operands. All abended jobs in the queue are listed. The size of the abended job queue can be set with the ABENDLIM command.


2351I NO MATCHING ENTRIES FOUND Explanation: A DAB command was issued, but no matching job names were found. System Action: User Response: Correct the LEVEL parameter and try again.

2352W NO ABENDED JOBS QUEUED Explanation: A DAB command was issued, but there are no abended jobs on the queue. System Action:

298 ESP-5.4-MC-03

User Response:

2353C QUEUE DISPLAY Explanation: This message introduces the response to the DQ command. System Action: User Response:

2354I NO MATCHING P-NODE QUEUE FOUND Explanation: A DQ or DN command specified a QUEUE name that matched no existing

P-node queues. System Action: User Response: Correct the QUEUE parameter and try again.

2355I NO P-NODE QUEUES IN EXISTENCE Explanation: A DQ command was issued, but there are no P-node queues in the system. System Action: User Response:

2356C JOBNAME DISPLAY Explanation: This message introduces the response to the DN command. System Action: User Response:

2357I NO JOB FOUND MATCHING SELECTION CRITERIA Explanation: A DN command was issued, but there are no matching job names on the

P-node queue. System Action: User Response: Correct the QUEUE parameter or the JOB parameter and try again.

2358W INVALID COUNT nn, MUST BE IN RANGE 0-999 Explanation: The size of the abended jobs queue must be smaller than 1000. System Action: The ABENDLIM count was not changed. User Response: Correct the count and try again.

2359I ABEND QUEUE MAX = nn, nn CURRENTLY QUEUED Explanation: In response to an ABENDLIM command with no operand, this message

displays the size of the abended jobs queue and its maximum size as set by the ABENDLIM command.


2360I DEFAULT P-NODE FOR xxxx IS yyyy Explanation: In response to a DFPNODE command with no operand, this message

displays the current setting of default P-node as set by the last DFPNODE command.


Messages and Codes

ESP-5.4-MC-03 299

2361I NO DEFAULT P-NODE SET FOR xxxx Explanation: In response to a DFPNODE command with no operand, this message

indicates that no default P-node has been set. System Action: User Response: Use an operand on the DFPNODE command to set a default P-node.

2362C QUEUE DATASET DISPLAY Explanation: This message introduces the response to the LISTQ command. The

information displayed includes the time that the queue data set was formatted, the amount of space allocated and the amount of space used.


2363C TRAKFILE DISPLAY Explanation: This message introduces the response to the LISTTRAK command. The

information displayed includes the time that the job tracking file was formatted and the current allocation status, including the number of free blocks.


2364W TRAKFILE NOT DEFINED, OR IS NOT OPENED Explanation: In response to a LISTTRAK command, this message indicates that the job

tracking file could not be opened. System Action: User Response: The job tracking file must be defined in the ESP initialization

parameters with the TRAKFILE command.

2365W NO APPLICATION TRAKFILES DEFINED Explanation: In response to a LISTAPTF command, this message indicates that no

application files are defined. System Action: User Response:

2366C SYSTEM DISPLAY Explanation: This message introduces the response to the LSYS command. System Action: User Response:

2367W NO DOCUMENTATION AVAILABLE FOR xxxx Explanation: The JOBINFO command specified a job name or number that could not be

found. System Action: User Response: Correct the job name or number and try again.

2368W JOB DOCUMENTATION DATASET NOT DEFINED IN ESPPROC Explanation: The JOBINFO command could not find the documentation data set.

300 ESP-5.4-MC-03

System Action: User Response: Define a DOCLIB in the ESP proc and try again.

2369I SADLINK xxxx LOADED Explanation: The SADLOAD has successfully loaded the SAD data set. System Action: User Response:

2370C PENDING EXTERNAL LINKAGE DISPLAY Explanation: This message introduces the display of applications with external

linkages. System Action: User Response:

2371W INVALID JOBNAME/NUMBER Explanation: The JOBINFO command specified a job name or number that could not be

found. System Action: User Response: Correct the job name or number and try again.

2372C SCHEDULE LIST Explanation: This message introduces the display of the LISTSCH command. System Action: User Response:

2373W EVENT DATASET WITH ID xxxx NOT FOUND Explanation: The DEFERRED parameter in a LISTSCH command specified an event data

set which is not defined to ESP. System Action: No events are listed. User Response: Correct the DEFERRED parameter and try again.

2374W NO EVENTS HELD IN CLASS xxxx Explanation: The held class specified in the HELD parameter of a LISTSCH command

was not found. System Action: No events were listed. User Response: Correct the HELD parameter and try again.

2375I OK Explanation: This message indicates that the CLASS command was successful. System Action: Processing continues. User Response: None.

2376W NO MATCHING ENTRIES FOUND Explanation: A CLASS RESUME command specified a class name mask for which no

matching entries were found. System Action: User Response: Correct the CLASS name mask and try again.

Messages and Codes

ESP-5.4-MC-03 301

2377I nn ENTRIES RESUMED Explanation: This message indicates that a CLASS RESUME command has been

successful. System Action: User Response:

2378W NO MATCHING ENTRIES FOUND Explanation: A CLASS PROCESS command specified a class name mask for which no


2379I nn ENTRIES TAKEN OUT OF IGNORE STATUS Explanation: A CLASS PROCESS command has successfully removed the IGNORE status

from one or more class entries. System Action: User Response:

2380W NO MATCHING ENTRIES FOUND Explanation: A CLASS DEEXEMPT command specified a class name mask for which no


2381I nn ENTRIES DEEXEMPTED Explanation: This message indicates that a CLASS DEEXEMPT command has been

successful. System Action: User Response:

2382I nnxxxx{| RELEASED} FROM CLASS yyyy Explanation: This message summarizes the activity performed by a CLASS EXEMPT,

RELEASE, or FLUSH command. System Action: User Response:

2383I DELETE REQUEST MUST BE ISSUED FROM A CONSOLE Explanation: A HISTFILE command was issued to delete a history file. The command

was not issued by a console. System Action: The delete request is not processed. User Response: Issue the command from a system console.

2384E NO SPACE LEFT IN CHECKPOINT Explanation: The HISTFILE command could not obtain space in the checkpoint to hold

the Histfile checkpoint element. System Action: The HISTFILE request is not processed. User Response: Use the LISTCKPT command to determine the amount of space remaining in

302 ESP-5.4-MC-03

the checkpoint.

2385I NEXT JOB INDEX DATASET BACKUP AT xxxx ON yyyy Explanation: This message displays when the next backup will be for the job index

database. System Action: User Response: To change the backup schedule, use the BKUPJNDX command with a valid

scheduling criterion. To perform an immediate backup, use the BKUPJNDX command with no operands.

2386I NO JOB INDEX BACKUP TIME SET Explanation: A BKUPJNDX command was issued to display the next backup time for the

job index database, but no backup time has been scheduled. System Action: User Response: To change the backup schedule, use the BKUPJNDX command with a valid

scheduling criterion. To perform an immediate backup, use the BKUPJNDX command with no operands.

2387E NO SPACE LEFT IN CHECKPOINT Explanation: There is no space in the checkpoint file with which to record a backup

schedule for the job index database. System Action: No backup has been scheduled for the job index database. User Response: Wait until some scheduled events have been triggered, and try again.

To perform an immediate backup of the job index database, use the BKUPJNDX command with no operands.

2388W HISTFILE xxxx NOT FOUND Explanation: The BKUPHIST command specified an undefined history file id. System Action: User Response: Correct the history file id and try again.

2389C HISTORY DATASET STATUS Explanation: This message introduces a display of the status of the history files. System Action: User Response:

2390W HISTFILE xxxx NOT FOUND Explanation: The LISTHIST command specified a history file id which was not defined

to ESP. System Action: User Response: Correct the history file id and try again.

2391W NO HISTORY DATASETS DEFINED Explanation: A LISTHIST command with no operands was issued, but no history files

have been defined to ESP. System Action: User Response:

Messages and Codes

ESP-5.4-MC-03 303


2393E INVALID P-NODE NAME xxxx Explanation: A DEFTM command was issued which contained an invalid P-node name. System Action: The track model is not defined or replaced. User Response: Reenter the command specifying a correct P-node name.

2394E INVALID P-NODE/DUE OUT TIME SYNTAX xxxx Explanation: A DEFTM command was issued which contained an invalid P-node name or

due out time specification. System Action: The track model is not defined or replaced. User Response: Reenter the command specifying a correct P-node name and optional due

out time.

2395E ERROR SCANNING COMMAND, RC=nn Explanation: A problem was encountered while parsing the command line. System Action: The command is ignored. The user is prompted for a new command. User Response: If the problem persists, notify your support personnel.




2398I TRACK MODEL xxxx{ REPLACED | ADDED} Explanation: The DEFTM command has successfully defines or altered a job tracking

model. System Action: User Response:

2399I TRACK MODEL DELETED Explanation: The DELTM command has successfully deleted the job tracking model. System Action: User Response:

2400C MODEL DISPLAY Explanation: This message introduces the result of a LISTTM command. System Action:

304 ESP-5.4-MC-03

User Response:

2401I NO MATCHING ENTRIES FOUND LEVEL xxxx Explanation: The LISTM command specified a tracking model name mask which matched

no job tracking models. System Action: User Response: Correct the mask and try again.

2402I JOB {PREFIX }xxxx DEFINED Explanation: The DEFTJ command has successfully defined the tracking parameters for

the specified job name or prefix. System Action: User Response:

2403W MODEL NAME REQUIRED FOR DEFINE REQUEST Explanation: A DEFTJ command was issued without a MODEL parameter. This is a

required parameter for the DEFTJ command. System Action: User Response: Add a MODEL parameter and try again.

2404I nn xxxx ALTERED LEVEL yyyy Explanation: The ALTTJ command has successfully altered the characteristics of one

or more jobs which match the job name specification. System Action: None. User Response: None.

2405I JOB {PREFIX }xxxx ALTERED Explanation: The ALTTJ has successfully altered the characteristics of this job or

prefix. System Action: User Response:

2406I NO MATCHING PREFIX ENTRIES FOUND Explanation: The LTJ command specified a job name prefix for which no matching

prefixes were found. System Action: User Response: Correct the job name prefix and try again.

2407I PREFIX xxxx NOT FOUND Explanation: The LTJ command specifies a prefix which has not been defined to ESP. System Action: User Response: Correct the prefix and try again, or define the prefix with DEFTJ.

2408I P-NODE xxxx{ REPLACED | ADDED} Explanation: The DEFPN command has successfully defined or altered a processing

node. System Action: The processing node has been defined or altered. User Response:

Messages and Codes

ESP-5.4-MC-03 305

2409I P-NODE xxxx DELETED Explanation: The DELPN command has successfully deleted the specified processing

node. System Action: The processing node has been deleted. User Response:

2410C P-NODE DISPLAY Explanation: This message introduces the listing of the definition of one or more

processing

2411E JOB/ACCOUNT AUTHORITY STRINGS NOT PAIRED Explanation: In a DEFAT command, the INCLUDE and EXCLUDE parameters must specify

a sequence of job name/authstring pairs. The pairs are separated from one another by blanks. Within a single pair, the job name and the authstring are separated by a comma. For example, INCLUDE(JOBABC-,AUTHCOD0 JOBDEF-,AUTHCOD1 JOBGHI-,AUTHCOD2).

System Action: The authorization table was not defined. User Response: Correct the INCLUDE or EXCLUDE parameter and try again.

2412I JOB AUTHORITY TABLE xxxx{ REPLACED | ADDED} Explanation: The DEFAT command has successfully defined or altered the

authorization table. System Action: User Response:

2413I JOB AUTHORITY TABLE xxxx DELETED Explanation: The DELAT command has successfully deleted the authorization table. System Action: User Response:

2414C JOB AUTH TABLE DISPLAY Explanation: This message introduces the display of the authorization table that

was specified in the LISTAT command. System Action: User Response:

2415W INVALID JOB NAME/NUMBER xxxx Explanation: The LJ command specified a job identifier that was syntactically

incorrect. System Action: No job information was listed. User Response: The operand to LJ must be either a job number (without a 'J' prefix),

a job name, or a job name followed by a parenthesized job number. Examples are 'LJ 6635', 'LJ JOBNAME', and 'LJ JOBNAME(J6635)'. A valid job number is within the range 1 through 65534, inclusive.

306 ESP-5.4-MC-03

2416W NO DOCUMENTATION AVAILABLE FOR xxxx Explanation: The job documentation library contains no member for this job. ESP

has searched the DOCLIB data set for a member whose name is the same as the job name, unless a DOCMEM statement a different member name. No such member was found.


2417W JOB DOCUMENTATION DATA SET NOT DEFINED Explanation: ESP could not search the documentation library since there was no

DOCLIB statement in the ESPPROC. System Action: All documentation processing is ignored. User Response: Add a DOCLIB statement to the ESPPROC. If ESP is being executed from

TSO, a TSO ALLOC statement can be used to allocate the JOBDOC file. If ESP is being executed from batch, a JOBDOC DD statement can be present.

2418I NO TCELL POOLS DEFINED Explanation: In response to a LTCELL command, this message indicates that no TCELL

pools have been defined. System Action: User Response:

2419I NO MATCHING ENTRIES FOUND LEVEL xxxx Explanation: An LTJ command was issued, but no job names were found that matched

the job name mask. System Action: User Response: Correct the job name mask and try again.

2420I NO MATCHING ENTRIES FOUND LEVEL xxxx Explanation: The LISTPN command specified a processing node name mask which did not

match any processing nodes that are defined to ESP. System Action: User Response: Correct the processing node mask and try again.

2421I NO MATCHING ENTRIES FOUND LEVEL xxxx Explanation: The LISTAT command specified an authorization table mask which did not

match the name of any authorization table defined to ESP. System Action: User Response: Correct the authorization table mask and try again.

2422I JOB {PREFIX }xxxx DELETED Explanation: The DELTJ has successfully deleted a tracked job definition from the

job index file. System Action: The tracked job definition was deleted. User Response:

Messages and Codes

ESP-5.4-MC-03 307

2423W INVALID JOBNAME/NUMBER Explanation: The JOBINFO command specified a job identifier that was syntactically

incorrect. System Action: No job information was listed. User Response: The operand to JOBINFO must be either a job number (without a 'J'

prefix), a job name, or a job name followed by a parenthesized job number. Examples are 'JOBINFO 6635', 'JOBINFO JOBN', and 'JOBINFO JOBN(J6635)'.

2424W xxxx Explanation: An error occurred processing the alternate queue data set. The text of

the message fully describes the problem. System Action: This message is followed by message 0322W. User Response: Respond to the message that follows.

2425W INVALID RESPONSE Explanation: An invalid response was given to message 0313A. System Action: The prompt is reissued. User Response: Respond to the reprompt.

2426E ERROR OCCURRED READING/WRITING END RECORD FOR JOB xxxx

Explanation: A job tracking record was being updated when a job was forced complete when an I/O error occurred on the track file. The error will have been described by a preceding message.


2427E ERROR OCCURRED READING/WRITING xxxxx RECORD FOR JOB yyyy

Explanation: A job tracking record was being updated at job purge/transmit time when an I/O error occurred on the track file. The error will have been described by a preceding message. The message indicates whether a normal purge (PURGE) or JES3 BDT transmit (TRANSMIT) record was being processed.


2428E ERROR OCCURRED UPDATING INFOSERV DATA FOR JOB xxxx Explanation: A job tracking record's Infoserv data was being updated at job

termination time or at job purge when an I/O error occurred on the track file. The error will have been described by a preceding message.


308 ESP-5.4-MC-03

2429E INVALID TRACKING ELEMENT CODE DETECTED, nn Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

2430W JOB TRACKING SUSPENDED DUE TO PRIOR REQUEST Explanation: Jobs are not being tracked because a TRACKING NOSTORE command had been

issued. System Action: User Response: To resume job tracking, issue the TRACKING STORE command.

2431E INVALID JOB AUTHORITY TABLE GENERATED Explanation: System Action: User Response:

2432W JOB xxxx ALREADY DEFINED Explanation: The DEFTJ command specified a job name that was already defined. System Action: The job name or prefix was not redefined. User Response: Delete the tracking parameters for this job name by using the DELTJ

command, and then try the DEFTJ command again.

2433W PREFIX xxxx ALREADY EXISTS Explanation: The DEFTJ command specified a job prefix that was already defined. System Action: The job name or prefix was not redefined. User Response: Delete the tracking parameters for this job prefix by using the DELTJ

command, and then try the DEFTJ command again.

2434W {PREFIX ENTRY |INDEX ENTRY }xxxx NOT FOUND Explanation: A DELTJ command specified a job name or prefix that was not defined to

ESP. System Action: User Response: Correct the job name or prefix and try again.

2435W TRACK MODEL xxxx ALREADY EXISTS Explanation: The DEFTM command specified a job tracking model that is already

defined to ESP. System Action: User Response: Correct the job tracking model name and try again.

2436W TRACK MODEL xxxx NOT FOUND Explanation: A DELTM command specified a job tracking model that was not defined to

ESP. System Action: User Response: Correct the job tracking model name and try again.

Messages and Codes

ESP-5.4-MC-03 309

2437E TRACK MODEL xxxx IS INVALID Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

2438W P-NODE xxxx ALREADY EXISTS Explanation: A DEFPN command specified a processing node name that has already been

defined to ESP. System Action: User Response: Correct the P-node name, or delete the P-node first with DELPN, and

then try again.

2439W P-NODE xxxx NOT FOUND Explanation: A DELPN command specified a processing node name that was not defined

to ESP. System Action: User Response: Correct the P-node name and try again.

2440W JOB AUTHORITY TABLE xxxx ALREADY EXISTS Explanation: A DEFAT command specifies an authorization table name that has already

been defined to ESP. System Action: User Response: Correct the authorization table name, or delete the authorization

table first with DELAT, and then try again.

2441W JOB AUTHORITY TABLE xxxx NOT FOUND Explanation: A DELAT command specifies an authorization table that has not been

defined to ESP. System Action: User Response: Correct the authorization table name and try again.

2442I JOB NOT FOUND OR ACCESS DENIED Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

2443W FUNCTION NOT SUPPORTED YET Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

2444E I/O ERROR READING JOB AUTHORITY TABLE Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

310 ESP-5.4-MC-03

2445W JOB AUTHORITY TABLE xxxx NOT FOUND FOR USER yyyy Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

2446W INVALID JOBNAME/NUMBER nn Explanation: The job identifier is syntactically incorrect. System Action: User Response: The job identifier must be either a job number (without a 'J' prefix),

a job name, or a job name followed by a parenthesized job number. Examples are '6635', 'JOBNAME', and 'JOBNAME(J6635)'. A valid job number is within the range 1 through 65534, inclusive.

2447W P-NODE xxxx NOT FOUND Explanation: A POST command was issued specifying a P-node that was not found on

the queue data set. System Action: The POST request is not processed. User Response: Specify the correct P-node name. If you are sure the P-node exists,

post the job using a job number rather than job name.

2448W Job xxxx(yyyy) not on TRAKFILE Explanation: An internal ESP/WM error has occurred.

xxxx specifies the job name. yyyy specifies the job identifier.

System Action: User Response: Please contact Cybermation for further assistance.

2449C JOB xxxx LISTING Explanation: This message introduces the listing produced by the LJ command. System Action: User Response:

2450W NO RESPONSE RECEIVED FROM SUBSYSTEM Explanation: The command was sent to the ESP subsystem for processing, but no

response was received. System Action: User Response: Check the status of the ESP subsystem. It may need to be restarted.

2451E COMMAND IGNORED, SHOULD BE LESS THAN 116 CHARACTERS Explanation: An OPER command was issued, but it was too long. System Action: The command was not executed. User Response: The command must be shortened before being re-issued.

2452I COMMAND ACCEPTED BY SUBSYSTEM Explanation: This OPER command has been successfully sent to the ESP subsystem for

processing.

Messages and Codes

ESP-5.4-MC-03 311






2456I SYMLIB xxxx{ REPLACED| ADDED} Explanation: The DEFSYML command has successfully added or replaced a symbol

library set. System Action: The symbol library set has been added or replaced. User Response:

2457I SYMLIB xxxx DELETED Explanation: The DELSYML command has successfully deleted a symbol library set. System Action: The symbol library set has been deleted. User Response:

2458I NO ENTRIES FOUND MATCHING xxxx Explanation: The LISTSYML command specified a symbol library name mask that did not

match any symbol library names defined to ESP. System Action: User Response: Correct the symbol library set name mask and try again.

2459I NO TIME ZONES DEFINED Explanation: An LTZONE command was issued, but no time zones have been defined. System Action: User Response: Time zones can be defined with the TIMEZONE command.

2460E NOT AUTHORIZED FOR SYMLIB DEFINE/DELETE Explanation: This user is not authorized to define or delete symbol library sets. System Action: The requested function was not performed. User Response: In a non-SAF system, the user must have either special, calendar, or

312 ESP-5.4-MC-03

scheduler authority. In a SAF system, the user must have alter access to the resource SYMLIB.symname.

2461E INCOMPLETE SYMBOL ASSIGNMENT STATEMENT Explanation: System Action: User Response:

2462E COMMAND xxxx NOT DEFINED Explanation: System Action: User Response:




2466E INVALID COMPARATOR xxxx Explanation: This operator is invalid. A binary comparator operator is required.

Only EQ, NE, GT, GE, LT, and LE and their symbolic equivalents are allowed.

System Action: User Response: Correct the operator and resubmit the report.

2467E INVALID SELECTION CRITERIA xxxx Explanation: The selection criteria in this CRITERIA subcommand were invalid. System Action: The report was not produced. User Response: Please consult the ESP Command Reference to find the correct syntax

for the CRITERIA subcommand.

2468E INCOMPLETE INPUT STATEMENT Explanation: This report subcommand is incomplete. System Action: The report was not produced. User Response: Please complete the subcommand and resubmit the report.

2469W 'OR' INVALID OUTSIDE OF A CRITERIA SECTION, IGNORED Explanation: The OR keyword is valid when describing selection criteria in a

CRITERIA subcommand. It is valid nowhere else.

Messages and Codes

ESP-5.4-MC-03 313

System Action: The report was not produced. User Response: Correct the subcommand and resubmit the report.

2470E BREAK FIELD NOT DEFINED FOR DISPLAY Explanation: The field name in the BREAK statement must have been specified in a

previous DISPLAY statement. System Action: The report was not produced. User Response: Correct the BREAK statement and resubmit the report.

2471E MISSING COMPARISON LENGTH FOR BREAK Explanation: The BREAK statement must specify a numeric length field. This length

describes the number of characters in the display field which are checked. When a mismatch occurs within this portion of the display field, then a break occurs.

System Action: The report was not produced. User Response: Correct the BREAK statement and resubmit the report.

2472W REPORT DEFINITION INCOMPLETE / NO DISPLAY ENTRIES Explanation: Each report definition must contain either a DISPLAY statement or a

COPY statement. Without these statements, there is no way for ESP to format the report or write the history file records.

System Action: The report was not produced. User Response: Add a DISPLAY or a COPY statement and resubmit the report.

2473E REPORT BYPASSED DUE TO ABOVE ERRORS Explanation: The report was not generated because of errors found by ESP in the

report definition. System Action: The report was not produced. User Response: Check the previous error messages, correct the report definition and

resubmit the report.

2474I NO RECORDS FOUND TO MATCH SPECIFIED CRITERIA Explanation: No errors were found in the report definition, but no history file

records were found that match the selection criteria. System Action: The report was not produced. User Response: If this is not the intended result, then modify the selection criteria

in the report definition and resubmit the report.

2475E UNABLE TO OPEN xxxx yyyy Explanation: An I/O error was encountered while trying to open an input file.

The file type is specified by xxxx. The file value is specified by yyyy.

System Action: The report is not produced. User Response: Correct the I/O problem and resubmit the report.

2476E xxxx Explanation: An I/O error was encountered while trying to open the COPY file. System Action: The report was not produced.

314 ESP-5.4-MC-03

User Response: Correct the I/O problem and resubmit the report.

2477E xxxx Explanation: An I/O error occurred during the processing of a history file. System Action: The report was not produced. User Response: Correct the I/O problem and resubmit the report.

2478E xxxx Explanation: An I/O error occurred while writing to a COPY file. System Action: The report was not produced. User Response: Correct the I/O problem and resubmit the report.

2479E INVALID REQUEST CODE DETECTED Explanation: The history file request processor was passed an invalid request code.

This would normally only happen due to a logic error. System Action: The request is not processed. User Response: Notify your software support personnel.

2480W TRACKING FACILITY NOT ACTIVE Explanation: A user or operator entered a history file that requires the tracking

facility be active. The tracking facility was not active. System Action: The request is not processed. User Response: The tracking facility may be inactive because the appropriate

parameters were not specified in the initialization parameter file, or due to an error during initialization. If you are in doubt, ask your installation support personnel.

2482E INVALID DATABASE RECORD TYPE xxxx REQUESTED Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

2483E INVALID DATABASE REQUEST TYPE xxxx SPECIFIED Explanation: An internal ESP error has occurred. System Action: User Response: Please contact Cybermation for further assistance.

2484E YOU ARE NOT DEFINED TO xxxx Explanation: Your user id has not been defined to the ESP subsystem. System Action: Your userid will not be permitted to define or delete Events. User Response: Request the ESP administrator to define your userid to the system.

2485E xxxx IS NOT AUTHORIZED IN THE UPDT OR BY SAF Explanation: Either the event prefix specification (normally equivalent

to a security user ID) xxxx is not defined in the User Profile Definition Table, or the user ID xxxx is not authorized by SAF to perform this action.

System Action: The request is denied.

Messages and Codes

ESP-5.4-MC-03 315

User Response: Notify your installation security administrator.

2486E INVALID PASSWORD SPECIFIED Explanation: An invalid current password was specified when changing the password

or accessing ESP through a batch job. System Action: The access to ESP is denied. User Response: Ensure a correct current password is specified.

2487W COMMAND NOT AUTHORIZED Explanation: System Action: User Response:

2488I SPECIAL USER ATTRIBUTES ASSIGNED Explanation: System Action: User Response:







2494W NEXT PROCESSING ENDED AFTER nnn SUSPENDED SCHEDULES Explanation: The NEXT command could not find another scheduled execution time of

this event. The event has a large suspend count, and there are not sufficient RESUMEs pending to reduce this count.

System Action: NEXT processing ends.

316 ESP-5.4-MC-03

User Response:

2495W EVENT IS CURRENTLY SUSPENDED WITH NO SCHEDULED RESUME

Explanation: The NEXT command could not find another scheduled execution time of this event. The event is suspended, and there are no scheduled RESUMEs.


2496E xxxx Explanation: The INVOKE command encountered an error while opening a data set for




2497E xxxx Explanation: The SUBMIT command encountered an error while opening a CA-Panvalet

data set for verification purposes during the definition of an Event. The message text fully describes the error.



2498E xxxx Explanation: The SUBMIT command encountered an error while opening a CA-Librarian




2499E xxxx Explanation: The COPYJCL command encountered an error while opening a data set for




2500E xxxx Explanation: The SUBMIT command encountered an error while opening a




Messages and Codes

ESP-5.4-MC-03 317

2501I EVENT xxxx.yyyy, {SUSPEND|HOLD} COUNT {INCREMENTED|DECREMENTED}, HOLD(nn), SUSP(nn)

Explanation: The suspend or hold count of this event have been successfully modified.


2502I EVENT TRIGGERED Explanation: A TRIGGER command has successfully triggered the event. System Action: The event has been triggered. User Response:

2503I SCHEDULED EXECUTION AT xxxx ON yyyy WILL BE BYPASSED Explanation: A TRIGGER NOXEQ command has been issued, and the next scheduled

execution of the event will be bypassed. System Action: User Response:

2504W SCHEDULED OCCURRENCE NOT FOUND Explanation: A TRIGGER NOXEQ command was issued, but no scheduled execution of this

event could be found. System Action: No scheduled execution is being bypassed. User Response:

2505E MEMBER NAME OMITTED FOR PANVALET DATA SET xxxx Explanation: A member name must be specified when submitting from a CA-Panvalet

data set. System Action: The job was not submitted. User Response: Specify a member name in parentheses after the data set name, or in

the MEMBER keyword, and try again.

2506E MEMBER NAME OMITTED FOR LIBRARIAN DATA SET xxxx Explanation: A member name must be specified when submitting from a CA-Librarian

data set. System Action: The job was not submitted. User Response: Specify a member name in parentheses after the data set name, and try

again.


When nn=12: invalid parameters passed to parse from CP. nn=16: No space available. nn=20: Validity check routine termination. nn=24: An error in input parameters was detected in the IKJPARS2 load module.

318 ESP-5.4-MC-03

nn=28: A line drop condition was detected and IKJPTGT (PUTGET I/O service routine) or IKJPUTL (PUTLINE I/O service routine) set return codes of 24 and 32 respectively.








2512I nn GROUPS DISPLAYED Explanation: The LISTGRP has displayed nn group definitions. System Action: None. User Response: None.

2515I nn USERS DISPLAYED Explanation: The LISTUSER has displayed nn user definitions. System Action: None. User Response: None.


When nn=12: invalid parameters passed to parse from CP. nn=16: No space available. nn=20: Validity check routine termination. nn=24: An error in input parameters was detected in the IKJPARS2 load module. nn=28: A line drop condition was detected and IKJPTGT (PUTGET I/O service routine) or IKJPUTL (PUTLINE I/O service

Messages and Codes

ESP-5.4-MC-03 319

routine) set return codes of 24 and 32 respectively. If the problem persists, notify your support personnel.







2521E INVALID LOGICAL DAY SHIFT VALUE xxxx Explanation: In the DEFCAL command, the SHIFT value must be specified as "hh:mm",

where hh is a number less than 24, and mm is a number less than 60. System Action: User Response: Correct the SHIFT parameter and try again.

2522I CALENDAR xxxx {ALTERED|DELETED|DEFINED} Explanation: A DEFCAL, ALTCAL, or DELCAL command has successfully processed this

calendar. System Action: User Response:

2523W NO MATCHING CALENDARS FOUND Explanation: A LISTCAL command was issued, but no matching calendars are defined to

ESP. System Action: User Response: Correct the calendar name mask, or define a calendar to ESP, and try

again.


320 ESP-5.4-MC-03









2529E YOU ARE NOT DEFINED TO xxxx Explanation: Your userid has not been defined to the ESP subsystem. System Action: Your userid will not be permitted to define or delete Events. User Response: Request the ESP administrator to define your userid to the system.

2530E YOU ARE NOT AUTHORIZED TO GROUP xxxx Explanation: You attempted to access a group prefix to which you are not

authorized. System Action: The request is denied. User Response: Ensure you access only the groups to which you are authorized.

2531I NO DEFAULT GROUP NAME SET Explanation: A GROUP command was issued with no operands, in order to display the

current default group prefix. However, no group prefix has been established.

System Action:

Messages and Codes

ESP-5.4-MC-03 321

User Response: Use the GROUP command to set a default group prefix.

2532I CURRENT DEFAULT GROUP IS xxxx Explanation: This is the current default group prefix, as established by the

previous GROUP command. System Action: User Response: To change the group prefix, use the GROUP command with an operand.

2533E INVALID PASSWORD SPECIFIED Explanation: The PASSWORD command specified the wrong "current" password. To

change to a new password, both the "current" password and the "new" one must be specified.

System Action: User Response: Correct the current password and try again.

2534I EVENT ALTERED Explanation: The ALTEVENT command has successfully altered this event. System Action: The event has been altered. User Response:

2535I nn xxxx ALTERED Explanation: The ALTEVENT command has successfully altered one or more events that

matched the event name specification. System Action: One or more events were altered. User Response:

2536I RACF DATA UPDATED Explanation: The DEFAULT command has successfully established the default values

for RACF parameters. These parameters are inserted into the JOB statements of all jobs submitted by ESP, unless those parameters are already present on the JOB statement. These parameters are USER, GROUP, and PASSWORD.


2537W 'TIMESEQ' AND 'ALL' INCOMPATIBLE, 'TIMESEQ' IGNORED Explanation: On a LIST command, the TIMESEQ and ALL keywords cannot appear

together. The TIMESEQ keyword causes the events to be displayed in the order of next execution time. The ALL keyword causes all available information to be displayed for each event, not just for next execution time. The intention of TIMESEQ is to display the upcoming sequence of events. The intention of ALL is to display the entire definition of the events.

System Action: User Response: Remove either one of these keywords and try again.

2542I DATASET TRIGGERING NOT ACTIVE Explanation: A LISTDTE command was entered. Data set triggering is not currently

322 ESP-5.4-MC-03

active. System Action: None. User Response: If required, ensure data set triggering is active.

2544E INVALID JOURNAL SMF RECORD NUMBER SPECIFIED Explanation: A non-numeric value or a numeric value outside the range 128-255 was

specified on the SMFREC initialization statement. System Action: The initialization statement is ignored. This message is followed by

message 0802A. User Response: Respond to message 0802A.

2545E INVALID DAY OF WEEK NAME xxxx Explanation: An invalid day of week name was specified to the WKSTART

initialization statement. The valid days are SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY and SATURDAY. The names may be abbreviated down to the first 3 characters.

System Action: The initialization statement is not processed. The operator is reprompted to correct the statement.

User Response: Enter a valid day, or list of days.

2546E INVALID DAY OF WEEK NAME xxxx Explanation: An invalid day of week name was specified to the WORKDAYS

initialization statement. The valid days are SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY and SATURDAY. The names may be abbreviated down to the first 3 characters.

System Action: The initialization statement is not processed. The operator is reprompted to correct the statement.

User Response: Enter a valid day, or list of days.

2547C SYSTEM MESSAGE LIST Explanation: The system messages currently being intercepted by ESP are listed in

response to a LSYSMSGS command. System Action: None. User Response: None.

2548C COMMAND PREFIX SUBSTITUTIONS Explanation: The command prefix substitutions currently in effect via the CMDPRFX

command are listed in response to a LCMDPRFX command. System Action: None. User Response: None.

2549C TRACKING DATA ANALYSIS Explanation: The current job tracking XME usage is listed in response to a LISTXMEZ

command. System Action: None. User Response: None.

Messages and Codes

ESP-5.4-MC-03 323

2550E INVALID COLUMN VALUE OR RANGE Explanation: The COL keyword was specified on a SYSMSGS command or initialization

statement. Either the start or end column value was greater than 132 or the end column value was greater than the start column value.

System Action: The command or initialization statement is ignored. If the error occurred on an initialization statement, this message is followed by message 0802A.

User Response: Correct the command or respond to message 0802A and correct the initialization statement.

2551E INVALID ROUTING OR DESCRIPTOR CODE Explanation: The ROUTE or DESC keyword was specified on a SYSMSGS command or

initialization statement. A code outside the range 1:16 was specified.



2552E INVALID EVENT ID xxxx SPECIFIED FOR SYSMSGS' Explanation: The EVENT keyword was specified on a SYSMSGS command or initialization

statement. The Event id value contains incorrect syntax according to Event naming rules.



2553E ID REQUIRED FOR IGNORE OPTION OF SYSMSGS STATEMENT Explanation: The IGNORE keyword was specified on a SYSMSGS command or

initialization statement. The IGNORE keyword requires the ID keyword also be specified. The ID keyword was not specified.



2554E INVALID DATE FORMAT xxxx Explanation: An invalid date format was specified on a DATEFORM command or

initialization statement. System Action: The command or initialization statement is ignored. If the error

occurred on an initialization statement, this message is followed by message 0802A.


324 ESP-5.4-MC-03


This is a confirmation that the command has completed successfully. System Action: None. User Response: None.

2556I DATA SET TRIGGER DELAY VALUE CURRENTLY SET AT nn xxxx Explanation: The data set trigger delay was set and/or listed in response to a

DSTRDLY command or initialization statement. System Action: If requested, the data set trigger delay is altered. User Response: None.

2558I TRACKING OPTIONS: Explanation: The job tracking options were set and/or listed in response to a

TRACKOPT command or initialization statement. System Action: If requested, the job tracking options are altered. User Response: None.

2559I EVENT SEND WTO RESTRICTED Explanation: The use of a WTO in an Event was restricted in response to an EVENTWTO

command. System Action: ESP will not permit WTOs within an Event definition. User Response: The EVENTWTO command has been superseded by the EVENTOPT command.

Use the EVENTOPT command to restrict WTO access in an Event.

2560I EVENT SEND WTO ALREADY RESTRICTED Explanation: An EVENTWTO command was issued to restrict the use of WTOs in an

Event. The use of WTOs in an Event was already restricted. System Action: The command is ignored. User Response: The EVENTWTO command has been superseded by the EVENTOPT command.

Use the EVENTOPT command to restrict WTO access in an Event.

2561I EVENT SEND WTO DERESTRICTED Explanation: The restriction on use of a WTO in an Event was removed in response to

an EVENTWTO command. System Action: ESP will permit the use of WTOs within Event definitions. User Response: The EVENTWTO command has been superseded by the EVENTOPT command.

Use the EVENTOPT command to permit WTO access in an Event.

2562I EVENT SEND WTO NOT RESTRICTED Explanation: An EVENTWTO command was issued to remove the restriction on the use of

WTOs in an Event. The use of WTOs in an Event was already permitted. System Action: The command is ignored. User Response: The EVENTWTO command has been superseded by the EVENTOPT command.

Use the EVENTOPT command to permit WTO access in an Event.

Messages and Codes

ESP-5.4-MC-03 325

2563I EVENT SEND WTO FACILITY {NOT }RESTRICTED Explanation: The status of use of a WTO in an Event was listed in response to an

EVENTWTO command. System Action: None. User Response: The EVENTWTO command has been superseded by the EVENTOPT command.

Use the EVENTOPT command to list the status of WTO access in an Event.

2564I EVENT OPTIONS: Explanation: The Event options were set and/or listed in response to a EVENTOPT

command or initialization statement. System Action: If requested, the Event options are altered. User Response: None.

2565I NULL PASSWORD Explanation: The password string placed on JOB cards to designate a string to be

substituted was listed in response to a NULLPSWD command or initialization statement.


2566I NO SYSTEM MESSAGES ARE BEING SCANNED Explanation: A LSYSMSGS command was entered to list the system messages currently

being intercepted by ESP. No messages are currently being intercepted by ESP.


2567I NO COMMAND PREFIX SUBSTITUTION IN EFFECT Explanation: A LCMDPRFX command was entered to list the command prefix

substitutions currently in effect. No command prefix substitutions are currently in effect.


2568I SPUSER xxxx ALREADY DEFINED Explanation: An SPUSER command or initialization statement was issued to define an

initial userid to have access to perform user and group definitions. The userid specified has already been defined by a previous SPUSER command or initialization statement.

System Action: The command or initialization statement is ignored. User Response: Ensure you specify the correct userid.

2569I DATE FORMAT SET Explanation: The date format was altered by a DATEFORM command or initialization

statement. System Action: The date format is changed to the format specified on a DATEFORM

command or initialization statement.

326 ESP-5.4-MC-03


2570I CURRENT DATE FORMAT IS xxxx Explanation: The current date format was listed in response to a DATEFORM command

or initialization statement. System Action: None. User Response: None.

2571I CURRENT DATE FORMAT IS DEFAULT OF YMD Explanation: The current date format was listed in response to a DATEFORM command

or initialization statement. The current date format is the default value YMD.


2572W TRACE FACILITY NOT CURRENTLY ACTIVE Explanation: A CKPTRACE command or initialization statement was entered to activate

tracing of Checkpoint related functions. The ESP general trace facility is required and is not currently active.

System Action: The command or initialization statement is ignored. User Response: Activate the ESP general trace facility and re-issue the CKPTRACE

command.

2573I JOB xxxx(yyyy) AUTOPOSTED FROM EXEC Explanation: At initialization or as the result of a QUPDATE command, ESP detected

that the job queue status of the identified job had not been updated, and that a mismatch existed between the JES status and the ESP status. In this case, the job is in on the ESP exec queue but not on the JES exec queue. This could happen at any time where ESP had not received an explicit notification of job start, job end or purge. This situation can arise when jobs are active when the system is brought down or crashes, or if ESP is down for an extended period.



2574I JOB xxxx(yyyy) AUTOPOSTED FROM OUTPUT Explanation: At initialization or as the result of a QUPDATE command, ESP detected

that the job queue status of the identified job had not been updated, and that a mismatch existed between the JES status and the ESP status. In this case, the job is on the ESP output queue but not on the JES output queue. This could happen at any time where ESP had not received an explicit notification of job start, job end or purge. This situation can arise when jobs are active when the system is brought down or crashes, or if ESP is down for an extended period.

System Action: The job is moved to the appropriate queue. The job is posted with a post id of 'SYSTEM!' to indicate that the post was not a normal post

Messages and Codes

ESP-5.4-MC-03 327

and that some data might be missing or inaccurate (e.g. time on queue etc.).


2575I JOB xxxx(yyyy) REQUEUED FOR EXECUTION Explanation: At initialization or as the result of a QUPDATE command, ESP detected

that the job queue status of the identified job had not been updated, and that a mismatch existed between the JES status and the ESP status. In this case, the job was on the JES input queue but not on the ESP input queue. This could happen at any time where ESP had not received an explicit notification of job start, job end or purge. This situation can arise when jobs are active when the system is brought down or crashes, or if ESP is down for an extended period.



2576E ERROR OCCURRED READING SYMTAB ENTRY xxxx Explanation: During Event execution, an error occurred attempting to read a symbol

table entry 'xxxx'. System Action: This message is followed by a message describing the error. User Response: Correct the error described by the message following this message.

2577E GROUP PREFIX xxxx NOT AUTHORIZED FOR SYMTAB yyyy Explanation: An Event requested a symbol table to which it was not permitted

access. System Action: The symbol data sets specified by the symbol table will not be read. User Response: The access to symbol tables is controlled by the ESP administrator.

2578I MESSAGE FROM EVENT xxxx.yyyy Explanation: During Event execution, a non-terminal condition occurred in Event

'xxxx.yyyy', resulting in a message being issued. System Action: A message follows this message describing the condition. User Response: If necessary, correct the condition described by the message

following this message.

2579E ERROR SCANNING COMMAND, RC=nn Explanation: A problem was encountered while parsing a command. System Action: The command is ignored. User Response: System routine IKJPARS returned error code nn.

When nn=12: invalid parameters passed to parse from CP. nn=16: No space available. nn=20: Validity check routine termination. nn=24: An error in input parameters was detected in the IKJPARS2 load module. nn=28: A line drop condition was detected and IKJPTGT (PUTGET I/O service routine) or IKJPUTL (PUTLINE I/O service

328 ESP-5.4-MC-03

routine) set return codes of 24 and 32 respectively. If the problem persists, notify your support personnel.

2580E DATA SET xxxx PARTITIONED AND NO MEMBER SPECIFIED Explanation: An INVOKE command was issued. The specified data set 'xxxx' is a

partitioned data set and a member name was not specified. System Action: The command is ignored. User Response: Correct the command by specifying a member name and re-issue the

command.

2581E xxxx Explanation: During the execution of an Event, an error occurred in a SUBMIT,

ROSSUB, PANSUB or LIBSUB command while reading the reading the data set to be submitted. The message text describes the error.

System Action: The Event execution will be bypassed. User Response: Correct the error described by the message text. If the problem

persists, notify your software support personnel.

2582E xxxx Explanation: An I/O error occurred opening an OS data set for a SUBMIT command in

the execution of an Event. System Action: The Event execution will be bypassed. User Response: Notify your software support personnel.

2583E xxxx Explanation: An I/O error occurred opening a data set for a SUBMIT

command in the execution of an Event. System Action: The Event execution will be bypassed. User Response: Notify your software support personnel.

2584E xxxx Explanation: An I/O error occurred opening a CA-Panvalet data set for a SUBMIT


2585E xxxx Explanation: An I/O error occurred opening a CA-Librarian data set for a SUBMIT


2586W UNABLE TO OBTAIN SUFFICIENT CSA FOR xxxx Explanation: There is insufficient CSA storage in the MVS system to process a RAXE

initialization statement. The storage may reside above the 16Mb line. System Action: The command is terminated. User Response: Take action to restore CSA levels or remove the initialization

statement.

Messages and Codes

ESP-5.4-MC-03 329

2587W EVENT FILE SUSPENDED Explanation: A request was made to access an event file which is currently in

suspended status. System Action: Processing continues. User Response: Contact your ESP administrator to have the event file reopened or

issue the EVENTSET operator command with the OPEN option if you are authorized.

2589C Default Resource Assignments Explanation: The default Resource assignments were set and/or listed in response to

a RESDFLT command or initialization statement specifying the LIST keyword.

System Action: If requested, the default Resource assignments are altered. User Response: None.

2590C RERUN MANAGER STEP JCL Explanation: The Rerun Manager step JCL was listed in response to a ERMSTEP command

or initialization statement. System Action: None. User Response: None.

2591I NO RERUN MANAGER JCL DEFINED Explanation: The Rerun Manager step JCL was listed in response to a ERMSTEP command

or initialization statement. There is no Rerun Manager step JCL defined.


2592C RESTART ACTION EXCLUSION DISPLAY Explanation: The Restart Action Exclusion entries were listed in response to a RAXE

command or initialization statement. System Action: None. User Response: None.

2593C ALERT DEFINITION DISPLAY Explanation: The Alert definitions were set and/or listed in response to a ALERTDEF

command or initialization statement. System Action: If requested, the Alert definitions are altered. User Response: None.

2595C PREALLOCATED DATA SET LIST Explanation: A pre-allocated data set was allocated, unallocated and/or listed in

response to a PREALLOC command or initialization statement. System Action: If requested, the specified data set is allocated or unallocated. User Response: None.

330 ESP-5.4-MC-03

2596W SCOREBOARD/SCHEDULE FILE NOT ACTIVE Explanation: A LOADSCHF or PURGSCHF command or initialization statement was entered

to load or purge a schedule file. The scoreboard or the schedule file was not active.

System Action: The command or initialization statement is terminated. User Response: Activate the scoreboard or schedule file.



2598I No default resource names defined Explanation: A RESDFLT command or initialization statement was entered to list the

default Resource assignments. No default Resource names were defined. System Action: None. User Response: None.

2599E MODEL, NODE or NETNODE required with XMITMDL DELETE Explanation: An XMITMDL command or initialization statement was issued to delete

a tracking model. The MODEL, NODE or NETNODE keywords were not specified. A global tracking model delete is not permitted.

System Action: The command or initialization statement is ignored. User Response: Specify the MODEL, NODE and/or NETNODE keyword operand(s) on the

"XMITMDL DELETE" command.

2600E Node name xxxx length exceeds 16 characters Explanation: An XMITMDL ADD command was specified with the NODE(xxxx) operand. NJE

node name xxxx is longer than the maximum permissible 16 characters. System Action: If the XMITMDL ADD command was specified in the ESPPARM initialization

file, then action message 802A is issued to prompt for an END reply to ignore the command, a CANCEL reply to terminate ESP/WM, or an ESP/WM initialization command reply. If the XMITMDL ADD command was specified as an ESP operator command, then it is ignored.

User Response: Correct the command or initialization statement to specify an NJE node name that does not exceed 16 characters.

2601E NODE NAME xxxx NOT DEFINED Explanation: An XMITMDL ADD command or initialization statement was entered with

the NODE keyword specified. The specified NODE is not defined. System Action: The command or initialization statement is ignored. User Response: Correct the command or initialization statement.

2602E MODEL xxxx NOT FOUND Explanation: An XMITMDL DELETE command or initialization statement was entered with

Messages and Codes

ESP-5.4-MC-03 331

the MODEL keyword specified. The specified MODEL is not currently defined.

System Action: The command or initialization statement is ignored. User Response: Correct the command or initialization statement.

2603E MODEL|{NODE and/or NETNODE} missing Explanation: An XMITMDL ADD command or initialization statement was entered.

Either the MODEL keyword operand was missing, or the NODE and/or NETNODE keyword operand(s) were missing.

System Action: The command or initialization statement is ignored. User Response: Correct the command or initialization statement.

2604I SCHEDULE FILE LOAD REQUEST QUEUED Explanation: A LOADSCHF command or initialization statement was entered to load a

schedule file. The request has been accepted. System Action: The LOADSCHF command is queued for processing. User Response: None.

2605I SCHEDULE FILE PURGE REQUEST QUEUED, nn ENTRIES SELECTED

Explanation: A PURGSCHF command or initialization statement was entered to purge a schedule file. The request has been accepted.

System Action: The PURGSCHF command is queued for processing. A total of 'nn' entries will be purged.


2606I NO RESTART ACTION EXCLUSION ENTRIES FOUND Explanation: The Restart Action Exclusion entries were listed in response to a RAXE

command or initialization statement. There are no Restart Action Exclusion entries defined.


2607I ALERT DEFINITION xxxx ADDED Explanation: An ALERTDEF ADD command or initialization statement was successfully

processed. System Action: The Alert definition 'xxxx' was added. User Response: None.

2608I ALERT DEFINITION xxxx DELETED Explanation: An ALERTDEF DELETE command or initialization statement was

successfully processed. System Action: The Alert definition 'xxxx' was deleted. User Response: None.

2609I ALERT DEFINITION xxxx ALTERED Explanation: An ALERTDEF ALTER command or initialization statement was successfully

processed.

332 ESP-5.4-MC-03

System Action: The Alert definition 'xxxx' was altered. User Response: None.

2610I ERROR PROCESSING ALERT COMMAND Explanation: An ALERTDEF ADD, DELETE or ALTER command or initialization statement

was entered. If ADD or ALTER was specified, the ID and/or EVENT keywords were not specified. If DELETE was specified, the ID keyword was not specified.

System Action: The command or initialization statement is terminated. User Response: Correct the command or initialization statement.

2611I ALERT DEFINITION xxxx NOT DEFINED Explanation: An ALERTDEF LIST, DELETE or ALTER command or initialization statement

was entered. The specified Alert ID was not currently defined. System Action: The command or initialization statement is terminated. User Response: Correct the command or initialization statement.

2612I ALERT DEFINITION xxxx ALREADY DEFINED Explanation: An ALERTDEF ADD command or initialization statement was entered. The

specified Alert ID has already been defined. System Action: The command or initialization statement is terminated. User Response: Correct the command or initialization statement.

2613E NODE operand of XMITMDL ADD invalid for ISCOPT NETWORK Explanation: An XMITMDL ADD command was specified with the NODE operand. However,

the ISCOPT statement in the ESPPARM initialization file specifies the NETWORK keyword operand, which indicates that only network (NDS) internodal job tracking is permitted. The NODE operand of the XMITMDL ADD command only applies to LU62 (TP Server) or NJE internodal job tracking.

System Action: If the XMITMDL ADD command was specified in the ESPPARM initialization file, then action message 802A is issued to prompt for an END reply to ignore the command, a CANCEL reply to terminate ESP/WM, or an ESP/WM initialization command reply. If the XMITMDL ADD command was specified as an ESP operator command, then it is ignored.

User Response: If the XMITMDL ADD command was specified in the ESPPARM initialization file, then reply to action message prompt 802A. Then either delete the XMITMDL ADD command in the ESPPARM initialization file or replace the NODE operand with the NETNODE operand to specify a network (NDS) node name. If the XMITMDL ADD command was specified as an ESP operator command, then if necessary, re-enter the command specifying the NETNODE operand instead of the NODE operand.

2614I DATA SET xxxx PREALLOCATED, DD NAME yyyy Explanation: A PREALLOC ALLOC command or initialization statement was successfully

processed. System Action: The data set 'xxxx' was allocated to DD name 'yyyy'.

Messages and Codes

ESP-5.4-MC-03 333


2615I DATA SET xxxx REMOVED FROM PREALLOCATION LIST Explanation: A PREALLOC UNALLOC command or initialization statement was

successfully processed. System Action: The data set 'xxxx' was deallocated. User Response: None.

2616I DATA SET xxxx ALREADY PREALLOCATED Explanation: A PREALLOC ALLOC command or initialization statement was entered. The

data set 'xxxx' was already preallocated. System Action: The command or initialization statement is terminated. User Response: Correct the command or initialization statement.

2617I DATA SET xxxx NOT CURRENTLY PREALLOCATED Explanation: A PREALLOC UNALLOC command or initialization statement was entered.

The data set 'xxxx' was not currently preallocated. System Action: The command or initialization statement is terminated. User Response: Correct the command or initialization statement.

2619I BAD TTPBF RECEIVED Explanation: The TP Server received a request unit. The length of the request unit

did not correspond with the expected length. System Action: The failure is logged and the request unit is discarded. User Response: Notify your system support personnel.

2620E USER xxxx NOT AUTHORIZED FOR SYMTAB yyyy Explanation: An Event requested a symbol table to which it was not permitted

access. System Action: The event will not execute. User Response: The access to symbol tables is controlled by the ESP administrator.

2621I BAD XME RECEIVED Explanation: The TP Server received a request unit. The length of an XME within

the request unit did not correspond with the expected length. System Action: The failure is logged and the XME is discarded. User Response: Notify your system support personnel.


When nn=12: invalid parameters passed to parse from CP. nn=16: No space available. nn=20: Validity check routine termination. nn=24: An error in input parameters was detected in the IKJPARS2 load module. nn=28: A line drop condition was detected and IKJPTGT (PUTGET

334 ESP-5.4-MC-03

I/O service routine) or IKJPUTL (PUTLINE I/O service routine) set return codes of 24 and 32 respectively.


2623I Sending a TTPBF with nn XMEs to xxxx Explanation: The TP Server transmitted a request unit to node 'xxxx'. The request

unit contained nn XMEs. System Action: This is a diagnostic message which will only be issued upon special

instructions from Cybermation. User Response: None.

2624W INSUFFICIENT MAIN STORAGE FOR GQSCAN REQUEST Explanation: An attempt was made to obtain storage to process system enqueue

chains. The requested amount of storage could not be obtained. System Action: The requested GQSCAN function is terminated. User Response: Increase the region size available to the job.

2625W NO MATCHING UCBS FOUND Explanation: A request was issued to locate volume with a specified volume serial

number or prefix. No UCB's could be located which matched the specified request.

System Action: The requested UCB scan function is terminated. User Response: Ensure the correct volume serial number or prefix was specified.

2626C xxxx Explanation: The current CSA usage was listed in response to a request to list

current CSA usage. System Action: None. User Response: None.

2627W Cannot execute requested function on an ESP proxy subsystem when JOBINDEX data set is not shared

Explanation: A user attempted a command that would require updating the JobIndex file. The subsystem the command was issued from was not a MASTER ESP, and the JobIndex did not have the SHR attribute. This could lead to an integrity exposure.

System Action: The command is not executed. User Response: Reissue the command from an ESP master subsystem.

2628I Third party SAF profiles refreshed Explanation: The SAFREFR command completed successfully. The profiles used by

the simulated 3rd party RACHECK function have been destroyed so that they will be rebuilt on demand.


2629W Simulated 3rd party RACHECK not active Explanation: The SAFREFR command was entered to refresh the profiles used by the

Messages and Codes

ESP-5.4-MC-03 335

simulated third party RACHECK function. However, the simulated third party RACHECK option was not active.

System Action: None. User Response: This function is only supported with simulated third party RACHECK.

It is not required with RACF. (Use SETROPTS REFRESH GENERIC(...))

2630W No function requested, command ignored Explanation: The utility routine CYBESUDI was invoked with no function verb. System Action: The command is ignored. User Response: Specify a function verb, such as RESYNCH to resynchronize the data set

trigger entries.

2631W No Eventsets currently open, Resynch request ignored Explanation: The data set trigger index RESYNCH function was requested. However,

no Eventsets were currently open. The Resynch function requires at least one open data set.

System Action: The request is not processed. User Response: Ensure at least one Eventset is defined, or open.

2632I A total of nn data set trigger entries rebuilt Explanation: The data set trigger resynch utility has completed. The message

indicates how many data set trigger entries were rebuilt. System Action: None. User Response: None.

2633I nn data set trigger entries rebuilt for Eventset xxxx Explanation: The data set trigger resynch routine has completed scanning an

Eventset. This message indicates how many data set trigger entries were rebuilt from Events in this file.

System Action: Processing continues with any more Eventsets. A grand total is displayed after the final Eventset is scanned.


2634I A total of nn DXEs deleted in nn blocks Explanation: The data set trigger resynchronization utility has completed deleting

existing data set trigger entries from the INDEX data set. This message indicates how many entries (DXEs) have been deleted, and the number of records it took to house them in the VSAM file.

System Action: The resynchronization utility will continue by scanning the Event files and rebuilding the DXEs.


2635C Usermod Status Explanation: This message precedes the display of the currently active usermod

options. Usermod options are installation selectable user requested modifications.


336 ESP-5.4-MC-03

2636I Event Message Limits are currently set to nn, nn Explanation: This message is given in response to the MSGLIMIT command. The first

displayed value is the maximum number of messages to be issued by a single execution of an Event. The second value is the message threshold at which Event execution is terminated.


2637I Event Message Limits are currently inactive Explanation: This message is given in response to the MSGLIMIT command. It means

that the message limits are not active. That is, there is no limit to the number of messages that may be generated by an Event.


2638I NO USER DEF BACKUP TIME SET Explanation: There is currently no scheduled time set for a backup of the USERDEF

data set. System Action: None. User Response: The user can set a scheduled time for the backup of the USERDEF

data set using the BKUPUDEF command, if that is desired. Otherwise the user does not have to take any specific action.

2640E Message limit of 1048576 exceeded. Explanation: The MSGLIMIT command was entered with an excessive limit value. System Action: The command is ignored. User Response: Re-issue the command with a limit value of less than 1048576.

2641E PURGSCHF TIME IS NOT IN THE PAST Explanation: The PURGSCHF command was entered but the time value specified was

not a time in the past. It was the present time or a time in the future.

System Action: The PURGSCHF command is ignored. User Response: Re-enter the command with a date in the past.

2643I COMMAND PREFIX xxxx CANCELLED Explanation: A request to cancel command prefix "xxxx" was successful. System Action: The command prefix "xxxx" is no longer honored. User Response: None.

2640E Message limit of 1048576 exceeded. Explanation: The MSGLIMIT command was entered with an excessive limit value. System Action: The command is ignored. User Response: Re-issue the command with a limit value of less than 1048576.

2645I COMMAND PREFIX xxxx {ADDED | REPLACED} Explanation: A request to update command prefix "xxxx" was successful.

Messages and Codes

ESP-5.4-MC-03 337

System Action: The command prefix "xxxx" is updated. User Response: None.

2646E INVOKE nesting limit of 10 exceeded, INVOKE ignored Explanation: In an ESP procedure, a nested INVOKE statement was encountered. There

are already 10 nested INVOKES, which is the maximum allowed. Possibly, a loop has occurred due to recursive INVOKE statements.

System Action: The INVOKE is ignored. An event error results. User Response: If there is not a recursion loop, restructure the procedure to have a

maximum nesting depth of 10.

2647E Insufficient checkpoint space to build DSTRIG object list. Resynch cancelled. Explanation: CYBESUDI could not complete a list of DSTRIG objects that require

DXEs. System Action: The Resynch request will not be executed. The INDEX file remains

unchanged. User Response: None.

2648I DSTRIG object entries rebuilt. Triggering <not> unquiesced. Explanation: Data set triggering is always quiesced while DXEs that belong to

DSTRIG workload objects are being rebuilt. When that is finished, triggering is returned to its state prior to the operation.


2649W Previous RESYNCH process has not finished yet. Request ignored. Explanation: CYBESUDI requested the DSTRIG workload object package to rebuild

its DXEs. The workload object package has not completed the work yet. A new RESYNCH request cannot be executed until the previous one completes.

System Action: The request is ignored. User Response: After the workload object package completes building DXEs, it will

issue message 2648I.

2650E DSTRIG <job{.qual}: Trigger data not defined. Explanation: A job <job{.qual> has been defined as a DSTRIG workload object but

a valid DSNAME statement did not appear before the ENDJOB statement.

System Action: The application will not be built. User Response:

Provide a correct trigger description within the DSTRIG workload object definition.

2651E EVENT NOT SPECIFIED WITH COUNT Explanation: A SYSMSGS command specified a COUNT parameter but no corresponding

EVENT parameter. System Action: The command is not processed. User Response: Correct the command and re-issue it.

338 ESP-5.4-MC-03

2652E MESSAGE TEXT NOT SPECIFIED Explanation: A SYSMSGS command specified parameters which required the message

text but none was specified. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2653E MESSAGE TEXT NOT ALLOWED Explanation: A SYSMSGS command specified one of the IGNORE, DISABLE or ENABLE

parameters along with a message text. No parameters other than ID are permitted for these requests.

System Action: The command is not processed. User Response: Correct the command and re-issue it.

2654E key_name KEYWORD MISSING Explanation: A SYSMSGS command specified a request such as IGNORE, DISABLE or

DISABLE but did not specify the additional named keyword which is required.


2655E EXTRANEOUS KEYWORD SPECIFIED Explanation: A SYSMSGS command specified one of the IGNORE, ENABLE or DISABLE

parameters along with other keywords which are not permitted for these requests. The only other parameter allowed is ID.


2656E ID NOT FOUND Explanation: A SYSMSGS command specified an ID parameter but no message with

a matching identifier was found. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2657I MESSAGE ID(S) CLEARED Explanation: The message(s) requested by the CLRSYSMS command have been cleared. System Action: Processing continues. User Response: None required.

2658E MISSING MESSAGE ID Explanation: A CLRSYSMS command did not specify an ID parameter. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2659E MESSAGE ID NOT FOUND Explanation: A CLRSYSMS command specified an ID parameter but no message with

a matching identifier was found. System Action: The command is not processed.

Messages and Codes

ESP-5.4-MC-03 339

User Response: Correct the command and re-issue it.

2661E MISSING EVENT NAME Explanation: A MAPGEN command did not specify an EVENT parameter. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2662E NO MATCHING EVENTS Explanation: A MAPGEN specified an EVENT parameter but no event names which

correspond to the value specified were found. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2663E MISSING DATA SET NAME Explanation: A JOBMAP command did not specify a DSN parameter. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2664E ILLEGAL NODISPLAY Explanation: A JOBMAP specified a NODISPAY parameter but one of the items in

the list did not correspond to a documented legal value. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2665E DATA SET xxxx IS NOT SEQUENTIAL Explanation: A JOBMAP command was specified. However, the data set was not a

sequential data set. System Action: The map data set cannot be processed. User Response: Specify a sequential data set and reissue the command.

2666W NO JOBS FOUND Explanation: A JOBMAP command was specified. However, the input data was either

empty or did not contain any jobs for the application(s) specified by the APPL keyword.

System Action: The command is not processed. User Response: Either specify a different data set or a different APPL parameter and

reissue the command.

2667E UNABLE TO PROCESS INPUT FILE Explanation: The data set specified in the JOBMAP command could not be processed.


System Action: The command is not processed. User Response: Re-specify the command with a data set that can be processed. Consult

any previous messages at the terminal or on the system messages of the batch job to determine the exact nature of the error.

340 ESP-5.4-MC-03

2668E MISSING DATA SET NAME Explanation: A JOBTREE command did not specify a DSN parameter. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2669E MISSING JOB NAME Explanation: A JOBTREE command did not specify a JOB parameter. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2670E DATA SET xxxx IS NOT SEQUENTIAL Explanation: A JOBTREE command was specified. However, the

data set was not a sequential data set. System Action: The map data set cannot be processed. User Response: Specify a sequential data set and reissue the command.

2671E JOB NOT FOUND Explanation: The job name specified in the JOB parameter of the JOBTREE command

was not found in the input map data set. If the APPL parameter was also specified, then ESP could not find the named job in the named application.


2672E UNABLE TO PROCESS INPUT FILE Explanation: The data set specified in the JOBTREE command could not be processed.


System Action: The command is not processed. User Response: Re-specify the command with a data set that can be processed. Consult

any previous messages at the terminal or on the system messages of the batch job to determine the exact nature of the error.

2673E INVALID COUNT VALUE Explanation: A SYSMSGS command specified a COUNT parameter that was either

negative or greater than 255. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2674E MISSING DATASET NAME Explanation: A MAPGEN command did not specify a DATASET parameter. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2675E EVENTFILE NOT FOUND Explanation: The event file specified in the MAPGEN command was not defined in the

ESP checkpoint.

Messages and Codes

ESP-5.4-MC-03 341

System Action: The command is not processed. User Response: Correct the name of the data set, or define it to ESP.

2676E INVALID JOBNAME/QUALIFIER Explanation: An invalid job name or job name qualifier combination was specified

in a JOBTREE command. The job name and qualifier may not exceed 8 characters each and must be separated by a period.



Explanation: The application manager was processing a new generation of an application that was marked waiting in the jobindex file. However, the APPLFILE record for the new generation was invalid, or did not correspond to the jobindex entry.

System Action: The new generation of the application is not picked up for processing. User Response: Try to unwait the generation nn of the application xxxx.

Notify Cybermation support.


Explanation: An I/O error occurred reading an APPLFILE record for a new generation of an application marked waiting. The error is described in a preceding message.

System Action: The application can not be processed. User Response: If the I/O error is corrected, try to unwait the generation nn of the

application xxxx. If it fails, notify Cybermation support.

2679E ABOVE I/O ERROR OCCURRED WRITING APPL xxxx, GENERATION nn

Explanation: The application manager encountered an error while updating an APPLFILE entry for a generation of an application marked waiting. The nature of the error is described in the preceding message.

System Action: The generation nn of the application xxxx remains in APPLWAIT status. User Response: Try to unwait the generation nn of the application xxxx. If it fails,

the remedial action depends on the error. Physical damage to the data set may require the restoration of the data set.

2680E TOO MANY JOBS Explanation: More than 50 predecessors or successors were specified on the

APPLJOB command. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2681E Simulation of a WOB with the AGENT command is not valid on a local proxy subsystem.

Explanation: Simulation on a local proxy subsystem encountered a WOB definition

342 ESP-5.4-MC-03

containing the AGENT command. System Action: Simulation continues. User Response: Simulate the event on the master subsystem. You can simulate this

event on the local proxy subsystem, if it is set up to route subsystem requests to the master when the ESP High Availability Option or the High Performance Option is installed.

2682E INVALID RELATIONSHIP SPECIFICATION x Explanation: The conditional relationship for predecessor or successor jobs on

the APPLJOB command was not one of A, N or U. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2683E COMMAND NOT ALLOWED Explanation: USERMOD 35 has not been activated to enable the APPLJOB command from

the operator console. System Action: The command is not processed. User Response: Correct the command and re-issue it.

2684E NO FUNCTION SPECIFIED Explanation: The COMPLETE parameter was not specified on the APPLJOB command from


2685E MISSING APPLICATION NAME Explanation: The APPL parameter was not specified on the APPLJOB command from


2686E VS COMMAND HAS MISSING OPERAND Explanation: VS Command has been submitted with no operand. The most likely cause

for this is a missing continuation character in an ESP procedure, or a missing USERn parameter.

System Action: Command rejected. User Response: Correct the ESP procedure, and retry.

2689I Job xxxx{.yyyy}(Jnnnn) resumed, no longer on critical path Explanation: An active job in an ESP application running on a system in goal mode

was expedited because it was on the critical path. However its service class has been resumed to its original one because it is no longer on the critical path. xxxx specifies the job name; yyyy specifies the job qualifier; nnnn specifies the job number.

System Action: A system resume command is issued on the job. User Response: None.

Messages and Codes

ESP-5.4-MC-03 343

2690I AUX_AS is active, ASCB at xxxxxxxx ASID xxxx Name xxxxxxxx AUX_AS is not active

Explanation: The operator issued an AUX_AS command with no operands. ESP is displaying current status information about the auxiliary address space.

System Action: None. User Response: None normally required. If the second form of response is issued,

but an auxiliary address space is required, issue an "AUX_AS START" command.

2691E AUX_AS failed, SS006 return code is n AUX_AS is not active

Explanation: The AUX_AS command called SS006 to execute the function, but SS006 failed. If the error involved the creation of the address space, them message 0710S will have also been issued with the details of the problem.

System Action: The request was not executed. User Response: For a start error, investigate message 0710S. For a cancel, this

means the auxiliary address space is not active or is not connected to this subsystem, and no action is required.

2693E AUX_AS not supported for this subsystem Explanation: An AUX_AS command was issued, but the present ESP subsystem does not

use an auxiliary address space. System Action: The command is ignored. User Response: None.

2694W Job xxxx{.yyyy} not expedited, {no associated policy zzzz| zzzz policy not defined|no eligible policy zzzz actions| waiting for execution on remote node}

xxxx specifies the job name yyyy specifies the ESP job qualifier zzzz specifies the expedite policy name.

Explanation: Response to "XP" line command from CSF or to "AJ xxxx{.yyyy}

EXPEDITE" command in ESP page mode or ESP work station line mode interface (LMI) mode. An attempt was made to manually expedite job xxxx{.yyyy}, but the operation could not be performed for the reason specified in the message.

System Action: None. Processing continues. User Response: If job xxxx{.yyyy} could not be expedited because it has no expedite

policy associated with it, an expedite policy should be defined via the ESP EXPEDITE command, and associated with the job's application via the ESP application EXPEDITE statement. If job xxxx{.yyyy} could not be expedited because expedite policy

344 ESP-5.4-MC-03

zzzz is not defined, then it should be defined via ADD option of the ESP EXPEDITE command. If job xxxx{.yyyy} could not be expedited because expedite policy zzzz does not specify any eligible actions, it means one of the following: 1) Job xxxx{.yyyy} is waiting for execution and expedite policy zzzz does not specify any execution wait expedite actions (CLASS, PRIORITY or START keywords of the EXPEDITE command). 2) Job xxxx{.yyyy} is executing and expedite policy zzzz does not specify a valid execution expedite action (SRVCLASS keyword of EXPEDITE command if execution system is in goal mode or PERFORM keyword of EXPEDITE command if execution system is in compatibility mode). If expedite support is required for the specified job state, then it should be added to the expedite policy via the ALTER keyword of the ESP OPER EXPEDITE command. In addition, if expedite policy zzzz is defined in the ESPPARM initialization file, it should be modified to include the new expedite action(s), so that the new option(s) can take effect when ESP is restarted. Expedite is not supported for jobs waiting for execution on a remote JES node. Therefore, if this is the case for job xxxx{.yyyy} then it cannot be expedited until it begins executing, and expedite policy zzzz specifies an eligible execution expedite action.

2695E EXPEDITE policy name missing Explanation: An EXPEDITE statement in an ESP application procedure does not

specify an expedite policy name. System Action: The ESP application does not execute. User Response: Correct the EXPEDITE statement to specify an expedite policy name or

"OFF" if no expedite policy is to be associated with subsequent jobs in the application.

2696W Expedite policy aaaa ignored, Access denied, User=bbbb, Appl=cccc{, Job=xxxx{.yyyy}}

Explanation: An ESP application contains an EXPEDITE statement specifying expedite policy aaaa. However, user bbbb, under which ESP application cccc is executing, is not authorized to access expedite policy aaaa. If the EXPEDITE statement was specified at the JOB level, xxxx is the job name, and yyyy is the job qualifier, if one exists.

System Action: The application continues to execute, but the expedite policy is ignored.

User Response: If user bbbb should be granted access authority to expedite policy aaaa, then bbbb should be given read access to a SAF profile with resource name "pppp.EXPEDITE.aaaa", where: "pppp" is the SAF resource prefix specified in the PREFIX keyword of the SAFCLASS command in the ESPPARM initialization file. "aaaa" is the expedite policy name. Resource name "pppp.EXPEDITE.aaaa" should be defined under the SAF

Messages and Codes

ESP-5.4-MC-03 345

class specified by the name operand of the SAFCLASS command in the ESPPARM initialization file. If user bbbb is really not authorized to access expedite policy eeee, then the EXPEDITE statement should be removed from the ESP application procedure.

2697S Invalid system command request code nnnn Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

2698I {Submitted|Executing} job xxxx{.yyyy}(Jnnnn) expedited {manually{ by user zzzz}|{, {start|end} time overdue}{, on critical path}}

xxxx specifies the job name. yyyy specifies the ESP job qualifier. zzzz specifies the manual expedite issuer's userid. nnnn specifies the JES job number.

Explanation: A job in an ESP application has been expedited.

The reason is specified in the message. System Action: Processing continues. User Response: None.

2720W UNABLE TO ALLOCATE xxxx, S99 ERROR CODE X'yyyy', INFO CODE X'zzzz'

Explanation: An error occurred during a dynamic allocation request. System Action: This message is followed by another message indicating the action

taken. User Response: Take note of the following message.

2721W UNABLE TO ALLOCATE xxxx, VOLUME OFFLINE Explanation: An error occurred during a dynamic allocation request due to a

required volume being offline. System Action: This message is followed by another message indicating the action


2722W DATA SET xxxx NOT CATALOGUED Explanation: An error occurred during a dynamic allocation request due to a data set

not being catalogued. System Action: This message is followed by another message indicating the action


2723W UNABLE TO GET EXCLUSIVE ALLOCATION TO DATA SET xxxx Explanation: A data set that is needed exclusively was already allocated to another

user.

346 ESP-5.4-MC-03

System Action: This message is followed by another message indicating the action taken.

User Response: Take note of the succeeding message.

2724W UNABLE TO GET SHARED ALLOCATION TO DATA SET xxxx Explanation: A data set that is needed for shared access is allocated exclusively

to another user. System Action: This message is usually followed by another message indicating the

action taken. User Response: Take note of the succeeding message if one is present. If no

succeeding message was issued, you can try to access the data set again after the other user has released control of the data set.

2725W DATA SET xxxx NOT ON {CATALOGUED VOLUME | VOLUME yyyy} Explanation: A data set was not found on the volume as catalogued or explicitly

specified. System Action: This message is followed by another message indicating

the action taken. User Response: Take note of the succeeding message.

2726W ACCESS TO DATA SET xxxx DENIED BY INSTALLATION SAF SECURITY

Explanation: An attempt was made to a allocate a data set. The installation required allocation control by SAF rules. The SAF rules did not permit allocation to the requested data set.

System Action: The allocation request is failed. User Response: Ensure you specify the correct data set name. If necessary, request

authorization from your installation security administrator.

2727W UNABLE TO FREE xxxx, S99 ERROR CODE X'yyyy', INFO CODE X'zzzz'Explanation: An error occurred while performing a dynamic unallocation. System Action: This message is followed by another message indicating the action


2728E UNABLE TO PERFORM TASK SWITCH Explanation: ESP tried to switch to a subtask to perform an allocation request.

The task switch failed. System Action: This message is followed by another message indicating the action


2729E UNABLE TO REVERT TO MAIN TASK Explanation: After an allocation was performed on a subtask, the routine was unable

to rejoin the main task. System Action: This message is followed by another message indicating the action


Messages and Codes

ESP-5.4-MC-03 347

2730W Data set xxxx is migrated Explanation: An error occurred during a dynamic allocation request due to a required

data set being migrated. System Action: This message is followed by another message indicating the action


2740W SYMBOL xxxx NOT DEFINED Explanation: A request was issued to alter or delete symbol 'xxxx'. Symbol 'xxxx'

is not currently defined. System Action: The request is terminated. User Response: Ensure the correct symbol is specified.

2741W SYMBOL xxxx ALREADY DEFINED Explanation: A request was issued to define symbol 'xxxx'. Symbol 'xxxx' is

already defined. System Action: The request is terminated. User Response: Ensure the correct symbol is specified.

2742W SYMBOL xxxx IS READ ONLY Explanation: A request was issued to alter or delete symbol 'xxxx'. Symbol 'xxxx'

is a "read only" symbol and cannot be altered or deleted. System Action: The request is terminated. User Response: Ensure the correct symbol is specified.

2743W INVALID SYMBOL TABLE ENTRY Explanation: A request was issued to insert a symbol. The specified symbol was not

defined to be binary, Boolean, character or floating point. System Action: The request is terminated. User Response: Correct the symbol definition. If the problem persists, notify your

system support personnel.

2744E INVALID SUBSTRING SPECIFICATION Explanation: A request was issued to process a substring. The specification for the

substring in not valid. System Action: The request is terminated. User Response: Correct the substring specification. If the problem persists, notify

your system support personnel.

2745W DATA TOO LONG FOR SYMBOL xxxx Explanation: A request was issued to alter symbol 'xxxx'. The length of the value

specified for symbol 'xxxx' exceeded the defined length of symbol 'xxxx'.

System Action: The request is terminated. User Response: Increase the symbol length or decrease the length of the symbol value.

348 ESP-5.4-MC-03

2746W INCONSISTENT PARAMETERS REQUESTED FOR SYMBOL xxxx Explanation: A request was issued to define a variable length symbol 'xxxx'.

Variable length symbols must be external symbols. Symbol 'xxxx' was not defined to be an external symbol.

System Action: The request is terminated. User Response: Correct the symbol specification.

2747E INCOMPLETE SYMBOL SPECIFICATION Explanation: A symbol value contained a subfield specification. The subfield

contained unbalanced parentheses or quotes. System Action: The request is terminated. User Response: Correct the subfield specification.

2748E INVALID SYMBOL SPECIFICATION Explanation: A compound symbol contained an invalid character or built-in function

routine determined the symbol was invalid. System Action: The request is terminated. User Response: Correct the symbol specification.

2749E INVALID FORMAT DESCRIPTOR Explanation: A statement specified an invalid symbol output format descriptor. System Action: The statement is ignored. User Response: Correct the output format descriptor.

2750E EXPRESSION CONTAINS DIVIDE BY ZERO Explanation: An evaluated expression contains a operation which would cause a

divide by zero. System Action: The statement is ignored. User Response: Correct the evaluated expression.

2751E INVALID EXPRESSION Explanation: A statement contains an invalid expression. System Action: The statement is ignored. User Response: Correct the evaluated expression.

2752E Internal error - symbol xxxx Explanation: An internal error was encountered trying to process symbol xxxx. System Action: Processing for the symbol is terminated. User Response: Contact your system support personnel.

2753E QUALIFIED JOB NAME NOT PERMITTED WITH MANUAL JOB Explanation: A user made an attempt to insert a manual job with a job qualifier. System Action: The job is not inserted. User Response: Repeat the command without the job qualifier.

2754E Not in line mode Explanation: The user attempted to enter a UTIL command while in ESP page mode.

Messages and Codes

ESP-5.4-MC-03 349

System Action: The command is ignored. User Response: When in page mode, the user must first enter line mode via the @LINEMD

command before entering the UTIL command. After all UTIL functions have been performed, the user can exit from line mode via the END command.

2755E IAE xxxx byte subpool yyy core request failed Explanation: A subsystem request required xxxx bytes of work area core in subpool

yyy to return the information requested by the caller. However, there was insufficient contiguous free core available in subpool yyy to satisfy the request.

System Action: The request fails with return code 16. User Response: This request is most likely to fail when the subsystem request

originates from an ESP/WM client (TSO or ESP/WSS) address space, when yyy specifies a CSA subpool. If so, this indicates insufficient ECSA, or fragmentation of ECSA. It is possible that this problem will be temporary, but in most cases an IPL is required to recover. If this happens frequently, the size of ECSA should be increased. Processing for large applications may require large chunks of ECSA for short periods.

2760E DUPLICATE KEY AT OFFSET xxxxxx FOR RECORD nnnnn KEY=value Explanation: While writing to the database, a duplicate record was encountered. System Action: Processing continues. The information for a specific job might be

lost. User Response: Contact Cybermation Technical Support for assistance.

2761E VSAM ERROR EXIT AT OFFSET xxxxxx for RECORD nnnnn Explanation: An internal VSAM error has been detected while performing database

I/O. System Action: Processing is terminated. The database is not usable. User Response: Contact Cybermation Technical Support for assistance.

2762E RETURN CODE nn AT OFFSET xxxxxx ON RECORD nnnnn Explanation: A VSAM error has been detected while performing database I/O. System Action: Processing is terminated. The database is not usable. User Response: Contact Cybermation Technical Support for assistance.

2763E INPUT FILE ERROR Explanation: A I/O error has been detected while reading the input file. System Action: Processing is terminated. User Response: Correct the I/O error and re-run the job.

2764E MISSING TO DATE Explanation: A control statement specified a FROM date but no TO date. System Action: Processing is terminated. User Response: Correct the error and re-run the job.

350 ESP-5.4-MC-03

2765E CONFLICTING DATES Explanation: A control statement specified a FROM date and a DATE parameter.

The DATE parameter specifies a single date whereas the FROM and TO parameters specify a date range.

System Action: Processing is terminated. User Response: Correct the error and re-run the job.

2766E MISSING DATE Explanation: A control statement specified neither a DATE parameter or a FROM-TO

date range. System Action: Processing is terminated. User Response: Correct the error and re-run the job.

2767E VSAM ERROR EXIT FOR function_name Explanation: An internal VSAM error has been detected while performing database

I/O. System Action: Processing is terminated. User Response: Contact Cybermation Technical Support for assistance.

2768E RETURN CODE nn FROM FUNCTION function_name Explanation: A VSAM error has been detected while performing database I/O. System Action: Processing is terminated. User Response: Contact Cybermation Technical Support for assistance.

2769E MISSING EVENT NAME Explanation: A control statement specified a PREFIX parameter with no NAME

parameter. System Action: Processing is terminated. User Response: Correct the error and re-run the job.

2770E EVENT AND APPL MUTUALLY EXCLUSIVE Explanation: A control statement specified both an APPL parameter and event

parameters. System Action: Processing is terminated. User Response: Correct the error and re-run the job.

2771E NEITHER EVENT NOR APPL MUTUALLY SPECIFIED Explanation: A control statement specified neither an APPL parameter nor event

parameters. System Action: Processing is terminated. User Response: Correct the error and re-run the job.

2772E NO CONTROL STATEMENTS Explanation: No valid control statements were present in the input. System Action: Processing is terminated. User Response: Correct the error and re-run the job.

Messages and Codes

ESP-5.4-MC-03 351

2773E APPL appl_name NOT FOUND Explanation: The named application was not present in the database. System Action: The request is ignored. User Response: Correct the error and re-run the job.

2774E EVENT prefix.name NOT FOUND Explanation: The named event was not present in the database. System Action: The request is ignored. User Response: Correct the error and re-run the job.

2775E ILLEGAL ORDER Explanation: The ORDER parameter on the FLOWDOC command was not one

of NAME or RUN. System Action: The request is ignored. User Response: Correct the statement and re-run the job.

2776E DATABASE FULL AT OFFSET xxxxxx FOR RECORD nnnnn Explanation: The database has run out of space on the volume. System Action: Processing is terminated. The database is unusable. User Response: Re-allocate the database on a volume with more free space.

2777E ILLEGAL COMMAND Explanation: An unknown command was entered. System Action: Processing is terminated. User Response: Rerun the job using valid command input.

2778E INVALID OBJECT TYPE SPECIFIED FOR RESUMED OBJECT DEFINITION

Explanation: A resumed object definition in application refers to a different object type.

System Action: The application is not processed. User Response: Either change an object type appropriately, or change an object name.

2779I DEFINITION OF OBJECT xxxx IN APPL yyyy RESUMED; APPL GENERATION CONTINUES

Explanation: A resumed object definition in application refers to the same object type.

System Action: The processing continues. User Response: Check the object definition, that caused this message to be issued.

2780E xxxx Explanation: An I/O error was encountered getting a command for FlowDoc. This

could include a file not allocated condition or an actual I/O error on the SYSIN data set. The text of the message fully describes the error.

System Action: Processing is terminated. User Response: Correct the problem and rerun the job.

352 ESP-5.4-MC-03

2781E ERROR OCCURRED DURING COMMAND PARAMETER SCAN Explanation: An error occurred during the parameter scan of a statement from the

FlowDoc input stream. This is probably due to an internal logic error.

System Action: Processing terminates. User Response: Notify your software support personnel.

2782E ERROR SCANNING COMMAND, RC=nn Explanation: A problem was encountered while parsing the command. System Action: The command is ignored. User Response: System routine IKJPARS returned error code nn.


2799W Cannot delete CPU - invalid use of keyword FORCE Explanation: A CPU xxxx DELETE command was issued. The CPU being deleted is not

the last CPU. Keyword FORCE can be used only with the last CPU. System Action: The CPU definition is not deleted. User Response: If you really want to delete that CPU remove FORCE keyword from the

command.

2800W xxxx is the only CPU defined, you cannot delete the last CPU unless it is inactive and FORCE keyword is used

Explanation: A CPU xxxx DELETE command was issued. The CPU being deleted is the last CPU. Either the CPU is in ACTIVE state or keyword FORCE was not used.

System Action: The CPU definition is not deleted. User Response: If you really want to delete the last CPU from RESOURCE file make sure

it is INACTIVE and use FORCE keyword.

2801W CPU xxxx has active jobs, cannot delete at this time Explanation: A CPU definition was being deleted from the resource manager network

topology. The CPU has jobs currently using some of the resources owned by the CPU. A CPU definition cannot be deleted while jobs are queued to resource pools that are owned by it.

System Action: The CPU will not be deleted. User Response: Set the CPU to INACTIVE first, in order to prevent more jobs from

being routed to it. Then retry the command again later.

Messages and Codes

ESP-5.4-MC-03 353

2802E Logic error encountered in CPU delete routine Explanation: A logic error was encountered in the CPU delete routine. An attempt

was made to remove a resource pool which was still in use. This is an internal logic error.

System Action: ESP will follow this with a user abend 2802 to prevent the Resfile from being damaged.

User Response: Contact Cybermation technical support.

2803W Unable to delete node xxxx, delete attached CPU(s) first Explanation: A NODE xxxx DELETE command was used to delete a NODE definition from

the Resfile. However, the NODE still had one or more CPUs attached to it. A NODE can only be deleted when it has no more CPUs.

System Action: The NODE definition is not deleted. User Response: Use the CPU command to delete any CPUs attached to this node. When

that has been successfully performed, reissue the NODE delete command.

2804E Scope cannot be changed with SET. Resource xxxx not updated Explanation: A RESDEF SET command was issued, and a scope was specified (i.e.,

ENTERPRISE, GLOBAL, or LOCAL). However, the scope of the resource cannot be changed with the SET verb.


User Response: To change the scope, delete the resource with RESDEF DELETE and then create it once again with RESDEF ADD, specifying the new scope.

2805E Type cannot be changed with SET. Resource xxxx not updated Explanation: A RESDEF SET command was issued, and a type was specified (i.e.,

RENEWABLE, DEPLETABLE or THRESHOLD). However, the type of the resource cannot be changed with the SET verb.


User Response: To change the type, delete the resource with RESDEF DELETE and then create it once again with RESDEF ADD, specifying the new type.

2806W AUTHORIZATION TABLE NOT ACTIVE Explanation: In a SAF environment, Authorization Tables are not applicable,

therefore the user should not try to list an AT. System Action: Processing continues. User Response: Do not use LISTAT in a SAF-based system.

2807E JCL LIBRARY MEMBER xxxx MISSING %ENDINCL OR %ENDEXCL Explanation: The submit processor came to the end of a member of a JCL library

member and found that still had an exclude in progress. Either a %EXCLUDE did not have a matching %ENDEXCL at the end of the member or a %INCLUDE had failed and there was no matching %ENDINCL.

System Action: The submit process will not complete. User Response: The user should edit the JCL library member in question and insert

either a %ENDINCL or %ENDEXCL, whichever is appropriate.

354 ESP-5.4-MC-03

2808E MESSAGE TEXT REQUIRED FOR SYSMSGS STATEMENT Explanation: The user entered a SYSMSGS command with either no message text

specified or with the message text no enclosed in apostrophes. System Action: The SYSMSGS command is ignored. User Response: Enter the SSYSMSGS command with the message text enclosed in

apostrophes.

2809? PUTLINE ERROR CODE nn Explanation: A PUTLINE informational message has failed. The PUTLINE return code

is nn. System Action: This message is followed by message 2811. User Response: Contact your system support personnel.

2810? PUTLINE ERROR CODE nn Explanation: A PUTLINE data message has failed. The PUTLINE return code is nn. System Action: This message is followed by message 2812. User Response: Contact your system support personnel.

2811? PARM=xxxx yyyy zzzz aaaa Explanation: A PUTLINE informational message has failed. The PUTLINE parameters

are listed. System Action: This message is preceded by message 2809. User Response: Contact your system support personnel.

2812W Unable to free output data set, RC=nn Explanation: The GENPROJ command attempted to free the output data set. The attempt

failed with an SVC 99 return code 'nn'. System Action: Processing continues. User Response: Use the TSO FREE command to manually free the output data set. If the

problem persists, contact your System Programmer.

2813W 'DO' STATEMENT EXTRANEOUS INFORMATION IGNORED Explanation: DO statements in CLANG should not have any operands, continuations or

other commands following the DO command. If there is any command after the DO, or a continuation, the command is ignored resulting in unexpected results in the procedure.

System Action: The warning message is displayed, and the unexpected commands are ignored (not processed).

User Response: The user should remove the continuation from the ESP procedure DO statements or remove the extraneous commands on the DO statements and retry the procedure to ensure that proper results are obtained.

2814E REEXEC MAXIMUM cannot be greater than 255 Explanation: The MAXIMUM parameter entered on the REEXEC statement is higher

than the maximum value allowed. This value should be less than or equal to 255.

System Action: The procedure is ended with an error condition.

Messages and Codes

ESP-5.4-MC-03 355

User Response: The user should specify a valid MAXIMUM on the REEXEC command and reenter the command or rerun the procedure.

2815E ROUTEJCL SPECIFIES ILLEGAL VALUE Explanation: The NODE initialization statement or command specifies data in the

ROUTEJCL parameter that does not start with /* or // System Action: The NODE statement is ignored. User Response: Correct the ROUTEJCL parameter and either re-enter the command or

restart ESP.

2816E ROUTEJCL SPECIFIES ILLEGAL VALUE Explanation: The CPU initialization statement or command specifies data in the

ROUTEJCL parameter that does not start with /* or // System Action: The CPU statement is ignored. User Response: Correct the ROUTEJCL parameter and either re-enter the command or

restart ESP.

2818E INVALID COMMAND ENTERED, ONLY LISTSYML ALLOWED Explanation: The user is only allowed to enter the LISTSYML command on the

CYBESSYM panel. No other commands are allowed. System Action: The CYBESSYM panel and invalid command are displayed for the user

to make a valid selection in order to continue. User Response: The user should either enter a valid LISTSYML command, on the command

line, or leave the command line blank. The user should make the appropriate change and press enter to continue.

2820E JOB xxxx HAS BEEN ALREADY BEEN BYPASSED Explanation: A user is trying to use the APPLJOB command to perform a RESET on a

job which has already been bypassed. This cannot be done, since the APPL manager has already bypassed scheduling of the job.

System Action: The APPLJOB command does not make any changes to the job. This message is issued and control is returned to the user.

User Response: The user should verify that the proper job was selected for the RESET. If not, the user should re-enter the APPLJOB command (or CSF line command) with the proper job name. If the user does want the bypassed job to be scheduled, the user should find an alternative method of running the job. Perhaps another generation will need to be triggered or some other option used.

2821E JOB xxxx IS WAITING FOR RESOURCES, CANNOT BE RESET Explanation: The user is trying to reset the named job in the APPL manager. This

job is currently no longer in APPL Manager's control. It has been passed on to the RESOURCE Manager and is currently waiting for resources which it requires to become available. This job cannot be reset in APPL Manager now.

System Action: The user's reset command is rejected with an error return code of 8. User Response: The user should verify that the proper job was selected for the RESET.

356 ESP-5.4-MC-03

2822E JOB xxxx IS WAITING FOR RESOURCES, CANNOT DROP DEPENDENCIES

Explanation: The user is trying to drop dependencies for the named job in the APPL manager. This job is currently no longer in the APPL Manager's control. It has been passed on to the RESOURCE Manager and is currently waiting for resources which it requires to become available. This job cannot have dependencies dropped in APPL Manager now.

System Action: The users Dropdep command is rejected with an error return code of 8. User Response: The user should verify that the proper job was selected for the

DROPDEP.

2823E Command exceeded internal buffer Explanation: While processing a WOBCMD or JOBRES command, the internally generated

Automation Framework Message (AFM) exceeded the capacity of the buffer.

System Action: The command is not executed. User Response: If your installation has reduced MAXLRECL from the default, you may

be able to increase MAXLRECL so this command can be processed. Otherwise the command is simply too long.

2824W DEFAULT CALENDARS 1 AND 2 ARE DUPLICATES, xxxx,yyyy FOR USER zzzz

Explanation: A User PROFILE statement for the named user has specified CALENDAR1 and CALENDAR2. Both calendars have the same name. This will result in the same calendar being searched twice or when a LISTSPEC is issued, days from the same calendar will be listed twice.

System Action: The system is continuing to process the PROFILE statement as it is specified.

User Response: The user should remove the duplicate CALENDAR specification from the PROFILE statement. PROFILE statements are kept in the data set specified in the LOADUPDT subcommand in the ESPPARM data set.

2825W DEFAULT CALENDAR IS BEING SET TO SYSTEM FOR USER xxxx Explanation: A User PROFILE statement for the named user has specified

CALENDAR1 or CALENDAR2 with the name SYSTEM. This will result in the SYSTEM calendar being searched twice or when a LISTSPEC is issued, days from the SYSTEM calendar will be listed twice.

System Action: The system is continuing to process the PROFILE statement as it is specified.

User Response: The user should remove the SYSTEM CALENDAR specification from the PROFILE statement. PROFILE statements are kept in the data set specified in the LOADUPDT subcommand in the ESPPARM data set.

2826E RELDELAY cannot be greater than 255 Explanation: A value larger than 255 appeared as the operand of the RELDELAY

statement. System Action: The application is not built.

Messages and Codes

ESP-5.4-MC-03 357

User Response: Specify a value of 255 or less minutes for the release delay.

2827E BAD JOB NAME xxxxxxxx IN APPL, EXPECTED yyyyyyyy Explanation: When ESP is submitting a job, it has found that the name on the JOB

card is not the same as the JOBNAME on the JOB statement. System Action: ESP does not submit the job with the offending job name. User Response: The user should look at the job name on the ESP JOB statement

and be sure that it matches the job names in the JCL in the member of the JCL library being submitted. If there is a mismatch, either the JCL should be changed or the JOB statement changed.

2828E BAD JOB NAME xxxxxxxx EXPECTED yyyyyyyy Explanation: When ESP is submitting a job, it has found that the name on the JOB

card is not the same as the member name on the SUBMIT statement. System Action: ESP does not submit the job with the offending job name. User Response: The user should look at the member name on the ESP submit statement

and be sure that it matches the job names in the JCL in the member of the JCL library being submitted. If there is a mismatch, either the JCL should be changed or the member name should be changed.

2829E A SIGLOST condition cannot be deleted Explanation: The SIGLOST keyword on the SIGPNNM command is a read only indicator.

It is used internally by the system and cannot be deleted. System Action: The request is not processed. User Response:

2830E Unable to locate port nn Explanation: A STATCHAN or RESPCHAN command specified a port that cannot be

found. The port is erroneous or the channel has been closed. System Action: Processing continues. User Response: Correct the port and resubmit the command.

2834E Port nn is the current port Explanation: A STATCHAN or RESPCHAN command specifies the port of the channel

through which the command was sent. System Action: Processing continues. User Response: Correct the port id and resubmit the command.

2845E LUNAME and xxxx parameters are mutually exclusive Explanation: The work station server LUNAME JCL initialization parameter was

specified with a mutually exclusive TCP/IP initialization parameter. System Action: Work station server terminates. User Response: Specify either LUNAME or TCP/IP initialization parameter(s), but not

both, for work station server.

2846E Port or LUname parameter is required Explanation: Either the PORT or the LUNAME JCL initialization parameter is required

to start work station server.

358 ESP-5.4-MC-03

System Action: Work station server terminates. User Response: Specify either the PORT (for TCP/IP) or the LUNAME (for APPC) JCL

initialization parameter (PARM operand in the JCL EXEC statement) to start work station server.

2850I Client nn.nn.nn.nn:nn ended Explanation: A work station client connection has terminated. System Action: Processing continues. User Response: None.

2858E ESP subsystem xxxx not found Explanation: Work station server could not find the ESP subsystem specified by the

SUBSYS JCL initialization parameter. System Action: Work station server terminates. User Response: If the SUBSYS parameter is valid, start the ESP subsystem first, then

start work station server. If the SUBSYS parameter is invalid, correct it and restart work station server.

2859E DURATION cannot be greater than 6553 Explanation: The value coded on DURATION statements exceeds the allowed maximum

of 6553. System Action: The application will not be built. User Response: Correct the value.

2870C Non-SAF user ID mappings Explanation: This message is issued in response to the MAPUSER OPER command.

It should be followed by a list of the MAPUSER entries in AGENTDEF. System Action: N/A User Response: N/A

2871I No User ID mappings defined Explanation: This message is issued in response to the MAPUSER OPER command.

There are no MAPUSER entries in AGENTDEF to display. System Action: None. User Response: N/A

2888W Connection rejected from nn.nn.nn.nn, reason code=xx Explanation: The WorkStation Server has rejected a connect request from a client

whose IP address is nn.nn.nn.nn. The reason code indicates: 4: 250 clients are already connected to the server. 8: The indicated IP address already has 8 connections. 12: There are already 2 pending connections to this IP address which have not yet provided a valid userid and password.

System Action: The socket is closed. No client environment is created. The server continues to listen for a valid connection request.

User Response: For reason 4, investigate whether the current connections are valid. For more than 250 connections, additional servers may be needed. Note that each ESP WorkStation requires 2 connections, one each for the command and status channels.

Messages and Codes

ESP-5.4-MC-03 359

For reasons 8 and 12, investigate the the indicated IP address for a possible loop creating connections.

2971E Invalid structure in JTR vvvv(wwww), error code xx: yyyy in zzzz Explanation: During ESP processing, a job tracking record (JTR) failed a validity

check. vvvv specifies the job name. wwww specifies the job identifier. xx specifies an error code. yyyy specifies location of the job. zzzz specifies "Error" or "Loop".

System Action: ESP/WM will discontinue processing of this job. If this occurs during tracking, the tracking data is discarded, but the error is reported as a logical track file I/O error.


2972E Invalid structure in ATR aaaa.gggg, error code nn Explanation: During ESP processing, a application tracking record (ATR) failed

a validity check. The application affected is named "aaaa" and the generation in error is "gggg".

System Action: ESP will discontinue processing of this generation, unless the damage can be repaired. Repair is not yet implemented.


2978E Asterisk not allowed in dataset name for DSTRIG Explanation: ESP encountered a DSTRIG event command that specifies a dataset

name with an imbedded asterisk. System Action: The ESP event is suppressed. User Response: Specify a valid dataset name.

2979I ESP Agent for z/OS release xxxx initialized, subsys yyyy Explanation: The ESP Agent for z/OS has completed its initialization. System Action: Processing continues. User Response: None.

2980I ESP Agent for z/OS shutdown in progress, subsys xxxx Explanation: A shutdown command was issued to the ESP Agent for z/OS or a

P or STOP command was received. System Action: The ESP Agent for z/OS continues with the shutdown. User Response: None.

2981I ESP Agent for z/OS release xxxx status Explanation: This message introduces the display of the current status of the

ESP Agent for z/OS. System Action: The messages that follow will describe the current processing status

of the ESP Agent for z/OS. User Response: None

360 ESP-5.4-MC-03

3000E Invalid call to extended MCS console services Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Contact Cybermation support.

3001I Extended MCS console {not defined|cccc {already }{in}active{, Termname=tttt}{, Key=kkkk}

Explanation: Response to ESP Workload Manager's "MCS STATUS" command, "MCS ACTIVATE" command if the extended MCS console is already active, or "MCS DEACTIVATE" command if the extended MCS console is already inactive. cccc specifies the extended MCS console name. tttt specifies the extended MCS console terminal name. kkkk specifies the extended MCS console key.


3002S xMCS Activate parameter list not a valid MCRA Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Contact Cybermation support.

3003S xCOMMAND parameter list not a valid CCRA Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Contact Cybermation support.

3004W MCS console cccc alert detected, {Memory limit reached| Queue depth limit reached|Internal error|Alert percentage reached| Request to suspend operator|Reason unknown}

Explanation: A console alert, i.e. a console event that disrupts extended MCS console message queueing, has occurred. cccc specifies the extended MCS console name.

System Action: ESP Workload Namager's extended MCS console is de-activated. User Response: To restart ESP Workload Manager's extended MCS console, enter the

command - OPER CONSOLE ACTIVATE {NAME(cccc)} {TERMNAME(tttt)} {KEY(kkkk)} or OPER CN A {N(cccc)} {T(tttt)} {K(kkkk)} where - cccc specifies an optional console name (default is ESP SYSID). tttt specifies an optional console terminal name (default is console name). kkkk specifies an optional console key (default is no console key).

Messages and Codes

ESP-5.4-MC-03 361

3005I McsOp{er|Msg} {Activate|Deactivate|GetMsg|Req=nnn}, Console=cccc{, Termname=tttt}{, Key=kkkk}

Explanation: An extended MCS console event has completed successfully. cccc specifies the extended MCS console name. tttt specifies the extended MCS console terminal name. kkkk specifies the extended MCS console key. nnn specifies a request code if the request is unknown.

System Action: Processing continues. User Response: None

3006E McsOp{er|Msg} {Activate|Deactivate|GetMsg|Req=nnn}{, rrrr} {, Rtn=xx, Rsn=yy}, Console=cccc{, Termname=tttt}{, Key=kkkk}

Explanation: An extended MCS console API call has failed. rrrr specifies the reason for the extended MCS console API call failure. cccc specifies the extended MCS console name. tttt specifies the extended MCS console terminal name. kkkk specifies the extended MCS console key. nnn specifies a request code if the request is unknown. xx specifies the hexadecimal return code of the extended MCS console API call. yy specifies the hexadecimal reason code of the extended MCS console API call.

System Action: Processing continues. User Response: Attempt to determine the cause of the failure and, if possible,

correct it. If unable to correct the problem and/or it persists, contact Cybermation support.

3007E xMCS {Activate|Deactivate}, xxxx Explanation: Internal extended MCS console logic error. Should never happen.

xxxx specifies the reason for the error. System Action: Processing continues. User Response: Contact Cybermation support.

3008E xCommand text end address xxxxxxxx not within valid range yyyyyyyy-zzzzzzzz

Explanation: xxxxxxxx, yyyyyyyy and zzzzzzzz specify virtual storage addresses. Internal logic error. Should never happen.

System Action: Processing continues. User Response: Contact Cybermation support.

3009I MCS not active, system command response not retrievable Explanation: A Cybermation product could not retrieve the response to a system

command that it issued because it is not active as an extended MCS console.

System Action: Processing continues. User Response: Acivate the Cybermation product as an extended MCS console.

362 ESP-5.4-MC-03

For ESP Workload Manager, issue the following ESP operator command - MCS ACTIVATE or MCS A This must be prefixed with OPER if issued in page mode or an ESP line mode interface. In addition, the following command should be added to the ESPPARM initialization file - MCS ACTIVATE

3010E MCS {NAME|TERMNAME|KEY} keyword incompatible with {DEACTIVATE|STATUS} request

Explanation: The MCS operator command has been issued with incompatible parameters. System Action: Processing continues. User Response: Re-issue the MCS command with compatible parameters.

3011W Time out waiting for system command response Explanation: A Cybermation product issued a system command and timed out waiting

for a system command. This may happen if the system is congested. System Action: Processing continues. User Response: Normally none.

If the problem is persists and it does not appear to be due to system congestion, call Cybermation support.

3012W Job jjjj{.qqqq} on remote JES node, JES status not available Explanation: Response to $D CSF line command or APPLJOB DISPLAY command.

Job jjjj has been submitted to a remote JES node and its JES status cannot be displayed. qqqq specifies the job's qualifier if it has one.


3013W MCS not active, JES job display not available Explanation: A $D CSF line command or an APPLJOB DISPLAY command was issued to

display the JES status of a job in an ESP Workload Manager application. However, the command cannot be processed because the ESP Workload Manager subsystem is not active as an extended MCS console, and therefore cannot retrieve the response to the JES command required to display the job's JES status.

System Action: Processing continues. User Response: Acivate the Cybermation product as an extended MCS console.

For ESP Workload Manager, issue the following ESP operator command - MCS ACTIVATE or MCS A This must be prefixed with OPER if issued in page mode or an ESP line mode interface. In addition, the following command should be added to the ESPPARM initialization file -

Messages and Codes

ESP-5.4-MC-03 363

MCS ACTIVATE

3016E Default CONSOLE NAME xxxx is invalid - it must begin with A-Z, #, $ or @

Explanation: The console name in an MCS initialization parameter or an MCS command must begin with the letters A through Z or with a #, $ or @. If omitted, the console name defaults to the value specified in the SYSID initialization parameter. If the SYSID initialization parameter is omitted, the current SMF system identifier is used. Accordingly, the console name must not be allowed to default if the SYSID initialization parameter or, if it is omitted, the current SMF system identifier does not begin with the letters A through Z or with a #, $ or @.

System Action: Processing continues. User Response: Re-issue the MCS command with the correct console name.

3100E NO SAF CLASS DEFINED Explanation: The SAF resource class is not defined by SAFCLASS command. System Action: The request is denied. User Response: Notify your installation security administrator.

3101E INVALID REQUEST CODE Explanation: Invalid request code specified in SAF request. System Action: The request is denied. User Response: Contact Cybermation Customer Support and Services for assistance.

3102E RACF ERROR RECEIVED Explanation: RACF error received while processing a SAF request. System Action: The request is denied. User Response: Notify your installation security administrator.

3103E RACDEL ERROR CODE xxxx, REASON CODE yyyy Explanation: RACF error code xxxx, reason code yyyy received while processing

a SAF delete resource request. System Action: The request is denied. User Response: Notify your installation security administrator.

3104E RACDEF ERROR CODE xxxx, REASON CODE yyyy Explanation: RACF error code xxxx, reason code yyyy received while processing

a SAF define resource request. System Action: The request is denied. User Response: Notify your installation security administrator.

3200E Network node name required when network services requested Explanation: A Network Delivery Services (NDS) request was made. However, a

NETNODE command was not previously specified to define the network node name of the local Cybermation system.

System Action: The local Cybermation system terminates.

364 ESP-5.4-MC-03

User Response: For an ESP/WM subsystem, add a NETNODE statement to the LOADNET initialization file and restart the job.

3201W Active NETQUEUE data set is <data_set_name> Explanation: A NETQUEUE command was specified, but a NETQUEUE data set is already

open. This will never occur under ESP/WM. This message is followed by message 3202E.

System Action: The NETQUEUE command is ignored. User Response: If more than one NETQUEUE command has been specified in an

initialization file, then delete all but one of them.

3202E NETQUEUE request for data set <data_set_name> rejected Explanation: A NETQUEUE command was specified, but a NETQUEUE data set is already

open. This will never occur under ESP/WM. This message is preceded by message 3201W.

System Action: The NETQUEUE command is ignored. User Response: If more than one NETQUEUE command has been specified in an

initialization file, then delete all but one of them.

3203E Network node <netnode_name> is a network destination, cannot also be local

Explanation: A NETNODE command in the LOADNET initialization file specifies a network node name that has already been defined as a remote network node by a NETDEST command in the LOADNET initialization file.

System Action: ESP/WM action message 3328A is issued to prompt for an END response to ignore the NETNODE command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command.

User Response: Enter CANCEL to terminate ESP/WM or enter a valid NETNODE statement. Enter a valid NETNODE command in the LOADNET initialization file. If ESP/WM was terminated, then restart it.

3204E NETAUTH DELETE|LIST|HELP invalid during initialization Explanation: A NETAUTH command in the LOADNET initialization file specifies the

DELETE, LIST or HELP function, or no function, which defaults to LIST. Only the ADD function is valid in the LOADNET initialization file.

System Action: ESP/WM action message 3328A is issued to prompt for an END response to ignore the NETAUTH command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command.

User Response: Respond to the prompt and correct or delete the erroneous NETAUTH command in the LOADNET initialization file. Then if ESP/WM was terminated, restart it.

3205C NETAUTH HELP Explanation: Response to NETAUTH HELP command. System Action: The NETAUTH command options are displayed. User Response: None.

3206E HOST operand missing Explanation: A NETAUTH ADD or NETAUTH DELETE command was specified, but the

Messages and Codes

ESP-5.4-MC-03 365

required HOST(<host_or_ip>) operand was missing. <host_or_ip> specifies a DNS host name or IP address.

System Action: The NETAUTH ADD or NETAUTH DELETE command is ignored. User Response: If required, re-issue the NETAUTH ADD or NETAUTH DELETE command

specifying the HOST(<host_or_ip>) operand.

3207E NETDEST ALTER|DELETE|LIST|HELP invalid during initialization Explanation: A NETDEST command in the LOADNET initialization file specifies the

ALTER, DELETE, LIST or HELP function, or no function, which defaults to LIST. Only the ADD function is valid in the LOADNET initialization file.

System Action: ESP/WM action message 3328A is issued to prompt for an END response to ignore the NETDEST command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command.

User Response: Respond to the prompt and correct or delete the erroneous NETDEST command in the LOADNET initialization file. Then if ESP/WM was terminated, restart it.

3208C NETDEST HELP Explanation: Response to NETDEST HELP command. System Action: The NETDEST command options are displayed. User Response: None.

3209E Network node name missing Explanation: A NETDEST command specifying the ADD, ALTER or DELETE functions did

not specify the NETNODE operand. System Action: If the NETDEST command was issued from the LOADNET initialization

file, ESP/WM action message 3328A is issued to prompt for an END response to ignore the NETDEST command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command. If the NETDEST command was issued as an operator command, processing continues.

User Response: If the NETDEST command was issued from the LOADNET initialization file, respond to the prompt and correct or delete the erroneous NETDEST command in the LOADNET initialization file. Then if ESP/WM was terminated, restart it. If the NETDEST command was issued as an operator command, re-enter the NETDEST command specifying NETNODE(xxxx), where - xxxx specifies a valid network node name.

3210E NETWORK command missing Explanation: A NETWORK command was issued with no operands. System Action: The NETWORK command is ignored. User Response: For a list of valid NETWORK command options, enter:

NETWORK HELP or NET H or NET ?

366 ESP-5.4-MC-03

3211E NETWORK <option> command invalid Explanation: A NETWORK command was issued with an invalid option. System Action: The NETWORK <option> command is ignored. User Response: For a list of valid NETWORK command options, enter:

NETWORK HELP or NET H or NET ?

3212E NETWORK <option> not an initialization command Explanation: A NETWORK command in the LOADNET file specifies an option that is

invalid at initialization. System Action: ESP/WM action message 3328A is issued to prompt for an END response to

ignore the NETWORK <option> command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command.

User Response: Respond to the prompt and delete the erroneous NETWORK <option> command in the LOADNET initialization file.

3213E NETWORK <option> sub-command missing Explanation: A NETWORK <option> command that was issued requires one or more

additional operands. System Action: The NETWORK <option> command is ignored. User Response: For a list of valid NETWORK <option> command options, enter:

NETWORK HELP <option> or NET H <option> or NET ? <option>

3214E NETWORK <option> sub-command <sub_option> invalid Explanation: A NETWORK <option> command specified an invalid operand <sub_option>. System Action: The NETWORK <option> command is ignored. User Response: For a list of valid NETWORK <option> command options, enter:

NETWORK HELP <option> or NET H <option> or NET ? <option>

3215C NET HELP Explanation: Response to NETWORK HELP command. System Action: The NETDEST command options are displayed. User Response: None.

3216E NETWORK HELP command operand <operand> invalid Explanation: A NETWORK HELP command specified an invalid operand. System Action: The NETWORK HELP command is ignored. User Response: For a list of valid NETWORK HELP command options, enter:

NETWORK HELP HELP or NET H H or NET ? ?

Messages and Codes

ESP-5.4-MC-03 367

3217C NET DISPLAY LOCAL Explanation: Response to NETWORK DISPLAY LOCAL command. System Action: Network and host attributes of the local network node are displayed. User Response: None.

3218I No active network TCP listeners Explanation: Response to NETWORK DISPLAY LISTENERS command. System Action: Processing continues. User Response: None.

3219I TCP listener active on port <port> Explanation: Response to NETWORK DISPLAY LISTENERS command.

One TCP listener is active, on TCP port number <port>. System Action: Processing continues. User Response: None.

3220C NET DISPLAY LISTENERS Explanation: Response to NETWORK DISPLAY LISTENERS command.

More than one TCP listener is active. System Action: Processing continues. User Response: None.

3221W TCP listener already active on port <port> Explanation: Response to NETWORK START LISTENER PORT(<port>) command.

<port> specifies a TCP port number. System Action: If the NETWORK START LISTENER PORT(<port>) command was issued from the

LOADNET initialization file, ESP/WM action message 3328A is issued to prompt for an END response to ignore the command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command. If the NETWORK START LISTENER PORT(<port>) command was issued as an operator command, processing continues.

User Response: If the NETWORK START LISTENER PORT(<port>) command was issued from the LOADNET initialization file, reply END to action message 3328A and delete the duplicate NETWORK START LISTENER PORT(<port>) command from the LOADNET initialization file.

3222I TCP listener started on port <port> Explanation: Response to NETWORK START LISTENER PORT(<port>) command.

<port> specifies a TCP port number. System Action: A Network Delivery Service (NDS) listener listens for incoming

connections requests on TCP port <port>. User Response: None.

3223I TCP listener on port <port> stopped Explanation: Response to NETWORK STOP LISTENER PORT(<port>) command.

<port> specifies a TCP port number. System Action: The Network Delivery Services (NDS) listener listening for incoming

368 ESP-5.4-MC-03

connection requests on TCP port <port> terminates. User Response: None.

3224W TCP listener not active on port <port> Explanation: Response to NETWORK STOP LISTENER PORT(<port>) command.

<port> specifies a TCP port number. System Action: The NETWORK STOP LISTENER PORT(<port>) command is ignored. User Response: To display the active Network Delivery Services (NDS) listeners,

enter the command: NETWORK DISPLAY LISTENERS or NET D L If only one Network Delivery Services (NDS) listener is active, then it can be stopped with the command: NETWORK STOP LISTENER or NET P L If more than one Network Delivery Services (NDS) listener is active, then the PORT(<port>) operand must be specified to stop a listener with the command: NETWORK STOP LISTENER <PORT> or NET P L <port>

3225W TCP listener(s) not active Explanation: Response to NETWORK STOP LISTENER PORT(<port>) command.

No Network Delivery Servcies (NDS) TCP listeners are active. <port> specifies a TCP port number.

System Action: The NETWORK STOP LISTENER PORT(<port>) command is ignored. User Response: None.

3226W TCP port required, more than one TCP listener active Explanation: Response to NETWORK STOP LISTENER command.

There is more than one active Network Delivery Services (NDS) TCP listener. Therefore the PORT(<port>) operand must be specified to identify which one to stop.

System Action: The NETWORK STOP LISTENER command is ignored. User Response: To display the active Network Delivery Services (NDS) TCP listeners,

enter: NETWORK DISPLAY LISTENERS or NET D L Then if required, enter: NETWORK STOP LISTENER PORT(<port>) or NET P L P(<port>) where - <port> specifies the TCP port number of the Network Delivery Services (NDS) listener to be stopped.

3227I No pending network connects Explanation: Response NETWORK DISPLAY PENDING command. System Action: Processing continues.

Messages and Codes

ESP-5.4-MC-03 369


3228C NET DISPLAY PENDING Explanation: Response to NETWORK DISPLAY PENDING command. System Action: The pending Network Delivery Services (NDS) connections are

displayed. User Response: None.

3229E NETWORK STOP PENDING operand(s) missing Explanation: Response NETWORK STOP PENDING command.

Either the HOST(<host_or_ip>) or ALL operand must be specified to identify which pending Network Delivery Services (NDS) connect(s) to stop. <host_or_ip> specifies a DNS host name or IP address.

System Action: The NETWORK STOP PENDING command is ignored. User Response: To display the pending Network Delivery Services (NDS) connect(s),

enter the command: NETWORK DISPLAY PENDING or NET D P Then, if required, re-issue a NETWORK STOP PENDING command specifying either the HOST(<host_or_ip>) or ALL operand.

3230E HOST required when PORT specified Explanation: Response NETWORK STOP PENDING command.

If the PORT(<port>) operand is specified, then the HOST(<host_or_ip>) operand must also be specified. <host_or_ip> specifies a DNS host name or IP address. <port> specifies a TCP port number.


enter the command: NETWORK DISPLAY PENDING or NET D P Then if required, enter the command: NETWORK STOP PENDING HOST(<host_or_ip>) PORT(<port>) or NET P P H(<host_or_ip>) P(<port>)

3231E ALL and PORT mutually exclusive Explanation: Response NETWORK STOP PENDING command.

Either the ALL operand, the HOST(<host_or_ip>) operand, or the HOST(<host_or_ip>) and PORT(<port>) operands must be specified. <host_or_ip> specifies a DNS host name or IP address. <port> specifies a TCP port number.


enter the command: NETWORK DISPLAY PENDING or NET D P Then if required, re-issue the NETWORK STOP PENDING command with

370 ESP-5.4-MC-03

compatible operands. For a list of valid NETWORK STOP command options, enter the command: NETWORK HELP STOP or NET H P or NET ? P

3232W No pending network connects Explanation: Response NETWORK STOP PENDING ALL command.

There are no pending Network Delivery Services (NDS) connects. Therefore none can be stopped.


3233W Pending connect{(s)} to {(<host>)}<ip>{:<port>} not found Explanation: Response NETWORK STOP PENDING HOST(<host_or_ip>) {PORT(<port>)}

command. The specified Network Delivery Services (NDS) pending connect(s) were not found. <host_or_ip> specifies a DNS host name or IP address. <host> specifies a DNS host name. <ip> specifies an IP address. <port> specifies a TCP port number.

System Action: Processing continues. User Response: To display the pending Network Delivery Services (NDS) connect(s),

enter the command: NETWORK DISPLAY PENDING or NET D P Then if required, enter the command: NETWORK STOP PENDING HOST(<host_or_ip>) {PORT(<port>)} or NET P P H(<host_or_ip>) {P(<port>)}

3234C NET STOP PENDING Explanation: Response NETWORK STOP PENDING command.

More than one pending Network Delivery Services (NDS) connect was stopped.

System Action: The specified pending Network Delivery Services (NDS) connects are stopped.


3235I Pending connect to {(<host>)}<ip>:<port> stopped Explanation: Response NETWORK STOP PENDING command.

One pending network connect was stopped. <host> specifies a DNS host name. <ip> specifies an IP address. <port> specifies a TCP port number.

System Action: The specified pending Network Delivery Services (NDS) connect is stopped.


Messages and Codes

ESP-5.4-MC-03 371

3236I No active network connections Explanation: Response NETWORK DISPLAY CONNECTIONS command.

There are no active Network Delivery Services (NDS) connections. System Action: Processing continues. User Response: None.

3237C NET DISPLAY CONNECTIONS Explanation: Response NETWORK DISPLAY CONNECTIONS command. System Action: The active Network Delivery Services (NDS) connections are displayed. User Response: None.

3238C NET SET CONNECTIONS Explanation: Response NETWORK SET CONNECTIONS command. System Action: Requested Network Delivery Services (NDS) connection default changes,

if any, are made. Then the Network Delivery Services (NDS) connection defaults are displayed.


3239C NET START CONNECTION Explanation: Response NETWORK START CONNECTION command. System Action: The specified Network Delivery Services (NDS) connection is started. User Response: None.

3240E NETWORK STOP CONNECTIONS operand missing Explanation: Response NETWORK STOP CONNECTIONS command.

Either the ALL, IDENTIFIER(<id>), NETNODE(<netnode>) or HOST(<host_or_ip>) operand must be specified to identify which Network Delivery Service (NDS) connection(s) to stop. <id> specifies a unique host identifier. <netnode> specifies a network node name. <host_or_ip> specifies a DNS host name or IP address.

System Action: The NETWORK STOP CONNECTIONS command is ignored. User Response: If required, re-issue the NETWORK STOP CONNECTIONS command with the

ALL, IDENTIFIER(<id>), NETNODE(<netnode>) or HOST(<host_or_ip>) operand. For a list of valid NETWORK STOP command options, enter the command: NETWORK HELP STOP or NET H P or NET ? P To display active network connections, enter the command: NETWORK DISPLAY CONNECTIONS or NET D C

3241C NET STOP CONNECTIONS Explanation: Response NETWORK STOP CONNECTIONS command. System Action: The specified Network Delivery Services (NDS) connection(s) are

stopped. User Response: None

372 ESP-5.4-MC-03

3242W No active network connections Explanation: Response NETWORK STOP CONNECTIONS ALL command.

There are no active Network Delivery Services (NDS) connections. System Action: Processing continues. User Response: None

3243W {Connection <id>}|{Network node <netnode>} not found Explanation: Response to NETWORK STOP CONNECTION IDENTIFIER(<id>) or

NETWORK STOP NETNODE(<id>) command. The specified Network Delivery Services (NDS) connection was not found. <id> specifies the unique identifier of a Network Delivery Services (NDS) connection. <netnode> specifies the network node of a Network Delivery Services (NDS) connection.

System Action: The NETWORK STOP CONNECTION IDENTIFIER(<id>) or NETWORK STOP NETNODE(<id>) command is ignored.

User Response: To display the active network TCP connections, enter the command: NETWORK DISPLAY CONNECTIONS or NET D C Then if required, enter: NETWORK STOP CONNECTION IDENTIFIER(<id>) or NET P C ID(<id>) or NETWORK STOP CONNECTION NETNODE(<netnode>) or NET P C N(<netnode>)

3244W No active connection(s) for host {(<host>)}<ip> Explanation: Response NETWORK STOP CONNECTIONS HOST(<host_or_ip>) command. No

active Network Delivery Services (NDS) connection for the specified host exists. <host_or_ip> specifies a DNS host name or IP address. <host> specifies a DNS host name. <ip> specifies an IP address.

System Action: The NETWORK STOP CONNECTIONS HOST(<host_or_ip>) command is ignored.

User Response: To display the active network TCP connections, enter the commandL NETWORK DISPLAY CONNECTIONS or NET D C Then if required, enter the command: NETWORK STOP CONNECTIONS HOST(<host_or_ip>) or NET P C H(<host_or_ip>)

3245E <command> only permissible from a console Explanation: An authorized Network Delivery Services (NDS) command has been issued

from a source other than a console, such as from TSO/ISPF page mode or an ESP line mode interface. <command> specifies one of the following Network Delivery Services (NDS) commands -

Messages and Codes

ESP-5.4-MC-03 373

NETAUTH ADD NETAUTH DELETE NETDEST ADD NETDEST ALTER NETDEST DELETE NETWORK SET CONNECTION AUTHENTICATE NETWORK SET CONNECTION NOAUTHENTICATE NETWORK STOP CONNECTIONS

System Action: The Network Delivery Services (NDS) command is ignord. User Response: Issue the Network Delivery Services (NDS) command from a console if

authorized to do so.

3246I No registered network services Explanation: Response to NETWORK DISPLAY SERVICES command.

There are no network (NDS) services. Never happens under ESP/WM. System Action: Processing continues. User Response: None.

3247C Network Services Explanation: Response to NETWORK DISPLAY SERVICES command. System Action: The registered network (NDS) services and their status are displayed. User Response: None.

3248W Network <service> service already active Explanation: Response to NETWORK START SERVICE <service> command.

The specified network (NDS) service is already active and therefore cannot be started. <service> specifies a network service name.

System Action: If the NETWORK START SERVICE <service> command was issued from the LOADNET initialization file, ESP/WM action message 3328A is issued to prompt for an END response to ignore the command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command. If the NETWORK START SERVICE <service> command was issued as an operator command, processing continues.

User Response: If the NETWORK START SERVICE <service> command was issued from the LOADNET initialization file, reply END to action message 3328A and delete the duplicate NETWORK START SERVICE <service> command from the LOADNET initialization file.

3249W Network <service> service not active Explanation: Response to NETWORK STOP SERVICE <service> command.

The specified network (NDS) service is not active and therefore cannot be stopped. <service> specifies a network service name.

System Action: Processing continues. User Response: None

3250E Network <service> service not found Explanation: Response to NETWORK START|STOP SERVICE <service> command

374 ESP-5.4-MC-03

The specified network (NDS) service does not exist. <service> specifies a network service name.

System Action: If a NETWORK START SERVICE <service> command was issued from the LOADNET initialization file, ESP/WM action message 3328A is issued to prompt for an END response to ignore the command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command. If a NETWORK START SERVICE <service> or NETWORK STOP SERVICE <service> command was issued as an operator command, processing continues.

User Response: If a NETWORK START SERVICE <service> command was issued from the LOADNET initialization file, reply to action message 3328A, correct or delete the NETWORK START SERVICE <service> command in the LOADNET initialization file, and if ESP/WM was terminated, restart it. If a NETWORK START SERVICE <service> or NETWORK STOP SERVICE <service> command was issued as an operator command, then to display the network services, enter the command: NETWORK DISPLAY SERVICES or NET D S Then if required, re-issue the NETWORK START|STOP SERVICE <service> command specifying the correct network (NDS) service name.

3251I Network <service> service started Explanation: Response to NETWORK START SERVICE <service> command.

<service> specifies a network service name. System Action: The specified network (NDS) service is started. User Response: None

3252I Network <service> service stopped Explanation: Response to NETWORK STOP SERVICE <service> command.

<service> specifies a network service name. System Action: The specified network (NDS) service is stopped. User Response: None

3253E Connection rejected, cannot determine identity of {(<host>)}<ip>:<port>

Explanation: An unexpected error occurred during Network Delivery Service (NDS) connection handshake processing. <host> specifies the DNS host name of the connection partner. <ip> specifies the IP address of the connection partner. <port> specifies the TCP port number of the connection partner.

System Action: The connection is terminated. User Response: Attempt to restart the Network Delivery Service (NDS) connection with

the command: NETWORK START CONNECTION HOST(<host_or_ip>) PORT(<port>) or NET S C H(<host_or_ip>) P(<port>) where - <host_or_ip> specifies the DNS host name or IP address of the connection partner. <port> specifies the TCP port number of the connection partner.

Messages and Codes

ESP-5.4-MC-03 375

If the problem persists, contact Cybermation support.

3254W Connect request from|to <ip> rejected, not authorized Explanation: An outbound or inbound Network Delivery Services (NDS) connection

has been requested. However, the host that the remote ESP/WM is executing on is not authorized to connect to the local ESP/WM because the local ESP/WM's network authentication is enabled and the remote ESP/WM host's IP address has not been authorized to connect to the local ESP/WM. <ip> specifies the IP address of the remote host.

System Action: The Network Delivery Services (NDS) connection is not established. User Response: If ESP/WM on the remote host should be authorized to connect to the

local ESP/WM, then the following command should be added to the local ESP/WM's LOADNET initialization file or issued from a console to the local ESP/WM: NETAUTH HOST(<host_or_ip>) where - <host_or_ip> specifies the DNS host name or IP address of the host that the remote ESP/WM is executing on. If ESP/WMs on any host in the network should be authorized to connect to the local ESP/WM, then the following command should be added to the local ESP/WM's LOADNET initialization file or issued from a console to the local ESP/WM: NETWORK SET CONNECTIONS AUTHENTICATE

3255C Network Connection {Out|In}bound TCP connection established

Explanation: An outbound or inbound Network Delivery Services (NDS) connection has been established.


3256E Network node <netnode> not defined as a network destination Explanation: While attempting to establish a Network Delivery Services (NDS)

connection, the network node name that the remote partner identified itself with was not defined as a network destination to the local partner. <netnode> specifies the network node name of the remote partner.

System Action: Message 3273C is issued and the connection is aborted. User Response: If the Network Delivery Service (NDS) connection is desired, then

ensure that there is a NETDEST command in the local ESP/WM's LOADNET initialization file specifying the same network node name that the remote ESP/WM's NETNODE command specifies in its LOADNET initialization file.

3257W Network node <netnode> duplicate connection Explanation: An attempt was made to establish a Network Delivery Services (NDS)

connection. However, a connection between the local network node and

376 ESP-5.4-MC-03

the remote network node already exists. <netnode> specifies the remote network node name.

System Action: Message 3273C is issued and the connection is aborted. User Response: None.

3258E Network node <netnode> destination specification mismatch Explanation: While attempting to establish a Network Delivery Services (NDS)

connection, a host destination specification that the remote partner identified itself with did not correspond to the host destination specification of the network destination definition (specified by the NETDEST ADD command) for the network node of the remote partner. Possible host destination specifications (NETDEST ADD command operands) are: SYSPLEX, SYSNAME, XCFGROUP, XCFMEMBER, JESNODE, JESMEMBER, SYSID

System Action: Message 3272C is issued and the connection is aborted. User Response: Either modify the host destination specification in the NETDEST ADD

command that defines the remote partner, or delete the host destination specification. A NETDEST ADD command must contain at least one host destination specification. For ESP/WM subsystems, NETDEST ADD commands are specified in the LOADNET initialization file. They can also be issued dynamically as ESP operator commands from a console provided there is no active Network Delivery Services (NDS) connection to the specified network node.

3259I Buffer size negociated down from <higher_value> to <lower_value> by TCP partner {(<host>)}<ip>:<port>

Explanation: During Network Delivery Services (NDS) connection handshake processing the remote ESP/WM informed the local ESP/WM that its proposed network buffer size is too large and must be adjusted downward to a lower value. <higher_value> specifies the original proposed network buffer size. <lower_value> specifies the value that the network buffer size has been negociated downward to. <host> specifies the DNS host name of the remote ESP/WM. <ip> specifies the IP address the remote ESP/WM. <port> specifies the TCP port number the remote ESP/WM.

System Action: The local ESP/WM adjusts its network buffer size down from <higher_value> to <lower_value> and Network Delivery Services (NDS) connection establishment continues.


3260E Unidentifiable acknowledgement from {(<host>)}<ip>:<port>, Message=<token>

Explanation: An acknowledgement to a Network Delivery Services (NDS) message was received from a remote ESP/WM. However, the local ESP/WM's network receiver (for the Network Delivery Services (NDS) connection to the

Messages and Codes

ESP-5.4-MC-03 377

remote ESP/WM) was unable to associate the acknowledgement with a previously transmitted message requiring an acknowledgement. <host> specifies the DNS host name of the connection partner. <ip> specifies the IP address of the connection partner. <port> specifies the IP address of the connection partner. <token> specifies an internal hexadecimal token to identify the message.

System Action: The acknowledgement is discarded. User Response: If the problem is persistent, call Cybermation support.

3261C Negative Ack <reason> Partner={(<host>)}<ip>:<port>, NetNode=<netnode>, Service=<service>, Message=<token>

Explanation: The local Network Delivery Services (NDS) partner received a negative acknowledgement from the remote partner after transmitting data to it. <reason> specifies the reason for the negative acknowledgement. <host> specifies the DNS host name of the remote Network Delivery Services (NDS) partner. <ip> specifies the IP address of the remote Network Delivery Services (NDS) partner. <port> specifies the TCP port number of the remote Network Delivery Services (NDS) partner. <netnode> specifies the network node name of the remote Network Delivery Services (NDS) partner. <service> specifies the network (NDS) service on behalf of which the data was transmitted. <token> specifies a token that uniquely identifies the message.

System Action: Additional message(s) clarifying the reason for the negative ackowledgement may follow. Network Delivery Services (NDS) recovers from the error and processing continues.

User Response: If the condition is an isolated incident, then there is probably no problem and it can be ignored. However, if the condition persists, then attempt to determine its cause, and correct it if possible. If unable to determine and/or correct the problem, contact Cybermation support.

3262C Response Error Command not found for response <reason> Partner={(<host>)}<ip>:<port>, NetNode=<netnode>, Service=<service>, Message=<token>

Explanation: The local Network Delivery Services (NDS) partner received a data response from the remote partner. However, the command to which the response was responding could not be found. This condition could occur, for example, if the command times out before the response is received. <host> specifies the DNS host name of the remote Network Delivery

378 ESP-5.4-MC-03

Services (NDS) partner. <ip> specifies the IP address of the remote Network Delivery Services (NDS) partner. <port> specifies the TCP port number of the remote Network Delivery Services (NDS) partner. <netnode> specifies the network node name of the remote Network Delivery Services (NDS) partner. <service> specifies the network (NDS) service on behalf of which the data was transmitted. <token> specifies a token that uniquely identifies the message.

System Action: The data response is discarded. User Response: If the condition is an isolated incident, then there is probably no

problem and it can be ignored. However, if the condition persists, then attempt to determine its cause, and correct it if possible. If unable to determine and/or correct the problem, contact Cybermation support.

3263C Connection aborted Duplicate partner{(<host>)}<ip>:<port> detected

Explanation: The local partner was attempting to establish a Network Delivery Services (NDS) connection with a remote partner at the same time that the remote partner was attempting to establish a Network Delivery Services (NDS) connection with the local partner <host> specifies the DNS host name of the remote Network Delivery Services (NDS) partner. <ip> specifies the IP address of the remote Network Delivery Services (NDS) partner. <port> specifies the TCP port number of the remote Network Delivery Services (NDS) partner.

System Action: One of the connections is aborted. The other connnection is established, provided no errors occur.


3264W TCP receive <interval> second time out: <socket> Explanation: A TCP receive timed out while a Network Delivery Services (NDS)

connection was being established. <interval> specifies the receive timer interval in seconds. <socket> specifies the local and remote IP addresses and TCP port numbers, and the data flow direction.

System Action: The connection is aborted. User Response: If required, attempt to reconnect to the target Network Delivery

Services (NDS) listener by issuing the command: NETWORK START CONNECTION HOST(<host_or_ip>) PORT(<port>) command, where - <host_or_ip> specifies the DNS host name or IP address of the target host. <port> specifies the TCP port number of the target Network Delivery Services (NDS) TCP listener. If the problem persists, attempt to determine the cause and correct

Messages and Codes

ESP-5.4-MC-03 379

it. Then attempt to reconnect to the target Network Delivery Services (NDS) listener.

3265C Network Connection TCP receive <interval> second time out

Explanation: A TCP receive on a Network Delivery Services (NDS) connection timed out. <interval> specifies the receive timer interval in seconds.

System Action: The Network Delivery Services (NDS) connection is terminated. User Response: If required, attempt to reconnect to the target Network Delivery

Services (NDS) listener by issuing the command: NETWORK START CONNECTION HOST(<host_or_ip>) PORT(<port>) command, where - <host_or_ip> specifies the DNS host name or IP address of the target host. <port> specifies the TCP port number of the target Network Delivery Services (NDS) TCP listener. If the problem persists, attempt to determine the cause and correct it. Then attempt to reconnect to the target Network Delivery Services S) (NDS) listener.

3266W TCP connection purged: <socket> Explanation: A TCP connection was purged while a Network Delivery Services (NDS)

connection was being established. <socket> specifies the local and remote IP addresses and TCP port numbers, and the data flow direction.

System Action: The Network Delivery Services (NDS) connection is aborted. User Response: If required, attempt to reconnect to the target Network Delivery

Services (NDS) listener by issuing the command: NETWORK START CONNECTION HOST(<host_or_ip>) PORT(<port>) command, where - <host_or_ip> specifies the DNS host name or IP address of the target host. <port> specifies the TCP port number of the target Network Delivery Services (NDS) TCP listener.

3267C Network Connection TCP connection purged Explanation: A Network Delivery Services (NDS) TCP connection was purged. System Action: The Network Delivery Services (NDS) connection is terminated. User Response: If required, attempt to reconnect to the target Network Delivery


380 ESP-5.4-MC-03

3268W TCP connection terminating due to error: <socket> Explanation: A TCP error occurred while a Network Delivery Services (NDS)

connection was being established. <socket> specifies the local and remote IP addresses and TCP port numbers, and the data flow direction.

System Action: The Network Delivery Services (NDS) connection is aborted. User Response: If required, attempt to reconnect to the target Network Delivery

Services (NDS) listener by issuing the command: NETWORK START CONNECTION HOST(<host_or_ip>) PORT(<port>) command, where - <host_or_ip> specifies the DNS host name or IP address of the target host. <port> specifies the TCP port number of the target Network Delivery Services (NDS) TCP listener. If the problem persists, attempt to determine the cause and correct it. Then attempt to reconnect to the target Network Delivery Services S) (NDS) listener.

3269C Network Connection TCP connection terminating due to error Explanation: A TCP error occurred on a Network Delivery Services (NDS) connection.

<socket> specifies the local and remote IP addresses and TCP port numbers, and the data flow direction.

System Action: The Network Delivery Services (NDS) connection is terminated. User Response: If required, attempt to reconnect to the target Network Delivery

Services (NDS) listener by issuing the command: NETWORK START CONNECTION HOST(<host_or_ip>) PORT(<port>) command, where - <host_or_ip> specifies the DNS host name or IP address of the target host. <port> specifies the TCP port number of the target Network Delivery Services (NDS) TCP listener. If the problem persists, attempt to determine the cause and correct it. Then attempt to reconnect to the target Network Delivery Services (NDS) listener.

3270W TCP connection prematurely terminated by partner: <socket> Explanation: While a Network Delivery Services (NDS) connection was being

established, the remote partner unexpectedly terminated it. <socket> specifies the local and remote IP addresses and TCP port numbers, and the data flow direction.

System Action: The Network Delivery Services (NDS) connection is aborted. User Response: The reason the Network Delivery Services (NDS) connection was

terminated by the remote partner is specified in a message in the remote partner's JES job message log. In some cases a normal condition caused the error and nothing need be done. If an abnormal condition occurred, attempt to determine its cause and correct it. Then, if required, attempt to reconnect to the target Network Delivery

Messages and Codes

ESP-5.4-MC-03 381


3271C Network Connection TCP connection terminating due to error Explanation: A Network Delivery Services (NDS) connection was unexpectedly

terminated by the remote partner. System Action: The Network Delivery Services (NDS) connection is terminated. User Response: The reason the Network Delivery Services (NDS) connection was

terminated by the remote partner is specified in a message in the remote partner's JES job message log. In some cases a normal condition caused the error and nothing need be need be done. If an abnormal condition occurred, attempt to determine its cause and correct it. Then, if required, attempt to reconnect to the target Network Delivery Services (NDS) listener by issuing the command: NETWORK START CONNECTION HOST(<host_or_ip>) PORT(<port>) command, where - <host_or_ip> specifies the DNS host name or IP address of the target host. <port> specifies the TCP port number of the target Network Delivery Services (NDS) TCP listener.

3272W Duplicate connection closed by partner {(<host>)}<ip>:<port> Explanation: A Network Delivery Services (NDS) connection was started. However, a

connection to the specified remote partner already exists. <host> specifies the DNS host name of the remote Network Delivery Services (NDS) partner. <ip> specifies the IP address of the remote Network Delivery Services (NDS) partner. <port> specifies the TCP port number of the remote Network Delivery Services (NDS) partner.

System Action: The Network Delivery Services (NDS) connection is terminated. User Response: None.

3273C Network Data Error {<code>, }<reason> Connection to {(<host>)}<ip>:<port> aborted

Explanation: While attempting to establish a Network Delivery Services (NDS) connection, an error in the data transmitted by the remote partner was detected by the local partner. <code> specifies a 4 character internal code. <reason> specifies the reason for the network data error. <host> specifies the DNS host name of the remote Network Delivery Services (NDS) partner. <ip> specifies the IP address of the remote Network Delivery

382 ESP-5.4-MC-03

Services (NDS) partner. <port> specifies the TCP port number of the remote Network Delivery Services (NDS) partner.

System Action: The connection is aborted. User Response: Attempt to determine the cause of the connection failure, and correct

it. If the problem persists, contact Cybermation support.

3274W Network <service> service not active Explanation: An unsuccessful attempt was made to transmit data to a remote Network

Delivery Servicies (NDS) node. However, the network service, which does not support message queuing, was not active. <service> specifies the network service.

System Action: The data is not transmitted User Response: The network service must be started with the command:

NETWORK START SERVICE <service> before a retry of the request that transmits data to the remote network node can be successful.

3275W Network Connection TCP connection stopped due to error Explanation: An error was detected in data received from the remote network node

of a Network Delivery Services (NDS) connection. This message is usually preceded by an error message that describes the data error.

System Action: The Network Delivery Service (NDS) connection is stopped. User Response: If the problem persists, then attempt to diagnose and correct it.

Then attempt to restart the Network Delivery Services (NDS) connection with the command: NETWORK START CONNECTION HOST(<host_or_ip>) PORT(<port>) command, where - <host_or_ip> specifies the DNS host name or IP address of the target host. <port> specifies the TCP port number of the target Network Delivery Services (NDS) TCP listener. If unable to determine and/or correct the problem, contact Cybermation support.

3276I {Service=<service>}{, }{NetNode=<netnode>}{, }{Host=<ip>} Explanation: This message normally follows a Network Delivery Services (NDS)

connections related warning or error message. It identifies the network service and the network node of the remote Network Delivery Services (NDS) partner. <service> specifies the network service name. <netnode> specifies the remote partner network node name. <ip> specifies the remote partner IP address.

System Action: Depends on the condition described by the preceding warning or error message.

User Response: See documentation for preceding warning or error message and if necessary, take appropriate steps to correct the condition.

Messages and Codes

ESP-5.4-MC-03 383

3277C Network Destination {Service=<service>}{, }{NetNode=<netnode>}{, }{Host=<host>}{, } {Sysplex=<sysplex>{, Sysname=<sysname>}{, XcfGroup=<xcfgroup> {, XcfMember=<xcfmember>}}}{, JesNode=<jesnode>{, JesMember=<jesmember>}}{, Sysid=sysid}

Explanation: This message normally follows a Network Delivery Services (NDS) connections related warning or error message. It identifies the network service and the remote network node. <service> specifies the remote partner network service name. <netnode> specifies the remote partner network node name. <host> specifies the remote partner IP address. <sysplex> specifies the remote partner sysplex name. <sysname> specifies the remote partner system name. <xcfgroup> specifies the remote partner XCF group name. <xcfmember> specifies the remote partner XCF member name. <jesnode> specifies the remote partner JES node name. <jesmember> specifies the remote partner JES member name. <sysid> specifies the remote partner Cybermation system identifier.

System Action: Depends on the condition described by the preceding warning or error message.

User Response: See documentation for preceding warning or error message and if necessary, take appropriate steps to correct the condition.

3278I No network authority profiles defined Explanation: Response to NETAUTH LIST command.

No Network Delivery Services (NDS) authority profiles have been defined with NETAUTH ADD commands.


3279C NETAUTH LIST Explanation: Response to NETAUTH or NETAUTH LIST command. System Action: The Network Delivery Services (NDS) authority profiles are displayed. User Response: None.

3280E Network authority profile already defined, Host={(<host>)}<ip> Explanation: Response to NETAUTH ADD HOST(<host_or_ip>) command.

An attempt was made to create a Network Delivery Services (NDS) authority profile that already exists for the specified host. <host_or_ip> specifies the DNS host name or IP address of the remote Network Delivery Services (NDS) destination. <host> specifies the DNS host name of the remote Network Delivery Services (NDS) destination. <ip> specifies the IP address of the remote Network Delivery Services (NDS) destination.

System Action: If the NETAUTH ADD HOST(<host_or_ip>) command was issued from the LOADNET initialization file, ESP/WM action message 3328A is issued to

384 ESP-5.4-MC-03

prompt for an END response to ignore the command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command. If NETAUTH ADD HOST(<host_or_ip>) was issued as an operator command, it is ignored.

User Response: If the NETAUTH ADD HOST(<host_or_ip>) command was issued from the LOADNET initialization file, reply END to action message 3328A and delete the duplicate NETAUTH ADD HOST(<host_or_ip>) command from the LOADNET initialization file.

3281I Network authority profile added, Host={(<host>)}<ip> Explanation: Response to NETAUTH ADD HOST(<host_or_ip>) command.

<host_or_ip> specifies the DNS host name or IP address of the remote Network Delivery Services (NDS) destination. <host> specifies the DNS host name of the remote Network Delivery Services (NDS) destination. <ip> specifies the IP address of the remote Network Delivery Services (NDS) destination.

System Action: A qetwork Delivery Services (NDS) authority profile is added for the specified host.


3282E Network authority profile not found, Host={(<host>)}<ip> Explanation: Response to NETAUTH DELETE HOST(<host_or_ip>) command.


System Action: The NETAUTH DELETE HOST(<host_or_ip>) command is ignored. User Response: To display the Network Delivery Services (NDS) authority profiles,

enter the command: NETAUTH or NETAUTH LIST Then, if required, re-enter the NETAUTH DELETE HOST(<host_or_ip>) command specifying the DNS host name or IP address of an existing Network Delivery Services (NDS) authority profile.

3283I Network authority profile deleted, Host={(<host>)}<ip> Explanation: Response to NETAUTH DELETE HOST((<host_or_ip>) command.


System Action: The specified Network Delivery Services (NDS) authority profile is deleted.


Messages and Codes

ESP-5.4-MC-03 385

3284C NETDEST LIST Explanation: Response to NETDEST or NETDEST LIST command. System Action: The Network Delivery Service (NDS) destination profiles are displayed. User Response: None.

3285I No{ matching} network destinations found Explanation: Response to NETDEST or NETDEST LIST command.

If the command was specified with no network destination operands then no network (NDS) destinations have been defined. If the command was specified with at least one destination operand, then no matching network (NDS) destinations have been defined. The following network destination operands may be specified: HOST, SYSPLEX, SYSNAME, XCFGROUP, XCFMEMBER, JESNODE, JESMEMBER, SYSID.

System Action: Processing continues. User Response: If the NETDEST or NETDEST LIST command was specfied with at least one

network (NDS) destination operand, then the command can be re-issued with no network (NDS) destination operands in order to determine if any network (NDS) destinations exist.

3286E Network node <netnode> is local, cannot also be a network destination Explanation: Response to NETDEST ADD NETNODE(<netnode>) command.

The specified network node has already been defined as the local network node with a NETNODE <netnode> command. <netnode> specifies the network node of the network (NDS) destination.

System Action: If the NETDEST ADD NETNODE(<netnode>) command was issued from the LOADNET initialization file, ESP/WM action message 3328A is issued to prompt for an END response to ignore the command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command. If the NETDEST ADD NETNODE(<netnode>) was issued as an operator command, it is ignored.

User Response: If the NETDEST ADD NETNODE(<netnode>) command was issued from the LOADNET initialization file, reply to action message 3328A and correct or delete the NETDEST ADD NETNODE(<netnode>) command in the LOADNET initialization file. Then if ESP/WM was terminated, restart it. If the NETDEST ADD NETNODE(<netnode>) command was issued as an operator command, then to display the network destinations, enter the command: NETDEST or NETDEST LIST Then if required, re-issue the NETDEST ADD NETNODE(<netnode>) specifying the correct network node name.

3287E Network node <netnode> already defined Explanation: Response to NETDEST ADD NETNODE(<netnode>) command.

An attempt was made to create a network (NDS) destination profile that

386 ESP-5.4-MC-03

already exists for the specified network node. <netnode> specifies the network node of the network destination.

System Action: If the NETDEST ADD NETNODE(<netnode>) command was issued from the LOADNET initialization file, ESP/WM action message 3328A is issued to prompt for an END response to ignore the command, a CANCEL response to terminate ESP/WM, or to re-enter a LOADNET initialization command. If the NETDEST ADD NETNODE(<netnode>) was issued as an operator command, it is ignored.

User Response: If the NETDEST ADD NETNODE(<netnode>) command was issued from the LOADNET initialization file, reply END to action message 3328A and delete the duplicate NETDEST ADD NETNODE(<netnode>) command from the LOADNET initialization file.

3288C NETDEST ADD Explanation: Response to NETDEST ADD command. System Action: A network (NDS) destination profile is created for the specified

network node. User Response: None.

3289C NETDEST ALTER Explanation: Response to NETDEST ALTER command. System Action: The network (NDS) destination profile for the target network node is

altered as specified in the NETDEST ALTER command. User Response: None.

3290E DELETE mutually exclusive with destination specification(s) Explanation: A NETDEST DELETE command specified one or more of the following

destination specification operands - HOST, SYSPLEX, SYSNAME, XCFGROUP, XCFMEMBER, JESNODE, JESMEMBER, SYSID. Destination specifications are not valid for the DELETE function of the NETDEST command.

System Action: The NETDEST DELETE command is ignored. User Response: If required, re-issue the NETDEST DELETE command without any

destination specifications.

3291W Network node <netnode> connected, cannot be deleted Explanation: An attempt was made to delete a network (NDS) destination profile with

a NETDEST DELETE NETNODE(<netnode>) command. However, a Network Delivery Services (NDS) connection to the target network node was active. <netnode> specifies the target network node name.

System Action: The NETDEST DELETE NETNODE(<netnode>) command is ignored. User Response: If the network (NDS) destination profile must be deleted, then stop

the connection to the target network node with the command: NETWORK STOP CONNECTION NETNODE(<netnode>) or NET P C N(<netnode>) Then re-issue the command -

Messages and Codes

ESP-5.4-MC-03 387

NETDEST DELETE NETNODE(<netnode>) or NETDEST D NET(<netnode>)

3292I Network node <netnode> deleted Explanation: Response to NETDEST DELETE NETNODE(<netnode>) command.

<netnode> specifies the target network node name. System Action: The target network (NDS) destination profile is deleted. User Response: None.

3293E Network node <netnode> not found Explanation: Response to NETDEST ALTER NETNODE(<netnode>) or

NETDEST DELETE NETNODE(<netnode>) command. The target network node is not defined as a network (NDS) destination. <netnode> specifies the target network node name.

System Action: Processing continues. User Response: To display network (NDS) destination profiles, enter the command:

NETDEST or NETDEST LIST Then, if required, re-enter the NETDEST ALTER NETNOODE(<netnode>) or NETDEST DELETE NETNODE(<netnode>) command specifying the network node name of an existing network (NDS) destination profile.

3294E Destination specification(s) missing Explanation: A NETDEST ADD or NETDEST ALTER command was issued without any

destination specifications. System Action: Processing continues. User Response: If required, re-issue the NETDEST ADD or NETDEST ALTER command with

at least one of the following destination specification operands: HOST, SYSPLEX, SYSNAME, XCFGROUP, XCFMEMBER, JESNODE, JESMEMBER, SYSID.

3295E <operand1> required when <operand2> specified Explanation: A NETDEST ADD or NETDEST ALTER command was issued with destination

specification <operand1> omitted and destination specification <operand2> specified. The following destination specification operand dependencies are enforced: If SYSNAME is specified, then SYSPLEX is required. If XCFGROUP is specified, then SYSPLEX is required. If XCFMEMBER is specified, then XCFGROUP is required. If JESMEMBER is specified, then JESNODE is required.

System Action: The NETDEST ADD or NETDEST ALTER command is ignored. User Response: If required, re-issue the NETDEST ADD or NETDEST ALTER command with

destination specifications <operand1> and <operand2>.

3300S ESP/WM network request xxxx invalid Explanation: Internal logic error. Should never occur. System Action: Processing continues.

388 ESP-5.4-MC-03

User Response: Notify Cybermation support.

3301E ESP/WM network service registration requested more than once Explanation: Internal logic error. Should never occur. System Action: Processing continues. User Response: Notify Cybermation support.

3302E xxxx network service(s) could not be registered Explanation: An attempt to register one or more ESP/WM network services failed.

xxxx is the number of network service that could not be registered. Should never occur.

System Action: Processing continues with the unregistered network services unavailable.

User Response: Notify Cybermation support.

3303E Network service xxxx not registered Explanation: An attempt to start an ESP/WM network service was made.

However, the network service was not previously registered. xxxx specifies the name of the network service. Internal logic error Should never occur.

System Action: The unregistered network service terminates. User Response: Notify Cybermation support.

3304E Network service xxxx already active Explanation: An attempt to start an ESP/WM network service was made.

However, the network service was already active. xxxx specifies the name of the network service.

System Action: The second network service instance terminates. User Response: None.

3305W Network service not supported by ESP/WM master|proxy subsystem Explanation: The ESPPARM initialization file contains a

"NETWORK START SERVICE xxxx" to start network service xxxx. However, either the ESP/WM subsystem is a master and the network service is not supported by ESP/WM master subsystems, or the ESP/WM is a proxy and the network service is not supported by ESP/WM proxy subsystems.

System Action: The network service terminates User Response: Remove the "NETWORK START SERVICE xxxx" from the ESPPARM

initialization file.

3306E Network service xxxx not found Explanation: An attempt to stop an ESP/WM network service was made.

However, the network service is not active. System Action: Processing continues. User Response: None.

Messages and Codes

ESP-5.4-MC-03 389

3307E NPSA not found (ESP/WM network services not initialized) Explanation: Internal logic error. Should never occur. System Action: Processing continues. User Response: Notify Cybermation support.

3309W LOADNET command ignored, only valid for ESP/WM master{ or shadow} Explanation: A LOADNET command was issued from the ESPPARM initialization file of

an ESP/WM proxy subsystem. However, the LOADNET command may only be issued from the ESPPARM initialization file of an ESP/WM master subsystem (or an ESP/WM Shadow Manager subsystem if the High Availability Option (HAO) is installed).

System Action: ESP/WM action message 802A is issued to prompt for an END reply to ignore the LOADNET command, a CANCEL reply to terminate ESP/WM, or an ESP/WM initialization command reply.

User Response: Reply to action message 802A and remove the erroneous LOADNET command from the ESPPARM initialization file.

3310I Network TRACKING receiver started Explanation: An ESP/WM master's network job tracking receiver has been started by a

"NETWORK START SERVICE TRACKING" command. System Action: Processing continues. User Response: None.

3311I Network TRACKING receiver ended Explanation: An ESP/WM master's network job tracking receiver has ended, normally

due to a "NETWORK STOP SERVICE TRACKING" command. System Action: Processing continues. User Response: None.

3312I Network TRACKING receiver waiting for checkpoint file space Explanation: An ESP/WM master's network job tracking receiver has made an

unsuccessful request for checkpoint file space. System Action: The network job tracking receiver waits for checkpoint space to become

available before proceeding. User Response: If the problem persists, attempt to determine the cause of the

checkpoint file space shortage condition.

3313I Network TRACKING receiver resumed, checkpoint file space available Explanation: An ESP/WM master's network job tracking receiver that was suspended

due to a checkpoint file space shortage condition, has resumed normal processing as sufficient checkpoint file space is now available.


3314E ISC input XME size xxxx below minimum yyyy Explanation: An ESP/WM master's network job tracking receiver has detected a data

error from a remote ESP/WM tracking transmitter.

390 ESP-5.4-MC-03

Should never happen. System Action: The network connection to the remote ESP/WM is terminated. User Response: Call Cybermation support.

3315E ISC input XME buffer size <bufsize> {mismatch with XME element size <xmesize>| inconsistency with extension offset <extoffset>, size <extsize>}

Explanation: An ESP/WM master's network job tracking receiver has detected a data error from a remote ESP/WM tracking transmitter. Should never happen.

System Action: The network connection to the remote ESP/WM is terminated. User Response: Call Cybermation support.

3316E Network routing response xxxx invalid Explanation: An ESP/WM subsystem request was transmitted to a remote ESP/WM via the

network routing service. The response to the subsystem request was invalid. xxxx specifies up to the first 16 bytes of the response in hexadecimal.

System Action: The connection to the remote ESP/WM that sent the erroneous response is stopped.

User Response: Should never happen. Call Cybermation support.

3318E xxxx byte core request failed for network response IAR and IAE, Request=yyy

Explanation: There is not enough private area virtual storage for the transmission of the response to an ESP/WM subsystem request that was issued from a remote ESP/WM via the network routing service. xxxx specifies the number of bytes required for the response to the subsystem request. yyy specifies the subsystem request function code.

System Action: ESP/WM sends error response message 3319E to the issuer of the subsystem request.

User Response: If the problem persists, recycle ESP/WM with a larger region size.

3319E Request RC=xxx, Insufficient core for yyyy byte response Explanation: An ESP/WM subsystem request was issued to a remote ESP/WM via the

network routing service. The subsystem request was processed but there was not enough virtual storage in the remote ESP/WM's address space private area for the the response to be transmitted to the local requesting ESP/WM. xxx specifies the return code of the subsystem request. yyyy specifies the number of bytes required for the response to the subsystem request.

System Action: Processing continues. User Response: If the problem persists, recycle the remote ESP/WM with a larger

region size.

Messages and Codes

ESP-5.4-MC-03 391

3320I Network ROUTING receiver started Explanation: An ESP/WM subsystem's network routing receiver has been started by a

"NETWORK START SERVICE ROUTING" command. System Action: Processing continues. User Response: None.

3321I Network ROUTING receiver ended Explanation: An ESP/WM subsystem's network routing receiver has ended, normally due

to a "NETWORK STOP SERVICE ROUTING" command. System Action: Processing continues. User Response: None.

3322E Network ROUTING receiver input data length xxxx too small for IAR Explanation: An ESP/WM subsystem's network routing receiver received input of

length xxxx from a remote ESP/WM. xxxx is too small to contain valid ESP/WM subsystem request data.

System Action: The network ROUTING service is stopped and the network routing receiver terminates.

User Response: Should never happen. Contact Cybermation support.

3323E Network ROUTING receiver input data xxxx invalid Explanation: An ESP/WM subsystem's network service ROUTING receiver received

invalid input data. xxxx specifies the first 16 bytes of the input data in hexadecimal.

System Action: The network ROUTING service is stopped and the network routing receiver terminates.

User Response: Should never happen. Contact Cybermation support.

3325E Invalid command syntax detected{ in line nnnn of xxxx{(yyyy)} Explanation: The LOADNET PARMLIB initialization file contains a command with

invalid syntax. nnnn specifies the line number of the erroneous command. xxxx specifies the data set name of the LOADNET PARMLIB file. yyyy specifies the member name of the LOADNET PARMLIB file if it a member of a PDS.

System Action: ESP/WM action message 3328A is issued to prompt for an END reply to ignore the LOADNET command, a CANCEL reply to terminate ESP/WM, or a LOADNET command reply.

User Response: Reply to action message 3328A and correct or remove the erroneous command from the LOADNET PARMLIB initialization file.

3326E Undefined command cccc{ in line nnnn of xxxx{(yyyy)} Explanation: The LOADNET PARMLIB initialization file contains an undefined command.

cccc specifies the undefined command name. nnnn specifies the line number of the undefined command. xxxx specifies the data set name of the LOADNET PARMLIB file.

392 ESP-5.4-MC-03

yyyy specifies the member name of the LOADNET PARMLIB file if it a member of a PDS.


User Response: Reply to action message 3328A and correct or remove the undefined command from the LOADNET PARMLIB initialization file.

3327E cccc command error{ in line nnnn of xxxx{(yyyy)} Explanation: A LOADNET PARMLIB initialization file command failed.

cccc specifies the command name. nnnn specifies the line number of the command. xxxx specifies the data set name of the LOADNET PARMLIB file. yyyy specifies the member name of the LOADNET PARMLIB file if it a member of a PDS.


User Response: Replay to action message 3328A and correct or remove the command from the LOADNET PARMLIB initialization file.

3328A Re-enter command, CANCEL or END Explanation: This message follows an error in a LOANET PARMLIB initialization

file command. It is preceded by a message indicating the cause of the error.

System Action: ESP/WM waits for a reply. If END is specified, ESP/WM ignores the erroneous command. If CANCEL is specified, ESP/WM terminates. If a command is entered, ESP/WM attempts to execute it.

User Response: Re-enter the correct command if the erroneous command cannot be ignored. Reply END if the erroneous command can be ignored. If uncertain what to do, reply CANCEL and ESP/WM will terminate. ESP/WM can then be restarted when the correct action has been determined. Correct or remove the erroneous command in the LOANET PARMLIB initialization file.

3350E NETQUEUE <dsname> specification ignored, message queuing not supported

Explanation: A NETQUEUE <dsname> command was issued to specify a Network Delivery Services (NDS) message queue data set. However, no registered network (NDS) service supports message queueing. <dsname> specifies the data set name of the message queue data set.

System Action: The NETQUEUE <dsname> command is ignored. User Response: Should never happen. Contact Cybermation support.

Messages and Codes

ESP-5.4-MC-03 393

3351S NETQUEUE data set not specified, message queuing required Explanation: At least one registered network (NDS) service supports message

queueing. Therefore a NETQUEUE command is required. System Action: The system shuts down. User Response: For an ESP/WM subsystem, add a NETQUEUE <dsname> command to the

LOADNET initialization file to define a Message Delivery Service (NDS) message queue data set and restart ESP/WM. <dsname> specifies the name of the Message Delivery Service (NDS) message queue data set. Library member ASEPSAME(CYBESS01) includes a sample NETQUEUE data set definition.

3352E NETQUEUE data set <dsname> verification failed Explanation: An error in the Network Delivery Services (NDS) message queue

data set was detected. This message is preceded by message 668E, which describes the error. <dsname> specifies the name of the Network Delivery Services (NDS) message queue data set.

System Action: Action message prompt 3354A follows. User Response: Respond to action message prompt 3354A.

For an ESP/WM subsystem, if the data set specified in the NETQUEUE command in the LOADNET initialization file is not a Network Delivery Service (NDS) message queue data set, then reply P to message action prompt 3354A to shutdown ESP/WM. Then correct the NETQUEUE command and restart ESP/WM. For an ESP/WM subsystem, if the Network Delivery Service (NDS) message queue data set is corrupted and it cannot be repaired with a zap, then reply F to message action prompt 3354A to request a cold reformat of the data set. Caution: Do not reply F to message action prompt 3354A if the NETQUEUE command in the LOADNET initialization file specifies a linear data set that is NOT the Network Delivery Services (NDS) message queue data set because the data sets's contents will be lost.

3353W NETQUEUE data set <dsname> format requested, already formatted Explanation: A format of the Network Delivery Services (NDS) message queue

data set was requested. However, the message queue data set is already formatted. For an ESP/WM subsystem, the request was specified by the NQFORMAT startup parameter. <dsname> specifies the data set name of the Network Delivery Services (NDS) message queue data set.

System Action: Action message prompt 3354A follows. User Response: Respond to action prompt 3354A.

Respond C to bypass a reformatting of the NETQUEUE data set. Respond F to format the NETQUEUE data set. Respond P to shutdown the system.

394 ESP-5.4-MC-03

3354A Enter {C to continue, }F to format or P to shutdown Explanation: A Network Delivery Services (NDS) data set (NETQUEUE data set) problem

was detected that caused the system to be uncertain of what action to take regarding the data set. At least one message precedes this one explaining the problem.

System Action: The Cybermation system waits for a response. User Response: Respond to the action prompt.

If the response is C, and C was specified as a valid response in the action prompt, then the NETQUEUE data set is not reformatted, and processing continues. If the response is F, then the NETQUEUE data set is reformatted and processing continues. If the response is P, then the system is shutdown. If the response is invalid, message 3368E is issued and action prompt 3354A is re-issued.

3355S <dsname> not a valid NETQUEUE data set Explanation: A NETQUEUE <dsname> command in the LOADNET initialization file

specified an invalid Network Delivery Services (NDS) message queue data set. <dsname> specifies the name of the invalid Network Delivery Services (NDS) message queue data set.

System Action: The system shuts down. User Response: For an ESP/WM subsystem, correct the NETQUEUE <dsname> command in the

LOADNET initialization to specify a valid Network Delivery Services (NDS) message queue data set. Then restart ESP/WM.

3356I NETQUEUE data set <dsname> formatted Explanation: The Network Delivery Services (NDS) message queue data set was

formatted, either because the format was required or explicitly requested. <dsname> specifies the data set name of the Network Delivery Services (NDS) message queue data set.


3357E SPACE invalid with destination/service specification(s) Explanation: A NETWORK QUEUE DISPLAY command was issued specifying the SPACE

operand and at least one of the following incompatible operands: NETNODE, HOST, SYSPLEX, SYSNAME, XCFGROUP, XCFMEMBER, JESNODE, JESMEMBER, SYSID, SERVICE

System Action: The NETWORK QUEUE DISPLAY command is ignored. User Response: If required, re-enter the NETQUEUE DISPLAY command specifying either

the SPACE operand, or destination/service operand(s), but not both.

3358I NETQUEUE data set not defined|initialized Explanation: Response to NETWORK QUEUE DISPLAY command.

Messages and Codes

ESP-5.4-MC-03 395

System Action: Processing continues. User Response: None. Does not happen under ESP/WM.

3359E NETNODE mutually exclusive with destination criteria Explanation: Response to NETWORK QUEUE DISPLAY command. Both the NETNODE

operand and at least one of the following operands were specified: SYSPLEX, SYSNAME, XCFGROUP, XCFMEMBER, JESNODE, JESMEMBER, SYSID.

System Action: The NETWORK QUEUE DISPLAY command is ignored. User Response: If required, re-enter a NETWORK QUEUE DISPLAY command with compatible

operands.

3360E <service> service {not found|does not support message queuing} Explanation: A NETWORK QUEUE DISPLAY command specified the SERVICE(<service>)

operand. However, network (NDS) service <service> either does not exist or does not support message queueing.

System Action: Processing continues. User Response: If required, re-enter a NETWORK QUEUE DISPLAY command specifying a

network service that supports message queueing, or omitting the SERVICE(<service>) operand.

3361I No queued messages{ for {specified destination{ and }}{<service> service}}

Explanation: Response to NETWORK QUEUE DISPLAY command. <service> specifies a network (NDS) service name.


3362C NET QUEUE DISPLAY Explanation: Response to NETWORK QUEUE DISPLAY command. System Action: The requested Network Delivery Services (NDS) message queue(s) are

displayed. User Response: None.

3363C NET QUEUE FLUSH Explanation: Response to NETWORK QUEUE FLUSH IDENTIFIER(<id>) command.

<id> specifies the identifier of the Network Delivery Services (NDS) message queue to be flushed.

System Action: The requested Network Delivery Services (NDS) message queue is flushed.


3364E Network queue identifier <id> not found Explanation: Response to NETWORK QUEUE FLUSH IDENTIFIER(<id>) command.

<id> specifies the identifier of the Network Delivery Services (NDS) message queue to be flushed.

System Action: Processing continues. User Response: To display the existing Network Delivery Services (NDS) message

396 ESP-5.4-MC-03

queues, enter the command: NETWORK QUEUE DISPLAY or NET Q D Then if required, re-enter the NETWORK QUEUE FLUSH IDENTIFIER(<id>) command, specifying an existing Network Delivery Services (NDS) message queue identifier.

3365W NETQUEUE space shortage, Dsname=<dsname> Explanation: There is insufficient space in the Network Delivery Services (NDS)

message queue data set to satisfy a request for space on it. <dsname> specifies the name of the Network Delivery Services (NDS) message queue data set.

System Action: Action message prompt 3367A follows requesting that Network Delivery Services (NDS) message queue backlog(s) be cleared before an R command is entered to retry the Network Delivery Services (NDS) message queue data set space request.

User Response: Display Network Delivery Services (NDS) message queue backlogs with the following command: NETWORK QUEUE DISPLAY or NET Q D If a Network Delivery Services (NDS) message queue backlog exists for an obsolete network node, then it can be flushed with the following command: NETWORK QUEUE FLUSH IDENTIFIER(<id>) or NET Q FL ID(<id>) where - <id> specifies the identifier of the backlogged Network Delivery Services (NDS) message queue. Determine if a Network Delivery Services (NDS) connection to the network node (NETNODE) with the highest backlog exists, with the following command: NETWORK DISPLAY CONNECTIONS or NET D C If no Network Delivery Services (NDS) connection to the network node exists, then start one with the following command: NETWORK START CONNECTION HOST(<host_or_ip>) PORT(<port>) where - <host_or_ip> specifies the DNS host name or IP address of the network node. <port> specifies the TCP port number of the network node listener. If a Network Delivery Services (NDS) connection between the local and remote network nodes does exist, then check if the network service with the highest backlog is inactive on either the local and/or the remote network node by issuing the following command on both the local and the remote network nodes: NETWORK DISPLAY SERVICES or

Messages and Codes

ESP-5.4-MC-03 397

NET D S If the network service is inactive on either network node, then start it with the following command: NETWORK START SERVICE <service> or NET S S <service> where - <service> specifies the network service Then reply R to action message prompt 3367A. If Network Delivery Services (NDS) connections to all network nodes that have message queue backlogs exist, and all the message queuing network services are receiving on both the local network node and all remote network nodes, then the Network Delivery Services (NDS) message queue data set needs to be re-allocated with more space. Attempt to reply R to message action prompt 3367A until it is accepted. Then stop the job. If the reply to action message prompt 3376A is consistently rejected, then the job must be cancelled. Once the job is down, create a larger linear data set with an IDCAMS DEFINE command and copy the data from the old data set to the new with an IDCAMS REPRO command. It is highly recommended that the data set be created with secondary extents, as they will be used if the primary extent runs out of space. Once the new Network Delivery Services (NDS) message queue data set is created and the data copied into it, ensure that the NETQUEUE command (in the LOADNET initialization file for ESP/WM) specifies the new data set. Then restart the job.

3366I NETQUEUE data set <dsname> extended by <hex> bytes Explanation: In order to satisfy a request for Network Delivery Services (NDS)

message queue data set space, the system has to extend the data set by at least one secondary extent. <dsname> specifies the name of the Network Delivery Services (NDS) message queue data set. <hex> specifies the number of bytes in hexadecimal that the Network Delivery Services (NDS) message queue data set was extended by.

System Action: The system extends the Network Delivery Services (NDS) message queue data set by one or more secondary extents.


3367A Clear NETQUEUE backlog(s) and enter R to retry Explanation: There is insufficient space in the Network Delivery Services (NDS)

message queue data set to satisfy a request for space on it. This message is preceded by message 3365W indicating the NETQUEUE space shortage.

System Action: Display Network Delivery Services (NDS) message queue backlogs with the following command: NETWORK QUEUE DISPLAY or NET Q D

398 ESP-5.4-MC-03

If a Network Delivery Services (NDS) message queue backlog exists for an obsolete network node, then it can be flushed with the following command: NETWORK QUEUE FLUSH IDENTIFIER(<id>) or NET Q FL ID(<id>) where - <id> specifies the identifier of the backlogged Network Delivery Services (NDS) message queue. Determine if a Network Delivery Services (NDS) connection to the network node (NETNODE) with the highest backlog exists, with the following command: NETWORK DISPLAY CONNECTIONS or NET D C If no Network Delivery Services (NDS) connection to the network node exists, then start one with the following command: NETWORK START CONNECTION HOST(<host_or_ip>) PORT(<port>) where - <host_or_ip> specifies the DNS host name or IP address of the network node. <port> specifies the TCP port number of the network node listener. If a Network Delivery Services (NDS) connection between the local and remote network nodes does exist, then check if the network service with the highest backlog is inactive on either the local and/or the remote network node by issuing the following command on both the local and the remote network nodes: NETWORK DISPLAY SERVICES or NET D S If the network service is inactive on either network node, then start it with the following command: NETWORK START SERVICE <service> or NET S S <service> where - <service> specifies the network service Then reply R to action message prompt 3367A. If Network Delivery Services (NDS) connections to all network nodes that have message queue backlogs exist, and all the message queuing network services are receiving on both the local network node and all remote network nodes, then the Network Delivery Services (NDS) message queue data set needs to be re-allocated with more space. Attempt to reply R to message action prompt 3367A until it is accepted. Then stop the job. If the reply to action message prompt 3376A is consistently rejected, then the job must be cancelled. Once the job is down, create a larger linear data set with an IDCAMS DEFINE command and copy the data from the old data set to the new with an IDCAMS REPRO command. It is highly recommended that the data set be created with secondary

Messages and Codes

ESP-5.4-MC-03 399

extents, as they will be used if the primary extent runs out of space. Once the new Network Delivery Services (NDS) message queue data set is created and the data copied into it, ensure that the NETQUEUE command (in the LOADNET initialization file for ESP/WM) specifies the new data set. Then restart the job.

3368S NETQUEUE space shortage, unable to issue clear backlog prompt, terminating

Explanation: There is insufficient space in the Network Delivery Services (NDS) message queue data set to satisfy a request for space on it. The system was unable to issue action message prompt 3367A to request an attempt to alleviate the problem and to retry the message queue data set space request.

System Action: The system terminates. User Response: If the Network Delivery Services (NDS) message queue data set space

shortage is a temporary condition due to message backlog(s), then restart the system. If the above persists, then contact Cybermation support. If the Network Delivery Services (NDS) message queue data space shortage is chronic, then a larger linear data set should be created with an IDCAMS DEFINE command and the data copied from the old data set to the new with an IDCAMS REPRO command. It is highly recommended that the data set be created with secondary extents, as they will be used if the primary extent runs out of space. With ESP/WM, once the new Network Delivery Services (NDS) message data set is created, ensure the NETQUEUE <dsname> command in the LOADNET initialization file specifies the newly created data set. Then restart ESP/WM.

3369E Invalid NETQUEUE file action response Explanation: This message follows action message prompt 3354A or 3368A.

An invalid reply to the prompt has been entered. System Action: The action message prompt is re-issued. User Response: Enter a valid reponse as specified in the action message prompt.

3370S Network lock requested while NETQUEUE lock held Explanation: Internal logic error. Should never happen. System Action: The system terminates abnormally with code U2920. User Response: Contact Cybermation support.

3371E Network Delivery Services not available Explanation: A Network Delivery Service (NDS) request was issued.

However, Network Delivery Services (NDS) has not been activated. System Action: The Network Delivery Service (NDS) request is ignored. User Response: Should never happen. Contact Cybermation support.

400 ESP-5.4-MC-03

3372W xNetwork <function>, <description> Explanation: An internal Network Delivery Services (NDS) internal API request has

been issued. An existing condition prevented the request from being serviced. <function> specifies the internal API function. <description> describes the condition that prevented the Network Delivery Services (NDS) API request from being serviced.

System Action: The Network Delivery Services (NDS) API request is not processed. User Response: If the condition that prevented the Network Delivery Services (NDS)

API request from being serviced is normal, probably no action is required. If not, then correct it.

3373E xNetwork <function>, <description> Explanation: An internal Network Delivery Services (NDS) API request has resulted

in an error condition. <function> specifies the internal API function. <description> describes the error condition.

System Action: The Network Delivery Services (NDS) API request is not processed. User Response: Attempt to diagnose the problem from the error description and correct


3374S xNetwork <function>, <error_description> Explanation: An internal Network Delivery Services (NDS) API request has resulted

in a severe error condition. <function> specifies the internal API function. <description> describes the error condition.

System Action: The Network Delivery Services (NDS) API request is not processed. User Response: Attempt to diagnose the problem from the error description and correct


3400E DB_Mon xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


3401E DB_Mon xxxx in Appl yyyy, missing Data Source Name Explanation: Each DB_Mon requires a Data Source Name to be specified indicating

what work is to be done by the agent. This job does not have one. System Action: The job is not processed. User Response: Add the missing information to the job in the ESP procedure.

3402E DB_Mon xxxx in Appl yyyy, missing QUERY Statement Explanation: Each DB_Mon requires a QUERY Statement to be specified indicating


Messages and Codes

ESP-5.4-MC-03 401




the job.









3406E Unable to find password matching xxxx, yyyy, zzzz, nnnn, RC=n Explanation: A user ID was specified which required a password. ESP was unable

to find a password entry which matched user xxxx, workload object type yyyy, agent name zzzz and data source name nnnn.


PASSWORD command. Then resubmit the job.

3407E QUERY too long Explanation: The length of the QUERY exceeds the maximum of 4078 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the QUERY.

3408E Destination too long, maximum length nn Explanation: Destination is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of Destination.

402 ESP-5.4-MC-03





3411E FTP_JOB xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


3412E FTP_JOB xxxx in Appl yyyy, missing Server Address Explanation: Each FTP_JOB requires a Server Address to be specified indicating


3413E FTP_JOB xxxx in Appl yyyy, missing Remote File Name Explanation: Each FTP_JOB requires a Remote File Name to be specified indicating




3415E FTP_JOB xxxx in Appl yyyy, missing Transfer Code Type Explanation: Each FTP_JOB requires a Transfer Code Type to be specified indicating


Messages and Codes

ESP-5.4-MC-03 403

3416E FTP_JOB xxxx in Appl yyyy, missing Transfer Direction Explanation: Each FTP_JOB requires a Transfer Direction to be specified indicating


3417E FTP_JOB xxxx in Appl yyyy, Transfer Direction DOWNLOAD specified with Type U

Explanation: This combination of parameters is not allowed. System Action: The job is not processed. User Response: Correct the Transfer Direction in the ESP procedure.




the job.









3421E Server Address too long, maximum length nn Explanation: Server Address is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of Server Address.

404 ESP-5.4-MC-03

3422E Remote File Name too long, maximum length nn Explanation: Remote File Name is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of Remote File Name.

3423E Local File Name too long, maximum length nn Explanation: Local File Name is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of Local File Name.

3424E IP_Mon xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


3425E IP_Mon xxxx in Appl yyyy, missing TCP/IP Device Address Explanation: Each IP_Mon requires a TCP/IP Device Address to be specified indicating


3426E IP_Mon xxxx in Appl yyyy, missing Status Explanation: Each IP_Mon requires a Status to be specified indicating





the job.





Messages and Codes

ESP-5.4-MC-03 405





3430E TCP/IP Device Address too long, maximum length nn Explanation: TCP/IP Device Address is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of TCP/IP Device Address.

3431E MISSING required Status Explanation: There was no Status specified. System Action: The job is not processed. User Response: Add the missing information to the job in the ESP procedure.

3432E MISSING Mode Explanation: There was no Mode specified. System Action: The job is not processed. User Response: Add the missing information to the job in the ESP procedure.



3434E EVENTLOG_Mon xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


3435E EVENTLOG_Mon xxxx in Appl yyyy, missing Log Name Explanation: Each EVENTLOG_Mon requires a Log Name to be specified indicating


406 ESP-5.4-MC-03




the job.









3439E EventCategory too long Explanation: The length of the EventCategory exceeds the maximum of 4078 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the EventCategory.

3440E EventDescription too long Explanation: The length of the EventDescription exceeds the maximum

of 4078 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the EventDescription.

3441E LogName too long, maximum length nn Explanation: LogName is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of LogName.

3442E EventSource too long, maximum length nn Explanation: EventSource is longer than the maximum nn allowed for

Messages and Codes

ESP-5.4-MC-03 407

the workload object type. System Action: Application generation fails. User Response: Reduce the length of EventSource.

3443E EventComputer too long, maximum length nn Explanation: EventComputer is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of EventComputer.

3444E MISSING Event ID Explanation: There was no Event ID specified. System Action: The job is not processed. User Response: Add the missing information to the job in the ESP procedure.



3446E PROCESS_Mon xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


3447E PROCESS_Mon xxxx in Appl yyyy, missing Process Name Explanation: Each PROCESS_Mon requires a Process Name to be specified indicating


3448E PROCESS_Mon xxxx in Appl yyyy, missing Status Explanation: Each PROCESS_Mon requires a Status to be specified indicating





the job.

408 ESP-5.4-MC-03









3452E Process Name too long, maximum length nn Explanation: Process Name is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of Process Name.





3456E SERVICE_Mon xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status

Messages and Codes

ESP-5.4-MC-03 409


3457E SERVICE_Mon xxxx in Appl yyyy, missing Service Name Explanation: Each SERVICE_Mon requires a Service Name to be specified indicating


3458E SERVICE_Mon xxxx in Appl yyyy, missing Status Explanation: Each SERVICE_Mon requires a Status to be specified indicating





the job.









3462E Service Name too long, maximum length nn Explanation: Service Name is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of Service Name.

410 ESP-5.4-MC-03





3466E TEXT_Mon xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


3467E TEXT_Mon xxxx in Appl yyyy, missing Text File Explanation: Each TEXT_Mon requires a Text File to be specified indicating


3468E TEXT_Mon xxxx in Appl yyyy, missing Text String Explanation: Each TEXT_Mon requires a Text String to be specified indicating


3469E TEXT_Mon xxxx in Appl yyyy, missing search boundary type Explanation: Each TEXT_Mon requires a search boundary type to be specified

indicating what work is to be done by the agent. This job does not have one.

System Action: The job is not processed. User Response: Add the missing information to the job in the ESP procedure.



Messages and Codes

ESP-5.4-MC-03 411


the job.









3473E Text String too long Explanation: The length of the Text String exceeds the maximum

of 1022 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the Text string.

3474E Textfile too long, maximum length nn Explanation: Textfile is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of Textfile.

3475E TimeFormat too long, maximum length nn Explanation: TimeFormat is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of TimeFormat.



412 ESP-5.4-MC-03

3477E FROM too long, maximum length nn Explanation: FROM is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of FROM.

3478E TO too long, maximum length nn Explanation: TO is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of TO.



3480E CPU_Mon xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


3481E CPU_Mon xxxx in Appl yyyy, both FROM and TO parameters are missing Explanation: Both FROM and TO parameters are missing in CONTINUOUS mode. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Provide FROM and/or TO parameter. Then resubmit the job.

3482E CPU_Mon xxxx in Appl yyyy, parameter FROM higher than parameter TO Explanation: Parameter FROM is higher than parameter TO. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Correct FROM and/or TO parameters. Then resubmit the job.




the job.

Messages and Codes

ESP-5.4-MC-03 413











3487E DISK_Mon xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


3488E DISK_Mon xxxx in Appl yyyy, missing Drive name Explanation: There was no Drive name to identify a logical partition to monitor. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Provide the Drive name. Then resubmit the job.

3489E DISK_Mon xxxx in Appl yyyy, both FROM and TO parameters are missing Explanation: Both FROM and TO parameters are missing in CONTINUOUS mode. System Action: The execution of the object fails, and a "submit error" status


414 ESP-5.4-MC-03

3490E DISK_Mon xxxx in Appl yyyy, parameter FROM higher than parameter TO Explanation: Parameter FROM is higher than parameter TO. System Action: The execution of the object fails, and a "submit error" status


3491E DISK_Mon xxxx in Appl yyyy, invalid parameter FROM Explanation: Parameter FROM higher than 100 and Format type is PERCENT. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Correct parameter FROM. Then resubmit the job.

3492E DISK_Mon xxxx in Appl yyyy, invalid parameter TO Explanation: Parameter TO higher than 100 and Format type is PERCENT. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Correct parameter TO. Then resubmit the job.

3493E DISK_Mon xxxx in Appl yyyy, invalid parameter NoChange Explanation: Parameter NoChange higher than 100 and Format type is PERCENT. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Correct parameter NoChange. Then resubmit the job.




the job.







Messages and Codes

ESP-5.4-MC-03 415



3497E Drive too long, maximum length nn Explanation: Drive name is longer than the maximum nn. System Action: Application generation fails. User Response: Reduce the length of Drive.

3498E Invalid Operator Explanation: EventID Operator code is not EQ, LT, LE, GT or GE System Action: Application generation fails. User Response: Correct the Operator in EventID statement.

3499E TEXT_Mon xxxx in Appl yyyy, both FROM and TO parameters are missing Explanation: Both FROM and TO parameters are missing. System Action: The execution of the object fails, and a "submit error" status


3500E TEXT_Mon xxxx in Appl yyyy, missing Time Format Explanation: Each TEXT_Mon requires a Time Format to be specified if the search

boundary type is DATETIME. This job does not have one. System Action: The job is not processed. User Response: Add the missing information to the job in the ESP procedure.

3501E TEXT_Mon xxxx in Appl yyyy, non-numeric FROM parameter Explanation: Each TEXT_Mon requires FROM parameter to be numeric if the search

boundary type is LINE. System Action: The job is not processed. User Response: Correct the FROM parameter.

3502E TEXT_Mon xxxx in Appl yyyy, non-numeric TO parameter Explanation: Each TEXT_Mon requires TO parameter to be numeric if the search

boundary type is LINE. System Action: The job is not processed. User Response: Correct the TO parameter.

3503E TEXT_Mon xxxx in Appl yyyy, parameter FROM higher than parameter TO Explanation: Parameter FROM is higher than parameter TO. System Action: The execution of the object fails, and a "submit error" status


3504E No CKPT space to trigger event xxxx.yyyy specified by AMNOTIFY stmt for object xxxxx.

Explanation: Agent Monitor WOB was unable to obtain enough checkpoint space to

416 ESP-5.4-MC-03

trigger an event specified in AMNOTIFY statement. System Action: The trigger is not processed. User Response: The checkpoint space situation should be monitored.

3505E Alert ID and Event ID are mutually exclusive. Explanation: AMNOTIFY statement for an Agent Monitor WOB specified both an ALERT and

and EVENT parameters. System Action: Processing of the ESP procedure stops. User Response: Correct the statement to use either an ALERT or EVENT parameter.

3506E Both Alert ID and Event ID defined for Agent Monitor object xxxx. Explanation: ESP detected that both Alert ID and Event ID were defined for the same

Agent Monitor object by more than one AMNOTIFY statement. It is possible that one of the AMNOTIFY statements was placed outside of the WOB definition in the ESP proc.

System Action: Processing of the ESP procedure stops. User Response: Correct your ESP proc to use either an ALERT or EVENT parameter per

single Agent Monitor WOB.

3507I xxxx STATE yyyyyyyy. Explanation: Agent Monitor object xxxx has changed the state to yyyyyyyy. System Action: Processing continues. User Response: None.



System Action: Processing ends for this request. User Response: Define a password to match the parameters above using the ESP


3509E User uuuuuuuu, Unathorized access to event xxxx.yyyy in AMNOTIFY stmt for object xxxxx.

Explanation: Agent Monitor WOB was unable to trigger an event specified by AMNOTIFY statement. Either the event prefix specification (normally equivalent to a security user ID) xxxx is defined in the User Profile Definition Table, or the user ID uuuuuuuu is not authorized by SAF to perform this action.

System Action: The trigger is not processed. User Response: Notify your installation security administrator.

3881E Action not supported. Explanation: The action specified in the EVENT statement of the SAPE_JOB WOB

definition is not supported. Currently supported actions are REGISTEREVENT and TRIGGER.

System Action: Processing of the ESP procedure stops. User Response: Specify either REGISTEREVENT or TRIGGER action keyword.

Messages and Codes

ESP-5.4-MC-03 417




User Response: Define a password to match the parameters above using the ESP PASSWORD command. Then retry the operation.

3883E Unable to find password matching xxxx, yyyy, zzzz, RC=n Explanation: A user ID was specified which required a password. ESP was unable
















418 ESP-5.4-MC-03




the job.

3888E SAPE_JOB xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status results. User Response: Provide the Agent name. Then resubmit the job.


SAPE_Job jjjj in application aaaa. System Action: The application is not built. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


3890W Agent wwww is not defined or you are not authorized to use it Explanation: The agent named wwww was not defined or you were not authorized to

use it when a RESDEF command was entered. System Action: Agent monitoring is ignored for this Agent. User Response: Either correct the Agent name, or define the Agent, and resubmit

the RESDEF command.


Explanation: The application manager was processing a new generation of an application with JOB_ANCESTOR_WAIT. However, the APPLFILE record for the new generation was invalid, or did not correspond to an ESP internal control block.

System Action: The new generation of the application will remain in ancestor wait status.

User Response: Try to unwait the generation nn of the application xxxx. Notify Cybermation support.


Explanation: An I/O error occurred reading an APPLFILE record for a new generation of an application with JOB_ANCESTOR_WAIT. The error is described in a preceding message.

System Action: The new generation of the application will remain in ancestor wait status.

Messages and Codes

ESP-5.4-MC-03 419

User Response: Try to unwait the generation nn of the application xxxx. Notify Cybermation support.


use it when agent monitoring was being initialized after a LOADAGDF command was entered.

System Action: Agent monitoring is ignored for this Agent. User Response: Either correct the Agent name, or define the Agent, and resubmit

the LOADAGDF command.


use it when a CPU command was entered. System Action: Agent monitoring is ignored for this Agent. User Response: Either correct the Agent name, or define the Agent, and resubmit

the CPU command.

3895W Agent wwww not found for job yyyy Explanation: The job yyyy has the Agent wwww with NOROUTING parameter (default)

specified (Agent affinity). This Agent is not defined in the system topology.

System Action: Resource request fails. User Response: Update the system topology if needed.

3896E Real resource must be defined as LOCAL. Resource xxxx rejected. Explanation: A RESDEF ADD command for a real resource with the scope parameter

specified as GLOBAL or ENTERPRISE was issued. System Action: The resource is not added. Any other parameters on the command

are ignored. User Response: Re-enter the command with scope LOCAL.

3897E WLM resource type XXXXXXXX is not supported Explanation: A RESDEF ADD or RESDEF SET command with parameter WLM was issued.

The type of WLM resource specified in parentheses is not currently supported.

System Action: The resource is not added/updated. Any other parameters on the command are ignored.

User Response: Please refer to Reference Guide for currently supported types of the WLM resource.

3898E The type of real resource cannot be changed with SET.

Resource xxxx is not updated. Explanation: A RESDEF SET command specifying a real resource was issued.

ESP detected that resource xxxx was defined with different type of a real resource.

System Action: The resource is not updated. Any other parameters on the command

420 ESP-5.4-MC-03

are ignored. User Response: To change the type of a real resource delete the resource with

RESDEF DELETE and then create it once again with RESDEF ADD, specifying the required type of a real resource.

3899E WLM cannot be changed with SET. Resource xxxx is in use Explanation: A RESDEF SET command specifying a real resource was issued.

ESP found job(s) waiting for this resource. System Action: The resource was not updated. User Response: Wait until no jobs are waiting for this resource, and then update it.

3900W Parameter error on EXEC card Explanation: A syntax error was encountered in the Communication Server EXEC card

parameter string. The syntax of one or more of the parameters is incorrect or one or more of the parameters is not supported.

System Action: Message 3906 follows, indicating the incorrect parameter. Message 3907, which prompts for new parameters, follows.

User Response: Reply to message 3907 which follows. Correct the parameter on the Communication Server EXEC card.

3901W Parameter error on START command Explanation: A syntax error was encountered in the Communication Server START

command parameter string. The syntax of one or more of the parameters is incorrect or one or more of the parameters is not supported.


User Response: Reply to message 3907 which follows. Correct the parameter on the Communication Server START command.

3902E Error occurred during command parameter scan Explanation: An error occurred during the scan of parameters on the EXEC card or

the START command. This is probably due to an internal logic error. System Action: Communication Server processing terminates. User Response: Notify your software support personnel. Note preceding messages which

identify the failing parameter.

3903W Parameter error on the following statement from xxxx file Explanation: An error occurred during the scan of parameters on the initialization

parameter file "xxxx". This is probably due to an internal logic error.


User Response: Reply to message 3907 which follows. Correct the parameter in the initialization file "xxxx".

3904W Following statement from xxxx has an invalid syntax Explanation: A syntax error was encountered in an initialization parameter statement

in the "xxxx" initialization parameter file. The syntax of one or more of the parameters is incorrect.

Messages and Codes

ESP-5.4-MC-03 421



3905W Following statement from xxxx has an undefined parameter Explanation: A syntax error was encountered in an initialization parameter statement

in the "xxxx" initialization parameter file. The syntax of one or more of the parameters is not supported. Typically, a spelling error occurred in one of the initialization parameters.



3906W xxxx Explanation: This message follows an parameter error on the EXEC card, START command

or initialization file. The parameter containing the error is being displayed.

System Action: Message 3907, which prompts for new parameters, follows. User Response: Reply to message 3907 which follows. Correct the parameter on the

Communication Server EXEC card, START command or initialization file.

3907A Reenter entire statement, 'CANCEL' or 'END' Explanation: Communication Server is prompting for an initialization parameter.

This message follows an parameter error on the EXEC card, START command or initialization file. It is preceded by message 3906 indicating the parameter in error.

System Action: Communication Server waits for a response. If "CANCEL" is specified, Communication Server terminates. If "END" is specified, Communication Server ignores the incorrect parameter statement.

User Response: Enter the correct initialization parameters. Correct the initialization parameters on the EXEC card, START command or initialization file.

3908A Enter initialization parameter or 'END' Explanation: In response to the PROMPT parameter on the EXEC card or START command,

the Communication Server is prompting the operator to enter an initialization parameter from the console.

System Action: The Communication Server waits for a response. Once received, it processes the response.

User Response: Enter an initialization parameter. All parameters which can be specified in the CMSPARM data set may be specified as a response. When all initialization parameters have been defined, enter "END" to terminate the prompt and continue with normal processing.

3909I COMMSERV log dataset xxxx has been extended Explanation: In response to a DUMPLOG command, the Communication Server log data

set "xxxx" was re-opened in extend mode.

422 ESP-5.4-MC-03

System Action: The Communication Server log data et is opened in extend mode. Log messages written previous to the DUMPLOG command are available for viewing. New log messages will be added after the current messages.

User Response: Take maintenance action for the Communication Server log data set based on the type of x37 abend which occurred.

3910E xxxx Explanation: An I/O error was encountered reading the initialization parameter

data set. This could include a file not allocated condition or an actual I/O error. The text of the message fully describes the error.

System Action: Communication Server processing is terminated. User Response: Correct the problem and restart the Communication Server.

3911I COMMSERV log dataset xxxx has been overwritten Explanation: While attempting to write a message to the Communication Server log

data set "xxxx", an x37 type abend occurred. The Communication Server log data set was overwritten because it could not be extended.

System Action: The Communication Server log data set is open as new rather than extended. Existing information in the log data set will be overwritten.

User Response: Take maintenance action for the Communication Server log data set based on the type of x37 abend which occurred.

3912E Error opening COMMSERV log dataset Explanation: Communication Server could not open the log data set. This may occur

during initialization or after an x37 type abend occurred. A message(s) is issued preceding this message which describes the error.

System Action: The Communication Server log data set processing is suspended. User Response: Take maintenance action for the Communication Server log data set

based on the type of x37 abend which occurred and/or the message which preceded this message.

3913I Cybermation COMMSERV Release xxxx initialization complete Explanation: The Communication Server Release "xxxx" has completed initialization

and is ready to accept work. System Action: None. User Response: None.

3916E Unable to close COMMSERV log dataset Explanation: Communication Server received a "DUMPLOG" command from the console

command processor. The Communication Server was unable to close the log data set. A message(s) describing the error precedes this message.

System Action: The command is ignored. The Communication Server log data set processing is no longer available.

User Response: Notify your software support personnel. Make note of the message preceding this message.

Messages and Codes

ESP-5.4-MC-03 423

3917S COMMSERV xxxx error processing has completed Explanation: An abend occurred during Communication Server processing. "xxxx" is the

SYSID of abended Communication Server. System Action: Communication Server is terminated. User Response: Notify your system support personnel.

3918C COMMSERV Status Explanation: The operator entered a "STATUS" command with no operands. If the

current STATUS setting is "ON", various statistics regarding the Communication Server are displayed.


3919I xxxx command accepted Explanation: An "xxxx" command was entered by the operator. The command has been

accepted and will be scheduled for execution. System Action: The command is scheduled for execution. User Response: None.

3920I SRETRACE is set to {ON|OFF} Explanation: The operator entered a "SRETRACE" command with the ON|OFF keyword

specified. The currently SRETRACE setting is displayed. System Action: None. User Response: None.

3921I Cybermation COMMSERV xxxx has terminated Explanation: Communication Server has terminated in response to an internal or

external request to terminate processing. System Action: None. User Response: None.

3922E Error returning transaction, RC=nn Explanation: A multi-transaction Communication Server encountered an error while

attempting to return from processing the previous transaction. The return code from attempting to obtain a transaction was "nn".

System Action: Communication Server is terminated. User Response: Notify your system support personnel. Make note of the return code.

3923S Error obtaining a command, RC=nn Explanation: The Communication Server console command processor encountered an error

during processing. The return code from command processing is "nn". System Action: This message is followed by message 2324. User Response: See message 2324.

3924S Command processing terminated Explanation: The Communication Server console command processor encountered a

severe error while processing a command. The severe error has caused

424 ESP-5.4-MC-03

console command processing to terminate. System Action: Communication Server processing continues with the operator

communication facility disabled. User Response: Notify your software support personnel. Use the MVS "STOP" command

to terminate Communication Server. The MVS "MODIFY" interface will not work.

3925W Invalid command, xxxx Explanation: Communication Server received an unknown command "xxxx" from the

operator console. System Action: The command is ignored. User Response: Reenter the correct command.

3926W Invalid command name syntax Explanation: Communication Server received a command from the operator console which

did not conform to the syntax for command names. System Action: The command is ignored. User Response: Reenter the correct command.

3927S Explanation:

An abend occurred during multi-transaction Communication Server processing. "xxxx" is the SYSID of abended Communication Server.

System Action: Communication Server is terminated. User Response: Notify your system support personnel.

3928S Error attaching xxxx, RC=nn Explanation: An error occurred while attempting to attach a module for the specified

function "xxxx". The return code from the attach is "nn". This is an internal logic error.

System Action: Communication Server is terminated. User Response: Notify your software support personnel.

3929E Data exchange TP not currently supported Explanation: A Communication Server type of "DATAXCHANGE" was specified on the

SERVTYPE initialization parameter. The DATAXCHANGE transaction type is not currently supported.

System Action: Transactions to the Communication Server are ignored. User Response: Alter the initialization parameters to specify a different server type.

3931E Error scanning command, RC=nn Explanation: An error occurred while scanning a Communication Server command.

This is probably an internal logic error. System Action: The command is not processed. User Response: If the problem persists, notify your software support personnel.

3932I Trace buffer limit set to nn Explanation: The operator entered an "XBTRACE" command to set the number of cross

Messages and Codes

ESP-5.4-MC-03 425

system buffers to be traced. The number of cross system buffers being traced is displayed.


3933W Error occurred in Standard transaction program Explanation: A multi-transaction Communication Server encountered an error in

standard transaction processing. This message is preceded by a message(s) from standard transaction processing.

System Action: None. User Response: Notify your software support personnel.

3934I STATUS is set to {ON|OFF} Explanation: The operator entered a "STATUS" command with the ON|OFF keyword

specified. The currently STATUS setting is displayed. System Action: None. User Response: None.

3935I Multi transaction shell terminating due to timeout Explanation: A multi-transaction Communication Server has not received a request

within a system determined time. Communication Server is terminating. This is part of normal Communication Server processing.

System Action: Communication Server will terminate. User Response: None.

3936E Error obtaining transaction, RC=nn Explanation: A multi-transaction Communication Server encountered an error while

attempting to obtain a tranasaction. The return code from attempting to obtain a transaction was "nn".

System Action: Communication Server is terminated. User Response: Notify your system support personnel. Make note of the return code.

4001I INPUT VALUE = xxxx Explanation: A request was made to the Event Data Set Record maintenance utility to

replace a field value 'xxxx' with another value. System Action: None. This message is followed by message 4002I. User Response: None.

4002I OUTPUT VALUE = xxxx Explanation: A request was made to the Event Data Set Record maintenance utility to

replace a field value with value 'xxxx'. System Action: None. This message is preceded by message 40012I. User Response: None.

4003I EVENT xxxx HAS BEEN UPDATED Explanation: Event 'xxxx' was updated by the Event Data Set Record maintenance

utility as a result of a REPLACE statement. System Action: None.

426 ESP-5.4-MC-03


4004I EVENT DB SCAN COMPLETE Explanation: The Event Data Set Record maintenance utility has successfully

completed processing. System Action: None. User Response: None.

4005E VSAM OPEN ERROR: RC = xxxx EC = yyyy Explanation: The Event Data Set Record maintenance utility encountered an error

when trying to open the Event database data set. 'xxxx' is the VSAM return code. 'yyyy' is the VSAM error code.

System Action: The processing for the current statement is terminated. User Response: Determine the cause of the error from the VSAM Programmer's Guide.

4006E VSAM POINT ERROR - ERROR CODE = xxxx Explanation: The Event Data Set Record maintenance utility encountered an error

when trying to point to the next Event record. 'xxxx' is the VSAM return code.


4007E VSAM PUT ERROR - ERROR CODE = xxxx Explanation: The Event Data Set Record maintenance utility encountered an error

when trying to write an Event record. 'xxxx' is the VSAM return code.


4008E FIELD NAME xxxx IS INVALID Explanation: A request was made to the Event Data Set Record maintenance utility to

operate on a field name 'xxxx'. Field name 'xxxx' is not supported. System Action: The processing for the current statement is terminated. User Response: Correct the field name.

4009E THE INPUT VALUE IS IDENTICAL TO THE REPLACEMENT VALUE Explanation: A request was made to the Event Data Set Record maintenance utility to

replace an input field value with an output field value. The input and output field values are identical.

System Action: The processing for the current statement is terminated. This message is preceded by messages 4001I and 4002I.

User Response: Ensure the input and output values are different.

4010E BOTH A MATCH VALUE AND A REPLACEMENT VALUE MUST BE SPECIFIED

Explanation: A request was made to the Event Data Set Record maintenance utility to replace an input field value with an output field value. One or both of the input (match) and output (replacement) field values is missing.

Messages and Codes

ESP-5.4-MC-03 427

System Action: The processing for the current statement is terminated. User Response: Ensure both the input and output values are specified.

4011E SYNTAX ERROR IN COMMAND STATEMENT Explanation: A syntax error existed in a statement supplied to the Event Data Set

Record maintenance utility. System Action: The processing for the current statement is terminated. User Response: Correct the syntax error.

4012E VSAM READ UNSUCCESSFUL - ERROR CODE = xxxx Explanation: The Event Data Set Record maintenance utility encountered an error

when trying to read an Event record. 'xxxx' is the VSAM return code. System Action: The processing for the current statement is terminated. User Response: Determine the cause of the error from the VSAM Programmer's Guide.

4020W APPLFILE OR TRAKFILE KEYWORD OMITTED, COMMAND IGNORED

Explanation: An statement was issued to the Tracking/Application file slot reclaim maintenance utility. One of the keywords APPLFILE or TRAKFILE were required but not specified.

System Action: The processing for the current statement is terminated. User Response: Specify one of the required keywords.

4021E NO APPL RECORDS FOUND IN JOBINDEX Explanation: A statement was issued to the Tracking/Application file slot reclaim

maintenance utility. No APPL records were found in the specified JOBINDEX data set.

System Action: The processing for the current statement is terminated. User Response: None.

4022E NO JOB ENTRIES FOUND IN JOBINDEX Explanation: A statement was issued to the Tracking/Application file slot reclaim

maintenance utility. No JOB records were found in the specified JOBINDEX data set.

System Action: The processing for the current statement is terminated. User Response: None.

4030W No function requested, command ignored Explanation: The JOBINDEX file cleanup utility (CYBESUT7) was invoked

without a valid function being specified. System Action: The request is ignored. User Response: Reissue the request, specifying a valid function (ANALYZE

or UPDATE).

4039W Neither APPL nor TRAK requested, command ignored Explanation: The JOBINDEX file cleanup utility (CYBESUT7) was invoked

without requesting processing of either Application or Job Tracking records

428 ESP-5.4-MC-03

System Action: The request is ignored. User Response: Reissue the request, specifying at least one of the APPL

or TRAK operands.


OA_Job jjjj in application aaaa. System Action: The application is not built. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


4041E OA_Job xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status





the job.





4044E OA_Job xxxx in Appl yyyy, Oracle Application Name missing Explanation: Both ApplShortName and ApplDisplName statements are missing. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Provide ApplShortName or ApplDisplName statement.

Then resubmit the job.

4045E OA_Job xxxx in Appl yyyy, both Oracle Application Names defined Explanation: Both ApplShortName and ApplDisplName statements are defined. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Remove either ApplShortName or ApplDisplName statement.

Messages and Codes

ESP-5.4-MC-03 429


4046E OA_Job xxxx in Appl yyyy, neither Program nor Request Set Name defined Explanation: Both Program and RequestSet statements are missing. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Provide Program or RequestSet statement.


4047E OA_Job xxxx in Appl yyyy, both Program and Request Set Names defined Explanation: Both Program and RequestSet statements are defined. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Remove Program or RequestSet statement.


4048E OA_Job xxxx in Appl yyyy, Description invalid for Request Set Explanation: Desc (Description) statement is invalid for Request Set. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Correct invalid combination of statements.


4049E OA_Job xxxx in Appl yyyy, missing ProgramData statement Explanation: ProgramData statements are missing for Request Set. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Provide ProgramData statement(s).


4050E OA_Job xxxx in Appl yyyy, Args statement invalid for Request Set Explanation: Args statement is invalid for Request Set. System Action: The execution of the object fails, and a "submit error" status



4051E OA_Job xxxx in Appl yyyy, ProgramData statement invalid for Program Explanation: ProgramData statement is invalid for Program. System Action: The execution of the object fails, and a "submit error" status



4052E OA_Job xxxx in Appl yyyy, ProgArgs statement invalid for Program Explanation: ProgArgs statement is invalid for Program. System Action: The execution of the object fails, and a "submit error" status

results.

430 ESP-5.4-MC-03

User Response: Correct invalid combination of statements. Then resubmit the job.

4053E OA_Job xxxx in Appl yyyy, ProgPrinter statement invalid for Program Explanation: ProgPrinter statement is invalid for Program. System Action: The execution of the object fails, and a "submit error" status



4054E OA_Job xxxx in Appl yyyy, ProgPrintStyle statement invalid for Program Explanation: ProgPrintStyle statement is invalid for Program. System Action: The execution of the object fails, and a "submit error" status



4055E OA_Job xxxx in Appl yyyy, ProgPrintCopies statement invalid for Program Explanation: ProgPrintCopies statement is invalid for Program. System Action: The execution of the object fails, and a "submit error" status



4056E OA_Job xxxx in Appl yyyy, ProgSaveOutput statement invalid for Program Explanation: ProgSaveOutput statement is invalid for Program. System Action: The execution of the object fails, and a "submit error" status



4057E User xxxx denied access to User ID yyyy Explanation: User xxxx is not authorized to submit jobs to this agent using

user ID yyyy. "xxxx" is the user id under which the event executes for this job, normally the event prefix, but it may be a triggering user, or may be overridden by an installation EVENTSAF exit.

System Action: The job enters the SUBERROR state. User Response: In order to submit jobs to this agent using ID yyyy, user xxxx

must have read access to SAF profile AGENTUSR.yyyy.agentname. Once this has been established, resubmit the job.




Messages and Codes

ESP-5.4-MC-03 431


4059E Invalid Program Number Explanation: The number in ProgramData statement in not higher than the

current number. System Action: The event fails. The object is not generated. User Response: Correct ProgramData statement.

4060E ARGS too long Explanation: The length of the ARGS exceeds the maximum of 4070 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the ARGS.

4061E Invalid Args specification Explanation: More than 100 Args statements have been defined. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Reduce the number of the ARGS statements. Then resubmit the job.

4062E PROGARGS too long Explanation: The length of the PROGARGS exceeds the maximum of 4070 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the PROGARGS.

4063E Invalid ProgArgs specification Explanation: More than 100 ProgArgs statements have been defined. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Reduce the number of the PROGARGS statements. Then resubmit the job.

4101E FTP_JOB xxxx in Appl yyyy, missing Local File Name Explanation: Each FTP_JOB requires a Local File Name to be specified indicating





the job.

4103E Invalid ENVAR specification Explanation: A syntactical error was found scanning the ENVAR statement to

extract the names and values of the variables

432 ESP-5.4-MC-03


User Response: Correct the syntax of the ENVAR statement. Then resubmit the job.

4104E ???_Job xxxx in Appl yyyy, missing zzzz name Explanation: A required item, zzzz, was not provided. For example, an OS2_Job

requires a command name. An HPUX_Job requires a script name. System Action: The execution of the object fails, and a "submit error" status

results. User Response: Provide the required information. Then resubmit the job.



4106E SAP_Job xxxx in Appl yyyy, missing ABAPname Explanation: Each SAP_Job requires an ABAPname to be specified indicating what

work is to be done by the agent. This job does not have one. System Action: The job is not processed. User Response: Add the missing information to the job in the ESP procedure.











Messages and Codes

ESP-5.4-MC-03 433





System Action: The application is not built. User Response: In order to submit jobs to this agent using ID yyyy, user xxxx

must have read access to SAF profile AGENTUSR.yyyy.agentname. Once this has been established, retrigger the event.

4114E USER can only be used with encrypted agents Explanation: The USER statement can only be used with agents that have encryption

enabled on their communications channel. System Action: Application generation fails. User Response: if the use of USER is required, have the ESP administrator activate

encryption on this agent's communications.

4115I xxxxxxxx: yyyyyyyyyyyyyyyyyy Explanation: This message was issued by an Agent_Monitor object in response to

a 'CONTROL LOG INFO Text(yyyyyyyyyyy)' automation framework message. The source of the message is xxxxxxxx.


4116W xxxxxxxx: yyyyyyyyyyyyyyyyyy Explanation: This message was issued by an Agent_Monitor object in response to

a 'CONTROL LOG WARNING Text(yyyyyyyyyyy)' automation framework message. The source of the message is xxxxxxxx.


4117E xxxxxxxx: yyyyyyyyyyyyyyyyyy Explanation: This message was issued by an Agent_Monitor object in response to

a 'CONTROL LOG ERROR Text(yyyyyyyyyyy)' automation framework message. The source of the message is xxxxxxxx.





434 ESP-5.4-MC-03

User Response: Define a password to match the parameters above using the ESP PASSWORD command. Then resubmit the job.

4119E COMMANDNAME too long Explanation: The value on the COMMANDNAME statement exceeded the maximum length

of 100 characters. System Action: The statement is not processed. Event processing fails. User Response: Reduce the length of the value.

4120E COMMAND too long Explanation: The value on the COMMAND statement exceeded the maximum length

allowed for this platform type. System Action: The statement is not processed. Event processing fails. User Response: Reduce the length of the value.

4121E ERROR SCANNING COMMAND, RC=x Explanation: An invalid parameter was coded on a command. System Action: The command is not processed. User Response: Check for error messages preceding this message for further details.

Refer to the command reference to check the command syntax.

4122E Invalid Agent name xxx in Appl yyy Explanation: Agent specified in AGENT statement could not be found. System Action: Application will not be built. User Response: Make sure the correct name is used in the AGENT statement.

4123I Update successful Explanation: A define, update or delete requested through the PASSWORD command

completed successfully. System Action: N/A User Response: N/A

4124E xxxx must be specified Explanation: The operation requested requires that keyword xxxx be specified on

the PASSWORD command. System Action: The command is not processed. User Response: Correct the command and retry the operation.

4125W No entries found to match your criteria Explanation: No entries were found that matched the criteria specified on the

PASSWORD LIST command. System Action: N/A User Response: Retry the command with different criteria.

4126E Index dataset is not open Explanation: The user attempted to update a password entry, but the index data set

is not open. System Action: The command is not processed.

Messages and Codes

ESP-5.4-MC-03 435

User Response: Investigate why the index data set is closed. Retry the command when it is re-opened.

4127E The encryption routine reported an error Explanation: The user attempted to update a password entry, but the encryption

routine reported an error. System Action: The command is not processed. User Response: This is most likely an internal error. Contact Cybermation technical

support.

4128W No matching entries found Explanation: No entries were found that matched the criteria specified on the

PASSWORD LIST command. System Action: N/A User Response: Retry the command with different criteria.

4129E Duplicate password entry Explanation: The user attempted to define a password entry, but the entry already

exists. System Action: The command is not processed. User Response: Use the LIST option of the PASSWORD command to list existing

entries to verify your information.

4131E Password does not match, update refused Explanation: The user attempted to update or delete a password entry, but the

password supplied did not match the password on file. System Action: The command is not processed. User Response: Use the correct password. If you do not know the correct password,

a user with UPDATE access to SAF resource PASSWORD can reset passwords without knowing the old password.

4132E You are not authorized to update password entries Explanation: The user attempted to update or delete a password entry and did

not supply a verification password. The SAF check for UPDATE access to SAF resource PASSWORD failed.

System Action: The command is not processed. User Response: Either specify a verification password, or acquire UPDATE access to

SAF resource PASSWORD.

4133E Specified password entry not found Explanation: The user attempted to update or delete a password entry, but the

specified entry does not exist. System Action: The command is not processed. User Response: Use the LIST option of the PASSWORD command to list defined password

entries and verify your specification.

4134E Index dataset is not open, PWDE init failed Explanation: The index dataset was found closed during PWDE initialization.

436 ESP-5.4-MC-03

System Action: The password entry list is not initialized. User Response: Verify why the index data set was closed during ESP initialization.

Perform an ESP warm start to initialize the password entry list when the index data set becomes available.

4135E Above error occurred during PWDE initialization Explanation: An I/O error occurred on the index data set during PWDE

initialization. System Action: The password entry list is not, or only partially, initialized. User Response: This message should be preceded by a message detailing the nature

of the I/O error.

4136E User ID too long, maximum length nn Explanation: A user ID specified on the USER statement was longer than the

maximum allowed for the workload object type. System Action: Application generation fails. User Response: Replace the user ID with a valid ID.

4140E FileTrig xxx in Appl yyy, missing file name Explanation: The file name is missing for workload object xxx in application yyy. System Action: The application is not built. User Response: Make sure a FILENAME statement with the correct File Name is present

for workload object xxx in application yyy.

4141E FileTrig xxx in Appl yyy, missing Agent name Explanation: The agent name is missing for FileTrig object xxx in application yyy. System Action: The application is not built. User Response: Make sure an AGENT statement with the correct Agent Name is present

for FileTrig object xxx in application yyy.

4147E No space in ATR to store AS/400 message text Explanation: A workload object message was received from an AS/400 agent

containing an operator message, but there was no free space in the ATR to store the message text.

System Action: The operator message text is ignored. The rest of the message is processed as normal.


4148E FILENAME specification error: xxxxxxxxxxxxxxxxxxxx Explanation: The File_Trigger object encountered an error on the FILENAME

statement. The variable part of the message describes the error in more detail.

System Action: The system stops processing the procedure. User Response: Correct the error.

Messages and Codes

ESP-5.4-MC-03 437

4150E Invalid SETVAR Specification Explanation: A SETVAR statement coded within a Data_Object is invalid. System Action: The system stops processing the procedure. User Response: Correct the syntax error.

4151E No space in ATR to store data for object xxxxx Explanation: An ACTION SET message was received by a Data_Object object, but

there was no free space in the ATR to store the data. System Action: The ACTION message text is ignored. The data item is not stored. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


4152E Error in WOBDATA function - 'Reason string' Explanation: An error occurred in the WOBDATA CLANG function. The reason string

contains further details about the error. System Action: Processing ends. User Response: This is most likely a syntax error. Check for an invalid object name

or missing parameters.

4153E No space in ATR to store dependencies for object xxxxx Explanation: There was insufficient space in the ATR to build the dependency

links for an ApplEnd object. System Action: The application is not built. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


4154E ApplEnd can only be defined once Explanation: More than one ApplEnd object was defined in an application. Only one

ApplEnd per application may be coded. System Action: The applicaiton is not build. User Response: Remove all but one ApplDef object.

4155E tttt xxxx in Appl yyyy, missing user name for agent aaaa Explanation: Workload object xxxx of type tttt is bound for virtual agent aaaa.

The virtual agent requires a user name for TelNet login, but neither the job nor the agent definition contains a user name.

System Action: ESP does not submit the job to the agent. The Job's PNODE is set to SUBERROR.

User Response: Specify a user name and rerun the job.


readied.

438 ESP-5.4-MC-03


User Response: Either correct the Agent name, or define the Agent. Then resubmit the job.




the job.

4158E tttt xxxx in Appl yyyy, missing user name for agent aaaa Explanation: Workload object xxxx of type tttt is bound for virtual agent aaaa.

The virtual agent requires a user name for TelNet login, but neither the job nor the agent definition contains a user name.

System Action: ESP does not submit the job to the agent. The Job's PNODE is set to SUBERROR.

User Response: Specify a user name and rerun the job.




the job.

4160E MPEiX_Job xxxx in Appl yyyy, missing account Explanation: An account name, which is necessary for login to an MPE/iX system,

was not provided in the job definition. System Action: The execution of the object fails, and a "submit error" status


4161E User xxxx denied access to account yyyy on agent aaaa Explanation: User xxxx is not authorized to submit jobs to this agent using

account yyyy. This condition can be detected while submitting the job or while building an application containing the job.

System Action: The current process (submission of a job or building of an application) is aborted.

User Response: In order to submit jobs to this agent using account yyyy, provide user xxxx with read access to SAF profile AGENTACC.yyyy.aaaa.

4162E User xxxx denied access to group yyyy on agent aaaa Explanation: User xxxx is not authorized to submit jobs to this agent using group

yyyy. This condition can be detected while submitting the job or while building an application containing the job.

Messages and Codes

ESP-5.4-MC-03 439

System Action: The current process (submission of a job or building of an application) is aborted.

User Response: In order to submit jobs to this agent using group yyyy, provide user xxxx with read access to SAF profile AGENTGRP.yyyy.aaaa.

4163E ARGS too long Explanation: The length of the ARGS exceeds the maximum of 4078 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the ARGS.

4164E OTHERS too long Explanation: The length of the OTHERS exceeds the maximum of 4070 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the OTHERS.

4165E PARAM too long Explanation: The length of the PARAM exceeds the maximum of 4070 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the PARAM.

4166W JOB xxxx SUBMISSION FAILED, STATUS: ssss Explanation: This message is issued on the request of a NOTIFY statement in an ESP

Procedure. The message text indicates that an ESP submitted job has a submission failure. The message text can include the application name or jobnet ID.




Procedure. The message text indicates that an ESP submitted job has started to execute. The message text can include the application name or jobnet ID.



Procedure. The message text indicates that an ESP submitted job has ended execution. The message text includes the completion code and can also include the application name or jobnet ID.


4169W xxxx Explanation: This message is issued on the request of a NOTIFY statement in an ESP

440 ESP-5.4-MC-03

Procedure. The message text indicates that an ESP submitted job has failed during execution. The message text includes the completion code and can also include the application name or jobnet ID.



4170I xxxx yyyy COMPLETED Explanation: This message is issued on the request of a NOTIFY statement in an ESP

Procedure. The message text indicates that an ESP submitted JOB LINK of JOB TASK is completed. The message text can also include the application name or jobnet ID.


4171I TASK xxxx REQUIRES MANUAL COMPLETION Explanation: This message is issued on the request of a NOTIFY statement in an ESP

Procedure. The message text indicates that an ESP submitted JOB TASK has been readied and requires manual intervention (completion) to proceed. The message text can also include the application name or jobnet ID.


User Response: After this TASK is completed, mark it complete to release its successor jobs.

4172W xxxx yyyy Explanation: A job LINK or a job TASK has missed its late end time.

The late end time was defined by the user defining the job to the system.

System Action: The job is considered overdue. User Response: The job's performance group or priority should be raised if this is a

critical job.

4173W MANUAL JOB xxxx Explanation: A MANUAL job has missed its late end time.

The late end time was defined by the user defining the job to the system.

System Action: The job is considered overdue. User Response: The job's performance group or priority should be raised if this is a

critical job.

4174W APPLICATION xx GENERATION nn, User yy, WILL BE FORCED COMPLETE BY ESP

Explanation: The newest generation of the application will FORCE COMPLETE the oldest active generation. User name is the event owner.

System Action: The oldest active generation of the application is forced to complete. User Response: None.

Messages and Codes

ESP-5.4-MC-03 441

4175W APPLICATION xx, User yy, IS REACHING THE LIMIT OF ACTIVE GENERATIONS

Explanation: The maximum number of active generations of the application is going to be reached after 5 (or less) new generations are created. When the limit is reached, the oldest generation will be forced to complete by ESP. User name is the event owner.

System Action: Processing continues. User Response: Notify the application owner.

4176I Auditlog data set spun with nn records to sysout class xxxx Explanation: An automatic SPINLOG command was executed, resulting in the Auditlog

data set being closed and spun off to JES. This message indicates how many records were contained that data set.

System Action: A new data set is allocated and processing continues. User Response: The spun data set is available for viewing, or can be printed or

collected by a sysout archival program.

4177E Above error occurred while trying to open a new Auditlog data set, Auditlog will be unavailable

Explanation: An automatic SPINLOG command was executed, resulting in the closing and deallocation of an Auditlog data set. On attempting to allocate and open a new one, an error occurred. The error is described by the previous message.

System Action: The Auditlog data set will not be available, and audit information may be lost until ESP is restarted.

User Response: ESP should be restarted. If the error persists, comment out the AUDITLOG initialization statement and place an AUDITLOG DD statement in the ESP started task procedure until the problem can be resolved.

4178W Dynamic sysout auditlog not initialized, use AUDITLOG initialization parameter

Explanation: The SPINLOG command was issued. This command is only available if the AUDITLOG initialization parameter is used.

System Action: The command is not executed. User Response: Add the AUDITLOG initialization statement to the ESP parameter data

set and restart ESP. The AUDITLOG statement has the following syntax: AUDITLOG c <FORM(ffff)> <EXTWTR(xxxxxxxx)> <AUDCOUNT(nnnnnnnn)> where c is a one character sysout class ffff is an optional sysout form name, of up to 4 characters xxxxxxxx is an optional external writer name, of up to 8 characters nnnnnnnn is an optional maximal number of records written to the AUDITLOG data set before it is spun

442 ESP-5.4-MC-03

4179I APPLICATION xxxx GENERATION nn JOB yyyy FORCED COMPLETE BY zzzz

Explanation: A job has just been forced complete by a user. System Action: The job is marked as complete. If this job is the last completed

job in its application generation, this application generation is completed.


4180I APPLICATION xxxx GENERATION nn JOB yyyy Resources dropped by zzzz

Explanation: Resource requirements for a job have just been dropped by a user. System Action: The job is submitted for execution, since its resource dependencies

have been dropped. User Response: None.

4181E Invalid LIBL parameter Explanation: The LIBL parameter is in violation of one of the following rules:

- When using more than one LIBL, special values *CURRENT, *JOBD, *SYSVAL, *NONE are not allowed; - Duplication of libraries in the library list is not allowed; - No more than 25 names can be specified.

System Action: The LIBL list processing is not completed. User Response: Correct the parameter and try again.

4182W AUDCOUNT VALUE IS IGNORED SINCE IT IS LESS THAN 5 Explanation: The AUDCOUNT operand of the AUDITLOG parameter specified value that is

too low (less than 5). System Action: The AUDCOUNT operand is ignored and no automatic SPINLOG will occur. User Response: Correct the AUDCOUNT parameter. The correction will take effect after

ESP is restarted.

4183E PROCESS TYPE too long Explanation: The length of the PROCESS TYPE exceeds the maximum of 32 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the PROCESS TYPE.

4184E RUNCONTROLID too long Explanation: The length of the RUNCONTROLID exceeds the maximum of 30 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the RUNCONTROLID.

4185E Unable to find password matching xxxx, yyyy, zzzz Explanation: A PSOprID was specified which required a password. ESP was unable



Messages and Codes

ESP-5.4-MC-03 443


4186E PS_Job xxxx in Appl yyyy, missing Process Name Explanation: A Process Name, which is necessary for a PeopleSoft system,



4187E PS_Job xxxx in Appl yyyy, missing Process Type Explanation: A Process Type, which is necessary for a PeopleSoft system,



4188E DistrListUsers too long Explanation: The length of the DistrListUsers exceeds the maximum of 256 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the DistrListUsers.

4189E DistrListRoles too long Explanation: The length of the DistrListRoles exceeds the maximum of 256 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the DistrListRoles.

4190E EmailAddr too long Explanation: The length of the EmailAddr exceeds the maximum of 256 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the EmailAddr.

4191E EmailSubject too long Explanation: The length of the EmailSubject exceeds the maximum of 256 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the EmailSubject.

4192E EmailAddrExp too long Explanation: The length of the EmailAddrExp exceeds the maximum of 256 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the EmailAddrExp.

4193E EmailText too long Explanation: The length of the EmailText exceeds the maximum of 1024 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the EmailText.

4194E SAPEmailAddr too long Explanation: The length of the SAPEmailAddr exceeds the maximum of 256 characters.

444 ESP-5.4-MC-03

System Action: The event fails. The object is not generated. User Response: Reduce the length of the SAPEmailAddr.


4200S XCFCMD command code xxxx invalid Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4201E SYSPLEX error, Default XCF group xxxx already joined, Member=yyyy Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4202W SYSPLEX TERMOPT=QUIESCE ignored, Sysplex in XCFLOCAL mode Explanation: The SYSPLEX statement in the ESPPARM file specifies TERMOPT(QUIESCE)

and MVS is in XCFLOCAL mode, i.e. PLEXCFG=XCFLOCAL is specified on the active IEASYSxx member of MVS's SYS1.PARMLIB. An XCF member cannot be quiesced on an XCFLOCAL system.

System Action: Processing continues. ESP will leave the XCF group when it terminates, because it cannot quiesce its XCF member.

User Response: Remove the TERMOPT(QUIESCE) operand from the ESPPARM file SYSPLEX statement. Note that if TERMOPT is omitted on the SYSPLEX statement, TERMOPT(QUIESCE) is the default for non-XCFLOCAL systems and TERMOPT(LEAVE) is the default for XCFLOCAL systems.

4203E XCF command missing Explanation: An XCF command was issued with no operands. System Action: Processing continues. User Response: For a list of valid XCF command options, enter:

XCF HELP or XCF H or XCF ?

4204E XCF xxxx command invalid Explanation: An XCF command was issued with an invalid option xxxx. System Action: Processing continues. User Response: For a list of valid XCF command options, enter:


4205E XCF xxxx not an initialization command Explanation: An XCF statement in the ESPPARM file specifies option xxxx, which is

Messages and Codes

ESP-5.4-MC-03 445

invalid at initialization. System Action: ESP action message 802A is issued to prompt for an END (to ignore the

"XCF xxxx" statement) or a CANCEL (to terminate ESP) response. User Response: Respond to action message 802A and remove erroneous "XCF xxxx"

statement from ESPPARM file.

4206E XCF xxxx object missing Explanation: The XCF command with option xxxx requires one or more additional

operands. System Action: Processing continues. User Response: For a list of valid XCF command options, enter:


4207E XCF xxxx object yyyy invalid Explanation: The XCF command with option xxxx specified an invalid option yyyy. System Action: Processing continues. User Response: For a list of valid XCF command options, enter:


4208I XCF HELP Explanation: Response to "XCF HELP", "XCF H" or "XCF ?" command. System Action: Processing continues. User Response: None.

4209I No active XCF connections Explanation: Response to "XCF DISPLAY ACTIVE" or "XCF D A" command. System Action: Processing continues. User Response: None.

4210I XCF DISPLAY ACTIVE Explanation: Response to "XCF DISPLAY ACTIVE" or "XCF D A" command.

Displays active XCF listeners and active XCF connections. System Action: Processing continues. User Response: None.

4211W No XCF groups joined Explanation: Response to "XCF DISPLAY GROUP" or "XCF D G" command.

During initialization, ESP tried unsuccessfully to join an XCF group as a member specified by the SYSPLEX statement in the ESPPARM file. This usually happens when another ESP has already joined the XCF group as the same member name.

System Action: Processing continues. User Response: To request the current ESP to retry joining the XCF group as the

specified member, enter the following ESP operator command: TRYJOIN

446 ESP-5.4-MC-03

If this fails with the following 4282 error message: IXCJOIN, Member already active, Group=xxxx, Member=yyyy where xxxx is the XCF group name and yyyy is the already active XCF member name, then enter the following ESP operator command: TRYJOIN MEMBER(zzzz) where zzzz specifies a new XCF member name.

4212I XCF DISPLAY GROUP Explanation: Response to "XCF DISPLAY GROUP" or "XCF D G" command.

Displays members of the XCF group in the sysplex that the current ESP (or other Cybermation product) has joined.


4213I XCF DISPLAY SYSTEMS Explanation: Response to "XCF DISPLAY SYSTEMS" or "XCF D SYS" command.

Displays MVS systems in the sysplex. System Action: Processing continues. User Response: None.

4214W No registered XCF services Explanation: Response to "XCF DISPLAY SERVICES" or "XCF D S" command.

No XCF services are available to the current ESP. This happens when there are no "XCF START SERVICE" statements in the ESPPARM file.

System Action: Processing continues. User Response: None if the use of XCF services are not required by the current ESP.

If the use of XCF services (TRACKING, DSTRIG, ROUTING etc.) are required by the current ESP, an "XCF START SERVICE" statement must be added to the ESPPARM file for each required XCF service. Then ESP must be restarted.

4215I XCF DISPLAY SERVICES Explanation: Response to "XCF DISPLAY SERVICES" or "XCF D S" command.

Displays the status of each registered XCF service, i.e. each XCF service specified by an "XCF START SERVICE" statement in the ESPPARM file.


4216I XCF service xxxx already started|resumed{, Group=yyyy{, Member=zzzz}} Explanation: Response to "XCF START SERVICE xxxx" or "XCF S S xxxx" command, or

automatic resumption of suspended XCF service xxxx after its suspend time interval has expired. xxxx is the Cybermation product XCF service, yyyy is the XCF group name and zzzz is the local XCF member name.


Messages and Codes

ESP-5.4-MC-03 447

4217I XCF service xxxx started{, Group=yyyy{, Member=zzzz}} Explanation: Response to "XCF START SERVICE xxxx" or "XCF S S xxxx" command.

xxxx is the Cybermation product XCF service, yyyy is the XCF group name and zzzz is the local XCF member name.

System Action: XCF service xxxx is activated. User Response: None.

4218W XCF service xxxx not active{, Group=yyyy{, Member=zzzz}} Explanation: Response to "XCF STOP SERVICE xxxx" or "XCF P S xxxx" command.



4219W XCF service xxxx cannot be stopped|suspended, no associated connection{, Group=yyyy{, Member=zzzz}}

Explanation: Response to "XCF STOP SERVICE xxxx" or "XCF P S xxxx" command, or internal attempt to suspend XCF service following XCF I/O error. xxxx is the Cybermation product XCF service, yyyy is the XCF group name and zzzz is the local XCF member name. A Cybermation product's XCF service xxxx was registered (via an "XCF START SERVICE xxxx" statement) with no "XCF STOP SERVICE" exit, and no XCF connection is associated with it. Such an XCF service cannot be stopped with an "XCF STOP SERVICE xxxx" command, nor can it be suspended. Currently all ESP's XCF services are registered with an "XCF STOP SERVICE" exit. This message should therefore never be displayed by ESP.

System Action: Processing continues. User Response: Call Cybermation support.

4220I XCF service xxxx stopped|suspended{, Group=yyyy{, Member=zzzz}} Explanation: Response to "XCF STOP SERVICE xxxx" or "XCF P S xxxx" command, or

internal suspension of XCF service xxxx following an XCF I/O error. xxxx is the Cybermation product XCF service, yyyy is the XCF group name and zzzz is the local XCF member name.

System Action: XCF service xxxx stops or suspends. User Response: None.

4221I {Listener and }wwww connections purged, Service=xxxx{, Group=yyyy{, Member=zzzz}}

Explanation: Response to "XCF PURGE SERVICE xxxx" or "XCF PURGE S xxxx" command. wwww is the number of connections purged, xxxx is the Cybermation product XCF service, yyyy is the XCF group name and zzzz is the local XCF member name.

System Action: The listener (if one exists) and all connections associated with XCF service xxxx terminate. ESP then immediately restarts XCF service xxxx.


448 ESP-5.4-MC-03

4222E XCF {START|STOP|PURGE} SERVICE object missing Explanation: Response to "XCF START SERVICE", "XCF S S", "XCF STOP SERVICE",

"XCF P S", "XCF PURGE SERVICE" or "XCF PURGE S" command. An XCF service name was not specified in the command.

System Action: Processing continues. User Response: Re-enter the command specifying which XCF service to START, STOP or

PURGE. For example: XCF STOP SERVICE TRACKING

4223E XCF {START|STOP|PURGE} object xxxx invalid Explanation: Response to "XCF START SERVICE", "XCF S S", "XCF STOP SERVICE",

"XCF P S", "XCF PURGE SERVICE" or "XCF PURGE S" command. The specified XCF service name xxxx is invalid. It must be a 1 to 8 character alphanumeric and/or national character name.

System Action: Processing continues. User Response: Re-enter the command specifying a valid XCF service to START, STOP or

PURGE. For example: XCF STOP SERVICE ROUTING

4224E Connection xxxx not found Explanation: Response to "XCF PURGE CONNECTION xxxx" or "XCF PURGE CON xxxx"

command. xxxx is the local connection number. System Action: Processing continues. User Response: Re-enter the command specifying the local connection number of an

active XCF connection. To display the active XCF connections, enter the command: XCF DISPLAY ACTIVE or XCF D A The first of 2 numbers in the "Connection" field is the local connection number yyyy to use in the "XCF PURGE CONNECTION yyyy" command.

4225I Connection xxxx purged Explanation: Response to "XCF PURGE CONNECTION xxxx" or "XCF PURGE CON xxxx"

command. xxxx is the local connection number. System Action: Connection xxxx is closed. User Response: None.

4226I xxxx members stopped Explanation: Response to "XCF STOP GROUP" or "XCF P G" command.

xxxx is the number of stopped XCF members. System Action: All members of the XCF group except the local member are stopped. User Response: None.

4227E XCF SET MEMBER invalid at initialization Explanation: Response to "XCF SET MEMBER" or "XCF T M" statement in the ESPPARM

file. System Action: Processing continues.

Messages and Codes

ESP-5.4-MC-03 449

User Response: Remove the "XCF SET MEMBER" or "XCF T M" statement from ESPPARM file.

4228E XCF SET MEMBER object missing Explanation: Response to "XCF SET MEMBER" or "XCF T M" command.

An XCF member name was not specified in the command. System Action: Processing continues. User Response: Re-enter the command specifying which XCF member to SET, and what to

set it to (MASTER or M). For example: XCF SET MEMBER ESP001 MASTER where ESP001 is the target XCF member name.

4229E XCF SET MEMBER object xxxx invalid Explanation: Response to "XCF SET MEMBER xxxx" or "XCF T M xxxx" command.

The XCF specified member name xxxx is invalid. It must be a 1 to 16 character alphanumeric and/or national character name other than "MISSING".

System Action: Processing continues. User Response: Re-enter the command specifying a valid XCF member to SET, and what to

set it to (MASTER or M). For example: XCF SET MEMBER ESP002 MASTER where ESP002 is the target XCF member name. To display the current XCF group members, enter the command: XCF DISPLAY GROUP or XCF D G

4230E XCF SET MEMBER exit not registered Explanation: Response to "XCF SET MEMBER" or "XCF T M" command.

If a Cybermation product does not register an "XCF SET MEMBER exit", the command has no meaning. However, ESP registers an "XCF SET MEMBER exit" to process the {MASTER|M} operand. This message should therefore never be displayed by ESP.


4231I XCF member xxxx stopped, Group=yyyy Explanation: Response to "XCF STOP MEMBER", "XCF P M", "XCF STOP MEMBER xxxx" or

"XCF P M xxxx" command. xxxx is the target XCF member name and yyyy is the XCF group. If xxxx is omitted in the command, the local XCF member is stopped.

System Action: Target XCF member xxxx terminates. User Response: None.

4232I XCF member xxxx forced, Group=yyyy Explanation: Response to "XCF FORCE MEMBER xxxx" or "XCF FORCE M xxxx" command.

xxxx is the target XCF member name and yyyy is the XCF group. System Action: Target XCF member xxxx is abnormally terminated with code S00C. User Response: None.

450 ESP-5.4-MC-03

4233E XCF member xxxx active, cannot be deleted, Group=yyyy Explanation: Response to "XCF FORCE MEMBER xxxx" or "XCF FORCE M xxxx" command.

xxxx is the target XCF member name and yyyy is the XCF group. An XCF member cannot be deleted if it is in the active state. It must be in the created, quiesced or failed state.

System Action: Processing continues. User Response: To display the current XCF group members and their respective states,

enter the command: XCF DISPLAY GROUP or XCF D G

4234I XCF member xxxx deleted, Group=yyyy Explanation: Response to "XCF FORCE MEMBER xxxx" or "XCF FORCE M xxxx" command.

xxxx is the target XCF member name and yyyy is the XCF group. System Action: Target XCF member xxxx is removed from XCF group yyyy. User Response: None.

4235E XCF SET INTERVAL invalid at initialization Explanation: The "XCF SET INTERVAL" or "XCF T INT" command is invalid as an ESPPARM

file statement. System Action: ESP action message 802A is issued to prompt for an END (to ignore the

"XCF SET INTERVAL" or "XCF T INT" statement) or a CANCEL (to terminate ESP) response.

User Response: Respond to action message 802A and remove "XCF SET INTERVAL" or "XCF T INT" statement from ESPPARM file.

4236E XCF SET INTERVAL value missing Explanation: Response to an "XCF SET INTERVAL" or "XCF T INT" command.

The "XCF SET INTERVAL" or "XCF T INT" command was issued without an interval specification.

System Action: Processing continues. User Response: Re-issue the "XCF SET INTERVAL" or "XCF T INT" command specifying a

valid interval in seconds (number within range 3-86400).

4237E Status monitoring not active, Group=xxxx, Member=yyyy Explanation: Response to an "XCF SET INTERVAL" or "XCF T INT" command.

xxxx is the XCF group name and yyyy is the local XCF member name. The SYSPLEX statement in the ESPPARM file did not specify the INTERVAL(zzzz) option, where zzzz is the interval in seconds, a number within the range 3-86400. Therefore XCF status monitoring is not active, and there is no interval to set.

System Action: Processing continues. User Response: If XCF status monitoring is not desired, none. Otherwise add the

INTERVAL(zzzz) keyword to the SYSPLEX statement in the ESPPARM file.

4238I Status monitoring interval set to xxxx, Group=yyyy, Member=zzzz Explanation: Response to an "XCF SET INTERVAL xxxx" or "XCF T INT xxxx" command.

xxxx is the status monitoring interval in seconds, yyyy is the XCF

Messages and Codes

ESP-5.4-MC-03 451

group name and zzzz is the local XCF member name. System Action: The XCF status monitoring interval is reset to xxxx seconds. User Response: None.

4239E XCF SET TERMOPT invalid at initialization Explanation: The "XCF SET TERMOPT" or "XCF T TO" command is invalid as an ESPPARM

file statement. System Action: ESP action message 802A is issued to prompt for an END (to ignore the

"XCF SET TERMOPT" or "XCF T TO" statement) or a CANCEL (to terminate ESP) response.

User Response: Respond to action message 802A and remove "XCF SET TERMOPT" or "XCF T TO" statement from ESPPARM file.

4240E XCF SET TERMOPT action (LEAVE or QUIESCE) missing Explanation: Response to an "XCF SET TERMOPT" or "XCF T TO" command. System Action: Processing continues. User Response: Re-enter the "XCF SET TERMOPT" or "XCF T TO" command with the LEAVE or

QUIESCE option.

4241E XCF SET TERMOPT QUIESCE invalid, system is in XCFLOCAL mode Explanation: Response to an "XCF SET TERMOPT QUIESCE" or "XCF T TO Q" command.

MVS is running in XCFLOCAL mode, i.e. PLEXCFG=XCFLOCAL is specified on the active IEASYSxx member of the MVS's SYS1.PARMLIB. An XCF member cannot be quiesced in an XCFLOCAL system.

System Action: Processing continues. ESP (or other Cybermation product) will leave the XCF group when it terminates, because it cannot quiesce its XCF member.


4242I XCF TERMOPT set to {LEAVE|QUIESCE}, Group=xxxx, Member=yyyy Explanation: Response to an "XCF SET TERMOPT" or "XCF T TO" command.

xxxx is the XCF group name and yyyy is the local XCF member name. System Action: Processing continues. ESP (or other Cybermation product) will leave the

XCF group if LEAVE was specified, or quiesce its XCF member if QUIESCE was specified, when it terminates.


4243I Verify request transmitted to XCF member xxxx, Group=yyyy Explanation: Response to an "XCF VERIFY MEMBER" or "XCF VER M" command.

xxxx is the XCF group name and yyyy is the target XCF member name. System Action: Target XCF member xxxx verifies if any broken connections on its end

with the local XCF member exist, and closes them if any are found. It then transmits a verify response to the local XCF member, who verifies if any broken connections on its end with XCF member xxxx exist, and closes them if any are found.


4244E XCF group xxxx not joined Explanation: Response to various XCF commands.

During initialization, ESP tried unsuccessfully to join an XCF group as

452 ESP-5.4-MC-03

a member specified by the SYSPLEX statement in the ESPPARM file. This usually happens when another ESP has already joined the XCF group as the same member name.

System Action: Processing continues. User Response: To request the current ESP to retry joining the XCF group as the

specified member, enter the following ESP operator command: TRYJOIN If this fails with the following 4282 error message: IXCJOIN, Member already active, Group=xxxx, Member=yyyy where xxxx is the XCF group name and yyyy is the XCF member name, then enter the following ESP operator command: TRYJOIN MEMBER(zzzz) where zzzz specifies a new XCF member name.

4245E Local XCF member xxxx invalid, Group=yyyy Explanation: Response to an XCF command that specified local XCF member xxxx in XCF

group yyyy. The command requires a non-local target XCF member specification.

System Action: Processing continues. User Response: If necessary, re-enter the command specifying a non-local XCF member.

To display the current XCF group members, enter the command: XCF DISPLAY GROUP or XCF D G

4246E XCF member xxxx not found, Group=yyyy Explanation: Response to an XCF command that specified target XCF member xxxx in

XCF group yyyy. XCF member xxxx does not exist. System Action: Processing continues. User Response: Re-enter the command specifying a valid XCF member.

To display the current XCF group members, enter the command: XCF DISPLAY GROUP or XCF D G

4247E XCF member xxxx not active, Group=yyyy Explanation: Response to an XCF command that specified non-active XCF member xxxx in

XCF group yyyy. The command requires an active target XCF member specification.

System Action: Processing continues. User Response: If necessary, re-enter the command specifying an active XCF member.

To display the current XCF group members and their respective states, enter the command: XCF DISPLAY GROUP or XCF D G

4248E XCF service xxxx not found{, Group=yyyy{, Member=zzzz}} Explanation: Response to an XCF command that specifies a non-existent target XCF

service xxxx. yyyy is the XCF group name and zzzz is the local XCF member name.


Messages and Codes

ESP-5.4-MC-03 453

User Response: If necessary, re-enter the command specifying a valid XCF service. To display XCF services, enter the command: XCF DISPLAY SERVICES or XCF D S

4249W No connections found for XCF service xxxx{, Group=yyyy{, Member=zzzz}} Explanation: Response to "XCF PURGE SERVICE xxxx" or "XCF PG S xxxx" command.



4250W System xxxx in sysplex partitioning, shutdown initiated, Group=yyyy, Member=zzzz

Explanation: ESP (or other Cybermation product) has been notified by MVS that the current system xxxx is being removed from the sysplex, i.e. a "VARY XCF,xxxx,OFFLINE" system command has been issued. yyyy is the XCF group name and zzzz is the local XCF member name.

System Action: ESP (or other Cybermation product) terminates. User Response: None.

4251E Message event, MSGCNTL invalid, Group=xxxx, Member=yyyy, Partner=zzzz Explanation: XCF member zzzz transmitted invalid data to local XCF member yyyy in

XCF group xxxx. This probably means that XCF member zzzz is a non-Cybermation product. The current message is immediately followed by message 4252, which displays the contents of the message control (MSGCNTL) field found to be invalid.

System Action: Processing continues. User Response: Check if a Cybermation and a non-Cybermation product have joined the

same XCF group. To display the current XCF group members, enter the command: XCF DISPLAY GROUP or XCF D G If the local XCF member is an ESP, the XCF members in which the "ASID", "Jobname", "SSID" and "ESP" fields are blank may indicate a non-Cybermation product. If the problem is still not solved, call Cybermation support and provide the text of both the current message and message 4252 that immediately follows.

4252E MSGCNTL=X'xxxx' Explanation: This message follows message 4251. It displays the hexadecimal value

xxxx of the 32-byte message control (MSGCNTL) field found to be invalid (from a Cybermation product's point of view).


same XCF group. To display the current XCF group members, enter the command: XCF DISPLAY GROUP or

454 ESP-5.4-MC-03

XCF D G If the local XCF member is an ESP, the XCF members in which the "ASID", "Jobname", "SSID" and "ESP" fields are blank may indicate a non-Cybermation product. If the problem is still not solved, call Cybermation support and provide the text of both the current message and the immediately preceding message 4251.

4253E Message event, Request wwww invalid, Group=xxxx, Member=yyyy, Partner=zzzz

Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4254W XCF buffer core request failed, Length=<length>, Partner=<member>, Group=<group>, Service=<service>

Explanation: There is insufficient virtual storage for a buffer to receive <length> bytes of data transmitted by member <member> of XCF group <group> for XCF service <service>.

System Action: Processing continues. User Response: Perhaps the REGION parameter value of the JCL EXEC statement for the

local XCF member job should be increased. Cybermation's XCF component supports the transmission of data up to a maximum length of 16 megabytes.

4255I XCF STOP command received from member xxxx, Group=yyyy Explanation: A request to stop the current ESP (or other Cybermation product) was

received from XCF member xxxx in XCF group yyyy. System Action: ESP (or other Cybermation product) terminates. User Response: None.

4256I Closing broken connection, Group=<group>, Member=<local_member>{, Partner=<partner_member>}, Service=<service>{, Token=(<local_token>, <partner_token>)}

Explanation: A broken XCF connection (one previously closed by the partner XCF member but not by the local XCF member) has been detected and closed. This message follows a "VERIFY MEMBER" request from either the local or the partner XCF member.

System Action: The broken XCF connection is closed by the local XCF member. User Response: None.

Messages and Codes

ESP-5.4-MC-03 455

4257E Message event, {Connect|Connect response|Send|Send response|Close| Signal|Verify|Verify response|Stop|Unknown request <number>}, {Listener not found|Core shortage|Connection not found|Connection closed |Unknown reason <number>}, Group=<group>, Member=<local_member>, Partner=<partner_member>{, Service=<service>, Token=(<local_token>, <partner_token>)}{{, Offset=<offset>}, Length=<length>}

Explanation: A message with an associated error has been received from member <partner_member> in XCF group <group>.

System Action: Processing continues. User Response: Usually none. If a problem exists, call Cybermation support.

4258W XCF service xxxx stopped, default XCF group not defined Explanation: A request was made to conditionally delete XCF service xxxx if it has

not been started by an "XCF START SERVICE xxxx" command. XCF service xxxx was started, but its associated (default) XCF group has not yet been defined. XCF service xxxx is therefore stopped. For ESP subsystems, in the ESPPARM initialization file, an "XCF START SERVICE xxxx" statement was specified, but the required SYSPLEX statement statement was missing or invalid.

System Action: Processing continues. User Response: For ESP subsystems, either add a valid SYSPLEX statement to, or remove

the "XCF START SERVICE xxxx" statement from the ESPPARM initialization file.

4259W XCF service xxxx not active, XCF group yyyy not joined Explanation: A request was made to conditionally delete XCF service xxxx if it has

not been started by an "XCF START SERVICE xxxx" command. XCF service xxxx has been started and is therefore not deleted. However, XCF service xxxx could not be activated because its XCF group yyyy has not been successfully joined. This usually happens when ESP attempts to join XCF group yyyy as the same member name as an existing active ESP.

System Action: Processing continues. User Response: For ESP subsystems, attempt to join the XCF group as the member

specified in the MEMBER operand of the ESPPARM file SYSPLEX statement with the following command: OPER TRYJOIN If this fails because another ESP is active in XCF group yyyy as the same member name as specified in the MEMBER operand of the ESPPARM file of the local ESP, then issue the following command: OPER TRYJOIN MEMBER(zzzz) where zzzz specifies a 1 to 16 alphanumeric XCF member name other than "MISSING" that no other ESP has used to join XCF group yyyy. Once XCF group yyyy has been successfully joined, all started XCF services, including xxxx, are activated.

456 ESP-5.4-MC-03

4260E Cannot join sysplex, default XCF group not defined Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4261E User state field length xxxx invalid, must be 32, Member=yyyy, Group=zzzz

Explanation: XCF member xxxx of the XCF group yyyy was found to have a user state field less than 32 bytes long. This probably means that XCF member xxxx is a non-Cybermation product.


same XCF group. To display the current XCF group members, enter the command: XCF DISPLAY GROUP or XCF D G If the local XCF member is an ESP, the XCF members in which the "ASID", "Jobname", "SSID" and "ESP" fields are blank may indicate a non-Cybermation product. If the problem is still not solved, call Cybermation support.

4262E User state field X'xxxx' invalid, Member=yyyy, Group=zzzz Explanation: XCF member yyyy of the XCF group zzzz was found to have an invalid user

state field xxxx (a 32-byte hexadecimal value). This probably means that XCF member yyyy is a non-Cybermation product.


same XCF group. To display the current XCF group members, enter the command: XCF DISPLAY GROUP or XCF D G If the local XCF member is an ESP, the XCF members in which the "ASID", "Jobname", "SSID" and "ESP" fields are blank may indicate a non-Cybermation product. If the problem is still not solved, call Cybermation support.

4275E Suspend interval value missing Explanation: Response to "XCF SET SERVICE xxxx" or "XCF T S xxxx" command.

xxxx is the Cybermation product XCF service. An "XCF SET SERVICE xxxx' command was issued without specifying the SUSPEND(nnn) keyword operand, where nnn is the XCF service suspend time (a value within the range 0-3600) in seconds.


4276I XCF service xxxx suspend interval set to nnn second{s}{, Group=yyyy{, Member=zzzz}}

Explanation: Response to "XCF SET SERVICE xxxx" or "XCF T S xxxx" command.

Messages and Codes

ESP-5.4-MC-03 457


System Action: XCF service xxxx's suspend time interval is set to nnn seconds. User Response: None.

4280I IXC{DELET|JOIN|LEAVE|MOD|MSGI|MSGO|QUERY|QUIES|SETUS| TERM}{, REQINFO={SYSPLEX|GROUP}} {, Return=<number>, Reason=<hex_value>} {,<result>}{, {Connect|Connect response|Send|Send response|Close|Signal| Verify|Verify response|Stop|Unknown request <number>} {,Listener not found|Core shortage|Connection not found| Connection closed |Unknown reason <number>}}{, Group=<group>} {, Member=<member>}{, Partner=<partner_member>} {,Target=<target_member>}{, Interval=<interval>{, Service=<service> {,Token=(<local_token>,<partner_token>)}} {, {Offset=<offset>, Length=(<segment_length>, <total_length>)|Length=<length>}}

Explanation: An informational message describing the result of an API call to XCF. System Action: Processing continues. User Response: None.

4281W IXC{DELET|JOIN|LEAVE|MOD|MSGI|MSGO|QUERY|QUIES|SETUS| TERM}{, REQINFO={SYSPLEX|GROUP}} {, Return=<number>, Reason=<hex_value>} {,<result>}{, {Connect|Connect response|Send|Send response|Close|Signal| Verify|Verify response|Stop|Unknown request <number>} {,{Listener not found|Core shortage|Connection not found| Connection closed |Unknown reason <number>}}{, Group=<group>} {,Member=<member>}{, Partner=<partner_member>} {,Target=<target_member>}{, Interval=<interval>{, Service=<service> {,Token=(<local_token>,<partner_token>)}} {, {Offset=<offset>, Length=(<segment_length>, <total_length>)|Length=<length>}}

Explanation: A warning message describing the result of an API call to XCF. System Action: Processing continues. User Response: None.

458 ESP-5.4-MC-03

4282E IXC{DELET|JOIN|LEAVE|MOD|MSGI|MSGO|QUERY|QUIES|SETUS| TERM}{, REQINFO={SYSPLEX|GROUP}} {, Return=<number>, Reason=<hex_value>} {, <result>}{, {Connect|Connect response|Send|Send response|Close|Signal| Verify|Verify response|Stop|Unknown request <number>} {,{Listener not found|Core shortage|Connection not found| Connection closed |Unknown reason <number>}}{, Group=<group>} {,Member=<member>}{, Partner=<partner_member>} {,Target=<target_member>}{, Interval=<interval>{, Service=<service> {,Token=(<local_token>,<partner_token>)}} {, {Offset=<offset>, Length=(<segment_length>, <total_length>)|Length=<length>}}

Explanation: An error message describing the result of an API call to XCF. System Action: Processing continues. User Response: Usually none. The content of the message may indicate a specific

action. If a problem arises, call Cybermation support.

4285W XCF not active Explanation: An XCF command was issued, but XCF has not been activated for the

Cybermation product. For ESP, there is no SYSPLEX statement in the ESPPARM file.

System Action: Processing continues. User Response: If XCF services are required, add a SYSPLEX statement to the ESPPARM

file and recycle ESP.

4286W XXCF <function>, <warning_description>{, <connection_infomation>} Explanation: An internal Cybermation API request for an XCF service has resulted in

an unexpected condition. XXCF is a macro that generates an internal Cybermation API call for an XCF service.

System Action: Processing continues. User Response: Check if the XCF services are in order with the command:

XCF DISPLAY SERVICES or XCF D S Check if the XCF connections are in order with the command: XCF DISPLAY ACTIVE or XCF D A If a problem exists, call Cybermation support.

4287E XXCF <function>, <error_description>{, <connection_information>} Explanation: An internal Cybermation API request for an XCF service has resulted in

an error condition. XXCF is a macro that generates an internal Cybermation API call for an XCF service.


Messages and Codes

ESP-5.4-MC-03 459

User Response: Check if the XCF services are in order with the command: XCF DISPLAY SERVICES or XCF D S Check if the XCF connections are in order with the command: XCF DISPLAY ACTIVE or XCF D A If a problem exists, call Cybermation support.

4288S XXCF <function>, <error_description>{, <connection_infomation>} Explanation: Internal logic error. Should never happen.

XXCF is a macro that generates an internal Cybermation API call for an XCF service.


4290I IXCARM Associate|DeRegister|Ready|Register|WaitPred{, aaaa| Return=bbbb, Reason=cccc}, Element=dddd{, ElemType=eeee} {, TElement=ffff}{, StartTxt='gggg'}{, TermType=AllTerm|ElemTerm} aaaa is an informational message description. bbbb specifies the IXCARM call return code. cccc specifies the IXCARM call reason code. dddd specifies the ARM element name (ESP/WM ARMELEM command NAME keyword). eeee specifies the ARM element type (ESP/WM ARMELEM TYPE keyword). ffff specifies the ARM target element name of an ARM associate request (not supported by ESP/WM). gggg specifies start text of an ARM register request (not supported by ESP/WM).

Explanation: An Automatic Restart Management (ARM) request has completed successfully. The message describes the request.


460 ESP-5.4-MC-03

4291E IXCARM Associate|DeRegister|Ready|Register|WaitPred{, aaaa| Return=bbbb, Reason=cccc}, Element=dddd{, ElemType=eeee} {, TElement=ffff}{, StartTxt='gggg'}{, TermType=AllTerm|ElemTerm} aaaa is an error message description. bbbb specifies the IXCARM call return code. cccc specifies the IXCARM call reason code. dddd specifies the ARM element name (ESP/WM ARMELEM command NAME keyword). eeee specifies the ARM element type (ESP/WM ARMELEM TYPE keyword). ffff specifies the ARM target element name of an ARM associate request (not supported by ESP/WM). gggg specifies start text of an ARM register request (not supported by ESP/WM).

Explanation: An Automatic Restart Management (ARM) request has failed. aaaa or bbbb and cccc describe the reason for the failure. Under ESP/WM, the ARMELEM intialization statement usually causes this error.

System Action: ESP/WM action message 802A is issued to prompt for an END (to ignore the ARMELEM statement) or a CANCEL (to terminate ESP/WM) response.

User Response: Attempt to determine the cause of the ARM request failure, and correct it. Then respond to ESP/WM action message 802A by re-entering a correct ARMELEM statement, or "END" if there is no need to register ESP/WM with ARM, or "CANCEL" to terminate ESP. If the ARMELEM statement in the ESPPARM initialization file is erroneous, then correct it.

4292E XARM Associate|DeRegister|Ready|Register|WaitPred xxxx xxxx is an error message descrption.

Explanation: An Automatic Restart Management (ARM) request is invalid. xxxx describes the reason for the failure. Under ESP/WM, the ARMELEM initialization statement usually causes this error.

System Action: ESP/WM action message 802A is issued to prompt for an END (to ignore the ARMELEM statement) or a CANCEL (to terminate ESP/WM) response.

User Response: Attempt to determine the cause of the invalid ARM request, and correct it. Then respond to ESP/WM action message 802A by re-entering a correct ARMELEM statement, or "END" if there is no need to register ESP/WM with ARM, or "CANCEL" to terminate ESP/WM. If the ARMELEM statement in the ESPPARM initialization file is erroneous, then correct or delete it. Note that this error message will be displayed if there is more than one ARMELEM statement in the ESPPARM initialization file.

Messages and Codes

ESP-5.4-MC-03 461

4293W No request for XCF message response rrrr, Group=gggg, Member=mmmm, Partner=pppp, Service=ssss, Token=(ttt1,ttt2) rrrr is the XCF message response number. gggg is the XCF group name. mmmm is the local XCF member name. pppp is the XCF partner member name. ssss is the XCF service name. ttt1 is the local XCF connection token ttt2 is the partner XCF connection token.

Explanation: A response to an XCF send request was received. However, the original XCF send could not be found. This could occur if the XCF send request timed out before the response was received.

System Action: Processing continues. User Response: Normally none. If the problem persists, contact Cybermation support.

4300S Invalid ESP XCF request xxxx Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4301E XCF join request invalid, ESP xxxx has already joined XCF group yyyy as member zzzz


4302W Cannot join XCF group, default not specified Explanation: ESP cannot join an XCF group because a SYSPLEX statement was not

specified in the ESPPARM file. ESP currently suppresses this message.

System Action: Processing continues. User Response: If XCF services are desired, add a SYSPLEX statement in the ESPPARM

file specifying which XCF group ESP should join, and which member it should join as.

4303I ESP xxxx has joined XCF group yyyy as member zzzz Explanation: Response to "TRYJOIN" or "TRYJOIN MEMBER(zzzz)" command. ESP

subsystem xxxx has successfully joined XCF group yyyy as member zzzz after a previous attempt to join group yyyy as the member specified by the SYSPLEX MEMBER operand in the ESPPARM file failed during ESP initialization. If the TRYJOIN MEMBER operand was omitted, zzzz is the member specified in the SYSPLEX MEMBER operand.


462 ESP-5.4-MC-03

4304E XCF add services request invalid, ESP xxxx services already registered, Member=yyyy, Group=zzzz


4305E ESP master hold time xxxx not within range 1-1440 Explanation: Response to "SHADOW SHUTDOWN HOLD(xxxx)" command issued on an ESP

master subsystem, where xxxx is a value in minutes. xxxx must specify a number within the range 1-1440.

System Action: The local ESP does not terminate. Processing continues. User Response: Re-issue the "SHADOW SHUTDOWN HOLD" command specifying an xxxx value

within the range 1-1440, or omitting xxxx and allowing it to default to 5.

4306I ESP master hold time set to xxxx minutes, Member=yyyy, Group=zzzz Explanation: Response to "SHADOW SHUTDOWN HOLD(xxxx)" command issued on an ESP

master subsystem. yyyy and zzzz specify the XCF group and member names respectively of the ESP master subsystem.

System Action: ESP terminates. If, after xxxx minutes, no ESP master has been activated, all active ESP shadow managers without an active shadow goal will output warning message 4320 to the console. Shadow goal action times earlier than the hold time expiration will be delayed until the hold time expiration.


4307W No active ESP shadow manager to relinquish control to Explanation: Response to "SHADOW SHUTDOWN RELINQUISH" command issued on an ESP

master subsystem. There is no active ESP shadow to relinquish control to. System Action: The local ESP does not terminate. Processing continues. User Response: If an ESP shadow manager is needed to take over as the ESP master when

the current one terminates, start one. Then re-issue the "SHADOW SHUTDOWN RELINQUISH" command. To terminate the current ESP without relinquishing control to an active ESP shadow manager, enter the command: SHUTDOWN or SHADOW SHUTDOWN

4308E XCF member xxxx not found Explanation: Response to "SHADOW SHUTDOWN RELINQUISH(xxxx)" command issued on

an ESP master, where xxxx must specify the XCF member name of an active ESP shadow manager.

System Action: The local ESP does not terminate. Processing continues. User Response: To display the current XCF group members, enter the command:

XCF DISPLAY GROUP or XCF D G If an active ESP shadow manager exists, and the user wishes to relinquish control to it after terminating the current ESP master, then re-issue the "SHADOW SHUTDOWN RELINQUISH(xxxx)" command

Messages and Codes

ESP-5.4-MC-03 463

specifying a valid active ESP shadow manager xxxx. To terminate the current ESP without relinquishing control to an active ESP shadow manager, enter the command: SHUTDOWN or SHADOW SHUTDOWN

4309W XCF member xxxx not an active ESP shadow manager Explanation: Response to "SHADOW SHUTDOWN RELINQUISH(xxxx)" command issued on

an ESP master. System Action: The local ESP does not terminate. Processing continues. User Response: To display the current XCF group members, enter the command:

XCF DISPLAY GROUP or XCF D G If an active ESP shadow manager exists, and the user wishes to relinquish control to it after terminating the current ESP master, then re-issue the "SHADOW SHUTDOWN RELINQUISH(xxxx)" command specifying a valid active ESP shadow manager xxxx. To terminate the current ESP without relinquishing control to an active ESP shadow manager, enter the command: SHUTDOWN or SHADOW SHUTDOWN

4310S Local XCF member xxxx XMSE missing, Group=yyyy Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4311I XCF listener started, Service=xxxx Explanation: Response to "XCF START SERVICE xxxx" or "XCF S S xxxx" ESPPARM file

statement or command on an ESP master subsystem, where xxxx specifies an ESP XCF service such as TRACKING, DSTRIG, ROUTING etc.


4312I XCF listener ended, Service=xxxx Explanation: Response to "XCF STOP SERVICE xxxx or "XCF P S yyyy command on an ESP

master subsystem, where xxxx specifies an ESP XCF service such as TRACKING, DSTRIG, ROUTING etc.


4313I XCF {transmitter|receiver} started, Service=xxxx, Partner=yyyy Explanation: The local ESP proxy's XCF service xxxx has connected to the ESP master

(XCF member yyyy). XCF service xxxx (e.g. TRACKING, DSTRIG, ROUTING, SCOREBD etc.) is now active between the local ESP proxy and the partner ESP master.


4314I XCF transmitter ended, Service=xxxx, Partner=yyyy Explanation: The local ESP proxy's XCF connection with the ESP master (XCF member

yyyy) for ESP XCF service xxxx (e.g. TRACKING, DSTRIG, ROUTING, SCOREBD etc.) is closed. This happens if one of the following occurs:

464 ESP-5.4-MC-03

- An "XCF STOP SERVICE xxxx" or "XCF P S xxxx" command is issued on either the local ESP proxy or the partner ESP master (XCF member yyyy). - An "XCF PURGE CONNECTION zzzz" or "XCF PURGE CON zzzz" command, where zzzz represents the local connection token for ESP XCF service xxxx is issued on either the local ESP proxy or the partner ESP master (XCF member yyyy). - The XCF service's connection is closed for any other reason.

System Action: If the XCF service is still active on both the local ESP proxy and the partner ESP master after its connection has been closed, a receiver (SCOREBD XCF service) or transmitter (TRACKING, DSTRIG and ROUTING XCF services) is restarted after a few seconds.


4315I XCF status update resumed, probable main task normal execution Explanation: XCF status monitoring is active for the local ESP subsystem, i.e. the

SYSPLEX statement in the ESPPARM file specifies the INTERVAL(xxxx) keyword operand, where xxxx specifies a value in seconds within the range 3-86400). An XCF status update missing condition was previously reported by the local ESP, but status updating has now resumed. A possible ESP main task loop or hang appears to be resolved.


4316I XCF status update missing, possible main task loop or hang Explanation: XCF status monitoring is active for the local ESP subsystem, i.e. the

SYSPLEX statement in the ESPPARM file specifies the INTERVAL(xxxx) keyword operand, where xxxx specifies a value in seconds within the range 3-86400). The local ESP has not updated its XCF status-monitoring field for at least xxxx*2 seconds. This may indicate either a loop or hang in the local ESP's main task. Note that this message does not necessarily indicate a problem with ESP. For example, the system that it is running under may be heavily loaded and MVS may not be dispatching ESP. It may be also be possible that MVS is malfunctioning in some way.

System Action: Processing continues. User Response: Attempt to determine the cause of the failed XCF status monitoring

update. If it is determined that ESP is either looping or hung, then cancel it with a dump and call Cybermation support.

4318I XCF status update resumed, Member=xxxx, Group=yyyy, System=zzzz Explanation: XCF member xxxx has resumed updating its XCF status-monitoring field

after a status update missing condition had previously been reported by XCF (MVS) to the local ESP. A possible loop or hang in XCF member xxxx appears to have been resolved. yyyy specifies the joined XCF group and zzzz specifies the local MVS system in the sysplex.


Messages and Codes

ESP-5.4-MC-03 465

4319E XCF Member=xxxx incorrectly set to ESP master, ESP master is Member=yyyy

Explanation: The local ESP has been notified that XCF member xxxx has been set to the ESP master. However, an ESP master already exists (XCF member yyyy). This condition is unlikely to occur, but may if 2 ESPs are set to the master at almost exactly the same time.

System Action: The local ESP considers XCF member yyyy, not xxxx, to be the ESP master. Processing continues.

User Response: Verify that all ESPs in the XCF group recognize the same XCF member as the ESP master by enter the following command on each ESP: XCF DISPLAY GROUP or XCF D G If any discrepancy exists, stop any ESP considered to be the master by any other ESP. Then restart the ESPs, specifying unambiguously which one is to be the master. This can be done with a "TRACKOPT MASTER" statement in the ESPPARM file of the desired ESP master.

4320W Stopped ESP master hold time has expired, Member=xxxx Explanation: An ESP master (XCF member xxxx) was previously stopped specifying a

hold time with a "SHADOW SHUTDOWN HOLD(yyyy)" command, where yyyy specifies a hold time value in minutes within the range 1-1440. No other ESP master has since been started. The local ESP, a shadow manager, has determined that the ESP master hold time has expired and it (the shadow manager) is now ready to assume the role of the ESP master.

System Action: Processing continues. User Response: Either start a new ESP master, or request that the local ESP or

another active ESP shadow manager take over as the ESP master with the following command, issued from any ESP in the XCF group: XCF SET MEMBER xxxx MASTER or XCF T M xxxx M where xxxx is the XCF member name of the active ESP shadow manager being set to the ESP master. Or issue the following command from the ESP shadow manager that will take over as the ESP master: SHADOW ASSUMEPRIMARY or SHAD A

4321E Invalid XCF signal code xxxx received from member yyyy Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4322E XCF SET MEMBER option missing Explanation: Response to "XCF SET MEMBER xxxx" or "XCF T M xxxx" command, where

xxxx is the target XCF member of the command. The "XCF SET MEMBER" command must specify MASTER or M. For example: XCF SET MEMBER ESP001 MASTER

466 ESP-5.4-MC-03

where ESP001 is the XCF member name of the ESP shadow manager being set to the master.

System Action: Processing continues. User Response: Re-enter the command specifying MASTER or M.

4323E XCF member xxxx not active Explanation: Response to "XCF SET MEMBER xxxx" or "XCF T M xxxx" command, where

xxxx is the target XCF member of the command. System Action: Processing continues. User Response: To display the current XCF group members, enter the command:

XCF DISPLAY GROUP or XCF D G Then, if necessary, re-enter the command specifying an ESP subsystem active XCF member.

4324E XCF member xxxx not an ESP subsystem Explanation: Response to "XCF SET MEMBER xxxx" or "XCF T M xxxx" command, where

xxxx is the target XCF member of the command. XCF member xxxx is not an ESP subsystem and therefore cannot be set to the ESP master.

System Action: Processing continues. User Response: To display the current XCF group members, enter the command:

XCF DISPLAY GROUP or XCF D G The "ESP" field in the response specifies "Master" for an ESP master, "Proxy" for an ESP proxy, "Shadow" for an ESP shadow manager, and "Unknown" for an ESP that is neither the master, nor a proxy, nor a shadow manager. Then, if necessary, re-enter the command specifying an (active XCF member) ESP proxy, ESP shadow manager, or unknown ESP.

4325W XCF member xxxx is already the ESP master Explanation: Response to "XCF SET MEMBER xxxx MASTER" or "XCF T M xxxx M" command,

where xxxx is the target XCF member of the command. System Action: Processing continues. User Response: None.

4326E XCF member xxxx is not an ESP shadow manager Explanation: Response to "XCF SET MEMBER xxxx MASTER" or "XCF T M xxxx M" command. System Action: None. User Response: To display the current XCF group members, enter the command:

XCF DISPLAY GROUP or XCF D G The "ESP" field in the response specifies "Master" for an ESP master, "Proxy" for an ESP proxy, "Shadow" for an ESP shadow manager, and "Unknown" for an ESP that is neither the master, nor a proxy, nor a shadow manager. Then, if necessary, re-enter the command specifying an (active XCF member) ESP shadow manager to be set to the ESP master.

Messages and Codes

ESP-5.4-MC-03 467

4328I XCF member xxxx set to ESP master Explanation: Response to "XCF SET MEMBER xxxx MASTER" or "XCF T M xxxx M" if target

XCF member xxxx is the local XCF member and is an ESP shadow manager. System Action: The local ESP shadow manager becomes the master. User Response: None.

4329I Set to ESP master request sent to member xxxx Explanation: Response to "XCF SET MEMBER xxxx MASTER" or "XCF T M xxxx M" command

if target XCF member xxxx is not the local XCF member and is an ESP shadow manager.

System Action: The command is transmitted to and processed by target XCF member xxxx.

User Response: To verify that the target ESP shadow manager was set to the master as requested, enter the command: XCF DISPLAY GROUP or XCF D G and check the "ESP" field of the target XCF member.

4330W XCF member xxxx not set to ESP master, ESP master {is XCF member yyyy|already set}

Explanation: Response to "XCF SET MEMBER xxxx MASTER", "XCF T M xxxx M", "TRACKOPT MASTER", "SHADOW ASSUMEPRIMARY" or "SHAD A" command, where yyyy is the XCF member name of the ESP master and xxxx is the target XCF member of the command. Only one XCF master is permitted in an ESP XCF group.

System Action: Processing continues. User Response: If it is necessary to make XCF member xxxx the ESP master, then:

If the ESP master was unknown during the attempt to set the local ESP to the master, then issue the following command to determine the current ESP master: XCF DISPLAY GROUP or XCF D G Assuming there still is an ESP master and its XCF member name is yyyy, then stop it with the following command: XCF STOP MEMBER yyyy or XCF P M yyyy Re-issue the command to set XCF member xxxx to the ESP master.

4331W XCF status update missing, Member=xxxx, Group=yyyy, System=zzzz Explanation: The local ESP (member xxxx in XCF group yyyy on MVS system zzzz) has

been notified by XCF (MVS) that another ESP member of the XCF group has failed to update its XCF status monitor interval field, and therefore may be looping or hung.


468 ESP-5.4-MC-03

User Response: To determine the job name and subsystem identifier of XCF member xxxx that has failed to update its XCF status monitor interval field, enter the command: XCF DISPLAY GROUP or XCF D G and check the "Jobname" and "SSID" fields of XCF member xxxx. Then attempt to determine the cause of the failed XCF status monitoring update. If the ESP is either looping or hung, then cancel it with a dump and call Cybermation support.

4333W SHADGOAL xxxx only valid in shadow mode, ignored Explanation: A SHADGOAL command was issued, but the system is not in shadow mode. System Action: The command is ignored. User Response: None.

4335I XCF receiver started, Service=TRACKING, Partner=xxxx Explanation: An ESP proxy system's TRACKING XCF service has connected to the local

ESP master. XCF job tracking between the local ESP master and the partner ESP proxy (XCF member xxxx) is now active.


4336I XCF receiver ended, Service=TRACKING, Partner=xxxx Explanation: An ESP proxy system's TRACKING XCF service connection to the local ESP

master has been closed. XCF job tracking between the local ESP master and the partner ESP proxy (XCF member xxxx) is no longer active. This happens if the XCF TRACKING service is stopped on either the local ESP master or the partner ESP proxy, or if the partner ESP proxy is shut down.


4337W XCF receiver waiting for CKPT file space, Service=TRACKING, Partner=xxxx

Explanation: The local ESP master's checkpoint file is full, i.e. cannot accommodate any job tracking records transmitted from the partner ESP proxy (XCF member xxxx).

System Action: The local ESP master's XCF TRACKING receiver waits for checkpoint space to become available while other processing continues.

User Response: Ensure that the local ESP master's tracking processor is active.

4338I XCF receiver resumed, CKPT file space available, Service=TRACKING, Partner=xxxx

Explanation: The local ESP master's checkpoint file was previously full, i.e. did not have sufficient space to accommodate any job tracking records transmitted from the partner ESP proxy (XCF member xxxx). This condition has now been resolved and the partner ESP proxy has resumed transmitting job-tracking records via XCF to the local ESP master.


Messages and Codes

ESP-5.4-MC-03 469


4340I XCF receiver started, Service=DSTRIG, Partner=xxxx Explanation: An XCF proxy system's DSTRIG XCF service has connected to the local

ESP master. XCF data set triggering between the local ESP master and the partner ESP proxy (XCF member xxxx) is now active.


4341I XCF receiver ended, Service=DSTRIG, Partner=xxxx Explanation: An ESP proxy system's DSTRIG XCF service connection to the local ESP

master has been closed. XCF data set triggering between the local ESP master and the partner ESP proxy (XCF member xxxx) is no longer active. This happens if the XCF DSTRIG service is stopped on either the local ESP master or the partner ESP proxy is stopped, or if the partner ESP proxy is shut down.


4342W XCF receiver waiting for CKPT file space, Service=DSTRIG, Partner=xxxx Explanation: The local ESP master's checkpoint file is full, i.e. cannot

accommodate any data set triggering records transmitted from the partner ESP proxy (XCF member xxxx).

System Action: The local ESP master's XCF DSTRIG receiver waits for checkpoint space to become available while other processing continues.

User Response: Most of the records on the ESP master checkpoint file are usually job tracking records. Therefore ensure that the local ESP master's tracking processor is active.

4343I XCF receiver resumed, CKPT file space available, Service=DSTRIG, Partner=xxxx

Explanation: The local ESP master's checkpoint file was previously full, i.e. did not have sufficient space to accommodate any data set triggering records transmitted from the partner ESP proxy (XCF member xxxx). This condition has now been resolved and the partner ESP proxy has resumed transmitting data set triggering records via XCF to the local ESP master.


4345I XCF receiver started, Service=ROUTING, Partner=xxxx Explanation: An ESP proxy system's ROUTING XCF service has connected to the local

ESP master. XCF subsystem request routing between the local ESP master and the partner ESP proxy (XCF member xxxx) is now active.


4346I XCF receiver ended, Service=ROUTING, Partner=xxxx Explanation: An ESP proxy system's ROUTING XCF service connection to the local ESP

470 ESP-5.4-MC-03

master has been closed. XCF subsystem request routing between the local ESP master and the partner ESP proxy (XCF member xxxx) is no longer active. This happens if the XCF ROUTING service is stopped on either the local ESP master or the partner ESP proxy is stopped, or if the partner ESP proxy is shut down.


4347E XCF receiver buffer length xxxx too small for IAR, Service=ROUTING, Partner=yyyy


4348E XCF receiver buffer xxxx invalid, Service=ROUTING, Partner=yyyy Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4349E High Availability Option or High Performance Option not installed Explanation: A command was issued from an ESP client (ESP/WM TSO/ISPF user or ESP

Work Station Server) to an ESP/WM proxy subsystem with ROUTING set to MASTER. However, the target ESP/WM proxy subsystem does not have the High Availability Option (HAO) or High Performance Option (HPO) installed, and therefore cannot route the command to the ESP/WM master subsystem in its XCF group.

System Action: The command is ignored. User Response: This message should not normally appear, as an ESP client is able to

determine if the ESP/WM proxy subsystem it is connected to has the High Availability Option (HAO) or High Performance Option (HPO) installed, and will not attempt to route a subsystem request to the ESP/WM master if the local ESP/WM proxy is not authorized to do so. There may be a mismatch between the version of the ESP client and the ESP/WM proxy subsystem it is connected to. If unable to determine the problem, contact Cybermation support.

4350E XCF response xxxx invalid, Service=TRACKING Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4351W XCF proxy->master TRACKING service suspended, ESP master CKPT file full

Explanation: The ESP master's checkpoint file is full, i.e. cannot accommodate any Job-tracking records transmitted from the local ESP proxy.

System Action: The local ESP proxy's XCF TRACKING transmitter waits for a request from the ESP master to re-transmit the job tracking record(s).

User Response: Ensure that the ESP master's tracking processor is active.

Messages and Codes

ESP-5.4-MC-03 471

4352I XCF proxy->master TRACKING service resumed Explanation: The ESP master's checkpoint file was previously full, i.e. did not

have sufficient space to accommodate any job tracking records transmitted by the local ESP proxy. This condition has now been resolved and the local ESP proxy has resumed transmitting job tracking records via XCF to the ESP master.


4353E xxxx byte core request failed for XCF response IAR and IAE, Request=yyy

Explanation: There is not enough private area virtual storage for the transmission of the response to an ESP Workload Manager subsystem request issued from an ESP Workload Manager master to an ESP Workload Manager proxy via the XCF ROUTING service. xxxx specifies the number of bytes required for the response to the subsystem request. yyy specifies the subsystem request function code.

System Action: The ESP Workload Manager master sends error response message 4354E to to the issuer of the subsystem request.

User Response: If the problem persists, recycle the ESP Workload Manager master with a larger region size.

4354E Request RC=xxx, Insufficient core for yyyy byte response Explanation: An ESP Workload Manager subsystem request was issued to an ESP Workload

Manager master to an ESP Workload Manager proxy via the XCF ROUTING service. The subsystem request was processed but there was not enough virtual storage in the remote ESP Workload Manager's address space private area for the the response to be transmitted to the local requesting ESP Workload Manager proxy. xxx specifies the return code of the subsystem request. yyyy specifies the number of bytes required for the response to the subsystem request.

System Action: Processing continues. User Response: If the problem persists, recycle the ESP Workload Manager master with a larger

a larger region size.

4355E XCF response xxxx invalid, Service=DSTRIG Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4356W XCF proxy->master DSTRIG service suspended, ESP master CKPT file full Explanation: The ESP master's checkpoint file is full, i.e. cannot accommodate any

data set triggering records transmitted from the local ESP proxy. System Action: The local ESP proxy's XCF DSTRIG transmitter waits for a request from

472 ESP-5.4-MC-03

the ESP master to re-transmit the data set triggering record(s). User Response: Most of the records on the ESP master checkpoint file are usually job

tracking records. Therefore ensure that the ESP master's tracking processor is active.

4357I XCF proxy->master DSTRIG service resumed Explanation: The ESP master's checkpoint file was previously full, i.e. did not

have sufficient space to accommodate any data set triggering records transmitted by the local ESP proxy. This condition has now been resolved and the local ESP proxy has resumed transmitting data set triggering records XCF to the ESP master.


4360E XCF ROUTING invalid, local ESP not master or proxy Explanation: The local ESP has been requested to route ESP subsystem requests to

the ESP master in the XCF group, but (the local ESP) is neither a master nor a proxy. This should never happen.

System Action: The ROUTING XCF service is stopped if it is active. User Response: Call Cybermation support.

4362W Local ESP XCF ROUTING service {suspended|not active} Explanation: A command was entered from an ESP client (TSO, ISPF or workstation

server) connected to an ESP proxy. The client has been set to instruct the connected ESP proxy to route ESP subsystem requests to the ESP master (via the MASTER operand of the ESP command or the "ROUTING MASTER" ESP subcommand). However, the ESP proxy cannot route the command to the ESP master because its XCF ROUTING service is eiher suspended or not active.

System Action: Processing continues. User Response: First enter the following command:

ROUTING LOCAL or ROUTING L This instructs the connected ESP proxy to process ESP subsystem requests locally rather than route them to the ESP master. Then enter the following command: XCF START SERVICE ROUTING or XCF S S ROUTING This starts the connected ESP proxy's XCF ROUTING service. Then enter the following command: ROUTING MASTER or ROUTING M This instructs the connected ESP proxy to route ESP subsystem requests to the ESP master. Then re-enter the original command.

4363W ESP master XCF ROUTING service not active Explanation: A command was entered from an ESP client (TSO, ISPF or workstation

server) connected to an ESP proxy. The client has been set to instruct

Messages and Codes

ESP-5.4-MC-03 473

the connected ESP proxy to route ESP subsystem requests to the ESP master (via the MASTER operand of the ESP command or the "ROUTING MASTER" ESP subcommand). However, the ESP proxy cannot route the command to the ESP master because its (the ESP master's) XCF ROUTING service is not active or not registered.

System Action: Processing continues. User Response: Issue the following command to the ESP master, either from an ESP

client connected DIRECTLY to the master or via the MVS MODIFY command: XCF START SERVICE ROUTING or XCF S S ROUTING If message 4248 appears, the XCF ROUTING service was not registered by the ESP master. In this event, the following statement must be added to the ESPPARM statement of the ESP master: XCF START SERVICE ROUTING or XCF S S ROUTING Then the ESP master must be recycled.

4364W ESP master not active Explanation: A command was entered from an ESP client (TSO, ISPF or workstation

server) connected to an ESP proxy. The client has been set to instruct the connected ESP proxy to route ESP subsystem requests to the ESP master (via the MASTER operand of the ESP command or the "ROUTING MASTER" ESP subcommand). However, the ESP master is not active, i.e. no active ESP master has joined the same XCF group as the connected ESP proxy.

System Action: Processing continues. User Response: Start an ESP master that includes in its ESPPARM file both a SYSPLEX

statement that specifies the same GROUP as the SYSPLEX statement of the connected ESP proxy, and an "XCF START SERVICE ROUTING" or "XCF S S ROUTING" statement.

4365W XCF connection to ESP master closed, Service=ROUTING Explanation: A command was entered from an ESP client (TSO, ISPF or workstation

server) connected to an ESP proxy. The client has been set to instruct the connected ESP proxy to route ESP subsystem requests to the ESP master (via the MASTER operand of the ESP command or the "ROUTING MASTER" ESP subcommand). The XCF connection between the ESP proxy and master was closed by the master while processing the command. This happens when, under the above circumstances, the ESP master is stopped via an "XCF STOP MEMBER", "XCF P M", "XCF STOP MEMBER xxxx", or "XCF P M xxxx" command, where xxxx is the XCF member name of the ESP master.

System Action: Processing continues. User Response: To instruct the connected ESP proxy to process subsystem requests

itself rather than attempt to route them to the ESP master, enter the following ESP subcommand from the ESP client: ROUTING LOCAL or ROUTING L If it is necessary for the ESP proxy to route subsystem requests to the ESP master, restart the ESP master and its XCF ROUTING service.

4366E XCF response xxxx invalid, Service=ROUTING Explanation: Internal logic error. Should never happen. System Action: Processing continues.

474 ESP-5.4-MC-03


4367I XCF transmitter started, Service=SCOREBD, Partner=xxxx Explanation: A remote ESP proxy's XCF SCOREBD service receiver has connected to

the local ESP master's XCF SCOREBD service transmitter. This occurs when both the local ESP master's and the remote ESP proxy's XCF SCOREBD service has been started by an "XCF START SERVICE SCOREBD" command. The ESP master's scoreboard will henceforth be mirrored in the remote ESP proxy where it can be directly viewed by TSO users and work station servers connected to the ESP proxy via the subsystem interface. The remote ESP is joined to ESP's XCF group as member xxxx.


4368I XCF transmitter ended, Service=SCOREBD, Partner=xxxx Explanation: The local ESP master's XCF SCOREBD service transmitter's connection

with a remote ESP proxy's XCF SCOREBD service receiver has been closed. This occurs when an "XCF STOP SERVICE SCOREBD" or an "XCF PURGE SERVICE SCOREBD" command is issued on either the local ESP master or the remote ESP proxy. The remote ESP proxy's copy of the scoreboard is flushed. The scoreboard cannot be directly viewed by TSO users and work station servers connected to the remote ESP proxy via the subsystem interface until the XCF SCOREBD service connection is re-established. This occurs when the XCF SCOREBD service becomes active on both the local ESP master and the remote ESP proxy. The remote ESP is joined to ESP's XCF group as member xxxx.


4369E XCF SCOREBD data received invalid, Length=xxxx, Data='yyyy', Partner=zzzz

Explanation: The local ESP proxy's XCF SCOREBD service receiver has received invalid data from the ESP master. xxxx specifies the length of the received data and yyyy specifies the first 24 bytes of the received data in hexadecimal. zzzz is the ESP master's XCF member name. This condition should never happen.

System Action: The XCF connection is closed and the XCF SCOREBD service is stopped on the local ESP proxy.

User Response: Attempt to re-establish the XCF SCOREBD service connection by issuing the "XCF START SERVICE SCOREBD" command on the local ESP proxy. If this does not resolve the problem, call Cybermation support.

4370S Invalid shadow manager function code xxxx Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

Messages and Codes

ESP-5.4-MC-03 475

4371I Entering shadow mode Explanation: The local ESP has been started as an XCF shadow manager. System Action: The local ESP shadow manager waits for a command to take over as the

ESP master in the XCF group, or to terminate. User Response: The local ESP shadow manager can be set to the ESP master with one of

the following commands: XCF SET MEMBER xxxx MASTER from any ESP in the XCF group or XCF T M xxxx M from any ESP in the XCF group or SHADOW ASSUMEPRIMARY from the local ESP shadow or SHAD A from the local ESP shadow or SHADOW SHUTDOWN RELINQUISH(xxxx) from the ESP master or SHAD SH R(xxxx) from the ESP master SHADOW TAKEOVER from the local ESP shadow or SHAD T from the local ESP shadow or where xxxx is the XCF member name of the local ESP shadow manager

4372I Exiting shadow mode Explanation: The local ESP has changed its status from shadow manager to master. System Action: The local ESP completes initialization and runs as the master in the

XCF group. User Response: None.

4373E SHADOW TAKEOVER only valid in shadow mode Explanation: Response to "SHADOW TAKEOVER", "SHAD T", "SHADOW

ASSUMEPRIMARY" or "SHAD A" command. The local ESP is already the master (primary ESP) in the XCF group. Therefore setting to the master is invalid. The above commands may only be issued from an ESP shadow manager.


4374I Shadow manager assuming ESP master (primary) role Explanation: Response to "SHADOW TAKEOVER", "SHAD T", "SHADOW

ASSUMEPRIMARY" or "SHAD A" command. The local ESP shadow manager has become the master in the XCF group.

System Action: The local ESP completes initialization and runs as the master in the XCF group.


4375E {HOLD|RELINQUISH} option invalid for SHADOW LIST Explanation: Response to "SHADOW LIST", "SHAD L", "SHADOW STATUS", "SHAD ST",

"SHADOW" or "SHAD" command. System Action: Processing continues. User Response: Re-enter the "SHADOW LIST", "SHAD L", "SHADOW STATUS", "SHAD ST",

"SHADOW" or "SHAD" command without the HOLD or RELINQUISH option.

476 ESP-5.4-MC-03

4376E SHADOW SHUTDOWN option {HOLD|RELINQUISH} only valid for ESP master

Explanation: Response to "SHADOW SHUTDOWN HOLD", "SHADOW SHUTDOWN RELINQUISH", "SHAD SH H" or "SHAD SH R" command issued from an ESP shadow manager.


4377E Command syntax invalid Explanation: A syntax error was encountered in a command issued on an ESP shadow

manager. System Action: Processing continues. User Response: If necessary, enter a valid ESP shadow manager command.

4378E Command xxxx not found Explanation: Command xxxx issued from an ESP shadow manager is not valid. System Action: Processing continues. User Response: If necessary, enter a valid ESP shadow manager command.

4379S Error obtaining a command, RC=nn Explanation: An unexpected error occurred while the shadow manager was attempting

to obtain a command. System Action: The command thread terminated. User Response: Contact Cybermation support.

4380I SHADOW Command Options Explanation: Response to "SHADOW HELP" or "SHAD H" command. System Action: Processing continues. User Response: None.

4381I SHADGOAL Command Options Explanation: Response to "SHADGOAL HELP" command. System Action: Processing continues. User Response: None.

4382I No shadow goals defined Explanation: Response to "SHADGOAL" or "SHADGOAL LIST" command. System Action: Processing continues. User Response: None.

4383I Shadow goal definitions Explanation: Response to "SHADGOAL" or "SHADGOAL LIST" command. System Action: Processing continues. User Response: None.

4384E Shadow goal action(s) not specified Explanation: Response to "SHADGOAL" command.

Messages and Codes

ESP-5.4-MC-03 477

An ESP shadow manager shadow goal was defined without specifying any actions to take after the ESP master terminates. Shadow goal actions are specified by the following SHADGOAL command keywords: COMMAND(xxxx), TAKEOVER, TRIGGER(yyyy), WARN xxxx is an OS/390 system command. yyyy is an ESP event identifier.

System Action: Processing continues. User Response: Respecify the SHADGOAL command with at least one action keyword.

Note that TAKEOVER and TRIGGER are mutually exclusive.

4385I Route subsystem requests to {ESP master|local ESP} Explanation: Response to "ROUTING MASTER", "ROUTING M", "ROUTING LOCAL" or

"ROUTING L" command. System Action: Processing continues. User Response: None.

4386W Local ESP XCF SCOREBD service not active Explanation: A TSO/ISPF user connected to an ESP proxy via the MVS subsystem

interface is attempting to view the ESP scoreboard under the Consolidated Status Facility (CSF). However, the local ESP proxy's XCF SCOREBD service is not active, and therefore not receiving scoreboard data from the ESP master.

System Action: Processing continues. User Response: If running under an ESP client (TSO, ISPF, Work Station etc.), issue

the "ROUTING" command. If commands are being routed to the ESP master, issue a "ROUTING LOCAL" command. Start the local ESP proxy's XCF SCOREBD service with an "XCF START SERVICE SCOREBD" command. If commands were being routed to the ESP master, restore this condition with a "ROUTING MASTER" command.

4387W ESP master XCF SCOREBD service not active Explanation: A TSO/ISPF user connected to an ESP proxy via the MVS subsystem

interface is attempting to view the ESP scoreboard under the Consolidated Status Facility (CSF). However, the ESP master's XCF SCOREBD service is not active. Therefore the local ESP proxy cannot access the scoreboard.

System Action: Processing continues. User Response: Start the ESP master's XCF SCOREBD service with an "XCF START SERVICE

SCOREBD" command. This command can be issued by an ESP client (TSO, ISPF, Work Station etc.) connected to an ESP proxy via the MVS subsystem interface, provided the ESP proxy has an active XCF ROUTING connection to the ESP master, and ESP subsystem commands are being routed to the ESP master. To determine if ESP subsystem commands are being routed to the ESP master, issue a "ROUTING" command. To route ESP subsystem commands to the ESP master, issue a "ROUTING MASTER" command.

4388W ESP master not active Explanation: A TSO/ISPF user connected to an ESP proxy via the MVS subsystem

interface is attempting to view the ESP scoreboard under the

478 ESP-5.4-MC-03

Consolidated Status Facility (CSF). However, the ESP master is not active. Therefore there is no scoreboard.

System Action: Processing continues. User Response: Start the ESP master and ensure that the XCF SCOREBD service is

started via an "XCF START SERVICE SCOREBD" command on both the ESP master and the local ESP proxy subsystems.

4389C ROUTING Command Options Explanation: Response to ROUTING HELP command. System Action: Displays ROUTING command options. User Response: None.

4390I Master fail|leave|quiesce shadow goal, After xxxx seconds{, Warn}{, Command('yyyy')}{, Takeover|Trigger(zzzz)}

Explanation: Response to "SHADGOAL MASTER(FAIL|LEAVE|QUIESCE)" shadow goal definition command. The shadow goal has been successfully defined. xxxx specifies the time in seconds to wait after the ESP master termination event occurs. yyyy specifies an MVS command to issue xxxx seconds after the shadow goal ESP master termination event has occurred. zzzz specifies an ESP event to trigger xxxx seconds after the shadow goal ESP master termination event has occurred and after the local shadow manager has taken over as the ESP master.


4391W Master fail|leave|quiesce shadow goal not defined Explanation: Response to "SHADGOAL DELETE MASTER(FAIL|LEAVE|QUIESCE)" command.

An attempt has been made to delete a shadow goal, which has either not been previously defined or has already been deleted.


4392I Master fail|leave|quiesce shadow goal deleted Explanation: Response to "SHADGOAL DELETE MASTER(FAIL|LEAVE|QUIESCE)" command.

The specified shadow goal has been successfully deleted. System Action: Processing continues. User Response: None.

4393E xxxx option invalid for SHADGOAL yyyy Explanation: Operand xxxx is invalid when operand yyyy is specified in the SHADGOAL

command. System Action: Processing continues. User Response: If necessary, re-issue the SHADGOAL command with valid operands.

For a list of valid SHADGOAL command options, enter: SHADGOAL HELP

Messages and Codes

ESP-5.4-MC-03 479

4394E SHADGOAL xxxx option missing Explanation: A SHADGOAL command was issued with an option that requires that

operand xxxx be specified. However it (operand xxxx) was omitted. System Action: Processing continues. User Response: If necessary, re-issue the SHADGOAL command with valid operands.

For a list of valid SHADGOAL command options, enter: SHADGOAL HELP

4395I Master fail|leave|quiesce shadow goal {takeover complete|event xxxx triggered}

Explanation: The ESP master has terminated and the local shadow manager's shadow goal for the specified master termination state (fail, leave or quiesce) has been activated. The shadow manager has subsequently taken over as the ESP master and, if specified in the shadow goal, triggered an ESP event.


4396I Master fail|leave|quiesce shadow goal activated, ESP master ended, Member=xxxx, Group=yyyy

Explanation: The ESP master has terminated and the local ESP shadow manager's shadow goal for the specified master termination state (fail, leave or quiesce) has been activated. The shadow goal specified a non-zero interval to wait (via the AFTER operand of the SHADGOAL command). xxxx and yyyy specify the XCF group and member names respectively of the ESP master subsystem.

System Action: The shadow goal action(s) will execute after the interval specified by the AFTER operand of the SHADGOAL command expires.


4397W ESP master in failed|undefined|quiesced state {for xxxx seconds} Explanation: The ESP master has terminated and the local shadow manager's shadow

goal for the specified master termination state (fail, leave or quiesce) has been activated. The WARN option was specified in the SHADGOAL command for the active shadow goal. This results in the above message.

System Action: If the active shadow's SHADGOAL command specified either the TAKEOVER or TRIGGER(yyyy) operands, the local shadow manager takes over as the ESP master. If the active shadow's SHADGOAL command specified the TRIGGER(yyyy) operand, event yyyy is triggered after it (the local shadow manager) takes over as the ESP master. If the active shadow's goal's SHADGOAL command specified neither the TAKEOVER nor the TRIGGER(yyyy) operands, processing continues.

User Response: If the local shadow manager's shadow goal has specified that it takeover as the ESP master (via the TAKEOVER or TRIGGER(yyyy) operands of the SHADGOAL command), probably no response is required. If the local shadow manager's shadow goal has not specified that it takeover as the ESP master, then probably either the ESP master

480 ESP-5.4-MC-03

should be restarted, or the local shadow manager should be explicitly requested to takeover as the ESP master (for example via the "XCF SET MEMBER zzzz MASTER" command, where zzzz is the XCF member name of the local shadow manager).

4398W Master fail|leave|quiesce shadow goal command 'xxxx' issued Explanation: The ESP master has terminated and the local shadow manager's shadow

goal for the specified master termination state (fail, leave or quiesce) has been activated. The COMMAND('xxxx') option was specified in the SHADGOAL command for the active shadow goal. 'xxxx' has just been issued as an MVS command.

System Action: If the active shadow's SHADGOAL command specified either the TAKEOVER or TRIGGER(yyyy) operands, the local shadow manager takes over as the ESP master. If the active shadow's goal's SHADGOAL command specified the TRIGGER(yyyy) operand, event yyyy is triggered after it (the local shadow manager) takes over as the ESP master. If the active shadow's SHADGOAL command specified neither the TAKEOVER nor the TRIGGER(yyyy) operands, processing continues.

User Response: Depends on what command 'xxxx' was issued and whether or not the local shadow manager's shadow goal specified that it takeover as the ESP master (via the TAKEOVER or TRIGGER(yyyy) operands of the SHADGOAL command). If the local shadow manager has not taken over as the ESP master, then probably either the ESP master should be restarted, or the local shadow manager should be explicitly requested to takeover as the ESP master (for example via the "XCF SET MEMBER zzzz MASTER" command, where zzzz is the XCF member name of the local shadow manager).

4399W Master fail|leave|quiesce shadow goal cancelled, ESP master started, Member=xxxx, Group=yyyy

Explanation: An ESP master has been started externally while the local ESP shadow manager had an active shadow goal. The shadow goal is cancelled. xxxx and yyyy specify the XCF group and member names respectively of the ESP master subsystem.

System Action: The local ESP shadow manager monitors the new ESP master for its termination so that it (the shadow manager) can respond according to its shadow goals.


4400S WLMCMD command code xxxx invalid Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4401E WLM command missing Explanation: A WLM command was issued with no operands. System Action: Processing continues. User Response: For a list of valid WLM command options, enter:

WLM HELP or

Messages and Codes

ESP-5.4-MC-03 481

WLM H or WLM ?

4402E WLM xxxx command invalid Explanation: A WLM command was issued with an invalid option xxxx. System Action: Processing continues. User Response: For a list of valid WLM command options, enter:

WLM HELP or WLM H or WLM ?

4403E WLM xxxx not an initialization command Explanation: A WLM statement in the ESPPARM file specifies option xxxx, which is

invalid at initialization. System Action: ESP action message 802A is issued to prompt for an END (to ignore the

"WLM xxxx" statement) or a CANCEL (to terminate ESP) response. User Response: Respond to action message 802A and remove erroneous "WLM xxxx"

statement from ESPPARM file.

4404E WLM xxxx object missing Explanation: The WLM command with option xxxx requires one or more additional

operands. System Action: Processing continues. User Response: For a list of valid WLM command options, enter:


4405E WLM xxxx object yyyy invalid Explanation: The WLM command with option xxxx specified an invalid option yyyy. System Action: Processing continues. User Response: For a list of valid WLM command options, enter:


4406I WLM Command Options Explanation: Response to "WLM HELP", "WLM H" or "WLM ?" command. System Action: Processing continues. User Response: None.

4407S XENCLAVE function code xxxx invalid Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4408E XENCLAVE <function>, <error_description> Explanation: An internal Cybermation API request for a WLM enclave service has

482 ESP-5.4-MC-03

resulted in an error condition. Internal logic error. Should not happen.


4409S XENCLAVE <function>, <error_description> Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4410W IWM{CONN|DISC|ECREA|EDELE|EJOIN|ELEAV|RESET|WMCON| WSYSQ}{,{Return=<number>| Reason=<hex_value>|<reason_description>}} {,SST=<subsystem_type>} {, SSN=<subsystem_name>} {,APPLENV=<applenv_name>}{, Tasks=<work_processor_task_count} {,UI=<userid>}{, TC=<trxclass>} {, TN=<trxname>} {,SPM=<subsystem_parameter>}{, Jobname=<jobname>}{, ASID=<asid>} {,Perform=<pgn>}{, SrvClass=<srvclass>}{, Function=<Quiesce|Resume>} {,Userid=<userid>}

Explanation: A warning message describing the result of an API call to WLM. System Action: Processing continues. User Response: None.

4411E IWM{CONN|DISC|ECREA|EDELE|EJOIN|ELEAV|RESET|WMCON|WSYSQ} {,{Return=<number>| Reason=<hex_value>|<reason_description>}} {,SST=<subsystem_type>} {, SSN=<subsystem_name>} {,APPLENV=<applenv_name>}{, Tasks=<work_processor_task_count} {,UI=<userid>}{, TC=<trxclass>} {, TN=<trxname>} {,SPM=<subsystem_parameter>}{, Jobname=<jobname>}{, ASID=<asid>} {,Perform=<pgn>}{, SrvClass=<srvclass>}{, Function=<Quiesce|Resume>} {,Userid=<userid>}

Explanation: An error message describing the result of an API call to WLM. System Action: Processing continues. User Response: Usually none. The content of the message may indicate a specific

action. If a problem arises, call Cybermation support.

4412I WLM DISPLAY CONNECTION Explanation: Response to "WLM DISPLAY CONNECTION" or "WLM D C" command.

Displays workload manager (WLM) connection information. System Action: Processing continues. User Response: None.

4425W Not connected to workload manager Explanation: A WLM command was issued on a Cybermation product that has not

connected to the MVS workload manager (WLM). System Action: Processing continues. User Response: Under ESP, issue a WORKMGR operator command to connect to workload

Messages and Codes

ESP-5.4-MC-03 483

manager, or add a WORKMGR statement to the ESPPARM initialization file and recycle the job.

4426S XWLMCONN parameter list not a valid WCRA Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4427S XENCLAVE parameter list not a valid WERA Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4428S XRESET parameter list not a valid WRRA Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4430I Connected to WLM, SST=xxxx, SSN=yyyy, Enclave support {en|dis}abled Explanation: Response to "WORKMGR" statement in ESPPARM initialization file or

"WORKMGR" operator command, where xxxx specifies ESP's workload manager subsystem type and yyyy specifies ESP's workload manager subsystem name. ESP has connected to OS/390's workload manager (WLM) as a work manager.


4431I IWM{CONN|DISC|ECREA|EDELE|EJOIN|ELEAV|RESET|WMCON| WSYSQ}{,{Return=<number>| Reason=<hex_value>|<reason_description>}} {,SST=<subsystem_type>} {, SSN=<subsystem_name>} {,APPLENV=<applenv_name>}{, Tasks=<work_processor_task_count} {,UI=<userid>}{, TC=<trxclass>} {, TN=<trxname>} {,SPM=<subsystem_parameter>}{, Jobname=<jobname>}{, ASID=<asid>} {,Perform=<pgn>}{, SrvClass=<srvclass>}{, Function=<Quiesce|Resume>} {,Userid=<userid>}

Explanation: An information message describing the result of an API call to WLM. System Action: Processing continues. User Response: None.

4440E {Cannot {QUIESCE|RESET|RESUME} job xxxx, }System yyyy not {found| in goal mode}

Explanation: An attempt was made to quiesce, reset or resume job xxxx on system yyyy that does not exist, or to quiesce or resume job xxxx on system yyyy that is not in WLM goal mode.

System Action: Processing continues. User Response: If unable to determine the cause of the problem, call Cybermation

support.

484 ESP-5.4-MC-03

4441E XRESET {GETMODE|QUIESCE|RESET|RESUME}, error_reason Explanation: An unsuccessful attempt was made to either obtain the WLM mode of a

system in the sysplex (goal mode or compatibility mode), or to change the status (quiesce, reset or resume) of a job running on a system in the sysplex. error_reason should give a clear explanation of what error condition occured.

System Action: Processing continues. User Response: Attempt to determine the cause of the error from the error_reason

description, and correct it if possible. If unable to determine the cause of the problem or unable to correct it, call Cybermation support.

4442C WLM DISPLAY STATUS Explanation: Response to "WLM DISPLAY STATUS" or "WLM D ST" command issued to a

Cybermation product, e.g. to an ESP subsystem from an ESP work station in line mode or from a TSO/ISPF session in ESP page mode.


4443W System xxxx not {found|in goal mode} Explanation: Response to "WLM DISPLAY SYSTEM xxxx" or "WLM D S xxxx" command issued

to a Cybermation product, e.g. to an ESP subsystem from an ESP work station in line mode or from a TSO/ISPF session in ESP page mode. Target system xxxx is not an active goal mode member of the sysplex.


4444C WLM DISPLAY SYSTEM{S| xxxx} Explanation: Response to "WLM DISPLAY SYSTEMS", "WLM D S",

"WLM DISPLAY SYSTEM xxxx", "WLM D S xxxx" command issued to a Cybermation product, e.g. to an ESP subsystem from an ESP work station in line mode or from a TSO/ISPF session in ESP page mode. xxxx specifies a single system in the sysplex or "ALL".


4446E SYSEVENT REQSRMST Retcode=xxxx Explanation: An unsuccessful attempt was made to obtain Workload Management (WLM)

mode status information from MVS. This should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4447I TOKEN(token) [listid] QNAME(qname) RNAME(rname) SCOPE(scope) CTLTYPE(ctltype) REQTYPE(reqtype) USER(user) LOCKED(time) LASTLOCK(time) [EXPIRY(time)][UNLOCKED(time)]

Explanation: This message reports the status of a CPEENQ lock. The following

Messages and Codes

ESP-5.4-MC-03 485

fields appear: TOKEN Unique token assigned to the CPEENQ lock [listid] Optional text information, if any QNAME ENQ queue name RNAME ENQ resource name SCOPE ENQ scope CTLTYPE ENQ control type (E, S) REQTYPE ENQ request type (USE, etc.) USER Id of the user on whose behalf a CPEENQ lock was obtained LOCKED Time (YYYYMMDD-hhmmss) at which a CPEENQ lock was obtained LASTLOCK Time (YYYYMMDD-hhmmss) at which a CPEENQ lock record was last updated. [EXPIRY] Time (YYYYMMDD-hhmmss), if any, at which a CPEENQ lock is scheduled to expire. [UNLOCKED] Time (YYYYMMDD-hhmmss), if any, at which a CPEENQ was unlocked.

System Action: Processing continues. User Response: If the UNLOCKED time is displayed, then the CPEENQ lock should be

considered as having been terminated.

4448I ENQ's found: nnnn Explanation: When a CPEENQ list request is issued with the TERSE option, this

message shows the number of ENQ's that satisfied the list criteria. System Action: Processing continues. User Response: None.

4449I ENQ's displayed: nnnn Explanation: When a CPEENQ list request is issued without the TERSE option, this

message shows the number of ENQ's that satisfied the list criteria. System Action: Processing continues. User Response: None.

4450I TOTCOUNT(a) CURCOUNT(b) TOTCOUNT_LOCAL(c) CURCOUNT_LOCAL(d) TOTCOUNT_SSR(e) CURCOUNT_SSR(f) TOTCOUNT_REMOTE(g) CURCOUNT_REMOTE(h) EXPIRED(i)

Explanation: When a CPEENQ request is issued with the STATUS option, this message shows CPEENQ status information. The following fields appear: TOTCOUNT(a) Total number of CPEENQ locks obtained since the creation of the address space. CURCOUNT(b) Current number of CPEENQ locks held by the address pace. TOTCOUNT_LOCAL(c) Total number of CPEENQ locks held by the local address space since the creation of the address space.

486 ESP-5.4-MC-03

CURCOUNT_LOCAL(d) Current number of CPEENQ locks held by the local address space. TOTCOUNT_SSR(e) Total number of CPEENQ locks obtained in response to a subsystem request since the creation of the address space. CURCOUNT_SSR(f) Current number of CPEENQ locks obtained in response to a subsystem request. TOTCOUNT_REMOTE(g) Total number of CPEENQ locks obtained in response to a remote subsystem request carried by the Network Delivery Services since the creation of the address space. CURCOUNT_REMOTE(h) Current number of CPEENQ locks obtained in response to a remote subsystem request carried by the Network Delivery Services. EXPIRED(i) Number of CPEENQ locks that expired since the creation of the address space.


4451I --- BUFFERED TRACE MESSAGES ------------- Explanation: When a CPEENQ request is issued with the tracing option enabled,

the title above precedes the listing of the queued trace messages. System Action: Processing continues. User Response: None.

4452I <trace message> Explanation: When a CPEENQ request is issued with the tracing option enabled,

this message contains one of the queued trace messages. System Action: Processing continues. User Response: None.

4453I --- END OF BUFFERED TRACE MESSAGES ----- Explanation: When a CPEENQ request is issued with the tracing option enabled,

this message immediately follows the listing of the queued trace messages.



this is a trace message prepared by program CYBXQ100. System Action: Processing continues. User Response: None.

4455I Lock expired|flushed: USER(user) TOKEN(token) [DEQ_RC(X'hhhhhhhh')] Explanation: A CPEENQ lock expired automatically or was flushed in response to a

flush request. System Action: Processing continues. User Response: None.

Messages and Codes

ESP-5.4-MC-03 487

4456I Response truncated Explanation: The response to a CPEENQ request was truncated because space ran out

in the response block. System Action: Processing continues. User Response: None or retry the request again later. If this persists, please

notify Cybermation.

4457E CYBXQ101 - A subsystem request to NETNODE aaaa failed because of a network problem detected by the Network Delivery Services

Explanation: The Network Delivery Services were unable to route a CPEENQ request to a destination NETNODE and receive the response in a limited time. This message should be preceded by an explanatory message such as 3372 or 3373. The target NETNODE may be disconnected or a time-out may have occurred in the network or in an ESP Workload Manager.

System Action: Processing continues. User Response: Check the previous message. Retrying the request might succeed

if the underlying problem is transitory.

4458E CYBXQ101 - Subsystem error aaaa-bbbb Explanation: A CPEENQ request failed because of an error during the execution of

a subsystem request. aaaa is the value returned in register 15 by program CYBSS005 and bbbb is the value of XSCMRETCD.

System Action: Processing continues. User Response: Look for recent or nearby messages that might account for this error.

Retrying the request might succeed if the underlying problem is transitory.


this is a trace message prepared by program CYBXQ101. System Action: Processing continues. User Response: None.

4460E Error scanning command, RC=nn Explanation: A syntax error has been detected when scanning an input command. System Action: The command is not processed. User Response: System routine IKJPARS returned error code nn.


488 ESP-5.4-MC-03

4461E CPEENQ ERROR: Invalid xxxx specification[: yyyy] Explanation: Argument xxxx in a CPEENQ command contains the invalid value yyyy. System Action: The command is not processed User Response: Re-issue the corrected command.

4462E CPEENQ ERROR: <error message> Explanation: An error occurred during the processing of a CPEENQ command. System Action: Processing continues. User Response: If the syntax of the command is correct, decide how to proceed based

on the error message.

4463I CPEENQ INFO: <informational message> Explanation: This message contains diagnostic information about the outcome of

a CPEENQ command. System Action: Processing continues. User Response: None.

4464I Locks flushed: xxxx Explanation: Indicates the number of CPEENQ locks released in response to a CPEENQ

FLUSHTSK or CPEENQ FLUSHJOB command. System Action: Processing continues. User Response: None.

4500I xxxx {sysout class} {not set|set to y{, active on z} Explanation: Response to a "cccc DISPLAY TRACE" or "cccc D TR" command.

cccc is the command name. xxxx is the sysout log/trace file identifier. y is a sysout class or a sysout DDNAME. z is a sysout class or a sysout DDNAME. Displays the status of a sysout log/trace file.


4501I xxxx {sysout class} set to y Explanation: Response to "cccc SET TRACE SYSOUT(xxxx)" or "cccc T TR S(xxxx)"

command. cccc is the command name. xxxx is the sysout log/trace file identifier. y is a sysout class or DDNAME.

System Action: The sysout class for sysout log/trace file xxxx is set to y or file xxxx is assigned to the sysout DDNAME shown.


4502W xxxx already active Explanation: Response to "cccc START TRACE" or "cccc S TR" command.

cccc is the command name.

Messages and Codes

ESP-5.4-MC-03 489

xxxx is the sysout log/trace file identifier. System Action: Processing continues. User Response: None.

4503E xxxx sysout class not set Explanation: Response to "cccc START TRACE" or "cccc S TR" command.

cccc is the command name. xxxx is the sysout log/trace file identifier. Before sysout log/trace file xxxx can be started, its sysout class must be set.

System Action: Processing continues. User Response: To set sysout log/trace file xxxx's sysout class to y, enter:

cccc SET TRACE SYSOUT(y) or cccc T TR S(xxxx) Then re-enter the "cccc START TRACE" or "cccc S TR" command.

4504I xxxx started {on sysout class y}|{, DDNAME=x} Explanation: Response to "cccc START TRACE" or "cccc S TR" command.

cccc is the command name. xxxx is the sysout log/trace file identifier. y is a sysout class. x is a sysout DDNAME.

System Action: Sysout log/trace file xxxx is activated. User Response: None.

4505I xxxx stopped {on sysout class y}|{, DDNAME=x} Explanation: Response to "cccc STOP TRACE" or "cccc P TR" command.

cccc is the command name. xxxx is the sysout log/trace file identifier. y is a sysout class. x is a sysout DDNAME.

System Action: Sysout log/trace file xxxx is spun to output on sysout class y or sysout DDNAME x and de-activated.


4506I xxxx spun to output {on sysout class y}|{, DDNAME=x} Explanation: Response to "cccc RESTART TRACE", "cccc RS TR", "cccc SPIN TRACE" or

"cccc SP TR" command. cccc is the command name. xxxx is the sysout log/trace file identifier. y is a sysout class. x is a sysout DDNAME.

System Action: Sysout log/trace file xxxx is spun to output on sysout class y or sysout DDNAME x.


4507I xxxx restarted on {sysout class y}|{, DDNAME=x} Explanation: Response to "cccc RESTART TRACE", "cccc RS TR", "cccc SPIN TRACE" or

490 ESP-5.4-MC-03

"cccc SP TR" command. cccc is the command name. xxxx is the sysout log/trace file identifier. y is a sysout class. x is a sysout DDNAME.

System Action: After sysout log/trace file xxxx is spun to output, a new one is allocated to sysout class y or DDNAME x and opened. This message immediately follows message 4506.


4508E xxxx file open error Explanation: Response to "cccc START TRACE", "cccc S TR", "cccc RESTART TRACE",

"cccc RS TRACE", "cccc SPIN TRACE" or "cccc SP TR" command. cccc is the command name. xxxx is the sysout log/trace file identifier. Sysout log/trace file xxxx could not be opened.

System Action: Processing continues. User Response: Check if the JES spool file is full.

4509E <sysout_log/trace_file_error_message> Explanation: An error has occurred writing a record to a sysout log/trace file. System Action: The sysout log/trace file is closed and de-activated. User Response: Attempt to determine from the message text what the problem is, and

correct it if possible. Then restart the sysout log/trace file with the command: cccc START TRACE or cccc S TR where cccc is the command name to start that particular sysout log/trace file.

4510W xxxx not active Explanation: Response to "cccc STOP TRACE", "cccc P TR", "cccc RESTART TRACE",

"cccc RS TR", "cccc SPIN TRACE" or "cccc SP TR" command. cccc is the command name. xxxx is the sysout log/trace file identifier. The requested operation cannot be performaed as sysout log/trace file xxxx is not active.


4511E XSYSOUT interface not initialized Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4512E XSYSOUT token xxxx invalid Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

Messages and Codes

ESP-5.4-MC-03 491

4513S IEFSSREQ SSVI function SSOBRETN=n Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4514S IEFSSREQ error return code n Explanation: Internal logic error. Should never happen. System Action: Processing continues. User Response: Call Cybermation support.

4515E Subsystem xxxx yyyy Explanation: An error occurred in the subsystem interface. 'yyyy' is one of:

does not support SSI function n not active not defined to MVS A request was made to extract information about sybsystem xxxx, but it failed for the reason given. None of these conditions are expected

System Action: The information is not extracted. Processing continues. User Response: Investigate the state of the named subsystem.

4516W Subsystem xxxx does not support JES_NODE keyword Explanation: An attempt was made to determine the name of the local JES node,

but the JES level in use does not support the function. System Action: Processing continues without knowledge of the node name. User Response: None.

4517E Load failed for xxxx, RC=X'nnnn' Explanation: The Workstation Server is starting up and failed to load a vital

program whose name is xxxx. The return code is 'nnnn'. System Action: Workstation Server fails to start up. User Response: Ensure that the specified module resides in the Workstation Server's

load library and retry starting the Workstation Server. If the problem persists, contact Cybermation.

4518W Redundant prefix argument: xxxx Explanation: The Workstation Server received a message with a duplicate prefix

argument xxxx. System Action: Workstation Server ignores the input. User Response: Re-enter the message with no duplicate prefix arguments. If the

problem persists, contact Cybermation.

4519W Invalid prefix argument: xxxx Explanation: The Workstation Server received a message with an invalid value

for prefix argument xxxx. System Action: Workstation Server ignores the input. User Response: Re-enter the message with valid prefix arguments. If the problem

492 ESP-5.4-MC-03

persists, contact Cybermation.

4520I IAMHERE Explanation: Normal response to an RUTHERE command. Confirms the presence of

the program that responded. System Action: Processing continues. User Response: None.

4521E SUBSCRIB syntax invalid Explanation: Response to an incorrectly formulated SUBSCRIB command. System Action: Workstation Server ignores the input. User Response: Correct the command and retry.

4522E Subscription token already registered: xxxx Explanation: A SUBSCRIB command attempted to create a new subscription but

specified an already-used subscription token. System Action: Workstation Server ignores the input. User Response: Specify a different subscription token and retry.

4523E Subscription token not registered: xxxx Explanation: A command attempted to modify an existing subscription but

specified an unknown subscription token. System Action: Workstation Server ignores the input. User Response: Specify the correct subscription token and retry.

4525E Client issued command without prior logon; Subsystem WSS IP address: xx Explanation: A command could not be executed because the client did not first

log on through the command channel. System Action: Workstation Server ignores the input. User Response: Correct the IP address or log on before retrying the failed

command.

4527E Invalid number of data spaces in xxxx request: nn Explanation: An invalid value nn was specified in a xxxx request. System Action: The request is rejected User Response: This is caused by an internal logic error. Notify


4528E TCBTOKEN failed, RC=X'nnnn' Explanation: The TCBTOKEN function required to establish the environment

necessary for using a data space failed with return code 'nnnn'. System Action: Processing is terminated. User Response: Notify Cybermation Support.

4529E DSPSERV CREATE failed, RC=X'nnnn', Reason=X'nnnn' Explanation: The DSPSERV function required to establish the environment

necessary for using a data space failed with return code 'nnnn'. System Action: Processing is terminated.

Messages and Codes

ESP-5.4-MC-03 493

User Response: Notify Cybermation Support.

4530E DSPSERV DELETE failed, RC=X'nnnn', Reason=X'nnnn' Explanation: The DSPSERV function required to release the environment necessary

for using a data space failed with return code 'nnnn'. System Action: Processing continues. User Response: If the problem persists, notify Cybermation Support.

4531E ALESERV ADD failed, RC=X'nnnn' Explanation: The ALESERV function required to establish the environment

necessary for using a data space failed with return code 'nnnn'. System Action: Processing is terminated. User Response: Notify Cybermation Support.

4532E ALESERV DELETE failed, RC=X'nnnn' Explanation: The ALESERV function required to release the environment necessary

for using a data space failed with return code 'nnnn'. System Action: Processing continues. User Response: If the problem persists, notify Cybermation Support.

4533I Status channel termination triggered Explanation: A STATCHAN END or STOP command was successfully processed. System Action: Processing continues. User Response: None.

4534W The target of this command is unknown. Explanation: Response to a command whose Subsys() routing argument refers to an

unknown ESP subsystem. System Action: The command is ignored. User Response: Correct the Subsys() argument or ensure that the Workstation

Server is connectible to the specified target ESP subsystem.

4535E XDNR, GETHOSTID failed, RC=X'nnnn' Explanation: The Workstation Server is starting up and failed to obtain its own

IP address. The return code from the function call is 'nnnn'. System Action: Workstation Server fails to start up. User Response: Retry starting the Workstation Server. If the problem persists,

contact Cybermation.

4536E ADD_ESDW failed, RC=X'nnnn' Explanation: The Workstation Server is starting up and failed to create and

initialize a vital control block. The return code is 'nnnn'. System Action: Workstation Server fails to start up. User Response: Ensure that the ESP Workload Manager is active and retry starting

the Workstation Server. If the problem persists, contact Cybermation.

494 ESP-5.4-MC-03

4537I Response channel successfully established Explanation: A RESPCHAN command was successfully processed. System Action: Processing continues. User Response: None.

4538I Response channel ending Explanation: The task dedicated to a response channel is terminating. System Action: Processing continues. User Response: None.

4539E Port nn already has a response channel Explanation: A RESPCHAN command was issued for a port which was specified in a

previous successful RESPCHAN command. System Action: Processing continues. User Response: If the specified port was wrong, correct it and resubmit the RESPCHAN

command. Otherwise, do not resubmit the RESPCHAN command for that port.

4540I Response channel termination triggered Explanation: A RESPCHAN END or STOP command was successfully processed. System Action: Processing continues. User Response: None.

4541E Port nn is not a command channel Explanation: A STATCHAN or RESPCHAN command was issued for a port which is already

a status or a response channel. System Action: Processing continues. User Response: If the specified port was wrong, correct it and resubmit the command.

4542E No response channel defined Explanation: A RESPCHAN END command was issued through a command channel which has

no associated response channel. System Action: Processing continues. User Response: None.

4543E RESPCHAN requires TCP/IP Explanation: A RESPCHAN command was issued to a Workstation Server whose

communication protocol is not TCP/IP. System Action: Processing continues. User Response: If it is desirable to do so, make TCP/IP the communication protocol

of the target Workstation Server.

4544E Channel cannot be converted because it controls (a status channel) (and) (a response channel)

Explanation: A STATCHAN or RESPCHAN command was issued for a port which owns and controls a status or a response channel.


Messages and Codes

ESP-5.4-MC-03 495

User Response: Issue the command through a different channel, or terminate the channel's associated channels and retry.

4545E Invalid TIRA address: xxxxxxxx Explanation: A Workstation Server client requested a service without first

connecting to the Workstation Server or after the connection was severed.

System Action: Control returns to the calling program. User Response: This is caused by an internal logic error. Notify Cybermation

support.

4546E WSSPROXY command discarded Explanation: A WSSPROXY command has been discarded because the client has not

yet passed a USER or LOGON command through WSSPROXY. System Action: Processing continues. User Response: Pass a USER or LOGON command through WSSPROXY before passing

other commands through WSSPROXY.

4547E WSSPROXY parameter missing: xxxxx Explanation: The WSSPROXY parameter xxxxx has been omitted. System Action: Processing continues. User Response: Supply the missing parameter and retry.

4548E WSSPROXY requires a response channel Explanation: A WSSPROXY command was issued before the establishment of a response

channel. System Action: Processing continues. User Response: Establish a response channel and retry.

4549E WSSPROXY contains a syntax error Explanation: The Workstation Server received a badly-formed WSSPROXY command. System Action: Processing continues. User Response: Make the necessary corrections and retry.

4550I WSSPROXY passing message to a new proxy task Explanation: The Workstation Server is starting a new proxy task to log on a new

user. System Action: Processing continues. User Response: None.

4551I WSSPROXY passing message to a new proxy task with self-LOGON Explanation: The Workstation Server is starting a new proxy task for a user whose

previous proxy task timed out. A LOGON command will be executed before the command passed with WSSPROXY.


496 ESP-5.4-MC-03

4552I WSSPROXY passing message to an existing proxy task Explanation: The Workstation Server is passing a command to an existing proxy task.

The specified proxy task is still active and was started for the same user id logging on with the same password.


4553E WSSPROXY parameter badly formed: xx Explanation: The length or the format of the xx WSSPROXY parameter is incorrect. System Action: Processing continues. User Response: Make the necessary corrections and retry.

4554E WSSPROXY version is invalid: x Explanation: The version x specified in the P1 WSSPROXY parameter is invalid. System Action: Processing continues. User Response: Make the necessary corrections and retry.

4555I Logon successful P1(aaaaaaaa) P2(bbbbbbbb) P3(cccccccccccccccc) LOGONTYPE(dddddd)

Explanation: A proxy command task successfully logged on a user. System Action: Processing continues. User Response: None.

4556E Command cannot be routed to a remote WSS: xxxxxxxx Explanation: The client requested that the WSS route a command to a remote WSS, but

the WSS does not allow the specified command to be routed to a different WSS.


4557I WMSTATUS IPADDR(aa.aa.aa.aa) PORT(bbbb) WM(cccc) STATUS(dddddd)

Explanation: This message reports the status of the ESP Workload Manager whose Workstation Server has the stated IP address and port.


4558I WSSDOMN IPADDR(aa.aa.aa.aa) PORT(bbbb) WM(cccc) Explanation: This message is a response to the WSSDOMN command. It provides

identification data on one of the Workload Managers in a Workstation Server's domain. IPADDR and PORT represent the IP address and port of the Workstation Server dedicated to the Workload Manager. If the 4-character Workload Manager's subsystem name is known, it appears in the WM() keyword.


Messages and Codes

ESP-5.4-MC-03 497

4559E Error in LIKE argument or its usage Explanation: This message is a response to the USER or LOGON command. The command

specified an incomplete or badly-formed LIKE argument. System Action: Processing continues. User Response: Correct the LIKE argument and retry.

4560E LIKE cannot be specified for a Workstation Server that already serves as a model

Explanation: This message is a response to the USER or LOGON command. The command specified a LIKE argument that represents a Workstation Server which was selected in the LIKE argument of an earlier USER or LOGON command.

System Action: Processing continues. User Response: Specify a different LIKE argument and retry.

4561E LIKE cannot be specified for the home Workstation Server Explanation: This message is a response to the USER or LOGON command. The command

specified a LIKE argument to log on to the Workstation Server's home subsystem.

System Action: Processing continues. User Response: Remove the LIKE argument, supply a user id and a password, and retry.

4562E LIKE specifies a subsystem not in the domain of the Workstation Server Explanation: This message is a response to the USER or LOGON command. The command

specified a LIKE argument that represents a subsystem not in the domain of the Workstation Server.


4563E LIKE specifies a subsystem to which the user is not logged on Explanation: This message is a response to the USER or LOGON command. The command

specified a LIKE argument that represents a Workstation Server to which the user is not yet currently logged on.

System Action: Processing continues. User Response: Log on to the subsystem specified in the LIKE argument and retry.

4564E LIKE contains a circular specification Explanation: This message is a response to the USER or LOGON command. The command

specified a LIKE argument that represents the same Workstation Server to which the user is trying to log on.


4565W The subsystem name for xx has been corrected from yy to zz Explanation: The ESP subsystem name supplied in the Workstation Server's

configuration data is different from the subsystem name returned by the remote Workstation Server. The prior value yy is replaced by the correct name zz. The IP address and port of the remote Workstation

498 ESP-5.4-MC-03

Server is xx. System Action: Processing continues. User Response: Correct the configuration data for the next run of the Workstation

Server.

4566I TRACELOG opened Explanation: CYBES065 has issued an open request for the TRACELOG file. System Action: Processing continues. User Response: None.

4567I TRACELOG closed Explanation: CYBES065 has issued a close request for the TRACELOG file. System Action: Processing continues. User Response: None.

4568E INIT_ESDW failed, RC=X'nnnn' Explanation: The Workstation Server is starting up and failed to initialize a vital

control block. The return code is 'nnnn'. System Action: Workstation Server fails to start up. User Response: Check if any other error messages or warnings were issued before this

message. If the problem persists, contact Cybermation.

4569E WSS Configuration failed, RC=X'nnnn' Explanation: The Workstation Server is starting up and detected one or more errors

in the provided configuration data. The return code is nnnn. System Action: Workstation Server fails to start up. User Response: Correct all reported errors and restart the Workstation Server.

4570I WSS parameters successfully tested Explanation: The Workstation Server has successfully tested the syntax of all the

statements in the WSSREMOT data set. System Action: Workstation Server terminates. User Response: Restart the Workstation Server without the TESTPARMS keyword.

4571I nnn Remote WSS connections have been made, currently mmm are/is active

Explanation: Continuation to message 0472; display of requested information. System Action: Processing continues. User Response: None.

4572I ESDW added; Subsystem WSS IP address: nn Explanation: The Workstation Server successfully created the control block

it requires in order to keep track of an ESP Workload Manger. The IP address and port number of a Workstation Server dedicated to that Workload Manager are displayed in this message.


Messages and Codes

ESP-5.4-MC-03 499

4573I ESDW deleted; Subsystem WSS IP address: nn Explanation: The Workstation Server successfully deleted the control block

it requires in order to keep track of an ESP Workload Manger. The IP address and port number of a Workstation Server dedicated to that Workload Manager are displayed in this message.


4574E Load failed for xxxx, RC=X'nnnn' Explanation: The Workstation Server is starting up and failed to load a

vital program whose name is xxxx. The return code is 'nnnn'. System Action: Workstation Server fails to start up. User Response: Ensure that the specified module resides in the Workstation Server's

load library and retry starting the Workstation Server. If the problem persists, contact Cybermation.

4575I <variable> = <value> : <variable description> Explanation: This message reports the value of a Workstation Server variable. System Action: Processing continues. User Response: None.

4576E DSPSERV EXTEND failed, RC=X'nnnn', Reason=X'mmmm' Explanation: The DSPSERV function required to extend a data space failed

with return code 'nnnn'. System Action: Processing is terminated. User Response: If the problem persists, notify Cybermation Support.

4577I Start of processing, command file = xxxx Explanation: The Workstation Server has begun processing the command file

allocated to ddname xxxx. System Action: Processing continues. User Response: None.

4578I OK Command=xxxx, File=yyyy, Line#=zzzz Explanation: The Workstation Server has successfully processed the command xxxx

on line zzzz of the file allocated to ddname yyyy. System Action: Processing continues. User Response: None.

4579E Invalid command syntax, File=xxxx, Line=yyyy Explanation: The Workstation Server encountered a syntax error in the command

on line yyyy of the file allocated to ddname xxxx. System Action: Processing continues. User Response: Correct the command on line xxxx of file yyyy.

4580E Command xxxx not found, File=yyyy, Line=zzzz Explanation: The Workstation Server encountered a command xxxx that it does not

500 ESP-5.4-MC-03

recognize as valid, in line zzzz of the file allocated to ddname yyyy. System Action: Processing continues. User Response: Correct the command on line zzzz of file yyyy.

4581E xxxx Explanation: An attempt by the Workstation Server to open the WSSREMOT file failed.

Message xxxx should explain the reason for the failure.

System Action: Processing continues. User Response: Determine the problem from message xxxx and correct it.

4582I End of processing, command file = xxxx Explanation: The Workstation Server has finished processing the command file

allocated to ddname xxxx. System Action: Processing continues. User Response: None.

4583E WSSREMOT data rejected Explanation: The Workstation Server rejected one or more statements in the WSSREMOT

data set. System Action: Processing continues. User Response: Examine earlier error messages and apply the necessary corrections

to the statements in the WSSREMOT data set.

4584E xxxx failed, RC=X'yyyy'; Subsystem WSS IP address: zzzz Explanation: The Workstation Server failed with return code yyyy while performing

operation xxxx for the ESP Workload Manager whose Workstation Server listens to IP address and port zzzz.

System Action: Processing is terminated. User Response: Examine earlier error messages. If the problem persists, contact

Cybermation.

4585E REMOTE cannot be executed without CYBES111 Explanation: The Workstation Server has read in a REMOTE command, but cannot

this command is not supported if module CYBES111 is missing. System Action: The REMOTE command is rejected and the start-up of the Workstation

Server fails. User Response: Verify whether the Workstation Server has been correctly installed.

4586E REMOTE requires TCP/IP Explanation: The Workstation Server cannot execute the REMOTE command if the

Workstation Server's communication protocol is not TCP/IP. System Action: The REMOTE command is rejected and the start-up of the Workstation

Server fails. User Response: If it is desirable to do so, make TCP/IP the Workstation Server's

communication protocol.

Messages and Codes

ESP-5.4-MC-03 501

4587E REMOTE command error Explanation: The Workstation Server detected an error while parsing the REMOTE

command. System Action: The REMOTE command is rejected and the start-up of the Workstation

Server fails. User Response: Verify any earlier error messages and correct the REMOTE command.

4588E REMOTE host name not resolved: xxxx Explanation: The Workstation Server was unable to resolve the host name

specified in a REMOTE command. System Action: The REMOTE command is rejected and the start-up of the Workstation

Server fails. User Response: Correct the host name specified in the REMOTE command.

4589E REMOTE WSS cannot point to itself, remote WSS: xxxx Explanation: The Workstation Server's host and port are identical to the host

and port specified in a REMOTE command. System Action: The REMOTE command is rejected and the start-up of the Workstation

Server fails. User Response: Correct the host and port of the REMOTE command.

4590E Duplicate REMOTE command for the same WSS: xxxx Explanation: A REMOTE command specifies a host and port identical to those

specified in a previous REMOTE command. System Action: The REMOTE command is rejected and the start-up of the Workstation

Server fails. User Response: Ensure that no two REMOTE commands specify the same host and port.

4591E Duplicate PRIMARY command Explanation: The Workstation Server read in more than one PRIMARY command. System Action: The PRIMARY command is rejected and the start-up of the Workstation

Server fails. User Response: Ensure that only one PRIMARY command is passed to the Workstation

Server.

4592E PRIMARY command error Explanation: The Workstation Server detected an error while parsing the PRIMARY

command. System Action: The PRIMARY command is rejected and the start-up of the Workstation

Server fails. User Response: Verify any earlier error messages and correct the PRIMARY command.

4593W RWSSaaaa (bbbb), ID=cc, Task=dddddddd, eeee connection closed. Task terminating.

Explanation: The connection from a Workstation Server to a remote Workstation Server has been closed and the task which maintained that connection is terminating.

502 ESP-5.4-MC-03

aaaa is the number of the remote Workstation Server task; bbbb gives the IP address and port of the connection; cc is the TCP/IP connection number; dddddddd is the address of the task's TEE; eeee is the task's function.

System Action: The remote Workstation Server task is shut down. User Response: None.

4594E RWSSaaaa (bbbb), ID=cc, Task=dddddddd, eeee ff failed Explanation: Operation ff failed in a remote Workstation Server task.



4595I RWSSaaaa (bbbb), ID=cc, Task=dddddddd, eeee terminating Explanation: A remote Workstation Server task is terminating.



4596I RWSSaaaa (bbbb), ID=cc, Task=dddddddd, eeee received message ff from remote WSS

Explanation: A remote Workstation Server task received an unexpected message from the remote Workstation Server. If the message number is known, it appears in the place of ff. aaaa is the number of the remote Workstation Server task; bbbb gives the IP address and port of the connection; cc is the TCP/IP connection number; dddddddd is the address of the task's TEE; eeee is the task's function.

System Action: The remote Workstation Server task decides whether to resume processing.


4597I RWSSaaaa (bbbb), ID=cc, Task=dddddddd, eeee connected Explanation: A remote Workstation Server task has established a connection

to a remote Workstation Server.

Messages and Codes

ESP-5.4-MC-03 503



4598I RWSSaaaa (bbbb), ID=cc, Task=dddddddd, eeee trying to connect every ff seconds

Explanation: A remote Workstation Server task has not yet established a connection to a remote Workstation Server and is trying every ff seconds. aaaa is the number of the remote Workstation Server task; bbbb gives the IP address and port of the connection; cc is the TCP/IP connection number; dddddddd is the address of the task's TEE; eeee is the task's function.


4599I RWSSaaaa (bbbb), ID=cc, Task=dddddddd, eeee logged on Explanation: A remote Workstation Server task has successfully logged on to

a remote Workstation Server. aaaa is the number of the remote Workstation Server task; bbbb gives the IP address and port of the connection; cc is the TCP/IP connection number; dddddddd is the address of the task's TEE; eeee is the task's function.


4600I RWSSaaaa (bbbb), ID=cc, Task=dddddddd, eeee discarding a message Explanation: A remote Workstation Server response task is discarding a message

received from a remote Workstation Server. aaaa is the number of the remote Workstation Server task; bbbb gives the IP address and port of the connection; cc is the TCP/IP connection number; dddddddd is the address of the task's TEE; eeee is the task's function.


4601E Invalid RWSSST type Explanation: A remote Workstation Server task was initiated with an invalid

task function.

504 ESP-5.4-MC-03

System Action: The remote Workstation Server task terminates. User Response: This is caused by an internal logic error. Notify Cybermation

support.

4602E Time-out while waiting for response from remote WSS Explanation: The wait interval for arrival of a response from a remote Workstation

Server expired. System Action: The Workstation Server assumes that no response will ever arrive.

If a response does eventually arrive, it will be discarded. User Response: The remote Workstation Server or its Workload Manager may be

unavailable. The user may reenter the command that failed.

4603E Message rejected by remote WSS Explanation: A command was rejected by a remote Workstation Server.

This message is normally preceded by one or more error messages that explain why the remote Workstation Server rejected the command.

System Action: Processing continues. User Response: Examine earlier error messages and correct the rejected command.

4604E Remote WSS cannot currently be reached Explanation: The Workstation Server cannot pass a command to a remote Workstation

Server because the connection has not been established or has been interrupted.

System Action: Processing continues. User Response: The user may retry.

4605E Message for remote WSS is too large Explanation: The Workstation Server cannot pass a command to a remote Workstation

Server because the message is too large. System Action: Processing continues. User Response: Consider dividing the message.

4606I Proxy task xxxx starting for user yyyy Explanation: Proxy task number xxxx for user yyyy is starting. The user id appears

only when a proxy task is being attached for a user after an previous proxy task timed out.


4607I Proxy task xxxx ending for user yyyy Explanation: Proxy task number xxxx for user yyyy is ending. System Action: Processing continues. User Response: None.

4608I <variable> = <value> : <variable description> Explanation: This message reports the value of a Workstation Server variable. System Action: Processing continues.

Messages and Codes

ESP-5.4-MC-03 505


4609E Command error, File=xx, Line#=yy Explanation: The Workstation Server detected an error while processing a command.

on line number yy of the file whose ddname is xx. System Action: The command is rejected and the start-up of the Workstation Server

fails. User Response: Verify any earlier error messages and correct the REMOTE command.

4610I First scoreboard scan completed. STOKEN(xx) Explanation: The Workstation Server has completed its first scoreboard scan

for the status-update subscriptions whose STOKENs are listed. System Action: Processing continues. User Response: None.

4611E HOME host name not resolved: xx Explanation: The Workstation Server is starting up and failed to resolve the

IP address for the host specified in the HOME EXEC parameter or the HOME WSSPARM command.

System Action: Workstation Server fails to start up. User Response: Correct the host if it is erroneous and retry starting the Workstation

Server. If the problem persists, contact Cybermation.

4612E CREATE_KEY failed, KEY=X'aa', RC=X'bb' Explanation: The Workstation Server rejected the encryption key aa with return

code bb. System Action: Workstation Server fails to start up. User Response: Correct the key if it is erroneous and retry starting the Workstation

Server. If the problem persists, contact Cybermation.

4613I LOGON encryption enabled Explanation: The Workstation Server is able to accept encrypted client logons. System Action: Processing continues. User Response: None.

4614E ENCRYPT_BUFFER failed, RC=X'aa' Explanation: The Workstation Server failed to encrypt a message before

sending it to a client. The return code is aa. System Action: Workstation Server terminates the client session. User Response: This is caused by an internal logic error. Notify Cybermation


4615E ENCRYPT_BUFFER failed, RC=X'aa' Explanation: The Workstation Server failed to encrypt a change-of-direction

message before sending it to a client. The return code is aa. System Action: Workstation Server terminates the client session. User Response: This is caused by an internal logic error. Notify Cybermation

support.

506 ESP-5.4-MC-03

4616E DECRYPT_BUFFER failed, RC=X'aa' Explanation: The Workstation Server failed to decrypt a message received

from a client. The return code is aa. System Action: Workstation Server terminates the client session. User Response: This is caused by an internal logic error. Notify Cybermation


4617E ENCRYPTTYPE and KEY are corequisite parameters Explanation: The Workstation Server received a USER or LOGON command that

specified ENCRYPTTYPE or KEY, however one cannot be specified without the other.

System Action: The command is rejected and no encryption is enabled for the client. User Response: Correct the command and retry.

4618E CREATE_KEY failed, KEY=X'aa', RC=X'bb' Explanation: CYBESLMI rejected the encryption key aa with return code bb. System Action: CYBESLMI fails to start up. User Response: Correct the key if it is erroneous and retry running CYBESLMI.

4619E EncryptionÛDecryption error, RC=X'aa' Explanation: A failure occurred while encrypting a message destined for

a Workstation Server or while decrypting a message received from a Workstation Server. The return code is aa.

System Action: Workstation Server terminates the client session. User Response: This is caused by an internal logic error. Notify Cybermation


4638I File xxx locked Explanation: The Workstation Server has successfully issued an exclusive

ENQ on file xxx. File xxx may thus be modified and updated without the risk of simultaneous update by another user.


4639E File xxx in use Explanation: The Workstation Server tried unsuccessfully to issue an

exclusive ENQ on file xxx. Another user successfully performed an exclusive ENQ in order to update the file.

System Action: Processing continues. User Response: None or retry.

4640I File xxx unlocked Explanation: The Workstation Server has successfully issued a DEQ to

release a prior exclusive ENQ on file xxx. The file thus becomes available for update by another user.


Messages and Codes

ESP-5.4-MC-03 507

4641E File xxx not previously locked Explanation: The user specified the UNLOCK keyword in a PUTFILE command

for file xxx, but the user did not lock the file in a prior GETFILE command.

System Action: Processing continues. User Response: Issue the GETFILE command with the LOCK keyword before

using the PUTFILE command to update and unlock the file.

4642E UNDOLOCK: xxx Explanation: Error xxx occurred while processing the UNDOLOCK command. System Action: Processing continues. User Response: Correct and resubmit the command.

4643E Data set type not supported for PUTFILE Explanation: A PUTFILE command specified a data set name begining with LIB-,

PAN-, or ROS-. Data sets in these proprietary formats can only be read by Cybermation software. Writing to them is not possible.

System Action: The command is rejected. User Response: Do not attempt to upload to CA-Librarian, CA-Panvalet or CA-Roscoe

data sets.

4644I 'UNDOLOCK aaa' submitted by xxx yyy at yyyymmdd-hhmmss Explanation: The UNDOLOCK command was submitted by an operator or user yyy

at the date and time. System Action: Processing continues. User Response: None.

4645I File xxx.yyy.zzz(aaa) unlocked by bbb at yyyymmdd-hhmmss Explanation: A data set locked by the indicated user has been unlocked in

response to an UNDOLOCK command entered by an operator. System Action: Processing continues. User Response: None.

4646I Locks released = 999 Explanation: Shows the total number of data set locks released as a result of an

UNDOLOCK command. System Action: Processing continues. User Response: None.

4647I List of Currently Locked Files Explanation: This is header line one for the display of locked data sets

to be shown in response to the LISTLOCK command. System Action: Processing continues. User Response: None.

4648I User ID Task Date-Time File Explanation: This is header line two for the display of locked data sets

508 ESP-5.4-MC-03

to be shown in response to the LISTLOCK command. System Action: Processing continues. User Response: None.

4649I Userid Lockid Taskid yyyymmdd hhmmss xxx.yyy.zzz(aaa) Explanation: Locked data set information shown in response to a LISTLOCK

command entered by an operator. System Action: Processing continues. User Response: None.

4650I Locks currently held = 999 Explanation: Total count of locked data sets shown in response to a LISTLOCK

command entered by an operator. System Action: Processing continues. User Response: None.

4651I Lock not released because of PUTFILE in progress = 999 Explanation: In response to an UNDOLOCK command, a lock was not released

because a PUTFILE operation was in progress against the data set at the same time.

System Action: Processing continues. User Response: Re-enter the UNDOLOCK command again after a small time interval.

If this situation persists and it is necessary to release the data set lock, determine which user initiated the PUTFILE and have the user user complete it. If there is no alternative, use the UNDOLOCK with the FORCE keyword.

4652E User xxxxxxxx is not authorized to execute command yyyyyyyy Explanation: A SAF security check has determined that the indicated user is not

authorized to issue the indicated command. System Action: Processing continues. User Response: If it is necessary for you to issue the command, check with your SAF security

administrator for the appropriate access.

4653E File xxx.yyy.zzz was forcibly unlocked at yyyymmdd-hhmmss Explanation: The user has entered a PUTFILE command with the UNLOCK keyword

for a data set that has already been unlocked by another user with the UNDOLOCK command.


4654I Operator command received: xxx Explanation: An operator has appended command xxx to an MVS MODIFY command

and the Workstation Server has received it. System Action: Processing continues. User Response: None.

Messages and Codes

ESP-5.4-MC-03 509

4655E WSSCTL command missing Explanation: A "WSSCTL" command was issued without any parameters. System Action: Processing continues. User Response: Enter a "WSSCTL" command with valid parameters.

Or enter "WSSCTL HELP", "WSSCTL H" or "WSSCTL ?" for a list of "WSSCTL" command options.

4656I 'aaa' submitted by bbb ccc at yyyymmdd-hhmmss Explanation: The command aaa was submitted by an operator or user ccc at the

date and time shown. System Action: Processing continues. User Response: None.

4657E WSSCTL xxxx command invalid Explanation: The parameter immediately following "WSSCTL" in a "WSSCTL" command is

invalid. System Action: Processing continues. User Response: Enter a "WSSCTL" command with valid parameters.


4658E WSSCTL xxxx not an initialization command Explanation: A "WSSCTL" command was issued while the Workstation Server was still

initializing. The command cannot be processed until Workstation Server initialization is complete. Note that some "WSSCTL" commands can be issued during Workstation Server initialization while others cannot.

System Action: Processing continues. User Response: Remove the "WSSCTL" command from the initialization parameters.

4659E WSSCTL xxxx object missing Explanation: A "WSSCTL xxxx" command was entered that required at least one

additional parameter. System Action: Processing continues. User Response: Enter the "WSSCTL xxxx" command with valid parameters.


4660E WSSCTL xxxx object yyyy invalid Explanation: Parameter 'yyyy' in the command "WSSCTL xxxx yyyy" is invalid for the

command "WSSCTL xxxx". System Action: Processing continues. User Response: Enter a "WSSCTL xxxx" command with valid parameters.


510 ESP-5.4-MC-03

4661C WSSCTL Command Options Explanation: Response to a "WSSCTL HELP" command.

Lists all valid "WSSCTL" command options. System Action: Processing continues. User Response: None.

4662E SET TRACE SYSOUT is not compatible with the TRACELOG DD statement

Explanation: The Workstation Server still supports the TRACELOG DD statement for backward compatibility with existing JCL, but it cannot be used simultaneously with the "WSSCTL SET TRACE SYSOUT(x)" command or with the SET_WSSTRACE(x) parameter on the EXEC JCL statement.

System Action: The Workstation Server fails to start up. User Response: Delete the TRACELOG DD statement and use the "WSSCTL SET TRACE

SYSOUT(x)" command in the WSSPARM file or the SET_WSSTRACE(x) parameter (abbreviation: T_WSSTR(x)) on the EXEC JCL statement. To activate Workstation Server message tracing at start-up time, add the "WSSCTL START TRACE" command to the WSSPARM file or the START_WSSTRACE(x) parameter (abbreviation: S_WSSTR(x)) to the EXEC JCL statement. To enable or disable message tracing while the Workstation Server is executing, use the "WSSCTL START|STOP TRACE" command.

4663W User xxxxxxxx is not authorized to execute command yyyyyyyy Explanation: A SAF security check has determined that the indicated user is not

authorized to issue the indicated command. System Action: Processing continues. User Response: If it is necessary for you to issue the command, ask your ESP

Administrator to grant you OPER authority.

4664E DDNAME xxxx is not a SYSOUT data set Explanation: The DD statement with DDNAME xxxx should designate a SYSOUT

data set. System Action: Processing stops. User Response: Correct the DD statement or delete it and use the command

cccc SET TRACE SYSOUT(y) or cccc T TR S(y) where y is a sysout class.

4665E ERROR SCANNING COMMAND, RC=nnn Explanation: Error occurred while scanning command received from Workstation. System Action: The command is ignored. User Response: Depending on RC=nn different actions could be considered.

When nn=12: invalid command structure. Transmission error is likely, Check init parms. Try again. nn=16: No space available. nn=20: Validity check routine termination. nn=24: An error in input parameters was detected in the

Messages and Codes

ESP-5.4-MC-03 511

IKJPARS2 load module. nn=28: A line drop condition was detected and IKJPTGT (PUTGET I/O service routine) or IKJPUTL (PUTLINE I/O service routine) set return codes of 24 and 32 respectively.

4666E Length xxxx exceeds allowed limit of yyyy Explanation: The "LENGTH" parameter of a "WSSMSG" command is too high or

the text of a "WSSECHO" command is too long. System Action: Processing continues. User Response: Correct the "LENGTH" parameter of the "WSSMSG" command or shorten

the "WSSECHO" message.

4667E File xxx.yyy.aaa is a PDS, must specify a member name Explanation: A Getfile operation was specified for a PDS dataset but no member name

was specified with the dataset. A member name is needed. A Getfile operation with no member name specified is only valid for other types of datasets such as Sequential, etc.

System Action: The Getfile operation is not performed. User Response: Respecify the PDS dataset name with a valid member name in the form of

xxx.yyy.aaa(mbrname) and retry the operation.

4695E The scoreboard cannot presently be scanned Explanation: Response to the SUBSCRIB command when the Workstation Server

is unable to immediately perform a scoreboard scan. The SUBSCRIB request is rejected.

System Action: Processing continues. User Response: Retry the SUBSCRIB command at a later time.

4696E Invalid response from remote WSS xxx Explanation: A Consolidated Workstation Server has received an invalid

message in response to a client command that was routed to a remote Workstation Server. xxx gives the IP and port of the connection.

System Action: Processing continues. User Response: This is caused by an internal logic error. If the problem persists,

contact Cybermation.

4697I SIGNOFF COMPLETE Explanation: Response to the SIGNOFF command. System Action: Processing continues. User Response: None.

4698E RWSSaaaa (bbbb), ID=cc, Task=dddddddd, eeee logon retry disabled: ffff

Explanation: A remote Workstation Server task has failed to log on and has not to retry. aaaa is the number of the remote Workstation Server task;

512 ESP-5.4-MC-03

bbbb gives the IP address and port of the connection; cc is the TCP/IP connection number; dddddddd is the address of the task's TEE; eeee is the task's function; ffff is the reason for which the logon retry was disabled.

System Action: The Consolidated Workstation Server will not reattempt to log on to the remote Workstation Server. The remote Workstation Server cannot be accessed through the Consolidated Workstation Server.

User Response: Examine the cause of the logon failure (for example, an invalid password), make the necessary correction, and stop and restart the Consolidated Workstation Server.

4699I Monitor thread terminating; Subsystem WSS IP address: xxx Explanation: The Consolidated Workstation Server thread that monitors

the connection to a particular remote Workstation Server is terminating. xxx is the IP address of the remote Workstation Server monitored by the thread.

System Action: The remote Workstation Server cannot be accessed through the Consolidated Workstation Server.

User Response: If any error messages precede this message, make the necessary correction, and stop and restart the Consolidated Workstation Server.


BDC_Job jjjj in application aaaa. System Action: The application is not built. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


4701E BDC_Job xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status





the job.


Messages and Codes

ESP-5.4-MC-03 513




4704E BDC_JOB xxxx in Appl yyyy, missing ABAPname Explanation: Each BDC_JOB requires an ABABname to be specified indicating

















514 ESP-5.4-MC-03


4709E SAPEmailAddr too long Explanation: The length of the SAPEmailAddr exceeds the maximum of 256 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the SAPEmailAddr.


4711E BDC system name too long, maximum length nn Explanation: BDC System name is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of Remote File Name.


SAPA_Job jjjj in application aaaa. System Action: The application is not built. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


4713E SAPA_Job xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status





the job.




Messages and Codes

ESP-5.4-MC-03 515


4716E SAPA_JOB xxxx in Appl yyyy, missing ArcObjName Explanation: Each SAPA_JOB requires an ArcObjName to be specified indicating


4717E SAPA_JOB xxxx in Appl yyyy, missing ArcObjVariant Explanation: Each SAPA_JOB requires an ArcObjVariant to be specified indicating


4718E SAPA_JOB xxxx in Appl yyyy, missing ArcMode Explanation: Each SAPA_JOB requires an ArcMode to be specified indicating


4719E SAPA_JOB xxxx in Appl yyyy, missing ArcObjType Explanation: Each SAPA_JOB requires an ArcObjType to be specified indicating


4720E SAPA_JOB xxxx in Appl yyyy, missing ArcDocType Explanation: Each SAPA_JOB requires an ArcDocType to be specified indicating


4721E SAPA_JOB xxxx in Appl yyyy, missing ArcInfo Explanation: Each SAPA_JOB requires an ArcInfo to be specified indicating


4722E SAPA_JOB xxxx in Appl yyyy, missing PrintDest Explanation: Each SAPA_JOB requires a PrintDest to be specified indicating



user ID yyyy. "xxxx" is the user id under which the event

516 ESP-5.4-MC-03

executes for this job, normally the event prefix, but it may be a triggering user, or may be overridden by an installation EVENTSAF exit.

















SAPM_Job jjjj in application aaaa. System Action: The application is not built. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


Messages and Codes

ESP-5.4-MC-03 517

4729E SAPM_Job xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


4730E SAPM_JOB xxxx in Appl yyyy, missing Status Explanation: Each SAPM_JOB requires a Status to be specified indicating





the job.












518 ESP-5.4-MC-03











BWPC_Job jjjj in application aaaa. System Action: The application is not built. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


4738E BWPC_Job xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


4739E BWPC_JOB xxxx in Appl yyyy, missing Process Chain name Explanation: Each BWPC_JOB requires a Process Chain name to be specified indicating





the job.

Messages and Codes

ESP-5.4-MC-03 519





















520 ESP-5.4-MC-03


BWIP_Job jjjj in application aaaa. System Action: The application is not built. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


4747E BWIP_Job xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


4748E BWIP_JOB xxxx in Appl yyyy, missing Info Package name Explanation: Each BWIP_JOB requires a Info Package name to be specified indicating





the job.








must have read access to SAF profile AGENTUSR.yyyy.agentname.

Messages and Codes

ESP-5.4-MC-03 521

Once this has been established, resubmit the job.














EJB_Job jjjj in application aaaa. System Action: The application is not built. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


4756E EJB_Job xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


4757E EJB_JOB xxxx in Appl yyyy, missing BEAN Statement Explanation: Each EJB_JOB requires a BEAN to be specified indicating


522 ESP-5.4-MC-03

4758E EJB_JOB xxxx in Appl yyyy, missing METHOD Statement Explanation: Each EJB_JOB requires a METHOD to be specified indicating


4759E EJB_JOB xxxx in Appl yyyy, missing Initial_Context Statement Explanation: Each EJB_JOB requires an Initial_Context to be specified indicating


4760E EJB_JOB xxxx in Appl yyyy, missing Location Statement Explanation: Each EJB_JOB requires a Location to be specified indicating





the job.









Messages and Codes

ESP-5.4-MC-03 523





4765E BEAN Name too long Explanation: The length of the BEAN Name exceeds the maximum of 1024 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the BEAN Name.

4766E METHOD Name too long Explanation: The length of the METHOD Name exceeds the maximum of 1024 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the METHOD Name.

4767E Initial Context too long Explanation: The length of the Initial Context exceeds the maximum of 1024 .

characters. . System Action: The event fails. The object is not generated. User Response: Reduce the length of the Initial Context.

4768E Location too long Explanation: The length of the Location exceeds the maximum of 1024 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the Location.


the workload object type. System Action: Application generation fails. User Response: Reduce the length of the Destination.

4770E Missing Parameter Type Explanation: Each PARAMETER requires a Type to be specified indicating


4771E Parameter Type too long Explanation: The length of the Parameter Type exceeds the maximum of 1024

characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the Parameter Type.

524 ESP-5.4-MC-03

4772E Parameter Value too long Explanation: The length of the Parameter Value exceeds the maximum of 1024 .

characters. . System Action: The event fails. The object is not generated. User Response: Reduce the length of the Parameter Value.


JMSP_Job jjjj in application aaaa. System Action: The application is not built. User Response: It may be possible to increase the maximum size of an ATR. Enlarge


4774E JMSP_Job xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


4775E JMSP_JOB xxxx in Appl yyyy, missing Initial_Context Statement Explanation: Each JMSP_JOB requires an Initial_Context to be specified indicating


4776E JMSP_JOB xxxx in Appl yyyy, missing Connection Statement Explanation: Each JMSP_JOB requires a Connection to be specified indicating


4777E JMSP_JOB xxxx in Appl yyyy, missing Message Class Statement Explanation: Each JMSP_JOB requires a Message Class to be specified indicating


4778E JMSP_JOB xxxx in Appl yyyy, missing Destination Name Statement Explanation: Each JMSP_JOB requires a Destination Name to be specified indicating


4779E JMSP_JOB xxxx in Appl yyyy, missing Location Statement Explanation: Each JMSP_JOB requires a Location to be specified indicating

Messages and Codes

ESP-5.4-MC-03 525


4780E JMSP_JOB xxxx in Appl yyyy, missing Topic Statement Explanation: Each JMSP_JOB requires a Topic to be specified indicating





the job.













4785E Initial Context too long Explanation: The length of the Initial Context exceeds the maximum of 1024

characters.

526 ESP-5.4-MC-03

System Action: The event fails. The object is not generated. User Response: Reduce the length of the Initial Context.

4786E Connection Factory too long Explanation: The length of the Connection Factory exceeds the maximum of 1024

characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the Connection Factory.

4787E Message Class too long Explanation: The length of the Message Class exceeds the maximum of 1024

characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the Message Class.

4788E Location too long Explanation: The length of the Location exceeds the maximum of 1024 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the Location.

4789E Destination Name too long, maximum length nn Explanation: Destination Name is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of Destination Name.

4790E Missing Parameter Type Explanation: Each PARAMETER requires a Type to be specified indicating


4791E Parameter Type too long Explanation: The length of the Parameter Type exceeds the maximum of 1024

characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the Parameter Type.

4792E Parameter Value too long Explanation: The length of the Parameter Value exceeds the maximum of 1024

characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the Parameter Value.


JMSS_Job jjjj in application aaaa. System Action: The application is not built.

Messages and Codes

ESP-5.4-MC-03 527


4794E JMSS_Job xxxx in Appl yyyy, missing Agent name Explanation: There was no agent name to identify where the work was to run. System Action: The execution of the object fails, and a "submit error" status


4795E JMSS_JOB xxxx in Appl yyyy, missing Initial_Context Statement Explanation: Each JMSS_JOB requires an Initial_Context to be specified indicating


4796E JMSS_JOB xxxx in Appl yyyy, missing Connection Statement Explanation: Each JMSS_JOB requires a Connection to be specified indicating


4797E JMSS_JOB xxxx in Appl yyyy, missing Destination Name Statement Explanation: Each JMSS_JOB requires a Destination Name to be specified indicating


4798E JMSS_JOB xxxx in Appl yyyy, missing Location Statement Explanation: Each JMSS_JOB requires a Location to be specified indicating


4799E JMSS_JOB xxxx in Appl yyyy, missing Topic Statement Explanation: Each JMSS_JOB requires a Topic to be specified indicating





the job.

528 ESP-5.4-MC-03













4804E Initial Context too long Explanation: The length of the Initial Context exceeds the maximum of 1024

characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the Initial Context.

4805E Connection Factory too long Explanation: The length of the Connection Factory exceeds the maximum of 1024

characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the Connection Factory.

4806E Filter too long Explanation: The length of the Filter exceeds the maximum of 1024 characters. System Action: The event fails. The object is not generated. User Response: Reduce the length of the Filter.

4807E Location too long Explanation: The length of the Location exceeds the maximum of 1024 characters.

Messages and Codes

ESP-5.4-MC-03 529

System Action: The event fails. The object is not generated. User Response: Reduce the length of the Location.


the workload object type. System Action: Application generation fails. User Response: Reduce the length of the Destination.

4809E Destination Name too long, maximum length nn Explanation: Destination Name is longer than the maximum nn allowed for

the workload object type. System Action: Application generation fails. User Response: Reduce the length of Destination Name.

5000S ESP C/M IS ALREADY ACTIVE FOR SYSTEM ID sys_id Explanation: You have attempted to start a copy of ESP Console Manager which

specifies a subsystem name which is already active on your system. System Action: The newly started ESP Console Manager copy terminates. User Response: Insure that the ESP Console Manager system which you are attempting to

start specifies a unique subsystem name.

5001S ESP C/M INITIALIZATION DENIED BY INSTALLATION STARTUP EXIT

Explanation: The installation ESP Console Manager exit has denied the start for the ESP Console Manager system.

System Action: ESP Console Manager terminates. User Response: Check with the installation systems programmer to determine why the

installation start up exit may have denied the request.

5002E ERROR OCCURRED DURING COMMAND PARAMETER SCAN Explanation: A syntax error was detected when processing the PARM field from the ESP

Console Manager MVS START command. System Action: ESP Console Manager terminates. User Response: Re-issue the START command specifying a proper PARM field.

5003W PARAMETER ERROR ON EXEC CARD Explanation: When invoking ESP Console Manager in batch, an illegal parameter was

entered and an error message has been issued. System Action: ESP Console Manager terminates. User Response: Enter a proper input parameter.

5004W PARAMETER ERROR ON START COMMAND Explanation: When invoking ESP Console Manager via an MVS START command, an illegal

parameter was entered and an error message has been issued. System Action: ESP Console Manager terminates. User Response: Start ESP Console Manager with a valid input parameter.

530 ESP-5.4-MC-03

5005W LOCAL TIME hh:mm:ss ON ddd nn mmm yy Explanation: The GMTCHECK parameter was entered in the ESP Console Manager

initialization parameters and the GMT and the local time differ by more than 2 seconds.

System Action: The 5007 message will be issued. User Response: Enter the appropriate reply to the 5007 message.

5006W GMT TIME hh:mm:ss ON ddd nn mmm yy Explanation: The GMTCHECK parameter was entered in the ESP Console Manager


System Action: The 5007 message will be issued. User Response: Enter the appropriate reply to the 5007 message.

5007A REPLY 'Y' TO PROCEED OR REPLY 'N' TO TERMINATE Explanation: The GMTCHECK parameter was entered in the ESP Console Manager


System Action: Processing waits for the user response. User Response: Enter Y to continue with ESP Console Manager processing or enter N to

terminate ESP Console Manager.

5008I INVALID RESPONSE Explanation: The user replied to a prompt message was not Y or N. System Action: The user is prompted for a new response. User Response: Enter a valid response.

5009W WARNING, ERRORS MAY OCCUR DUE TO TOD CLOCK INCONSISTENCY

Explanation: The GMTCHECK parameter was entered in the ESP Console Manager initialization parameters and the GMT and the local time differ by more than 2 seconds. The user has subsequently replied N to the 5007 message.

System Action: Processing continues. User Response: Verify that the system clocks are set properly and that the system

initialization parameters specify the correct time variation from Greenwich Mean Time. If desired, the GMTCHECK parameter can be removed from the ESP Console Manager initialization parameters.

5010W CHECKPOINT DATASET dsname IS CORRECTLY FORMATTED Explanation: A cold start has been requested but the checkpoint data set is

correctly formatted. System Action: The 5011 message will be issued. User Response: Enter the appropriate reply to the 5011 message.

5011A CONFIRM REQUEST FOR COLD START, ENTER 'Y' OR 'N' Explanation: A cold start has been requested but the checkpoint data set is

Messages and Codes

ESP-5.4-MC-03 531

correctly formatted. System Action: Processing waits for the user response. User Response: Enter Y if you wish to proceed with the cold start. Otherwise, reply

with N.

5012I WARM START WILL BE ATTEMPTED Explanation: The user replied N to the 5011 message. System Action: ESP Console Manager will attempt a warm start. User Response: None required.

5014W CHECKPOINT dsname LAST USED BY SYSTEM sysid AT hh:mm ON ddmmmyy

Explanation: The checkpoint data set is correctly formatted but, internally, it says that it is in use by another system.

System Action: The 5015 message will be issued. User Response: Enter the appropriate response to the 5015 message.

5015A ENTER 'Y' TO PROCEED WITH COLD START OR REPLY 'N' Explanation: Either the user has requested a cold start or else ESP Console Manager

has determined that a cold start should be performed. System Action: Processing waits for the user response. User Response: Enter Y if you wish to proceed with the cold start. If you enter N, ESP

Console Manager will terminate.

5016E I/O error message Explanation: ESP Console Manager has encountered an I/O error on the checkpoint

data set. System Action: ESP Console Manager terminates. User Response: Either correct the I/O error or redefine a new checkpoint data set and

cold start ESP Console Manager.

5017S PRIMARY CHECKPOINT UNUSABLE Explanation: ESP Console Manager has encountered an I/O error on the checkpoint

data set. Message 5016 has been issued describing the error. System Action: ESP Console Manager terminates. User Response: Either correct the I/O error or redefine a new checkpoint data set and

cold start ESP Console Manager.

5018W INVALID CHECKPOINT FORMAT ON dsname Explanation: ESP Console Manager has determined that the checkpoint data set is

improperly formatted. System Action: ESP Console Manager will attempt to cold start. User Response: Enter the appropriate response to the 5015 message.

5019S NO CHECKPOINT DATASETS SPECIFIED IN ECMPARM Explanation: The ESP Console Manager initialization parameters did not specify a

checkpoint data set. System Action: ESP Console Manager terminates.

532 ESP-5.4-MC-03

User Response: Correct the ESP Console Manager initialization parameters.

5020S ALTERNATE CHECKPOINT START REQUESTED BUT ALTERNATE NOT DEFINED

Explanation: The user started ESP Console Manager with the ALTERNATE parameter but no alternate checkpoint data set was defined in the ESP Console Manager initialization parameters.

System Action: ESP Console Manager terminates. User Response: Either start ESP Console Manager without the ALTERNATE parameter or

else correct the ESP Console Manager initialization parameters.

5021S PRIMARY CHECKPOINT DATASET NOT DEFINED Explanation: The ESP Console Manager initialization parameters specified the data

set name of the primary checkpoint data set but no data set of that name is defined in the system.

System Action: ESP Console Manager terminates. User Response: Either define the proper data set or else correct the ESP Console

Manager initialization parameters.

5022S ESP C/M DATABASE DATASET NOT DEFINED Explanation: The ESP Console Manager initialization parameters specified the data

set name of the database data set but no data set of that name is defined in the system.

System Action: ESP Console Manager terminates. User Response: Either define the proper data set or else correct the ESP Console

Manager initialization parameters.

5024W ESP C/M LAST ACTIVE AT hh:mm:ss ON mmm dd yy Explanation: The current time is either less than the last write time on the

checkpoint data set or is more than the allowed time. This message displays the time of the last checkpoint write.


5025W IT IS NOW hh:mm:ss ON mmm dd yy Explanation: The current time is either less than the last write time on the

checkpoint data set or is more than the allowed time. This message displays the current time.


5026A CONFIRM DATE AND REPLY 'Y' TO CONTINUE, 'N' TO TERMINATE OR 'Q' TO QUIESCE

Explanation: The current time is either less than the last write time on the checkpoint data set or is more than the allowed time.

System Action: Processing waits for the user response. User Response: Enter Y if you wish to proceed. Enter N if you wish to terminate ESP

Console Manager or enter Q if you wish to quiesce any outstanding ESP

Messages and Codes

ESP-5.4-MC-03 533

Console Manager processing from the checkpoint.

5027S ESP C/M TERMINATING DUE TO INCORRECT CLOCK SETTING Explanation: The current time is either less than the last write time on the

checkpoint data set or is more than the allowed time. The user replied with N to the 5026 message.

System Action: ESP Console Manager terminates. User Response: None required.

5028W message text Explanation: An unusual condition was encountered while opening the checkpoint

data set. System Action: Processing continues. User Response: Determine the nature of the unusual condition based upon the message

text and take any corrective which may be indicated.

5029W UNABLE TO OPEN ALTERNATE CHECKPOINT Explanation: An alternate checkpoint data set was defined but ESP Console Manager

was unable to open it. System Action: Processing continues. User Response: Either remove the alternate checkpoint definition from the ESP Console

Manager initialization parameters or else insure that the alternate checkpoint data set can be properly opened.

5031S ESP C/M DATABASE dsname UNUSABLE Explanation: Errors were encountered while trying to open the ESP Console Manager

database. The nature of the error is described in a previous message. System Action: ESP Console Manager terminates. User Response: Take the appropriate corrective action based on the error messages

issued and restart ESP Console Manager.

5032E INCORRECT KEY LENGTH SPECIFIED FOR DATABASE DATASET Explanation: The ESP Console Manager database has been defined with an invalid key

length. System Action: ESP Console Manager terminates. User Response: Redefine the ESP Console Manager database as per the ESP Console

Manager Installation manual and restart ESP Console Manager.

5033I ESP C/M DATABASE HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED

Explanation: The ESP Console Manager database does not contain a valid control record.

System Action: ESP Console Manager will add a control record to the database and continue processing.

User Response: None required.

5034I ESP C/M DATABASE EMPTY, WILL FORMAT Explanation: The ESP Console Manager database has not yet been formatted.

534 ESP-5.4-MC-03

System Action: ESP Console Manager will format the database and continue processing. User Response: None required.

5040S ESP C/M SUBSYSTEM CANNOT BE RUN IN BATCH AT INSTALLATION REQUEST

Explanation: An installation exit has prevented the running of ESP Console Manager in batch mode.

System Action: ESP Console Manager terminates. User Response: Check with the systems programmer to determine why the batch

invocation has not been allowed.

5041E INVALID TIMEZONE ADJUSTMENT value Explanation: An illegal time zone adjustment value has been specified. System Action: ESP Console Manager terminates. User Response: Correct the ESP Console Manager initialization parameters and re-start

ESP Console Manager.

5042E INVALID TIMEZONE CODE, code SHOULD BE 0-63 Explanation: A time zone code has been specified which did not fall within the

allowable range. System Action: ESP Console Manager terminates. User Response: Correct the ESP Console Manager initialization parameters and re-start


5043E TIMEZONE CODE code NOT VALID FOR ZONE NAME name Explanation: The time zone code is not legal for the named time zone. System Action: ESP Console Manager terminates. User Response: Correct the ESP Console Manager initialization parameters and re-start


5045E INVALID MAXLRECL VALUE value, VALID RANGE 4000-32760 Explanation: The MAXRECL initialization parameter specifies a value which is

outside of the legal range. System Action: ESP Console Manager terminates. User Response: Correct the ESP Console Manager initialization parameters and re-start


5046E INVALID JOURNAL SMF RECORD NUMBER SPECIFIED Explanation: The journalling SMF record number is outside of the legal range. System Action: ESP Console Manager terminates. User Response: Correct the ESP Console Manager initialization parameters and re-start


5047E INVALID SVC NUMBER SPECIFIED Explanation: The SVC parameter specifies a value which is outside of the legal

range. System Action: ESP Console Manager terminates. User Response: Correct the ESP Console Manager initialization parameters and re-start

Messages and Codes

ESP-5.4-MC-03 535


5048A ENTER INITIALIZATION PARAMETER OR 'END' Explanation: A PROMPT parameter has been specified and ESP Console Manager is

asking for the next initialization parameter. System Action: Processing waits for the user input. User Response: Enter another ESP Console Manager initialization parameter or else

enter END to complete the initialization parameters.

5049W PARAMETER ERROR ON FOLLOWING STATEMENT FROM ddname FILE

Explanation: An error was detected on an input parameter statement. System Action: Processing continues. User Response: Correct the parameter and restart ESP Console Manager.

5050W FOLLOWING STATEMENT FROM ddname HAS AN INVALID SYNTAX


5051W FOLLOWING STATEMENT FROM ddname HAS AN UNDEFINED PARAMETER


5052E message text Explanation: An optional DD statement has been requested but there is no such DD

name in the input JCL. System Action: ESP Console Manager terminates. User Response: Correct the input and restart ESP Console Manager.

5053W message text Explanation: An error has been encountered on an input statement. System Action: Message 5054 will be issued. User Response: Enter the proper response to the 5054 message.

5054A REENTER ENTIRE STATEMENT, 'CANCEL' OR 'END' Explanation: An error has been encountered on an input statement. System Action: Processing waits for the user response. User Response: Either enter a replacement statement, enter CANCEL to terminate ESP

Console Manager or enter END to complete input processing.

5056S CANNOT PURGE START WITH AUXILIARY ACTIVE Explanation: An attempt has been made to purge start ESP Console Manager. However,

the ESP Console Manager auxiliary address space is currently operational.

536 ESP-5.4-MC-03

System Action: ESP Console manager terminates. User Response: You must either warm start ESP Console Manager or else FORCE ARM the

auxiliary address space prior to performing the purge start.

5056S CANNOT PURGE START WITH AUXILIARY ACTIVE Explanation: An attempt has been made to purge start ESP Console Manager. However,

the ESP Console Manager auxiliary address space is currently operational.

System Action: ESP Console manager terminates. User Response: You must either warm start ESP Console Manager or else FORCE ARM the

auxiliary address space prior to performing the purge start.

5060S UNABLE TO INITIALIZE SUBSYSTEM Explanation: ESP Console Manager could not initialize its subsystem. System Action: ESP Console Manager terminates. User Response: Examine all other messages issued to see what corrective action should

be taken.

5061S UNABLE TO GETMAIN STORAGE FOR THE VECTOR TABLE Explanation: ESP Console Manager could not obtain storage for its internal vector

table. System Action: ESP Console Manager terminates. User Response: Relieve the CSA storage shortage and re-start ESP Console Manager.

5065S INSUFFICIENT CSA TO LOAD MODULE name Explanation: ESP Console Manager could not obtain sufficient CSA storage to load

the named module. System Action: ESP Console Manager terminates. User Response: Relieve the CSA storage shortage and re-start ESP Console Manager.

5066S UNABLE TO LOAD MODULE name Explanation: ESP Console Manager could not locate the named module. System Action: ESP Console Manager terminates. User Response: Insure that the named module resides in one of the ESP Console Manager

STEPLIB, a link list library or in LPA and re-start ESP Console Manager.

5067I message text Explanation: This message contains the information detected when starting the

auxiliary address space in debug mode. System Action: Processing continues. User Response: None required.

5068E SUBSYSTEM ID name IN USE BY ANOTHER SUBSYSTEM Explanation: The ESP Console Manager subsystem is already in use by another ESP

Console Manager subsystem. System Action: ESP Console Manager terminates. User Response: Either stop the other subsystem or else change the ESP Console Manager

Messages and Codes

ESP-5.4-MC-03 537

initialization parameters to specify a new subsystem name.

5070I OK Explanation: The user has entered a command and ESP Console Manager has processed it

successfully. System Action: Processing continues. User Response: None required.

5071I COMMAND PREFIX SUBSTITUTIONS Explanation: The command prefix substitutions are being displayed. System Action: ESP Console Manager will list the command prefix substitutions which

are in effect. User Response: None required.

5072I NO COMMAND PREFIX SUBSTITUTION IN EFFECT Explanation: The user requested that the command prefix substitutions be listed but

none were in effect. System Action: Processing continues. User Response: None required.

5075I DATE FORMAT SET Explanation: The date format has been set from the DATEFORM statement. System Action: Processing continues. User Response: None required.

5076I CURRENT DATE FORMAT IS xxx Explanation: The display of the date format has been requested via the DATEFORM

statement. System Action: Processing continues. User Response: None required.

5077I CURRENT DATE FORMAT IS DEFAULT OF YMD Explanation: The display of the date format has been requested via the DATEFORM

statement. No specific date format has been set. System Action: Processing continues. User Response: None required.

5078E INVALID DATE FORMAT xxx Explanation: An illegal date format was specified on the DATEFORM statement. System Action: The DATEFORM statement is ignored. User Response: Correct the DATEFORM statement and re-start ESP Console Manager.

5080W MODULE name NOT DEFINED Explanation: A RELOAD command was entered but the named module could not be found. System Action: The RELOAD command is ignored. User Response: Insure that the RELOAD command specifies a valid module name.

538 ESP-5.4-MC-03

5081E UNABLE TO LOAD MODULE name Explanation: An error was encountered when trying to load a module specified on the

RELOAD command. System Action: The RELOAD command is ignored. User Response: Insure that the RELOAD command specifies a valid module name.

5082W UNABLE TO OBTAIN SUFFICIENT CSA FOR name Explanation: ESP Console Manager could not obtain sufficient CSA storage for the

named control block. System Action: The processing of the requested ESP Console Manager operation

terminates. User Response: Relieve the CSA shortage and re-issue the command.

5083I MESSAGE AUTOMATION TABLE LOADED, MEMBER name FROM FILE ddname

Explanation: The named message automation table has been loaded. System Action: Processing continues. User Response: None required.

5084I MESSAGE AUTOMATION TABLE LOADED Explanation: The message automation table has been loaded as a result of a MAT LOAD

command. System Action: Processing continues. User Response: None required.

5085W MEMBER NAME NOT SPECIFIED FOR RELOAD FUNCTION Explanation: A RELOAD command has been entered with no member name. System Action: The RELOAD command is ignored. User Response: Re-issue the RELOAD command with a valid member name.

5086I AUTOMATION MEMBER name RELOADED Explanation: A MAT RELOAD command has been processed. System Action: Processing continues. User Response: None required.

5087I RELOAD SUCCESSFUL FOR name Explanation: A RELOAD command has been processed. System Action: Processing continues. User Response: None required.

5088W PREVIOUS AUTOMATION TABLE NOT YET DRAINED, RETRY IN 30 SECONDS

Explanation: A RELOAD command has been entered but the previous automation table is still active.

System Action: The RELOAD command is ignored. User Response: Re-issue the RELOAD command after a suitable delay.

Messages and Codes

ESP-5.4-MC-03 539

5089W NO CURRENT MESSAGE AUTOMATION TABLE ACTIVE, DO BUILD REQUEST FIRST

Explanation: A MAT RELOAD command has been entered but their is no message automation table active.

System Action: The MAT command is ignored. User Response: Insure that a message automation table is active before issuing a MAT

command.

5092E INVALID DAY OF WEEK NAME name Explanation: An invalid day name was present on the WKSTART parameter. System Action: The WKSTART parameter is ignored. User Response: Correct the WKSTART parameter and re-start ESP Console Manager.

5092E INVALID DAY OF WEEK NAME name Explanation: An invalid day name was present on the WKSTART parameter. System Action: The WKSTART parameter is ignored. User Response: Correct the WKSTART parameter and re-start ESP Console Manager.

5094E UNABLE TO LOAD USER-VERIFY EXIT ROUTINE Explanation: The USERVFYX parameter specified a module name which was could not be

loaded. System Action: The USERVFYX statement is ignored. User Response: Either insure that the module is in the ESP Console Manager STEPLIB, a

link list library or in LPA or else change the USERVFYX statement.

5095E MODULE name NOT IN COMMON STORAGE Explanation: The USERVFYX parameter specified a module name which was not loaded in

CSA. System Action: The USERVFYX statement is ignored. User Response: Insure that the module is loaded into CSA.

5096E CANNOT RELOAD PRIMARY AUTOMATION TABLE Explanation: A MAT RELOAD command has been entered for the primary message

automation table. System Action: The command is ignored. User Response: If you wish to refresh the primary message automation table, you must

enter a MAT BUILD command.

5099E INVALID TCELL CELL SIZE nnn Explanation: The XMEPOOL SIZE parameter specified a value that was not in the

allowable range. System Action: The XMEPOOL statement is ignored. User Response: Correct the XMEPOOL SIZE parameter and re-start ESP Console Manager.

5100E INVALID TCELLG EXPANSION LIMIT nnn 10 USED Explanation: The XMEPOOL COUNT parameter specified a value that was not in the

allowable range.

540 ESP-5.4-MC-03

System Action: The XMEPOOL statement is ignored. User Response: Correct the XMEPOOL COUNT parameter and re-start ESP Console Manager.

5101E INVALID TCELL EXPANSION LIMIT nnn 10 USED Explanation: The XMEPOOL MAX parameter specified a value that was not in the

allowable range. System Action: The XMEPOOL statement is ignored. User Response: Correct the XMEPOOL MAX parameter and re-start ESP Console Manager.

5102E INVALID JOURNAL SMF RECORD NUMBER SPECIFIED Explanation: The SMFREC parameter specified a value that was not in the allowable

range. System Action: The SMFREC statement is ignored. User Response: Correct the SMFREC parameter and re-start ESP Console Manager.

5110I OK Explanation: A ESP Console Manager command has been successfully processed. System Action: Processing continues. User Response: None required.

5111I SHUTDOWN COMMAND ACCEPTED Explanation: A P ESPCM or F ESPCM,SHUTDOWN command has been entered. System Action: Termination is initiated. User Response: None required.


5113I ALREADY QUIESCED Explanation: A QUIESCE command has been entered but the system has already been

quiesced. System Action: The command is ignored. User Response: None required.

5114I QUIESCING Explanation: A QUIESCE command has been entered. System Action: ESP Console Manager is quiescing. User Response: None required.

5115I RESTARTING Explanation: A RESTART command has been entered. System Action: ESP Console Manager is restarting. User Response: None required.

5116I NOT QUIESCED Explanation: A RESTART command has been entered but the system has not been

Messages and Codes

ESP-5.4-MC-03 541

quiesced. System Action: The command is ignored. User Response: None required.

5117I ESP C/M RELEASE nnn STATUS Explanation: A STATUS command has been entered. System Action: The ESP Console Manager status is displayed. User Response: None required.

5119I ESP C/M RELEASE nnn INITIALIZATION COMPLETE Explanation: ESP Console Manager has been initialized as the result of an MVS START

command. System Action: Processing continues. User Response: None required.

5120I ESP C/M SHUTDOWN IN PROGRESS Explanation: ESP Console Manager is processing the shutdown request. System Action: The shutdown is proceeding. User Response: None required.

5121W INVALID COMMAND, command Explanation: An illegal command has been entered. System Action: The command is ignored. User Response: Re-issue a valid command.

5122W INVALID COMMAND NAME SYNTAX Explanation: An illegal command has been entered. System Action: The command is ignored. User Response: Re-issue a valid command.

5123W YOU ARE NOT AUTHORIZED FOR OPERATOR COMMANDS Explanation: You have entered a ESP Console Manager command but you have not been

given command authority. System Action: The command is ignored. User Response: Check with your systems administrator for command authorization.

5124S ERROR OBTAINING A COMMAND, RC=nn Explanation: An error condition has been encountered while trying to read a command. System Action: Message 5125 will be issued. User Response: Correct the problem and re-start ESP Console Manager.

5125S COMMAND PROCESSING TERMINATED Explanation: An error condition has been encountered while trying to read a command. System Action: All ESP Console Manager command processing is terminated. User Response: Correct the problem and re-start ESP Console Manager.

5126I DATASET dsname UNALLOCATED Explanation: An UNALLOC command has been processed.

542 ESP-5.4-MC-03


5127E SVC 99 failure message Explanation: An UNALLOC command was entered but an error was detected while trying

to de-allocate the data set. System Action: The command is ignored. User Response: Correct the problem based upon the text of the message and re-issue

the command.

5128W CALLRTN command parameter error Explanation: A CALLRTN command was entered but there was a syntax error in the

command parameters. System Action: The command is ignored. User Response: Re-issue a correct command.

5129E ERROR LINKING TO cmdname Explanation: A CALLRTN command was entered but the routine name specified could not

be loaded. System Action: The command is ignored. User Response: Re-issue a correct command.

5131W NO task_id AUTOMATION TASKS DEFINED Explanation: An IPL procedure has been specified but no automation tasks have been

defined. System Action: The IPL procedure is ignored. User Response: Insure that the proper automation tasks exist before requesting an IPL

procedure.

5132W NO task_id AUTOMATION TASKS DEFINED Explanation: An IMPLEXEC command was entered but no automation tasks have been

defined. System Action: The command is ignored. User Response: Insure that the proper automation tasks exist before issuing the

command.

5133I QUIESCED Explanation: A STATUS command was entered and ESP Console Manager has been quiesced. System Action: Processing continues. User Response: None required.

5134I SUBSYSTEM NAME: name Explanation: A STATUS command was entered and the name of the ESP Console Manager

subsystem is being displayed System Action: Processing continues. User Response: None required

Messages and Codes

ESP-5.4-MC-03 543

5135I DATABASE NAME: dsname Explanation: A STATUS command was entered and the data set name of the ESP Console

Manager database is being displayed System Action: Processing continues. User Response: None required

5136I CHECKPOINT NAME: dsname Explanation: A STATUS command was entered and the data set name of the ESP Console

Manager checkpoint is being displayed System Action: Processing continues. User Response: None required

5140S ERROR ATTACHING COMMAND TASK, RC=nn Explanation: An error was detected while trying to attach the command task. System Action: ESP Console Manager terminates. User Response: Contact Cybermation Technical Support.

5150S ESP C/M REQUIRES APF AUTHORIZATION Explanation: The ESP Console Manager STEPLIB is not an authorized library. System Action: ESP Console Manager terminates. User Response: Authorize the ESP Console Manager load module library and re-start ESP

Console Manager.

5160W UNABLE TO OBTAIN SUFFICIENT CSA FOR name Explanation: ESP Console Manager was unable to obtain sufficient CSA storage for

the named control block. System Action: ESP Console Manager terminates. User Response: Relieve the CSA shortage and re-start ESP Console Manager.


5162I PROCEDURE name {REPLACED IN|ADDED TO} SCHEDULE, ID name Explanation: An SCHPROC ADD or REPLACE command has been processed. System Action: Processing continues. User Response: None required.

5163I SCHEDULE ENTRY name DELETED Explanation: An SCHPROC DELETE command has been processed. System Action: Processing continues. User Response: None required.

5164I SCHEDULE ENTRY name NOT FOUND Explanation: An SCHPROC command was entered but the named schedule entry could not

be found.

544 ESP-5.4-MC-03

System Action: The command is ignored. User Response: Re-issue the command with a valid schedule name.

5165I AUTOMATION TASK name NOT FOUND Explanation: An SCHPROC command was entered but the named task could not be found. System Action: The command is ignored. User Response: Re-issue the command with a valid task name.

5166I SCHEDULE ENTRY ID name ALREADY DEFINED Explanation: An SCHPROC ADD command has been entered but the named entry has

already been added. System Action: The command is ignored. User Response: Re-issue the command with a new entry name.

5167I NO SCHEDULE TIME SPECIFIED, REQUEST IGNORED Explanation: An SCHPROC ADD command has been entered but not scheduled time has been

specified. System Action: The command is ignored. User Response: Re-issue the command with a valid scheduled time.

5168E Time parameter error message Explanation: An SCHPROC command was entered but the time specified contained a

syntax error. System Action: The command is ignored. User Response: Re-issue the command with a valid scheduled time.

5169I ABOVE ERROR OCCURRED PROCESSING SCHEDULE ENTRY name Explanation: An error has been detected on an SCHPROC command. System Action: The command is ignored. User Response: Correct the command based on previous errors and re-issue the

corrected command.

5170I SCHEDULE DISPLAY Explanation: An SCHPROC command was entered to display the schedule. System Action: The schedule is displayed. User Response: None required.

5171I NO MATCHING ENTRIES FOUND Explanation: An SCHPROC command was entered with an entry name but that entry was

not defined. System Action: The command is ignored. User Response: Re-issue the corrected command.

5172I NO PROCEDURES SCHEDULED Explanation: An SCHPROC display command was entered but nothing was scheduled. System Action: Processing continues. User Response: None required.

Messages and Codes

ESP-5.4-MC-03 545

5180I I/O ERROR OCCURRED PROCESSING SCHEDULE ENTRY FOR SCHEDULE ENTRY name

Explanation: An I/O error was encountered when processing a schedule entry. A previous message describes the nature of the I/O error.

System Action: The schedule entry is not processed. User Response: Examine the messages to determine the nature of the I/O error and take

corrective action based upon these messages.

5181I ABOVE ERROR OCCURRED CYCLING SCHEDULE ENTRY name Explanation: An time parameter error was encountered when processing a schedule

entry. A previous message describes the nature of the error. System Action: The schedule entry is not processed. User Response: Examine the messages to determine the nature of the error and take

corrective action based upon these messages.

5182W UNABLE TO SCHEDULE PROCEDURE proc TO TASK task FOR SCH ID name

Explanation: The named task has not been defined. System Action: The schedule entry is not processed. User Response: Either insure that the named task has been defined or else change the

schedule to reflect a valid task name.

5190E stmt STATEMENT NOT VALID OUTSIDE OF MAIN AUTOMATION MEMBER

Explanation: The listed statement was found in a member which was not the main automation member.

System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5191E ABOVE ERROR OCCURRED ON LINE nnn OF MEMBER name OF MESSAGE AUTOMATION

LIBRARY Explanation: A previous message indicated an error in the indicated statement. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5192E COMMAND value NOT DEFINED Explanation: The specified command has not been defined to ESP Console Manager. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5193E INVALID PARAMETER NAME SYNTAX Explanation: The parameter name contains an invalid syntax. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

546 ESP-5.4-MC-03

5194E error message Explanation: An error was encountered when processing an input statement. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5195E ERROR OCCURRED READING A COMMAND FROM MEMBER name OF MESSAGE AUTOMATATION LIBRARY

Explanation: An input error was detected. A previous message should indicate the nature of the error.


5196E INVALID FUNCTION CODE ISSUED TO CYBRO014 Explanation: An internal error has been detected. System Action: The member is not processed. User Response: Contact Cybermation Technical Support.

5197E INCONSISTENT PARAMETERS ISSUED TO CYBRO014 Explanation: An internal error has been detected. System Action: The member is not processed. User Response: Contact Cybermation Technical Support.

5198W HASH SIZE STATEMENT SHOULD PRECEDE FIRST MESSAGE STATEMENT

Explanation: The HASHSIZE statement must come before any MESSAGE statements. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5199E MAXVARS LIMIT EXCEEDED, VARIABLE name WILL NOT BE DEFINED

Explanation: You have defined too many variables. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command. The member can be

corrected by either no defining any more variables or by increasing the MAXVARS value.

5200E VARIABLE name ALREADY DEFINED Explanation: The named variable has already been defined. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5201E VARIABLE name NOT FOUND Explanation: The named variable is undefined. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

Messages and Codes

ESP-5.4-MC-03 547

5202E LOGICAL ROUTING name NOT FOUND Explanation: The listed logical routing name has not been defined. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5203E INVALID CHARACTER SET RANGE value Explanation: The ending character is lower than the starting character in a

character set range. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5204E Message:MAXCOND LIMIT EXCEEDED, CONDITION name WILL NOT BE DEFINED

Explanation: Too many conditions have been defined. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command. A possible

corrective action is to increase the MAXCOND value.

5205E CONDITION NESTING LEVEL LIMIT OF 3 EXCEEDED FOR CONDITION name

Explanation: Conditions have exceeded the allowable nesting limit. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5206E MESSAGE msg_id ALREADY DEFINED IN MEMBER name Explanation: The message identifier has already been defined elsewhere. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5207E LROUTE value NOT DEFINED Explanation: The named routing value is undefined. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5208E TARGET VARIABLE FOR name FUNCTION MUST BE A GLOBAL INTEGER

Explanation: You have referenced a local variable where a global variable is required.


5209E INVALID STRING/VALUE value Explanation: The listed string contains a syntactic error. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

548 ESP-5.4-MC-03

5210E VARIABLE NAME name NOT FOUND Explanation: Reference has been made to an undefined variable. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5211E VARIABLE NAME name EXCEEDS 16 CHARACTERS Explanation: The variable name is too long. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5212E INDEX MISSING FOR TOKEN OR WORD Explanation: The token or word used requires an index value but none was supplied. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5213E INVALID INDEX SPECIFIED FOR TOKEN OR WORD Explanation: You specified an illegal index value. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5214E INVALID SUBFIELD VALUE value Explanation: You specified an illegal subfield value. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5215E TOO MANY SUBFIELDS IN SPECIFIED value Explanation: The subfields exceeded the maximum number. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5216E INVALID EXPRESSION SYNTAX IN WHERE/WHEN SUBFIELD Explanation: The statement contained a syntax error. System Action: The member is not processed. User Response: Correct the member and re-issue the LOAD command.

5220I OK Explanation: A command has been processed successfully. System Action: Processing continues. User Response: None required.

5221W UNABLE TO OBTAIN SUFFICIENT CSA FOR name Explanation: There was a CSA shortage when trying to obtained storage for the named

control block. System Action: The command is ignored. User Response: Re-issue the command when the CSA shortage has been relieved.

Messages and Codes

ESP-5.4-MC-03 549

5222I ESP C/M TASK LIST Explanation: An LTASK command has been entered. System Action: A list will be produced of the active tasks. User Response: None required.

5223I NO AUTOMATION TASKS DEFINED Explanation: An LTASK was issued but there were no automation tasks defined. System Action: Processing continues. User Response: None required.

5224W THE NAME name IS USED BY A STREAM Explanation: The named item is not an automation task. System Action: The command is ignored. User Response: Re-issue the command with a valid task name.

5225I nnn SUBTASKS ATTACHED FOR TASK name Explanation: An AUTOTASK START command was entered and the subtasks have been

started. System Action: Processing continues. User Response: None required.

5226I nnn SUBTASKS SHUT DOWN FOR TASK name Explanation: An AUTOTASK STOP command was entered and the subtasks have been shut

down. System Action: Processing continues. User Response: None required.

5230A ENTER INPUT FOR COMMAND command, TASK name.id Explanation: A command has requested user input. System Action: Processing waits until the user has completed the input. User Response: Enter the appropriate input for the command.

5231E ERROR INITIALIZING REXX ENVIRONMENT FOR AUTOTASK name.id

Explanation: An internal error has been detected when trying to initialize for a REXX exec in an automation task.

System Action: The automation task will not invoke the REXX exec. User Response: Correct the error based upon previous messages and try again.

5240E ERROR SCANNING COMMAND, RC=nn Explanation: A syntax error has been detected when scanning an input command. System Action: The command is not processed. User Response: Re-issue the corrected command.

5250I command response Explanation: The MVSCMD command has issued an MVS command and the result of that

command is being displayed.

550 ESP-5.4-MC-03


5260E ESP C/M AUXILIARY SUBSYSTEM UNABLE TO INITIALIZE, SUBSYSTEM NAME MISSING

Explanation: No subsystem name has been defined in the ESP Console Manager initialization parameters.

System Action: ESP Console Manager terminates. User Response: Correct the problem and re-start ESP Console Manager.

5261E ESP C/M AUXILIARY ADDRESS SPACE ALREADY ACTIVE FOR SUBSYSTEM name

Explanation: The user has requested a PURGE or a COLD start but the auxiliary address space is already active.

System Action: Processing continues. User Response: FORCE the termination of the auxiliary address space and re-start ESP

Console Manager.

5262E UNABLE TO LOCATE SSCT FOR SUBSYSTEM name Explanation: An internal error has been detected. System Action: ESP Console Manager terminates. User Response: Contact Cybermation Technical Support.

5263E NO SUBSYSTEM VECTOR TABLE FOR SUBSYSTEM name Explanation: An internal error has been detected. System Action: ESP Console Manager terminates. User Response: Contact Cybermation Technical Support.

5264E INVALID SUBSYSTEM VECTOR TABLE FOR SUBSYSTEM name Explanation: An internal error has been detected. System Action: ESP Console Manager terminates. User Response: Contact Cybermation Technical Support.

5270W UNABLE TO LOCATE name VECTOR TABLE Explanation: An internal error has been detected. System Action: ESP Console Manager terminates. User Response: Contact Cybermation Technical Support.

5271E NOT AUTHORIZED TO ACCESS ESP C/M Explanation: You have invoked ESP Console Manager but the user verification exit has

denied the access. System Action: Your request has not been honored. User Response: Check with your systems programmer to obtain access permission.

5272W name SUBSYSTEM NOT ACTIVE Explanation: The named ESP Console Manager subsystem is not active. System Action: Your request is allowed but very few ESP Console Manager functions

will be operational.

Messages and Codes

ESP-5.4-MC-03 551

User Response: Insure that the ESP Console Manager subsystem is active and re-issue your request.

5273E SUBSYSTEM name IS NOT A ESP C/M SUBSYSTEM Explanation: You have specified a subsystem name that is not that of a ESP Console

Manager subsystem. System Action: Your request has been denied. User Response: Re-issue your request with a valid ESP Console Manager subsystem name.

5274E SUBSYSTEM name IS NOT A COMPATIBLE ESP C/M SUBSYSTEM Explanation: You have specified a subsystem name that is not that of a current ESP

Console Manager subsystem. System Action: Your request has been denied. User Response: Re-issue your request with a valid ESP Console Manager subsystem name.

5275E ERROR SCANNING COMMAND, RC=nn Explanation: A syntax command has been encountered while scanning a ESP Console

Manager command. System Action: The command is not processed. User Response: Re-issue a valid command.

5276I ESP C/M COMMAND ENDED Explanation: A ESP Console Manager command has successfully completed. System Action: Processing continues. User Response: None required.

5280W NO PARAMETERS, COMMAND IGNORED Explanation: You have issued a ESP Console Manager command with no parameters. System Action: The command is ignored. User Response: Re-issue a valid ESP Console Manager command.




will be operational. User Response: Insure that the ESP Console Manager subsystem is active and re-issue

your request.

5283I NO TIME ZONES DEFINED Explanation: An LTZONE command was entered but there were no time zones defined. System Action: Processing continues. User Response: None required.

552 ESP-5.4-MC-03

5290W NO PARAMETERS, COMMAND IGNORED Explanation: You have issued a ESP Console Manager command with no parameters. System Action: The command is ignored. User Response: Re-issue a valid ESP Console Manager command.




will be operational. User Response: Insure that the ESP Console Manager subsystem is active and re-issue

your request.

5293E ERROR OCCURRED STARTING AN AUTOMATION SUBTASK Explanation: Some error has been detected when starting an automation subtask. One

or more previous messages should indicate the nature of the error. System Action: The subtask is not started. User Response: Take corrective action based upon the messages issued.

5294E INVALID PROCEDURE NAME Explanation: An automation subtask has attempted to access an illegal procedure

name. System Action: The request is ignored. User Response: Re-issue a valid request.

5295E ERROR OCCURRED SCHEDULING THE PROCEDURE Explanation: Some error has been detected when attempting to schedule a procedure.

One or more previous messages should indicate the nature of the error. System Action: The procedure is not scheduled. User Response: Take corrective action based upon the messages issued.

5300W UNABLE TO OBTAIN SUFFICIENT CSA FOR name Explanation: There was a CSA shortage when trying to obtained storage for the named

control block. System Action: The command is ignored. User Response: Re-issue the command when the CSA shortage has been relieved.

5301C USERMOD Status Explanation: This message precedes the display of the currently active usermod

options. Usermod options are installation selectable user requested modifications.

System Action: None.

Messages and Codes

ESP-5.4-MC-03 553


7000E INVALID COMMAND, xxxx Explanation: An undefined command name was entered as an ESP/Encore command. System Action: The command is ignored. The TSO user is prompted for a new command. User Response: A TSO user should reenter the command with the correct name. A batch

user should correct the command for the next execution.

7001W RC nn WHILE OPENING ENCORE EXH FILE IN CYBRM314 Explanation: ESP Encore was unable to open the EXH file. System Action: The EXH file will not be updated by ESP Encore. User Response: Make sure that the EXH file has been allocated and formatted, and

that its name is specified in the EXHFILE statement in the ESP/WM initialization parameters.

7002W RC nn WHILE READING SLOT 0 IN CYBRM314 Explanation: The ESP Encore EXH file has not been properly formatted. System Action: The EXH file will not be updated by ESP Encore. User Response: Make sure that the EXH file has been allocated and formatted, and


7003W ENCORE EXH FILE SLOT ZERO IN ERROR Explanation: The ESP Encore EXH file has either not been formatted or has been

damaged. System Action: The EXH file will not be updated by ESP Encore. User Response: Make sure that the EXH file has been allocated and formatted, and


7004W ENCORE EXH FILE USAGE IS BECOMING CRITICAL (nn% FULL) Explanation: The ESP Encore EXH file has exceeded the "high" threshold value

specified in the CYBRMTHR sample job. System Action: None. User Response: Run the CYBRMPRG sample job to remove unneeded records from the file.

7005W ENCORE EXH FILE USAGE REMAINS CRITICAL (%nn FULL) Explanation: The ESP Encore EXH file still exceeds the "low" threshold value

specified in the CYBRMTHR sample job. System Action: This message is issued every five minutes until the EXH file usage

becomes lower than the "low" threshold value. User Response: Run the CYBRMPRG sample job to remove unneeded records from the file.

7006I ENCORE EXH FILE SHORTAGE IS NOW RELIEVED (nn% FULL) Explanation: The ESP Encore EXH file is now lower than the "high" threshold value

specified in the CYBRMTHR sample job. System Action: None. User Response: None.

554 ESP-5.4-MC-03

7010I ESP ENCORE (SUBSYS=xxxx) ALREADY ACTIVE Explanation: The ESP Encore system is already active. System Action: None. User Response: None.

7011I ESP ENCORE (SUBSYS=xxxx) ACQUIRING EXHVT Explanation: The ESP Encore subsystem is allocating an EXHVT control block. This

informational message is issued when the ESP Encore subsystem is starting for the first time since the last IPL.


7012I ESP ENCORE (SUBSYS=xxxx) PC NUMBER yyyy Explanation: The ESP Encore subsystem has chosen a PC number. This informational

message is issued when the ESP Encore subsystem is starting for the first time since the last IPL.


7013S ESP ENCORE (SUBSYS=xxxx) CROSS MEMORY ENV COULD NOT BE ESTABLISHED

Explanation: ESP Encore was not able to establish a cross memory environment. System Action: ESP Encore is not properly started. User Response: Please contact Cybermation.

7014I ESP ENCORE (SUBSYS=xxxx) NOW ACTIVE Explanation: ESP Encore is now active. System Action: None. User Response: None.

7015I ESP ENCORE (SUBSYS=xxxx) IMMEDIATE SHUTDOWN Explanation: An immediate shutdown of the ESP Encore auxiliary address space has

been requested. System Action: The auxiliary address space will shut down. User Response: None.

7020W ESP ENCORE (SUBSYS=xxxx) n EXH REQUESTS QUEUED Explanation: The ESP Encore subsystem has a large number of requests queued in

the auxiliary address space. This message is issued to alert operations to a possible problem. It will be reissued, no more frequently than once every five minutes, as long as the queue remains above the threshold limit.

System Action: None. User Response: Investigate possible causes for the backlog. Encore may be quiesced,

or ESP may be down.

Messages and Codes

ESP-5.4-MC-03 555

7021I ESP ENCORE (SUBSYS=xxxx) EXH REQUEST QUEUE NOW OKAY Explanation: The system previously issued message 7020W indicating a possible

problem with ESP Encore. The queue length has now fallen below 80% of the threshold value.


7022E ESP ENCORE (SUBSYS=xxxx) EXH REQUEST FAILED Explanation: The ESP Encore subsystem has rejected a request from this job to

queue information to Encore. This is generally caused by exhaustion of virtual storage in the auxiliary address space. Message 7020E is issued long before this stage is reached, but may not have been responded to.

System Action: If this happens during processing of the Encore step, the job will be flushed. If it is detected in the SMF intercept, processing continues, but a restart of this job may not be correct.

User Response: Investigate possible causes for the backlog. Encore may be quiesced, or ESP may be down.

7030I ESP ENCORE (COMPRESSING) (QUIESCED) Explanation: This message is in response to the ENCPARM STATUS operator command.

It indicates whether or not ESP Encore is compressing records and whether or not it is quiesced.


7031E THE AUXILIARY ADDRESS SPACE HAS NOT BEEN PROPERLY INITIALIZED

Explanation: The PC numbers in the ESP auxiliary address space are zero. System Action: The job is not recorded in the ESP Encore EXH file, and can therefore

not be tracked by ESP Encore nor restarted. User Response: Contact Cybermation.

7032E THE AUXILIARY ADDRESS SPACE HAS RESPONDED RC=<rc> TO A PC0

Explanation: ESP Encore tried to communicate with the auxiliary address space with a PC0 call, but a return code of <rc> was returned.

System Action: The job is not recorded in the ESP Encore EXH file, and can therefore not be tracked by ESP Encore nor restarted.

User Response: Contact Cybermation.

7033E THE WRONG ESP SYSTEM HAS BEEN IDENTIFIED Explanation: The XASV control block contains the incorrect job number. This

usually results from ESP Encore not finding the correct ESP system with which to track this job.

System Action: The job is not fully recorded in the ESP Encore EXH file, and can

556 ESP-5.4-MC-03

therefore neither be tracked by ESP Encore nor restarted. User Response: Rerun the job with ENCPARM TRACE CYBRM501. This will add some

diagnostic output to the ESP Encore report. This output will indicate which ESP system has been identified as the one with which the job should be tracked. Once this output has been produced, please contact Cybermation for further assistance.

7034E AN ERROR HAS OCCURRED WITH SMF INTERCEPTION Explanation: The XASVNOTR switch is turned off, so that ESP is not tracking

this job. This can result from the wrong ESP system being identified or from a problem with SMF interception.

System Action: The job is not fully recorded in the ESP Encore EXH file, and can therefore not be tracked by ESP Encore nor restarted.

User Response: Recycle ESP with the RELOAD option and rerun the job. If the problem persists then contact Cybermation.

7035E AN ERROR HAS OCCURRED WITH SMF INTERCEPTION Explanation: The XASV control block contains no ALD pointer. This usually

results from the SMF intercept routine not operating correctly. System Action: The job is not fully recorded in the ESP Encore EXH file, and can

therefore not be tracked by ESP Encore nor restarted. User Response: Recycle ESP with the RELOAD option and rerun the job. If the

problem persists then contact Cybermation.

7036E AN ERROR HAS OCCURRED WITH SMF INTERCEPTION Explanation: The ALD that is pointed to by the XASV is invalid. This usually

results from the SMF intercept routine not operating correctly. System Action: The job is not fully recorded in the ESP Encore EXH file, and can

therefore not be tracked by ESP Encore nor restarted. User Response: Recycle ESP with the RELOAD option and rerun the job. If the

problem persists then contact Cybermation.

7037E JOB <jobname> #(<jobnum>) IS TOO LARGE, RESTART IMPOSSIBLE Explanation: The job is too large to be restarted. The job processes too many

files. The total number of files includes both those allocatedd using DD JCL statements and those allocated dynamically. Encore's in memory work area is used to store restart analysis information and current and historical job and step information. When this work area is exhausted, Encore cannot continue and issues this message.

System Action: The restart of the job is abandoned. User is notified. User Response: If the total number of files is nearing the 8,000 limit, decrease

the total number of files the job processes. If there are too many steps, break the job into several smaller jobs.

7040I THIS IS A RESTART OF JOB jobname (Jjobnumber) Explanation: Part of series of informational messages written to ESP Encore job log.

Messages and Codes

ESP-5.4-MC-03 557


7041I ORIGINALLY RUN AT time ON date Explanation: Part of series of informational messages written to ESP Encore job log. System Action: N/A User Response: N/A

7043I (THIS JOB WAS ITSELF A RESTART OF JOB Jjobnumber) Explanation: Part of series of informational messages written to ESP Encore job log. System Action: N/A User Response: N/A

7044I RESTARTING FROM STEP stepname Explanation: Part of series of informational messages written to ESP Encore job log. System Action: N/A User Response: N/A

7045I TO STEP stepname Explanation: Part of series of informational messages written to ESP Encore job log. System Action: N/A User Response: N/A

7060E RACINIT FOR USER xxxx FAILED, ERROR CODE yy-zz Explanation: A RACINIT request failed in a task that was getting ready to process

an ENCREQ request on behalf of a user. A few examples of error code values are listed below: 4-4 User not defined to RACF 8-4 User not defined to RACF 8-8 Invalid password given 8-12 Password is expired and no new password supplied 8-16 New password not valid to RACF 8-28 User ID is revoked 8-100 User ID is valid, but no access allowed to ESP 8-104 Second copy of new password doesn't match first

System Action: The request is not processed. User Response: Compare the error code to the error codes associated with the

installation's security facility.

7070E Execution halted because of an error in an ESP Encore command Explanation: An ESP Workload Manager was processing an ENCREQ request and

encountered an error after executing an Encore command invoked by this request.

System Action: The ENCREQ request is stopped. User Response: Look for relevant messages in the command execution summary and,

if appropriate, re-issue the corrected command.

558 ESP-5.4-MC-03

7071I ESP ENCORE COMMAND: xxxx Explanation: An ESP Workload Manager was processing an ENCREQ request that

invoked the Encore command displayed in this message. System Action: Processing continues. User Response: None.

7080E Error scanning command, RC=nn Explanation: A syntax error has been detected when scanning an input command. System Action: The command is not processed. User Response: System routine IKJPARS returned error code nn.


7081E CPEENQ ERROR: Invalid xxxx specification[: yyyy] Explanation: Argument xxxx in an ENCREQ command contains the invalid value yyyy. System Action: The command is not processed. User Response: Re-issue the corrected command.

7082E ENCREQ ERROR: <error message> Explanation: An error occurred during the processing of an ENCREQ command. System Action: Processing continues. User Response: If the syntax of the command is correct, decide how to proceed based

on the error message.

7083I ENCREQ INFO: <informational message> Explanation: This message contains diagnostic information about the outcome of

an ENCREQ command. System Action: Processing continues. User Response: None.

7084E TOO MANY EXCLUDED STEPS: nn Explanation: The number of excluded steps in an ENCREQ command exceeds the limit

established for the AJ command. System Action: The command is not processed. User Response: Reduce the number of items in the excluded-step list and re-issue

the command.

7085E PREVTIME invalid: xxxx Explanation: An ENCREQ command contains an invalid value for the PREVTIME

argument.

Messages and Codes

ESP-5.4-MC-03 559

System Action: The command is not processed. User Response: Correct the value of the PREVTIME argument and re-issue the command.

7086E The ESP Workload Manager does not support the ENCREQ command: <reason>

Explanation: An ENCREQ subsystem request cannot be relayed to the ESP Workload Manager because the Workload Manager is not equipped to process the request.

System Action: The subsystem request is not processed. User Response: Switch to an ESP Workload Manager that does support the ENCREQ

subsystem request.

7090E ESP ENCORE UI Service error - Subsystem error xx-yy Explanation: A request was made to the ESP subsystem, but an error occurred.

xx is the value returned in register 15 by program CYBSS005 and yy is the value of XSCMRETCD.



7091E ESP ENCORE UI Service error - Subsystem request failed: aa [bb], ERROR CODE cc-dd

Explanation: A request was made to the ESP subsystem, but an error occurred. aa and bb identify the type of subsystem request. xx is the value returned in register 15 by program CYBSS005 and yy is the value of XSCMRETCD.



7092E ESP ENCORE UI Service error - A required record could not be read from a slot file

Explanation: A subsystem request failed because an error occurred when the ESP Workload Manager tried to read a slot-file record. The desired record may have been freed or reused.

System Action: Processing continues. User Response: Re-issue the request. If the error persists, contact Cybermation.

7093E ESP ENCORE UI Service error - <error message> Explanation: An error occurred during the processing of an ENCREQ subsystem

request. System Action: Processing continues. User Response: Decide how to proceed based on the error message.

560 ESP-5.4-MC-03

7094E ESP ENCORE UI Service error - Serialization-control error – aaaa failure: [TOKEN(token)] <reason> Flags: Error=X'bbbb' Info=X'cccc'

Explanation: The CPEENQ request aaaa failed for the reason displayed. The conditions most likely to make this message appear would be that another user already holds the requested lock or that the lock has expired.

System Action: Processing continues. User Response: Examine the reason given in this message and decide whether to retry.

7095E ESP ENCORE UI Service error - A subsystem request to NETNODE aaaa failed because of a network problem detected by the Network Delivery Services

Explanation: The Network Delivery Services were unable to route a request to a destination NETNODE and receive the response in a limited time. This message should be preceded by an explanatory message such as 3372 or 3373. The target NETNODE may be disconnected or a time-out may have occurred in the network or in an ESP Workload Manager.

System Action: Processing continues. User Response: Check the previous message. Retrying the request might succeed

if the underlying problem is transitory.

7096E ESP ENCORE UI Service error - Requested generation aa of application bb not found

Explanation: The ATR (Application Tracking Record) for generation aa of application bb could not be retrieved.

System Action: Processing continues. User Response: Ensure you have specified the correct application name and generation

number.

7097E ESP ENCORE UI Service error - Application-level data not found for job aa in application bb, generation cc

Explanation: The AJQE (Application Job Queue Element) for job aa of application bb, generation cc could not be retrieved.

System Action: Processing continues. User Response: Ensure you have specified the correct application name, generation

number, and job name.

7099I DDN=xxxxxxxx RC=n ERROR=yyyy INFO=zzzz Explanation: The auxiliary address space has completed initialiation, and

attempted to deallocate the task library from which modules were potentially fetched. This allocation is identical to the STEPLIB provided in the ESP/WM started task. The unallocation was not successful. This message contains the SVC 99 return code in decimal, and the error and information codes in hex. This condition, and message, are not expected to occur.

System Action: Processing continues. Although closed, the data sets remain allocated to the auxiliary address space.

Messages and Codes

ESP-5.4-MC-03 561

User Response: If this message is issued, you may wish to investigate the the meaning and cause of the indicated unallocation condition.

7100W EXH data set xxxx is not properly formatted Explanation: The Execution History file is not formatted. This is expected the

first time the data set is used. System Action: ESP Encore follows with message 7101. User Response: Respond to message 7101.

7101A Reply 'Y' to format the EXH file, or reply 'N' Explanation: The EXH file was found to be unformatted, or improperly formatted.

Before proceeding to format it, Encore requests permission from the operator.

System Action: Encore waits for the reply. User Response: If you wish the EXH file to be formatted, reply Y, otherwise reply N

and Encore will terminate. The tracking file should only need to be formatted once, or after it has been newly created. If this is not the first time the data set is used, call your software support personnel.

7102W Invalid response Explanation: An invalid response was given to message 7101A. System Action: The prompt is reissued. User Response: Respond to the prompt.



7104E Correct the above problem and restart ESP Explanation: This message is issued after an error has occurred that prevents



7104I Starting to format the EXH file Explanation: The formatting run of the EXH file has begun. You may expect this to

take an appreciable amount of time. System Action: The EXH file is formatted. User Response: None. Be patient.

7106I EXH file format complete Explanation: The formatting run of the EXH file has been completed. System Action: Processing continues. User Response: None.

562 ESP-5.4-MC-03

7116I ESP ENCORE QUIESCE IN PROGRESS. EXH FILE USE COUNT: nn Explanation: An ENCPARM QUIESCE command has been issued to an ESP Workload

Manager, but the EXH file is currently in use by one or more process in the ESP Workload Manager's address space.

System Action: The Encore task that executes the ENCPARM QUIESCE logic in the ESP Workload Manager's address space waits for the EXH file use count to drop to zero.

User Response: Wait for the ENCPARM QUIESCE to take effect.

7117I EXH FILE INCOMPLETEKEEP= PARAMETER CHANGED FROM nn TO nn

Explanation: The INCOMPLETEKEEP parameter that controls the retention of the "incomplete job groups" has been changed and the change just become active. The change of the parameter is done using CYBRMKEP utility. (The INCOMPLETEKEEP parameter specifies the number of incomplete job groups that are to be kept on the EXH file.)


7118I EXH FILE AGE= PARAMETER CHANGED FROM nn TO nn Explanation: The AGE parameter that controls the retention of the

"complete job groups" has been changed and the change just become active. The change of the parameter is done using CYBRMKEP utility. (The AGE parameter specifies the minimum number of days a complete job group is kept on the EXH file.)


7119I EXH FILE INCOMPLETEAGE= PARAMETER CHANGED FROM nn TO nn

Explanation: The INCOMPLETEAGE parameter that controls the retention of the "incomplete job groups" has been changed and the change just become active. The change of the parameter is done using CYBRMKEP utility. (The INCOMPLETEAGE parameter specifies the minimum number of days an incomplete job group is kept on the EXH file.)


7120W EXH FILE INDEX DAMAGE HAS BEEN CORRECTED AFTER JOB xxxx Explanation: ESP Encore has detected corruption within an EXH file index record.

That damage has now been corrected. System Action: None. User Response: If several different systems are sharing an EXH file, make sure that

ESP's QNAMEs are correctly defined to GRS and/or MIM.

7121W EXH FILE INDEX DAMAGE HAS BEEN CORRECTED FOR JOB xxxx Explanation: ESP Encore has detected corruption within an EXH file index record.

Messages and Codes

ESP-5.4-MC-03 563

That damage has now been corrected. System Action: None. User Response: If several different systems are sharing an EXH file, make sure that

ESP's QNAMEs are correctly defined to GRS and/or MIM.

7122I EXH FILE KEEP= PARAMETER CHANGED FROM nn TO nn Explanation: The KEEP parameter that controls the retention of the

"complete job groups" has been changed and the change just become active. The change of the parameter is done using CYBRMKEP utility. (The KEEP parameter specifies the number of instances of the completed job groups that are to be kept on the EXH file.)


7123W THE EXH FILE CONTAINS xxxx ENTRIES FOR JOB yyyy (LOOP-SAFEGUARD LIMIT IS zzzz)

Explanation: ESP Encore has found a very high number of entries, xxxx, for job yyyy in the index of the EXH file. If this number is greater than zzzz, ESP Encore assumes that an infinite loop has appeared in the EXH file's index and discards the entire index chain for job yyyy.

System Action: None. User Response: A purge job should be run in order to reduce the number of old

jobs in the EXH file. A sample purge job can be found in the CYBRMPRG member of the SSCPSAME library.

7124I ESP ENCORE PREVIOUSLY IN QUIESCED STATE Explanation: This message may appear when an ESP Workload Manager is

restarted. It means that ESP Encore was in a quiesced state when the ESP Workload Manager was previously shut down.

System Action: ESP Encore remains quiesced. User Response: To restart ESP Encore, issue an ENCPARM RESTART command.

7125I ESP ENCORE IS ALREADY QUIESCED Explanation: An ENCPARM QUIESCE command has been issued by an operator, or by a

user as an OPER command, but ESP Encore is already quiesced. System Action: None. User Response: None.

7126I ESP ENCORE IS NOW QUIESCED Explanation: The Encore recording task has been quiesced. Either an error was

encountered writing to the EXH file, or an ENCPARM QUIESCE command has been issued by an operator, or by a user as an OPER command. Encore has now completed the execution of the request, and is now quiesced. Requests will be accumulated in the auxiliary address space until Encore's recording function is restarted. Note: The quiesced state will be remembered across restarts of ESP, but not across an IPL.

System Action: None.

564 ESP-5.4-MC-03

User Response: When appropriate, issue an ENCPARM RESTART command. If Encore internally issued the quiesce request, investigate the cause of the error and take corrective action prior to issuing ENCPARM RESTART. Issuing an "ENCPARM RESTART" command automatically through automation is definitely not recommended.

7127I ESP ENCORE IS NOT QUIESCED Explanation: An ENCPARM RESTART command has been issued by an operator, or by a

user as an OPER command. However, ESP Encore is not quiesced, so that it doesn't need to be restarted.


7128E UNABLE TO REALLOCATE EXH FILE Explanation: An ENCPARM RESTART command has been issued by an operator, or by a

user as an OPER command. However, ESP Encore is unable to allocate the EXH file.

System Action: None. ESP Encore remains quiesced. User Response: Make sure that the EXH file is cataloged, has been properly

formatted, and is not allocated to any other batch job or user.

7129I ESP ENCORE IS NOW RESTARTED Explanation: An ENCPARM RESTART command has been issued by an operator, or by a

user as an OPER command. System Action: ESP Encore is restarted. Activity to the EXH file has been resumed. User Response: None.

7130E XSSV IS INVALID. BACKGROUND TASKS CANNOT START Explanation: The ESP environment has been corrupted. System Action: ESP Encore is not started. User Response: Recycle ESP with PURGE.

7131E THE WRONG VERSION OF ESP ENCORE IS ACTIVE IN THE AUXILIARY ADDRESS SPACE

Explanation: Version 2 of ESP Encore has been installed, but an older version of Encore created the existing auxiliary address space.

System Action: ESP Encore is not started. User Response: Recycle ESP with PURGE.

7132E PLEASE SHUT DOWN THE AUXILIARY ADDRESS SPACE AND THEN RECYCLE ESP

Explanation: Follows message 7131. System Action: ESP Encore is not started. User Response: Issue the ESP AUX_AS CANCEL command. Then, recycle ESP.

7140I ESP ENCORE EXH FILE ERROR <rc> WHILE <operation> Explanation: An error has occurred while updating the EXH file. The <operation>

field indicates what I/O operation was being performed. The <rc>

Messages and Codes

ESP-5.4-MC-03 565

indicates the nature of the error: <rc> = 8: The EXH file is not formatted. The CYBRMALC utility job must be run in order to properly create and format the EXH file. <rc> = 16: A physical I/O error has occurred on the EXH file. It needs to be recreated with the CYBRMALC job. <rc> = 20: The EXH file is full. A larger EXH file must be created (with CYBRMALC), and then the old file can be copied into the new one with the CYBRMCPY utility job. Any other <rc> value should be reported to Cybermation.

System Action: I/O activity with the EXH file is suspended. User Response: Quiesce ESP Encore, correct the problem with the EXH file, and then

restart ESP Encore. The commands to use are: F ESP,ENCPARM QUIESCE and F ESP,ENCPARM RESTART

7170I ENCPARM DELETED Explanation: An ENCPARM DELETE statement was entered, and the ENCPARM has been

successfully deleted from the list of default ENCPARMs. System Action: The specified ENCPARM was deleted. User Response: None.

7171I DEFAULT ENCPARMS Explanation: This message lists the default ENCPARMs. These are the ENCPARM

statements that will be added to every job that is being tracked ESP Encore.


7175E ENCPARM NOT DELETED Explanation: An ENCPARM DELETE statement was entered, but the specified number

was invalid. System Action: No ENCPARM was deleted. User Response: Correct the statement and enter it again.

7186W JOB <jobname> JOB #(<jobnum>) TRACKING SUSPENDED DUE TO JOB SIZE

Explanation: The named job is being flagged by ENCORE as a 'large job', and is beyond ENCORE's tracking capability. ENCORE's definition of a 'large job' is a job containing approx 11K+ JCL DD statements.

System Action: The job continues to execute. ENCORE does not store any more information on this job in its EXH file.

User Response: This job is not a candidate for tracking or restart using ENCORE.

566 ESP-5.4-MC-03

Use the job name and job number supplied in the message to find an ESP application that should have the job, or the OPTIONS RESTARTSTEP parameter, removed.

7187W JOB <jobname> #(<jobnum>) WAS TOO LARGE TO BE TRACKED BY ENCORE

Explanation: The named job has just ended or abended. The user is reminded that this job was flagged by ENCORE as a 'large job', and was beyond ENCORE's tracking capability. ENCORE's definition of a 'large job' is a job containing approx 11K+ JCL DD statements.

System Action: The job ends or abends. User Response: This job was not a candidate for tracking or restart using

ENCORE. Use the job name and job number supplied in the message to find an ESP application that should have the job, or the OPTIONS RESTARTSTEP parameter, removed. Do not restart this job using ENCORE.

7188W JOB <jobname> #(<jobnum>) IF ABENDED, RERUN FROM THE BEGINNING

Explanation: The named job has just ended or abended. The user is reminded that this job was flagged by ENCORE as a 'large job', and was beyond ENCORE's tracking capability. ENCORE's definition of a 'large job' is a job containing approx 11K+ JCL DD statements.

System Action: The job ends or abends. User Response: This job was not a candidate for tracking or restart using

ENCORE. Use the job name and job number supplied in the message to find an ESP application that should have the job, or the OPTIONS RESTARTSTEP parameter, removed. Do not restart this job using ENCORE.

7189I BAD DATA FOUND IN EXH INDEX RECORD AT SLOT xxxx Explanation: ESP Encore has detected corruption within an EXH file index record. System Action: None. User Response: A Sanity Check should be run in order to search for other damaged

areas. This job is the CYBRMSAN member in your SSCPSAME library.

7190E CSI error, xxxx Explanation: The accessor of the CSI (Catalog Search Interface) received an error

while searching the system catalog. xxxx specifies the reason for the CSI (Catalog Search Interface) error.

System Action: Depending upon the severity of the problem, the program may either terminate with a severe error, or in case of a non severe error, the CSI interface is disabled and catalog searches revert to an older method using IDCAMS. When the program does not abnormally terminate, the processing is not effected.

User Response: A. When the program does not abnormally terminate, the processing is

Messages and Codes

ESP-5.4-MC-03 567

not effected. No action is required. B. When the program terminates abnormally, the CSI interface needs to be disabled and the job needs to be reexecuted. C. To disable CSI interface, please add this command to your Initialization parameters: ENCPARM MODIFY USECSI(NO) D. Please report all severe errors to Cybermation technical support. E. Some error messages have reason and return codes. These reason and return codes can be found in IBM documentation GC28-1786 MVS System Messages (EWX-IEB). Please refer to the description of the message IDC3009I. In some instances, the problem may be specific to your installation and you may be able to correct it. In all other instances, please contact Cybermation technical support.

7199E RACROUTE CREATE FAILED FOR USER xx IN CYBRM974, SAF ERROR CODE yy-zz

Explanation: A RACINIT request failed in a task that was getting ready to issue one or more IDCAMS command on behalf of a user. A few examples of error code values are listed below: 4-4 User not defined to RACF 8-4 User not defined to RACF 8-8 Invalid password given 8-12 Password is expired and no new password supplied 8-16 New password not valid to RACF 8-28 User ID is revoked 8-100 User ID is valid, but no access allowed to ESP 8-104 Second copy of new password doesn't match first

System Action: The request is not processed. User Response: Compare the error code to the error codes associated with the

installation's security facility.

7200E DATA SET NOT AVAILABLE: <dsname> Explanation: The named data set is not available for ENQ by ESP Encore.

This message will only occur if ENCPARM MODIFY GDGENQ(YES) has been specified. It is generally due to a concurrently executing disk maintenance job having hold of a number of GDG generation data sets.

System Action: The job does not execute. User Response: Rerun the job after the maintenance job has completed.

568 ESP-5.4-MC-03

ESP Workload Manager Messages and Codes

Documents

Transcript of ESP Workload Manager Messages and Codes