ESP Codes and Messages

CA Workload Automation ESP
Edition
Message Reference Guide

Release 11.4
This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to
as the Documentation) is for your informational purposes only and is subject to change or withdrawal by CA at any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without
the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed
by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing
your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and
CA.
Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may
print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your
employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced
copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable
license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to
certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY
KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,
DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE
POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such
license agreement is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is CA.
Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions
set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or
their successors.
Copyright 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to
their respective companies.
CA Technologies Product References

This topic lists the CA Technologies products that are referenced by the CA Workload
Automation ESP Edition (CA WA ESP Edition) documentation.
Note: The names in parenthesis are the shorter product names that are used in the
documentation.
CA ACF2 (CA ACF2)
CA Librarian Base for z/OS (CA Librarian for z/OS )
CA Mainframe Software Manager (CA MSM)
CA OPS/MVS Event Management and Automation (CA OPS/MVS)
CA Top Secret (CA Top Secret)
CA Workload Automation Agent for Application Services (CA WA Agent for

Application Services)
CA Workload Automation Agent for Databases (CA WA Agent for Databases)
CA Workload Automation Agent for HP Integrity NonStop
CA Workload Automation Agent for i5/OS (CA WA Agent for i5/OS)
CA Workload Automation Agent for Micro Focus (CA WA Agent for Micro Focus)
CA Workload Automation Agent for Microsoft SQL Server
CA Workload Automation Agent for Oracle E-Business Suite (CA WA Agent for
Oracle E-Business Suite)
CA Workload Automation Agent for PeopleSoft (CA WA Agent for PeopleSoft)
CA Workload Automation Agent for Remote Execution
CA Workload Automation Agent for SAP (CA WA Agent for SAP)
CA Workload Automation Agent for UNIX, Linux, or Windows
CA Workload Automation Agent for Web Services (CA WA Agent for Web Services)
CA Workload Automation Agent for z/OS (CA WA Agent for z/OS)
CA Workload Automation AE
CA Workload Automation CA 7 Edition
CA Workload Automation DE
CA Workload Automation ESP Edition (CA WA ESP Edition)
CA Workload Automation High Availability ESP Edition (CA WA High Availability ESP
Edition)
CA JCLCheck Workload Automation (CA JCLCheck )
CA Workload Automation Restart Option ESP Edition (CA WA Restart Option ESP
Edition)
CA Workload Automation Restart Option for z/OS Schedulers (CA WA Restart

Option for z/OS Schedulers)
CA Workload Automation Service Governor ESP Edition (CA WA Service Governor

ESP Edition)
CA Workload Automation Workstation ESP Edition (CA WA Workstation ESP Edition)
Contact CA Technologies
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the
information that you need for your Home Office, Small Business, and Enterprise CA
Technologies products. At http://ca.com/support, you can access the following
resources:
Online and telephone contact information for technical assistance and customer
services
Information about user communities and forums
Product and documentation downloads
CA Support policies and guidelines
Other helpful resources appropriate for your product
Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you
can send a message to techpubs@ca.com.
To provide feedback about CA Technologies product documentation, complete our
short customer survey which is available on the CA Support website at
http://ca.com/docs.
Documentation Changes
The following documentation updates have been made since the last release of this
documentation:
Sending User Messages to OPS/MVS
Added messages 6660 to 6668.
zIIP Processor Support for CA WA ESP Edition
Added messages 4471 to 4488.
Messages for Control File Usage
Added new messages 1070 to 1072, and 1290
Reporting Whether Event Triggered with Replace or Add Option
Updated message 6150
Queuing Operator Commands When CA WA ESP Edition is Down
Added new messages 0445 to 0447, 0504, 1075 to 1078, and 6457 and 6458.
Updated messages 4362 to 4364.
Cleanup Utility for the Jobstats Data Set
Added messages 4028 and 4029
Adding a Restart Step to All Jobs
Added messages 1073E and 1074E
CA Interface to IBM Health Checker
Updated message 6449
Performance Metrics
Added new messages 4489 to 4495, 6501 to 6535, and 6551 to 6565
Conditional Job Release Based on a Step Completion Code
Added new message 2082E
Incrementing and Decrementing Resources
Added messages 2083 and 2084.
Documentation Fixes
Added missing message 772E
Added messages 1987E, 2051E, 3398I, and 3399I
4669SRemoved a reference to CWSS (Consolidated Workstation Server) in the

Reason section.
Contents
Chapter 1: Messages 001 Through 999
001 - 099 ...................................................................................................................................................................... 9

100 - 199 .................................................................................................................................................................... 44
200 - 299 .................................................................................................................................................................... 80
300 - 399 .................................................................................................................................................................. 117
400 - 499 .................................................................................................................................................................. 153
500 - 599 .................................................................................................................................................................. 190
600 - 699 .................................................................................................................................................................. 228
700 - 799 .................................................................................................................................................................. 267
800 - 899 .................................................................................................................................................................. 302
900 - 999 .................................................................................................................................................................. 336
367
1000 - 1099 .............................................................................................................................................................. 367

1100 - 1199 .............................................................................................................................................................. 397
1200 - 1299 .............................................................................................................................................................. 435
1400 - 1499 .............................................................................................................................................................. 477
1500 - 1599 .............................................................................................................................................................. 511
1600 - 1699 .............................................................................................................................................................. 542
1700 - 1799 .............................................................................................................................................................. 577
1800 - 1899 .............................................................................................................................................................. 613
1900 - 1999 .............................................................................................................................................................. 647
681
2000 - 2099 .............................................................................................................................................................. 681

2100 - 2199 .............................................................................................................................................................. 717
2200 - 2299 .............................................................................................................................................................. 745
2300 - 2399 .............................................................................................................................................................. 776
2400 - 2499 .............................................................................................................................................................. 810
2500 - 2599 .............................................................................................................................................................. 846
2600 - 2699 .............................................................................................................................................................. 882
2700 - 2799 .............................................................................................................................................................. 917
2800 - 2899 .............................................................................................................................................................. 940
2900 - 2999 .............................................................................................................................................................. 962
Contents 7
965
3000 - 3099 .............................................................................................................................................................. 965

3100 - 3199 .............................................................................................................................................................. 974
3200 - 3299 .............................................................................................................................................................. 976
3300 - 3399 ............................................................................................................................................................ 1034
3400 - 3499 ............................................................................................................................................................ 1062
3500 - 3599 ............................................................................................................................................................ 1095
3600 - 3699 ............................................................................................................................................................ 1130
3700 - 3799 ............................................................................................................................................................ 1163
3800 - 3899 ............................................................................................................................................................ 1176
3900 - 3999 ............................................................................................................................................................ 1193
1195
4000 - 4099 ............................................................................................................................................................ 1195

4100 - 4199 ............................................................................................................................................................ 1222
4200 - 4299 ............................................................................................................................................................ 1254
4300 - 4399 ............................................................................................................................................................ 1291
4400 - 4499 ............................................................................................................................................................ 1333
4500 - 4599 ............................................................................................................................................................ 1365
4600 - 4699 ............................................................................................................................................................ 1400
4700 - 4799 ............................................................................................................................................................ 1423
4800 - 4899 ............................................................................................................................................................ 1460
4900 - 4999 ............................................................................................................................................................ 1492
1525
6000 - 6099 ............................................................................................................................................................ 1525

6100 - 6199 ............................................................................................................................................................ 1547
6200 - 6299 ............................................................................................................................................................ 1568
6300 - 6399 ............................................................................................................................................................ 1574
6400 - 6499 ............................................................................................................................................................ 1578
6500 - 6599 ............................................................................................................................................................ 1597
6600 - 6699 ............................................................................................................................................................ 1614
6900 - 6999 ............................................................................................................................................................ 1635
7000 - 7099 ............................................................................................................................................................ 1667
7100 - 7199 ............................................................................................................................................................ 1687
7200 - 7299 ............................................................................................................................................................ 1703
7300 - 7399 ............................................................................................................................................................ 1704
8 Message Reference Guide

This chapter contains messages numbered from 001 through 999.
Note: Not all numbers have a message. If a message number is not listed, then there is
no message with that number.
001 - 099
001E
UNBALANCED PARENTHESES
Reason:
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.
Action:
Correct the command and retry.
002E
INVALID STRING
Reason:
A string was not properly enclosed within single quotation marks.
System Action:
The command containing the string is not executed.
Action:
Ensure the string is enclosed within single quotation marks.
Chapter 1: Messages 001 Through 999 9
001 - 099
003E
Data set is not opened
Reason:
The data set could not be opened.
System Action:
The utility function was not performed.
Action:
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.
004E
INVALID STATEMENT SYNTAX
Reason:
The reverse Polish statement contains a syntax error.
System Action:
The statement is not evaluated.
Action:
Correct the statement and try again.
005E
OPERATOR OUT OF SEQUENCE
Reason:
An infix operator must follow a value.
System Action:
Action:
001 - 099
006E
INCOMPATIBLE DECLARE OPTIONS SPECIFIED
Reason:
A DCL statement is incomplete. No variable names have been specified.
System Action:
The requested function is not completed.
Action:
Correct the DCL statement and try again.
007E
INVALID VARIABLE NAME xxxx
Reason:
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:
Action:
Correct the DCL statement and try again.
008E
UNDEFINED DATA TYPE xxxx
Reason:
The only valid data types are CHAR, BIN, FIXED, BOOLEAN and NOSTRIP.
System Action:
Action:
001 - 099
009E
CONFLICTING VARIABLE TYPES
Reason:
The statement should only contain one data type keyword.
System Action:
Action:
010E
SYNTAX ERROR IN EXPRESSION
Reason:
The expression contains too few arguments.
System Action:
The expression is not evaluated.
Action:
Correct the expression and try again.
011E
OPERATOR USE INCONSISTENT WITH DATA TYPE
Reason:
An operator is being applied to arguments of the wrong type.
System Action:
Action:
001 - 099
012E
INVALID EXPRESSION
Reason:
The C-language expression is syntactically incorrect.
System Action:
Action:
013E
VARIABLE xxxx NOT DEFINED
Reason:
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.
Action:
Add a variable declaration or assignment statement and try again.
014E
INTERMEDIATE STRING LENGTH EXCEEDS MAXIMUM
Reason:
During an addition operation, the combined string length exceeds 2048 characters.
System Action:
Action:
Correct the program and try again.
001 - 099
015E
SYNTAX ERROR IN EXPRESSION
Reason:
The expression contains too few arguments.
System Action:
Action:
016E
OPERATOR USE INCONSISTENT WITH DATA TYPE
Reason:
An operator is being applied to arguments of the wrong type.
System Action:
Action:
017E
INVALID EXPRESSION
Reason:
The C-language expression is syntactically incorrect.
System Action:
Action:
001 - 099
018E
VARIABLE xxxx NOT DEFINED
Reason:
The variable must first appear in a declarative statement or on the left-hand side of an
assignment statement.
System Action:
Action:
Add a variable declaration or assignment statement and try again.
019E
INVALID SUBFIELD FOR xxxx
Reason:
The parenthesized part of the data type is incompatible with that data type.
System Action:
Action:
Correct the variable declaration and try again.
020E
LABEL xxxx NOT FOUND
Reason:
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 signaled.
Action:
Insert a label at the appropriate location, or correct the label specification.
001 - 099
021E
'ELSE' STATEMENT FOUND OUT OF CONTEXT
Reason:
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.
Action:
Check the nesting levels of the 'IF-THEN-ELSE' logic.
022E
NO THEN STATEMENT FOUND
Reason:
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.
Action:
You need to specify a THEN clause on the same logical input line as the IF statement.
023E
INVALID LOGICAL EXPRESSION
Reason:
An IF statement encountered an invalid logical expression.
System Action:
The statement is not executed. The input stack is flushed.
Action:
A logical expression must consist of an expression that returns an integer result, or must
contain a relational operator.
001 - 099
024E
INVALID VARIABLE NAME
Reason:
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:
Action:
Specify a correct variable name.
025E
ENDDO HAS NO MATCHING DO STATEMENT
Reason:
An 'ENDDO' statement was found without a matching 'DO' statement. 'DO' and 'ENDDO'
statements must come in matching pairs. They can be nested to any depth.
System Action:
An error condition is raised.
Action:
Check the source for nested 'DO' and 'ENDDO' statements. You will find it easier to
locate errors if you indent nested DO..ENDDO statements.
026E
MISSING 'ENDDO' STATEMENT
Reason:
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.
Action:
Check the source to match 'DO' and 'ENDDO' statements. You may find it easier to
locate errors if you indent nested DO...ENDDO statements.
001 - 099
027E
xxxx
Reason:
An error has occurred which prevents the proc from being executed.
System Action:
The requested function is terminated.
Action:
Refer to the previous message for further information regarding this error.
028E
INVALID DATE PARAMETER ON FUNCTION CALL
Reason:
A single character-string parameter is required.
System Action:
Action:
029E
Reason:
Invalid parameter on call of DAYS_TO function.
System Action:
Action:
Correct the parameter and try again.
001 - 099
030E
INVALID READVAL SOURCE STRING
Reason:
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.
Action:
Correct the input string.
031E
INVALID READVAL KEYWORD SPECIFIED
Reason:
The READVAL statement had an unrecognized keyword specified.
System Action:
The statement is not processed.
Action:
Correct or remove the invalid keyword.
032E
INVALID READVAL POSITIONAL COUNT
Reason:
The POS keyword of the READVAL statement had an invalid operand. Valid operands are
numeric strings or integer or Boolean variables.
System Action:
Action:
Correct the specification, using a valid type.
001 - 099
033E
INVALID READVAL TARGET VARIABLE
Reason:
A target variable name passed to the READVAL statement did not conform to the
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.
Action:
Correct the target variable name.
034E
INVALID PARAMETERS PASSED TO PROMPT FUNCTION
Reason:
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.
Action:
Correct the function parameters.
001 - 099
035E
INVALID OR INCOMPLETE ASSIGNMENT STATEMENT OR EXPRESSION
Reason:
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:
Action:
Correct the statement. Either complete the assignment statement, or place a blank after
the command name.
036E
Reason:
Invalid parameter on call of DAYS_BETWEEN function.
System Action:
Action:
037E
INVALID PARAMETER PASSED TO ACTIVE FUNCTION
Reason:
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.
Action:
001 - 099
038E
INVALID PARAMETER PASSED TO SQRT FUNCTION
Reason:
A single double-precision parameter is required.
System Action:
Action:
039E
INVALID PARAMETER PASSED TO TAPES FUNCTION
Reason:
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.
System Action:
Action:
040E
Unable to open the input or output data set
Reason:
The GENFLOW command could not open the input and/or output data sets.
System Action:
Action:
Reenter the command with the correct parameters. Enter the GENFLOW command,
ensuring data set names and attributes are correct.
001 - 099
041E
Reason:
Invalid parameter on call of DAYS_TO function.
System Action:
Action:
042E
Reason:
Invalid parameter on call of DAYS_BETWEEN function.
System Action:
Action:
043E
INVALID JOBNAME
Reason:
The job name is too long in the LOCASCB function.
System Action:
Action:
Correct the job name and try again.
001 - 099
044E
INVALID PARAMETERS PASSED TO JOBONQ FUNCTION
Reason:
Job name missing or too long, or there were too many parameters to the JOBONQ or
JOBONCSF function.
System Action:
Action:
Correct the parameters and try again.
045E
SUBSYSTEM REQUEST ERROR CODE nn ENCOUNTERED BY JOBONQ FUNCTION
Reason:
Subsystem or JES error in JOBONQ or JOBONCSF function.
System Action:
Action:
Ensure that the subsystem is functioning properly.
046E
IRXINIT ERROR CODE nn, REASON CODE nn
Reason:
The IRXINIT initialization module has failed.
System Action:
The REXX interface is not available through the product.
Action:
Ensure that the IRXINIT module is available in the link list or a STEPLIB library.
001 - 099
047E
IRXTERM ERROR CODE nn
Reason:
The IRXTERM initialization module has failed.
System Action:
Processing continues.
Action:
Ensure that the IRXTERM module is available in the link list or a STEPLIB library.
048I
INVALID SELECTION LIST SPECIFIED
Reason:
The selection list in the SELECT parameter is not valid.
System Action:
the command is ignored.
Action:
Correct the SELECT parameter and try again.
049E
INVALID SYMBOL ON LEFT HAND SIDE OF ASSIGNMENT
Reason:
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 the product itself.
System Action:
Assignment is ignored.
Action:
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.
001 - 099
050E
Expression contains divide by zero
Reason:
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.
Action:
Determine why the divisor variable value was zero. Correct the problem and trigger the
Event again.
051E
Command is not valid with SAF
Reason:
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 environment.
System Action:
The request is denied.
Action:
Do not request non-SAF commands in a SAF environment.
052E
Invalid Request Block passed to xxxx
Reason:
An invalid request block was passed from a module to the workload object
object-oriented interface layer service module.
System Action:
The request is rejected.
Action:
This is caused by an internal logic error. Notify CA Support.
001 - 099
053E
InfoServ is not installed
Reason:
During initialization, it was determined the InfoServ product was not installed.
System Action:
Action:
If InfoServ is supposed to be installed, contact your system support.
054E
Invalid Agent Message format
Reason:
A workload object message was passed to the API. The message did not have the correct
header format.
System Action:
The message is ignored.
Action:
If this message comes from a MGRMSG command or AGENTMSG command, 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.
055E
Agent definition not found for xxxx
Reason:
An AGENTMSG command specified an incorrect agent name.
System Action:
The request is ignored.
Action:
correct the agent name.
001 - 099
056E
Agent definition not found for xxxx
Reason:
An AGENTMSG command was issued. However, no agents have been defined.
System Action:
Action:
The agent definition file needs to be loaded. (LOADAGDF command or initialization
statement)
057E
Agent name xxxx is too long
Reason:
The agent name specified in an AGENTMSG command exceeded 16 characters. The
maximum length allowed for the name is 16 characters.
System Action:
Action:
Correct the agent name and reissue the command.
058E
Invalid request code passed to xxxx
Reason:
An invalid request code was passed from a module to the workload object
object-oriented interface layer service module.
System Action:
Action:
001 - 099
059S
EVENT SCAN CANNOT BE DONE, CHECKPOINT FILE IS CLOSED
Reason:
This message follows a response of 'Y' to message 110.
System Action:
The product proceeds with the time change, but the event scan is not done.
Action:
Manually issue EVENTSET <eventdsid> SET BUILDSCHED command for every active
event data set.
060W
No response received from subsystem
Reason:
An operator command was issued to the subsystem. The subsystem did not respond to
the command.
System Action:
Action:
Contact your system support personnel.
061E
Command ignored, should be less than 116 characters
Reason:
An operator command was issued which the subsystem tried to execute. The command
was 116 or more characters in length.
System Action:
Action:
Reduce the length of the command string.
001 - 099
062I
Command accepted by subsystem
Reason:
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.
Action:
None.
063W
Data set is not sequential or a member of a PDS
Reason:
The SCAN command specified a partitioned data set. A sequential data set or member of
a PDS is required.
System Action:
The SCAN command is terminated.
Action:
Enter the SCAN command specifying a sequential data set or member of a PDS.
064E
Subsystem request error code nn nn encountered by RETSCBD function
Reason:
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.
Action:
001 - 099
065E
Invalid parameters passed to RETSCBD function
Reason:
Invalid parameters were passed to the RETSCBD function.
System Action:
Action:
Correct the parameters and re-issue the function.
066E
Subsystem request error code nn encountered by RETSCBD function
Reason:
A subsystem error occurred in the RETSCBD function. 'nn' is the subsystem return code.
System Action:
Action:
067E
Subsystem request error code nn nn encountered by JOBONCSF function
Reason:
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.
Action:
001 - 099
068E
Invalid parameters passed to JOBONCSF function
Reason:
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:
Action:
Correct the parameters and re-issue the function.
069E
Subsystem request error code nn encountered by JOBONCSF function
Reason:
A subsystem error occurred in the JOBONCSF function. 'nn' is the subsystem return
code.
System Action:
Action:
070I
xxxx
Reason:
An error occurred allocating the output data set for the CYBESUTS utility. The message
text describes the error.
System Action:
The utility is terminated.
Action:
Correct the error and execute the utility again.
001 - 099
071I
Scoreboard report generated
Reason:
The CYBESUTS utility has successfully dumped the scoreboard to the data set specified.
System Action:
None.
Action:
None.
072I
No scoreboard active
Reason:
The CYBESUTS utility attempted to dump the scoreboard. No scoreboard was found for
the specified subsystem.
System Action:
The CYBESUTS utility is terminated.
Action:
Ensure the specified subsystem is active and re-execute the utility.
073W
ApplID specified for job xxxx which is not external, ignored
Reason:
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.
Action:
Remove the APPLID keyword. One Event can only define a single application.
001 - 099
074E
INVALID MEMBER NAME xxxx
Reason:
A job refers to an invalid member name on a POSTREQ, PREREQ, COREQ or RELEASE
statement.
System Action:
The entire ESPPROC is aborted.
Action:
Correct the statement in error and trigger the Event.
075E
Possible loop in predecessor/successor relationships
Reason:
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.
Action:
Correct the job linkages.
076E
ILLEGAL INPUT FILE
Reason:
The data set specified in the MODEL command was not a Scheduled Activity data set.
System Action:
The command processing is terminated.
Action:
Re-specify the command with a data set that is a Scheduled Activity data set.
001 - 099
077E
Insufficient space in Appl record to insert job xxxx into Appl yyyy
Reason:
The application tracking record for application yyyy is full.
System Action:
The named job (xxxx) will not be tracked.
Action:
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 CA Support for further information.
078E
Insufficient space in Appl record to update job xxxx in Appl yyyy
Reason:
The application tracking record for application yyyy is full.
System Action:
The tracking information for the named job (xxxx) will not be up to date.
Action:
079W
Job xxxx already exists in Appl yyyy
Reason:
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:
Action:
Ensure the job name was correctly specified. If you need another copy of the same job,
use a unique qualifier.
001 - 099
080W
Job xxxx already exists in Appl yyyy
Reason:
System Action:
Action:
081E
Unable to locate job xxxx for update in Appl yyyy
Reason:
The 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:
Action:
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.
001 - 099
082E
Unable to locate job xxxx for update in Appl yyyy
Reason:
System Action:
Action:
083W
Requested generation of Appl xxxx not found
Reason:
A user requested action on a job within an Application. The requested Application did
not exist.
System Action:
The command is aborted.
Action:
Use the LISTAPPL command to confirm the existence of the specified Application.
084S
Unable to initialize subsystem
Reason:
An error occurred while trying to build the subsystem interface. This is probably an
internal logic error.
System Action:
Processing terminates.
Action:
Notify your software support personnel.
001 - 099
085S
Unable to getmain storage for the vector table
Reason:
The product was unable to obtain common area storage for the subsystem vector table.
System Action:
Action:
This problem is due to a shortage of common storage. The subsystem may be restarted
after the shortage is relieved.
086S
Insufficient CSA to load module xxxx
Reason:
A shortage of common storage area (CSA) prevented the loading of a subsystem
module.
System Action:
If the subsystem cannot continue without the specified load module, it terminates. If
the subsystem can continue without the specified load module, process continues.
However, some functionality may be lost.
Action:
When the CSA storage problem has been resolved, restart the subsystem. If the
subsystem was started with the RELOAD option and the CSA storage problem has not
been resolved, then restarting the subsystem without the RELOAD option may work.
However, some subsystem CSA module versions may be back-dated.
001 - 099
087S
Unable to load module xxxx
Reason:
An error occurred while trying to load a subsystem module into common storage (CSA).
System Action:
If the subsystem cannot continue without the specified load module, it terminates. If
the subsystem can continue without the specified load module, process continues.
However, some functionality may be lost.
Action:
Attempt to determine the cause of the module load failure. Usually it means the module
is not in the subsystem load library. Then restart the subsystem. If unable to determine
the cause of the CSA module load failure, contact CA Support.
088E
Error scanning command, RC=nn
Reason:
A problem was encountered while parsing the command line.
System Action:
The command is ignored. The user is prompted for a new command.
Action:
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.
001 - 099
089E
xxxx is not a partitioned data set
Reason:
A non-partitioned data set was specified as input to the OBJCHECK command.
System Action:
The command is terminated.
Action:
Specify a partitioned data set as input to the OBJCHECK command.
090E
xxxx is not a fixed length 80 byte record data set
Reason:
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:
Action:
Specify a data set with proper DCB attributes as input to the OBJCHECK command.
091W
Node xxxx not found
Reason:
In a CPU statement, the value of the NODE parameter specified an undefined node
name.
System Action:
The CPU is not defined.
Action:
Add a definition for the node.
001 - 099
092E
Reason:
An invalid request block was passed from a module to the workload object
object-oriented interface layer.
System Action:
Action:
093E
Invalid request code passed to xxxx
Reason:
An invalid request code was passed from a module to the workload object
object-oriented interface layer.
System Action:
Action:
094E
Invalid Parameters passed to xxxx
Reason:
Invalid parameters were passed from a module to the workload object object-oriented
interface layer.
System Action:
Action:
001 - 099
095E
Inconsistent parameters passed to xxxx (nn)
Reason:
This is an internal product error.
System Action:
The function is terminated.
Action:
Report this to CA and include the xxxx and nn codes.
096E
Module directory passed to xxxx is invalid
Reason:
An internal error has occurred.
System Action:
Processing for the current workload object is terminated.
Action:
The JES job log and ESP audit log should be preserved and this should be reported to CA
Support.
097E
Unable to load workload object package xxxx
Reason:
The named load module (xxxx) could not be loaded into memory.
System Action:
Action:
Insure that the named module is specified in the WOBDEF initialization parameter. Also
verify that this module is present in the STEPLIB or JOBLIB libraries and that no I/O error
has been encountered on these libraries.
001 - 099
098E
Module xxxx does not contain a valid workload object package
Reason:
An internal error has been detected while processing the named module (xxxx).
System Action:
Action:
The user should verify that a valid copy of the named module exists in the JOBLIB or
STEPLIB concatenations.
0099C
WOB Definition Modules
Reason:
This is the header for a list of WOB modules as specified by the WOBDEF initialization
parameter or operator command.
System Action:
The system proceeds to list the modules along with additional information for each
module.
Action:
None required.
100 - 199
100 - 199
100W
SYSTEM TIME HAS BEEN CHANGED
Reason:
The product detected the system time change has occurred, and the difference between
new time and old time is greater than the value specified by initialization parameter
TIMECHK.
System Action:
This message is followed by message 110.
Action:
See description of message 110.
101W
INVALID COMMAND, xxxx
Reason:
An undefined command name was entered as a command.
System Action:
The command is ignored. The TSO user is prompted for a new command.
Action:
A TSO user should reenter the command with the correct name. A batch user should
correct the command for the next execution.
100 - 199
102I
OK
Reason:
A conversational command with no specific response has completed. This is a
confirmation that the command has completed successfully.
System Action:
None.
Action:
N/A
103E
ERROR SCANNING COMMAND, RC=nn
Reason:
System Action:
Action:
System routine IKJPARS returned error code nn. When
nn=12 - Invalid parameters passed to parse from CP.
nn=24 - An error in input parameters was detected in the IKJPA-RS2 load module.
respectively.
100 - 199
104E
COMMAND xxxx NOT FOUND
Reason:
This is not a valid TSO command.
System Action:
Command ignored.
Action:
Correct the command and try again.
105S
ERROR OBTAINING A COMMAND, RC=nn
Reason:
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.
Action:
Notify your support personnel.
106S
COMMAND PROCESSING TERMINATED
Reason:
A previous error caused the command processor to terminate.
System Action:
Command processing is terminated.
Action:
100 - 199
107E
COMMAND SUPPRESSED BY INSTALLATION EXIT
Reason:
A user specified command was rejected by the installation command authorization exit.
System Action:
Action:
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.
108W
nn Out of extent slots encountered in data set xxxx, File recovered
Reason:
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.
Action:
None required.
109W
The number of successors is limited to 50 in JES3 dependent job control network.
Reason:
Up to 50 successors for a job can be specified in JES3 dependent job control network.
System Action:
Simulation continues.
Action:
Limit the number of successors.
100 - 199
110A
CONFIRM THE TIME CHANGE AND REPLY 'Y' TO CONTINUE, 'N' TO TERMINATE ESP, OR
'R' TO RETRY
Reason:
This message follows messages 100. See above.
System Action:
The product awaits a response. If the response is 'Y', the product proceeds with the time
change. A response of 'N' causes the product to terminate. If the response is 'R', the
product will repeat this message and wait for a response
Action:
If the time change is correct, reply 'Y'. If the time change is incorrect, and you do not
want the product to continue, reply 'N'. If the time change is incorrect, but you want the
product to continue, you may change the system time accordingly, and then reply 'R'. It
will allow the product to pick up a new time change.
111W
INVALID ITERATION FACTOR
Reason:
The TEST command was entered with an invalid iteration factor. A valid iteration factor
consists of an all numeric field.
System Action:
Action:
Reenter the command with a valid iteration factor.
100 - 199
112C
JSS TEST
Reason:
The TEST command results are being displayed.
System Action:
None.
Action:
None.
113C
SDB DISPLAY
Reason:
A request was made to list the storage used by the CA WA ESP Edition product. This is
the first line of a multiple line display detailing the storage usage by the CA WA ESP
Edition product.
System Action:
Action:
None.
114I
Agent Receiver for xxxx is now terminated
Reason:
An Agent communications receiver has been shutdown down at the request of an
operator or user.
System Action:
The Receiver terminates.
Action:
None.
100 - 199
115E
GDTTITEE is xxxx
Reason:
A timer is being set for an agent receiver and a global timer task was already active in
the system. This message is for diagnostic purposes only.
System Action:
Processing continues without interruption.
Action:
No user response is required. However, the JES job log and ESP audit log should be
preserved and the message should be reported to CA Support.
116W
Unexpected Data Received return code nn encountered by Agent Receiver xxxx
Reason:
The system was in APPC communication with an agent and was attempting to receive a
message. A return code was encountered that did not indicate the status of the data
received.
System Action:
Communication with the agent has been terminated.
Action:
Verify that there were no communication errors on the system at the time. If this
problem persists, insert the following DD statement into the JCL for the ESP started task:
//COMTRACE DD SYSOUT=X,DCB=LRECL=6000
Restart ESP. When the message is encountered, gather the JES job log, the ESP audit log
and the COMTRACE output and report the problem to CA Support.
100 - 199
117W
Unexpected Status Received nn encountered by Agent Receiver xxxx
Reason:
The system was in APPC communication with an agent and a status code was received
that was not expected.
System Action:
Communication with the agent has been terminated.
Action:
Verify that there were no communication errors on the system at the time. If this
problem persists, insert the following DD statement into the JCL for the ESP started task:
//COMTRACE DD SYSOUT=X,DCB=LRECL=6000
Restart ESP. When the message is encountered, gather the JES job log, the ESP audit log
and the COMTRACE output and report the problem to CA Support.
118S
ESP TERMINATING DUE TO INCORRECT CLOCK SETTING
Reason:
This message follows a response of 'N' to message 110.
System Action:
The product terminates.
Action:
The product should be restarted after the clocks are reset.
100 - 199
119E
User security token extract failed
Reason:
The product 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.
Action:
Notify your system support personnel.
120E
xxxx SUBSYSTEM ERROR CODE nn
Reason:
A request was made to the subsystem, but an error occurred. The return code from the
subsystem was "nn".
System Action:
Action:
Notify your software support personnel, indicating the request you made and the
resultant return code "nn".
121E
xxxx SUBSYSTEM NOT FOUND
Reason:
The subsystem named "xxxx" has not been started since the most recent IPL.
System Action:
None. Certain command functions require the subsystem to be up and running. These
commands will fail.
Action:
Wait for the subsystem to initialize.
100 - 199
122E
xxxx SUBSYSTEM NOT ACTIVE
Reason:
The subsystem, named "xxxx" was not active at the time the command was issued.
System Action:
None. Certain command functions require the subsystem to be up and running. These
commands will fail.
Action:
Wait for the subsystem to be restarted.
123E
xxxx REQUEST ALREADY PENDING FOR THIS ADDRESS SPACE
Reason:
The 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.
Action:
Do not issue concurrent requests from multiple subtasks.
124E
INSUFFICIENT STORAGE AVAILABLE FOR xxxx SUBSYSTEM REQUEST
Reason:
A main storage shortage prevented normal subsystem request execution to proceed.
System Action:
Action:
This is usually a temporary problem. Retry the command.
100 - 199
125E
LOGIC ERROR, BAD PARAMETERS PASSED TO xxxx SUBSYSTEM
Reason:
An internal logic error has occurred in subsystem "xxxx".
System Action:
Action:
Notify your software support personnel, indicating the request you made.
126E
SUBSYSTEM REQUEST ESTAE FAILURE
Reason:
The subsystem request processor was unable to establish a recovery environment. This
is normally due to a storage problem.
System Action:
Action:
Retry the command. If the problem persists, notify your system support personnel.
127E
SUBSYSTEM FAILURE
Reason:
The subsystem had a failure while your request was pending.
System Action:
Action:
Wait for the subsystem to be restarted, then retry your command.
100 - 199
128E
ERROR OCCURRED IN SUBSYSTEM REQUEST PROCESSOR
Reason:
The subsystem request processor intercepted an abend.
System Action:
The request is terminated. A dump is produced.
Action:
Report the problem to your system support personnel.
129E
USERID OR PASSWORD NOT SPECIFIED
Reason:
A request was made to the product from a batch job. The product 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 the product was unable to verify the
ID of the user making the request.
System Action:
Action:
Identify the request by using the USER/PASSWORD keywords on the job card, or by
using the USER command in the input stream.
130W
UNABLE TO LOCATE xxxx VECTOR TABLE
Reason:
The 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.
Action:
Wait for the subsystem to be started.
100 - 199
131C
Pre-V5.4 TRAKFILE
****************************************************
* Please run CYBESUT4 utility to upgrade TRAKFILE
*
* Sample JCL on ASEPSAME(CYBESS36) or ASEPSAME(CYBESS37) *
* Then restart the product with upgraded TRAKFILE
*
****************************************************
Reason:
The product has been upgraded to V5.4 or higher without a corresponding upgrade to
the TRAKFILE. The TRAKFILE upgrade is required in order for the product 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 subsystem terminates.
Action:
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 subsystem.
132W
YOU ATTEMPTED TO SET AN ATTRIBUTE TO WHICH YOU ARE NOT AUTHORIZED
Reason:
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.
Action:
Ensure you have the valid authority for the request.
100 - 199
133E
SUBSYSTEM REQUEST ERROR CODE nn-nn
Reason:
The subsystem request processor handling a request could not complete a request. The
resultant return code from the request was "nn-nn".
System Action:
The request is not completed.
Action:
Notify your software support personnel, indicating the request you made and the
resultant return codes "nn-nn".
134E
User ID / Password not verified. [User ID = *]
Reason:
The USER command was entered with an invalid password for 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:
Action:
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.
CA WA ESP Edition API product users: Review the access privileges of the
programs that are using the CA WA ESP Edition API product.
100 - 199
135E
YOU ARE NOT DEFINED TO xxxx
Reason:
Your userid has not been defined to the subsystem.
System Action:
Your userid will not be permitted to define or delete Events.
Action:
Request the administrator to define your userid to the system.
136E
SUBSYSTEM xxxx IS NOT AN ESP SUBSYSTEM
Reason:
An attempt was made to locate a subsystem with the name indicated by 'xxxx'. Although
a subsystem was located with that name, it did not belong to a subsystem.
System Action:
Processing continues as if the product is inactive. Certain commands that require the
subsystem to be active will not execute.
Action:
If you wish to use commands that require the subsystem, wait until the subsystem is
initialized.
100 - 199
137E
SUBSYSTEM xxxx IS NOT A COMPATIBLE ESP SUBSYSTEM
Reason:
An attempt was made to locate a 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 the product is inactive. Certain commands that require the
subsystem to be active will not execute.
Action:
This may occur when a new release of the product is installed and either the subsystem
or the TSO command processor are not upgraded simultaneously. Notify your software
support personnel.
138E
REQUEST REJECTED BY INSTALLATION USER VERIFICATION EXIT
Reason:
A request was made to the product from a batch job. The installation user verification
processor denied access to the request.
System Action:
Action:
Notify your installation support personnel.
100 - 199
139E
ABEND OCCURRED IN INSTALLATION USER VERIFICATION EXIT
Reason:
A request was made to the product from a batch job. The installation user verification
processor was invoked, but an abend occurred while it was processing.
System Action:
The request is not processed.
Action:
Notify your installation support personnel.
140E
xxxx IS NOT AUTHORIZED {IN THE UPDT|BY SAF}
Reason:
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:
Action:
Notify your installation security administrator.
141I
ENDDEF STATEMENT GENERATED
Reason:
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.
Action:
None.
100 - 199
142E
NO EVENT IDENTIFIER SPECIFIED
Reason:
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.
Action:
Respecify the EVENT statement.
143E
ERROR PROCESSING EVENT xxxx.yyyy, SUBSYSTEM ERROR CODE nn
Reason:
An error occurred processing an EVENT.
System Action:
The processing request is not completed.
Action:
144E
EVENT DATASET FOR GROUP xxxx SUSPENDED
Reason:
An attempt was made to define or display an EVENT while the database containing the
EVENT definitions for that group was unavailable to the product.
System Action:
The request is not performed.
Action:
100 - 199
145E
EVENT xxxx.yyyy NOT DEFINED
Reason:
You attempted to display or modify an EVENT that has not been defined to the product.
System Action:
The request is not performed.
Action:
Ensure that you enter the correct EVENT name.
146E
xxxx IS NOT AUTHORIZED IN THE UPDT OR BY SAF
Reason:
System Action:
Action:
147E
EVENT xxxx.yyyy ALREADY DEFINED
Reason:
An EVENT was defined with the 'ADD' option while a similarly named EVENT was
previously defined.
System Action:
If the EVENT was defined interactively, that is directly from a terminal while in prompt
mode, this message is followed by message 186A. In other cases, the define request is
ignored.
Action:
Respond to message 186A.
100 - 199
148E
I/O ERROR PROCESSING EVENT xxxx.yyyy
Reason:
An I/O error occurred while processing an EVENT on behalf of a user.
System Action:
Action:
149E
EVENT xxxx.yyyy IS HELD OR SUSPENDED
Reason:
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, the product will store a
pending TDR in the event definition.
Action:
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.
150E
EVENT DEFINITION SIZE EXCEEDED
Reason:
The EVENT definition contained too many statements.
System Action:
The EVENT definition is terminated.
Action:
Redefine your EVENT to contain less definition statements. If necessary, break it down
into multiple EVENTs.
100 - 199
151E
EVENT DEFINITION IGNORED DUE TO PREVIOUS ERRORS
Reason:
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.
Action:
Correct and reenter the EVENT definition.
152E
NO ACTION ELEMENTS DEFINED, EVENT DEFINITION IGNORED
Reason:
An EVENT definition was entered which contained only schedule type elements. No
action statements were included.
System Action:
The EVENT definition is ignored.
Action:
Redefine the EVENT with valid action statements.
153W
WARNING, NO SCHEDULE ELEMENTS DEFINED, DIRECT TRIGGER REQUIRED
Reason:
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.
Action:
None needed, unless the schedule elements were accidentally omitted.
100 - 199
154I
EVENT xxxx WILL EXECUTE AT yyyy ON zzzz
Reason:
An EVENT has just been defined. This message indicates the first scheduled execution of
the EVENT.
System Action:
None.
Action:
None.
155E
xxxx
Reason:
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.
Action:
The response depends on the error encountered.
156W
DATA SET xxxx IS NOT PARTITIONED, LEVEL KEYWORD IGNORED
Reason:
A SUBMIT command in an EVENT definition specified the 'LEVEL' keyword for a
non-partitioned data set.
System Action:
The 'LEVEL' keyword is ignored.
Action:
Ensure that the correct data set name was specified.
100 - 199
157E
INVALID DAY OF WEEK xxxx
Reason:
An ON statement contained an invalid day of the week.
System Action:
The ON statement is ignored.
Action:
Correct the statement.
158E
INVALID ON UNIT ACTION TYPE xxxx
Reason:
An ON statement in an Event definition specified an invalid action. The valid actions are
IGNORE, ADVANCE and DELAY.
System Action:
Action:
159E
INVALID ON UNIT COUNT nn
Reason:
An ON statement in an EVENT definition contained an invalid ADVANCE/DELAY count.
The maximum count allowed is 31.
System Action:
Action:
100 - 199
160E
ERROR PROCESSING USER/GROUP ENTRY, SUBSYSTEM ERROR CODE nn
Reason:
A subsystem error was encountered when defining or altering a GROUP or USER entry.
System Action:
Action:
Notify your support personnel, indicating the message number and return code.
161E
ENTRY NOT FOUND
Reason:
A GROUP or USER entry specified on an alter or display command was not found.
System Action:
Action:
Ensure the GROUP or USER entry is correctly entered.
162E
Not authorized for requested function
Reason:
You attempted to perform a DEFINE, DELETE or ALTER request on a GROUP or USER
entry to which you are not authorized.
System Action:
Action:
Ensure that you have the correct authority for the functions you need to perform.
100 - 199
163E
ENTRY ALREADY DEFINED
Reason:
An attempt was made to define an already existing USER or GROUP.
System Action:
Action:
Ensure that the command was entered correctly.
164E
I/O ERROR ON USER DEFINITION DATASET
Reason:
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.
Action:
165E
INVALID PASSWORD SPECIFIED
Reason:
An invalid current password was specified when changing the password or accessing the
product through a batch job.
System Action:
The access to the product is denied.
Action:
Ensure a correct current password is specified.
100 - 199
166I
PASSWORD SUCCESSFULLY ALTERED
Reason:
The password for a USER was successfully altered by use of the PASSWORD command.
System Action:
None.
Action:
None.
167I
Mgr Message Received
Reason:
Messages from an agent have been received and are being traced.
System Action:
The incoming message is dumped to the log.
Action:
None required.
168I
xxxx
Reason:
Messages from an agent have been received and are being traced. This line contains the
actual content of the message.
System Action:
Action:
None required.
100 - 199
169W
SPECIAL DAY xxxx NOT DEFINED IN CALENDAR(S) yyyy zzzz
Reason:
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.
Action:
Ensure that the name is entered correctly.
170I
NO SPECIAL DAYS DEFINED
Reason:
A LISTSPEC command was entered, to display the special days. No special days had been
defined.
System Action:
None.
Action:
None.
100 - 199
171E
INVALID EVENT ID, xxxx
Reason:
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.
Action:
Enter a valid EVENT name.
172E
EVENT ID PREFIX MISSING, xxxx
Reason:
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.
Action:
Enter a fully qualified EVENT name.
100 - 199
174E
INVALID END TIME AND DATE SPECIFIED
Reason:
When defining a holiday, an end time and date was specified that was earlier than the
start time and date.
System Action:
Action:
Respecify the command.
175E
You do not have authority to set the requested {USER|OWNER} field
Reason:
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.
Action:
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.
176W
Resfile commands not available from a proxy ESP/WM
Reason:
A resource management related command was issued from a proxy subsystem.
System Action:
Action:
Issue this command from a master subsystem.
100 - 199
177W
Resource facility is not initialized
Reason:
A resource manager related command was issued to a system where the resource
manager was not initialized.
System Action:
Action:
The resource manager needs to be initialized. In the master system initialization
parameter data set, specify the RESFILE parameter. The product will need to be
restarted.
178E
INVALID LOGICAL EXPRESSION
Reason:
An IF statement encountered an invalid logical expression.
System Action:
The statement is not executed. The input stack is flushed.
Action:
A logical expression must consist of an expression that returns an integer result, or must
contain a relational operator.
179W
Data set xxxx is partitioned and no members were specified
Reason:
A INVOKE statement specified a partitioned data set. The INVOKE statement must
specify a PDS member name.
System Action:
The statement is ignored.
Action:
Specify a member name.
100 - 199
180W
STATEMENT INVALID, xxxx ON yyyy HAS ALREADY PASSED
Reason:
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.
Action:
Respecify the time and date.
181E
MEMBER NAME AND LEVEL OPTION MUTUALLY EXCLUSIVE
Reason:
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.
Action:
Respecify the SUBMIT statement. If you wish to use a specific member as well as the
LEVEL option, define two SUBMIT statements.
182W
NO ENTRIES FOUND LEVEL xxxx
Reason:
A LIST command was unable to find any EVENTs with the requested high level string.
System Action:
None.
Action:
Respecify the command with the correct high level string.
100 - 199
183W
NO ACTION STATEMENTS SPECIFIED YET
Reason:
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.
Action:
Specify one or more action statements.
184I
CONTINUE EVENT DEFINITION WITH AN ACTION STATEMENT OR ENTER 'CANCEL'
Reason:
An EVENT was defined with no actions. This message is issued after message 183W.
System Action:
The previous ENDDEF statement is ignored.
Action:
If you wish to terminate the EVENT definition, enter 'CANCEL'. Otherwise you should
enter one or more action statements.
185W
EVENT xxxx.yyyy ALREADY EXISTS
Reason:
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.
Action:
100 - 199
186A
ENTER NEW NAME, 'REPLACE' OR 'CANCEL'
Reason:
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.
Action:
You may cancel the current definition by entering CANCEL, you may replace the
previous version by entering REPLACE or you may specify a new name.
187W
USER SUBCOMMAND ONLY VALID IN BATCH
Reason:
A USER subcommand was entered from a TSO terminal session. It can only be issued in a
batch environment.
System Action:
Action:
You can only use your own userid in a TSO session. The USER command is therefore
unnecessary.
188E
MISSING PASSWORD
Reason:
A USER subcommand was specified, but a password omitted.
System Action:
The command is ignored. The product will not allow access to the requested userid.
Action:
Specify the correct password.
100 - 199
189W
DATA SET xxxx IS PARTITIONED AND NO MEMBERS WERE SPECIFIED
Reason:
A SUBMIT statement specified a partitioned data set. Neither a LEVEL option or member
name were specified.
System Action:
Action:
Specify a member name or use the LEVEL option.
191E
ABEND code OCCURRED ON data set name
Reason:
The operating system detected an error while processing the named data set.
System Action:
Processing for the command is terminated.
Action:
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.
192W
DATA SET TRIGGER OPTION NOT CURRENTLY ENABLED
Reason:
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.
Action:
Request your system programmer to specify data set triggering.
100 - 199
193E
GENERIC DATA SET ENTRY MUST BE AT LEAST 8 BYTES LONG
Reason:
A DSTRIG statement referred to a data set name by high level generic string. The
minimum generic string length is 8 characters.
System Action:
Action:
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.
195E
INCOMPATIBLE DATA SET TYPE SPECIFIED FOR xxxx
Reason:
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:
Action:
Specify the appropriate command for the data set type.
100 - 199
196E
ACCESS TO ESP SUBSYSTEM DENIED BY SECURITY SYSTEM
Reason:
Your userid is not defined as having access to the online system. You need to be
permitted to the online resource with at least the READ access attribute.
System Action:
The online session with the product is denied.
Action:
If you require access to the product, request permission from your security
administrator. If you think you already have access to the product, check that you
attempted to access the product with the correct userid.
197E
xxxx COMMAND NOT SUPPORTED WITH SAF BASED SECURITY
Reason:
A command was issued which was not supported when resources are controlled by SAF
based security.
System Action:
The command is suppressed.
Action:
The command you requested is not supported with SAF. The function you requested is
probably available through a host security based facility.
198E
Invalid template parameters
Reason:
The template definition contained illegal parameters.
System Action:
The definition is ignored.
Action:
Correct the template definition.
200 - 299
199I
EVENT DEFINED, WILL REQUIRE DATA SET TRIGGER
Reason:
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.
Action:
None needed.
200 - 299
200W
UNABLE TO QUEUE DIRECTLY TO SYSTEM xxxx
Reason:
An Event was defined or triggered to execute on another system. The QUEUE data set
was unavailable so the local 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.
Action:
Ensure the correct system id was specified. If not, redefine the Event with the correct
system id, or use the ALTEVENT command.
200 - 299
201W
SYSTEM xxxx NOT MEMBER OF SHARED QUEUE
Reason:
An Event was defined or triggered to execute on another system. The designated system
was not sharing the QUEUE data set. The local system was unable to queue it to the
requested system.
System Action:
Action:
202W
Job xxxx(yyyy) overdue in P-Node zzzz
Reason:
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.
Action:
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.
200 - 299
203E
NOT AUTHORIZED FOR HISTORY FILE ACCESS
Reason:
A user requested history file data. However, the user entry specified no history file
access string.
System Action:
The history file access is denied.
Action:
If you need access to the history file, request authorization from your administrator.
204W
NO SYSTEMS FOUND MATCHING xxxx
Reason:
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.
Action:
If you made an error in specification, alter or redefine the Event.
205E
NOT AUTHORIZED TO MODIFY CALENDAR xxxx
Reason:
You attempted to modify a calendar to which you are not authorized.
System Action:
Action:
Ensure that you specified the correct calendar. If you require access to this calendar,
request authorization from your administrator.
200 - 299
206E
INSUFFICIENT SPACE LEFT IN CALENDAR xxxx
Reason:
During the process of defining a HOLIDAY or SPECIAL DAY the product could not allocate
enough space in the CALENDAR.
System Action:
Action:
Space may be obtained in the CALENDAR by deleting old, unused entries (HOLIDAYs and
SPECIAL DAYS). If this is not possible the CALENDAR should be split.
207E
HOLIDAY xxxx NOT FOUND
Reason:
A HOLIDAY specified by a user, during CALENDAR processing was not found.
System Action:
Action:
Ensure the holiday name is specified correctly.
208E
SPECIAL DAY ENTRY FOR xxxx NOT FOUND
Reason:
A SPECIAL DAY specified by a user, during CALENDAR processing was not found.
System Action:
Action:
Ensure the special day is specified correctly.
200 - 299
209W
EVENT FILE SUSPENDED
Reason:
A request was made to access an event file which is currently in suspended status.
System Action:
Action:
Contact your administrator to have the event file reopened or issue the EVENTSET
operator command with the OPEN option if you are authorized.
210E
LIBRARY ACCESS DENIED TO USER
Reason:
An Event containing a non-supported command was being defined by a non-valid userid.
System Action:
Action:
You must redefine the Event from a valid userid.
211E
INVALID RECORD TYPE DETECTED ON USER DEFINITION DATASET
Reason:
A record in the USERDEF data set contains an invalid type indicator.
System Action:
The user entry retrieval request will fail.
Action:
200 - 299
212E
NOT AUTHORIZED TO DELETE/ALTER CALENDAR xxxx
Reason:
You attempted to delete or alter a calendar to which you are not authorized.
System Action:
Action:
213W
NOT AUTHORIZED FOR CALENDAR DEFINE
Reason:
You attempted to define a calendar to which you are not authorized.
System Action:
Action:
214E
CALENDAR xxxx ALREADY DEFINED
Reason:
An attempt was made to define an already existing CALENDAR.
System Action:
Action:
Depends on the cause of the problem. Ensure that the command was entered correctly.
200 - 299
215E
CALENDAR xxxx NOT DEFINED
Reason:
The CALENDAR requested by a user was not found.
System Action:
The CALENDAR is not processed.
Action:
Ensure the calendar name is specified correctly.
216E
USER/GROUP xxxx NOT FOUND
Reason:
A GROUP or USER entry specified during CALENDAR processing was not found.
System Action:
Action:
Ensure the GROUP or USER entry is correctly entered.
217E
Command xxxx invalid in Agent Definition Table
Reason:
A User Profile Definition Table contained an invalid command.
System Action:
The User Profile Definition Table is not loaded.
Action:
Correct the table and reissue the LOADUPDT command.
200 - 299
218E
xxxx
Reason:
A LOADUPDT command encountered an error allocating or opening a User Profile
Definition Table. The preceding message will have described the error.
System Action:
Action:
Ensure the table name was specified correctly and reissue the LOADUPDT command.
219E
Above error occurred opening Agent Definition Table
Reason:
System Action:
Action:
220E
DATA SET xxxx IS NOT PARTITIONED
Reason:
The COPYJCL parameter specified a non-partitioned data set for the JCL to be copied to.
System Action:
The COPYJCL statement is not accepted.
Action:
Specify the name of an OS partitioned data set.
200 - 299
221E
COPYJCL DATA SET MUST BE AN OS PARTITIONED DATA SET
Reason:
The COPYJCL parameter specified a Librarian or Panvalet data set as an output data set.
Only OS partitioned data sets are supported.
System Action:
The COPYJCL statement is not accepted.
Action:
Specify the name of an OS partitioned data set.
222I
DEFAULT USERID ASSIGNED
Reason:
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.
Action:
None.
223E
Above error occurred reading Agent Definition Table
Reason:
An error occurred while reading in a User Profile Definition Table. The error is described
in a preceding message.
System Action:
Action:
After the error is corrected, reissue the LOADUPDT command.
200 - 299
224E
Invalid command syntax detected in line nn of Agent Definition Table
Reason:
A User Profile Definition Table contained a statement with invalid syntax.
System Action:
Action:
Correct the table definition and reissue the LOADUPDT command.
225E
Above error occurred on line nn of the Agent Definition data set
Reason:
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.
Action:
Correct the error and reissue the LOADAGDF command.
226W
No Distributed Managers defined
Reason:
A DMANAGER LIST command was entered to list the current Distributed Manager
topology. There are no known Distributed Managers.
System Action:
Action:
None.
200 - 299
227C
DM Display
Reason:
The current Distributed Manager topology is displayed in response to a DMANAGER LIST
command.
System Action:
Action:
None.
228I
Workload Object Module Directory not created
Reason:
The WOBDEF DISPLAY command was entered to display active workload object
modules. There are no workload object modules currently active.
System Action:
Action:
None.
229E
AGENTRCV xxxx parameter invalid for TCP/IP receiver yyyy
Reason:
A parameter valid only for APPC agent receivers was specified in an "AGENTRCV"
command for a TCP/IP receiver.
System Action:
Action:
None.
200 - 299
230W
SIGNAL xxxx HAS EVENTS PENDING, CANNOT DELETE
Reason:
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.
Action:
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.
231W
SIGNAL xxxx NOT DEFINED
Reason:
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.
Action:
Check the spelling of the signal name.
232W
SIGNAL xxxx ALREADY DEFINED
Reason:
A signal define command was issued, specifying a name that was already in use.
System Action:
The signal is not defined.
Action:
Use a unique name. If you wish to redefine the signal, delete it first.
200 - 299
233W
YOU DO NOT HAVE SUFFICIENT ACCESS TO SIGNAL xxxx
Reason:
You are not authorized to perform the requested action against the named signal(s).
System Action:
The request is not executed.
Action:
None.
234W
GENERATION NUMBER nn NOT PRESENT FOR SIGNAL xxxx
Reason:
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.
Action:
Specify the correct generation number. Use the LISTSIG command to display the current
signal generation count.
235W
SIGNAL xxxx GENERATION nn ALREADY POSTED
Reason:
A SIGPOST command was issued against a signal that was already posted.
System Action:
The SIGPOST is ignored.
Action:
Ensure correct generation number was specified.
200 - 299
236E
INSUFFICIENT CHECKPOINT SPACE TO QUEUE REQUEST
Reason:
A SIGPOST or SIGCYCLE request could not proceed as there was insufficient space in the
checkpoint to queue the request.
System Action:
Action:
Retry a little later.
237W
SIGNAL PROCESSOR SUSPENDED DUE TO PRIOR REQUEST
Reason:
A SIGSTAT SUSPEND command had been issued.
System Action:
The signal processor ignores all signal posts and signal waits until signal processing is
resumed.
Action:
When signal processing is required, issue the SIGNAL RESUME command.
238W
SIGNAL PROCESSOR QUIESCED DUE TO PRIOR REQUEST
Reason:
A SIGSTAT QUIESCE command had been issued.
System Action:
Signal processing is quiesced, meaning any requests are deferred until signal processing
is restarted.
Action:
When you wish to restart signal processing, issue the SIGSTAT RESTART operator
command.
200 - 299
239E
ABOVE ERROR OCCURRED PROCESSING xxxx REQUEST OR SIGNAL yyyy
Reason:
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.
Action:
Depends on the nature of the I/O error.
240E
INVALID SIGNAL REQUEST, CODE xxxx, ENCOUNTERED FOR SIGNAL yyyy
Reason:
A signal request was passed to the signal manager. The request code is displayed in hex.
System Action:
The signal request is ignored.
Action:
This is probably due to an internal logic error. Notify your software support personnel.
241E
INVALID SIGNAL NAME xxxx
Reason:
An invalid signal name was specified for a SIGWAIT request.
System Action:
The SIGWAIT is not processed.
Action:
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.
200 - 299
242E
GENERIC SPECIFICATION NOT ALLOWED IN GROUP NAME FOR SIGCYCLE
Reason:
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.
Action:
Respecify the SIGCYCLE with an explicit group name. To cycle several groups of signals,
use a SIGCYCLE for each group.
243E
SIGNAL xxxx NOT FOUND
Reason:
A SIGPOST or SIGCYCLE was issued by an Event. However, the signal was not found.
System Action:
The SIGPOST or SIGCYCLE request is ignored.
Action:
The signal should be defined, or the Event changed to identify the correct signal.
200 - 299
244E
Reason:
An invalid signal name was specified for a signal define, delete alter, display or cycle
command.
System Action:
The command is not processed.
Action:
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.
245E
GENERIC SPECIFICATION NOT PERMITTED IN GROUP NAME
Reason:
A LISTSIG command was entered and a signal name specified with a '-' or '*' in the group
name. This is not permitted.
System Action:
Action:
Reissue the command with an explicit group name. To display several groups, issue the
command once for each group.
200 - 299
246E
Reason:
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.
Action:
Correct the spelling of the signal name. The Event will need to be re-triggered manually.
247W
NO MATCHING EVENTS FOUND
Reason:
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.
Action:
None.
248E
INSUFFICIENT SPACE TO ENTER PENDING ELEMENT FOR EVENT
Reason:
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.
Action:
The Event should be manually triggered with the FORCE option.
200 - 299
249E
INSUFFICIENT SPACE TO ENTER SIGWAIT ELEMENT FOR EVENT
Reason:
An Event requested a SIGWAIT. However, there was insufficient space in the Event
definition block to store the cross relation information.
System Action:
Action:
The Event should be manually triggered with the FORCE option.
250W
SIGNAL xxxx GEN nn NOT FOUND FOR EVENT yyyy, ASSUMED POSTED
Reason:
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.
Action:
You may wish to redefine the signal or redefine the Event.
251E
INSUFFICIENT SPACE TO ENTER SIGWAIT ELEMENT FOR EVENT xxxx
Reason:
Insufficient space was available in an Event definition block to queue a SIGWAIT request.
System Action:
Action:
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.
200 - 299
252E
ABOVE ERROR OCCURRED READING SIGNAL xxxx FOR EVENT yyyy
Reason:
An I/O error, documented by the preceding message, occurred while accessing a signal
definition block for an Event.
System Action:
Action:
The Event has to be triggered manually.
253E
FORCE OPTION INVALID, EVENT xxxx HAS NO PENDING EXECUTIONS
Reason:
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.
Action:
The FORCE option should only be used to force the execution of an Event that has
signals pending.
254E
EVENT xxxx IS NOT PENDING AT SPECIFIED TIME
Reason:
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.
Action:
Respecify the trigger with the correct time. To force the oldest or only pending
execution, you can omit the time specification.
200 - 299
256E
xxxx
Reason:
A severe error occurred while allocating the COPYJCL library.
System Action:
See the return code.
Action:
CATALOG return codes can be found in the IBM Message manual under the heading
'IDC3009'.
257E
SIGPNNM STATEMENT MUST BE PRECEDED BY SIGPEND
Reason:
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.
Action:
This is probably due to an accidental delete of the SIGPEND during an edit of an Event.
The SIGPEND statement should be restored.
200 - 299
258E
INSUFFICIENT CHECKPOINT SPACE TO QUEUE CYCLE/POST REQUEST FOR EVENT xxxx,
SIGNAL yyyy
Reason:
An Event performed a SIGPOST/SIGCYCLE request. However, insufficient checkpoint
space remained for the request to be queued.
System Action:
Action:
The SIGPOST/SIGCYCLE will have to be done manually.
259E
UNDEFINED HISTORY FILE
Reason:
A history file was specified as input to a report. However, the specified history file has
not been defined to the product.
System Action:
The report is not produced.
Action:
Specify the name of a valid history file. See your administrator for information about
history files. If you wish access to all history files, simply omit the HISTFILE statement.
260C
Agent Display
Reason:
This is the header line for the display that follows.
System Action:
The agent information is displayed following the header.
Action:
None
200 - 299
261W
No Agents defined
Reason:
ESP has not found any agents that are defined.
System Action:
None
Action:
Create an agent file if an agent is required.
262C
Agent Receiver display
Reason:
This is the header line for the display that follows.
System Action:
The agent information is displayed following the header.
Action:
None
263I
OK
Reason:
The previous input for the AGENTRCV DEFINE command was accepted.
System Action:
The input is processed.
Action:
None
200 - 299
264I
OK
Reason:
The previous input for the AGENTRCV SET command was accepted.
System Action:
The input is processed.
Action:
None
265I
Agent Receiver xxxx halted
Reason:
The named agent receiver was halted as requested.
System Action:
The receive is halted.
Action:
None
266I
Agent receiver xxxx shutdown requested
Reason:
An "AGENTRCV DELETE" command was issued for agent receiver "xxxx".
System Action:
Agent receiver "xxxx" is shutdown and deleted.
Action:
None.
200 - 299
267I
Agent Receiver xxxx restarted
Reason:
An Agent Receiver has been restarted after a Halt request.
System Action:
Action:
None required.
268E
Missing agent receiver name
Reason:
An "AGENTRCV" command that did not specify the "NAME" parameter was issued.
System Action:
Action:
To list all agent receivers, enter one of the following commands:
AGENTRCV
AGENTRCV LIST
AGENTRCV DISPLAY
Then reissue the original "AGENTRCV" command specifying a valid agent receiver.
200 - 299
269E
Agent xxxx already defined
Reason:
An "AGENTRCV NAME(xxxx) DEFINE" command was issued for an agent receiver "xxxx"
that already exists.
System Action:
Action:
None.
270E
Agent receiver xxxx not defined
Reason:
An "AGENTRCV NAME(xxxx)" or "AGENTRCV AGENTRECEIVER(xxxx)" command specified
an agent receiver "xxxx" that does not exist.
System Action:
Action:
To list all agent receivers, enter one of the following commands:
AGENTRCV
AGENTRCV LIST
AGENTRCV DISPLAY
Then reissue the original "AGENTRCV" command specifying a valid agent receiver.
200 - 299
271E
PORT, SYMDEST or LU/TPNAME/LOGMODE missing for Agent Receiver xxxx
Reason:
An "AGENTRCV" command was issued with a required TCP/IP or APPC parameter(s)
missing.
System Action:
Action:
Issue the "AGENTRCV" command with the required TCP/IP (PORT) or APPC (LU and
TPNAME or SYMDEST) parameter(s) specified.
272W
Requested generation of Appl <application_name> not found
Reason:
The generation specified in APPLJOB command could not be found.
System Action:
APPLJOB command rejected.
Action:
Re-issue AJ command with valid generation number.
273E
INVALID OPERATION CODE SPECIFIED TO XI005
Reason:
System Action:
The operation code is ignored.
Action:
Please contact your software support personnel for further assistance.
200 - 299
274E
ERROR OPENING DATA SET xxxx, OPEN ERROR CODE nn
Reason:
An error during OPEN prevented the access to a VSAM data set.
System Action:
A message will follow describing the action taken.
Action:
Look up the error code in the VSAM Programmer's Guide.
275E
PUT UPDATE PERFORMED OUT OF CONTEXT
Reason:
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.
Action:
276E
VSAM xxxx ERROR CODE nn ON DATA SET yyyy
Reason:
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.
Action:
Look up the error code in the VSAM Programmer's Guide.
200 - 299
277E
INSUFFICIENT SPACE TO ADD DATA TO DATA SET xxxx (gggggg)
Reason:
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.
Action:
The data set may need to be reorganized, or loaded into a larger data set.
278E
RECORD KEY 'xxxx' NOT FOUND IN DATA SET yyyy (gggggg)
Reason:
This error occurred while processing a request on a VSAM data set. 'gggggg' is function
being performed.
System Action:
Action:
Check any following messages to get more information.
279E
RECORD KEY X'xxxx' NOT FOUND IN DATA SET yyyy (gggggg)
Reason:
This error occurred while processing a request on a VSAM data set. 'gggggg' is function
being performed.
System Action:
Action:
Check any following messages to get more information.
200 - 299
280E
I/O ERROR ON xxxx(gggggg),yyyyzzzzaaaabbbbccccddddeeeeffff
Reason:
A physical error occurred while processing a request on a VSAM data set.
xxxx is the data set name.
gggggg is the function being performed.
yyyy is COMPONENT NAME.
zzzz is VOLUME SERIAL.
aaaa is UNIT.
bbbb is DEVICE TYPE.
cccc is COMMAND CODE.
dddd is MESSAGE.
eeee is MBBCCHHR.
ffff is the access method.
System Action:
Depends on the data set. A message will follow indicating the action taken.
Action:
Take action based on the succeeding messages.
281I
Delay interval set to nn minute(s)
Reason:
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.
System Action:
None.
Action:
None.
200 - 299
282E
Not authorized to set security ID xxxx
Reason:
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.
Action:
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.
283E
Not authorized to Event owner xxxx
Reason:
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.
Action:
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.
200 - 299
284E
Generic DSNAME invalid when member specified
Reason:
The product 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.
Action:
Specify a discreet data set name or remove the PDS member name from the DSNAME
application statement.
285E
Generic DSNAME invalid when member specified
Reason:
The product encountered a DSTRIG event command that specifies a generic data set
name and a PDS member name.
System Action:
The event is suppressed.
Action:
Specify a discreet data set name or remove the PDS member name from the DSTRIG
event command.
200 - 299
286E
DSNAME member invalid for implicit data set trigger
Reason:
The product 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:
Action:
Remove the PDS member name from the data set name specification of the DSTRIG
event command.
287E
ESP <product> not enabled, unexpected <ddb> error
Reason:
Optional feature <product> is installed but its Diagnostic Data Block module <ddb> was
not found or contains unexpected version or licensing information.
System Action:
The optional feature is not enabled.
Action:
This problem should never occur. If it does, please contact CA Support.
288I
xxx Checkpointed and yyy uncheckpointed messages flushed
Reason:
The indicated number of messages were flushed from one or more agent queues as the
result of an AGENT FLUSH command.
System Action:
None.
Action:
None.
200 - 299
289E
Agent MPL level must range from 1 to 50
Reason:
The valid range of values that can be specified on the AGENTMPL command is from 1 to
50.
System Action:
Action:
Specify a valid number on the AGENTMPL command.
290E
ALESERV ADD failed, RC=X'nnnn'
Reason:
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:
Action:
Re-issue the CSF request. If the problem persists, contact CA Support.
291E
Filter interpreter load failed, RC=X'nnnn'
Reason:
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:
Action:
Correct the problem indicated by the return code 'nnnn'. The return codes are identical
to those return codes for a system abend 806.
200 - 299
292E
The scoreboard is not active
Reason:
The user has requested a CSF function. The scoreboard is not currently active.
System Action:
Action:
Ensure the subsystem specified is active and that the scoreboard facility is available.
293E
Scoreboard request not valid from a proxy subsystem
Reason:
The user has requested a CSF function from a proxy subsystem.
System Action:
Action:
Re-issue the request from a master system. Scoreboard API requests can only be made
from the master system in a master/proxy complex.
294E
ALESERV DELETE failed, RC=X'nnnn'
Reason:
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:
Action:
200 - 299
295E
Error retrieving scoreboard data, CMPC=X'sssuuu'
Reason:
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).
Action:
296E
Error retrieving device list for xxxx, RC=X'yyyy', SC=X'zzzz'
Reason:
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.
Action:
Contact your system programmer and provide the return code and reason code.
200 - 299
297E
Error retrieving UCB X'xxxx', RC=X'yyyy', SC=X'zzzz'
Reason:
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.
Action:
Contact your system programmer and provide the return code and reason code.
298I
Agent MPL is set to nn, current usage is nn
Reason:
The agent maximum MultiProcessing Level is currently set to nn. The highest number
used so far is nn.
System Action:
None.
Action:
None.
299W
Agent xxx could not be quiesced, no checkpoint space
Reason:
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.
Action:
Investigate why no space is available on the checkpoint.
300 - 399
300 - 399
300I
nn Agents quiesced|restarted
Reason:
nn Agents were quiesced or restarted as the result of an AGENT xxx QUIESCE|RESTART
command.
System Action:
None.
Action:
None.
301E
Invalid string/value xxxx
Reason:
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.
Action:
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.
300 - 399
302E
Variable name xxxx not found
Reason:
A filter statement contained a variable name that did not correspond to a valid field
name.
System Action:
Action:
Correct the string. The field name may be misspelled, or you may have omitted to put a
literal value in quotes.
303E
Invalid subfield value xxxx
Reason:
A filter statement contained a term consisting of a variable followed by a substring
specifier. The substring specifier was invalid.
System Action:
Action:
Correct the substring field.
304E
Too many subfields in specified, xxxxyyyy
Reason:
A variable in a filter statement has a substring specifier that has more than 2 subfields.
System Action:
Action:
Correct the subfield. You have probably forgotten a closing parenthesis.
300 - 399
305E
Invalid expression syntax in filter statement
Reason:
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.
Action:
Correct the filter expression.
307S
INSUFFICIENT SPACE TO REBUILD THE QUEUE DATASET
Reason:
The QUEUE data set was being rebuilt, probably due to the install of a new release of
the product. Insufficient space exists in the queue data set t perform the rebuild
function. This may be due to the new control blocks being larger than before.
System Action:
The product follows this message with a 0097 user abend.
Action:
Notify your software support personnel. The product can be restarted with the QFORM
parameter. This will destroy the 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 the product could be restarted.
300 - 399
308W
QUEUE DATASET xxxx IS CORRECTLY FORMATTED
Reason:
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. The product is confirming that a
format start is really required, and not inadvertently specified.
System Action:
The product follows by issuing message 309A.
Action:
309A
CONFIRM REQUEST FOR QUEUE DATASET FORMAT, REPLY 'Y' OR 'N'
Reason:
The product is requesting confirmation that a format of the queue is really required.
System Action:
The product waits for the reply. If a Y is entered, the product proceeds with to format
the queue data set. If the reply is N, the product proceeds with a war start.
Action:
If you wish to proceed with the format start, enter Y. Otherwise enter N and the product
will attempt a warm start.
310I
WARM QUEUE START WILL BE ATTEMPTED
Reason:
The product is attempting a warm queue data set start after the operator entered a
reply of N to the message 309A.
System Action:
None.
Action:
The product will attempt a warm queue data set start.
300 - 399
312W
INVALID QUEUE DATASET FORMAT ON xxxx
Reason:
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.
Action:
If you wish to proceed with the format start, enter Y. Otherwise enter N and the product
will terminate.
313A
ENTER 'Y' TO PROCEED WITH QUEUE FORMAT OR REPLY 'N'
Reason:
This message requests confirmation that you wish to proceed with the formatting of the
queue data set.
System Action:
The product waits for your response. If you answer Y, the format is performed.
Otherwise, a warm start is attempted.
Action:
Enter Y if you wish to proceed with the format.
314E
xxxx
Reason:
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.
Action:
Respond to the message that follows.
300 - 399
315W
INVALID RESPONSE
Reason:
An invalid response was given to message 0309A.
System Action:
The prompt is reissued.
Action:
Respond to the reprompt.
317S
QUEUE DATASET UNUSABLE
Reason:
This message follows another message describing an error on the queue data set.
System Action:
Action:
The previous message described an error condition. After the problem is corrected, the
product can be restarted.
320S
QUEUE DATASET NOT DEFINED
Reason:
A queue data set was not specified on a startup.
System Action:
Action:
Define a queue data set by use of the QUEUE parameter in the ESPPARM file.
300 - 399
321E
DSNAME member invalid for implicit data set trigger
Reason:
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.
Action:
Remove the PDS member name from the data set name specification of the DSNAME
application statement.
323W
QUEUE DATASET IS DOWNLEVEL, FORMAT REQUIRED
Reason:
A WARM start was attempted when bringing up a new release of the product. The new
release uses a queue of slightly different format, and therefore a format start is
required.
System Action:
Action:
Respond to message 313.
300 - 399
324E
MANAGER already defined
Reason:
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.
Action:
Remove the extra MANAGER statement and re-enter the LOADAGDF command.
325E
No xxxx type MANAGER defined{, DM=yyyy|, Agent=zzzz}
Reason:
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'.
System Action:
Action:
Add the appropriate communication type to the MANAGER statement and re-enter the
LOADAGDF command.
300 - 399
326E
Duplicate node name encountered: nnnn
Reason:
During the processing of a LOADAGDF command, a duplicate node name was
encountered. 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.
Action:
Correct the duplicate name and re-enter the LOADAGDF command.
327E
Comm type APPC or TCPIP must be specified, {DM=xxxx|AGENT=yyyy}
Reason:
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.
System Action:
Action:
Add the communication type to the appropriate statement and re-enter the LOADAGDF
command.
300 - 399
328E
xxxx must be specified for yyyy{, DM=zzzz|, Agent=aaaa}
Reason:
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.
System Action:
Action:
Correct the definition and re-enter the LOADAGDF command.
329E
xxxx cannot be specified with yyyy{, DM=zzzz|, Agent=aaaa}
Reason:
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.
System Action:
Action:
Correct the definition and re-enter the LOADAGDF command.
330W
TRACK MODEL xxxx NOT FOUND FOR JOB yyyy(nn)
Reason:
A job tracking model specified for a job was not located.
System Action:
No tracking or history recording will be performed for that job.
Action:
The job model may have been accidentally deleted. The job model should be redefined.
300 - 399
331E
JOB INDEX ERROR CAUSING POSSIBLE LOSS OF TRACKING DATA FOR JOB xxxx(nn)
Reason:
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.
Action:
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.
332E
TRAKFILE error causing possible loss of tracking data for job xxxx(yyyy)
Reason:
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.
Action:
Notify your software support personnel. If the errors persist, quiesce the tracking option
with the TRACKING NOSTORE command until the error on the tracking file is corrected.
300 - 399
333E
P-NODE xxxx NOT FOUND FOR JOB yyyy
Reason:
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.
Action:
Notify your software support personnel. The p-node may have been deleted by
accident, or the job model definition may be out of date.
334E
ERROR OCCURRED READING P-NODE ENTRY FOR JOB xxxx
Reason:
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.
Action:
335E
INSUFFICIENT CHECKPOINT SPACE TO POST JOB xxxx
Reason:
A job was to be posted to a P-node but insufficient checkpoint space was available to
queue the request.
System Action:
Action:
300 - 399
336E
INSUFFICIENT QUEUE SPACE TO QUEUE JOB xxxx TO P-NODE yyyy
Reason:
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:
Action:
337E
ERROR OCCURRED READING/WRITING STEP RECORD FOR JOB xxxx
Reason:
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.
Action:
338E
ERROR OCCURRED READING/WRITING END RECORD FOR JOB xxxx
Reason:
A job tracking record was being updated at job termination time when an I/O error
System Action:
The tracking information for the job will not be updated.
Action:
300 - 399
339E
ERROR OCCURRED FREEING TRACKFILE SLOTS FOR JOB xxxx
Reason:
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.
Action:
340E
ERROR OCCURRED UPDATING P-NODE DATA FOR JOB xxxx
Reason:
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:
Action:
341E
JOB xxxx NOT DESTINED FOR P-NODE yyyy
Reason:
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.
Action:
Notify your software support personnel. This would in most cases indicate a logic error.
300 - 399
342W
Job xxxx(yyyy) not being tracked
Reason:
A post command was issued specifying a job number that did not belong to a job being
tracked by the product. xxxx specifies the job name. yyyy specifies the job identifier.
System Action:
The post request is not processed.
Action:
Specify the correct job number.
343W
P-NODE xxxx NOT FOUND
Reason:
A DFPNODE command was issued specifying a P-node that was not found on the queue
data set.
System Action:
Action:
Specify the correct P-node name.
300 - 399
344W
Job xxxx(yyyy) not queued to P-Node zzzz
Reason:
A POST command was issued against a job for a p-node to which it was not currently
queued.
zzzz - specifies the P-Node.
System Action:
The POST request is not processed.
Action:
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.
345W
Job xxxx(yyyy) not destined for P-Node zzzz
Reason:
A POST command was issued against a job for a P-node which was not in the job's model
definition.
zzzz - specifies the P-node.
System Action:
Action:
Specify the correct P-node name.
300 - 399
346W
nn JOBS QUEUED TO xxxx, USE JOB NUMBER
Reason:
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:
Action:
Respecify the command using a job number rather than job name.
347W
INSUFFICIENT CHECKPOINT SPACE TO QUEUE POST REQUEST
Reason:
A post command was issued for a job, but the checkpoint data set was full and the
request could not be queued.
System Action:
Action:
Reissue the command a little later.
348E
ESP subsystem has different version than CYBES079
Reason:
The version of the sub-system is not the same as the version of CYBES079, which resides
at the CSA. The common reason for this error is that the sub-system was not started
with parameter RELOAD after system upgrade.
System Action:
The CSF cannot be entered.
Action:
Start the sub-system with PARM=RELOAD.
300 - 399
349E
USER xxxx NOT AUTHORIZED FOR JOB POST FUNCTION
Reason:
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:
Action:
Consult your installation administrator.
350E
INVALID REQUEST CODE DETECTED
Reason:
The job tracking request processor was passed an invalid request code. This would
normally only happen due to a logic error.
System Action:
Action:
351W
NO SPACE LEFT IN PREFIX BLOCK
Reason:
A DEFTJ command was issued to define a tracked job prefix entry, but no space was left
in the prefix block.
System Action:
Action:
Notify your software support personnel. Some unused job prefixes could be deleted, or
the maximum record length on the job index should be increased.
300 - 399
352E
PORT operand missing for agent receiver <name>
Reason:
Response to AGENTRCV DEFINE NAME(<name>) command. The PORT(<port>) operand
was not specified.
System Action:
The AGENTRCV DEFINE NAME(<name>) command is ignored.
Action:
Re-enter the AGENTRCV DEFINE NAME(<name>) command specifying PORT(<port>),
where <port> specifies a TCP port number for the agent receiver to listen on.
353W
TRACKING FACILITY NOT ACTIVE
Reason:
A user or operator entered a command that was part of the tracking facility. The
tracking facility was not active.
System Action:
Action:
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.
300 - 399
354E
AGENTRCV SET specification(s) missing
Reason:
An "AGENTRCV SET" command was issued without specifying what to set.
System Action:
Action:
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.
355E
INVALID P-NODE BLOCK GENERATED
Reason:
A DEFPN command built a p-node block which did not pass the request processor
validity check.
System Action:
Action:
Notify your software support personnel. This is likely a logic error.
356W
NOT AUTHORIZED TO P-NODE xxxx
Reason:
A DFPNODE or POST command specified a P-NODE to whom the user or console was not
authorized.
System Action:
Action:
The console or user should be added to the authorized list for the p-node through the
DEFPN command.
300 - 399
357W
NO SPACE IN USERDEF ENTRY FOR DEFAULT PNODE
Reason:
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:
Action:
The logical record length on the USERDEF data set should be increased.
358W
xxxx NOT DEFINED TO ESP
Reason:
The console or TSO user issuing a request to the product was not defined in the user
definition data set.
System Action:
Action:
Request that your userid or console be defined by your installation administrator.
359W
JOB NOT ON TRACK FILE
Reason:
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:
Action:
None.
300 - 399
360W
JOB xxxx ANCESTOR nn NOT ON INDEX FILE
Reason:
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 the product.
System Action:
Action:
None.
361W
JOB xxxx NOT BEING TRACKED
Reason:
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 the product.
System Action:
Action:
If you wish the job to be tracked, enter a tracking definition for the job.
300 - 399
362E
HISTFILE xxxx NOT FOUND OR IS CLOSED FOR JOB yyyy(nn)
Reason:
At the completion of a job, the product attempted to write a history file record.
However, the history file with the I.D. xxxx 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.
Action:
Check that the history file identified in the message is defined to the product. 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.
363E
Above error occurred writing HISTFILE record for job xxxx(nnn)
Reason:
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.
Action:
Investigate the cause of the error, and take appropriate action.
300 - 399
364E
UNABLE TO RECEIVE INTER SYSTEM TRACKING DATA, READ ERROR nn
Reason:
An error occurred when trying to receive inter system tracking data through NJE. The
return code from the sysout interface was nn.
System Action:
The NJE receiver shuts down.
Action:
Probable system error.
365E
Wrong Job in JTR: Expected xxxx(nn), found yyyy(mm)
Reason:
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 condition is treated as an I/O error. Processing of the XME is discontinued
Action:
None.
366E
Reason:
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.
Action:
This is an internal processing logic error. Please contact CA Support.
300 - 399
367E
Inconsistent parameters passed to xxxx (nn)
Reason:
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:
Action:
368E
Invalid request code passed to xxxx, RQ=nn
Reason:
During internal processing, an invalid request code was passed to DM formatting
services. "nn" is the invalid code.
System Action:
Action:
369E
xxxx parameter invalid for AGENTRCV yyyy
Reason:
An "AGENTRCV" command was issued with an invalid parameter.
System Action:
Action:
Issue the "AGENTRCV" without the invalid parameter.
300 - 399
370E
INSUFFICIENT QUEUE SPACE FOR SYSTEM ID RECORD
Reason:
During initialization, a system identification record was to be placed in the QUEUE data
set. However, the queue data set had insufficient space.
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.
Action:
Restart the product after a short interval.
371E
INSUFFICIENT CHECKPOINT SPACE TO QUEUE EVENT xxxx.yyyy
Reason:
Another 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.
Action:
372E
EVENT DATASET ID xxxx NOT FOUND FOR EVENT yyyy.zzzz
Reason:
Another 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.
Action:
Notify your software support personnel. The Event data set definitions for shared
systems must be identical.
300 - 399
373W
P-NODE xxxx NOT DELETED, QUEUE NOT EMPTY
Reason:
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.
Action:
Respecify the command once the jobs have been posted out of the p-node.
374W
YOU ARE NOT AUTHORIZED FOR THE REQUESTED FUNCTION
Reason:
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:
Action:
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.
300 - 399
375W
QUEUE DATASET NOT OPEN
Reason:
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.
Action:
The QUEUE data set must be defined in the initialization parameter file.
376E
INVALID P-NODE NAME xxxx
Reason:
A DEFTM command was issued which contained an invalid P-node name.
System Action:
The track model is not defined or replaced.
Action:
Reenter the command specifying a correct P-node name.
377E
INVALID P-NODE/DUE OUT TIME SYNTAX xxxx
Reason:
A DEFTM command was issued which contained an invalid P-node name or due out time
specification.
System Action:
Action:
Reenter the command specifying a correct P-node name and optional due out time.
300 - 399
378I
Agent receiver <name> listening on {port CA Portal}|{<ip>:CA Portal}
Reason:
Agent receiver <name> is waiting on IP address <ip> (if applicable), and TCP port
number CA Portal for incoming client connection requests.
System Action:
Action:
None.
379W
Suspending|Halting agent receiver <name> due to {TCP/IP error|retry limit|purge}
Reason:
An agent receiver TCP error occurred or an agent receiver listener socket was explicitly
purged by an INET PURGE ID command. <name> specifies the logical name of the agent
receiver.
System Action:
If a TCP error occurred and the agent receiver's retry limit has not been reached, the
agent receiver is suspended for 5 minutes and then restarted. If a TCP error occurred
and the agent receiver's retry limit has been reached or the agent receiver's TCP socket
was explicitly purged by an INET PURGE ID command, the agent receiver is halted.
Action:
If a TCP error occurred and remains unresolved, then attempt to determine the cause,
and correct it. If the agent receiver has been halted, then after the cause of the TCP
error has been resolved, restart the agent receiver with the command: AGENTRCV
RESTART NAME(<name>) where <name> specifies the name of the agent receiver. If
unable to determine the cause of the TCP error, contact CA Support.
300 - 399
380E
INVALID SYMBOL TABLE RECORD GENERATED
Reason:
In response to a DEFSYML command, an invalid control block was generated.
System Action:
The DEFSYML command is not processed.
Action:
This is most likely a logic error. Notify your software support personnel.
381W
SYMLIB xxxx ALREADY EXISTS
Reason:
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.
Action:
If you wish to replace the definition, use the REPLACE option.
382W
SYMLIB xxxx NOT FOUND
Reason:
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.
Action:
Re-enter the command specifying the correct name.
300 - 399
383E
SYMLIB xxxx DEFINITION TOO LARGE
Reason:
The specified SYMLIB definition contained too many elements, and would not fit in a
database record.
System Action:
The SYMLIB definition is not added.
Action:
The MAXLRECL initialization parameter should be increased to accommodate larger
records.
384E
SUBSYSTEM REQUEST ERROR CODE nn FOR JOB STATUS
Reason:
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.
Action:
If this problem persists, it could be due to a logic error in the program, or an error in the
job entry subsystem.
385I
WAITING FOR JOB ENTRY SUBSYSTEM RESTART
Reason:
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.
Action:
Ensure the job entry subsystem is restarted.
300 - 399
386I
QUEUE UPDATE PROCESSOR WAITING FOR CHECKPOINT SPACE
Reason:
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.
Action:
None
387I
JOB xxxx(yyyy) AUTOPOSTED FROM INPUT
Reason:
At initialization or as the result of a QUPDATE command, the product 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 product status In this case, the job is on the
product input queue but not on the JES input queue. This could happen at any time
where the product had not receive 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 the product 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 (such as time on queue etc.).
Action:
None.
300 - 399
388E
JOB INDEX DATASET REQUIRED FOR SCHEDULED ACTIVITY DATABASE UPDATE
Reason:
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.
Action:
Ensure a jobindex data set is available. Check the initialization parameter data set.
389E
AGENTRCV xxxx invalid at initialization time
Reason:
An AGENTRCV command was entered with an option that is invalid while the product is
initializing.
System Action:
The product issues a prompt to the operator console for either a new command,
"CANCEL" to terminate the product, or "END" to ignore the command and continue
processing.
Action:
Respond to the above console prompt. Remove erroneous "AGENTRCV xxxx" command
from ESPPARM data set.
390E
DATASET xxxx PARTITIONED BUT NO MEMBER SPECIFIED
Reason:
A member name must be specified with this partitioned data set.
System Action:
The requested function was not completed.
Action:
Add a member name and try again.
300 - 399
391E
GENERIC DATA SET ENTRY MUST BE AT LEAST 8 BYTES LONG
Reason:
The generic data set entry in the DSNAME statement is too short.
System Action:
The statement is rejected.
Action:
Be more specific in specifying generic data set names
392E
ERROR LINKING TO <cmd_name>
Reason:
A CALLRTN command was issued in line mode and the link was unsuccessful.
System Action:
Action:
Check the validity of all parameters in the CALLRTN command and correct them. If the
problem persists call CA Support.
393W
INVALID COMMAND <cmd_name>
Reason:
An invalid command was received from API.
System Action:
Action:
Correct the request that caused the error.
300 - 399
394W
INVALID COMMAND NAME SYNTAX
Reason:
The syntax of the command received from API is invalid.
System Action:
The command is rejected.
Action:
Correct the request that caused the message.
395S
Reason:
An API related problem was found while validating a command.
System Action:
The command is ignored. This message is followed by 0396S.
Action:
See message 0396S.
396S
Reason:
This message follows a 0395S message.
System Action:
The API server is terminating.
Action:
Check if all necessary tasks are up and running. If some are down, find out why and start
them.
300 - 399
397I
DATA SET <dsn> UNALLOCATED
Reason:
This is an information message to the user UNALLOC command.
System Action:
Action:
Not required.
398E
xxxxx
Reason:
Freeing asked by command UNALLOC failed.
System Action:
Action:
Check whether the data set name was correctly specified in the command.
399S
SCHEDULE FILE <DSN> UNUSABLE
Reason:
Schedule file could not be opened.
System Action:
Scoreboard display aborted.
Action:
Check the status of schedule file. It must be a KSDS VSAM data set.
400 - 499
400 - 499
400E
Error Sxxx linking to <program>
Reason:
The CALLRTN service could not link to program <program>. xxx is the link system error
completion code.
System Action:
Action:
Correct the <program> parameter to CALLRTN and try again.
401W
Reason:
An unrecognized command was entered from an operator's console.
System Action:
Action:
Reenter the correct command name.
402W
Reason:
A command was issued which did not conform to the syntax for command names.
System Action:
Action:
Reenter the correct command name.
400 - 499
403W
<program> return code <rc>
Reason:
Response to "OPER CALLRTN <program>" command. Program <program>, after being
invoked by the CALLRTN command, returned a non-zero completion code <rc>.
System Action:
Action:
None.
404E
Agent receiver xxxx must be halted to set port
Reason:
An "AGENTRCV SET PORT" command was issued for an active TCP/IP agent receiver.
System Action:
Action:
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)
405S
Reason:
The console command processor encountered an error in command processing.
System Action:
Action:
See message 406.
400 - 499
406S
Reason:
A severe error has caused the console communications processor to terminate.
System Action:
The product continues to operate without the operator communication facility.
Action:
Notify your software support personnel. Use the STOP command to shut the product
down, as the modify interface will not work.
407W
YOU ARE NOT AUTHORIZED FOR OPERATOR COMMANDS
Reason:
A user attempted to issue an operator command to which he or she was not authorized.
System Action:
Action:
Authorization for operator commands is the responsibility of the installation
administrator.
408W
YOU ARE NOT AUTHORIZED TO THE xxxx COMMAND
Reason:
Use of this command requires OPER authority.
System Action:
Action:
Ask the System Administrator to authorize you to use this command.
400 - 499
409E
REEXEC MAXIMUM VALUE HAS BEEN REACHED,
Reason:
A specified maximum of REEXECs has been reached.
System Action:
REEXEC request ignored.
Action:
None.
410E
QUEUE update not allowed from a proxy subsystem
Reason:
A cleanup of the QUEUE data set was attempted from a proxy subsystem.
System Action:
Request ignored.
Action:
Any update of the QUEUE data set can be done only from a master subsystem.
411W
Generation <gen> of [assign the value for appl in your book] NOT FOUND REQUESTED
GENERATION OF APPL [assign the value for appl in your book] NOT FOUND
Reason:
Requested generation <gen> of application [assign the value for appl in your book] not
found.
System Action:
Processing continues
Action:
Check for errors in appl.gen specification.
400 - 499
412W
REQUESTED GENERATION OF APPL [assign the value for appl in your book] NOT
FOUND
Reason:
Appl.gen specified in APPLJOB command not found.
System Action:
Action:
Specify a valid appl.gen.
413E
JOB <jobname> NOT FOUND IN APPL [assign the value for appl in your book]
Reason:
Job <jobname> does not exist in application [assign the value for appl in your book].
System Action:
The APPLJOB command is ignored.
Action:
Use a valid job name and application name in the APPLJOB command.
414E
JOB <jobname> IS NOT A MEMBER OF AN APPLICATION
Reason:
Job <jobname> is not a member (part) of the application.
System Action:
Action:
Use a valid job name in the APPLJOB command.
400 - 499
415W
Workload Object <name{.qual}> in appl <appl.gen> started at <ttt>
Reason:
The named workload object started at time <ttt>.
System Action:
Action:
None (if the workload object is supposed to start).
416W
Workload Object <name{.qual}> in appl <appl.gen> ended at <ttt>
Reason:
The named workload object ended at time <ttt>.
System Action:
Action:
None (if the workload object is supposed to end).
417W
Workload Object <name{.qual}> in appl <appl.gen> failed at <ttt>, Exitcode=cc
Reason:
This message is issued on the request of a NOTIFY statement in a Procedure. The named
workload object failed at time <ttt> with Completion Code=cc.
System Action:
Action:
None (if the workload object is supposed to fail).
400 - 499
418I
CONTROL TRANSACTION HANDLER TERMINATED
Reason:
Module that handles control transactions and delegates all other types to the
appropriate handling modules has terminated.
System Action:
TP Server cleanup completes,
Action:
None.
419I
TP SERVER CONTROL TRANSACTION ACTIVE
Reason:
This message is issued after the TP Server initialization has completed.
System Action:
System is ready to send and receive transactions.
Action:
None.
420W
EVENT DATASET CONTAINING xxxx.yyyy IS SUSPENDED
Reason:
A request was made to read an Event definition. However, the data set was currently
suspended.
System Action:
The Event retrieval fails.
Action:
If the Event data set is useable, issue the EVENTSET command to reopen it.
400 - 499
421E
AN INVALID TRANSACTION FUNCTION WAS RECEIVED
Reason:
TP Server received an invalid transaction code.
System Action:
Transaction ignored.
Action:
Check if all systems to be connected have valid parameters.
422I
CONTROL TRANSACTION TERMINATING
Reason:
TP Server is stopping due to previous error(s).
System Action:
TP Server will stop.
Action:
If problem persist contact your software support personnel.
423S
CONTROL TRANSACTION RECEIVE FAILED - xxx
Reason:
Invalid control transaction received. The beginning of the received data is presented in
hexadecimal format xxx.
System Action:
Action:
See message 0422.
400 - 499
424I
LU 6.2 TRANSMISSION SERVER SHUTDOWN COMPLETE
Reason:
TP Server has stopped successfully.
System Action:
None.
Action:
None.
425W
INVALID JOBNAME SPECIFICATION <jobsp>
Reason:
An invalid job specification appeared in command from Workstation.
System Action:
Action:
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
400 - 499
426E
INVALID JOBNAME SPECIFICATION <jobsp>
Reason:
An invalid job specification appeared in command from console.
System Action:
Action:
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
427E
No jobs were eligible out of the <nn> jobs in Subappl <subapplname>
Reason:
Out of <nn> jobs in subapplication <subapplname> no one was eligible for requested
action entered from console.
System Action:
Action:
Check subapplication for presence of jobs qualified for the action.
400 - 499
428W
INVALID APPLICATION SPECIFICATION [assign the value for appl in your book]
Reason:
An invalid application name appeared in command from Workstation.
System Action:
Action:
Correct the application name.
429E
INVALID APPLICATION SPECIFICATION [assign the value for appl in your book]
Reason:
An invalid application name appeared in command from console.
System Action:
Action:
Correct the application name.
430E
DATASET NAME NECESSARY FOR AN HISTFILE DEFINE
Reason:
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.
Action:
400 - 499
431E
HISTFILE xxxx NOT DEFINED
Reason:
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.
Action:
432E
HISTFILE xxxx ALREADY DEFINED
Reason:
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:
Action:
If this is for a new definition, ensure you use a unique identifier.
433?
HISTFILE xxxx OPEN, PERFORM CLOSE FIRST
Reason:
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:
Action:
Use the CLOSE option of the HISTFILE command to close the data set, then issue the
delete.
400 - 499
434E
ERROR SCANNING COMMAND, RC=nnn
Reason:
Error occurred while scanning command received from Workstation.
System Action:
Action:
Depending on RC=nn different actions could be considered. When
nn=12 - invalid command structure. Transmission error is likely, Check the init
parameters. Try again.
respectively.
435W
HISTFILE xxxx ALREADY OPEN
Reason:
A HISTFILE command was issued to open a history data set which was already open.
System Action:
Action:
Ensure that the correct data set identifier was specified.
400 - 499
436W
HISTFILE xxxx ALREADY CLOSED
Reason:
A HISTFILE command was issued to close a history data set which was already closed.
System Action:
Action:
437A
CONFIRM REQUEST TO DELETE HISTFILE xxxx, REPLY Y OR N
Reason:
A HISTFILE command was issued to delete a history data set.
System Action:
The product waits for a reply.
Action:
Reply Y if you wish to continue with the delete request, otherwise reply N to cancel the
request.
438I
DELETE REQUEST CANCELLED
Reason:
This message is issued if a reply of N was given to message 0437A.
System Action:
The delete request is not performed.
Action:
None.
400 - 499
439I
HISTFILE xxxx DELETED
Reason:
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.
Action:
None.
440E
<command> REJECTED: <reason>
Reason:
A command was rejected for the reason given.
System Action:
Action:
Examine the reason and respond accordingly. If necessary, contact CA Support.
441E
HISTFILE WITH DSN xxxx ALREADY DEFINED
Reason:
A HISTFILE command was issued to define a history data set. However, a data set is
already defined with the same dsname.
System Action:
Action:
Ensure that you specify the correct name. If you wish to alter a definition, use the SET
option of the HISTFILE command.
400 - 499
442I
TRACKING OPTIONS: {NO}COLLECT, {NO}STORE, {NO}LOG
Reason:
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 the product.
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 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:
Action:
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.
443W
JOB TRACKING FACILITY NOT INITIALIZED
Reason:
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:
Action:
Ensure that all the initialization parameters for the job tracking facility are specified
correctly.
400 - 499
444W
xxxxx
Reason:
API Server received invalid data.
System Action:
Line ignored.
Action:
None.
0445W
QOPRCMDS ignored, only permissible in batch client
Reason:
An ESP command was issued in an interactive TSO environment specifying the
QOPRCMDS operand. However, QOPRCMDS is only valid in a batch client environment.
System Action:
The QOPRCMDS operand is ignored.
Action:
None
0446I
Queue OPER commands if subsystem {<SSID> }not active
Reason:
Response to batch client QOPRCMDS startup JCL PARM operand. <SSID> specifies the
target CA WA ESP Edition subsystem identifier.
System Action:
If the CA WA ESP Edition subsystem is not active, OPER commands will be queued for
later execution when the target subsystem becomes active. Also if the batch client is
connected to a CA WA ESP Edition proxy subsystem with ROUTING set to MASTER and
the XCF ROUTING connection between the proxy and master is not active, OPER
commands will be queued to the proxy's checkpoint file for later execution when the
XCF ROUTING connection between the proxy and master becomes active.
400 - 499
Action:
None
0447I
{Ignore|Queue} OPER commands if subsystem <SSID> not active
Reason:
Response to QOPRCMDS command in a batch client job. <SSID> specifies the target CA
WA ESP Edition subsystem identifier.
System Action:
If no operand or the YES operand was specified and the target CA WA ESP Edition
subsystem is not active, then OPER commands will be queued for later execution when
the target CA WA ESP Edition subsystem becomes active.
If the NO operand was specified and the target CA WA ESP Edition subsystem is not
active, then OPER commands will be ignored. If the STATUS operand was specified, no
action will be taken.
Action:
None
0449C
DVOL HELP
Reason:
Response to DVOL or OPER CALLRTN CYBUT002 command with no operands.
System Action:
Action:
To see DASD volume data, enter DVOL or OPER CALLRTN CYBUT002 with required
operand(s)
400 - 499
450E
EXIT FUNCTION REQUIRED FOR DEFINE REQUEST
Reason:
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.
Action:
Respecify the command or initialization statement.
451E
INVALID EXIT FUNCTION xxxx
Reason:
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.
Action:
Respecify the command or initialization statement using the correct function name.
452W
DUPLICATE MODULE/EXIT SPECIFIED, xxxx/yyyy, IGNORED
Reason:
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.
Action:
Ensure that the duplicate entry is removed from the initialization file.
400 - 499
453E
MODULE xxxx, EXIT nn, GAVE INVALID RETURN CODE OF nn
Reason:
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.
Action:
Notify your software support personnel. This is a user error.
454I
DATA SET xxxx UNALLOCATED
Reason:
A data set was unallocated as a result of the UNALLOC command being issued.
System Action:
The data set is unallocated.
Action:
None
455E
xxxx
Reason:
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.
Action:
Check the message text for the cause.
400 - 499
456C
XMITMDL DISPLAY
Reason:
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.
Action:
None.
457I
NO TRACKING MODELS DEFINED FOR CROSS NODE TRANSMISSION
Reason:
The LIST option of the XMITMDL was requested, but no tracking models were defined
for inter-nodal communication.
System Action:
None
Action:
Use the ADD option of the XMITMDL command to add inter-nodal tracking definitions.
458W
PROGRAM NAME xxxx NOT DEFINED IN JOB TRACKING PROGRAM EXCLUSION LIST
Reason:
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.
Action:
Ensure the program name was correctly specified. To obtain a display of the current
exclusion list, issue the JTPEXCL command without any operands.
400 - 499
459C
JTPE DISPLAY
Reason:
This line is displayed in response to the JTPEXCL command issued with no operands.
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.
Action:
None.
460W
JOB TRACKING EXCLUSION LIST IS EMPTY
Reason:
No job names are excluded from the job tracking function.
System Action:
None
Action:
None
461I
OK
Reason:
API Server normal end of action.
System Action:
Action:
None.
400 - 499
462E
ERROR LOADING/RELOADING/UNLOADING MODULE xxxx
Reason:
The module could not be found by the MVS LOAD macro.
System Action:
The user exit is disabled.
Action:
Ensure that the module name is correct and that it can be found in the link list or in a
STEPLIB library.
463E
MODULE xxxx NOT FOUND
Reason:
A user exit module could not be found in the Load Module Entry list. The module might
not have been defined previously.
System Action:
Action:
Ensure that the module name is correct and that it has been defined previously.
464E
MISSING MODULE NAME
Reason:
There is no MODULE parameter in the DEFINE or EXIT statement.
System Action:
Action:
Add a MODULE parameter and try again.
400 - 499
465E
MODULE mmmm, EXIT nn, ABENDED xxxx, SUSPENDED
Reason:
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.
Action:
Notify your software support personnel. This is a user error.
466E
Unable to read JFCB for DD xxxxxxxx, R15=n
Reason:
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.
Action:
This is most likely an internal error. Contact your software support personnel.
467E
Numeric value <value> exceeds maximum
Reason:
A numeric value has been supplied that exceeds the maximum unsigned 64-bit value
18446744073709551615.
System Action:
Processing of the procedure is stopped.
Action:
Supply a numeric value within the range 0-18446744073709551615.
400 - 499
468I
ESP Workstation Server release <rel> STATUS
Reason:
This is a display of requested information.
System Action:
Action:
None.
469I
xxx xxx xxx ...
Reason:
This is a trace data used for diagnostic purposes.
System Action:
Action:
None.
470I
ES056: xxxxxxxxxxxxx
Reason:
This is tracing information from the Workload Object Interface Layer.
System Action:
Action:
None.
400 - 499
471I
Reason:
This is a tracing information from Multi-Platform Agent Message Router.
System Action:
Action:
None.
472?
<nnn> Client connections have been made, currently <mmm> are/is active
Reason:
Continuation to message 0468: display of requested information.
System Action:
Action:
None.
473I
Command was xxxxxxxxx
Reason:
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
Action:
None
400 - 499
474I
Reason:
This is a tracing information from DM Application Format Services.
System Action:
Action:
None.
475I
xxxx
Reason:
Open/allocation file error. This message is issued when synchronization is requested but
the data set cannot be found.
System Action:
CALLRTN command ignored.
Action:
Correct the trigger Data Set Name and re-issue the command.
476W
EXIT FUNCTION NOT DEFINED
Reason:
No user exit has been defined.
System Action:
The ENABLE|DISABLE|DISPLAY request is ignored.
Action:
Specify a correct exit function and re-issue the request.
400 - 499
477E
Unsigned 64-bit expression evaluates to negative number
Reason:
A CLANG expression with an unsigned 64-bit numeric result evaluates to a negative
number.
System Action:
If the CLANG expression is in an event or procedure, the event or procedure terminates.
Action:
Determine why the CLANG unsigned 64-bit expression results in a negative number and
correct it.
478E
Unsigned 64-bit value too large for signed 32-bit expression
Reason:
A CLANG expression with a signed 32-bit result value includes an unsigned 64-bit
variable or constant with a value exceeding the maximum signed 32-bit positive value
2147483647.
System Action:
Action:
Determine why the CLANG signed 32-bit expression's unsigned 64-bit variable or
constant exceeds 2147483647 and correct it.
400 - 499
479E
Unsigned 64-bit expression overflow
Reason:
A CLANG expression with an unsigned 64-bit numeric result evaluates to a value
exceeding the maximum 18446744073709551615.
System Action:
Action:
Determine why the CLANG unsigned 64-bit expression results in an overflow and correct
it.
480E
Character value overflow in unsigned 64-bit expression
Reason:
A CLANG expression with an unsigned 64-bit numeric result includes a numeric
character variable or constant with a value exceeding the maximum unsigned 64-bit
value 18446744073709551615.
System Action:
Action:
Determine why the CLANG unsigned 64-bit expression's numeric character variable or
constant exceeds 18446744073709551615 and correct it.
481W
YOU ARE NOT AUTHORIZED FOR OPERATOR COMMANDS
Reason:
You must have OPER authority to issue commands that require OPER authority.
System Action:
Action:
Ask Administrator to grant you OPER authority.
400 - 499
482E
Unable to queue directly to system xxxx
Reason:
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.
Action:
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.
483E
System xxxx not a member of shared QUEUE
Reason:
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.
System Action:
Action:
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.
400 - 499
484E
Insufficient CKPT space to queue event for execution
Reason:
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.
System Action:
Action:
Investigate the cause of the shortage of checkpoint space. When this has been
alleviated, enter a TRIGGER command to trigger the event manually.
485E
Insufficient QUEUE file space to queue event for execution
Reason:
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.
System Action:
Action:
Investigate the cause of the shortage of Queue file space. When this has been
alleviated, enter a TRIGGER command to trigger the event manually on the specified
system.
400 - 499
486W
Event xxxx.yyyy not executed
Reason:
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.
Action:
Correct the problem reported in the preceding message. If necessary, enter a TRIGGER
command to trigger the event manually.
487W
CYBESODT ABOVE ERROR OCCURRED DELETING TRIGGER INDEX FOR xxxx.yyyy APPL
aaa.nnn
Reason:
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.
Action:
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.
400 - 499
488E
Invalid FROM or UNTIL date/time in TEMPLIB
Reason:
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.
Action:
Correct the date/time specification in error. Resubmit the job from the appropriate
source.
489E
SYMLIB record length too large
Reason:
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.
Action:
Copy the symbol library to a data set with a legal maximum record length, and re-trigger
the event.
400 - 499
490E
SYMLIB record length too large
Reason:
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.
Action:
Copy the symbol library to a data set with a legal maximum record length, and re-trigger
the event.
491E
COPYJCL not reserved: DDname=xxxx, DSname=yyyy
Reason:
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.
Action:
None. This message is preceded by other errors that must be corrected.
400 - 499
492E
COPYJCL not released: DDname=xxxx, DSname=yyyy DEQ cccc
Reason:
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 task and dequeued or "unsuccessful" - the 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.
Action:
None. This message is preceded by other errors that must be corrected.
493I
JOB TERMINATED BY CCCHK STOP REQUEST
Reason:
As a result of a matching CCCHK statement with the STOP option, the product has
terminated the execution of the job. This message appears in the log and messages for
the job in question.
System Action:
The product terminates the execution of the job.
Action:
None.
400 - 499
494E
Job jjjjjjjj has an illegal RESTART keyword
Reason:
The named job contained a RESTART= operand on the JCL JOB statement. However, it
also requested CA Workload Automation Restart Option EE which depends upon a
product-inserted step being executed as the first step of the job. These conditions are
incompatible, as the RESTART will cause MVS to bypass the product-inserted step.
System Action:
The job is flushed from the internal reader.
Action:
Either:
Remove the RESTART= operand from the JCL JOB statement of the job in question,
or
Change the procedure to not request CA Workload Automation Restart Option EE

for the job in question. Then resubmit the job using CSF or AJ RESUB.
495E
SHADOW start parameter specifies xxxx, must be within range 0-31
Reason:
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:
Action:
Correct the JCL EXEC PARM or START command parameter to specify a shadow image
number xxxx within the range 0-31, and restart the product. Note that the master and
each shadow manager in an XCF group should have a unique shadow image number.
400 - 499
496E
SHADOW requested, SYSPLEX not specified, terminating
Reason:
The product is shadow enabled, that is the JCL EXEC PARM operand or START command
parameter specified the SHADOW and/or PRIMARY or SECONDARY keywords. In
addition, the High Availability Option is installed. However, a SYSPLEX statement was
not specified in the ESPPARM initialization file.
System Action:
Action:
If the product is to run shadow enabled, add a SYSPLEX statement to the ESPPARM file.
If the product is not to run shadow enabled, that is not as a shadow enabled 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.
497E
TRACKOPT MASTER|PROXY|HELD_MANUAL|NOHELD_MANUAL option only valid
during ESP/WM initialization
Reason:
Response to TRACKOPT MASTER, TRACKOPT PROXY, TRACKOPT HELD_MANUAL or
TRACKOPT NOHELD_MANUAL issued a CA WA ESP Edition operator command. CA WA
ESP Edition cannot be set to a master or a proxy and the held manual job feature cannot
be enabled or disabled after initialization.
System Action:
None. Processing continues.
Action:
None.
500 - 599
498I
ESP SHUTDOWN IN PROGRESS, SUBSYS xxxx
Reason:
A shutdown command was issued to the product or a P or STOP command was received.
System Action:
The product continues with the shutdown.
Action:
None.
499I
ESP RELEASE xxxx INITIALIZED, SUBSYS yyyy
Reason:
The product has completed its initialization.
System Action:
Action:
None.
500 - 599
500E
INVALID RECORD TYPE KEY ON USERDEF DATASET FOR ENTRY xxxx
Reason:
A record in the USERDEF data set contains an invalid type indicator.
System Action:
The user entry retrieval request will fail.
Action:
500 - 599
501E
EVENT DATASET ID xxxx, REQUIRED FOR EVENT yyyy.zzzz, NOT FOUND
Reason:
The Event data set required to access the specified Event was not defined to the
product.
System Action:
The Event access fails. If the Event was scheduled for execution, it is ignored.
Action:
Notify your software support personnel. This may be expected after an Event data set
has been deleted.
502E
Tracking transmitter name missing
Reason:
An ISCXMTR statement was encountered with the transmitter name operand missing.
System Action:
The ISCXMTR statement is ignored.
Action:
Correct the ISCXMTR statement to specify a valid transmitter name.
503E
Non-numeric character value in unsigned 64-bit expression
Reason:
A CLANG expression with an unsigned 64-bit numeric result includes a non-numeric
character variable or constant.
System Action:
Action:
Determine why the CLANG unsigned 64-bit expression's character variable or constant is
non-numeric and correct it.
500 - 599
0504I
Subsystem <SSID> not active, command queued for later processing
Reason:
A batch client specified the QOPRCMDS startup JCL PARM operand or the QOPRCMDS or
QOPRCMDS YES command in its SYSIN input stream, and an OPER command was
encountered in the SYSIN input stream while target CA WA ESP Edition subsystem
<SSID> was not active.
System Action:
The OPER command was queued in ECSA virtual storage. When the target CA WA ESP
Edition subsystem becomes active it will process the OPER command.
Action:
None
505W
Node xxxx already defined for tracking model yyyy, ignored
Reason:
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.
Action:
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.
500 - 599
506E
Prefixing must be 0, 1 or 2
Reason:
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.
Action:
Correct the PREFIXING specification.
507E
Missing or invalid agent name in prefix: xxxxxx
Reason:
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.
Action:
This could be caused by an agent name mismatch between the AGENTDEF and
AgentParm files.
508E
Encryption type incompatible with agent xxxxx
Reason:
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.
Action:
This could be caused by a mismatch of the encryption type between the AGENTDEF and
AgentParm files.
500 - 599
509E
Only encrypted messages can be accepted by receiver xxxxxxxx
Reason:
The agent receiver has been configured to receive only encrypted messages.
System Action:
The current message is discarded.
Action:
If non-encrypted messages should be received normally, remove the ENCRYPT keyword
from the AGENTRCV command in ESPPARM.
510E
DATASET NAME NECESSARY FOR AN EVENTSET DEFINE
Reason:
An EVENTSET command was issued to define an Event data set. However, the data set
name was omitted.
System Action:
The EVENTSET command is not processed.
Action:
511E
EVENTSET xxxx NOT DEFINED
Reason:
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.
Action:
500 - 599
512E
EVENTSET xxxx ALREADY DEFINED
Reason:
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:
Action:
If this is for a new definition, ensure you use a unique identifier.
513W
EVENTSET xxxx OPEN, PERFORM CLOSE FIRST
Reason:
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:
Action:
Use the CLOSE option of the EVENTSET command to close the data set, then issue the
delete.
500 - 599
514I
JCL RESTART ADAPTED BY ESP/WM
Reason:
The job contained a RESTART= operand on the JCL JOB statement. However, it also
requested one of the features which depend upon a product-inserted step being
executed as the first step of the job. The product 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.
Action:
None.
515W
EVENTSET xxxx ALREADY OPEN
Reason:
An EVENTSET command was issued to open an already open Event data set.
System Action:
Action:
516W
EVENTSET xxxx ALREADY CLOSED
Reason:
An EVENTSET command was issued to close an already closed Event data set.
System Action:
Action:
500 - 599
517A
CONFIRM REQUEST TO DELETE EVENTSET xxxx, REPLY Y OR N
Reason:
An EVENTSET command was issued to delete an Event data set.
System Action:
Action:
Reply Y if you wish to continue with the delete request, otherwise reply N to cancel the
request.
518I
DELETE REQUEST CANCELLED
Reason:
This message is issued if a reply of N was given to message 517.
System Action:
The delete request is not performed.
Action:
None.
519I
EVENTSET xxxx DELETED
Reason:
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.
Action:
None.
500 - 599
520E
EVENTSET WITH DSN xxxx ALREADY DEFINED
Reason:
An EVENTSET command was issued to define an Event data set. However, a data set is
already defined with the same dsname.
System Action:
Action:
Ensure that you specify the correct name. If you wish to alter a definition, use the SET
option of the EVENTSET command.
521I
EVENT DATA SET xxxx SUSPENDED
Reason:
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.
Action:
None.
522E
ERROR OCCURRED READING xxxx.yyyy EVENT DEFINITION
Reason:
An I/O error occurred reading an Event definition.
System Action:
Action:
Wait for and examine message 523.
500 - 599
523W
xxxx
Reason:
This message describes the error encountered while reading and Event definition.
System Action:
This message is followed by a message indicating the action that the product will take.
Action:
Note any message that follows.
524W
EVENT xxxx.yyyy DEFERRED
Reason:
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 described is
corrected.
Action:
Notify your software support personnel of the error condition.
525I
VS COMMAND NOT AUTHORIZED IN EVENT xxxx.yyyy
Reason:
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.
Action:
None.
500 - 599
526E
xxxx
Reason:
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.
Action:
527W
Event xxxx.yyyy delayed nn minute(s) due to contention on aaaa
Reason:
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.
Action:
If this condition persists, determine the user having the data set allocated, and request
they free it.
528E
ERROR OCCURRED PROCESSING EVENT xxxx.yyyy {TRDSN xxxx|IN APPL xxxx.yy}
Reason:
This message indicates that some error has occurred during the execution of an Event. If
the event was triggered by a dataset, the dataset is displayed after 'TRDSN'. If the event
failed when submitting a job, the application name and its generation number is
displayed.
System Action:
This message is followed by another message describing the actual error.
Action:
Respond to the next message.
500 - 599
529E
ERROR OCCURRED UPDATING xxxx.yyyy
Reason:
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.
Action:
Respond to the next message.
530E
NO SPACE LEFT IN CHECKPOINT
Reason:
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.
Action:
Use the LISTCKPT command to determine the amount of space remaining in the
checkpoint.
531W
Event xxxx.yyyy delayed nn minute(s) due to migrated data set aaaa
Reason:
The data set 'aaaa' required for the submission of JCL during the 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.
Action:
If this condition persists, determine why the data set has not been recalled.
500 - 599
532W
EVENT xxxx.yyyy SUSPENDED
Reason:
An error occurred while computing the next scheduled execution time of an Event.
System Action:
The Event is suspended.
Action:
This message is preceded by messages describing the error. The corrective action
depends on the error.
533W
GROUP 'xxxx' NOT DEFINED
Reason:
The product 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 the product will take.
Action:
The GROUP or USER entry to which the Event belongs may have been deleted.
534W
ERROR ON JCL FOR EVENT
Reason:
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.
Action:
Take action according to the messages that follow.
500 - 599
535I
xxxx
Reason:
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.
Action:
Correct the error indicated by the message.
536W
INVALID EVENT ID ON INCLUDE STATEMENT
Reason:
A %INCLUDE statement contained an invalid Event name as an operand of the EVENT
keyword.
System Action:
Action:
Correct the EVENT name.
537I
Attempting to recall data set nn
Reason:
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 indicated in
messages following this message.
Action:
If necessary, retry the function using data set "nn" after it has been recalled.
500 - 599
538I
Migrated data set function is not available
Reason:
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.
Action:
None.
539W
ERROR ON DAY OF WEEK FIELD
Reason:
A JCL image statement described by previous messages contained an invalid day of
week name.
System Action:
Action:
Correct the day of week name.
540E
INSUFFICIENT CHECKPOINT SPACE TO QUEUE EVENT xxxx
Reason:
During a DEFINE or TRIGGER, the product 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.
Action:
The Event should be triggered when more checkpoint space becomes available.
500 - 599
541E
EVENT DATASET ID xxxx NOT FOUND
Reason:
An Event data set needed to store or retrieve an Event could not be found.
System Action:
The storage or retrieval request fails.
Action:
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.
542W
INVALID INCLUDE STATEMENT SYNTAX
Reason:
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.
Action:
See description for message 544.
543W
INVALID TIME SYNTAX ON INCLUDE STATEMENT
Reason:
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.
Action:
See description for message 544.
500 - 599
544W
JOB xxxx DELETED, WILL NEED RESUBMISSION
Reason:
An error, described by a preceding message, was found in the JCL of a 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.
Action:
Correct the error and resubmit the job if necessary.
545E
Error in xxxx, RC=nn
Reason:
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.
Action:
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.
500 - 599
546E
INSUFFICIENT CHECKPOINT SPACE TO QUEUE EVENT FOR DELAYED EXECUTION
Reason:
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.
Action:
The Event will have to be manually rescheduled, or triggered, once some space is freed
up in the checkpoint.
547W
EVENT xxxx.yyyy NOT EXECUTED
Reason:
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 be bypassed.
Action:
548W
SWITCH TO SUBMISSION SUBTASK FAILED, MAIN TASK USED
Reason:
The product was unable to switch to a subtask while performing the execution of an
Event.
System Action:
The product will execute the Event at the main task level. This can cause the product to
take slightly longer to respond to user or operator requests, as they are serialized with
submission processing.
Action:
If this message is repeated often, notify your software support personnel.
500 - 599
549W
xxxx
Reason:
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.
Action:
550E
xxxx
Reason:
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 will not be executed.
Action:
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.
551W
ERROR COPYING JCL FOR EVENT xxxx.yyyy
Reason:
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.
Action:
Take action according to the message that follows.
500 - 599
552W
xxxx
Reason:
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.
Action:
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.
553W
EVENT xxxx.yyyy BYPASSED, CLASS zzzz SUSPENDED
Reason:
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.
Action:
None. This was requested by an operator command.
500 - 599
554W
EVENT xxxx.yyyy HELD, CLASS zzzz
Reason:
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.
Action:
None. This was requested by an operator command.
555E
RACINIT FOR USER xxxx FAILED, ERROR CODE nn
Reason:
While executing an Event, the product attempted to initialize the user's environment.
The RACF initialization request failed.
System Action:
The Event is not executed.
Action:
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.
500 - 599
556I
VS COMMAND SUPPRESSED BY USER EXIT IN EVENT xxxx.yyyy
Reason:
A VS command requested in an Event or Procedure was rejected by the installation
command exit.
System Action:
The VS command is suppressed.
Action:
Check with your installation system programming team.
557E
RECORD LENGTH OF DATA SET xxxx EXCEEDS MAXIMUM LENGTH OF 136
Reason:
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.
Action:
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.
558W
Event xxxx.yyyy delayed nn minute(s), data set aaaa is offline
Reason:
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.
Action:
None. If the volume is no longer in use, edit the Event to point to the new volume.
500 - 599
559E
UNBALANCED PARENTHESES FOR IF KEYWORD OF INCLUDE STATEMENT
Reason:
The IF keyword of the %INCLUDE or %EXCLUDE statement had an unequal number of
left and right parentheses.
System Action:
Action:
Check the number of parentheses. Probably the closing parenthesis was omitted.
560W
ERROR ON SYMBOL LIBRARY SCAN FOR EVENT
Reason:
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.
Action:
Look at the messages that follow. Look at the messages that follow.
561I
DATA SET xxxx LINE nn
Reason:
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.
Action:
Look at the messages that follow. Look at the messages that follow.
500 - 599
562I
JOB xxxx DELETED BY INSTALLATION EXIT
Reason:
The installation exit requested deletion of the job.
System Action:
The job is deleted.
Action:
The job may requires resubmission.
563W
xxxx NOT FOUND FOR EVENT yyyy.zzzz
Reason:
During SADGEN (Scheduled Activity Data GENeration), an entry was not located in the
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.
Action:
The Event needs to be updated to specify the correct entry name, or the entry that the
Event requires needs to be defined.
500 - 599
564E
Event xxxx.yyyy terminated due to msg limit exceeded
Reason:
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 using the MSGLIMIT statement in the 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.
Action:
If the Event needs to issue more messages than the current message limit, specify a
higher value on the MSGLIMIT statement in the Procedure.
565E
SCANTIME VALID ONLY ON DEFINE
Reason:
The scan time has already been established for this event set. It cannot 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.
Action:
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.
500 - 599
566E
AFM invalid, xxxx
Reason:
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.
Action:
If the AFM was generated by a user, correct it and re-enter it into the subsystem. If the
AFM was generated internally by the product, call CA Support.
567E
AFM destination name xxxx is too long
Reason:
The length of destination name xxxx (3rd positional operand) of an Automated
Framework Message (AFM) exceeds the maximum (100 bytes).
System Action:
Action:
If the AFM was generated by a user, correct it and re-enter it into the subsystem. If the
AFM was generated internally by the product, call CA Support.
500 - 599
568E
AFM destination xxxx not defined
Reason:
Destination name xxxx (3rd positional operand) of an Automated Framework Message
(AFM) is not defined to the product, that is it does not specify a valid network node
(typically an AGENT or DMANAGER).
System Action:
Action:
Ensure that the destination name xxxx was correctly specified (defined in the AGENTDEF
file if an AGENT or DMANAGER).
569W
Shadow manager not joined to XCF group, terminating
Reason:
This instance of the product 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
Action:
Investigate and correct the XCF problem.
500 - 599
570S
QUEUE DATASET CONTROL INFORMATION HAS BEEN CORRUPTED
Reason:
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.
Action:
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.
571W
PLEASE RESTART THE SUBSYSTEM AFTER THE FOLLOWING ABEND
Reason:
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.
Action:
This message will be followed by message 572. Follow the instructions to the next
message.
572W
IF ABENDS PERSIST, RESTART WITH THE QFORM OPTION
Reason:
This is the third message regarding the situation
System Action:
None.
Action:
See messages 570S and 571W for complete information.
500 - 599
573E
QUEUE DATASET INFORMATION RECOVERED AFTER ERROR
Reason:
The product detected a corruption in the queue data set prior to a write. However, the
information was recovered from the previous write.
System Action:
A system dump is taken. Processing continues.
Action:
The dump should be sent to CA Support for analysis.
574E
QUEUE DATASET REFORMATTED
Reason:
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.
Action:
Please forward the dump to CA Support for analysis.
575E
Event xxxx.yyyy not found, needed for zzzz{.aaaa} in Appl bbbb.nn
Reason:
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.
Action:
The Event will need to be redefined, and the job resubmitted using CSF or the AJ
command.
500 - 599
576E
Overlength message received by Agent Receiver xxxx
Reason:
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.
Action:
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.
579E
ESP not SHADOW enabled, SHADGOAL invalid
Reason:
A SHADGOAL initialization parameter was encountered, but SHADOW(n) had not been
specified. This instance of the product is not SHADOW enabled.
System Action:
The subsystem does not initialize.
Action:
Specify SHADOW(n) as a start parameter, or remove SHADGOAL from the ESPPARM
500 - 599
580W
INDEX DATASET FULL FOR PREFIX xxxx
Reason:
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.
Action:
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.
581W
ABOVE ERROR OCCURRED DELETING TRIGGER INDEX FOR xxxx.yyyy
Reason:
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.
Action:
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
500 - 599
582W
DATA SET TRIGGERING SUSPENDED DUE TO PRIOR REQUEST
Reason:
This message is issued when the product 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.
Action:
If you wish data set triggering to be resumed, use the DSTRST command with the
RESUME option.
583W
EVENT EXECUTION SUSPENDED DUE TO PRIOR REQUEST
Reason:
This message is issued when the product 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.
Action:
If you wish to restart Event execution, use the RESTART command.
584E
INDEX DATASET ERROR, DATASET TRIGGERING NOT FULLY INITIALIZED
Reason:
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.
Action:
Correct the I/O on the INDEX data set.
500 - 599
585E
INDEX DATA SET ERROR CAUSING SUSPENSION OF DATA SET TRIGGERING
Reason:
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.
Action:
Notify your software support personnel. When the problem with the INDEX data set is
corrected, resume data set triggering with the DSTRIG command.
586E
ESP/WM not set to master or proxy, reply M for master or P for proxy
Reason:
A subsystem has not been set to a master or a proxy.
System Action:
The operator is prompted to specify whether the subsystem must be set to a master or
a proxy.
Action:
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 subsystem to a master
TRACKOPT PROXY to set the system to a proxy system.
587E
GROUP PREFIX xxxx NOT AUTHORIZED FOR SYMTAB yyyy
Reason:
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.
Action:
The access to symbol tables is controlled by the administrator.
500 - 599
588I
EVENT xxxx.yyyy AUTODELETED
Reason:
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.
Action:
None.
589E
ERROR OCCURRED DURING AUTODELETE OF EVENT xxxx.yyyy
Reason:
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.
Action:
The Event may need to be deleted manually.
590E
JOB AUTH TABLE xxxx NOT FOUND FOR USER yyyy
Reason:
The product 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:
Action:
Notify your installation CA Support personnel.
500 - 599
591E
I/O ERROR RETRIEVING JOB AUTH TABLE xxxx FOR USER yyyy
Reason:
An I/O error occurred while the product tried to read a job authorization table to verify
a user's access to a job.
System Action:
Action:
Notify your installation CA Support personnel.
592E
EVENT EXECUTION CANCELLED BY INSTALLATION EXIT
Reason:
The execution of an Event was cancelled by the installation defined event execution
exit.
System Action:
The processing for the Event is bypassed.
Action:
Check with the installation support team.
593E
INVALID REQUEST CODE xxxx IN TDR, REQUEST BYPASSED
Reason:
An invalid request code was found in a TDR (Time Driven Request) element.
System Action:
The TDR is bypassed.
Action:
This is probably due to an I/O error or a logic error in the program. Notify your software
support personnel.
500 - 599
594E
NO EVENT DATASETS DEFINED
Reason:
No Event data sets were found to exist when a request was made to the subsystem.
System Action:
Action:
Ensure that at least one Event data set is defined to the product.
595E
TRACKOPT PROXY invalid for shadow enabled ESP/WM
Reason:
Response to TRACKOPT PROXY command. The current system is shadow enabled. A
shadow enabled system cannot be set to a proxy system.
System Action:
The command fails.
Action:
If the system is intended to be a proxy, then remove the SHADOW, PRIMARY and/or
SECONDARY keywords from the JCL EXEC PARM operand. If the system 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.
500 - 599
596E
AGENTRCV {NO}PREFIXING obsolete, TCP/IP data prefixing auto-detected
Reason:
An AGENTRCV command was issued specifying obsolete keyword NOPREFIXING or
PREFIXING. Agent receivers 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:
Action:
If the AGENTRCV command was specified in a file, remove the NOPREFIXNG or
PREFIXING operand. Otherwise none.
597W
Manager address not available
Reason:
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:
Action:
If required, issue a LOADAGDF command to process an AGENTDEF file that includes a
"MANAGER TCPIP" command. Then re-issue the MGRADDR command.
500 - 599
598E
PORT only valid for MGRADDR AGENT option
Reason:
Response to MGRADDR command. The PORT keyword is not valid unless the MGRADDR
command included the AGENT keyword.
System Action:
Action:
If required, re-issue the MGRADDR command with compatible operands.
599W
NO MORE xxxx DATES DEFINED
Reason:
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.
Action:
Extend the special day definition.
600 - 699
600 - 699
600E
INCOMPLETE DATE/TIME SPECIFICATION
Reason:
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.
Action:
Respecify the date and time.
601E
NO MORE xxxx DATES DEFINED
Reason:
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.
Action:
Extend the special day definition.
602E
DATE xxxx NO LONGER DEFINED
Reason:
An Event definition contained reference to a special day that was no longer defined.
System Action:
The schedule element cannot be cycled any more.
Action:
Redefine the Event so as to avoid the special day, or define the special day.
600 - 699
603E
SYSTEM CLOCK NON-OPERATIONAL
Reason:
The system clock is not operational.
System Action:
Depends on which component detected the error.
Action:
The product should be brought down and restarted when the CPU clock is restored.
604E
INVALID DATE/TIME SPECIFICATION
Reason:
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.
Action:
Respecify the date and or time.
605E
INCONSISTENT DATE PARAMETERS
Reason:
Inconsistent parameters were detected on the date/time specification. For example,
30FEB1984 is inconsistent, as February contains 29 days in 1984.
System Action:
Action:
600 - 699
606E
NO DATE SPECIFIED
Reason:
No data recognizable as a date or time were specified where expected.
System Action:
Action:
607E
SYNTAX ERROR STARTING AT 'xxxx'
Reason:
An unrecognizable parameter was detected in a date/time specification.
System Action:
Action:
608E
INVALID CONVERSION REQUEST
Reason:
This is probably an internal logic error.
System Action:
The time conversion request is denied.
Action:
600 - 699
609E
PARAMETER STARTING 'xxxx' NOT VALID IN SPECIFIED CONTEXT
Reason:
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.
Action:
Re-enter the time schedule correctly. The parameters might need to be specified in a
different order.
610E
SCHEDULE STATEMENT INCOMPLETE
Reason:
Parameter specification in a time or schedule statement ended prematurely.
System Action:
The specification is ignored.
Action:
Retype the schedule statement in full.
611E
INTERNAL FORMAT ERROR IN TIME ELEMENT
Reason:
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.
Action:
600 - 699
612E
NO MORE COMPLETE xxxx PERIODS DEFINED
Reason:
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.
Action:
Check the period definitions.
613E
INVALID SCHEDULE TERM USAGE
Reason:
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.
Action:
You should include enough information to provide an iteration algorithm.
614E
SPECIFIED INTERVAL INVALID IN CURRENT CONTEXT
Reason:
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.
Action:
Correct the schedule specification.
600 - 699
615E
REQUESTED OPTION NOT SUPPORTED IN CURRENT CONFIGURATION
Reason:
You requested a time or schedule option that is only supported with the extended
scheduling option installed.
System Action:
The request cannot be completed.
Action:
Respecify the schedule or time statement omitting the unsupported parameters. If this
is inconvenient, install the extended scheduling option.
616E
Auxiliary address space initialization failed
Reason:
During the initialization of an auxiliary address space, an unexpected error occurred
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 occurred. 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.
Action:
Contact your software support personnel. Have the registers at the time of the error
available.
600 - 699
617I
Invalid environment for CYBSS007-Valid only in a system address space
Reason:
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.
Action:
Do not attempt to execute CYBSS007 yourself.
618W
Duplicate auxiliary address space
Reason:
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 instead.
Action:
None.
619E
The length of the following command exceeds 32763 characters:
Reason:
A command was encountered that exceeds 32763 characters, the maximum allowed.
System Action:
The requested command is rejected, processing stops.
Action:
Divide the long command into several shorter commands.
600 - 699
620E
DATA SET xxxx NOT CATALOGUED
Reason:
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.
Action:
Ensure the correct data set name is specified.
621E
CATALOG ERROR CODE nn FOR DATA SET xxxx
Reason:
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.
Action:
Error codes are documented in the manual System Messages and Codes.
622E
NO DATA SET/DDNAME SPECIFIED FOR FREE REQUEST
Reason:
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.
Action:
Notify the software support group.
600 - 699
623E
DATA SET xxxx IS NOT A MEMBER OF A GENERATION GROUP
Reason:
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.
Action:
Ensure the correct data set was specified. A generation data group base should be
defined.
624E
Unable to open data set xxxx
Reason:
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.
Action:
Rectify the cause of the failure.
625E
I/O ERROR ON xxxx,yyyyzzzz,aaaa
Reason:
An I/O error occurred while attempting to access this data set.
System Action:
Action:
Try again. If the problem persists, ask your System Administrator to repair this data set.
600 - 699
626E
xxxx
Reason:
An error occurred while processing a slotted data set.
System Action:
The requested I/O service was not performed.
Action:
Gather the JES job log for ESP, the ESP audit log and the system log and contact CA
Support.
627E
ERROR LOADING MODULE xxxx FOR yyyy COMMAND
Reason:
A command processor module "xxxx" was invoked to process the command identified
by "yyyy". The module could not be loaded.
System Action:
Action:
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.
628W
Reason:
This command name has invalid syntax.
System Action:
The command was not executed.
Action:
600 - 699
629E
Result exceeds maximum value of 50000
Reason:
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.
Action:
Ensure that such calls to this function produce results in the allowed range.
630E
Result exceeds maximum value of 50000
Reason:
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.
Action:
Ensure that such calls to this function produce results in the allowed range.
631W
Data set xxxx is unformatted
Reason:
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.
Action:
Note the message that follows.
600 - 699
632C
MGRADDR Command Options
Reason:
Response to MGRADDR HELP command. The MGRADDR command options are
displayed.
System Action:
Action:
None.
633E
Invalid record header encountered, Slot nn, data set xxxx
Reason:
A record on the specified data set contained invalid data. The 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.
Action:
634E
Attempt made to write too long a record to data set xxxx, Size=nnnn,
Maximum=mmmm
Reason:
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.
Action:
Note the message that follows. Notify your software support personnel.
600 - 699
635E
Record too large for input buffer, data set xxxx, Slot nn
Reason:
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:
time.
Action:
636E
ATTEMPT MADE TO FREE AN INVALID SLOT NUMBER
Reason:
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:
time.
Action:
600 - 699
637E
Insufficient free slots in data set xxxx
Reason:
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.
Action:
Check the description for the message that follows.
638E
Attempt made to write to slot 0, data set xxxx
Reason:
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.
Action:
Contact your software support personnel.
600 - 699
639E
xDab <request>, Dsn=<dsname> not open
Reason:
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.
<request> specifies the VSAM data set access request.
<dsname> specifies the VSAM data set name.
System Action:
The operation is not performed. This message is returned to the caller as an I/O error.
Action:
If the problem persists, contact CA Support.
640E
INVALID FRB OPERATION, DATA SET IS NOT OPEN
Reason:
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:
Action:
Please contact your software support personnel for further assistance.
600 - 699
641E
IEFSSREQ SSVI function SSOBRETN=nn, Subsystem=xxxx
Reason:
A request to obtain version information from MVS subsystem xxxx failed with an
unexpected SSOB return code nn.
System Action:
Action:
Should never happen. If it does, attempt to determine the cause of the problem and, if
possible, correct it. If the product issued this message during initialization, it should be
recycled after the problem is corrected.
642E
IEFSSREQ error return code nn, Subsystem=xxxx
Reason:
A request to obtain version information from MVS subsystem xxxx failed with an
unexpected return code nn.
System Action:
Action:
600 - 699
643E
Subsystem xxxx {does not support SSI function yyyy|not active|not defined to MVS}
Reason:
A request to obtain version information from MVS subsystem xxxx failed for the reason
specified in the message.
System Action:
Action:
644E
Subsystem xxxx does not support JES_NODE|JES_MEMBER_NAME keyword
Reason:
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 name or JES
member name.
Action:
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 the product issued this
message during initialization, it should be recycled after the problem is corrected.
600 - 699
645E
xxxx repeat interval unit invalid
Reason:
A repeat unit interval not supported by the issued command was specified. This is the
case for the procedure RUN command. xxxx is one of the following: YEAR, MONTH,
HOUR, MINUTE, SECOND, unknown. Only WEEK{S} and DAY{S} are supported by the
command.
System Action:
The command is not processed. If the error occurred in a procedure RUN command,
then the event that invokes the procedure is suppressed.
Action:
Correct the error. If the error occurred in a procedure RUN command, then correct the
RUN command and trigger the event again.
646E
Null token passed to event service
Reason:
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 initialization.
System Action:
The requesting task terminates abnormally with code U1203.
Action:
Internal logic error. Should never happen. Contact your software support personnel.
600 - 699
647E
Event token xxxxxxxx at yyyyyyyy invalid
Reason:
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 initialization.
System Action:
The requesting task terminates abnormally with code U1203.
Action:
648E
ERROR OCCURRED OPENING TRACE DATA SET
Reason:
The trace data set could not be opened.
System Action:
The trace function is not activated.
Action:
Check the previous message for further information regarding this error.
649E
INVALID ROSCOE LIBRARY MEMBER NAME, xxxx
Reason:
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.
Action:
Correct the member name and try again.
600 - 699
650I
TRACE PROCESSING INITIALIZED
Reason:
The trace requested by a TRCINIT command has been successfully initialized.
System Action:
Tracing will be enabled.
Action:
None.
651E
INSUFFICIENT VIRTUAL STORAGE FOR TRACE BUFFERS
Reason:
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.
Action:
Specify a smaller buffer count, or increase the virtual region size for the subsystem.
652E
ERROR OCCURRED ALLOCATING/OPENING TRACE DATA SET
Reason:
A trace data set could not be allocated.
System Action:
Action:
Check the previous message for further information regarding this error.
600 - 699
653E
ERROR ATTACHING TRACE SUBTASK
Reason:
The TRCINIT function could not be started.
System Action:
Action:
Examine the JES job log for ESP to determine the nature of the error. If you are not able
to determine the cause of the error, this log and the system SYSLOG should be collected.
Contact CA Support.
654E
TRACE ALREADY INITIALIZED
Reason:
The trace data set is already initialized.
System Action:
Action:
Use TRACE REUSE to reuse the trace data set.
655W
TRACE NOT CURRENTLY INITIALIZED
Reason:
The trace function is not available, since it wasn't defined in the initialization
parameters.
System Action:
Action:
Add a TRACEDEF statement to the initialization parameters.
600 - 699
656E
INVALID TRACE ID ELEMENT/RANGE SPECIFIED
Reason:
The SET or RESET parameter was invalid.
System Action:
Action:
Correct the SET or RESET parameter and try again.
657I
TRACE RECORDING ON DATA SET xxxx
Reason:
The trace function has been activated.
System Action:
Action:
None required.
658I
DATA SET xxxx FULL
Reason:
The trace data set is full.
System Action:
The product has attempted to switch trace data sets.
Action:
Consider allocating larger trace datasets or allocating more trace datasets.
600 - 699
659C
TRACE STATUS
Reason:
The status of the trace data sets is being displayed.
System Action:
Action:
None required.
660S
UNABLE TO ATTACH A SUBTASK, MONITOR ENDED
Reason:
The product is unable to initialize itself in the ROSCOE environment.
System Action:
The product is not available.
Action:
Check the status of the ROSCOE system. A storage shortage might be causing this
problem. If the problem persists, please contact your software support personnel for
further assistance.
661S
MONITOR SUBTASK ABEND Sxxxx, Uyyyy
Reason:
The product has abended under the ROSCOE subtask.
System Action:
The product is no longer available to ROSCOE users.
Action:
Check the status of the ROSCOE system. A storage shortage might be causing this
problem. If the problem persists, please contact your software support personnel for
further assistance.
600 - 699
662E
TCBTOKEN error, Return=<rc>, DataSpace=<name>
Reason:
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.
Action:
Should never happen. Contact your software support personnel.
663E
ALESERV ADD error, Return=<rc>, DataSpace=<name>
Reason:
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.
Action:
600 - 699
664S
xDspace Create|Delete|Extend|Release|Load|Out, CBID=X'<hexid>'(<ident>) invalid,
must be X'C4E2C4C1|E2E2E2C1'(DSDA|SSSA)
Reason:
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.
Action:
665E
DspServ Create|Delete|Extend|Release|Load|Out error, Return=<rc>,
Reason=X'<reason>', Name=<name>, Blocks={+}<number>{, Maximum=<maxnum>}
Reason:
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.
System Action:
The data space request fails.
Action:
If error message does not give sufficient information to correct the problem, and it
persists, then contact your software support personnel.
600 - 699
666S
xHspace Create|Delete|Extend|Release|SRead|SWrite, CBID=X'<hexid>'(<ident>)
invalid, must be X'C8E2C4C1|C8E2D9C1|E2E2E2C1'(HSDA|HSRA|SSSA)
Reason:
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.
Action:
667E
DspServ|HspServ Create|Delete|Extend|Release|SRead|SWrite error, Return=<rc>,
Reason=X'<reason>', Name=<name>, Blocks={+}<number>{, Maximum=<maxnum>}
Reason:
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.
Action:
If error message does not give sufficient information to correct the problem, and it
persists, then contact your software support personnel.
600 - 699
668E
<name> error{, Invalid FSQE at <address>}, <reason>
Reason:
Verification of a space object indicated that it is incorrectly formatted. If <name>
specifies NETQUEUE under the product, 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.
Action:
For the NETQUEUE space object of a 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 the product. Then correct the NETQUEUE command and restart the product.
For the NETQUEUE space object of a 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.
Important! 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 content of the data set will
be lost.
600 - 699
669W
Time RetCode=<rc>, <name> space object format date and time unavailable
Reason:
While formatting space object <name>, an attempt to determine the current date and
time failed with error return code <rc>.

<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.
Action:
None. Should never happen.
670C
<name> Space Object
Reason:
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.

System Action:
The specified space object's attributes and space usage data are displayed.
Action:
None.
600 - 699
671S
xSpace Get|Free|Extend{, {Name=<name>|Address=<freeaddr>}}, Length=<length>{,
Invalid FSQE at <fsqeaddr>|<reason>}
Reason:
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.
Action:
Contact your software support personnel. 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.
0672C
LHBSF
Reason:
Response to LHBSF command to display Hiperspace Buffer Swap Facility (HBSF) status.
HBSF is used by CA WA ESP Edition to process subsystem request commands from ESP
clients.
System Action:
Action:
None.
600 - 699
673E
xHbsf Create|Delete|GetSize|GetBuf|FreeBuf|RelBuf|Display, <reason>
Reason:
A HiperSpace Buffer Swap Facility (HBSF) request failed. HBSF is used by the product to
process subsystem request commands from clients. <reason> specifies the reason for
the HBSF failure.
System Action:
Processing continues but the subsystem request cannot be serviced.
Action:
If the problem persists, contact your software support personnel.
674S
xHbsf Create|Delete|GetSize|GetBuf|FreeBuf|RelBuf|Display, <reason>
Reason:
A HiperSpace Buffer Swap Facility (HBSF) request failed. HBSF is used by the product to
process subsystem request commands from clients. <reason> is the reason for the HBSF
failure.
System Action:
The task is abnormally terminated with code U1112.
Action:
675I
Update successful
Reason:
New or modified encryption key has been stored successfully.
System Action:
N/A.
Action:
None required. The key will be available for agent communications next time the agent
definitions are loaded.
600 - 699
676E
<keyword> must be specified
Reason:
CRYPTKEY command was entered without a keyword that is required.
System Action:
Command is rejected.
Action:
Reenter the command with all necessary parameters.
677W
No entries found to match your criteria
Reason:
CRYPTKEY LIST command found no keys matching the request.
System Action:
The list is not displayed.
Action:
Not required.
678E
Error retrieving encryption key named <kkkk>
Reason:
Agent definition file refers to a key named <kkkk>, which was not found in key
repository.
System Action:
New agent definitions are not loaded.
Action:
Verify 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.
600 - 699
679E
Key name is mutually exclusive with explicit key
Reason:
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.
Action:
Correct the statement by removing either the explicit key or the key name. Reenter the
LOADAGDF command.
680E
UNABLE TO LOAD ISPF INTERFACE MODULE
Reason:
The ISPLINK module could not be loaded.
System Action:
The ISPF interface cannot be supported.
Action:
Ensure that your LOGON procedure specifies a STEPLIB library that contains the ISPLINK
module.
681E
ERROR WITH ISPF INTERFACE
Reason:
An unknown error occurred inside the ISPF interface module.
System Action:
Action:
Logon to TSO again and retry.
600 - 699
682E
UNABLE TO LOAD ISPEXEC MODULE
Reason:
The ISPEXEC module could not be loaded.
System Action:
Action:
Ensure that your LOGON procedure specifies a STEPLIB library that contains the ISPEXEC
module.
683E
SEVERE ERROR FROM ISPF INTERFACE
Reason:
A return code of 20 was returned by the ISPF interface module.
System Action:
The ISPF interface cannot be initialized.
Action:
Logon to TSO again and retry.
684W
No matching entries found
Reason:
A request to list encryption keys found no entries that fit the selection criteria.
System Action:
No list is produced.
Action:
Not required.
600 - 699
685E
Duplicate key entry
Reason:
An attempt was made to define an encryption key with a name that already exists in the
repository.
System Action:
Action:
Either use a different name or change the request from DEFINE to UPDATE.
686E
Key does not match, update refused
Reason:
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:
Action:
687E
You are not authorized to update key entries
Reason:
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:
Action:
Either provide the correct old key or ask the system administrator for assistance.
600 - 699
688E
Specified key entry not found
Reason:
A request to modify or delete an encryption key, but the key entry was not found in the
repository.
System Action:
The system could not complete the request.
Action:
Check the original request for the correct key.
689E
Above error occurred during CKDE initialization
Reason:
An error occurred during initialization of key repository service. A preceding message
explains the error.
System Action:
Key repository service will not be available.
Action:
The error described by the preceding message must be corrected.
600 - 699
690E
Insufficient checkpoint/queue file space for event execution request
Reason:
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.
Action:
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).
691W
Processing of <n> events ended abnormally in the previous session
Reason:
During a warm start, the product 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.
Action:
Review the ESP692I messages and verify whether the individual events have to be
reprocessed.
600 - 699
692I
Event <event data>
Reason:
The event described in this message was executing when the product 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 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.
Action:
Examine the results of the interrupted event execution and re-trigger the event (or
resubmit the affected job) if necessary.
693E
Reason:
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.
Action:
Report problem to Level 2 Support.
694E
Invalid TIMEREF adjustment: <adjustment string>
Reason:
The value of TIMEREF parameter of a TIMEZONE statement is invalid.
System Action:
Message ESP802A prompts operator to correct the error.
Action:
Respond to message ESP802A.
600 - 699
695E
STRING STARTING 'xxxxx' HAS MULTIPLE RANGES AND ONE ORDINAL EXCEEDS 31
Reason:
A time schedule specification contains multiple ranges and at least one ordinal value is
greater than 31 (such as 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.
Action:
Split up the SCHEDULE statement into one or more statements containing one range
each for a given level.
696A
CCCHK aa bb cc dd CC=ee=X'ff' Reply: C=Fail/Continue, S=Fail/Stop, O=OK/Continue
Reason:
A job step terminated and its completion code matched the conditions specified in a
CCCHK statement that specifies ASK.
aa, bb, ... ff represent:
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.
Action:
Reply C, S, or O.
600 - 699
697E
Allocation of CCCHK ASK work area failed S=Fail/Stop assumed.
Reason:
A job step terminated and its completion code matched the conditions specified in a
CCCHK statement that specifies ASK, however a subroutine of the product'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:
The product terminates the execution of the job.
Action:
None.
698E
Both ALERT and EVENT specified
Reason:
These parameters cannot both be specified on the same statement
System Action:
The NOTIFY statement is rejected.
Action:
Correct the NOTIFY statement.
699E
CANNOT GO BEYOND DECEMBER 31, 2040.
Reason:
A date was calculated which was past December 31, 2040. This date is last date
supported.
System Action:
The current function is terminated.
Action:
Change the date calculation so the result will not be beyond the last supported date.
700 - 799
700 - 799
700E
CANNOT GO BEYOND SEPTEMBER 17, 2042.
Reason:
A date was calculated which was past September 17, 2042. This date is last date
supported.
System Action:
The current function is terminated.
Action:
Change the date calculation so the result will not be beyond the last supported date.
701E
DOs exceed ENDDOs in application
Reason:
DOs exceed ENDDOs in application
System Action:
Action:
Correct the CLANG statements as appropriate
702E
Too many DO statements
Reason:
More than 255 nested DO statements
System Action:
Action:
700 - 799
703E
ELSE not preceded by IF at same level
Reason:
ELSE not preceded by IF at same DO/ENDDO level
System Action:
Action:
704E
Too many ENDDO statements
Reason:
More ENDDO statements than DO statements in application
System Action:
Action:
705I
Current message prefix is <prefix>
Reason:
This message is displayed when "oper msgprfx" command without operands is issued by
TSO users.
System Action:
System just displays the current message prefix and does no changes.
Action:
User can change the message prefix by supplying it as an operand to the command, ex.
"oper msgprfx MyPrefix"
700 - 799
706I
DATE ADVANCED nnxxxx TO yyyy
Reason:
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.
Action:
Ensure that this is what you intended, otherwise respecify the date.
707E
Insufficient CSA to load time zone table
Reason:
The product could not obtain enough storage in CSA to load the time zone table.
System Action:
The time zone table. Processing continues without it.
Action:
The subsystem can be stopped and restarted when the CSA shortage is relieved.
708E
RESOURCE CONFLICT - TYPE MUST BE THE SAME AS PREVIOUSLY DEFINED
Reason:
Two RESOURCE statements specify the same resource, but types are different. For
example, one statement specifies resource as GLOBAL, the other one as LOC
System Action:
The second RESOURCE statement is ignored.
Action:
Correct RESOURCE statement and re-issue the request.
700 - 799
709E
Unable to initialize WTO broadcast
Reason:
An attempt during CA WA ESP Edition subsystem initialization to request broadcasting
to the subsystem failed. Events that depend on intercepting WTO messages cannot be
tracked. For example, jobs terminated due to a JCL error.
System Action:
CA WA ESP Edition initialization continues.
Action:
Should never occur. If it does, and it causes problems, contact CA Support.
710S
ASCRE for auxiliary failed, return code n, reason code m
Reason:
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.
Action:
Probable system error. Investigate the reason for the ASCRE error and contact your
711W
SUBMISSION ABANDONED FOR JOB xxxx IN APPL yyyy
Reason:
The abandon submission time for the job has passed, so an appropriate message is
logged, and submission is abandoned.
System Action:
The job is not submitted.
Action:
None
700 - 799
712W
JOB xxxx.qqqq IN APPL aaaa.nn, LATE END TIME EXCEEDED
Reason:
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. This message is displayed as a result of having
NOTIFY OVERDUE statement associated with this job.
System Action:
The job is considered overdue.
Action:
The job's performance group or priority should be raised if this is a critical job.
713W
MANUAL JOB xxxx.qqqq IN APPL aaaa.nn, LATE END TIME EXCEEDED
Reason:
A MANUAL job has missed its late end time. The late end time was defined by the user
defining the job to the system. This message is displayed as a result of having NOTIFY
OVERDUE statement associated with this job.
System Action:
Action:
714W
Reason:
A job has missed its late end time. The late end time was specified in the definition of
the job. This message is displayed as a result of having NOTIFY OVERDUE statement
associated with this job.
System Action:
Action:
700 - 799
715W
JOB xxxx.qqqq IN APPL aaaa.nn, LATE SUBMIT TIME EXCEEDED
Reason:
A job has missed its late submit time. The late submit time was specified in the
definition of the job. This message is displayed as a result of having NOTIFY OVERDUE
statement associated with this job.
System Action:
Action:
You should display the application to find out what the job is waiting on.
716W
Job xxxx in Appl zzzz Late Start Time exceeded
Reason:
A job has missed its late start time. The late start time was defined by the user defining
the job to the system. This message is displayed as a result of having NOTIFY OVERDUE
statement associated with this job.
System Action:
Action:
You should investigate why JES has not started the job yet.
717E
INVALID RESOURCE QUANTITY xxxxx
Reason:
The quantity specified on a RESOURCE statement contains non-numeric characters.
System Action:
Action:
Correct the error
700 - 799
718E
Application name <applname> invalid
Reason:
Response to NOTWITH application command in a procedure. An invalid application
name <applname> was specified.
System Action:
The entire event is suppressed.
Action:
Correct the application name specification in the NOTWITH application command.
719E
TO MANY REPORTS, MAXIMUM 32 ALLOWED
Reason:
More than 32 MREPORT statements are specified for modeling.
System Action:
Modeling terminates immediately.
Action:
MREPORT statements should be grouped by 32 or less and processed separately.
720W
UNABLE TO ALLOCATE xxxx, S99 ERROR CODE X'yyyy', INFO CODE X'zzzz'
Reason:
An error occurred during a dynamic allocation request.
System Action:
This message is followed by another message indicating the action taken.
Action:
Take note of the following message.
700 - 799
721W
UNABLE TO ALLOCATE xxxx, VOLUME OFFLINE
Reason:
An error occurred during a dynamic allocation request due to a required volume being
offline.
System Action:
Action:
Take note of the succeeding message.
722W
DATASET xxxx NOT CATALOGUED
Reason:
An error occurred during a dynamic allocation request due to a data set not being
catalogued.
System Action:
Action:
723W
UNABLE TO GET EXCLUSIVE ALLOCATION TO DATASET xxxx
Reason:
A data set that is needed exclusively was already allocated to another user.
System Action:
Action:
700 - 799
724W
UNABLE TO GET SHARED ALLOCATION TO DATASET xxxx
Reason:
A data set that is needed for shared access is allocated exclusively to another user.
System Action:
Action:
725W
DATASET xxxx NOT ON {CATALOGUED VOLUME | VOLUME yyyy}
Reason:
A data set was not found on the volume as catalogued or explicitly specified.
System Action:
Action:
726E
PREDECESSOR/SUCCESSOR keywords are valid only for JR1 report - ignored
Reason:
In the MREPORT statement, keywords PREDECESSOR or SUCCESSOR are only applicable
to the JR1 report. For other reports the above warning is issued.
System Action:
Modeling ignores these keywords and continues processing.
Action:
Delete PREDECESSOR/SUCCESSOR keywords
700 - 799
727W
UNABLE TO FREE xxxx, S99 ERROR CODE X'yyyy', INFO CODE X'zzzz'
Reason:
An error occurred while performing a dynamic unallocation.
System Action:
Action:
728E
UNABLE TO PERFORM TASK SWITCH
Reason:
The product tried to switch to a subtask to perform an allocation request. The task
switch failed.
System Action:
Action:
729E
UNABLE TO REVERT TO MAIN TASK
Reason:
After an allocation was performed on a subtask, the routine was unable to rejoin the
main task.
System Action:
Action:
700 - 799
730C
MGRADDR DISPLAY
Reason:
Response to MGRADDR, MGRADDR DISPLAY or MGRADDR LIST command. The manager
address, home IP address and EspCom client TCP bind status, specified by the MANAGER
command in the AGENTDEF file, are displayed. If the MANAGER command specifies
TCPIP(xxxx), then xxxx is the manager address and the corresponding IP address is the
home IP address. If the MANAGER command specifies TCPIP, then the manager and
home IP address are the system default home IP address. If the MANAGER command
specifies BIND, then the EspCom client TCP bind status is "Bind", else it is "No Bind".
System Action:
Action:
None.
731I
STARTING BACKUP OF HISTFILE xxxx
Reason:
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.
Action:
None
700 - 799
732I
Manager address xxxx{:yyyy} notify scheduled to zzzz agent{s}
Reason:
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.
System Action:
Action:
None.
733I
HISTFILE BACKUP ENDED FOR xxxx, nn RECORDS BACKED UP
Reason:
A BACKUP or SCAN of an History data set has completed.
System Action:
Action:
None.
734S
DATASET NOW SUSPENDED
Reason:
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.
Action:
Once the problem with the History data set is corrected, the data set can be reactivated
through the HISTFILE OPEN command.
700 - 799
735E
ERROR OPENING BACKUP DATASET xxxx
Reason:
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.
Action:
The message will describe the error condition. After the problem is diagnosed and
corrected, the BKUPEVS command should be issued to take a backup.
736E
ERROR WRITING TO BACKUP xxxx
Reason:
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 performed, it will
continue.
Action:
737E
ERROR CLOSING BACKUP DATASET, xxxx
Reason:
An error occurred while closing the backup data set for a History file.
System Action:
Action:
700 - 799
738W
RESOURCE <resource_name> NOT AVAILABLE FOR DELETE, AVAIL=<qty_avail>,
DEL=<qty_del>
Reason:
During the processing of the request for resource deletion:
RESOURCE <resource_name> <qty_del> DEL ...
modeling system discovered that the requested amount of resource to delete exceeded
the available amount. Message shows resource name <resource_name>, requested
amount of resource to delete <qty_del>, and available amount of resource <qty_avail>.
System Action:
Modeling system sets the amount of <resource_name> resource to 0 and continue
processing.
Action:
Correct RESOURCE statement and repeat modeling run.
739E
HISTFILE xxxx BACKUP BYPASSED DUE TO SUSPENDED STATE
Reason:
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.
Action:
When the problem with the data set is corrected, reopen the data set with the HISTFILE
command.
700 - 799
740I
STARTING BACKUP OF JOB INDEX
Reason:
A backup of the Job Index data set has begun.
System Action:
The Job Index data set is backed up.
Action:
None.
741I
PNODE changed to zzzz for Job xxxx in Appl yyyy
Reason:
This message is issued on the request of a NOTIFY statement in a Procedure. The
message text indicates that the PNODE of a job has been changed. The message text can
also include the application name or jobnet ID.
System Action:
Action:
None.
742E
BACKUP OF JOB INDEX DATASET ENDED WITH ERRORS
Reason:
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.
Action:
Notify your system support personnel. The backup can be performed again after the
problem has been corrected.
700 - 799
743I
JOB INDEX DATASET BACKUP ENDED, nn RECORDS BACKED UP
Reason:
A backup of the Job Index data set has completed successfully.
System Action:
Action:
None.
744E
ERROR CLOSING JOB INDEX BACKUP DATASET, xxxx
Reason:
An error occurred while closing the backup data set. The backup may not be usable.
System Action:
Action:
The message text more fully describes the error. If the error is correctable, the backup
can be may be executed again.
745E
ERROR OPENING JOB INDEX BACKUP DATASET xxxx
Reason:
An error occurred while opening a backup data set for the Job Index data set.
System Action:
The backup is not performed.
Action:
Notify your system support personnel. Once the problem is resolved, the backup should
be executed again.
700 - 799
746E
ERROR WRITING TO JOB INDEX BACKUP xxxx
Reason:
An error occurred while writing to the backup data set for the Job Index data set.
System Action:
The backup is not completed.
Action:
be executed again.
747E
JOB INDEX DATASET BACKUP TIME WILL HAVE TO BE RESET
Reason:
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.
Action:
Use the BKUPJNDX command to set the scheduled backup time.
748E
NO BACKUP DATASET SPECIFIED FOR JOB INDEX DATASET
Reason:
The product attempted to take a backup of the Job Index data set. A backup data set
was not specified in the initialization parameters.
System Action:
Action:
The backup data set should be placed in the ESPPARM data set and the product
restarted.
700 - 799
749W
FTP SMF119 not available on OS/390. SMF118 used.
Reason:
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 product will listen for SMF 118 records.
System Action:
The default SMF 118 records will be "listened to"
Action:
No action is required. To avoid seeing this message in the future, please correct the
initialization parameter.
750W
DATASET xxxx WAS IN THE SUSPENDED STATE
Reason:
During a warm start, the product found a data set that was previously in the suspended
state.
System Action:
The data set remains suspended.
Action:
In order to activate the data set, use the EVENTSET or HISTFILE command with the OPEN
keyword.
700 - 799
751S
DATASET xxxx NOW PLACED IN SUSPENDED STATE
Reason:
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.
Action:
When the error has been corrected, use the EVENTSET OPEN command to reactivate
use of the data set.
752W
EVENT DATASET xxxx EMPTY, WILL FORMAT
Reason:
An uninitialized Event data set was opened.
System Action:
The data set will be formatted.
Action:
None.
753W
EVENT DATASET xxxx HAS INCORRECT KEYLENGTH
Reason:
An Event data set was defined with the wrong key length. See the installation reference
manual for the correct key length.
System Action:
The data set is suspended.
Action:
The Event data set should be redefined or modified through the ALTER command of the
IDCAMS utility.
700 - 799
754W
EVENT DATASET xxxx HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED
Reason:
The specified event data set had no valid control record.
System Action:
A control record will be added.
Action:
None
755E
ENDDO immediately preceded by THEN or ELSE
Reason:
ENDDO immediately preceded by THEN or ELSE in the same statement
System Action:
Action:
756S
DATASET xxxx NOW PLACED IN SUSPENDED STATE
Reason:
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.
Action:
When the error has been corrected, use the HISTFILE OPEN command to reactivate use
of the data set.
700 - 799
757W
HISTORY DATASET xxxx EMPTY, WILL FORMAT
Reason:
An uninitialized history data set was opened.
System Action:
The data set will be formatted.
Action:
None.
758W
HISTORY DATASET xxxx HAS INCORRECT KEYLENGTH
Reason:
A history data set was defined with the wrong key length. See the installation reference
manual for the correct key length.
System Action:
The data set is suspended.
Action:
The history data set should be redefined or modified through the ALTER command of
the IDCAMS utility.
759W
HISTFILE xxxx HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED
Reason:
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.
Action:
None
700 - 799
760A
SYSTEM CLOCK(S) INOPERATIVE, REPLY WHEN OPERATIONAL AGAIN OR CANCEL ESP
Reason:
The product found the system clocks to be inoperative.
System Action:
Action:
Reply to this message when the clocks are operational again. If the system needs to be
brought down, you can cancel the product.
761W
EVENT DATASET xxxx DOWNLEVEL, USE CONVERT UTILITY
Reason:
An event data set was found to be created by an incompatible release of the product.
System Action:
The Event data set is put in the suspended state.
Action:
Use the CONVERT command of the utility processor.
762E
xxxx incompatible with yyyy
Reason:
The product encountered a DSTRIG event command that specifies at least two
incompatible operands xxxx and yyyy.
System Action:
Action:
Correct the DSTRIG event command so that it does not specify any incompatible
operands. Then re-trigger the event.
700 - 799
763E
xxxx incompatible with yyyy
Reason:
object that specifies at least two incompatible operands xxxx and yyyy.
System Action:
The application is not built.
Action:
Correct the DSNAME application statement so that it does not specify any incompatible
operands. Then re-trigger the event that invokes the application.
764E
FTP trigger host name look up failed for {event uuuu.eeee|application aaaa.gggg}
Reason:
The product encountered an FTP data set trigger definition that specified a TCP/IP host
name (using 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 application name.
eeee - specifies an event name.
gggg - specifies an application generation number. uuuu specifies an event userid.
System Action:
The data set trigger is ignored.
Action:
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.
700 - 799
765E
EDTINFO RtnUnit, DevType=xxxx, RtnCode=yy, RsnCode=zz
Reason:
In order to set the %ESPTRUNIT symbolic variable the product 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 issued to obtain
the unit name.
System Action:
The %ESPTRUNIT symbolic variable is set to value *UNKNOWN.
Action:
Should not happen. If the problem persists call CA Support.
766I
{FTP SMF number {set to [assign the value for SMF in your book]|not set}{, } {FTP user
(TCPaccess) SMF number set to <usersmf>}
Reason:
Response to FTP command. Indicates which FTP SMF records the product is listening on
for FTP triggers.
[assign the value for SMF in your book] specifies an IBM Communication Server FTP SMF
number. It can be either 118 or 119.
<usersmf> specifies a CA-TCPaccess FTP SMF number. It can be within the range
128-255, and is usually 130.
System Action:
If the FTP command specified no operands, no action is taken. If the FTP command
specified SMF([assign the value for SMF in your book]), the FTP trigger SMF number is
set to [assign the value for SMF in your book] (118 or 119). If the FTP command
specified USER(<usersmf>), the FTP trigger user (CA-TCPaccess) SMF number is set to
<usersmf> (128-255).
Action:
None.
700 - 799
767A
PAUSE now in effect, Reply 'GO' to resume
Reason:
As a result of the operator's request, the product has temporarily halted processing.
This instance of the product has control of the shared data sets, including the queue file.
System Action:
The product waits for the operator to reply 'GO' to the WTOR.
Action:
When ready to proceed, reply 'GO' to the WTOR.
768I
PAUSE completed, processing resuming
Reason:
A reply of 'GO' has been received, and the product has resumed normal processing.
System Action:
None.
Action:
None.
769I
PAUSE request must be issued from a console
Reason:
A pause command was issued from a source other than an MVS MODIFY command.
System Action:
The system ignores the command.
Action:
None.
700 - 799
770W
NO BACKUP DEFINED FOR EVENTSET xxxx
Reason:
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.
Action:
Ensure that the EVENTSET has an associated backup data set before issuing the
BKUPEVS command.
771I
STARTING BACKUP/SCAN OF EVENTSET xxxx
Reason:
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.
Action:
None
700 - 799
0772E
No submit library for XXXXXXXX.XXXXXXXX job
Reason:
During application processing or simulation WLM detected that there is no submit
library for a job in the application.
System Action:
CSF will show a submit error for this job. Simulation will continue, though this job will
not be written to output file if it is specified in simulation parameters.
Action:
Users can specify a submit library in JCLLIB/TEMPLIB statements or in DATASET
statement for this individual job only.
773I
EVENTSET SCAN/BACKUP ENDED FOR xxxx, nn RECORDS BACKED UP
Reason:
A BACKUP or SCAN of an Event data set has completed.
System Action:
Action:
None.
774S
DATASET NOW SUSPENDED
Reason:
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.
Action:
Once the problem with the Event data set is corrected, the data set can be reactivated
through the EVENTSET OPEN command.
700 - 799
775E
Reason:
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.
Action:
776E
Reason:
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.
Action:
777E
Reason:
An error occurred while closing the backup data set for an Event file.
System Action:
Action:
700 - 799
778E
NO MORE SPACE IN CHECKPOINT FOR A SUBMISSION REQUEST ELEMENT
Reason:
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.
Action:
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.
779E
EVENTSET xxxx BACKUP/SCAN BYPASSED DUE TO SUSPENDED STATE
Reason:
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.
Action:
When the problem with the data set is corrected, reopen the data set with the
EVENTSET command.
780I
STARTING BACKUP OF USERDEF
Reason:
A backup of the user definition data set has begun.
System Action:
The userdef data set is backed up.
Action:
None.
700 - 799
781E
Attempt made to undelete occupied slot aaa in bbb
Reason:
An attempt was made to reacquire slot number aaa that was freed in slotted file bbb. If
the slot is occupied, it has been reassigned to a different record and is no longer
available.
System Action:
Action:
None.
782E
BACKUP OF USERDEF ENDED WITH ERRORS
Reason:
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:
Action:
Notify your system support personnel. The backup can be done again after the problem
has been corrected.
783I
USERDEF BACKUP ENDED, nn RECORDS BACKED UP
Reason:
A backup of the user definition data set has completed successfully.
System Action:
Action:
None.
700 - 799
784E
Reason:
An error occurred whilst closing the backup data set. The backup may not be usable.
System Action:
Action:
can be taken again.
785E
Reason:
An error occurred while opening a backup data set for the user definition data set.
System Action:
Action:
be retaken.
786E
Reason:
An error occurred while writing to the backup data set for the user definition data set.
System Action:
Action:
be retaken.
700 - 799
787E
USERDEF BACKUP TIME WILL HAVE TO BE RESET
Reason:
message would have been preceded by a message describing the error.
System Action:
Action:
Use the BKUPUSER command to set the scheduled backup time.
788E
NO BACKUP DATASET SPECIFIED FOR USERDEF
Reason:
The product attempted to take a backup of the USERDEF data set. However, a backup
data set was not specified in the initialization parameters.
System Action:
Action:
restarted.
789I
No candidates for adhoc jobs found
Reason:
A user tried to insert adhoc job(s) into an application, but the product detected that
there is no not-selected jobs in the invoked procedure(s).
System Action:
Reject the command.
Action:
None.
700 - 799
790I
STARTING BACKUP OF INDEX
Reason:
A backup of the user definition data set has begun.
System Action:
The userdef data set is backed up.
Action:
None.
791W
Job XXXXXXXX not found in ESP procedure
Reason:
A user issued command to insert adhoc job(s) into an application, but specified job
XXXXXXXX was not defined in associated procedure(s).
System Action:
The product proceeds with the jobs that are found in associated procedure(s).
Action:
Correct the jobname and re-issue the command.
792E
BACKUP OF INDEX DATASET ENDED WITH ERRORS
Reason:
A previous error has caused termination of the Index data set backup. This message is
preceded by another message describing the error.
System Action:
Action:
700 - 799
793I
INDEX DATASET BACKUP ENDED, nn RECORDS BACKED UP
Reason:
A backup of the Index data set has completed successfully.
System Action:
Action:
None.
794E
ERROR CLOSING INDEX BACKUP DATASET, xxxx
Reason:
System Action:
Action:
can be performed again.
795E
ERROR OPENING INDEX BACKUP DATASET xxxx
Reason:
An error occurred while opening a backup data set for the Index data set.
System Action:
Action:
be performed again.
700 - 799
796E
ERROR WRITING TO INDEX BACKUP xxxx
Reason:
An error occurred while writing to the backup data set for the Index data set.
System Action:
Action:
be performed again.
797E
INDEX DATASET BACKUP TIME WILL HAVE TO BE RESET
Reason:
System Action:
Action:
Use the BKUPUSER command to set the scheduled backup time.
798E
NO BACKUP DATASET SPECIFIED FOR INDEX DATASET
Reason:
The product attempted to take a backup of the Index data set. A backup data set was
not specified in the initialization parameters.
System Action:
Action:
restarted.
800 - 899
799W
Joining XCF Group failed, use command TRYJOIN later
Reason:
The sub-system could not join XCF group, because of a reason explained in the previous
messages. The user need to issue command 'TRYJOIN' to join the XCF group.
System Action:
Processing continues without XCF services.
Action:
Issue operator command 'TRYJOIN' to join XCF group if the system needs XCF services.
800 - 899
800W
PARAMETER ERROR ON EXEC CARD
Reason:
An invalid initialization option was specified on the EXEC card parameter of the
procedure.
System Action:
The product continues with message 803.
Action:
Reply to the prompt that follows.
801W
PARAMETER ERROR ON START COMMAND
Reason:
An invalid initialization option was specified on the START command for the product.
System Action:
Processing continues with message 803.
Action:
Reply to the prompt that follows.
800 - 899
802A
REENTER ENTIRE STATEMENT, 'CANCEL' OR 'END'
Reason:
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:
The product waits for a response. If CANCEL is specified, the product terminates. If END
is specified, the product ignores the parameter statement, EXEC or START option in
error.
Action:
Reenter the correct parameters. If you are not sure what they are supposed to be, reply
CANCEL, and the product will terminate. The product can then be restarted when the
correct parameters are found.
803W
xxxx
Reason:
The product is displaying the initialization option on the EXEC card or START command,
or the parameter statement which had an error.
System Action:
Action:
Reply to the message that follows.
800 - 899
804W
PARAMETER ERROR ON FOLLOWING STATEMENT FROM xxxx FILE
Reason:
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:
Action:
Reply to the message 802 prompt that follows.
805W
FOLLOWING STATEMENT FROM xxxx HAS AN INVALID SYNTAX
Reason:
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.
System Action:
Action:
806W
FOLLOWING STATEMENT FROM xxxx HAS AN UNDEFINED PARAMETER
Reason:
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.
System Action:
Action:
800 - 899
807E
xxxx
Reason:
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.
Action:
Correct the problem and restart the product.
808W
CHECKPOINT DATA SET xxxx IS CORRECTLY FORMATTED
Reason:
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. The product is confirming
that a cold start is really required, and not inadvertently specified.
System Action:
The product follows by issuing message 809.
Action:
809A
CONFIRM REQUEST FOR COLD START, ENTER 'Y' OR 'N'
Reason:
The product is requesting confirmation that a cold start is really required.
System Action:
The product waits for the reply. If a Y is entered, the product proceeds with a cold start.
If the reply is N, the product proceeds with a warm start.
Action:
If you wish to proceed with the cold start, enter Y. Otherwise enter N and the product
will attempt a warm start.
800 - 899
810I
WARM START WILL BE ATTEMPTED
Reason:
The product is attempting a warm start after the operator entered a reply of N to the
message 809A.
System Action:
A warm start is attempted.
Action:
None.
812W
INVALID CHECKPOINT FORMAT ON xxxx
Reason:
A warm start was requested. However, the checkpoint data set does not have a valid
format.
System Action:
This messages followed by message 813.
Action:
If you wish to proceed with the cold start, enter Y. Otherwise enter N and the product
will terminate.
813A
ENTER 'Y' TO PROCEED WITH COLD START OR REPLY 'N'
Reason:
This message requests confirmation that you wish to proceed with a cold start.
System Action:
The product waits for your response. If you answer Y, the cold start is performed.
Otherwise, a warm start is attempted.
Action:
Enter Y if you wish to proceed with a cold start.
800 - 899
814E
xxxx
Reason:
An error occurred processing a checkpoint data set. The text of the message fully
describes the problem.
System Action:
Action:
Respond to message 0817S.
815W
INVALID RESPONSE
Reason:
System Action:
Action:
Respond to the prompt.
816W
CHECKPOINT xxxx LAST USED BY SYSTEM yyyy AT zzzz ON aaaabbbbcccc
Reason:
A cold-start or warm-start was being performed and the product 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:
Action:
Respond to message 813A. You will not be able to perform a warm start unless the
system ID matches that in the checkpoint.
800 - 899
817S
CHECKPOINT UNUSABLE
Reason:
This message follows another message describing an error on the checkpoint data set.
System Action:
Action:
The previous message described an error condition. After the problem is corrected, the
818S
NO CHECKPOINT DATA SET SPECIFIED IN ESPPARM
Reason:
No checkpoint data set was defined in the ESPPARM file.
System Action:
Action:
Enter the CKPT parameter in the ESPPARM file and restart the product.
820S
CHECKPOINT DATA SET NOT DEFINED
Reason:
A checkpoint data set was not specified on a startup.
System Action:
Action:
Define a checkpoint data set by use of the CKPT parameter in the ESPPARM file.
800 - 899
821S
USER DEFINITION DATA SET NOT DEFINED
Reason:
The user definition data set (USERDEF) was not defined in the ESPPARM data set. The
data set is required for the product to operate.
System Action:
Action:
Enter a USERDEF statement in the ESPPARM file to define the user definition data set.
Then restart the product.
823W
CHECKPOINT DATA SET IS DOWNLEVEL, COLD START REQUIRED
Reason:
A WARM start was attempted when bringing up a new release of the product. The new
release uses a checkpoint of different format, and therefore a cold start is required.
System Action:
Action:
824S
USER DEFINITION DATA SET xxxx UNUSABLE
Reason:
An error, described by a preceding message, has caused the user definition data set to
be unusable.
System Action:
Action:
The preceding message documents the error. After the error is corrected, the product
can be restarted.
800 - 899
825E
Job statistics data set needed for a Master
Reason:
The sub-system is set to be a Master system, while the JOBSTATS is not specified in the
System Action:
Action:
Specify JOBSTATS initialization parameter.
826E
INCORRECT KEY LENGTH SPECIFIED FOR USER DEFINITION DATASET
Reason:
The ESPPARM data set specified a User Definition data set which had an incorrect key
length.
System Action:
Action:
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.
827I
USER DEFINITION DATA SET EMPTY, WILL FORMAT
Reason:
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.
Action:
None, unless the User Definition data set is not supposed to be empty.
800 - 899
828E
INVALID JOURNAL SMF RECORD NUMBER SPECIFIED
Reason:
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.
Action:
Respond to the message that follows. If you are unsure of the correct number, notify
your software support staff.
829E
INVALID MINDORM VALUE nn
Reason:
The MINDORM value cannot be less than 10 nor greater than 100,000.
System Action:
The value is not changed.
Action:
Correct the MINDORM value.
831E
INVALID SVC NUMBER SPECIFIED
Reason:
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.
Action:
800 - 899
832E
ERROR OCCURRED DURING COMMAND PARAMETER SCAN
Reason:
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:
Action:
833E
INVALID MAXDORM VALUE nn
Reason:
The MAXDORM value cannot be less than 100 nor greater than 100,000.
System Action:
Action:
Correct the MAXDORM value.
834E
INVALID MINHOLD VALUE nn
Reason:
The MINHOLD value cannot be less than 10 nor greater than 100,000.
System Action:
Action:
Correct the MINHOLD value.
800 - 899
835I
USER DEFINITION DATA SET HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED
Reason:
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.
Action:
None.
836E
APPLJOB LIST specified with incompatible operand(s)
Reason:
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.
Action:
If required, re-issue the APPLJOB or AJ command with compatible operands.
837C
APPLJOB LIST
Reason:
An APPLJOB or AJ LIST command.
System Action:
The status of the specified job in the specified application is displayed.
Action:
None.
800 - 899
838?
ENTER INITIALIZATION PARAMETER OR 'END'
Reason:
In response to the PROMPT keyword on the start command, the product is prompting
the operator to enter an initialization parameter from the console.
System Action:
The product waits for a response, then processes the parameter.
Action:
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.
839E
INVALID MAXLRECL VALUE nn, VALID RANGE 4000-32760
Reason:
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.
Action:
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 database.
800 - 899
840S
UNABLE TO INITIALIZE SUBSYSTEM
Reason:
An error occurred while trying to build the subsystem interface. This is probably an
System Action:
Action:
841S
ERROR WRITING CHECKPOINT
Reason:
The product encountered an error while writing to the checkpoint.
System Action:
Action:
Investigate and correct the problem. Then restart the product.
842S
CANNOT PURGE START WITH AUXILIARY ACTIVE
Reason:
An attempt has been made to PURGE start the product. However, the auxiliary address
space is currently operational.
System Action:
Action:
You must either start the product without the PURGE option, or else terminate the
auxiliary address space prior to performing the PURGE start.
800 - 899
843S
INSUFFICIENT CSA TO ENABLE DATA SET TRIGGERING
Reason:
The product 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.
Action:
The product can be stopped and restarted when the CSA shortage is relieved.
844W
USERMOD 65 set, user SVC <nnn> overlaid
Reason:
A CA WA ESP Edition subsystem, initializing for the first time since IPL, determined that
user SVC <nnn>, specified in the ESPPARM initialization file SVC command, was already
installed as another software product's user SVC.
System Action:
Because USERMOD 65 was set in the ESPPARM initialization file, the SVC table entry for
SVC <nnn> was overlaid by the CA WA ESP Edition user SVC.
Action:
If USERMOD 65 was correctly set, and the previously installed user SVC <nnn> was
determined to not actually be used by any other software product, then no response is
required. Caution: USERMOD 65 should only be set in the ESPPARM initialization file if it
is important to use the specified SVC number and there is certainty that the previously
installed conflicting user SVC is not actually used by any other software product. If
USERMOD 65 was incorrectly set and the previously installed user SVC is being used by
another software product, then a system integrity problem is likely to occur. If this is the
case, then - Remove the USERMOD SET(65) command in the ESPPARM initialization file.
Specify an available user SVC number <nnn> in the ESPPARM initialization file SVC
command. Restart the CA WA ESP Edition subsystem. The available user SVC numbers
can be determined by listing all user SVCs with the following command in page or line
mode - DSVC START(200) or DSVC S(200) Any SVC that is specified as "Undefined" is
available, assuming no other software product dynamically updates it after the CA WA
ESP Edition subsystem initializes for the first time since IPL. Note: The DSVC command
works regardless of whether or not the target CA WA ESP Edition subsystem is active.
800 - 899
845W
Insufficient CSA storage for tracking cell
Reason:
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.
Action:
Provide additional CSA by terminating unnecessary tasks using CSA or increase CSA size.
846W
INSUFFICIENT CSA FOR DATASET TRIGGER DESCRIPTOR
Reason:
The product 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.
Action:
The product can be stopped and restarted once the CSA shortage is relieved.
847W
INSUFFICIENT CSA STORAGE FOR TRIGGER EXCLUSION ENTRY xxxx
Reason:
The product 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.
Action:
The product can be stopped and restarted once the CSA shortage is relieved.
800 - 899
848S
ERROR ATTACHING COMMAND TASK, RC=nn
Reason:
An error occurred while attempting to attach the command processor task.
System Action:
Action:
Notify your software support personnel. This is normally caused by a lack of virtual
storage. Increase the region size and restart the product.
849S
ERROR OCCURRED READING QUEUE DATA SET
Reason:
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:
Action:
Notify your software support personnel. The preceding message will have described the
error. Restart the product when the problem is corrected.
850S
ESP IS ALREADY ACTIVE FOR SYSTEM ID xxxx
Reason:
The product was started while another copy of the program was executing with the
same system ID.
System Action:
Action:
This is a probably due to an operator error, when more than one task is started.
800 - 899
851E
UNABLE TO LOAD ACF2 MUSASS INITIALIZATION EXIT
Reason:
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.
Action:
Respond to the prompt message that follows. Notify your software support personnel.
852E
JOB INDEX AND TRACKFILE BOTH NEEDED FOR TRACKING OPTION
Reason:
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:
Action:
Update the initialization parameter data set to define both data sets. Restart the
product.
853E
QUEUE DATA SET NEEDED FOR TRACKING OPTION
Reason:
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:
Action:
The queue data set should be defined by adding the QUEUE parameter to the
initialization parameter data set.
800 - 899
854E
xxxx
Reason:
An error occurred while performing I/O to or opening the track file. The message text
describes the error.
System Action:
Action:
Take action based on message 0855S.
855S
TRACK FILE DATASET xxxx UNUSABLE
Reason:
An error, described by a preceding message, has prevented the product from using the
job tracking file.
System Action:
Action:
Notify your software support personnel. After the error has been corrected, the product
can be restarted.
856E
TRACK FILE DATASET IS TOO SMALL
Reason:
The job tracking file was found to be too small. A minimum number of slots are required
for normal processing.
System Action:
Action:
Notify your software support personnel. The data set should be reallocated with
sufficient room for processing. The product can then be restarted. See the Installation
Guide for further information.
800 - 899
857S
STARTUP TERMINATED BY INSTALLATION ACF2 EXIT
Reason:
The installation ACF2 interface initialization exit encountered an error and requested
shutdown.
System Action:
Action:
858E
DUPLICATE JOB NAME WHEN USERMOD 25 ENABLED: xxxxxxxx
Reason:
More than one job card with the same job name has been found in a JCL member when
Usermod 25 is enabled
System Action:
Only the first job is submitted
Action:
Correct the error
860S
INDEX DATA SET xxxx UNUSABLE
Reason:
An error, described by a preceding message, has prevented the product from accessing
the index data set.
System Action:
Action:
can be restarted.
800 - 899
861E
INCORRECT KEY LENGTH SPECIFIED FOR INDEX DATA SET
Reason:
The ESPPARM data set specified an index data set data set which had an incorrect key
length.
System Action:
Action:
862I
INDEX DATA SET HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED
Reason:
The index data set contained no control record. A control record is always the first
record in the data set.
System Action:
Action:
None.
863I
INDEX DATA SET EMPTY, WILL FORMAT
Reason:
An empty index data set was detected. This is expected the first time the data set is
used.
System Action:
The product formats the data set and continues processing.
Action:
None, unless the index data set is not supposed to empty.
800 - 899
864S
INDEX DATA SET DOWNLEVEL, USE CONVERT UTILITY
Reason:
The index data set was found to be created by an incompatible release of the product.
System Action:
The data set cannot be used, and so processing terminates.
Action:
Use the convert subcommand of the UTIL processor of the ESP TSO command, then
restart the subsystem.
865I
Data set trigger cell count <count>, expansion limit <limit>
Reason:
DSTRIG operator command response.
System Action:
The data set trigger cell count is set to value <count> and the data set trigger sell
expansion is set to <limit>.
Action:
None.
866E
INVALID DSTRIG CELL COUNT nn{ 10 USED}
Reason:
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.
Action:
800 - 899
867S
INDEX DATA SET NOT DEFINED
Reason:
No INDEX statement was found in the ESPPARM data set. The product does not know
the index data set name.
System Action:
Action:
Notify your software support personnel. The INDEX statement should be inserted into
the ESPPARM file to describe the name and other characteristics if the index data set.
868E
INVALID DSTRIG EXPANSION LIMIT nn{ 50 USED}
Reason:
A DSTRIG parameter with a cell expansion limit outside of the range 0-1000 was
specified.
System Action:
The default of 50 is used.
Action:
Notify your software support personnel, who will then correct the initialization
parameters.
869E
TCELL type specification missing
Reason:
A TCELL command did not specify the JOBSTART, STEPEND or JOBEND keyword operand.
System Action:
The operator is prompted to re-enter the command.
Action:
Respond to the message that follows and correct the erroneous TCELL command in the
ESPPARM initialization file.
800 - 899
870E
TCELL initial count nnn invalid
Reason:
A TCELL command with an initial count nnn outside the range 0-100 was specified.
System Action:
Action:
871E
TCELL expansion limit nnn invalid
Reason:
A TCELL command with an expansion count nnn outside the range 0-5000 was specified.
System Action:
Action:
872E
INVALID DAY OF WEEK NAME xxxx
Reason:
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 may be abbreviated down to the first 3
characters.
System Action:
Action:
Enter a valid day, or list of days.
800 - 899
873E
Reason:
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:
Action:
0874S
ERROR PROCESSING CHECKPOINT DATA SET, RC=XX, CKTERCOD=XX,
CKTSYNAD=XXXXXXXX
Reason:
The checkpoint data set had an invalid format or a permanent I/O error occurred
reading the data set.
RC - Return code from checkpoint processing routine.
CKTERCOD - Original error code.
CKTSYNAD - Address of error routine, if any. If CKTSYNAD = 0, then RC is the same as
CKTERCOD
System Action:
The scheduled activity report generation process is terminated.
Action:
Ensure a valid checkpoint data set name is specified in the ESP parameter file.
800 - 899
875E
INVALID APPLBUF VALUE nnnn, VALID RANGE 16376-4177912
Reason:
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).
Action:
Supply a correct value to the prompt message that follows.
876E
Error reading/writing TRAKFILE while tracking RESET jjj command
Reason:
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.
Action:
877E
{IfHolidayPlus|IfHolidayLess} cannot be combined with another Plus|Less opt
Reason:
IfHolidayPlus and IfHolidayLess cannot be combined with any of the following terms:
Plus, Less, IfHolidayPlus and IfHolidayLess.
System Action:
Action:
Respecify the schedule statement.
800 - 899
878E
Workday or Weekday are invalid with {IfHolidayPlus|IfHolidayLess}
Reason:
WORKDAY or WEEKDAY cannot be used as the amount unit of IfHolidayPlus or
IfHolidayLess.
System Action:
Action:
Respecify the schedule statement.
879S
SVC <nnn> specification conflicts with existing SVC
Reason:
A CA Workload Automation EE subsystem, initializing the first time since IPL,
determined that user SVC <nnn>, specified in the ESPPARM initialization file SVC
command, was already installed as another software product's user SVC.
System Action:
The CA Workload Automation EE subsystem terminates.
Action:
In the ESPPARM initialization file SVC command, specify a user SVC number <nnn> that
does not conflict with another product's user SVC. Then restart the CA Workload
Automation EE subsystem. The available user SVC numbers can be determined by listing
all user SVCs with the following command in page or line mode - DSVC START(200) or
DSVC S(200) Any SVC that is specified as "Undefined" is available, assuming no other
software product dynamically updates it after the CA Workload Automation EE
subsystem initializes for the first time since IPL. Note: The DSVC command works
regardless of whether or not the target CA Workload Automation EE subsystem is
active.
800 - 899
880S
JOB INDEX DATASET xxxx UNUSABLE
Reason:
the job index data set.
System Action:
Action:
can be restarted.
881E
INCORRECT KEY LENGTH SPECIFIED FOR JOB INDEX DATASET
Reason:
The ESPPARM data set specified a job index data set which had an incorrect key length.
System Action:
Action:
882I
JOB INDEX DATASET HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED
Reason:
The job index data set contained no control record. A control record is always the first
System Action:
Action:
None.
800 - 899
883I
JOB INDEX DATASET EMPTY, WILL FORMAT
Reason:
An empty job index data set was detected. This is expected the first time the data set is
used.
System Action:
Action:
None, unless the job index data set is not supposed to empty.
885W
TRACK FILE xxxx UNFORMATTED
Reason:
The Job Tracking file was found to be unformatted. This is expected the first time the
data set is used.
System Action:
The product follows with message 886.
Action:
886A
REPLY 'Y' TO FORMAT THE TRACK FILE, OR REPLY 'N'
Reason:
The Job Tracking file was found to be unformatted. Before proceeding to format it, the
product requests permission from the operator.
System Action:
The product waits for the reply.
Action:
If you wish the tracking file to be formatted, reply Y, otherwise reply N and the product
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.
800 - 899
887E
CORRECT THE ABOVE PROBLEM AND RESTART ESP
Reason:
This message is issued after an error has occurred that prevents to further execution of
the product. This message would have been preceded by another describing the error.
System Action:
Action:
After the problem has been corrected, you may restart the product.
888I
STARTING TO FORMAT THE TRACK FILE
Reason:
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.
Action:
None. Be patient.
889I
TRACK FILE FORMAT COMPLETE
Reason:
The formatting run of the job tracking file has been completed.
System Action:
Action:
None.
800 - 899
890S
ESP INITIALIZATION DENIED BY INSTALLATION STARTUP EXIT
Reason:
The installation STARTUP exit gave a non-zero return code, requesting the product to
terminate.
System Action:
Action:
891W
ESP LAST ACTIVE AT xxxx ON yyyy
Reason:
The product is being restarted, and the current date and time differ by more than a user
defined threshold from the time that the product was last active.
System Action:
Action:
Check the times specified on this message and the following message.
892W
IT IS NOW xxxx ON yyyy
Reason:
The product is displaying the current system time and date. This message follows
message 891.
System Action:
Action:
Check to ensure the time as displayed by the product is the correct time and date.
800 - 899
893A
CONFIRM DATE AND REPLY 'Y' TO CONTINUE, 'N' TO TERMINATE OR 'Q' TO QUIESCE
Reason:
This message follows messages 891 and 892. See above.
System Action:
The product awaits a response. If the response is 'Y', the product continues. A response
of 'N' causes the product to terminate.
Action:
If the current date and time is correct, reply 'Y'. If the date or time is incorrect, reply 'N'
to terminate the product then schedule an IPL to correct the time. The product may
then be restarted.
894S
ESP TERMINATING DUE TO INCORRECT CLOCK SETTING
Reason:
This message follows a response of 'N' to message 893.
System Action:
Action:
The product should be restarted after the clocks are reset.
895E
UNABLE TO LOAD USER-VERIFY EXIT ROUTINE
Reason:
The product attempted to but was unable to load the user verification exit routine.
System Action:
This message is followed by a prompt message.
Action:
800 - 899
896E
MODULE xxxx NOT IN COMMON STORAGE
Reason:
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.
Action:
Notify your system programmer who should ensure that the exit routine is placed in the
LPA or MLPA. The product can be initialized without the exit by responding 'END' to the
prompt message that follows this one.
897W
LOCAL TIME xxxx ON yyyy zzzzaaaa bbbb
Reason:
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.
Action:
800 - 899
898A
REPLY 'Y' TO PROCEED OR REPLY 'N' TO TERMINATE
Reason:
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:
Action:
If you meant to offset the local time from GMT time, reply 'Y' to allow the product to
continue. To reset the TOD clock, reply 'N' to terminate the product. 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.
899W
WARNING, ERRORS MAY OCCUR DUE TO TOD CLOCK INCONSISTENCY
Reason:
discrepancy was found between the Local and GMT time. In response to message 989,
the operator had replied 'Y'.
System Action:
Action:
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.
900 - 999
900 - 999
900I
xxxx
Reason:
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:
Action:
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.
901A
xxxx
Reason:
This is a prompt message which requests a user to enter or reenter a parameter.
System Action:
The system waits for the response.
Action:
Enter the missing parameter or reenter an incorrectly specified parameter.
900 - 999
902E
LOGIC ERROR IN MESSAGE I/O REQUEST
Reason:
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.
Action:
903E
xDab <function>, Dsn=<dsname>, not locked by current thread
Reason:
An internal logic error occurred while processing a VSAM I/O API request. <function>
specifies the VSAM API request. <dsname> specifies the VSAM data set name that the
request was issued to.
System Action:
The VSAM I/O API request is ignored.
Action:
This problem should never occur. If it does, contact CA Support.
904E
PRINT FILE xxxx NOT FOUND
Reason:
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:
Action:
Ensure the correct file name is specified.
900 - 999
905I
REQUIRED ENTRY NOT FOUND
Reason:
The specified command name was not found.
System Action:
The command's CLE was not dumped.
Action:
Correct the command name and try again.
906E
xxxx
Reason:
This message is an error message relating to a command or parameter statement that is
being scanned.
System Action:
Action:
Check parameters for validity, correct the error and retry.
907I
OK
Reason:
The requested HISTFILE operation has completed successfully.
System Action:
The operation is complete.
Action:
None.
900 - 999
908E
ATTACH ERROR nn
Reason:
An error occurred while attaching the command.
System Action:
Action:
Try again later.
909W
Reason:
The syntax of this command is incorrect.
System Action:
Action:
910S
XTLOCK request logic error
Reason:
An invalid thread locking request was made within CA Workload Automation EE.
System Action:
Task is abended with code U0901.
Action:
Internal logic error. Call your software support personnel.
900 - 999
911W
WARNING, LICENCE PERIOD EXPIRES IN nn xxxx
Reason:
The license period for the product is coming close to expiry.
System Action:
Processing continues. The product will not execute after days unless the appropriate
authorization codes are applied.
Action:
Contact CA to obtain authorization codes for your site.
912S
xxxx
Reason:
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.
Action:
This depends on the error.
913S
UNABLE TO OPEN FILE xxxx, PROCESSING TERMINATED
Reason:
An I/O error occurred while trying to open the primary output file. This is probably due
to a missing DD statement.
System Action:
Action:
Correct the problem and retry.
900 - 999
914E
xxxx
Reason:
An error occurred trying to close an input or output data set. The text of the message
System Action:
This depends on how critical the data set is.
Action:
Retry after the problem is corrected.
915E
xxxx
Reason:
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.
Action:
916E
UNEXPECTED END OF DATA ON FILE xxxx
Reason:
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.
Action:
900 - 999
917E
xxxx DD STATEMENT MISSING
Reason:
A Print command specified output to a preallocated file. However, the file was not
preallocated.
System Action:
The print file request is ignored.
Action:
Preallocate the file, or correct the file name.
918E
PRINT ID MISSING OR INVALID ON DEFPRINT COMMAND
Reason:
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.
Action:
Ensure a valid print ID is specified.
919E
PRINT FILE xxxx NOT FOUND
Reason:
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:
Action:
Ensure the correct file name is specified.
900 - 999
920W
COMMAND INVALID IN BATCH
Reason:
An implicit EXEC, a HELP or a TSO command was specified outside of the TSO
environment.
System Action:
Action:
Only specify the command in a TSO environment.
921E
ENDTEMPL statement missing
Reason:
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.
Action:
Add the ENDTEMPL statement to the end of the TEMPLATE definition.
922E
TEMPLATE nesting limit of n exceeded. TEMPLATE ignored
Reason:
The depth of a TEMPLATE invocation exceeds n. There is probably a line in a template
which invokes itself.
System Action:
Execution of current procedure is terminated.
Action:
Check for recursive invocation and correct procedure. If there is no recursive invocation
redesign templates to reduce the depth to acceptable level.
900 - 999
923C
SVC Display
Reason:
Response to DSVC or OPER CALLRTN CYBUT003 command. A request was made to
display information from the SVC table. This is the first line of a multiple line display.
System Action:
Action:
None.
924I
DASD DISPLAY
Reason:
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.
System Action:
Action:
None.
900 - 999
925E
GQSCAN RC=8. Request terminated
Reason:
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.
Action:
Increase Region Size or be more specific in the request or use keyword SEGMENTED,
which allows the program to accept the data portion after portion.
Important!. 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
926S
GQSCAN RC=nn. Request can not be processed
Reason:
MVS (nn=12) or CPE (nn=16) error was encountered while processing the request.
System/CPE tables/queues may be corrupted.
System Action:
Action:
You may retry the request one or more times. If it won't help, then recycle will.
900 - 999
927E
GQSCAN RC=20. Request could not be processed. Try later
Reason:
The limit for the number of concurrent resource requests has been reached (this limit is
system defined).
System Action:
Action:
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.
928C
DSVC HELP
Reason:
Response to DSVC HELP or OPER CALLRTN CYBUT003 HELP command.
System Action:
DSVC or OPER CALLRTN CYBUT003 command options are displayed.
Action:
None.
929W
xxxxxx
Reason:
The message xxxxx explains the actions taken or the result achieved while processing
the request.
System Action:
Execution continues/completes.
Action:
Analyze the results of the request and if not satisfied reissue another request with
different parameters.
900 - 999
930E
Space obtained for WASIZE not enough to hold all data
Reason:
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:
Action:
Increase the SIZE specification, and reexecute the request. To double the size of the
work area, for instance, specify:
CALLRTN CYBUT005 SIZE(131072)
931S
Error in Virtual Storage Management data areas
Reason:
MVS system error. An error encountered while scanning VSM data areas.
System Action:
Action:
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.
900 - 999
932S
Invalid Return Code from system macro VSMLIST. RC=n
Reason:
System macro VSMLIST returned invalid RC.
System Action:
Action:
Notify system support personnel. Anything is possible including corruption of system
linkage table.
933C
Subsystem Interface Display
Reason:
Response to DSUBSYS or OPER CALLRTN CYBUT004 command. A request was made to
display subsystem interface information. This is the first line of a multiple line display.
System Action:
Action:
None.
934C
DSUBSYS HELP
Reason:
Response to DSUBSYS HELP or OPER CALLRTN CYBUT004 HELP command.
System Action:
DSUBSYS or OPER CALLRTN CYBUT004 command options are displayed.
Action:
None.
900 - 999
935C
DSMFI HELP
Reason:
Response to DSMFI HELP or OPER CALLRTN CYBUT008 HELP command.
System Action:
DSMFI or OPER CALLRTN CYBUT008 command options are displayed.
Action:
None.
936I
SMF Intercept Display
Reason:
Response to DSMFI or OPER CALLRTN CYBUT008 command. A request was made to
display SMF intercept information. This is the first line of a multiple line display.
System Action:
Action:
None.
936I
SMF Intercept Display
Reason:
Response to DSMFI or OPER CALLRTN CYBUT008 command. A request was made to
display SMF intercept information. This is the first line of a multiple line display.
System Action:
Action:
None.
900 - 999
938S
SVCUPDTE error return code <ccc> for SVC <nnn>
Reason:
A CA Workload Automation EE subsystem attempted unsuccessfully to update the
system SVC table entry for SVC <nnn>. The SVCUPDTE system service gave an error
return code <ccc>.
System Action:
Action:
Should never occur. If it does, call CA Support.
939S
Data set xxxxxx has been overwritten
Reason:
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. ABENDU1106 is issued to abnormally terminate processing.
Action:
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.
900 - 999
940S
ABOVE ERROR OCCURRED READING PRIMARY CHECKPOINT
Reason:
An error occurred reading the primary checkpoint data set. A preceding message would
describe the exact error.
System Action:
Action:
Take action according to the preceding message.
941S
ABOVE ERROR OCCURRED WRITING PRIMARY CHECKPOINT
Reason:
An error occurred writing the primary checkpoint data set. A preceding message would
describe the exact error.
System Action:
Action:
Take action according to the preceding message.
942I
TERMINATING
Reason:
There has been a severe error while writing the primary checkpoint file.
System Action:
The product is shutting down.
Action:
Check the preceding messages for more information on this error.
900 - 999
943E
WILL ATTEMPT REFORMAT
Reason:
A severe error has occurred on the alternate checkpoint file.
System Action:
The product is attempting to reformat the alternate checkpoint file.
Action:
None required if the reformat is successful. If it is not successful, a new alternate
checkpoint file should be defined.
944E
REFORMAT FAILED, TERMINATING
Reason:
There has been an uncorrectable error on the alternate checkpoint file.
System Action:
Action:
945I
TERMINATING
Reason:
There has been a severe error while reading from the primary checkpoint file.
System Action:
Action:
900 - 999
946S
ERROR OCCURRED PROCESSING ALTERNATE CHECKPOINT
Reason:
A severe error has occurred on the alternate checkpoint file.
System Action:
The product is attempting to reformat the alternate checkpoint file.
Action:
Support.
947S
Serialization-control error on XXXXXX.
Reason:
The Queue File XXXXXX is found to be overridden by another system. This was caused by
the failure of serialization setting.
System Action:
The product system is shut down.
Action:
Solve the serialization problem, and re-start the system. The most likely reasons for the
problem are:
The initialization parameter RSVLOGIC was not set to be the same for all the
systems accessing the same Queue File.
The serialization system (that is GRS or MIM) doesn't work for all the systems
accessing the same Queue File.
The queue name(QNAME) used by RSVLOGIC is incorrectly defined to the

serialization system, that is, excluded from GRS, but not included in MIM.
900 - 999
948I
REFORMAT OF DUPLEX SUCCESSFUL
Reason:
The alternate checkpoint file has been successfully reformatted.
System Action:
Action:
None required.
949W
WAITING FOR {I/O COMPLETION|RESERVE} ON DATA SET xxxx
Reason:
The product is waiting for access to a data set.
System Action:
The product will issue this message periodically until access has been granted.
Action:
Verify that nothing is holding a long term reserve on the named data set.
950E
INVALID TIMEZONE ADJUSTMENT xxxx
Reason:
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.
Action:
Reenter the statement at the prompt.
900 - 999
951E
INVALID TIMEZONE CODE, nn SHOULD BE 0-63
Reason:
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.
Action:
Respond to the prompt that follows. The initialization parameter library should also be
updated.
952E
TIMEZONE CODE nn NOT VALID FOR ZONE NAME xxxx
Reason:
A TIMEZONE statement specified an invalid code id and timezone name combination.
Certain codes are reserved for certain time zones. These include: 0-LOCAL, 1-UTC,
2-GMT, 3-Z.
System Action:
The operator is prompted to reenter the statement.
Action:
Use a valid combination. If defining a new zone, use a non-reserved code id.
953S
ESP SUBSYSTEM CANNOT BE RUN IN BATCH AT INSTALLATION REQUEST
Reason:
The subsystem was being invoked as a batch job. However, the RUNMODE NOBATCH
option was specified in the initialization parameter data set.
System Action:
The job terminates.
Action:
This is a probable user error, by invoking the started task procedure instead of the
command interface module.
900 - 999
954S
TP SERVER INITIALIZATION FAILED, ERROR CODE nn
Reason:
The initialization for the VTAM LU 6.2 communication server task failed. The errors
would be described on preceding messages.
System Action:
The subsystem terminates.
Action:
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 the product.
955W
Console xxxx {not found|invalid}
Reason:
A CONSOLE command specified either a console that was not found or an invalid
console name. xxxx must be one of the following - 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.
Action:
Correct CONSOLE specification xxxx and try again.
900 - 999
956W
EMCS console xxxx specification invalid, CNID=yyyy{, System=zzzz}
Reason:
A CONSOLE command specified an extended MCS console xxxx. xxxx must specify a real
console.
System Action:
Action:
Correct CONSOLE specification xxxx to specify a real console and try again.
957W
Console xxxx inactive, CNID=yyyy
Reason:
A CONSOLE command specified an inactive console xxxx. yyyy is the console ID of
console xxxx.
System Action:
Action:
Correct CONSOLE specification xxxx to specify an active console and try again.
958W
Request only valid from a console
Reason:
An asterisk can only be used in a CONSOLE command entered at a console.
System Action:
Action:
Remove this CONSOLE command from the initialization parameters, or replace the
asterisk by a valid console name.
900 - 999
959I
Primary console is cccc, CNID=iiii{, System=ssss}{, Unit=uuuu}
Reason:
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.
System Action:
None.
Action:
None.
960W
{Command xxxx|STOP command} rejected, source invalid|unknown
Reason:
A MODIFY,xxxx or STOP system command was issued from an invalid or unknown
source. 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.
Action:
If authorized, re-issue the MODIFY or STOP system command from a console or TSO
address space.
900 - 999
961E
CSVDYNL List RtnCode=<rtncode>, RsnCode=<rsncode>
Reason:
A CSVDYNL LIST system call to retrieve system LINKLIST information failed.
<rtncode> - specifies the decimal return code of the CSVDYNL LIST system call.
<rsncode> - specifies the hexadecimal reason code of the CSVDYNL LIST system call.
System Action:
Action:
Should not occur. If unable to diagnose the problem contact CA Support.
962E
UNABLE TO SET RESERVE QNAME, RESERVE IS ACTIVE
Reason:
The QNAME cannot be changed if a RESERVE is presently active.
System Action:
The QNAME was not changed.
Action:
Try again later.
965C
DDB DISPLAY
Reason:
The LISTDDB command displays maintenance levels, shipping dates, and authorization
codes.
System Action:
Action:
None required.
900 - 999
966E
AUTHORITY CODE OFFSET OUT OF RANGE - 1 TO 32 ALLOWED
Reason:
The OFFSET parameter is out of range. Only offset from 1 to 32 are allowed.
System Action:
The LISTDDB command is terminated.
Action:
Correct the OFFSET and try again.
967E
INVALID DIAGNOSTIC DATA BLOCK
Reason:
The Diagnostic Data Block has been damaged.
System Action:
Action:
Restore a valid Diagnostic Data Block module to the load library.
968E
PRODUCT xxxx NOT FOUND
Reason:
The specified PRODUCT name could not be found in the DDB descriptor.
System Action:
Action:
Specify a product name of 'ESP'.
900 - 999
970I
RESERVE LOGIC NOT INITIALIZED
Reason:
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.
Action:
If you want reserve/enqueue logic to be performed, use the RSVLOGIC command to
initialize it.
971S
INVALID TOKEN PASSED TO RELEASE/DEQ ROUTINE
Reason:
The RELEASE/DEQ routine was passed an invalid token. This is probably due to an
System Action:
Since the RELEASE or DEQ could not be performed, the program abends to release the
reserve or cross systems ENQ.
Action:
The resulting dump should be sent to your software support personnel. The subsystem
can be restarted.
972E
UNABLE TO UPDATE RSVLOGIC, DATABASE IS CURRENTLY LOCKED
Reason:
The RSVLOGIC method cannot be changed while the database is locked.
System Action:
The requested function is not performed.
Action:
Try the RSVLOGIC command later.
900 - 999
973S
POSSIBLE LOSS OF INTEGRITY AS DATABASES ARE NOT ON SAME VOLUME
Reason:
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.
Action:
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.
974C
RSVLOGIC STATUS
Reason:
This command describes the reserve logic now in use by the product.
System Action:
Action:
None required.
975W
INVALID MESSAGE ID RANGE, nn:nn
Reason:
The first number must be no larger than the second.
System Action:
Action:
Correct the range and try again.
900 - 999
976W
MESSAGE ID OUTSIDE OF PERMITTED RANGE
Reason:
The valid range of message ID's is from 100 to 3500.
System Action:
Action:
Correct the message ID range and try again.
977E
INVALID MESSAGE TYPE NAME xxxx
Reason:
The message type must be INFOR, WARNING, ERROR or SEVERE.
System Action:
The message was not defined.
Action:
Correct the message type and try again.
979S
PUTGET ERROR CODE nn
Reason:
The CPE message handler attempted to obtain the next input line from a TSO user using
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.
Action:
Investigate the failure of the IBM TSO service routine.
900 - 999
980S
PARM=xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
Reason:
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.
Action:
See message 0979.
981E
GETMAIN failed in CYBUT005 with RC=xx
Reason:
GETMAIN was not able to allocate enough memory in CYBUT005. The return code from
the GETMAIN macro is shown in the message - RC=xx.
System Action:
CYBUT005 processing terminates with a return code 4.
Action:
Ensure there is enough REGION size given to the ESP subsystem and ensure there is
adequate SIZE when calling CYBUT005 utility. Increase the REGION specification on the
EXEC card and restart ESP or decrease the SIZE parameter specified when calling
CYBUT005 utility: CALLRTN CYBUT005 SIZE(xxxx).
982E
Optional SIZE parameter must be above 4095 bytes.
Reason:
Minimal SIZE parameter value must be above 4095 bytes.
System Action:
CYBUT005 processing terminates with a return code 4.
Action:
Ensure there is optional SIZE parameter value above 4095 bytes.
900 - 999
990E
UNABLE TO LOAD SORT PROGRAM
Reason:
The requested sort program could not be found.
System Action:
The SORT function was not performed.
Action:
Specify the correct sort program in the initialization parameters using the 'SORT pgm'
statement, and restart the product.
991E
ERROR OCCURRED DURING SORT
Reason:
The sort program did not complete.
System Action:
The sort operation was not performed.
Action:
Check the console log for further sort error messages, or try a different sort program.
992W
Ambiguous RESOURCE statement
Reason:
RESOURCE statement may cause unexpected result when space is between 'ADD' and
'('.
System Action:
Process continues.
Action:
Check LR CSF command to see resources allocated to the job.
900 - 999
997E
Alert Event processing error
Reason:
During processing of the Continuous parameter on a WOB command, the system could
not locate required control blocks.
System Action:
Statement is rejected.
Action:
Determine cause of problem, and retry.
998E
Alert ID too long: xxxxxx
Reason:
Alert ID should not exceed 4 characters, unless parameter designates an event ID, in
which case it must include a period.
System Action:
Statement is rejected.
Action:
Correct statement and retry.
999W
UNABLE TO OBTAIN SUFFICIENT CSA FOR xxxx
Reason:
There is insufficient CSA storage in the MVS system. The required storage may reside
above the 16Mb line.
System Action:
Action:
An IPL is required to restore CSA levels.

1000 - 1099
1000E
APPLID NOT SPECIFIED FOR WOB xxxx
Reason:
No application ID was specified for a WOB, either at the job level or for the application
as a whole.
System Action:
The application is rejected.
Action:
Correct the error
1001E
xxxx INVALID IN A JOBDOC ENTRY
Reason:
A statement was encountered in a job documentation entry that is only valid in an
ESPPROC member.
System Action:
The entire Event is suppressed.
Action:
Correct the statement or move it into the calling ESPPROC.
1000 - 1099
1002E
xxxx INVALID OUTSIDE OF A JOBDOC ENTRY
Reason:
A statement was encountered in an ESPPROC that is only valid in a job documentation
entry.
System Action:
The entire Event is suppressed.
Action:
Correct the statement or move it into a job documentation entry.
1003E
xxxx INVALID OUTSIDE OF A JOB ENTRY
Reason:
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.
Action:
Correct the placing of the statement.
1004E
P-NODE NAME MISSING OR INVALID
Reason:
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.
Action:
A P-node name should consist of 1-16 alphanumeric characters, including the
underscore character. The first character should be alphabetic.
1000 - 1099
1005E
INCONSISTENT xxxx PARAMETERS
Reason:
The parameters on a COREQ, PREREQ, RELEASE, POSTREQ or RESOURCE statement were
not consistent. For example, the ADD or DROP keywords may have been combined
incorrectly.
System Action:
The ESPPROC and the entire Event calling it is aborted.
Action:
Correct the specification.
1006E
INVALID KEYWORD xxxx
Reason:
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.
Action:
Correct the statement in error.
1007I
xxxx
Reason:
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.
Action:
See the description of the preceding message.
1000 - 1099
1008E
INVALID PARAMETER ON CCFAIL STATEMENT
Reason:
A CCFAIL statement did not have the correct format.
System Action:
The ESPPROC is terminated.
Action:
Correct the CCFAIL statement in error and trigger the Event again.
1009E
INVALID PARAMETER xxxx
Reason:
A CCFAIL statement in an ESPPROC or JOBDOC entry had invalid data.
System Action:
Action:
Correct the error, and trigger the Event again.
1010E
INVALID PARAMETERS PASSED TO "SELECTED" FUNCTION
Reason:
The 'SELECTED' function in a 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:
Action:
Correct the job name specification.
1000 - 1099
1011E
Job xxxx has invalid reference to itself
Reason:
A job refers to itself on a POSTREQ, PREREQ, COREQ or RELEASE statement. This is
invalid.
System Action:
Action:
Correct the statement in error and trigger the Event.
1012E
NET ID REQUIRED BUT NOT SPECIFIED FOR JOB xxxx
Reason:
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:
Action:
Specify a jobnet ID for the job, and trigger the Event. If an application is desired, provide
an APPL statement prior to the first job.
1000 - 1099
1013E
INVALID RESOURCE NAME xxxx
Reason:
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:
Action:
Correct the RESOURCE statement in error and reschedule the ESPPROC.
1014E
INVALID SYSTEM ID SPECIFIED
Reason:
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.
Action:
Correct the specification and reschedule the ESPPROC.
1000 - 1099
1015E
xxxx EXCEEDS MAXIMUM ALLOWABLE NUMBER OF RESOURCES
Reason:
A RESOURCE statement specified a number of resources greater than the maximum
allowable of 8 megabytes (-/+ 8388607).
System Action:
Action:
Correct the RESOURCE statement in error and reschedule the ESPPROC.
1016E
Invalid job name
Reason:
An invalid job name was entered. The job name must conform to the following rules The length may not exceed 64 characters. The first character must be alphabetic (upper
or lower case) or national (@, # or $). The remaining characters must be alphanumeric,
a period (.) or an underscore (_). Two consecutive periods (.) are not permitted. The last
character may not be a period (.). For MVS jobs - If the length exceeds 8 characters, a
period must be specified before the 10th character. Characters preceding the 1st
period, or the entire job name if no period exists, must conform to MVS job name rules
(underscores not permitted), except alphabetics may be lower case.
System Action:
The Event is suppressed.
Action:
Correct the erroneous ESPPROC job name and trigger the Event again.
1000 - 1099
1017E
INVALID PARAMETERS PASSED TO JOBONQ FUNCTION
Reason:
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.
Action:
1018E
SUBSYSTEM REQUEST ERROR CODE nn ENCOUNTERED BY JOBONQ FUNCTION
Reason:
A serious error has occurred with either JES or the subsystem.
System Action:
The JOBONQ function was not performed.
Action:
Check the status of JES and the subsystem.
1019W
RESOURCES ARE IGNORED FOR LINKS
Reason:
A link has been defined, and its definition contains a RESOURCE statement. This
statement is ignored.
System Action:
The link is treated as if it has no RESOURCE statement. This warning message is only
displayed if the event was simulated.
Action:
Make sure the LINK option was desired.
1000 - 1099
1020E
ABANDON STATEMENT PARAMETERS OMITTED OR INVALID
Reason:
An ABANDON statement in an ESPPROC or job documentation member contained an
invalid parameter.
System Action:
The Event is failed.
Action:
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
Reason:
A job has missed its late submit time. The late submit time was specified in the
definition of the job.
System Action:
Action:
You should display the application to find out what the job is waiting on.
1022W
Reason:
A job has missed its late end time. The late end time was specified in the definition of
the job.
System Action:
Action:
1000 - 1099
1023I
Auditlog data set spun with nn records to sysout class xxxx
Reason:
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.
Action:
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
Reason:
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 the
product is restarted.
Action:
The product should be restarted. If the error persists, comment out the AUDITLOG
initialization statement and place an AUDITLOG DD statement in the started task
procedure until the problem can be resolved.
1000 - 1099
1025W
Dynamic sysout auditlog not initialized, use AUDITLOG initialization parameter
Reason:
The SPINLOG command was issued. This command is only available if the AUDITLOG
initialization parameter is used.
System Action:
Action:
Add the AUDITLOG initialization statement to the parameter data set and restart the
product. 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'
Reason:
The 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.
Action:
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 CA Support.
1000 - 1099
1027E
ISCDEF STATEMENT INCOMPATIBLE WITH ISCOPT LU62
Reason:
In the initialization parameters, the LU 6.2 TP server was chosen as the method of
inter-system communication using the ISCOPT statement. The statement ISCDEF is valid
only for the NJE method.
System Action:
Action:
Specify either ISCOPT NJE or remove the statement in question.
1028E
UNABLE TO START INTERSYSTEM JOB TRACKING, FDBK = X'xxxx'
Reason:
The inter-system tracking receiver component 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.
Action:
If the problem cannot be determined from the feedback code, contact CA Support.
1000 - 1099
1029E
UNABLE TO RECEIVE INTER SYSTEM TRACKING DATA, FDBK = X'xxxx'
Reason:
The inter-system tracking receiver component attempted to issue a receive to the TP
server but was unable to do so, resulting in the feedback code xxxx.
System Action:
The product will not obtain the tracking data; it will be stored on the local checkpoint
until a receive can be properly completed.
Action:
1030E
UNABLE TO STOP ISC TRACKING RECEIVER, FDBK = X'xxxx'
Reason:
During shutdown processing, the product 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:
The product shutdown processing continues. The TP server's cleanup processing should
complete the stop request.
Action:
If the product shuts down successfully, there is not a problem. Otherwise, contact CA
Support.
1031I
INTER-SYSTEM TRACKING RECEIVER IS STOPPED
Reason:
The product has successfully stopped the receiver for inter-system job tracking data.
System Action:
None.
Action:
None.
1000 - 1099
1032E
UNABLE TO START INFOSERV_JOB_TRACKING PROCESSOR, FDBK = X'xxxx'
Reason:
The Infoserv job tracking response processor component 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.
Action:
1033E
UNABLE TO RECEIVE INFOSERV JOB TRACKING RESPONSE DATA, FDBK = X'xxxx'
Reason:
The Infoserv job tracking response processor component attempted to receive data
from the TP server but was unable to do so, resulting in the feedback code xxxx.
System Action:
The product will not obtain the response data it will be stored on the local response
data checkpoint until a receive can be properly completed.
Action:
1000 - 1099
1034E
UNABLE TO STOP INFOSERV_JOB_TRACKING PROCESSOR, FDBK = X'xxxx'
Reason:
Due to a previous error condition, the product attempted to shut down 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 complete the stop
request.
Action:
Contact CA Support to report the error.
1035I
INFOSERV_JOB_TRACKING PROCESSOR IS STOPPED
Reason:
The product has successfully stopped the receiver for inter-system job tracking data.
System Action:
Action:
None.
1036E
ERROR CODE nn PROCESSING INFOSERV RESPONSE BUFFER
Reason:
The Infoserv job tracking response processor component encountered an error while
processing a response from INFOSERV. This is an internal error condition.
System Action:
The response is not processed. Processing continues.
Action:
Report the error code to CA Support.
1000 - 1099
1037E
INSUFFICIENT SPACE IN xxxx APPL RECORD FOR INFO/SYSTEM UPDATE TO JOB yyyy
Reason:
When the product 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.
Action:
1038W
Insufficient space in xxxx APPL record for status message insertion for JOB yyyy
Reason:
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.
Action:
1000 - 1099
1039E
Unknown alert ID: xxxx
Reason:
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.
Action:
Either correct the alert name, or define the alert.
1040E
QUEUE update not allowed from a proxy subsystem
Reason:
A cleanup of the QUEUE data set was attempted from a proxy subsystem.
System Action:
Request ignored.
Action:
Any update of the QUEUE data set can be done only from the master subsystem of a
master/proxy complex.
1041W
MULTIPLE NET RELEASES NOT PERMITTED FOR JES3
Reason:
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.
Action:
Re-enter the event specifying only one job per NETREL request on the DJCDATA
statement.
1000 - 1099
1042E
Insufficient checkpoint space to queue type 9 XME
Reason:
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 history file. This message is followed by message 1043E,
which gives details of the affected job.
Action:
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 history file.
1043E
Error occurred for job jjjj in appl aaaa.ggg
Reason:
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:
Action:
Follow the instructions for the preceding message.
1000 - 1099
1044E
Job jjjj(nnn) in appl aaaa.ggg not being tracked
Reason:
jjjj - Job name
nnn - JES job number
aaaa - Application name
ggg - Application generation
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.
Action:
Be aware that this job's modified overdue time(s) will not be propagated to the job
history file. Contact CA Support for further assistance.
1045E
Error occurred updating job jjjj(nnn) in appl aaaa.ggg
Reason:
jjjj - Job name
nnn - JES job number
aaaa - Application name
ggg - Application generation
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:
Action:
Follow the instructions for the preceding message.
1000 - 1099
1046W
Application manager is waiting for checkpoint space.
Reason:
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.
Action:
Checkpoint should be made bigger to prevent processing delays.
1047E
Insufficient space in xxx APPL record to store event parms for yyy
Reason:
When the product 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.
Action:
1048W
Command rejected, High Performance Option not enabled
Reason:
An APPLJOB or AJ command or equivalent CSF line command was issued that requires
that the High Performance Option (HPO) be enabled.
System Action:
Action:
None.
1000 - 1099
1049E
INVALID PARAMETERS PASSED TO "COMPLETED" FUNCTION
Reason:
The 'COMPLETED' function in a Procedure was passed an invalid application name or
second parameter. The name must be a character variable or literal value, with a length
not exceeding 8 characters. The second parameter, if specified, must be a literal ALL.
System Action:
Action:
Correct the application name specification and/or second parameter.
1050E
NOT AUTHORIZED FOR REXXON STATEMENT
Reason:
A REXXON statement was encountered in a 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.
Action:
If you need access to the REXX facility, request read access to the REXXON resource
from your administrator.
1051E
Not authorized for ABSORB statement
Reason:
You do not have authorization to use the ABSORB function.
System Action:
The application is not generated.
Action:
Remove the ABSORB statement. Or, have your security administrator grant read access
to the profile prefix.RESABSORB.
1000 - 1099
1052E
Invalid resource quantity at offset nn in RELRES list
Reason:
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.
Action:
Correct the RELRES statement.
1053E
Resource name expected at offset nn in RELRES list
Reason:
The resource name was missing from the RELRES list.
System Action:
The resource status is not altered. The remainder of the RELRES list is ignored.
Action:
Correct the RELRES statement.
1054E
Command invalid outside of job entry
Reason:
An StepEnd statement was encountered, but it was not within a job.
System Action:
The statement is rejected. An event error results.
Action:
Reposition or remove the statement.
1000 - 1099
1057I
Procedure cache status
Reason:
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
Action:
N/A
1058I
Critical path calculation is ssss
Reason:
This message is a response to CRITPATH operator command. It displays the status of
dynamic critical path processing by the product. 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.
System Action:
N/A
Action:
N/A
1000 - 1099
1059W
SELFCOMPLETE is only valid for tasks, ignored
Reason:
The SELFCOMPLETE parameter is only meaningful for tasks. It is ignored for other job
types.
System Action:
The parameter is ignored.
Action:
Remove this parameter.
1060E
Not authorized to trigger events in group xxxxxxxx
Reason:
User is not authorized to trigger events in this group - this level of authorization is
required by the EVENT subparameter in the NOTIFY statement.
System Action:
The NOTIFY statement is rejected
Action:
Get the appropriate authority, or change NOTIFY statement
1061E
Application Manager subsystem request ended with return code xxxx
Reason:
The Application Manager encountered an error while processing a rerun-multiple-jobs
request and did not return an error message.
System Action:
The rerun-multiple-jobs request is not completed.
Action:
1000 - 1099
1063E
Not authorized to events in group xxxxxxxx
Reason:
User is not authorized to READ events in this group. This level of authorization is
System Action:
The NOTIFY statement is rejected
Action:
1068S
I/O Error on <dsname>, <I/O_error_description>
Reason:
An I/O error occurred on QUEUE file data set <dsname> during CA Workload
Automation EE subsystem initialization.
System Action:
Action:
Attempt to determine the cause of the QUEUE data set I/O error and resolve it. If the
QUEUE file data set is corrupted, restart the CA Workload Automation EE subsystem
with the QFORMAT start-up parameter to reformat the QUEUE file data set. If unable to
determine the problem, contact CA Support.
1070W
File <percent>% full, Dsn=<data.set.name>
Reason:
CKPT or QUEUE file usage has exceeded 50%, 70%, 90% or 99%.
<percent> specifies the CKPT or QUEUE file usage percentage value.
<data.set.name> specifies the CKPT or QUEUE file data set name.
The <percent> value is calculated by adding a 0.5% rounding value to file usage value.
This means, for example, that when 100% is specified in the message, the actual file
usage is within the range 99.5%-100% and if 51% percent is specified in the message,
the actual file usage is within the range 50.5%-51.4%.
1000 - 1099
System Action:
Another 1070W message will be issued if file usage exceeds another threshold. Message
1071I will be issued if file usage drops below the current threshold.
Action:
CKPT file high usage conditions are often the result of temporary conditions which can
be resolved by a simple action. For example, if a proxy's CKPT file has accumulated a
large job tracking backlog because the master has been down for some time, then
restarting the master will immediately clear the proxy CKPT file job tracking backlog
resulting in at least one 1071I message in the proxy's JESMSGLG file indicating the
proxy's CKPT file usage has dropped.
QUEUE file high usage conditions should not occur under normal operating conditions.
If a CKPT or QUEUE file's usage percent frequently rises above 90 percent under normal
operating conditions, then creating a new larger file should be considered.
If a new larger CKPT file is created to replace the existing CKPT file, a cold format of the
new CKPT file will be required using the COLD startup parameter when the CA WA ESP
Edition subsystem is started for the first time with the new CKPT file.
If a new larger QUEUE file is created to replace the existing QUEUE file, a cold format of
the new QUEUE file will be required using the QFORMAT startup parameter when the
CA WA ESP Edition subsystem is started for the first time with the new QUEUE file.
Note:
CKPT file usage can be displayed with the LISTCKPT command.
QUEUE file usage can be displayed with the LISTQ command.
1071I
File usage is down to <percent>%, Dsn=<data.set.name>
Reason:
CKPT or QUEUE file usage has dropped below 50%, 70%, 90% or 99%.
<percent> specifies the CKPT or QUEUE file usage percentage value.
<data.set.name> specifies the CKPT or QUEUE file data set name.
The <percent> value is calculated by adding a 0.5% rounding value to file usage value.
This means, for example, that when 42% is specified in the message, the actual file
usage is within the range 41.5%-42.4%.
1000 - 1099
System Action:
Message 1070W will be issued if the usage threshold that the file dropped below is
exceeded again. Message 1071I will be issued if file usage drops below a lower
threshold than the threshold it has just dropped below.
Action:
None.
1072W
<ci_percent>% CI usage, <ca_percent>% CA usage, <extents> {extent{s}|{st|nd|rd|th}
extent added}, Dsn=<dsname>
Reason:
A VSAM KSDS (Key Sequenced Data Set) data component's file CI or CA usage threshold
has been crossed or a new extent has been added.
CI: A VSAM file Control Interval. It corresponds to a physical record.
CA: A VSAM file Control Area. It is one cylinder when the file is allocated in cylinder
units.
<ci_percent> gives the VSAM KSDS data component's CI usage percent. It is the ratio of
the total size of all used CIs to the total size of the VSAM KSDS data component, times
100. Any CI containing data is considered to be used, regardless of how much free space
it may have.
<ca_percent> gives the VSAM KSDS data component's CA usage percent. It is the ratio of
the total size of all used CAs to the total size of the VSAM KSDS data component, times
100. Any CA containing at least one used CI is considered to be used, regardless of how
may empty CIs the CA may have.
<extents> specifies the number of extents, a value within the range 1-123, in the VSAM
KSDS data component.
<dsname> specifies the data set name of the VSAM KSDS data component.
CI usage percent will always be less than or equal to CA usage percent because there are
usually free CIs in used CAs and all CIs in free CAs are free.
1000 - 1099
If the VSAM KSDS data component has one extent and the extent size is equal to the CA
size, then CA usage is always 100%, even when the data component is almost empty.
When this occurs only CI usage (not CA usage) is used to determine if a threshold has
been crossed and the message should be issued. Other than this, the following criteria
are used to determine when to issue the message 1 - If CI or CA usage percent crosses one of the following values: 50%, 70%, 90%, 99%,
then the message will be issued in the following form:
<ci_percent>% CI usage, <ca_percent>% CA usage, <extents>extent{s}, Dsn=<dsname>
2 - If a new extent is added to the KSDS data component, then the message will be
issued in the following form <ci_percent>% CI usage, <ca_percent>% CA usage, <extents>{st|nd|rd|th}extent added,
Dsn=<dsname>
System Action:
Action:
If the VSAM KSDS data component frequently goes into new extents then the data set
could be re-organized with larger allocation values, particularly the primary extent
allocation value. If possible, the VSAM KSDS data component primary allocation should
specify a sufficient number of cylinders to avoid secondary extent allocations between
data re-organizations.
When a VSAM KSDS data component is defined (by the IDCAMS DEFINE CLUSTER
command) in cylinder space allocation units (as should always be the case) then the
data component CA size will always be one cylinder. If a VSAM KSDS data component's
primary and secondary extent size is one cylinder, CA usage will always be 100%, even
though a large number of CIs within the CAs may be free. If a VSAM KSDS data
component's primary extent size exceeds one cylinder but the secondary extent size is
one cylinder, then CA usage will always be 100% after the data component goes into
secondary extents, even though a large number of CIs within the CAs may be free.
When the current VSAM KSDS data component extent size (primary or secondary)
exceeds one cylinder then free CA(s) may exist and CA usage will be less than 100%. A
new extent can only be added to a VSAM KSDS component if its CA usage is 100%.
When CA usage is 100%, CI usage percent gives a clue as to when an extent may be
added to the VSAM KSDS data component.
1073E
TRACKOPT RESTARTSTEP invalid on Proxy
Reason:
TRACKOPT initialization statement (or command) with a RESTARTSTEP operand is invalid
if entered on a Proxy
1000 - 1099
System Action:
TRACKOPT RESTARTSTEP is ignored
Action:
Remove the RESTARTSTEP operand from the TRACKOPT statement or command
1074E
TRACKOPT RESTARTSTEP invalid, not yet determined if Master
Reason:
TRACKOPT initialization statement with a RESTARTSTEP operand is entered before it can
be determined if it is entered on a Master or a Proxy
System Action:
TRACKOPT RESTARTSTEP is ignored
Action:
Correct the TRACKOPT initialization statement
1075I
Subsystem <SSID> {active|not found}
Reason:
Response to LOPRCMDS command. There are no OPER commands queued for later
execution because the target CA WA ESP Edition subsystem <SSID> is either active or
was not found.
System Action:
Action:
None
1076I
No queued OPER commands
Reason:
Response to LOPRCMDS command. The target CA WA ESP Edition subsystem is not
active and there are no OPER commands queued for later execution.
1000 - 1099
System Action:
Action:
None
1077C
LOPRCMDS
Reason:
Response to LOPRCMDS command.
System Action:
OPER commands queued for later execution because the target CA WA ESP Edition
subsystem is not active, are displayed.
Action:
None
1078E
Abend S0C4
Reason:
Response to LOPRCMDS command. An abend S0C4 occurred.
System Action:
The client recovers and processing continues.
Action:
This message should very rarely, if ever, occur. Retry the LOPRCMDS command. If it
continues to abend S0C4, call CA support.
1100 - 1199
1100 - 1199
1101W
Data set type not specified
Reason:
The RESTORE command did not specify the data set type to be restored.
System Action:
Action:
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
Reason:
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.
System Action:
Action:
None.
1103I
Restore of VSAM data set xxxx in progress
Reason:
Restore processing is now in progress. The original data set will be restored to its
current version.
System Action:
Action:
None.
1100 - 1199
1104E
Error allocating new VSAM data set xxxx
Reason:
An error occurred while allocating the specified data set for output during restore
processing.
System Action:
Restore processing is terminated.
Action:
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
Reason:
An error occurred while allocating the specified data set for output during restore
processing.
System Action:
Action:
The preceding message will describe the error condition. Reissue the RESTORE
command after the problem is diagnosed and corrected.
1100 - 1199
1106I
Record in error was from SMF JOURNAL data set
Reason:
An error occurred while writing a JOURNAL record to the output data set during restore
processing.
System Action:
Action:
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
Reason:
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:
Action:
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.
1100 - 1199
1108I
Key at time of error: xxxx
Reason:
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:
Action:
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
Reason:
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.
System Action:
Action:
None.
1100 - 1199
1110I
nn updates restored from JOURNAL data set
Reason:
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.
System Action:
Action:
None.
1111I
Restore of VSAM data set xxxx ended successfully
Reason:
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.
System Action:
Action:
None.
1112I
nn records written to VSAM data set
Reason:
The count represents the total number of records written to the VSAM data set during
restore processing. This message is followed by message ESP1113.
System Action:
Action:
None.
1100 - 1199
1113E
Restore of VSAM data set xxxx terminated due to errors
Reason:
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.
Action:
Check the preceding messages for more information on the cause of the error.
1114E
VSAM control record not found in BACKUP data set xxxx
Reason:
The BACKUP data set has been damaged or has not been written to.
System Action:
The RESTORE operation is terminated.
Action:
Retry the RESTORE operation after locating a valid BACKUP data set.
1115E
Error occurred processing BACKUP data set xxxx
Reason:
The BACKUP data set has been damaged.
System Action:
The RESTORE operation is terminated.
Action:
Retry the RESTORE operation after locating an undamaged BACKUP data set.
1100 - 1199
1116E
Error occurred processing SORT data set
Reason:
An I/O error occurred while processing the SORT input data set.
System Action:
The sort operation is terminated.
Action:
Check the previous message for further information.
1117E
Invalid SMF record ID nn, must be in range 1-255
Reason:
The SMF record number in the SMFID parameter was out of range.
System Action:
The journal sort was not performed.
Action:
Correct the SMFID parameter and try again.
1118E
Error occurred during sort processing
Reason:
An I/O error occurred while processing the SORT output data set.
System Action:
Action:
1100 - 1199
1119E
Error occurred processing JOURNAL data set
Reason:
An I/O error occurred while attempting to sort the JOURNAL data set.
System Action:
Action:
1120W
APPL FILE xxxx UNFORMATTED
Reason:
The specified APPL file was found to be unformatted, or a new SlotSize was specified (in
the 'ApplFile' init statement) for an old APPL file.
System Action:
The product follows with message 1121.
Action:
1121A
REPLY 'Y' TO FORMAT THE APPL FILE WITH SLOTSIZE=nnnn OR REPLY 'N'
Reason:
The APPL file was found to be unformatted, or a new SlotSize was specified (in the
'ApplFile' init statement) for an old APPL file. Before proceeding, the product requests
permission from the operator.
System Action:
The product waits for the reply.
Action:
If you wish the APPL file to be formatted, reply Y, otherwise reply N and the product 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. WARNING: do not reformat the active APPL file in a production system.
1100 - 1199
1122W
INVALID RESPONSE
Reason:
An invalid response was given to a prompt message. The prompt is expecting a 'Y' or 'N'.
System Action:
Action:
1123E
CORRECT THE ABOVE PROBLEM AND RESTART ESP
Reason:
This message is issued after an error has occurred that prevents to further execution of
the product. This message would have been preceded by another describing the error.
System Action:
Action:
After the problem has been corrected, you may restart the product.
1124I
STARTING TO FORMAT THE APPL FILE xxxx
Reason:
The formatting run of the APPL file has begun. You may expect this to take an
System Action:
The APPL file is formatted.
Action:
None. Be patient.
1100 - 1199
1125I
APPL FILE FORMAT COMPLETE, SLOTSIZE=nnnn
Reason:
The formatting run of the APPL file has been completed. The new SlotSize is indicated.
System Action:
Action:
None.
1126E
APPL FILE DATASET IS TOO SMALL
Reason:
The APPL file data set is too small for effective processing.
System Action:
The APPL file cannot be used.
Action:
Allocate a larger file and restart the product. The file should be at least 10 cylinders in
size.
1127E
xxxx
Reason:
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.
Action:
1100 - 1199
1128S
APPL FILE DATASET xxxx UNUSABLE
Reason:
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 the product will terminate.
Action:
The APPL file data set may need to be restored from a backup.
1129W
JOB xxxx ALREADY EXISTS IN APPL yyyy
Reason:
System Action:
Action:
1130E
APPLFILE xxxx NOT FOUND FOR EVENT yyyy
Reason:
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.
Action:
Ensure that the APPLFILE definition is in the initialization parameter data set.
1100 - 1199
1131E
I/O ERROR OCCURRED READING APPL RECORD FOR EVENT xxxx
Reason:
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:
Action:
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
Reason:
A subsystem, executing with the job tracking processor in proxy mode, tried to queue a
tracking record to the master tracking 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.
Action:
Ensure that the master tracking processor is active.
1133W
The ESP MASTER system is either not tracking or is temporarily busy.
Reason:
This message follows message 1132. See the documentation of that message for more
information.
System Action:
See message 1132.
Action:
Ensure the master tracking system is active. If not, the TRACKOPT command can be used
to make this a master system.
1100 - 1199
1134E
INSUFFICIENT SPACE TO BUILD DESCRIPTOR FOR APPL xxxx, EVENT yyyy
Reason:
During the execution of an Event using an APPL, insufficient space was available to build
the APPL descriptor record.
System Action:
The APPLICATION is not built.
Action:
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
Reason:
An APPL file could not be found during application processing for an Event.
System Action:
The APPL is not built.
Action:
Ensure that the Event group or userid entry is assigned to a valid APPL file.
1100 - 1199
1136E
I/O ERROR OCCURRED BUILDING INDEX ENTRY FOR APPL xxxx, EVENT yyyy
Reason:
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.
Action:
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
Reason:
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.
Action:
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 restored from a backup. After the
problem is corrected, the Event will have to be retriggered manually to rebuild the
application.
1100 - 1199
1138E
INSUFFICIENT CHECKPOINT SPACE TO QUEUE ACTIVATION REQUEST FOR APPL xxxx,
EVENT y
Reason:
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 the product to pause for a few seconds.
Action:
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
Reason:
A user issued a command related to the application processing function of the product.
That function is not active.
System Action:
Action:
The application processing function must be activated. This requires the tracking facility
as well as at least one APPLFILE data set.
1100 - 1199
1140E
APPLFILE xxxx NOT FOUND
Reason:
An APPLFILE, required by an application processing command was not found.
System Action:
Action:
This may be due to the omission of an APPLFILE statement in the initialization
parameter data set.
1141W
APPLICATION xxxx NOT DEFINED
Reason:
An APPLICATION requested by a user was not found.
System Action:
The APPLICATION is not processed.
Action:
Ensure the application name is specified correctly.
1142W
NO MATCHING APPLICATIONS DEFINED OR NOT AUTHORIZED
Reason:
A user requested the retrieval of one or more applications. However, no matching
applications were found.
System Action:
Action:
Ensure the name is correctly specified, and that you have proper authority to the
application.
1100 - 1199
1143E
APPLBUFF TOO SMALL TO RETRIEVE APPLICATION
Reason:
A user requested a retrieval of a large application. However, the APPLBUF initialization
parameter was too small to retrieve.
System Action:
Action:
Increase the size of the APPLBUF initialization parameter and restart ESP.
1144E
APPLFILE xxxx IS CLOSED
Reason:
An application record retrieval failed because the required APPLFILE was closed.
System Action:
The record is not retrieved.
Action:
Determine the reason the file was closed. Retry when the file becomes available.
1145E
YOUR AUTHORITY IS INSUFFICIENT FOR ACCESS, OR APPLICATION xxxx NOT FOUND
Reason:
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:
Action:
Ensure the application name was specified correctly or grant the user sufficient access
to the application record.
1100 - 1199
1146E
INSUFFICIENT CHECKPOINT SPACE TO QUEUE REQUEST
Reason:
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.
Action:
Retry the command a little later.
1147E
REQUIRED GENERATION OF APPLICATION xxxx NOT FOUND
Reason:
A particular absolute or relative generation of an application was requested. However,
that generation was no longer available.
System Action:
Action:
Ensure you have specified the correct application name and generation number.
1100 - 1199
1148E
APPLFILE xxxx NOT FOUND FOR APPLICATION yyyy GEN nn
Reason:
During 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.
Action:
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 the product. 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
Reason:
During 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.
Action:
When the error with the jobindex data set is corrected, the product can be restarted to
pick up all the applications.
1100 - 1199
1150I
nn Applications are active
Reason:
After 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 the product as needed.
Action:
None.
1151E
INVALID FILE RECORD FOUND FOR APPL xxxx, GENERATION nn, SLOT nn
Reason:
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.
Action:
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 will pick up the application again.
1152E
ABOVE I/O ERROR OCCURRED READING APPL xxxx, GENERATION nn, SLOT nn
Reason:
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.
Action:
If the I/O error is corrected, a restart will cause the application to be picked up again.
1100 - 1199
1153W
APPLICATION MANAGER QUIESCED DUE TO PRIOR REQUEST
Reason:
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.
Action:
None.
1154W
APPLICATION MANAGER UNABLE TO ESTABLISH TIMER
Reason:
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.
Action:
1155E
INVALID ACTION CODE xxxx IN APPLICATION JOB QUEUE ELEMENT
Reason:
An application job queue element had an invalid time action code.
System Action:
The timed action is ignored.
Action:
This is due to a logic error. Notify your software support personnel.
1100 - 1199
1156E
INSUFFICIENT CHECKPOINT SPACE TO QUEUE JOB xxxx IN APPL yyyy FOR SUBMISSION
Reason:
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.
Action:
The checkpoint space situation should be monitored.
1157E
INSUFFICIENT CHECKPOINT SPACE TO NOTIFY APPL MANAGER OF JOB STATUS FOR
JOB <jobname>{(<jobid>)| IN APPLICATION <applname>,<applgen#>} where <jobname> specifies the job name. <jobid> specifies the job identifier. <applname>
specifies the application name. <applgen#> specifies the application generation
number.
Reason:
The tracking processor could not notify the application manager of the change of job
status for a job due to insufficient checkpoint data set space.
System Action:
The application manager may not be notified of job completion.
Action:
The job may have to be manually posted.
1100 - 1199
1158E
ABOVE I/O ERROR OCCURRED WRITING APPL xxxx, GENERATION nn
Reason:
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.
Action:
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
Reason:
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.
Action:
None.
1100 - 1199
1160E
ERROR OCCURRED READING INDEX ENTRY FOR APPL xxxx.nn
Reason:
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.
Action:
The remedial action will depend on the exact nature of the error. Notify your software
support personnel.
1161E
ERROR OCCURRED UPDATING INDEX ENTRY FOR APPL xxxx.nn
Reason:
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
System Action:
The index entry is not updated.
Action:
support personnel.
1100 - 1199
1162E
INVALID REQUEST CODE xxxx PASSED TO APPLICATION MANAGER
Reason:
The application manager was issued a request that was invalid.
System Action:
Action:
This is probably due to a logic error. It could also happen if an older release of the
product is brought up using a checkpoint data set used b a newer release of the
product.
1163E
UNABLE TO LOCATE JOB xxxx FOR RESUBMIT IN APPL yyyy
Reason:
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.
Action:
This is probable an internal logic error. Please notify your software support personnel.
1164W
REQUESTED GENERATION OF APPL xxxx NOT FOUND
Reason:
A user requested action on a job within an Application. The requested Application did
not exist.
System Action:
Action:
1100 - 1199
1165E
JOB xxxx NOT FOUND IN APPL yyyy
Reason:
An application job manipulation command identified a job that was not found for the
requested application.
System Action:
Action:
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
Reason:
An application modification request could not complete as there was insufficient space
to queue the request.
System Action:
Action:
Try the command again later.
1167E
JOB xxxx IS NOT A MEMBER OF AN APPLICATION
Reason:
An application manipulation command was issued for a job that is not part of an
application.
System Action:
Action:
Ensure that the job name/number is specified correctly.
1100 - 1199
1168E
Application request not valid from a proxy subsystem
Reason:
An application processing related request was made to the product. However, the
request is only valid from a master subsystem, and not a proxy subsystem.
System Action:
Action:
Reissue the command from the master address space.
1169E
APPL xxxx GENERATION nn IS NOW SUSPENDED
Reason:
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.
Action:
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
Reason:
This is the control line preceding a display of application file(s) in response to a LISTAPTF
command.
System Action:
The display follows.
Action:
None
1100 - 1199
1171W
APPLID STATEMENT ONLY ALLOWED ONCE
Reason:
An APPLID or APPL statement was encountered more than one time in a procedure. It
should only be specified once, as a Procedure can only define a single application at a
time.
System Action:
The second and subsequent APPL statements are ignored.
Action:
Ensure that only one APPL statement is executed.
1172W
APPLID SPECIFIED FOR JOB xxxx WHICH IS NOT EXTERNAL, IGNORED
Reason:
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.
Action:
Remove the APPLID keyword. One Event can only define a single application.
1173E
INVALID SCOPE TIME xxxx
Reason:
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.
Action:
Correct the statement, using the above guidelines.
1100 - 1199
1174E
DATA SET xxxx IS NOT PARTITIONED
Reason:
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.
Action:
Allocate a partitioned data set and reissue the command.
1175I
JOB TRACKING DEFINITION TABLE LOADED
Reason:
A LOADJTDT command was successfully executed.
System Action:
The new job tracking definition table is now active.
Action:
None.
1176E
COMMAND xxxx INVALID IN JOB TRACKING DEFINITION TABLE
Reason:
A Job Tracking Definition Table contained an invalid command.
System Action:
The Job Tracking Definition Table is not loaded.
Action:
Correct the table and reissue the LOADJTDT command.
1100 - 1199
1177E
ABOVE ERROR OCCURRED OPENING JOB TRACKING DEFINITION TABLE
Reason:
A LOADJTDT command encountered an error allocating or opening a Job Tracking
System Action:
Action:
Ensure the table name was specified correctly and reissue the LOADJTDT command.
1178E
ABOVE ERROR OCCURRED READING JOB TRACKING DEFINITION TABLE
Reason:
An error occurred while reading in a Job Tracking Definition Table. The error is described
System Action:
Action:
After the error is corrected, reissue the LOADJTDT command.
1179E
INVALID COMMAND SYNTAX DETECTED IN LINE nn OF JOB TRACKING DEFINITION
TABLE
Reason:
A Job Tracking Definition Table contained a statement with invalid syntax.
System Action:
Action:
Correct the table definition and reissue the LOADJTDT command.
1100 - 1199
1180E
ABOVE ERROR OCCURRED ON LINE nn OF JOB TRACKING DEFINITION TABLE
Reason:
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:
Action:
Correct the error and reissue the LOADJTDT command.
1181E
INVALID MODEL SPECIFICATION xxxx
Reason:
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.
Action:
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 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.
1100 - 1199
1182E
MODEL SPECIFICATION EXCEEDS 8 CHARACTERS
Reason:
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:
Action:
1183E
INVALID WILDCARD RANGE, xxxx
Reason:
A WILDCARD statement in a Job Tracking Definition Table had an invalid character
range.
System Action:
Action:
1184E
TOO MANY WILDCARDS DEFINED, LIMIT IS 60
Reason:
A Job Tracking Definition Table was being loaded. The table contained more than 60
WILDCARD statements.
System Action:
Action:
1100 - 1199
1185E
xxxx
Reason:
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.
Action:
Take action according to the following message.
1186E
ERROR OCCURRED READING INDEX ENTRY FOR JOB xxxx FOR PRED REQ IN APPL
yyyy.nn
Reason:
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.
Action:
If the external job is complete, it will have to be manually marked complete in the
application.
1100 - 1199
1187E
SADLINK ENTRY xxxx NOT FOUND
Reason:
A SADLINK entry specified on a SADLOAD or SADLINK command. However, no entry with
a matching name could be found.
System Action:
Action:
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
Reason:
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.
Action:
The command should be issued by a user who has update authority to the group owning
the SADLINK.
1100 - 1199
1189E
ABOVE ERROR OCCURRED LOADLINK SADLINK xxxx
Reason:
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.
Action:
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
Reason:
More than 2 notify statements were encountered in a Procedure. The limit is two.
System Action:
The extra notify statement is ignored.
Action:
Refrain from using more than two notify statements. You can combine several notify
requests onto one statement.
1191E
INVALID COMPLETION CONDITION xxxx
Reason:
A RELEASE, AFTER, POSTREQ or PREREQ statement contained a job completion
condition other than 'N', 'U', or 'A'.
System Action:
The procedure is aborted.
Action:
Correct the completion condition.
1100 - 1199
1192I
xxxx
Reason:
message text indicates that the product has submitted a job into the system. The
message text can include the application name or jobnet ID.
System Action:
Action:
None.
1193I
xxxx
Reason:
message text indicates that a submitted job has started to execute. The message text
can include the application name or jobnet ID.
System Action:
Action:
None.
1194I
xxxx
Reason:
message text indicates that a submitted job has ended execution. The message text
includes the completion code and can also include the application name or jobnet ID.
System Action:
Action:
None.
1100 - 1199
1195W
xxxx
Reason:
message text indicates that a 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.
Action:
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)
Reason:
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.
Action:
None. This message is used for documentation.
1197E
POSSIBLE LOOP IN PREDECESSOR/SUCCESSOR RELATIONSHIPS
Reason:
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.
Action:
Correct the job linkages.
1100 - 1199
1198I
NJE TIME TOLERANCE FACTOR SET TO nn, nn
Reason:
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.
Action:
None
1199E
JOB xxxx ALREADY EXISTS IN APPL yyyy
Reason:
System Action:
Action:
1200 - 1299
1200 - 1299
1200E
MODELING IS ACTIVE - RECURSIVE MODEL CALL NOT ALLOWED
Reason:
A MODEL command was issued while model processing is already active. The model
processor may not be called recursively.
System Action:
Action:
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
Reason:
A problem was encountered while parsing a MODEL command.
System Action:
Action:
respectively.
1200 - 1299
1202E
INVALID MODEL START TIME SPECIFIED
Reason:
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:
Action:
Correct the syntax error and reenter the MODEL command.
1203E
ERROR OCCURRED OPENING SCHEDULED ACTIVITY DATA SET xxxx
Reason:
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.
Action:
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
Reason:
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.
System Action:
Action:
None.
1200 - 1299
1205W
MODELING NOT ACTIVE
Reason:
An attempt was made to enter a MODELING command when the MODEL processor not
active.
System Action:
Action:
Issue the MODEL subcommand 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
Reason:
A MAXINITS command was entered but the maximum number of initiators specified was
0.
System Action:
Action:
Specify a maximum number of initiators available on all CPUs in the range 1-999.
1207E
DEFAULT PRIORITY NUMBER OUT OF RANGE
Reason:
The default job priority specified was not in the range 1-15.
System Action:
Action:
Specify a default job priority in the range 1-15 to be assigned to all jobs without a
priority in their JCL.
1200 - 1299
1208E
NO INITIATOR ACTION SPECIFIED
Reason:
An INIT command was entered but no action was specified.
System Action:
Action:
Reenter the INIT command and specify the action you want performed on the initiator
(that is START, SET, STOP).
1209E
NO INITIATOR CLASS(ES) SPECIFIED
Reason:
An INIT command was entered but no initiator class(es) were specified.
System Action:
Action:
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
Reason:
A TIME command specified invalid schedule criteria.
System Action:
Action:
Review the schedule criteria and correct any errors. If the schedule statement contains
separators, then it must be enclosed in quotes.
1200 - 1299
1211E
CONFLICTING KEYWORDS - CPU NUMBER SPECIFIED FOR GLOBAL RESOURCE
Reason:
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:
Action:
Reenter the RESOURCE command without the CPU keyword if you are defining a global
resource.
1212E
RESOURCE CONFLICT - SCOPE MUST BE SAME AS PREVIOUSLY DEFINED
Reason:
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:
Action:
Reenter the RESOURCE command and specify the correct scope.
1200 - 1299
1213E
CPU NUMBER REQUIRED FOR LOCAL RESOURCE
Reason:
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:
Action:
Reenter the RESOURCE command and specify which CPU the resource exists on or is
being defined to.
1214E
ZERO MANUAL TASK SERVERS NOT ALLOWED
Reason:
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:
Action:
Reenter the MAXINITS command and specify one or more server initiators.
1200 - 1299
1215E
ERROR ALLOCATING PRINT FILE FOR xxxx
Reason:
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:
Action:
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
Reason:
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:
Action:
Reenter the MREPORT command with the correct report time criteria. if you have
difficulty in resolving the error with your schedule statement, contact your support
personnel for assistance or remove the FROM keyword from your MREPORT command
(allow default).
1200 - 1299
1217I
nn JOBS READ FROM SCHEDULED ACTIVITY DATASET
Reason:
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.
System Action:
Action:
None.
1218E
ERROR READING SCHEDULED ACTIVITY FILE
Reason:
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.
Action:
Retry model processing after the problem is diagnosed and corrected.
1219I
NO REPORTS REQUESTED - MODEL PROCESSING TERMINATED
Reason:
The ENDMODEL command detected that no modeling reports were requested.
System Action:
Model processing is terminated.
Action:
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
using the MREPORT command.
1200 - 1299
1220W
INITIATOR nn NOT DEFINED
Reason:
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:
Action:
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
Reason:
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:
Action:
None. There is no need to start an active initiator.
1222W
INITIATOR nn IN DRAINED STATUS
Reason:
An INIT SET command was issued against a drained initiator. Only started initiators may
be altered by an INIT SET command.
System Action:
Action:
Issue an INIT START command to activate the initiator with the desired options.
1200 - 1299
1223E
RESOURCE xxxx NOT DEFINED
Reason:
A RESOURCE command was issued to alter, delete or model a resource which was not
previously defined to the model processor.
System Action:
Action:
Correct the RESOURCE name or define the resource to the model processor using a
RESOURCE ADD command.
1224E
MAXIMUM NUMBER OF RESOURCES EXCEEDED
Reason:
A RESOURCE command attempted to add to or set the count of a resource to more than
1000 megs.
System Action:
Action:
Reenter the command and ensure the maximum allowable number of resources is not
exceeded.
1225E
NO EXECUTION CLASS FOUND FOR JOB xxxx
Reason:
This is an internal error condition occurring at job end. It may affect model processing
and should be reported.
System Action:
Action:
Report the message to your support personnel.
1200 - 1299
1226E
PROCESSING TERMINATED FOR MODEL REPORT xxxx
Reason:
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.
Action:
Restart the modeling process after the problem is diagnosed and corrected.
1227E
NO RESOURCES FOUND FOR REPORT xxxx
Reason:
A resource utilization by system report (RR1) was requested but no resources were
defined to the model processor to report on.
System Action:
Action:
Define some resources to the model processor using the RESOURCE command or do not
request this report.
1228E
INSUFFICIENT DATA WIDTH ON REPORT xxxx
Reason:
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:
Action:
Review the modeling documentation to determine the minimum required data width
for this report.
1200 - 1299
1229E
INVALID ADJUSTMENT PERCENTAGE FACTOR
Reason:
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:
Action:
Reenter the command specifying an execution or CPU adjustment percentage factor of
greater than -100%.
1230E
ERROR ALLOCATING REPORT FORMAT WORKFILE DURING REPORT xxxx PROCESSING
Reason:
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.
Action:
Restart the report after diagnosing and correcting the error. If the problem persists,
contact your support personnel.
1200 - 1299
1231E
ERROR OPENING REPORT FORMAT WORKFILE DURING REPORT xxxx PROCESSING
Reason:
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.
System Action:
Action:
1232E
ERROR WRITING TO REPORT FORMAT WORKFILE DURING REPORT xxxx PROCESSING
Reason:
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.
System Action:
Action:
1200 - 1299
1233E
BUFFER LENGTH ERROR DURING REPORT xxxx PROCESSING
Reason:
This is an internal error condition which occurred while processing the specified logical
report name.
System Action:
Action:
Contact your support personnel to report the problem.
1234E
ERROR READING REPORT FORMAT WORKFILE DURING REPORT xxxx PROCESSING
Reason:
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.
System Action:
Action:
1235E
CPU NUMBER OUT OF RANGE
Reason:
The INIT or RESOURCE statement specified a CPU number of 8 or 9. The maximum CPU
number allowed is 7.
System Action:
The INIT or RESOURCE statement is ignored.
Action:
Correct the INIT or RESOURCE statement and re-issue the request.
1200 - 1299
1236E
Mailbox <box name> is not defined
Reason:
A message was addressed to a mailbox that is not defined in notification list.
System Action:
The message is discarded.
Action:
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
Reason:
The preceding message describes the error.
System Action:
Sending of the email message is aborted.
Action:
See the preceding message.
1238I
Notification list loaded/tested, (no) errors found
Reason:
This is a response to a LOADNL command used to load or test a notification list.
System Action:
The list was loaded.
Action:
None.
1200 - 1299
1239I
Notification list active, loaded from <data set name>
Reason:
A new notification list has been loaded from the indicated source as a result of a
LOADNL command.
System Action:
The list is active.
Action:
None.
1240I
MODEL PROCESSING COMPLETE
Reason:
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.
Action:
None.
1241E
ERROR OPENING SCHEDULED ACTIVITY DATASET FOR UPDATE
Reason:
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.
Action:
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.
1200 - 1299
1242I
MODEL PROCESSING BEGINS AT xxxx ON yyyy
Reason:
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.
Action:
None.
1243E
Missing Agent Definition Table Data Set Name
Reason:
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.
Action:
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
Reason:
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.
Action:
Contact CA Support.
1200 - 1299
1245E
Missing data set name for notification list
Reason:
A LOADNL command was entered without a data set name, and no prior name is known
to the product.
System Action:
Action:
Reenter the command with data set name on it.
1246E
Above error occurred opening notification list
Reason:
The data set name specified on a LOADNL command could not be opened. The
preceding message describes the error.
System Action:
Action:
Correct the data set name in error and retry.
1247E
Above error occurred reading notification list
Reason:
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.
Action:
N/A
1200 - 1299
1248E
Invalid command syntax detected in line <number> of notification list
Reason:
An erroneous statement was found in notification list.
System Action:
Action:
Correct the error in the list.
1249E
Command <cmdname> invalid in notification list
Reason:
The indicated statement is not allowed in notification list.
System Action:
Action:
Correct the error.
1250E
UNABLE TO TRANSMIT JOB TRACKING DATA TO xxxx, DESTINATION NOT DEFINED
Reason:
The product was attempting to transmit tracking data to a destination defined by an
XMITMDL statement. The destination was not defined using a TPAPPL statement.
System Action:
The tracking data are not transmitted.
Action:
Correct the XMITMDL statement, or add a TPAPPL definition.
1200 - 1299
1251I
ESP CHKPT THRESHOLD EXCEEDED, WAITING FOR CHKPT SPACE FOR INTER SYSTEM
DATA
Reason:
The product is waiting for space to become available on the checkpoint file.
System Action:
ESP waits.
Action:
None.
1253E
You are not permitted to issue verb xxxx to Agent yyyy
Reason:
You have attempted to issue a message to an 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:
Action:
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.
1200 - 1299
1254W
Cache could not be activated for dddd. Macro mmm RC=rrr Reason=sss
Reason:
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.
Action:
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.
Reason:
The CACHE operand on APPLFILE or TRAKFILE statement was specified with a value of
nnn which is invalid. The product substituted the value of mmm.
System Action:
A cache will be created with size of mmm megabytes.
Action:
To avoid this message, specify a cache size within 0-2000 range.
1200 - 1299
1256E
Slot number nnnn invalid (XX op)
Reason:
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:
Action:
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 your software support personnel for
further assistance, reporting the value of XX.
1258W
NetNode xxxx already defined for tracking model yyyy, ignored
Reason:
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.
Action:
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.
1200 - 1299
1259E
MODEL, NODE and/or NETNODE invalid with XMITMDL LIST
Reason:
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.
Action:
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=<rc>, CSA, Address=<address>, Length=<length>, Subsystem=<ssid>
Reason:
The explicit data set trigger notification utility program ESPDST (alias CYBESDT1)
attempted unsuccessfully to verify the validity of the specified subsystem's
communication area in CSA while processing an explicit data set trigger notification.
<rc> - specifies the address verification service (VSMLOC) return code.
<address> - specifies the address of the CSA communication area.
<length> - specifies the hexadecimal length the CSA communication area.
<ssid> - specifies the subsystem identifier.
System Action:
The explicit data set trigger notification is not processed by the subsystem <ssid>.
Program ESPDST (alias CYBESDT1) terminates with an error return code.
Action:
Should never happen. Call CA Support.
1200 - 1299
1261E
GDS number <condition>, GDG=<dsname>
Reason:
The explicit data set trigger notification utility program ESPDST (alias CYBESDT1) or the
DSTRIG ACTIVATE command sent an explicit data set trigger notification to a target
subsystem whose EXPDSTRG data set authentication level is set to SECURE or VERIFY.
The explicit data set trigger notification specified a GDG base <dsname>. Either no GDS
generation number, or an invalid GDS generation number <number>, or a GDS
generation number <number> (adjusted by GDS bias value if present) lower than the
earliest existing generation number, was specified. <condition> specifies one of the
following - missing {+|-}<number> invalid {minus bias value } -<number> below earliest
generation
System Action:
The explicit data set trigger notification is rejected by the target subsystem. Program
ESPDST (alias CYBESDT1) terminates with an error return code.
Action:
Re-execute program ESPDST (alias CYBESDT1) or re-issue the DSTRIG ACTIVATE
command specifying a valid GDS generation number <number> for GDG base
<dsname>.
1200 - 1299
1262E
CYB1262E Entry <entry> not found in catalog
Reason:
While the specified data set was being verified, a catalog search for entry <entry> failed.
<entry> may be the name of the specified explicit trigger data set, or it may be the name
of an entry related to the specified data set that is expected to be present in the catalog.
This condition occurs when the specified explicit trigger data set does not exist or is not
on the specified volume.
System Action:
Action:
If the specified explicit trigger data set exists but is not cataloged, re-execute program
ESPDST (alias CYBESDT1) or re-issue the DSTRIG ACTIVATE command specifying the
VOLSER(<volume>) or VOLUME(<volume>) input parameter, where <volume> specifies
the serial number of the volume that the specified data set resides on. If the specified
explicit trigger data set does not exist, re-execute program ESPDST (alias CYBESDT1)
specifying DSNAME(<dsname>) or DATASET(<dsname>), or re-issue the DSTRIG
ACTIVATE command specifying <dsname>, where <dsname> is the name of a data set
that exists.
1200 - 1299
1263E
OBTAIN error, {<reason>|RC=<rc>, Dsname=<dsname>, Volser=<volser>}
Reason:
While the specified data set was being verified, an error occurred issuing a format 1
DSCB OBTAIN to determine if data set <dsname> resides on volume <volser>.
<reason> - specifies the reason for the OBTAIN error, and can be one of the
following
I/O error or invalid format 1 DSCB, Dsname=<dsname>, Volser=<volser>
Invalid work area pointer, Dsname=<dsname>, Volser=<volser>
<rc> - specifies the OBTAIN error return code if the error reason is unknown.
<dsname> - specifies the input data set name.
<volser> - specifies the input volume serial number, if specified, else the volume
serial number in the catalog entry for the input data set.
System Action:
Action:
Attempt to determine the cause of the problem according to the error message text,
and re-execute program ESPDST (alias CYBESDT1) or re-issue the DSTRIG ACTIVATE
command with the correct data set and (optionally) volume specification(s).
1200 - 1299
1264E
RACROUTE REQUEST=AUTH error, RC=<saf_rtn>-<racf_rtn>/<racf_rsn>,
{Dsname|Alias}=<dsname>{, Volser=<volser>}
Reason:
The ESP explicit data set trigger notification utility program ESPDST (alias CYBESDT1) or
the DSTRIG ACTIVATE command sent an explicit data set trigger notification to a target
ESP subsystem whose EXPDSTRG data set authentication level is set to SECURE or
SECURE(NOVERIFY). A SAF (RACROUTE) authorization request was issued to determine if
the owning user has update access to the specified explicit trigger data set <dsname>,
on volume <volser>, if the volume serial number has been determined. The
authorization request failed.
<saf_rtn> specifies the SAF return code.
<racf_rtn> specifies the RACF return code.
<racf_rsn> specifies the RACF reason code.
System Action:
The explicit data set trigger notification is rejected by the target ESP subsystem.
Program ESPDST (alias CYBESDT1) terminates with an error return code.
Action:
If the user should be permitted update access to data set <dsname>, then add the
permission to the security subsystem.
Then re-execute program ESPDST (alias CYBESDT1) or re-issue the DSTRIG ACTIVATE
command to send an explicit data trigger notification for data set <dsname>.
1200 - 1299
1265E
{Cataloged d|D}ata set <dsname> {volume <volser> not mounted | not on volume
<volser>}
Reason:
While the specified data set was being verified, an error occurred issuing a format 1
DSCB OBTAIN to determine if data set <dsname> resides on volume <volser>. Either
volume <volser> was not mounted or data set <dsname> does not reside on volume
<volser>.
<dsname> - specifies the input data set name.
<volser> - specifies the input volume serial number, if specified, else the volume
serial number in the catalog entry for the input data set.
System Action:
Action:
Determine the cause of the problem according to the error message text, and
re-execute program ESPDST (alias CYBESDT1) or re-issue the DSTRIG ACTIVATE
command, specifying the correct data set name <dsname> and (if required) volume
serial number <volser>.
1200 - 1299
1266I
Explicit data set trigger for <dsname> {(<gdsnum>){(<bias>)}} sent to ESP subsystem
<ssid>
Reason:
The explicit data set trigger notification utility program ESPDST (alias CYBESDT1) sent an
explicit data set trigger notification for data set <dsname> to subsystem <ssid>. For a
GDS, if subsystem <ssid>'s EXPDSTRG data set authentication level is set to SECURE or
VERIFY and the GDS has been verified, <dsname> gives the fully qualified GDS data set
name, <gdsnum> gives the relative generation number and <bias>, if specified, gives the
GDS bias value.
System Action:
If a matching explicit data set trigger definition exists for the specified explicit data set
trigger, then subsystem <ssid> performs the action specified by the explicit data set
trigger. If no matching explicit data set trigger definition exists for the specified explicit
data set trigger, then no action is taken.
Action:
None.
1267E
Subsystem <ssid> not {found|{an|a tracking} ESP}
Reason:
The explicit data set trigger notification utility program ESPDST (alias CYBESDT1),
verifying the specified subsystem <ssid>, determined that it either does not exist, is not
a subsystem, or is not a tracking subsystem. A tracking subsystem is one whose
ESPPARM initialization file does not contain the following statement - SMFINT OFF Note
that if subsystem <ssid> is not found but is a valid tracking subsystem, then subsystem
<ssid> has not executed since the system was IPL'd.
System Action:
The explicit data set trigger is not processed. Program ESPDST (alias CYBESDT1)
terminates with an error return code.
Action:
If the specified subsystem was not found, but is a valid tracking subsystem, then start
the product before re-executing program ESPDST (alias CYBESDT1). Otherwise
re-execute program ESPDST (alias CYBESDT1) specifying a tracking subsystem in the
SUBSYSTEM or SSID start-up parameter.
1200 - 1299
1268E
CSI error, <description>
Reason:
The explicit data set trigger notification utility program ESPDST (alias CYBESDT1) or
While the specified data set was being verified, a catalog search failed for either the
specified data set or an entry related to the specified data set. <description> describes
the reason for the CSI (Catalog Interface Search) error.
System Action:
Action:
Attempt to determine the cause of the problem according to the error message text,
and re-execute program ESPDST (alias CYBESDT1) or re-issue the DSTRIG ACTIVATE
command with the correct data set specification.
1269W
APPLICATION STATEMENT MISSING
Reason:
A SUBAPPL statement was found in a procedure, however, no preceding 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.
Action:
Either insert an APPL statement, or remove the SUBAPPL statement from the procedure.
1200 - 1299
1270E
THE SCOREBOARD IS NOT ACTIVE
Reason:
A scoreboard related request was made to the subsystem. However, the scoreboard
was not active.
System Action:
Action:
Activate the scoreboard.
1271E
ABOVE ERROR OCCURRED LOADING SCOREBOARD FROM SCHEDULE FILE
Reason:
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.
Action:
This depends on the I/O error encountered. When the data set is restored, you can
shutdown the product and restart it to reload the scoreboard.
1272I
nn ENTRIES ADDED TO SCOREBOARD
Reason:
This message is issued when a LOADSCHF command has completed loading the
schedfile/scoreboard from a scheduled activity data set.
System Action:
Action:
None.
1200 - 1299
1273C
Control Block Addresses:
Reason:
In response to a DCBADDR command, the addresses of various control blocks were
listed.
System Action:
None.
Action:
None.
1274C
DSTRIG exclude list:
Reason:
In response to a LDTREL command, the Data Set Trigger Exclude List entries have been
listed. The entries follow this message.
System Action:
None.
Action:
None.
1275W
The TRACK_MANUAL option has been withdrawn
Reason:
The TRACK_MANUAL or NOTRACK_MANUAL keyword was specified as an option within
a Procedure. This option has been withdrawn starting with release 4.3.0.
System Action:
The keyword is ignored.
Action:
You should remove the keyword from the OPTIONS statement in the procedure. Jobs
that are manually submitted should be identified with the MANUAL keyword.
1200 - 1299
1276I
Subappl xxxx now complete in Appl yyyy.nn
Reason:
A Subappl of an 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.
Action:
None.
1277W
DFPNODE NOT AVAILABLE WHEN SAF SECURITY ACTIVE
Reason:
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 a USERDEF entry.
System Action:
Action:
You will have to explicitly specify the PNODE name on a POST command.
1278W
PNODE NAME MISSING
Reason:
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:
Action:
Specify the name of the PNODE from which you want to post the job.
1200 - 1299
1279W
JOB xxxx IN APPL zzzz LATE START TIME EXCEEDED
Reason:
A job has missed its late start time. The late start time was defined by the user defining
the job to the system.
System Action:
Action:
You should investigate why JES has not started the job yet.
1280I
No DSTRIG exclude entries are defined
Reason:
A LDTREL command was entered to list the Data Set Trigger Exclude List entries. It was
determined no such entries exist.
System Action:
None.
Action:
None.
1281I
DSTRIG exclude entry xxxx {not} deleted
Reason:
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.
Action:
None.
1200 - 1299
1282E
HELD_MANUAL specification invalid, {TRACKOPT HELD_MANUAL not set| Currently
not supported under JES3}
Reason:
An application OPTIONS, JOB or JOBATTR command in a procedure specifies the
HELD_MANUAL operand. However, the held manual job facility is not enabled, either
because the ESPPARM initialization file TRACKOPT command does not specify the
HELD_MANUAL operand, or because JES3 is the job entry subsystem.
System Action:
The event that invoked the procedure with the application OPTIONS, JOB or JOBATTR
command, specifying the HELD_MANUAL operand, fails.
Action:
If the error occurred because the ESPPARM initialization file TRACKOPT command does
not specify the HELD_MANUAL operand, then add the HELD_MANUAL operand to the
TRACKOPT command in the ESPPARM initialization file(s) of all CA WA ESP Edition
subsystems, and restart all CA WA ESP Edition subsystems. If the error occurred because
JES3 is the job entry subsystem, then the held manual job facility is not currently
supported, and the HELD_MANUAL operand must be removed from the application
OPTIONS, JOB or JOBATTR command.
1283W
Held manual job <jobname> in application <applname>.<applgen#>
Reason:
A held manual job was encountered in an application during CA WA ESP Edition
Subsystem master initialization. However, the held manual job facility is no longer
enabled.
System Action:
Action:
If the held manual job facility was deliberately disabled by removing the HELD_MANUAL
operand of the TRACKOPT command in the ESPPARM initialization file, then the held
manual job can only be completed by the APPLJOB <jobspec> COMPLETE command or
the C line command in CSF. If the held manual job facility was inadvertently disabled by
removing the HELD_MANUAL operand of the TRACKOPT command in the ESPPARM
initialization file, then restore it in all CA Workload Automation subsystems, and restart
all CA Workload Automation subsystems.
1200 - 1299
1284W
<nnn> pending held job{s}, TRACKOPT HELD_MANUAL not set
Reason:
A count of <nnn> held manual jobs were encountered in applications during CA WA ESP
Edition Subsystem master initialization. However, the held manual job facility is no
longer enabled.
System Action:
Action:
If the held manual job facility was deliberately disabled by removing the HELD_MANUAL
operand of the TRACKOPT command in the ESPPARM initialization file, then held
manual jobs can only be completed by the APPLJOB <jobspec> COMPLETE command or
the C line command in CSF. If the held manual job facility was inadvertently disabled by
removing the HELD_MANUAL operand of the TRACKOPT command in the ESPPARM
initialization file, then restore it in all CA Workload Automation subsystems, and restart
all CA Workload Automation subsystems.
1285E
Cannot resubmit held manual job that is not submitted, started, ended or failed
Reason:
An attempt was made to restart a manual held job in an application using the APPLJOB
<jobspec> RESTART command or the R line command in CSF. However, the held manual
job has not yet been submitted or completed.
System Action:
The APPLJOB <jobspec> RESTART command or the R line command in CSF is ignored.
Action:
None.
1200 - 1299
1286E
HELD_MANUAL specification invalid, held manual job facility not enabled
Reason:
An attempt was made to insert a held manual job into an active application using the
APPLJOB <jobspec> INSERT HELD_MANUAL command or the IJ line command in CSF,
specifying H in the ISPF prompt panel.
System Action:
The APPLJOB <jobspec> INSERT HELD_MANUAL command or the IJ line command in
CSF, specifying H in the ISPF prompt panel, is ignored.
Action:
None.
1287E
Error reading/writing TRAKFILE for released job <jobname>(<jobid>)
Reason:
A job tracking record, notifying that a job is awaiting execution, was being updated
when an I/O error occurred on the TRAKFILE date set. The I/O error is described by a
preceding message.
System Action:
If the job awaiting execution is a held manual job that was previously in a held state,
then the held manual job's released state will not be updated in its application.
Action:
Attempt to determine the cause of the TRAKFILE data set I/O error. Once the I/O error is
corrected, if the affected job awaiting execution is a held manual job that was
previously in a held state, then the job can be manually "re-released" by issuing an
APPLJOB <jobspec> RELEASE(JES) command or a $A line command in CSF. If unable to
determine the cause of the TRAKFILE data set I/O error, call CA Support.
1200 - 1299
1288W
Held manual job <jobname>(<jobid>) not released
Reason:
A JES release command was issued unsuccessfully for a submitted held manual job in an
application
System Action:
The JES release command is re-issued for the held manual job.
Action:
None.
1289E
Held manual job <jobname>(<jobid>) not released
Reason:
A JES release command was issued four times unsuccessfully for a held manual job in an
application.
System Action:
The JES release command is re-issued every 30 seconds for the held manual job until it is
either successful or the job completes.
Action:
Investigate the cause of the JES release command failures and attempt to correct it.
1290E
Open failed, SHR specified for data set with no DVSI, Dsn=<data.set.name>
Reason:
An attempt to open CA WA ESP Edition VSAM KSDS (Key Sequenced Data Set)
<data.set.name> failed because the SHR (share) attribute was requested, but the data
set does not support sharing, as its first record is not a DVSI, an internal CA WA ESP
Edition structure used to serialize CA WA ESP Edition VSAM KSDS files across systems.
System Action:
The VSAM KSDS OPEN failed and the data set cannot be processed.
1200 - 1299
Action:
This problem should not occur under normal operating conditions, but if it does, then
request that the VSAM KSDS be opened non-shared, if possible. If not, then call CA
support.
1291E
Above error occurred on line <number> of notification list
Reason:
This message describes the location of an error in the notification list being read by a
LOADNL command.
System Action:
Action:
Correct the error.
1292E
Wildcards are not allowed in mailbox name
Reason:
A mailbox name in a notification list contains wildcard characters.
System Action:
Action:
Correct the error.
1200 - 1299
1293E
Mailbox <name> already exists
Reason:
A duplicate mailbox name was found in a notification list.
System Action:
Action:
Correct the error.
1294E
Subscription out of order: no mailbox defined
Reason:
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:
Action:
Correct the error.
1295I
No matching mailboxes found
Reason:
A MAILBOX command found no mailboxes matching the name provided in the
command.
System Action:
Action:
Correct the mailbox name.
1200 - 1299
1296C
Mailbox display
Reason:
This is a heading of a multiline console message issued in response to MAILBOX
operator command.
System Action:
N/A
Action:
N/A
1297E
GDS number specification invalid, <dsname> not a GDG
Reason:
DSTRIG ACTIVATE command sent an explicit data set trigger request to a target
subsystem specifying a <dsname>(<gdsnumber>) parameter where <dsname> is a data
set name and <gdsnumber> is a GDS generation number. However, data set <dsname>
is not a GDG base.
System Action:
The explicit data set trigger notification is ignored. Program ESPDST (alas CYBESDT1)
Action:
Re-execute program ESPDST (alias CYBESDT1) or re-issue the DSTRIG ACTIVATE
command specifying a valid GDG base data set name with a GDS number or a non-GDG
data set name without a GDS generation number.
1200 - 1299
1298C
EXPDSTRG Command Options
Reason:
Response to EXPDSTRG HELP command.
System Action:
Action:
None.
1299I
Explicit Data Set Trigger Authentication Level: Secure|Verify|NoVerify
Reason:
Response to EXPDSTRG {LIST|SECURE|VERIFY|NOVERIFY} command.
System Action:
Action:
None.
1400 - 1499
1400 - 1499
1400E
CHECKPOINT GETMAIN ERROR - X'xxxx'
Reason:
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 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 subsystem.
Action:
Ensure there is enough REGION specified for the subsystem. Increase the REGION
specification on the EXEC card and restart the product.
1401I
OPEN_LU REQUEST RECEIVED
Reason:
This is an informational message, indicating that the system received a request to open
an LU.
System Action:
Go to open a VTAM ACB.
Action:
None.
1400 - 1499
1402I
A NON-CPE CONVERSATION WAS STARTED
Reason:
This is an informational message, indicating as stated.
System Action:
None.
Action:
None.
1403E
xxxx
Reason:
An error happened when the system tried to open the TRACELOG. This messages
provides details of the open error.
System Action:
Trace information could not be logged.
Action:
Investigate on the error message and correct the problem.
1404W
UNABLE TO CLOSE ACB - ERROR = X'xxxx'
Reason:
The TpServer encountered an error when attempting to close the ACB for the partner
logical unit. "xx" is the VTAM OPEN error code as found in the manual entitled "VTAM
Programming"
System Action:
None.
Action:
None.
1400 - 1499
1405W
CNOS FAILURE WITH xxxx
Reason:
CNOS failed during the TP Server initializing an application due to APPC error.
System Action:
This application can not be started.
Action:
Solve APPC problem and retry TPAPPL START.
1406W
Reason:
CNOS failed during the TP Server initializing an application due to VTAM error.
System Action:
This application can not be started.
Action:
Solve VTAM problem and retry TPAPPL START.
1407I
CYBERMATION TP SERVER STARTED FOR xxxx
Reason:
TP Server with partner xxxx is initialized and started.
System Action:
None.
Action:
None.
1400 - 1499
1409W
at SND99999 with TPRE=0
Reason:
Obsolete Message.
System Action:
.
Action:
.
1410W
SEND IS DEALLOCATING A CONV
Reason:
Obsolete Message.
System Action:
.
Action:
.
1411E
SEND TO xxxx FAILED Reason:
Obsolete Message.
System Action:
.
Action:
.
1400 - 1499
1412E
Obsolete Message.
System Action:
.
Action:
.
1413W
TRANSACTION xxxx NOT DEFINED TO THIS APPLICATION
Reason:
Obsolete Message.
System Action:
.
Action:
.
1414W
TP Application xxxx not defined
Reason:
Obsolete Message.
System Action:
.
Action:
.
1400 - 1499
1415I
CHECKPOINT MANAGER SHUTDOWN COMPLETE
Reason:
Obsolete Message.
System Action:
.
Action:
.
1416I
CHECKPOINT AREA SIZE =
Reason:
Obsolete Message.
System Action:
.
Action:
.
1417I
DATA SET IS EMPTY - CLEAR PROCESSING INITIATED
Reason:
Obsolete Message.
System Action:
.
Action:
.
1400 - 1499
1418E
CHECKPOINT CONTAINS INVALID DATA Reason:
Obsolete Message.
System Action:
.
Action:
.
1419I
TP SERVER CHECKPOINT FORMAT COMPLETE
Reason:
Obsolete Message.
System Action:
.
Action:
.
1420I
APPLICATION xxxx NOT ACTIVE - CONNECTION DEFERRED
Reason:
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 labeled "Return Codes". "xxxx" corresponds to the field
RPL6RCPR and "yyyy" corresponds to the field RPL6RCSC.
System Action:
Action:
Insure that the destination application is active before issuing the command.
1400 - 1499
1421W
Reason:
A communications failure occurred with the partner.
System Action:
The connection fails.
Action:
Ensure the partner is present and active.
1422I
Application xxxx not active - connection deferred
Reason:
The desired application is not active.
System Action:
The connection is deferred.
Action:
Ensure that the application is present and active.
1423I
TP SERVER LU OPENED SUCCESSFULLY
Reason:
Communication is successful.
System Action:
None.
Action:
None.
1400 - 1499
1424I
TP CHECKPOINT DATA SET NAME IS xxxx
Reason:
The name of the checkpoint dsn is displayed.
System Action:
None.
Action:
None.
1425W
TP SERVER LU already active
Reason:
The server LU was found active during an activation attempt.
System Action:
None.
Action:
None.
1426W
TP SERVER feedback code xxxx
Reason:
The TP SERVER LU was attempted to be activated.
System Action:
Displays the error (feedback) code.
Action:
Determine from the feedback code.
1400 - 1499
1427I
APPLICATION STATUS DISPLAY
Reason:
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:
Action:
None required.
1428E
COMMAND PROCESSING ERROR - TP FEEDBACK = X'xxxx'
Reason:
The message indicates TPAPPL command failure, xxxx is a number of remaining
conversations.
System Action:
The communication initiation attempt failed.
Action:
Verify communication status and retry.
1400 - 1499
1429I
TP SERVER IS NOT ACTIVE
Reason:
The TP server stopped for debugging purposes. The message indicating that we are in
debug mode simulating timeout request. The 1430I message is coming right after to
confirm it.
System Action:
The TP Server debug mode taking place.
Action:
Check the 1430I presents and proceed with required testing.
1430I
TIMEOUT DEBUG TEST MODE SET
Reason:
The message is coming right after the 1429I message staying that TP Server is down
now. The message indicating that we are in debug mode simulating timeout request.
System Action:
The TP Server debug mode taking place.
Action:
Proceed with required testing.
1431I
LOST I/O TIME INTERVAL SET
Reason:
The message is coming in response to TPTIME nn command. The message indicating
that the lost I/O time interval has been set.
System Action:
None.
Action:
None.
1400 - 1499
1432I
Automatic retry for appl xxxx not active
Reason:
The TPRETRY command sets and displays the interval at which attempts will be made to
contact an LU that is down. If no value specified, the current value is displayed. If the
current value is 0, then this message is coming out.
System Action:
None.
Action:
None.
1433I
Automatic retry for appl xxxx currently set to nnyyyy
Reason:
The TPRETRY command sets and displays the interval at which attempts will be made to
contact an LU that is down. If no value has been specified with TPRETRY command then
the current value is displayed as nnyyyy in this message.
System Action:
None.
Action:
None.
1434W
TP Application xxxx not defined
Reason:
The message is coming in response to TPRETRY command, when the application it is
referencing to is not defined.
System Action:
Command terminated.
Action:
Check the application name and retry.
1400 - 1499
1435I
NO TRANSACTIONS HELD
Reason:
The message is coming out in response to TPAPPL with delete, show or release
transaction request, if no held transaction is present.
System Action:
None.
Action:
None.
1436E
The attempt to send data to application xxxx has failed, due to VTAM error.
System Action:
Deallocate the conversation.
Action:
Check VTAM error code and try later.
1437I
THE SERVER IS NOT ACTIVE
Reason:
The server is not running.
System Action:
None.
Action:
Activate the server if needed.
1400 - 1499
1438E
DIV IDENTIFY ERROR RETCODE = xxxx REASON = zzzz
Reason:
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.
Action:
Using the appropriate IBM manual, which will have a title like 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
Reason:
The APPC error during the SEND to TPPD.
System Action:
The system retries conversation.
Action:
None.
1400 - 1499
1440I
CONVERSATION ADDED
Reason:
The message is coming out in response on TPAPPL ADDCONV command. The new
conversation was added successfully.
System Action:
Proceed conversation.
Action:
None.
1441I
CONVERSATION DELETED
Reason:
The message is coming out in response on TPAPPL DELCONV command. The
conversation has been successfully removed.
System Action:
Conversation removed.
Action:
None.
1442W
LU xxxx IS NOT ACTIVE
Reason:
OPEN VTAM file failure, application not active.
System Action:
None.
Action:
Check LU definition. TPSTART command will cause a retry.
1400 - 1499
1443E
SETLOGON FAILED
Reason:
VTAM SETLOGON failure.
System Action:
None.
Action:
Check VTAM RPL code. TPSTART command will cause a retry.
1444E
GETMAIN FOR BELOW THE LINE STORAGE FAILED
Reason:
TP server initialization failed due to lack of storage in the region.
System Action:
Initialization failed.
Action:
Verify that there is sufficient storage in the region.
1445E
TRANSACTION DOES NOT EXIST
Reason:
TPTRAN command unable to locate the transaction specified.
System Action:
Command terminated.
Action:
Verify transaction ID using TPDISP and retry.
1400 - 1499
1446E
TPALIAS COMMAND FAILED - TPAR FEEDBACK = X'xxxx'
Reason:
TPALIAS command failed, invalid verb used.
System Action:
Command terminated.
Action:
Check the syntax and try again.
1447E
A TRANSACTION AND APPLICATION NAME MUST BE PROVIDED
Reason:
TPALIAS command failed, transaction or application name is missing.
System Action:
Command terminated.
Action:
Check the syntax and try again.
1448E
UNABLE TO LOAD MODULE xxxx
Reason:
TPATTACH command failed, module xxxx not found.
System Action:
Command terminated.
Action:
Verify module existence and retry.
1400 - 1499
1449E
UNABLE TO LOAD MODULE xxxx
Reason:
TPTRAN command failed, module xxxx not found.
System Action:
Command terminated.
Action:
Verify module existence and retry.
1450I
APPLICATION xxxx
Reason:
Application xxxx is now connected.
System Action:
Conversation request succeed.
Action:
None.
1451I
APPLICATION xxxx
Reason:
Incoming application xxxx is now connected
System Action:
Incoming conversation request succeed.
Action:
None.
1400 - 1499
1452E
APPLICATION START FAILED - TP SERVER IS STOPPING
Reason:
The application start failed, because of CNOS VTAM or APPC failure.
System Action:
TP Server is stopping.
Action:
Verify VTAM definitions and retry with TPSTART.
1454W
VTAM IS NOT ACTIVE
Reason:
OPEN VTAM file failure, VTAM is not active.
System Action:
None.
Action:
Verify VTAM status. TPSTART command will cause a retry.
1455I
TP SERVER AWAITING CHECKPOINT INITIALIZATION
Reason:
The message is being issued during TP Server initialization time if TP checkpoint file is
not initialized yet.
System Action:
Wait until initialization completes, then continue.
Action:
None.
1400 - 1499
1456S
THE TP SERVER CHECKPOINT IS FULL
Reason:
There is no space to queue a new none-conversational transaction.
System Action:
Request terminated.
Action:
Wait until the DEQUEUE process cleans it up and try again. If it happen to often, the file
size can be reconsidered.
1457W
Reason:
CNOS failed during Application initialization due to APPC error.
System Action:
The attempted communication failed.
Action:
Verify the APPC status and try TPAPPL START later.
1458W
TP SERVER LU OPEN FAILED
Reason:
The TPSTART command fails trying to reopen VTAM ACB.
System Action:
Command terminated.
Action:
Check definitions and retry later.
1400 - 1499
1459I
RESUMED TRANSACTION ERROR OCCURRED, FEEDBACK CODE = xxxx
Reason:
An error has occurred while resuming checkpointed transactions.
System Action:
None.
Action:
None.
1460E
DIV ACCESS ERROR RETCODE = xxxx REASON = zzzz
Reason:
The TP Server issued a DIV ACCESS request, but the return code from the operating
System Action:
Action:
should uniquely ACCESS the problem, and indicate a response. The codes are
1461E
CKPT ALLOCATION ERROR - X'xxxx'
Reason:
An error occurred during a dynamic allocation request. S99 error code is X'xxxx'
System Action:
TP server is stopping.
Action:
Verify TP checkpoint file allocation.
1400 - 1499
1462E
DIV MAP ERROR RETCODE = xxxx REASON = zzzz
Reason:
The TP Server issued a DIV MAP 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:
Action:
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.
1463E
DIV UNMAP ERROR RETCODE = xxxx REASON = zzzz
Reason:
The TP Server issued a DIV UNMAP request, but the return code from the operating
System Action:
Action:
should uniquely UNMAP the problem, and indicate a response. The codes are
1400 - 1499
1464E
DIV SAVE ERROR RETCODE = xxxx REASON = zzzz
Reason:
The TP Server issued a DIV SAVE request, but the return code from the operating system
System Action:
Action:
should uniquely SAVE the problem, and indicate a response. The codes are documented
situation.
1465I
CONNECTION WITH APPLICATION xxxx HAS BEEN REMOVED
Reason:
A TP server connection that is related to the specific partner application has been
released.
System Action:
N/A.
Action:
N/A.
1400 - 1499
1466I
nn TRANSACTION(S) RELEASED FOR xxxx
Reason:
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.
Action:
None.
1467I
xxxx TRANSACTIONS DELETED FOR yyyy
Reason:
There are specified numbers of transactions deleted as per requested. The transaction
name is yyyy.
System Action:
N/A.
Action:
N/A.
1468E
UNABLE TO OPEN ACB - ERROR = X'xxxx'
Reason:
An error was encountered during checkpoint processing initialization. A bad return code
was received from a call to OPEN ACB. The return code from OPEN is displayed in the
message. The meaning of this return code can be found in the IBM manual.
System Action:
Action:
Using the appropriate IBM manual, investigate the meaning of the error code. Then,
respond as indicated by IBM for the particular situation.
1400 - 1499
1469S
TP SERVER CHECKPOINT nn PERCENT FULL
Reason:
The checkpoint dataset is more than 90% full, which is a severe problem.
System Action:
None.
Action:
Check the content of the checkpoint dataset to see what filled it up. If it is data to be
sent to a remote partner who for some reason can't connect, you need to fix that
problem, and the data will be sent over. If you start ESP with TPFORM, it will reformat
the checkpoint and discard everything.
1470W
Reason:
The checkpoint dataset is more than 75% full, which need attention.
System Action:
None.
Action:
Check the content of the checkpoint dataset to see what filled it up. If it is data to be
sent to a remote partner who for some reason can't connect, you need to fix that
problem, and the data will be sent over. If you start ESP with TPFORM, it will reformat
the checkpoint and discard everything.
1471I
Reason:
The checkpoint dataset is more than 50% full.
System Action:
None.
Action:
None.
1400 - 1499
1472E
DIV SAVE ERROR RETCODE = xxxx REASON = zzzz
Reason:
The TP Server issued a DIV SAVE request, but the return code from the operating system
System Action:
Action:
should uniquely SAVE the problem, and indicate a response. The codes are documented
situation.
1473S
AN ABEND Sxxxx HAS occurred IN CYBTP004
Reason:
Unpredicted problem occurred and the checkpoint manager CYBTP004 was ABEND with
ABEND code Sxxxx.
System Action:
Action:
Collect the dump output and ESP logs and seek help from CA Support.
1400 - 1499
1477I
TP SERVER INITIALIZATION IN PROGRESS
Reason:
TP SERVER is starting up and being initialized.
System Action:
None.
Action:
None.
1478S
THE LOCAPPL STATEMENT IS REQUIRED BUT WAS NOT SPECIFIED
Reason:
The LOCAPPL statement is not found in init parms.
System Action:
TP SERVER initialization fails. TP Server is not started.
Action:
Add LOCAPPL statement to the TP SERVER init parm. For the syntax of LOCAPPL, refer to
CYBESS06 in the SAMPLE library.
1479S
THE TPCKPT STATEMENT IS REQUIRED BUT WAS NOT SPECIFIED
Reason:
The TPCKPT statement is not found in init parms.
System Action:
TP SERVER initialization fails. TP Server is not started.
Action:
Add TPCKPT statement to the TP SERVER init parm. For the syntax of TPCKPT, refer to
CYBESS06 in the SAMPLE library.
1400 - 1499
1480S
A TP SERVER IS ALREADY ACTIVE FOR APPLICATION xxxx
Reason:
Another TP Server is already active for this application name. But only one TP Server is
allowed.
System Action:
This TP Server terminates.
Action:
None.
1481W
INVALID STARTUP PARAMETER SPECIFIED
Reason:
The parameters specified with start command or exec card for TP Server are invalid.
System Action:
The system will prompt the operator to re-enter the parameters.
Action:
Re-enter the correct startup parameters at prompt.
1482E
THE SERVER IS NOT ACTIVE - COMMAND NOT EXECUTED
Reason:
The inter-system tracking command component attempted to process a command, but
the TP server component was not active.
System Action:
Action:
Recycle the subsystem. If the problem persists, contact your software support
personnel.
1400 - 1499
1483I
xxxx Async mode is {On|Off}
Reason:
The message is coming out in response to TPASYNC command showing whether the LU
set up as asynchronous.
System Action:
The required mode is set.
Action:
None.
1484E
MAXIMUM CONVERSATIONS ALLOCATED
Reason:
The message is coming out in response on TPAPPL ADDCONV command which attempt
to add a new conversation with application, but the number of possible conversations
for this application has been reached.
System Action:
Action:
Monitor the current conversation number using TPDISP and try later.
1485E
CANNOT DELETE THE LAST OUTGOING CONVERSATION
Reason:
The last outgoing conversation cannot be deleted.
System Action:
Action:
None.
1400 - 1499
1486E
TP SERVER ABEND Sxxxx IN CYBTP001
Reason:
The TP SERVER program ends abnormally with system code Sxxxx in module CYBTP001.
System Action:
The TP Server is not longer available.
Action:
Please contact your software support personnel.
1487I
xxxx ACTIVE CONVERSATIONAL TRANSACTIONS TERMINATED
Reason:
The message is coming out whenever attempt to stop any conversational transaction
with a particular partner succeeds.
System Action:
Transaction dropped.
Action:
None.
1488I
xxxx INCOMING DATA PACKETS RELEASED FOR APPLICATION yyyy
Reason:
This is an informational message, indicating a specific number of incoming transactions
yyyy having been released.
System Action:
None.
Action:
None.
1400 - 1499
1489E
Reason:
The message is coming out if TP SERVER startup parameters scan routine fails. This
common message indicates a problem with parameters specified with start command or
exec card at TP server initiation time.
System Action:
TP Server doesn't start.
Action:
Check parameters and try again.
1490C
ENTER INITIALIZATION PARAMETER OR 'END'
Reason:
This is a prompt message which requests a user to enter or reenter a parameter or END
to stop initialization.
System Action:
The system waits for the response.
Action:
Enter the missing parameter or reenter an incorrectly specified parameter.
1491E
xxxx
Reason:
An I/O error was encountered reading the TPPARM file. The text of the message fully
System Action:
Action:
Correct the problem and restart the product.
1400 - 1499
1492W
FOLLOWING STATEMENT FROM xxxx HAS AN INVALID SYNTAX
Reason:
Processing TPPARM file parameters routine has encouraged statement with invalid
syntax.
System Action:
The system waits for response to 1496A message prompting to reenter an entire
statement, cancel or end
Action:
Locate and response to the prompt message.
1493W
FOLLOWING STATEMENT FROM xxxx HAS AN UNDEFINED PARAMETER
Reason:
Processing TPPARM file parameters routine has encouraged statement with undefined
parameter.
System Action:
Action:
Response to the prompt message.
1494W
PARAMETER ERROR ON FOLLOWING STATEMENT FROM xxxx FILE
Reason:
Processing TPPARM file parameters routine has encouraged statement with parameter
error.
System Action:
Action:
1400 - 1499
1495W
xxxx
Reason:
Processing TPPARM file parameters routine has encouraged a problem. The problem
description provided in a separate message. The prompt message 1496A should be
issued along with this message.
System Action:
Action:
1496A
REENTER ENTIRE STATEMENT, 'CANCEL' OR 'END'
Reason:
This is a prompt message. Processing TPPARM file parameters routine has encouraged a
problem. The message with a problem description should be issued before this
message.
System Action:
The system waits for response.
Action:
Reenter entire statement, or CANCEL to terminate, or END to continue.
1400 - 1499
1497I
nn of mm TRANSACTION(S) RELEASED FOR yyyy
Reason:
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.
Action:
None.
1498W
TP I/O to application xxxx has been outstanding for nn minutes
Reason:
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.
Action:
If this message is repeated, check the state of the VTAM connection to the specified LU.
1500 - 1599
1499S
UNABLE TO OPEN ACB - ERROR = X'xx'
Reason:
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:
Action:
Taker the proper VTAM corrective action as indicated by the error code and re-start the
product.
1500 - 1599
1514E
ESPCOM is not active
Reason:
The product 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.
Action:
If a COMMQ statement is present in ESPPARM, look in the start up messages for a
message describing a possible error. Enter the correct COMMQ statement in ESPPARM
and restart the product.
1500 - 1599
1515E
Invalid format of SEND request
Reason:
This is an internal error.
System Action:
The request is ignored. An additional message will be issued that describes the request.
Action:
Report the error to CA Support.
1516E
CommQ file is full
Reason:
The CommQ file is used by 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.
Action:
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 the product with the new CommQ
file.
1500 - 1599
1517E
ESPCOM display
Reason:
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:
Action:
None.
1518E
Destination name is missing for QUIESCE/RESTART/FLUSH request
Reason:
The User entered an ESPCOM command with one of the above keywords but without a
destination name. The destination name is required.
System Action:
Action:
Reenter the command with a destination name in it. (generics accepted).
1519I
Quiesce requested for nnnn destinations
Reason:
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.
Action:
None.
1500 - 1599
1520I
Restart requested for nnnn destinations
Reason:
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.
Action:
None.
1521I
Queue flush requested for nnnn destinations
Reason:
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.
Action:
None.
1522E
Unable to quiesce communications with dddd: CommQ file is full
Reason:
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.
Action:
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 the product.
1500 - 1599
1523E
Number of active destinations is at the limit: nnnn. Some destinations are quiesced.
Reason:
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.
Action:
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
Reason:
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:
N/A
Action:
Look for error messages from underlying network services. If the problem persists,
consult the network specialist.
1525I
nnnn messages flushed from dddd queue
Reason:
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.
Action:
None.
1500 - 1599
1526E
Unable to encrypt a message for dddd. Sender quiesced.
Reason:
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.
Action:
It is probably an internal error. Report it to CA Support.
1527E
CommQ ssss error. R15=aaaaaaaa R0=bbbbbbbb
Reason:
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.
Action:
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 data set.
1528E
CommQ data set has invalid format
Reason:
ESPCOM found that the CommQ file is not empty and its format is incorrect.
System Action:
ESPCOM is not initialized.
Action:
Either provide the correct data set, or start the product with the COMQFORMAT
parameter to format the present data set.
1500 - 1599
1529I
CommQ file is full. Space allocated: aaaa, used: uuuu bytes
Reason:
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.
Action:
None.
1530E
CommQ expansion limit reached
Reason:
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 session.
System Action:
The CommQ file will not be expanded.
Action:
Simply restarting the product 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 the
product with the new file.
1500 - 1599
1531I
An attempt to expand CommQ file failed
Reason:
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.
Action:
Allocate a bigger CommQ file, copy the contents of the old file into it using the REPRO
function of IDCAMS, and restart the product with the new file.
1532I
CommQ file has been expanded. Space allocated: aaaa, used: uuuu bytes.
Reason:
The CommQ file has filled up and was successfully expanded.
System Action:
Action:
None.
1533I
CommQ file usage is down to nn%
Reason:
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:
Action:
None.
1500 - 1599
1534W
CommQ file is nn% full
Reason:
The current using of the file is displayed.
System Action:
Action:
None.
1535E
Unable to send a message to Distributed Manager
Reason:
Due to a problem described by a previous message, the product failed to send a
message to a Distributed Manager.
System Action:
The message will be lost.
Action:
Correct the underlying problem indicated by a previous message.
1536E
Incompatible requests for resource rrrr in aggregate aaaa.qqqq
Reason:
The request is for a non-zero inverse request but the cluster does support addition to
that resource.
System Action:
Action:
Correct and re-issue the request.
1500 - 1599
1537E
Error obtaining local IP address. RC=cccc
Reason:
While processing a LOADAGDF command, the product encountered a MANAGER
statement indicating that the product is to use TCP/IP. The product attempted
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.
Action:
Correct the underlying TCP/IP problem.
1538W
Agent/DM receiver not defined for port pppp
Reason:
While processing a LOADAGDF command, the product encountered a MANAGER
statement that specifies a port pppp for inbound communications but no agent receiver
is defined for that port.
System Action:
Action:
Either correct the port number or define an agent receiver for port pppp.
1500 - 1599
1539E
Insertion not allowed: application contains DM-controlled objects
Reason:
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.
Action:
None.
1540E
Unable to send agent message
Reason:
The product encountered an error attempting to send a message to an agent. A
preceding message describes the error.
System Action:
The message may be lost.
Action:
Correct the underlying communication problem.
1541I
Command forwarded to the owning manager, mmmm
Reason:
The user issued a command to change status of a workload object that is controlled by a
Distributed Manager named mmmm. The product forwarded the command to mmmm.
System Action:
The owning manager will execute the command.
Action:
None.
1500 - 1599
1542E
Internal error: invalid message type tttt in call from mmmm
Reason:
ESPCOM was passed an unexpected message type tttt in a call from module mmmm.
System Action:
Action:
1543E
Internal error: duplicate listener for msgtype tttt in mmmm
Reason:
ESPCOM was passed an unexpected request for message type tttt in a call from module
mmmm.
System Action:
Action:
1544I
Message to dddd has been sent successfully
Reason:
ESPCOM has succeeded in sending a message with which it encountered errors in
previous attempts. dddd is the destination name.
System Action:
Action:
None.
1500 - 1599
1545E
Error connecting to dddd
Reason:
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.
Action:
Ensure that the correspondent named dddd is active and the product uses its correct
address and the network is functioning properly.
1546E
Error sending a message to dddd
Reason:
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.
Action:
Ensure that the correspondent named dddd is active and the network is functioning
properly.
1500 - 1599
1547W
Invalid message received by Agent Receiver rrrr from aaaa:pppp
Reason:
An Agent Receiver received a message with unexpected format. aaaa:pppp is the
sender's TCP/IP address and port. If the sender is a node, inconsistent configuration is a
possible reason.
System Action:
The message is discarded.
Action:
If the message comes from a node, ensure that the node parameters are correctly
described in the agent definition table.
1548W
Invalid feedback message received from pppp
Reason:
The product received invalid feedback on a message it sent to a partner named pppp.
The error may result from incorrect description of the partner in the agent definition
table.
System Action:
The product will retry the communication.
Action:
If the error persists, correct either agent definition table or partner parameters so that
they are consistent with each other.
1500 - 1599
1549W
Message rejected by pppp
Reason:
The product 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 the agent
definition table.
System Action:
The product will retry the communication.
Action:
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
Reason:
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
session, it will remain in force.
Action:
Correct the error and load the agent definition again.
1500 - 1599
1551E
Too many aliases for aaaa. Maximum allowed is mmmm
Reason:
The number of virtual agents, or aliases, for real agent aaaa exceeds the allowed
maximum of mmmm.
System Action:
Action:
1553E
No workload object modules found
Reason:
The product could not find the workload object module directory while processing the
WOBCMD command.
System Action:
The command will not be executed.
Action:
Ensure that the workload object type on which you wish to operate is properly defined
to the product with a WOBDEF statement.
1554E
Undefined workload object type
Reason:
A WOBCMD command was issued for a workload object type that is unknown to the
product.
System Action:
Action:
Ensure that the workload object type on which you wish to operate is properly defined
to the product with a WOBDEF statement.
1500 - 1599
1555E
Job not found
Reason:
A WOBCMD command was issued for a job that could not be found within the specified
application.
System Action:
Action:
Reissue the command with the correct job name and qualifier.
1556E
Not a WOBDEF-controlled object type
Reason:
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:
Action:
None.
1557E
Unable to find password matching xxxx, yyyy, zzzz
Reason:
A user ID was specified which required a password. The product 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.
Action:
Define a password to match the parameters above using the PASSWORD command.
Then retry the operation.
1500 - 1599
1558E
No space in ATR to store data for jjjj/aaaa
Reason:
There was insufficient space in the ATR to store data for a SAP_Job jjjj in application
aaaa.
System Action:
Action:
1559W
Invalid nnnn: tttt. Ignored. A numeric up to 8 digits expected.
Reason:
The value tttt for the environment variable nnnn is invalid. The value should be a
numeric string no longer than 8 digits.
System Action:
The product will use a default value.
Action:
Set a correct value using the SET operator command.
1500 - 1599
1560E
Invalid variable name
Reason:
A SET command had operands, but they did not begin with a valid variable name,
delimited by an assignment operator ('='). 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:
Action:
Not required.
1561I
ESP Environment Variables
Reason:
This is the heading for the list of environment variables.
System Action:
Variables are listed after this message.
Action:
Not required.
1562E
User xxxx denied access to agent yyyy
Reason:
User xxxx is not authorized to submit jobs to agent 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.
Action:
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.
1500 - 1599
1563E
???_Job xxxx in Appl yyyy, SAPJOBNAME statement missing
Reason:
The product detected that a JOBCOPY statement was specified in a SAP_JOB WOB, but a
SAPJOBNAME was not. SAPJOBNAME statement is mandatory in a SAP_JOB WOB that
has JOBCOPY statement.
System Action:
The execution of the object fails, and a "submit error" status results.
Action:
Specify the JOBCOPY statement. Then resubmit the job.
1564E
Reason:
System Action:
Action:
AGENT.yyyy. Once this has been established, retrigger the event.
1565E
Destination name xxxxxxxx does not exist
Reason:
Destination xxxxxxxx referenced in an ESPCOM command does not exist.
System Action:
Action:
Correct the destination name, and reissue the command.
1500 - 1599
1566E
???_Job xxxx in Appl yyyy, missing Agent name
Reason:
There was no agent name to identify where the work was to run.
System Action:
Action:
Provide the Agent name. Then resubmit the job.
1567E
Invalid Agent name wwww in Appl yyyy
Reason:
The agent named wwww was not defined when the workload object was readied.
System Action:
Action:
Either correct the Agent name, or define the Agent. Then resubmit the job.
1568E
Unable to find password matching xxxx, yyyy, zzzz, RC=n
Reason:
zzzz.
System Action:
Action:
Then resubmit the job.
1500 - 1599
1570E
Wild cards are not allowed for exclusive ENQUEUE: nnnn
Reason:
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.
Action:
1571C
Enqueue Display
Reason:
This message is a header for the product's response to the ENQUEUE command.
System Action:
The display follows.
Action:
None.
1572I
No matching Enqueues found
Reason:
This message is displayed in response to an ENQUEUE command when the product has
no enqueues matching the name on the command.
System Action:
None.
Action:
None.
1500 - 1599
1573I
EnqSelf mode is (NOT)ALWAYS
Reason:
This message is a response to ENQSELF command and shows the current setting, which
can be either ALWAYS or NOTALWAYS.
System Action:
None.
Action:
None.
1574E
APPLINS: job definition statements missing
Reason:
An APPLINS command was entered in line mode without job definition statements.
System Action:
Action:
Either supply the statements in the APPLINS command, or issue the command in ISPF
full screen mode where the product can open an edit session for you to enter job
definition statements.
1575E
Insufficient space to insert jobs in appl aaaa.nnnn
Reason:
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:
Action:
None. However, it may be possible to increase the application buffer size to provide
headroom in the future generations.
1500 - 1599
1576E
Insert request error: job jjjj already exists in appl aaaa.nnnn
Reason:
An attempt was made to insert job jjjj into generation nnnn of application aaaa. A job
with this name already exists in that application.
System Action:
Action:
None.
1577W
Insert request does not contain job definitions
Reason:
The statements provided in the APPLINS command do not define a job.
System Action:
Action:
Supply a valid job definition.
1578E
Application aaaa.nnnn is already complete
Reason:
An attempt was made to insert a job into generation nnnn of application aaaa, but this
application is already complete.
System Action:
Action:
None.
1500 - 1599
1579E
Circular reference in scheduling criteria
Reason:
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.
Action:
Correct the job definition.
1580E
Variable name is too long: exceeds nnnn bytes
Reason:
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:
Action:
1581E
Variable value is too long: exceeds nnnn bytes
Reason:
The string representing the value specified on a SETVAR statement exceeds the
maximum length allowed (nnnn bytes).
System Action:
Action:
1500 - 1599
1582E
Extraneous data: dddd
Reason:
A SETVAR statement contains unexpected data following the required parameters.
System Action:
Action:
1583E
Invalid keyword, wwww
Reason:
WOBCMD command contains an unrecognized keyword wwww.
System Action:
Action:
Correct and reenter the command.
1584E
WOBCMD is not supported for tttt
Reason:
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 wrong object.
System Action:
Action:
1500 - 1599
1585W
Job jjj, Appl aaa.ggg: No active CPU/NODE defined to resource manager
Reason:
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.
Action:
Define the active CPUs and verify their resource counts.
1586S
xxxx
Reason:
An error occurred while writing a record to scoreboard dump data set. The text of the
System Action:
The CYBESUTS utility is terminated.
Action:
This depends on the error.
1500 - 1599
1588E
<function> <message>
Reason:
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.
Action:
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.
1589E
Reason:
System Action:
Action:
1500 - 1599
1590E
Reason:
System Action:
Action:
1591E
Reason:
System Action:
Action:
1592E
No space in ATR to store data for object xxxxx
Reason:
There was no free space in the ATR to store the data.
System Action:
Action:
1500 - 1599
1593E
???_Job xxxx in Appl yyyy, missing External Scheduler name
Reason:
There was no External Scheduler name to identify where the work was to run.
System Action:
Action:
Provide the External Scheduler name. Then resubmit the job.
1594E
ERROR OCCURRED READING INDEX ENTRY FOR JOB xxxx
Reason:
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.
Action:
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
Reason:
Agent xxxxxxxx referenced in an AGENT or MGRADDR command does not exist.
System Action:
Action:
Correct the agent name, and reissue the command.
1500 - 1599
1596E
External Scheduler yyyy already defined
Reason:
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.
System Action:
Action:
Remove the extra EXTSCHED statement and re-enter the LOADAGDF command.
1597E
Agent or CommChan yyyy not defined
Reason:
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:
Action:
1598E
Format of TP checkpoint is obsolete.
Reason:
At current maintenance level, TP Server requires checkpoint file with modified format.
System Action:
TP Server stops.
Action:
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.
1600 - 1699
1599W
Application aaaa start failed: LU uuuu assigned to bbbb
Reason:
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.
Action:
Correct either application or LU name and reissue the command.
1600 - 1699
1613W
EspCom clients cannot bind to xxxx
Reason:
Response to MANAGER command in AGENTDEF file. The MANAGER command specified
both the TCPIP(xxxx) and BIND operands, where xxxx is a DNS host name or IP address.
The product cannot bind to the IP address specified by the TCPIP(xxxx) operand when it
connects to an Agent because the IP address does not represent a network interface on
the local system.
System Action:
The MANAGER command is processed as if the BIND operand had been omitted. When
the product connects to an Agent, the operating system's TCP/IP will assign a local IP
address to the TCP connection.
Action:
Change the MANAGER command in the AGENTDEF file to specify TCPIP(xxxx), where
xxxx specifies a DNS host name or IP address that represents a network interface on the
local system. Then issue the operator command: OPER LOADAGDF yyyy where yyyy is
the data set name of the AGENTDEF file, to update the EspCom client's TCP bind status.
1600 - 1699
1614E
NAME SAME AS SPECIAL DAY IN xxxxxx CALENDAR: yyyyyyyy
Reason:
A DEFHOL command has been issued for a day with the same name as a special day in
the same calendar.
System Action:
Action:
Issue a LISTCAL command to show the special days defined in the calendar in question.
1615E
NAME SAME AS HOLIDAY IN xxxxxx CALENDAR: yyyyyyy
Reason:
A DEFSPEC command has been issued for a day with the same name as a holiday in the
same calendar.
System Action:
Action:
Issue a LISTCAL command to show the holidays defined in the calendar in question.
1616E
DATE AND TIME ALREADY SPECIFIED FOR SPECIAL DAY xxxxxxxx
Reason:
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:
Action:
Issue a LISTSPEC command to show the dates and times defined for the special day in
question.
1600 - 1699
1617E
Access to event xxxx.yyyy denied.
Reason:
Authority access check to the event specified by VTRDEF command failed.
System Action:
Action:
1618E
String too long
Reason:
Global variable processing encountered a string longer than the maximum of 255
characters.
System Action:
Action:
Correct the long string.
1619E
Trigger iiii already exists in table tttt
Reason:
VTRDEF command was entered for table tttt with trigger id iiii, but the table already
contains a trigger with this id.
System Action:
Action:
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
the product will assign a unique id
1600 - 1699
1620E
Variable table update request not valid from ESP proxy subsystem
Reason:
A request was made to update a variable table under a proxy subsystem. However,
proxies have read-only access to variable tables.
System Action:
Action:
Issue the request to the master subsystem.
1621E
Invalid global variable table access request xxxx
Reason:
The request was invalid.
System Action:
Action:
Correct the request and retry.
1622E
Insufficient space in variable table xxxx for request
Reason:
The named variable table is full.
System Action:
Action:
Purge old unneeded entries or create a new table.
1600 - 1699
1623E
Variable table xxxx not defined or access not authorized
Reason:
The variable table name supplied could be incorrect.
System Action:
Action:
Correct the request or gain access to the variable table.
1624E
Global Variable Table xxxx already defined
Reason:
The table already exists.
System Action:
Action:
Correct the request.
1625E
Global Variable Table xxxx not defined
Reason:
The table does not exist.
System Action:
Action:
1600 - 1699
1626E
Variable xxxx not found
Reason:
The variable is not defined.
System Action:
Action:
1627E
No matches found or access not authorized
Reason:
A generic VTLIST command returned no entries matching your query. Either matching
entries do not exist or you are not authorized to view them.
System Action:
None.
Action:
Correct the request or gain access to view the list.
1628I
Global Variable Table xxxx deleted
Reason:
The variable table named xxxx has been successfully deleted.
System Action:
None
Action:
None
1600 - 1699
1629E
Error performing global variable processing on Table xxxx
Reason:
The system encountered an error for the specified table.
System Action:
Action:
1630E
Variable xxxx error code n
Reason:
An unknown error code has been encountered while processing a variable handling
request.
System Action:
Action:
Support.
1631E
Variable xxxx Not authorized for requested access
Reason:
The access to the variable is not granted.
System Action:
Action:
You will need to be authorized.
1600 - 1699
1632E
Variable xxxx not found on Table yyyyyy.
Reason:
Specified variable is not found in table.
System Action:
Action:
Correct the request. The specified table could be wrong or the variable name incorrect.
1633E
Variable xxxx not updated, old value mismatch
Reason:
The variable was not updated because the old value specified in the request did not
match the current value of the variable.
System Action:
Action:
Change the old value, making other changes as appropriate. Then reissue the command.
1634E
Variable xxxx locked
Reason:
An attempt was made to update a variable in a locked table.
System Action:
Action:
Unlock the table and re-issue the request.
1600 - 1699
1635E
Variable xxxx lock expired
Reason:
This message is no longer used.
System Action:
Action:
None required.
1636E
Variable xxxx not updated, table full
Reason:
The variable table is full and cannot accept the update.
System Action:
Action:
Purge unneeded table entries or create a new table.
1637E
Variable xxxx not numeric
Reason:
The variable must be numeric.
System Action:
Action:
1600 - 1699
1638E
Variable xxxx function nn not supported
Reason:
A request was made to increment a variable that cannot be incremented.
System Action:
Action:
1639E
Variable xxxx not defined
Reason:
The specified variable name could be in error.
System Action:
Action:
1640E
Error retrieving REXX variable xxxx
Reason:
A problem was detected when trying to retrieve a variable from REXX.
System Action:
Action:
Support.
1600 - 1699
1641E
Variable xxxx not defined
Reason:
The variable name could be in error.
System Action:
Action:
1642E
Error setting REXX variable xxxx
Reason:
The REXX variable was not set.
System Action:
Action:
Correct the value and retry.
1643I
Trigger defined/replaced in table xxxx ID yyyy
Reason:
Information only.
System Action:
None.
Action:
None.
1600 - 1699
1644E
Trigger ID yyyy deleted in table xxxx
Reason:
Information only.
System Action:
The request is completed.
Action:
None.
1645E
Variable Trigger xxxx not found
Reason:
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:
Action:
Specify a valid trigger name.
1646E
HOLIDAY WITH SAME NAME AND START DATE AND TIME ALREADY EXISTS: xxxxxx
Reason:
User is trying to specify a holiday with same name and start date and time as existing
one in specified calendar.
System Action:
Action:
Determine cause of error, and reissue corrected command.
1600 - 1699
1647E
Reason:
System Action:
Action:
respectively.
1648E
Insufficient checkpoint space for global variable table trigger request
Reason:
A change to a variable satisfied the conditions for a variable trigger, but the checkpoint
did not have sufficient free space to hold the data describing the required action.
System Action:
The event is not triggered.
Action:
Investigate and correct the checkpoint-full condition.
1600 - 1699
1649E
Unsupported encryption type
Reason:
Support for the requested encryption algorithm is not installed.
System Action:
The request fails.
Action:
Either use an available encryption algorithm or install the missing component. DES
encryption is always available.
1650E
Invalid parameter passed to encrypt/decrypt routine
Reason:
The encryption/decryption service routine detected a missing or invalid parameter.
System Action:
The current action is aborted.
Action:
This is most likely a code defect. Contact your software support personnel.
1651E
Invalid length passed to encrypt/decrypt routine
Reason:
The encryption/decryption service routine was passed an invalid buffer length.
System Action:
The current action is aborted.
Action:
This is most likely a code defect. Contact your software support personnel.
1600 - 1699
1652E
Error opening DD xxxxxxxx
Reason:
An error occurred while opening the file associated with DD name xxxxxxxx.
System Action:
Processing ends.
Action:
Check for other product or system messages explaining the error.
1653E
xxxxxxxx record length invalid
Reason:
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.
Action:
Correct the error.
1600 - 1699
1654E
Dsname=<dsname> too long for GDG base
Reason:
The explicit data set trigger notification utility program ESPDST (alias CYBESDT1) was
processing an explicit data set trigger that specified DSNAME(<dsname>(<gdsnum>)),
where <dsname> is the data set name of a GDG base and <gdsnum> is a GDS generation
number. However, <dsname> was longer than the 35 character maximum permissible
for a GDG base data set name.
System Action:
The explicit data set trigger notification is ignored. Program ESPDST (alas CYBESDT1)
Action:
Re-execute program ESPDST (alias CYBESDT1) specifying a valid GDG base data set name
and GDS generation number.
1655W
Explicit data set trigger for <dsname> {(<gdsnum>){(<bias>)}} not defined to ESP
subsystem <ssid>
Reason:
The explicit data set trigger notification utility program ESPDST (alias) CYBESDT1 sent an
explicit data set trigger notification for data set <dsname> to subsystem <ssid>.
However, subsystem <ssid> did not find a matching explicit data set trigger definition for
the specified explicit data set trigger notification. For a GDS, if subsystem <ssid>'s
EXPDSTRG data set authentication level is set to SECURE or VERIFY and the GDS has
been verified, <dsname> gives the fully qualified GDS data set name, <gdsnum> gives
the relative generation number and <bias>, if specified, gives the GDS bias value.
System Action:
Program ESPDST (alias CYBESDT1) terminates with a warning return code.
Action:
Ensure that both the explicit data set was specified correctly to program ESPDST (alias
CYBESDT1) and the explicit data set trigger was defined correctly to subsystem <ssid>. If
an error is found, then correct it and re-execute ESPDST (alias CYBESDT1).
1600 - 1699
1656W
Data set trigger cell shortage in ESP subsystem <ssid>
Reason:
Subsystem <ssid> was unable to process an explicit data set trigger notification sent by
explicit data set trigger utility ESPDST (alias CYBESDT1) because of a data set trigger cell
shortage. This condition is most likely to occur when subsystem <ssid> has been down
for an extended period and a data set trigger backlog has built up.
System Action:
The explicit data set trigger notification is ignored. Program ESPDST (alias CYBESDT1)
Action:
To handle larger data set trigger backlogs, the subsystem's ESPPARM initialization file
should specify a DSTRIG command with a larger data set trigger cell count or a larger
maximum data set trigger cell expansion limit. The DSTRIG command syntax is:
DSTRIG {CELLS(<cells>)} {EXPANSIONLIMIT(<limit>)}
<cells> - specifies the initial number of data set trigger cells. If omitted, the default
is 10.
<limit> - specifies the maximum data set trigger cell expansion limit. If omitted, the
default is 50.
1657W
Data set trigger cell core request failure in ESP subsystem <ssid>
Reason:
Subsystem <ssid> was unable to process an explicit data set trigger notification sent by
explicit data set trigger utility ESPDST (alias CYBESDT1) because there was insufficient
ECSA virtual storage to satisfy a request for a data set trigger cell. This condition is most
likely to occur when subsystem <ssid> has been down for an extended period and a data
set trigger backlog has built up.
System Action:
The explicit data set trigger notification is ignored. Program ESPDST (alias CYBESDT1)
Action:
Subsystem <ssid> can be stopped and restarted when the ECSA shortage is relieved.
1600 - 1699
1658W
Explicit data set trigger function not supported by ESP subsystem <ssid>
Reason:
The explicit data set trigger notification utility program ESPDST (alias CYBESDT1) sent an
explicit data set notification to a subsystem <ssid> that does not support the data set
trigger function using the subsystem request interface. Note that this condition occurs
when the explicit data set trigger notification is sent by a V5.5 or above version of
ESPDST (alias CYBESDT1) to a pre-V5.5 version of the subsystem.
System Action:
The explicit data set trigger notification is ignored by subsystem <ssid>. Program ESPDST
(alias CYBESDT1) terminates with an error return code.
Action:
Correct any version mismatches between the explicit data set trigger program ESPDST
(alias CYBESDT1) and the target subsystem. Then re-execute ESPDST (alias CYBESDT1). If
there is no version mismatch, restart subsystem <ssid> with the RELOAD start-up
option.
1659E
ESP subsystem <ssid> return code <ret>-<rsn>
Reason:
The explicit data set trigger notification utility program ESPDST (alias CYBESDT1)
attempted to send an explicit data set trigger notification to subsystem <ssid>.
However, an error occurred in the subsystem request interface. <ret> specifies the
return code. <rsn> specifies the reason code.
System Action:
The explicit data set trigger is not processed by subsystem <ssid>. Program ESPDST (alias
CYBESDT1) terminates with an error return code.
Action:
Attempt to determine the cause of the subsystem error and correct if possible. If unable
to determine the cause of the subsystem error, contact CA Support.
1600 - 1699
1660C
DSTRIG HELP
Reason:
Response to DSTRIG HELP explicit data set trigger activate command.
System Action:
DSTRIG explicit data set trigger activate command options are displayed.
Action:
None.
1661E
ACTIVATE operand required for explicit data set trigger notification
Reason:
Response to DSTRIG explicit data set trigger activate command. When the DSTRIG
command is issued outside an event, the ACTIVATE operand must be specified to
indicate an explicit data set trigger notification.
System Action:
The DSTRIG command is ignored.
Action:
If an explicit data set trigger notification is required, re-issue the DSTRIG command with
the ACTIVATE operand.
1662W
Subsystem <ssid> not found
Reason:
Response to DSTRIG ACTIVATE command. An explicit data set trigger notification was
sent to a subsystem <ssid> that could not be found.
System Action:
The DSTRIG ACTIVATE command is ignored.
Action:
If <ssid> is a valid subsystem, then wait until it becomes active for the first time since
the system was IPL'd before re-executing the DSTRIG ACTIVATE command.
1600 - 1699
1663E
Dsname=<dsname> too long for GDG base
Reason:
Response to DSTRIG ACTIVATE activate command. An explicit data set notification
request specified <dsname>(<gdsnum>), where <dsname> is the data set name of a
GDG base and <gdsnum> is a GDS generation number. However, <dsname> was longer
than the 35 character maximum permissible for a GDG base data set name.
System Action:
Action:
Re-issue the DSTRIG ACTIVATE command specifying a valid GDG base data set name and
GDS generation number.
1664C
DSTRIG ACTIVATE Explicit data set trigger sent to ESP subsystem <ssid> for data set:
{GDG }<dsname>{ (<gdsnum>){(<bias>)}}
Reason:
Response to DSTRIG ACTIVATE command. An explicit data set trigger notification for
data set <dsname> was sent to subsystem <ssid>. For a GDS, if subsystem <ssid>'s
EXPDSTRG data set authentication level is set to SECURE or VERIFY and the GDS has
been verified, <dsname> gives the fully qualified GDS data set name, <gdsnum> gives
the relative generation number and <bias>, if specified, gives the GDS bias value.
System Action:
If a matching explicit data set trigger definition exists for the specified explicit data set
trigger, then subsystem <ssid> performs the action specified by the explicit data set
trigger. If no matching explicit data set trigger definition exists for the specified explicit
data set trigger, then no action is taken.
Action:
None.
1600 - 1699
1665W
Explicit data set trigger for <dsname> {(<gdsnum>){(<bias>)}} not defined to ESP
subsystem <ssid>
Reason:
Response to DSTRIG ACTIVATE command. An explicit data set trigger notification for
data set <dsname> was sent to subsystem <ssid>. However, subsystem <ssid> did not
find a matching explicit data set trigger definition for the specified explicit data set
trigger notification. For a GDS, if subsystem <ssid>'s EXPDSTRG data set authentication
level is set to SECURE or VERIFY and the GDS has been verified, <dsname> gives the fully
qualified GDS data set name, <gdsnum> gives the relative generation number and
<bias>, if specified, gives the GDS bias value.
System Action:
Action:
Ensure that both the DSTRIG ACTIVATE command was specified correctly and the
explicit data set trigger was defined correctly to subsystem <ssid>. If an error is found,
then correct it and re-execute the DSTRIG ACTIVATE command.
1666W
Data set trigger cell shortage in ESP subsystem <ssid>
Reason:
Response to DSTRIG ACTIVATE command. Subsystem <ssid> was unable to process an
explicit data set trigger notification because of a data set trigger cell shortage. This
condition is most likely to occur when subsystem <ssid> has been down for an extended
period and a data set trigger backlog has built up.
System Action:
The explicit data set trigger notification is ignored.
Action:
To handle larger data set trigger backlogs, the subsystem's ESPPARM initialization file
should specify a DSTRIG command with a larger data set trigger cell count or a larger
maximum data set trigger cell expansion limit. The DSTRIG command syntax i:
DSTRIG {CELLS(<cells>)} {EXPANSIONLIMIT(<limit>)}
<cells> - specifies the initial number of data set trigger cells. If omitted, the default
is 10.
<limit> - specifies the maximum data set trigger cell expansion limit. If omitted, the
default is 50.
1600 - 1699
1667W
Data set trigger cell core request failure in ESP subsystem <ssid>
Reason:
Response to DSTRIG ACTIVATE command. Subsystem <ssid> was unable to process an
explicit data set trigger notification because there was insufficient ECSA virtual storage
to satisfy a request for a data set trigger cell. This condition is most likely to occur when
subsystem <ssid> has been down for an extended period and a data set trigger backlog
has built up.
System Action:
The explicit data set trigger notification is ignored.
Action:
Subsystem <ssid> can be stopped and restarted when the ECSA shortage is relieved.
1668W
Explicit data set trigger function not supported by ESP subsystem <ssid>
Reason:
Response to DSTRIG ACTIVATE command. An explicit data set notification was sent to an
subsystem <ssid> that does not support the data set trigger function using the
subsystem request interface. Note that this condition occurs when the explicit data set
trigger notification is sent to a pre-V5.5 version of the subsystem.
System Action:
The explicit data set trigger is ignored by subsystem <ssid>.
Action:
Ensure the client is accessing a 5.5 or above version of the subsystem. Then re-issue the
DSTRIG ACTIVATE command. If there is no version mismatch, restart the subsystem
<ssid> with the RELOAD start-up option.
1600 - 1699
1669E
Unable to locate Job xxxx for JOBSTATS save in Appl yyyy
Reason:
The subsystem was unable to locate Job "xxxx" in Application "yyyy".
System Action:
Action:
Contact your system support.
1670E
Error occurred saving Job Statistics entry for Job xxxx in Appl yyyy
Reason:
An I/O error on the job statistics data set, described by a preceding message, has
occurred.
System Action:
No job statistics recording will be performed for the indicated job.
Action:
1671E
Error occurred saving Job Statistics entry for Job xxxx in Appl yyyy under le zzzz
Reason:
occurred.
System Action:
Action:
1600 - 1699
1672E
Job Statistics error causing possible loss of statistics for Job xxxx in Ap yy
Reason:
occurred.
System Action:
Action:
1673E
Error occurred reading Job Statistics entry for Job xxxx in Appl yyyy
Reason:
occurred.
System Action:
Action:
1674E
Error occurred reading Job Statistics entry for Job xxxx in Appl yyyy under profile zzzz
Reason:
occurred.
System Action:
Action:
1600 - 1699
1675E
Job Statistics error causing possible loss of statistics for Job xxxx in Ap yy
Reason:
occurred.
System Action:
Action:
1676E
WOBCMD is not supported for external jobs
Reason:
WOBCMD command was entered against an external workload object. External
workload objects do not support the command.
System Action:
Action:
1677W
Profile Definition wwww not found for Job xxxx(yyyy)
Reason:
A job Profile Definition specified for a job was not located.
System Action:
No job statistics recording will be performed for that job.
Action:
The job Profile Definition may have been accidentally deleted. The job Profile Definition
should be redefined.
1600 - 1699
1678E
Error occurred reading Profile Definition wwww for Job xxxx(yyyy)
Reason:
occurred.
System Action:
Action:
1679E
Error updating JOBINDEX information for Job xxxx
Reason:
An I/O error on the JOBINDEX data set, described by a preceding message, has occurred.
System Action:
Action:
1600 - 1699
1680E
DIV object allocate error, Dsname=<dsname>
Reason:
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 initialized as a Data In Virtual (DIV) object. If the data set to be
allocated was the object of a NETQUEUE <dsname> command in the 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 the
product, or to re-enter a LOADNET initialization command.
Action:
If the data set to be allocated was the object of a NETQUEUE <dsname> command in the
LOADNET initialization file, then either reply CANCEL to action message prompt 3328A
to terminate the product, 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 the product if it was terminated.
1681E
Requested DIV object not allocated, DDname=<ddname>
Reason:
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.
Action:
None. Does not occur under the product.
1600 - 1699
1682E
DIV object not found in catalog, Dsname=<dsname>
Reason:
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.
System Action:
The data set is not initialized as a Data In Virtual (DIV) object.
Action:
1683E
DIV object not VSAM linear data set, Dsname=<dsname>
Reason:
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 initialized as a Data In Virtual (DIV) object. If the data set to be
allocated was the object of a NETQUEUE <dsname> command in the LOADNET
ignore the NETQUEUE <dsname> command, a CANCEL response to terminate the
product, or to re-enter a LOADNET initialization command.
Action:
If the DIV object to be initialized was the object of a NETQUEUE <dsname> command in
the LOADNET initialization file, then either reply CANCEL to action message prompt
3328A to terminate the product, 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 the product if it was terminated. The
NETQUEUE data set must be a VSAM linear data set.
1600 - 1699
1684W
xDiv Init|Open|Close|Extend|Save, <description>
Reason:
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.
Action:
Attempt to diagnose the condition that prevented the Data In Virtual (DIV) object API
request from being serviced and correct it if possible.
1685E
Reason:
An internal Data In Virtual (DIV) object API request has resulted in an error condition.
<description> describes the error condition.
System Action:
Action:
Attempt to diagnose the problem from the error description and correct it if possible. If
unable to, contact your software support personnel.
1600 - 1699
1686S
Reason:
An internal Data In Virtual (DIV) object API request has resulted in a severe error
condition. <description> describes the error condition.
System Action:
Action:
1687E
DIV core request failed, Size=<bytes>
Reason:
A request for address space virtual storage to accommodate a Data In Virtual (DIV)
object failed. <bytes> specifies the size in byte units of the address space virtual storage
request.
System Action:
The Data In Virtual (DIV) object is not created as requested.
Action:
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 your
1600 - 1699
1688E
xDiv Save rejected, Div object closed, Dsname=<dsname> {, Dspace=<dspname>}
Reason:
An internal API request for a Data In Virtual (DIV) save 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) save request is not serviced.
Action:
1689E
Div Identify|Access|Map|Save|Unidentify, Return=<rc>, Reason=<reason>,
Dsname=<dsname>{, Dspace=<dspname>}
Reason:
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.
Action:
If possible, diagnose and correct the Data In Virtual (DIV) error. If unable to do so,
contact your software support personnel.
1600 - 1699
1690E
Unknown NOTIFY event name: xxxxxxxx
Reason:
The application requested a NOTIFY event named xxxxxxxx. However, the event name is
incorrect.
System Action:
The NOTIFY event request is ignored. Processing of the application continues.
Action:
1691E
Entry limit reached creating new Job Name Lookup record for Job xxxx in App y under
Profile zzzz
Reason:
The maximum number of active entries with the same job name that can occupy a single
record in the JOBINDEX data set has been reached.
System Action:
Job statistics recording will be performed for the indicated job, but retrieval is restricted
to using the long job name only.
Action:
1692E
Error updating new Job Name Lookup record for Job xxxx in Appl yyyy
Reason:
System Action:
Action:
1600 - 1699
1693E
Error updating old Job Name Lookup record for Job xxxx in Appl yyyy
Reason:
System Action:
Action:
1694E
Alert ID xxxx has bad event name
Reason:
The application requested an alert named xxxx. However, the event name specified in
the alert definition is incorrect.
System Action:
Action:
Either correct the alert name, or define the alert correctly.
1695I
Mail Log status
Reason:
This message is displayed on the console in response to MAILLOG command. It serves as
a header for subsequent messages that provide details about the setting of the mail log .
System Action:
N/A
Action:
N/A
1600 - 1699
1696I
TSO Send status
Reason:
This message is displayed on the console in response to TSOSEND command. It serves as
a header for subsequent messages that provide details about the setting of sending
messages to TSO users by the product.
System Action:
N/A
Action:
N/A
1697E
Parameter ORIGUSER is mandatory when using SECURE option
Reason:
The SECURE option was set in the SMTPPARM statement of the MAILLIST data set, but
the ORIGUSER parameter was not provided.
System Action:
Message ESP802A prompts operator to correct the error.
Action:
Respond to message ESP802A.
1600 - 1699
1698E
DIV data set CI size <cisize> invalid, must be 4096, Dsname=<dsname> {,
DataSpace=<dspname>}
Reason:
A request to initialize a Data In Virtual (DIV) object failed because the specified VSAM
linear data set <dsname> was defined with a control interval size <cisize> other than
4096. DIV can only process linear data sets defined with a control interval size of 4096.
This message is issued if the NETQUEUE command in the LOADNET initialization file
specifies a VSAM linear data set that was defined with a control interval other than
4096. If the DIV object is in a data space, <dspname> specifies the data space name.
System Action:
The Data In Virtual (DIV) object is not initialized. If this message is a response to the
NETQUEUE command in the LOADNET initialization file, error message 3327E and
prompt message 3328A follow.
Action:
Redefine the VSAM linear data set with the IDCAMS DEFINE CLUSTER command
specifying (or defaulting to) CONTROLINTERVALSIZE(4096) or CISZ(4096). If this message
is a response to the NETQUEUE command in the LOADNET initialization file, respond to
message prompt 3328A with a NETQUEUE command specifying a VSAM linear data set
with control interval size 4096, or with a CANCEL or END command. Note that if the
prompt message 3328A response is END, the product will terminate when Network
Delivery Services (NDS) fails to find a NETQUEUE data set. Also, correct the NETQUEUE
command in the LOADNET initialization file if necessary.
1699E
Unknown alert ID: xxxx
Reason:
The application requested an alert named xxxx. However, no such alert is defined in the
system.
System Action:
Action:
Either correct the alert name, or define the alert.
1700 - 1799
1700 - 1799
1700W
JOB xxxx IN APPL aaaa IS NOW IN MANUAL HOLD WAITING RELEASE
Reason:
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.
Action:
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
Reason:
In response to a LOADUPDT statement or command, the user profile definition table has
been loaded.
System Action:
The data in the user profile definition table will be used.
Action:
None
1700 - 1799
1702I
USER PROFILE DEFINITION TABLE ACTIVE, LOADED FROM xxxx(yyyy)
Reason:
This message identifies the active user profile definition table.
System Action:
None
Action:
None
1703I
SAF Options:
Reason:
The product is listing the SAF security option settings.
System Action:
None.
Action:
None.
1704E
User profile data set not specified, needed when SAF security has been requested
Reason:
The initialization statements included a SAFCLASS statement, requesting that host based
SAF security be used for internal security. However, this requires that a user profile data
set be defined. This was not performed.
System Action:
The subsystem will not initialize.
Action:
Code a LOADUPDT statement in the initialization data set. A sample user profile
member supplied in the sample library. Once this is done, restart the subsystem.
1700 - 1799
1705E
Command xxxx not available within REXXON/REXXOFF
Reason:
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 subsystem is not initialized.
Action:
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.
REXXON
"PLEXNM='"PLEXNAME()"'"
REXXOFF
QUEUE %PLEXNM..ESP.QUEUE
1706I
Agent Definition Table loaded
Reason:
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.
Action:
None
1700 - 1799
1707I
Agent Definition Table active, loaded from xxxx(yyyy)
Reason:
This message identifies the active multi-platform agent definition table.
System Action:
None
Action:
None
1708I
SAF Class:
Reason:
The product is listing the SAF class and resource options.
System Action:
None.
Action:
None.
1709W
Duplicate definitions for time zone xxxx
Reason:
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, the product will use the
instance of this name whose zone number is lowest, and ignore any duplicates with
higher zone numbers.
Action:
Correct or remove the line in the ESPPARM data set.
1700 - 1799
1710I
Backing out to xxxx
Reason:
In response to a BACKOUT command, the product is performing processing required to
allow a version xxxx system to execute using the same data sets as the current version
of the product.
System Action:
The backout processing is performed. After the processing is completed, the product
will perform SHUTDOWN processing and terminate.
Action:
Start product version xxxx.
1711E
Not authorized to Event Initiator Class nnn
Reason:
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.
Action:
Remove the non-zero Event initiator class from the request or obtain READ access to the
resource.
1700 - 1799
1712E
Invalid EICLASS value specified
Reason:
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.
Action:
Correct the EICLASS value.
1713I
Event class nn deleted, xx TDR(s) moved to class 0
Reason:
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.
Action:
None.
1714I
Event multiprogramming level for class nn set to xx
Reason:
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:
Action:
None.
1700 - 1799
1715C
Event Initiator Display
Reason:
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.
System Action:
Action:
None.
1716E
Invalid CLASS value nnn specified
Reason:
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.
Action:
Correct the CLASS value and retry the command.
1700 - 1799
1717E
Invalid MPL value nn specified
Reason:
An EICLASS SET command was entered with an MPL value of nn. nn is outside the
acceptable range of 1 to 16.
System Action:
Action:
Correct the MPL value and retry the command.
1718E
xxxx value required for SET or DELETE
Reason:
An EICLASS SET or DELETE command was entered without a required keyword xxxx.
System Action:
Action:
Supply the missing keyword xxxx and retry the command.
1719E
Member name '+|-' invalid
Reason:
An attempt was made to activate an explicit data set trigger using the ESPDST (alias
CYBESDT1) utility. However, an invalid data set member name '+' or '-' was specified.
System Action:
The explicit data set trigger utility ESPDST (alias CYBESDT1) exits with return code 32.
Action:
Correct the explicit data set trigger job's JCL EXEC PARM operand to specify a valid
member name, or no member name, as required. Then rerun the explicit data set job.
1700 - 1799
1720E
Member name '+|-' invalid
Reason:
Response to DSTRIG ACTIVATE activate command. An explicit data set notification
request specified an invalid data set member name '+' or '-'.
System Action:
Action:
Re-issue the DSTRIG ACTIVATE command specifying a valid member name, or no
member name, as required.
1722E
Expedite policy name xxxx invalid
Reason:
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:
Action:
Re-enter the EXPEDITE command specifying a valid expedite policy name.
1723C
EXPEDITE Command Options
Reason:
Response to EXPEDITE HELP command.
System Action:
Displays EXPEDITE command options.
Action:
None.
1700 - 1799
1724C
EXPEDITE {xxxx }LIST
Reason:
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 the respective criteria and action
specifications. If xxxx is omitted, all expedite policies are listed.
Action:
None.
1725I
{No expedite policies|xxxx expedite polic{y|ies} not} defined
Reason:
This is a 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.
This message is one of the following:
No expedite policies defined
xxxx expedite policy not defined
xxxx expedite policies not defined
System Action:
Action:
None.
1700 - 1799
1726E
Expedite policy xxxx already exists, cannot be added
Reason:
Response to EXPEDITE xxxx ADD command. xxxx specifies an expedite policy that
already exists, and therefore cannot be added.
System Action:
Action:
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.
1727I
Expedite policy xxxx {added|altered|deleted}
Reason:
Response to EXPEDITE xxxx ADD, ALTER or DELETE command. xxxx specifies an expedite
policy name. The requested EXPEDITE command completed successfully.
System Action:
Action:
None.
1700 - 1799
1728W
Expedite policy xxxx specifies no {criteria{ nor actions}|actions}
Reason:
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 application
job cannot be expedited. If expedite policy xxxx specifies no criteria, but at least one
action, then any associated product can be expedited, but only manually (using 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:
Action:
Add any required criteria and/or actions to expedite policy xxxx with the "OPER
EXPEDITE xxxx ALTER" command.
1729E
Expedite policy xxxx not defined
Reason:
Response to "EXPEDITE xxxx ALTER" or "EXPEDITE xxxx DELETE" command.
System Action:
Action:
If necessary, re-enter the EXPEDITE command specifying an existing expedite policy. To
list all expedite policies, enter the command: OPER EXPEDITE
1700 - 1799
1730C
JES2RLSE Command Options
Reason:
Response to JES2RLSE HELP command.
System Action:
Displays JES2RLSE command options.
Action:
None.
1731I
JES2 release specified as {earlier than V2R4|V2R4 or later}
Reason:
Response to JES2RLSE or JESRLSE LIST command. If the JES2 release is specified as earlier
than V2R4, then the product will issue JES2 commands using the old pre-V2R4 syntax. If
the JES2 release is specified as V2R4 or later, then the product will issue JES2 commands
using the new V2R4 and later syntax.
System Action:
Action:
None.
1700 - 1799
1732E
EXPEDITE LIST option cannot specify criteria and/or actions.
Reason:
Response to EXPEDITE or EXPEDITE LIST command. An EXPEDITE command that defaults
to or specifies the LIST option 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:
Action:
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
Reason:
Response to EXPEDITE ALTER command. An EXPEDITE command that specifies the
ALTER option must, but does not specify at least 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:
Action:
Re-enter the EXPEDITE ALTER command specifying at least one criterion or action.
1700 - 1799
1734E
INVALID COMMAND PARAMETER ENTERED
Reason:
The TP Server command has an invalid format or invalid parameter.
System Action:
The TP Server command is not processed.
Action:
1735E
TP INITIALIZATION TERMINATED
Reason:
The LOCAPPL command has an invalid format or invalid parameter.
System Action:
The LOCAPPL command is not processed.
Action:
1736E
INVALID CHECKPOINT DATASET NAME ENTERED
Reason:
The TPCKPT command has an invalid CHECKPOINT data set name.
System Action:
The TPCKPT command is not processed.
Action:
1700 - 1799
1737I
THE CHECKPOINT MANAGER IS ALREADY STARTED
Reason:
A TPCKPT command has already been processed.
System Action:
The TPCKPT command is ignored.
Action:
None.
1738E
APPLICATION xxxx DOES NOT EXIST
Reason:
The TPAPPL command has an invalid application name.
System Action:
The TPAPPL command is not processed.
Action:
1739E
ABEND CODE = xxxx
Reason:
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.
Action:
1700 - 1799
1740E
TPTEST ERROR FROM TP SERVER = xxxx
Reason:
The TPTEST command cannot send a test transaction to a partner application.
System Action:
The TPTEST command is not processed.
Action:
1741I
THE DEFAULT LOGON MODE IS xxxx
Reason:
The TPSTATS command displayed the default logon mode.
System Action:
None.
Action:
None.
1742E
Unknown NOTIFY event name: xxxxxxxx
Reason:
The application requested a NOTIFY event named xxxxxxxx. However, the event name is
incorrect.
System Action:
The NOTIFY event request is ignored. Processing of the application continues.
Action:
1700 - 1799
1743E
Unknown MONITOR event name: xxxxxxxx
Reason:
The application requested a job MONITOR event named xxxxxxxx, such as
JOBSTARTEVENT(xxxxxxxx), defined in the tracking model for the job. However, the
event name is incorrect.
System Action:
The MONITOR event request is ignored. Processing of the application continues.
Action:
Correct the tracking model.
1744E
Alert ID xxxx has bad event name
Reason:
The application requested an alert named xxxx. However, the event name specified in
the alert definition is incorrect.
System Action:
Action:
Either correct the alert name, or define the alert correctly.
1745E
Reason:
User is not authorized to trigger events in this group. This level of authorization is
System Action:
The event is not triggered
Action:
1700 - 1799
1746E
Reason:
System Action:
Action:
1747E
Reason:
System Action:
Action:
1700 - 1799
1748C
Event Initiator Display
Reason:
In response to EICLASS STATISTICS(DISPLAY) command, the Event initiator statistics is
displayed. For each defined Event initiator class a count of the currently defined,
maximum allowed and currently active Event initiators are displayed. For each Event
initiator the count of Events and jobs processed by that Event initiator are displayed, as
well as the event name, start time and consumed time of the processed events, which
consumed the highest CPU time and the highest elapsed time.
System Action:
Action:
None.
1749W
No ESP subsystems supporting explicit data set trigger API found
Reason:
An attempt was made to activate an explicit data set trigger using the ESPDST (alias
CYBESDT1) utility. However, no subsystem supporting the explicit data set trigger API
was found on the system. ESP versions earlier than 5.5 do not support the explicit data
set trigger API. Therefore the above message can be issued when the explicit data set
trigger utility (ESPDST or CYBESDT1) version is 5.5 or later and the system is running only
pre-5.5 ESP subsystem(s), or when no subsystems are active on the system.
System Action:
The explicit data set trigger utility ESPDST (alias CYBESDT1) exits with return code 4.
Action:
If there are only pre-5.5 ESP subsystems running on the system, then use a pre-5.5
version of the explicit data set trigger utility CYBESDT1 to activate the explicit data set
trigger. If there are no subsytems running on the system, then a version 5.5 or above
tracking the product that will respond to the explicit data set trigger activation should
be started.
1700 - 1799
1750I
Application aaaa, Generation bbbb is now Uncompleted
Reason:
The Application Manager uncompleted a completed application and the entire
application can rerun as a new subgeneration.
System Action:
Action:
None.
1751E
APPLICATION DATA SET aaaa NOT FOUND: APPL bbbb, GENERATION cccc, SLOT dddd
Reason:
While processing a request, the Application Manager could not find the data set that is
supposed to contain the tracking record for a specified application.
System Action:
The request fails. Processing continues.
Action:
This is probably due to an internal logic error. Contact CA Support.
1752E
I/O ERROR aaaa bbbb cccc
Reason:
While processing a request, the Application Manager encountered an I/O error during
operation aaaa (READING or WRITING) for record type bbbb (TRACKING RECORD,
PROCEDURE CACHING RECORD, or INDEX ENTRY) in application cccc. The error is
System Action:
Action:
support personnel.
1700 - 1799
1753E
TRACKING RECORD CANNOT BE RESTORED: APPL aaaa, GENERATION bbbb, SLOT cccc
Reason:
While processing a request, the Application Manager was unable to reactivate a
completed application. The application tracking record was deleted when the
application was marked complete, but the record is no longer intact and cannot be
restored.
System Action:
Action:
None.
1754E
APPL NOT UNCOMPLETED BECAUSE NOT COMPLETE: APPL aaaa, GENERATION bbbb,
SLOT cccc
Reason:
While processing a request, the Application Manager was attempting to reactivate an
application that was expected to have completed or been marked complete. According
to the application tracking record, the application is not complete.
System Action:
Action:
Retry the request. If this error persists, contact CA Support.
1700 - 1799
1755E
PROCEDURE CACHING RECORD CANNOT BE RESTORED: APPL aaaa, GENERATION
bbbb, SLOT cccc
Reason:
completed application. The application had a procedure caching record that was deleted
when the application was marked complete, but the record is no longer intact and
cannot be restored.
System Action:
Action:
None.
1756E
INDEX ENTRY NOT FOUND: APPL aaa, GENERATION bbb, SLOT ccc
Reason:
completed application. The application's index entry can no longer be found, most likely
because the index entry has been reused.
System Action:
Action:
None.
1700 - 1799
1757E
INDEX ENTRY NOT USABLE: APPL aaaa, GENERATION bbbb, SLOT cccc
Reason:
completed application. The application's index entry was found, but it was not usable.
System Action:
Action:
None.
1758E
ATTEMPT TO CREATE APMW FAILED RC=aaaa: APPL bbbb, GENERATION cccc, SLOT
dddd
Reason:
While processing a request, the Application Manager uncompleted a completed
application but was unable to queue a required control block.
System Action:
Action:
This should never happen, but in the unlikely event that it does, please contact CA
Support. If other messages were received before this message, they should be noted.
Messages that appear at the same time in the JESMSGLG and Auditlog might also be
relevant.
1700 - 1799
1759E
This operation is not supported for an externally scheduled application
Reason:
A user attempted an operation that is not allowed for externally scheduled applications
such as those generated for the z/OS Agent.
System Action:
The user request fails. Processing continues.
Action:
None.
1760E
Statement text too long: nnnn bytes over the limit
Reason:
The total size of job definition statements in APPLINS command exceeds the limit.
System Action:
Action:
Modify the command to make the statement block more. APPLINS command can
contain an INVOKE statement pointing to a data set with job definition text.
1761E
LongName(xxxx) is conflict with existing usable LONGNAME in Appl yyyy. Job not
inserted.
Reason:
An Agent INSERT message attempted to insert a job into an active application. However,
the job name specified in LongName() keyword is a usable LONGNAME of an existing
active job in the specified application.
System Action:
The insertion is rejected.
Action:
Change the job name in LongName() to a non-conflict name.
1700 - 1799
1767E
<keyword> specified with no JCLCHECK parameter
Reason:
The named keyword was specified on a SIMULATE command that did not also specify
the JCLCHECK keyword.
System Action:
Processing of the SIMULATE command is terminated.
Action:
Either remove the named keyword or else add the JCLCHECK keyword to the command.
1768E
CA-JCLCheck module not found
Reason:
The library containing the CA-JCLCheck modules was not available in the STEPLIB or
using the LNKLST.
System Action:
Action:
Correct the STEPLIB specification for the step.
1769W
CA-JCLCheck Common Services used
Reason:
The user requested JCLCheck to be invoked for this simulation. No expilcit request was
made for Common Services invocation but the program was unable to locate the full
JCLCheck product module.
System Action:
The Common Services invocation is used by default for this simulation.
Action:
None required.
1700 - 1799
1770E
No overrides specified
Reason:
The modeling OVERRIDE command does not specify any override operands. At least one
of the following override operands is required: CPUTIME(seconds),
EXECTIME|ELAPSED(minutes), CRITICAL, NOTCRITICAL.
System Action:
The OVERRIDE command is rejected.
Action:
Correct the OVERRIDE command to specify at least one override operand.
1771E
FOVMGR: Error in manager message format
Reason:
System Action:
Action:
Please contact CA Support for further assistance.
1772I
FOVMGR: Passing msg_verb msg_verbm to SensMgr for agent_name
Reason:
The Failover manager has intercepted a CONTROL message and it is being sent on to the
Senor manager.
System Action:
Action:
None required.
1700 - 1799
1773E
FOVMGR: Return code xxx from CYBES057 for agent_name
Reason:
The Failover manager attempted to send a status message to an agent but an error was
encountered during that process.
System Action:
Action:
Save the audit log and the JES job log and contact CA Support.
1774I
FOVMGR: Agent name changed from old_name to new_name
Reason:
An agent has changed its name while it was operating. This is usually caused by a "fail
over" of an agent within an agent cluster.
System Action:
Fail over processing is initiated for the agent.
Action:
None required.
1777I
FOVMGR Telling SensMgr of change from old_name to new_name
Reason:
An agent has changed its name while it was operating. The Failover manager is
informing the Sensor manager of that fact.
System Action:
Action:
None required.
1700 - 1799
1776I
FOVMGR: Msg <WOB message>
Reason:
This message will follow an error message by the Fail Over manager and it describes a
message sent to it by an agent.
System Action:
Action:
Refer to the previous message in the audit log to determine the nature of the problem.
1777C
Product License Status
Reason:
Response to LISTLMP or LLMP command.
System Action:
The CA license status of the primary product, and any installed optional CA product
components, is displayed.
Action:
If a product component license is about to expire or has expired, please contact CA.
1778E
<ddb> inconsistency detected
Reason:
A product Diagnostic Data Block module <ddb> contains unexpected version or licensing
information.
System Action:
The product terminates with a non-zero return code.
Action:
This problem should never occur. If it does, please contact CA Support.
1700 - 1799
1779E
CAIRIM has not run, cannot verify CA licensing for product.
Reason:
A product was started but the CA Resource Initialization module CAIRIM has not run.
CAIRIM initializes LMP, the CA License Management Program. Licensing for the product
cannot be verified until CAIRIM has run.
System Action:
The product terminates with a non-zero return code.
Action:
Start the product after CAIRIM has run.
1780W
<Message text>
Reason:
A JESOUT command issued to a subsystem or a Work Station Server resulted in a
condition, described in the message text, where the output spool file request could not
be met for the specified job.
System Action:
The JESOUT command request is not fulfilled.
Action:
If the condition is legitimate, for example the specified job has no processed spool
output files, then no action is necessary. If the JESOUT command specified incomplete
or incorrect operands, then re-issue the JESOUT with the correct operands.
1700 - 1799
1781E
<Message text>
Reason:
A JESOUT command issued to a subsystem or a Work Station Server resulted in an error
condition, described in the message text.
System Action:
Action:
Attempt to determine the cause of the error condition and correct it if possible. Then
re-issue the JESOUT command if appropriate. If the problem is persistent and cannot be
resolved, then contact your software support personnel.
1782W
<Message text>
Reason:
A JESOUT command issued to a TSO client resulted in a condition, described in the
message text, where the output spool file request could not be met for the specified
job.
System Action:
Action:
If the condition is legitimate, for example the specified job has no processed spool
output files, then no action is necessary. If the JESOUT command specified incomplete
or incorrect operands, then re-issue the JESOUT with the correct operands.
1700 - 1799
1783E
<Message text>
Reason:
A JESOUT command issued to a TSO client resulted in an error condition, described in
the message text.
System Action:
Action:
Attempt to determine the cause of the error condition and correct it if possible. Then
re-issue the JESOUT command if appropriate. If the problem is persistent and cannot be
resolved, then contact your software support personnel.
1784E
Reason:
An invalid parameter was coded on a command.
System Action:
Action:
Refer to Command Reference to check command syntax. Then re-issue command with
correct syntax if necessary.
1785C
JESOUT Command
Reason:
Response to JESOUT command with no operands.
System Action:
The JESOUT command syntax is displayed.
Action:
None.
1700 - 1799
1786W
LJS command not permissible on a proxy subsystem
Reason:
An LJS command was issued to a proxy subsystem. The LJS command accesses the
JOBSTATS file which is only available to the master.
System Action:
Action:
Re-issue the LJS command to a master subsystem.
1787W
JOBSTATS job|profile entry <name> not found
Reason:
LJS command response. The specified job or profile entry <name> was not found in the
JOBSTATS file.
System Action:
Action:
Re-issue the LJS command specifying an existing job or profile entry.
1788E
Unable to locate Job xxxx for update in Appl yyyy.nnn
Reason:
As a result of a change in NOTIFY parameters of a resubmitted job 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.
Action:
Contact CA Support.
1700 - 1799
1789E
Insufficient space in Appl record to update job xxxx in Appl yyyy
Reason:
The application record (ATR) does not have enough free space to modify or insert
NOTIFY parameters.
System Action:
The ATR is not updated.
Action:
1790E
TAPETRAK command invalid for non-tracking ESP/WM
Reason:
A TAPETRAK command has been issued to a subsystem that is not tracking jobs, that is a
subsystem that specifies "SMFINT ON" in its ESPPARM initialization file statement, or
defaults to "SMFINT ON".
System Action:
Action:
If the TAPETRAK command is specified in the ESPPARM initialization file of the
non-tracking subsystem, then remove it.
1791C
TAPETRAK HELP
Reason:
Response to TAPETRAK HELP command.
System Action:
Action:
None.
1700 - 1799
1792E
LIST and {NO}EXCLUDE mutually exclusive
Reason:
A TAPETRAK command has been issued with the incompatible operands LIST and
EXCLUDE or NOEXCLUDE.
System Action:
Action:
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
Reason:
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.
System Action:
Action:
Re-issue TAPETRAK command from a console if authorized to do so.
1794C
TAPETRAK Tape Tracking: Real {No}Virtual {Exclude: nnnn{-nnnn} {nnnn{-nnnn}} ...}
Reason:
Response to successful TAPETRAK command execution. Displays current tape tracking
status. nnnn specify tape device numbers.
System Action:
Action:
None.
1700 - 1799
1795E
RESOURCE NAME CAN NOT CONTAIN WILD CARD CHARACTERS ON THIS OPERATION
Reason:
Wild card characters (asterisk and dash) are not allowed with the ADD operand.
System Action:
The processing of this command is aborted.
Action:
Correct the command and retry it.
1796W
n jobs are missing from resfile, details in audit log
Reason:
The product 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.
Action:
Review the job list. Jobs whose records were lost while they were waiting for resource
will need a resubmission.
1798E
Condition string is too long
Reason:
The condition string specified in COND() keyword in RELEASE statement is longer than
4080 bytes, which is the maximum length.
System Action:
The processing on application is stopped.
Action:
Shorten the condition string to be within the limit and redo.
1800 - 1899
1799W
The execution frequency of event XXXX.XXXX is higher than allowed by the THRESH
operand.
Reason:
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.
Action:
Decrease the THRESH operand value to include more scheduled instances of the event
in the SADGEN data set.
1800 - 1899
1800I
ABOVE ERROR OCCURRED ON FOLLOWING STATEMENT{ IN JOB xxxx}
Reason:
The statement which follows appears in the procedure being executed.
System Action:
If an application is defined in the procedure, it is not processed.
Action:
Check the previous message for an explanation of the error.
1800 - 1899
1801I
n RECORDS WRITTEN TO SAD FILE
Reason:
The specified number of records were written to the SAD file as the result of the
SADGEN request.
System Action:
Action:
None required.
1802I
UNABLE TO ALLOCATE WORK FILE
Reason:
There is insufficient space to allocate work files.
System Action:
The work file is not allocated.
Action:
Wait until there is sufficient space available and then retry.
1803E
INSUFFICIENT BUFFER STORAGE
Reason:
There is insufficient memory available to complete the operation.
System Action:
The requested operation is not performed.
Action:
If this problem persists, recycle the subsystem.
1800 - 1899
1804C
JOBINFO FOR xxxx
Reason:
This is the JOBINFO listing.
System Action:
N/A.
Action:
N/A.
1805E
<type> not defined
Reason:
The dataset specified for either the JCLOPTS or JCLPROCLIB keyword cannot be found. If
it was specified as a DD name, the DD has not been defined in the JCL for the step. If it
was specified as a dataset name, the dataset could not be located in the catalog.
System Action:
Action:
If specifying a DD name, be that the DD name specified is defined in the JCL for the step.
If specifying a dataset name, be sure that the fully qualified name is entered and that it
specifies a cataloged dataset.
1800 - 1899
1806E
UNABLE TO PROCESS INPUT FILE
Reason:
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:
Action:
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
Reason:
The data set specified in the MODEL command was not a scheduled activity data set.
System Action:
The command processing is terminated.
Action:
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
Reason:
Recovery of the slot number was completed.
System Action:
None.
Action:
None.
1800 - 1899
1809I
Slot number is valid, unable to read above APPL
Reason:
There is missing data in the application file.
System Action:
Processing is halted for that application.
Action:
Support.
1810I
Error still occurred after second read with refreshed slot number
Reason:
There is an I/O error on the application file.
System Action:
Action:
Support.
1811I
Unable to locate index entry for this APPL generation
Reason:
There is missing data in the application file.
System Action:
Action:
Support.
1800 - 1899
1812E
INSUFFICIENT SPACE IN APPL RECORD TO INSERT JOB xxxx INTO APPL yyyy
Reason:
The application record does not have enough free space to insert the new job.
System Action:
The job is not inserted.
Action:
1813E
UNABLE TO LOCATE JOB xxxx FOR UPDATE IN APPL yyyy
Reason:
System Action:
Action:
1800 - 1899
1814W
UNABLE TO LOCATE APPL xxxx.nn SLOT yyyy FOR APPL PROCESSING REQUEST
Reason:
An application command (such as AJ) has been issued for an application which is no
longer active.
System Action:
Action:
This message should only be received when special diagnostic material has been
supplied by CA Support. When you receive this message, please contact CA 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
Reason:
There is extraneous information in the application file.
System Action:
Action:
None required.
1816W
EXISTING APPL xxxx.nn SLOT yyyy
Reason:
The slot for the appl in question is displayed.
System Action:
None.
Action:
None.
1800 - 1899
1817W
NEW APPL xxxx.nn SLOT yyyy
Reason:
The slot for the appl in question is displayed.
System Action:
None.
Action:
None.
1818W
NO ENTRIES FOUND TO MATCH YOUR SELECTION CRITERIA
Reason:
No jobs matched the LISTAPPL command criteria.
System Action:
None.
Action:
Select a different appl to display.
1819E
INVALID JOBNAME SPECIFICATION xxxx
Reason:
The parameters to the AJ command were invalid.
System Action:
The AJ command was not processed.
Action:
1800 - 1899
1820E
APPLICATION NAME MISSING
Reason:
The application name is missing from the AJ command.
System Action:
The AJ command is not executed.
Action:
Add an application name and try again.
1821W
NO FUNCTION SPECIFIED, COMMAND IGNORED
Reason:
No function name (such as, COMPLETE, HOLD, etc) was specified on the AJ command.
System Action:
The AJ command was not executed.
Action:
Add a function name and try again.
1822E
No jobs were eligible out of the nn jobs in Subappl xxxx
Reason:
No job names were found that matched the job specification in the AJ command.
System Action:
The AJ command is ignored.
Action:
Re-issue the AJ command with a valid job specification.
1800 - 1899
1823W
NO RESET TIMES SPECIFIED, COMMAND IGNORED
Reason:
In an AJ RESET command, neither EARLYSUB, LATESUB, LATEEND nor DROPEXEC were
specified.
System Action:
The AJ command was not executed.
Action:
1824E
INVALID APPLICATION SPECIFICATION xxxx
Reason:
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.
Action:
Correct the application name and try again.
1825E
INVALID REQUEST CODE ISSUED TO CYBES037
Reason:
System Action:
The SADLINK was not completed.
Action:
1800 - 1899
1826E
INVALID REQUEST CODE, xx, ISSUED TO CYBES038
Reason:
System Action:
Request is refused.
Action:
1827E
INVALID SCBUR REQUEST CODE DETECTED
Reason:
System Action:
None.
Action:
1828E
INCORRECT KEY LENGTH SPECIFIED FOR SCHEDULE FILE
Reason:
The ESPPARM data set specified a Schedule data set which had an incorrect keylength.
System Action:
Action:
1800 - 1899
1829I
SCHEDULE FILE DATA SET HAS NO VALID CONTROL RECORD, ONE WILL BE ADDED
Reason:
The Schedule data set contained no control record. A control record is always the first
System Action:
Action:
None.
1830E
XCF SCOREBD data received invalid, Master version too low, Partner=XXXX
Reason:
The Proxy is running on a version V5.5 or up, but the Master is running on a version V5.4
or less.
System Action:
The Proxy refuses to enter CSF.
Action:
Install the same version of Proxy and Master.
1831E
INVALID SUB-FUNCTION SPECIFIED
Reason:
The sub-function specified in command LAPX is invalid. Please refer to the manual for
the syntax of LAPX command.
System Action:
No output is shown.
Action:
Change the LAPX command.
1800 - 1899
1832W
Job jobname.qual in Appl applname.gen# Predicted to be Late
Reason:
The indicated job in the indicated Application is predicted to be late. This is determined
by adding the estimated run times of all its predecessors.
System Action:
Action:
Take whatever actions are appropriate to expedite predecessor jobs.
1833I
Job jobname.qual in Appl applname.gen# now Predicted to be On Time
Reason:
The indicated job in the indicated Application was previously predicted to be late (using
message 1832W), but is now predicted to be on time. This is determined by adding the
estimated run times of all its predecessors.
System Action:
Action:
Non required.
1834I
SCHEDULE FILE DATA SET EMPTY, WILL FORMAT
Reason:
An empty Schedule data set was detected. This is expected the first time the data set is
used.
System Action:
Action:
None, unless the Schedule data set is not supposed to be empty.
1800 - 1899
1835W
SUBJECT ignored - no MAILBOX specified
Reason:
A NOTIFY statement specified the SUBJECT keyword. However, no MAILBOX keyword
was supplied for the notification.
System Action:
The SUBJECT value is ignored.
Action:
Either remove the SUBJECT keyword or else add the appropriate MAILBOX keyword.
1836E
Option cannot be used with COMMON invocation
Reason:
The JCLCHECKPRINT parameter was specified along with the COMMON COMMON
parameter for a JCLCHECK request.
System Action:
Action:
Either remove the JCLCHECKPRINT parameter or else remove the COMMON parameter
for a full product invocation.
1837W
REASON STRING SPECIFIED FOR JOB XXXX WHICH IS NOT PLACED ON MANUAL HOLD,
IGNORED
Reason:
This message is issued when the REASON operand is used but the HOLD operand is not
specified in a JOB statement.
System Action:
The REASON operand is ignored. Processing continues.
Action:
Either remove the REASON operand or specify the HOLD operand.
1800 - 1899
1838E
Insufficient checkpoint space, agent message rejected
Reason:
A message just came from an Agent. However, insufficient checkpoint space was
available to process it.
System Action:
The message is rejected.
Action:
Investigate and remedy the reason for the shortage of checkpoint space.
1839E
REQUIRED SCOREBOARD ENTRY NOT FOUND
Reason:
System Action:
None.
Action:
Contact CA Support for further assistance.
1840E
SCHEDFILE RECORD NOT FOUND
Reason:
System Action:
None.
Action:
1800 - 1899
1841I
Late Prediction processing is ON(XX-hrs,YY-mins)/OFF
Reason:
The late prediction option is ON or OFF (set using the LATEPRED command). The user
can also issue the LATEPRED command to set the late Notify thresholds, which are XX
hours and YY minutes. This sets limits on the Notify so that it is not issued too far in
advance (XX hours), or for objects which are only a few minutes late (YY minutes).
System Action:
Action:
Non required.
1842E
Scoreboard request not valid from a proxy subsystem
Reason:
The user has requested a CSF function from a proxy subsystem.
System Action:
Action:
Scoreboard API requests can only be made from a proxy subsystem in 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
Reason:
A command was entered with no parameters when parameters were expected.
System Action:
Action:
Reenter the command with the correct parameters.
1800 - 1899
1850E
Reason:
System Action:
Action:
1851W
Reason:
A request was made to the subsystem while it was not active.
System Action:
Action:
1800 - 1899
1852E
ERROR SCANNING MODEL COMMAND, RC=nn
Reason:
A problem was encountered while parsing a MODEL command.
System Action:
Action:
respectively.
1853W
MODELLING NOT ACTIVE
Reason:
An attempt was made to enter a MODELLING command when the MODEL processor not
active.
System Action:
Action:
1800 - 1899
1854W
MODELLING NOT ACTIVE
Reason:
An attempt was made to enter a MODELLING command when the MODEL processor not
active.
System Action:
Action:
1855E
Reason:
System Action:
Action:
respectively.
1800 - 1899
1856I
File already exists
Reason:
A Putfile command was entered with the subparameter Putnew that specifies for Putfile
to check for the existence of the dsname in the Putfile command and if found use this
message without overwriting existing data.
System Action:
The pds dataset member is not overwritten.
Action:
If it is desired to overwrite an existing member then reissue the Putfile command as
before but without the Putnew parameter.
1859E
APPLICATION PROCESSING IS NOT ACTIVE
Reason:
A user issued a command related to the application processing function of the product.
That function is not active.
System Action:
Action:
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
Reason:
An application record retrieval failed because the required APPLFILE was closed.
System Action:
Action:
Determine the reason the file was closed. Retry when the file becomes available.
1800 - 1899
1861E
YOUR AUTHORITY IS INSUFFICIENT FOR ACCESS, OR APPLICATION xxxx NOT FOUND
Reason:
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:
Action:
Ensure the application name was specified correctly or grant the user sufficient access
to the application record.
1862W
Reason:
System Action:
Action:
1863E
xxxx NOT VALID WITHIN AN EVENT DEFINITION
Reason:
A subcommand was entered that is not valid within an EVENT definition.
System Action:
The subcommand is ignored.
Action:
Terminate the EVENT definition before reentering the subcommand.
1800 - 1899
1864E
xxxx NOT VALID OUTSIDE OF AN EVENT DEFINITION
Reason:
A subcommand was entered that is only valid within an EVENT definition.
System Action:
Action:
Specify the subcommand within an EVENT definition.
1865W
Reason:
System Action:
Action:
1800 - 1899
1866E
Reason:
System Action:
Action:
respectively.
1867I
Checking interval for late prediction is ssss seconds.
Reason:
The system will check all held and/or active jobs to predict late jobs in every 'ssss'
seconds.
System Action:
Action:
Non required.
1800 - 1899
1868E
Reason:
A problem was encountered while parsing the GENFLOW command line.
System Action:
Action:
respectively.
1869W
invalid resfile entry (entries) found, retained because esp quiesced.
Reason:
This usually happens when the user creates a new application file and start ESP in
quiesce mode to format it.
System Action:
The entry was left in the resfile.
Action:
None
1800 - 1899
1870E
COMMAND xxxx INVALID IN USER PROFILE DEFINITION TABLE
Reason:
A User Profile Definition Table contained an invalid command.
System Action:
Action:
Correct the table and reissue the LOADUPDT command.
1871E
xxxx
Reason:
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.
Action:
1872E
ABOVE ERROR OCCURRED OPENING USER PROFILE DEFINITION TABLE
Reason:
System Action:
Action:
1800 - 1899
1873E
INVALID COMMAND SYNTAX DETECTED IN LINE nn OF USER PROFILE DEFINITION
TABLE
Reason:
A User Profile Definition Table contained a statement with invalid syntax.
System Action:
Action:
Correct the table definition and reissue the LOADUPDT command.
1874E
ABOVE ERROR OCCURRED ON LINE nn OF USER PROFILE DEFINITION TABLE
Reason:
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:
Action:
Correct the error and reissue the LOADUPDT command.
1875E
Reason:
A WILDCARD statement in a User Profile Definition Table had an invalid character range.
System Action:
Action:
1800 - 1899
1876E
Reason:
A User Profile Definition Table was being loaded. The table contained more than 60
WILDCARD statements.
System Action:
Action:
1877E
INVALID MODEL SPECIFICATION xxxx
Reason:
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.
Action:
1878E
MODEL SPECIFICATION EXCEEDS 8 CHARACTERS
Reason:
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:
Action:
1800 - 1899
1879E
ABOVE ERROR OCCURRED READING USER PROFILE DEFINITION TABLE
Reason:
An error occurred while reading in a User Profile Definition Table. The error is described
System Action:
Action:
After the error is corrected, reissue the LOADUPDT command.
1880E
INSUFFICIENT CHECKPOINT SPACE TO QUEUE JOB xxxx IN APPL yyyy FOR SUBMISSION
Reason:
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.
Action:
1881E
Invalid request code issued to Resource Manager
Reason:
System Action:
None.
Action:
1800 - 1899
1882E
Invalid Resource Manager Anchor Block address passed to Resource Manager
Reason:
System Action:
None.
Action:
1883E
Insufficient access authority for requested function
Reason:
You are not authorized to define or manage resources.
System Action:
Action:
Contact your ESP administrator to arrange appropriate authority.
1884E
No Resfile data set name specified
Reason:
No RESFILE command was found in the initialization parameters.
System Action:
Resource management is not activated.
Action:
Add a RESFILE command to the initialization parameters.
1800 - 1899
1885E
Resfile DIV Identify error nn
Reason:
An error was encountered while opening the RESFILE data set.
System Action:
Resource management is not available.
Action:
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
Reason:
An error was encountered while accessing the RESFILE data set.
System Action:
Action:
1887E
Resfile DIV Map error nn
Reason:
An error was encountered while mapping the RESFILE data set.
System Action:
Action:
1800 - 1899
1888E
Insufficient Extended Private Area to Map the Resfile
Reason:
There is not enough memory to enable the product's resource management feature.
System Action:
Action:
Recycle the product with a larger region size.
1889E
Resfile data set xxxx contains invalid data
Reason:
The file named in the RESFILE initialization parameter is not a valid resource file.
System Action:
Action:
Correct the RESFILE command in the initialization parameters to point to a valid
resource file, and then recycle. Alternatively recycle the product with the RESFORM
option to format the named data set.
1890I
Resfile data set xxxx will be formatted
Reason:
The file named in the RESFILE initialization parameter will be formatted as a new
resource file.
System Action:
The Resource file is formatted.
Action:
None.
1800 - 1899
1891E
Resfile DIV Save error nn
Reason:
A data-in-virtual save operation onto the RESFILE has failed.
System Action:
None.
Action:
Refer to the IBM DIV documentation for an explanation of this DIV error code.
1892E
Resfile DIV UnIdentify error nn
Reason:
A data-in-virtual unidentify operation onto the RESFILE has failed.
System Action:
None.
Action:
1893E
Resfile DIV UnAccess error nn
Reason:
A data-in-virtual unaccess operation onto the RESFILE has failed.
System Action:
None.
Action:
1800 - 1899
1894E
Resfile DIV UnMap error nn
Reason:
A data-in-virtual unmap operation onto the RESFILE has failed.
System Action:
None.
Action:
1896W
Node xxxx not found
Reason:
In a RESOURCE statement, the value of the NODE parameter specified an undefined
node name.
System Action:
The resource is not defined.
Action:
Add a definition for the node.
1897I
CPU xxxx not found
Reason:
In a RESOURCE statement, the value of the CPU parameter specified an undefined CPU
name.
System Action:
Action:
Add a definition for the CPU.
1800 - 1899
1898I
Resource xxxx not found
Reason:
The RESOURCE DELETE statement specifies a resource which has not yet been defined.
System Action:
None.
Action:
Correct the RESOURCE statement, or remove it.
1899I
CPU xxxx not defined on Node yyyy
Reason:
In a RESOURCE statement, the value of the CPU parameter specified a CPU which is not
on the specified NODE.
System Action:
Action:
Change the RESOURCE statement to refer to the proper CPU or the proper NODE.
1900 - 1999
1900 - 1999
1900S
Resource file full
Reason:
There is not sufficient free space in the rsource file to process the current resource
request
System Action:
The resource manager terminates with ABENDU4001.
Action:
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
Reason:
Too many resources have been defined.
System Action:
The resource was not defined.
Action:
Increase the maximum possible number of resources by changing the RESFILE command
in the initialization parameters. The MAXRES parameter on this command specified the
maximum number of resources that can be defined.
1900 - 1999
1902E
Resource xxxx already defined
Reason:
A RESOURCE ADD statement names a resource that has already been defined.
System Action:
The resource is not redefined.
Action:
Remove either one of the RESOURCE ADD statements for this resource.
1903I
Resource xxxx defined
Reason:
The resource named in the RESOURCE ADD statement has been successfully defined.
System Action:
None.
Action:
None.
1904C
Resource Display
Reason:
Following this message will be the result of a RESOURCE LIST command.
System Action:
N/A
Action:
N/A
1900 - 1999
1905I
No matching Resources found
Reason:
A RESOURCE LIST command was issued, but no matching resource names were found in
the resource file.
System Action:
Action:
Re-issue the RESDEF LIST command with a valid resource name specification.
1906I
No Resources defined
Reason:
A RESOURCE LIST command was issued, but no resources have been defined in this
resource file.
System Action:
None.
Action:
Restart the product with a different resource file, or define some resources in this
resource file.
1907W
Resource xxxx not deleted, it is in use
Reason:
A resource cannot be deleted while some job is waiting for it.
System Action:
The resource was not deleted.
Action:
Wait until no jobs are waiting for this resource, and then delete it.
1900 - 1999
1908I
Resource xxxx updated
Reason:
The resource definition has been updated as a result of a RESOURCE SET command.
System Action:
None.
Action:
None.
1909I
Node xxxx defined
Reason:
A new node has been successfully defined.
System Action:
None.
Action:
None.
1910I
Node xxxx deleted
Reason:
A Node definition was successfully removed from the Resfile after a NODE xxxx DELETE
command was issued.
System Action:
None. The request was successful.
Action:
None.
1900 - 1999
1911I
Node xxxx modified
Reason:
The node definition has been modified as a result of a NODE SET command.
System Action:
None.
Action:
None.
1912C
Node Display
Reason:
A display of the definition of this node will follow.
System Action:
N/A
Action:
N/A
1913I
Resource xxxx deleted
Reason:
A resource has been deleted as a result of a RESOURCE DELETE command.
System Action:
The resource has been deleted.
Action:
None.
1900 - 1999
1914W
No matching Nodes found
Reason:
There are no nodes whose name matches the specification given in the NODE LIST
command.
System Action:
None.
Action:
Correct the node name specification and try again.
1915W
Node xxxx not defined
Reason:
The node specified in a NODE SET or NODE DELETE command has not been defined.
System Action:
None.
Action:
Correct the node name and try again.
1916E
Node xxxx already defined
Reason:
The node name specified in a NODE ADD command has already been defined.
System Action:
The node was not redefined.
Action:
Correct the node name and try again.
1900 - 1999
1917I
CPU xxxx defined
Reason:
The CPU ADD statement has successfully defined a CPU.
System Action:
N/A
Action:
N/A
1918I
CPU xxxx deleted
Reason:
A CPU delete request was successful in removing all references to a CPU from the
Resfile.
System Action:
None. The request was successful.
Action:
None.
1919I
CPU xxxx modified
Reason:
The CPU SET command has successfully changed the definition of this CPU.
System Action:
N/A
Action:
N/A
1900 - 1999
1920C
CPU Display
Reason:
Following this message is a display of the definition of a CPU.
System Action:
N/A
Action:
N/A
1921I
No matching CPUs found
Reason:
A CPU DISPLAY command was entered, but no CPUs were found that match the
specification.
System Action:
No CPUs were displayed.
Action:
Correct the CPU name specification and try again.
1922E
The maximum of nn has been reached
Reason:
Too many CPUs have been defined.
System Action:
The CPU was not defined.
Action:
Increase the maximum possible number of CPUs by changing the RESFILE command in
the initialization parameters. The MAXCPU parameter on this command specified the
maximum number of CPUs that can be defined.
1900 - 1999
1923W
CPU xxxx not defined
Reason:
The CPU specified in a CPU SET or CPU DELETE command has not been defined.
System Action:
None.
Action:
Correct the CPU name and try again.
1924E
CPU xxxx already defined
Reason:
A CPU ADD statement names a CPU that has already been defined.
System Action:
None.
Action:
Remove either one of the CPU ADD statements for this CPU.
1925W
No Nodes defined
Reason:
In a CPU ADD command, no NODE parameter was specified, and no nodes have yet
been defined.
System Action:
The CPU was not defined.
Action:
Define at least one node before this CPU definition.
1900 - 1999
1926W
Node xxxx not found for job yyyy
Reason:
Node affinity failed for this job.
System Action:
The job is not processed.
Action:
Check the Affinity keyword in the resource definitions to make sure it is correct.
1927W
CPU xxxx not found for job yyyy
Reason:
The resource needed was not found.
System Action:
Action:
Correct the resource definitions and retry.
1928W
Resource xxxx not found for job yyyy
Reason:
The resource needed was not found.
System Action:
Action:
Correct the resource definitions and retry.
1900 - 1999
1929W
No UCBs found for unit name xxxx
Reason:
The DEVICE parameter of a RESOURCE ADD statement specified a unit name with which
no UCBs are associated.
System Action:
None.
Action:
Correct the unit name with the RESOURCE SET DEVICE(...) statement and try again.
1933E
Resource name xxxx is invalid
Reason:
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:
Action:
Specify a valid name.
1934I
ABOVE ERROR OCCURRED ON FOLLOWING STATEMENT
Reason:
The following statement in the procedure was in error.
System Action:
The statement was not processed.
Action:
1900 - 1999
1935I
xxxx
Reason:
An error has been detected while processing this statement.
System Action:
The statement was not processed.
Action:
Check the previous messages for further information.
1936E
Cannot change available count for renewable resource xxxx.
Reason:
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.
Action:
None
1937W
WLM type xxxxx is different from one or more WLM types for resource yyyyy
Reason:
A RESDEF SET command was issued specifying a WLM type value which was different
from one or more WLM types currently in effect for the same resource.
System Action:
The RESDEF command is allowed.
Action:
The user should make sure that the correct value has been specified.
1900 - 1999
1938E
Resfile DIV Reset error nn
Reason:
A data-in-virtual reset operation on the Resource file has failed.
System Action:
None.
Action:
1939E
Reason:
System Action:
Action:
respectively.
1900 - 1999
1940E
DATA SET TRIGGERING NOT RESTARTED, RESYNCH IN PROGRESS
Reason:
The operator issued a DSTRST RESTART command, but a data set trigger resynchronize
operation initiated by CYBESUDI is in progress.
System Action:
Action:
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
Reason:
No applications were found that matched the specification on the GENPROJ command.
System Action:
The GENPROJ command was not executed.
Action:
Correct the Application specification and re-issue the command.
1942I
Application xxxx.nn no longer on APPLFILE
Reason:
The GENPROJ command refers to an Application which is no longer available on the
APPLFILE.
System Action:
Action:
Correct the Application specification and re-issue the command.
1900 - 1999
1943W
Invalid Application specification xxxx
Reason:
The Application name specified to the GENPROJ command was not valid. The
application name must be no longer than eight characters, and may 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.
Action:
Correct the application name and try again.
1944W
Requested generation of Application xxxx not found
Reason:
The GENPROJ command requested a specific generation of an Application. The
Application generation did not exist.
System Action:
Action:
Use the LISTAPPL command to confirm the existence of the specified Application and
generation.
1945W
GMT TIME xxxx ON yyyy zzzzaaaa bbbb
Reason:
discrepancy was found between the Local and GMT time. Message 0897W precedes this
message for local time.
System Action:
Action:
1900 - 1999
1946W
INVALID RESPONSE
Reason:
System Action:
Action:
1947W
INVALID RESPONSE
Reason:
System Action:
Action:
1949E
JOB INDEX AND TRACKFILE BOTH NEEDED FOR APPLFILE OPTION
Reason:
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:
Action:
Update the initialization parameter data set to define both data sets. Restart the
product.
1900 - 1999
1950E
QUEUE DATA SET NEEDED FOR APPLFILE OPTION
Reason:
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:
Action:
The queue data set should be defined by adding the QUEUE parameter to the
initialization parameter data set.
1951I
xxxx
Reason:
In debug mode, the subsystem initialization module is being invoked directly by the
product.
System Action:
None.
Action:
None.
1952E
SUBSYSTEM ID xxxx IN USE BY ANOTHER SUBSYSTEM
Reason:
The subsystem ID is being used by some system other than the product.
System Action:
The product will not start.
Action:
Choose a different subsystem ID for the product, and then restart it.
1900 - 1999
1953I
QUEUE DATA SET HAS BEEN DAMAGED AT OP REQ
Reason:
The queue data set has been purposely corrupted by the @CRPTQUE command.
System Action:
Action:
None required.
1954I
THERE ARE NO FREE ELEMENTS IN QUEUE
Reason:
The @CRPTQUE command was issued, but there are no queue elements to be
corrupted.
System Action:
None.
Action:
None.
1955W
xxxx
Reason:
System Action:
None.
Action:
1900 - 1999
1956I
OK
Reason:
The previously entered command has completed successfully.
System Action:
None.
Action:
None.
1957I
SHUTDOWN COMMAND ACCEPTED
Reason:
A SHUTDOWN command has been entered, and the product is commencing shutdown
processing.
System Action:
ESP is shutdown.
Action:
None.
1958I
ALREADY QUIESCED
Reason:
A QUIESCE command was entered, but the product is already quiesced.
System Action:
None.
Action:
None.
1900 - 1999
1959I
QUIESCING
Reason:
The product is entering quiesce mode.
System Action:
None.
Action:
None.
1960I
RESTARTING
Reason:
The product is resuming normal operation, after having been quiesced.
System Action:
ESP resumes normal operation.
Action:
None.
1961W
NOT QUIESCED
Reason:
A RESTART command was entered, but the product was not quiesced.
System Action:
Action:
None.
1900 - 1999
1962I
DATA SET TRIGGERING RESUMED
Reason:
A RESUME DSTRIG command was just entered.
System Action:
The product has resumed data set triggering.
Action:
None.
1963I
DATA SET TRIGGERING NOT SUSPENDED
Reason:
A RESUME DSTRIG command was just entered, but data set triggering had not been
suspended.
System Action:
None.
Action:
None.
1964I
DATA SET TRIGGERING ALREADY SUSPENDED
Reason:
The DSTRST command specified SUSPEND, but data set triggering is already suspended.
System Action:
None.
Action:
None.
1900 - 1999
1965I
DATA SET TRIGGERING SUSPENDED
Reason:
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.
Action:
To resume data set triggering, issue the DSTRST RESUME command.
1966I
DATA SET TRIGGERING RESTARTED
Reason:
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.
Action:
None.
1967I
DATA SET TRIGGERING NOT QUIESCED
Reason:
The DSTRST command specified RESTART, but data set triggering is not quiesced.
System Action:
None.
Action:
Resubmit the command with the appropriate operands.
1900 - 1999
1968I
DATA SET TRIGGERING ALREADY QUIESCED
Reason:
The DSTRST command specified QUIESCE, but data set triggering is already quiesced.
System Action:
None.
Action:
None.
1969I
DATA SET TRIGGERING QUIESCED
Reason:
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.
Action:
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
Reason:
Data set triggers are no longer being written to the system log.
System Action:
Data set trigger logging is deactivated.
Action:
To resume logging of data set triggers, issue the DSTRST LOG command.
1900 - 1999
1971I
DATA SET TRIGGER LOGGING NOT ACTIVE
Reason:
The DSTRST command specified NOLOG, but logging of data set triggers is not active.
System Action:
None.
Action:
Resubmit the command with the appropriate operands.
1972I
DATA SET TRIGGER LOGGING ALREADY ACTIVE
Reason:
The DSTRST command specified LOG, but logging of data set triggers is already active.
System Action:
None.
Action:
None.
1973I
DATA SET TRIGGER LOGGING ACTIVATED
Reason:
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.
Action:
To stop logging of data set triggers, issue the DSTRST NOLOG command.
1900 - 1999
1974I
DATA SET TRIGGERING {SUSPENDED|ACTIVE}{ (QUIESCED)}, {NO}LOG
Reason:
This message is in response to a DSTRST command without operands. It displays the
current status of data set triggering.
System Action:
None.
Action:
None.
1975I
QUPDATE REQUEST QUEUED
Reason:
The QUPDATE command has been accepted.
System Action:
The product will do a JES status and update the P-Node queue information.
Action:
None.
1976I
QUPDATE REQUEST ALREADY QUEUE
Reason:
A QUPDATE command is already in progress.
System Action:
None.
Action:
None.
1900 - 1999
1977I
ESP release xxxx status
Reason:
This message introduces the display of processing status.
System Action:
None.
Action:
The messages that follow will describe processing status.
1978I
EVENT SCHEDULING {QUIESCED|ACTIVE}
Reason:
This message indicates the status of the event scheduling function.
System Action:
None.
Action:
None.
1979I
DATA SET TRIGGERING {SUSPENDED|ACTIVE} {(QUIESCED)} {(RESYNCHING)}
Reason:
This message indicates the status of data set triggering function.
System Action:
None.
Action:
None.
1900 - 1999
1980I
EVENTSET xxxx IS IN SUSPENDED STATE
Reason:
This event has been suspended with the SUSPEND command.
System Action:
None.
Action:
This event may be resumed by issuing the RESUME command.
1981I
ROSCOE PROC NAME NOT SET
Reason:
In response to a ROSCOE command without operands, this message indicates that the
ROSCOE proc name has not yet been established.
System Action:
None.
Action:
Specify the name of a ROSCOE proc with the ROSCOE command.
1982I
ROSCOE PROC SET TO xxxx
Reason:
In response to a ROSCOE command without operands, this message indicates the name
of the ROSCOE proc.
System Action:
None.
Action:
None.
1900 - 1999
1983C
DEFAULT USER
Reason:
This message introduces the response to the LDFLTU command.
System Action:
None.
Action:
None.
1984W
NO DEFAULT USER DEFINED
Reason:
In response to a LDFLTU command, this message indicates that no default user has been
defined.
System Action:
None.
Action:
If required, define a default user.
1985C
TRACKMODEL BUFFER DISPLAY
Reason:
This message introduces the response to the LISTJTML command.
System Action:
None.
Action:
None.
1900 - 1999
1986W
Dependency loop found at xxxx releasing yyyy in appl aaaa
Reason:
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, such as 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.
Action:
Correct the dependency loop.
1987E
Command invalid on proxy
Reason:
A command that is only valid on a master subsystem was issued to a proxy subsystem.
System Action:
Action:
Issue the command to the master subsystem.
1900 - 1999
1988W
Owner zzzz of Event xxxx.yyyy no longer defined to ESP. Execution continues
Reason:
The product is executing an Event owned by a Userid that has been deleted from the
User Definition File.
System Action:
Execution continues.
Action:
Either reinstate the Userid or update the Event. After updating the event become the
new owner.
1989E
xxxx
Reason:
This error occurred while trying to validate the user that was associated with a
time-delayed event.
System Action:
Action:
See message 1990 which follows this one. The user may not be authorized.
1990E
EVENT xxxx.yyyy NOT EXECUTED DUE TO ABOVE I/O ERROR
Reason:
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.
Action:
Refer to the previous ESP1989 message for further information on this error.
1900 - 1999
1991W
EVENT ALTERATION SUPPRESSED BY INSTALLATION EXIT
Reason:
The installation exit has prevented this event from being altered.
System Action:
The event is not altered.
Action:
Your installation does not allow events to be altered.
1992I
INSUFFICIENT DATA SPACE TO UPDATE EVENT xxxx.yyyy
Reason:
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.
Action:
Reduce the number of items in the event and trigger the event again.
1993E
EVENTSET ID xxxx NOT FOUND
Reason:
The ALTEVENT command specified an invalid EVENTSET name.
System Action:
The event was not altered.
Action:
Correct the EVENTSET parameter and try again.
1900 - 1999
1994W
UNABLE TO QUEUE DIRECTLY TO SYSTEM xxxx
Reason:
An Event was defined or triggered to execute on another system. The QUEUE data set
was unavailable so the local system was unable to queue it to the requested system.
System Action:
Action:
1995W
SYSTEM xxxx NOT MEMBER OF SHARED QUEUE
Reason:
An Event was defined or triggered to execute on another system. The designated system
was not sharing the QUEUE data set. The local system was unable to queue it to the
requested system.
System Action:
Action:
1900 - 1999
1996W
EVENT DEFINITION SUPPRESSED BY INSTALLATION EXIT
Reason:
Your installation has suppressed the event definition.
System Action:
None.
Action:
None.
1997W
EVENT DATASET WITH ID xxxx NOT FOUND
Reason:
The DEFERRED parameter in a LISTSCH command specified an event data set that is not
defined to the product.
System Action:
No entries are listed.
Action:
Correct the DEFERRED parameter and try again.
1998W
THERE ARE NO EVENTS ON THE OVERDUE QUEUE
Reason:
A LISTSCH OVERDUE command was issued, but there are no overdue events.
System Action:
None.
Action:
None.
1900 - 1999
1999W
NO EVENTS HELD IN CLASS xxxx
Reason:
A LISTSCH HELD command was issued, but there are no held events on the specified
hold class.
System Action:
None.
Action:
Correct the hold class and resubmit the command.

2000 - 2099
2000E
DUPLICATE ISCDEF COMMAND ISSUED
Reason:
More than one ISCDEF command appeared in the initialization stream.
System Action:
Each ISCDEF except the first is ignored.
Action:
Remove the extraneous ISCDEF command(s).
2001E
ISCDEF STATEMENT MUST PRECEDE ISCXMTR
Reason:
An ISCXMTR statement was encountered for an NJE job trackintransmitter, but no
ISCDEF statement had been processed.
System Action:
The ISCXMTR statement is ignored.
Action:
Ensure that the ISCDEF statement precedes any ISCXMTR statement that defines an NJE
job tracking transmitter.
2000 - 2099
2002E
INVALID FUNCTION CODE PASSED TO CYBIS000
Reason:
An internal logic error has occurred.
System Action:
The Inter-System communication process is not started.
Action:
2003E
SUBSYSTEM FUNCTION ERROR CODE xx, SYSOUT RECEIVER TERMINATING
Reason:
The product received an unexpected subsystem error code from JES.
System Action:
The receive portion of this ISC terminates.
Action:
2004E
SUBSYSTEM REQUEST ERROR CODE xx, SYSOUT RECEIVER TERMINATING
Reason:
The product received an unexpected return code from JES.
System Action:
The receive portion of this ISC terminates.
Action:
2000 - 2099
2005E
ERROR ENCOUNTERED BY SYSTEM RECEIVER
Reason:
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.
Action:
2006E
<variable text describing the I/O error>
Reason:
A synchronous I/O error occurred reading an ISC data set from JES.
System Action:
Action:
2007E
INVALID TRANSACTION RECORD ENCOUNTERED BY SYSOUT RECEIVER
Reason:
ISC received a record from JES which does not have the correct header information in it.
System Action:
Action:
2000 - 2099
2008E
ON DATA SET xxxxxxxx
Reason:
This message provides the name of the data set being processed when the error causing
message 2007E to be issued was detected.
System Action:
Action:
2009E
CHAR=cccc HEX=xxxx
Reason:
Inter System Communication module received bad transmission. Character format is
cccc, hex format is xxxx.
System Action:
Processing of this transmission terminates. ISC waits for the next receiving.
Action:
If problem persists contact your software support personnel.
2010E
DATASET xxxx IS NOT SEQUENTIAL
Reason:
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.
Action:
Allocate a sequential data set and reissue the command.
2000 - 2099
2011E
WILDCARDS NOT ALLOWED IN SUBAPPL
Reason:
A LAP command with the SUBAPPL keyword was specified. However, the SUBAPPL
parameter value contained wildcard characters.
System Action:
Action:
Re-issue the corrected command.
2013E
{DE}SELECTED SUBAPPL xxxx NOT DEFINED
Reason:
The selected or deselected sub-application was not defined in the procedure with a
SUBAPPL statement.
System Action:
The procedure will not run.
Action:
Either define the sub-application with a SUBAPPL statement, or delete the erroneous
{DE}SELECT statement.
2014E
SUCCESSOR LOOP DETECTED: xxxxyyyy
Reason:
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.
Action:
Correct the dependencies and re-run the application.
2000 - 2099
2015W
OWNER is valid only for links and tasks, ignored
Reason:
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.
Action:
Correct the job definition by removing the OWNER keyword.
2016I
nn jobs will be selected for rerun: j1, j2,....
Reason:
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
Action:
Review the job list. If it is followed by a prompt, reply to it.
2017E
Parm string too long, up to nnn bytes allowed
Reason:
The rerun parameter string coded in RerunM command exceeds the allowed limit.
System Action:
RerunM command is aborted.
Action:
Reenter the command with correct parm string.
2000 - 2099
2018E
Application <name.gen> is already complete
Reason:
RerunM command was entered for a completed application. Jobs in completed
applications cannot be resubmitted.
System Action:
Action:
N/A.
2019I
nn jobs selected for rerun
Reason:
This is a response from subsystem after it processed RerunM command. The number of
jobs is reported back to the user.
System Action:
N/A.
Action:
N/A.
2020E
ERROR ALLOCATING SYSOUT DATA SET FOR SYSOUT TRANSMITTER xxxxxxxx
Reason:
The product 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.
Action:
2000 - 2099
2021E
<variable message text>
Reason:
This message provides details of the open error causing message 2022E to be issued.
System Action:
Action:
2022E
ERROR OCCURRED OPENING DATA SET FOR SYSOUT TRANSMITTER xxxxxxxx
Reason:
The product 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:
Action:
2023E
Insufficient storage for rerun parameters
Reason:
RerunM command could not modify the application record: there was not enough room
for rerun parameters.
System Action:
Action:
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.
2000 - 2099
2024E
Request denied: insufficient authority
Reason:
The request to application manager failed an authorization check.
System Action:
Action:
Ask the security administrator for help.
2025W
Resource file is nn% full
Reason:
nn refers to the two-digit percentage of the resource file currently in use. When the
percentage of the resource file that is currently in use exceeds the 50%, 70%, 90% or
99% margin, Message 2025W tells you this percentage.
System Action:
Action:
To prevent the product from abending,
1.
Stop the product.
2.
Use IDCAMs REPRO to copy the data from the Resource file to a sequential file.
3.
Define a bigger VSAM file. Make the new primary allocation the sum of the current
primary allocation's size plus the size of all current secondary allocations. It is
recommended that the new secondary allocation be a non zero.
4.
Use IDCAMS REPRO to copy the data to the new VSAM file.
5.
Update SIZE initialization parameter in the RESFILE statement.
2000 - 2099
2026I
Resource file usage is down to nn%
Reason:
The Resource file had filled to a level that warrants user attention, and now the usage
has gone down to the value shown.
System Action:
Action:
None.
2027I
Resource file has been expanded. Space allocated: aaaa, used: uuuu bytes.
Reason:
The Resource file was successfully expanded because it has filled up, or because the
user increased the value of the RESFILE SIZE initialization parameter.
System Action:
Action:
None.
2000 - 2099
2028E
An attempt to expand Resource file failed
Reason:
The product's attempt to expand the Resource file failed. This message is accompanied
by other messages describing the failure.
System Action:
If the product tried to expand the Resource file during initialization because the user
increased the value of the RESFILE SIZE parameter, then processing will continue
normally. Otherwise, the product tried to increase the Resource file because it has filled
up and therefore the product will terminate.
Action:
Allocate a bigger Resource file, copy the contents of the old file into it using the REPRO
function of IDCAMS, increase the value of the RESFILE SIZE initialization parameter and
restart the product with the new file.
2029I
SYSOUT TRANSMITTER xxxxxxxx HAS SPUN A DATA SET WITH nnn RECORDS
Reason:
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.
System Action:
None.
Action:
None.
2000 - 2099
2030E
Resource file expansion limit reached
Reason:
The product needs to store a record in the Resource 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 session.
System Action:
The Resource file will not be expanded.
Action:
Simply restarting the product will provide a new 4M expansion window, but it is better
to allocate a bigger Resource file, copy the contents of the old file into it using the
REPRO function of IDCAMS, increase the value of the RESFILE SIZE initialization
parameter and restart the product with the new file.
2031I
Resource file was reorganized with maximum CPU of nn
Reason:
The Resource file was successfully reorganized with a maximum CPU of nn, because the
user increased the value of the RESFILE MAXCPU initialization parameter.
System Action:
Action:
None.
2000 - 2099
2032E
An attempt to reorganize the Resource file with maximum CPU of nn failed.
Reason:
The MAXCPUS (maximum CPU usage) value in the RESFILE initialization parameter
statement was increased. During startup, the product tried to reorganize the Resource
file with the new setting, but it failed because the Resource file was too small.
System Action:
The product recovers the Resource file and abends.
Action:
Decrease the MAXCPUS value to its original value or enlarge the Resource file. To
enlarge the Resource file
1.
Use IDCAMS REPRO to copy the data from the Resource file to a sequential file.
2.
Define a larger VSAM file. Make the new primary allocation the sum of the current
primary allocation's size plus the size of all current secondary allocations. It is
recommended that the new secondary allocation be a non zero.
3.
Use IDCAMS REPRO to copy the data to the new VSAM file.
4.
Update SIZE initialization parameter in the RESFILE statement.
2033E
HISTFILE <histid> not found or is closed for application [assign the value for appl in
your book].<gen>
Reason:
At the completion of an application, the product attempted to write an Application
History Record to the history file. However, the history file with the ID <histid> could not
be found, or is closed or suspended.
System Action:
The Application History Record is dropped. Processing continues.
Action:
Check that the history file identified in the message is defined to the product. 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.
2000 - 2099
2034E
Above error occurred writing <histfile> record for application xxx
Reason:
An I/O error occurred when the tracking manager attempted to write the history record
for the named application. This message is preceded by a message describing the actual
error.
System Action:
Processing continues, but the history information is lost.
Action:
Investigate the cause of the error, and take appropriate action.
2035W
Slot file, "xxxxFile", is nn% full
Reason:
xxxx refers to a particular slot file ('Appl' or 'Trak'). nn refers to the currently used
percentage of the named file. Each time the percentage exceeds the 50%, 70%, 90% or
99% margin, message 2035W is issued.
System Action:
Processing continues. Another 2035W message will be issued if a higher margin is
reached. Message 2036I will be issued if the percentage decreases.
Action:
Once you reach the 90% margin consider increasing the file size:
APPLFILE:
1.
Stop the product.
2.
Run the CYBESUT3 utility (see System Programmer's Guide).
3.
Verify the 'APPLBUF', 'APPLFILE', and 'SLOTSIZE' Initparms.
4.
Restart the product.
TRAKFILE:
1.
Stop the product.
2.
Run the CYBESUT4 utility (see System Programmer's Guide).
3.
Verify the 'TRAKFILE' Initparm.
4.
Restart the product.
2000 - 2099
2036I
Slot file, "xxxxFile", usage is down to nn%
Reason:
xxxx refers to a particular slot file ('Appl' or 'Trak'). nn refers to the currently used
percentage of the named file. The named slot file had filled to a level that may warrant
attention, but now the usage has gone down to the value shown.
System Action:
Processing continues. Message 2035W is issued if the file usage increases.
Action:
None.
2037I
Importing Job Statistics data
Reason:
Job Statistics data set is found to be empty, which means that this is the first time to run
the product version with JOBSTATS file. So need to gather existing job statistics
information to Job Statistics data set.
System Action:
Existing job statistics information will be added to JOBSTATS file.
Action:
None.
2038I
Importing complete, xxxx jobs and xxxx entries inserted
Reason:
Existing job statistics information has been added to Job Statistic data set. The total
numbers of jobs and entries are indicated.
System Action:
The product continue processing.
Action:
None.
2000 - 2099
2039E
Record length of xxxxxxxx is too small
Reason:
The record length of Job Statistics file JOBSTATS is specified too small.
System Action:
Action:
Specify a bigger record length and redefine JOBSTATS data set.
2040S
Job Statistics data set xxxx unusable
Reason:
the Job Statistics data set.
System Action:
Action:
can be restarted.
2041E
Incorrect key length specified for Job Statistics data set
Reason:
The ESPPARM data set specified a Job Statistics data set which had an incorrect
keylength.
System Action:
Action:
2000 - 2099
2042I
Job Statistics data set has no valid control record, one will be added
Reason:
The Job Statistics data set contained no control record. A control record is always the
first record in the data set.
System Action:
Action:
None.
2043I
Job Statistics data set empty, will format
Reason:
An empty Job Statistics data set was detected. This is expected the first time the data
set is used.
System Action:
Action:
None, unless the Job Statistics data set is not supposed to empty.
2044I
Job Statistics data set has no valid default Profile Definition record, one will be added
Reason:
The Job Statistics data set contained no default Profile Definition record. The default
Profile Definition record is normally the second record in the data set.
System Action:
A default Profile Definition record will be built and written out.
Action:
None.
2000 - 2099
2045I
Next JOBSTATS data set backup at xxxx on yyyy
Reason:
This message displays when the next backup will be for the Job Statistics data set.
System Action:
None.
Action:
To change the backup schedule, use the BKUPJSTS command with a valid scheduling
criterion. To perform an immediate backup, use the BKUPJSTS command with no
operands.
2046I
No JOBSTATS backup time set
Reason:
A BKUPJSTS command was issued to display the next backup time for the Job Statistics
data set, but no backup time has been scheduled.
System Action:
None.
Action:
To change the backup schedule, use the BKUPJSTS command with a valid scheduling
criterion. To perform an immediate backup, use the BKUPJSTS command with no
operands.
2000 - 2099
2047E
No CHECKPOINT space available
Reason:
There is no space in the checkpoint file with which to record a backup schedule for the
Job Statistics data set.
System Action:
No backup has been scheduled for the Job Statistics data set.
Action:
Wait until some scheduled events have been triggered, and try again. To perform an
immediate backup of the Job Statistics data set, use the BKUPJSTS command with no
operands.
2048I
No old Resources found
Reason:
There were no resources matching the date criteria specified.
System Action:
The product response to a "RESDEF - {LIST} LASTUSED(date)" command.
Action:
None.
2049E
LastUsed date/time criteria unresolvable
Reason:
The LASTUSED date criteria was incorrect or missing.
System Action:
The product response to a "RESDEF - LIST/DEL LASTUSED(date)" command.
Action:
Specify a valid date criteria.
2000 - 2099
2050I
Starting backup of Job Statistics
Reason:
A backup of the Job Statistics data set has begun.
System Action:
The Job Statistics data set is backed up.
Action:
None.
2051E
Command invalid on proxy
Reason:
A command that is only valid on a master subsystem was issued to a proxy subsystem.
System Action:
Action:
Issue the command to the master subsystem.
2052E
Backup of Job Statistics data set ended with errors
Reason:
A previous error has caused termination of the Job Statistics data set backup. This
message will have been preceded by another message describing the error.
System Action:
Action:
2000 - 2099
2053I
Job Statistics data set backup ended, nn records backed up
Reason:
A backup of the Job Statistics data set has completed successfully.
System Action:
Action:
None.
2054E
Error closing Job Statistics backup data set, xxxx
Reason:
System Action:
Action:
can be may be executed again.
2055E
Error opening Job Statistics backup data set xxxx
Reason:
An error occurred while opening a backup data set for the Job Statistics data set.
System Action:
Action:
be executed again.
2000 - 2099
2056E
Error writing to Job Statistics backup data set xxxx
Reason:
An error occurred while writing to the backup data set for the Job Statistics data set.
System Action:
Action:
be executed again.
2057E
Job Statistics data set backup time will have to be reset
Reason:
System Action:
Action:
Use the BKUPJSTS command to set the scheduled backup time.
2058E
No backup data set specified for Job Statistics data set
Reason:
The product attempted to take a backup of the Job Statistics data set. A backup data set
was not specified in the initialization parameters.
System Action:
Action:
restarted.
2000 - 2099
2059E
JOB STATISTICS DATA SET XXXX UNUSABLE
Reason:
An error, described by the preceding message, has prevented the product SADGEN
processing from accessing the job statistics data set.
System Action:
Action:
1.
Notify your software support personnel. after the error has been corrected, the
2.
Run SADGEN processing with 'NOHIST' option.
2060E
Invalid job name xxxx
Reason:
A command specified an invalid job name xxxx. A job name must conform to the
following rules - The length may not exceed 64 characters. The first character must be
alphabetic (upper or lower case) or national (@, # or $). The remaining characters must
be alphanumeric, a period (.) or an underscore (_). There must not be two consecutive
periods. The last character must not be a period (.). For MVS job names, characters
preceding the 1st period, or the entire job name if no period exists, must conform to
MVS job name rules, except alphabetics may be lower case.
System Action:
Action:
Re-issue the command specifying a valid job name.
2000 - 2099
2061E
Insufficient space in pool xxxxxxxx for nn byte LJNA
Reason:
A storage request could not be satisfied to accommodate a job name due to insufficient
space.
xxxxxxxx - specifies the storage pool address.
nn - specifies the size of the job name storage request and should be within the
range 10-73.
System Action:
Processing continues but a job name could not be copied to an internal data area. This
may or may not be a serious situation. This condition should not normally occur.
Action:
2062E
<function> <message error reason>
Reason:
A job name related error condition occurred.
<function> - Specifies an internal job name function and may be one of the
following: VFYJOBNM, GENJOBNM, CPYJOBNM, CMPJOBNM, GETLJNA, FREELJNA,
GENJOBQF.
<message error reason> - Describes what the error was.
System Action:
Processing continues but a job name related function could not be performed. This may
or may not be a serious situation. This condition should never occur.
Action:
2000 - 2099
2067W
LONGNAME invalid {for MVS job|when long job name specified}, ignored
Reason:
The LONGNAME keyword operand was specified for a workload object other than an
agent-run job or for a job defined with a long job name positional operand. A long job
name has more than 8 characters preceding and/or following the 1st period, or more
than 8 characters if no period exists.
System Action:
The erroneous LONGNAME keyword operand is ignored. Processing continues.
Action:
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.
Reason:
User specified a SCOPE parameter value in the JOB/JOBATTR statement which exceeds
the maximum that could be accommodated by control blocks.
System Action:
The value in the SCOPE parameter is set to 546 hours. Processing continues.
Action:
Correct the value in the SCOPE parameter as needed.
2000 - 2099
2069W
LONGNAME <longname> in job <jobname> unusable as long job name: <reason>
Reason:
An application job definition command for job <jobname> specified an invalid long job
name <longname> in the LONGNAME keyword operand. Either <longname> does not
conform to long job name syntax rules or there is an inconsistency with another long job
name in the application. <reason> specifies why <longname> is invalid. A LONGNAME
specification should conform to the following syntax rules: The length may not exceed
64 characters. The first character should be alphabetic (upper or lower case) or national
(@, # or $). The remaining characters should be alphanumeric, a period (.) or an
underscore (_). There should not be two consecutive periods. The last character should
not be a period (.).
System Action:
The long job name is marked unusable and processing continues. An unusable long job
name will not be used in job name displays and cannot be used to reference the job in
commands.
Action:
If possible, correct or remove the LONGNAME specification. CA recommends replacing
the LONGNAME specification in the job definition with a positional operand long job
name. If the user does not wish to correct the LONGNAME specification and considers
this warning message to be a nuisance, USERMOD 58 can be set to suppress this
message.
2070E
Invalid MVS job name xxxx
Reason:
An application JOB command specified a job name xxxx that does not conform to MVS
job name syntax rules. Characters preceding the 1st period, or the entire job name if no
period exists, must conform to MVS job name rules, except alphabetics may be lower
case.
System Action:
The entire procedure is aborted.
Action:
Correct the erroneous job name specification and re-trigger the event.
2000 - 2099
2072E
Unexpected mismatch processing job <job1{.<qual1>}, current job is <job2{.<qual2>}
Reason:
An application procedure command that references a job other than the current job, is
being processed. This is an internal logic error and should never occur. <job1{.<qual1>}
is the job referenced by the command being processed. <job2{.<qual2>} is the current
application job.
System Action:
The entire application procedure is aborted.
Action:
2073E
Long job name <jobname> conflict with prior LONGNAME reference
Reason:
An application procedure command incorrectly specifies a job name <jobname> that
corresponds to a LONGNAME(<jobname>) specification in a previous non-MVS job
definition command in the procedure. This error can occur on any of the following
application commands: AFTER, COREQ, POSTREQ, PREREQ, RELEASE, SELECT.
System Action:
Action:
The LONGNAME(<jobname>) specification in the previous conflicting non-MVS job
definition command can be removed and replaced by the <jobname> positional
operand (this option is recommended), or the flagged command can be modified to
specify <name>{.<qual>}, where <name> is the short job name and <qual> is the
optional job qualifier in the previous conflicting non-MVS job definition command. After
the correction is made, the application procedure can rerun.
2000 - 2099
2074E
LONGNAME <jobname> conflict with prior long job name reference
Reason:
An application procedure non-MVS job definition command incorrectly specifies
LONGNAME(<jobname>), where <jobname> corresponds to a long job name reference
in a previous command, which may be one of the following:
AFTER, COREQ, POSTREQ, PREREQ, RELEASE, SELECT.
System Action:
Action:
The LONGNAME(<jobname>) specification in the non-MVS job definition command can
be removed and replaced by the <jobname> positional operand (this option is
recommended), or the previous conflicting command can be modified to specify
<name>{.<qual>}, where <name> is the short job name and <qual> is the optional job
qualifier in the non-MVS job definition command that specifies
LONGNAME(<jobname>). After the correction is made, the application procedure can
rerun.
2075W
LONGNAME invalid when long obj name specified, Appl yyyy
Reason:
The LONGNAME keyword operand was found in an Agent INSERT message, which
already has a long job name found in the object id. A long job name has more than 8
characters preceding and/or following the 1st period, or more than 8 characters if no
period exists.
System Action:
The erroneous LONGNAME keyword operand is ignored. Processing continues.
Action:
Correct the INSERT message by removing the LONGNAME keyword.
2000 - 2099
2076W
LONGNAME xxxx syntax invalid, unusable as long job name
Reason:
An Agent INSERT message specified an invalid long job name in the LONGNAME
keyword operand. A LONGNAME specification should conform to the following rules The length may not exceed 64 characters. The first character should be alphabetic
(upper or lower case) or national (@, # or $). The remaining characters should be
alphanumeric, a period (.) or an underscore (_). There should not be two consecutive
periods. The last character should not be a period (.).
System Action:
The long job named is marked unusable and processing continues. An unusable long job
commands.
Action:
If possible, correct or remove the LONGNAME specification. It is recommended to
replace the LONGNAME specification in the Agent INSERT message with a long job name
specified in the object id. If the user does not wish to correct the LONGNAME
specification and considers this warning message to be a nuisance, USERMOD 58 can be
set to suppress this message.
2077W
LONGNAME(xxxx) already exists in Appl yyyy
Reason:
An Agent INSERT message attempted to insert a job into an active application. However,
the job name specified in LONGNAME() keyword was already used by an active member
of the specified application.
System Action:
The long job named is marked unusable and processing continues. An unusable long job
commands.
Action:
If possible, correct or remove the LONGNAME specification. It is recommended to
replace the LONGNAME specification in the Agent INSERT message with a long job name
specified in the object id.
2000 - 2099
2078E
Wrong condition code xxxx found in Pred/Succ parameter for updating job yyyy in
Appl zzzz
Reason:
The condition keyword specified in an ACTION INSERT message is invalid. The valid
codes include A, U, N, COND or NOMARK.
System Action:
The job is not updated or inserted.
Action:
Correct the condition keyword in Pred() or Succ() parameter.
2079I
SHR PARAMETER WILL BE IGNORED FOR HISTFILE xxxx
Reason:
SHR parameter was specified on HISTFILE command for history data set xxxx.
System Action:
The parameter is ignored. Processing continues.
Action:
None.
2080I
SHR PARAMETER WILL BE IGNORED FOR HISTFILE xxxx
Reason:
SHR parameter was specified on HISTFILE command for history data set xxxx.
System Action:
The parameter is ignored. Processing continues.
Action:
None.
2000 - 2099
2081I
HISTFILE xxxx IS NOT USED ON PROXY AND WILL BE SUSPENDED
Reason:
HISTFILE OPEN command was issued on proxy for data set xxxx.
System Action:
The product does not open the specified history data set. It will be suspended.
Action:
None.
2082E
STEPRC: Invalid <parameter>
Reason:
The specified parameter of the STEPRC function has incorrect format. The parameter
can be a step name or a completion code. Step name must be enclosed in single quotes
and contain a period separating the proc step name (the name on an EXEC statement in
an invoked procedure) from the step name (the name in the job's JCL).
The completion code that does not represent an abend can be a number or a range (two
numbers separated by a semicolon) without quotes. An abend code must be in quotes
and begin with either S or U.
System Action:
Simulation ends with an error condition. This error will not be reported in real event
execution. At run time, the function will return FALSE.
Action:
Correct the error.
2083E
INCREMENT|DECREMENT invalid for RESDEF ADD
Reason:
Response to RESDEF ADD command. Either the INCREMENT or DECREMENT keyword
operand was specified. INCREMENT and DECREMENT are valid for the RESDEF SET
command, but not for the RESDEF ADD command.
2000 - 2099
System Action:
The RESDEF ADD command is ignored.
Action:
If required, specify the RESDEF ADD command without the INCREMENT or DECREMENT
keyword operands.
2084E
AVAIL invalid when INCREMENT or DECREMENT specified
Reason:
Response to RESDEF SET command. The AVAIL operand was specified along with the
INCREMENT or DECREMENT operand. AVAIL is mutually exclusive with INCREMENT and
DECREMENT.
System Action:
The RESDEF SET command is ignored.
Action:
If required, reissue the RESDEF SET command the AVAIL operand or the INCREMENT or
DECREMENT operand.
2088E
I/O error occurred writing Procedure Caching Record for appl yyyy
Reason:
The product encountered an error while updating an APPLFILE entry for a Procedure
Caching Record of appl yyyy. The nature of the error is described in the preceding
message.
System Action:
The Procedure Caching Record(PCR) is not updated. Processing continues.
Action:
2000 - 2099
2089E
Insert request error: found conflict job name with job jjjj LONGNAME(xxxx) in appl
aaaa.nnnn
Reason:
An attempt was made to insert a job with name xxxx or LONGNAME(xxxx) into
generation nnnn of application aaaa. This is a job name conflict with an existing job with
name jjjj and LONGNAME(xxxx) in the application.
System Action:
Action:
Change the name xxxx in the job name or LONGNAME keyword specified in the inserting
procedure.
2090E
Reason:
message.
System Action:
The Procedure Caching Record(PCR) is not built. Processing continues.
Action:
2000 - 2099
2091E
I/O error occurred reading Procedure Caching Record for appl yyyy
Reason:
The product was trying to update Procedure Caching Record, but there was an error
encountered while reading an APPLFILE entry for a Procedure Caching Record of appl
yyyy. The nature of the error is described in the preceding message.
System Action:
A cached copy will be made by re-reading a procedure. Processing continues.
Action:
2092E
Insufficient space in Procedure Caching Record for appl yyyy
Reason:
The Procedure Caching Record(PCR), where the product was storing elements for
cached procedures for appl yyyy, has run out of space.
System Action:
Action:
2093E
Only one TEMPPROC command is allowed in event definition
Reason:
During Event definition, more than one TEMPPROC commands were entered.
System Action:
Action:
Leave only one TEMPPROC command and re-save the Event definition.
2000 - 2099
2094I
ESP Procedure yyyy is unavailable in Procedure Caching Record in APPLFILE, appl xxxx,
a new copy will be built
Reason:
The product was unable to locate and/or validate Procedure Caching Record for
application generation xxxx, or Procedure yyyy was not found in Procedure Caching
Record for this generation.
System Action:
Processing continues. A new copy of procedure(s) associated with application xxxx will
be made in memory allocated for Procedure caching as well as in Procedure Caching
Record for this generation.
Action:
None.
2095E
An error detected in USETIME statement of ESP procedure XXXX
Reason:
An error was detected in USETIME statement of procedure XXXX.
System Action:
Processing of the event stops.
Action:
Correct the USETIME statement.
2096E
Insufficient space in Procedure Caching Record for appl yyyy
Reason:
The Procedure Caching Record(PCR), where the product was storing elements for
cached procedures for appl yyyy, has run out of space.
System Action:
Action:
Contact CA Support.
2000 - 2099
2097E
Reason:
message.
System Action:
Action:
2098E
Invalid Procedure Caching Record detected for appl yyyy, PCR slot nn
Reason:
The product was trying to build a copy of a cached procedure in memory using as an
input the Procedure Caching Record, which failed validity check.
System Action:
The product produces SVC dump. A cached copy will be made by re-reading a
procedure. Processing continues.
Action:
Capture the SVC dump and contact CA Support.
2100 - 2199
2099E
I/O error occurred reading Procedure Caching Record for appl yyyy
Reason:
The product was trying to build a copy of a cached procedure in memory using as an
input the Procedure Caching Record, but there was an error encountered while reading
an APPLFILE entry for a Procedure Caching Record of appl yyyy. The nature of the error
is described in the preceding message.
System Action:
The product produces SVC dump. A cached copy will be made by re-reading a
procedure. Processing continues.
Action:
2100 - 2199
2100C
INET Command Options
Reason:
Response to an "INET HELP" command. Lists all valid "INET" command options.
System Action:
Action:
None.
2100 - 2199
2101E
INET command missing
Reason:
An "INET" command was issued without any parameters.
System Action:
Action:
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
Reason:
The parameter immediately following "INET" in an "INET" command is invalid.
System Action:
Action:
Enter an "INET" command with valid parameters. Or enter "INET HELP", "INET H" or
2103E
INET xxxx object missing
Reason:
An "INET xxxx" command was entered that required at least one additional parameter.
System Action:
Action:
Enter the "INET xxxx" command with valid parameters. Or enter "INET HELP", "INET H"
or "INET ?" for a list of "INET" command options.
2100 - 2199
2104E
INET xxxx object yyyy invalid
Reason:
Parameter 'yyyy' in the command "INET xxxx yyyy" is invalid for the command "INET
xxxx".
System Action:
Action:
Enter an "INET xxxx" command with valid parameters. Or enter "INET HELP", "INET H" or
2105E
INET xxxx not an initialization command
Reason:
An "INET" command was issued while CA Workload Automation EE 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.
System Action:
Action:
Remove the "INET" command from the initialization parameters.
2100 - 2199
2106I
TCP/IP={IBM({HPNS|IUCV}), Job=xxxxxxxx|Interlink(TCPaccess), API=yyyy, DNR=zzzz}
Reason:
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.
System Action:
Action:
None.
2107E
INET SET HOST_CACHE TTL interval missing
Reason:
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.
Action:
Re-enter the "INET SET HOST_CACHE" or "INET T HC" command specifying a valid TTL
(time to live) interval in seconds, that is a number within the range 0-99999999. For
example: INET SET HOST_CACHE TTL(3600)
2108C
Host Cache
Reason:
Response to an "INET DISPLAY HOST_CACHE" command. Displays TCP/IP host cache host
names and corresponding IP addresses.
System Action:
Action:
None.
2100 - 2199
2109I
Host cache empty, TTL (time to live) = 30 seconds.
Reason:
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.
Action:
None.
2110I
Host cache flushed
Reason:
Response to an "INET FLUSH HOST_CACHE" command.
System Action:
Action:
None.
2123E
IPv4 address {<ipv4_address> rejected|invalid}|missing
Reason:
An instance of the product specified an invalid IPv4 address or failed to specify an IPv4
address when one was expected while performing a TCP/IP request.
System Action:
The TCP/IP is rejected.
Action:
Internal logic error. Should never happen. If it does, call CA Support.
2100 - 2199
2124I
Host cache time to live interval set to nnnn seconds
Reason:
Response to "INET SET HOST_CACHE" or "INET T HC" command. The TTL interval has
been set to the indicated value.
System Action:
None.
Action:
None.
2125E
INET QUERY HOST object missing
Reason:
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:
Action:
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
Reason:
Response to "INET QUERY HOST" or "INET Q H" command. The command entered did
contained an improper host name.
System Action:
Action:
Re-enter the "INET QUERY HOST" or "INET Q H" command specifying a valid TCP/IP host
name.
2100 - 2199
2127I
Host xxxx not found
Reason:
Response to "INET QUERY HOST" or "INET Q H" command. The host name could not be
resolved.
System Action:
None.
Action:
None.
2128I
Host xxxx, Address nnn.nnn.nnn.nnn
Reason:
Response to "INET QUERY HOST" or "INET Q H" command. The host name was resolved
to the indicated IP address.
System Action:
None.
Action:
None.
2100 - 2199
2129E
Host cache entry <host> gives <ipv6>, IPv6 not supported
Reason:
A pre-11.3 ESP release was requested to perform a host cache lookup for a DNS host
name <host) that resolves to IPv6 address <ipv6>. This entry was probably created by a
Network Delivery Services (NDS) process and requested by an Agent communication
process. Network Delivery Services (NDS) supports IPv6 prior to release 11.3 but agent
communication does not.
System Action:
The requested process fails.
Action:
Correct any Agent (or other) command so that it does not specify a DNS host name that
resolves to an IPv6 address. As of CA Workload Automation EE release 11.3 this will not
be necessary, and the above message should never appear.
2131E
INET PURGE TASK object missing
Reason:
An "INET PURGE TASK" command was issued without specifying the task ID.
System Action:
Action:
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.
2100 - 2199
2132E
INET PURGE TASK object xxxx invalid
Reason:
Parameter 'xxxx' in the command "INET PURGE TASK xxxx' specifies an invalid task ID.
System Action:
Action:
caution.
2133I
Default TCP close option set to {reset|shutdown}
Reason:
Response to "INET DISPLAY CLOSE", "INET D CL", "INET SET CLOSE" or "INET T CL"
command. The current default TCP close option is displayed.
System Action:
None.
Action:
None.
2100 - 2199
2134E
INET SET CLOSE option (SHUTDOWN|RESET) missing
Reason:
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:
Action:
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
Reason:
An "INET" command was issued while CA Workload Automation EE TCP/IP component
was still initializing. The command cannot cannot be processed until TCP/IP initialization
is complete.
System Action:
Action:
Wait for TCP/IP initialization to complete and re-issue the command.
2100 - 2199
2136S
TCP/IP InitCall issued under subtask
Reason:
A TCP/IP initialization call was issued in Workload Automation EE under a subtask.
System Action:
Action:
2137W
TCP/IP stack set to HPNS, requested IUCV is obsolete
Reason:
A CA product request to set its TCP/IP stack to IUCV was issued. Under the product, the
TCPIP command in the ESPPARM initialization file specifies IUCV. Under the 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 CA.
System Action:
The CA product sets its TCP/IP stack to IBM's HPNS instead of IUCV.
Action:
Under the product, 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 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 WSS, the TCPIUCV parameter should be changed to TCPIBM or
TCPHPNS, or removed in order to default to IBM/HPNS.
2100 - 2199
2138E
INET SET BIND option (REUSEADDR|NOREUSEADDR) missing
Reason:
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:
Action:
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
Reason:
Response to "INET DISPLAY BIND", "INET D B", "INET SET BIND" or "INET T B" command.
The current TCP bind option is displayed.
System Action:
None.
Action:
None.
2100 - 2199
2140C
TCP/IP Activity
Reason:
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.
System Action:
Action:
None.
2141I
No TCP/IP activity
Reason:
Response to "INET DISPLAY ACTIVE" command. The TCP/IP stack is IBM's IUCV.
System Action:
Action:
None.
2142E
INET PURGE ID not supported under IBM IUCV TCP/IP
Reason:
Response to "INET PURGE ID" command. An individual pending socket function cannot
be purged under IBM's IUCV TCP/IP.
System Action:
Action:
None.
2100 - 2199
2143E
INET PURGE TASK object xxxxxx not found
Reason:
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:
Action:
caution.
2144I
INET PURGE TASK xxxxxx complete
Reason:
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.
System Action:
Action:
None. *** Warning **** "INET PURGE TASK" should be used with caution.
2100 - 2199
2145E
Invalid port number xxxx
Reason:
An invalid port number was passed to the TCP/IP component of CA Workload
Automation EE. 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.
Action:
Correct the TCP/IP port number parameter.
2146E
Invalid port number length nn
Reason:
The length of a port number passed to the TCP/IP component of CA Workload
Automation EE exceeds 5 characters. This is normally the result of an incorrect user port
number parameter specification. The TCP/IP stack is IBM's IUCV.
System Action:
Action:
2150C
TCP/IP Activity
Reason:
Interlink Software's TCPaccess.
System Action:
Action:
None.
2100 - 2199
2151I
No TCP/IP activity
Reason:
Response to "INET DISPLAY ACTIVE" command. The TCP/IP stack is Interlink Software's
TCPaccess.
System Action:
Action:
None.
2152E
INET PURGE ID object nn not found
Reason:
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:
Action:
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
Reason:
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.
System Action:
Action:
None. *** Warning **** "INET PURGE ID" should be used with caution.
2100 - 2199
2154E
Reason:
not exist or does not have any active TCP/IP sockets. The TCP/IP stack is Interlink
Software's TCPaccess.
System Action:
Action:
caution.
2155I
Reason:
task have been purged. The TCP/IP stack is Interlink Software's TCPaccess.
System Action:
Action:
2100 - 2199
2156W
nn second time out closing connection to raddr:rport, sent data may be lost
Reason:
CA Workload Automation EE was attempting to close a TCP 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.
Action:
Attempt to determine the reason for the remote connection partner's failure to respond
to the local CA Workload Automation EE'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
Reason:
CA Workload Automation EE was attempting to close a TCP connection with remote
partner raddr:rport in an orderly manner. However, an error occurred 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.
Action:
None.
2100 - 2199
2160I
Listening on port nnnn, QLen=nn
Reason:
CA Workload Automation EE TCP/IP server is listening for incoming connection requests
on the specified port. The TCP/IP stack is IBM's IUCV.
System Action:
Action:
None.
2161I
Connected to server raddr:rport
Reason:
CA Workload Automation EE TCP/IP client has connected to a remote server. The TCP/IP
stack is IBM's IUCV.
System Action:
Action:
None.
2162I
Connected to client raddr:rport
Reason:
CA Workload Automation EE TCP/IP server has accepted a connection request from a
remote client. The TCP/IP stack is IBM's IUCV.
System Action:
Action:
None.
2100 - 2199
2164W
nn second time out on receive from raddr:rport
Reason:
CA Workload Automation EE TCP/IP receive has timed out. The TCP/IP stack is IBM's
IUCV.
System Action:
The TCP/IP socket is closed.
Action:
None.
2165E
function{(n)}{, {*:lport}{->|<-}{raddr:rport}}, error, Sock=nn, id=nn, Task=xxxxxx
Reason:
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:
Action:
Attempt to determine the cause of the error, and correct it. If the problem is serious,
call your software support personnel.
2166W
function{(n)}{, {*:lport}{->|<-}{raddr:rport}}, info, Sock=nn, id=nn, Task=xxxxxx
Reason:
An unusual TCP/IP socket function event has occurred. The TCP/IP stack is IBM's IUCV.
System Action:
Action:
None.
2100 - 2199
2167E
XTCP xxxx, TIRA token yyyyyyyy invalid
Reason:
CA Workload Automation EE 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:
Action:
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 your software support personnel.
2168S
TCP/IP InitCall issued after initialization has completed
Reason:
A TCP/IP initialization call was issued in CA Workload Automation EE after TCP/IP
initialization completed. The TCP/IP stack is IBM's IUCV.
System Action:
Task is abended with code U2911
Action:
2170I
Listening on port nnnn, QLen=nn
Reason:
CA Workload Automation EE TCP/IP server is listening for incoming connection requests
on the specified port. The TCP/IP stack is Interlink Software's TCPaccess.
System Action:
Action:
None.
2100 - 2199
2171I
Reason:
stack is Interlink Software's TCPaccess.
System Action:
Action:
None.
2172I
Reason:
remote client. The TCP/IP stack is Interlink Software's TCPaccess.
System Action:
Action:
None.
2173W
nn second time out on connect to raddr:rport
Reason:
A time out occurred while CA Workload Automation EE TCP/IP client was attempting to
connect to a remote host. The TCP/IP stack is Interlink Software's TCPaccess.
System Action:
Application dependant.
Action:
Identify the reason why the remote host is unreachable and correct it.
2100 - 2199
2174W
nn second time out on receive from raddr:rport
Reason:
CA Workload Automation EE TCP/IP receive has timed out. The TCP/IP stack is Interlink
System Action:
Action:
None.
2175E
DNRfunc, DNRarg, SSID=xxxx, error, DPLRTNCD=yyyyyyyy, Task=zzzzzz
Reason:
A TCP/IP DNR (Domain Name Resolver) function error has occurred in CA Workload
Automation EE. The function is usually "Get Host by Name". The TCP/IP stack is Interlink
System Action:
Action:
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
Reason:
An error occurred in CA Workload Automation EE attempting to connect to (AOPEN) or
disconnect from (ACLOSE) TCP/IP. The TCP/IP stack is Interlink Software's TCPaccess.
System Action:
The TCP/IP application terminates.
Action:
Ensure that TCPaccess is up and running and the product is correctly configured to
access it.
2100 - 2199
2177E
APIfunc{(n)}{, {*:lport}{->|<-}{raddr:rport}}{, Qlen=nn}, RC=nn, error,
TPLRTNCD=xxxxxxxx, id=nn, Task=yyyyyy
Reason:
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.
Action:
2178W
APIfunc{(n)}{, {*:lport}{->|<-}{raddr:rport}}{, Qlen=nn}, RC=nn, info,
TPLRTNCD=xxxxxxxx, id=nn, Task=yyyyyy
Reason:
An unusual TCP/IP socket function event has occurred. The TCP/IP stack is IBM's
System Action:
Action:
None.
2100 - 2199
2179E
Reason:
longer exists, or never existed. The TCP/IP stack is Interlink Software's TCPaccess.
System Action:
Action:
2181S
Invalid DNRA, id=xxxxxxxx
Reason:
An invalid DNRA (Domain Name Request Area) was used by CA Workload Automation EE
product to request a TCP/IP service. The TCP/IP stack is IBM's IUCV.
System Action:
Action:
2182S
TCP/IP DNR request xx invalid
Reason:
An invalid TCP/IP DNR (Domain Name Resolver) request was made by CA Workload
Automation EE. The TCP/IP stack is IBM's IUCV.
System Action:
Action:
2100 - 2199
2183S
Invalid TIRA, id=xxxxxxxx
Reason:
An invalid TIRA (TCP/IP Request Area) was used by CA Workload Automation EE to
request a TCP/IP service. The TCP/IP stack is IBM's IUCV.
System Action:
Action:
2184S
TCP/IP API request xx invalid
Reason:
An invalid TCP/IP request was made by CA Workload Automation EE. The TCP/IP stack is
IBM's IUCV.
System Action:
Action:
2185S
CPE TCP/IP does not currently support xxxx
Reason:
CA Workload Automation EE requested a TCP/IP function that is not currently
supported. The TCP/IP stack is IBM's IUCV.
System Action:
Action:
2100 - 2199
2190S
Reason:
initialization completed. The TCP/IP stack is Interlink Software's TCPaccess.
System Action:
Action:
2191S
Reason:
to request a TCP/IP service. The TCP/IP stack is Interlink Software's TCPaccess.
System Action:
Action:
2192S
Reason:
Automation EE The TCP/IP stack is Interlink Software's TCPaccess.
System Action:
Action:
2100 - 2199
2193S
Reason:
request a TCP/IP service. The TCP/IP stack is Interlink Software's TCPaccess.
System Action:
Action:
2194S
Reason:
System Action:
Action:
2195S
Reason:
The TCP/IP stack is Interlink Software's TCPaccess. The functions GETHOSTBYADDR,
GETSERVBYPORT, GETHOSTNAME, and UDP are not currently supported.
System Action:
Action:
2200 - 2299
2200 - 2299
2200C
TCP/IP Activity
Reason:
IBM's HPNS.
System Action:
Action:
None.
2201I
No TCP/IP activity
Reason:
Response to "INET DISPLAY ACTIVE" command. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
None.
2200 - 2299
2202E
INET PURGE ID object nn not found
Reason:
Response to an "INET PURGE ID nn" command. The specified TCP/IP socket does not
exist. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
2203I
INET PURGE ID nn complete
Reason:
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.
System Action:
Action:
None. *** Warning **** "INET PURGE ID" should be used with caution.
2200 - 2299
2204E
Reason:
not exist or does not have any active TCP/IP sockets. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
caution.
2205I
Reason:
task have been purged. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
2200 - 2299
2206E
Invalid port number xxxx
Reason:
An invalid port number was passed to the TCP/IP component of CA Workload
Automation EE. This is normally the result of an incorrect user port number parameter
specification. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
2207E
Invalid port number length nn
Reason:
The length of a port number passed to the TCP/IP component of a CA Workload
Automation EE exceeds 5 characters. This is normally the result of incorrect user port
number parameter specification. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
2210I
Listening on {<ip_address>:|port }CA Portal, QLen=nn
Reason:
A product TCP/IP server is listening for incoming TCP connection requests on IP address
<ip_address>, if specified, and TCP port number CA Portal. The TCP/IP stack is
IBM/HPNS or CA-TCPaccess/HPNS.
System Action:
Action:
None.
2200 - 2299
2211I
Reason:
stack is IBM's HPNS.
System Action:
Action:
None.
2212I
Reason:
remote client. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
None.
2200 - 2299
2213W
<interval> second time out on connect to <remote_ip>:<remote_port> { from
<local_ip>}
Reason:
A time-out occurred while a product TCP/IP client was attempting to connect to a
remote TCP listener. The TCP/IP stack API is IBM HPNS or CA-TCPaccess HPNS. <interval>
specifies the time-out value in seconds. <remote_ip> specifies the remote connect IP
address. <remote_port> specifies the remote connect TCP port number. <local_ip>
specifies the local bind IP address.
System Action:
Action:
Identify the reason why the remote host is unreachable and correct it.
2214W
nn second time out on {send to|receive from} raddr:rport
Reason:
CA Workload Automation EE TCP/IP send or receive has timed out after nn seconds. The
TCP/IP stack is IBM's HPNS.
System Action:
Action:
None.
2200 - 2299
2215E
function{(n)}{, {*:lport}{->|<-}{raddr:rport}}, error, Sock=nn, id=nn, Task=xxxxxx
Reason:
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:
Action:
2216W
function{(n)}{, {*:lport}{->|<-}{raddr:rport}}, info, Sock=nn, id=nn, Task=xxxxxx
Reason:
An unusual TCP/IP socket function event has occurred. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
None.
2217E
Reason:
longer exists, or never existed. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
2200 - 2299
2218S
Reason:
initialization completed. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
2219W
<nn> second time out on TCP accept, Port=<port>
Reason:
A time out occurred while CA Workload Automation EE TCP listener was waiting for
incoming connection requests from remote hosts. The TCP/IP stack is IBM's HPNS. <nn>
specifies the time out value in seconds. <port> specifies the listener's TCP port number.
System Action:
Action:
If the conditions is abnormal, attempt to identify the reason why the listener timed out
on the TCP accept and attempt to correct it. If there is a problem that cannot be
corrected, contact your software support personnel.
2220E
Bind|Connect address <ipv6_address>:<port> invalid, IPv6 not supported
Reason:
An instance of the product specified an IPv6 address on a socket BIND or CONNECT to a
TCP/IP stack that does not support IPv6.
System Action:
The socket BIND or CONNECT is rejected.
Action:
Internal logic error. Should never happen. If it does, call CA Support.
2200 - 2299
2221S
Reason:
to request a TCP/IP service. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
2222S
Reason:
Automation EE. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
2223S
Reason:
request a TCP/IP service. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
2200 - 2299
2224S
Reason:
IBM's HPNS.
System Action:
Action:
2225S
Reason:
CA Workload Automation EE requested a TCP/IP function that is not currently
supported. The TCP/IP stack is IBM's HPNS.
System Action:
Action:
2226E
INET PURGE ID nn cancelled because the owner is freeing the socket
Reason:
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.
System Action:
Action:
2200 - 2299
2227E
INET PURGE ID nn cancelled to allow the owner to self-purge
Reason:
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.
System Action:
Action:
2228E
INET PURGE ID nn/INET PURGE TASK xxxxxx cancelled due to requeue failure
Reason:
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.
System Action:
Action:
the socket ID. *** Warning **** "INET PURGE ID" and "INET PURGE TASK" should be
used with caution.
2200 - 2299
2240E
ESP/WSS xxx.xxx.xxx:yyyy mode message not followed by change direction
Reason:
This message is issued by a mainframe work station client connected to a work station
server using TCP/IP. xxx.xxx.xxx is the IP address of the work station server. yyyyy is the
TCP port number of the work station server. When a work station server sends a mode
message ("09 800000 -->") to a 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 work station server partner is closed.
Action:
Call your software support personnel.
2241E
XWSS PUT request invalid, multi-line message not fully received
Reason:
server using TCP/IP. This is an internal error that should never occur.
System Action:
Action:
2242E
XWSS GET request invalid in send mode
Reason:
server using TCP/IP. This is an internal error that should never occur.
System Action:
Action:
2200 - 2299
2243E
XWSS GET DATALEN=wwww too small for xxxx byte message from yyy.yyy.yyy:zzzzz
Reason:
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 work station client is
connected to a work station server, this is an internal error. Otherwise the connection is
invalid, and a protocol error has occurred.
System Action:
The TCP/IP connection is closed.
Action:
Ensure that connection partner yyy.yyy.yyy:zzzzz is a valid work station server. If it is,
2244W
ESP/WSS xxx.xxx.xxx:yyyy connection closed
Reason:
server using TCP/IP. xxx.xxx.xxx is the IP address of the work station server host. yyyyy is
the TCP port number of the work station server. The connection has been closed.
System Action:
The mainframe work station client terminates.
Action:
None.
2200 - 2299
2245E
Received data length wwww from xxx.xxx.xxx:yyyyy exceeds maximum zzzz
Reason:
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 work station client can accept from its TCP/IP connection
partner. If the local work station client is connected to a work station server, this is an
internal error. Otherwise the connection is invalid, and a protocol error has occurred.
System Action:
Action:
Ensure that connection partner xxx.xxx.xxx:yyyyy is a valid work station server. If it is,
2246E
Invalid ESP/WSS message received from xxx.xxx.xxx:yyyyy
Reason:
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 work station client is connected to
a work station server, this is an internal error. Otherwise the connection is invalid, and a
protocol error has occurred.
System Action:
Action:
Ensure that connection partner xxx.xxx.xxx:yyyyy is a valid work station server. If it is,
2200 - 2299
2250I
CA-ESP TCP/IP Diagnostic Utility
Reason:
Introductory identification message when the TCP/IP diagnostic utility CYBTCPIP is
activated.
System Action:
CYBTCPIP initialization continues.
Action:
None.
2251W
SINGLE_TASK option invalid for IUCV, ignored
Reason:
The 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.
Action:
When running CYBTCPIP using the IUCV TCP/IP stack, do not specify the SINGLE_TASK
start parameter.
2252I
Primary home IP address: xxx.xxx.xxx.xxx
Reason:
When the TCP/IP diagnostic utility CYBTCPIP is activated, it displays the primary home IP
address xxx.xxx.xxx of the TCP/IP stack it uses to service its connections.
System Action:
Action:
None.
2200 - 2299
2253E
Invalid command syntax, File=xxxx, Line=yyyy
Reason:
The TCP/IP diagnostic utility CYBTCPIP encountered a syntax error in the command on
line yyyy of the file allocated to ddname xxxx.
System Action:
Action:
Correct the command on line xxxx of file yyyy.
2254E
Command xxxx not found, File=yyyy, Line=zzzz
Reason:
The 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:
Action:
Correct the command on line zzzz of file yyyy.
2255W
xxxx
Reason:
Message xxxx is usually "FILE TCPPARM NOT ALLOCATED". An attempt by the 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:
Action:
If a TCPPARM file to read commands during CYBTCPIP initialization is required, then add
a TCPPARM DD statement to the job's JCL.
2200 - 2299
2256E
xxxx
Reason:
An attempt by the TCP/IP diagnostic utility CYBTCPIP to open the TCPPARM file failed.
Message xxxx should explain the reason for the failure.
System Action:
Action:
Determine the problem from message xxxx and correct it.
2257I
For command options, enter HELP or H
Reason:
Issued by the TCP/IP diagnostic utility CYBTCPIP when activated as a TSO command.
System Action:
Action:
Entering HELP or H will display all the CYBTCPIP command options.
2258E
Command get error, RC=xxxx, terminating
Reason:
The TCP/IP diagnostic utility CYBTCPIP encountered an error attempting to get an input
command interactively.
System Action:
The CYBTCPIP job or TSO command terminates.
Action:
Rerun the CYBTCPIP job or TSO command. If the problem persists, call your software
support personnel.
2200 - 2299
2259E
Invalid command syntax
Reason:
The TCP/IP diagnostic utility CYBTCPIP encountered a syntax error in the input command
entered interactively.
System Action:
Action:
Reenter the command correctly.
2260E
Command xxxx not found
Reason:
The TCP/IP diagnostic utility CYBTCPIP encountered a command xxxx, entered
interactively, that it does not recognize as valid.
System Action:
Action:
Reenter the command correctly.
2261C
CYBTCPIP Command Options
Reason:
Response to the TCP/IP diagnostic utility CYBTCPIP's HELP or H command. Lists all the
commands supported by the TCP/IP diagnostic utility CYBTCPIP.
System Action:
Action:
None.
2200 - 2299
2262I
No active CYBTCPIP daemons
Reason:
Response to the TCP/IP diagnostic utility CYBTCPIP's DISPLAY SERVERS or D S command.
No CYBTCPIP servers (daemons) are currently active.
System Action:
Action:
None.
2263C
CYBTCPIP TCP Server Connections
Reason:
Response to the TCP/IP diagnostic utility CYBTCPIP's DISPLAY SERVERS or D S command.
All currently active CYBTCPIP TCP servers are displayed.
System Action:
Action:
None.
2264I
No active TCP clients
Reason:
Response to the 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.
System Action:
Action:
None.
2200 - 2299
2265C
CYBTCPIP TCP Clients
Reason:
Response to the 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.
System Action:
Action:
None.
2266I
Client xxxx connecting to host yyyy:zzzz
Reason:
Response to the 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. 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.
Action:
None.
2200 - 2299
2267I
Client xxxx connection local_ip:local_port<>remote_host:remote_port set to current
Reason:
Response to the 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.
System Action:
Action:
None.
2268I
Client xxxx connection local_ip:local_port<>remote_host:remote_port established
Reason:
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:
Action:
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.
2200 - 2299
2269I
Client xxxx connection local_ip:local_port<>remote_host:remote_port
{closed|purged}
Reason:
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.
System Action:
Action:
None.
2270I
Connecting to xxxx service yyyy:zzzz
Reason:
Response to the TCP/IP diagnostic utility CYBTCPIP's DAYTIME, DISCARD or ECHO
command. xxxx is the TCP service that the client is attempting to connect to, that is
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, 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 message is displayed.
Action:
None.
2200 - 2299
2271I
local_ip:local_port->remote_ip:remote_port The quick brown fox jumps over the lazy
dog
Reason:
"The quick brown fox jumps over the lazy dog" is sent to the connected server on
remote_host:remote_port by the 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.
Action:
None.
2272W
Connection local_ip:local_port<>remote_host:remote port prematurely closed by
peer
Reason:
The 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.
Action:
None.
2200 - 2299
2273I
xxxx TCP daemon started on {port yyyy|assigned port}
Reason:
Response to the 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. If port 0 was specified on the
DAYTIMED, DISCARDD, ECHOD, LISTEN or LI command, then this message displays
"assigned port". 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. The echo server receives data from the client and sends
it right back in identical format until the client closes the connection.
Action:
None.
2274I
xxxx TCP server connection local_ip:local_port<>remote_ip:remote:port established
Reason:
A 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.
Action:
None.
2200 - 2299
2275I
xxxx TCP server connection local_ip:local_port<>remote_ip:remote_port terminated
Reason:
A 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.
System Action:
Action:
None.
2276W
CYBTCPIP daemon xxxx not found
Reason:
Response to the TCP/IP diagnostic utility CYBTCPIP's STOP xxxx command. An attempt
was made to stop a CYBTCPIP TCP server (daemon) identified by server identifier xxxx.
However, no such server is active.
System Action:
Action:
To display the active TCP servers (daemons) under CYBTCPIP, enter one of the following
commands:
DISPLAY SERVERS
D S.
Then, if necessary, re-issue the STOP xxxx command specifying an existing CYBTCPIP
server (daemon).
2200 - 2299
2277I
wwww CYBTCPIP daemon xxxx {*|yyy.yyy.yyy.yyy}:zzzz stopped
Reason:
Response to the TCP/IP diagnostic utility CYBTCPIP's STOP xxxx or P xxxx command.
wwww specifies the service that the CYBTCPIP server (daemon) was providing, either
"Daytime", "Discard" or "Echo". xxxx specifies the CYBTCPIP server identifier.
yyy.yyy.yyyy.yyyy specifies the home IP address that the CYBTCPIP server (daemon) was
listening on. zzzz specifies the TCP port that the CYBTCPIP server (daemon) was listening
on.
System Action:
The specified CYBTCPIP server (daemon) terminates.
Action:
None.
2278W
Client not specified, current client not set
Reason:
Response to TCP/IP diagnostic utility CYBTCPIP's SEND, SE, >>, RECEIVE, RECV, RE, >>,
SENDRECV, ><, CLOSE or CL command. 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.
Action:
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 one of the following commands:
DISPLAY CLIENTS
DC
D
2200 - 2299
2279E
Client xxxx not found
Reason:
Response to 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.
Action:
To display the current active CYBTCPIP clients, enter one of the following commands:
DISPLAY CLIENTS
DC
D.
Then, if necessary, re-issue the CYBTCPIP client command specifying an active client.
2280W
CYBTCPIP daemon already active on {*|xxx.xxx.xxx}:yyy
Reason:
Response to TCP/IP diagnostic utility CYBTCPIP's DAYTIMED, DISCARDD, ECHOD, LISTEN
or LI command. An attempt to start a TCP/IP diagnostic utility CYBTCPIP server (daemon)
using the DAYTIMED, ECHOD, LISTEN or LI command failed because another CYBTCPIP
server is already listening on IP address xxx.xxx.xxx, if specified, and TCP port number
yyyy.
System Action:
The started CYBTCPIP server terminates.
Action:
To display the current active CYBTCPIP servers, enter one of the following commands:
DISPLAY SERVERS
D S.
Then, if necessary, re-issue the CYBTCPIP server command specifying an unused home
host name an TCP port combination.
2200 - 2299
2281W
wwww CYBTCPIP daemon xxxx {*|yyy.yyy.yyy}:zzzz not found, closing connection
Reason:
A TCP client has connected to a TCP/IP diagnostic utility CYBTCPIP server (daemon). 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. wwww specifies the service that the CYBTCPIP server (daemon) was
providing, either "Daytime", "Discard" or "Echo". xxxx specifies the CYBTCPIP server
identifier. yyy.yyy.yyyy.yyyy specifies the home IP address that the CYBTCPIP server
(daemon) was listening on. zzzz specifies the TCP port that the CYBTCPIP server
(daemon) was listening on.
System Action:
The connection is closed and the task terminates.
Action:
None.
2282I
xxxx scheduled to client yyyy connection to remte_host:remote_port
Reason:
Response to a TCP/IP diagnostic utility CYBTCPIP client command, that is 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.
Action:
None.
2200 - 2299
2283I
local_ip:local_port->remote_host:remote_port xxxx
Reason:
A TCP/IP diagnostic utility CYBTCPIP client or server has sent data xxxx to its TCP
connection partner.
System Action:
Action:
None.
2284I
local_ip:local_port<-remote_host:remote_port xxxx
Reason:
A TCP/IP diagnostic utility CYBTCPIP client or server has received data xxxx from its TCP
connection partner.
System Action:
Action:
None.
2285I
local_ip:local_port<-remote_host:remote_port xxxx
Reason:
A 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.
Action:
None.
2200 - 2299
2286I
Default home IP address: xxx.xxx.xxx.xxx
Reason:
When the TCP/IP diagnostic utility CYBTCPIP is activated, it displays the default home IP
address xxx.xxx.xxx if the HOME or HOME(yyy) startup keyword parameter was
specified. yyy specifies either IP address xxx.xxx.xxx.xxx or a DNS host name that
represents IP address xxx.xxx.xxx.xxx.
System Action:
Action:
None.
2287I
Default home IP address: xxx.xxx.xxx.xxx
Reason:
Response to the TCP/IP diagnostic utility CYBTCPIP's HOME or HOME yyy command,
where yyy specifies either IP address xxx.xxx.xxx.xxx or a DNS host name that represents
IP address xxx.xxx.xxx.xxx.
System Action:
If response to HOME command, processing continues. If response to HOME yyy
command, the default home IP address is set to xxx.xxx.xxx.xxx.
Action:
None.
2200 - 2299
2288I
No default home IP address
Reason:
Response to the TCP/IP diagnostic utility CYBTCPIP's HOME or NOHOME command.
System Action:
If response to HOME command, processing continues. If response to NOHOME
command, the default home IP address is cleared.
Action:
None.
2290W
ESPLMI must execute in a foreground TSO environment
Reason:
An attempt was made to execute the TSO Line Mode Interface in a non-TSO
environment.
System Action:
The Line Mode Interface terminates.
Action:
None.
2291I
ESP Line Mode Interface
Reason:
Introductory message when Line Mode Interface is invoked.
System Action:
The Line Mode Interface attempts to logon to the specified work station server.
Action:
None.
2300 - 2399
2292E
Command get error, RC=xxxx, terminating
Reason:
The Line Mode Interface utility encountered an error attempting to get an input
command interactively.
System Action:
The Line Mode Interface terminates.
Action:
Rerun the Line Mode Interface. If the problem persists, call CA Support.
2300 - 2399
2300E
USER xxxx NOT AUTHORIZED FOR ESP OPERATOR COMMANDS
Reason:
An operator command was issued, but the issuer does not have the authority to issue
such commands.
System Action:
Action:
Your ESP administrator must authorize you to use operator commands.
2301E
xxxx
Reason:
This message describes an I/O error encountered while processing the audit log.
System Action:
The audit log process failed.
Action:
The audit log may need to be recreated.
2300 - 2399
2302W
DATA SET xxxx FOR COPYJCL FUNCTION IS NOT PARTITIONED
Reason:
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.
Action:
Specify a partitioned data set in the COPYJCL statement.
2303I
OK
Reason:
An EVENTSET command was accepted and processed.
System Action:
None.
Action:
None.
2304I
nn {entry | entries} flushed from Deferred queue
Reason:
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.
System Action:
Action:
None.
2300 - 2399
2305I
DELETE REQUEST MUST BE ISSUED FROM A CONSOLE
Reason:
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.
Action:
Issue the command from a system console.
2307I
EVENT TRIGGERED
Reason:
The TRIGGER command has successfully triggered the event.
System Action:
The event has been triggered.
Action:
None.
2308W
EVENT IS IN THE HELD STATE
Reason:
The TRIGGER command would not trigger the event since the hold count is greater than
zero.
System Action:
The event was not triggered.
Action:
The event must be released before being triggered.
2300 - 2399
2309W
EVENT IS IN THE SUSPENDED STATE
Reason:
The TRIGGER command would not trigger the event since the suspend count is greater
than zero.
System Action:
Action:
The event must be resumed before being triggered.
2310W
INSUFFICIENT CHECKPOINT SPACE FOR A REQUEST ELEMENT
Reason:
There is no checkpoint file space in which to record another scheduling of this event.
System Action:
Action:
Wait until several other time-delayed events have been triggered, and then try again.
2311W
EVENT xxxx NOT FOUND
Reason:
This event could not be found in the event data set.
System Action:
None.
Action:
Correct the event name and try again.
2300 - 2399
2312W
EVENTSET xxxx NOT FOUND
Reason:
The BKUPEVS command specified an event data set which is not defined.
System Action:
No event data set was backed up.
Action:
Correct the event data set name and try again.
2313I
OK
Reason:
In response to a DFLTUSER NONE command, this message indicates that a userid has
become unauthorized.
System Action:
None.
Action:
None.
2314E
Reason:
The DFLTUSER command could not obtain space in the checkpoint to hold the default
user definition.
System Action:
The DFLTUSER request is not processed.
Action:
checkpoint.
2300 - 2399
2315E
UNABLE TO QUEUE DIRECTLY TO SYSTEM <sysid>
Reason:
The operator issued a TRIGGER command to trigger an EVENT on another system but
the Queue Data Set can not be found.
System Action:
Action:
Check the <sysid>.
2316E
SYSTEM <sysid> NOT A MEMBER OF SHARED QUEUE
Reason:
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:
Action:
Check the <sysid>.
2317C
EVENT DATASET STATUS
Reason:
This message introduces the response to the LISTEVS command
System Action:
The status of event databases will be displayed.
Action:
N/A.
2300 - 2399
2318W
EVENTSET xxxx NOT FOUND
Reason:
The LISTEVS command specified an event database, but that database has not been
defined.
System Action:
None.
Action:
Correct the event database name and try again.
2319W
NO EVENT DATASETS DEFINED
Reason:
A LISTEVS command specified no operands, but no event databases have been defined.
System Action:
None.
Action:
Define the event databases.
2320C
CHECKPOINT DATASET STATUS
Reason:
In response to a LISTCKPT command, this message introduces a display of information
describing the checkpoint data set.
System Action:
Action:
None.
2300 - 2399
2321I
NEXT USERDEF BACKUP AT xxxx ON yyyy
Reason:
In response to a BKUPUDEF command, this message confirms that a backup will take
place at a scheduled time.
System Action:
N/A
Action:
N/A
2322E
NO CHECKPOINT SPACE AVAILABLE
Reason:
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.
Action:
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.
2300 - 2399
2323E
Reason:
System Action:
Action:
respectively.
2324W
Reason:
System Action:
Action:
2300 - 2399
2325I
ESP COMMAND ENDED
Reason:
This command confirms that the session has ended, as a result of an END command
being issued from a terminal.
System Action:
The session has ended.
Action:
None.
2326C
EVENT LIST
Reason:
This message introduces the display of one or more events specified in a LIST command.
System Action:
The list follows.
Action:
None.
2328W
xxxx
Reason:
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.
Action:
Correct the input data set or specify a different data set, and try again.
2300 - 2399
2329W
xxxx
Reason:
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.
Action:
Correct the data set or specify a different data set and try again.
2330E
Access to xxxx denied by security system
Reason:
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.
Action:
Obtain access to the required command resource and re-enter the command.
2331W
No record in buffer
Reason:
A command was issued which operates on an individual record. A target record has not
yet been selected.
System Action:
Action:
Select a record as the target of the command and reenter the command.
2300 - 2399
2332E
INDEX data set unload ended with errors
Reason:
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.
Action:
Scan any previous messages to determine what caused the error. Correct the error and
reissue the CONVERT command.
2333I
Conversion run ended successfully
Reason:
The CONVERT command has successfully updated all data sets to the current level.
System Action:
None.
Action:
None.
2334I
Starting to unload EVENT data set xxxx
Reason:
The CONVERT command is starting to process the EVENT data set xxxx.
System Action:
Action:
None.
2300 - 2399
2335W
APPLFILE or TRAKFILE keyword omitted
Reason:
An EXTEND command was issued which did not contain an APPLFILE or TRAKFILE
keyword.
System Action:
Action:
Re-enter the EXTEND command specifying one of the required keywords.
2336E
Above error occurred during COPY function
Reason:
An error occurred during the COPY command. The previous message details the error.
System Action:
The COPY command is terminated.
Action:
Determine what cause the error and re-issue the COPY command.
2337I
nn slots added to data set, nn slots total
Reason:
The EXTEND utility has successfully added mm SLOTS to the specified slotfile, which now
has a total of nn SLOTS.
System Action:
None.
Action:
The resulting slotfile may be allocated for use, if desired.
2300 - 2399
2338I
nn records read from SMF JOURNAL data set
Reason:
During processing of the RESTORE command, nn records were read from the SMF
JOURNAL data set.
System Action:
None.
Action:
None.
2339I
nn journal updates found for xxxx
Reason:
During processing of the RESTORE command, nn records from the SMF JOURNAL data
set provided updates.
System Action:
None.
Action:
None.
2340W
DATA SET TRIGGERING QUIESCED DUE TO PRIOR REQUEST
Reason:
This message is issued when the product 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.
Action:
To restart data set triggering, use the DSTRST RESTART command.
2300 - 2399
2341I
NEXT INDEX DATASET BACKUP AT xxxx ON yyyy
Reason:
This message confirms the success of the BKUPINDX command.
System Action:
A backup of the index file has been scheduled.
Action:
None.
2342I
NO INDEX BACKUP TIME SET
Reason:
In response to a BKUPINDX ? command, this message indicates that no backup of the
index file is scheduled.
System Action:
None.
Action:
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
Reason:
There is no checkpoint file space available with which to schedule a backup of the index
file.
System Action:
None.
Action:
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.
2300 - 2399
2344W
INVALID RECORD FORMAT ON INDEX DATASET
Reason:
A record that was found on the Index dataset is longer than expected.
System Action:
The list is terminated.
Action:
Call CA Support.
2345E
Reason:
System Action:
Action:
respectively.
2300 - 2399
2346W
Reason:
System Action:
Action:
2347I
OK
Reason:
The command was successful.
System Action:
The requested action has been taken.
Action:
None.
2348W
INVALID JOBNAME/NUMBER xxxx
Reason:
The LJ command specified a job identifier that was syntactically incorrect.
System Action:
No job information was listed.
Action:
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.
2300 - 2399
2349I
SPECIFIED JOB NOT FOUND
Reason:
The LJ command specified a job that either was not found in the product, or for which
the user is not authorized.
System Action:
None.
Action:
Correct the job name or number and try again.
2350C
ABENDED JOB LIST
Reason:
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.
System Action:
N/A
Action:
N/A
2351I
NO MATCHING ENTRIES FOUND
Reason:
A DAB command was issued, but no matching job names were found.
System Action:
None.
Action:
Correct the LEVEL parameter and try again.
2300 - 2399
2352W
NO ABENDED JOBS QUEUED
Reason:
A DAB command was issued, but there are no abended jobs on the queue.
System Action:
None.
Action:
None.
2353C
QUEUE DISPLAY
Reason:
This message introduces the response to the DQ command.
System Action:
N/A
Action:
N/A
2354I
NO MATCHING P-NODE QUEUE FOUND
Reason:
A DQ or DN command specified a QUEUE name that matched no existing P-node
queues.
System Action:
None.
Action:
Correct the QUEUE parameter and try again.
2300 - 2399
2355I
NO P-NODE QUEUES IN EXISTENCE
Reason:
A DQ command was issued, but there are no P-node queues in the system.
System Action:
None.
Action:
2356C
JOBNAME DISPLAY
Reason:
This message introduces the response to the DN command.
System Action:
N/A.
Action:
N/A.
2357I
NO JOB FOUND MATCHING SELECTION CRITERIA
Reason:
A DN command was issued, but there are no matching job names on the P-node queue.
System Action:
None.
Action:
Correct the QUEUE parameter or the JOB parameter and try again.
2300 - 2399
2358W
INVALID COUNT nn, MUST BE IN RANGE 0-999
Reason:
The size of the abended jobs queue must be smaller than 1000.
System Action:
The ABENDLIM count was not changed.
Action:
Correct the count and try again.
2359I
ABEND QUEUE MAX = nn, nn CURRENTLY QUEUED
Reason:
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.
System Action:
None.
Action:
None.
2360I
DEFAULT P-NODE FOR xxxx IS yyyy
Reason:
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.
System Action:
None.
Action:
None.
2300 - 2399
2361I
NO DEFAULT P-NODE SET FOR xxxx
Reason:
In response to a DFPNODE command with no operand, this message indicates that no
default P-node has been set.
System Action:
None.
Action:
Use an operand on the DFPNODE command to set a default P-node.
2362C
QUEUE DATASET DISPLAY
Reason:
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.
System Action:
N/A.
Action:
N/A.
2363C
TRAKFILE DISPLAY
Reason:
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.
System Action:
N/A.
Action:
N/A.
2300 - 2399
2364W
TRAKFILE NOT DEFINED, OR IS NOT OPENED
Reason:
In response to a LISTTRAK command, this message indicates that the job tracking file
could not be opened.
System Action:
None.
Action:
The job tracking file must be defined in the initialization parameters with the TRAKFILE
command.
2365W
NO APPLICATION TRAKFILES DEFINED
Reason:
In response to a LISTAPTF command, this message indicates that no application files are
defined.
System Action:
None.
Action:
Define application files as required.
2366C
SYSTEM DISPLAY
Reason:
This message introduces the response to the LSYS command.
System Action:
N/A.
Action:
N/A.
2300 - 2399
2367W
NO DOCUMENTATION AVAILABLE FOR xxxx
Reason:
The JOBINFO command specified a job name or number that could not be found.
System Action:
None.
Action:
2368W
JOB DOCUMENTATION DATASET NOT DEFINED IN ESPPROC
Reason:
The JOBINFO command could not find the documentation data set.
System Action:
None.
Action:
Define a DOCLIB in the proc and try again.
2369I
SADLINK xxxx LOADED
Reason:
The SADLOAD has successfully loaded the SAD data set.
System Action:
None.
Action:
None.
2300 - 2399
2370C
PENDING EXTERNAL LINKAGE DISPLAY
Reason:
This message introduces the display of applications with external linkages.
System Action:
N/A.
Action:
N/A.
2371W
INVALID JOBNAME/NUMBER
Reason:
The JOBINFO command specified a job name or number that could not be found.
System Action:
None.
Action:
2372C
SCHEDULE LIST
Reason:
This message introduces the display of the LISTSCH command.
System Action:
N/A.
Action:
N/A.
2300 - 2399
2373W
EVENT DATASET WITH ID xxxx NOT FOUND
Reason:
The DEFERRED parameter in a LISTSCH command specified an event data set which is
not defined.
System Action:
No events are listed.
Action:
Correct the DEFERRED parameter and try again.
2374W
NO EVENTS HELD IN CLASS xxxx
Reason:
The held class specified in the HELD parameter of a LISTSCH command was not found.
System Action:
No events were listed.
Action:
Correct the HELD parameter and try again.
2375I
OK
Reason:
This message indicates that the CLASS command was successful.
System Action:
Action:
None.
2300 - 2399
2376W
Reason:
A CLASS RESUME command specified a class name mask for which no matching entries
were found.
System Action:
None.
Action:
Correct the CLASS name mask and try again.
2377I
nn ENTRIES RESUMED
Reason:
This message indicates that a CLASS RESUME command has been successful.
System Action:
None.
Action:
None.
2378W
Reason:
A CLASS PROCESS command specified a class name mask for which no matching entries
were found.
System Action:
None.
Action:
2300 - 2399
2379I
nn ENTRIES TAKEN OUT OF IGNORE STATUS
Reason:
A CLASS PROCESS command has successfully removed the IGNORE status from one or
more class entries.
System Action:
None.
Action:
None.
2380W
Reason:
A CLASS DEEXEMPT command specified a class name mask for which no matching
entries were found.
System Action:
None.
Action:
2381I
nn ENTRIES DEEXEMPTED
Reason:
This message indicates that a CLASS DEEXEMPT command has been successful.
System Action:
None.
Action:
None.
2300 - 2399
2382I
nnxxxx{| RELEASED} FROM CLASS yyyy
Reason:
This message summarizes the activity performed by a CLASS EXEMPT, RELEASE, or
FLUSH command.
System Action:
None.
Action:
None.
2383I
DELETE REQUEST MUST BE ISSUED FROM A CONSOLE
Reason:
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.
Action:
Issue the command from a system console.
2384E
Reason:
The HISTFILE command could not obtain space in the checkpoint to hold the Histfile
checkpoint element.
System Action:
The HISTFILE request is not processed.
Action:
checkpoint.
2300 - 2399
2385I
NEXT JOB INDEX DATASET BACKUP AT xxxx ON yyyy
Reason:
This message displays when the next backup will be for the job index database.
System Action:
None.
Action:
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
Reason:
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:
None.
Action:
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.
2300 - 2399
2387E
Reason:
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.
Action:
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
Reason:
The BKUPHIST command specified an undefined history file id.
System Action:
None.
Action:
Correct the history file id and try again.
2389C
HISTORY DATASET STATUS
Reason:
This message introduces a display of the status of the history files.
System Action:
N/A.
Action:
N/A.
2300 - 2399
2390W
HISTFILE xxxx NOT FOUND
Reason:
The LISTHIST command specified a history file id which was not defined.
System Action:
None.
Action:
Correct the history file id and try again.
2391W
NO HISTORY DATASETS DEFINED
Reason:
A LISTHIST command with no operands was issued, but no history files have been
defined.
System Action:
None.
Action:
None.
2392W
INVALID RESPONSE
Reason:
System Action:
Action:
2300 - 2399
2393E
INVALID P-NODE NAME xxxx
Reason:
A DEFTM command was issued which contained an invalid P-node name.
System Action:
Action:
Reenter the command specifying a correct P-node name.
2394E
INVALID P-NODE/DUE OUT TIME SYNTAX xxxx
Reason:
A DEFTM command was issued which contained an invalid P-node name or due out time
specification.
System Action:
Action:
Reenter the command specifying a correct P-node name and optional due out time.
2395E
Reason:
System Action:
Action:
2300 - 2399
2396W
Reason:
System Action:
Action:
2397W
Reason:
System Action:
Action:
2398I
TRACK MODEL xxxx{ REPLACED | ADDED}
Reason:
The DEFTM command has successfully defines or altered a job tracking model.
System Action:
None.
Action:
None.
2400 - 2499
2399I
TRACK MODEL DELETED
Reason:
The DELTM command has successfully deleted the job tracking model.
System Action:
None.
Action:
None.
2400 - 2499
2400C
MODEL DISPLAY
Reason:
This message introduces the result of a LISTTM command.
System Action:
N/A.
Action:
N/A.
2401I
NO MATCHING ENTRIES FOUND LEVEL xxxx
Reason:
The LISTM command specified a tracking model name mask which matched no job
tracking models.
System Action:
None.
Action:
Correct the mask and try again.
2400 - 2499
2402I
JOB {PREFIX }xxxx DEFINED
Reason:
The DEFTJ command has successfully defined the tracking parameters for the specified
job name or prefix.
System Action:
None.
Action:
None.
2403W
MODEL NAME REQUIRED FOR DEFINE REQUEST
Reason:
A DEFTJ command was issued without a MODEL parameter. This is a required parameter
for the DEFTJ command.
System Action:
None.
Action:
Add a MODEL parameter and try again.
2404I
nn xxxx ALTERED LEVEL yyyy
Reason:
The ALTTJ command has successfully altered the characteristics of one or more jobs
which match the job name specification.
System Action:
None.
Action:
None.
2400 - 2499
2405I
JOB {PREFIX }xxxx ALTERED
Reason:
The ALTTJ has successfully altered the characteristics of this job or prefix.
System Action:
None.
Action:
None.
2406I
NO MATCHING PREFIX ENTRIES FOUND
Reason:
The LTJ command specified a job name prefix for which no matching prefixes were
found.
System Action:
None.
Action:
Correct the job name prefix and try again.
2407I
PREFIX xxxx NOT FOUND
Reason:
The LTJ command specifies a prefix which has not been defined.
System Action:
None.
Action:
Correct the prefix and try again, or define the prefix with DEFTJ.
2400 - 2499
2408I
P-NODE xxxx{ REPLACED | ADDED}
Reason:
The DEFPN command has successfully defined or altered a processing node.
System Action:
The processing node has been defined or altered.
Action:
None.
2409I
P-NODE xxxx DELETED
Reason:
The DELPN command has successfully deleted the specified processing node.
System Action:
The processing node has been deleted.
Action:
None.
2410C
P-NODE DISPLAY
Reason:
This message introduces the listing of the definition of one or more processing
System Action:
N/A.
Action:
N/A.
2400 - 2499
2411E
JOB/ACCOUNT AUTHORITY STRINGS NOT PAIRED
Reason:
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.
Action:
Correct the INCLUDE or EXCLUDE parameter and try again.
2412I
JOB AUTHORITY TABLE xxxx{ REPLACED | ADDED}
Reason:
The DEFAT command has successfully defined or altered the authorization table.
System Action:
None.
Action:
None.
2413I
JOB AUTHORITY TABLE xxxx DELETED
Reason:
The DELAT command has successfully deleted the authorization table.
System Action:
None.
Action:
None.
2400 - 2499
2414C
JOB AUTH TABLE DISPLAY
Reason:
This message introduces the display of the authorization table that was specified in the
LISTAT command.
System Action:
N/A.
Action:
N/A.
2415W
INVALID JOB NAME/NUMBER xxxx
Reason:
The LJ command specified a job identifier that was syntactically incorrect.
System Action:
Action:
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.
2400 - 2499
2416W
NO DOCUMENTATION AVAILABLE FOR xxxx
Reason:
The job documentation library contains no member for this job. The product has
searched the DOCLIB data set for a member whose name is the same as the job name,
unless a DOCMEM statement indicated a different member name. No such member was
found.
System Action:
None.
Action:
Add the member to the Doclib data set.
2417W
JOB DOCUMENTATION DATA SET NOT DEFINED
Reason:
The product could not search the documentation library since there was no DOCLIB
statement in the ESPPROC.
System Action:
All documentation processing is ignored.
Action:
Add a DOCLIB statement to the ESPPROC. If the product is being executed from TSO, a
TSO ALLOC statement can be used to allocate the JOBDOC file. If the product is being
executed from batch, a JOBDOC DD statement can be present.
2400 - 2499
2418I
NO TCELL POOLS DEFINED
Reason:
In response to a LTCELL command, this message indicates that no TCELL pools have
been defined.
System Action:
None.
Action:
Define the TCells if required.
2419I
Reason:
An LTJ command was issued, but no job names were found that matched the job name
mask.
System Action:
None.
Action:
Correct the job name mask and try again.
2420I
Reason:
The LISTPN command specified a processing node name mask which did not match any
processing nodes that are defined.
System Action:
None.
Action:
Correct the processing node mask and try again.
2400 - 2499
2421I
Reason:
The LISTAT command specified an authorization table mask which did not match the
name of any authorization table defined.
System Action:
None.
Action:
Correct the authorization table mask and try again.
2422I
JOB {PREFIX }xxxx DELETED
Reason:
The DELTJ has successfully deleted a tracked job definition from the job index file.
System Action:
The tracked job definition was deleted.
Action:
None.
2423W
INVALID JOBNAME/NUMBER
Reason:
The JOBINFO command specified a job identifier that was syntactically incorrect.
System Action:
Action:
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)'.
2400 - 2499
2424W
xxxx
Reason:
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.
Action:
2425W
INVALID RESPONSE
Reason:
System Action:
Action:
2426E
ERROR OCCURRED READING/WRITING END RECORD FOR JOB xxxx
Reason:
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.
System Action:
Action:
2400 - 2499
2427E
ERROR OCCURRED READING/WRITING xxxxx RECORD FOR JOB yyyy
Reason:
A job tracking record was being updated at job purge/transmit time when an I/O error
The message indicates whether a normal purge (PURGE) or JES3 BDT transmit
(TRANSMIT) record was being processed.
System Action:
Action:
2428E
ERROR OCCURRED UPDATING INFOSERV DATA FOR JOB xxxx
Reason:
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.
System Action:
Action:
2429E
INVALID TRACKING ELEMENT CODE DETECTED, nn
Reason:
System Action:
None.
Action:
2400 - 2499
2430W
JOB TRACKING SUSPENDED DUE TO PRIOR REQUEST
Reason:
Jobs are not being tracked because a TRACKING NOSTORE command had been issued.
System Action:
None.
Action:
To resume job tracking, issue the TRACKING STORE command.
2431E
INVALID JOB AUTHORITY TABLE GENERATED
Reason:
The job authority table generated by the DEFAT command is invalid.
System Action:
None.
Action:
Check the parameters supplied on the command and correct if applicable.
2432W
JOB xxxx ALREADY DEFINED
Reason:
The DEFTJ command specified a job name that was already defined.
System Action:
The job name or prefix was not redefined.
Action:
Delete the tracking parameters for this job name by using the DELTJ command, and then
try the DEFTJ command again.
2400 - 2499
2433W
PREFIX xxxx ALREADY EXISTS
Reason:
The DEFTJ command specified a job prefix that was already defined.
System Action:
The job name or prefix was not redefined.
Action:
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
Reason:
A DELTJ command specified a job name or prefix that was not defined.
System Action:
None.
Action:
Correct the job name or prefix and try again.
2435W
TRACK MODEL xxxx ALREADY EXISTS
Reason:
The DEFTM command specified a job tracking model that is already defined.
System Action:
None.
Action:
Correct the job tracking model name and try again.
2400 - 2499
2436W
TRACK MODEL xxxx NOT FOUND
Reason:
A DELTM command specified a job tracking model that was not defined.
System Action:
None.
Action:
Correct the job tracking model name and try again.
2437E
TRACK MODEL xxxx IS INVALID
Reason:
System Action:
None.
Action:
2438W
P-NODE xxxx ALREADY EXISTS
Reason:
A DEFPN command specified a processing node name that has already been defined.
System Action:
None.
Action:
Correct the P-node name, or delete the P-node first with DELPN, and then try again.
2400 - 2499
2439W
Reason:
A DELPN command specified a processing node name that was not defined.
System Action:
None.
Action:
Correct the P-node name and try again.
2440W
JOB AUTHORITY TABLE xxxx ALREADY EXISTS
Reason:
A DEFAT command specifies an authorization table name that has already been defined.
System Action:
None.
Action:
Correct the authorization table name, or delete the authorization table first with DELAT,
and then try again.
2441W
JOB AUTHORITY TABLE xxxx NOT FOUND
Reason:
A DELAT command specifies an authorization table that has not been defined.
System Action:
None.
Action:
Correct the authorization table name and try again.
2400 - 2499
2442I
JOB NOT FOUND OR ACCESS DENIED
Reason:
System Action:
None.
Action:
2443W
FUNCTION NOT SUPPORTED YET
Reason:
System Action:
None.
Action:
2444E
I/O ERROR READING JOB AUTHORITY TABLE
Reason:
System Action:
None.
Action:
2400 - 2499
2445W
JOB AUTHORITY TABLE xxxx NOT FOUND FOR USER yyyy
Reason:
System Action:
None.
Action:
2446W
INVALID JOBNAME/NUMBER nn
Reason:
The job identifier is syntactically incorrect.
System Action:
None.
Action:
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
Reason:
A POST command was issued specifying a P-node that was not found on the queue data
set.
System Action:
Action:
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.
2400 - 2499
2448W
Job xxxx(yyyy) not on TRAKFILE
Reason:
An internal error has occurred. xxxx specifies the job name. yyyy specifies the job
identifier.
System Action:
None.
Action:
2449C
JOB xxxx LISTING
Reason:
This message introduces the listing produced by the LJ command.
System Action:
N/A.
Action:
N/A.
2450W
NO RESPONSE RECEIVED FROM SUBSYSTEM
Reason:
The command was sent to the subsystem for processing, but no response was received.
System Action:
None.
Action:
Check the status of the subsystem. It may need to be restarted.
2400 - 2499
2451E
COMMAND IGNORED, SHOULD BE LESS THAN 116 CHARACTERS
Reason:
An OPER command was issued, but it was too long.
System Action:
Action:
The command must be shortened before being re-issued.
2452I
COMMAND ACCEPTED BY SUBSYSTEM
Reason:
This OPER command has been successfully sent to the subsystem for processing.
System Action:
N/A.
Action:
N/A.
2400 - 2499
2453E
Reason:
System Action:
Action:
respectively.
2454E
FTPIP specification xxxx not a valid IP address
Reason:
A SIMULATE command specified an invalid FTPIP(xxxx) operand. xxxx is not a valid IP
address.
System Action:
The SIMULATE command fails.
Action:
Re-issue the SIMULATE command specifying FTPIP(xxxx), where xxxx is a valid IP
address.
2400 - 2499
2455W
Reason:
System Action:
Action:
2456I
SYMLIB xxxx{ REPLACED| ADDED}
Reason:
The DEFSYML command has successfully added or replaced a symbol library set.
System Action:
The symbol library set has been added or replaced.
Action:
None.
2457I
SYMLIB xxxx DELETED
Reason:
The DELSYML command has successfully deleted a symbol library set.
System Action:
The symbol library set has been deleted.
Action:
None.
2400 - 2499
2458I
NO ENTRIES FOUND MATCHING xxxx
Reason:
The LISTSYML command specified a symbol library name mask that did not match any
symbol library names defined.
System Action:
None.
Action:
Correct the symbol library set name mask and try again.
2459I
NO TIME ZONES DEFINED
Reason:
An LTZONE command was issued, but no time zones have been defined.
System Action:
None.
Action:
Time zones can be defined with the TIMEZONE command.
2460E
NOT AUTHORIZED FOR SYMLIB DEFINE/DELETE
Reason:
This user is not authorized to define or delete symbol library sets.
System Action:
The requested function was not performed.
Action:
In a non-SAF system, the user must have either special, calendar, or scheduler authority.
In a SAF system, the user must have alter access to the resource SYMLIB.symname.
2400 - 2499
2461E
INCOMPLETE SYMBOL ASSIGNMENT STATEMENT
Reason:
The assignment statement that was entered is not complete.
System Action:
None.
Action:
Correct the statement and retry.
2462E
COMMAND xxxx NOT DEFINED
Reason:
An incorrect command was entered.
System Action:
None.
Action:
2400 - 2499
2463E
Reason:
System Action:
Action:
respectively.
2464E
CANNOT START MULTIPLE ESPs FROM THE SAME TCB
Reason:
If a user is in a TSO session and then starts another session on the same screen, an 0C4
abend will result when an exit is made from the first session. In addition, after exiting
from the second session, strange behaviour or abends might be experienced if work is
done in the first session.
System Action:
An abend occurs as noted.
Action:
Avoid running multiple sessions on the same screen
2400 - 2499
2465W
Reason:
System Action:
Action:
2466E
INVALID COMPARATOR xxxx
Reason:
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:
None.
Action:
Correct the operator and resubmit the report.
2467E
INVALID SELECTION CRITERIA xxxx
Reason:
The selection criteria in this CRITERIA subcommand were invalid.
System Action:
The report was not produced.
Action:
Please consult the Command Reference to find the correct syntax for the CRITERIA
subcommand.
2400 - 2499
2468E
INCOMPLETE INPUT STATEMENT
Reason:
This report subcommand is incomplete.
System Action:
Action:
Please complete the subcommand and resubmit the report.
2469W
'OR' INVALID OUTSIDE OF A CRITERIA SECTION, IGNORED
Reason:
The OR keyword is valid when describing selection criteria in a CRITERIA subcommand. It
is valid nowhere else.
System Action:
Action:
Correct the subcommand and resubmit the report.
2470E
BREAK FIELD NOT DEFINED FOR DISPLAY
Reason:
The field name in the BREAK statement must have been specified in a previous DISPLAY
statement.
System Action:
Action:
Correct the BREAK statement and resubmit the report.
2400 - 2499
2471E
MISSING COMPARISON LENGTH FOR BREAK
Reason:
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:
Action:
Correct the BREAK statement and resubmit the report.
2472W
REPORT DEFINITION INCOMPLETE / NO DISPLAY ENTRIES
Reason:
Each report definition must contain either a DISPLAY statement or a COPY statement.
Without these statements, there is no way for the product to format the report or write
the history file records.
System Action:
Action:
Add a DISPLAY or a COPY statement and resubmit the report.
2473E
REPORT BYPASSED DUE TO ABOVE ERRORS
Reason:
The report was not generated because of errors found by the product in the report
definition.
System Action:
Action:
Check the previous error messages, correct the report definition and resubmit the
report.
2400 - 2499
2474I
NO RECORDS FOUND TO MATCH SPECIFIED CRITERIA
Reason:
No errors were found in the report definition, but no history file records were found
that match the selection criteria.
System Action:
Action:
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
Reason:
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.
Action:
Correct the I/O problem and resubmit the report.
2476E
xxxx
Reason:
An I/O error was encountered while trying to open the COPY file.
System Action:
Action:
2400 - 2499
2477E
xxxx
Reason:
An I/O error occurred during the processing of a history file.
System Action:
Action:
2478E
xxxx
Reason:
An I/O error occurred while writing to a COPY file.
System Action:
Action:
2479E
INVALID REQUEST CODE DETECTED
Reason:
The history file request processor was passed an invalid request code. This would
normally only happen due to a logic error.
System Action:
Action:
2400 - 2499
2480W
TRACKING FACILITY NOT ACTIVE
Reason:
A user or operator entered a history file that requires the tracking facility be active. The
tracking facility was not active.
System Action:
Action:
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
Reason:
System Action:
None.
Action:
2483E
INVALID DATABASE REQUEST TYPE xxxx SPECIFIED
Reason:
System Action:
None.
Action:
2400 - 2499
2484E
Reason:
Your user id has not been defined to the subsystem.
System Action:
Action:
2485E
xxxx IS NOT AUTHORIZED IN THE UPDT OR BY SAF
Reason:
System Action:
Action:
2486E
Reason:
An invalid current password was specified when changing the password or accessing the
product through a batch job.
System Action:
The access to the product is denied.
Action:
Ensure a correct current password is specified.
2400 - 2499
2487W
COMMAND NOT AUTHORIZED
Reason:
You are not authorized to issue the command.
System Action:
Action:
None required.
2488I
SPECIAL USER ATTRIBUTES ASSIGNED
Reason:
A request has been entered to assign special attributes to a user ID.
System Action:
Action:
None required.
2400 - 2499
2489E
Reason:
System Action:
Action:
respectively.
2490E
A Z/OS AGENT EVENT CANNOT BE EDITED
Reason:
A user attempted to update an event definition created by a z/OS Agent. This is not
allowed because of internal settings that would be lost if the update were to proceed.
System Action:
Action:
Cancel the event definition or rename the event.
2400 - 2499
2491E
EVENT DEFINITION SIZE EXCEEDED
Reason:
The EVENT definition contained too many statements.
System Action:
Action:
Redefine your EVENT to contain fewer definition statements. If necessary, break it down
into multiple EVENTs.
2492E
Reason:
System Action:
Action:
2493E
Reason:
System Action:
Action:
2400 - 2499
2494W
NEXT PROCESSING ENDED AFTER nnn SUSPENDED SCHEDULES
Reason:
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.
Action:
Manually reduce the suspend count.
2495W
EVENT IS CURRENTLY SUSPENDED WITH NO SCHEDULED RESUME
Reason:
The NEXT command could not find another scheduled execution time of this event. The
event is suspended, and there are no scheduled RESUMEs.
System Action:
None.
Action:
The event must be resumed to continue.
2496E
xxxx
Reason:
The INVOKE command encountered an error while opening a data set for verification
System Action:
Action:
2400 - 2499
2497E
xxxx
Reason:
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.
System Action:
Action:
2498E
xxxx
Reason:
The SUBMIT command encountered an error while opening a CA-Librarian data set for
verification purposes during the definition of an Event. The message text fully describes
the error.
System Action:
Action:
2499E
xxxx
Reason:
The COPYJCL command encountered an error while opening a data set for verification
System Action:
Action:
2500 - 2599
2500 - 2599
2500E
xxxx
Reason:
The SUBMIT command encountered an error while opening a data set for verification
System Action:
Action:
2501I
EVENT xxxx.yyyy, {SUSPEND|HOLD} COUNT {INCREMENTED|DECREMENTED},
HOLD(nn), SUSP(nn)
Reason:
The suspend or hold count of this event have been successfully modified.
System Action:
None.
Action:
None.
2502I
EVENT TRIGGERED
Reason:
A TRIGGER command has successfully triggered the event.
System Action:
The event has been triggered.
Action:
None.
2500 - 2599
2503I
SCHEDULED EXECUTION AT xxxx ON yyyy WILL BE BYPASSED
Reason:
A TRIGGER NOXEQ command has been issued, and the next scheduled execution of the
event will be bypassed.
System Action:
None.
Action:
None.
2504W
SCHEDULED OCCURRENCE NOT FOUND
Reason:
A TRIGGER NOXEQ command was issued, but no scheduled execution of this event could
be found.
System Action:
No scheduled execution is being bypassed.
Action:
Correct the event name and retry.
2505E
MEMBER NAME OMITTED FOR PANVALET DATA SET xxxx
Reason:
A member name must be specified when submitting from a CA-Panvalet data set.
System Action:
The job was not submitted.
Action:
Specify a member name in parentheses after the data set name, or in the MEMBER
keyword, and try again.
2500 - 2599
2506E
MEMBER NAME OMITTED FOR LIBRARIAN DATA SET xxxx
Reason:
A member name must be specified when submitting from a CA-Librarian data set.
System Action:
The job was not submitted.
Action:
Specify a member name in parentheses after the data set name, and try again.
2507E
Reason:
System Action:
Action:
respectively.
2500 - 2599
2508W
Reason:
System Action:
Action:
2509W
Reason:
System Action:
Action:
2510E
Reason:
System Action:
Action:
2500 - 2599
2511E
Reason:
System Action:
Action:
2512I
nn GROUPS DISPLAYED
Reason:
The LISTGRP has displayed nn group definitions.
System Action:
None.
Action:
None.
2515I
nn USERS DISPLAYED
Reason:
The LISTUSER has displayed nn user definitions.
System Action:
None.
Action:
None.
2500 - 2599
2516E
Reason:
System Action:
Action:
respectively.
2517W
Reason:
System Action:
Action:
2500 - 2599
2518W
Reason:
System Action:
Action:
2519E
Reason:
System Action:
Action:
2520E
Reason:
System Action:
Action:
2500 - 2599
2521E
INVALID LOGICAL DAY SHIFT VALUE xxxx
Reason:
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:
None.
Action:
Correct the SHIFT parameter and try again.
2522I
CALENDAR xxxx {ALTERED|DELETED|DEFINED}
Reason:
A DEFCAL, ALTCAL, or DELCAL command has successfully processed this calendar.
System Action:
None.
Action:
None.
2523W
NO MATCHING CALENDARS FOUND
Reason:
A LISTCAL command was issued, but no matching calendars are defined.
System Action:
None.
Action:
Correct the calendar name mask, or define a calendar, and try again.
2500 - 2599
2524E
Reason:
System Action:
Action:
respectively.
2525W
Reason:
System Action:
Action:
2500 - 2599
2526W
Reason:
System Action:
Action:
2527E
Reason:
System Action:
Action:
2528E
Reason:
System Action:
Action:
2500 - 2599
2529E
Reason:
Your userid has not been defined to the subsystem.
System Action:
Action:
2530E
YOU ARE NOT AUTHORIZED TO GROUP xxxx
Reason:
You attempted to access a group prefix to which you are not authorized.
System Action:
Action:
Ensure you access only the groups to which you are authorized.
2531I
NO DEFAULT GROUP NAME SET
Reason:
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:
None.
Action:
Use the GROUP command to set a default group prefix.
2500 - 2599
2532I
CURRENT DEFAULT GROUP IS xxxx
Reason:
This is the current default group prefix, as established by the previous GROUP
command.
System Action:
None.
Action:
To change the group prefix, use the GROUP command with an operand.
2533E
Reason:
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:
None.
Action:
Correct the current password and try again.
2534I
EVENT ALTERED
Reason:
The ALTEVENT command has successfully altered this event.
System Action:
The event has been altered.
Action:
None.
2500 - 2599
2535I
nn xxxx ALTERED
Reason:
The ALTEVENT command has successfully altered one or more events that matched the
event name specification.
System Action:
One or more events were altered.
Action:
None.
2536I
RACF DATA UPDATED
Reason:
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 the product, unless those parameters are already present on the JOB
statement. These parameters are USER, GROUP, and PASSWORD.
System Action:
None.
Action:
None.
2500 - 2599
2537W
'TIMESEQ' AND 'ALL' INCOMPATIBLE, 'TIMESEQ' IGNORED
Reason:
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:
None.
Action:
Remove either one of these keywords and try again.
2538E
Reason:
System Action:
Action:
respectively.
2500 - 2599
2539W
'VERBOSE' AND 'ALL' INCOMPATIBLE, 'VERBOSE' IGNORED
Reason:
On a LIST command, the VERBOSE and ALL keywords cannot appear together. The
VERBOSE keyword requests one line of summary data, while the intention of ALL is to
display the entire definition of the events.
System Action:
None.
Action:
Remove either one of these keywords and try again.
2541E
More than one service units default resource name specified
Reason:
Only one service units default resource name is allowed in the RESDFLT command, that
is one of these: SU60, SU180 or SU600.
System Action:
The user is prompted to enter a correct RESDFLT command.
Action:
Reenter the RESDFLT command with the error corrected.
2542I
DATASET TRIGGERING NOT ACTIVE
Reason:
A LISTDTE command was entered. Data set triggering is not currently active.
System Action:
None.
Action:
If required, ensure data set triggering is active.
2500 - 2599
2544E
INVALID JOURNAL SMF RECORD NUMBER SPECIFIED
Reason:
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.
Action:
2545E
Reason:
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.
Action:
2500 - 2599
2546E
Reason:
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.
Action:
2547C
SYSTEM MESSAGE LIST
Reason:
The system messages currently being intercepted are listed in response to a LSYSMSGS
command.
System Action:
None.
Action:
None.
2548C
COMMAND PREFIX SUBSTITUTIONS
Reason:
The command prefix substitutions currently in effect using the CMDPRFX command are
listed in response to a LCMDPRFX command.
System Action:
None.
Action:
None.
2500 - 2599
2549C
TRACKING DATA ANALYSIS
Reason:
The current job tracking XME usage is listed in response to a LISTXMEZ command.
System Action:
None.
Action:
None.
2550E
INVALID COLUMN VALUE OR RANGE
Reason:
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.
Action:
Correct the command or respond to message 0802A and correct the initialization
statement.
2500 - 2599
2551E
INVALID ROUTING OR DESCRIPTOR CODE
Reason:
The ROUTE or DESC keyword was specified on a SYSMSGS command or initialization
statement. A code outside the range 1:16 was specified.
System Action:
Action:
statement.
2552E
INVALID EVENT ID xxxx SPECIFIED FOR SYSMSGS'
Reason:
The EVENT keyword was specified on a SYSMSGS command or initialization statement.
The Event id value contains incorrect syntax according to Event naming rules.
System Action:
Action:
statement.
2500 - 2599
2553E
ID REQUIRED FOR IGNORE OPTION OF SYSMSGS STATEMENT
Reason:
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.
System Action:
Action:
statement.
2554E
INVALID DATE FORMAT xxxx
Reason:
An invalid date format was specified on a DATEFORM command or initialization
statement.
System Action:
Action:
statement.
2500 - 2599
2555I
OK
Reason:
System Action:
None.
Action:
None.
2556I
DATA SET TRIGGER DELAY VALUE CURRENTLY SET AT nn xxxx
Reason:
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.
Action:
None.
2558I
TRACKING OPTIONS:
Reason:
The job tracking options were set and/or listed in response to a TRACKOPT command or
System Action:
If requested, the job tracking options are altered.
Action:
None.
2500 - 2599
2559I
EVENT SEND WTO RESTRICTED
Reason:
The use of a WTO in an Event was restricted in response to an EVENTWTO command.
System Action:
The product will not permit WTOs within an Event definition.
Action:
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
Reason:
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:
Action:
EVENTOPT command to restrict WTO access in an Event.
2561I
EVENT SEND WTO DERESTRICTED
Reason:
The restriction on use of a WTO in an Event was removed in response to an EVENTWTO
command.
System Action:
The product will permit the use of WTOs within Event definitions.
Action:
EVENTOPT command to permit WTO access in an Event.
2500 - 2599
2562I
EVENT SEND WTO NOT RESTRICTED
Reason:
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:
Action:
EVENTOPT command to permit WTO access in an Event.
2563I
EVENT SEND WTO FACILITY {NOT }RESTRICTED
Reason:
The status of use of a WTO in an Event was listed in response to an EVENTWTO
command.
System Action:
None.
Action:
EVENTOPT command to list the status of WTO access in an Event.
2564I
EVENT OPTIONS:
Reason:
The Event options were set and/or listed in response to a EVENTOPT command or
System Action:
If requested, the Event options are altered.
Action:
None.
2500 - 2599
2565I
NULL PASSWORD
Reason:
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.
System Action:
None.
Action:
None.
2566I
NO SYSTEM MESSAGES ARE BEING SCANNED
Reason:
A LSYSMSGS command was entered to list the system messages currently being
intercepted by the product. No messages are currently being intercepted by the
product.
System Action:
None.
Action:
None.
2567I
NO COMMAND PREFIX SUBSTITUTION IN EFFECT
Reason:
A LCMDPRFX command was entered to list the command prefix substitutions currently
in effect. No command prefix substitutions are currently in effect.
System Action:
None.
Action:
None.
2500 - 2599
2568I
SPUSER xxxx ALREADY DEFINED
Reason:
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.
Action:
Ensure you specify the correct userid.
2569I
DATE FORMAT SET
Reason:
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
Action:
None.
2570I
CURRENT DATE FORMAT IS xxxx
Reason:
The current date format was listed in response to a DATEFORM command or
System Action:
None.
Action:
None.
2500 - 2599
2571I
CURRENT DATE FORMAT IS DEFAULT OF YMD
Reason:
The current date format was listed in response to a DATEFORM command or
initialization statement. The current date format is the default value YMD.
System Action:
None.
Action:
None.
2572W
TRACE FACILITY NOT CURRENTLY ACTIVE
Reason:
A CKPTRACE command or initialization statement was entered to activate tracing of
Checkpoint related functions. The product general trace facility is required and is not
currently active.
System Action:
Action:
Activate the product general trace facility and re-issue the CKPTRACE command.
2500 - 2599
2573I
JOB xxxx(yyyy) AUTOPOSTED FROM EXEC
Reason:
existed between the JES status and the product status. In this case, the job is in on the
product exec queue but not on the JES exec queue. This could happen at any time
where the product 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
System Action:
Action:
None.
2574I
JOB xxxx(yyyy) AUTOPOSTED FROM OUTPUT
Reason:
existed between the JES status and the product status. In this case, the job is on the
product output queue but not on the JES output queue. This could happen at any time
where the product 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
System Action:
Action:
None.
2500 - 2599
2575I
JOB xxxx(yyyy) REQUEUED FOR EXECUTION
Reason:
existed between the JES status and the product status. In this case, the job was on the
JES input queue but not on the product input queue. This could happen at any time
where the product had not receive 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
System Action:
Action:
None.
2576E
ERROR OCCURRED READING SYMTAB ENTRY xxxx
Reason:
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.
Action:
Correct the error described by the message following this message.
2500 - 2599
2577E
GROUP PREFIX xxxx NOT AUTHORIZED FOR SYMTAB yyyy
Reason:
System Action:
The symbol data sets specified by the symbol table will not be read.
Action:
2578I
MESSAGE FROM EVENT xxxx.yyyy
Reason:
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.
Action:
If necessary, correct the condition described by the message following this message.
2500 - 2599
2579E
Reason:
A problem was encountered while parsing a command.
System Action:
Action:
respectively.
2580E
DATA SET xxxx PARTITIONED AND NO MEMBER SPECIFIED
Reason:
An INVOKE command was issued. The specified data set 'xxxx' is a partitioned data set
and a member name was not specified.
System Action:
Action:
Correct the command by specifying a member name and re-issue the command.
2500 - 2599
2581E
xxxx
Reason:
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.
Action:
Correct the error described by the message text. If the problem persists, notify your
2582E
xxxx
Reason:
An I/O error occurred opening an OS data set for a SUBMIT command in the execution
of an Event.
System Action:
Action:
2583E
xxxx
Reason:
An I/O error occurred opening a data set for a SUBMIT command in the execution of an
Event.
System Action:
Action:
2500 - 2599
2584E
xxxx
Reason:
An I/O error occurred opening a CA-Panvalet data set for a SUBMIT command in the
execution of an Event.
System Action:
Action:
2585E
xxxx
Reason:
An I/O error occurred opening a CA-Librarian data set for a SUBMIT command in the
execution of an Event.
System Action:
Action:
2586W
UNABLE TO OBTAIN SUFFICIENT CSA FOR xxxx
Reason:
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:
Action:
Take action to restore CSA levels or remove the initialization statement.
2500 - 2599
2587W
EVENT FILE SUSPENDED
Reason:
A request was made to access an event file which is currently in suspended status.
System Action:
Action:
Contact your 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
Reason:
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.
Action:
None.
2590C
RERUN MANAGER STEP JCL
Reason:
The Rerun Manager step JCL was listed in response to a ERMSTEP command or
System Action:
None.
Action:
None.
2500 - 2599
2591I
NO RERUN MANAGER JCL DEFINED
Reason:
The Rerun Manager step JCL was listed in response to a ERMSTEP command or
initialization statement. There is no Rerun Manager step JCL defined.
System Action:
None.
Action:
None.
2592C
RESTART ACTION EXCLUSION DISPLAY
Reason:
The Restart Action Exclusion entries were listed in response to a RAXE command or
System Action:
None.
Action:
None.
2593C
ALERT DEFINITION DISPLAY
Reason:
The Alert definitions were set and/or listed in response to a ALERTDEF command or
System Action:
If requested, the Alert definitions are altered.
Action:
None.
2500 - 2599
2594I
No alerts defined
Reason:
Response to ALERTDEF LIST command.
System Action:
Action:
None.
2595C
PREALLOCATED DATA SET LIST
Reason:
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.
Action:
None.
2596W
SCOREBOARD/SCHEDULE FILE NOT ACTIVE
Reason:
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.
Action:
Activate the scoreboard or schedule file.
2500 - 2599
2597I
OK
Reason:
System Action:
None.
Action:
None.
2598I
No default resource names defined
Reason:
A RESDFLT command or initialization statement was entered to list the default Resource
assignments. No default Resource names were defined.
System Action:
None.
Action:
None.
2599E
MODEL, NODE or NETNODE required with XMITMDL DELETE
Reason:
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:
Action:
Specify the MODEL, NODE and/or NETNODE keyword operand(s) on the "XMITMDL
DELETE" command.
2600 - 2699
2600 - 2699
2600E
Node name xxxx length exceeds 16 characters
Reason:
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 the product, or a initialization command reply. If the
XMITMDL ADD command was specified as an operator command, then it is ignored.
Action:
Correct the command or initialization statement to specify an NJE node name that does
not exceed 16 characters.
2601E
NODE NAME xxxx NOT DEFINED
Reason:
An XMITMDL ADD command or initialization statement was entered with the NODE
keyword specified. The specified NODE is not defined.
System Action:
Action:
Correct the command or initialization statement.
2600 - 2699
2602E
MODEL xxxx NOT FOUND
Reason:
An XMITMDL DELETE command or initialization statement was entered with the MODEL
keyword specified. The specified MODEL is not currently defined.
System Action:
Action:
2603E
MODEL|{NODE and/or NETNODE} missing
Reason:
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:
Action:
2604I
SCHEDULE FILE LOAD REQUEST QUEUED
Reason:
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.
Action:
None.
2600 - 2699
2605I
SCHEDULE FILE PURGE REQUEST QUEUED, nn ENTRIES SELECTED
Reason:
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.
Action:
None.
2606I
NO RESTART ACTION EXCLUSION ENTRIES FOUND
Reason:
The Restart Action Exclusion entries were listed in response to a RAXE command or
initialization statement. There are no Restart Action Exclusion entries defined.
System Action:
None.
Action:
None.
2607I
ALERT DEFINITION xxxx ADDED
Reason:
An ALERTDEF ADD command or initialization statement was successfully processed.
System Action:
The Alert definition 'xxxx' was added.
Action:
None.
2600 - 2699
2608I
ALERT DEFINITION xxxx DELETED
Reason:
An ALERTDEF DELETE command or initialization statement was successfully processed.
System Action:
The Alert definition 'xxxx' was deleted.
Action:
None.
2609I
ALERT DEFINITION xxxx ALTERED
Reason:
An ALERTDEF ALTER command or initialization statement was successfully processed.
System Action:
The Alert definition 'xxxx' was altered.
Action:
None.
2610I
ERROR PROCESSING ALERT COMMAND
Reason:
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:
Action:
2600 - 2699
2611I
ALERT DEFINITION xxxx NOT DEFINED
Reason:
An ALERTDEF LIST, DELETE or ALTER command or initialization statement was entered.
The specified Alert ID was not currently defined.
System Action:
Action:
2612I
ALERT DEFINITION xxxx ALREADY DEFINED
Reason:
An ALERTDEF ADD command or initialization statement was entered. The specified Alert
ID has already been defined.
System Action:
Action:
2600 - 2699
2613E
NODE operand of XMITMDL ADD invalid for ISCOPT NETWORK
Reason:
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:
action message 802A is issued to prompt for an END reply to ignore the command, a
CANCEL reply to terminate the product, or a initialization command reply. If the
XMITMDL ADD command was specified as an operator command, then it is ignored.
Action:
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 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
Reason:
A PREALLOC ALLOC command or initialization statement was successfully processed.
System Action:
The data set 'xxxx' was allocated to DD name 'yyyy'.
Action:
None.
2600 - 2699
2615I
DATA SET xxxx REMOVED FROM PREALLOCATION LIST
Reason:
A PREALLOC UNALLOC command or initialization statement was successfully processed.
System Action:
The data set 'xxxx' was deallocated.
Action:
None.
2616I
DATA SET xxxx ALREADY PREALLOCATED
Reason:
A PREALLOC ALLOC command or initialization statement was entered. The data set 'xxxx'
was already preallocated.
System Action:
Action:
2617I
DATA SET xxxx NOT CURRENTLY PREALLOCATED
Reason:
A PREALLOC UNALLOC command or initialization statement was entered. The data set
'xxxx' was not currently preallocated.
System Action:
Action:
2600 - 2699
2619I
BAD TTPBF RECEIVED
Reason:
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.
Action:
2620E
USER xxxx NOT AUTHORIZED FOR SYMTAB yyyy
Reason:
System Action:
The event will not execute.
Action:
2621I
BAD XME RECEIVED
Reason:
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.
Action:
2600 - 2699
2622E
Reason:
System Action:
Action:
respectively.
2623I
Sending a TTPBF with nn XMEs to xxxx
Reason:
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 CA
Support.
Action:
None.
2600 - 2699
2624W
INSUFFICIENT MAIN STORAGE FOR GQSCAN REQUEST
Reason:
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.
Action:
Increase the region size available to the job.
2625W
NO MATCHING UCBS FOUND
Reason:
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.
Action:
Ensure the correct volume serial number or prefix was specified.
2626C
xxxx
Reason:
The current CSA usage was listed in response to a request to list current CSA usage.
System Action:
None.
Action:
None.
2600 - 2699
2627W
Cannot execute requested function on an ESP proxy subsystem when JOBINDEX data
set is not shared
Reason:
A user attempted a command that would require updating the JobIndex file. The
subsystem the command was issued from was not a MASTER and the JobIndex did not
have the SHR attribute. This could lead to an integrity exposure.
System Action:
Action:
Reissue the command from a master subsystem.
2628I
Third party SAF profiles refreshed
Reason:
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.
System Action:
None.
Action:
None.
2600 - 2699
2629W
Simulated 3rd party RACHECK not active
Reason:
The SAFREFR command was entered to refresh the profiles used by the simulated third
party RACHECK function. However, the simulated third party RACHECK option was not
active.
System Action:
None.
Action:
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
Reason:
The utility routine CYBESUDI was invoked with no function verb.
System Action:
Action:
Specify a function verb, such as RESYNCH to resynchronize the data set trigger entries.
2631W
No Eventsets currently open, Resynch request ignored
Reason:
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:
Action:
Ensure at least one Eventset is defined, or open.
2600 - 2699
2632I
A total of nn data set trigger entries rebuilt
Reason:
The data set trigger resynch utility has completed. The message indicates how many
data set trigger entries were rebuilt.
System Action:
None.
Action:
None.
2633I
nn data set trigger entries rebuilt for Eventset xxxx
Reason:
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.
Action:
None.
2634I
A total of nn DXEs deleted in nn blocks
Reason:
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.
Action:
None.
2600 - 2699
2635C
Usermod Status
Reason:
This message precedes the display of the currently active usermod options. Usermod
options are installation selectable user requested modifications.
System Action:
None.
Action:
None.
2636I
Event Message Limits are currently set to nn, nn
Reason:
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.
System Action:
Action:
None.
2637I
Event Message Limits are currently inactive
Reason:
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.
System Action:
Action:
None.
2600 - 2699
2638I
NO USER DEF BACKUP TIME SET
Reason:
There is currently no scheduled time set for a backup of the USERDEF data set.
System Action:
None.
Action:
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.
2639E
Prompt terminated: Reason(aa) PromptToken(bb)
Reason:
A z/OS Agent issued a mode message to prompt a client for input, but stopped waiting
for a reply. Diagnostic data:
aa - Reason: time-out, cancellation of the prompt by the client, or z/OS Agent

termination.
bb - PromptToken of the interrupted prompt.
System Action:
The z/OS Agent event initiator that was waiting for a reply registers an end-of-data
condition for the command it was processing.
Action:
Examine the reason and determine whether to resubmit the command that caused the
prompt to be issued.
2600 - 2699
2640E
Message limit of 1048576 exceeded.
Reason:
The MSGLIMIT command was entered with an excessive limit value.
System Action:
Action:
Re-issue the command with a limit value of less than 1048576.
2641E
PURGSCHF TIME IS NOT IN THE PAST
Reason:
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.
Action:
Re-enter the command with a date in the past.
2643I
COMMAND PREFIX xxxx CANCELLED
Reason:
A request to cancel command prefix "xxxx" was successful.
System Action:
The command prefix "xxxx" is no longer honored.
Action:
None.
2600 - 2699
2640E
Message limit of 1048576 exceeded.
Reason:
The MSGLIMIT command was entered with an excessive limit value.
System Action:
Action:
Re-issue the command with a limit value of less than 1048576.
2645I
COMMAND PREFIX xxxx {ADDED | REPLACED}
Reason:
A request to update command prefix "xxxx" was successful.
System Action:
The command prefix "xxxx" is updated.
Action:
None.
2646E
INVOKE nesting limit of 10 exceeded, INVOKE ignored
Reason:
In a 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.
Action:
If there is not a recursion loop, restructure the procedure to have a maximum nesting
depth of 10.
2600 - 2699
2647E
Insufficient checkpoint space to build DSTRIG object list. Resynch cancelled.
Reason:
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.
Action:
None.
2648I
DSTRIG object entries rebuilt. Triggering <not> unquiesced.
Reason:
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.
System Action:
Action:
None.
2649W
Previous RESYNCH process has not finished yet. Request ignored.
Reason:
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:
Action:
After the workload object package completes building DXEs, it will issue message 2648I.
2600 - 2699
2650E
DSTRIG <job{.qual}: Trigger data not defined.
Reason:
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.
Action:
Provide a correct trigger description within the DSTRIG workload object definition.
2651E
EVENT NOT SPECIFIED WITH COUNT
Reason:
A SYSMSGS command specified a COUNT parameter but no corresponding EVENT
parameter.
System Action:
Action:
Correct the command and re-issue it.
2652E
MESSAGE TEXT NOT SPECIFIED
Reason:
A SYSMSGS command specified parameters which required the message text but none
was specified.
System Action:
Action:
2600 - 2699
2653E
MESSAGE TEXT NOT ALLOWED
Reason:
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:
Action:
2654E
key_name KEYWORD MISSING
Reason:
A SYSMSGS command specified a request such as IGNORE, DISABLE or DISABLE but did
not specify the additional named keyword which is required.
System Action:
Action:
2655E
EXTRANEOUS KEYWORD SPECIFIED
Reason:
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.
System Action:
Action:
2600 - 2699
2656E
ID NOT FOUND
Reason:
A SYSMSGS command specified an ID parameter but no message with a matching
identifier was found.
System Action:
Action:
2657I
MESSAGE ID(S) CLEARED
Reason:
The message(s) requested by the CLRSYSMS command have been cleared.
System Action:
Action:
None required.
2658E
MISSING MESSAGE ID
Reason:
A CLRSYSMS command did not specify an ID parameter.
System Action:
Action:
2600 - 2699
2659E
MESSAGE ID NOT FOUND
Reason:
A CLRSYSMS command specified an ID parameter but no message with a matching
identifier was found.
System Action:
Action:
2661E
MISSING EVENT NAME
Reason:
A MAPGEN command did not specify an EVENT parameter.
System Action:
Action:
2662E
NO MATCHING EVENTS
Reason:
A MAPGEN specified an EVENT parameter but no event names which correspond to the
value specified were found.
System Action:
Action:
2600 - 2699
2663E
MISSING DATA SET NAME
Reason:
A JOBMAP command did not specify a DSN parameter.
System Action:
Action:
2664E
ILLEGAL NODISPLAY
Reason:
A JOBMAP specified a NODISPAY parameter but one of the items in the list did not
correspond to a documented legal value.
System Action:
Action:
2665E
DATA SET xxxx IS NOT SEQUENTIAL
Reason:
A JOBMAP command was specified. However, the data set was not a sequential data
set.
System Action:
The map data set cannot be processed.
Action:
Specify a sequential data set and reissue the command.
2600 - 2699
2666W
NO JOBS FOUND
Reason:
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:
Action:
Either specify a different data set or a different APPL parameter and reissue the
command.
2667E
Reason:
The data set specified in the JOBMAP command could not be processed. This could be
System Action:
Action:
2668E
MISSING DATA SET NAME
Reason:
A JOBTREE command did not specify a DSN parameter.
System Action:
Action:
2600 - 2699
2669E
MISSING JOB NAME
Reason:
A JOBTREE command did not specify a JOB parameter.
System Action:
Action:
2670E
DATA SET xxxx IS NOT SEQUENTIAL
Reason:
A JOBTREE command was specified. However, the data set was not a sequential data
set.
System Action:
The map data set cannot be processed.
Action:
Specify a sequential data set and reissue the command.
2671E
JOB NOT FOUND
Reason:
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 the product
could not find the named job in the named application.
System Action:
Action:
2600 - 2699
2672E
Reason:
The data set specified in the JOBTREE command could not be processed. This could be
System Action:
Action:
2673E
INVALID COUNT VALUE
Reason:
A SYSMSGS command specified a COUNT parameter that was either negative or greater
than 255.
System Action:
Action:
2674E
MISSING DATASET NAME
Reason:
A MAPGEN command did not specify a DATASET parameter.
System Action:
Action:
2600 - 2699
2675E
EVENTFILE NOT FOUND
Reason:
The event file specified in the MAPGEN command was not defined in the checkpoint.
System Action:
Action:
Correct the name of the data set, or define it to the product.
2676E
INVALID JOBNAME/QUALIFIER
Reason:
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.
System Action:
Action:
2677E
Reason:
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.
Action:
Try to unwait the generation nn of the application xxxx. Notify CA Support.
2600 - 2699
2678E
Reason:
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.
Action:
If the I/O error is corrected, try to unwait the generation nn of the application xxxx. If it
fails, notify CA Support.
2679E
ABOVE I/O ERROR OCCURRED WRITING APPL xxxx, GENERATION nn
Reason:
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.
Action:
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
Reason:
More than 50 predecessors or successors were specified on the APPLJOB command.
System Action:
Action:
2600 - 2699
2681E
Simulation of a WOB with the AGENT command is not valid on a local proxy
subsystem.
Reason:
Simulation on a local proxy subsystem encountered a WOB definition containing the
AGENT command.
System Action:
Simulation continues.
Action:
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 High
Availability Option or the High Performance Option is installed.
2682E
INVALID RELATIONSHIP SPECIFICATION x
Reason:
The conditional relationship for predecessor or successor jobs on the APPLJOB
command was not one of A, N or U.
System Action:
Action:
2683E
COMMAND NOT ALLOWED
Reason:
USERMOD 35 has not been activated to enable the APPLJOB command from the
operator console.
System Action:
Action:
2600 - 2699
2684E
NO FUNCTION SPECIFIED
Reason:
The COMPLETE parameter was not specified on the APPLJOB command from the
operator console.
System Action:
Action:
2685E
MISSING APPLICATION NAME
Reason:
The APPL parameter was not specified on the APPLJOB command from the operator
console.
System Action:
Action:
2686E
VS COMMAND HAS MISSING OPERAND
Reason:
VS Command has been submitted with no operand. The most likely cause for this is a
missing continuation character in a procedure, or a missing USERn parameter.
System Action:
Command rejected.
Action:
Correct the procedure, and retry.
2600 - 2699
2689I
Job xxxx{.yyyy}(Jnnnn) resumed, no longer on critical path
Reason:
An active job in an 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.
Action:
None.
2690I
AUX_AS is active, ASCB at xxxxxxxx ASID xxxx Name xxxxxxxx AUX_AS is not active
Reason:
The operator issued an AUX_AS command with no operands. The product is displaying
current status information about the auxiliary address space.
System Action:
None.
Action:
None normally required. If the second form of response is issued, but an auxiliary
address space is required, issue an "AUX_AS START" command.
2600 - 2699
2691E
AUX_AS failed, SS006 return code is n AUX_AS is not active
Reason:
The AUX_AS command called SS006 to execute the function, but SS006 failed. If the
error involved the creation of the address space, then message 0710S will have also
been issued with the details of the problem.
System Action:
The request was not executed.
Action:
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
Reason:
An AUX_AS command was issued, but the present subsystem does not use an auxiliary
address space.
System Action:
Action:
None.
2600 - 2699
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 job qualifier
zzzz - specifies the expedite policy name.
Reason:
Response to "XP" line command from CSF or to "AJ xxxx{.yyyy} EXPEDITE" command in
page mode or 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:
Action:
If job xxxx{.yyyy} could not be expedited because it has no expedite policy associated
with it, an expedite policy should be defined using the EXPEDITE command, and
associated with the job's application using the application EXPEDITE statement.
If job xxxx{.yyyy} could not be expedited because expedite policy zzzz is not defined,
then it should be defined using ADD option of the 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 using the ALTER keyword of the 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 the
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.
2600 - 2699
2695E
EXPEDITE policy name missing
Reason:
An EXPEDITE statement in an application procedure does not specify an expedite policy
name.
System Action:
The application does not execute.
Action:
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}}
Reason:
An application contains an EXPEDITE statement specifying expedite policy aaaa.
However, user bbbb, under which 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.
Action:
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 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 application procedure.
2600 - 2699
2697S
Invalid system command request code nnnn
Reason:
Internal logic error. Should never happen.
System Action:
Action:
2698I
{Submitted|Executing} job xxxx{.yyyy}(Jnnnn) expedited {manually{ by user zzzz}|{,
{start|end} time overdue}{, on critical path}}
yyyy - specifies the job qualifier.
zzzz - specifies the manual expedite issuer's userid. nnnn specifies the JES job
number.
Reason:
A job in an application has been expedited. The reason is specified in the message.
System Action:
Action:
None.
2700 - 2799
2700 - 2799
2700E
2700E CYBSS030 XJOBSTAT: {JSRA invalid|Job name missing}
Reason:
An invalid internal job status subsystem request was issued.
System Action:
The job status subsystem request is rejected.
Action:
This is an internal logic error that should never occur. If it does, call CA Support.
2701E
2701E CYBSS030 IEFSSREQ XStatus, {RtnCode|SSOBRETN}=<rc>
Reason:
An internal job status subsystem request returned error code <rc>
System Action:
The job status subsystem request is rejected.
Action:
If unable to determine the cause of the job status subsystem request failure, call CA
Support.
2711E
SITECMD too long
Reason:
The length of the SITECMD exceeds the maximum of 4070 characters.
System Action:
The event fails. The object is not generated.
Action:
Reduce the length of the SITECMD statement.
2700 - 2799
2712I
Program <name> loaded{ from {PLPA|FLPA|MLPA|EPLPA|EFLPA|EMLPA|<dsname>
in LINKLIST|JOBLIB|STEPLIB|<tasklib>}}
Reason:
Response to one of the following commands - OPER CALLRTN CYBUT009 <name>
DLMOD <name> Load module <name> is loaded and deleted and its location is
displayed. PLPA specifies the Pageable Link Pack Area FLPA specifies the Fixed Link Pack
Area MLPA specifies the Modified Link Pack Area EPLPA specifies the Extended Pageable
Link Pack Area EFLPA specifies the Extended Fixed Link Pack Area EMLPA specifies the
Extended Modified Link Pack Area.
<dsname> - specifies the load module library data set name.
<tasklib> - specifies the task library where the load module was found.
System Action:
Action:
None.
2713W
Error Sxxx{-xx} loading program <name>{ from <dsname>
LINKLIST|JOBLIB|STEPLIB|<tasklib>}
Reason:
Response to one of the following commands - OPER CALLRTN CYBUT009 <name>
DLMOD <name> An attempt to load module <name> failed with completion code xxx
and reason code xx.
<dsname> - specifies the load module library data set name.
<tasklib> - specifies the task library where the load module was found.
System Action:
Action:
None.
2700 - 2799
2714C
Display File
Reason:
Response to one of the following commands - OPER CALLRTN CYBUT010 <ddname>|ALL
DLMOD <ddname>|ALL File <ddname> is displayed if <ddname> was specified. All files
are displayed if ALL was specified.
System Action:
Action:
None.
2715W
File <ddname> not found
Reason:
Response to one of the following commands - OPER CALLRTN CYBUT010 <ddname>
DLMOD <ddname> File <ddname> was not found.
System Action:
Action:
None.
2716C
Display LinkList
Reason:
Response to one of the following commands - OPER CALLRTN CYBUT011{ <lsname>}
DLNKLST{ <lsname>} LINKLIST set name <lsname> is displayed if <lsname> was specified.
The current job's active LINKLIST set is displayed if <lsname> was omitted.
System Action:
Action:
None.
2700 - 2799
2717W
LINKLIST set <lsname> not found
Reason:
Response to one of the following commands - OPER CALLRTN CYBUT011 <lsname>
DLNKLST <lsname> LINKLIST set <lsname> was not found.
System Action:
Action:
None.
2720W
UNABLE TO ALLOCATE xxxx, S99 ERROR CODE X'yyyy', INFO CODE X'zzzz'
Reason:
An error occurred during a dynamic allocation request.
System Action:
Action:
Take note of the following message.
2721W
UNABLE TO ALLOCATE xxxx, VOLUME OFFLINE
Reason:
An error occurred during a dynamic allocation request due to a required volume being
offline.
System Action:
Action:
2700 - 2799
2722W
DATA SET xxxx NOT CATALOGUED
Reason:
An error occurred during a dynamic allocation request due to a data set not being
catalogued.
System Action:
Action:
2723W
UNABLE TO GET EXCLUSIVE ALLOCATION TO DATA SET xxxx
Reason:
A data set that is needed exclusively was already allocated to another user.
System Action:
Action:
2724W
UNABLE TO GET SHARED ALLOCATION TO DATA SET xxxx
Reason:
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.
Action:
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.
2700 - 2799
2725W
DATA SET xxxx NOT ON {CATALOGUED VOLUME | VOLUME yyyy}
Reason:
A data set was not found on the volume as catalogued or explicitly specified.
System Action:
Action:
2726W
ACCESS TO DATA SET xxxx DENIED BY INSTALLATION SAF SECURITY
Reason:
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.
Action:
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'
Reason:
An error occurred while performing a dynamic unallocation.
System Action:
Action:
2700 - 2799
2728E
UNABLE TO PERFORM TASK SWITCH
Reason:
The product tried to switch to a subtask to perform an allocation request. The task
switch failed.
System Action:
Action:
2729E
UNABLE TO REVERT TO MAIN TASK
Reason:
After an allocation was performed on a subtask, the routine was unable to rejoin the
main task.
System Action:
Action:
2730W
Data set xxxx is migrated
Reason:
An error occurred during a dynamic allocation request due to a required data set being
migrated.
System Action:
Action:
2700 - 2799
2731I
Custom character table loaded: <dsn>
Reason:
The address space that issued this message is performing initializations and has
successfully loaded a data set containing custom ASCII-EBCDIC and EBCDIC-ASCII
characterconversion tables.
System Action:
Action:
None.
2732E
CUSTCTBL error: <reason>
Reason:
The address space that issued this message is performing initializations and did not
successfully load a data set containing custom ASCII-EBCDIC and EBCDIC-ASCII characterconversion tables.
System Action:
The address space applies its policy regarding initialization errors.
Action:
If the <reason> given in the message is not self-explanatory, look for other messages in
the system log. If the initialization parameters contain a faulty CUSTCTBL statement,
apply the necessary correction.
2739W
Variable name length of xxx exceeds maximum of 256 characters
Reason:
A symbolic variable name contained xxx characters. This exceeds the maximum allowed.
System Action:
Action:
Shorten the name.
2700 - 2799
2740W
SYMBOL xxxx NOT DEFINED
Reason:
A request was issued to alter or delete symbol 'xxxx'. Symbol 'xxxx' is not currently
defined.
System Action:
Action:
Ensure the correct symbol is specified.
2741W
SYMBOL xxxx ALREADY DEFINED
Reason:
A request was issued to define symbol 'xxxx'. Symbol 'xxxx' is already defined.
System Action:
Action:
2742W
SYMBOL xxxx IS READ ONLY
Reason:
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:
Action:
2700 - 2799
2743W
INVALID SYMBOL TABLE ENTRY
Reason:
A request was issued to insert a symbol. The specified symbol was not defined to be
binary, Boolean, character or floating point.
System Action:
Action:
Correct the symbol definition. If the problem persists, notify your system support
personnel.
2744E
INVALID SUBSTRING SPECIFICATION
Reason:
A request was issued to process a substring. The specification for the substring in not
valid.
System Action:
Action:
Correct the substring specification. If the problem persists, notify your system support
personnel.
2745W
DATA TOO LONG FOR SYMBOL xxxx
Reason:
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:
Action:
Increase the symbol length or decrease the length of the symbol value.
2700 - 2799
2746W
INCONSISTENT PARAMETERS REQUESTED FOR SYMBOL xxxx
Reason:
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:
Action:
Correct the symbol specification.
2747E
INCOMPLETE SYMBOL SPECIFICATION
Reason:
A symbol value contained a subfield specification. The subfield contained unbalanced
parentheses or quotes.
System Action:
Action:
Correct the subfield specification.
2748E
INVALID SYMBOL SPECIFICATION
Reason:
A compound symbol contained an invalid character or built-in function routine
determined the symbol was invalid.
System Action:
Action:
Correct the symbol specification.
2700 - 2799
2749E
INVALID FORMAT DESCRIPTOR
Reason:
A statement specified an invalid symbol output format descriptor.
System Action:
Action:
Correct the output format descriptor.
2750E
EXPRESSION CONTAINS DIVIDE BY ZERO
Reason:
An evaluated expression contains a operation which would cause a divide by zero.
System Action:
Action:
Correct the evaluated expression.
2751E
INVALID EXPRESSION
Reason:
A statement contains an invalid expression.
System Action:
Action:
Correct the evaluated expression.
2700 - 2799
2752E
Internal error - symbol xxxx
Reason:
An internal error was encountered trying to process symbol xxxx.
System Action:
Processing for the symbol is terminated.
Action:
2754E
Not in line mode
Reason:
The user attempted to enter a UTIL command while in page mode.
System Action:
Action:
When in page mode, the user must first enter line mode using the @LINEMD command
before entering the UTIL command. After all UTIL functions have been performed, the
user can exit from line mode using the END command.
2700 - 2799
2755E
IAE xxxx byte subpool yyy core request failed
Reason:
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.
Action:
This request is most likely to fail when the subsystem request originates from a client
(TSO or 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.
2757E
Reason:
There was insufficient space in the ATR to store data for a DSTRIG job jjjj in application
aaaa.
System Action:
Action:
2700 - 2799
2758E
Error in JOBDATA function - 'Reason string'
Reason:
An error occurred in the JOBDATA CLANG function. The reason string contains further
details about the error.
System Action:
Processing ends.
Action:
This is most likely a syntax error. Check for an invalid job name or missing parameters.
2760E
DUPLICATE KEY AT OFFSET xxxxxx FOR RECORD nnnnn KEY=value
Reason:
While writing to the database, a duplicate record was encountered.
System Action:
Processing continues. The information for a specific job might be lost.
Action:
2761E
VSAM ERROR EXIT AT OFFSET xxxxxx for RECORD nnnnn
Reason:
An internal VSAM error has been detected while performing database I/O.
System Action:
Processing is terminated. The database is not usable.
Action:
2700 - 2799
2762E
RETURN CODE nn AT OFFSET xxxxxx ON RECORD nnnnn
Reason:
A VSAM error has been detected while performing database I/O.
System Action:
Processing is terminated. The database is not usable.
Action:
2763E
INPUT FILE ERROR
Reason:
A I/O error has been detected while reading the input file.
System Action:
Action:
Correct the I/O error and re-run the job.
2764E
MISSING TO DATE
Reason:
A control statement specified a FROM date but no TO date.
System Action:
Action:
Correct the error and re-run the job.
2700 - 2799
2765E
CONFLICTING DATES
Reason:
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:
Action:
2766E
MISSING DATE
Reason:
A control statement specified neither a DATE parameter or a FROM-TO date range.
System Action:
Action:
2767E
VSAM ERROR EXIT FOR function_name
Reason:
An internal VSAM error has been detected while performing database I/O.
System Action:
Action:
2700 - 2799
2768E
RETURN CODE nn FROM FUNCTION function_name
Reason:
A VSAM error has been detected while performing database I/O.
System Action:
Action:
2769E
MISSING EVENT NAME
Reason:
A control statement specified a PREFIX parameter with no NAME parameter.
System Action:
Action:
2770E
EVENT AND APPL MUTUALLY EXCLUSIVE
Reason:
A control statement specified both an APPL parameter and event parameters.
System Action:
Action:
2700 - 2799
2771E
NEITHER EVENT NOR APPL MUTUALLY SPECIFIED
Reason:
A control statement specified neither an APPL parameter nor event parameters.
System Action:
Action:
2772E
NO CONTROL STATEMENTS
Reason:
No valid control statements were present in the input.
System Action:
Action:
2773E
APPL appl_name NOT FOUND
Reason:
The named application was not present in the database.
System Action:
Action:
2700 - 2799
2774E
EVENT prefix.name NOT FOUND
Reason:
The named event was not present in the database.
System Action:
Action:
2775E
ILLEGAL ORDER
Reason:
The ORDER parameter on the FLOWDOC command was not one of NAME or RUN.
System Action:
Action:
Correct the statement and re-run the job.
2776E
DATABASE FULL AT OFFSET xxxxxx FOR RECORD nnnnn
Reason:
The database has run out of space on the volume.
System Action:
Processing is terminated. The database is unusable.
Action:
Re-allocate the database on a volume with more free space.
2700 - 2799
2777E
ILLEGAL COMMAND
Reason:
An unknown command was entered.
System Action:
Action:
Rerun the job using valid command input.
2778E
INVALID OBJECT TYPE SPECIFIED FOR RESUMED OBJECT DEFINITION
Reason:
A resumed object definition in application refers to a different object type.
System Action:
The application is not processed.
Action:
Either change an object type appropriately, or change an object name.
2779I
DEFINITION OF OBJECT xxxx IN APPL yyyy RESUMED APPL GENERATION x IN APPL yyyy
RESUMED CONTINUES
Reason:
A resumed object definition in application refers to the same object type.
System Action:
The processing continues.
Action:
Check the object definition, that caused this message to be issued.
2700 - 2799
2780E
xxxx
Reason:
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
System Action:
Action:
Correct the problem and rerun the job.
2781E
Reason:
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:
Action:
2700 - 2799
2782E
Reason:
A problem was encountered while parsing the command.
System Action:
Action:
respectively.
2799W
Cannot delete CPU - invalid use of keyword FORCE
Reason:
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.
Action:
If you really want to delete that CPU remove FORCE keyword from the command.
2800 - 2899
2800 - 2899
2800W
xxxx is the only CPU defined, you cannot delete the last CPU unless it is inactive and
FORCE keyword is used
Reason:
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.
Action:
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
Reason:
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.
Action:
Set the CPU to INACTIVE first, in order to prevent more jobs from being routed to it.
Then retry the command again later.
2800 - 2899
2802E
Logic error encountered in CPU delete routine
Reason:
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:
The product will follow this with a user abend 2802 to prevent the Resfile from being
damaged.
Action:
2803W
Unable to delete node xxxx, delete attached CPU(s) first
Reason:
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.
Action:
Use the CPU command to delete any CPUs attached to this node. When that has been
successfully performed, reissue the NODE delete command.
2800 - 2899
2804E
Scope cannot be changed with SET. Resource xxxx not updated
Reason:
A RESDEF SET command was issued, and a scope was specified (that is, ENTERPRISE,
GLOBAL, or LOCAL). However, the scope of the resource cannot be changed with the SET
verb.
System Action:
Action:
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
Reason:
A RESDEF SET command was issued, and a type was specified (that is, RENEWABLE,
DEPLETABLE or THRESHOLD). However, the type of the resource cannot be changed
with the SET verb.
System Action:
Action:
To change the type, delete the resource with RESDEF DELETE and then create it once
again with RESDEF ADD, specifying the new type.
2800 - 2899
2806W
AUTHORIZATION TABLE NOT ACTIVE
Reason:
In a SAF environment, Authorization Tables are not applicable, therefore the user should
not try to list an AT.
System Action:
Action:
Do not use LISTAT in a SAF-based system.
2807E
JCL LIBRARY MEMBER xxxx MISSING %ENDINCL OR %ENDEXCL
Reason:
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.
Action:
The user should edit the JCL library member in question and insert either a %ENDINCL or
%ENDEXCL, whichever is appropriate.
2808E
MESSAGE TEXT REQUIRED FOR SYSMSGS STATEMENT
Reason:
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.
Action:
Enter the SSYSMSGS command with the message text enclosed in apostrophes.
2800 - 2899
2809?
PUTLINE ERROR CODE nn
Reason:
A PUTLINE informational message has failed. The PUTLINE return code is nn.
System Action:
Action:
2810?
PUTLINE ERROR CODE nn
Reason:
A PUTLINE data message has failed. The PUTLINE return code is nn.
System Action:
Action:
2811?
PARM=xxxx yyyy zzzz aaaa
Reason:
A PUTLINE informational message has failed. The PUTLINE parameters are listed.
System Action:
This message is preceded by message 2809.
Action:
2800 - 2899
2812W
Unable to free output data set, RC=nn
Reason:
The GENPROJ command attempted to free the output data set. The attempt failed with
an SVC 99 return code 'nn'.
System Action:
Action:
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
Reason:
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).
Action:
The user should remove the continuation from the procedure DO statements or remove
the extraneous commands on the DO statements and retry the procedure to ensure
that proper results are obtained.
2800 - 2899
2814E
REEXEC MAXIMUM cannot be greater than 65535
Reason:
The MAXIMUM parameter entered on the REEXEC statement is higher than the
maximum value allowed. This value should be less than or equal to 65535.
System Action:
The procedure is ended with an error condition.
Action:
The user should specify a valid MAXIMUM on the REEXEC command and reenter the
command or rerun the procedure.
2815E
ROUTEJCL SPECIFIES ILLEGAL VALUE
Reason:
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.
Action:
Correct the ROUTEJCL parameter and either re-enter the command or restart the
product.
2816E
ROUTEJCL SPECIFIES ILLEGAL VALUE
Reason:
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.
Action:
Correct the ROUTEJCL parameter and either re-enter the command or restart the
product.
2800 - 2899
2818E
INVALID COMMAND ENTERED, ONLY LISTSYML ALLOWED
Reason:
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.
Action:
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
Reason:
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.
Action:
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.
2800 - 2899
2821E
JOB xxxx IS WAITING FOR RESOURCES, CANNOT BE RESET
Reason:
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.
Action:
The user should verify that the proper job was selected for the RESET.
2822E
JOB xxxx IS WAITING FOR RESOURCES, CANNOT DROP DEPENDENCIES
Reason:
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.
Action:
The user should verify that the proper job was selected for the DROPDEP.
2800 - 2899
2823E
Command exceeded internal buffer
Reason:
While processing a WOBCMD or JOBRES command, the internally generated
Automation Framework Message (AFM) exceeded the capacity of the buffer.
System Action:
Action:
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
Reason:
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.
Action:
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.
2800 - 2899
2825W
DEFAULT CALENDAR IS BEING SET TO SYSTEM FOR USER xxxx
Reason:
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.
Action:
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
Reason:
A value larger than 255 appeared as the operand of the RELDELAY statement.
System Action:
Action:
Specify a value of 255 or less minutes for the release delay.
2800 - 2899
2827E
BAD JOB NAME xxxxxxxx IN APPL, EXPECTED yyyyyyyy
Reason:
When the product 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:
The product does not submit the job with the offending job name.
Action:
The user should look at the job name on the product 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
Reason:
When the product 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:
The product does not submit the job with the offending job name.
Action:
The user should look at the member name on the 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.
2800 - 2899
2829E
A SIGLOST condition cannot be deleted
Reason:
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:
Action:
None.
2830E
Unable to locate port nn
Reason:
A STATCHAN or RESPCHAN command specified a port that cannot be found. The port is
erroneous or the channel has been closed.
System Action:
Action:
Correct the port and resubmit the command.
2831I
Status channel successfully established
Reason:
A STATCHAN command was successfully executed and a status channel has been
opened.
System Action:
Action:
None.
2800 - 2899
2832I
Status channel ending
Reason:
A status channel has been shut down.
System Action:
Action:
None if the status channel shutdown was requested or is understood. If investigation is
required, contact CA Support.
2833E
Port aaaa already has a status channel
Reason:
A status channel has already been opened through the specified port. A successful
STATCHAN command was probably executed earlier.
System Action:
Action:
If investigation is required, contact CA Support.
2834E
Port nn is the current port
Reason:
A STATCHAN or RESPCHAN command specifies the port of the channel through which
the command was sent.
System Action:
Action:
Correct the port id and resubmit the command.
2800 - 2899
2835E
Logon failed, SAF error code xx-yy
Reason:
Logon failed, expected values for error codes are:
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 the product
8-104 Second copy of new password doesn't match first
System Action:
Logon fails.
Action:
Correct the logon information as required.
2836I
Logon successful
Reason:
A USER or LOGON command was successfully executed. The user is logged on.
System Action:
Action:
None.
2800 - 2899
2837E
Error in filter request string
Reason:
An error was detected in a filter string.
System Action:
The command is rejected. Processing continues.
Action:
Correct the filter string. If necessary, review the syntax of the filter.
2838E
No secondary channel defined
Reason:
An action that requires a secondary or status channel cannot proceed because the
channel has not yet been established.
System Action:
Action:
If appropriate, issue a STATCHAN command and retry.
2839E
variable text
Reason:
A GETFILE command was in progress and the command processor's SYNAD routine was
entered with a prepared message whose content is situation-dependent. For example, if
the GETFILE processor was asked to read a PDS member that does not exist, the text
would report "MEMBER 'aaaa' NOT FOUND" and state the data set name. If the LOCK
keyword was not specified, the request would fail. If the LOCK keyword was specified,
the PUTFILE command can be used to create a new member.
System Action:
Situation-dependent. The request might fail.
Action:
Examine the message text and, if appropriate, take action.
2800 - 2899
2840E
Data set has an unsupported format
Reason:
A GETFILE command cannot proceed because the format of the target data set is not
supported.
System Action:
Action:
Review the data set types supported by the GEFTILE command.
2841I
File stored
Reason:
The target data set of a PUTFILE command has been saved.
System Action:
Action:
None.
2842I
File update cancelled
Reason:
A request to cancel a PUTFILE command in progress has been successfully processed.
System Action:
Action:
None.
2800 - 2899
2843E
variable text
Reason:
A PUTFILE command was in progress and the command processor's SYNAD routine was
entered with a prepared message whose content is situation-dependent. For example, if
the PUTFILE processor was creating or updating a member of a PDS that needs to be
compressed, the text would report "ABEND E37-04" and state the data set name.
System Action:
Action:
Examine the message text and, if appropriate, take action. If, for example, a PDS has run
out of extents, compress the PDS before retrying the PUTFILE command.
2844E
Invalid input, connection will be closed
Reason:
A PUTFILE command was in progress and the command processor received invalid input.
The PUTFILE command is normally used only by automated processes, so the invalid
input might be due to an internal logic error in the automated process that initiated the
PUTFILE.
System Action:
Action:
This is probably due to an internal logic error. Contact CA Support.
2800 - 2899
2845E
LUNAME and xxxx parameters are mutually exclusive
Reason:
The work station server LUNAME JCL initialization parameter was specified with a
mutually exclusive TCP/IP initialization parameter.
System Action:
Work station server terminates.
Action:
Specify either LUNAME or TCP/IP initialization parameter(s), but not both, for work
station server.
2846E
Port or LUname parameter is required
Reason:
Either the PORT or the LUNAME JCL initialization parameter is required to start work
station server.
System Action:
Action:
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
Reason:
A work station client connection has terminated.
System Action:
Action:
None.
2800 - 2899
2858E
ESP subsystem xxxx not found
Reason:
Work station server could not find the subsystem specified by the SUBSYS JCL
System Action:
Action:
If the SUBSYS parameter is valid, start the 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
Reason:
The value coded on DURATION statements exceeds the allowed maximum of 6553.
System Action:
The application will not be built.
Action:
Correct the value.
2860E
Member|File aaaa in use
Reason:
A PUTFILE command was issued for a data set or PDS member that is already locked by
another user or program.
System Action:
Action:
If appropriate, wait for the data set to become available. If the address space of an
Workstation Server or Agent for z/OS appears to be holding a data set it should have
released, your CA Support personnel can issue an UNDOLOCK command to forcibly
release the data set.
2800 - 2899
2870C
Non-SAF user ID mappings
Reason:
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
Action:
N/A
2871I
No User ID mappings defined
Reason:
This message is issued in response to the MAPUSER OPER command. There are no
MAPUSER entries in AGENTDEF to display.
System Action:
None.
Action:
N/A
2800 - 2899
2888W
Connection rejected from nn.nn.nn.nn, reason code=xx
Reason:
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.
Action:
For reason 4, investigate whether the current connections are valid. For more than 250
connections, additional servers may be needed. Note that each WorkStation requires 2
connections, one each for the command and status channels. For reasons 8 and 12,
investigate the indicated IP address for a possible loop creating connections.
2900 - 2999
2900 - 2999
2971E
Invalid structure in JTR vvvv(wwww), error code xx: yyyy in zzzz
Reason:
During 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:
The product 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.
Action:
None.
2972E
Invalid structure in ATR aaaa.gggg, error code nn
Reason:
During 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:
The product will discontinue processing of this generation, unless the damage can be
repaired. Repair is not yet implemented.
Action:
None.
2900 - 2999
2978E
Asterisk not allowed in dataset name for DSTRIG
Reason:
The product encountered a DSTRIG event command that specifies a dataset name with
an imbedded asterisk.
System Action:
Action:
Specify a valid dataset name.
2979I
ESP Agent for z/OS release xxxx initialized, subsys yyyy
Reason:
The Agent for z/OS has completed its initialization.
System Action:
Action:
None.
2980I
ESP Agent for z/OS shutdown in progress, subsys xxxx
Reason:
A shutdown command was issued to the Agent for z/OS or a P or STOP command was
received.
System Action:
The Agent for z/OS continues with the shutdown.
Action:
None.
2900 - 2999
2981I
ESP Agent for z/OS release xxxx status
Reason:
This message introduces the display of the current status of the Agent for z/OS.
System Action:
The messages that follow will describe the current processing status of the Agent for
z/OS.
Action:
None

3000 - 3099
3000E
Invalid call to extended MCS console services
Reason:
System Action:
Action:
Contact CA Support.
3000 - 3099
3001I
Extended MCS console {not defined|cccc {already }{in}active{, Termname=tttt}{,
Key=kkkk}
Reason:
Response to the "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. This is the UserID that
issued the MCS command.
kkkk - specifies the extended MCS console key.
System Action:
Action:
None.
3002S
xMCS Activate parameter list not a valid MCRA
Reason:
System Action:
Action:
3000 - 3099
3003S
xCOMMAND parameter list not a valid CCRA
Reason:
System Action:
Action:
3004W
MCS console cccc alert detected, {Memory limit reached| Queue depth limit
reached|Internal error|Alert percentage reached| Request to suspend
operator|Reason unknown}
Reason:
A console alert, that is a console event that disrupts extended MCS console message
queuing, has occurred. cccc specifies the extended MCS console name.
System Action:
The extended MCS console is de-activated.
Action:
To restart the extended MCS console, enter the command - OPER MCS ACTIVATE
{NAME(cccc)} {KEY(kkkk)} where - cccc specifies an optional console name (default is the
SYSID). kkkk specifies an optional console key (default is no console key).
3000 - 3099
3005I
McsOp{er|Msg} {Activate|Deactivate|GetMsg|Req=nnn}, Console=cccc{,
Termname=tttt}{, Key=kkkk}
Reason:
An extended MCS console event has completed successfully.
cccc specifies the extended MCS console name.
tttt - specifies the extended MCS console terminal name. This is the UserID that
issued the MCS command.
kkkk - specifies the extended MCS console key.
nnn - specifies a request code if the request is unknown.
System Action:
Action:
None
3006E
McsOp{er|Msg} {Activate|Deactivate|GetMsg|Req=nnn}{, rrrr} {, Rtn=xx, Rsn=yy},
Console=cccc{, Key=kkkk}
Reason:
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. 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:
Action:
Attempt to determine the cause of the failure and, if possible, correct it. If unable to
correct the problem and/or it persists, contact your software support personnel.
3000 - 3099
3007E
xMCS {Activate|Deactivate}, xxxx
Reason:
Internal extended MCS console logic error. Should never happen. xxxx specifies the
reason for the error.
System Action:
Action:
3008E
xCommand text end address xxxxxxxx not within valid range yyyyyyyy-zzzzzzzz
Reason:
xxxxxxxx, yyyyyyyy and zzzzzzzz specify virtual storage addresses. Internal logic error.
Should never happen.
System Action:
Action:
3000 - 3099
3009I
MCS not active, system command response not retrievable
Reason:
CA Workload Automation EE could not retrieve the response to a system command that
it issued because it is not active as an extended MCS console.
System Action:
Action:
Activate CA Workload Automation EE as an extended MCS console. Then issue one of
the following operator commands:
MCS ACTIVATE
MCS A
This must be prefixed with OPER if issued in page mode or in line mode interface. In
addition, the following command should be added to the ESPPARM initialization file:
MCS ACTIVATE
3010E
MCS {NAME|KEY} keyword incompatible with {DEACTIVATE|STATUS} request
Reason:
The MCS operator command has been issued with incompatible parameters.
System Action:
Action:
Re-issue the MCS command with compatible parameters.
3000 - 3099
3011W
Time out waiting for system command response
Reason:
CA Workload Automation EE issued a system command and timed out waiting for a
system command. This may happen if the system is congested.
System Action:
Action:
Normally none. If the problem is persists and it does not appear to be due to system
congestion, call your software support personnel.
3012W
Job jjjj{.qqqq} on remote JES node, JES status not available
Reason:
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.
System Action:
Action:
None.
3000 - 3099
3013W
MCS not active, JES job display not available
Reason:
A $D CSF line command or an APPLJOB DISPLAY command was issued to display the JES
status of a job in an application. However, the command cannot be processed because
the 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:
Action:
Activate the subsystem as an extended MCS console. For the product, issue the
following operator command - MCS ACTIVATE or MCS A This must be prefixed with
OPER if issued in page mode or a line mode interface. In addition, the following
command should be added to the ESPPARM initialization file - MCS ACTIVATE
3014E
{ConsName=<consname>|ConsId=<consid>}{ invalid|, ConvCon RetCode=<retcode>}
Reason:
Console name <consname> or console id <consid> was specified to identify a console to
receive the response to a system command issued by CA Workload Automation EE. If a
VS event or procedure command was being processed, then the VS command specified
either the CONSNAME(<consname>) or the CONSID(<consid>) keyword operand.
Validation of the specified console using the CONVCON system service failed. If
CONVCON returned a code <retcode> exceeding 8, then <retcode> is displayed in the
message text.
System Action:
The system command is not issued. If the error occurred in an event or procedure VS
command, then the event does not execute.
Action:
Correct the console specification to identify a valid console. If the error occurred in an
event or procedure VS command, re-trigger the event after the console specification has
been corrected.
3000 - 3099
3015W
MCS de-activated, cannot retrieve system command response
Reason:
The CA Workload Automation EE extended MCS console was de-activated after a system
command was issued, but before the system command's response could be retrieved.
System Action:
Action:
If responses to system commands are not required, none. If responses to system
commands are required, then the CA Workload Automation EE extended MCS console
must be re-activated. Under the product, the "MCS ACTIVATE" command activates its
extended MCS console.
3016E
Default CONSOLE NAME xxxx is invalid - it must begin with A-Z, #, $ or @
Reason:
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:
Action:
Re-issue the MCS command with the correct console name.
3100 - 3199
3020E
COUNT MUST BE BETWEEN 0 AND 255
Reason:
The value selected is not within the permissible range.
System Action:
Action:
Correct the value and resave the event.
3021E
CURRENT MUST BE BETWEEN 0 AND 255
Reason:
The value selected is not within the permissible range.
System Action:
Action:
Correct the value and resave the event.
3100 - 3199
3100E
NO SAF CLASS DEFINED
Reason:
The SAF resource class is not defined by SAFCLASS command.
System Action:
Action:
3100 - 3199
3101E
INVALID REQUEST CODE
Reason:
Invalid request code specified in SAF request.
System Action:
Action:
3102E
RACF ERROR RECEIVED
Reason:
RACF error received while processing a SAF request.
System Action:
Action:
3103E
RACDEL ERROR CODE xxxx, REASON CODE yyyy
Reason:
RACF error code xxxx, reason code yyyy received while processing a SAF delete resource
request.
System Action:
Action:
3200 - 3299
3104E
RACDEF ERROR CODE xxxx, REASON CODE yyyy
Reason:
RACF error code xxxx, reason code yyyy received while processing a SAF define resource
request.
System Action:
Action:
3200 - 3299
3200E
Network node name required when network services requested
Reason:
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 system.
System Action:
The local system terminates.
Action:
For a subsystem, add a NETNODE statement to the LOADNET initialization file and
restart the job.
3200 - 3299
3201W
Active NETQUEUE data set is <data_set_name>
Reason:
A NETQUEUE command was specified, but a NETQUEUE data set is already open. This
will never occur under the product. This message is followed by message 3202E.
System Action:
The NETQUEUE command is ignored.
Action:
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
Reason:
A NETQUEUE command was specified, but a NETQUEUE data set is already open. This
will never occur under the product. This message is preceded by message 3201W.
System Action:
The NETQUEUE command is ignored.
Action:
If more than one NETQUEUE command has been specified in an initialization file, then
delete all but one of them.
3200 - 3299
3203E
Network node <netnode_name> is a network destination, cannot also be local
Reason:
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:
The product action message 3328A is issued to prompt for an END response to ignore
the NETNODE command, a CANCEL response to terminate the product, or to re-enter a
LOADNET initialization command.
Action:
Enter CANCEL to terminate the product or enter a valid NETNODE statement. Enter a
valid NETNODE command in the LOADNET initialization file. If the product was
terminated, then restart it.
3204E
NETAUTH DELETE|LIST|HELP invalid during initialization
Reason:
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:
Action message 3328A is issued to prompt for an END response to ignore the NETAUTH
command, a CANCEL response to terminate the product, or to re-enter a LOADNET
initialization command.
Action:
Respond to the prompt and correct or delete the erroneous NETAUTH command in the
LOADNET initialization file. Then if the product was terminated, restart it.
3200 - 3299
3205C
NETAUTH HELP
Reason:
Response to NETAUTH HELP command.
System Action:
The NETAUTH command options are displayed.
Action:
None.
3206E
HOST operand missing
Reason:
A NETAUTH ADD or NETAUTH DELETE command was specified, but the 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.
Action:
If required, re-issue the NETAUTH ADD or NETAUTH DELETE command specifying the
HOST(<host_or_ip>) operand.
3200 - 3299
3207E
NETDEST ALTER|DELETE|LIST|HELP invalid during initialization
Reason:
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
System Action:
Action message 3328A is issued to prompt for an END response to ignore the NETDEST
initialization command.
Action:
Respond to the prompt and correct or delete the erroneous NETDEST command in the
LOADNET initialization file. Then if the product was terminated, restart it.
3208C
NETDEST HELP
Reason:
Response to NETDEST HELP command.
System Action:
The NETDEST command options are displayed.
Action:
None.
3200 - 3299
3209E
Network node name missing
Reason:
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, action
message 3327A is issued to prompt for an END response to ignore the NETDEST
initialization command. If the NETDEST command was issued as an operator command,
processing continues.
Action:
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 the product 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
Reason:
A NETWORK command was issued with no operands.
System Action:
The NETWORK command is ignored.
Action:
For a list of valid NETWORK command options, enter: NETWORK HELP or NET H or NET ?
3200 - 3299
3211E
NETWORK <option> command invalid
Reason:
A NETWORK command was issued with an invalid option.
System Action:
The NETWORK <option> command is ignored.
Action:
For a list of valid NETWORK command options, enter: NETWORK HELP or NET H or NET ?
3212E
NETWORK <option> not an initialization command
Reason:
A NETWORK command in the LOADNET file specifies an option that is invalid at
initialization.
System Action:
Action message 3328A is issued to prompt for an END response to ignore the NETWORK
<option> command, a CANCEL response to terminate the product, or to re-enter a
LOADNET initialization command.
Action:
Respond to the prompt and delete the erroneous NETWORK <option> command in the
3213E
NETWORK <option> sub-command missing
Reason:
A NETWORK <option> command that was issued requires one or more additional
operands.
System Action:
Action:
For a list of valid NETWORK <option> command options, enter: NETWORK HELP
<option> or NET H <option> or NET ? <option>
3200 - 3299
3214E
NETWORK <option> sub-command <sub_option> invalid
Reason:
A NETWORK <option> command specified an invalid operand <sub_option>.
System Action:
Action:
For a list of valid NETWORK <option> command options, enter: NETWORK HELP
<option> or NET H <option> or NET ? <option>
3215C
NET HELP
Reason:
Response to NETWORK HELP command.
System Action:
The NETDEST command options are displayed.
Action:
None.
3216E
NETWORK HELP command operand <operand> invalid
Reason:
A NETWORK HELP command specified an invalid operand.
System Action:
The NETWORK HELP command is ignored.
Action:
For a list of valid NETWORK HELP command options, enter: NETWORK HELP HELP or NET
H H or NET ? ?
3200 - 3299
3217C
NET DISPLAY LOCAL
Reason:
Response to NETWORK DISPLAY LOCAL command.
System Action:
Network and host attributes of the local network node are displayed.
Action:
None.
3218I
No active network TCP listeners
Reason:
Response to NETWORK DISPLAY LISTENERS command.
System Action:
Action:
None.
3200 - 3299
3219I
TCP listener {<id> }active on {port |<ip>:}<port>
Reason:
An NDS (Network Delivery Services) TCP listener has become active either in response to
a "NETWORK START LISTENER" command or due to a successful restart while in a retry
pending state.
<id> - specifies the unique NDS listener identifier. It is only displayed if more than
one NDS listener is in an active or retry pending state.
<port> - specifies the TCP port number that the NDS listener bound to and is
listening on for incoming connections.
<ip> - specifies the IP address that the NDS listener has bound to and is listening on
for incoming connection. If not displayed, the NDS listener will accept incoming
connections through any IP address on the TCP/IP that NDS is connected to.
System Action:
The NDS TCP listener waits for incoming TCP connect requests from remote master
subsystems.
Action:
None.
3220C
NET DISPLAY LISTENERS
Reason:
Response to NETWORK DISPLAY LISTENERS command.
System Action:
Action:
None.
3200 - 3299
3221W
TCP listener {<id> }already active on {port |<ip>:}<port>
Reason:
Response to NETWORK START LISTENER PORT(<port>){ HOME{(<host>)}} command. An
attempt was made to start a duplicate NDS (Network Delivery Services) listener.
System Action:
If the NETWORK START LISTENER PORT(<port>){ HOME{(<host>)}} command was issued
from the LOADNET initialization file, action message 3328A is issued to prompt for an
END response to ignore the command, a CANCEL response to terminate the master
subsystem, or to re-enter a LOADNET initialization command. If the NETWORK START
LISTENER PORT(<port>){ HOME{(<host>)}} command was issued as an operator
command, processing continues.
<id> - specifies the unique NDS listener identifier. It is only displayed if more than
one NDS listener is in an active or retry pending state.
<port> - specifies the TCP port number that the NDS listener has bound to. <host>
specifies the DNS host name or IP address that the NDS listener has bound to. If not
specified, the NDS listener will accept incoming connections through any IP address
on the TCP/IP that NDS is connected to.
<ip> - specifies the IP address that the NDS listener has bound to. If not displayed,
the NDS listener will accept incoming connections through any IP address on the
TCP/IP that NDS is connected to.
Action:
If the NETWORK START LISTENER PORT(<port>){ HOME{(<host>)}} command was issued
from the LOADNET initialization file, reply END to action message 3328A and delete the
duplicate NETWORK START LISTENER PORT(<port>){ HOME{(<host>)}} command from
3200 - 3299
3222I
TCP listener {<id> }{re}started on {port |<ip>:}CA Portal
Reason:
Response to NETWORK START LISTENER PORT(CA Portal){ HOME{(<host>)}} command to
start an NDS (Network Delivery Services) listener.
<id> - specifies the unique NDS listener identifier. It is only displayed if no other
NDS listener is in an active or retry pending state at the time the command is
issued.
CA Portal - specifies a TCP port number that the NDS listener is to bind to.
<host> - specifies an optional DNS host name or IP address that the NDS listener is
to bind to. If not specified, the NDS listener will accept incoming connections
through any IP address on the TCP/IP that NDS is connected to.
System Action:
If the specified NDS listener is not in an active or retry pending state, it is started. If the
specified NDS listener is in a retry pending state, it is restarted.
Action:
None.
3223I
TCP listener {<id> }on {port |<ip>:}CA Portal stopped
Reason:
Response to NETWORK STOP LISTENER {IDENTIFIER(id)|PORT(CA Portal)} command to
stop an NDS (Network Delivery Services) listener.
<id> - specifies the unique NDS listener identifier, which is displayed in response to
the NETWORK DISPLAY LISTENERS command.
CA Portal - specifies the TCP port number that the NDS listener(s) is/are listening
on. More than one NDS listener can listen on a given TCP port number provided
they are listening on different IP addresses.
System Action:
The requested NDS TCP listener(s) terminate(s).
Action:
None.
3200 - 3299
3224W
TCP listener {<id> }not active{ on port CA Portal}
Reason:
Response to NETWORK STOP LISTENER {IDENTIFIER(<id>)|PORT(CA Portal)} command.
The specified NDS (Network Delivery Services) listener does not exist.
<id> - specifies the unique NDS listener identifier, which is displayed in response to
the NETWORK DISPLAY LISTENERS command.
CA Portal - specifies the TCP port number that the NDS listener(s) is/are listening
on. More than one NDS listener can listen on a given TCP port number provided
they are listening on different IP addresses.
System Action:
The NETWORK STOP LISTENER {IDENTIFIER(id)|PORT(CA Portal)} command is ignored.
Action:
To display the active Network Delivery Services (NDS) listeners, enter one of the
following commands:
NETWORK DISPLAY LISTENERS
NET D L
If only one Network Delivery Services (NDS) listener is active, then it can be stopped
with one of the following commands:
NETWORK STOP LISTENER
NET P L
If more than one Network Delivery Services (NDS) listener is active, then the
IDENTIFIER(<id>) or PORT(CA Portal) operand must be specified to stop a listener with
one of the following commands:
NETWORK STOP LISTENER IDENTIFER(<id>)
NETWORK STOP LISTENER PORT(CA Portal)
NET P L I(<id>)
NET P L P(CA Portal)
3200 - 3299
3225W
TCP listener(s) not active
Reason:
Response to NETWORK STOP LISTENER PORT(<port>) command. No Network Delivery
Services (NDS) TCP listeners are active. <port> specifies a TCP port number.
System Action:
The NETWORK STOP LISTENER PORT(<port>) command is ignored.
Action:
None.
3226W
Identifier or port required, more than one TCP listener active
Reason:
Response to NETWORK STOP LISTENER command. There is more than one active NDS
(Network Delivery Services) TCP listener. Therefore the IDENTIFIER(<id>) or PORT(CA
Portal) operand must be specified to identify which one to stop.
System Action:
The NETWORK STOP LISTENER command is ignored.
Action:
To display the active NDS listeners, enter one of the following:
NETWORK DISPLAY LISTENERS
NET D L
Then if required, enter one of the following commands:
NETWORK STOP LISTENER IDENTIFIER(<id>)
NETWORK STOP LISTENER PORT(CA Portal)
NET P L I(<id>)
NET P L P(CA Portal)
where
<id> - specifies the unique identifier of the NDS listener to be stopped.
CA Portal - specifies the TCP port number of the NDS listener to be stopped.
3200 - 3299
3227I
No pending network connects
Reason:
Response NETWORK DISPLAY PENDING command.
System Action:
Action:
None.
3228C
NET DISPLAY PENDING
Reason:
Response to NETWORK DISPLAY PENDING command.
System Action:
The pending Network Delivery Services (NDS) connections are displayed.
Action:
None.
3200 - 3299
3229E
NETWORK STOP PENDING operand(s) missing
Reason:
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.
Action:
To display the pending Network Delivery Services (NDS) connect(s), enter one of the
following commands:
NETWORK DISPLAY PENDING
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
Reason:
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.
System Action:
Action:
following commands:
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>)
3200 - 3299
3231E
ALL and PORT mutually exclusive
Reason:
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.
System Action:
Action:
following commands:
NET D P
Then if required, re-issue the NETWORK STOP PENDING command with compatible
operands. For a list of valid NETWORK STOP command options, enter one of the
following commands:
NETWORK HELP STOP
NET H P
NET ? P
3232W
No pending network connects
Reason:
Response NETWORK STOP PENDING ALL command. There are no pending Network
Delivery Services (NDS) connects. Therefore none can be stopped.
System Action:
Action:
None.
3200 - 3299
3233W
Pending connect {<id>|to {(<host>)}<ip>} not found
Reason:
Response to NETWORK STOP PENDING IDENTIFIER(<id>)|HOST(<host_or_ip>)
command. The specified NDS (Network Delivery Services) pending connect was not
found.
<id> - specifies a unique connection identifier.
<host_or_ip> - specifies a DNS host name or IP address.
<host> - specifies a DNS host name.
<ip> - specifies an IP address.
System Action:
Action:
To display the pending NDS connect(s), enter one of the following commands:
NET D P
NETWORK STOP PENDING IDENTIFIER(<id>)
NETWORK STOP PENDING HOST(<host_or_ip>)
NET P P I(<id>)
NET P P H(<host_or_ip>)
3234C
NET STOP PENDING
Reason:
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.
Action:
None.
3200 - 3299
3235I
Pending connect <id> to {(<host>)}<ip>:CA Portal stopped
Reason:
Response NETWORK STOP PENDING command. The specified pending network connect
was stopped.
<id> - specifies a unique connect identifier.
CA Portal - specifies a TCP port number.
System Action:
The specified pending NDS (Network Delivery Services) connect is stopped.
Action:
None.
3236I
No active network connections
Reason:
Response NETWORK DISPLAY CONNECTIONS command. There are no active Network
Delivery Services (NDS) connections.
System Action:
Action:
None.
3200 - 3299
3237C
NET DISPLAY CONNECTIONS
Reason:
Response NETWORK DISPLAY CONNECTIONS command.
System Action:
The active Network Delivery Services (NDS) connections are displayed.
Action:
None.
3238C
NET SET CONNECTIONS
Reason:
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.
Action:
None.
3239C
NET START CONNECTION
Reason:
Response NETWORK START CONNECTION command.
System Action:
The specified Network Delivery Services (NDS) connection is started.
Action:
None.
3200 - 3299
3240E
NETWORK STOP CONNECTIONS operand missing
Reason:
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.
System Action:
The NETWORK STOP CONNECTIONS command is ignored.
Action:
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 one of the following commands:
NETWORK HELP STOP
NET H P
NET ? P
To display active network connections, enter one of the following commands:
NETWORK DISPLAY CONNECTIONS
NET D C
3241C
NET STOP CONNECTIONS
Reason:
Response NETWORK STOP CONNECTIONS command.
System Action:
The specified Network Delivery Services (NDS) connection(s) are stopped.
Action:
None
3200 - 3299
3242W
No active network connections
Reason:
Response NETWORK STOP CONNECTIONS ALL command. There are no active Network
Delivery Services (NDS) connections.
System Action:
Action:
None
3243W
{Connection <id>}|{Network node <netnode>} not found
Reason:
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.
Action:
To display the active network TCP connections, enter one of the following commands:
NETWORK DISPLAY CONNECTIONS o
NET D C
NETWORK STOP CONNECTION IDENTIFIER(<id>)
NET P C ID(<id>)
NETWORK STOP CONNECTION NETNODE(<netnode>)
NET P C N(<netnode>)
3200 - 3299
3244W
No active connection(s) for host {(<host>)}<ip>
Reason:
Response NETWORK STOP CONNECTIONS HOST(<host_or_ip>) command. No active
Network Delivery Services (NDS) connection for the specified host exists.
System Action:
The NETWORK STOP CONNECTIONS HOST(<host_or_ip>) command is ignored.
Action:
To display the active network TCP connections, enter one of the following commands:
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
Reason:
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 a line mode interface.
<command> - specifies one of the following Network Delivery Services (NDS)

commands:
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 ignored.
Action:
Issue the Network Delivery Services (NDS) command from a console if authorized to do
so.
3200 - 3299
3246I
No registered network services
Reason:
Response to NETWORK DISPLAY SERVICES command. There are no network (NDS)
services. Never happens under the product.
System Action:
Action:
None.
3247C
Network Services
Reason:
Response to NETWORK DISPLAY SERVICES command.
System Action:
The registered network (NDS) services and their status are displayed.
Action:
None.
3200 - 3299
3248W
Network <service> service already active
Reason:
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
ignore the command, a CANCEL response to terminate the product, or to re-enter a
LOADNET initialization command. If the NETWORK START SERVICE <service> command
was issued as an operator command, processing continues.
Action:
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
Reason:
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:
Action:
None
3200 - 3299
3250E
Network <service> service not found
Reason:
Response to NETWORK START|STOP SERVICE <service> command 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
LOADNET initialization command. If a NETWORK START SERVICE <service> or NETWORK
STOP SERVICE <service> command was issued as an operator command, processing
continues.
Action:
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 the product 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 one of
the following commands:
NETWORK DISPLAY SERVICES
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
Reason:
Response to NETWORK START SERVICE <service> command. <service> specifies a
System Action:
The specified network (NDS) service is started.
Action:
None
3200 - 3299
3252I
Network <service> service stopped
Reason:
Response to NETWORK STOP SERVICE <service> command. <service> specifies a
System Action:
The specified network (NDS) service is stopped.
Action:
None
3253E
Connection rejected, cannot determine identity of {(<host>)}<ip>:<port>
Reason:
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.
Action:
Attempt to restart the Network Delivery Service (NDS) connection with one of the
following commands:
NETWORK START CONNECTION HOST(<host_or_ip>) PORT(<port>)
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.
If the problem persists, contact your software support personnel.
3200 - 3299
3254W
Connect request from|to <ip> rejected, not authorized
Reason:
An outbound or inbound Network Delivery Services (NDS) connection has been
requested. However, the host that the remote is executing on is not authorized to
connect to the local because the local product's network authentication is enabled and
the remote host's IP address has not been authorized to connect to the local product.
<ip> specifies the IP address of the remote host.
System Action:
The Network Delivery Services (NDS) connection is not established.
Action:
If the product on the remote host should be authorized to connect to the local product,
then the following command should be added to the product's LOADNET initialization
file or issued from a console to the local product:
NETAUTH HOST(<host_or_ip>)
where <host_or_ip> specifies the DNS host name or IP address of the host that the
remote product is executing on.
If instances of the product on any host in the network should be authorized to connect
to the local product, then the following command should be added to the local
product's LOADNET initialization file or issued from a console to the local product:
NETWORK SET CONNECTIONS AUTHENTICATE
3255C
Network Connection {Out|In}bound TCP connection established
Reason:
An outbound or inbound Network Delivery Services (NDS) connection has been
established.
System Action:
Action:
None.
3200 - 3299
3256E
Network node <netnode> not defined as a network destination
Reason:
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.
Action:
If the Network Delivery Service (NDS) connection is desired, then ensure that there is a
NETDEST command in the local product's LOADNET initialization file specifying the same
network node name that the remote product's NETNODE command specifies in its
3257W
Network node <netnode> duplicate connection
Reason:
An attempt was made to establish a Network Delivery Services (NDS) connection.
However, a connection between the local network node and the remote network node
already exists.
<netnode> specifies the remote network node name.
System Action:
Action:
None.
3200 - 3299
3258E
Network node <netnode> destination specification mismatch
Reason:
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:
Action:
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
subsystems, NETDEST ADD commands are specified in the LOADNET initialization file.
They can also be issued dynamically as operator commands from a console provided
there is no active Network Delivery Services (NDS) connection to the specified network
node.
3200 - 3299
3259I
Buffer size negotiated down from <higher_value> to <lower_value> by TCP partner
{(<host>)}<ip>:<port>
Reason:
During Network Delivery Services (NDS) connection handshake processing the remote
informed the local 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 product.
<ip> - specifies the IP address the remote product.
<port> - specifies the TCP port number the remote product.
System Action:
The local product adjusts its network buffer size down from <higher_value> to
<lower_value> and Network Delivery Services (NDS) connection establishment
continues.
Action:
None.
3200 - 3299
3260E
Unidentifiable acknowledgement from {(<host>)}<ip>:CA Portal, Message=<token>
Reason:
An acknowledgement to a Network Delivery Services (NDS) message was received from
a remote product. However, the local product's network receiver (for the Network
Delivery Services (NDS) connection to the remote product) 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.
CA Portal - specifies the IP address of the connection partner.
<token> - specifies an internal hexadecimal token to identify the message.
System Action:
The acknowledgement is discarded.
Action:
If the problem is persistent, call your software support personnel.
3200 - 3299
3261C
Negative Ack
<reason>
Partner={(<host>)}<ip>:<port>, NetNode=<netnode>, Service=<service>,
Message=<token>
Reason:
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 acknowledgement may
follow. Network Delivery Services (NDS) recovers from the error and processing
continues.
Action:
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 your
3200 - 3299
3262C
Response Error
Command not found for response
<reason>
Partner={(<host>)<ip>:CA Portal, NetNode=<netnode>, Service=<service>,
Message=<token>
Reason:
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.
(NDS) partner.
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.
Action:
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 your
3200 - 3299
3263C
Connection aborted
Duplicate partner{(<host>)}<ip>:<port> detected
Reason:
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.
(NDS) partner.
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 connection is established, provided no
errors occur.
Action:
None.
3200 - 3299
3264W
TCP receive <interval> second time out: <socket>
Reason:
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.
Action:
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(CA Portal) command,
where
<host_or_ip> - specifies the DNS host name or IP address of the target host.
CA Portal - 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.
3200 - 3299
3265C
Network Connection TCP receive <interval> second time out
Reason:
A TCP receive on a Network Delivery Services (NDS) connection timed out.
<interval> - specifies the receive timer interval in seconds.
System Action:
The connection is terminated.
Action:
NETWORK START CONNECTION HOST(<host_or_ip>) PORT(CA Portal) command, where
(NDS) TCP listener.
3266W
TCP connection purged: <socket>
Reason:
A TCP connection was purged while a Network Delivery Services (NDS) connection was
being established.
System Action:
The Network Delivery Services (NDS) connection is aborted.
Action:
(NDS) TCP listener.
3200 - 3299
3267C
Network Connection TCP connection purged
Reason:
A Network Delivery Services (NDS) TCP connection was purged.
System Action:
The Network Delivery Services (NDS) connection is terminated.
Action:
(NDS) TCP listener.
3268W
TCP connection terminating due to error: <socket>
Reason:
A TCP error occurred while a Network Delivery Services (NDS) connection was being
established.
System Action:
Action:
(NDS) TCP listener.
3200 - 3299
3269C
Network Connection TCP connection terminating due to error
Reason:
A TCP error occurred on a Network Delivery Services (NDS) connection.
System Action:
Action:
(NDS) TCP listener.
3200 - 3299
3270W
TCP connection prematurely terminated by partner: <socket>
Reason:
While a Network Delivery Services (NDS) connection was being established, the remote
partner unexpectedly terminated it.
System Action:
Action:
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 Services (NDS) listener by
issuing the command:
(NDS) TCP listener.
3200 - 3299
3271C
Network Connection TCP connection terminating due to error
Reason:
A Network Delivery Services (NDS) connection was unexpectedly terminated by the
remote partner.
System Action:
Action:
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:
(NDS) TCP listener.
3272W
Duplicate connection closed by partner {(<host>)}<ip>:CA Portal
Reason:
A Network Delivery Services (NDS) connection was started. However, a connection to
the specified remote partner already exists.
(NDS) partner.
partner.
CA Portal - specifies the TCP port number of the remote Network Delivery Services
(NDS) partner.
System Action:
Action:
None.
3200 - 3299
3273C
Network Data Error {<code>, }
<reason>
Connection to {(<host>)}<ip>:CA Portal aborted
Reason:
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.
(NDS) partner.
partner.
CA Portal - specifies the TCP port number of the remote Network Delivery Services
(NDS) partner.
System Action:
The connection is aborted.
Action:
Attempt to determine the cause of the connection failure, and correct it. If the problem
persists, contact your software support personnel.
3200 - 3299
3274W
Network <service> service not active
Reason:
An unsuccessful attempt was made to transmit data to a remote Network Delivery
Services (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
Action:
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
Reason:
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.
Action:
If the problem persists, then attempt to diagnose and correct it. Then attempt to restart
the Network Delivery Services (NDS) connection with the command:
(NDS) TCP listener.
If unable to determine and/or correct the problem, contact your software support
personnel.
3200 - 3299
3276I
{Service=<service>}{, }{NetNode=<netnode>}{, }{Host=<ip>}
Reason:
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.
Action:
See documentation for preceding warning or error message and if necessary, take
appropriate steps to correct the condition.
3200 - 3299
3277C
Network Destination
{Service=<service>}{, }{NetNode=<netnode>}{, }{Host=<host>}{, }
{Sysplex=<sysplex>{, Sysname=<sysname>}{, XcfGroup=<xcfgroup>
{, XcfMember=<xcfmember>}}}{, JesNode=<jesnode>
{, JesMember=<jesmember>}}{, Sysid=sysid}
Reason:
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 system identifier.
System Action:
Depends on the condition described by the preceding warning or error message.
Action:
See documentation for preceding warning or error message and if necessary, take
appropriate steps to correct the condition.
3200 - 3299
3278I
No network authority profiles defined
Reason:
Response to NETAUTH LIST command. No Network Delivery Services (NDS) authority
profiles have been defined with NETAUTH ADD commands.
System Action:
Action:
None.
3279C
NETAUTH LIST
Reason:
Response to NETAUTH or NETAUTH LIST command.
System Action:
The Network Delivery Services (NDS) authority profiles are displayed.
Action:
None.
3200 - 3299
3280E
Network authority profile already defined, Host={(<host>)}<ip>
Reason:
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.
(NDS) destination.
destination.
System Action:
If the NETAUTH ADD HOST(<host_or_ip>) command was issued from the LOADNET
LOADNET initialization command. If NETAUTH ADD HOST(<host_or_ip>) was issued as
an operator command, it is ignored.
Action:
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.
3200 - 3299
3281I
Network authority profile added, Host={(<host>)}<ip>
Reason:
Response to NETAUTH ADD HOST(<host_or_ip>) command.
(NDS) destination.
destination.
System Action:
A qetwork Delivery Services (NDS) authority profile is added for the specified host.
Action:
None.
3200 - 3299
3282E
Network authority profile not found, Host={(<host>)}<ip>
Reason:
Response to NETAUTH DELETE HOST(<host_or_ip>) command.
(NDS) destination.
destination.
System Action:
The NETAUTH DELETE HOST(<host_or_ip>) command is ignored.
Action:
To display the Network Delivery Services (NDS) authority profiles, enter the command:
NETAUTH
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.
3200 - 3299
3283I
Network authority profile deleted, Host={(<host>)}<ip>
Reason:
Response to NETAUTH DELETE HOST((<host_or_ip>) command.
(NDS) destination.
destination.
System Action:
The specified Network Delivery Services (NDS) authority profile is deleted.
Action:
None.
3284C
NETDEST LIST
Reason:
Response to NETDEST or NETDEST LIST command.
System Action:
The Network Delivery Service (NDS) destination profiles are displayed.
Action:
None.
3200 - 3299
3285I
No{ matching} network destinations found
Reason:
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:
Action:
If the NETDEST or NETDEST LIST command was specified 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.
3200 - 3299
3286E
Network node <netnode> is local, cannot also be a network destination
Reason:
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
LOADNET initialization command. If the NETDEST ADD NETNODE(<netnode>) was issued
as an operator command, it is ignored.
Action:
initialization file, reply to action message 3328A and correct or delete the NETDEST ADD
NETNODE(<netnode>) command in the LOADNET initialization file. Then if the product
was terminated, restart it. If the NETDEST ADD NETNODE(<netnode>) command was
issued as an operator command, then to display the network destinations, enter one of
NETDEST
NETDEST LIST
Then if required, re-issue the NETDEST ADD NETNODE(<netnode>) specifying the correct
network node name.
3200 - 3299
3287E
Network node <netnode> already defined
Reason:
Response to NETDEST ADD NETNODE(<netnode>) command. An attempt was made to
create a network (NDS) destination profile that already exists for the specified network
node. <netnode> specifies the network node of the network destination.
System Action:
LOADNET initialization command. If the NETDEST ADD NETNODE(<netnode>) was issued
as an operator command, it is ignored.
Action:
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
Reason:
Response to NETDEST ADD command.
System Action:
A network (NDS) destination profile is created for the specified network node.
Action:
None.
3200 - 3299
3289C
NETDEST ALTER
Reason:
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.
Action:
None.
3290E
DELETE mutually exclusive with destination specification(s)
Reason:
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.
Action:
If required, re-issue the NETDEST DELETE command without any destination
specifications.
3200 - 3299
3291W
Network node <netnode> connected, cannot be deleted
Reason:
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.
Action:
If the network (NDS) destination profile must be deleted, then stop the connection to
the target network node with one of the following commands:
NETWORK STOP CONNECTION NETNODE(<netnode>)
NET P C N(<netnode>)
Then re-issue one of the following commands:
NETDEST DELETE NETNODE(<netnode>)
NETDEST D NET(<netnode>)
3292I
Network node <netnode> deleted
Reason:
Response to NETDEST DELETE NETNODE(<netnode>) command. <netnode> specifies the
target network node name.
System Action:
The target network (NDS) destination profile is deleted.
Action:
None.
3200 - 3299
3293E
Network node <netnode> not found
Reason:
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:
Action:
To display network (NDS) destination profiles, enter one of the following commands:
NETDEST
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
Reason:
A NETDEST ADD or NETDEST ALTER command was issued without any destination
specifications.
System Action:
Action:
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.
3200 - 3299
3295E
<operand1> required when <operand2> specified
Reason:
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.
Action:
If required, re-issue the NETDEST ADD or NETDEST ALTER command with destination
specifications <operand1> and <operand2>.
3296W
No pending listeners or connects
Reason:
Response to NETWORK RESTART command to restart pending NDS (Network Delivery
Services) listener(s) and/or connect(s). However, none were found.
System Action:
Action:
None.
3200 - 3299
3297I
{<x> listener{s}}{ and }{<y> pending connect(s)} restarted
Reason:
Response to NETWORK RESTART command to restart pending NDS (Network Delivery
Services) listener(s) and/or connect(s). <x> specifies the number of pending NDS
listeners restarted. <y> specifies the number of pending NDS connects restarted.
System Action:
Action:
None.
3298C
Network Connection TCP connection stopped by partner
Reason:
A Network Delivery Services (NDS) connection was stopped because a NETWORK STOP
CONNECTION command was issued to the remote partner.
System Action:
Action:
None.
3300 - 3399
3300 - 3399
3300S
ESP/WM network request xxxx invalid
Reason:
Internal logic error. Should never occur.
System Action:
Action:
3301E
ESP/WM network service registration requested more than once
Reason:
System Action:
Action:
3302E
xxxx network service(s) could not be registered
Reason:
An attempt to register one or more 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.
Action:
3300 - 3399
3303E
Network service xxxx not registered
Reason:
An attempt to start a 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.
Action:
Notify CA Support.
3304E
Network service xxxx already active
Reason:
An attempt to start a 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.
Action:
None.
3305W
Network service not supported by ESP/WM master|proxy subsystem
Reason:
The ESPPARM initialization file contains a "NETWORK START SERVICE xxxx" to start
network service xxxx. However, either the subsystem is a master and the network
service is not supported by master subsystems, or the product is a proxy and the
network service is not supported by proxy subsystems.
System Action:
The network service terminates
Action:
Remove the "NETWORK START SERVICE xxxx" from the ESPPARM initialization file.
3300 - 3399
3306E
Network service xxxx not found
Reason:
An attempt to stop a network service was made. However, the network service is not
active.
System Action:
Action:
None.
3307E
NPSA not found (ESP/WM network services not initialized)
Reason:
System Action:
Action:
3300 - 3399
3309W
LOADNET command ignored, only valid for ESP/WM master{ or shadow}
Reason:
A LOADNET command was issued from the ESPPARM initialization file of a proxy
subsystem. However, the LOADNET command may only be issued from the ESPPARM
initialization file of a master subsystem (or a Shadow Manager subsystem if the High
Availability Option (HAO) is installed).
System Action:
The product action message 802A is issued to prompt for an END reply to ignore the
LOADNET command, a CANCEL reply to terminate the product, or an initialization
command reply.
Action:
Reply to action message 802A and remove the erroneous LOADNET command from the
3310I
Network TRACKING receiver started
Reason:
A master's network job tracking receiver has been started by a "NETWORK START
SERVICE TRACKING" command.
System Action:
Action:
None.
3300 - 3399
3311I
Network TRACKING receiver ended
Reason:
A master's network job tracking receiver has ended, normally due to a "NETWORK STOP
SERVICE TRACKING" command.
System Action:
Action:
None.
3312I
Network TRACKING receiver waiting for checkpoint file space
Reason:
A 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.
Action:
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
Reason:
A 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.
System Action:
Action:
None.
3300 - 3399
3314E
ISC input XME size xxxx below minimum yyyy
Reason:
A master's network job tracking receiver has detected a data error from a remote
tracking transmitter. Should never happen.
System Action:
The network connection to the remote is terminated.
Action:
3315E
ISC input XME buffer size <bufsize> {mismatch with XME element size <xmesize>|
inconsistency with extension offset <extoffset>, size <extsize>}
Reason:
A master's network job tracking receiver has detected a data error from a remote
tracking transmitter. Should never happen.
System Action:
The network connection to the remote is terminated.
Action:
3316E
Network routing response xxxx invalid
Reason:
A subsystem request was transmitted to a remote through 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 that sent the erroneous response is stopped.
Action:
Should never happen. Call CA Support.
3300 - 3399
3318E
xxxx byte core request failed for network response IAR and IAE, Request=yyy
Reason:
There is not enough private area virtual storage for the transmission of the response to
a subsystem request that was issued from a remote through 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:
The product sends error response message 3319E to the issuer of the subsystem
request.
Action:
If the problem persists, recycle the product with a larger region size.
3319E
Request RC=xxx, Insufficient core for yyyy byte response
Reason:
A subsystem request was issued to a remote through the network routing service. The
subsystem request was processed but there was not enough virtual storage in the
remote product's address space private area for the response to be transmitted to the
local requesting the product.
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:
Action:
If the problem persists, recycle the remote with a larger region size.
3300 - 3399
3320I
Network ROUTING receiver started
Reason:
A subsystem's network routing receiver has been started by a "NETWORK START
SERVICE ROUTING" command.
System Action:
Action:
None.
3321I
Network ROUTING receiver ended
Reason:
A subsystem's network routing receiver has ended, normally due to a "NETWORK STOP
SERVICE ROUTING" command.
System Action:
Action:
None.
3322E
Network ROUTING receiver input data length xxxx too small for IAR
Reason:
A subsystem's network routing receiver received input of length xxxx from a remote
product.
xxxx - is too small to contain valid subsystem request data.
System Action:
The network ROUTING service is stopped and the network routing receiver terminates.
Action:
Should never happen. Contact CA Support.
3300 - 3399
3323E
Network ROUTING receiver input data xxxx invalid
Reason:
A 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.
Action:
Should never happen. Contact CA Support.
3325E
Invalid command syntax detected{ in line nnnn of xxxx{(yyyy)}
Reason:
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 is a member of
a PDS.
System Action:
Action message 3328A is issued to prompt for an END reply to ignore the LOADNET
command, a CANCEL reply to terminate the product, or a LOADNET command reply.
Action:
Reply to action message 3328A and correct or remove the erroneous command from
the LOADNET PARMLIB initialization file.
3300 - 3399
3326E
Undefined command cccc{ in line nnnn of xxxx{(yyyy)}
Reason:
The LOADNET PARMLIB initialization file contains an undefined command.
cccc - specifies the undefined command name. nnnn specifies the line number of
the undefined command.
a PDS.
System Action:
Action:
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)}
Reason:
A LOADNET PARMLIB initialization file command failed.
cccc - specifies the command name.
nnnn - specifies the line number of the command.
a PDS.
System Action:
Action:
Replay to action message 3328A and correct or remove the command from the
LOADNET PARMLIB initialization file.
3300 - 3399
3328A
Re-enter command, CANCEL or END
Reason:
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:
The product waits for a reply. If END is specified, the product ignores the erroneous
command. If CANCEL is specified, the product terminates. If a command is entered, the
product attempts to execute it.
Action:
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
the product will terminate. The product can then be restarted when the correct action
has been determined. Correct or remove the erroneous command in the LOANET
PARMLIB initialization file.
3348I
NETQUEUE SAVE every {update|<interval> second{s}}
Reason:
Response to one of the following commands
NETWORK QUEUE DISPLAY SAVE
NETWORK QUEUE SET SAVE(<interval>
where <interval> specifies a second value within the range 0-30.
System Action:
Action:
None.
3300 - 3399
3349E
Unable to establish NETQUEUE recovery environment: NETQUEUE data may be lost if
subsystem abends
Reason:
The master attempted unsuccessfully to establish an abend recovery environment that
would have enabled it to save pending NETQUEUE data set updates if an abend were to
occur.
System Action:
Processing continues. However, if the master terminates abnormally, some NETQUEUE
(remote tracking) data may be lost.
Action:
Should never happen. If it does, call CA Support.
3350E
NETQUEUE <dsname> specification ignored, message queuing not supported
Reason:
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 queuing. <dsname> specifies the data set name of the message queue data
set.
System Action:
The NETQUEUE <dsname> command is ignored.
Action:
3300 - 3399
3351S
NETQUEUE data set not specified, message queuing required
Reason:
At least one registered network (NDS) service supports message queuing. Therefore a
NETQUEUE command is required.
System Action:
The system shuts down.
Action:
For a subsystem, add a NETQUEUE <dsname> command to the LOADNET initialization
file to define a Message Delivery Service (NDS) message queue data set and restart the
product. <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
Reason:
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.
Action:
Respond to action message prompt 3354A. For a 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 the product. Then correct the NETQUEUE command and restart the product.
For a 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.
Important! 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 set contents will be
lost.
3300 - 3399
3353W
NETQUEUE data set <dsname> format requested, already formatted
Reason:
A format of the Network Delivery Services (NDS) message queue data set was
requested. However, the message queue data set is already formatted. For a 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.
Action:
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.
3354A
Enter {C to continue, }F to format or P to shutdown
Reason:
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 system waits for a response.
Action:
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.
3300 - 3399
3355S
<dsname> not a valid NETQUEUE data set
Reason:
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.
Action:
For a subsystem, correct the NETQUEUE <dsname> command in the LOADNET
initialization to specify a valid Network Delivery Services (NDS) message queue data set.
Then restart the product.
3356I
NETQUEUE data set <dsname> formatted
Reason:
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.
System Action:
Action:
None.
3300 - 3399
3357E
SPACE|SAVE invalid with destination/service specification(s)
Reason:
A NETWORK QUEUE DISPLAY command was issued specifying the SPACE or SAVE
operands with 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.
Action:
If required, re-enter the NETQUEUE DISPLAY command specifying either the SPACE or
SAVE operand, or destination/service operand(s), but not both.
3358I
NETQUEUE data set not defined|initialized
Reason:
Response to NETWORK QUEUE DISPLAY command.
System Action:
Action:
None. Does not happen under the product.
3300 - 3399
3359E
NETNODE mutually exclusive with destination criteria
Reason:
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.
Action:
If required, re-enter a NETWORK QUEUE DISPLAY command with compatible operands.
3360E
<service> service {not found|does not support message queuing}
Reason:
A NETWORK QUEUE DISPLAY command specified the SERVICE(<service>) operand.
However, network (NDS) service <service> either does not exist or does not support
message queuing.
System Action:
Action:
If required, re-enter a NETWORK QUEUE DISPLAY command specifying a network service
that supports message queuing, or omitting the SERVICE(<service>) operand.
3300 - 3399
3361I
No queued messages{ for {specified destination{ and }}{<service> service}}
Reason:
Response to NETWORK QUEUE DISPLAY command. <service> specifies a network (NDS)
service name.
System Action:
Action:
None.
3362C
NET QUEUE DISPLAY
Reason:
Response to NETWORK QUEUE DISPLAY command.
System Action:
The requested Network Delivery Services (NDS) message queue(s) are displayed.
Action:
None.
3363C
NET QUEUE FLUSH
Reason:
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.
Action:
None.
3300 - 3399
3364E
Network queue identifier <id> not found
Reason:
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:
Action:
To display the existing Network Delivery Services (NDS) message queues, enter one of
NETWORK QUEUE DISPLAY
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.
3300 - 3399
3365W
NETQUEUE space shortage, Dsname=<dsname>
Reason:
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.
Action:
Display Network Delivery Services (NDS) message queue backlogs with one of the
following commands:
NET Q D
If a Network Delivery Services (NDS) message queue backlog exists for an obsolete
network node, then it can be flushed with one of the following commands:
NETWORK QUEUE FLUSH IDENTIFIER(<id>)
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 one of the following commands:
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(CA Portal)
where
<host_or_ip> - specifies the DNS host name or IP address of the network node.
CA Portal - 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 one of the following
commands on both the local and the remote network nodes:
3300 - 3399

NET D S
If the network service is inactive on either network node, then start it with one of the
following commands:
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.
Note: 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 the product) specifies the new data set. Then restart the job.
3300 - 3399
3366I
NETQUEUE data set <dsname> extended by <hex> bytes
Reason:
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.
Action:
None.
3300 - 3399
3367A
Clear NETQUEUE backlog(s) and enter R to retry
Reason:
set to satisfy a request for space on it. This message is preceded by message 3365W
indicating the NETQUEUE space shortage.
System Action:
Prompt user to clear backlog and retry
Action:
Display Network Delivery Services (NDS) message queue backlogs with one of the
following commands:
NET Q D
If a Network Delivery Services (NDS) message queue backlog exists for an obsolete
network node, then it can be flushed with one of the following commands:
NETWORK QUEUE FLUSH IDENTIFIER(<id>)
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 one of the following commands:
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(CA Portal)
where
<host_or_ip> - specifies the DNS host name or IP address of the network node.
CA Portal - 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 one of the following
commands on both the local and the remote network nodes:
3300 - 3399
NET D S
If the network service is inactive on either network node, then start it with one of the
following commands:
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.
Note: 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 the product) specifies the new data set. Then restart the job.
3300 - 3399
3368S
NETQUEUE space shortage, unable to issue clear backlog prompt, terminating
Reason:
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.
Action:
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 your software support personnel. 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 the product, 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 the product.
3369E
Invalid NETQUEUE file action response
Reason:
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.
Action:
Enter a valid response as specified in the action message prompt.
3300 - 3399
3370S
Get|Free network lock requested while NETQUEUE lock held
Reason:
System Action:
The system terminates abnormally with code U2920.
Action:
3371E
Network Delivery Services not available
Reason:
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.
Action:
3300 - 3399
3372W
xNetwork <function>, <description>
Reason:
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.
Action:
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>
Reason:
An internal Network Delivery Services (NDS) API request has resulted in an error
condition.
<description> - describes the error condition.
System Action:
Action:
3300 - 3399
3374S
xNetwork <function>, <error_description>
Reason:
An internal Network Delivery Services (NDS) API request has resulted in a severe error
condition.
<description> - describes the error condition.
System Action:
Action:
3398I
TRACK MODEL xxxx{ REPLACED | ADDED} BY userid
Reason:
The DEFTM command has successfully defined or altered a job tracking model.
System Action:
Log this message in the audit log.
Action:
None.
3399I
TRACK MODEL modelname DELETED BY userid
Reason:
The DELTM command has successfully deleted the job tracking model.
System Action:
Log this message in the audit log.
Action:
None.
3400 - 3499
3400 - 3499
3400E
DB_Mon xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3401E
DB_Mon xxxx in Appl yyyy, missing Data Source Name
Reason:
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:
Action:
Add the missing information to the job in the procedure.
3402E
DB_Mon xxxx in Appl yyyy, missing QUERY Statement
Reason:
Each DB_Mon requires a QUERY Statement to be specified indicating what work is to be
System Action:
Action:
3400 - 3499
3403E
Reason:
System Action:
Action:
3404E
Reason:
System Action:
Action:
3405E
Reason:
System Action:
Action:
3400 - 3499
3406E
Unable to find password matching xxxx, yyyy, zzzz, nnnn, RC=n
Reason:
password entry which matched user xxxx, workload object type yyyy, agent name zzzz
and data source name nnnn.
System Action:
Action:
3407E
QUERY too long
Reason:
The length of the QUERY exceeds the maximum of 4078 characters.
System Action:
Action:
Reduce the length of the QUERY.
3408E
Destination too long, maximum length nn
Reason:
Destination is longer than the maximum nn allowed for the workload object type.
System Action:
Application generation fails.
Action:
Reduce the length of Destination.
3400 - 3499
3409E
Reason:
System Action:
Action:
3410E
Reason:
System Action:
Action:
3411E
tttt xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3400 - 3499
3412E
tttt xxxx in Appl yyyy, missing Server Address
Reason:
Job type tttt requires a Server Address to be specified indicating what work is to be
System Action:
Action:
3413E
tttt xxxx in Appl yyyy, missing Remote File Name
Reason:
Job type tttt requires a Remote File Name to be specified indicating what work is to be
done by the agent. This job does not have one. Note: Job type SFTP_JOB requires a
Remote File Name only if the Local File Name does not contain wildcards.
System Action:
Action:
3414E
Reason:
System Action:
Action:
3400 - 3499
3415E
FTP_JOB xxxx in Appl yyyy, missing Transfer Code Type
Reason:
Each FTP_JOB requires a Transfer Code Type to be specified indicating what work is to
be done by the agent. This job does not have one.
System Action:
Action:
3416E
tttt xxxx in Appl yyyy, missing Transfer Direction
Reason:
Job type tttt requires a Transfer Direction to be specified indicating what work is to be
System Action:
Action:
3417E
FTP_JOB xxxx in Appl yyyy, Transfer Direction DOWNLOAD specified with Type U
Reason:
This combination of parameters is not allowed.
System Action:
Action:
Correct the Transfer Direction in the procedure.
3400 - 3499
3418E
Reason:
System Action:
Action:
3419E
Reason:
System Action:
Action:
3420E
Reason:
System Action:
Action:
3400 - 3499
3421E
Server Address too long, maximum length nn
Reason:
Server Address is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of Server Address.
3422E
Remote File Name too long, maximum length nn
Reason:
Remote File Name is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of Remote File Name.
3423E
Local File Name too long, maximum length nn
Reason:
Local File Name is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of Local File Name.
3400 - 3499
3424E
IP_Mon xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3425E
IP_Mon xxxx in Appl yyyy, missing TCP/IP Device Address
Reason:
Each IP_Mon requires a TCP/IP Device Address to be specified indicating what work is to
System Action:
Action:
3426E
IP_Mon xxxx in Appl yyyy, missing Status
Reason:
Each IP_Mon requires a Status to be specified indicating what work is to be done by the
agent. This job does not have one.
System Action:
Action:
3400 - 3499
3427E
Reason:
System Action:
Action:
3428E
Reason:
System Action:
Action:
3429E
Reason:
System Action:
Action:
3400 - 3499
3430E
TCP/IP Device Address too long, maximum length nn
Reason:
TCP/IP Device Address is longer than the maximum nn allowed for the workload object
type.
System Action:
Action:
Reduce the length of TCP/IP Device Address.
3431E
MISSING required Status
Reason:
There was no Status specified.
System Action:
Action:
3432E
MISSING Mode
Reason:
There was no Mode specified.
System Action:
Action:
3400 - 3499
3433E
Reason:
System Action:
Action:
3434E
EVENTLOG_Mon xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3435E
EVENTLOG_Mon xxxx in Appl yyyy, missing Log Name
Reason:
Each EVENTLOG_Mon requires a Log Name to be specified indicating what work is to be
System Action:
Action:
3400 - 3499
3436E
Reason:
System Action:
Action:
3437E
Reason:
System Action:
Action:
3438E
Reason:
System Action:
Action:
3400 - 3499
3439E
EventCategory too long
Reason:
The length of the EventCategory exceeds the maximum of 4078 characters.
System Action:
Action:
Reduce the length of the EventCategory.
3440E
EventDescription too long
Reason:
The length of the EventDescription exceeds the maximum of 4078 characters.
System Action:
Action:
Reduce the length of the EventDescription.
3441E
LogName too long, maximum length nn
Reason:
LogName is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of LogName.
3400 - 3499
3442E
EventSource too long, maximum length nn
Reason:
EventSource is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of EventSource.
3443E
EventComputer too long, maximum length nn
Reason:
EventComputer is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of EventComputer.
3444E
MISSING Event ID
Reason:
There was no Event ID specified.
System Action:
Action:
3400 - 3499
3445E
Reason:
System Action:
Action:
3446E
PROCESS_Mon xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3447E
PROCESS_Mon xxxx in Appl yyyy, missing Process Name
Reason:
Each PROCESS_Mon requires a Process Name to be specified indicating what work is to
System Action:
Action:
3400 - 3499
3448E
PROCESS_Mon xxxx in Appl yyyy, missing Status
Reason:
Each PROCESS_Mon requires a Status to be specified indicating what work is to be done
by the agent. This job does not have one.
System Action:
Action:
3449E
Reason:
System Action:
Action:
3450E
Reason:
System Action:
Action:
3400 - 3499
3451E
Reason:
System Action:
Action:
3452E
Process Name too long, maximum length nn
Reason:
Process Name is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of Process Name.
3453E
Reason:
System Action:
Action:
3400 - 3499
3454E
MISSING Mode
Reason:
System Action:
Action:
3455E
Reason:
System Action:
Action:
3456E
SERVICE_Mon xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3400 - 3499
3457E
SERVICE_Mon xxxx in Appl yyyy, missing Service Name
Reason:
Each SERVICE_Mon requires a Service Name to be specified indicating what work is to
System Action:
Action:
3458E
SERVICE_Mon xxxx in Appl yyyy, missing Status
Reason:
Each SERVICE_Mon requires a Status to be specified indicating what work is to be done
System Action:
Action:
3459E
Reason:
System Action:
Action:
3400 - 3499
3460E
Reason:
System Action:
Action:
3461E
Reason:
System Action:
Action:
3462E
Service Name too long, maximum length nn
Reason:
Service Name is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of Service Name.
3400 - 3499
3463E
Reason:
System Action:
Action:
3464E
MISSING Mode
Reason:
System Action:
Action:
3465E
Reason:
System Action:
Action:
3400 - 3499
3466E
TEXT_Mon xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3467E
TEXT_Mon xxxx in Appl yyyy, missing Text File
Reason:
Each TEXT_Mon requires a Text File to be specified indicating what work is to be done
System Action:
Action:
3468E
TEXT_Mon xxxx in Appl yyyy, missing Text String
Reason:
Each TEXT_Mon requires a Text String to be specified indicating what work is to be done
System Action:
Action:
3400 - 3499
3469E
TEXT_Mon xxxx in Appl yyyy, missing search boundary type
Reason:
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:
Action:
3470E
Reason:
System Action:
Action:
3471E
Reason:
System Action:
Action:
3400 - 3499
3472E
Reason:
System Action:
Action:
3473E
Text String too long
Reason:
The length of the Text String exceeds the maximum of 1022 characters.
System Action:
Action:
Reduce the length of the Text string.
3474E
Textfile too long, maximum length nn
Reason:
Textfile is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of Textfile.
3400 - 3499
3475E
TimeFormat too long, maximum length nn
Reason:
TimeFormat is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of TimeFormat.
3476E
Reason:
System Action:
Action:
3477E
FROM too long, maximum length nn
Reason:
FROM is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of FROM.
3400 - 3499
3478E
TO too long, maximum length nn
Reason:
TO is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of TO.
3479E
Reason:
System Action:
Action:
3480E
CPU_Mon xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3400 - 3499
3481E
CPU_Mon xxxx in Appl yyyy, both FROM and TO parameters are missing
Reason:
Both FROM and TO parameters are missing in CONTINUOUS or WAITMODE WAIT mode.
System Action:
Action:
Provide FROM and/or TO parameter. Then resubmit the job.
3482E
CPU_Mon xxxx in Appl yyyy, parameter FROM higher than parameter TO
Reason:
Parameter FROM is higher than parameter TO.
System Action:
Action:
Correct FROM and/or TO parameters. Then resubmit the job.
3483E
Reason:
System Action:
Action:
3400 - 3499
3484E
Reason:
System Action:
Action:
3485E
Reason:
System Action:
Action:
3400 - 3499
3486E
Reason:
System Action:
Action:
3487E
DISK_Mon xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3488E
DISK_Mon xxxx in Appl yyyy, missing Drive name
Reason:
There was no Drive name to identify a logical partition to monitor.
System Action:
Action:
Provide the Drive name. Then resubmit the job.
3400 - 3499
3489E
DISK_Mon xxxx in Appl yyyy, both FROM and TO parameters are missing
Reason:
Both FROM and TO parameters are missing in CONTINUOUS or WAITMODE WAIT mode.
System Action:
Action:
3490E
DISK_Mon xxxx in Appl yyyy, parameter FROM higher than parameter TO
Reason:
System Action:
Action:
3491E
DISK_Mon xxxx in Appl yyyy, invalid parameter FROM
Reason:
Parameter FROM higher than 100 and Format type is PERCENT.
System Action:
Action:
Correct parameter FROM. Then resubmit the job.
3400 - 3499
3492E
DISK_Mon xxxx in Appl yyyy, invalid parameter TO
Reason:
Parameter TO higher than 100 and Format type is PERCENT.
System Action:
Action:
Correct parameter TO. Then resubmit the job.
3493E
DISK_Mon xxxx in Appl yyyy, invalid parameter NoChange
Reason:
Parameter NoChange higher than 100 and Format type is PERCENT.
System Action:
Action:
Correct parameter NoChange. Then resubmit the job.
3494E
Reason:
System Action:
Action:
3400 - 3499
3495E
Reason:
System Action:
Action:
3496E
Reason:
System Action:
Action:
3497E
Drive too long, maximum length nn
Reason:
Drive name is longer than the maximum nn.
System Action:
Action:
Reduce the length of Drive.
3500 - 3599
3498E
Invalid Operator
Reason:
EventID Operator code is not EQ, LT, LE, GT or GE
System Action:
Action:
Correct the Operator in EventID statement.
3499E
TEXT_Mon xxxx in Appl yyyy, both FROM and TO parameters are missing
Reason:
Both FROM and TO parameters are missing.
System Action:
Action:
3500 - 3599
3500E
TEXT_Mon xxxx in Appl yyyy, missing Time Format
Reason:
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:
Action:
3500 - 3599
3501E
TEXT_Mon xxxx in Appl yyyy, non-numeric FROM parameter
Reason:
Each TEXT_Mon requires FROM parameter to be numeric if the search boundary type is
LINE.
System Action:
Action:
Correct the FROM parameter.
3502E
TEXT_Mon xxxx in Appl yyyy, non-numeric TO parameter
Reason:
Each TEXT_Mon requires TO parameter to be numeric if the search boundary type is
LINE.
System Action:
Action:
Correct the TO parameter.
3503E
TEXT_Mon xxxx in Appl yyyy, parameter FROM higher than parameter TO
Reason:
System Action:
Action:
3500 - 3599
3504E
No CKPT space to trigger event xxxx.yyyy specified by AMNOTIFY stmt for object
xxxxx.
Reason:
Agent Monitor WOB was unable to obtain enough checkpoint space to trigger an event
specified in AMNOTIFY statement.
System Action:
The trigger is not processed.
Action:
3505E
Alert ID and Event ID are mutually exclusive.
Reason:
AMNOTIFY statement for an Agent Monitor WOB specified both an ALERT and EVENT
parameters.
System Action:
Processing of the procedure stops.
Action:
Correct the statement to use either an ALERT or EVENT parameter.
3506E
Both Alert ID and Event ID defined for Agent Monitor object xxxx.
Reason:
The product 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 proc.
System Action:
Action:
Correct your proc to use either an ALERT or EVENT parameter per single Agent Monitor
WOB.
3500 - 3599
3507I
xxxx STATE yyyyyyyy.
Reason:
Agent Monitor object xxxx has changed the state to yyyyyyyy.
System Action:
Action:
None.
3508E
Reason:
zzzz.
System Action:
Processing ends for this request.
Action:
3500 - 3599
3509E
User uuuuuuuu, Unauthorized access to event xxxx.yyyy in AMNOTIFY stmt for object
xxxxx.
Reason:
Authority access check to the event specified by AMNOTIFY statement failed. This check
is made when the application containing an Agent Monitor WOB is being generated, and
also, when the WOB is trying to trigger the event. 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:
If this error occurs during generating of an application, then the generation stops. If it
occurs during the triggering of the event, then the trigger is not processed.
Action:
3510E
EJB_Job xxxx in Appl yyyy, CreateMethod Name does not start with "create"
Reason:
CreateMethod Name should start with "create"
System Action:
Action:
Correct the Create Method name. Then resubmit the job.
3500 - 3599
3511E
CREATEMETHOD too long
Reason:
The length of the CREATEMETHOD exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the CREATEMETHOD.
3512E
Missing CreateParameter Type
Reason:
Each CREATEPARAMETER requires a Type to be specified indicating what work is to be
System Action:
Action:
3513E
CreateParameter Type too long
Reason:
The length of the CreateParameter Type exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the CreateParameter Type.
3500 - 3599
3514E
CreateParameter Value too long
Reason:
The length of the CreateParameter Value exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the CreateParameter Value.
3515E
No space in ATR to store data for object jjjj/aaaa
Reason:
There was insufficient space in the ATR to store data for a WEB_Serv jjjj in application
aaaa.
System Action:
Action:
3516E
WEB_Serv xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3500 - 3599
3517E
WEB_Serv xxxx in Appl yyyy, missing TargetNamespace Statement
Reason:
There was no TargetNamespace provided.
System Action:
Action:
Provide the TargetNamespace. Then resubmit the job.
3518E
WEB_Serv xxxx in Appl yyyy, missing OPERATION Statement
Reason:
There was no OPERATION name provided.
System Action:
Action:
Provide the OPERATION name. Then resubmit the job.
3519E
Reason:
System Action:
Action:
3500 - 3599
3520E
Reason:
System Action:
Action:
3521E
Reason:
System Action:
Action:
3500 - 3599
3522E
Reason:
System Action:
Action:
3523E
OPERATION too long
Reason:
The length of the OPERATION exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the OPERATION statement.
3524E
WSDL_URL too long
Reason:
The length of the WSDL_URL exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the WSDL_URL.
3500 - 3599
3525E
Endpoint_URL too long
Reason:
The length of the Endpoint_URL exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Endpoint_URL.
3526E
Reason:
System Action:
Action:
Reduce the length of the Destination.
3527E
TargetNamespace too long, maximum length nn
Reason:
TargetNamespace is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the TargetNamespace.
3500 - 3599
3528E
ServiceName too long, maximum length nn
Reason:
ServiceName is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the ServiceName.
3529E
PortName too long, maximum length nn
Reason:
PortName is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the PortName.
3530E
ReturnNamespace too long, maximum length nn
Reason:
ReturnNamespace is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the ReturnNamespace.
3500 - 3599
3531E
ReturnClass too long, maximum length nn
Reason:
ReturnClass is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the ReturnClass.
3532E
ReturnXML too long, maximum length nn
Reason:
ReturnXML is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the ReturnXML.
3533E
Filter too long
Reason:
The length of the Filter exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Filter.
3500 - 3599
3534E
Missing Parameter Type
Reason:
Each PARAMETER requires a Type to be specified indicating what work is to be done by
the agent. This job does not have one.
System Action:
Action:
3535E
Parameter Type too long
Reason:
The length of the Parameter Type exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Parameter Type.
3536E
Parameter Value too long
Reason:
The length of the Parameter Value exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Parameter Value.
3500 - 3599
3537E
Reason:
There was insufficient space in the ATR to store data for an EJBE_Job jjjj in application
aaaa.
System Action:
Action:
3538E
EJBE_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3539E
EJBE_JOB xxxx in Appl yyyy, missing BEAN Statement
Reason:
Each EJBE_JOB requires a BEAN to be specified indicating what work is to be done by
System Action:
Action:
3500 - 3599
3540E
EJBE_JOB xxxx in Appl yyyy, missing OPERATIONTYPE Statement
Reason:
Each EJBE_JOB requires an OPERATIONTYPE to be specified indicating what work is to be
System Action:
Action:
3541E
EJBE_JOB xxxx in Appl yyyy, missing METHOD Statement
Reason:
Each EJBE_JOB requires a METHOD to be specified indicating what work is to be done by
System Action:
Action:
3542E
EJBE_JOB xxxx in Appl yyyy, missing FINDERMETHOD Statement
Reason:
Each EJBE_JOB requires a FINDERMETHOD to be specified indicating what work is to be
System Action:
Action:
3500 - 3599
3543E
EJBE_JOB xxxx in Appl yyyy, missing Initial_Context Statement
Reason:
Each EJBE_JOB requires an Initial_Context to be specified indicating what work is to be
System Action:
Action:
3544E
EJBE_JOB xxxx in Appl yyyy, missing Location Statement
Reason:
Each EJBE_JOB requires a Location to be specified indicating what work is to be done by
System Action:
Action:
3545E
EJBE_Job xxxx in Appl yyyy, CreateMethod Name does not start with "create"
Reason:
CreateMethod Name should start with "create"
System Action:
Action:
Correct the Create Method name. Then resubmit the job.
3500 - 3599
3546E
EJBE_Job xxxx in Appl yyyy, CREATEPARAMETER defined for OPERATIONTYPE UPDATE
or REMOVE
Reason:
CreateParameter is only valid for Operation Type CREATE
System Action:
Action:
Correct the error. Then resubmit the job.
3547E
EJBE_Job xxxx in Appl yyyy, MODIFYPARAMETER defined for OPERATIONTYPE CREATE
or REMOVE
Reason:
ModifyParameter is only valid for Operation Type UPDATE
System Action:
Action:
3548E
EJBE_Job xxxx in Appl yyyy, FINDERPARAMETER defined for OPERATIONTYPE CREATE
Reason:
FinderParameter is only valid for Operation Types UPDATE and REMOVE
System Action:
Action:
3500 - 3599
3549E
Reason:
System Action:
Action:
3550E
Reason:
System Action:
Action:
3551E
Reason:
System Action:
Action:
3500 - 3599
3552E
Reason:
System Action:
Action:
3553E
BEAN Name too long
Reason:
The length of the BEAN Name exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the BEAN Name.
3554E
METHOD Name too long
Reason:
The length of the METHOD Name exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the METHOD Name.
3500 - 3599
3555E
CREATEMETHOD too long
Reason:
The length of the CREATEMETHOD exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the CREATEMETHOD.
3556E
FINDERMETHOD too long
Reason:
The length of the FINDERMETHOD exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the FINDERMETHOD.
3557E
Initial Context too long
Reason:
The length of the Initial Context exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Initial Context.
3500 - 3599
3558E
Location too long
Reason:
The length of the Location exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Location.
3559E
Missing CreateParameter Type
Reason:
Each CREATEPARAMETER requires a Type to be specified indicating what work is to be
System Action:
Action:
3560E
CreateParameter Type too long
Reason:
The length of the CreateParameter Type exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the CreateParameter Type.
3500 - 3599
3561E
CreateParameter Value too long
Reason:
The length of the CreateParameter Value exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the CreateParameter Value.
3562E
Missing ModifyParameter Type
Reason:
Each MODIFYPARAMETER requires a Type to be specified indicating what work is to be
System Action:
Action:
3563E
ModifyParameter Type too long
Reason:
The length of the ModifyParameter Type exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the ModifyParameter Type.
3500 - 3599
3564E
ModifyParameter Value too long
Reason:
The length of the ModifyParameter Value exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the ModifyParameter Value.
3565E
Missing FinderParameter Type
Reason:
Each FINDERPARAMETER requires a Type to be specified indicating what work is to be
System Action:
Action:
3566E
FinderParameter Type too long
Reason:
The length of the FinderParameter Type exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the FinderParameter Type.
3500 - 3599
3567E
FinderParameter Value too long
Reason:
The length of the FinderParameter Value exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the FinderParameter Value.
3568E
Reason:
There was insufficient space in the ATR to store data for a HTTP_Job jjjj in application
aaaa.
System Action:
Action:
3569E
HTTP_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3500 - 3599
3570E
HTTP_Job xxxx in Appl yyyy, missing INVOCATIONTYPE Statement
Reason:
Each HTTP_Job requires an INVOCATIONTYPE to be specified indicating what work is to
System Action:
Action:
3571E
Reason:
A Connection User ID was specified which required a password. The product was unable
to find a password entry which matched user xxxx, workload object type yyyy, agent
name zzzz and connection user domain name nnnn.
System Action:
Action:
3572E
HTTP_Job xxxx in Appl yyyy, missing SERVLET_URL Statement
Reason:
Each HTTP_Job requires a SERVLET_URL to be specified indicating what work is to be
System Action:
Action:
3500 - 3599
3573E
Reason:
System Action:
Action:
3574E
Reason:
System Action:
Action:
3575E
Reason:
System Action:
Action:
3500 - 3599
3576E
LocalUser ID too long, maximum length nn
Reason:
A user ID specified on the LOCALUSER statement was longer than the maximum allowed
for the workload object type.
System Action:
Action:
Replace the user ID with a valid ID.
3577E
ACTION too long
Reason:
The length of the ACTION exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the ACTION statement.
3578E
Servlet_URL too long
Reason:
The length of the Servlet_URL exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Servlet_URL.
3500 - 3599
3579E
Filter too long
Reason:
System Action:
Action:
3580E
Missing Parameter Keyword
Reason:
Each PARAMETER requires a Keyword to be specified indicating what work is to be done
System Action:
Action:
3581E
Parameter Keyword too long
Reason:
The length of the Parameter Keyword exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Parameter Keyword.
3500 - 3599
3582E
Reason:
System Action:
Action:
3583E
Reason:
There was insufficient space in the ATR to store data for a POJO_Job jjjj in application
aaaa.
System Action:
Action:
3584E
POJO_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3500 - 3599
3585E
POJO_Job xxxx in Appl yyyy, missing ClassName Statement
Reason:
There was no ClassName provided.
System Action:
Action:
Provide the ClassName. Then resubmit the job.
3586E
POJO_Job xxxx in Appl yyyy, missing METHOD Statement
Reason:
Each POJO_Job requires a METHOD to be specified indicating what work is to be done
System Action:
Action:
3587E
Reason:
System Action:
Action:
3500 - 3599
3588E
Reason:
System Action:
Action:
3589E
Reason:
System Action:
Action:
3500 - 3599
3590E
Reason:
System Action:
Action:
3591E
Reason:
System Action:
Action:
3592E
Reason:
System Action:
Action:
3500 - 3599
3593E
Reason:
System Action:
Action:
3594E
Reason:
System Action:
Action:
3595E
Reason:
System Action:
Action:
3500 - 3599
3596E
ClassName too long
Reason:
The length of the ClassName exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the ClassName.
3597E
Reason:
There was insufficient space in the ATR to store data for a POJO_Job jjjj in application
aaaa.
System Action:
Action:
3598E
RMI_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3600 - 3699
3599E
RMI_Job xxxx in Appl yyyy, missing RemoteClassName Statement
Reason:
There was no RemoteClassName provided.
System Action:
Action:
Provide the RemoteClassName. Then resubmit the job.
3600 - 3699
3600E
RMI_Job xxxx in Appl yyyy, missing METHOD Statement
Reason:
Each RMI_Job requires a METHOD to be specified indicating what work is to be done by
System Action:
Action:
3601E
Reason:
System Action:
Action:
3600 - 3699
3602E
Reason:
System Action:
Action:
3603E
Reason:
System Action:
Action:
3604E
tttt xxxx in Appl yyyy, Transfer Direction UPLOAD specified with LOCALUSER
Reason:
LOCALUSER can only be specified with Transfer Direction DOWNLOAD.
System Action:
Action:
Correct the error.
3600 - 3699
3605E
Reason:
System Action:
Action:
3606E
Reason:
System Action:
Action:
3607E
Reason:
System Action:
Action:
Add the missing information to the job in the
3600 - 3699
3608E
Reason:
System Action:
Action:
3609E
Reason:
System Action:
Action:
3610E
RemoteClassName too long
Reason:
The length of the RemoteClasName exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the RemoteClassName.
3600 - 3699
3611E
Reason:
There was insufficient space in the ATR to store data for a JMXA_Job jjjj in application
aaaa.
System Action:
Action:
3612E
JMXA_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3613E
JMXA_Job xxxx in Appl yyyy, missing MBean Statement
Reason:
There was no MBean provided.
System Action:
Action:
Provide the MBean. Then resubmit the job.
3600 - 3699
3614E
JMXA_Job xxxx in Appl yyyy, missing Attribute Statement
Reason:
There was no Attribute provided.
System Action:
Action:
Provide the Attribute. Then resubmit the job.
3615E
JMXA_Job xxxx in Appl yyyy, missing URL Statement
Reason:
There was no URL provided.
System Action:
Action:
Provide the URL. Then resubmit the job.
3616E
Reason:
System Action:
Action:
3600 - 3699
3617E
Reason:
System Action:
Action:
3618E
Reason:
System Action:
Action:
3600 - 3699
3619E
Reason:
zzzz.
System Action:
Action:
3621E
MBean too long
Reason:
The length of the MBean exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the MBean.
3622E
Attribute too long
Reason:
The length of the Attribute exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Attribute.
3600 - 3699
3623E
URL too long
Reason:
The length of the URL exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the URL.
3624E
Filter too long
Reason:
System Action:
Action:
3625E
Reason:
System Action:
Action:
3600 - 3699
3626E
Reason:
System Action:
Action:
3627E
Reason:
System Action:
Action:
3628E
Reason:
There was insufficient space in the ATR to store data for a JMXS_Job jjjj in application
aaaa.
System Action:
Action:
3600 - 3699
3629E
JMXS_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3630E
JMXS_Job xxxx in Appl yyyy, missing MBean Statement
Reason:
System Action:
Action:
3631E
JMXS_Job xxxx in Appl yyyy, missing URL Statement
Reason:
System Action:
Action:
3600 - 3699
3632E
Reason:
System Action:
Action:
3633E
Reason:
System Action:
Action:
3634E
Reason:
System Action:
Action:
3600 - 3699
3635E
Reason:
System Action:
Action:
3637E
MBean too long
Reason:
System Action:
Action:
3638E
URL too long
Reason:
System Action:
Action:
3600 - 3699
3639E
AttributesFilter too long
Reason:
The length of the AttributesFilter exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the AttributesFilter.
3640E
TypesFilter too long
Reason:
The length of the TypesFilter exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the TypesFilter.
3641E
Reason:
There was insufficient space in the ATR to store data for a JMXO_Job jjjj in application
aaaa.
System Action:
Action:
3600 - 3699
3642E
JMXO_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3643E
JMXO_Job xxxx in Appl yyyy, missing MBean Statement
Reason:
System Action:
Action:
3644E
JMXO_Job xxxx in Appl yyyy, missing Operation Statement
Reason:
There was no Operation provided.
System Action:
Action:
Provide the Operation. Then resubmit the job.
3600 - 3699
3645E
JMXO_Job xxxx in Appl yyyy, missing URL Statement
Reason:
System Action:
Action:
3646E
tttt xxxx in Appl yyyy, Wildcards are not allowed in Local File Name
Reason:
Job type tttt cannot have wildcard characters in a Local File name.
System Action:
Action:
Correct the problem in the job in the procedure.
3647E
Reason:
System Action:
Action:
3600 - 3699
3648E
Reason:
System Action:
Action:
3649E
Reason:
System Action:
Action:
3600 - 3699
3650E
Reason:
System Action:
Action:
3652E
MBean too long
Reason:
System Action:
Action:
3653E
Operation too long
Reason:
The length of the Operation exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Operation.
3600 - 3699
3654E
URL too long
Reason:
System Action:
Action:
3655E
Filter too long
Reason:
System Action:
Action:
3656E
Reason:
System Action:
Action:
3600 - 3699
3657E
Reason:
System Action:
Action:
3658E
Reason:
System Action:
Action:
3659E
Missing Parameter Value, Array or URI
Reason:
Each PARAMETER requires a Value or an Array or a URI to be specified indicating what
work is to be done by the agent. This job does not have one.
System Action:
Action:
3600 - 3699
3660E
Reason:
System Action:
Action:
3661E
Reason:
System Action:
Action:
3662E
Missing CreateParameter Value, Array or URI
Reason:
Each CREATEPARAMETER requires a Value or an Array or a URI to be specified indicating
what work is to be done by the agent. This job does not have one.
System Action:
Action:
3600 - 3699
3663E
Missing ModifyParameter Value, Array or URI
Reason:
Each MODIFYPARAMETER requires a Value or an Array or a URI to be specified
indicating what work is to be done by the agent. This job does not have one.
System Action:
Action:
3664E
Missing FinderParameter Value, Array or URI
Reason:
Each FINDERPARAMETER requires a Value or an Array or a URI to be specified indicating
System Action:
Action:
3665E
Missing Parameter Value
Reason:
Each PARAMETER requires a Value to be specified indicating what work is to be done by
System Action:
Action:
3600 - 3699
3666E
Reason:
System Action:
Action:
3667E
Reason:
System Action:
Action:
3668E
Reason:
System Action:
Action:
3600 - 3699
3669E
JMXS_Job xxxx in Appl yyyy, Only one of AttributesFilter and TypesFilter can be
provided
Reason:
Both mutually exclusive AttributesFilter and TypesFilter statements are included in
Application yyyy
System Action:
Action:
Remove either AttributesFilter or TypesFilter URL. Then resubmit the job.
3670E
Reason:
There was insufficient space in the ATR to store data for a JMXN_Job jjjj in application
aaaa.
System Action:
Action:
3671E
JMXN_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3600 - 3699
3672E
JMXN_Job xxxx in Appl yyyy, missing MBean Statement
Reason:
System Action:
Action:
3673E
JMXN_Job xxxx in Appl yyyy, missing URL Statement
Reason:
System Action:
Action:
3674E
JMXN_Job xxxx in Appl yyyy, missing ClassName Statement
Reason:
There was no ClassName provided.
System Action:
Action:
Provide the ClassName. Then resubmit the job.
3600 - 3699
3675E
tttt xxxx in Appl yyyy, missing REMOTEDIR statement
Reason:
Job type tttt requires a Remote Directory to be specified indicating what work is to be
System Action:
Action:
3676E
Reason:
System Action:
Action:
3677E
Reason:
System Action:
Action:
3600 - 3699
3678E
Reason:
System Action:
Action:
3679E
Reason:
zzzz.
System Action:
Action:
3681E
MBean too long
Reason:
System Action:
Action:
3600 - 3699
3682E
URL too long
Reason:
System Action:
Action:
3683E
Reason:
System Action:
Action:
3684E
Reason:
System Action:
Action:
3600 - 3699
3685E
Reason:
System Action:
Action:
3686E
Reason:
System Action:
Action:
3687E
ClassName too long
Reason:
The length of the ClassName exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the ClassName.
3600 - 3699
3688E
Reason:
System Action:
Action:
3689E
Reason:
A Proxy User ID was specified which required a password. The product was unable to
find a password entry which matched user xxxx, workload object type yyyy, agent name
zzzz and proxy user domain name nnnn.
System Action:
Action:
3690E
ConnectionUser too long, maximum length nn
Reason:
ConnectionUser is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the ConnectionUser.
3600 - 3699
3691E
ConnectionUser Domain too long, maximum length nn
Reason:
ConnectionUser Domain is longer than the maximum nn allowed for the workload
object type.
System Action:
Action:
Reduce the length of the ConnectionUser Domain.
3692E
ProxyUser too long, maximum length nn
Reason:
ProxyUser is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the ProxyUser.
3693E
ProxyUser Domain too long, maximum length nn
Reason:
ProxyUser Domain is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the ProxyUser Domain.
3600 - 3699
3694E
ConnectionOrigin too long
Reason:
The length of the ConnectionOrigin exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the ConnectionOrigin.
3695E
ConnectionDomain too long
Reason:
The length of the ConnectionDomain exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the ConnectionDomain.
3696E
ProxyOrigin too long
Reason:
The length of the ProxyOrigin exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the ProxyOrigin.
3600 - 3699
3697E
ProxyDomain too long
Reason:
The length of the ProxyDomain exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the ProxyDomain.
3698E
ProxyHost too long
Reason:
The length of the ProxyHost exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the ProxyHost.
3700 - 3799
3699E
{ConsName=<consname>|ConsId=<consid>}{ invalid|, ConvCon RetCode=<retcode>}
Reason:
Console name <consname> or console id <consid> was specified in a SEND command. If
a SEND event or procedure command was being processed, then the SEND command
specified the CN(<consname>) or the CN(<consid>) keyword operand. Validation of the
specified console using the CONVCON system service failed. If CONVCON returned a
code <retcode> exceeding 8, then <retcode> is displayed in the message text.
System Action:
The system command is not issued. If the error occurred in an event or procedure SEND
command, then the event does not execute.
Action:
Correct the console specification to identify a valid console. If the error occurred in an
event or procedure SEND command, re-trigger the event after the console specification
has been corrected.
3700 - 3799
3700I
ENTERING ASSEMBLER MODULE ESPAHLDW.S (date time)
Reason:
The web service is starting.
System Action:
Info only
Action:
None
3700 - 3799
3701I
SSID PARM PASSED:
Reason:
Displays passed parameter
System Action:
Info only
Action:
None
3702I
WORK NAME PASSED:
Reason:
System Action:
Info only
Action:
None
3703I
ESP COMMAND PASSED:
Reason:
Displays generated command
System Action:
Command is passed to the product
Action:
None
3700 - 3799
3704I
RETURNED FROM ESP
RETURN CODE=X'00000000', REASON CODE=X'00000000'
Reason:
The product returned successfully
System Action:
The product Error codes are displayed
Action:
If a non zero code is noted, check the log for further messages
3705E
ERROR OCCURRED DURING REQUEST PROCESSING
Reason:
The product returned an error
System Action:
Processing continues
Action:
Check the log for further messages
3706E
REQUEST HANDLER (CYBES170) CANNOT BE LOADED
Reason:
The product interface could not be activated
System Action:
Action:
Make sure that the path statements are correct.
3700 - 3799
3707E
PARM SUBSYSID IS INVALID
Reason:
The subsystem id must be 1 to 4 national characters
System Action:
Action:
Correct the subsystem id
3708E
PARM SUBSYSID IS MISSING IN PLIST
Reason:
The parameter is missing
System Action:
Action:
Add the parameter to the request.
3709E
PARM SUBSYSID HAS BAD FOOTPRINT
Reason:
System Action:
Action:
Contact support
3700 - 3799
3712N
SSID IS NOT ACTIVE, REQUEST ENDED
Reason:
The selected system is not active.
System Action:
Action:
Arrange for the selected system to be activated
3713N
SSID CHECK (ESPCHKSS) CANNOT BE LOADED
Reason:
Web Services cannot check if the product is active
System Action:
The request proceeds but may fail is the product is not active
Action:
Make sure that the path statements are correct.
3715E
parm holdparms has bad footprint
Reason:
System Action:
Action:
Contact support
3700 - 3799
3716E
parm holdparms is missing in plist
Reason:
System Action:
Action:
3717E
parm worktoken has bad footprint
Reason:
System Action:
Action:
Contact support
3718E
Parm worktoken has bad footprint
Reason:
System Action:
Action:
Contact support
3700 - 3799
3719I
Parm worktoken is missing in plist
Reason:
System Action:
Action:
3720I
ENTERING ASSEMBLER MODULE ESPARLSW.S (date time)
Reason:
System Action:
Info only
Action:
None
3735E
parm releaseparms has bad footprint
Reason:
System Action:
Action:
Contact support
3700 - 3799
3736E
Parm releaseparms is missing in plist
Reason:
System Action:
Action:
3739I
Exiting assembler module ESPARLSW.s
Reason:
The web service has finished.
System Action:
Info only
Action:
None
3740I
ENTERING ASSEMBLER MODULE ESPASHWW.S (date time)
Reason:
System Action:
Info only
Action:
None
3700 - 3799
3741E
TYPE PARM VALUE IS INVALID
Reason:
The value supplied for the TYPE= keyword is incorrect. It should be one of EVENT,
JOBNAME or APPL
System Action:
Info only
Action:
Correct the value and resubmit the request.
3755E
Parm showparms has bad footprint
Reason:
System Action:
Action:
Contact support
3756E
Parm showparms is missing in plist
Reason:
System Action:
Action:
3700 - 3799
3759I
Exiting assembler module ESPASHWW.s
Reason:
System Action:
Info only
Action:
None
3760I
ENTERING ASSEMBLER MODULE ESPASTCD.S (date time)
Reason:
System Action:
Info only
Action:
None
3770I
COND NAME PASSED:
Reason:
System Action:
Info only
Action:
None
3700 - 3799
3771I
COND VALUE PASSED:
Reason:
System Action:
Info only
Action:
None
3775E
Parm setparms has bad footprint
Reason:
System Action:
Action:
Contact support
3776E
Parm setparms is missing in plist
Reason:
System Action:
Action:
3700 - 3799
3779I
Exiting assembler module ESPASTCD.s
Reason:
System Action:
Info only
Action:
None
3780I
ENTERING ASSEMBLER MODULE ESPASTPW.S (date time)
Reason:
System Action:
Info only
Action:
None
3795E
Parm stopparms has bad footprint
Reason:
System Action:
Action:
Contact support
3700 - 3799
3796E
Parm stopparms is missing in plist
Reason:
System Action:
Action:
3797E
Parm worktoken has bad footprint
Reason:
System Action:
Action:
Contact support
3798E
Parm worktoken is missing in plist
Reason:
System Action:
Action:
3800 - 3899
3799I
Exiting assembler module ESPASTPW.s
Reason:
System Action:
Info only
Action:
None
3800 - 3899
3800I
ENTERING ASSEMBLER MODULE ESPASTRW.S (date time)
Reason:
System Action:
Info only
Action:
None
3801E
TYPE PARM VALUE IS INVALID
Reason:
The value supplied for the TYPE= keyword is incorrect. It should be REPLACE or ADD
System Action:
Info only
Action:
Correct the value and resubmit the request.
3800 - 3899
3810I
WORK ID PASSED:
Reason:
System Action:
Info only
Action:
None
3811E
Parm workname is missing in plist
Reason:
System Action:
Action:
3812E
Parm workname has bad footprint
Reason:
System Action:
Action:
Contact support
3800 - 3899
3813E
Parm identity is missing in plist
Reason:
System Action:
Action:
3814E
Parm identity has bad footprint
Reason:
System Action:
Action:
Contact support
3815E
Parm startparms has bad footprint
Reason:
System Action:
Action:
Contact support
3800 - 3899
3816E
Parm startparms is missing in plist
Reason:
System Action:
Action:
3819I
Exiting assembler module ESPASTPW.s
Reason:
System Action:
Info only
Action:
None
3820E
INVALID EXEC PARM
Reason:
An invalid parameter was specified
System Action:
Action:
Correct and resubmit the job
3800 - 3899
3821E
ESPDRIVR: CANNOT LOAD ESPAxxxx
Reason:
The requested service cannot be located
System Action:
Action:
Make sure that the path statements are correct.(STEPLIB or JOBLIB)
3822I
EXEC PARAMETERS SUPPLIED:
Reason:
System Action:
Info only
Action:
None
3823I
PARAMETERS READ FROM:
Reason:
Displays the parameters in the input file
System Action:
Info only
Action:
None
3800 - 3899
3824I
PARAMETERS IN EFFECT:
Reason:
Displays the active parameters
System Action:
Info only
Action:
None
3825I
RETURN CODE FROM THE PROCESS
Reason:
Displays the return code from the product
System Action:
Info only
Action:
If the return code is non zero, check the log for additional messages
3826I
REASON CODE FROM THE PROCESS
Reason:
Displays the reason code from the product
System Action:
Info only
Action:
The reason code will accompany a non zero return code but could also be 0 if it
3800 - 3899
3827I
LOADED SERVICE IS xxxxxxxx
Reason:
Displays the selected service module's id
System Action:
Info only
Action:
None
3830E
Internal Error - parm parmname is missing in plist in service
Reason:
The requested web service detected an error. parmname - this identifies the parameter
in error and is one of workname, startparms, stopparms, holdparms, release parms,
setparms, or showparms service - this identifies the service that generated the fault and
is one of startWork, stopWork, holdWork, releaseWork, showWork, or setCondition
System Action:
The web service request is aborted.
Action:
Contact CA Support - this cannot be resolved by the user.
3831E
Internal Error - parm parmname has a bad control block in service
Reason:
The requested web service detected an error. parmname - this identifies the parameter
in error and is one of workname, startparms, stopparms, holdparms, release parms,
setparms, or showparms service - this identifies the service that generated the fault and
is one of startWork, stopWork, holdWork, releaseWork, showWork, or setCondition
System Action:
The web service request is aborted.
Action:
Contact CA Support - this cannot be resolved by the user.
3800 - 3899
3840E
MISSING required WaitMode
Reason:
There was no WaitMode specified.
System Action:
Action:
3841E
CPU_Mon xxxx in Appl yyyy, WAITMODE and CONTINUOUS are mutually exclusive
Reason:
There was WAITMODE statement specified together with CONTINUOUS operand on the
CPU statement.
System Action:
Action:
Choose between WAITMODE and CONTINUOUS and use only one of them.
3842E
CPU_Mon xxxx in Appl yyyy, CPU statement does not apply for WAITMODE NOW
Reason:
CPU statement was specified together with WAITMODE NOW.
System Action:
Action:
Remove the whole CPU statement or do not use WAITMODE NOW.
3800 - 3899
3843E
DISK_Mon xxxx in Appl yyyy, WAITMODE and CONTINUOUS are mutually exclusive
Reason:
DISK statement.
System Action:
Action:
3844E
DISK_Mon xxxx in Appl yyyy, FROM, TO, NOCHANGE, WITHIN, OUTSIDE, AVAILABLE ,
and USED operands do not apply for WAITMODE NOW
Reason:
The FROM, TO, NOCHANGE, WITHIN, OUTSIDE, AVAILABLE, or USED operands on the
DISK statement were specified together with WAITMODE NOW.`
System Action:
Action:
Remove the FROM, TO, NOCHANGE, WITHIN, OUTSIDE, AVAILABLE, and USED operands
on the DISK statement or do not use WAITMODE NOW.
3845E
EVENTLOG_Mon xxxx in Appl yyyy, WAITMODE and CONTINUOUS are mutually
exclusive
Reason:
EVENTLOG statement.
System Action:
Action:
3800 - 3899
3846E
TEXT_Mon xxxx in Appl yyyy, WAITMODE and CONTINUOUS are mutually exclusive
Reason:
TEXTSTRING statement.
System Action:
Action:
3847E
TEXT_Mon xxxx in Appl yyyy, TO is specified on the SEARCHRANGE for WAITMODE
WAIT
Reason:
There was TO specified on the SEARCHRANGE together with WAITMODE WAIT.
System Action:
Action:
Remove the TO operand on the SEARCHRANGE, when WAITMODE WAIT is specified.
3848E
TEXT_Mon xxxx in Appl yyyy, NOTEXIST is specified on the TEXTSTRING for
WAITMODE WAIT
Reason:
There was NOTEXIST operand specified on the TEXTSTRING statement together with
WAITMODE WAIT.
System Action:
Action:
Use WAITMODE NOW with NOTEXIST or remove NOTEXIST for WAITMODE WAIT.
3800 - 3899
3881E
Action not supported.
Reason:
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:
Action:
Specify either REGISTEREVENT or TRIGGER action keyword.
3882E
Reason:
zzzz.
System Action:
Action:
3800 - 3899
3883E
Reason:
zzzz.
System Action:
Action:
3884E
Reason:
System Action:
Action:
3800 - 3899
3885E
Reason:
System Action:
Action:
3886E
Reason:
System Action:
Action:
3887E
Reason:
System Action:
Action:
3800 - 3899
3888E
SAPE_JOB xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
3889E
Reason:
There was insufficient space in the ATR to store data for a SAPE_Job jjjj in application
aaaa.
System Action:
Action:
3890W
Agent wwww is not defined or you are not authorized to use it
Reason:
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.
Action:
Either correct the Agent name, or define the Agent, and resubmit the RESDEF command.
3800 - 3899
3891E
Reason:
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 internal control block.
System Action:
The new generation of the application will remain in ancestor wait status.
Action:
3892E
Reason:
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.
Action:
3893W
Reason:
The agent named wwww was not defined or you were not authorized to use it when
agent monitoring was being initialized after a LOADAGDF command was entered.
System Action:
Action:
Either correct the Agent name, or define the Agent, and resubmit the LOADAGDF
command.
3800 - 3899
3894W
Reason:
The agent named wwww was not defined or you were not authorized to use it when a
CPU command was entered.
System Action:
Action:
Either correct the Agent name, or define the Agent, and resubmit the CPU command.
3895W
Agent wwww not found for job yyyy
Reason:
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.
Action:
Update the system topology if needed.
3896E
Real resource must be defined as LOCAL. Resource xxxx rejected.
Reason:
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.
Action:
Re-enter the command with scope LOCAL.
3800 - 3899
3897E
WLM resource type XXXXXXXX is not supported
Reason:
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.
Action:
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.
Reason:
A RESDEF SET command specifying a real resource was issued. The product detected
that resource xxxx was defined with different type of a real resource.
System Action:
Action:
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 as resource xxxx is in use
Reason:
A RESDEF SET command specifying a real resource was issued. The product found job(s)
waiting for this resource.
System Action:
The resource was not updated.
Action:
Wait until no jobs are waiting for this resource, and then update it.
3900 - 3999
3900 - 3999
3938E
Must be 16 bytes long
Reason:
One of the following CRYPTKEY command operands KEY or OLDKEY was entered with
invalid encryption key length. The CRYPTKEY command was issued with AES parameter
specifying the AES encryption type. This encryption type requires length of the
encryption key be equal to 16 bytes (16 characters or 32 hexadecimal characters).
System Action:
Command is rejected.
Action:
Reenter the command with valid parameter length.

4000 - 4099
4001I
INPUT VALUE = xxxx
Reason:
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.
Action:
None.
4002I
OUTPUT VALUE = xxxx
Reason:
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.
Action:
None.
4000 - 4099
4003I
EVENT xxxx HAS BEEN UPDATED
Reason:
Event 'xxxx' was updated by the Event Data Set Record maintenance utility as a result of
a REPLACE statement.
System Action:
None.
Action:
None.
4004I
EVENT DB SCAN COMPLETE
Reason:
The Event Data Set Record maintenance utility has successfully completed processing.
System Action:
None.
Action:
None.
4005E
VSAM OPEN ERROR: RC = xxxx EC = yyyy
Reason:
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.
Action:
Determine the cause of the error from the VSAM Programmer's Guide.
4000 - 4099
4006E
VSAM POINT ERROR - ERROR CODE = xxxx
Reason:
point to the next Event record. 'xxxx' is the VSAM return code.
System Action:
Action:
4007E
VSAM PUT ERROR - ERROR CODE = xxxx
Reason:
write an Event record. 'xxxx' is the VSAM return code.
System Action:
Action:
4008E
FIELD NAME xxxx IS INVALID
Reason:
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:
Action:
Correct the field name.
4000 - 4099
4009E
THE INPUT VALUE IS IDENTICAL TO THE REPLACEMENT VALUE
Reason:
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.
Action:
Ensure the input and output values are different.
4010E
BOTH A MATCH VALUE AND A REPLACEMENT VALUE MUST BE SPECIFIED
Reason:
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.
System Action:
Action:
Ensure both the input and output values are specified.
4011E
SYNTAX ERROR IN COMMAND STATEMENT
Reason:
A syntax error existed in a statement supplied to the Event Data Set Record
maintenance utility.
System Action:
Action:
Correct the syntax error.
4000 - 4099
4012E
VSAM READ UNSUCCESSFUL - ERROR CODE = xxxx
Reason:
read an Event record. 'xxxx' is the VSAM return code.
System Action:
Action:
4020W
APPLFILE OR TRAKFILE KEYWORD OMITTED, COMMAND IGNORED
Reason:
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:
Action:
Specify one of the required keywords.
4021E
NO APPL RECORDS FOUND IN JOBINDEX
Reason:
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:
Action:
None.
4000 - 4099
4022E
NO JOB ENTRIES FOUND IN JOBINDEX
Reason:
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:
Action:
None.
4028W
Reason:
The JOBSTATS file cleanup utility (CYBESUT8) was invoked without a valid function being
specified.
System Action:
Action:
Reissue the request, specifying a valid function (ANALYZE or UPDATE).
4029W
No records requested, command ignored
Reason:
The JOBSTATS file cleanup utility (CYBESUT8) was invoked without any records being
specified.
System Action:
Action:
Reissue the request, specifying a valid function (JOB, PROFILE or EXTERNAL).
4000 - 4099
4030W
Reason:
The JOBINDEX file cleanup utility (CYBESUT7) was invoked without a valid function being
specified.
System Action:
Action:
Reissue the request, specifying a valid function (ANALYZE or UPDATE).
4039W
Neither APPL nor TRAK requested, command ignored
Reason:
The JOBINDEX file cleanup utility (CYBESUT7) was invoked without requesting
processing of either Application or Job Tracking records
System Action:
Action:
Reissue the request, specifying at least one of the APPL or TRAK operands.
4040E
Reason:
There was insufficient space in the ATR to store data for a OA_Job jjjj in application
aaaa.
System Action:
Action:
4000 - 4099
4041E
OA_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4042E
Reason:
System Action:
Action:
4043E
Reason:
System Action:
Action:
4000 - 4099
4044E
OA_Job xxxx in Appl yyyy, Oracle Application Name missing
Reason:
Both ApplShortName and ApplDisplName statements are missing.
System Action:
Action:
Provide ApplShortName or ApplDisplName statement. Then resubmit the job.
4045E
OA_Job xxxx in Appl yyyy, both Oracle Application Names defined
Reason:
Both ApplShortName and ApplDisplName statements are defined.
System Action:
Action:
Remove either ApplShortName or ApplDisplName statement. Then resubmit the job.
4046E
OA_Job xxxx in Appl yyyy, neither Program nor Request Set Name defined
Reason:
Both Program and RequestSet statements are missing.
System Action:
Action:
Provide Program or RequestSet statement. Then resubmit the job.
4000 - 4099
4047E
OA_Job xxxx in Appl yyyy, both Program and Request Set Names defined
Reason:
Both Program and RequestSet statements are defined.
System Action:
Action:
Remove Program or RequestSet statement. Then resubmit the job.
4048E
OA_Job xxxx in Appl yyyy, Description invalid for Request Set
Reason:
Desc (Description) statement is invalid for Request Set.
System Action:
Action:
Correct invalid combination of statements. Then resubmit the job.
4049E
OA_Job xxxx in Appl yyyy, missing ProgramData statement
Reason:
ProgramData statements are missing for Request Set.
System Action:
Action:
Provide ProgramData statement(s). Then resubmit the job.
4000 - 4099
4050E
OA_Job xxxx in Appl yyyy, Args statement invalid for Request Set
Reason:
Args statement is invalid for Request Set.
System Action:
Action:
4051E
OA_Job xxxx in Appl yyyy, ProgramData statement invalid for Program
Reason:
ProgramData statement is invalid for Program.
System Action:
Action:
4052E
OA_Job xxxx in Appl yyyy, ProgArgs statement invalid for Program
Reason:
ProgArgs statement is invalid for Program.
System Action:
Action:
4000 - 4099
4053E
OA_Job xxxx in Appl yyyy, ProgPrinter statement invalid for Program
Reason:
ProgPrinter statement is invalid for Program.
System Action:
Action:
4054E
OA_Job xxxx in Appl yyyy, ProgPrintStyle statement invalid for Program
Reason:
ProgPrintStyle statement is invalid for Program.
System Action:
Action:
4055E
OA_Job xxxx in Appl yyyy, ProgPrintCopies statement invalid for Program
Reason:
ProgPrintCopies statement is invalid for Program.
System Action:
Action:
4000 - 4099
4056E
OA_Job xxxx in Appl yyyy, ProgSaveOutput statement invalid for Program
Reason:
ProgSaveOutput statement is invalid for Program.
System Action:
Action:
4057E
User xxxx denied access to User ID yyyy
Reason:
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:
Action:
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.
4000 - 4099
4058E
Reason:
System Action:
Action:
4059E
Invalid Program Number
Reason:
The number in ProgramData statement in not higher than the current number.
System Action:
Action:
Correct ProgramData statement.
4060E
ARGS too long
Reason:
The length of the ARGS exceeds the maximum of 4070 characters.
System Action:
Action:
Reduce the length of the ARGS.
4000 - 4099
4061E
Invalid Args specification
Reason:
More than 100 Args statements have been defined.
System Action:
Action:
Reduce the number of the ARGS statements. Then resubmit the job.
4062E
PROGARGS too long
Reason:
The length of the PROGARGS exceeds the maximum of 4070 characters.
System Action:
Action:
Reduce the length of the PROGARGS.
4063E
Invalid ProgArgs specification
Reason:
More than 100 ProgArgs statements have been defined.
System Action:
Action:
Reduce the number of the PROGARGS statements. Then resubmit the job.
4000 - 4099
4064E
Reason:
There was insufficient space in the ATR to store data for a SQL_Job jjjj in application
aaaa.
System Action:
Action:
4065E
SQL_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4066E
SQL_Job xxxx in Appl yyyy, missing SQL Statement
Reason:
There was no SQL Statement to identify the work to run.
System Action:
Action:
Provide the SQL Statement. Then resubmit the job.
4000 - 4099
4067E
Reason:
System Action:
Action:
4068E
Reason:
System Action:
Action:
4069E
Reason:
System Action:
Action:
4000 - 4099
4070E
DB_URL too long
Reason:
The length of the DB_URL exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the DB_URL.
4071E
OUTPUT_FILE too long
Reason:
The length of the OUTPUT_FILE exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the OUTPUT_FILE.
4072E
JOB_CRITERIA too long
Reason:
The length of the JOB_CRITERIA exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the JOB_CRITERIA.
4000 - 4099
4073E
SQL Command too long
Reason:
The length of the SQL Command exceeds the maximum of 4070 characters.
System Action:
Action:
Reduce the length of the SQL Command.
4074E
User Type too long, maximum length nn
Reason:
User Type is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of User Type.
4075E
Reason:
There was insufficient space in the ATR to store data for a DBSP_Job jjjj in application
aaaa.
System Action:
Action:
4000 - 4099
4076E
DBSP_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4077E
DBSP_Job xxxx in Appl yyyy, missing SpName Statement
Reason:
There was no SpName Statement to identify the work to run.
System Action:
Action:
Provide the SpName Statement. Then resubmit the job.
4078E
Reason:
System Action:
Action:
4000 - 4099
4079E
Reason:
System Action:
Action:
4080E
Reason:
System Action:
Action:
4081E
DB_URL too long
Reason:
System Action:
Action:
4000 - 4099
4082E
Stored Procedure name too long
Reason:
The length of the Stored Procedure name exceeds the maximum of 100 characters.
System Action:
Action:
Reduce the length of the Stored Procedure name.
4083E
Return data type too long
Reason:
The length of the Return data type exceeds the maximum of 100 characters.
System Action:
Action:
Reduce the length of the Return data type.
4084E
JOB_CRITERIA too long
Reason:
The length of the JOB_CRITERIA exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the JOB_CRITERIA.
4000 - 4099
4085E
Reason:
System Action:
Action:
4086E
ARGS too long
Reason:
System Action:
Action:
4087E
Reason:
There was insufficient space in the ATR to store data for a DB_TRIG jjjj in application
aaaa.
System Action:
Action:
4000 - 4099
4088E
DB_TRIG xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4089E
DB_TRIG xxxx in Appl yyyy, missing TableName Statement
Reason:
There was no TableName Statement to identify the work to run.
System Action:
Action:
Provide the TableName Statement. Then resubmit the job.
4090E
Reason:
System Action:
Action:
4000 - 4099
4091E
Reason:
System Action:
Action:
4092E
Reason:
System Action:
Action:
4093E
Reason:
System Action:
Action:
4000 - 4099
4094E
DB_URL too long
Reason:
System Action:
Action:
4095E
TRIGTYPE too long
Reason:
The length of the TRIGTYPE exceeds the maximum of 50 characters.
System Action:
Action:
Reduce the length of the TRIGTYPE.
4096E
TRIGCOND too long
Reason:
The length of the TRIGCOND exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the TRIGCOND.
4000 - 4099
4097E
TABLENAME too long
Reason:
The length of the TABLENAME exceeds the maximum of 100 characters.
System Action:
Action:
Reduce the length of the TABLENAME.
4098E
Reason:
There was insufficient space in the ATR to store data for a DB_MON jjjj in application
aaaa.
System Action:
Action:
4099E
DB_MON xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4100 - 4199
4100 - 4199
4100E
Reason:
System Action:
Action:
4101E
tttt xxxx in Appl yyyy, missing Local File Name
Reason:
Job type tttt requires a Local File Name to be specified indicating what work is to be
System Action:
Action:
4102E
Reason:
System Action:
Action:
4100 - 4199
4103E
Invalid ENVAR specification
Reason:
A syntactical error was found scanning the ENVAR statement to extract the names and
values of the variables
System Action:
Action:
Correct the syntax of the ENVAR statement. Then resubmit the job.
4104E
???_Job xxxx in Appl yyyy, missing zzzz name
Reason:
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:
Action:
Provide the required information. Then resubmit the job.
4105E
Reason:
System Action:
Action:
4100 - 4199
4106E
SAP_Job xxxx in Appl yyyy, missing ABAPname
Reason:
Each SAP_Job requires an ABAPname to be specified indicating what work is to be done
System Action:
Action:
4109E
Reason:
System Action:
Action:
4100 - 4199
4110E
Reason:
System Action:
Action:
job.
4112E
Reason:
System Action:
Action:
4100 - 4199
4113E
Reason:
System Action:
Action:
SAF profile AGENTUSR.yyyy.agentname. Once this has been established, retrigger the
event.
4114E
USER can only be used with encrypted agents
Reason:
The USER statement can only be used with agents that have encryption enabled on their
communications channel.
System Action:
Action:
if the use of USER is required, have the administrator activate encryption on this agent's
communications.
4100 - 4199
4115I
xxxxxxxx: yyyyyyyyyyyyyyyyyy
Reason:
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.
System Action:
None.
Action:
None.
4116W
Reason:
WARNING Text(yyyyyyyyyyy)' automation framework message. The source of the
message is xxxxxxxx.
System Action:
None.
Action:
None.
4117E
Reason:
ERROR Text(yyyyyyyyyyy)' automation framework message. The source of the message
is xxxxxxxx.
System Action:
None.
Action:
None.
4100 - 4199
4118E
Reason:
zzzz.
System Action:
Action:
4119E
COMMANDNAME too long
Reason:
The value on the COMMANDNAME statement exceeded the maximum length of 100
characters.
System Action:
The statement is not processed. Event processing fails.
Action:
Reduce the length of the value.
4120E
COMMAND too long
Reason:
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.
Action:
Reduce the length of the value.
4100 - 4199
4121E
ERROR SCANNING COMMAND, RC=x
Reason:
An invalid parameter was coded on a command.
System Action:
Action:
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
Reason:
Agent specified in AGENT statement could not be found.
System Action:
Application will not be built.
Action:
Make sure the correct name is used in the AGENT statement.
4123I
Update successful
Reason:
A define, update or delete requested through the PASSWORD command completed
successfully.
System Action:
N/A
Action:
N/A
4100 - 4199
4124E
xxxx must be specified
Reason:
The operation requested requires that keyword xxxx be specified on the PASSWORD
command.
System Action:
Action:
Correct the command and retry the operation.
4125W
No entries found to match your criteria
Reason:
No entries were found that matched the criteria specified on the PASSWORD LIST
command.
System Action:
N/A
Action:
Retry the command with different criteria.
4126E
Index dataset is not open
Reason:
The user attempted to update a password entry, but the index data set is not open.
System Action:
Action:
Investigate why the index data set is closed. Retry the command when it is re-opened.
4100 - 4199
4127E
The encryption routine reported an error
Reason:
The user attempted to update a password entry, but the encryption routine reported an
error.
System Action:
Action:
This is most likely an internal error. Contact CA Support.
4128W
No matching entries found
Reason:
No entries were found that matched the criteria specified on the PASSWORD LIST
command.
System Action:
N/A
Action:
Retry the command with different criteria.
4129E
Duplicate password entry
Reason:
The user attempted to define a password entry, but the entry already exists.
System Action:
Action:
Use the LIST option of the PASSWORD command to list existing entries to verify your
information.
4100 - 4199
4131E
Password does not match, update refused
Reason:
The user attempted to update or delete a password entry, but the password supplied
did not match the password on file.
System Action:
Action:
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
Reason:
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:
Action:
Either specify a verification password, or acquire UPDATE access to SAF resource
PASSWORD.
4100 - 4199
4133E
Specified password entry not found
Reason:
The user attempted to update or delete a password entry, but the specified entry does
not exist.
System Action:
Action:
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
Reason:
The index dataset was found closed during PWDE initialization.
System Action:
The password entry list is not initialized.
Action:
Verify why the index data set was closed during initialization. Perform a warm start to
initialize the password entry list when the index data set becomes available.
4135E
Above error occurred during PWDE initialization
Reason:
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.
Action:
This message should be preceded by a message detailing the nature of the I/O error.
4100 - 4199
4136E
User ID too long, maximum length nn
Reason:
A user ID specified on the USER statement was longer than the maximum allowed for
the workload object type.
System Action:
Action:
Replace the user ID with a valid ID.
4140E
FileTrig xxx in Appl yyy, missing file name
Reason:
The file name is missing for workload object xxx in application yyy.
System Action:
Action:
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
Reason:
The agent name is missing for FileTrig object xxx in application yyy.
System Action:
Action:
Make sure an AGENT statement with the correct Agent Name is present for FileTrig
object xxx in application yyy.
4100 - 4199
4147E
No space in ATR to store AS/400 message text
Reason:
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.
Action:
4148E
FILENAME specification error: xxxxxxxxxxxxxxxxxxxx
Reason:
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.
Action:
Correct the error.
4149E
DB_MON xxxx in Appl yyyy, missing TableName Statement
Reason:
There was no TableName Statement to identify the work to run.
System Action:
Action:
Provide the TableName Statement. Then resubmit the job.
4100 - 4199
4150E
Invalid SETVAR Specification
Reason:
A SETVAR statement coded within a Data_Object is invalid.
System Action:
The system stops processing the procedure.
Action:
Correct the syntax error.
4151E
Reason:
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.
Action:
4152E
Error in WOBDATA function - 'Reason string'
Reason:
An error occurred in the WOBDATA CLANG function. The reason string contains further
details about the error.
System Action:
Processing ends.
Action:
This is most likely a syntax error. Check for an invalid object name or missing
parameters.
4100 - 4199
4153E
No space in ATR to store dependencies for object xxxxx
Reason:
There was insufficient space in the ATR to build the dependency links for an ApplEnd
object.
System Action:
Action:
4154E
ApplEnd can only be defined once
Reason:
More than one ApplEnd object was defined in an application. Only one ApplEnd per
application may be coded.
System Action:
The application is not build.
Action:
Remove all but one ApplDef object.
4155E
tttt xxxx in Appl yyyy, missing user name for agent aaaa
Reason:
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:
The product does not submit the job to the agent. The Job's PNODE is set to SUBERROR.
Action:
Specify a user name and rerun the job.
4100 - 4199
4156E
Reason:
System Action:
Action:
4157E
Reason:
System Action:
Action:
4158E
tttt xxxx in Appl yyyy, missing user name for agent aaaa
Reason:
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:
The product does not submit the job to the agent. The Job's PNODE is set to SUBERROR.
Action:
Specify a user name and rerun the job.
4100 - 4199
4159E
Reason:
System Action:
Action:
4160E
MPEiX_Job xxxx in Appl yyyy, missing account
Reason:
An account name, which is necessary for login to an MPE/iX system, was not provided in
the job definition.
System Action:
Action:
4161E
User xxxx denied access to account yyyy on agent aaaa
Reason:
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.
Action:
In order to submit jobs to this agent using account yyyy, provide user xxxx with read
access to SAF profile AGENTACC.yyyy.aaaa.
4100 - 4199
4162E
User xxxx denied access to group yyyy on agent aaaa
Reason:
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.
System Action:
The current process (submission of a job or building of an application) is aborted.
Action:
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
Reason:
System Action:
Action:
4164E
OTHERS too long
Reason:
The length of the OTHERS exceeds the maximum of 4070 characters.
System Action:
Action:
Reduce the length of the OTHERS.
4100 - 4199
4165E
PARAM too long
Reason:
The length of the PARAM exceeds the maximum of 4070 characters.
System Action:
Action:
Reduce the length of the PARAM.
4166W
JOB xxxx SUBMISSION FAILED, STATUS: ssss
Reason:
message text indicates that a submitted job has a submission failure. The message text
System Action:
Action:
4167I
xxxx
Reason:
message text indicates that a submitted job has started to execute. The message text
System Action:
Action:
None.
4100 - 4199
4168I
xxxx
Reason:
message text indicates that a submitted job has ended execution. The message text
includes the completion code and can also include the application name or jobnet ID.
System Action:
Action:
None.
4169W
xxxx
Reason:
message text indicates that a 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:
Action:
4100 - 4199
4170I
xxxx yyyy COMPLETED
Reason:
message text indicates that a submitted JOB LINK of JOB TASK is completed. The
message text can also include the application name or jobnet ID.
System Action:
Action:
None.
4171I
TASK xxxx REQUIRES MANUAL COMPLETION
Reason:
message text indicates that a 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.
System Action:
Action:
After this TASK is completed, mark it complete to release its successor jobs.
4172W
xxxx yyyy
Reason:
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:
Action:
4100 - 4199
4173W
MANUAL JOB xxxx
Reason:
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:
Action:
4174W
APPLICATION xx GENERATION nn, User yy, WILL BE FORCED COMPLETE BY ESP
Reason:
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.
Action:
None.
4175W
APPLICATION xx, User yy, IS REACHING THE LIMIT OF ACTIVE GENERATIONS
Reason:
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 the product. User name is the event owner.
System Action:
Action:
Notify the application owner.
4100 - 4199
4176I
Auditlog data set spun with nn records to sysout class xxxx
Reason:
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.
Action:
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
Reason:
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 the
Action:
The product should be restarted. If the error persists, comment out the AUDITLOG
initialization statement and place an AUDITLOG DD statement in the started task
procedure until the problem can be resolved.
4100 - 4199
4178W
Dynamic sysout auditlog not initialized, use AUDITLOG initialization parameter
Reason:
The SPINLOG command was issued. This command is only available if the AUDITLOG
initialization parameter is used.
System Action:
Action:
Add the AUDITLOG initialization statement to the parameter data set and restart the
product. 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
4179I
APPLICATION xxxx GENERATION nn JOB yyyy FORCED COMPLETE BY zzzz
Reason:
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.
Action:
None.
4100 - 4199
4180I
APPLICATION xxxx GENERATION nn JOB yyyy Resources dropped by zzzz
Reason:
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.
Action:
None.
4181E
Invalid LIBL parameter
Reason:
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.
Action:
4100 - 4199
4182W
AUDCOUNT VALUE IS IGNORED SINCE IT IS LESS THAN 5
Reason:
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.
Action:
Correct the AUDCOUNT parameter. The correction will take effect after the product is
restarted.
4183E
PROCESS TYPE too long
Reason:
The length of the PROCESS TYPE exceeds the maximum of 32 characters.
System Action:
Action:
Reduce the length of the PROCESS TYPE.
4184E
RUNCONTROLID too long
Reason:
The length of the RUNCONTROLID exceeds the maximum of 30 characters.
System Action:
Action:
Reduce the length of the RUNCONTROLID.
4100 - 4199
4185E
Reason:
A PSOprID was specified which required a password. The product was unable to find a
zzzz.
System Action:
Action:
4186E
PS_Job xxxx in Appl yyyy, missing Process Name
Reason:
A Process Name, which is necessary for a PeopleSoft system, was not provided in the job
definition.
System Action:
Action:
4187E
PS_Job xxxx in Appl yyyy, missing Process Type
Reason:
A Process Type, which is necessary for a PeopleSoft system, was not provided in the job
definition.
System Action:
Action:
4100 - 4199
4188E
DistrListUsers too long
Reason:
The length of the DistrListUsers exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the DistrListUsers.
4189E
DistrListRoles too long
Reason:
The length of the DistrListRoles exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the DistrListRoles.
4190E
EmailAddr too long
Reason:
The length of the EmailAddr exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the EmailAddr.
4100 - 4199
4191E
EmailSubject too long
Reason:
The length of the EmailSubject exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the EmailSubject.
4192E
EmailAddrExp too long
Reason:
The length of the EmailAddrExp exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the EmailAddrExp.
4193E
EmailText too long
Reason:
The length of the EmailText exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the EmailText.
4100 - 4199
4194E
SAPEmailAddr too long
Reason:
The length of the SAPEmailAddr exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the SAPEmailAddr.
4195E
EmailAddr too long
Reason:
System Action:
Action:
4196E
Reason:
System Action:
Action:
4100 - 4199
4197E
Reason:
System Action:
Action:
4198E
Reason:
System Action:
Action:
4199E
DB_URL too long
Reason:
System Action:
Action:
4200 - 4299
4200 - 4299
4200S
XCFCMD command code xxxx invalid
Reason:
System Action:
Action:
4201E
SYSPLEX error, Default XCF group xxxx already joined, Member=yyyy
Reason:
System Action:
Action:
4200 - 4299
4202W
SYSPLEX TERMOPT=QUIESCE ignored, Sysplex in XCFLOCAL mode
Reason:
The SYSPLEX statement in the ESPPARM file specifies TERMOPT(QUIESCE) and MVS is in
XCFLOCAL mode, that is 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. The product will leave the XCF group when it terminates, because
it cannot quiesce its XCF member.
Action:
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
Reason:
An XCF command was issued with no operands.
System Action:
Action:
For a list of valid XCF command options, enter one of the following:
XCF HELP
XCF H
XCF ?
4200 - 4299
4204E
XCF xxxx command invalid
Reason:
An XCF command was issued with an invalid option xxxx.
System Action:
Action:
XCF HELP
XCF H
XCF ?
4205E
XCF xxxx not an initialization command
Reason:
An XCF statement in the ESPPARM file specifies option xxxx, which is invalid at
initialization.
System Action:
The product action message 802A is issued to prompt for an END (to ignore the "XCF
xxxx" statement) or a CANCEL (to terminate the product) response.
Action:
Respond to action message 802A and remove erroneous "XCF xxxx" statement from
ESPPARM file.
4200 - 4299
4206E
XCF xxxx object missing
Reason:
The XCF command with option xxxx requires one or more additional operands.
System Action:
Action:
XCF HELP
XCF H
XCF ?
4207E
XCF xxxx object yyyy invalid
Reason:
The XCF command with option xxxx specified an invalid option yyyy.
System Action:
Action:
XCF HELP
XCF H
XCF ?
4200 - 4299
4208I
XCF HELP
Reason:
Response to "XCF HELP", "XCF H" or "XCF ?" command.
System Action:
Action:
None.
4209I
No active XCF connections
Reason:
Response to "XCF DISPLAY ACTIVE" or "XCF D A" command.
System Action:
Action:
None.
4210I
XCF DISPLAY ACTIVE
Reason:
Response to "XCF DISPLAY ACTIVE" or "XCF D A" command. Displays active XCF listeners
and active XCF connections.
System Action:
Action:
None.
4200 - 4299
4211W
No XCF groups joined
Reason:
Response to "XCF DISPLAY GROUP" or "XCF D G" command. During initialization, the
product tried unsuccessfully to join an XCF group as a member specified by the SYSPLEX
statement in the ESPPARM file. This usually happens when another instance of the
product has already joined the XCF group has the same member name.
System Action:
Action:
To request the current instance of the product to retry joining the XCF group as the
specified member, enter the following 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 already active XCF
member name, then enter the following operator command: TRYJOIN MEMBER(zzzz)
where zzzz specifies a new XCF member name.
4212I
XCF DISPLAY GROUP
Reason:
Response to "XCF DISPLAY GROUP" or "XCF D G" command. Displays members of the
XCF group in the sysplex that the current instance of the product has joined.
System Action:
Action:
None.
4200 - 4299
4213I
XCF DISPLAY SYSTEMS
Reason:
Response to "XCF DISPLAY SYSTEMS" or "XCF D SYS" command. Displays MVS systems in
the sysplex.
System Action:
Action:
None.
4214W
No registered XCF services
Reason:
Response to "XCF DISPLAY SERVICES" or "XCF D S" command. No XCF services are
available to the current instance of the product. This happens when there are no "XCF
START SERVICE" statements in the ESPPARM file.
System Action:
Action:
None if the use of XCF services are not required by the current product. If the use of XCF
services (TRACKING, DSTRIG, ROUTING etc.) are required by the current product, an
"XCF START SERVICE" statement must be added to the ESPPARM file for each required
XCF service. Then the product must be restarted.
4200 - 4299
4215I
XCF DISPLAY SERVICES
Reason:
Response to "XCF DISPLAY SERVICES" or "XCF D S" command. Displays the status of each
registered XCF service, that is each XCF service specified by an "XCF START SERVICE"
statement in the ESPPARM file.
System Action:
Action:
None.
4216I
XCF service xxxx already started|resumed{, Group=yyyy{, Member=zzzz}}
Reason:
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 product XCF service, yyyy is the XCF group name and zzzz is the local XCF
member name.
System Action:
Action:
None.
4217I
XCF service xxxx started{, Group=yyyy{, Member=zzzz}}
Reason:
Response to "XCF START SERVICE xxxx" or "XCF S S xxxx" command. xxxx is the product
XCF service, yyyy is the XCF group name and zzzz is the local XCF member name.
System Action:
XCF service xxxx is activated.
Action:
None.
4200 - 4299
4218W
XCF service xxxx not active{, Group=yyyy{, Member=zzzz}}
Reason:
Response to "XCF STOP SERVICE xxxx" or "XCF P S xxxx" command. xxxx is the product
XCF service, yyyy is the XCF group name and zzzz is the local XCF member name.
System Action:
Action:
None.
4219W
XCF service xxxx cannot be stopped|suspended, no associated connection{,
Group=yyyy{, Member=zzzz}}
Reason:
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 XCF service, yyyy is the XCF
group name and zzzz is the local XCF member name. The 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 the product's
XCF services are registered with a "XCF STOP SERVICE" exit. This message should
therefore never be displayed by the product.
System Action:
Action:
4200 - 4299
4220I
XCF service xxxx stopped|suspended{, Group=yyyy{, Member=zzzz}}
Reason:
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 XCF service, yyyy is
the XCF group name and zzzz is the local XCF member name.
System Action:
XCF service xxxx stops or suspends.
Action:
None.
4221I
{Listener and }wwww connections purged, Service=xxxx{, Group=yyyy{,
Member=zzzz}}
Reason:
Response to "XCF PURGE SERVICE xxxx" or "XCF PURGE S xxxx" command. wwww is the
number of connections purged, xxxx is the 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. The product then immediately restarts XCF service xxx
Action:
None.
4200 - 4299
4222E
XCF {START|STOP|PURGE} SERVICE object missing
Reason:
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:
Action:
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
Reason:
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:
Action:
Re-enter the command specifying a valid XCF service to START, STOP or PURGE. For
example: XCF STOP SERVICE ROUTING
4200 - 4299
4224E
Connection xxxx not found
Reason:
Response to "XCF PURGE CONNECTION xxxx" or "XCF PURGE CON xxxx" command. xxxx
is the local connection number.
System Action:
Action:
Re-enter the command specifying the local connection number of an active XCF
connection. To display the active XCF connections, enter one of the following
commands:
XCF DISPLAY ACTIVE
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
Reason:
Response to "XCF PURGE CONNECTION xxxx" or "XCF PURGE CON xxxx" command. xxxx
is the local connection number.
System Action:
Connection xxxx is closed.
Action:
None.
4200 - 4299
4226I
xxxx members stopped
Reason:
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.
Action:
None.
4227E
XCF SET MEMBER invalid at initialization
Reason:
Response to "XCF SET MEMBER" or "XCF T M" statement in the ESPPARM file.
System Action:
Action:
Remove the "XCF SET MEMBER" or "XCF T M" statement from ESPPARM file.
4228E
XCF SET MEMBER object missing
Reason:
Response to "XCF SET MEMBER" or "XCF T M" command. An XCF member name was not
specified in the command.
System Action:
Action:
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.
4200 - 4299
4229E
XCF SET MEMBER object xxxx invalid
Reason:
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:
Action:
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 one of the following commands:
XCF DISPLAY GROUP
XCF D G
4230E
XCF SET MEMBER exit not registered
Reason:
Response to "XCF SET MEMBER" or "XCF T M" command. If the product does not
register an "XCF SET MEMBER exit", the command has no meaning. However, the
product registers an "XCF SET MEMBER exit" to process the {MASTER|M} operand. This
message should therefore never be displayed by the product.
System Action:
Action:
4200 - 4299
4231I
XCF member xxxx stopped, Group=yyyy
Reason:
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.
Action:
None.
4232I
XCF member xxxx forced, Group=yyyy
Reason:
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.
Action:
None.
4200 - 4299
4233E
XCF member xxxx active, cannot be deleted, Group=yyyy
Reason:
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:
Action:
To display the current XCF group members and their respective states, enter one of the
following commands:
XCF DISPLAY GROUP
XCF D G
4234I
XCF member xxxx deleted, Group=yyyy
Reason:
target XCF member name and yyyy is the XCF group.
System Action:
Target XCF member xxxx is removed from XCF group yyyy.
Action:
None.
4200 - 4299
4235E
XCF SET INTERVAL invalid at initialization
Reason:
The "XCF SET INTERVAL" or "XCF T INT" command is invalid as an ESPPARM file
statement.
System Action:
The product 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 the product) response.
Action:
Respond to action message 802A and remove "XCF SET INTERVAL" or "XCF T INT"
statement from ESPPARM file.
4236E
XCF SET INTERVAL value missing
Reason:
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:
Action:
Re-issue the "XCF SET INTERVAL" or "XCF T INT" command specifying a valid interval in
seconds (number within range 3-86400).
4200 - 4299
4237E
Status monitoring not active, Group=xxxx, Member=yyyy
Reason:
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:
Action:
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
Reason:
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 group name and zzzz is the local
XCF member name.
System Action:
The XCF status monitoring interval is reset to xxxx seconds.
Action:
None.
4200 - 4299
4239E
XCF SET TERMOPT invalid at initialization
Reason:
The "XCF SET TERMOPT" or "XCF T TO" command is invalid as an ESPPARM file
statement.
System Action:
The product 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 the product) response.
Action:
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
Reason:
Response to an "XCF SET TERMOPT" or "XCF T TO" command.
System Action:
Action:
Re-enter the "XCF SET TERMOPT" or "XCF T TO" command with the LEAVE or QUIESCE
option.
4200 - 4299
4241E
XCF SET TERMOPT QUIESCE invalid, system is in XCFLOCAL mode
Reason:
Response to an "XCF SET TERMOPT QUIESCE" or "XCF T TO Q" command. MVS is running
in XCFLOCAL mode, that is 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. The product will leave the XCF group when it terminates, because
it cannot quiesce its XCF member.
Action:
None.
4242I
XCF TERMOPT set to {LEAVE|QUIESCE}, Group=xxxx, Member=yyyy
Reason:
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. The product will leave the XCF group if LEAVE was specified, or
quiesce its XCF member if QUIESCE was specified, when it terminates.
Action:
None.
4200 - 4299
4243I
Verify request transmitted to XCF member xxxx, Group=yyyy
Reason:
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.
Action:
None.
4244E
XCF group xxxx not joined
Reason:
Response to various XCF commands. During initialization, the product tried
unsuccessfully to join an XCF group a member specified by the SYSPLEX statement in the
ESPPARM file. This usually happens when another instance of the product has already
joined XCF group as the same member name.
System Action:
Action:
To request the current product to retry joining the XCF group as the specified member,
enter the following 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
operator command: TRYJOIN MEMBER(zzzz) where zzzz specifies a new XCF member
name.
4200 - 4299
4245E
Local XCF member xxxx invalid, Group=yyyy
Reason:
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:
Action:
If necessary, re-enter the command specifying a non-local XCF member. To display the
current XCF group members, enter one of the following commands:
XCF DISPLAY GROUP
XCF D G
4246E
XCF member xxxx not found, Group=yyyy
Reason:
Response to an XCF command that specified target XCF member xxxx in XCF group yyyy.
XCF member xxxx does not exist.
System Action:
Action:
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
4200 - 4299
4247E
XCF member xxxx not active, Group=yyyy
Reason:
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:
Action:
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}}
Reason:
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.
System Action:
Action:
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}}
Reason:
Response to "XCF PURGE SERVICE xxxx" or "XCF PG S xxxx" command. xxxx is the XCF
service, yyyy is the XCF group name and zzzz is the local XCF member name.
System Action:
Action:
None.
4200 - 4299
4250W
System xxxx in sysplex partitioning, shutdown initiated, Group=yyyy, Member=zzzz
Reason:
The product has been notified by MVS that the current system xxxx is being removed
from the sysplex, that is 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:
Action:
None.
4251E
Message event, MSGCNTL invalid, Group=xxxx, Member=yyyy, Partner=zzzz
Reason:
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-CA 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:
Action:
Check if a CA and a non-CA product have joined the same XCF group. To display the
current XCF group members, enter one of the following commands:
XCF DISPLAY GROUP
XCF D G
If the local XCF member is a CA product, the XCF members in which the "ASID",
"Jobname", "SSID" and "ESP" fields are blank may indicate a non-CA product. If the
problem is still not solved, call your software support and provide the text of both the
current messpersonnel.ssage 4252 that immediately follows.
4200 - 4299
4252E
MSGCNTL=X'xxxx'
Reason:
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 product point of
view).
System Action:
Action:
Check if the product and a non-CA product have joined the same XCF group. To display
the current XCF group members, enter one of the following commands:
XCF DISPLAY GROUP
XCF D G
problem is still not solved, call your software support personnel 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
Reason:
System Action:
Action:
4200 - 4299
4254W
XCF buffer core request failed, Length=<length>, Partner=<member>, Group=[set the
product group or family], Service=<service>
Reason:
There is insufficient virtual storage for a buffer to receive <length> bytes of data
transmitted by member <member> of XCF group [set the product group or family] for
XCF service <service>.
System Action:
Action:
Perhaps the REGION parameter value of the JCL EXEC statement for the local XCF
member job should be increased. The product'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
Reason:
A request to stop the current product was received from XCF member xxxx in XCF group
yyyy.
System Action:
Action:
None.
4200 - 4299
4256I
Closing broken connection, Group=[set the product group or family],
Member=<local_member>{, Partner=<partner_member>}, Service=<service>{,
Token=(<local_token>, <partner_token>)}
Reason:
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.
Action:
None.
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=[set the product group or family], Member=<local_member>,
Partner=<partner_member>{, Service=<service>, Token=(<local_token>,
<partner_token>)}{{, Offset=<offset>}, Length=<length>}
Reason:
A message with an associated error has been received from member
<partner_member> in XCF group [set the product group or family].
System Action:
Action:
Usually none. If a problem exists, call your software support personnel.
4200 - 4299
4258W
XCF service xxxx stopped, default XCF group not defined
Reason:
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
subsystems, in the ESPPARM initialization file, an "XCF START SERVICE xxxx" statement
was specified, but the required SYSPLEX statement was missing or invalid.
System Action:
Action:
For 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
Reason:
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 the product
attempts to join XCF group yyyy as the same member name as an existing active
instance of the product.
System Action:
Action:
For 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 product is active in XCF group yyyy as the same
member name as specified in the MEMBER operand of the ESPPARM file of the local
product, 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
product has used to join XCF group yyyy. Once XCF group yyyy has been successfully
joined, all started XCF services, including xxxx, are activated.
4200 - 4299
4260E
Cannot join sysplex, default XCF group not defined
Reason:
System Action:
Action:
4261E
User state field length xxxx invalid, must be 32, Member=yyyy, Group=zzzz
Reason:
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-CA product.
System Action:
Action:
XCF DISPLAY GROUP
XCF D G
problem is still not solved, call your software support personnel.
4200 - 4299
4262E
User state field X'xxxx' invalid, Member=yyyy, Group=zzzz
Reason:
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-CA product.
System Action:
Action:
XCF DISPLAY GROUP
XCF D G
problem is still not solved, call your software support personnel.
4276I
XCF service <service> Timer=<timer>, Suspend=<suspend>
Reason:
Response to command: XCF SET SERVICE <service>{ TIMER=<timer>}{
SUSPEND=<suspend>} or XCF T S <service>{ T=<timer>}{ S=<suspend>}
System Action:
XCF service <service> default timer <timer> and suspend time <suspend> are displayed.
If the XCF service timer is unspecified (0), <timer> is displayed as "Null".
Action:
None.
4200 - 4299
4277W
XCF service <service> not started, subsystem terminating {, Group=[set the product
group or family]{, Member=<member>}}
Reason:
Response to "XCF START SERVICE <service>" or "XCF S S <service>" command. An
attempt was made to start XCF service <service> while the local subsystem was
terminating.
[set the product group or family] - specifies the XCF group name.
<member> - specifies the local XCF member name.
System Action:
The command is ignored and subsystem termination continues.
Action:
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=[set the product group or family]}{, 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>}}
Reason:
An informational message describing the result of an API call to XCF.
System Action:
Action:
None.
4200 - 4299
4281W
IXC{DELET|JOIN|LEAVE|MOD|MSGI|MSGO|QUERY|QUIES|SETUS|TERM}{,
Group=[set the product group or family]}{, Member=<member>}{,
Reason:
A warning message describing the result of an API call to XCF.
System Action:
Action:
None.
4282E
IXC{DELET|JOIN|LEAVE|MOD|MSGI|MSGO|QUERY|QUIES|SETUS|TERM}{,
Group=[set the product group or family]}{, Member=<member>}{,
Reason:
An error message describing the result of an API call to XCF.
System Action:
Action:
Usually none. The content of the message may indicate a specific action. If a problem
arises, call your software support personnel.
4200 - 4299
4285W
XCF not active
Reason:
An XCF command was issued, but XCF has not been activated for the product. For the
product, there is no SYSPLEX statement in the ESPPARM file.
System Action:
Action:
If XCF services are required, add a SYSPLEX statement to the ESPPARM file and recycle
the product.
4286W
XXCF <function>, <warning_description>{, <connection_infomation>}
Reason:
An internal API request for an XCF service has resulted in an unexpected condition. XXCF
is a macro that generates an internal API call for an XCF service.
System Action:
Action:
Check if the XCF services are in order with one of the following commands:
XCF D S
Check if the XCF connections are in order with one of the following commands:
XCF DISPLAY ACTIVE
XCF D A
If a problem exists, call your software support personnel.
4200 - 4299
4287E
XXCF <function>, <error_description>{, <connection_information>}
Reason:
An internal API request for an XCF service has resulted in an error condition. XXCF is a
macro that generates an internal API call for an XCF service.
System Action:
Action:
Check if the XCF services are in order with one of the following commands:
XCF D S
Check if the XCF connections are in order with one of the following commands:
XCF DISPLAY ACTIVE
XCF D A
If a problem exists, call your software support personnel.
4288S
XXCF <function>, <error_description>{, <connection_infomation>}
Reason:
Internal logic error. Should never happen. XXCF is a macro that generates an internal API
call for an XCF service.
System Action:
Action:
4200 - 4299
4290I
IXCARM Associate|DeRegister|Ready|Register|WaitPred{, aaaa| Return=bbbb,
Reason=cccc}, Element=dddd{, ElemType=eeee} {, TElement=ffff}{, StartTxt='gggg'}{,
TermType=AllTerm|ElemTerm}
aaaa - an informational message description.
bbbb - specifies the IXCARM call return code.
cccc - specifies the IXCARM call reason code.
dddd - specifies the ARM element name (ARMELEM command NAME keyword).
eeee - specifies the ARM element type (ARMELEM TYPE keyword).
ffff - specifies the ARM target element name of an ARM associate request (not
supported by the product).
gggg - specifies start text of an ARM register request (not supported by the
product).
Reason:
An Automatic Restart Management (ARM) request has completed successfully. The
message describes the request.
System Action:
Action:
None.
4200 - 4299
4291E
IXCARM Associate|DeRegister|Ready|Register|WaitPred{, aaaa| Return=bbbb,
Reason=cccc}, Element=dddd{, ElemType=eeee} {, TElement=ffff}{, StartTxt='gggg'}{,
TermType=AllTerm|ElemTerm}
aaaa - an error message description.
bbbb - specifies the IXCARM call return code.
cccc - specifies the IXCARM call reason code.
dddd - specifies the ARM element name (ARMELEM command NAME keyword).
eeee - specifies the ARM element type (ARMELEM TYPE keyword).
ffff - specifies the ARM target element name of an ARM associate request (not
supported by the product).
gggg - specifies start text of an ARM register request (not supported by the
product).
Reason:
An Automatic Restart Management (ARM) request has failed. aaaa or bbbb and cccc
describe the reason for the failure. Under the product, the ARMELEM initialization
statement usually causes this error.
System Action:
Action message 802A is issued to prompt for an END (to ignore the ARMELEM
statement) or a CANCEL (to terminate the product) response.
Action:
Attempt to determine the cause of the ARM request failure, and correct it. Then
respond to action message 802A by re-entering a correct ARMELEM statement, or
"END"
if there is no need to register the product with ARM, or "CANCEL" to terminate the
product. the ARMELEM statement in the ESPPARM initialization file is erroneous, then
correct it.
4200 - 4299
4292E
XARM Associate|DeRegister|Ready|Register|WaitPred xxxx xxxx is an error message
description.
Reason:
An Automatic Restart Management (ARM) request is invalid. xxxx describes the reason
for the failure. Under the product, the ARMELEM initialization statement usually causes
this error.
System Action:
Action message 802A is issued to prompt for an END (to ignore the ARMELEM
Action:
Attempt to determine the cause of the invalid ARM request, and correct it. Then
respond to action message 802A by re-entering a correct ARMELEM statement, or
"END" if there is no need to register the product with ARM, or "CANCEL" to terminate
the product. 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.
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.
Reason:
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:
Action:
Normally none. If the problem persists, contact your software support personnel.
4300 - 4399
4300 - 4399
4300S
Invalid ESP XCF request xxxx
Reason:
System Action:
Action:
4301E
XCF join request invalid, ESP xxxx has already joined XCF group yyyy as member zzzz
Reason:
System Action:
Action:
4302W
Cannot join XCF group, default not specified
Reason:
The product cannot join an XCF group because a SYSPLEX statement was not specified in
the ESPPARM file. The product currently suppresses this message.
System Action:
Action:
If XCF services are desired, add a SYSPLEX statement in the ESPPARM file specifying
which XCF group the product should join, and which member it should join as.
4300 - 4399
4303I
ESP xxxx has joined XCF group yyyy as member zzzz
Reason:
Response to "TRYJOIN" or "TRYJOIN MEMBER(zzzz)" command. 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 initialization. If the TRYJOIN MEMBER operand was omitted, zzzz is the
member specified in the SYSPLEX MEMBER operand.
System Action:
Action:
None.
4304E
XCF add services request invalid, ESP xxxx services already registered, Member=yyyy,
Group=zzzz
Reason:
System Action:
Action:
4300 - 4399
4305E
ESP master hold time xxxx not within range 1-1440
Reason:
Response to "SHADOW SHUTDOWN HOLD(xxxx)" command issued on a master
subsystem, where xxxx is a value in minutes. xxxx must specify a number within the
range 1-1440.
System Action:
The local system does not terminate. Processing continues.
Action:
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
Reason:
Response to "SHADOW SHUTDOWN HOLD(xxxx)" command issued on a master
subsystem. yyyy and zzzz specify the XCF group and member names respectively of the
master subsystem.
System Action:
The product terminates. If, after xxxx minutes, no master has been activated, all active
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.
Action:
None.
4300 - 4399
4307W
No active ESP shadow manager to relinquish control to
Reason:
Response to "SHADOW SHUTDOWN RELINQUISH" command issued on a master
subsystem. There is no active shadow to relinquish control to.
System Action:
Action:
If a shadow manager is needed to take over as the master when the current one
terminates, start one. Then re-issue the "SHADOW SHUTDOWN RELINQUISH" command.
To terminate the current system without relinquishing control to an active shadow
manager, enter the command: SHUTDOWN or SHADOW SHUTDOWN
4308E
XCF member xxxx not found
Reason:
Response to "SHADOW SHUTDOWN RELINQUISH(xxxx)" command issued on a master,
where xxxx must specify the XCF member name of an active shadow manager.
System Action:
Action:
To display the current XCF group members, enter the command: XCF DISPLAY GROUP or
XCF D G
If an active shadow manager exists, and the user wishes to relinquish control to it after
terminating the current master, then re-issue the "SHADOW SHUTDOWN
RELINQUISH(xxxx)" command specifying a valid active shadow manager xxxx.
4300 - 4399
4309W
XCF member xxxx not an active ESP shadow manager
Reason:
Response to "SHADOW SHUTDOWN RELINQUISH(xxxx)" command issued on a master.
System Action:
Action:
XCF D G
If an active shadow manager exists, and the user wishes to relinquish control to it after
terminating the current master, then re-issue the "SHADOW SHUTDOWN
RELINQUISH(xxxx)" command specifying a valid active shadow manager xxxx.
4310S
Local XCF member xxxx XMSE missing, Group=yyyy
Reason:
System Action:
Action:
4300 - 4399
4311I
XCF listener started, Service=xxxx
Reason:
Response to "XCF START SERVICE xxxx" or "XCF S S xxxx" ESPPARM file statement or
command on a master subsystem, where xxxx specifies an XCF service such as
TRACKING, DSTRIG, ROUTING etc.
System Action:
Action:
None.
4312I
XCF listener ended, Service=xxxx
Reason:
Response to "XCF STOP SERVICE xxxx or "XCF P S yyyy command on a master subsystem,
where xxxx specifies an XCF service such as TRACKING, DSTRIG, ROUTING etc.
System Action:
Action:
None.
4313I
XCF {transmitter|receiver} started, Service=xxxx, Partner=yyyy
Reason:
The local proxy's XCF service xxxx has connected to the master (XCF member yyyy). XCF
service xxxx (such as TRACKING, DSTRIG, ROUTING, SCOREBD etc.) is now active
between the local proxy and the partner master.
System Action:
Action:
None.
4300 - 4399
4314I
XCF transmitter ended, Service=xxxx, Partner=yyyy
Reason:
The local proxy's XCF connection with the master (XCF member yyyy) for XCF service
xxxx (such as TRACKING, DSTRIG, ROUTING, SCOREBD etc.) is closed. This happens if one
of the following occurs:
An "XCF STOP SERVICE xxxx" or "XCF P S xxxx" command is issued on either the local
proxy or the partner master (XCF member yyyy).
An "XCF PURGE CONNECTION zzzz" or "XCF PURGE CON zzzz" command, where zzzz
represents the local connection token for XCF service xxxx is issued on either the
local proxy or the partner 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 proxy and the partner 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.
Action:
None.
4315I
XCF status update resumed, probable main task normal execution
Reason:
XCF status monitoring is active for the local subsystem, that is 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 product, but status updating has now resumed. A
possible main task loop or hang appears to be resolved.
System Action:
Action:
None.
4300 - 4399
4316I
XCF status update missing, possible main task loop or hang
Reason:
XCF status monitoring is active for the local subsystem, that is 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 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 the product's main task. Note that this message does not necessarily
indicate a problem with the product. For example, the system that it is running under
may be heavily loaded and MVS may not be dispatching the product. It may also be
possible that MVS is malfunctioning in some way.
System Action:
Action:
Attempt to determine the cause of the failed XCF status monitoring update. If it is
determined that the product is either looping or hung, then cancel it with a dump and
call CA Support.
4318I
XCF status update resumed, Member=xxxx, Group=yyyy, System=zzzz
Reason:
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
product. 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.
System Action:
Action:
None.
4300 - 4399
4319E
XCF Member=xxxx incorrectly set to ESP master, ESP master is Member=yyyy
Reason:
The local system has been notified that XCF member xxxx has been set to the master.
However, a 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 system considers XCF member yyyy, not xxxx, to be the master. Processing
continues.
Action:
Verify that all ESPs in the XCF group recognize the same XCF member as the master by
enter the following command on each member of the group: XCF DISPLAY GROUP or
XCF D G If any discrepancy exists, stop any system considered to be the master by any
other system. Then restart the systems, 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 master.
4320W
Stopped ESP master hold time has expired, Member=xxxx
Reason:
A 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 master has since been started. The local
system, a shadow manager, has determined that the master hold time has expired and
it (the shadow manager) is now ready to assume the role of the master.
System Action:
Action:
Either start a new master, or request that the local system or another active shadow
manager take over as the master with the following command, issued from any system
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 shadow manager being set to the master. Or issue the
following command from the shadow manager that will take over as the master:
SHADOW ASSUMEPRIMARY or SHAD A
4300 - 4399
4321E
Invalid XCF signal code xxxx received from member yyyy
Reason:
System Action:
Action:
4322E
XCF SET MEMBER option missing
Reason:
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 where ESP001 is the XCF
member name of the shadow manager being set to the master.
System Action:
Action:
Re-enter the command specifying MASTER or M.
4323E
XCF member xxxx not active
Reason:
target XCF member of the command.
System Action:
Action:
XCF D G Then, if necessary, re-enter the command specifying a subsystem active XCF
member.
4300 - 4399
4324E
XCF member xxxx not an ESP subsystem
Reason:
target XCF member of the command. XCF member xxxx is not a subsystem and
therefore cannot be set to the master.
System Action:
Action:
XCF D G The "ESP" field in the response specifies "Master" for a master, "Proxy" for a
proxy, "Shadow" for a shadow manager, and "Unknown" for a that is neither the
master, nor a proxy, nor a shadow manager. Then, if necessary, re-enter the command
specifying an (active XCF member) proxy, shadow manager, or unknown system.
4325W
XCF member xxxx is already the ESP master
Reason:
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:
Action:
None.
4300 - 4399
4326E
XCF member xxxx is not an ESP shadow manager
Reason:
Response to "XCF SET MEMBER xxxx MASTER" or "XCF T M xxxx M" command.
System Action:
None.
Action:
XCF D G The "ESP" field in the response specifies "Master" for a master, "Proxy" for a
proxy, "Shadow" for a shadow manager, and "Unknown" for a system that is neither the
master, nor a proxy, nor a shadow manager. Then, if necessary, re-enter the command
specifying an (active XCF member) shadow manager to be set to the master.
4328I
XCF member xxxx set to ESP master
Reason:
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 a shadow manager.
System Action:
The local shadow manager becomes the master.
Action:
None.
4300 - 4399
4329I
Set to ESP master request sent to member xxxx
Reason:
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 a shadow manager.
System Action:
The command is transmitted to and processed by target XCF member xxxx.
Action:
To verify that the target 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}
Reason:
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 master and xxxx is the target XCF member of the command. Only one XCF
master is permitted in an XCF group.
System Action:
Action:
If it is necessary to make XCF member xxxx the master, then: If the master was unknown
during the attempt to set the local to the master, then issue the following command to
determine the current master: XCF DISPLAY GROUP or XCF D G Assuming there still is a
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 master.
4300 - 4399
4331W
XCF status update missing, Member=xxxx, Group=yyyy, System=zzzz
Reason:
The local system (member xxxx in XCF group yyyy on MVS system zzzz) has been notified
by XCF (MVS) that another member of the XCF group has failed to update its XCF status
monitor interval field, and therefore may be looping or hung.
System Action:
Action:
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
system is either looping or hung, then cancel it with a dump and call CA Support.
4333W
SHADGOAL xxxx only valid in shadow mode, ignored
Reason:
A SHADGOAL command was issued, but the system is not in shadow mode.
System Action:
Action:
None.
4300 - 4399
4335I
XCF receiver started, Service=TRACKING, Partner=xxxx
Reason:
A proxy system's TRACKING XCF service has connected to the local master. XCF job
tracking between the local master and the partner proxy (XCF member xxxx) is now
active.
System Action:
Action:
None.
4336I
XCF receiver ended, Service=TRACKING, Partner=xxxx
Reason:
A proxy system's TRACKING XCF service connection to the local master has been closed.
XCF job tracking between the local master and the partner proxy (XCF member xxxx) is
no longer active. This happens if the XCF TRACKING service is stopped on either the local
master or the partner proxy, or if the partner proxy is shut down.
System Action:
Action:
None.
4300 - 4399
4337W
XCF receiver waiting for CKPT file space, Service=TRACKING, Partner=xxxx
Reason:
The local master's checkpoint file is full, that is it cannot accommodate any job tracking
records transmitted from the partner proxy (XCF member xxxx).
System Action:
The local master's XCF TRACKING receiver waits for checkpoint space to become
available while other processing continues.
Action:
Ensure that the local master's tracking processor is active.
4338I
XCF receiver resumed, CKPT file space available, Service=TRACKING, Partner=xxxx
Reason:
The local master's checkpoint file was previously full, that is it did not have sufficient
space to accommodate any job tracking records transmitted from the partner proxy
(XCF member xxxx). This condition has now been resolved and the partner proxy has
resumed transmitting job-tracking records via XCF to the local master.
System Action:
Action:
None.
4300 - 4399
4340I
XCF receiver started, Service=DSTRIG, Partner=xxxx
Reason:
An XCF proxy system's DSTRIG XCF service has connected to the local master. XCF data
set triggering between the local master and the partner proxy (XCF member xxxx) is now
active.
System Action:
Action:
None.
4341I
XCF receiver ended, Service=DSTRIG, Partner=xxxx
Reason:
A proxy system's DSTRIG XCF service connection to the local master has been closed.
XCF data set triggering between the local master and the partner proxy (XCF member
xxxx) is no longer active. This happens if the XCF DSTRIG service is stopped on either the
local master or the partner proxy is stopped, or if the partner proxy is shut down.
System Action:
Action:
None.
4300 - 4399
4342W
XCF receiver waiting for CKPT file space, Service=DSTRIG, Partner=xxxx
Reason:
The local master's checkpoint file is full, that is it cannot accommodate any data set
triggering records transmitted from the partner proxy (XCF member xxxx).
System Action:
The local master's XCF DSTRIG receiver waits for checkpoint space to become available
while other processing continues.
Action:
Most of the records on the master checkpoint file are usually job tracking records.
Therefore ensure that the local master's tracking processor is active.
4343I
XCF receiver resumed, CKPT file space available, Service=DSTRIG, Partner=xxxx
Reason:
The local master's checkpoint file was previously full, that is it did not have sufficient
space to accommodate any data set triggering records transmitted from the partner
proxy (XCF member xxxx). This condition has now been resolved and the partner proxy
has resumed transmitting data set triggering records via XCF to the local master.
System Action:
Action:
None.
4300 - 4399
4345I
XCF receiver started, Service=ROUTING, Partner=xxxx
Reason:
A proxy system's ROUTING XCF service has connected to the local master. XCF
subsystem request routing between the local master and the partner proxy (XCF
member xxxx) is now active.
System Action:
Action:
None.
4346I
XCF receiver ended, Service=ROUTING, Partner=xxxx
Reason:
A proxy system's ROUTING XCF service connection to the local master has been closed.
XCF subsystem request routing between the local master and the partner proxy (XCF
member xxxx) is no longer active. This happens if the XCF ROUTING service is stopped
on either the local master or the partner proxy is stopped, or if the partner proxy is shut
down.
System Action:
Action:
None.
4347E
XCF receiver buffer length xxxx too small for IAR, Service=ROUTING, Partner=yyyy
Reason:
System Action:
Action:
4300 - 4399
4348E
XCF receiver buffer xxxx invalid, Service=ROUTING, Partner=yyyy
Reason:
System Action:
Action:
4349E
High Availability Option or High Performance Option not installed
Reason:
A command was issued from a client (TSO/ISPF user or Work Station Server) to a proxy
subsystem with ROUTING set to MASTER. However, the target proxy subsystem does
not have the High Availability Option (HAO) or High Performance Option (HPO) installed,
and therefore cannot route the command to the master subsystem in its XCF group.
System Action:
Action:
This message should not normally appear, as a client is able to determine if the 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 master
if the local proxy is not authorized to do so. There may be a mismatch between the
version of the client and the proxy subsystem it is connected to. If unable to determine
the problem, contact CA Support.
4300 - 4399
4350E
XCF response xxxx invalid, Service=TRACKING
Reason:
System Action:
Action:
4351W
XCF proxy->master TRACKING service suspended, ESP master CKPT file full
Reason:
The master's checkpoint file is full, that is it cannot accommodate any Job-tracking
records transmitted from the local proxy.
System Action:
The local proxy's XCF TRACKING transmitter waits for a request from the master to
re-transmit the job tracking record(s).
Action:
Ensure that the master's tracking processor is active.
4352I
XCF proxy->master TRACKING service resumed
Reason:
The master's checkpoint file was previously full, that is it did not have sufficient space to
accommodate any job tracking records transmitted by the local proxy. This condition
has now been resolved and the local proxy has resumed transmitting job tracking
records via XCF to the master.
System Action:
Action:
None.
4300 - 4399
4353E
xxxx byte core request failed for XCF response IAR and IAE, Request=yyy
Reason:
There is not enough private area virtual storage for the transmission of the response to
a subsystem request issued from a master to a 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 master sends error response message 4354E to the issuer of the subsystem request.
Action:
If the problem persists, recycle the master with a larger region size.
4354E
Request RC=xxx, Insufficient core for yyyy byte response
Reason:
A subsystem request was issued to a master to a proxy via the XCF ROUTING service.
The subsystem request was processed but there was not enough virtual storage in the
remote address space private area for the response to be transmitted to the local
requesting 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:
Action:
If the problem persists, recycle the master with a larger region size.
4300 - 4399
4355E
XCF response xxxx invalid, Service=DSTRIG
Reason:
System Action:
Action:
4356W
XCF proxy->master DSTRIG service suspended, ESP master CKPT file full
Reason:
The master's checkpoint file is full, that is it cannot accommodate any data set triggering
records transmitted from the local proxy.
System Action:
The local proxy's XCF DSTRIG transmitter waits for a request from the master to
re-transmit the data set triggering record(s).
Action:
Most of the records on the master checkpoint file are usually job tracking records.
Therefore ensure that the master's tracking processor is active.
4357I
XCF proxy->master DSTRIG service resumed
Reason:
The master's checkpoint file was previously full, that is it did not have sufficient space to
accommodate any data set triggering records transmitted by the local proxy. This
condition has now been resolved and the local proxy has resumed transmitting data set
triggering records XCF to the master.
System Action:
Action:
None.
4300 - 4399
4360E
XCF ROUTING invalid, local ESP not master or proxy
Reason:
The local has been requested to route subsystem requests to the master in the XCF
group, but (the local system) is neither a master nor a proxy. This should never happen.
System Action:
The ROUTING XCF service is stopped if it is active.
Action:
4362W
Local ESP XCF ROUTING service {suspended|not active}{, command queued for later
execution|, no checkpoint space to queue command}
Reason:
A command was entered from a client (TSO, ISPF or Workstation Server) connected to a
CA WA ESP Edition proxy subsystem. The client has been set to instruct the connected
proxy to route subsystem requests to the master (via the MASTER operand of the ESP
command or the "ROUTING MASTER" subcommand). However, the proxy cannot route
the command to the master because its XCF ROUTING service is either suspended or is
not active.
If an OPER command was entered by a batch client requesting command queuing if the
target CA WA ESP Edition proxy subsystem is not active, then the command will be
stored in the proxy's checkpoint data set for later execution in the master when the XCF
ROUTING connection between the proxy and master becomes active. If there is
insufficient space in the proxy's checkpoint data set to store the command, then the
proxy subsystem will wait until checkpoint space becomes available before storing
command in the checkpoint data set.
System Action:
Action:
First enter the following command ROUTING LOCAL or
ROUTING L
This instructs the connected proxy to process subsystem requests locally rather than
route them to the master.
4300 - 4399
Then enter the following command XCF START SERVICE ROUTING or

XCF S S ROUTING
This starts the connected proxy's XCF ROUTING service.
Then enter the following command:
ROUTING MASTER or
ROUTING M
This instructs the connected proxy to route subsystem requests to the master.
Then re-enter the original command if it was not queued for later execution.
4363W
ESP master XCF ROUTING service not active{, command queued for later execution|,
no checkpoint space to queue command}
Reason:
command or the "ROUTING MASTER" subcommand). However, the proxy cannot route
the command to the master because the master's XCF ROUTING service is not active or
not registered.
stored in the proxy's checkpoint data set for later execution in the master when the XCF
ROUTING connection between the proxy and master becomes active. If there is
System Action:
Action:
Issue the following command to the master, either from a client connected DIRECTLY to
the master or via the MVS MODIFY command XCF START SERVICE ROUTING or XCF S S ROUTING
4300 - 4399
If message 4248 appears, the XCF ROUTING service was not registered by the master. In
this event, the following statement must be added to the ESPPARM statement of the
master XCF START SERVICE ROUTING
or
XCF S S ROUTING
Then the master must be recycled.
4364W
ESP master not active {suspended|not active}{, command queued for later
processing|, no checkpoint space to queue command}
Reason:
command or the "ROUTING MASTER" subcommand). However, the master is not active,
i.e. no active master is joined to the same XCF group as the proxy.
stored in the proxy's checkpoint data set for later processing in the master when the
XCF ROUTING connection between the proxy and master becomes active. If there is
System Action:
Action:
Start a master that includes in its ESPPARM file both a SYSPLEX statement that specifies
the same GROUP as the SYSPLEX statement of the connected proxy, and an "XCF START
SERVICE ROUTING" or "XCF S S ROUTING" statement.
4300 - 4399
4365W
XCF connection to ESP master closed, Service=ROUTING
Reason:
A command was entered from a client (TSO, ISPF or workstation server) connected to a
proxy. The client has been set to instruct the connected proxy to route subsystem
requests to the master (via the MASTER operand of the ESP command or the "ROUTING
MASTER" subcommand). The XCF connection between the proxy and master was closed
by the master while processing the command. This happens when, under the above
circumstances, the 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 master.
System Action:
Action:
To instruct the connected proxy to process subsystem requests itself rather than
attempt to route them to the master, enter the following subcommand from the client:
ROUTING LOCAL or ROUTING L If it is necessary for the proxy to route subsystem
requests to the master, restart the master and its XCF ROUTING service.
4366E
XCF response xxxx invalid, Service=ROUTING
Reason:
System Action:
Action:
4300 - 4399
4367I
XCF transmitter started, Service=SCOREBD, Partner=xxxx
Reason:
A remote proxy's XCF SCOREBD service receiver has connected to the local master's XCF
SCOREBD service transmitter. This occurs when both the local master's and the remote
proxy's XCF SCOREBD service has been started by an "XCF START SERVICE SCOREBD"
command. The master's scoreboard will henceforth be mirrored in the remote proxy
where it can be directly viewed by TSO users and work station servers connected to the
proxy via the subsystem interface. The remote is joined to system's XCF group as
member xxxx.
System Action:
Action:
None.
4368I
XCF transmitter ended, Service=SCOREBD, Partner=xxxx
Reason:
The local master's XCF SCOREBD service transmitter's connection with a remote 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
master or the remote proxy. The remote 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 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 master and the remote proxy. The remote is joined to system's XCF
group as member xxxx.
System Action:
Action:
None.
4300 - 4399
4369E
XCF SCOREBD data received invalid, Length=xxxx, Data='yyyy', Partner=zzzz
Reason:
The local proxy's XCF SCOREBD service receiver has received invalid data from the
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 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
proxy.
Action:
Attempt to re-establish the XCF SCOREBD service connection by issuing the "XCF START
SERVICE SCOREBD" command on the local proxy. If this does not resolve the problem,
call CA Support.
4370S
Invalid shadow manager function code xxxx
Reason:
System Action:
Action:
4300 - 4399
4371I
Entering shadow mode
Reason:
The local system has been started as an XCF shadow manager.
System Action:
The local shadow manager waits for a command to take over as the master in the XCF
group, or to terminate.
Action:
The local shadow manager can be set to the master with one of the following
commands:
XCF SET MEMBER xxxx MASTER
from any system in the XCF group
XCF T M xxxx M
from any system in the XCF group
SHADOW ASSUMEPRIMARY
from the local shadow
SHAD A
SHADOW SHUTDOWN RELINQUISH(xxxx)
from the master
SHAD SH R(xxxx)
from the master
SHADOW TAKEOVER
SHAD T
from the local shadow or where xxxx is the XCF member name of the local shadow
manager
4300 - 4399
4372I
Exiting shadow mode
Reason:
The local system has changed its status from shadow manager to master.
System Action:
The local system completes initialization and runs as the master in the XCF group.
Action:
None.
4373E
SHADOW TAKEOVER only valid in shadow mode
Reason:
Response to "SHADOW TAKEOVER", "SHAD T", "SHADOW ASSUMEPRIMARY" or "SHAD
A" command. The local system is already the master (primary the product in the XCF
group. Therefore setting to the master is invalid. The above commands may only be
issued from a shadow manager.
System Action:
Action:
None.
4374I
Shadow manager assuming ESP master (primary) role
Reason:
Response to "SHADOW TAKEOVER", "SHAD T", "SHADOW ASSUMEPRIMARY" or "SHAD
A" command. The local shadow manager has become the master in the XCF group.
System Action:
The local system completes initialization and runs as the master in the XCF group.
Action:
None.
4300 - 4399
4375E
{HOLD|RELINQUISH} option invalid for SHADOW LIST
Reason:
Response to "SHADOW LIST", "SHAD L", "SHADOW STATUS", "SHAD ST", "SHADOW" or
"SHAD" command.
System Action:
Action:
Re-enter the "SHADOW LIST", "SHAD L", "SHADOW STATUS", "SHAD ST", "SHADOW" or
"SHAD" command without the HOLD or RELINQUISH option.
4376E
SHADOW SHUTDOWN option {HOLD|RELINQUISH} only valid for ESP master
Reason:
Response to "SHADOW SHUTDOWN HOLD", "SHADOW SHUTDOWN RELINQUISH",
"SHAD SH H" or "SHAD SH R" command issued from a shadow manager.
System Action:
Action:
None.
4377E
Command syntax invalid
Reason:
A syntax error was encountered in a command issued on a shadow manager.
System Action:
Action:
If necessary, enter a valid shadow manager command.
4300 - 4399
4378E
Command xxxx not found
Reason:
Command xxxx issued from a shadow manager is not valid.
System Action:
Action:
If necessary, enter a valid shadow manager command.
4379S
Error obtaining a command, RC=nn
Reason:
An unexpected error occurred while the shadow manager was attempting to obtain a
command.
System Action:
The command thread terminated.
Action:
Contact CA Support.
4380I
SHADOW Command Options
Reason:
Response to "SHADOW HELP" or "SHAD H" command.
System Action:
Action:
None.
4300 - 4399
4381I
SHADGOAL Command Options
Reason:
Response to "SHADGOAL HELP" command.
System Action:
Action:
None.
4382I
No shadow goals defined
Reason:
Response to "SHADGOAL" or "SHADGOAL LIST" command.
System Action:
Action:
None.
4383I
Shadow goal definitions
Reason:
Response to "SHADGOAL" or "SHADGOAL LIST" command.
System Action:
Action:
None.
4300 - 4399
4384E
Shadow goal action(s) not specified
Reason:
Response to "SHADGOAL" command. A shadow manager shadow goal was defined
without specifying any actions to take after the 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 event identifier.

System Action:
Action:
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}
Reason:
Response to "ROUTING MASTER", "ROUTING M", "ROUTING LOCAL" or "ROUTING L"
command.
System Action:
Action:
None.
4300 - 4399
4386W
Local ESP XCF SCOREBD service not active
Reason:
A TSO/ISPF user connected to a proxy via the MVS subsystem interface is attempting to
view the scoreboard under the Consolidated Status Facility (CSF). However, the local
proxy's XCF SCOREBD service is not active, and therefore not receiving scoreboard data
from the master.
System Action:
Action:
If running under a client (TSO, ISPF, Work Station etc.), issue the "ROUTING" command.
If commands are being routed to the master, issue a "ROUTING LOCAL" command. Start
the local proxy's XCF SCOREBD service with an "XCF START SERVICE SCOREBD"
command. If commands were being routed to the master, restore this condition with a
"ROUTING MASTER" command.
4387W
ESP master XCF SCOREBD service not active
Reason:
view the scoreboard under the Consolidated Status Facility (CSF). However, the master's
XCF SCOREBD service is not active. Therefore the local proxy cannot access the
scoreboard.
System Action:
Action:
Start the master's XCF SCOREBD service with an "XCF START SERVICE SCOREBD"
command. This command can be issued by a client (TSO, ISPF, Work Station etc.)
connected to a proxy via the MVS subsystem interface, provided the proxy has an active
XCF ROUTING connection to the master, and subsystem commands are being routed to
the master. To determine if subsystem commands are being routed to the master, issue
a "ROUTING" command. To route subsystem commands to the master, issue a
"ROUTING MASTER" command.
4300 - 4399
4388W
ESP master not active
Reason:
view the scoreboard under the Consolidated Status Facility (CSF). However, the master
is not active. Therefore there is no scoreboard.
System Action:
Action:
Start the master and ensure that the XCF SCOREBD service is started via an "XCF START
SERVICE SCOREBD" command on both the master and the local proxy subsystems.
4389C
ROUTING Command Options
Reason:
Response to ROUTING HELP command.
System Action:
Displays ROUTING command options.
Action:
None.
4300 - 4399
4390I
Master fail|leave|quiesce shadow goal, After xxxx seconds{, Warn}{,
Command('yyyy')}{, Takeover|Trigger(zzzz)}
Reason:
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 master termination event occurs.
yyyy specifies an MVS command to issue xxxx seconds after the shadow goal
master termination event has occurred.
zzzz specifies an event to trigger xxxx seconds after the shadow goal master
termination event has occurred and after the local shadow manager has taken over
as the master.
System Action:
Action:
None.
4391W
Master fail|leave|quiesce shadow goal not defined
Reason:
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.
System Action:
Action:
None.
4300 - 4399
4392I
Master fail|leave|quiesce shadow goal deleted
Reason:
Response to "SHADGOAL DELETE MASTER(FAIL|LEAVE|QUIESCE)" command. The
specified shadow goal has been successfully deleted.
System Action:
Action:
None.
4393E
xxxx option invalid for SHADGOAL yyyy
Reason:
Operand xxxx is invalid when operand yyyy is specified in the SHADGOAL command.
System Action:
Action:
If necessary, re-issue the SHADGOAL command with valid operands. For a list of valid
SHADGOAL command options, enter: SHADGOAL HELP
4394E
SHADGOAL xxxx option missing
Reason:
A SHADGOAL command was issued with an option that requires that operand xxxx be
specified. However it (operand xxxx) was omitted.
System Action:
Action:
If necessary, re-issue the SHADGOAL command with valid operands. For a list of valid
SHADGOAL command options, enter: SHADGOAL HELP
4300 - 4399
4395I
Master fail|leave|quiesce shadow goal {takeover complete|event xxxx triggered}
Reason:
The 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 master and, if specified in the
shadow goal, triggered an event.
System Action:
Action:
None.
4396I
Master fail|leave|quiesce shadow goal activated, ESP master ended, Member=xxxx,
Group=yyyy
Reason:
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 master subsystem.
System Action:
The shadow goal action(s) will execute after the interval specified by the AFTER operand
of the SHADGOAL command expires.
Action:
None.
4300 - 4399
4397W
ESP master in failed|undefined|quiesced state {for xxxx seconds}
Reason:
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 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 master. If the active
shadow's goal's SHADGOAL command specified neither the TAKEOVER nor the
TRIGGER(yyyy) operands, processing continues.
Action:
If the local shadow manager's shadow goal has specified that it takeover as the 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 master, then probably either the master should be restarted, or
the local shadow manager should be explicitly requested to take over as the master (for
example via the "XCF SET MEMBER zzzz MASTER" command, where zzzz is the XCF
member name of the local shadow manager).
4300 - 4399
4398W
Master fail|leave|quiesce shadow goal command 'xxxx' issued
Reason:
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 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 master. If
the active shadow's SHADGOAL command specified neither the TAKEOVER nor the
TRIGGER(yyyy) operands, processing continues.
Action:
Depends on what command 'xxxx' was issued and whether or not the local shadow
manager's shadow goal specified that it takeover as the master (via the TAKEOVER or
TRIGGER(yyyy) operands of the SHADGOAL command). If the local shadow manager has
not taken over as the master, then probably either the master should be restarted, or
the local shadow manager should be explicitly requested to take over as the 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
Reason:
A master has been started externally while the local 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 master subsystem.
System Action:
The local shadow manager monitors the new master for its termination so that it (the
shadow manager) can respond according to its shadow goals.
Action:
None.
4400 - 4499
4400 - 4499
4400S
WLMCMD command code xxxx invalid
Reason:
System Action:
Action:
4401E
WLM command missing
Reason:
A WLM command was issued with no operands.
System Action:
Action:
For a list of valid WLM command options, enter: WLM HELP or WLM H or WLM ?
4402E
WLM xxxx command invalid
Reason:
A WLM command was issued with an invalid option xxxx.
System Action:
Action:
4400 - 4499
4403E
WLM xxxx not an initialization command
Reason:
A WLM statement in the ESPPARM file specifies option xxxx, which is invalid at
initialization.
System Action:
Action message 802A is issued to prompt for an END (to ignore the "WLM xxxx"
Action:
Respond to action message 802A and remove erroneous "WLM xxxx" statement from
ESPPARM file.
4404E
WLM xxxx object missing
Reason:
The WLM command with option xxxx requires one or more additional operands.
System Action:
Action:
4405E
WLM xxxx object yyyy invalid
Reason:
The WLM command with option xxxx specified an invalid option yyyy.
System Action:
Action:
4400 - 4499
4406I
WLM Command Options
Reason:
Response to "WLM HELP", "WLM H" or "WLM ?" command.
System Action:
Action:
None.
4407S
XENCLAVE function code xxxx invalid
Reason:
System Action:
Action:
4408E
XENCLAVE <function>, <error_description>
Reason:
An internal API request for a WLM enclave service has resulted in an error condition.
Internal logic error. Should not happen.
System Action:
Action:
4400 - 4499
4409S
XENCLAVE <function>, <error_description>
Reason:
System Action:
Action:
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>}
Reason:
A warning message describing the result of an API call to WLM.
System Action:
Action:
None.
4400 - 4499
4411E
Reason:
An error message describing the result of an API call to WLM.
System Action:
Action:
Usually none. The content of the message may indicate a specific action. If a problem
arises, call your software support personnel.
4412I
WLM DISPLAY CONNECTION
Reason:
Response to "WLM DISPLAY CONNECTION" or "WLM D C" command. Displays workload
manager (WLM) connection information.
System Action:
Action:
None.
4400 - 4499
4425W
Not connected to workload manager
Reason:
A WLM command was issued on the product that has not connected to the MVS
workload manager (WLM).
System Action:
Action:
Under the product, issue a WORKMGR operator command to connect to workload
manager, or add a WORKMGR statement to the ESPPARM initialization file and recycle
the job.
4426S
XWLMCONN parameter list not a valid WCRA
Reason:
System Action:
Action:
4427S
XENCLAVE parameter list not a valid WERA
Reason:
System Action:
Action:
4400 - 4499
4428S
XRESET parameter list not a valid WRRA
Reason:
System Action:
Action:
4430I
Connected to WLM, SST=xxxx, SSN=yyyy, Enclave support {en|dis}abled
Reason:
Response to "WORKMGR" statement in ESPPARM initialization file or "WORKMGR"
operator command, where xxxx specifies the product's subsystem type and yyyy
specifies the product's subsystem name. The product has connected to OS/390's
workload manager (WLM) as a work manager.
System Action:
Action:
None.
4400 - 4499
4431I
Reason:
An information message describing the result of an API call to WLM.
System Action:
Action:
None.
4440E
{Cannot {QUIESCE|RESET|RESUME} job xxxx, }System yyyy not {found| in goal mode}
Reason:
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:
Action:
If unable to determine the cause of the problem, call your software support personnel.
4400 - 4499
4441E
XRESET {GETMODE|QUIESCE|RESET|RESUME}, error_reason
Reason:
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 occurred.
System Action:
Action:
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 your software support personnel.
4442C
WLM DISPLAY STATUS
Reason:
Response to "WLM DISPLAY STATUS" or "WLM D ST" command issued to a subsystem
from a work station in line mode or from a TSO/ISPF session in page mode.
System Action:
Action:
None.
4400 - 4499
4443W
System xxxx not {found|in goal mode}
Reason:
Response to "WLM DISPLAY SYSTEM xxxx" or "WLM D S xxxx" command issued to a
subsystem from a work station in line mode or from a TSO/ISPF session in page mode.
Target system xxxx is not an active goal mode member of the sysplex.
System Action:
Action:
None.
4444C
WLM DISPLAY SYSTEM{S| xxxx}
Reason:
Response to "WLM DISPLAY SYSTEMS", "WLM D S", "WLM DISPLAY SYSTEM xxxx",
"WLM D S xxxx" command issued to a subsystem from a work station in line mode or
from a TSO/ISPF session in page mode. xxxx specifies a single system in the sysplex or
"ALL".
System Action:
Action:
None.
4446E
SYSEVENT REQSRMST Retcode=xxxx
Reason:
An unsuccessful attempt was made to obtain Workload Management (WLM) mode
status information from MVS. This should never happen.
System Action:
Action:
4400 - 4499
4447I
TOKEN(token) listid QNAME(qname) RNAME(rname) SCOPE(scope) CTLTYPE(ctltype)
REQTYPE(reqtype) USER(user) LOCKED(time) LASTLOCK(time) EXPIRY(time)
UNLOCKED(time)
Reason:
This message reports the status of a CPEENQ lock. The following 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:
Action:
If the UNLOCKED time is displayed, then the CPEENQ lock should be considered as
having been terminated.
4400 - 4499
4448I
ENQ's found: nnnn
Reason:
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:
Action:
None.
4449I
ENQ's displayed: nnnn
Reason:
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:
Action:
None.
4400 - 4499
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)
Reason:
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.
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.
System Action:
Action:
None.
4400 - 4499
4451I
--- BUFFERED TRACE MESSAGES ------------Reason:
When a CPEENQ request is issued with the tracing option enabled, the title above
precedes the listing of the queued trace messages.
System Action:
Action:
None.
4452I
<trace message>
Reason:
When a CPEENQ request is issued with the tracing option enabled, this message
contains one of the queued trace messages.
System Action:
Action:
None.
4453I
--- END OF BUFFERED TRACE MESSAGES ----Reason:
When a CPEENQ request is issued with the tracing option enabled, this message
immediately follows the listing of the queued trace messages.
System Action:
Action:
None.
4400 - 4499
4454I
<trace message>
Reason:
When a CPEENQ request is issued with the tracing option enabled, this is a trace
message prepared by program CYBXQ100.
System Action:
Action:
None.
4455I
Lock expired|flushed: USER(user) TOKEN(token) DEQ_RC(X'hhhhhhhh')
Reason:
A CPEENQ lock expired automatically or was flushed in response to a flush request.
System Action:
Action:
None.
4456I
Response truncated
Reason:
The response to a CPEENQ request was truncated because space ran out in the response
block.
System Action:
Action:
None or retry the request again later. If this persists, please notify your software
support personnel.
4400 - 4499
4457E
A subsystem request to NETNODE aaaa failed because of a network problem detected
by the Network Delivery Services
Reason:
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 a subsystem.
System Action:
Action:
Check the previous message. Retrying the request might succeed if the underlying
problem is transitory.
4458E
Subsystem error aaaa-bbbb
Reason:
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:
Action:
Look for recent or nearby messages that might account for this error. Retrying the
request might succeed if the underlying problem is transitory.
4400 - 4499
4459I
<trace message>
Reason:
When a CPEENQ request is issued with the tracing option enabled, this is a trace
message prepared by program CYBXQ101.
System Action:
Action:
None.
4460E
Reason:
A syntax error has been detected when scanning an input command.
System Action:
Action:
System routine IKJPARS returned error code nn.
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
respectively.
4400 - 4499
4461E
CPEENQ ERROR: Invalid xxxx specification: yyyy
Reason:
Argument xxxx in a CPEENQ command contains the invalid value yyyy.
System Action:
The command is not processed
Action:
4462E
CPEENQ ERROR: <error message>
Reason:
An error occurred during the processing of a CPEENQ command.
System Action:
Action:
If the syntax of the command is correct, decide how to proceed based on the error
message.
4463I
CPEENQ INFO: <informational message>
Reason:
This message contains diagnostic information about the outcome of a CPEENQ
command.
System Action:
Action:
None.
4400 - 4499
4464I
Locks flushed: xxxx
Reason:
Indicates the number of CPEENQ locks released in response to a CPEENQ FLUSHTSK or
CPEENQ FLUSHJOB command.
System Action:
Action:
None.
4465C
<command> Options
Reason:
Response to "<command> HELP" or "<command> ?" command.
System Action:
Displays <command> command options.
Action:
None.
4466W
<command>{ TRACE} set to LOGTRACE, active on LOGTRACE, restart request ignored
Reason:
Response to command: <command> RESTART{ TRACE} LOGTRACE The trace cannot be
restarted while it is set to LOGTRACE and active on the LOGTRACE file.
System Action:
The "<command> RESTART{ TRACE} LOGTRACE" command is ignored.
Action:
If the user wishes to spin the current LOGTRACE file and start a new LOGTRACE file, then
issue the following command: LOGTRACE RESTART Note that traces other than the
<command> trace may also be active on the LOGTRACE file.
4400 - 4499
4467I
<command>{ TRACE} <action>
Reason:
Response to one of the following commands:
<command> DISPLAY{ TRACE}
<command> SET{ TRACE}
<command> START{ TRACE}
<command> STOP{ TRACE}
<command> RESTART{ TRACE}
System Action:
The command is processed as described by <action> above.
Action:
None.
4468E
<command>{ TRACE} <error reason>
Reason:
Trace command <command> was issued with an error, as described by <error reason>.
System Action:
The trace command is ignored.
Action:
If necessary, re-issue the trace command specifying correct operand(s). To display trace
command <command> options, issue the command - <command> HELP or <command>
?
4400 - 4499
4469E
No space in ATR to store dependencies for object xxxxx
Reason:
There was insufficient space in the ATR to build the dependency links for an ApplStart
object.
System Action:
Action:
4470E
ApplStart can only be defined once
Reason:
More than one ApplStart object was defined in an application. Only one ApplStart per
application may be coded.
System Action:
Action:
Remove all but one ApplStart object.
4471W
zIIP API module CCS@ZE01 load failed, zIIP processing not available
Reason:
PARM=ZIIP was specified in the CA WA ESP Edition subsystem or Workstation Server JCL
procedure or system START command, requesting zIIP enablement. However, the CA
zIIP API service module could not be loaded into memory.
System Action:
The PARM=ZIIP specification in the CA WA ESP Edition subsystem or Workstation Server
JCL procedure or system START command is ignored and initialization continues without
zIIP enablement.
4400 - 4499
Action:
Attempt to determine why the CA zIIP API service module could not be loaded and
correct the problem if necessary.
4472W
zIIP enablement request rejected, no active zIIP processors
Reason:
PARM=ZIIP was specified in the CA WA ESP Edition subsystem or Workstation Server JCL
procedure or system START command, requesting zIIP enablement. However, the
system on which the CA WA ESP Edition subsystem or Workstation Server is running has
no active zIIP processors.
System Action:
The PARM=ZIIP specification in the CA WA ESP Edition subsystem or Workstation Server
JCL procedure or system START command is ignored and initialization continues without
zIIP enablement.
Action:
If the PARM=ZIIP specification is in the CA WA ESP Edition subsystem or WorkStation
Server JCL procedure then it may be removed if desired. However, leaving it there will
result in zIIP enablement if the CA WA ESP Edition subsystem or Workstation Server is
started when a zIIP processor becomes active in the system.
4473E
<@ZE TASK_INIT error message>
Reason:
This error message is formatted by CA zIIP Services when an attempt to initialize the CA
zIIP interface fails for a task.
System Action:
CA WA ESP Edition or Workstation Server continues processing without zIIP support for
the task.
Action:
This error should not normally occur. If it does, try using the message text to determine
why the CA zIIP interface could not be initialized for the task. If possible, correct the
error and recycle CA WA ESP Edition or Workstation Server. If you cannot find the cause
of the problem, call CA Support.
4400 - 4499
4474I
One of the following:
- zIIP processing not requested
- zIIP processing requested and enabled
- zIIP processing requested but no active zIIP processors in system
- zIIP processing requested but zIIP interface not available
- zIIP processing requested but zIIP interface not enabled
Reason:
Response to "DSPMODE" operator command.
System Action:
The "DSPMODE" command response is displayed as follows:
"zIIP processing not requested"
The CA WA ESP Edition OR Workstation Server started task JCL procedure or system
START command did not specify PARM=ZIIP.
"zIIP processing requested and enabled"

The CA WA ESP Edition or Workstation Server started task JCL procedure or system
START command specified PARM=ZIIP and the CA zIIP interface is available and enabled.
"zIIP processing requested but no active zIIP processors in system"

START command specified PARM=ZIIP but there are no active zIIP processors in the
system. CA WA ESP Edition or Workstation Server runs as if PARM=ZIIP was not
specified.
"zIIP processing requested but zIIP interface not available"

START command specified PARM=ZIIP but the CA zIIP interface module could not be
loaded into memory. CA WA ESP Edition or Workstation Server runs as if PARM=ZIIP was
not specified.
4400 - 4499
"zIIP processing requested but CA zIIP interface not enabled"

START command specified PARM=ZIIP but a CA zIIP service request failed. Message
4473E describing the error should appear in the CA WA ESP Edition or Workstation
Server JESMSGLG file. CA WA ESP Edition runs as if PARM=ZIIP was not specified.
Action:
If the message is "zIIP processing not requested", "zIIP processing requested and
enabled", or "zIIP processing requested but no active zIIP processors in system", no
action is necessary.
If the message is "zIIP processing requested but CA zIIP interface not available" or "zIIP
processing requested but CA zIIP interface not enabled", determine if there is a problem
and attempt to correct it.
4475E
zIIP request setting <value> invalid
Reason:
Response to "DSPMODE" operator command. The zIIP request internal setting <value> is
invalid. <value> specifies a 2 digit hexadecimal value.
System Action:
Action:
This error should not occur. If it does, call CA Support.
4476I
DSPMODE TASKS
Reason:
Response to {"DSPMODE TASKS(taskname{,taskname{,...}})"} operator command.
System Action:
TCB to SRB switch count, SRB to TCB switch count, CPU usage, zIIP processor usage and
zIIP eligibility are displayed for each selected task.
Action:
None.
4400 - 4499
4477I
No tasks match selection criteria
Reason:
Response to "DSPMODE TASKS(taskname{,taskname{,...}})" operator command.
System Action:
None.
Action:
If necessary, re-issue the "DSPMODE TASKS" operator command either specifying
"taskname" criteria that will match at least one task or omitting "taskname" criteria to
display all zIIP registered tasks.
4478C
DSPMODE CPUS
Reason:
Response to "DSPMODE CPUS" operator command.
System Action:
The number of defined and active normal CPUs, zAAP processors and zIIP processors in
the system are displayed.
Action:
None
4479E
@ZE GET_CPU_INFO RetCode=<RetCode>, RsnCode=<RsnCode>
Reason:
Response to "DSPMODE CPUS" operator command.
System Action:
A request for system CPU information failed with return code <RetCode> and reason
code <RsnCode>.
Action:
This error should not occur. If it does, call CA support.
4400 - 4499
4480W
CA zIIP interface not available|enabled
Reason:
Response to "DSPMODE TASKS" or "DSPMODE CPUS" operator command. The request
cannot be processed because the CA zIIP interface is not available or not enabled.
System Action:
Action:
Determine if the absence of a functional CA zIIP interface is a problem and attempt to
correct it.
4481I
No zIIP exclude task list
Reason:
Response to "DSPMODE EXCLUDE" operator command to display the zIIP exclude task
list. However, there is no zIIP exclude task list because either the target CA WA ESP
Edition subsystem or Workstation Server was not started with PARM=ZIIP or no ZIIPEXCL
command was specified in the ESPPARM or WSSPARM initialization file.
System Action:
Action:
None.
4482I
DSPMODE EXCLUDE
Reason:
Response to "DSPMODE EXCLUDE" operator command. The target CA WA ESP Edition
subsystem or Workstation Server was started with PARM=ZIIP and a ZIIPEXCL command
was specified in the ESPPARM or WSSPARM initialization file. The zIIP exclude task list is
displayed.
System Action:
4400 - 4499
Action:
None.
4483I
DSPMODE HELP
Reason:
Response to "DSPMODE HELP" operator command.
System Action:
The "DSPMODE" operator command options are displayed.
Action:
None.
4484E
ZIIPEXCL ignored, previously specified
Reason:
The PARM=ZIIP startup parameter was specified to request zIIP enablement and more
than one ZIIPEXCL command has been specified in the ESPPARM or WSSPARM
initialization file.
System Action:
The current ZIIPEXCL command is ignored because the first one was processed.
Action:
Under CA WA ESP Edition, respond to WTOR prompt message 802A. Remove all but one
ZIIPEXCL command from the ESPPARM or WSSPARM initialization file.
4485E
DSPMODE service requires APF authorization
Reason:
A non-APF program requested a DSPMODE (CA zIIP) service.
System Action:
The DSPMODE (CA zIIP) service request is ignored.
4400 - 4499
Action:
4486S
Invalid DSPMODE TCB request, already in TCB mode
Reason:
A request was made to switch from SRB mode to TCB mode. However, the requestor
was already in TCB mode.
System Action:
The job terminates abnormally with abend code U1204.
Action:
4487S
Second EVENTS table request, Task=<taskid>
Reason:
A task identified internally by <taskid> attempted to set the system EVENTS table entry
count for the second time.
System Action:
Action:
4488S
@ZE STIMERM,SET|CANCEL error, RtnCode=<RtnCode>{, RsnCode=<RsnCode>}
Reason:
An internal CA zIIP service timer request failed. <RtnCode> specifies the CA zIIP service
timer request return code. <RsnCode> specifies the CA zIIP service timer request reason
code. A reason code is only specified if the return code is 8.
System Action:
4400 - 4499
Action:
4489C
CPUSTATS HELP
Reason:
Response to CPUSTATS HELP command.
System Action:
The CPUSTATS command options are displayed.
Action:
None.
4490W
CPU statistics not started, CA zIIP interface not available|enabled
Reason:
Response to CPUSTATS ON command. CPU statistics collection cannot be started
because the CA zIIP interface is either not available or not enabled.
System Action:
CPU statistics collection is not started.
Action:
If the CPUSTATS ON command is specified in the ESPPARM or WSSPARM initialization
file and the CA zIIP interface is not available, then the CPUSTATS command may be
removed if desired, although leaving it there will not cause any harm. If the CA zIIP
interface is not enabled, call CA support.
4400 - 4499
4491I
CPU statistics {started|already active}
Reason:
Response to CPUSTATS ON command.
System Action:
CPU statistics collection is started if not already active.
Action:
None.
4492I
CPU statistics {stopped|already inactive}
Reason:
Response to CPUSTATS OFF command.
System Action:
CPU statistics collection is stopped if active.
Action:
None.
4400 - 4499
4493I
CPU statistics not active
Reason:
Response to CPUSTATS DISPLAY command. CPU statistics cannot be displayed because
CPU statistics collection has not been activated.
System Action:
Action:
If CPU statistics collection is required, issue the command - CPUSTATS ON. In client page
or line mode the above command must be prefixed with OPER.
In Workstation line mode the command must be prefixed with OPER if referencing the
target master or proxy subsystem and must not be prefixed with OPER if referencing
Workstation Server.
4494I
No CPU usage data {available yet|meeting selection criteria}
Reason:
Response to CPUSTATS DISPLAY command.
If no thread or task name filtering criteria were specified, then no CPU statistics are
available yet.
If thread or task name filtering criteria were specified, then no non-zero CPU statistics
meeting the criteria are available.
System Action:
Action:
None.
4400 - 4499
4495C
CPUSTATS
Reason:
Response to CPUSTATS DISPLAY command.
System Action:
CPU statistics are displayed.
Action:
None.
4497E
Invalid Request Block passed to CYBXO000: CPE Sysout Log File Services
Reason:
An internal logic error occurred while initiating a sysout trace file.
System Action:
The sysout trace file is not initialized.
Action:
This problem should never occur. If it does, contact CA Support.
4498E
LOGTRACE <error reason>
Reason:
The LOGTRACE command was issued with an error, as described by <error reason>.
System Action:
The LOGTRACE command is ignored.
Action:
If necessary, re-issue the LOGTRACE command specifying correct operand(s). To display
LOGTRACE command options, issue the command: LOGTRACE HELP or LOGTRACE ?
4500 - 4599
4499C
LOGTRACE Command Options
Reason:
Response to "LOGTRACE HELP" or "LOGTRACE ?" command.
System Action:
Displays LOGTRACE command options.
Action:
None.
4500 - 4599
4500I
xxxx {sysout class} {not set|set to y{, active on z}
Reason:
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.

System Action:
Action:
None.
4500 - 4599
4501I
xxxx {sysout class} set to y
Reason:
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.
Action:
None.
4502W
xxxx already active
Reason:
Response to "cccc START TRACE" or "cccc S TR" command. cccc is the command name.
xxxx is the sysout log/trace file identifier.
System Action:
Action:
None.
4500 - 4599
4503E
xxxx sysout class not set
Reason:
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:
Action:
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}
Reason:
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.
Action:
None.
4505I
xxxx stopped {on sysout class y}|{, DDNAME=x}
Reason:
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.
Action:
None.
4500 - 4599
4506I
xxxx spun to output {on sysout class y}|{, DDNAME=x}
Reason:
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.
Action:
None.
4507I
xxxx restarted on {sysout class y}|{, DDNAME=x}
Reason:
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:
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.
Action:
None.
4500 - 4599
4508E
xxxx file open error
Reason:
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:
Action:
Check if the JES spool file is full.
4509E
<sysout_log/trace_file_error_message>
Reason:
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.
Action:
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.
4500 - 4599
4510W
xxxx not active
Reason:
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 performed as sysout
log/trace file xxxx is not active.
System Action:
Action:
None.
4511E
XSYSOUT interface not initialized
Reason:
System Action:
Action:
4512E
XSYSOUT token xxxx invalid
Reason:
System Action:
Action:
4500 - 4599
4517E
Load failed for xxxx, RC=X'nnnn'
Reason:
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.
Action:
Ensure that the specified module resides in the Workstation Server's load library and
retry starting the Workstation Server. If the problem persists, contact CA Support.
4518W
Redundant prefix argument: xxxx
Reason:
The Workstation Server received a message with a duplicate prefix argument xxxx.
System Action:
Workstation Server ignores the input.
Action:
Re-enter the message with no duplicate prefix arguments. If the problem persists,
contact CA Support.
4519W
Invalid prefix argument: xxxx
Reason:
The Workstation Server received a message with an invalid value for prefix argument
xxxx.
System Action:
Action:
Re-enter the message with valid prefix arguments. If the problem persists, contact CA
Support.
4500 - 4599
4520I
IAMHERE
Reason:
Normal response to an RUTHERE command. Confirms the presence of the program that
responded.
System Action:
Action:
None.
4521E
SUBSCRIB syntax invalid
Reason:
Response to an incorrectly formulated SUBSCRIB command.
System Action:
Action:
4522E
Subscription token already registered: xxxx
Reason:
A SUBSCRIB command attempted to create a new subscription but specified an
already-used subscription token.
System Action:
Action:
Specify a different subscription token and retry.
4500 - 4599
4523E
Subscription token not registered: xxxx
Reason:
A command attempted to modify an existing subscription but specified an unknown
subscription token.
System Action:
Action:
Specify the correct subscription token and retry.
4524E
Not logged onto remote WSS <ip>:CA Portal
Reason:
A user connected to a Consolidated Workstation Server has issued a command to a
remote Workstation Server that is connected to the Consolidated Workstation Server.
However, the user has not yet logged onto the remote Workstation Server. <ip>
specifies the IP address of the remote Workstation Server. CA Portal specifies the TCP
port number of the remote Workstation Server.
System Action:
Action:
Logon to the remote Workstation Server and re-issue the command.
4525E
Client issued command without prior logon Subsystem WSS IP address: xx prior logon
Reason:
A command could not be executed because the client did not first log on through the
command channel.
System Action:
Action:
Correct the IP address or log on before retrying the failed command.
4500 - 4599
4527E
Invalid number of data spaces in xxxx request: nn
Reason:
An invalid value nn was specified in a xxxx request.
System Action:
The request is rejected
Action:
4528E
TCBTOKEN failed, RC=X'nnnn'
Reason:
The TCBTOKEN function required to establish the environment necessary for using a
data space failed with return code 'nnnn'.
System Action:
Action:
Notify CA Support.
4529E
DSPSERV CREATE failed, RC=X'nnnn', Reason=X'nnnn'
Reason:
The DSPSERV function required to establish the environment necessary for using a data
space failed with return code 'nnnn'.
System Action:
Action:
Notify CA Support.
4500 - 4599
4530E
DSPSERV DELETE failed, RC=X'nnnn', Reason=X'nnnn'
Reason:
The DSPSERV function required to release the environment necessary for using a data
System Action:
Action:
If the problem persists, notify CA Support.
4531E
ALESERV ADD failed, RC=X'nnnn'
Reason:
The ALESERV function required to establish the environment necessary for using a data
System Action:
Action:
Notify CA Support.
4532E
ALESERV DELETE failed, RC=X'nnnn'
Reason:
The ALESERV function required to release the environment necessary for using a data
System Action:
Action:
4500 - 4599
4533I
Status channel termination triggered
Reason:
A STATCHAN END or STOP command was successfully processed.
System Action:
Action:
None.
4534W
The target of this command is unknown.
Reason:
Response to a command whose Subsys() routing argument refers to an unknown
subsystem.
System Action:
Action:
Correct the Subsys() argument or ensure that the Workstation Server is connectible to
the specified target subsystem.
4535E
XDNR, GETHOSTID failed, RC=X'nnnn'
Reason:
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:
Action:
Retry starting the Workstation Server. If the problem persists, contact CA Support.
4500 - 4599
4536E
ADD_ESDW failed, RC=X'nnnn'
Reason:
The Workstation Server is starting up and failed to create and initialize a vital control
block. The return code is 'nnnn'.
System Action:
Action:
Ensure that the product is active and retry starting the Workstation Server. If the
problem persists, contact CA Support.
4537I
Response channel successfully established
Reason:
A RESPCHAN command was successfully processed.
System Action:
Action:
None.
4538I
Response channel ending
Reason:
The task dedicated to a response channel is terminating.
System Action:
Action:
None.
4500 - 4599
4539E
Port nn already has a response channel
Reason:
A RESPCHAN command was issued for a port which was specified in a previous
successful RESPCHAN command.
System Action:
Action:
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
Reason:
A RESPCHAN END or STOP command was successfully processed.
System Action:
Action:
None.
4541E
Port nn is not a command channel
Reason:
A STATCHAN or RESPCHAN command was issued for a port which is already a status or a
response channel.
System Action:
Action:
If the specified port was wrong, correct it and resubmit the command.
4500 - 4599
4542E
No response channel defined
Reason:
A RESPCHAN END command was issued through a command channel which has no
associated response channel.
System Action:
Action:
None.
4543E
RESPCHAN requires TCP/IP
Reason:
A RESPCHAN command was issued to a Workstation Server whose communication
protocol is not TCP/IP.
System Action:
Action:
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)
Reason:
A STATCHAN or RESPCHAN command was issued for a port which owns and controls a
status or a response channel.
System Action:
Action:
Issue the command through a different channel, or terminate the channel's associated
channels and retry.
4500 - 4599
4545E
Invalid TIRA address: xxxxxxxx
Reason:
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.
Action:
This is caused by an internal logic error. Notify your software support personnel.
4546E
WSSPROXY command discarded
Reason:
A WSSPROXY command has been discarded because the client has not yet passed a
USER or LOGON command through WSSPROXY.
System Action:
Action:
Pass a USER or LOGON command through WSSPROXY before passing other commands
through WSSPROXY.
4547E
WSSPROXY parameter missing: xxxxx
Reason:
The WSSPROXY parameter xxxxx has been omitted.
System Action:
Action:
Supply the missing parameter and retry.
4500 - 4599
4548E
WSSPROXY requires a response channel
Reason:
A WSSPROXY command was issued before the establishment of a response channel.
System Action:
Action:
Establish a response channel and retry.
4549E
WSSPROXY contains a syntax error
Reason:
The Workstation Server received a badly-formed WSSPROXY command.
System Action:
Action:
Make the necessary corrections and retry.
4550I
WSSPROXY passing message to a new proxy task
Reason:
The Workstation Server is starting a new proxy task to log on a new user.
System Action:
Action:
None.
4500 - 4599
4551I
WSSPROXY passing message to a new proxy task with self-LOGON
Reason:
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.
System Action:
Action:
None.
4552I
WSSPROXY passing message to an existing proxy task
Reason:
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.
System Action:
Action:
None.
4553E
WSSPROXY parameter badly formed: xx
Reason:
The length or the format of the xx WSSPROXY parameter is incorrect.
System Action:
Action:
4500 - 4599
4554E
WSSPROXY version is invalid: x
Reason:
The version x specified in the P1 WSSPROXY parameter is invalid.
System Action:
Action:
4555I
Logon successful P1(aaaaaaaa) P2(bbbbbbbb) P3(cccccccccccccccc)
LOGONTYPE(dddddd)
Reason:
A proxy command task successfully logged on a user.
System Action:
Action:
None.
4556E
Command cannot be routed to a remote WSS: xxxxxxxx
Reason:
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.
System Action:
Action:
None.
4500 - 4599
4557I
WMSTATUS IPADDR(aa.aa.aa.aa) PORT(bbbb) WM(cccc) STATUS(dddddd)
Reason:
This message reports the status of the system whose Workstation Server has the stated
IP address and port.
System Action:
Action:
None.
4558I
WSSDOMN IPADDR(aa.aa.aa.aa) PORT(bbbb) WM(cccc)
Reason:
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.
System Action:
Action:
None.
4559E
Error in LIKE argument or its usage
Reason:
This message is a response to the USER or LOGON command. The command specified an
incomplete or badly-formed LIKE argument.
System Action:
Action:
Correct the LIKE argument and retry.
4500 - 4599
4560E
LIKE cannot be specified for a Workstation Server that already serves as a model
Reason:
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:
Action:
Specify a different LIKE argument and retry.
4561E
LIKE cannot be specified for the home Workstation Server
Reason:
LIKE argument to log on to the Workstation Server's home subsystem.
System Action:
Action:
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
Reason:
LIKE argument that represents a subsystem not in the domain of the Workstation
Server.
System Action:
Action:
4500 - 4599
4563E
LIKE specifies a subsystem to which the user is not logged on
Reason:
LIKE argument that represents a Workstation Server to which the user is not yet
currently logged on.
System Action:
Action:
Log on to the subsystem specified in the LIKE argument and retry.
4564E
LIKE contains a circular specification
Reason:
LIKE argument that represents the same Workstation Server to which the user is trying
to log on.
System Action:
Action:
4500 - 4599
4565W
The subsystem name for xx has been corrected from yy to zz
Reason:
The 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 Server is xx.
System Action:
Action:
Correct the configuration data for the next run of the Workstation Server.
4566I
TRACELOG opened
Reason:
CYBES065 has issued an open request for the TRACELOG file.
System Action:
Action:
None.
4567I
TRACELOG closed
Reason:
CYBES065 has issued a close request for the TRACELOG file.
System Action:
Action:
None.
4500 - 4599
4568E
INIT_ESDW failed, RC=X'nnnn'
Reason:
The Workstation Server is starting up and failed to initialize a vital control block. The
return code is 'nnnn'.
System Action:
Action:
Check if any other error messages or warnings were issued before this message. If the
4569E
WSS Configuration failed, RC=X'nnnn'
Reason:
The Workstation Server is starting up and detected one or more errors in the provided
configuration data. The return code is nnnn.
System Action:
Action:
Correct all reported errors and restart the Workstation Server.
4570I
WSS parameters successfully tested
Reason:
The Workstation Server has successfully tested the syntax of all the statements in the
WSSREMOT data set.
System Action:
Workstation Server terminates.
Action:
Restart the Workstation Server without the TESTPARMS keyword.
4500 - 4599
4571I
nnn Remote WSS connections have been made, currently mmm are/is active
Reason:
Continuation to message 0472 display of requested information.
System Action:
Action:
None.
4572I
ESDW added Subsystem WSS IP address: nn
Reason:
The Workstation Server successfully created the control block it requires in order to
keep track of a system. The IP address and port number of a Workstation Server
dedicated to that Workload Manager are displayed in this message.
System Action:
Action:
None.
4573I
ESDW deleted Subsystem WSS IP address: nn
Reason:
The Workstation Server successfully deleted the control block it requires in order to
keep track of a system. The IP address and port number of a Workstation Server
dedicated to that Workload Manager are displayed in this message.
System Action:
Action:
None.
4500 - 4599
4574E
Load failed for xxxx, RC=X'nnnn'
Reason:
The Workstation Server is starting up and failed to load a vital program whose name is
xxxx. The return code is 'nnnn'.
System Action:
Action:
Ensure that the specified module resides in the Workstation Server's load library and
retry starting the Workstation Server. If the problem persists, contact CA Support.
4575I
<variable> = <value> : <variable description>
Reason:
This message reports the value of a Workstation Server variable.
System Action:
Action:
None.
4576E
DSPSERV EXTEND failed, RC=X'nnnn', Reason=X'mmmm'
Reason:
The DSPSERV function required to extend a data space failed with return code 'nnnn'.
System Action:
Action:
4500 - 4599
4577I
Start of processing, command file = xxxx
Reason:
The Workstation Server has begun processing the command file allocated to ddname
xxxx.
System Action:
Action:
None.
4578I
OK Command=xxxx, File=yyyy, Line#=zzzz
Reason:
The Workstation Server has successfully processed the command xxxx on line zzzz of the
file allocated to ddname yyyy.
System Action:
Action:
None.
4579E
Invalid command syntax, File=xxxx, Line=yyyy
Reason:
The Workstation Server encountered a syntax error in the command on line yyyy of the
file allocated to ddname xxxx.
System Action:
Action:
Correct the command on line xxxx of file yyyy.
4500 - 4599
4580E
Command xxxx not found, File=yyyy, Line=zzzz
Reason:
The Workstation Server encountered a command xxxx that it does not recognize as
valid, in line zzzz of the file allocated to ddname yyyy.
System Action:
Action:
Correct the command on line zzzz of file yyyy.
4581E
xxxx
Reason:
An attempt by the Workstation Server to open the WSSREMOT file failed. Message xxxx
should explain the reason for the failure.
System Action:
Action:
Determine the problem from message xxxx and correct it.
4582I
End of processing, command file = xxxx
Reason:
The Workstation Server has finished processing the command file allocated to ddname
xxxx.
System Action:
Action:
None.
4500 - 4599
4583E
WSSREMOT data rejected
Reason:
The Workstation Server rejected one or more statements in the WSSREMOT data set.
System Action:
Action:
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
Reason:
The Workstation Server failed with return code yyyy while performing operation xxxx
for the system whose Workstation Server listens to IP address and port zzzz.
System Action:
Action:
Examine earlier error messages. If the problem persists, contact CA Support.
4585E
REMOTE cannot be executed without CYBES111
Reason:
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.
Action:
Verify whether the Workstation Server has been correctly installed.
4500 - 4599
4586E
REMOTE requires TCP/IP
Reason:
The Workstation Server cannot execute the REMOTE command if the Workstation
Server's communication protocol is not TCP/IP.
System Action:
Action:
If it is desirable to do so, make TCP/IP the Workstation Server's communication
protocol.
4587E
REMOTE command error
Reason:
The Workstation Server detected an error while parsing the REMOTE command.
System Action:
Action:
Verify any earlier error messages and correct the REMOTE command.
4588E
REMOTE host name not resolved: xxxx
Reason:
The Workstation Server was unable to resolve the host name specified in a REMOTE
command.
System Action:
Action:
Correct the host name specified in the REMOTE command.
4500 - 4599
4589E
REMOTE command specifies local WSS <host>:CA Portal
Reason:
The Workstation Server's host and port are identical to the host and port specified in a
REMOTE command.
System Action:
Action:
Correct the host and port of the REMOTE command.
4590E
Duplicate REMOTE command for WSS <host>:CA Portal
Reason:
A REMOTE command specifies a host and port identical to those specified in a previous
REMOTE command.
System Action:
Action:
Ensure that no two REMOTE commands specify the same host and port.
4591E
Duplicate PRIMARY command
Reason:
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.
Action:
Ensure that only one PRIMARY command is passed to the Workstation Server.
4500 - 4599
4592E
PRIMARY command error
Reason:
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.
Action:
Verify any earlier error messages and correct the PRIMARY command.
4593W
RWSSaaaa bbbb, id=cc, Task=dddddddd, eeee connection closed, task terminating.
Reason:
The connection from a Workstation Server to a remote Workstation Server has been
closed and the task which maintained that connection is terminating.
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.
Action:
None.
4500 - 4599
4594E
RWSSaaaa bbbb, id=cc, Task=dddddddd, eeee ff failed
Reason:
Operation ff failed in a remote Workstation Server task.
dddddddd is the address of the task's TEE
eeee is the task's function.
System Action:
Action:
None.
4595I
RWSSaaaa bbbb, id=cc, Task=dddddddd, eeee terminating
Reason:
A remote Workstation Server task is terminating.
System Action:
Action:
None.
4500 - 4599
4596I
RWSSaaaa bbbb, id=cc, Task=dddddddd, eeee received message ff from remote WSS
Reason:
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.
System Action:
The remote Workstation Server task decides whether to resume processing.
Action:
None.
4597I
RWSSaaaa bbbb, id=cc, Task=dddddddd, eeee connected
Reason:
A remote Workstation Server task has established a connection to a remote
Workstation Server.
System Action:
Action:
None.
4500 - 4599
4598I
RWSSaaaa bbbb, id=cc, Task=dddddddd, eeee trying to connect every ff seconds
Reason:
A remote Workstation Server task has not yet established a connection to a remote
Workstation Server and is trying every ff seconds.
System Action:
Action:
None.
4599I
RWSSaaaa bbbb, id=cc, Task=dddddddd, eeee logged on
Reason:
A remote Workstation Server task has successfully logged on to a remote Workstation
Server.
System Action:
Action:
None.
4600 - 4699
4600 - 4699
4600I
RWSSaaaa bbbb, id=cc, Task=dddddddd, eeee discarding a message
Reason:
A remote Workstation Server response task is discarding a message received from a
remote Workstation Server.
System Action:
Action:
None.
4601E
Invalid RWSSST type
Reason:
A remote Workstation Server task was initiated with an invalid task function.
System Action:
The remote Workstation Server task terminates.
Action:
4600 - 4699
4602E
Time-out while waiting for response from remote WSS
Reason:
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.
Action:
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
Reason:
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:
Action:
Examine earlier error messages and correct the rejected command.
4604E
Remote WSS cannot currently be reached
Reason:
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:
Action:
The user may retry.
4600 - 4699
4605E
Message for remote WSS is too large
Reason:
The Workstation Server cannot pass a command to a remote Workstation Server
because the message is too large.
System Action:
Action:
Consider dividing the message.
4606I
Proxy task xxxx starting for user yyyy
Reason:
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.
System Action:
Action:
None.
4607I
Proxy task xxxx ending for user yyyy
Reason:
Proxy task number xxxx for user yyyy is ending.
System Action:
Action:
None.
4600 - 4699
4608I
<variable> = <value> : <variable description>
Reason:
This message reports the value of a Workstation Server variable.
System Action:
Action:
None.
4609E
Command error, File=xx, Line#=yy
Reason:
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.
Action:
Verify any earlier error messages and correct the REMOTE command.
4610I
First scoreboard scan completed. STOKEN(xx)
Reason:
The Workstation Server has completed its first scoreboard scan for the status-update
subscriptions whose STOKENs are listed.
System Action:
Action:
None.
4600 - 4699
4611E
HOME host name not resolved: xx
Reason:
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:
Action:
Correct the host if it is erroneous and retry starting the Workstation Server. If the
4612E
CREATE_KEY failed, KEY=X'aa', RC=X'bb'
Reason:
The Workstation Server rejected the encryption key aa with return code bb.
System Action:
Action:
Correct the key if it is erroneous and retry starting the Workstation Server. If the
4613I
LOGON encryption enabled
Reason:
The Workstation Server is able to accept encrypted client logons.
System Action:
Action:
None.
4600 - 4699
4614E
ENCRYPT_BUFFER failed, RC=X'aa'
Reason:
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.
Action:
4615E
ENCRYPT_BUFFER failed, RC=X'aa'
Reason:
The Workstation Server failed to encrypt a change-of-direction message before sending
it to a client. The return code is aa.
System Action:
Action:
4616E
DECRYPT_BUFFER failed, RC=X'aa'
Reason:
The Workstation Server failed to decrypt a message received from a client. The return
code is aa.
System Action:
Action:
4600 - 4699
4617E
ENCRYPTTYPE and KEY are corequisite parameters
Reason:
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.
Action:
4618E
CREATE_KEY failed, KEY=X'aa', RC=X'bb'
Reason:
CYBESLMI rejected the encryption key aa with return code bb.
System Action:
CYBESLMI fails to start up.
Action:
Correct the key if it is erroneous and retry running CYBESLMI.
4619E
Encryption|Decryption error, RC=X'aa'
Reason:
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:
Action:
This is caused by an internal logic error. Notify your software support personnel.
4600 - 4699
4638I
File xxx locked{: LockToken(yyy)}
Reason:
The Workstation Server or z/OS Agent 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. The LockToken is only displayed by a z/OS Agent.
System Action:
Action:
None.
4639E
File xxx in use
Reason:
The Workstation Server or z/OS Agent 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:
Action:
None or retry.
4640I
File xxx unlocked{: LockToken(yyy)}
Reason:
The Workstation Server or z/OS Agent has successfully issued a DEQ to release a prior
exclusive ENQ on file xxx. The file thus becomes available for update by another user.
The LockToken is only displayed when LockToken is specified in the PUTFILE command.
System Action:
Action:
None.
4600 - 4699
4641E
File xxx not previously locked
Reason:
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:
Action:
Issue the GETFILE command with the LOCK keyword before using the PUTFILE command
to update and unlock the file.
4642E
UNDOLOCK: xxx
Reason:
Error xxx occurred while processing the UNDOLOCK command.
System Action:
Action:
Correct and resubmit the command.
4643E
Data set type not supported for PUTFILE
Reason:
A PUTFILE command specified a data set name beginning with LIB-, PAN-, or ROS-. Data
sets in these proprietary formats can only be read by the product. Writing to them is not
possible.
System Action:
Action:
Do not attempt to upload to CA-Librarian, CA-Panvalet or CA-Roscoe data sets.
4600 - 4699
4644I
'UNDOLOCK aaa' submitted by xxx yyy at yyyymmdd-hhmmss
Reason:
The UNDOLOCK command was submitted by an operator or user yyy at the date and
time.
System Action:
Action:
None.
4645I
File xxx.yyy.zzz(aaa) unlocked by bbb at yyyymmdd-hhmmss
Reason:
A data set locked by the indicated user has been unlocked in response to an UNDOLOCK
command entered by an operator.
System Action:
Action:
None.
4646I
Locks released = 999
Reason:
Shows the total number of data set locks released as a result of an UNDOLOCK
command.
System Action:
Action:
None.
4600 - 4699
4647I
List of Currently Locked Files
Reason:
This is header line one for the display of locked data sets to be shown in response to the
LISTLOCK command.
System Action:
Action:
None.
4648I
User ID Task Date-Time File
Reason:
This is header line two for the display of locked data sets to be shown in response to the
LISTLOCK command.
System Action:
Action:
None.
4649I
Userid Lockid Taskid yyyymmdd hhmmss xxx.yyy.zzz(aaa)
Reason:
Locked data set information shown in response to a LISTLOCK command entered by an
operator.
System Action:
Action:
None.
4600 - 4699
4650I
Locks currently held = 999
Reason:
Total count of locked data sets shown in response to a LISTLOCK command entered by
an operator.
System Action:
Action:
None.
4651I
Lock not released because of PUTFILE in progress = 999
Reason:
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:
Action:
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 complete it. If there is no alternative, use the UNDOLOCK
with the FORCE keyword.
4600 - 4699
4652E
User xxxxxxxx is not authorized to execute command yyyyyyyy
Reason:
A SAF security check has determined that the indicated user is not authorized to issue
the indicated command.
System Action:
Action:
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{: LockToken(aaa)}
Reason:
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. The
LockToken is only displayed by a z/OS Agent.
System Action:
Action:
None.
4654I
Operator command received: xxx
Reason:
An operator has appended command xxx to an MVS MODIFY command and the
Workstation Server has received it.
System Action:
Action:
None.
4600 - 4699
4655E
WSSCTL command missing
Reason:
A "WSSCTL" command was issued without any parameters.
System Action:
Action:
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
Reason:
The command aaa was submitted by an operator or user ccc at the date and time
shown.
System Action:
Action:
None.
4657E
WSSCTL xxxx command invalid
Reason:
The parameter immediately following "WSSCTL" in a "WSSCTL" command is invalid.
System Action:
Action:
Enter a "WSSCTL" command with valid parameters. Or enter "WSSCTL HELP", "WSSCTL
H" or "WSSCTL ?" for a list of "WSSCTL" command options.
4600 - 4699
4658E
WSSCTL xxxx not an initialization command
Reason:
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:
Action:
Remove the "WSSCTL" command from the initialization parameters.
4659E
WSSCTL xxxx object missing
Reason:
A "WSSCTL xxxx" command was entered that required at least one additional
parameter.
System Action:
Action:
Enter the "WSSCTL xxxx" command with valid parameters. Or enter "WSSCTL HELP",
"WSSCTL H" or "WSSCTL ?" for a list of "WSSCTL" command options.
4600 - 4699
4660E
WSSCTL xxxx object yyyy invalid
Reason:
Parameter 'yyyy' in the command "WSSCTL xxxx yyyy" is invalid for the command
"WSSCTL xxxx".
System Action:
Action:
Enter a "WSSCTL xxxx" command with valid parameters. Or enter "WSSCTL HELP",
"WSSCTL H" or "WSSCTL ?" for a list of "WSSCTL" command options.
4661C
WSSCTL Command Options
Reason:
Response to a "WSSCTL HELP" command. Lists all valid "WSSCTL" command options.
System Action:
Action:
None.
4600 - 4699
4662E
SET TRACE SYSOUT is not compatible with the TRACELOG DD statement
Reason:
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.
Action:
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
Reason:
A SAF security check has determined that the indicated user is not authorized to issue
the indicated command.
System Action:
Action:
If it is necessary for you to issue the command, ask your Administrator to grant you
OPER authority.
4600 - 4699
4664E
DDNAME xxxx is not a SYSOUT data set
Reason:
The DD statement with DDNAME xxxx should designate a SYSOUT data set.
System Action:
Processing stops.
Action:
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
Reason:
Error occurred while scanning command received from Workstation.
System Action:
Action:
Depending on RC=nn different actions could be considered. When
nn=12 - Invalid command structure. Transmission error is likely, Check init

parameters. Try again.
respectively.
4600 - 4699
4666E
Length xxxx exceeds allowed limit of yyyy
Reason:
The "LENGTH" parameter of a "WSSMSG" command is too high or the text of a
"WSSECHO" command is too long.
System Action:
Action:
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
Reason:
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.
Action:
Respecify the PDS dataset name with a valid member name in the form of
xxx.yyy.aaa(mbrname) and retry the operation.
4668S
Inconsistent version between ESP subsystem and Workstation Server
Reason:
The version of sub-system is not the same as the version of Workstation Server.
System Action:
The Workstation Server is ABEND with code 600.
Action:
Install the same version of sub-system and Workstation Server.
4600 - 4699
4669S
Inconsistent version between ESP subsystem and Workstation Server
Reason:
The version of the subsystem is not the same as the version of the Workstation Server.
System Action:
The Workstation Server is ABEND with code 600.
Action:
Install the same version of the subsystem and the Workstation Server.
4670E
Missing parameter: xxxx
Reason:
The required parameter xxxx was omitted from a PUTFILE command.
System Action:
The PUTFILE command is rejected.
Action:
Resubmit the command with the missing parameter.
4671E
File xxxx was forcibly unlocked before PUTFILE began to write{: LockToken(yyy)}
Reason:
The PUTFILE command processor was about to update the target data set, but the lock
on the target data set was removed some time after the PUTFILE command began
executing. The loss of the lock is probably due to an UNDOLOCK command. The
LockToken is only displayed when LockToken is specified in the PUTFILE command.
System Action:
Processing of the PUTFILE command comes to an end. The system log should contain
message 4644 or 4645, indicating that a command was issued to undo the lock on the
target data set.
Action:
Decide whether to start over, that is retrieve the data set and re-apply changes.
4600 - 4699
4672E
Inconsistent version of Scoreboard data
Reason:
When processing LCSF command, it is found that the version of sub-system is not the
same as the version of Workstation Server.
System Action:
Return error message without retrieving any CSF data.
Action:
Install the same version of sub-system and Workstation Server.
4673E
Scoreboard data received invalid
Reason:
When processing LCSF command, it is found that Scoreboard data is invalid. The most
possible reason is that sub-system was not started with PARM=RELOAD
System Action:
Return error message without retrieving any more CSF data.
Action:
Restart the sub-system with PARM=RELOAD option.
4695E
The scoreboard cannot presently be scanned
Reason:
Response to the SUBSCRIB command when the Workstation Server is unable to
immediately perform a scoreboard scan. The SUBSCRIB request is rejected.
System Action:
Action:
Retry the SUBSCRIB command at a later time.
4600 - 4699
4696E
Invalid response from remote WSS xxx
Reason:
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:
Action:
This is caused by an internal logic error. If the problem persists, contact CA Support.
4697I
SIGNOFF COMPLETE
Reason:
Response to the SIGNOFF command.
System Action:
Action:
None.
4600 - 4699
4698E
RWSSaaaa (bbbb), id=cc, Task=dddddddd, eeee logon retry disabled: ffff
Reason:
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.
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.
Action:
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
Reason:
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.
Action:
If any error messages precede this message, make the necessary correction, and stop
and restart the Consolidated Workstation Server.
4700 - 4799
4700 - 4799
4700E
Reason:
There was insufficient space in the ATR to store data for a BDC_Job jjjj in application
aaaa.
System Action:
Action:
4701E
BDC_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4702E
Reason:
System Action:
Action:
4700 - 4799
4703E
Reason:
System Action:
Action:
4704E
BDC_JOB xxxx in Appl yyyy, missing ABAPname
Reason:
Each BDC_JOB requires an ABAPname to be specified indicating what work is to be done
System Action:
Action:
4700 - 4799
4705E
Reason:
System Action:
Action:
job.
4706E
Reason:
System Action:
Action:
4700 - 4799
4707E
Reason:
System Action:
Action:
4708E
Reason:
zzzz.
System Action:
Action:
4709E
SAPEmailAddr too long
Reason:
The length of the SAPEmailAddr exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the SAPEmailAddr.
4700 - 4799
4710E
EmailAddr too long
Reason:
System Action:
Action:
4711E
BDC system name too long, maximum length nn
Reason:
BDC System name is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of Remote File Name.
4712E
Reason:
There was insufficient space in the ATR to store data for a SAPA_Job jjjj in application
aaaa.
System Action:
Action:
4700 - 4799
4713E
SAPA_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4714E
Reason:
System Action:
Action:
4715E
Reason:
System Action:
Action:
4700 - 4799
4716E
SAPA_JOB xxxx in Appl yyyy, missing ArcObjName
Reason:
Each SAPA_JOB requires an ArcObjName to be specified indicating what work is to be
System Action:
Action:
4717E
SAPA_JOB xxxx in Appl yyyy, missing ArcObjVariant
Reason:
Each SAPA_JOB requires an ArcObjVariant to be specified indicating what work is to be
System Action:
Action:
4718E
SAPA_JOB xxxx in Appl yyyy, missing ArcMode
Reason:
Each SAPA_JOB requires an ArcMode to be specified indicating what work is to be done
System Action:
Action:
4700 - 4799
4719E
SAPA_JOB xxxx in Appl yyyy, missing ArcObjType
Reason:
Each SAPA_JOB requires an ArcObjType to be specified indicating what work is to be
System Action:
Action:
4720E
SAPA_JOB xxxx in Appl yyyy, missing ArcDocType
Reason:
Each SAPA_JOB requires an ArcDocType to be specified indicating what work is to be
System Action:
Action:
4721E
SAPA_JOB xxxx in Appl yyyy, missing ArcInfo
Reason:
Each SAPA_JOB requires an ArcInfo to be specified indicating what work is to be done by
System Action:
Action:
4700 - 4799
4722E
SAPA_JOB xxxx in Appl yyyy, missing PrintDest
Reason:
Each SAPA_JOB requires a PrintDest to be specified indicating what work is to be done
System Action:
Action:
4723E
Reason:
System Action:
Action:
job.
4700 - 4799
4724E
Reason:
System Action:
Action:
4725E
Reason:
System Action:
Action:
4700 - 4799
4726E
Reason:
zzzz.
System Action:
Action:
4727E
EmailAddr too long
Reason:
System Action:
Action:
4728E
Reason:
There was insufficient space in the ATR to store data for a SAPM_Job jjjj in application
aaaa.
System Action:
Action:
4700 - 4799
4729E
SAPM_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4730E
SAPM_JOB xxxx in Appl yyyy, missing Status
Reason:
Each SAPM_JOB requires a Status to be specified indicating what work is to be done by
System Action:
Action:
4731E
Reason:
System Action:
Action:
4700 - 4799
4732E
Reason:
System Action:
Action:
4733E
Reason:
System Action:
Action:
job.
4700 - 4799
4734E
Reason:
System Action:
Action:
4735E
Reason:
System Action:
Action:
4700 - 4799
4736E
Reason:
zzzz.
System Action:
Action:
4737E
Reason:
There was insufficient space in the ATR to store data for a BWPC_Job jjjj in application
aaaa.
System Action:
Action:
4738E
BWPC_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4700 - 4799
4739E
BWPC_JOB xxxx in Appl yyyy, missing Process Chain name
Reason:
Each BWPC_JOB requires a Process Chain name to be specified indicating what work is
to be done by the agent. This job does not have one.
System Action:
Action:
4740E
Reason:
System Action:
Action:
4741E
Reason:
System Action:
Action:
4700 - 4799
4742E
Reason:
System Action:
Action:
job.
4743E
Reason:
System Action:
Action:
4700 - 4799
4744E
Reason:
System Action:
Action:
4745E
Reason:
zzzz.
System Action:
Action:
4700 - 4799
4746E
Reason:
There was insufficient space in the ATR to store data for a BWIP_Job jjjj in application
aaaa.
System Action:
Action:
4747E
BWIP_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4748E
BWIP_JOB xxxx in Appl yyyy, missing Info Package name
Reason:
Each BWIP_JOB requires a Info Package name to be specified indicating what work is to
System Action:
Action:
4700 - 4799
4749E
Reason:
System Action:
Action:
4750E
Reason:
System Action:
Action:
4700 - 4799
4751E
Reason:
System Action:
Action:
job.
4752E
Reason:
System Action:
Action:
4700 - 4799
4753E
Reason:
System Action:
Action:
4754E
Reason:
zzzz.
System Action:
Action:
4700 - 4799
4755E
Reason:
There was insufficient space in the ATR to store data for a EJB_Job jjjj in application
aaaa.
System Action:
Action:
4756E
EJB_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4757E
EJB_JOB xxxx in Appl yyyy, missing BEAN Statement
Reason:
Each EJB_JOB requires a BEAN to be specified indicating what work is to be done by the
System Action:
Action:
4700 - 4799
4758E
EJB_JOB xxxx in Appl yyyy, missing METHOD Statement
Reason:
Each EJB_JOB requires a METHOD to be specified indicating what work is to be done by
System Action:
Action:
4759E
EJB_JOB xxxx in Appl yyyy, missing Initial_Context Statement
Reason:
Each EJB_JOB requires an Initial_Context to be specified indicating what work is to be
System Action:
Action:
4760E
EJB_JOB xxxx in Appl yyyy, missing Location Statement
Reason:
Each EJB_JOB requires a Location to be specified indicating what work is to be done by
System Action:
Action:
4700 - 4799
4761E
Reason:
System Action:
Action:
4762E
Reason:
System Action:
Action:
4763E
Reason:
System Action:
Action:
4700 - 4799
4764E
Reason:
System Action:
Action:
4765E
BEAN Name too long
Reason:
The length of the BEAN Name exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the BEAN Name.
4766E
Reason:
System Action:
Action:
4700 - 4799
4767E
Reason:
System Action:
Action:
4768E
Location too long
Reason:
System Action:
Action:
4769E
Reason:
System Action:
Action:
4700 - 4799
4770E
Reason:
System Action:
Action:
4771E
Reason:
System Action:
Action:
4772E
Reason:
System Action:
Action:
4700 - 4799
4773E
Reason:
There was insufficient space in the ATR to store data for a JMSP_Job jjjj in application
aaaa.
System Action:
Action:
4774E
JMSP_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4775E
JMSP_JOB xxxx in Appl yyyy, missing Initial_Context Statement
Reason:
Each JMSP_JOB requires an Initial_Context to be specified indicating what work is to be
System Action:
Action:
4700 - 4799
4776E
JMSP_JOB xxxx in Appl yyyy, missing Connection Statement
Reason:
Each JMSP_JOB requires a Connection to be specified indicating what work is to be done
System Action:
Action:
4777E
JMSP_JOB xxxx in Appl yyyy, missing Message Class Statement
Reason:
Each JMSP_JOB requires a Message Class to be specified indicating what work is to be
System Action:
Action:
4778E
JMSP_JOB xxxx in Appl yyyy, missing Destination Name Statement
Reason:
Each JMSP_JOB requires a Destination Name to be specified indicating what work is to
System Action:
Action:
4700 - 4799
4779E
JMSP_JOB xxxx in Appl yyyy, missing Location Statement
Reason:
Each JMSP_JOB requires a Location to be specified indicating what work is to be done by
System Action:
Action:
4780E
JMSP_JOB xxxx in Appl yyyy, missing Topic Statement
Reason:
Each JMSP_JOB requires a Topic to be specified indicating what work is to be done by
System Action:
Action:
4781E
Reason:
System Action:
Action:
4700 - 4799
4782E
Reason:
System Action:
Action:
4783E
Reason:
System Action:
Action:
4700 - 4799
4784E
Reason:
System Action:
Action:
4785E
Reason:
System Action:
Action:
4786E
Connection Factory too long
Reason:
The length of the Connection Factory exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Connection Factory.
4700 - 4799
4787E
Message Class too long
Reason:
The length of the Message Class exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Message Class.
4788E
Location too long
Reason:
System Action:
Action:
4789E
Destination Name too long, maximum length nn
Reason:
Destination Name is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of Destination Name.
4700 - 4799
4790E
Reason:
System Action:
Action:
4791E
Reason:
System Action:
Action:
4792E
Reason:
System Action:
Action:
4700 - 4799
4793E
Reason:
There was insufficient space in the ATR to store data for a JMSS_Job jjjj in application
aaaa.
System Action:
Action:
4794E
JMSS_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4795E
JMSS_JOB xxxx in Appl yyyy, missing Initial_Context Statement
Reason:
Each JMSS_JOB requires an Initial_Context to be specified indicating what work is to be
System Action:
Action:
4700 - 4799
4796E
JMSS_JOB xxxx in Appl yyyy, missing Connection Statement
Reason:
Each JMSS_JOB requires a Connection to be specified indicating what work is to be done
System Action:
Action:
4797E
JMSS_JOB xxxx in Appl yyyy, missing Destination Name Statement
Reason:
Each JMSS_JOB requires a Destination Name to be specified indicating what work is to
System Action:
Action:
4798E
JMSS_JOB xxxx in Appl yyyy, missing Location Statement
Reason:
Each JMSS_JOB requires a Location to be specified indicating what work is to be done by
System Action:
Action:
4800 - 4899
4799E
JMSS_JOB xxxx in Appl yyyy, missing Topic Statement
Reason:
Each JMSS_JOB requires a Topic to be specified indicating what work is to be done by
System Action:
Action:
4800 - 4899
4800E
Reason:
System Action:
Action:
4800 - 4899
4801E
Reason:
System Action:
Action:
4802E
Reason:
System Action:
Action:
4800 - 4899
4803E
Reason:
System Action:
Action:
4804E
Reason:
System Action:
Action:
4805E
Connection Factory too long
Reason:
The length of the Connection Factory exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Connection Factory.
4800 - 4899
4806E
Filter too long
Reason:
System Action:
Action:
4807E
Location too long
Reason:
System Action:
Action:
4808E
Reason:
System Action:
Action:
4800 - 4899
4809E
Destination Name too long, maximum length nn
Reason:
Destination Name is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of Destination Name.
4810E
ERROR IN RESCHEDULING EVENTS BY CALENDAR OPERATION
Reason:
There is an error when scheduling statements in events are being updated after
calendar changes.
System Action:
The event scheduling statements are not updated.
Action:
Check the audit log for the cause of this error and correct it.
4811I
Expedite requested, Jobname=xxxx, JobPriority=nn, JobClass=cccc,
ProcessPriority=pppp
Reason:
An expedite request has been sent to an agent job xxxx. The optional expedite operands
are nn (Job Priority), cccc (Job Class) and pppp (Process Priority)
System Action:
Action:
Check the audit log for the response to the expedite request.
4800 - 4899
4812I
xx completed applications found, yy rejected
Reason:
During initialization, the Application Manager determines the number of completed
Applications (xx). Some completed Application records (yy) may be flagged as unusable.
System Action:
Completed Applications (xx) are added to the Application Scoreboard.
Action:
None.
4813I
PURGAPPL completed, nn entries purged
Reason:
A PURGAPPL command or initialization statement was entered to purge entries from
the Application file. nn entries have been purged.
System Action:
The Application Scoreboard is also purged.
Action:
None.
4814E
PURGAPPL time is invalid. Application file purge request rejected.
Reason:
The PURGAPPL command was entered, but the date/time expression was not accepted.
System Action:
The PURGAPPL command is refused.
Action:
Re-enter the command with a correct date/time expression... that is 'PURGAPPL today
less 1 week'
4800 - 4899
4815W
Request refused - filter table versions are xxx and yyy - a RELOAD may be required...
Reason:
A CSF or Application Monitor request has been refused because different versions of the
Filter Dictionary table were found.
System Action:
Access to the CSF and/or Application Monitor display is denied.
Action:
Restarting the product with the 'RELOAD' parameter may fix the problem.
4816E
MonCond too long
Reason:
The length of the MonCond exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the MonCond.
4817E
TABLENAME too long
Reason:
The length of the TABLENAME exceeds the maximum of 100 characters.
System Action:
Action:
Reduce the length of the TABLENAME.
4800 - 4899
4818E
Invalid EventTime Statement
Reason:
The FROM time definition is invalid.
System Action:
Action:
Correct the EventTime statement.
4819E
JobObject too long
Reason:
The length of the JobObject exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the JobObject.
4820E
MONTYPE too long
Reason:
The length of the MONTYPE exceeds the maximum of 50 characters.
System Action:
Action:
Reduce the length of the MONTYPE.
4800 - 4899
4821E
Reason:
System Action:
Action:
4822E
Reason:
System Action:
Action:
4800 - 4899
4823E
Reason:
System Action:
Action:
4824E
Reason:
System Action:
Action:
4800 - 4899
4825x
<applname.gen> scoreboard entry xxxxxxxx failed, entry-id yyzzzzzz. {Attempting
retry.}
Reason:
An attempt to process an Application Scoreboard entry failed. The attempted action is
xxxxxxxx, the access code is yyzzzzzz.
System Action:
4825I: alternative processing is employed (Attempting retry). 4825E: this Application
Scoreboard action is abandoned. Note that an error in ApplMon processing does not
affect job scheduling.
Action:
Contact CA Support if excessive numbers of '4825' messages appear.
4826E
DB_MON xxxx in Appl yyyy, missing MonType Statement
Reason:
There was no MonType Statement to identify the work to run.
System Action:
Action:
Provide the MonType Statement. Then resubmit the job.
4827E
DB_TRIG xxxx in Appl yyyy, missing TrigType Statement
Reason:
There was no TrigType Statement to identify the work to run.
System Action:
Action:
Provide the TrigType Statement. Then resubmit the job.
4800 - 4899
4828E
Invalid structure in Calendar xxxx
Reason:
During processing, Calendar xxxx failed a validity check. A validity check fails when the
Calendar records (in INDEX Data Set) are corrupted.
System Action:
The product will discontinue processing of this Calendar.
Action:
Delete the Calendar. It can be restored from an INDEX Data Set backup. First, create a
VSAM copy of your INDEX Data Set from the backup, and after that REPRO the Calendar
from the INDEX Data Set copy into your INDEX Data Set using parameters
FROMKEY(Cxxxx*) and TOKEY(Cxxxx*), where xxxx is your Calendar name.
4829E
Error occurred processing Job Statistics entry for External Scheduler Ap Job xxxx in
Appl yyyy
Reason:
An I/O error on the Job Statistics data set, described by a preceding message, has
occurred.
System Action:
No Job Statistics recording will be performed for the indicated External Scheduler job.
Action:
4800 - 4899
4830E
Error occurred processing Job Statistics entry for External Scheduler Ap Job xxxx in
Appl yyyy
Reason:
An I/O error on the Job Statistics data set, described by a preceding message, has
occurred.
System Action:
No Job Statistics recording will be performed for the indicated External Scheduler job.
Action:
4831E
Reason:
System Action:
Action:
4832E
EXTSCH xxxx in Appl yyyy: missing External Scheduler name
Reason:
There was no External Scheduler name to identify where the work was to run.
System Action:
Action:
Provide the External Scheduler name. Then resubmit the job.
4800 - 4899
4833E
Invalid External Scheduler name wwww in Appl yyyy
Reason:
The External Scheduler named wwww was not defined when the workload object was
readied.
System Action:
Action:
Either correct the External Scheduler name, or define the External Scheduler. Then
resubmit the job.
4833E
Invalid External Scheduler name wwww in Appl yyyy
Reason:
The External Scheduler named wwww was not defined when the workload object was
readied.
System Action:
Action:
Either correct the External Scheduler name, or define the External Scheduler. Then
resubmit the job.
4800 - 4899
4834E
User xxxx denied access to External Scheduler yyyy
Reason:
User xxxx is not authorized to submit jobs to External Scheduler yyyy. "xxxx" is the user
id under which the event executes for this job, normally the event prefix, but it may be a
System Action:
Action:
In order to submit jobs to External Scheduler yyyy, user xxxx must have read access to
SAF profile AGENT.yyyy. Once this has been established, resubmit the job.
4836E
Reason:
There was insufficient space in the ATR to store data for a SNPE_Job jjjj in application
aaaa.
System Action:
Action:
4837E
SNPE_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4800 - 4899
4838E
SNPE_Job xxxx in Appl yyyy, missing MIB Statement
Reason:
There was no MIB provided.
System Action:
Action:
Provide the MIB. Then resubmit the job.
4839E
SNPE_Job xxxx in Appl yyyy, missing SNMPNODE
Reason:
There was no SNMPNODE provided.
System Action:
Action:
Provide the SNMPNODE. Then resubmit the job.
4840E
SNPE_Job xxxx in Appl yyyy, missing HOST
Reason:
There was no SNMP HOST provided.
System Action:
Action:
Provide the SNMP HOST. Then resubmit the job.
4800 - 4899
4841E
SNPE_Job xxxx in Appl yyyy, missing VERSION
Reason:
There was no SNMP VERSION provided.
System Action:
Action:
Provide the SNMP VERSION. Then resubmit the job.
4842E
tttt xxxx in Appl yyyy, missing USER statement
Reason:
Job type tttt requires a User be specified indicating what work is to be done by the
System Action:
Action:
4843E
SNPE_Job xxxx in Appl yyyy, missing SNMPUSER Statement
Reason:
There was no SNMPUSER provided.
System Action:
Action:
Provide the SNMPUSER. Then resubmit the job.
4800 - 4899
4844E
SNPE_Job xxxx in Appl yyyy, missing AUTHPROTOCOL Statement
Reason:
There was no AUTHPROTOCOL provided.
System Action:
Action:
Provide the AUTHPROTOCOL. Then resubmit the job.
4845E
SNPE_Job xxxx in Appl yyyy, missing PRIVPROTOCOL Statement
Reason:
There was no PRIVPROTOCOL provided.
System Action:
Action:
Provide the PRIVPROTOCOL. Then resubmit the job.
4846E
SNPE_Job xxxx in Appl yyyy, missing COMMUNITY Statement
Reason:
There was no COMMUNITY provided.
System Action:
Action:
Provide the COMMUNITY. Then resubmit the job.
4800 - 4899
4847E
Reason:
System Action:
Action:
4848E
Reason:
System Action:
Action:
4849E
Reason:
System Action:
Action:
4800 - 4899
4850E
Unable to find password matching xxxx, yyyy, zzzz, Protocol type AUTH, RC=n
Reason:
and data source name AUTH.
System Action:
Action:
4851E
Unable to find password matching xxxx, yyyy, zzzz, Protocol type PRIV, RC=n
Reason:
and data source name PRIV.
System Action:
Action:
4852E
MIB too long, maximum length nn
Reason:
MIB file name is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the MIB file name.
4800 - 4899
4853E
SNMPNODE too long, maximum length nn
Reason:
SNMP NODE is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the SNMP NODE.
4854E
HOST too long, maximum length nn
Reason:
SNMP HOST is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the SNMP HOST.
4855E
Reason:
System Action:
Action:
4800 - 4899
4856E
Reason:
System Action:
Action:
4857E
Reason:
System Action:
Action:
4858E
Reason:
System Action:
Action:
4800 - 4899
4859E
COMMUNITY too long, maximum length nn
Reason:
SNMP COMMUNITY is longer than the maximum nn allowed for the workload object
type.
System Action:
Action:
Reduce the length of the SNMP COMMUNITY.
4860E
EngineID too long, maximum length nn
Reason:
EngineID is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the EngineID.
4861E
AUTHPROTOCOL has invalid length, correct length nn
Reason:
AUTHPROTOCOL has invalid length.
System Action:
Action:
Correct the AUTHPROTOCOL Statement.
4800 - 4899
4862E
AUTHPROTOCOL invalid, it must be MD5 or SHA
Reason:
AUTHPROTOCOL is invalid.
System Action:
Action:
Correct the AUTHPROTOCOL Statement.
4863E
PRIVPROTOCOL has invalid length, correct length nn
Reason:
PRIVPROTOCOL has invalid length.
System Action:
Action:
Correct the PRIVPROTOCOL Statement.
4864E
PRIVPROTOCOL invalid, it must be DES or AES
Reason:
PRIVPROTOCOL is invalid.
System Action:
Action:
Correct the PRIVPROTOCOL Statement.
4800 - 4899
4865E
Reason:
There was insufficient space in the ATR to store data for a OAC_Job jjjj in application
aaaa.
System Action:
Action:
4866E
OAC_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4867E
Reason:
System Action:
Action:
4800 - 4899
4868E
Reason:
System Action:
Action:
4869E
OAC_Job xxxx in Appl yyyy, RequestID statement missing
Reason:
There was no REQUESTID provided.
System Action:
Action:
Provide the REQUESTID. Then resubmit the job.
4800 - 4899
4870E
Reason:
System Action:
Action:
job.
4871E
Reason:
System Action:
Action:
4800 - 4899
4872E
Reason:
There was insufficient space in the ATR to store data for a SNPC_Job jjjj in application
aaaa.
System Action:
Action:
4873E
SNPC_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4874E
SNPC_Job xxxx in Appl yyyy, missing MIB Statement
Reason:
There was no MIB provided.
System Action:
Action:
Provide the MIB. Then resubmit the job.
4800 - 4899
4875E
SNPC_Job xxxx in Appl yyyy, missing FILTER Statement
Reason:
There was no FILTER provided.
System Action:
Action:
Provide the FILTER. Then resubmit the job.
4876E
Reason:
System Action:
Action:
4877E
Reason:
System Action:
Action:
4800 - 4899
4878E
Reason:
System Action:
Action:
4879E
Reason:
zzzz.
System Action:
Action:
4880E
MIB too long, maximum length nn
Reason:
MIB file name is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of the MIB file name.
4800 - 4899
4881E
Filter too long
Reason:
System Action:
Action:
4882E
Reason:
zzzz.
System Action:
Action:
4883E
Length of MAC is not 17
Reason:
The MAC statement can only be 17 characters long
System Action:
Action:
4800 - 4899
4884E
WakeHost too long, maximum length nn
Reason:
WakeHost is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of WakeHost.
4885E
Soft value is greater than Hard value
Reason:
Error in ULIMIT statement. The value specified with SOFT parameter must be less than
or equal to the value specified with parameter HARD.
System Action:
Action:
Correct the error, then regenerate application.
4900 - 4999
4900 - 4999
4901E
Reason:
There was insufficient space in the ATR to store data for a JMXB_Job jjjj in application
aaaa.
System Action:
Action:
4902E
JMXB_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4903E
JMXB_Job xxxx in Appl yyyy, missing MBean Statement
Reason:
System Action:
Action:
4900 - 4999
4904E
JMXB_Job xxxx in Appl yyyy, missing Attribute Statement
Reason:
There was no Attribute provided.
System Action:
Action:
Provide the Attribute. Then resubmit the job.
4905E
JMXB_Job xxxx in Appl yyyy, missing URL Statement
Reason:
System Action:
Action:
4906E
Reason:
System Action:
Action:
4900 - 4999
4907E
Reason:
System Action:
Action:
4908E
Reason:
System Action:
Action:
4900 - 4999
4909E
Reason:
zzzz.
System Action:
Action:
4910E
RemoteDir too long, maximum length nnn
Reason:
RemoteDir is longer than the maximum nnn allowed for the workload object type.
System Action:
Action:
Reduce the length of RemoteDir.
4911E
MBean too long
Reason:
System Action:
Action:
4900 - 4999
4912E
Attribute too long
Reason:
The length of the Attribute exceeds the maximum of 1024 characters.
System Action:
Action:
Reduce the length of the Attribute.
4913E
URL too long
Reason:
System Action:
Action:
4914E
Filter too long
Reason:
System Action:
Action:
4900 - 4999
4915E
JMXA_Job xxxx in Appl yyyy, missing PARAMETER Statement
Reason:
There was no PARAMETER provided.
System Action:
Action:
Provide the PARAMETER. Then resubmit the job.
4919E
Reason:
There was insufficient space in the ATR to store data for a JMXR_Job jjjj in application
aaaa.
System Action:
Action:
4920E
JMXR_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4900 - 4999
4921E
JMXR_Job xxxx in Appl yyyy, missing MBean Statement
Reason:
System Action:
Action:
4922E
JMXR_Job xxxx in Appl yyyy, missing URL Statement
Reason:
System Action:
Action:
4923E
Reason:
System Action:
Action:
4900 - 4999
4924E
Reason:
System Action:
Action:
4925E
Reason:
System Action:
Action:
4900 - 4999
4926E
Reason:
zzzz.
System Action:
Action:
4928E
MBean too long
Reason:
System Action:
Action:
4929E
URL too long
Reason:
System Action:
Action:
4900 - 4999
4931E
WOL_JOB xxxx in Appl yyyy, missing MAC statement
Reason:
There was no MAC provided.
System Action:
Action:
Provide the MAC. Then resubmit the job.
4932E
LDA string is too long
Reason:
The length of the LDA exceeds the maximum of 1024 characters or 2051 characters in
HEX form (it includes the leading X' and ending ').
System Action:
Action:
Reduce the length of the LDA.
4933E
Reason:
There was insufficient space in the ATR to store data for a SNPG_Job jjjj in application
aaaa.
System Action:
Action:
4900 - 4999
4934E
SNPG_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4935E
SNPG_Job xxxx in Appl yyyy, missing SNMPNODE
Reason:
There was no SNMPNODE provided.
System Action:
Action:
Provide the SNMPNODE. Then resubmit the job.
4936E
SNPG_Job xxxx in Appl yyyy, missing HOST
Reason:
System Action:
Action:
4900 - 4999
4937E
SNPG_Job xxxx in Appl yyyy, missing VERSION
Reason:
System Action:
Action:
4938E
SNPG_Job xxxx in Appl yyyy, missing SNMPUSER Statement (mandatory for SNMP v3)
Reason:
System Action:
Action:
4939E
SNPG_Job xxxx in Appl yyyy, missing PRIVPROTOCOL Statement (mandatory for SNMP
v3)
Reason:
System Action:
Action:
4900 - 4999
4940E
SNPG_Job xxxx in Appl yyyy, missing AUTHPROTOCOL Statement (mandatory for
SNMP v3)
Reason:
System Action:
Action:
4941E
SNPG_Job xxxx in Appl yyyy, missing COMMUNITY Statement (mandatory for SNMP
v1 and v2)
Reason:
System Action:
Action:
4942E
Invalid Agent name xxxx in Appl yyyy
Reason:
The agent named xxxx was not defined when the workload object was readied.
System Action:
Action:
4900 - 4999
4943E
Reason:
System Action:
Action:
4944E
Reason:
System Action:
Action:
4900 - 4999
4945E
Reason:
System Action:
Action:
4946E
Reason:
System Action:
Action:
4947E
SNMPUser too long
Reason:
The length of the SNMPUser exceeds the maximum of 128 characters.
System Action:
Action:
Reduce the length of the SNMPUser.
4900 - 4999
4948E
COMMUNITY too long
Reason:
The length of the COMMUNITY exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the COMMUNITY.
4949E
MIB too long
Reason:
The length of the MIB exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the MIB.
4950E
ContextEngineID too long
Reason:
The length of the ContextEngineID exceeds the maximum of 512 hexadecimal
characters.
System Action:
Action:
Reduce the length of the ContextEngineID.
4900 - 4999
4951E
ContextName too long
Reason:
The length of the ContextName exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the ContextName.
4952E
SNMPNODE too long
Reason:
The length of the SNMP NODE exceeds the maximum of 256 characters.
System Action:
Action:
4953E
HOST too long
Reason:
The length of the SNMP HOST exceeds the maximum of 256 characters.
System Action:
Action:
4900 - 4999
4954E
Subtree keyword should be also provided, if TableView was specified
Reason:
Tableview was specified without Subtree keyword.
System Action:
Action:
Add Subtree keyword.
4955E
Reason:
There was insufficient space in the ATR to store data for a SNPS_Job jjjj in application
aaaa.
System Action:
Action:
4956E
SNPS_Job xxxx in Appl yyyy, missing Agent name
Reason:
System Action:
Action:
4900 - 4999
4957E
SNPS_Job xxxx in Appl yyyy, missing SNMPNODE
Reason:
There was no SNMP NODE provided.
System Action:
Action:
Provide the SNMP NODE. Then resubmit the job.
4958E
SNPS_Job xxxx in Appl yyyy, missing HOST
Reason:
System Action:
Action:
4959E
SNPS_Job xxxx in Appl yyyy, missing VERSION
Reason:
System Action:
Action:
4900 - 4999
4960E
SNPS_Job xxxx in Appl yyyy, missing PARAMETER Statement
Reason:
There was no PARAMETER provided.
System Action:
Action:
Provide the PARAMETER. Then resubmit the job.
4961E
SNPS_Job xxxx in Appl yyyy, missing SNMPUSER Statement (mandatory for SNMP v3)
Reason:
System Action:
Action:
4962E
SNPS_Job xxxx in Appl yyyy, missing PRIVPROTOCOL Statement (mandatory for SNMP
v3)
Reason:
System Action:
Action:
4900 - 4999
4963E
SNPS_Job xxxx in Appl yyyy, missing AUTHPROTOCOL Statement (mandatory for
SNMP v3)
Reason:
System Action:
Action:
4964E
SNPS_Job xxxx in Appl yyyy, missing COMMUNITY Statement (mandatory for SNMP v1
and v2)
Reason:
System Action:
Action:
4965E
Invalid Agent name xxxx in Appl yyyy
Reason:
The agent named xxxx was not defined when the workload object was readied.
System Action:
Action:
4900 - 4999
4966E
Reason:
System Action:
Action:
4967E
Reason:
System Action:
Action:
4900 - 4999
4968E
Reason:
System Action:
Action:
4969E
Reason:
System Action:
Action:
4970E
SNMPUser too long
Reason:
The length of the SNMPUser exceeds the maximum of 128 characters.
System Action:
Action:
Reduce the length of the SNMPUser.
4900 - 4999
4971E
COMMUNITY too long
Reason:
The length of the COMMUNITY exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the COMMUNITY.
4972E
Reason:
System Action:
Action:
4973E
Reason:
System Action:
Action:
4900 - 4999
4974E
Reason:
System Action:
Action:
4975E
Reason:
System Action:
Action:
4976E
MIB too long
Reason:
The length of the MIB exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the MIB.
4900 - 4999
4977E
ContextName too long
Reason:
The length of the ContextName exceeds the maximum of 256 characters.
System Action:
Action:
Reduce the length of the ContextName.
4978E
ContextEngineID too long
Reason:
The length of the ContextEngineID exceeds the maximum of 512 hexadecimal
characters.
System Action:
Action:
Reduce the length of the ContextEngineID.
4979E
SNMPNODE too long
Reason:
The length of the SNMP NODE exceeds the maximum of 256 characters.
System Action:
Action:
4900 - 4999
4980E
HOST too long
Reason:
The length of the SNMP HOST exceeds the maximum of 256 characters.
System Action:
Action:
4981E
Encoding too long, maximum length nn
Reason:
Encoding is longer than the maximum nn allowed for the workload object type.
System Action:
Action:
Reduce the length of Encoding.
4982E
RUNCONTROLTABLE too long
Reason:
The length of the RUNCONTROLTABLE exceeds the maximum of 100 characters.
System Action:
Action:
Reduce the length of the RUNCONTROLTABLE.
4900 - 4999
4983E
RunControlArgs too long
Reason:
The length of RunControlArgs exceeds the maximum of 4078 characters.
System Action:
Action:
Reduce the length of the RunControlArgs.
4984E
Parameter Array too long
Reason:
The length of the Parameter Array exceeds the maximum of 3588 characters, including
all delimiters and the Type operand.
System Action:
Action:
Reduce the length of the Parameter Array.
4985E
Reason:
System Action:
Action:
4900 - 4999
4986E
Reason:
System Action:
Action:
4987E
Reason:
System Action:
Action:
4988E
Reason:
System Action:
Action:
4900 - 4999
4989E
Reason:
System Action:
Action:
4990E
Reason:
System Action:
Action:
4991E
Reason:
System Action:
Action:
4900 - 4999
4992E
Reason:
System Action:
Action:
4993E
Reason:
System Action:
Action:
4994E
Reason:
System Action:
Action:
4900 - 4999
4995E
CreateParameter Array too long
Reason:
The length of the CreateParameter Array exceeds the maximum of 3588 characters,
including all delimiters and the Type operand.
System Action:
Action:
Reduce the length of the CreateParameter Array.
4996E
Missing CreateParameter Value, Array or URI
Reason:
Each CREATEPARAMETER requires a Value or an Array or a URI to be specified indicating
System Action:
Action:
4997E
CreateParameter Array too long
Reason:
The length of the CreateParameter Array exceeds the maximum of 3588 characters,
System Action:
Action:
Reduce the length of the CreateParameter Array.
4900 - 4999
4998E
ModifyParameter Array too long
Reason:
The length of the ModifyParameter Array exceeds the maximum of 3588 characters,
System Action:
Action:
Reduce the length of the ModifyParameter Array.
4999E
FinderParameter Array too long
Reason:
The length of the FinderParameter Array exceeds the maximum of 3588 characters,
System Action:
Action:
Reduce the length of the FinderParameter Array.

6000 - 6099
6001I
ADMFUNC: User entry e added by u
Reason:
The user entry 'e' has been added by user 'u'
System Action:
The function was performed.
Action:
N/A
6002I
ADMFUNC: User entry e deleted by u
Reason:
The user entry 'e' has been deleted by user 'u'
System Action:
Action:
N/A
6000 - 6099
6003I
ADMFUNC: User u connected to group g by u2
Reason:
The user 'u' has been connected to group 'g' by user 'u2'
System Action:
Action:
N/A
6004I
ADMFUNC: User u disconnected from group g by u2
Reason:
The user 'u' has been disconnected from group 'g' by user 'u2'
System Action:
Action:
N/A
6005I
ADMFUNC: Group g deleted by u
Reason:
The group entry 'g' has been deleted by user 'u'
System Action:
Action:
N/A
6000 - 6099
6006I
ADMFUNC: Group entry g added by u
Reason:
The group entry 'g' has been added by user 'u'
System Action:
Action:
N/A
6007I
ADMFUNC: Group entry g updated by u
Reason:
The group entry 'g' has been updated by user 'u'
System Action:
Action:
N/A
6010I
AgentMR: Agent found quiesced: a
Reason:
The agent 'a' was found quiesced
System Action:
Information only.
Action:
N/A
6000 - 6099
6011I
AgentMR: MgrMsg cannot be checkpointed: m
Reason:
The manager message 'm' cannot be checkpointed.
System Action:
Information only.
Action:
N/A
6012I
AgentMR: Message received:
Reason:
A message was received.
System Action:
Information only.
Action:
N/A
6013E
AgentMR: Recipient not found for msg:
Reason:
The recipient of the message was not found.
System Action:
Information only.
Action:
N/A
6000 - 6099
6014I
AgentMR: Attaching comm task for Agent
Reason:
A comm task was attached for the agent.
System Action:
Information only.
Action:
N/A
6015I
AgentMR: A specific message from the Agent MR processing.
Reason:
Self explanatory.
System Action:
Information only.
Action:
N/A
6020I
Appl a job j expedite response: r
Reason:
The system displays the response from an expedite request.
System Action:
The expedite response is shown
Action:
None
6000 - 6099
6021E
Error e from SendAFM
Reason:
The SendAFM function received an error.
System Action:
The error is reported.
Action:
Contact CA Support.
6022I
VarTab: tttt created by uuuu
Reason:
The variable table named tttt was created by user uuuu.
System Action:
Action:
None
6023I
VarTab: tttt deleted by uuuu
Reason:
The variable table named tttt was deleted by user uuuu.
System Action:
Action:
None
6000 - 6099
6024I
VarTab: Table tttt variable vvvv deleted by uuuu
Reason:
The variable table tttt variable vvvv was deleted by user uuuu.
System Action:
Action:
None
6025I
VarTab: Table tttt Trigger id iiii replaced/defined by user uuuu
Reason:
The variable table tttt trigger id iiii was replaced or defined user uuuu.
System Action:
Action:
None
6026I
VarTab: Table tttt Trigger id iiii deleted/deleted with variable vvvv by user uuuu.
Reason:
The variable table tttt trigger id iiii was deleted or deleted with variable vvvv by user
uuuu.
System Action:
Action:
None
6000 - 6099
6027I
VarTab: Table tttt variable vvvv changed from "" to "value" by uuuu
Reason:
The variable table tttt variable vvvv was added or changed by user uuuu.
System Action:
Action:
None
6028I
VarTab: Table tttt variable vvvv could not be time stamped
Reason:
The variable table tttt did not have sufficient free space to add a user ID and time stamp
to the variable vvvv.
System Action:
Action:
The user has several options: (a) ignore the message (b) delete some unused variables
from the table (c) split the table into two or more separate tables (d) increase the
MAXLRECL value in the product initialization statements
6000 - 6099
6029I
Table cannot be expanded to hold time stamps
Reason:
The variable table in use did not have sufficient free space to add a user ID and time
stamp to a variable. This message is accompanied by message 6028 in the audit log to
indicate what variable experienced the problem.
System Action:
Action:
The user has several options: (a) ignore the message (b) delete some unused variables
from the table (c) split the table into two or more separate tables (d) increase the
MAXLRECL value in the product initialization statements
6030I
Appl aaaa created slot ssss
Reason:
An application management record has been created for the application. The slot
number in the application file is displayed for information purposes only.
System Action:
The slot was created by the application.
Action:
None required.
6031E
Appl a error building index entry
Reason:
An index entry initialization process failed.
System Action:
The application record is not stored
Action:
See message 1136E for details.
6000 - 6099
6032E
Appl a error writing Applfile record
Reason:
An I/O error occurred while trying to write an application record.
System Action:
The application record is not stored
Action:
See message 1137E for details.
6040I
Appl a slot s now under appl manager control
Reason:
The index entry for the application is being processed
System Action:
The application manager is processing the application.
Action:
None
6041I
Appl a slot s (old) restored and uncompleted in slot s
Reason:
The index entry for the application has been reset.
System Action:
The application has been uncompleted
Action:
None
6000 - 6099
6042I
Appl a PCR at slot (old) restored in slot s (new)
Reason:
The persistent caching record has been restored.
System Action:
A new index entry for the application has been used.
Action:
None
6043E
Error in manager message format
Reason:
System Action:
The message is discarded
Action:
See Messages 6051 & 6052
6044E
Invalid verb in message to manager
Reason:
System Action:
Action:
6000 - 6099
6045W
Invalid state message ignored
Reason:
System Action:
Action:
6046E
Invalid EXTSCH WAIT or FORCE message
Reason:
System Action:
Action:
6047E
Invalid EXTSCH POST message
Reason:
System Action:
Action:
6000 - 6099
6048E
Unable to locate Appl for manager message
Reason:
System Action:
Action:
6049E
Invalid verb specified in manager message
Reason:
System Action:
Action:
6050E
Invalid verb modifier specified in manager message
Reason:
System Action:
Action:
6000 - 6099
6051E
Msg: x
Reason:
Explanation of the internal error.
System Action:
Action:
See also Message 6043 & 6052
6052E
(cont'd) x
Reason:
Continuation of message 6051
System Action:
Action:
See also Message 6043 & 6053
6053I
Longname invalid for MVS job in MGRMSG
Reason:
A MVS jobname is limited to 8 characters.
System Action:
A MVS job with the longname parameter in MGRMSG is rejected.
Action:
Correct the jobname.
6000 - 6099
6054E
Invalid parameters specified in MGRMSG
Reason:
The internal MGRMSG control block is incorrect.
System Action:
Processing of the message is discontinued.
Action:
None
6055I
Appl a job j priority changed to p
Reason:
A priority change has occurred.
System Action:
The job's priority is changed.
Action:
None
6056E
Invalid manager service request made
Reason:
Internal error.
System Action:
Action:
None
6000 - 6099
6057I
Token t in resfile contains appl a job j but it is referred to by appl a job j
Reason:
A control block mismatch has occurred.
System Action:
Processing of the token is discontinued.
Action:
See also Message 6063
6058I
Appl a job j removed from resfile entry was invalid
Reason:
The entry was erased from the resfile
System Action:
Cleanup is performed
Action:
None
6059E
Missing identification on AF message
Reason:
The userid is missing on the message
System Action:
The userid that the message should be processed under cannot be located. Process
Action:
None
6000 - 6099
6060I
Insertion not allowed: application contains DM controlled objects
Reason:
The application manager tried to insert a message in the queue
System Action:
The insertion is denied.
Action:
None
6061I
MgrMsg forwarded to n
Reason:
The message was forwarded to manager n
System Action:
Message forwarded
Action:
None
6062I
Appl a job j ESP priority changed to p
Reason:
The priority was changed.
System Action:
The priority was changed.
Action:
None
6000 - 6099
6063I
text
Reason:
See previous messages
System Action:
See previous messages
Action:
None
6064I
AUDITLG: Auditlog opened, sysout class x
Reason:
The Audit log has been opened for output using class x where x is the class selected
using parmlib entry AUDITLOG x
System Action:
The Audit log is open
Action:
None
6065I
Postreq invoked
Reason:
Post request processing was invoked.
System Action:
The request was posted
Action:
None
6000 - 6099
6066I
Subtask processing a request
Reason:
The subtask is processing a request
System Action:
The subtask is processing a request
Action:
None
6067I
Subtask going into wait
Reason:
The subtask is beginning a wait.
System Action:
The subtask is beginning a wait.
Action:
None
6070I
Event e triggered by data set d job j
Reason:
The event was triggered.
System Action:
Action:
None
6000 - 6099
6080I
Explicit data set trigger (variable portion)
Reason:
A dataset trigger was received.
System Action:
A dataset trigger was received.
Action:
None
6090I
Event e rescheduled by calendar operation
Reason:
An event was rescheduled
System Action:
A calendar change has necessitated the rescheduling of an event.
Action:
None
6091I
Unable to queue directly to system s
Reason:
The event could not be queued to the system
System Action:
The queue cannot be located
Action:
None
6000 - 6099
6092I
s NOT MEMBER OF SHARED QUEUE
Reason:
System s is not part of the queue
System Action:
The specified system cannot be found
Action:
None
6093W
NO SYSTEMS FOUND MATCHING s
Reason:
System s cannot be found
System Action:
The specified system cannot be found
Action:
None
6094I
Insufficient queue file space to queue event e
Reason:
The event is not queued
System Action:
The TDR is not queued.
Action:
None
6000 - 6099
6095I
Insufficient checkpoint space to queue event e
Reason:
The event is not checkpointed
System Action:
The TDR is not checkpointed.
Action:
None
6096I
Time conversion error processing event e
Reason:
A calendar/event error has occurred.
System Action:
The event is not recycled.
Action:
None
6097I
Scheduled time has already passed for event e
Reason:
The scheduled time is in the past.
System Action:
The SCE is ignored
Action:
None
6100 - 6199
6098I
Event e defined by u
Reason:
User u has defined event e
System Action:
The event is defined.
Action:
None
6099I
Event e replaced by u
Reason:
User u has replaced event e
System Action:
The event is replaced.
Action:
None
6100 - 6199
6100I
Invalid TDR length l. TDR request code = r. TDR ignored.
Reason:
An internal control block is in error
System Action:
The control block is ignored.
Action:
None
6100 - 6199
6101I
Unidentified TDR type = t encountered TDR ignored.
Reason:
An internal control block is in error
System Action:
The control block is ignored.
Action:
None
6102I
Event e not executed- bypass requested.
Reason:
The user requested the event be bypassed.
System Action:
The event is bypassed.
Action:
None
6103I
Event e not executed- class is SUSPENDED.
Reason:
The class is suspended so the event cannot execute.
System Action:
Action:
None
6100 - 6199
6104I
Event e postponed- class is HELD
Reason:
The class is in hold status so the event is not executed.
System Action:
Action:
None
6105I
Event e not executed- SCE_type=DELETE
Reason:
The event was not executed as the schedule control element indicated deletion.
System Action:
Action:
None
6106I
Next execution of Event e not scheduled: unsuccessful CYCLING
Reason:
The cycling of an event failed
System Action:
The next execution of the event is not scheduled.
Action:
None
6100 - 6199
6107I
TDR ignored for event e which is in SUSPENDED status
Reason:
The event is suspended
System Action:
The TDR for the event is ignored.
Action:
None
6108I
e scheduled (variable info)
Reason:
Information about event e
System Action:
See message text
Action:
None
6109I
Event e in class c moved to class 0
Reason:
The specified class could not be found.
System Action:
The system tries class 0
Action:
None
6100 - 6199
6110I
Missing class 0 TDR ignored
Reason:
Class 0 is not found
System Action:
Action:
See also message 6109
6111I
Event e not found needed for j in Appl a
Reason:
An event is missing
System Action:
The TDR is discarded
Action:
6112I
Previous request to replace next scheduled time of Event bypassed
Reason:
The request is bypassed
System Action:
The next scheduled time is not changed.
Action:
None
6100 - 6199
6113I
Event reexecution requested for Event e
Reason:
Reexecution of the event is requested
System Action:
Reexecution is scheduled.
Action:
None
6114I
User u no longer defined. Possible diagnostic messages on execution of Event
Reason:
The owner/user of the event has become undefined.
System Action:
Event information cannot be sent to the user.
Action:
Check if the user is defined. See also messages 6115 & 1988
6115I
e will not reach the owner
Reason:
The owner/user of the event has become undefined.
System Action:
Event information cannot be sent to the user.
Action:
See also messages 6114 & 1988
6100 - 6199
6116I
Event AUTODELETED (By z/OS Agent)
Reason:
The z/OS agent has deleted the event
System Action:
Event deleted.
Action:
6117I
Error occurred during AUTODELETE of Event e
Reason:
Internal error.
System Action:
Autodelete fails.
Action:
6118I
Schedule for event not updated - invalid SCE type
Reason:
A control block is in error
System Action:
The event schedule is not changed
Action:
None
6100 - 6199
6119I
Event e not scheduled PSE/TDR not added: no space
Reason:
The system is out of space
System Action:
The event is not scheduled
Action:
None
6120I
Last schedule of Event e ignored. Pending will be executed. SWPs deleted (F
Reason:
The pending event will be executed
System Action:
The pending event is executed
Action:
None
6121I
Last schedule of Event e ignored - SWP not found (FORCE option in effect)
Reason:
Event e is ignored because of an internal error
System Action:
Event is not executed
Action:
None
6100 - 6199
6122I
Event bypassed waiting for multiple trigger to complete
Reason:
All triggers must complete for the event to execute
System Action:
Action:
None
6123I
Multiple trigger completed for above Event
Reason:
All triggers have completed
System Action:
The event executes.
Action:
None
6124I
e execution bypassed due to NOSCHED request
Reason:
A Noschedule statement has bypassed event execution
System Action:
Action:
None
6100 - 6199
6125I
Parms: ESPTRUSR(u) ESPTRTYP(t) RESUB_USER(ru)
Reason:
Parameters sent to event
System Action:
Parameters displayed.
Action:
None
6150I
e triggered by u with o
Reason:
User u has triggered the event using o (REPLACE or ADD)
System Action:
The event executes.
Action:
None
6151I
Execution bypass requested by u for System s Event e
Reason:
User u has bypassed event e
System Action:
Action:
None
6100 - 6199
6152I
Execution bypass requested by u
Reason:
User u has bypassed event e
System Action:
Action:
None
6153I
e SUSPEND count incremented by u
Reason:
User u has suspended event e
System Action:
Suspend count is incremented
Action:
None
6154I
e suspended by u
Reason:
Initial suspension of event e
System Action:
Event is suspended
Action:
None
6100 - 6199
6155I
e HOLD count incremented by u
Reason:
User u has held event e
System Action:
Hold count is incremented
Action:
None
6156I
e held by u
Reason:
Initial hold of event e
System Action:
Event is hold
Action:
None
6157I
e SUSPEND count decremented by u
Reason:
User u has resumed event e
System Action:
Suspend count is decremented
Action:
None
6100 - 6199
6158I
e resumed by u
Reason:
Suspend count has reached 0
System Action:
Event is resumed
Action:
None
6159I
HOLD count decremented by u
Reason:
User u has released the event
System Action:
Hold count is decremented
Action:
None
6160I
e released by u
Reason:
User u has released the event
System Action:
Event is released
Action:
None
6100 - 6199
6161I
e altered by u
Reason:
User u has updated event e
System Action:
Event is updated
Action:
None
6162I
e flushed from Deferred queue
Reason:
Event e is taken off the deferred queue
System Action:
Event dequeued
Action:
None
6163I
e Execution bypass requested
Reason:
Bypass is requested
System Action:
Event e is bypassed
Action:
None
6100 - 6199
6164I
Event e cancelled by u
Reason:
Event e is cancelled by user u
System Action:
Event cancelled
Action:
None
6165I
Event e deleted by u
Reason:
Event e is deleted by user u
System Action:
Event deleted.
Action:
None
6170I
Backout processing moved
Reason:
Backout processing is moved
System Action:
Backout processing is moved
Action:
None
6100 - 6199
6171I
Default EICB created for class 0
Reason:
An internal control block is created
System Action:
An internal control block is created
Action:
None
6172I
Class c MPL level is l
Reason:
Class and MPL level setting
System Action:
Settings displayed
Action:
None
6173I
Created EICC for class c
Reason:
Class c is queued in the system
System Action:
Class c is defined
Action:
None
6100 - 6199
6174I
Deleted class c moved to class 0
Reason:
A deleted class is moved to the default class
System Action:
Class c elements moved to class 0
Action:
None
6175I
Event class c deleted n TDRs moved to class 0
Reason:
Class c is deleted
System Action:
TDRs are preserved in class 0
Action:
None
6176I
Created EICB for class c
Reason:
An event initiator class block is created
System Action:
Class c is associated with the EICB
Action:
None
6100 - 6199
6177I
Created EICC for class c
Reason:
An event initiator class checkpoint is created
System Action:
Class c is associated with the EICC
Action:
None
6178I
Altered class c MPL level to mpl
Reason:
The class MPL level is altered
System Action:
The MPL level is set to mpl
Action:
None
6190I
ESPLOG Message table loaded
Reason:
The table is loaded
System Action:
Loads the table
Action:
None
6100 - 6199
6191I
ESPLOG Message table active loaded from dsn
Reason:
Location of the table
System Action:
Load location
Action:
6192E
Command cccc invalid in message table
Reason:
The message log table contains an illegal command.
System Action:
The message table is not loaded.
Action:
Correct the table and reissue the LOADESPL command.
6193E
Self described text
Reason:
An error occurred allocating or opening a Message Table.
System Action:
The Message Table is not loaded. This message is followed by 6194E.
Action:
6100 - 6199
6194E
Above error occurred opening message table
Reason:
A LOADESPL command encountered an error allocating or opening a Message Table.
System Action:
The message table is not loaded
Action:
Ensure the table name was specified correctly and reissue the LOADESPL command.
6195E
Above error occurred reading message table
Reason:
An error occurred while reading a Message Table. The error is described in a previous
message.
System Action:
Action:
6196E
Invalid command syntax detected in line # of message table
Reason:
A Message Table contained a statement with invalid syntax.
System Action:
Action:
6100 - 6199
6197E
Above error occurred on line # of message table
Reason:
An error was detected in the Message Table. The error is described in a preceding
message
System Action:
Action:
6198W
SELECT RANGES MUST BE SPECIFIED AS VALUE PAIRS ORPHAN VALUE IGNORED;
ECIFIED AS VALUE PAIRS CONTINUING WITH GOOD VALUES
Reason:
An error was detected in the SELECT RANGE statement. For example, in SELECT
RANGE(6030:6040,6050), the value 6050 is ignored, since it is not part of a range pair.
SELECT RANGE(6030:6040,6050,6060) is also incorrect, since a pair must be separated
by a colon (:).
System Action:
The orphan value is ignored. Good values are processed.
Action:
6199E
INVALID MESSAGE NUMBER SPECIFIED
Reason:
Message numbers must be all numeric and 4 digits long including leading zeroes.
System Action:
The value is ignored.
Action:
6200 - 6299
6200 - 6299
6210I
RU length does not correspond to TTPBF
Reason:
Buffer length incompatible with received data length
System Action:
Data is ignored
Action:
6211I
RU length does not correspond to XME size
Reason:
Buffer length incompatible with received data length
System Action:
Data is ignored
Action:
6220I
x
Reason:
AF message
System Action:
AF message
Action:
None
6200 - 6299
6221W
Dependency loop found at the following jobs:
Reason:
The Global Job Map processor found that there is one or more than one dependency
loops exist among a group of jobs. Message 6222I will be followed to list that group of
jobs.
System Action:
Calculation of expected end time and critical path will not be done for the affected jobs.
If the listed jobs' dependency structure is modified, for example by inserting a job or by
forcing a job complete, calculation of expected end time and critical path will be
attempted again.
Action:
Correct the dependency loop.
6222I
j in application a.g
Reason:
This message follows message 6222W, to list one job found in the dependency loop. j is
the full name of a job, a is the application name and g is the generation number.
System Action:
n/a
Action:
Correct the dependency loop related to this job.
6230I
Command type command
Reason:
Command entered by operator
System Action:
Operator command
Action:
None
6200 - 6299
6240I
a purged from scoreboard
Reason:
The application is purged
System Action:
Scoreboard is cleaned up
Action:
None
6241I
a ADXE update failed
Reason:
Control block error
System Action:
ADXE is not updated
Action:
None
6242I
a purged from scoreboard
Reason:
The application is purged
System Action:
Scoreboard is cleaned up
Action:
None
6200 - 6299
6250I
Purging j in appl a because r
Reason:
Job is purged for reason r
System Action:
Job is purged
Action:
None
6260I
Job j in appl a resources satisfied
Reason:
Job j obtained needed resources
System Action:
Job is processed
Action:
None
6261E
Reason:
Error e is received
System Action:
AFM processing is terminated
Action:
None
6200 - 6299
6262I
Address addr added for unit ucb
Reason:
Unit ucb is added
System Action:
Unit ucb is added
Action:
None
6263E
Reason:
Transmission error
System Action:
Start resource monitoring processing is terminated
Action:
None
6264E
Reason:
Transmission error
System Action:
Stop resource monitoring processing is terminated
Action:
None
6200 - 6299
6270I
Extending scoreboard bookkeeping capacity for jobs/applications from b by i
Reason:
The capacity has being extended from b bits to b+I bits
System Action:
Capacity extended
Action:
None
6280I
e cycled by u
Reason:
The user has cycled event e
System Action:
Event cycled
Action:
None
6290I
Signal s by u
Reason:
User u has issued signal s
System Action:
Signal issued
Action:
None
6300 - 6399
6291I
Signal had pending elements and was forced
Reason:
The signal was force deleted.
System Action:
Signal deleted.
Action:
None.
6292I
XIOERROR
Reason:
Signal I/O error.
System Action:
Signal I/O error.
Action:
None
6300 - 6399
6310I
Symlib sl updated by u
Reason:
The symlib sl is updated by user u
System Action:
Symlib updated
Action:
None
6300 - 6399
6311I
Symlib sl defined by u
Reason:
The symlib sl is defined by user u
System Action:
Symlib defined
Action:
None
6312I
Symlib sl deleted by u
Reason:
The symlib sl is deleted by user u
System Action:
Symlib deleted
Action:
None
6350I
Special day d on date time defined in calendar c
Reason:
Details of the day that was defined
System Action:
Day is put in calendar
Action:
None
6300 - 6399
6360I
Special day d on date time deleted from calendar c
Reason:
Details of the day that was deleted
System Action:
Day is removed from calendar
Action:
None
6370I
Holiday d starting date time defined in calendar c
Reason:
Details of the day that was defined
System Action:
Day is put in calendar
Action:
None
6380I
Holiday d starting date time deleted from calendar c
Reason:
Details of the day that was deleted
System Action:
Day is removed from calendar
Action:
None
6300 - 6399
6390I
Calendar cal defined by u
Reason:
A new calendar is defined
System Action:
Calendar data updated
Action:
None
6395I
Calendar cal deleted by u
Reason:
A calendar is deleted
System Action:
Action:
None
6399I
Calendar cal altered by u
Reason:
Calendar attributes are altered
System Action:
Action:
None
6400 - 6499
6400 - 6499
6400I
(Modname) added to HZSADDCHECK
Reason:
A health check module (name modname) was added to the Health Checker.
System Action:
Check added
Action:
None
6401W
(Modname) previously added to HZSADDCHECK
Reason:
A health check module (name modname) was already added to the Health Checker.
System Action:
No change
Action:
None
6402I
Health Checker interface for mmmm monitoring is inactive
Reason:
The health check interface for mmmm monitoring did not initialize.
System Action:
No change
Action:
If Health Checker support is not installed in the system, this message can safely be
ignored. Otherwise, a module or modules may be absent from a linklist library which
enables Health Checker to initialize the checks.
6400 - 6499
6403E
(Modname) not found in Linklist
Reason:
The health check module (name modname) was not found in the system linklist and
cannot be activated.
System Action:
The health check module is missing and cannot be executed.
Action:
Add the indicated module to the linklist and restart the product.
6410I
HZSCHECK addnew function successful
Reason:
The health check was activated.
System Action:
Check activated.
Action:
None
6411E
HZSCHECK addnew function failure RC=retcode Reason=reason
Reason:
The health check was not activated.
System Action:
No change
Action:
Report error message to support.
6400 - 6499
6412W
GETMAIN Failure, Working storage could not be obtained. No health checks added
Reason:
A health check command failed due to lack of storage in the Health Check region.
System Action:
Check not added
Action:
Verify that there is sufficient storage in the Health Checker region.
6413W
HZSADDCK MACRO Failure. A request to add a check failed.
Reason:
A health check command failed.
System Action:
Check not added
Action:
See Health Check messages that are previous and subsequent to this message.
6414E
RTNCD = xx, RSNCD = rrrrrrrr, Check Name = nnnn
Reason:
A health check command failed. This is the associated return and reason code. xx is the
return code, rrrrrrrr is the reason code, and nnnn is the name of the check.
System Action:
Command failed
Action:
See Health Check messages and codes manual.
6400 - 6499
6415W
GETMAIN Failure, Working storage could not be obtained. No health checks added
Reason:
A health check command failed due to lack of storage in the Health Check region.
System Action:
Check not added
Action:
Verify that there is sufficient storage in the Health Checker region.
6416W
HZSADDCK MACRO Failure. A request to add a check failed.
Reason:
A health check command failed.
System Action:
Check not added
Action:
See Health Check messages that are previous and subsequent to this message.
6417E
RTNCD = xx, RSNCD = rrrrrrrr, Check Name = nnnn
Reason:
A health check command failed. This is the associated return and reason code. xx is the
return code, rrrrrrrr is the reason code, and nnnn is the name of the check.
System Action:
Command failed
Action:
See Health Check messages and codes manual.
6400 - 6499
6418I
IBM Health Checker not active
Reason:
The IBM Health Checker is not running in the system.
System Action:
None.
Action:
Check whether the IBM Health Checker should be running or not. If not, remove the
HEALTHCK parameter from parmlib.
6421E
The check was called with an unknown PQE Function Code (PQE_Function_Code) of x
Reason:
Internal error.
System Action:
The check is ignored
Action:
6422E
The check was called with an unknown Check Entry Code (PQE_Entry_Code) of x
Reason:
Internal error.
System Action:
Action:
6400 - 6499
6423E
The One Time Call Check does not expect parameters. The first 50 characters of the
invalid parameters are displayed
Reason:
Parameters were supplied with a onetime check
System Action:
The invalid parameters are displayed
Action:
Correct the input and retry.
6424I
System: system ASID: asid Time: date time Module Name Module Level
Reason:
Time and version information
System Action:
Check module information
Action:
None
6425I
Interval Check: Call#-count System-s ASID-asid Time- date time Check: Call#-count
System-s ASID-asid Time- date time # of SSIDs monitored
Reason:
Number of SSIDs being monitored
System Action:
Action:
None
6400 - 6499
6426E
Parameters have requested the check to ABEND.
Reason:
A severe internal error has occurred
System Action:
The check abends
Action:
6427E
The Parameters are not allowed for the One Time Check routine.
Reason:
Parameters were supplied with a onetime check
System Action:
Action:
6428E
The Parameters are incorrect. The first 50 characters of the incorrect value are
displayed.
Reason:
Bad parameters were passed to the check
System Action:
The parameters are either incorrect or have bad syntax. Previous values in effect
Action:
6400 - 6499
6429E
The Parameter string length in error. Length was x
Reason:
The string is not the correct length
System Action:
The parameter is ignored
Action:
Reissue the modify command.
6430E
Parameter has a syntax error
Reason:
Syntax is incorrect
System Action:
The parameter is ignored
Action:
Correct the parmlib member
6431I
The Parameters were changed. The check call count was changed by the user.
Reason:
The call count is reset
System Action:
The call count is reset
Action:
None
6400 - 6499
6432I
The Parameters were updated. The Subsys ID added was ssid
Reason:
The user requested the SSID to be added
System Action:
The id is added
Action:
None
6433W
The Local stack is out of space. Entry ignored.
Reason:
Internal error.
System Action:
The request is ignored
Action:
If the problem recurs report it to support
6434I
SSID x has been added
Reason:
A request to add a SSID was made
System Action:
The SSID is added
Action:
None
6400 - 6499
6435I
Monitored SSIDs
Reason:
Title
System Action:
None
Action:
None
6436I
SSID is status
Reason:
SSID display showing whether the subsystem ID is active or inactive
System Action:
None
Action:
None
6437I
SSID x monitoring terminated
Reason:
Monitoring is terminated
System Action:
SSID is removed from the monitor list
Action:
None
6400 - 6499
6438W
SSID x not found being monitored
Reason:
An attempt was made to delete a SSID but the SSID was not found
System Action:
Request is ignored
Action:
6439I
No SSIDs being monitored
Reason:
An attempt was made to delete a SSID but no SSIDs are being monitored
System Action:
Request is ignored
Action:
6440I
DSTrig Cell statistics display
Reason:
Statistics for the SSID are displayed
System Action:
None
Action:
None
6400 - 6499
6441I
Interval check Call # system ASID Time Number of SSIDs monitored
Reason:
Number of SSIDs being monitored
System Action:
Action:
None
6442I
SSID DSTRIG Statistics:
Reason:
Title
System Action:
None
Action:
None
6443I
SSID-ssid, Tcell-tcellid, Used n%, Current n, Max nn, Max used nn Overflow nnn
Reason:
Tcell statistics for the SSID are displayed, for example SSID-ssid, Tcell-STEPEND, Used
45%, Current 9, Max 20, Max used 20, Overflow 30 Tcells currently used are 45% or 9
Maximum Tcells allocated are 20 Maximum Tcells used since start are 20 Tcells used
above maximum (overflow) are 30
System Action:
None
Action:
None
6400 - 6499
6444I
SSID TCell Statistics:
Reason:
Title
System Action:
None
Action:
None
6445I
OPS/MVS PARAMETER ERROR, RC=rc, REASON=reascode
Reason:
OPS/MVS has encountered an error. The return code is rc and the reason code is
reascode.
System Action:
The system ignores the error.
Action:
Report the error only if the OPS/MVS function is required.
6446I
OPS/MVS STG MGT ERROR, RC=rc, REASON=reascode
Reason:
reascode.
System Action:
Action:
6400 - 6499
6447I
OPS/MVS INTERNAL ERROR, RC=rc, REASON=reascode
Reason:
reascode.
System Action:
Action:
6448W
HEALTH CHECK THRESHOLD VALUE INVALID. OPERAND IGNORED
Reason:
A specified Health Check threshold is invalid.
System Action:
The system ignores the error and uses the default value.
Action:
Correct the error and retry. The threshold value must be between 50 and 99.
6400 - 6499
6449I
HEALTH CHECK SETTINGS: THRESHOLD pp%,
INTERVAL ii MINS, PRODUCT ID "pid", DEBUG(d)
Reason:
pp is the current threshold value.
status is either blank or (DISPLAY ONLY ALLOWED)
ii is the interval between checks
pid is the product id, e.g. ESP
debug is {N|Y}
System Action:
None.
Action:
None. Note that the parameters can be set only once at ESP initialization. They can be
displayed subsequently.
6450I
HEALTH CHECK INTERFACE DISABLED
Reason:
The interface to the Health Checker has not been enabled.
System Action:
None.
Action:
Supply the HEALTHCK parameter in Parmlib.
6400 - 6499
6457I
OPERCKP: BY <userid> <oper_command_text>
Reason:
An OPER command <oper_command_text> was issued by a batch client under user ID
<userid>. The batch client is connected to a CA WA ESP Edition proxy subsystem with
ROUTING set to MASTER, and requesting OPER commands to be queued when the
proxy subsystem is not active or when the proxy is active but the XCF ROUTING
connection between the proxy and master is not active, via the ESP client QOPRCMDS
startup parameter or the "QOPRCMDS {YES}" command.
Note:
This message is written to the CA WA ESP Edition proxy subsystem AUDITLOG file.
System Action:
The CA WA ESP Edition proxy subsystem queues the OPER command to its checkpoint
data set until its XCF ROUTING connection to the master becomes active, and then
forwards the OPER command to the master.
6400 - 6499
Action:
The CA WA ESP Edition proxy subsystem's XCF ROUTING connection to the master
should be activated.
If the CA WA ESP Edition master subsystem is not active it should be started.
If the CA WA ESP Edition master subsystem is active, then to determine if there is an XCF
ROUTING connection between proxy and master, enter the following command to
either the proxy or master XCF DISPLAY ACTIVE
or
XCF D A
If there is no ROUTING connection entry then the XCF ROUTING service has either been
stopped or suspended in the proxy or master. Issue the following command to the proxy
and/or master to determine where the XCF ROUTING service was stopped or suspended
or
XCF D S
To re-activate the XCF ROUTING connection between the proxy and master enter the
following command where the XCF ROUTING service is not active (proxy or master) XCF START SERVICE ROUTING
or
XCF S S ROUTING
When the XCF ROUTING connection between proxy and master is established then any
OPER commands checkpointed by the proxy will be forwarded to the master for
processing.
6458W
OPERCKW: BY <userid> <oper_command_text>
Reason:
An OPER command <oper_command_text> was issued by a batch client under user ID
<userid>. The batch client is connected to a CA WA ESP Edition proxy subsystem with
ROUTING set to MASTER, and requesting OPER commands to be queued when the
proxy subsystem is not active or when the proxy is active but the XCF ROUTING
connection between the proxy and master is not active, via the ESP client QOPRCMDS
startup parameter or "QOPRCMDS {YES}" command.
Note:
This message is written to the CA WA ESP Edition proxy subsystem AUDITLOG file.
6400 - 6499
System Action:
The CA WA ESP Edition proxy subsystem attempts to queue the OPER command to its
checkpoint data set because its XCF ROUTING connection to the master is not active.
However, the checkpoint file is full, so it waits until checkpoint space becomes available
and then queues the OPER command to the checkpoint data set.
Action:
The CA WA ESP Edition proxy subsystem's XCF ROUTING connection to the master
should be activated.
If the CA WA ESP Edition master subsystem is not active it should be started.
If the CA WA ESP Edition master subsystem is active, then to determine if there is an XCF
ROUTING connection between proxy and master, enter the following command on
either the proxy or master XCF DISPLAY ACTIVE
or
XCF D A
If there is no ROUTING connection entry then the XCF ROUTING service has either been
stopped or suspended on the proxy or master. Issue the following command on the
proxy and/or master to determine where the XCF ROUTING service was stopped or
suspended XCF DISPLAY SERVICES
or
XCF D S
To re-activate the XCF ROUTING connection between the proxy and master enter the
following command where the XCF ROUTING service is not active (proxy or master) XCF START SERVICE ROUTING
or
XCF S S ROUTING
When the XCF ROUTING connection between the proxy and master is established then
any OPER commands checkpointed by the proxy will be forwarded to the master for
processing.
6400 - 6499
6459I
OPSMVS INTERFACE status {- OPSMVS INACTIVE}
Reason:
The interface to OPS/MVS is either ENABLED or DISABLED via a statement in Parmlib (
OPSMVS ENABLED({Y|N}) ). Additionally, if Parmlib specified ENABLED(Y) and OPS/MVS
is inactive or not installed on the target system, then "OPSMVS INACTIVE" will be
displayed.
System Action:
Info only.
Action:
Adjust the OPSMVS ENABLED value if the desired one is not set. If OPS/MVS was inactive
when ESP was initialized, the interface will be disabled until ESP is recycled.
6470W
OPSMVS ENABLED VALUE INVALID. DEFAULT OF N USED.
Reason:
The value specified for the OPSMVS ENABLED parm was not valid.
(Y|N)
System Action:
ENABLED is set to N
Action:
Alter the value in Parmlib to suit.
6500 - 6599
6500 - 6599
6500I
JOBTRAK: By userid ALTTJ for job jobname requested.
Reason:
The user has entered an ALTTJ command.
System Action:
Action:
N/A
6501E
CRITICAL ERROR, RUN ABORTED
Reason:
An unrecognized function has been requested.
System Action:
The program is terminated.
Action:
6502I
EXEC PARAMETERS SUPPLIED:
Reason:
A print of the Exec Card parameters supplied.
System Action:
None.
Action:
Information only.
6500 - 6599
6503E
func IS AN INVALID FUNCTION
Reason:
The requested function listed is not supported.
System Action:
Action:
6504E
FUNCTION NOT SUPPLIED; REQUIRED. RUN ABORTED.
Reason:
No function was requested.
System Action:
Action:
6505I
EXEC PARAMETERS IN USE:
Reason:
The parameters that the program will use.
System Action:
The program proceeds.
Action:
None.
6500 - 6599
6506E
ddname (INDD) MISSING
Reason:
The DD definition for INDD is missing.
System Action:
Action:
6507E
ddname (OUTDD) MISSING
Reason:
The DD definition for OUTDD is missing.
System Action:
Action:
6508I
COMPLETED COPY
Reason:
The function has completed.
System Action:
Action:
None.
6500 - 6599
6509E
COPY FUNCTION PARAMETER MISSING. COPY REQUIRES INDD, OUTDD, STARTDATE
AND ENDDATE
Reason:
A needed parameter is missing.
System Action:
Action:
6510E
DSNAME LOCATE FAILED FOR dd
Reason:
The program was unable to find the data set name associated with INDD dd
System Action:
Action:
6511E
DSNAME LOCATE FAILED FOR dd
Reason:
The program was unable to find the data set name associated with OUTDD dd
System Action:
Action:
6500 - 6599
6512E
DSNAME FOR indd AND outdd CANNOT BE IDENTICAL
Reason:
The two data sets supplied in INDD and OUTDD cannot be identical.
System Action:
Action:
6513E
OPEN FAILURE WHILE CHECKING DSNAMES
Reason:
While comparing INDD and OUTDD data set names, an open error was encountered.
System Action:
Action:
6514I
COMPLETED DELETE
Reason:
The requested function has completed.
System Action:
Action:
None.
6500 - 6599
6515E
DELETE FUNCTION PARAMETER MISSING. DELETE REQUIRES INDD, STARTDATE AND
ENDDATE
Reason:
System Action:
Action:
6516E
OPEN FAILURE FOR INDD dd
Reason:
Could not open INDD dd during the DELETE function.
System Action:
Action:
6517E
READ FAILURE ON INDD FILE dd
Reason:
A read operation failed on INDD dd during DELETE.
System Action:
Action:
6500 - 6599
6518E
COMPLETED ARCHIVE
Reason:
System Action:
Action:
None.
6519E
ERROR ENCOUNTERED DURING ARCHIVE COPY FUNCTION
Reason:
During the Copy processing of the Archive function, an error was encountered.
System Action:
Action:
Check the log for additional information.
6520E
ERROR ENCOUNTERED DURING ARCHIVE DELETE FUNCTION
Reason:
During the Delete processing of the Archive function, an error was encountered.
System Action:
Action:
6500 - 6599
6521E
ARCHIVE FUNCTION PARAMETER MISSING. COPY REQUIRES INDD, OUTDD,
STARTDATE AND ENDDATE
Reason:
System Action:
Action:
6522I
COMPLETED GENCSV
Reason:
System Action:
Action:
None.
6523E
GENCSV FUNCTION PARAMETER MISSING. COPY REQUIRES INDD, OUTDD, STARTDATE
AND ENDDATE
Reason:
System Action:
Action:
6500 - 6599
6524E
OPEN FAILURE ON OUTDD FILE dd
Reason:
An open to the CSV file failed.
System Action:
Action:
6525E
WRITE FAILURE ON OUTDD FILE dd
Reason:
A write to the CSV file failed.
System Action:
Action:
6526E
ERROR PROCESSING DD dd
Reason:
An error occurred while processing DD dd.
System Action:
Action:
6500 - 6599
6527E
DELETE RECORD FAILURE FOR RECORD KEY=key, DABRC=rc, DABERRCD=errcd
Reason:
A delete operation failed for record with key key.
System Action:
Action:
Note the rc and errcd and check your input.
6528E
ERROR WRITING CONTROL CARD
Reason:
An error occurred while writing control information.
System Action:
Action:
Check the definition for dd CONTROL and correct if needed.
6529E
OPEN ERROR ON DD CONTROL
Reason:
An error occurred while processing dd CONTROL.
System Action:
Action:
6500 - 6599
6530I
SEE DD PRINT FOR DETAILS
Reason:
Additional details can be found on dd PRINT.
System Action:
Action:
None.
6531I
nn RECORDS DELETED FROM indd
Reason:
Count of records deleted.
System Action:
Action:
None.
6532I
nn RECORDS COPIED FROM indd
Reason:
A count of the records copied.
System Action:
Action:
None.
6500 - 6599
6533I
nn RECORDS ARCHIVED TO outdd
Reason:
A count of the records archived.
System Action:
Action:
None.
6534I
nn RECORDS READ FROM indd
Reason:
A count of the records read.
System Action:
Action:
None.
6535I
nn RECORDS WRITTEN TO indd
Reason:
A count of the records written.
System Action:
Action:
None.
6500 - 6599
6551I
Data collection started on DATE at TIME
Reason:
Performance Metrics started collection at the indicated DATE and TIME.
System Action:
Performance Metrics started the collection of metric data.
Action:
None.
6552I
Metrics ON
Reason:
Performance Metrics collection has been started.
System Action:
Performance Metrics collection is started if not already active.
Action:
None.
6553E
Error during Metrics ON, Code=nn
Reason:
Performance Metrics ON request has failed. The code value will be one of the following:
8 - termination in process
12 - error opening the log file
Additional messages from the log file recorder will provide more detailed information
on why the log file could not be opened.
System Action:
The enable request is suppressed.
6500 - 6599
Action:
If the error is for "termination in process", then wait for Performance Metrics to shut
down before attempting to restart it. If the error is for a log file error, then correct the
problem and retry the request.
6554I
Metrics OFF
Reason:
Performance Metrics collection has been stopped.
System Action:
Performance Metrics collection is stopped if active.
Action:
None.
6555E
Error during Metrics OFF, Code=nn
Reason:
Performance Metrics stop processing has failed. An unexpected failure occurred during
Metrics stop processing.
System Action:
The disable request was not successful.
Action:
Report the problem to CA Support.
6556I
METRICS SET INTERVAL: nn
Reason:
The metrics collection interval has been set to nn minutes.
System Action:
Performance Metrics interval is set to the specified value.
6500 - 6599
Action:
None.
6557E
Invalid interval value: nn must be 1-10
Reason:
The metrics collection interval specified must be in the range of 1-10.
System Action:
The SET request is ignored.
Action:
Reissue the METRICS SET command with a valid value.
6558I
METRICS SET SIZE: nn
Reason:
The metrics collection repository size value is set to nn.
System Action:
Performance Metrics repository size is set to the specified value.
Action:
None.
6559E
Invalid size value: nn must be 1-120
Reason:
The metrics collection repository size specified must be in the range of 1-120.
System Action:
Action:
6500 - 6599
6560I
METRICS SET FREQUENCY: nn
Reason:
The metrics log file recording frequency is set to nn. The frequency value specifies the
number of repository update intervals that occur between each log file recording.
System Action:
Performance Metrics frequency is set to the specified value.
Action:
None.
6561E
Invalid frequency value: nn must be 1-30
Reason:
The metrics collection log file record frequency must be in the range of 0-30.
System Action:
Action:
6562I
Metrics recording disabled due to zero Frequency value
Reason:
If the frequency value is set to zero then the metrics are not recorded to the metrics log
file.
System Action:
The metrics are no longer recorded to the log file.
Action:
None.
6500 - 6599
6563I
METRICS SET LOGFILENAME: dsn
Reason:
The metrics collection log file data set name is set.
System Action:
Performance Metrics log file data set name is set to the specified value.
Action:
None.
6564I
Frequency must be less than Size. Size set to nn
Reason:
The Metrics repository must have a Size value that is larger than the Frequency value.
System Action:
The Metrics Size value is increased to Frequency + 1.
Action:
None.
6565I
METRICS SET can only be issued when Metrics is OFF
Reason:
The METRICS SET values can only be changed when the metrics system is OFF.
System Action:
Action:
Issue a METRICS OFF command, modify the desired SET parameters, and then issue a
METRICS ON command to restart metrics collection with the updated SET values.
6600 - 6699
6600 - 6699
6600I
Calling Dispatcher
Reason:
Internal trace point
System Action:
Info Only
Action:
None
6601I
APPL applname JOB jobname RESUBMITTED by user
Reason:
A job was resubmitted by the user
System Action:
Info Only
Action:
None
6602E
APPL applname JOB jobname INSUFFICIENT APPL STORAGE FOR RESUB PARMS
Reason:
Short on storage
System Action:
The requested action was not performed.
Action:
None
6600 - 6699
6603I
APPL applname JOB jobname INSERTED BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6604I
APPL applname JOB jobname Ended execution
Reason:
N/A
System Action:
Info Only
Action:
None
6605E
APPL applname JOB jobname FAILED APPL INSERTION FOR LACK OF SPACE
Reason:
Short on storage
System Action:
Action:
See message 1812
6600 - 6699
6606I
APPL applname JOB jobname HELD BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6607I
APPL applname JOB jobname RELEASED BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6608I
APPL applname JOB jobname REMOVED FROM JOB ANCESTOR WAIT BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6609I
APPL applname JOB jobname FORCED READY BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6610I
APPL applname JOB jobname FORCED COMPLETE BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6611I
APPL applname JOB jobname REQUESTED BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6612I
APPL applname JOB jobname USER STATUS UPDATED BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6613I
APPL applname JOB jobname UNREQUESTED BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6614I
APPL applname JOB jobname BYPASSED BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6615I
APPL applname JOB jobname UNBYPASSED BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6616I
APPL applname JOB jobname PARTIAL DEPENDENCIES DROPPED BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6617I
APPL applname JOB jobname DEPENDENCIES DROPPED BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6618I
APPL applname JOB jobname Resources dropped by user
Reason:
N/A
System Action:
Info Only
Action:
None
6619I
APPL applname JOB jobname TIMES RESET BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6620I
APPL applname ALL COMPLETED BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6621I
APPL applname ALL HELD BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6622I
APPL applname REMOVED FROM APPLWAIT BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6623I
APPL applname ALL RELEASED BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6624E
APPL applname JOB jobname Ended execution, failed
Reason:
The process was terminated
System Action:
Error
Action:
Check the job for errors
6625E
APPL applname JOB jobname Insufficient checkpoint space for APMR
Reason:
Short on storage
System Action:
Action:
None
6626I
APPL applname JOB jobname REMOVED FROM SUBAPPL WAIT BY user
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6627E
APPL applname JOB jobname is missing from RESFILE
Reason:
N/A
System Action:
Error
Action:
None
6628I
APPL applname REQUEST BY user failed authority check
Reason:
N/A
System Action:
Info Only
Action:
None
6629I
APPL applname NOW COMPLETE
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6630E
APPL applname JOB jobname Insufficient checkpoint space for APMR
Reason:
Short on storage
System Action:
Action:
None
6631I
APPL applname SUBAPPL applname now complete
Reason:
N/A
System Action:
Info Only
Action:
None
6632I
APPL applname JOB jobname BYPASSED, (NOT REQUESTED)
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6633I
APPL application JOB jobname READIED
Reason:
N/A
System Action:
Info Only
Action:
None
6634I
APPL applname SUBAPPL applname RELEASED BY ANCESTOR SUBAPPL
Reason:
N/A
System Action:
Info Only
Action:
None
6635I
APPL applname JOB jobname RELEASED BY ANCESTOR JOB
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6636E
APPL applname JOB jobname FAILED INFO/SYSTEM UPDATE FOR LACK OF SPACE
Reason:
The update was not done
System Action:
Error
Action:
See message 1037
6637E
APPL applname JOB jobname FAILED Status message insertion for lack of space
Reason:
The insertion was not performed
System Action:
Error
Action:
See message 1038
6638I
APPL applname JOB jobname LATE ENDING
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6639I
APPL applname JOB jobname LATE START TIME EXCEEDED
Reason:
N/A
System Action:
Info Only
Action:
None
6640I
APPL applname JOB jobname Now Complete
Reason:
N/A
System Action:
Info Only
Action:
None
6641E
APPL applname JOB jobname FAILED appl
Reason:
N/A
System Action:
Error
Action:
None
6600 - 6699
6642E
APPL applname JOB jobname Failed event parm update for lack of space
Reason:
System Action:
Error
Action:
See message 1047
6643I
APPL applname JOB jobname LATE SUBMIT TIME EXCEEDED
Reason:
N/A
System Action:
Info Only
Action:
None
6644I
APPL applname JOB jobname BYPASSED
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6645E
APPL applname JOB jobname FAILED APPL UPDATE FOR LACK OF SPACE
Reason:
System Action:
Error
Action:
See message 78
6646I
APPL applname JOB jobname Dependencies Abandoned
Reason:
N/A
System Action:
Info Only
Action:
None
6647I
APPL applname JOB jobname Resources abandoned
Reason:
N/A
System Action:
Info Only
Action:
None
6600 - 6699
6648E
APPL applname JOB jobname EXECUTION ABANDONED
Reason:
The process was terminated
System Action:
Error
Action:
None
6649I
RerunM command entered by userid for appl applid
Reason:
The rerunm command was entered
System Action:
The command is processed.
Action:
None
6650I
n jobs selected for rerun: job1, job2, ...job n
Reason:
The jobs which were selected for rerun are listed
System Action:
The command is processed.
Action:
None
6600 - 6699
6651W
REQUESTED GENERATION OF APPL xxxx NOT FOUND
Reason:
The requested application does not exist.
System Action:
Action:
6653I
APPL applname.gen JOB jobname WITHDRAWN BY user
Reason:
The job jobname was withdrawn in Application applname.
System Action:
None.
Action:
None.
6654I
APPL applname.gen WITHDRAWN BY user
Reason:
The generation number gen of Application applname was withdrawn.
System Action:
None.
Action:
None.
6600 - 6699
6655I
APPL applname.gen JOB jobname WITHDRAWN BY user
Reason:
Job jobname was withdrawn after a user issued a command to withdraw its
sub-application.
System Action:
None.
Action:
None.
6660I
MESSAGE SENT SUCCESSFULLY TO OPS/MVS, RC=retcode, REASON=reason
Reason:
Confirmation of message transfer with OPS/MVS. The return code and reason are
displayed.
System Action:
The requested message has been sent.
Action:
None
6661E
OPS/MVS PARAMETER ERROR, RC=retcode, REASON=reason
Reason:
An undefined error has occurred while connecting with OPS/MVS. The return code and
reason are displayed.
System Action:
The requested message has not been sent.
Action:
Make sure that OPS/MVS is fully initialized. Check the OPS/MVS log for errors.
6600 - 6699
6662E
OPS/MVS PARAMETER ERROR, RC=retcode, REASON=reason
Reason:
A parameter error has occurred while connecting with OPS/MVS. The return code and
reason are displayed.
System Action:
Action:
Make sure that OPS/MVS is fully initialized. Check the OPS/MVS log for errors.
6663E
OPS/MVS STG MGT ERROR, RC=retcode, REASON=reason
Reason:
OPS/MVS indicates an insufficient storage condition to process the request. The return
code and reason are displayed.
System Action:
Action:
Check the OPS/MVS log for errors.
6664I
OPS/MVS INACTIVE, RC=retcode, REASON=reason
Reason:
OPS/MVS is not active. The return code and reason are displayed.
System Action:
Action:
Determine why OPS/MVS is not running.
6600 - 6699
6665E
OPS/MVS INTERNAL ERROR, RC=retcode, REASON=reason
Reason:
OPS/MVS indicates an internal error has occurred. The return code and reason are
displayed.
System Action:
Action:
6666E
UNKNOWN ERROR, RC=retcode, REASON=reason
Reason:
OPS/MVS indicates an unknown error has occurred. The return code and reason are
displayed.
System Action:
Action:
6667E
SEND2OPS COMMAND LENGTH OF nnnn
EXCEEDS MAXIMUM LENGTH OF 4095 CHARS; COMMAND IGNORED
Reason:
The text of the SEND2OPS command exceeded the maximum allowed.
System Action:
Action:
Correct the command and resubmit.
6900 - 6999
6668E
SEND2OPS COMMAND HAS NULL TEXT; COMMAND IGNORED
Reason:
There was no text in the SEND2OPS command.
System Action:
Action:
Correct the command and resubmit.
6900 - 6999
6900I
ATR does not match a for event e: found atr
Reason:
Internal error.
System Action:
The ATR is discarded
Action:
None
6901I
Event e signal s lost/satisfied
Reason:
The event e signal is either lost or satisfied.
System Action:
Event signal status displayed
Action:
None
6900 - 6999
6902E
RESYNCH process is not allowed on proxy
Reason:
A user issued CALLRTN CYBESUDI RESYNCH command on a proxy.
System Action:
Action:
Re-issue the command on the master.
6903E
Invalid request code issued to Event Level Sensors executer
Reason:
System Action:
Request was not processed.
Action:
6904E
WOB Trigger {activation|termination|parms build} failed for event <event>
Reason:
WOB trigger function has failed.
System Action:
The WOB is not triggered.
Action:
Additional information on the nature of the error could be found in error messages
issued prior to that.
6900 - 6999
6905E
Event Level Sensors executer failed to allocate a WOB request block
Reason:
System Action:
The Event Level Sensors executer stops processing that WOB.
Action:
6906E
Event Level Sensors Manager is waiting for checkpoint file space
Reason:
Event Level Sensors manager has made an unsuccessful request for checkpoint file
space.
System Action:
The Event Level Sensors manager waits for checkpoint space to become available before
proceeding.
Action:
If the problem persists, attempt to determine the cause of the checkpoint file space
shortage condition.
6907E
Definition of event <event> failed. <reason>
Reason:
Definition of an event with the WOBTRIG command failed, due to an error returned
from the agent
System Action:
The WOBTRIG command in the event was marked as failed
Action:
Use the reason to determine the cause of the problem
6900 - 6999
6908E
WOBTRIG IS AVAILABLE ONLY BY CONNECTING TO A MASTER
Reason:
The event command WOBTRIG can be used only, if you're connected to a master.
System Action:
Action:
Use the ROUTING MASTER command to route the command to a master
6909E
WOBTRIG is not supported by selected workload object
Reason:
The workload object type used in the WOBTRIG command is not supported by the
WOBTRIG command.
System Action:
Action:
Delete the WOBTRIG command, or use a different workload object type.
6910E
Invalid {DELTA|SIZE|PERCENT} value
Reason:
The specified value of the printed keyword is invalid.
System Action:
Action:
Type a valid value.
6900 - 6999
6911E
<keyword> keyword is mandatory
Reason:
The printed keyword is missing in the command.
System Action:
Action:
Specify the missing keyword.
6912I
DEFINITION IS DELAYED UNTIL CONFIRMATION IS RECEIVED FROM THE AGENT
Reason:
The event definition needs to be confirmed by the agent due to the WOBTRIG command
in the event
System Action:
The event definition has been delayed.
Action:
Check the event status. If the status is 'WOBTRIG REJECTED', the agent rejected the
definition of the event and message 6907E was sent to the user. If the status is
'WOBTRIG IN PROGRESS', confirmation yet not received from the agent. If the status is
'REQUIRES WOB TRIGGER', the definition was confirmed and accepted by the agent.
6913E
Invalid object format <object>
Reason:
System Action:
The incoming message is ignored.
Action:
6900 - 6999
6914E
SensMGR: Event <prefix.name.tod> Communication error: <error>
Reason:
Event Level Sensors manager received a communication error while trying to send a
message to the agent
System Action:
The system tries to continue processing the event.
Action:
6915E
SensMGR: Request by <agent> failed authority check
Reason:
Event Level Sensors manager received an unauthorized message from an agent.
System Action:
Agent's message is ignored.
Action:
6916I
SensMGR: Processing WOBMSG <message>
Reason:
Event Level Sensors manager received a message from an agent
System Action:
The agent's message is being processed by the Event Level Sensors manager.
Action:
None required.
6900 - 6999
6917E
SensMGR: Reading of event <event> failed
Reason:
Event Level Sensors manager failed to read an event definition.
System Action:
The event is ignored.
Action:
6918W
SensMGR: Event <event> bypassed. Not confirmed by all agents
Reason:
Event Level Sensors manager received a message from an agent to trigger an event due
to a WOBTRIG command, but the event was yet not confirmed by all agents.
System Action:
Action:
Check the event status. If the status is 'WOBTRIG REJECTED', the agent rejected the
definition of the event and message 6907E was sent to the user. If the status is
'WOBTRIG IN PROGRESS', confirmation yet not received from the agent. If the status is
'REQUIRES WOB TRIGGER', the definition was confirmed and accepted by the agent.
6900 - 6999
6919I
SensMGR: Event <event> triggered by <agent> MNPoint(<WOB type>)
Status(<status>)
Reason:
Event Level Sensors manager received a message from an agent to trigger an event due
to a WOBTRIG command.
System Action:
Action:
None required.
6920I
SensMGR: Msg <WOB message>
Reason:
This message will follow an error message by the Event Level Sensors manager and it
describes a message sent to it by an agent.
System Action:
Processing continues - information only.
Action:
None required.
6921E
SensMGR: Error occurred reading event file <file-name>
Reason:
Event Level Sensors manager failed to read from the event file.
System Action:
The event is ignored.
Action:
6900 - 6999
6922E
SensMGR: Error in manager message format
Reason:
System Action:
Action:
6923E
Report Server is already active
Reason:
Report Server is already active.
System Action:
The operation was not performed.
Action:
Check the Report Server status using the RSERVER STATUS command.
6924E
Report Server is not active
Reason:
Report Server is not active.
System Action:
Action:
Check the Report Server status using the RSERVER STATUS command.
6900 - 6999
6925E
<operand> operand is valid only with the START operand
Reason:
The operand in error is valid only with the START operand of the RSERVER command.
System Action:
Action:
Add the START operand to the RSERVER command.
6926E
<operand1> operand is not allowed when <operand2> is specified
Reason:
The RSERVER command cannot be issued with both <operand1> and <operand2>
operands.
System Action:
Action:
Issue the command with either <operand1> or <operand2>, not both.
6900 - 6999
6927A
HISTFILE <histid> is closed. Type "I" to ignore updates, "R" to retry updates or "S" to
stop Report Server
Reason:
Report Server tried to read a record from the HISTFILE, but the file was closed or
suspended.
System Action:
The product waits for your reply. Options include the following:
Stops the Report Server from passing any HISTFILE updates from <histid> to the
database for the next hour R.
Causes the Report Server to attempt to resume passing HISTFILE updates from
<histid> to the database S.
Stops the Report Server
Action:
If HISTFILE cannot be opened, reply to this error message with "I". If HISTFILE can be
opened, do the following:
1.
Issue the HISTFILE OPEN command.
2.
Reply to this error message with "R".
If HISTFILE is only temporarily closed, do the following:

1.
Reply to this error message with "S".
2.
When the HISTFILE becomes available, start the Report Server.
For descriptions of the replies to this error message, see "System Action".
6928E
PROC or HOST operand must be specified
Reason:
The RSERVER START command was issued without the PROC or HOST operand.
System Action:
Action:
Issue the command with either the PROC or HOST operand.
6900 - 6999
6929W
Report Server tracking option is already active
Reason:
The RSERVER TRACK command was issued to start tracking HISTFILE updates for the
Report Server, but the tracking was already active.
System Action:
Action:
None
6930W
Report Server tracking option is not active
Reason:
The RSERVER NOTRACK command was issued to stop tracking HISTFILE updates for the
Report Server, but the tracking was already inactive.
System Action:
Action:
None
6931I
RServer: Report Server tracking started
Reason:
Tracking Manager started tracking HISTFILE updates for the Report Server.
System Action:
None
Action:
None
6900 - 6999
6932I
RServer: Report Server tracking stopped
Reason:
Tracking Manager stopped tracking HISTFILE updates for the Report Server.
System Action:
None
Action:
None
6933E
Error connecting to Report Server
Reason:
An error occurred while trying to connect to the Report Server.
System Action:
The connection to the Report Server was not established.
Action:
Check for prior error messages that could explain the current error.
6934E
Error sending <msg> message to Report Server
Reason:
An error occurred while trying to send a message to the Report Server.
System Action:
The message was not sent.
Action:
6900 - 6999
6935E
Error receiving message from Report Server
Reason:
An error occurred while trying to receive a message from the Report Server.
System Action:
The message was not received.
Action:
6936E
Invalid message length received from Report Server
Reason:
A message with invalid length was received from the Report Server.
System Action:
The message was ignored.
Action:
6937E
Invalid message keyword <keyword> received from Report Server
Reason:
A message with an invalid keyword was received from the Report Server.
System Action:
The message was ignored.
Action:
6900 - 6999
6938C
Report Server status: <status>
Reason:
This message displays the current status of the Report Server.
System Action:
None
Action:
None
6939W
No more HISTFILE update keys in queue
Reason:
The queue of HISTFILE update keys in the COMMQ file is empty.
System Action:
None
Action:
None
6940E
HISTFILE update key was not found
Reason:
A HISTFILE update key was not found in the COMMQ file after it was read from the
COMMQ file and sent to the Report Server.
System Action:
The confirmation of the HISTFILE update is ignored.
Action:
6900 - 6999
6941S
Tracking Manager stopped tracking HISTFILE updates for Report Server
Reason:
Tracking Manager stopped tracking HISTFILE updates for the Report Server because the
Report Server was not active for the past hour.
System Action:
HISTFILE updates are not passed to the Report Server.
Action:
Use the RSERVER STATUS command to check why the Report Server is not active. After
the problem is solved and the Report Server is active ,use the RSERVER TRACK command
to resume tracking. In addition, use the Report Server batch option to propagate
HISTFILE updates made while tracking was inactive.
6942E
Error saving HISTFILE update in COMMQ file for Report Server
Reason:
Tracking Manager failed to store a HISTFILE update for the Report Server in the COMMQ
file.
System Action:
The HISTFILE update was not passed to the Report Server.
Action:
6900 - 6999
6943E
Error using ASCRE, RC=<rc>, Reason=<rsn>
Reason:
The MVS ASCRE service failed. The product invoked the service to start the Report
Server address space.
System Action:
Report Server is not active.
Action:
Investigate the reason for the ASCRE error using the z/OS MVS Programming Authorized
Assembler Services Reference Vol1(ALESERV-DYNALLOC).
6944E
<error-desc>
Reason:
Error message as received from Report Server
System Action:
None
Action:
None
6945I
Report Server is now inactive
Reason:
The connection to the Report Server is closed.
System Action:
The product closed its connection to the Report Server due to a user request or a
system error.
Action:
If the connection to the Report Server was closed due to an error, check for prior error
messages that could explain the current error.
6900 - 6999
6946I
Report Server is now active
Reason:
The product opened a connection to the Report Server successfully and received a ready
indication from the server.
System Action:
None
Action:
None
6947E
Error removing HISTFILE update from COMMQ file for Report Server
Reason:
The product failed to remove a HISTFILE update from the COMMQ file after it was read
and sent to the Report Server.
System Action:
The confirmation of the HISTFILE update is ignored.
Action:
6948E
Incorrect HISTFILE update confirmation received from Report Server
Reason:
The product sent a HISTFILE update to the Report Server, but mistakenly received
confirmation of a different HISTFILE update from the Report Server.
System Action:
The product will resend the HISTFILE update to the Report Server again.
Action:
6900 - 6999
6949E
HISTFILE update confirmation was not received from Report Server
Reason:
The product sent a HISTFILE update to the Report Server, but did not receive
confirmation back from the server.
System Action:
The product will resend the HISTFILE update to the Report Server again.
Action:
None
6950E
Error reading next HISTFILE update from COMMQ file for Report Server
Reason:
The product failed to read the next HISTFILE update from the COMMQ file for the
Report Server.
System Action:
The product will reread the HISTFILE update from the COMMQ File.
Action:
6951E
Report Server failed to locate HISTFILE <histid>
Reason:
The product failed to locate a HISTFILE id.
System Action:
The HISTFILE update was not sent to the Report Server.
Action:
Check why the HISTFILE id is not defined to the product.
6900 - 6999
6952E
Report Server failed to read from HISTFILE <hist>
Reason:
Report Server failed to read a record from the HISTFILE.
System Action:
Action:
6953E
HISTFILE record for <job> <histid> not found by Report Server
Reason:
Report Server failed to locate a HISTFILE record in the file although the record key was
tracked and saved in the COMMQ file by Tracking Manager.
System Action:
Action:
6954E
THE COMMAND IS NOT ALLOWED AFTER THE SQL COMMAND
Reason:
If you have first used the SQL command, you cannot then use other history reporting
commands.
System Action:
Action:
Use only SQL query statements with the SQL command.
6900 - 6999
6955E
THE SQL COMMAND IS NOT ALLOWED WITH OTHER HISTORY REPORTING
COMMANDS
Reason:
You cannot use the SQL command if you have first used other History reporting
commands.
System Action:
Action:
Do not use the SQL command with other History reporting commands.
6956E
SQL STATEMENT EXCEEDS MAXIMUM SUPPORTED LENGTH
Reason:
The SQL statement exceeded the maximum length supported by the product.
System Action:
The report is not generated.
Action:
Use an SQL client to generate the report.
6957I
SensMGR: WOBTRIG confirmation received for event <event>
Reason:
Event Level Sensors manager received a WOB trigger confirmation message from an
agent.
System Action:
The WOB trigger confirmation is being processed by the Event Level Sensors manager.
Action:
None required.
6900 - 6999
6958E
Procedure Caching output truncated
Reason:
Ad hoc command failed to retrieved the application text from Procedure Caching. The
cache is needed because the TEMPPROC command is used in the event definition.
System Action:
Action:
Enlarge the APPLBUF parameter in the startup parameters.
6959E
Unexpected HISTFILE update confirmation received from Report Server
Reason:
The product received a HISTFILE update confirmation from the Report Server, but no
confirmation was expected from the server.
System Action:
The HISTFILE update confirmation is ignored.
Action:
6960E
Invalid request code issued to Report Server executer
Reason:
System Action:
Request was not processed.
Action:
6900 - 6999
6961E
Invalid HISTFILE record type <type> tracked for Report Server
Reason:
The product tracked a HISTFILE update with an invalid record type.
System Action:
The HISTFILE update is ignored.
Action:
6962E
<operand> OPERAND IS MISSING
Reason:
The <operand> was not specified with the RSERVERB command.
System Action:
The RSERVERB command is ignored.
Action:
Correct the RSERVERB command by adding the missing <operand>.
6963E
NOT IN BATCH MODE
Reason:
The user attempted to enter a RSERVERB command while in page mode.
System Action:
Action:
The RSERVERB command can run only under batch mode.
6900 - 6999
6964E
Access to RSERVERB denied by security system
Reason:
The user attempted to enter the RSERVERB command, but access to the command was
denied by the security system.
System Action:
Action:
Obtain access to the RSERVERB command resource and re-enter the command.
6965E
<i/o error message>
Reason:
An I/O error occurred while opening or reading a record from the Report Server parmlib
member (STDENV DD statement).
System Action:
Action:
Use the message text to understand the problem with the STDENV DD statement.
6966E
MISSING <parameter> IN STDENV
Reason:
The <parameter> was not found in the Report Server parmlib member.
System Action:
Action:
Make sure that the STDENV DD statement of the job you're running, points to the
correct Report Server parmlib member, and that the missing <parameter> is specified in
that member.
6900 - 6999
6967E
NOT A MASTER ESP SUBSYSTEM. USE SYSID OPERAND TO PROVIDE ESP SYSTEM ID
Reason:
The RSERVERB command was not executing under a master system, but the SYSID
operand was not specified.
System Action:
Action:
If you attempted to run the RSERVERB command under a master system, then make
sure you typed the correct subsystem name in the SUBSYSTEM operand inside your JCL.
Otherwise, if you cannot run the RSERVERB command under a master system, then add
the SYSID operand to the RSERVERB command to specify the master system ID. The
correct master system ID can be copied from the SYSID command located in the
ESPPARM parmlib member of the master system.
6968E
UNABLE TO LOCATE ESP SYSTEM ID
Reason:
The RSERVERB command failed to locate the system ID.
System Action:
Action:
The RSERVERV command requires the subsystem to be up and running. Check why the
subsystem is not active, and wait for the subsystem to initialize.
6900 - 6999
6969E
<i/o error message>
Reason:
An I/O error occurred while opening or writing a record to the Report Server batch
environment variables file (ESPBENV DD statement).
System Action:
Action:
Use the message text to understand the problem with the ESPBENV DD statement.
6970E
<event definition failure long status>
Reason:
Definition of an event with the WOBTRIG command failed, due to an error returned
from the agent
System Action:
The WOBTRIG command in the event was marked as failed
Action:
Use the reason to determine the cause of the problem
6971I
RServer: Report Server is active
Reason:
The Report Server RSERVER command was issued with the START operand
System Action:
None
Action:
None
6900 - 6999
6972I
RServer: Report Server is inactive
Reason:
The Report Server RSERVER command was issued with the STOP operand
System Action:
None
Action:
None
6973I
RServer: <error>
Reason:
An error message received from the Report Server
System Action:
The connection to the Report Server was closed
Action:
Correct the error and then start the Report Server
6974E
Connection prematurely closed by partner
Reason:
The Report Server closed its connection to subsystem
System Action:
The TCP/IP socket is closed
Action:
Check the Report Server job log to understand why the connection was closed
6900 - 6999
6975E
JOBMAP OPERAND 'DISPLAY' IS MISSING
Reason:
A JOBMAP command with the CSV operand was specified, but the required DISPLAY
operand was missing.
System Action:
Action:
Add the DISPLAY operand and reissue the command.
6976E
INVALID DISPLAY KEYWORD <keyword>
Reason:
A JOBMAP command with the DISPLAY operand was specified, but the <keyword> in the
DISPLAY list did not correspond to a valid keyword.
System Action:
Action:
Correct the JOBMAP command and reissue it.
6977E
Undefined workload object type 'xx'
Reason:
A workload object type is unknown to the product
System Action:
Processing bypassed for the unknown workload object type.
Action:
Ensure that the workload object type is properly defined using the WOBDEF command
in the parmlib member.
6900 - 6999
6978E
DISPLAY IS MUTUALLY EXCLUSIVE WITH NODISPLAY
Reason:
A JOBMAP command specified both the NODISPLAY and DISPLAY operands.
System Action:
Action:
Remove the NODISPLAY operand and reissue the command.
6979E
ADHOC COMMAND IS INVALID FOR A COMPLETE APPLICATION
Reason:
The ADHOC command was issued for a complete application.
System Action:
6980I
APPLICATION TRACKING DEFINITION TABLE LOADED
Reason:
A LOADATDT command was successfully executed.
System Action:
The new application tracking definition table is now active.
Action:
None.
6900 - 6999
6981I
APPLICATION TRACKING DEFINITION TABLE ACTIVE, LOADED FROM <dataset>
Reason:
In response to a LOADATDT statement or command, an application tracking definition
table was loaded from the specified data set and made active.
System Action:
The application tracking definition table will be used to control application tracking.
6982E
COMMAND <command> INVALID IN APPLICATION TRACKING DEFINITION TABLE
Reason:
An Application Tracking Definition Table contained an invalid command.
System Action:
The Application Tracking Definition Table is not loaded.
Action:
Correct the table and reissue the LOADATDT command.
6983E
xxxx
Reason:
An error occurred allocating or opening an Application Tracking Definition Table. The
message text is self describing.
System Action:
The Application Tracking Definition Table is not loaded. This message is followed by
message 6984E.
Action:
6900 - 6999
6984E
ABOVE ERROR OCCURRED OPENING APPLICATION TRACKING DEFINITION TABLE
Reason:
A LOADATDT command encountered an error allocating or opening an Application
Tracking Definition Table. The preceding message describes the error.
System Action:
Action:
Ensure the table name was specified correctly and reissue the LOADATDT command.
6985E
ABOVE ERROR OCCURRED READING APPLICATION TRACKING DEFINITION TABLE
Reason:
An error occurred while reading in an Application Tracking Definition Table. The error is
System Action:
Action:
After the error is corrected, reissue the LOADATDT command.
6986E
INVALID COMMAND SYNTAX DETECTED IN LINE nn OF APPLICATION TRACKING
DEFINITION TABLE
Reason:
An Application Tracking Definition Table contained a statement with invalid syntax.
System Action:
Action:
Correct the table definition and reissue the LOADATDT command.
6900 - 6999
6987E
ABOVE ERROR OCCURRED ON LINE nn OF APPLICATION TRACKING DEFINITION TABLE
Reason:
An error was detected in an Application Tracking Definition Table statement. The error
is described in a preceding message. This message indicates the line number containing
the error.
System Action:
Action:
Correct the error and reissue the LOADATDT command.
6988E
Reason:
A WILDCARD statement in an Application Tracking Definition Table had an invalid
character range.
System Action:
Action:
6989E
Reason:
An Application Tracking Definition Table was being loaded. The table contained more
than 60 WILDCARD statements.
System Action:
Action:
7000 - 7099
6990E
HISTFILE IS MISSING
Reason:
An Application Tracking Definition Table was being loaded. The table contained an
APPTRACK command without the HISTFILE operand.
System Action:
Action:
7000 - 7099
7000E
Reason:
An undefined command name was entered as a CA Workload Automation Restart
Option EE command.
System Action:
The command is ignored. The TSO user is prompted for a new command.
Action:
A TSO user should reenter the command with the correct name. A batch user should
correct the command for the next execution.
7000 - 7099
7001W
RC nn WHILE OPENING ENCORE EXH FILE IN CYBRM314
Reason:
CA Workload Automation Restart Option EE was unable to open the EXH file.
System Action:
The EXH file will not be updated by CA Workload Automation Restart Option EE.
Action:
Make sure that the EXH file has been allocated and formatted, and that its name is
specified in the EXHFILE statement in the initialization parameters.
7002W
RC nn WHILE READING SLOT 0 IN CYBRM314
Reason:
The EXH file has not been properly formatted.
System Action:
Action:
7003W
ENCORE EXH FILE SLOT ZERO IN ERROR
Reason:
The EXH file has either not been formatted or has been damaged.
System Action:
Action:
7000 - 7099
7004W
ENCORE EXH FILE USAGE IS BECOMING CRITICAL (nn% FULL)
Reason:
The EXH file has exceeded the "high" threshold value specified in the CYBRMTHR sample
job.
System Action:
None.
Action:
Run the CYBRMPRG sample job to remove unneeded records from the file.
7005W
ENCORE EXH FILE USAGE REMAINS CRITICAL (nn% FULL)
Reason:
The 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.
Action:
Run the CYBRMPRG sample job to remove unneeded records from the file.
7006I
ENCORE EXH FILE SHORTAGE IS NOW RELIEVED (nn% FULL)
Reason:
The EXH file is now lower than the "high" threshold value specified in the CYBRMTHR
sample job.
System Action:
None.
Action:
None.
7000 - 7099
7010I
ESP ENCORE (SUBSYS=xxxx) ALREADY ACTIVE
Reason:
The CA Workload Automation Restart Option EE system is already active.
System Action:
None.
Action:
None.
7011I
ESP ENCORE (SUBSYS=xxxx) ACQUIRING EXHVT
Reason:
The CA Workload Automation Restart Option EE subsystem is allocating an EXHVT
control block. This informational message is issued when the CA Workload Automation
Restart Option EE subsystem is starting for the first time since the last IPL.
System Action:
None.
Action:
None.
7012I
ESP ENCORE (SUBSYS=xxxx) PC NUMBER yyyy
Reason:
The CA Workload Automation Restart Option EE subsystem has chosen a PC number.
This informational message is issued when the CA Workload Automation Restart Option
EE subsystem is starting for the first time since the last IPL.
System Action:
None.
Action:
None.
7000 - 7099
7013S
ESP ENCORE (SUBSYS=xxxx) CROSS MEMORY ENV COULD NOT BE ESTABLISHED
Reason:
CA Workload Automation Restart Option EE was not able to establish a cross memory
environment.
System Action:
CA Workload Automation Restart Option EE is not properly started.
Action:
Please contact CA Support.
7014I
ESP ENCORE (SUBSYS=xxxx) NOW ACTIVE
Reason:
CA Workload Automation Restart Option EE is now active.
System Action:
None.
Action:
None.
7015I
ESP ENCORE (SUBSYS=xxxx) IMMEDIATE SHUTDOWN
Reason:
An immediate shutdown of the auxiliary address space has been requested.
System Action:
The auxiliary address space will shut down.
Action:
None.
7000 - 7099
7020W
ESP ENCORE (SUBSYS=xxxx) n EXH REQUESTS QUEUED
Reason:
The CA Workload Automation Restart Option EE 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.
Action:
Investigate possible causes for the backlog. CA Workload Automation Restart Option EE
may be quiesced, or the Workload Manager subsystem may be down.
7021I
ESP ENCORE (SUBSYS=xxxx) EXH REQUEST QUEUE NOW OKAY
Reason:
The system previously issued message 7020W indicating a possible problem with CA
Workload Automation Restart Option EE. The queue length has now fallen below 80% of
the threshold value.
System Action:
None.
Action:
None.
7000 - 7099
7022E
ESP ENCORE (SUBSYS=xxxx) EXH REQUEST FAILED
Reason:
The CA Workload Automation Restart Option EE subsystem has rejected a request from
this job to queue information to CA Workload Automation Restart Option EE. This is
generally caused by exhaustion of virtual storage in the auxiliary address space.
Message 7020W is issued long before this stage is reached, but may not have been
responded to.
System Action:
If this happens during processing of the CA Workload Automation Restart Option EE
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.
Action:
Investigate possible causes for the backlog. CA Workload Automation Restart Option EE
may be quiesced, or the Workload Manager subsystem may be down.
7030I
ESP ENCORE (COMPRESSING) (QUIESCED)
Reason:
This message is in response to the ENCPARM STATUS operator command. It indicates
whether or not CA Workload Automation Restart Option EE is compressing records and
whether or not it is quiesced.
System Action:
None.
Action:
None.
7000 - 7099
7031E
THE AUXILIARY ADDRESS SPACE HAS NOT BEEN PROPERLY INITIALIZED
Reason:
The PC numbers in the Workload Manager auxiliary address space are zero.
System Action:
The job is not recorded in the EXH file, and can therefore not be tracked by CA Workload
Automation Restart Option EE nor restarted.
Action:
Contact CA Support.
7032E
THE AUXILIARY ADDRESS SPACE HAS RESPONDED RC=<rc> TO A PC0
Reason:
CA Workload Automation Restart Option EE 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 EXH file, and can therefore not be tracked by CA Workload
Automation Restart Option EE nor restarted.
Action:
Contact CA Support.
7000 - 7099
7033E
THE WRONG ESP SYSTEM HAS BEEN IDENTIFIED
Reason:
The XASV control block contains the incorrect job number. This usually results from CA
Workload Automation Restart Option EE not finding the correct Workload Manager
system with which to track this job.
System Action:
The job is not fully recorded in the EXH file, and can therefore neither be tracked by CA
Workload Automation Restart Option EE nor restarted.
Action:
Rerun the job with ENCPARM TRACE CYBRM501. This will add some diagnostic output to
the CA Workload Automation Restart Option EE report. This output will indicate which
Workload Manager system has been identified as the one with which the job should be
tracked. Once this output has been produced, please contact CA Support for further
assistance.
7034E
AN ERROR HAS OCCURRED WITH SMF INTERCEPTION
Reason:
The XASVNOTR switch is turned off, so that Workload Manager is not tracking this job.
This can result from the wrong Workload Manager system being identified or from a
problem with SMF interception.
System Action:
The job is not fully recorded in the EXH file, and can therefore not be tracked by CA
Action:
Recycle Workload Manager with the RELOAD option and rerun the job. If the problem
persists then contact CA Support.
7000 - 7099
7035E
Reason:
The XASV control block contains no ALD pointer. This usually results from the SMF
intercept routine not operating correctly.
System Action:
Action:
7036E
Reason:
The ALD that is pointed to by the XASV is invalid. This usually results from the SMF
intercept routine not operating correctly.
System Action:
Action:
7000 - 7099
7037E
JOB <jobname> #(<jobnum>) IS TOO LARGE, RESTART IMPOSSIBLE
Reason:
The job is too large to be restarted. The job processes too many files. The total number
of files includes both those allocated using DD JCL statements and those allocated
dynamically. CA Workload Automation Restart Option EE'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, CA Workload Automation Restart Option EE cannot
continue and issues this message.
System Action:
The restart of the job is abandoned. User is notified.
Action:
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)
Reason:
Part of series of informational messages written to the CA Workload Automation Restart
Option EE job log.
System Action:
N/A
Action:
N/A
7000 - 7099
7041I
ORIGINALLY RUN AT time ON date
Reason:
Option EE job log.
System Action:
N/A
Action:
N/A
7043I
(THIS JOB WAS ITSELF A RESTART OF JOB Jjobnumber)
Reason:
Option EE job log.
System Action:
N/A
Action:
N/A
7044I
RESTARTING FROM STEP stepname
Reason:
Option EE job log.
System Action:
N/A
Action:
N/A
7000 - 7099
7045I
TO STEP stepname
Reason:
Option EE job log.
System Action:
N/A
Action:
N/A
7060E
RACINIT FOR USER xxxx FAILED, ERROR CODE yy-zz
Reason:
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-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 Workload Manager
8-104 - Second copy of new password doesn't match first
System Action:
Action:
Compare the error code to the error codes associated with the installation's security
facility.
7000 - 7099
7070E
Execution halted because of an error in an ESP Encore command
Reason:
A Workload Manager system was processing an ENCREQ request and encountered an
error after executing a CA Workload Automation Restart Option EE command invoked
by this request.
System Action:
The ENCREQ request is stopped.
Action:
Look for relevant messages in the command execution summary and, if appropriate,
re-issue the corrected command.
7071I
ESP ENCORE COMMAND: xxxx
Reason:
A Workload Manager was processing an ENCREQ request that invoked the CA Workload
Automation Restart Option EE command displayed in this message.
System Action:
Action:
None.
7000 - 7099
7080E
Reason:
System Action:
Action:
respectively.
7081E
CPEENQ ERROR: Invalid xxxx specification: yyyy
Reason:
Argument xxxx in an ENCREQ command contains the invalid value yyyy.
System Action:
Action:
7000 - 7099
7082E
ENCREQ ERROR: <error message>
Reason:
An error occurred during the processing of an ENCREQ command.
System Action:
Action:
message.
7083I
ENCREQ INFO: <informational message>
Reason:
This message contains diagnostic information about the outcome of an ENCREQ
command.
System Action:
Action:
None.
7084E
TOO MANY EXCLUDED STEPS: nn
Reason:
The number of excluded steps in an ENCREQ command exceeds the limit established for
the AJ command.
System Action:
Action:
Reduce the number of items in the excluded-step list and re-issue the command.
7000 - 7099
7085E
PREVTIME invalid: xxxx
Reason:
An ENCREQ command contains an invalid value for the PREVTIME argument.
System Action:
Action:
Correct the value of the PREVTIME argument and re-issue the command.
7086E
The CA WA ESP Edition does not support the ENCREQ command: <reason>
Reason:
An ENCREQ subsystem request cannot be relayed to the Workload Manager because
the Workload Manager is not equipped to process the request.
System Action:
The subsystem request is not processed.
Action:
Switch to a Workload Manager that does support the ENCREQ subsystem request.
7090E
ESP ENCORE UI Service error - Subsystem error xx-yy
Reason:
A request was made to the Workload Manager subsystem, but an error occurred. xx is
the value returned in register 15 by program CYBSS005 and yy is the value of
XSCMRETCD.
System Action:
Action:
7000 - 7099
7091E
ESP ENCORE UI Service error - Subsystem request failed: aa bb, ERROR CODE cc-dd
Reason:
A request was made to the Workload Manager 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.
System Action:
Action:
7092E
ESP ENCORE UI Service error - A required record could not be read from a slot file
Reason:
A subsystem request failed because an error occurred when the Workload Manager
tried to read a slot-file record. The desired record may have been freed or reused.
System Action:
Action:
Re-issue the request. If the error persists, contact CA Support.
7093E
ESP ENCORE UI Service error - <error message>
Reason:
An error occurred during the processing of an ENCREQ subsystem request.
System Action:
Action:
Decide how to proceed based on the error message.
7000 - 7099
7094E
ESP ENCORE UI Service error - Serialization-control error - aaaa failure:
TOKEN(token) <reason> Flags: Error=X'bbbb' Info=X'cccc'
Reason:
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:
Action:
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
Reason:
The Network Delivery Services were unable to route a request to a destination
disconnected or a time-out may have occurred in the network or in a Workload
Manager.
System Action:
Action:
7000 - 7099
7096E
ESP ENCORE UI Service error - Requested generation aa of application bb not found
Reason:
The ATR (Application Tracking Record) for generation aa of application bb could not be
retrieved.
System Action:
Action:
7097E
ESP ENCORE UI Service error - Application-level data not found for job aa in
application bb, generation cc
Reason:
The AJQE (Application Job Queue Element) for job aa of application bb, generation cc
could not be retrieved.
System Action:
Action:
Ensure you have specified the correct application name, generation number, and job
name.
7100 - 7199
7099I
DDN=xxxxxxxx RC=n ERROR=yyyy INFO=zzzz
Reason:
The auxiliary address space has completed initialization, and attempted to deallocate
the task library from which modules were potentially fetched. This allocation is identical
to the STEPLIB provided in the Workload Automation 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.
Action:
If this message is issued, you may wish to investigate the meaning and cause of the
indicated unallocation condition.
7100 - 7199
7100W
EXH data set xxxx is not properly formatted
Reason:
The Execution History file is not formatted. This is expected the first time the data set is
used.
System Action:
CA Workload Automation Restart Option EE follows with message 7101.
Action:
7100 - 7199
7101A
Reply 'Y' to format the EXH file, or reply 'N'
Reason:
The EXH file was found to be unformatted, or improperly formatted. Before proceeding
to format it, CA Workload Automation Restart Option EE requests permission from the
operator.
System Action:
CA Workload Automation Restart Option EE waits for the reply.
Action:
If you wish the EXH file to be formatted, reply Y, otherwise reply N and CA Workload
Automation Restart Option EE 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
Reason:
System Action:
Action:
7103I
OK
Reason:
System Action:
None.
Action:
None.
7100 - 7199
7104E
Correct the above problem and restart ESP
Reason:
This message is issued after an error has occurred that prevents further execution of
Workload Manager. This message would have been preceded by another describing the
error.
System Action:
Workload Manager terminates.
Action:
After the problem has been corrected, you may restart Workload Manager.
7104I
Starting to format the EXH file
Reason:
The formatting run of the EXH file has begun. You may expect this to take an
System Action:
The EXH file is formatted.
Action:
None. Be patient.
7106I
EXH file format complete
Reason:
The formatting run of the EXH file has been completed.
System Action:
Action:
None.
7100 - 7199
7116I
ESP ENCORE QUIESCE IN PROGRESS. EXH FILE USE COUNT: nn
Reason:
An ENCPARM QUIESCE command has been issued to a Workload Manager, but the EXH
file is currently in use by one or more process in the Workload Manager's address space.
System Action:
The CA Workload Automation Restart Option EE task that executes the ENCPARM
QUIESCE logic in the Workload Manager's address space waits for the EXH file use count
to drop to zero.
Action:
Wait for the ENCPARM QUIESCE to take effect.
7117I
EXH FILE INCOMPLETEKEEP= PARAMETER CHANGED FROM nn TO nn
Reason:
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.)
System Action:
None.
Action:
None.
7100 - 7199
7118I
EXH FILE AGE= PARAMETER CHANGED FROM nn TO nn
Reason:
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.)
System Action:
None.
Action:
None.
7119I
EXH FILE INCOMPLETEAGE= PARAMETER CHANGED FROM nn TO nn
Reason:
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.)
System Action:
None.
Action:
None.
7100 - 7199
7120W
EXH FILE INDEX DAMAGE HAS BEEN CORRECTED AFTER JOB xxxx
Reason:
CA Workload Automation Restart Option EE has detected corruption within an EXH file
index record. That damage has now been corrected.
System Action:
None.
Action:
If several different systems are sharing an EXH file, make sure that the Workload
Automation QNAMEs are correctly defined to GRS and/or MIM.
7121W
EXH FILE INDEX DAMAGE HAS BEEN CORRECTED FOR JOB xxxx
Reason:
index record. That damage has now been corrected.
System Action:
None.
Action:
If several different systems are sharing an EXH file, make sure that the Workload
Automation QNAMEs are correctly defined to GRS and/or MIM.
7100 - 7199
7122I
EXH FILE KEEP= PARAMETER CHANGED FROM nn TO nn
Reason:
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.)
System Action:
None.
Action:
None.
7123W
THE EXH FILE CONTAINS xxxx ENTRIES FOR JOB yyyy (LOOP-SAFEGUARD LIMIT IS zzzz)
Reason:
CA Workload Automation Restart Option EE 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, CA
Workload Automation Restart Option EE 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.
Action:
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.
7100 - 7199
7124I
ESP ENCORE PREVIOUSLY IN QUIESCED STATE
Reason:
This message may appear when Workload Manager is restarted. It means that CA
Workload Automation Restart Option EE was in a quiesced state when the Workload
Manager was previously shut down.
System Action:
CA Workload Automation Restart Option EE remains quiesced.
Action:
To restart CA Workload Automation Restart Option EE, issue an ENCPARM RESTART
command.
7125I
ESP ENCORE IS ALREADY QUIESCED
Reason:
An ENCPARM QUIESCE command has been issued by an operator, or by a user as an
OPER command, but CA Workload Automation Restart Option EE is already quiesced.
System Action:
None.
Action:
None.
7100 - 7199
7126I
ESP ENCORE IS NOW QUIESCED
Reason:
The CA Workload Automation Restart Option EE 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. CA
Workload Automation Restart Option EE has now completed the execution of the
request, and is now quiesced. Requests will be accumulated in the auxiliary address
space until CA Workload Automation Restart Option EE's recording function is restarted.
Note: The quiesced state will be remembered across restarts of Workload Automation
but not across an IPL.
System Action:
None.
Action:
When appropriate, issue an ENCPARM RESTART command. If CA Workload Automation
Restart Option EE 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
Reason:
An ENCPARM RESTART command has been issued by an operator, or by a user as an
OPER command. However, CA Workload Automation Restart Option EE is not quiesced,
so that it doesn't need to be restarted.
System Action:
None.
Action:
None.
7100 - 7199
7128E
UNABLE TO REALLOCATE EXH FILE
Reason:
OPER command. However, CA Workload Automation Restart Option EE is unable to
allocate the EXH file.
System Action:
None. CA Workload Automation Restart Option EE remains quiesced.
Action:
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
Reason:
OPER command.
System Action:
CA Workload Automation Restart Option EE is restarted. Activity to the EXH file has
been resumed.
Action:
None.
7130E
XSSV IS INVALID. BACKGROUND TASKS CANNOT START
Reason:
The Workload Manager environment has been corrupted.
System Action:
CA Workload Automation Restart Option EE is not started.
Action:
Recycle Workload Manager with PURGE.
7100 - 7199
7131E
THE WRONG VERSION OF ESP ENCORE IS ACTIVE IN THE AUXILIARY ADDRESS SPACE
Reason:
Version 2 of CA Workload Automation Restart Option EE has been installed, but an older
version created the existing auxiliary address space.
System Action:
Action:
Recycle Workload Manager with PURGE.
7132E
PLEASE SHUT DOWN THE AUXILIARY ADDRESS SPACE AND THEN RECYCLE ESP
Reason:
Follows message 7131.
System Action:
Action:
Issue the AUX_AS CANCEL command. Then, recycle Workload Manager.
7100 - 7199
7140I
ESP ENCORE EXH FILE ERROR <rc> WHILE <operation>
Reason:
An error has occurred while updating the EXH file.
<operation> - Indicates what I/O operation was being performed.
<rc> - 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 CA Support.
System Action:
I/O activity with the EXH file is suspended.
Action:
Quiesce CA Workload Automation Restart Option EE, correct the problem with the EXH
file, and then restart CA Workload Automation Restart Option EE. The commands to use
are:
F ESP,ENCPARM QUIESCE
F ESP,ENCPARM RESTART
7170I
ENCPARM DELETED
Reason:
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.
Action:
None.
7100 - 7199
7171I
DEFAULT ENCPARMS
Reason:
This message lists the default ENCPARMs. These are the ENCPARM statements that will
be added to every job that is being tracked by CA Workload Automation Restart Option
EE.
System Action:
None.
Action:
None.
7175E
ENCPARM NOT DELETED
Reason:
An ENCPARM DELETE statement was entered, but the specified number was invalid.
System Action:
No ENCPARM was deleted.
Action:
Correct the statement and enter it again.
7100 - 7199
7186W
JOB <jobname> JOB #(<jobnum>) TRACKING SUSPENDED DUE TO JOB SIZE
Reason:
The named job is being flagged by CA Workload Automation Restart Option EE as a
'large job', and is beyond CA Workload Automation Restart Option EE's tracking
capability. CA Workload Automation Restart Option EE's definition of a 'large job' is a
job containing approx 11K+ JCL DD statements.
System Action:
The job continues to execute. CA Workload Automation Restart Option EE does not
store any more information on this job in its EXH file.
Action:
This job is not a candidate for tracking or restart using CA Workload Automation Restart
Option EE. Use the job name and job number supplied in the message to find a
Workload Manager application that should have the job, or the OPTIONS RESTARTSTEP
parameter, removed.
7187W
JOB <jobname> #(<jobnum>) WAS TOO LARGE TO BE TRACKED BY ENCORE
Reason:
The named job has just ended or abended. The user is reminded that this job was
flagged by CA Workload Automation Restart Option EE as a 'large job', and was beyond
CA Workload Automation Restart Option EE's tracking capability. CA Workload
Automation Restart Option EE's definition of a 'large job' is a job containing approx 11K+
JCL DD statements.
System Action:
The job ends or abends.
Action:
This job was not a candidate for tracking or restart using CA Workload Automation
Restart Option EE. Use the job name and job number supplied in the message to find a
parameter, removed. Do not restart this job using CA Workload Automation Restart
Option EE.
7100 - 7199
7188W
JOB <jobname> #(<jobnum>) IF ABENDED, RERUN FROM THE BEGINNING
Reason:
The named job has just ended or abended. The user is reminded that this job was
flagged by CA Workload Automation Restart Option EE as a 'large job', and was beyond
CA Workload Automation Restart Option EE's tracking capability. CA Workload
Automation Restart Option EE's definition of a 'large job' is a job containing approx 11K+
JCL DD statements.
System Action:
The job ends or abends.
Action:
This job was not a candidate for tracking or restart using CA Workload Automation
Restart Option EE. Use the job name and job number supplied in the message to find a
parameter, removed. Do not restart this job using CA Workload Automation Restart
Option EE.
7189I
BAD DATA FOUND IN EXH INDEX RECORD AT SLOT xxxx
Reason:
index record.
System Action:
None.
Action:
A Sanity Check should be run in order to search for other damaged areas. This job is the
CYBRMSAN member in your SSCPSAME library.
7100 - 7199
7190E
CSI error, xxxx
Reason:
The accesser 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 affected.
Action:
When the program does not abnormally terminate, the processing is not affected.
No action is required.
When the program terminates abnormally, the CSI interface needs to be disabled
and the job needs to be re-executed.
To disable CSI interface, please add this command to your Initialization parameters:
ENCPARM MODIFY USECSI(NO)
Please report all severe errors to CA Support.
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 CA Support.
7200 - 7299
7199E
RACROUTE CREATE FAILED FOR USER xx IN CYBRM974, SAF ERROR CODE yy-zz
Reason:
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:
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 Workload Manager
8-104 - Second copy of new password doesn't match first
System Action:
Action:
Compare the error code to the error codes associated with the installation's security
facility.
7200 - 7299
7200E
DATA SET NOT AVAILABLE: <dsname>
Reason:
The named data set is not available for ENQ by CA Workload Automation Restart Option
EE. 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.
Action:
Rerun the job after the maintenance job has completed.
7300 - 7399
7300 - 7399
7300I
CA11OPT <Start> [Not initialized] |[ Settings for CA-11 PROCRMS(aaa) STEPRMS(bbb)
CA-11 interface: ENABLED|DISABLED| A REQUIRED CA-11 MODULE COULD NOT BE
LOADED Default restart manager: Unicenter CA-11|ESP Encore Default initial-run
U11RMS step PARM='default-parm' CA-11 DBAS Status: ACTIVE|INACTIVE CA11OPT
<End> ]
Reason:
The product issues this message in response to a CA11OPT initialization statement or
operator command. If a required CA-11 module could not be loaded, CA-11 is probably
not installed on the system.
System Action:
Action:
None.
7301I
CA-11 DBAS subsystem active
Reason:
This message indicates that the status of a CA-11 DBAS (Database Address Space) has
been verified and that the address space was found to be active.
System Action:
Action:
None.
7300 - 7399
7302I
CMT member deleted
Reason:
This message confirms that a request to delete a job's CMT member was successfully
processed.
System Action:
Action:
None.
7303I
CA11_REASON(reason)
Reason:
This message shows how CA-11 expands the reason code specified in the request which
produced this message.
System Action:
Action:
None.
7304I
JOBNAME(jobname) Found(Yes|No) CA11_USAGE(usage-code)
CA11_START(stepname) CA11_END(stepname) CA11_CC(cond-code)
CA11_BYPGDG(NO|YES|VER|CAT) CA11_PSEUDO(NO|YES) CA11_REASON('reason')
CA11_LRTCD(stepname) CA11_LRTCD_CC(cond-code) BTCHID(2-hex-digits)
HISTORY(52-hex-digits)
Reason:
This message lists information retrieved from a job's CA-11 CMT record.
System Action:
Action:
None.
7300 - 7399
7305I
<trace message>
Reason:
When a CA11REQ request is issued with the tracing option enabled, this is a trace
message prepared by program CYBES180.
System Action:
Action:
None.
7306E
Reason:
System Action:
Action:
respectively.
7300 - 7399
7307E
CA11REQ ERROR: Invalid xxxx specification: yyyy
Reason:
Argument xxxx in a CA11REQ command contains the invalid value yyyy.
System Action:
The command is not processed
Action:
7308E
CA11REQ ERROR: <error message>
Reason:
An error occurred during the processing of a CA11REQ command.
System Action:
Action:
message.
7309I
CA11REQ INFO: <informational message>
Reason:
This message contains diagnostic information about the outcome of a CA11REQ
command.
System Action:
Action:
None.
7300 - 7399
7310E
PREVTIME invalid: aaaa
Reason:
An CA11REQ command contains an invalid value for the PREVTIME argument.
System Action:
Action:
Correct the value of the PREVTIME argument and re-issue the command.
7311E
Reason:
The Network Delivery Services were unable to route a CA11REQ request to a destination
disconnected or a time-out may have occurred in the network or in a Workload
Manager.
System Action:
Action:
7300 - 7399
7312E
Subsystem error aaaa-bbbb
Reason:
A CA11REQ 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:
Action:
7313I
<trace message>
Reason:
When a CA11REQ request is issued with the tracing option enabled, this is a trace
message prepared by program CYBES182.
System Action:
Action:
None.
7314E
Subsystem error xx-yy
Reason:
A request was made to the subsystem, but an error occurred. xx is the value returned in
register 15 by program CYBSS005 and yy is the value of XSCMRETCD.
System Action:
Action:
7300 - 7399
7315E
Subsystem request failed: aa bb, ERROR CODE cc-dd
Reason:
A request was made to the 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.
System Action:
Action:
7316E
A required record could not be read from a slot file
Reason:
A subsystem request failed because an error occurred when the product tried to read a
slot-file record. The desired record may have been freed or reused.
System Action:
Action:
Re-issue the request. If the error persists, contact CA Support.
7300 - 7399
7317E
Reason:
The Network Delivery Services were unable to route a request to a destination
disconnected or a time-out may have occurred in the network or in the product.
System Action:
Action:
7318E
<error message>
Reason:
An error occurred during the processing of an CA11REQ subsystem request.
System Action:
Action:
Decide how to proceed based on the error message.
7319E
Requested generation aa of application bb not found
Reason:
The ATR (Application Tracking Record) for generation aa of application bb could not be
retrieved.
System Action:
Action:
7300 - 7399
7320E
Application-level data not found for job aa in application bb, generation cc
Reason:
The AJQE (Application Job Queue Element) for job aa of application bb, generation cc
could not be retrieved.
System Action:
Action:
Ensure you have specified the correct application name, generation number, and job
name.
7321E
Serialization-control error - aaaa failure: TOKEN(token) <reason> Flags: Error=X'bbbb'
Info=X'cccc'
Reason:
The CA11REQ 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:
Action:
Examine the reason given in this message and decide whether to retry.
7322I
CA-11 STATUS: ACTIVE|INACTIVE
Reason:
The product issues this message when it processes a CA11REQ RQCA request and
notices a change in the status of the CA-11 DBAS (Database Address Space).
System Action:
Action:
None.
7300 - 7399
7323E
Reason:
System Action:
Action:
respectively.
7324E
OPTIONS ERROR: <diagnosis>
Reason:
Error <diagnosis> was detected in an OPTIONS statement.
System Action:
Action:
In the case of a syntax error, correct the statement and retry.
7300 - 7399
7325E
CA11OPT FAILURE: <diagnosis>
Reason:
The product issues this message when it encounters a problem while processing a
CA11OPT initialization statement or operator command.
System Action:
The input is not processed.
Action:
In the case of a syntax error, apply a correction and retry.
7326E
CA-11 UI service error: <diagnosis>
Reason:
An error occurred during execution of a CA11REQ service invoked in preparation for
job-resubmission request.
System Action:
The resubmission request is not processed.
Action:
Retrying the request might succeed if the underlying problem is transitory.
7327E
Execution error: <diagnosis>
Reason:
An error was detected during preparation of a job-resubmission request.
System Action:
Action:
Examine the error type and decide if action is required.
7300 - 7399
7328E
Reason:
An error was detected during preparation of a job-resubmission request.
System Action:
Action:
Correcting an operand in the resubmission request might succeed if the underlying
problem is not serious.
7329E
Validation error: <diagnosis>
Reason:
Invalid input was detected.
System Action:
Action:
7330I
<Start|End of Rerun Multiple Summary>
Reason:
A RERUNM command with the keyword VERBOSE was issued. This message delimits the
beginning and the end of the summary portion of the response.
System Action:
Action:
None.
7300 - 7399
7331E
Reason:
An error was detected during preparation of a Rerun Multiple request.
System Action:
Action:
Correcting an operand in the request might succeed if the underlying problem is not
serious.
7332E
The job has a restart manager other than CA-11
Reason:
A CA11REQ command was issued for a job defined to use a different restart manager
than CA-11.
System Action:
Action:
If the request was not issued manually by a user, this message might indicate an internal
error that requires CA Support.
7333E
The job definition does not enable insertion of a CA-11 step
Reason:
A CA11REQ command was issued for a job whose definition does not enable insertion of
a CA-11 U11RMS step.
System Action:
Action:
If the request was not issued manually by a user, this message might indicate an internal
error that requires CA Support.
7300 - 7399
7334W
Reset recommended, CA-11 step omitted in previous run
Reason:
A CA11REQ LIST request was issued for a job in which the insertion of a CA-11 U11RMS
step was suppressed in the previous run. If a job with the same name exists in the CA-11
database, the job's CMT record is not up-to-date.
System Action:
Action:
The user can choose to heed or ignore this warning. If the user decides to resubmit the
job, it is recommended that the user select the reset-for-production option to request
an initial run beginning at the job's first step.
7361W
Data set aaaa is unavailable for event xxxx.yyyy due to contention/migration/offline
status
Reason:
The message is issued for the event xxxx.yyyy in simulation or in SADGEN mode. The
data set 'aaaa' required for the event execution could not be allocated due to specific
reason:
contention if another job or TSO user had allocated the data set exclusively
migration if the data set was migrated by HSM or an equivalent product
offline status if event attempted to access the data set on an offline volume.
System Action:
None. In case of migration reason a recall is initiated for the specified data set.
Action:
If contention persists, determine the user having the data set allocated, and request
they free it.
If migration persists, determine why the data set has not been recalled.
If offline volume is no longer in use, edit the Event to point to the new volume.
7300 - 7399
7362W
Data set aaaa is unavailable for event xxxx.yyyy due to contention/migration/offline
status
Reason:
The message is issued for the event xxxx.yyyy in simulation or in SADGEN mode. The
data set 'aaaa' required for the event execution could not be allocated due to specific
reason:
contention if another job or TSO user had allocated the data set exclusively
migration if the data set was migrated by HSM or an equivalent product
offline status if event attempted to access the data set on an offline volume.
System Action:
None. In case of migration reason a recall is initiated for the specified data set.
Action:
If contention persists, determine the user having the data set allocated, and request
they free it.
If migration persists, determine why the data set has not been recalled.
If offline volume is no longer in use, edit the Event to point to the new volume.
7363W
Job or Profile record XXXXXX is incorrect. Statistics ignored.
Reason:
Application Manager keeps statistics about workload objects (jobs or WOBs). The
statistics are kept in Job or Profile records in JOBSTATS file. If Application Manager
detects that a statistics record is invalid, then it issues 7363W messages and ignores the
record.
XXXXXX in the message represents incorrect record's key. It starts with J for Job record
and with P for Profile record followed by the name of the job or profile.
System Action:
System will not use statistics from this incorrect record.
Action:
Users should delete this record from the file. This record will be recreated automatically
when an application with JOBPROF statement runs, and ESP will start collecting statistics
again.
7300 - 7399
7364W
REASON STRING FOR JOB XXXX WHICH IS PLACED ON MANUAL HOLD IS EMPTY,
IGNORED
Reason:
This message is issued when the REASON operand is used but the reason string is not
specified in a JOB statement.
System Action:
The REASON operand is ignored. Processing continues.
Action:
Either remove the REASON operand or specify the reason string.
7365W
<modname>.<rmid>+<offset> NOTIFY service is not available; The following message
cannot be delivered:
Reason:
The message is issued when attempt is made to send a notification but NOTIFY service is
not available. This may happen during ESP shutdown when NOTIFY service is already
stopped. This message is followed by the text of failed notification enclosed in double
quotes. Message contains information about service requestor that can be useful for
diagnostics.
<modname> - name of caller module
<rmid> - maintenance level of the caller module
<offset> - offset to the point of return to the caller module
System Action:
After issuing this message system also outputs a text of the failed notification enclosed
in double quotes. If this error occurs NOT during shutdown then system also requests a
dump of ESP address space.
Action:
User can examine an ESP subsystem job log to see what notification messages failed to
be delivered and take an action if necessary. Any possible dump should be sent to ESP
support for problem determination.
7300 - 7399
7368W
SCHEDULED is only valid for EXTERNAL jobs, ignored
Reason:
The SCHEDULED parameter is only meaningful for EXTERNAL jobs. It is ignored for other
job types. This message is only issued in simulation.
System Action:
The parameter is ignored.
Action:
Remove this parameter.
7373E
Workstation security patch is missing
Reason:
The message is issued for the Workstation without security patch trying to logon to the
Workstation Server with ENCRPSW parameter on. The above security patch makes
workstation logon encrypted. Workstation logon is being rejected with 'Logon Failed'
message.
System Action:
None.
Action:
Apply workstation security patch encrypting USER/LOGON command.

ESP Codes and Messages

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ESP Codes and Messages

Încărcat de

Drepturi de autor:

Formate disponibile

CA Workload Automation ESP

Message Reference Guide

CA Technologies Product References

CA ACF2 (CA ACF2)

CA Librarian Base for z/OS (CA Librarian for z/OS )

CA Mainframe Software Manager (CA MSM)

CA OPS/MVS Event Management and Automation (CA OPS/MVS)

CA Top Secret (CA Top Secret)

CA Workload Automation Agent for Application Services (CA WA Agent for

CA Workload Automation Agent for Databases (CA WA Agent for Databases)

CA Workload Automation Agent for HP Integrity NonStop

CA Workload Automation Agent for i5/OS (CA WA Agent for i5/OS)

CA Workload Automation Agent for Microsoft SQL Server

CA Workload Automation Agent for PeopleSoft (CA WA Agent for PeopleSoft)

CA Workload Automation Agent for Remote Execution

CA Workload Automation Agent for SAP (CA WA Agent for SAP)

CA Workload Automation Agent for UNIX, Linux, or Windows

CA Workload Automation Agent for z/OS (CA WA Agent for z/OS)

CA Workload Automation CA 7 Edition

CA Workload Automation ESP Edition (CA WA ESP Edition)

CA JCLCheck Workload Automation (CA JCLCheck )

CA Workload Automation Restart Option for z/OS Schedulers (CA WA Restart

CA Workload Automation Service Governor ESP Edition (CA WA Service Governor

CA Workload Automation Workstation ESP Edition (CA WA Workstation ESP Edition)

Information about user communities and forums

Product and documentation downloads

CA Support policies and guidelines

Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

Added messages 6660 to 6668.

zIIP Processor Support for CA WA ESP Edition

Added messages 4471 to 4488.

Messages for Control File Usage

Added new messages 1070 to 1072, and 1290

Reporting Whether Event Triggered with Replace or Add Option

Updated message 6150

Queuing Operator Commands When CA WA ESP Edition is Down

Updated messages 4362 to 4364.

Cleanup Utility for the Jobstats Data Set

Added messages 4028 and 4029

Adding a Restart Step to All Jobs

Added messages 1073E and 1074E

CA Interface to IBM Health Checker

Updated message 6449

Conditional Job Release Based on a Step Completion Code

Added new message 2082E

Incrementing and Decrementing Resources

Added messages 2083 and 2084.

Added missing message 772E

Added messages 1987E, 2051E, 3398I, and 3399I

4669SRemoved a reference to CWSS (Consolidated Workstation Server) in the

001 - 099 ...................................................................................................................................................................... 9

Chapter 2: Messages 1000 Through 1999

1000 - 1099 .............................................................................................................................................................. 367

Chapter 3: Messages 2000 Through 2999

2000 - 2099 .............................................................................................................................................................. 681

Chapter 4: Messages 3000 Through 3999

3000 - 3099 .............................................................................................................................................................. 965

Chapter 5: Messages 4000 Through 5999

4000 - 4099 ............................................................................................................................................................ 1195

Chapter 6: Messages 6000 Through 7999

6000 - 6099 ............................................................................................................................................................ 1525

8 Message Reference Guide

Chapter 1: Messages 001 Through 999