EndevorSCM MessagesRef ENU

CA Endevor Software Change
Manager
Messages and Codes Reference Guide

Version 16.0.00
Fourth Edition
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 is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or
duplicated, in whole or in part, without the prior written consent of CA.
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 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to
their respective companies.
CA Technologies Product References

This document references the following CA Technologies products:
CA Endevor Software Change Manager (CA Endevor SCM)
CA Endevor Software Change Manager Automated Configuration (CA Endevor

Automated Configuration)
CA Endevor Software Change Manager Parallel Development (CA Endevor Parallel

Development)
CA Endevor Software Change Manager Quick Edit (CA Endevor Quick Edit)
CA Endevor Software Change Manager External Security Interface (CA Endevor

External Security Interface)
CA Endevor Software Change Manager InfoMan Interface (CA Endevor InfoMan

Interface)
CA Endevor Software Change Manager CA Librarian Interface (CA Endevor CA

Librarian Interface)
CA Endevor Software Change Manager Integration for the Natural Environment

(CA Endevor Integration for the Natural Environment)
CA Endevor Software Change Manager CA Netman Interface (CA Endevor CA

Netman Interface)
CA Endevor Software Change Manager for CA Panvalet Interface (CA Endevor for
CA Panvalet Interface)
CA Endevor Software Change Manager CA Roscoe Interface (CA Endevor CA

Roscoe Interface)
CA Librarian Base for z/OS (CA Librarian)
CA Panvalet for z/OS (CA Panvalet for z/OS)
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 [email protected].
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:
Note: In PDF format, page references identify the first page of the topic in which a
change was made. The actual change may appear on a later page.
Version 16.0, Fourth Edition
API Element Action Messages (see page 87) Updated to add the message
API0086E.
CIG Messages (see page 269) Updated the action text for C1G0033E and
C1G0034E and changed the message and reason text for C1G0148E.
ENBE Messages (see page 516) Updated to add the message ENBE049E
PKMR Messages (see page 883) Updated to add message PKMR012C and to
update the action text for the message PKMR012E.
SCHK Messages (see page 952) Updated to add the message SCHK105C.
SYN Messages (see page 1006) Updated to add the messages SYN0040I and
SYN0040I.
Version 16.0, Third Edition

For PTF RO68348, March 2014:
C1BX Messages (see page 244) Updated to add the messages C1BX107S and
C1BX107I.
For PTF RO67723, April 2014:
PKEX Messages (see page 867) Updated to add the messages PKEX119E and
PKEX120E.
Version 16.0, Second Edition
CIG Messages (see page 269) Updated to add the message CIG0186E.
VAL Messages (see page 1015) Updated the severity level of the following
messages from warn to error: VAL0002E, VAL0003E, VAL0004E, and VAL0005E.
Version 16.0
0047 Abend Code (see page 15) Added to document why this abend code can
appear.
API Element Action Messages (see page 87) Updated to add the message
API0113W.
C1BM Messages (see page 172) Updated to change the message severity from
C1BM4100:W027 to C1BM4100:E027 and change the message text.
C1BX Messages (see page 244) Added this topic for package shipment processing
messages: C1BX100I, C1BX100W, C1BX101I, C1BX102E, C1BX103E, C1BX104S, and
C1BX105E.
CIG Messages (see page 269) Updated to add the messages C1G0072C, C1G0343I,
C1G0345I, C1G0352W, and C1G0353E. Updated to clarify the action for the
message: C1G0128E.
C1U Messages (see page 447) Updated to add the messages C1U0970E,
C1U0971E, C1U0972E, C1U0973E, C1U0974E, C1U0975E, C1U0976E, C1U0977E,
and C1U0978E.
C1X Messages (see page 456) Updated to delete obsolete messages C1X0516E
and C1X0517I.
C1Y Messages (see page 485) Updated to add the message C1Y0103W.
ENBE Messages (see page 516) Updated to add the messages ENBE037E,
ENBE038W, ENBE039W, ENBE045E, ENBE046E, ENB E047E, ENBE048E, ENBE082E,
ENBE140C, ENBE161I, ENBE179W, and ENBE205C.
ENBS Messages (see page 615) Updated to add the messages: ENBS004I,
ENBS005I, ENBS014W, ENBS071C, ENBS072E, ENBS073E, and ENBS074I. Also,
updated the message, reason, or action text for the following: ENBS021I, ENBS022I,
ENBS024I, ENBS025I, ENBS027I, ENBS028I, ENBS031E to ENBS034E, ENBS045I,
ENBS054S, ENBS064I, ENBS066W, and ENBS070E. Deleted these obsolete
messages: ENBS011E, ENBS013E, and ENBS026I. Changed the severity for ENBS006I
to ENBS006E, and ENBS012I to ENBS012W, ENBS049S to ENBS049E, ENBS050S to
ENBS050E, ENBS067W to ENBS067E, ENBS903I to ENBS903E, and ENBS904I to
ENBS904E.
ECAP Messages (see page 505) Updated to add the messages: ECAP033I and
ECAP034S.
ENDE Messages (see page 682) Updated to add the message ENDE00BE.
EWS Messages (see page 741) Added the EWS messages, which can be generated
during Web Services processing.
PKMR Messages (see page 883) Updated to add the messages PKMR105E,
PKMR143E, PKMR144E, PKMR145E, PKMR410E, PKMR619I, PKMR629E, PKMR 630I,
PKMR631I, PKMR632C, PKMR632W, PKMR633C, PKMR633W, PKMR721I, and
PKMR731I. Also, updated the message and reason text for the following:
PKMR139E, PKMR282E, PKMR284E, PKMR285E, PKMR287E, PKMR316C,
PKMR608E, PKMR616E, and PKMR618I. Also, removed the obsolete message
PKMR513E.
Various messages were updated to change the version and level format to VVLL.
Release 15.1
C1G Messages (see page 269)Updated as follows:
Added messages C1G0120W and C1G0475W.
Changed the message number C1G0005E to C1G0005S, with no changes to the

message text, reason, or action.
Removed obsolete message C1G0455I.
C1BM Messages (see page 172)Updated the text, reason, and action for message
C1BM4100:E007.
C1BML Messages (see page 197)Updated the text, reason, and action for
message C1BML13E and added message C1BML32E.
C1I Messages (see page 394)Updated the text, reason, and action for message
C1I0013E.
C1LB Messages (see page 400)Updated the text for message C1LB034S.
C1R Messages (see page 424)Updated as follows:
Updated the text, reason, and action for message C1R0028E.
Added message C1R0041I.
ENDE Messages (see page 682)Updated the text, reason, and action for message
ENDE057E.
JRCV Messages (see page 809)Added message JRCV011W.
VSIO Messages (see page 1022)Updated the action text for VSI1102E.
Version 15.0
ACM Messages (see page 15)Added message ACMR035E.
API Reason Codes (see page 71)Added 04,016 reason code and return code.
BC1PSVCS Messages (see page 155)Added this topic for SVCS program messages.
C1F Messages (see page 269)Added message C1F0001E.
C1G Messages (see page 269)Added message C1G0455E.
C1I Messages (see page 394)Added message C1I0022E.
C1LB Message (see page 400)Updated message text for C1LB003E.
C1R Messages (see page 424)Added message C1R100I.
C1X Messages (see page 456)Added messages C1X0516E and C1X0517I.
C1Y Messages (see page 485)Added message C1Y0008E.
ENBE Messages (see page 516)Updated message ENBE192E. Added message

ENBE204E.
PDM Messages (see page 824)Added messages PDM0049E and PDM0049I.
PKMR Messages (see page 883)Added messages PKMR130I through PKMR142I.

Updated the reason for PKMR501E.
SMGR Messages (see page 960)Updated message SMGR157E. Added messages

SMGR202E, SMGR232E, SMGR234E, and SMGR235I.
SYN Messages (see page 1006)BEND--C1BMX Messages (see page 210)Added

message SYN0999W.
Contents
Chapter 1: Format and Conventions
13
Module Numbers (mmmm) ....................................................................................................................................... 13

Message Numbers (nnn or nnnn) .............................................................................................................................. 13
Suffix Descriptions ...................................................................................................................................................... 14
Chapter 2: Error Codes and Messages
15
0047 Abend Code ....................................................................................................................................................... 15

ACM Messages ........................................................................................................................................................... 15
Analysis Utility Messages ........................................................................................................................................... 35
API Messages.............................................................................................................................................................. 69
API Return Codes ................................................................................................................................................ 70
API Reason Codes ................................................................................................................................................ 71
API Element Action Messages ............................................................................................................................. 87
BSTAPI Messages .............................................................................................................................................. 116
BSTERR Messages .............................................................................................................................................. 121
EN$TRAPI Error Messages ................................................................................................................................. 125
WTO Messages .................................................................................................................................................. 126
B1E Message Codes .................................................................................................................................................. 127
B1E Messages .................................................................................................................................................... 127
B1NM Messages ....................................................................................................................................................... 140
B1TS Messages ......................................................................................................................................................... 151
BC1PSVCS Messages................................................................................................................................................. 155
BTSQ Messages ........................................................................................................................................................ 155
C1A Messages .......................................................................................................................................................... 159
C1B Messages ........................................................................................................................................................... 163
C1BM Messages ....................................................................................................................................................... 172
C1BML Messages...................................................................................................................................................... 197
C1BMX Messages ..................................................................................................................................................... 210
C1BR Messages ........................................................................................................................................................ 237
C1BX Messages......................................................................................................................................................... 244
C1C Messages ........................................................................................................................................................... 247
C1E Messages ........................................................................................................................................................... 249
C1EI Message Codes ................................................................................................................................................. 259
C1EI Messages ................................................................................................................................................... 260
C1F Messages ........................................................................................................................................................... 269
C1G Messages .......................................................................................................................................................... 269
Contents 9
C1I Messages ............................................................................................................................................................ 394

C1LB Messages ......................................................................................................................................................... 400
C1M Messages ......................................................................................................................................................... 412
C1P Messages ........................................................................................................................................................... 423
C1R Messages ........................................................................................................................................................... 424
C1U Messages .......................................................................................................................................................... 447
C1V Messages........................................................................................................................................................... 455
C1X Messages ........................................................................................................................................................... 456
C1Y Messages ........................................................................................................................................................... 485
CIIO Messages .......................................................................................................................................................... 494
CONRELE Messages .................................................................................................................................................. 495
C2FM Messages........................................................................................................................................................ 501
ECAP Messages......................................................................................................................................................... 505
ENBE Messages ........................................................................................................................................................ 516
ENBP Messages ........................................................................................................................................................ 588
ENBS Messages ........................................................................................................................................................ 615
ENBX Messages ........................................................................................................................................................ 651
ENCI Messages ......................................................................................................................................................... 664
ENCP9xx Messages ................................................................................................................................................... 667
ENCS Messages ........................................................................................................................................................ 673
ENDE Messages ........................................................................................................................................................ 682
ENDI Messages ......................................................................................................................................................... 714
ENIP Messages ......................................................................................................................................................... 715
ENMP Messages ....................................................................................................................................................... 732
EWS Messages .......................................................................................................................................................... 741
FPVL Messages ......................................................................................................................................................... 748
FUPD Messages ........................................................................................................................................................ 752
IMGR Messages ........................................................................................................................................................ 756
JLOG Messages ......................................................................................................................................................... 790
JRCV Messages ......................................................................................................................................................... 809
MCS Messages.......................................................................................................................................................... 822
PDM Messages ......................................................................................................................................................... 824
PKEX Messages ......................................................................................................................................................... 867
PKMR Messages ....................................................................................................................................................... 883
RDLT Messages ......................................................................................................................................................... 947
SCHK Messages ........................................................................................................................................................ 952
Source Sync Check Return and Reason Codes .................................................................................................. 956
SHP Messages........................................................................................................................................................... 956
SMGR Messages ....................................................................................................................................................... 960
SYN Messages......................................................................................................................................................... 1006
VAL Messages ......................................................................................................................................................... 1015
VSIO and BC1PVSIO Messages ............................................................................................................................... 1021
10 Messages and Codes Reference Guide
VSIO Messages ................................................................................................................................................ 1022

BC1VSIO Messages .......................................................................................................................................... 1029
Appendix A: Trace Information
1031
Trace Back Data ...................................................................................................................................................... 1031
Contents 11
Chapter 1: Format and Conventions

This chapter details the format and conventions of the messages generated in the
course of processing.
Messages appear in one of two formats:
Prefixmodule numbersuffix. Messages in this format are generated by the SCL

parser (with prefix C1BM) or the reporting utilities (with prefix C1BR). The following
examples illustrate this format:
Prefix
Module
Suffix
Example
C1BM
mmmm
:xnnn
C1BM4100:E066
C1BR
mmmm
:xnnn
C1BR3040:W001
Prefixmessage numbersuffix. All messages other than the C1BM and C1BR
messages, have this format. The following examples illustrate this format:
Prefix
Message
Suffix
Example
API
nnnn
API0000E
ENBE
nnn
ENBE002I
Module Numbers (mmmm)

The module number in messages appearing in prefix-module number-suffix format
identifies the CA Endevor SCM utility that produces the message.
Message Numbers (nnn or nnnn)

Messages have either three-digit or four-digit numbers. Message numbers are part of
the suffix in messages that appear in prefix-module number-suffix format.
Messages display in the upper right corner of the terminal screen, in accord with
TSO/ISPF message conventions. You can display a one-line expanded message by
pressing PF1.
Chapter 1: Format and Conventions 13
Suffix Descriptions
Suffix Descriptions
Suffixes include the following information:
A severity code (x) and message number if the message is in the prefix-module
number-suffix format
A severity code (x) if the message is in the prefix-message number-suffix format
Severity levels correspond to CA Endevor SCM return codes. These return codes
determine whether processing will be interrupted by an error condition. The following
severity levels are described along with their corresponding return codes:
I
I indicates an informational message. Processing concluded normally. The message
is for information purposes only.
Return Code:
00
W
W indicates a warning message. An error was encountered that was not serious
enough to terminate processing.
Return Code:
04
C
C indicates a caution message. An error was encountered that may prevent further
processing.
Return Code:
08
E
E indicates an error message. An error was encountered that terminated processing
of a current action, but allowed CA Endevor SCM to continue with the next action
request.
Return Code:
12
S
S indicates a severe error was encountered that prevented CA Endevor SCM from
completing the requested action. Processing will terminate immediately. This
category includes internal, system, and I/O errors.
Return Code:
16
F
F indicates a fatal error. The reporting job will terminate.
Chapter 2: Error Codes and Messages

This guide includes a listing of the messages that display during the execution of CA
Endevor SCM functions.
0047 Abend Code

If you attempt to execute NDVRC1 in an unauthorized state, the follow message appears
in the JES log and no other messages appear.
NDVRBAT
1 NDVRC1 0047
Reason:
NDVRC1 was found to be unauthorized. This is usually caused by a non-APF-authorized
library in the STEPLIB concatenation.
Action:
Verify that all the libraries in the STEPLIB concatenation are APF-authorized.
Note: For more information about the 0047 abend code, see the documentation
provided by IBM for their IBM Information Management Software for z/OS.
ACM Messages
This section details messages generated by the Automated Configuration Manager
(ACM) of the Automated Configuration option, along with possible causes and
corrective actions to take in error situations.
ACM0000E
ACM ROOT/XREF DATASET ALLOCATION ERROR
Reason:
This message indicates that allocation of ACM Root and Xref data sets failed.
Action:
Check for the reason. Normally, you will also receive a C1A0011E or C1A0012E message
that explains the problem further.
Chapter 2: Error Codes and Messages 15
ACM Messages
ACMB001E
ACM FILE OPEN FAILED - PROCESS ABORTED
Reason:
An attempt to open the ACM root or cross reference data set failed.
Action:
Make sure the data set names specified in the C1DEFLTS table are correct and the data
sets exist and are available.
ACMB002I
Count ROOT RECORDS WERE ADDED
Reason:
The indicated number of Root Records was successfully added to the ACM root data set.
Action:
None.
ACMB003E
ACM PARENT UNDEFINED: parent name
Reason:
An ACM Parent record could not be retrieved or added (or both).
Action:
Add the element to your environment and retry the transaction. Make sure the ACM
Root file is not full. If the error still occurs, rebuild the ACM Root and XREF files.
ACM Messages
ACMB004E
ACM ROOT FOR CHILD UNDEFINED
Reason:
If this message occurs as part of component updates, it implies the ACM VSAM root is
out of space or non-accessible. If it occurs as part of the batch load procedure, BUILDX,
an ACM root associated with the CHILD component was deleted.
Action:
For component update, review the VSAM characteristics, reallocate and rebuild. For
batch load, review the integrity of the ACMLIST and ACMCOMP files used by BUILDR and
BUILDX and correct the discrepancy.
ACMB005I
KEY:ELM element name ENV:environment name STG:stage id SYS:system name
SBS:subsystem name TYPE:type name
Reason:
This is an informational message. For batch load, it represents the number of
component Objects processed and related, and the maximum return code. For
component processing, it indicates that the child ELEMENT record could not be
retrieved or added.
Action:
For batch load, no action is required. For component processing, review the ACM root
VSAM file to determine if there is a space or authority problem.
ACMB006I
KEY:MBR:member name DSN:data set name
Reason:
A related member component could not be retrieved or added to the ACM Root file.
Action:
Review the VSAM attributes of the ACM Root file to detect a space or authority
problem. If the problem was caused by an out of space condition, REPRO and rebuild
the VSAM file in error.
ACM Messages
ACMB007I
ACM ROOT CREATED FOR CHILD child name
Reason:
This message indicates that the ACM Root and XREF files were successfully initialized.
Action:
None.
ACMB0009E
PARENT ELEMENT UNDEFINED: parent element
Reason:
The element which was specified for the query was not found in the ACM configuration
data.
Action:
Check the element name specification; if the specification was correct, contact CA
Technical Support for help.
ACMB010E
ACM ddname FILE operation ERROR - RC=return code
Reason:
During dynamic allocation of the ACM Root and XREF VSAM files, an error occurred. The
ddname indicates the file in error, operation is the operation being attempted, and RC is
the R15 value from the operation.
Action:
Based on the information in the message, correct the problem and re-execute the job.
ACM Messages
ACMB011C
Corrupted ROOT/XREF UPDATED
Reason:
The ACM ROOT/XREF data sets, which were in optimized format, were updated by a
version of the CA Endevor SCM software which was superseded.
Action:
Make sure that older releases of CA Endevor SCM are not used to update the ACM
ROOT and XREF data sets. Run BC1JACMO to re-optimize the ROOT and XREF data sets.
ACMB011I
KEY:comment/object text
Reason:
The indicated comment or object component was not retrieved or added in the ACM
root file. This is probably due to a space or authority problem on the VSAM file.
Action:
Review the characteristics of the ACM Root file, and correct. If it is a space problem, the
ACM Root and XREF must be resized and rebuilt.
ACMB012E
UNKNOWN CHILD TYPE:child-value
Reason:
ACM component processing received an invalid child-value during component update.
Action:
Contact CA Technical Support with the invalid child-value.
ACMB015W
JOB SUBMITTED
Reason:
A job was submitted to perform your ACMQ request.
Action:
None.
ACM Messages
ACMB016W
REQUEST COMPLETED
Reason:
Your ACMQ request was completed.
Action:
None.
ACMB020I
NO ACM INDEX UPDATES REQUIRED
Reason:
No updates to the ACM index data set are necessary. Updates are necessary only when
component relationships are modified.
Action:
None.
ACMB021I
ACM INDEX UPDATE BYPASSED DUE TO SITE OPTION SPECIFICATION
Reason:
The ACMIDXUP option of the C1DEFLTS table is set to a value of 'N'. This causes this
feature to be bypassed.
Action:
None.
ACMB022I
ACM INDEX UPDATES COMPLETED:
Reason:
Updates to the ACM index data set are complete. Updates are necessary when
component relationships are modified.
Action:
None.
ACM Messages
ACMB023I
Component-type count
Reason:
This informational message is issued by component processing. The component-type is
one of the types listed next, and the count is the numeric count of the indicated type
added to the ACM Root and XREF files.
Component-Type:
ACM ELEMENT UPDATES:
ACM MEMBER UPDATES:
RELATED ELEMENT UPDATES:
RELATED MEMBER UPDATES:
RELATED OBJECT UPDATES:
RELATED COMMENT UPDATES:
Action:
None.
ACMB024I
ACM QUERY INDICATES: THIS ELEMENT IS REFERENCED BY nn ELEMENTS
Reason:
Informational message. This message specifies the number of elements that are
referenced by this element.
Action:
None.
ACMB025I
ACM QUERY INDICATES: THIS ELEMENT IS REFERENCED BY NO OTHER ELEMENTS
Reason:
Informational message. This message informs the user that this element is not
referenced by any other element.
Action:
None.
ACM Messages
ACMB026I
ACM QUERY INDICATES: THIS ELEMENT IS REFERENCED BY ONE ELEMENT
Reason:
Informational message. This message informs the user that this element is referenced
by one other element.
Action:
None.
ACMB030W
NO NEW RELATIONS HAVE BEEN FOUND IN FILE ACMCOMP
Reason:
This message appears with a RC=4. BC1PACMO notifies you with this message if the file
ACMCOMP was present during the BC1PACMO run (not dummy or nullfile), and the
ACMCOMP file did not contain any element relation information different from what
was already contained in the ACMQ files before the run.
Action:
None.
ACMB036C
count INVALID RECORDS WERE FOUND AND REMOVED FROM THE XREF DATASET
Reason:
Invalid records were found in XREF while running BC1JACMO.The reorganization utility
has removed these records.
Action:
Contact CA Technical Support for help with the problem analysis.
ACM Messages
ACMB037W
VALIDATE DETECTED ONE OR MORE ORPHANED COMPONENT LISTS
Reason:
BC1PACMO utility was run with parameter VALIDATE and has detected orphaned ACM
entries and deleted them.
Action:
None.
ACMO004E
EOF MISSING FOR DDNAME: ddname
Reason:
The ROOT or XREF file does not contain a logical EOF record and is now considered
logically corrupted.
Action:
Check when the file was last used and why, and when it stopped working.
ACMQ203I
LIST list COMPONENTS FOR element/member/related object/related comment
Reason:
Informational message. LIST used/using components for ELEMENT/MEMBER/RELATED
OBJECT/RELATED COMMENT. This message is issued when a wildcarded ACMQ batch
request is translated into one or more specific ACMQ requests.
Action:
None.
ACM Messages
ACMQ204I
ELEMENT: element name ENVIRONMENT: environment name
Reason:
Action:
None.
ACMQ205I
SYSTEM: system name SUBSYSTEM: subsystem name
Reason:
Action:
None.
ACMQ206I
TYPE: type name STAGE NUMBER: stage id
Reason:
Action:
None.
ACM Messages
ACMQ207I
MEMBER: member name DSNAME: data set name
Reason:
Action:
None.
ACMQ208I
Text
Reason:
Action:
None.
ACMQ209I
OPTION FILTER COMPONENTS WITH ENVIRONMENT: environment
Reason:
Action:
None.
ACM Messages
ACMQ210I
STMT #statement COMPLETED RC=return code.
Reason:
The ACMQ batch query #nn has completed with return code=xx. RC=04 indicates that no
entries were found.
Action:
None.
ACMQ211I
THIS ENTITY entity
Reason:
Entity contains no references or is not referenced. An ACMQ query did not find any
references.
Action:
Make sure that you have no spelling errors.
ACMQ212I
NO MATCHING ENTRY FOUND
Reason:
The name specified in your query does not exist in the ACMQ database.
Action:
Make sure that you have no spelling errors.
ACMQ213S
Program name : ABEND abend IN BC1PACMC
Reason:
BC1PACMC abended.
Action:
Check when this worked last time, and compare to see what has changed. Contact CA
Technical Support for help if necessary.
ACM Messages
ACMQ214S
Program name : ERROR IN BC1PACMC RC=return code
Reason:
BC1PACMC returned a non-zero return code.
Action:
Contact CA Technical Support.
ACMQ215S
ALESERV ERROR: error FUNC: function RC=return code
Reason:
An internal function call returned a bad return code.
Action:
ACMQ216S
DSPSERV ERROR: error FUNC: function, RC=return code - REASON=reason code
Reason:
Action:
ACMQ217S
DIV ERROR: error FUNC: function, RC=return code - REASON=reason code
Reason:
Action:
ACM Messages
ACMQ218S
SVC99 ERROR (error) RC=return code - REASON=reason code
Reason:
Action:
ACMQ219S
Program name SORT RETURN CODE >0
Reason:
BC1PACMC returned a non-zero return code.
Action:
ACMQ221S
Program name : TCBTOKEN ERROR RC=return code
Reason:
Action:
ACMQ300I
DSN=data set name
Reason:
Informational message. This message indicates the ACMOUT data set name.
Action:
None.
ACM Messages
ACMQ301I
DSN=data set name (member name)
Reason:
Informational message. This message indicates the ACMOUT data set name and
member name.
Action:
None.
ACMQ400I
(CCID: content)
Reason:
ACMQ401I
(COMMENT: content)
Reason:
Action:
None.
ACMQ402I
(SET FROM environment content)
Reason:
Action:
None.
ACM Messages
ACMQ403I
(COPYBACK) or (COPYBACK SEARCH)
Reason:
Action:
None.
ACMQ410I
Option EXCLUDE RELATED
Reason:
Action:
None.
ACMR001E
Initialization Failed
Reason:
ACMQ could not open the Root or XREF files (or both).
Action:
Make sure the following:
C1DEFLTS is correctly defined and ACMQ points to the correct data sets.
Proper authorization exists on the VSAM files.
No other jobs are holding enqueues on the ACM files.
ACM Messages
ACMR002E
Component-type UNDEFINED
Reason:
A query was issued against the ACM files, but the indicated component-type is not in the
ACM root file.
Action:
Check the specification screen to make sure that all fields are either specified explicitly,
or contain wildcard (*) character. A blank specification screen attempts to query using a
blank value. Retry the query after modifying the criteria.
ACMR003E
INVALID COMPONENT LIST POINTERS
Reason:
A relationship exists in the ACM XREF file, but the associated Root record is missing
from the ACM Root file. This represents an incorrectly built ACM Root and XREF file.
Action:
Rebuild the Root and XREF ensuring that the source ACMLIST and ACMCOMP outputs
are properly related.
ACMR004I
ELEMENT NOT PART OF OTHER ELEMENTS
Reason:
One or more of the selected children components are not associated with any parent
components.
Action:
Either refine your query to avoid these children, or disregard these entries.
ACM Messages
ACMR005E
ROOT/XREF FILES NOT SYNCHRONIZED
Reason:
The last update data/timestamps in the ROO and XREF files are not the same.
Action:
Determine when this condition started and how the files got out of SYNC. Contact CA
Technical Support. You may have to rebuild your ROOT/XREF files.
ACMR005I
THE ACMSCL DATA SET MUST BE COPIED TO YOUR SCL
Reason:
This informational message appears as an SCL comment to direct the user to copy the
SCL file from the temporary data set to a permanent location.
Action:
None.
ACMR006E
ACM ROOT DATA SET MISSING
Reason:
The name of the ACM root data set name is missing from the C1DEFLTS table.
Action:
Specify the name of the data set in the C1DEFLTS ACMROOT parameter.
ACMR007E
ACM XREF DATA SET MISSING
Reason:
The name of the ACM cross-reference data set name is missing from the C1DEFLTS
table.
Action:
Specify the name of the data set in the C1DEFLTS ACMXREF parameter.
ACM Messages
ACMR008E
UNABLE TO LOAD C1DEFLTS
Reason:
Unable to load the C1DEFLTS table.
Action:
Make sure the C1DEFLTS table exists in the authorized load library and the library exists
within your login procedure.
ACMR009E
DEFAULTING TO PRINTER CLASS A
Reason:
An ACM query was directed to go directly to print, but a printer class was not specified.
A default printer class was chosen as the target of the output.
Action:
Either specify a printer class, or take the default of A.
ACMR010E
DEFAULTING TO SYSTEM DESTINATION
Reason:
An ACM query was directed to go directly to print, but a destination was not specified.
Output will go to the system-defined destination.
Action:
None.
ACMR032W
YOU NEED EXCL ACMOUT [RNAME|DSNAME]
Reason:
The ACMOUT file, required for your query, cannot be allocated because someone else is
already using it.
Action:
Determine who is using the file, or wait until the file is available.
ACM Messages
ACMR033E
STAGE stage id INVALID FORenv
Reason:
When processing a SET FROM ENV/STG the program detected that the named ENV does
not contain the named stage.
Action:
Correct the SCL statement and resubmit.
ACMR034E
Dataset name IS IN USE BY ANOTHER USER - RETRY THE ACTION AT A LATER TIME
Reason:
The ACMQ ROOT file is in use by another user.
Action:
Retry the action when the ACMQ ROOT file is no longer in use.
ACMR035E
ACMQ WAS REQUESTED, BUT ASCM IS SET TO N. TO USE ACMQ, ASCM MUST BE SET
TO Y
Reason:
ACMQ is not activated.
Action:
The CA Endevor SCM administrator can activate ACMQ by entering Y in the ASCM field
in the CA Endevor SCM C1DEFLTS table, provided your site is licensed for this option.
Analysis Utility Messages

This section details messages generated by the Inventory Analyzer in the course of
processing, along with possible causes and corrective actions to take in error situations.
ANAL001I
PARAMETER ANALYSIS
Reason:
Informational message. This message appears in the Execution Report, and indicates
that analysis of the program parameter is beginning. You receive this message only if
you specified a program parameter in the JCL for the Inventory Analyzer.
Action:
None.
ANAL002E
PARAMETER SYNTAX ERROR, EXECUTION TERMINATED
Reason:
The parameter format is invalid.
Action:
Correct the errors and retry execution.
ANAL030I
SOURCE OPTIONAL REQUESTED, "FROM" DATA SETS NO LONGER REQUIRED
Reason:
Informational message. This message appears in the Parameter Syntax section of the
Execution Report, and indicates that the SOURCE OPTIONAL parameter was coded. This
option allows you to omit FROM data sets from your ANALYZE requests. If a FROM data
set is omitted, analysis proceeds without any source analysis. You receive this message
only if you specified the SOURCE OPTIONAL parameter in the JCL for the Inventory
Analyzer.
Action:
None.
ANAL031I
OUTPUT MODEL DEFINITION ASSIGNED TO DDNAME ddname.
Reason:
that a parameter was coded that overrides the default ddname associated with the
output model definition. You receive this message only if you specified a ddname that
overrides the ddname BSTMODEL in the JCL for the Inventory Analyzer.
Action:
Make sure that the DDname "BSTMODEL" is replaced in the jobsteps with the ddname
identified in the message in order to read the output model definition.
ANAL032I
DETAIL MESSAGE LOG ASSIGNED TO DDNAME ddname.
Reason:
that a parameter was coded that overrides the default DDname associated with the
Execution Report.
You receive this message only if you specified a DDname that overrides the default
DDname C1MSGS1 in the JCL for the Inventory Analyzer.
Action:
Make sure that the DDname "C1MSGS1" is replaced in the jobstream with the DDname
identified in the message in order to obtain the Execution Report.
ANAL033I
INPUT REQUEST DATA SET ASSIGNED TO DDNAME ddname.
Reason:
input request data set.
DDname BSTIPT01 in the JCL for the Inventory Analyzer.
Action:
Make sure that the DDname "BSTIPT01" is replaced in the jobstream with the DDname
identified in the message in order to read the input requests.
ANAL034I
INPUT RULE DEFINITIONS ASSIGNED TO DDNAME ddname.
Reason:
input rule definitions.
DDname BSTRULES in the JCL for the Inventory Analyzer.
Action:
Make sure that the DDname "BSTRULES" is replaced in the jobstream with the DDname
identified in the message in order to read the input rule definitions.
ANAL035I
SUMMARY LOG ASSIGNED TO DDNAME ddname.
Reason:
Summary Report.
DDname C1SUMARY in the JCL for the Inventory Analyzer.
Action:
Make sure that the DDname (C1SUMARY) is replaced in the jobstream with the DDname
identified in the message in order to obtain the Summary Report.
ANAL040I
OUTPUT MODEL DIRECTED TO DDNAME ddname FOR count SUCCESSFULLY
PROCESSED MEMBERS
Reason:
Informational message. This message appears in the Execution and Summary Reports,
and indicates the number of COND=SUCCESS members processed with output model
directed to the DDname specified.
Action:
None.
ANAL041I
OUTPUT MODEL DIRECTED TO DDNAME ddname FOR count UNSUCCESSFULLY
PROCESSED MEMBERS
Reason:
and indicates the number of COND=FAILURE members processed with output model
directed to the DDname specified.
Action:
None.
ANAL050I
count ACTIONS SELECTED count MEMBERS TO BE PROCESSED.
Reason:
and indicates the number of actions selected for processing as well as the number of
members associated with those actions.
Action:
None.
ANAL051I
count MEMBERS WERE NOT FOUND IN "USING" DATA SETS AND PROCESSING WAS
BYPASSED.
Reason:
and indicates the number of members in FROM data sets for which no corresponding
output member in a USING data set was found.
Action:
Make sure that the USING data set list contains all of the associated output data sets to
be used for analysis.
ANAL052I
count MEMBERS WERE PROCESSED WITH count MATCHING EXACTLY ONE
TYPE/PROCESSOR GROUP RULE.
Reason:
and indicates the total number of members analyzed as well as the number of members
that were successfully processed; that is, those members for which exactly one type and
processor group were established.
Action:
None.
ANAL053I
count DID NOT MATCH ANY TYPE/PROCESSOR GROUP CRITERIA.
Reason:
and indicates the number of members analyzed for which no type and processor group
were established.
Action:
Review the Execution Report. Either you need more information about the members or
you may need to modify some rules.
ANAL054I
count MATCHED MORE THAN ONE TYPE/PROCESSOR GROUP CRITERIA.
Reason:
and indicates the number of members analyzed for which more than one type and
processor group were established.
Action:
Review the Execution Report. Either you need more information about the members or
you may need to modify some rules.
ANAL055I
nnn MEMBERS MATCHED TYPE type name GROUP group name
Reason:
Informational message. This summary is provided at the end of the job listing the types
and groups for which members were successfully matched, and indicates how many
matches occurred.
Action:
None.
ANAL100I
REQUEST STMT #number:
Reason:
that the next logical request will be read and parsed. Each logical request is assigned a
statement number.
Action:
None.
ANAL101E
MEMBER REQUIRED ON ANALYZE STATEMENT
Reason:
The member name clause, which must be specified, was omitted from the ANALYZE
statement.
Action:
Correct the ANALYZE statement by adding a member name.
ANAL102E
MEMBER SPECIFIED MUST BE A LOWER VALUE THAN THE THROUGH MEMBER
SPECIFIED
Reason:
A THROUGH clause was specified on an ANALYZE statement. The member specified has
a greater value than the through member specified, resulting in no possible members in
the range.
Action:
Correct either the member name or the through member name.
ANAL103E
"FROM" DATA SET REQUIRED ON ANALYZE STATEMENT
Reason:
The FROM data set clause, which must be specified, was omitted from the ANALYZE
statement.
Action:
Specify the FROM data set name on the ANALYZE statement, or include a SET statement
with the FROM clause in the request data set prior to the ANALYZE statement, or run
with source, opt parameter.
ANAL110S
STORAGE ERROR, INCREASE REGION SIZE (function-name)
Reason:
An attempt to obtain storage failed.
Action:
Increase the region size on the JOB or EXEC card.
ANAL111E
INVALID CHARACTERS PRESENT IN MEMBER NAME FIELD-"member"
Reason:
The member name field contains some invalid characters or an invalid sequence of
characters.
Action:
Correct the member name. A member name can contain only the characters: A- Z, 0-9,
@, #, and $. In addition, you can use a question mark (?) as a character placeholder and
an asterisk (*) as a terminating wildcard. However, you cannot code any characters
following an asterisk. Also, you cannot use embedded blanks
ANAL199I
END-OF-FILE ENCOUNTERED ON REQUEST DATA SET
Reason:
that the request data set was completely parsed.
Action:
None.
ANAL200I
RULE STMT #number:
Reason:
Informational message. This message appears in the Execution Report, and indicates the
next rule to be read and parsed. Each rule read is assigned a statement number.
Action:
None.
ANAL201E
INVALID CHARACTERS PRESENT IN FIELD -"value"
Reason:
The member name field contains an invalid sequence of characters.
Action:
Correct the field value. A question mark (?) can be used as a character placeholder, and
an asterisk (*) can be used as a terminating wildcard.
ANAL202E
WHEN CLAUSE REQUIRED, OMITTED
Reason:
No WHEN clause was coded for this rule definition. A rule definition requires a WHEN
clause.
Action:
Add a valid WHEN clause to the rule definition.
ANAL203E
INVALID QUALIFIER SPECIFIED WITH EXTERNAL DEFINED OPERAND, "ANY" OR
"PRIMARY" ARE VALID
Reason:
A Format 1 expression was specified using an invalid qualifier. Valid qualifiers for this
format are ANY and PRIMARY.
Action:
Correct the qualifier in the expression.
ANAL204E
INVALID QUALIFIER SPECIFIED WITH RULE DEFINED OPERAND, "ANY" OR "ONLY" ARE
VALID
Reason:
A Format 3 expression was specified using an invalid qualifier. Valid qualifiers for this
format are ANY and ONLY.
Action:
ANAL205E
INVALID OPERATOR, MUST USE EQUALS OR CONTAINS CLAUSE
Reason:
A Format 2 expression was specified using an invalid operator. Valid operators for this
format are EQUALS and CONTAINS.
Action:
Correct the operator in the expression.
ANAL206E
INVALID QUALIFIER, MUST USE "ANY", "ONLY", OR "PRIMARY"
Reason:
An expression was specified using an invalid qualifier. Valid qualifiers include ANY,
ONLY, and PRIMARY.
Action:
ANAL207E
RECURSIVE REFERENCE TO CURRENT DEFINE STATEMENT
Reason:
The current DEFINE statement contains a direct reference to the same category and
entity name. That is, the statement is trying to define a category/entity relationship
using that same category/entity as definition criteria.
Action:
Correct the recursive clause.
ANAL208E
INVALID PRIMITIVE FUNCTION, MUST USE "ATTRIBUTE", "CSECT DATA", "CSECT
NAME", "FOOTPRINT", "IDENTIFY DATA", "LINKAGE EDITOR", "TRANSLATOR", OR
"ZAP DATA"
Reason:
A Format 1 expression contains an invalid component reference. Valid component
references are as identified in the message.
Action:
Correct the component reference.
ANAL209E
EXPECTING AND/OR, NOT FOUND
Reason:
An incomplete expression was encountered when a Boolean AND or OR expression is
expected.
Action:
Correct the expression.
ANAL210E
category-name REFERENCED, BUT NEVER DEFINED category-name/entity-name
REFERENCED, BUT NEVER DEFINED
Reason:
After reading all rules, it was determined that references were made to categories
and/or entities that do not exist.
Action:
Either correct the reference or add the appropriate definition.
ANAL211E
category-name/entity-name HAS AN IMBEDDED, RECURSIVE REFERENCE TO
category-name/entity-name
Reason:
After reading all rules, it was determined that the initial category/entity contains an
imbedded, recursive reference to the second category/entity. That is, a category/entity
relationship was defined indirectly using this same category/entity as definition criteria.
Action:
Remove the recursive reference.
ANAL212I
category-name/entity-name DEFINED, BUT NEVER REFERENCED
Reason:
After reading all rules, it was determined that the category/entity was defined but that
no references exist.
Action:
None. This is a valid situation.
ANAL213S
Reason:
Action:
ANAL214E
DEFINED NAMES ARE LIMITED TO 8 CHARACTERS, "category-name" IS INVALID
Reason:
A Format 3 expression contained a reference to an invalid category name. Category
names cannot be greater than 8 characters
Action:
Correct the referenced category name.
ANAL215E
MAXIMUM SIZE FOR REFERENCED FIELD IS count CHARACTERS, "value" EXCEEDS THIS
LIMIT
Reason:
Comparison data exceeded the maximum allowable size for the field specified.
Action:
Change the comparison data identified so that it does not exceed the maximum length
for the specified field.
ANAL216E
COLUMN RANGE ENDING IS PRIOR TO LINE RANGE BEGINNING
Reason:
The data clause in a Format 2 expression contains an invalid column range specification.
The column range must specify a beginning column number which is less than (or equal
to) the ending column number.
Action:
Correct the column range specification.
ANAL217E
COLUMN RANGE MUST BE LARGE ENOUGH TO CONTAIN THE SOURCE TEXT
Reason:
The data clause in a Format 2 expression contains an invalid column range specification.
The column range must be at least large enough to contain the comparison data string.
For example, if the string contains 10 characters, the column range must include at least
10 columns.
Action:
Correct the column range specification.
ANAL218E
LINE RANGE ENDING IS PRIOR TO LINE RANGE BEGINNING
Reason:
The data clause in a Format 2 expression contains an invalid line range specification. The
line range must specify a beginning line number which is less than (or equal to) the
ending line number.
Action:
Correct the line range specification.
ANAL219W
LINE RANGE BEGINNING IS RELATIVE WITH AN ABSOLUTE RANGE ENDING, RESULTS
MAY BE UNPREDICTABLE
Reason:
The data clause in a Format 2 expression contains a confusing line range specification.
The line range specified contains a mixture of relative line numbers and absolute line
numbers.
Action:
None. This is a valid, although unusual, specification.
ANAL220W
LINE RANGE BEGINNING IS ABSOLUTE WITH A RELATIVE RANGE ENDING, RESULTS
MAY BE UNPREDICTABLE
Reason:
The data clause in a Format 2 expression contains a confusing line range specification.
The line range specified contains a mixture of relative line numbers and absolute line
numbers.
Action:
None. This is a valid, although unusual, specification.
ANAL221E
value FIELD INVALID
Reason:
The value indicated should be a valid numeric string, and may have a leading sign. The
value specified is not a valid numeric string.
Action:
Correct the number.
ANAL222E
value FIELD CONTAINS NON-NUMERIC DIGITS
Reason:
The value indicated should be a valid numeric string, and may have a leading sign. The
value specified is not a valid numeric string.
Action:
Correct the number.
ANAL223E
value FIELD IS TOO BIG TO PROCESS
Reason:
The value indicated should be a valid numeric string, possibly containing a leading sign.
The number may not exceed 15 digits.
Action:
Correct the number.
ANAL224E
RELATIVE LINE RANGE REFERENCE IS ONLY VALID FROM WITHIN A WITH-CLAUSE
Reason:
The data clause in a Format 2 expression contains an inappropriate line range
specification. The line range specified is a relative number, but is invalid unless
contained within a WITH clause.
Action:
Correct the line range number.
ANAL225I
category-name/entity-name DEFINED, BUT ONLY INDIRECTLY REFERENCED BY THE
CATEGORY NAME
Reason:
After reading all rules, it was determined that the category/entity was defined, but the
only references that exist are directed to the category as a whole, not the entity.
Action:
ANAL226I
CATEGORY category-name IS NOT REFERENCED BY TYPE type-name, PROCESSOR
GROUP processor-group-name
Reason:
After all rules were read, it was determined that this type and processor group made no
references to the specified category.
Action:
ANAL299I
END-OF-FILE ENCOUNTERED ON RULES DATA SET
Reason:
that the rules data set was completely parsed.
Action:
None.
ANAL301I
MODEL LINE #number: text
Reason:
Informational message. This message appears in the Execution Report, and indicates the
next model definition input line to be read and parsed. Each line read is assigned a line
number.
Action:
None.
ANAL302E
TEMPLATE DATA FOUND BEFORE ANY CONTROL CARD, BYPASSED
Reason:
A data line was encountered prior to a model definition control card. This data card
cannot be associated with any output DD statement.
Action:
Correct the positioning of this template data line.
ANAL303W
DDNAME ddname SPECIFIED HAS NOT BEEN ALLOCATED, PROCESSING FOR THIS FILE
WILL BE BYPASSED
Reason:
The DDname specified in this control card is not allocated. Output processing associated
with this DD statement will not occur.
Action:
None. Make sure the DDname has been correctly specified.
ANAL310E
DDNAME SPECIFIED IS GREATER THAN 8 CHARACTERS
Reason:
The DDname specified in this control card is invalid. DDnames cannot exceed 8
characters.
Action:
Correct the DDname specification.
ANAL311E
DDNAME MISSING FROM CONTROL CARD
Reason:
The DDname is a required operand on the output model definition control card.
Action:
Add the DDname specification.
ANAL312E
OPERAND FOLLOWING DDNAME IS INVALID
Reason:
The DDname was specified and is followed by an unrecognizable operand. The only valid
operand after the DDname is the COND clause.
Action:
Correct the control card specification.
ANAL313E
COND CLAUSE MISSING VALUE
Reason:
The COND clause is missing the operand value. The COND clause can be specified as one
of the following:
COND=SUCCESS
COND=FAILURE
COND=(SUCCESS,FAILURE)
Action:
Correct the COND clause specification.
ANAL314E
COND CLAUSE INVALID
Reason:
The COND clause contains an unrecognizable value. The COND clause can be specified as
one of the following:
COND=SUCCESS
COND=FAILURE
COND=(SUCCESS,FAILURE)
Action:
Correct the COND clause specification.
ANAL315S
Reason:
Action:
ANAL401I
REQUEST #number: ANALYZE MEMBER member-name
Reason:
Informational message. This message appears in the Final Request Interpretation
section of both the Execution and Summary Reports. All applicable global parameters
were merged with the request and each ANALYZE request is printed a final time. This
message represents the beginning of an ANALYZE request that contains a single member
specification, which may be wildcarded.
Action:
None.
ANAL402I
REQUEST #number: ANALYZE MEMBER member-name THROUGH member-name
Reason:
section of the Execution and Summary Reports. All applicable global parameters were
merged with the request and each ANALYZE request is printed a final time. This message
represents the beginning of an ANALYZE request that contains a member name range.
Action:
None.
ANAL403I
ASSIGN symbolic = "value"
Reason:
section of the Execution and Summary Reports. For each request, a complete set of
symbolics is printed, along with their associated values. When more than one symbolic
is associated with the request, message ANAL404I prints the additional symbolics.
Action:
None.
ANAL404I
symbolic = 'value'
Reason:
section of the Execution and Summary Reports, and is a continuation of message
ANAL403I.
Action:
None.
ANAL405I
FROM DSNAME 'data set-name'
Reason:
section of the Execution and Summary Reports. For each request, a complete list of
source (FROM) data sets is printed. When more than one source data set is associated
with the request, message ANAL406I prints the additional data set names.
Action:
None.
ANAL406I
'data set-name'
Reason:
ANAL405I.
Action:
None.
ANAL407I
USING DSNAME 'data set-name'
Reason:
section of the Execution and Summary Reports. For each request, a complete list of
output (USING) data sets is printed. When more than one output data set is associated
with the request, message ANAL408I prints the additional data set names.
Action:
None.
ANAL408I
'data set-name'
Reason:
ANAL407I.
Action:
None.
ANAL411I
RULE #number: DEFINE category-name entity-name WHEN
Reason:
Informational message. This message appears in the Rule Interpretation section of the
Execution Report, and represents a rule which is defining an entity within a category.
The rule number matches the number assigned when the rule was originally read and
parsed.
Action:
None.
ANAL412I
RULE #number: ESTABLISH TYPE type-name PROCESSOR GROUP
processor-group-name WHEN
Reason:
Execution Report, and represents a rule which is establishing a processor group for a
type. The rule number matches the number assigned when the rule was originally read
and parsed.
Action:
None.
ANAL413I
when-clause-text
Reason:
Execution Report, and reflects the interpreted WHEN clausewith each operand,
whether specified or assumed, explicitly stated. Each logical expression begins on a new
line and may continue over several lines. All parentheses are shown.
Action:
None.
ANAL500I
PROCESSING REQUEST STATEMENT number:
Reason:
that the specified logical request will be processed.
Action:
None.
ANAL501I
REQUEST number MEMBER number:
Reason:
that member analysis is about to begin.
Action:
None.
ANAL502I
ANALYZE MEMBER member-name
Reason:
Informational message. This message appears in the Execution Report, and identifies
the member being analyzed.
Action:
None.
ANAL504I
FROM DSNAME 'data set-name'
Reason:
the source (FROM) data set used for analyzing the member. If the member is found in
multiple source data sets, this message identifies the member used for analysis.
Message ANAL505I identifies the other source data sets in which the member is located.
Action:
None.
ANAL505I
*IGNORED* 'data set-name'
Reason:
additional source data sets that contain occurrences of the member currently being
analyzed. These occurrences are not used during the analysis. Message ANAL504I
identifies the source data set which is used to analyze the member.
Action:
None.
ANAL506E
MEMBER NOT LOCATED IN ANY "USING" DATA SETS
Reason:
The member to be analyzed was found in at least one source (FROM) data set, but not
found in any of the associated output (USING) data sets. Since the request contained a
list of output data sets, an output member is required. The data sets examined for the
output member are listed after this message, using message ANAL507I.
Action:
If the output member exists in an output data set, add that data set to the list of USING
data sets. If no output exists for this member, place this member in a separate request
with no USING data sets or run with source opt parameter.
ANAL507I
DSNAME 'data set-name'
Reason:
Informational message. This message appears in the Execution Report, immediately
following message ANAL506E. This message identifies the output (USING) data sets
searched for the member occurrence.
Action:
None. Refer to message ANAL506E.
ANAL508I
USING DSNAME 'data set-name'
Reason:
the output (USING) data set used for analyzing the member. If the member is found in
multiple output data sets, this message identifies the member used for analysis.
Message ANAL509I identifies the other output data sets in which the member is located.
Action:
None.
ANAL509I
*IGNORED*'data set-name'
Reason:
additional output data sets that contain occurrences of the member currently being
analyzed. These occurrences are not used during the analysis. Message ANAL508I
identifies the output data set which is used to analyze the member.
Action:
None.
ANAL512E
MEMBER ANALYSIS TERMINATED
Reason:
Analysis for the member is terminated. This message follows message ANAL506E.
Action:
Refer to message ANAL506E.
ANAL513S
Reason:
Action:
ANAL514E
ERROR ALLOCATING DATA SET "data set-name", REQUEST TERMINATED
Reason:
Allocation of the data set failed; the request is terminated.
Action:
Refer to the preceding allocation error messages.
ANAL515E
ERROR VALIDATING DATA SET "data set-name", REQUEST TERMINATED
Reason:
Validation of the data set failed; the request is terminated.
Action:
Refer to the validation error messages immediately preceding this message.
ANAL516E
DATA SET "data set-name" IS SEQUENTIAL, REQUEST TERMINATED
Reason:
Sequential data sets may not be used for analysis; the request is terminated.
Action:
Remove the sequential data set from the data set list.
ANAL517E
ERROR BUILDING MEMBER LIST FROM DATA SET "data set-name", REQUEST
TERMINATED
Reason:
An attempt to read the data set directory failed; the request is terminated.
Action:
Refer to the error messages immediately preceding this message.
ANAL518I
MODULE SOURCE IS:
Reason:
Informational message. This message appears in the Execution Report when analysis for
a member failed (message ANAL520E or ANAL522E). The member source is listed, using
message ANAL529I, to assist in determining the reason behind the failure.
Action:
None.
ANAL519E
MEMBER ANALYSIS TERMINATED BY USER EXIT
Reason:
The user exit set a return code of 08, forcing member analysis to terminate.
Action:
None.
ANAL520E
ANALYSIS OF MEMBER member-name FAILED, NO RULES MATCHED
Reason:
Analysis of the member is unable to establish a type and processor group combination.
All information known about the member is formatted and printed following this
message.
Action:
Review the module information and rule summary to determine whether any rule
modifications should be performed. Make sure that the correct member source and
outputs were used for the analysis.
ANAL521I
MEMBER member-name MATCHES RULE #number, TYPE type-name PROCESSOR
GROUP processor-group-name SELECTED.
Reason:
Informational message. This message appears in the Execution Report, and lists each
type and processor group that matched the member being analyzed.
Action:
None.
ANAL522E
MEMBER member-name MATCHED count RULES, UNABLE TO SELECT APPROPRIATE
TYPE/PROCESSOR GROUP
Reason:
Analysis of the member is unable to result in establishing a single type and processor
group combination. Several ANAL523I messages immediately follow this message,
identifying the rules matched. All information known about the member is also
formatted and printed.
Action:
Review the module information and rule summary to determine whether any rule
modifications should be performed. Make sure that the correct member source and
outputs were used for the analysis.
ANAL523I
RULE #number, TYPE type-name PROCESSOR GROUP processor-group-name
Reason:
Informational message. This message appears in the Execution Report, and lists each
type and processor group that matched the member being analyzed. Immediately
follows message ANAL522E.
Action:
None.
ANAL524I
MODULE ATTRIBUTES ARE:
Reason:
Informational message. This message appears in the Execution Report. After this
message, you see a list of the load module attributes. This message immediately
precedes message ANAL525I.
Action:
None.
ANAL525I
attribute-text
Reason:
Informational message. This message appears in the Execution Report, and identifies all
load module attributes. This message immediately follows message ANAL524I.
Action:
None.
ANAL526I
MODULE CSECT NAMES AND TRANSLATORS ARE:
Reason:
message, you see a list of all CSECTs and translators. This message immediately
Action:
None.
ANAL527I
ESD #: number CSECT NAME: csect-name TRANSLATOR: translator-1 translator-2
Reason:
CSECTs and translators. This message immediately follows message ANAL526I. The
primary CSECT and translator is identified by an arrow.
Action:
None.
ANAL528I
LINKAGE EDIT TRANSLATOR IS: translator
Reason:
the linkage editor translator.
Action:
None.
ANAL529I
module-source-text
Reason:
Informational message. This messages appears in the Execution Report, and lists the
member source. This message immediately follows message ANAL518I.
Action:
None.
ANAL530I
LIST OF DEFINITIONS WITH RESULTS:
Reason:
message, you see a list of all defined categories and entities. This message immediately
Action:
None.
ANAL531I
MAJOR CATEGORY: category-name MINOR CATEGORY: entity-name RESULT: state
Reason:
defined categories and entities. There are three possible results: TRUE, FALSE, and
UNRESOLVED. This message immediately follows message ANAL530I.
Action:
None.
ANAL532I
MODULE IDENTIFY DATA RECORDS ARE:
Reason:
message, you see a list of linkage editor identify data. This message immediately
precedes messages ANAL533I and ANAL534I.
Action:
None.
ANAL533I
ESD #: number DATA='identify-data'
Reason:
linkage editor identify data contained in a load module. This message immediately
follows message ANAL532I and can be used in combination with message ANAL534I.
Action:
None.
ANAL534I
ESD #: number FOOTPRINT: SITE: site-id ENVIRONMENT: env-name SYSTEM:
system-name SUBSYSTEM: subsystem-name
Reason:
CSECT footprints contained in a load module. This message immediately follows
message ANAL532I and can be used in combination with message ANAL533I.
Action:
None.
ANAL535I
TYPE: @08CN STAGE: @01CN ELEMENT: @10CN VVLL: @02CY@02CY
Reason:
This is a continuation of message ANAL534I.
Action:
None.
ANAL536I
MODULE ZAP DATA RECORDS ARE:
Reason:
message, you see a list of all zap data. This message immediately precedes message
ANAL537I.
Action:
None.
ANAL537I
ESD #: number DATA='zap-data'
Reason:
zap data. This message immediately follows message ANAL536I.
Action:
None.
ANAL601S
Reason:
Action:
API Messages
ANAL602E
** NO TYPE RULES HAVE BEEN ESTABLISHED
Reason:
This message is produced during the analysis phase, and indicates that no rules were
established for any types.
Action:
Establish rules for types and groups.
ANAL603E
MEMBER member-name NOT FOUND IN DATA SET data set-name
Reason:
When loading the source member from the source data set, the member was not found.
This should never occur since the member was validated prior to actually beginning
member analysis.
Action:
Rerun the job.
API Messages
The API uses return codes and reason codes to report on the status of your API function
calls. Messages are returned for validation errors (WTO), the trace error log (BSTERR),
the API diagnostic log (BSTAPI), and the API internal trace log (EN$TRAPI).
API Messages
API Return Codes

The return code is presented to you in two ways, through register 15 and through the
AACTL_RTNCODE field. The following is a list of possible return codes that may result
after an API function call:
00
Indicates an informational message. Processing concluded normally.
Severity level:
04
Indicates a warning message. An error was encountered that was not serious
enough to terminate processing.
Severity level:
08
Indicates a caution message. An error was encountered that may prevent further
processing.
Severity level:
12
Indicates an error message. An error was encountered that terminated processing
of the current action, but allowed CA Endevor SCM to continue with the next action
request.
Severity level:
16
Indicates a severe message. A severe error was encountered that prevented CA
Endevor SCM from completing the requested action. Processing terminates
immediately. This category includes internal, system, and I/O errors.
Severity level:
20
Indicates a fatal message. No further processing is possible.
API Messages
API Reason Codes

Each return code has a reason code associated with it. The reason code is presented to
you through register 0 and through the AACTL_REASON field. The following list includes
all possible reason codes that can accompany a return code. For each return code and
reason code combination, the list shows the associated problem and an explanation.
00, 000
No problems
Request ended successfully.
04, 001
Environment not found
Occurs on ALENV function calls. An IMR error message is associated with this error. You
can find the message in the output message file specified through the control structure.
If the EN$TRAPI DD statement is included, the message also appears there.
The high message ID field in the control structure: The IMR message code (for example
IMGR001E).
04, 002
Stage not found
Occurs on ALSTG function calls. An IMR error message is associated with this error. You
IMGR001E).
04, 003
System not found
Occurs on ALSYS function calls. An IMR error message is associated with this error. You
can find this message in the output message file specified through the control structure.
IMGR005E).
API Messages
04, 004
Subsystem not found
Occurs on ALSBS function calls. An IMR error message is associated with this error. You
The high message ID field in the control structure: he IMR message code (for example
IMGR005E).
04, 005
Type not found
Occurs on ALTYP function calls. An IMR error message is associated with this error. You
IMGR013E).
04, 006
Element not found
Occurs on ALELM function calls. An IMR error message is associated with this error. You
IMGR009E).
04, 007
Processor group not found
Occurs on an ALPGR function call. An IMR error message is associated with this error.
You can find this message in the output message file specified through the control
structure. If the EN$TRAPI DD statement is included, the message also appears there.
IMGR013E).
API Messages
04, 008
Data set not found
Occurs on an ALDSN function call. An IMR error message is associated with this error.
You can find this message in the output message file specified through the control
IMGR005E).
04, 009
Approver group not found
Occurs on an ALAGR function call. An IMR error message is associated with this error.
The message can be found in the output message file specified through the control
IMGR018E).
04, 010
Approver junction not found
Occurs on an ALAGJ function call. An IMR error message is associated with this error.
The message can be found in the output message file specified through the control
IMGR019E).
04, 011
No packages found
No packages were found to match the package ID specified. Either no package exists
with that package ID or security rules eliminated that package from being selected.
04, 012
No packages selected
No packages were found to match the selection criteria. Either the selection criteria
specified in the request block or a package user exit caused all the packages to be
eliminated. If you are unable to determine why no packages were selected, you can
activate the EN$TRAPI trace to give you the reason each package was eliminated. Note
that output is produced for each package returned.
API Messages
04, 013
Requested version/level not found
An element function call was issued with a version or level that does not exist or an
illogical element function call was issued (for example, changes of vv.11 1.00).
The high message ID field in the control structure: AP04013W.
04, 014
No component data exists
An element component function call was issued. The element exists, but there is no
component data.
The high message ID field in the control structure: AP04014W.
04, 015
No changes exists
No changes exist for the element or component list you specified.
04, 016
An extract element request was made on a sourceless element
The extract element and component data API function call (API AEELM request) results
in a return code of 04 and a reason code of 016 when an extract element request is
made on a sourceless element.
08, 001
No found condition detected
A request was made to perform a package list action against an entity that does not
exist. Refer to the E-level messages for detailed information.
08, 002
CAST function issued caution messages
The caution messages can be found in the CAST report.
12, 000
An action request to CA Endevor SCM failed
The action has failed, but no message has been passed back to the API. A return code of
12 has been returned, but no reason has been given. See the Execution Report, where
the message code and text of a severity 12 message can be found.
API Messages
12, 001
Reserved field error
A request structure contains data within one of its reserved fields. The only valid
character is a blank. An error message is written out to the file reference by the BSTERR
DD statement. The message contains more information concerning the error.
The high message ID field in the control structure: AP12001E.
12, 002
Field value error
A request structure contains invalid data within one of its fields. An error message is
written out to the file reference by the BSTERR DD statement. The message contains
more information concerning the error.
12, 003
$IMR error
An IMR error occurred while processing an extract function call. The message associated
with this error can be found in the output message file, which was specified through the
control structure. If the EN$TRAPI DD statement was included, the message also
appears there.
The high message ID field in the control structure: The IMR message code.
12, 004
File validation error
A validation error was detected on a response file by C1SSDVLD. An API message also
with the CA Endevor SCM validation error message is written out to the trace data set
(EN$TRAPI), if specified in the JCL stream. A Write to Operator (WTO) message is issued
for the CA Endevor SCM validation error.
12, 005
File RECFM error
An unsupported RECFM of 'U' was used on a response file (either the message file or a
list/extract file). A WTO message is issued and if the EN$TRAPI DD statement was
included, the message also appears there.
API Messages
12, 006
Response file I/O error
An I/O error occurred while writing a record to the response file. An API message is
written to the trace file, EN$TRAPI, if specified. If the user has a message response file,
the actual CA Endevor SCM error message is written there.
12, 007
Message file I/O error
An I/O error occurred while writing a record to the message file. An API message is
written to the trace file, EN$TRAPI, if specified.
12, 008
$SMR error
A $SMR error occurred while processing an extract function call. The message
associated with this error can be found in the output message file which was specified
through the control structure. If the EN$TRAPI DD statement was included, the message
also appears there.
The high message ID field in the control structure: The SMR message code
12, 009
Extract file I/O error
An I/O error occurred while writing a record to the output extract file. An API message is
written to the trace file, EN$TRAPI, if specified. If the user has a message response file,
the actual CA Endevor SCM error message is written there.
12, 010
Storage unavailable
Storage was unavailable. Increase the region size and try again. An error message is
written out to the file reference by the BSTERR DD statement. The message contains
more information concerning the error.
API Messages
12, 012
Request failed by package exit 7
A user defined package exit 7 caused this request to terminate.
12, 013
Invalid status for this request
The status of this package is not in the correct state required to perform this action. For
example, a package must be IN-EDIT status to cast it or in APPROVED status to execute
the package. IN-EXEC and EXECUTE status are also permitted for the execute action if
the package is in a failed state. See the detailed error message for a list of value statuses
for the action you are attempting to perform.
12, 014
Endevor package processing detected an error condition
Refer to the E-level PKMR message in the message file for detailed information. Most
likely the requested package does not exist, or an attempt to create an existing record
occurred. For the EXECUTE action, refer to the C1EXMSGS file for detailed error
information. If the package is an enterprise package, an action restriction may have
been detected.
12, 015
Unable to allocate the BSTIPT01 file
Unable to allocate the BSTIPT01 file. This temporary data set is necessary to execution a
package. This is an internal error condition. One of the allocation parameters specified is
not valid at your site. Review the E-level messages in the message file for detailed
information.
12, 016
An enterprise correlation exists
A request was made to associate an enterprise correlation with a package. A
relationship already exists and only one relationship is permitted. For a RESET action,
this action is not allowed if a enterprise correlation exists.
12, 017
No enterprise correlation records are associated with this package
A request was made to modify or delete an enterprise correlation associated with a CA
Endevor SCM package. No enterprise correlations are associated with this package.
API Messages
12, 019
Batch package error detected
Errors were detected by the package facility. This is usually an allocation error related
to one of the following reasons:
The IMPORT SCL data set
The import DD statement was not specified in the JCL
The import data set or member specified does not exist
Review the C1MSGS1 file for details.
12, 020
SCL allocation error
The API allocates a temporary file to hold SCL statements. The allocation of this file
failed. Review the message file for details.
The high message ID field in the control structure: AP16001S.
12, 021
ACM error
The ACMQ facility detected an error when attempting to retrieve component data.
Review the E-level messages for detailed information.
12, 022
Shareability error
The package action (CAST, DELETE, or RESET) was attempted against a non-sharable
package, and the user is not the owner or a super-user.
16, 001
AACTL_SHUTDOWN
Invalid characters given. You must use (Y)es, (N)o or leave the field blank.
16, 002
AACTL_MSG_DDN is invalid
The DD name of the message file was not allocated. Make sure that the DD statement is
specified in the JCL stream. No error message is produced.
API Messages
16, 003
Too many request structures
ENA$NDVR was presented with a multiple request structure. Only one request may be
presented to the interface. No error message is produced.
16, 004
No request structure
ENA$NDVR was called without a request structure. No error message is produced.
16, 005
Too many response structures
ENA$NDVR was presented with a multiple response structure. Only one response can be
presented to the interface. No error message is produced.
16, 006
No response structure
ENA$NDVR was called without a response structure. No error message is produced.
16, 007
Request not response
ENA$NDVR was presented with a response structure that does not correspond to the
request structure. No error message is produced.
16, 008
AACTL_LIST_DDN is invalid
The DD name of the response file was not allocated. Make sure that the DD statement is
specified in the JCL stream. No error message is produced.
API Messages
16, 009
C1BMINIT failed
CA Endevor SCM initialization failed - C1BMINIT. An error message is written out to the
file reference by the BSTERR DD statement. The message contains more information
concerning the error. The API server terminates.
16, 012
A severe error was detected when attempting to execute a package
Check the JES log for file related problems. Most likely, CA Endevor SCM was unable to
allocate the C1EXMSGS file required for the package execution messages due to a
missing DD statement or file attributes.
16, 013
Invalid REB id
The ID associated with the request extension block is invalid. Check the header of the
AAREB block to make sure it contains the proper values.
16, 014
Multiple AAREB blocks encountered
The API expects one and only one AAREB block per request. Multiple AAREB blocks exist.
16, 015
AAREB block not allowed
The AAREB block is only allowed for actions that support long names.
16, 016
One the AACTL block was found and shutdown flag is not Y
If only the AACTL block is specified, the shutdown flag must be Y.
16, 017
SCL write error
Unable to write the SCL to the temporary file. Internal error.
API Messages
16, 018
Unauthorized API caller
An unauthorized program attempted to execute an API function that requires
authorization.
20, 001
Control structure eye-catcher is invalid
ENA$NDVR was presented with a control structure that does not have a valid
eye-catcher string. The control structure return and reason codes will not be set. The
codes are returned through register 15 and 0 respectfully. The control structure cannot
be used to return the codes since its structure is damaged.
20, 002
Control structure id is invalid
ENA$NDVR was presented with a control structure that has an invalid control structure
ID. The control structure return and reason codes will not be set. The codes are
returned through register 15 and 0 respectfully. The control structure cannot be used to
return the codes since its structure is damaged.
20, 003
Control structure version number is invalid
ENA$NDVR was presented with a control structure that does not have a valid version
number. The control structure return and reason codes will not be set. The codes are
returned through register 15 and 0 respectfully. The control structure cannot be used to
return the codes since its structure is damaged.
20, 004
Control structure length is invalid
ENA$NDVR was presented with a control structure that has an invalid control structure
length value. The control structure return and reason codes will not be set. The codes
are returned through register 15 and 0 respectfully. The control structure cannot be
used to return the codes since its structure is damaged.
20, 005
ROLLIST error
Internal error: ROLLIST error. The ROLFSPEC is not valid. An API message is written to
the BSTAPI DD file.
API Messages
20, 006
ROLFFUNC error
Internal error: ROLLIST error. The ROLFFUNC is not valid. An API message is written to
the BSTAPI DD file.
20, 007
Type not in ROLLIST
Internal error: ROLLIST error. Type not found in ROL-LIST. An API message is written to
the BSTAPI DD file.
20, 008
Invalid type in ROLLIST
Internal error: ROLLIST error. Invalid type found in ROL-LIST. An API message is written
to the BSTAPI DD file.
20, 009
$PINIT failed
$PINIT failure during an API function call. An API message is written to the BSTAPI DD
file.
20, 010
REQMSG not in ROLLIST
Internal error: ROLLIST error. OTREQMSG not found in ROL-LIST. An API message is
written to the BSTAPI DD file.
20, 011
$PGET failed
$PGET failure during an API function call. An API message is written to the BSTAPI DD
file.
API Messages
20, 012
$PSEND failed
$PSEND failure during an API function call. An API message is written to the BSTAPI DD
file.
20, 013
$BGETSTG for $API failed
Storage could not be obtained. An API message is written to the BSTAPI DD file.
20, 014
$BATTACH failed
Attach failure. An API message is written to the BSTAPI DD file.
20, 015
$PWAIT failed
$PWAIT failure during an API function call. An API message is written to the BSTAPI DD
file.
20, 016
$PRECV failed
$PRECV failure during an API function call. An API message is written to the BSTAPI DD
file.
20, 017
$PFREE failed
$PFREE failure during an API function call. An API message is written to the BSTAPI DD
file.
API Messages
20, 018
Internal message area is too small
Internal error. Storage area within the ENA$NDVR interface program is too small to
construct the message request.
20, 019
Structure cross check
Internal error. The structure pointers in the message request does not point to the
correct structure headers that are contained in the message request. An API message is
written to the BSTAPI DD file.
20, 020
AAMSG structure improper
Internal error. The AAMSG structure list (message request) is improper. The pointer list
is not an even multiple. An API message is written to the BSTAPI DD file.
20, 021
AAMSG structure not found
Internal error. The AAMSG structure list does not contain an entry for the structure
returned by the API server. An API message is written to the BSTAPI DD file.
20, 022
P2PMSG structure improper
Internal error. The P-to-P structure sent by the API server is improper. The total
structure size within the AAMSG did not agree with the P-to-P structure. An API
message is written to the BSTAPI DD file.
20, 023
ENAPIMGR parameter length error
Internal error. The API manager received its parameter list with an invalid length. An API
message is written to the BSTERR DD file. The API server terminates.
API Messages
20, 024
ENAPIMGR parameter EYE error
Internal error. The API manager expected to receive a parameter list that maps to
$AAPRM. The parameter it received did not contain the identifier string of '$AAPRM'. An
API message is written to the BSTERR DD file. The API server terminates.
20, 025
$PHDL failed
Internal error. $PHDL failure during an API server initialization. An API message is
written to the BSTERR DD file. The API server terminates.
20, 026
Invalid request id
Not used.
20, 027
AAMSG structure EYE invalid
Internal error. The API received an invalid message structure that did not conform to its
expected ENHAAMSG layout. An API message is written to the BSTERR DD file. The
server waits for another message request.
20, 028
No control structure in AAMSG
The API server received a request but the control structure was not found after the
message structure AAMSG. An API message is written to the BSTERR DD file. The server
waits for another message request.
20, 029
Control structure is invalid
The API server received a request which had an invalid control structure. An API
message is written to the BSTERR DD file. The server waits for another message request.
API Messages
20, 030
Structure lengths do not add up
The API server expects to receive a message control request with four structures:
AAMSG, AACTL, request, and response structure. During the validation process the total
lengths of these structures did not agree with the value stored in the message structure.
An API message is written to the BSTERR DD file. The server waits for another message
request.
20, 031
Request structure invalid
The request structure within a message request structure could not be identified. An API
message is written to the BSTERR DD file. The server waits for another message request.
20, 032
Response structure invalid
The response structure within a message request structure could not be identified. An
API message is written to the BSTERR DD file. The server waits for another message
request.
20, 033
Server error
A severe error was detected by the API Server. Review the log for additional error
messages.
API Messages
API Element Action Messages

All messages issued by the API are written to the file supplied in the AACTL_MSG_DDN
field of the CONTROL storage block. This file is optional. If you do not specify one, you
need to rely on the return and reason codes to determine the results of your request.
We recommend that you provide a message file name. The following possible messages
are issued by the API element action program (ENAPIACT). All messages issued by the
parser program (C1BM4100) and the action-processing program (C1BM4200) are
written to this file. This output is similar to what you see when viewing the reports
produced by a foreground or batch action request.
The following API messages include possible causes and actions to take in error
situations:
API0000C
CAUTION(S) DETECTED, PROCESSING COMPLETE, REVIEW THE ddname EXECUTION
REPORT FOR DETAILS
Reason:
Caution conditions occurred during the execution of an element action through the API
interface.
Action:
Review the execution report for details. Getting this message does not mean that the
action failed.
API0000E
Syntax error detected
Reason:
This message is issued when a syntax error is detected in the request block data.
Action:
Review the other detailed E level messages to determine the fields in error. Correct any
errors and rerun the job.
API Messages
API0000I
Text
Reason:
Informational message. Intended to give you information related to your request.
Action:
None.
API0000S
Text
Reason:
This message is issued when a severe error is detected in the API request. This is an
internal error. Most likely, an invalid function code was detected.
Action:
None.
API0000W
Text
Reason:
Intended to give you information related to your request. This message is issued when
records are returned but fail to pass the selection criteria specified on the request.
Action:
None.
API0001E
Both the DDNAME and DSNAME are specified. Only one of the two values can be
specified
Reason:
This message is issued when both DDNAME and DSNAME are specified in the request
block.
Action:
Specify either the DDNAME or DSNAME in the request block, but not both.
API Messages
API0002E
The ff field value must be blank or a value 1-99. vv is invalid
Reason:
The value you specified in this request block field is invalid. ff indicates the field in error
and vv indicates the value you specified.
Action:
Correct the field value.
API0003E
The ff field value must be Y or N. v is invalid
Reason:
and v indicates the value you specified.
Action:
Change the value to Y, N, or to use the default, leave it blank.
API0004E
The ff field value must be blank. v is invalid
Reason:
and v indicates the value you specified. This is a reserved field and must be left blank.
Action:
Set the field value to a blank.
API0005E
ff1 and ff2 are not specified. One of the two fields must be specified
Reason:
One of the two fields must contain a value. ff1 indicates the first field and ff2 indicates
the second field.
Action:
Specify the values for the identified fields.
API Messages
API0006E
ff1 and ff2 are specified. Only one of the two fields can be specified
Reason:
Both of the two fields contain a value, causing a conflict. ff1 indicates the first field and
ff2 indicates the second field.
Action:
Correct the specification. Remove the value from one of the two fields.
API0007E
The ff field value must be 1 or 2. v is invalid
Reason:
Action:
Change the value to a 1 or a 2.
API0008E
The ff field value must be A, C, or R. v is invalid
Reason:
Action:
Change the value to A, C, or R or to use the default, leave it blank.
API0009S
Unable to obtain storage to create where CCID/Process Group chain. Result=rc.
Reason:
This is an internal error.
Action:
Increase the region size in this step or job and rerun.
API Messages
API0010E
SEARCH is only valid when you have selected the COPYBACK option.
Reason:
The SEARCH action option can only be used along with the COPYBACK option.
Action:
Either code the COPYBACK option or code a value of N in the search field.
API0011E
The ff field value must be blank or a value of 0-99. vv is invalid.
Reason:
Action:
Correct the specification.
API0012E
THE field-name FIELD VALUE MUST BE B, C, H, L, M, S OR BLANK.
Reason:
The AEPRE_RQ_PRT_OPT field value in the API Print Element request is invalid. Valid
options are: B, C, H, L, M, S and blank.
Action:
Action:
Specify a value of blank, B, C, H, M, or S.
API Messages
API0013E
The (M)aster option is not valid when requesting component data
Reason:
The master print option is only allowed along with element data. You selected this
option along with the component data option.
Action:
None.
API0014E
The ff field value must be S or E. v is invalid
Reason:
Action:
Specify a value of S or E.
API0015E
The ff field value must be CR, MO, CA, AP, EX, BO, BI, or CO. vv is invalid
Reason:
and vv indicates the value you specified
Action:
Specify a value of CR, MO, CA, AP, EX, BO, BI, or CO.
API0016E
The ff field value must be comprised of National Standard Characters
Reason:
The value you specified in this request block field is invalid. ff indicates the field in error.
Valid characters are 0-9, A-Z, @, #, and $.
Action:
Specify a character value of 0-9, A-Z, @, #, or $.
API Messages
API0017E
The ff field value must be blank or a value of 0-999. vvv is invalid
Reason:
and vvv indicates the value you specified.
Action:
Specify a value that is either blank, or a value of 0-999.
API0018E
The ff field value is blank or contains a wildcard (*) or placeholder (%) char
Reason:
Action:
You must specify a fully qualified value for this field.
API0019E
The ff field value must be H, I, or U. v is invalid
Reason:
Action:
Specify a value of H, I, or U.
API0020E
No from DDNAME or DSNAME was specified. One of the two values must be provided
Reason:
You did not provide a DDNAME or DSNAME for this request.
Action:
Specify a DDNAME or DSNAME for this request.
API Messages
API0021E
The ff field value must be C, D, or M. v is invalid
Reason:
Action:
Specify a value that is either C, D, or M.
API0022E
PKG status must be IN-APPR, APPROVED, or DENIED in order to approve or deny.
Status is v
Reason:
You are only allowed to approve or deny a package when the package status is IN-APPR,
APPROVED, or DENIED. v indicates the current status of the package.
Action:
Change the status of the package to IN-APPR, APPROVED, or DENIED.
API0023E
Status must be IN-EDIT, CAST, IN-APPROVAL, APPROVED or DENIED to create a
correlation. Status is pkg-name.
Reason:
You are only allowed to modify a correlation when the package status is IN-EDIT, CAST,
IN-APPROVAL, APROVED or DENIED.
Action:
If you need to create, delete, or modify a correlation, change the package status.
API Messages
API0024EPKG
Status must be APPROVED, IN-EXEC, or EXEC-DONE in order to execute. Status is v
Reason:
You are only allowed to execute a package when the status is APPROVED, IN-EXEC, or
EXEC-DONE. v indicates the current status of the package.
Action:
Specify a status of APPROVED, IN-EXEC, or EXEC-DONE to execute the package.
API0025E
Unable to allocate the BSTIPT01 file
Reason:
Unable to allocate the BSTIPT01 file. This temporary data set is necessary for execution
of a package. This is an internal error condition.
Action:
One of the allocation parameters specified is not valid at your site. Review the other
E-level (error) messages in the message file for detailed information.
API0026E
An enterprise correlation already exists for this package
Reason:
A request was made to associate an enterprise correlation with an package. A
relationship already exists.
Action:
Make sure that only one relationship is defined, as only one relationship is permitted.
API0027E
No correlation records are associated with this package
Reason:
A request was made to modify or delete a correlation associated with an package. No
correlations are associated with this package.
Action:
None.
API Messages
API0028E
The ff field value must be A, E, or X. v is invalid
Reason:
Action:
Specify a value of A, E, or X.
API0029E
The ff field value must be L or P. v is invalid.
Reason:
Action:
Specify a value of L or P.
API0030E
The ff field value must be F or A. v is invalid.
Reason:
Action:
Specify a value of F or A.
API0031E
The ff field value must be A, B, E, N, or R. v is invalid.
Reason:
Action:
Specify an A, B, E, N, or R.
API Messages
API0032E
The ff field value must be specified when the search field value is B or R.
Reason:
The "to environment/stage ID" fields must be specified when the search value is
(B)etween or (R)ange. ff indicates the field in error.
Action:
API0033E
The ff field value contains an invalid character or an embedded blank.
Reason:
Action:
The value must consist of the values 1-9, A-Z, or #, $, or @.
API0034E
The ff field value must be blank. v is invalid.
Reason:
Action:
Change the specification to a blank.
API0035E
The ff field value must be a *, %, 1, 2, or blank. vv is invalid
Reason:
Action:
Specify a *, %, 1, 2, or a blank.
API Messages
API0036E
The ff field value must be B or blank. vv is invalid.
Reason:
The value you specified in this request block is invalid. ff indicates the field in error and
vv indicates the value you specified.
Action:
Specify a B or a blank.
API0037E
The ff execution window date and/or time is invalid or time is missing.
Reason:
The formats of the date or time field values are invalid.
Action:
The date field must contain a valid date in the format of DDMMMYY (for example,
31JAN02). The format of the time must be HH:MM (for example, 23:59 or 00:00).
API0038E
The execution window TO date/time is less than the FROM date/time.
Reason:
The FROM date/time value must be less than the TO date/time value.
Action:
Change the FROM date/time value to a value that is less than the TO date/time value.
API0039E
The ff field value must be B, C, H, or blank. vv is invalid
Reason:
Action:
Specify a B, C, H, or a blank.
API Messages
API0040E
The ff field value must be E or C. vv is invalid.
Reason:
Action:
Specify an E or a C.
API0041E
An enterprise correlation exists for this package. Action is not allowed.
Reason:
You must perform the delete correlation action prior to executing this action.
Action:
Perform the delete correlation action first, and then execute the intended action.
API0042E
Path name must be specified when processing an HFS file structure.
Action:
The presence of the AAREB block indicates long name processing. The HFS from/target
path name must be specified in this block.
Reason:
Specify the HFS from/target path name in this block.
API0043E
DDNAME and DSNAME cannot be specified when processing an HFS file structure.
Action:
You cannot specify both DDNAME and DSNAME when you process an HFS file
structure.
Reason:
Specify either the DDNAME or DSNAME name in the request block, but not both.
API Messages
API0044E
The ff field and the request extension block are both specified
Action:
You cannot specify both this field and the request extension block.
Reason:
For HFS processing, all element and member names must be coded in the request
extension block.
API0045E
The ff field value must be specified
Action:
The package description field must be coded when creating a package.
Reason:
When creating a package, you must specify a description.
API0046E
Specify 1 and only 1 of the copy from or import from values
Action:
Both the copy from field and the import from field were coded.
Reason:
Decide if you want to create this package by copying another package or by importing
SCL.
API0047E
The ff field value must be C or M. v is invalid
Action:
Reason:
Specify a C or M.
API Messages
API0048E
The append option can only be specified when modifying a package
Action:
The append option was coded for a create package request.
Reason:
Do not code the append option when creating a package.
API0049E
Package exists and function is not modify. v is invalid
Action:
The function code must be M (modify) for an existing package.
Reason:
Code a function code of M.
API0050E
Package does not exist and function is not create. v is invalid.
Reason:
The function code must be C or M. If M is specified, the package must already exist.
Action:
Specify function code C or M. The package must already exist if you specify M.
API0051E
The ff field value must be A, D, G, M, or blank. v is invalid.
Reason:
Action:
Specify an A, D, G, M, or a blank.
API Messages
API0052E
The ff field value must be A, C, G, L, R, or blank. v is invalid.
Reason:
Action:
Specify an A, C, G, L, R, or a blank.
API0053E
The ff field value must be specified when a CCID value is specified.
Reason:
When you specify the CCID value, you must also specify the ff field value.
Action:
Specify a valid ff field value along with the CCID value.
API0054E
The vv generate vv field is invalid. The format must be vv.
Reason:
The value you specified in this request block field is invalid.
Action:
Specify a valid value.
API0055W
The defaults table indicates comp validation is required. Value overridden.
Reason:
The value you specified conflicts with the defaults table value. The defaults table value
is overridden.
Action:
None.
API Messages
API0056E
From vv name value is less than thru name value.
Reason:
From vv name value cannot be less than the through name value.
Action:
Specify a from name value that is greater than the through name value.
API0057E
Path name invalid. It must begin and end with a forward slash.
Reason:
The path name you specified must begin and end with a forward slash.
Action:
Include a slash as the beginning and ending character of the path name.
API0058E
List action is not allowed against a sequential or null file, DSORG=vv.
Reason:
The list action is not allowed against the type of data set that you specified.
Action:
None.
API0059W
CSECT option ignored, dataset is not a load library (RECFM=U).
Reason:
CSECTs only exist for load modules. Option is ignored and processing continues.
Action:
None.
API Messages
API0060E
Call to CONIDRDS failed. Internal error.
Reason:
Internal error. CA Endevor SCM attempted to retrieve the footprint information and
encountered an error.
Action:
None.
API0061E
Specify either stage ID or stage number, but not both.
Reason:
Only one of the two values can be specified.
Action:
Specify either the stage ID or the stage number.
API0064E
PKG status must be IN-EDIT in order for the package to be modified. Status is vv.
Reason:
You are only allowed to modify a package when it is in IN-EDIT status.
Action:
Use the RESET function to set this package back to the IN-EDIT status, and then modify
the package.
API0065S
Unable to write to the temporary SCL dataset.
Reason:
Internal error. CA Endevor SCM allocates a temporary file to hold generated SCL
statements. A write to this file failed.
Action:
Make sure the file was successfully allocated.
API Messages
API0066E
Errors were detected by the package facility. Review the C1MSGS1 file for details.
Reason:
The package facility detected errors. The C1MSGS1 file contains the error details.
Action:
Review the C1MSGS1 file for error details. If this file does not exist, add the C1MSGS1
DD statement to your JCL and re-execute the job.
API0067E
The copy from package, vv, does not exist.
Reason:
The package ID specified in the copy from package does not exist.
Action:
Specify a valid package ID and resubmit the copy from package.
API0068E
The ff field value must be C or W. v is invalid.
Reason:
Action:
Change the value to C for a component list request, or to W for a where-used request.
API0069E
The ff field value must be blank or UPLOADDD when APDEF_RQ_RMTSCL=Y.
Reason:
The value you specified in this request block field is invalid.
Action:
If APDEF_RQ_RMTSCL=Y, the field must be blank or UPLOADDD.
API Messages
API0070E
Copy from PKG ID and IMPORT FROM DSN must be blank when
APDEF_RQ_RMTSCL=Y.
Reason:
The value you specified in the request block field is invalid.
Action:
The PKGID and IMPORT FROM DSN fields must be blank when using the remote SCL
option.
API0071E
The ff field value must be C, E, M, O, or blank. v is invalid.
Reason:
The value you specified in the request block field is invalid. ff indicates the field in error
Action:
Change the value to a C, E, M, O, or leave it blank.
API0072E
The SCL file, ff, must be defined as RECFM=FB, LRECL=80.
Reason:
You requested SCL to be written to the AACTL_LIST_DDN file. The attributes of this file
must be fixed blocked and the record length must be 80.
Action:
Change the attributes of the file to RECFM=FB, LRECL=80.
API Messages
API0073E
The response file, AACTL_LIST_DDN, must be specified when the build SCL option is
requested.
Reason:
You requested that SCL be written to the response file, but the response file field,
AACTL_LIST_DDN, is blank.
Action:
Specify the AACTL_LIST_DDN response file and resubmit.
API0074E
THE ff FIELD VALUE MUST BE BLANK, A, F, OR B. v IS INVALID
Reason:
The value of the status field must be A (approved), F (execfailed), or B (both approved
and execfailed). The value you specified is invalid.
Action:
Correct the value of this field and rerun your job.
API0075E
THE MULTIPLE JOBSTREAM AND INCREMENT JOBNAME OPTIONS ARE NOT ALLOWED
WITH CA-7 REQUESTS
Reason:
These two features cannot be used along with CA 7 requests.
Action:
Remove the values from these fields and rerun the job.
API Messages
API0076E
THE SCL TYPE FIELD VALUE MUST BE A, C, E, P, R OR S. x IS INVALID
Reason:
The value you specified in the SCL TYPE field is invalid.
Action:
Make sure that the type of SCL request specified in the AUSCL_RQ_SCLTYPE is one of
the following valid values:
A-for Environment administration actions
C-for CSV actions
E-for Element actions
P-for Package actions
S-for Package ship actions
API0077E
THE EXECUTION MESSAGE FILE ddname IS NOT ALLOCATED
Action:
Possible ddname values are C1MSGS1, BSTRPTS, or C1BMXLOG.
API0078W
THE AACTL_LIST_DDN FIELD VALUE ddname IS IGNORED BY THE API SCL FUNCTION
Reason:
The value coded in the AACTL_LIST_DDN field was ignored by the API SCL function.
Action:
The AACTL_LIST_DDN field should be left blank, because the API SCL function does not
return response records. If a value is coded, it is ignored by the API SCL function. Due to
field validation logic, if you code a value, you must include a DD statement in your JCL.
API0079
ERRORS WERE DETECTED. REVIEW THE ddname EXECUTION REPORT FOR DETAILS
Action:
Possible ddname values are C1MSGS1, BSTRPTS, or C1BMXLOG.
API Messages
API0080E
UNABLE TO LOCATE THE DESTINATION ID IN THE SCL COMMAND
Reason:
The destination ID value was not found in the SCL statement.
Action:
The destination id value must be located in the first 65 characters of the SCL statement.
API0081E
THE (L)ISTING OPTION IS NOT VALID WITH NOCC OPTION OR WHEN REQUESTING
COMPONENT DATA
Reason:
On an API Print Element action request, you cannot specify a Y value in the
AEPRE_RQ_NOCC and AEPRE_RQ_COMP fields when AEPRE_RQ_PRT_OPT is set to L.
Action:
API0081S
UNABLE TO ALLOCATE THE TEMPORARY JCL FILE
Reason:
CA Endevor SCM is unable to allocate a temporary JCL file required to build the JCL to
execute the PROC statement.
Action:
None.
API0082E
THE LIST TEXT STRING IS ONLY VALID WITH THE (L)ISTING OPTION
Reason:
The above message applies to the API Print Element action request. You cannot specify
a listing text string if the print option has a value other than L.
Action:
API Messages
API0083E
ERROR DETECTED WRITING TO THE TEMPORARY JCL FILE
Reason:
CA Endevor SCM is unable to write to the temporary JCL file it is building containing the
EXEC PROC statement and SCL statement.
Action:
None.
API0084E
THE @20CY VALUE MUST BE L (LOCAL), S (BDT1) OR X (XCOM). @1CY I S INVALID.
Reason:
This message indicates that the specified transmission method is not supported by the
API ship facility.
Action:
The only three transmission methods supported by the API ship facility are L (LOCAL), S
(BDT1) and X (XCOM).
API0085E
THE REQUESTED PACKAGE ACTION WAS NOT EXECUTED: THE PACKAGE IS NOT
SHARABLE.
Reason:
The API program attempted a CAST, RESET, or DELETE package action against a
non-sharable package, and the user was not the owner or a super-user.
Action:
Validate the package name. If it is correct, ask the owner to make the package sharable.
API Messages
API0086E
THE ff FIELD VALUE MUST BE Y, N OR W. v IS INVALID
Reason:
Action:
Change the value to Y, N, W, or to use the default, leave it blank.
API0090S
The ff field value is invalid. This is an internal error. The unknown function value is vvv
Reason:
The API is unable to determine the type of request due to an invalid function code. ff
indicates the field in error and vvv indicates the value found.
Action:
Determine the valid function code for your request and resubmit.
API0091W
pp/gg is an EXT APPRV GRP. The SEL APPRVR ID, xx does not match the ACEE ID, yy
Reason:
The API is unable to determine if this user is associated with this external approver
group. The API continues to check all other groups, looking for non-external approver
groups containing an approver ID that matches the selection ID. pp is the package name,
gg is the approver group name, xx is the selection approver ID specified in the request
block, and yy is the TSO/jobname.
Note: This message appears only under the following conditions: list package header
action is requested; the selection approver ID is specified and it is different than the
TSO/jobname user ID; the approver group is an external approver group.
Action:
None.
API Messages
API0092E
THE CAST @4CY FIELD IS INVALID. THE FORMAT MUST BE @7CY
Reason:
The package list selection criteria cast from date and time, or the thru date and time, or
both are coded incorrectly.
Action:
Specify the cast dates and times in the proper format. The date format is DDMMMYY.
The time format is hh:mm.
API0093E
THE CAST FROM DATE/TIME CANNOT BE GREATER THAN THE THRU DATE/TIME
Reason:
The cast selection criteria are incorrectly coded.
Action:
Specify a cast from date and time that is the same as, or earlier than, the cast through
date and time.
API0100E
Informational message
Reason:
This message is intended to give you the information related to your request.
Action:
None.
API0100I
Reason:
Informational message intended to give you the information related to your request.
Same as message ID API0000I except that the timestamp is not printed.
Action:
None.
API Messages
API0101I
Beginning of API action processing
Reason:
Bookend to indicate the API action processing has begun.
Action:
None.
API0102I
Dispatching API action
Reason:
Bookend to indicate the request block contains no syntax errors and the action is being
dispatched.
Action:
None.
API0103E
API EXECUTION WITHIN A PROCESSOR NOT ALLOWED
Reason:
The execution of the API SCL feature is not allowed in a processor.
Action:
Remove the API SCL feature execution step from the processor.
API0104E
RETURN OPTION INVALID, MUST BE (A)LL OR (L)AST
Reason:
The Return option on the List Package Ship request is invalid.
Action:
Change the Return option to either A, for return all records, or L, for return the last
record. Then resubmit the request.
API Messages
API0105E
DATA OPTION INVALID, MUST BE Y, N, S, or C
Reason:
The DATA option (field ALELM_RQ_BDATA) specified in the ALELM_RQ control block is
invalid.
Action:
Change the DATA option to a valid option: Y, N, S, or C. Then resubmit the request.
API0106E
ALELM_RQ_WCCID_TYP FIELD VALUE CANNOT BE S UNLESS SUMMARY DATA IS
REQUESTED
Reason:
The WHERE CCID TYPE option (field ALELM_RQ_WCCID_TYP) specified in the ALELM_RQ
control block contains an S (WHERE CCID OF CHANGE), but the DATA SUMMARY (field
ALELM_RQ_BDATA equal to S or C) was not specified.
Action:
Add the DATA SUMMARY (field ALELM_RQ_BDATA equal to S or C) and resubmit the
request.
API0107E
THE ALPKG_RQ_PROMFILTY FIELD VALUE MUST BE A, P, X OR BLANK. x IS INVALID
Reason:
A value other than A, P, X, or blank was specified in the ALPKG_RQ_PROMFILTY field.
Action:
Specify a valid value in the ALPKG_RQ_PROMFILTY field and resubmit the request.
API Messages
API0108E
TARGET ENV AND STAGE ID FILTERS ARE NOT ALLOWED WHEN FILTER TYPE IS X
Reason:
A promotion package target environment or a stage ID filter was specified on a request
that also specified a value of X for ALPKG_RQ_PROMFILTY, which filters out all
promotion packages. This combination is not allowed.
Action:
If you want the selection list to include promotion packages, the ALPKG_RQ_PROMFILTY
value must be blank, A, or P. If you want the selection list to exclude all promotion
packages, specify a value of X for the ALPKG_RQ_PROMFILTY filter, but do not specify a
target environment or stage ID. Correct the values and resubmit the request.
API0109E
THE ALPKG_RQ_PROMFILEN VALUE SPECIFIED; environment, DOES NOT EXIST
Reason:
The promotion package target environment specified on the selection list filter does not
exist.
Action:
Specify a valid environment and resubmit the request.
API0110E
THE ALPKG_RQ_PROMFILSI VALUE SPECIFIED; x, DOES NOT EXIST WITHIN THIS ENV
Reason:
The promotion package target stage ID specified on the selection list filter does not exist
in the specified environment.
Action:
Specify a stage ID that exists within the specified environment. If no environment was
specified, specify a stage ID that exists within the Defaults (C1DEFLTS) table definitions.
Resubmit the request.
API Messages
API0111E
THE PROMOTION HISTORY OPTION CANNOT BE REQUESTED WHEN FILTER TYPE IS X
Reason:
The promotion package history filter was specified on a request to create a selection list
when the filter type specified a value of X, which excludes all promotion packages.
Action:
If you want the selection list to include promotion packages, the ALPKG_RQ_PROMFILTY
value must be blank, A, or P. Correct the value and resubmit the request.
API0113W
THE LIST ELEMENT SUMMARY ACTION CANNOT BE REQUESTED WHEN ONLY
SOURCE-LESS ELEMENTS ARE FOUND
Reason:
All the elements that meet the search criteria on the List Element request are
source-less elements, meaning their element source and delta files are not present at
the location specified on the request. The action does not try to resolve the true
location of the source.
Action:
Modify the inventory location on the request to where the source is located.
BSTAPI Messages
The following messages are written to the BSTAPI data set (API diagnostic trace):
BC1PAPI
rc,reason ROLFSPEC NOT VALID - INTERNAL ERROR.
Reason:
This message is written to the BSTAPI DD file when an internal ROL LIST error occurs, an
invalid ROLFSPEC. API request processing terminates.
API Messages
BC1PAPI
rc,reason ROLFFUNC NOT VALID - INTERNAL ERROR.
Reason:
This message is written to the BSTAPI DD file when an internal ROL LIST error occurs,
and invalid ROLFFUNC. API request processing terminates.
BC1PAPI
rc,reason TYPE NOT FOUND IN ROL-LIST - INTERNAL ERROR.
Reason:
This message is written to the BSTAPI DD file when an internal ROL LIST error occurs;
type not found in ROL-LIST. API request processing terminates.
BC1PAPI
rc,reason INVALID TYPE IN ROL-LIST - INTERNAL ERROR.
Reason:
invalid type found in ROL-LIST. API request processing terminates.
BC1PAPI
rc,reason $PINIT FAILED WITH RC=xxxx DURING API CALL
Reason:
This message is written to the BSTAPI DD file when an internal $PINIT function fails. The
return code is recorded in the message. API request processing terminates.
BC1PAPI
rc,reason REQMSG NOT FOUND IN ROL-LIST - INTERNAL ERROR.
Reason:
OTREQMSG not found in the ROL-LIST. API request processing terminates.
API Messages
BC1PAPI
rc,reason $PGET FAILED WITH RC=xxxx DURING API CALL.
Reason:
This message is written to the BSTAPI DD file when an internal $PGET function fails. The
BC1PAPI
rc,reason $PSEND FAILED WITH RC=xxxx DURING API CALL.
Reason:
This message is written to the BSTAPI DD file when an internal $PSEND function fails.
The return code is recorded in the message. API request processing terminates.
BC1PAPI
rc,reason $PWAIT FAILED WITH RC=xxxx DURING API CALL.
Reason:
This message is written to the BSTAPI DD file when an internal $PWAIT function fails.
BC1PAPI
rc,reason $PFREE FAILED WITH RC=xxxx DURING API CALL.
Reason:
This message is written to the BSTAPI DD file when an internal $PFREE function fails. The
BC1PAPI
rc,reason $PRECV FAILED WITH RC=xxxx DURING API CALL.
Reason:
This message is written to the BSTAPI DD file when an internal $PRECV function fails.
API Messages
BC1PAPI
rc,reason $BGETSTG FOR @API STORAGE FAILED - xxxxxxxx.
Reason:
This message is written to the BSTAPI DD file when storage was not obtained for the
@API control block. The storage reason characters are recorded in the message. API
request processing terminates.
BC1PAPI
rc,reason $BGETSTG FOR $API STORAGE FAILED (ATTACH) - xxxxxxxx
Reason:
This message is written to the BSTAPI DD file when storage was not obtained for the
$API control block. The storage result characters are recorded in the message. API
request processing terminates.
BC1PAPI
rc,reason $BATTACH FAILED - xxxxxxxx
Reason:
This message is written to the BSTAPI DD file when the API server was not attached. The
attach result characters are recorded in the message. API request processing
terminates.
BC1PAPI
rc,reason BUILDMSG - AAMSG STRUCTURE CROSS-CHECK FAILED
Reason:
This message is written to the BSTAPI DD file when the BUILDMSG routine detects an
error during the construction of the P-to-P message structure. Before building the P-to-P
structure, the pointers to the caller's structure headers are cross-checked against the
message request. This is an internal error. API request processing terminates.
API Messages
BC1PAPI
rc,reason BUILDMSG - AAMSG STRUCTURE LIST IMPROPER
Reason:
This message is written to the BSTAPI DD file when the BUILDMSG routine detects an
error during the construction of the P-to-P message structure. The message request
structure pointer list was found to structure. The pointer list structure of the message
request was NOT an even multiple when checked against the message request pointer
list length. This is an internal error. API request processing terminates.
BC1PAPI
rc,reason COPYMSG - AAMSG STRUCTURE LIST IMPROPER
Reason:
This message is written to the BSTAPI DD file when the COPYMSG routine detects an
error while updating the caller area with data from the P-to-P message structure. The
pointer list structure of the message request was NOT an even multiple when checked
against the message request pointer list length. This is an internal error. API request
processing terminates.
BC1PAPI
rc,reason COPYMSG - P2PMSG STRUCTURE LIST IMPROPER
Reason:
This message is written to the BSTAPI DD file when the COPYMSG routine detects an
error while updating the caller area with data from the P-to-P message structure. The
message request total structure size value did not agree with the total P-to-P message
received from the API server. This is an internal error. API request processing
terminates.
API Messages
BSTERR Messages
The following messages are written to the BSTERR data set (trace error log):
ENAPISUB
re,reason FIELD VALIDATION ERROR FIELD=field name LENGTH=field length
VALUE=field value.
Reason:
This message is written to the file referenced by the BSTERR DD statement when a field
fails its validation.
Action:
Correct the field in error.
ENAPIEXT
rc,reason EELMRUTN - STORAGE UNAVAILABLE FOR BUFFER, RC=xxxxx
RESULT=xxxxxxxx
Reason:
This message is written to the file referenced by the BSTERR DD statement when an
element extract request failed to acquire buffer storage. The RC/RESULT fields are our
internal get storage error codes.
ENAPIMGR
rc,reason C1BMINIT ENDED WITH RC=xxxxx
Reason:
This message is written to the file referenced by the BSTERR DD statement when the
C1BMINIT initialization of CA Endevor SCM fails. A return code from C1BMINIT is
recorded in the message. The API server terminates.
ENAPIMGR
rc,reason PARM FIELD CONTAINS AN INCORRECT LENGTH - xxxx
Reason:
This message is written to the file referenced by the BSTERR DD statement when the API
Manager receives a parameter list that has an incorrect length. The parameter list
should be mapped to $AAPRM. This is an internal error. API server terminates.
API Messages
ENAPIMGR
rc,reason PARM FIELD CONTAINS BAD EYE-CATCHER - xxxxxx
Reason:
This message is written to the file referenced by the BSTERR DD statement when the API
Manager receives a parameter list that has an incorrect identifier character string. The
parameter list should be mapped to $AAPRM. This is an internal error. API server
terminates.
ENAPIMGR
rc,reason $PINIT FAILED WITH RC=xxxx DURING INIT
Reason:
This message is written to the BSTERR DD file when an internal $PINIT function fails. The
return code is recorded in the message. API server terminates.
ENAPIMGR
rc,reason $PHDL FAILED WITH RC=xxxx DURING INIT
Reason:
This message is written to the BSTERR DD file when an internal $PHDL function fails. The
ENAPIMGR
rc,reason $PGET FAILED WITH RC=xxxx DURING INIT
Reason:
This message is written to the BSTERR DD file when an internal $PGET function fails. The
ENAPIMGR
rc,reason $PSEND FAILED WITH RC=xxxx DURING INIT
Reason:
This message is written to the BSTERR DD file when an internal $PSEND function fails.
The return code is recorded in the message. API server terminates.
API Messages
ENAPIMGR
rc,reason $PRECV FAILED WITH RC=xxxx DURING PROCESSING
Reason:
This message is written to the BSTERR DD file when an internal $PRECV function fails.
ENAPIMGR
rc,reason $PWAIT FAILED WITH RC=xxxx DURING PROCESSING
Reason:
This message is written to the BSTERR DD file when an internal $PWAIT function fails.
ENAPIMGR
rc,reason $PSEND FAILED WITH RC=xxxx DURING PROCESSING
Reason:
This message is written to the BSTERR DD file when an internal $PSEND function fails.
ENAPIMGR
rc,reason API REQUEST BLOCK - AAMSG DOES NOT VALIDATE xxxxxxxxxxxx
Reason:
This message is written to the BSTERR DD file when the API server does not receive a
proper message block. It expects the block to contain a character string identifier of
$MSG. The first 12 hexadecimal values are recorded in the message. The API server then
waits for another message block.
ENAPIMGR
rc,reason API CONTROL STRUCTURE NOT FOUND IN API REQUEST xxxxxxxxxxxx
Reason:
This message is written to the BSTERR DD file when the API server received a message
request without a control structure immediately following the message structure. The
first 12 hexadecimal values that follow the message structure are recorded in the
message. The API server then waits for another message block.
API Messages
ENAPIMGR
rc,reason UNABLE TO IDENTIFY THE CONTROL STRUCTURE xxxxxxxxxxxx
Reason:
request with an invalid control structure. The first 12 hexadecimal values of that
structure are recorded in the message. The API server then waits for another message
block.
ENAPIMGR
rc,reason STRUCTURE LENGTHS DO NOT ADD UP CORRECTLY
Reason:
request where its total structure length did not agree with the other structure lengths,
that is, the AAMSG length, the AACTL length, the request length, and the response
length. The API server then waits for another message block.
ENAPIMGR
rc,reason UNABLE TO IDENTIFY THE REQUEST STRUCTURExxxxxxxxxxxx
Reason:
request with an invalid request structure header. The first 12 hexadecimal values of that
structure are recorded in the message. The API server then waits for another message
block.
ENAPIMGR
rc,reason UNABLE TO IDENTIFY THE RESPONSE STRUCTURExxxxxxxxxxxx
Reason:
This message is written to the BSTERR DD file when the API server abends with
ENAPIMGR rc,reason API SERVER ABEND OCCURRED xxxx. The interface shuts down.
API Messages
EN$TRAPI Error Messages

The following messages are written to the EN$TRAPI data set (API internal trace):
ENAPISUB FOPO8000
FILE VALIDATE ERROR, DDNAME=file ddname
Reason:
This message is written to the file referenced by the EN$TRAPI DD statement when an
output file for the list and extract request fails the validation logic within C1SSDVLD. The
actual CA Endevor SCM error message follows this one. The API request completes with
a return reason code of 12,004.
ENAPISUB FOPO8000
FILE IS UNSUPPORTED RECFM, DDNAME=file ddname
Reason:
This message is written to the file referenced by the EN$TRAPI DD statement when a
RECFM=U is used on an output file (either the message file or a list/extract file). The API
request completes with a return reason code of 12,005.
ENAPISBUB FRSP8000
FILE I/O ERROR, DDNAME=file ddname RC=return code,MSG=Endevor message ID
Reason:
I/O error occurs on the LIST output file. The API request completes with a return reason
code of 12,006.
ENAPISUB FRCD8000
FILE I/O ERROR, DDNAME=file ddname,RC=return code,MSG=Endevor message ID
Reason:
I/O error occurs on the EXTRACT output file. The API request completes with a return
reason code of 12,009.
API Messages
ENAPISUB MSGIO800
FILE I/O ERROR, DDNAME=file ddname,RC=return code, MSG=Endevor message ID
Reason:
I/O error occurs on the message output file. The API request completes with a return
WTO Messages
The following WTO messages are issued for the validation errors:
BC1PAP1
API HALTED BECAUSE OF RC=00020 ENCOUNTERED.
Reason:
This message is sent to the operator's console when a severe error is encountered. The
AACTL block contains the return and reason codes for the failure. The API Server is
brought down.
ENAPISUB FOPO8000
FILE IS UNSUPPORTED RECFM, DDNAME=file ddname
Reason:
This message is sent to the operator console when a RECFM=U is used on an output file
(either the message file or a list/extract file). The API request completes with a return
B1E Message Codes
B1E Message Codes

B1E messages are issued by the CA Endevor SCM InfoMan Interface. These messages
use the following codes when describing corrective actions:
A
A indicates that the action should be tried again, after increasing the region size. If
this does not work, proceed according to the other suggestions for corrective
action.
B
B indicates that the full message text and return codes should be provided.
C
C indicates that either a SYSM or SYSABEND dump should be provided.
D
D indicates that the concatenation for the PIDT table should be provided.
E
E indicates that the data set attributes should be provided.
F
F indicates that the JES job log and all output listings should be provided.
G
G indicates that the script used as input should be sent to the batch utility.
B1E Messages
This section details the B1E messages issued by the CA Endevor SCM InfoMan Interface,
along with possible causes and corrective actions to take in error situations.
B1EI001I
Text
Reason:
Informational message.
Action:
None.
B1E Message Codes
B1EI010E
INFO/MAN API NOT ACTIVE
Reason:
The CA Endevor SCM side of the interface has failed to establish a connection with the
CA Endevor SCM InfoMan Interface, because the CA Endevor SCM InfoMan Interface is
not active.
Action:
Contact your CA Endevor SCM InfoMan Interface Administrator.
B1EI050E
INFO/MAN API OBTAIN RESOURCE REQUEST FAILURE IN module name: routine name
PIDT: pidt name
Reason:
This is a CA Endevor SCM InfoMan Interface error.
Action:
Examine any CA Endevor SCM InfoMan Interface error codes, and then contact your CA
Endevor SCM InfoMan Interface Administrator.
B1EI051E
INFO/MAN API INQUIRY REQUEST FAILURE IN module name: routine name
Reason:
Action:
Examine any CA Endevor SCM InfoMan Interface error codes; then contact your CA
Endevor SCM InfoMan Interface Administrator.
B1E Message Codes
B1EI052E
$PKMR EXTRACT FAILURE IN module name: routine name, RC=return code (HEX)
REASON=reason code (HEX)
Reason:
Internal error.
Action:
Provide the JES job log and all output listings; then contact your CA Endevor SCM
Administrator.
B1EI053E
REQUIRED PIDT SWORD s-word MISSING FROM table name TABLE
Reason:
A required S-word is missing from the IBM PIDT tables.
Action:
Contact your CA Endevor SCM InfoMan Interface Administrator. The required S-word
must be included in the PIDT table and in all other relevant places in the Info/Man
system. After updating the PIDT tables, rerun the batch utility before trying to restart
the interface.
B1EI054E
MORE THAN ONE INFO/MAN CHANGE RECORD EXISTS FOR PACKAGE package name
Reason:
There should be only one CA Endevor SCM InfoMan Interface Change record per
package.
Action:
Examine the Info/Man database, determine which Change record is the correct one;
then delete the other record.
B1E Message Codes
B1EI055E
$PKMR CREATE FAILURE IN module name: routine name, RC=return code (HEX)
Reason:
Internal error.
Action:
Administrator.
B1EI056E
THE CHANGE RECORD FOR PACKAGE package name WAS NOT FOUND IN INFO/MAN
DB
Reason:
The interface expects a Change record to exist in Info/Man for the named package, but
the record does not exist.
Action:
Create the record, reset the package if the message was generated during package
processing; then resubmit.
B1EI056W
THE CHANGE RECORD FOR PACKAGE package name WAS NOT FOUND IN INFO/MAN
DB
Reason:
The interface expects a Change record to exist in Info/Man for the named package, but
the record does not exist.
Action:
Create the record, reset the package if the message was generated during package
processing; then resubmit.
B1E Message Codes
B1EI057E
INFO/MAN API FREE PIDT REQUEST FAILURE IN module name: routine name
Reason:
Action:
Examine any Info/Man error codes; then contact your Info/Man Administrator.
B1EI058E
INFO/MAN API FREE PIRT REQUEST FAILURE IN module name: routine name
Reason:
Action:
B1EI059E
PURGE OF ACTIVITY RECORDS DURING RESET/AFTER FAILED
Reason:
Action:
B1EI060E
INFO/MAN API OBTAIN CREATE RESOURCE REQUEST FAILURE IN module name:
routine name PIDT: pidt name
Reason:
Action:
B1E Message Codes
B1EI061E
INFO/MAN API CREATE REQUEST FAILURE IN module name: routine name
Reason:
Action:
B1EI062E
INFO/MAN API OBTAIN ADD RELATION REQUEST FAILURE IN module name: routine
name PIDT: pidt name
Reason:
Action:
B1EI063E
INFO/MAN API CHECK-IN REQUEST FAILURE IN module name: routine name
Reason:
Action:
B1EI064E
INFO/MAN API CHECK-OUT REQUEST FAILURE IN module name: routine name
Reason:
Action:
B1E Message Codes
B1EI065E
INFO/MAN API ADD RELATION REQUEST FAILURE IN module name: routine name
Reason:
Action:
B1EI066E
INFO/MAN API UPDATE REQUEST FAILURE IN module name: routine name
Reason:
Action:
B1EI067E
INTERNAL ERROR - UNKNOWN STRUCTURE FOUND IN LABEL label name UNDER USE:
module name: routine name
Reason:
The script used to create the E/PIDT table contains an error.
Action:
Provide the JES job log and all output listings, obtain the script, and contact your CA
Endevor SCM Administrator.
B1EI068E
INFO/MAN TSP INVOCATION FAILURE IN BC1PEI50: TSPRUTN
Reason:
Action:
B1E Message Codes
B1EI069E
INFO/MAN API RETRIEVE REQUEST FAILURE IN module name: routine name
Reason:
Action:
B1EI070E
S-WORD s-word NOT FOUND IN RETRIEVE table name PIDT TABLE
Reason:
The named IBM PIDT table does not include the specified S-word.
Action:
Contact your Info/Man site Administrator. The specified S-word must be included in the
named PIDT table, and in all related locations in Info/Man. Make sure to rerun the batch
utility before restarting the interface.
B1EI071E
INTERNAL ERROR IN BC1PEI50 AT CRITRUTN, ENDEVOR KEYWORD keyword code NOT
RECOGNIZED OR DATE CONVERSION ERROR
Reason:
Internal error.
Action:
Administrator.
B1E Message Codes
B1EI072E
INTERNAL ERROR IN BC1PEI50, UNKNOWN STRUCTURE FOUND FOLLOWING A CFLD
SEGMENT IN LABEL label name
Reason:
Internal error.
Action:
Administrator.
B1EI073E
S-WORD s-word NOT FOUND IN table name PIDT TABLE
Reason:
The named IBM PIDT table does not include the specified S-word.
Action:
Contact your Info/Man site Administrator. The specified S-word must be included in the
named PIDT table, and in all related locations in Info/Man. Make sure to rerun the batch
utility before restarting the interface.
B1EI074E
INTERNAL ERROR IN BC1PEI50 AT POPLRUTN, ENDEVOR KEYWORD keyword code NOT
RECOGNIZED OR DATE CONVERSION ERROR
Reason:
Internal error.
Action:
Administrator.
B1E Message Codes
B1EI075W
POPULATION OF s-word BYPASSED. ONLY S-WORDS WHOSE DEFINITIONS ARE "R" OR
"X" CAN BE POPULATED
Reason:
The specified S-word has a definition that is other than R or X.
Action:
Contact your Info/Man Administrator. If you specify the S-word again, make sure to
rerun the batch utility before attempting to restart the interface.
B1EI076W
POPULATION OF s-word BYPASSED. TEXT FORMAT MUST BE USED AGAINST A FREE
FORM S-WORD DEFINITION
Reason:
The specified S-word was not populated because the script used to create the E/PIDT
table did not associate the TEXT keyword with the information to be stored in Info/Man.
Action:
Change the keyword associated with the relevant information to TEXT; then rerun the
batch utility.
B1EI077E
PURGE OF ACTIVITY RECORDS DURING THE CREATE ACTIVITY PROCESS FAILED
Reason:
Action:
B1EI078E
PURGE OF ACTIVITY RECORDS DURING THE PACKAGE DELETE PROCESS FAILED
Reason:
Action:
B1E Message Codes
B1EI079E
PURGE OF PARENT RECORD DURING THE PACKAGE DELETE PROCESS FAILED
Reason:
Action:
B1EI080E
INTERNAL ERROR - INSUFFICIENT STORAGE: module name routine name
Reason:
Internal error.
Action:
Administrator.
B1EI081E
INTERNAL ERROR - ALLOCATION ERROR IN BC1PEI50 ALLORUTN
Reason:
Internal error.
Action:
Administrator.
B1EI082E
OPEN FOR OUTPUT ON FREE FORM TEXT DSN: data set name FAILED
Reason:
Internal error.
Action:
Administrator.
B1E Message Codes
B1EI083E
WRITE TO FREE FORM TEXT DSN: data set name FAILED
Reason:
The interface was unable to write freeform text to the named data set.
Action:
Administrator.
B1EI084E
CLOSE OF FREE FORM TEXT DSN: data set name FAILED
Reason:
The interface was unable to close the named data set.
Action:
Administrator.
B1EI085E
$PKMR DELETE FAILURE IN module name: routine name, RC=return code (HEX)
Reason:
Internal error.
Action:
Administrator.
B1EI086E
INVALID ACTION CCID VALUE
Reason:
The CCID specified for an action contains blanks.
Action:
Submit the request again with a valid CCID. Contact your CA Endevor SCM Administrator
for a list of valid CCIDs.
B1E Message Codes
B1EI200E
NO PICA CONTROL BLOCK
Reason:
Initialization with the CA Endevor SCM InfoMan Interface failed, and the PICA block was
not allocated.
Action:
Administrator.
B1EI201E
LOAD OF THE INFO/MAN API SERVER "BLGYSRVR" FAILED
Reason:
The Info/Man BLGYSRVR module failed to load.
Action:
Examine any Info/Man error codes, then contact your Info/Man Administrator.
B1EI202E
INFO/MAN API INITIALIZATION FAILED, RC=return code (HEX), REASON=reason code
(HEX)
Reason:
The interface was unable to initialize the CA Endevor SCM InfoMan Interface.
Action:
Look up the specified return and reason code in the appropriate IBM Information
Management Family documentation and proceed accordingly.
B1EI203E
INFO/MAN API SERVER NOT ACTIVE
Reason:
The CA Endevor SCM InfoMan Interface server is not active.
Action:
Contact the Info/Man Administrator.
B1NM Messages
B1EI204E
INFO/MAN API SERVER TRANSACTION transaction number FAILED, RC=return code
(HEX), REASON=reason code (HEX)
Reason:
The specified CA Endevor SCM InfoMan Interface server transaction failed.
Action:
Look up the specified transaction number, return code and reason code in the
appropriate IBM Information Management Family documentation and proceed
accordingly.
B1EI205E
INFO/MAN API SERVER INITIALIZATION OR TRANSACTION FAILURE
Reason:
The CA Endevor SCM InfoMan Interface server could not be started.
Action:
Contact your Info/Man System Administrator (check SYSLOG for possible
Info/Man-related error messages).
B1NM Messages
B1NM messages are issued by the CA Endevor SCM CA Netman Interface. This section
details these messages along with possible causes and corrective actions to take in error
situations.
B1NM001E
ENDEVOR /NETMAN.COMMON STORAGE NOT AVAILABLE - ACTION CANCELLED.
Reason:
Storage needed by the CA Endevor SCM CA Netman Interface was unavailable.
Action:
The region size should be increased. This storage is obtained once through the
initialization exit of CA Endevor SCM.
B1NM Messages
B1NM002E
ENDEVOR/NETMAN USER DEFINITION TABLE BC1TNM90, WAS NOT LOADED - ACTION
CANCELLED.
Reason:
Module BC1TNM90 was not loaded, action cancelled.
Action:
Check library concatenation.
B1NM003E
ENDEVOR/NETMAN SESSION NOT ACTIVE BUT SESSION IS REQUIRED BY USER ACTION CANCELLED.
Reason:
The administrator turned on the CA Endevor SCM CA Netman Interface-required
indicator in the BC1TNM90 module.
Action:
All element and package actions are cancelled until you are able to successfully sign in
to CA Endevor SCM CA Netman Interface through the initialization process in CA
Endevor SCM. By allocating the trace data set and re-entering CA Endevor SCM, CA
Endevor SCM CA Netman Interface, and CCI error messages should be logged in this file.
Refer to these errors for a resolution.
B1NM004E
FIND ON TASK RECORD FAILED, RC=rc (HEX) RE=re (HEX) - ACTION CANCELLED.
Reason:
A CA Endevor SCM CA Netman Interface error occurred.
Action:
See previous logged error message for the proper resolution.
B1NM Messages
B1NM005E
CCID OF ccid FAILED VALIDATION - ACTION CANCELLED.
Reason:
The administrator turned on the CA Endevor SCM CA Netman Interface CCID validation
indicator in the BC1TNM90 module. The element action was cancelled because the CA
Endevor SCM CA Netman Interface task record for CCID validation was not defined.
Action:
Contact your CA Endevor SCM/CA Endevor SCM CA Netman Interface Administrator.
B1NM007E
FIND ON TASK RECORD FAILED DURING EXIT 3, RC=rc (HEX) RE=re (HEX).
Reason:
Action:
B1NM008E
FIND ON ACTION CHANGE RECORD FAILED DURING EXIT 3, RC=rc (HEX) RE=re (HEX).
Reason:
Action:
B1NM009E
CREATE OF ACTION CHANGE RECORD FAILED DURING EXIT 3, RC=rc (HEX) RE=re (HEX).
Reason:
Action:
B1NM Messages
B1NM010E
CREATE OF TASK RECORD FAILED DURING EXIT 3, RC=rc (HEX) RE=re (HEX).
Reason:
Action:
B1NM011E
CREATE OF TASK LOG RECORD FAILED DURING EXIT 3,RC=rc (HEX) RE=re (HEX).
Reason:
Action:
B1NM012E
INFO/MAN CAN NOT BE ACTIVE ALONG WITH NETMAN.
Reason:
Both the CA Endevor SCM CA Netman Interface and the InfoMan interface were
specified in the C1DEFLTS table. You can specify either CA Endevor SCM CA Netman
Interface or Info/Man, but not both.
Action:
Contact your CA Endevor SCM Administrator.
B1NM013E
COULD NOT LOAD DEFINITION TABLE - BC1TNM90.
Reason:
The BC1TNM90 table could not be loaded during initialization.
Action:
Check library concatenation.
B1NM Messages
B1NM014E
NO STORAGE AVAILABLE FOR NETMAN COMMUNICATION BLOCKS.
Reason:
Storage for the CA Endevor SCM CA Netman Interface ASR and ARB blocks is
unavailable.
Action:
Increase region size.
B1NM015E
NETMAN API SIGNON CALL FAILED, RC=rc (HEX) RE=re (HEX).
Reason:
The CA Endevor SCM CA Netman Interface signon function failed.
Action:
Allocate the trace data set and re-enter CA Endevor SCM. CA Endevor SCM CA Netman
Interface and CCI messages should appear in this data set. Refer to these messages for a
proper resolution.
B1NM016E BC1PNM50
NETMAN INTERFACE CALLED WITH INVALID FUNCTION function name.
Reason:
The CA Endevor SCM CA Netman Interface module BC1PNM50 was invoked with an
invalid function name. This should never occur (internal error).
Action:
B1NM Messages
B1NM017E
netman error message.
Reason:
An error occurred during a CA Endevor SCM CA Netman Interface function call.
Action:
Refer to the text message for the proper resolution. It may be necessary to turn on the
trace facility, re-enter CA Endevor SCM and retry the function that originally caused the
problem. Once an Interface error occurs, further CA Endevor SCM CA Netman Interface
functions are suspended. If the CA Endevor SCM CA Netman Interface-required indicator
is on in the BC1TNM90 module, both element and package actions will be cancelled.
B1NM018E BC1PNM50
IMPROPER USE OF THE NETMAN API CONTINUATION RULES.
Reason:
A CA Endevor SCM CA Netman Interface ASR command block contains API commands
with incorrect continuation syntax. Continuation syntax is not used by any of the CA
Endevor SCM or CA Endevor SCM CA Netman Interface modules. This error may be
introduced by the client when changing module BC1PNM60. This module is distributed
in source so that the client can alter Change, Task, and Log record field population.
Action:
The trace facility should be used to pinpoint the problem.
B1NM019E BC1PNM50
COMMAND STRING WRITTEN TO NTMADFR FILE, NETMAN PROCESSING DID NOT
OCCUR.
Reason:
Deferred processing is not supported by the Interface. This error should never occur.
Action:
B1NM Messages
B1NM020E BC1PNM50
NETMAN SENDDFR COMMAND FAILURE.
Reason:
Deferred processing is not supported by the Interface. This error should never occur.
Action:
B1NM021E BC1PNM50
NETMAN ARB BLOCK TOO SMALL, DATA CANNOT BE RETRIEVED.
Reason:
The CA Endevor SCM CA Netman Interface response block is too small and cannot be
used to hold all the requested data. This could be because the CA Endevor SCM CA
Netman Interface might not be active. This error should not occur (internal error).
Action:
B1NM022E BC1PNM50
NTMAPI PARAMETER LIST PROBLEM, INTERNAL ERROR.
Reason:
Turn on the trace facility and reproduce the problem.
Action:
Contact CA Technical Support with the trace log results.
B1NM023E BC1PNM50
NTMAPI INTERNAL LOGIC ERROR.
Reason:
An internal CA Endevor SCM CA Netman Interface logic error occurred.
Action:
Contact CA Technical Support. Try to obtain a CA Endevor SCM or CA Endevor SCM CA
Netman Interface log trace, if possible, before calling support.
B1NM Messages
B1NM024E BC1PNM50
UNKNOWN RETURN CODE OF rc (HEX) FROM NTMAPI.
Reason:
An internal CA Endevor SCM CA Netman Interface error occurred.
Action:
B1NM025E BC1PNM50
GCHGRUTN - COULD NOT FIND CHCHANGE FIELD WITHIN NETMAN'S ARB.
Reason:
An internal CA Endevor SCM/CA Endevor SCM CA Netman Interface error occurred.
Action:
B1NM026E BC1PNM50
CTSKRUTN - BUFFER AREA NOT LARGE ENOUGH TO HOLD ASR DATA. TASK RECORD
NOT CREATED.
Reason:
This error occurs when you modify the module's task record population routine in
BC1PNM60. This message indicates that insufficient room is left in the buffer for the
interface to append the closing command of ENTER. Although the buffer area is large, if
more is needed, there is no way of increasing the ASR data buffer area. This is a CA
Endevor SCM CA Netman Interface restriction.
Action:
None.
B1NM Messages
B1NM027E BC1PNM50
CCHGRUTN - BUFFER AREA NOT LARGE ENOUGH TO HOLD ASR DATA. CHANGE
RECORD NOT CREATED.
Reason:
This error occurs when you modify the module's change record population routine for
the CCID anchor record, the Package action record, or both in BC1PNM60. This message
indicates that insufficient room is left in the buffer for the Interface to append the
closing command of ENTER.
Action:
None. Although the buffer area is large, if more is needed, there is no way of increasing
the ASR data buffer area. This is a CA Endevor SCM CA Netman Interface restriction.
B1NM028E BC1PNM50
CCHGRUTN - CHANGE ID VALUE NOT RETURNED IN NETMAN API RESPONSE BUFFER.
Reason:
This error should not occur.
Action:
Allocate the trace data set and rerun the same condition that produced this error; then
contact CA Technical Support.
B1NM029E BC1PNM50
CTLGRUTN - BUFFER AREA NOT LARGE ENOUGH TO HOLD ASR DATA. TASK LOG NOT
CREATED.
Reason:
This error can only occur when you modify the module's task log record population
routine in BC1PNM60. This message indicates that insufficient room is left in the buffer
for the interface to append the closing command of ENTER. Although the buffer area is
large, if more is needed, there is no way of increasing the ASR data buffer area. This is a
CA Endevor SCM CA Netman Interface restriction.
B1NM Messages
B1NM030E BC1PNM50
CCLGRUTN - BUFFER AREA NOT LARGE ENOUGH TO HOLD ASR DATA. CHANGE LOG
NOT CREATED.
Reason:
This error can only occur when you modify the module's change log record population
routine in BC1PNM60. This message indicates that insufficient room is left in the buffer
for the interface to append the closing command of ENTER. Although the buffer area is
large, if more is needed, there is no way of increasing the ASR data buffer area. This is a
CA Endevor SCM CA Netman Interface restriction.
B1NM031E
FIND ON PACKAGE CHG RECORD FAILED DURING PACKAGE PROCESSING, RC=rc (HEX)
RE=re (HEX).
Reason:
Action:
B1NM032E
PACKAGE package ID FAILED VALIDATION - ACTION CANCELLED.
Reason:
The administrator turned on package validation and the CA Endevor SCM CA Netman
Interface package change record is not defined. All package functions apart from List
and Display functions are prohibited for this package until the package change record is
defined.
Action:
Contact your administrator.
B1NM Messages
B1NM033E
FIND ON PACKAGE CHG RECORD FAILED DURING AFTER PACKAGE PROCESSING, RC=rc
(HEX) RE=re (HEX).
Reason:
Action:
B1NM034E
CREATE OF PACKAGE LOG RECORD FAILED DURING FTER PACKAGE PROCESSING, RC=rc
(HEX) RE=re (HEX).
Reason:
Action:
B1NM035E
CREATE OF PACKAGE CHG RECORD FAILED DURING AFTER PACKAGE PROCESSING,
RC=rc (HEX) RE=re (HEX).
Reason:
Action:
B1NM036E
INVALID CCID VALUE ccid - ACTION CANCELLED. CANNOT EXCEED 8 CHARACTERS.
Reason:
Action cancelled. User specified a CCID value greater than eight characters. The
Interface restricts this field to no more than eight characters.
Action:
Specify the CCID value again. The value should not be more than eight characters.
B1TS Messages
B1NM037E
INVALID PACKAGE ID package-id - ACTION CANCELLED. CANNOT EXCEED 8
CHARACTERS.
Reason:
Package action cancelled. User specified a package ID value greater than eight
characters. The Interface restricts this field to no more than eight characters.
Action:
Respecify the package ID value. The value should not be more than eight characters.
B1TS Messages
B1TS messages are issued by initialization, if the option Global Type Sequencing is
enabled. This section details these messages along with possible causes and corrective
actions to take in error situations.
B1TS001S
ENDEVOR PARMLIB DATA SET NOT IN C1DEFLTS TABLE.
Reason:
The type sequence data set is specified in the C1DEFLTS table but the parmlib data set is
missing. The type sequence file must be a member of the Parmlib dataset.
Action:
Update the C1DEFLTS' PARMLIB= parameter with the correct data set name.
B1TS003S
TYPE SEQUENCE FILE ALLOCATION FAILED, RC= , (HEX)
Reason:
Allocation failure.
Action:
Check the C1DEFLTS' Parmlib and Typeseqmbr specification. Check the output for any
relevant error messages. If the problem cannot be resolved, contact CA Technical
Support.
B1TS Messages
B1TS004S
TYPE SEQUENCE FILE OPEN FAILURE ON DSN=data set name MBR= member name.
Reason:
Open failure.
Action:
Check the C1DEFLTS' Parmlib and Typeseqmbr name specification. Check output for any
relevant error messages. If the problem cannot be resolved, contact CA Technical
Support.
B1TS005S
MAXIMUM LRECL OF 80 FOR TYPE SEQ PARSER INPUT IS SUPPORTED
Reason:
This message is generated when you specify a LRECL value greater than 80 for the Type
Seq Parser Input.
Action:
Re-build the type sequence file with a LRECL of 80.
B1TS006S
SERIOUS ERROR OCCURRED WHILE PARSING ENDEVOR TYPE SEQ FILE
Reason:
See previous error message for the actual problem. The likely problem is invalid data
within the file.
Action:
Correct the erroneous type sequence statement within the type sequence file and
invoke CA Endevor SCM.
B1TS Messages
B1TS007S
STORAGE ALLOCATION ERROR DURING TYPE SEQ HEADER BUILD
Reason:
Memory problem.
Action:
Increase the region size of the job and invoke CA Endevor SCM. If the problem
continues, contact CA Technical Support.
B1TS008S
STORAGE ALLOCATION ERROR DURING TYPE SEQ DATA ENTRY BUILD
Reason:
Memory problem.
Action:
B1TS009S
STORAGE ALLOCATION ERROR ON TYPE SEQ MESSAGE QUEUE
Reason:
Memory problem.
Action:
B1TS010S
DUPLICATE TYPE SEQ STATEMENT FOUND: TYPE type name SYSTEM system name.
Reason:
User error. Only one type sequence statement can be specified with the same type and
system name.
Action:
Choose the correct statement by deleting the other duplicates and invoke CA Endevor
SCM.
B1TS Messages
B1TS011E
TYPE SEQUENCE TABLE HAS ERRORS ON DSN=dsnname MBR=mbrname.
Reason:
Errors have been detected with the named (dsn/member) TYPE SEQUENCE table.
Action:
Correct the errors so that TYPE SEQUENCE processing can be enabled.
B1TS012I
SCL PROCESSING IS NOW DISABLED. NOTIFY YOUR ENDEVOR ADMINISTRATOR.
Reason:
The named TYPE SEQUENCE table (dsn/member) in message B1TS010I is not usable, and
CA Endevor SCM disallows any action attempting to use TYPE SEQUENCING.
Action:
Notify your administrator that the named TYPE SEQUENCE table (dsn/member) in
message B1TS010I is unusable, and needs to be corrected.
BC1PSVCS Messages
BC1PSVCS Messages
BC1PSVCS is the SVCS program. This program is the SVC screen services module, which
manages the SVC and DESERV exit screening environments. It is called to activate,
terminate, setup, and tear down, the SVC and DESERV environments. In addition, it
establishes the tables required for DDNAME monitoring for the Automated
Configuration Manager (ACM). This section details these messages along with possible
causes and corrective actions to take in error situations.
BC1PSVCS: E010 ENDEVOR RACF ID INIT ERROR - nnnn/nnnn/nnnn
BC1PSVCS: E010 - XXXXXXXX
Reason:
A RACFROUT VERIFY request was issued for the CA Endevor SCM alternate ID and the
request failed. Following the text, three parameters are returned: the return code from
the RACFROUT request, the return code issued by the Security Authorization Facility
(SAF) interface, and the reason code issued by the Security Authorization Facility (SAF)
interface. The second part of message E010 displays the name of the one-to
eight-character alternate ID that is being verified. The alternate ID value is specified in
the C1DEFLTS table.
Action:
Check with your security administrator to ensure the alternate ID security access was
properly setup in your security product.
BTSQ Messages
BTSQ messages are issued by CA Endevor SCM when you use the Build Type Sequence
utility. This section details these messages along with possible causes and corrective
BTSQ001E
CIBMINIT FAILURE. CALL ENDEVOR TECHNICAL SUPPORT
Reason:
See previous error messages for actual error.
Action:
Contact CA Technical Support if you cannot resolve the problem.
BTSQ Messages
BTSQ002E
$IMR REQUEST FAILED. $IMR ERROR MESSAGE FOLLOWS
Action:
BTSQ003E
STORAGE FAILURE. CALL ENDEVOR TECHNICAL SUPPORT
Reason:
The allocated memory is insufficient.
Action:
Increase the region size of the job and then rerun the job. If problem still occurs, contact
CA Technical Support.
BTSQ004E
ACQUIRE ENTRY STORAGE FOR INTERNAL TBL FAILED, ERR: error text.
Reason:
Memory problem.
Action:
If the error text indicates lack of memory, increase the region size and re-run the job. If
it is not a memory problem, call CA Technical Support.
BTSQ005E
TEMP WORK FILE OPEN FOR OUTPUT FAILED
Reason:
An open error occurred against an internal temporary work file.
Action:
Check the job output for any relevant messages. If the problem cannot be resolved,
BTSQ Messages
BTSQ006E
WRITE TO TEMP FILE FAILED
Reason:
A write error occurred on an internal temporary work file.
Action:
BTSQ007E
CLOSE ON INTERNAL WORK FILE FAILED.
Reason:
An error occurred while closing the internal work file.
Action:
BTSQ008E
INTERNAL WORK FILE SORT FAILURE, RESULT= sort result
Reason:
Sort failure occurred on internal work file.
Action:
Check the sort result information and any other output sort related error messages. If
the problem cannot be resolved, contact CA Technical Support.
BTSQ009E
INTERNAL WORK FILE OPEN FAILURE
Reason:
An error occurred while opening the internal work file.
Action:
Check the job output for any relevant error messages. If the problem cannot be
resolved, contact CA Technical Support.
BTSQ Messages
BTSQ010E
STORAGE PROBLEM WHILE ALLOCATING TYPE SEQUENCE JOB BLOCK
Reason:
Memory problem.
Action:
Increase the job's region size and re-run the job. Contact CA Technical Support if the
problem continues.
BTSQ011E
OPEN OUTPUT ERROR ON TYPE SEQUENCE FILE
Reason:
An error occurred while opening the type sequence file for output.
Action:
BTSQ012E
READ ERROR ON INTERNAL WORK FILE
Reason:
A read error occurred on the temporary internal work file.
Action:
BTSQ013E
WRITE ERROR ON THE TYPE SEQUENCE FILE
Reason:
A write error occurred on the type sequence file.
Action:
C1A Messages
C1A Messages
This section details messages generated in the course of processing, along with possible
C1A0001E
ERROR BUILDING SVC99 TEXT UNITS, UNABLE TO MATCH DDB UNIT unit id.
Reason:
Either there was an internal error, or you have mixed CA Endevor SCM releases.
Action:
Verify that you have not inadvertently mixed CA Endevor SCM releases. Otherwise,
contact your administrator.
C1A0002E
ERROR FORMATTING SVC99 TEXT UNITS, DATA IS TOO LONG
Reason:
A value was specified for a JCL parameter that is too long.
Action:
Respecify the parameter. See message C1A0009E for details regarding the field in error.
C1A0003E
ERROR FORMATTING SVC99 TEXT UNITS, FIELD VALUE NOT FOUND IN CONVERSION
TABLES.
Reason:
There is an invalid JCL parameter specification.
Action:
C1A Messages
C1A0004E
ERROR FORMATTING SVC99 TEXT UNITS, INVALID NUMERIC DIGITS.
Reason:
There is an invalid JCL parameter specification. A numeric value was expected but was
not supplied.
Action:
C1A0008I
TEST OF DATA SET NAME TYPE: ALLOCATION TEST RC=<return code-reason code >
DDNAME= <ddname, if known>
Reason:
Action:
None.
C1A0009E
** NAME=field name, PRFLD=endevor field ID, KEYFLD=svc99 field ID, DATA=data
value **
Reason:
Informational message. This message is issued along with the previous messages to
provide detailed information. For processor allocation errors, the data parameter
provides an indication of the parameter in error, the location of the subparameter in the
processor, and allows you to verify that the syntax and specified value are valid.
Action:
None.
C1A Messages
C1A0010E
RC=return code - reason code ALLOCATION ERROR DDNAME=ddname
DSNAME=dsname
Reason:
A dynamic allocation error occurred for the named data set. Refer to the appropriate
IBM documentation for your operating system for a definition of the return and reason
codes. If DDname and DSname are blank; then the data set that failed to allocate is
C1SORTIO, which is dynamically allocated.
Action:
Correct the indicated condition and resubmit the request. If the problem continues,
contact the appropriate systems programming personnel. If the type definition has a
comparison length of more than 4000 characters: LRECL=LRECL+4000, BLKSIZE=new
LRECL+4.
C1A0011E
text associated with return/reason code identified in C1A0010E
Reason:
Action:
None.
C1A0011I
< message number > DATA SET < data set name > < error description>
Reason:
Informational message. This message pertains to the action described in C1A0008I.
Action:
None.
C1A Messages
C1A0012E
additional text associated with return/reason code identified in C1A0010E
Reason:
Action:
None.
C1A0012I
<text>
Reason:
Informational message. If present, this message provides additional information
pertaining to C1A0008I and C1A0011I that are displayed just prior to this message.
Action:
None.
C1A0013E
MAXIMUM NUMBER OF SIMULTANEOUS TEMPORARY DATA SETS EXCEEDED.
Reason:
This message is issued when more than 100 temporary data sets are allocated
simultaneously.
Action:
Modify the processor so that no more than 100 temporary data sets are allocated
simultaneously.
C1B Messages
C1B Messages
C1B0100I
HIGHEST ENDEVOR RC WAS return code
Reason:
Informational message. This message indicates the highest return code for an action.
Action:
None.
C1B0103I
PRINT MEMBER REQUEST - member name
Reason:
Informational message. This message indicates that a request was submitted to print
the member named in the message.
Action:
None.
C1B0104I
member name SUCCESSFULLY PRINTED
Reason:
Informational message. This message indicates that the member named in the message
was printed.
Action:
None.
C1B Messages
C1B0107E
DDNAME "BSTPDS" NOT FOUND
Reason:
The input library for the footprint utility program was not specified, or the DDNAME in
the JCL was misspelled.
Action:
Verify that the library was specified for the BSTPDS ddname.
C1B0108E
INVALID DATA SET SPECIFIED
Reason:
The input library specified for the footprint utility program was neither a partitioned CA
Panvalet nor a CA Librarian library.
Action:
Verify that the library specification is one of the above library types.
C1B0109E
NO MEMBERS WERE FOUND IN LIBRARY THAT MATCHED SELECTION CRITERIA:
dsname
Reason:
No members in the library allocated to the DDname BSTPDS matched the selection
criteria (the library may be empty).
Action:
Verify that the selection criteria is correct.
C1B0110E
RUN WILL TERMINATE ABNORMALLY
Reason:
Premature termination of the job step was caused by previously encountered errors.
Action:
Correct the errors and resubmit the job.
C1B Messages
C1B0111I
END OF JOB
Reason:
Informational message. This message is issued at termination of the footprint utility
program.
Action:
None.
C1B0112I
RECORDS WRITTEN TO OUTPUT FILE: number of records
Reason:
Informational message. Issued during normal termination of the footprint utility
program. The number of records written is the count of member/CSECT information
records written to the output file.
Action:
None.
C1B0113I
PARAMETERS SPECIFIED AS INPUT TO PROGRAM BC1PFOOT
Reason:
Informational message. This message precedes the list of input parameters to the
footprint utility program.
Action:
None.
C1B0114E
ERROR PROCESSING MEMBER member name. BC1PFOOT IS TERMINATING
Reason:
BC1PFOOT was unable to process the named member, and terminated.
Action:
Check any associated messages and take the appropriate corrective action.
C1B Messages
C1B0114W
THIS MEMBERS IDR DATA CANNOT BE READ. MEMBER IS SKIPPED
Reason:
Warning. CA Endevor SCM is unable to read the identification record associated with
this member in order to obtain footprint information. The member is skipped.
Action:
None.
C1B0200I
STATISTICS FOR LIBRARY = dsname
Reason:
Informational message. This message displays statistics associated with running the
logical delete utility during library cleanup. Prior to exiting CA Endevor SCM, any
elements deleted during source management are physically removed from the library at
CA Endevor SCM termination. This message appears only if the base and delta libraries
are partitioned data sets.
Action:
None.
C1B0201I
MEMBER ENTRIES DELETED = number of members
Reason:
This informational message indicates the number of members physically deleted by the
logical delete facility. This facility is an internal routine that cleans up base and delta
libraries when exiting CA Endevor SCM. Prior to exiting CA Endevor SCM, any elements
deleted during source management are physically removed from the library at CA
Endevor SCM termination. This message appears only if the base and delta libraries are
partitioned data sets.
Action:
None.
C1B Messages
C1B0202I
MEMBER ENTRIES KEPT = number of members
Reason:
Informational message. This message indicates the number of members not physically
deleted by the logical delete facility. This facility is an internal routine that cleans up
base and delta libraries when exiting CA Endevor SCM. Prior to exiting CA Endevor SCM,
any elements deleted during source management are physically removed from the
library at CA Endevor SCM termination. This message appears only if the base and delta
libraries are partitioned data sets.
Action:
None.
C1B0203I
DIRECTORY BLOCKS READ = number of blocks
Reason:
Informational message. This message indicates the number of directory blocks read by
the logical delete facility. This facility is an internal routine that cleans up base and delta
libraries when exiting CA Endevor SCM. Prior to exiting CA Endevor SCM, any elements
partitioned data sets.
Action:
None.
C1B0204I
DIRECTORY BLOCKS WRITTEN = number of blocks
Reason:
Informational message. This message indicates the number of directory blocks written
by the delete utility during library cleanup. Library cleanup occurs when exiting CA
Endevor SCM. Prior to exiting CA Endevor SCM, any elements deleted during source
management are physically removed from the library at CA Endevor SCM termination.
This message appears only if the base and delta libraries are partitioned data sets.
Action:
None.
C1B Messages
C1B0205C
WARNING - SEQUENCE ERROR DETECTED, SKIPPING DUPLICATE ENTRY FOR member
name
Reason:
This message indicates that a duplicate member name was found in the library when
the logical delete utility was internally invoked during library cleanup. Library cleanup
occurs when exiting CA Endevor SCM. Prior to exiting CA Endevor SCM, any elements
partitioned data sets. This error occurs if the base and delta libraries are physically
damaged (for example, disk crash, operating system problems) when exiting CA Endevor
SCM.
Action:
None. The next time you sign on to CA Endevor SCM, the library will be cleaned up.
C1B0206E
DIRECTORY HAS NO ENDING ENTRY
Reason:
Informational message. This message indicates that the library against which the logical
delete utility was running does not contain an ending directory entry. Library cleanup
occurs when exiting CA Endevor SCM. Prior to exiting CA Endevor SCM, any elements
partitioned data sets. This error occurs if the base and delta libraries are physically
SCM.
Action:
None. The next time you sign on to CA Endevor SCM, the library will be cleaned up. If
this error persists, the library must be restored and all updates must be re-applied.
C1B Messages
C1B0207E
UNRECOVERABLE IO ERROR READING DIRECTORY
Reason:
An I/O error occurred when attempting to read a member from a library against which
the logical delete utility was running. Library cleanup occurs when exiting CA Endevor
SCM. Prior to exiting CA Endevor SCM, any elements deleted during source
This message appears only if the base and delta libraries are partitioned data sets. This
error occurs if the base and delta libraries are physically damaged (for example, disk
crash, operating system problems) when exiting CA Endevor SCM.
Action:
this error persists, the library must be restored and all updates must be re-applied.
C1B0208E
UNRECOVERABLE IO ERROR WRITING DIRECTORY
Reason:
Informational message. This message indicates that the PDS directory was corrupted
when the logical delete utility was internally invoked during library cleanup. Library
cleanup occurs when exiting CA Endevor SCM. Prior to exiting CA Endevor SCM, any
elements deleted during source management are physically removed from the library at
CA Endevor SCM termination. This message appears only if the base and delta libraries
are partitioned data sets. This error occurs if the base and delta libraries are physically
SCM.
Action:
None. If the error appears the next time you exit CA Endevor SCM, you probably have a
corrupted partitioned data set. Restore the data set from a previous backup and retry
action.
C1B Messages
C1B0209I
LIBRARY PROCESSING COMPLETE, RETURN CODE=return code
Reason:
This is an informational message produced by the logical delete utility which was
internally invoked during library cleanup. Library cleanup occurs when exiting CA
Endevor SCM. Prior to exiting CA Endevor SCM, any elements deleted during source
Action:
None. If error appears the next time you exit CA Endevor SCM, you probably have a
corrupt partitioned data set. Restore the data set from a previous backup and retry
action.
C1B0210E
LIBRARY PROCESSING ABORTED, RETURN CODE=return code
Reason:
Informational message. This message indicates the failure of the CA Endevor SCM logical
delete utility during library cleanup. Library cleanup occurs when exiting CA Endevor
Action:
this error persists, the library was probably damaged or an internal error is occurring. If
you are unable to correct the problem or if the problem persists, contact your CA
Endevor SCM Administrator.
C1B Messages
C1B0211E
DATA SET IS NOT A PDS
Reason:
Action:
None. This problem should be corrected the next time you sign on to CA Endevor SCM.
C1B0212E
CANNOT DETERMINE DATA SET TYPE
Reason:
Action:
C1BM Messages
C1B0213E
UNABLE TO OPEN LIBRARY
Reason:
Informational message. Indicates the failure of the CA Endevor SCM logical delete utility
during library cleanup. Library cleanup occurs when exiting CA Endevor SCM. Prior to
exiting CA Endevor SCM, any elements deleted during source management are
physically removed from the library at CA Endevor SCM termination. This message
appears only if the base and delta libraries are partitioned data sets. This error occurs if
the base and delta libraries are physically damaged (for example, disk crash, operating
system problems) when exiting CA Endevor SCM.
Action:
C1BM Messages
This section details messages generated by the SCL parser in the course of processing,
C1BM4100:E002
MEMBER NAME NOT ALLOWED UNLESS FULL ELEMENT NAME IS SPECIFIED
Reason:
A member name was entered, but a name mask was used with the element name in the
"action ELEMENTS name" clause.
Action:
A fully qualified element name must be specified in the ELEMENTS clause of the action
statement. Correct the error and resubmit the job.
C1BM4100:E005
MEMBER NAME NOT ALLOWED IF WILDCARD IS used in ELEMENT NAME (I.E., "*")
Reason:
A member name was entered, but a name mask was used with the element name in the
ELEMENTS clause.
Action:
C1BM Messages
C1BM4100:E006
MEMBER NAME NOT ALLOWED IF THROUGH CLAUSE IS SPECIFIED
Reason:
Both a THROUGH clause and a member name were coded for the action; only one of
these selections is allowed.
Action:
Remove the THROUGH clause and code individual action statements for all elements
against which you wish to operate.
C1BM4100:E007
VERSION AND LEVEL MUST BE SPECIFIED TOGETHER OR NOT AT ALL
Reason:
The request contains one of the Version or Level keywords but is missing the required
second keyword.
Action:
Specify both the Version and Level in the request or do not specify either keyword.
C1BM4100:E008
ENVIRONMENT REQUIRED ON "FROM" CLAUSE FOR THIS ACTION
Reason:
FROM ENVIRONMENT information, which is required for this action, cannot be found in
the syntax.
Action:
Make sure that a FROM ENVIRONMENT clause is entered. The clause can be coded in
the SET FROM statement or specified in the FROM clause within the action.
C1BM Messages
C1BM4100:E009
SYSTEM REQUIRED ON "FROM" CLAUSE FOR THIS ACTION
Reason:
FROM SYSTEM information, which is required for this action, cannot be found in the
syntax.
Action:
Make sure that a FROM SYSTEM clause is entered. The clause can be coded in the SET
FROM statement or specified in the FROM clause within the action.
C1BM4100:E010
SUBSYSTEM REQUIRED ON "FROM" CLAUSE FOR THIS ACTION
Reason:
FROM SUBSYSTEM information, which is required for this action, cannot be found in the
syntax.
Action:
Make sure that a FROM SUBSYSTEM clause is entered. The clause can be coded in the
SET FROM statement or specified in the FROM clause within the action.
C1BM4100:E011
TYPE REQUIRED ON "FROM" CLAUSE FOR THIS ACTION
Reason:
FROM TYPE information, which is required for this action, cannot be found in the syntax.
Action:
Make sure that a FROM TYPE clause is entered. The clause can be coded in the SET
FROM statement or specified in the FROM clause within the action.
C1BM Messages
C1BM4100:E012
STAGE REQUIRED ON "FROM" CLAUSE FOR THIS ACTION
Reason:
FROM STAGE or FROM STAGE NUMBER is required for this action, but was not found in
the syntax.
Action:
Make sure that a FROM STAGE or FROM STAGE NUMBER clause is entered. The clause
can be coded in the SET FROM statement or specified in the FROM clause within the
action.
C1BM4100:E013
STAGE NUMBER ON FROM CLAUSE REQUIRED FOR THIS ACTION WHEN SOURCE IS
ARCHIVE
Reason:
The source location for this action is an archive file, but the source specification does
not include a stage number.
Action:
Specify a stage number in the source statement, and then resubmit the action request.
C1BM4100:E014
TARGET ELM NAME NOT ALLOWED IF WILDCARD IS USED IN SOURCE ELM NAME
Reason:
An element name was entered, but a name mask was used with the element name in
the ELEMENTS clause for the source of the action.
Action:
C1BM Messages
C1BM4100:E016
ENVIRONMENT REQUIRED ON "TO" CLAUSE FOR THIS ACTION
Reason:
TO ENVIRONMENT information, which is required for this action, was not found in the
syntax.
Action:
Make sure that a TO ENVIRONMENT clause is entered. The clause can be coded in the
SET TO statement or specified in the TO clause within the action.
C1BM4100:E017
SYSTEM REQUIRED ON "TO" CLAUSE FOR THIS ACTION
Reason:
TO SYSTEM information, which is required for this action, cannot be found in the syntax.
Action:
Make sure that a TO SYSTEM clause is entered. The clause can be coded in the SET TO
statement or specified in the TO clause within the action.
C1BM4100:E018
SUBSYSTEM REQUIRED ON "TO" CLAUSE FOR THIS ACTION
Reason:
TO SUBSYSTEM information, which is required for this action, cannot be found in the
syntax.
Action:
Make sure that a TO SUBSYSTEM clause is entered. The clause can be coded in the SET
TO statement or specified in the TO clause within the action.
C1BM Messages
C1BM4100:E019
TYPE REQUIRED ON "TO" CLAUSE FOR THIS ACTION
Reason:
TO TYPE information, which is required for this action, cannot be found in the syntax.
Action:
Make sure that a TO TYPE clause is entered. The clause can be coded in the SET TO
C1BM4100:E021
FILE REQUIRED ON "TO" CLAUSE FOR THIS ACTION
Reason:
TO FILE information, which is required for this action, cannot be found in the syntax.
Action:
Make sure that a TO FILE clause is entered. The clause can be coded in the SET TO
C1BM4100:E025
CONFLICT IN "SET " CLAUSE. AN ATTEMPT TO SET BOTH C1 LOCATION AND DSNAME
INVALID
Reason:
An attempt was made to code both CA Endevor SCM location information and DSNAME
location information. Entry of both types of information is invalid.
Action:
Code either CA Endevor SCM location data - environment, system, subsystem, type, and
stage (as required) - or a DSNAME, but not both. Resubmit the job.
C1BM Messages
C1BM4100:E026
CONFLICT IN "SET " CLAUSE. AN ATTEMPT TO SET BOTH FILE AND DSNAME INVALID
Reason:
An attempt was made to code both FILE location information and DSNAME location
information. Entry of both types of information is invalid.
Action:
Code either FILE or DSNAME data, but not both. Resubmit the job.
C1BM4100:E027
VALID RANGE FOR "SET STOPRC" COMMAND IS 4 THRU 16 SPECIFIED STOPRC IS
OUTSIDE RANGE.
Reason:
The specified STOPRC is not within the range indicated in the message.
Action:
Specify a STOPRC value of 4 through 16 and resubmit the job.
C1BM4100:E028
FROM CLAUSE IS REQUIRED FOR THIS ACTION
Reason:
The FROM clause is required for this action, but none was found in the syntax.
Action:
For a description of the syntax required for this action, see the appropriate section of
the SCL Reference Guide
C1BM4100:E029
LAST STATEMENT NOT TERMINATED WITH PERIOD - JOB WILL BE TERMINATED
Reason:
All SCL statements must be terminated with a period. The last statement in the input did
not contain a period.
Action:
Specify a period in the last statement and resubmit the job.
C1BM Messages
C1BM4100:E030
NO "SET ACTION" STATEMENT WAS SPECIFIED BUT &&ACTION. REQUEST WAS
ENCOUNTERED
Reason:
An "&&ACTION. ELEMENTS name" statement was encountered, but no SET ACTION
statement precedes. A SET ACTION statement must be coded prior to any &&ACTION.
ELEMENTS statements.
Action:
Specify a SET ACTION clause and resubmit the job. For information regarding the SET
ACTION and &&ACTION. clauses, see the appropriate section of the SCL Reference
Guide.
C1BM4100:E031
NO ACTION REQUESTS WERE GENERATED
Reason:
No valid action requests were found when the SCL was parsed.
Action:
Correct all syntax errors. Be sure that an action clause has been specified as input to the
SCL run.
C1BM4100:E032
INVALID DATE - DATE MUST BE SPECIFIED IN MM/DD/YY FORMAT
Reason:
An invalid date was entered. The date specified is either not in the correct format or is
outside the valid range of dates.
Action:
Enter a valid date and retry the action.
C1BM Messages
C1BM4100:E033
INVALID TIME - TIME MUST BE SPECIFIED IN HH:MM FORMAT
Reason:
An invalid time was entered. The time specified is either not in the correct format or is
outside the valid time range.
Action:
Specify a valid time and retry the action.
C1BM4100:E034
WILDCARD SPECIFICATION ON ELEMENT NAME IS NOT ALLOWED IF LEVEL SPECIFIED
Reason:
You cannot use both a name mask with the element name in the "action ELEMENTS
name" clause and code a level specification for the element. Only one of these entries is
allowed.
Action:
If you want to specify a particular level, each element must be explicitly identified (that
is, no name mask). Define an individual action statement for each element against
which you wish to operate. For additional information, see the appropriate section in
the SCL Reference Guide.
C1BM4100:E035
FROM DATE/TIME GREATER THAN THROUGH DATE/TIME IN WHERE CLAUSE
Reason:
You have specified a FROM date and time in a WHERE clause that is later than the
THROUGH date and time. This is not allowed.
Action:
Respecify the date and time information, and then resubmit.
C1BM Messages
C1BM4100:E036
SPECIFY EITHER STAGE ID OR STAGE NUMBER, BUT NOT BOTH
Reason:
Both a stage ID and a stage number were found in the syntax for either the FROM or TO
clause. Only one stage identifier is allowed.
Action:
Enter either the stage ID or stage number and resubmit the job.
C1BM4100:E037
STAGE NUMBER MUST BE EITHER 1 OR 2
Reason:
Stage number was specified but contained a value other than 1 or 2. Only 1 or 2 is
allowed for the STAGE NUMBER statement.
Action:
Specify either 1 or 2 in the STAGE NUMBER clause and resubmit the job.
C1BM4100:E037
STAGE MUST BE EXPLICIT WHEN COPYBACK OR NOSOURCE IS SPECIFIED
Reason:
The stage is missing from a Generate Copyback or Generate Nosource action.
Action:
Supply the stage on the Generate action and resubmit the job.
C1BM4100:E112
COPYBACK AND NOSOURCE ARE MUTALLY EXCLUSIVE, BOTH CANNOT BE ACTIVE
Reason:
Both options cannot be active at the same time.
Action:
Change the Generate action option to either Copyback or Nosource and then re-submit
the job.
C1BM Messages
C1BM4100:E113
NOSEARCH CANNOT BE USED WITH COPYBACK
Reason:
Generate Copyback implies Search. Nosearch is no longer a valid option with Generate
Copyback.
Action:
Remove the Nosearch option and re-submit the job.
C1BM4100:E039
ENVIRONMENT, SYSTEM, SUBSYSTEM, TYPE, AND STAGE NUMBER MUST ALL BE
SUPPLIED WHEN ANY ARE USED IN THE COMPONENT CLAUSE
Reason:
SCL requires that if one of the following fields is coded in the WHERE COMPONENTS
EQUAL clause, all fields (that is, all location information) must be specified:
environment, system, subsystem, type, stage number. You can use the name mask with
any or all of these fields.
Action:
Enter the required (missing) information and resubmit the job. For additional
information, see the appropriate section in the SCL Reference Guide.
C1BM4100:E040
BUILD WITH COMPONENTS REQUIRES WHERE COMPONENTS CLAUSE
Reason:
A BUILD WITH COMPONENTS clause was coded for the List action, but no WHERE
COMPONENTS EQUAL clause can be found. Use of the BUILD WITH COMPONENTS
clause requires entry of an associated WHERE COMPONENTS EQUAL clause.
Action:
Enter the required WHERE COMPONENTS EQUAL clause and resubmit the job.
C1BM Messages
C1BM4100:E041
WHERE TEXT IS MUTUALLY EXCLUSIVE WITH WHERE COMPONENTS
Reason:
Both a WHERE TEXT EQUALS clause and a WHERE COMPONENTS EQUAL clause was
specified for the List action, but only one of these clauses is allowed in the syntax.
Action:
Enter either a WHERE TEXT EQUALS clause or a WHERE COMPONENTS EQUAL clause
and resubmit the job.
C1BM4100:E042
WHERE GENERATE FAILED IS MUTUALLY EXCLUSIVE WITH WHERE COMPONENTS
Reason:
Both a WHERE GENERATE FAILED clause and a WHERE COMPONENTS EQUAL clause
were specified for the List action, but only one of these clauses is allowed in the syntax.
Action:
Enter either a WHERE GENERATE FAILED clause or a WHERE COMPONENTS EQUAL
clause and resubmit the job.
C1BM4100:E043
WILDCARD NOT ALLOWED IN "FROM" ENVIRONMENT NAME
Reason:
A name mask was used in the FROM ENVIRONMENT name clause, but a name mask is
not allowed with this particular field.
Action:
Enter a complete (fully qualified) environment name in the FROM clause and resubmit
the job.
C1BM Messages
C1BM4100:E044
INVALID NAME SPECIFIED - ALLOWABLE CHARACTERS ARE: @, #, $, A-Z, 0-9
Reason:
An invalid characters was coded in the name specified.
Action:
The only characters allowed when coding the name are: A-Z, 0-9, @, #, and $. Correct
the error and resubmit the job.
C1BM4100:E045
WILDCARD NOT ALLOWED IN "TO" ENVIRONMENT NAME
Reason:
A name mask was used in the TO ENVIRONMENT name clause, but a name mask is not
allowed with this particular field.
Action:
Enter a complete (fully qualified) environment name in the TO clause and resubmit the
job.
C1BM4100:E046
WILDCARDING NOT ALLOWED IN "TO" SYSTEM NAME
Reason:
A name mask was used in the TO SYSTEM name clause, but a name mask is not allowed
with this particular field.
Action:
Enter a complete (fully qualified) system name in the TO clause and resubmit the job.
C1BM Messages
C1BM4100:E047
WILDCARDING NOT ALLOWED IN "TO" SUBSYSTEM NAME
Reason:
A name mask was used in the TO SUBSYSTEM name clause, but a name mask is not
allowed with this particular field.
Action:
Enter a complete (fully qualified) subsystem name in the TO clause and resubmit the
job.
C1BM4100:E048
WILDCARDING NOT ALLOWED IN "TO" TYPE NAME
Reason:
A name mask was used in the TO TYPE name clause, but a name mask is not allowed
with this particular field.
Action:
Enter a complete (fully qualified) type name in the TO clause and resubmit the job.
C1BM4100:E049
FROM "ENDEVOR" NOT VALID FOR THIS ACTION
Reason:
The FROM clause specified contains CA Endevor SCM location information
(environment, system, subsystem, type, or stage), but these are not allowed for this
action.
Action:
Remove the CA Endevor SCM location information coded for the indicated action and
resubmit the job. For details about coding this action, see the appropriate section in the
SCL Reference Guide.
C1BM Messages
C1BM4100:E050
FROM ARCHIVE FILE NOT VALID FOR THIS ACTION
Reason:
A FROM FILE name ENVIRONMENT (or SYSTEM, SUBSYSTEM, TYPE, or STAGE) clause was
found for this action, indicating that input comes from an archive file created by the
Transfer or Archive actions. Archive file input is not supported for the action being
flagged (in error).
Action:
Do not specify both FILE information and CA Endevor SCM location information (that is,
environment, system, subsystem, type, and stage). For information about the required
and optional fields allowed for the indicated action, see the SCL Reference Guide.
Correct the error and resubmit the job.
C1BM4100:E051
CONFLICT IN "SET " CLAUSE. AN ATTEMPT TO SET BOTH ENDEVOR LOCATION AND
MEMBER NAME INVALID.
Reason:
The SET TO clause contains both CA Endevor SCM location information (that is,
environment, system, subsystem, type, and stage) and a member name. Entering both
specifications is not allowed.
Action:
Specify either CA Endevor SCM location information (that is, environment, system,
subsystem, type, and stage) or a member name, but not both. For additional coding
information, see the SCL Reference Guide. Correct the error and resubmit the job.
C1BM4100:E052
INVALID SITE VALUE SPECIFIED - ALLOWABLE CHARACTERS ARE: @, #, $, A-Z, 0-9
Reason:
An invalid character was coded in the site ID specified.
Action:
The only characters allowed when coding the site ID are: A-Z, 0-9, @, #, and $. Correct
C1BM Messages
C1BM4100:E053
INVALID ENVIRONMENT VALUE SPECIFIED - ALLOWABLE CHARACTERS ARE: @, #, $,
A-Z, 0-9
Reason:
An invalid character was coded in the environment name specified.
Action:
The only characters allowed when coding the environment name are: A-Z, 0-9, @, #,
and $. Correct the error and resubmit the job.
C1BM4100:E054
INVALID SYSTEM VALUE SPECIFIED - ALLOWABLE CHARACTERS ARE: @, #, $, A-Z, 0-9
Reason:
An invalid character was coded in the system name specified.
Action:
The only characters allowed when coding the system name are: A-Z, 0-9, @, #, and $.
C1BM4100:E055
INVALID SUBSYSTEM VALUE SPECIFIED - ALLOWABLE CHARACTERS ARE: @, #, $, A-Z,
0-9
Reason:
An invalid character was coded in the subsystem name specified.
Action:
The only characters allowed when coding the subsystem name are: A-Z, 0-9, @, #, and
$. Correct the error and resubmit the job.
C1BM Messages
C1BM4100:E056
INVALID TYPE VALUE SPECIFIED - ALLOWABLE CHARACTERS ARE: @, #, $, A-Z, 0-9
Reason:
An invalid character was coded in the type name specified.
Action:
The only characters allowed when coding the type name are: A-Z, 0-9, @, #, and $.
C1BM4100:E057
INVALID STAGE ID VALUE SPECIFIED - ALLOWABLE CHARACTERS ARE: @, #, $, A-Z, 0-9
Reason:
An invalid character was coded in the stage ID value specified.
Action:
The only characters allowed when coding the stage ID are: A-Z, 0-9, @, #, and $. Correct
C1BM4100:E058
THROUGH ELEMENT NAME IS NOT ALLOWED IF LEVEL IS SPECIFIED
Reason:
The THROUGH element name was specified but the LEVEL clause was also found. If
specifying the LEVEL clause, the THROUGH element clause is not allowed.
Action:
If you want to use the LEVEL clause, you must explicitly define each element. Remove
either the LEVEL clause or the THROUGH clause and resubmit the job.
C1BM Messages
C1BM4100:E060
TO ARCHIVE FILE NOT VALID FOR THIS ACTION
Reason:
A TO FILE named ENVIRONMENT (or SYSTEM, SUBSYSTEM, TYPE, or STAGE) clause was
found for this action, indicating that an archive file was specified as the TO location. An
archive file (or file created by the Transfer action) is not supported by the action
indicated.
Action:
Do not specify an archive file in the TO clause for this action. For information about the
coding requirements and options available for the action, see the SCL Reference Guide.
C1BM4100:E061
TO FILE (DDNAME) IS NOT VALID FOR THIS ACTION
Reason:
A TO FILE clause was found in the syntax, but is not supported for this action.
Action:
Do not specify a TO FILE clause for this action. For information about the coding
requirements and options available for the action, see the SCL Reference Guide. Correct
C1BM4100:E062
TO DSNAME IS NOT VALID FOR THIS ACTION
Reason:
A TO DSNAME clause was found in the syntax, but is not supported for this action.
Action:
Do not specify a TO DSNAME clause for this action. For information about the coding
requirements and options available for the action, see the SCL Reference Guide. Correct
C1BM Messages
C1BM4100:E063
TO "ENDEVOR" IS NOT VALID FOR THIS ACTION
Reason:
CA Endevor SCM location information (that is, environment, system, subsystem, type,
and stage) was coded in the TO clause, but this data is not supported for this action.
Action:
Do not specify CA Endevor SCM location information (that is, environment, system,
subsystem, type, and stage) in the TO clause for this action. For information about the
coding requirements and options available for the action, see the appropriate section in
the SCL Reference Guide. Correct the error and resubmit the job.
C1BM4100:E064
FROM FILE (DDNAME) IS NOT VALID FOR THIS ACTION
Reason:
A FROM FILE clause was found in the syntax, but is not supported for this action.
Action:
Do not specify a FROM FILE clause for this action. Refer to the appropriate section in the
SCL Reference Guide for information about the coding requirements and options
available for the action. Correct the error and resubmit the job.
C1BM4100:E065
FROM DSNAME IS NOT VALID FOR THIS ACTION
Reason:
A FROM DSNAME clause was found in the syntax, but is not supported for this action.
Action:
Do not specify a FROM DSNAME clause for this action. Refer to the appropriate section
in the SCL Reference Guide for information about the coding requirements and options
available for the action. Correct the error and resubmit the job.
C1BM Messages
C1BM4100:E066
ONLY 1 "*" ALLOWED IN THE ELEMENT NAME. MUST BE LAST CHARACTER OF FIELD.
Reason:
When using a name mask, one of the following situations occurred:
More than one asterisk was entered in the element name field
The asterisk was not the last character in the name
Action:
Enter only one asterisk when using a name mask with the element name. Be sure the
asterisk is the last character coded in the field.
C1BM4100:E067
WILDCARD SPECIFICATION ON ELEMENT NAME IS NOT ALLOWED IN PACKAGE
PROCESSING
Reason:
You specified an element using a wildcard when building a package. This is not valid
syntax.
Action:
Make the element specification specific.
C1BM4100:E068
THROUGH ELEMENT CLAUSE IS NOT ALLOWED IN PACKAGE PROCESSING
Reason:
You used a THROUGH ELEMENT clause when building a package. This is not a valid
syntax.
Action:
Respecify the request without the THROUGH ELEMENT clause.
C1BM Messages
C1BM4100:E069
FROM FILE (DDNAME) IS NOT ALLOWED IN PACKAGE PROCESSING
Reason:
You used a FROM FILE (DDNAME) clause when building a package. This is not valid
syntax.
Action:
Respecify the request without the FROM FILE (DDNAME) clause.
C1BM4100:E070
WILDCARD SPECIFICATION IS NOT ALLOWED FOR SOURCE ENVIRONMENT, SYSTEM,
SUBSYSTEM, TYPE, AND STAGE IN PACKAGE PROCESSING
Reason:
You used a wildcard to specify one or more of the parameters indicated in the message.
This is not valid syntax for package processing.
Action:
Respecify the request without wildcards.
C1BM4100:E071
TO FILE (DDNAME) IS NOT ALLOWED IN PACKAGE PROCESSING
Reason:
You used a TO FILE (DDNAME) clause when building a package. This is not valid syntax.
Action:
Respecify the request without the TO FILE (DDNAME) clause.
C1BM4100:E072
WILDCARD SPECIFICATION IS NOT ALLOWED FOR TARGET ENVIRONMENT, SYSTEM,
SUBSYSTEM, TYPE, AND STAGE IN PACKAGE PROCESSING
Reason:
You used a wildcard to specify one or more of the parameters indicated in the message.
This is not valid syntax for package processing.
Action:
Respecify the request without wildcards.
C1BM Messages
C1BM4100:E081
BYPASS DELETE PROCESSOR AND BYPASS ELEMENT DELETE ARE MUTUALLY EXCLUSIVE
Reason:
You specified both the BYPASS DELETE PROCESSOR and BYPASS ELEMENT DELETE
options on an action request. These options are mutually exclusive.
Action:
Respecify the request.
C1BM4100:E082
GLOBAL CLEAR FROM/TO STMT INCOMPLETE
Reason:
You specified a CLEAR FROM or CLEAR TO statement using incorrect syntax.
Action:
Correct the syntax.
C1BM4100:E083
SPECIFY EITHER SEARCH OR NOSEARCH, BUT NOT BOTH
Reason:
You specified both the SEARCH and NOSEARCH options on an action request. These
options are mutually exclusive.
Action:
Respecify the request.
C1BM4100:E084
CONFLICT - SPECIFY SIGNOUT TO, RETAIN SIGNOUT, OR SIGNIN
Reason:
You specified more than one of the options indicated in the message. These options are
mutually exclusive.
Action:
Respecify the action request using only one of these options.
C1BM Messages
C1BM4100:E085
ON GENERATE WITHOUT COPYBACK, OPTIONS SEARCH/NOSEARCH CANNOT BE USED
Reason:
You requested a Generate action and specified either SEARCH or NOSEARCH as an
option. Neither option can be specified with this action.
Action:
Respecify the request without a search option.
C1BM4100:E086
"SIGNIN", "RETAIN SIGNOUT", AND "SIGNOUT TO" ARE NOT VALID WHEN "TO" IS AN
ARCHIVE FILE
Reason:
You requested a Transfer action to an archive file, with one of the options indicated in
the message. These options cannot be used when the target of a transfer is an archive
file.
Action:
Respecify the request without these options.
C1BM4100:E087
CANNOT SPECIFY "SHOW TEXT" WITHOUT THE "WHERE TEXT" CLAUSE
Reason:
You specified a List action using the SHOW TEXT option, but did not included a WHERE
TEXT clause in the request.
Action:
Respecify the request to include a WHERE TEXT clause.
C1BM Messages
C1BM4100:E088
"WHERE COMPONENT" VALUE MUST BE LESS THAN ITS PARTNER "THROUGH" VALUE
Reason:
You specified a WHERE COMPONENT clause with an initial value that is higher than the
THROUGH value. This is invalid syntax.
Action:
Respecify the WHERE COMPONENT clause.
C1BM4100:E089
"ELEMENT" NAME MUST BE LESS THAN ITS "THROUGH" NAME
Reason:
You specified an ELEMENT clause with an initial value that is higher than the THROUGH
value. This is invalid syntax.
Action:
Respecify the ELEMENT clause.
C1BM4100:E090
INVALID MEMBER NAME SPECIFIED - ALLOWABLE CHARACTERS ARE: @, #, $, A-Z, 0-9
Reason:
You used invalid characters to specify a member name.
Action:
Respecify the name using the characters indicated in the message.
C1BM4100:E092
WILDCARD SPECIFICATION ON MEMBER NAME IS NOT ALLOWED
Reason:
You specified a member using wildcards. This is invalid syntax.
Action:
Respecify the member name without a wildcard.
C1BM Messages
C1BM4100:E093
THE "FROM MEMBER" CLAUSE IS NOT ALLOWED ON THIS ACTION
Reason:
The current action does not allow the FROM MEMBER clause. The parsing routine
generates a syntax error when it finds the FROM MEMBER clause.
Action:
Remove the FROM MEMBER clause from the action.
C1BM4100:E094
THE PROCESSOR GROUP CANNOT BE WILDCARDED
Reason:
The processor group cannot be a wildcarded name mask. It must be a fully qualified
name. The parsing routine generates a syntax error when it finds a wildcarded processor
group name.
Action:
Specify a fully qualified name on the OPTIONS PROCESSOR GROUP clause. Resubmit the
request.
C1BM4100: E095
THE PROCESSOR GROUP CANNOT BE BLANK
Reason:
The processor group option was specified, but the name of the processor group is blank.
Action:
Correct the SCL by adding the name of the processor group and reexecute the job.
C1BM4100: E096
THE LEVEL NUMBER IS NON-NUMERIC
Reason:
The WHERE component level clause was specified and the level number is missing or
non-numeric.
Action:
Correct the SCL statement and reexecute the job.
C1BML Messages
C1BM4100: E097
REGION STORAGE EXHAUSTED, EXECUTION TERMINATED
Reason:
An attempt to acquire storage to build the user request block failed.
Action:
Increase the size of the region parameter on the JOB card and reexecute the job.
C1BML Messages
This section details messages generated by the Load Utility in the course of processing,
C1BML01I
LOAD PROCESSING SUCCESSFULLY COMPLETED
Reason:
Informational message. This message appears in the CA Endevor SCM Load Execution
Log and indicates that the load procedure completed successfully.
Action:
None.
C1BML01E
LOAD PROCESSING FAILED, EXECUTION TERMINATED
Reason:
An error was found when parsing the input data or attempting to load or footprint
members. Processing was terminated.
Action:
Correct the problems related to parsing the input data, loading, or footprinting
members. See also the preceding messages.
C1BML Messages
C1BML10I
DATA ERRORS FOUND REQUEST = request no
Reason:
Data errors were found in the request designated in the message. This message is
followed by a second message indicating the exact problem.
Load execution is not attempted when data errors exist.
Action:
Correct the problem indicated by the message, and then resubmit.
C1BML10E
INVALID OPTION-LOAD REQUIRED-FOOTPRINT OPTNL
Reason:
An invalid action was specified in the syntax request. The only valid action is LOAD
MEMBER; this is a required clause. You can also request that the members be
footprinted, by using the optional FOOTPRINT clause.
Action:
Respecify the request, and then resubmit.
C1BML11E
INVALID STARTING MEMBER starting member name
Reason:
The (first) member requested contains invalid characters.
Action:
Check your data and enter the member name again.
C1BML12E
INVALID ENDING MEMBER through member name
Reason:
The THROUGH member name specified contains invalid characters.
Action:
Check your data and reenter the name.
C1BML Messages
C1BML13E
FROM DSNAME INVALID OR NOT SPECIFIED
Reason:
Either a FROM DSNAME contains invalid characters, or it was not specified in a SET
FROM DSNAME statement and it was not entered in the actual LOAD request.
Action:
Reenter a valid FROM DSNAME statement with this action.
C1BML14E
INVALID ENVIRONMENT env-name
Reason:
This environment name contains invalid characters.
Action:
C1BML15E
INVALID SYSTEM sys-name
Reason:
This system name contains invalid characters.
Action:
C1BML16E
INVALID SUBSYSTEM subsys-name
Reason:
This subsystem name contains invalid characters.
Action:
C1BML Messages
C1BML17E
INVALID TYPE type-name
Reason:
This type name contains invalid characters.
Action:
C1BML18E
PROCESSOR GROUP group-name DOES NOT EXIST
Reason:
This processor group does not exist in the environment specified in the LOAD request.
Action:
Check your data and enter an appropriate group name.
C1BML19E
ENVIRONMENT env-name DOES NOT EXIST
Reason:
This environment name does not exist in the C1DEFLTS Table.
Action:
Check your data and either add this name to the C1DEFLTS Table or change the
environment name.
C1BML20E
AUTHORIZATION FAILED FOR ENVIRONMENT env-name
Reason:
Either the security package at your installation or CA Endevor SCM authorization denied
access to this environment.
Action:
For more information about setting up both native security and external security
interfaces, see the Security Guide.
C1BML Messages
C1BML21E
SYSTEM sys-name DOES NOT EXIST
Reason:
This system does not exist in the environment specified in the LOAD request.
Action:
Check your data and enter an appropriate system name.
C1BML22E
SUBSYSTEM subsys-name DOES NOT EXIST
Reason:
This subsystem does not exist in the environment specified in the LOAD request.
Action:
Check your data and enter an appropriate subsystem name.
C1BML23E
TYPE type-name DOES NOT EXIST
Reason:
This type does not exist in the environment specified in the LOAD request.
Action:
Check your data and enter an appropriate type name.
C1BML24W
MEMBER member-name IS NOT FOUND IN DATA SET from-dsname - FLUSHING
REQUEST
Reason:
This member name cannot be found in the FROM data set specified in the LOAD
request.
Action:
Check to see where the member exists and reenter the member or the FROM data set,
as appropriate.
C1BML Messages
C1BML25E
VERIFICATION FAILED FOR data set-name
Reason:
The data set name specified in the LOAD request is not a valid data set type.
Action:
Specify a data set that is either a partitioned data set, a CA Librarian file, a CA Panvalet
file, or a sequential data set.
C1BML26E
ALLOCATION FAILED FOR data set-name
Reason:
The data set specified cannot be allocated by the LOAD utility.
Action:
For complete information about data set allocation, see the Installation Guide.
C1BML27E
DEALLOCATION FAILED FOR data set-name
Reason:
The data set specified in this message was allocated by the LOAD utility, but cannot be
deallocated successfully.
Action:
C1BML28E
FOOTPRINT DATA SET NAME NOT SPECIFIED
Reason:
A FOOTPRINT data set was not previously established by a SET FOOTPRINT statement,
nor was it entered in the actual LOAD request. If you enter the FOOTPRINT clause, you
must specify a data set name.
Action:
Specify a data set name, and then resubmit.
C1BML Messages
C1BML29E
FOOTPRINT DATA SET data set-name NOT CATALOGED
Reason:
The data set specified in the FOOTPRINT clause cannot be found in your system catalog.
Action:
Check your entry and code an appropriate data set name.
C1BML30E
STAGE stage-id DOES NOT EXIST
Reason:
The stage specified in the LOAD request was not defined in the environment specified
for the request.
Action:
Check your data and enter the appropriate stage ID.
C1BML32E
INVALID PROCESSOR GROUP procgrp-name
Reason:
This processor group name contains invalid characters.
Action:
Make sure you know the correct name and reenter the name.
C1BML40I
REQUEST ERROR TOTAL = nnnnnnnn
Reason:
Informational message. This message appears after each LOAD request in the Data
Report, and lists the total number of errors found in each request.
Action:
None.
C1BML Messages
C1BML41I
DATA REPORT FINAL TOTAL = nnnnnnnn
Reason:
Informational message. This message lists the total number of errors found in all LOAD
requests in the CA Endevor SCM Data Validation Report.
Action:
None.
C1BML42E
OPEN FAILED FOR DDNAME ddname
Reason:
An attempt to open the data set related to the specified DDname failed.
Action:
Refer to the appropriate IBM documentation for your operating system for a list of
applicable return codes and their meanings.
C1BML43I
FLUSHED REQUEST TOTAL = nnnnnnnn
Reason:
Informational message. When requests are flushed, the return code is 0004. This is a
warning that a request was ignored and processing continues.
Action:
None.
C1BML44E
STARTING MEMBER (member name) MUST BE LESS THAN THE ENDING MEMBER
(member name)
Reason:
Starting member location (PDS range) must be less than that of the end member.
Action:
Check input and change member specifications as necessary.
C1BML Messages
C1BML50I
LOAD REQUEST NUMBER request-number
Reason:
Informational message. This message indicates the beginning of the load execution
process for a particular LOAD request. The request number is automatically assigned by
the system for identification purposes only.
Action:
None.
C1BML51I
Text
Reason:
Action:
None.
C1BML52I
STARTING LOAD
Reason:
Informational message. This message indicates when load processing actually begins for
the LOAD request.
Action:
None.
C1BML53I
member-name LOADED
Reason:
Informational message. This message indicates that the member specified was loaded
successfully.
Action:
None.
C1BML Messages
C1BML54E
member-name LOAD FAILED - LOADING NEXT MEMBER
Reason:
The load process failed for the member specified and processing terminated for this
member. Processing continues for the remaining members (if any) in the request.
Action:
None.
C1BML55I
LOAD ENDED FOR REQUEST NUMBER request-number
Reason:
Informational message. This message indicates that the load process ended for this
particular LOAD request. For the return code for this request, see the CA Endevor SCM
Load Execution Summary report.
Action:
None.
C1BML56E
MEMBER member-name ALREADY LOADED-LOADING NEXT MEMBER
Reason:
The member shown was already loaded into the environment designated in the LOAD
request. Processing continues for the remaining members (if any), beginning with the
next member in the request.
Action:
None.
C1BML Messages
C1BML57I
FOOTPRINTING MEMBER member-name IN DATA SET data set-name
Reason:
Informational message. This message indicates that the member shown is currently
being footprinted in the data set specified.
Action:
None.
C1BML58I
MEMBER member-name FOOTPRINTED
Reason:
Informational message. This message indicates that the member shown was
footprinted successfully.
Action:
None.
C1BML59I
FOOTPRINTING FAILED FOR MEMBER member-name
Reason:
The footprint process failed for the member shown.
Action:
Review the accompanying messages to see why the member was not footprinted.
C1BML Messages
C1BML64I
LOAD REQUEST NUMBER request-number COMPLETE - RC=return code
Reason:
Informational message. This message indicates that processing completed for this
particular load request, with the return code shown.
Return codes are defined as follows:
0 = All members loaded successfully.
04 = A warning message was issued during footprinting. All members loaded and
footprinted successfully. You may need to relink at least one member to create
more HMASPZAP records for future ZAPs. If you relink, the module must be
reloaded and re-footprinted.
08 = This message appears in one of two situations. Either syntax errors were
found in the input data, preventing further processing, or a member specified for
footprinting was not found in the designated libraries.
12 = An error was encountered that terminated processing of a current load action.
Action:
None.
C1BML66I
TOTAL MEMBERS REQUESTED = nnnnnnnn
Reason:
Informational message. This message reflects the total number of members processed
for this load request.
Action:
None.
C1BML67I
MEMBERS LOADED = nnnnnnnn MEMBERS NOT LOADED = nnnnnnnn
Reason:
Informational message. This message shows, out of the total number of members
requested, the number of members loaded successfully and the number of members for
which the load failed.
Action:
None.
C1BML Messages
C1BML68I
FOOTPRINTS ATTEMPTED = nnnnnnnn FOOTPRINTS FAILED = nnnnnnnn
Reason:
Informational message. The LOAD utility attempts to footprint only those members
eligible for footprinting; that is, those members loaded successfully and for which a
FOOTPRINT clause or SET FOOTPRINT statement was coded. This message lists the total
number of members for which footprinting was attempted, as well as the number of
(eligible) members for which footprinting failed.
Action:
None.
C1BML69I
FATAL ERROR - TERMINATING LOAD
Reason:
Informational message. A return code of greater than 12 caused the job to terminate.
Action:
None.
C1BML70E
LOAD UTILITY TERMINATION FAILED DURING DEALLOCATION
Reason:
The load utility failed while deallocating either one of the footprint data sets or the
FROM data set.
Action:
C1BMX Messages
C1BMX Messages
The following messages are generated by the package shipment utility in the course of
processing. Possible causes and recommended corrective actions are described along
with each message.
C1BMX00I
END OF RUN - ENDEVOR RC return code
Reason:
Informational message. This message is written to the message log when package
shipment processing is about to terminate. It records the final return code for this run.
Action:
None.
C1BMX01I
INPUT VERIFICATION COMPLETED
Reason:
Informational message. This message is written to the message log when the input is
free of syntax errors and the destinations and packages exist. Both conditions must be
met in order to receive this message.
Action:
None.
C1BMX02W
INPUT VERIFICATION COMPLETED - WARNINGS ISSUED
Reason:
The verification process detected errors in the utility input that do not affect the
shipment of the requested packages.
Action:
Examine the Validation Report for warning messages ("W" as the last character in the
message number). Take the corrective action associated with any message.
C1BMX Messages
C1BMX03E
INPUT VERIFICATION FAILED - RC return code
Reason:
The verification process detected errors in the utility input that will cause processing to
terminate.
Action:
Examine the Validation Report for error messages ("E" or "S" as the last character in the
message number). Take the corrective action associated with the message.
C1BMX04I
PACKAGE STAGING COMPLETED
Reason:
Informational message. This message is written to the message log when the utility has
determined the content of the packages.
Action:
None.
C1BMX05W
PACKAGE STAGING COMPLETED - WARNINGS ISSUED
Reason:
The package staging process detected errors that do not affect the shipment of the
requested packages.
Action:
Examine the Message Log for warning messages ("W" as the last character in the
message number) that precede this message. Take the corrective action associated with
the warning message.
C1BMX Messages
C1BMX06E
PACKAGE STAGING FAILED - RC return code
Reason:
The package staging process detected errors in the utility input that caused processing
to terminate.
Action:
Examine the Message Log for error messages ("E" or "S" as the last character in the
the error message.
C1BMX07I
SHIPMENT STAGING COMPLETED
Reason:
Informational message. This message is written to the message log when the Package
Shipment Utility determines the following:
The packages being shipped to a given destination do not conflict with one another.
The package members do exist.
At this point, the host staging data sets and various control statement data sets are
built.
Action:
None.
C1BMX Messages
C1BMX08W
SHIPMENT STAGING COMPLETED - WARNINGS ISSUED
Reason:
This message is written to the message log when the utility determines that:
The packages being shipped to a given destination do not conflict with one another.
The package members do exist.
However, an error condition was detected that does not affect the transmission of the
requested packages. At this point, the host staging data sets and various control
statement data sets are built.
Action:
Examine the Message Log for warning messages ("W" as the last character in the
message number) that precede this message. Take the action associated with the
warning message. Examine the Activity Report for detail lines flagged with a warning
message.
C1BMX09E
SHIPMENT STAGING FAILED - RC return code
Reason:
The staging process for this shipment was terminated due to errors.
Action:
Examine the Message Log for error messages ("E" or "S" as the last character in the
the error message. Examine the Activity Report for detail lines flagged with an error
message.
C1BMX10S
VALIDATION OF THE EXECUTION PARM FAILED
Reason:
The execution parm passed to the staging utility or the confirmation utility was found to
be in error. This message is preceded by a message stating the cause of the error.
Action:
Take the corrective action for the message that precedes this one.
C1BMX Messages
C1BMX11S
PROGRAM program name ABENDED WITH CODE abend code
Reason:
The program named in the message has abended with either a system abend (abend
code = Snnn) or a user abend (abend code = Unnnn).
Action:
For information about user abends, see the corresponding sections in this guide. For
information about "S0Cx" system abends, obtain a dump and contact your
administrator. Other system abends typically represent set-up problems or internal
errors; if resolution of the problem is not obvious, obtain a dump and contact your
administrator.
C1BMX12E
PACKAGE ID WAS NEITHER SET NOR SPECIFIED
Reason:
A SHIP action did not contain the package name.
Action:
Specify the package name on the SHIP statement.
C1BMX13E
DESTINATION WAS NEITHER SET NOR SPECIFIED
Reason:
A SHIP request did not contain a DESTINATION, and a SET DESTINATION was not in
effect for that request.
Action:
Specify a destination on the SHIP request, or code a SET statement prior to the SHIP
statement, specifying a destination.
C1BMX Messages
C1BMX14E
PACKAGE "package name" DOES NOT EXIST
Reason:
The specified package name is not on file.
Action:
Correct the package name specified in the SHIP request.
C1BMX15E
DESTINATION destination id NOT FOUND IN package dataset name
Reason:
The specified destination is not on file.
Action:
Make sure that the correct package file is being accessed. Correct the destination or add
a new one using the Destination Definition panel.
C1BMX16E
PACKAGE "package name" WAS CAST WITH BACKOUT DISABLED
Reason:
When the requested package was cast, the ENABLE BACKOUT indicator was set to "NO."
Action:
Packages can be shipped only when backout records exist. This package cannot be
shipped because backout records are not created when ENABLE BACKOUT = NO.
C1BMX17E
PACKAGE "package name" HAS NOT BEEN EXECUTED
Reason:
The requested package was not executed.
Action:
An unexecuted package cannot be shipped. Either execute the package or delay
shipment until after its execution.
C1BMX Messages
C1BMX18E
PACKAGE "package name" HAS BEEN COMMITTED
Reason:
A COMMIT was issued for this package after its execution.
Action:
Packages can be shipped only when backout records exist. This package cannot be
shipped because backout records are deleted when a package is committed.
C1BMX19W
DUPLICATE PACKAGE "package id" TO DESTINATION destination id
Reason:
A package is being shipped twice in the same run.
Action:
None. The second request is ignored.
C1BMX20E
PACKAGE "package id" AND BACKOUT TO SAME DESTINATION destination id IS
INVALID
Reason:
Two SHIP actions for the same package were detected for the same destination. One of
the actions specified OPTION OUTPUTS and the other action specified OPTION
BACKOUT.
Action:
Choose one of the actions and delete the other.
C1BMX Messages
C1BMX21E
PACKAGE "package name" HAS NO BACKOUT RECORDS - CANNOT BE STAGED
Reason:
The package header record has indicators turned on, but there are no package backout
records. If the indicators are on, package backout records should be available.
Action:
This can indicate package file integrity problems or an internal error. Contact your
administrator.
C1BMX22S
ERROR IN FILE QUERY FOR PACKAGE "package name" - RC=return code
REASON=reason code
Reason:
An error other than "package not found" was returned by the package file query
routine.
Action:
Make sure that the package file still exists and is catalogued. Also, make sure that the
package file DSN is correctly coded in the C1DEFLTS table being used.
C1BMX23S
ERROR IN FILE QUERY FOR DESTINATION "destination name" - RC=return code
REASON=reason code
Reason:
An error other than "package not found" was returned by the package file query
routine.
Action:
Make sure that the package file still exists and is catalogued. Also, verify that the
package file DSN is correctly coded in the C1DEFLTS table being used.
C1BMX Messages
C1BMX24S
$BSTGLST ERROR - STGID=stage id - RC=return code - reason code
Reason:
An "out of storage" condition or an internal error has occurred.
Action:
If the reason code is "NOSTG", increase the amount of storage available to the region or
decrease the number of packages being shipped. If RC=0; then it possibly shipped in a
prior package. For other reason codes, contact your administrator.
C1BMX25E
PACKAGE "package name" DID NOT EXECUTE SUCCESSFULLY
Reason:
When the package was executed, the return code was greater than 8.
Action:
A package cannot be shipped if it does not execute successfully.
C1BMX26S
BACKOUT KEY record key HAS NO ID RECORD
Reason:
The link between a package backout record and its ID record cannot be established.
Action:
This message can indicate a package file integrity problem or an internal error. Contact
your administrator.
C1BMX27S
ddname DATASET FAILED TO OPEN
Reason:
The Package Shipment Utility's input data set (C1BMXIN) could not be opened.
Action:
Check for a missing C1BMXIN DD card.
C1BMX Messages
C1BMX28E
OUTPUT + BACKOUT OPTIONS ARE MUTUALLY EXCLUSIVE
Reason:
A single SHIP was coded with both OPTION OUTPUTS and OPTION BACKOUT.
Action:
Choose one option and delete the other.
C1BMX29E
NO SHIP REQUESTS WERE FOUND IN THE INPUT FILE
Reason:
There were no SHIP statements found in the input file.
Action:
Check for misspelled action code. Make sure that the input file contains at least one
SHIP request.
FINISHED
ACTIONS=number of actions ACTIONS IN ERROR=number of errors
SHIPMENTS=number of shipments
Reason:
Summarizes the results of a batch run.
Action:
If there are actions with errors, correct the errors, otherwise no action is required.
C1BMX Messages
C1BMX30E
$PKMR ERR request record type "package name" - RC=return code REASON=reason
code
Reason:
The Package File I/O routine passed back an unexpected return code for one of the
following requests: Extract ID, Extract Backout, Query Element Stub. The package name
and return/reason codes are displayed. For Query Element Stub, message C1BMX90I is
also displayed.
Action:
C1BMX31E
PACKAGE "package name" - BACKOUT SCL number HAS NO ID RECORDS
Reason:
The link between a package backout record and its ID record cannot be established.
Action:
This message can indicate a package file integrity problem or an internal error. Contact
your administrator.
C1BMX32S
PACKAGE "package name" HAS NO ID RECORDS
Reason:
The package header record has indicators turned on, but there are no ID records. If the
indicators are on, ID records should be available.
Action:
This message can indicate package file integrity problems or an internal error. Contact
your administrator.
C1BMX Messages
C1BMX33S
PACKAGE "package name" HAS NO BACKOUT RECORDS
Reason:
The package header record has indicators turned on, but there are no backout records.
If the indicators are on, backout records should be available.
Action:
your administrator.
C1BMX34E
MCF ERROR - PACKAGE "package name" - RC=return code REASON=reason code
Reason:
An unexpected return code was passed back by the Master Control File I/O routine
during a read operation for an element master record. This message is followed by
message C1BMX91I.
Action:
your administrator.
C1BMX Messages
C1BMX35E
RELATED PACKAGE "package name" error condition
Reason:
A related package is needed to process the shipment of the package named in the
preceding C1BMX91I message. When examining the related package, a condition was
found that prevents shipment of the package named in C1BMX91I. The possible error
conditions are as follows:
package name IS NOT ON FILE
package name HAS BEEN COMMITTED
package name HAS NOT BEEN EXECUTED
package name DID NOT EXECUTE SUCCESSFULLY
package name HAS BACKOUT DISABLED
package name HAS NO BACKOUT RECORDS
package name IS PREVENTING SHIPMENT
A related package is a package that supersedes, or is superseded by, the package being
requested. A superseding package is a package whose execution affects the members in
one or more other packages. Therefore, packages are considered related when at least
one member that participates in the requested package also participates in another
package.
Action:
The error condition "IS PREVENTING SHIPMENT" is an "undefined" error and should be
brought to the attention of your administrator.
The error condition "IS NOT ON FILE" may be due to the use of the Package Delete
Utility.
All error conditions will prevent the shipment of the package.
C1BMX36E
DATASET NOT CATALOGUED
Reason:
The DSN listed in the preceding message (C1BMX91I) is not cataloged.
Action:
Restore the data set.
C1BMX Messages
C1BMX37E
ALLOCATION ERROR (error code) SVC99 RC=return code - REASON=reason code
Reason:
The DSN listed in the preceding message (C1BMX91I) could not be dynamically
allocated. The message contains the SVC99 return code and reason code. If the
allocation error was a "data set not found" condition (code 1708), message C1BMX36E
displays.
Action:
For SVC99 return codes, see the appropriate IBM documentation.
C1BMX38S
"request" FAILED FOR data set name - RC=return code 1-return code 2 ERROR=error
code INFO=information code
Reason:
A dynamic allocation request failed for the named data set. The SVC 99 return code is
rc2, the error code field contains S99ERROR, and the information code contains
S99INFO.
Action:
For SVC99 return codes, see the appropriate IBM documentation.
C1BMX Messages
C1BMX39E
STAGING DATASET COPY ERROR - RC=return or abend code
Reason:
While attempting to copy members to a staging data set, the copy utility either abended
or encountered an abnormal situation.
Action:
To determine whether you have received a return code or an abend code, note the
following, and keep in mind that the return code is six hex characters:
If the RC shown is less than 000010, it represents a return code (see the SYSPRINT
data set for the reason).
If the RC shown is greater than 000010, and the first three characters are 000; then
the code reflects a user abend (see the CA Endevor SCM Messages and Codes
guide).
If the RC shown is greater than 000010, and the last three characters are 000; then
the code reflects a system abend. For 0Cx abends, obtain a dump and contact your
administrator. For other types of system abends, examine the JES log for further
information.
C1BMX40S
ERROR WRITING TO data set name - RC=return code
Reason:
CA Endevor SCM encountered an error writing to the named data set.
Action:
Check the JES log for a message related to the I/O error.
C1BMX41W
C1BMXRCN DATASET IS MISSING - THERE WILL BE NO REMOTE CONFIRMATIONS
Reason:
The C1BMXRCN data set is missing. This is the remote confirmation JCL data set. It is
distributed under the name C1BMXRCN as an ISPF skeleton and should be in the ISPSLIB
data set.
Action:
If remote confirmation is not desired, this message can be suppressed by creating a
C1BMXRCN skeleton containing a "//*".
C1BMX Messages
C1BMX42I
EXIT CANCELLED SHIPMENT OF "package id" TO destination
Reason:
Informational message. This message indicates that the user "before" exit for package
shipment cancelled this transaction.
Action:
None.
C1BMX43S
I/O ERROR READING C1BMXRCN - RC=return code
Reason:
The staging utility has encountered an I/O error reading the remote confirmation JCL
data set (DDNAME=C1BMXRCN).
Action:
Check the JES log for a message related to the I/O error.
C1BMX44E
DESTINATION destination id HAS NO JOB CARDS
Reason:
The destination named in the message has no associated job cards.
Action:
Provide job cards for the destination through the Destination Definition panel.
C1BMX Messages
C1BMX45E
INVALID DSN data set name DETECTED IN SHIPMENT TO destination
Reason:
A data set name mapping rule was applied to a host CA Endevor SCM output data set
and the resultant remote data set name was found to be invalid.
Action:
Examine the data set name for errors. Application of the rule may have caused the
generation of a data set name containing more than 44 characters or a qualifier
containing more than 9 characters. Correct the data set mapping rule or add a more
specific rule to handle this particular name.
C1BMX46I
DSN=data set name WILL NOT BE INCLUDED IN THE SHIPMENT OF PACKAGES TO
destination
Reason:
A data set name mapping rule was found to exclude the named data set from shipment
to named destination.
Action:
See the Packages Guide.
C1BMX48S
SYMBOLIC SUBSTITUTION ERROR FOR symbol - result
Reason:
An error was detected in defining a symbolic variable in a model control statement. The
result is a return code from the symbol resolution routine. This is an internal error.
Action:
Call your CA Endevor SCM Administrator.
C1BMX Messages
C1BMX49E
SYMBOL OVERFLOW - DDNAME=ddname - MEMBER=membername - LINE nn
TRUNCATED
Reason:
Truncation occurred during package ship model control statement symbol substitution.
Action:
Reformat the member (contained in the library associated with the DDNAME in the
message) so that symbol substitution does not result in data truncation.
C1BMX52S
member NOT FOUND - DDNAME=ddname
Reason:
The JCL used to build the remote IEBCOPY and IDCAMS job steps could not be found.
The named member will be C1BMXCOP (COPY) or C1BMXDEL (IDCAMS DELETE). These
members were provided as ISPSLIB skeletal members under those names.
Action:
Make sure that the named data set contains the members. See the Packages Guide.
C1BMX53S
ERROR - action MEMBER mbr-name - DDNAME ddname - RC=nnnn
Reason:
An error was detected while performing a FIND or READ action on the named model
transmission control card data set and member. The return code is in hex.
Action:
Consult the JES log for messages associated with the error.
C1BMX60I
CONFIRMATION PROCESSING COMPLETE
Reason:
The record of shipment has been marked "confirmed".
Action:
None.
C1BMX Messages
C1BMX61E
NO SHIPMENTS FOUND FOR ddmonyy hh:mm
Reason:
The confirmation utility was passed date and time that do not correspond to any
shipment date/time recorded for any destination.
Action:
Someone may have deleted the packages associated with this shipment before the
confirmation could be executed. Check the date and time specification and resubmit the
request.
C1BMX62E
NO SHIPMENTS FOUND FOR DESTINATION destination id ON ddmonyy hh:mm
Reason:
The confirmation utility was passed a date and time that do not correspond to any
shipment staging date/time for the named destination.
Action:
Someone may have deleted the packages associated with this shipment before the
confirmation could be executed. Check the date and time specification and resubmit the
request.
C1BMX63E
message text
Reason:
An error was encountered in trying to extract the confirmed record of shipment. The
text of this message will contain a "PKMRnnnn" message ID and text describing the
cause of the error.
Action:
Take the corrective action dictated by the "PKMRnnnn" message.
C1BMX Messages
C1BMX64S
message text
Reason:
An error was encountered in trying to replace the confirmed record of shipment. The
text of this message will contain a "PKMRnnnn" message ID and text describing the
cause of the error.
Action:
Take the corrective action dictated by the "PKMRnnnn" message.
C1BMX65E
MODEL MEMBER "member-name" (error) - 80 character card image
Reason:
When processing the named model member, the statement displayed as an 80
character card image was in error.
Action:
This message will be followed by message C1BMX66I for symbolic substitution errors or
C1BMX67E for all other errors. Refer to information contained in these messages.
C1BMX66I
SYMBOLICS AFTER SUBSTITUTION - 80 character card image
Reason:
The card image shown in the preceding C1BMX65I message is redisplayed after
symbolics have been substituted. Truncation has probably occurred.
Action:
If truncation has occurred, rearrange the model statement or break it up into two
statements.
C1BMX Messages
C1BMX67E
LEVEL number - EXPECTING clause; BUT FOUND clause
Reason:
A command error or sequence error has occurred in the model statement displayed in
the preceding C1BMX65I message. The level number shows the depth of nested
@INCLUDE statements. If the level number is *SYSTEM*, no @INCLUDE statements are
in effect. The "EXPECTING" clause tells what was expected and the "BUT FOUND" clause
tells what was found instead.
Action:
Correct the statement in error.
C1BMX68E
CONFIRMATION PROCESSING FAILED
Reason:
The confirmation utility could not mark the record of shipment "confirmed". This
message is preceded by a message stating the cause of the error.
Action:
Take the corrective action for the message that precedes this one.
C1BMX70I
{MODEL/ACTUAL} PARM: text
Reason:
For MODEL PARM the text is a legend describing the format of the parm. For ACTUAL
PARM the text is an image of the actual parm received by the staging utility
(C1BMX000).
Action:
None.
C1BMX Messages
C1BMX71E
REQUIRED PORTION OF THE EXECUTION PARM WAS OMITTED
Reason:
The required portion of the staging or confirmation parm includes the character string
"C1BMX000", the date, the time, and the function.
Action:
Correct the parm.
C1BMX72E
EXECUTION PARM IS TOO SHORT
Reason:
The parm passed to the staging utility or the confirmation utility did not contain all the
required parameters.
Action:
Correct the parm.
C1BMX73E
MISSING DELIMITER DETECTED AFTER THE field name PARM FIELD
Reason:
The parm passed to the staging utility or the confirmation utility consists of several
parameters separated by commas. A comma was found to be missing after one of the
following fields: "C1BMX000", DATE, TIME, FUNCTION, OPERATION, CONDITION,
CODE_VALUE, or DEST_ID.
Action:
Correct the parm.
C1BMX Messages
C1BMX74E
field name IS A REQUIRED PARM FIELD
Reason:
The parm passed to the confirmation utility did not contain all the required fields. One
of the following was missing: FUNCTION, USER ID, OPERATION, CONDITION,
CODE_VALUE, or DEST_ID.
Action:
Correct the parm.
C1BMX75E
EXECUTION PARM IS TOO LONG
Reason:
The parm passed to the staging utility or the confirmation utility contained superfluous
data.
Action:
Correct the parm.
C1BMX80E
date IS AN INVALID SHIPMENT DATE (YYYYMMDD)
Reason:
The parm passed to the staging utility or the confirmation utility contains an invalid
shipment date (second parameter in the parm).
Action:
Correct the date. If the message indicates that $CURR_DT is invalid; then the
C1BMXDTM DD statement is missing in one or more of the following ISPF skeletons:
C1BMXJOB, C1BMXHCN, C1BMXRCN. The format of the C1BMXDTM DD statement. can
be found in the skeleton examples found in the Packages Guide.
C1BMX Messages
C1BMX81E
time IS AN INVALID SHIPMENT TIME (HHMMSSHT)
Reason:
shipment time (third parameter in the parm).
Action:
Correct the time. If the message indicates that $CURR_TM is invalid; then the
C1BMXDTM DD statement is missing in one or more of the following ISPF skeletons:
C1BMXJOB, C1BMXHCN, C1BMXRCN. The format of the C1BMXDTM DD statement. can
be found in the skeleton examples found in the Packages Guide.
C1BMX82E
function IS AN INVALID FUNCTION (FUNC) - SHIP, COLL, OR CONF?
Reason:
function. Valid values are SHIP (to execute the shipment staging utility) or CONF (to
execute the shipment confirmation utility).
Action:
Correct the function CODE.
C1BMX84E
operation IS AN INVALID OPERATION (1ST VARIABLE DATA FIELD) - HX MT, RRCV,
RCPY, SP01, SP02
Reason:
The first variable data field (see preceding message C1BMX70I) passed as a parm to the
confirmation utility was incorrect. This is the operation field. Possible values are shown
in the message.
Action:
Correct the operation field.
C1BMX Messages
C1BMX85E
condition IS AN INVALID CONDITION (2ND VARIABLE DATA FIELD) - LT, LE, EQ, GE, GT,
EX, AB
Reason:
The second variable data field (see preceding message C1BMX70I) passed as a parm to
the confirmation utility was incorrect. This is the condition field. Possible values are
shown in the message.
Action:
Correct the condition field.
C1BMX86E
return code IS AN INVALID RETURN CODE (3RD VARIABLE DATA FIELD) - 0-4095
Reason:
The third variable data field (see preceding message C1BMX70I) passed as a parm to the
confirmation utility was incorrect. This is the return code field. Possible values are
Action:
Correct the return code.
C1BMX87W
return code CODED AS R.C. VALUE (3RD VARIABLE DATA FIELD) - IGNO RED FOR
CONDITON [AB/EX]
Reason:
The third variable data field (see preceding message C1BMX70I) passed as a parm to the
confirmation utility will be ignored when the condition (2nd variable data field) is "AB"
or "EX".
Action:
Code "****" to eliminate this warning.
C1BMX Messages
C1BMX90I
package name: (ENVIRONMENT: environment name SYSTEM system name
SUBSYSTEM subsystem name ELEMENT element name TYPE type name STAGE stage
id)
Reason:
Informational message. This multi-line message may follow messages C1BMX30E and
C1BMX34E.
Action:
Take the corrective action of the preceding message.
C1BMX91I
RE: PACKAGE "package name" - MEMBER member name - DSN data set name
Reason:
Informational message. This message precedes messages C1BMX35E, C1BMX36E, and
C1BMX37E.
Action:
Take the corrective action of the message that follows.
C1BMX91W
SUPERCEDING PKG "package name" - MBR member name - DSN data set name
Reason:
Warning message. This message indicates that a member of a package being shipped
has been superseded by another package.
Action:
Verify the status of this member.
C1BMX Messages
C1BMX92I
RELATED PACKAGE "package name" WAS PROCESSED SUCCESSFULLY
Reason:
Informational message. This message is preceded by message C1BMX91I and followed
by message C1BMX35E. The message specifies the last related package that was
successfully processed before an error condition was detected (as reported in message
C1BMX35E).
Action:
Take the corrective action for message C1BMX35E.
C1BMX93E
RELATED PACKAGE package name WAS REUSED OR EXTERNALLY CHANGED
Reason:
A package related to the one named in the preceding C1BMX91I message contains data
which indicates that it may have been re-used, deleted and re-added, or otherwise
changed. The package named in the preceding C1BMX91I message may be unshippable
or uncollectible.
Action:
None.
C1BMX97S
CANNOT RUN SHIP ON PACKAGE pkg-name, ELEMENT element/type IN USE AT LOC
environment/system/subsystem
Reason:
Ship fails. Element cannot be shipped. It is currently in use by another user.
Action:
Retry later.
C1BR Messages
C1BMX98I
group symbolic name WAS [NOT] CREATED - DDNAME=ddname [NOT FOUND]
Reason:
This informational message indicates whether or not one of the standard group
symbolics was created.
Action:
None.
C1BMX99I
TESTING DSNT OF TARGET. STAGING DS WILL USE DSNTYPE OF HOST,< data set name
of host library >
Reason:
Action:
None.
C1BR Messages
This section details messages generated by CA Endevor SCM reporting utilities in the
course of processing, along with possible causes and corrective actions to take in error
situations.
C1BR033E
UNLOAD ERROR ON [BASEDELTA] MEMBER FOR ELE: element name, ENV:
environment name, SYS: system name, SUBSYS: subsystem name, TYPE: type name,
STAGE: stage id
Reason:
An invalid base or delta record was encountered for the named element.
Action:
C1BR Messages
C1BR1000:E001
C1BMINIT FAILED (RCODE= X'xxxx') - PROCESSING TERMINATED
Reason:
Indicates that the report processing initialization logic encountered an error. This
message may or may not be preceded by one of the errors documented in this manual.
Action:
If another message does precede C1BR1000:E001, see the description of that message
for instruction to resolve the problem. Otherwise, contact your administrator.
C1BR1000:E002
COMMAND INPUT ANALYSIS FAILED (C1BR2000 RCODE = X'xxxx') - PROCESSING
TERMINATED
Reason:
Indicates that the report processing (command analysis phase) encountered an error.
Action:
Note that this message is preceded by another message, which is documented
elsewhere in this manual. See the description of that first error message for instruction
to resolve the problem.
C1BR1000:E003
DATA EXTRACTION FAILED (C1BR3000 RCODE = X'xxxx') - PROCESSING TERMINATED
Reason:
Indicates that the report processing (data extraction phase) encountered an error.
Action:
elsewhere in this chapter. See the description of that first error message for instruction
C1BR Messages
C1BR1000:E004
REPORT FORMATTING FAILED (C1BR4000 RCODE = X'xxxx') - PROCESSING
TERMINATED
Reason:
Indicates that the report processing (data formatting phase) encountered an error.
Action:
elsewhere in this chapter. See the description of that first error message for instruction
C1BR2000:E001
INVALID [REPORTEXTRACT] NUMBER: nnnnn
Reason:
You specified report or extract number nnnnn, which is not supported.
Action:
Be sure that the copy of CA Endevor SCM that you are running is the same as is
documented in the User Guide; correct the input and resubmit the job.
C1BR3000:E001
MCF DATA EXTRACTION FAILED (C1BR3010 RCODE = X'xxxx')
Reason:
Indicates that the data extraction phase of report processing encountered an error
while reading the Master Control File.
Action:
This message is preceded by another message, which is documented elsewhere in this
chapter. See the description of that first error message for instruction to resolve the
problem.
C1BR Messages
C1BR3000:E002
SMF DATA EXTRACTION FAILED (C1BR3020 RCODE = X'xxxx')
Reason:
while reading the BSTSMF data file.
Action:
problem.
C1BR3000:E003
FOOTPRINT DATA EXTRACTION FAILED (C1BR3030 RCODE = X'xxxx')
Reason:
while reading the BSTPDS data file.
Action:
problem.
C1BR3000:E004
PACKAGE DATA EXTRACTION FAILED (C1BR3060 RCODE = X'xxxx')
Reason:
while reading the package data set for the environment.
Action:
problem.
C1BR Messages
C1BR3000:E005
UNLOAD DATA EXTRACTION FAILED (C1BR3050 RCODE=X'xxxx')
Reason:
while reading the Master Control file (during unload) or the BSTUNLD file (during
reload).
Action:
problem.
C1BR3010:E001
$IMR REQUEST FAILED - MSGID=message id IMR MESSAGE FOLLOWS
Reason:
An unexpected status was received from an internal $IMR request, returning the
message ID shown in this message. The text of the $IMR message follows.
Action:
Correct the condition indicated in the $IMR message, and then resubmit your request.
C1BR3010:E002
Reason:
Action:
C1BR Messages
C1BR3010:E003
Reason:
Action:
C1BR3010:E004
Reason:
Action:
C1BR3010:E005
Reason:
Action:
C1BR3010:E006
Reason:
Action:
C1BR Messages
C1BR3010:E007
Reason:
Action:
C1BR3010:E008
Reason:
Action:
C1BR3010:E009
Reason:
Action:
Correct the condition indicated in the $IMR message, then resubmit your request.
C1BR3030:E001
UNABLE TO OPEN FOOTPRINT DDNAME ddname
Reason:
CA Endevor SCM was unable to open the extract data set from BC1PFOOT.
Action:
Make sure that the footprint DDname in the SCL is the same as the DDNAME
specification in the JCL.
C1BX Messages
C1BR3030: E002
THE FOOTPRINT DDNAME (ABOVE) MUST REFER TO A SEQUENTIAL DATASET
Reason:
CA Endevor SCM requires the footprint file to be a sequential data set.
Action:
Ensure that the DCB attributes refer to a sequential data set.
C1BX Messages
The following messages are generated by the package shipment utility in the course of
processing. Possible causes and recommended corrective actions are described along
with each message.
C1BX100I
RE: PACKAGE package id
Reason:
Informational message. This message identifies the package id being shipped. See other
message(s) associated with it.
Action:
None.
C1BX100W
SUPERCEDING PKG package id
Reason:
Warning message. This message indicates that a USS file of a package being shipped has
been superseded by another package. The USS path and file name follows this message.
Action:
Verify the status of this file.
C1BX Messages
C1BX101I
PATH WILL NOT BE INCLUDED IN THE SHIP OF PACKAGES TO destination-id
Reason:
The path name identified in the message prior to this message was found to be excluded
by the mapping rule for the shipment to the named destination.
Action:
See the Package Guide.
C1BX102E
INVALID PATH DETECTED IN THE SHIP TO destination-id
Reason:
A path name mapping rule was applied to a host CA Endevor SCM output path and the
resultant remote path name was found to be invalid. The path name is shown on the
message prior to this one.
Action
Examine the path name for errors. Correct the path mapping rule or add a more specific
rule to handle this particular name.
C1BX103E
HOST PATH FAILED VALIDATION IN SHIP TO destination-id
Reason:
The Path name listed in the message prior to this one did not pass validation. The host
path name may not exist. See prior errors for more detail.
Action:
See prior messages for more detailed information.
C1BX Messages
C1BX104S
ERROR WRITING TO STDPARM IN SHIP FOR DESTID destination-id..
Reason:
An error occurred when writing UNIX shell commands to the STDPARM DD statement
dataset during package shipment.
Action:
More information may be available prior to this message. If the problem cannot be
resolved contact CA technical support..
C1BX105E
PAX FAILURE DURING ARCHIVE OF HOST STAGING DIRECTORIES RC=return code.
Reason:
While attempting to create the PAX dataset for shipment of host USS staging files, the
BPXBATCH utility either abended or encountered an abnormal situation.
Action:
Check the STDERR data set for the reason. Also examine all prior messages and the JES
log for further information.
C1BX107S
SHIP NOT ALLOWED FOR PACKAGE package name ELEMENT element name/element
type LOC=Environment/System/Subsystem
C1BX107I
THE LAST PROCESSING OF THE ABOVE ELEMENT WAS NOT DONE IN A PACKAGE.
Reason:
The ship request was denied for the specified package, because the specified element
was last changed outside of package processing.
Action:
Create a new package relationship for the element through the Cast and Execute
actions.
C1C Messages
C1C Messages
C1C0001I
BEGINNING [CREATE/UPDATE] OF COMPONENT LIST AT STAGE stage name
Reason:
Informational message. This message appears in the Execution Report indicating that
the Component List was created or updated.
Action:
None.
C1C0003I
COMPONENT LIST INFORMATION DISCARDED DUE TO PROCESSOR FAILURE
Reason:
Informational message. This message is produced by the ACM facility. The message
indicates that a Component List was not created because the processor associated with
the element did not successfully complete its run. As a result, a new component level
was not created for this element. For example, if a COBOL program is added to CA
Endevor SCM and the program contains errors, no Component List (or component level)
is created.
Action:
Correct the source associated with the element being added to CA Endevor SCM and
generate the element.
C1C0004E
NO COMPONENT INFORMATION EXISTS FOR THIS ELEMENT
Reason:
The action requires element component information.
Action:
The user must have purchased and activated Endevor ACM. If ACM is active and you are
still getting this message, then the elements generate process did not produce
component data.
C1C Messages
C1C0004W
NO COMPONENT INFORMATION EXISTS FOR THIS ELEMENT
Reason:
The element does not have any associated component information.
Action:
None.
C1C0006E
AN INVALID FUNCTION CODE,"code", WAS PASSED TO C1GPCNFG
Reason:
Internal error.
Action:
C1C0007E
PROGRAM BC1PMVCL CAN ONLY BE INVOKED AS PART OF A MOVE PROCESSOR
Reason:
You tried to invoke program BC1PMVCL from a non-Move processor. This program can
only be invoked by a Move processor.
Action:
Eliminate the call to BC1PMVCL in the non-Move processor. If this message is produced
by a Move processor, contact your administrator.
C1E Messages
C1E Messages
C1E0001E
INSUFFICIENT STORAGE - REASON CODE return code
Reason:
CA Endevor SCM was unable to obtain sufficient working storage for the component
indicated by return code. Reason codes and their meanings are as follows:
04 - Base Deck
08 - Rebuild Element
12 - Cumulative Inserts
16 - Cumulative Deletes
20 - New Changes
24 - New Duplicate Statements
28 - Old Duplicate Statements
99 - Large Element
Action:
Resubmit the request, specifying a larger region size on the job statement. If the error
occurred during foreground processing, log on to TSO with a larger region size.
C1E0002E
STEP xxxxxxxx PARM= INVALID--VALUE LONGER THAN MAX ALLOWED (100 CHARS)
Reason:
The PARM= value in a processor step is greater than 100 characters in length. The
maximum is 100 characters.
Action:
Reduce the value of the PARM= parameter and resubmit the request.
C1E Messages
C1E0101E
STAGE stage name NOT DEFINED
Reason:
The request specified a CA Endevor SCM stage name which was not defined, or was
specified incorrectly.
Action:
Verify the stage name specification in the request. If necessary, contact your
administrator.
C1E0102E
userid NOT DEFINED AS A ENDEVOR USER
Reason:
The USERID or JOBNAME attempting the request was not defined to CA Endevor SCM. If
this message was generated in a background request, the JOBNAME corresponds to a
USERID that was not defined to CA Endevor SCM.
Action:
Contact your administrator to define the USERID or JOBNAME, or both.
C1E0103E
USER userid NOT AUTHORIZED FOR action OF environment/system/subsystem
Reason:
The USERID associated with the request is not authorized for the requested action for
the system, subsystem, or element specified in the request. Access to a system,
subsystem, or element is defined on the basis of USERID for one or more actions and
one or more systems and subsystems in the Environment. Native security - action
violation.
Action:
Verify that the system, subsystem, and element name were specified correctly in the
request. If necessary, contact your administrator to request access privileges.
C1E Messages
C1E0103I
USER userid NOT AUTHORIZED FOR function OF environment/system/subsystem
Reason:
Informational message. This user is not authorized to perform a function of
environment/system/subsystem.
Action:
None.
C1E0104E
USER NOT AUTHORIZED FOR ENVIRONMENT/SYSTEM/SUBSYSTEM/ELEMENT
Reason:
The user specified in the request is not authorized to access the specified element at the
specified location. Native security - resource violation.
Action:
Verify that the element name, system and subsystem were specified correctly in the
request. If necessary, contact your administrator to request access privileges.
C1E0104I
USER NOT AUTHORIZED FOR ENVIRONMENT/SYSTEM/SUBSYSTEM
Reason:
Informational message. This user is not authorized to access
environment/system/subsystem.
Action:
None.
C1E Messages
C1E0105E
A SECURITY VIOLATION HAS OCCURRED. ACTION DENIED.
Reason:
A security violation was detected. The user is not allowed to perform this action based
on the ESI security rules defined.
Action:
Verify all the information you specified is correct. If so, have your CA Endevor SCM or
security administrator view the security violation written to the security violation log to
determine the reason for the violation.
C1E0105I
A SECURITY VIOLATION HAS OCCURRED. ACTION DENIED.
Reason:
Informational message. Previous messages in the report contain detailed information
relating to the security violation.
Action:
None.
C1E0106E
environment NOT DEFINED IN CUSTOMER DEFAULTS TABLE OR THE USER NOT
AUTHORIZED TO USE THIS ENV.
Reason:
The environment name specified is not defined in the defaults table or users are
attempting to access an environment for which they are not authorized.
Action:
Contact your administrator, if required.
C1E Messages
C1E0107I
USER userid IS RESTRICTED FROM USE OF RESOURCE resource name
Reason:
Informational message. This user is not authorized to access this resource.
Action:
None.
C1E0108E
SYMBOLIC ERROR error code DETECTED IN DATA SET/PATH NAME
Reason:
Internal error. A problem occurred when CA Endevor SCM attempted to resolve a
symbolic parameter in the data set or path name.
Action:
C1E0109E
LIBRARY DSN ID data set id NOT DEFINED ON TYPE type name
Reason:
The data set named in the message was not defined on the type record named in the
message.
Action:
Define the data set on the type record.
C1E0110E
DATA SET DSORG dsorg UNSUPPORTED
Reason:
The data set [DSN] has an organization [DSORG] which is not supported by CA Endevor
SCM. Supported data set types are partitioned, sequential, CA Librarian, and CA
Panvalet. The requested action cannot be performed.
Action:
Make sure that the data set was correctly specified. If necessary, correct the request
and resubmit.
C1E Messages
C1E0111E
DATA SET RECFM format IS INCONSISTENT WITH THE ACTION REQUESTED
Reason:
The data set dsname has a record format that is not consistent with the action
requested.
Action:
and resubmit.
C1E0112E
ATTRIBUTES OF DATA SET ARE INVALID - UNABLE TO CONTINUE PROCESSING TYPE
type name
Reason:
A data set dsname associated with the processing of requests for element type name
has attributes which are not valid for this request. No further processing was attempted
for all elements remaining in the request data set member for type name.
Action:
and resubmit.
C1E0113E
TYPE type name NOT DEFINED FOR system AT STAGE stage name
Reason:
An action request specified an element type that was not defined for the named system
and stage.
Action:
Verify the element type definition for the requested system at both stages. Make sure
that the action requested specified the element type correctly. Resubmit the request if
necessary. If a type must be defined, or a type definition must be modified, contact your
administrator.
C1E Messages
C1E0114E
DDNAME ddname1 NOT COPIED TO ddname2 - INCOMPATIBLE RECORD FORMATS
(format1/format2)
Reason:
A step in the current processor which executes a copy procedure was not executed. The
source data set for the copy is identified by ddname1 (record format format1), and the
destination by ddname2 (record format format2). The Copy request was not be
executed because format1 and format2 were not compatible with each other.
Action:
Verify the attributes of both data sets, and make sure that both are correctly specified.
Contact your administrator to correct any data sets which may be incorrectly specified.
Resubmit the request after the data sets in question are corrected.
C1E0115E
ERROR DURING IMR FUNCTION CALL
Reason:
Internal error.
Action:
Check to make sure that the C1DEFLTS order matches the map order.
C1E0116E
RC=rrrr-nnnn ALLOCATION ERROR ddname-dsname
Reason:
A dynamic allocation error occurred for data set [DSN] whose return code is [RRRR] and
whose reason code is [NNNN in decimal). Refer to the appropriate IBM documentation
for your operating system for a definition of the return and reason codes.
Action:
Correct the condition indicated by the return and reason codes and resubmit the
request. If the problem continues, contact the appropriate systems programming
personnel.
C1E Messages
C1E0117E
MEMBER IS IN USE BY ANOTHER USER - RETRY ACTION LATER
Reason:
An attempt to perform an action against a member of a partitioned data set that is
currently in use by another user is not permitted until the other user finishes using the
member in question. It is also possible that the element is in use by you if you are in
split-screen mode.
Action:
Wait until the user finishes using the member you are attempting to perform an action
against, and then retry the action.
C1E0118E
UNABLE TO DEFINE STAGE DEFINITION IN DATA SET
Reason:
An improper stage definition was attempted against the VSAM data set name shown in
the message. The specified data set name may be improperly allocated.
Action:
Review steps required to define stages as described in the Administrator Guide.
C1E0119E
THE ATTRIBUTES OF THE ddname DATA SET ARE INVALID. UNABLE TO CONTINUE
WITH CONDELE PROCESSING
Reason:
The CONDELE utility cannot process data sets with the attributes of the named data set.
Action:
Adjust the attributes of the named data set then resubmit the action request.
C1E Messages
C1E0120E
DATA SET MAY BE PANV/LIBR. LIBRARY TYPE MUST BE DEFINED IN THE C1DEFLTS
TABLE
Reason:
CA Endevor SCM attempted to read from or write to a data set but was unsuccessful.
Action:
If the library accessed was a CA Panvalet or a CA Librarian library, the C1DEFLTS table is
not properly defined. Review steps required to define access to CA Panvalet or CA
Librarian as described in the Administrator Guide. If the C1DEFLTS table contains proper
definition for CA Panvalet or CA Librarian access, make sure that the correct C1DEFLTS
load module is accessed.
C1E0121I
IF NOT PANVALET OR LIBRARIAN, DSORG organization format IS UNSUPPORTED
Reason:
CA Endevor SCM attempted to read from or write to a data set but was unsuccessful.
This is a continuation of message C1E0120E.
Action:
If the library accessed was a CA Panvalet or a CA Librarian library, the C1DEFLTS table is
not properly defined. Review steps required to define access to CA Panvalet or CA
Librarian as described in the Administrator Guide. If the C1DEFLTS table contains proper
definition for CA Panvalet or CA Librarian access, make sure that the correct C1DEFLTS
load module is accessed.
C1E0122E
DSORG "organization code" IS INVALID FOR library type LIBRARY
Reason:
The named DSORG is invalid for the named data set.
Action:
Reallocate the data set with the correct data set organization.
C1E Messages
C1E0123E
RECFM=U IS NOT SUPPORTED
Reason:
The U record format is not supported for the named data set.
Action:
Reallocate the data set with another record format.
C1E0124E
PROCESSOR GROUP processor group name WAS NOT FOUND FOR TYPE type name AT
SYSTEM system name, STAGE stage name
Reason:
The processor group specified for the action was not located.
Action:
Specify a valid processor group name, and then resubmit the request.
C1E0125E
THE processor name PROCESSOR FOR GROUP group name FOR TYPE type name
CANNOT BE EXECUTED IN F/G MODE
Reason:
"No" was specified for the foreground execution option on the processor group.
Action:
Contact your administrator to determine why this processor cannot run in foreground,
or rerun the action in batch.
C1E0126I
WAITING FOR MEMBER WHICH IS IN USE BY ANOTHER USER
Reason:
You are attempting to access a member that is currently in use by another user. CA
Endevor SCM will attempt to access this member several times, and then fail if the
member is still in use.
Action:
None. If the job fails, try again later.
C1EI Message Codes
C1E0127E
RETRIEVAL TO AN ELIB FILE IS NOT ALLOWED
Reason:
The retrieve action is not compatible with ELIB files.
Action:
Correct the data set specification in the request and resubmit the request.
C1EI Message Codes

C1EI messages are issued by CA Endevor SCM. When describing corrective actions, the
messages use the following codes:
A
A indicates that action should be tried again, after increasing the region size. If this
does not work, proceed according to the other suggestions for corrective action.
B
B indicates that the full message text and return codes should be provided.
C
C indicates that either a SYSM or SYSABEND dump should be provided.
D
D indicates that the concatenation for the PIDT table should be provided.
E
E indicates that data set attributes should be provided.
F
F indicates the JES job log and all output listings should be provided.
G
G indicates that the script used as input should be sent to the batch utility.
C1EI Message Codes
C1EI Messages
This section details messages generated by CA Endevor SCM in the course of processing,
C1EI001E
module name INTERNAL ERROR - STORAGE UNAVAILABLE
Reason:
Storage request by the named module failed.
Action:
Perform the tasks indicated by A and C return codes; then contact your administrator.
C1EI002E
OPEN FAILED ON DDNAME NDVRIN
Reason:
Internal error.
Action:
Perform the tasks indicated by B, E, and F return codes; then contact your administrator.
C1EI003E
OPEN FAILED ON DDNAME NDVRPIDT
Reason:
Internal error.
Action:
C1EI Message Codes
C1EI005E
PREMATURE END OF FILE ON NDVRIN
Reason:
The script used as input to the batch utility contained a previous error that prevents the
program from recognizing the ETABLE statement.
Action:
Check the syntax, and then resubmit.
C1EI008E
READ ERROR OCCURRED ON NDVRIN, RC return code (HEX)
Reason:
Internal error.
Action:
C1EI019E
READ ERROR OCCURRED ON NDVRPIDT, RC return code (HEX)
Reason:
Internal error.
Action:
C1EI023E
INTERNAL ERROR WITHIN C1BMEI30 AT XTBLRUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI Message Codes
C1EI028E
INTERNAL ERROR WITHIN C1BMEI30 AT USERUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI073E
INTERNAL ERROR WITHIN C1BMEI30 AT LABLRUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI076E
INTERNAL ERROR WITHIN C1BMEI30 AT TSPRUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI087E
INTERNAL ERROR WITHIN C1BMEI30 AT RCRUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI Message Codes
C1EI088E
INTERNAL ERROR WITHIN C1BMEI30 AT USERUTN - CBUSE CHAIN IS CORRUPTED
Reason:
Internal error, probably in the script used as input to the batch utility.
Action:
Obtain the script, and then contact your administrator.
C1EI094E
INTERNAL ERROR WITHIN C1BMEI30 AT VMSGRUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI098E
INTERNAL ERROR WITHIN C1BMEI30 AT CRITRUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI119E
INTERNAL ERROR WITHIN C1BMEI30 AT IFRUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI Message Codes
C1EI120E
INTERNAL ERROR WITHIN C1BMEI30 AT POPRUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI124E
program name-routine name INTERNAL ERROR - CBUSE SHOULD HAVE BEEN BUILT
Reason:
Internal error, probably in the script used as input to the batch utility. This error
frequently occurs when the utility tries to populate a field with freeform text.
Action:
First break the field statement into several smaller statements, and then retry the job. If
this doesn&rq.t work, obtain the script, and then contact your administrator.
C1EI131E
INTERNAL ERROR WITHIN C1BMEI30 AT PATHRUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI140E
INTERNAL ERROR WITHIN C1BMEI30 AT SL04RUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI Message Codes
C1EI141E
INTERNAL ERROR WITHIN C1BMEI30 AT SL03RUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI142E
OPEN FAILED ON DDNAME NDVRWK1
Reason:
Internal error.
Action:
C1EI143E
WRITE ERROR OCCURRED ON NDVRWK1, RC return code (HEX)
Reason:
Internal error.
Action:
C1EI144E
C1BMEI40: NO CHAINED LABEL SEGMENTS
Reason:
Internal error.
Action:
Perform the tasks indicated by F and G return codes; then contact your administrator.
C1EI Message Codes
C1EI145E
C1BMEI40: FIRST ENTRY ON GACLABEL CHAIN WAS NOT A LABEL SEGMENT
Reason:
Internal error.
Action:
Perform the tasks indicated by F and G return codes; then contact your administrator.
C1EI146E
C1BMEI40: CONDITIONAL BRANCH LABEL label name WAS NOT CHAINED
Reason:
Action:
Perform the tasks indicated by F and G return codes; then obtain the script and contact
your administrator.
C1EI147E
C1BMEI40: UNKNOWN CHAINED STRUCTURE TYPE
Reason:
Action:
your administrator.
C1EI148E
C1BMEI40: INTERNAL ERROR, NO ENTRIES ON CBUSE CHAIN
Reason:
Action:
your administrator.
C1EI Message Codes
C1EI149E
INTERNAL ERROR WITHIN C1BMEI40 AT CUSERUTN - INSUFFICIENT STORAGE
Reason:
Internal error.
Action:
C1EI150E
CLOSE FAILED ON DDNAME NDVRWK1 IN C1BMEI50
Reason:
Internal error.
Action:
Perform the tasks indicated by B, E, and F return codes; then contact your CA Endevor
SCM Administrator.
C1EI151E
OPEN FOR INPUT FAILED ON DDNAME NDVRWK1 IN C1BMEI50
Reason:
Internal error.
Action:
C1EI152E
OPEN FOR OUTPUT FAILED ON DDNAME NDVRWK2 IN C1BMEI50
Reason:
Internal error.
Action:
C1EI Message Codes
C1EI153E
C1BMEI50: INTERNAL ERROR, NO ENTRIES ON USE SEGMENT CHAIN
Reason:
Action:
your administrator.
C1EI154E
WRITE FAILED ON DDNAME NDVRWK2 IN C1BMEI50 AT routine name
Reason:
Internal error.
Action:
C1EI155E
READ ERROR OCCURRED ON NDVRWK1, IN C1BMEI50, RC=return code (HEX)
Reason:
Internal error.
Action:
C1EI156E
CLOSE FAILED ON DDNAME NDVRWK2 IN C1BMEI50
Reason:
Internal error.
Action:
C1F Messages
C1EI157E
C1BMEI50: INTERNAL ERROR - LINK EDIT OF E-INFO FAILED, RC=return code (HEX)
Reason:
Internal error.
Action:
Provide the JES job log and all output listings, then contact your administrator.
C1F Messages
This section lists error messages issued during processing along with possible causes and
corrective actions to take.
C1F0001E
LOAD FAILURE ON PREVIOUS COMMAND
Reason:
CA Endevor SCM was unable to load the program passed to BC1PTMP0 for execution. A
reason code of 7 is returned by BC1PTMP0
Action:
Resubmit the request, specifying the necessary LOAD library in the STEPLIB statement.
C1G Messages
This section lists error messages issued during processing along with possible causes and
corrective actions to take.
C1G0000I
Reason:
Generic message used to display the type of object (DATA SET, ELEMENT, FILE,
MEMBER, PATH) followed by the name of the object. For long path and file names, this
may span multiple lines.
Action:
None.
C1G Messages
C1G0001E
UNABLE TO ALLOCATE PROCESSOR LOAD LIBRARIES FOR SYSTEM system name
Reason:
CA Endevor SCM encountered an allocation error while attempting to allocate the
processor load libraries defined for the system identified in the message.
Action:
This message is issued along with an allocation error message. Refer to that message to
resolve the problem.
C1G0002E
ERROR OBTAINING MASTER FILE DEFINITION FOR SYSTEM system name,
ENVIRONMENT environment name
Reason:
An error occurred when attempting to read the system definition for the system
identified in the message.
Action:
Make sure the system was properly defined at both Stage 1 and Stage 2.
C1G0003E
OPEN ERR error ddname/dsname1/dsname2
Reason:
An OPEN error occurred while attempting to open the DDname (allocated to the
system-defined processor load libraries) in the message.
Action:
C1G Messages
C1G0004E
OPEN ERR - ddname/dsname1/dsname2
Reason:
Internal error.
Action:
Reexecute the request. If the error occurs again, contact CA Technical Support.
C1G0005S
PROC processor - FND - ddname/dsname1/dsname2
Reason:
The processor identified in the message does not exist in either of the processor load
libraries defined for the system.
Action:
Make sure that the processor successfully generated and that the system definition
does refer to the correct processor load libraries.
C1G0006I
SYMBOLIC SUBSTITUTION:
Reason:
This is an informational message. It is issued along with message C1G0007I to identify all
occurrences of processor symbolic substitution.
Action:
None.
C1G0007I
SYMBOLIC symbolic [DEFINED/OVERRIDDEN] BY [PROCESSOR/GROUP]: symbolic value
Reason:
Informational message. This message is issued when a processor is loaded for execution.
The value of the symbolic may originate from either the default defined in the processor
or from a processor group override.
Action:
None.
C1G Messages
C1G0008E
NO INPUT/TARGET LIBRARY SPECIFIED FOR TYPE element type - UNABLE TO PERFORM
action REQUEST
Reason:
An Add, Update or Retrieve request was submitted for one or more elements associated
with the type named in the message, but no user data set was indicated as the location
for the input (Add or Update) or output (Retrieve) member.
Action:
Resubmit the request, specifying a user data set name for each element type that has an
Add, Update or Retrieve action in the request data set.
C1G0009I
[ORIGINAL/SUBSTITUTED]: JCL statement information
Reason:
Informational message. It is issued as symbolic parameters are substituted during
processor execution. The message is issued twiceonce with the original JCL statement
information and once with the substituted symbolic data.
Action:
None.
C1G0010E
INVALID OR MISSING FOOTPRINT FOR PROCESSOR LOAD MODULE member name.
Reason:
A processor was loaded that either contained an invalid footprint or no footprint at all.
Action:
Regenerate the processor.
C1G Messages
C1G0011I
PROCESSOR SYMBOLIC SUBSTITUTION OCCURRED Reason:
Informational message. This message is issued when symbolic substitution occurs during
processor execution.
Action:
None.
C1G0012W
A PROCESSOR GROUP NAME CHANGE OCCURRED. EXECUTING THE DELETE
PROCESSOR FROM GROUP processor-group-name.
Reason:
A processor group switch occurred as a result of the specification of the option PROC
GROUP group name on an action. The delete processor of the original processor group is
executed prior to executing the generate processor defined in the new processor group,
because they may not contain the same output libraries.
Action:
None.
C1G0013E
THE ELEMENT IS NOT FOUND AT STAGE stage id
Reason:
The element is not found at the stage referenced in the message. The requested action
cannot be executed.
Action:
Verify the location and the name of the element specified in the request, correct, and
resubmit.
C1G Messages
C1G0014E
DATA SET/FILE NOT FOUND
Reason:
The member name in a user data set dsname was not found.
Action:
Verify the request, ensuring that the element name was correctly specified. If an Add or
Update was requested and the TO/FROM option used, check that the TO/FROM
member name was specified correctly. Resubmit the request.
C1G0015E
ATTEMPT TO COMMUNICATE BETWEEN TASKS HAS FAILED WITH CODE=return
code-reason code
Reason:
Internal error.
Action:
C1G0016E
NEW VERSION OPTION IS NOT ALLOWED, THE ELEMENT EXISTS AT TARGET LOCATION
Reason:
You attempted to add the element using the new version. CA Endevor SCM rejected the
request because it does not permit you to reversion existing elements.
Action:
Correct the request and resubmit.
C1G0017E
THE SELECTED ELEMENT IS CURRENTLY IN USE BY ANOTHER JOB OR USER. PLEASE TRY
AGAIN
Reason:
An action was requested for an element that another user is currently modifying.
Action:
Retry the action at a later time.
C1G Messages
C1G0018E
THE SELECTED ELEMENT IS UNAVAILABLE, SYSTEM MAINTENANCE IS IN PROGRESS
Reason:
An action was requested for an element that belongs to a system that is currently
undergoing maintenance (for example, UNLOAD processing).
Action:
Retry the action at a later time.
C1G0019E
UNABLE TO IDENTIFY THE TARGET INVENTORY LOCATION FOR THE MOVE ACTION.
SYS: system name SBS: subsystem name TYPE: type name STG: stage id
Reason:
The FROM location for the requested Move action is not mapped to a target location in
the C1DEFLTS table. The requested FROM location is indicated in the second part of this
message.
Action:
Correct the FROM location specification, or contact CA Technical Support.
C1G0019I
THE MOVE "FROM" LOCATION IS ENV: environment, SYS: system, SBS: subsystem,
TYPE: type, STAGE ID: stage id
Reason:
Informational message. The MOVE action from location displays.
Action:
None.
C1G Messages
C1G0020E
UNABLE TO MOVE PROCESSOR processor name TO ANOTHER ENVIRONMENT
Reason:
You attempted to move a processor to an environment other than the one in which it
was created.
Action:
Respecify the Move request.
C1G0021E
INVALID FUNCTION REQUEST FOR BC1PACTN
Reason:
Internal error.
Action:
C1G0022E
ACTION REQUIRES VALID ENDEVOR INVENTORY LOCATION TO BE SPECIFIED
Reason:
Internal error.
Action:
C1G0023W
NO CHANGES DETECTED - SOURCE MANAGEMENT MAY HAVE ALREADY BEEN
PERFORMED FOR THIS ACTION
Reason:
No differences between the source and target elements were detected during ADD,
UPDATE, MOVE, or TRANSFER action processing.
Action:
None.
C1G Messages
C1G0024E
THE ELEMENT WAS ALREADY PRESENT AT stage name
Reason:
An Add request specified an element name that already exists at the named stage.
Action:
Review the action request. Verify that the element specified for an Add request is the
correct one, and modify the request if appropriate. If a different action was intended,
correct the request and resubmit.
C1G0025E
THE VERSION NUMBER TO BE ADDED MUST BE GREATER THAN version number
Reason:
An Add request specified a new version option that was not greater than the current
version number for the specified element at the entry stage.
Action:
C1G0026E
NEW VERSION NUMBER MUST BE IN THE RANGE OF 01 TO 99
Reason:
An Add or Transfer request specified a new version option of 0.
Action:
C1G Messages
C1G0027C
XX% BASE STATEMENTS DELETED AND/OR NEW INSERTS EXCEED YY% OF BASE
Reason:
The request resulted in a regression on the base level of the element specified by
deleting XX% of the original statements and/or inserting a quantity of new statements
equivalent to YY% of the base level.
Regression occurs when either XX or YY is greater than the maximum permissible level
specified in the associated element type record.
Action:
None. However, check the current version of the element to make sure that the deletes
and/or re-inserts in the current level were intended. If regression occurs frequently for
this element type, contact the CA Endevor SCM environment manager to consider
increasing the regression threshold.
C1G0028C
XX% PRIOR INSERTS DELETED AND/OR YY% PRIOR DELETES RE-INSERTED
Reason:
The request resulted in a regression on the prior level of the element specified by
deleting XX% of statements inserted and/or re-inserting YY% of statements deleted in
previous updates. Regression occurs when either XX or YY is greater than the threshold
level specified in the associated element type record.
Action:
None. However, check the current level to make sure that the deletes and/or re-inserts
in the current level were intended. If regression occurs frequently for this element type,
contact CA Technical Support to consider increasing the regression threshold.
C1G0029W
NO ELEMENT SOURCE CHANGES DETECTED
Reason:
An action that normally creates an element delta level detected no source differences.
Action:
None.
C1G Messages
C1G0030E
UNABLE TO VERIFY FOOTPRINT FOR ELEMENT IN THE [BASE/DELTA/COMPONENT
BASE COMPONENT DELTA/PROCESSOR OUTPUT LIBRARY]
Reason:
One of the following members was not found while attempting to obtain the footprint
from the library: element base; element delta; component base; component delta;
processor output.
Action:
If the error is associated with a processor output, regenerate the element.
If the error is associated with an element, delete the element and restore it from a
prior unload tape or archive file.
If the error is associated with a component list, use the Delete action with ONLY
COMPONENT option to delete the component list base and delta, and then
regenerate the element to recreate the component list.
C1G0030I
AT LOCATION; ENV: environment, STG: stage id, SYS: system, SBS: subsystem, TYPE:
type
Reason:
Informational message. This message is associated with the previous message in the log.
It identifies the inventory location.
Action:
None.
C1G0031W
NO CHANGES EXIST AT THIS VVLL OF THE ELEMENT
Reason:
During source management, no source code changes were found at the version/level
specified.
Action:
None. This message is informational only.
C1G Messages
C1G0032E
UNABLE TO MOVE ELEMENT - PROCESS RC (return code) > THAN THE MAXIMUM
ACCEPTABLE RC (return code)
Reason:
An error condition detected during the execution of the move process was greater than
the maximum RC specified in the MAXRC parameter within this process.
Action:
Review the Execution Report to determine the step and cause of the error. Correct the
error and re-execute the request.
C1G0033E
UNABLE TO [MOVE|TRANSFER] ELEMENT - STATUS OF PROCESSOR OUTPUT IS
UNKNOWN - ELEMENT WAS RESTORED W/O REPROCESSING
Reason:
A Restore action was performed against the element indicated in the message, but the
element was not processed.
Action:
Generate the element in the entry stage. and retry the Move action. For Transfer
actions you can also code the Ignore Generate Failed clause.
C1G0034E
UNABLE TO [MOVE/TRANSFER] ELEMENT - ELEMENT HAS NOT BEEN REGENERATED
SINCE LAST SOURCE UPDATE
Reason:
A Move or Transfer action was requested for an element that was not generated. This
can occur when the BYPASS GENERATE PROCESS option was specified on an Add or
Update action.
Action:
Regenerate the element and resubmit the Move or Transfer request. For Transfer
actions you can also code the Ignore Generate Failed clause.
C1G Messages
C1G0035E
INVALID STAGE SPECIFICATION FOR COPYBACK OPTION
Reason:
A Generate action was submitted with the COPYBACK option specified. However the
stage specified was not a valid stage.
Action:
Correct the stage specification and resubmit the request.
C1G0036E
ONLY $IMR FUNCTION OF QUERY IS SUPPORTED IN PROCESSORS
Reason:
Internal error.
Action:
C1G0037E
ILLOGICAL DATE RANGE SPECIFICATION (FROM > TO)
Reason:
The date range specified is not valid.
Action:
Correct the values or the format of the dates (or both) and try again.
C1G0038E
SYSTEM CANNOT BE SPECIFIED WITHOUT ENVIRONMENT SPECIFICATION
Reason:
The system name cannot be specified without specifying the environment name.
Action:
Specify both the environment and system name on the request.
C1G Messages
C1G0039E
ELEMENT NAME, ASSOCIATED WITH THE ELEMENT ALIAS element name, WAS NOT
FOUND IN THE CATALOGUE
Reason:
CA Endevor SCM attempted to access the element master for the element associated
with this alias and it was not found.
Action:
C1G0040E
THE OBJECT TYPE PARM VALUE MUST BE D, E, EA, FA, OR PA. xx IS INVALID
Reason:
An internal error was detected in a call to the BC1PMSGL subroutine. The object type
parm value must be D, E, EA, FA, or PA. xx is invalid.
Action:
C1G0041E
THE OBJECT AREA LENGTH PARM VALUE OF nnnn IS INVALID
Reason:
Internal error. The BC1PLMSG message subroutine was passed an object area. The
length of the object found in the first two bytes of the area is zero or invalid.
Action:
C1G0042E
text
Reason:
Member name length of nn, exceeds maximum length allowed of nn.
Action:
Make sure the element name is correctly specified. If so, check the data set attributes to
verify the correct type of data set is specified.
C1G Messages
C1G0043E
MEMBER NAME member name CONTAINS INVALID OR LOWER CASE CHARACTERS
Reason:
An error condition was detected while attempting to store a member in a PDS. The
name must consist of national standard characters (A-Z, 0-9, #, $, @).
Action:
Choose a valid member name. If this name is generated by a program in your processor,
the program may need to be modified to generate a valid name.
C1G0044E
FOOTPRINT FILE FORMAT IS INVALID, REASON= reason
Reason:
The header information in the HFS footprint file is invalid. The reason literal indicates
the type of problem encountered.
Action:
C1G0045E
UNABLE TO ACQUIRE STORAGE TO SAVE THIS ENTRY, RESULT= result
Reason:
Unable to acquire storage to save this HFS directory entry information. The result literal
indicates the type of problem encountered.
Action:
C1G Messages
C1G0046E
THE ROOT ELEMENT IS NO LONGER VALID. ELEMENT NOT AT THE LOCATION SPECIFIED
IN THE WIP FILE.
Reason:
After the WIP file was built, the ROOT element is no longer at the location when the WIP
file was built. The PDM merge action terminates.
Action:
Rebuild the WIP file then perform the PDM merge again.
C1G0047E
ELEMENT AT TARGET. AN OUT-OF-SYNC CONDITION EXISTS BETWEEN THE ROOT
ELEMENT AND THE TARGET.
Reason:
The element was found at the merge target and is not the same as the Root Element.
Action:
Examine all locations along the map for this element. Then determine corrective action.
To override the out-of-sync condition, specify the SYNC NDVR OUTPUT option. Note,
this option will create a change level to bring the element back to the Root level before
creating the merge change levels.
C1G0048E
AN OUT-OF-SYNC CONDITION EXISTS BETWEEN THE ROOT AND THE ELEMENT UP THE
MAP.
Reason:
The element found up the map from the merge target location is not the same as the
Root element.
Action:
Examine all locations along the map for this element. Then determine corrective action.
To override the out-of-sync condition, specify the SYNC NDVR OUTPUT option. Note,
this option will first fetch the element from up the map back to the target location then
it will create a change level to bring the element back to the Root level before creating
the merge change levels.
C1G Messages
C1G0049E
ELEMENT UPDATED BEFORE THE FETCH BACK TO TARGET LOCATION COMPLETED.
Reason:
During the PDM merge process, an element was found up the map and it was in sync
with the Root element. Before the fetch process, that element was updated. The merge
process stopped, because this would have created an out-of-sync condition.
Action:
Examine all locations along the map for this element, and then determine the corrective
action.
C1G0050I
SCAN STOP OPTION ENABLED/DISABLED
Reason:
An action was initiated from an archive or unload file. This message lists the setting of
the SCAN_STOP parameter in the options table.
Action:
None.
C1G0051I
SCAN STOP OPTION DISABLED: INPUT DATA NOT IN LIFO ORDER
Reason:
An action was initiated from an archive or unload file and the SCAN_STOP option was
ENABLED in ENCOPTBL. While reading the archive or unload file CA Endevor SCM
detected that the data was not in LIFO order. CA Endevor SCM requires the data to be in
LIFO order to use this feature. The feature is disabled for the duration of the job.
Action:
None.
C1G Messages
C1G0052I
SCAN STOP OPTION DISABLED: AT LEAST ONE SCL STATEMENT CONTAINS A
WILDCARD
Reason:
ENABLED in ENCOPTBL. While reading the SCL statements for this request, at least one
SCL statement contained a wildcard. The option requires that NO WILDCARDS are used.
The feature is disabled for the duration of the job.
Action:
None.
C1G0053I
READ FROM ARCHIVE FILE STOPPED AS REQUESTED BY PRODUCT OPTION SCAN_STOP
Reason:
ENABLED IN ENCOPTBL. While reading the archive or unload file, CA Endevor SCM
detected that all SCL requests were serviced exactly once. No conflicting parameters
were found (C1G0051I/C1G0052I). CA Endevor SCM closes the archive/unload file
(concatenation) as if a physical End Of File was reached.
Action:
None.
C1G0054E
DATASET name IS NOT CATALOGUED
Reason:
Error occurred while trying to access the elements listing dataset. The dataset named in
the message was not cataloged.
Action:
The dataset must be cataloged to use the List Listing and Print Option Listing feature.
Check the execution log for any related messages.
C1G Messages
C1G0055E
DATASET name ALLOCATION FAILURE
Reason:
An allocation error occurred while trying to access the elements listing dataset. The
dataset name is named in the message.
Action:
Check the log for any related messages.
C1G0056E
LISTING MEMBER name NOT FOUND IN DATASET name
Reason:
The member does not exist in the dataset. This occurred during the Find Member I/O
request while performing the Print element option listing request.
Action:
The component data is out of sync. Re-generation of the element will correct its
associated output component data.
C1G0057I
LISTING PRINTED FROM DATASET ds-name MEMBER mem-name.
Reason:
The output listing file for the element was printed from the dataset member referenced
by this message.
Action:
None. Informational message.
C1G Messages
C1G0058E
LISTING MEMBER member-name FOUND IN DATASET dataset-name; FOOTPRINTS DO
NOT MATCH.
Reason:
The footprint in the output listing file for the element contains information that is not
consistent with the current location or date of the element.
Action:
Verify that the listing member was written for the current level of the selected element.
C1G0059W
LISTING MEMBER member-name FOUND IN DATASET dataset-name; HAS NO
FOOTPRINT
Reason:
In attempting to verify that the listing matched the current element, CA Endevor SCM
found that the listing does not contain a footprint.
Action:
Verify that the listing represents the current level of the selected element.
C1G0060C
LISTING MEMBER member-name FOUND IN DATASET dataset-name; CANNOT READ
FOOTPRINT.
Reason:
The listing member appears to have a footprint; but something is wrong with it.
Action:
Investigate how the listing was obtained, and determine what errors might have
occurred in this process.
C1G Messages
C1G0060E
ONLY MOVE ACTIONS ARE ALLOWED IN PROMOTION PACKAGES. OTHER ACTIONS
WERE FOUND
Reason:
During cast, validation of the actions in the promotion package found actions that are
not move actions. Only move actions are valid.
Action:
Edit the promotion package to remove any actions that are not move actions.
C1G0061E
THE ENV/STG ON ALL PROMOTION PKG ACTIONS MUST BE EQUAL. MULTIPLE LOCS
FOUND:
Reason:
During cast, validation of the promotion package found different from environment and
stage locations. To be valid, the from environment and stage locations for all move
actions must be the same.
Action:
Edit the promotion package to make sure that all the from environment and stage
locations for all the move actions are the same.
C1G0062E
SRC LOC1-> ENV: envir STG: stage-id SRC LOC2-> ENV: envir STG: stage-id
Reason:
This message provides additional information related to message C1G0061E. The LOC2
data shows the location of the first move action that did not match the location of
previous move actions.
Action:
Edit the SCL associated with the promotion package to ensure all the from environment
and stage locations are the same.
C1G Messages
C1G0064I
PROCESSING STATEMENT #scl-stmt-num
Reason:
This identifies which action (SCL statement) in the cast report is associated with the
subsequent messages.
Action:
No action required.
C1G0065E
ROOT SPECIFICATION IS DIFFERENT FROM THE ROOT'S CURRENT VVLL.
Reason:
Either the root element was updated after the WIP file was built, or the specified root
VVLL was not the element's last VVLL. Merge cannot proceed, otherwise the updated
root would be out-of-sync.
Note: This error does not occur if the merge target location maps to or is the same as
DV1 element.
Action:
Rebuild the WIP file with the most current VVLL of the root element or use the target
location which maps to or is the same as DV1 element.
C1G Messages
C1G0066C
SRC FOOTPRINT DOES NOT MATCH FOOTPRINT FOUND IN DSN:
PUBLIC.P5736.STG1.LISTLIB MBR: TESTPGM
Reason:
Action:
None.
C1G0067C
WITH FOOTPRINT ENV: ENV1 SYS: EZSYS SBS: EZSUB ELE: TESTPGM
TYP: PGM STG: 1 VVLL: 0100
Reason:
Action:
None.
C1G0068E
THE VALIDATE ACTION IS NOT SUPPORTED IN A PACKAGE
Reason:
The Validate action cannot be included in a package. It must be executed from a batch
job outside of a package.
Action:
Remove all Validate actions from the package.
C1G Messages
C1G0069E
THE AUTOGEN OPTION IS NOT ALLOWED IN PACKAGES
Reason:
The AUTOGEN option cannot be specified on actions that are included in a package.
Action:
Execute this action from outside of a package or remove the AUTOGEN option from all
the actions included in the package.
C1G0070E
THE AUTOGEN OPTION MAY ONLY BE USED IN BATCH
Reason:
The AUTOGEN option cannot be specified on actions you are executing in foreground
mode.
Action:
Execute this action within a batch job or remove the AUTOGEN option from all the
foreground actions.
C1G0071E
GLOBAL TYPE SEQUENCING MUST BE ENABLED FOR AUTOGEN
Reason:
The AUTOGEN option cannot be specified on actions unless the global type sequencing
feature is enabled.
Action:
Refer to the TYPESEQMBR parameter in the C1DEFLTS table for additional information
on how to enable this feature.
C1G Messages
C1G0072C
MEMBER NAME member name CONTAINS INVALID CHARACTERS AND WILL BE
SKIPPED
Reason:
A caution condition was detected while attempting to add an element from a member
in a PDS. The name contains an invalid character or a wildcard character and the
member was not added to Endevor.
Action:
To add that member from PDS, you have to change its name so that it consists of
national standard characters (A-Z, 0-9, #, $, @).
C1G0103W
PACKAGE BACKOUT DOES NOT SUPPORT THE "IEBCOPY" UTILITY PROGRAM
Reason:
A package was submitted for execution with the BACKOUT option enabled. However, a
processor step that invokes IEBCOPY was encountered. Because IEBCOPY uses
nonstandard techniques when updating a partitioned data set directory, BACKOUT
information cannot be captured.
Action:
Update the processor, changing the IEBCOPY specification to the CA Endevor SCM
program BSTCOPY.
C1G0110E
THE ELEMENT WAS NOT FOUND AT EITHER stage name 1 OR stage name 2
Reason:
A Generate request was made for element name, but the element is not present at
either stage. The action was not executed.
Action:
Verify that the element you want to process is correctly specified in the request. If
necessary, resubmit the request. If the element was correctly specified; then it must
first be added.
C1G Messages
C1G0111W
TO-FROM NAME (member name) IGNORED - USER DATA SET ORGANIZATION IS
SEQUENTIAL
Reason:
A request specified a member name to use in the users source or target data set.
However, the source or target data set is not partitioned. The member name
specification was ignored.
Action:
None. However, verify that the request specified the source or target data set correctly.
If necessary, resubmit the request with the correct data set name.
C1G0112I
element name vvll DELETED FROM dsname
Reason:
Informational message. A processor output associated with element name was deleted
from data set dsname.
Action:
None.
C1G0114E
SYSTEM system NOT DEFINED
Reason:
A request specified a system for which no definition exists in the master file.
Action:
Make sure that the system name was correctly specified in the request. If appropriate,
resubmit the request. If a new system must be defined, contact CA Technical Support.
C1G Messages
C1G0118C
FOOTPRINT COMPROMISED: field-name field-value
Reason:
The footprint associated with a base/delta or processor output member was
compromised. The reason is given at the end of the message.
Action:
Regenerate the element if it is a processor output member. If it is a base/delta member,
retrieve the element, delete it, then re-add it.
C1G0118I
FOOTPRINT COMPROMISED: reason
Reason:
Informational message. The footprint associated with a base/delta or processor output
member was compromised. The reason is given at the end of the message.
Action:
retrieve the element, delete it, and then re-add it.
C1G0119E
Reason:
CA Endevor SCM validated the footprint. This field was in error.
Action:
retrieve the element, delete it, and then re-add it.
C1G0119W
Reason:
CA Endevor SCM validated the footprint. This field was in error.
Action:
None.
C1G Messages
C1G0120W
FOOTPRINT VERIFY - UNABLE TO LOCATE ELEMENT USING FOOTPRINT INFORMATION,
BUT DATE/TIME MATCHES
Reason:
During footprint validation, CA Endevor SCM tried to locate an element using the
element's ENV/STG/SYS/SUB information. The system and or subsystem no longer exist
in this environment.
Action:
None. Footprint validation will default to DATE/TIME stamp checking.
C1G0126E
NOT RETRIEVED - NO REPLACE SPECIFIED AND THE ELEMENT WAS FOUND IN THE
DATA SET
Reason:
A Retrieve request for element name found a member with that name already exists in
the target data set dsname.
Action:
Reexecute the request, using a different data set as the destination, or enable
replacement of the present member element name.
C1G0127C
element name DOES NOT EXIST IN dsname - BYPASSING DELETE
Reason:
A request for element name found no such member in data set dsname. CA Endevor
SCM proceeded to execute the next step.
Action:
Make sure that the delete request specified the correct element name. If necessary,
resubmit the request.
C1G Messages
C1G0128E
data set type NOT FOUND IN INCLUDE CHARACTERISTICS TABLE FOR TYPE type name
AT STAGE stage name
Reason:
This message is issued when CA Endevor SCM attempts to expand INCLUDEs but is
unable to determine the characteristics based on data set type and language defined for
the type identified in the message.
Action:
Make sure that the language is specified correctly on the type definition identified in the
message.Also, verify that the LIBENV field in the C1DEFLTS table is in agreement with
the language specified on the type definition.
C1G0129E
STEP step name RC (return code) EXCEEDS THE MAX RC (max return code) FOR THE
PROCESSOR STEP
Reason:
The named step in a processor resulted in a return code that is greater than the
maximum acceptable return code for that step in the processor definition. CA Endevor
SCM set a "processor failed flag."
Action:
Examine the processor output and messages to determine the cause of the error.
Correct the error condition and resubmit the request. If the requested action was Move,
a Generate action must be executed prior to submitting a new Move request.
C1G0131C
INVALID PARM - parm name - DEFAULTING TO EXPAND
Reason:
An invalid value was specified for the EXPINCL parm during a CONWRITE step in the
processor. Valid parms are Y and N only. The default value of Y was used.
Action:
Contact CA Technical Support and verify the specification in the processor step.
C1G Messages
C1G0132I
ELEMENT VVLL vvll WRITTEN TO DATA SET
Reason:
Informational message. Element name was successfully written to dsname during
processing.
Action:
None.
C1G0134I
ELEMENT FOOTPRINTED IN DATA SET
Reason:
Informational message. A footprint was created for element name in data set dsname.
Action:
None.
C1G0134W
ELEMENT FOOTPRINTED WITH WARNING IN DATA SET
Reason:
While footprinting a module, CA Endevor SCM encountered a warning condition.
Action:
See previous messages. Processing continues.
C1G0134E
UNABLE TO FOOTPRINT ELEMENT IN DATA SET
Reason:
CA Endevor SCM cannot footprint the member identified in the message.
Action:
C1G Messages
C1G0135C
ELIB LISTING COMPONENT DATA WAS NOT CREATED THRU CONLIST
Reason:
The CONLIST utility was attempting to create component data for this ELIB output
listing. One of the P-to-P operations failed.
Action:
C1G0136W
EXIT PROGRAM program name : HFS FILE UPDATES NOT SUPPORTED THROUGH EXITS,
UPDATE IGNORED
Reason:
Informational message. HFS file updates are not supported through exits.
Action:
None.
C1G0138E
INVALID EXECUTION PARAMETER - parm name
Reason:
A processor parameter was specified that is not valid for the processor associated with
the element in the request. If [PARM] requested a footprint, the object data set was not
opened successfully.
Action:
Verify that the required parameter is correctly specified in the processor definition.
Contact CA Technical Support to correct the processor definition. Resubmit the request.
C1G Messages
C1G0139I
MEMBER DELETED FROM DATA SET
Reason:
Informational message. A delete processor step successfully deleted member name
from data set dsname. However, member name did not contain a footprint in the PDS
directory.
Action:
None.
C1G0140S
processor name - csect name ABENDED CODE=return code
Reason:
The program in the processor identified in the message terminated abnormally. The
reason for the abend is the indicated return code.
Action:
This message has three parameters:
processor nameThe name of the processor that produced the abend code.
csect nameThe CSECT name where the abend occurred.
return codeThe return code indicating why the job terminated.
Consult the appropriate documentation for the meaning of the return code. The
appropriate documentation is a function of the program currently in control when the
message was issued. For example, if a COBOL compile produced the message, refer to
the COBOL error messages and codes. Correct the condition that caused the abend and
C1G Messages
C1G0141E
SYSTEM system REQUIRES A COMMENT TO BE SPECIFIED - REQUEST NOT PERFORMED
Reason:
No comment was specified for the request. The system specified in the request requires
a comment.
Action:
Check the request. To see if a system requires a comment, check the system definition
using the Display Systems/Subsystems option. If the COMMENT REQUIRED field is YES;
then you must always include a comment for Add, Update, Retrieve, and Generate
requests.
C1G0142E
SYSTEM system REQUIRES A CCID TO BE SPECIFIED - REQUEST NOT PERFORMED
Reason:
No CCID was specified for the request. The system specified in the request requires a
CCID.
Action:
Check the request. To see if a system requires a CCID, check the system definition using
the Display Systems/Subsystems option. If the CCID REQUIRED field is YES; then you
must always include a change CCID for requests that modify source code.
C1G0143I
BEGINNING EXECUTION OF [GENERATE/DELETE/MOVE] PROCESSOR processor name
OF GROUP group name.
Reason:
Informational message. This message is issued immediately prior to processor
execution.
Action:
None.
C1G Messages
C1G0144I
PROCESSOR processor name EXECUTION COMPLETED, HIGHEST PROCESSOR STEP RC
WAS return code
Reason:
Informational message. This message is issued when processor execution is complete.
Action:
None.
C1G0145E
A [GENERATE|MOVE|DELETE] PROCESSOR IS NOT DEFINED FOR PROCESSOR GROUP
processor group name
Reason:
No processor was defined for the processor group definition for the element type and
system specified in the request. A processor is usually specified for generate (Add,
Update and Generate), delete, and move functions.
Action:
Contact CA Technical Support to verify that the omission of the processor name is
intended.
C1G0146W
DELETE PROCESSING COMPLETED. RECOVERABLE ERRORS WERE ENCOUNTERED
DURING DELETE PROCESSING
Reason:
The Delete action completed but CA Endevor SCM encountered one or more
recoverable errors. It is possible that the CA Endevor SCM execution log may contain
one or more E level messages. These errors can be ignored.
Action:
None. The element was deleted.
C1G Messages
C1G0147E
THE GENERATE PROCESSOR FOR TYPE element type (processor 1) WAS NOT THE LAST
PROCESSOR EXECUTED (processor 2)
Reason:
If the last processor to execute was Generate, verify that the Generate processor
executed is the same as is associated with the processor group. If they are the same,
verify that the Generate date and time is greater than the last Update date and time.
Action:
Generate the element, and then resubmit the Move or transfer request. If you receive
this message for a Transfer request, you can resubmit the request, specifying the
IGNORE GENERATE FAILED option. If a valid return code was produced from the
generate step and you are still getting this error, make sure that the current processor
group is defined at the target of the transfer.
C1G0148E
THE LAST processor-type PROCESSOR EXECUTION AT stage FAILED
Reason:
During a Move or Transfer request, CA Endevor SCM checks the results of the most
recent processor. The processor return code was greater than the maximum acceptable
return code specified in the processor definition, and a "processor failed" flag was set,
preventing the action.
Action:
Correct and rerun the failed processor before restarting the action. For Transfer actions
you can also code the Ignore Generate Failed clause.
C1G0149E
EXECUTION OF processor name TERMINATED - FOOTPRINT IS NOT VALID
Reason:
During execution of [PROCESSOR], CA Endevor SCM encountered a missing or invalid
footprint. The step during which the message was issued specified footprint verification
(FOOTPRNT=VERIFY). Execution was terminated.
Action:
Submit a Generate request for the element in order to verify the valid footprints are
present for each processor output. The action request that generated this message may
be resubmitted.
C1G Messages
C1G0150I
dsname(member name) FOOTPRINT VERIFIED
Reason:
Informational message. A footprint for member name in library dsname was successfully
verified. Footprint verification was specified for the processor that executed.
Action:
None.
C1G0151E
RC - nnnn UNABLE TO READ JOB FILE CONTROL BLOCK FOR DDNAME ddname
Reason:
A CA Endevor SCM job attempted to read job file control block data for ddname and was
unable to read the required data. Either the requested DD statement was not
dynamically allocated, or the DD statement was missing from the JCL stream.
Action:
Examine the Execution Report and note the return code. Refer to the appropriate IBM
documentation for your operating system for a listing of applicable return codes and
their meanings.
C1G0152E
RC - nnnn UNABLE TO OBTAIN DATA SET CONTROL BLOCK FOR THIS DATA SET
Reason:
A CA Endevor SCM job attempted to obtain the data set control block for dsname and
was unable to read the required data. The required data was either not found on the
volume where it is cataloged, or the required volume was not mounted.
Action:
Examine the Execution Report and note the return code. Refer to the appropriate IBM
their meanings.
C1G Messages
C1G0153E
RC - nnnn UNABLE TO OPEN ddname/dsname
Reason:
A CA Endevor SCM job was unable to open dsname, allocated to DDname. The return
code [NNNN] was issued by an OPEN macro instruction.
Action:
Examine the execution report and note the return code. Refer to the appropriate IBM
their meanings.
C1G0154W
dsname (member name) NOT FOUND
Reason:
A CA Endevor SCM job was unable to locate an entry for the named member in the PDS
directory for the named data set.
Action:
None.
C1G Messages
C1G0155S
UNKNOWN STOW ERROR return code:reason code, MEMBER member name, DSN data
set name
Reason:
A STOW macro instruction was issued for the member and data set specified. CA
Endevor SCM was unable to interpret the return code and reason code from the STOW,
and may indicate an error condition which requires immediate attention.
Action:
The return codes and reason codes from STOW are documented in the appropriate IBM
data management manuals for the release of your operating system and DFP or DFSMS.
Check the tables of return codes for recommended IBM corrective action.
If you need CA Technical Support, the following information is required:
CA Endevor SCM release and maintenance level.
Operating system base release and DFP and DFSMS release and maintenance level.
CA Endevor SCM action being executed.
Attributes of the data set against which the error was reported, including all DCB
operands, PDSE information if applicable.
Information related to other PDS system management products in use at your site.
C1G0156S
INSUFFICIENT VIRTUAL STORAGE TO READ/UPDATE DIRECTORY OF dsname
Reason:
CA Endevor SCM was unable to obtain sufficient virtual storage to perform the
requested read or update for the PDS directory of data set dsname. Either a region
specification on a job statement was too small, a TSO logon region size was insufficient,
or CA Endevor SCM was in use in split-screen mode.
Action:
If the error occurred in split-screen mode, revert to a single screen and retry the
request. If region size is still insufficient, log on to TSO with a larger region size. If the
error occurred during background execution, increase the region size requested on the
job statement.
C1G Messages
C1G0157E
UNABLE TO DELETE MBR member name/dsname - DDNAME ddname NOT OPEN
Reason:
An error occurred during an earlier processing step in a CA Endevor SCM job, resulting in
a situation where DDname was not allocated when requested.
Action:
Review the Execution Report for the request. Correct the error condition and reexecute
this request.
C1G0158C
OUT OF SPACE IN THE DIRECTORY OF dsname
Reason:
The PDS directory of the named data set is using all the directory blocks allocated to it.
The requested action created a new member in the named data set, but CA Endevor
SCM is unable to create a directory for that member.
Action:
Delete unneeded members from the data set or reallocate the data set, requesting a
larger quantity of directory blocks. Resubmit the request.
C1G0158S
OUT OF SPACE IN THE DIRECTORY OF dsname
Reason:
The PDS directory of the named data set is using all the directory blocks allocated to it.
The requested action created a new member in the named data set, but CA Endevor
SCM is unable to create a directory for that member.
Action:
Delete unneeded members from the data set or reallocate the data set, requesting a
larger quantity of directory blocks. Resubmit the request.
C1G Messages
C1G0159E
ddname - UNABLE TO PERFORM I/O REQUEST - DDNAME ddname NOT ALLOCATED
Reason:
An error occurred during an earlier processing step in a CA Endevor SCM job, resulting in
a situation where DDname was not allocated when requested.
Action:
Review the Execution Report for the request. Correct the error condition and reexecute
this request.
C1G0161I
PROCESSOR processor id NOT EXECUTED BECAUSE OF ERRORS ENCOUNTERED DURING
SOURCE MANAGEMENT
Reason:
The element type specified for this action executes both a basic and an extended
processor. This message indicates that the appropriate extended processor was not
executed as a result of errors encountered during the basic processor step.
Action:
Examine the execution report for errors associated with the basic processor for the
specified element type. Correct the errors indicated and reexecute the request.
C1G0162I
SOURCE MANAGEMENT HAS RUN OUT OF SPACE DURING SORT PROCESSING
Reason:
Informational message which follows C1G0140S when source management runs out of
space on the temporary data set C1SORTIO. CA Endevor SCM uses C1SORTIO when
comparing elements of types that have a COMPARE COLUMN range greater than 4000
characters.
Action:
Allocate a C1SORTIO DD in the JCL of the failing step: C1SORTIO DD
UNIT=SYSDA,SPACE=(CYL,(nnn,nnn)). The allocated data set must be large enough to
hold both the old and the new version of the element.
C1G Messages
C1G0164E
MEMBER member name ALREADY EXISTS IN DATA SET dsname.
Reason:
Internal error.
Action:
Notify CA Technical Support.
C1G0165E
THE action name ACTION CANNOT BE PERFORMED - PROC GRP processor group name
NOT DEFINED FOR TYPE type name AT STAGE stage id
Reason:
The processor group selection program cannot find the identified processor group at the
identified stage.
Action:
Define the processor group for the type. If the action is a Move, verify that the
processor group mapping is defined properly and that the target processor group is
defined.
C1G0166E
element name CANNOT BE PROCESSED. PROCESSOR GROUP processor group name IS
NOT DEFINED FOR TYPE type name
Reason:
The processor group identified in the message was not defined for the type identified in
the message.
Action:
Define the processor group.
C1G Messages
C1G0167E
ELEMENT IS NOT AVAILABLE. IT IS ALREADY "SIGNED-OUT" TO userid
Reason:
An action was attempted against the element identified in the message, but was
rejected because the element was signed out to the user identified in the message.
Action:
If you are authorized to do so, you may specify the override signout option.
C1G0168E
ELEMENT CANNOT BE ADDED BECAUSE IT IS NOT IN "SIGNED OUT" STATUS IN
environment/stage
Reason:
An Add was attempted for an element but was rejected because the element exists up
the map, at the environment/stage specified in the message, where it was not signed
out.
Action:
Retrieve the element, and then resubmit the Add request.
C1G0169E
SIGN-OUT ERROR. DATA SET MISMATCH DETECTED
Reason:
The Validate DSNAME option was specified for the system to which the element is being
added, and the data set name associated with the previous Retrieve of this element is
not the same as the data set name specified for the Add action.
Action:
Copy the member to the correct data set and resubmit the Add request.
C1G Messages
C1G0170E
DSN VALIDATION OPTION IS ACTIVE - ELEMENT MUST BE RETRIEVED PRIOR TO
ADD/UPDATE
Reason:
The data set validation option is active for the current system. The element must be
retrieved prior to updating, or the data set and/or member name of the retrieve data
set is different than the name of the source data set and/or member.
Action:
Use the element master display panel to determine the location to which the element
was retrieved. Make sure this matches the name of the source location you are
specifying when executing the Add with Update or Update action.
C1G0171I
THE ELEMENT HAS BEEN SUCCESSFULLY SIGNED-IN
Reason:
Informational message. This message confirms the success of the Sign-in action.
Action:
None.
C1G0172W
EXPLICIT SIGN-IN NOT PERFORMED, ELEMENT IS CURRENTLY NOT SIGNED OUT
Reason:
A request was made to explicitly sign-in an element. However, the element is not
signed-out.
Action:
None.
C1G Messages
C1G0173E
EXPLICIT SIGN-IN NOT PERFORMED - SIGN-IN/SIGN-OUT OPTION NOT IN EFFECT FOR
SYSTEM system
Reason:
The Sign-in/Sign-out action is not supported for the system in which the element in
question resides.
Action:
Sign-in/Sign-out authorization is specified on the System Definition.
C1G0174W
THE FETCHED ELEMENT IS LOCKED BY PACKAGE package AND CANNOT BE SIGNED
OUT
Reason:
Even though SOFETCH=Y was specified in the defaults table, the element was not signed
out, because the element was reserved by a package and changing the signout status of
a locked element can cause a failure during package execution. The action processing
continues but the signout status of the element is not changed.
Action:
None.
C1G0176I
THE ELEMENT HAS BEEN REASSIGNED TO userid
Reason:
The element was signed out to the user ID referenced in the message.
Action:
None.
C1G Messages
C1G0178I
member name DELETED FROM THE dsname
Reason:
Informational message. This indicates that the DELETE INPUT SOURCE option was
specified when issuing an Add or Update action and the delete was successful.
Action:
None.
C1G0179C
UNABLE TO DELETE element name FROM THE dsname
Reason:
An Add or Update action was requested with the option DELETE INPUT SOURCE. The
element will not be deleted due to errors previously encountered when attempting to
perform the Add or Update action.
Action:
Review messages that precede the C1G0179C message. Correct any errors and retry the
action.
CIG0186E
GENERATE FAILURE
Reason:
A request to generate an element was issued, but the Type is not valid for the Processor
Group.
Action:
Verify that the Processor Group is defined for the Type at the Stage that is the target of
the Generate action.
C1G Messages
C1G0187E
THE ELEMENT WAS NOT FOUND IN STAGE stage name
Reason:
A request to generate an element was issued but the element against which the request
was issued no longer exists.
Action:
Verify that the element against which the action is being issued was coded correctly. If
the element name and location information was properly specified (that is,
environment, system, etc.), determine if the element was archived or deleted while you
were attempting to generate the element.
C1G0189I
DATA SET DELETED
Reason:
An Add or Update action was requested. The option DELETE INPUT SOURCE was
specified. Upon successful completion of the action the source input was deleted.
Action:
None.
C1G0191C
MEMBER member name COPY OPERATION COMPLETED WITH WARNINGS, REASON
CODE reason code
Reason:
BSTCOPY attempted to copy a program object to or from a PDSE load library, and the
operation completed with cautionary (return code 8). The reason code is generated by a
binder interface module, and is not the actual binder reason code.
Normally, cautionary return codes indicate errors which require immediate attention,
and following corrective procedures, usually require rerunning the action that resulted
in the failure.
Action:
Other messages may be issued by CA Endevor SCM (written to C1MSGS DD) or by the
binder (written to the batch message log or on the TSO users terminal). Check other
messages issued and follow the corrective action specified.
C1G Messages
C1G0191W
MEMBER member name COPY OPERATION COMPLETED WITH WARNINGS, REASON
CODE reason code
Reason:
operation completed with warnings (return code 4). The reason code is generated by a
binder interface module, and is not the actual binder reason code.
Normally, warning return codes do not indicate serious errors, and may not require
serious attention.
Action:
Other messages may be issued by CA Endevor SCM (written to C1MSGSDD) or by the
C1G0192E
MEMBER member name COULD NOT BE COPIED, REASON CODE reason code
Reason:
operation failed in return code 12. The reason code is generated by a binder interface
module, and can be the actual binder reason code.
Action:
Other messages may be issued by CA Endevor SCM (written to C1MSGSDD) or by the
Normally, error return codes require immediate attention, and following corrective
procedures, usually require rerunning the action which resulted in the failure.
C1G0193I
message text
Reason:
This message may accompany C1G0191W, C1G0191C, OR C1G0192E. The message text
shown is generated by a binder interface module and is used to assist in diagnosis of
errors indicated by the other messages. If no message text is generated by the binder
interface module, this message does not appear.
C1G Messages
C1G0194E
ALIAS alias name COULD NOT BE STORED FOR MEMBER member name, BINDER
RETURN CODE return code, REASON CODE reason code
Reason:
BSTCOPY attempted to store an alias for a root member and failed. The return code and
reason code are generated by a binder interface module, and are not the actual binder
return code and reason code.
Action:
Other messages may be issued by CA Endevor SCM (written to the C1MSGS DD) or by
the binder (written to the batch message log or the TSO users terminal). Check other
Normally, error return codes require immediate attention, and following the corrective
procedures, usually require rerunning the action which resulted in the failure.
C1G0195I
STATEMENT synstmt number
Reason:
This message ties together the requests shown in the Syntax Request Report with
actions specifying wildcarded location that were not executed during CA Endevor SCM
processing.
Action:
None.
C1G0199W
THE FOLLOWING ELEMENT WAS NOT VALIDATED: element name
Reason:
This component could not be validated. Most likely there is no MCF entry for this
element.
Action:
None.
C1G Messages
C1G0200I
ELEMENT ACTION REQUEST PROCESSING COMPLETED, HIGHEST ENDEVOR RC WAS
return code
Reason:
Informational message. CA Endevor SCM completed processing of all requests for
element name. The highest return code encountered during all request processing was
return code.
Action:
None.
C1G0201E
NO ACTIONS PERFORMED - SYNTAX STMT statement
Reason:
The syntax parsed by the SCL parser contained errors or no actions were included in the
SCL input.
Action:
Correct any syntax errors previously printed in the SYNTAX REQUEST REPORT or make
sure some actions were specified as input to the parser. If &&ACTION requests were
included as input to the SCL syntax parser, make sure a SET ACTION action was
specified.
C1G0202I
ACTION action number / STMT synstmt number
Reason:
This message ties together the requests shown in the Syntax Request Report with the
actions actually performed in the Execution Report. Each syntax statement parsed by
the SCL syntax parser is assigned a SYNSTMT number. Each action performed is assigned
an ACTNUM.
Action:
None.
C1G Messages
C1G0203I
action ELEMENT element name
Reason:
This message shows the name against which an action is issued. The action and syntax
number precede this message in the Execution Report. The FROM and TO location of
the element is shown in messages following this message.
Action:
None.
C1G0204I
[FROM|TO] ENVIRONMENT: environment name SYSTEM: system SUBSYSTEM:
subsystem: TYPE: type name: STAGE ID: stage id
Reason:
This message indicates the FROM or TO location of the element against which an action
is performed. The element name and action precede this message. The information
shown in this message is related to the FROM and TO clause specified in the SCL syntax
specified as input to the SCL parser. Message C1G0202I indicates the syntax that relates
to the action performed.
Action:
None.
C1G0205I
[FROM|TO] [DDNAME|FILE] (dsname or ddname) [MEMBER|BLANK] (member name
or blank)
Reason:
is performed. The element name and action precedes this message. The information
shown in this message is related to the FROM and TO clause specified in the SCL syntax
Action:
None.
C1G Messages
C1G0206I
ACTION ELEMENT RC RC ENVIRONMENT SYSTEM SUBSYSTEM TYPE STAGE TIME
NUMBER NUMBER WRITTEN
Reason:
This informational message appears as a header on the Action Summary Report. This
message indicates the element against which an action occurred along with return code
information. For a description of the Action Summary Report, see the SCL Reference
Guide.
The first line of this message is message C1G0222I, described later.
Action:
None.
C1G0207I
text
Reason:
This informational message is produced on Execution Summary Report.
Action:
None.
C1G0208E
ELEMENT NOT FOUND FOR SYNTAX STATEMENT #stmt-number
Reason:
This message indicates that the element against which an action was issued was not
found.
Action:
Verify that the element is currently in the Master Control File. If the element name is
not correct, specify the correct element name and resubmit the request.
C1G Messages
C1G0208W
ELEMENT NOT FOUND FOR SYNTAX STATEMENT #stmt-number
Reason:
This message indicates that the element against which an action was issued was not
found.
Action:
Verify that the element is currently in the Master Control File. If the element name is
not correct, specify the correct element name and resubmit the request.
C1G0209E
TYPE type WITHIN SYSTEM system HAS NOT BEEN DEFINED AT STAGE 2
Reason:
An action request was issued against an element. The Stage 1 type associated with the
element does not have a corresponding Stage 2 type definition. The specified type must
be defined at both stages in the environment.
Action:
Contact CA Technical Support. The Stage 1 type definition must be modified. Define the
associated Stage 2 element type shown in the message that precedes this message.
C1G0210S
SERIOUS ERROR HAS OCCURRED - PROCESSING WILL BE TERMINATED
Reason:
The message that precedes this message indicates the serious error that occurred. This
message indicates that no additional actions will be executed.
Action:
Review the messages that precede this message, correct the errors, and resubmit this
job.
C1G Messages
C1G0211I
VERSION version number [LEVEL level number]
Reason:
Informational message for batch Retrieve and Print actions that echoes the input SCL
information.
Action:
None.
C1G0212E
INVALID STAGE SPECIFIED
Reason:
The stage ID specified on the request shown in the message that precedes this message
is invalid.
Action:
Specify the proper stage and retry the action.
C1G0213I
[FROM|TO] ARCHIVE FILE: ddname
Reason:
is performed. The element name and action precedes this message. The information
shown in this message is related to the FROM and TO clause specified in the SCL syntax,
Action:
None.
C1G Messages
C1G0214S
UNABLE TO DELETE DATA SET
Reason:
The action was requested but could not complete.
Action:
Review the DSNAME against which the request is being issued. Make sure that the
DSNAME is a format supported by CA Endevor SCM. Correct the data set name and retry
the action.
C1G0215E
ERROR ENCOUNTERED WHEN ATTEMPTING TO OPEN DATA SET dsname
Reason:
An attempt to open the data set shown in this message failed.
Action:
Review the DSNAME against which the request was issued. Make sure that the DSNAME
is a format supported by CA Endevor SCM. Correct the data set name and retry the
action.
C1G0216E
UNABLE TO OPEN THE DATASET
Reason:
An attempt to open the input data set failed. This error is issued for one of the following
reasons: 1) the data set does not exist, 2) the data set is not catalogued, 3) the data set
is in use by another user or job, 4) the data set attributes are not valid for use by CA
Endevor SCM.
Action:
Check the conditions listed above. If no problem is found, it was probably in use by
another user or job. Retry the action.
C1G Messages
C1G0217E
member name NOT FOUND IN dsname
Reason:
An action request was issued requiring members from a data set to be selected, but
there were no members in the data set that matched the element name or name mask
specified on the action request.
Action:
Review the DSNAME against which the request is being issued. Correct the data set
name or member name and retry the action.
C1G0218E
LIST ACTION NOT ALLOWED AGAINST SEQUENTIAL dsname
Reason:
A List action was issued against a sequential data set. The List action is not supported
against sequential data sets.
Action:
Review the DSNAME against which the request is being issued. The List action is not
supported against sequential data sets.
C1G0219I
PROCESSOR IS NOT COMPATIBLE WITH THIS RELEASE. PLEASE REGENERATE
Reason:
Processor listings are not available for view.
Action:
C1G Messages
C1G0220I
action MEMBER member name
Reason:
This message shows the name against which an action was issued. The action and syntax
number precedes this message in the Execution Report. The FROM and TO location of
the member is shown in messages following this message.
Action:
None.
C1G0221I
From/To ELEMENT/MEMBER/PATH/HFSFILE object-name
Reason:
Informational message. This message contains the name of the FROM or TO object
specified in this action.
Action:
None.
C1G0222I
PROC NDVR + - - - - - - - - - - - - FROM INFORMATION - - - - - - - - - - + ACTION ACTION
STMT SCL
Reason:
This is the heading line that appears on the Action Summary Report. This line indicates
the action that was requested, the processor and return codes, the location from where
the element originally existed prior to the action executed, the action performed, the
syntax statement number, and the page number within the Execution Report on which
the action was executed.
Action:
None.
C1G Messages
C1G0223E
TO DDNAME ddname NOT VALID FOR PRINT OUTPUT
Reason:
The DDNAME specified in the TO clause of the Print action is not valid.
Action:
For a description of the Print action, see the SCL Reference Guide. Correct the syntax and
retry the action.
C1G0224E
PRINT ACTION MUST SPECIFY TO FILE OR NULL DESTINATION
Reason:
No DDNAME was specified in the TO clause of the Print action.
Action:
For a description of the Print action, see the SCL Reference Guide.
C1G0225S
I/O ERROR ON FILE ddname REASON reason - ACTION TERMINATED
Reason:
When writing to the DDNAME shown above, an I/O error was encountered. The reason
code shown in the message indicates the cause of the problem. Most likely, the file
written to is invalid or is full.
Action:
If the file shown in the DDNAME is invalid, specify a valid data set name. If the file is full,
increase the space associated with the DSNAME and retry the action.
C1G Messages
C1G0226I
[TO|FROM] ENVIRONMENT: environment SYSTEM: system SUBSYSTEM: subsystem
TYPE: element type STAGE #: stage number
Reason:
This message appears immediately after the action executed is displayed. This message
indicates the FROM or TO location of the element.
Action:
None.
C1G0227E
UNABLE TO MATCH SYSTEM system IN ENVIRONMENT environment name
Reason:
The system specified against the action shown in the previous message was not found in
the environment specified.
Action:
Specify a valid environment and system name. Correct the action request and resubmit
the job.
C1G0228E
UNABLE TO MATCH SUBSYSTEM subsystem IN SYSTEM system
Reason:
The subsystem specified against the action shown in the previous message was not
found in the system specified.
Action:
Specify a valid system and subsystem name. Correct the action request and resubmit
the job.
C1G Messages
C1G0229E
TYPE type name NOT DEFINED FOR SYSTEM system
Reason:
The type identified in the message was not found in the system identified in the
message.
Action:
Verify that system and type name are correctly specified.
C1G0230W
ELEMENT(S) BYPASSED, FAILED TO SATISFY "WHERE" CLAUSE
Reason:
One or more elements/members from a selection list did not meet the WHERE TEXT or
the WHERE COMP SPEC specifications of a List request.
Action:
Correct the request and resubmit the action.
C1G0231E
ELEMENT(S) FOUND, BUT FAILED TO SATISFY "WHERE" CLAUSE OR VVLL SPECIFIED
DOES NOT EXIST
Reason:
All element or members on a selection list for a List action either did not meet the
WHERE GENERATE FAILED, WHERE GENERATE DATE, WHERE CCID OF, OF WHERE
PROCESSOR GROUP EQUAL selection criteria, or the version and level specified for the
element do not exist. This message can also appear as a warning.
Action:
Correct the request and resubmit the action.
C1G Messages
C1G0231W
ELEMENT(S) FOUND, BUT FAILED TO SATISFY "WHERE" CLAUSE OR VVLL SPECIFIED
DOES NOT EXIST
Reason:
Elements were found that match the naming convention, but due to WHERE clause
selection criteria or the VVLL specified, no elements were selected.
Action:
Verify that the WHERE clause selection criteria and VVLL are correct. If so, no action is
required.
C1G0232I
text
Reason:
The text in this message shows those options that are in effect for the element against
which an action is executed.
Action:
None.
C1G0233E
INVALID RECFM/LRECL/BLKSIZE SPECIFIED FOR DDNAME ddname
Reason:
The ddname specified contains invalid DCB information as related to the action being
performed. A subsequent message will contain the data set name.
Action:
Correct the request and resubmit the action. Check the DCB information on the
specified data set and correct the error.
C1G Messages
C1G0234E
ARCHIVE DDNAME ddname REQUIRES LRECL >= record size
Reason:
The ddname identified in the message contains an LRECL less than the indicated record
size. The Transfer, Restore, or Archive actions found the DCB information on the input
file contained an LRECL less than the indicated record size. A subsequent message will
contain the data set name.
Action:
Specify a valid LRECL associated with the DSNAME shown in the message text and retry
the action.
C1G0235E
ARCHIVE DDNAME ddname REQUIRES RECFM TO BE V/VB
Reason:
The ddname specified contains a DCB=RECFM= other than V or VB. When reading or
writing to an archive file with the Transfer, Restore, or Archive actions, the RECFM must
be either V or VB.A subsequent message will contain the data set name.
Action:
Specify a valid RECFM associated with the DSNAME shown in the message text and retry
the action.
C1G0236E
PROCESSING TERMINATED - ENDEVOR RC return code IS GREATER THAN OR EQUAL TO
STOP RETURN CODE return code
Reason:
The command SET STOPRC nn specified as input to the SCL run was less than the return
code for the executed action. Processing will terminate.
Action:
Correct any errors that caused the STOPRC to be invoked and retry the action.
s
C1G Messages
C1G0236S
PROCESSING TERMINATED - ENDEVOR RC return code IS GREATER THAN OR EQUAL TO
STOP RETURN CODE return code
Reason:
The command SET STOPRC nn specified as input to the SCL run was less than the return
code for the executed action. Processing will terminate.
Action:
Correct any errors that caused the STOPRC to be invoked and retry the action.
C1G0237I
[TO|FROM] ENVIRONMENT: environment name SYSTEM: system SUBSYSTEM:
subsystem TYPE: element type
Reason:
This informational message appears immediately after the action being executed is
displayed. This message indicates the FROM or TO location of the element.
Action:
None.
C1G0238E
LIBRARY TYPE NOT SUPPORTED IN THIS SYSTEM
Reason:
The CA Endevor SCM interface to Librarian and Panvalet was not installed at your site.
An attempt to access either library type through a CA Endevor SCM request produces
this message.
Action:
Contact CA Technical Support if required.
C1G Messages
C1G0239E
NO MATCH FOR element type element name IN ARCHIVE FILE ddname
Reason:
An attempt was made to restore or transfer an elements from an archive file. The
criteria specified (environment, system, subsystem, stage or type) did not match the
information found on the file.
Action:
Verify that the correct information was specified for this request. Check to make sure
the correct archive file was specified in the JCL.
C1G0240I
BEGINNING COPY TO SOURCE OUTPUT LIBRARY
Reason:
This informational message appears immediately before the source output
management processing of CA Endevor SCM begins.
Action:
None.
C1G0241I
COPY TO SOURCE OUTPUT LIBRARY COMPLETED. HIGHEST STEP RC WAS return code
Reason:
This informational message appears immediately after the completion of the source
output management. The message indicates the highest return code (RC).
Action:
None.
C1G Messages
C1G0242I
BEGINNING DELETE FROM SOURCE OUTPUT LIBRARY
Reason:
This informational message appears immediately before the delete processing from the
source output library begins.
Action:
None.
C1G0243I
DELETE FROM SOURCE OUTPUT LIBRARY COMPLETED. HIGHEST STEP RC WAS return
code
Reason:
This informational message appears immediately after the completion of the source
output management. The message indicates the highest return code (RC).
Action:
None.
C1G0244C
CANNOT COPY BACK ELEMENT AT ENV:environment nameSTG:stage id SYS:system
name SUB:subsystem name TYPE:type name
Reason:
This message appears in combination with the next message, C1G0245C.
Action:
None.
C1G Messages
C1G0245C
OCCURRENCES FOUND AT LOWER STAGE(S) WHICH DID NOT PASS THE
"WHERE"SELECTION CRITERIA
Reason:
This message appears with the previous message, C1G0244C. These messages are
issued when a Generate with copyback attempts to copyback an ineligible element.
Action:
Verify the WHERE selection criteria and the element you wish to copyback.
C1G0246I
PROCESSOR processor name LOADED FROM dsname
Reason:
Informational message. This message is issued when a processor is first loaded for
execution.
Action:
None.
C1G0247I
FOOTPRINT: ENV: environment SYS: system SBS: subsystem ELM: element TYPE: type
STG NBR: stage number
Reason:
Informational message. This message identifies the footprint of the processor that was
just loaded.
Action:
None.
C1G Messages
C1G0248I
VER: vvll DATE: date/time
Reason:
Informational message. This message identifies the version and level, date and time
portion of the footprint of the processor that was just loaded.
Action:
None.
C1G0249I
Processor JCL statement text
Reason:
Informational message. The first time a processor is loaded, each statement in the
processor JCL is printed out.
Action:
None.
C1G0250E
MEMBER NAME IS TOO LONG FOR THIS TYPE OF DATA SET
Reason:
An action was requested that involved writing an element name of greater than 8
characters to a library that only supports 8-character names.
Action:
Correct the library specification.
C1G0251E
XFER NOT ALLOWED. ENV/SYS/SUB/ELM/STG THE SAME FOR SOURCE AND TARGET
Reason:
Transfer action was requested that specified the same source and target locations.
Action:
Correct the source and/or target location specifications.
C1G Messages
C1G0252E
EXCEEDED AVAILABLE PAM I/O MODULES (C1PIPAMX)
Reason:
This message is issued when more than 16 Panvalet libraries are opened simultaneously.
Action:
Reduce the number of open libraries and resubmit the action.
C1G0253E
ERROR ON DATA SET VALIDATION FOR DDNAME ddname
Reason:
The data set indicated in the FOOTPRINT clause is not a valid data set type.
Action:
Specify a data set that is a PDS, CA Librarian, or CA Panvalet file, or a sequential data set.
C1G0254E
ERROR ON FOOTPRINT VERIFICATION FOR MEMBER
Reason:
The verification of the footprint for the member specified failed. Either the footprint
cannot be found or it contains incorrect data.
Action:
C1G0255E
OPEN FAILED DURING FOOTPRINTING FOR DDNAME ddname
Reason:
An attempt to open the data set specified failed.
Action:
C1G Messages
C1G0256C
MEMBER member-name NOT FOUND IN LIBRARY SPECIFIED
Reason:
The member just loaded cannot be found in the FOOTPRINT data set specified.
Action:
Delete the member from the environment (using the Delete action) and reload the
member using the correct FOOTPRINT library.
C1G0256E
MEMBER member-name NOT FOUND IN LIBRARY SPECIFIED
Reason:
The member just loaded cannot be found in the FOOTPRINT data set specified.
Action:
Delete the member from the environment and reload the member using the
correct FOOTPRINT library.
C1G0257E
HMASPZAP SEGMENTS NOT AVAILABLE, 5 REQUIRED
Reason:
The HMASPZAP record does not contain the required number of segments to
apply the footprint. At least 5 segments are required.
Action:
None.
C1G0258C
CAUTION: THE PROCESSOR OUTPUTS HAVE BEEN BACKED OUT FOR ELEMENT BY
PACKAGE package id
Reason:
Issued when element is retrieved, but outputs are backed out.
Action:
None.
C1G Messages
C1G0259E
NO ESD RECORD FOUND IN DATA SET SPECIFIED
Reason:
The data set specified in the FOOTPRINT clause contains no ESD record or there is no
name associated with the ESD record. At least one ESD record must exist in order for
footprinting to occur. The data set may contain invalid data.
Action:
C1G0259W
NO ESD RECORD OR ESD HAS NO NAME
Reason:
This object module contains no ESD record or the ESD entry name is blank.
Action:
None.
C1G0260E
CLOSE FAILED FOR DDNAME ddname
Reason:
An attempt to close the data set related to the DDname shown failed.
Action:
C1G0261E
STOW FAILED DURING FOOTPRINTING FOR MEMBER
Reason:
An attempt to stow the footprint in the data set directory, for this member, failed.
Action:
C1G Messages
C1G0262E
THE ELEMENT WITH TYPE type name NOT FOUND AT ENV: environment name STG:
stage id SYS: system name SBS: subsystem
name
Reason:
The element is not associated with the named type in the system/subsystem and at the
environment/stage named in the message.
Action:
Make sure that you have specified the element name correctly. Then resubmit the
request.
C1G0263E
ENV: environment name STAGE: stage id IS NOT DEFINED INCUSTOMER DEFAULTS
TABLE
Reason:
The environment and stage named in the message is not defined in the C1DEFLTS table.
Action:
Make sure you have specified the environment and stage names correctly. Define them
if necessary, and then resubmit the request.
C1G Messages
C1G0264E
THE action name ACTION CANNOT BE PERFORMED. A VALID PROCESSOR GROUP
CANNOT BE FOUND. REASON=reason code
Reason:
The action identified was not completed for the element identified because CA Endevor
SCM could not identify the appropriate processor group to be used for the action or the
processor group identified could not be located. The reason code contains one of the
following values:
4-Parameter list error.
16-Element type record was not found.
20-The NEXT PROCESSOR GROUP record was not found in the MCF.
24-Internal processing error.
32-A processor group record was not found in the MCF.
Action:
For reason codes 4, 8, 12 and 24, contact CA Technical Support. For reason code 16,
verify that the element type record associated with the element is defined in the MCF at
the target environment. For reason code 20, verify that the next processor group
identified in the processor group currently assigned to the element is defined in the next
stage of the map. For reason code 32, verify that the processor group to be assigned to
the element is defined in the MCF. Refer to the matrix titled "Impact of Actions on
Processor Group Selection" in the Action Processing chapter of the &U$ENUSR. to
determine how CA Endevor SCM selects processor groups.
C1G0265I
PROCESSOR GROUP processor group name FOR THIS ELEMENT WAS OBTAINEDFROM
text
Reason:
Informational message. The text at the end of the message identifies where the
processor group selection program found the named processor group.
Action:
None.
C1G Messages
C1G0266E
AN UNRECOVERABLE ERROR OCCURRED DURING PROCESSOR GROUP SELECTION
Reason:
An error occurred in the routine that determines the processor group that is used with
the current action. Action processing is terminated.
Action:
Review the Execution Report for any other error messages immediately preceding
C1G0266E. Follow the corrective actions indicated in those messages. If there are no
other messages, contact CA Technical Support.
C1G0267E
ENVIRONMENT/STAGE MAP RECORD WAS NOT FOUND FOR ENVIRONMENT
environment_name STAGE stage_id
Reason:
The $IMR call to locate the map information for the environment and stage identified
failed. The current processing is terminated.
Action:
Check the C1DEFLTS table used to verify that the environment specified is correctly
defined. Retry the action. If the problem persists, contact CA Technical Support.
C1G0268E
ELEMENT RECORD WAS NOT FOUND FOR ELEMENT INENV: env SYS: sys SBS: sbs
STAGE: stage
Reason:
The Master Control File definition for the element identified was not found.
Action:
Use the CA Endevor SCM display element dialog to verify the element identified is found
at the location identified.
C1G Messages
C1G0269W
ELEMENT IN ENV: environment name SYS: system name SBS: subsystem name TYPE:
type name STG: stage id NOT VALIDATED
Reason:
You executed the LIST ELEMENT command with the "build with components" clause. CA
Endevor SCM built an SCL component for a related element component which was not
valid when built into the element's component list using CONRELE.
Action:
None.
C1G0270E
THE PREVIOUS $IMR ERROR TERMINATED action_name PROCESSING
Reason:
A $IMR error occurred while performing the processing needed for the action identified.
A previous $IMR error message was issued to identify the error.
Action:
For more information, see the $IMR message that immediately precedes message
C1G0270E.
C1G0271W
"BYPASS GENERATE" WAS NOT HONORED BECAUSE THE MOVE PROCESSOR WAS
USED FOR THE TRANSFER ACTION
Reason:
The Transfer action specified the BYPASS GENERATE PROCESSOR option but the
processor used was the move processor. The move processor execution cannot be
bypassed.
Action:
None. Remove the BYPASS GENERATE PROCESSOR option to eliminate the message.
Also verify that the correct processor group is selected or verify that the correct
processor type is specified on the type record for the Transfer action.
C1G Messages
C1G0272C
THE ddname DD STATEMENT IS MISSING
Reason:
This DD statement is missing from the JCL. As a result, some of the output may be
suppressed.
Action:
If necessary, add this DD statement to the JCL and rerun the job.
C1G0272E
Reason:
A CA Endevor SCM action referred to a DD statement that either was not found in the
execution JCL or was not allocated to the TSO session. This error can also occur if a data
set is dynamically allocated and the system limit for dynamically allocated data sets has
been exceeded. Action processing is terminated.
Action:
Add the required DD statement to the JCL or allocate the DD statement to the TSO
session and reinvoke the action. If the ddname refers to a dynamically allocated data
set, SYSnnnnn, try adding DYNAMNBR=1500 to the EXEC statement.
C1G0272W
Reason:
This DD statement is missing from the JCL.
Action:
If necessary, add this DD statement to the JCL and rerun the job.
C1G Messages
C1G0273E
THE ACTION WAS TERMINATED BECAUSE OF AN ERROR READING DDNAME ddname
Reason:
An I/O error occurred reading the file identified by ddname. The Restore or
Transfer action was terminated.
Action:
Verify that the ddname identified is correctly specified in the JCL. Also refer to any error
messages that may appear in the JES job log. If the data set was created by Archive then
verify that the Archive action completed successfully.
C1G0274E
A PREVIOUS INVENTORY MGR (IMR) ERROR OCCURRED DURING THE function
FUNCTION CALL
Reason:
An internal error occurred while attempting to perform an inventory management
request. This message indicates if the problem is related to the LNAME, REGISTER, or
REMOVE function.
Action:
C1G0275I
THE "OVERRIDE SIGNOUT" OPTION IS IN EFFECT. ELEMENT IS CURRENTLY SIGNED OUT
TO userid
Reason:
The element identified was signed out to the user specified. The action specified the
OVERRIDE SIGNOUT option. This message informs the user that signout status was
overridden. Action processing proceeds normally.
Action:
None.
C1G Messages
C1G0276S
AN abend_code ABEND OCCURRED IN module_name DURING action_name
PROCESSING
Reason:
CA Endevor SCM intercepted an ABEND in the module identified while executing the
action specified. Processing is immediately terminated with a return code of 20.
Action:
Retry the action. If the problem persists then contact CA Technical Support.
C1G0277E
action PROCESSING TERMINATED BECAUSE OF THE PREVIOUS ERROR
Reason:
An unrecoverable error occurred while performing the action identified. CA Endevor
SCM stopped processing the action.
Action:
See C1MSGS1 output for any other E or S level messages and take the actions necessary
to correct that error.
C1G0277I
action PROCESSING TERMINATED BECAUSE OF THE PREVIOUS ERROR
Reason:
Informational message. Review previous messages for the details of why this action
failed.
Action:
None.
C1G Messages
C1G0278E
THE ARCHIVE RECORD SIZE (size) IS GREATER THAN THE ARCHIVE BUFFER(size)
Reason:
The length of the record that you want to write to the archive data set is greater than
the length of the archive data set buffer.
Action:
C1G0279E
ACTION BYPASSED BECAUSE OF A PREVIOUS ERROR WRITING TO DD ddname
Reason:
An error occurred in a previous List action that was writing output to the file identified.
In order to prevent subsequent errors or incorrect output processing of this List action is
bypassed.
Action:
For the previous List action error, see the C1MSGS1 data set. Correct the error and
resubmit the job.
C1G0280I
ELEMENT AT LOCATION environment/stage id/system name/subsystem name/type
name SELECTED FOR PROCESSING
Reason:
Informational message. The element was selected for processing.
Action:
None.
C1G Messages
C1G0281E
STAGE ID AND STAGE NUMBER ARE MUTUALLY EXCLUSIVE
Reason:
You have coded a WRITE SCL statement in a CONWRITE job step that specifies both a
stage ID and a stage number. These options are mutually exclusive.
Action:
Respecify the SCL with either option, but not both.
C1G0282E
PARAMETER parameter IS REQUIRED FOR THIS ACTION
Reason:
The parameter specified in the message is required for a requested action, but was
omitted from the action request.
Action:
Respecify the request, including the required parameter.
C1G0283E
PARAMETER parameter MAY NOT BE WILDCARDED
Reason:
The parameter identified in the message was specified using a wildcard. This syntax is
not valid.
Action:
Respecify the request, providing an explicit specification for this parameter.
C1G0284E
"TO DDNAME" AND "TO PROGRAM" ARE MUTUALLY EXCLUSIVE
Reason:
You have specified both a DDname and a program name as the targets for CONWRITE
output. These options are mutually exclusive.
Action:
Respecify the request with either parameter.
C1G Messages
C1G0285E
UNABLE TO DETERMINE OUTPUT DESTINATION
Reason:
CA Endevor SCM cannot determine the output destination from the CONWIN statement
provided.
Action:
Correct the CONWIN statement and resubmit the request.
C1G0286E
ATTEMPT TO LOAD I/O PROGRAM program name FAILED
Reason:
CA Endevor SCM failed to load the user program named in the CONWRITE step of the
processor.
Action:
Check the CONWRITE step of the processor, making sure that the STEPLIB specification
points to the library containing the program load module.
C1G0287I
I/O PGM MESSAGE: user-defined message text
Reason:
The message returned from the I/O program when it returns a return code of 4.
Action:
Act on the message as necessary.
C1G0287E
I/O PGM MESSAGE: user-defined message text
Reason:
The message returned from the I/O program when it returns a return code of 8.
Action:
Act on the message as necessary.
C1G Messages
C1G0288E
AN INVALID RETURN CODE, X "return code", WAS RECEIVED FROM THE USER PROGRAM
program name
Reason:
The user exit program specified in the TO PROGRAM statement in CONWRITE returned
the return code identified. This return code is not expected by CONWRITE. This
terminated processing of the current WRITE ELEMENT statement.
Action:
Contact CA Technical Support to identify why the user program is returning the
incorrect return code. Correct the user program, and then resubmit the action.
C1G0289E
ATTEMPT TO COMMUNICATE BETWEEN TASKS HAS FAILED WITH CODE = returncode
Reason:
Internal error.
Action:
C1G0290E
ALLOC=/MONITOR=value WAS INCORRECTLY SPECIFIED IN PROCESSOR
processor_name
Reason:
The ALLOC= or MONITOR= processor keyword contained an incorrect value in the
processor identified in the message. The valid specifications are
ALLOC=LMAP|PMAP|STD and MONITOR=COMPONENTS.
Action:
Correct the named processor and re-execute the action.
C1G Messages
C1G0291E
TYPE type name MUST HAVE AN LRECL OF AT LEAST 80 TO SUPPORT RECFM=U (LOAD
MODULES)
Reason:
CA Endevor SCM detected that the element to be added or updated was a load module.
The type definition identified for the element specified a record length of less than 80.
The type definition record length must be at least 80 to support load modules.
Action:
Correct the named type definition and re-execute the Add or Update action.
C1G0292E
PROCESSOR GROUP group name USES THE MOVE PROCESSOR FOR A TRANSFER BUT
THE ELEMENT NAME HAS CHANGED
Reason:
The named processor group specifies that the move processor is used by the Transfer
action. The Transfer action also specifies that the FROM element is renamed at the TO
location. This combination is not supported by CA Endevor SCM. If you want to use the
move processor on the Transfer action, then the FROM element name cannot change.
Action:
Either update the processor group definition so that the generate processor is used for
the Transfer action or do not rename the FROM element at the TO location.
C1G0293E
MEMBER NOT FOUND IN DATA SET FOR ADD/UPDATE ACTION
Reason:
The specified input member used for the Add or Update action was not found in the
data set identified.
Action:
Verify that the FROM data set and member are correctly specified on the Add or Update
action. Resubmit the action request after the correct data set name and/or member
name are identified.
C1G Messages
C1G0293W
MEMBER NAME TRUNCATION OCCURRED
Reason:
An element with a name greater than eight characters was added to an element type
with a PDS Source Output Library. The element name was truncated to eight characters
when written to the Source Output Library.
Action:
You may want to verify that elements with names of eight characters or more have not
been written to the PDS source Output Library.
C1G0294E
LISTING MEMBER COULD NOT BE FOUND
Reason:
The CONLIST processor program did not locate the specified listing member in the
specified data set. The listing data set is identified by the C1LLIBI DD statement. This
message is issued when the Copy or Print parameters are specified.
Action:
Verify that the listing member is present. You may have to regenerate the
element to recreate the listing.
C1G0294C
LISTING MEMBER COULD NOT BE FOUND
Reason:
The CONLIST processor program did not locate the specified listing member in the
specified data set. The listing data set is identified by the C1LLIBI DD statement. This
message is issued when the DELETE parameter is specified.
Action:
None is necessary. The delete function is bypassed but a return code of 4 is issued.
C1G Messages
C1G0295C
BYPASSING DELETE BECAUSE MEMBER DOES NOT EXIST IN DATA SET
Reason:
CA Endevor SCM attempted to delete a member from the data set, but the member
does not exist. Processing continues.
Action:
None. You may want to verify that the names of the data sets in the delete processor
are correct.
C1G0295W
BYPASSING DELETE BECAUSE MEMBER DOES NOT EXIST IN DATA SET
Reason:
CA Endevor SCM attempted to delete a member from a data set, but the member does
not exist. Processing continues.
Action:
None. You may want to verify that the names of the data sets in the delete processor
are correct.
C1G0296E
THE OUTPUT DATA SET LRECL (record length), IS LESS THAN THE TYPE DEFINITION
LRECL OF (type length)
Reason:
The user-specified data set on the Retrieve action or the output data set specified with
the data set specified with the CONWRITE utility has a record length that is less than the
element record length as defined in the element type record. CA Endevor SCM will not
write the element to the output data set to avoid potential truncation of the element
source.
Action:
Select another data set for the retrieve action or increase the LRECL of the current data
set to avoid truncation of the output file.
C1G Messages
C1G0296W
THE OUTPUT DATA SET LRECL (record length), IS LESS THAN THETYPE DEFINITION
LRECL OF (type length)
Reason:
The user-specified data set on the Retrieve action or the output data set specified with
the data set specified with the CONWRITE utility has a record length that is less than the
element record length as defined in the element type record. CA Endevor SCM writes
the element to the output data set but the output records may be truncated.
Action:
If the element records can be truncated without causing subsequent problems, then the
warning message can be ignored. Otherwise, change the output data set to one that
supports the entire output record length.
C1G0297I
ELEMENT SUCCESSFULLY PROCESSED BY USER PROGRAM program name
Reason:
Informational message. CONWRITE successfully processed the element, and passed it to
the user program specified in the WRITE ELEMENT TO PROGRAM statement.
Action:
None.
C1G0298E
AN OUTPUT DDNAME WAS NOT DEFINED IN THE PROCESSOR FOR CONWRITE
PROCESSING
Reason:
The current processor step executes the CONWRITE utility and CONWRITE did not locate
the output DD name. CONWRITE immediately stopped execution.
Action:
Contact CA Technical Support to update the current processor with the appropriate
CONWRITE output DD statement. For information on defining the CONWRITE output DD
statement, see the Extended Processors Guide.
C1G Messages
C1G0299I
THE CONWRITE PARAMETER WAS NOT SPECIFIED OR IS INVALID. DEFAULTINGTO
"EXPINCL(N)"
Reason:
The current processor step executes the CONWRITE utility but the EXEC statement did
not contain a PARM= statement or the PARM= statement was invalid. CONWRITE
processing continues without expanding INCLUDE statements.
Action:
If the default value of EXPINCL(N) is not appropriate, then contact CA Technical Support
to update the processor. If the default value is appropriate then ignore the message.
C1G0300S
$COMP3 - INVALID REQUEST CODE
Reason:
Internal error.
Action:
C1G0301E
RESULT AREA NOT LARGE ENOUGH FOR COMPRESSION RESULTS
Reason:
Internal error. Variable blocked target file's record length is too small for the record
being written.
Action:
Copy current file over to a new data set with a VB record length of 259 or greater.
C1G0302E
RESULT AREA NOT LARGE ENOUGH FOR DECOMPRESSION RESULTS
Reason:
Internal error.
Action:
C1G Messages
C1G0303S
$COMP3- TBL#RUTN - INVALID REQUEST CODE
Reason:
Internal error.
Action:
C1G0304E
UNABLE TO INITIALIZE STORAGE
Reason:
Internal error.
Action:
C1G0305E
UNABLE TO ACQUIRE STORAGE
Reason:
Internal error.
Action:
C1G0306E
$COMP3 - REQUEST MISSING STORAGE ANCHOR ADDRESS
Reason:
Internal error.
Action:
C1G Messages
C1G0307E
$COMP3 EYE-CATCHER IS MISSING FROM FILE TO BE DECOMS
Reason:
Internal error.
Action:
C1G0308I
$COMP3 COMPRESSION RESULTS: IN=number of bytes, OUT=number of bytes,
RATIO=ratio:1
Reason:
Used for diagnostic purposes.
Action:
C1G0309I
$COMP3 DECOMPRESSION RESULTS: IN=number of bytes, OUT=number of bytes,
RATIO=1:ratio
Reason:
Used for diagnostic purposes.
Action:
C1G0310E
CONWRITE PROCESSING OF THIS ELEMENT TERMINATED BECAUSE OF A $SMRERROR
Reason:
$SMR returned an unexpected return code while CONWRITE was writing the identified
element. This terminated CONWRITE processing.
Action:
For any additional error messages and perform the corrective action identified in the
messages, see the CA Endevor SCM execution log. If there are no additional messages,
C1G Messages
C1G0311I
CONWRITE OUTPUT DATA SET IS SEQUENTIAL. THE TO"MEMBER" NAME IS IGNORED
Reason:
The WRITE ELEMENT statement in CONWRITE contained a TO MEMBER keyword. The
output data set identified is a sequential data set. CONWRITE will write the element but
ignore the MEMBER statement.
Action:
If the output data set is supposed to be a partitioned data set, then contact CA Technical
Support to update the processor definition. If the output data set is supposed to be a
sequential data set, then no action is necessary.
C1G0312E
A CONWIN PARSE ERROR OCCURRED. THE REMAINING CONTROL STATEMENTSWILL
BE SYNTAX CHECKED ONLY
Reason:
CONWRITE detected a syntax error in CONWIN DD statement input. This terminated
processing of This terminated processing of the current statement. If any additional
WRITE ELEMENT statements remain in the CONWIN DD statement, they are
syntax-checked but NOT executed. The CONWRITE step terminates with a return code
of 12.
Action:
Contact CA Technical Support to correct the WRITE control statements that have the
error.
C1G0313W
THE OUTPUT DATA SET LRECL OF (record length), IS GREATER THAN THE TYPE
DEFINITION LRECL OF (type length)
Reason:
The user-specified data set on the RETRIEVE action or the output data set specified with
the CONWRITE utility has a record length that is larger than the record length associated
with the element type record. When CA Endevor SCM writes the element to the data set
it may pad the output records with spaces.
Action:
If the output records can be padded with spaces with no adverse affects then the
message can be ignored. Otherwise, specify an output data set that has a record length
of sufficient size to hold the element records.
C1G Messages
C1G0314E
THE INPUT DATA SET LRECL OF (record length), IS GREATER THAN THE TYPE
DEFINITION LRECL OF (type length)
Reason:
The user specified data set on the Add or Update action has a record length that is
larger than the record length associated with the element type record. Adding or
updating the element may result in truncated records. The action is terminated.
Action:
Add or update the element from a data set that is at least as large as the type record
length identified in the message.
C1G0315W
DATA SET IS A [PANVALET/LIBRARIAN] DATA SET. TYPEDEFINITION LRECL OF (type
length) SHOULD BE 80
Reason:
The Add or Update action specified either a CA Librarian or CA Panvalet data set as the
FROM location but the element type definition indicated that the element length is not
80. 80 is the standard size of members that are stored in CA Panvalet or CA Librarian
data sets.
Action:
Verify that the element type record has the correct value for the maximum record
length. If the value is correct you can ignore the message. Otherwise, update the
element type record with the correct value.
C1G0316E
COMPLIST AND EXPAND INCLUDES OPTIONS ARE MUTUALLY EXCLUSIVE
Reason:
Both the COMPLIST and EXPAND INCLUDES options were specified with the CONWRITE
command
Action:
Remove either the COMPLIST or the EXPAND INCLUDES option from the CONWRITE
command and reenter the command.
C1G Messages
C1G0317I
COMPONENT LIST FOR ELEMENT AT LOCATION environment name/stage id/system
name/subsystem name/type name SELECTED FOR PROCESSING
Reason:
The CONWRITE command is writing the component list for the specified element.
Action:
None.
C1G0318E
CONWRITE PROCESSING OF COMPONENT LIST FOR THIS ELEMENTTERMINATED
BECAUSE OF A $SMR ERROR
Reason:
The CONWRITE command processing of the component list terminated.
Action:
Read the following SMR message to find out more about the problem.
C1G0319W
OUTPUT DATA SET LRECL record length IS BELOW THE MINIMUMALLOWABLE LRECL
SIZE OF record length
Reason:
The user output data set specified with the CONWRITE utility when writing component
list records has a record length that is less than the minimum component list record
length. CA Endevor SCM writes the component list records to the output data set but
the output records may be truncated.
Action:
If the component records can be truncated without subsequent problems, then you can
ignore the message. Otherwise, change the output data set to one that supports the
entire output record length
C1G Messages
C1G0320E
CONCOMP1 COMPRESSION EXCEEDED MAXIMUM ALLOWABLE COMPRESSED
RECORDSIZE (255)
Reason:
Internal error.
Action:
C1G0321E
"MEMBER" AND "HFSFILE" SYNTAX ARE MUTUALLY EXCLUSIVE
Reason:
Both the MEMBER and HFSFILE parameters are coded in the SCL. They are mutually
exclusive.
Action:
Determine if you are dealing with a PATH/HFS file or a DATA SET and MEMBER. Correct
the SCL accordingly.
C1G0322S
FAILURE TO OPEN FILE file name
Reason:
Unable to open JOURNAL file.
Action:
Review previous CA Endevor SCM messages and the JES messages for details.
C1G Messages
C1G0323W
ELEMENT IS NOT REFERENCED IN ACMQ
Reason:
The element specified in the PRINT EXPLODE action is not referenced in ACMQ. There
can be two possible reasons for this.
The specified element does not exist in the CA Endevor SCM inventory.
An existing element does not have any input components and the specified instance
if the element is not used as an input component in any other component list.
ACMQ only references input components.

Action:
Verify that the element name and inventory location are correctly spelled and that the
element has a component list with input components.
C1G0330E
BLDL RETURNED AN "OUTSIDE EXTENT" CONDITION FOR MBR member name IN data
set name
Reason:
The BLDL system service returned a value indicating that the identified member was
located outside the used extents of the data set identified. This error may occur if the
data set is physically damaged or if the data set directory is managed by an external
directory optimizer.
Action:
If the data set is physically damaged, delete and reallocate the data set. If the data set is
managed by an external directory optimizer, have your systems programmer either
remove the data set from the control of the optimizer or refresh the optimizer's control
information.
C1G Messages
C1G0331E
THE action name ACTION FAILED BECAUSE THE "TO" INFORMATION FAILED
VALIDATION
Reason:
The SCL for the identified action did not specify complete information on the TO
statement. CA Endevor SCM, therefore, used information from the FROM statement to
complete the request. The composite TO information did not pass CA Endevor SCM
validation criteria. The message immediately preceding C1G0331E indicates the reason
for the failure.
Action:
For the appropriate corrective action, see the message immediately preceding
C1G0331E.
C1G0332W
THE ELEMENT WAS NOT PRINTED BECAUSE THE SELECTION CRITERIAWERE NOT MET
Reason:
The element identified was not printed because the selection criteria specified on the
PRINT command was not met. For more information on the criteria that was not met,
see the PRINT TO location.
Action:
If you want to print the element, respecify the selection criteria and resubmit
the action.
C1G0333W
PROCESS MANAGEMENT MAY HAVE ALREADY BEEN PERFORMED FOR THIS ELEMENT
Reason:
The Move action determined that the appropriate processor may have already executed
for this element. The message is issued when a failed Move action is restarted, or when
a Move action with BYPASS ELEMENT DELETE is restarted.
Action:
None. The target location processor for the element processed by the Move action is
not executed.
C1G Messages
C1G0334W
THE TRANSFER ACTION HAS RESTARTED AT THE DELETE SOURCE ELEMENT STEP
Reason:
The Transfer action determined that the target location processor for the element being
transferred does not have to execute. The Transfer action begins processing at the
element delete step. This message is issued when a failed Transfer action is restarted.
Action:
None. The target location processor for the element processed by the Transfer action
does not execute. CA Endevor SCM processing restarts at the element delete step.
C1G0335E
UNABLE TO ACCESS MULTI-VOLUME DATA SET
Reason:
Unable to access a data set that resides on multiple volumes.
Action:
Review the previous CA Endevor SCM messages and the JES messages or possible
reasons.
C1G0336E
COMPONENT LIST FOR ELEMENT AT LOCATION inventory location HAS NO
COMPONENT LIST
Reason:
A component list for this element does not exist at this inventory location.
Action:
You may need to regenerate the element to build the component list.
C1G Messages
C1G0336W
COMPONENT LIST FOR ELEMENT AT LOCATION inventory location HAS NO
COMPONENT LIST
Reason:
A component list for this element does not exist at this inventory location.
Action:
You may need to regenerate the element to build the component list.
C1G0337E
CONRELE WAS REQUESTED, BUT ASCM IS SET TO N. TO USE CONRELE, ASCMMUST BE
SET TO Y
Reason:
A user-invoked CONRELE to relate a user component to the component list. This request
fails because ASCM was set to N. Component data cannot be added to a non-existent
component list.
Action:
In order to generate component lists, ASCM must be active. Make sure that ASCM was
a purchased CA Endevor SCM option.
C1G0338E
C1PRINT FILE MUST HAVE LRECL=133
Reason:
The incorrect LRECL was specified for the C1PRINT ddname in a PRINT ELEMENT action.
Action:
Specify LRECL=133 for the C1PRINT and resubmit the request.
C1G0338W
Element has no input components
Reason:
ACMQ query indicates that this element references no other elements.
Action:
None.
C1G Messages
C1G0339E
A CONWIN PARSE ERROR OCCURRED: NO ACTION REQUESTS WERE GENERATED,
MISSING ENDING PERIOD
Reason:
The ending period was not found in the CONWIN data set.
Action:
Verify the SCL and correct the syntax. Make sure there is an ending period after every
SCL statement.
C1G0340I
OPTION AUTOGEN IN USE, ALL ACTIONS WILL BE RESOLVED BASED ON CURRENT
INVENTORY CONTENTS
Reason:
Informational message. This message is issued when one of more of the actions contains
the AUTOGEN option. It notifies you that all actions are expanded (name masking
resolved) prior to any action being executed.
Action:
None.
C1G0340E
THE LISTnn DD STATEMENT IS MISSING
Reason:
The CONLIST utility used with parameter STORE or PRINT requires at least one LISTnn
DD statement.
Action:
Specify one or more LISTnn DD statements as an input for the CONLIST utility.
C1G Messages
C1G0341I
AUTOGEN: autogen trace information
Reason:
Informational message. This message is issued when the EN$TRAUT DD statement is
coded in the batch job SCL. It indicates this message contains trace information.
Action:
None.
C1G0342S
OPTION AUTOGEN MAY NOT BE USED, ACMQ HAS NOT BEEN PURCHASED
Reason:
The AUTOGEN Option cannot be specified on actions if your site has not purchased the
Endevor Automated Configuration Manager add-on.
Action:
Remove the AUTOGEN action from all the actions or purchase the ACM add-on.
C1G0343I
ELEMENT element-name / type / system / subsystem WILL BE GENERATED [DUE TO
SPAN]
Reason:
Informational message. This message is issued when the AUTOGEN option or an
AUTOGEN SPAN option is in effect. It indicates that this using element is being
generated on behalf of the component element listed in message C1G0345I.
Action:
None.
C1G Messages
C1G0344I
ELEMENT element-name / type / system / subsystem IS ALREADY BEING GENERATED
Reason:
Informational message. This message is issued when AUTOGEN is in effect. It indicates
that this using element is already in the list of elements to be generated and does not
need to be added again. This message is issued when the EN$TRAUT DD statement is
coded in the batch job SCL.
Action:
None.
C1G0345I
PROCESSING AUTOGEN FOR ELEMENT element-name / type. TARGET IS
environment/system/subsystem/stage
Reason:
Informational message. This message is issued when AUTOGEN is in effect. It indicates
the target location of the generate action.
Action:
None.
C1G0346S
ERROR ON $ACMQ FOR AUTOGEN, R15=return-code
Reason:
Internal error. The call to ACM failed.
Action:
C1G0347S
ERROR OBTAINING STORAGE FOR AUTOGEN, R15=return-code
Reason:
Internal error. Unable to obtain storage necessary to build the chain of elements.
Action:
C1G Messages
C1G0348S
ERROR QUEUING GENERATE FOR AUTOGEN, R15=return-code
Reason:
Internal error. Problem writing out the ARQ.
Action:
C1G0349S
ERROR RESOLVING ELEMENTS, R15=return-code
Reason:
Internal error. Generic keyed read for element failed.
Action:
C1G0350S
STORAGE ERROR CHAINING REQUEST FOR AUTOGEN, R15=return-code
Reason:
Internal error. Unable to add entries to the storage chain of elements.
Action:
C1G0351S
STORAGE/MAP/ETR ERROR DURING AUTOGEN MAP CHECK, R15=return-code
Reason:
Internal error. IMR MAP or ETR call failed.
Action:
C1G Messages
C1G0352W
ELEMENT element-name / type / system / subsystem BYPASSED; SYS/SUB NOT
DEFINED AT TARGET
Reason:
Warning message. This message is issued when one of the Autogen Span action options
is in effect. This element was selected as a using element for the component listed in
message C1G0345I, but the using elements system, subsystem, or both do not exist at
the target environment. The using element was not generated.
Action:
Either leave the using element un-generated, or create a generate or transfer request
for this element that has a valid target system and subsystem for the target
environment.
C1G0353E
ELEMENT element-name / type / system / subsystem BYPASSED; $IMR ERROR FOR
TARGET LOCATION
Reason:
Internal error. This message is issued when one of the Autogen Span action options is in
effect. The call to IMR failed when trying to verify the target location for the using
element built on behalf of the component element listed in message C1G0345I. The
using element was not generated.
Action:
Either leave the using element un-generated, or create a generate or transfer request
for this element that has a valid target system and subsystem for the target
environment.
CiG0400I
NEW VERSION PARM IGNORED FOR UPDATE ACTION
Reason:
Action:
None.
C1G Messages
C1G0450E
AN IMR ERROR OCCURRED IN ROUTINE rtn-name, SEE PREVIOUS MESSAGE FOR
DETAILS.
Reason:
An internal inventory management error occurred in the routine specified in this
message. See the previous message for details.
Action:
If you cannot resolve the problem, contact CA Technical Support.
C1G0451E
DURING action ON A SRC-LESS ELEMENT, THE ASSOCIATED SOURCE WAS NOT FOUND.
Reason:
During an action, a sourceless element was encountered but no associated sourced
element existed upstream from the sourceless element.
On an Add action, the upstream element is sourceless and no sourced element

upstream from it exists along the route.
On an Update action, the target location has a sourceless element and no sourced
element upstream could be found.
On a Generate, Retrieve or Move action, the source location is a sourceless element

and no sourced element upstream could be found.
Action:
On an Add or Update, you may want to delete the sourceless element upstream from
the actions target location then re-submit the job. The Generate, Retrieve, and Move
cannot be executed, because the source for the element could not be found. You may
want to delete these sourceless elements.
C1G Messages
C1G0452E
DURING action ON A SRC-LESS ELEMENT, THE LL TSTAMP IS DIFFERENT ON NEXT SRC
ELEMENT.
Reason:
During a Move or Update action, the source location contains a sourceless element and
the last level timestamp between the sourceless element and the next sourced element
upstream is not the same. When this condition occurs, the outputs at the source
location created by a Generate Nosource action are not current with the sourced
element up the map.
Action:
Either re-generate the action at the source location and re-submit the job, or delete the
sourceless element. If the action was an Update, change it to an Add before
re-submitting the job.
C1G0453E
LL TSTAMP BETW SRC AND TGT ELEMENT IS DIFFERENT ON A action OF A SRC-LESS
ELEMENT.
Reason:
On a Move action when an element exists at the target and the source location contains
a sourceless element, the last level timestamps between these two locations are not
equal. When this condition occurs, the outputs at the source location created by a
Generate Nosource action are not current with the target element.
Action:
Delete the sourceless element at the source location or re-generate the element at the
source location.
C1G0454W
ON A action OF A SRC-LESS ELEMENT, THE LL TSTAMP IS DIFFERENT ON NEXT SRC
ELEMENT.
Reason:
On a Retrieve of a sourceless element, the associated source up the map does not have
the same last level timestamp. The source from up the map is still retrieved.
Action:
None.
C1G Messages
C1G0455E
action ACTION DOES NOT SUPPORT SRC-LESS ELEMENT.
Reason:
The Transfer and Archive actions and Unload Transfer and Copy actions cannot be used
on sourceless elements.
Action:
None.
C1G0456I
PRINT type ACTION DOES NOT SUPPORT SRC-LESS ELEMENTS.
Reason:
Print Browse, Change, History, and Summary do not support sourceless elements.
Action:
None.
C1G0457E
ELEMENT CANNOT BE ARCHIVED AND DELETED AT
env-name/stgid/sys-name/sbs-name/type-name.
Reason:
A sourced element on the Archive action supports a previous mapped sourceless
element and cannot be deleted.
Action:
You can Archive the element if you use the Bypass Element Delete option.
C1G Messages
C1G0458E
SRC-LESS ELEMENT EXISTS PRIOR TO THIS LOCATION.
Reason:
A sourced element on a Delete or Archive action supports a previous mapped sourceless
Action:
If you still want to delete the sourced element, you need to delete the sourceless
element first. You can still Archive the element if you use the Bypass Element Delete
option.
C1G0459E
ELEMENT CANNOT BE TRANSFERRED AND DELETED AT
Reason:
Sourced element on the Transfer action supports a previous mapped sourceless element
and cannot be deleted.
Action:
You may Transfer the element if you use the Bypass Element Delete option.
C1G0460E
ELEMENT CANNOT BE DELETED AT env-name/stgid/sys-name/sbs-name/type-name.
Reason:
A sourced element on the Delete action supports a previous mapped sourceless
Action:
You will need to delete its dependent sourceless element if you still want to delete this
element.
C1G Messages
C1G0461E
ON A action, THE ASSOCIATED SOURCE FOR THE SRC-LESS TGT ELEMENT WAS NOT
FOUND.
Reason:
On a Move or Transfer action, the target location contains a sourceless element and its
associated sourced element was not found upstream from it.
Action:
You may want to delete the sourceless element at the target location and then retry the
action.
C1G0462E
THE ASSOCIATED SOURCE FOR THE SRC-LESS TGT ELEMENT HAS A DIFFERENT LL
TSTAMP.
Reason:
On a Move or Transfer action, the target location contains a sourceless element and its
associated sourced element found upstream from it has a different last level timestamp.
This means that the sourceless element at the target was generated with different
source than the found element.
Action:
You may want to delete the sourceless element at the target location and then retry the
action.
C1G0463E
ELEMENT IS OUT-OF-SYNC WITH ELEMENT AT
Reason:
On a Move or Transfer action, the target contains a sourceless element and its
associated source upstream from it is out-of-sync with the actions source.
Action:
Resolve the differences between the source and the element associated with the target.
If you want to override the out-of-sync condition, specify the SYNC option and retry the
action.
C1G Messages
C1G0464E
ON A action OF A SRC-LESS ELEMENT, THE LL TSTAMP IS DIFFERENT FROM THE
ELEMENT UPSTREAM.
Reason:
During a Move action on a sourceless element, the last level timestamp is different from
that of the element upstream.
Action:
Re-generate the sourceless element and then perform the Move action, or you may
want to abandon the Move and simple delete the sourceless element.
C1G0465E
ELEMENT UPSTREAM FROM THE TGT IS SRC-LESS. ITS ASSOCIATED SOURCE IS NOT
FOUND.
Reason:
On a Move or Transfer action, no element exists at the target, and although an
upstream sourceless element was found, its associated sourced element is missing.
Action:
You may want to delete the sourceless element upstream from the target location and
then retry the action.
C1G0466E
ELEMENT UPSTREAM FROM THE TGT IS SRC-LESS. ITS SRC ELEMENT HAS A DIFFERENT
LAST LVL TSTAMP.
Reason:
On a Move or Transfer action, no element exists at the target. An upstream sourceless
element was found, but its last level timestamp is different than its associated sourced
element.
Action:
You may want to delete the sourceless element upstream from the target location and
then retry the action. Alternatively, you could re-generate the sourceless element and
retry the action.
C1G Messages
C1G0467E
ERROR OCCURRED WHILE LOOKING FOR SOURCE FOR ELEMENT AT
Reason:
Refer to previous error messages that may have been logged.
Action:
If you cannot determine the problem contact CA Technical Support.
C1G0468E
NO SOURCE FOUND FOR TGT SRC-LESS ELEMENT.
Reason:
During a PDM add to CA Endevor SCM, the supporting source for the target location
could not be found. The target location contains a sourceless element.
Action:
If you want to continue the process, you will need to delete the sourceless element if
you are not able to recover the missing associated sourced element.
C1G0469E
LL TSTAMP ON TGT SRC-LESS ELEMENT IS DIFFERENT ON THE NEXT SRC ELEMENT.
Reason:
During a PDM add to CA Endevor SCM, the target location has a sourceless element and
its supporting source for the target location has a different last level timestamp.
Action:
You can delete the sourceless element or re-generate it before performing the PDM
action again.
C1G Messages
C1G0470E
NO SOURCE FOUND FOR SRC-LESS ELEMENT UPSTREAM FROM TGT LOCATION.
Reason:
During a PDM add to CA Endevor SCM, a sourceless element was found upstream from
the target location and its supporting sourced element could not be found.
Action:
If you want to continue the process, you will need to delete the sourceless element if
you were not able to recover the missing associated sourced element.
C1G0471E
LL TSTAMP ON SRC-LESS ELEMENT UPSTREAM FROM TGT IS DIFFERENT ON THE NEXT
SRC ELEMENT.
Reason:
During a PDM add to CA Endevor SCM, a sourceless element was found upstream from
the target location and its supporting source has a different last level timestamp.
Action:
You can delete the sourceless element or re-generate it before performing the PDM
action again.
C1G0472E
ROOT ELEMENT CANNOT BE A SRC-LESS ELEMENT.
Reason:
The PDM ROOT specification must be on a sourced element, not a sourceless element.
Action:
Specify the sourced element on the ROOT specification.
C1G Messages
C1G0473E
SOURCE NOT FOUND FOR SRC-LESS ELEMENT AT
Reason:
While processing a CONWRITE request against a sourceless element, its associated
sourced element was not found.
Action:
You will need to determine why the sourced element is missing and take corrective
action.
C1G0474E
SRC LL TSTAMP IS DIFFERENT ON SRC-LESS AT
Reason:
While processing a CONWRITE request against a sourceless element, the last level
timestamp was found to be different on its associated sourced element.
Action:
You may want to re-generate the sourceless element.
C1G0475W
SOURCELESS ELEMENT SKIPPED BECAUSE IT CANNOT BE ARCHIVED/TRANSFERRED
Reason:
During the wildcard expansion, sourceless elements were encountered. Archive and
transfer actions do not support sourceless elements, so these elements are skipped.
Action:
None
C1G Messages
C1G0500E
INTERNAL ERROR IN C1BM4200: ERR1RUTN INCORRECTLY INVOKED
Reason:
Internal error.
Action:
C1G0501I
ELEMENT RESERVED FOR PACKAGE package id
Reason:
Informational message - issued when an element is reserved to a package during
package cast.
Action:
None
C1G0502I
ELEMENT HAS BEEN UNASSIGNED FROM PKG package id - PACKAGENO LONGER
ACTIVE
Reason:
Informational message - issued when a reserved element is referenced by a package
which is being cast or an element action and the package which reserved the element
no longer exists or is not in a valid state to reserve the element. The element is
unassigned and the package cast or element action is permitted to continue.
Action:
None
C1G Messages
C1G0503C
ELEMENT WAS RESERVED BY PKG package id, DUE TO EMERGENCY STATUS, RESERVE
OVERRIDDEN
Reason:
Caution message - issued when an emergency package which contains a reference to a
reserved element is being cast. The element is unassigned and the package cast is
permitted to continue.
Action:
None
C1G0503E
ELEMENT IS UNAVAILABLE - RESERVED BY PKG package id
Reason:
Error message - issued when a reserved element is referenced by a package which is
being cast or referenced an element action. The cast or action is terminated.
Action:
None
C1G0504E
[PCF or MCF] ERROR error text
Reason:
Error message - issued when an I/O error occurred while attempting to access the
master or package control file.
Action:
The information contained in the error text portion of the message should provide
information as to how to resolve the problem.
C1G Messages
C1G0505E
ELEMENT IS CURRENTLY IN USE BY ANOTHER JOBOR USER - TRY
AGAIN LATER
Reason:
Error message - During package cast processing an exclusive element access is required.
This message is issued when another JOB or USER has access to an element referenced
by the package or when the CA Endevor SCM UNLOAD utility is being used to backup the
environment and system.
Action:
Retry cast.
C1G0506I
ENV: environment SYS: system SBS: subsystem STGID: stage id TYPE:
type
Reason:
Informational message. Provides the CA Endevor SCM inventory location for the
element referenced by the preceding message.
Action:
None
C1G0507C
ELEMENT IS REFERENCED BY MULTIPLE ACTIONS WITHIN THIS PACKAGE
Reason:
Caution message. There is more than one action in this package that is referencing the
same element. Review the actions and determine which action should process this
element.
Action:
Modify the package to correct the problem.
C1G Messages
C1G0507E
Reason:
There is more than one action in this package that is referencing the same element.
Review the actions and determine which action should process this element.
Action:
C1G0507W
Reason:
There is more than one action in this package that is referencing the same element.
Review the actions and determine which action should process this element.
Action:
C1G0508S
INTERNAL ERROR IN FUNCTION module subroutine error description.
Reason:
An unexpected internal error occurred in module subroutine. The error is described in
error description.
Action:
C1G Messages
C1G0510E
USS function ERROR - RC=nnnn, REASON CODE=nnnn, RETURN VALUE=nnnn,
error-literal
Reason:
One of the USS functions failed. The error literal, which only appears for some of the
more common return codes, should give you a good indication of the reason. You can
also check the return codes and reason codes in the Unix Systems Services Messages
and Codes documentation.
Action:
If the error-literal or the USS Messages and Codes do not help, contact CA Technical
Support.
C1G0511E
C1IO1FUN, function, IS UNKNOWN TO C1UIO000
Reason:
Internal error. The USS I/O program received a request. The function code is invalid.
Action:
C1G0512E
C1UI0000 ERROR - DSN NOT TOKENIZED
Reason:
Internal error. The first four characters of the DDNAME passed to the USS I/O do not
contain the characters "/LNS", indicating an HFS file.
Action:
C1G Messages
C1G0513E
C1UI0000 LOGIC ERROR
Reason:
Internal error. A second IOB exists, but the pointer is zero.
Action:
C1G0516E
LENGTH ERROR IN USS FOOTPRINT FILE
Reason:
Internal error. The length of the footprint segment does not match the calculated size.
Action:
C1G0517E
USS WRITE ERROR. RC=return code, REASON CODE=reason code, RETURN
VALUE=return value
Reason:
Internal error. An attempt to write the output buffer failed.
Action:
C1G Messages
C1G0518E
THE LENGTH OF A REC IN THIS FILE EXCEEDS THE TYPEDEF REC LENGTH OF length
Reason:
While reading records from an HFS data set, a record length error was detected. The
length of a record in this file exceeds the length specified on the type definition. The
type definition record length value is displayed in this message. The name of the path
and file in error are displayed in the error log along with this message.
Action:
Increase record length value on the element type definition and rerun the action. If the
problem recurs, it may be due to an internal processing error (a storage buffer may
exceed 32,000 bytes or the RDW is invalid); contact CA Technical Support.
C1G0519E
LOAD OF USS ROUTINES UNSUCCESSFUL
Reason:
Internal error. Unable to load the USS routines.
Action:
C1G0520E
FIND MEMBER FUNCTION BUT MEMBER NAME IS BLANK
Reason:
Internal error. A request to locate an HFS file was made, but the file name is blank.
Action:
C1G0521E
HFS DELTA LIBRARIES ARE NOT SUPPORTED. TYPE DEFINITION IS INVALID
Reason:
Delta libraries cannot be HFS files.
Action:
Modify the type definition to correct this problem.
C1G Messages
C1G0522E
SOURCE/TARGET OR BASE PATH DOES NOT EXIST
Reason:
The source/target or base path specified in the action does not exist.
Action:
Verify that the path name is correct.
C1G0546E
UNIX initusp func failed for userid SAF RC return code, RACF RC return code, RACF
REAS reason code
Reason:
CA Endevor SCM attempted to establish the UNIX security context for the userid by
issuing the initusp callable service. The call failed with the SAF return code, RACF return
code, and RACF reason code shown in the message. See accompanying message
C1G0549I for more information. CA Endevor SCM will be unable to access CA Endevor
SCM managed UNIX files (base directory files, include library files, and source output
files.)
Action:
Contact your security administrator.
C1G0547W
UNIX deleteUSP func failed for userid SAF RC return code, RACF RC return code,
RACF REAS reason code
Reason:
CA Endevor SCM attempted to remove the UNIX security context for the userid by
issuing the deleteUSP callable service. The call failed with the SAF return code, RACF
return code, and RACF reason code shown in the message. See the accompanying
message C1G0549I for more information. Because CA Endevor SCM was in the process
of terminating when this error occurred, all CA Endevor SCM element actions have
completed.
Action:
Contact your security administrator.
C1G Messages
C1G0548E
Unable to dub address space reason text
Reason:
CA Endevor SCM attempted to dub the address space as a UNIX process by issuing a
UNIX callable service, in this case the getUID callable service. The call failed because of
the reason specified in the message. See the accompanying message C1G0549I for more
information. CA Endevor SCM will be unable to access CA Endevor SCM managed UNIX
files (base directory files, include library files, and source output files.)
Action:
Contact your CA Endevor SCM administrator.
C1G0549I
text
Reason:
This message contains additional data that relates to a CA Endevor SCM UNIX error
message. The text displays the UNIX service call, return codes (SAF return code, RACF
return code, and RACF reason code) and a brief explanation of the error.
Action:
See the Action: associated with the error message that precedes this message in the
C1MSGS1 report.
C1G0565E
UNABLE TO ACCESS UNIX FILES
Reason:
This message occurs if the user had requested alternate id protection for CA Endevor
SCM managed UNIX files (base, source output and include files), but an initial UNIX call
failed. CA Endevor SCM was unable to establish the security context through the
initUSP service or was unable to dub the address space. Check C1MSGS1 for associated
error messages.
Action:
C1G Messages
C1G0566S
ENDEVOR MODULE C1UIO000 EXCEEDED ABEND COUNT
Reason:
The CA Endevor SCM UNIX I/O module C1UIO000 experienced multiple failures and
disabled itself. See the C1MSGS1 report for related error messages.
Action:
C1G0600W
PROGRAM OBJECT FOOTPRINT WARNING: warning message
Reason:
A warning condition occurred when writing the footprint record into the program object
library. The warning information will be appended to this message. Processing
continues.
Action:
None.
C1G0600C
PROGRAM OBJECT FOOTPRINT ERROR: error information
Reason:
An error occurred writing the footprint record into the program object library.
Action:
Make sure that the attributes of the PSDE library are correct. If they are, contact CA
Technical Support.
C1G0604I
element name
Reason:
Informational message. This message contains the name of the element that was
overridden.
Action:
None.
C1G Messages
C1G0620S
ALLOCATION FAILED ON INTERNAL IAR WORK FILE IN MODULE C1BM4201
Reason:
An internal error occurred while dynamically allocating the IAR work file.
Action:
Contact technical support.
C1G0621S
GETMAIN IOB FAILED FOR ONTERNAL IAR WORK IN MODULE
C1BM4201
Reason:
The Job's region size is too small.
Action:
Increase the Job's region size. Contact technical support if the problem continues.
C1G0622S
CLOSE FAILED ON INTERNAL IAR WORK FILE IN MODULE C1BM4201
Reason:
An internal error occurred while closing the IAR work file.
Action:
C1G0623S
OPEN FAILED ON INTERNAL IAR WORK FILE DURING C1BM4201 SORT
Reason:
During the sort process, an open failure occurred on the IAR work file.
Action:
C1G Messages
C1G0624S
ALLOCATION OF SORTOUT FAILED DURING C1BM4201 SORT
Reason:
During the sort process, the dynamic allocation of SORTOUT failed.
Action:
C1G0625S
CLOSE FAILED ON INTERNAL IAR WORK FILE DURING C1BM4201 SORT
Reason:
During the sort process, a close failure occurred on the IAR work file.
Action:
C1G0626S
DE-ALLOCATION FAILURE OF INTERNAL IAR WORK FILE DURING C1BM4201 SORT
Reason:
After the sort process, the de-allocation of the IAR work file failed.
Action:
C1G0627S
INTERNAL IAR WORK FILE SORT FAILED IN MODULE C1BM4201
Reason:
IAR sort failed.
Action:
Check output for any related sort messages. If problem cannot be resolved call technical
support.
C1G Messages
C1G0628S
IAR INTERNAL WORK FILE OPEN FAILURE IN C1BM4201, WIARRUTN
Reason:
While attempting to open for output the IAR, an open failure occurred.
Action:
Check output for any relevant open messages. If problem cannot be resolved,
call technical support.
C1G0629S
IAR INTERNAL WORK FILE WRITE FAILURE IN C1BM4201, WIARRUTN
Reason:
While attempting to write an IAR record, a write failure occurred.
Action:
Check output for any relevant messages. If problem cannot be resolved, call
technical support.
C1G0630S
GETMAIN IOB FAILED FOR INTERNAL SIAR WORK FILE IN MODULE C1BM4201
Reason:
Getmain failed.
Action:
Check output for any relevant messages. Try increasing the job's regions size. If problem
cannot be determined call technical support.
C1G Messages
C1G0631S
SIAR INTERNAL WORK FILE OPEN FAILURE IN C1BM4201, WSRTRUTN While
attempting to create dump records from the sorted IAR internal file, an open error
occurred.
Reason:
Check the output for any relevant messages.
Action:
If the problem cannot be resolved, contact technical support.
C1G0632S
SIAR INTERNAL WORK FILE READ FAILURE IN C1BM4201, WSRTRUTN
Reason:
While attempting to create trace dump record from the SIAR internal file, a read error
occurred.
Action:
Check the output for any relevant messages. If the problem cannot be resolved, contact
technical support.
C1G0633S
SIAR INTERNAL WORK FILE OPEN FAILURE IN C1BM4201, PROCRUTN
Reason:
During the action execution process, an open error occurred against the sorted IAR work
file.
Action:
Check the output for any relevant messages. If the problem cannot be
resolved, contact technical support.
C1G Messages
C1G0634S
SIAR INTERNAL WORK FILE READ FAILURE IN C1BM4201, PROCRUTN
Reason:
During the action execution process, a read error occurred against the sorted IAR work
file.
Action:
Check the output for any relevant messages. If the problem cannot be resolved, contact
technical support.
C1G0635S
C1BM4201: GETMAIN FAILURE ON EITHER THE OFC1 OR OTC1 ARQ STRUCTUES
Reason:
Memory problem.
Action:
Try increasing the job's region size. Check the output for any relevant
messages. If problem continues, contact technical support.
C1G0700I
PROGRAM NDVRC1 WAS FOUND NOT TO BE AUTHORIZED
Reason:
This message indicates that a non-authorized program attempted to execute a CA
Endevor SCM utility program, such as C1BM3000, which requires the calling program to
be authorized.
Action:
Re-link the calling program as authorized and place it in an authorized library.
C1G0701I
ALTERNATE ID, ESI, ELEMENT AND PACKAGE PROCESSING DIABLED
Reason:
This message appears along with C1G0700I.
Action:
See action for message C1G0700I.
C1G Messages
C1G0702S
program name REQUIRES SYSTEM AUTHORIZATION FOR PROGRAM NDVRC1-EXEC
TERMINATED
Reason:
This message indicates that a non-authorized program has requested a CA Endevor SCM
API function that requires the calling program to be authorized.
Action:
Re-link the calling program to be authorized and place it in an authorized library.
C1G0703E
ENDEVOR API OPERATING IN READ-ONLY MODE-EXEC TERMINATED
Reason:
This message indicates that a non-authorized program has requested a CA Endevor SCM
API function that requires the calling program to be authorized.
Action:
Re-link the calling program as authorized and place it in an authorized library.
C1G0804E
UNABLE TO LOAD TABLE C1GTAPGM. REASON: NOTFOUND.
Reason:
The C1GTAPGM table was not found. The SMP/E install process installs (assembles and
links) the C1GTAPGM table into iprfx.iqual.CSIQAUTU. C1GTAPGM is a table of program
names that are eligible to be called by the automated process driver in an authorized
mode. It should be included in the STEPLIB of the your JCL. Unless you need to make
changes to the table, you don't need to edit the source at all.
Action:
If changes are required to the table, it must be assembled and linkedited using the JCL
member BC1JTABL.
C1I Messages
C1I Messages
C1I0001E
MODULE BC1TPGML NOT FOUND IN CONLIB
Reason:
Module BC1TPGML is required for the loading and initialization of the CA Endevor SCM
system. The data set name specified for the DDNAME CONLIB was improperly set during
installation.
Action:
Verify that the CA Endevor SCM CONLIB is set up properly and available. Also verify that
the installation procedure was followed to make sure that the libraries and JCL created
were properly established.
C1I0002E
MODULE member name NOT FOUND IN ddname 1 OR ddname 2, ENDEVOR
INITIALIZATION HAS ABORTED
Reason:
Internal error.
Action:
C1I0005E
THE C1DEFLTS TABLE IS NOT COMPATIBLE WITH THE CURRENT ENDEVOR *** PLEASE
CONTACT YOUR ENDEVOR ADMINISTRATOR TO REASSEMBLE THE C1DEFLTS TABLE
Reason:
The current release of CA Endevor SCM has found a C1DEFLTS Table that was assembled
with an older release of this product.
Action:
Make sure that the STEPLIB and ISPPLIB DD statements point to a copy of C1DEFLTS,
which was reassembled since the last installation of CA Endevor SCM.
C1I Messages
C1I0007E
REQUIRED USER ID PARAMETER IS MISSING FROM THE JOBCARD
Reason:
The BATCHID parameter within the defaults table contains a value that requires that the
USERID parameter be coded on the jobcard.
Action:
Code the USERID parameter on the jobcard and resubmit the job.
C1I0010E
BC1TPGML MODULE TABLE IS EMPTYC1B. ENDEVOR INITIALIZATION IS ABORTING
Reason:
Internal error.
Action:
C1I0011E
THE C1DEFLTS TABLE DOES NOT CONTAIN ANY ENVIRONMENT DEFINITIONS
Reason:
The C1DEFLTS table was created without any environment definitions.
Action:
Recreate the C1DEFLTS table with environment definitions.
C1I0012E
YOU ARE NOT AUTHORIZED TO ACCESS ANY ENVIRONMENTS
Reason:
You are not authorized to access any environments.
Action:
C1I Messages
C1I0013E
CAILMP Common Enforcement Software is not installed
Reason:
The RIM component of CA Common Services is not operational.
Action:
Contact your systems administrator.
C1I0014E
VERSION version number OF BC1TPGML IS INVALID. ENDEVOR INITIALIZATION IS
TERMINATING
Reason:
Internal error.
Action:
C1I0015E
THE C1UEXITS TABLE IS NOT COMPATIBLE WITH THE CURRENT ENDEVOR *** PLEASE
CONTACT YOUR ENDEVOR ADMINISTRATOR TO REASSEMBLE THE C1UEXITS TABLE
Reason:
The user exits table, C1UEXITS, is from an earlier release of CA Endevor SCM.
Action:
The C1UEXITS table is loaded from an authorized data set in the STEPLIB, JOBLIB, link
list, or LPALIB concatenation. Reassemble the table and link edit it into a data set that is
defined in one of the above. If the C1UEXITS table was reassembled but linked into a
CONLIB data set, move it to one of the previously listed libraries.
C1I Messages
C1I0016E
THE C1BEXITS TABLE IS NOT COMPATIBLE WITH THE CURRENT ENDEVOR *** PLEASE
CONTACT YOUR ENDEVOR ADMINISTRATOR TO move C1BEXITS to the proper library
Reason:
The system exits table, C1BEXITS, is from an earlier release of CA Endevor SCM. This
table is loaded from CONLIB.
Action:
Make sure that the data sets in the CONLIB concatenation do not contain modules from
an older release of CA Endevor SCM.
C1I0017E
LOAD OF TABLE c1deflts_table_name FAILED, RESULT=result
Reason:
During initialization, the C1DEFLTS table is loaded from the Task library, STEPLIB, system
link list, or Link Pack Area. If CA Endevor SCM cannot load C1DEFLTS, it issues this
message.
Action:
The value of result may be one of the reasons listed next. Follow the appropriate
recommendations based upon the result shown in the message.
STORAGEIncrease the REGION= specification on the EXEC PGM= statement, or on

the TSO logon screen.
NON-EXECThe C1DEFLTS table was not linked correctly. Check the output of the
last job or process which link-edited C1DEFLTS for messages issued by the
assembler or linkage editor. Correct the error and rerun the assemble and link-edit.
Then retry CA Endevor SCM.
MISS-OPAn internal programming error occurred. An abend may accompany the

message, and a system dump is produced if either SYSUDUMP or SYSABEND DD
statements were allocated. Call your administrator for instructions to analyze the
dump.
NOTFOUND This is the most common cause of this message. C1DEFLTS (or the
substitute name established by ENUXSITE) did not exist in any concatenation or the
task library, STEPLIB, system link list, or Link Pack Area. Make sure that your JCL,
TSO procedure, or CLIST allocates the correct libraries for the version of CA Endevor
SCM you are using, or make sure that the library containing C1DEFLTS is listed in the
LNKLSTxx member of SYS1.PARMLIB or in the LPA lists. If using system link list, be
sure that no new extent has been created to your library. If so, issue a refresh LLA
command.
C1I Messages
C1I0018E
LOAD OF ENUXSITE FAILED - RESULT=<result-of-load>
Reason:
Module ENUXSITE was found in a STEPLIB or link list data set, but it could not be loaded
because it is either marked non-executable or an I/O error occurred.
Action:
This is a user written module. Check the output of the linkedit and ensure that the
module is executable. Check for operating system messages or abends that will isolate
the cause of the load failure.
C1I0021E
THE MASTER SECURITY TABLE IS NOT COMPATIBLE WITH THE CURRENT ENDEVOR
***PLEASE CONTACT YOUR ENDEVOR ADMINISTRATOR TO REASSEMBLE THE MASTER
SECURITY TABLE
Reason:
The security table, usually BC1TNEQU for the CA Endevor SCM External Security
Interface, and ACCSTABL for Native Security, is from an earlier release of CA Endevor
SCM.
Action:
The security table name is specified in the ACCSTBL field in the TYPE=MAIN section of
the C1DEFLTS table. The security table is loaded from an authorized data set in the
STEPLIB, JOBLIB, LNKLST, or LPALIB concatenation. Reassemble the table and link edit it
into a data set that is defined in one of the above. If the security table was reassembled
but linked into a CONLIB data set, move it to one of the previously listed libraries.
Alternatively, verify that you have not enabled both Native Security and External
Security features together in the C1DEFLTS table. For example, specifying
ACCSTBL=ACCSTABL and ESSI=Y can result in the loading of an incompatible BC1TNEQU
security table from one of the previously listed libraries.
C1I Messages
C1I0022E
THE SYMBOL TABLE IS NOT COMPATIBLE WITH THE CURRENT ENDEVOR ***PLEASE
CONTACT YOUR ENDEVOR ADMINISTRATOR TO REASSEMBLE THE SYMBOL TABLE
Reason:
The site symbol table is missing or is from an earlier release of CA Endevor SCM.
Action:
Create the table before defining the table name with the SYMBOLTBL= field in the
TYPE=MAIN section of the C1DEFLTS table.
If the table is from an earlier release of CA Endevor SCM, use JCL member BC1JTABL in
iprfx.iqual.CSIQJCL to assemble and link-edit the table. An alternative is to use an SMP/E
USERMOD to accomplish this.
C1LB Messages
C1LB Messages
C1LB000S
C1LB0003 INTERNAL ERROR # error number UNEXPECTED BUG text ENDEVOR LIB
FUNCTION # function number
Reason:
Internal error.
Following is a list of the codes and their meanings for the function number parameter:
0001
0002
0003
0004
0005
0006
0007
0008
0009
0010
0011
0012
0013
0014
0015
0016
0017
0018
0019
0020
0021
OPEN INPUT
OPEN OUTPUT
CLOSE
FIND MEMBER
DELETE MEMBER
READ MEMBER RECORD
ADD MEMBER (FAIL NOT NEW)
ADD/REPLACE MEMBER
SORTED MEMBER LIST
UNSORTED MEMBER LIST
STOW MEMBER
READ FROM BEGINNING
ROLLBACK PARTIAL UPDATE
OPEN SEQ LOAD (INIT/EXTEND)
REOPEN FOR RANDOM UPDATE
RESERVE DATA SET EXCLUSIVE ENQ
RELEASE DATA SET EXCLUSIVE DEQ
REORG DIRECTORY (REHASH)
EXPAND LIBRARY
ADJUST AUTO EXPAND CRITERIA
CLOSE TYPE=T
Action:
C1LB Messages
C1LB001E
IMPROPER / OUT OF SEQ ENDEVOR LIB FUNCTION # function number
MEMBER=member name DDNAME/DSN ddname or dsname
Reason:
Internal error.
0001
0002
0003
0004
0005
0006
0007
0008
0009
0010
0011
0012
0013
0014
0015
0016
0017
0018
0019
0020
0021
ENSURE SINGLE THREADED OUTPUT

OPEN LIBRARY FOR INPUT
CLOSE LIBRARY
FIND MEMBER
DELETE MEMBER
READ MEMBER
ADD MEMBER
REPLACE MEMBER
SORTED DIRECTORY LIST
UNSORTED DIRECTORY LIST
STOW MEMBER
READ MEMBER FORM BEGINNING
ROLLBACK MEMBER ABORT STOW
OPEN EXTEND (INIT/EXTEND)
REOPEN (SEQ->RANDOM)
ENQ DATA SET EXCLUSIVE
DEQ DATA SET
REORG DIRECTORY PAGES
EXPAND DATA SET
ADJUST EXPAND DEFAULTS
CLOSE TYPE=T
Action:
C1LB002S
LIBRARY IS NOT ENDEVOR LIB DATA SET.
Reason:
You requested an ELIB function against a data set that is not defined as an ELIB data set.
Action:
Contact CA Technical Support about allocating the data set as an ELIB data set.
C1LB Messages
C1LB003E
ELIB FULL OR MEMBER SIZE > RESERVE PAGES - data set (member)
Reason:
The named member cannot be added to the library because the library is full or the size
of the member exceeds the reserve threshold for the library.
Action:
Adjust the reserve threshold of the library.
C1LB004S
LIBRARY SPACE MAP IS DAMAGED, NEEDS RECOVERY.
Reason:
The ELIB space map is damaged.
Action:
Run BC1PNCPY to salvage as many members as possible. Revert to backups for
members that cannot be recovered.
C1LB005W
LIBRARY IS BUSY BEING EXTENDED OR INITIALIZED.
Reason:
The requested action cannot be executed because the library is busy.
Action:
Resubmit the action at a later time.
C1LB006E
LIBRARY OPEN FAILED.
Reason:
Internal error.
Action:
This error is usually caused by failure to initialize an Elib. However, there may be other
causes, so also check for other messages.
C1LB Messages
C1LB007C
DATA SET IS NEW (EMPTY)
Reason:
You submitted a job using the INITIALIZE function and DESTROY TO REUSE option of the
BC1PNLIB utility. However, the data set against which you ran the action has no
members.
Action:
Correct the INITIALIZE syntax and rerun the job.
C1LB008C
DATA SET IS NOT EMPTY
Reason:
You submitted a job using the INITIALIZE function and DESTROY TO REUSE option of the
BC1PNLIB utility. However, the data set against which you ran the action has members
in it.
Action:
Correct the INITIALIZE syntax and rerun the job.
C1LB Messages
C1LB009C
INSUFFICIENT STORAGE TO PROCESS FUNCTION = function number
Reason:
CA Endevor SCM could not acquire enough storage to execute the named function.
0001
0002
0003
0004
0005
0006
0007
0008
0009
0010
0011
0012
0013
0014
0015
0016
0017
0018
0019
0020
0021

CLOSE LIBRARY
FIND MEMBER
DELETE MEMBER
READ MEMBER
ADD MEMBER
REPLACE MEMBER
STOW MEMBER
DEQ DATA SET
EXPAND DATA SET
CLOSE TYPE=T
Action:
C1LB Messages
C1LB010S
ENDEVOR LIB INTERNAL LINKAGE ERROR FUNCTION=function number DDNAME/DSN
ddname or dsname
Reason:
Internal error.
0001
0002
0003
0004
0005
0006
0007
0008
0009
0010
0011
0012
0013

CLOSE LIBRARY
FIND MEMBER
DELETE MEMBER
READ MEMBER
ADD MEMBER
REPLACE MEMBER
STOW MEMBER
Action:
C1LB011E
ENDEVOR LIB PAGE # page number OUT OF RANGE DDNAME/DSN ddname or dsname
Reason:
Another user may have expanded the library while you were attempting to read a
member.
Action:
Retry the action.
C1LB Messages
C1LB013S
ENDEVOR LIB BUFFER MGMT STORAGE DAMAGED DDNAME/DSN ddname or dsname
Reason:
Internal error.
Action:
C1LB014E
ENDEVOR LIB PAGE # page number HEADER DATA DAMAGED DDNAME/DSN ddname
or dsname
Reason:
The header data on the indicated page is damaged.
Action:
Identify and correct the problem using the ELIB data set utilities. For more information,
see the chapter "Setting Up ELIB Data Sets" in the Utilities Guide. You may be required
to re-org your ELIB data set. If the data set cannot be corrected using these utilities, call
CA Technical Support.
C1LB015C
ENDEVOR LIB LOADING PAGE # page number - OUT OF SEQ DDNAME/DSN ddname or
dsname
Reason:
CA Endevor SCM attempted to load the page indicated in the message but it was out of
sequence.
Action:
C1LB Messages
C1LB016C
MEMBER NAME = member name CONTAINS INVALID CHARACTERS
Reason:
The indicated member contains invalid characters. This can occur when using
BC1PNCOPY to copy from a PDS with binary characters in member names.
Action:
C1LB017S
DIRECTORY PAGE # page number KEY NOT "DIRddddd"
Reason:
The indicated page number is a directory page but its key is not in the indicated format.
Action:
C1LB018S
ENDEVOR LIB ROLLBACK FAILURE MEMBER=member name DDNAME/DSN ddname or
dsname
Reason:
Internal error.
Action:
C1LB Messages
C1LB019S
ENDEVOR LIB FUNCTION # function number PARAMS INVALID DDNAME/DSN ddname
or dsname
Reason:
Internal error.
0001
0002
0003
0004
0005
0006
0007
0008
0009
0010
0011
0012
0013
0014
0015
0016
0017
0018
0019
0020
0021

CLOSE LIBRARY
FIND MEMBER
DELETE MEMBER
READ MEMBER
ADD MEMBER
REPLACE MEMBER
STOW MEMBER
DEQ DATA SET
EXPAND DATA SET
CLOSE TYPE=T
Action:
C1LB020W
MEMBER = member name ALREADY EXISTS
Reason:
A member already exists in the target data set with the name indicated in the message.
Action:
Make sure that you specified the member name correctly.
C1LB Messages
C1LB021C
MEMBER = member name RECORD LENGTH = length TOO BIG
Reason:
The record length for the member referenced in the message is too large for the target
data set.
Action:
C1LB022C
ENDEVOR LIB UNABLE TO LOAD BDAM SUPPORT MODULE DDNAME/DSN ddname or
dsname
Reason:
Internal error.
Action:
C1LB023E
MEMBER = member name TOO LARGE OR FRAGMENTED TO STOW
Reason:
The named member is either too large or too fragmented to store in the directory pages
for this data set.
Action:
C1LB024W
MEMBER member name NOT FOUND
Reason:
CA Endevor SCM could not find the named member.
Action:
Make sure that you specified the member name correctly, and then resubmit the action
request.
C1LB Messages
C1LB025W
MEMBER member name UNDER UPDATE BY ANOTHER USER
Reason:
The named member is being updated by another user.
Action:
Access the member at a later time.
C1LB027E
ENDEVOR LIB library name INIT INCOMPLETE - RERUN INIT
Reason:
CA Endevor SCM was unable to initialize the named library.
Action:
Rerun the initialization job.
C1LB028W
ENDEVOR LIB TOO FULL TO REORG - USE EXPAND DDNAME/DSN ddname or dsname
Reason:
The named library is too full to reorganize.
Action:
Use the expand function of the BC1PNLIB utility to expand the size of the library.
C1LB029E
ENDEVOR LIB CAN NOT BE MADE SMALLER BY EXPAND DDNAME/DSN ddname or
dsname
Reason:
The EXPAND request makes the named library smaller. This is an invalid request.
Action:
Resubmit the request with different size specifications.
C1LB Messages
C1LB030S
ENDEVOR LIB MEMBER=member name HAS DAMAGED PAGE(S) DDNAME/DSN:
ddname or dsname
Reason:
The named member has damaged pages.
Action:
Revert to a backup copy of the member.
C1LB034S
FILE MUST BE DISP=OLD OR YOU MUST USE LSERV
Reason:
You are attempting to access a non-sharable file with CA L-Serv.
Action:
Verify that the subsystem is correct and that the share options specified on the DEFINE
statement were SHAREOPTIONS(3,3). When using this data set, such as in the BC1PNLIB
utility, make sure that the DISP=OLD disposition is specified on the DD statement.
C1LB800E
MEM=member name PAGE# xxxxxxx DSN=xxxxxxxxxxxx
Reason:
Internal error.
Action:
C1LB801E
MEM=member name VSAM xxxxxxxx RPL busy. RC=xx
Reason:
Internal error.
Action:
C1M Messages
C1LB802E
MEM=member name VSAM xxxxxxxx RC=xx
Reason:
Internal error.
Action:
C1LB810E
MEM=member name PAGE #,nnnnnn, DSN=dsname
Reason:
Internal error.
Action:
C1M Messages
This section details messages generated by the MCF (Master Control File) and package
extract utility in the course of processing, along with possible causes and corrective
C1M0001I
ENDEVOR MCF EXTRACT SUMMARY:
Reason:
Informational message. This message is the header for the Master Control File (MCF)
extract summary report.
Action:
None.
C1M Messages
C1M0002I
NUMBER OF ENVIRONMENT RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Environment records
written to the MCF extract (BSTXMCF) data set.
Action:
None.
C1M0003I
NUMBER OF STAGE RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Stage records written to
the MCF extract (BSTXMCF) data set.
Action:
None.
C1M0004I
NUMBER OF ENVIRONMENT/STAGE RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Environment to Stage
mapping records written to the MCF extract (BSTXMCF) data set.
Action:
None.
C1M0005I
NUMBER OF DATA SET NAME RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Data Set Name records
Action:
None.
C1M Messages
C1M0006I
NUMBER OF SYSTEM RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of System records written to
the MCF extract (BSTXMCF) data set.
Action:
None.
C1M0007I
NUMBER OF SUBSYSTEM RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Subsystem records
Action:
None.
C1M0008I
NUMBER OF TYPE DEFINITION RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Element Type records
Action:
None.
C1M0009I
NUMBER OF ELEMENT RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Element records written
to the MCF extract (BSTXMCF) data set.
Action:
None.
C1M Messages
C1M0010I
NUMBER OF APPROVER GROUP RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Approver Group records
Action:
None.
C1M0011I
NUMBER OF APPROVER GROUP JUNCTION RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Approver Group Junction
records written to the MCF extract (BSTXMCF) data set.
Action:
None.
C1M0012I
NUMBER OF PROCESSOR GROUP RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Processor Group records
Action:
None.
C1M0013I
NUMBER OF PROCESSOR GROUP SYMBOLIC RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Processor Group Symbolic
Action:
None.
C1M Messages
C1M0014I
TOTAL NUMBER OF RECORDS WRITTEN TO BSTXMCF FILE:
Reason:
Informational message. This message indicates the total number of records written to
the MCF extract (BSTXMCF) data set. The total printed should equal the sum of the
values shown in messages C1M002I through C1M0013I.
Action:
None.
C1M0015I
ENDEVOR PACKAGE EXTRACT SUMMARY:
Reason:
Informational message. This message is the header for the Package Data Set Extract
Summary report.
Action:
None.
C1M0016I
NUMBER OF PACKAGE HEADER RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Package Header records
written to the Package Data set extract (BSTXPKG) data set.
Action:
None.
C1M0017I
NUMBER OF PACKAGE SCL RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Package SCL records
Action:
None.
C1M Messages
C1M0018I
NUMBER OF PACKAGE APPROVER RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Package Approver
records written to the Package Data set extract (BSTXPKG) data set.
Action:
None.
C1M0019I
NUMBER OF PACKAGE ELEMENT-ID RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Package Element
Identification records written to the Package Data set extract (BSTXPKG) data set.
Action:
None.
C1M0020I
NUMBER OF PACKAGE CAST-REPORT RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Package Cast Report
Action:
None.
C1M0021I
NUMBER OF PACKAGE ORPHAN DATA SET RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Package Orphan records
Action:
None.
C1M Messages
C1M0022I
NUMBER OF PACKAGE BACKOUT RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Package Backout records
Action:
None.
C1M0023I
NUMBER OF PACKAGE-SHIP DESTINATION RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Package Shipment
Destination records written to the Package Data set extract (BSTXPKG) data set.
Action:
None.
C1M0024I
NUMBER OF PACKAGE-SHIP DATA SET NAME MAPPING RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Package Shipment Data
set name mapping records written to the Package Data set extract (BSTXPKG) data set.
Action:
None.
C1M0025I
NUMBER OF PACKAGE SHIPMENT RECORDS WRITTEN:
Reason:
Informational message. This message indicates the number of Package Shipment
Action:
None.
C1M Messages
C1M0026I
TOTAL NUMBER OF RECORDS WRITTEN TO BSTXPKG:
Reason:
Informational message. This message indicates the total number of records written to
the Package Data set extract file (BSTXPKG). The total indicated should equal the sum of
the values shown in messages C1M0016I through C1M0025I.
Action:
None.
C1M0027I
NO ENVIRONMENT COMMAND WAS SPECIFIED. MCF INFORMATION WILL NOT BE
EXTRACTED.
Reason:
Informational message. The BC1PXTRA command file (BSTIPT) did not contain an
ENVIRONMENT keyword. Therefore, the extract program will not extract any MCF
information.
Action:
None. If you want to extract MCF information add the ENVIRONMENT keyword to the
BSTIPT control statements and add a //BSTXMCF DD statement to the execution JCL.
C1M0028I
MCF DATA WILL BE EXTRACTED FOR ENVIRONMENT environment_name
Reason:
Informational message. The BC1PXTRA command file (BSTIPT) contained an
ENVIRONMENT keyword. This message is produced for each environment specified on
the ENVIRONMENT keyword.
Action:
None.
C1M Messages
C1M0029I
NO EXTRACT COMMAND WAS SPECIFIED. PACKAGE INFORMATION WILL NOT BE
EXTRACTED.
Reason:
Informational message. The BC1PXTRA command file (BSTIPT) did not contain an
EXTRACT PACKAGES statement. Therefore, the extract program will not extract any
Package Data set information.
Action:
None. If you want to extract Package Data set information add the EXTRACT PACKAGES
statement to the BSTIPT control statements and add a //BSTXPKG DD statement to the
execution JCL.
C1M0030I
PACKAGE DATA WILL BE EXTRACTED
Reason:
Informational message. The BC1PXTRA command file (BSTIPT) contained the EXTRACT
PACKAGES statement. The program is indicating that Package Data set information will
be extracted.
Action:
None.
C1M0031E
ENVIRONMENT environment_name WAS NOT FOUND EXECUTION HAS BEEN
ABORTED.
Reason:
The environment specified on the ENVIRONMENT keyword was not located in the
C1DEFLTS table used during the program run. Execution of BC1PXTRA terminated with a
return code of 12.
Action:
Verify that the environment identified is specified in the C1DEFLTS table used during the
program run. If it was not found in C1DEFLTS then remove the environment name from
the ENVIRONMENT statement and re-execute the program or use a C1DEFLTS table that
contains the environment.
C1M Messages
C1M0032E
Reason:
The $IMR service returned an unrecoverable error. The message following C1M0032E
identifies the specific $IMR error.
Action:
For more information about the error, see the message that follows C1M0032E.
C1M0033E
C1BMINIT FAILURE. Call Endevor Technical Support
Reason:
One of the BC1PXTRA initialization programs did not complete successfully. BC1PXTRA
execution was terminated.
Action:
Resubmit the job. If the problem persists contact your administrator.
C1M0034E
PROCESSING TERMINATED BECAUSE OF CONTROL STATEMENT ERRORS
Reason:
The BSTIPT control statement parse routine detected an error in the control statements
passed to BC1PXTRA. The parser generated one or more messages to identify the
problem.
Action:
See the parser messages generated and correct the error in the BSTIPT control
statements. Resubmit the job after the errors have been corrected.
C1M Messages
C1M0035E
$PKMR EXTRACT REQUEST FAILED. PKMRRTYP=record_type. $PKMR ERROR MESSAGE
FOLLOWS
Reason:
The $PKMR service returned an error when attempting to extract information from the
Package Data set. The record_type identifies the type of Package Data set record that
was being processed. A $PKMR message that further identifies the problem will be
printed after message C1M0035E.
Action:
For more information, see the $PKMR message that follows message, C1M0035E.
C1M0036W
INVALID RECORD LENGTH FOR $IMR DATA. ONLY 70 BYTES WRITTEN TO RECORD
record_number IN BSTXMCF FILE
Reason:
The MCF data returned by the $IMR service is too long to write to the BSTXMCF data
set. Only the first 70 bytes (the record header) will be written. The record_number field
identified the logical record number in the BSTXMCF that was truncated.
Action:
C1M0037W
INVALID RECORD LENGTH FOR $PKMR DATA. ONLY 64 BYTES WRITTEN TO RECORD
record_number in BSTXPKG FILE
Reason:
The Package Data set data returned by the $PKMR service is too long to write to the
BSTXPKG data set. Only the first 64 bytes (the record header) will be written. The
record_number field identified the logical record number in the BSTXPKG that was
truncated.
Action:
C1P Messages
C1M0041I
DUPLICATE ELEMENTS-ELIMINATED number
Reason:
Informational Message. This message indicates the number of duplicate elements
eliminated before writing element records to the MCF extract (BSTXMCF) data set.
Action:
None.
C1M0042I
ELM EXTENSION RECORDS WRITTEN:
Reason:
Informational Message. This message indicates the number of Element Extension
Action:
None.
C1P Messages
C1P0004E
ERROR ENCOUNTERED ATTEMPTING TO UPDATE PACKAGE DATA SET
Reason:
CA Endevor SCM was unable to update the package named in the action request.
Action:
C1R Messages
C1P0015I
PACKAGE PROCESSING COMPLETED SUCCESSFULLY
Reason:
Informational message. CA Endevor SCM successfully completed the requested package
processing.
Action:
None.
C1R Messages
C1R0001E
OPEN OF OUTPUT DDNAME ddname FAILED
Reason:
An unload request was submitted that specified a ddname that could not be opened.
Action:
Make sure that the ddname was specified correctly.
C1R0002E
SECURITY CHECK FOR ENV environment SYSTEM system FAILED
Reason:
You are not authorized to perform unload/reload processing for the environment and
system identified in this message.
Action:
C1R Messages
C1R0003E
VSAM ERROR RC return code FDBK feedback code DSN dsname
Reason:
Internal error. A VSAM I/O error occurred while accessing the VSAM cluster identified in
the message.
Action:
Check the VSAM feedback code for the action.
C1R0004I
SYSTEM system STARTED
Reason:
Informational message. Unload/Reload processing began for the system identified in the
message.
Action:
None.
C1R0004W
ENV/SYS UNLOADS NOT PERFORMED - ALL ENV/SYS CONBINATIONS EXCLUDED
Reason:
No environment and system combinations were unloaded because all eligible
combinations were bypassed due to the Exclude clauses specified on the Unload SCL.
Action:
None.
C1R0005I
SYSTEM system SUBSYSTEM subsystem AT STAGE stage BEING PROCESSED
Reason:
Informational message. Unload/Reload processing has begun for the system, subsystem,
and stage identified in the message.
Action:
None.
C1R Messages
C1R0006I
SUBSYSTEM subsystem COMPLETED
Reason:
Informational message. Unload/Reload processing was completed for the subsystem
Action:
None.
C1R0007E
ALLOCATION OF BASE FILE FOR TYPE type FAILED
Reason:
An error occurred while attempting to allocate the base library defined for the type
Action:
See the allocation error message that preceded this message.
C1R0008E
ALLOCATION OF DELTA FILE FOR TYPE type FAILED
Reason:
An error occurred while attempting to allocate the delta library defined for the type
Action:
See the allocation error message that preceded this message.
C1R0009I
PROCESSING FOR ENV environment SYSTEM system COMPLETE
Reason:
Informational message. Unload/Reload processing was completed for the environment
and system identified in the message.
Action:
None.
C1R Messages
C1R0010E
UNABLE TO FIND A MATCHING TYPE FOR TYPEID type id
Reason:
During Unload processing an element was found that does not have a type definition.
Action:
C1R0011I
ELEMENT HAS BEEN PROCESSED
Reason:
Informational message. Unload/Reload processing has been completed for the element
Action:
None.
C1R0012I
ELEMENT (TYPE type) PROCESSING STARTED
Reason:
Informational message. Unload/Reload processing has started for the element and type
Action:
None.
C1R0013I
PROCESSING STARTED FOR STAGE stage
Reason:
Informational message. Unload/Reload processing has started for the stage identified in
the message.
Action:
None.
C1R Messages
C1R0014I
PROCESSING STARTED FOR ENVIRONMENT environment
Reason:
Informational message. Unload/Reload processing has started for the environment
Action:
None.
C1R0015C
ELEMENT FAILED VALIDATION
Reason:
The element identified in this message has failed validation. Preceding messages
provide more information about the cause of the validation failure. This element will not
be unloaded.
Action:
See preceding messages for corrective action.
C1R0016I
ELEMENT PROCESSED WITHOUT COMPONENT LIST
Reason:
Informational message. An error was detected during component list base/delta
validation. Unload/Reload processed the element without the component list.
Action:
None.
C1R0017I
VALIDATION OF ELEMENT element TYPE type BEGUN
Reason:
Informational message. Unload/Reload processing has begun validating the element of
the type identified in the message.
Action:
None.
C1R Messages
C1R0018I
OPEN OF DDNAME SUCCESSFUL
Reason:
Informational message. The data set identified in the message has been opened
successfully.
Action:
None.
C1R0019I
PACKAGE PROCESSING BEGUN
Reason:
Informational message. Indicates beginning of Unload/Reload processing for the
package data set.
Action:
None.
C1R0020I
PACKAGE PROCESSING COMPLETED
Reason:
Informational message. Indicates completion of Unload/Reload processing for the
package data set.
Action:
None.
C1R0021I
PACKAGE package id COMPLETED
Reason:
package identified in the message.
Action:
None.
C1R Messages
C1R0022I
PROCESSING DDNAME ddname
Reason:
Informational message. Unload/Reload is processing the data set identified in the
message.
Action:
None.
C1R0023I
DESTINATION destination id COMPLETED
Reason:
destination identified in the message.
Action:
None.
C1R0024E
ERROR WRITING TO PACKAGE FILE - PACKAGE package name
Reason:
An error was detected writing the named package to the package file.
Action:
See associated messages for corrective action.
C1R0025E
ERROR WRITING TO PACKAGE FILE - DESTINATION destination id
Reason:
An error was detected writing the named destination to the package file.
Action:
C1R Messages
C1R0026E
ERROR OPENING DDNAME "C1SCL1"
Reason:
The unload/reload utility has found but cannot open the C1SCL1 ddname.
Action:
Make sure that the DDNAME is specified correctly in the JCL.
C1R0027E
UNLOAD DATA SET LRECL NOT ENOUGH FOR THE LONGEST TYPE type name, HAS TO
BE AT LEAST record length.
Reason:
The unload data set LRECL is too small for the named type.
Action:
Make sure that the unload data set LRECL is at least 84 bytes larger than the largest type
record length that will be unloaded.
C1R0028E
UNLOAD PROCESSING TERMINATED WITH CRITICAL ERRORS
Reason:
CA Endevor SCM unload processing has terminated and one or more critical errors were
encountered during processing.
Action:
Check for E-level messages in the unload output. Some inventory areas may have been
unloaded successfully while others may have been unloaded partially or not at all.
Correct the errors and rerun a full unload or an incremental unload of the inventory
areas that were not unloaded successfully.
C1R Messages
C1R0029E
CRITICAL ERROR OCCURRED DURING RELOAD PROCESSING: EXECUTION TERMINATED
Reason:
CA Endevor SCM has encountered a critical error during reload processing and
terminated execution.
Action:
Check for previous E-level messages in message log and fix. Contact your administrator.
C1R0030E
ABEND OCCURRED DURING UNLOAD OR RELOAD PROCESSING: EXECUTION
TERMINATED
Reason:
An abend has occurred during unload or reload processing.
Action:
C1R0031E
TYPE type name IS MISSING FROM ENV environment name
Reason:
The named type is missing from the named environment.
Action:
Make sure that you've spelled the type name correctly. Otherwise, contact your
administrator.
C1R0033E
UNLOAD DATA SET RECFM MUST BE "VB"
Reason:
The unload data set must be a variable block file.
Action:
Specify a variable blocked data set or redefine this data set as "VB".
C1R Messages
C1R0034E
PROCESSING FOR ENV environment name SYSTEM system name TERMINATED
Reason:
An attempt to reload an element from a backup tape failed. The inventory location was
found, but there is a conflict between the element on disk and the element on tape. The
validation routine determined the element on disk is newer than the element being
reloaded and failed the action.
Action:
Performing this action will cause regression of this element. If it is absolutely necessary
to reload the backup version, delete the existing version from the inventory area and
re-execute the RELOAD action.
C1R0035E
ELEMENT NAME MISSING FROM CATALOGUE FOR ELEMENT ALIAS
Reason:
Internal error. An entry for this element is missing from the catalogue. This error was
detected by the UNLOAD utility.
Action:
C1R0036C
FROM EXTENSION DATA SET INFO MISSING FOR ELEMENT AT ENV environment name
STGID stage id
Reason:
While uploading this element, it was determined that the FROM data set information
does not exist. This may be a normal condition, depending upon how this element was
created.
Action:
None.
C1R Messages
C1R0037C
TO EXTENSION DATA SET INFO MISSING FOR ELEMENT AT ENV environment name
STGID stage id
Reason:
While uploading this element, it was determined that the TO data set information does
not exist. This may be a normal condition, depending upon how this element was
created.
Action:
None.
C1R0039I
ENVIRONMENT environment SYSTEM system EXCLUDED FROM UNLOAD
Reason:
The environment and system identified in the message was excluded from Unload
processing because of an Exclude clause in the Unload SCL.
Action:
None.
C1R0040W
ENV/SYS UNLOADS NOT PERFORMED - ALL ENV/SYS CONBINATIONS EXCLUDED
No environment/systems were unloaded, because all eligible environment and system
combinations were bypassed due to the specified EXCLUDE clauses.
None.
C1R0041I
LAST action OF PACKAGE package-id DID NOT TERMINATE CORRECTLY
Reason
Informational message. This is an explanatory message that follows a package error
message during Unload. It is issued due to the incorrect termination of the last package
action (either Reset, Commit or Delete) which caused the previous error.
Action
Either reload the backup version of the package, or re-execute the last package action
that did not complete correctly.
C1R Messages
C1R0095E
"OPTIONS CHECKPOINT ONLY" REQUIRES "UNLOAD FULL" TO BE SPECIFIED
Reason:
A syntax error was found in the unload SCL. If the "checkpoint only" option is specified,
"unload full" must also be specified.
Action:
Correct the syntax and rerun the job.
C1R0096W
NO SYSTEMS FOUND WITHIN ENV environment name TO MATCH THE WILD CARD
CRITERIA OF system name mask
Reason:
There are no systems which match "system name mask" for the named environment.
Action:
Make sure that the environment/system combination was correctly specified.
C1R0096E
SYSTEM system name WITHIN ENVIRONMENT environment name NOT FOUND
Reason:
The named system is not defined to the named environment.
Action:
Make sure that you have specified the environment and system names correctly. Define
the system to the named environment if necessary.
C1R0097W
NO ENVIRONMENTS FOUND TO MATCH THE WILDCARD CRITERIA OF name mask
Reason:
No environments have been defined to CA Endevor SCM that meet the criteria of the
name mask in the message.
Action:
Make sure that you have specified the name mask correctly.
C1R Messages
C1R0097E
ENVIRONMENT environment NOT FOUND
Reason:
Either you do not have access to this environment, or the environment does not exist.
Action:
Correct input request and resubmit.
C1R0098E
ENVIRONMENT, SYSTEM AND DDNAME REQUIRED
Reason:
The input request does not specify an environment and/or a system and/or a ddname.
Action:
Correct the input request and resubmit.
C1R0099E
SECURITY VIOLATION ON ENVIRONMENT environment
Reason:
You are not authorized to access the environment specified in the message.
Action:
C1R020W
NO FOOTPRINT PRESENT, UNABLE TO CORRELATE TO MCF
Reason:
No footprint was found for the member or CSECT.
Action:
Determine the cause of this error before proceeding.
C1R Messages
C1R021W
THE CSECT HAS BEEN ZAPPED
Reason:
The named CSECT has been zapped.
Action:
None.
C1R022W
NO MCF ELEMENT MASTERS FOUND WHICH MATCH FOOTPRINT ID
Reason:
No elements were found in the MCF with the same name as the element referenced in
the footprint.
Action:
C1R023W
THE FOOTPRINT DATE/TIME DOES NOT MATCH MCF LAST GENERATE OR MOVE
DATE/TIME
Reason:
No elements were found in the MCF with a generate or move date/time that matches
the date/time in the footprint.
Action:
C1R024W
THE FOOTPRINT DATE/TIME INDICATES ELEMENT FROM A PRIOR STAGE
Reason:
The footprint date and time only matched an element record from an MCF for a
previous stage.
Action:
C1R Messages
C1R025W
THE FOOTPRINT DATE/TIME DOES NOT MATCH LAST LEVEL DATE/TIME
Reason:
The footprint date and time only matched an element record from an MCF for a
previous stage.
Action:
C1R026W
THE FOOTPRINT ENVIRONMENT/STAGE WAS NOT FOUND
Reason:
CA Endevor SCM could not find the environment/stage location contained in the
footprint.
Action:
C1R027W
THE FOOTPRINT ENVIRONMENT/STAGE NOT IN MAP OR EXPLICIT MATCH FOUND BUT
INV NAMES CHANGE
Reason:
In the first case the environment and stage referenced in the footprint are not on the
map route where the element currently resides. In the second case the package
component validation function has found an explicit component match, but system,
subsystem, or type names change across map locations, so a more recent version of the
component may exist at an intermediate stage.
Action:
In the first case, see your administrator to determine if the footprint environment and
stage are on another map. In the second case, check intermediate stages for the
presence of the component. If you find the component, regenerate the element
containing the component to pick up the more recent version.
C1R Messages
C1R028W
THE FOOTPRINT DATE/TIME INDICATES AN ENVIRONMENT/STAGE MISMATCH
Reason:
The footprint environment/stage correlates to an environment/stage location higher in
the map than the current location of the element.
Action:
C1R100I
Activating the CA-Roscoe release-number Interface
Reason:
Informational. Displays the CA Endevor SCM interface software level.
Action:
None.
C1R5201E
UNABLE TO PROCESS INPUT ON DDNAME ddname
Reason:
Informational message. The tape that has been loaded is not recognized as an unload
tape.
Action:
Make sure that the correct tape has been loaded.
C1R5205I
INPUT ON DDNAME ddname IS NOT IN PROPER FORMAT
Reason:
Informational message. The tape that has been loaded is not recognized as an unload
tape.
Action:
Make sure correct tape is loaded.
C1R Messages
C1R5206E
PROCESSING SYS system ENV environment HALTED - DATA SET NOT CATALOGED
Reason:
Reload processing terminated for the environment and system identified in the message
because a data set defined on a type definition for that system could not be found.
Action:
Make sure that the data set identified in the message is properly allocated and
cataloged.
C1R5207E
ONE OR MORE OF THE DATA SETS ASSOCIATED WITH THE TYPE type name ARE NOT
CATALOGED
Reason:
One or more of the data sets defined to the type identified in the message could not be
found. This message will be preceded by allocation error messages.
Action:
Make sure that the data sets identified in the preceding message is (are) properly
allocated and cataloged.
C1R5208E
CATALOG LOOKUP FOR DATA SET FAILED
Reason:
Data set name identified in the message could not be found.
Action:
Make sure that the data set is properly allocated and cataloged.
C1R Messages
C1R5209I
ELEMENT WITHIN inventory location RESTORED BY RELOAD PROCESS
Reason:
Reload has successfully restored the element identified in the message to the inventory
location identified in the message.
Action:
None.
C1R5210I
ELEMENT WITHIN inventory location DELETED BY RELOAD PROCESS
Reason:
Informational message. The element was deleted by reload processing because it did
not exist at the specified location at the time the unload file was created, and had a
create date prior to when the unload file was created. However, if the element was
created after the unload file was created the element would not be deleted.
Action:
None.
C1R5211I
DELETE OF ELEMENT COMPLETED
Reason:
Informational message. Reload processing has completed the deletion of the element
identified in the previous message.
Action:
None.
C1R Messages
C1R5289W
SYSTEM system WAS NOT FOUND WITHIN ENV environment ON INPUT DDNAME
ddname
Reason:
One or more environment/system combinations specified on the Reload request did not
exist in the reload input.
Action:
Make sure that the correct Unload/Reload processing occurred and if it did not correct
the environment/system specifications.
C1R5290W
NO RELOAD UPDATES PERFORMED FOR THIS JOB
Reason:
The reload program detected that no updates were performed. This message can be
issued as a result of environment or system not found.
Action:
None.
C1R5300I
VALIDATION FOUND AN ERROR WHILE PROCESSING
[BASE/DELTA/CONFIG_BASE/CONFIG_DELTA]
Reason:
Informational message. Associated with other messages that more explicitly identify the
problem.
Action:
None.
C1R Messages
C1R5301E
LOGICAL INTEGRITY ERROR PROCESSING BASE ELEMENT
Reason:
The number of statements contained in the base member of the element is out of sync
with the Element Master record.
Action:
If the element can be browsed, retrieve it, delete it, and add it back into CA Endevor
SCM. If the element cannot be browsed, delete it, and then Restore it from an earlier
unload tape or archive file.
C1R5302E
LOGICAL END OF FILE MISSING IN [DELTA/CONFIG_DELTA]
Reason:
The element delta is missing the CA Endevor SCM logical end of file control statement.
Action:
If the error is associated with the component list, use the DELETE action with only
component option to delete the component list base and delta, and then regenerate the
element to recreate the component list. If the control record for an element delta is
missing, delete the element and restore it from a prior unload tape or archive file.
C1R5303E
MISSING HEADER RECORD
Reason:
A CA Endevor SCM control record was found missing from either an element delta or a
component list delta. Subsequent messages will identify which is the case.
Action:
element to recreate the component list.
If the control record for an element delta is missing, delete the element and restore it
from a prior unload tape or archive file.
C1R Messages
C1R5304E
LOGICAL END OF FILE REACHED PREMATURELY
Reason:
A control record was found missing from either an element delta or a component list
delta. Subsequent messages will identify which is the case.
Action:
C1R5305E
EXPECTED INS/DEL COUNTS DO NOT MATCH CALCULATED
Reason:
A delta level contains a logically incorrect number of statement inserts and/or deletes.
Action:
C1R5306E
DELTA LEVEL NUMBERS OUT OF ORDER
Reason:
A delta member contains levels that are physically out of sequence.
Action:
C1R Messages
C1R5307E
FOOTPRINT VALIDATION FAILED FOR [BASE/DELTA/CONFIG_BASE/ CONFIG_DELTA]
ENCRYPTED NAME member name
Reason:
The footprint associated with the identified member failed validation.
Action:
If the error is associated with the element, delete the element and restore it from a
C1R5308I
LOCATION: SYS: system SBS: subsystem TYPE: type name (type id) STG: stage id
Reason:
Informational message. This message is issued to identify an element that contained
errors.
Action:
See associated error messages.
C1R5309I
DATA SET: dsname(encrypted member name)
Reason:
Informational message. This message is issued to identify a data set name and member
that contained errors.
Action:
C1R Messages
C1R5310E
[BASE/DELTA/CONFIG_BASE/CONFIG_DELTA] MEMBER IS EMPTY
Reason:
The member identified in the message was found to be empty.
Action:
C1R5311E
LAST LEVEL NUMBER IN DELTA DOES NOT MATCH EXPECTED Reason:
The last level contained in an element delta member is out of sync with the Element
Master record.
Action:
C1R5312E
MASTER RECORD CURRENT STATEMENT COUNT DOES NOT EQUAL THE LAST LEVEL
CUMULATIVE TOTAL
Reason:
The statement count contained in the last level of an element delta member is out of
sync with the Element Master record.
Action:
component option to delete the component list base and delta, and then regenerate
the element to recreate the component list.
C1U Messages
C1U Messages
C1U0000I
EXIT exit number - text
Reason:
Informational message. This message appears when the exit identified in the message
issued a message with a return code of 0.
Action:
None.
C1U0000W
Reason:
This message appears when the exit identified in the message has a return code of 4.
Action:
C1U0000C
Reason:
Action:
C1U Messages
C1U0000E
Reason:
Action:
C1U0900E
ACTION DENIED. INVENTORY AREA PACKAGE UPDATE ONLY.
Reason:
The specified inventory area for which an action was requested has an approver group
relationship.
Action:
Delete the relationship between the inventory area and the approver group, or use
package processing to update the inventory area.
C1U0901E
INVALID CALL PARAMETERS. CALL ENDEVOR TECHNICAL SUPPORT.
Reason:
Internal error.
Action:
C1U0902E
UNSUPPORTED ACTION. CALL ENDEVOR TECHNICAL SUPPORT.
Reason:
Internal error.
Action:
C1U Messages
C1U0903E
INTERNAL LOGIC ERROR. CALL ENDEVOR TECHNICAL SUPPORT.
Reason:
Internal error.
Action:
C1U0910E
CCID ccid parm IS NOT DEFINED. ACTION DENIED.
Reason:
The CCID specified for an action was not defined in the CCID Validation Data Set.
Action:
Verify that the specified CCID is correct.
C1U0911E
INVALID CALL PARAMETERS. CALL ENDEVOR TECHNICAL SUPPORT.
Reason:
Internal error.
Action:
C1U0912E
UNSUPPORTED ACTION. CALL ENDEVOR TECHNICAL SUPPORT.
Reason:
Internal error.
Action:
C1U Messages
C1U0913E
INTERNAL LOGIC ERROR. CALL ENDEVOR TECHNICAL SUPPORT.
Reason:
Internal error.
Action:
C1U0915E
ACTION DENIED. CCID VALIDATION DATASET (C1DEFLTS CIPODSN) COULD NOT BE
ALLOCATED.
Reason:
An error occurred while attempting to allocate the CCID Validation Data Set, so the
action was denied.
Action:
For more information, see the associated allocation error messages.
C1U0917E
DATASET VALIDATE FAILED FOR C1DEFLTS CIPODSN (SSDVLD RCODE = return code.)
Reason:
The CCID Validation Data Set has incorrect DCB attributes.
Action:
Make sure that the CCID Validation Data Set is allocated as follows:
DSORG=PS,RECFM=F(FB),LRECL=80.
C1U0918E
CCID VALIDATION DATA SET HAS IMPROPER FORMAT: MUST BE DSORG=PS,
RECFM=F(B), LRECL=80
Reason:
The CCID Validation Data Set has incorrect DCB attributes.
Action:
Make sure that the CCID Validation Data Set is allocated as follows:
DSORG=PS,RECFM=F(FB),LRECL=80.
C1U Messages
C1U0919E
CCID ccid parm IS DEFINED BUT YOU CANNOT USE IT FOR THAT ELEMENT.
Reason:
The CCID specified for the action is not eligible for use with the element.
Action:
Verify that the specified CCID is correct and if it is, update the CCID Validation Data Set.
C1U0920E
I/O ERROR READING C1DEFLTS CIPODSN (GIOX RC=X return code SVC RC=X return
code.
Reason:
Internal error.
Action:
C1U0970E
RETRIEVE ACTION DENIED - REPLACE=N SPECIFIED AND OBJECT EXISTS IN NATURAL
LIBRARY
Reason:
A Retrieve request for an element name found a member with that name already exists
in the target Natural library.
Action:
Re-execute the request, using a different Natural library as the destination, or enable
the replacement of the present member element name.
C1U0971E
DATASET VALIDATE FAILED FOR ddname O/P DDNAME(SSDVLD RCODE = return code)
Reason:
Internal error in the CA Endevor Integration for the Natural Environment BC1PNEX2 exit.
Action:
Contact your CA Endevor Integration for the Natural Environment administrator.
C1U Messages
C1U0972E
I/O ERROR READING DATASET (GIO RC=X return code SVC RC=X return code)
Reason:
Action:
C1U0973E
BC1PNEX2 INVALID $ECBDS - CALL ENDEVOR TECHNICAL SUPPORT
Reason:
Action:
C1U0974E
BC1PNEX2 INVALID $REQPDS - CALL ENDEVOR TECHNICAL SUPPORT
Reason:
Action:
C1U0975E
BC1PNEX2 INVALID $ENVDS - CALL ENDEVOR TECHNICAL SUPPORT
Reason:
Action:
C1U Messages
C1U0976E
BC1PNEX2 LOGIC ERROR - CALL ENDEVOR TECHNICAL SUPPORT
Reason:
Action:
C1U0977E
Reason:
Action:
C1U0978E
Reason:
Action:
C1U0990E
NDVREX4B - YOU ARE NOT AUTHORIZED FOR UPDATE ACCESS TO DATA SET data set
name
Reason:
User is in exit 4, the external data set exit. The exit has passed a ddname/data set back
to CA Endevor SCM that the user is unauthorized to update.
Action:
Contact your security administrator or the exit programmer to resolve.
C1U Messages
C1U0991E
NDVREX4B - UNEXPECTED RACF RESULT CODE - FAILING REQUEST
Reason:
This message is issued by the optional user exit program, NDVREX4.
Action:
Review the exit 4 program and check the RACF documentation.
C1U0992E
NDVREX4B - RACINIT ISSUED BY 3RD PARTY RACEHECK FAILED - RACINIT RC=return
code
Reason:
Action:
C1U0992E
NDVREX4B - UNEXPECTED RACROUTE FAILURE - RC= return code
Reason:
Action:
C1V Messages
C1V Messages
C1V0001E
CALL TO BSTPCOMP FAILED WITH RC return code
Reason:
The standalone COMPARE utility has rejected a PDM COMPARE operation.
Action:
For more information, check the BSTPCOMP return codes listed in the Utilities Guide.
C1V0003E
STORAGE UNAVAILABLE:INCREASE REGION SIZE
Reason:
PDM was unable to obtain sufficient virtual storage to perform the requested function.
Either a region specification on a job statement was too small, or a TSO logon region
size was insufficient.
Action:
If the error occurred during background operation, increase the region size requested
on the job statement. If the error occurred in foreground, log on to TSO with a bigger
region size.
C1V0040E
NO MEMBERS OR ELEMENTS FOUND FOR location
Reason:
An input to the Build WIP process was not located. The member or element specified for
[INPUT] location was not found in that location.
Action:
Check that the PDM input syntax language specified the information location correctly.
If the problem persists, verify that the CA Endevor SCM location exists.
C1X Messages
C1X Messages
C1X0001I
The ASXBSENV and ASXBUSER values were forced from the alternate id to the user id
at processor end
Reason:
The processor step included an OPEN of LGNT$$$I to force the ASXBSENV and
ASXBUSER fields to those of the alternate id. However, the corresponding LGNT$$$O
OPEN was not done. In this case, CA Endevor SCM reset the ASXBSENV and ASXBUSER
fields back to their original values when the processor step ended.
Action:
None
C1X0003E
RC=severity code ERROR ACCESSING vsam ddname MASTER FILE
Reason:
An open request was issued against the Master Control File for the indicated stage. An
open error was encountered.
Action:
Make sure that the specified C1DEFLTS found in the files CONLIB and STEPLIB correctly
define the Stage 1 Master Control File for which the action was requested. Verify that
the VSAM file DSNAME exists and is available.
C1X0004E
RC=vsam error code VSAM ERROR ACCESSING dsname
Reason:
An error was encountered when attempting to open the VSAM master file.
Action:
See the appropriate IBM VSAM manual to determine the cause of the error.
C1X Messages
C1X0005E
VSAM ERROR RC return code FDBK feedback DSN data set name
Reason:
An error was detected when attempting to read, write, or delete a record from a VSAM
file. The name of the current data set is displayed.
Action:
Look up the VSAM return code and feedback to determine the cause of this condition.
C1X0006E
C1DEFLTS ELM CTLG NAME DIFFERENT THAN LAST ELM CTLGUSED: CTLGUSED: catalog
data set name
Reason:
A stage record was successfully read. The name of the catalog in the stage record is
different than the name of the catalog found in the defaults table.
Action:
Verify that you are picking up the correct C1DEFLTS table. If you are using the correct
CIDEFLTS table, run BC1JXCNM to synchronize your catalog with the MCFs.
C1X0007E
CANNOT CONSTRUCT THE EINDEX NAME FROM THE CATALOG NAME. IT CANNOT BE
GREATER THAN 37 CHARACTERS.
Reason:
The catalog name is too large.
Action:
Create a catalog name that is 37 characters or less.
C1X Messages
C1X0008C
UNABLE TO LOCATE INCLUDE ELEMENT element name REFERENCED BY element name
Reason:
Unable to expand INCLUDEs found in the requested element.
Action:
Verify that the INCLUDE library definitions specified in the Stage 1 and Stage 2 type
definitions are correct and contain the INCLUDE members.
C1X0009E
RECURSIVE REFERENCE TO INCLUDE MEMBER member name DETECTED WHILE
EXPANDING INCLUDE MEMBER member name
Reason:
A reference to a previously specified INCLUDE module would result in an endless loop.
Action:
Make sure that, when nesting INCLUDE modules, not to include a previously specified
INCLUDE module (that is, remove all recursive calls to previously referenced INCLUDE
modules).
C1X0010I
STEP step name PROGRAM program name COMPLETED, RC = return code
Reason:
This is an informational message which displays the highest return code associated with
the indicated processor.
Action:
None. You should review these processor return codes to verify that the requested
action successfully completed.
C1X Messages
C1X0011S
STEP step name PROGRAM program name ABENDED, CODE = return code
Reason:
A processor has abended. The message indicates the abend code associated with the
abended processor.
Action:
Review the messages displayed prior to this message and check the appropriate IBM
Error Codes and Messages manual. If the abend code BADGU is displayed, it means the
program named in this message is not supported in a processor.
C1X0012I
STEP step name INVOKING PROGRAM program name
Reason:
This is an informational message that indicates the name of the processor to be
executed.
Action:
None. In the event that an error is encountered in a processor to follow, this message
gives an indication of the element name which was executed.
C1X0013I
PARM = parameter
Reason:
This is an informational message that indicates the parameter passed to the program as
displayed in message C1X0012I. This is useful in verifying parameter values passed as
input to a particular program. Substituted symbolics are displayed.
Action:
None. If an error is encountered during processor execution, information displayed in
the PARM=VALUE may be useful to verify that the processor is executing against the
correct system, element, and so on.
C1X Messages
C1X0014I
STEP step number (name) NOT EXECUTED BECAUSE OF CONDITION CODE(S)
Reason:
The step identified in the message was not executed because of the COND parameter
specification on the EXEC statement.
Action:
None.
C1X0015I
STEP step number (name) NOT EXECUTED BECAUSE OF AN "EXECIF" CLAUSE
Reason:
The step identified in the message was not executed because it did not meet the
conditions set in the EXECIF parameter.
Action:
None.
C1X0016E
ERROR IN processor name PROCESSOR DEFINITION - INVALID COND CLAUSE
Reason:
The COND parameter is specified incorrectly in the processor identified in the message.
Action:
Correct the COND parameter specification.
C1X0017E
ERROR IN processor name PROCESSOR DEFINITION - UNABLE TO RESOLVE STEP NAME
IN COND PARM FOR STEP step number.
Reason:
The step name specified in the COND parameter is not defined in the processor
Action:
Correct the COND parameter specification.
C1X Messages
C1X0018E
ERROR IN processor id PROCESSOR DEFINITION - NO OUTPUT DD STATEMENT WAS
SPECIFIED IN THE CONWRITE STEP step
Reason:
The CONWRITE utility requires the specification of a DD statement that is used as
output. CONWRITE writes the output to the first DD statement, after the EXEC
statement that does not begin with the characters C1INCL. This statement is missing.
Action:
Add the DD statement to the processor.
C1X0019E
THIS PROCESSOR MUST BE REGENERATED IT CONTAINS IF-THEN-ELSE STMTS FROM
ENDEVOR RELEASE 3.72
Reason:
Indicates that a processor from a previous CA Endevor SCM release with IF-THEN-ELSE
statements was encountered.
Action:
C1X0030E
ELM EXTENSION DEFINE FUNCTION CALLED WITH AN INVALID PATH AREA
Reason:
Internal error. The PATH area passed to this program contains an invalid length. This
error was detected by the element extension subroutine, BC1PEEXT.
Action:
C1X Messages
C1X0031E
VSAM I/O ERROR ON ELM EXTENSION CREATE/DELETE/UPDATE FUNCTION AGAINST
DDNAME ddname, RC= return code, FEEDBK= feedback code
Reason:
A VSAM error was detected while attempting to create, delete, or update an element
extension record in the master control file.
Action:
Look up the VSAM return code and feedback code to determine the cause of this
problem.
C1X0032E
ELM EXTENSION RCD NOT FOUND ON DDNAME ddname, KEY= record key DURING
CREATE/DELETE/UPDATE RETRIEVE TO/ADD FROM FUNCTION
Reason:
An element extension record was not found.
Action:
C1X0033E
ELEMENT RCD DOES NOT CONTAIN A VALID EXTENSION KEY, KEY= record key
Reason:
Internal error. The key to access an extension record is stored in the element record.
The value found at this location is not a valid extension key.
Action:
C1X Messages
C1X0034E
ELEMENT EXTENSION "TO" LIBRARY DELETION FAILED, KEY= record key, ENV
environment name STG stage id
Reason:
Internal error. The delete of the element extension "TO" library record failed. The key of
the extension record and the environment and stage ID are displayed.
Action:
C1X0100E
RC=return code message [INTERNAL FUNCTION] ERROR ATTEMPTING action FOR
dsname (member name)
Reason:
See the following corrective Action.
Action:
For the error messages associated with the indicated error, see the appropriate library
management documentation.
C1X0102E
LIBRARIAN utility return code ERROR: RC=return code - [READ ACCESS RETURN CODE]
Reason:
A CA Librarian error was encountered.
Action:
See the appropriate library management documentation for the error messages
associated with the indicated error.
C1X Messages
C1X0103C
ELEMENT WAS FOUND AT PHYSICAL PATH LOCATION ENV/environment name
SYS/system name SBS/subsystem name STAGE/stage id
Reason:
A version of the element was found at the named location, which is in a mapped
environment but is not on the current map route.
Action:
See message C1X0104E.
C1X0103W
Reason:
Action:
C1X0103I
Reason:
Action:
C1X Messages
C1X0104E
JUMP OPTION IS REQUIRED FOR SYSTEM system name TO BYPASS THE ELEMENT IN
THE PHYSICAL PATH
Reason:
The system named in the message requires that MOVE actions be specified with
JUMP=Y when CA Endevor SCM encounters a version of the element(s) to be moved in a
mapped environment, but not on the map.
Action:
Resubmit the MOVE request with JUMP=Y.
C1X0201E
STMT statement number INVALID--NAME OPERAND EXCEEDS 8 CHARACTERS
Reason:
The NAME operand in the statement identified in the message contains more than eight
characters. Only eight characters are allowed.
Action:
Correct the statement and resubmit.
C1X0202E
STMT statement number INVALID statement
Reason:
A JCL error was encountered during the Scan 1 phase of JCL translation. Scan 1 errors
are typically due to omitting a comma when attempting to continue a JCL statement to a
second line.
Action:
Review the JCL statement in error, correct the problem, and reprocess the JCL.
C1X Messages
C1X0203E
STMT statement number INVALID--REQUIRED PARAMETER "PGM" MUST BE THE FIRST
PARAMETER ON THE EXECUTE STATEMENT
Reason:
The statement identified in the message is an EXECUTE statement, but does not have
PGM as its first parameter.
Action:
C1X0204E
STMT statement number INVALID--REFERBACK NOT SUPPORTED ON THE "PGM"
PARAMETER
Reason:
A referback was specified for the PGM parameter.
Action:
Change the referback to an explicit specification.
C1X0205W
STMT statement number INVALID--KEYWORD keyword IS NOT SUPPORTED
Reason:
The keyword identified in the message is not supported as used in the statement
Action:
C1X0206E
STMT statement number INVALID--KEYWORD keyword IS NOT SUPPORTED
Reason:
The keyword identified in the message is not supported as used in the statement
Action:
C1X Messages
C1X0207E
STMT statement number INVALID--CONTAINS UNBALANCED PARENTHESES
Reason:
Nesting specified in the indicated JCL statement is invalid.
Action:
Make sure that parentheses are properly balanced, correct the error, and resubmit the
JCL.
C1X0208E
STMT statement number INVALID--CONTAINS UNBALANCED QUOTES
Reason:
Nesting specified in the indicated JCL statement is invalid.
Action:
Make sure that quotes are properly balanced, correct the error, and resubmit the JCL.
C1X0209E
STMT statement number INVALID--CONTAINS ILLEGAL FORMAT
Reason:
During scan 1 of JCL translation, the JCL statement that was indicated was invalid,
probably due to improper continuation specification.
Action:
Make sure that the JCL statement was specified correctly, correct the error, and
resubmit the job.
C1X0210E
STMT statement number INVALID--CONTAINS INVALID KEYWORD: keyword
Reason:
The JCL statement specified an unknown keyword that was flagged as an error.
Action:
Make sure that the keyword flagged is a valid JCL keyword as shown in the appropriate
JCL reference book. Correct the keyword and resubmit the job.
C1X Messages
C1X0211E
STMT statement number INVALID--COND PARAM VALUE LONGER THAN nnn
CHARACTERS
Reason:
The COND= parameter was improperly specified.
Action:
For details about the COND=parameter, see the Extended Processors Guide. Correct the
COND= parameter and resubmit the job.
C1X0212E
STMT statement number INVALID--IMPROPER EVEN/ONLY SPECIFICATION IN THE
COND PARAMETER
Reason:
The COND parameter in the statement identified in the message contains improper
coding of the EVEN/ONLY specification.
Action:
Correct the EVEN/ONLY syntax and resubmit.
C1X0213E
STMT statement number INVALID--FOOTPRINT PARAM CONTAINS INVALID VALUE
Reason:
The footprint parameter is improperly coded.
Action:
For a list of the valid values that can be specified for the FOOTPRINT= parameter, see
the Extended Processors Guide.
C1X0214E
STMT statement number INVALID--DDNAME IS REQUIRED
Reason:
A DD statement was coded in the processor but no DDname was specified.
Action:
Correct the format of the DD statement.
C1X Messages
C1X0215E
STMT statement number INVALID--NUMERIC VALUE EXPECTED IN FIELD field name
Reason:
The statement identified in the message allows other than a numeric value for the field
identified in the message. However, the field requires numeric values.
Action:
C1X0216E
STMT statement number INVALID--DLM SPECIFICATION IS IN ERROR
Reason:
The DLM parameter in the statement identified in the message was coded incorrectly.
Action:
C1X0217E
STMT statement number INVALID--TOO MANY POSITIONAL PARAMETERS IN FIELD
field name
Reason:
The field identified in the message was assigned too many positional parameters in the
statement identified in the message.
Action:
C1X Messages
C1X0218E
STMT statement number INVALID--EXPECTING KEYWORD OPERAND
Reason:
1) The statement identified in the message contains a keyword that must be used with
an operand, but the operand is missing.
2) If the error occurs on the first statement in the processor, the probable cause is an
invalid symbol defined on the proc statement.
Action:
1) Correct the statement and resubmit.
2) Check all the variable names defined on the proc statment. Correct any that are nine
or more characters in length and resubmit.
C1X0219E
STMT statement number INVALID--DLM IS ONLY VALID IN COMBINATION WITH A
SYSIN DATASTREAM
Reason:
The DLM parameter in the statement identified in the message was not coded as part of
a SYSIN statement. The DLM parameter is only valid when it is coded as part of a SYSIN
statement.
Action:
C1X0220E
STMT statement number INVALID--MUTUALLY EXCLUSIVE FIELDS field1 name AND
field2 name SPECIFIED
Reason:
The two fields identified in the message cannot be coded in the same statement.
Action:
C1X Messages
C1X0221E
UNDEFINED SYMBOLIC PARAMETER - parameter
Reason:
There is a symbolic in this statement that is not a CA Endevor SCM symbolic and is not
defined in the PROC statement.
Action:
Make sure that the symbolic is coded correctly. Include it in the PROC statement if
necessary.
C1X0222E
STMT statement number INVALID--EXECIF PARAM VALUE LONGER THAN nnn
CHARACTERS
Reason:
One or both of the values in the EXECIF statement of the statement identified in the
message has more than 999 characters.
Action:
Correct the EXECIF statement and resubmit.
C1X0223E
STMT statement-number INVALID--FOOTPRNT, MONITOR AND DSN KEYWORDS NOT
ALLOWED WITH PATH
Reason:
The PATH keyword was specified on the DD statement. The FOOTPRNT, MONITOR, and
DSN keywords cannot be specified along with the PATH keyword.
Action:
If using a PATH, remove the FOOTPRNT and MONITOR keywords from the statement. If
using a DSN, remove the PATH keyword from the statement.
C1X Messages
C1X0224E
STMT statement number INVALID--INVALID OPERATOR IN parameter name
PARAMETER - EQ,NE,GT,GE,LT,LE
Reason:
The operator coded in the parameter identified in the message is not one of the
following: EQ, NE, GT, GE, LT, LE.
Action:
Correct the parameter specification and resubmit.
C1X0226E
STMT statement number INVALID--SYNTAX ERROR, TOO MANY SUBFIELDS IN
parameter name PARAMETER
Reason:
The parameter identified in the message specifies more than the allowed number of
subfields.
Action:
C1X0228E
STMT statement number INVALID--OPERATOR MISSING FROM parameter name
PARAMETER
Reason:
The parameter identified in the message does not specify an operator.
Action:
Correct the parameter specification using one of the following operators: EQ, NE, GT,
GE, LT, LE.
C1X Messages
C1X0230E
STMT statement number INVALID--SYNTAX ERROR IN parameter name PARAMETER
Reason:
The parameter identified in the message was coded incorrectly.
Action:
C1X0231E
STMT statement number INVALID - EXPECTING CONTINUATION CARD
Reason:
A JCL statement was improperly continued.
Action:
Make sure that the JCL statement flagged in error is properly continued. For a
description of continuing JCL statements, see the appropriate IBM JCL manual.
C1X0232E
STMT statement number INVALID--NON-JCL CARD ENCOUNTERED PRIOR TO FIRST
STEP
Reason:
A non-JCL statement was encountered prior to the first EXEC statement.
Action:
Remove the non-JCL statement.
C1X0233E
STMT statement number INVALID--EXCESSIVE PARAMETER LENGTH (>nnn CHARS) FOR
KEYWORD keyword
Reason:
The statement identified in the message contains an invalid length specification for the
keyword identified in the message.
Action:
Recode the statement and resubmit.
C1X Messages
C1X0234E
STMT statement number INVALID--EXPECTING CONTINUATION CARD, NULL CARD
ENCOUNTERED
Reason:
The statement prior to the statement identified in the message was continued, however
the statement identified in this message is a null (end-of-job) statement.
Action:
Correct the JCL.
C1X0236E
STMT statement number INVALID--EXPECTING CONTINUATION CARD, END OF FILE
ENCOUNTERED
Reason:
The statement prior to the statement identified in the message was continued, however
the statement identified in this message is not a valid continued JCL statement.
Action:
Correct the JCL.
C1X0237E
STMT statement number INVALID--IF-THEN-ELSE EXPRESSIONS MUST BE CONTAINED
IN PARENTHESES
Reason:
The expression must be enclosed in parentheses.
Action:
Correct the syntax error in this statement.
C1X Messages
C1X0238E
STMT statement number INVALID USE OF QUOTES
Reason:
The statement identified in the message contains quotes that are either used
improperly or placed incorrectly.
Action:
Modify the statement as necessary, and then resubmit.
C1X0239E
STMT statement number INVALID USE OF PARENTHESIS
Reason:
The statement identified in the message contains parentheses that are either used
improperly or placed incorrectly.
Action:
Modify the statement as necessary, and then resubmit.
C1X0240I
jcl statement and line number
Reason:
This is an informational message. The JCL statement and associated line number are
shown. Use this information to aid in the debugging of any messages which will appear
following the input JCL.
Action:
None.
C1X Messages
C1X0241E
STMT statement number INVALID--PARM= VALUE EXPANDS TO GREATER THAN MAX
ALLOWED (nnn CHARS)
Reason:
A PARM= value was greater than 100 characters.
Action:
Make sure that the PARM= value does not exceed 100 characters. For a description of
coding the PARM= parameter, see the appropriate IBM JCL manual.
C1X0242E
STMT statement number INVALID--USER SYMBOLICS MAY NOT BEGIN WITH "C1",
RESERVED FOR ENDEVOR USE
Reason:
One or more symbolics defined in the PROC statement begin with C1.
Action:
Correct the symbolic specification.
C1X0243E
STMT statement number INVALID--USER SYMBOLICS MAY NOT CONTAIN
AMPERSANDS
Reason:
One or more symbolics defined in the PROC statement contain an ampersand.
Action:
Correct the symbolic specification.
C1X0244E
DUPLICATE KEYWORD FOUND - keyword
Reason:
The DCB subparameter duplicates an ESA keyword coded outside the DCB.
Action:
Change either the DCB information, or the external keyword.
C1X Messages
C1X0245E
DSNAME MAY BE TRUNCATED: DEFINED LENGTH CAN BE UP TO nn BYTES, DEPENDING
ON JOBNAME
Reason:
Internal error. The size of the data set name exceeds the maximum allowed. This could
happen when a temporary data set name is generated by CA Endevor SCM.
Action:
C1X0245W
DSNAME MAY BE TRUNCATED: DEFINED LENGTH CAN BE UP TO nn BYTES, DEPENDING
ON JOBNAME
Reason:
The size of the data set name exceeds the maximum allowed. This could happen when a
temporary data set name is generated by CA Endevor SCM.
Action:
C1X0249E
STMT statement number INVALID--RIGHT COMPARATOR MISSING FROM EXECIF
CLAUSE
Reason:
EXECIF clause syntax require the specification of two values for comparison. The EXECIF
clause in this statement does not specify the second value.
Action:
Specify the second value and resubmit.
C1X Messages
C1X0250W
ddname IS A RESERVED ENDEVOR DDNAME - ALLOCATION REQUEST NOT PERFORMED
Reason:
The DDNAME shown in the message is a DDNAME that CA Endevor SCM retains for its
own use.
Action:
Specify a DDNAME other than the DDNAME shown in the message. If the DDNAME
shown in the message cannot be changed, contact your administrator for assistance.
C1X0251E
INVALID PARAMETER SPECIFIED FOR keyword KEYWORD: parameter
Reason:
The format of syntax associated with this keyword is invalid. The parameter is invalid or
missing.
Action:
For the proper syntax format of this keyword, see the SCL Reference Guide.
C1X0260W
REQUIRED THEN CLAUSE IS MISSING ON IF-THEN STATEMENT
Reason:
A THEN clause is missing on an IF-THEN statement.
Action:
Correct the syntax.
C1X0261E
INVALID EXPRESSION ELEMENT element; TRUE OR FALSE EXPECTED
Reason:
During processing, the IF clause discovered an invalid element.
Action:
Correct the syntax.
C1X Messages
C1X0262E
INVALID REFERBACK. THE REFERENCED STEP stepname IS NOT IN PROCESSOR
Reason:
A referback to the indicated stepname is invalid because the stepname is not in the
processor.
Action:
Correct the syntax.
C1X0263E
AN ERROR OCCURRED PARSING IF-THEN-ELSE, RC(return code), +
Reason:
Parsing an IF-THEN-ELSE caused an error.
Action:
Correct the syntax. If the error persists, note the return and reason code in the error
message and contact CA Technical Support. The return code and reason code that
appear is for use by CA Technical Support as an aid to help locate and debug
IF-THEN-ELSE issues that cannot be resolved by correcting the syntax.
C1X0264E
INVALID EXPRESSION OPERATOR (operator)
Reason:
The indicated expression operator is invalid.
Action:
Correct the syntax. Valid operators are GT, LT, NG, NL, EQ, NE, GE, LE, NOT, AND, OR.
C1X0265E
RUN EXPRESSION REQUIRES STEP REFERBACK
Reason:
The RUN expression is specified in the IF-THEN-ELSE logic. This expression requires a
refer back step name (IF RUN.stepname=TRUE).
Action:
Modify the syntax to include a refer back step name.
C1X Messages
C1X0266E
INVALID REFERBACK VALUE referback step name
Reason:
The refer back step name does not exist.
Action:
Make sure the step name is spelled correctly.
C1X0270E
MISMATCHED IF-ENDIF PAIR: unmatched if statement| unmatched endif statement
Reason:
The number of IF and ENDIF statements do not match. The message text indicates if
there are more IF or ENDIF statements.
Action:
Modify the processor syntax and make sure all the IF statements are paired with ENDIF
statements.
C1X0500E
INVALID SYNTAX IN INPUT DATA
Reason:
The control statement read from SYSIN contained invalid syntax.
Action:
Correct the syntax.
C1X0501W
MEMBER member name NOT FOUND IN ANY INPUT LIBRARY
Reason:
The member identified in the message does not exist in the input library.
Action:
Make sure that the member name was specified correctly on the input control
statement.
C1X Messages
C1X0502I
MEMBER member name SUCCESSFULLY COPIED
Reason:
Informational message. The member identified in the message was successfully copied.
Action:
None.
C1X0503E
MEMBER member name RESIDES IN OUTPUT LIBRARY AND REPLACE NOT SPECIFIED
Reason:
The input control statement specifies a member that currently exists in the output
library, however, REPLACE was not specified on the control statement.
Action:
Specify REPLACE on the control statement.
C1X0504E
COMPRESS NOT SUPPORTED: input ddname SAME AS output ddname
Reason:
A COMPRESS was requested, but BSTCOPY does not support the IEBCOPY COMPRESS
function.
Action:
If a COMPRESS is desired, specify IEBCOPY instead of BSTCOPY.
C1X0505E
DSORG OF dsorg NOT SUPPORTED
Reason:
The data set organization specified in the message is not supported by BSTCOPY.
BSTCOPY only supports an organization of PO.
Action:
Use IEBCOPY instead of BSTCOPY.
C1X Messages
C1X0506E
ROOT MODULE member name NOT SELECTED WITH ALIAS member name
Reason:
One or more aliases were specified on the input control statement(s), however their
root member was not specified.
Action:
Root members must be copied with aliases.
C1X0507E
THE BLKSIZE OF THE INPUT DATA SET IS > THE BLKSIZE OF THE OUTPUT DATA SET
Reason:
BSTCOPY has determined that the block size for the input data set is greater than the
block size for the output data set. This condition cannot exist when RECFM=U.
Action:
Make sure that the block size is the same at the source and the target of BSTCOPY
statements.
C1X0508E
SCATTERED OR OVERLAY NOT ALLOWED (member name)
Reason:
The member name identified in the message is in overlay or SCATTER format.
Action:
Use IEBCOPY instead of BSTCOPY.
C1X0509E
BEGINNING TTR EQUAL TO TEXT TTR
Reason:
BSTCOPY detected a load module that is invalid because the beginning TTR is equal to
the text TTR.
Action:
Regenerate the element associated with the load module.
C1X Messages
C1X0510E
INVALID SELECT FORMAT FOR HEX MEMBER NAME SUPPORT
Reason:
When using BSTCOPY to copy a member with a non-standard name (non-alphanumeric
characters) the following rules must be followed:
Only one member can be copied per SELECT statement.
The format of the statement must be one of the following: SELECT M=((member
name)) SELECT M=((member name, member name))
In this example, the member name must be exactly eight characters long.
If the REPLACE option is desired, it must be coded as part of the INDD keyword of
the COPY statement.
Action:
Correct the BSTCOPY request and resubmit.
C1X0511I
text
Reason:
The text in this message echoes BSTCOPY input statements, and displays input and
output data set names used by BSTCOPY.
Action:
None.
C1X0512E
VALIDATION ERROR, RECFM INCOMPATIBLE: source ddname(recfm) target
ddname(recfm)
Reason:
The RECFM at the source location of a BSTCOPY statement is not the same as the
RECFM at the target.
Action:
Make sure that the RECFM is the same at the source and the target of BSTCOPY
statements.
C1X Messages
C1X0513E
ERROR ACCESSING SYSIN FILE
Reason:
An error was encountered accessing the SYSIN file.
Action:
Make sure that the SYSIN file is present and pointing to the input stream.
C1X0514W
INPUT LIBRARY ddname CONTAINS NO MEMBERS
Reason:
The input library specified in the BSTCOPY processor step contains no members.
Action:
Make sure the library name is correct. If not, correct the processor and re-execute the
action.
C1X0515E
< I/O operation 1 > IN SHIPPED PKG AND < I/O operation 2 > IN SUPERSEDING PKG
INDICATE OUT OF SEQUENCE CONDITION
Reason:
An operation was performed on a member, after the package that is being shipped was
executed, and before the superseding package was executed. The member may have
been updated in another package, but under a different element type. Another
possibility is that the member was updated under the same element name and type, but
outside of package processing.
Action:
Investigate to find out what has happened to the member between the two package
executions. Recover the member as indicated by the situation.
C1Y Messages
C1Y Messages
C1Y messages are generated during processing. The following list of C1Y messages
includes possible causes and corrective actions to take in error situations.
C1Y0001E
AN I/O ERROR OCCURRED WHILE ATTEMPTING text ddname DDNAME
Reason:
An I/O error occurred when attempting to perform some activity against the DDNAME
Action:
Make sure the DDNAME is correctly specified. Correct the action and retry.
C1Y0002E
PREMATURE END OF FILE ENCOUNTERED WHILE READING ENDEVOR ARCHIVE FILE
ALLOCATED TO DDNAME ddname
Reason:
The file containing archived or transferred elements does not contain a logical
end-of-file.
Action:
Make sure the input specified to the RESTORE or TRANSFER action contains CA Endevor
SCM information. If the file contains elements, contact your administrator.
C1Y0003E
SEQUENCE ERROR ENCOUNTERED WHILE READING ENDEVOR ARCHIVE FILE
ALLOCATED TO DDNAME ddname
Reason:
The file containing archived or transferred elements contains archived information that
is not in the proper sequence as required by the RESTORE or TRANSFER action.
Action:
Make sure that the input specified to the RESTORE or TRANSFER action contains CA
Endevor SCM information. If the file contains elements, contact your administrator.
C1Y Messages
C1Y0006E
THE PREVIOUS $SMR ERROR HAS TERMINATED PROCESSING
Reason:
See the previous message.
Action:
Act on the previous message.
C1Y0007E
THE OUTPUT RECORD LENGTH (length) EXCEEDS THE OUTPUT BUFFER SIZE (size)
Reason:
The output record length exceeds the output buffer size.
Action:
Increase the LRECL and block size specifications for the data set.
C1Y0008E
THE ARCHIVE DATASET LRECL IS NOT LARGE ENOUGH. IT MUST BE AT LEAST (size).
Reason:
The minimum LRECL should be the greater of three times the maximum MCF-record
length or the TYPE-LENGTH plus (+) 14.
Action:
Increase the LRECL size specifications for the data set.
C1Y0012E
NO SELECTION INPUT FILE FOUND. JCL STMT //BSTIPT01 DD ....
Reason:
There was no input to perform any of the actions requested. Either an invalid library
name was specified, or there is an invalid member name within a data set.
Action:
Make sure the data set specified on the BSTIPT01 DD statement contains SCL syntax.
Correct the JCL and resubmit the job. If the job is being submitted from the background
panels, make sure that the JCL found in ISPSLIB associated with CA Endevor SCM
contains the BSTIPT01 DD statement.
C1Y Messages
C1Y0013E
ERROR ENCOUNTERED WHEN PARSING SYNTAX
Reason:
A syntax error was encountered by the SCL parser. This message appears after all input
is parsed.
Action:
Review the syntax and messages that precede this message. Correct any errors and
resubmit the job.
C1Y0014E
ERROR ENCOUNTERED WHEN PARSING SYNTAX. PROCESSING WILL BE TERMINATED.
Reason:
A syntax error was encountered by the SCL parser. This message appears after all input
is parsed.
Action:
Review the syntax and messages that precede this message. Correct any errors and
resubmit the job.
C1Y0015I
STARTING PARSE OF REQUEST CARDS
Reason:
The CA Endevor SCM syntax parser is beginning to parse the request cards.
Action:
None.
C1Y0016I
REQUEST CARDS SUCCESSFULLY PARSED
Reason:
Informational message. This message indicates that the syntax cards were successfully
parsed.
Action:
None.
C1Y Messages
C1Y0017W
REQUEST CARDS PARSED WITH WARNINGS
Reason:
Warning message. This message indicates that an incorrect option was specified.
Action:
Correct the SCL to avoid future warning messages.
C1Y0018E
DUPLICATE MEMBER NAME member name IN FILE ddname - DATA SET dsname
Reason:
A COPY or LIST function is directed to an existing member name, and the REPLACE
option was not specified.
Action:
Specify REPLACE, or choose a different target member name.
C1Y0025I
MEMBER member name SUCCESSFULLY COPIED
Reason:
Informational message. This message indicates that the member name was copied to
the target Restore data set.
Action:
None.
C1Y0026W
*** ERROR *** MEMBER member name NOT COPIED
Reason:
A COPY action failed. This message is preceded by an error message indicating the
reason.
Action:
Review other messages in the log to determine the cause of the problem.
C1Y Messages
C1Y0027E
THE COMBINATION OF BYPASS GENERATE PROCESSOR AND PROCESSOR GROUP YOU
HAVE CHOSEN IS ILLOGICAL
Reason:
The processor group you specified does not include a GENERATE processor, therefore
the BYPASS GENERATE PROCESSOR option will be ignored.
Action:
Make sure that you specified the correct processor group.
C1Y0028E
MUTUALLY EXCLUSIVE WHERE CLAUSES WERE CODED
Reason:
Two or more WHERE clauses in this job are mutually exclusive.
Action:
Make sure that all the WHERE clauses are compatible.
C1Y0029E
MAXIMUM LRECL OF 80 FOR PARSER INPUT IS SUPPORTED
Reason:
The maximum record length of the input file is 80. The attributes of the input file
indicate the record length is greater than 80.
Action:
Make sure the name of the input file is correct. If so, reallocate with a record length of
80.
C1Y0030E
CANNOT SPECIFY CCID "OF" AGAINST AN ARCHIVE FILE
Reason:
You have specified WHERE CCID OF as part of a LIST or TRANSFER request from an
archive file. This syntax is invalid.
Action:
Respecify the request using WHERE CCID.
C1Y Messages
C1Y0031E
"AUTOGEN" AND "BYPASS GENERATE PROCESSOR" ARE MUTUALLY EXCLUSIVE
Reason:
This message is issued when AUTOGEN is in effect. It indicates that both the AUTOGEN
and bypass generate processor options were specified on the same request. These two
options are mutually exclusive.
Action:
Review the options and remove the option you do not need.
C1Y0038I
END OF EXECUTION LOG - HIGHEST ENDEVOR RC = return code
Reason:
This message indicates the end of the execution log. The highest return code
encountered by the RESTORE program was return code.
Action:
None.
C1Y0040E
I/O ERROR ENCOUNTERED WHEN READING DATA SET dd-name
Reason:
A temporary file as indicated by the DDNAME encountered an I/O error. The file that
encountered the error may have been too small and may need to be increased to hold a
large element.
Action:
Verify that the template JCL associated with the RESTORE, COPY, or LIST action properly
defines all temporary files. The template JCL is described in the Installation Guide.
C1Y Messages
C1Y0041E
I/O ERROR ENCOUNTERED WHEN WRITING TO DSNAME data set name
Reason:
An I/O was detected while writing to the data set identified in the message.
Action:
Review other messages in the log to determine the cause of the problem.
C1Y0042E
ELEMENT element name ALREADY EXISTS AT STAGE stage id
Reason:
This element already exists at this stage.
Action:
A request to RESTORE an element into an environment, stage, system, subsystem, and
type was made. This message indicates that an element of same name already exists.
Action:
Delete the element in target stage, or RESTORE the element to a different CA Endevor
SCM location.
C1Y0043E
NEW VERSION CANNOT BE USED, ELEMENT FOUND UP THE MAP FROM:
env-name/stage-id/sys-name/sbs-name/type-name
Reason:
A request to RESTORE was made when this element already exists at the target location
or further up the map from the location specified in the message.
Action:
Delete the element.
C1Y Messages
C1Y0044C
COMPONENT LIST BASE IS CORRUPTED AND WAS NOT RESTORED
Reason:
The component list base in the archive file is corrupted.
Action:
The element is restored correctly, but the component list cannot be restored from the
archive. Re-generate the element to create a component list.
C1Y0053E
THE FOLLOWING ERROR OCCURRED WHILE PROCESSING ELEMENT element
Reason:
The ARCHIVE, LIST, or TRANSFER actions encountered an error processing an external
data set. The error is described in a message that follows message C1Y0053E.
Action:
For the appropriate corrective action, see the message that follows C1Y0053E.
C1Y0094E
REBUILD OF MERGED ELEMENT FAILED RC = return code
Reason:
The element and component base and delta records are being copied from an archive
file and merged into a file. The merge failed.
Action:
C1Y0100E
THE SCL INPUT FILE ddname DD STATEMENT IS NOT ALLOCATED
Reason:
BSTIPT01 or the DDNAME override specified in the first character string of the
C1BM3000 execution parameter is not allocated.
Action:
Provide a BSTIPT01 DD card or a DD card for the parameter override.
C1Y Messages
C1Y0101E
An invalid execution parameter was received the format of the parameter is SCLDD,
MSGDD, PACKAGEID, SUMMARYdd.
Reason:
The C1BM3000 execution parameter was incorrect. The parameter can contain up to
four parameters separated by commas. The first parameter is the override to the SCL
DDNAME (defaults to BSTIPT01) and can be up to any eight characters which constitute
a valid DDNAME; the second is the override to the message file DDNAME (defaults to
CONMSGS1); the third is the package ID; and the fourth is the override to the message
summary DDNAME (defaults to CONMSGS2).
This message is WTOd since it may be the message DDNAME which cannot be allocated.
In this case, nothing can be written to the messages data set.
Action:
Correct the parameter.
C1Y0102E
THE MESSAGE FILE ddname DD STATEMENT IS NOT ALLOCATED.
Reason:
The primary message data set, usually C1MSGS1, is not allocated. The system,
therefore, is not able to write any messages.
This message is WTOd since it may be the message DDNAME which cannot be allocated;
in this case, nothing can be written to the messages data set.
Action:
Correct the parameter.
C1Y0103W
THE RETAINAPI PARAMETER HAS BEEN IGNORED TO PREVENT POSSIBLE PROBLEM
Reason:
CA Endevor SCM turned off the RETAINAPI parameter, because it would cause an
ABEND in this setup. The BC1PCSV0 utility is attached and not linked or branched to.
Action:
Remove the RETAINAPI parameter or change the way the BC1PCSV0 utility is executed.
CIIO Messages
C1Y0274E
ELM TYPE for ELM element name IN ENV: environment name SYS: system name SBS:
subsystem name TYPE: type name STG: stage id NOT FOUND
Reason:
CA Endevor SCM cannot find the type definition named in the message.
Action:
Verify that the type name was specified correctly. Define the type if necessary.
CIIO Messages
CIIO050
INVALID REQUEST'
.ALARM=YES
'SX/BX/CX/HX/PX REQUIRE ACM OPTION WITH ASCM=Y SET IN C1DEFLTS.

Reason:
The ASCM value in the C1DEFLTS table is set to N, and the options BX, SX, CX, or HX on
the PACKAGE ELEMENT INFORMATION PANEL are selected.
Action:
ASCM=Y must be specified in the C1DEFLTS table to allow processing to continue.
CIIO082
VERSION NUMBER INVALID FOR UPDATE ACTION
Reason:
You cannot specify a new version number for an element UPDATE action. You can only
specify a new version number for the new element when using the ADD or TRANSFER
actions and only if the element is not already present at the target location.
Action:
Resubmit the UPDATE action without specifying a new version number.
CONRELE Messages
CONRELE Messages
This section lists error messages issued during CONRELE processing along with possible
CONRELE E001
INVALID COMMAND SYNTAX RECEIVED.
Reason:
An error occurred in the input syntax parsing.
Action:
Correct the syntax errors and reenter the command.
CONRELE E002
ELEMENT WAS NOT FOUND.
Reason:
The element was not included with the RELATE ELEMENT command.
Action:
Add the element to the RELATE ELEMENT command and reenter the command.
CONRELE E003
INPUT OR OUTPUT MUST BE SPECIFIED FOR ELEMENT, BUT NOT BOTH.
Reason:
Both the input component and the output component were specified with the RELATE
ELEMENT command.
Action:
Remove either the input component or the output component from the RELATE
ELEMENT command and reenter the command.
CONRELE Messages
CONRELE E004
INPUT OR OUTPUT MUST BE SPECIFIED FOR ELEMENT.
Reason:
An input clause or an output clause was not specified with the RELATE ELEMENT
command.
Action:
Add an input clause or an output clause to the RELATE ELEMENT command and reenter
the command.
CONRELE E005
ERROR OCCURRED ON ELEMENT. ENV: environment_name SYSTEM: system_name
SUBSYSTEM: subsystem_name NAME: element_name TYPE: type_name STG: stage_id.
Reason:
This message indicates the element (associated with the RELATE ELEMENT command)
where the error occurred. This message is followed by another message indicating the
type of error.
Action:
Read the following message and respond accordingly.
CONRELE E006
DATA SET NOT SPECIFIED. <- ERROR ON RELATE MEMBER COMMAND.
Reason:
The data set was not specified with the RELATE MEMBER command.
Action:
Add the data set to the RELATE MEMBER command and reenter the command.
CONRELE Messages
CONRELE E007
INPUT OR OUTPUT MUST BE SPECIFIED FOR MEMBER, BUT NOT BOTH.
Reason:
Both the input clause and the output clause were specified with the RELATE MEMBER
command.
Action:
Remove either the input clause or the output clause from the RELATE MEMBER
command and reenter the command.
CONRELE E008
INPUT OR OUTPUT MUST BE SPECIFIED FOR MEMBER.
Reason:
An input clause or an output clause must be specified with the RELATE MEMBER
command.
Action:
Specify an input clause or an output clause with the RELATE MEMBER command and
reenter the command.
CONRELE E009
UNABLE TO ALLOCATE DATA SET, RC = return_code
Reason:
This message indicates that the data set specified with the RELATE MEMBER command
could not be allocated.
Action:
Check the spelling of the data set name and verify that the data set exists.
CONRELE Messages
CONRELE E010
DATA SET FAILED VALIDATION, RC = return_code
Reason:
could not be validated.
Action:
CONRELE E011
UNABLE TO OPEN DATA SET, RC = return_code
Reason:
could not be opened.
Action:
CONRELE E012
UNABLE TO OBTAIN FOOTPRINT, RC = return_code
Reason:
This message indicates that the footprint for the member specified with the RELATE
MEMBER command could not be obtained.
Action:
Verify that a footprint exists for the data set member and run a processor to create a
footprint if a footprint does not exist.
CONRELE E013
ERROR OCCURRED ON MEMBER. DATA SET: data set_name MEMBER: member_name
Reason:
This message indicates the data set and the member where the error occured. See the
following message for the cause.
Action:
Read the following message and respond accordingly.
CONRELE Messages
CONRELE E014
STORAGE REQUEST FOR OBJECT FAILED: RC = return_code
Reason:
The storage request failed because of insufficient storage.
Action:
Note the return code and contact your administrator.
CONRELE E015
NO OBJECT DATA SPECIFIED FOR RELATE OBJECT COMMAND.
Reason:
The object data was not specified with the RELATE OBJECT command.
Action:
Add the data clause and reenter the command.
CONRELE E016
STORAGE REQUEST FOR COMMENT FAILED: RC = return_code
Reason:
The storage request failed because of insufficient storage.
Action:
Note the return code and contact your administrator.
CONRELE E017
NO COMMENT DATA SPECIFIED FOR RELATE COMMENT COMMAND.
Reason:
This message indicates that the comment data was not specified with the RELATE
COMMENT command.
Action:
Add the data clause and reenter the command.
CONRELE Messages
CONRELE E018
NO INPUT COMMANDS TO PROCESS.
Reason:
Use the CONRELE utility only if you have commands to process.
Action:
Do not use CONRELE if you do not have commands to process.
CONRELE I019
COMMANDS PROCESSED: command_count
Reason:
This message lists the number of commands processed.
Action:
None.
CONRELE I020
ELEMENT COMMANDS PROCESSED: command_count MEMBER OBJECT
COMMENT
Reason:
This message lists the number of ELEMENT, MEMBER, OBJECT, or COMMENT commands
processed.
Action:
None.
CONRELE I021
CONRELE PROCESSING SUCCESSFULLY COMPLETED.
Reason:
This message indicates that the CONRELE processing completed successfully.
Action:
None.
C2FM Messages
CONRELE E022
CONRELE PROCESSING COMPLETED WITH ERRORS, RC= return_code.
Reason:
The CONRELE processing completed with errors.
Action:
None.
C2FM Messages
This section details messages generated in the course of processing, specifically
regarding the CONSCAN Utility. Possible causes and corrective actions to take in error
situations are described. All CONSCAN utility messages are routed to SYSPRINT and the
z/OS console.
C2FM0001
INIT CPOOL ERROR - ABEND 999
Reason:
An attempt was made to initialize a CONSCAN control block, which is already defined.
Action:
C2FM0002
ADD CPOOL ERROR - ABEND 999
Reason:
An attempt was made to add a CONSCAN control block, which is already defined.
Action:
C2FM Messages
C2FM0003
GET CPOOL ERROR - ABEND 999
Reason:
An attempt was made to read a CONSCAN control block, which was not found.
Action:
C2FM0004
DEL CPOOL ERROR - ABEND 999
Reason:
An attempt was made to delete a CONSCAN control block; which was not found.
Action:
C2FM0005
FREE CPOOL ERROR - ABEND 999
Reason:
An attempt was made to free a CONSCAN control block, which was already defined.
Action:
C2FM0006
INSERT CPOOL ERROR - ABEND 999
Reason:
An attempt was made to insert an item in a CONSCAN control block, which was not
found.
Action:
C2FM Messages
C2FM0007
PARM FIELD IN ERROR
Reason:
During scanning, an error was detected in the PARMSCAN rules.
Action:
Review the output, correct the error, and rerun the scan.
C2FM0010
C2FSCANC C2FSCANC SCANCE COMMENT CARD IN ERROR
Reason:
A syntax error was detected in one of the COMMENT control cards.
Action:
Correct the syntax error and rerun the job.
C2FM0011
C2FSCANR C2FSCANR SCANCR CARD RULE IN ERROR
Reason:
A syntax error was detected in one of the SCANTYPE control cards.
Action:
Correct the syntax error and rerun the job.
C2FM000D
C2FM4000 RETURNED RC > 0
Reason:
A scanner subroutine returned a non-zero value.
Action:
Review the output files for the cause. If a secondary error message is not present,
contact your administrator.
C2FM Messages
C2FM000E
RC=4 - NO RECORD FOUND IN SCANNER
Reason:
The target element to scan is empty.
Action:
Either correct the target element so that it contains data, or choose another element
and rerun the scan.
C2FM000F
COMMENT DEFINITION IN ERROR
Reason:
A COMMENT syntax error was detected in the PARMSCAN rules member.
Action:
Correct the rules syntax and rerun the scan.
C2FM0010
RULE DEFINITION IN ERROR
Reason:
A RULES syntax error was detected in the PARMSCAN rules member.
Action:
Correct the rules syntax and rerun the scan.
C2FM001F
SYSPRINT DD Statement Missing
Reason:
The DD for SYSPRINT was missing from the supplied JCL.
Action:
Correct the JCL and rerun the job.
ECAP Messages
ECAP Messages
This section lists ECAP messages generated during Concurrent Action Processing, along
with possible causes and corrective actions to take in error situations.
ECAP001I
Concurrent Action Processing will be used to process actions.
Reason:
This message, written before the actions are dispatched, indicates that parallel
processing will be used for ADD, UPDATE, MOVE, DELETE, SIGNIN, RETRIEVE, GENERATE,
and TRANSFER (CA Endevor SCM to CA Endevor SCM) actions.
Action:
None.
ECAP002W
Uncatalogued data set found in SCL - text.
Reason:
A reference to an uncatalogued data set was found in the SCL. Concurrent Action
Processing will not be used to process actions. An uncatalogued data set can be a
temporary data set, a SYSOUT data set, or a data set with a disposition of NEW. The data
set name or the ddname specified is described in text.
Action:
None.
ECAP003W
Concurrent Action Processing cannot be used to process actions because Global Type
Sequencing is not enabled.
Reason:
This message appears if the user has requested Concurrent Action Processing by
specifying a SPAWNCNT greater than zero on C1DEFLTS or by using an EN$CAPnn DD
statement on the job JCL, but Global Type Sequencing has not been enabled. CA
Endevor SCM will terminate.
Action:
Enable Global Type Sequencing and resubmit the job.
ECAP Messages
ECAP004W
User is not authorized to request Endevor Concurrent Action Processing.
Reason:
You are not authorized to request that Concurrent Action processing be used. Element
actions will be processed serially.
Action:
Change the request so that it does not request Concurrent Action Processing, or contact
your CA Endevor SCM administrator.
ECAP005W
Invalid region count in ddname DD Statement-- Spawncnt value of nn substituted
Reason:
The last two digits of the ENCAP$nn DD statement are not valid. The last two digits are
used to specify the number of Concurrent Action Processing action request regions to
be spawned. The digits must be a two-digit numeric value of 00 or a number between
02 and the SPAWNMAX as defined in C1DEFLTS.
Action:
CA Endevor SCM uses the default number of action request processing regions as
specified in the C1DEFLTS SPAWNCNT value.
ECAP006W
Concurrent Action Processing will not be used because C1DEFLTS SPAWN value is N.
Reason:
An ENCAP$nn DD statement, which specifies the number of Concurrent Action
Processing servers, has been allocated. However Concurrent Action Processing is not
enabled because the C1DEFLTS SPAWN parameter is N. The job will continue using
nonparallel processing.
Action:
Remove the ENCAP$nn DD statement, or contact your CA Endevor SCM Administrator
regarding the C1DEFLTS SPAWN parameter value.
ECAP Messages
ECAP007W
EN$CAPnn exceeds C1DEFLTS SPAWNMAX value -- SPAWNCNT value will be used.
Reason:
An ENCAP$nn DD statement exists in the JCL, but the last two digits specify a value, nn,
that exceeds the SPAWNMAX value in C1DEFLTS. The SPAWNCNT value will be used.
Action:
None.
ECAP008S
program-name communication error -[SEND||RECEIVE||INIT||TERM] command
failed rc reason code description.
Reason:
A failure occurred when program program-name issued a CAICCI communication
request. The #CCI return code and error description are displayed. Concurrent
Processing is terminated. Any requests currently being processed are allowed to
terminate before CA Endevor SCM terminates.
Action:
ECAP009S
Concurrent Action Processing terminating termination reason.
Reason:
CA Endevor SCM is terminating because an action ended with a return code that
exceeded the STOPRC value, or a server has terminated abnormally.
Action:
Examine the C1MSG1 data set to determine the reason for termination. If the
termination occurred because the STOPRC value was exceeded, correct the problem
and try again. If a Concurrent Action Processing error occurred, contact your CA Endevor
SCM administrator.
ECAP Messages
ECAP010S
Message handler failure reason
Reason:
A failure occurred in the message management component of Concurrent Action
Processing.
Action:
ECAP011I
Concurrent action request region cci-id jobnumber jobname started.
Reason:
The action request region has been created. The cci-id uniquely identifies the server.
Action:
None
ECAP012S
Concurrent Action Processing cannot spawn cci-id RC rc description
Reason:
CA Endevor SCM was unable to spawn an action request processing region. The #CCI
return code and error description are displayed. CA Endevor SCM terminates. Cci-id
identifies the unique name that would have been assigned to the action request region.
Action:
ECAP Messages
ECAP013S
Concurrent action request region cci-id jobname jobnumber has terminated
unexpectedly
Reason:
The action request region has terminated. To determine the reason it ended
unexpectedly, check the previous messages in C1MSGS1 in both the request routing
region and action request region, as well as the JES log of the action request processing
address space.
Action:
ECAP014I
Maximum response time - nnnn seconds Action #action-num Statement #stmt-num
Reason:
The maximum response time for an action was nnnn seconds. The action that incurred
this time is Action # Statement#. This message is displayed after concurrent action
processing completes.
Action:
None.
ECAP015I
Average response time - nnnn seconds.
Reason:
The average response time across all action requests, that were processed by
concurrent action processing is nnnn seconds.
Action:
None.
ECAP Messages
ECAP016I
Minimum response time - nnnn seconds Action #action-num Statement #stmt-num
Reason:
The minimum response time for an action was nnnn seconds. The action that incurred
this time was Action # Statement#.
Action:
None.
ECAP017I
Accumulated response time - nnnnnnnn seconds
Reason:
The total of all response time values for all actions that were processed using
Concurrent Action Processing.
Action:
None.
ECAP018I
Action processing elapsed time - nnnnnnnn seconds.
Reason:
The amount of time that elapsed between the dispatch of the first action processed
until the completion of the last action processed by Concurrent Action Processing.
Action:
None.
ECAP019I
Concurrent action request region cci-id jobname jobnumber has terminated.
Reason:
The action request region has terminated.
Action:
None.
ECAP Messages
ECAP020I
Concurrent Action Processing ended
Reason:
The Concurrent Action Processing Facility has terminated. All acquired resources have
been released.
Action:
None.
ECAP022S
C1DEFLTS timestamp timestamp in cci-id jobname jobnumber does not match main
jobs timestamp.
Reason:
The C1DEFLTS module in the action request region is not the same C1DEFLTS used in the
request routing region. The timestamp value is used to determine whether the modules
match.
Action:
Either change the started task procedure or change the request routing region jobs JCL.
ECAP023W
Incomplete messages for act #nnnn stmt #nnnn from cci-id jobname jobnumber
Reason:
Not all C1MSGS1 messages for action #nnnn statement #nnnn were received from the
action request region. This was probably due to an error in that address space.
Action:
Examine the output of the action request region for any error messages. Contact your
CA Endevor SCM administrator.
ECAP Messages
ECAP024W
Concurrent Action Processing cannot be used - reason
Reason:
Although Concurrent Action processing was requested, it cannot be used, for the reason
explained in reason. Actions will be performed serially.
Action:
Correct the problem described in the message.
ECAP025S
Internal error : module routine explanation
Reason:
An unexpected error occurred in module routine. The error is explained in description.
Action:
ECAP026I
CAICCI ID complete cci-id
Reason:
This message shows the complete 30 character CAICCI ID of an action request region. It
follows those messages that display server information but list only the abbreviated 8
byte id of the action request region.
Action:
None.
ECAP027S
MVS Command Handler Failure - text
Reason:
The Command Handler task, which receives and processes MVS commands for
Concurrent Action Processing, has ended unexpectedly. The text contains the failure
reason.
Action:
ECAP Messages
ECAP028W
EN$CAP01 is invalid Concurrent Action Processing will not be used
Reason:
An EN$CAP01 DD statement was specified in the JCL. The number of action request
regions must be 0 or a number between 2 and the SPAWNMAX as defined in C1DEFLTS.
Actions will be processed serially.
Action:
Correct the EN$CAPnn DD statement.
ECAP029I
Concurrent Action Processing - text
Reason:
You issued an MVS Modify command to the Concurrent Action Processing main job. The
text shows the command you entered. The command will be processed and the results
displayed.
Action:
None.
ECAP032W
CONCURRENT ACTION PROCESSING CANNOT BE USED IF ONLY ONE ELEMENT IS BEING
PROCESSED
Reason:
Concurrent Action Processing was requested for the element actions, but the SCL
specified only one action that was eligible for concurrent processing. Because this
action contains no wildcards or placeholders, only one element will be processed. There
would be no benefit in using Concurrent Action Processing to process one element, and
so it is not used. Actions are processed serially.
Action:
Remove the EN$CAPnn DD card from the job to request serial processing of actions or
include more actions that are eligible for Concurrent Action Processing (ADD, UPDATE,
DELETE, RETRIEVE, MOVE, GENERATE, SIGNIN, TRANSFER from CA Endevor SCM to CA
Endevor SCM).
ECAP Messages
ECAP033I
CONCURRENT ACTION REQUEST REGION TERMINATED DUE TO A TIMEOUT
Reason:
A spawned action has exceeded the timeout limit.
Action:
The message indicates the jobname and job number of the spawned STCs that timed
out. Use this information to search the main job log to see the action, element, and
inventory location of the timed-out action. Information is also available in C1MSGS1.
ECAP034S
CONCURRENT ACTION PROCESSING HAS ENDED.
Reason:
One or more spawned actions have exceeded the timeout limit. A quiesce of all STCs is
forced and the tasks are terminated.
Action:
The main job log and ECAP033I messages in C1MSGS1 provide information about the
timed-out STCs. Check the main job and the STCs to try to determine the source of the
contention.
ECAP051I
REQUEST ROUTING REGION ADDRESS SPACE IS cci-id jobname jobnumber.
Reason:
This message lists the eight-byte abbreviated CCI ID for the request routing region
address space, as well as the jobname and jobnumber.
Action:
None.
ECAP Messages
ECAP060I
PROCESSED BY jobname - STC nnnnn
Reason:
This message is issued at the very beginning of every new action that runs in a spawned
STC, identifying the jobname and the STC number of the STC where the action is being
processed.
Action:
None.
ECAP100S
ACTION #nnnnnnnn / STMT #nnnnnnn
Reason:
The action and statement number associated with the error message immediately
preceding this message.
Action:
None.
ECAP200E
Invalid command - text
Reason:
The user issued an MVS MODIFY command but the syntax of the message was not
recognized. The first 30 bytes of the invalid command are shown in text.
Action:
Enter a valid command.
ENBE Messages
ENBE Messages
This section details messages generated in the course of Batch Environment
Administration Facility processing, along with possible causes and corrective actions to
take in error situations.
ENBE001I
Statement number Object number
Reason:
This message appears in the Action Execution report to identify the current action
number that is being processed. The statement number refers to the corresponding
action in the Control Statement Summary report. The SCL Object number is for the
number of the object associated with the SCL statement. This number is always 1 if the
object is not wildcarded. If the statement contains a wildcarded object name that
generates multiple SCL statements, the statement number remains the same and the
object number increments for each SCL statement generated.
Action:
None.
ENBE002I
Statement number
Reason:
This message appears in the Control Statement Summary report to identify the number
of the control statement that is being processed. The control statement numbers are
assigned sequentially beginning at one.
Action:
None.
ENBE003I
The control statements will not be executed at the users request
Reason:
The execution JCL contained the PARM=VALIDATE statement. The program only
validates the syntax of the control statements. The control statements are not executed.
Action:
None. However, to execute the actions, remove the PARM=VALIDATE statement from
the JCL.
ENBE Messages
ENBE004E
You are not authorized to perform the action object action
Reason:
You are not authorized to perform the Batch Environment Administration Facility action
identified.
Action:
Contact your administrator to obtain the necessary authorization to execute the Batch
Environment Administration Facility action.
ENBE005E
The ENESCLIN DD statement is not allocated
Reason:
The execution JCL did not contain the ENESCLIN DD statement. The ENESCLIN DD
statement contains the Batch Environment Administration Facility control statements
(SCL).
Action:
Add a valid ENESCLIN DD statement to the execution JCL and resubmit the JCL.
ENBE006E
The ENESCLIN DD statement does not have the correct attributes
Reason:
The data set associated with the ENESCLIN DD statement does not have the correct
attributes. The data set must be either a sequential data set, a partitioned data set with
an explicit member, or an instream data set. In addition, the data set LRECL must be 80
if the record format is fixed, or at least 84 if the record format is variable.
Action:
Verify that the data set that the ENESCLIN DD statement refers to has the appropriate
attributes. If not, use a data set that has the correct data set attributes and resubmit the
JCL.
ENBE Messages
ENBE007E
The program received the following invalid execution parameter:
Reason:
The execution JCL contained an unidentified parameter on the PARM statement. The
program issues message ENBE008E and terminates with a return code of 12.
Action:
Correct the invalid execution parameter in the JCL and resubmit the JCL.
ENBE008E
parameter
Reason:
This message is issued immediately after message ENBE007E. It identifies the invalid
parameter that was passed to the program.
Action:
Correct the invalid execution parameter in the JCL, and resubmit the JCL.
ENBE009E
Program initialization failed. Processing will terminate
Reason:
The Batch Environment Administration Facility initialization routine encountered one or
more errors. One or more error messages should precede message ENBE009E. The
Batch Environment Administration Facility terminates with a return code of 12.
Action:
See the previous message to determine why the initialization failed and take the
corrective action that the error message indicates.
ENBE Messages
ENBE010E
The Quorum Size for Approver Group approver group (value) is larger than the
number of Approver IDs defined (value)
Reason:
The Quorum Size associated with the Approver Group is larger than the number of
Approver User IDs associated with the Approver Group. This can occur under two
circumstances. First, a DEFINE APPROVER GROUP action is adding User IDs to the
Approver Group and the QUORUM SIZE value is greater than the number of Approver
User IDs specified on the APPROVER clause. Second, the DELETE APPROVER action is
removing one or more Approver User IDs from the Approver Group, and the number of
Approver User IDs that would remain is less than the existing QUORUM SIZE value.
Action:
Either reduce the QUORUM SIZE value, add more Approver User IDs to the DEFINE
APPROVER GROUP action APPROVER clause, or remove one or more Approver User IDs
from the DELETE APPROVER GROUP action APPROVER clause.
ENBE018E
The COMPARE from | to Column value (value) is greater than the Type Source Element
Length (value)
Reason:
The COMPARE FROM or TO COLUMN value is greater than the SOURCE ELEMENT
LENGTH. The source element length can be obtained from either the existing Type
definition or from the SOURCE ELEMENT LENGTH clause.
Action:
Change the COMPARE FROM or the COMPARE TO value so that it is equal to or less than
the SOURCE ELEMENT LENGTH that is associated with the Type definition.
ENBE Messages
ENBE022E
Symbolic name name is not defined in move|generate|delete processor name
Reason:
The symbol name identified is not defined in the processor identified in the message.
The DEFINE PROCESSOR SYMBOL action can only modify symbols that are defined in the
processor.
Action:
Remove the symbol name identified from the SYMBOL clause of the DEFINE PROCESSOR
SYMBOL action. Also, verify that the correct PROCESSOR GROUP and PROCESSOR TYPE
was specified on the DEFINE PROCESSOR SYMBOL action request. Resubmit the request.
ENBE023C
move|generate|delete processor name was not found in the processor load libraries
for system name
Reason:
The MOVE, GENERATE, or DELETE processor that was specified on the DEFINE
PROCESSOR GROUP action was not found in the Stage 1 or Stage 2 processor load
library for the system identified in the message.
Action:
Verify that the DEFINE PROCESSOR GROUP action specifies the correct processor name.
ENBE023E
move|generate|delete processor name was not found in the processor load libraries
for system name
Reason:
The MOVE, GENERATE, or DELETE processor that was specified on the DEFINE
PROCESSOR SYMBOL action was not found in the Stage 1 or Stage 2 processor load
library for the system identified in the message.
Action:
Verify that the DEFINE PROCESSOR SYMBOL action specifies the correct processor name
or type (or both).
ENBE Messages
ENBE024E
Processor Load Library data set name could not be allocated. S99INFO=value,
S99ERROR=value
Reason:
The specified processor load library could not be allocated. The Dynamic Allocation (SVC
99) service error code and information codes are shown.
Action:
Refer to the appropriate IBM documentation for your operating system for an
explanation of the S99INFO and S99ERROR codes. Take any corrective action possible
and resubmit the request. If the problem persists, contact your administrator.
ENBE027W
The STAGE ONE LOAD|LIST LIBRARY and the STAGE TWO load|list LIBRARY refer to
the same data set
Reason:
The STAGE ONE LOAD or LIST LIBRARY and the corresponding STAGE TWO LOAD or LIST
LIBRARY refer to the same data set. The DEFINE SYSTEM action continues processing.
Action:
None. If the STAGE ONE LOAD or LIST LIBRARY should be different than the
corresponding STAGE TWO LIBRARY, use the DEFINE SYSTEM action to make the
appropriate change.
ENBE028E
The STAGE ONE|TWO LOAD|LIST LIBRARY, data set name, is not catalogued
Reason:
The Processor LOAD or LIST library specified in the message was not found in the system
catalog.
Action:
Verify that the correct data set was specified on the DEFINE SYSTEM action. If necessary,
allocate the data set specified on the request. Resubmit the request.
ENBE Messages
ENBE029E
The STAGE ONE|TWO LOAD|LIST LIBRARY, data set name, has the incorrect data set
attributes
Reason:
The Processor LOAD or LIST library that was specified on the DEFINE SYSTEM action has
incorrect data set attributes. For information on the correct attributes for the processor,
see the Administration Guide. LOAD and LIST libraries.
Action:
Verify that the correct data set was specified on the DEFINE SYSTEM action. Verify the
data set attributes of the data set specified and, if necessary, reallocate the data set
with the correct attributes. Resubmit the request.
ENBE030E
The base|delta|source output|include LIBRARY, data set name, has an invalid &C1
symbolic
Reason:
The BASE, DELTA, SOURCE OUTPUT, or INCLUDE LIBRARY name contains an invalid &C1.
symbol.
Action:
Make sure that the &C1. symbol is spelled correctly. For a list of valid &C1. symbols, see
the Administration Guide.
ENBE031E
The base|delta|source output|include LIBRARY, data set name, is not catalogued
Reason:
The BASE, DELTA, SOURCE OUTPUT, or INCLUDE LIBRARY identified was not found in the
system catalog.
Action:
Verify that the data set name specified is correct. If the data set name is correct,
allocate the data set. Resubmit the request.
ENBE Messages
ENBE032C
The COMPARE COLUMN range (from column/to column ) for language language falls
outside the standard range
Reason:
The COMPARE FROM and TO column values fall outside the standard column range for
the language identified. The DEFINE TYPE continues processing the request.
Action:
If the COMPARE column range identified in the message is correct, no changes are
necessary. For a list of the standard COMPARE column ranges for each standard
language, see the SCL Reference Guide.
ENBE033E
The CONSOLIDATE element|component AT LEVEL value (value) must be less than the
NUMBER OF element|component LEVELS TO CONSOLIDATE value (value)
Reason:
The NUMBER OF ELEMENT LEVELS or the NUMBER OF COMPONENT LEVELS value is
greater than the CONSOLIDATE ELEMENT AT LEVEL or the CONSOLIDATE COMPONENT
AT LEVEL value.
Action:
Specify a NUMBER OF ELEMENT LEVELS or NUMBER OF COMPONENT LEVELS value that
is less than or equal to the CONSOLIDATE ELEMENT AT LEVEL or the CONSOLIDATE
COMPONENT AT LEVEL value.
ENBE035E
The DEFINE object action requires the clause clause
Reason:
The DEFINE action requires the clause that is identified by the clause field.
Action:
Add the required clause to the DEFINE statement. Resubmit the request.
ENBE Messages
ENBE036E
The DEFINE SYSTEM action requires the STAGE one|two LOAD LIBRARY clause
Reason:
The DEFINE SYSTEM action requires a valid STAGE ONE LOAD LIBRARY or STAGE TWO
LOAD LIBRARY clause.
Action:
Specify a valid STAGE ONE LOAD LIBRARY or STAGE TWO LOAD LIBRARY clause on the
DEFINE SYSTEM request. Resubmit the request.
ENBE037E
The USS HOST PATH PREFIX | USS HOST DISPOSITION | USS REMOTE PATH PREFIX |
USS REMOTE DISPOSITION clause is invalid for the Xmit method
Reason:
This clause can only be used with LOCAL, NDM and XCOM transmission methods.
Action:
Correct the syntax and resubmit the job.
ENBE038W
The USS HOST PATH NAME PREFIX is removed from the destination.
C1G0000W
Old Prefix: old prefix path name
Reason:
An update to the destination record changed the transmission method from one that
supports USS file transmissions to one that does not support USS file transmissions. The
update removed the USS HOST PATH NAME PREFIX value from the destination record.
The original prefix name is displayed in the message.
Action:
None.
ENBE Messages
ENBE039W
The USS REMOTE PATH NAME PREFIX is removed from the destination
C1G0000W
Old Prefix: old prefix path name
Reason:
An update to the destination record changed the transmission method from one that
supports USS file transmissions to one that does not support USS file transmissions. The
update removed the USS REMOTE PATH NAME PREFIX value from the destination
record. The original prefix name is displayed in the message.
Action:
None.
ENBE040E
The ddname DD statement has not been allocated
Reason:
The DD statement specified on the BUILD SCL TO DDNAME clause was not allocated in
the execution JCL.
Action:
Add the DDname specified on the TO DDNAME clause to the execution JCL and resubmit
the request.
ENBE041E
Data set data set name could not be found in the system catalog
Reason:
The data set specified on the BUILD SCL FOR action TO DSNAME clause could not be
located in the system catalog.
Action:
Verify that the data set specified on the BUILD SCL FOR action TO DSNAME clause exists.
Either correct the TO DSNAME clause or allocate a new data set. Resubmit the request.
ENBE Messages
ENBE042E
Member member already exists in data set data set name
Reason:
The member name specified on the BUILD SCL FOR action TO DSNAME MEMBER clause
already exists in the data set specified and the REPLACE clause was not specified.
Action:
Either specify the name of a member that does not exist on the MEMBER clause or
specify the REPLACE clause to replace the existing member. Resubmit the request.
ENBE044E
The BUILD TO location (ddname/data set name) does not have the correct attributes
Reason:
The data set associated with the BUILD SCL FOR action TO clause does not have the
correct attributes for the action. The data set must be either a sequential data set or a
partitioned data set with explicit member. In addition, the data set LRECL must be 80 if
the record format is fixed, or at least 84 if the record format is variable.
Action:
Either refer to a data set that has the correct attributes for the BUILD SCL FOR action or
reallocate the data set identified with the correct attributes.
ENBE045E
The USS HOST PATH PREFIX | USS REMOTE PATH PREFIX value is too long max length
cannot exceed 732 characters
Reason:
The path name prefix value cannot exceed 732 characters
Action:
ENBE Messages
ENBE046E
The USS HOST PATH PREFIX | USS REMOTE PATH PREFIX | USS HOST PATH NAME |
USS REMOTE PATH NAME value exceeds the maximum length while inserting the
missing /
Reason:
The path prefix or path name specification did not have a trailing / character and
contains the maximum number of characters.
Action:
ENBE047E
USS REMOTE PATH NAME value must begin with a /
Reason:
The path prefix or path name specification must have a beginning / in its name.
Action:
ENBE048E
The USS HOST PATH NAME | USS REMOTE PATH NAME value is too long max length
cannot exceed 768 characters
Reason:
The name cannot exceed 768 characters.
Action:
ENBE Messages
ENBE049E
DISP=MOD is not allowed for an existing PDS(E) member DSNAME(MEMBER)
Reason:
An attempt was made to extend an exising member in a PDS or PDSE using DISP=MOD.
DISP=MOD cannot be used to append data to PDS(E) members.
Action:
Change the DISP parameter to DISP=OLD if you want to rewrite a specified PDS member
or change the membername to create a new member.
ENBE050I
Environment-object-name has been deleted
Reason:
The DELETE action has successfully deleted the Environment Object definition.
Action:
None.
ENBE051E
System name cannot be deleted. Type name exists at Stage Number 1|2
Reason:
The system specified on the DELETE SYSTEM action cannot be deleted because at least
one Type is associated with the system.
Action:
Delete all of the Types associated with the System and resubmit the request.
ENBE052E
System name cannot be deleted. Subsystem name exists at Stage Number 1|2
Reason:
The System specified on the DELETE SYSTEM action cannot be deleted because at least
one Subsystem is associated with the system.
Action:
Delete all the Subsystems associated with the System and resubmit the request.
ENBE Messages
ENBE053E
Type name cannot be deleted. Element name exists at environment name/stage
number/system name/subsystem name
Reason:
The Type specified cannot be deleted because an element is associated with the Type.
The message identifies the name and inventory location of the element associated with
the Type.
Action:
Delete all of the elements associated with the Type and resubmit the request.
ENBE054E
Subsystem name cannot be deleted. Element name exists at environment name/stage
number/system name/type name
Reason:
The Subsystem specified cannot be deleted because an element is associated with the
Subsystem. The message identifies the name and inventory location of the element
associated with the Subsystem.
Action:
Delete all of the elements associated with the Subsystem and resubmit the request.
ENBE055E
Processor Group name cannot be deleted. Element name exists at environment
name/stage number/system name/subsystem name/type name
Reason:
The Processor Group specified cannot be deleted because an element is associated with
the Processor Group. The message identifies the name and inventory location of the
element associated with the Processor Group.
Action:
Delete all of the elements associated with the Processor Group and resubmit the
request.
ENBE Messages
ENBE070I
Processing is complete. Highest return code is return code
Reason:
The Batch Environment Administration Facility has completed execution. The program
terminates with the return code specified.
Action:
None.
ENBE072E
Unable to load external programname
Reason:
The Batch Environment Administration Facility initialization routine was unable to
dynamically load the named program. The initialization routine fails and the program
terminates.
Action:
Verify that the execution JCL contains the appropriate data sets in the CONLIB DD
statement. Check the JES system log for the job and for any system messages that may
indicate a system error. If any system errors are present, take corrective action for those
errors. If the problem persists, contact your administrator.
ENBE073E
MCF integrity error: System name is defined for Environment name Stage number but
not Stage number
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action detected that the SYSTEM specified on the
DEFINE, DELETE, or BUILD SYSTEM action was defined at only one of the two stages in
the Environment.
ENBE074E
MCF integrity error: Subsystem name is defined for Environment name, System name
Stage number but not Stage number
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action detected that the SUBSYSTEM specified
on the DEFINE, DELETE, or BUILD SYSTEM action was defined at only one of the two
stages in the Environment.
ENBE Messages
ENBE075E
Environment name is not defined
Reason:
The ENVIRONMENT specified on the DEFINE, DELETE, or BUILD SCL FOR action is not
defined. This occurs if the Environment is not defined in the C1DEFLTS table or if you are
not authorized to access an Environment that is defined in the C1DEFLTS table.
Action:
Verify that the Environment is valid. If the Environment is defined, contact your
administrator to determine if you should be authorized to access the Environment.
ENBE076E
No valid action statements were found. Action processing will not occur
Reason:
The ENESCLIN data set did not contain any valid action SCL statements. Either the data
set was empty, or the data set contained syntactically invalid statements.
Action:
Verify that the ENESCLIN DD statement refers to a data set that contains Batch
Environment Administration control statements (SCL). Correct the execution JCL as
needed and resubmit the request.
ENBE077E
System name is not defined to Environment name
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a SYSTEM that is not defined to
the ENVIRONMENT identified.
Action:
Verify that the correct Environment and System were specified on the request, and
ENBE Messages
ENBE078E
Subsystem name is not defined to Environment name, System name
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a SUBSYSTEM that is not defined
to the ENVIRONMENT and SYSTEM identified.
Action:
Verify that the correct Environment, System, and Subsystem were specified on the
request, and resubmit the request.
ENBE079E
Type name is not defined to Environment name, System name, Stage number
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a TYPE that is not defined to the
ENVIRONMENT, SYSTEM, and STAGE identified.
Action:
Verify that the correct Environment, System, Stage, and Type were specified on the
ENBE080E
Approver Group name is not defined to Environment name
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified an APPROVER GROUP that is not
defined to the ENVIRONMENT.
Action:
Verify that the correct Environment and Approver Group were specified on the request,
and resubmit the request.
ENBE Messages
ENBE081W
Processor Group name is not defined to Environment name, System name, Type
name, Stage number
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a PROCESSOR GROUP that is not
defined to the Environment, System, Type, and Stage identified.
Action:
Verify that the correct Environment, System, Stage, Type, and Processor Group were
specified on the request, and resubmit the request.
ENBE082E
USS REMOTE PATH NAME value cannot contain both a single and double quote
character
Reason:
The path prefix or path name can contain a single quote character or a double quote
character, but not both.
Action:
ENBE083E
Reason:
A $IMR error occurred in routine name. The $IMR message text follows:
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action received an error condition from the $IMR
service. The message that follows ENBE083E identifies the error that occurred.
Action:
ENBE Messages
ENBE084E
With rel 4.0 the next type name cannot differ from the current type.
Reason:
Beginning with CA Endevor SCM release 4.0, the NEXT TYPE name cannot differ from the
current TYPE, because type name changes across the map are not allowed.
Action:
Verify that the correct type name is specified on the request and resubmit the request.
ENBE085E
STAGE ID id is not defined to Environment name
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a STAGE ID that is not defined to
the Environment.
Action:
Change the STAGE ID clause to a valid Stage ID. Resubmit the request.
ENBE086E
No matches were found for System name Environment name
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a wildcarded SYSTEM name and
there were no matches for the wildcarded SYSTEM name.
Action:
Verify that the correct Environment and System were specified. Resubmit the request.
ENBE087E
No matches were found for Subsystem name in Environment name, System name
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a wildcarded Subsystem name
and there were no matches for the wildcarded Subsystem name.
Action:
Verify that the correct Environment, System, and Subsystem were specified on the
ENBE Messages
ENBE088E
No matches were found for Type name in Environment name, System name, Stage
number
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a wildcarded TYPE name and
there were no matches for the wildcarded TYPE name.
Action:
Verify that the correct Environment, System, Type, and Stage were specified on the
ENBE089W
No inventory structures were found in Environment name
Reason:
The Environment specified on the BUILD SCL FOR ENVIRONMENT action did not contain
any Systems, Subsystems, Type, and Processor Groups. Subsystems, Type, and Processor
Groups.
Action:
None.
ENBE090S
Function function name was unable to obtain Xvalue bytes of storage
Reason:
The specified function was unable to obtain the specified amount of storage. The
number of bytes is specified in hexadecimal.
Action:
Increase the region size on the REGION= JCL statement and resubmit the request. If the
problem persists and the DEFINE or DELETE action contains a wildcarded object name,
modify the request to specify multiple explicit requests. If the BUILD SCL FOR action
specifies the INCLUDE SUBORDINATES clause, remove the clause. If the ENESCLIN data
set contains more than one request, submit each request as an individual job. If the
problem persists, contact your administrator.
ENBE Messages
ENBE091S
Internal error in function name. error text.
Reason:
An internal error occurred in the above function. The error text identifies the error that
occurred.
Action:
ENBE092S
Internal error in function name. Unable to build a TDF for field code X value
Reason:
An internal error occurred in the above function. The DEFINE, DELETE, or BUILD SCL FOR
action cannot continue to process.
Action:
ENBE094S
Internal error in function name. $IMR did not return data for field code Xvalue
Reason:
Action:
ENBE095S
Internal error in function name. Unable to allocate a TFC. Return Code=Xvalue
Reason:
Action:
ENBE Messages
ENBE096S
Invalid value return by parser, function = function name,
Reason:
An internal function determined that the parser passed an invalid token. Message
ENBE097S further identifies the error.
Action:
ENBE097S
Field = field name, value = value
Reason:
This message is issued with message ENBE096S to identify the parser token that was
invalid.
Action:
ENBE098S
Invalid string return by parser, function = function name,
Reason:
An internal function determined that the parser returned an invalid token. The field that
contains the invalid string appears in message ENBE099S.
Action:
ENBE099S
Field = field name, string = string
Reason:
This message is issued with message ENBE098S to identify the parser token that was
invalid.
Action:
ENBE Messages
ENBE100S
Unexpected return code from function function name. Return code = return code,
Reason:
An unexpected return code was received from the internal function identified. See
message ENBE101S. This message lists the field name and string that was passed to the
above function.
Action:
ENBE101S
Reason:
This message is issued with message ENBE100S to identify the invalid return code.
Action:
ENBE102S
Function function name was passed an invalid parameter value
Reason:
An invalid parameter value was passed to the internal function identified. See message
ENBE103S. This message lists the parameter name of the field and value that was
passed to the above function.
Action:
ENBE103S
Field = field name, value = value
Reason:
See message ENBE102S. This message lists the parameter name of the field and value
that was passed to the above function listed in message ENBE102S.
Action:
ENBE Messages
ENBE104S
Unable to create a new Tagged Field Object
Reason:
An error occurred when trying to create a new Tagged Field Object. The DEFINE,
DELETE, or BUILD SCL FOR action cannot continue processing.
Action:
ENBE105S
Invalid keyword value, function = function name
Reason:
An invalid keyword value was used in function "FUNCTION NAME." See message
ENBE106S. This message lists the keyword and the value of the keyword.
Action:
ENBE106S
Keyword = keyword, value = value
Reason:
See message ENBE105S. This message lists the keyword and the value of the keyword
used in the above function listed in message ENBE105S.
Action:
ENBE107S
Unexpected return code from function function name, return code = return code
Reason:
An unexpected return code was received from function "FUNCTION NAME." See
message ENBE108S. This message lists the field name and data set name that was
passed to the above function.
Action:
ENBE Messages
ENBE108S
Field = field name, data set name =data set name
Reason:
See message ENBE107S. This message lists the field name and data set name that was
passed to the function listed in message ENBE107S.
Action:
ENBE110I
The define|delete|build object action has completed. Return Code is return code
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action for the object identified has completed
with the return code indicated. If the return code is not zero, one or more messages
should be written to indicate the reason for the non-zero return code.
Action:
None.
ENBE111I
System name in Environment name has been created|updated
Reason:
The DEFINE SYSTEM action created or modified the System definition identified.
Action:
None.
ENBE112I
Subsystem name in Environment name, System name has been created|updated
Reason:
The DEFINE SUBSYSTEM action created or modified the Subsystem definition identified.
Action:
None.
ENBE Messages
ENBE113I
Type name in Environment name, System name, Stage number has been
created|updated
Reason:
The DEFINE TYPE action created or modified the Type definition identified.
Action:
None.
ENBE114I
The Type Sequence record for Environment name, System name, Stage number has
been created|updated
Reason:
The Type Sequence record listed associated with the Environment, System, and Stage
identified was created or updated.
Action:
None.
ENBE115I
DEFINE SCL created for System name in Environment name
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the System identified.
Action:
None.
ENBE116I
DEFINE SCL created for Subsystem name in Environment name, System name
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the Subsystem identified.
Action:
None.
ENBE Messages
ENBE117I
DEFINE SCL created for Type name in Environment name, System name, Stage number
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the Type identified.
Action:
None.
ENBE118I
DEFINE SCL created for Processor Group name in Environment name, System name,
Type name, Stage number
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the Processor Group identified.
Action:
None.
ENBE119E
No matches were found for Processor Group name in Environment name, System
name, Type name, Stage Number number
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a wildcarded PROCESSOR
GROUP name and there were no matches for the wildcarded PROCESSOR GROUP name
in the above inventory location.
Action:
Verify that the inventory locations specified on the ENVIRONMENT, SYSTEM, TYPE,
STAGE, and PROCESSOR GROUP clauses are valid, and resubmit the request.
ENBE120I
DEFINE SCL created for Approver Group name in Environment name
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the Approver Group identified.
Action:
None.
ENBE Messages
ENBE121W
There are no TYPEs associated with System name at Stage number
Reason:
The BUILD SCL FOR action determined that there were no Types associated with the
System and Stage identified.
Action:
None.
ENBE122I
DEFINE SCL created for the TYPE SEQUENCE record for System name in Environment
name, Stage number
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the Type Sequence definition at
the Environment, System, and Stage identified.
Action:
None.
ENBE123E
More than 16 Approvers have been defined to Approver Group name
Reason:
The DEFINE APPROVER GROUP action is modifying an existing Approver Group. The
number of Approver User IDs that will be added to the Approver Group will cause more
than 16 Approver User IDs to be associated with the Approver Group. An Approver
Group can only contain 16 Approver User IDs.
Action:
Decrease the number of Approver User IDs specified on the DEFINE APPROVER GROUP
action APPROVER clause, and resubmit the request.
ENBE Messages
ENBE124E
No matches were found for Approver Group name in Environment name
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a wildcarded APPROVER GROUP
name and there were no matches for the wildcarded APPROVER GROUP name in the
Environment.
Action:
Verify that the ENVIRONMENT name and the APPROVER GROUP name specified on the
action are valid.
ENBE125S
Function function name was passed an invalid parameter,
Reason:
An internal function received an invalid parameter value. Message ENBE126S identifies
the invalid parameter that the routine received.
Action:
ENBE126S
Reason:
See message ENBE125S. This message lists the parameter name of the field and string
that was passed to the above function listed in message ENBE125S.
Action:
ENBE Messages
ENBE127W
Approver ID userid is not defined to Approver Group name
Reason:
The Approver User ID specified on the DELETE APPROVER GROUP action APPROVER
clause was not defined to the Approver Group. The DELETE APPROVER GROUP action
continues to process.
Action:
Verify that the Approver User IDs specified on the APPROVER clause are correct. Also
verify that the correct Approver Group and Environment were specified on the request,
ENBE128I
Approver ID userid has been removed from Approver Group name
Reason:
The APPROVER ID user ID was successfully deleted from the APPROVER GROUP
identified.
Action:
None.
ENBE129I
Approver Group name in Environment name has been created|updated
Reason:
The DEFINE APPROVER GROUP action has either created or modified the Approver
Group identified.
Action:
None.
ENBE Messages
ENBE130E
Approver Relation for group name in environment name/stage number/system
name/subsystem name/type name is not defined
Reason:
The Approver Group specified on the DEFINE, DELETE, or BUILD SCL FOR action is not
defined.
Action:
Verify that Approver Group, Environment, System, Stage, Subsystem, and Types
specified are correct, and resubmit the request.
ENBE131E
name/subsystem name/type name is already defined
Reason:
An attempt was made to DEFINE an APPROVER RELATION that already existed.
Action:
Verify that Approver Group, Environment, System, Stage, and Subsystem specified are
correct, and resubmit the request.
ENBE132I
Processor Group name in Environment name, System name, Type name, Stage
number has been created3updated
Reason:
The DEFINE PROCESSOR GROUP action has created or updated the Processor Group
identified.
Action:
None.
ENBE Messages
ENBE133I
name/subsystem name/type name has been created|updated
Reason:
The DEFINE APPROVER RELATION action has created or modified the Approver
Relationship between the Approver group and the inventory location identified.
Action:
None.
ENBE134E
No matches were found for Shipment Destination name
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified a wildcarded SHIPMENT
DESTINATION name and there were no matches for the wildcarded SHIPMENT
DESTINATION name.
Action:
Verify that the correct Shipment Destination name was specified, and resubmit the
request.
ENBE135E
The DEFINE PROCESSOR SYMBOL action requires at least one SYMBOL clause
Reason:
The DEFINE PROCESSOR SYMBOL action requires at least one SYMBOL clause. The
SYMBOL clause identifies the SYMBOL name that will be updated by the action.
Action:
Add at least one SYMBOL clause to the DEFINE PROCESSOR SYMBOL action, and
ENBE Messages
ENBE136I
DEFINE SCL created for Processor Symbols for Group name in environment
name/stage number/system name/type name
Reason:
The BUILD SCL FOR action has created DEFINE SCL for the Processor Symbols associated
with the Processor Group identified.
Action:
None.
ENBE137E
The DEFINE PROCESSOR SYMBOL action is not valid when the generate|move|delete
processor is *NOPROC*
Reason:
The DEFINE PROCESSOR SYMBOL action is only valid if the GENERATE, DELETE, or MOVE
Processor Name is not *NOPROC*.
Action:
Verify that the correct Environment, System, Type, Stage, Processor Group, and
Processor Type were specified, and resubmit the request.
ENBE138E
A $PKMR error occurred in routine name. The $PKMR Message text follows:
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action received an error condition from the
$PKMR service. The message that follows ENBE138E should indicate the error that
occurred.
Action:
Review the message that follows ENBE138E. Contact your administrator.
ENBE Messages
ENBE139W
Shipment Destination name has an invalid Transmission Method code of value
Reason:
The BUILD SCL FOR SHIPMENT DESTINATION action was unable to determine the
transmission method associated with the Shipment Destination. The SCL for the
TRANSMISSION METHOD clause was assigned the value *UNKNOWN*.
Action:
Use the DEFINE SHIPMENT DESTINATION action to correct the TRANSMISSION METHOD
associated with the Shipment Destination. The SCL created by the BUILD SCL FOR
SHIPMENT DESTINATION action will contain an invalid transmission method.
ENBE140C
DEFINE SCL created for Shipment Destination dest-name
C1G0000C
Host path name invalid: path-name
C1G0000C
Remote path name invalid: path-name
Reason:
The SHIPMENT DESTINATION define SCL statement is still generated even though the
host and/or remote path names are invalid. Single and double quotes cannot be used
together in the path-name. If this syntax is used, this Define action will fail.
Action:
You will need to adjust the affected path name.
ENBE140I
DEFINE SCL created for Shipment Destination name
Reason:
The BUILD SCL FOR SHIPMENT DESTINATION action has created DEFINE SCL from the
Shipment Destination identified and any associated Mapping Rules.
Action:
None.
ENBE Messages
ENBE141E
Shipment Destination name is not defined
Reason:
The DELETE or BUILD SCL FOR action specified a SHIPMENT DESTINATION that is not
defined.
Action:
Verify that the Shipment Destination specified on the DELETE or BUILD SCL FOR
SHIPMENT DESTINATION action is correct, and resubmit the request.
ENBE142E
The following error occurred in routine name while building the Processor Symbol
chain for processor name
Reason:
An unrecoverable error occurred while processing the DEFINE PROCESSOR SYMBOL
action. A detailed message follows this message.
Action:
Examine the detailed message and take the appropriate action.
ENBE143E
Processor Symbol name is not defined to generate|move|delete processor name
Reason:
The Processor Symbol identified is not defined to the Processor identified.
Action:
Verify the symbol name specified on the DEFINE PROCESSOR SYMBOL action SYMBOL
clause is spelled correctly. Verify that the correct Environment, System, Type, Stage,
Processor Group, and Processor Type were specified, and resubmit the request.
ENBE Messages
ENBE144W
Processor Symbol name has not been overridden or is not defined for
generate|move|delete processor name
Reason:
The symbol name specified in the DELETE PROCESSOR SYMBOL action SYMBOL clause
did not have an override assigned or the symbol does not exist in the processor.
Action:
None.
ENBE146I
All of the symbol overrides have been deleted from generate|move|delete processor
name
Reason:
The user specified a DELETE PROCESSOR SYMBOL action and ALL the Processor Symbol
override values were deleted.
Action:
None.
ENBE147I
count symbol overrides have been deleted from generate|move|delete processor
name
Reason:
The DELETE PROCESSOR SYMBOL action has deleted the number of symbols indicated
from the Generate, Move, or Delete Processor identified.
Action:
None.
ENBE Messages
ENBE148S
A $BSTGLST error occurred in routine name. The $BSTGLST RESULT code is return
code
Reason:
An internal CA Endevor SCM service returned an error condition. The DEFINE, DELETE, or
BUILD SCL FOR action cannot continue processing.
Action:
ENBE149S
Routine MergeProcSymbols detected an mismatch between the number of Symbol
Names and Symbol Values
Reason:
An internal routine encountered an unrecoverable error. The DEFINE, DELETE, or BUILD
SCL FOR action cannot continue processing.
Action:
ENBE150I
Processor Symbol name will be created|updated
Reason:
The above Processor Symbol will be created or updated unless a processing error
occurs.
Action:
None.
ENBE Messages
ENBE151I
Shipment Destination name has been created|updated
Reason:
The DEFINE SHIPMENT DESTINATION action has created or updated the Shipment
Destination identified.
Action:
None.
ENBE152I
Processor Symbols for generate|move|delete processor name in environment
name/stage number/system name/subsystem name/type name have been defined
Reason:
The DEFINE PROCESSOR SYMBOL has added the processor symbol overrides for the
GENERATE, MOVE, or DELETE Processor associated with the Processor that is identified.
Action:
None.
ENBE153I
Processor Group name has been deleted from environment name/stage
number/system name/subsystem name/type name
Reason:
The DELETE PROCESSOR GROUP action has deleted the Processor Group identified.
Action:
None.
ENBE Messages
ENBE154I
There are no Processor Symbols associated with generate|move|delete processor
name
Reason:
The GENERATE, MOVE, or DELETE Processor associated with the Processor Group
specified on the BUILD SCL FOR PROCESSOR SYMBOLS action did not contain any
symbols. The BUILD SCL FOR action cannot, therefore, create any DEFINE SCL
statements.
Action:
None.
ENBE155E
The BUILD SCL TO data set validation failed. Refer to the previous error message
Reason:
The BUILD SCL FOR action TO location data set failed validation. The previous error
message indicates the reason for the failure.
Action:
See the previous error message and take the corrective action associated with the error.
If the data set has an invalid data set attribute, either respecify the correct TO location,
or reallocate the data set with the correct attributes, and resubmit the request.
ENBE156I
DEFINE SCL created for Group name related to environment name/stage
number/system name/subsystem name/type name
Reason:
The BUILD SCL FOR APPROVER RELATION action has created DEFINE SCL to relate the
Approver Group identified to the inventory location identified.
Action:
None.
ENBE Messages
ENBE157I
DEFINE SCL created for Ship Destination name data set data set name
Reason:
The BUILD SCL FOR SHIPMENT MAPPING RULE action has created a DEFINE SCL
statement for the data set Mapping Rule identified and associated with the Shipment
Destination identified.
Action:
None.
ENBE158I
Shipment Destination name Map Rule for data set data set name has been
created|updated
Reason:
The DEFINE SHIPMENT MAPPING RULE action has created or modified the Mapping Rule
for the data set specified.
Action:
None.
ENBE159I
Shipment Destination name has been created|updated|deleted
Reason:
The Shipment Destination identified was created, updated, or deleted.
Action:
None.
ENBE Messages
ENBE160E
Shipment Mapping Rule data set name is not defined for destination name
Reason:
The DELETE or BUILD SCL FOR action specified a SHIPMENT MAPPING RULE that was not
defined for the Shipment Destination specified.
Action:
Verify that both the SHIPMENT DESTINATION and the HOST DATA SET clauses are
correct, and resubmit the request.
ENBE161I
Ship Destination dest-name USS Map Rule has been deleted for
C1G0000I
path name: p-name
Reason:
Informational message to confirm that the USS mapping rule has been deleted for the
specified destination and path name.
Action:
None.
ENBE162E
Shipment Destination name is being used by another user
Reason:
The Shipment Destination specified is in use by another user. Only one user can process
a Shipment Destination at a time.
Action:
Resubmit the request at a later time.
ENBE Messages
ENBE163E
The ELEMENT DELTA FORMAT IS FORWARD clause cannot be specified when DO NOT
COMPRESS BASE has been specified
Reason:
The ELEMENT DELTA FORMAT IS FORWARD and the DO NOT COMPRESS BASE clauses
are mutually exclusive. If the ELEMENT DELTA FORMAT IS FORWARD clause is specified,
the DO NOT COMPRESS BASE cannot be specified; or, if the DO NOT COMPRESS BASE
clause was specified, the ELEMENT DELTA FORMAT IS FORWARD clause cannot be
specified.
Action:
Change the DO NOT COMPRESS BASE clause to COMPRESS BASE; or, change the
ELEMENT DELTA FORMAT IS FORWARD to ELEMENT DELTA FORMAT IS REVERSE.
ENBE164E
DO NOT COMPRESS BASE cannot be specified when the Type ELEMENT DELTA
FORMAT is FORWARD
Reason:
When ELEMENT DELTA FORMAT IS FORWARD is specified, the base files have to be
compressed, and the DO NOT COMPRESS BASE clause cannot be specified.
Action:
Change the DO NOT COMPRESS BASE clause to COMPRESS BASE or change the
ELEMENT DELTA FORMAT IS FORWARD to ELEMENT DELTA FORMAT IS REVERSE.
ENBE165E
CONSOLIDATE element|component LEVELS is not valid when the NUMBER OF
ELEMENT|COMPONENT LEVELS TO CONSOLIDATE is zero
Reason:
The NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or the NUMBER OF COMPONENT
LEVELS TO CONSOLIDATE value must not be zero when the corresponding CONSOLIDATE
element LEVELS or CONSOLIDATE component LEVELS clause is specified.
Action:
Specify a value of greater than zero for the NUMBER OF ELEMENT LEVELS TO
CONSOLIDATE or the NUMBER OF COMPONENT LEVELS TO CONSOLIDATE clause.
ENBE Messages
ENBE166E
DO NOT CONSOLIDATE element|component LEVELS is not valid when the NUMBER OF
element|component LEVELS TO CONSOLIDATE is non-zero
Reason:
LEVELS TO CONSOLIDATE must be zero when the corresponding CONSOLIDATE element
LEVELS or CONSOLIDATE component LEVELS clause is specified.
Action:
Specify a value of zero for the NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or the
NUMBER OF COMPONENT LEVELS TO CONSOLIDATE clause. Resubmit the request.
ENBE167E
NUMBER OF element|component LEVELS TO CONSOLIDATE cannot be zero when
CONSOLIDATE element|component LEVELS is active
Reason:
LEVELS TO CONSOLIDATE must not be zero when the corresponding CONSOLIDATE
Action:
Specify a NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or the NUMBER OF
COMPONENT LEVELS TO CONSOLIDATE value that is greater than or equal to zero.
ENBE168E
NUMBER OF element|component LEVELS TO CONSOLIDATE must be zero when DO
NOT CONSOLIDATE element|component levels is active
Reason:
LEVELS TO CONSOLIDATE value must be zero when the corresponding CONSOLIDATE
Action:
Specify a NUMBER OF ELEMENT LEVELS TO CONSOLIDATE or the NUMBER OF
COMPONENT LEVELS TO CONSOLIDATE value of zero. Resubmit the request.
ENBE Messages
ENBE169E
The record length for data set data set name (value) is less than the Source Element
Length (value)
Reason:
The data set logical record length (LRECL) for the SOURCE OUTPUT DATA SET associated
with the DEFINE TYPE action is smaller than the SOURCE ELEMENT LENGTH value
associated with the Type. The SOURCE OUTPUT DATA SET logical record length must be
greater than or equal to the SOURCE ELEMENT LENGTH value.
Action:
Verify that the correct SOURCE ELEMENT LENGTH value was specified. Verify that the
correct SOURCE OUTPUT DATA SET was specified. Correct either the SOURCE ELEMENT
LENGTH value or the SOURCE OUTPUT DATA SET value. If necessary, reallocate the
SOURCE OUTPUT data set so that it has a record length that is at least as large as the
SOURCE ELEMENT LENGTH value.
ENBE170E
base|delta|include|source output data set data set name has invalid attributes for a
Type data set
Reason:
The BASE, DELTA, INCLUDE, or SOURCE OUTPUT data set has invalid attributes for a
TYPE data set.
Action:
For information on the attributes of the Base, Delta, and Source Output libraries, see
the Administration Guide.
ENBE171E
An error occurred while validating base|delta|include|source output data set data set
Reason:
An internal CA Endevor SCM service was unable to validate the data set identified in the
message. A second error message should follow message ENBE171E to indicate the
error that occurred.
Action:
See the corrective action associated with the error message that should follow message
ENBE171E.
ENBE Messages
ENBE172E
An internal error occurred in routine name. The Type Sequence counters are not
synchronized
Reason:
An internal error occurred while processing the DEFINE, DELETE, or BUILD SCL FOR TYPE
SEQUENCE action.
Action:
ENBE173E
The NUMBER OF element|component LEVELS TO CONSOLIDATE value must be less
than or equal to the CONSOLIDATE AT LEVEL
Reason:
The NUMBER OF ELEMENT LEVELS or the NUMBER OF COMPONENT LEVELS is greater
than the corresponding CONSOLIDATE ELEMENT AT LEVEL or CONSOLIDATE
Action:
Specify a NUMBER OF ELEMENT LEVELS or NUMBER OF COMPONENT LEVELS clause
value that is less than or equal to the corresponding CONSOLIDATE ELEMENT AT LEVEL
or CONSOLIDATE COMPONENT AT LEVEL clause value.
ENBE174E
The CONSOLIDATE element|component AT LEVEL value must be greater than or equal
to the NUMBER OF LEVELS TO CONSOLIDATE
Reason:
The CONSOLIDATE ELEMENT AT LEVEL or the CONSOLIDATE COMPONENT AT LEVEL
VALUE was less than the corresponding NUMBER OF ELEMENT LEVELS TO CONSOLIDATE
or NUMBER OF COMPONENT LEVELS TO CONSOLIDATE value.
Action:
Specify a CONSOLIDATE ELEMENT AT LEVEL or a CONSOLIDATE COMPONENT AT LEVEL
clause value that is greater than or equal to the corresponding NUMBER OF ELEMENT
LEVELS or NUMBER OF COMPONENT LEVELS clause value.
ENBE Messages
ENBE175E
The SIGNOUT DATA SET VALIDATION IS ACTIVE clause is not valid when SIGNOUT is
not active
Reason:
The SIGNOUT DATA SET VALIDATION IS ACTIVE cannot be specified if the Signout option
is not active for the system.
Action:
Change the SIGNOUT IS NOT ACTIVE clause to SIGNOUT IS ACTIVE or change the
SIGNOUT DATA SET VALIDATION IS ACTIVE to SIGNOUT DATA SET VALIDATION IS NOT
ACTIVE.
ENBE176E
The SIGNOUT IS NOT ACTIVE clause is not valid when SIGNOUT DATA SET VALIDATION
is active
Reason:
The SIGNOUT DATA SET VALIDATION IS ACTIVE cannot be specified if data set signout
validation was already activated for the System.
Action:
ACTIVE.
ENBE177E
Processing will terminate because of an application ABEND
Reason:
An application ABEND occurred during execution of the Batch Environment
Administration Facility. Processing is unable to continue.
Action:
ENBE Messages
C1G0000IW
USS Map Rule: host path name
ENBE179W
is not defined for destination dest-name
Reason:
No USS mapping rule is defined for the specified host path name and destination.
Action:
Verify the syntax to make sure you specified the correct information.
ENBE186S
An unrecoverable I/O error occurred during the BUILD SCL request
Reason:
An error occurred when attempting to write SCL statements for a BUILD SCL FOR action.
Action:
See the JES Message log to determine if there were any system errors. If so, take the
corrective action associated with the error. Resubmit the request. If the problem
persists, contact your administrator.
ENBE187E
Environment name and System name are currently in use by another user
Reason:
The Batch Environment Administration Facility or the ISPF dialog is currently processing
an environment definition associated with the Environment and System specified. Only
one user at a time can access an environment definition in an Environment and System.
The current request is terminated.
Action:
ENBE Messages
ENBE188E
No relationships were found for Approver Group name in Environment name
Reason:
There are no approver group relationships defined for the approver group identified in
the environment.
Action:
Verify that the correct approver group was specified in the request. Resubmit the
request after any changes are made.
ENBE189I
Data set name is sequential. The MEMBER clause will be ignored
Reason:
The data set specified on the BUILD SCL FOR action TO DSNAME clause was sequential.
The action also contained the MEMBER clause. The MEMBER clause is inconsistent with
the data set organization, so the BUILD action ignores the clause.
Action:
None. However, to eliminate the message, remove the MEMBER clause from the action.
Alternatively, specify a partitioned data set for the TO DSNAME.
ENBE190E
An error occurred while validating STAGE ONE|TWO LOAD|LIST data set data set
name
Reason:
An error occurred while attempting to validate the attributes of the STAGE ONE or TWO
LOAD or LIST library. A second message may follow message ENBE190E to indicate the
reason for the failure.
Action:
If a second error message was issued, follow the corrective action described for the
message, and resubmit the request.
ENBE Messages
ENBE192E
Invalid regression percentage value, must be zero for Full Image and Log Deltas
Reason:
The element Type delta format is defined as either full Image or log. The regression
percentage value has no meaning or purpose for the types defined as full image and log.
Action:
The value must be set to zero. If omitted on a new definition, it defaults to zero.
ENBE193E
Element delta format cannot be changed. Element <element> exists at
<environment>/<stage>/<system>/<subsystem>/<type>
Reason:
You cannot change a type definition from Full Image to Reverse or Forward delta or
from Reverse or Forward to Full Image delta, if elements exist at the specified location
for this type.
Action:
None.
ENBE194E
Invalid file ext name
Reason:
Values must be a-z, A-Z, 0-9, or blanks. Embedded blanks are not allowed.
Action:
Define a file extension name that satisfies the naming standard.
ENBE Messages
ENBE195E
Source Element Length cannot be changed. Element <element> exists at
<environment>/<stage>/<system>/<subsystem>/<type>
Reason:
You cannot change the Source Element Length in a type definition, if elements exist at
the specified location for this type.
Action:
None.
ENBE200S
A abend code ABEND occurred in function function
Reason:
The Batch Environment Administration Facility abended with the code identified. The
current action will terminate processing immediately and any remaining, unexecuted
actions will not be executed.
Action:
Resubmit the request. If the problem persists, contact your administrator. You will need
to create a diagnostic dump of the ABEND before you contact your administrator,
however. Add the following card to the execution JCL and resubmit the request:
//SYSABEND DD SYSOUT=*
This JCL statement creates a diagnostic dump when the ABEND occurs.
ENBE202W
Site level type sequencing in effect, Type Sequence will be defined but will have no
effect
Reason:
A batch admin job was submitted with Define TYPE Sequence SCL. This SCL refers to
type sequencing under a particular environment, stage, and system. When global Type
Sequencing is turned on at the site level, these definitions are ignored. The Define SCL
action completes and creates or updates the local Type Sequence. However because the
Global Type Sequence is in effect, the local TYPE Sequence order will not be used for
action processing.
Action:
No action is required, but you may want to remove the Define TYPE Sequence SCL
statements in batch admin jobs submitted in the future to avoid getting this message.
ENBE Messages
ENBE203E
Invalid members per cylinder. Valid ranges are .01-.99, 1.0-9.9, and 10-999.
Reason:
Value specified in the APPROX MEMBERS PER CYL is not within range.
Action:
Specify the correct value.
ENBE204E
Type name in Environment name and System name is currently in use by another user
Reason:
The Batch Environment Administration Facility or the ISPF dialog is currently processing
a Type definition associated with the Environment and System specified. Only one user
at a time can access a Type definition in an Environment and System. The current
request is terminated.
Action:
ENBE205C
DEFINE SCL created for Ship Destination dest-name
path name: path-name
C1G0000C
Host path name invalid: path-name
C1G0000C
Remote path name invalid: path-name
Reason:
The SHIPMENT USS MAPPING RULE define SCL statement for the named destination is
still generated even though the host and/or remote path names are invalid. Single and
double quotes cannot be used together in the path-name. If this syntax is used, this
Define action will fail.
Action:
You will need to adjust the affected path name.
ENBE Messages
ENBE900I
Control statement parsing is beginning
Reason:
The program is beginning to parse the user-supplied control statements.
Action:
None.
ENBE901I
Control statement parsing has completed with no errors
Reason:
The program has completed parsing the control statements and no errors were
detected.
Action:
None.
ENBE902E
Control statement parsing has completed with errors
Reason:
The program has completed parsing the control statements. One or more errors were
detected in the control statements. None of the actions specified will be performed.
Action:
Refer to the Batch Environment Control Statement Summary Report to determine the
error that terminated the request. Take the corrective action that the error message
indicates, and resubmit the request.
ENBE903I
The control statements will not be executed at the users request
Reason:
The execution JCL contained the PARM=VALIDATE statement. The program only parses
the control statements. The control statements will not be executed.
Action:
None.
ENBE Messages
ENBE904E
The Environment name cannot be wildcarded
Reason:
The Environment name specified on the BUILD SCL FOR ENVIRONMENT action
contained a wildcard.
Action:
Change the BUILD SCL FOR ENVIRONMENT action to refer to a fully qualified
Environment, and resubmit the request.
ENBE905E
The from|to clause contains a wildcarded Environment name
Reason:
An environment name specified on the DEFINE, DELETE, or BUILD SCL FOR action
ENVIRONMENT clause contained a wildcard.
Action:
Specify a fully qualified Environment name on the DEFINE, DELETE, or BUILD SCL FOR
action ENVIRONMENT clause, and resubmit the request.
ENBE907E
The DEFINE TYPE action requires the SOURCE ELEMENT LENGTH clause
Reason:
The DEFINE TYPE action did not specify the required SOURCE ELEMENT LENGTH clause.
Action:
Add the SOURCE ELEMENT LENGTH clause to the DEFINE TYPE statement, and resubmit
the request.
ENBE Messages
ENBE908E
The DEFINE TYPE action requires the COMPARE FROM COLUMN clause
Reason:
The DEFINE SYSTEM action did not specify the required COMPARE FROM COLUMN
clause.
Action:
Add the COMPARE FROM COLUMN clause to your DEFINE TYPE statement, and resubmit
the request.
ENBE909E
The name clause value is outside the valid range
Reason:
The DEFINE action clause identified specified a value that is outside the valid range for
the clause. See the SCL Reference Guide to determine the valid value range for the
clause that was identified.
Action:
Specify a valid value in the clause. Resubmit the request.
ENBE910E
The DEFINE TYPE action requires the LANGUAGE clause
Reason:
The DEFINE TYPE action did not specify the required LANGUAGE clause.
Action:
Add the LANGUAGE clause to your DEFINE TYPE statement.
ENBE Messages
ENBE911E
The DEFINE TYPE action requires the BASE or DELTA LIBRARY clause
Reason:
The DEFINE TYPE action did not specify the required BASE LIBRARY or or DELTA LIBRARY
clause.
Action:
Add the BASE LIBRARY or DELTA LIBRARY clause to the DEFINE TYPE action and resubmit
the request.
ENBE913E
The NEXT object name cannot be wildcarded
Reason:
The DEFINE action contained a wildcard value for the NEXT SYSTEM, SUBSYSTEM, TYPE,
or PROCESSOR GROUP.
Action:
Specify a fully qualified NEXT clause. Resubmit the request.
ENBE914E
The DEFINE TYPE SEQUENCE action contained a duplicate sequence number of value
Reason:
The DEFINE TYPE SEQUENCE action SEQUENCE clause contained at least two (type
name, sequence number) pairs that specified the same sequence number. For example:
SEQUENCE=((TYPE1,15),(TYPE2,15)). The
sequence number values must be unique.
Action:
Change the duplicate sequence numbers so that the values are unique, and resubmit
the request.
ENBE Messages
ENBE915E
The DEFINE TYPE SEQUENCE action contained a duplicate Type of value
Reason:
The DEFINE TYPE SEQUENCE action SEQUENCE clause contained at least two (type
name, sequence number) pairs that specified the same element type. For example:
SEQUENCE=((TYPE1,15),(TYPE1,25)). The element
type values must be unique.
Action:
Change the duplicate element types so that the values are unique, and resubmit the
request.
ENBE918E
The COMPARE FROM value must be less than or equal to the COMPARE TO value
Reason:
The DEFINE TYPE action COMPARE FROM value is greater than the TO value.
Action:
Change the COMPARE FROM value to a value less than or equal to the COMPARE TO
value, and resubmit the request.
ENBE923W
The STAGE ONE loadlist LIBRARY and the STAGE TWO loadlist LIBRARY refer to the
same data set
Reason:
The STAGE ONE LOAD or LIST LIBRARY and the corresponding STAGE TWO LOAD or LIST
LIBRARY refer to the same data set. The DEFINE SYSTEM action continues processing.
Action:
None. However, if the STAGE ONE LOAD or LIST library should be different than the
corresponding STAGE TWO LIBRARY, use the DEFINE SYSTEM action to make the
appropriate change.
ENBE Messages
ENBE924E
The name name is not valid
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action contained a clause that specified an
invalid value. The name identifies the DEFINE, DELETE, or BUILD SCL FOR action clause
that contained the invalid parameter. In general, the values specified on a DEFINE,
DELETE, or BUILD SCL FOR action clause can contain only alphanumeric and national
characters. For a detailed | description of the valid characters for each action clause, see
the SCL Reference Guide.
Action:
Specify a valid value for the action clause that was identified, and resubmit the request.
ENBE925E
The Stage Number must be a 1 or 2
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action STAGE NUMBER can only be a 1 or a 2.
Action:
Change the STAGE NUMBER to a 1 or a 2. Resubmit the request.
ENBE926E
Language language is not a valid [PANVALETLIBRARIAN] language
Reason:
The language specified for the PANVALET or LIBRARIAN LANGUAGE clause is not a valid
CA Panvalet or CA Librarian language.
Action:
Specify a valid CA Panvalet or CA Librarian language. For a list of valid CA Panvalet or CA
Librarian languages, see the SCL Reference Guide.
ENBE Messages
ENBE927C
The COMPARE COLUMN values are outside the standard range for the for the
[PANVALETLIBRARIANEXTERNAL LANGUAGE] language
Reason:
The COMPARE FROM and TO column values fall outside the standard column range for
the language identified. The DEFINE TYPE continues processing the request.
Action:
If the COMPARE column range identified in the message is correct, no changes are
necessary. For a list of the standard COMPARE column ranges for each standard
language, see the SCL Reference Guide.
ENBE928E
The name cannot be wildcarded
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action contained a clause that specified a
wildcarded value. The name field identifies the action clause that does not support
wildcards.
Action:
Specify a fully qualified value for DEFINE, DELETE, or BUILD SCL FOR action clause
specified in the message. Resubmit the request.
ENBE929E
The name cannot be partially wildcarded
Reason:
The DEFINE, DELETE, or BUILD SCL FOR APPROVER RELATION action contained a clause
that specified a partially wildcarded value. The name field identifies the clause that does
not support partial wildcards. The value specified for the clause that was identified must
be either fully qualified or fully wildcarded.
Action:
Specify a fully qualified or a fully wildcarded value for the action clause specified, and
ENBE Messages
ENBE932E
The COMPARE fromto column value value is greater than the Type Source Element
Length value
Reason:
The COMPARE FROM or TO value specified on the DEFINE TYPE action is greater than
the source element length. The source element length can be obtained from the existing
type definition or from the SOURCE ELEMENT LENGTH clause.
Action:
Change the COMPARE FROM clause so that the values are less than or equal to the
SOURCE ELEMENT LENGTH or change the SOURCE ELEMENT LENGTH so that it is greater
than or equal to the COMPARE TO value. Resubmit the request.
ENBE936E
A TO DDNAME or TO DSNAME clause must be specified
Reason:
The BUILD SCL FOR action requires either the TO DSNAME or the TO DDNAME. These
clauses identify the location to which the DEFINE SCL statements will be written.
Action:
Add a valid TO DDNAME or TO DSNAME clause to the BUILD SCL FOR action, and
ENBE937E
The name must be specified
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action is missing the clause identified. The
missing clause is required for the action.
Action:
Specify the missing clause and resubmit the request.
ENBE Messages
ENBE938E
The FROM Stage ID or Stage Number must be specified
Reason:
The DELETE or BUILD SCL FOR request requires the FROM STAGE ID or FROM STAGE
NUMBER clause. The request did not contain such a clause.
Action:
Add either the FROM STAGE ID or the FROM STAGE NUMBER clause to the action, and
ENBE939E
The [PANVALETLIBRARIAN] LANGUAGE clause does not match your C1DEFLTS table
Reason:
There is a mismatch between the DEFINE TYPE request and the level of CA Panvalet or
CA Librarian support that is specified in the C1DEFLTS table. The level of CA Panvalet or
CA Librarian support is identified by the LIBENV parameter on the C1DEFLTS TYPE=MAIN
macro. The mismatch can occur under the following circumstances:
C1DEFLTS indicates that CA Panvalet is installed and the DEFINE TYPE action
specified the LIBRARIAN LANGUAGE clause.
C1DEFLTS indicates that CA Librarian is installed and the DEFINE TYPE action
specified the PANVALET LANGUAGE clause.
C1DEFLTS indicates that neither CA Panvalet nor CA Librarian is installed and the
DEFINE TYPE action specified either the PANVALET LANGUAGE or LIBRARIAN
LANGUAGE clause.
Action:
If neither CA Panvalet nor CA Librarian are installed, do not specify the LIBRARIAN or
PANVALET LANGUAGE clause. If CA Librarian is installed, use the LIBRARIAN LANGUAGE
clause. If CA Panvalet is installed, use the PANVALET LANGUAGE clause. Resubmit the
request.
ENBE Messages
ENBE940E
The [basedeltaincludesource output] Library contained invalid symbolics
Action:
See message ENBE942E.
ENBE941E
Data set Name = data set name
Action:
See message ENBE942E.
ENBE942E
Invalid Symbolics = data set name
Reason:
Symbolics were being resolved in the BASE, DELTA, INCLUDE, or SOURCE OUTPUT
LIBRARY. The symbolics were invalid. Messages ENBE941 and ENBE942 contain the
details of the error message. There will be plus signs (+) in the data set name for
message ENBE942 to show the locations of the invalid symbolics.
Action:
Correct the symbolics in the BASE, DELTA, INCLUDE or SOURCE OUTPUT LIBRARY name.
ENBE950E
When DEFINE TYPE is PROCESS, the LANGUAGE must be CNTLPROC
Reason:
Type PROCESS is a special type and the language specified in the LANGUAGE clause must
be CNTLPROC.
Action:
Change the language in the LANGUAGE clause to CNTLPROC and resubmit the request.
ENBE Messages
ENBE952E
The SEQUENCE clause must be specified
Reason:
The DEFINE TYPE SEQUENCE action requires at least one valid SEQUENCE clause but the
request did not contain a SEQUENCE clause.
Action:
Add the appropriate SEQUENCE clause to resequence the Type names into the sequence
that you want, and resubmit the request.
ENBE953E
Sequence Number value is invalid. Sequence Number must be between 0 and 9999
Reason:
The Sequence Number specified must be between 0 and 9999.
Action:
Change the invalid sequence number to a value between 0 and 9999, and resubmit the
request.
ENBE954E
Only one of the TO DDNAME or TO DSNAME clauses may be specified, not both
Reason:
The BUILD SCL FOR action specified both the TO DDNAME and the TO DSNAME clauses.
These clauses are mutually exclusive. Only one of the clauses can be specified.
Action:
Remove either the TO DDNAME clause or the TO DSNAME clause, and resubmit the
request.
ENBE Messages
ENBE955E
TYPE SEQUENCE number value is invalid. The TYPE SEQUENCE number cannot be a
multiple of 10
Reason:
The Type Sequence number specified on the SEQUENCE clause cannot be a multiple of
10, for example, 10, 20, 30, and so on. The Type Sequence number can be any value that
is not a multiple of 10.
Action:
Change any sequence numbers specified that are multiples of 10, and resubmit the
request.
ENBE956E
The number of (type, sequence) pairs exceeds the maximum. The maximum number
of (type, sequence) pairs is 256
Reason:
The Maximum Number of (type, sequence) pairs is 256. Since the maximum number of
TYPES for one SYSTEM is 256, it is not possible to resequence more than 256 (type,
sequence) pairs.
Action:
Remove any (TYPE, SEQUENCE) pairs that are not valid, and resubmit the request.
ENBE957E
When processor group is *NOPROC* clause clause cannot be specified
Reason:
If the DEFINE PROCESSOR GROUP is for the Group *NOPROC*, the clause identified is
not allowed on the request.
Action:
Remove the invalid clause from the DEFINE PROCESSOR GROUP request and resubmit
the job.
ENBE Messages
ENBE958E
generatemovedelete PROCESSOR name name is an Endevor reserved processor
name
Reason:
GENERATE, DELETE, or MOVE Processors cannot be named with Reserved Processor
names. The following Processor Names are reserved by CA Endevor SCM: BASICDEL,
BASICGEN, DPPROCESS, and GPPROCSS.
Action:
Specify a valid, non-reserved name for the GENERATE, DELETE, or MOVE processor, and
ENBE959E
The FROMTO PROCESSOR GROUP name cannot be *NOPROC*
Reason:
The FROM or TO Processor Group Name must be a valid Processor Group, and cannot
be *NOPROC*.
Action:
Change the FROM or TO PROCESSOR GROUP name to the name of a valid Processor
Group, and resubmit the request.
ENBE960E
A duplicate Symbol name, name, was specified
Reason:
The DEFINE or DELETE PROCESSOR SYMBOL action specified a duplicate symbol name
on the SYMBOL clause.
Action:
Change the duplicate symbol names so that the names are unique, and resubmit the
request.
ENBE Messages
ENBE961E
A duplicate Approver ID, userid, was specified
Reason:
The duplicate Approver ID was specified. The Approver IDs specified for an Approver
Group must be unique.
Action:
Remove the duplicate Approver ID from the APPROVER clause of the DEFINE APPROVER
action, and resubmit the request.
ENBE962E
More than 16 Approvers have been specified for Approver Group name
Reason:
An Approver Group can have a maximum of 16 Approver User IDs. The DEFINE
APPROVER GROUP action specified more than 16 Approver User IDs on the APPROVER
clause.
Action:
Specify a maximum of 16 Approver User IDs on the APPROVER clause of the DEFINE
APPROVER GROUP action, and resubmit the request.
ENBE963E
Transmission Method method is not valid
Reason:
The DEFINE SHIPMENT DESTINATION action specified an invalid TRANSMISSION
METHOD. For a list of valid Transmission Methods, see the SCL Reference Guide.
Action:
Correct the TRANSMISSION METHOD clause. Resubmit the request.
ENBE Messages
ENBE964E
The name cannot contain embedded blanks
Reason:
The REMOTE NODENAME, HOST UNIT, or REMOTE UNIT name contains embedded
blanks.
Action:
Remove the embedded blanks from the REMOTE NODENAME, HOST UNIT, or REMOTE
UNIT name, and resubmit the request.
ENBE965E
The DEFINE PROCESSOR SYMBOL action requires at least one SYMBOL clause
Reason:
The DEFINE PROCESSOR SYMBOL action requires at least one valid SYMBOL clause. The
request did not contain any SYMBOL clauses.
Action:
Add at least one valid SYMBOL clause to the request, and then resubmit the request.
ENBE966E
The REMOTE DATA SET clause cannot be specified when the EXCLUDE clause is
specified
Reason:
The DEFINE SHIPMENT DESTINATION action REMOTE DATA SET clause and the EXCLUDE
clauses are mutually exclusive.
Action:
Remove either the REMOTE DATA SET clause or the EXCLUDE clause, and resubmit the
request.
ENBE Messages
ENBE967E
The clause must be specified
Reason:
The DEFINE action did not contain the identified clause. The clause is required for the
action to complete.
Action:
Add the required clause to the request and resubmit the request.
ENBE968E
The NUMBER OF elementcomponent LEVELS TO CONSOLIDATE cannot exceed the
CONSOLIDATE elementcomponent AT LEVEL value
Reason:
The NUMBER OF ELEMENT LEVELS or the NUMBER OF COMPONENT LEVELS is greater
than the corresponding CONSOLIDATE ELEMENT AT LEVEL or CONSOLIDATE
Action:
Specify a NUMBER OF ELEMENT LEVELS or NUMBER OF COMPONENT LEVELS value that
is less than or equal to the corresponding CONSOLIDATE ELEMENT AT LEVEL or
CONSOLIDATE COMPONENT AT LEVEL value, and resubmit the request.
ENBE969W
The DO NOT COMPRESS BASE will be ignored because ELEMENT DELTA FORMAT is
FORWARD.
Reason:
When ELEMENT DELTA FORMAT IS FORWARD is specified, the base files have to be
compressed. If the DO NOT COMPRESS BASE clause is specified, it is ignored.
Action:
None.
ENBE Messages
ENBE970E
The NUMBER OF elementcomponent LEVELS must be zero when the DO NOT
CONSOLIDATE elementcomponent LEVELS is specified.
Reason:
The NUMBER OF ELEMENT LEVELS or the NUMBER OF COMPONENT LEVELS must be
zero when CONSOLIDATE element LEVELS or CONSOLIDATE component LEVELS is
specified.
Action:
Specify a value of zero for the NUMBER OF ELEMENT LEVELS OR NUMBER OF
COMPONENT LEVELS, and resubmit the request.
ENBE971E
The SOURCE ELEMENT LENGTH for the TYPE PROCESS must be 80
Reason:
The SOURCE ELEMENT LENGTH for TYPE PROCESS does not have the value of 80.
Action:
Specify a value of 80 for the SOURCE ELEMENT LENGTH, and resubmit the request.
ENBE972E
The STAGE onetwo LOAD LIBRARY is not allowed when Processor support is not
available
Reason:
If the Extended Processor support option was not purchased (or missing the PROC
password in the C1DEFLTS table), the DEFINE SYSTEM action does not support the
STAGE ONE or LOAD LIBRARY and the STAGE TWO LOAD LIBRARY clauses.
Action:
Either remove the STAGE ONE LOAD LIBRARY or the STAGE TWO LOAD LIBRARY clauses
(or both) from the DEFINE SYSTEM action and resubmit the request, or define the
password and reassemble and link the C1DEFLTS table.
ENBE Messages
ENBE973E
The DEFINE TYPE action cannot specify the type PROCESS when Processor support is
not available
Reason:
password in the C1DEFLTS table), the DEFINE TYPE action does not support the Type
name 'PROCESS'
Action:
Either change the Type name specified on the DEFINE TYPE action and resubmit the
request or define the password and reassemble and link the C1DEFLTS table.
ENBE974E
The DEFINE PROCESSOR GROUP action does not allow the name name when Processor
support is not available
Reason:
password in the C1DEFLTS table), the DEFINE PROCESSOR GROUP action can only specify
'*NOPROC*' as the GENERATE, DELETE, and MOVE Processor names. Any other
Processor Name is invalid.
Action:
Either remove the GENERATE, DELETE, or MOVE PROCESSOR clauses, or change the
Processor Names to *NOPROC* and resubmit the request, or define the password and
reassemble and link the table.
ENBE975E
The generatemovedelete PROCESSOR NAME must be *NOPROC* when the
PROCESSOR GROUP name is *NOPROC*
Reason:
When the DEFINE PROCESSOR GROUP name is *NOPROC*, the generatemovedelete
PROCESSOR names, if specified, must also be *NOPROC*.
Action:
Either remove the GENERATE, DELETE, MOVE PROCESSOR clauses, or change the
Processor Names to *NOPROC*. Resubmit the request.
ENBE Messages
ENBE976E
The BASEDELTASTAGE ONE LOADSTAGE TWO LOAD LIBRARY cannot be blank
Reason:
The data set name for the DEFINE action clause identified was blank. The data set name
must be a valid, non-blank name.
Action:
Specify a valid data set name for the identified clause and resubmit the request.
ENBE977E
The STAGE ID and the STAGE NUMBER cannot both be specified
Reason:
The DEFINE, DELETE, or BUILD SCL FOR action specified both the STAGE ID clause and
the STAGE NUMBER clause. Only one of these clauses can be specified.
Action:
Remove either the STAGE ID clause or the STAGE NUMBER clause and resubmit the
request.
ENBE978E
When DEFINE TYPE is not PROCESS, the LANGUAGE cannot be CNTLPROC
Reason:
The DEFINE TYPE action specified 'CNTLPROC' on the LANGUAGE clause must
CNTLPROC. The 'CNTLPROC' LANGUAGE is reserved for the Type name 'PROCESS'. The
DEFINE TYPE action was for a Type other than 'PROCESS'. Therefore, the LANGUAGE
clause cannot specify the value 'CNTLPROC'.
Action:
Correct the LANGUAGE clause of the Type name and resubmit the request.
ENBE Messages
ENBE979W
When the TYPE name is PROCESS, the PANVALETLIBRARIAN LANGUAGE must be
datadat. It has been changed to datadat
Reason:
When the TYPE name is PROCESS and the PANVALET LANGUAGE is specified it must be
DATA. If the LIBRARIAN LANGUAGE is specified it must be DAT. Any other values
specified in these fields will be changed to DATA or DAT.
Action:
None.
ENBE980E
The SIGNOUT DATA SET VALIDATION IS ACTIVE clause is only valid when SIGNOUT IS
ACTIVE
Reason:
If the SIGNOUT DATA SET VALIDATION IS ACTIVE clause is specified, the SIGNOUT IS
ACTIVE is a valid combination. If SIGNOUT IS NOT ACTIVE is specified you will receive
this error.
Action:
ACTIVE. Resubmit the request.
ENBE981E
When the TYPE name is PROCESS, the DEFAULT PROCESSOR GROUP must be PROCESS
Reason:
The DEFAULT PROCESSOR GROUP name was not PROCESS for TYPE PROCESS.
Action:
Change the DEFAULT PROCESSOR GROUP name to PROCESS and resubmit the request.
ENBE Messages
ENBE982E
When TYPE name is PROCESS, the clause clause cannot be specified
Reason:
If the DEFINE TYPE or DEFINE PROCESSOR GROUP is for the Type 'PROCESS', the clause
cannot be specified.
Action:
Remove the invalid clause from the DEFINE TYPE or DEFINE PROCESSOR GROUP and
ENBE983E
When TYPE name is PROCESS, the generatemovedelete PROCESSOR NAME must be
gpprocssdpprocss
Reason:
If the TYPE name is PROCESS the GENERATE and MOVE Processor names must be
GPPROCSS and the DELETE PROCESSOR name must be DPPROCSS.
Action:
Correct the invalid processor name and resubmit the request.
ENBE983E
The final control statement is missing a terminating period
Reason:
The final control statement did not contain a terminating period. All Batch Environment
Administration Facility control statements must be terminated with a period.
Action:
Add a terminating period to the final control statement, and resubmit the request.
ENBP Messages
ENBP Messages
This section details messages generated in the course of Batch Package Facility
ENBP001E
Package ID name was not found
Reason:
A fully specified package ID was provided on the Batch Package Facility request but the
package ID was not defined or is not available. It is possible that the package exists but
the LIST BEFORE or AFTER exit has suppressed presenting the package. It is also possible
that the ID associated with the batch job is not an approver or that the package is not
sharable.
Action:
Verify that the correct package ID was specified on the request. If the correct package ID
was specified, verify that you are authorized to access the package. If you did not create
the package, the package must be defined as a sharable package. If the package has one
or more approver groups associated with it, you must be a member of one of the
approver groups. If you are authorized to access the package, contact your
administrator to determine if the LIST BEFORE or AFTER exits are suppressing the
package.
ENBP001W
Package ID 'name' was not found
Reason:
A fully specified DELETE PACKAGE action was provided on the Batch Package Facility
request but the package ID was not defined or is not available. It is possible that the
package exists but the LIST BEFORE or AFTER exit has suppressed presenting the
package. It is also possible that the ID associated with the batch job is not an approver
or that the package is not sharable.
Action:
Verify that the correct DELETE PACKAGE action was specified on the request. If the
correct DELETE PACKAGE action was specified, verify that you are authorized to access
the package. If you did not create the package, the package must be defined as a
sharable package. If the package has one or more approver groups associated with it,
you must be a member of one of the approver groups. If you are authorized to access
the package, contact your administrator to determine if the LIST BEFORE or AFTER exits
are suppressing the package.
ENBP Messages
ENBP002E
No matches were found for package ID 'name'
Reason:
A partially or fully wildcarded package ID was specified on the Batch Package Facility
request but there were not packages that matched the mask specified. It is possible that
one or more packages exist but that the LIST BEFORE or AFTER exit suppressed
presenting the package. It is also possible that the ID associated with the batch job is not
an approver or that the package is non sharable. If the WHERE OLDER THAN clause was
specified, it is possible that there are no packages older than the number of days
specified. If the WHERE PACKAGE STATUS clause was specified, it is possible that there
are no packages in the specified state.
Action:
was specified, verify that you are authorized to access the packages that may match the
wildcard. If you did not create the packages, the packages must be defined as a sharable
package. If the packages have one or more approver groups associated with it, you must
be a member of one of the approver groups. If you are authorized to access the
packages, contact your administrator to determine if the LIST BEFORE or AFTER exits are
suppressing the packages.
ENBP003E
Program initialization failed. Processing will terminate
Reason:
The Batch Package Facility initialization routine encountered one or more errors. One or
more error messages should precede message ENBP003E. The Batch Package Facility
will terminate with a return code of 12.
Action:
Perform the corrective action associated with the error message that preceded message
ENBP003E.
ENBP Messages
ENBP004E
The ENPSCLIN DD statement was not allocated
Reason:
The ENPSCLIN DD statement was not allocated to the session. The ENPSCLIN DD
statement defines the Batch Package Facility control statements.
Action:
Add a valid ENPSCLIN DD statement to the execution JCL and resubmit the JCL.
ENBP005E
The ENPSCLIN DD statement has incorrect attributes
Reason:
The data set that the ENPSCLIN DD statement refers to has the incorrect attributes. The
data set must be either sequential or partitioned (with a member specification), it must
contain either fixed or variable length records and the record length must be exactly 80
for RECFM=F and at least 84 for RECFM=V.
Action:
Add a valid ENPSCLIN DD statement to the execution JCL or reallocate the data set that
was specified with the correct attributes. Resubmit the JCL.
ENBP006E
No valid action statements were found. Action processing will not occur
Reason:
The ENPSCLIN data set did not contain any valid action SCL statements. Either the data
set was empty or the data set contained syntactically invalid statements. Package action
processing will terminate.
Action:
Change the ENPSCLIN DD statement to refer to a data set that contains valid Batch
Package facility control statements. Resubmit the job.
ENBP Messages
ENBP007E
Unable to load external program name
Reason:
The Batch Package Facility initialization routine was unable to dynamically load the
named program. The initialization routine will fail and the program will terminate.
Action:
Verify that the execution JCL contains the appropriate data sets in the CONLIB DD
statement. Check the JES system log for the job for any system messages that may
indicate a system error and, if any are present, take the corrective action for those
errors. If the problem persists, contact CA Technical Support.
ENBP009E
User generated package ID 'name' is already defined
Reason:
The package ID returned by the GENPKGID exit already exists in the package file. The
package name returned by the GENPKGID exit must be unique.
Action:
Either specify a fully qualified package ID or resubmit the request to redrive the
GENPKGID exit. If the problem persists, contact the administrator to determine why the
installation GENPKGID exit is generating a duplicate Package ID.
ENBP010I
Processing is complete. Highest return code is rc
Reason:
The Batch Packages Facility program has completed execution. The program will
terminate with the return code specified.
Action:
No action is necessary.
ENBP Messages
ENBP011I
Statement number Package number
Reason:
This message appears in the Action Execution report to identify the current action
number that is being processed. The statement number refers to the corresponding
action in the Control Statement Summary report.
Action:
ENBP012I
Beginning execution of the action action
Reason:
The Batch Package Facility is passing control to the Package Application Interface to
perform the action specified.
Action:
ENBP013E
You are not authorized to perform the action PACKAGE action
Reason:
The user is not authorized to access the Batch Package Facility.
Action:
Contact CA Technical Support to obtain the necessary authorization to execute the
Batch Package Facility.
ENBP Messages
ENBP020E
Data set data set name could not be allocated. S99ERROR=s99error, S99INFO=s99info
Reason:
The specified data set could not be dynamically allocated. The s99error and s99info
fields identify the Dynamic Allocation error and information codes that were returned
with the request.
Action:
See the IBM publication GC28-1852 Systems Programming Library: Application
Development Guide (or the equivalent manual for your release of x/OS90) for the
definition of the error and information codes. Correct the condition and resubmit the
request. If the error persists, it may be necessary to contact your system administrator
or CA Technical Support.
ENBP023I
The action action has completed for package ID 'name'. Return Code is return code
Reason:
The action identified has been successfully performed against the package named. If the
return code is greater than zero, one or more messages should precede message
ENBP023I to indicate the reason for the non-zero return code.
Action:
ENBP050E
The DEFINE PACKAGE DESCRIPTION is required for a new package
Reason:
The DEFINE action has determined that a new package is to be created but the
DESCRIPTION clause was not specified on the DEFINE action. The DESCRIPTION clause is
required when a new package is being created.
Action:
Add the DESCRIPTION clause to the request and resubmit the request.
ENBP Messages
ENBP051C
Package ID ' name' will not be updated. No additional package information was
provided
Reason:
The DEFINE PACKAGE control statements did not include an IMPORT SCL FROM, COPY
PACKAGE, DESCRIPTION, or any OPTIONS clauses. The package will not be updated
because there is no information to be added to the package.
Action:
Add the DESCRIPTION, IMPORT SCL FROM, or COPY PACKAGE FROM clause or one or
more of the OPTION clauses to the request and resubmit the request.
ENBP052E
Data set data set name could not be located in the system catalogue
Reason:
The data set specified on the DEFINE PACKAGE IMPORT SCL FROM DSNAME clause or
the SUBMIT PACKAGES JOBCARD DSNAME clauses could not be located in the system
catalogue.
Action:
Verify that the correct data set name was specified in the request and verify that the
data set is catalogued. If the incorrect data set name was specified, correct and
ENBP053E
Member name could not be found in data set data set name
Reason:
The member name specified on the DEFINE PACKAGE IMPORT SCL FROM DSNAME
MEMBER clause or the SUBMIT PACKAGE JOBCARD DSNAME MEMBER clause could not
be found in the data set specified.
Action:
Change the MEMBER clause to refer to a member that exists in the data set or create
the member in the data set. Resubmit the request.
ENBP Messages
ENBP054E
The ddname DD statement has not been allocated
Reason:
The DD statement specified on the DEFINE PACKAGE IMPORT SCL FROM DDNAME
clause, the SUBMIT PACKAGE JOBCARD DDNAME clause, or the SUBMIT PACKAGE
INTERNAL READER DDNAME clause is not allocated to the Batch Package Facility
session.
Action:
Add the specified DD statement to the execution JCL. Resubmit the request.
ENBP055E
The COPY PACKAGE FROM package ID 'name' was not found
Reason:
The package specified on the DEFINE PACKAGE action COPY PACKAGE FROM clause
could not be found.
Action:
Verify that the correct package ID was specified on the COPY PACKAGE FROM clause. If
the package ID does not exist, change the clause to refer to a package that does exist.
ENBP057E
Package SCL was not provided for new package ID name
Reason:
The DEFINE package action will create a new package but SCL for the package was not
provided. In order to create a new package, the IMPORT SCL FROM or COPY PACKAGE
FROM clause must be specified. These clauses define the location of the package SCL.
Action:
Specify the location of the SCL to be added to the package by specifying either an
IMPORT SCL FROM or a COPY PACKAGE FROM clause to the DEFINE action. Resubmit
the request.
ENBP Messages
ENBP058E
Data set data set name has the incorrect attributes for the action action
Reason:
The data set identified has invalid attributes for the package action requested.
Action:
For the action to determine the appropriate characteristics for the data set that is
invalid, see the SCL Reference Guide. Either refer to a data set with the correct attributes
or reallocate the specified data set with the correct attributes. Resubmit the request.
ENBP059E
The INTERNAL READER DD, dd name, has incorrect attributes
Reason:
The INTERNAL READER DD statement does not have the correct attributes. The DD
statement must specify a sequential data set that has fixed length, 80 byte records.
Action:
Verify that the data set that the INTERNAL READER DD statement refers is a sequential
data set with fixed length records and a record length of 80. If the DD statement refers
to a SYSOUT data set, it may be necessary to add the
DCB=(LRECL=80,RECFM=F,BLKSIZE=80) statement to the DD statement. Resubmit the
request.
ENBP Messages
ENBP060E
No packages were available that match package ID 'name'
Reason:
The request contained a wildcarded package name. The wildcard expansion routine
found at least one package ID that matched the wildcarded package ID that was
specified. The package or packages were not selected for one or more of the following
reasons:
The package was created with the NONSHARABLE PACKAGE clause and the current
user did not create the package.
The package has one or more Approver Groups associated with it and the current
user is not a member of any of the Approver Groups.
The package is not in the correct state for the action. For example, the request was
EXECUTE and the package was in the IN-EDIT state.
The package did not pass the WHERE PACKAGE STATUS or WHERE OLDER THAN
clause filter criteria.
Action:
If the action request contained an OPTIONS WHERE clause, change the clause to
broaden the selection criteria. For example, change the WHERE OLDER THAN clause to a
smaller value to enlarge the number of possible packages selected. If the package has
one or more Approver Groups, verify that you are a member of one of the Approver
Groups. Contact your administrator to be placed in the appropriate Approver Group, if
necessary. If the package is non-sharable, contact the owner of the package and have
the owner perform the desired action.
ENBP061E
Package ID 'name' has an invalid package state of 'state'
Reason:
The package state associated with the package identified contains an undefined value.
Action:
Use the ISPF dialog to verify the status of the package. If the package has a valid status,
resubmit the request. If the package status is invalid, contact your administrator.
ENBP Messages
ENBP062E
Package ID package id is not available for the action action
Reason:
The indicated package ID is not available for the indicated action.
Action:
Verify the package ID and resubmit the action request.
ENBP071E
Member name already exists in data set data set name
Reason:
The member name specified on the EXPORT SCL TO DSNAME MEMBER clause already
exists in the data set specified and the REPLACE clause was not specified. The REPLACE
clause is required in order to overwrite an existing member.
Action:
Either specify the name of a member that does not exist or add the REPLACE keyword to
the MEMBER clause. Resubmit the request.
ENBP076I
Data set data set name is sequential. The TO MEMBER clause will be ignored
Reason:
The TO DSNAME MEMBER clause was specified for a sequential data set. The action will
ignore the MEMBER name specified.
Action:
ENBP Messages
ENBP077W
Data set data set name is sequential. The MEMBER clause will be ignored
Reason:
The IMPORT SCL FROM DSNAME MEMBER clause was specified for a sequential data
set. The action will ignore the MEMBER name specified.
Action:
No action is necessary. To eliminate the message, either remove the MEMBER clause or
specify a partitioned data set that contains the member specified in the MEMBER
clause.
ENBP078E
Data set data set name is partitioned but the MEMBER clause was not specified
Reason:
The data set specified on the DEFINE action IMPORT SCL FROM DSNAME clause is a
partitioned data set and the MEMBER clause was not specified. A member clause is
required in order to identify the member to be used by the DEFINE action.
Action:
Either add a MEMBER clause to the IMPORT SCL FROM DSNAME clause or change the
data set name specified on the IMPORT SCL FROM DSNAME clause to a sequential data
set. Resubmit the request.
ENBP079E
The new EXECUTION WINDOW FROM value is later than the existing EXECUTION
WINDOW TO value
Reason:
The request specified the EXECUTION WINDOW FROM value but did not specify an
EXECUTION WINDOW TO value. The EXECUTION WINDOW FROM value specified on the
request is later than the EXECUTION WINDOW TO value that is already associated with
an existing package.
Action:
Either change the EXECUTION WINDOW FROM value to a date and time that is earlier
than the existing EXECUTION WINDOW TO value or add an EXECUTION WINDOW TO
clause to the request. Resubmit the request.
ENBP Messages
ENBP080E
The EXECUTION WINDOW cannot be modified because the existing EXECUTION
WINDOW is still open
Reason:
The EXECUTE PACKAGE request specified the EXECUTION WINDOW clause but the
EXECUTION WINDOW that is associated with the package is still open; that is, the
current date and time falls within the EXECUTION WINDOW FROM and TO time range.
The EXECUTE PACKAGE action can only change the Execution Window if the Window is
closed.
Action:
Either remove the EXECUTION WINDOW clause from the request or wait for the existing
Execution Window to close. Resubmit the request.
ENBP081E
Processing will terminate because of an application ABEND
Reason:
An unrecoverable ABEND occurred during Batch Package Facility execution. One or
more messages should precede message ENBP081E to indicate the error that occurred.
The Batch Package Facility will immediately terminate.
Action:
Resubmit the request. If the problem persists, contact CA Technical Support.
ENBP082E
Package 'name' was not defined with BACKOUT ENABLED
Reason:
The BACKOUT PACKAGE action cannot process the package because the package was
not defined with the BACKOUT ENABLED option.
Action:
Verify that the correct package ID was specified on the BACKIN PACKAGE request.
ENBP Messages
ENBP083E
Package 'name' has not been backed-out
Reason:
The BACKIN PACKAGE action cannot process the package specified because the package
has not been backed-out.
Action:
Verify that the correct package ID has been specified on the BACKIN PACKAGE action.
ENBP090S
Function function name was unable to obtain X'size' bytes of storage
Reason:
The specified function was unable to obtain the specified amount of storage. Processing
will terminate with a return code of 16.
Action:
Increase the REGION= parameter on the JOB or EXEC JCL statement and resubmit the
request. If the problem persists, reduce the number of actions that are specified by the
ENPSCLIN DD statement.
ENBP091S
Internal error in function name. error text
Reason:
An internal logic error occurred in the function identified. The error text may provide an
indication of the error.
Action:
ENBP Messages
ENBP092S
Internal error in function name. Unable to build a TDF for field code X'field code'
Reason:
The specified function was unable to build a TDF. The Build TDF routine returned a NULL
pointer. The field code value identifies the field code of the TDF to be built.
Action:
ENBP093S
Internal error in function name. The PAI returned a NULL TFC pointer
Reason:
Action:
ENBP094S
Internal error in function name. The PAI did not return data for TDF X'field code'
Reason:
Action:
ENBP095E
Internal error in function name. Error text
Reason:
A call to the Package Interface routine returned a non-zero return code or interface
return code. The Error Text contains a formatted interpretation of the return code from
the Package Application Interface.
Action:
ENBP Messages
ENBP095S
Internal error in function name. Error text
Reason:
return code. The Error Text contains a formatted interpretation of the return code from
the Package Application Interface.
Action:
ENBP096S
Internal error in function name. Return Code=X'reason code', Reason Code=X' reason
code'
Reason:
return code. The message contains the interface return and reason codes and the
function return code. This message is issued if the return code and reason code cannot
be converted into a message string.
Action:
ENBP097S
Internal error. Unable to obtain a new I/O Object
Reason:
An internal error occurred while allocating a new I/O Object.
Action:
ENBP Messages
ENBP200S
A abend code ABEND occurred in function function
Reason:
The Batch Package Facility ABENDed with the code identified. The current action will
terminate processing immediately and any remaining, unexecuted actions will not be
executed.
Action:
Resubmit the request. If the problem persists, contact CA Technical Support. Before
calling Technical Support, however, add the following card to the execution JCL and
resubmit the request:
a //SYSABEND DD SYSOUT=_
This JCL statement will create a diagnostic dump when the ABEND occurs.
ENBP900I
Reason:
The Batch Package Facility is beginning to parse the user supplied control statements.
Action:
ENBP901I
Reason:
The Batch Package Facility has completed parsing the control statements and no errors
were detected.
Action:
ENBP Messages
ENBP902E
Control statement parsing has completed with one or more errors
Reason:
The Batch Package Facility has completed parsing the control statements. One or more
errors were detected in the control statements. None of the control statements will be
executed.
Action:
Correct the errors identified by the parsing and validation routine and resubmit the JCL.
ENBP903E
The package ID must be fully qualified. Wild cards are not allowed
Reason:
The package ID specified on the DEFINE, APPROVE, DENY, BACKOUT, BACKIN, RESE, or
EXPORT action contained a wildcard character. These actions do not support wildcarded
package IDs.
Action:
Change the package ID that was specified on the action so that it does not contain a
wildcard character. Resubmit the JCL.
ENBP904E
PKG window FROM/TO dates and times are the same. PKG can not execute.
Reason:
The user set the Package Execution window with the same FROM/TO Date and Time.
Action:
Ensure that the Package Execution Window is at least one minute.
ENBP Messages
ENBP905E
The WHERE OLDER THAN clause is required with a wild card package ID
Reason:
The COMMIT or DELETE action specified a wildcarded package ID but the WHERE OLDER
THAN clause was not specified. The WHERE OLDER THAN clause is required when a
wildcarded package ID is specified.
Action:
Either add the appropriate WHERE OLDER clause to the request or specify a fully
qualified package ID. Resubmit the request.
ENBP906E
The EXECUTION WINDOW FROMTO DATETIME value is invalid
Reason:
The date or time value specified on the EXECUTE WINDOW clause is syntactically invalid.
The date value must be specified in the format DDMMMYY and the time value must be
specified in the format HH:MM. For example, January 1, 1993 would be specified as
01JAN93 and 1:30 PM would be specified as 13:30.
Action:
Correct the EXECUTION WINDOW date or time value and resubmit the request.
ENBP907E
The EXECUTION WINDOW FROM date is greater than the TO date
Reason:
The EXECUTION WINDOW FROM date specified is greater than the TO date specified or
the default EXECUTION WINDOW TO date.
Action:
Correct the EXECUTION WINDOW clause so that the FROM date and time is earlier than
the TO date and time.
ENBP Messages
ENBP908E
The EXECUTION WINDOW TO DATETIME is earlier than the current DATETIME
Reason:
The EXECUTION WINDOW TO date or time specified is earlier than the current system
date and time. The EXECUTION WINDOW TO value must be later than the date and time
that the action is being executed.
Action:
Correct the EXECUTION WINDOW TO clause so that the date and/or time specified is
later than the current date and time. Resubmit the request.
ENBP909E
The TO DDNAME clause is mutually exclusive with the TO DSNAME clause
Reason:
The EXPORT PACKAGE action specified both a TO DDNAME and a TO DSNAME clause.
The clauses are mutually exclusive. Only one of the clauses can be specified.
Action:
Remove either the TO DDNAME or the TO DSNAME clause from the EXPORT PACKAGE
action. Resubmit the JCL.
ENBP910E
The TO DDNAME or the TO DSNAME clause is required
Reason:
The EXPORT PACKAGE action did not specify either a TO DDNAME or a TO DSNAME
clause. One of the two clauses is required.
Action:
Add either the TO DDNAME or the TO DSNAME clause to the EXPORT PACKAGE action. If
the TO DDNAME is added, also add the DD Name to the execution JCL. Resubmit the JCL.
ENBP Messages
ENBP911W
The WHERE OLDER THAN clause is ignored for fully specified package IDs
Reason:
The COMMIT PACKAGE or DELETE PACKAGE action contained a fully specified package
ID and the WHERE OLDER THAN clause was also specified. The WHERE OLDER THAN
clause is ignored when a fully specified package ID is provided.
Action:
No action is necessary. To eliminate this message, remove the WHERE OLDER THAN
clause from the COMMIT or DELETE PACKAGE action statement.
ENBP912E
The COPY PACKAGE package ID can not be wild carded
Reason:
The DEFINE PACKAGE action contained a COPY PACKAGE FROM clause but the package
ID specified was wildcarded. The package ID must be fully specified.
Action:
Specify a fully qualified package ID on the COPY PACKAGE FROM clause. Resubmit the
request.
ENBP913I
The control statements will be syntax checked but NOT executed
Reason:
The execution JCL contained the PARM=VALIDATE statement. The program will only
syntax check the control statements. The control statements will not be executed.
Action:
No action is necessary. In order to execute the Batch Package Facility control
statements, remove the VALIDATE parameter from the execution JCL.
ENBP Messages
ENBP914E
The program received the following invalid execution parameter:
Reason:
The execution JCL contained an unidentifiable parameter on the PARM statement. The
program will terminate with a return code of 12.
Action:
See message ENBP926E for the invalid JCL PARM parameter. Correct the parameter and
ENBP915E
The FROM DDNAME clause is mutually exclusive with the FROM DSNAME clause
Reason:
The DEFINE action request contained both a FROM DDNAME and a FROM DSNAME
clause. Only one of the clauses can be specified for a specific request.
Action:
Remove one of the two clauses from the request and resubmit the request.
ENBP916E
The WHERE OLDER THAN value must be in the range of 1 to 999, inclusive
Reason:
The value specified on the WHERE OLDER THAN clause was either less than one or
greater than 999.
Action:
Specify a value between 1 and 999, inclusive, for the WHERE OLDER THAN clause.
ENBP Messages
ENBP917E
The JOBCARD DDNAME clause is mutually exclusive with the JOBCARD DSNAME
clause
Reason:
The SUBMIT PACKAGE clause specified both the JOBCARD DDNAME and the JOBCARD
DSNAME clauses. Only one of the clauses can be specified.
Action:
ENBP918E
The STANDARD PACKAGE clause is mutually exclusive with the EMERGENCY PACKAGE
clause
Reason:
The DEFINE PACKAGE clause specified both the STANDARD PACKAGE and the
EMERGENCY PACKAGE clauses. Only one of the clauses can be specified.
Action:
ENBP919E
The SHARABLE PACKAGE clause is mutually exclusive with the NONSHARABLE
PACKAGE clause
Reason:
The DEFINE PACKAGE clause specified both the SHARABLE PACKAGE and the
NONSHARABLE PACKAGE clauses. Only one of the clauses can be specified.
Action:
ENBP Messages
ENBP920E
The EXECUTION WINDOW clause cannot be specified if the package ID is wild carded
Reason:
The EXECUTION WINDOW clause can only be specified with a fully qualified package ID.
The request contained a fully or partially wildcarded package ID.
Action:
Either remove the EXECUTION WINDOW clause from the request or use a fully specified
package ID on the request. Resubmit the request.
ENBP921E
The GENPKGID exit did not supply a package ID
Reason:
The DEFINE PACKAGE statement specified a blank package name but the installation
GENPKGID exit did not provide a replacement package ID.
Action:
If the GENPKGID exit is not being used then supply a non-blank package ID on the
DEFINE PACKAGE action. If the GENPKGID exit is being used, contact CA Technical
Support to determine why the exit did not provide a package ID.
ENBP922E
The package name cannot be blank
Reason:
The action specified a blank package name. Only the DEFINE action supports a blank
package name.
Action:
Specify a valid, non blank package ID on the request. Resubmit the request.
ENBP Messages
ENBP923I
Statement number number
Reason:
This message identifies the current statement number of the SCL statement that is being
parsed.
Action:
ENBP924E
The GENPKGID exit failed. Refer to the previous error messages
Reason:
The Package ID specified on the DEFINE PACKAGE action was blank and the call to the
installation GENPKGID exit failed. For any error messages that the GENPKGID exit may
have generated, see the SCL Reference Guide.
Action:
Determine why the installation GENPKGID exit failed and correct the situation. Resubmit
the request.
ENBP925E
The GENPKGID exit call returned an unexpected return code
Reason:
The GENPKGID exit passed back a return code that could not be handled by the Batch
Package Facility.
Action:
Contact CA Technical Support to determine why the GENPKGID passed a non-standard
return code. Resubmit the request after the situation has been corrected.
ENBP Messages
ENBP926E
parameter text
Reason:
This message is issued immediately after message ENBP914E. It identifies the invalid
parameter that was passed to the Batch Package Facility.
Action:
See message ENBP914E.
ENBP927E
Too many NOTE lines were specified
Reason:
The OPTIONS NOTES clause contained more NOTE text lines than are currently
supported. The maximum number of NOTE text lines that can be specified are eight (8).
Action:
Correct the DEFINE, CAST, APPROVE or DENY PACKAGE action so that at most eight (8)
NOTE text lines are specified. Resubmit the request.
ENBP928W
The WHERE PACKAGE STATUS clause is ignored for a fully qualified package ID
Reason:
The WHERE PACKAGE STATUS clause is valid only when the package ID is wildcarded. It
is ignored for fully qualified package IDs.
Action:
No action is necessary. To eliminate the message, remove the WHERE PACKAGE STATUS
clause from the request.
ENBP Messages
ENBP929E
The WHERE PACKAGE STATUS clause is required with a wild carded package ID
Reason:
The action specified a wildcarded package ID but did not specify a WHERE PACKAGE
STATUS clause.
Action:
Either add the WHERE PACKAGE STATUS clause to the request or provide a fully
specified package ID on the request. Resubmit the request.
ENBP930E
The C1DEFLTS table indicates that Component Validation is mandatory. VALIDATE
COMPONENTS cannot be specified
Reason:
The CAST PACKAGE VALIDATE COMPONENTS clause is invalid if the C1DEFLTS table
indicates that Component validation is mandatory (PKGCVAL=Y).
Action:
Remove the VALIDATE COMPONENTS clause from the CAST request and resubmit the
request.
ENBP931E
The COPY FROM PACKAGE and the IMPORT SCL FROM clauses are mutually exclusive
Reason:
The DEFINE PACKAGE action cannot specify both the COPY FROM PACKAGE and the
IMPORT SCL FROM clauses. These two clauses are mutually exclusive.
Action:
Remove one of the two clauses from the DEFINE PACKAGE action. Resubmit the request.
ENBS Messages
ENBP932E
The final control statement is missing a terminating period
Reason:
The final control statement did not contain a terminating period. All Batch Package
Facility control statements must be terminated with a period.
Action:
Add a terminating period to the final control statement. Resubmit the request.
ENBP933E
Package ID 'name' contains one or more invalid characters
Reason:
The package ID specified on the package action or the COPY PACKAGE FROM clause
contained one or more invalid characters. Only alphanumeric, blanks, and the national
characters # and $ are allowed in a package ID.
Action:
Correct the invalid package ID. Resubmit the request.
ENBS Messages
This section details messages generated in the course of Search and Replace Utility
ENBS000I
Element elementname
Reason:
Informational. Identifies the element name.
Action:
None.
ENBS Messages
ENBS001I
Statement Number nnnn
Reason:
This message indicates that processing for the specified statement has begun. A
formatted version of the SCL statement appears immediately after this message.
Action:
None.
ENBS002I
Processing is complete. Highest return code is nnnn
Reason:
This message indicates that the Search & Replace utility has finished processing, and
displays the highest return code received during execution. This return code is also used
to set the return code for the batch jobstep.
Action:
None.
ENBS003I
SEARCH ELEMENT processing searched nnnn ELEMENTs, updated nnnn ELEMENTs, and
had nnnn errors.
Reason:
This message appears after the utility completed processing for a SEARCH ELEMENTS
statement. The message displays the number of elements searched and updated, as
well as the number of errors encountered during processing.
Action:
None.
ENBS Messages
ENBS004I
SEARCH ELEMENT COMPONENT LIST searched nnnn COMPONENT LIST(s),updated
nnnn, and had nnnn error(s)'
Reason:
This message appears after the utility completed processing for a SEARCH ELEMENT
COMPONENT LIST statement. The message displays the number of element component
lists searched and updated, as well as the number of errors encountered during
processing.
Action:
None.
ENBS005I
Component list elementname
Reason:
Informational.
Action:
None.
ENBS006E
Cannot continue processing due to severity of previous errors
Reason:
A previous error occurred that was severe enough to warrant termination of further
processing. An example of such an error is a corrupt Master Control File (MCF) index.
Further activity against the MCF may produce erroneous results or possible loss of data.
Action:
Examine the listing for previous error messages to determine the exact cause of this
condition.
ENBS Messages
ENBS009I
A replacement string was truncated - insufficient space to insert a replacement string
Reason:
A search string was identified, but due to insufficient space in the line, it could not be
replaced with the entire replacement string. This message appears after the messages
that display a portion of the line in error.
Action:
Either check the boundary columns to make sure that they are not restrictive, or check
that the length of the replacement string is not excessive. Modify the search string or
the replacement string, or both, if necessary.
ENBS010W
Element will not be updated - no net change
Reason:
The element was searched and the replacement strings were applied, but no net
changes were produced. The altered image of the element is identical to the image
searched.
Action:
Check whether the search and replacement strings contain redundant requests. For
example, the first request changes the letter A to the letter B. The second request
changes the letter B to the letter A. If the letter B did not exist in the original line, the
text after the second request would be the same as the original text; see below:
First Request:
+----1
Original text:
Search string:
Replacement string:
Updated text:
Second Request:
AACCCC
Az
B
BBCCCC
+----1
Original text:
Search string:
Replacement string:
Updated text:
BBCCCC
B
A
AACCCC
The updated text after the second replacement takes place is the same as the original
text before the first search took place. Therefore, there is no net change in the element.
If this is not acceptable, modify the search string or the replacement string, or both, if
necessary.
ENBS Messages
ENBS012W
*NO CHANGE* element-data-90
Reason:
Message ENBS012I is displayed when the SEARCH ELEMENTS statement contains both a
search string and a replacement string. This message lists the altered contents of the
text shown by message ENBS016I. The message indicates that a line was altered but the
before and after images of the line are identical. All non-printable characters are
displayed as periods.
Action:
The column ruler and element text appear when OPTIONS LIST DETAILS has been coded.
If you want to suppress listing details, do not code the OPTIONS LIST DETAILS clause in
the SEARCH ELEMENTS statement.
ENBS014W
No ELEMENT/COMPONENT LIST selected in ENV env, SYS sys, SBS sbs, TYPE typ
Reason:
No eligible elements were found for one of the following reasons:
No elements matched the search criteria.
Elements were found that matched the search criteria but were not eligible for
further processing due to additional qualifying criteria. For example, the WHERE
CCID clause was specified, but none of the elements contained matching CCID
information.
Element does not have a component list.
This statement cannot be processed any further.

Action:
Increase the scope of the search or specify other qualifying information.
ENBS Messages
ENBS015I
COL nnnnn +----t1----+----t2----+----t3----+--...
Reason:
This message displays a column ruler for the element text that follows in subsequent
messages. The column offset, nnnn, will be a multiple of 10 and every tenth character
thereafter represents the next highest multiple of ten. For example, if nnnn=0, t1=1,
t2=2, t3=3, . . ., t9=9.
Action:
The column ruler and text appear when OPTIONS LIST DETAIL has been coded. If you
want to suppress listing details, do not code the OPTIONS LIST DETAILS clause in the
SEARCH ELEMENTS statement.
ENBS016I
LINE nnnnn element-data-90
Reason:
Either all or a portion of the element data is displayed. Examine the preceding ENBS015I
message to determine the offset of the first byte of data that is displayed. Up to 90
bytes of data may be shown with non-printable characters being displayed as a period.
This message is used to display the original, unmodified, element data at line number
nnnnn within the element being processed.
Note: Only 90 bytes of the record are displayed at or near the offset of the first search
string found in the record. If the record length is larger than 90 bytes, other occurrences
of the search string may be found but are not shown.
Action:
The column ruler and element text are displayed when you are using OPTIONS LIST
DETAILS and a search string has been located. If you want to suppress listing details, do
not code the OPTIONS LIST DETAILS clause in the SEARCH ELEMENTS statement.
ENBS Messages
ENBS017I
*UPDT* element-data-90
Reason:
Message ENBS017I is displayed when the SEARCH ELEMENTS statement contains both a
search string and a replacement string. This message lists the altered contents of the
text shown by message ENBS016I, and shows all or part of the record that will be
written to the entry stage for the element being processed. All non-printable characters
are displayed as periods.
Action:
The column ruler and element text appear when OPTIONS LIST DETAILS has been coded.
If you want to suppress listing details, do not code the OPTIONS LIST DETAILS clause in
ENBS018C
*TRUNC* *UPDT* element-data-90
Reason:
Message ENBS018C is displayed when the SEARCH ELEMENTS statement contains both a
search string and a replacement string, and the following conditions exist:
The replacement string is larger than the search string.
The original line of data does not have sufficient space to accommodate the
replacement string, causing some of the original data to be truncated.
This message lists the altered contents of the text shown by message ENBS016I, and
shows all or part of the record that will be written to the entry stage for the element
being processed. Note that a portion of the original data is lost when the
replacement-string is inserted into the record. All non-printable characters are displayed
as periods.
Action:
The column ruler and subsequent element text is displayed when OPTIONS LIST DETAILS
has been coded. If you want to suppress listing details, do not code the OPTIONS LIST
DETAILS clause in the SEARCH ELEMENTS statement.
If you want to prevent data truncation and possible loss of element data, do not code
the OPTIONS DATA TRUNCATION IS PERMITTED clause in the SEARCH ELEMENTS
statement. Data truncation is prohibited by default.
ENBS Messages
ENBS019E
*ERROR* *UPDT* element-data-90
Reason:
Message ENBS019E displays when the SEARCH ELEMENTS statement contains both a
search string and a replacement string, and the following conditions exist:
The replacement string is larger than the search string.
The original line of data does not have sufficient space to accommodate the
replacement string, causing some of the original data to be truncated.
This message lists the altered contents of the text shown by message ENBS016I, and
shows all or part of the record that will be written to the entry stage for the element
being processed. Note that one of two situations cause this message to appear:
Some of the original data would be lost when the replacement-string is inserted
into the record.
A search-string was located but there is insufficient room to insert the

corresponding replacement-string.
All non-printable characters display as periods. Message ENBS019E may also be issued
when a search string is found at the end of the modifiable columns (as determined by
the IN COLUMNS and BOUNDS ARE clauses) but the replacement string cannot be
inserted without being truncated. The column ruler and subsequent element text
display when OPTIONS LIST DETAILS has been coded. To suppress listing details, do not
code the OPTIONS LIST DETAILS clause in the SEARCH ELEMENTS statement.
If you want to enable data truncation, and possible loss of element data, code the
OPTIONS DATA TRUNCATION IS PERMITTED clause in the SEARCH ELEMENTS statement.
ENBS020E
I/O error writing to DDNAME ddname - Return Code = nnnn
Reason:
An I/O error was encountered when trying to write to the file indicated in the message
(DDname). The return code nnnn was received by the routine issuing the write request.
Either the machine is out of disk space or a medium error has been encountered.
Action:
Check the output for other messages that may indicate the nature of the I/O error and
take corrective action. Consider increasing the amount of space allocated to the file
associated with the DDname. Also consider moving the file to another location (for
example, to another physical device).
ENBS Messages
ENBS021I
nnnnn ELEMENTS/COMPONENT LISTS will be processed
Reason:
Indicates the number of elements (component lists) eligible for processing. This value
represents the number of elements (component lists) that satisfy the search
qualifications specified on the Search Element statement or the Search Element
Component List statement. Each element (component list) is searched for possible
occurrences of the search strings specified in the request, if Search Element is being
executed. If Search Element Component List is being executed, each element with
associated component data is examined for the output data set name specified in the
request.
Action:
None.
ENBS022C
nnnnn ELEMENTS/COMPONENT LISTS were not processed
Reason:
Message ENBS022C indicates the number of elements (component lists) that were
eligible for processing. These elements satisfied the search criteria on the SEARCH
ELEMENT statement, but were not processed due to a previous error that caused the
search operation to terminate.
Action:
Check the output to find the error that caused processing to stop. Take corrective
action, as necessary. You should consider, however, the effect that rerunning the search
operation may have on the elements that were successfully processed before the error
occurred.
ENBS023I
Found at location env/stg-id/sys/sbs/typ
Reason:
The element specified in message C1G0000I was found at the location indicated and will
be searched.
Action:
None.
ENBS Messages
ENBS024I
ELEMENTS/COMPONENT LISTS searched, nnnn text matches found
//Note: element-name is not present in this message.
Reason:
The SEARCH ELEMENT (SEARCH ELEMENT COMPONENT LIST) statement specified one or
more search strings, but no replacement strings. This message indicates the number of
occurrences of the search string found within the search columns of the element
(component list) specified.
Action:
None.
ENBS025I
ELEMENT/COMPONENT LIST searched, nnnn text matches found, nnnn-2 will be
replaced
Reason:
The SEARCH ELEMENTS (SEARCH ELEMENT COMPONENT LIST) statement specified one
or more search strings and at least one replacement string. This message indicates the
number of occurrences of the search string found within the search columns of the
element (component list) specified and the number of substitutions that were made.
Action:
None.
ENBS027I
ELEMENT/COMPONENT LIST could not be updated due to previous errors
Reason:
The element (component list) specified cannot be updated because of errors that
occurred during the search phase of processing.
Action:
Check the output for a prior error message. Take corrective action, as necessary.
ENBS Messages
ENBS028I
ELEMENT/COMPONENT LIST could not be updated. Replace operation failed on line
nnnn
Reason:
An error occurred when attempting to replace the search string with its corresponding
replacement string. Therefore, the specified element (component list) cannot be
updated. The error occurred on the line number indicated. The error may have occurred
due to insufficient space in the record. Either of the following conditions could cause the
error:
Data truncation would have resulted if the replacement string had been inserted
into the record. Data truncation is prohibited, however.
The replacement string would have extended beyond the last modifiable column of
the line, as determined by the BOUNDS ARE parameters.
Action:
Check the output for a prior error message and take corrective action, as necessary. If
you decide that you want to permit data truncation, you need to consider the effects of
using that option on the element data.
ENBS029I
SEARCH ELEMENT/COMPONENT LIST processing is complete, Return Code = nnnn
Reason:
Processing for the SEARCH ELEMENT (SEARCH ELEMENT COMPONENT LIST) has
completed. The message indicates the highest return code encountered while
processing this statement.
Action:
None.
ENBS Messages
ENBS030I
Element will be added to location env/stg-id/sys/sbs/typ
Reason:
This message indicates where the element specified would be added back into CA
Endevor SCM. This message appears when you use replacement mode or when you
generate SEARCH ELEMENT SCL. If you are using replacement modethat is, OPTIONS
UPDATE ELEMENTS is coded in the SEARCH ELEMENT statementthe update operation
begins after this message is written.
Action:
None.
ENBS031E
Not authorized to RETRIEVE element at location env/stg-id/sys/sbs/typ/elm
Reason:
You do not have the authority to retrieve the element specified in the message from the
location shown.
Action:
ENBS032E
Not authorized to ADD element at location env/stg-id/sys/sbs/typ/elm
Reason:
You do not have the authority to add the element specified in the message into the
location shown.
Action:
ENBS Messages
ENBS033E
Not authorized to UPDATE element at location env/stg-id/sys/sbs/typ/elm
Reason:
You do not have the authority to update the element specified in the message at the
location shown.
Action:
ENBS034E
Not authorized to GENERATE element at location env/stg-id/sys/sbs/typ/elm
Reason:
You do not have the authority to generate the element specified in the message at the
location shown.
Action:
ENBS035S
Internal error. Invalid parameter passed to module.function
Reason:
The calling module is not passing the information expected by the called module. The
function in the module received control but the calling routine did not provide the
proper calling parameters. The called module (specified in this message) may be
associated with a different release of the product than the calling-module.
Action:
ENBS Messages
ENBS036I
1 ELEMENTS were skipped. Long names, mixed and special cased characters are not
supported.
Reason:
Informational message. The Search and Replace utility is skipping the current element
because the element name contains mixed or special case characters, or it is a long
name, or both.
Action:
None.
ENBS037I
DSNAME data set name.
Reason:
The data set name displayed is that specified in the For Output Dsname clause of the
Search Element Component List statement. The data set name has been found in an
output component record for the element. This message is used to display the original,
unmodified, output data set component item.
Action:
The column ruler and output data set name are displayed when you specify the Options
List Details clause and the output data set name has been located in the output
component data. If you want to suppress listing details, do not code Options List Details
in the Search Element Component List statement.
ENBS038E
Record number nnnn was not stored successfully
Reason:
The record number could not be stored either in memory or on the ENSSPILL file. This
message appears when all available memory is exhausted and one of the following
conditions occurs
The ENSSPILL file is not allocated.
The ENSSPILL file cannot hold the record indicated.
Processing for this element is terminated. The next element may be processed if enough
storage can be released to the operating system.
Action:
Consider increasing the region size or the size of the ENSSPILL file.
ENBS Messages
ENBS039E
Unable to read record number nnnn from the ENSSPILL file
Reason:
The record indicated in the message was previously written to the ENSSPILL file, but
cannot be read from the file. This situation is due to one of the following reasons:
Possible damage to ENSSPILL.
The previous write operation was not completely successful.
Action:
Consider increasing the region size or the size of the ENSSPILL file. Check the output for
any other messages that may indicate why the record could not be obtained.
ENBS040E
MOVE authority needed to update component list at location
env/stg-id/sys/sbs/typ/elm
Reason:
You do not have the authority to update the element specified in the message at the
location shown.
Action:
ENBS041E
ELEMENT is signed-out to another user
Reason:
The element specified in the message is signed out to another user and one of the
following conditions is true:
You did not code the OPTIONS OVERRIDE SIGNOUT in the SEARCH ELEMENTS
request.
You do not have the authority to override the signout.
Therefore, processing cannot continue for this element.

Action:
Try the operation again when the element is no longer signed out. Consider using the
OPTIONS OVERRIDE SIGNOUT parameter if you have the proper level of authority.
ENBS Messages
ENBS042E
Not authorized to override sign-out processing for env/stg-id/sys/sbs/typ/elm
Reason:
The element specified in the message is signed out to another user and you do not have
the proper authority to override the signout.
Action:
Try the operation again when the element is no longer signed out.
ENBS043E
No statements to process
Reason:
The ENSSCLIN file does not contain any SEARCH ELEMENTS statements.
Action:
Specify a valid SEARCH ELEMENTS statement in the ENSSCLIN file.
ENBS044S
Internal Error. Unexpected parameter "xx" passed to module.function
Reason:
An unexpected parameter was received by function specified in module specified. This is
an internal error.
Action:
The function returns to the calling module with a severe return code (RC=16).
Otherwise, processing of the request is ignored.
ENBS045I
Beginning update phase for the elementname
Reason:
Update processing has begun for the element specified at the location shown in the
message. Update processing adds or updates the element at the entry stage of the
environment, and executes the generate processor if applicable.
Action:
None.
ENBS Messages
ENBS046E
OPTIONS CCID is required for elements in Environment env System sys
Reason:
A CCID is required in order to update elements in the environment and system specified.
The SEARCH ELEMENTS statement does not contain a CCID, however.
Action:
Specify a CCID on the SEARCH ELEMENTS statement by coding the OPTIONS CCID clause.
Check the system record to see if comments are also required for the update operation.
ENBS047E
OPTIONS COMMENT is required for elements in Environment env System sys
Reason:
A comment is required in order to update elements in the environment and system
specified. The SEARCH ELEMENTS statement does not contain a comment, however.
Action:
Specify a comment on the SEARCH ELEMENTS statement by coding the OPTIONS
COMMENT clause. Check the system record to see if CCIDs are also required for the
update operation.
ENBS Messages
ENBS048E
Column values outside the compare-column range for type typ in env/stg-id/sys
Reason:
The column values specified on the SEARCH ELEMENTS statement are outside the range
of columns permitted for all elements of the type specified, in all subsystems, in the
environment, stage, and system indicated. The column values in error are coded in
either the IN COLUMNS clause or the BOUNDS ARE clause.
For example, COBOL programs are stored with a type restricting compare columns to
column 7 through column 72. The error message appears if the SEARCH ELEMENTS
statement refers to a column outside this range. Either of the following clauses would
invoke this message:
SEARCH . . .FOR TEXT value IN COLUMN 1 to 72
SEARCH . . .FOR TEXT value IN COLUMN 7 to 8_
Action:
Modify the appropriate column information in the SEARCH ELEMENTS statement, to
provide a value that lies within the element type's compare columns. You can specify
FIRST or LAST, or both, to dynamically select the first or last column of the types
compare column range.
ENBS049E
ESTAE exit invoked. Terminating processing
Reason:
An error that cannot be corrected occurred and caused the program's error recovery
exit to be invoked. Termination processing is immediately invoked. The program may try
to print the Summary Report before terminating unless the ESTAE exit was previously
invoked.
This situation is caused by any condition that might result in an abnormal end (ABEND)
state, such as a storage violation (usually caused by a corrupt or invalid pointer).
Action:
Determine the nature of the abnormal termination and consider trying the operation
again. If the problem persists or you are not certain about the effects of trying the
operation again, talk with your administrator.
ENBS Messages
ENBS050E
The ENSSCLIN DD statement is missing
Reason:
The ENSSCLIN DD statement was not allocated. The Search & Replace utility program
reads the SEARCH ELEMENTS SCL statements from the ENSSCLIN file.
Action:
Correct the JCL statements and try the operation again.
ENBS051I
Statement not processed - running in SCL validation mode
Reason:
The SEARCH ELEMENTS statement was successfully parsed but was not processed
because the VALIDATE parameter was specified on the PARM= statement in the
execution JCL.
Action:
If you do not want to run in validate mode, remove the VALIDATE parameter from the
PARM= statement in the execution JCL.
ENBS052E
Boundary or column values invalid for type typ in env/stg-id/sys
Reason:
The boundary columns are invalid for elements of the type indicated in the location
indicated in the message. This message appears if the from-column is greater than the
to- column (in the IN COLUMNS clause) or the left-column is greater than the
right-column (in the BOUNDS ARE clause). Message ENBS907E or message ENBS908E, or
both, may follow this message. These messages specify the column values that were
coded in the SEARCH ELEMENTS statement or derived from the element type compare
columns.
Action:
Review the SEARCH ELEMENTS statement and the values displayed in the subsequent
ENBS907E and ENBS908E messages. Take corrective action as necessary.
ENBS Messages
ENBS053E
Cannot process element; found at location: env/stg-id/sys/sbs/typ/elm
Reason:
The element indicated in the message was found in the location specified, but this
location is an "in-between" stage. That is, the stage (location) is not on the environment
map. For example, consider the following environment map:
ENV1.STAGE1ENV1.STAGE2ENV2.STAGE2
The first occurrence of the element in the map is found at ENV2.STAGE2. The utility then
checks whether the element exists anywhere else between Stage 1 of the base
environment (ENV1.STAGE1) and the location in which the element was found, and
finds an occurrence of the element at ENV2.STAGE1which is not on the map. The
element cannot be processed because ENV2.STAGE1 is an in-between stage of the
environment map.
Action:
Move or delete the element from the in-between stage and try the operation again.
ENBS054S
Cannot process element due to invalid record length
Reason:
A record with an invalid record length was read for the element specified in the
message, at the location specified. Record lengths must be within the range of 1 to
32000, inclusive. This situation may indicate an internal error.
Action:
Check for other error messages that may indicate a problem with your system. Contact
your administrator.
ENBS Messages
ENBS055E
Invalid attributes for the ENSSCLOT data set
Reason:
The ENSSCLOT DD statement is present but the data set allocated to that DD statement
does not have the proper attributes. Either the wrong data set was allocated or the
attributes of the data set were other than those required.
Message ENBS056I, which immediately follows this message, provides the correct
attributes for the data set.
Action:
Make sure that the data set allocated to the ENSSCLOT DD statement is not a NULLFILE
data set. Also, ensure that the attributes of the data set allocated to ENSSCLOT
correspond to those described in message ENBS056I.
ENBS056I
ENSSCLOT requires: DSORG=PS,RECFM=F.FB,LRECL=80
Reason:
This message immediately follows message ENBS055E and describes the attributes
permitted for the data sets allocated to the ENSSCLOT DD statement:
The data set must be sequential or a member of a partitioned data set.
The record format can be either fixed (F) or fixed blocked (FB)
The logical record length must be 80.
If RECFM=F, the blocksize must be 80; otherwise the blocksize can be a multiple of
80.
Action:
Make sure that the data set allocated to ENSSCLOT has the appropriate attributes:
DSORG=PS, RECFM=F.FB, and LRECL=80.
ENBS Messages
ENBS057E
Invalid attributes for the ENSSPILL data set
Reason:
The ENSSPILL DD statement was present and the data set allocated to that DD
statement does not have the proper attributes. Either the wrong data set was allocated
or the attributes of the data set were other than those required.
Message ENBS058I, which immediately follows this message, provides the correct
attributes for the data set.
Action:
Make sure that the data set allocated to the ENSSPILL DD statement is not a NULLFILE
data set. Also, make sure that the attributes of the data set allocated to ENSSPILL
correspond to those described in message ENBS058I.
ENBS058I
ENSSPILL requires: DSORG=PS,RECFM=V.VB,LRECL=32004
Reason:
This message describes the attributes permitted for the data sets allocated to the
ENSSPILL DD statement. The data set must be sequential with a logical record length not
less than 32004 for variable length (RECFM=V) data sets or variable length blocked
(RECVM=FB) data sets. For RECFM=VB data sets, the block size must be 4 bytes larger
than the record length.
This message immediately follows message ENBS057E and describes the attributes
permitted for the data sets allocated to the ENSSPILL DD statement:
The data set must be sequential.
The record format can be either variable length (V) or variable length blocked (VB).
The logical record length must be not less than 32004.
If RECFM=VB, the blocksize must be 4 bytes larger then the record length.
Action:
Be sure the data set allocated to ENSSPILL has the appropriate attributes: DSORG=PS,
RECFM=V.VB, and LRECL=32004.
ENBS Messages
ENBS059S
Unexpected End-Of-File on ENSSPILL file
Reason:
The logical end-of-file on the ENSSPILL was reached prematurely. This may indicate a
possible loss of data. This situation may be caused by an I/O error on the ENSSPILL file.
Action:
Determine if there was any loss of data for the element being processed. Take
corrective action as necessary.
ENBS060E
Unable to ENQ on resource env/*/sys/sbs/typ/elm, Return Code = nnnn
Reason:
When running in replacement mode, the Search & Replace program attempts to gain
exclusive use of an element at both the source and entry stages. The ENQ request for
the element specified, in the location indicated, failed. The return code returned by the
ENQ/DEQ processor is shown.
This situation may occur if the element is being used by another user for an update
operation.
Action:
Try the operation again at a later time.
ENBS061E
Unable to DEQ from resource env/*/sys/sbs/typ/elm, Return Code = nnnn
Reason:
After processing an element, the Search & Replace program releases exclusive use of
the resources via a DEQ request. The DEQ request for the element specified, in the
location indicated, failed. The return code returned by the ENQ/DEQ processor is
shown. If the resource is not released, other jobs or users may be unable to update the
element until the present job or user session is terminated.
This situation most likely occurs if there is an internal error.
Action:
The operating system automatically releases the resource when the current job or user
session is terminated. Contact your administrator if this problem continues.
ENBS Messages
ENBS062E
Processor group (group-name) not found
Reason:
The process group specified in the message was not found. Element processing is
terminated.
Action:
Check whether the processor group name exists at the Stage 1 of the base environment.
If it does not, specify another processor group name or create a processor for the name
indicated.
ENBS063E
Cannot invoke processor group (group-name) - Return Code = nnnn, Reason Code =
nnnn
Reason:
The process group name specified in the message cannot be invoked. The return code
and reason code is shown in the message.
Action:
None.
ENBS064I
Update phase for this ELEMENT/COMPONENT LIST is complete, RC=@8CY
Reason:
The update processing for the element specified in the message has completed. The
highest return code detected during the update processing for this element is also
Action:
None.
ENBS Messages
ENBS065E
Bounds values outside the compare-column range for type typ in env/stg-id/sys
Reason:
The BOUNDS ARE values specified for the SEARCH ELEMENTS statement are outside the
compare column range defined for the type shown in the message.
Action:
Correct the BOUNDS ARE clause and try the operation again.
ENBS066W
Search string was not found in any of the elements (component lists) that were
searched
Reason:
The search string cannot be found in any elements (component lists), in the columns
specified (or derived from the element type compare columns). Either the elements
(component lists) do not contain the string at all or elements contain the string in other
than the columns specified. This warning message is issued to draw attention to this
condition; it does not necessarily indicate a problem.
Action:
None.
ENBS067E
Element location has changed - found at env/stg-id/sys/sbs/typ/elm
Reason:
The element has been moved or updated, to the location indicated in the message,
since the Search & Replace utility identified it as a possible candidate for processing. The
element will not be processed.
Action:
None.
ENBS Messages
ENBS068E
Search string length exceeds length of search area
Reason:
The length of the search string is larger than the size of the search area.
Action:
Check whether the IN COLUMNS and BOUNDS ARE parameters are too restrictive. Then,
either increase the size of the search area or decrease the length of the search string.
ENBS069E
Replacement string length exceeds length of modifiable area
Reason:
The size of the replacement string is larger than the size of the area that can be
modified (modifiable range) for the element being processed. The replacement string
may be too large or the BOUNDS ARE right-column (or IN COLUMNS to-column) may be
too restrictive.
Action:
Correct the appropriate clause in the SEARCH ELEMENTS statement and try the
operation again.
ENBS070E
Stage [number or id] [stage-number or stage-id] does not exist.
Reason:
The stage number or stage ID specified in the Search Element Component List statement
does not exist. This error condition is not recognized during SCL syntax checking. It
appears when the utility attempts to search for the output data set name in the output
component information.
Action:
Change the Search Element Component List statement to specify a valid and explicit
stage number or stage ID for the location at which you want to execute the action.
Correct the appropriate clause in the SEARCH ELEMENT statement and try the operation
again.
ENBS Messages
ENBS071C
Sourceless element TSTAMP differs from sourced at
Environment/Stage/System/Subsystem/Type
Reason:
A sourceless element was selected for processing and its last level timestamp is
different from the next sourced element found up the map.
Action:
Re-generate or delete the sourceless element then perform the Search and Replace
action.
ENBS072E
Sourced element not found for sourceless element at
Reason:
The corresponding source for the selected sourceless element was not found up the
map from the sourceless element.
Action:
Try to determine the cause for the missing source. If the sourceless element is no longer
needed, delete it.
ENBS073E
Sourced element location has changed - not at
Reason:
The source location for the selected sourceless element has changed between the
element selection process and the source retrieval process.
Action:
Retry the Search and Replace action.
ENBS Messages
ENBS074I
ELEMENT element-name
Reason:
Informational. Identifies the element name.
Action:
None.
ENBS900I
Correct the appropriate clause in the SEARCH ELEMENTS statement and try the
operation again.
ENBS900I Control statement parsing is beginning
Reason:
Records from the ENSSCLIN file are being read, interpreted and validated.
Action:
None.
ENBS901I
Statement Number nnnn
Reason:
The text of statement nnn, as it was read by the parser, appears below this message.
This text appears in the same format as it appeared in the ENSSCLIN file.
Action:
None.
ENBS902I
Reason:
The utility has successfully parsed all the control statements.
Action:
None.
ENBS Messages
ENBS903E
Reason:
The utility detected one or more errors in the control statements during the parsing
process. This condition prevents further processing of the statements.
Action:
Correct the errors and try again.
ENBS904E
SCL statement contains errors
Reason:
The utility detected one or more errors in the SCL statement just parsed. The utility
continues parsing the next SCL statements, if any.
Action:
Correct the errors and try again.
ENBS905E
The FOR TEXT search string is either missing or empty
Reason:
The SEARCH ELEMENTS statement contains an invalid FOR TEXT clause. The search
string was either omitted from the clause or was null (that is, " "). The FOR TEXT clause
must contain a search string of one or more bytes in length.
Action:
Specify a search string of one or more bytes in the FOR TEXT clause.
ENBS Messages
ENBS906E
The FOR TEXT and REPLACE WITH TEXT strings are identical - statement bypassed
Reason:
The SEARCH ELEMENTS statement contains a FOR TEXT clause with identical search and
replacement strings. This is explicitly prohibited for performance reasons.
Action:
If you do not intend to replace the search string, do not specify a replacement string. If
you want to replace the search string with another value, specify that value and make
sure that it is not the same as the search string value.
ENBS907E
Invalid BOUNDS column values (left, right) specified
Reason:
The boundary columns, as specified by the BOUNDS operand of the FOR TEXT
parameter, are invalid. Either the left-column boundary is greater than the right-column
boundary, or the use of the FIRST and LAST qualifiers is improper.
Action:
Check that the left-column boundary specified is not greater than the right- column
boundary specified. If you use the FIRST and LAST parameters, avoid coding clauses such
as the following:
BOUNDS ARE LAST TO FIRST
BOUNDS ARE LAST to 2_
BOUNDS ARE 2_ TO FIRST
ENBS Messages
ENBS908E
Invalid IN COLUMNS column values (from, to) specified
Reason:
The boundary columns, as specified by the IN COLUMNS operand of the FOR TEXT
parameter, are invalid. Either the from-column is greater than the to-column or the use
of the FIRST and LAST qualifiers is improper.
Action:
Check that the from-column is not greater than the to-column parameter. If you use the
FIRST and LAST parameters, avoid coding clauses such as the following:
IN COLUMNS LAST TO FIRST
IN COLUMNS LAST to 2_
IN COLUMNS 2_ TO FIRST
ENBS909E
A search/replace clause was not specified. Specify a "FOR TEXT" clause with this
statement
Reason:
The SEARCH ELEMENTS statement did not contain a FOR TEXT clause.
Action:
You must code at least one FOR TEXT clause on the SEARCH ELEMENTS statement.
ENBS913E
Missing element name(s)
Reason:
The SEARCH ELEMENTS statement did not specify which elements are to be searched.
Action:
Specify an element name, a wildcarded element name, or a range of element names on
ENBS Messages
ENBS914E
Element sequence is invalid. Specify element element-2 before element element-1
Reason:
The SEARCH ELEMENTS statement specified a range of elements in the wrong order.
Action:
Either specify the elements in the order shown in this message or change the element
names as necessary to make sure that the second element is greater than the first.
ENBS915E
Environment name was not specified
Reason:
The FROM ENVIRONMENT clause is required but was not specified.
Action:
Specify the environment from which the search is to originate. Be sure to enter an
explicit environment name.
ENBS916E
The environment name must not contain a wildcard character
Reason:
The FROM ENVIRONMENT clause was specified but contained a wildcard character.
Action:
You must specify an explicit environment name. You cannot use a wildcard with this
value.
ENBS917E
System name was not specified
Reason:
The FROM SYSTEM clause is required but was not specified.
Action:
Specify the system from which the search is to originate. You can enter an explicit
system name or use a wildcard.
ENBS Messages
ENBS918E
Subsystem name was not specified
Reason:
The FROM SUBSYSTEM clause is required but was not specified.
Action:
Specify the subsystem from which the search is to originate. You can enter an explicit
subsystem name or use a wildcard.
ENBS919E
Type name was not specified
Reason:
The FROM TYPE clause is required but was not specified.
Action:
Specify the type associated with the elements to be searched. You can enter an explicit
type or use a wildcard.
ENBS920E
From column number not in range 1 >= n >= 32000
Reason:
The FOR TEXT IN COLUMNS parameter specified a column value that was not in the
range of 1 to 32000 inclusive, which is the valid range for this parameter.
Action:
Specify a column number in the range of 1 to 32000 inclusive. Or, if appropriate, specify
FIRST or LAST.
ENBS Messages
ENBS921E
To column number not in range 1 >= n >= 32000
Reason:
The FOR TEXT IN COLUMNS parameter specified a column value that was not in the
Action:
FIRST or LAST.
ENBS922E
Left boundary number not in range 1 >= n >= 32000
Reason:
The FOR TEXT BOUNDS ARE parameter specified a column value that was not in the
Action:
FIRST or LAST.
ENBS923E
Right boundary number not in range 1 >= n >= 32000
Reason:
The FOR TEXT BOUNDS ARE parameter specified a column value that was not in the
Action:
FIRST or LAST.
ENBS Messages
ENBS930E
The REPLACE WITH DSName dsname is not cataloged.
Reason:
The data set name specified as the replacement data set name in the Search Element
Component List statement is not a cataloged data set.
Action:
Specify the name of a cataloged data set that is a valid name and an existing data set in
the Replace With Output Dsname clause in the Search Element Component List
statement.
ENBS931E
DSName exceeds 44 characters - dsname
Reason:
An invalid data set name was specified in Search Element Component List statement.
The data set name specified exceeds 44 characters in length.
Action:
Ensure that the data set name is a valid name and is an existing data set.
ENBS932E
A stage number or stage id must be specified.
Reason:
The Search Element Component List statement did not contain a stage number or stage
ID value. This value is required.
Action:
Specify an explicit stage number or stage ID for the location at which you want to
execute the Search and Replace utility.
ENBS Messages
ENBS933E
A stage number or stage id cannot be wildcarded.
Reason:
The Search Element Component List statement contained a wildcarded value for stage
number or stage ID. Only explicit stage number and stage ID values are valid.
Action:
Specify an explicit stage number or stage ID for the location at which you want to
execute the Search and Replace utility.
ENBS934E
Wild cards are not allowed in DSName dsname.
Reason:
The Search Component List statement contained a wildcarded value for the DSName
value specified in either the For Output Dsname or the Replace With Output Dsname
clause. These data set names cannot contain wild card characters.
Action:
Specify the fully qualified name of an existing data set in the SCL.
ENBS999I
EOF control statement generated
Reason:
The EOF control statement was automatically generated when the parser reached the
logical end- of-file on the ENSSCLIN file. Or, the control statements in the ENSCCLIN file
were not terminated by the EOF control statement.
Action:
Code an EOF control statement at the end of the ENSSCLIN file if you want to avoid
generating this message; otherwise, no further action is required.
ENBX Messages
ENBX Messages
This section describes the messages generated in the course of Expand Includes Utility
ENBX001I
Statement Number statement number
Reason:
Batch expand include syntax.
Action:
None.
ENBX002I
Processing is complete. Highest return code is return code
Reason:
This message indicates the termination of the utility.
Action:
None.
ENBX003E
An invalid JCL parameter was provided. The JCL parameter follows.
Reason:
An invalid execution parameter was specified. The parameter in error printed out after
this message.
Action:
Correct the error and resubmit.
ENBX Messages
ENBX004E
parameter date
Reason:
See message ENBX003E.
Action:
Correct the error and resubmit.
ENBX005I
The ENXSCLIN DD statement is present. The JCL member parameter will be ignored.
Reason:
The member name specification via ENXSCLIN overrides the JCL member name
execution parameter specification.
Action:
None.
ENBX006E
The ENXSCLIN DD statement was not provided or a JCL parameter was not provided.
Reason:
A member name must be specified either via ENXSCLIN syntax or via the JCL execution
parameter.
Action:
Specify the member name and resubmit.
ENBX007E
Initialization failed. Processing will terminate immediately.
Reason:
An initialization error occurred.
Action:
ENBX Messages
ENBX008E
Control statement validation failed. Processing will terminate immediately.
Reason:
A processing error occurred during syntax validation.
Action:
ENBX009E
The C1DEFLTS table does not indicate that either Panvalet or Librarian are installed.
Reason:
Neither CA Panvalet nor CA Librarian include statement syntax was specified in the
C1DEFLTS table.
Action:
Update the C1DEFLTS with the appropriate specification.
ENBX010E
There are no ENXINCnn DD statements allocated
Reason:
There are no DD statements beginning with ENXINCnn found allocated to include
libraries.
Action:
Correct the JCL and resubmit.
ENBX011E
The include data set, dsname/member, has invalid attributes
Reason:
The library identified in the message does not have DCB information consistent for
include members.
Action:
Verify that the data set name identified is correct.
ENBX Messages
ENBX020E
Data set data set is not cataloged
Reason:
The data set name identified in the message cannot be found in the catalog.
Action:
Make sure that the data set name in the specification is correct.
ENBX021E
DDname ddname is not allocated
Reason:
The ddname specified in the message was found to be allocated.
Action:
Correct the JCL and resubmit.
ENBX022E
Data set data set has the incorrect attributes for an include data set
Reason:
ENBX023C
The destination data set record length LRECL is too small. Output records may be
truncated.
Reason:
The LRECL of the target data set is smaller than the source data set.
Action:
Check the LRECL specification to make sure it is correct.
ENBX Messages
ENBX024E
Allocation failed for data set dsname, S99ERROR=return code, 99INFO=reason code
Reason:
A dynamic allocation error occurred for the named data set. See IBM Publication
Application Development Guide Authorized Assembler Language Programs for a
definition of the return and reason codes.
Action:
Refer to the action.
ENBX025E
The source/destination data set, dsname, has invalid data set attributes
Reason:
The source/destination data set, dsname, has invalid data set attributes.
Action:
Verify that you have specified the correct source and destination data sets.
ENBX026E
The ENXIN DD statement does not contain a member name, nor does the JCL
parameter. No member selected.
Reason:
The data set pointed to by the ENXIN DD statement is a library but no member names
were specified.
Action:
Specify a member name and resubmit.
ENBX027E
Validation failed for DD ddname, data set dsname
Reason:
Validation failed for DD ddname, data set dsname.
Action:
Verify that the specified dsname is correct.
ENBX Messages
ENBX028E
Data set dsname has invalid attributes for a source/destination data set
Reason:
Action:
Verify that you have specified the correct source and destination data sets.
ENBX029E
Member member was not found in data set dsname
Reason:
The specified member name is not found in the specified library name.
Action:
Correct the member name and resubmit.
ENBX030I
Member member has been selected. nn include members totaling nnn lines were
expanded
Reason:
The indicated member has been selected and expanded.
Action:
None.
ENBX031I
Input data set is data set
Reason:
This message indicates the name of the input data set.
Action:
None.
ENBX Messages
ENBX032I
Output data set is data set
Reason:
This message indicates the name of the output data set.
Action:
None.
ENBX033I
nn members were successfully expanded. nn members had an error.
Reason:
This message indicates the number of members that were successfully expanded and
the number of members that had an error.
Action:
None.
ENBX034E
Member member already exists in data set data set
Reason:
The indicated member already exists in the named data set.
Action:
Check the specification of the member and resubmit.
ENBX034W
Member member already exists in data set data set
Reason:
The indicated member already exists in the named data set.
Action:
Check the specification of the member and resubmit.
ENBX Messages
ENBX035I
EXPAND INCLUDE processing is complete. Return code nn
Reason:
EXPAND INCLUDE processing completed with the indicated return code.
Action:
None.
ENBX036I
Sequential input has been processed. nn include members totaling member lines were
expanded
Reason:
This message indicates that sequential input has been processed resulting in the
number of include members with the number of lines expanded.
Action:
None.
ENBX037E
The destination data set must include an output member name
Reason:
This message indicates that the destination data set does not include an output member
name.
Action:
Specify an output member name and resubmit.
ENBX038E
No matches were found for member in data set data set
Reason:
This message indicates that no matches were found for the member in the data set
named.
Action:
Verify that the data set name is correct.
ENBX Messages
ENBX039E
Member member was not found in data set data set
Reason:
The indicated member was not found in the named data set.
Action:
Verify the member name and the data set name.
ENBX041E
A loop has been detected in include member member. Processing has been
terminated for the input file
Reason:
A circular reference where A includes B and B includes A has been caused by the include
member reference.
Action:
Correct the include members.
ENBX043C
Include member member could not be located
Reason:
The named include member could not be located.
Action:
Verify that the data set name's include libraries are correct.
ENBX044E
The source member name is required
Reason:
The source member name is missing.
Action:
Specify a source member.
ENBX Messages
ENBX045E
The size of internal table table has been exceeded
Reason:
The size of the named internal table has been exceeded.
Action:
Call CA Technical Support.
ENBX046E
Replace by expansion of a line has exceeded the internal workarea. Expansion
ignored.
Reason:
The expansion of a line has exceeded the internal workarea.
Action:
ENBX047E
Original value = text
Reason:
Action:
ENBX100S
An abend code ABEND occurred
Reason:
The named abend has occurred.
Action:
Correct the condition that caused the abend.
ENBX Messages
ENBX101S
A storage failure has occurred in module program in routine routine
Reason:
A storage failure has occurred in the named routine of the named module program.
Action:
ENBX900I
Reason:
This message indicates that control statement parsing has begun.
Action:
None.
ENBX901I
Reason:
This message indicates that control statement parsing has completed with no errors.
Action:
None.
ENBX902E
Reason:
This message indicates that control statement parsing has completed with errors.
Action:
Check the corresponding error messages.
ENBX Messages
ENBX903E
The FROM DDNAME or DSNAME clause is required
Reason:
This message indicates that the FROM DDNAME or DSNAME clause is missing.
Action:
Specify a FROM DDNAME or DSNAME clause.
ENBX904E
The TO DDNAME or DSNAME clause is required
Reason:
This message indicates that the TO DDNAME or DSNAME clause is missing.
Action:
Specify a TO DDNAME or DSNAME clause.
ENBX905E
An invalid DDNAME, ddname, was specified
Reason:
The named ddname is invalid.
Action:
Correct the ddname specification and resubmit.
ENBX906E
An invalid MEMBER name, member, was specified
Reason:
The named member is invalid.
Action:
Correct the member specification and resubmit.
ENBX Messages
ENBX907E
TO MEMBER invalid. Contains * or, FROM MEMBER is wildcarded
Reason:
Either the TO MEMBER contains an asterisk (*) or the FROM MEMBER is wildcarded.
Action:
Verify both the TO MEMBER and FROM MEMBER specifications.
ENBX908E
The FROM DSNAME clause and the FROM DDNAME clause are mutually exclusive
Reason:
The FROM DSNAME clause and the FROM DDNAME clause are mutually exclusive.
Action:
Check the FROM DSNAME and FROM DDNAME specifications.
ENBX909E
The TO DSNAME clause and the TO DDNAME clause are mutually exclusive
Reason:
The TO DSNAME and the TO DDNAME clause are mutually exclusive.
Action:
Check the TO DSNAME and TO DDNAME specifications.
ENCI Messages
ENCI Messages
This section details messages generated in the course of object oriented I/O service
ENCI900I
No error messages are outstanding
Reason:
The application issued a RETRIEVE_ERROR_TEXT request but there was no error
message associated with the I/O Object. This message is issued to indicate this fact.
Action:
ENCI901EI
An attempt was made to read past the end-of-file for data set data set name
Reason:
The application issued a READ_RECORD request after a previous READ_RECORD request
has reached the end-of-file. The application had not issued an intervening CLOSE_DATA
SET request. The I/O Object cannot read past the end-of-file.
Action:
The application does not contain the correct end-of-file processing logic. Contact the
application developer.
ENCI902E
Allocation failed for data set data set name. S99ERROR=s99error, S99INFO=s99info
Reason:
The dynamic allocation request for the data set specified failed. The dynamic allocation
service returned the error code and information code specified.
Action:
Refer to IBM manual GC28-1852 Systems Programming Library: Application
Development Guide (or the equivalent manual for your release of z/OS) for an
explanation of the S99INFO and S99ERROR codes. Take any corrective action possible
ENCI Messages
ENCI903E
An invalid data set type, value, was passed to the EDIT_DATA SET_ATTRIBUTES
function.
Reason:
The application made an EDIT_DATA SET_ATTRIBUTES request but passed an invalid
data set type code. The message contains the attribute code passed.
Action:
Contact the application developer to determine why an invalid data set type was passed
with the request.
ENCI904E
An unrecoverable error occurred during a READ request. The READ RESULT code is
value
Reason:
A READ_RECORD request failed for an I/O Object that is using the XP I/O services. The
XP $BQIO RESULT code is provided in the message text.
Action:
If the RESULT code is I/O ERR, refer to the system job log to determine if any system
related error messages were issued. If so, take the corrective action for those errors. For
any other RESULT code, contact the application developer.
ENCI905E
Unable to allocate storage for an I/O buffer. The $BGETSTG RESULT was value
Reason:
An internal storage request for an I/O buffer failed. The storage management service
return code is indicated in the message.
Action:
Increase the REGION= JCL parameter on the JOB or EXEC statement and resubmit the
job.
ENCI Messages
ENCI905E
An unrecoverable error occurred during a READ request. The READ RESULT code is
value
Reason:
A READ_RECORD request failed for an I/O Object that is using the XP I/O services. The
Action:
If the RESULT code is I/O ERR, refer to the system job log to determine if any system
ENCI907E
An unrecoverable error occurred during a WRITE request. The WRITE RESULT code is
value
Reason:
A WRITE_RECORD request failed for an I/O Object that is using the XP I/O services. The
Action:
If the RESULT code is I/O error, refer to the system job log to determine if any system
ENCI908E
An unrecoverable error occurred during a WRITE request. The ABEND Code is value
Reason:
A WRITE_RECORD request failed with the ABEND code identified.
Action:
If the ABEND code is SB37, SD37 or SE37, the output data set allocation is not large
enough. In these cases, reallocate the data set with a larger allocation. Any other ABEND
code indicates an application error.
ENCP9xx Messages
ENCP9xx Messages
This section describes the messages generated during parsing, along with possible
causes and actions to take in error situations.
ENCP901E
A literal or identifier was expected, found: x
Reason:
A parsing error occurred as noted in the message.
Action:
ENCP902E
A literal was expected, found: x
Reason:
Action:
ENCP903E
An identifier was expected, found: x
Reason:
Action:
ENCP904E
Invalid wording was encountered, found: x
Reason:
Action:
ENCP9xx Messages
ENCP905E
A keyword was expected, found: x
Reason:
Action:
ENCP906E
Command not recognized, found: x
Reason:
Action:
ENCP907E
The value specified is too long: x
Reason:
Action:
ENCP908E
An ending quote was not found for: x
Reason:
Action:
ENCP9xx Messages
ENCP909E
Expecting a number from 0 to 2,147,483,647, found: x
Reason:
Action:
ENCP910E
Storage was not available to parse: x
Reason:
Action:
Increase the size parameter and rerun.
ENCP911E
Expecting a number from 0 to 32,767, found: x
Reason:
Action:
ENCP912E
Expecting the end of a statement, found: x
Reason:
Action:
ENCP9xx Messages
ENCP913E
An invalid hexadecimal constant was specified, found: x
Reason:
Action:
ENCP914E
Expected a keyword or an end-of-statement, found: x
Reason:
Action:
ENCP915E
Expected a keyword or an end-of-statement, found: "end-of-file"
Reason:
Action:
ENCP916E
Expected an end-of-statement, found end-of-file
Reason:
Action:
ENCP9xx Messages
ENCP917E
Internal error: The CALL stack size was exceeded
Reason:
Action:
ENCP918E
Internal error: The CALL stack is empty. A RTRN is mismatched
Reason:
Action:
ENCP919E
Unbalanced expression: Too many parentheses were found
Reason:
Action:
ENCP920E
Internal error: An invalid syntax rule was found
Reason:
Action:
ENCP9xx Messages
ENCP921E
Internal error: The CALL stack not empty at the end of the statement
Reason:
Action:
ENCP922E
Internal error: A nested statement is not complete at the end of the statement
Reason:
Action:
ENCP923E
Internal error: An ALLOC rule did not precede a store operation
Reason:
Action:
ENCP924E
An I/O error occurred reading the input file
Reason:
Action:
Check for other error messages. Correct and resubmit.
ENCS Messages
ENCP925E
Internal error: The syntax tree is invalid. The end of the tree may have been reached
Reason:
Action:
ENCS Messages
This section lists error messages issued during security checking, along with possible
ENCS001S
XIT PARM HEADER DOES NOT MATCH PROGRAM XIT PARM HEADER pldata- expdata
Reason:
This message indicates that Security processing has terminated, and access to the
resource has been denied.
Action:
None.
ENCS002S
XPA PARM HEADER DOES NOT MATCH PROGRAM XPA PARM HEADER pldata-expdata
Reason:
This message indicates that Security processing has terminated and access to the
resource has been denied.
Action:
None.
ENCS Messages
ENCS010I
LOOK ASIDE TABLE ALLOCATED (beginaddr,endaddr):
Reason:
The security look aside table is allocated, beginning at storage address, beginaddr and
ending at storage address, endaddr. Processing continues.
Action:
None.
ENCS011W
LOOK ASIDE TABLE PAGE COUNT IS EXCESSIVE (length)
Reason:
The page count for the security lookaside table, specified in the C1DEFLTS, parameter
LATSIZE, exceeds the maximum value allowed (524287). The security look aside table is
disabled. Security processing continues without the look aside table.
Action:
Recode the LATSIZE parameter specifying a smaller value in the range 0-524287.
ENCS Messages
ENCS012W
LOOK ASIDE TABLE BYPASSED, SIZE(length), FLAG(code), DFLTADDR(address)
Reason:
The security look aside table (SLAT) is bypassed for one of the following reasons:
The program invoking ESI indicated not to use the SLAT.
You specified zero pages for the table.
The length of the table is given, along with the C1DEFLTS table address (dfltaddr). Code
identifies the flag within the C1DEFLTS table used by ESI to indicate the use of the look
aside table. This message is only issued when ESI is in debugging mode and (ddname
EN$DBESI) is allocated.
Action:
This is probably not an error. If you want to use the look aside table, do one of the
following:
If the length is zero, specify a nonzero value on the LATSIZE parameter in the name
equates table, and reassemble and link edit the table.
If the code is 0, it implies that CA Endevor SCM did not use the default tables. You
cannot change this.
If neither of the above is true, contact CA Endevor SCM support for assistance.
ENCS018C
INVALID NAME EQUATES TABLE ADDRESS, (address), ID(tablename)
Reason:
The address of the name equates table does not point to a valid table. Either the
address is zero or it does not point to a name equates table. The table name is the value
found in the name equates table.
This is an internal error. ESI SMF exception records are not written.
Action:
None.
ENCS Messages
ENCS030E
INVALID NAME EQUATE LOG OPTION, NUMBER
Reason:
The log option in the name equates table contained a value outside the allowable range.
ESI security is bypassed and access is denied.
Action:
Make sure that a valid name equate table is available to CA Endevor SCM. Correct the
log parameter and regenerate the name equates table. For more information about the
name equates log option, see the SCL Reference Guide.
ENCS031C
UNABLE TO WRITE WARNING MODE SMF RECORDS
Reason:
ESI could not create an ESI SMF exception record. This is possibly due to a storage
deficiency. Processing continues and one or more SMF records may be missing.
Action:
Increase the region size and retry the request.
ENCS039C
UNABLE TO LOCATE SIOT ENTRY FOR TRACE DATA SET
Reason:
The CA Endevor SCM External Security Interface could not locate a control block
necessary to determine the correct attributes of the trace DD EN$TRESI. This may occur
when EN$TRESI is allocated to DUMMY or the DA(*) in TSO/E. ESI may not write records
to the trace file when this message is issued.
Action:
Allocate the EN$TRESI DD to a data set or to SYSOUT file. The trace will proceed to be
written correctly.
ENCS Messages
ENCS045C
ERROR OCCURRED WRITING RECORD TO SMF, RC=code
Reason:
An attempt to write an SMF exception record failed with return code rtcd. This message
is displayed only when ESI is in warning mode. One or more SMF records are not written
and processing continues.
Action:
Action depends upon meaning of return code rtcd.
ENCS046C
SMF RECORD SYNTAX ERROR
Reason:
An error was detected in the format of the SMF exception record generated by ESI. This
is an internal error. This message is only displayed when in debugging mode. The SMF
record is not written and processing continues.
Action:
None.
ENCSI48S
NAME EQUATE TABLE table name SPECIFIED FOR USE WITH NATIVE SECURITY
Reason:
During initialization, security check processing detected that the security table name
table-name is valid for ESI, but the ESI security interface was not specified in the
C1DEFLTS table. (Native security is implied in this case.)
Action:
Enable ESI by specifying a correct password for ESSI=keyword of the C1DEFLTS
TYPE=MAIN macro, or specify the name of a security table that is configured to be used
with Native Security. Next, reassemble and relink the C1DEFLTS table and rerun CA
Endevor SCM.
ENCS Messages
ENCS050C
UNABLE TO PROTECT ESI LOOKASIDE TABLE STORAGE, RC=ndvrrtcd, PGRC=pgrtcd, LAT
disabled
Reason:
The PGSER macro request returned a non-zero return code to protect the look aside
table (LAT) storage. ndvrrtcd is the internal return code and pgrtcd is the PGSER return
code. The security look aside table must be in protected storage. CA Endevor SCM
disables the look aside table and processing continues.
Action:
The action depends on the meaning of the pgrtcd return code.
ENCS051C
UNABLE TO UNPROTECT ESI LOOKASIDE TABLE STORAGE, RC=rtcd, PGRC=pgrtcd, LAT
disabled
Reason:
An attempt to remove protection from the storage associated with the look aside table
failed. rtcd is the internal CA Endevor SCM return code. pgrtcd is the return code from
the PGSER protect request. The security look aside table is disabled. Security processing
continues without the look aside table.
Action:
Action is dependent upon the meaning associated with pgrtcd.
ENCS101C
C1GSEXTI INIT ERROR IN macro name MACRO,RC=code
Reason:
Unable to append the SMF record to the message.
Action:
ENCS Messages
ENCS101I
ORMAT=fmtnumber, PASS=passnumber, AUTH=authnumber, ACEE=address,
CLASS=class, ENTITY=resource.name, USER ACCESS IS action FROM source RACROUTE
RC=rrrtcd, RACHECK RC=rcrtcd, REASON=code
Reason:
This is the ESI trace message and the following fields are traced:
fmtnumber identifies the entity name format number.
passnumber identifies the current ESI pass.
authnumber identifies the SAF authorization code
address is the address of the ACEE passed to SAF.
class identifies the entity name resource class
resource.name is the entity name being verified
userid identifies the user for whom the record verification was performed
action is the result of the resource verification, either allowed or denied
source identifies the source of the verification, either SAF or LAT for the ESI security
look aside table
rrrtcd is the return code from the RACROUTE macro
rcrtcd is the return code from the RACHECK macro
code is the verification reason code
Action:
None.
ENCS147S
INVALID NAME EQUATES TABLE LOADED: EXTERNAL(external name)
INTERNAL(internal name)
Reason:
The name associated with the name equates table (BC1TNEQU) load module does not
match the name specified in the C1DEFLTS table.
Action:
Check the name specified with the ACCSTBL parameter on the C1DEFLTS table to make
sure it is correct. Check the name specified within the ESIDFLTS macro on the
BC1TNEQU to make sure it is correct. Make sure the tables are loaded from the correct
library.
ENCS Messages
ENCS148S
NAME EQUATES TABLE table name SPECIFIED WITH USE OF NATIVE SECURITY
Reason:
A conflict exists between the ACCSTBL and ESSI parameters within the C1DEFLTS table.
The ESSI parameter is set to a value of Y and the ACCSTBL is blank or the ESSI parameter
is set to a value of N and the ACCSTBL parameter is not blank.
Action:
Correct the conflict in the C1DEFLTS table.
ENCS301S
module-name NOT LOADED FROM AN AUTHORIZED LIBRARY
Reason:
Some modules and table in the CA Endevor SCM runtime environment must reside in
APF authorized libraries. These include ENUXISTE and C1DEFLTS, and depending on the
setting of the AUTHTBLS= operand in the C1DEFLTS TYPE=MAIN macro, may include exit
tables security tables (for both Native Security and the External Security Interface). CA
Endevor SCM verifies modules which must be loaded from authorized libraries and
issues this message if they are not.
ENCS301C is issued if AUTHTBLS=ALLOW was coded in C1DEFLTS. ENCS301S is issued if
AUTHTBLS=REQUIRED was coded, and will be followed by a S306 abend.
Action:
Check the allocations for the load libraries for STEPLIB, if one exists, or for the link list
allocations defined at your site. The libraries in use must be named in the IEAAPFxx or
PROGxx members of SYS1.PARMLIB in order to be authorized. If they are not, ask your
systems programmer to authorize them by adding them to the appropriate
SYS1.PARMLIB member. Your system must be IPLd for the new APF authorizations to
take effect.
ENCS Messages
ENCS302S
CS302S Load Module ',module-name,' was not found in any of the authorized libraries.
Reason=reason.
Reason:
This load module was not found in any of the libraries specified in the STEPLIB, LINKLST,
or LPA.
Action:
Make sure that the load library containing this module is included in the concatenation.
CA Endevor SCM modules are generally located in iprfx.iqual.CSIQAUTH or
iprfx.iqual.CSIQLOAD. User-defined tables are generally located in iprfx.iqual.CSIQAUTU.
ENCS303S
ENCS302S Load Module ',module-name,' was not found in
[ddname|STEPLIB\LNKLIST]. Reason=reason.
Reason:
This load module was not found. If a ddname appears in the message, then the load
module was not found in the any of the libraries associated with that ddname. If
STEPLIB/LNKLIST appears in the message, it implies that the load module was not found
in any of the libraries specified in the STEPLIB, LINKLST, or LPA.
Action:
Make sure that the load library containing this module is included in the concatenation.
CA Endevor SCM modules are generally located in iprfx.iqual.CSIQAUTH or
iprfx.iqual.CSIQLOAD. User-defined tables are generally located in iprfx.iqual.CSIQAUTU.
ENCS999I
SLAT ENTRY FOUND FOR resource.name
Reason:
A look aside table entry was found for the entity name called name. This message is
only produced when in debugging mode. Processing continues.
Action:
None.
ENDE Messages
ENDE Messages
ENDE messages are issued during processing when you are using the CA Endevor SCM
Quick Edit option.
ENDE00BE
Valid options are NONE, ALL, SYS, or SUB
Reason:
An invalid Span option was submitted on a batch request.
Action:
Correct the Span option and resubmit the request. Enter one of the following correct
Span options: AUTOGEN SPAN NONE, AUTOGEN SPAN ALL, AUTOGEN SPAN SYSTEMS,
or AUTOGEN SPAN SUBSYSTEMS.
ENDE001E
The Quick-Edit dialog has not been purchased by the installation
Reason:
The EDITELM password was not provided in the C1DEFLTS table.
Action:
Add the EDITELM password to the C1DEFLTS table.
ENDE002E
The field contains an ENDEVOR inventory location object name
Reason:
One or more of the following fields are in error: environment, system, subsystem, or
type.
Action:
Correct the field and try again.
ENDE Messages
ENDE003E
The field requires a Y or N value
Reason:
Either the Search Map field is specified incorrectly or the Include JCL field is specified
incorrectly on the batch JCL panel.
Action:
ENDE004E
Environment env-name is not defined or you are not authorized
Reason:
The environment entered is not found. It is either not defined in the C1DEFLTS table or
you do not have the proper authorization to access the environment.
Action:
Perform one of the following actions:
Correct the environment name.
Add the environment name to the C1DEFLTS table.
Change the security to allow access to this environment.
ENDE004W
Environment not defined
Reason:
A footprint of an element referred to an Environment in the defaults table, but the
Environment does not exist, or no longer exists in the defaults table.
Action:
Validate that you are using the correct inventory. If in doubt, contact your CA Endevor
SCM administrator. CA Endevor SCM will allow access to the files.
ENDE Messages
ENDE005E
The system specified is not defined
Reason:
The system specified is not defined to the environment specified.
Action:
Correct the system name.
Add the system to the environment.
ENDE006E
ENDE006E The Subsystem specified is not defined
Reason:
The subsystem entered is not defined to the system specified.
Action:
Correct the subsystem name.
Add the subsystem to the system.
ENDE007E
ENDE007E The Type specified is not defined
Reason:
The type entered is not defined to the system specified.
Action:
Correct the type name.
Add the type to the system.
ENDE Messages
ENDE008E
The Processor Group specified is not defined
Reason:
The processor group entered is not defined to the type specified.
Action:
Correct the processor group name.
Add the processor group to the type.
ENDE009E
The Processor Group specified is invalid
Reason:
The processor group entered is not defined to the type specified.
Action:
ENDE011E
There are no Environments that match the Environment mask
Reason:
A wildcarded environment name was entered into the environment field. No
environments are defined which match the mask, or the user doesnt have the proper
authorization (security) to access any environments which match the mask.
Action:
Perform one of the following:
Add the environment name to the C1DEFLTS table.
Change the security to allow access to this environment.
ENDE Messages
ENDE012E
ENDE012E There are no Systems that match the System mask
Reason:
A wildcarded system name was entered into the system field. No systems exist within
the environment specified which match the wildcarded mask.
Action:
Add the system to the environment.
ENDE013E
There are no Subsystems that match the Subsystem mask
Reason:
A wildcarded subsystem name was entered into the subsystem field. No subsystems
exist within the system specified which match the wildcard mask.
Action:
Correct the subsystem name.
Add the subsystem to the system.
ENDE014E
There are no Types that match the Type mask. A system may be required
Reason:
A wildcarded type name was entered into the type field. No types exist within the
system specified which match the wildcard mask.
Action:
Add the type to the system.
ENDE Messages
ENDE015E
There are no Processor Groups that match the Processor Group Mask
Reason:
A wildcarded processor group name was entered into the processor group field. No
processor groups exist within the type specified which match the wildcard mask.
Action:
ENDE016E
The element specified was not found
Reason:
No elements were found in the specified environment, system, subsystem, type or
stage. If search map was specified, the element was not found anywhere in the map.
Action:
Correct the element name, or Create the element.
ENDE018E
The element name specified is invalid
Reason:
The element name specified has one of the following problems:
Invalid character set: Characters must be A-Z, 0-9, $, #, @,?
Improper use of wildcard character: * can only appear once, and may be followed
by blanks.
Action:
ENDE Messages
ENDE019E
There were no elements found that match the selection criteria
Reason:
Some elements may have been found in the specified environment, system, subsystem,
type, and stage (or in the map if search map was specified), BUT additional criteria was
specified which prevented any elements from being selected for processing. Such
criteria includes:
Where CCID is:
Where Processor Group is:
Action:
Change or eliminate the additional search criteria, or change the element name field.
ENDE020E
Single quotation marks are not allowed in the Comment field
Reason:
The comment field contains single quotation marks.
Action:
Remove the single quotation marks from the comment field.
ENDE021E
The Processor Group name specified is invalid
Reason:
One or more of the following fields are in error:
Processor Group
Where Processor Group is
The name specified has one of the following problems:
Invalid character set: Characters must be A-Z, 0-9, $, #, @,?
Improper use of wildcard character: * can only appear once, and may be followed
by blanks.
Action:
ENDE Messages
ENDE022E
The environment env-name contains an incorrect stage ID.
Reason:
The specified stage ID is not defined for the specified environment
Action:
Correct the stage ID.
ENDE023E
The create option is not allowed from the selection list
Reason:
The create option was specified in the element selection list.
Action:
None.
ENDE024E
Retain Signout=Y and Set Signout Id are mutually exclusive.
Reason:
Two mutually exclusive options, retain Signout=y and Signout to ID, were specified
together.
Action:
Either leave the Signout to ID blank or specify retain Signout=n.
ENDE025E
No data sets selected from the component list.
Reason:
A component list action (LO or LL) was specified, but no data sets were selected from
the component list.
Action:
Verify the component list contains the desired information.
ENDE Messages
ENDE026E
The selected member was not found in the data set.
Reason:
A component list action (Lo or LL) was specified, but the member was not found in the
data set.
Action:
ENDE027W
The component list has been copied and may not be accurate.
Reason:
A component list action (LO or LL) was specified and the output components did not
reflect the actual output member locations because the component list was copied
when the element was last moved.
Action:
ENDE028E
Requested member is no longer in specified data set.
Reason:
A component list action (LO or LL) was specified and the member was not found in the
data set. The output components no longer reflect the actual output member locations
because the component list was copied when the element was last moved.
Action:
Check the Component listing footprints from the CA Endevor SCM Footprints Display.
ENDE Messages
ENDE029E
The footprint is missing or it does not match the current element location.
Reason:
Indicates a footprint error caused by one of the following:
A component list action (LO or LL) was specified and the member was found, but
the footprint information of the component list does not correspond to the current
selected member. The component list was copied to the next stage in the map, but
not updated to match the current element location when the element was last
moved and there is a new version of the element residing in the first stage of the
map.
The footprint information is missing or is corrupted.
Action:
Check the Component listing footprints from the CA Endevor SCM Footprint Display.
ENDE030I
Element element-name has been created
Reason:
The element has been created and placed into the entry stage of the environment
specified.
Action:
None.
ENDE031I
Element element-name has been saved and generated
Reason:
The element has been saved and generated in the foreground.
Action:
None.
ENDE Messages
ENDE032I
The element was saved but the processor cannot execute in the foreground
Reason:
The element has been saved, but either the processor cannot execute in foreground or
generate element after edit was not selected on the entry panel.
Action:
A generation of the element should be performed.
ENDE033I
VVLL &variable of element &EEVELMNM has been created
Reason:
As a result of entering a SAVE command in ISPF/PDF edit, a new delta level of the
element has been created.
Action:
None.
ENDE036E
The CREATE action requires a fully specified element name
Reason:
The element name field is blank. The CREATE action requires an element name to be
specified without any wildcard characters.
Action:
Correct the element name field and try again.
ENDE Messages
ENDE037E
The element already exists. It cannot be created
Reason:
An element with this name already exists in the inventory. It may exist in the location
specified, or somewhere in the map. The map is always searched prior to allowing a new
element to be created.
Action:
Correct the element name field, or EDIT the element instead of attempting to CREATE
the element.
ENDE038I
The element will be created when the END or SAVE command is issued
Reason:
When ISPF/PDF is entered to create a new element, this message displays to indicate
that the element doesn't actually get created until you either save it, or exit ISPF/PDF
and allow automatic save to occur. If you cancel from ISPF/PDF at this point, the
element will not be created.
Action:
None.
ENDE039E
The element name cannot be wild carded on a CREATE request
Reason:
The element name field is wildcarded. The CREATE action requires an element name to
be specified without any wildcard characters.
Action:
Correct the element name field and try again.
ENDE Messages
ENDE041I
The element was located by searching the environment map
Reason:
When ISPF/PDF is entered to edit an existing element, this message may be display
indicating that the element was found in the search map, not at the edit location. The
element will be fetched to the edit location when the first save is performed, or when
exiting ISPF/PDR an automatic save occurs.
Action:
None.
ENDE042I
System system-name requires a CCID
Reason:
The system requires a CCID to be specified.
Action:
Specify a valid CCID.
ENDE043I
System system-name requires a comment
Reason:
The system requires a comment to be specified.
Action:
Specify a valid comment.
ENDE044I
System system-name requires a CCID. Should this CCID be used?
Reason:
The system requires a CCID to be specified. Previously in this session, you used the CCID
shown.
Action:
To use the CCID again, press ENTER or specify a new CCID.
ENDE Messages
ENDE045I
System system-name requires a comment. Should this CCID be used?
Reason:
The system requires a comment to be specified. Previously in this session, you used the
comment shown.
Action:
To use the comment again, press ENTER or specify a new comment.
ENDE046E
The request was canceled by the user
Reason:
When prompted for a CCID or comment, the user entered the END command and
canceled the request.
Action:
None.
ENDE046I
The request was canceled by the CANCEL command
Reason:
The user entered the CANCEL command while editing an element. The save or creation
of the element is bypassed and essentially nothing has changed.
Action:
None.
ENDE047I
Element element-name was changed but the generate processor was NOT run
Reason:
The user entered the CANCEL command while editing an element, BUT the element had
already been saved by the SAVE command. Any changes entered after the SAVE
command have not been recorded and the element has not been generated.
Action:
The element needs to be generated.
ENDE Messages
ENDE048I
Element element-name was successfully generated
Reason:
The element has been successfully generated in foreground.
Action:
None.
ENDE049E
Element element-name is signed out to another user
Reason:
The element is signed out to another user and signout override has not been specified.
Action:
Contact the other user to sign in the element, or specify signout override to
edit/generate the element anyway.
ENDE050E
The Source Element Length for type type-name is greater than 255
Reason:
The element length (as defined in the type record) is greater than 255. ISPF/PDF does
not allow editing of data sets where the LRECL is greater than 255.
Action:
If the element length specified in the type record can be reduced to 255, change the
element length in the type record. Otherwise, no elements of this type can be edited
with QuickEdit.
ENDE051E
There is no component information associated with the element
Reason:
The request to browse the component list has failed. This element does not have any
component information. The request may be BX, CX, or HX.
Action:
None.
ENDE Messages
ENDE052E
There are no element or component change levels for the element
Reason:
The request to display the last level changes has failed. The request may be C (element
changes) or CX (component changes). If C, the element does not have any change
levels. If CX, it is the component list which does not have any changes.
Action:
None.
ENDE053E
The specified processor group could not be found
Reason:
The processor group is not valid for the specified type.
Action:
Correct the processor group field, or change to a different type.
ENDE054I
No changes were found. A new level was NOT created
Reason:
A save was specified. No changes were detected. A new level was not created. The
element may have been fetched and stored into the entry stage if it did not exist there
previously.
Action:
None.
ENDE055I
No changes were made to the element. Source Management was NOT done
Reason:
The ISPF/PDF edit session is complete. No element changes were made.
Action:
None.
ENDE Messages
ENDE056E
The element is currently being used by another ENDEVOR user
Reason:
The element is currently being used by someone else. This may be an on-line user or a
batch job.
Action:
Try again later when the element may be available.
ENDE057E
Endevor system system-name is currently locked for backup
Reason:
CA Endevor SCM has locked the system while an UNLOAD or RELOAD is being
performed.
Action:
Try again later after the system UNLOAD or RELOAD has finished.
ENDE058E
You are not authorized to perform the action against the element
Reason:
The security system rejects the request. The user is not authorized to perform the
request against the element.
Action:
Change the authority of the user.
ENDE059E
Generate processor for group group-name cannot execute in foreground
Reason:
The generate processor is flagged to not allow execution in foreground.
Action:
Use batch generate to execute the generate processor in batch.
ENDE Messages
ENDE060I
An environment was NOT selected from the Environment List
Reason:
The environment name field was wildcarded and an environment list presented. The
user did not select any environment from the list. Processing cannot continue without a
valid environment.
Action:
Specify a valid environment name, or select an environment from the list presented.
ENDE061I
A system was NOT selected from the System List
Reason:
The system name field was wildcarded and a system list presented. The user did not
select any system from the list. For a CREATE request, processing cannot continue
without a valid system. For an EDIT or GENERATE request, the 'Display
system/subsystem list' field is set to 'Y' and a system must be chosen from the list.
Action:
For a CREATE request, enter a valid system name, or select a system from the list
presented. For an EDIT or GENERATE request, enter a valid system name, or select a
system from the list presented, or change 'Display system/subsystem list' field to 'N'.
ENDE062I
A Subsystem was NOT selected from the Subsystem List
Reason:
The subsystem name field was wildcarded and a subsystem list presented. The user did
not select any subsystem from the list. For a CREATE request, processing cannot
continue without a valid subsystem. For an EDIT or GENERATE request, the 'Display
system/subsystem list' field is set to 'Y' and a subsystem must be chosen from the list.
Action:
For a CREATE request, enter a valid subsystem name, or select a subsystem from the list
presented. For an EDIT or GENERATE request, enter a valid subsystem name, or select a
subsystem from the list presented, or change 'Display system/subsystem list' field to
'N'.
ENDE Messages
ENDE063I
A Type was NOT selected from the Type List
Reason:
The type name field was wildcarded and a type list presented. The user did not select
any type from the list. This is a CREATE request and processing cannot continue without
a valid type.
Action:
Specify a valid type name, or select a type from the list presented.
ENDE064E
A Processor Group was NOT selected from the Processor Group List
Reason:
The processor group name field was wildcarded and a processor group list presented.
The user did not select any processor group from the list. Processing cannot continue
without a valid processor group.
Action:
Specify a valid processor group name, or select a processor group name from the list
presented.
ENDE065E
The selection character specified is invalid
Reason:
A selection list was presented and a character other than 'S' was placed in the select
column in the list.
Action:
Use the proper select character - 'S'.
ENDE Messages
ENDE066E
Only one selection can be made from the list
Reason:
A selection list was present and more than one item was selected.
Action:
Limit the selection to one entry.
ENDE067E
Enter F for Foreground mode or B for Batch mode.
Reason:
An invalid character was used in the field 'Generate Process or Mode'. Either an 'F' or 'B'
must be used.
Action:
Change the character specified to 'F' or 'B'.
ENDE068I
JCL to generate element element-name has been submitted.
Reason:
A job has been submitted to generate the element.
Action:
None.
ENDE069E
At least one JCL JOB Card is required.
Reason:
At least one JCL image is required in the JOB Card fields.
Action:
Specify at least one JCL image in the JOB Card fields.
ENDE Messages
ENDE072E
A valid Unit Name must be specified
Reason:
In the defaults panel, a valid unit name must be specified. The field is only checked for
its presence, but an invalid name will cause allocation errors to occur during processing.
Action:
Specify a valid unit name.
ENDE074I
The Dialog Defaults update was canceled at the user's request
Reason:
The user entered the END command and the update of the defaults was cancelled.
Action:
None.
ENDE075I
The Dialog Defaults were successfully updated
Reason:
The defaults panel has been processed and all changes have been saved.
Action:
None.
ENDE076E
The Space Unit value specified is invalid
Reason:
The value specified in the Space Unit field is not supported.
Action:
Enter BLK for logical block allocation, TRK for trace allocation, or CYL for cylinder
allocation.
ENDE Messages
ENDE077I
The Action Options update was canceled at the user's request
Reason:
The END key was pressed on the Action Options panel to cancel any updates.
Action:
Press ENTER to save the updates.
ENDE078I
The Action Options were successfully updated
Reason:
The ENTER key was pressed on the Action Options panel to save any updates.
Action:
Press END to cancel the updates.
ENDE079I
Element element-name was successfully moved
Reason:
A MOVE action was successfully completed.
Action:
None.
ENDE080E
The element is a component of a package that has been backed out
Reason:
The element selected is in a backed out state. This means that the source for the
element is not reflected by the current outputs from the latest generate of the element.
Action:
None.
ENDE Messages
ENDE081E
The ISPF/PDF BROWSE service passed a return code of X''return-code''
Reason:
The ISPF/PDF BROWSE service set a return code greater than 4 when returning to
QuickEdit. This is considered an error.
Action:
Note the return code value and notify your systems programmer.
ENDE082E
The ISPF/PDF EDIT service passed a return code of X 'return-code'
Reason:
The ISPF/PDF EDIT service set a return code greater than 4 when returning to QuickEdit.
This is considered an error.
Action:
Note the return code value and notify your systems programmer.
ENDE083E
The action was canceled by an Endevor User Exit
Reason:
The site supplied user exit 2 has canceled the request, but no message was set by the
user exit.
Action:
Notify your site QuickEdit Administrator to examine the user exit 2 for reasons why the
request was canceled.
ENDE Messages
ENDE084E
The element is signed out and Override Signout is not authorized
Reason:
Message C1E0104E was issued indicating that the element is currently signed out to
another user, and Signout Override was specified on the QuickEdit panel. However, this
user is not authorized to use Signout Override.
Action:
Communicate with the user who has the element signed out.
ENDE085E
The Quick Edit dialog is already active in this ISPF logical screen
Reason:
QuickEdit cannot be invoked recursively.
Action:
Use PF3 (END) to back up until the QuickEdit panels display again.
ENDE086I
Foreground execution of the generate processor is NOT allowed
Reason:
When ISPF/PDF is entered to edit this element, this message will display if the processor
group is marked to not allow foreground execution.
Action:
None.
ENDE087E
The Batch Generate request has been canceled at the users request
Reason:
The JCL panel was displayed and the user ended the request without the batch job being
submitted.
Action:
None.
ENDE Messages
ENDE088I
Element element-name was successfully deleted
Reason:
A DELETE action was successfully completed.
Action:
None.
ENDE089l
The component list for element element-name was successfully deleted.
Reason:
The DELETE action with the ONLY COMPONENTS option was successfully completed.
Action:
None.
ENDE090E
The service-name service passed a RC of X''return-code'' (program-name)
Reason:
An unexpected return code was returned from the specified ISPF/PDF service routine.
Action:
Make note of the information and notify your systems programmer.
ENDE091E
$IMR passed a RC of X''return-code''. Enter HELP for more information
Reason:
An unexpected return code was returned from the internal $IMR service routine.
Additional information can be obtained by entering HELP when the error occurs.
Action:
Make note of the information and contact your administrator.
ENDE Messages
ENDE092E
$SMR passed a RC of X''return-code''. Enter HELP for more information
Reason:
An unexpected return code was returned from the internal $SMR service routine.
Action:
ENDE093S
A abend code ABEND occurred during Quick Edit processing
Reason:
QuickEdit has abended.
Action:
ENDE094E
Unable to load program program-name. $BLOAD RESULT=result-code
Reason:
A required program cannot be found.
Action:
Most likely this is a CONLIB concatenation error. Review CONLIB allocations. If the
ENDE095E
$FPGR passed a RC of X''return-code''. Enter HELP for more information
Reason:
An unexpected return code was returned from the internal $FPGR service routine.
Action:
ENDE Messages
ENDE100E
Data set allocation failed. Enter HELP for more information
Reason:
SVC 99 (dynamic allocation) returned an unexpected return code. Additional
information can be obtained by entering HELP when the error occurs.
Action:
ENDE101E
Generate In-Place and NoSource cannot both be set to Y
Reason:
This message is generated from the QE Action Options panel ENDIE150 when both
Generate In Place and Generate NoSource are set to Y.
Action:
Either Generate Element In Place or Generate Element NoSource must be set to N.
ENDE102E
B, C, H, and S options are invalid on a sourceless element.
Reason:
This message is generated from the Quick Edit Element Selection List panel ENDIE250 if
options (B)rowse, (C)hange, (H)istory or (S)ummary are specified on a sourceless
element.
Action:
None.
ENDE103I
The ENV/SYS/SBS selection dialog was canceled by PF3 or the END command
Reason:
The user entered an END command or used the PF3 key command on the Target
Location Specification panel ENDIE205. This user action canceled the dialog.
Action:
None.
ENDE Messages
ENDE104E
There is no possible target location with the specified names that map to the selected
element
Reason:
The chosen inventory location does not map to the selected element.
Action:
Enter another location or leave the environment, system and subsystem fields blank to
be prompted with valid locations.
ENDE105E
The entered combination of Environment, System, and Subsystem does not exist
Reason:
The combination of the entered ENV/SYS/SBS values does not exist.
Action:
Enter another location or leave the environment, system and subsystem fields blank to
be prompted with valid locations.
ENDE106E
The Environment does not exist, or you do not have permission to use it
Reason:
The specified Environment does not exist in the CA Endevor SCM repository or you do
not have security permission to access it.
Action:
Enter a valid Environment or select it from ENV selection panel.
ENDE107E
The System does not exist, or you do not have permission to use it
Reason:
The specified System does not exist in the CA Endevor SCM repository or you do not
have security permission to access it.
Action:
Enter a valid System or select it from the SYS selection panel.
ENDE Messages
ENDE108E
The Subsystem does not exist, or you do not have permission to use it
Reason:
The specified Subsystem does not exist in the CA Endevor SCM repository or you do not
have security permission to access it.
Action:
Enter a valid Subsystem or select it from the SBS selection panel.
ENDE109E
ISPF error occurred during processing
Reason:
ISPF services used in the routine ended with an error.
Action:
ENDE110S
program-name: An abend-code ABEND occurred during processing
Reason:
A QuickEdit program has abended while attempting to process the ISPF/PDF CANCEL,
SAVE, or END comment. Additional information can be obtained by entering HELP when
the error occurs.
Action:
ENDE130I
JCL has been submitted to generate the element
Reason:
A batch generate was requested. The JCL has been submitted to generate the element.
Action:
None.
ENDE Messages
ENDE131E
The request to generate the element in batch mode was canceled
Reason:
A batch generate was requested. The user canceled the request.
Action:
None.
ENDE132I
The element was saved and JCL was submitted to generate the element
Reason:
An element was edited and batch generate was requested. The edit was successful and
the batch job submitted.
Action:
None.
ENDE133I
The element was saved but the user canceled the batch generate
Reason:
An element was edited and batch generate was requested. The edit was successful, but
the user cancelled the batch job submission.
Action:
The element still needs to be generated.
ENDE134l
The element was copied into the current EDIT session
Reason:
A COPYELM action was successfully completed.
Action:
None.
ENDE Messages
ENDE135l
The request to copy an element was canceled
Reason:
A COPYELM action was canceled by pressing the END key without selecting any element.
Action:
None.
ENDE136l
JCL has been submitted to delete the element
Reason:
A DELETE action using the DELETE ACTION MODE =Batch command has been processed.
Action:
None.
ENDE137E
The request to delete the element in the batch mode was canceled
Reason:
A DELETE action using the MOVE ACTION MODE=Batch command has been canceled.
Action:
None.
ENDE138l
JCL has been submitted to move the element
Reason:
A MOVE action with the MOVE ACTION MODE=Batch command has been processed.
Action:
None.
ENDE Messages
ENDE139E
The request to move the element in the batch mode was canceled
Reason:
A MOVE action using the MOVE ACTION MODE= Batch has been canceled.
Action:
None.
ENDE150I
The element element-name was successfully signed in
Reason:
The SIGNIN action was successfully completed.
Action:
None.
ENDE153l
The element element-name was successfully signed out
Reason:
The SIGNOUT action was successfully completed.
Action:
None.
ENDI Messages
ENDE200E
Element exists at lower stage, use Generate-in-place
Reason:
An attempt was made to generate an element with the option GENERATE IN PLACE set
to N. This option copies the element back into the entry stage for the generate of the
starting environment. However in this case, the element could not be copied back
because it was either at the target location already or at a stage lower than the selected
element location.
Action:
You can perform any of the following actions, when this message appears:
With the option GENERATE IN PLACE set to Y, attempt to generate the element
again. This option generates the element in the stage where it is found.
With the Generate in place option set to N, select the element that exists in the
lower stage in the lifecycle for GENERATE w/COPYBACK.
ENDI Messages
ENDI001E
Unable to load the Endevor ISPF Configuration table, ENDICNFG'
Reason:
The load module 'ENDICNFG' was not found in CONLIB.
Action:
Most likely this is a CONLIB concatenation error. Review CONLIB allocations. If the
ENDI002E
The Endevor dialog is already active in this ISPF logical screen'
Reason:
CA Endevor SCM cannot be invoked recursively.
Action:
Use the END key to back up until the CA Endevor SCM panels display again.
ENIP Messages
ENDI003S
The Endevor Dialog terminated with a &C1ABC ABEND'
Reason:
CA Endevor SCM has abended.
Action:
ENIP Messages
This section details messages generated by the CA Endevor SCM ISPF in the course of
ENIP001E
Invalid Action
Reason:
The action selected is undefined.
Action:
Select a valid action.
ENIP002E
Data Set not Found
Reason:
The data set specified was not found in the system catalog.
Action:
Specify a valid data set.
ENIP Messages
ENIP003E
A Y or N is Required
Reason:
A Y(es) or N(o) is required for this field.
Action:
Enter the Y or N as appropriate.
ENIP004E
Invalid DS Attributes
Reason:
The SCL data set specified has incorrect attributes.
Action:
Enter the Y or N as appropriate.
ENIP005E
JCL JOB Card Required.
Reason:
At least one JCL JOB card statement is required.
Action:
Add a JCL JOB card and execute the job.
ENIP006I
Job Submitted
Reason:
Informational message. The Batch Package Facility job was successfully submitted.
Action:
None.
ENIP Messages
ENIP007I
No Syntax Errors
Reason:
Informational message. The SCL statements were validated with no errors.
Action:
None.
ENIP008E
Validation Error
Reason:
The SCL statements contained one or more syntax errors.
Action:
The syntax must conform to the standards described in the SCL Reference Guide.
ENIP0009E
Member not Found
Reason:
Informational message. The member was not found in the specified data set.
Action:
None.
ENIP0101
&PDVSCLCR Statements written
Reason:
&PDVSCLCR action statements were written.
Action:
None. This is an informational message.
ENIP Messages
ENIP011I
DESCRIPTION REQUIRED DESCRIPTION FIELD IS REQUIRED - ENTER A NON-BLANK
CHAR
Reason:
The description field was left blank.
Action:
Enter a non-blank character in the description field.
ENIP020E
Package ID Required
Reason:
A package ID is required when the DEFINE action is selected.
Action:
Enter the name of the package you are defining in the Package ID field.
ENIP021E
Wild Card not Allowed
Reason:
A wild card package ID is not allowed for the action selected.
Action:
Enter the full name of the package ID.
ENIP022E
Package ID not Found
Reason:
Informational Message. The package ID specified was not found.
Action:
None.
ENIP Messages
ENIP023E
No Packages Selected
Reason:
There were no packages that matched the filter criteria.
Action:
ENIP024E
Invalid Value
Reason:
The Where Older than value must be blank or numeric.
Action:
Either make the field blank or enter the correct numerical value.
ENIP030E
Invalid Status
Reason:
Package &PDVCPKGI is not in a valid state for the action.
ENIP036E
Description Required
Reason:
The package description field must be completed.
Action:
Provide a package description in the Description field.
ENIP Messages
ENIP037E
Imbedded Quotes
Reason:
The package description field contains one or more single quote marks.
Action:
This is an informational message. If the text of the description contains imbedded
spaces, they must be enclosed in single quotation marks.
ENIP038E
Date Required
Reason:
The Execution Window date field is required.
Action:
The Execution Window indicates the time frame within which the package can be
executed. Enter the start and end dates in the From and To fields in Execution Window.
ENIP039E
Time Required
Reason:
The Execution Window TIME field was left blank.
Action:
Enter the start and end times in the Execution Window FROM and TO fields.
ENIP040E
Invalid Date
Reason:
The dates in the Execution Window FROM and TO fields were not entered in the proper
format.
Action:
Specify the Execution Window date in DDMMMYY format. For example, 01JAN98.
ENIP Messages
ENIP041E
Invalid Time
Reason:
The times in the Execution Window FROM and TO fields were not entered in the proper
format.
Action:
Specify the Execution Window time in HH:MM format. For example, 12:00.
ENIP042E
Incorrect Date/Time
Reason:
The TO date and time is earlier than the current date and time.
Action:
Reenter the date and time and make sure that the date and time is later than the
current date and time.
ENIP043E
Incorrect Date/Time
Reason:
The TO date and time is earlier than the FROM date and time.
Action:
Reenter the date and time to ensure that the FROM date and time is earlier than the TO
date and time.
ENIP044E
Package not Found
Reason:
Informational message. Package &PDVCPPKG does not exist.
Action:
None.
ENIP Messages
ENIP045E
Invalid Package ID
Reason:
The specified package ID is invalid. The Package to be copied cannot be wild carded.
Action:
Specify the full name of the package ID.
ENIP050E
Invalid Attributes
Reason:
The data set specified has invalid attributes.
Action:
Check the attributes specified and provide the correct attributes.
ENIP051E
Member Exists
Reason:
The member specified already exists and NO REPLACE was specified.
Action:
Check the member name specified. If the member name is correct and you want to
replace the existing member, specify Y in the REPLACE MEMBER field.
ENIP052E
Validation Failed
Reason:
The data set specified failed the validation process.
Action:
Specify a valid data set.
ENIP Messages
ENIPN053E
Data Set Name Required
Reason:
A data set name is required for the &PDVACTN action.
Action:
Specify a valid data set name.
ENIP054E
SCL Must be Provided
Reason:
The DEFINE action requires that SCL be provided for the package.
Action:
Specify the location of the SCL to be added to the package by specifying either an
IMPORT SCL FROM or a COPY PACKAGE FROM clause to the DEFINE action. Resubmit
the request.
ENIP055E
Mutually Exclusive
Reason:
IMPORT SCL Data set and "Package to be copied" are mutually exclusive.
ENIP056E
Not Authorized for Action
Reason:
You are not authorized for the &PDVACTN action against &PDVCPKGI package.
Action:
ENIP Messages
ENIP057E
Invalid Value
Reason:
The value specified is invalid.
Action:
Specify Y, N, or W for this field.
ENIP058E
JCL Procedure Required
Reason:
The JCL Procedure name is required.
Action:
Specify the name of the JCL Procedure.
ENIP060E
Packages not Available
Reason:
The C1DEFLTS table does not contain a Package Data Set.
ENIP061E
Invalid Member
Reason:
The member name is too long or contains invalid characters.
Action:
Specify the correct member name.
ENIP Messages
ENIP062E
Member Specified
Reason:
Informational message. A member was specified for a sequential data set.
Action:
None.
ENIP063E
Dataset Validation Error
Reason:
The SCL data set failed the validation criteria.
Action:
Specify a valid SCL data set.
ENIP064E
Wild Card not Allowed
Reason:
The SCL data set member name cannot be wild carded.
Action:
Enter the full name of the SCL data set member.
ENIP065E
Member Name Required
Reason:
A partitioned data set requires a member name
Action:
Specify a valid member name.
ENIP Messages
ENIP070E
Internal Dialog Error
Reason:
The SCL data set object could not be created
Action:
ENIP071E
Reason:
The Package Dialog Work Area (PWA) could not be allocated.
Action:
ENIP072E
Reason:
The dialog flow-of-control table could not be loaded.
Action:
ENIP073E
Reason:
The XP Service Object does not exist.
Action:
ENIP Messages
ENIP080E
Invalid Value
Reason:
The value specified for Package Type is invalid.
Action:
The Package Type must be either STANDARD or EMERGENCY.
ENIP081E
Change not Allowed
Reason:
The Execution Window can be changed ONLY when it is closed.
Action:
Close the Execution Window before making any changes.
ENIP082E
Package Not Eligible
Reason:
Package &PDVPKGID is not eligible to be modified.
Action:
ENIP083E
Action Not Supported
Reason:
Foreground Execution of the &PDVACTN action is not supported.
Action:
ENIP Messages
ENIP084E
Invalid Package ID
Reason:
Package ID &PDVPKGID contains one or more invalid characters. Only alphanumeric,
blanks, and the national characters # and $ are allowed in a package ID.
Action:
Correct the invalid package ID. Resubmit the request.
ENIP085I
SCL Written
Reason:
Informational message. The SCL statement has been written to the SCL data set.
Action:
None.
ENIP086I
Define Cancelled
Reason:
Informational message. This message confirms that the DEFINE action has been
cancelled.
Action:
None.
ENIP087E
Not Allowed. HELP=ENIPH087
Reason:
The specified action is not allowed for this package. Enter HELP for more information.
Action:
ENIP Messages
ENIP088E
Imbedded Quote
Reason:
The Package Note Text cannot contain imbedded single quotes.
Action:
This is an informational message. If the text of the Package Note contains imbedded
spaces, they must be enclosed in single quotation marks.
ENIP090E
Internal Error
Reason:
An internal error occured.
Action:
ENIP091E
ISPF Service Error
Reason:
The ISPF &PDVISRV. service failed with a return code of X&PDVERRRC
Action:
ENIP100I
Member Saved
Reason:
Informational Message. The partitioned data set member has been saved.
Action:
None.
ENIP Messages
ENIP101E
Data Set in Use
Reason:
The specified data set is in use by another user.
Action:
Retry later.
ENIP102E
No Matches Found
Reason:
Informational message. No members matched the specified pattern.
Action:
None.
ENIP103E
Serious Error
Reason:
A serious ISPF/PDF EDIT or BROWSE error occurred.
Action:
Check the syntax of the command and issue it again.
ENIP104I
Data Set Saved
Reason:
Informational message. The specified data set has been updated
Action:
None.
ENIP Messages
ENIP105E
Member not Found
Reason:
Informational message. The requested member was not found in the SCL data set.
Action:
None.
ENIP106E
No Matches Found
Reason:
Informational message. No members matched the specified pattern or the SCL data set
is empty.
Action:
None.
ENIP107E
Empty Data Set
Reason:
Informational Message. The SCL data set or data set member was empty
Action:
None.
ENIP110E
VALIDATE Not Available
Reason:
The VALIDATE option is not yet available.
Action:
None.
ENMP Messages
ENMP Messages
This section details messages generated in the course of Batch Package processing,
ENMP001E
Package package id already exists
Reason:
An attempt was made to create a package which already exists.
Action:
Choose a different package ID or modify the package specified.
ENMP080I
Submitting jobname
Reason:
The named job is being submitted for the execution of one or more packages.
Action:
ENMP081E
Jobcard for package submission could not be accessed
Reason:
The data set containing the package submission JOB card was either empty, could not
be found or could not be opened.
Action:
Correct the jobcard DDNAME, DSNAME, or DSNAME/member on the "submit package"
statement.
ENMP Messages
ENMP090I
userid initiating request of package id
Reason:
A package request editor/executor received a request (create, modify, cast, execute,
etc.) to operate on the package. More messages follow.
Action:
No action required.
ENMP091I
Successful request of package id
Reason:
A package request (create, modify, cast, execute, etc.) completed successfully.
Action:
No action required.
ENMP092I
Unsuccessful attempt to request package id
Reason:
A package request (create, modify, cast, execute, etc.) completed with a non-zero
return code.
Action:
Check previous messages and the JES log for the reason for the failure.
ENMP093E
data set name (member) exists and replace was not specified
Reason:
An "export" or "archive" action specified a data set name and member name. The
member already exists and "replace" was not specified.
Action:
Specify "replace" or choose a member name which does not exist.
ENMP Messages
ENMP094E
userid was denied access to non-sharable package package id
Reason:
The package was marked non-sharable and the user requesting access to the package is
not the owner. Non-sharable was not overridden in the corresponding package exit.
Action:
The creator of this package must change it to sharable if others are to be allowed to
modify it.
ENMP095E
data set name record length must be greater than 4095 to be an archive data set
Reason:
Archive data sets must be RECFM=V or VB and have a minimum LRECL of 4096. The data
set specified has an LRECL which is less than the minimum.
Action:
Choose or allocate a data set with the minimum LRECL and the correct RECFM.
ENMP096E
data set name RECFM must be V or VB to be an archive data set
Reason:
Archive data sets must be RECFM=V or VB and have a minimum LRECL of 4096. The data
set specified has an invalid RECFM.
Action:
Choose or allocate a data set with a RECFM of V or VB.
ENMP Messages
ENMP097E
The package data set name was not specified in the defaults table (C1DEFLTS)
Reason:
The C1DEFLTS that was loaded cannot be used for package processing because PKGDSN
was not coded.
Action:
Assemble the C1DEFLTS table with PKGDSN coded and link it into a library where it will
be the one loaded.
ENMP098E
Tagged Field Error
Reason:
An attempt was made to Create_TFC or Create_TDF and it didnt work. Possible storage
error (format 1), old version of ENMC$TFO (format 2), or none zero return code (format
3).
Action:
If a storage error and the result is "NOSTG", increase the region size. If any of the other
formats occur, check the data sets making up CONLIB and make sure that the
concatenation doesnt contain more than one release of CA Endevor SCM.
ENMP099E
Package package id is not eligible for function
Reason:
The current status of the package (in-edit, approved, in-approval, executed, etc.) makes
it ineligible for the specified function (casting, execution, etc.).
Action:
For more information about packages, see the Packages Guide.
ENMP Messages
ENMP201E
Package name package id must consist of valid characters, numerics, and nationals
Reason:
The package has an illegal character in its name. Valid characters are A-Z (capitals only),
0- 9, $, @, #, and embedded spaces. Leading spaces are invalid.
Action:
Examine the package ID and make the appropriate corrections.
ENMP204E
type data set or member not found
Reason:
The data set or member was not found. The type can be "Import", "Export", or
"Archive."
Action:
Correct the DDNAME, DSNAME, or DSNAME/member name on the package SCL
statement. If DDNAME was used, be sure that there is a DD card bearing that name in
the JCL.
ENMP233E
Input package package id was not found
Reason:
A request to define (create or modify) a package specified another package ID which
contains the SCL. The latter package was not found.
Action:
Correct the COPY FROM package ID.
ENMP Messages
ENMP234I
Package "pkgid" has no SCL statements
Reason:
A package was created or modified resulting in a package without any SCL statements.
Action:
None. The package has been created and can be updated later with the required SCL
statements.
ENMP234W
Package "pkgid" has no SCL statements
Reason:
A request to export PKG SCL was made, but the package contained no SCL statements.
Action:
Ensure that the correct package ID was specified. The target data set of the EXPORT has
not been modified.
ENMP290E
dynamic allocation error message text
Reason:
An error was encountered in attempting to allocate the package work data set or the
package report data set. The message contains the dynamic allocation return code.
Action:
See the appropriate IBM documentation to interpret the return code.
ENMP296E
No SCL was built, copied, or imported
Reason:
An attempt was made to create a package but no SCL was provided via the import or
copy process.
Action:
Make sure that the import data set or COPY FROM package is not empty.
ENMP Messages
ENMP300E
Package will not execute due to a closed execution window
Reason:
A package INSPECT function was executed against a package whose execution window
has passed. The package can no longer be executed.
Action:
None.
ENMP300I
Package execution window is from date time thru date time - status is status
Reason:
Informational message. This message is generated by the PACKAGE INSPECT action.
Packages that are In-approval, Approved, In-execution, or Exec-failed can be selected for
the INSPECT action. This message is followed by message ENMP300W if the execution
window is closed.
Action:
None.
ENMP300W
The Package execution window is in the future
Reason:
Warning message generated by the PACKAGE CAST/INSPECT actions. The date and time
of the CAST/INSPECT actions does not fall within the specified execution window for the
package. The execution window is printed in the preceding ENMP300I message.
Although the rest of the CAST/INSPECT actions may successfully complete, the package
will not execute unless the date and time fall within the execution window.
Action:
None.
ENMP Messages
ENMP301I
Package SCL successfully extracted
Reason:
Informational message. This message is generated by the package inspect action. The
SCL associated with the package was successfully extracted from the package file.
Parsing of the SCL follows this message.
Action:
None.
ENMP302I
Package element and member validation started
Reason:
element and member validation part of the inspect action has been started. This
message can be followed by error messages associated with security violations, signout
conflicts, and/or source changes.
Action:
None.
ENMP303I
Package element and member validation successfully completed
Reason:
element and member validation part of the inspect action has been successfully
completed.
Action:
None.
ENMP Messages
ENMP304I
Package element and member validation completed with warnings, cautions, and/or
errors
Reason:
element and member validation part of the inspect action has been completed.
Non-zero return codes have been detected.
Action:
Check for other error messages accompanying this message.
ENMP305I
Package STMT stmt number
Reason:
Informational message. This message indicates that a validation of a PKG action, whose
statement number is xxxxx, issued a message. This message is always followed by
ENMP306I.
Action:
None.
ENMP306I
NO, WARNING, CAUTION, or ERROR messages were issued during SRC-ELM, TGT-ELM,
COMMENT, CCID, EXIT-2, SYNC, JUMP, or SIGNOUT
Reason:
This message indicates a validation (SRC-ELM, TGT-ELM, COMMENT, CCID, EXIT-2, SYNC,
JUMP, or SIGNOUT) resulted in (NO, WARNING, CAUTION, or ERROR) messages. Another
message is issued with the error reason.
Action:
None.
EWS Messages
EWS Messages
The following EWS messages are generated by the Web Services component. These
error messages can indicate coding issues with client programs that use Web Services,
or they can indicate Web Services internal errors. If you need additional information or
assistance with these messages, contact CA Technical Support.
EWS0100E
LIST ELEMENT | DATA dataOption | SCL keywords required for objectName operation
EWS0101E
Errors were detected during the Web Service validation, see the Web Service report.
EWS0101I
Endevor Web Services information
EWS0102E
Errors were detected during SCL statement conversion to API request, see the Web
Service report.
EWS0103E
SCL ACTION action NOT SUPPORTED BY WEB SERVICE.
EWS0104E
SCL ACTION action IS NOT IDENTIFIED.
EWS0105E
SCL ACTION action SUBMITTED WITH AN INCORRECT CATEGORY.
EWS0106E
Cannot open schema file in schemaFilePath
EWS0107E
Invalid pool size defined for dataSourceName
EWS0108I
Please consider updating the data source dataSourceName to take advantage of the
STC Pool
EWS Messages
EWS0109I
Please note that the updated dataSource dataSourceName operates without STC Pool
EWS0110E
Errors were detected during the Type identification, no Types found to match criteria
EWS0111E
Errors were detected during the Type identification
EWS0112E
the File extension does not match the Type FILEEXT property
EWS0120E
The DataSource property of the LoginProperty object must be specified.
EWS Messages
EWS0121E
The UserId property of the LoginProperty object must be specified.
EWS0122E
The Password property of the LoginProperty object must be specified.
EWS0130E
A well formatted SCL command is expected in the statement property of the SCL
object
EWS0131E
A well formatted attributes string is expected in the wsParameters property of the SCL
object
EWS0132E
Invalid SCL command, LISt objectName expected
EWS0133E
SCL OPTions NOCsv or NOTitle, for LISt objectName not supported
EWS0134E
A well formatted attributes string is expected in the wsParameters property of the SCL
object
EWS0135E
WsParameters property validation error (message)
EWS0136E
SCL contains invalid double quoted literal
EWS Messages
EWS0137E
SCL contains invalid single quoted literal
EWS0138E
Category="C" is expected to be coded in the wsParameters property
EWS0139E
The SCL statement contains a non-authorized character, found: "character"
EWS0201E
The data source datasource is not recorded due to the following errors:
parserErrorMessage
statement
OR
The data source dataSource is not recorded due to the following errors:
parserErrorMessage
_dataSourceContents
OR
The data source dataSource is not recorded dataSource
OR
The data source dataSource is not recorded statement
OR
The data source dataSource is not updated statement
EWS0203E
The data source is not accessible yet, please consult your administrator
EWS0204E
Message
EWS Messages
EWS0205E
The data source does not exist
EWS0206E
The data source document is invalid
EWS0207E
Please code Category attribute
EWS0208E
The data source dataSource is not recorded
dataSourceContents
EWS0209E
shortage of free STC resources, try later ...
EWS0301E
no monitor Actions identified for _dataSourceName dataSource
EWS0302E
dataSource _dataSourceName not found
EWS0303E
possible Buffer corruption for _dataSourceName
EWS0304E
see MONITOR ddname for monitor Actions identified for _dataSourceName
dataSource
EWS Messages
EWS0401E
REQUEST DATA OUTPUT fetchResponse PROCESSING IN ERROR rc
EWS0402E
REQUEST DATA OUTPUT getSCLDataBuffer PROCESSING IN ERROR 6002
EWS0403E
REQUEST DATA OUTPUT readResponse PROCESSING IN ERROR 7002
EWS0404E
REQUEST DATA OUTPUT writeSCLData PROCESSING IN ERROR rc
EWS0405E
REQUEST APIMSGS fetchResponse PROCESSING IN ERROR rc
EWS0406E
REQUEST APIMSGS getSCLDataBuffer PROCESSING IN ERROR 6003
EWS0407E
REQUEST APIMSGS readResponse PROCESSING IN ERROR 7003
EWS0408E
REQUEST APIMSGS writeSCLData PROCESSING IN ERROR rc
EWS0409E
REQUEST CMDMSGS fetchResponse PROCESSING IN ERROR rc
EWS0410E
REQUEST CMDMSGS getSCLDataBuffer PROCESSING IN ERROR 6004
EWS0411E
REQUEST CMDMSGS readResponse PROCESSING IN ERROR 7004
EWS0412E
REQUEST CMDMSGS writeSCLData PROCESSING IN ERROR rc
EWS Messages
EWS0413E
REQUEST C1MSGS fetchResponse PROCESSING IN ERROR rc
EWS0414E
REQUEST C1MSGS getSCLDataBuffer PROCESSING IN ERROR 6005
EWS0415E
REQUEST CMDMSGS readResponse PROCESSING IN ERROR 7005
EWS0416E
REQUEST C1MSGS writeSCLData PROCESSING IN ERROR rc
EWS0417E
REQUEST C1MSGSA fetchResponse PROCESSING IN ERROR rc
EWS0418E
REQUEST C1MSGSA getSCLDataBuffer PROCESSING IN ERROR 6006
EWS0419E
REQUEST CMDMSGSA readResponse PROCESSING IN ERROR 7006
EWS0420E
REQUEST C1MSGSA writeSCLData PROCESSING IN ERROR rc
EWS0421E
DataHandler Internal Error, please consult your System Administrator
EWS0422E
Communication Error, CciWebsapi internal code : rc "mes
PRC=PrcCode SRC=SrcCode DRC=DrcCode
Jobname=serverJobName ServerId=EndevorServerId
CCIMES=ReturnCodeText
FPVL Messages
FPVL Messages
This section details messages generated by footprint validation in the course of
processing. It also describes the possible causes and corrective actions to take in error
situations.
FPVL001E
INPUT COMPONENT VALIDATION ERROR HAS OCCURRED FOR
Reason:
The input component validation processing has detected an error.
Action:
Review the other validation messages for details.
FPVL001W
INPUT COMPONENT VALIDATION ERROR HAS OCCURRED FOR
Reason:
The input component validation processing has detected an error.
Action:
FPVL002E
NO MCF RECORD FOUND FOR
Reason:
CA Endevor SCM has found no Master Control File records that match the element
name in the footprint.
Action:
FPVL Messages
FPVL003E
FOOTPRINT MISMATCH FOR
Reason:
No Master Control File records for the element match the location and event
information in the footprint.
Action:
FPVL004E
INPUT COMPONENT WAS FOUND IN A STAGE PRIOR TO THIS ELEMENT'S ENV/STG
LOCATION
Reason:
Another copy of this component exists at an inventory location prior to the current
stage. This indicates someone may be making changes to this component.
Action:
None. Make sure the changes are unrelated to your changes.
FPVL004W
INPUT COMPONENT WAS FOUND IN A STAGE PRIOR TO THIS ELEMENT'S ENV/STG
LOCATION
Reason:
Another copy of this component exists at an inventory location prior to the current
stage. This indicates someone may be making changes to this component.
Action:
None. Make sure the changes are unrelated to your changes.
FPVL Messages
FPVL005E
LAST LEVEL DATE/TIME MISMATCH FOR
Reason:
The last level date and time information on the footprint do not match the date and
time information from the Master Control File.
Action:
FPVL006E
FOOTPRINT ENVIRONMENT STAGE NOT FOUND FOR
Reason:
CA Endevor SCM cannot find the environment and stage named in the footprint.
Action:
FPVL007E
FOOTPRINT ENVIRONMENT STAGE NOT IN ENVIRONMENT MAP FOR
Reason:
The input component validation processing has detected an error. The environment and
stage names found in the footprint do not exist in the current C1DEFLTS table.
Action:
FPVL Messages
FPVL007W
FOOTPRINT ENVIRONMENT STAGE NOT IN ENVIRONMENT MAP FOR
Reason:
In the first case the environment and stage referenced in the footprint are not on the
map route where the element currently resides. In the second case the package
component validation function has found an explicit component match, but system,
subsystem, or type names change across map locations, so a more recent version of the
component may exist at an intermediate stage.
Action:
In the first case, contact your administrator to determine if the footprint environment
and stage are on another map. In the second case, check intermediate stages for the
presence of the component. If you find the component, regenerate the element
containing the component to pick up the more recent version.
FPVL008E
FPVL008W
THIS ELEMENT DOES NOT USE THE FIRST FOUND COPY OF THE FOLLOWING
COMPONENT:
Reason:
The footprint of the component that was used matches a component located in the
map, but there is another copy of this component in a prior location of the map that
should have been used instead.
Action:
Recompile the program to use the first copy of the component that is found in the map.
FPVL013E
FPVLDS.FPVHDR IS NOT IN SYNC
Reason:
Internal error. The header of the footprint validation block is invalid.
Action:
FUPD Messages
FPVL014E
PROCESSOR FAILED FLAG IS SET. INPUT COMPONENT MUST BE RE-GENERATED.
Reason:
The processor failed flag is set for this component. This flag is set when the Generate or
Move processor associated with this element fails, or if the NO GENERATE action option
was enabled when the element was added or updated.
Action:
Regenerate this element, and use the ACM query facility to determine where this
element is used. Regenerate each of the parent elements.
FPVL014W
PROCESSOR FAILED FLAG IS SET. INPUT COMPONENT MUST BE RE-GENERATED.
Reason:
An element is moved up the map and one of its components was either not generated
or its Generate processor has failed. Action completes.
Action:
Verify this element's components and take appropriate action, if necessary.
FUPD Messages
This chapter details messages generated by the IEBUPDTE program along with possible
FUPD001I
BEGINNING EXECUTION... SEQUENCE NUMBERS BEGINNING IN COLUMN column
number FOR A LENGTH OF number of columns WILL BE USED
Reason:
This is an informational message that gives you the starting column and length used in
this run.
Action:
None. Information was derived from the IEBUPDTE control statement you specified. If
not specified, the defaults are a start column of 73 and a length of 7.
FUPD Messages
FUPD002E
INVALID PARM: parm
Reason:
The parm information provided on the execute statement is invalid.
Action:
For detailed coding instructions, see the Utilities Guide.
FUPD003E
UNABLE TO CONTINUE - OPEN FOR DDNAME ddname FAILED
Reason:
An attempt to open the file associated with the DDNAME statement listed in the
message failed.
Action:
Check the JCL to make sure that the DD statement is correct. The error may be related
to DSN, UNIT, DISP, or VOL=SER information.
FUPD004E
UNABLE TO CONTINUE - THE NAME= SUBPRAMETER WAS NOT SPECIFIED ON THE
PARM STATEMENT
Reason:
If the standalone compare program was used to create the input file, the NAME=
subparameter must be specified on the parm.
Action:
Add this subparameter to the parm.
FUPD Messages
FUPD005E
UNABLE TO CONTINUE - THE NAME=SUBPARAMETER IS NOT ALLOWED IF THE INPUT
IS FROM SCL
Reason:
If the print action was used to create the input file, the NAME=subparameter cannot be
specified on the parm.
Action:
Remove this subparameter from the parm.
FUPD006E
THE RECORD LENGTH OF THE INPUT FILE [C1CHGSI] IS INVALID
Reason:
If the print action was used to create the input file, the record length of the file must be
133. If the standalone Compare program was used to create the input file, the record
length must be 88. Note that the NAME=subparameter of the parm statement is only
allowed if the input file was created by the standalone Compare program.
Action:
Check the DCB attributes of the input file.
FUPD010I
ELEMENT element name VERSION vvll SELECTED
Reason:
This informational message identifies the element being used in this run.
Action:
None.
FUPD011I
ENV environment SYS system SUBSYS subsystem TYPE type STAGE stage
Reason:
This informational message identifies the information used in this run.
Action:
None.
FUPD Messages
FUPD012I
input record
Reason:
Use the information supplied by this message in conjunction with message FUPD012E to
help identify the record from the input file that is causing the error.
Action:
Regenerate the input file.
FUPD012E
SKIPPING TO NEXT ELEMENT... SEQUENCE NUMBER ERROR - sequence number
Reason:
An out of sequence error was detected in the input file (C1CHGSI). Blank sequence
numbers are not allowed.
Action:
Regenerate the input file.
FUPD014I
IEBUPDTE number of statements CNTL CARDS SUCCESSFULLY GENERATED
Reason:
This informational message indicates the number of control statements created by the
control statement generator.
Action:
None.
FUPD015I
END EXECUTION - number of elements ELEMENT(S) SELECTED, IEBUPDTE CNTL CARDS
HAVE BEEN GENERATED FOR number of elements ELEMENT(S)
Reason:
This informational message indicates the results of the execution run.
Action:
None
IMGR Messages
IMGR Messages
This section details messages generated by inventory management functions along with
possible causes and corrective actions to take in error situations.
Note: The following messages, which indicate that no match is found and are
documented in this section with an E suffix, can also appear with a W suffix: IMGR001W,
IMGR005W, IMGR007W,IMGR009W, IMGR011W, and IMGR013W.
IMGR001E
NO ENVIRONMENTS MATCH environment name OR USER NOT AUTHORIZED TO USE
THIS ENV
Reason:
Either the environment specified on the request does not exist, or the user making the
request is not authorized to access the named environment.
Action:
Make sure that the environment was specified correctly. See your administrator if
necessary to obtain access privileges.
IMGR002E
NO MAP INFO AVAILABLE WITH SEARCH=search type ON ENVIRON environment name
STAGE stage id
Reason:
The environment and stage named in the message are not mapped to a subsequent
environment or stage location.
Action:
IMGR Messages
IMGR003E
"TO" LOCATION environment name/stage id IS INVALID FROM environment
name/stage id
Reason:
The second environment name/stage pair named in the message is not a valid target
location for the requested action.
Action:
Correct and resubmit the request, or see your administrator.
IMGR004E
environment name IS AN INVALID "TO" ENVIRONMENT FROM environment name
Reason:
The second environment named in the message is not a valid target environment for the
first named environment.
Action:
Correct and resubmit the request, or see your administrator.
IMGR005E
NO SYSTEMS MATCH system name IN ENVIRONMENT environment name
Reason:
The system named in the message has not been defined to the environment named in
the message.
Action:
Make sure that the system and environment names were specified correctly.
IMGR Messages
IMGR006E
UNKNOWN PROCESSOR TYPE processor type
Reason:
CA Endevor SCM does not recognize the processor type identified in the message.
Action:
Specify the processor type correctly.
IMGR007E
NO SUBSYSTEMS MATCH subsystem name IN SYSTEM system name
Reason:
The subsystem named in the message was not defined to the system named in the
message.
Action:
Make sure that the subsystem and system names were specified correctly.
IMGR008E
NO SYMBOLICS FOR [GENERATE/DELETE/MOVE] PROCESSOR processor group name IN
SYSTEM system name - STAGE stage id
Reason:
No symbolics were defined for the processor named in the message at the system and
stage identified in the message.
Action:
Define the symbolics used in the processor to CA Endevor SCM, and resubmit the job.
IMGR Messages
IMGR009E
NO ELEMENT MATCH(ES) FOUND AT SPECIFIED LOCATION
Reason:
The element is not associated with the type at the specified stage.
Action:
Make sure that you have specified the element name correctly.
IMGR009W
NO ELEMENT MATCH(ES) FOUND AT SPECIFIED LOCATION
Reason:
Informational message. No elements were found that matched the criteria specified.
Action:
None.
IMGR011E
NO STAGES MATCH stage id IN ENVIRONMENT environment name
Reason:
The stage ID in the message is not associated with the environment named in the
message.
Action:
Make sure that the stage and environment names were specified correctly.
IMGR Messages
IMGR012E
NO PROCESSOR GROUP MATCH group name FOR TYPE type name IN SYSTEM system
name - STAGE stage id
Reason:
The processor group named in the message is not defined for the type named in the
message at the system/stage identified in the message.
Action:
Make sure that you have specified the processor group name correctly.
IMGR013E
NO TYPES MATCH type name IN SYSTEM system name - STAGE stage id
Reason:
The type named in the message is not defined to the system/stage identified in the
message.
Action:
Make sure that you have specified the type name correctly.
IMGR014E
NO TYPE ID MATCH id number IN SYSTEM system name - STAGE stage id
Reason:
The type ID named in the message is not defined to the system/stage identified in the
message.
Action:
IMGR Messages
IMGR015E
NO DATA SETS MATCH data set key IN SYSTEM system name - STAGE stage id
Reason:
Internal error.
Action:
IMGR016E
TYPE SEQUENCE RECORD NOT DEFINED FOR SYSTEM system name - STAGE stage id
Reason:
No type sequence record was defined for the system and stage named in the message.
Action:
Define a type sequence record.
IMGR017E
field name NAME CONTAINS INVALID SYNTAX (OR INVALID FOR THE FUNCTION)
Reason:
The field named in the message contains invalid syntax.
Action:
Correct the syntax.
IMGR Messages
IMGR018E
NO APPROVER GROUPS MATCH approver group name IN ENVIRONMENT environment
name
Reason:
The approver group named in the message is not defined to the environment named in
the message.
Action:
Make sure that you have specified the approver group name correctly. Define the
approver group if necessary.
IMGR019E
NO GROUP JUNCTIONS MATCH approver group relationship IN ENVIRONMENT
environment name
Reason:
The approver group relationship named in the message is not defined to the
environment named in the message.
Action:
Make sure that you have specified the approver group relationship correctly. Define the
approver group relationship if necessary.
IMGR020E
NEXT LOCATION NOT FOUND FROM ENV environment name STG stage id
Reason:
There is no "next" location on the map for the named environment and stage.
Action:
IMGR Messages
IMGR021E
NEXT SYSTEM LOCATION NOT FOUND FROM ENV environment name STG stage id SYS
system name
Reason:
There is no "next" location on the map for the named environment, stage, and system.
Action:
IMGR022E
NEXT SUBSYSTEM LOCATION NOT FOUND FROM ENV environment name STG stage id
SYS system name SBS subsystem name
Reason:
There is no "next" location on the map for the named environment, stage, system, and
subsystem.
Action:
IMGR023E
NEXT TYPE LOCATION NOT FOUND FROM ENV environment name STG stage id SYS
system name TYPE type name
Reason:
type name.
Action:
IMGR Messages
IMGR024E
NO ELEMENTS FOUND AFTER ENV environment name STG stage id SYS system name
SBS subsystem name TYPE type name
Reason:
CA Endevor SCM found no elements at any map location, beginning from and including
the named location.
Action:
IMGR025E
NO NEXT ENVIRONMENT IN MAP. FROM ENV is environment name
Reason:
The named environment is not mapped to another environment in the C1DEFLTS table.
Action:
IMGR026E
NEXT TYPE LOCATION NOT FOUND FROM ENV environment name STG stage id SYS
system name TYPE ID type id
Reason:
type ID.
Action:
IMGR Messages
IMGR031E
SYS system name ROUTE INCOMPLETE BTWN environment 1/stage id 1
environment 2/stage id 2
Reason:
The named system is not mapped to a system at the indicated target location.
Action:
IMGR032E
SBS sub-system name ROUTE INCOMPLETE UNDER SYS system name BTWN
environment 1/stage id 1 environment 2/stage id 2
Reason:
The named subsystem is not mapped to a subsystem at the indicated target location.
Action:
IMGR033E
TYPE type name ROUTE INCOMPLETE UNDER SYS system name BTWN environment
1/stage id 1 environment 2/stage id 2
Reason:
The named type is not mapped to a type at the indicated target location.
Action:
IMGR Messages
IMGR034E
PRG processor group name ROUTE INCOMPLETE UNDER SYS system name TYP type
name BTWN environment 1/stage id 1 environment 2/stage id 2
Reason:
The named processor group is not mapped to a processor group at the indicated target
location.
Action:
IMGR100E
RC=return code - reason code ALLOCATION ERROR ddname - data set name
Reason:
Internal error.
Action:
IMGR101E
RC=return code VSAM READ ERROR - ON DDNAME ddname
Reason:
Internal error.
Action:
IMGR Messages
IMGR200E
ENVIRONMENT environment name STAGE stage-name LOCATION INVALID.
Reason:
The request has been cancelled because unknown environment stage location was
specified on request.
Action:
See accompanying error messages for a resolution.
IMGR201E
VSAM I/O ERROR ON IMR FUNCTION AGAINST DDNAME ddname, RC= return code
FEEDBK= feedback code
Reason:
An I/O error occurred against the MCF file. The ddname in the above statement
identifies the file. The VSAM return and feedback codes are also supplied on the
message.
Action:
See the appropriate IBM VSAM manual first. Have all output available, for example JES
spool files and dump information, before calling your administrator.
IMGR202E
CONSTRUCTION OF TAGGED FIELD OBJECT FAILED DURING BC1PIMGU INITIALIZATION
Reason:
Internal error. An error occurred while calling internal OBJECT initialization routines
during BC1PIMGU initialization.
Action:
Resolve any accompanying error messages first. Gather related output, for example, JES
spool file, logs, and dumps, before calling your administrator.
IMGR Messages
IMGR203E
SYSTEM system name ALREADY DEFINED IN ENV environment name STAGE ID stage id
Reason:
The request to create a system definition failed because the system record is already
defined.
Action:
IMGR204E
FIELD MAPPING BLOCKS COULD NOT BE BUILT DURING
[junction/approvers/procgroup/subsystem/system/type]
Reason:
Internal error. BC1PIMGU called an internal OBJECT routine to create an FMB structure.
This routine failed to process the request.
Action:
IMGR205E
TDF FIELD CODE X "error code" INVALID DURING
[system/subsystem/type/appr_grp/appr_jun/proc_grp/proc_sym/data set]
[create/delete/read/update]
Reason:
Internal error. Invalid tagged field code.
Action:
IMGR Messages
IMGR206E
TDF FIELD CODE X "error code" MISSING DURING
Reason:
Internal error. A required field was missing from the TFC chain.
Action:
IMGR207E
TDF FIELD CODE X "error code" IS NOT APPLICABLE DURING
Reason:
Internal error. Invalid tagged field code for this request.
Action:
IMGR208E
TDF FIELD CODE X "error code" DUPLICATED DURING
Reason:
Internal error. A duplicate field code was encountered on the TFC chain.
Action:
IMGR Messages
IMGR209E
TDF FIELD CODE X "error code" EXCEEDED ITS OCCURRENCE DURING
Reason:
Internal error. An occurring field code exceeded its maximum on the TFC chain.
Action:
IMGR210E
SYSTEM system name DOES NOT EXIST IN ENV environment name STAGE ID stage id
Reason:
Request fails. System definition must exist for this environment/stage location.
Action:
IMGR211E
TYPE RECORDS EXIST FOR SYSTEM system name IN ENV environment name STAGE ID
stage id
Reason:
Request fails. Type definition records must not exist for this system at this
environment/stage location.
Action:
IMGR Messages
IMGR212E
SUBSYSTEM RECORDS EXIST FOR SYSTEM system name IN ENV environment name
STAGE ID stage id
Reason:
Request fails. Subsystem records must not exist for this system at this
Action:
IMGR213E
SUBSYSTEM subsystem name EXISTS FOR SYSTEM system name IN ENV environment
name STAGE ID stage id
Reason:
Request fails. This subsystem must not exist under this system at this
Action:
IMGR214E
SUBSYSTEM subsystem name DOES NOT EXIST FOR SYSTEM system name IN ENV
environment name STAGE ID stage id
Reason:
Request fails. Subsystem must exist for this system at this environment/stage location.
Action:
IMGR Messages
IMGR215E
ELEMENTS EXIST FOR SYSTEM system name SUBSYSTEM subsystem name IN ENV
Reason:
Request fails. For this request, elements must not exist for this system/subsystem at this
Action:
IMGR216E
SYSTEM system name WAS NOT UPDATED DURING INVENTORY CHANGE ON DDNAME
ddname, RC= return code FEEDBK= feedback code
Reason:
VSAM I/O error occurred while updating the system record timestamp field. This user
request most likely completed. The user must resolve the problem which caused the
system record update to fail.
Action:
See the appropriate IBM VSAM manual first. Have all output available, for example, JES
IMGR217E
TYPE type name ALREADY EXISTS FOR SYSTEM system name IN ENV environment
Reason:
Request fails. Type already defined for this system under this environment/stage
location.
Action:
IMGR Messages
IMGR218E
TYPE SEQUENCE RECORD FOR SYSTEM system name IN ENV environment name STAGE
ID stage id NOT FOUND
Reason:
The type sequence record is always created at the time the system record is defined.
This request fails when this condition occurs. Try deleting the system record, and if this
is possible, recreate it.
Action:
IMGR219E
MAXIMUM OF 256 TYPE RECORDS ALREADY DEFINED FOR SYSTEM system name IN
ENV environment name STAGE ID stage id
Reason:
Request fails. This is an internal limitation. Only 256 type definition records may exist
per system.
Action:
IMGR220E
TYPE SEQUENCE SLOT FOR SYSTEM system, DESIGNATED FOR TYPE type name
UPDATE, CONTAINED INVALID DATA
Reason:
Request fails. Invalid data was found within the type sequence record where the type ID
slot was assigned for the type during a create type request.
Action:
IMGR Messages
IMGR221E
MAXIMUM OF 256 DATA SETS ALREADY DEFINED FOR SYSTEM system IN ENV
Reason:
Request fails. This is an internal limitation. Only 256 data sets may be defined per
system.
Action:
IMGR222E
TYPE type name NOT DEFINED FOR SYSTEM system name IN ENV environment name
STAGE ID stage id
Reason:
Request fails. The type definition must exist for this system under this
Action:
IMGR223E
processor name PROCESSOR RECORD WRITE FAILURE ON DDNAME ddname, RC=
return code FEEDBK= feedback code
Reason:
VSAM I/O error occurred while writing this processor record to the MCF which is
identified by the DDname value in the above message. The VSAM return code and
feedback values are returned.
Action:
See the appropriate IBM VSAM manual first. Have all output available, for example, JES
IMGR Messages
IMGR224E
ELEMENTS EXIST FOR SYSTEM system name TYPE type name IN ENV environment
Reason:
Request fails. Elements must not exist for this system and type under this
Action:
IMGR225E
TYPE SEQUENCE SLOT FOR SYSTEM system name, DESIGNATED FOR TYPE type name,
WAS NOT FOUND
Reason:
Request fails. During a delete type request, the type sequence record did not contain
the type record id.
Action:
IMGR226E
STAGE 1 INFORMATION ACCESS FOR ENVIRONMENT environment name FAILED WITH
A NOTFOUND CONDITION
Reason:
Stage 1 of this location could not be located. If this message occurs during a delete type
request, the action is incomplete. The junction record deletion logic is not done and the
system record timestamp update count logic is also not done.
Action:
IMGR Messages
IMGR227E
APPROVER JUNCTION INVENTORY NOT ON MCF FOR ENV environment name
Reason:
Request fails. The approver junction inventory for this environment was not defined on
the MCF.
Action:
IMGR228E
APPROVER GROUP approver group name NOT DEFINED FOR JUNCTION INVENTORY IN
ENV environment name
Reason:
Request fails. A junction record with this approver group was not defined on the MCF.
Action:
IMGR229E
JUNCTION FOR APPROVER GROUP ALREADY DEFINED IN ENV environment name
Reason:
Request fails. The junction inventory definition was already defined for the requested
approver group.
Action:
IMGR Messages
IMGR230E
MAXIMUM OF 256 JUNCTION RECORDS FOR THE SAME INVENTORY IS ALREADY
DEFINED
Reason:
Request fails. This is an internal limitation. Only 256 junction definitions having the same
inventory may be defined per environment.
Action:
IMGR231E
APPROVER GROUP approver group name NOT DEFINED FOR ENVIRONMENT
environment name
Reason:
Request fails. The specified approver group is not defined for this environment.
Action:
IMGR232E
APPROVER GROUP approver group name ALREADY DEFINED FOR ENVIRONMENT
environment name
Reason:
Request fails. The specified approver group is already defined for this environment.
Action:
IMGR Messages
IMGR233E
TYPE SEQUENCE NOT DEFINED FOR SYSTEM system name IN ENV environment name
STAGE ID stage id
Reason:
Request fails. During a type sequence update or read request, the type sequence record
was not found for this system under this environment/stage location.
Action:
IMGR234E
TFC COULD NOT BE BUILT DURING symbols/typeseq read
Reason:
Internal error. BC1PIMGU called an internal OBJECT routine to create a tagged field
collection block (TFC). This routine failed to process the request.
Action:
IMGR235E
TDF COULD NOT BE BUILT DURING symbols/typeseq read
Reason:
Internal error. BC1PIMGU called an internal OBJECT routine to create a tagged data field
block (TDF). This routine failed to process the request.
Action:
IMGR Messages
IMGR236E
NO TYPES WERE FOUND FOR SYSTEM system name IN ENV environment name STAGE
ID stage id
Reason:
Request fails. During a type sequence update request, no type records were found for
this system. The requester type count indicated that type records should be defined for
this system under this environment/stage location.
Action:
IMGR237E
PROCESSOR GROUP processor group name ALREADY DEFINED FOR SYSTEM system
name TYPE type name
Reason:
Request fails. The processor group is already defined for this system and type.
Action:
IMGR238E
PROCESSOR GROUP processor group name NOT DEFINED FOR SYSTEM system name
TYPE type name
Reason:
Request fails. The specified processor group is not defined for the system and type.
Action:
IMGR Messages
IMGR239E
ELEMENTS EXIST WHICH USE PROCESSOR GROUP processor group name
Reason:
Request fails. Elements still exist that use this processor group.
Action:
IMGR240E
UNKNOWN PROCESSOR TYPE X "processor type value" FROM CALLER
Reason:
Request fails. The caller specified an invalid processor type. The processor type should
be one of the following: x&rq.01&rq., x&rq.02&rq. or x&rq.03&rq..
Action:
IMGR241E
NO MATCHING DATA FOR SYMBOL symbol name IN TDF CHAIN.
Reason:
Request fails. Caller did not provide override data for the symbolic name anywhere in
the tagged data field (TDF) chain.
Action:
IMGR Messages
IMGR242E
PROCESSOR NAME WITHIN THE TDF CHAIN IS NOT DEFINED WITHIN GROUP group
name
Reason:
Request fails. The Processor name specified within the caller tagged data field (TDF)
chain is not defined within this processor group.
Action:
IMGR243E
REQUIRED TDF ENTRY entry name MISSING FROM CHAIN
Reason:
Request fails. The caller failed to include this required tagged data field (TDF) entry
within the TFC chain.
Action:
IMGR244E
CATALOGUE SEGMENT WAS NOT FOUND FOR ELEMENT TYPE
Reason:
The catalogue segment does not exist for this element or type.
Action:
IMGR Messages
IMGR245E
NO MATCH IN MCF DDN ddname FOR CATAL ENTRY: catalog-key
Reason:
Internal error. Sync error between the master control file and the catalog.
Action:
IMGR246E
CATALOGUE SEGMENT ALREADY EXISTS FOR ELEMENT TYPE
Reason:
The catalogue segment already exists for this element or type.
Action:
IMGR247E
$IMR REQUEST FAILED, $IMR ERROR MESSAGE FOLLOWS
Reason:
Internal error. The $IMR request failed. Review the other messages to determine the
reason.
Action:
IMGR Messages
IMGR248I
ELEMENT ENTRY FOR LOCATION ALREADY EXISTS, A CATALOGUE UPDATE WILL BE
PERFORMED
Reason:
Informational message. A catalogue entry already exists for this element or type. The
entry will be updated.
Action:
None.
IMGR249I
ELEMENT ENTRY FOR LOCATION DOES NOT EXIST, A CATALOGUE ADD WILL BE
PERFORMED
Reason:
Informational message. A catalogue entry does not exist for this element or type. The
entry will be created.
Action:
None.
IMGR250E
SECOND ATTEMPT TO RECORD IN CATALOGUE FAILED: inventory location
Reason:
A previous Update action failed with a segment not found condition. An Add action with
Update was attempted, which also failed.
Action:
IMGR Messages
IMGR251E
LOOP DETECTED WHILE TRYING TO GENERATE AN ALIAS ELEMENT NAME
Reason:
CA Endevor SCM generated an alias for an element. The alias already exists as an
element.
Action:
IMGR252E
INVALID CATALOGUE RECORDS FOUND FOR THIS ELEMENT
Reason:
Internal error. A catalogue record exists for this element or type, but the data found in
the record is invalid.
Action:
IMGR253E
SEGMENT FOUND WITH INVALID INVENTORY inventory location
Reason:
An invalid catalog segment was found for this element.
Action:
IMGR Messages
IMGR254E
SEGMENT FOUND WITH INVALID ENVIRONMENT environment name SYSTEM system
name
Reason:
An invalid catalog segment was found for this element.
Action:
IMGR255C
REG. ERROR: ELM EXISTS W/SAME PROC GRP O/P TYPE (processor group output type)
AT LOC environment/stage - system/subsystem/type
Reason:
Registration error. A duplicate element was found within the same processor group
output type. This is a caution message and processing continues.
Action:
None.
IMGR255E
Reason:
output type.
Action:
Duplicates are not allowed. Change the element name or processor group output type.
IMGR Messages
IMGR255W
Reason:
output type. This is a warning message and processing continues.
Action:
None.
IMGR256E
PROCESSOR GROUP xx FOR ENV environment STG stage SYS system TYPE type DOES
NOT EXIST
Reason:
This processor group does not exist within this inventory location.
Action:
Verify that the processor group name is correct. If so, make sure the processor group is
properly defined.
IMGR257C
REG. ERROR: ELEMENT NAME ALREADY EXISTS AT environment/stage system/subsystem
Reason:
Registration error. A duplicate element was found in a non-mapped location. This
caution message is issued and processing continues.
Action:
None.
IMGR Messages
IMGR257E
Reason:
Registration error. A duplicate element found in a non-mapped location.
Action:
Duplicates are not allowed. Change the element name.
IMGR257W
Reason:
Registration error. A duplicate element was found in a non-mapped location. This
warning message is issued and processing continues.
Action:
None.
IMGR258E
ELM EXTENSION RECORD element extension record key NOT FOUND IN ENV env STGID
stage id
Reason:
An element extension record was not found within this directory location.
Action:
IMGR Messages
IMGR259E
REQUIRED ELEMENT RECORD PARAMETER MISSING FROM ELEMENT EXTENSION
QUERY CALL
Reason:
The parameter list passed to the element extension subroutine must contain the
address of the element record. This parameter is invalid.
Action:
IMGR260E
INVALID EXTENSION DATA FOUND IN ELEMENT AT inventory location
Reason:
An element extension record was found, but the data is invalid.
Action:
IMGR261E
INVALID EXTENSION TYPE PARAMETER SPECIFIED ON THE ELEMENT EXTENSION CALL
Reason:
Internal error. The first parameter on the call to the element extension subroutine is the
extension type. The value specified is invalid.
Action:
IMGR Messages
IMGR900E
TRUNC OCCURRED WHILE MOVING RECORD TYPE type id TO BUFFER - CALL ENDEVOR
TECHNICAL SUPPORT
Reason:
An internal error occurred.
Action:
IMGR901E
INVALID PARAMETER LIST RECEIVED - CALL ENDEVOR TECHNICAL SUPPORT
Reason:
Action:
IMGR902E
STORAGE UNAVAILABLE TO PROCESS REQUEST - CALL ENDEVOR TECHNICAL SUPPORT
Reason:
Action:
JLOG Messages
JLOG Messages
This section details CA Endevor SCM messages generated in the course of PITR
JLOG001S
BC1PJLOG - UNSUPPORTED CALL FUNCTION = function number
Reason:
Internal error. The JLOGFUNC contained an unsupported value.
Action:
JLOG002S
BC1PJLOG - MAIN(DFLTRUTN) - UNSUPPORTED RETURN CODE= return code
Reason:
Internal error. DFLRUTN resulted in an invalid return code.
Action:
JLOG003S
BC1PJLOG - ENVIRONMENT environment name NOT FOUND IN C1DEFLTS
Reason:
The named environment is not defined in the C1DEFLTS table.
Action:
JLOG004S
BC1PJLOG - STAGE stage name NOT VALID FOR ENVIRONMENT environment name
Reason:
The named environment exists, but the named stage is not defined to that environment.
Action:
JLOG Messages
JLOG005S
BC1PJLOG - DATA SET WAS IDENTIFIED AS AN ENV OR PKGDATA SET, BUT WAS NOT
FOUND IN THE DEFAULTS TBL
Reason:
The named data set was identified as a valid environment or package data set, but is not
defined in the C1DEFLTS table.
Action:
JLOG006E
BC1PJLOG - ACTNRUTN - TRANSACTION LEFT ACTIVE, TERMINATING
Reason:
Internal error. An abend has probably occurred, bypassing normal cleanup of an action
or a package request. Automatic cleanup will terminate the transaction.
Action:
None.
JLOG007S
BC1PJLOG - ACTNRUTN - INVALID REQUEST (request code)
Reason:
Internal error. An internal call to ACTNRUTN supplied an invalid request code.
Action:
JLOG008S
BC1PJLOG - ACTNRUTN - ACTION TABLE SIZE EXCEEDED
Reason:
Internal error. The transaction table was designed with a limit of concurrent
transactions. This limit has been exceeded. For release 3.6, the maximum number of
valid transactions should be 2. The table holds 15.
Action:
JLOG Messages
JLOG009S
BC1PJLOG - BUFFRUTN - DATA BLOCK block size LARGER THAN I/O BUFFER buffer size
Reason:
Internal error. The constructed data block is larger than the maximum block size
allowed.
Action:
JLOG010E
BC1PJLOG - CLOSRUTN - ERROR CLOSING LSERV JOURNAL FILE file name-L-Serv name
(error code)
Reason:
An error was encountered when closing the named journal file. The CA L-Serv name is
the journal group ID associated with the file. The error code is the CA L-Serv error code.
This message should be followed by a JLOG061I-JLOG089I message explaining the error
code.
Action:
For an explanation of the error code, see the CA L-Serv documentation, and act
accordingly.
JLOG011E
BC1PJLOG - CLOSRUTN - ERROR TERMINATING LSERV SESSION FOR JOURNAL FILE file
name-L-Serv name (error code)
Reason:
An error was encountered when terminating the CA L-Serv session for the named
journal file. The CA L-Serv name is the group ID associated with the file. The error code
is the CA L-Serv error code. This message should be followed by a JLOG061I-JLOG089I
message explaining the error code.
Action:
For an explanation of the error code, see the CA L-Serv documentation, and act
accordingly.
JLOG Messages
JLOG012E
BC1PJLOG - CLOSRUTN - ERROR CLOSING SEQUENTIAL JOURNAL FILE file name (error
code)
Reason:
An error was encountered when closing the named sequential journal file. The error
code is a QIO hex error code.
Action:
JLOG013S
BC1PJLOG - LOCJRUTN - UNABLE TO ACQUIRE STORAGE FOR JOURNAL BLOCK, ERROR
= reason code
Reason:
An attempt to acquire JRNLDSCT main storage failed with the indicated reason code.
Action:
Increase the region size and try again.
JLOG014S
BC1PJLOG - LOCJRUTN - UNABLE TO ACQUIRE I/O BUFFER STORAGE, ERROR = reason
code
Reason:
An attempt to acquire QIO buffer storage failed, returning the named reason code.
Action:
JLOG015S
BC1PJLOG - NQDQRUTN - INVALID REQUEST (request code)
Reason:
Internal error. An internal call to NQDQRUTN supplied an invalid request code.
Action:
JLOG Messages
JLOG016S
BC1PJLOG - OPENRUTN - LSERV JOURNAL FILE file name-L-Serv name NOT AVAILABLE error code
Reason:
CA L-Serv must be active in order to access the named journal file, but is not available.
This message should be followed by a JLOG061I-JLOG089I message explaining the error
code.
Action:
Make sure that CA L-Serv is available, and retry the request.
JLOG017S
BC1PJLOG - OPENRUTN - GENCB FAILED FOR REQUIRED LSERV JOURNAL FILE file
name-L-Serv name, error code
Reason:
Internal error. The VSAM GENCB for the ACB failed for the named journal file and
journal group.
Action:
JLOG018S
BC1PJLOG - OPENRUTN - OPEN FAILED FOR REQUIRED LSERV JOURNAL FILE file
Reason:
An open request for the named journal file and CA L-Serv has failed. This message
should be followed by a JLOG061I-JLOG089I message explaining the error code.
Action:
For information about the error code, see the CA L-Serv documentation.
JLOG Messages
JLOG019S
BC1PJLOG - OPENRUTN - LSERV STATISTICS REQUEST FAILED FOR JOURNAL FILE file
Reason:
A CA L-Serv statistics request for the named journal file and CA L-Serv has failed with the
indicated return code.
Action:
JLOG020S
BC1PJLOG - OPENRUTN - REQUIRED SEQUENTIAL JOURNAL FILE file name NOT
AVAILABLE
Reason:
The DD statement for the named file is not present.
Action:
Add the requested DD statement.
JLOG021S
BC1PJLOG - OPENRUTN - OPEN FAILED FOR REQUIRED SEQUENTIAL JOURNAL FILE file
name, error code
Reason:
An error was encountered when opening the named sequential journal file. The error
code is a QIO error code.
Action:
JLOG Messages
JLOG022S
BC1PJLOG - OPENRUTN - LSERV JOURNAL FILE (file name-L-Serv name) MUST BE AN
ESDS VSAM FILE
Reason:
The named CA L-Serv has identified the named journal file as a non-ESS VSAM file.
Journal files must be ESDS VSAM files.
Action:
Reallocate the file as an ESDS file.
JLOG023S
BC1PJLOG - OPENRUTN - LSERV ERROR ISSUING "GETID" REQUEST FOR JOURNAL: file
name-L-Serv name (error code)
Reason:
A "GETID" request from the named CA L-Serv against the named journal file has failed,
returning the indicated error code.
Action:
JLOG024S
BC1PJLOG - STORRUTN - INVALID REQUEST (request code)
Reason:
Internal error. An internal call to STORRUTN supplied an invalid request code.
Action:
JLOG Messages
JLOG025S
BC1PJLOG - STORRUTN - UNABLE TO ACQUIRE STORAGE FOR JOURNAL CONTROL,
ERROR = error code
Reason:
An attempt to acquire main storage for LONGJLOG has failed with the indicated error
code.
Action:
JLOG026S
BC1PJLOG - STORRUTN - UNABLE TO INITIALIZE STORAGE FOR JOURNAL CONTROL,
ERROR = error code
Reason:
An attempt to acquire main storage for LONGPAGE has failed with the indicated error
code.
Action:
JLOG027S
BC1PJLOG - STORRUTN - ERROR RELEASING STORAGE, ERROR = error code
Reason:
An attempt to release main storage has failed with the indicated error code.
Action:
JLOG028S
BC1PJLOG - TASKRUTN - INVALID REQUEST (request code)
Reason:
Internal error. An internal call to TASKRUTN has failed with the indicated reason code.
Action:
JLOG Messages
JLOG029S
BC1PJLOG - TASKRUTN - INTERNAL TASK DOES NOT EXIST task code
Reason:
An attempt to locate the transaction block associated with the named task code has
failed.
Action:
JLOG030S
BC1PJLOG - STORRUTN - UNABLE TO ACQUIRE STORAGE FOR INTERNAL TASK
CONTROL, ERROR = error code
Reason:
An attempt to acquire TASKDSCT main storage has failed with the indicated error code.
Action:
Increase region size and try again.
JLOG031S
BC1PJLOG - WRITRUTN - I/O ERROR (error code) WRITING TO SEQUENTIAL JOURNAL
FILE (file name)
Reason:
An I/O error has occurred accessing the named file. The error code is a QIO error code.
Action:
JLOG032S
BC1PJLOG - OPENRUTN - UNABLE TO ACQUIRE SHARED STORAGE FOR SEQUENTIAL
FILE ANCHOR BLOCK, ERROR = error code
Reason:
An attempt to acquire JQIODSCT anchor storage in main storage has failed with the
indicated reason code.
Action:
JLOG Messages
JLOG033S
BC1PJLOG - OPENRUTN - UNABLE TO ACQUIRE SHARED STORAGE FOR SEQUENTIAL
FILE, ERROR = error code
Reason:
An attempt to acquire JQIODSCT anchor storage in main storage has failed with the
indicated reason code.
Action:
JLOG034S
BC1PJLOG - OPENRUTN - ATTEMPT TO ACCESS GROUP file name FAILED, FOUND
INDIVIDUAL DATA SET, NOT GROUP
Reason:
CA L-SERV has identified the named file as an individual VSAM data set, not as a
member of a journal group.
Action:
Check the CA L-SERV ADDFILE statement to make sure that the group name parameter
has been specified correctly.
JLOG035S
BC1PJLOG - OPENRUTN - ATTEMPT TO ACCESS GROUP file name FAILED, REQUIRED
OPTION "OUTPUT" IS MISSING
Reason:
CA L-SERV has identified the named file as a member of a group, but the required option
of OUTPUT was not specified for this group.
Action:
Correct the CA L-SERV ADDFILE statement.
JLOG Messages
JLOG036S
BC1PJLOG - OPENRUTN - ATTEMPT TO ACCESS GROUP group name FAILED, REQUIRED
MAXIMUM RECORD SIZE MUST BE 32640
Reason:
CA L-SERV identified the named file as a member of a group, but the file did not have
the required maximum record size of 32,640.
Action:
Check the journal data set allocations.
JLOG051E
BC1PJLOG - GETRPL - VSAM ERROR - JOURNAL file name-L-Serv name, MACRO macro
name
Reason:
A CA L-SERV check has failed for the named file under the named CA L-SERV. The macro
should be identified as CHECK. The accompanying JLOG059E message explains the error
code.
Action:
See the description of message JLOG059E.
JLOG052E
BC1PJLOG - OPENRUTN - VSAM ERROR - JOURNAL file name-L-Serv name, MACRO
macro name
Reason:
A VSAM GENCB RPL has failed for the named file under the named CA L-SERV. The
macro should be identified as GENCB. The accompanying JLOG059I message explains
the error code.
Action:
JLOG Messages
JLOG053E
BC1PJLOG - OPENRUTN - VSAM ERROR - JOURNAL file name-L-Serv name, MACRO
macro name
Reason:
A VSAM GENCB RPL WRTBFR has failed for the named file under the named CA L-SERV.
The macro should be identified as GENCB. The accompanying JLOG059I message
explains the error code.
Action:
JLOG054E
BC1PJLOG - SYNCRUTN - VSAM ERROR - JOURNAL file name-L-Serv name, MACRO
macro name
Reason:
An LSERV WRTBFR has failed for the named file under the named LSERV. The macro
should be identified as WRTBFR. The accompanying JLOG059I message explains the
error code.
Action:
JLOG055E
BC1PJLOG - WRITRUTN - VSAM ERROR - JOURNAL file name-L-Serv name, MACRO
macro name
Reason:
A MODCB has failed for the named file under the named CA L-Serv. The macro should be
identified as MODCB. The accompanying JLOG059I message explains the error code.
Action:
JLOG Messages
JLOG056E
BC1PJLOG - WRITRUTN - VSAM ERROR - JOURNAL file name-L-Serv name, MACRO
macro name
Reason:
An LSERV PUT has failed for the named file under the named CA L-Serv. The macro
should be identified as PUT. The accompanying JLOG059I message explains the error
code.
Action:
JLOG059I
R15 = R15 contents, R0 = R0 contents, FTNCD = FTNCD contents, FDBK = FDBK contents
Reason:
A L-Serv VSAM error has occurred. The information in this message is for diagnostic
purposes. A JLOG061I-JLOG089I message should follow explaining particular error
codes.
Action:
JLOG061I
0140 - NO SESSION FOUND FOR THIS USER
Reason:
Informational message. This is a CA L-Serv return code.
Action:
None.
JLOG062I
0240 - DDNAME IS NOT MANAGED BY LSERV
Reason:
Action:
None.
JLOG Messages
JLOG063I
0340 - FILE IS IN A HOLD STATUS
Reason:
Action:
None.
JLOG064I
0440 - FILE IS IN A CLOSED STATUS
Reason:
Action:
None.
JLOG065I
0540 - THE DATA SET CANNOT BE OPENED
Reason:
Informational message. A VSAM error prevented the file from being opened. This is a CA
L-Serv return code.
Action:
None.
JLOG066I
0640 - FILE NOT PREVIOUSLY OPENED
Reason:
Action:
None.
JLOG Messages
JLOG067I
0740 - OPEN FAILED FOR THE DATA SET
Reason:
Informational message. A VSAM error prevented the file from being opened. This is a CA
L-SERV return code.
Action:
None.
JLOG068I
0840 - VERIFY FAILED FOR THE DATA SET
Reason:
Informational message. A VSAM error has occurred. This is a CA L-SERV return code.
Action:
None.
JLOG069I
0940 - UNEXPECTED RPL CODE
Reason:
Informational message. L-Serv encountered an unexpected request. This is a CA L-SERV
return code.
Action:
None.
JLOG070I
0A40 - LOCK NOT HELD WHEN EXPECTED
Reason:
Informational message. This is a CA L-SERV return code.
Action:
None.
JLOG Messages
JLOG071I
0B40 - LCOMM SEND FAILED OR WAS REJECTED
Reason:
Informational message. An L-Comm SEND request failed or was rejected. This is a CA
L-SERV return code.
Action:
None.
JLOG072I
0C40 - LCOMM RECEIVE FAILED OR WAS REJECTED
Reason:
Informational message. An L-Comm RECV request failed or was rejected. This is a CA
L-SERV return code.
Action:
None.
JLOG073I
0D40 - LCOMM CONTINUED RECEIVE WAS TOO LONG
Reason:
Informational message. An error occurred in an L-Comm RECV request. This is a CA
L-SERV return code.
Action:
None.
JLOG074I
0E40 - LCOMM RECEIVED INVALID FUNCTION CODE
Reason:
Informational message. An error occurred in an L-Comm RECV request. This is a CA
L-SERV return code.
Action:
None.
JLOG Messages
JLOG075I
0F40 - RECORD LOCK ALREADY HELD
Reason:
Informational message. A record lock is already being held by another user. This is an LServ return code.
Action:
None.
JLOG076I
1040 - RECORD LOCK NOT HELD WHEN EXPECTED
Reason:
Action:
None.
JLOG077I
1140 - DSNAME IS NOT MANAGED BY LSERV
Reason:
Action:
None.
JLOG078I
1240 - ABEND OCCURRED WHILE PROCESSING REQUEST
Reason:
Action:
None.
JLOG Messages
JLOG079I
1340 - ENQUEUE CANCELLED
Reason:
Action:
None.
JLOG080I
1440 - NO GROUP FILE AVAILABLE (MAYBE ALL FILES FULL?)
Reason:
Action:
None.
JLOG081I
1540 - FILE IS NOT PART OF A GROUP
Reason:
Action:
None.
JLOG082I
1640 - GROUP FILE SWITCH ALREADY IN PROGRESS
Reason:
Action:
None.
JLOG Messages
JLOG083I
0044 - LSERV SUBSYSTEM SPECIFIED IS NOT ACTIVE OR AVAILABLE
Reason:
Action:
None.
JLOG084I
0048 - LSERV SUBSYSTEM SPECIFIED IS SHUTTING DOWN
Reason:
Action:
None.
JLOG085I
0050 - HOST LSERV SYSTEM IS NOT AVAILABLE
Reason:
Action:
None.
JLOG099S
program name - routine name - request code - JOURNAL ERROR
Reason:
A journal error has been detected when processing the named request in the named
routine in the named program.
Action:
This message is preceded by other messages. Correct the problems identified in these
other messages.
JRCV Messages
JRCV Messages
This section details messages generated in the course of PITR processing, along with
possible causes and corrective actions to take in error situations.
JRCV001E
INVALID field name date/time FIELD VALUE - field content
Reason:
The field and date/time values are invalid.
Action:
Correct the parameter specification and resubmit the request.
JRCV002I
MCF RECORD TIMESTAMP ERROR DETECTED - KEY: record key
Reason:
The recovery utility has detected an error in an MCF time stamp record. The record key
is provided.
Action:
JRCV003E
SORT ERROR SORT RETURN CODE: return code
Reason:
An error has occurred when sorting journal data set input for the recovery utility.
Action:
JRCV Messages
JRCV004E
stage name STAGE FROM JOURNAL NOT DEFINED FOR ENVIRONMENT environment
name
Reason:
The named stage occurs in records recovered from a journal data set, but is not defined
in the current C1DEFLTS table.
Action:
JRCV005E
ENVIRONMENT environment name FROM JOURNAL NOT DEFINED IN C1DEFLTS
Reason:
The named environment occurs in records recovered from a journal data set, but is not
defined in the current C1DEFLTS table.
Action:
JRCV006E
UNABLE TO OBTAIN TYPE DEFINITION PROCESSING TERMINATED
Reason:
The recovery utility is trying to recover an element from a journal tape, but cannot find
the type for the element defined in the current MCF.
Action:
Define the type, and resubmit the job.
JRCV007E
UNIDENTIFIABLE MCF RECORD - KEY: key data
Reason:
The recovery utility has detected an unrecognizable MCF.
Action:
JRCV Messages
JRCV008E
SYNTAX ERROR - EMBEDDED blank/asterisk FOUND IN THE environment/system
SPECIFICATION
Reason:
The environment or system specification in the recovery utility syntax contains an
asterisk. These parameters must be specified explicitly.
Action:
Respecify the parameter and resubmit the request.
JRCV009E
MISSING JOURNAL RECORD segment name SEGMENT - SEGMENT ID: segment id
Reason:
Internal error.
Action:
JRCV010I
SKIPPING TO NEXT JOURNALED TRANSACTION
Reason:
Informational message. The recovery utility is skipping the current journal transaction.
Action:
None.
JRCV011E
JOURNAL RECORD SEQUENCE ERROR - error description
Reason:
The time stamp on a journal record has changed before the recovery utility reached the
number of records in the transaction record count. This often happens because a
journal file is missing.
Action:
Make sure that all appropriate journal files have been supplied as input to the recovery
utility.
JRCV Messages
JRCV011W
JOURNAL RECORD SEQUENCE ERROR - error description
Reason:
The time stamp on a journal record has changed before the recovery utility reached the
number of records in the transaction record count. This often happens because a
journal file is missing.
Action:
utility.
JRCV012E
INCOMPLETE JOURNAL TRANSACTION SET EXPECTING number of records FOUND
number of records
Reason:
The number of records in the recovered journal transaction does not correspond to the
record count for that transaction. This often happens because a journal file is missing.
Action:
utility.
JRCV013E
UNEXPECTED JOURNAL PROCESSOR GROUP RECORD ENCOUNTERED
Reason:
The recovery utility has encountered a processor group record on a journal tape that is
out of sequence.
Action:
JRCV Messages
JRCV014E
MEMBER FOUND NOT FOOTPRINTED IN LIBRARY
Reason:
The recovery utility has found the member in a current base or delta library, but there is
no footprint associated with the member.
Action:
Research the problem carefully, but it is likely that the member can be deleted.
JRCV015I
create/update/delete
Reason:
Informational message. This is the first message in the log portion of the Journal
Recovery Execution report for each recovered base or delta journal record.
Action:
None.
JRCV016I
ENV=environment name STG=stage name SYS=system name SBS=subsystem name
TYPE=type name
Reason:
Informational message. This is the second message in the log portion of the Journal
Recovery Execution report for each recovered base or delta journal record.
Action:
None.
JRCV Messages
JRCV017E
INVALID REQUEST - recover/list CANNOT BE SPECIFIED BECAUSE recover/list
PREVIOUSLY SPECIFIED
Reason:
You have submitted a recovery utility job that requests both a LIST action and a
RECOVER action. Each request can specify one or the other, but not both.
Action:
Respecify the job and resubmit the request.
JRCV018I
JOURNAL DELETE TRANSACTION NOT PROCESSED MEMBER/RECORD NOT FOUND
Reason:
Informational message. While processing a delete transaction from a journal tape, the
recovery utility checked a base or delta library for the member and did not find it. This
indicates that the member has already been deleted.
Action:
None.
JRCV019I
JOURNAL TRANSACTION BYPASSED OUTDATED TRANSACTION
Reason:
Informational message. The current member/record update date and time stamp is
more recent than the journal transaction. The recovery utility has therefore ignored the
journal transaction.
Action:
None.
JRCV Messages
JRCV020I
JOURNAL TRANSACTION RECOVERY COMPLETED, RETURN CODE=return code
Reason:
This is the last message written for each successful recovery transaction in the log
portion of the Journal Recovery Execution report.
Action:
None.
JRCV021I
create/update/delete mcf/pkg
Reason:
Informational message. This is the first message in the log portion of the Journal
Recovery Execution report for each recovered MCF or PCF transaction.
Action:
None.
JRCV022I
record type number Endevor information
Reason:
Informational message. This is the second message in the log portion of the Journal
Recovery Execution report for each recovered MCF or PCF transaction. It specifies the
CA Endevor SCM location associated with the transaction, and includes the number of
the record type.
Action:
None.
JRCV Messages
JRCV023I
CONSTRUCTION OF GENERATE SCL SCHEDULED FOR THIS ELEMENT
Reason:
Informational message. The recovery utility has scheduled a batch job to build
GENERATE SCL for the element named earlier in this recovery record.
Action:
None.
JRCV027I
JOURNAL list/recovery PROCESSING COMPLETED, HIGHEST RETURN CODE=return code
Reason:
This is the last message in the Journal Recovery Execution Log. It indicates whether this
run of the report was for a RECOVER or a LIST job, and the job return code.
Action:
None.
JRCV028E
JOURNAL GROUP ID NOT DEFINED IN C1DEFLTS FOR environment/package
Reason:
If an environment name appears in this message, the C1DEFLTS table does not reference
a journal group ID in the ENVIRONMENT section for that environment. If a package
name appears in the message, the C1DEFLTS table does not reference a journal group ID
in the MAIN section.
Action:
JRCV Messages
JRCV029W
NOT AUTHORIZED FOR JRNL RECOVERY OF ENV environment name - BYPASSING ALL
RELATED JRNL TRANSACTIONS
Reason:
The user who submitted the recovery request is not authorized to access the named
environment. The recovery utility will therefore ignore all journaled transactions
pertaining to that environment.
Action:
If you need to recover transactions related to the named environment, a user with
authority to access that environment should resubmit the job.
JRCV030W
NO JOURNAL TRANSACTION RECORDS FOUND TO MATCH SELECTION CRITERIA
Reason:
The recovery utility found no journal records that met the specified selection criteria.
Action:
Make sure the criteria was specified correctly.
JRCV031I
record type LAST UPDT DATE: date time MEMBER NOT FOUND
Reason:
Informational message. This message indicates either the date and time of the last
update of the named member, or that the recovery utility did not find the member.
Action:
None.
JRCV Messages
JRCV032I
transaction number JOURNAL TIMESTAMP: date time RECORD COUNT: number of
records
Reason:
Informational message. The first message for each recovery transaction. The message
contains the number of the transaction, the date and time stamp from the journal data
set, and the number of records in the transaction.
Action:
None.
JRCV100I
DATA SET USAGE: usage
Reason:
Informational message. This is the first message for each data set reported on in the
data set activity portion of the Journal Recovery Execution Summary report.
Action:
None.
JRCV101I
MEMBERSRECORDS CREATED................................number
Reason:
Informational message. This message indicates the number of members or records
created in the data set identified in the preceding JRCV100I message.
Action:
None.
JRCV Messages
JRCV102I
MEMBERSRECORDS UPDATED................................number
Reason:
updated in the data set identified in the preceding JRCV100I message.
Action:
None.
JRCV103I
MEMBERSRECORDS DELETED................................number
Reason:
deleted in the data set identified in the preceding JRCV100I message.
Action:
None.
JRCV105I
NBR OF GENERATE SCL STMTS WRITTEN:
Reason:
Informational message. This message serves as the header for the
SCL statement portion of the Journal Recovery Execution Summary report. It
is followed by one or more JRCV106I messages.
Action:
None.
JRCV Messages
JRCV106I
TYPE=type name....number
Reason:
Informational message. This message identifies the number of GENERATE SCL
statements written for the named CA Endevor SCM location and classification.
Action:
None.
JRCV108I
NO GENERATE SCL STMTS WRITTEN
Reason:
Informational message. This message follows message JRCV105I if no SCL statements
were written during the run of the recovery utility.
Action:
None.
JRCV110I
NO RECOVERY ACTIVITY OCCURRED
Reason:
Informational message. This message follows message JRCV113I if no recovery activity
occurred for a named data set during a run of the recovery utility.
Action:
None.
JRCV Messages
JRCV111I
TYPE=type name....number
Reason:
Informational message. This message indicates the number of generate or delete
processors executed for the specified location during a run of the recovery utility.
Action:
None.
JRCV112I
NBR OF record type and transaction CONTAINED IN JOURNAL INPUT.......number
Reason:
Informational message. This message indicates the number of transactions for a specific
record type during a run of the recovery utility.
Action:
None.
JRCV113I
ENV=environment name STG=stage id SYS=system name SBS=subsystem name
TYPE=type name
Reason:
Informational message. This message indicates the CA Endevor SCM location associated
with a data set named in message JRCV100I.
Action:
None.
MCS Messages
MCS Messages
This section details CA Endevor SCM messages generated by Catalog Synchronization
utility in the course of processing, along with possible causes and corrective actions to
take in error situations.
MCS0001I
NO ENVIRONMENT COMMAND WAS SPECIFIED. NO CATALOG SEGMENTS WILL BE
WRITTEN
Reason:
Informational message. The BC1PCSYN command file did not contain an ENVIRONMENT
keyword. Therefore, the extract program will not extract any MCF information.
Action:
None.
MCS0002I
MCF CATALOG SEGMENT DATA WILL BE CREATED FOR ENVIRONMENT
Reason:
Informational message. This message indicates the number of catalog segments created
for the corresponding MCF records found missing from the catalog.
Action:
None.
MCS0003I
NUMBER OF CATALOG SEGMENTS WRITTEN FOR ENVIRONMENT
Reason:
Informational message. This message indicates the number of catalog segments created
for the corresponding MCF records found missing from the catalog.
Action:
None.
MCS Messages
MCS0004E
Reason:
The $IMR service returned an unrecoverable error. The message following MCS0005E
specifies the $IMR error.
Action:
For more information about the error, see the message that follows MCS0005E.
MCS0005E
C1BMINIT FAILURE. Call Endevor Technical Support
Reason:
One of the BC1PCSYN initialization programs did not complete successfully. BC1PCSYN
execution was terminated.
Reason:
Resubmit the job. If the problem persists, contact your administrator.
MCS0006E
PROCESSING TERMINATED
Reason:
An unrecoverable error occurred while performing the action identified. CA Endevor
SCM stopped processing the action.
Action:
PDM Messages
MCS0007E
PROCESSING TERMINATED BECAUSE OF CONTROL STATEMENT ERRORS
Reason:
The BSTIPT control statement parse routine detected an error in the control statements
passed to BC1PCSYN. The parser generated one or more messages to identify the
problem.
Action:
See the parser messages generated and correct the error in the BSTIPT control
statements. Resubmit the job after the errors have been corrected.
MCS0012C
ENVIRONMENT: <ENV> DOES NOT EXIST
Reason:
Either you do not have access to this environment, or the environment does not exist.
Action:
Correct the input request and resubmit.
PDM Messages
This section details messages generated during processing by the Parallel Development
Manager (PDM) when you are using the CA Endevor SCM Parallel Development option.
Possible causes and corrective actions to take in error situations are provided.
PDM0002E
Invalid password specified in the C1DEFLTS table
Reason:
The PDM installation password is missing or invalid. Either PDM was installed
incorrectly or the PDM license has expired.
Action:
Verify that the correct PDM password is specified in the installation C1DEFLTS table.
Reassemble the table if necessary.
PDM Messages
PDM0003E
A $STORAGE request failed. Increase the job region size
Reason:
PDM was unable to obtain virtual storage to perform the requested function. The
region size associated with the batch job or TSO session is not large enough for PDM to
complete the current operation.
Action:
If the error occurred during batch execution of PDM, increase the REGION parameter in
the JOB or EXEC JCL statement. If the error occurred during foreground execution,
logon with a larger region size.
PDM0021E
Member data set(member) exists and the REPLACE option was not specified
Reason:
The specified member exists in the specified data set and the REPLACE option was not
used in the BUILD WIP or the MERGE statement. PDM will terminate the Build WIP or
Merge processing.
Action:
If you want to replace the specified member, add the REPLACE clause to the BUILD WIP
or MERGE statement or the appropriate member/element mask. Alternatively, you can
delete the member from the specified data set.
PDM0023E
Internal logic error. The Merge operation was called without a Header block
Reason:
The Merge processing routine was called with an incorrect internal control block
structure. PDM will terminate Merge processing.
Action:
Retry the Merge operation. If the problem persists, contact your administrator.
PDM Messages
PDM0025E
A MERGE error occurred processing data set data set(member)
Reason:
The Merge operation detected a WIP record with an invalid prefix. PDM is unable to
determine what to do with the record. The record in error will be printed in message
PDM0026E. PDM will terminate the Merge process.
Action:
See message PDM0026E to identify the WIP record that is in error. Use the PDM Edit
WIP function to edit the WIP file and correct the WIP record. After the WIP file has been
corrected, resubmit the Merge request.
PDM0026E
The invalid record follows: WIP record text
Reason:
This message follows message PDM0025E, and identifies the WIP record that is in error.
The message contains the first 70 characters of the WIP record. The WIP prefix is
located in the first eight characters of the record.
Action:
Correct the invalid WIP prefix. For a list of valid WIP prefixes and their meanings, see the
Parallel Development Option Guide. After the WIP record has been corrected, resubmit
the Merge request.
PDM0027E
reason-code ERROR ACQUIRING INITIAL STORAGE
Reason:
An out-of-storage condition or an internal error has occurred.
Action:
If the reason code is NOSTG, increase the amount of storage available to the region. For
other reason codes, contact CA Technical Support.
PDM Messages
PDM0028E
Reason:
Action:
PDM0029E
DV1 and ROOT MUST BE INVENTORY LOCATIONS SINCE THE MERGE IS TO AN
INVENTORY LOCATION
Reason:
All merging items must be CA Endevor SCM elements, if the target of the merge is an CA
Endevor SCM inventory location.
Action:
Merge to an output file, and then add the member into CA Endevor SCM.
PDM0030E
DV1, DV2 AND ROOT MUST BE INVENTORY LOCATIONS SINCE THE MERGE IS TO AN
INVENTORY LOCATION.
Reason:
All merging items must be CA Endevor SCM elements, if the target of the merge is an CA
Endevor SCM Inventory location.
Action:
Merge to an output file then add the member into CA Endevor SCM.
PDM0031E
TARGET INVENTORY TYPE DEFINITION NOT DEFINED
Reason:
An incorrect type name was specified on the target CA Endevor SCM location.
Action:
Re-do the merge using the correct type name.
PDM Messages
PDM0040E
ENDEVOR type name could not be located
Reason:
The Build request specified a CA Endevor SCM location as the ROOT, DV1 or DV2
location. PDM was unable to locate the environment, system, subsystem, type, or stage
specified in the ROOT, DV1 or DV2 clause.
Action:
Correct the location field specified in the ROOT, DV1 or DV2 clause and identified by
type. If the specified ROOT, DV1 or DV2 parameter was correct, verify that PDM is using
the correct C1DEFLTS table.
PDM0041E
Overlay of WIP member name is not allowed with the specified masking
Reason:
If PDM finds an explicit WIP member mask, it requires that the ROOT mask is also
explicit. The Build request contained an explicit WIP member mask and a non-explicit
(wildcarded) ROOT member mask. PDM will terminate the Build request.
Action:
Change the BUILD member mask to reflect the correct combination of WIP, ROOT, DV1
and DV2 member masks. If the WIP is explicit then the ROOT, DV1 and DV2 masks must
also be explicit. If multiple Root members/elements are to be processed, use a WIP
member mask to generate the appropriate member name or explicitly list each of the
Root files desired.
PDM0042E
Unable to get member/element list for the file name file
Reason:
PDM was unable to build a member or element list for the file specified.
Action:
This message is usually generated because another error was detected. For any other
error message, see the PDM Build WIP Detail Report. If another error message was
generated then see the corrective action indicated for the message. If another error
message was not found, verify that the location information was specified correctly in
the Build request and that the member/element mask statements are also valid.
PDM Messages
PDM0043C
Member/element name was not found in the file name location
Reason:
PDM was unable to locate the member or element in the ROOT, DV1, DV2, or WIP file.
PDM will terminate the current operation.
Action:
Verify that at least one member or element matching the mask specified is found at the
location specified and resubmit the Build or Merge request. If a matching member or
element is not found then specify another member/element mask in the Build or Merge
request.
PDM0043E
Reason:
Action:
request.
PDM0043I
Reason:
Action:
request.
PDM Messages
PDM0043S
Reason:
Action:
request.
PDM0043W
Reason:
Action:
request.
PDM0044E
WIP must be 8 bytes larger than Root, DV1, or DV2. If RECFM=VB then WIP must be 12
bytes larger
Reason:
PDM determined that the logical record length (LRECL) of the WIP file is not large
enough. The logical record length of the WIP file must be at least eight bytes larger then
the largest record length of the Root, Derivation 1 or Derivation 2 files. If the WIP file
contains variable length records then the WIP file must be at least 12 bytes larger. PDM
will terminate the Build WIP processing.
Action:
Reallocate the WIP file with the correct record length and resubmit the Build WIP
request.
PDM Messages
PDM0045E
An invalid COMPARE column name value of value was specified
Reason:
The BUILD WIP statement specified an invalid COMPARE from or COMPARE THRU value.
The valid COMPARE column range is 1 through 256, inclusive. The COMPARE THRU value
cannot be larger than the ROOT data set or element record length. PDM will terminate
the Build WIP processing.
Action:
Correct the COMPARE clause and resubmit the BUILD WIP request.
PDM0046E
The COMPARE from column value is greater than the COMPARE THRU column value
Reason:
The BUILD WIP statement specified a COMPARE from value that was larger than the
COMPARE THRU value. The COMPARE THRU value must be greater than or equal to the
COMPARE from value. PDM will terminate the Build WIP processing.
Action:
Correct the COMPARE clause and resubmit the Build WIP request.
PDM0047E
Panvalet or Librarian format is invalid for data set data set name
Reason:
Build WIP processing determined that the identified data set was a CA Panvalet or CA
Librarian data set and that CA Panvalet or CA Librarian data sets are not supported.
PDM will terminate the Build WIP processing.
Action:
Specify a data set that is not a CA Panvalet or CA Librarian data set and resubmit the
Build WIP request.
PDM Messages
PDM0048E or PDM0048I
ENDEVOR Element elm-name at env/stgid/sys/sbs/type is a sourceless element and
cannot be used.
Reason:
The element identified in the message is a sourceless element and cannot be specified
as a Root, DV1, or DV2 element.
Action:
Use the actual element associated to the sourceless element.
PDM0049E or PDM0049I
ENDEVOR Element ele-name at env/stgid/system/subsystem/type is a delta log
element. Last version level must be specified.
Reason:
The PDM WIP specification for the element identified on the PDM0049E message has a
wrong version level. Log delta elements are restricted to use the elements current
version level since source is unavailable for prior levels.
Action:
Specify the current level.
PDM0064I
[BUILD WIPMERGE] operation is complete. Return Code=return code
Reason:
PDM has completed the Build WIP or Merge processing. The operation completed with
the specified return code.
Action:
None. If the return code is non-zero, check the PDM Build WIP Detail Report for
messages that may identify an error.
PDM Messages
PDM0080I
count statistics records were written to data set data set name
Reason:
The WRITE STATISTICS TO clause was specified in either a Build or Merge request. PDM
has written the indicated number of statistics records to the specified data set.
Action:
None.
PDM0081E
PDM internal error. The required name parameter was not passed
Reason:
An internal error occurred during PDM processing. PDM will terminate the current
operation.
Action:
Resubmit the request. If the problem persists, contact your administrator.
PDM0087E
PDM Statistics routine error. Routine=name, Return Code=return code.
Reason:
An internal error occurred during PDM statistics processing. PDM will terminate the
current operation.
Action:
Resubmit the request. If the problem persists, contact your administrator.
PDM0104I
WIP member data set(member) was deleted after the successful Merge
Reason:
The Merge operation completed successfully and the specified WIP member was
deleted. The Merge operation deletes the WIP member if OPTIONS DELETE WIP AFTER
MERGE has been specified in the MERGE statement.
Action:
None.
PDM Messages
PDM0120E
Data set data set name is not catalogued. [BUILD WIPMERGE] processing is
terminated
Reason:
PDM could not locate the specified data set name in the system catalog. The identified
action cannot continue processing.
Action:
Correct the data set name and resubmit the action that failed.
PDM0133E
Statistics data set data set name failed validation
Reason:
The identified statistics data set had invalid attributes. The statistics data set must be
sequential and must have variable length records or at least 533 bytes.
Action:
Reallocate the statistics data set with the correct attributes or specify a data set that has
the correct attributes. Resubmit the request that failed.
PDM0134E
Statistics data set DD ddname is not allocated
Reason:
OPTIONS WRITE STATISTICS TO DDNAME was specified in the BUILD WIP or MERGE
statement, but the DDname specified was not allocated to the PDM session. PDM will
terminate the Build WIP or Merge processing.
Action:
If PDM is executing in batch mode, add the specified DDname to the PDM JCL. If PDM is
executing in foreground, use the TSO ALLOCATE command to allocate the DDname to
the TSO session.
PDM Messages
PDM0135I
The PDMSTATS DD is ignored. Statistics will be written to data set data set name
Reason:
WRITE STATISTICS TO was specified in the BUILD WIP or MERGE statement. PDM also
detected that the PDMSTATS DD statement was allocated. PDM will write the statistics
to the data set identified in the WRITE STATISTICS TO clause. The PDMSTATS DD
statement will be ignored.
Action:
None. To prevent the message from being issued, remove the PDMSTATS DD statement
from the PDM execution JCL.
PDM0138E
The COMPARE THRU column (value) is greater than the data set name record length
(value)
Reason:
Build WIP processing determined that the COMPARE THRU value specified is larger than
the record length of the data set identified. PDM cannot compare data that is outside
the bounds of a source record. PDM will terminate the Build WIP processing.
Action:
Correct the COMPARE THRU clause and resubmit the Build WIP request.
PDM0139E
Language value is not valid for [PanvaletLibrarian] data set data set name
Reason:
The CA Panvalet or CA Librarian language specified in the OPTIONS LANGUAGE clause is
not valid. PDM will terminate the Build WIP processing.
Action:
Correct the OPTIONS LANGUAGE clause and resubmit the Build WIP request.
PDM Messages
PDM0140E
Internal logic error in BUILD WIP processing routine, name
Reason:
Build WIP processing detected an internal logic error in the routine identified. PDM will
terminate the Build WIP processing.
Action:
Retry the Build WIP action. If the problem persists, contact your administrator.
PDM0141E
BUILD WIP processing error. BC1PSCMP passed a return code of return code
Reason:
The CA Endevor SCM compare program, BC1PSCMP, returned a non-zero return code.
PDM cannot continue with the Build WIP processing.
Action:
Check the PDM Build WIP Detail Report for additional error messages. Take any
corrective action identified by those messages. If the error cannot be corrected, contact
your administrator.
PDM0142E
Statistics data set data set name is not catalogued
Reason:
PDM could not locate the statistics data set specified in the OPTIONS WRITE STATISTICS
TO DSNAME in the system catalog. PDM will terminate the Build WIP or Merge
processing.
Action:
Correct the WRITE STATISTICS TO DSNAME clause and resubmit the Build WIP or Merge
request.
PDM Messages
PDM0143E
Statistics data set data set name could not be allocated. S99ERROR=value,
S99INFO=value
Reason:
PDM could not allocate the data set specified in the OPTIONS WRITE STATISTICS TO
DSNAME clause. An error message identifying the Dynamic Allocation return code
should precede this message. PDM will terminate the Build WIP or Merge processing.
Action:
See IBM publication GC28-1852 MVS/ESA System Programming Library: Application
Development Guide or GC28-1303 OS/VS2 MVS Systems Programming Library: Job
Management for a definition of the S99ERROR and S99INFO fields. Correct the error and
PDM0150E
An unrecoverable I/O error occurred accessing DD ddname, data set data set name
Reason:
An unrecoverable I/O error occurred while PDM was accessing the identified data set. A
specific I/O routine generated message should precede this message. PDM will
terminate the Build WIP or Merge processing.
Action:
See the previous I/O routine error message and take any corrective action identified.
Resubmit the Build WIP or Merge request.
PDM0151E
The following $IMR error occurred accessing record type record name:
Reason:
The CA Endevor SCM $IMR service returned an error condition when PDM accessed the
Master Control File (MCF). The error message returned by the $IMR service will follow
this message. PDM will terminate the Build
WIP processing.
Action:
See the $IMR message that follows this message, take any corrective action specified,
and resubmit the Build WIP request.
PDM Messages
PDM0152E
An unrecoverable $SMR error occurred while rebuilding element element name
Reason:
The CA Endevor SCM $SMR service returned an error condition when PDM attempted to
retrieve the specified element. The PDM Build WIP Detail report should contain an error
message that identifies the $SMR error. PDM will terminate the Build WIP processing.
Action:
See the $SMR error message and take any corrective action specified. If the problem
cannot be corrected, contact your administrator.
PDM0153E
An error occurred during [HeaderEntry] Block initialization. [Build WIPMerge]
processing is terminated
Reason:
An error occurred during PDM Build WIP or Merge initialization processing. A message
that identifies the cause of the error should precede this message. PDM will terminate
the Build WIP or Merge processing.
Action:
See any previous error message, take the corrective action identified, and resubmit the
Build WIP or Merge request.
PDM0155E
BUILD WIP processing has terminated because of the previous error
Action:
See any previous error message, take the corrective action identified, and resubmit the
Build WIP request.
PDM Messages
PDM0156E
The PDM statistics routine has passed a return code of return code
Reason:
The PDM Statistics routine passed a non-zero return code. PDM will terminate the Build
WIP or Merge processing.
Action:
Retry the Build WIP or Merge request. If the problem persists, contact your
administrator.
PDM0157E
A BUILD WIP logic error occurred. A premature end-of-file for the file name file was
encountered
Reason:
PDM detected an unexpected end-of-file while reading the Root, Derivation 1 (DV1), or
Derivation 2 (DV2) file during Build WIP processing. PDM will terminate the Build WIP
processing.
Action:
Retry the Build WIP request. If the problem persists, contact your administrator.
PDM0158E
A BUILD WIP logic error occurred. Cross pointers (value1/value2/value3/value4) do
not match
Reason:
The internal structure returned by the CA Endevor SCM compare program is logically
inconsistent. PDM will terminate the Build WIP processing.
Action:
Retry the Build WIP request. If the problem persists, contact your administrator.
PDM Messages
PDM0159E
An error occurred during BUILD WIP pass number processing
Reason:
An error occurred during Build WIP processing. PDM was executing the Build WIP pass
number identified. A previous message should identify the cause of the error. PDM will
terminate the Build WIP processing.
Action:
See the previous error message, take any corrective action identified and resubmit the
Build WIP request.
PDM0160C
The BUILD WIP MERGE operation was bypassed because data set(member) exists
Reason:
PDM successfully completed the Build WIP processing. The Build WIP request specified
the MERGE OUTPUT clause. PDM was unable to perform the Merge request because the
MERGE OUTPUT member already exists and the REPLACE option was not specified. This
is an informational message. PDM will continue with the Build WIP request.
Action:
If you want the WIP member to be merged, submit a separate request for the merge.
PDM0161I
The Merge operation is beginning
Reason:
The Build WIP request specified the MERGE OUTPUT clause. PDM has completed the
Build WIP with no errors and is now beginning the Merge operation.
Action:
None.
PDM Messages
PDM0162C
The WIP file was not MERGED because at least one conflict was found
Reason:
The PDM Build WIP action contained the MERGE OUTPUT clause. PDM will
automatically merge the WIP file only if it finds no conflicts in the WIP file. The current
WIP file had at least one conflict. PDM, therefore, will not perform the Merge operation
as part of the Build WIP processing.
Action:
None. Resolve the conflicts with the Edit WIP function and use the Merge action to
create the Merge file.
PDM0163E
A WIP, ROOT, DV1, and/or DV2 mask is required when a non-sequential or ENDEVOR
location is used
Reason:
A Build WIP member/element was not specified with the BUILD WIP statement and the
WIP, Root, Derivation 1 or Derivation 2 data set is not a sequential data set or the Root,
Derivation 1 or Derivation 2 location is a element. The Build WIP member/element mask
can be omitted only when the WIP, Root, Derivation 1 and Derivation 2 files are
sequential data sets. In all other cases, PDM requires the Build WIP member/element
mask.
Action:
Add the appropriate element/member mask statements to the BUILD WIP statement
PDM0164E
A WIP and OUT mask is required when a non-sequential WIP file is used
Reason:
The WIP file specified in the MERGE statement is a non-sequential data set and an
appropriate Merge member mask was not specified. PDM requires a Merge member
mask if the WIP data set is non-sequential. PDM will terminate the Merge request.
Action:
Add the appropriate member mask statements to the MERGE statement and resubmit
the request.
PDM Messages
PDM0165E
An invalid member mask was specified for a sequential file name file
Reason:
The member mask specified for the identified file is incorrect for a sequential data set. If
the file is sequential, the member mask specified must be '(N/A)'. PDM will terminate
the Build WIP or Merge request.
Action:
Correct the member mask statement and resubmit the request.
PDM0166I
THE WIP FILE WAS MERGED INTO DATASET dataset-name
Reason:
The BUILD WIP statement contained the MERGE OUTPUT clause. PDM successfully
merged the WIP file into the identified data set after the Build WIP completed.
Action:
None.
PDM0166I
THE WIP FILE WAS MERGED INTO INVENTORY env/stgid/sys/sbs/type
Reason:
Action:
None.
PDM Messages
PDM0167I
The BUILD WIP performance enhancement was disabled for the file file at the users
request
Reason:
The BUILD WIP statement contained the OPTIONS DISABLE PERFORMANCE
ENHANCEMENT clause. PDM will not use the performance enhancement for the
identified file as part of the Build processing. By default, the performance enhancement
is always enabled.
Action:
None.
PDM0168E
The MERGE data set (data set name) LRECL is not large enough to write the merged
WIP records
Reason:
The logical record length (LRECL) of the Merge Output data set is not large enough to
write the merged WIP records. The LRECL of the Merge data set must be greater than or
equal to the LRECL of the WIP data set minus eight. For example, if the WIP data set
LRECL is 88, the Merge data set LRECL must be at least 80. The four-byte RDW of
variable length records is not included in the calculations. PDM will terminate the Merge
processing.
Action:
Specify a Merge data set that has a sufficiently large LRECL or reallocate the Merge data
set with an appropriate LRECL.
PDM0169E
An invalid Header Block was found. HFUNC=X'value'
Reason:
PDM found an invalid internal control block structure. The message identifies the
function code associated with the PDM Header Block structure. PDM will terminate any
further processing.
Action:
Retry the operation. If the problem persists, contact your administrator.
PDM Messages
PDM0170E
Unable to allocate data set data set name. S99ERROR=error code, S99INFO=info code
Reason:
PDM was unable to dynamically allocate the data set specified. The dynamic allocation
service returned the error code and information code identified. PDM will terminate the
Build or Merge processing.
Action:
PDM0171E
PDM does not support data sets allocated to DD DUMMY
Reason:
PDM found that one of the data sets specified in the BUILD or MERGE statement was
allocated to DD DUMMY or DD DSN=NULLFILE. PDM does not support DUMMY data sets
for the BUILD ROOT, DV1 or DV2 files or the MERGE WIP file.
Action:
Specify a valid data set for the file that was in error and resubmit the request.
PDM0172E
PDM does not support load module libraries. Data set=data set name
Reason:
PDM determined that the identified data set was a load module library, that is, the
record format was Undefined (RECFM=U). PDM does not support load module libraries.
Action:
Replace the specified data set with a non-load module library and resubmit the request.
PDM Messages
PDM0173E
The Merge process was unable to allocate a temporary work data set.
S99ERROR=error code, S99INFO=info code
Reason:
The Merge operation uses a dynamically allocated, temporary data set during
processing. PDM was unable to allocate the temporary data set. PDM will terminate the
Merge operation.
Action:
resubmit the request. If the error persists, contact your systems programming area.
PDM0174E
Validation of the temporary Merge data set failed
Reason:
The Merge operation uses a dynamically allocated, temporary data set during
processing. The temporary data set dynamically allocated by PDM did not meet the
Merge operation validation requirements.
Action:
One or more error messages should have preceded message PDM0174E. Follow the
corrective action indicated for the error messages and resubmit the request.
PDM Messages
PDM0176C
Compare not done for ROOT <rootname> DERIV <derivationname>. EMPTY member
or inconsistent results.
Reason:
PDM determined that the internal structure returned by the compare program,
BC1PSCMP, is logically inconsistent with the return code received from BC1PSCMP. PDM
is unable to complete the Build processing. This message may be issued if attempting to
compare a ROOT, or DERIVATION entity that contains no source lines (an EMPTY
member). An EMPTY member causes the line number table (LNT) to contain zero lines of
source with which to compare. Because the count of the number of lines is zero, this
message is issued.
Action:
If the source of the message is not due to the comparison of an EMPTY member, retry
the Build request. If the problem persists, use the OPTIONS DISABLE PERFORMANCE
ENHANCEMENT clause in the BUILD WIP statement to disable the Build WIP
performance enhancement. If the problem still persists, contact your CA Endevor SCM
Administrator.
PDM0176E
BC1PSCMP returned inconsistent results. The BUILD WIP will terminate
Reason:
PDM determined that the internal structure returned by the compare program,
BC1PSCMP, is logically inconsistent with the return code received from BC1PSCMP. PDM
is unable to complete the Build processing.
Action:
Retry the Build request. If the problem persists, use the OPTIONS DISABLE
PERFORMANCE ENHANCEMENT clause in the BUILD WIP statement to disable the Build
WIP performance enhancement. If the problem still persists, contact your administrator.
PDM Messages
PDM0177I
The MERGE performance enhancement was disabled at the users request
Reason:
The MERGE statement contained the OPTIONS DISABLE PERFORMANCE ENHANCEMENT
clause. PDM will not use the performance enhancement as part of the Merge
processing. By default, the performance enhancement is always enabled.
Action:
None.
PDM0178S
A abend code ABEND occurred during [Build WIPMerge] processing. PDM will
terminate
Reason:
An unrecoverable ABEND occurred during either BUILD or Merge processing. The abend
code identifies the ABEND that occurred. PDM will immediately terminate processing.
Action:
If the abend code was an Sx37 ABEND, one of the PDM files ran out of space. See the
system job log for the name of the data set that ran out of space. Increase the size of
the data set and resubmit the request. If any other abend code occurred, retry the
operation. If the problem persists, contact your administrator.
PDM0179C
An Entry Block is missing a ROOT or DV1 member name. ROOT=root, DV1=dv1,
DV2=dv2
Reason:
One or more BUILD member/element masks contained a ROOT or DV1 wildcard. While
expanding the wildcarded member PDM was unable to match a Root member with a
Derivation 1 member. The message identifies the names of the ROOT, DV1 and DV2
members that PDM could resolve. A member name containing 10 asterisks will identify
the file for which PDM could not match a member. PDM processing will continue but
the Build return code will be set to eight.
Action:
Specify one or more discrete member/element masks in place of the wildcarded
member/element mask and resubmit the request.
PDM Messages
PDM0180C
The MERGE operation completed with a return code of return code
Reason:
The Merge operation performed as part of Build processing completed with a non-zero
return code. Build processing will continue, but the Build action return code will be set
to eight. The WIP member will be valid. The Merge file will not be valid.
Action:
See the PDM Build WIP Detail Report for any other error message that would indicate
the cause of the error. See the corrective action for the error message.
PDM0180I
THE MERGE OPERATION COMPLETED WITH A RETURN CODE OF rc
Reason:
Action:
None.
PDM Messages
PDM0181C
The ROOT specification is not present in the DV1 element
Reason:
An incompatible Root element was used in the WIP process. The Root's last level source
timestamp is not present in the derivation element's change levels. Source statements
may have been dropped.
Action:
Check results to make sure that the merge completed correctly, because PDM was not
able to verify that the derivation was built from the Root.
PDM0182C
The ROOT specification is not present in the DV2 element
Reason:
An incompatible Root element was used in the WIP process. The Root's last level source
timestamp is not present in the derivation element's change levels. Source statements
may have been dropped.
Action:
Check results to make sure that the merge completed correctly, because PDM was not
able to verify that the derivation was built from the Root.
PDM0200I
PDM control statement parsing beginning
Reason:
PDM is beginning to parse the PDM control statements.
Action:
None.
PDM Messages
PDM0201I
PDM control statement parsing has successfully completed
Reason:
PDM has successfully completed parsing the control statements. No errors were
detected by the parsing routine. PDM will begin processing the specified requests.
Action:
None.
PDM0202E
One or more errors occurred during parsing. Processing will be terminated
Reason:
The PDM parsing routine detected one or more errors with the control statements
specified. A message that identifies the error will be written to the PDM Syntax Request
Report. PDM will terminate further processing.
Action:
See the error message issued, correct the control statements and resubmit the request.
PDM0203E
An error occurred opening the Batch Request data set, DDName=ddname
Reason:
PDM was unable to open the Batch Request data set associated with the identified
ddname. PDM will terminate further processing.
Action:
Verify that the Batch Request data set identified by the specified DDname has been
allocated to the PDM session. Resubmit the request.
PDM Messages
PDM0204E
The maximum LRECL supported for the Batch Request data set is 80 (84 if RECFM=V)
Reason:
The logical record length (LRECL) of the Batch Request data set is invalid. The LRECL
must be 80 for fixed length records and 84 for variable length records. PDM will
terminate further processing.
Action:
Reallocate the Batch Request data set with the appropriate logical record length and
PDM0205E
The Batch Request data set record format must be either fixed or variable
Reason:
The PDM Batch Request data set has an invalid record format. The data set must contain
either fixed length or variable length records. PDM will terminate further processing.
Action:
Reallocate the Batch Request data set with the correct attributes and resubmit the
request.
PDM0206E
The COMPARE THRU value (value) is greater than the derivation id element length
(value)
Reason:
The COMPARE THRU value is larger than the element record length defined in the
element type record for the derivation identifier specified. PDM will terminate the
BUILD action with a return code of 12.
Action:
The COMPARE THRU value must be no larger than the derivation file logical record
length (LRECL). Respecify the COMPARE THRU value so that it is less than or equal to the
data set LRECL identified. If the ROOT is an element, the COMPARE column values are
taken from the element type record. In that case, either modify the ROOT element type
record or specify a different element type.
PDM Messages
PDM0207E
The COMPARE THRU value (value) is greater than the derivation id data set LRECL
(value)
Reason:
The COMPARE THRU value is larger than the logical length (LRECL) of the derivation file
identified. PDM will terminate the BUILD action with a return code of 12.
Action:
The COMPARE THRU value must be no larger than the derivation file logical record
length (LRECL). Respecify the COMPARE THRU value so that it is less than or equal to the
data set LRECL identified. If the ROOT is an element, the COMPARE column values are
taken from the element type record. In that case, either modify the ROOT element type
record or specify a different element type.
PDM0416I
Note: the WIP files were not created at the users request
Reason:
PDM did not create the WIP files as part of Build processing because the BUILD WIP
statement specified the OPTIONS CREATE WIP NEVER clause.
Action:
None. If you want the WIP files to be created then remove the OPTIONS CREATE WIP
NEVER clause and resubmit the Build WIP request.
PDM1001E
WIP DDNAME or DSNAME must be specified for a BUILD operation
Reason:
The WIP location parameter was not specified in the BUILD WIP statement. PDM
requires a WIP DDNAME or a WIP DSNAME parameter.
Action:
Add the WIP DDNAME or WIP DSNAME clause to the BUILD WIP statement and
PDM Messages
PDM1002E
ROOT DDNAME, DSNAME or ENDEVOR location must be specified for a BUILD
operation
Reason:
The required ROOT location information was not specified in the BUILD WIP statement.
Action:
Add the appropriate ROOT DDNAME, ROOT DSNAME or ROOT location information to
the BUILD WIP statement and resubmit the request.
PDM1003E
DV1 DDNAME, DSNAME or ENDEVOR location must be specified for a BUILD operation
Reason:
The required Derivation 1 (DV1) location information was not specified in the BUILD WIP
statement.
Action:
Add the appropriate DV1 DDNAME, DV1 DSNAME or DV1 location information to the
BUILD WIP statement and resubmit the request.
PDM1004E
OUTPUT DDNAME, DSNAME or Endevor location must be specified for the MERGE
operation.
Reason:
You must specify an output location on the PDM Merge statement.
Action:
Specify a Merge output location and resubmit the job.
PDM Messages
PDM1005E
WIP DDNAME or DSNAME must be specified for a MERGE operation
Reason:
The required WIP location information was not specified in the MERGE statement.
Action:
Add the appropriate WIP DDNAME or WIP DSNAME to the MERGE statement and
PDM1006E
Header Block not found: A valid BUILD or MERGE operation must be specified
Reason:
A PDM member/element mask statement was encountered but a valid BUILD WIP or
MERGE statement was not found.
Action:
Verify that a valid BUILD WIP or MERGE statement was specified. Check the PDM Syntax
Request Report for any previous error messages. Correct any previous errors or add a
valid BUILD WIP or MERGE statement and resubmit the request.
PDM1007E
Invalid Syntax: OUTPUT member mask specification is not allowed on a BUILD
operation
Reason:
The OUTPUT member mask was found following a BUILD statement. The OUTPUT clause
is valid only after a MERGE statement.
Action:
Remove the OUTPUT mask clause. The Build operation requires the ROOT, DV1, DV2,
and WIP member mask clauses. The OUTPUT clause is used with the MERGE operation.
PDM Messages
PDM1008E
Invalid Syntax: ROOT member mask specification is not allowed on a MERGE
operation
Reason:
The ROOT member mask was found following a MERGE statement. The ROOT clause is
valid only after a BUILD statement.
Action:
Remove the Root mask clause. The MERGE operation requires the OUTPUT and WIP
member mask clauses. The ROOT clause is used with the Build operation.
PDM1009E
Invalid Syntax: DV1 member mask specification is not allowed on a MERGE operation
Reason:
The DV1 member mask was found following a MERGE statement. The DV1 clause is valid
only after a BUILD statement.
Action:
Remove the DV1 mask clause. The Merge operation requires the OUTPUT and WIP
member mask clauses. The DV1 clause is used with the Build operation.
PDM1010E
Invalid Syntax: DV2 member mask specification is not allowed on a MERGE operation
Reason:
The DV2 member mask was found following a MERGE statement. The DV2 clause is valid
only after a BUILD statement.
Action:
Remove the DV2 mask clause. The Merge operation requires the OUTPUT and WIP
member mask clauses. The DV2 clause is used with the Build operation.
PDM Messages
PDM1011E
Invalid Syntax: DV2 member mask specified but a DV2 location was not defined
Reason:
A DV2 member/element mask was specified but the BUILD statement did not contain a
DV2 clause. The DV2 location must be defined if a DV2 mask is specified.
Action:
Either add a DV2 clause to the BUILD statement to define the DV2 location or remove
the DV2 member/element mask clause.
PDM1012E
Invalid Syntax: Specify either DDNAME, DSNAME or ENDEVOR location information
Reason:
Multiple locations were specified for a given file location in the BUILD or MERGE
statement. For example, both WIP DSNAME and WIP DDNAME were specified. Only one
definition for each location is allowed.
Action:
Remove the incorrect location specification from the BUILD or MERGE statement. Only
one location definition can be specified.
PDM1013E
Invalid Syntax: All ENDEVOR location information was either missing or incorrect.
Reason:
The CA Endevor SCM location for the ROOT, DV1 or DV2 clauses were either missing
keywords, or contained incorrect values.
Action:
Correct the CA Endevor SCM location specification of the ROOT, DV1, and DV2 clauses.
Make sure the ENVIRONMENT, SYSTEM, SUBSYSTEM, TYPE and STAGE keywords are all
specified and that they contain correct values.
PDM Messages
PDM1014E
Invalid Syntax: The LEVEL specified is not in the range 00 through 99
Reason:
A location was specified for the ROOT, DV1 or DV2 location and the LEVEL option was
also specified but the level specified was not in the range 00 through 99, inclusive.
Action:
Specify a level number that is in the range 00 through 99, or remove the LEVEL keyword
to use the current level of the element.
PDM1015E
Invalid Syntax: ROOT member mask is required on a BUILD operation
Reason:
The ROOT member/element mask specified is blank. A non-blank member/element
mask is required.
Action:
Specify the appropriate, non-blank member mask in the ROOT clause.
PDM1016E
Invalid Syntax: OUTPUT member mask is required on a MERGE operation
Reason:
The OUTPUT member mask specified is blank. A non-blank member mask is required.
Action:
Specify the appropriate, non-blank member mask in the OUTPUT clause.
PDM1017E
DV2 DDNAME, DSNAME or ENDEVOR location must be specified for a BUILD operation
Reason:
The required Derivation 2 (DV2) location information was not specified in the PDM
BUILD statement.
Action:
Add the appropriate DV2 DDNAME, DV2 DSNAME or DV2 location information to the
BUILD statement and resubmit the request.
PDM Messages
PDM1018E
Invalid Syntax: The VERSION specified is not in the range 00 through 99
Reason:
An location was specified for the ROOT, DV1 or DV2 location and the VERSION option
was also specified but the version specified was not in the range 00 through 99,
inclusive.
Action:
Specify a version number that is in the range 00 through 99, or remove the VERSION
keyword to use the current level of the element.
PDM1019E
Invalid Syntax: STATS option requires OFF DETAILALL syntax
Reason:
The STATS statement was found but the statement parameters were coded incorrectly.
The format of the STATS statement is STATS OFF DETAIL or STATS OFF ALL.
Action:
Correct the STATS statement syntax. Specify STATS OFF ALL to suppress all PDM reports
or STATS OFF DETAIL to suppress the PDM Detail Report.
PDM1020E
Invalid Syntax: ROOT member mask contains invalid characters
Reason:
The ROOT member/element mask specified contains one or more invalid characters.
Action:
Correct the member/element mask value. For the member/element naming convention,
see the Parallel Development Option Guide.
PDM Messages
PDM1021E
Invalid Syntax: DV1 member mask contains invalid characters
Reason:
The DV1 member/element mask specified contains one or more invalid characters.
Action:
PDM1022E
Invalid Syntax: DV2 member mask contains invalid characters
Reason:
The DV2 member/element mask specified contains one or more invalid characters.
Action:
PDM1023E
Invalid Syntax: WIP member mask contains invalid characters
Reason:
The WIP member mask specified contains one or more invalid characters.
Action:
Correct the member mask value. For the member naming convention, see the Parallel
Development Option Guide.
PDM1024E
Invalid Syntax: OUTPUT member mask contains invalid characters
Reason:
The OUTPUT member/element mask specified contains one or more invalid characters.
Action:
Correct the member mask value. For the member naming convention, see the Parallel
PDM Messages
PDM1029E
Invalid Syntax: Last statement is not terminated with a period. The job will be
terminated
Reason:
A PDM BUILD, MERGE, STATS or mask statement was not terminated with a period.
PDM syntax rules require that all statements end with a period.
Action:
Add the missing period to the PDM statement. Also verify that no other errors were
detected with the PDM control statements. If any other errors were detected, correct
those errors and resubmit the request.
PDM1037E
No PDM requests were generated
Reason:
The PDM batch interface was executed but the Batch Request data set did not contain
any valid PDM control statements.
Action:
Verify that the correct Batch Request data set was specified. Also, verify that the PDM
control statements specified are syntactically correct. For any errors with the PDM
control statements, see the PDM Syntax Request Report.
PDM1038E
Invalid Syntax: DV1 member mask is required on a BUILD operation
Reason:
The DV1 member/element specified is blank. A non-blank member/element mask is
required.
Action:
Specify the appropriate, non-blank member mask in the Derivation 1 clause.
PDM Messages
PDM1039E
Invalid Syntax: DV2 member mask is required on a BUILD operation
Reason:
The DV2 member/element specified is blank. A non-blank member/element mask is
required.
Action:
Specify the appropriate, non-blank member mask in the DV2 clause.
PDM1040E
Invalid Syntax: The COMPARE from column value is non-numeric
Reason:
The BUILD WIP COMPARE from column value specified is non-numeric. The clause can
contain only numeric characters in the range 1 to 256, inclusive.
Action:
Correct the COMPARE from value specified in the BUILD WIP statement.
PDM1041E
Invalid Syntax: The COMPARE THRU column value is non-numeric
Reason:
The Build WIP COMPARE THRU column value specified is non-numeric. The clause can
contain only numeric characters in the range 1 to 256, inclusive.
Action:
Correct the COMPARE THRU value specified in the BUILD WIP statement.
PDM Messages
PDM1042E
Invalid Syntax: The WRITE STATISTICS TO must specify a non-blank DDNAME or
DSNAME
Reason:
The DDNAME or DSNAME specified in the WRITE STATISTICS TO clause contained a
blank value. The DDNAME or DSNAME must specify a valid, non-blank identifier.
Action:
Correct the WRITE STATISTICS TO clause so that a valid identifier is specified with the
DDNAME or DSNAME keyword.
PDM1045E
Invalid Syntax: The WRITE STATISTICS TO statement must specify DDNAME or
DSNAME but not both
Reason:
The WRITE STATISTICS TO clause must contain a DDNAME or a DSNAME but it cannot
contain both keywords.
Action:
Correct the WRITE STATISTICS TO clause so that only the DDNAME or the DSNAME
keyword is specified.
PDM1046E
Invalid Syntax: The MERGE OUTPUT statement is invalid when CREATE WIP NEVER is
specified
Reason:
The Build WIP request cannot contain a MERGE OUTPUT clause if the OPTIONS CREATE
WIP NEVER clause is also specified.
Action:
Remove either the MERGE OUTPUT clause or the OPTIONS CREATE WIP NEVER clause
from the Build request.
PDM Messages
PDM1047E
Invalid Syntax. The BUILD WIP MERGE OUTPUT statement must specify DDNAME,
DSNAME or Endevor location.
Reason:
You must specify an output location on the BUILD WIP MERGE OUTPUT statement.
Action:
Specify a Merge output location and resubmit the job.
PDM1048W
DELETE WIP is ignored without the MERGE OUTPUT statement
Reason:
The OPTIONS DELETE WIP AFTER MERGE clause was specified in the Build request but
the MERGE OUTPUT clause was not also specified. PDM will ignore the OPTIONS DELETE
WIP AFTER MERGE clause.
Action:
None. To eliminate the message, remove the OPTIONS DELETE WIP AFTER MERGE
clause from the Build request.
PDM1049W
LANGUAGE is ignored without the MERGE OUTPUT statement
Reason:
The OPTIONS LANGUAGE clause was specified in the Build request but the MERGE
OUTPUT clause was not also specified. PDM will ignore the OPTIONS LANGUAGE clause.
Action:
None. To eliminate the message, remove the OPTIONS LANGUAGE clause from the Build
request.
PDM Messages
PDM1051E
Invalid Endevor environment name on MERGE OUTPUT statement.
Reason:
An output CA Endevor SCM location was specified for the merge. The environment
name used is invalid.
Action:
Specify a correct environment name and resubmit the job.
PDM1052E
Invalid Endevor system name on MERGE OUTPUT statement.
Reason:
An output CA Endevor SCM location was specified for the merge. The system name used
is invalid.
Action:
Specify a correct system name and resubmit the job.
PDM1053E
Invalid Endevor subsystem name on MERGE OUTPUT statement.
Reason:
An output CA Endevor SCM location was specified for the merge. The subsystem name
is invalid.
Action:
Specify a correct subsystem name and resubmit the job.
PDM1054E
Invalid Endevor type name on MERGE OUTPUT statement.
Reason:
An output CA Endevor SCM location was specified for the merge. The type name is
invalid.
Action:
Specify a correct type name and resubmit the job.
PDM Messages
PDM1055E
Invalid Endevor stage on MERGE OUTPUT statement.
Reason:
An output CA Endevor SCM location was specified for the merge. The stage is invalid.
Action:
Specify a correct stage name and resubmit the job.
PDM1056E
Invalid Processor Group Name.
Reason:
The processor group name is not defined for the type specified on the merge output CA
Endevor SCM location.
Action:
Specify a correct processor group name and resubmit the job.
PDM1057W
DELETE NDVR DV1 DV2 is ignored without the MERGE OUTPUT Endevor location
statement.
Reason:
The DELETE NDVR DV1 DV2 clause is only applicable when the merge is to an CA
Action:
Nothing.
PDM1058W
SYNC NDVR OUTPUT is ignored without the MERGE OUTPUT Endevor location
statement.
Reason:
The SYNC NDVR OUTPUT clause is only applicable when the merge is to an CA Endevor
SCM location.
Action:
Nothing.
PDM Messages
PDM1059W
BYPASS GENERATE PROCESSOR is ignored without the MERGE OUTPUT Endevor
location statement.
Reason:
The BYPASS GENERATE PROCESSOR clause is only applicable when the merge is to an CA
Action:
Nothing.
PDM1060W
PROCESSOR GROUP NAME is ignored without the MERGE OUTPUT Endevor location
statement.
Reason:
The PROCESSOR GROUP NAME clause is only applicable when the merge is to an CA
Action:
Nothing.
PDM2001E
$BSTGLST function error. RESULT=result code
Reason:
The PDM Build WIP I/O routine received an error from the $BSTGLST service. The
$BSTGLST service that was invoked is identified by function. The $BSTGLST service
returned the error code identified by result code
Action:
If the named function is ACQUIRE or INIT and the named result code is $BGETSTG, it
implied that PDM was unable to obtain virtual storage for the request.
If PDM is executing in batch mode, increase the REGION parameter specified in the PDM
batch EXEC or JOB JCL statement. If PDM is executing in foreground mode, signon to
TSO with a larger region size.
For any other result code, retry the operation. If the problem persists use the OPTIONS
DISABLE PERFORMANCE ENHANCEMENT clause in the BUILD or MERGE statement or set
the disable the build wip and merge performance enhancement on the PDM User
Defaults screen to Y. For more information on these actions, see the Parallel
PKEX Messages
PKEX Messages
PKEX messages are generated during package processing. The following list of PKEX
messages includes possible causes and corrective actions to take in error situations.
PKEX100E
STORAGE ERROR OCCURRED DURING function/subfunction/ [BEFOREAFTER]
PACKAGE EXIT PROCESSING. CONTACT ENDEVOR TECHNICAL SUPPORT
Reason:
CA Endevor SCM encountered a storage error when executing the package exit function
named in the message.
Action:
PKEX101E
ERROR OCCURRED DURING GENPKGID PROCESSING. USEREXIT RETURN BLANK
PACKAGE ID.
Reason:
Either the user exit has sent back a blank ID field, or CA Endevor SCM has cleared the
field.
Action:
Using the trace facility, verify what the user exit is sending back to CA Endevor SCM in
the PECBPKID field. If the PECBPKID field is not blank, contact your administrator.
PKEX101W
WARNING: ONLY GENPKGID FUNCTION CAN REQUEST UPDATE OF PECBDS. REQUEST
IGNORED.
Reason:
The exit program has requested an update of the PECBDS control block. CA Endevor
SCM ignored the request because the exit was not invoked by the GENPKGID function.
Action:
None.
PKEX Messages
PKEX102E
ERROR OCCURRED DURING UPDATING THE $PFILDS. DDNAME SUPPLIED BY USEREXIT
NOT ALLOCATED.
Reason:
CA Endevor SCM could not update the $PFILDS control block because the data set
named by the exit program was not allocated.
Action:
Allocate the data set and rerun the job.
PKEX103E
SETUP OPTION ERROR OCCURRED DURING function/subfunction/ [BEFOREAFTER]
PACKAGE EXIT PROCESSING. CONTACT TECHNICAL SUPPORT
Reason:
The setup module in the exit program for the named exit function contains an error.
Action:
PKEX104E
DATE FORMAT ERROR OCCURRED DURING function/subfunction/ [BEFOREAFTER]
PACKAGE EXIT $PREQPDS UPDATE.
Reason:
The exit program for the function identified in the message has formatted data
incorrectly for a requested update of the $PREQDS control block.
Action:
Modify the program and resubmit the job.
PKEX Messages
PKEX105W
WARNING: function name FUNCTION CANNOT REQUEST $PREQPDS UPDATE.
REQUEST IGNORED.
Reason:
Exit programs for the named exit function cannot request an update of $PFILDS.
Action:
Remove the $PFILDS update request from the exit program. Check each exit function
you are enabling to see if any of the $PFILDS fields can be filled in.
PKEX106W
WARNING: function name FUNCTION CANNOT REQUEST $PFILDS UPDATE. REQUEST
IGNORED.
Reason:
The exit program for the function identified in the message has requested an update of
the $PFILDS control block. Exits for this function cannot request an update of this block.
Action:
Modify the program as necessary, and resubmit the job.
PKEX107I
PACKAGE EXIT PROGRAM program name HAS NOT ENABLED ITSELF FOR THIS xx RUN
Reason:
Informational message. The package exit program program-name is not enabled to run
in a BATCH mode.
Action:
None. Refer to the C1UEXITS table if you want to change the settings.
PKEX Messages
PKEX108E
PACKAGE EXIT PROGRAM module-name MODIFIED PECBBOEN WITH AN INVALID
VALUE "character" - CHOOSE "Y" OR "N"
Reason:
The named user exit modified the "Backout Enabled" indicator with an invalid character.
Y (YES) and N (NO) are the only valid values.
Action:
Correct the user exit program and rerun.
PKEX109E
PACKAGE EXIT PROGRAM module-name MODIFIED PECBPSHR WITH AN INVALID
Reason:
The named user exit modified the "Package Shareability" indicator with an invalid
character. Y (YES) and N (NO) are the only valid values.
Action:
PKEX110E
PACKAGE EXIT PROGRAM module-name MODIFIED PECBDARC WITH AN INVALID
Reason:
The named user exit modified the "Delete after Archiving" indicator with an invalid
character. Y (YES) and N (NO) are the only valid values.
Action:
PKEX Messages
PKEX111E
PACKAGE EXIT PROGRAM module-name modified PECBPAPD "character" - CHOOSE
"Y" or "N"
Reason:
The named user exit modified the "Append SCL" indicator with an invalid character. Y
(YES) and N (NO) are the only valid values.
Action:
PKEX112E
PACKAGE EXIT PROGRAM module_name BLANKED OUT PREQCOMM - THIS FIELD IS
REQUIRED.
Reason:
The named user exit blanked out the "Comment" field. The comment (package
description) is required.
Action:
PKEX113W
PACKAGE EXIT PROGRAM program name DID NOT SUPPLY AN SCL FILE DDN OR
DDN/MEMBER FOR THE function name FUNCTION
Reason:
The ARCHIVE CREATE, EXPORT, or REPLACE function is being processed. The package
exit program program-name did not supply a DD name override for the SCL file.
Action:
None. This is a warning message to inform you that the exit is not overriding the SCL file.
PKEX Messages
PKEX114E
PACKAGE EXIT PROGRAM program name MEMBER NAME NOT ALLOWED FOR A
SEQUENTIAL SCL FILE - function FUNCTION
Reason:
exit program program-name supplied a member name, but the data set is a sequential
file.
Action:
Modify your exit program. Remove the member name or specify the name of a
partitioned data set.
PKEX115E
PACKAGE EXIT PROGRAM program name MEMBER NAME REQUIRED FOR
PARTITIONED SCL FILE - function FUNCTION
Reason:
exit program program-name supplied the name of a partitioned data set, but it did not
supply a member name.
Action:
Modify your exit program. Supply a member name or specify the name of a sequential
data set.
PKEX116I
PACKAGE EXIT PROGRAM program name RETURNED WITH RC=04 BUT DIDN'T SET
UPDATE OR DATA REQUEST FLAGS
Reason:
The package exit program program-name set the return code to a value of 4, indicating
that changes were made, but the data was not modified.
Action:
PKEX Messages
PKEX117W
PACKAGE EXIT PROGRAM program name: HFS FILE UPDATES NOT SUPPORTED
Reason:
Informational message. HFS file updates are not supported through exits.
Action:
None.
PKEX118E
PACKAGE EXIT PROGRAM @08CY MODIFIED PECBPROM WITH AN INVALID VALUE
"@1CY" - CHOOSE "Y" OR "N"
Reason:
This message indicates that the promotion package indicator value in the PECBPROM
field is invalid.
Action:
The logic in the user defined package exit 7 sets the value of the PECBPROM field to an
invalid value. Edit the program and set this field to a value of Y or N. This program must
be compiled and link-edited after completing the source changes.
PKEX119E
The package exit program name updated PREQCVAL with value. Only "Y", "N" or "W"
are valid.
Reason:
PREQCVAL was updated with an invalid value.
Action:
Correct the package exit program to update PREQCVAL with a valid value.
PKEX Messages
PKEX120I
Exit program name has changed the component validation setting from value1 to
value2
Reason:
The exit program changed the component validation setting.
Action:
None.
PKEX200E
USEREXIT REQUESTED INV DATA TYPE DURING function/subfunction/
[BEFOREAFTER] PACKAGE EXIT PROCESSING. DATA TYPE = ACTION
Reason:
An exit program for the function identified in the message has requested action
information from CA Endevor SCM. This is an invalid request for this exit point.
Action:
PKEX201E
USEREXIT REQSTD DATA AFTER EOF OR NOT-FOUND COND. AT
function/subfunction/[BEFOREAFTER] EXIT POINT. DATA TYPE= ACTION.
Reason:
An exit program for the function identified in the message has requested action
information from CA Endevor SCM after an end-of-file or not-found condition was
encountered. This is an invalid request.
Action:
PKEX Messages
PKEX202E
EXTRACT ERROR OCCURRED DURING function/subfunction/[BEFOREAFTER] PACKAGE
EXIT PROCESSING. DATA TYPE = ACTION.
Reason:
An exit program for the function identified in the message encountered an error when
attempting to extract action information from CA Endevor SCM.
Action:
PKEX203E
USEREXIT REQSTD INV DATA TYPE DURING function/subfunction/ [BEFOREAFTER]
PKG EXIT PROCESSING. DATA TYPE = APPROVER
Reason:
An exit program for the function identified in the message has requested approver
Action:
PKEX204E
USEREXIT REQSTD DATA AFTER EOF OR NOT-FOUND COND. AT
function/subfunction/[BEFOREAFTER] EXIT POINT. DATA TYPE= APPROVER
Reason:
An exit program for the function identified in the message has requested approver
Action:
PKEX Messages
PKEX205E
EXTRACT ERROR OCCURRED DURING function/subfunction/ [BEFOREAFTER]
PACKAGE EXIT PROCESSING. DATA TYPE = APPROVER
Reason:
attempting to extract approver information from CA Endevor SCM.
Action:
PKEX206E
USEREXIT REQUESTED INVALID DATA TYPE DURING function/subfunction/
[BEFOREAFTER] PKG EXIT PROCESSING. DATA TYPE = BACKOUT
Reason:
An exit program for the function identified in the message has requested backout
Action:
PKEX207E
USEREXIT REQSTD DATA AFTER EOF OR NOT-FOUND CONDITION AT
function/subfunction/[BEFOREAFTER] EXIT POINT. DATA TYPE = BACKOUT
Reason:
An exit program for the function identified in the message has requested backout
Action:
PKEX Messages
PKEX208E
EXTRACT ERROR OCCURRED DURING function/subfunction/ [BEFOREAFTER]
PACKAGE EXIT PROCESSING. DATA TYPE = BACKOUT
Reason:
attempting to extract backout information from CA Endevor SCM.
Action:
PKEX210E
[BEFOREAFTER] PKG EXIT PROCESSING. DATA TYPE = SHIP
Reason:
An exit program for the function identified in the message has requested ship
Action:
PKEX211E
USEREXIT REQSTD DATA AFTER EOF OR NOT-FOUND COND. AT function/subfunction/
[BEFOREAFTER] EXIT POINT. DATA TYPE = SHIP
Reason:
An exit program for the function identified in the message has requested ship
Action:
PKEX Messages
PKEX212E
EXTRACT ERROR OCCURRED DURING function/subfunction/[BEFOREAFTER] PACKAGE
EXIT PROCESSING. DATA TYPE = SHIP
Reason:
attempting to extract ship information from CA Endevor SCM.
Action:
PKEX213E
[BEFOREAFTER] PACKAGE EXIT PROCESSING. DATA TYPE = SCL
Reason:
A user program has requested an SCL data type. This is an invalid request for the named
function and subfunction.
Action:
Modify the user program as necessary.
PKEX214E
USEREXIT REQSTD DATA AFTER EOF OR NOT-FOUND COND. AT function/subfunction/
[BEFOREAFTER] EXIT POINT. DATA TYPE = SCL
Reason:
A user program has requested an SCL data type after an EOF or not-found condition was
encountered. This is an invalid request for the named function and subfunction.
Action:
PKEX Messages
PKEX215E
EXTRACT ERROR OCCURRED DURING function/subfunction/ [BEFORE AFTER]
PACKAGE EXIT PROCESSING. DATA TYPE = SCL
Reason:
A user program has requested an SCL data type, but an extract error occurred during
package exit processing.
Action:
PKEX216W
WARNING: INV CANCEL REQUEST SENT FROM EXIT FUNCTION function/subfunction.
CANCEL ONLY VALID AT BEFORE EXIT POINTS
Reason:
A user program has sent a cancel request at an after-exit point. This is an invalid request
for the named function and subfunction.
Action:
PKEX217E
CREATE APPROVER ERROR OCCURRED DURING
function/subfunction/[BEFOREAFTER] PKG EXIT PROCESSING - RC=return code,
REASON=reason code
Reason:
An error occurred trying to create an approver.
Action:
Check for additional messages.
PKEX Messages
PKEX300E
PACKAGE EXIT MESSAGE DATA SET ALLOCATION ERROR
Reason:
CA Endevor SCM was unable to allocate the package exit message data set. An
accompanying message explains the reason for the allocation failure.
Action:
Allocate the data set.
PKEX303E
NOTIFY UTILITY SYNTAX ERROR. CHECK $NOTIFY
Reason:
CA Endevor SCM has encountered a syntax error in the $notify macro.
Action:
Correct the error then resubmit the job.
PKEX400I
APPROVER GROUP approver group name ADDED FROM EXTERNAL SOURCE FOR
PACKAGE ID package name
Reason:
Action:
None.
PKEX401E
ADD APPROVER REQUEST ONLY VALID FOR BEFORE/CAST EXIT POINT. USEREXIT
REQUESTED AT [BEFORE AFTER] function
Reason:
The package exit facility only allows user exits to add approver groups at the before-cast
exit point. This exit program tried to add an approver group at a different exit point.
Action:
Recode the exit program to enable the Add Approver group code only at the before-cast
exit point.
PKEX Messages
PKEX402E
USEREXIT SUPPLIED APPROVER GROUP HAS FORMAT ERROR. CHECK INPUT
REQUIREMENTS IN THE ADMINISTRATORS GUIDE
Reason:
The user exit has attempted to add one or more approver groups that do not meet
approver group control block format requirements.
Action:
Review the section on the $PAPPREQ control block in the Exits Guide for format
specifications.
PKEX403E
USEREXIT SUPPLIED APPROVER GROUP approver group name IS NOT VALID. CHECK
SOURCE OF LITERAL
Reason:
The user exit has attempted to add an approver to an approver group name that is not
valid.
An exit can add an approver to an approver group only after a request for data on
approvers is processed. If the exit tries to add the approver before a request is
processed, this message is issued.
This message is also issued when the package exit facility tries to update the PREQAPGP
field in the $PREQPDS with the values in the PECBUSER or PREQAPID fields, and the
value in the PREQAPGP field is invalid.
Action:
To inactivate, clear these fields in the PREQPDS.
PKEX404I
USEREXIT SUCCESSFULLY UPDATED APPROVER GROUP approver group name WITH ID
user id
Reason:
Action:
None.
PKEX Messages
PKEX404E
GENPKGID EXIT ERROR. PACKAGE ID package id IS WILDCARDED. MUST SEND FULLY
QUALIFIED ID.
Reason:
The user exit has sent back a wildcarded package ID. This is not allowed.
Action:
Check the user exit code.
PKEX405E
GENPKGID EXIT ERROR. PACKAGE ID package id ALREADY EXISTS. MUST SEND UNIQUE
PACKAGE ID.
Reason:
The user exit has sent back a package ID that already exists. This is not allowed.
Action:
Check the code in the exit program.
PKEX407E
GENPKGID EXIT PROCESSING ERROR.
Reason:
The user exit has enabled the GENPKGID exit point. There was an error that does not fit
into a specific category.
Action:
Use the trace facility to check what the exit is sending back to CA Endevor SCM in the
PECBPKID field. If this does not solve the problem, contact your administrator.
PKMR Messages
PKEX500E
PACKAGE PROCESSING DENIED BY SECURITY EXIT RC(return code)+
Reason:
A package action was denied due to the results of a security call. The return code and
reason code indicates why the action was denied.
Action:
Contact the administrator for additional assistance. The EN$TRESI security trace or the
log facility within the security package installed at your site can be used to determine
the security rule that failed.
Also, this message can be issued if the person attempting to execute the package is not
an approver of the package. If the client has selected MIGRATE and has the package
security, the message could be caused either by an approver or ESI problem - both will
have to be checked.
PKMR Messages
PKMR messages are generated during CA Endevor SCM package processing. The
following list of PKMR messages includes possible causes and corrective actions to take
in error situations.
PKMR000E
NO PACKAGES FOUND TO MATCH package-id
Reason:
A request was made to access the package identified in the message, but the package
could not be found.
Action:
Make sure that the package ID specification is correct.
PKMR001E
PACKAGE package-id ALREADY EXISTS
Reason:
A request was made to create a package, but the package already exists.
Action:
Select another package ID.
PKMR Messages
PKMR002E
PACKAGE package-id IS NOT MODIFIABLE
Reason:
A request was made to change the package identified in the message, however the
package is not in a state that allows it to be modified.
Action:
The package must be restored in order to modify it.
PKMR003E
NO PACKAGES EXIST
Reason:
No packages were found to match the package selection criteria.
Action:
Make sure that the selection criteria are correct.
PKMR004E
NO APPROVERS EXIST FOR PACKAGE package-id
Reason:
A request was made to display the approvers associated with the package identified in
the message, however no approvers exist.
Action:
None.
PKMR005E
NO SCL STATEMENTS EXIST FOR PACKAGE package-id
Reason:
A request was made to display/extract the SCL statements associated with the package
identified in the message, however no SCL statements exist.
Action:
None.
PKMR Messages
PKMR006E
NO ELEMENT/MEMBER IDENTIFICATION RECORDS EXIST FOR PACKAGE package-id
Reason:
A request was made to display/extract the element/member identification records
associated with the package identified in the message, however no identification
records exist.
Action:
None.
PKMR007E
NO BACK-OUT INFORMATION EXISTS FOR PACKAGE package-id
Reason:
A request was made to display/extract the backout information associated with the
package identified in the message, however no backout information exist.
Action:
None.
PKMR009E
PACKAGE STATUS NOT IN-APPROVAL - REQUIRED FOR CREATE APPROVER FUNCTION
Reason:
Internal error.
Action:
PKMR010E
ONE OR MORE PACKAGE CAST ERRORS HAVE OCCURRED
Reason:
A request was made to cast this package, but errors occurred during cast processing.
Action:
PKMR Messages
PKMR011E
INTERNAL ERROR - CREATE BACK-OUT REQUEST FOR A MBR WITH NO
CORRESPONDING IDENTIFICATION RECORD
Reason:
The specified record type was deleted outside of CA Endevor SCM or an internal error
has occurred.
Action:
Reset the package or contact CA Technical Support.
PKMR012C
INTEGRITY ERROR. PACKAGE yyyy HAS BEEN MODIFIED BY EXTERNAL MEANS
Reason:
The package content has been modified outside of CA Endevor SCM, thus invalidating
the package. However the delete action was completed successfully.
The message variable yyyy is the identifier of the record (the package name).
Action:
None.
PKMR012E
INTEGRITY ERROR. xxxx RECORD yyyyyyyy HAS BEEN MODIFIED BY EXTERNAL MEANS
Reason:
The package content has been modified outside of CA Endevor SCM, thus invalidating
the package.
The message variables are:
xxxx
DSN - Dataset name
HDR - Package header
APPR - Package approver
SCL - Package SCL
ID - Package SOURCE-ID
B/O - Package backout
STUB - Package stub
PKMR Messages
RPT - Package report

CORR - Correlation
DEST - Destination
MAP - Shipment mapping
SHIP - Package Shipment
yyyyyyyy
The identifier of the record (the package name or the DSN, MAP, or destination
ID)
Action:
If the identifier names a specific package then the package must be deleted. If the
record-ID is not related to a specific package then delete this record (for example
DELETE DESTINATION). Also, try to determine when this record became corrupted and
what may be the cause of the corruption. Package records may not be updated outside
of CA Endevor SCM. See if the package can be reloaded from a package UNLOAD file.
This package can only be deleted through Batch Package processing or through an API
program.
PKMR013E
PACKAGE BACK-OUT ERROR(S) HAVE OCCURRED
Reason:
A request was made to back out this package, but errors occurred during back out
processing.
Action:
PKMR014E
PACKAGE BACK-IN ERROR(S) HAVE OCCURRED
Reason:
A request was made to back in this package, but errors occurred during back in
processing.
Action:
PKMR Messages
PKMR015E
ELEMENT STUB RECORD NOT FOUND
Reason:
has occurred.
Action:
PKMR016E
NO CAST REPORT RECORDS EXISTS
Reason:
has occurred.
Action:
PKMR017E
NO {DESTINATIONS | CONNECTIONS} FOUND TO MATCH {destination id | connection
id}
Reason:
There are no destinations or connections on file that match the requested destination ID
(specific or wildcarded).
Action:
None
PKMR018W
NO SHIPMENTS FOUND
Reason:
No shipment records are found as a result of the List Package Ship function.
Action:
None
PKMR Messages
PKMR019E
THE DATA SET MAPPING RULE WAS NOT FOUND
Reason:
The host data set mapping rule does not exist for the destination in question.
Action:
None
PKMR020E
CORRELATION ALREADY EXISTS
Reason:
A correlation record already exists for this package.
Action:
Make sure the package ID, correlation type, and correlation ID values are correct.
PKMR021R
CORRELATION DOES NOT EXIST
Reason:
The correlation record specified does not exist for this package.
Action:
PKMR022E
INVALID CORRELATION DATA ELEMENT, ELEMENT element name
Reason:
Internal error.
Action:
Contact CA Technical Support for assistance.
PKMR Messages
PKMR023E
INVALID CORRELATION TYPE: X "type value"
Reason:
The correlation type value supplied is invalid. The valid correlation type values are 2 for
Info/Man, 3 for user-defined, and 4 for enterprise.
Action:
Make sure your request contains a valid type value.
PKMR024E
CORRELATION DATA ELEMENT NOT SUPPLIED
Reason:
Internal error.
Action:
Contact CA Technical Support for assistance.
PKMR025E
CORRELATION RECORD NOT FOUND
Reason:
The correlation record specified does not exist for this package.
Action:
PKMR032E
NOT DYNAMIC APPROVER ONLY THE DYNAMIC APPROVER GROUP CAN BE DELETED
FROM A PACKAGE
Reason:
The delete package approver group action is valid only for the Dynamic Approver group.
This is an internal error.
Action:
PKMR Messages
PKMR033E
APPROVER NOT FOUND THE APPROVER ID WAS NOT FOUND IN THE PACKAGE
APPROVER GROUP RECORD
Reason:
A request was made to update or delete an approver in the Dynamic Approver group
package approver record. However, the approver ID was not found in the record. This is
an internal error.
Action:
PKMR034E
INVALID APP GROUP INTERNAL ERROR - NO APPROVER IDS EXIST IN APPROVER
GROUP RECORD
Reason:
The package approver group record does not contain any approver IDs. In the case of
the Dynamic Approver group record, this is an invalid situation. This is an internal error.
Action:
PKMR035E
INVALID PARAMETER INTERNAL ERROR - QUORUM AND REQUIRED ONLY VALID FOR
DYNAMIC APPROVER
Reason:
An internal error has occurred. Invalid parameters were specified on the request to
update or create a package approver group record. The quorum and required
parameters can only be specified when creating or updating the Dynamic Approver
package approver record.
Action:
PKMR Messages
PKMR036E
MISSING PARAMETER INTERNAL ERROR - THE APPROVER PARAMETER IS MISSING
Reason:
An internal error has occurred. The approver ID parameter was not passed when issuing
a request to create or update a package approver group record. The approver
parameter must be passed if the group name is not Dynamic Approver or if the package
approver record does not yet exist.
Action:
PKMR037E
USER NOT AUTHORIZED APPROVER ID CAN BE UPDATED ONLY BY SUPERUSER OR
USER WHO ADDED APPRVR
Reason:
An internal error has occurred. An approver ID entry in the Dynamic Approver package
approver group can be updated only by the user who originally added the entry or by a
superuser.
Action:
PKMR038E
APPROVER NOT ADDED THE DYNAMIC APPROVER GROUP CANNOT CONTAIN MORE
THAN SIXTEEN APPROVERS
Reason:
An internal error has occurred. The Dynamic Approver package approver record can
contain a maximum of 16 approvers.
Action:
PKMR Messages
PKMR039E
QUORUM CANNOT BE 0 THE QUORUM VALUE CANNOT BE ZERO IF THERE ARE NO
REQUIRED APPROVERS
Reason:
The user specified a quorum value of zero when attempting to create or update the
Dynamic Approver record. A quorum of zero is not valid if there are no required
approvers.
Action:
Specify a quorum value between one and the number of approvers. Make sure that this
value is greater than the number of approvers who have already approved the package.
PKMR040E
QUORUM VALUE TOO SMALL THE QUORUM VALUE MUST BE GREATER THAN THE
NUMBER OF APPROVALS
Reason:
The user specified a quorum value that is less than or equal to the number of approvers
who have approved the package. This value is invalid because it would logically change
the status of the Dynamic Approver group to APPROVED, something that should only
happen during REVIEW APPROVAL processing.
Action:
Specify a quorum value that is greater than the number of approvers who have already
approved this package.
PKMR041E
DUPLICATE APPROVER ID THE APPROVER ID IS ALREADY SPECIFIED
Reason:
The user specified an approver ID that already appears on the Dynamic Approver panel.
Action:
Remove the duplicate approver ID from the panel.
PKMR Messages
PKMR042E
CANNOT UPDATE/DELETE APPROVER ID APPROVER HAS APPROVED PACKAGE AND
CANNOT BE UPDATED OR DELETED
Reason:
An internal error has occurred. The approver has approved the package and therefore
cannot be updated.
Action:
PKMR043E
CANNOT DELETE DYNAMIC APPROVER GROUP. GROUP CANNOT BE DELETED IF AT
LEAST ONE APPROVER HAS APPROVED PKG
Reason:
An internal error has occurred. At least one of the approvers in the Dynamic Approver
package approver group has approved the package. Therefore the request to delete the
Dynamic Approver group cannot be honored.
Action:
PKMR044E
INVALID USERID
Reason:
The user specified an approver ID that begins with a number.
Action:
Specify a valid TSO user ID as the approver ID.
PKMR Messages
PKMR100E
RC=return code-reason code ALLOCATION ERROR ddname - dsname
Reason:
An allocation occurred during package processing for the data set name identified in the
message.
Action:
Refer to the return code-reason code to determine what corrections are required.
PKMR101I
CAUTIONARY MESSAGES ISSUED DURING CAST PROCESSING
Reason:
Informational message. This message serves as a header for other cast-related messages
to follow.
Action:
None.
PKMR102E
PACKAGE IN USE BY ANOTHER JOB OR USER - TRY LATER
Reason:
This package is in use by another job or user.
Action:
Try again at a later time.
PKMR103E
AN ABEND OCCURRED DURING PACKAGE PROCESSING
Reason:
This message serves as a header for other package-related messages to follow.
Action:
Review the messages that follow to determine the cause of the problem.
PKMR Messages
PKMR104C
PKG CONTAINS MULTIPLE ACTIONS THAT REFERENCE THE SAME INVENTORY
LOCATION
Reason:
This package contains multiple actions against the same element.
Action:
Modify or remove actions against the same elements.
PKMR105E
PATH VALIDATION FAILED
Reason:
Pathname either does not exist or is inaccessible.
Action:
Determine the cause. You may need to create this directory or restore it.
PKMR110E
RC=return code-reason code VSAM i/o function ERROR - dsname
Reason:
A VSAM I/O error occurred during package processing.
Action:
Refer to the return code-reason code to determine what corrections are required.
PKMR117E
INTERNAL ERROR - INVALID FMID OF PKG HEADER FOR PKGNOTES
Reason:
Internal error.
Action:
PKMR Messages
PKMR118E
RESERVED NAME, NONAPPVR, CANNOT BE USED FOR APPROVER GROUP NAME
Reason:
The approver group name of NONAPPVR is reserved.
Action:
Choose a different name for your approver group.
PKMR119E
APPROVE/DENY FUNCTION ATTEMPTED BY NON-APPROVER
Reason:
You are attempting to approve or deny a package for which you are not an approver.
Action:
None.
PKMR120E
PACKAGE package-id IN USE AND NOT AVAILABLE AT THIS TIME
Reason:
The package ID identified in the message is currently being modified or used by another
user.
Action:
Retry the request at a later time.
PKMR Messages
PKMR121E
DEL HISTORY ERROR.
THE ONLY VALID VALUES FOR DELETE PROMOTION HIST ARE: "Y" OR "N"
Reason:
A commit package action included an incorrectly coded Delete Promotion History
option.
Action:
Set the Delete Promotion History option to N to retain all the promotion history
associated with the previous versions of the promotion package you are committing. Or
set the option to Y, to delete all the promotion history associated with the previous
versions of the promotion package.
PKMR123E
PROMOTION PACKAGE EXISTS
THE CREATE/MODIFY PACKAGE ID IS AN EXISTING PROMOTION PACKAGE
Reason:
You attempted to create or modify a package and specified a package ID for the new
promotion package that is the same as a package ID that is already in use.
Action:
Specify another package ID that is not already in use.
PKMR130I
BACKOUT OF ELEMENT WAS SUCCESSFUL
Reason:
This is an informational message. The outputs for the specified element action were
backed out without error.
Action:
None.
PKMR Messages
PKMR131I
BACKIN OF ELEMENT WAS SUCCESSFUL
Reason:
This is an informational message. The outputs for the specified element action were
backed in without error.
Action:
None.
PKMR132E
BACKOUT OF ELEMENT HAD ERRORS
Reason:
The backout of outputs for the specified element action did not complete successfully.
Action:
Review the output report generated as a result of executing this action.
PKMR133E
BACKIN OF ELEMENT HAD ERRORS
Reason:
The backin of outputs for the specified element action did not complete successfully.
Action:
Review the output report generated as a result of executing this action.
PKMR134E
UNABLE TO BACK-OUT ELEMENT -- ACTION IS ALREADY BACKED OUT
Reason:
The element action you selected has already been backed out.
Action:
If you are not sure which element actions have been backed out, run a CONRPT72
Package Detail report or view the Element Action Backout panel, accessible from the
Backout Package panel.
PKMR Messages
PKMR135E
UNABLE TO BACK-IN ELEMENT -- ACTION IS NOT BACKED OUT
Reason:
The element action you selected cannot be backed in, because it is not backed out.
Action:
If you are not sure which element actions are backed out, run a CONRPT72 Package
Detail report or view the Element Action Backout panel, accessible from the Backout
Package panel.
PKMR136E
PACKAGE package ID IS INELIGIBLE FOR ELEMENT BACKOUT/BACKIN
Reason:
The package selected for element action backout or backin is not eligible for the action.
Action:
See messages PKMR137I and PKMR138 for more information.
PKMR137I
THERE ARE MULTIPLE ACTIONS PRODUCING THE SAME OUTPUT MEMBER: member
Reason:
The element action you selected for backout is not eligible to be backed out. If multiple
actions within the package produce the same output member, those actions cannot be
backed out.
Action:
None.
PKMR138I
data.set.name(member) IS OUTPUT FOR STMT #nnnnn AND STMT #nnnnn
Reason:
The same member, as indicated, is output by the SCL statements displayed in the
message. This message always occurs with messages PKMR136E and PKMR137I.
Action:
None.
PKMR Messages
PKMR139E
FOR STMT #nnnnn--element name2
Note: Message PKMR139E is preceeded with the following additional messages that
relate directly to it:
C1G0000I SPECIFIED ELEMENT: element-name
C1G0000I DOES NOT MATCH ELEMENT: element-name
Reason:
The element name specified in the element action backout or backin request does not
match the element name for the specified statement number.
Action:
Resubmit the request with the correct element name and statement number.
PKMR140E
STATEMENT #nnnnn NOT FOUND FOR PACKAGE package name
Reason:
The statement number was not found in the package name specified in the backout or
backin request.
Action:
Resubmit the request with the correct statement number and package name.
PKMR141E
STATEMENT #nnnnn DOES NOT HAVE ANY BACKOUT RECORDS
Reason:
The statement number cannot be backed out, because it does not have any backout
records.
Action:
None.
PKMR Messages
PKMR142I
STATEMENT #nnnnn ELEMENT element name
Reason:
This message is issued with message numbers PKMR600I and PKMR700I to indicate the
statement number and element name specified for the Element Action Backout action.
Action:
None.
PKMR143I
THERE ARE MULTIPLE ACTIONS PRODUCING THE SAME OUTPUT FILE:
Reason:
The element action you selected for backout is not eligible to be backed out. If multiple
actions within the package produce the same USS output file, those actions cannot be
backed out. The file and path names will follow this message. Message PKMR144I will
also appear, which identifies the statement numbers.
Action:
None.
PKMR144I
SAME OUTPUT FOR STMT #nnnnn AND STMT #nnnnn
Reason:
This message appears with message PKMR143I and identifies the action statement
numbers.
Action:
None.
PKMR Messages
PKMR145I
STATEMENT #nnnnn
Reason:
See prior log message. This statement identifies the actions statement number. This
statement is usually followed by the element name.
Action:
None.
PKMR200E
PROMOTION PKG ERROR
THE ONLY VALID VALUES FOR PROMOTION PACKAGE ARE: "Y" OR "N"
Reason:
This message indicates that the promotion package field you specified while creating or
modifying the package is invalid. This value must be Y or N.
Action:
Change the value of this field to a value of Y or N.
PKMR208E
THE PACKAGE SELECTED IS NOT AVAILABLE
Reason:
The specified package is not available for the selected action.
Action:
was specified, verify that you are authorized to access the package or that the package
is in the correct status for the requested action. If you did not create the package, the
package must be defined as a sharable package. If the package has one or more
approver groups associated with it, you must be a member of one of the approver
groups.
PKMR Messages
PKMR209E
PACKAGE TYPE ERROR
Reason:
The package type must be specified as either "standard" or "emergency."
Action:
Respecify the package type.
PKMR230E
APPEND SYNTAX ERROR
Reason:
The only valid values for append are: "Y" or "N."
Action:
Enter a correct value for append.
PKMR231E
SHARE SYNTAX ERROR
Reason:
The only valid values for share are: "Y" or "N."
Action:
Enter a correct value for share.
PKMR233E
INPUT PKG ID NOT FOUND
Reason:
The input package ID was not found or is wildcarded.
Action:
Respecify the input package ID.
PKMR Messages
PKMR234E
BACK-OUT SYNTAX ERROR
Reason:
The only valid values for backout are: "Y" or "N."
Action:
Correct the syntax.
PKMR235E
DESCRIPTION OMITTED
Reason:
Description is a required field.
Action:
Enter a description.
PKMR236E
DATE ERROR
Reason:
The window start date is invalid.
Action:
Specify the window start date in DDMMMYY format.
PKMR237E
TIME ERROR
Reason:
The window start time is invalid.
Action:
Specify the window start time in HH:MM format. For example, 14:23.
PKMR Messages
PKMR238E
TE ERROR
Reason:
The window end date is invalid.
Action:
Specify the end date in DDMMMYY format.
PKMR239E
ME ERROR
Reason:
The window end time is invalid.
Action:
Specify the window end time in HH:MM format. For example, 14:23.
PKMR241E
DATE ERROR
Reason:
The window end date is prior to today's date.
Action:
Correct the end date.
PKMR242E
DATE ERROR
Reason:
The window end date is prior to window start date.
Action:
Correct the end date.
PKMR Messages
PKMR244E
INSTALLATION SPECIFICATION DOES NOT ALLOW FOREGROUND EXECUTION OF
PACKAGES
Reason:
A request was submitted to execute this package in foreground, but foreground
processing for packages has not been enabled.
Action:
PKMR246E
WINDOW CANNOT BE CHANGED
Reason:
The Package Execution window can be changed only if it is closed.
Action:
Close the Package Execution window before changing it.
PKMR249E
SYNTAX ERROR
Reason:
The only valid values for this option are: "Y," "W," or "N."
Action:
Correct the syntax.
PKMR280E
DSNAME QUALIFIER CANNOT START WITH A NUMBER
Reason:
Each qualifier in a data set name must begin with an alphabetic or national character.
The "4" in the following data set name is invalid: "PROD.4ABC.LIB".
Action:
Correct the invalid qualifier.
PKMR Messages
PKMR281E
DSNAME contains an invalid character
Reason:
Data set names are built using alphabetic (capitalized), numeric, and national ($, @, #)
characters.
Action:
Correct the invalid character.
PKMR282E
DSN/PATH QUALIFIER LENGTH ERROR DSN 1-8 CHARS, PATH 1-255 CHARS
Reason:
A qualifier with 0 length (two periods in a row or a period as the final character) or
longer than 8 characters for DSN or longer than 255 for Path directory was detected.
Action:
PKMR283E
DSNAME contains an imbedded blank
Reason:
The data set name contains an embedded blank.
Action:
Correct or remove the invalid blank.
PKMR284
DSN/PATH HAS TOO MANY QUALIFIERS DSN 1-22 CHARS, PATH 1-128
Reason:
Too many qualifiers defined for the dataset or pathname. A dataset can have a
maximum of 22 qualifers, a pathname can have a maximum of 128.
Action:
PKMR Messages
PKMR285E
DSN/PATH CONTAINS AN EMBEDDED WILD CARD CHARACTER
Reason:
Wildcards can only appear as the last character of a dataset/path name qualifier or as
the only character making up a qualifier.
Action:
Correct or remove the invalid character.
PKMR287E
A RULE ALREADY EXISTS FOR SPECIFIED HOST DSN OR PATH
Reason:
A mapping rule already exists for the host DSN or path specified.
Action:
Modify the existing rule or create a new rule with a different host DSN or path than
what is specified.
PKMR288E
DESTINATION ALREADY EXISTS
Reason:
A DEFINE DESTINATION is being executed and the Destination already exists.
Action:
Define a new destination or use the one that already exists.
PKMR291E
THE OPTION SELECTED REQUIRES A DATA SET NAME
Reason:
The data set name mapping operation requires a data set name.
Action:
Provide the required data set name.
PKMR Messages
PKMR316C
MAPPED DSN/PATH IS TOO LONG
Reason:
The dataset/path mapping rule which was used to generate a remote dataset/path
name from a certain host dataset/path, resulted in a dataset name greater than 44
character or a path name greater than 768 characters in length.
Action:
Correct the dataset/path name mapping rule.
PKMR320E
INVALID MEMBERS PER CYLINDER. VALID RANGES ARE .01-.99, 1.0-9.9, AND 10-999.
Reason:
The value specified for the approximate number of members that can be contained in
one cylinder of a host staging data set for this mapping rule is invalid. Valid ranges are
stated in the message. Values less than one indicate that a single member requires more
than one cylinder of space. Examples follow:
.01 members per cylinder means that 1 member requires 100 cylinders of space
Action:
Change the value to one which falls in the valid range of values.
PKMR343E
THE PACKAGE FILE CONTAINS NO {DESTINATION | CONNECTION} RECORDS.
Reason:
An attempt was made to ship a package without first setting up a shipment destination.
Action:
Use the "Create/Modify Destination" panel to set up a shipment destination.
PKMR Messages
PKMR348E
PKG window FROM/TO dates and times are the same. PKG can not execute.
Reason:
The user set the Package Execution window to have the same FROM/TO Date and Time.
Action:
Ensure that Package Execution Window is at least one minute.
PKMR400I
BEGINNING ACTION VALIDATION AND SEARCH FOR APPLICABLE APPROVER GROUPS
Reason:
Informational message. This message is issued during cast processing. CA Endevor SCM
is searching for approver groups associated with the inventory areas affected by the
package.
Action:
None.
PKMR401I
ACTION VALIDATION COMPLETED [*WITH/*WITHOUT] ERRORS
Reason:
Informational message. This message indicates whether errors occurred during
validation.
Action:
None.
PKMR402I
number APPROVER GROUP(S) FOUND APPLICABLE FOR PACKAGE
Reason:
Informational message. This message is issued at the completion of the approver group
search during cast processing and indicates how many approver groups are associated
with the package.
Action:
None.
PKMR Messages
PKMR403E
TARGET ON MOVE ACTION DOES NOT EXIST FROM ENV: env-name SYS: sys-name SBS:
subsys-name TYPE: type-name STG: stage-id
Reason:
No target location exists for the environment, system, subsystem, type, and stage
specification in the message.
Action:
Make sure that the from location is specified correctly, and resubmit the Move request.
Otherwise, contact CA Technical Support.
PKMR404E
SRC LOC FOR GEN NOT FND - ELM FOUND AT TGT ENV: env-name STG: stage-id SYS:
sys-name SBS: subsys-name TYPE: type-name
Reason:
CA Endevor SCM did not find the element identified in the message at the location
specified in the message and therefore could not Generate the element.
Action:
Check the element and location specifications, and resubmit the request.
PKMR405E
SOURCE LOCATION ENV: env-name STG: stage-id NOT DEFINED OR UNAVAILABLE
Reason:
The environment and stage named in the message are either not defined or are not
accessible to the user requesting the action.
Action:
Make sure the environment and stage names are specified correctly.
PKMR Messages
PKMR406E
TARGET LOCATION ENV: env-name STG: stage-id NOT DEFINED OR UNAVAILABLE
Reason:
The environment and stage named in the message are either not defined or are not
accessible to the user requesting the action.
Action:
Make sure the environment and stage names are specified correctly.
PKMR407E
STORAGE MANAGEMENT ERROR OCCURRED WHILE PROCESSING APPROVERS FOR
PACKAGE package-id.
Reason:
CA Endevor SCM encountered a storage error when casting a package.
Action:
PKMR408E
CAST ERRORS DETECTED. REVIEW THE CAST REPORT FOR DETAILS
Reason:
Informational message. This message is issued when cast processing detects an error
(usually a reserved element conflict), which causes the cast to terminate.
Action:
None
PKMR Messages
PKMR409I
ELEMENT NOT UNLOCKED DUE TO ACTION FAILURE
Reason:
Informational message. This message is issued during package execution when a CA
Endevor SCM action receives a return code of 12 or higher. The element is left in a
locked state with the expectation that it will re-execute. The element can be unlocked
by resetting or deleting the package.
Action:
None
PKMR410C
ENTERPRISE PACKAGES REQUIRE THE USE OF CA CHANGE MANAGER ENTERPRISE
WORKBENCH (CMEW)
Reason:
A package action using wildcarded package name was attempted on a package that was
included as a component of an Enterprise package. The action can only be performed
through CA CM Enterprise Workbench (CMEW).
Action:
Use CA CM Enterprise Workbench or contact CA Technical Support for more
information.
PKMR410E
ENTERPRISE PACKAGES REQUIRE THE USE OF CA CHANGE MANAGER ENTERPRISE
WORKBENCH (CMEW)
Reason:
A package action was attempted on a package that was included as a component of an
Enterprise package. The action can only be performed through CA Change Manager
Enterprise Workbench (CMEW).
Action:
Use CA CMEW or contact CA Technical Support for more information.
PKMR Messages
PKMR411E
ACTION DENIED - THIS PACKAGE HAS BEEN SCHEDULED BY CA-7 FOR EXECUTION CA-7 job name
Reason:
You are attempting to perform the Execute Package action against a package which is
under the control of CA 7.
Action:
Let CA 7 execute the package when scheduled.
PKMR412I
DYN APPRS CREATED THE DYNAMIC APPROVER GROUP HAS BEEN CREATED
Reason:
The Dynamic Approver Group record has been created.
Action:
None
PKMR413I
DYN APPRS UPDATED THE DYNAMIC APPROVER GROUP HAS BEEN UPDATED
Reason:
The Dynamic Approver Group has been updated with the changes requested by the
user.
Action:
None
PKMR414I
DYN APPRS DELETED THE DYNAMIC APPROVER GROUP HAS BEEN DELETED
Reason:
The user has requested that all approver IDs be removed from the Dynamic Approver
Group. Therefore, the Dynamic Approver Group record has been deleted.
Action:
None
PKMR Messages
PKMR415I
ACTION CANCELLED THE END KEY WAS PRESSED PRIOR TO COMPLETING THE ACTION
Reason:
The user pressed PF3 on the Dynamic Approvers Panel. No requested changes were
applied.
Action:
None
PKMR416I
NO ACTION TAKEN THE DYNAMIC APPROVER GROUP RECORD WAS NOT CREATED OR
UPDATED
Reason:
The user did not update the Dynamic Approver group record. Therefore the record is
unchanged.
Action:
None
PKMR417E
ERROR OCCURRED AN ERROR OCCURRED WHILE PROCESSING THE DYNAMIC
APPROVER GROUP
Reason:
An error occurred while attempting to create, update, or delete the Dynamic Approver
record.
Action:
Contact your administrator. This error may occur if an exit program has cancelled the
Dynamic Approver action, but did not return a message.
PKMR Messages
PKMR418E
UPDATE FAILED THE DYNAMIC APPROVER GROUP CANNOT BE UPDATED IF GROUP IS
APPROVED
Reason:
The dynamic approver group cannot be updated once the group has approved the
package. This is an internal error.
Action:
PKMR419E
UPDATE FAILED THE DYNAMIC APPROVER GROUP CANNOT BE UPDATED IF GROUP IS
DENIED
Reason:
The dynamic approver group cannot be updated once the group has denied the
package. This is an internal error.
Action:
PKMR500I
BEGINNING PACKAGE VERIFICATION FOR PACKAGE package-id
Reason:
Informational message. This message is issued at the beginning of package execution
processing.
Action:
None.
PKMR Messages
PKMR501E
PACKAGE IS NOT IN A STATE THAT IS ELIGIBLE FOR EXECUTION
Reason:
You can only execute packages that are in Approved or Exec-Failed state. The selected
package is not in one these states.
Action:
None.
PKMR502W
PREVIOUS PACKAGE EXECUTION NOT COMPLETE--EXECUTION WILL BE RESTARTED
Reason:
The package being executed failed a prior attempt at execution.
Action:
None.
PKMR503E
PACKAGE CANNOT BE EXECUTED--NOT WITHIN EXECUTION WINDOW:
begin-date-and-time - end-date-and-time
Reason:
The package was submitted for execution outside of its specified execution window.
Action:
Resubmit the package within its execution window. If this is a re-execution of the
package and its window has passed, the execution window may be re-specified, and the
package resubmitted.
PKMR Messages
PKMR504I
PACKAGE BACK-OUT OPTION IS ENABLED
Reason:
Informational message. The executable members associated with the target of the
actions contained in the package will be retained for use during possible backin or
backout processing.
Action:
None.
PKMR505I
PACKAGE VERIFICATION SUCCESSFULLY COMPLETED
Reason:
Informational message. This message is issued at the completion of package verification
processing.
Action:
None.
PKMR506I
BEGINNING VALIDATION OF PACKAGE ACTION(S)
Reason:
Informational message. This message is issued at the beginning of package action
validation processing.
Action:
None.
PKMR507I
VALIDATION OF PACKAGE ACTION(S) COMPLETED [*WITH/*WITHOUT]ERRORS
Reason:
Informational message. This message is issued at the completion of package action
validation processing.
Action:
PKMR Messages
PKMR508W
ACTION ASSOCIATED WITH STMT statement-number PREVIOUSLY FAILED - WILL
ATTEMPT RE-EXECUTION OF THE ACTION
Reason:
This message appears when a package is resubmitted for execution after a prior failure.
Action:
None.
PKMR509E
STMT statement-number ELEMENT NOT FOUND AT
environment/system/subsystem/type/stage-name
Reason:
The element specified in the statement identified in the message was not found at the
specified CA Endevor SCM location.
Action:
Make sure that the element or location (or both) is/are specified correctly.
PKMR510E
STMT statement-number ENV environment NOT FOUND OR YOU ARE NOT
AUTHORIZED FOR ACCESS TO IT
Reason:
Either you are not authorized to access the environment identified in the message, or
the environment could not be found.
Action:
Make sure that the environment is specified correctly or contact CA Technical Support.
PKMR Messages
PKMR511E
STMT statement-number system/subsystem/type/stage-id NOT DEFINED IN
ENVIRONMENT environment
Reason:
The system/subsystem/type/stage ID specified in the statement identified in the
message is not defined to the environment identified in the message.
Action:
Make sure that the system/subsystem/type/stage and the environment are specified
correctly.
PKMR512E
STMT #nnnn ELEMENT VVLL MISMATCH - APPROVED vvll -- CURRENT vvll
Reason:
The current version of the identified element does not match the version of the element
at the time it was cast.
Action:
Reset, recast, and re-approve the package.
PKMR514E
STMT statement-number [DELTA/GENERATE/LASTPROC] TIMESTAMP MISMATCH ELM TIME AT CAST - (date-and-time) - CURRENT MCF TIME (date-and-time)
Reason:
The current time stamp of the identified element does not match the timestamp of the
element at the time it was cast.
Action:
PKMR Messages
PKMR515E
STMT statement-number INTEGRITY ERROR...
Reason:
One or more of the data sets specified in this statement were modified since the
package was cast.
Action:
See subsequent messages for corrective action.
PKMR516E
[DATA SET/member-name] HAS BEEN MODIFIED SINCE THE PACKAGE WAS CAST
Reason:
The data set identified in the message was modified since the package was cast.
Action:
PKMR517E
UNABLE TO RE-EXECUTE SCL STMT statement-number - ELEMENT ASSOC W/ ACTION
HAS BEEN SUPERCEDED BY PKG package-id
Reason:
The element associated with the action in this statement was superseded by the
package identified in this message since the first attempt to execute this package.
Action:
PKMR518E
PACKAGE IN USE package-id - ANOTHER USER IS WORKING WITH THIS PACKAGE.
Reason:
Another user is working with the package identified in the message.
Action:
Retry access to the package later.
PKMR Messages
PKMR519I
SKIPPING ACTION ASSOCIATED WITH STMT statement-number - PREVIOUS
EXECUTION SUCCESSFUL
Reason:
This statement executed successfully during a prior attempt to execute this package.
Action:
None.
PKMR520E
ACTION ASSOC W/STMT statement-number EXPECTED COPYBACK FROM STG
source-stage-name - ELEMENT ALREADY EXISTS AT STG target-stage-name
Reason:
The action specified in the statement identified in the message included the copyback
option; however the element already exists at the target stage.
Action:
Resubmit the action without the copyback specification.
PKMR521E
UNABLE TO RESTART PACKAGE EXECUTION - PACKAGE IS CURRENTLY IN A BACKED
OUT STATE
Reason:
The package was backed out after a prior attempt at execution, and has not been
backed-in.
Action:
Back in the package and re-execute.
PKMR Messages
PKMR522E
UNABLE TO RE-EXECUTE SCL STMT statement-number - ELEMENT ASSOC W/ ACTION
HAS BEEN MODIFIED BY A NON-PACKAGE ACTION
Reason:
The element specified in this statement has been modified outside of CA Endevor SCM
since the package was cast.
Action:
PKMR523E
ERROR IN $IMR PROCESSING - CONTACT ENDEVOR TECHNICAL SUPPORT
Reason:
CA Endevor SCM was checking for the existence of an element at a target location of a
package action, but could not complete the check.
Action:
PKMR524E
STMT statement-number LAST PROCESSOR EXECUTION FAILED FOR THIS ELM AT
env-name/sys-name/subsystem-name/type-name/stage-name
Reason:
CA Endevor SCM could not execute the current action against the element because the
most recent processor executed against the element failed.
Action:
Correct the failed processor condition, and resubmit the current action.
PKMR Messages
PKMR525E
LAST ACTION FOR THIS ELEMENT WAS ON date AT time BY user-id.
Reason:
This message is issued along with message PKMR522E, and identifies the user ID
associated with the last change to the element referenced in message PKMR522E.
Action:
If necessary, contact the user who made the change.
PKMR526I
STATEMENT # scl sequence-number SIGNOUT CONFLICT.
Reason:
Informational message generated by the package inspect action. This message is
preceded by a signout warning, caution, or error message. The SCL sequence number
refers to an SCL statement listed earlier in the report.
Action:
None.
PKMR527I
STATEMENT # scl sequence-number SYNCHRONIZATION CHECK FAILED.
Reason:
Informational message generated by the package inspect action. This message is
preceded by a synchronization warning, caution, or error message. The SCL sequence
number refers to an SCL statement listed earlier in the report.
Action:
None.
PKMR Messages
PKMR528E
PACKAGE CANNOT BE EXECUTED, CURRENT USER IS NOT A VALID APPROVER FOR THIS
PACKAGE
Reason:
A package requiring approval can only be executed by one of the valid approvers.
Action:
Inform one of the approvers to execute the package.
PKMR529I
STATEMENT statement-number JUMP CHECK FAILED
Reason:
Informational message. The JUMP option specified on the MOVE action failed.
Action:
Review the other related messages in the error log to find out the cause.
PKMR530S
STMT statement-number ELEMENT FOUND AT inventory-location HAS CHANGED SINCE
PKG STARTED
Reason:
The element specified in this SCL statement was modified since the package began to
execute.
Action:
Determine why the element was modified, and re-execute the package.
PKMR531E
STMT #NNN - SPECIFIED VVLL DOES NOT EXIST
Reason:
The VVLL clause was specified in the action, but the VVLL do not correspond to the VVLL
found in the MCF.
Action:
Remove the VVLL clause or change the values to match the MCF values.
PKMR Messages
PKMR532I
STATEMENT #statement-number CCID/COMMENTS CHECK FAILED
Reason:
Based on the system definitions, CCID/COMMENTS are required but are not specified.
Action:
Add the CCID/COMMENTS to this action.
PKMR533I
CASTING NEXT VERSION OF THIS PROMOTION PACKAGE
Reason:
This message appears at the end of the execution log to indicate that the cast of the
new version of the promotion package is being performed.
Action:
No action required.
PKMR534E
STMT #nn THE VALIDATION OF THE <<WHERE>> CLAUSE FAILED.
Reason:
The validation of the WHERE clause of SCL statement #nn failed.
Action:
Investigate whether a WHERE clause is required for this package action. Remove or
modify the WHERE clause.
PKMR600I
BEGINNING VERIFICATION FOR [BACKOUT/BACKIN] OF PACKAGE package-id
Reason:
Informational message. Verification has begun for backout or backin of the package
Action:
None.
PKMR Messages
PKMR601E
PKG STATUS (status) INCOMPATIBLE WITH [BACKOUT/BACKIN] REQUEST - STATUS
MUST BE EXECUTED OR IN-EXECUTION
Reason:
Package status must be EXECUTED or IN-EXECUTION to perform the backout/backin
request.
Action:
None.
PKMR602E
PACKAGE BACK-OUT HAS ALREADY BEEN SUCCESSFULLY PERFORMED
Reason:
A request was made to back out this package, however the package has already been
backed out.
Action:
None.
PKMR603E
PACKAGE [BACKOUT/BACKIN] IMPOSSIBLE - NO BACK-OUT INFORMATION EXISTS FOR
PACKAGE package-id
Reason:
A request has been issued to backout/backin the package identified in the message, but
no backout information exists for this package.
Action:
None.
PKMR Messages
PKMR604E
PACKAGE [BACKOUT/BACKIN] IMPOSSIBLE - NO BACK-OUT OPTION SPECIFIED DURING
PACKAGE package-id EXECUTION
Reason:
A request has been issued to backout/backin the package identified in the message, but
backout/backin was not enabled for this package when it was executed.
Action:
None.
PKMR605E
PACKAGE [BACKOUT/BACKIN] IMPOSSIBLE - NO ELEMENT/MEMBER IDENTIFICATION
RECORDS EXIST
Reason:
Internal error.
Action:
PKMR606E
UNABLE TO PERFORM PACKAGE [BACKOUT/BACKIN], PACKAGE SUPERSEDED BY THE
FOLLOWING PACKAGES:
Reason:
The packages identified in the message have superseded the package for which a
backin/backout was requested.
Action:
Backout/backin the packages identified in the message, in the order they occur in the
message, before re-attempting backout/backin of this package.
PKMR Messages
PKMR607E
UNABLE TO PERFORM PACKAGE BACKIN, THIS PACKAGE SUPERSEDES PACKAGE
package-name, WHICH IS STILL BACKED OUT
Reason:
The packages identified in the message have superseded the package for which a
backin/backout has been requested.
Action:
Backin the package identified in the message before re-attempting to backin this
package.
PKMR608E
UNABLE TO PERFORM PACKAGE (BACKOUT/BACKIN),
environment/system/subsystem/type/stage, ELEMENT NOT FOUND
Reason:
A request has been made to backin/backout a package, but the location specified in the
package cannot be found. The element name follows this message.
Action:
None.
PKMR609E
UNABLE TO PERFORM [BACKOUT/BACKIN], BACK-OUT MEMBER
dsname(member-name) NOT FOUND
Reason:
A request was made to backout a package, but the backout member in the target data
set could not be found.
Action:
This package cannot be backed out, but should be committed or reset to clear the
backout information.
PKMR Messages
PKMR610I
dsname(member-name) WILL BE RECOVERED AS OF PACKAGE package-id
Reason:
Informational message. This message is issued as a result of a package backout request.
The message identifies the package ID associated with the member that will be
recovered.
Action:
None.
PKMR611I
dsname(member-name) WILL BE LOGICALLY DELETED
Reason:
Informational message. This message is issued as a result of a backout request. The
member identified in the message was created when the package was executed, thus
the backout of the package will result in this member being deleted.
Action:
None.
PKMR612E
UNABLE TO PERFORM [BACKOUT/BACKIN] - SUPERSEDING PKG package-id HAS
INCORRECT STATUS package-status
Reason:
A request has been issued to backout/backin a package. To do this, any superseding
packages must first be backed out/backed in. To be backed out/backed in, a package
must have a status of EXECUTED or IN-EXECUTION. The superseding package identified
in this message is not in one of these states, and therefore cannot be backed
out/backed in.
Action:
None.
PKMR Messages
PKMR613I
PKG: package-id STATUS: status EXECUTION DATE: date-time execution status
Reason:
Informational message. This message is issued when a backout/backin request was
issued for a superseded package and indicates the status and most recent execution
date for the superseding packages.
Action:
None.
PKMR614E
UNABLE TO PERFORM PACKAGE [BACKOUT/BACKIN], THE FOLLOWING SUPERCEDING
PACKAGE NO LONGER EXISTS: package-id
Reason:
A request was issued to back out a package. Before this package can be backed out, any
superseding packages must be backed out first. The package identified in the message is
a superseding package, but it does not exist.
Action:
None.
PKMR615E
'UNABLE TO BACK-IN PACKAGE PACKAGE IS NOT BACKED_OUT
Reason:
A request was submitted to back-in this package, but the package is not backed out.
Action:
None.
PKMR Messages
PKMR616E
CANNOT (BACKOUT/BACKIN) PKG package-id,
environment/system/subsystem/type/stage, ELEMENT WAS MODIFIED
Reason:
The package identified in the message could not be backed in/backed out because the
element was modified by an action performed outside of package processing. The
element name follows this message.
Action:
None.
PKMR617I
PREVIOUS PACKAGE backin/backout NOT COMPLETE - backin/backout WILL BE
RESTARTED
Reason:
A previous backin/backout was not completed. The backin/backout will be restarted.
Action:
None.
PKMR618I
dataset(member) (BACKIN/BACKOUT) WILL BE SKIPPED PREVIOUS
(BACKIN/BACKOUT) WAS SUCCESSFUL
Reason:
The indicated backin/backout will be skipped because the previous backin/backout was
successful.
Action:
None.
PKMR Messages
PKMR619I
(BACKIN/BACKOUT) WILL BE SKIPPED PREVIOUS (BACKIN/BACKOUT) WAS
SUCCESSFUL
Reason:
The indicated backin/backout will be skipped because the previous backin/backout was
successful. The path and file name preceeds this message.
Action:
None.
PKMR620E
NON-ZERO RETURN CODE RETURN FROM CA-7 UTILITY PROGRAM (CAL2X2WP) RC=
return-code REASON CODE= reason-code
Reason:
This job is under the control of CA 7. CA 7 returned an error condition to CA Endevor
SCM.
Action:
Review the CA 7 message using the appropriate CA 7 manual for additional error
information.
PKMR621E
NO DATA RECEIVED FROM CA-7 AFTER CALL TO CA-7 UTILITY (CAL2X2WP)
Reason:
This job is under the control of CA 7. CA Endevor SCM called CA 7 to schedule the job,
but CA 7 did not respond to the request.
Action:
PKMR Messages
PKMR622I
PACKAGE SCHEDULED FOR EXECUTION BY CA-7 - BEGINNING CA-7 JOB SUBMISSION
CONFIRMATION
Reason:
Informational message. This message is issued at the time, the package is scheduled by
CA 7.
Action:
None.
PKMR623I
JOB SUBMISSION BY CA-7 HAS BEEN VERIFIED
Reason:
Informational message. This message is issued at the time, the package is accepted by
CA 7.
Action:
None.
PKMR624E
VERIF. FAILED DUE TO JOBNAME MISMATCH - SCHEDULED JOB job-name - THIS JOB
job-name
Reason:
The job name associated with the package on the CA Endevor SCM side is different than
the job name associated with this package on the CA 7 side.
Action:
PKMR625E
VERIF. FAILED - CA-7 DOES NOT REFLECT THAT THE SCHEDULED JOB IS EXECUTING
Reason:
CA Endevor SCM considers the job scheduled, but CA 7 is not aware of this job.
Action:
PKMR Messages
PKMR626E
VERIF. FAILED - CA-7 QUERY PRODUCED UNEXPECTED RESULTS - CA-7 (CAL2X2WP)
MESSAGES FOLLOW:
Reason:
CA Endevor SCM attempted to verify the job, but CA 7 returned unexpected results.
Action:
PKMR627I
text
Reason:
This message contains the text returned by the CA 7 query function.
Action:
None.
PKMR628I
CA-7 JOB SUBMISSION VERIFICATION SUCCESSFULLY COMPLETED
Reason:
This message indicates that CA Endevor SCM successfully verified that the job
submission was completed.
Action:
None.
PKMR629E
UNABLE TO PERFORM (BACKIN/BACKOUT), BACK-OUT FILE NOT FOUND.
Reason:
A request was made to backout a package, but the backout file in the target pathname
could not be found. The file and pathname are identified before this message.
Action:
This package cannot be backout out, but should be committed or reset to clear the
backout information..
PKMR Messages
PKMR630I
WILL BE RECOVERED AS OF PACKAGE package-id
Reason:
The message identifies the package ID associated with the USS file that will be
recovered. The path and file name precedes this message.
Action:
None.
PKMR631I
WILL BE LOGICALLY DELETED
Reason:
The USS file identified just prior to this message, was created when the package was
executed, thus the backout of the package will result in this file being deleted.
Action:
None.
PKMR632C
PACKAGE WAS PREVIOUSLY SHIPPED TO THE FOLLOWING DESTINATION(S) PRIOR TO
[BACK-OUT| BACK-IN]
PKMR633C
destination-name date time
Reason:
This package was shipped before the backout or backin function was executed. Multiple
PKMR633C messages can appear, because one message is shown for each date and time
the package was shipped to each destination.
Action:
You may need to reship the package now that the backout function has changed the
package outputs.
PKMR Messages
PKMR632W
PACKAGE WAS PREVIOUSLY SHIPPED TO THE FOLLOWING DESTINATION(S) PRIOR TO
[BACK-OUT| BACK-IN]
PKMR633W
destination-name date time
Reason:
This package was shipped before the backout or backin function was executed. Multiple
PKMR633W messages can appear, because one message is shown for each date and
time the package was shipped to each destination.
Action:
The package may need to the re-shipped.
PKMR690I
PACKAGE [BACK-IN|BACK-OUT] VERIFICATION COMPLETED [*WITH/*WITHOUT]
ERRORS
Reason:
Informational message. This message is issued at the completion of package backin or
backout verification.
Action:
None.
PKMR700I
BEGINNING [BACKOUT/BACKIN] OF PACKAGE package-id
Reason:
Informational message. This message is issued at the beginning of backout/backin
processing for the package identified in the message.
Action:
None.
PKMR Messages
PKMR710I
dsname(member-name) HAS BEEN RECOVERED AS OF PACKAGE package-id
Reason:Informational message. This message is issued as a result of a package backout request.
The message identifies the package ID associated with the member that has been
recovered.
Action:
None.
PKMR711I
dsname(member-name) HAS BEEN LOGICALLY DELETED
Reason:
The member, created when the package was executed, has been logically deleted. It can
be recovered through the package backin process.
Action:
None.
PKMR712I
HAS BEEN RECOVERED AS OF PACKAGE package-id
Reason:
The message identifies the package ID associated with the file that has been recovered.
The USS file name is identified just prior to the merssage.
Action:
None.
PKMR Messages
PKMR713I
HAS BEEN LOGICALLY DELETED
Reason:
The USS file identified just prior to this message, was created when the package was
executed, so this message indicates that this file has been logically deleted. It can be
recovered through the package backin process.
Action:
None.
PKMR790I
PACKAGE [BACKOUT/BACKIN] COMPLETED [*WITH/*WITHOUT] ERRORS
Reason:
Informational message. Backout/backin processing has been completed for the package
Action:
See any associated error messages for corrective action.
PKMR791I
COMPONENT VALIDATION STARTED
Reason:
Informational message. CA Endevor SCM has started component validation.
Action:
None.
PKMR792I
PACKAGE DOES NOT CONTAIN SCL STMTS WHICH REQUIRE COMPONENT VALIDATION
Reason:
Informational message. You have requested component validation, but the package
does not contain the SCL statement requiring this validation.
Action:
None.
PKMR Messages
PKMR793E
COMPONENT VALIDATION STOPPED, INTERNAL ERROR IN
BC1PPKVC/subroutine-name
Reason:
Internal error.
Action:
PKMR794E
COMPONENT VALIDATION BYPASSED - ELEMENT MASTER RECORD NOT FOUND
Reason:
CA Endevor SCM has bypassed the component validation step because it did not find the
master record for the element.
Action:
PKMR795E
COMPONENT VALIDATION BYPASSED - TYPE MASTER RECORD NOT FOUND
Reason:
This message indicates that the component validate was requested. A master record
does not exist for this element.
Action:
Determine if the element name and location are correct.
PKMR796E
INPUT COMPONENT MASTER RECORD NOT FOUND
Reason:
This message indicates that the component validate was requested. A master record
does not exist for this element.
Action:
Review the other component-related messages to determine the cause of this problem.
PKMR Messages
PKMR797E
INPUT COMPONENT WITHIN ELEMENT IS NOT CURRENT
Reason:
An old version of this component is included in the component list for this element.
Action:
Generate this element to pick up the latest components.
PKMR798E
COMMENTED SCL MOVE ACTIONS ADDED TO PACKAGE
Reason:
During the component validate process, it was determined that a parent element was
being moved in a package, but one or more of its components were being left behind.
CA Endevor SCM generates commented out SCL MOVE actions for each of the
components.
Action:
Edit the commented package SCL and recast the package.
PKMR798W
COMMENTED SCL MOVE ACTIONS ADDED TO PACKAGE
Reason:
CA Endevor SCM has appended commented Move SCL statements to the package for
input components that were not included in the original package SCL.
Action:
Edit the commented package SCL and recast the package.
PKMR Messages
PKMR799I
COMPONENT VALIDATION COMPLETED: HIGHEST RC= return code
Reason:
Informational message. CA Endevor SCM has completed component validation as
indicated in the message.
Action:
To determine the cause of package component validation errors or warnings, display the
Package Cast Report, which contains these error/warning messages.
PKMR800I
PACKAGE CONTAINS COMPONENT(S) FROM EXTERNAL ENVIRONMENT(S) WHICH
COULD NOT BE VALIDATED
Reason:
Informational message. Some of the components in the package exist in external
environments and therefore cannot be validated.
Action:
None.
PKMR801I
OF ENV:env-name SYS:syst-name SUBSYS:subsys-name TYPE:type-name STG:stage-id
Reason:
Informational message. The message contains the inventory location of the current
element.
Action:
None.
PKMR Messages
PKMR802I
FP ENV:env-name SYS:sys-name SUBSYS:subsys-name TYPE:type-name STG:stage-id
Reason:
Informational message. The message contains the FP information associated with this
input component.
Action:
None.
PKMR803I
ENV:env-name SYSTEM:sys-name SUBSYSTEM:subsys-name TYPE:type-name
STAGE:stage-id
Reason:
Informational message. The message contains the inventory location of the current
element.
Action:
None.
PKMR805I
FP DATE/TIME IN COMPONENT LIST : ddmmmyy mm:ss
Reason:
Informational message. This message indicates the footprint date and time
(yymmmdd,hh:mm).
Action:
None.
PKMR806I
LOCATED AT ENVIRONMENT : env-name STAGE: stage-id
Reason:
This message indicates the inventory location where the used component currently
resides.
Action:
None.
PKMR Messages
PKMR807I
GENERATE PROCESSOR DATE/TIME : ddmmmyy mm:ss
Reason:
Informational message. This message indicates the generate date and time.
Action:
None.
PKMR808I
LAST PROCESSOR DATE/TIME : ddmmmyy mm:ss
Reason:
Informational message. This message indicates the move date and time.
Action:
None.
PKMR809I
CURRENT SOURCE DATE/TIME : ddmmmyy mm:ss
Reason:
Informational message. This message indicates the last change date and time.
Action:
None.
PKMR810I
CHANGED VERSION FOUND IN ENV: environment SYS: system SUBSYS: subsystem STG:
stage-id
Reason:
Informational message. This message contains the inventory location of the "newer"
copy of the component that was found on the map.
Action:
None.
PKMR Messages
PKMR900E
TRUNCATION OCCURRED WHILE MOVING RECORD TYPE type TO BUFFER - CONTACT
ENDEVOR TECHNICAL SUPPORT
Reason:
Internal error.
Action:
PKMR901E
INVALID PARAMETER LIST RECEIVED - CONTACT ENDEVOR TECHNICAL SUPPORT
Reason:
Internal error.
Action:
PKMR902E
IO ERROR message textsave
Reason:
Internal error. The message text describes the kind of I/O error that occurred.
Action:
RDLT Messages
RDLT Messages
RDLT messages are generated by the CA Endevor SCM BC1PRDLT utility, used to remove
expired element and component deltas for age managed deltas. The following list of
RDLT messages includes possible causes and corrective actions to take in error
situations.
RDLT001E
C1BMINIT FAILURE. CONTACT TECHNICAL SUPPORT.
Reason:
Internal error occurred in C1BMINIT.
Action:
RDLT002E
Processing Terminated.
Reason:
Error occurred which caused the Utility to terminate.
Action:
A previous message should accompany this one. Refer to that message.
RDLT003E
BAD PARAMETER ON THE EXEC STATEMENT, ONLY PARAMETER EXAMINE IS ALLOWED
Reason:
Invalid text found in the PARM= field on the JCL EXEC statement.
Action:
Specify the EXAMINE parameter on the EXEC card or leave the parameter value blank,
and then resubmit the job.
RDLT Messages
RDLT004E
$IMR ENVIRONMENT REQUEST FAILED. $IMR ERROR MESSAGE FOLLLOWS
Reason:
Refer to the following $IMR message.
Action:
If problem cannot be resolved, contact your administrator.
RDLT005C
PROCESSING TERMINATED, NO ENVIRONMENTS FOUND
Reason:
No environments were found in your C1DEFLTS table.
Action:
Check that you are running with the correct table.
RDLT006E
error-code ERROR ACQUIRING STORAGE
Reason:
Problem occurred while acquiring storage during program initialization.
Action:
RDLT007E
$IMR SYSTEM REQUEST FAILED. $IMR ERROR MESSAGE FOLLLOWS
Reason:
Action:
RDLT Messages
RDLT008E
Reason:
Problem occurred while acquiring storage for an internal table.
Action:
RDLT009E
$IMR ELEMENT REQUEST FAILED. $IMR ERROR MESSAGE FOLLLOWS
Reason:
Action:
RDLT010E
Reason:
Problem occurred while acquiring storage during element processing.
Action:
RDLT011E
BEGINNING SYSTEM ROUTE WITHIN ENV env-name NOT FOUND FOR ENV env-name
SYS sys-name
Reason:
The system mapping route changed during the execution of this utility.
Action:
Check with your administrator, and then re-run the job.
RDLT Messages
RDLT012E
ENQUEUE FAILED ON MCF ELEMENT ele-name
Reason:
Enqueue lock failed on element. Processing continues with next element.
Action:
See accompanying error message.
RDLT013E
$IMR ELEMENT QUERY REQUEST FAILED. $IMR ERROR MESSAGE FOLLLOWS
Reason:
Action:
RDLT200I
ROUTE STARTING ENVIRONMENT: environment name
Reason:
Informational. This message identifies the starting environment location where the
Aged Deltas Utility will start looking for qualifying elements. All elements existing only at
the end of this route will be candidates for removals of aged delta levels.
Action:
None.
RDLT100I
AT LOCATION ENV env-name SID stage-id SYS sytem-name SBS subsys-name TYPE
type-name
Reason:
Information. Inventory location where element was found.
Action:
None.
RDLT Messages
RDLT101I
TOTAL END OF ROUTE AGED DELTA ELEMENTS IN ROUTE: nnnnnnnn
Reason:
Information. Total number of qualifying elements with aged delta levels found for a
given route.
Action:
None.
RDLT102I
TOTAL END OF ROUTE AGED DELTA COMPONENTS IN ROUTE: nnnnnnnn
Reason:
Information. Total number of qualifying element components with aged delta levels
found for a given route.
Action:
None.
RDLT103I
TOTAL AGED DELTA ELEMENTS FOUND/MODIFIED: nnnnnnnn
Reason:
Informational. If running in EXAMINE mode, this count represents the total number of
qualifying elements found with aged delta levels. If running in EXECUTE mode, this
count represents the total number of qualifying elements where aged delta levels were
removed from the delta file and applied to the base element.
Action:
None.
SCHK Messages
RDLT104I
TOTAL AGED DELTA COMPONENTS FOUND/MODIFIED: nnnnnnnn
Reason:
Informational. If running in EXAMINE mode, this count represents the total number of
qualifying element components found with aged delta levels. If running in EXECUTE
mode, this count represents the total number of qualifying element components where
aged delta levels were removed from the delta file and applied to the base element
component.
Action:
None.
SCHK Messages
When a source sync check is performed, the following error messages may be written to
the action log.
SCHK100E
UNSUPPORTED CALL FUNCTION = func-number
Reason:
Internal error.
Action:
SCHK101E
CATALOG SEGMENT DOES NOT EXIST FOR ELEMENT TYPE AT LOCATION
env-name/stg-id/sys-name/sbs-name
Reason:
CA Endevor SCM's MCF and Catalog data sets are not synchronized.
Action:
SCHK Messages
SCHK102E
INTERNAL $IMR ERROR - REFER TO NEXT MESSAGE
Reason:
Internal error occurred.
Action:
Refer to the corrective action for the error message following this message.
SCHK103E
INVALID ENVIRONMENT env-name
Reason:
Internal error.
Action:
SCHK104E
error ERROR ACQUIRING INITIAL PAGE STORAGE
Reason:
CA Endevor SCM encountered the named error while attempting to acquire initial
storage.
Action:
Increase the job's region size. If the problem still occurs, contact CA Endevor SCM
technical support.
SCHK105C
SOURCE SYNCHRONIZATION VALIDATION FAILED BECAUSE OF THE PREVIOUS ERROR
Reason:
CA Endevor SCM encountered a serious error during sync check processing
Action:
SCHK Messages
SCHK106E
error ERROR ACQUIRING STORAGE WHILE BUILDING AN ENV CHAIN
Reason:
The named amount of storage was not available.
Action:
Increase the job's region size. If problem still occurs, contact CA Endevor SCM technical
support.
SCHK108E
TYPE typ-name HAS NO CATALOG SEGMENT
Reason:
The element name appears before this message. CA Endevor SCM 's MCF and Catalog
data sets may not be synchronized.
Action:
SCHK109E
error ERROR ACQUIRING STORAGE WHILE BUILDING A SEGMENT CHAIN
Reason:
Action:
support.
SCHK Messages
SCHK112I
TYPE name SOURCE CHANGE LEVEL IS OUT-OF-SYNC AT LOCATION
Reason:
The element name appears before this message. The element type identified at the
location in this message is now out-of-sync. An email was sent to the owner of the
element.
Action:
The owner of the element needs to examine the changes made up the map and take
corrective action. Usually, the owner incorporates the changes found further up the
map. The email identifies the element location that caused the problem.
SCHK112W
Reason:
location in this message is now out-of-sync. An e-mail was sent to the owner of the
element.
Action:
map. The e-mail identifies the element location that caused the problem.
SCHK112C
Reason:
location in this message is now out-of-sync. An email was sent to the owner of the
element.
Action:
map. The email identifies the element location that caused the problem.
SHP Messages
SCHK113E
ERROR ACQUIRING STORAGE FOR THE SYNC CHECK CONTROL BLOCK
Reason:
The allocated memory is insufficient
Action:
support.
Source Sync Check Return and Reason Codes

The following return and reason codes result from source sync checks.
return code = 0, reason code = 0
The source sync check completed, but found no lower instances of the element.
return code = 0, reason code = 4
The source sync check completed and found lower instances of the element.
return code 12 or higher
The source sync check encountered a serious error.
SHP Messages
The SHP messages result from API Package Ship processing. The following list of CA
Endevor SCM SHP messages includes possible causes and corrective actions to take in
error situations.
SHP0001S
UNABLE TO ALLOCATE THE TEMPORARY JCL FILE
Reason:
CA Endevor SCM is unable to allocate a temporary JCL file required to build the JCL to
execute the PROC statement.
Action:
View the job log for additional clues.
SHP Messages
SHP0002E
UNABLE TO READ THE APIHJC JOBCARD FILE
Reason:
CA Endevor SCM is unable to read the skeleton host jobcard.
Action:
Verify that the APIHJC DD statement points to the jobcard file and that this sequential
file exists.
SHP0003E
ERROR DETECTED WRITING TO THE TEMPORARY JCL FILE
Reason:
CA Endevor SCM is unable to write to the temporary JCL file it is building containing the
JOBCARD, EXEC PROC statement and SCL statement.
Action:
SHP0004E
UNSUPPORTED SCL STATEMENT
Reason:
A keyword was found at the beginning of a statement that is not the keyword SHIP, EOF,
EOJ, or a comment.
Action:
Correct the SCL statement.
SHP0005E
SHIP STATEMENT NOT FOUND
Reason:
CA Endevor SCM parsed the SCL statements and did not locate the SHIP statement.
Action:
Ensure that the SHIP statement is included in the SCL.
SHP Messages
SHP0006E
UNABLE TO LOCATE THE "TO" KEYWORD IN THE SHIP STATEMENT
Reason:
CA Endevor SCM is unable to locate the TO keyword on the SHIP statement.
Action:
Ensure that the TO keyword is included in the SHIP statement.
SHP0007E
UNABLE TO LOCATE THE "DESTINATION" KEYWORD ON THE SHIP STATEMENT
Reason:
CA Endevor SCM is unable to locate the DESTINATION keyword on the SHIP statement
following the TO keyword.
Action:
Ensure that the DESTINATION keyword is included in the SHIP statement after the TO
keyword.
SHP0008E
UNABLE TO LOCATE THE DESTINATION ID VALUE ON THE SHIP STATEMENT
Reason:
CA Endevor SCM is unable to locate the destination ID on the SHIP statement following
the destination keyword.
Action:
Ensure that the destination ID is included in the SHIP statement following the
destination keyword.
SHP Messages
SHP0009E
THE @20CY VALUE MUST BE S-BDT1, B-BDT2, M-CONN, L-LOCL, F-NVFT OR X-XCOM.
@1CY IS INVLD
Reason:
The six transmission methods supported by the API ship facility are S (BDT1), B (BDT2),
M (CONN), L (LOCL), F (NVFT) and X (XCOM). The transmission method is determined by
the destination ID specified on the SHIP statement.
Action:
Ensure that a valid transmission method is associated with the specified destination ID.
SHP0010E
ONLY 1 SHIP STATEMENT IS ALLOWED PER REQUEST. MULTIPLE SHIP STATEMENTS
WERE DETECTED
Reason:
More than one SHIP statements were found within the SCL. Only one SHIP statement is
allowed per request.
Action:
Ensure that the SCL statement includes only one SHIP statement.
SHIP011E
UNABLE TO OBTAIN AND CONVERT THE CURRENT DATE AND TIME
Reason:
The current date and time are obtained from the operating system and converted into a
display format. This is an internal error.
Action:
SMGR Messages
SMGR Messages
SMGR messages are generated by source management functions. The following list of
CA Endevor SCM SMGR messages includes possible causes and corrective actions to take
in error situations.
SMGR001E
UNSUPPORTED CALL FUNCTION = function name
Reason:
Internal error.
Action:
SMGR002S
INTERNAL LOGIC ERROR
Reason:
Internal error.
Action:
SMGR003E
OLD LEVEL LINE COUNT PLUS INSERTS MINUS DELETES DO NOT ADD UP TO THE NEW
LEVEL COUNT
Reason:
Internal error.
Action:
SMGR Messages
SMGR004E
MAXIMUM OF 99,999 LINES/RECORDS EXCEEDED
Reason:
You have tried to add an element with more than 99,999 lines. This exceeds the limit for
CA Endevor SCM.
Action:
Break up the element, and resubmit the add request with elements having less than
99,999 lines.
SMGR005E
ERROR READING DELTA MEMBER - DATA RECORD LENGTH EXCEEDS MAXIMUM
LENGTH ALLOWED FOR TYPE - type name
Reason:
Internal error.
Action:
SMGR006E
ERROR READING DELTA MEMBER - EXPECTED DELTA CONTROL RECORD - record name
Reason:
Internal error.
Action:
SMGR007E
ERROR READING DELTA MEMBER - PREMATURE END OF FILE - file name
Reason:
A premature end-of-file was encountered while reading the delta member. The
symbolic literal indicates the type of error.
Action:
SMGR Messages
SMGR008E
EXTERNAL DATA SET EMPTY, ADD/UPDATE TERMINATED
Reason:
The data set that you specified in the add/update request does not contain any
members.
Action:
Make sure that you have specified the external data set correctly, and resubmit the
request.
SMGR009E
error code LOGIC ERROR DETECTED WHILE CREATING DELTA
Reason:
CA Endevor SCM encountered the named logic error when attempting to build a delta.
Action:
SMGR010E
MAXIMUM OF 65,535 INSERTS OR DELETES EXCEEDED
Reason:
CA Endevor SCM supports a maximum of 65,535 inserts or deletes for any given change
level of a component list. This limit has been exceeded.
Action:
Make the desired changes in groups that will result in fewer than the named number of
inserts or deletes to the component list.
SMGR011S
Reason:
Internal error.
Action:
SMGR Messages
SMGR012E
error name ERROR ACQUIRING REQUIRED STORAGE (amount) DURING REBUILD
Reason:
Action:
Increase region size and re-execute the request.
SMGR013E
error name ERROR ACQUIRING INITIAL STORAGE
Reason:
CA Endevor SCM encountered the named error while attempting to acquire initial
storage.
Action:
SMGR014E
ERROR OPENING [DELTA|BASE] FILE - ddname/data set name(member name)
Reason:
Internal error.
Action:
SMGR015E
DELTA MEMBER NOT FOUND
Reason:
CA Endevor SCM did not find the delta member named in the message.
Action:
component option to delete the component list base and delta, and regenerate the
SMGR Messages
SMGR016E
ELEMENT BASE/DELTA LIBRARIES CAN NOT BE THE SAME
Reason:
The data set associated with the base and delta libraries are the same.
Action:
Correct the base and delta data set names using the type definition panel.
SMGR020E
EXPECTED DELTA CONTROL RECORD NOT FOUND
Reason:
CA Endevor SCM did not find the expected control information in the named delta
member.
Action:
SMGR021E
INCORRECT FIRST RECORD IN DELTA FILE
Reason:
Element delta does not contain a CA Endevor SCM control record.
Action:
SMGR Messages
SMGR022E
DELTA [BASE/LAST] VERSION INCORRECT
Reason:
The element delta contains an unrecognizable record.
Action:
SMGR023E
UNRECOGNIZED DELTA RECORD
Reason:
CA Endevor SCM did not recognize the named delta member.
Action:
SMGR024E
EXPECTING DELTA VVLL vvll, FOUND vvll
Reason:
The element delta contains version and level delta identifiers that are out of sequence.
Action:
SMGR Messages
SMGR025E
DELTA INSERT COUNT NOT NUMERIC
Reason:
The insert count in the named member is not numeric.
Action:
SMGR026E
DELTA INSERT COUNT / FILE INSERT COUNT MISMATCH
Reason:
The insert count in the delta control record does not match the number of inserts in the
named member.
Action:
SMGR027E
DELTA DELETE COUNT NOT NUMERIC
Reason:
The delete count in the named member is not numeric.
Action:
SMGR Messages
SMGR028E
DELTA DELETE COUNT / FILE DELETE COUNT MISMATCH
Reason:
The delete count in the delta control record does not match the number of deletes in
the named member.
Action:
SMGR029E
DELTA INSERT LINE NUMBER NOT NUMERIC
Reason:
CA Endevor SCM has found a non-numeric insert line number in the named delta
member.
Action:
SMGR030E
DELTA DELETE FROM LINE NUMBER NOT NUMERIC
Reason:
CA Endevor SCM has found a non-numeric delete from line number in the named delta
member.
Action:
SMGR Messages
SMGR031E
DELTA DELETE TO LINE NUMBER NOT NUMERIC
Reason:
CA Endevor SCM has found a non-numeric delete to line number in the named delta
member.
Action:
prior unload tape or archive file. If the error is associated with the component list, use
the DELETE action with only component option to delete the component list base and
delta, and regenerate the element to recreate the component list.
SMGR032E
INTERNAL LOGIC ERROR - DELETING FROM DELTA FILE
Reason:
Internal error.
Action:
SMGR033E
INTERNAL LOGIC ERROR - DELTA FILE POSITIONING
Reason:
Internal error.
Action:
SMGR034E
Reason:
Internal error.
Action:
SMGR Messages
SMGR035E
Reason:
Internal error.
Action:
SMGR036E
UNEXPECTED END-OF-FILE FOR DELTA FILE
Reason:
CA Endevor SCM did not find an end-of-file marker in the named delta file.
Action:
SMGR037E
VVLL vvll ENTRY IS NOT IN THE SUMMARY LEVEL CHAIN
Reason:
Internal error in BC1PRBLD. Requested version-level missing from the summary level
chain.
Action:
SMGR040E
BASE FILE I/O ERROR
Reason:
CA Endevor SCM has encountered an error when attempting to access the base file.
Action:
See associated I/O error messages.
SMGR Messages
SMGR041E
BASE FILE PREMATURE END-OF-FILE
Reason:
CA Endevor SCM has encountered an end of file marker before it expected to do so.
Action:
SMGR042E
BASE FILE CONTAINS TOO MANY DATA RECORDS
Reason:
CA Endevor SCM has encountered more lines than it expected in the file.
Action:
SMGR050S
Reason:
Internal error.
Action:
SMGR Messages
SMGR051E
SPILL SLOT REQUESTED NOT VALID
Reason:
The requested spill slot is not valid.
Action:
Resubmit the request for a valid spill slot.
SMGR052E
ERROR OPENING SPILL FILE FOR READBACK
Reason:
A spill file error occurred.
Action:
Retry the request, and if the problem reoccurs contact your administrator.
SMGR053E
INTERNAL ERROR - STORE REQUEST AFTER GET OCCURRED
Reason:
Internal error.
Action:
SMGR054E
ERROR WRITING TO SPILL FILE
Reason:
Action:
SMGR Messages
SMGR055E
ERROR ALLOCATING SPILL FILE
Reason:
Action:
SMGR056E
ERROR WRITING TO SPILL FILE DURING INITIAL SPILL
Reason:
Action:
SMGR057E
INDIVIDUAL RECORD LENGTH (nn) GREATER THAN SPECIFIED ON TYPE DEFINITION
(nn)
Reason:
CA Endevor SCM has attempted to place a record in the spill file that is too large for that
file.
Action:
Enlarge the spill area, and retry the request.
SMGR058E
error code ERROR ACQUIRING SPILL CONTROL BLOCK STORAGE
Reason:
CA Endevor SCM has not been able to acquire spill storage.
Action:
SMGR Messages
SMGR060S
Reason:
Internal error.
Action:
SMGR061E
reason ERROR ACQUIRING INITIAL STORAGE
Reason:
CA Endevor SCM was unable to acquire initial storage to satisfy the request.
Action:
SMGR062E
ERROR OPENING [FILE 1|FILE 2] FILE - ddname/data set name(member name)
Reason:
Internal error.
Action:
SMGR063E
MEMBER NOT FOUND
Reason:
CA Endevor SCM could not find the named member.
Action:
Make sure that you have specified the member name correctly, and resubmit the
request.
SMGR Messages
SMGR064E
READ I/O ERROR FROM routine name - DDN=ddname
Reason:
CA Endevor SCM has encountered an I/O error reading from the named data set and
member.
Action:
See the accompanying I/O messages.
SMGR065E
SORT FAILURE - RETURN CODE = return code
Reason:
Internal error.
Action:
SMGR066C
SOME CHANGES HAVE BEEN DETECTED OUTSIDE OF THE COMPARE RANGE FOR THIS
ELEMENT TYPE
Reason:
CA Endevor SCM has detected changes in this element that are outside of the compare
range specified on the type definition.
Action:
None.
SMGR066I
ELEMENT TYPE
Reason:
Informational message. CA Endevor SCM has detected changes in this element that are
outside of the compare range specified on the type definition.
Action:
None.
SMGR Messages
SMGR066W
ELEMENT TYPE
Reason:
CA Endevor SCM has detected changes in this element that are outside of the compare
range specified on the type definition.
Action:
None.
SMGR067E
error code ERROR ACQUIRING SORT RECORD STORAGE
Reason:
There is not enough storage available for the request.
Action:
SMGR068E
ERROR ALLOCATING "SYSOUT" FILE FOR SORT PROCESSING
Reason:
CA Endevor SCM could not allocate a SYSOUT file for sort processing.
Action:
Act on the message that precedes this message.
SMGR069E
EXTERNAL DATA SET EMPTY, COMPARE TERMINATED
Reason:
The external data set specified for the compare is empty.
Action:
Make sure that you have specified the data set name correctly, and resubmit the
compare request.
SMGR Messages
SMGR070E
LINE TABLE LOGIC ERROR
Reason:
Internal error.
Action:
SMGR076E
MATCHUP ERROR - data
Reason:
Internal error.
Action:
SMGR077E
ERROR ALLOCATING TEMPORARY SORT SPILL FILE FOR SORT PROCESSING
Reason:
The reason for this error is contained in the previous message.
Action:
Act on the previous message.
SMGR078E
ERROR ACCESSING LINE NUMBER TABLE DURING COMPARE
Reason:
Internal error.
Action:
SMGR Messages
SMGR079E
REQUESTED error OF end number RETURN OFFSET = offset, TABLE AT base
Reason:
Internal error.
Action:
SMGR080E
BASE FILE I/O ERROR
Reason:
CA Endevor SCM has encountered an error when attempting to access the base file.
Action:
See accompanying I/O error messages.
SMGR081E
BASE FILE PREMATURE END-OF-FILE
Reason:
The file does not contain a logical end of file marker.
Action:
If the error is associated with an element, delete the element and restore it from a prior
unload tape or archive file.
If the error is associated with a component list, use the DELETE action with only
SMGR Messages
SMGR082E
MAXIMUM OF 99,999 INSERTS OR DELETES HAS BEEN EXCEEDED
Reason:
CA Endevor SCM supports a maximum of 99,999 inserts or deletes for any given change
level of an element. This limit has been exceeded.
Action:
Make the desired changes in groups that will result in fewer than the named number of
inserts or deletes.
SMGR083E
Reason:
Internal error in BC1PRBLF. Delta version-level missing from the summary level chain.
Action:
SMGR101S
UNSUPPORTED CALL FUNCTION = function.
Reason:
Internal error.
Action:
SMGR102S
Reason:
Internal error.
Action:
SMGR Messages
SMGR103E
RC=return code CREATE ERROR ACCESSING stage name MASTER FILE
Reason:
CA Endevor SCM has encountered an error when attempting to create an element
record in the master file for the named stage.
Action:
SMGR103S
RC=return code CREATE ERROR ACCESSING stage name MASTER FILE
Reason:
CA Endevor SCM has encountered an error when attempting to create an element
record in the master file for the named stage. The return code is in decimals.
Action:
SMGR104E
MORE THAN ONE TYPE RECORD FOUND: ENV=environment name SYS=system name
TYPE=type name STGID=stage id
Reason:
CA Endevor SCM has encountered more than one type record at the named location.
Action:
SMGR105E
UNABLE TO FIND THE REQUESTED VVLL (vvll) FOR THIS ELEMENT IN THE DELTA FILE
Reason:
CA Endevor SCM attempted to build an element for the version and level specified. This
version and level delta identifier does not exist.
Action:
SMGR Messages
SMGR106E
INCORRECT VVLL NUMBER SPECIFIED ON $SMR REQUEST (SPECIFIED nn - EXPECTED
FROM nn TO nn)
Reason:
The level number specified on the request is not within the range available for this
element.
Action:
Check to make sure the level specified is correct, or remove the level number from the
request.
SMGR107E
COMPONENT INFO (SIZE size1) DOES NOT FIT IN DATA SET (LRECL size2)
Reason:
The record length of the delta library (size2) is not large enough to handle the
component records created by CA Endevor SCM (size1).
Action:
The delta library must be a variable blocked file with a record length of size1. For more
information, see the Installation Guide.
SMGR108E
TYPE RECORD NOT FOUND: ENV=env-name SYS=sys-name TYPE=type-name
STGID=stage-id name.
Reason:
The type record not defined at target location and the action is terminated.
Action:
Define the type at the target location, and redo the request.
SMGR Messages
SMGR109E
A 10 CHARACTER ELEMENT NAME WOULD BE TRUNCATED WHEN WRITTEN TO PDS
SOURCE OUTPUT LIBRARY
Reason:
The source output library is a PDS. A PDS only supports eight character names.
Action:
Reduce the size of the element name to eight characters or less.
SMGR110S
$SMR VALIDATION FAILED, EYE-CATCHER INVALID
Reason:
Internal error.
Action:
SMGR111S
$SMR PARAMETER ERROR, ELEMENT OR COMPONENT MUST BE INDICATED
Reason:
You have submitted a request without specifying either an element or component.
Action:
Resubmit the request with the correct
SMGR112I
[ELEMENT|COMPONENT] element name VVLL vvll DELETED FROM LOCATION
environment name/stage id/system name/subsystem name/type name
Reason:
Informational message. The named element was deleted from the named stage.
Action:
None.
SMGR Messages
SMGR113E
RC=return code READ ERROR ACCESSING stage name MASTER FILE
Reason:
CA Endevor SCM encountered an error when attempting to read the named master file.
Action:
SMGR114E
RC=return code UPDATE ERROR ACCESSING stage name MASTER FILE
Reason:
CA Endevor SCM encountered an error when attempting to update the named master
file.
Action:
SMGR115E
RC=return code DELETE ERROR ACCESSING stage name MASTER FILE
Reason:
CA Endevor SCM encountered an error when attempting to delete the named master
file.
Action:
SMGR116C
SYNCHRONIZATION CONFLICT DETECTED FOR [ELEMENT|COMPONENT] VVLL vvll
Reason:
CA Endevor SCM has detected an occurrence of the element farther along the map that
is not in sync with the element.
Action:
Promote this element along the map carefully. You may need to use the SYNC=Y option
to do so.
SMGR Messages
SMGR116E
SYNCHRONIZATION ERROR DETECTED FOR [ELEMENT|COMPONENT] VVLL vvll
Reason:
You have attempted to move or transfer an element to a location where a version of
that element exists that is not in sync with the version being moved or transferred.
Action:
Retry the action specifying SYNC=Y.
SMGR116W
SYNCHRONIZATION WARNING DETECTED FOR [ELEMENT|COMPONENT] VVLL vvll
Reason:
CA Endevor SCM has detected an occurrence of this element/component further along
the map that is not in sync with this occurrence.
Action:
Promote this element along the map carefully. You may need to use the SYNC=Y option
to do so.
SMGR117I
Element will be synchronized with next element up the map
Reason:
The element is not synchronized with the next occurrence of the element up the map.
The option SYNC=Y was coded on the MOVE/TRANSFER SCL so the element at the target
location will be synchronized.
Action:
No action required.
SMGR Messages
SMGR117W
Reason:
Action:
No action required.
SMGR117C
Reason:
Action:
No action required.
SMGR118S
INVALID COPY FORMAT PARAMETER
Reason:
Internal error.
Action:
SMGR119E
INCORRECT VVLL NUMBER SPECIFIED ON $SMR REQUEST (SPECIFIED vvll - EXPECTED
vvll to vvll)
Reason:
Internal error.
Action:
SMGR Messages
SMGR120I
[ELEMENT|COMPONENT] VVLL vvll FETCHED FOR PROCESSING AT STAGE stage name
Reason:
Informational message. CA Endevor SCM has copied the element to the named stage.
Action:
None.
SMGR121I
[ELEMENT|COMPONENT] VVLL vvll CREATED AT LOCATION environment name/stage
id/system name/subsystem name/type name
Reason:
Informational message. CA Endevor SCM has created the element at the specified
location.
Action:
None.
SMGR122W
NO [ELEMENT|COMPONENT] SOURCE CHANGES DETECTED
Reason:
CA Endevor SCM has moved, updated, added, or transferred the element and found no
differences between the element and a version of the element at the target location of
the action
Action:
None.
SMGR Messages
SMGR123I
xx% PRIOR INSERTS DELETED AND/OR yy% PRIOR DELETES RE-INSERTED
Reason:
Informational message. The request resulted in a regression on the prior level of the
element specified by deleting XX% of statements inserted or reinserting (or both) YY% of
statements deleted in previous updates. Regression occurs when either XX or YY is
greater than the threshold level specified in the associated element type record. This
message is produced when REGRESSION SEVERITY=I on the type definition.
Action:
None. However, it is recommended that the current level be examined in detail to make
sure that the deletes or reinserts (or both) in the current level were intended. If
regression occurs frequently for this element type, contact the administrator to consider
SMGR123W
Reason:
element specified by deleting XX% of statements inserted or re-inserting (or both) YY%
of statements deleted in previous updates. Regression occurs when either XX or YY is
message is produced when REGRESSION SEVERITY=W on the type definition.
Action:
SMGR Messages
SMGR123C
Reason:
message is produced when REGRESSION SEVERITY=C on the type definition.
Action:
SMGR123E
Reason:
message is produced when REGRESSION SEVERITY=E on the type definition.
Action:
Examine the current level in detail to make sure that the deletes or reinserts (or both) in
the current level were intended. If regression occurs frequently for this element type,
contact the administrator to consider increasing the regression threshold.
SMGR Messages
SMGR124I
xx% BASE STATEMENTS DELETED AND/OR NEW INSERTS EXCEED yy% OF BASE
Reason:
Informational message. The request resulted in a regression on the base level of the
element by deleting XX% of the original statements or inserting new statements
equivalent to YY% of the base level (or both). Regression occurs when either XX or YY is
greater than the maximum permissible level specified in the associated element type
record. This message is produced when REGRESSION SEVERITY=I on the type definition.
Action:
None. However, it is recommended that the current version of the element be
examined in detail to make sure that the deletes or re-inserts (or both) in the current
level were intended. If regression occurs frequently for this element type, contact the
administrator to consider increasing the regression threshold.
SMGR124W
Reason:
element by deleting XX% of the original statements or inserting new statements (or
both) equivalent to YY% of the base level. Regression occurs when either XX or YY is
record. This message is produced when REGRESSION SEVERITY=W on the type
definition.
Action:
examined in detail to make sure that the deletes or reinserts in the current level (or
both) were intended. If regression occurs frequently for this element type, contact the
SMGR Messages
SMGR124C
Reason:
record. This message is produced when REGRESSION SEVERITY=C on the type definition.
Action:
SMGR124E
Reason:
record. This message is produced when REGRESSION SEVERITY=E on the type definition.
Action:
SMGR125I
[ELEMENT|COMPONENT] VVLL vvll NOT UPDATED
Reason:
Informational message. A request to Add or Update the element was not completed
because no changes were made. The level number was not incremented.
Action:
None.
SMGR Messages
SMGR127I
[ELEMENT|COMPONENT] VVLL vvll WRITTEN TO:
Reason:
Informational message. The element was successfully written to the named data set as
the named member.
Action:
None.
SMGR128I
[ELEMENT|COMPONENT] VVLL vvll WRITTEN TO ddname
Reason:
Informational message. The element was successfully written to the specified data set.
The member name is the same as the element name.
Action:
None.
SMGR129I
[ELEMENT|COMPONENT] VVLL vvll NOT UPDATED AT stage name
Reason:
Informational message. The element was not updated at the named stage because
there were no changes detected in the element.
Action:
None.
SMGR130I
[ELEMENT|COMPONENT] VVLL vvll CREATED AT LOCATION environment name/stage
Reason:
Informational message. The element was successfully created at the named stage by the
move action.
Action:
None.
SMGR Messages
SMGR131I
SOURCELESS ELEMENT VVLL vvll CREATED AT LOCATION environment name/stage
Reason:
Informational message. The sourceless element was successfully created at the named
stage by the move action.
Action:
None.
SMGR132I
SOURCELESS ELEMENT VVLL vvll UPDATED AT LOCATION environment name/stage
Reason:
Informational message. The sourceless element was successfully updated at the named
stage by the move action.
Action:
None.
SMGR133S
SOURCE MANAGEMENT REQUIRES ELEMENT INFORMATION
Reason:
Internal error.
Action:
SMGR134S
TARGET ELEMENT MAY NOT ALREADY EXIST
Reason:
Internal error.
Action:
SMGR Messages
SMGR135S
ELEMENT MUST ALREADY EXIST
Reason:
Internal error.
Action:
SMGR136I
[ELEMENT|COMPONENT] VVLL vvll CHANGES INCLUDE nn LINES INSERTED AND nn
LINES DELETED
Reason:
Informational message. The message indicates how many lines were inserted and how
many deleted in the indicated level of the element.
Action:
None.
SMGR137I
LEVEL SYNCHRONIZATION BEGINNING
Reason:
Action:
None.
SMGR138I
LEVEL SYNCHRONIZATION COMPLETE
Reason:
Action:
None.
SMGR Messages
SMGR139I
ELEMENT FOUND AT LOCATION environment name/stage id/system name/subsystem
name/type name SELECTED FOR FETCH PROCESSING
Reason:
Action:
None.
SMGR141E
WRITE REQUEST ISSUED AGAINST A READ-ONLY DATA SET
Reason:
Internal error.
Action:
SMGR142I
element VVLL vvll FULL IMAGE DELTA CREATED
Reason:
Informational message. This message appears in the CA Endevor SCM log whenever a
full image delta is created. Symbols VVLL represent the version and level of the element
just created.
Action:
None.
SMGR Messages
SMGR143E
option OPTION NOT AVAILABLE FOR FULL IMAGE DELTA
Reason:
Invalid option when specified against a full image element along with the Print or
Display element commands. Changes are not kept for full image delta elements. Each
level reflects the exact image of the element.
Also invalid during a Move and Transfer action. Move and Transfer with the history
option is invalid when an image delta file is being moved to a location where the target
type is not defined as an image delta. Move and Transfer with history is only valid when
both the source and target location type definition is set to image delta. This action will
fail if the source location is other than image and the target location is image.
Action:
None.
SMGR144E
CAN NOT DETERMINE THE NEW IMAGE NAME CREATED FROM MEMBER AT SOURCE
LOCATION
Reason:
Internal error. During the create delta process, a table is maintained to cross-reference
the source to target image delta member names. This error is generated when the new
delta member name was not found using the source image member name as the key.
Action:
SMGR145E
FULL IMAGE MEMBER MISSING FROM DELTA FILE
Reason:
When image members are copied from the source location to the target location via
information stored in the delta file member, a source member could not be found in the
data set. Action is terminated.
Action:
SMGR Messages
SMGR146E
FULL IMAGE MISSING FROM DELTA FILE FOR ELEMENT AT VVLL vvll
Reason:
Delta image records are missing from the external data set when attempting to restore
image members for the element. Action is terminated.
Action:
SMGR147E
END OF LEVEL MISSING FROM DELTA FILE FOR ELEMENT AT VVLL vvll
Reason:
The delta image record's end-of-level indicator for the level number shown is missing
from the external data set when attempting to restore image members for the element.
Action is terminated.
Action:
SMGR148E
Reason:
Internal error in BC1PSMGR. Requested version-level missing from the summary level
chain.
Action:
SMGR150E
I/O ERROR CLOSING FILE - DDN=ddname
Reason:
CA Endevor SCM has encountered an error when attempting to close the named
member.
Action:
SMGR Messages
SMGR151E
I/O ERROR DELETING MEMBER - DDN=ddname
Reason:
CA Endevor SCM has encountered an error when attempting to delete the named
member.
Action:
SMGR152E
I/O ERROR DURING MEMBER FIND REQUEST - DDN=ddname
Reason:
CA Endevor SCM has encountered an error when attempting to find the named
member.
Action:
SMGR153E
I/O ERROR READING FILE - DDN=ddname
Reason:
CA Endevor SCM has encountered an error when attempting to read the named
member.
Action:
SMGR154E
I/O ERROR WRITING FILE - DDN=ddname
Reason:
CA Endevor SCM has encountered an error when attempting to write to the named
member.
Action:
SMGR Messages
SMGR155E
BASE MEMBER ALREADY EXISTS FOR THIS ELEMENT
Reason:
A member with the requested element name already exists in the named library named
in the following message.
Action:
Resubmit the request using a different element name.
SMGR156E
DDN=ddname DSN=data set name MEM=member name
Reason:
Informational message issued with message SMGR155E. This message names the library
containing the member with the requested element name.
Action:
None.
SMGR157E
A 10 CHARACTER ELEMENT NAME WOULD BE TRUNCATED WHEN USING
REV/IMG/LOG PDS; ACTION NOT ALLOWED
Reason:
A 10-character element name cannot be used if the type's delta is reverse, image, or log
format and the base is a PDS. The element name cannot be greater than eight
characters. The action fails.
Action:
Retry the action using an eight-character element name.
SMGR Messages
SMGR160E
INVALID SOURCE RECORD LENGTH - length EXCEEDS MAXIMUM RECORD LENGTH FOR
TYPE - length
Reason:
The record length of the source exceeds the maximum record length allowed for this
type.
Action:
Classify the source under a type that allows the requisite record length.
SMGR161E
EXPANDED INCLUDE DETECTED IN INPUT SOURCE - CHANGE TO ++INCLUDE/-INC
PRIOR TO ADD/UPDT
Reason:
CA Endevor SCM detected an expanded include member in the source being added or
updated.
Action:
Replace the expanded include member with a ++INCLUDE/-INC statement and resubmit
the request.
SMGR162C
INVALID STATEMENT text - DISCARDED
Reason:
The statement referenced in the message has been discarded.
Action:
If the information in the statement is important, rewrite the statement as a valid
statement and resubmit the job.
SMGR Messages
SMGR163C
LINKEDIT STMT IGNORED: statement
Reason:
The linkage editor control statement [STMT] requested a function that is not supported
by CA Endevor SCM. The rejected statement was a NAME or ALIAS request. This
message applies only to element types with an internal language specification of
LINKEDIT.
Action:
None. However, the request to modify the name of the output load module created by
the request was not executed.
SMGR164E
The element you are about to edit is not synchronized with the next version of this
element up the map.
Reason:
An element selected for editing using Quick-Edit is not synchronized with the next
version of this element in its map.
Action:
Either cancel the edit session and resolve the synchronization problem prior to making
new element modifications or continue the edit session and ignore the synchronization
problems.
SMGR170I
[ELEMENT|COMPONENT] element name DELTA CONSOLIDATION WILL BE
PERFORMED
Reason:
CA Endevor SCM will perform delta consolidation on the named element.
Action:
None required, but you should be sure that you want CA Endevor SCM to perform the
consolidation.
SMGR Messages
SMGR171I
BEFORE CONSOLIDATION, ELEMENT VVLL vvll WOULD CONTAIN nnnn LEVELS
Reason:
Informational message. This message indicates the number of levels, the element will
contain before consolidation.
Action:
None.
SMGR172I
AFTER CONSOLIDATION, ELEMENT VVLL vvll WILL CONTAIN nnnn LEVELS
Reason:
Informational message. This message indicates the number of levels the element will
contain after consolidation.
Action:
None.
SMGR173I
LEVEL vvll THROUGH vvll [AT|FROM] STAGE stage name WILL BE CONSOLIDATED
Reason:
Informational message. This message indicates which levels will be consolidated at the
indicated location.
Action:
None.
SMGR174W
NEW LEVEL NUMBER EXCEEDS 9995, DELTA CONSOLIDATION IS NECESSARY
Reason:
This message indicates that the level just created is the highest allowable level number
for the element.
Action:
If you anticipate further changes to this element, you must consolidate the delta levels.
SMGR Messages
SMGR175E
NEW LVL NBR nnnnn EXCEEDS MAX LVL NBR OF 9996, UNABLE TO CONSOLIDATE,
ACTION TERMINATED
Reason:
An add, update, move, or transfer action has resulted in a level number greater than
9996 at the target of the action. In addition, the base level at the target is such that the
deltas cannot be consolidated.
Action:
Repeat the action specifying with history=n.
SMGR176E
NEW LVL NBR vvll EXCEEDS MAX LVL NBR OF 99.99, CONSOLIDATION DISABLED,
ACTION TERMINATED
Reason:
An ADD, UPDATE, MOVE, or TRANSFER action has resulted in a level number greater
than 9999 at the target of the action. In addition, the base level at the target is such that
the deltas cannot be consolidated.
Action:
You can remove levels from the element by transferring it to another location, deleting
the element from the source location, and transferring back to the original source
location.
SMGR177E
ELEMENT EXTENSION RECORD DELETE FUNCTION FAILED AT TARGET LOCATION
Reason:
The delete element extension record function failed.
Action:
SMGR Messages
SMGR178E
ELEMENT EXTENSION RECORD DEFINE FUNCTION FAILED AT TARGET LOCATION
Reason:
The define element extension record function failed.
Action:
SMGR179E
USER "FROM/TO" LIBRARY DATA UPDATE TO TARGET ELEMENT FAILED
Reason:
CA Endevor SCM attempted to move the MCF data from the source to the target
location. This process failed.
Action:
SMGR180I
REMOVAL OF AGED [ELEMENT|COMPONENT] DELTA WILL BE PERFORMED
Reason:
CA Endevor SCM will perform aged delta removal on the named element.
Action:
None. Informational only.
SMGR180S
INVALID REBUILD FORMAT PARAMETER
Reason:
Internal error.
Action:
SMGR Messages
SMGR181I
BEFORE REMOVAL, [ELEMENT|COMPONENT] VVLL vvll CONTAINS nnnnn LEVELS
Reason:
Informational message. This message indicates the number of levels the
element/component will contain before aged levels are removed.
Action:
None.
SMGR182I
AFTER REMOVAL, [ELEMENT|COMPONENT] VVLL vvll WILL CONTAIN nnnn LEVELS
Reason:
Informational message. This message indicates the number of levels the
element/component will contain after aged levels are removed.
Action:
None.
SMGR183I
LEVEL vvll THROUGH vvll [AT|FROM] STAGE stage name WILL BE REMOVED
Reason:
Informational message. This message indicates which levels will be consolidated into the
base.
Action:
None.
SMGR190E
Reason:
Internal error in BC1PRBMI. Delta version-level missing from the summary level chain.
Action:
SMGR Messages
SMGR200E
Reason:
Internal error in BC1PSMGR at CIMTRUTN. Delta version-level missing from the
summary level chain.
Action:
SMGR201E
Reason:
Internal error in BC1PSMGR at CXDTRUTN. Delta version-level missing from the
summary level chain.
Action:
SMGR202E
dis-option OPTION IS NOT AVAILABLE FOR LOG DELTAS
Reason:
The Change and History display options cannot be used on a log delta element. Only the
current source is kept for this delta type.
Action:
None.
SMGR231E
ELEMENT SOURCED AT LOCATION env/stage/sys/subsys/type
Reason:
Indicates the source location of a sourceless element, if the element is not at the target
location or the element at the target location is sourceless.
Action:
None.
SMGR Messages
SMGR232E
ELEMENT VVLL vvll NOT LAST LEVEL FOR LOG DELTA TYPE
Reason:
An action or a display request was made against a log delta element and the action or
request referred to a source level prior to the current level. With this delta type, only
the current (last) level source is available.
Action:
Retry the action or request using a current source version level.
SMGR234E
SOURCE DELTA CANNOT CHANGE TO TARGET TYPE SPECIFICATION
Reason:
A reverse, forward, or image delta element cannot be converted to the target delta type
of log. A log delta element cannot be converted to a target delta type of reverse,
forward, or image. This condition can occur during a move or transfer action when a log
delta element is targeted to a non-log delta location or when a non-log delta element is
targeted to a log delta location.
Action:
Change your delta type definitions or perform the function using the Transfer to Archive
action followed by Transfer from Archive.
SMGR235I
ELEMENT VVLL vvll LOG DELTA CREATED
Reason:
Action:
None.
SYN Messages
SYN Messages
SYN messages are generated by the catalog synchronization utility. The following list of
SYN messages includes possible causes and corrective actions to take in error situations.
SYN0000I
BEGINNING PHASE 1.
Reason:
Informational. Start of the Master Control File to catalog verification phase of the
verification and synchronization process.
Action:
None.
SYN0000I
BEGINNING PHASE 2.
Reason:
Informational. Start of the catalog to Master Control File synchronization phase of the
verification and synchronization process.
Action:
None.
SYN0001E
NO ENVIRONMENT COMMAND WAS SPECIFIED. SYNCHRONIZATION CHECKS WILL
NOT BE DONE.
Reason:
R/C = 12. An input environment statement was expected, but none was found.
Processing is terminated.
Action:
Specify an environment statement and resubmit the command.
SYN Messages
SYN0002I
ENVIRONMENT env-name MCF ELEMENT TO CATALOG SYNCHRONIZATION STARTING.
Reason:
Informational. Identifies the environment for which the synchronization process is
starting.
Action:
None.
SYN0003I
TOTAL CATALOG SEGMENTS CREATED FOR ENVIRON env-name: count
Reason:
Informational. Identifies the number of catalog segments created for the specified
environment.
Action:
None.
SYN0003I
TOTAL # OF MISSING CTLG SGMTS FROM ENVIRON env-name: count
Reason:
Informational. Identifies the number of catalog segments missing from the specified
environment.
Action:
None.
SYN0004I
TOTAL CATALOG SEGMENTS UPDATED FOR ENVIRON env-name: count
Reason:
Informational. Identifies the number of catalog segments updated for the specified
environment.
Action:
None.
SYN Messages
SYN0004I
TOTAL # OF OLD CTLG SGMTS FOUND IN ENVIRON env-name: count
Reason:
Informational. Identifies the number of old catalog segments found in the specified
environment.
Action:
None.
SYN0005I
TOTAL # OF ELEMENTS PROCESSED FROM ENVIRON env-name: count
Reason:
Informational. Identifies the number of elements processed from the specified
environment.
Action:
None.
SYN0006E
ENVIRONMENT: env-name DOES NOT EXIST.
Reason:
R/C = 12. The environment specified by the user input does not exist in the C1DEFLTS
table. Processing continues with the next environment.
Action:
None.
SYN0007E
$IMR REQUEST FAILED. $IMR ERROR MESSAGE FOLLOWS.
Reason:
R/C = 12. An Inventory Manager error occurred. Processing terminates.
Action:
See the next message for the actual error.
SYN Messages
SYN0008E
C1BMINIT FAILURE. CALL ENDEVOR TECHNICAL SUPPORT.
Reason:
R/C = 12. Internal error occurred. Processing terminates.
Action:
Contact CA Endevor SCM Technical Support.
SYN0009E
PROCESSING TERMINATED.
Reason:
R/C = 12. Processing terminates.
Action:
Contact CA Endevor SCM Technical Support.
SYN0010E
PROCESSING TERMINATED BECAUSE OF CONTROL STATEMENT ERRORS,
RESULT=parser literal.
Reason:
R/C = 12. Processing terminates.
Action:
Refer to the parser literal and any other parser error log created by the utility. Correct
the problem and resubmit job.
SYN0011I
TOTAL # OF ELEMENTS PROCESSED, ALL ENVIRONMENTS: count
Reason:
Informational. Indicates the number of elements processed from all environments.
Action:
None.
SYN Messages
SYN0032I
TOTAL CATALOG SEGMENTS DELETED FOR ENVIRON env-name: count
Reason:
Informational. Indicates the number of catalog segments deleted for the specified
environment.
Action:
None.
SYN0032I
TOTAL # OF ORPHAN CTLG SGMTS IN ENVIRON env-name: count
Reason:
Informational. Indicates the number of catalog segments in the specified environment
that are orphaned.
Action:
None.
SYN0033I
TOTAL CATALOG SEGMENTS PROCESSED FOR ENVIRON env-name: count
Reason:
Informational. Indicates the number of catalog segments processed for the specified
environment.
Action:
None.
SYN0034I
TOTAL CATALOG SEGMENTS PROCESSED, ALL ENVIRONMENTS: count
Reason:
Informational. Indicates the number of catalog segments processed for all
environments.
Action:
None.
SYN Messages
SYN0035E
STORAGE PROBLEM WHILE ACQUIRING ENVIRON ENTRY SPACE.
Reason:
R/C = 12. Processing is terminated.
Action:
Refer to messages contained in the job log.
SYN0036E
$IMR EXTRACT ALL SEGMENTS REQUEST FAILED. $IMR ERROR MESSAGE FOLLOWS.
Reason:
R/C = 12. An Inventory Manager error occurred. Processing terminates.
Action:
See the next message for the actual error.
SYN0037E
BAD PARM STATEMENT ON EXEC STATEMENT, MUST BE UPDATE OR VALIDATE.
Reason:
R/C = 12. Processing terminates. The execution statement did not specify update or
validate.
Action:
Correct the PARM statement and resubmit the job.
SYN0040I
TOTAL # OF EINDEX RECORDS CREATED FOR ENV env-name: count
Reason:
Informational. Identifies the number of element index records created for the specified
environment.
Action:
None.
SYN Messages
SYN0040I
TOTAL # OF MISSING EINDEX RECORDS FOR ENV env-name: count
Reason:
Informational. Identifies the number of element index records missing in the specified
environment.
Action:
None.
SYN0999W
OUT OF SYNC DATA FOUND, DATA has/has not BEEN UPDATED
Reason:
Informational message. The utility found discrepancies between the MCF and the
catalog. If the utility processed in update mode, it corrected the discrepancies. The step
finished with RC 4.
Action:
None.
*ERROR * $SMR ERROR ON DELTA RETRIEVAL, MCF ELEMENT ele-name TYPE
typ-name, PROCESSING BYPASSED.
Reason:
R/C = 12. An error occurred while trying to retrieve the elements long name from its
delta file. The element is bypassed and the job continues to run. At end of processing,
the job ends with a return code of at least 12.
Action:
See previous error messages for additional information.
SYN Messages
*WARNING* LONG NAME NOT FOUND IN DELTA, MCF ELEMENT ele-name TYPE
typ-name USED FOR CATALOG.
Reason:
R/C = 8. For some reason unknown, a long named element did not have its name
recorded in its delta file. The Master Control File element name is substituted for the
long element name. Processing continues. At the end of processing, the job ends with a
return code of at least 8.
Action:
Review all the elements that were created this way. If its name is invalid, retrieve the
element, delete it from CA Endevor SCM, and then add the element back into CA
Endevor SCM with its actual name.
*WARNING* INVALID ELEMENT LENGTH OR NAME FIELD W/IN DELTA FILE, MCF
ELEMENT ele-name TYPE typ-name USED FOR CATALOG.
Reason:
R/C = 8. For some reason unknown, the long named element was recorded incorrectly in
its delta file. The Master Control File element name is substituted for the long element
name. Processing continues. At end of processing, the job ends with a return code of at
least 8.
Action:
Review all the elements that were created this way. If its name is invalid, retrieve the
element, delete it from CA Endevor SCM, and then add the element back into CA
Endevor SCM with its actual name.
*UPDATE* CTLG SGMT: ELEMENT ele-name
TYPE typ-name AT ENV env-name SID stg-id SYS sys-name SBS sbs-name
Reason:
R/C = 4. An out of date element segment was found. The segment was updated with the
Master Control File element data.
Action:
None.
SYN Messages
*OLD * CTLG SGMT: ELEMENT ele-name

Reason:
R/C = 4. An out of date element was found. The utility is running in validation mode, the
catalog is not updated.
*CREATED* CTLG SGMT: ELEMENT ele-name
Reason:
R/C = 4. The catalog did not contain an element entry for the Master Control File
element identified in the above message. A segment was created for it.
*MISSING* CTLG SGMT: ELEMENT ele-name
Reason:
R/C = 4. The catalog did not contain an element entry for the Master Control File
element identified in the above message. The utility is running in validation mode, the
catalog was not updated.
*DELETED* CTLG SGMT: ELEMENT ele-name
Reason:
R/C = 4. A catalog segment was found for a nonexistent Master Control File element
record. The segment was deleted.
*ORPHAN * CTLG SGMT: ELEMENT ele-name
Reason:
R/C = 4. A catalog segment was found for a nonexistent Master Control File element
record identified in the message above. The utility is running in validation mode, no
changes are made to the catalog.
VAL Messages
VAL Messages
VAL messages are generated during processing of the Validate action. The following list
of VAL messages includes possible causes and corrective actions to take in error
situations.
VAL0001I
ELEMENT MASTER VALIDATION STARTED
Reason:
Informational. This message notifies you that the element master validation process has
begun.
Action:
None.
VAL0002E
STATUS OF PROCESSOR OUTPUT IS UNKNOWN - ELEMENT WAS RESTORED W/O
REPROCESSING
Reason:
Error message. This message notifies you that the Restore action was executed for this
element, but it has not been generated following the restore.
Action:
If this element is valid, consider executing the Generate action against it.
VAL0003E
ELEMENT HAS NOT BEEN RE-GENERATED SINCE LAST SOURCE UPDATE
Reason:
Error message. This message notifies you that this element has not been generated
since after the source was last changed.
Action:
If this element is valid, consider executing the Generate action against it.
VAL Messages
VAL0004E
THE LAST GENERATE PROCESSOR EXECUTION FAILED
Reason:
Error message. This message notifies you that the last time this element was generated,
the generate failed.
Action:
If this element is valid, view the listing to determine why the generate action failed.
Correct the error and generate the element.
VAL0005E
ELEMENT IS LOCKED IN PACKAGE: package-id
Reason:
Error message. This message notifies you that this element is currently locked in a
package.
Action:
None.
VAL0006I
ELEMENT MASTER VALIDATION COMPLETE: HIGHEST RC = nn
Reason:
Informational message. This message notifies you that the element master validation
process is complete. The return code indicates if any element master validation errors
were detected.
Action:
None.
VAL Messages
VAL0010I
SYNCHRONIZATION PROCESSING STARTED
Reason:
Informational message. This message notifies you that the synchronization validation
process has begun.
Action:
None.
VAL0011I
A COPY OF THIS ELEMENT WAS FOUND UP THE LOGICAL MAP AT LOCATION:
Reason:
Informational message. This message notifies you that a copy of the element was found
up the logical map and it will be used in the synchronization validation process.
Action:
None.
VAL0012I
ENV: env-name SYSTEM: sys-name SUBSYSTEM: subsys-name TYPE: type-name STAGE
ID: stage-id
Reason:
Informational message. This message notifies you of the location of the copy of the
element found up the logical map that will be used in the synchronization validation
process.
Action:
None.
VAL Messages
VAL0013I
THESE TWO COPIES OF THE ELEMENT ARE SYNCHRONIZED
Reason:
Informational message. This message notifies you that the two copies of the element
are synchronized.
Action:
None.
VAL0014I
NO OTHER COPY OF THIS ELEMENT EXISTS UP THE LOGICAL MAP
Reason:
Informational message. This message notifies you that no other copy of this element
was found up the logical map. Therefore, synchronization validation is not performed.
Action:
None.
VAL0015I
SYNCHRONIZATION PROCESSING COMPLETE: HIGHEST RC = nn
Reason:
Informational message. This message notifies you that the synchronization validation
process is complete. The return code indicates if any element synchronization validation
errors were detected.
Action:
None.
VAL Messages
VAL0020I
SEARCHING FOR AN IN-BETWEEN COPY OF ELEMENT IN THE PHYSICAL MAP
Reason:
Informational message. This message notifies you that two copies of this element were
found in the logical map. Therefore, a search for an in-between copy in the physical
map is performed.
Action:
None.
VAL0021I
AN IN-BETWEEN COPY OF THIS ELEMENT DOES NOT EXIST
Reason:
Informational message. This message notifies you that two copies of this element were
found in the logical map. A search for an in-between copy in the physical map was
performed and no copy exists.
Action:
None.
VAL0022I
SEARCH FOR IN-BETWEEN COPY COMPLETE: HIGHEST RC = = nn
Reason:
Informational message. This message notifies you that the search for an in-between
copy of this element in the physical map is complete. The return code indicates if an
in-between copy of this element exists.
Action:
None.
VAL Messages
VAL0030W
ACM IS NOT INSTALLED AT YOUR SITE. THE COMPONENT VALIDATION OPTION
IGNORED
Reason:
Warning message. The component validation option was specified, but the ASCM
parameter in the C1DEFLTS table is not enabled.
Action:
Determine if the CA Endevor SCM Automated Configuration Manager option is available
at your site. If so, talk to the Administrator to determine why it in not enabled.
VAL0031I
NO COMPONENTS EXIST FOR THIS ELEMENT
Reason:
Informational message. The component validation option was specified, but no
components exist for this element. Therefore, component validation processing is not
performed for this element.
Action:
None.
VAL0032I
NUMBER OF COMPONENTS VALIDATED: cmp-cnt, NUMBER CONTAINING ERRORS:
error-cnt
Reason:
Informational message. The component validation option was specified. This message
indicates how many components were validated and how many errors were detected.
Action:
None.
VSIO and BC1PVSIO Messages
VAL0040W
NO ACTION OPTIONS SPECIFIED ALL VALIDATE ACTION OPTIONS WILL BE
PERFORMED
Reason:
Warning message. None of the action options were specified. The validate action will
assume all were specified.
Action:
None.
VAL0090S
UNABLE TO OBTAIN STORAGE FOR COMPONENT CHAIN - BC1PVLDE, INITRUTN RCreturn-code
Reason:
An unexpected internal error occurred while attempting to obtain storage.
Action:
VAL0091S
ELEMENT MASTER ADDRESS PASSED TO BC1PVLVC BY BC1PVLDE IS INVALID
Reason:
An unexpected internal error occurred. The element master address passed to the
component validation program is invalid.
Action:

This section details messages generated by the VSAM I/O module in the course of CA
Endevor SCM processing, along with possible causes and corrective actions to take.
VSIO Messages
VSI0401E
UNCOVERABLE ABEND OCCURRED DURING VSAM OPEN PROCESSING
Reason:
A VSAM open error has occurred.
Action:
Gather all output, determine the cause of this problem or contact CA Technical Support.
VSI0404E
BACBRUTN - RLS DATASET OPENED BY NON-RLS ddname/dsname
Reason:
A VSAM open error has occurred while attempting to open DDNAME or DSNAME. The
data set should be opened using RLS.
Action:
VSI0406E
NO DDNAME FOUND TO MATCH ddname
Reason:
While trying to use an existing ACB for the DDNAME, no active TIOT entry was found for
the file.
Action:
VSI0407E
NON-ZERO RC reason-code RECEIVED FROM RDJFCB OF DD ddname
Reason:
A RDJFCB operation failed because the DDNAME gave a non-zero reason code.
Action:
Gather all output and contact CA Technical Support.
VSI0408E
DATASET NOT AVAILABLE FOR VSAM RLS ddname/dsname
Reason:
While trying to open DDNAME or DSNAME using RLS, the file was not available for RLS
processing.
Action:
VSI0501E
VSAM FILE dsname HAS BEEN ESTABLISHED WITH INVALID SHARE OPTIONS
Reason:
This message will be followed by VSI0502E.
Action:
See VSI0502E.
VSI0502E
LSERV ACCESS MAY NOT BE USED FOR SHARABLE DATASETS
Reason:
The wrong SHAREOPTION is used for this dataset.
Action:
Correct error and retry.
VSI0510E
SHAREOPTIONS INVALID FOR DSN=
Reason:
Incorrect VSAM share options specified for dsname
Action:
Check for other diagnostic messages. Check definitions for file.
VSI0601I
FILE REORGANIZATION RECOMMENDED FOR VSAM CLUSTER dsname
Reason:
The VSAM data set has too many CI or CA splits.
Action:
Reorganize the file.
VSI0602I
BEGINNING INDEX LEVEL EXPANSION: dsname
Reason:
A VSAM file's index area is being expanded to two levels.
Action:
None.
VSI0603E
UNABLE TO EXPAND INDEX LEVELS
Reason:
An error occurred during the index area expansion.
Action:
VSI0604I
INDEX LEVEL EXPANSION SUCCESSFUL
Reason:
A VSAM file's index area has been expanded to two levels.
Action:
None.
VSI0701E
UNABLE TO RELEASE SHARED STORAGE - ERROR
Reason:
An internal control block could not be found.
Action:
Gather all output and contact CA Technical Support.
VSI0802E
VSAM FILE dsname IS CURRENTLY IN USE BY LSERV
Reason:
A VSAM file could not be opened, because it was already owned by another task.
Action:
VSI0803E
UNABLE TO ESTABLISH LSERV SESSION
Reason:
A VSAM file is under CA L-Serv control, but no CA L-Serv session could be established.
Action:
VSI0804E
OPENRUTN - RLS DATASET OPEN FAILED, RC=16 dname/dsname
Reason:
The VSAM data set is under RLS control, but the open failed.
Action:
VSI0806E
LSERV OR VSAM RLS ACCESS MUST BE USED FOR NON-SHARABLE DATASETS
Reason:
The file has been defined as non-sharable but CA L-Serv or RLS is not activated for this
file.
Action:
Perform any of the following actions:
Correct the share options
Define this file to CA L-SERV
Define this file as an RLS VSAM sphere
VSI1101E
INVALID DATASET, BUFNI/BUFND MODIFIED OR SHARED DATASET OPTION IN USE
Reason:
An error occurred during VSAM VERIFY of the data set.
Action:
VSI1102E
RETURN CODE return-code FEEDBACK CODE feedback-code RECEIVED FROM
macro-name MACRO FOR control-block-name CNTL BLOC
Reason:
While accessing a VSAM file, the VSAM MACRO macro-name has failed with RETURN
CODE return-code and FEEDBACK CODE feedback-code. The return code and the
feedback code are in decimals.
Action:
The return code and feedback code (reason code) can be found in the VSAM section of
IBM's DFSMSdfp Diagnosis Reference or equivalent, or in MVS/QuickRef by entering
Item VSAMxxx, where xxx is the macro-name. Run BC1JCSYN with
PARM='BC1PCSYNUPDATE' to ensure that the Element Catalog and MCFs are in sync.
Then call CA Technical Support immediately with the BC1JCSYN output.
VSI1501E
VSAM FILE HAS BEEN ESTABLISHED WITH SHARE OPTIONS (1,3) or (2,3)
Reason:
The file has been defined as non-sharable, but CA L-Serv or RLS is not activated for this
file.
Action:
Perform any of the following actions:
Correct the SHAREOPTIONS
Define this file to CA L-Serv
Define this file as an RTS file
VSI1502E
LSERV ACCESS MAY ONLY BE USED WITH SHAREOPTIONS (1,3) OR (2,3)
Reason:
A file was under CA L-Serv control but did not have the correct shareoptions.
Action:
Correct the shareoptions or remove the file from CA L-Serv control.
VSI1503E
CATALOG SEARCH INTERFACE ERROR RC=xx, RSN=xx, DSN='dataset name'
VSI1504E
variable text - 'NON ICF CATALOG, NOT SUPPORTED' 'NO ENTRY FOUND FOR THIS
CATALOG' 'DATA GOTTEN FOR THIS CATALOG NOT COMPLETE' 'WHOLE CATALOG NOT
PROCESSED DUE TO ERROR' 'CATALOG PARTIALLY PROCESSED DUE TO ERROR'
'INSUFFICIENT STORAGE FOR GETMAIN' 'INVALID ENTRY TYPE IN CSIDTYPS' 'INVALID
DATA/INDEX OPTION IN CSICLDI' 'INVALID RESUME OPTION IN CSIRESUM' 'INVALID
SEARCH ONE CATALOG OPTION IN CSIS1CAT' 'INVALID NUMBER OF FIELDS VALUE IN
CSINUMEN' 'INVALID WORK AREA LENGTH' 'THE CSIOPTNS VALUE IS NOT F OR BLANK'
Reason:
When trying to determine the DSN shareoptions, the CATALOG SEARCH INTERFACE
(IGGCSI00) gave a non-zero return code. Messages VSI1503E and VSI1504E are issued
together; VSI1504E explains the RC and RSN in VSI1503E.
Action:
VSI1505E
VSAM FILE HAS BEEN ESTABLISHED WITH SHARE OPTIONS (3,3) or (4,3)
Reason:
A file has been defined to CA L-Serv or VSAM RLS but its share options are incorrect for
CA L-Serv or RLS.
Action:
Message VSI1510E indicates the name of the dataset. Contact your administrator.
VSI1506E
RLS ACCESS MAY ONLY BE USED WITH SHARE OPTIONS (1,3) OR (2,3)
Reason:
A file was under RLS's control but did not have the correct share options.
Action:
Correct the shareoptions or remove the file from RLS's control.
VSI1510E
SHR OPTION INVALID FOR DSN=dsname
Reason:
The SHAREOPTIONS are invalid for this data set.
Action:
BC1VSIO Messages
BC1PVSIO E0400
Beginning Index Level Expansion
Reason:
A brand new index or the data set was reorganized and a two-level expansion is needed.
Action:
BC1PVSIO E0402
Finished Index Level Expansion
Reason:
This message indicates that CA Endevor SCM completed expanding the index.
Action:
Appendix A: Trace Information

In cases of abnormal software termination (ABEND), a calling path trace back is
generally produced. The trace back data is written to an output media selected from the
following list in order of availability:
1.
File BSTERR (not available to T/P monitors) if provided
2.
User's Terminal (IDMS, TSO, CMS...)
3.
System console log
You should have this trace information available when you call your CA Endevor SCM
Administrator.
Trace Back Data

The following example shows a typical trace as shown on a terminal:
BSTPOPSV: E001 MACRO $BLOAD
RC=028
BC1PSM10: F000 ABEND CODE=MACR NUMBER=3009
BC1PSM10: F000 ABEND CODE=MACR NUMBER=3009
BST PRODUCT: ENDEVOR
VERSION: X.X RELEASE: XNNNN
OPERATING SYSTEM: MVS/XA
RELEASE: 038
TASK/JOB/USERID: DA1FB22
CALL FROM $FUNC=$BABEND EPA=00051BA8 R1=00058948 R14=80051E7C STACK=000588FO
CSECT=BSTPMPGM 06/17/01
CALL FROM $FUNC=BSTPOPSV EPA=0004E5E8 R1=00058818 R14=8004E67A STACK=00058890
CALL FROM $FUNC=RESCHECK EPA=0004E6E8 R1=00058818 R14=8004E7D4 STACK=000587C0
CALL FROM $FUNC=BSTPOPSV EPA=0004E5E8 R1=00000000 R14=8004E68C STACK=00058760
CSECT=BSTPOPSV 06/17/01
CALL FROM $FUNC=BC1PINIT EPA=03A3BD98 R1=000586F8 R14=83A3BFC8 STACK=00058698
CSECT=BC1PINIT 09/09/01
CALL FROM $FUNC=INITCALL EPA=03A36DE8 R1=00058660 R14=83A36E74 STACK=00058608
CALL FROM $FUNC=BC1PSM10 EPA=03A36A08 R1=00057658 R14=83A36B3E STACK=000575F8
CALL FROM PROGM=BC1PSM10 ASM DT=08/20/01 VERS=0002 EPA=83A36998 RET=83A369FC
IEA995I SYMPTOM DUMP OUTPUT
USER COMPLETION CODE=3009
TIME=09.47.22 SEQ=55966 CPU=0000 ASID=01B9
PSW AT TIME OF ERROR 078D1000
80051EAO ILC 2 INTC OD
ACTIVE LOAD MODULE=BSTPMOPS ADDRESS=0004E538 OFFSET=00003968
DATA AT PSW 00051E9A - 00181610 0A0D47FO C3001812
GPR 0-3 80000000 80000BC1 00000BC1 D4C1C3D9
***
Appendix A: Trace Information 1031
Trace Back Data
The call trace displays the modules and subfunctions at the point of ABEND. The fields in
bold type vary with each trace, and are explained as follows:
BC1PSM10
Identifies the module that produced the abend.
ABEND CODE=MACR
Identifies the abend code.
NUMBER=3009
Identifies the user abend number associated with the abend.

EndevorSCM MessagesRef ENU

Uploaded by

Copyright:

Available Formats

EndevorSCM MessagesRef ENU

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EndevorSCM MessagesRef ENU

Uploaded by

Copyright:

Available Formats

CA Endevor Software Change

Messages and Codes Reference Guide

CA Technologies Product References

CA Endevor Software Change Manager (CA Endevor SCM)

CA Endevor Software Change Manager Automated Configuration (CA Endevor

CA Endevor Software Change Manager Parallel Development (CA Endevor Parallel

CA Endevor Software Change Manager External Security Interface (CA Endevor

CA Endevor Software Change Manager InfoMan Interface (CA Endevor InfoMan

CA Endevor Software Change Manager CA Librarian Interface (CA Endevor CA

CA Endevor Software Change Manager Integration for the Natural Environment

CA Endevor Software Change Manager CA Netman Interface (CA Endevor CA

CA Endevor Software Change Manager CA Roscoe Interface (CA Endevor CA

CA Librarian Base for z/OS (CA Librarian)

CA Panvalet for z/OS (CA Panvalet for z/OS)

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

Version 16.0, Third Edition

For PTF RO67723, April 2014:

Version 16.0, Second Edition

C1G Messages (see page 269)Updated as follows:

Added messages C1G0120W and C1G0475W.

Changed the message number C1G0005E to C1G0005S, with no changes to the

Removed obsolete message C1G0455I.

C1R Messages (see page 424)Updated as follows:

Updated the text, reason, and action for message C1R0028E.

Added message C1R0041I.

JRCV Messages (see page 809)Added message JRCV011W.

ACM Messages (see page 15)Added message ACMR035E.

C1F Messages (see page 269)Added message C1F0001E.

C1G Messages (see page 269)Added message C1G0455E.

C1I Messages (see page 394)Added message C1I0022E.

C1LB Message (see page 400)Updated message text for C1LB003E.

C1R Messages (see page 424)Added message C1R100I.

C1X Messages (see page 456)Added messages C1X0516E and C1X0517I.

C1Y Messages (see page 485)Added message C1Y0008E.

ENBE Messages (see page 516)Updated message ENBE192E. Added message

PDM Messages (see page 824)Added messages PDM0049E and PDM0049I.

PKMR Messages (see page 883)Added messages PKMR130I through PKMR142I.

SMGR Messages (see page 960)Updated message SMGR157E. Added messages

SYN Messages (see page 1006)BEND--C1BMX Messages (see page 210)Added

Module Numbers (mmmm) ....................................................................................................................................... 13

Chapter 2: Error Codes and Messages

0047 Abend Code ....................................................................................................................................................... 15

C1I Messages ............................................................................................................................................................ 394

10 Messages and Codes Reference Guide

VSIO Messages ................................................................................................................................................ 1022

Appendix A: Trace Information

Trace Back Data ...................................................................................................................................................... 1031

Chapter 1: Format and Conventions

Prefixmodule numbersuffix. Messages in this format are generated by the SCL

Module Numbers (mmmm)

Message Numbers (nnn or nnnn)

Chapter 1: Format and Conventions 13

A severity code (x) if the message is in the prefix-message number-suffix format

14 Messages and Codes Reference Guide

Chapter 2: Error Codes and Messages