CA7 33 Messages

CA-7®
Message Guide
3.3
This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for
the end user's informational purposes only and is subject to change or withdrawal by Computer Associates Interna-
tional, Inc. (“CA”) at any time.
THIS DOCUMENTATION MAY NOT BE COPIED, TRANSFERRED, REPRODUCED, DISCLOSED, OR

DUPLICATED, IN WHOLE OR IN PART, WITHOUT THE PRIOR WRITTEN CONSENT OF CA. THIS DOC-
UMENTATION IS PROPRIETARY INFORMATION OF CA AND PROTECTED BY THE COPYRIGHT LAWS
OF THE UNITED STATES AND INTERNATIONAL TREATIES.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS”
WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRAN-
TIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN
NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR
DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT
LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS
EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.
THE USE OF ANY PRODUCT REFERENCED IN THIS DOCUMENTATION AND THIS DOCUMENTATION
IS GOVERNED BY THE END USER'S APPLICABLE LICENSE AGREEMENT.
The manufacturer of this documentation is Computer Associates International, Inc.
Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and
(2) or DFARS Section 252.227.7013(c)(1)(ii) or applicable successor provisions.
First Edition, September 2000
 1988-2000 Computer Associates International, Inc.

One Computer Associates Plaza, Islandia, NY 11749
All rights reserved.
All trademarks, trade names, service marks, or logos referenced herein belong to their respective companies.
Contents
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 Summary of Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.1.1 Product Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.1.2 Documentation Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.2 New or Changed Messages at Version 3.3 . . . . . . . . . . . . . . . . . . . . . 1-6
1.2.1 Chapter 1 - AR through CA7Mxxxx . . . . . . . . . . . . . . . . . . . . . 1-6
1.2.2 Chapter 2 - CA-7.A through CA-7.X . . . . . . . . . . . . . . . . . . . . 1-12
1.2.3 Chapter 3 - CA-7.000 through CA-7.999 . . . . . . . . . . . . . . . . . . 1-14
1.2.4 Chapter 4 - CDSI through RSCx . . . . . . . . . . . . . . . . . . . . . . 1-15
1.2.5 Chapter 5 - SANx through SJR2 . . . . . . . . . . . . . . . . . . . . . . . 1-16
1.2.6 Chapter 6 - SLFA through SPOR . . . . . . . . . . . . . . . . . . . . . . 1-17
1.2.7 Chapter 7 - SPO0 through XTRK . . . . . . . . . . . . . . . . . . . . . . 1-19
1.2.8 Appendix A - Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Chapter 2. AR - CA7M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1 AR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.2 BCLP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
2.3 BK0x Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
2.4 BSTR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
2.5 BTSO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
2.6 CACR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
2.7 CAL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
2.8 CAXPS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102
2.9 CA7M Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-120
Chapter 3. CA-7.A - CA-7.X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1 CA-7.AIJC Through CA-7.DT60 Messages . . . . . . . . . . . . . . . . . . . . 3-2
3.2 CA-7.D32V Through CA-7.VB99 Messages . . . . . . . . . . . . . . . . . . . 3-13
3.3 CA-7.VTAM Through CA-7.V001 Messages . . . . . . . . . . . . . . . . . . 3-71
3.4 Format for VSAM Database Messages . . . . . . . . . . . . . . . . . . . . . . 3-73
3.5 CA-7.V002 Through CA-7.V020 Messages . . . . . . . . . . . . . . . . . . . 3-74
3.8 CA-7.V300 Through CA-7.V329 Messages . . . . . . . . . . . . . . . . . . 3-100
3.14 CA-7.W Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-125
3.15 CA-7.X Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-126
Chapter 4. CA-7.000 - CA-7.999 . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 CA-7.000 Through CA-7.094 Messages . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2 CA-7.100 Through CA-7.151 Messages . . . . . . . . . . . . . . . . . . . . . 4-13
Contents iii
4.4 CA-7.3XXX Through CA-7.378 Messages . . . . . . . . . . . . . . . . . . . . 4-20
Chapter 5. CDSI - RSCx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1 CDSI Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.2 DPCH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.3 DTxx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.4 EDTx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.5 GRLA Through GRLX Messages . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
5.6 HEDT Through HISx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
5.7 HLP0 Through HS0x Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
5.8 INxx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
5.9 JCKn Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
5.10 L2xxx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
5.11 MLRF Through MNU0 Messages . . . . . . . . . . . . . . . . . . . . . . . . 5-36
5.12 QMxx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
5.13 RMS1 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
5.14 RSCx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
Chapter 6. SANx - SJR2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.1 SANx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6.2 SATO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
6.3 SCMx Through SCM9 Messages . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
6.4 SCNI Through SCN0 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
6.5 SCO0 Through SCRJ Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
6.6 SDxx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38
6.7 SFCx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39
6.8 SFEx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54
6.9 SIRx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56
6.10 SJC0 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-59
6.11 SJLx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61
6.12 SJRx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-64
Chapter 7. SLFA - SPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

7.1 SLFA Through SPOE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.1.1 SASSSLIY Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
7.2 SMF0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
7.3 SMxx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
7.4 SPOx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-55
Chapter 8. SPO0 - XTRK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

8.1 SPO0 Through SPO9 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
8.2 SPRG Through SRC2 Messages . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
8.3 SSM0 Through SYS0 Messages . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
8.4 TIQ1 Through Tnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 8-46
8.5 UTLx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-51
iv CA-7 3.3 Message Guide

8.6 U7SVC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-62
8.7 WPxx Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-65
8.8 XREF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-71
8.9 XTRE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-72
8.10 XTRK Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-74
Chapter 9. Database Verification (DBVR) . . . . . . . . . . . . . . . . . . . . . . 9-1

9.1 000 Through 255 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Appendix A. Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Contents v
vi CA-7 3.3 Message Guide
Chapter 1. Introduction
This publication lists the messages and codes produced by CA-7. This guide is intended
for all users of CA-7.
The messages and codes are arranged in alphanumerical order for easy reference. (This
includes messages with hex prefixes.) The basic format of the guide is to give the code
and message, an explanation of the error condition, and the required action to facilitate
recovery, where recovery is necessary.
Some of the messages produced are information messages and require no action. Some
messages have multiple reasons for the message.
Chapter 1. Introduction 1-1

1.1 Summary of Revisions
This topic explains changes to both CA-7 and to the documentation.
1.1.1 Product Changes

CA-7 Version 3.3 contains the following major enhancements:
Parallel Sysplex Exploitation
CA-7 can optionally maintain a memory structure in the Coupling Facility in which
participating ICOMs record tracking data. One or more Host ICOM(s) read from the
memory structure and write to the Communication data set. This can significantly
reduce I/O contention and increase feedback throughput.
UNIX System Services Interface
The OS/390 UNIX System Services (USS) CA-7 interface allows communication
with CA-7 from the USS environment. The interface can be called directly from the
UNIX shell or from the IBM USS batch interface (BPXBATCH).
CA-7 CCI Interface
The CA-7 CCI interface allows two-way communication with CA-7 from other
address spaces and environments. The interface can be engaged in a batch mode, in
a REXX address environment or it can be called directly from a user program. It
accepts single or stacked commands as input and returns the CA-7 output from the
commands as if they had been executed in batch mode.
Critical Path Monitoring
Through integration with CA-OPS/MVS II, Unicenter TNG and Unicenter TNG
MVS Event Manager Option (MEMO), CA-7 can support the definition and moni-
toring of critical job flows within the CA-7 workload. CA-OPS/MVS II provides
management and administration of critical path displays.
Mixed Case Support in CA-7 Editor
Character translation controls can be set in the CA-7 Editor. New Editor subcom-
mands 'UPPER' and 'MIXED' determine whether editor data is translated to uppercase
or left "as is."
These subcommands are enabled with a new initialization file option. If this option
is not coded, then all edit data is translated to uppercase.
Job Completion Tracking Precision
CA-7 records job completion times in hundredths of seconds. This allows job com-
pletions to be discriminated with a high degree of precision, thus reducing the likeli-
hood of requirement posting ambiguities where jobs complete within the same
minute.
1-2 CA-7 3.3 Message Guide

Display Duplicate Days for RESOLVe

CA-7 can optionally display the duplicate RESOLV day(s) in new message
SRC1-137. This occurs when a job is scheduled to execute the same day under two
or more different Schedule IDs. With this information one can more quickly and
efficiently determine the source of the scheduling conflict.
VRM Device Control
Virtual Resource Management (VRM) Device Control provides an alternative to
Workload Balancing control of job submission based on tape drive availability.
VRM resource count resources representing the number and type of storage devices
used by the job are defined dynamically during CA-7 LOAD processing.
Workload Balancing only permits two types of tape drives. With VRM Device
Control, the number and structure of device groups is determined by the user.
CA-7 Command Retrieval
Command line input for CA-7 VTAM terminals is recorded in storage and may be
retrieved with the /FETCH command. When the /PFnn command is used to associate
/FETCH with a PF key, the CA-7 user can conveniently retrieve the last five CA-7
commands entered at an online terminal.
CA-7 Base Calendar Security
CA-7 security can allow clients to define CA-7 base calendar names to an external
security product and secure user access to individual base calendars.
REXX Address Environment
Using the new CA-7 CCI interface, CA-7 allows REXX programs to pass commands
to CA-7 and take action based on the output from those commands.
Job 'Purge' Function
The DB.1 (Job) panel provides a new function, PURGE, which deletes all CA-7 data-
base records related to a job. In addition to the standard delete processes, the
PURGE function deletes incoming trigger definitions, requirement successor defi-
nitions, and the CA-11 CMT member for the job.
Suppress LATE Designation
Through an Initialization File option, the PROMPTS field on the DB.1 (Job) panel
can be used to indicate certain jobs should never be marked as LATE on status dis-
plays. This means operations and production control staff will not be distracted
when test or non-critical jobs do not complete on time.
CSA Chains Above the 16M Line
CA-7 CSA SMF and Trailer chains now reside in extended CSA (above-the-line),
thereby reducing utilization of this critical resource.
Automated Recovery Facility (ARF) Enhancements
CA-7 can optionally add a LOGON parameter to the ARF TSO SEND command to
cause messages to be retained until the user logs on to TSO. Also, support for ARF
has been added to the Database Transportability facility.

Prior Run Queue Expansion

The maximum size of the Prior Run Queue is now approximately twice as large as in
prior releases.
CA-7 JCLCheck Common Component
The CA-JCLCheck Common Component is provided in place of the CA-7 JCL
syntax checker.
Documentation Files on Tape
The current CA-7 documentation files are provided in IBM Book Manager and PDF
format on the product tape.
Other Enhancements:
– SMF Purge records may optionally be sent to a test copy of CA-7. This allows
detection of pre-execution JCL Errors by the test copy.
– The Scratch and Disk Queue Table queues can be formatted during a CA-7
ERST start which facilitates use of VIO to improve performance.
– The LJOB command provides a new option, LIST=RQEXCP, that lists only
those requirements with a SKIP or ONLY indication.
– The reverse forecast commands, FRJOB and FRQJOB, have a new option,
LIST=HDRS. This will limit the display to only the target job and all 'header'
jobs.
– Database Transportability now supports a new keyword, NODSNS, for
SASSDT30 which prevents the generation of data set definitions.
– The LQ family of commands (LREQ, LRDY, LACT, and so forth) now support
a Schedule ID filter, SCHID=.
– The LRLOG command has a new sequence option, SEQ=REV, which causes
entries to be displayed in reverse date/time sequence (most recent first).
– The OPTIONS initialization file statement has a new keyword DPROCCOM= to
enable comment statements in CA-Driver procedures.
– The OPTIONS initialization file statement has a new keyword EXTSCHID= to
set a default schedule ID for externally tracked jobs that are not assigned a non-
zero schedule ID from the SASSEXTT table.
– The CA-7 CAIRIM initialization module now accepts a new reinitialization
parameter (REINIT=UTABS) to reload only user defined table modules.
– The /DISPLAY command has a new STATUS option (/DISPLAY,ST=CA7) to
describe the current copy of CA-7 (VTAM application ID and so forth).

1.1.2 Documentation Changes

The documentation for CA-7 Version 3.3 differs from previous releases as follows:
The documentation set has been engineered to take advantage of the latest technology
for online viewing, keyword searching, book marking, and printing. The set consists
of a hard copy CA-7 Getting Started guide and Version 3.3 of CA-7 for OS/390 doc-
umentation in both IBM BookManager and Adobe Acrobat Reader format on the
tape.
Unicenter TNG Framework for OS/390 is composed of the services formerly known
as CA90s and Unicenter TNG Framework.
Reading Syntax Diagrams in the CA-7 Commands Guide explains how to read the
command syntax used in all guides.
Technical changes are identified by a revision bar (|) in the left margin. Revision bars
are not used for editorial changes and new manuals.

1.2 New or Changed Messages at Version 3.3
The following messages are new or changed since the previous version of CA-7:
1.2.1 Chapter 1 - AR through CA7Mxxxx
Message number Message

AR31-00 ENTER INPUT DATA
AR31-02 ARFSET NOT FOUND
AR31-07 ARFSET ALREADY EXISTS
AR32-17 TOO MANY DEFINITIONS -- MAX IS 20
CAL2A085E NAME OR JOBSET NAME OR MASK REQUIRED.
CAL2A086E Too much data for single call. Please qualify request.
CAL2A088E FLOW ID REQUIRED FOR DELETE
CAL2A089E ID/NAME/SCHID/DUPID REQUIRED FOR DELETE
CAL2A090E INVALID PR_VIEW TYPE
CAL2A091E INVALID DELETE TYPE REQUESTED
CAL2A092E SYMBOLIC JCLLIB NOT SUPPORTED BY YOUR RELEASE OF CA-7
CAL2A093E ARF FACILITY NOT SUPPORTED BY YOUR RELEASE OF CA-7
CAL2A099E INVALID L2WKFLAG VALUE.
CAL2A507 SYNTAX ERROR PARSING ACB NAME FOR SESSION
CAL2A618E (xx yyyy) QUERY TYPE NOT SUPPORTED BY API TABLE : nnnnnnnn
CAL2C100E UNABLE TO GETMAIN STORAGE FOR xxxxxxxx RC=cccc
CAL2C101E ERROR RETURN FROM IXCQUERY CALL: TYPE=tt R15=cc INFO=iiiiiiii
CAL2C102E ERROR FROM tttttttt CALL: RC=rr CC=cccccccc ffffffff
CAL2C103W CF NOT ENABLED: xxx...xxx
CAL2C150W CA-7 ICOM COUPLE FACILITY STRUCTURE IS FULL. TASKS WAITING.
CAL2C151E ERROR RETURN FROM ICMC CALL (ttt). FUNC=ffffffff RC=rr CC=cc
CAL2C152E UNKNOWN ECB POST TO ICOM CF TASK
CAL2C200I CF STRUCTURE CONNECTED
CAL2C201I CF MONITORING STARTED


CAL2C202I CF BUFFER WRITTEN TO xxxx
CAL2C203I CF BUFFER READ FROM xxxx
CAL2C204I CF STRUCTURE DISCONNECTED
CAL2C205I CF TERMINATION COMPLETE
CAL2C206I CF MONITORING STOPPED
CAL2C250I CF TASK HAS POSTED SMF TASK
CAL2C251I CF TASK HAS POSTED TRL TASK
CAL2C300W X2W0 ESTAE ENTERED - WIP=wwww (aaaa) (pppppppp): ddd...ddd
CAL2C301W 'SUBMIT' CLASS/RESOURCE NOT DEFINED TO EXTERNAL SECURITY. FUNC-
TION ALLOWED.
CAL2C401I SESSION INIT SENT.
CAL2C402I DATA CLOSE SENT. (EOD)
CAL2C403I DATA CLOSE RECEIVED.
CAL2C404I SESSION END SENT.
CAL2C452I (X2W) CCIF=ffff RC=rr CC=cc: CCI=f2f2 RC=r2 CC=c2 rrr...rrr
CAL2C501I ***** INPUT TO CA-7 CCI BATCH INTERFACE *****
CAL2C502I ***** END OF INPUT TO CA-7 CCI BATCH INTERFACE *****
CAL2C503W ***** NO CA-7 COMMANDS IN INPUT *****
CAL2C504I ***** RESPONSES RECEIVED FROM CA-7 *****
CAL2C505I ***** END OF CA-7 RESPONSES *****
CAL2C506W ***** NO CA-7 RESPONSES RECEIVED *****
CAL2C508W ERROR MSGS FOUND IN OUTPUT. MSGS MATCHED=xxx, HIGH CC=ccc
CAL2C509I CA-7 CCI BATCH PROCESS COMPLETE. RC=rrrr CC=cccc
CAL2C580W WARNING - DD STATEMENT IS MISSING OR INVALID: dddddddd
CAL2C581W UNABLE TO OPEN ERRORS DD. MESSAGE TABLE ERRORS WILL NOT BE
REPORTED.
CAL2C582W ERROR MSG TABLE MATCH (CC=ccc): ...text...
CAL2C590E INVALID PARAMETER LIST
CAL2C591E INVALID PARAMETER STARTING WITH (xxxxxxxx) - ABORTING
CAL2C592E DD STATEMENT IS MISSING OR INVALID: dddddddd
CAL2C593E ERROR DURING DCB OPEN: dddddddd


CAL2C594E UNABLE TO GETMAIN STORAGE FOR xxxxxxxx
CAL2C595E UNABLE TO LOAD MODULE mmmmmmmm . RC=rrrr
CAL2C596E NON-ZERO RETURN FROM CA-7 CCI INTERFACE. RC=rrrr CC=cccc
CAL2C600W VARIABLE xxxxxxxx COULD NOT BE RETRIEVED--CODE cc
CAL2C601E UNABLE TO ACCESS CA-7 MODULE CAL2X2W0
CAL2C602E CA-7 COMMAND STRING IS MISSING
CAL2C901E INVALID PARAMETER: xxxxxxxx: ABORTING
CAL2C902E UNABLE TO LOAD MODULE mmmmmmmm. RC=rrrr
CAL2C903E CA-7 RECEIVER NOT FOUND (aaa...aaa/nnn...nnn)
CAL2C904E BUFSIZE FROM CA-7 INVALID.
CAL2C905E CA-7 XTM NOT RESPONDING (aaa...aaa/nnn...nnn)
CAL2C906E XTM INIT FAILED. RC=rr RSN=cc TEXT=ttt...ttt
CAL2C907E INVALID RECORD RECEIVED. REC = rrr...rrr
CAL2C908E UNEXPECTED REC RECEIVED. EXPECTED eeeeeeee RECEIVED rrrrrrrr (zzzz)
CAL2C909E INVALID BATCH CMD: ccc...ccc
CAL2C927E (ttt) CCI ERROR FUNC=ffff RC=rr CC=cc TEXT=xxx...xxx
CAL2C928E (ttt) CCIF CALL FAILED: FUNC=ffff RC=rr CC=cc
CAL2C950E BATCH SUBMIT SECURITY VIOLATION - SKIPPING TO NEXT /LOGON
COMMAND
CAL2P001E INVALID PARMLIST RECEIVED: xxxxxxxx
CAL2P002E UNABLE TO GETMAIN STORAGE FOR xxxxxxxx
CAL2P003E UNABLE TO LOAD MODULE xxxxxxxx
CAL2P004E INVALID xxxxxxxx IN CA7PARMS STARTING WITH yyy...yyy
CAL2P005E ERROR FROM CA-7: xxx...xxx
CAL2P006E ERROR FROM CA-7 CCI CALL : RC=rrrr CC=cccc
CAL2P050I REQUEST xxx: FUNC=ffff ARG=aaa...aaa RC=rrrr CC=cccc SUCC=ssss
CAL2P051I RETURN FROM CA-7 CCI CALL : RC=rrrr CC=cccc CMD=cccccccc
CAL2P060I **** CAL2CPCB AT INITIALIZATION ****
CAL2P061I **** CMD INPUT TO CA-7 CCI ****
CAL2P062I **** CMD OUTPUT FROM CA-7 CCI: RC=rrrr CC=cccc ****
CAL2P063I **** READ CALL PARAMETER LIST


CAL2P064I **** READ RESULTS: RC=rrrr CC=cccc : ARGUMENT=aaa...aaa
CAL2XV01I CA-7 CROSS-PLATFORM TRACKING CHECKPOINT CONVERSION STARTED
(V3.2 TO V3.3)
CAL2XV02I CHECKPOINT ENTRY ADDED : xxxxxxxx (yyyy/ddd hh:mm:ss.th)
CAL2XV03I PROFILE MEMBER BYPASSED : xxxxxxxx REASON=rrr...rrr
CAL2XV09I CA-7 CROSS-PLATFORM TRACKING CHECKPOINT CONVERSION COMPLETE
(V3.2 TO V3.3)
CAL2XV10E XCKPT OUTPUT DCB OPEN FAILED.
CAL2XV11E XCKPT INPUT DCB OPEN FAILED.
CAL2XV12E XCKPT FILE IS NOT EMPTY.
CAL2XV13E RDJFCB CALL FAILED FOR PROFILE DD (x).
CAL2XV14E MONITOR= VALUE NOT FOUND IN PROFILE MEMBER CACCENV.
CAL2XV15E NO MEMBERS FOUND IN PROFILE.
CAL2XV16E MEMBER CACCENV NOT FOUND IN PROFILE.
CAL2XV17E PROFILE OPEN FAILED.
CAL2X014E Request NOT submitted : Job jjjjjjjj (####) Node nnnnnnnn
CAL2X015E UNABLE TO LOAD MODULE CAL2CCIF. RC=cccc - process aborted.
CAL2X101I CA-7 CROSS-PLATFORM TRACKING SYSTEM (XTRK) IS INITIALIZING (Vx.y)
CAL2X102I CA-7 CROSS-PLATFORM TRACKING SUB-TASK ACTIVE: ttt...ttt
CAL2X103I CA-7 CROSS-PLATFORM TRACKING (XTRK) IS ACTIVE FOR xxxx
CAL2X104I XTRK MONITOR=mmmmmmm LOCAL NODE=nnn...nnn
CAL2X107I CROSS-PLATFORM TRACKING (XTRK) HAS RECEIVED A STOP COMMAND
CAL2X108I ALL CA-7 CROSS-PLATFORM TRACKING SUB-TASKS HAVE TERMINATED
CAL2X109I CA-7 CROSS-PLATFORM TRACKING (XTRK) HAS TERMINATED
CAL2X140W *WARNING* CA-7 XTRK CKPT FILE HOST SYSTEM ID CONFLICT *WARNING*
CAL2X141W xxxx: MONITOR=mmmmmmm NODE=nnn...nnn
CAL2X142I OVERRIDE THE CA-7 XTRK CKPT FILE SYSTEM ID? (REPLY Y FOR YES, ANY
OTHER CHARACTER FOR NO)
CAL2X150I XTRK COMMAND PROCESSING COMPLETE: ccc...ccc
CAL2X151W INVALID XTRK COMMAND IGNORED: ccc...ccc
CAL2X152W XTRK COMMAND PROCESS ERROR: ccc...ccc
CAL2X154I xxx NODE NAME=


CAL2X155I NODE STATUS LAST ACTIVITY CHECKPOINT DATE/TIME
CAL2X156I nnn...nnn ssssssssss yyyy/ddd hh:mm:ss.th yyy2/dd2 hh:mm:ss.th
CAL2X157I XTRK xxxx TABLE DOES NOT HAVE ANY ENTRIES.
CAL2X158I NO XTRK NODE TABLE ENTRIES MATCH SELECT CRITERIA.
CAL2X159I TRACE STATUS: PRT(p) CON(c) PRTDD(dddddddd,ddddd) SNAPDD(sssss,ssss)
CAL2X160W UNABLE TO HONOR SNAP COMMAND. SNAP IS CLOSED, OR SNAP DD IS NOT
AVAILABLE.
CAL2X161W UNABLE TO OBTAIN xxxx LOCK WORD. LOCK BEING FORCED (own/cur).
CAL2X162W cc...cc COMMAND FAILED: xxx...xxx
CAL2X170I XTRK SYNCHRONIZATION (yyyy/ddd hh:mm:ss.th) NODE=nnn...nnn
CAL2X171I XTRK HAS CONTACTED NODE nnn...nnn
CAL2X174W XTRK UNABLE TO CONTACT NODE nnn...nnn
CAL2X177W XTRK HAS LOST CONTACT WITH nnn...nnn
CAL2X178W XTRK MGR POSTED WITH UNKNOWN COMMAND CODE
CAL2X181I XTRK EXTERNAL EVENT TABLE RE-BUILT. ALL NODES WILL BE
RE-SYNCHRONIZED
CAL2X182W XTRK EXTERNAL EVENT TABLE NOT BUILT: xxx...xxx
CAL2X183W XTRK EXTERNAL EVENT TABLE DOES NOT HAVE ANY ENTRIES.
CAL2X184W NO XTRK EXTERNAL EVENT TABLE ENTRIES MATCH SELECT CRITERIA.
CAL2X185I TRIGID TYPE XEVENT ENTRY INFORMATION
CAL2X186I tttttttt xxx = iii...iii
CAL2X199I VALID CMDS ARE: STOP, ADDNODE, BLDXEVT, DELNODE, NODE, NODEN,
NODEX, PING, SNAP, TRC AND XEVT
CAL2X201I XTRK FBK xxxxxxxx (yyyy/ddd hh:mm:ss.th) tttttttt iii...iii nnn...nnn
CAL2X202E XTRK FBK RECORD FORMAT ERROR: xxx...xxx REC=rrr...rrr NODE=nnn...nnn
CAL2X301I CA-7 SMF REC: SMF=xx(tttttttt) SVC=xx (.UNI) iii...iii
CAL2X372I SETUP REQUEST FROM NODE nnn...nnn
CAL2X374I XTRK RECEIVED UNKNOWN RECTYPE: rrrrrrrr/nnn...nnn
CAL2X400I XTRK SYSTEM ENTERED IN xxx..xxx
CAL2X450I (ttt) TABF EXIT: FUNC=ffff RC=rrrr CC=cccccccc
CAL2X451I (TAB) CKPF CALL: FUNC=ffff RC=rrrr CC=cccccccc


CAL2X452I (tid) CCIF CALL: FUNC=ffff RC=rr CC=cc:
CCI FUNC=f2f2 RC=r2 CC=c2 (r/nnnnnnnn)
CAL2X471I MGR POSTED FOR COMMAND
CAL2X472I (MGR) PERFORMING PING LOOP PROCESS
CAL2X475I (MGR) CCI RECEIVE RTN ENTERED
CAL2X480I (ttt) EVTF EXIT: FUNC=ffff RC=rc CC=cccccccc
CAL2X801E SYNTAX ERROR NEAR LINE llll COLUMN cc CODEx
CAL2X803E PREMATURE EOF, LINE lllll
CAL2X804E ERROR NEAR LINE lllll COLUMN cc: xxx...xxx
CAL2X900W CA-7 XTRK WAITING FOR ENF/CCI TO BECOME ACTIVE.
CAL2X901W CA-7 XTRK WAITING FOR CA-7 CAS9 INITIALIZATION.
CAL2X902E INVALID PARAMETER STARTING WITH (xxx..xxx) - ABORTING
CAL2X903E INVALID TRACE CODE(S) SPECIFIED - ABORTING
CAL2X904E UNABLE TO LOAD MODULE mmm..mmm . RC=rrrr
CAL2X905E XTRK SUB-TASK ENDED PREMATURELY: tttttttt (mmmmmmmm)
TCBCMP=xxxxxxx
CAL2X906E SUBTASK HAS NOT RESPONDED TO TERM CALL: xxx...xxx
CAL2X907E ERROR RETURN FROM ATTACH FOR xxxxxxxx RC=rrrr
CAL2X908E STARTUP OF SUBTASK xxxxxxxx FAILED. COMP=cccccccc
CAL2X909E SUBTASK HAS NOT RESPONDED TO INIT CALL: xxx...xxx
CAL2X910E XTRK ffff OF dddddddd FAILED. RC=rc CC=cc
CAL2X911W XTRK ESTAE ENTERED - WIP=ww (cccc) (pppppppp): ddd........ddd
CAL2X914E INVALID OR MISSING MONITOR NAME - ABORTING
CAL2X915E MISSING OR INVALID XTRK PARM LIST - ABORTING
CAL2X925E XTRK MGR TASK RECEIVED INVALID PARM LIST
CAL2X926E CA-7 CROSS-PLATFORM TRACKER ALREADY ACTIVE ON THIS SYSTEM
CAL2X927E (ttt) sss ERROR FUNC=ffff RC=rr CC=cc TEXT=xxx...xxx
CAL2X928E (tid) ssss ERROR: FUNC=ffff RC=rr CC=cc
CAL2X929E XTRK xxxxxxxxxx FUNCTION ERROR: FUNC=ffff RC=rrrr CC=cccc
CAL2001I CA-7 RIM : CA-7 PRODUCTION SYSTEM INITIALIZATION COMPLETE.
(SSCT=xxxx)
CAL2002I CA-7 RIM : CA-7 TEST SYSTEM INITIALIZATION COMPLETE. (SSCT=xxxx)


CAL2038I CA-7 RIM:USER TABLE RELOAD REINITIALIZATION COMPLETE.
CAXPS148W (CASH_I_0148) SUBMIT FAILURE FROM monitor CODE=xxxxxxxx
(nnnnnnn/mmmmmmm/jjjjjjjj/eeeeeeeeeeeeee)
CAXPS801I PARMLIST FORMAT IS 'TARGET-NODE, TARGET-MONITOR,
START-DATE/TIME (YYYYDDDHHMMSSTH)'
CAXPS802I ALL PARMS ARE OPTIONAL. PARTIAL START DATE/TIME CAN BE SPECIFIED
(E.G. 1999063)
CAXPS803I PARMLIST FORMAT IS 'TARGET-CCI-NODE,TARGET-CCI-APPL-NAME'
CAXPS804I BOTH ARE OPTIONAL. NODE MUST BE SPECIFIC. APPL INTERPRETED AS A
PREFIX
1.2.2 Chapter 2 - CA-7.A through CA-7.X

CA-7.A001 ARF Response job (nnnn) jjjjjjjj Type=cc, Intercept=xxxx at hh:mm:ss.th
CA-7.BSTR BTERM FLAG RESET, MAY NEED TO RESUBMIT
CA-7.CPMA Unable to track flow for XXXXXXXX
FLOW ADD Error for XXXXXXXX RSPLFDBK=YYYYYYYY
FLOW ADD Error for XXXXXXXX ; Already on flow chain
FLOW ADD Error for XXXXXXXX ; Already on CRQ chain
FLOW FFF Error for XXXXXXXX ZZZZZ RC=YYYYYYYY
CA-7.CPMP FFFFFF error -- XXXXXXXX (nnnn) in YYYYYYYY/ZZZZZZZZ (mmmm) yyyy.ddd
hh:mm:ss.th AA/rrrrrrrr
CA-7.CPMT Unable to track XXXXXXXX (nnnn) in YYYYYYYY/ZZZZZZZZ (mmmm) yyyy.ddd
hh:mm:ss.th AA/00000000
CA-7.IARR xxxxx JOBS ON qqqqqqqq QUEUE, yyyyy JOBS USED ARF.
CA-7.IJCK JCLCHECK COMMON COMPONENT INTERFACE LOADED.


CA-7.IOPT CA-DRIVER COMMENT INDICATOR IS: nnnnnnnn
CPM REQUIRES RSRC=Y ON DBASE STMT
CPM REQUIRES AT LEAST ONE CCI DEVICE
CPM ACTIVE
SHOULD CA-7 READ COMMDS EVERY FIVE SECONDS? REPLY TO CONFIRM
(YES/NO)
CA-7 WILL WAKE UP EVERY xxxx SECONDS TO READ THE COMMDS.
CA-7.INWC NO TRX TERMINALS DEFINED, SWITCHING TO ARF=MAINT
CA-7.IVRM-16 NO COREQUISITE RESOURCE RECORD(S) TO BE DELETED.
CA-7.IVRM-30 CPM FLOW CHAIN NOT CREATED
CA-7.IVRM-31 NO CPM FLOW RECORDS TO DELETE.
CA-7.I32V APPLID(aaaaaaa) TERM(ttttttt) LU(lllllll)
CA-7.MA31 CORE TAG CHECK FAILED, R1=XXXXXXXX R6=XXXXXXXX
LENGTH CHECK FAILED, R0=XXXXXXXX R1=XXXXXXXX
R10=XXXXXXXX R11=XXXXXXXX R14=XXXXXXXX
CA-7.NUC ARF INITIALIZATION FAILED
CA-7 JSCB AUTHORIZED
MVS PROGRAM MANAGEMENT USED
CA-7 JSCB NOT AUTHORIZED
UNABLE TO SUPPORT SGETM31/SPUTM31
CA-7.RSC5-01 JOB NOT FOUND IN READY QUEUE
CA-7.RSC5-02 I/O ERROR ON READ OF READY QUEUE
CA-7.R152 CPM FLOW CHAIN CREATED
CA-7.R154 ERROR ON DELETE CPM FLOW RECORD
CA-7.R155 ERROR ON GETUPD CPM FLOW RECORD
CA-7.R156 CPM FLOW RECORDS DELETED
CA-7.SJLV One or more VRM Device Definitions dropped for XXXXXXXX
VRM IO err X FUNC=GETUPD RC=XXXXXXXX REASON=YYYYYYYY
JOB=NNNNNNNN
Unable to update VRM Device Definitions. Length=NNNNNNNN
Maxlen=XXXXXXXX Job=YYYYYYYY
CA-7.SJL0 VRM DEVICE TABLE SPACE EXCEEDED


CA-7.SVCT012I IGCS3XXX SIZE IN BYTES IS xxxxxxxx (HEX)
CA-7.SVCT099I NORMAL TERMINATION FOR THIS JOB IS A U0099 ABEND.
CA-7.TRLR-00 (jobname) PROCESS xxxxxxxx JOBSTEP=stepname,
PROCSTEP=procstep, NODE=nodename, OPT=option
CA-7.V151 s mmmm (dddd) UCC7VSAM INITIALIZATION COMPLETE
CA-7.XTM0 SASSXTM0 initialization in progress
SASSXTM0 initialization complete
CCI Interface initialized.
CCI Interface initialization failed.
RECEIVE error; Data dropped.
Session started (nnnnnnnn) xx-xx
Session ended (nnnnnnnn) xx-xx
Exceeded max num of RPLs.
FFFF note: mm-mm (aabbccdd) nn-nn
1.2.3 Chapter 3 - CA-7.000 through CA-7.999

CA-7.003 Vx.y (gggg) PHASE [(I)|(II)] SHUTDOWN IN PROGRESS AT hh:mm:ss ON yy.ddd
ALL SYSTEM FUNCTIONS COMPLETE
PHASE [(I)|(II)] SHUTDOWN COMPLETE AT hh:mm:ss
CA-7.010 Vx.y (gggg) UNIDENTIFIED COMMAND, PLEASE RE-ENTER
CA-7.022 Vx.y (gggg) LOGON FORMAT INCORRECT AT tttttttt
CA-7.200 BOTH LOG FILES ARE FULL,
DUMP LOG FILES,
THEN REPLY "LOGP" IF PRIMARY WAS DUMPED,
OR REPLY "LOGS" IF SECONDARY WAS DUMPED,
AWAITING REPLY: LOGP, LOGS, OR CANCEL
CA-7.404 SUBTASK xxxxxxxx TERMINATED. TCBCMP = xxyyyzzz
CA-7.560 SASSMA31 - STORAGE NOT AVAILABLE,NO WAIT REQUESTED - U560
SASSMA31 - STORAGE NOT AVAILABLE. ZERO BYTES REQUESTED
CA-7.586 ICOM COUPLING FACILITY MODE = xxxx
CA-7.587 ICOM CF : CURRENT : SMF sssssss TRL ttttttt NCF nnnnnnn
ICOM CF : PROCESSED : SMF sssssss TRL ttttttt NCF nnnnnnn
CA-7.588 INVALID ICOM COUPLING FACILITY PARAMETER


CA-7.589 INVALID ICOM PARM KEYWORD(S).
CA-7.590 XMONITOR= KEYWORD IGNORED: XCKPT DD NOT FOUND/DUMMIED
CA-7.592 XTRK TASK NOT ACTIVE UNDER ICOM
CA-7.688 PARM VALUES INCONSISTENT WITH SYMBOLIC DEFINITION
CA-7.880 TRX INIT ERR CODE xx
CA-7.925 LOG DATASET AREAS INITIALIZED
CA-7.928 LOG DATASET [(CLOSED)|(OPENED)]
CA-7.994 STORAGE POOLS NEED MORE STORAGE.
1.2.4 Chapter 4 - CDSI through RSCx

CDSI-10 UCC7CMDS DD STATEMENT MISSING
CDSI-11 TOO MUCH INPUT DATA
HIS8-18 CONTROL CARD EDIT FINAL RESULTS.
HLP0-00 HELP REQUEST COMPLETED AT hh:mm:ss ON yy.ddd
MNU0-00 SPECIFY DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE.
QMxx-00 ENTER VALUES, TRANSFER OR ENTER A COMMAND ON THE TOP LINE
QMxx-05 INVALID VALUE ENTERED FOR FIELD: xxxxxxxx
QMxx-12 FUNCTION ONLY AVAILABLE ON-LINE
QMxx-13 NO SUCH TASK IN THE QUEUE
QMxx-58 CANNOT HOLD = JOB ALREADY SUBMITTED OR COMPLETE
QM10-00 ENTER FUNCTION (C,F,H,I,O,P, OR R) IN 'F' FIELD OR ENTER A COMMAND ON
THE TOP LINE
QM10-00 nn TRANSACTIONS PROCESSED, nn ERRORS DETECTED
QM10-01 SCRATCH QUEUE ACCESS ERROR, RC=xxxxxxxx
QM10-09 LAST ? SHOWN WAS SECURITY AUTHORIZATION FAILURE
QM2F-01 QUEUE ACCESS OR SORT ERROR: xxxx
QM2F-08 YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB
QM2F-09 YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION


QM20-61 CANNOT CANCEL - JOB HAS ACTIVE ARF
QM20-62 XQ E NOT VALID FOR 7UNI JOBS WITHOUT MIXED CASE SUPPORT
QM20-63 CANNOT CANCEL - ERROR IN ARF PURGE
QM30-00 SET 'F' = 'X' TO POST OR ENTER A COMMAND ON TOP LINE
QM70-10 *** ATTENTION *** JOB=xxxxxxxx (nnnn) HAS BEEN CANCELED
RSCx-00 xxxxxxxx FUNCTION SUCCESSFUL
RSCx-02 JOB NOT FOUND
RSCx-04 NO RESOURCES DEFINED FOR JOB
RSCx-15 DUPLICATE RESOURCE CONNECTED TO JOB
1.2.5 Chapter 5 - SANx through SJR2

SATO-15 JOB xxxxxxxx (nnnn) ENTERED INTO REQUEST 'Q'.
AUTO [(JOB=yyyyyyyy)|(DSNBR=zznnnnnn)]
DUE-OUT ON yy.ddd AT hh:mm.
SCMx-00 xxxxxxxx COMPLETED AT hh:mm:ss ON yy.ddd
SCMx-99 INVALID ERROR CODE
SCMO-02 OPERATOR ID NOT SPECIFIED
SCM0-12 HARDCOPY DEVICE NOT FOUND.
SCM0-17 PROCESSING COMPLETE FOR /SWAP
SCM0-77 /FETCH SERVICE UNAVAILABLE
SCM0-78 NO COMMAND RING ESTABLISHED
SCM0-79 /FETCH STORAGE LIMIT EXCEEDED
SCM2-10 /SHUTDOWN MAY BE ENTERED FROM CA-7 MASTER TERMINAL ONLY
/SHUTDOWN IGNORED
SCM9-13 COMMAND INVALID FOR INTERNAL SECURITY
SCM9-14 RESOURCE NAME IS REQUIRED
SCM9-15 CA-7 RESOURCE TABLE NOT FOUND
SCM9-16 INVALID FORMAT FOR CA-7 RESOURCE TABLE.
SCM9-17 RESOURCE (xxxxxxxx) NOT FOUND IN CA-7 RESOURCE TABLE


SCM9-18 ACCESS TO RESOURCE (xxxxxxxx) DENIED BY EXTERNAL SECURITY
SCM9-21 UID VALUE UPDATED
SCM9-32 UID RESOURCE TABLE REFRESHED
SCM9-33 MODULE NAME REQUIRED FOR REFRESH.
SCM9-34 MODULE XXXXXXXX NOT FOUND FOR REFRESH
SCM9-35 NO STORAGE AVAILABLE FOR RESOURCE TABLE
SCM9-36 UNABLE TO FREE STORAGE DURING REFRESH
SDM0-00 SPECIFY DESIRED OPTION OR ENTER A COMMAND ON THE TOP LINE
SCRJ-12 JOB xxxxxxxx (nnnn) COMPLETED NORMALLY. ***COMPLETED***.
HIGHEST CONDITION CODE=nnnn.
SFCW-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd
SFC1-00 REQUEST COMPLETED AT hh:mm:ss ON yy-ddd
SIRD-11 **** JOB=xxxxxxxx (nnnn) EXECUTION REQUIREMENTS **** JCLID=nnn
SYSTEM=ssssssss DESC=d...d
DUE-OUT yy.ddd/hhmm DEAD-LINE yy.ddd/hhmm
SUBMIT yy.ddd/hhmm MAINID=xxx
SCHID=nnn PROSE#=pppppppp ERQD=nnn ENSAT=nnn IRQD=nnn
INSAT=nnn MCNT=nnn FLAGS=xx/xx/xx/xx/xx/xx/xx
*** REQUIREMENTS ***
*** JOB PROSE ***
SIRD-12 END OF REQUIREMENTS FOR JOB=xxxxxxxx(nnnn).
SJR0-35 BYPGDG= IS NOT VALID
1.2.6 Chapter 6 - SLFA through SPOR

SLIx-00 REQUEST COMPLETED AT hh:mm:ss ON yyddd
SLIx-02 JOB=xxxxxxxx NOT FOUND
[DSN= x....x)|(DSNBR= x...x)] NOT FOUND
NW=xxxxxxxx NOT FOUND
SLIx-05 INVALID 'ST=' OPTION
SLIL-48 CRITICAL PATH MANAGEMENT SUPPORT NOT ACTIVE
SLIL-49 NO FLOW RECORDS CHAINED


SLIL-50 NO FLOW RECORDS SELECTED
SLIL-53 INVALID VALUE FOR xxxxxxx
SLI0-16 INVALID KEYWORD OR DATA IN INPUT
SM20-00 xxxxxxxx SUCCESSFUL [nnn DATASET(S) DELETED]
[,DEFAULTJOB USED FOR DEFAULT VALUES]
[,RESIDUALS PURGED.]
[WARNING: SOME RESIDUAL ELEMENTS COULD NOT BE DELETED.]
SM20-15 ARFSET NOT DEFINED
SM4x-02 NETWORK NOT FOUND
SM50-12 JCL FE NOT VALID FOR 7UNI JOBS WITHOUT MIXED CASE SUPPORT
SM75-00 xxxxxxxx FUNCTION SUCCESSFUL
ENTER INPUT FOR NEXT REQUEST
SM75-14 NO TRIGGERS DEFINED
SM80-00 xxxxxxxx FUNCTION SUCCESSFUL FOR xxxxxxxx
SM85-07 ACCESS TO CALENDAR xxxxxxxx DENIED BY EXTERNAL SECURITY
SM90-18 QJCL FE/FETCH NOT VALID FOR 7UNI JOBS WITHOUT MIXED CASE SUPPORT
SPOA-07 JCL SUBMISSION POSTED [(EXPRESS)]
SPOB-07 CRITICAL PATH MANAGEMENT SUPPORT NOT ACTIVE
SPOB-08 NO FLOW RECORDS SELECTED FOR DELETION
SPOB-09 FLOW RECORD(S) DELETED : nnnn
SPOB-10 VSAM ERROR : FUNC=ff RC=rrrr CC=cccc KEY=kkkkkkkk
SPOE-00 JOB xxxxxxxx (nnnn) ADDED TO [(PRE/Q)|(POST/Q)]
FOR NETWORK= yyyyyyyy, [SUBID= zzzzzzzz]
REQUEST COMPLETED AT hh:mm:ss ON yyddd
SPOF-06 NO ARF QUEUE ELEMENTS FOUND FOR JOB nnnn.
SPOR-39 PRSQA SUCCESSFUL
CO-REQUISITE RESOURCE: resourcename
ACTIVATED
SPOR-40 PRSQD UNSUCCESSFUL
NOT FOUND
ALREADY ACTIVE

1.2.7 Chapter 7 - SPO0 through XTRK

SPO4-04 JOB xxxxxxxx NOT FOUND IN REQ/Q
SPO6-10 *** ATTENTION *** JOB xxxxxxxx (nnnn) HAS BEEN CANCELED
SPO7-00 JOB xxxxxxxx (nnnn) ADDED TO THE REQ/Q BY yyyyyyy
[*** JOB TRIGGERING WILL BE BYPASSED ***]
[*** CA-7 DATABASE UPDATES BYPASSED ***]
[*** NEXT SCHEDULED CYCLE WILL BE SKIPPED ***]
REQUEST COMPLETED AT hh:mm:ss ON yy.ddd.
SRC1-117 (W) ID MULTIPLE SCHEDULES AT LEAST ONE DAY
SRC1-136 JOB|NETWORK nnnnnnnn NOT RESOLVED - CALENDAR SCALyyss DENIED BY
EXTERNAL SECURITY
SRC1-137W SCHEDULE IDS xxx AND yyy ARE BOTH SCHEDULED ON mmm dd
SSM0-30 JOB xxxxxxxx(nnnn) SUBMITTED TO yyyyyyyy SYn (USERID=zzzzzzzz)
SSM0-36 JOB xxxxxxxx (nnnn) NOT SUBMITTED TO yyyyyyyy.
INVALID #J OR #X OVERRIDE CARD
HAS BEEN MOVED BACK TO THE REQUEST 'Q'
XTRE-11 FROM DATE REQUIRED FOR JOB=*
XTRE-12 TO DATE REQUIRED FOR JOB=*
XTRK-01 xxxxxxxx DD NOT OPENED SUCCESSFULLY
XTRK-06 NO CONTROL CARD SPECIFIED
1.2.8 Appendix A - Abend Codes
Abend number
U3319 (X'CF7')

Chapter 2. AR - CA7M
This chapter contains the AR through CA7M messages.
Chapter 2. AR - CA7M 2-1

2.1 AR Messages
AR31-00 –AR31-13
2.1 AR Messages
AR31-00 ENTER INPUT DATA

Explanation: This is the prompt to request input data.
User Response: Self-explanatory.
AR31-00 xxxxxxxx FUNCTION SUCCESSFUL

Explanation: The requested function completed successfully.
User Response: None.
AR31-02 ARFSET NOT FOUND

Explanation: The requested ARFSET was not found.
User Response: Check for correct input. If in error, correct and retry.
AR31-05 INVALID OR OMITTED xxxxxxxx DATA

Explanation: The xxxxxxxx field is required and was not entered, or an invalid value was entered.
User Response: Enter a valid value for the indicated field.
AR31-07 ARFSET ALREADY EXISTS

Explanation: An attempt was made to add an ARFSET, but that ARFSET name already exists.
User Response: Change the ARFSET name to a unique value.
AR31-08 YOU ARE NOT AUTHORIZED TO ACCESS THAT ARFSET

Explanation: An attempt was made to alter or add an ARFSET definition that is not accessible due
to UID security.
User Response: If you need to change an existing ARFSET or to add a new one, contact your
security administrator.
AR31-13 NO SAVE -- DEFINITION COUNT ZERO

Explanation: This message is issued if an attempt is made to save an ARFSET with no condition
definitions. A valid ARFSET contains at least one condition definition.
User Response: Define a valid condition definition and attempt the SAVE again.

2.1 AR Messages
AR31-14 –AR32-07
AR31-14 nnnn ARFIO ERROR R15=xxxx R0=yyyy R1=zzzz

Explanation: An error occurred while trying to update the ARF database. nnnn is the offset in
SASSAR31 where the error was detected. Additional diagnostic information is returned in R15, R0,
and R1. If R15=0010, a duplicate record is indicated.
User Response: Contact your installation's CA-7 specialist. For R15=0010, check the UID security
of the ARFSET being added.
AR31-15 ARFIO INIT FAILED

Explanation: ARF database processing indicated a bad return code.
User Response: Make sure that the RESTART statement in the initialization file uses ARF=YES or
ARF=MAINT.
AR31-16 RECORD NOT FOUND FOR UPDATE

Explanation: An attempt was made to replace an ARFSET definition that is not defined.
AR31-17 RESPONSE ID IS MISSING OR INVALID

Explanation: This message is issued when an ARFSET is added or updated without supplying a
valid RESPONSE ID. This ID is required to log on to a CA-7 internal terminal when responses are
to be executed. The ID must have the authority to execute any of the commands implied in the
recovery sequence.
User Response: Supply a valid RESPONSE ID and attempt the SAVE or REPLACE again.
AR32-00 xxxxxxxx FUNCTION SUCCESSFUL

AR32-02 DEFINITION NOT FOUND

Explanation: The definition associated with the DEFID specified could not be located.
User Response: Supply a valid DEFID and retry the command.
AR32-05 INVALID OR OMITTED DEF INDX DATA

Explanation: The DEFID is a required value when defining an ARF condition. A valid DEFID
was not supplied. This message may also be issued if the number of DEFIDs exceeds the maximum
allowable: 20.
AR32-07 DEFINITION INDEX ALREADY EXISTS

Explanation: The DEFID value supplied is already associated with an existing definition in the set.

2.1 AR Messages
AR32-14 –AR32-17
AR32-14 xxxx(nnnn) INVALID VALUE FOR kkkkkkkk

Explanation: A valid value for the field kkkkkkkk was not supplied. The last four characters of
the name of the module detecting the error are xxxx. The program offset is nnnn. This message is
usually accompanied by a detail message.
User Response: Correct and retry the command.
AR32-17 TOO MANY DEFINITIONS -- MAX IS 20

Explanation: Each ARFSET can only have 20 definition indexes.
User Response: Consolidate DEFIDs, or create a new ARFSET.

2.2 BCLP Messages
BCLP-00 –BCLP-15
2.2 BCLP Messages
BCLP-00 INVALID MSG NUMBER - MSG NO=xx

Explanation: Message number xx was issued by SASSBCLP but was not found in the messages
module SASSBCLM. The program is aborted and no further processing is done.
User Response: Notify Computer Associates Technical Support.
BCLP-10 DATA SET SCRATCHED ON VOL=xxxxxx AT hh:mm:ss ON yy.ddd

Explanation: On a REPLACE, the original data set on volume xxxxxx was scratched at the time
and date indicated. This is a normal information message on a REPLACE.
BCLP-11 DATA SET ALLOCATED ON VOL=xxxxxx AT hh:mm:ss ON yy.ddd

Explanation: A data set has been allocated on volume xxxxxx at the time and date indicated. This
is a normal information message.
BCLP-12 DATA SET ACCESS COMPLETE AT hh:mm:ss ON yy.ddd

Explanation: The data set has been successfully created or modified at the time and date indicated.
This is a normal information message.
BCLP-13 DATA SET CATALOGED ON VOL=xxxxxx AT hh:mm:ss ON yy.ddd

Explanation: The data set has been successfully cataloged or recataloged on volume xxxxxx at the
time and date indicated. This is a normal information message.
BCLP-14 DATA SET RECATALOGED ON VOL=xxxxxx AT hh:mm:ss ON yy.ddd

Explanation: The data set has been recataloged on volume xxxxxx at the time and date indicated.
The data set originally pointed to by the catalog was not scratched.
BCLP-15 TYPE 99 RECORD CREATED AT hh:mm:ss ON yy.ddd

Explanation: A pseudo-SMF record (type 99) was successfully created at the time and date indi-
cated. This is a normal information message.

2.2 BCLP Messages
BCLP-16 –BCLP-21
BCLP-16 DATA SET PROCESSING COMPLETE AT hh:mm:ss ON yy.ddd

Explanation: All required actions for the data set were completed at the time and date indicated.
This is a normal information message.
BCLP-17 BATCH CARD LOAD PROCESSING COMPLETE AT hh:mm:ss ON yy.ddd

Explanation: All requests for data set processing have been completed at the time and date indi-
cated. This is a normal information message.
BCLP-18 DATA SET SKIPPED DUE TO ERROR

Explanation: All processing for the data set was suspended because of the displayed error(s). Any
actions noted as complete stand as noted.
User Response: Correct the error(s) displayed, restore the data set if necessary and rerun the Batch
Card Load Program (BCLP).
BCLP-19 DATA SET SKIPPED DUE TO EXIT REQUEST

Explanation: All processing for the data set was suspended because of a data set skip request by
the user exit routine. Any actions noted as complete stand as noted.
User Response: Correct as noted by the exit program and rerun BCLP.
BCLP-20 INVALID PARM FIELD

Explanation: The parameter field on the EXEC statement is invalid because:
1. The keyword is not EXITPROG or ERROR
or,
2. The operand of EXITPROG is longer than 8 characters.
The program is aborted.
User Response: Correct the parameter field and resubmit the job.
BCLP-21 ERROR CALCULATING TRACKS - RC=xxxx

Explanation: An error was returned from the TRKCALC macro while calculating space required
for the data set. An abend will occur.
User Response: Verify volume requested is a valid DASD device. If not, correct and rerun. If
device is DASD, save the JCL, SYSLOG and SYSUDUMP data. Then contact Computer Associates
Technical Support for assistance.

2.2 BCLP Messages
BCLP-22 –BCLP-33
BCLP-22 DDNAME/VOLSER DON'T MATCH dddddddd/vvvvvv

Explanation: The DDNAME (dddddddd) and VOLSER (vvvvvv) displayed do not match. This is
a warning message only; normal processing continues. Requests for a specific volume will be satis-
fied by inspecting and assigning the volume by VOLSER. If the volume is not specified in the JCL,
the ddname must be U7VOLSER.
User Response: Verify that data sets are created on the desired volumes.
BCLP-23 NO DATA SET CONTROL CARDS

Explanation: No valid data set control statements were found. The job is ended without a dump.
User Response: Correct errors or enter control statements or both.
BCLP-24 INVALID RETURN CODE FROM EXIT

Explanation: The user exit program returned an invalid return code. The Batch Card Load
Program is aborted.
User Response: Correct the exit program and resubmit the job.
BCLP-30 MISSING OR INVALID OPERATOR

Explanation: The control statement operator was either missing or invalid. The data set request is
bypassed.
User Response: Correct control statement and resubmit.
BCLP-31 OUT OF PLACE OPTION CARD

Explanation: An OPTION statement was found but was not the first control statement encountered.
The Batch Card Load Program is aborted.
User Response: Examine, correct and resubmit.
BCLP-32 MISSING CONTROL CARD

Explanation: An EODS control statement was followed by a data statement(s) without an inter-
vening data set control statement. All statements are bypassed until the next valid data set control
statement is found.
User Response: Examine, correct and resubmit the data set request.
BCLP-33 INVALID CONTROL CARD - BLANK

Explanation: A control statement with a valid ID (&UCC7) was found but did not contain an oper-
ator or keyword. All statements are bypassed until the next valid control statement (with operator) is
found.
User Response: Examine, correct and resubmit.

2.2 BCLP Messages
BCLP-34 –BCLP-45
BCLP-34 EXPECTED CONTINUATION NOT RECEIVED

Explanation: A control statement ending with a comma was not followed by another control state-
ment. The data set request is bypassed.
User Response: Correct the error and resubmit the data set request.
BCLP-35 INVALID CONTROL CARD - EXTENDS BEYOND COL 71

Explanation: A control statement was encountered which extended beyond column 71. The data
set request is bypassed.
BCLP-40 INVALID KEYWORD - xxxxxxxx

Explanation: Keyword xxxxxxxx is not a recognizable keyword. An attempt will be made to find
the next valid keyword. The data set request is bypassed.
BCLP-41 KEYWORD INVALID WITH OPERATOR - KW=xxxxxx

Explanation: Keyword xxxxxx is invalid with the operator entered. The remaining keywords are
examined and the data set request is bypassed.
BCLP-42 KEYWORD OPERAND TOO LONG - KW=xxx...

Explanation: The operand of keyword xxx... is longer than the maximum allowed. The remaining
keywords are examined and the data set request is bypassed.
BCLP-43 UNBALANCED PARENTHESIS IN KW=xxx...

Explanation: Keyword xxx... contains an unbalanced parenthesis. The remaining keywords are
BCLP-44 MISSING DSN

Explanation: The DSN keyword, required for all data set requests, is missing. The data set request
is bypassed.
BCLP-45 INVALID DSN - NODE LONGER THAN 8 CHARACTERS

Explanation: An operand of a DSN keyword contains a node longer than 8 characters. The
maximum is 8 characters. The remaining keywords are examined and the data set request is
bypassed.

2.2 BCLP Messages
BCLP-46 –BCLP-52
BCLP-46 ATTEMPT TO CREATE GDG GREATER THAN +1

Explanation: An attempt was made to create a Generation Data Group (GDG) data set with a rela-
tive number greater than +l. The remaining keywords are checked for errors and the data set request
is bypassed.
BCLP-47 CREATE NOT SPECIFIED WITH +1 GDG

Explanation: A data set name indicating a new generation of a GDG was encountered but the
operator was not CREATE. The remaining keywords are examined and the data set request is
bypassed.
BCLP-48 OPERAND OF KEYWORD NOT NUMERIC - KW=xxxxxx

Explanation: The operand of keyword xxxxxx must be numeric, but is not. The remaining
BCLP-49 BLKSIZE NOT DIVISIBLE BY 80

Explanation: The operand of the keyword BLKSIZE is not divisible by 80. The remaining
BCLP-50 SCHID NOT IN THE RANGE 1 TO 255

Explanation: A schedule ID entered was not between 1 and 255. The remaining keywords are
BCLP-51 MAXJOBS NOT IN THE RANGE 1 TO 255

Explanation: The operand of the MAXJOBS keyword is not between 1 and 255. The Batch Card
Load Program is aborted.
BCLP-52 MAXJOBS EXCEEDED

Explanation: The number of jobs entered on the JOBS keyword exceeded the maximum number
allowed. The remaining keywords are examined and the data set request is bypassed.
User Response: Use the MAXJOBS keyword on the OPTION control statement to increase the
maximum number of jobs allowed and resubmit the data set request.

2.2 BCLP Messages
BCLP-53 –BCLP-70
BCLP-53 JOBNAME NOT FOUND ON CA-7 JLIB - JOB=jobname

Explanation: The job name displayed (jobname) was entered in the JOB keyword but was not
found in the Job data set, or the job names entered were not in collating sequence. The remaining
BCLP-54 I/O ERROR ON CA-7 JLIB

Explanation: An I/O error was encountered while accessing UCC7JLIB. The Batch Card Load
Program is aborted.
User Response: Correct the error and resubmit data set requests not processed.
BCLP-55 CAN NOT CATALOG THIS DATA SET

Explanation: An attempt was made to catalog a GDG version which had already been dropped.
The catalog operation is not done. Processing for the data set request continues. Since JCL over-
rides may be required, the type 99 record is not created.
User Response: Check for JCL overrides. POST the requirement as complete.
BCLP-56 OPERAND OF VOL= NOT 6 CHARACTERS

Explanation: The operand of the keyword VOL is shorter or longer than 6 characters. The
remaining keywords are examined and the data set request is bypassed.
BCLP-57 OPERAND OF CVOL= NOT 6 CHARACTERS

Explanation: The operand of the keyword CVOL is shorter or longer than 6 characters. The Batch
Card Load Program is aborted.
User Response: Correct and resubmit the job.
BCLP-58 CVOL POINTS TO VOLUME WITH CA-7 IDS

Explanation: The volume specified in connection with the CVOL keyword specifies the volume
which contains the CA-7 Index Data Set (IDS). The remaining keywords are examined and the data
BCLP-70 ERROR ON SYSTEM CATALOG SEARCH - RC=

Explanation: The displayed return code was received from a LOCATE issued against the Index
data set (IDS). The data set request is bypassed.

2.2 BCLP Messages
BCLP-71 –BCLP-77
BCLP-71 GDG NOT CATALOGED

Explanation: While searching for a GDG in the IDS, it was determined that the data set was not
cataloged. The data set request is bypassed.
User Response: Catalog the GDG and resubmit the data set request.
BCLP-72 ERROR ON SYSTEM CATALOG UPDATE - RC=

Explanation: An attempt to CATALOG or RECATALOG the data set resulted in the return code
displayed. The data set request is bypassed. All actions noted as complete are still effective.
BCLP-73 VOLSER FROM VOL= OR CATALOG IS INVALID

Explanation: An attempt was made to assign a volume serial number either from the VOL keyword
or from the IDS. However, the volume was not represented by a CA-7 DD statement. The data set
request is bypassed.
User Response: Correct the VOLSER or add a DD statement for the volume and resubmit the data
set request.
BCLP-74 ERROR ON CA-7 IDS SEARCH - RC=

Explanation: The return code displayed was received in response to an attempt to LOCATE the
data set in the CA-7 IDS. The data set request is bypassed.
User Response: Correct the problem and resubmit the data set request.
BCLP-75 INVALID CA-7 IDS ENTRY - ID=2 NOT FOUND

Explanation: The CA-7 Index Data Set (IDS) entry was found but did not contain a type 2 entry.
The data set request is bypassed.
User Response: Correct the CA-7 IDS and resubmit the data set request. The data set may need to
be added to the database from the DSN screen.
BCLP-76 UNABLE TO FIND DATA SET ON REPLACE

Explanation: On a request for the replacement of a data set, the data set was not found. The data
BCLP-77 MODDATA DATA SET FOUND ON NON-SPECIFIC REQ

Explanation: On a MODDATA request VOL was omitted and the data set was not cataloged. As a
result the first volume was assigned. However, the data set was found on that volume. All further
processing of this data set is bypassed.

2.2 BCLP Messages
BCLP-78 –BCLP-85
BCLP-78 CREATE SPECIFIED AND DATA SET FOUND ON VOL

Explanation: The operator CREATE was specified but the data set was found on the assigned
volume. The data set request is bypassed.
BCLP-79 REPLACE SPECIFIED AND DATA SET NOT ON VOL

Explanation: The operator REPLACE was specified but the data set was not found on the assigned
volume. The data set request is bypassed.
BCLP-80 DURING VOL ROTATION THE DATA SET WAS FOUND

Explanation: After an initial insufficient space condition was encountered, volume rotation was
initiated. During rotation the data set name was found on a volume. All further processing of the
data set request is bypassed.
BCLP-81 ERROR ON OBTAIN - RC=

Explanation: The return code displayed was encountered after an attempt to OBTAIN the DSCB
for the data set. All further processing of this data set request is bypassed.
User Response: Correct the condition and resubmit the data set request.
BCLP-82 REQUEST DENIED BY SECURITY, ACCESS = xxxxxxxx

Explanation: Data set action requested is not authorized by the security system for the USERID
that Batch Card Load is running under. The access indicated by xxxxxxxx in the message is
rejected. See the JOB statement USER parameter or /*LOGONID or /*JOBFROM statements in the
JCL for the USERID being checked.
User Response: Resubmit the job with a USERID authorized for the desired data set action or
contact your local CA-7 Security Administrator to arrange access for the USERID being checked.
BCLP-83 SECURITY NOT ACTIVE, ACCESS = xxxxxxxx

Explanation: Either no security system is installed or it is not active for some reason. The access
indicated by xxxxxxxx in the message is allowed.
User Response: No action is necessary unless a security system is installed. If a security system is
installed, check to see if it is active. If a security system is active, notify your local CA-7 Security
Administrator to check the installation of the security interface.
BCLP-85 JOB NOT RUN SINCE LAST DATA SET UPDATE - JOB=
Explanation: The job displayed was entered on the JOB keyword and has not run since the last
update of this data set. All further processing of this data set request is bypassed.

2.2 BCLP Messages
BCLP-89 –BCLP-95
BCLP-89 ERROR ON SCRATCH - RC=

Explanation: While scratching the data set, the displayed return code was encountered. All further
processing of this data set request is bypassed.
BCLP-90 BLKSIZE TOO LARGE FOR DEVICE(S)

Explanation: The block size requested is too large for the device assigned, or no volume capable of
containing the block size was found. All further processing of this data set request is bypassed.
User Response: Either decrease the block size requested or add a device capable of containing the
block size. Resubmit the data set request.
BCLP-91 INSUFFICIENT SPACE ON DEVICE(S)

Explanation: For a specific volume request, the device did not have sufficient space to contain the
data set. For a nonspecific volume request or when volume rotation is authorized, no volume was
found which had both sufficient space and could contain the requested block size. All further proc-
essing of the data set request is bypassed.
BCLP-92 ERROR ON CA-7 SVC - RC=

Explanation: The CA-7 SVC used to execute the ALLOCATE SVC returned the code displayed.
All further processing of the data set request is bypassed.
BCLP-93 ERROR ON ALLOCATE - RC=

Explanation: The ALLOCATE SVC returned the code displayed. All further processing of this
data set request is bypassed.
BCLP-94 BLKSIZE MISSING FOR ALLOCATED DSN

Explanation: DSN was being replaced or created but was allocated without a block size.
User Response: Reallocate the data set and specify the block size.
BCLP-95 NCF NOT INSTALLED

Explanation: The NCFNODE keyword was specified in PARM input to BCLP, but NCF is not
installed.
User Response: Remove NCFNODE keyword from PARM input and retry if NCF routing is not
required. If NCF routing is needed, verify the CA-7 NCF installation with your installation's CA-7
specialist or systems programmer.

2.2 BCLP Messages
BCLP-96 –BCLP-97
BCLP-96 UNDEFINED NCF NODE=xxxxxxxx

Explanation: The NCFNODE keyword specified in PARM input to BCLP requested a name not
found in the NCF Node Table. The invalid node is indicated by xxxxxxxx.
User Response: Remove NCFNODE keyword and retry if NCF routing is not required. If NCF
routing is needed, verify the node name specified with your installation's CA-7 specialist or systems
programmer.
BCLP-97 ALLVSAM ERROR ATTEMPTING TO INIT/CONN, RC=xxxx

Explanation: Errors occurred while attempting to initialize, connect, disconnect, or finish with an
ALLVSAM database. RC value gives error code which is further explained by WTO messages.
User Response: Diagnose problem from WTO messages and take appropriate action.

2.3 BK0x Messages
BK00.001 –BK00.006
2.3 BK0x Messages
BK00.001 NO PARMS ENTERED ON EXEC CARD.

Explanation: The Backup/Reload program requires parameters to be supplied on the EXEC state-
ment in the JCL to specify which options are chosen.
User Response: Enter appropriate parameters in JCL and resubmit the job.
BK00.002 ONE OR MORE PARMS INVALID.

Explanation: The parameters specified on the EXEC statement in the JCL had at least one invalid
specification.
User Response: Correct the parameter(s) and resubmit the job.
BK00.003 SPECIFIED EXIT ROUTINE NOT FOUND.

Explanation: The exit routine requested to be called during this execution was not found in the
load library by BLDL. The exit name may have been spelled incorrectly or the library containing the
exit may not be concatenated with the JOBLIB/STEPLIB.
User Response: Check the spelling of the exit program name and correct it if necessary. If the exit
program name is correct, find in which library it exists and supply the appropriate DD statement in
the concatenation.
BK00.004 SVINIT MACRO FAILED.

Explanation: The initialization of the CA-7 Backup/Reload program failed. Programs and parame-
ters required to continue execution could not be initialized.
User Response: Save console listings and logs. Review any preceding messages (CA-7.Vxxx) for
explanation of errors. Contact your installation's CA-7 specialist for assistance.
BK00.005 SVCONN MACRO FAILED.

Explanation: The CA-7 databases could not be CONNected for this Backup/Reload execution.
User Response: Save console listings and logs. Review any preceding messages (CA-7.Vxxx) for
explanation of errors. Contact your installation's CA-7 specialist for assistance.
BK00.006 xxxxxx FAILED FOR DDN=dddddddd

Explanation: A failure occurred on the file indicated by dddddddd. The operation which failed is
identified by xxxxxx.
User Response: Correct the error indicated by xxxxxx and retry. The most likely error is a missing
DD statement.

2.3 BK0x Messages
BK00.008 –BK01.101
BK00.008 LOAD FAILED FOR SASSBK08

Explanation: A load attempt failed for module SASSBK08.
User Response: Verify that SASSBK08 is in an available library. Correct by specifying the library
containing SASSBK08.
BK00.x99 yyyyyy COMPLETED WITH ERRORS NOTED ABOVE

Explanation: The message indicates that the BACKUP or RELOAD operation completed, but some
records were found to be in error as noted by the preceding WTOs.
User Response: Examine the preceding WTO error messages from this run and correct the prob-
lems noted. RELOAD will correct many errors noted during BACKUP. The Database Verification
program should be executed to check for possible related errors, especially if RELOAD indicates
error conditions.
BK01.100 UCC7DLIB POINTS TO EMPTY FILE

Explanation: Backup was requested for a PDS/VSAM or PDS/CVOL database; however, the file
pointed to by UCC7DLIB is empty.
User Response: The database being backed up must be initialized. Verify that UCC7DLIB is
pointing to the correct data set. If it is, initialize the database using SASSCDSI. See the CA-7
Systems Programmer Guide.
BK01.101 SVBACKUP FAILED, RC=xx, REAS=yyyy

Explanation: A failure occurred while putting data to the backup data set.
If RC=8, see REAS codes noted below.
04 - VSVT PARAMETER ABSENT OR INVALID
08 - RECRD PARAMETER ABSENT OR INVALID
12 - KEYAD PARAMETER ABSENT OR INVALID
16 - RECTYP PARAMETER ABSENT OR INVALID (bad data record)
20 - DSTYPE PARAMETER ABSENT OR INVALID
24 - CALLID PARAMETER ABSENT OR INVALID
28 - SVAGNPCB MACRO FAILED ON FIND
32 - SVGETTYP MACRO FAILED
36 - SVGETLEN MACRO FAILED
40 - RECORD SEQUENCE ERROR (previous messages show keys)
44 - SVAGNPCB MACRO FAILED ON ASSIGN
48 - VDVT EYECATCHER NOT 'VDVT'
52 - ILLEGAL DATATYPE CODE
56 - CALLID SPECIFIED NOT USED EXCLUSIVELY FOR BACKUP FUNCTION
User Response: Review the job's log for other error messages which should describe the problem.

2.3 BK0x Messages
BK01.102 –BK02.201
BK01.102 BAD MEMBER ENTRY FOR KEY=kkkkkkkk, DSTYPE=ddd, INVALID BLOCK HAS BEEN
WRITTEN
Explanation: An error was found while processing the member data for the indicated key and data
set. The data was written to the backup file but probably is not usable for reloading.
User Response: Check the indicated key for access using Database Maintenance and listing screens
such as JOB, LJOB, LPROS and DSN. For DSTYPE=JOB, try issuing a LOAD command to CA-7
to rebuild the member. The entry may have to be deleted and added to the database.
BK01.103 POINT FAILED, SKIPPING MEMBER FOR KEY=kkkkkkkk, DSTYPE=ddd

Explanation: The POINT macro failed when accessing the member portion of the indicated key.
The member was not backed up and will not be available for reload.
User Response: Check the indicated member using CA-7 screens such as JOB, DSN, PROSE,
JOBCONN, and so forth. If DSTYPE=JOB, try issuing a LOAD command to CA-7. The entry may
have to be deleted and added to the database.
BK01.105 OPEN FAILED FOR DDN=dddddddd

Explanation: The DD statement indicated could not be opened.
User Response: Verify that the DD statement is present.
BK01.106 NO MEMBER FOUND FOR KEY=kkkkkkkk, DSTYPE=ddd

Explanation: The key had no member data.
User Response: Delete the indicated key. If the entry is required, add it to the database.
BK01.108 BACKUP TERMINATED DUE TO SPOOL ERROR

Explanation: An error was returned from a request to spool directory entries. Preceding messages
describe the problem.
User Response: Check the preceding messages for corrections.
BK02.200 IEHLIST FAILED.

Explanation: This applies to a CVOL type of IDS database only. An IEHLIST operation failed on
this database.
User Response: Check the JCL to ensure that the correct database is specified. Ensure that no
other JCL errors exist (for example, parameters). Save the console listings and logs. Contact your
installation's CA-7 specialist for assistance.
BK02.201 OPEN FAILED FOR DDN=dddddddd, (RC=xx, ERROR=xxxx)

Explanation: The DD statement could not be opened.
If RC=8, see ERROR codes noted below.
136 - insufficient storage (increase region)
148 - no record in catalog (may require STEPCAT)
152 - security failed (needs correct PASSWORD in DBPARMS)

2.3 BK0x Messages
BK02.202 –BK03.302
180 - probably wrong DSN on STEPCAT in JCL

188 - data set not VSAM, cannot use ACB to OPEN
User Response: Verify that the indicated DD statement is in your JCL. If present, check the IBM
messages and above codes, if applicable, for corrective actions. See the IBM VSAM Programmer's
Guide (GC26-3838).
BK02.202 INSUFFICIENT ROOM IN OUTPUT AREA.

Explanation: This applies to a CVOL type of IDS database only. The output area required for this
operation was too small.
User Response: Save console listings and logs. Contact your installation's CA-7 specialist for
assistance.
BK02.203 GET FAILED ON UCC7IDS, RC=xx, FDBK=yyyy, KEY=k...k

Explanation: A GET request failed on UCC7IDS. The RC and FDBK codes can be found in the
IBM VSAM Programmer's Guide (GC26-3838). The key is the last one returned.
User Response: See the IBM manuals for corrective action. See also the message BK03.301 where
REAS codes match FDBK codes.

User Response: See message BK01.101 for RC and REAS values.

BK03.301 SVEXTGET FAILED, RC=xx, REAS=yyyy

Explanation: A failure occurred while getting data from the database.
20 - Control Interval conflict (someone else updating DB)
BK03.302 BAD MEMBER ENTRY FOR KEY=kkkkkkkk, DSTYPE=ddd, INVALID BLOCK HAS BEEN
WRITTEN
set. The data was written to the backup file but probably cannot be used for reloading, since any
remaining records for the member are dropped.

2.3 BK0x Messages
BK04.400 –BK04.403
to rebuild the member. The entry may have to be deleted and added to the database. This can be
caused by using 3.0 or later load libraries against a pre-3.0 database.
BK04.400 DIRECTORY STOW FAILED FOR KEY=kkkkkkkk, DSTYPE=ddd

Explanation: A directory add failed on the data set and key noted. If the problem was due to lack
of directory blocks, the word STOW will be replaced with the word SPACE.
User Response: Check the job's log for IBM messages describing the problem. If SPACE is indi-
cated, change your allocation and rerun the job.
BK04.401 SVRELOAD FAILED, RC=xx, REAS=yyyy

Explanation: A failure occurred while getting data from the backup data set.
00 - VSVT PARAMETER INVALID
04 - KEYAD PARAMETER INVALID
12 - RECTYP PARAMETER INVALID (bad data record)
16 - DSTYPE PARAMETER INVALID
24 - ACCTYP LOAD OR RELOAD NOT CONNECTED
28 - SVAGNPCB FAILED ON FIND
32 - CALLID ALREADY IN USE
36 - KEY SEQUENCE ERROR (previous messages show keys)
40 - VPCB INVALID. VPCBFLG
44 - VDVT DAMAGED OR INVALID
48 - DATATYPE NOT IN VDVT
52 - SASSVZ00 ERROR ON OUTPUT
56 - SVANGPCB FAILED ON ASSIGN
60 - GET MACRO FAILED (IBM messages show error)
64 - VPCB INVALID. VPCBFL7
68 - SASSVZ00 ERROR ON INPUT
72 - SASSV081 ABNORMAL COMP
BK04.402 BAD MEMBER ENTRY FOR KEY=kkkkkkkk, DSTYPE=ddd, INVALID BLOCK DROPPED
set. The data was not loaded to the database.

User Response: Verify that the DD statement indicated is present, then check for other messages in
the job log. Correct any errors identified and retry.

2.3 BK0x Messages
BK04.404 –BK05.501
BK04.404 DSDS ZERO REBUILT FOR RECTYP=rrr

Explanation: A numbering control record (DS0, NW0, and so on) was missing or in error from the
backup file. RELOAD has rebuilt the ZERO record for the RECTYP indicated.
BK04.405 RECORD INVALID, NOT RELOADED

Explanation: The record key identified in immediately preceding messages was invalid. The record
was not reloaded so as to prevent possible abend situations. Generally, the error is a key edit failure
which is probably an Index Data Set entry representing a noncatalogable data set name.
User Response: If you want the record reloaded despite the errors identified in preceding messages,
rerun the RELOAD with the FORCE parameter; that is, OPT=(RELOAD,FORCE).
Note: Some error conditions will not be reloaded in spite of the FORCE parameter. If the keys
reported are needed, they must be added to the system and may require cleanup of invalid
keys.
BK04.406 NO xxxxxxxx FOUND FOR KEY=kkkkkkkk, DSTYPE=ddd

Explanation: Either DIRECTORY or MEMBER data for the noted key was missing from the
backup file.
User Response: Run Database Verification to identify any related database entries requiring cor-
rection.
BK04.408 RELOAD TERMINATED DUE TO SPOOL ERROR

Explanation: An error was returned from a request to spool directory entries. Preceding messages
describe the problem.
User Response: Check the preceding messages for corrections.
BK05.500 CATALOG FUNCTION FAILED.

Explanation: This applies to a CVOL type of IDS database only. An attempt to write to the IDS
database had a fatal error.
assistance.
BK05.501 OPEN FAILED FOR DDN=UCC7IDS, RC=xx, ERROR=yyyy

Explanation: The DD statement noted could not be opened. The RC and ERROR codes are pro-
vided for DDN=UCC7IDS and are VSAM codes found in the IBM VSAM Programmer's Guide
(GC26-3838).
User Response: See message BK02.201 for RC and ERROR values.

2.3 BK0x Messages
BK05.502 –BK06.601
BK05.502 PUT FAILED ON DDN=UCC7IDS, RC=xx, FDBK=yyyy, KEY=k...k

Explanation: A PUT request failed on UCC7IDS. The RC and FDBK codes are found in the IBM
VSAM Programmer's Guide (GC26-3838). The key was the one being output.
User Response: See the IBM manuals for corrective action. See also message BK06.601 where
REAS codes match FDBK codes.

BK05.504 PREMATURE END OF DATA ON RELOAD

Explanation: End of data was reached on the backup file during reload of a PDSVSAM or
PDSCVOL database while processing IDS entries. Since there must be certain other entries for the
Dataset data set, this is an error. No Job data set entries have been loaded.
User Response: Check for other error messages in the job's log and correct any conditions indi-
cated. Try RELOAD again. You may have to RELOAD from an earlier copy of a SASSBK00
backup file.

Explanation: The record key indicated in the immediately preceding messages was invalid. The
record was not reloaded so as to prevent possible abend situations. Generally, the error is a key edit
failure which is probably an Index data set entry representing a noncatalogable data set name.
keys.

BK06.601 SVEXTPUT FAILED, RC=xx, REAS=yyyy

Explanation: A failure occurred while putting data to the database.
20 - Control Interval conflict (someone else updating DB)

2.3 BK0x Messages
BK06.602 –BK08.801
BK06.602 BAD MEMBER ENTRY FOR KEY=kkkkkkkk, DSTYPE=ddd, INVALID BLOCK DROPPED
Explanation: An error was found while processing the member data for the key and data set indi-
cated. The data was not loaded to the database.
BK06.604 DSDS ZERO REBUILT FOR RECTYP=rrrr

Explanation: A numbering control record (DS0, NW0, and so on) was missing or in error from the
backup file. RELOAD has rebuilt the ZERO record for the RECTYP indicated.

Explanation: The record key indicated in the immediately preceding messages was invalid. The
record was not reloaded so as to prevent possible abend situations. Generally, the error is a key edit
failure which is probably an Index Data Set entry representing a noncatalogable data set name.
keys.

User Response: Verify that the DD statement noted is present, then check for other messages in the
job log. Correct any errors identified and retry.
BK08.800 PDSWORK NOT FOUND, CORE SPOOLING USED

Explanation: The DD statement for PDSWORK was not found so spooling of directory entries will
be done in memory rather than on disk.
User Response: None, this is normal and expected.
BK08.801 CANNOT USE TAPE DATA SET FOR PDSWORK

Explanation: The DD statement for PDSWORK was pointing to a tape device. Directory spooling
is only done on disk devices or in memory.
User Response: Change the DD statement to reference temporary disk storage or remove the DD
entirely.

2.3 BK0x Messages
BK08.802 –BK08.807
BK08.802 GETMAIN ERROR, SPOOLING TERMINATED

Explanation: Directory spooling is being done in memory but storage is not available.
User Response: Try specifying a larger region for the job. If a larger region does not resolve the
problem, use disk spooling by including a DD statement for PDSWORK which references temporary
disk.
BK08.803 OPEN FAILED FOR PDSWORK, SPOOLING TERMINATED

Explanation: The PDSWORK file failed to open.
User Response: Check the job's log for error messages explaining the failure. Correct the problem
and retry.
BK08.804 NO DSDS ZERO FOUND FOR RECTYP=rrr

Explanation: A numbering control record (DS0, NW0, and so on) was missing or in error for the
RECTYP noted.
User Response: If this message appears from a BACKUP run, a RELOAD will correct the
problem. Otherwise, no action is required.
BK08.805 INVALID RECORD TYPE, SPOOLING TERMINATED

Explanation: Directory spooling encountered a bad record type.
User Response: If doing a BACKUP, verify that the database is for CA-7 and that it has been
initialized by the SASSCDSI program (install job N030). If doing a RELOAD, verify that the
backup file was created by SASSBK00.
BK08.806 NO xxxxxxxx FOUND FOR KEY=kkkkkkkk, DSTYPE=ddd

Explanation: Either DIRECTORY or MEMBER data for the noted key was missing.
User Response: Run Database Verification to identify any related database entries requiring cor-
rection.
BK08.807 DUPLICATE DIRECTORY DROPPED FOR KEY=kkkkkkkk, DSTYPE=ddd

Explanation: Multiple directory entries with the same key were processed. When this happens, the
first directory is used and subsequent entries are dropped.
User Response: Contact your installation's CA-7 specialist for assistance.

2.4 BSTR Messages
BSTR-00 –BSTR-11
2.4 BSTR Messages
BSTR-00 ***INPUT TO BATCH TERMINAL***

Explanation: The original input is listed as part of the output processing messages from
SASSBSTR. This message indicates the start of the input statements.
BSTR-00 ***END OF INPUT***

Explanation: This message terminates the list of input statements.
BSTR-10 CA-7 IS NOT ACTIVE

Explanation: CA-7 must be active to process the batch terminal input. The control record in the
Communications data set or an operator's reply to a WTOR indicates CA-7 is not active.
User Response: Check the UCC7CMDS DD statement in the Batch Terminal Interface PROC and
CA-7's PROC to be sure that it is correct. If it is, resubmit the Batch Terminal Interface job when
CA-7 is active.
BSTR-11 INVALID PARM FIELD (xxxxxxxxxxxxxxxxxxxx) STARTING AT yyyyyyyyyyyy

Explanation: The PARM value on the SASSBSTR execute statement contains invalid data or incor-
rect syntax. The exact reason for the error is described in the (xxxxxxxxxxxxxxxx) field of the
message. The text of the PARM value is in the yyyyyyyyyyyyyyy field starting at the point where
the error was recognized.
User Response: Correct the PARM value in error and resubmit the Batch Terminal Interface job.
Possible reason messages are in (xxxxxxxxxxxxxxxxx) and the corrective action is one of the
following:
UNKNOWN KEYWORD
The PARM value contains an invalid keyword. The valid
keywords are POOL, DSNPFX, NOMCHK, and NOWAIT.
NON-NUMERIC TERMINAL
Terminal numbers must be numeric.
INVALID TERMINAL
When used in the first position of the PARM field, the terminal number must be between
0 and 8 (zero indicating Dynamic BTI Management). When used as operands of the
POOL= keyword, terminal numbers must be between 1 and 8.
INVALID TERMINAL RANGE
When specifying a range of terminals on the POOL= keyword, the format is POOL=(x-y)
where x and y are terminal numbers. The terminal number for y must be greater than
the terminal number for x.

2.4 BSTR Messages
BSTR-12 –BSTR-16
INVALID TERMINAL LIST

When specifying a list or range of terminals on the POOL= keyword, you must specify
more than one terminal number.
INVALID DSN PREFIX
The data set name prefix on the DSNPFX= keyword is invalid. If the prefix begins with
a quote mark, it must end with a quote mark. The prefix must be 35 characters or less
(not including quotes).
BSTR-12 OPERATOR RESPONDED TO WTOR WITH CANCEL

Explanation: An operator replied CANCEL to a WTOR. Check your SYSOUT for information.
User Response: Determine the condition which caused the WTOR to be issued. Take any neces-
sary corrective action and resubmit the Batch Terminal Interface job.
BSTR-13 SYSIN DD STATEMENT MISSING

Explanation: The SYSIN file was omitted from the Batch Terminal Interface JCL.
User Response: Correct and resubmit the Batch Terminal Interface job.
BSTR-14 BATCHIN DD STATEMENT MISSING

Explanation: The BATCHIN DD statement, which identifies the input data set for the batch ter-
minal, was omitted from the JCL. This message only occurs when Dynamic BTI Management is not
being used.
BSTR-15 BATCHOUT DD STATEMENT MISSING

Explanation: The BATCHOUT DD statement, which identifies the output data set for the batch
terminal, was omitted from the interface JCL.
BSTR-16 CA-7 UNABLE TO START BATCH TERMINAL

Explanation: Any of the following conditions may cause this message:
1. The PARM value on the SASSBSTR execute statement specified a relative batch terminal which
does not exist (for example, PARM=7 was specified but only 4 batch terminals are defined in
CA-7's initialization file).
2. The control record in the Communications data set indicates the specified batch terminal is
already in use. This may be due to an erroneous RESET reply to the CA-7.252 WTOR, or a
/START may have been issued from a CA-7 terminal.
3. No batch terminals are defined to CA-7.
User Response: If the PARM value is invalid, correct and resubmit the Batch Terminal Interface
job. If a RESET reply was inadvertently entered or if a /START was issued, make sure that data
center personnel understand the proper use of these commands. There should be no problem in
rerunning the interface job.

2.4 BSTR Messages
BSTR-17 –BSTR-23
BSTR-17 BATCHOUT OVERFLOWED - OUTPUT TRUNCATED

Explanation: The Batchout data set is not large enough to handle the output for the Batch Terminal
Interface.
User Response: Increase the size of the Batchout data set and try running the interface again.
BSTR-18 ABOVE TRANSACTION IS INVALID FROM BATCH -- BYPASSED

Explanation: A system command such as /COPY was detected and bypassed. If executed, the
command could cause a system abend.
User Response: Remove the command from the SYSIN and resubmit the Batch Terminal Interface
(BTI) job, unless that was the only command in the SYSIN.
BSTR-19 BATCH SUBMIT SECURITY VIOLATION - SKIPPING TO NEXT /LOGON CARD

Explanation: The external security system would not authorize the owner of the BTI job to submit
a logon for operator ID specified on the /LOGON statement listed above this message. Any mes-
sages returned by the external security system will be listed following this message. The batch input
statements following that logon will be skipped until another /LOGON statement is encountered.
The owner of the BTI job is specified implicitly (the user that submits the job) or explicitly through a
USER= job parameter or equivalent.
User Response: Ensure the owner of the BTI job has SUBMIT authority for all operator IDs speci-
fied on /LOGON statements used as batch input.
If you do not want submit security checking for CA-7 batch jobs (BTI, BCLP, and so on,), the
ICMDSECT can be zapped with an option bit to bypass these checks. See the CA-7 Security Guide
for details on implementing this option.
BSTR-20 'SUBMIT' RESOURCE NOT DEFINED TO EXTERNAL SECURITY SYSTEM FUNCTION

ALLOWED
Explanation: An attempt was made to check the authorization for the owner of the BTI job to
submit a logon for the operator ID specified on the /LOGON statement listed above this message.
The external security system responded with a return code 4, indicating SUBMIT is not a defined
resource. The /LOGON statement and the subsequent batch input statements will be processed
normally.
All messages returned by the external security system will be listed following this message.
User Response: If you want CA-7 batch jobs to be controlled by your external security system, the
SUBMIT resource and applicable rules must be defined. See the CA-7 Security Guide for details on
implementation.
BSTR-23 UNABLE TO EXTRACT MODEL DSN FOR DYNAMIC ALLOCATION

Explanation: The DSN prefix extracted from the BATCHIN, BATCHOUT, or Communications
data set is greater than 35 characters.
User Response: Specify the data set name prefix of the BATCHIN/BATCHOUT data sets in the
DSNPFX= keyword on the PARM field of the SASSBSTR step execution statement.

2.4 BSTR Messages
BSTR-24 –BSTR-28
BSTR-24 COMMUNICATIONS DATA SET DD MISSING (UCC7CMDS)

Explanation: The DD statement for the CA-7 Communications data set is missing from the JCL
(DDNAME = UCC7CMDS).
User Response: Supply the proper UCC7CMDS DD statement.
BSTR-25 UNABLE TO ALLOCATE BATCHx#y. RC=cc ERR=eeee INFO=iiii DSN=ddddd...

Explanation: An error was encountered attempting to allocate DSN=ddd..... as DDNAME
BATCHx#y (where x is I or O, and y is the Batch Terminal number). The Dynamic Allocation
return code (RC=), error code (ERR=) and information codes (INFO=) which produced the error are
listed.
User Response: Confirm that the data set name (DSN=) is correct for your batch terminal data sets.
If not, specify the correct data set name prefix in the DSNPFX= keyword in the PARM data on the
SASSBSTR execution statement. If the data set name is correct, contact your installation's CA-7
specialist for assistance.
BSTR-26 UNABLE TO OBTAIN JFCB FOR xxxxxxxx DD.

Explanation: An error was encountered issuing a RDJFCB request for ddname xxxxxxxx.
BSTR-27 UNABLE TO LOCATE BATCH DATA SETS. MODEL DSN = xxxxx...

Explanation: The Dynamic BTI Management facility was unable to locate the BATCHIN data sets
for any of the batch terminals in the pool of available terminal numbers. The model DSN used to
attempt to allocate the BATCHIN data sets is listed in the message.
User Response: Confirm that the model DSN listed in the message has the correct format for your
BATCHIN/BATCHOUT data sets. If so, confirm that these data sets are cataloged and accessible on
the system where the BTI job is being executed. Also, if the POOL= parameter is specified on the
SASSBSTR execution PARM, check to ensure that the terminal numbers specified for the terminal
pool are actually defined to CA-7 and have BATCHIN/BATCHOUT data sets allocated for them.
If the model DSN listed in the message is NOT the correct format, specify the correct data set name
prefix in the DSNPFX= keyword in the PARM data on the SASSBSTR execution statement.
BSTR-28 UNABLE TO OPEN ERRORS DD. MESSAGE TABLE ERRORS WILL NOT BE
REPORTED.
Explanation: The OPEN failed for the ddcard ERRORS.
User Response: The ERRORS ddcard is needed when the SASSXXBT user exit is used. Either
add the ERRORS ddcard, or delete the SASSXXBT module, or use the the NOMCHK parm.

2.5 BTSO Messages
BTSO-10 –BTSO-17
2.5 BTSO Messages
BTSO-10 CA-7 IS NOT ACTIVE

Explanation: CA-7 must be active to process the TSO input. The control record in the Communi-
cations data set indicates it is not active.
User Response: If CA-7 is active, re-enter your data. If problem persists, contact your installation's
CA-7 specialist for assistance.
BTSO-11 INVALID PARM FIELD

Explanation: The PARM data in the CLIST is bad. It must be exactly 8 characters. The first
character must be a number from 1 to 8. The second character must be either S or M.
User Response: Correct the CLIST and retry.
BTSO-13 UCC7IN DD STATEMENT MISSING

BTSO-14 BATCHIN DD STATEMENT MISSING
BTSO-15 BATCHOUT DD STATEMENT MISSING
Explanation: The required DD statement is not allocated in your CLIST.
User Response: Correct the CLIST and retry.
BTSO-16 CA-7 UNABLE TO START BATCH TERMINAL

Explanation: Either of two conditions may cause this message:
1. The PARM value specified a relative batch terminal which does not exist.
2. The control record in the Communications data set indicates the specified batch terminal is
already in use. This may be due to a /START being inadvertently issued from the CA-7 Master
Terminal.
User Response: If the PARM value in the CLIST is invalid, correct and retry. If condition 2
occurred, make sure that the data center personnel understand the proper use of the /START
command. You should be able to retry your command.
BTSO-17 TEMPFILE DD STATEMENT MISSING

Explanation: The required DD statement is not allocated in your CLIST.
User Response: Correct your CLIST and retry.

2.5 BTSO Messages
BTSO-18 –BTSO-19
BTSO-18 BATCH TERMINAL IN USE

Explanation: The requested relative batch terminal is in use.
User Response: Wait a few minutes and try again. If the problem persists, check to see if someone
is entering multiple line input from a terminal. The data should be saved in a sequential data set or
PDS member, and UCC7IN changed to point there for multiple line input.
BTSO-19 BTERM FLAG RESET, CA-7 SHUTDOWN ASSUMED

Explanation: The control record in the Communications data set indicates the batch terminal is no
longer in use. CA-7 may have been shut down immediately after your command.
User Response: If CA-7 has not been shut down, check to see if PGM SASSBEND or SASSICLR
was executed during this time frame. These programs should execute only if CA-7 or SASSBSTR
terminate abnormally (COND=ONLY).

2.6 CACR Messages
CACR500E –CACR507E
2.6 CACR Messages
CACR500E CACM614E DTADD error.

Explanation: The DTADD parameters are invalid.
User Response: Correct the parameters.
CACR501E CA-Driver INITIALIZATION FAILED.

Explanation: An unrecoverable error has occurred during storage allocation in initialization.
CA-Driver terminates.
User Response: Increase the amount of virtual storage allocated to JES task.
CACR503E END OF PROCEDURE BEFORE DATA END.

Explanation: CA-Driver detected an end-of-file condition without a DEND statement during data
inclusion. Error statement issued.
User Response: Make sure DEND statement has been included.
CACR504E IRRECOVERABLE ERROR IN DATA INCLUSION.

Explanation: CA-Driver cannot return to the procedure from which data inclusion has been
invoked. CA-Driver terminates.
User Response: Contact Computer Associates Technical Support.
CACR505E SUBMIT END STATEMENT WITHOUT SUBMIT.

Explanation: A SUBMIT END was detected without a corresponding submit statement. Error
statement issued.
User Response: Resubmit job without the SUBMIT END or include a SUBMIT statement previous
to the SUBMIT END statement.
CACR506E SUBMIT END STATEMENT MISSING.

Explanation: More than one SUBMIT statement detected without corresponding SUBMIT END
statement. Error statement issued.
User Response: Correct the job stream.
CACR507E "varnam" WAS NOT DEFINED IN DPROC STATEMENT.

Explanation: A variable name was detected on an EXEC statement which was not defined in a
DPROC. Error message issued. Variable value not assigned.
User Response: Add a definition for that variable in the DPROC statement for that procedure.

2.6 CACR Messages
CACR508E DATA STATEMENT IS INVALID.

Explanation: A data statement can only be included in a cataloged procedure. Error message
issued.
User Response: Remove DATA statement.
CACR509E NAME IN DATA END DOES NOT MATCH.

Explanation: Data verification facility detects a data name on a DEND statement that does not
match a name on corresponding DATA statement. Error message issued.
User Response: Fix names on DATA and DEND statements.
CACR516E DPROC STATEMENT SYNTAX ERROR.

Explanation: An error occurred while scanning a DPROC statement. Rest of DPROC statement is
ignored.
User Response: Correct error and resubmit job.
CACR518E EXPECTED CONTINUATION DID NOT APPEAR.

Explanation: CA-Driver was expecting a continuation on an EXEC or DPROC statement and none
was found. Error message issued.
User Response: Check if continuation formats are being conformed to. Correct problem and
resubmit job.
CACR519E STATEMENT HAS OVERRUN BOUNDARIES - REMAINDER TRUNCATED.

Explanation: During variable substitution, more space on statement than is available is needed to
expand statement. Statement is truncated; editing continues.
User Response: Check default or assigned value for variables to correct problem.
CACR523E LOOP COUNTER EXCEEDED FOR LABEL LABELNAM.

Explanation: A label was unconditionally branched more times than specified in LCTR statement.
Branch is not taken.
User Response: Increase loop counter.
CACR525E FORMAT ERROR ON LCTR STATEMENT.

Explanation: The operand of a LCTR statement was not positive numeric. Error message issued.
Loop counter not assigned.
User Response: Correct operand of statement. Resubmit job.

2.6 CACR Messages
CACR527E INVALID LABEL NAME ENCOUNTERED ON IF STATEMENT.

INVALID LABEL NAME ENCOUNTERED ON GOTO STATEMENT.
Explanation: The object of branch on an IF or GOTO statement exceeds 8 characters in length.
Error message issued.
User Response: Make sure label names are eight characters or less.
CACR528E IF OR GOTO STATEMENTS NOT VALID EXCEPT IN PROCEDURES.

Explanation: An IF or GOTO statement was detected from reader. Error message issued.
User Response: Remove statement and resubmit job.
CACR529E LABEL MISSING ON IF OR GOTO STATEMENT.

Explanation: An IF or GOTO statement has no object of a branch. Error message issued.
User Response: Supply label for branching on IF or GOTO.
CACR532E LABEL NAME EXCEEDS 8 CHARS - IGNORED.

Explanation: An invalid label name was detected. Label is ignored.
User Response: Correct label name problem and resubmit job.
CACR533E "labelnam" WAS PREVIOUSLY DEFINED - IGNORED.

Explanation: A label name has been doubly defined. Error message issued.
User Response: Correct problem and resubmit job.
CACR535E OVER255 LABELS DEFINED - REST IGNORED.

Explanation: Over 255 label names have been defined in a procedure. Any more specified in that
procedure will be ignored. Remainder of statement labels ignored.
User Response: Reduce the number of labels and resubmit job.
CACR536E ABORT STATEMENT VALID ONLY IN PROCEDURE - IGNORED.

FLUSH STATEMENT VALID ONLY IN PROCEDURE - IGNORED.
Explanation: An ABORT or FLUSH statement was detected from reader. Statement is ignored;
error message issued.
User Response: Remove statement and resubmit job.
CACR537E NEST LIMIT HAS BEEN EXCEEDED.

Explanation: The maximum nest limit specified at generation time has been exceeded. Error
message issued. Any further nesting is suppressed.
User Response: Increase nest limit specified at CA-Driver generation.

2.6 CACR Messages
CACR538E TOO FEW OPERANDS ON IF STATEMENT.

Explanation: An IF statement is missing operands or a valid relational operator. Error message
issued.
User Response: Correct if statement and resubmit job.
CACR539E SECOND OPERAND MUST BE POSITIVE NUMERIC.

Explanation: A conditional statement with a length attribute specified is being tested against a non-
numeric or negative value. Error message issued.
User Response: Correct the statement and resubmit job.
CACR540E FORMAT ERROR ON IF STATEMENT.

Explanation: A syntax error made it impossible for CA-Driver to interpret statement. Error
message issued.
User Response: Check format of statement.
CACR541E INVALID OPERATION FIELD: xxx.

Explanation: An invalid relational operator detected in an IF statement. Error message issued; IF
statement bypassed.
User Response: Correct to a valid relational operator.
CACR543E MIXED DATA TYPES ON IF STATEMENT.

Explanation: A comparison is being made between two different data types. Error message issued.
The IF statement is bypassed.
User Response: Make sure that numeric and alphabetic data are not being compared. Resubmit the
job.
CACR546E NUMBER ATTRIBUTE ONLY VALID FOR ARRAYS.

Explanation: The number attribute was requested for a nonarray variable. Error message issued.
User Response: Correct the statement and resubmit the job.
CACR549E UNPAIRED DELIMITERS IN LITERAL EXPRESSION.

Explanation: A character expression was being defined and the second delimiter was not detected
by CA-Driver. Skips to next valid expression; expansion continues.
User Response: Correct statement and resubmit job.
CACR553E PARM NAME LENGTH ERROR - NAME="varname".

Explanation: A variable name "varname" with over seven characters was detected. Error message
issued; name truncated.

2.6 CACR Messages
CACR554E xxxxxxx IS NOT NUMERIC.

Explanation: The specified field was expected to contain numeric data and did not. Error message
issued.
User Response: Check format of statement. Correct error and resubmit job.
CACR555E UNPAIRED PARENTHESES IN VARIABLE EXPRESSION.

Explanation: A substring or array reference has not been closed with a right parenthesis. Error
message issued. Skip to next valid expression.
CACR556E NON-NUMERIC DISPLACEMENT IN SUBFIELD REFERENCE.

Explanation: A subfield reference displacement has non-numeric data. Error message issued. Skip
to next valid expression.
User Response: Check subfield reference and correct.
CACR557E NON-NUMERIC LENGTH IN SUBFIELD REFERENCE.

Explanation: A subfield length reference has non-numeric data. Error message issued. Skip to
next valid expression.
User Response: Check subfield reference and correct.
CACR558E INVALID DISPLACEMENT IN SUBFIELD REFERENCE.

Explanation: Displacement of subfield exceeds the maximum length of a literal. Error message
issued.
User Response: Check value assigned to variable. Correct statement and resubmit job.
CACR559E INVALID LENGTH IN SUBFIELD REFERENCE.

Explanation: Length of subfield exceeds maximum length of a literal. Error message issued.
CACR560E INVALID SUBFIELD REFERENCE IN EXPRESSION.

Explanation: Subfield reference is outside the range of the value assigned to the variable. Error
message issued.
CACR561E NON-NUMERIC SUBSCRIPT VALUE.

Explanation: A non-numeric subscript was detected. Error message issued.
User Response: Correct subscript and resubmit job.

2.6 CACR Messages
CACR562E SUBSCRIPT OUT OF RANGE - 1 ASSUMED.

Explanation: A subscript was specified which is greater than which was defined in DPROC state-
ment. Error message issued.
User Response: Check DPROC statement and refer to array which has been previously defined.
CACR563E ARRAY ENTRY REFERENCED IS UNDEFINED.

Explanation: An array member was referenced which has no assigned or default value. Error
message issued. Value not substituted.
User Response: Check EXEC statement which is used to expand procedure. Make sure entry has
an assigned value previous to reference.
CACR564E VARIABLE NOT ARRAY ELEMENT - SUBSCRIPT IGNORED.

Explanation: A subscript was used to refer to a variable which is not defined as an array. Error
message issued.
User Response: Check definition of variable in DPROC statement. Correct statement and resubmit
job.
CACR565E "varnam" HAS NO VALUE CLAUSE - VARIABLE NOT DEFINED.

Explanation: A variable without a value clause was detected on an EXEC statement. Error
message issued.
CACR566E "varname HAS NO ASSIGNED OR DEFAULT VALUE.

Explanation: A variable was referenced which has no assigned or default value. Error message
issued.
CACR567E ZERO LENGTH CHARACTER STRING - IGNORED.

Explanation: Two commas in a row were detected by parser. Error message issued.
User Response: Correct error and resubmit job.
CACR568E UNBALANCED DELIMITERS - IGNORED.

Explanation: A character expression definition is not closed with a corresponding delimiter. Error
message issued.
CACR569E MORE THAN 64 VARIABLES GIVEN - NO MORE ACCEPTED.

Explanation: A DPROC statement has definitions for more than 64 variables. Error message
issued; further definitions bypassed.
User Response: Correct DPROC statement and recatalog procedure.

2.6 CACR Messages
CACR570E NUMBER OF ARRAY VALUES EXCEED ARRAY DIM - NO MORE ACCEPTED.

Explanation: More values than there are array members have been entered on a DPROC statement.
CACR571E COMMA MUST SEPARATE ARRAY VALUES.

Explanation: An invalid delimiter was detected in an array definition in a DPROC or EXEC state-
ment. Error message issued.
CACR572E RIGHT PARENTHESIS DOES NOT CLOSE DIMENSION SPECIFICATION.

Explanation: An array dimension is not enclosed in parentheses. Error message issued.
User Response: Correct dimension specification and recatalog procedure.
CACR573E ARRAY DIMENSION IS GREATER THAN 64.

Explanation: An array was defined with greater than 64 members. Error message issued; variable
not defined.
CACR574E "varnam" IS NOT ALPHANUMERIC.

Explanation: A variable name containing nonalphanumeric characters was detected. Error message
issued; variable bypassed.
User Response: Correct variable name and recatalog procedure.
CACR575E ARRAY DIMENSION IS INVALID OR GIVEN AS ZERO.

Explanation: A non-numeric or zero dimension was detected in an array definition on DPROC
statement. Error message issued; variable not defined.
User Response: Correct dimension and recatalog procedure.
CACR576E "varnam" IS NOT AN ARRAY VARIABLE.

Explanation: An array definition was used to assign values to a nonarray variable. Error message
issued; value not assigned.
CACR577E "varnam" HAS BEEN PREVIOUSLY DEFINED - IGNORED.

Explanation: A variable has been defined twice on a DPROC statement. Error message issued;
second definition ignored.

2.6 CACR Messages
CACR578E "varnam" WAS NOT PREVIOUSLY DEFINED - IGNORED.

Explanation: A variable is referred to in an EXEC statement which was not previously defined in a
DPROC. Error message issued.
User Response: Correct procedure and resubmit job.
CACR579E PARM VALUE LENGTH EXCEEDS 64 - TRUNCATED.

Explanation: The value clause in an EXEC or DPROC statement exceeds 64 characters in length.
Error message issued; value truncated.
CACR580E SYNTAX ERROR DETECTED IN SCAN.

Explanation: The EXEC or DPROC statement does not adhere to syntax rules for those statements.
CACR581E SUBFIELDS IN ARRAY DEF NOT TERMINATED.

Explanation: An array definition is not terminated with a closing parenthesis. Error message
issued; variable not defined.
User Response: Check array definition. Correct statement and recatalog procedure.
CACR582E BAD EXEC FIELD: xxxxxxxxxxxxxxx.

Explanation: An unidentifiable string has been detected in scanning an EXEC statement. Error
message issued. Skip to next valid field.
CACR583E FIRST CHAR OF PARM MUST BE ALPHABETIC.

Explanation: A variable name with a numeric first character detected. Error message issued; vari-
able not defined.
User Response: Change variable name to conform to coding rules.
CACR584E SET STATEMENT FORMAT ERROR.

Explanation: A syntax error was detected in scanning a SET statement. Error message issued;
statement ignored.
CACR585E DIVISION BY ZERO IN SET.

Explanation: An attempt was made to divide by zero in a set expression. Error message issued;
value not SET.
User Response: Make sure divisor is a nonzero number or literal.

2.6 CACR Messages
CACR586E RESULT OF MATHEMATICAL EXPRESSION INVALID.

Explanation: A result of over 65535 or less than -65535 was the result of a numeric expression.
Error message issued; value not assigned.
CACR587E &varnam IS A RESERVED VARIABLE.

Explanation: A reserved variable (&DATE, &TIME, and so forth) was used for a variable name in
an EXEC or DPROC statement. Error message issued.
User Response: Change variable name and resubmit job.
CACR588E NESTED PROC="procnam",NOT FOUND.

Explanation: The requested "procnam" was not found in the CA-Driver procedure library. Error
message issued.
User Response: Catalog the requested procedure.
CACR589E VALID TYPE ATTRIBUTES ARE C,N,M, AND O.

Explanation: A type attribute test in an IF statement was invalid. The valid attribute types are C,
N, M, and O.
User Response: Fix the attribute test and resubmit.
CACR590E LABEL "label" IS NOT DEFINED.

Explanation: A GOTO or IF statement detected a branch to a label not defined in that procedure.
User Response: Make sure label is defined in procedure.
CACR591E NO LABEL SPECIFIED IN STEP STATEMENT.

Explanation: A step statement was found without a label identifier. Error message issued.
User Response: Place STEP label in position 3 of STEP statement.
CACR999E CA-Driver/OS ABNORMAL TERMINATION

Explanation: CA-Driver has abended. CA-Driver is deactivated.
User Response: Contact your local Computer Associates representative with the details of the
problem.

2.7 CAL Messages
CAL2A001E –CAL2A011E
2.7 CAL Messages
CAL2A001E CA-7 Session Not initialized. CA-7 signon failed.

Explanation: The CA-7 API interface was unable to establish an online session with CA-7. The
API attempted to sign on to CA-7 with the current user ID, but the signon was rejected.
User Response: Ensure your TSO user ID is defined as a valid user ID to CA-7.
CAL2A002E CA-7 Session Not initialized. VTAM connection failed.

Explanation: The CA-7 API interface was unable to establish an online session with CA-7. The
API attempted to establish a VTAM interface with CA-7 but was unable to do so.
User Response: Ensure the CA7APPL= parameter in member CACCENV of your
'userid.VPOINT.PROFILE' specifies the correct VTAM applid of the CA-7 with which you wish to
communicate. Also, ensure the CA7SESS= parameter specifies a valid ACB name and that the
ACBs are active. Check the system log messages for WTOs issued for your TSO address space
which may contain additional diagnostic information. See the Diagnostics section of the CA-7
Getting Started guide for additional information.
CAL2A003E CA-7 Session Not initialized. Unknown init failure.

Explanation: The CA-7 API interface was unable to establish an online session with CA-7.
User Response: Check the system log messages for WTOs issued for your TSO address space
which may contain additional diagnostic information. See the Diagnostics section of the CA-7
Getting Started guide for additional information.
CAL2A004I Please re-issue request. CA-7 session reconnected.

Explanation: The API interface with CA-7 was lost (probably because of a timeout condition).
The API has reestablished the connection.
User Response: Reissue the request which caused the message. The new request should be proc-
essed normally.
CAL2A009E API Data validation error. Unable to process request.

Explanation: The CA-7 API interface was unable to properly interpret the information passed from
the CA-7 Address Space. The current request has not been satisfied.
User Response: Contact Computer Associates Technical Support. Please be prepared to describe
the exact sequence of events which led up to the above message.
CAL2A011E DSNBR not allowed for add function.

Explanation: You are not allowed to specify a DSNBR when adding a data set. The DSNBR will
be assigned by CA-7 when a successful add is completed.
User Response: Ensure the DSNBR field is empty when attempting an ADD function.

2.7 CAL Messages
CAL2A012E Jobname or CA-7 Job number required.

Explanation: Restart request was made without specifying either the job name or CA-7 job number.
User Response: Ensure that the job name or CA-7 job number (or both) are specified when
requesting a restart.
CAL2A013E Specify either jobname or job number.

Explanation: An Add Requirement request was made without specifying either a job name or CA-7
job number.
User Response: Ensure that the job name or CA-7 job number (or both) are specified when making
the request.
CAL2A014E Specify either dependent job or user requirement.

Explanation: An Add Requirement request was made without specifying either the dependent
jobname, or user requirement to be added.
User Response: Ensure that the dependent job name or user requirement is specified when making
the request.
CAL2A015E Action is required (ADD or SUB).

Explanation: An Adjust Schedule request was made without specifying whether to add to or sub-
tract from the due-out times for jobs/networks.
User Response: Specify either ADD (to add time to schedules) or SUB (to subtract times from
schedules) when making the request.
CAL2A016E Adjustment time is required.

Explanation: An Adjust Schedule request was made without specifying the number of minutes to
be added/subtracted from due-out times.
User Response: Specify the number of minutes to be used to adjust due-out times when making the
request.
CAL2A017E Specify either job criteria or network reference number.

Explanation: An Adjust Schedule request was made specifying both a CA-7 job number and a
network reference number.
User Response: Specify only the CA-7 job number (or ALL or ALLP) or the network reference
number when making the request. If you wish to effect both, issue them as two separate requests.
CAL2A018E Either Job, or, Reference number must be specified.

Explanation: An Adjust Schedule request was made without specifying either a CA-7 job number
or a network reference number.
User Response: Specify the CA-7 job number (or ALL or ALLP), or the network reference number
when making the request.

2.7 CAL Messages
CAL2A019E Only one criteria can be specified at a time.

Explanation: A Hold Queues request was made with multiple selection criteria.
User Response: Specify only one of the selection criteria (job name, CA-7 job number, queue, or
network reference number) when making the request.
CAL2A020E No criteria supplied. No action taken.

Explanation: A Hold Queues request was made without specifying any selection criteria.
User Response: Specify one of the selection criteria (job name, CA-7 job number, queue, or
network reference number) when making the request.
CAL2A021E Invalid Queue type. Must be omitted or REQ, RDY or ACT.

Explanation: A List Queue(s) request was made specifying an invalid queue type.
User Response: Leave the queue type blank (defaults to all queues) or specify REQ, RDY, or ACT
when making the request.
CAL2A022E Specified requirement not found.

Explanation: A request was made to post or unpost a job predecessor (requirement); however, the
specified predecessor could not be found.
User Response: One possible reason is that when the last requirement for a job is posted, you can
no longer list the predecessors. Reissue the VIEW command to reselect the job predecessors to
confirm whether there are still any outstanding predecessors. If there are, but they cannot be posted,
contact Computer Associates Technical Support for assistance.
CAL2A023E Target task not found. Unable to process.

Explanation: A request was made to update an input or output network task in the preprocess or
postprocess queue; however, the specified network task could not be found.
User Response: One possible reason is that the task has already been satisfied. Reissue the VIEW
command to reselect the network tasks to confirm whether the task is still active. If it is, but it
cannot be updated, contact Computer Associates Technical Support for assistance.
CAL2A024E Missing or invalid action. Should be PRMP or NOPRMP.

Explanation: A request was made from the Queue Prompting Control panel; however, the action
code was missing or invalid.
User Response: This window can either initiate prompting (action=PRMP) or suspend prompting
(action=NOPRMP). Specify the desired action and reissue the request.
CAL2A025E Specify either Job, or, Reference criteria.

Explanation: A request was made from the Queue Prompting Control panel; however, both job
number and network reference numbers were specified.
User Response: For a single request only one of these criteria may be specified. Reissue the
request specifying only one target (job number or network reference number).

2.7 CAL Messages
CAL2A026E Neither Job nor Reference criteria specified.

Explanation: A request was made from the Queue Prompting Control panel; however, neither a job
number or a network reference number was specified.
request specifying only one target (either job number or network reference number).
CAL2A027E Only one criteria can be specified at a time.

Explanation: A request was made from the Release Queues panel; however, multiple selection cri-
teria were specified.
request specifying only one target (job name, job number, queue type, or network reference number).
CAL2A028E No criteria supplied. No action taken.

Explanation: A request was made from the Release Queues panel; however, no selection criteria
was specified.
User Response: Reissue the request specifying target criteria (job name, job number, queue type, or
network reference number).
CAL2A029E Invalid or missing action. Must be START or STOP.

Explanation: A request was made from the Queue Control panel; however, the action code was
missing or invalid.
User Response: This window is used to start (action=START) or stop (action=STOP) the queues.
Specify the desired action and reissue the request.
CAL2A030E Invalid queue type. Must be ALL, REQ or RDY.

Explanation: A request was made from the Queue Control panel; however, the queue type was
missing or invalid.
User Response: You may start/stop all of the queues (ALL), or only the Request queue (REQ) or
only the Ready queue (RDY). Specify the desired queue(s) and reissue the request.
CAL2A031E API function error. IFUNC not VIEW or UPD.

Explanation: Internal error in the communication between the ViewPoint system and the CA-7/API
interface.
User Response: Contact Computer Associates Technical Support for assistance.
CAL2A032E Editor commands not allowed in command window.

Explanation: A CA-7 editor command was entered in the CA-7 Command window.
User Response: Editor commands are not allowed in the CA-7 Command window. Use native
CA-7 or the CA-7/ISPF interface to perform these functions.

2.7 CAL Messages
CAL2A033E Job has no JCL attached.

Explanation: The CA-7 Restart window was entered for a job which has no JCL.
User Response: Jobs without JCL cannot be submitted for restart.
CAL2A034I Job does not have a defined schedule.

Explanation: A View function was performed to list the schedules for a job which has no schedules
defined.
User Response: If you wish to define a schedule for the job, enter the job name and perform an
add function (edit/add).
CAL2A035I Schedule ID added.

Explanation: The schedule ID entered has been added for the specified job.
User Response: No action necessary.
CAL2A036E SCAL value MUST be supplied.

Explanation: An attempt was made to add a job schedule without supplying a calendar (SCAL).
User Response: Specify the last two characters of the desired calendar to be used for this schedule.
See the CA-7 Database Maintenance Guide for additional information on calendars.
CAL2A037I Schedule ID updated.

Explanation: The schedule ID has been updated for the specified job.
CAL2A038I Last schedule ID for this job deleted.

Explanation: The schedule ID just deleted was the last one defined for this job.
CAL2A039I Schedule ID deleted.

Explanation: The schedule ID has been deleted as requested.
CAL2A040E Network does not have a defined schedule.

Explanation: A View function was performed to list the schedules for an input network which has
no schedules defined.
User Response: If you wish to define a schedule for the job, enter the network name and perform
an add function (edit/add).

2.7 CAL Messages
CAL2A041E Network not defined as Input Network.

Explanation: A View function was performed to list the schedules for a network which is not
defined as an input network.
User Response: Use the Output Network Scheduling window (PL2DB23) to maintain schedules for
output networks.

Explanation: The schedule ID has been deleted for the specified network.

Explanation: The schedule ID has been added for the specified network.
CAL2A044E SCAL value must be supplied.

Explanation: An attempt was made to add a network schedule without supplying a calendar
(SCAL).

Explanation: The schedule ID has been updated for the specified network.
CAL2A046I Last schedule id for this network deleted.

Explanation: The schedule ID just deleted was the last one defined for this network.
CAL2A047E Network does not have a defined schedule.

Explanation: A View function was performed to list the schedules for an input network which has
no schedules defined.
User Response: If you wish to define a schedule for the job, enter the network name and perform
an add function (edit/add).
CAL2A048E Network not defined as Output Network.

Explanation: A View function was performed to list the schedules for a network which is not
defined as an output network.
User Response: Use the Input Network Scheduling window (PL2DB22) to maintain schedules for
input networks.

2.7 CAL Messages
CAL2A049I –CAL2A056W

Explanation: The schedule ID has been added for the specified network.
CAL2A050E SCAL value must be supplied.

Explanation: An attempt was made to add a network schedule without supplying a calendar
(SCAL).

Explanation: The schedule ID has been updated for the specified network.
CAL2A052I Last schedule id for this network deleted.

Explanation: The schedule ID just deleted was the last one defined for this network.

Explanation: The schedule ID has been deleted for the specified network.
CAL2A054I Verify transaction successful.

Explanation: The VERIFY transaction was completed without error.
CAL2A055I JCLOVRD transaction successful.

Explanation: The JCL Override (JCLOVRD) transaction was completed without error.
CAL2A056W Specified job is not found in expected queue.

Explanation: The job selected for action from the PL2QM1 panel was not found in the selected
CA-7 Queue. The job has probably moved to another queue. The requested action was not
attempted.
User Response: Return to the PL2QM1 panel and reissue the view request to determine if this job
has changed queues. If you still wish to perform an action on it, select it to transfer to the
PL2QM1B panel and reissue the action request.

2.7 CAL Messages
CAL2A057E Unidentified internal function. No action taken.

Explanation: Internal error. Function code passed to the CA-7/API system was not recognized by
the API table processing module.
User Response: Please contact Computer Associates Technical Support for assistance.
CAL2A058W Verify and Hold requirements cannot be unposted.

Explanation: Once a VERIFY or HOLD requirement has been posted, it cannot be unposted.
CAL2A059I Job has no unsatisfied predecessors.

Explanation: Request was issued with List ALL? = N (no). The job was found in the request
queue but there were no outstanding job predecessors.
CAL2A060E CA-7 Job Number is required for CANCEL.

Explanation: A Cancel request was issued from the PL2QM1C panel without a CA-7 Job Number.
The Job Number is required for cancel.
User Response: Reissue the request with the correct CA-7 Job Number for the job to be canceled.
CAL2A061E Calendar Year and Calendar ID are required.

Explanation: A request to delete a CA-7 base calendar was issued without specifying both the year
and ID of the calendar.
User Response: Reissue the request with both the year and ID of the Calendar to be deleted.
CAL2A062E Calendar ID is required.

Explanation: A request to act on a CA-7 base calendar was issued without specifying the name of
the calendar.
User Response: Reissue the request with the name of the calendar to be acted upon.
CAL2A063E Jobtype is required.

Explanation: A request was made to act upon a job or network; however, the type was not speci-
fied.
User Response: Reissue the request with the correct job type (CPU, PRECPU, or POSTCPU).
CAL2A064E Jobtype is invalid.

Explanation: A request was made to act upon a job or network; however, the jobtype specified is
invalid.
User Response: Reissue the request with the correct job type (CPU, PRECPU, or POSTCPU).

2.7 CAL Messages
CAL2A065E –CAL2A072W
CAL2A065E Your level of CA-7 does not support new calendar structure.
Explanation: A request was made to act upon a CA-7 base calendar; however, your level of CA-7
does not support the new calendar update features.
User Response: Confirm you are connected to the correct copy of CA-7. If so, contact Computer
Associates Technical Support for assistance.
CAL2A067E SYSTEM is required.

Explanation: A request was made from the PL2DB46 panel (System documentation); however, no
CA-7 System name was specified.
User Response: Reissue the request with the CA-7 System name whose Prose you wish to edit.
CAL2A068E Prose member not found.

Explanation: A request was made for CA-7 Prose; however, the requested documentation was not
found in the CA-7 database.
User Response: Confirm you are specifying the correct information for the type of Prose you wish
to access. If the Prose is not defined, you may create it by using the Edit/Edit function.
CAL2A069E Member and JCLID are required for Delete.

Explanation: A request was made from the PL2DB7 panel to delete a job's JCL; however, the
JCLID for the JCL was not specified.
User Response: Reissue the request with the correct JCLID for the PDS which holds the job's JCL.
CAL2A070E Resource name missing or invalid.

Explanation: A request was made from one of the CA-7 Virtual Resource Management panels;
however, the resource name was either not specified, or was invalid.
User Response: Reissue the request with the correct VRM resource name.
CAL2A071W JCLID is required to create new members.

Explanation: A request was made from the PL2DB7 panel to create a new JCL member; however,
the JCLID for the JCL was not specified.
User Response: Reissue the request with the correct JCLID for the PDS which will hold the new
member.
CAL2A072W Duplicate Jobnames in the queue. No action taken.

Explanation: A request was received to action a job in the CA-7 queues. A jobname was speci-
fied, but no CA-7 job number. There are multiple occurrences of the same jobname in the queue.
No action was taken since the request is ambiguous.
User Response: Use another path where you can select the exact job (with job number) that you
wish to update.

2.7 CAL Messages
CAL2A073W –CAL2A079E
CAL2A073W Duplicate Jobnames in the queue. No actions available.

Explanation: Control was transferred to the PL2QM1B panel with a job name, but no CA-7 job
number. There are multiple occurrences of that job name in the same CA-7 queue.
User Response: Requests to act upon that job on the PL2QM1B panel will be ignored. Use
another path to PL2QM1B where you can select the exact job you wish to update.
CAL2A074E CA-7 Job Number required for this function.

Explanation: A request was made on the PL2QM1B to update a job, but the job number was not
specified.
User Response: Requests to act upon that job on the PL2QM1B panel will be ignored. Use
another path to PL2QM1B where you can select the exact job you wish to update.
CAL2A075I Edit session has been canceled.

Explanation: A CA-7 API Edit session has been canceled without updating the original text. This
message is normal if no changes are made to the text, or, the user explicitly chooses to cancel
changes made during the edit session.
User Response: If you intended to save the changes, ensure you are saving the data before leaving
the text-edit session. Also ensure that you select the 'OK' option when prompted for save confirma-
tion.
CAL2A076E JOBNAME is required.

Explanation: A request was made for Job Prose, but the job name was not specified on the request.
User Response: Reissue the request providing the proper job name.
CAL2A077E NETWORK is required.

Explanation: A request was made for Network Prose, but the network was not specified on the
request.
User Response: Reissue the request providing the proper network.
CAL2A078E USERNAME is required.

Explanation: A request was made for User Prose, but the user identifier was not specified on the
request.
User Response: Reissue the request providing the proper user identifier.
CAL2A079E DSN is required.

Explanation: A request was made for Data Set Prose, but the data set name was not specified on
the request.
User Response: Reissue the request providing the proper data set name.

2.7 CAL Messages
CAL2A080E JOBNAME, STEPNAME and DDNAME are required.

Explanation: A request was made for ddname Prose, but the job, step and/or ddname were not
specified on the request.
User Response: Reissue the request providing all of the required columns.
CAL2A081E JOBNAME is required.

Explanation: A request was made to act on a job definition in the CA-7 database. The job name
was not specified on the request.
User Response: Reissue the request providing the job name.
CAL2A082I Submit Time has been turned off.

Explanation: A request was made to satisfy a Submit Time requirement for a job in the CA-7
request queue. Any outstanding Submit Time requirement for the job has been satisfied.
User Response: No action required.
CAL2A083E Your level of CA-7 does not support this feature.

Explanation: A request was made to a CA-7/API table for information or services which require a
higher version of CA-7 than what you are currently executing.
User Response: If you have multiple copies of CA-7, confirm that you have connected with the
correct copy. If so, then you will need to upgrade to the current version of CA-7 to use the services
you have requested.
CAL2A084E SAVE FAILED FOR xxxxxxxx : INVALID OR OMITTED JCLLIB DATA

Explanation: An invalid value was entered for JCLLIB.
User Response: Enter a valid JCLLIB value. Use /DISPLAY, ST=JCLVAR to find possible
values.
CAL2A085E NAME OR JOBSET NAME OR MASK REQUIRED.

Explanation: A request was made for a list of CA-7 jobs for Jobflow. However, no JOBSET
(CA-7 system name) or JOBNAME argument was supplied.
User Response: Specify a search argument for JOBNAME, JOBSET or both.
CAL2A086E Too much data for single call. Please qualify request.
Explanation: A request was made to a CA-7/API table which caused an overflow condition in the
CA-7 output. No data is returned to the caller.
User Response: Reissue the request with more specific search criteria.

2.7 CAL Messages
CAL2A088E FLOW ID REQUIRED FOR DELETE

Explanation: Internal error. A call was made to the CA-7/API to delete a JOBFLOW from the
API structure. However, a flow-ID was not sent with the request.
CAL2A089E ID/NAME/SCHID/DUPID REQUIRED FOR DELETE

Explanation: Internal error. A call was made to the CA-7/API to delete a JOBFLOW element
from the API structure. However, all of the information needed to identify the element was not sent
with the request.
CAL2A090E INVALID PR_VIEW TYPE

Explanation: Internal error. A call was made to the CA-7/API to build/update a JOBFLOW in the
API structure. However, the JOBFLOW type was not specified or was invalid.
CAL2A091E INVALID DELETE TYPE REQUESTED

Explanation: Internal error. A call was made to the CA-7/API to delete something from a
JOBFLOW in the API structure. However, the type of delete was not specified or was invalid.
CAL2A092E SYMBOLIC JCLLIB NOT SUPPORTED BY YOUR RELEASE OF CA-7

Explanation: A call was made to the CA-7/API to update a CA-7 job definition with a symbolic
JCLLIB value. However, you must be at CA-7 Version 3.2 or above to use the symbolic JCLLIB
feature.
User Response: Respecify the request without a JCLLIB value.
CAL2A093E ARF FACILITY NOT SUPPORTED BY YOUR RELEASE OF CA-7

Explanation: A call was made to the CA-7/API to update a CA-7 job definition with an ARFSET
value. However, you must be at CA-7 Version 3.2 or above to use the ARF feature.
User Response: Respecify the request without an ARFSET value.
CAL2A099E INVALID L2WKFLAG VALUE.

Explanation: Internal error. A flag used within the CA-7/API to build/update JOBFLOW structures
contained an invalid value.

2.7 CAL Messages
CAL2A501E NO xxxxxxxx VALUE SUPPLIED.

Explanation: The value supplied for a program parameter keyword is invalid. Default values are
supplied for these parameters in 'userid.VPOINT.PROFILE(CACCENV)'.
User Response: Correct the parameter values CA7APPL= and CA7SESS= and re-execute.
CAL2A503E INVALID ENTRY CODE, R1=nnnnnnnn.

Explanation: This is an internal error.
User Response: The error may be transient. Attempt to re-execute the CA-7 API. If the error
persists, save all ISPF log and list output. Also collect any dumps that may have been produced and
contact your installation's CA-7 specialist for assistance.
CAL2A504E INVALID RETURN CODE, R15=nnnnnnnn.

User Response: The error may be transient. Attempt to re-execute CA-7. If the error persists, save
all ISPF log and list output. Also collect any dumps that may have been produced and contact your
CAL2A505E SESSION TERMINATED DUE TO ERROR.

Explanation: The CA-7 terminal session under the CA-7 API has been terminated. The reasons for
termination may be explained by previous error messages.
User Response: See the previous error messages for information on the reason for termination.
Take the indicated action and attempt to execute the CA-7 API again. If the error persists, contact
your installation's CA-7 specialist for assistance.
CAL2A506E xxxxxxxx GENCB FAILED, R15 = nnnnnnnn

Explanation: A GENCB macro failed for the VTAM control block named. R15 contains the return
code from the GENCB. See the IBM ACF/VTAM Programming (SC27-0449).
User Response: Specific information on the reason for the failure will be found in the aforemen-
tioned publication. A common reason for a GENCB failure is an insufficient region size for the
CA-7 API session. If the error persists, contact your installation's CA-7 specialist for assistance.
CAL2A507E SYNTAX ERROR PARSING ACB NAME FOR SESSION

Explanation: An error was encountered trying to parse the ACB name provided on the CA7SESS=
keyword in the CACCENV member of the Profile data set.
User Response: Make sure that the value supplied for the CA7SESS= parameter follows the format
XXXNNNN where it is the highest ACB defined to VTAM for CA-7 (for example, CA70010). See
the CA-7 Interfaces Guide CA-7/API Requirements for more information.

2.7 CAL Messages
CAL2A508E CONNECT ACB UNAVAILABLE OVER 10 SECONDS

Explanation: The ACB needed for the CA-7 API session establishment could not be OPENed
during the time period allowed. The ACB used for session establishment is the ACB name that ends
with 0000. Please refer to the CA-7 Systems Programmer Guide for further information on the defi-
nition of the ACBs.
Note: This message could be produced during a period of high activity when there are many users
attempting to establish CA-7 terminal sessions under TSO-ISPF and/or the CA-7 API.
User Response: If the message was produced during a period of high activity, simply wait a few
minutes and re-execute CA-7 API. If an error condition seems possible then attempt to activate the
VTAM application where the ACBs are defined by issuing a
v net,id=APPL,act
APPL in this example should be replaced by the name of the appropriate VTAM application. If this
fails, review the installation steps outlined in the CA-7 Systems Programmer Guide pertaining to the
definition of the VTAM ACBs for possible errors. If the error persists, contact your installation's
CAL2A509E xxxxxxxx ACB OPEN FAILED, ACBOFLGS = nnnnnnnn

Explanation: A VTAM OPEN macro failed for the ACB named by xxxxxxxx. The ACBOFLGS
codes may provide information as to the reason for the failure. Please refer to IBM ACF/VTAM
Programming (SC27-0449).
User Response: If the ACB named is the 0000 ACB, then this message will probably be accompa-
nied by a CAL2A508 message. In that event, please refer to the recommended action for that
message. Otherwise refer to the aforementioned IBM publication for information on the reasons why
VTAM failed the OPEN request. If the error persists, contact your installation's CA-7 specialist for
assistance.
CAL2A510E RTNCD = xxxxxxxx, FDBK2 = yyyyyyyy

Explanation: This is an informational message which may be preceded by a message indicating an
RPL based VTAM macro failure. For information on the meaning of these codes, please refer to
IBM ACF/VTAM Programming (SC27-0449).
User Response: None. This message is informational. See the action recommended for the
message specific to the macro failure.
CAL2A511E SESSION USER LIMIT REACHED, TRY AGAIN LATER

Explanation: All of the VTAM ACBs defined for use with the CA-7/TSO-ISPF and CA-7 API
interface are currently in use by other ISPF or the CA-7 API sessions.
User Response: Wait a few minutes and try the interface again. If the problem persists, consider
increasing the number of VTAM ACBs.

2.7 CAL Messages
CAL2A512E xxxxxxxx TRANSLATION FAILED, R0 = nnnnnnnn

Explanation: An error occurred during the attempt to evaluate an address. xxxxxxxx is the internal
function name and R0 contains the return code from the function routine.
User Response: Note the sequence of events that resulted in the failure. Collect all ISPF log and
list output from the time frame when the failure occurred. Contact your installation's CA-7 specialist
for assistance.
CAL2A513E SCREEN TRANSLATION ERROR

Explanation: An error occurred during the attempt to build CA-7 API output for a CA-7 screen.
This message may be accompanied by others which will give a reason for the error.
User Response: See the action(s) recommended for any accompanying messages.
CAL2A514E ERROR DETECTED IN EDITOR

Explanation: An error occurred during an API edit session. This message may be accompanied by
others which will give a reason for the error.
User Response: See the action(s) recommended for any accompanying messages.
CAL2A515E xxxxxxxx FAILED, R0 = nnnnnnnn

Explanation: The VTAM macro named at xxxxxxxx failed. Please refer to IBM ACF/VTAM Pro-
gramming (SC27-0449) for further information.
User Response: If the error persists, contact your installation's CA-7 specialist for assistance.
CAL2A516E INVALID WRITE CONTROL CHARACTER - xx

Explanation: An invalid 3270 write control character was received from CA-7. xx is the hex value
of the character.
User Response: The problem may be transient. Re-execute the interface. If the problem persists,
CAL2A517E INVALID 3270 DATASTREAM ORDER - xx

Explanation: An invalid 3270 datastream order character was received from CA-7. xx is the hex
value of the character.
User Response: The problem may be transient. Re-execute the interface. If the problem persists,
CAL2A518E INVALID EDIT HEADER, EDIT SESSION TERMINATED

Explanation: Internal information needed to maintain Editor protocols between CA-7 and the API
was missing or invalid.
User Response: If the CA-7 API modules are accessed from a library other than the CA-7 pro-
duction load library, then make sure that all of the API modules are running at the same maintenance
level as the CA-7 address space. If the problem persists, contact your installation's CA-7 specialist
for assistance.

2.7 CAL Messages
CAL2A519E UNABLE TO OPEN EDITOR WORK FILE

Explanation: The work file that was dynamically allocated for use in a CA-7 API edit session
could not be opened.
User Response: This message may be accompanied by other messages. If so, refer to the action(s)
recommended for any accompanying messages. If there are no other messages, re-enter the edit
session.
CAL2A520E UNABLE TO COMPLETE VTAM CONNECTION WITH CA-7

Explanation: A VTAM REQSESS macro was issued to establish a session with CA-7; however, no
response from CA-7 was received.
User Response: This message may be ignored if CA-7 was terminating during the attempt to
connect to CA-7 from the CA-7 API. Re-execute the interface. If the condition persists, contact
Computer Associates Technical Support.
CAL2A521E NSEXIT CLEANUP REQUEST - LINK IS DOWN

Explanation: The VTAM link with CA-7 is no longer active. There are several possible explana-
tions for this condition. For example, a VTAM command may have been issued to inactivate the
application, or CA-7 may be down, or a /CLOSE may have been issued to close the CA-7 VTAM
ACB.
User Response: No CA-7 terminal sessions will be available under the CA-7 API until the VTAM
link is reestablished. Determine the cause of the outage and re-execute the interface. If the error
persists, contact Computer Associates Technical Support.
CAL2A522E NSPE RU RECEIVED - SESSION TERMINATED

Explanation: The NSEXIT exit was entered for a Network Services Procedure Error. See the IBM
ACF/VTAM Programming (SC27-0449) for information on the specific error conditions that might
cause this condition.
User Response: Re-execute the interface. If the error persists and no VTAM problem is indicated,
then contact your installation's CA-7 specialist.
CAL2A523E LOSTERM EXIT ENTERED - SESSION TERMINATED

Explanation: This exit may be entered under certain session outage conditions. See the IBM
CAL2A524E TPEND EXIT ENTERED - SESSION TERMINATED

Explanation: The TPEND exit was entered for this ACB. This exit may be entered in response to
a VTAM HALT command, or may be entered if VTAM terminates.
User Response: No CA-7 session under CA-7 API will be available until the VTAM link between
CA-7 and the CA-7 API sessions is reestablished. If the error persists and no problem can be
detected in VTAM, then contact your installation's CA-7 specialist.

2.7 CAL Messages
CAL2A525E INVALID RESPONSE FROM CA-7 TO REQUEST FOR SLU ACBNAME

Explanation: A CA-7 API session requested the assignment of an ACB name for use in estab-
lishing a VTAM link. CA-7 returned a response not recognized by the requestor.
User Response: Review the following for possible error conditions:
1. Determine that the VTAM link is being attempted for the correct copy of CA-7. Make sure that
the ACB defined for that copy of CA-7 is named on the CA7APPL keyword in
'userid.VPOINT.PROFILE(CACCENV)'.
2. The value for the CA7SESS= keyword in 'userid.VPOINT.PROFILE(CACCENV)' must match
the VTAM ACF definitions.
Correct any parameter values that may be in error, and then re-execute the interface. If the error
persists, contact your installation's CA-7 specialist for assistance.
CAL2A526E SVC 99 ERROR, R15=xxxxxxxx, R0=xxxxxxxx

Explanation: An attempt to allocate an editor work file failed. The R15 and R0 values should
indicate the nature of the problem. See the IBM MVS/SPL Job Management (GC28-1303) for infor-
mation on the return codes from dynamic allocation.
User Response: Correct the problem that prevented the successful dynamic allocation and re-
execute the interface.
CAL2A527E CA-7 SCRGET DISP=FIRST FAILED. EDIT TERMINATED.

Explanation: CA-7 encountered an error attempting to read Active Area data for this terminal. The
edit session will be terminated.
User Response: If the problem persists, contact Computer Associates Technical Support.
CAL2A530E OPEN/CLOSE SUBTASK ENDED. TCBCMP= xxsssuuu

Explanation: The subtask that was created to handle OPEN and CLOSE requests for the VTAM
ACBs used for the CA-7 terminal session ended. A nonzero TCBCMP indicates an abnormal termi-
nation. In such a case, sss is the system abend code and uuu is the user abend code.
User Response: Collect any dumps that may have been produced and contact Computer Associates
Technical Support.
CAL2A542E ERROR OCCURRED IN SCIP EXIT

Explanation: The VTAM SCIP exit for this terminal session's ACB encountered an error.
User Response: Collect any console and dump information that may have been produced and
contact Computer Associates Technical Support.
CAL2A543E VTAM LOGICAL ERROR EXIT ENTERED

Explanation: The VTAM LERAD exit for this terminal session's ACB was entered.
User Response: If this message is produced and there are no accompanying messages indicating
either VTAM or CA-7 error conditions, contact Computer Associates Technical Support.

2.7 CAL Messages
CAL2A544E VTAM SYNAD EXIT ENTERED

Explanation: The VTAM SYNAD exit for this terminal session's ACB was entered.
CAL2A546E VTAM APPL FOR CA-7 NOT ACTIVE OR NOT ACCESSIBLE

Explanation: The VTAM APPL named on the CA7APPL= parameter in
'userid.VPOINT.PROFILE(CACCENV)' is not currently active or is not accessible in this domain.
User Response: Make sure that the copy of CA-7 associated with the VTAM APPL named in the
CA7APPL parameter is active and that the VTAM ACB is open. Make sure that this APPL is
accessible in the domain where the CA-7 API session is running.
CAL2A547E CA-7 UNRESPONSIVE FOR 10 SECONDS, SESSION TERMINATED.

Explanation: The CA-7 API was invoked and timed out before CA-7 responded to the initialization
calls.
User Response: Check the parameters in your API PROFILE data set, member CACCENV.
Ensure that the CA7APPL= keyword specifies the correct VTAM APPLid for the CA-7 you wish to
communicate with.
CAL2A601E No table module found.

Explanation: The API table module used to satisfy the current request was not found when an
attempt was made to load it.
User Response: Check your STEPLIB, ISPLLIB, and linklist concatenations to ensure the
CA-7/ViewPoint CAILIB is accessible to the CA-7 API user session.
CAL2A605E APIRB_SESSN_ANCHOR is zero.

Explanation: Internal error in the communication between SQL interface online system and the
CA-7 API interface.
CAL2A610E Table module does not begin with DESCRIBE.

Explanation: Internal error in the CA-7 API interface.
CAL2A615E (aa bbbb) BAD QSEQ - L2APIRB IS CLOSED. QUERY : cccccccc

Explanation: A validate call from an existing SQL Query request failed. aa is the caller's prefix.
bbbb is the offset into the table. cccccccc is the query type.
User Response: If this was during API startup, shut down the API server and make sure that the
CA7APPL points to the correct CA7SESS variable. Check to see if the major node defined for the
CA-7 API session is active, and if not, activate it. If this was not during startup, cancel the current
request and retry your request. If the errors persists, contact your installation's CA-7 specialist for
assistance.

2.7 CAL Messages
CAL2A616E (aa bbbb) L2APIRB ALLOCATION FAILED, R15=cccccccc

Explanation: An allocation request for the named API control block failed. R15 contains a
hexadecimal code that identifies the location within the API subroutine module.
User Response: This message more than likely followed the CAL2A615E message. Attempt to
resolve the prior message. If the errors persists, contact your installation's CA-7 specialist for assist-
ance.
CAL2A618E (xx yyyy) QUERY TYPE NOT SUPPORTED BY API TABLE : nnnnnnnn
Explanation: A request is invalid for this screen.
User Response: Make sure that the latest maintenance is applied.
CAL2A620E Unrecognized APIRB_QUERY_TYPE.

Explanation: Internal error in the communication between the SQL interface and the CA-7 API
interface.
CAL2A630E GETMAIN failure.

Explanation: The CA-7 API interface was unable to acquire the storage needed to satisfy the
current request.
User Response: Increase your TSO region and retry the sequence of commands that led to the
error.
CAL2A640E Unrecognized verb in table module.

interface.
CAL2A650E Conversion error from L2L10042 on xxxx at yyyy.

CAL2A660E Unrecognized parm on xxxxx at yyyyy.

CAL2A670E TOO MANY OPTIONS SELECTED. PLEASE RESPECIFY.

Explanation: The total length of the options specified on the request exceeded the limit for the API
to pass to CA-7. The request was not processed.
User Response: Respecify the request to limit the overall length of the options.

2.7 CAL Messages
CAL2A700E L2VDB for xxxxxxxx not found.

CAL2A705E (aa bbbb) BAD QSEQ - REQ POINTS AT CLOSED RB. QUERY : cccccccc
Explanation: A call from an existing SQL Query request failed. aa is the caller's prefix. bbbb is
the offset into the table. cccccccc is the query type.
User Response: This message more than likely followed the CAL2A615E message. Attempt to
resolve the prior message. If the errors persists, contact your installation's CA-7 specialist for assist-
ance.
CAL2A720E L2VP not found.

CAL2A800E Variable not found - xxxxxxxx.

CAL2A810E QRYD_WHRNAMES pointer is zero.

interface.
CAL2A820E Table col name not in QRYD_WHRNAMES.

interface.
CAL2A830E Located WHRNAMES but WHRVALS is zero.

Explanation: Internal error in the communication between SQL interface and the CA-7 API inter-
face.
CAL2A840E FREEMAIN error.


2.7 CAL Messages
CAL2A850E –CAL2C103W
CAL2A850E Not supported by your version of CA-7.

Explanation: The function you requested is not supported by the version of CA-7 that you are
connected to. This usually means the CA-7 API you are using is at a higher version level than the
CA-7 you are connected to, and you have requested a function that requires features contained in the
new version of CA-7.
communicate with.
CAL2A900E API/CA-7 interface ended, unable to process request.

Explanation: The VTAM interface between the CA-7 API and the CA-7 address space has termi-
nated.
User Response: First check to ensure the CA-7 Address space is still active. If so, back out of
ViewPoint and re-enter it. Access a CA-7 data panel to reestablish the connection. If the problem
persists, contact Computer Associates Technical Support for assistance.
CAL2C100E UNABLE TO GETMAIN STORAGE FOR xxxxxxxx RC=cccc

Explanation: ICOM was unable to get storage for the control block indicated by xxxxxxx. The
return code from the GETMAIN call is indicated by cccc.
User Response: Increase the REGION size of the ICOM started task.
CAL2C101E ERROR RETURN FROM IXCQUERY CALL: TYPE=tt R15=cc INFO=iiiiiiii

Explanation: An error was returned from the IXCQUERY call. The type of IXCQUERY call is
indicated by tt, the return code is cc, and the information code is indicated by iiiiiiii.
CAL2C102E ERROR FROM tttttttt CALL: RC=rr CC=cccccccc ffffffff

Explanation: An error was returned from an IXL service call. The type of service is indicated by
tttttttt, the return code is rr, the condition code is cccccccc, and the requested function is ffffffff.
CAL2C103W CF NOT ENABLED: xxx...xxx

Explanation: The ICOM Coupling Facility interface has not been enabled. The specific reason is
indicated by xxx...xxx.
User Response: If you wish to use the ICOM Coupling Facility interface, correct the situation indi-
cated by the message and restart ICOM.

2.7 CAL Messages
CAL2C150W –CAL2C203I
CAL2C150W CA-7 ICOM COUPLE FACILITY STRUCTURE IS FULL. TASKS WAITING.

Explanation: An attempt to write data to the Coupling Facility failed because there is no space left.
ICOM will continue to attempt to write the data. This message will automatically be deleted from
the console if the full condition is relieved.
User Response: If the message persists, check to ensure that at least one ICOM in the SYSPLEX is
operating in a READ mode (CF=R). If so, switch one or more other ICOMs to CF=R mode. If the
problem occurs on a regular basis expand the size of the CA-7 ICOM Coupling Facility data set.
CAL2C151E ERROR RETURN FROM ICMC CALL (ttt). FUNC=ffffffff RC=rr CC=cc
Explanation: An error was returned from a call to the ICOM Coupling Facility communications
module. The ICOM task which made the call is indicated by ttt (SMF, TRL or CF), the function
called is ffffffff, the return code is rr, and the condition code is cc.
User Response: Check for other messages which may further identify the nature of the error. If the
problem persists, contact Computer Associates Technical Support for assistance.
CAL2C152E UNKNOWN ECB POST TO ICOM CF TASK

Explanation: The ICOM Coupling Facility subtask was posted with an unknown code. The Cou-
pling Facility subtask will abend with a User 703 code. ICOM processing will terminate.
User Response: Check for other messages which may further identify the nature of the error. If the
problem persists contact Computer Associates Technical Support for assistance.
CAL2C200I CF STRUCTURE CONNECTED

Explanation: This is an ICOM Coupling Facility trace message indicating that a connection has
been made to the ICOM CF structure in the Coupling Facility.
CAL2C201I CF MONITORING STARTED

Explanation: This is an ICOM Coupling Facility trace message indicating that monitoring of lists
in the ICOM CF structure has been started.
CAL2C202I CF BUFFER WRITTEN TO xxxx

Explanation: This is an ICOM Coupling Facility trace message indicating that a data buffer has
been written to list xxxx in the ICOM CF structure.
CAL2C203I CF BUFFER READ FROM xxxx

Explanation: This is an ICOM Coupling Facility trace message indicating that a data buffer has
been read from list xxxx in the ICOM CF structure.

2.7 CAL Messages
CAL2C204I –CAL2C300W
CAL2C204I CF STRUCTURE DISCONNECTED

Explanation: This is an ICOM Coupling Facility trace message indicating that the connection to the
ICOM CF structure in the Coupling Facility has been disconnected.
CAL2C205I CF TERMINATION COMPLETE

Explanation: This is an ICOM Coupling Facility trace message indicating that the ICOM CF termi-
nation processing is complete.
CAL2C206I CF MONITORING STOPPED

Explanation: This is an ICOM Coupling Facility trace message indicating that monitoring of lists
in the ICOM CF structure has been terminated.
CAL2C250I CF TASK HAS POSTED SMF TASK

Explanation: This is an ICOM Coupling Facility trace message indicating that the ICOM CF
subtask has posted the SMF task to process a data buffer read from the ICOM data structure.
CAL2C251I CF TASK HAS POSTED TRL TASK

Explanation: This is an ICOM Coupling Facility trace message indicating that the ICOM CF
subtask has posted the Trailer (TRL) task to process a data buffer read from the ICOM data structure.
CAL2C300W X2W0 ESTAE ENTERED - WIP=wwww (aaaa) (pppppppp): ddd...ddd

Explanation: The main task error routine has been entered for an abend in processing. The where-
in-program code is indicated by wwww. The abend code is indicated by aaaa (hex). The abend
PSW is indicated by pppppppp. If the PSW points to an address within the main task program
(CAL2X2W0) it will be in the form of '+offset'. If not, it will be the full 8 character PSW. The
description of the action being taken by the recovery routine is indicated by ddd...ddd. If the
recovery routine will attempt to continue processing, the description will be 'RETRY IS BEING
ATTEMPTED'. If the abend occurred during a call to the user print exit then no more calls will be
made to the print exit. If the recovery routine will not attempt to continue, the description will be
'ALLOWING ABEND TO PROCEED' and the task will abend.
User Response: If the abend occurred in the user print exit (WIP=M7EX), check your exit for
errors. Otherwise, contact Computer Associates Technical Support for assistance.

2.7 CAL Messages
CAL2C301W –CAL2C452I
CAL2C301W 'SUBMIT' CLASS/RESOURCE NOT DEFINED TO EXTERNAL SECURITY. FUNCTION

ALLOWED.
Explanation: An attempt was made to check the authorization for the owner of the current environ-
ment to submit a CA-7 logon for the operator ID specified on the /LOGON command being proc-
essed. The external security system responded with a return code 4, indicating SUBMIT is not a
defined resource. The /LOGON command and subsequent commands will be processed normally.
Any messages returned by the external security system will be listed following this message.
User Response: If you want CA-7 External Communicators to be controlled by your external secu-
rity system, the SUBMIT resource and applicable rules must be defined. See the CA-7 Security
Guide for details on implementation.
CAL2C401I SESSION INIT SENT.

Explanation: This is a trace message indicating that a Session Initialization record was sent to
CA-7.
CAL2C402I DATA CLOSE SENT. (EOD)

Explanation: This is a trace message indicating that a Data Close record was sent to CA-7 indi-
cating end of data on command input.
CAL2C403I DATA CLOSE RECEIVED.

Explanation: This is a trace message indicating that a Data Close record was received from CA-7
indicating end of data on command output.
CAL2C404I SESSION END SENT.

Explanation: This is a trace message indicating that a Session End record was sent to CA-7.
CAL2C452I (X2W) CCIF=ffff RC=rr CC=cc: CCI=f2f2 RC=r2 CC=c2 rrr...rrr

Explanation: This is a trace message indicating the completion of a specific CCI call. The func-
tion, return code and condition code of the call to the CCI interface module are indicated by ffff, rr
and cc. The function, return code and condition code of the call to CAICCI itself are indicated by
f2f2, r2 and c2. If the function is a send or receive then the first 60 characters of the data is listed in
rrr...rrr.

2.7 CAL Messages
CAL2C501I –CAL2C508W
CAL2C501I ***** INPUT TO CA-7 CCI BATCH INTERFACE *****

Explanation: This message is printed before listing the command input to the CA-7 CCI batch
interface. The input commands are listed following this message.
CAL2C502I ***** END OF INPUT TO CA-7 CCI BATCH INTERFACE *****

Explanation: This message is printed after listing the command input to the CA-7 CCI batch inter-
face.
CAL2C503W ***** NO CA-7 COMMANDS IN INPUT *****

Explanation: This message indicates that there were no CA-7 commands in the input to the CA-7
CCI interface.
User Response: Check to ensure that DDNAME SYSIN is in the JCL to invoke the CA-7 CCI
interface. If you have overridden the DDNAME for command input, ensure that the DDNAME in
your JCL correctly corresponds to the override.
CAL2C504I ***** RESPONSES RECEIVED FROM CA-7 *****

Explanation: This message is printed before listing the command output sent from CA-7 to the
CA-7 CCI interface. The command output lines are listed following this message.
CAL2C505I ***** END OF CA-7 RESPONSES *****

Explanation: This message is printed after listing the command output sent from CA-7 to the CA-7
CCI interface.
CAL2C506W ***** NO CA-7 RESPONSES RECEIVED *****

Explanation: This message is printed to indicate that no command output was received from CA-7.
User Response: Look for other messages in SYSPRINT or in the JES Log to indicate errors in the
commands or the interface.
CAL2C508W ERROR MSGS FOUND IN OUTPUT. MSGS MATCHED=xxx, HIGH CC=ccc

Explanation: This WTO is issued at the end of CA-7 CCI Batch processing if any lines in the
CA-7 output matched an entry in the user-defined batch message table (SASSXXBT). The number
of matches made (xxx) and the highest condition code associated with those entries (ccc) are detailed.
The return code of the CA-7 CCI Batch step is set to the highest condition code matched.

2.7 CAL Messages
CAL2C509I –CAL2C591E
CAL2C509I CA-7 CCI BATCH PROCESS COMPLETE. RC=rrrr CC=cccc

Explanation: The CA-7 CCI Batch Interface module (CAL2X2WB) has completed processing. The
return code (rrrr) and condition code (cccc) from the process are listed (in hexadecimal).
User Response: If the return and/or condition codes are non-zero, refer to any messages preceding
this one. For an explanation of the return and condition codes, refer to External Communicators in
the CA-7 Interfaces Guide.
CAL2C580W WARNING - DD STATEMENT IS MISSING OR INVALID: dddddddd

Explanation: This DDNAME dddddddd is either missing from the JCL or is invalid. The DD
statement is optional and processing will continue without it.
User Response: If the DD was omitted on purpose, ignore the message. If not, correct the JCL to
supply the listed DD statement.
CAL2C581W UNABLE TO OPEN ERRORS DD. MESSAGE TABLE ERRORS WILL NOT BE
REPORTED.
Explanation: This message is issued when a user-defined Batch Message Table (SASSXXBT) is
available, but the DD statement for the ERRORS file is not in the JCL. Normally, messages from
the Batch Message Table checking are routed to this ERRORS DD. Since this DD is not available,
the messages will not be produced. However, you will still get the CAL2C508W message which
informs you how many table matches were made, and what the highest matched condition code is.
User Response: Add a DD statement for ERRORS. The format is the same as the existing
SYSPRINT DD.
CAL2C582W ERROR MSG TABLE MATCH (CC=ccc): ...text...

Explanation: This message is written to the ERRORS DD when a line in the CA-7 CCI Batch
output matches an entry in the user-defined batch message table (SASSXXBT). The condition code
(CC=) that is associated with that table entry is listed. Also, the text of the matching output line is
displayed.
CAL2C590E INVALID PARAMETER LIST

Explanation: The parameter list passed to the CA-7 CCI interface was invalid. A return code of 16
is set and processing is terminated.
User Response: Correct the parameter list and resubmit the job.
CAL2C591E INVALID PARAMETER STARTING WITH (xxxxxxxx) - ABORTING

Explanation: A value (xxxxxxxx) in the parameter list passed to the CA-7 CCI interface was
invalid. A return code of 16 is set and processing is terminated.
User Response: Correct the parameter list and resubmit the job.

2.7 CAL Messages
CAL2C592E –CAL2C601E
CAL2C592E DD STATEMENT IS MISSING OR INVALID: dddddddd

Explanation: This DDNAME dddddddd is either missing from the JCL or is invalid. The DD
statement is optional and processing will continue without it.
User Response: If the DD was omitted on purpose, ignore the message. If not, correct the JCL to
supply the listed DD statement.
CAL2C593E ERROR DURING DCB OPEN: dddddddd

Explanation: An error occurred attempting to open the DCB for DDNAME dddddddd. Processing
will terminate.
User Response: Check the JCL and correct the DD statement in error.
CAL2C594E UNABLE TO GETMAIN STORAGE FOR xxxxxxxx

Explanation: An error occurred attempting to get storage for control block xxxxxxxx. Processing
will terminate.
User Response: Increase the region size and resubmit the job.
CAL2C595E UNABLE TO LOAD MODULE mmmmmmmm . RC=rrrr

Explanation: An error occurred attempting to load module mmmmmmmm. The return code from
the LOAD call is rrrr.
User Response: Check the STEPLIB DD statement in the JCL and ensure that the CA-7 load
library (CAILIB) is in the concatenation.
CAL2C596E NON-ZERO RETURN FROM CA-7 CCI INTERFACE. RC=rrrr CC=cccc

Explanation: An error code was returned from the CA-7 CCI interface module (CAL2X2W0). The
return code was rrrr, and the reason code was cccc.
User Response: See any messages in the JES Log indicating the nature of the error encountered.
Otherwise, contact Computer Associates Technical Support for assistance.
CAL2C600W VARIABLE xxxxxxxx COULD NOT BE RETRIEVED--CODE cc

Explanation: An error code was encountered in the CA-7 CCI interface REXX facility. The vari-
able xxxxxxxx could not be accessed. The return code from the access attempt was cc.
User Response: See the sample CA-7 REXX CLIST (CA7REXX) in the CA CLIST library
(CAICLIB). Ensure that your execution of the facility does not specify invalid values for variables
that are available.
CAL2C601E UNABLE TO ACCESS CA-7 MODULE CAL2X2W0

Explanation: An error occurred attempting to load module CAL2X2WO (CA-7 CCI interface) from
the CA-7 CCI REXX facility.
User Response: Check the environment and ensure that the CA-7 load library (CAILIB) is acces-
sible.

2.7 CAL Messages
CAL2C602E CA-7 COMMAND STRING IS MISSING

Explanation: The CA-7 CCI interface REXX facility was invoked, but no CA-7 commands were
specified.
User Response: Execute the interface specifying one or more CA-7 commands. See the sample
CA-7 REXX exec (CA7REXX) in the CA CLIST library (CAICLIB) for an example.
CAL2C901E INVALID PARAMETER: xxxxxxxx: ABORTING

Explanation: An invalid parameter (xxxxxxxx) was passed to the CA-7 CCI interface module.
User Response: Correct the specified parameter and resubmit/execute the interface.
CAL2C902E UNABLE TO LOAD MODULE mmmmmmmm. RC=rrrr

Explanation: An error occurred attempting to load module mmmmmmmm. The return code from
the LOAD call is rrrr.
User Response: Check the STEPLIB DD statement in the JCL/environment and ensure that the
CA-7 load library (CAILIB) is in the concatenation.
CAL2C903E CA-7 RECEIVER NOT FOUND (aaa...aaa/nnn...nnn)

Explanation: The CA-7 CCI interface module could not locate the CA-7 CCI Terminal CAICCI
receiver where: aaa...aaa indicates the CA-7 CCI Terminal receiver name, and nnn...nnn indicates the
CCI node name.
User Response: Check to ensure that the CA-7 address space is active. If so, check the CA-7
address space to ensure that one or more CCI Terminals are defined (DEVICE=CCI). If so, check
the CA-7 JES Log for CA-7.XTM... messages to confirm that the CCI terminal interface has initial-
ized properly. If so, check to ensure that the CA-7 CCI interface is looking for CA-7 at the correct
CAICCI node (nnn...nnn). Otherwise, contact Computer Associates Technical Support for assistance.
CAL2C904E BUFSIZE FROM CA-7 INVALID.

Explanation: The CA-7 CCI interface module received an Init response record from CA-7 which
contained an invalid buffer size. Processing is terminated.
CAL2C905E CA-7 XTM NOT RESPONDING (aaa...aaa/nnn...nnn)

Explanation: The CA-7 CCI Terminal facility is not responding to calls from the CA-7 CCI inter-
face. The CA-7 CCI Terminal CAICCI receiver is indicated where: aaa...aaa is the CA-7 CCI Ter-
minal receiver name, and nnn...nnn is the CCI node name.
User Response: Check to ensure that the CA-7 address space is active. If so, check the CA-7 JES
Log for CA-7.XTM... messages to see if the CCI terminal interface has encountered any errors.
Otherwise, contact Computer Associates Technical Support for assistance.

2.7 CAL Messages
CAL2C906E XTM INIT FAILED. RC=rr RSN=cc TEXT=ttt...ttt

Explanation: The CA-7 CCI Terminal facility returned and error when the CA-7 CCI interface
attempted to initialize a session. The return code (rr) reason code (cc) from CA-7 are specified along
with any message sent from CA-7 (ttt...ttt).
User Response: See the information supplied in the message and take any appropriate corrective
measures. Check the CA-7 JES Log for CA-7.XTM... messages to see if the CCI terminal interface
has encountered any errors. Otherwise, contact Computer Associates Technical Support for assist-
ance.
CAL2C907E INVALID RECORD RECEIVED. REC = rrr...rrr

Explanation: The CA-7 CCI Terminal facility returned an invalid record to the CA-7 CCI interface.
The first 24 characters of the record are listed (rrr...rrr).
CAL2C908E UNEXPECTED REC RECEIVED. EXPECTED eeeeeeee RECEIVED rrrrrrrr (zzzz)

Explanation: The CA-7 CCI Terminal facility returned an unexpected record to the CA-7 CCI
interface. The interface was expecting eeeeeee, but received rrrrrrrr (record code zzzz).
CAL2C909E INVALID BATCH CMD: ccc...ccc

Explanation: The CA-7 CCI interface was passed a CA-7 command which is only valid in an
online CA-7 session. The invalid batch command is listed (ccc...ccc). The command is not sent to
CA-7. Processing continues with the next command.
CAL2C927E (ttt) CCI ERROR FUNC=ffff RC=rr CC=cc TEXT=xxx...xxx

Explanation: The CAICCI subfunction module has encountered an error. The task calling the sub-
function is identified by ttt. The subfunction is indicated by fff, the return code and condition codes
are indicated by rr and cc. A text description of the error is indicated by xxx...xxx.
User Response: Review any preceding or following messages and take corrective actions indicated
by them. If there are no other messages contact Computer Associates Technical Support for assist-
ance.
CAL2C928E (ttt) CCIF CALL FAILED: FUNC=ffff RC=rr CC=cc

Explanation: The CAICCI subfunction module has encountered an internal error. The task calling
the subfunction is identified by ttt. The function is indicated by fff, the return code and condition
codes are indicated by rr and cc.
by them. If there are no other messages, contact Computer Associates Technical Support for assist-
ance.

2.7 CAL Messages
CAL2C950E –CAL2P005E
CAL2C950E BATCH SUBMIT SECURITY VIOLATION - SKIPPING TO NEXT /LOGON COMMAND

Explanation: The external security system would not authorize the owner of the current environ-
ment to submit a CA-7 logon for the operator ID specified on the /LOGON command being proc-
essed. Any messages returned by the external security system will be listed following this message.
The /LOGON command and subsequent commands will be processed normally. The commands fol-
lowing that logon will be skipped until another /LOGON statement is encountered.
User Response: Ensure the owner of the environment has SUBMIT authority for all operator IDs
specified on /LOGON statement(s).
If you do not want submit security checking for CA-7 External Communicators, the ICMDSECT can
be zapped with an option bit to bypass these checks. Refer to the CA-7 Security Guide for details on
implementing this option.
CAL2P001E INVALID PARMLIST RECEIVED: xxxxxxxx

Explanation: The CA-7 CPM Flow Build program received an invalid parmlist. The text xxxxxxxx
describes the error.
CAL2P002E UNABLE TO GETMAIN STORAGE FOR xxxxxxxx

Explanation: The CA-7 CPM Flow Build program could not obtain needed storage for xxxxxxxx.
User Response: Increase the region size.
CAL2P003E UNABLE TO LOAD MODULE xxxxxxxx

Explanation: The CA-7 CPM Flow Build program could not obtain needed storage for xxxxxxxx.
User Response: Increase the region size.
CAL2P004E INVALID xxxxxxxx IN CA7PARMS STARTING WITH yyy...yyy

Explanation: The CA-7 CPM Flow Build program encountered an error in the CA7PARMS
options. The type of error is described by xxxxxxxx, and the first 16 bytes of the data in error is
displayed in yyy...yyy.
User Response: Correct the statement in error.
CAL2P005E ERROR FROM CA-7: xxx...xxx

Explanation: The CA-7 CPM Flow Build program encountered an error message in the output
received from CA-7. The error message is displayed in xxx...xxx.
User Response: If the nature of the error is obvious (security error, and so on), correct the source
of the problem. If not, consult your installation's CA-7 specialist for assistance.

2.7 CAL Messages
CAL2P006E –CAL2P061I
CAL2P006E ERROR FROM CA-7 CCI CALL : RC=rrrr CC=cccc

Explanation: The CA-7 CPM Flow Build program encountered a bad return code from the CA-7
CCI interface when attempting to send a command to CA-7.
User Response: If the nature of the error is obvious (CA-7 is down) then correct the source of the
problem. If not, consult your installation's CA-7 specialist for assistance.
CAL2P050I REQUEST xxx: FUNC=ffff ARG=aaa...aaa RC=rrrr CC=cccc SUCC=ssss

Explanation: The CA-7 CPM Flow Build program is running with the trace option enabled. Field
xxx indicates IN or OUT to indicate whether the line traces the receipt of a request or the results of a
request. Field ffff indicates the function code for the request. Based upon the type of request
involved, one or more of the following fields will be displayed.
Field Description
aaa...aaa Displays the job name and schedule ID for a READ request.
rrrr cccc Show the return code and condition code for the completion of a request.
ssss Shows the number of successors returned for the argument job upon the successful com-
pletion of a READ request.
CAL2P051I RETURN FROM CA-7 CCI CALL : RC=rrrr CC=cccc CMD=cccccccc

Explanation: The CA-7 CPM Flow Build program is running with the trace option enabled.
Field Description
rrrr cccc Show the return code and condition code from the CA-7 CCI interface.
cccccccc Shows the CA-7 command sent through the CA-7 CCI interface.
CAL2P060I **** CAL2CPCB AT INITIALIZATION ****

Explanation: The CA-7 CPM Flow Build program is running with the trace option enabled. This
message is the storage dump header for the primary control block for the flow build process at the
end of initialization processing.
CAL2P061I **** CMD INPUT TO CA-7 CCI ****

message is the storage dump header for the command block being passed to the CA-7 CCI interface.

2.7 CAL Messages
CAL2P062I –CAL2V004I
CAL2P062I **** CMD OUTPUT FROM CA-7 CCI: RC=rrrr CC=cccc ****
message is the storage dump header for the command output block(s) which contain the CA-7 output
returned using the CA-7 CCI interface.
CAL2P063I **** READ CALL PARAMETER LIST

message is the storage dump header for the parameter information passed on the READ request. It is
followed by the read results storage (see CAL2P064I).
CAL2P064I **** READ RESULTS: RC=rrrr CC=cccc : ARGUMENT=aaa...aaa

message is the storage dump header for the buffer returned for a READ request.
Field Description
aaa...aaa Displays the target job name and schedule ID.
rrrr cccc Field rrrr and cccc show the return code and condition code for the completion of the
READ request.
CAL2V001I Add successfully completed.

Explanation: The add function requested has been performed without error.
CAL2V002I Update successfully completed.

Explanation: The update function requested has been performed without error.
CAL2V003I Delete successfully completed.

Explanation: The delete function requested has been performed without error.
CAL2V004I Rename successfully completed.

Explanation: The rename function requested has been performed without error.

2.7 CAL Messages
CAL2V005I –CAL2V703W
CAL2V005I Enter Schid and Jobname or Network.

Explanation: Too few parameters were specified to perform the current function.
User Response: Specify either a Jobname and Schedule ID (Schid) or a Network name and
Schedule ID (Schid).
CAL2V006I Generic or specific Jobname required.

User Response: This message is issued from the List Job screen (PL2GLJOB) when no Jobname
parameter has been specified.
User Response: In order to generate a List Job transaction you must specify some kind of Jobname
parameter. This can be fully generic (%), partially generic (ABC%), or a specific job name.
CAL2V007I All tasks processed. None remain for specified criteria.

Explanation: This message is issued from the QM - Output Networks screen when all tasks for the
specified criteria have been posted or canceled.
CAL2V701W CA7APPL= VARIABLE NOT FOUND. DEFAULT USED.

Explanation: The keyword variable CA7APPL was not found in the CACCENV member of the
API PROFILE data set. The CA-7 API attempts to use the default value (CA7).
communicate with.
CAL2V702W CA7SESS= VARIABLE NOT FOUND. DEFAULT USED.

Explanation: The keyword variable CA7SESS was not found in the CACCENV member of the
API PROFILE data set. The CA-7 API attempts to use the default value (CA70010).
Ensure that the CA7SESS= keyword specifies the high number of the range of ACBs to be used by
the API. If no special ACBs have been defined for the API you may be able to specify TSO0999
and use ACBs generated for TSO.
CAL2V703W SECURITY CHECK FAILED FOR CA7USER= VALUE. ALTERNATE USERID IGNORED.
Explanation: The keyword variable CA7USER was found in the CACCENV member of the API
PROFILE data set. External security has denied use of this ID to the owner of the API session.
User Response: The CA7USER parameter is ignored and an attempt is made to signon to CA-7
using the API owner ID.

2.7 CAL Messages
CAL2XV01I –CAL2XV11E
CAL2XV01I CA-7 CROSS-PLATFORM TRACKING CHECKPOINT CONVERSION STARTED (V3.2 TO

V3.3)
Explanation: This message is issued when the CA-7 Cross-Platform Tracking conversion process
begins. This process reads the CA-7 3.2 checkpoint information in a PROFILE PDS and creates a
Version 3.3 Cross-Platform Tracking Checkpoint File (XCKPT).
CAL2XV02I CHECKPOINT ENTRY ADDED : xxxxxxxx (yyyy/ddd hh:mm:ss.th)

Explanation: An entry has been created in the new Cross-Platform Tracking Checkpoint file for
node xxxxxxxx. The checkpoint date and time for the entry is yyyy/ddd hh:mm:ss.th.
CAL2XV03I PROFILE MEMBER BYPASSED : xxxxxxxx REASON=rrr...rrr

Explanation: An entry has NOT been created in the new Cross-Platform Tracking Checkpoint file
for a member in the old PROFILE PDS (xxxxxxxx). The reason the entry was not created is
described in rrr...rrr. It is normal for member CACCENV to be bypassed with the reason 'PROFILE
CONTROL MEMBER'.
User Response: If there are several of these messages, check to ensure that the PROFILE DD
points to your CA-7 3.2 Cross-Platform PDS used by the CA7FMUNI task.
CAL2XV09I CA-7 CROSS-PLATFORM TRACKING CHECKPOINT CONVERSION COMPLETE (V3.2

TO V3.3)
Explanation: This message is issued when the CA-7 Cross-Platform Tracking conversion process
completes successfully. This process reads the CA-7 3.2 checkpoint information in a PROFILE PDS
and creates a Version 3.3 Cross-Platform Tracking Checkpoint File (XCKPT).
CAL2XV10E XCKPT OUTPUT DCB OPEN FAILED.

Explanation: An attempt to open the new Cross-Platform Tracking Checkpoint file for output
failed.
User Response: Ensure that the XCKPT DD points to a newly allocated CA-7 Cross-Platform
Checkpoint file.
CAL2XV11E XCKPT INPUT DCB OPEN FAILED.

Explanation: An attempt to open the new Cross-Platform Tracking Checkpoint file for input failed.
Checkpoint file.

2.7 CAL Messages
CAL2XV12E –CAL2X001I
CAL2XV12E XCKPT FILE IS NOT EMPTY.

Explanation: The data set pointed to by the XCKPT DD statement is not an empty file. The
conversion process will not overlay an existing file. It will only build a new Checkpoint file from
scratch.
Checkpoint file.
CAL2XV13E RDJFCB CALL FAILED FOR PROFILE DD (x).

Explanation: A read JFCB call to obtain information about the PDS pointed to by the PROFILE
DD statement returned an error. The code (x) is an internal processing code.
User Response: Ensure that the PROFILE DD points to an existing 3.2 Cross-Platform Platform
PROFILE PDS.
CAL2XV14E MONITOR= VALUE NOT FOUND IN PROFILE MEMBER CACCENV.

Explanation: The CA-7 Cross-Platform monitor name keyword/value was not found in the
CACCENV member of the PDS pointed to by the PROFILE DD.
PROFILE PDS.
CAL2XV15E NO MEMBERS FOUND IN PROFILE.

Explanation: No members were found in the PDS pointed to by the PROFILE DD.
PROFILE PDS.
CAL2XV16E MEMBER CACCENV NOT FOUND IN PROFILE.

Explanation: The control member CACCENV was not found in the PDS pointed to by the
PROFILE DD.
PROFILE PDS.
CAL2XV17E PROFILE OPEN FAILED.

Explanation: An attempt to open the PDS pointed to by the PROFILE DD failed.
PROFILE PDS.
CAL2X001I CA-7 Cross-Platform Submit Process Starting - yyyy/ddd hh:mm:ss.th

Explanation: The CA-7 Cross-Platform submission process has been initiated. The starting date
(Julian) and time are indicated on the message.

2.7 CAL Messages
CAL2X002I –CAL2X008E
CAL2X002I Job jjjjjjjj (####) submitted to node nnnnnnnn

Explanation: A CA-7 Cross-Platform job request for job jjjjjjjj, job number ####, has been sent to
CAICCI node nnnnnnnn.
CAL2X003I CA-7 Cross-Platform Submit Process Complete - yyyy/ddd hh:mm:ss.th

Explanation: The CA-7 Cross-Platform submission process has completed. The completion date
(Julian) and time are indicated on the message.
User Response: If the Cross-Platform request was successfully sent to the target node, the submit
step will complete with a return code of zero. If the request was not sent successfully, the sub-
mission step will abend with a user abend code. If so, see the previous messages for an indication of
the specific error encountered.
CAL2X005W CAICCI Receiver 'SUBMITC Server' not found at node nnnnnnnn

Explanation: The CA-7 Cross-Platform submission process was unable to send the request because
CAICCI could not locate the target scheduling system at node nnnnnnnn.
User Response: Check the CAICCI TCPIP Gateway task to determine if the local MVS system has
a connection to the target node. If they are connected, check the target system to determine if the
CA scheduling system is active. Once the CAICCI connection has been established, and/or the target
scheduling system is activated, the CA-7 Cross-Platform Submit job can be rerun.
CAL2X006W pppppppp from ssssssss ignored : ....reason....

Explanation: The CA-7 Cross-Platform submission process encountered an input parameter
pppppppp from the source ssssssss (EXECPARM, PROFILE or SYSIN) which was ignored. The
reason for the exception is described (....reason....).
User Response: The submit process will continue. Check the parameter which caused the excep-
tion, and correct it if needed.
CAL2X007E pppppppp from ssssssss IN ERROR : ....reason....

Explanation: The CA-7 Cross-Platform submission process encountered an input parameter
pppppppp from the source ssssssss (EXECPARM, PROFILE or SYSIN) which was in error. The
reason for the exception is described (....reason....).
User Response: The submission process will be UNSUCCESSFUL. Once the parameter has been
corrected the CA-7 Cross-Platform Submit job can be rerun.
CAL2X008E Required Parameter missing (pppppppp) - process aborted.

Explanation: The required parameter pppppppp was not provided to the CA-7 Cross-Platform sub-
mission process. Processing cannot continue without it.
User Response: The submission process will be UNSUCCESSFUL. Once the parameter has been
specified the CA-7 Cross-Platform Submit job can be rerun.

2.7 CAL Messages
CAL2X009E –CAL2X016E
CAL2X009E One or more Parameters in error - process aborted.

Explanation: One or more parameters supplied to the CA-7 Cross-Platform submission process
were in error.
User Response: The submission process will be UNSUCCESSFUL. See the messages describing
the specific errors encountered. Once the parameter(s) have been corrected, the CA-7 Cross-Platform
Submit job can be rerun.
CAL2X010W SUBPASS from ssssssss ignored : NOT FROM SAME SOURCE AS SUBUSER
Explanation: The SUBPASS parameter was obtained from the source ssssssss (SYSIN or
PROFILE). This is not the same source as the SUBUSER parameter in effect. The SUBPASS
parameter will be ignored and the request will be sent without a password.
User Response: Determine if the password specified in SUBPASS should be used with the request.
If so, it and the SUBUSER parameter must be specified in the same place (for example, both in
SYSIN).
CAL2X011W DOMAIN from ssssssss ignored : NOT FROM SAME SOURCE AS NODE
Explanation: The DOMAIN parameter was obtained from the source ssssssss (SYSIN or
PROFILE). This is not the same source as the NODE parameter in effect. The DOMAIN parameter
will be ignored and the request will be sent without it.
User Response: Determine if the domain specified in DOMAIN should be used with the request. If
so, it and the NODE parameter must be specified in the same place (for example, both in SYSIN).
CAL2X014E Request NOT submitted : Job jjjjjjjj (####) Node nnnnnnnn

Explanation: The CA-7 Cross-Platform submission process was unable to send the request to the
target scheduling system at node nnnnnnnn. The jobname and CA-7 job number indicated by jjjjjjjj
(####).
User Response: See the previous messages for an indication of the specific error encountered.
Once the problem has been addressed the CA-7 Cross-Platform Submit job can be rerun.
CAL2X015E UNABLE TO LOAD MODULE CAL2CCIF. RC=cccc - process aborted.

Explanation: An attempt to load the CA-7 Cross-Platform CAICCI function module CAL2CCIF
failed. The return code from the load call is cccc.
User Response: The submission process will be UNSUCCESSFUL. Confirm that the submission
job is using the correct level of the CA-7 loadlib using STEPLIB or linklist.
CAL2X016E ffffffff DD STATEMENT MISSING - process aborted.

Explanation: The DD statement for the required file ffffffff was not found in the submit job JCL.
User Response: Supply the proper JCL and rerun.

2.7 CAL Messages
CAL2X017E OPEN FAILED FOR ffffffff DD - process aborted.

Explanation: An attempt to open the required file ffffffff was not successful.
User Response: Check the Job Log for related messages. Correct the error and rerun.
CAL2X018E RDJFCB FAILED FOR ffffffff DD - process aborted.

Explanation: An attempt to read the JFCB for required file ffffffff was not successful.
User Response: Check the Job Log for related messages. Correct the error and rerun.
CAL2X020I Parameters in effect for this execution :

Explanation: This is an informational message indicating that the following messages will describe
the parameters that are in effect for this execution of the CA-7 Cross-Platform submission process.
CAL2X021I pppppppp from ssssssss : ...value...

Explanation: This is an informational message indicating a parameter that is in effect for this exe-
cution of the CA-7 Cross-Platform submission process. The parameter is indicated by pppppppp.
The source for the parameter is indicated by ssssssss (EXECPARM, SYSIN or PROFILE). The first
32 characters of the parameter value are indicated by ...value.... If the value is longer than 32
characters, ...value.... will be followed by ' ...'.
User Response: None. The value for SUBPASS, if specified, will always appear as 14 asterisks
regardless of the length or content of the password.
CAL2X022E CCIF ERROR FUNC=ffff RC=rr CC=cc TEXT=xxxx...xxxx

Explanation: A call to the CAICCI sub-function module has encountered an error. The specific
function being performed is indicated by ffff (INIT, TERM, and so forth). The return code (rr) and
condition code (cc) from the error are also indicated. A text description of the error is indicated by
xxxx..xxxx.
User Response: Take corrective action based upon the error text listed. For example, if CAICCI is
not active start it. If the nature of the problem cannot be determined contact Computer Associates
CAL2X023E CCIF CALL FAILED : FUNC=ffff RC=rr CC=cc

Explanation: A call to the CAICCI sub-function module has encountered an error. The specific
function being performed is indicated by ffff (INIT, TERM, and so forth). The return code (rr) and
condition code (cc) from the sub-function are also indicated.

2.7 CAL Messages
CAL2X030E CA-7 ICMDSECT not present on system - process aborted./

Explanation: The CA-7 Cross-Platform submission process could not locate the CA-7 ICMDSECT
control block on the local system.
User Response: Ensure that CAIRIM has initialized the CA-7 system interfaces on the system
where the submission process is executing. Or, run the submission process on a system where CA-7
or ICOM is already active.
CAL2X031E CA-7 ICMDSECT IS INVALID - process aborted.

Explanation: The CA-7 ICMDSECT control block located on the current system is invalid.
User Response: Ensure that CAIRIM has initialized the CA-7 system interfaces on the system
where the submission process is executing. Or, run the submission process on a system where CA-7
or ICOM is already active.
CAL2X032E SUBMIT CHECK failed for SUBUSER: XXXXXXXX Current User: uuuuuuuu
Explanation: A call to the external security system to check the authority of the user ID the submit
job is running under (uuuuuuuu) to submit on behalf of the SUBUSER user ID (xxxxxxxx) returned
an error code.
User Response: See the CA-7 Security Guide for a discussion of the security requirements for
Cross-Platform submission. Change the external security rules, or change the SUBUSER value or the
user ID under which the submit job executes.
CAL2X033W WARNING: Using id=ROOT may violate security on target system

Explanation: A user ID of ROOT was sent with the request. Since this is a restricted ID on UNIX
systems, it could represent a breach of security.
User Response: If the use of ROOT is correct, no action is needed. However, it is recommended
that ROOT not be used to submit jobs to Unicenter TNG. Misuse of this user ID can have serious
and unexpected consequences. See the parameter SUBROOT to control use of this ID.
CAL2X034E ERROR: Use of id=ROOT not allowed - process aborted.

Explanation: A user ID of ROOT was specified for this request. However, the SUBROOT param-
eter was set to or defaulted to NO so the request will not be honored.
User Response: It is recommended that ROOT not be used to submit jobs to Unicenter TNG.
Misuse of this user ID can have serious and unexpected consequences. If you wish to use ROOT
you must specify SUBROOT=YES in the PROFILE parameters for the submission job.
CAL2X035E EXTRACT of current Userid failed : RC=xx - process aborted.

Explanation: An attempt to extract the user ID of the current environment failed.
User Response: Correct any errors indicated in the Job Log and rerun.

2.7 CAL Messages
CAL2X040I –CAL2X102I
CAL2X040I ssssssss input : xxx...xxx

Explanation: These messages are produced if the trace option has been turned on. A message will
be produced for each line of parameter input read. The source of the input is indicated by ssssssss
(EXECPARM, SYSIN or PROFILE). The actual input is echoed in the area indicated by xxx...xxx.
User Response: These trace messages may be helpful if you are getting a parameter exception error
and are having trouble determining exactly which line is producing the error.
CAL2X041I tttttttttttt : Card length = ccc Total Length = lll

be produced for each line of parameter input which is part of a continuation set and will follow the
CAL2X040I message displaying the line. The message will be identified by 'Continuation' or 'Con-
tinue End' in tttttttttttt to indicate whether the parameter continuation is complete or not. The length
of the parameter value on the current statement is indicated by ccc. The total length of the parameter
value so far (including the current line) is indicated by lll.
User Response: These trace messages may be helpful if you are getting a parameter exception error
and are having trouble determining exactly which line is producing the error.
CAL2X042I CCIF CALL FUNC=fff1 RC=r1 CC=c1 : CCI FUNC=fff2 RC=r2 CC=c2
be produced for each call to the CCI Function module. The current CCI Function module's function
is indicated by fff1. The return code and condition code from the CCI Function module are indicated
by r1 and c1. The CAICCI function is indicated by fff2. The return code and condition code from
CAICCI are indicated by r2 and c2.
User Response: These trace messages may be needed by Computer Associates Technical support to
assist in diagnosing error situations.
CAL2X043I SUBMIT CHECK called for SUBUSER: uuuuuuuu Current User: cccccccc RC=rc
Explanation: This message is produced if the trace option has been turned on and a call is made to
check the current users authority to submit on behalf of the user ID specified in SUBUSER. The
return code from the call is indicated by rc.
CAL2X101I CA-7 CROSS-PLATFORM TRACKING SYSTEM (XTRK) IS INITIALIZING (Vx.y)

Explanation: The initialization process for the CA-7 Cross-Platform Tracker (XTRK) has begun.
The release/version level is indicated by Vx.y.
CAL2X102I CA-7 CROSS-PLATFORM TRACKING SUB-TASK ACTIVE: ttt...ttt

Explanation: The CA-7 Cross-Platform Tracker (XTRK) sub-task ttt...ttt has initialized.

2.7 CAL Messages
CAL2X103I –CAL2X141W
CAL2X103I CA-7 CROSS-PLATFORM TRACKING (XTRK) IS ACTIVE FOR xxxx

Explanation: The CA-7 Cross-Platform Tracker (XTRK) has initialized and is now active. The
value of xxxx indicates the subsystem name for either the production (UC07) or test (UCT7) copy of
CA-7.
CAL2X104I XTRK MONITOR=mmmmmmm LOCAL NODE=nnn...nnn

Explanation: The CA-7 Cross-Platform Tracker (XTRK) has initialized and is now active. This
message indicates the monitor name (mmmmmmm) and the local CAICCI node name (nnn...nnn) that
comprise the local host ID for XTRK.
CAL2X107I CROSS-PLATFORM TRACKING (XTRK) HAS RECEIVED A STOP COMMAND

Explanation: The CA-7 Cross-Platform Tracker (XTRK) has received a stop command either from
an operator command or CA-7 ICOM.
CAL2X108I ALL CA-7 CROSS-PLATFORM TRACKING SUB-TASKS HAVE TERMINATED

Explanation: The CA-7 Cross-Platform Tracker (XTRK) sub-tasks have terminated.
CAL2X109I CA-7 CROSS-PLATFORM TRACKING (XTRK) HAS TERMINATED

Explanation: The CA-7 Cross-Platform Tracker (XTRK) system has completed its termination
process.
CAL2X140W *WARNING* CA-7 XTRK CKPT FILE HOST SYSTEM ID CONFLICT *WARNING*
Explanation: The CA-7 Cross-Platform Tracker (XTRK) has encountered a conflict between the
host system ID in the XTRK Checkpoint file and the host system ID of the current environment.
The host system ID is made up of the monitor name and the local CAICCI node name. This indi-
cates that either the monitor or CAICCI node name has changed, or XTRK has been started using the
wrong Checkpoint file.
User Response: This message will be followed by highlighted messages CAL2X141W and
CAL2X142I.
CAL2X141W xxxx: MONITOR=mmmmmmm NODE=nnn...nnn

Explanation: Two versions of this message will be displayed following CAL2X140W. The
message where xxxx=CKPT indicates the Monitor and CAICCI node name carried in the XTRK
Checkpoint file currently being accessed. The message where xxxx=LOCAL indicates the Monitor
name specified in the current XTRK startup parameters and the CAICCI node name of the local
CAICCI environment.
User Response: These messages will be followed by WTOR message CAL2X142I.

2.7 CAL Messages
CAL2X142I OVERRIDE THE CA-7 XTRK CKPT FILE SYSTEM ID? (REPLY Y FOR YES, ANY
OTHER CHARACTER FOR NO)
Explanation: This WTOR follows messages CAL2X140W and CAL2X141I. This WTOR allows
the operator to either override the XTRK Checkpoint Host System ID and continue processing, or
indicate that the XTRK system should terminate so that the XTRK Checkpoint file is not corrupted.
User Response: This message follows messages CAL2X140W and CAL2X141I. If the CA-7
Monitor name and/or the local CAICCI Node name have been deliberately changed, then reply Y to
this message and the Checkpoint file will be updated with the new local information.
If the CA-7 Monitor name and/or the local CAICCI Node name have not been deliberately changed
then reply with any character other than Y to this message and the XTRK system will terminate.
The most likely reason for this situation is attempting to use the same Checkpoint file for more than
one copy of the Cross-Platform Tracker.
CAL2X150I XTRK COMMAND PROCESSING COMPLETE: ccc...ccc

Explanation: Processing for the XTRK operator command ccc...ccc has completed.
CAL2X151W INVALID XTRK COMMAND IGNORED: ccc...ccc

Explanation: An invalid operator command (ccc...ccc) was passed to the CA-7 Cross-Platform
Tracker (XTRK). The command was ignored.
User Response: If the command was intended for XTRK correct and reissue it.
CAL2X152W XTRK COMMAND PROCESS ERROR: ccc...ccc

Explanation: An error was encountered attempting to process the CA-7 Cross-Platform Tracker
(XTRK) command (ccc...ccc).
User Response: Review any preceding or following messages and take corrective action as indi-
cated by them. If there are no other messages and the problem is impacting normal processing,
contact Computer Associates Technical Support for assistance.
CAL2X154I xxx NODE NAME=

Explanation: This message is issued in response to a NODEN CA-7 Cross-Platform Tracker
(XTRK) command. For each entry in the XTRK node table two of these messages will be issued.
The first where xxx=CCI to indicate the CAICCI node name, and the second where xxx=TNG to
indicate the TNG node name. These names should be the same unless a CAICCI alias is being used.
CAL2X155I NODE STATUS LAST ACTIVITY CHECKPOINT DATE/TIME

Explanation: This message is issued in response to a NODE CA-7 Cross-Platform Tracker (XTRK)
command. This is the title line indicating the information in the columns of message CAL2X156I
which follow.

2.7 CAL Messages
CAL2X156I nnn...nnn ssssssssss yyyy/ddd hh:mm:ss.th yyy2/dd2 hh:mm:ss.th
command. A message is issued for each entry in the XTRK node table where nnn...nnn is the
CAICCI node name, sssssss is the status of the XTRK connection with that node, yy/ddd... is the
date and time of the Last Activity with that node, and yyy2/dd2.... is the Checkpoint date/time for
that node. Possible status values are:
ACTIVE Synchronization complete, active connection.
NO CONTACT
XTRK has not been able to send a record to this node, nor has it ever received a record
from this node.
LOSTCONN
Contact with this node had been established, but has since been lost.
SYNCH XTRK is currently performing Checkpoint Synchronization with this node.
CAL2X157I XTRK xxxx TABLE DOES NOT HAVE ANY ENTRIES.

Explanation: This message is issued in response to a NODE or XEVT SNAP CA-7 Cross-Platform
Tracker (XTRK) command (where xxxx is either NODE or XEVT). There are no entries in the
XTRK Node table or External events to display/snap.
CAL2X158I NO XTRK NODE TABLE ENTRIES MATCH SELECT CRITERIA.

command. However, no XTRK Node table entries match the selection criteria specified on the
command.
CAL2X159I TRACE STATUS: PRT(p) CON(c) PRTDD(dddddddd,ddddd) SNAPDD(sssss,ssss)

Explanation: The CA-7 Cross-Platform Tracker (XTRK) was passed a TRC command. This
message indicates the status of the XTRK Trace facility. The information provided is:
PRT(p) The current print trace code.
CON(c) The current console trace code.
PRTDD(...
The trace print ddname (dddddddd), and the status of the DD (OPEN, CLOSED or
DUMMY).
SNAPDD(...
The trace snap ddname (dddddddd), and the status of the DD (OPEN, CLOSED or
DUMMY).

2.7 CAL Messages
CAL2X160W –CAL2X174W
CAL2X160W UNABLE TO HONOR SNAP COMMAND. SNAP IS CLOSED, OR SNAP DD IS NOT

AVAILABLE.
Explanation: The CA-7 Cross-Platform Tracker (XTRK) received a valid SNAP command.
However, the request could not be satisfied because the XTRK trace SNAP DCB is closed, or the
XSNAP DD is not in the JCL or is dummied.
User Response: Issue the XTRK Trace Status command (TRC with no operands) to determine the
status of the SNAP trace. If it is closed, issue the open command: TRC(OPEN,SNAP) then reissue
the snap request. If the XSNAP DD is dummied, XTRK will have to be terminated, the appropriate
DD statement added to the JCL, and XTRK restarted before the SNAP command can be honored.
CAL2X161W UNABLE TO OBTAIN xxxx LOCK WORD. LOCK BEING FORCED (own/cur).
Explanation: The CA-7 Cross-Platform Tracker (XTRK) message function module could not obtain
the internal lock for the print or snap dd indicated by xxxx, PRT or SNAP). The task-id which owns
the lock is indicated by 'own' and the task-id that is forcing control of the lock is 'cur'. After one
minute the lock is forced.
User Response: Contact Computer Associates Technical support if the message is issued repeatedly.
CAL2X162W cc...cc COMMAND FAILED: xxx...xxx

Explanation: The CA-7 Cross-Platform Tracker (XTRK) rejected an ADDNODE or DELNODE
command (cc...cc). The reason is indicated by xxx...xxx. For ADDNODE, 'NODE ENTRY
ALREADY EXISTS'. For DELNODE, 'NODE NOT FOUND IN TABLE'.
User Response: Check to ensure that your spelling of the node name is correct. Use the NODE
command to list existing entries in the XTRK node table.
CAL2X170I XTRK SYNCHRONIZATION (yyyy/ddd hh:mm:ss.th) NODE=nnn...nnn

Explanation: The CA-7 Cross-Platform Tracker (XTRK) has completed the Checkpoint Synchroni-
zation process with the remote node indicated by NODE=. The Checkpoint date and time used for
Synchronization is indicated by yyyy/ddd hh:mm:ss.th. If synchronization is performed for a node
that has already been synchronized the term 'RE-SYNCH' will appear in the message instead of
'SYNCHRONIZATION'.
CAL2X171I XTRK HAS CONTACTED NODE nnn...nnn

Explanation: The CA-7 Cross-Platform Tracker (XTRK) has sent a record to node nnn...nnn via
CAICCI to attempt to initiate the Cross-Platform Checkpoint Synchronization process with that node.
CAL2X174W XTRK UNABLE TO CONTACT NODE nnn...nnn

Explanation: The CA-7 Cross-Platform Tracker (XTRK) was unable to send a record to node
nnn...nnn via CAICCI to attempt to initiate the Cross-Platform Checkpoint Synchronization process
with that node. XTRK will continue to attempt to contact this node; however, this message will not
be repeated.
User Response: If this node should be connected, check the CAICCI definitions on both the

2.7 CAL Messages
CAL2X177W –CAL2X184W
mainframe and remote systems. If this node is no longer part of the Cross-Platform system, use the
DELNODE command to delete the node and prevent further messages.
CAL2X177W XTRK HAS LOST CONTACT WITH nnn...nnn

Explanation: The CA-7 Cross-Platform Tracker (XTRK) was unable to send a record to node
nnn...nnn even though XTRK had previously communicated with that node. XTRK will continue to
attempt to contact this node; however, this message will not be repeated.
User Response: Check the CAICCI definitions on both the mainframe and remote systems.
CAL2X178W XTRK MGR POSTED WITH UNKNOWN COMMAND CODE

Explanation: The CA-7 Cross-Platform Tracker (XTRK) tracking manager sub-task was posted
with an operator command. However, the command code is not defined to the manager.
CAL2X181I XTRK EXTERNAL EVENT TABLE RE-BUILT. ALL NODES WILL BE

RE-SYNCHRONIZED
Explanation: The CA-7 Cross-Platform Tracker (XTRK) External Event table has been re-defined
because of a BLDXEVT operator command. The XTRK Manager sub-task will be posted to force a
new Checkpoint Synchronization process for each remote node in the XTRK Node table.
CAL2X182W XTRK EXTERNAL EVENT TABLE NOT BUILT: xxx...xxx

Explanation: The CA-7 Cross-Platform Tracker (XTRK) encountered serious error(s) attempting to
build an External Event table from the rules pointed to by the XEVENTS DD statement. The spe-
cific reason is indicated by xxx...xxx.
User Response: If you wish to have External Event definitions, correct the error(s) indicated and
recycle XTRK, or issue the BLDXEVT command.
CAL2X183W XTRK EXTERNAL EVENT TABLE DOES NOT HAVE ANY ENTRIES.
Explanation: This message is issued in response to an XEVT or SNAP CA-7 Cross-Platform
Tracker (XTRK) command. There are no entries in the XTRK External Event table to display/snap.
CAL2X184W NO XTRK EXTERNAL EVENT TABLE ENTRIES MATCH SELECT CRITERIA.

Explanation: This message is issued in response to an XEVT or SNAP CA-7 Cross-Platform
Tracker (XTRK) command. However, no XTRK External Event table entries match the selection
criteria specified on the command.

2.7 CAL Messages
CAL2X185I TRIGID TYPE XEVENT ENTRY INFORMATION

Explanation: This message is issued in response to an XEVT CA-7 Cross-Platform Tracker
(XTRK) command. This is the title line indicating the information in the columns of message
CAL2X186I which follow.
CAL2X186I tttttttt xxx = iii...iii

Explanation: This message is issued in response to an XEVT CA-7 Cross-Platform Tracker
(XTRK) command. A set of these messages will be issued for each entry in the XTRK External
Event table. Where:
tttttttt Is the trigger ID for the event
xxxx Is the keyword for the information listed
iii...iii Is information from the table entry
CAL2X199I VALID CMDS ARE: STOP,ADDNODE,BLDXEVT,DELNODE,NODE,NODEN,NODEX,

PING,SNAP,TRC AND XEVT
Explanation: An invalid operator command (ccc...ccc) was passed to the CA-7 Cross-Platform
Tracker (XTRK). The command was ignored.
User Response: This message lists the valid XTRK command verbs. See the CA-7 Interfaces
Guide for detailed information on XTRK commands and their syntax.
CAL2X201I XTRK FBK xxxxxxxx (yyyy/ddd hh:mm:ss.th) tttttttt iii...iii nnn...nnn

Explanation: A Feedback event was received by the CA-7 Cross-Platform Tracker (XTRK).
Where:
xxxxxxxx Indicates whether the feedback was processed, in error, and so forth...
yyyy/ddd...
Is the date and time in the event
tttttttt Is the type of feedback event (JOBINITU, JOBTERMU, and so forth)
iii...iii Is the job name or file name from the feedback
nnn...nnn Is the CAICCI node that sent the feedback
CAL2X202E XTRK FBK RECORD FORMAT ERROR: xxx...xxx REC=rrr...rrr NODE=nnn...nnn

Explanation: A Feedback record received by the CA-7 Cross-Platform Tracker (XTRK) was in
error. Where:
xxx...xxx Indicates the specific error:
'INVALID RECTYPE'
'INVALID BLKSIZE'

2.7 CAL Messages
'INVALID LRECL '

'BAD DATE/TIME '
'PREPERR: xxxx '
REC= Is the first 16 characters of the feedback record
NODE= Is the CAICCI node that sent the feedback
CAL2X301I CA-7 SMF REC: SMF=xx(tttttttt) SVC=xx (.UNI) iii...iii

Explanation: A CA-7 pseudo-SMF record was generated based on information in a Cross-Platform
Feedback record. Where:
SMF=xx Is the SMF record type (in hex) and a literal
'STEPTERM'
'JOBTERM'
'DSCLOSE'
'JOBINIT'
SVC= Is the return code from the CA-7 SVC
.UNI Is either '7UNI' for CA-7 Cross-Platform jobs, or 'XUNI' for CA-7 Cross-Platform
External tracking jobs/data sets
iii...iii Is the related job name or data set name
CAL2X372I SETUP REQUEST FROM NODE nnn...nnn

Explanation: A request to initiate Checkpoint Synchronization (1 rec) was received by the CA-7
Cross-Platform Tracker (XTRK). The CAICCI node requesting setup is indicated by nnn...nnn.
CAL2X374I XTRK RECEIVED UNKNOWN RECTYPE: rrrrrrrr/nnn...nnn

Explanation: An unknown record type was received by the CA-7 Cross-Platform Tracker (XTRK).
The first 8 characters of the record are indicated by rrrrrrrr. The CAICCI node which sent the record
is indicated by nnn...nnn.
CAL2X400I XTRK SYSTEM ENTERED IN xxx..xxx

Explanation: This message indicates the mode that the CA-7 Cross-Platform Tracker (XTRK) was
entered in. The value xxx...xxx will be 'SUB-PGM MODE' if XTRK is running under CA7ICOM, or
'STC/JOB MODE' if XTRK is running as an independent job or started task.

2.7 CAL Messages
CAL2X450I (ttt) TABF EXIT: FUNC=ffff RC=rrrr CC=cccccccc

Explanation: This message indicates an exit from the CA-7 Cross-Platform Tracker (XTRK) Node
Table function module. Where:
ttt Is the taskid which called the function
ffff Is the function code for the call
rrrr Is the return code for the call (R15)
ccc... Is the condition code for the call (R0)
CAL2X451I (TAB) CKPF CALL: FUNC=ffff RC=rrrr CC=cccccccc

Explanation: This message indicates a return from a call by the CA-7 Cross-Platform Tracker
(XTRK) Node Table function module to the Checkpoint file function module. Where:
CAL2X452I (tid) CCIF CALL: FUNC=ffff RC=rr CC=cc:

CCI FUNC=f2f2 RC=r2 CC=c2 (r/nnnnnnnn)
Explanation: A CA-7 Cross-Platform Tracker (XTRK) task has called the CCI sub-function
module. The calling task is identified by tid. The specific function (INIT, TERM, and so forth) is
indicated by ffff. The return code (rr) and condition code (cc) are also indicated. The specific
CAICCI function performed is indicated by f2f2 and the CAICCI return code (r2) and condition code
(c2) are also indicated. If the specific function is a Receive Completion (RCMP) or send (SEND or
SNDX) the first byte of the record received or sent (record type) and the related CAICCI node are
indicated by (r/nnnnnnnn).
CAL2X471I MGR POSTED FOR COMMAND

Explanation: This message indicates that the XTRK Manager task has been posted for special proc-
essing.
CAL2X472I (MGR) PERFORMING PING LOOP PROCESS

Explanation: This message indicates that the XTRK Manager task has initiated the process where
an attempt is made to send each CAICCI node in the XTRK node table either a setup record (4) or
dummy record (0).

2.7 CAL Messages
CAL2X475I (MGR) CCI RECEIVE RTN ENTERED

Explanation: This message indicates that the XTRK Manager task has received a record from
CAICCI.
CAL2X480I (ttt) EVTF EXIT: FUNC=ffff RC=rc CC=cccccccc

Explanation: This message indicates an exit from the CA-7 Cross-Platform Tracker (XTRK)
External Event Table function module. Where:
ttt Is the taskid which called the function
CAL2X801E SYNTAX ERROR NEAR LINE llll COLUMN cc CODEx

Explanation: A syntax error was detected while processing a rule in the CA-7 Cross-Platform
Tracker (XTRK) External Events file (XEVENTS DD). The syntax error was detected near line llll,
column cc. The code is for internal debugging purposes. Processing continues with the next external
event rule.
User Response: Correct the syntax error(s) on the indicated line(s) and either terminate and restart
XTRK, or issue the BLDXEVT command to rebuild the External Events table.
CAL2X802E PREMATURE EOF WHILE PROCESSING DATA, LINE lllll

Explanation: An incomplete EVENT( was detected while processing the Cross-Platform Tracker
(XTRK) External Events file (XEVENTS DD). The error was detected near line llll. Processing
continues with the next external event rule.
CAL2X803E PREMATURE EOF, LINE lllll

Explanation: An incomplete EVENT( was detected while processing the Cross-Platform Tracker
(XTRK) External Events file (XEVENTS DD). The error was detected near line llll. Processing
continues with the next external event rule.

2.7 CAL Messages
CAL2X804E ERROR NEAR LINE lllll COLUMN cc: xxx...xxx

Explanation: A syntax or logic error was detected while processing the Cross-Platform Tracker
(XTRK) External Events file (XEVENTS DD). The error was detected near line llll column cc. The
specific nature of the error is indicated by the text xxx...xxx. Processing continues with the next
external event rule.
CAL2X900W CA-7 XTRK WAITING FOR ENF/CCI TO BECOME ACTIVE.

Explanation: This message is issued as a non-deletable WTO to the master console. The CA-7
Cross-Platform Tracker (XTRK) has detected that the CAIENF (Event Notification Facility) and/or
CAICCI (Common Communications Facility) are not active on the local system. If the XTRK sub-
tasks were already active they will be terminated. No cross-platform communication occurs while
XTRK is in this state.
XTRK will check for ENF/CCI availability every two minutes until they become active or XTRK is
shut down. In either case, this WTO is deleted from the master console.
User Response: Check the system for the CAIENF started task (default name=ENF). Check the
console log for any messages indicating a problem with CAIENF and/or CAICCI.
Start the CAIENF task. If CAIENF activation is successful, it causes CAICCI to be initialized also.
The next time XTRK checks for ENF/CCI availability, it detects them and starts the XTRK subtasks
to perform the CA-7 Cross-Platform Tracking functions.
CAL2X901W CA-7 XTRK WAITING FOR CA-7 CAS9 INITIALIZATION.

Explanation: This message is issued as a non-deletable WTO to the master console. The CA-7
Cross-Platform Tracker (XTRK) has detected that the CA-7 SMF and SVC interfaces have not been
initialized on the local system. These interfaces are initialized using the CAIRIM CAS9 initialization
procedure. If the XTRK subtasks were already active, they are terminated. No cross-platform com-
munication occurs while XTRK is in this state.
XTRK checks for CA-7 CAS9 initialization every two minutes until it detects them or XTRK is shut
down. In either case, this WTO is deleted from the master console.
User Response: Run the CAIRIM CAS9 procedure to initialize the CA-7 SMF and SVC interfaces
on the local system. See the CA-7 Systems Programmer Guide for specific information on CA-7 and
CAIRIM.
The next time XTRK checks for CA-7 interface initialization, it detects them and starts the XTRK
subtasks to perform the CA-7 Cross-Platform Tracking functions.
CAL2X902E INVALID PARAMETER STARTING WITH (xxx..xxx) - ABORTING

Explanation: An invalid parameter was passed to the CA-7 Cross-Platform Tracker (XTRK). The
value in error is indicated by xxx...xxx.
User Response: Correct the parameter error and restart XTRK.

2.7 CAL Messages
CAL2X903E INVALID TRACE CODE(S) SPECIFIED - ABORTING

Explanation: An invalid parameter was passed to the CA-7 Cross-Platform Tracker (XTRK). The
value in error is the trace codes which must be two numeric digits.
User Response: Correct the parameter error and restart XTRK. See the CA-7 Interfaces Guide for
information on XTRK trace codes.
CAL2X904E UNABLE TO LOAD MODULE mmm..mmm . RC=rrrr

Explanation: The CA-7 Cross-Platform Tracker (XTRK) was unable to load module mmm...mmm.
The return code from the LOAD macro is indicated by rrrr.
User Response: Ensure that the CA-7 load library (CAILIB) is specified in the STEPLIB or
LINKLIST concatenation. Also, ensure that there is sufficient REGION available for processing.
Restart XTRK.
CAL2X905E XTRK SUB-TASK ENDED PREMATURELY: tttttttt (mmmmmmmm) TCBCMP=xxxxxxx

Explanation: A CA-7 Cross-Platform Tracker (XTRK) subtask terminated outside of normal shut-
down processing. The title of the subtask is indicated by ttttt and the module name is indicated by
mmmmmmmm. The task completion code is indicated by cccccc. This message may be preceded
by other messages indicating the nature of the error. The XTRK system shuts down any other sub-
tasks which are active.
User Response: Review any preceding or following messages and take corrective action if needed.
If there are no other messages, contact Computer Associates Technical Support for assistance.
CAL2X906E SUBTASK HAS NOT RESPONDED TO TERM CALL: xxx...xxx

Explanation: A CA-7 Cross-Platform Tracker (XTRK) subtask has not responded to a termination
signal during normal shutdown processing. The title of the subtask is indicated by xxx...xxx. The
subtask will be forced to terminate (detached) by the main task and XTRK termination processing
will proceed.
User Response: Review any preceding messages and take corrective action indicated by them. If
there are no other messages, contact Computer Associates Technical Support for assistance.
CAL2X907E ERROR RETURN FROM ATTACH FOR xxxxxxxx RC=rrrr

Explanation: The CA-7 Cross-Platform Tracker (XTRK) was unable to attach a subtask during
initialization processing. The module being attached is indicated by xxxxxxxx. The return code
from the attach process is indicated by rrrr. The XTRK system will terminate with a return code of
12.
User Response: One possible reason for this error is insufficient storage. Try increasing the region
XTRK is running in. If this does not correct the problem, contact Computer Associates Technical
Support for assistance.

2.7 CAL Messages
CAL2X908E –CAL2X911W
CAL2X908E STARTUP OF SUBTASK xxxxxxxx FAILED. COMP=cccccccc

Explanation: A CA-7 Cross-Platform Tracker (XTRK) subtask could not initialize properly. The
subtask module is indicated by mmmmmmmm. The return code from the subtask is cccccccc. The
XTRK system will shut down any active tasks and terminate.
User Response: Review any preceding messages and take corrective actions indicated by them. If
there are no other messages, contact Computer Associates Technical Support.
CAL2X909E SUBTASK HAS NOT RESPONDED TO INIT CALL: xxx...xxx

Explanation: A CA-7 Cross-Platform Tracker (XTRK) subtask did not complete initialization
within two minutes of being engaged. The subtask title is indicated by xxx...xxx. XTRK will shut
down any active tasks and terminate with a return code of 8.
there are no other messages, contact Computer Associates Technical Support.
CAL2X910E XTRK ffff OF dddddddd FAILED. RC=rc CC=cc

Explanation: A CA-7 Cross-Platform Tracker (XTRK) main task call to a subfunction module
failed. The function is indicated by ffff (INIT, TERM, and so forth), the subfunction is indicated by
dddddddddd (TABLE FUNC, TRACE FUNC, and so forth). If the error occurs during initialization
processing, the XTRK system will shut down any active tasks and terminate. If the error occurs
during XTRK command processing, the command will be rejected, and normal processing will con-
tinue.
there are no other messages, and the problem is impacting processing, contact Computer Associates
CAL2X911W XTRK ESTAE ENTERED - WIP=ww (cccc) (pppppppp): ddd........ddd

Explanation: A CA-7 Cross-Platform Tracker (XTRK) main task error routine has been entered for
an abend in its own processing, or the processing of a task above it. The code is indicated by ww.
The abend code is indicated by cccc (hex). The abend PSW is indicated by pppppppp. If the PSW
points to an address within the XTRK main task program it will be in the form of '+ offset'. If not,
it will be the full 8 character PSW. The description of the action being taken is ddd......ddd. If the
recovery routine will attempt to continue processing the description will be 'RETRY IS BEING
ATTEMPTED'.
If the recovery is successful, XPS will continue its normal processing. If the error occurred in the
task which attached XTRK, or the error is persistent, or the error is of a critical nature the description
will be 'ALLOWING ABEND TO PROCEED'. In this case the XTRK system will be terminated
with the original error.

2.7 CAL Messages
CAL2X914E INVALID OR MISSING MONITOR NAME - ABORTING

Explanation: An invalid MONITOR name parameter was passed to the CA-7 Cross-Platform
Tracker (XTRK). Monitor names should be 7 alphanumeric characters. It should match the
MONITOR name being used for CA7TOUNI Cross-Platform jobs that this XTRK system will track.
User Response: Correct the parameter error and restart XTRK. See the CA-7 Interfaces Guide for
information on XTRK parameters.
CAL2X915E MISSING OR INVALID XTRK PARM LIST - ABORTING

Explanation: An invalid parameter list was passed to the CA-7 Cross-Platform Tracker (XTRK).
CAL2X925E XTRK MGR TASK RECEIVED INVALID PARM LIST

Explanation: An invalid parameter list was passed to the CA-7 Cross-Platform Tracker (XTRK)
manager sub-task. The sub-task terminates which will cause XTRK to terminate.
CAL2X926E CA-7 CROSS-PLATFORM TRACKER ALREADY ACTIVE ON THIS SYSTEM

Explanation: CAICCI indicates that there is already a CA-7 Cross-Platform Tracker (XTRK) active
at this CAICCI Node for the Monitor name specified in the XTRK startup parameters. Only one
copy of XTRK can be active for a given monitor name at a given CAICCI Node. The copy of
XTRK issuing this message will terminate.
User Response: Determine where the other copy of XTRK is executing. You may still have a copy
of the pre-Version 3.3 Tracker (CA7FMUNI) executing. If so, stop it and start the XTRK system.
Check to ensure the correct monitor name is specified in the XTRK parameters.
CAL2X927E (ttt) sss ERROR FUNC=ffff RC=rr CC=cc TEXT=xxx...xxx

Explanation: A CA-7 Cross-Platform Tracker (XTRK) subfunction module has encountered an
error. The calling task is identified by tid. The subfunction is indicated by sss (CCI, ENF and so
forth). The specific function being performed is indicated by ffff (INIT, TERM, and so forth. The
return code (rr) and condition code (cc) from the error are also indicated. A text description of the
error is indicated by xxxx....xxxx. The calling XTRK task may or may not terminate processing
based upon the error encountered. Other messages may follow this one.

2.7 CAL Messages
CAL2X928E –CAL2004I
CAL2X928E (tid) ssss ERROR: FUNC=ffff RC=rr CC=cc

internal error. The calling task is identified by tid. The subfunction module is indicated by ssss
(CCIF, ENFF, and so forth). The specific function being performed is indicated by ffff (INIT,
TERM, and so forth). The return code (rr) and condition code (cc) from the subfunction are also
indicated. The calling XTRK task may or may not terminate processing based on the error encount-
ered. Other messages may follow this one.
CAL2X929E XTRK xxxxxxxxxx FUNCTION ERROR: FUNC=ffff RC=rrrr CC=cccc

internal error processing a request from the main task. The subfunction module is indicated by
xxxx... (NODE TABLE, XEVT TABLE, or CA-7 SMF). The specific function being performed is
indicated by ffff (internal numeric function code). The return code (rr) and condition code (cc) from
the subfunction are also indicated. The calling XTRK task may or may not terminate processing
based on the error encountered. Other messages may follow this one.
CAL2001I CA-7 RIM : CA-7 PRODUCTION SYSTEM INITIALIZATION COMPLETE. (SSCT=xxxx)

Explanation: The CA-7 RIM initialization for the Production CA-7 system completed without
errors where xxxx is the CA-7 subsystem name.
CAL2002I CA-7 RIM : CA-7 TEST SYSTEM INITIALIZATION COMPLETE. (SSCT=xxxx)

Explanation: The CA-7 RIM initialization for the Test CA-7 system completed without errors
where xxxx is the CA-7 subsystem name.
CAL2003I CA-7 RIM : CA-7 ALREADY INITIALIZED. NO ACTION TAKEN.

Explanation: CA-7 was initialized during a prior run of RIM. Unless the REINIT parameter is
supplied on the CAIRIM PARM statement, no action is taken.
User Response: If reinitialization is desired, add PARM(REINIT) to the end of the CAIRIM param-
eter statement and rerun RIM. No action is necessary if reinitialization of CA-7 is not desired.
CAL2004I CA-7 RIM : REINIT PARM ACCEPTED. CA-7 WILL BE REINITIALIZED.

Explanation: CA-7 was initialized during a prior run of RIM and the REINIT parameter supplied
on the CAIRIM PARM statement. CA-7 will be reinitialized except for SSCTs and ICMDSECTs.

2.7 CAL Messages
CAL2005I –CAL2012E
CAL2005I CA-7 RIM : ***** ATTN : CA-7 COLD REINIT IN PROGRESS.

Explanation: CA-7 was initialized during a prior run of RIM and the REINIT(COLD) parameter
was supplied on the CAIRIM PARM statement. CA-7 will be initialized, including ICMDSECT and
the CA-7 SSCTs.
User Response: After a CA-7 COLD reinitialization, ICOM must be shut down and restarted to
access the new system component pointers.
CAL2006I CA-7 RIM : CHAINS PARM ACCEPTED. CA-7 SMF AND TRL CHAINS CLEARED.
Explanation: CA-7 was initialized during a prior run of RIM and the CHAINS parameter was sup-
plied on the CAIRIM PARM statement. The CA-7 SMF and Trailer chain headers in the common
storage ICMDSECT will be reset to zero.
CAL2010E CA-7 RIM : CA-7 ALREADY INITIALIZED OUTSIDE OF RIM.

Explanation: CA-7 was initialized, but not through CAIRIM. No action is taken and a return code
of 24 is set. This condition occurs when CA-7 is initialized through statements in the
SYS1.PARMLIB.
User Response: Items related to CA-7 need to be removed from SYS1.PARMLIB and the system
re-IPLed so that RIM can initialize CA-7. See the "Conversion" chapter of the CA-7 Getting Started
guide.
CAL2011E CA-7 RIM : CA-7 RIM INITIALIZATION FAILED - RC=zzz.

Explanation: The CA-7 RIM initialization process failed. This message is preceded by a specific
error message. The return code from this message is passed back to the RIM driver. Possible return
codes for zzz are:
008 = LPA-LOAD failed (msg CAL2013E)

012 = SVC INTERCEPT failed (msg CAL2015E)
016 = SMF EXIT ENGAGE failed(msg CAL2016E)
020 = SSCT definition failed (msg CAL2017E)
024 = already INIT outside RIM (msg CAL2010E)
028 = user parm error (msg CAL2020E)
User Response: See the action described under the specific error message which precedes this
message.
CAL2012E CA-7 RIM : ERROR DURING CA-7 REINIT. NO BACKOUT ACTION TAKEN.
Explanation: An error was encountered during CA-7 reinitialization. No action is taken to back up
CA-7. Some or all portions of CA-7 may not be functional as a result. This message is preceded by
a specific message detailing the error encountered.
User Response: See the action described under the specific error message which precedes this
message.

2.7 CAL Messages
CAL2013E –CAL2017E
CAL2013E CA-7 RIM : *ERROR* LPA LOAD FOR xxxxxxxx FAILED - RC=zzz.
Explanation: An error occurred attempting to load module xxxxxxx and create an LPA CDE for it.
Return code zzz is the reason code passed from MVS module IEWFETCH. This error causes CA-7
initialization to fail with a return code of 8 (message CAL2004E).
User Response: The most common occurrence is a not found condition (RC=004). Ensure the
module listed is in a LINKLIST or CAIRIM step library and rerun the CAIRIM initialization.
CAL2014W CA-7 RIM : * ERROR * LPA LOAD FOR xxxxxxxx FAILED - RC=zzz.
Explanation: An error occurred attempting to load module xxxxxxx and create an LPA CDE for it.
The return code zzz is described in message CAL2005E. The module involved is optional so normal
processing will continue. This error does NOT cause CA-7 initialization to fail.
User Response: Optional modules which may not be installed at your site are UCC7NODE (NCF
module) and IGCS6xxx (RPT interface module). If NCF or RPT is not installed at your site, this
message can be ignored. If NCF or RPT is to be installed and the respective module was not found,
ensure the module is in a LINKLIST or CAIRIM step library and rerun the CA-7 RIM initialization
with a parameter of REINIT.
CAL2015E CA-7 RIM : SVC INTERCEPT FAILED - MOD=xxxxxxxx, SVC=yyy, RC=zzz.

Explanation: An error occurred attempting to dynamically engage the CA-7 SVC module xxxxxxxx
as SVC number yyy. This error causes CA-7 initialization to fail with a return code of 12 (message
CAL2004E).
User Response: Confirm that the SVC number listed is the one assigned for CA-7 and that the
ICMDSECT module has been properly zapped with this number. If the SVC number is correct,
ensure CA-7's first load SVC module has been link edited under the proper name (xxxxxxx). Ensure
this module is in a LINKLIST or CAIRIM step library and rerun the CA-7 RIM initialization.
CAL2016E CA-7 RIM : SMF EXIT INTERCEPT FAILED - Exit=xxxxxxxx, RC=zzz.

Explanation: An error occurred attempting to add CA-7 SMF EXIT xxxxxxxx to the RIM/SMF
Interceptor structure. Possible return codes for zzz are:
004 - Exit already installed. Check to make sure no other SMFI exit has the CA-7 exit name
xxxxxxxx.
008 - Unable to load requested module.
012 - Environmental error. (No CSA available, LOAD error, and so on)
This error causes CA-7 initialization to fail with a return code of 16 (message CAL2004E).
CAL2017E CA-7 RIM : SUBSYSTEM DEFINITION FAILED - SUBYS=xxxx, RC=zzz.

Explanation: An error occurred attempting to define an SSCT for Subsystem xxxx. This error
causes CA-7 initialization to fail with a return code of 20 (message CAL2004E).

2.7 CAL Messages
CAL2020E –CAL2024E
CAL2020E CA-7 RIM : PARAMETER ERROR STARTING WITH 'xxxxxxxx'.

Explanation: The PARM(xxxxxxxx) value on the CA-7 initialization statement is in error. Value
xxxxxxxx is the first 8 characters of the invalid keyword.
User Response: Correct the PARM keyword and rerun CAIRIM. See the CA-7 Systems Pro-
grammer Guide, "CAIRIM Initialization Considerations" section for information on valid parameter
keywords.
CAL2021W CA-7 RIM : REINIT PARM IGNORED. CA-7 NOT YET INITIALIZED.
Explanation: CA-7 has not yet been initialized by CAIRIM; but, a REINIT parameter was specified
on the CA-7 initialization statement.
User Response: Since CA-7 will be initialized for the first time the REINIT PARM will be
ignored. You should check your CAIRIM initialization file and remove the REINIT parameter from
the CA-7 statement. Otherwise, CA-7 will be reinitialized each time you run CAIRIM. See the
CA-7 Systems Programmer Guide, "CAIRIM Initialization Considerations" section.
CAL2022W CA-7 RIM: CHAINS PARM IGNORED. CA-7 NOT YET INITIALIZED.
Explanation: CA-7 has not yet been initialized by CAIRIM, but a CHAINS parameter was speci-
fied on the CA-7 initialization statement.
User Response: Since CA-7 will be initialized for the first time, the CHAINS PARM is ignored.
You should check your CAIRIM initialization deck and remove the CHAINS PARM from the CA-7
statement. Otherwise the CA-7 SMF and Trailer chains are cleared each time you run CAIRIM.
This causes CA-7 to lose tracking for jobs. CA-7 Systems Programmer Guide, "CAIRIM Initializa-
tion Considerations" section for information on valid parameter keywords.
CAL2023E CA-7 RIM: PARAMETER ERROR. COLD SPECIFIED WITHOUT REINIT.

Explanation: The COLD keyword was incorrectly specified in the PARM field on the CA-7 initial-
ization statement.
User Response: No action is taken. If you wish to perform a COLD reinitialization of CA-7, refer
to the CA-7 Systems Programmer Guide, "CAIRIM Initialization Considerations" section for the
proper syntax.
CAL2024E CA-7 RIM: COLD REINIT REQUESTED, BUT CA-7 NOT YET INITIALIZED.
Explanation: CA-7 has not yet been initialized by CAIRIM, but a REINIT(COLD) parameter was
specified on the CA-7 initialization statement.
User Response: NO ACTION IS TAKEN. CA-7 WILL NOT BE INITIALIZED. You should
check your CAIRIM initialization deck and remove the REINIT(COLD) PARM from the CA-7 state-
ment. Rerun CAIRIM to initialize CA-7. You should use COLD reinitializations of CA-7 with
EXTREME CAUTION. See the CA-7 Systems Programmer Guide, "CAIRIM Initialization Consider-
ations" section for information on CA-7 Reinitialization options.

2.7 CAL Messages
CAL2025I –CAL2029W
CAL2025I CA-7 RIM: PREVIOUS RELEASE o.o IS CURRENTLY INSTALLED.

Explanation: The CA-7 CAIRIM initialization module has detected a previous version (o.o) of the
CA-7 system interfaces installed on the system. This message appears if you are upgrading CA-7
versions without an IPL.
User Response: If a REINIT PARM is specified on the CA-7 initialization statement, the previous
version of the CA-7 system interfaces is superseded by the new version (see message CAL2026I
below). If no REINIT PARM is specified, no action is taken (see message CAL2027I below).
CAL2026I CA-7 RIM: PREV RELEASE (o.o) SUPERSEDED BY NEW RELEASE (n.n ).
Explanation: The CA-7 CAIRIM initialization module has detected a previous version (o.o) of the
CA-7 system interfaces installed on the system, and a REINIT PARM is specified on the CA-7
initialization statement.
User Response: The CA-7 system interfaces from the previous CA-7 version are replaced by the
new version CA-7 system interface modules. See the CA-7 Systems Programmer Guide, "CAIRIM
Initialization Considerations" section for information on upgrading CA-7 versions without an IPL.
CAL2027I CA-7 RIM: NO ACTION TAKEN. USE REINIT TO UPGRADE TO NEW RELEASE.
Explanation: The CA-7 CAIRIM initialization module has detected a previous version of the CA-7
system interfaces installed on the system, and a REINIT PARM is NOT specified on the CA-7
initialization statement.
User Response: No action is taken. If you wish to dynamically upgrade to the new CA-7 version,
specify the REINIT PARM on the CA-7 initialization statement. See the CA-7 Systems Programmer
Guide, "CAIRIM Initialization Considerations" section for information on upgrading CA-7 versions
without an IPL.
CAL2028W CA-7 RIM: ERROR IN TEST SETUP. CA-7 TEST SYSTEM SUPPRESSED.
Explanation: The CA-7 CAIRIM initialization module encountered an error attempting to initialize
a test copy of CA-7 on the system. Other error messages may be listed.
User Response: The CA-7 test system is not initialized. The CA-7 production system may, or may
not have initialized properly. Check for other error messages relating to the production system. See
the CA-7 Systems Programmer Guide, "CAIRIM Initialization Considerations" section, and the "Test
Copy of CA-7" section for information on defining and initializing a CA-7 test system.
CAL2029W CA-7 RIM : SVC # xxx ALREADY IN USE ON SYSTEM (CA-7 PROD)
Explanation: CAIRIM attempted to initialize the CA-7 SVC indicated by xxx. The SVC number is
already being used on this system and is not CA-7's SVC or a BR14.
User Response: If there is an entry in IEASVCxx for this SVC number, this message may be
produced. If you are able to determine that the SVC is not in use, a PARM(FORCESVC) can be
added to the CA-7 initialization statement for CAIRIM. This will cause CA-7 to use the specified
SVC number (replacing any current user of that SVC). This option should be used with caution.

2.7 CAL Messages
CAL2030I –CAL2033W
CAL2030I CA-7 RIM : SVC # xxx OVERLAYED BY CA-7 SVC. (CA-7 PROD)
Explanation: The CAIRIM initialization statement for CA-7 had the PARM(FORCESVC) param-
eter coded. This forces the initialization to use the SVC number indicated by xxx even if that SVC
is already being used. The FORCESVC should not be used as the standard way of initializing for
CA-7; it should only be used with caution.
CAL2031E CA-7 RIM: UCC7NODE MODULE IS INVALID.

Explanation: The NCF Node Table module (UCC7NODE) loaded by CAIRIM does not have the
proper format.
User Response: CA-7 HAS NOT BE INITIALIZED. The initialization for CA-7 will fail with a
return code of 8. Check to ensure that the correct copy of UCC7NODE is in the STEPLIB for the
CAS9 procedure. Also, check to ensure that the directory of the load library where the NCF Table
module resides has not been corrupted. Correct the problem and rerun the CAIRIM initialization for
CA-7.
CAL2032E CA-7 RIM: REQUESTED NCF NODE IDENTIFIER IS NOT IN THE UCC7NODE TABLE
Explanation: The NCF node identifier specified on the CAIRIM initialization statement for CA-7
was not found in the UCC7NODE table loaded by CAIRIM.
User Response: CA-7 HAS NOT BE INITIALIZED. The initialization for CA-7 will fail with a
return code of 28 (decimal). Check to ensure that the identifier specified on the NCF(xx) parameter
is correct for this system. If so, check to ensure that the correct copy of UCC7NODE is in the
STEPLIB for the CAS9 procedure. If the table is being loaded from a link-list library, check the
linklist concatenation to ensure no old copies of the table are being accessed. Correct the problem
and rerun the CAIRIM initialization for CA-7.
CAL2033W CA-7 RIM: HOST NCF NODE HAS DEFAULTED TO FIRST ENTRY IN THE NODE
TABLE
Explanation: The first entry in the NCF Node Table (UCC7NODE) is being considered the host
(local) node for this system. This is because no NCF(xx) parameter was entered on the CAIRIM
initialization statement for CA-7, and no entry in the NCF Node Table matched the current systems
SMF ID.
User Response: See the CA-7.SJ message following this one (CA-7.SJ NCF IS PRESENT. LOCAL
NODE = xxxxxxx). If the node specified is correct for this site, no action is necessary. If the node
specified is not correct, check to ensure that the correct copy of NCF Node Table is in the CAS9
STEPLIB. If so, the NCF(xx) parameter may have been omitted from the CAIRIM initialization
statement for CA-7. See the CA-7 Systems Programmer Guide, "CAIRIM Initialization Consider-
ations" section for information on CA-7 CAIRIM parameters. Once you have corrected the source of
the problem, perform a COLD CAIRIM initialization for CA-7 to engage the changes.

2.7 CAL Messages
CAL2034I –CAL2038I
CAL2034I CA-7 RIM: DUMMY NCF NODE TABLE DETECTED. NCF OPTION SUPPRESSED.
Explanation: The NCF Node Table module (UCC7NODE) loaded by CAIRIM is the default
dummy module provided on the CA-7 distribution tape. The NCF option bit in the CSA copy of
ICMDSECT is turned off so that NCF processing will not occur on the system.
User Response: If you are not yet ready to implement your NCF network, no action is necessary.
When you are ready to implement it, refer to USERMOD UL2vm02 (where vm is the current CA-7
version) in the CA-7 Sample JCL library to receive and apply your own copy of the NCF Node
Table. If you have already customized the NCF Node Table check to ensure that the correct copy of
UCC7NODE is in the STEPLIB for the CAS9 procedure. If the table is being loaded from a link-list
library, check the linklist concatenation to ensure an old copy of the table is not being accessed.
CAL2035W CA-7 RIM : SASSXU83 TABLE FORMAT IS INVALID. TABLE IGNORED.

Explanation: The table module SASSXU83 loaded by the CA-7 CAIRIM initialization process does
not have a valid format for such a table module. The table is ignored, and CA-7 initialization proc-
essing continues.
User Response: Ensure that the correct library or libraries are in the CAS9 JCL procedure and/or
link list concatenation. If you think the correct module is being loaded, refer to the CA-7 Systems
Programmer Guide, "User Exits and Modifications" chapter, SMF 14/15 Record Selection Table, for
more information on the correct format of the table. The corrected table can be loaded by running
CAIRIM using a PARM(REINIT) on the CA-7 initialization statement.
CAL2036W CA-7 RIM : SASSEXTL TABLE FORMAT IS INVALID.

Explanation: CAIRIM loaded a SASSEXTL table, but did not find x'FF' terminating the module.
The x'FF' is required to be the last entry in SASSEXTL. No external jobs will be tracked.
User Response: Correct the SASSEXTL module and then run CAIRIM using a PARM(REINIT) on
the CA-7 initialization statement.
CAL2037W CA-7 RIM : SASSXDSN TABLE FORMAT IS INVALID

Explanation: CAIRIM loaded a SASSXDSN table, but did not find the table to have a valid format
(missing eyecatcher or invalid entries in the table). No external data sets will be tracked.
User Response: Correct the SASSXDSN module and then run CAIRIM using a PARM(REINIT) on
the CA-7 initialization statement.
CAL2038I CA-7 RIM: USER TABLE RELOAD REINITIALIZATION COMPLETE.

Explanation: The CA-7 RIM User Table Reload reinitialization process has completed. New
copies of the user table modules have been fetched and addressed in CSA/ECSA.

2.7 CAL Messages
CAL2100I UNAUTHORIZED CA-7 OPERATOR ID

Explanation: A user attempted to log on to CA-7 using an ID that was not defined in the module
that was named on the SECURITY statement in the CA-7 initialization file. The module is named at
the NAME= position on the statement. Issued by SASSSSEC.
User Response: Retry the logon using a different ID or define the ID in the security module.
CAL2101I LOGON FORMAT INCORRECT

Explanation: This message may be issued in the online environment when a /LOGON command is
attempted. The message may be issued in the batch environment in the event that the command
format does not conform to the syntax described for /LOGON in the CA-7 Commands Guide. Issued
by SASSSSEC.
User Response: Correct the command and re-enter.
CAL2102I LOGON REJECTED BY USER EXIT

Explanation: The logon attempt was rejected by SASSXXLX.
User Response: SASSXXLX is a user exit. It is NOT supplied with CA-7. Consult the person
responsible for maintenance of this exit at your site.
CAL2103I USER NOT AUTHORIZED FOR CA-7 COMMANDS

Explanation: The logon attempt was rejected because the user does not have sufficient authority to
execute CA-7 commands. This condition may result even if the USERID is valid in the external
security system (for example, CA-ACF2, CA-TOP SECRET or IBM RACF). If COMMAND was
not specified in the EXTERNAL= sublist on the SECURITY statement in the CA-7 initialization file,
command security will be controlled through the module named by the NAME= keyword on the
SECURITY statement. Issued by SASSSSEC.
User Response: If use of CA-7 commands is to be secured using CA-7 native security, then
USERIDs and security levels must be defined in the CA-7 security module. See the CA-7 Security
Guide for additional information.
CAL2120I UNRECOGNIZED TRANSACTION

Explanation: The command input did not match any entry in SASSTRAN. Issued by SASSSSEC.
User Response: Correct the command input and re-enter.
CAL2122I OPERATOR NOT AUTHORIZED FOR APPLICATION

Explanation: This message is issued when CA-7 native security is being used to control command
access. A command was attempted which belongs to an application which is not associated with the
user in the module named on the NAME= parameter of the SECURITY statement in the CA-7
initialization file. Issued by SASSSSEC.
User Response: If access to the command is needed, contact the person responsible for maintaining
CA-7 security at your site.

2.7 CAL Messages
CAL2124I UNDEFINED TRANSACTION CODE

Explanation: The command input exceeded the maximum length allowable for a CA-7 transaction.
Issued by SASSSSEC.
CAL2140I UNABLE TO LOAD SASSDSCR

Explanation: An error occurred attempting to load SASSDSCR. Issued by SASSSSEC during
panel access validation.
User Response: This is a serious error. Ensure that a usable copy of SASSDSCR resides on a
library accessible by CA-7.
CAL2141I UNRECOGNIZED ACCESS REQUEST

Explanation: A value was entered in the FUNCTION field of a CA-7 panel which was not defined
in SASSDSCR. Issued by SASSSSEC during panel access validation.
CAL2142I INSUFFICIENT AUTHORITY FOR PANEL ACCESS

Explanation: The application access level for the user is insufficient for the type of access
requested. The level associated with the application to which the panel belongs is defined for the
user in the module named by the NAME= keyword on the SECURITY statement in the CA-7 initial-
ization file. Issued by SASSSSEC during panel validation.
User Response: If access to the panel is needed, contact the person responsible for maintaining
CAL2143I PANEL NOT DEFINED

Explanation: Access was requested for a panel that is not defined in SASSDSCR. Issued by
SASSSSEC during panel validation.
CAL2160I DATA SET ACCESS REJECTED (UID)

Explanation: Data set access was denied based on the UID associated with the user in the module
named on the NAME= parameter of the SECURITY statement in the CA-7 initialization file. This
value was compared with the UID values associated with the data set entries in the USERID module.
Issued by SASSSSEC during data set access validation.
User Response: If access to the data set is needed, contact the person responsible for maintaining

2.7 CAL Messages
CAL2170I ACCESS DENIED BASED ON UID

Explanation: Access to database or queue information on the job was denied based on the UID
associated with the user in the module named on the NAME= parameter of the SECURITY statement
in the CA-7 initialization file. This value was compared with the UID value associated with the job
on the DB.1 screen. Issued by SASSSSEC during job access validation.
User Response: If access to the job is needed, contact the person responsible for maintaining CA-7
security at your site.

2.8 CAXPS Messages
CAXPS100I –CAXPS106I
2.8 CAXPS Messages
CAXPS100I XPS HAS ESTABLISHED CONTACT WITH nnnnnnnn/mmmmmmm

Explanation: The Cross-Platform Scheduling Router (XPS) has made contact with another system.
Contact is established when the other system successfully sends a record to XPS for the first time, or,
when the XPS system successfully makes contact because it has feedback data to send to that system.
nnnnnnnn/mmmmmmm indicates the other system's node/monitor.
Explanation: None.
CAXPS101I CROSS-PLATFORM SCHEDULING ROUTER (XPS) IS INITIALIZING

Explanation: The initialization process for the Cross-Platform Scheduling Router (XPS) has begun.
CAXPS102I CROSS-PLATFORM SCHEDULING SUB-TASK ACTIVE: tttttttttttttttt

Explanation: The Cross-Platform Scheduling Router subtask tttttttttttt has been successfully initial-
ized.
CAXPS103I CROSS-PLATFORM SCHEDULING ROUTER (XPS) IS ACTIVE

Explanation: The initialization process for the Cross-Platform Scheduling Router (XPS) has com-
pleted without error. The XPS Router is now functional.
CAXPS104I ALL CROSS-PLATFORM SCHEDULING SUB-TASKS TERMINATED.

Explanation: All of the Cross-Platform Scheduling Router subtasks have been terminated as a part
of the XPS shutdown process.
CAXPS105I CROSS-PLATFORM SCHEDULING ROUTER (XPS) HAS TERMINATED

Explanation: Shutdown of the Cross-Platform Scheduling Router has completed.
CAXPS106I NEW SETUP SYNCH BEING INITIATED: nnnnnnnn/mmmmmmm

Explanation: The Cross-Platform Scheduling Router (XPS) is initiating the checkpoint synchroniza-
tion process because the remote system has explicitly requested it, or because the remote system has
never responded to the setup request record that was previously sent. This usually indicates that the
target system has been recycled. nnnnnnnn/mmmmmmm indicates the target system node/monitor.
User Response: None. The XPS Setup Manager processes the checkpoint synchronization as if it
were a new contact.

2.8 CAXPS Messages
CAXPS120I –CAXPS122W
CAXPS120I XPS PASSWORD REQUIREMENT TABLE BUILT.

Explanation: The Cross-Platform Scheduling Router (XPS) has constructed a Password Require-
ment Table based upon the rules defined in the file pointed to by the XPSPSWD DD statement.
CAXPS121W XPS PSWD RQMT TABLE NOT BUILT : iiiiiiiiiiiiiiiiiiiiiiiiiii

Explanation: The Cross-Platform Scheduling Router (XPS) has not constructed a Password
Requirement Table. The reason it has not is described by iiiiiiiiiiiiiii:
XPSPSWD DD DUMMY
DDname XPSPSWD points to a DUMMY file.
XPSPSWD HAS NO VALID RULES
The file pointed to by the XPSPSWD DD does not contain any valid password requirement rules.
Check for preceding messages that may indicate syntax errors in the file.
XPSPSWD FILE OPEN ERROR
XPS encountered an error attempting to open the file pointed to by the XPSPSWD DD.
User Response: If you have not defined any Password Requirement rules, no action is needed. If
the DD statement is missing, add it to the JCL and shut down and restart the XPS environment. If
the Password Requirement rules contain syntax errors, correct the errors, shut down and restart the
XPS environment.
CAXPS122W XPSPSWD ERROR STARTING WITH tttttttttttttttt: iiiiiiiiiiiiiiiiii

Explanation: The Cross-Platform Scheduling Router (XPS) encountered a syntax error while proc-
essing a Password Requirement rule in the file pointed to by the XPSPSWD DD statement. The
error was encountered in the rule text indicated by tttttttttttttttt. The specific reason for the error is
described by iiiiiiiiiii:
UNKNOWN KEYWORD
The text displayed is not a valid Password Requirement rule keyword. Valid keywords are:
NODE=, MONITOR=, ID= and PSWD=.
PARTIAL GENERIC
The keyword value displayed for NODE=, MONITOR= or ID= is partially generic. Values for
these keywords must be specific or fully generic (single *).
VALUE LENGTH ERROR
The keyword value displayed is too long or too short.
INVALID VALUE
The keyword value displayed is not valid for keyword it is associated with.
User Response: Correct all Password Requirement rules which contained errors and shut down and
restart the XPS environment.

2.8 CAXPS Messages
CAXPS148W –CAXPS152W
CAXPS148W (CASH_I_0148) SUBMIT FAILURE FROM monitor CODE=xxxxxxxx

(nnnnnnn/mmmmmmm/jjjjjjjj/eeeeeeeeeeeeee)
Explanation: The Cross-Platform Scheduling Router (XPS) has received a Job Failure tracking
event for a Cross-Platform job indicating a pre-execution error. The value 'monitor' indicates who
generated the Job Failure event. If the monitor name is SUBMITC then the event was generated by
the XPS Router. The requesting node/monitor is indicated by nnnnnnnn/mmmmmmm the requesting
system job name is indicated by jjjjjjjj. The entry number is indicated by eeeeeeeeeeeeee. The
reason for the failure is indicated by CODE=xxxxxxxx. Codes starting with '1-' have been generated
by the XPS Router. Other codes are generated by the target scheduling system(s). Possible codes
are:
1-SUBCRT XPS Router could not locate scheduling system (monitor).
1-NOPSWD Request was received with explicit userid, but there was no password which was
required.
LOGONERR Scheduling system rejected the request because the userid sent with the request was
not recognized or honored. Check to confirm that the userid sent is valid for the
scheduling system, and if a password was sent, that the password is valid.
NOTFOUND Scheduling system rejected the request because the requested job was not defined.
SECURITY Scheduling system rejected the request because of a security error. Check to
confirm that the userid sent with the request has the authority to access the job
requested.
CAXPS150I XPS COMMAND PROCESSING COMPLETE: cccccccc

Explanation: Processing for the Cross-Platform Scheduling Router (XPS) user command cccccccc
has completed.
CAXPS151W INVALID XPS COMMAND IGNORED: cccccccc

Explanation: An invalid user command (cccccccc) was passed to the Cross-Platform Scheduling
Router (XPS). No processing for the command has been performed.
User Response: Correct the command and reissue it.
CAXPS152W XPS COMMAND PROCESS ERROR: cccccccc

Explanation: The Cross-Platform Scheduling Router (XPS) encountered an error while attempting
to process the command indicated by cccccccc.
by them. If there are no other messages and the problem is impacting normal processing, contact
Computer Associates Technical Support for assistance.

2.8 CAXPS Messages
CAXPS153W –CAXPS156I
CAXPS153W KILL COMMAND RECEIVED. S0C1 PROCEEDING

Explanation: The Cross-Platform Scheduling Router (XPS) was passed a KILL command. A
system 0C1 abend will follow which will produce a storage dump for diagnostic analysis.
CAXPS155I NODE MONITOR STATUS FLAGS LAST ACTIVITY REQ CNT FBK CNT
Explanation: The Cross-Platform Scheduling Router (XPS) was passed a NODE command. This is
the column title heading line. It will be followed by one or more CAXPS156I messages displaying
data from the XPS Node table.
Note: The last two columns will only appear if the long version of the command is entered
(NODEL).
CAXPS156I nnnnnnnn mmmmmmm ssssssssss (ffffffff) yyyy/ddd hh:mm:ss:th r,rrr,rrr k,kkk,kkk

Explanation: The Cross-Platform Scheduling Router (XPS) was passed a NODE or NODEL
command. A detail line will be produced for each node/monitor that XPS has had contact with. The
information supplied is:
The CAICCI node (nnnnnnn).
The monitor name (mmmmmmm). This is also sometimes referred to as the application name.
The status of communication with the node/monitor (ssssssssss):
ACTIVE
Checkpoint synchronization with the node/monitor is complete.
LOSTCONN
Communication with the node/monitor has been lost.
NEEDSYNCH
Communication with the node/monitor has been established, but the checkpoint synchronization
process has not yet begun.
SYNCH
Communication with the node/monitor has been established and the checkpoint synchronization
protocol has begun.
SYNCHSEARCH
Communication with the node/monitor has been established, the checkpoint synchronization pro-
tocol has been completed and the XPS Setup Manager is currently searching for any check-
pointed feedback to send.
SYNCHPEND
Communication with the node/monitor has been established, the checkpoint synchronization pro-
tocol has been completed, and the XPS Setup Manager will include this node/monitor in the next
feedback checkpoint search when the current search is completed.

2.8 CAXPS Messages
UNKNOWN
The status of the node/monitor does not fall into a defined category.
The internal flags for this node/monitor from the XPS internal table (ffffffff). These flags may be
needed by Computer Associates Technical Support to assist in diagnosing problem situations.
The date and time of the last activity for this node/monitor (yyyy/ddd hh:mm:ss.th). Last activity is
at the time when a CAICCI record was successfully sent to, or received from the node/monitor.
The number of requests for work (AJBs) received from the node/monitor (r,rrr,rrr) since XPS was
initialized.
Note: This column will only appear if the long version of the command is entered (NODEL).
The number of XPS feedback records sent to the node/monitor (k,kkk,kkk) since XPS was initialized.
Note: This column will only appear if the long version of the command is entered (NODEL).
CAXPS157I XPS tttt TABLE DOES NOT HAVE ANY ENTRIES.

Explanation: The Cross-Platform Scheduling Router (XPS) was passed a NODE or PSWD
command (tttt). For NODE, this message indicates that XPS has not yet established communication
with any node/monitor since it has initialized. For PSWD, this message indicates that no Password
Requirement Table was built at XPS initialization.
CAXPS158W UNABLE TO GET SUFFICIENT STORAGE TO FORMAT tttt DISPLAY

Explanation: The Cross-Platform Scheduling Router (XPS) was passed a NODE or PSWD
command (tttt). This message indicates that XPS was unable to dynamically obtain enough storage
to satisfy the request. The display will not be produced.
User Response: Review the storage specifications for XPS. You may wish to increase the
region/storage specification for the environment where XPS is executing.
CAXPS159I TRACE STATUS : PRT(p) CON(c) PRTDD(dddddddd,sssssss) SNAPDD(dddddddd,sssssss)

Explanation: The Cross-Platform Scheduling Router (XPS) was passed a TRC command to list the
status of the XPS Trace facility. The information provided is:
PRT(p)
The current print trace code.
CON(c)
The current console trace code.
PRTDD(...
The trace print DD name (dddddddd), and the status of the DD (OPEN, CLOSED or DUMMY).
SNAPDD(...
The trace snap DD name (dddddddd), and the status of the DD (OPEN, CLOSED or DUMMY).

2.8 CAXPS Messages
CAXPS160W –CAXPS201I
CAXPS160W UNABLE TO HONOR SNAP COMMAND. SNAP IS CLOSED, OR SNAP DD IS NOT

AVAILABLE
Explanation: The Cross-Platform Scheduling Router (XPS) received a valid SNAP command.
However, the request could not be satisfied because the XPS trace SNAP dcb is closed, or the SNAP
DD is not in the JCL or is dummied.
User Response: Issue the XPS Trace Status command (TRC with no operands) to determine the
status of the SNAP trace. If it is closed, issue the open command: TRC(OPEN,SNAP). Then reissue
the snap request. If the SNAP DD is dummied then XPS will have to be terminated, the appropriate
DD statement added to the JCL and XPS restarted before the SNAP command can be honored.
CAXPS161W UNABLE TO OBTAIN llll LOCK. LOCK BEING FORCED (own/cur)

Explanation: The Cross-Platform Scheduling Router (XPS) message function module was unable to
obtain the internal lock for the print or snap DD (indicated by llll, PRT or SNAP). The task-id
which owns the lock is indicated by 'own' and the task-id that is forcing control of the lock is 'cur'.
After one minute the lock will be forced.
User Response: Contact Computer Associates Technical support if the message is issued repeatedly.
CAXPS162I NODE MONITOR USER-ID PSWD REQUIRED

Explanation: The Cross-Platform Scheduling Router (XPS) was passed a PSWD command. This is
the column title heading line. It will be followed by one or more CAXPS163I messages displaying
data from the Password Requirement table.
CAXPS163I nnnnnnnn mmmmmmm uuuuuuuu y/n

Explanation: The Cross-Platform Scheduling Router (XPS) was passed a PSWD command. A
detail line will be produced for each entry in the Password Requirement Table. The information
supplied is:
The CAICCI node (nnnnnnn). An entry of '*' indicates it will match any node name.
The monitor name (mmmmmmm) (also sometimes referred to as the application name). An entry
of '*' indicated it will match any monitor name.
The user ID (uuuuuuuu) which will be passed with a job request from another system. An entry
of '*' indicated it will match any user ID.
The indication of whether a job request matching this entry must have a password if a specific
user ID is passed with the request (YES), or that a password is optional with such a request
(NO).
CAXPS201I SETUP REC SENT TO nnnnnnnn/mmmmmmm

Explanation: The Cross-Platform Scheduling Router (XPS) has sent a setup record to CAICCI
Node nnnnnnnn, Monitor name mmmmmmm, to begin feedback checkpoint synchronization.

2.8 CAXPS Messages
CAXPS202I SETUP RESPONSE FROM nnnnnnnn/mmmmmmm (yyyydddhhmmssth)

Explanation: The Cross-Platform Scheduling Router (XPS) has received a setup response from
CAICCI Node nnnnnnnn, Monitor name mmmmmmm, to begin feedback checkpoint synchronization.
The date and time (yyyydddhhmmssth) reflects the last feedback record XPS sent to that
node/monitor.
CAXPS203W UNKNOWN NODE SENT REC TO MGR: nnnnnnnn/cccccccccccccccccccc REC=rrrrrrrr

Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager task has received a
CAICCI record from a node which is not known to XPS. The CAICCI sender is node nnnnnnnn,
CCI application name cccccccccccccccccccc. The first eight characters of the record received are
shown as rrrrrrrr. The record is ignored.
CAXPS204W MGR RECEIVED UNKNOWN RECTYPE nnnnnnnn/mmmmmmm REC=rrrrrrrr

CAICCI record which has an invalid record type code. The CAICCI sender is node nnnnnnnn,
monitor name mmmmmmm. The first eight characters of the record received are shown as rrrrrrrr
(the first character is the record type code). The record is ignored.
CAXPS205W MGR NON-SEQ SITUATION: NODE=nnnnnnnn/mmmmmmm FLAGS=ff REC=r

CAICCI record which is not in the correct sequence based upon the previous records received from
this node/monitor. The CAICCI sender is node nnnnnnnn, monitor name mmmmmmm. The XPS
internal flag byte indicating the status of the dialog with this node/monitor is represented by ff. The
first character of the record received (record type code) is shown as r. The record is ignored.
CAXPS206I tid SENT: tttttttt (nnnnnnnn/mmmmmmm/jjjjjjjj/eeeeeeeeeeeeee)

Explanation: A Cross-Platform Scheduling Router (XPS) task has sent a Feedback record to the
target node/monitor. The task-id is indicated by tid. The type of feedback is indicated by tttttttt.
The target system node/monitor is indicated by nnnnnnnn/monitor. The first eight bytes of the target
system job name is indicated by jjjjjjjj. The entry number assigned by the target system is indicated
by eeeeeeeeeeeeee.

2.8 CAXPS Messages
CAXPS207W tid HAS LOST CONTACT WITH nnnnnnnn/mmmmmmm

Explanation: A Cross-Platform Scheduling Router (XPS) task has lost contact with a target system.
If the task (tid) is MGR then contact was lost during Checkpoint synchronization processing. If the
task (tid) is TKS then contact was lost when attempting to send real-time feedback. The target
system node/monitor is indicated by nnnnnnnn/mmmmmmm.
User Response: None. XPS will automatically initiate checkpoint synchronization when contact
with the target node/monitor is re-established.
CAXPS208W UNKNOWN CCI BLOCK FROM nnnnnnnn IGNORED. REC=rrrrrrrrrrrrrrrr

Explanation: The Cross-Platform Scheduling Router (XPS) Submit Server task has received a
CAICCI record which has an invalid record type code or has a valid code but invalid record format.
The record was sent from CAICCI node nnnnnnnn. The first sixteen characters of the record
received are shown as rrrrrrrrrrrrrrrr (the first character is the record type code). The record is
ignored.
CAXPS209W BAD AJB RECEIVED FROM nnnnnnnn/mmmmmmm RC=rr CC=cc

request for work (AJB) which has invalid data or an invalid format. The CAICCI sender is node
nnnnnnnn, monitor name mmmmmmm. The return code (rr) and condition code (cc) from the AJB
validation subroutine is listed. The request is ignored.
CAXPS210I AJB TO sssssss (nnnnnnnn/mmmmmmm/jjjjjjjj/eeeeeeeeeeeeee) (ffffffffffffffffffff)

request for work (AJB) which has been forwarded to scheduling system (sssssss) at the local node.
The requesting node/monitor is indicated by nnnnnnnn/mmmmmmm. The first eight bytes of the
requesting system job name is indicated by jjjjjjjj. The entry number assigned by the requesting
system is indicated by eeeeeeeeeeeeee. The first 20 bytes of the submission filename field (MVS job
to be executed) are indicated by ffffffffffffffffffff.
CAXPS211W ROUTE FAILED TO sssssss (nnnnnnnn/mmmmmmm/jjjjjjjj/eeeeeeeeeeeeee)

request for work (AJB) and attempted to forward it to scheduling system (sssssss) at the local node.
The attempt to forward the request was not successful. The requesting node/monitor is indicated by
nnnnnnnn/mmmmmmm. The first eight bytes of the requesting system job name is indicated by
jjjjjjjj. The entry number assigned by the requesting system is indicated by eeeeeeeeeeeeee.
A submission failure feedback event is automatically generated by the Submit Server and routed back
to the requesting system. The failure code for the job is '1-SUBCRT'.
User Response: Confirm that the monitor name listed (sssssss) is the correct name for the sched-
uling system you want to send the request to. If it is correct, confirm that the scheduling system is

2.8 CAXPS Messages
ready to accept requests. If it is not correct, check the job definition on the XPS Client and change
the MONITOR= keyword in the Submit File definition to the correct monitor name.
CAXPS212W FBK SEND FAILED tttttttt yyyy/ddd hh:mm:ss.th

nnnnnnnn/mmmmmmm/jjjjjjjj/eeeeeeeeeeeeee
Explanation: The Cross-Platform Scheduling Router (XPS) Tracking Sender attempted to send an
XPS feedback record using CAICCI. The attempt to forward the feedback was NOT successful. The
type of feedback is indicated by tttttttt. The date and time of the feedback event is indicated by
yyyy/ddd hh:mm:ss.th. The target system node/monitor is indicated by nnnnnnnn/mmmmmmm. The
first eight bytes of the target system job name is indicated by jjjjjjjj. The entry number assigned by
the target system is indicated by eeeeeeeeeeeeee.
User Response: None. When contact with the target system is re-established, this feedback record
will be sent as part of the automatic checkpoint synchronization processing.
CAXPS213W TKS HAS LOST CONTACT WITH nnnnnnnn/mmmmmmm

Explanation: The Cross-Platform Scheduling Router (XPS) Tracking Sender task has lost contact
with a target system while attempting to send an XPS feedback record. The target system
node/monitor is indicated by nnnnnnnn/mmmmmmm.
User Response: None. XPS will automatically initiate checkpoint synchronization when contact
with the target node/monitor is re-established. This will cause any pending feedback to be sent to the
target system.
CAXPS214W SEND OF SETUP REC FAILED - RECVR NOT FOUND - nnnnnnnn/mmmmmmm

Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager task attempted to send a
Setup Record to the target system to initiate a checkpoint synchronization session. The target system
node/monitor is indicated by nnnnnnnn/mmmmmmm.
User Response: None. The XPS Setup Manager will continue to attempt to establish contact with
the target system. However, this message will only be issued once for a given target system. Once
contact is established, a checkpoint sychronization session will be initiated.
CAXPS215W PSWD CHECK FAILED FOR (nnnnnnnn/mmmmmmm/jjjjjjjj/eeeeeeeeeeeeee)

request for work (AJB) that includes a user ID but does not have an associated password. The XPS
Password Requirement Table has an entry which matches on this request and indicates that a pass-
word is required if a user ID is sent. The requesting node/monitor is indicated by nnnnnnnn/
mmmmmmm. The first eight bytes of the requesting system job name is indicated by jjjjjjjj. The
entry number assigned by the requesting system is indicated by eeeeeeeeeeeeee.
A submission failure feedback event is automatically generated by the Submit Server and routed back
to the requesting system. The failure code for the job is '1-NOPSWD'.
User Response: In the job definition on the XPS Client, add the password that matches the user ID
associated with the job to the definition and re-submit the request.

2.8 CAXPS Messages
CAXPS301I FBK EVENT tttttttt nnnnnnnn/mmmmmmm/jjjjjjjj/eeeeeeeeeeeeee yyyy/ddd hh:mm:ss.th

Explanation: The Cross-Platform Scheduling Router (XPS) Tracking Sender has been passed an
XPS feedback record from the local CA-ENF system. The type of feedback is indicated by tttttttt.
The target system node/monitor is indicated by nnnnnnnn/mmmmmmm. The first eight bytes of the
target system job name is indicated by jjjjjjjj. The entry number assigned by the target system is
indicated by eeeeeeeeeeeeee. The date and time of the feedback event is indicated by yyyy/ddd
hh:mm:ss.th.
User Response: None. The XPS Tracking Sender will forward the feedback record to the target
Router if communication with that system is active. Otherwise, this feedback record will be sent as
part of the automatic checkpoint synchronization processing when contact is established.
CAXPS302W INVALID FBK EVENT: dddddddddddd: nnnnnnnn/mmmmmmm (yyyydddhhmmssth) tttttttt

Explanation: The Cross-Platform Scheduling Router (XPS) Tracking Sender or Setup Manager task
has been passed an invalid XPS feedback record from the local CA-ENF system. A description of
the specific error is indicated by dddddddddddd. The target system node/monitor is indicated by
nnnnnnnn/mmmmmmm. The date and time of the feedback event is indicated by yyyydddhhmmssth.
The type of feedback is indicated by tttttttt.
CAXPS304I NEW CKPT SEARCH FOR nnnnnnnn/mmmmmmm (yyyydddhhmmssth)

Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager has completed the
checkpoint synchronization setup protocol with target system nnnnnnn/mmmmmmm. A checkpoint
search has been initiated to collect and forward any feedback information that has been generated,
but not yet sent to the target system. The starting date/time for the search is indicated by
yyyydddhhmmssth.
CAXPS305I ADD TO SEARCH FOR nnnnnnnn/mmmmmmm (yyyydddhhmmssth)

search is already in progress to collect and forward any feedback information that has been gener-
ated, but not yet sent to the target system(s). The starting date/time for this system is indicated by
yyyydddhhmmssth. Since the current search has not yet reached this starting point, this system is
being added to the search already in progress.

2.8 CAXPS Messages
CAXPS306I SEARCH PENDING FOR nnnnnnnn/mmmmmmm (yyyydddhhmmssth)

search is already in progress to collect and forward any feedback information that has been gener-
ated, but not yet sent to the target system(s). The starting date/time for this system is indicated by
yyyydddhhmmssth. Since the current search has already passed this starting point, this system is put
into 'search pending' status.
User Response: None. When the current checkpoint search is completed, a new search will be
initiated to include this node/monitor along with any others which are in 'search pending' status.
CAXPS307I CKPT SYNCH COMPLETE FOR nnnnnnnn/mmmmmmm (yyyydddhhmmssth)

checkpoint search for any historical feedback not yet sent to the target system. The feedback event
which marks the end of the search is indicated by yyyydddhhmmssth. If the date and time are all
zeros, it indicates that the target system did not pass a checkpoint date/time; therefore, no search was
done.
User Response: None. Any new feedback generated for this system will be sent by the Tracking
Sender task.
CAXPS308I NEW CKPT SEARCH FOR PENDING ENTRIES (yyyydddhhmmssth)

Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager has detected that one or
more target systems need to have a new checkpoint synchronization search initiated. A new search is
started to include all pending target systems. The starting point for the search is indicated by
yyyydddhhmmssth.
CAXPS400I XPS SYSTEM ENTERED IN mmmmmmmm MODE

Explanation: The Cross-Platform Scheduling Router (XPS) was initiated in the indicated mode
(mmmmmmmm). A mode of STC/JOB indicates XPS is running as an MVS Started Task or JOB.
A mode of SUB-PGM indicates XPS was attached by another process.
CAXPS401I MGR POSTED FOR CONNECT

Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager has been posted to
check the internal node/monitor table and attempt to initiate checkpoint synchronization for any target
systems that require it.

2.8 CAXPS Messages
CAXPS402I MGR PERFORMING TIMER STATUS CHECK

Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager is performing an
internal status check. Such checks are performed if no other activity causes the Setup Manager to
awaken for a set period of time.
CAXPS403W MGR CHECKING MGR AND TKS EVENT COUNTS

Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager is checking for a mis-
match in the posting of CA-ENF events for itself and the Tracking Sender task.
User Response: None. If the mismatch persists, the Setup Manager takes action to reset the
CA-ENF thread it is using (see messages CAXPS404W and CAXPS931W).
CAXPS404W MGR AND TKS EVENT COUNTS DO NOT AGREE: m,mmm,mmm / t,ttt,ttt
Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager has detected a mismatch
in the posting of CA-ENF events for itself and the Tracking Sender task. The manager task counter
is indicated by m,mmm,mmm and the tracking task counter is indicated by t,ttt,ttt.
User Response: None. If the mismatch persists, the Setup Manager takes action to reset the
CA-ENF thread it is using (see message CAXPS931W).
CAXPS405I MGR CCI RECEIVE RTN ENTERED

Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager CAICCI Receive proc-
essing routine has been entered.
CAXPS406I MGR POSTED FOR ENF EVENT yyyydddhhmmssth tttttttt nnnnnnnn/mmmmmmm

Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager ENF Event processing
routine has been entered. The date and time of the event is yyyydddhhmmssth. The type of event
record is tttttttt. The node and monitor name of the target system for the event is
nnnnnnnn/mmmmmmm.
CAXPS407I EVT800 TABLE SCAN ENTERED

Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager has entered the routine
which scans the target system table to determine if the checkpoint synchronization search is complete
for one or more target systems.
CAXPS408I CKPT TABLE SEARCH ENDED - CALLING ENF TO TERM

Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager has determined that the
checkpoint synchronization search is complete for the target system(s) that were being processed.

2.8 CAXPS Messages
CAXPS425I SRV TASK POSTING SETUP MANAGER

Explanation: The Cross-Platform Scheduling Router (XPS) Submit Server task has posted the Setup
Manager task to check the internal Node/Monitor table and attempt to initiate checkpoint synchroni-
zation for any target systems that require it.
CAXPS450I TKS TASK POSTING SETUP MANAGER FOR SYNCH NODE

Explanation: The Cross-Platform Scheduling Router (XPS) Tracking Sender task has posted the
Setup Manager task to check the internal Node/Monitor table and attempt to initiate checkpoint syn-
chronization for any target systems that require it.
CAXPS451I TKS TASK POSTING SETUP MANAGER FOR LOST CONNECT

Explanation: The Cross-Platform Scheduling Router (XPS) Tracking Sender task has posted the
Setup Manager task to check the internal Node/Monitor table and attempt to initiate checkpoint syn-
chronization for a target system that the Tracking Sender has lost contact with.
CAXPS452I (tid) CCIF CALL : FUNC=ffff RC=rr CC=cc : CCI FUNC=f2f2 RC=r2 CC=c2 (r/nnnnnnnn)
Explanation: A Cross-Platform Scheduling Router (XPS) task has called the CCI subfunction
module. The calling task is identified by tid. The specific function being performed is indicated by
ffff (INIT, TERM, and so forth). The return code (rr) and condition code (cc) from the subfunction
are also indicated. The specific CAICCI function performed is indicated by f2f2, and the CAICCI
return code (r2) and condition code (c2) are also indicated. If the specific function is a Receive
Completion (RCMP), the first byte of the record received (record type) and the CAICCI node that
sent the record are indicated by (r/nnnnnnnn).
CAXPS453I (tid) ENFF CALL : FUNC=ffff RC=rr CC=cc : ENF FUNC=f2f2 RC=r2 CC=c2
Explanation: A Cross-Platform Scheduling Router (XPS) task has called the ENF subfunction
module. The calling task is identified by tid. The specific function being performed is indicated by
ffff (INIT, TERM, and so forth). The return code (rr) and condition code (cc) from the subfunction
are also indicated. The specific CA-ENF function performed is indicated by f2f2, and the CA-ENF
return code (r2) and condition code (c2) are also indicated.
CAXPS801I PARMLIST FORMAT IS 'TARGET-NODE,TARGET-MONITOR,START-DATE/TIME

(YYYYDDDHHMMSSTH)'
Explanation: The Cross-Platform Scheduling Router (XPS) Feedback Utility program was invoked
with an invalid parameter list. This message (and CAXPS802I) follows message CAXPS902E and
describes the correct format of the parmameter list.
User Response: Correct the parameter list and resubmit the Feedback Utility JCL.

2.8 CAXPS Messages
CAXPS802I –CAXPS901E
CAXPS802I ALL PARMS ARE OPTIONAL. PARTIAL START DATE/TIME CAN BE SPECIFIED (E.G.
1999063)
Explanation: The Cross-Platform Scheduling Router (XPS) Feedback Utility program was invoked
with an invalid parameter list. This message (and CAXPS801I) follows message CAXPS902E and
describes the correct format of the parmameter list.
User Response: Correct the parameter list and resubmit the Feedback Utility JCL.
CAXPS803I PARMLIST FORMAT IS 'TARGET-CCI-NODE,TARGET-CCI-APPL-NAME'

Explanation: The Cross-Platform Scheduling Router (XPS) CCI Inquiry Utility program was
invoked with an invalid parameter list. This message (and CAXPS804I) follows message
CAXPS902E and describes the correct format of the parameter list.
User Response: Correct the parameter list and resubmit the CCI Inquiry Utility JCL.
CAXPS804I BOTH ARE OPTIONAL. NODE MUST BE SPECIFIC. APPL INTERPRETED AS A PREFIX
Explanation: The Cross-Platform Scheduling Router (XPS) CCI Inquiry Utility program was
invoked with an invalid parameter list. This message (and CAXPS804I) follows message
CAXPS902E and describes the correct format of the parameter list.
If specified, the target CCI node must be a fully qualified name. If specified, the target CCI applica-
tion name will be interpreted as a prefix. That is, if an application name of 'SUBMITC' is specified,
every application which begins with 'SUBMITC' will be listed.
User Response: Correct the parameter list and resubmit the CCI Inquiry Utility JCL.
CAXPS900W XPS ROUTER WAITING FOR ENF/CCI TO BECOME ACTIVE.

Explanation: This message is issued as a non-deletable WTO to the master console. The Cross-
Platform Scheduling Router (XPS) has detected that the CA90s Services CA-ENF (Event Notification
Facility) and/or CAICCI (Common Communications Facility) are not active on the local system. If
the XPS subtasks were already active they will be terminated. No Cross-Platform communication
will occur while XPS is in this state.
XPS will check for ENF/CCI availability every two minutes until they either become available, or
XPS is shut down. In either of these cases, this WTO is deleted from the console.
User Response: Check the system for the CA-ENF started task (default name is ENF). Check the
console log for any messages indicating a problem with CA-ENF and/or CAICCI.
Start the CA-ENF task. If CA-ENF activation is successful, it causes the CAICCI facilities to be
initialized also. The next time XPS checks for ENF/CCI availability, it detects them and starts XPS
subtasks to perform the Cross-Platform Scheduling tasks.
CAXPS901E MISSING OR INVALID XPS PARM LIST - ABORTING

Explanation: The Cross-Platform Scheduling Router (XPS) was engaged from another program,
and the parameter list was either missing or had an invalid format. XPS will terminate with a return
code of 16.

2.8 CAXPS Messages
CAXPS902E –CAXPS907E
CAXPS902E INVALID PARAMETER STARTING WITH (pppppppp) - ABORTING

Explanation: The Cross-Platform Scheduling Router (XPS) was engaged with a parameter list
which contained an invalid keyword or value. The invalid parameter/value is indicated by pppppppp.
User Response: Correct the parameter in error and restart XPS.
CAXPS903E INVALID TRACE CODE(S) SPECIFIED - ABORTING

Explanation: The Cross-Platform Scheduling Router (XPS) was engaged with an invalid trace code
specified. Trace codes must be numeric.
User Response: Correct the parameter in error and restart XPS.
CAXPS904E UNABLE TO LOAD MODULE mmmmmmmm . RC=cccc

Explanation: The Cross-Platform Scheduling Router (XPS) was unable to load needed module into
storage during startup. The module name is indicated by mmmmmmmm. The system return code
from load is indicated by cccc.
User Response: Review the JCL for XPS and confirm the correct load library is in the STEPLIB
DD, or the library is Link-Listed. If these are correct, the problem may be insufficient storage.
Increase the region size and try again.
CAXPS905E XPS SUB-TASK ENDED PREMATURELY: tttttttttttttttt (mmmmmmmm) TCBCMP=cccccc

Explanation: A Cross-Platform Scheduling Router (XPS) subtask terminated outside of normal
shutdown processing. The title of the subtask is indicated by tttttttttttt. The subtask module is indi-
cated by cccccc. This message may be preceded by other messages which indicate the exact nature
of the error. The XPS system will shut down any other subtasks which are active and terminate
processing.
CAXPS906E SUBTASK HAS NOT RESPONDED TO TERM CALL: tttttttttttttttt

Explanation: A Cross-Platform Scheduling Router (XPS) subtask has not responded to a termi-
nation signal during normal shutdown processing. The title of the subtask is indicated by ttt...ttt.
The subtask will be forced to terminate (detached) by the main task and XPS shutdown processing
will proceed.
CAXPS907E ERROR RETURN FROM ATTACH FOR mmmmmmmm RC=cccc

Explanation: A Cross-Platform Scheduling Router (XPS) was unable to attach a subtask during
initialization processing. The module being attached is indicated by mmmmmmmm. The return code
from the attach process is indicated by cccc. The XPS system will shut down any active tasks and
terminate with a return code of 12.
User Response: One possible reason for this error is insufficient storage. Try increasing the region
XPS is running in. If this does not correct the problem contact Computer Associates Technical
Support for assistance.

2.8 CAXPS Messages
CAXPS908E –CAXPS911W
CAXPS908E STARTUP OF SUBTASK mmmmmmmm FAILED. COMP=cccccc

Explanation: A Cross-Platform Scheduling Router (XPS) subtask could not initialize properly. The
subtask module is indicated by mmmmmmmm. The return code from the subtask is indicated by
cccccc. The XPS system will shut down any active tasks and terminate with a return code of 8.
CAXPS909E SUBTASK HAS NOT RESPONDED TO INIT CALL: tttttttttttttttt

Explanation: A Cross-Platform Scheduling Router (XPS) subtask did not complete initialization
within two minutes of being engaged. The subtask title is indicated by tttttttttttttttt. The XPS system
will shut down any active tasks and terminate with a return code of 8.
CAXPS910E XPS ffff OF dddddddddd FAILED. RC=rr CC=cc

Explanation: A Cross-Platform Scheduling Router (XPS) main task call to a subfunction module
failed. The function is indicated by ffff (INIT, TERM, and so forth). The description of the sub-
function is indicated by dddddddddd (TABLE FUNC, TRACE FUNC, and so forth). If the error
occurs during initialization processing, the XPS system will shut down any active tasks and termi-
nate. If the error occurs during XPS command processing, the command will be rejected and normal
processing will continue.
there are no other messages and the problem is impacting normal processing, contact Computer Asso-
ciates Technical Support for assistance.
CAXPS911W XPS ESTAE ENTERED - WIP=ww (cccc) (pppppppp): dddddddddddd

Explanation: A Cross-Platform Scheduling Router (XPS) main task error routine has been entered
for an abend in its own processing, or the processing of a task above it. The where-in-program code
is indicated by ww. The abend code is indicated by cccc (hex). The abend PSW is indicated by
pppppppp. If the PSW points to an address within the XPS main task program it will be in the form
of '+ offset'. If not, it will be the full 8 character PSW. The description of the action being taken by
the XPS recovery routine is indicated by dddddddddddddd. If the recovery routine will attempt to
continue processing the description will be 'RETRY IS BEING ATTEMPTED'. If the recovery is
successful, XPS will continue its normal processing. If the error occurred in the task which attached
XPS, or the error is persistent, or the error is of a critical nature the description will be 'ALLOWING
ABEND TO PROCEED'. In this case the XPS system will be terminated with the original error.
there are no other messages and the problem is impacting normal processing, contact Computer Asso-

2.8 CAXPS Messages
CAXPS925E tid TASK RECEIVED INVALID PARM LIST

Explanation: A Cross-Platform Scheduling Router (XPS) subtask was engaged with a missing or
invalid parameter list. The subtask id is indicated by tid. The subtask will terminate with a return
code of 16.
CAXPS926E XPS tttttttttttt ALREADY ACTIVE ON THIS SYSTEM

Explanation: A Cross-Platform Scheduling Router (XPS) subtask has detected that another copy of
XPS is already active at the local CAICCI node. The XPS subtask title is indicated by tttttttttttt.
There can only be one XPS system active at each CCI node. The subtask will terminate with a
return code of 32 (decimal).
User Response: Review your operations procedures to ensure only one copy of XPS is started at
each CCI node (that is, MVS image). If necessary, contact Computer Associates Technical Support
for assistance.
CAXPS927E (tid) sss ERROR FUNC=ffff RC=rr CC=cc xxxx...xxxx

Explanation: A Cross-Platform Scheduling Router (XPS) subfunction module has encountered an
error. The calling task is identified by tid. The subfunction is indicated by ssss (CCI, ENF, and so
forth). The specific function being performed is indicated by ffff (INIT, TERM, and so forth). The
return code (rr) and condition code (cc) from the error are also indicated. A text description of the
error is indicated by xxxx....xxxx. The calling XPS task may or may not terminate processing based
upon the error encountered. Other messages may follow this one.
CAXPS928E (tid) ssss CALL FAILED: FUNC=ffff RC=rr CC=cc

Explanation: A Cross-Platform Scheduling Router (XPS) subfunction module has encountered an
internal error. The calling task is identified by tid. The subfunction module is indicated by ssss
(CCIF, ENFF, and so forth). The specific function being performed is indicated by ffff (INIT,
TERM, and so forth). The return code (rr) and condition code (cc) from the subfunction are also
indicated. The calling XPS task may or may not terminate processing based upon the error encount-
ered. Other messages may follow this one.

2.8 CAXPS Messages
CAXPS929E STATUS OF CAXPSFBK EVENT IS INVALID. CURRENT STATUS IS : ssssssss

Explanation: The Cross-Platform Scheduling Router (XPS) has determined that the status of the
CA-ENF event used by XPS is not correct. The event used by XPS is the Cross-Platform Scheduling
Feedback Event (CAXPSFBK). This event should be in RECORD status for the XPS system to
function properly. The current status of this event is indicated by ssssssss.
User Response: Review the installation procedures for XPS in your scheduling product documenta-
tion and add the CAXPSFBK event to CA-ENF with a status of RECORD. If ENF is currently
active it will need to be shut down and restarted for the new event to be available. Restart the XPS
system once this has been done (if XPS is running under CA-7, CA-7 needs to be recycled).
CAXPS931W RESET BEING FORCED FOR XPS SETUP MANAGER ENF THREAD
Explanation: The Cross-Platform Scheduling Router (XPS) Setup Manager has detected a persistent
mismatch in the posting of CA-ENF events for itself and the Tracking Sender task. This indicates a
problem with the CA-ENF thread the Setup Manager is using.
User Response: None. All connected nodes that are being processed for checkpoint synchroniza-
tion will be reset. The current CA-ENF thread is closed, and a new thread is established. Contact
your installation's CA-7 specialist if this message occurs more than once.
CAXPS950E PRINT DD IS INVALID OR UNAVAILABLE

Explanation: The Cross-Platform Scheduling Router (XPS) has determined that the DD statement
for print output is either not defined, or is invalid.
User Response: Review the requirements for the function being performed and correct the JCL.

2.9 CA7M Messages
CA7M0000 –CA7M0005
2.9 CA7M Messages
CA7M0000 I mmmmmmmm(nnnn) #CCI Initialization completed for tttttttt

Explanation: #CCI initialization is complete for the task named at tttttttt. Possible values of tttttttt
are: MONITOR and ROUTER. These are CA-7 XPS subtasks. The message is issued from the
module named at mmmmmmmm, offset nnnn.
CA7M0001 I mmmmmmmm(nnnn) Task initializing for tttttttt

Explanation: The subtask named at tttttttt is starting. Possible values for tttttttt are MONITOR and
ROUTER. The message is issued from the module named at mmmmmmmm, offset nnnn.
CA7M0002 I mmmmmmmm(nnnn) Task initialization complete for tttttttt

Explanation: Initialization is complete for the task named at tttttttt. Possible values for tttttttt are
MONITOR and ROUTER. The message is issued from the module named at mmmmmmmm, offset
nnnn.
CA7M0003 I mmmmmmmm(nnnn) CCI macro failure on tttttttt. Func was FFFF. RC = nnnnnnnn
Explanation: A CCI macro failure was detected on the subtask named at tttttttt. The function
attempted is named at FFFF. The return code is reported at nnnnnnnn. The message is issued from
the module named at mmmmmmmm, offset nnnn.
User Response: Contact your installation's CA-7 technical specialist for assistance.
CA7M0004 I mmmmmmmm(nnnn) FDBVDESC:

Explanation: A CCI macro failure was detected. A description of the error follows FDBVDESC:.
The message is issued from the module named at mmmmmmmm, offset nnnn.
CA7M0005 I mmmmmmmm(nnnn) STIMER issued for tttttttt. Interval is nnnnnnnn

Explanation: An STIMER was issued for the task named at tttttttt. The interval for the STIMER is
reported as a hex value in hundredths of seconds. This value appears at nnnnnnnn. This is only an
informational message. The message is issued from the module named at mmmmmmmm, offset
nnnn.

2.9 CA7M Messages
CA7M0006 –CA7M0011
CA7M0006 I mmmmmmmm(nnnn) Invalid numerics found in field length. Task: tttttttt

Explanation: Invalid data was detected in an XPS scheduling request. The request could not be
honored. The XPS CLIENT is notified of this error and the requested job does not run. tttttttt is the
subtask that detected the error. The message is issued from the module named at mmmmmmmm,
offset nnnn.
CA7M0007 I mmmmmmmm(nnnn) Required keyword value not supplied. tttttttt

Explanation: Invalid data was detected in an XPS scheduling request. The request could not be
offset nnnn.
CA7M0008 I mmmmmmmm(nnnn) No space in L2CMAREA for keyword. Task: tttttttt

Explanation: The XPS scheduling request was not parsed successfully. The request could not be
offset nnnn.
CA7M0009 I mmmmmmmm(nnnn) No space in L2CMAREA for keyword value. Task: tttttttt

offset nnnn.
CA7M0010 I mmmmmmmm(nnnn) Invalid length for keyword value. Task: tttttttt

offset nnnn.
CA7M0011 I mmmmmmmm(nnnn) Invalid data in field. Field = ffffffff Task: tttttttt

Explanation: The parameters supplied in the XPS scheduling request did not provide valid values
for the CA-7 scheduling command used to satisfy the request. tttttttt is the subtask that detected the
error. The message is issued from the module named at mmmmmmmm, offset nnnn.

2.9 CA7M Messages
CA7M0012 –CA7M0019
CA7M0012 I mmmmmmmm(nnnn) Data rejected from: nnnnnnnnnnnnnnnnnnnn. Task: tttttttt

Explanation: This message reports the origin of the invalid XPS scheduling request. tttttttt is the
offset nnnn.
CA7M0014 I mmmmmmmm(nnnn) nnnnnnnn failed for tttttttt. RC: nnnnnnnn

Explanation: This message reports a macro failure on the subtask named at tttttttt. The return code
is reported at nnnnnnnn. The message is issued from the module named at mmmmmmmm, offset
nnnn.
CA7M0015 I mmmmmmmm(nnnn) ATTACH successful for nnnnnnnn. Task: tttttttt

Explanation: This message reports that the task named at tttttttt successfully initiated processing for
the module named at nnnnnnnn. The message was issued from mmmmmmmm at offset nnnn.
CA7M0016 I mmmmmmmm(nnnn) L2CCISD waiting for post.

Explanation: This message reports that the task attaching the XPS ROUTER is waiting for input.
This is an informational message. The message was issued from mmmmmmmm at offset nnnn.
CA7M0017 I mmmmmmmm(nnnn) L2CCISD posted CAXPSYSD

Explanation: The XPS ROUTER has been posted for action. This is an informational message.
The message was issued from mmmmmmmm at offset nnnn.
CA7M0018 E mmmmmmmm(nnnn) Error. LOC=xxxxxxxx R15=yyyyyyyy R0 = zzzzzzzz

Explanation: An error was detected by the module named at mmmmmmmm. The location within
the module is reported at xxxxxxxx. The values of R15 and R0 are also reported. The message is
issued from the module named at mmmmmmmm, offset nnnn.
CA7M0019 E mmmmmmmm(nnnn) Error scheduling command.

Explanation: An error occurred during the attempt to schedule an internal terminal command for
cross-platform scheduling. The most likely cause is an invalid logonid. The message is issued from
the module named at mmmmmmmm, offset nnnn.
User Response: Examine the browse data set for the DEMAND or RUN command that was issued
for this cross-platform scheduling request. An error message should be produced for the command.
See the discussion of that message in this CA-7 Message Guide.

2.9 CA7M Messages
CA7M0020 –CA7M0020
CA7M0020 E mmmmmmmm(nnnn) Error. RC=xxxxxxxx

Explanation: An error was detected by the module named at mmmmmmmm. The error return code
is reported at xxxxxxxx. The message is issued by the module named at mmmmmmmm, offset
nnnn. For SASSTRX0 RC=4, a TRX terminal could not be obtained.
User Response: Contact your installation's CA-7 technical specialist for assistance. For
SASSTRX0 RC=4, you may need to add one or more TRX terminals to the CA-7 initialization file.
This would only be needed if the message is issued frequently.

Chapter 3. CA-7.A - CA-7.X
This chapter contains the CA-7.A through CA-7.X messages.
Chapter 3. CA-7.A - CA-7.X 3-1

3.1 CA-7.AIJC Through CA-7.DT60 Messages
CA-7.AIJC –CA-7.AIJC
CA-7.AIJC UNABLE TO LOCATE ARF TRAILER

Explanation: An ARF condition was detected for a job, but an error occurred. ARF was unable to
format information about the error in the ARF trailer segment for the job.
User Response: Check the CA-7 log for any additional error messages and contact Computer Asso-
ciates Technical Support.
CA-7.AIJC SQ ERROR AT xxxx ERR=cccc

Explanation: An ARF condition was detected for a job, but an error occurred on a CA-7 queue
access macro. ARF was unable to format information about the error in the ARF trailer segment for
the job. xxxx indicates the offset into SASSAIJC where the error occurred.
CA-7.AIJC INVALID SASSARQM ADDRESS

Explanation: CA-7 was unable to locate a module needed for ARF monitoring.
CA-7.AIJC JC ERROR FOR jjjjjjjj (nnnn)

CA-7.AIJC INVALID SASSARHT ADDRESS

Explanation: An error occurred during ARF monitoring of JC or EC exceptions. ARF was unable
to locate the address of the module used to evaluate the exceptions.
User Response: ARF has not been properly initialized. Ensure that ARF=YES had been coded on
the RESTART statement in the initialization file. Check for any console messages that may indicate
a problem with ARF initialization. Correct the problem and restart CA-7. If the problem persists,
CA-7.AIJC ERROR FOR jjjjjjjj(nnnn)

Explanation: An error occurred during ARF monitoring of JC or EC exceptions. This message
should be accompanied by others which more exactly specify the nature of the problem.
User Response: This message is issued for a variety of error conditions, but is informational only.

CA-7.AIJC –CA-7.AISC
CA-7.AIJC ERROR: ARQM ERR R15=xxxxxxxx, R0=yyyyyyyy, R1=zzzzzzzz

Explanation: An error occurred processing an ARF request. The R15, R0, and R1 values help to
determine the cause.
User Response: Contact your installation's CA-7 specialist for assistance. If R15=10 and R0=6, the
original job may have been canceled.
CA-7.AILE INVALID SASSARHT ADDRESS

CA-7.AILS UNABLE TO LOCATE ARF TRAILER

CA-7.AILS SQ ERROR AT xxxx ERR=cccc

CA-7.AILS INVALID SASSARHT ADDRESS

CA-7.AILS ERROR FOR jjjjjjjj (nnnn)

CA-7.AISC UNABLE TO LOCATE ARF TRAILER


CA-7.AISC –CA-7.ARF0
CA-7.AISC SQ ERROR AT xxxx ERR=cccc

format information about the error in the ARF trailer segment for the job. xxxx is the offset in
SASSAISC where the error occurred.
CA-7.AISC INVALID SASSARHT ADDRESS

CA-7.AISC ERROR FOR jjjjjjjj (nnnn)

CA-7.ARF0 ERROR FOR JOB (nnnn): ARGR R15=xxxxxxxx R0=yyyyyyyy R1=zzzzzzzz. SET=ssssssss
Explanation: An error occurred while trying to locate the next ARF response in an ARFSET for a
job.
CA-7.ARF0 ERROR FOR JOB (nnnn): UNABLE TO RESPOND TO cc CONDITION IN SET=ssssssss

Explanation: An error occurred while trying to respond to an ARF exception condition. The code
indicating the type of response to be executed was not recognized by SASSARF0.
CA-7.ARF0 ERROR FOR JOB (nnnn): ARQM R15=xxxxxxxx R0=yyyyyyyy R1=zzzzzzzz. SET=ssssssss
Explanation: An error occurred while trying to update the status of an ARF response in the ARF
queue.
CA-7.ARF0 ERROR FOR JOB (nnnn): RC FROM SASSTRX0 IS xxxxxxxx, SET=ssssssss.

Explanation: An error occurred while trying to schedule a command on a TRXDV terminal during
a response to an ARF exception.

CA-7.A001 –CA-7.BSTR
CA-7.A001 ARF Response job (nnnn) jjjjjjjj Type=cc, Intercept=xxxx at hh:mm:ss.th

Explanation: This message is issued as part of the ARF response defined on an AM action state-
ment. The name and CA-7 job number of the job in ARF recovery is reported along with the type of
ARF exception condition detected. The intercept number indicates how many exceptions of this type
have been detected since the last startup of CA-7.
CA-7.A002 (nnnn) TYPE=cc INDEX=ii

Explanation: This message is issued as part of the ARF response defined on an AM action state-
ment. The CA-7 job number of the job in ARF recovery is reported followed by an indication of the
type of exception condition detected. The index value is the value of the DEFID of the condition
definition containing the AM action statement.
CA-7.A003 (nnnn) ARF Set=ssssssss yyyy/ddd hh:mm:ss.th

Explanation: This message is issued as part of the ARF response requested on an AM action state-
ment. The CA-7 job number of the job in ARF recovery is reported followed by the name of the
ARFSET in containing the AM action statement. The date and time following the ARFSET name
identifies the instance of the ARFSET definition that is used for ARF monitoring.
CA-7.BCLPnn Refer to 2.2, “BCLP Messages” on page 2-5 for other BCLP messages.
CA-7.BCLP-95 NCF NODE TABLE NOT DEFINED
Explanation: The node control table was not found.
User Response: The job will abend.
Operator Response: The NCFNODE parameter can only be specified if NCF is installed.
Programmer Response: If appropriate, assemble and link the node table.
CA-7.BCLP-96 UNDEFINED NCF NODE xxxxxxxx

Explanation: A node name, xxxxxxxx, was found during processing that is not in the node table.
Operator Response: The node name in the parameter NCFNODE=nodename must be a node name
from the node control table. Recode the parameter and resubmit the job.
Programmer Response: None.
CA-7.BSTR BTERM FLAG RESET, MAY NEED TO RESUBMIT

Explanation: CA-7 terminated while a batch terminal interface was active. Issued by SASSBSTR.
User Response: Check that CA-7 is active. Resubmit the SASSBSTR job. The transaction(s) from
the preceding SASSBSTR run may already have been processed by CA-7.

CA-7.BSTR-21 –CA-7.BTMV
CA-7.BSTR-21 BATCH TERMINAL # x ALLOCATED

Explanation: This is an informational WTO indicating that SASSBSTR has assigned batch terminal
number x to this job.
CA-7.BSTR-22 BATCH TERMINAL # x RELEASED

Explanation: This is an informational WTO indicating that SASSBSTR has released batch terminal
number x.
CA-7.BSTR-28 UNABLE TO OPEN ERRORS DD. MESSAGE TABLE ERRORS WILL NOT BE
REPORTED.
Explanation: This message is issued when a user-defined BTI Message Table is available, but the
DD statement for the ERRORS file is not in the JCL. Normally, messages from the BTI Message
Table checking are routed to this ERRORS DD. Since this DD is not available, the messages will
not be produced. However, you will still get the CA-7.BSTR-30 WTO which informs you how
many table matches were made, and what the highest matched condition code is.
User Response: Add a DD statement for ERRORS. The format is the same as the existing
SYSPRINT DD.
CA-7.BSTR-29 * ERROR MSG TABLE MATCH (CC=xxx) : ...output line text.....

Explanation: This message is written to the ERRORS print DD when a line in the BTI output
matches an entry in the user-defined BTI message table (SASSXXBT). The condition code (cc=)
that is associated with that table is listed. Also, the text of the BTI output line is displayed.
CA-7.BSTR-30 ERROR MSGS FOUND IN OUTPUT. MSGS MATCHED=xxxxx, HIGH CC=ccc.

Explanation: This WTO is issued at the end of BTI processing if any lines in the BTI output
matched an entry in the user-defined BTI message table (SASSXXBT). The number of matches
made (xxxxx) and the highest condition code associated with those entries (ccc) are detailed. The
return code of the BTI step is set to the highest condition code matched.
CA-7.BTMV xx yy tttttt VSAM IDS [(OPEN)|(CLOSE)] ACB FAILURE

Explanation: The OPEN or (CLOSE) for the VSAM IDS was unsuccessful. If xx=04, this indi-
cates that the VSAM IDS was not opened or closed in a normal way (such as when CA-7 abends
rather than shuts down normally). No action is required. Another CA-7.BTMV message should
follow indicating the verify macro completed successfully. Issued by SASSBTMV.
If xx=08 or greater, the pack on which the VSAM IDS resides may have had an I/O error. If xx=08,
the following are possible reasons for the error:
1. There was not enough space to do a normal VSAM OPEN (or CLOSE).
2. If a security package is being used, CA-7 may not have authorization to access the IDS.

CA-7.BTMV –CA-7.CCIL
User Response: If xx=08 or greater, CA-7 will abend with a U0955 abend. If xx=08, first verify
the CWORK parameter value in the CA-7 Execution JCL. If the CWORK value is high enough,
check for security package definitions for the VSAM IDS to ensure that CA-7 can access it. Refer to
the CA-7 Systems Programmer Guide.
If none of the above apply, the IDS may need to be verified through IDCAMS or a database
recovery may need to be done.
CA-7.BTMV VERIFY MACRO COMPLETED SUCCESSFULLY

Explanation: This is an informational message following the previous CA-7.BTMV message indi-
cating an OPEN ACB failure. Issued by SASSBTMV.
CA-7.BTMX ABEND xxxx IN SUBTASK (yyyyyyy ; zz)

Explanation: This WTO is produced if the CA-7 subtask has abended. The subtask will be rein-
stated and the terminal in control that caused the abend will be logged off. If it is a virtual terminal,
it will be disconnected.
The xxxx is the abend code. The yyyyyyy is the terminal name. The zz is the code used by the
SASSBTMX module to determine what processing is to be done.
User Response: CA-7 stays up and running. Only the terminal user that issued the command is
disconnected. This user can log back on and continue. Depending on the command that was being
processed at the time of the failure, storage may not be freed or a data set may be left enqueued (for
example, JCL screen getting an S913 abend due to security access).
CA-7.CCIL No internal terminals for XPS SERVER requests.

Explanation: At least one terminal must be defined with DEVICE=TRXDV for use with cross-
platform scheduling. Refer to the CA-7 Systems Programmer Guide for more information on defining
internal terminals.
User Response: If cross-platform scheduling is to be used, ensure that at least one internal terminal
is defined and restart CA-7.
CA-7.CCIL XPS SERVER requests will be rejected.

Explanation: No XPS SERVER facilities are available because no internal terminals have been
defined. Refer to the CA-7 Systems Programmer Guide for information on defining internal terminals
(DEVICE=TRXDV).
User Response: If cross-platform scheduling is to be used, ensure that at least one internal terminal
is defined and restart CA-7.
CA-7.CCIL SEVERE ERROR; Could not locate SCT.

Explanation: An error occurred while trying to locate a system control block. The problem is
likely due to a storage overlay. CA-7 will abnormally terminate.
User Response: Contact your CA-7 technical specialist for assistance.

CA-7.CCIL –CA-7.CHDO
CA-7.CCIL Fast shutdown of SASSCCIL tasks started.

Explanation: A shutdown of CA-7 XPS subtasks was requested.
CA-7.CCIL Fast shutdown of SASSCCIL tasks ended.

Explanation: The requested shutdown of CA-7 XPS subtasks is complete.
CA-7.CDIO COMDS VOLUME STATUS HAS CHANGED. ICOM AND CA-7 MUST BE RECYCLED.
Explanation: This message is produced if the status changes for the disk drive containing the
volume on which the Communications data set resides. The particular status checked is the share
indication. Normally, this status will never change. However, one example of how it can change is
by doing a CPU split or merge operation.
User Response: CA-7 and all the ICOMs must be stopped and restarted as soon as possible. Any
delays in doing this can cause SMF tracking information (that CA-7 puts in the Communications data
set) to be lost.
CA-7.CHDO PAGE ERROR FOR TERM xxxxxxx

Explanation: CA-7 is unable to read a message from the scratch queue. The message may have
been written to the scratch queue incorrectly. Issued by SASSCHDO.
User Response: The WTO is informational and no action is required unless terminal xxxxxxx
hangs. In that case, the following steps are recommended:
1. Enter /STOP,T=xxxxxxx
2. Enter /PURGPG,LT=xxxxxxx
3. Enter /START,T=xxxxxxx
If the previous steps do not work, try starting CA-7 with a TYPE=ERST. It may be necessary to
relink CA-7 (N520 of install jobs) and/or execute a DMPQ/MOVQ start up.
CA-7.CHDO MESSAGE ALREADY QUEUED FOR TERM xxxxxxx

Explanation: A message is trying to be processed for a terminal when one is already in process.
Issued by SASSCHDO.
User Response: The WTO is informational and no action is required unless terminal xxxxxxx
hangs. In that case, the following steps are recommended:
1. Enter /STOP,T=xxxxxxx
2. Enter /PURGPG,LT=xxxxxxx
3. Enter /START,T=xxxxxxx
If the previous steps do not work, try starting CA-7 with a TYPE=ERST.

CA-7.CMGR –CA-7.CPMP
CA-7.CMGR SKIP TRAILER BLOCK

Explanation: During CA-7 startup (after a power failure, cancel, and so forth), an invalid block of
trailer terminal commands was found in the communications data set. Any commands in this block
that were not processed prior to the previous CA-7 termination would be ignored.
User Response: None required, though it may be possible that one or more trailer commands will
not be processed.
CA-7.CPMA Unable to track flow for xxxxxxxx

Explanation: An error occurred during FLOW initiation for the FLOW named xxxxxxxx. CA-7
will not be able to communicate information about the FLOW to CA-OPS/MVSII.
User Response: This message will be accompanied by one or more diagnostic messages that give
additional information about the underlying error. Contact your installation's CA-7 technical spe-
cialist with the output that includes these messages.
CA-7.CPMA FLOW ADD Error for xxxxxxxx RSPLFDBK=yyyyyyyy

Explanation: An I/O error occurred during FLOW initiation for the FLOW named xxxxxxxx.
yyyyyyyy is the VSAM feedback.
User Response: Contact your installation's CA-7 technical specialist.
CA-7.CPMA FLOW ADD Error for xxxxxxxx ; Already on flow chain

Explanation: A logic error occurred during FLOW initiation for the FLOW named xxxxxxxx.
CA-7.CPMA FLOW ADD Error for xxxxxxxx ; Already on CRQ chain

Explanation: A logic error occurred during FLOW initiation for the FLOW named xxxxxxxx.
CA-7.CPMA FLOW fff Error for xxxxxxxx zzzzz RC=yyyyyyyy

Explanation: A queue I/O error occurred during FLOW initiation for The FLOW named xxxxxxxx.
The function is fff, zzzzz is the SQ macro that failed. yyyyyyyy is the SQ macro return code.
CA-7.CPMP ffffff error -- xxxxxxxx (nnnn) in yyyyyyyy/zzzzzzzz (mmmm) yyyy.ddd hh:mm:ss.th

AA/rrrrrrrr
Explanation: An I/O error occurred while trying to update the FLOW record during FLOW purge
processing. ffffff is the function attempted. xxxxxxxx is the name of the job, (nnnn) reports the
CA-7 job number. The name of the flow is yyyyyyyy and zzzzzzzz is the name of the starting job in
the flow. The CA-7 job number for the starting job is (mmmm). AA is a code used to locate where
in SASSCPMP the error was detected and rrrrrrrr is the VSAM feedback code.

CA-7.CPMT –CA-7.DRVR
CA-7.CPMT Unable to track xxxxxxxx (nnnn) in yyyyyyyy/zzzzzzzz (mmmm) yyyy.ddd hh:mm:ss.th

AA/00000000
Explanation: An I/O error occurred during FLOW propagation. xxxxxxxx is the name of the job,
(nnnn) reports the CA-7 job number. The name of the flow is yyyyyyyy and zzzzzzzz is the name of
the starting job in the flow. The CA-7 job number for the starting job is (mmmm). AA is a code
used to locate where in SASSCPMT the error was detected and rrrrrrrr is the VSAM feedback code.
CA-7.DRVR THE CA-7 DRIVER IS ACTIVE. xxx...x

Explanation: This is an initial message indicating the driver is active. xxx...x is the 40 bytes of
comments from the driver control statement. Issued by SASSDRVR.
CA-7.DRVR SELECT A RESTART (TYPE=) OPTION

(FORM,COLD,MOVQ,WARM,ERST,STOP)
Explanation: This message indicates the driver is waiting for input to start or restart CA-7. This
message appears for the initial start of CA-7 under the driver and for all subsequent restarts. Issued
by SASSDRVR.
User Response: Reply one of the following:
FORM - For a CA-7 format queue restart.
COLD - For a CA-7 cold start.
WARM - For a CA-7 warm start.
ERST - For a CA-7 emergency restart.
MOVQ - To reload the queues from a previous /SHUTDOWN,DMPQ.
STOP - To terminate the driver.
CA-7.DRVR CA-7 ENDED WITH A xyyyy

Explanation: This message appears after CA-7 terminates and the driver receives control. x is
either an S for a system abend or a U for user abend or condition code. Issued by SASSDRVR.
User Response: If an automatic restart has been specified, then CA-7 will automatically be
restarted. If an automatic restart has not been specified or this termination is subsequent to an auto-
matic restart, then the driver will require an operator response for restarting or stopping.
CA-7.DRVR AUTOMATIC WARM (ERST) START IN PROCESS

Explanation: An automatic restart has been specified in the driver control statement. The driver is
automatically restarting CA-7. Issued by SASSDRVR.

CA-7.DRVR –CA-7.DT60-02
CA-7.DRVR OK.
Explanation: The driver acknowledges that the chosen restart option is valid. The driver is
restarting CA-7. Issued by SASSDRVR.
CA-7.DRVR SHUTDOWN IN PROGRESS

Explanation: The driver acknowledges that the STOP option has been chosen. The driver is shut-
ting down. Issued by SASSDRVR.
CA-7.DRVR INVALID PARM= OR DRVRIN DATA

Explanation: Either the PARM data on the EXEC statement for the CA-7 driver is invalid or data
supplied on the driver control card is incorrect. This message will be accompanied by a U101 abend.
Issued by SASSDRVR.
Possible problems:
1. No PARM specified.
2. TYPE=xxxx omitted from the PARM data.
3. Too much PARM data.
4. Unable to open DRVRIN.
5. No *DRVR* control statement.
6. Invalid control statement data.
User Response: Correct and resubmit the job.
CA-7.DT60-01 UNABLE TO OPEN SYSPRINT FILE

Explanation: The open failed for the SYSPRINT output file.
User Response: Examine the DD statement for correct values, including spelling of the DDNAME.
CA-7.DT60-01 VSAM PROCESSING ERROR RC=xx FDBK=yyyy

Explanation: Nonzero return code from VSAM.
User Response: Refer to IBM's VSAM Programmer's Guide for the return code and feedback codes
listed in this message.
CA-7.DT60-02 UNABLE TO OPEN JOBREPT REPORT FILE

Explanation: The open failed for the JOBREPR output file.
User Response: Examine the DD statement for correct values, including spelling to the DDNAME.

CA-7.DT60-03 –CA-7.DT60-08
CA-7.DT60-03 UNABLE TO OPEN SYSIN FILE

Explanation: The open failed for the SYSIN input file.
CA-7.DT60-05 ERROR READING RESOURCE FILE (CA7RSRC)

Explanation: The read of the resource file gave a nonzero return code.
CA-7.DT60-06 SYSIN CONTROL CARDS REQUIRED

Explanation: At least one SYSIN control statement is required.
User Response: Code valid control statement(s).
CA-7.DT60-06 INVALID CONTROL CARD SPECIFIED

Explanation: First character of control statement is blank.
User Response: Code valid command in first column.
CA-7.DT60-07 INVALID CONTROL CARD SPECIFIED

Explanation: Control statement did not specify JOB= in first four positions or first character after
JOB= not alpha.
User Response: Check for correct spelling of keyword. Check for correct operand; must have at
least one character if using generic that is JOB=A*.
CA-7.DT60-08 UNABLE TO OPEN RESREPT FILE

Explanation: The open failed for the RESREPT output file.
CA-7.DT60-08 UNRECOGNIZED PARM VALUE SPECIFIED

Explanation: PARM not 'REPORT' and/or 'ALLJOBS'.
User Response: Check for correct spelling of PARMS.

3.2 CA-7.D32V Through CA-7.VB99 Messages
CA-7.D32V –CA-7.HLTD
CA-7.D32V FREE FOR VTAM VIRTUAL ENTRY FAILED

Explanation: Unable to find current terminal entry in logon ID table. Issued by SASSD32V.
User Response: If error persists, contact your installation's CA-7 specialist.
CA-7.D32V MESSAGE ALREADY QUEUED

Explanation: CA-7 has automatically corrected an internal control block pointer error. Informa-
tional message.
CA-7.D32V (xx,yy) SYN CLSDST FOR xxxxxxx

Explanation: A VTAM CLSDST macro has been issued for terminal xxxxxxx. The return codes
from registers 15 and 0 are represented by xx and yy respectively. Issued by SASSDRVR.
User Response: None. The message is in response to a requested disconnection of the terminal
from the CA-7 application.
CA-7.FBAT EXTRANEOUS DATA BYPASSED

Explanation: The input to a batch terminal contains a transaction that is too large.
User Response: Check the batch terminal input. Make sure there are no continuation indicators in
column 72 except on transactions where it is valid.
CA-7.HALT REQUESTING SHUTDOWN OF PROBLEM MANAGEMENT SUBTASK

Explanation: The problem management subtask is shut down during normal termination of CA-7.
CA-7.HALT REQUESTING SASSCCIL TERMINATION.

Explanation: CA-7 XPS subtask termination is requested. This occurs as part of normal CA-7
shutdown.
CA-7.HLTD ALLVSAM ERROR ATTEMPTING TO DISCON/FINISH, RC=xxxx

Explanation: Errors occurred while attempting to initialize, connect, disconnect or finish with an
Issued by SASSHLTD.
User Response: None. System will continue shutdown process.

CA-7.IARE –CA-7.IARE
CA-7.IARE ARF HOOK PROCESSING ACTIVATED

Explanation: The CA-7 startup parameters included a 'RESTART,ARF=YES' or
'RESTART,ARF=MAINT' control statement requesting ARF processing. The ARF Hook Test Tables
have been acquired and initialized.
CA-7.IARE ARF HOOK PROCESSING WILL NOT BE USED

Explanation: The CA-7 startup parameters indicated ARF hook processing would not be used. The
ARF Hook Test Tables were not built.
CA-7.IARE ARF DATA BASE WILL NOT BE USED

Explanation: The CA-7 startup parameters indicated ARF would not be used.
CA-7.IARE ARF ENVIRONMENT HAS BEEN INITIALIZED

'RESTART,ARF=MAINT' control statement requesting ARF processing. All ARF control blocks
have been built and the ARF database is OPEN and ready for processing.
CA-7.IARE ERROR: RC=xx RS=rrrr INF=iiii

Explanation: An error has occurred during ARF environmental initialization. The return, reason,
and information codes define the problem exactly. Refer to the list of return codes below.
User Response: ARF processing will be disabled for this execution of CA-7.
RC=04 GETMAIN failed for AVT. The AVT is not initialized. Retry later.
RC=08 SASSTMNT table handler routine is not available. Job table was not initialized.
RC=12 SASSTMNT failed to initialize job table.
RC=16 GETMAIN failed for HTT. ARF HTT not initialized. Retry later.
RC=20 GETMAIN failed for ARF statistics area. Retry later.
RC=24 SASSTMNT table handler not available. Not initialized.
RC=28 SASSTMNT failed to initialize an HTTE's table area.
RC=32 'ARFIO STARTUP' failed.
RC=36 'ARFIO INIT' failed.
RC=40 'ARFIO SEQ' failed.
RC=44 'ARFIO GETNEXT' failed.
RC=48 GETMAIN failed for AAR. ARF active queue is not rebuilt.

CA-7.IARI –CA-7.IARI
RC=52 'ARFIO ENDREQ' failed.

RC=56 LOAD EP=SASSARJI failed.
RC=60 LOAD EP=SASSARHT failed.
RC=64 LOAD EP=SASSARJP failed.
RC=68 LOAD EP=SASSARQM failed.
RC=72 LOAD EP=SASSARGR failed.
RC=76 LOAD EP=SASSARMS failed.
CA-7.IARI ARF DATA BASE IS NOW ONLINE

'RESTART,ARF=MAINT' control statement requesting ARF processing. The ARF database is
required for ARF to process. This message indicates the entire ARF database access environment
has been built, and the ARF DB is ready for access.
CA-7.IARI ARF DB INIT ERROR: RC=xx RS=rrrr INF=iiii

Explanation: An error has occurred during ARF database startup. The return, reason, and informa-
tion codes define the problem exactly. Refer to the list of return codes below.
User Response: In all probability the ARF database is not operational. ARF processing will be
disabled for this execution of CA-7.
RC=04 The ARF database was already open.
RC=08 The ARF I/O routine, SASSARIO, was not loaded.
RC=12 GETMAIN for ARF ACB failed.
RC=16 GENCB BLK=ACB for ARF DB ACB failed.
RC=20 Issued by 'ARFIO STARTUP' macro when this module not found.
RC=24 GETMAIN for an ARFIO (AIO) area failed.
RC=28 GETMAIN for an ARFIO (AIO) buffer failed.
RC=32 GETMAIN for an ARFIO (AIO) RPL failed.
RC=36 GENCB for an ARFIO (AIO) RPL failed.
RC=40 RDJFCB failed for ARF database ddname.
RC=44 LOCATE for ARF database DSN failed.
RC=48 MVS Catalog record for ARF database cluster was found, but a problem was detected. The
reason code clarifies the problem:
RS=1 Catalog entity has no NAME field.
RS=2 ARF database is not a VSAM Cluster.
RS=3 ARF database is VSAM, but has no components.

CA-7.IARR –CA-7.IARR
RS=4 The primary ASSOC entity is not a Data component.

RS=5 The primary ASSOC entity has no NAME field.
RC=52 LOCATE for ARF database VSAM data component failed.
RC=56 MVS Catalog record for ARF database data component as found, but a problem was
detected. The information code clarifies the problem:
INF=1 Catalog entity has no High Used RBA field.
RC=60 MODCB for ARF DB ACB STRNO=1 (Load processing) failed.
RC=64 OPEN for Load (Create) failed.
RC=68 GETMAIN for Load RPL failed.
RC=72 GENCB for Load RPL failed.
RC=76 PUT for initial (create) record failed.
RC=80 CLOSE from Load (Create) failed.
RC=84 MODCB for ARF DB ACB STRNO=max (return to normal) failed.
RC=88 Normal OPEN for ARF database had a problem. The reason code is OPEN's return code:
RS=4 Warning message was issued, but ARF DB is OPEN.
RS=8 ARF DB OPEN failed.
The information code is OPEN's reason code:
INF=104 VSAM timestamp in ARF DB does not match timestamp in ICF catalog
(volume restore has occurred).
INF=128 CA7ARFDB DD is missing or invalid.
INF=136 CA-7 REGION size is too small to OPEN.
INF=168 ARF DB is currently OPEN for update by another address space.
CA-7.IARR SASSIARR PROCESSING BYPASSED.

Explanation: Only part of the ARF initialization processing has been done. This is normal if the
CA-7 startup parameters included a RESTART control statement with ARF=NO or ARF=MAINT.
User Response: Check for previous error messages, and make necessary corrections.
CA-7.IARR xxxxx JOBS ON qqqqqqqq QUEUE, yyyyy JOBS USED ARF.

Explanation: If ARF is used, CA-7 will read the queues at initialization and will attempt to locate
all jobs using ARF that were monitored by ARF at the time of the last /SHUTDOWN. To determine
this, CA-7 will read the request, ready, and active queues.
In this message, the name of the queue read is qqqqqqqq. The number of jobs found on the queue is
xxxxx. The number of jobs monitored by ARF is yyyyy.
User Response: None. This message is informational only.

CA-7.IARR –CA-7.IJCK
CA-7.IARR xxxxx ARF TRAILERS FOUND ON qqqqqqqq QUEUE, yyyyy RECONNECTED.

Explanation: If ARF is used, CA-7 will read the queues at initialization and will attempt to locate
all jobs using ARF that were monitored by ARF at the time of the last /SHUTDOWN. To determine
this, CA-7 will read the REQUEST, READY and ACTIVE queues. In order to resume ARF moni-
toring for a job, CA-7 must relocate the ARFSET that it used at the time of the /SHUTDOWN.
When the ARFSET is relocated, the job is said to be 'reconnected.'
In this message, the name of the queue read is qqqqqqqq. The number of jobs found on the queue
that were monitored at the time of the last /SHUTDOWN is xxxxx. The number of jobs for which
ARF resumed monitoring is yyyyy.
CA-7.ICM1-90 NCF NODE TABLE NOT DEFINED - IPL REQUIRED

Explanation: The NCF node control table was not found.
User Response: ICOM continues without NCF support active.
Operator Response: The ICOM reply NCF=YES can only be entered if NCF is properly installed.
CA-7.ICM1-91 NETWORK COMMUNICATION FACILITY NOT ACTIVE

Explanation: The CA-7 NCF interface is not active. This is an informative message only.
User Response: Processing continues without NCF support active.
Operator Response: None, unless NCF should be active. If so, it should be started.
CA-7.ICM1-92 NCF IS PRESENT - LOCAL NODE=xxxxxxxx

Explanation: The CA-7 NCF interface is active with your installation's node ID as shown.
User Response: Processing continues.
Operator Response: None. This is an informative message.
Programmer Response: None. This is an informative message.
CA-7.IJCK JCLCHECK INTERFACE BUFFER SIZE IS nnnnn.

Explanation: The buffer size used by the JCLCHECK interface is indicated by the nnnnn value.
User Response: None. This message is informational.
CA-7.IJCK MULTIPLE JCLCHECK STATEMENTS IGNORED

Explanation: More than one JCLCHECK statement was found in the CA-7 initialization file. Only
the first one is honored. Issued by SASSIJCK.
User Response: Remove the extraneous JCLCHECK statements.

CA-7.IJCK –CA-7.IJCK
CA-7.IJCK MULTIPLE KEYWORDS IGNORED, KW=

Explanation: Multiple occurrences of the same JCLCHECK statement keyword were encountered.
Only the first occurrence is honored.
User Response: Remove the extraneous JCLCHECK statement keywords.
CA-7.IJCK UNABLE TO OPEN DDNAME=xxxxxxxx, KEYWORD BYPASSED

Explanation: An attempt to OPEN the JCLCHECK options file failed.
User Response: Check that the name on the DD statement defining the options file matches the
DDNAME parameter on the JCLCHECK statement.
CA-7.IJCK MAXUSERS SPECIFIED ZERO VALUE

Explanation: MAXUSERS=0 was coded on the JCLCHECK statement. The interface is effectively
disabled.
User Response: If a MAXUSERS limit is desired, code a nonzero value on the keyword.
CA-7.IJCK UNABLE TO LOAD JCLCHECK, INTERFACE DISABLED

Explanation: The JCLCHECK module could not be LOADed. The interface is disabled.
User Response: Ensure that the JCLCHECK module is resident or in a library in the STEPLIB
concatenation for CA-7.
CA-7.IJCK SEVERE ERROR PROCESSING USER OPTIONS

Explanation: An error occurred processing CA-JCLCHECK user options. Processing terminated.
User Response: Check the options file for syntax errors and rerun.
CA-7.IJCK ERROR IN JCLCHECK USER OPTIONS AT POSITION xxx ON CARD yyy

Explanation: An error occurred processing CA-JCLCHECK user options at the specified position
(counting from column 1) on the statement indicated. Processing continues with the next option.
User Response: Correct indicated errors and rerun.
CA-7.IJCK THE FOLLOWING JCLCHECK OPTIONS IN EFFECT :

Explanation: This is a summary of the CA-JCLCHECK options which will be used when
JCLCHECK is called from the interface.
CA-7.IJCK MAXIMUM NUMBER OF CA-7/CA-JCLCHECK INTERFACE USERS IS nnn

Explanation: This message is produced if the MAXUSERS parameter is coded.

CA-7.IJCK –CA-7.IJLM-02
CA-7.IJCK NO MAXUSERS VALUE SPECIFIED.

Explanation: This message is produced if the MAXUSERS parameter is not coded.
CA-7.IJCK AUTOPROC OPTION SPECIFIED BUT USER HAS SYSPROC DD.

Explanation: The AUTOPROC option is not allowed if the DD statement for SYSPROC is found.
User Response: If the AUTOPROC option is desired, remove the SYSPROC DD statement from
CA-7's startup PROC.
CA-7.IJCK AUTOPROC OPTION SPECIFIED BUT USER NOT JES2.

Explanation: The AUTOPROC option is allowed only if CA-7 is running in a JES2 environment.
User Response: Remove the AUTOPROC option from the options file.
CA-7.IJCK AUTOPROC OPTION SPECIFIED BUT USER NOT AUTHORIZED.

Explanation: The AUTOPROC option is allowed only if CA-7 is APF authorized.
User Response: If the AUTOPROC option is desired, make certain that CA-7 is APF authorized.
CA-7.IJCK NO SYSPROC/AUTOPROC. INTERFACE DISABLED.

Explanation: The SYSPROC DD statement was not found in the CA-7 startup PROC and
AUTOPROC was not a valid specification. The CA-7 CA-JCLCHECK interface is disabled.
User Response: Either code a SYSPROC DD statement in the CA-7 startup PROC pointing to your
installation procedure libraries or code AUTOPROC in the options file.
CA-7.IJCK JCLCHECK COMMON COMPONENT INTERFACE LOADED.

Explanation: The JCLCHECK common component interface module CAZ2CJCL has been loaded
and will be used for JCL syntax checking.
CA-7.IJLM-01 NO STORAGE AVAILABLE

Explanation: No storage was available to construct a JCL table entry.
User Response: CA-7 abnormally terminates with a U001. Increase the region size specified for
CA-7 and restart CA-7.
CA-7.IJLM-02 GENERIC GET FAILED

Explanation: Unable to locate first JCL record.
User Response: CA-7 abnormally terminates with a U002. Contact Computer Associates Technical
Support.

CA-7.IJLM-03 –CA-7.ILCA
CA-7.IJLM-03 GET FOR UPDATE FAILED

Explanation: Unable to acquire JCL record for update.
Support.
CA-7.IJLM-04 DELETE FAILED

Explanation: Unable to delete JCL record.
Support.
CA-7.IJLM-05 ADD FAILED

Explanation: Unable to add JCL record.
Support.
CA-7.IJLM-20 JCLDSENT RECORD CONVERTED

Explanation: During startup of CA-7, a symbolic JCL data set entry in the database was found in
an old format, and has been automatically converted to the new format. The message is issued only
once, even if multiple entries are converted.
User Response: None. This is for information only.
CA-7.ILCA CALENDAR ACCESS VIA SLOAD

Explanation: No CALENDAR statement was found in the CA-7 initialization file. The CALMOD
transaction cannot be used to dynamically update calendars.
CA-7.ILCA xxxxxxxx NOW ON CALENDAR LIBRARY

Explanation: The module named at xxxxxxxx has been copied from the CA-7 Loadlib to the PDS
named on the CALENDAR statement in the CA-7 initialization file.
CA-7.ILCA xxxxxxxx LOAD FAILED

Explanation: CA-7 was unable to LOAD the calendar module even though a CALBLK statement
was found that named the calendar. This calendar could not be copied to the PDS named on the
CALENDAR statement.
User Response: Ensure that the calendar resides on a library in the CA-7 STEPLIB concatenation.

CA-7.ILCA –CA-7.INIT
CA-7.ILCA xxxxxxxx ALREADY ON CALENDAR LIBRARY

Explanation: The module named was not copied from STEPLIB to the calendar PDS because a
module with the same name was found on the calendar PDS.
User Response: If the module in the STEPLIB is to replace the module in the calendar PDS, then
use the REFRESH function on the CALMOD screen, otherwise no action need be taken.
CA-7.ILCA xxxxxxxx ERROR IN ADDING TO CALENDAR LIBRARY

Explanation: An error occurred while trying to add a module to the calendar PDS. This message
will be accompanied by an additional diagnostic message.
User Response: Respond to the CA-7.ILCA message indicating the reason for the failure to add the
calendar.
CA-7.ILCA text
Explanation: Check the SM50-14 message on page 7-32 for a comparison of the text value.
User Response: Take the action as indicated for the SM50-14 message.
CA-7.INAP INSUFFICIENT AINB STORAGE

Explanation: Storage sufficient to build an AINB control block was not available in subpool 7.
VTAM user data accompanying the VTAM LOGON will not be recognized by CA-7. A CA-7
/LOGON will be required AFTER the terminal is connected to CA-7.
User Response: Increase the region size specified for CA-7 and restart CA-7.
CA-7.INCD COMMDS ON xxxxxx ddd

Explanation: This informational message is produced each time CA-7 or ICOM is started or for
each run of the BTI (SASSBSTR). The message tells where the Communications data set is located.
Issued by SASSINCD. Where:
xxxxxx = the disk volume on which the data set resides.
ddd = SHR if the unit is SYSGENed as SHR; otherwise, it is blanks.
CA-7.INIT CA-DRIVER INTERFACE INITIALIZED

Explanation: The CA-Driver automatic parameter substitution facility has been made active based
on the presence of the CARPROC DD statement.
CA-7.INIT CA-DRIVER INTERFACE INITIALIZATION FAILED

Explanation: The CA-Driver automatic parameter substitution facility has not initialized properly.
User Response: Refer to other initialization messages. If the problem persists, contact your CA-7
specialist.

CA-7.INIT –CA-7.INTM
CA-7.INIT UNABLE TO LOAD CA7MDRV0

Explanation: The CA-Driver automatic parameter substitution facility has not initialized properly.
The module CA7MDRV0 could not be located.
User Response: Confirm that the proper CA-7 load library is accessible to the CA-7 address space
through steplib, linklib or LPA. If the problem persists, contact your CA-7 specialist.
CA-7.INTM MULTIPLE NETMAN STATEMENTS IGNORED.

Explanation: More than one NETMAN statement was found in the initialization file. Only one
will be honored.
CA-7.INTM LENGTH OF xxxxxxxx VALUE EXCEEDED MAXIMUM ALLOWABLE.

Explanation: Length of the value supplied for the NETMAN statement keyword named is greater
than the maximum allowed.
User Response: Correct the keyword value and retry.
CA-7.INTM UNABLE TO LOAD PROCESSING EXIT xxxxxxxx

Explanation: An error occurred during the attempt to load the module named in the error message.
This name is determined by the NETMAN statement keyword EXIT=.
User Response: Ensure that the module named resides on a library that is accessible to CA-7 and
retry.
CA-7.INTM NORMAL COMPLETIONS WILL BE IGNORED.

Explanation: Unless GOODCOMP=Y is specified on the NETMAN statement, jobs that complete
normally whose restart count is zero will be ignored by the problem management interface.
CA-7.INTM UNABLE TO ACQUIRE SUFFICIENT STORAGE FOR PROBLEM MANAGEMENT

SYSTEM INTERFACE
Explanation: There was not enough storage available to initialize the problem management inter-
face. The interface requires approximately 1mB of virtual storage above the 16mB line.
User Response: Ensure that sufficient storage is available and retry.
CA-7.INTM UNABLE TO LOAD INTERFACE MODULE, NAME=xxxxxxxx

Explanation: An error occurred during the attempt to load the module named in the error message.
User Response: Ensure that the module named resides on a library that is accessible to CA-7 and
retry.

CA-7.INTM –CA-7.INTM
CA-7.INTM INVALID VALUE FOR KEYWORD, KEYWORD WAS xxxxxxxx

Explanation: An invalid value was supplied for the keyword named.
User Response: Correct the keyword value and retry. Consult the CA-7 Systems Programmer
Guide for detailed information on the NETMAN statement.
CA-7.INTM CA-NETMAN INTERFACE INITIALIZATION FAILED DUE TO PREVIOUSLY NOTED

ERRORS.
Explanation: CA-NETMAN interface initialization failed.
User Response: Refer to prior error messages for further details on the reasons for the failure.
CA-7.INTM DBASENM VALUE NOT SUPPLIED.

Explanation: The CA-NETMAN database name is required.
User Response: Supply the appropriate CA-NETMAN database name for the DBASENM keyword
on the NETMAN statement.
CA-7.INTM ATTACH FOR SASSPM00 FAILED, R15=xxxxxxxx

Explanation: The ATTACH for the problem management subtask failed. The return code from
ATTACH is supplied in the message.
CA-7.INTM OPEN FAILED FOR NETMAN DD.

Explanation: The OPEN for the model transaction file failed. This OPEN is attempted if the
NETMAN statement is included in the initialization file.
User Response: Ensure that there is a NETMAN DD statement in the JCL for CA-7 if the
CA-NETMAN interface is to be used.
CA-7.INTM INVALID CONTINUATION FOR NETMAN STATEMENT.

Explanation: A rule for continuation of a model transaction was violated.
User Response: The length of a model transaction cannot exceed 1000 bytes. A continuation is
indicated by ending a model transaction line with a '+'.
CA-7.INTM MUST BE AT LEAST MVS SP 2 TO USE CA-NETMAN INTERFACE.

Explanation: The operating system level was not MVS SP 2 or higher.
User Response: The operating system level must be at least MVS SP 2 to use the CA-NETMAN
interface.

CA-7.INTM –CA-7.INW3
CA-7.INTM ONE OR MORE VARIABLES UNDEFINED.

Explanation: Values for one or more of the variables on a NETMAN statement could not be
resolved.
User Response: Refer to the CA-7 Systems Programmer Guide for information on allowable
NETMAN statement variables.
CA-7.INTM DATA TRUNCATED.

Explanation: A value for one or more variables on a NETMAN statement was truncated because of
space limitations.
User Response: The length of a single transaction as defined in a statement in the NETMAN file
cannot exceed 1000 bytes.
CA-7.INTM ONE OR MORE PARAMETERS REQUIRED BY SASSNTMV NOT SUPPLIED.

Explanation: This is an internal error. At least one required parameter was not supplied on a call
to SASSNTMV.
CA-7.INTM UNKNOWN ERROR RETURNED FROM SASSNTMV.

Explanation: This is an internal error. An unrecognized return code from SASSNTMV was
received.
CA-7.INTM CA-NETMAN INTERFACE INITIALIZATION COMPLETE.

Explanation: The CA-NETMAN interface is initialized.
CA-7.INWC NO TRX TERMINALS DEFINED, SWITCHING TO ARF=MAINT

Explanation: CA-7 detected ARF=Y is specified on the RESTART statement, but no TRX devices
are defined. ARF requires at least one GROUP statement with DEVICE=TRXDV. See the CA-7
Systems Programmer Guide for more information. If no TRX device is defined, then ARF is
switched to run in MAINT mode. In MAINT mode, ARF does not track job exceptions and does not
execute recovery actions.
User Response: Define at least one TRX device for use with ARF.
CA-7.INW3 DELETE JOBS/NETWORK? REPLY YES/NO.

xxxxxxxx HAS BEEN DELETED FROM yyyyyyyy
Explanation: CA-7 has detected bad pointers to the TRLQ. CA-7 will attempt to recover during
WARM or ERST initialization by deleting the bad job(s) or network(s). Issued by SASSINW3.
User Response: If the operator replies NO, then no deletions will be done. If the operator replies
YES, CA-7 will delete the bad job(s)/network(s). For either a YES or NO response, the third WTO
message will be issued for every bad job and/or network, where xxxxxxxx is the job or network

CA-7.IOPT –CA-7.IOPT
name and yyyyyyyy is the queue from which it was deleted. If the operator replied NO, CA-7 will
abend with a U0927.
Note: CA-7 cannot initialize correctly with bad TRLQ pointers.
The job(s) and/or network(s) that were deleted will need to be analyzed to determine if they must be
resubmitted or not. Also, triggers and dependencies affected by the deleted entries will have to be
handled manually. However, if the yyyyyyyy value indicates the UCC7PRNQ, then no actions will
be required.
CA-7.IOPT CA-DRIVER COMMENT INDICATOR IS: nnnnnnnn

Explanation: This message reports the value of the DPROCCOM keyword on the OPTIONS state-
ment in the CA-7 initialization file. CA-Driver procedure statements that begin with nnnnnnnn will
not appear in expansions.
CA-7.IOPT CPM REQUIRES RSRC=Y ON DBASE STMT

Explanation: CPM=Y was coded on the OPTIONS statement in the CA-7 initialization file, but
VRM was not activated. VRM must be active to use CPM.
User Response: Activate VRM by coding RSRC=YES on the DBASE statement.
CA-7.IOPT CPM REQUIRES AT LEAST ONE CCI DEVICE

Explanation: CPM=Y was coded on the OPTIONS statement in the CA-7 initialization file, but no
terminals were defined with DEVICE=CCI.
User Response: Define at least one terminal specifying DEVICE=CCI.
CA-7.IOPT CPM ACTIVE

Explanation: CPM=Y was coded on the OPTIONS statement in the CA-7 initialization file.
CA-7.IOPT SHOULD CA-7 READ COMMDS EVERY FIVE SECONDS? REPLY TO CONFIRM
(YES/NO)
Explanation: CMGRDELAY=YES was specified on the OPTIONS statement in the CA-7 initial-
ization file.
Note: This keyword should only be used in consultation with Computer Associates Technical
Support. Inappropriate use of this option could adversely affect CA-7 performance.
User Response: Reply YES to cause CA-7 to wake up every five seconds to read the communi-
cations data set. If the reply is NO then CA-7 will continue to wake up every ten seconds for this
purpose.

CA-7.IOPT –CA-7.ISVC
CA-7.IOPT CA-7 WILL WAKE UP EVERY xxxx SECONDS TO READ THE COMMDS.
Explanation: CMGRDELAY=YES was specified on the OPTIONS statement in the CA-7 initial-
ization file. This message simply reports the number of seconds that elapsed between CA-7's reads
of the communications data set.
CA-7.IRES UNABLE TO LOAD SASSENFT, CA-7 WILL NOT CREATE EVENT RECORDS.
Explanation: The CA-7 ENF event definition table could not be LOADed.
User Response: Ensure that SASSENFT resides on a library accessible to CA-7 and retry.
CA-7.IRES UNABLE TO LOAD SASSENFO, CA-7 WILL NOT CREATE EVENT RECORDS.
Explanation: The CA-7 module that creates ENF events could not be LOADed.
User Response: Ensure that SASSENFO resides on a library accessible to CA-7 and retry.
CA-7.IRES UNABLE TO ACQUIRE SUFFICIENT STORAGE FOR ENF EVENT CREATION

Explanation: Insufficient storage was available for ENF event workareas.
User Response: Increase the region size for CA-7 by 1mB and retry.
CA-7.IRST ARF MONITORING ACTIVATED

Explanation: The Automatic Recovery Facility (ARF) has been made fully active based upon the
ARF=YES keyword on the RESTART initialization statement.
CA-7.IRST ARF DATA BASE SERVICES REQUESTED

Explanation: The database services for the Automatic Recovery Facility (ARF) has been made
active based upon ARF=MAINT keyword on the RESTART initialization statement. However, CA-7
will not monitor jobs for ARF recovery while in maintenance mode.
CA-7.ISVC XPS SERVER NOT INITIALIZED.

Explanation: CA-7 will not initiate XPS SERVER functions. This message is produced in
response to options specified on the SVCNO statement in the CA-7 initialization file.
User Response: If CA-7 XPS SERVER functions are needed, specify the appropriate options on the
SVCNO statement and restart CA-7.
CA-7.ISVC ROUTER=YES IGNORED BECAUSE MONITOR=NO.

Explanation: The XPS ROUTER will not run as a CA-7 subtask unless CA-7 is an XPS SERVER.
User Response: If the XPS ROUTER is to run as a subtask of this copy of CA-7, then specify an
appropriate value for MONITOR. Refer to the CA-7 Systems Programmer Guide for information on
the SVCNO initialization file statement keywords MONITOR and ROUTER.

CA-7.ISVC –CA-7.IVRM-05
CA-7.ISVC XPS SERVER INITIALIZED. MONITOR VALUE: nnnnnnn

Explanation: The CA-7 XPS SERVER has been initialized. The monitor value is reported.
CA-7.ISVC XPS ROUTER WILL NOT RUN IN THIS ADDRESS SPACE

Explanation: The XPS ROUTER will not run in this address space. This message may be issued
during the initialization of the test copy of CA-7. In the typical configuration the XPS ROUTER
runs as a subtask of the production copy of CA-7. In such a case, the test copy of CA-7 may act as
a second CA-7 XPS SERVER on the same machine by specifying the appropriate value on the
MONITOR keyword of the SVCNO statement. No additional copies of the XPS ROUTER may be
activated. Although there may be up to two CA-7 XPS SERVERs at a CAIENF node, there must be
one and only one active copy of the XPS ROUTER.
User Response: If the XPS ROUTER is active on another copy of CA-7 at this CAIENF node, then
no action is required. If the XPS ROUTER is not active on another copy of CA-7 at this CAIENF
node, then ROUTER=YES should be coded on the SVCNO statement in the CA-7 initialization file.
CA-7.ISVC XPS ROUTER WILL RUN IN THIS ADDRESS SPACE

Explanation: The XPS ROUTER will run as a subtask of this copy of CA-7. One and only one
copy of the XPS ROUTER must be active at any CAIENF node where CA-7 XPS SERVER func-
tions are required.
CA-7.IVRM-02 ACTIVE JOB CHAIN NOT CREATED

Explanation: During CA-7 startup, VRM found no active records on the job chain.
CA-7.IVRM-03 ACTIVE JOB CHAIN CREATED

Explanation: During CA-7 startup, VRM has rebuilt the active job chain.
CA-7.IVRM-04 CO-REQ RSRC ACTIVE CHAIN NOT CREATED

Explanation: During CA-7 startup, VRM found no active records on the co-req chain.
CA-7.IVRM-05 RESOURCE COUNT ACTIVE CHAIN NOT CREATED

Explanation: During CA-7 startup, VRM found no active records on the resource count chain.

CA-7.IVRM-06 –CA-7.IVRM-13
CA-7.IVRM-06 NON-FREED RESOURCE CHAIN CREATED

Explanation: During CA-7 ERST, WARM, or MOVQ startup, VRM found active nonfreed
resource records.
CA-7.IVRM-07 NON-FREED RSRC CHAIN NOT CREATED

Explanation: During CA-7 startup, VRM found no active records for nonfreed resources.
CA-7.IVRM-08 VRM INITIALIZATION COMPLETE

Explanation: This message is displayed during CA-7 startup when VRM is initialized.
CA-7.IVRM-09 COREQUISITE RESOURCE RECORDS DELETED.

Explanation: During CA-7 COLD or FORM startup, VRM deleted all active corequisite resource
records.
CA-7.IVRM-10 RESOURCE COUNT RECORDS DELETED.

Explanation: During CA-7 COLD or FORM startup, VRM deleted all active resource count
records.
CA-7.IVRM-11 CA-7 COLD START - ALL PREVIOUS RESOURCE RECORDS DELETED.

Explanation: During CA-7 COLD or FORM startup, VRM deleted all active resource records. The
RM.7 definitions will be retained, but the CURR IN USE counts will be cleared (set to zero).
CA-7.IVRM-12 ERROR ON GETUPD OF COREQUISITE RESOURCE RECORD.

Explanation: During CA-7 COLD or FORM startup, an error occurred on a GET for an update of a
corequisite job resource record.
User Response: CA-7 abnormally terminates with a U0128. Contact Computer Associates Tech-
nical Support.
CA-7.IVRM-13 ERROR ON GETUPD OF RESOURCE COUNT RECORD.

Explanation: During CA-7 COLD or FORM startup, an error occurred on a GET for update of a
resource count record.
nical Support.

CA-7.IVRM-14 ERROR ON DELETE OF COREQUISITE RESOURCE RECORD.

Explanation: During CA-7 COLD or FORM startup, an error occurred on a delete of a corequisite
resource record.
User Response: CA-7 terminates with a U0130. Contact Computer Associates Technical Support.
CA-7.IVRM-15 ERROR ON DELETE OF RESOURCE COUNT RECORD.

Explanation: During CA-7 COLD or FORM startup, an error occurred on a delete of a resource
count record.
nical Support.
CA-7.IVRM-16 NO COREQUISITE RESOURCE RECORD(S) TO BE DELETED.

Explanation: During CA-7 COLD or FORM startup, VRM did not locate any corequisite resource
records to delete.
CA-7.IVRM-16 MANUAL RESOURCE COUNT CHAIN NOT CREATED

Explanation: During CA-7 startup, VRM found no active records on the manual resource count
chain.
CA-7.IVRM-17 NO RESOURCE COUNT RECORD(S) TO BE DELETED

Explanation: During CA-7 COLD or FORM startup, VRM did not locate any resource count
resource records.
CA-7.IVRM-18 ERROR ON GETU OF ACTIVE JOB RESOURCE RECORD.

Explanation: During CA-7 COLD or FORM startup, an error occurred during a GET of an active
job resource record.
nical Support.
CA-7.IVRM-19 ERROR ON DELETE OF ACTIVE JOB RESOURCE RECORD.

Explanation: During CA-7 COLD for FORM startup, an error occurred on delete of an active job
resource record.
User Response: CA-7 abnormally terminates with a U0122 abend. Contact Computer Associates
Technical Support.

CA-7.IVRM-20 ALL ACTIVE JOB RESOURCE RECORDS DELETED.

Explanation: During CA-7 COLD or FORM startup VRM deleted all active job resource records.
CA-7.IVRM-21 NO NON-FREED RESOURCE RECORDS TO BE DELETED.

Explanation: During CA-7 COLD or FORM startup, VRM did not locate any nonfreed resource
records to be deleted.
CA-7.IVRM-22 ERROR ON DELETE OF NON-FREED RESOURCE RECORD.

Explanation: During CA-7 COLD or FORM startup, an error occurred on a delete of a nonfreed
resource record.
CA-7.IVRM-23 ERROR ON GETUPD OF NON-FREED RESOURCE RECORD.

Explanation: During CA-7 COLD or FORM startup, an error occurred on an update of a nonfreed
resource record.
CA-7.IVRM-24 NO ACTIVE JOB RESOURCE RECORD(S) TO BE DELETED.

Explanation: During CA-7 COLD or FORM startup VRM did not locate any active resource
records to delete.
CA-7.IVRM-26 RESOURCE COUNT CHAIN CREATED.

Explanation: During CA-7 ERST, WARM, or MOVQ startup VRM found active resource count
records in the VRM database.
CA-7.IVRM-27 NON-FREED RESOURCE RECORDS DELETED.

Explanation: During CA-7 COLD or FORM startup, VRM deleted all nonfreed active job resource
records.
CA-7.IVRM-29 NO MANUAL RESOURCE COUNT RECORDS TO BE DELETED

Explanation: During CA-7 COLD or FORM startup VRM did not locate any manual resource
count records to delete.

CA-7.IVRM-30 –CA-7.JCKI
CA-7.IVRM-30 CPM FLOW CHAIN NOT CREATED

Explanation: During CA-7 startup no active FLOW records were found.
CA-7.IVRM-31 NO CPM FLOW RECORDS TO DELETE.

Explanation: During a COLD or FORM start of CA-7, no FLOW records were found.
CA-7.I32V FREE FOR VIRTUAL TERMINAL FAILED

Explanation: The logon ID for a terminal defined as virtual could not be found. The terminal
could not be freed. Issued by SASSD32V and SASSI32V.
User Response: If error persists, contact your installation's CA-7 specialist for assistance.
CA-7.I32V CONNECTION COMPLETE (xxxxxxxx=yyyyyyyy)

Explanation: Where:
xxxxxxxx Reflects the CA-7 name.
yyyyyyyy Reflects the VTAM ID.
Issued by SASSI32V.
CA-7.I32V APPLID(aaaaaaa) TERM(ttttttt) LU(lllllll)

Explanation: A successful connection has been made to CA-7, where:
aaaaaaa CA-7 application name.
ttttttt CA-7 terminal name.
lllllll VTAM Logical Unit.
CA-7.JCKI UNABLE TO ATTACH JCLCHECK SUBTASK

Explanation: An error occurred attempting to ATTACH the subtask which calls the JCLCHECK
module. Issued by SASSJCKI.
CA-7.JCKI LIMIT OF INTERFACE USERS REACHED, TRY AGAIN LATER

Explanation: The limit set by the MAXUSERS value on the JCLCHECK statement in the CA-7
initialization file was reached. Issued by SASSJCKI.
User Response: Wait and try the command again later or increase the MAXUSERS value.

CA-7.JCKI –CA-7.LGON
CA-7.JCKI JCLCHECK SUBTASK ENDED ABNORMALLY, TCBCMP=xxyyyzzz

Explanation: A JCLCHECK subtask abended. yyy is the system abend code (hex) and zzz is the
user abend code (hex). Issued by SASSJCKI.
User Response: If the yyy value in the TCBCMP field is 80A, try increasing the region size for
CA-7, otherwise collect any dumps produced and contact your CA-7 specialist for assistance.
CA-7.JCKI DETACH FAILED FOR JCLCHECK SUBTASK

Explanation: An error occurred attempting to DETACH the subtask which calls the JCLCHECK
module. Issued by SASSJCKI.
User Response: No action is necessary unless the message appears frequently. In that case, save
console logs, run report HR02 for the time around the error and contact Computer Associates Tech-
nical Support for assistance.
CA-7.JCKI JCLCHECK SUBTASK INITIALIZATION FAILED

Explanation: An attempt to start the task which calls the JCLCHECK module has failed. Issued by
SASSJCKI.
CA-7.JCLERR text
Explanation: Some error occurred during JCL submission, requiring CA-7 to flush the job by
causing a JCL error. This message only appears in a // JCL statement. The text part of the message
is the same as an error message issued to the master station to describe the error. The text part of
the message can be found elsewhere in this manual. Issued by SASSSSM0.
User Response: Correct the error and reexecute the job.
CA-7.LGON LGON VTAM INQUIRE FAILED FOR xxxxxxx / zzzzzzzz

Explanation: This WTO is produced if the VTAM INQUIRE macro has a bad return code.
xxxxxxx is the CA-7 terminal name. zzzzzzzz is the VTAMID. This WTO is followed by another
for CA-7.V001 displaying the bad code. Issued by SASSLGON.
User Response: If the terminal indicated cannot be used by CA-7, check the VTAM codes in the
V001 messages. If you are unable to resolve the problem, contact your installation's CA-7 specialist
for assistance.
CA-7.LGON INQUIRE FAILED FOR nnnnnnnn

Explanation: A VTAM INQUIRE macro failed for the ACB named in the message. ISPF sessions
will not be able to connect to CA-7 if this message is produced.
User Response: Note the ACB named in the message and contact Computer Associates Technical
Support.

CA-7.LGON –CA-7.LMGR
CA-7.LGON SHOWCB FAILED. AUTOLOGON REJECTED

Explanation: A VTAM SHOWCB macro failed during the attempt to build CA-7 logon information
from the VTAM user data supplied on the connection request. A CA-7 /LOGON will be required
after the terminal is connected to CA-7.
User Response: If the error persists, contact Computer Associates Technical Support.
CA-7.LGON ERROR LOCATING SCT FOR xxxxxxxx

Explanation: The SCT named at xxxxxxxx could not be found to build the CA-7 logon information
from the VTAM user data supplied on the connection request. A CA-7 /LOGON will be required
after the terminal is connected to CA-7.
CA-7.LINK L2DATES SERVICE INIT COMPLETE

Explanation: The internal date services routines have initialized successfully.
CA-7.LINK L2DATES SERVICE INIT FAILED

Explanation: The internal date services routines did not initialize properly.
User Response: Contact your CA-7 specialist.
CA-7.LINK SASSTMNT SERVICE INIT COMPLETE

Explanation: The internal table services routines have initialized successfully.
CA-7.LINK SASSTMNT SERVICE INIT FAILED

Explanation: The internal table services routines did not initialize properly.
User Response: Contact your CA-7 specialist.
CA-7.LMGR ERROR CODE=FVn TERM=xxxxxxx

Explanation: An error was detected by CA-7 while attempting to process an internal CA-7 terminal
buffer. xxxxxxx is the terminal associated with the error. n is an error code used for debugging.
Issued by SASSLMGR.
User Response: If the terminal continues to process normally, no action is required. Otherwise, the
following sequence of CA-7 commands should be used to regain the terminal:
/STOP,T=xxxxxxx
/PURGPG,LT=xxxxxxx
/START,T=xxxxxxx
Where xxxxxxx is the terminal name from the error message. /PURGPG may require a station name
other than the one indicated in message.
Note: If printer problem, station is probably MASTER.

CA-7.LOST –CA-7.MA31
CA-7.LOST (xx,yy) SYN CLSDST FOR xxxxxxx

Explanation: The connection was lost between the terminal xxxxxxx and CA-7. This message may
be accompanied by other terminal error messages including CA-7.V001. The return codes from reg-
isters 15 and 0 are represented by xx and yy, respectively. Issued by SASSLOST.
User Response: If the terminal is not connected to CA-7, try the following sequence of commands
to regain it:
/STOP,T=xxxxxxx
/CLOSE,T=xxxxxxx
Then vary the terminal inactive and active through VTAM.
/OPEN,T=xxxxxxx
/START,T=xxxxxxx
If the terminal is still not connected, then shut down CA-7 and bring it back up with a specific
TYPE=ERST.
CA-7.MAIN CORE TAG CHECK FAILED, R1=xxxxxxxx R6=xxxxxxx

Explanation: A storage integrity violation is suspected.
CA-7.MAIN LENGTH CHECK FAILED, R0=xxxxxxxx R1=xxxxxxx

CA-7.MAIN R10=xxxxxxxx R11=xxxxxxxx R14=xxxxxxxx

CA-7.MA31 CORE TAG CHECK FAILED, R1=xxxxxxxx R6=xxxxxxx

User Response: If a WARM start of CA-7 fails, attempt an ERST start. If the problem persists,
CA-7.MA31 LENGTH CHECK FAILED, R0=xxxxxxxx R1=xxxxxxxx


CA-7.MA31 –CA-7.NC104
CA-7.MA31 R10=xxxxxxxx R11=xxxxxxxx R14=xxxxxxxx

CA-7.NC101 UNKNOWN COMMAND IGNORED

Explanation: An operator command was not entered properly. A parameter was missing or incor-
rectly specified.
User Response: The command is ignored, and processing continues.
Operator Response: Reenter the correct command.
CA-7.NC102 VTAM TERMINATION CODE=xxxx

Explanation: The VTAM subtask terminated abnormally. xxxx is the completion code from the
subtask. The level of this error is catastrophic.
User Response: Processing halts.
Operator Response: Notify your installation's CA-7 specialist.
Programmer Response: Find the cause of the termination and correct.
CA-7.NC103 INVALID PARAMETER ENTERED

Explanation: The JCL parameter on the EXEC statement was not coded correctly. The level of
this error is serious.
Operator Response: Correct the JCL parameter and rerun the job.
CA-7.NC104 UNKNOWN NODE TABLE FULL

Explanation: There is no more room in the Unknown Node Table, the table which contains infor-
mation on nodes which have data but are not in the node table. The level of this error is serious.
User Response: Data for that node and all future unknown nodes will be lost. Processing con-
tinues.
Operator Response: Do a STATUS command to display the undeliverable block counts. If any
unknown nodes have zero undeliverable blocks, a SHUTDOWN and STARTUP will clear them from
the Unknown Node Table. In addition, to make room in the Unknown Node Table, data may be
purged prior to the SHUTDOWN/STARTUP.
Programmer Response: Verify that the node table (UCC7NODE) specifies the correct node names.
If the Unknown Node Table needs to be enlarged, contact Computer Associates Technical Support.

CA-7.NC105 –CA-7.NC109
CA-7.NC105 SHUTDOWN COMPLETE

Explanation: The shutdown process has been completed successfully.
Operator Response: A STOP or STARTUP command may be issued.
CA-7.NC106 INTERNAL LOGIC ERROR - ABENDING

Explanation: The program has detected an illogical situation. The level of this error is cat-
astrophic.
User Response: The task terminates abnormally.
Programmer Response: This is a probable program error. Save all JCL, console listings and
dumps and report the problem to Computer Associates Technical Support.
CA-7.NC107 NODE TABLE (tttttttt) NOT FOUND - ABENDING

Explanation: The load of the node table was not successful. tttttttt is the member name of the
node table not found. The level of this error is catastrophic.
User Response: Processing halts, and the program abnormally terminates.
Operator Response: None.
Programmer Response: Ensure that the TABLE= parameter on the EXEC statement contains the
correct table name. Ensure that the JOBLIB/STEPLIB cards provide the library that contains the
table specified. If no TABLE= parameter is specified, ensure that a node table exists with the name
UCC7NODE.
CA-7.NC108 ERROR PROCESSING UDQ FILE - ABENDING

Explanation: An error has occurred opening or reading the Undeliverable queue. The level of this
error is catastrophic.
User Response: Processing halts, and the program abnormally terminates.
Programmer Response: Ensure the file exists and is correct. If not a user error, save all listings
and dumps and notify Computer Associates Technical Support.
CA-7.NC109 ERROR PROCESSING NCF FILE - ABENDING

Explanation: An error has occurred opening or accessing the CA-7 NCF Communications data set.
The level of this error is catastrophic.
User Response: Processing halts and the program abnormally terminates.
Programmer Response: Ensure the file exists and is correct. If not a user error, save all listings
and dumps and notify Computer Associates Technical Support.

CA-7.NC110 –CA-7.NC194
CA-7.NC110 CA-7 NCF INTERNAL ERROR - xxxxx

Explanation: CA-7 has detected an internal error which cannot be processed. xxxxx is the internal
error code. The level of this error is catastrophic.
User Response: Processing halts and the program abnormally terminates.
Programmer Response: Save all listings and dumps and notify Computer Associates Technical
Support.
CA-7.NC113 CA-7 SYSTEM INTERFACES NOT PRESENT IN THE SYSTEM - ABENDING

Explanation: A control block setup by CAS9 for CA-7 could not be found.
User Response: Make sure that CAS9 has run on the system and the ICMDSECT has been zapped
for NCF.
CA-7.NC114 CA-7 SYSTEM INTERFACES NOT INITIALIZED TO SUPPORT NCF - ABENDING

Explanation: The ICMDSECT module has not been modified to indicate that NCF is installed.
User Response: Modify the ICMDSECT to indicate NCF is installed. A CAS9 REINT=COLD for
CA-7 (or IPL) will be required.
CA-7.NC190 xx..xx
Explanation: This is a redisplay of the modify input to NCF.
CA-7.NC191 ------------------ CA-7/NCF VTAM STATUS ------------------

Explanation: This is heading output for the NCF STATUS command.
CA-7.NC192 --NODE-- (ID) - STATUS- -LUTYPE- -RECV- -SENT- UNDL -PURG-

Explanation: This is the heading for the NCF STATUS command.
CA-7.NC193 xx..xx
Explanation: This is a data line for an NCF node.
CA-7.NC194 NCF QUEUE.. xx% USED UND QUEUE.. yy% USED

Explanation: This is a final line of output from an NCF STATUS command.

CA-7.NC201 –CA-7.NC202
CA-7.NC201 eeeeeeee (mmmmmmmm) oooooooo R15=cc RTNCD(FDBK2)=rr(ff)

SSENSMI(USENSEI)=ss(uuuu)
Explanation: This message will occur when a VTAM error is encountered for a RECEIVE or a
SETLOGON macro. For a further explanation of the error, refer to the "Return Code and Sense
Fields" section in the IBM ACF/VTAM Programming Manual.
eeeeeeee is a text representation of the error condition which has occurred.
mmmmmmmm is the VTAM macro name which caused the error.
oooooooo is a representation of any special options which were used in the invocation of the macro.
cc is the hex value contained in register 15 on exit from the macro.
rr is the hex value for the RTNCD field in the RPL.
ff is the hex value for the FDBK2 field in the RPL.
ss is the hex value for SSENSMI field in the RPL.
uuuu is the hex value for USENSEI field in the RPL.
User Response: The system action is dependent on the macro involved and the type of error. Refer
to the table listed below. If any error is not listed in the table, the default action, which is to con-
tinue processing, will be used.
Macro RTNCD FDBK2 Action

RECEIVE X'10' X'07' Terminate the session
X'10' X'09' Terminate the session
X'14' User abend CF6
SETLOGON X'14' User abend CF6
Operator Response: Notify the systems programmer.

Programmer Response: Consult the explanation of the error in the IBM ACF/VTAM Programming
Manual under "Return Codes and Sense Fields." Attempt to determine the severity and cause of the
error. If unable to determine and fix the cause of the problem, contact Computer Associates Tech-
nical Support.
CA-7.NC202 VTAM ERROR (OPEN) nnnnnnnn ERROR=ee

Explanation: An error occurred during the OPEN ACB to establish communication with VTAM.
nnnnnnnn is the APPLID that was trying to OPEN the ACB.
ee is the error field in the ACB after the unsuccessful OPEN of the ACB. Refer to the IBM
ACF/VTAM Programming Manual under the OPEN macro for an explanation of the error codes.
User Response: The program ends with an abnormal termination.
Operator Response: Notify your installation's CA-7 specialist. Check the nodes (APPL) and cross
domains to make sure they are active in VTAM.

CA-7.NC203 –CA-7.NC206
Programmer Response: Ensure that the ACF/VTAM parameters have been specified correctly.
Refer to the specific error code values for the resolution. Check the UCC7NODE module to make
sure the entries are specified correctly and that the first entry is the local node.
CA-7.NC203 NETWORK INITIALIZATION LIMIT EXCEEDED - PROCESSING CONTINUES

Explanation: This is a warning message. Not all of the asynchronous OPNDSTs have completed
within the time limit specified in the JCL parameter. Data transmission will commence and the
outstanding OPNDSTs will complete without waiting for the asynchronous ones.
Programmer Response: If this message occurs frequently, the system initialization parameter
TIME= on the JCL can be increased. If a SEND data is attempted before the logon completes for
that node, all data for that node will go to the Undeliverable queue.
CA-7.NC204 UNDELIVERABLE DATA FILE FULL - DATA LOST

Explanation: The Undeliverable queue is full. Data must be purged or sent before any more data
can be written to this data set. Warning messages should have preceded this error at 80 percent, 85
percent, 90 percent, and 95 percent plus. The level of this error is serious.
User Response: Undeliverable data is lost. Processing continues.
Operator Response: Inactive nodes can be logged on to receive data or a PURGE command can be
issued to make room on the data set.
Programmer Response: If this occurs regularly, the size of the Undeliverable queue should be
increased.
CA-7.NC205 NODE NOT FOUND IN UCC7NODE TABLE, DATA UNDELIVERABLE. NODE=nnnnnnnn

Explanation: This is a warning message. Data was read from the NCF Communications data set
for a node which was not defined in the UCC7NODE table. An entry was created in the Unknown
Node Table and all its data will go to the Undeliverable queue. nnnnnnnn is the node which was not
found in the table.
Programmer Response: Determine if the node table was specified correctly. If the node is incor-
rect or the data is not needed, it may be purged.
CA-7.NC206 UNDELIVERABLE QUEUE THRESHOLD REACHED - xx PERCENT FULL

Explanation: This is a warning message. This message will be produced the first time the UDQ
(Undeliverable queue) percentage exceeds 80 percent, 85 percent, and 90 percent. It will be
produced for every WRITE operation that exceeds 95 percent. The threshold is reset whenever the
percentage drops below 80 percent. xx is the actual percentage of space used in the Undeliverable
queue.

CA-7.NC207 –CA-7.NC209
Operator Response: Issue the STATUS command and then look for inactive nodes. Remove data
from the Undeliverable queue, either by LOGON or PURGE commands, before it becomes full and
data is lost.
Programmer Response: If this occurs frequently, increase the size of the Undeliverable queue.
CA-7.NC207 UNKNOWN NODE TABLE FULL - LOSING STATUS INFORMATION FOR

NODE=nnnnnnnn
Explanation: This is a warning message. There is no more room in the Unknown Node Table for
this node. Statistics will not be kept for this node and its data cannot be purged from the UDQ.
This message will only be produced once when the limit is exceeded. nnnnnnnn is the unknown
node name.
Operator Response: If there are any entries in the table with zero undeliverable blocks, a
SHUTDOWN/STARTUP may be performed to purge them from the table.
Programmer Response: Ensure that the node table contains all possible entries necessary to
prevent this situation from happening.
CA-7.NC208 ERROR PROCESSING UDQ FILE - ABENDING

Explanation: An error occurred accessing the Undeliverable queue. The error could have occurred
on an OPEN, READ or WRITE operation. The level of this error is catastrophic.
User Response: Processing halts with abnormal termination.
Operator Response: Ensure the Undeliverable queue exists and is contained in the JCL. Notify
your installation's CA-7 specialist.
Programmer Response: Evaluate the I/O operation that was being performed at the time the error
occurred. Rebuild the data set only if necessary.
CA-7.NC209 ERROR PROCESSING NCF FILE - ABENDING

Explanation: An error occurred accessing the CA-7 NCF Communications data set. The error
could have occurred on an OPEN, READ or WRITE operation. The level of this error is cat-
astrophic.
User Response: Processing halts with abnormal termination.
Operator Response: Ensure that the CA-7 NCF Communications data set exists and is contained in
the JCL. Notify your installation's CA-7 specialist.
Programmer Response: Evaluate the I/O operation that was being performed at the time the error
occurred. Rebuild the data set only if necessary.

CA-7.NC301 –CA-7.NC302

Explanation: This message will occur when a VTAM error is encountered for an OPNDST, SEND,
CLSDST or TERMSESS macro. For further explanation of the error refer to the "Return Code and
Sense Fields" section in the IBM ACF/VTAM Programming Manual.
oooooooo is a representation of any special options which were used in this invocation of the macro.

OPNDST X'14' - User abend CF6
SEND X'10' X'07' Terminate the session
CLSDST X'14' User abend CF6
TERMSESS X'14' User abend CF6

Manual under "Return Code and Sense Fields." Attempt to determine the severity and cause of the
nical Support.
CA-7.NC302 SESSION ESTABLISHED WITH NODE (nnnnnnnn)

Explanation: This message is produced following successful processing of a CA-7 NCF LOGON
command. Communication is now established with the node specified.

CA-7.NC303 –CA-7.NC304
CA-7.NC303 LOGOFF REQUEST COMPLETE FOR NODE=nnnnnnnn

Explanation: Communications have been discontinued with the node specified in the message. The
break in communications was initiated by this node. nnnnnnnn is the node with which communi-
cations have been broken.
CA-7.NC304 LOGON FAILED - NODE (xxxxxxxx)

Explanation: This message should follow an error message (CA-7.NC301 or CA-7.NC502)
describing the reason why the session could not be established. It is for information only, but may
indicate an error condition.
Operator Response: Correct the cause of the failure, if possible. Otherwise notify your installa-
tion's CA-7 specialist.
Programmer Response: Correct the cause of the failure, if possible. Otherwise get SYSLOG and
TRACE output before contacting Computer Associates Technical Support.
Note: The cause of error may have been detected at the remote node. Be sure to review the
console output at that site before assuming that the problem is with CA-7 NCF.

CA-7.NC501 –CA-7.NC502

Explanation: This message will occur when a VTAM error is encountered for a SEND or a
RECEIVE macro. For further explanation of the error refer to the "Return Code and Sense Fields"
section in the IBM ACF/VTAM Programming Manual.

SEND X'10' X'07' Terminate the session
RECEIVE X'10' X'07' Terminate the session

nical Support.
CA-7.NC502 ICR FROM NODE (nnnnnnnn) REJECTED, ENTRY FOR NODE (nnnnnnnn) INDICATES
ID X'nn'
Explanation: During establishment of a session between your installation's NCF node and the node
indicated, a serious mismatch between the two nodes' network definitions has been detected (that is,
one or the other node table was coded incorrectly).
User Response: The node cannot be logged on because the integrity of the NCF network would be
compromised.

CA-7.NC503 –CA-7.NC602

Programmer Response: First ensure that the network is correctly defined to all nodes. If the
problem cannot be corrected, save all listings and dumps and notify the Computer Associates Tech-
nical Support.
CA-7.NC503 WARNING: ICR FROM NODE (nnnnnnnn) INDICATES NCF NODE (nnnnnnnn) IS
MISSING FROM THE LOCAL NCT
Explanation: (See next message.)
User Response: (See next message.)
CA-7.NC503 WARNING: ICR FROM NODE (nnnnnnnn) INDICATES NCF NODE (nnnnnnnn) IS RELO-
CATED TO JES NODE (nnnnnnnn)
Note: One or the other of the above messages will appear. The write-up below applies equally to
either message.
Explanation: During establishment of a session between your installation's NCF node and the node
indicated, a discrepancy has been detected between the two nodes' network definitions.
User Response: Session establishment continues.
Programmer Response: Missing entries may or may not indicate that one or the other node table is
in error, depending on the intended configuration of the network. JES nodes in error should be
corrected as soon as possible but are not critical to the performance of NCF.
CA-7.NC602 VTAM ERROR (LOSTERM) NODE=nnnnnnnn CODE=cc

Explanation: The LOSTERM exit has been entered for the node specified in the message. The
level of this error is serious.
nnnnnnnn is the node which initiated the LOSTERM condition.
cc is the LOSTERM reason code. Refer to the IBM ACF/VTAM Programming Manual in the "Using
Exit Routines" section under the LOSTERM exit.
User Response: The action depends on the value of the reason code.
Reason code Meaning

X'00' - X'0B' Ignore the condition and continue.
X'0C' - X'1C' Terminate the session.
X'1D' - X'FF' Print message and continue.

Programmer Response: Correct the problem and resubmit.

CA-7.NC701 –CA-7.NC703
CA-7.NC701 VTAM NSEXIT (CLEANUP) NODE=nnnnnnnn mmm...

Explanation: This is a warning message. A cleanup session request has been received from VTAM
because communication with the node specified has been terminated abnormally.
nnnnnnnn is the node of the session which VTAM wants cleaned up.
mmm... is an optional text message to indicate that the node specified in the message could not be
found in the node control table.
User Response: The node specified in the message is marked as "not in session."
Operator Response: Verify that the node should no longer be operational. If it should be in opera-
tion, contact your installation's CA-7 specialist.
Programmer Response: Correct the error and resubmit.
CA-7.NC702 VTAM NSEXIT (NSPE) NODE=nnnnnnnn

Explanation: This is a warning message. VTAM has detected a Network Services Procedure Error
(NSPE) on a session initiation request that was responded to positively. However, something hap-
pened that made it impossible to ensure that the session will be set up successfully. nnnnnnnn is the
node name whose session is in question.
CA-7.NC703 VTAM NSEXIT (NOTIFY) NODE=nnnnnnnn

Explanation: This is a warning message. A session initiation request was responded to positively
but something happened that made it impossible to ensure that the session is set up correctly.
nnnnnnnn is the node whose session is in question.

CA-7.NC801 –CA-7.NC803

Explanation: A VTAM error has occurred as a result of an OPNSEC or SESSIONC macro. Refer
to the "Return Code and Sense Fields" section of the IBM ACF/VTAM Programming Manual for a
more detailed explanation.

OPNSEC X'14' User abend CF6
SESSIONC X'10' X'07' Terminate the session
X'14' Terminate the session

nical Support.
CA-7.NC803 LOGOFF COMPLETE FROM NODE=nnnnnnnn

Explanation: The node specified in the message initiated and completed a termination of communi-
cations. nnnnnnnn is the node which initiated the cessation of communications.

CA-7.NC901 –CA-7.NTM0
CA-7.NC901 VTAM TPEND (HALT)

Explanation: This is a warning message. A VTAM command was issued to do a controlled shut-
down of the application.
User Response: All nodes are marked to log off. Processing continues.
Operator Response: When communication can be established again, a LOGON command will have
to be issued for each node.
CA-7.NC902 VTAM TPEND (HALT,CANCEL)

Explanation: This is a warning message. A VTAM command was issued to cancel the application
immediately.
User Response: The VTAM application is terminated with a zero return code.
Operator Response: The VTAM application will have to be started when the VTAM problem is
resolved. Notify your installation's CA-7 specialist.
CA-7.NSXT CLEANUP REQUESTED FOR xxxxxxx

Explanation: An error was detected by CA-7 on the terminal shown. This message may be accom-
panied by other terminal error messages. Issued by SASSNSXT.
User Response: None. This message indicates that CA-7 is attempting to clean up its own error on
the terminal shown. If another CA-7 message appears, refer to the action to correct it.
CA-7.NSXT UNKNOWN VTAM CODE.

Explanation: The VTAM Network Services Exit routine in CA-7 received control from VTAM
with an unknown code. Issued by SASSNSXT.
User Response: The exit will ignore the request and pass a code of 0 to VTAM.
CA-7.NTMV Unable to evaluate variable in L2NTR at xxxxxxxx, first 16 bytes are: yyyyyyyyyyyyyyyy
Explanation: An error occurred attempting to evaluate the variable data at the address xxxxxxxx,
the first 16 bytes at that location are yyyyyyyyyyyyyyyy.
User Response: Ensure that the intended variable was properly named in the model NETMAN
transaction file and retry.
CA-7.NTM0 No plist address supplied for SASSNTM0.

Explanation: Insufficient storage was available for ENF event workareas.
User Response: Increase the region size for CA-7 by 1mB and retry.

CA-7.NTM0 –CA-7.NUC
CA-7.NTM0 Address of problem data not supplied for SASSNTM0.

Explanation: This is an internal error. No problem data was supplied on a call to SASSNTM0.
CA-7.NTM0 CA-NETMAN database name not supplied for MGPTUPD transaction

Explanation: This is an internal error. No NETMAN database name was supplied on a call to
SASSNTM0.
CA-7.NTM0 Address of NTMAPI not supplied for SASSNTM0.

Explanation: This is an internal error. No NTMAPI address was supplied on a call to
SASSNTM0.
CA-7.NTM0 NTMAPI called, RC=xxxxxxxx

Explanation: The NETMAN API was called and a nonzero return code was received.
CA-7.NUC ARF INITIALIZATION FAILED

Explanation: Initialization of the CA-7 ARF facility encountered an error. A U1004 abend will
occur.
User Response: Refer to any preceding messages relating to ARF. Correct any errors and restart
CA-7.
CA-7.NUC CA-7 JSCB AUTHORIZED

MVS PROGRAM MANAGEMENT USED
Explanation: This message is displayed when PGM=UCC7 is APF authorized as required.
User Response: No action required.
CA-7.NUC CA-7 JSCB NOT AUTHORIZED

Explanation: This message is displayed when PGM=UCC7 is NOT APF authorized (a U0988
abend will also occur).
User Response: Link program UCC7 with AC=1 and be sure that all STEPLIBs are APF author-
ized.
CA-7.NUC DORMANT START UP IN PROCESS

Explanation: This CA-7 was started with TYPE=DORM specified. Issued by SASSNUC.

CA-7.NUC –CA-7.PM10
CA-7.NUC UNABLE TO SUPPORT SGETM31/SPUTM31

Explanation: SGETM/SPUTM services unavailable for storage above the 16 Mb line.
User Response: Ensure that the SASSI31S module resides in a load library accessible to CA-7.
CA-7.PM00 Problem Management subtask termination requested.

Explanation: Termination was requested for the problem management interface.
CA-7.PM00 Unable to acquire FREE chain. FREEMAIN required.

Explanation: The problem management subtask was unable to reuse problem data because of con-
tention with the CA-7 main task. An OS FREEMAIN will be requested.
User Response: Occasional occurrences of this message present no cause for concern. However,
should this message be issued frequently consider increasing the region for CA-7. If the message
CA-7.PM00 FREEMAIN failed.

Explanation: A nonzero return code was received on an OS FREEMAIN issued by the problem
management subtask.
CA-7.PM10 Problem Management subtask ended.

Explanation: The end of task exit for the problem management subtask was entered. This message
should only be produced at CA-7 termination.
CA-7.PM10 End-of-Task Exit TCB address did not match L2PMA_PM00TCB

Explanation: The end of task exit for the problem management subtask was entered. The TCB
address at entry did not match the TCB address in the L2PMA.
CA-7.PM10 End-of-Task Exit could not locate L2PMA.

Explanation: The end of task exit for the problem management subtask was entered. The L2PMA
could not be located.
CA-7.PM10 End-of-Task Exit could not locate UCC7SVT.

Explanation: The end of task exit for the problem management subtask was entered. The
UCC7SVT could not be located.

CA-7.PPJC –CA-7.RSC5-01
CA-7.PPJC Storage request exceeds maximum allowable. Data lost.

Explanation: A limit on the amount of storage to be used by the problem management interface has
been reached. Problem data for job completions will be lost.
CA-7.PPJC GETMAIN failed. Unable to chain job completion data.

Explanation: The problem management subtask was unable to process job completion data because
of a GETMAIN failure.
CA-7.PPJC Chaining error. Data lost.

Explanation: The problem management subtask was unable to process job completion data because
of an internal error in chaining. This is probably due to a storage overlay.
CA-7.QMGO DQTQ WRAP AROUND

Explanation: Too many messages are queued to a terminal. Message is followed by an SOC3
abend of CA-7. Issued by SASSQMGO.
User Response: Restart CA-7 with TYPE=ERST which will clear out the messages in the DQTQ
and Scratch queue.
CA-7.RLOG UNABLE TO ADD ENTRY TO RUNLOG. NAME=xxxxxxxx

Explanation: The daily run log has filled up. The xxxxxxxx indicates the job name or network
name trying to be added.
User Response: No action required. The message is informational.
CA-7.RLOG ERROR TRYING TO ADD RLOG FOR TODAY'S DATE

Explanation: An attempt to add a new RLOG header entry failed. The PRNQ may be full.
User Response: Use the /DISPLAY,Q=ALL command to see if the PRNQ is full. Also, a trigger
loop (JOBA triggers JOBB, and JOBB triggers JOBA) can cause the problem.
CA-7.RLOG ERROR TRYING TO UPDATE CURR RLOG HEADER

Explanation: An attempt to update the current RLOG header failed. A possible I/O error has
occurred.
User Response: If the problem persists, contact your installation's CA-7 specialist for assistance.
CA-7.RSC5-01 JOB NOT FOUND IN READY QUEUE

Explanation: An entry was not found in a VRM table.
User Response: This message is informational only.

CA-7.RSC5-02 –CA-7.R155
CA-7.RSC5-02 I/O ERROR ON READ OF READY QUEUE

Explanation: An error occurred trying to read a CA-7 queue.
User Response: If the problem persists, notify your installation's CA-7 specialist.
CA-7.RW005 RESOURCE FILE SUCCESSFULLY CLOSED

Explanation: This message is issued at the end of the WLP processing of the VRM database.
CA-7.RW904 RSRC FILE SUCCESSFULLY OPEN R15=xx ER=yy

Explanation: This message is issued at the start of the WLP processing of the VRM database.
CA-7.RW905 DDNAME CA7RSRC NOT FOUND

Explanation: The ddcard for CA7RSRC is missing.
User Response: The WLP job abends with a U0105. Check the JCL used by the WLP job.
CA-7.R137 VRM FULL SUPPORT ACTIVE

Explanation: The Virtual Resource Management facility (VRM) has been made fully active based
upon the RSRC=YES keyword (or default) on the DBASE initialization statement.
CA-7.R138 VRM MAINT SUPPORT ACTIVE

Explanation: The database services for the Virtual Resource Management facility (VRM) has been
made active based upon RSRC=MAINT keyword on the DBASE initialization statement. However,
CA-7 will not honor virtual resource requirements while in maintenance mode.
CA-7.R152 CPM FLOW CHAIN CREATED

Explanation: During CA-7 startup, the chain of FLOW records was rebuilt.
CA-7.R154 ERROR ON DELETE CPM FLOW RECORD

Explanation: CA-7 was unable to delete a CPM FLOW record during initialization.
CA-7.R155 ERROR ON GETUPD CPM FLOW RECORD

Explanation: CA-7 was unable to get a CPM FLOW record for update during initialization.

CA-7.R156 –CA-7.R602
CA-7.R156 CPM FLOW RECORDS DELETED

Explanation: CA-7 deleted CPM FLOW records during a COLD or FORM start.
CA-7.R32V RPL RESET

Explanation: A CA-7 VTAM RPL was left in an unusable state. CA-7 has restored the RPL to a
usable state. Informational message issued by SASSR32V.
CA-7.R500 RESOURCE DEQ ERROR DURING JOB COMPLETION.

Explanation: During job completion, an error occurred during a DEQ macro instruction to dequeue
a resource.
nical Support.
CA-7.R501 GET ERROR ON ACTIVE RESOURCE RECORD CHAIN.

Explanation: During job completion, an error occurred on a GET of an active job resource record.
nical Support.
CA-7.R502 DELETE ERROR ON ACTIVE RESOURCE RECORD CHAIN.

Explanation: During job completion, an error occurred on a delete of an active job resource record.
nical Support.
CA-7.R503 ERROR ON ADD OF A MANUAL RESOURCE RECORD.

Explanation: During job completion, an error occurred on an add of a manual job resource record.
User Response: CA-7 continues processing. Check for messages CA-7.XRAC-03 and
CA-7.XRAC-06 for a description of the error.
CA-7.R600 ERROR ON DEQ OF RESOURCES.

Explanation: During processing of a PRSCF transaction, VRM detected an error when issuing a
DEQ instruction. This message is issued by SASSSPOR.
User Response: CA-7 continues processing. Contact Computer Associates Technical Support.
CA-7.R602 ERROR ON DELETE OF A RESOURCE RECORD.

Explanation: During processing of a PRSCF transaction, VRM was unable to delete a record
related to the resource being freed. This message is issued by module SASSSPOR.
User Response: CA-7 continues processing. See messages CA-7.IVRM-02 and CA-7.IVRM-03 for
specific details on the error.

CA-7.R603 –CA-7.R620
CA-7.R603 ERROR ON DELETE OF A COREQUISITE RESOURCE RECORD.

Explanation: An error occurred when deleting a corequisite resource record. This message is
issued by module SASSSPOR.
CA-7.R604 ERROR ON GET OF A COREQUISITE RESOURCE RECORD.

Explanation: An error occurred on a GET to a corequisite resource record. This message is issued
by module SASSSPOR.
CA-7.R610 ERROR ON ADD OF A COREQUISITE RESOURCE RECORD.

Explanation: An error occurred on add of a corequisite resource record. This message is issued by
module SASSSPOR.
User Response: CA-7 continues processing. See messages CA-7.XRAC-02 and CA-7.XRAC-03
for specific details on the error.
CA-7.R611 ERROR ON DEQ OF A COREQUISITE RESOURCE RECORD.

Explanation: An error occurred on a DEQ of resource record. This message is issued by module
SASSSPOR.
CA-7.R612 RECORD NOT FOUND ON GET FOR UPDATE.

Explanation: An invalid return code was received during VSAM I/O processing. This message is
CA-7.R613 UPDATE ERROR ON ACTIVE RESOURCE CHAIN.

Explanation: An invalid return code was received during VSAM I/O processing. This message is
CA-7.R620 ERROR ON LOOP ENQ

Explanation: During submission, an error occurred during VRM ENQ processing. This message is
issued by module SASSXRSU.
nical Support.

CA-7.R621 –CA-7.R901
CA-7.R621 GET ERROR ON ACTIVE JOB RESOURCE CHAIN.

Explanation: During submission, an error occurred during a GET for an active job resource record.
nical Support.
CA-7.R622 UPDATE ERROR ON ACTIVE JOB RESOURCE CHAIN.

Explanation: During submission, an error occurred during an update of an active job resource
record.
nical Support.
CA-7.R700 ERROR ON DEQ FOR RESOURCES.

Explanation: Invalid return code received from a DEQ for a resource after a cancel command was
issued.

Explanation: An error occurred during a GET of an active resource record when a cancel command
was issued.
CA-7.R730 ERROR ON DEQ AT JOB STEP COMPLETION.

Explanation: At job step end, an error occurred during a DEQ to free a resource.

Explanation: At job step end, an error occurred during a GET of an active resource record.
User Response: See messages CA-7.XRAC-02 and CA-7.XRAC-03 for specific details on the error.
CA-7.R732 UPDATE ERROR ON ACTIVE RESOURCE RECORD CHAIN.

Explanation: At job step end, an error occurred during an update of an active resource record.
User Response: See messages CA-7.XRAC-02 and CA-7.XRAC-03 for specific details on the error.
CA-7.R901 ERROR DURING GENCB (EXLST) R15=xx

Explanation: During CA-7 startup, an error xx (R15) occurred on VSAM control block generation
(exlst).
nical Support.

CA-7.R902 –CA-7.S3
CA-7.R902 ERROR DURING GENCB (ACB) R15=xx

(ACB).
nical Support.
CA-7.R903 ERROR DURING OPEN OF RESOURCE FILE R15=xx ER=aaa

Explanation: During CA-7 startup, an error occurred on the resource file open.
nical Support. Check the value in R15 and ACBERFLG (aaa) and correct the error.
CA-7.R904 RESOURCE FILE OPENED. R15=xx ER=xxx

Explanation: During CA-7 startup, the resource file was successfully opened.
CA-7.R905 DDNAME CA7RSRC NOT FOUND

Explanation: During CA-7 startup, the ddname corresponding to the VRM resource file was not
found.
User Response: CA-7 abnormally terminates with a U0905. Ensure that the CA-7 startup JCL
procedure contains the CA7RSRC DD and filename.
CA-7.R906 ERROR DURING GENCB (RPL) R15=xx

(RPL).
nical Support.
CA-7.R907 DDNAME CA7RSRC POINTS TO DUMMY FILE - U0907

Explanation: The DD statement for the CA-7 VRM VSAM file (CA7RSRC) does not point to an
actual data set. This data set is required for CA-7 operations. CA-7 abends with a User 907 code.
User Response: Provide a CA7RSRC DD statement that points to a valid CA-7 VRM data set and
restart CA-7.
CA-7.S3 NCF INTERFACE IS INACTIVE

Explanation: NCF is not active and the NCF data is discarded.
Operator Response: A job belonging to CA-7 at a remote node is executing without the support of
NCF and its SMF/Trailer data has been lost. If possible, activate the CA-7 NCF interface and
promptly inform the Production Control Supervisor.
Note: This message may be associated with NCF incoming data. For appropriate action, see the
documentation for the INCOMING DATA REJECTED message.

CA-7.S3 –CA-7.SCNJ
Programmer Response: Ensure that NCF has been properly installed.
CA-7.S3 INVALID NCF NODE ID xx (HEX)

Explanation: The NCF node identifier shown is invalid.
User Response: The data is discarded and processing continues.
Operator Response: Promptly inform the Production Control Supervisor.
Programmer Response: Each defined CA-7 identifier in the NCF node control table must represent
one and only one NCF node and may have any value except X'00', X'40', or X'E0' through X'FF'.
CA-7.S3 DATA FOR JOB xxxxxxxx DISCARDED

Explanation: SMF or Trailer data for the job shown has been discarded.
User Response: See the two preceding messages.
Operator Response: See the two preceding messages.
Programmer Response: See the two preceding messages.
CA-7.S3 INCOMING DATA REJECTED

Explanation: NCF is receiving data but the CA-7 NCF interface is not active or the incoming data
does not belong to the local CA-7 node.
User Response: The NCF node from which the data was received will be logged off. No data will
be lost.
Operator Response: If possible, activate the CA-7 NCF interface. If the problem persists, notify
the local CA-7 NCF specialist.
Programmer Response: Verify proper installation of NCF. This requires coordination with remote
nodes.
CA-7.S9 NO BUFFER FOR OUTBOUND DATA

Explanation: The NCF buffer pointer is zero.
User Response: SMF or Trailer data has been discarded. Processing continues.
Programmer Response: Verify proper installation of NCF.
CA-7.SCNJ SKIPPED DUPLICATE SCHEDULE MEMBER

Explanation: During a Schedule Scan, a schedule member was read that had already been proc-
essed by this same run of Schedule Scan. Issued by SASSSCNJ.
User Response: None. This message is for information only. The duplicate member is bypassed.
This can possibly occur when the Dataset data set is being updated during the time that Schedule
Scan runs.

CA-7.SCRJ –CA-7.SJLV
CA-7.SCRJ xxxxxxxx(nnnn), ARJP R15=yyyyyyyy, R0=zzzzzzzz

Explanation: An error occurred while attempting to delete ARF control blocks that are no longer
needed for a job.
User Response: This is an ARF internal error. The message is issued for debugging purposes and
does not necessarily indicate a problem with ARF functionality. However, if the message is issued
repeatedly or if it accompanies other error messages, contact Computer Associates Technical Support
for assistance.
CA-7.SJ NETWORK COMMUNICATION FACILITY NOT ACTIVE

Explanation: The CA-7 NCF interface has not been activated because the Operating System type
code in ICMDSECT is incorrect.
User Response: Processing proceeds without NCF support.
Programmer Response: NCF support is only provided in an MVS environment. If ICMDSECT is
in error, correct the error and restart.
CA-7.SJ NCF IS PRESENT - LOCAL NODE = xxxxxxxx

Explanation: The CA-7 NCF interface is active.
User Response: Processing proceeds.
Programmer Response: This is an informative message. Verify that the local node is as
expected/defined.
CA-7.SJLV One or more VRM Device Definitions dropped for xxxxxxxx

Explanation: An error occurred while trying to dynamically update the record of VRM devices.
One or more VRM device definitions were not updated. This could occur if the number of VRM
resources exceeds the database record capacity.
User Response: Contact your installation's CA7 technical specialist. The following items may be
required to diagnose the error:
1. RM.1 output for the job in error.
2. Listing of the current SASSDTAB module.
CA-7.SJLV VRM IO err X FUNC=GETUPD RC=xxxxxxxx REASON=yyyyyyyy JOB=nnnnnnnn

Explanation: An error occurred while trying to dynamically update VRM resource definitions. X is
a code indicating the type of record on the VRM database. FUNC is the function attempted. The
program return code is reported at RC and REASON is the VSAM feedback.
User Response: Contact your installation's CA7 technical specialist. The following items may be
required to diagnose the error:
1. RM.1 output for the job in error.
2. Listing of the current SASSDTAB module.

CA-7.SJLV –CA-7.SMF0
CA-7.SJLV Unable to update VRM Device Definitions. Length=nnnnnnnn Maxlen=xxxxxxxx Job=yyyyyyyy

Explanation: The record of VRM resources will not fit in the buffer allocated. The Length value is
the size of the VRM record retrieved, and Maxlen is the size of the working buffer.
User Response: Contact your installation's CA7 technical specialist. RM.1 output for the job in
error may be required.
CA-7.SJL0 VRM DEVICE TABLE SPACE EXCEEDED

Explanation: The size of the table of VRM Devices that is built during LOAD completion had to
be increased.
User Response: This is an informational message. No action is required.
CA-7.SJL0 RQMT LOAD TABLE OVERFLOW

Explanation: An attempt was made to LOAD a job into CA-7. The table that is set up to contain
requirements for the job cannot handle all of this job's requirements. Issued by SASSSJL0.
User Response: The load on the job will be successful despite this message. Use
LJOB,JOB=jobname,LIST=RQMT to see if the necessary requirements have been built for the job.
If all of these requirements are not included, contact your installation's CA-7 specialist for assistance.
CA-7.SMFI-33 CPU xxxx IPL - REQUEUING ACTIVE JOBS.

Explanation: This message is a WTO. An IPL of a system within the CA-7 complex was detected,
and the AUTOREQ option is in effect. All jobs in the Active queue for the affected CPU (xxxx)
will be automatically requeued to the Request queue with a status of R-REQUE.
User Response: Analyze each job moved into the Request queue to determine any corrective
actions. Once the appropriate steps have been taken, Job Restart must be used to resubmit these
jobs.
CA-7.SMFI-34 AUTO-REQUEUE FEATURE INACTIVE - IPL RECORDS IGNORED.

Explanation: An IPL of a system within the CA-7 complex was detected, and the AUTOREQ
option is not in effect. Any jobs active on systems at the point of an IPL will be left in the Active
queue. Jobs left in the Active queue following a system failure such as this must be manually
requeued to the Request queue (see the REQUEUE command). This message is displayed only once.
User Response: All jobs left stranded in the Active queue following the system failure must be
manually requeued to the Request queue (see the REQUEUE command).
To activate the Auto-Requeue feature, refer to the AUTOREQ keyword on the OPTIONS initializa-
tion statement in the CA-7 Systems Programmer Guide.
CA-7.SMF0 BAD SMF REC - BLOCK BYPASSED

Explanation: This message is a WTO. An SMF block in the Communications data set has a value
of zero in the first two bytes. This is a zero length field and zero is not valid. Issued by
SASSSMF0.
User Response: The bad block is skipped. Data in this block is not processed. This could result
in:

CA-7.SMF2 –CA-7.SMF4
1. Outstanding data set requirements.

2. Jobs staying in the Ready queue.
3. Jobs staying in the Active queue.
CA-7.SMF2 JOB jjjjjjjj NOT ADDED TO THE ACTIVE QUEUE.

Explanation: This WTO is issued when an external job initiation occurs but CA-7 is unable to add
it to the Active queue. This could occur if the Active queue was full or if there was already a job in
the Ready or Active queue by the same name.
User Response: None. This job will not be represented in CA-7's queues.
CA-7.SMF3 JOB xxxxxxxx (nnnn;jjjjj) FAILED: rrrrrrrrrrrrrrrrrrrr

Explanation: The job indicated by xxxxxxxx failed for the reason indicated by rrrrrrrrrrrrrrrr. The
jjjjj is the JES job number, if available. The nnnn is the CA-7 job number. This WTO is only
produced if the WTO= keyword is specified on the RESTART statement in the initialization file.
The possible reason values are:
JCL ERROR
ABEND Unnnn
ABEND Snnn
JOB CC nnnn
STEP ssssssss FLUSHED
STEP ssssssss CC nnnn
User Response: Refer to SMF0-33 messages in the CA-7 Browse data set for jobs that are automat-
ically requeued. Appropriate action should be taken to resolve the restart situation for the job. This
may involve canceling or restarting the job on CA-7.
CA-7.SMF3 UNABLE TO UPDATE ARF TRAILER FOR jjjjjjjj(nnnn)

Explanation: An error occurred while trying to evaluate an ARF 'late at job end' exception (LE).
However, ARF could not report the error because of an error encountered while trying to update the
trailer queue.
User Response: ARF cannot properly proceed with recovery from the late condition. Manual
recovery procedures should be employed to address the problem. If necessary, cancel the job and
retry. If the problem persists, contact Computer Associates Technical Support.
CA-7.SMF4 JOB xxxxxxxx (nnnn/jjjjj/systemnm) ON cccc STEP pppppppp.ssssssss yyyy

Explanation: The procstep/step indicated by pppppppp.ssssssss for job xxxxxxxx completed with
the indicated code. This WTO is produced when the WTOSTEP keyword is used on the CA-7
RESTART initialization statement. The default ROUTCDE is 2 (Master Console), this can be over-
ridden by the ROUTCDE= keyword on the RESTART statement.
The CA-7 job number (nnnn), JES job number (jjjjj) and CA-7 system name (systemnm) are also
provided.
Possible values for the termination code (yyyy) are:

CA-7.SMF5 –CA-7.SSM1
Uyyyy Indicates a User Abend code

Syyy Indicates a System Abend code
JCLER Indicates a JCL Error
Cyyyy indicates a condition code failure
yyyy Indicates a step condition code (not a failure)
User Response: No action is required.
CA-7.SMF5 OUTPUT DSN NOT POSED TO CA-7

Explanation: The Trailer queue was full at the time that CA-7 received a data set update SMF
record. When CA-7 attempted to update the job's record in the Active queue, an error occurred.
User Response: Verify the space allocation of the Trailer queue (it may need to be increased). If
this data set was supposed to trigger jobs or post requirements, manual intervention is required to
cause those events to occur.
CA-7.SMF5B SUBTASK FAILURE LIMIT EXCEEDED FOR xxx...x

Explanation: While processing the JCL data set xxx...x, a failure (abend) occurred, and the data set
has been disabled. All jobs using this file are left in SKELETON status.
User Response: Correct the error and then recycle CA-7 to regain use of the JCL data set.
CA-7.SORRY TERMINAL NOT DEFINED TO CA-7

Explanation: A remote 3270 terminal (BTAM) has been used to input a command and the terminal
is not defined to CA-7. Issued by SASSI32R.
User Response: If the terminal is to be used, it must be defined with a TERM statement in the
initialization file.
CA-7.SSM0 UNABLE TO PROCESS ARF EXCEPTION - IS.

Explanation: An IS condition for the job was detected by ARF, but the job could not be requeued
because of an internal error.
CA-7.SSM1 TABLE FULL

Explanation: More than 300 jobs have been submitted by CA-7 causing an internal table to become
full. Possibly some mutually exclusive requirements will not be honored. Issued by SASSSSM1.
User Response: If more than 300 jobs are in the Ready or Active queues at any one time, contact

CA-7.SVCA-nn –CA-7.SVCT001E
CA-7.SVCA-nn Refer to SVCA-nn messages.

CA-7.SVCA-15 NCF NODE TABLE NOT DEFINED
CA-7.SVCA-16 UNDEFINED NCF NODE xxxxxxxx

CA-7.SVCT000E CA-7 INDICATOR BYTE NOT SET

Explanation: The code indicating that the job was submitted by CA-7 was not found at the location
in the SMF Common Parameter Area that was specified by ICMDSECT. This may indicate a
tracking error.
User Response: Make the appropriate corrections in case:
1. The U7TESTSV job was not DEMANDed by CA-7.
2. Column 71 of the first JOB statement has been modified or columns 70/71 are not blank.
3. There is a conflict over the use of either the USERID field or the RDRDATE field in the SMF
Common Parameter Area so that the CA-7 indicator byte has been overlaid (probably by another
UJV exit). Make sure all copies of ICMDSECT agree on placement of the indicator byte (that
is, USERID field or RDRDATE field). There may be multiple copies of ICMDSECT located on
the CA-7 load library, LPA or CAIRIM libraries as well as those link edited with UJV, U83 and
U84 exits.
4. The CA-7 UJV exit is not getting control. This may occur if the IEFUJV exit is not linked
properly.
CA-7.SVCT001E ICM4 BIT SETTING INVALID

Explanation: An unexpected bit setting was found in ICMDSECT.
User Response: This may indicate an incorrect zap to ICMDSECT. Check all zaps to ICMDSECT,
particularly those that relate to the use of the RDRDATE field. This may also indicate that CA-7's
type IV SVC has not yet been installed or that the SVC number in ICMDSECT does not match the
SVC reserved for CA-7's use.

CA-7.SVCT002E –CA-7.SVCT010I
CA-7.SVCT002E INVALID CA-7 SVC RET CODE

Explanation: An unexpected code was returned from the SVC that was designated as the CA-7
SVC.
User Response: This may indicate that CA-7's type IV SVC has not been installed properly or that
the SVC number in ICMDSECT does not match the SVC number reserved for CA-7's use.
CA-7.SVCT003E TCT FIELD IN TCB IS ZERO

Explanation: An attempt to locate the SMF Common Parameter Area failed.
User Response: This is a severe error. Be sure that SMF has been properly SYSGENed and is
active. If the error persists, contact Computer Associates Technical Support.
CA-7.SVCT005E BLDL FAILED

Explanation: An attempt to locate the UJV, U83 and/or U84 exits failed because of an I/O error.
User Response: This is a severe error. If there is no problem accessing modules on the library
where the UJV, U83 and U84 exits are located, contact Computer Associates Technical Support.
CA-7.SVCT006W xxxxxxxx FOUND IN STEPLIB

Explanation: The module named xxxxxxx was located in one of the libraries in the STEPLIB con-
catenation, probably the CA-7 load library.
User Response: The module named cannot be properly validated because only the copy accessed by
SMF (residing in LPA) will be used in job tracking. Any modules named IEFUJV, IEFU83,
IEFU84, CA7UJV, CA7U83, or CA7U84 on any library in the STEPLIB concatenation should be
renamed to allow the validation to proceed.
CA-7.SVCT008E xxxx NOT MATCHED IN ICMDSECT

Explanation: The name xxxx was not matched in the ICMDSECT control module. Since this name
is used for enqueuing certain items, such a mismatch could cause system and data integrity problems.
User Response: Be sure the system was initialized using CAIRIM. If the xxxx value is ICOM, the
ICMDSECT is the wrong format (probably a wrong module) and should be reinstalled. If the xxxx
value is UC07 or UCT7, the system was not initialized using CAIRIM, in which case, running
CAIRIM to INIT or REINIT should correct the problem.
CA-7.SVCT009E FIRST LOAD OF CA-7 SVC NOT FIXED

Explanation: This message indicates an error unless the SVC module is in MLPA.
User Response: If there is not an entry for UC07 in an IEFSSNxx member of PARMLIB, the first
load of the CA-7 SVC must reside in FLPA. To avoid the FLPA requirement, put an entry for UC07
in IEFSSNxx or use CAIRIM to initialize.
CA-7.SVCT010I xxxx FOUND IN SSCVT

Explanation: This message indicates that an entry was found for UC07 in an SSCVT.
User Response: None. This message is strictly informational.

CA-7.SVCT011W –CA-7.SVCT017W
CA-7.SVCT011W ICOM NOT ACTIVE ON THIS CPU

Explanation: U7TESTSV determined that ICOM is not active, indicating that jobs will not be
tracked.
User Response: Start ICOM if job tracking is desired.
CA-7.SVCT012I IGCS3XXX SIZE IN BYTES IS xxxxxxxx (HEX)

Explanation: IGCS3XXX on LPA has the size indicated.
CA-7.SVCT013E UNABLE TO LOAD xxxxxxxx

Explanation: An attempt to LOAD the module named at xxxxxxxx failed.
User Response: Review any IBM messages associated with the LOAD failure and make appropriate
corrections. Make sure that the module named is in LPA.
CA-7.SVCT014W CA-7 CODE STILL IN xxxxxxxx

Explanation: This is a warning message indicating that CA-7 code was detected in the module
named. This message should be produced only if CAIRIM is being used.
User Response: If CAIRIM is being used, then be sure that all CA-7 code is removed from the
module named at xxxxxxxx.
CA-7.SVCT015I RIMINIT BIT IS ON AT ICM2

Explanation: The CAIRIM initialization routine for CA-7 has modified ICMDSECT with a code
indicating that CAIRIM is active.
CA-7.SVCT016I SASSxxx IS USERxxxn IN xxxxxxx

Explanation: This message indicates that the CA-7 driver is the entry point for the module named
at xxxxxxxx and that the SASSxxx module is the nth exit to receive control.
CA-7.SVCT017W CA-7 CODE NOT FOUND IN xxxxxxxx

Explanation: This message is issued when U7TESTSV is unable to locate CA-7 SMF processing
code in the module named at xxxxxxxx.
User Response: This is a warning message. Review the module named at xxxxxxxx to make sure
that the CA-7 code is in the module and will be executed.

CA-7.SVCT018W –CA-7.SVC4
CA-7.SVCT018W LMP VIOLATION HAS OCCURRED FOR CA-7

Explanation: This message indicates that an LMP (Licensed Management Program) violation has
occurred since the last COLD initialization by CAIRIM for CA-7. When this occurs, some SMF
and/or TRLR data may be lost.
User Response: Ensure that a proper LMP key is in the CAIRIM KEYS file for the CPU which
received the violation. It may be necessary to reinitialize CAIRIM for CA-7 using the
REINIT(COLD) parameter.
CA-7.SVCT098I BAD TERMINATION. ERR CODE = xxxxxx

Explanation: This signifies abnormal termination. The errors that caused the abnormal termination
should be indicated in previous messages whose prefix ends with E or W. The ERR CODE value is
an internal code used by Computer Associates Technical Support for debugging purposes.
User Response: None. Refer to previous messages.
CA-7.SVCT099I NORMAL TERMINATION FOR THIS JOB IS A U0099 ABEND.

Explanation: This signifies normal termination. No problems were found with the CA-7 SVC or
CA-7 SMF exits.
CA-7.SVC3 POSSIBLE TRACKING DATA LOST IN CSA

Explanation: A CSA storage overlay has been detected by CA-7. An external source has overlaid
a chain used by CA-7.
The loss of tracking data can result in various CA-7 problems. For example:
1. A job may stay in the ACTQ and never go back to the REQQ for completion processing.
2. A job may stay in the RDYQ and never go to the ACTQ.
3. A data set posting may never automatically occur.
User Response: Many CSA overlays cause the entire system to fail; hence, an IPL should be done
as soon as possible. CA-7 can sometimes recognize if its data has been overlaid and attempts a
partial recovery; however, since CSA has been overlaid, an IPL should be scheduled as soon as
possible.
CA-7.SVC4 POSSIBLE TRAILER DATA LOST IN CSA

Explanation: See CA-7.SVC3.
User Response: See CA-7.SVC3.
Also, the loss of Trailer data can result in commands not being given to CA-7. For example a
SASSTRLR or U7SVC DEMAND command may be lost.

CA-7.SVC9 –CA-7.S3
CA-7.SVC9 POSSIBLE TRACKING DATA LOST IN CSA

Explanation: See CA-7.SVC3.
User Response: See CA-7.SVC3.
CA-7.S3 NCF INTERFACE IS INACTIVE

Explanation: CA-7 NCF is not active and the NCF data is discarded.
Operator Response: A job belonging to CA-7 at a remote node is executing without the support of
CA-7 NCF and its SMF/Trailer data has been lost. If possible, activate the CA-7 NCF interface and
promptly inform the Production Control Supervisor.
Note: This message may be associated with CA-7 NCF incoming data. For appropriate action, see
the documentation for the INCOMING DATA REJECTED message.
Programmer Response: Ensure that CA-7 NCF has been properly installed.
CA-7.S3 INVALID NCF NODE ID xx (HEX)

User Response: The data is discarded and processing continues.
Programmer Response: Each defined CA-7 identifier in the NCF node control table must represent
one and only one NCF node and may have any value except X'00', X'40', or X'E0' through X'FF'.
CA-7.S3 DATA FOR JOB xxxxxxxx DISCARDED

Explanation: SMF or Trailer data for the job shown has been discarded.
User Response: See the two preceding messages.
Operator Response: See the two preceding messages.
Programmer Response: See the two preceding messages.
CA-7.S3 INCOMING DATA REJECTED

Explanation: NCF is receiving data but the CA-7 NCF interface is not active or the incoming data
does not belong to your installation's CA-7 node.
User Response: The NCF node from which the data was received will be logged off. No data will
be lost.
Operator Response: If possible, activate the CA-7 NCF interface. If the problem persists, notify
your installation's CA-7 specialist.
Programmer Response: Verify proper installation of CA-7 NCF. This requires coordination with
remote nodes.

CA-7.S9 –CA-7.TARI
CA-7.S9 BLOCKED RECORD EXCEEDS BUFFER

Explanation: A set of blocked Trailer records exceeds the buffer size for trailers. The blocked set
of records will be skipped and ICOM will continue to process other records.
User Response: Trailer data has been discarded, but the processing continues. This could indicate
an erroneous or incomplete installation or upgrade. Notify your installation's CA-7 specialist to
verify the installation of CA-7. Some data has been lost from Trailer Step or U7SVC input which
could affect production work.
CA-7.S9 NO BUFFER FOR OUTBOUND DATA

Explanation: The NCF buffer pointer is zero.
User Response: SMF or Trailer data has been discarded, but the processing continues.
Programmer Response: Verify proper installation of CA-7 NCF.
CA-7.TARI ARF DATA BASE IS NOW OFFLINE

Explanation: The 'ARFIO SHUTDOWN' call to SASSTARI has completed successfully. The ARF
database is now CLOSEd, but the ACB and buffer pool has been retained.
CA-7.TARI ARF DATA BASE WAS NOT ONLINE

Explanation: An 'ARFIO SHUTDOWN' call to SASSTARI was performed to CLOSE the ARF
database, but the ARF database was not OPEN. This is accompanied with a return code of 4.
CA-7.TARI ARF DATA BASE SHUTDOWN COMPLETE

Explanation: The 'ARFIO SHUTDOWN' call to SASSTARI has been completed successfully.
CA-7.TARI ARF DB TERM ERROR: RC=xx RS=rrrr INF=iiii

Explanation: An error has occurred during ARF database shutdown. The return, reason and infor-
mation codes define the problem exactly. Refer to the list of return codes below.
User Response: The ARF database may still be OPEN. CA-7 shutdown continues.
RC=04 ARF database was not OPEN.
RC=08 ARF initialization did not complete, CLOSE not attempted.
RC=12 ARF database was never initialized.
RC=16 ARF database CLOSE failed. R0=CLOSE return code. R1=CLOSE reason code.
RS=4 The ARF database did not CLOSE properly. The information code explains why the
CLOSE failed.

CA-7.TRLR-00 –CA-7.UJV
INF=004 Data set is already CLOSEd.

INF=132 Uncorrectable I/O error occurred while reading the JFCB.
INF=136 Not enough virtual storage to complete the CLOSE request.
INF=144 Uncorrectable I/O error occurred while updating the ICF catalog records.
INF=148 Error occurred during catalog search.
INF=184 Uncorrectable error occurred while completing the outstanding requests.
CA-7.TRLR-00 (jobname) PROCESS xxxxxxxx JOBSTEP=stepname,

PROCSTEP=procstep, NODE=nodename, OPT=option
Explanation: This is an informational message indicating the start or completion of Trailer program
processing. The name of the job executing the program is indicated by taskname. The job step
name is indicated by ssssssss. The procedure step name is indicated by pppppppp. The NCF node
name, if present, is indicated by nnnnnnnn. Any PARM options are indicated by oooooooo.
CA-7.TRLR-30 NCF NODE TABLE NOT DEFINED

CA-7.TRLR-31 UNDEFINED NCF NODE xxxxxxxx

CA-7.TVRM-03 RESOURCE FILE SUCCESSFULLY CLOSED

Explanation: During CA-7 shutdown. VRM has closed the VRM database file.
CA-7.UJV NCF NODE TABLE NOT DEFINED

Explanation: The NCF node control table was not found.
User Response: See the message below.
Operator Response: See the message below.
Programmer Response: See the message below.

CA-7.UJV –CA-7.U83
CA-7.UJV INVALID NCF NODE ID xx (HEX)

User Response: See the message below.
Operator Response: See the message below.
Programmer Response: See the message below.
CA-7.UJV JOB xxxxxxxx NO LONGER UNDER CA-7 CONTROL

Explanation: The job shown is no longer under CA-7 control. Either the node control table was
not found or an unidentified NCF node identifier has been encountered.
User Response: Processing continues as though the job was submitted outside of CA-7 control.
Programmer Response: Verify and correct the CA-7 NCF installation steps. Each defined CA-7
identifier in the NCF node control table for job identification purposes must represent one and only
one CA-7 NCF node and may have any value except X'00', X'40' or X'E0' through X'FF'.
CA-7.UJV SASSUJV ENTERED

Explanation: This WTO is produced when a job is submitted to a CA-7 system that has a stepname
of CA7B$$4U in it. Computer Associates Technical Support will sometimes request that you run a
job with this stepname in it to be sure that SASSUJV is getting control.
CA-7.UNLK CHAIN SERIALIZATION ERROR. SCT=xxxxxxxx

Explanation: A CA-7 execution thread did not release all of its chain locks before releasing
control. The address of the SCT is listed in the message.
User Response: Any locks still held by the SCT are released by the process which produces this
message. If the message occurs more than once, contact Computer Associates Technical Support for
assistance in debugging the error.
CA-7.U7SVC-nn Refer to U7SVC-nn messages.

CA-7.U83 SASSU83 ENTERED
of CA7B$$4U in it and a data set open occurs. (To be sure that a data set open occurs, use a
STEPLIB DD in the JCL.) Computer Associates Technical Support will sometimes request that you
run a job with this stepname in it to be sure that SASSU83 is getting control.

CA-7.U84 –CA-7.VB04
CA-7.U84 LCT COULD NOT BE FOUND (SASSU84)

Explanation: The Linkage Control Table (LCT) could not be found in core for a job run under
CA-7. The LCT is searched for during step and job termination. Issued by SASSU84.
This message is produced when an initiator abends.
User Response: Determine the cause of the initiator abend. This message is a result of an initiator
abend and not the cause of the abend. This message is informational only.
CA-7.U84 SASSU84 ENTERED

of CA7B$$4U in it. Computer Associates Technical Support will sometimes request that you run a
job with this stepname in it to be sure that SASSU84 is getting control.
CA-7.VB00 message text

Explanation: This is the VRM backup report summary message which indicates the record types
found on the VRM data set during backup processing.
CA-7.VB01 INVALID RECORD TYPE RC=4 KEY= xxxxxxxxxxxxxxxxxxxx

Explanation: An invalid record type was found on the VRM data set. The xx value indicates the
key of the invalid record type.
CA-7.VB02 INVALID RECORD FOUND RC=8

Explanation: An invalid record was found on the VRM data set.
CA-7.VB03 VSAM ERROR (HEXA) RC=nn FDBK=nnnn

Explanation: A VSAM error was encountered during processing of the VRM data set where
RC=nn is the VSAM return code and FDBK=nnnn is the VSAM feedback return code.
CA-7.VB04 TYPE J RECORD jobname INCOMPLETE

RESOURCE: resource name MISSING
Explanation: An invalid type J record (VRM job record) was found. The job name indicated in the
message is connected to a resource which did not exist on the VRM database. The VRM job record
is rebuilt without the indicated resource.

CA-7.VB05 –CA-7.VB99
CA-7.VB05 TYPE R RECORD resource name INCOMPLETE

JOBNAME: jobname MISSING
Explanation: An invalid type R record (VRM resource record was found. The resource indicated
in the message is connected to a job which did not exist on the VRM database. The VRM resource
record is rebuilt without the indicated job name.
CA-7.VB10 INVALID LRECL FOR CA7RSRC

Explanation: The VRM backup process found an invalid LRECL for the VRM data set DDNAME
CA7RSRC.
User Response: Ensure the data set name specified in the VRM backup procedure under DDNAME
CA7RSRC is the correct data set name for the VRM data set.
CA-7.VB11 SORT ERROR (CA7WORK1)

Explanation: A sort error occurred during the VRM backup processing.
CA-7.VB99 ERROR IN SASSXUNL RC = nn

Explanation: An internal error was encountered during SASSXUNL processing.

3.3 CA-7.VTAM Through CA-7.V001 Messages
CA-7.VTAM –CA-7.V001
CA-7.VTAM TPEND EXIT REQUESTED VTAM ACB CLOSE

Explanation: CA-7's TPEND exit has been scheduled by VTAM. This exit is given control when-
ever VTAM terminates abnormally or is shut down (HALT). The ACB linking the CA-7 application
to VTAM is closed. Issued by SASSLMGR.
User Response: After VTAM has been restarted, an /OPEN,GROUP=groupname must be done
from a non-VTAM terminal to OPEN the ACB and allow access to CA-7 through VTAM terminals.
CA-7.VTAM SASSLMGR NOT ASSEMBLED FOR VTAM

Explanation: The program that handles CA-7's TP control has not been assembled for VTAM.
When a user who does not have VTAM macros makes modifications or applies fixes to this module,
it must be assembled with the &VTAM symbolic set to NO. If this occurred, subsequent attempts to
use VTAM without reassembly with &VTAM set to YES will result in this message. A U499 abend
accompanies this message. Issued by SASSLMGR.
User Response: Verify the source statement sequence # 00007000, make sure the &VTAM sym-
bolic is being set to YES, assemble and link edit SASSLMGR, and link edit the CA-7 nucleus again.
CA-7.VTAM CONNECTION (xxxxxxxx) COMPLETE

Explanation: This is an information message indicating the VTAM terminal (node name xxxxxxxx)
has been successfully connected to CA-7. Issued by SASSI32V.
CA-7.VTAM DISCONNECT
Explanation: This is an information message indicating the VTAM terminal has been disconnected
from CA-7. Issued by SASSW32V.
CA-7.V001 rc yy 00 00000000 tttttt 0000000 00 xxxxxxxx

Explanation: rc is the return code from an ACB OPEN or CLOSE failure, or a SETLOGON
failure. For an open or close failure, yy is the ACBERFLG field. tttttt is the time of day and
xxxxxxxx is the operation that failed, either OPEN, CLOSE or SETLOGON. Issued by
SASSBTMV.
User Response: For OPEN/CLOSE, verify that the APPL specified on the UCC7VTAM statement
is the name of the APPL macro defining CA-7 to VTAM. For SETLOGON, verify that the CA-7
application in VTAM is allowing LOGONs to be queued. A VTAM operator command (DISPLAY)
can be used to determine application status.

CA-7.V001 –CA-7.V001
CA-7.V001 rc aa bb ssssssss hhmmss nnnnnnn cc d xxxxxxxxxx

Explanation: This is a VTAM I/O completion message with the following fields:
rc The return code in R15 from the CHECK macro, or xx if the CHECK macro was not
issued.
aa The RPLRTNCD (RTNCD) field from the RPL involved with the request.
bb The RPLFDB2 (FDBK2) field from the RPL involved with the request.
ssssssss The sense information from the RPL. RPLSSEI (SSENSEI) is the first two positions,
RPLSSMI (SSENSMI) is the next two positions, and RPLUSNSI (USENSEI) is the last
four positions.
hhmmss The time of day.
nnnnnnn The CA-7 terminal name (the NAME on the TERM statement). This may be all Xs if
the terminal name is not available.
cc The RPLREQ field from the RPL.
d Either a C if a CHECK macro has been issued, or an R if the CHECK macro was not
issued because the original macro request (RPLREQ) was not accepted.
xxxxxxx A general error description.
Issued by SASSI32V.
User Response: Refer to Appendix C of the IBM ACF/VTAM Macro Language Reference Manual
(SC38-0261) for a detailed explanation of the RPLRTNCD, RPLFDB2, RPLSSEI, RPLSSMI,
RPLUSNSI return code fields. In Appendix H, the IFGRPL DSECT defines the RPLREQ field.
Contact your installation's CA-7 specialist for assistance if an analysis of the error message does not
clarify the problem.

3.4 Format for VSAM Database Messages
CA-7.Vnnn –CA-7.Vnnn
3.4 Format for VSAM Database Messages
CA-7.Vnnn s mmmm (dddd) RC=xx REAS=yy message text

This is the format of VSAM database error messages displayed as a WTO. Some of
these messages, called noncrux messages, will contain RC=xx REAS=yy. Others, called
crux messages, will not contain RC=xx REAS=yy. A crux message is the first message
to appear when a problem occurs. As the system backs out to successively higher logic
levels, other messages related to the problem occur and display the return codes and
reason codes which they received from the lower level.
Vnnn The unique message number. This is the primary sequence of the fol-
lowing VSAM messages. The following conventions have been observed
in the numbering of VSAM system messages:
002 - 099 Common messages issued within all modules.
100 - 299 Messages issued within functional modules.
300 - 499 Messages issued within subroutine modules.
500 - 599 Messages issued within environment modules.
600 - 699 Messages issued on return from external routines.
700 - 799 Messages issued on return from functional modules.
800 - 899 Messages issued on return from subroutine modules.
900 - 999 Messages issued on return from environment modules.
s Severity indicator. Will contain one of the following values:
I Information
W Warning
E Error
mmmm The last 4 characters of the module name (for example, V0A0).
dddd Displacement within the module issuing the error message.
xx Return code displayed only for noncrux messages. Will contain one of
the following:
04 Warning.
08 Error encountered, processing cannot continue.
12 Error encountered, system cannot recover.
yy Reason code displayed only for noncrux messages.
Message text
A brief description of the problem encountered.

3.5 CA-7.V002 Through CA-7.V020 Messages
CA-7.V002 –CA-7.V008
CA-7.V002 s mmmm (dddd) VCTL EYECATCHER NOT 'VCTL'

Explanation: The control block identifier could not be located. The control block is either missing
or overwritten.
assistance.
CA-7.V003 s mmmm (dddd) VDVT EYECATCHER NOT 'VDVT'

or overwritten.
assistance.
CA-7.V004 s mmmm (dddd) VSCB EYECATCHER NOT 'VSCB'

or overwritten.
assistance.
CA-7.V005 s mmmm (dddd) VACB EYECATCHER NOT 'VACB'

or overwritten.
assistance.
CA-7.V007 s mmmm (dddd) VCPH EYECATCHER NOT 'VCPH'

or overwritten.
assistance.
CA-7.V008 s mmmm (dddd) VCRD EYECATCHER NOT 'VCRD'

or overwritten.
assistance.

CA-7.V009 –CA-7.V015
CA-7.V009 s mmmm (dddd) VDCB EYECATCHER NOT 'VDCB'

or overwritten.
assistance.
CA-7.V010 s mmmm (dddd) VDGP EYECATCHER NOT 'VDGP'

or overwritten.
assistance.
CA-7.V011 s mmmm (dddd) VDTP EYECATCHER NOT 'VDTP'

or overwritten.
assistance.
CA-7.V012 s mmmm (dddd) VETB EYECATCHER NOT 'VETB'

or overwritten.
assistance.
CA-7.V013 s mmmm (dddd) VETB EYECATCHER NOT 'VHDR'

or overwritten.
assistance.
CA-7.V014 s mmmm (dddd) VMSG EYECATCHER NOT 'VMSG'

or overwritten.
assistance.
CA-7.V015 s mmmm (dddd) VPCB EYECATCHER NOT 'VPCB'

or overwritten.
assistance.

CA-7.V016 –CA-7.V020
CA-7.V016 s mmmm (dddd) VRCB EYECATCHER NOT 'VRCB'

or overwritten.
assistance.
CA-7.V017 s mmmm (dddd) VRPL EYECATCHER NOT 'VRPL'

or overwritten.
assistance.
CA-7.V018 s mmmm (dddd) VWCB EYECATCHER NOT 'VWCB'

or overwritten.
assistance.
CA-7.V019 s mmmm (dddd) VWRK EYECATCHER NOT 'VWRK'

or overwritten.
assistance.
CA-7.V020 s mmmm (dddd) VSVT EYECATCHER NOT 'VSVT'

or overwritten.
assistance.

CA-7.V101 –CA-7.V108
CA-7.V101 s mmmm (dddd) MESSAGE TRACE TABLE UNAVAILABLE

Explanation: A CA-7 VSAM message trace table was not allocated during initialization.
User Response: Processing will continue without the message trace table.
CA-7.V102 s mmmm (dddd) CA-7 VSAM DATABASE NOT ON A DASD DEVICE

Explanation: The CA-7 VSAM database must be on a direct-access device. Initialization cannot
continue.
assistance.
CA-7.V103 s mmmm (dddd) STORAGE FOR VSVT/VSCB NOT OBTAINED

Explanation: CPU storage for required control blocks could not be acquired. The initialization of
CA-7 cannot continue.
User Response: Increase region and retry. If problem persists, save console listings and logs.
Contact your installation's CA-7 specialist for assistance.
CA-7.V104 s mmmm (dddd) COLUMN 1 OF DBPARMS STATEMENT NON-BLANK.

Explanation: This message is informational only. It indicates that column 1 of a DBPARMS state-
ment was nonblank. Since only columns 2-71 are valid for DBPARMS information, the information
in column 1 will be discarded. Syntax errors may result.
User Response: If syntax errors occur on DBPARMS statement, or DBPARMS data is rejected for
any reason, check to see if this error is present. If so, shift data to column 2 and retry.
CA-7.V106 s mmmm (dddd) DYNAMIC ALLOCATION SUPPORTED ONLY ON MVS/370 OR MVS/XA

Explanation: Dynamic allocation of the VSAM databases was requested in the DBPARMS control
statements. This feature is supported in MVS. The initialization of CA-7 cannot continue.
User Response: Update the DBPARMS statements specifying ALLOCJCL and a DDNAME
(ddname) for each VSAM data set. Save console listings and logs. Contact your installation's CA-7
CA-7.V108 s mmmm (dddd) MISSING DBPARMS DD STATEMENT

Explanation: The DBPARMS DD statement was not found in the JCL. This is a required data set
for VSAM database support. The initialization of CA-7 cannot continue.
User Response: Update the JCL to include a DBPARMS data set. Save console listings and logs.
The format of this data set is discussed in the CA-7 Systems Programmer Guide. If you have added
the DD statement and the problem persists, contact your installation's CA-7 specialist for assistance.

CA-7.V109 –CA-7.V113
CA-7.V109 s mmmm (dddd) DBPARMS OPEN FAILURE

Explanation: The DBPARMS data set specified in the JCL could not be opened. The initialization
of CA-7 cannot continue.
User Response: Check the allocation of the data set as described in the CA-7 Systems Programmer
Guide. Verify data set and retry. If failure persists, contact your installation's CA-7 specialist for
assistance.
CA-7.V110 s mmmm (dddd) SYNAD ERROR ROUTINE ENTERED

Explanation: An error occurred during initialization of the VSAM databases. The initialization of
CA-7 cannot continue. The DBPARMS DD statement may be pointing to a PDS without specifying
the member name.
assistance.
CA-7.V111 s mmmm (dddd) DYNALLOC FAILED - RC=xxxx,ERRCD=xxxx,INFOCD=xxxx,DSN=x...x

Explanation: An error occurred during dynamic allocation of the VSAM databases. The reason
code, error code, information code, and data set name are shown. The initialization of CA-7 cannot
continue.
User Response: Ensure that the VSAM database data set name(s) match what is specified in the
DBPARMS data set. Also, verify that ddnames for the database do not exist in the execution JCL.
Correct the error and try again. If the problem persists, save console listings and logs. Contact your
CA-7.V112 s mmmm (dddd) DBPARMS NOT FOUND

Explanation: The parameters describing the VSAM database could not be found in internal control
blocks.
User Response: Check UCC7DBASE statements in the DBPARMS data set for correct values. If a
problem persists, save console listings and logs. Contact your installation's CA-7 specialist for assist-
ance. Refer to the CA-7 Systems Programmer Guide for details on DBPARMS statements.
CA-7.V113 s mmmm (dddd) INVALID TYPE DEFINITION ON DBPARMS

Explanation: The parameters describing the VSAM database do not conform with the Data Type
Vector Table definition in program SASSVY00. The data type may be invalid.
User Response: Check UCC7DBASE statements in the DBPARMS data set for correct values. If a
ance. Refer to the CA-7 Systems Programmer Guide for details on DBPARMS statements.

CA-7.V114 –CA-7.V119
CA-7.V114 s mmmm (dddd) DATASET HAS NO DATATYPES DEFINED

Explanation: The parameters describing the VSAM database contain a definition of a data set but
do not include DATATYPE definitions. DATATYPE must be specified for each VSAM data set.
User Response: Review the DBPARMS data set DATATYPE definitions. Correct and reinitialize
CA-7. If a problem persists, save console listings and logs. Contact your installation's CA-7 spe-
cialist for assistance. Refer to the CA-7 Systems Programmer Guide for details on DBPARMS state-
ments.
CA-7.V115 s mmmm (dddd) NON-TERMINAL DYNALLOC ERROR -

INFOCD=xxxx,DSN=x...x
Explanation: Dynamic allocation of the VSAM database received a nonfatal error as shown by
INFOCD. Allocation should have been completed, but attention should be given to the error code.
User Response: Review the INFOCD. If unable to determine the cause, save console listings and
logs. Contact your installation's CA-7 specialist for assistance.
CA-7.V116 s mmmm (dddd) CALLID SPECIFIED NOT USED EXCLUSIVELY FOR

BACKUP FUNCTION
Explanation: The Caller's ID was used for a call other than BACKUP. This is an internal func-
tional error.
assistance.
CA-7.V117 s mmmm (dddd) NUMBER OF VSAM DATASETS EXCEEDS LIMIT

Explanation: The number of VSAM data sets specified during initialization exceeds the number
supported. Initialization cannot continue.
User Response: Be sure DBPARMS statements define only three data sets. If problem persists
after correcting DBPARMS, save console listings and logs. Contact your installation's CA-7 spe-
cialist for assistance.
CA-7.V118 s mmmm (dddd) DATATYPE CODE DUPLICATION IN DBPARMS

Explanation: A DATATYPE entry in the VSAM database definition in DBPARMS has been
repeated. Data types may not span multiple VSAM data sets.
User Response: Correct the DBPARMS parameters to match the database or else back up the data-
base using program SASSBK00 and reload according to the new DATATYPE configuration.
CA-7.V119 s mmmm (dddd) NUMBER OF DATATYPE CODES EXCEEDS LIMIT

Explanation: The number of DATATYPEs specified in DBPARMS exceeds the number allowed
according to table SASSVY00.
User Response: Correct the DBPARMS parameters to match the number of allowed DATATYPEs.
Refer to the CA-7 Systems Programmer Guide.

CA-7.V120 –CA-7.V126
CA-7.V120 s mmmm (dddd) DATATYPE NOT DEFINED TO VSAM SYSTEM

Explanation: The DATATYPE encountered has not been defined in the Data Relationships Table,
SASSVY00.
User Response: Check the DBPARMS parameters for invalid DATATYPE entries and correct.
CA-7.V121 s mmmm (dddd) DATATYPE INVALID FOR SPECIFIED DATASET

Explanation: The DATATYPE encountered was not defined in the specified data set. The
DBPARMS specifications may be incorrect.
User Response: Check the DBPARMS parameters for invalid or missing DATATYPE entries and
correct. Refer to the CA-7 Systems Programmer Guide.
CA-7.V122 s mmmm (dddd) DATATYPE REQUIRED FOR DATASET IS UNSPECIFIED

Explanation: A DATATYPE on a VSAM database was not defined in DBPARMS.
User Response: Check the DBPARMS parameters for missing DATATYPE entries and correct.
CA-7.V123 s mmmm (dddd) PARAMETER xxxxxx ABSENT OR INVALID

Explanation: A required DBPARMS parameter was not found or contained invalid data. The
called program returns to the caller with an error code. Other messages usually follow.
User Response: Correct the parameter. If problems persist, save console listings and logs. Contact
CA-7.V124 s mmmm (dddd) RC=xx REAS=yy VSAM KEY NOT IN

ASCENDING SEQUENCE
Explanation: A key sequence error was detected while attempting to write to the Backup data set.
The record in error is not written.
User Response: The database record which was in error may need to be reentered correctly after
reload and/or corrected on the existing database. Save console listings and logs. Contact your instal-
lation's CA-7 specialist for assistance.
CA-7.V126 s mmmm (dddd) ACCTYP=LOAD SPECIFIED WITH SOME OTHER ACCTYP

Explanation: An invalid combination of ACCESS TYPE parameters was used in the call to the
VSAM Connection module.
User Response: The parameters of the executing program must be specified correctly. Save
console listings and logs. Contact your installation's CA-7 specialist for assistance.

CA-7.V127 –CA-7.V132
CA-7.V127 s mmmm (dddd) INCOMPATIBLE ACCTYPS xxxxxx AND yyyyyy SPECIFIED

VSAM Connection module.
User Response: The parameters of the executing program must be specified correctly. Save
console listings and logs. Contact your installation's CA-7 specialist for assistance.
CA-7.V128 s mmmm (dddd) INCOMPATIBLE ACCSYNS ASYN AND SYNC SPECIFIED

Explanation: An invalid combination of ACCESS parameters, (SYNChronous and ASYNchronous)
was used in the call to the VSAM Connection module.
User Response: The parameters of the executing program must be specified correctly by the calling
program. Correct and resubmit. Save console listings and logs. Contact your installation's CA-7
CA-7.V129 s mmmm (dddd) ACCSYN=xxxx SPECIFIED, BUT yyyy SPECIFIED PREVIOUSLY

Explanation: An invalid combination of ACCESS parameters was used in the call to the VSAM
Connection module.
CA-7.V130 s mmmm (dddd) ACCTYP=xxxxxx SPECIFIED, BUT yyyyyy SPECIFIED PREVIOUSLY

VSAM Connection module. BKUP may have been specified after a RELD request.
CA-7.V131 s mmmm (dddd) DATASET NOT VSAM, DSN=x...x

Explanation: DBPARMS referenced data set x...x, but the data set is not a VSAM data set.
User Response: Check DSN and DD values in both DBPARMS and execution JCL. Correct the
reference so that a VSAM file is being referenced. Also verify that the ALLVSAM database was
requested. If the problem persists, save the listings and contact your installation's CA-7 specialist for
assistance.
CA-7.V132 s mmmm (dddd) VSAM DATASET NOT INITIALIZED BY RELOAD, DSN=x...x

Explanation: One of two situations has occurred:
If the action taken was not a RELOAD, the data set is empty and unusable.
If the action taken was a RELOAD, the data set is not empty and does not contain the CNTL
records required by CA-7.
User Response: Proceed as follows:

CA-7.V133 –CA-7.V139
If the action was not a RELOAD, initialize the data set by performing a RELOAD from a null
backup data set.
If the action taken was a RELOAD, verify that DBPARMS is referencing the correct DSN. If
the DSN is correct, use IDCAMS to DELETE the DSN; then retry the RELOAD. This may be
required if the database is on SMS controlled volumes.
If the problem persists, save the listings and contact your installation's CA-7 specialist for assist-
ance.
CA-7.V133 s mmmm (dddd) CALLID xxxxxxxx STILL ACTIVE AT DISCONNECT

Explanation: A thread identified by CALLID was active during DISCONNECT processing. Prob-
ably caused by use of one of the "fast shutdown" options.
CA-7.V134 s mmmm (dddd) ATTEMPTED TO DISCONNECT ACCESS TYPE NOT CONNECTED

Explanation: A request to DISCONNECT during termination was for an invalid ACCESS TYPE
(for example, RELD was requested when BKUP was CONNECTed).
assistance.
CA-7.V135 s mmmm (dddd) CONNECTION FAILED DUE TO ABOVE ERRORS

Explanation: A request to CONNECT to the VSAM database failed because of errors found earlier
in the execution.
User Response: See the messages issued earlier. Save console listings and logs. Contact your
CA-7.V136 s mmmm (dddd) LIST CONNECTION SUCCESSFUL

Explanation: A request to CONNECT to the VSAM database for LISTing data was successful.
CA-7.V137 s mmmm (dddd) ATTEMPTED TO CLOSE BACKUP DD WHEN NOT OPENED

Explanation: A request to close the Backup data set failed because the data set had already been
closed or had not been opened.
assistance.
CA-7.V139 s mmmm (dddd) VSAM DATABASE CLOSE FAILED

Explanation: A request to close the VSAM database failed.
assistance.

CA-7.V140 –CA-7.V151
CA-7.V140 s mmmm (dddd) END-OF-DATA DETECTED ON BACKUP DD

Explanation: An unexpected END-OF-DATA condition was detected on the Backup data set.
User Response: Verify that the data set being used as input to the database load is the proper
Backup data set. Save console listings and logs. Contact your installation's CA-7 specialist for
assistance.
CA-7.V143 s mmmm (dddd) VRCB SEARCH FAILED

Explanation: A VRCB for a specific data type could not be found on VRCB chain.
assistance.
CA-7.V145 s mmmm (dddd) SUBROUTINE MODULE LOAD SEQUENCE FAILED

Explanation: An SVLOAD request for a subroutine could not be completed.
assistance.
CA-7.V146 s mmmm (dddd) ENVIRONMENT MODULE LOAD SEQUENCE FAILED

Explanation: Initialization requested a load of an environment module which failed.
assistance.
CA-7.V147 s mmmm (dddd) FUNCTIONAL MODULE LOAD SEQUENCE FAILED

Explanation: Initialization requested a load of a main line module which failed.
assistance.
CA-7.V148 s mmmm (dddd) TABLE MODULE LOAD SEQUENCE FAILED

Explanation: Initialization requested a load of a table module which failed.
assistance.
CA-7.V150 s mmmm (dddd) VCTL TOO LARGE FOR BACKUP DD LRECL

Explanation: The LRECL for the Backup data set is smaller than the size of the internal control
block which contains the DBPARMS parameters.
User Response: Increase the LRECL on the BACKUP DD statement and resubmit. Minimum
LRECL is 3122. Contact your installation's CA-7 specialist for assistance as necessary.
CA-7.V151 s mmmm (dddd) UCC7VSAM INITIALIZATION COMPLETE

Explanation: The VSAM databases are ready for processing.

CA-7.V152 –CA-7.V158
CA-7.V152 s mmmm (dddd) ABEND xxx-xx DETECTED IN OPEN/CLOSE/EOV

FOR BACKUP DD - action
Explanation: An abnormal condition occurred while processing the Backup data set.
User Response: Save console listings and logs. If abend code is 002-18, increase the LRECL in
the BACKUP DD. Minimum LRECL is 3122. Contact your installation's CA-7 specialist for assist-
ance.
CA-7.V154 s mmmm (dddd) RELEASE CALLED FOR RELOAD BEFORE EOD DETECTED
Explanation: Termination was requested before all data was processed on the Backup data set.
User Response: The database may need to be reloaded. Save console listings and logs. Contact
CA-7.V155 s mmmm (dddd) SPECIFIED CALLID ALREADY IN USE

Explanation: The CALLER ID used for backup or reload operations cannot be used for any other
purpose while connected for BKUP or RELD. Either BKUP or RELD connection was in effect and
the CALLER ID used for backup or reload was also used for another purpose (such as to read the
VSAM database).
User Response: Correct CALLID conflict and resubmit. Contact your installation's CA-7 specialist
for assistance.
CA-7.V156 s mmmm (dddd) SPECIFIED DATATYPE NOT DEFINED IN VDTP

Explanation: The DATATYPE encountered has not been defined.
User Response: See program SASSVY00 for definition of data types and relationships.
CA-7.V157 s mmmm (dddd) RELOAD ATTEMPTED W/O LOAD OR RELOAD ACCESS TYPE CON-
NECTED
Explanation: A database RELOAD request was made without previously setting up a
LOAD/RELOAD environment.
User Response: Ensure that the job specified the proper parameters on the EXEC statement.
Correct the parameters and resubmit. Refer to the CA-7 Systems Programmer Guide.
CA-7.V158 s mmmm (dddd) ERROR IN LAST RECORD FLAG

Explanation: The last Record Flag was expected to be turned on in the VPCB, but it was not.
User Response: Verify that the BACKUP DD input to the RELOAD program is correct. Only
backup files created by SASSBK00 can be reloaded. Save console listings and logs. Contact your

CA-7.V159 –CA-7.V171
CA-7.V159 s mmmm (dddd) RELOAD EOD LOGIC ERROR

Explanation: Program SASSV080 could not complete End-Of-Data processing properly. EOD may
have been detected twice.
User Response: Verify that the BACKUP DD input to the RELOAD program is correct. Only
backup files created by SASSBK00 can be reloaded. Save console listings and logs. Contact your
CA-7.V160 s mmmm (dddd) NORMAL CONNECTION ATTEMPTED WITH DBTYPE NOT ALLVSAM
Explanation: The JCL used to execute the job had a parameter other than ALLVSAM when a
NORMAL allocation (CONNECTION) of VSAM databases was requested.
User Response: Correct the JCL and resubmit.
CA-7.V161 s mmmm (dddd) CALLID xxxxxxxx INVALID TYPE/DATATYPE COMBINATION

Explanation: An invalid data set type or data record type was specified. Probable programming
error.
User Response: Save console listings and logs, plus any screen messages and commands issued.
CA-7.V167 s mmmm (dddd) DBPARMS PARSE COMPLETE

Explanation: The parse of DBPARMS completed successfully.
CA-7.V168 s mmmm (dddd) DBPARMS ERROR: IDCAMS CTL STMT SYNTAX ERROR
Explanation: IDCAMS detected a syntax error on DBPARMS input control statements.
User Response: Correct IDCAMS control statement in DBPARMS data set.
CA-7.V169 s mmmm (dddd) DBPARMS ERROR: PARAMETER ABSENT OR INVALID - x...x

Explanation: Parameter x...x is absent or invalid.
User Response: Correct DBPARMS statement and retry.
CA-7.V170 s mmmm (dddd) DBPARMS ERROR: DDNAME PARAMETER NOT SPECIFIED WITH
ALLOCJCL
Explanation: A DDNAME parameter is required if ALLOCJCL is specified.
User Response: Include DDNAME parameter and retry.
CA-7.V171 s mmmm (dddd) DBPARMS ERROR: ALLOCDYN/ALLOCJCL PARAMETERS MUTU-

ALLY EXCLUSIVE
Explanation: ALLOCDYN and ALLOCJCL may not both be specified.
User Response: Eliminate either ALLOCDYN or ALLOCJCL and retry.

CA-7.V172 –CA-7.V178
CA-7.V172 s mmmm (dddd) DBPARMS ERROR: DATATYPES/STRINGS PARAMETERS INCOMPAT-

IBLE
Explanation: Number of data types specified differs from number of string specifications.
User Response: See that number of entries for DATATYPE parameter is same as number of entries
for STRINGS parameter.
CA-7.V173 s mmmm (ddd) DBPARMS ERROR: ALLOCJCL SPECIFIED FOR DDN=xxxxxxxx BUT
DSNAME CONFLICT EXISTS
Explanation: An error was detected for a UCC7DBASE entry in DBPARMS. The error is associ-
ated with DDN=xxxxxxxx. The data set referenced by the DDN in the JCL does not match the
NAME indicated for the DEFINE CLUSTER entry in DBPARMS.
User Response: Perform one of the following:
1. Correct the DDNAME entry in DBPARMS; or
2. Change the NAME in IDCAMSDEFINE in DBPARMS; or
3. Change the DSN in the JCL.
CA-7.V175 s mmmm (dddd) CALLID xxxxxxxx TERM=YES REQUIRES TYPE=OUTP

Explanation: The TERM=YES parameter on an SVEXTPUT macro is specified only internally
within the VSAM system. When used, it should always be for TYPE=OUTP.
User Response: Verify that TERM=YES is really required. If not, take it off and retry. If so, use
TYPE=OUTP or contact your installation's CA-7 specialist for assistance.
CA-7.V176 s mmmm (dddd) CALLID xxxxxxxx ACCTYP=RELD REQUIRES TYPE=ADD/CAT/OUTP

Explanation: If a database reload has been requested by specifying ACCTYP=RELD on the
SVCONN macro, then SVEXTPUT may only be issued with TYPE=ADD/CAT/OUTP.
User Response: Verify that TYPE=ADD, CAT or OUTP for all SVEXTPUT calls executed.
CA-7.V177 s mmmm (dddd) CALLID xxxxxxxx LOGIC ERROR ENCOUNTERED

Explanation: An error occurred while attempting to write to or delete an entry in the VSAM data-
base.
assistance.
CA-7.V178 s mmmm (dddd) CALLID xxxxxxxx RECRD/BLKAD PARAMETERS NOT ALLOWED ON

TYPE=UPDT OR TYPE=DELT/UNCT
Explanation: An SVEXTPUT macro call was issued with TYPE=UPDT or TYPE=DELT/UNCT
which included a RECRD or BLKAD parameter. These parameters may not be used with the speci-
fied TYPE.
User Response: Correct SVEXTPUT macro call and retry.

CA-7.V179 –CA-7.V185
CA-7.V179 s mmmm (dddd) CALLID xxxxxxxx TYPE=UPDT REQUIRES LAST ACCESS IN UPDATE
MODE
Explanation: An SVEXTPUT macro call was issued with TYPE=UPDT, but a previous
SVEXTGET macro had not been issued for that entry specifying the UPDATE parameter.
User Response: Issue an SVEXTGET call for UPDATE mode before issuing the SVEXTPUT
macro, TYPE=UPDT and retry.
CA-7.V180 s mmmm (dddd) CALLID xxxxxxxx TYPE=UPDT REQUIRES EXISTING VBUF/VRPL

Explanation: The VBUF or VRPL control blocks required for this SVEXTPUT call were not
found.
User Response: Check that no external macro calls were issued prior to the SVEXTPUT call which
would cause update intent to be released. If none found, save console listings and logs and contact
the CA-7 specialist.
CA-7.V181 s mmmm (dddd) CALLID xxxxxxxx RECRD PARAMETER REQUIRED ON TYPE=RCAT

Explanation: SVEXTPUT was called with TYPE=RCAT, but no RECRD parameter was provided
pointing to the record to be output.
User Response: Provide RECRD parameter and retry.
CA-7.V182 s mmmm (dddd) CALLID xxxxxxxx BLKAD PARAMETER NOT ALLOWED ON

TYPE=RCAT
Explanation: SVEXTPUT was called with TYPE=RCAT, and a BLKAD parameter was provided.
User Response: Provide RECRD parameter instead of BLKAD and retry.
CA-7.V183 s mmmm (dddd) CALLID xxxxxxxx TYPE=UPDT/REPL/RCAT REQUIRES EXISTING

VPCB
Explanation: SVEXTPUT was called with TYPE=UPDT or REPL or RCAT but no previous
SVEXTGET had been done.
User Response: Retrieve record with UPDATE intent before SVEXTPUT call and retry.
CA-7.V184 s mmmm (dddd) CALLID xxxxxxxx RECRD PARAMETER REQUIRED ON

TYPE=ADD/CAT
Explanation: SVEXTPUT was called with TYPE=ADD or CAT but no RECRD parameter was
provided.
User Response: Add RECRD parameter to calling sequence and retry.

TYPE=ADD/CAT
Explanation: SVEXTPUT was called with TYPE=ADD or CAT and a BLKAD parameter was
included in the calling sequence.
User Response: Ensure that calling sequence provides a RECRD parameter but no BLKAD param-
eter and retry.

CA-7.V186 –CA-7.V199
CA-7.V186 s mmmm (dddd) CALLID xxxxxxxx EXISTING VBUF/VRPL NOT ALLOWED ON

TYPE=ADD/CAT
Explanation: SVEXTPUT was called with TYPE=ADD or CAT and a VBUF or VRPL control
block was found to already exist for the data type to be added or cataloged.
User Response: Ensure that record being added or cataloged is not already present in database. If
it is there, either remove it or don't try to add it. If it is not already there, save console listings and
logs and contact your installation's CA-7 specialist for assistance.
CA-7.V187 s mmmm (dddd) CALLID xxxxxxxx RECRD PARAMETER REQUIRED ON TYPE=OUTP

FOR DS DS
Explanation: SVEXTPUT was called with TYPE=OUTP and DSTYPE=DS but no RECRD param-
eter was provided.
User Response: Add RECRD parameter to SVEXTPUT call and retry.

TYPE=OUTP FOR DS DS
Explanation: SVEXTPUT was called with TYPE=OUTP and DSTYPE=DS and BLKAD parameter
was used.
User Response: Ensure that SVEXTPUT calling sequence contains no BLKAD parameter and
includes a RECRD parameter and retry.
CA-7.V189 s mmmm (dddd) CALLID xxxxxxxx RECRD OR BLKAD PARAMETER REQUIRED ON

TYPE=OUTP FOR JOB DS
Explanation: SVEXTPUT was called with TYPE=OUTP and DSTYPE=JOB but no RECRD or
BLKAD parameter was provided.
User Response: Ensure that SVEXTPUT calling sequence includes either a RECRD or BLKAD
parameter and retry.
CA-7.V190 s mmmm (dddd) CALLID xxxxxxxx TYPE=OUTP REQUIRE EXISTING VBUF/VRPL IN

OUTP MODE
Explanation: SVEXTPUT was called with TYPE=OUTP but no previous SVEXTGET had been
executed with UPDATE intent.
User Response: Issue an SVEXTGET with UPDATE intent prior to the SVEXTPUT call and retry.
CA-7.V199 s mmmm (dddd) NOT ENOUGH SPACE IN WORK AREA FOR USE BY MODULE
xxxxxxxx
Explanation: SVSTATUS needed more work area to pass requested data than was provided. If the
calling program is employing the technique suggested below, this message may be normal.
User Response: The amount of work area required will be returned by SVSTATUS at offset 2 from
the start of the work area. Allocate that much space before calling SVSTATUS. (If work area
required will vary, a trial call of SVSTATUS can be made specifying a 4-byte work area.
SVSTATUS will then return with this message and the exact amount of storage required in the work
area. The correct amount of storage can then be acquired and another call of SVSTATUS made.)

CA-7.V200 –CA-7.V206
CA-7.V200 s mmmm (dddd) KEYNAME xxxxxxxx UNKNOWN TO SASSV090 STATUS MODULE

Explanation: SVSTATUS macro was called specifying a keyblock which pointed to a keyname
unknown to the Status Module, SASSV090.
User Response: Check all keyblocks in calling sequence. See that spelling of each keyname
pointed to is correct and retry.
CA-7.V202 s mmmm (dddd) MORE WORK AREA REQUIRED THAN AVAILABLE

Explanation: SVSTATUS needed more work area to pass requested data than was provided. If the
calling program is employing the technique suggested below, this message may be normal.
User Response: The amount of work area required will be returned by SVSTATUS at offset 2 from
the start of the work area. Allocate that much space before calling SVSTATUS. (If work area
required will vary, a trial call of SVSTATUS can be made specifying a 4-byte work area.
SVSTATUS will then return with this message and the exact amount of storage required in the work
area. The correct amount of storage can then be acquired and another call of SVSTATUS made.)
CA-7.V203 s mmmm (dddd) DBPARMS VDCB NOT AVAILABLE

Explanation: SVSTATUS macro was called requesting DBPARMS information before SVINIT
macro was issued to read DBPARMS data set.
User Response: Issue SVSTATUS call after SVINIT call and retry.
CA-7.V204 s mmmm (dddd) DBPARMS STATEMENTS NOT AVAILABLE.

Explanation: SVSTATUS macro was called requesting DBPARMS information before SVINIT
macro was issued to read DBPARMS data set.
CA-7.V205 s mmmm (dddd) BACKUP VDCB NOT AVAILABLE

Explanation: SVSTATUS macro was called requesting BACKUP information before SVCONN
macro was issued to open Backup data set, creating the VDCB.
User Response: Issue SVSTATUS call after SVCONN call and retry.
CA-7.V206 s mmmm (dddd) VSAMDB VCTL NOT AVAILABLE

Explanation: SVSTATUS macro was called requesting VSAM database information before SVINIT
macro was issued to build database control blocks such as VCTL from which SVSTATUS gets infor-
mation.

CA-7.V207 –CA-7.V214
CA-7.V207 s mmmm (dddd) KEYNAME xxxxxxxx IS NOT CONTROL BLOCK ANCHORED OFF VSCB
Explanation: This message is not issued unless the branch control table in SASSV090 contains
control block names which are not anchored off VSCB. This could only happen if a system modifi-
cation were made to the VSCB but no corresponding change was made to the SASSV090 control
table.
User Response: Check for any changes made and correct. If unable to determine the cause, save
console logs and listings. Contact your installation's CA-7 specialist for assistance.
CA-7.V208 s mmmm (dddd) REQUIRED DDNAME PARAMETER NOT SPECIFIED - DSN=x...x

Explanation: DDNAME is required for each data set on the DBPARMS cards if ALLOCJCL were
specified.
User Response: Add DDNAME parameter to DBPARMS where required and retry.
CA-7.V209 s mmmm (dddd) DATA SET HAS NO TYPES DEFINED - DSN=x...x

Explanation: Each data set defined in the DBPARMS statements must have at least one data type
defined for it.
User Response: Add DATATYPE parameter to DBPARMS for DSN=x...x and retry.
CA-7.V210 s mmmm (dddd) NOT ALL DATATYPES DEFINED IN DBPARMS

Explanation: Each legal data type must be specified once and only once in the DATATYPE param-
eter on the DBPARMS statements.
User Response: Check DBPARMS DATATYPE specifications to be sure all data types are
included and retry.
CA-7.V213 s mmmm (dddd) REQUESTED CONTROL BLOCK xxxx NOT AVAILABLE OR

EYECATCHER INCORRECT
Explanation: User called SVSTATUS macro requesting control block xxxx as keyname in keyblock
specified. There are two possible reasons for this error. Either the location pointed to by the VSCB
for that control block does not contain the proper eyecatcher for the control block indicating a system
problem or the VSCB pointer is zero, indicating the control block does not exist.
User Response: Most VSAM control blocks anchored off the VSCB are created at initialization
time. A few, such as the BACKUP VDCB, are only present after connection has been performed.
Ensure that SVINIT and SVCONN have been called before SVSTATUS. If not, correct code and
retry. Otherwise, save console logs and listings. Contact your installation's CA-7 specialist for
assistance.
CA-7.V214 s mmmm (dddd) VCTL TOO LARGE FOR VSAM LRECL - DSN=x...x
Explanation: The VCTL is written out to the database for record keeping and documentation pur-
poses. It is required that the LRECL for the database be large enough to handle it.
User Response: Increase maximum value in RECORDSIZE parameter for the identified data set in
the DBPARMS statements, then reload the database. Smallest maximum record size is approximately
3122. Refer to the CA-7 Systems Programmer Guide for details concerning DBPARMS statements
and reloading the database.

CA-7.V215 –CA-7.V222
CA-7.V215 s mmmm (dddd) WORK AREA MUST BE AT LEAST 4 BYTES LONG

Explanation: The work area passed to SVSTATUS must be at least 4 bytes long for status to put a
2-byte length available and a 2-byte length needed field in.
User Response: Specify a work area length of at least 4 in SVSTATUS call and retry.
CA-7.V216 s mmmm (dddd) GET FOR UPDATE WITHOUT ACCESS TYPE NORMAL
Explanation: The use of SVEXTGET with UPDATE intent specified indicates the intention of
modifying an existing database. This may only be done if access type specified on SVCONN macro
was NORMAL.
User Response: Resolve SVCONN and SVEXTGET incompatibilities and retry. Contact your
installation's CA-7 specialist for assistance, saving console listings and logs.
CA-7.V217 s mmmm (dddd) GET CALLED WITHOUT CALLID PROVIDED

Explanation: SVEXTGET macro requires CALLID parameter.
User Response: Add CALLID parameter to SVEXTGET call and retry.
CA-7.V218 s mmmm (dddd) GET CALLED WITHOUT KEYAD PROVIDED FOR CALLID xxxxxxxx
Explanation: SVEXTGET macro requires KEYAD parameter.
User Response: Add KEYAD parameter to SVEXTGET call and retry.
CA-7.V219 s mmmm (dddd) GET CALLED WITHOUT RECTYP PROVIDED FOR CALLID xxxxxxxx
Explanation: SVEXTGET macro requires RECTYP parameter.
User Response: Add RECTYP parameter to SVEXTGET call and retry.
CA-7.V220 s mmmm (dddd) GET CALLED WITHOUT DSTYPE PROVIDED FOR CALLID xxxxxxxx
Explanation: SVEXTGET macro requires DSTYPE parameter.
User Response: Add DSTYPE parameter to SVEXTGET call and retry.
CA-7.V221 s mmmm (dddd) GET CALLED WITHOUT RETTYP PROVIDED FOR CALLID xxxxxxxx
Explanation: SVEXTGET macro requires RETTYP parameter.
User Response: Add RETTYP parameter to SVEXTGET call and retry.
CA-7.V222 s mmmm (dddd) GET CALLED WITHOUT A VALID RETTYP PROVIDED FOR CALLID
xxxxxxxx
Explanation: RETTYP parameter not valid.
User Response: Ensure that SVEXTGET call specified a valid RETTYP.

CA-7.V223 –CA-7.V228
CA-7.V223 s mmmm (dddd) GET CALLED WITH RETTYP=UNIQUE AND NO DSTYPE VALUE FOR
CALLID xxxxxxxx
Explanation: On an SVEXTGET call, RETTYP=UNIQUE and DSTYPE pointed to a location con-
taining blanks or ALL. When retrieval type is unique, a specific DSTYPE must be given or pointed
to.
User Response: Specify DS or JOB or IDS for DSTYPE and retry.
CA-7.V224 s mmmm (dddd) GET CALLED WITH RETTYP=UNIQUE AND NO RECTYP VALUE FOR
CALLID xxxxxxxx
Explanation: On an SVEXTGET call, RETTYP=UNIQUE and RECTYP pointed to a location con-
taining blanks or ALL. When retrieval type is unique, a specific RECTYP must be given.
User Response: Specify DIR or MEM or IDS for RECTYP and retry.
CA-7.V225 s mmmm (dddd) GET CALLED WITH RETTYP=UNIQUE AND NO KEYAD VALUE FOR
CALLID xxxxxxxx
Explanation: On an SVEXTGET call, RETTYP=UNIQUE and KEYAD pointed to an invalid
location. When retrieval type is unique, a specific key must be provided at location KEYAD.
User Response: Point KEYAD at key of record desired and retry.
CA-7.V226 s mmmm (dddd) GET CALLED WITH RETTYP=UNIQUE AND KEYAD VALUE IS LESS
THAN SPACES FOR CALLID xxxxxxxx
Explanation: On an SVEXTGET call, RETTYP=UNIQUE and KEYAD pointed to a location con-
taining no key. When retrieval type is unique, a specific key must be provided at location KEYAD.
CA-7.V227 s mmmm (dddd) GET CALLED WITH RETTYP=NODE AND NO DSTYPE VALUE FOR
CALLID xxxxxxxx
Explanation: On an SVEXTGET call, RETTYP=NODE and DSTYPE pointed to a location con-
taining blanks or ALL. When retrieval type is node, a specific DSTYPE must be provided.
User Response: Point DSTYPE at location containing JOB or DS or IDS.
CA-7.V228 s mmmm (dddd) GET CALLED WITH RETTYP=NODE AND NO RECTYP VALUE FOR
CALLID xxxxxxxx
Explanation: On an SVEXTGET call, RETTYP=NODE and RECTYP pointed to a location con-
taining blanks or ALL. When retrieval type is node, a specific RECTYP must be provided.
User Response: Point RECTYP at location containing DIR or MEM or IDS.

CA-7.V229 –CA-7.V235
CA-7.V229 s mmmm (dddd) GET CALLED WITH RETTYP=NODE AND NO KEYAD VALUE FOR
CALLID xxxxxxxx
Explanation: On an SVEXTGET call, RETTYP=NODE and KEYAD pointed to an invalid
location. When retrieval type is NODE, a specific key must be provided at location KEYAD.
CA-7.V230 s mmmm (dddd) GET CALLED WITH RETTYP=NODE AND KEYAD VALUE IS LESS
Explanation: On an SVEXTGET call, RETTYP=NODE and KEYAD pointed to a location con-
taining no key. When retrieval type is NODE, a specific key must be provided at location KEYAD.
CA-7.V231 s mmmm (dddd) GET CALLED WITH RETTYP=FIRSTX AND NO KEYAD VALUE FOR
CALLID xxxxxxxx
Explanation: On an SVEXTGET call, RETTYP=FIRSTx and KEYAD pointed to an invalid
location. When retrieval type is FIRSTx, KEYAD must point to a location to contain key returned.
User Response: Point KEYAD at valid address and retry.
CA-7.V232 s mmmm (dddd) GET CALLED WITH RETTYP=FIRSTX AND COULD NOT DETERMINE
THE (X) VALUE FOR CALLID xxxxxxxx
Explanation: FIRSTx was specified for RETTYP on an SVEXTGET call where x was not a legal
value.
User Response: Correct x value in macro call and retry.
CA-7.V233 s mmmm (dddd) GET CALLED WITH RETTYP=DIR AND NO DSTYPE VALUE FOR
CALLID xxxxxxxx
Explanation: SVEXTGET RETTYP=DIR macro call must include a specific DSTYPE value (other
than blanks or ALL) to avoid ambiguities.
User Response: Point DSTYPE to a location containing DS or JOB or IDS. Retry.
CA-7.V234 s mmmm (dddd) GET CALLED WITH RETTYP=DIR AND NO RECTYP VALUE FOR
CALLID xxxxxxxx
Explanation: SVEXTGET RETTYP=DIR macro call must include RECTYP=MEM.
User Response: Include RECTYP=MEM and retry.
CA-7.V235 s mmmm (dddd) GET CALLED WITH RETTYP=DIR AND NO KEYAD VALUE FOR
CALLID xxxxxxxx
Explanation: SVEXTGET RETTYP=DIR was called but KEYAD pointed to an invalid location.
User Response: Point KEYAD to location of valid key and retry.

CA-7.V236 –CA-7.V241
CA-7.V236 s mmmm (dddd) GET CALLED WITH RETTYP=DIR AND KEYAD VALUE IS LESS THAN
SPACES FOR CALLID xxxxxx
Explanation: SVEXTGET macro, RETTYP=DIR was issued but KEYAD location pointed to did
not contain a valid key.
User Response: Point KEYAD to location of valid key and retry.
CA-7.V237 s mmmm (dddd) GET CALLED WITH RETTYP=DIR AND DETERMINED DATATYPE
CODE IS INVALID FOR CALLID xxxxxxxx
Explanation: Either DSTYPE, RECTYP and KEYAD form an illegal combination (for example,
DSTYPE=JOB, RECTYP=IDS) or the SASSVY00 table is invalid.
User Response: Verify that the specified DSTYPE, RECTYP and KEYAD parameters specify a
valid combination. If not, correct and retry. If unresolved, save console log and listings and contact
CA-7.V238 s mmmm (dddd) GET CALLED WITH RETTYP=DIR AND PRECEDING

RETTYP=FIRST/NODE/NEXT NOT FOUND FOR CALLID xxxxxxxx
Explanation: An SVEXTGET call specifying RETTYP=DIR requires a previous SVEXTGET call
specifying RETTYP=FIRSTX or NODE or NEXT.
User Response: Try request again, if problem persists, verify that previous SVEXTGET specified
the same DSTYPE as this call and that RECTYP=DIR was specified with RETTYP=FIRSTx or
NODE or NEXT. Save console listings and logs, then contact your installation's CA-7 specialist for
assistance.
CA-7.V239 s mmmm (dddd) GET CALLED WITH RETTYP=NEXT AND NO DSTYPE VALUE FOR
CALLID xxxxxxxx
Explanation: An SVEXTGET call specifying RETTYP=NEXT was specified and the location
pointed to by DSTYPE was invalid.
User Response: Verify that DSTYPE points to a valid address to contain the DSTYPE returned and
retry.
CA-7.V240 s mmmm (dddd) GET CALLED WITH RETTYP=NEXT AND NO RECTYP VALUE FOR
CALLID xxxxxxxx
pointed to by RECTYP was invalid.
User Response: Verify that RECTYP points to a valid address to contain the RECTYP returned and
retry.
CA-7.V241 s mmmm (dddd) GET CALLED WITH RETTYP=NEXT AND NO KEYAD VALUE FOR
CALLID xxxxxxxx
pointed to by KEYAD was invalid.
User Response: Verify that KEYAD points to a valid address to contain the key returned and retry.

CA-7.V242 –CA-7.V247
CA-7.V242 s mmmm (dddd) GET CALLED WITH RETTYP=NEXT AND KEYAD VALUE IS LESS
Explanation: An SVEXTGET call specifying RETTYP=NEXT was specified and KEYAD did not
contain a valid key. KEYAD must point to the key which was returned on the previous SVEXTGET
RETTYP=FIRSTX/NEXT call.
User Response: Verify that KEYAD points to the previous key returned and retry.
CA-7.V243 s mmmm (dddd) RETTYP=NEXT REQUESTED WHEN INITIAL GET WAS NOT FOUND,
CALLID xxxxxxxx
Explanation: An SVEXTGET call specifying RETTYP=NEXT must be preceded by a
RETTYP=FIRSTX call.
User Response: Verify that a previous SVEXTGET RETTYP=FIRSTX is executed and retry.
CA-7.V244 s mmmm (dddd) RETTYP=NEXT REQUESTED WHEN INITIAL RETTYP NOT SET UP,
CALLID xxxxxxxx
Explanation: An SVEXTGET call specifying RETTYP=NEXT must be preceded by a
RETTYP=FIRSTX call.
User Response: Verify that a previous SVEXTGET RETTYP=FIRSTX is executed and retry.
CA-7.V245 s mmmm (dddd) GET CALLED WITH RETTYP=NREC AND NO DSTYPE VALUE FOR
CALLID xxxxxxxx
Explanation: A SVEXTGET call specifying RETTYP=NREC must specify DSTYPE pointing to a
valid location containing the DSTYPE from a previous call.
User Response: Verify that DSTYPE points to a valid location and contains the DSTYPE returned
from the previous call.
CA-7.V246 s mmmm (dddd) GET CALLED WITH RETTYP=NREC AND NO RECTYP VALUE FOR
CALLID xxxxxxxx
Explanation: An SVEXTGET call specifying RETTYP=NREC must specify RECTYP pointing to a
valid location containing the RECTYP from a previous call.
User Response: Verify that RECTYP points to a valid location and contains the RECTYP returned
from the previous call. Retry.
CA-7.V247 s mmmm (dddd) GET CALLED WITH RETTYP=NREC AND NO KEYAD VALUE FOR
CALLID xxxxxxxx
Explanation: An SVEXTGET call specifying RETTYP=NREC must specify KEYAD pointing to a
valid location containing the key from a previous call.
User Response: Verify that KEYAD points to a valid location and contains the key returned from
the previous call. Retry.

CA-7.V248 –CA-7.V253
CA-7.V248 s mmmm (dddd) RETTYP=NREC AND KEYAD VALUE IS LESS THAN SPACES FOR
CALLID xxxxxxxx
Explanation: An SVEXTGET call specifying RETTYP=NREC must specify KEYAD pointing to a
valid location containing the key from a previous call.
User Response: Verify that KEYAD points to a valid location and contains the key returned from
the previous call and retry.
CA-7.V249 s mmmm (dddd) RETTYP=NREC AND CORRESPONDING RETTYP NOT SETUP FOR
CALLID xxxxxxxx
Explanation: An SVEXTGET call specifying RETTYP=NREC must be preceded by an
SVEXTGET call specifying RETTYP=UNIQUE/FIRSTX/ NEXT/NODE.
User Response: Verify that previous SVEXTGET call will be performed and retry. If unresolved,
save console logs and listings and contact your installation's CA-7 specialist for assistance.
CA-7.V250 s mmmm (dddd) LOGIC ERROR IN GET, OBTAIN VRPL WHEN VRPL ALREADY
EXISTED FOR CALLID xxxxxxxx
Explanation: Although SVEXTGET call passed all checks for order of VSAM calls, a VRPL
already existed when the system expected to create one.
User Response: Check that all constraints regarding ordering of SVEXTGET and SVEXTPUT calls
have been complied with. If not, correct problem and retry. If unresolved, save console log and
listings and contact your installation's CA-7 specialist for assistance.
CA-7.V251 s mmmm (dddd) LOGIC ERROR IN GET, GET RECORD WITHOUT A VRPL FOR
CALLID xxxxxxxx
Explanation: Although SVEXTGET call passed all checks for order of VSAM calls, a VRPL was
expected to exist but did not.
CA-7.V252 s mmmm (dddd) LOGIC ERROR IN GET, RELEASE VRPL WHEN VRPL DOES NOT
EXIST FOR CALLID xxxxxxxx
Explanation: An SVEXTGET call attempted to release a VRPL which did not exist.
CA-7.V253 s mmmm (dddd) INVALID DATATYPE xxxx FOR SVEXTPUT TYPE=DELT/UNCT

Explanation: Either SVEXTPUT was called with an illegal DSTYPE, RECTYPE and KEYAD
combination or module SASSVY00 is invalid.
User Response: Check that DSTYPE, RECTYP and KEYAD are compatible. If not, correct
problem and retry. If unresolved, save console log and listings and contact your installation's CA-7

CA-7.V254 –CA-7.V264
CA-7.V254 s mmmm (dddd) VPCB FOR SVEXTGET NOT FOUND FOR CALLID xxxxxxxx
Explanation: An SVEXTGET call attempted to locate a VPCB which did not exist.
CA-7.V259 s mmmm (dddd) RECRD/BLKAD PARAMETER NOT ALLOWED FOR TYPE=DELT/UNCT

Explanation: SVEXTPUT TYPE=DELT/UNCT specified a RECRD or BLKAD parameter.
User Response: Remove RECRD or BLKAD parameter from SVEXTPUT call and retry.
CA-7.V260 s mmmm (dddd) CONTROL INTERVAL CONFLICT FOR CALLID = xxxxxxxx

Explanation: Same CALLID has requested update intent on two different DSTYPEs. This is legal,
but by chance, access to both requests require the same VSAM control interval. This can only occur
if data types with different DSTYPES are specified in the DBPARMS statements to be on the same
VSAM data set and will probably only occur if the physical data set is very small. This can only
occur if the governor module SASSV004 is not being used.
User Response: Reconfigure database so that data types with different DSTYPEs do not share the
same VSAM data set.
CA-7.V261 s mmmm (dddd) BACKUP CONNECTION MADE TO DSN = x...x

Explanation: Data set x...x has been opened for output and will be used as the destination for
database backup. Access type = BKUP is in effect. Normal message.
CA-7.V262 s mmmm (dddd) RELOAD CONNECTION MADE TO DSN = x...x

Explanation: Data set x...x has been opened for input and will be used as source for RELOAD
operation. Access type RELOAD is in effect. Normal message.
CA-7.V263 s mmmm (dddd) NORM CONNECTION MADE TO DSN = x...x

Explanation: The VSAM cluster x...x has been opened for input and output. Access type = NORM
is in effect. Informational message.
CA-7.V264 s mmmm (dddd) NORMIN CONNECTION MADE TO DSN = x...x

Explanation: The VSAM cluster x...x has been opened for input only. Access type = NORMIN is
in effect. Informational message.

CA-7.V265 –CA-7.V272
CA-7.V265 s mmmm (dddd) CONNECTION COMPLETED SUCCESSFULLY

Explanation: No error. Informational message indicating completion of SVCONN processing.
CA-7.V266 s mmmm (dddd) DISCONNECTED DSN = x...x

Explanation: No error. Informational message indicating close of data set DSN = x...x.
CA-7.V267 s mmmm (dddd) DISCONNECTION COMPLETED SUCCESSFULLY

Explanation: No error. Informational message indicating completion of SVDISCON processing.
CA-7.V268 s mmmm (dddd) RETTYP=NEXT REQUESTED AFTER EOD REACHED FOR CALLID
xxxxxxxx
Explanation: SVEXTGET attempted for next record key after reaching end of data.
CA-7.V269 s mmmm (dddd) RETTYP=NREC REQUESTED AFTER EOD REACHED FOR CALLID
xxxxxxxx
Explanation: SVEXTGET attempted for next logical record after reaching end of data.
CA-7.V270 s mmmm (dddd) RECORD FAILED KEY EDIT

Explanation: A record containing an invalid key was encountered. Keys are invalid if they have
noncatalogable characters or nodes in them. This message is followed by messages V271, V272 and
V273 which list the invalid key. The first four characters of the key identify the data type as defined
in the CA-7 Systems Programmer Guide.
User Response: The SASSBK00 program can be executed with an OPTION of RELOAD to
remove these errors from the database.
CA-7.V271 s mmmm (dddd) KEY=C'...'

Explanation: This identifies a key in character format. Refer also to messages V272 and V273.
CA-7.V272 s mmmm (dddd) KEY=Z'...'

Explanation: This identifies the zone portion of a key. Refer also to messages V271 and V273.

CA-7.V273 –CA-7.V276
CA-7.V273 s mmmm (dddd) KEY=N'...'

Explanation: This identifies the numeric portion of a key. Refer also to messages V271 and V272.
CA-7.V274 s mmmm (dddd) RECORD ABOVE INVALID, DROPPED FROM BACKUP

Explanation: The record identified in the immediately preceding messages is invalid as described in
those messages. It was not written to the backup.
CA-7.V275 s mmmm (dddd) BACKUP FORMAT INVALID (NO 'CNTL') - RECORD=x...x

Explanation: The file referenced as reload input did not match the format expected. It did not
begin with CNTL records created by a backup run. x...x is the content of the record read from the
input file in character format.
User Response: Use a file created by the backup option of the SASSBK00 program.
CA-7.V276 s mmmm (dddd) DUPLICATE KEY DETECTED, RECORD DROPPED BY RELOAD

Explanation: A duplicate key from a backup file was encountered during reload processing. It has
been dropped and not reloaded.

CA-7.V301 –CA-7.V306
CA-7.V301 s mmmm (dddd) NO HITS on ANY SPECIFIED AGENDA OPERATION

Explanation: An error occurred during analysis of the list of operations to be performed on the
parameters passed to the next program.
assistance.
CA-7.V302 s mmmm (dddd) SPECIFIED PARAMETER LIST DID NOT BEGIN WITH 'PLST'
Explanation: The header of the parameter list did not contain the ID 'PLST'.
assistance.
CA-7.V303 s mmmm (dddd) SPECIFIED AGENDA DID NOT BEGIN WITH 'AGEN'
Explanation: The header of the AGENDA list did not contain the ID 'AGEN'.
assistance.
CA-7.V304 s mmmm (dddd) S-CON IN PARAMETER LIST SPECIFIED INVALID BASE REGISTER
Explanation: The S-CON to be used to find other data to be passed to this program used an invalid
base register. This may be an internal logic error.
assistance.
CA-7.V305 s mmmm (dddd) END OF AGENDA NOT FOUND

Explanation: The AGENDA list used to define functions to be performed on the parameters passed
in the parameter list did not have the end of the list identified. This may be an internal logic error.
assistance.
CA-7.V306 s mmmm (dddd) END OF PARAMETER LIST NOT FOUND

Explanation: The parameter list passed to this program did not have the end of the list identified.
This may be an internal logic error.
assistance.

CA-7.V307 –CA-7.V313
CA-7.V307 s mmmm (dddd) VALDAT OPERATION DETECTED INVALID PARAMETER FOR

MODULE SASSV0xx
Explanation: Program SASSVZ00 detected an invalid parameter to be passed to the program
(module) shown. This may be an internal logic error.
assistance.
CA-7.V308 s mmmm (dddd) PARAMETER FOR xxxxxx OPERATION NOT FOUND

Explanation: Program SASSVZ00 attempted the specified operation on the parameter to be passed
to the next program and the parameter was not in the parameter list. This may be an internal logic
error.
assistance.
CA-7.V309 s mmmm (dddd) VPCB TO BE ASSIGNED ALREADY EXISTED

Explanation: A PCB was requested for this function but the PCB was already on the chain.
assistance.
CA-7.V310 s mmmm (dddd) RELEASE PCB REQUESTED, BUT NOT FOUND

Explanation: A PCB for this function was requested to be released but it was not on the chain.
assistance.
CA-7.V311 s mmmm (dddd) VPCB CHAIN INVALID

Explanation: A search down the PCB chain found an invalid address.
assistance.
CA-7.V312 s mmmm (dddd) FIND PCB REQUESTED, BUT NOT FOUND

Explanation: A request for a specific PCB (for example, to continue an operation) failed to find
that PCB.
assistance.
CA-7.V313 s mmmm (dddd) CHAIN REQUESTED, ALREADY CHAINED

Explanation: A request to chain together two control blocks found that the chain was already in
place.
assistance.

CA-7.V314 –CA-7.V320
CA-7.V314 s mmmm (dddd) UNCHAIN REQUESTED, NOT CHAINED

Explanation: A request to unchain two control blocks found that the chain did not exist.
assistance.
CA-7.V315 s mmmm (dddd) SPECIFIED CONTROL BLOCK AND SPECIFIED CHAIN NOT COMPAT-
IBLE
Explanation: A request to unchain two control blocks found that the control blocks were not the
same type. Program SASSVZ50 could not complete the chaining for the Functional module or the
Subroutine.
assistance.
CA-7.V317 s mmmm (dddd) ERROR CONVERTING S-CON

Explanation: During the resolution of the base register and/or offset of the S-type address constant,
program SASSVZ00 could not compute a valid address.
assistance.
CA-7.V318 s mmmm (dddd) INVALID SYMBOLIC VALUE FOR EXTERNAL PARAMETER

Explanation: A request from the calling program used a symbolic parameter which was unknown
to the VSAM system.
assistance.
CA-7.V319 s mmmm (dddd) INVALID NUMERIC VALUE FOR EXTERNAL PARAMETER

Explanation: A request from the calling program used a numeric value which did not correspond to
any known symbolic parameter in the VSAM system.
assistance.
CA-7.V320 s mmmm (dddd) DSTYPE, RECTYP, KEYAD COMBINATION NOT A LEGAL DATATYPE
Explanation: The VSAM record service request for a specified type of record could not be satis-
fied. The record is not defined to the VSAM database in the form requested.
assistance.

CA-7.V321 –CA-7.V326
CA-7.V321 s mmmm (dddd) PTR-TO-VAL PARAMETER FORMAT REQUIRED FOR PUTPARM

OPERATION
Explanation: The PUTPARM operation of the Parameter Reformatter subroutine requires the
Pointer-to-Value parameter format. This form of parameter was not found.
assistance.
CA-7.V322 s mmmm (dddd) INVALID PARAMETER VALUE IN AGENDA

Explanation: The result of the conversion of the parameters into codes/values was invalid (for
example, a DSTYPE value was supposed to be IDS but a different code was found).
assistance.
CA-7.V323 s mmmm (dddd) DSTYPE AND RECTYP MUST BE NON-ZERO

Explanation: An external macro call specified a DSTYPE or RECTYPE value of 0 when a specific
value was required. Either ALL was specified or the parameter pointed to a location containing
blanks or ALL.
User Response: Correct the external macro call to point to a location containing a specific value for
DSTYPE and RECTYP. Contact your installation's CA-7 specialist for assistance if unable to deter-
mine cause.
CA-7.V324 s mmmm (dddd) INVALID DSTYPE xxxx

Explanation: An illegal DSTYPE xxxx was specified.
User Response: Correct the external macro call to specify a legal DSTYPE.
CA-7.V325 s mmmm (dddd) VSAM KEYS NOT IN ASCENDING SEQUENCE

Explanation: A sequence error was detected either on the backup data set or during sequential
access of the VSAM database.
User Response: Correct sequence problem and retry or contact your installation's CA-7 specialist
for assistance, if needed.
CA-7.V326 s mmmm (dddd) xxxKEY NOT VALID FOR THIS SEQUENCE

Explanation: A sequence error was detected either on the backup data set or during sequential
access of the VSAM database. If xxx is NEW and RELOAD was being attempted, the backup data
set was not created by the BACKUP option of SASSBK00.
User Response: Correct sequence problem and retry or contact your installation's CA-7 specialist
for assistance, if needed.

CA-7.V327 –CA-7.V329
CA-7.V327 s mmmm (dddd) REQUIRED DATATYPE NOT PRESENT IN SEQUENCE

Explanation: Certain data types are required within the CA-7 DATABASE and must be present.
One of these data types was not present in sequence.
User Response: Correct sequence problem and retry.
CA-7.V328 s mmmm (dddd) ERROR nn FOR MESSAGE yyy s mmmm (dddd)

Explanation: Module SASSVZ70 was unable to process a caller's message. The module attempting
to issue the message is identified in the second mmmm field. The displacement of the SASSVZ70
linkage instructions within the caller is denoted by the second dddd field. The message number
causing the error is indicated by yyy.
assistance.
CA-7.V329 s mmmm (dddd) TERM NOT VALID WITH POST OPERATION

Explanation: The SVRESRC macro was called for POST operation and TERM was specified.
Internal problem.
User Response: Remove TERM parameter and retry. Contact your installation's CA-7 specialist for
assistance.

CA-7.V501 –CA-7.V509
CA-7.V501 s mmmm (dddd) HEADER OF SPECIFIED CELL POOL DAMAGED

Explanation: An Environment module has encountered an "internal" UCC7VSAM cell pool whose
header has been damaged by an overlay.
assistance.
CA-7.V502 s mmmm (dddd) CELL TO BE FREED WAS NOT ALLOCATED

Explanation: An Environment module has detected an attempt to free a cell in an "internal" cell
pool which is not found in the pool's chain of allocated cells.
assistance.
CA-7.V505 s mmmm (dddd) INVALID CELL POOL ID

Explanation: An Environment module cannot locate a cell pool containing the pool ID specified by
a caller of the module.
assistance.
CA-7.V506 s mmmm (dddd) CELL POOL WITH ALLOC CELL(S) CANNOT BE FREED
Explanation: Module SASSVx60 has detected an attempt to free an entire cell pool which contains
allocated cells.
assistance.
CA-7.V508 s mmmm (dddd) CELL POOL IS FULL AND NO SECONDARY EXTENT WAS SPECIFIED
Explanation: Module SASSVx70 failed in its attempt to allocate a cell from a cell pool whose
primary extent is completely filled. The pool was created with a secondary cell count of zero; there-
fore, no secondary pool extent will be acquired.
assistance.
CA-7.V509 s mmmm (dddd) CPOOL GET MACRO FAILED

Explanation: An attempt to get a cell from a cell pool through the CPOOL macro failed.
assistance.

CA-7.V511 –CA-7.V518
CA-7.V511 s mmmm (dddd) SGETM FAILED

Explanation: Internal storage allocation request failed.
User Response: Check storage pools by issuing /DISPLAY,Q=ALL. If available NSP space is low
according to the /DISPLAY,Q=ALL, increase region size and try again. If available NSP space
seems sufficient, the problem may be due to temporary load in system. Try the request again.
CA-7.V512 s mmmm (dddd) INVALID CSIZE PARAMETER

Explanation: Module SASSVx90 has detected an attempt to build a cell pool whose cells have a
negative or zero length, or a length exceeding 4088.
assistance.
CA-7.V513 s mmmm (dddd) INVALID PCELLCT PARAMETER

Explanation: Module SASSVx90 has detected an attempt to build a cell pool with a primary cell
count which is negative or zero.
assistance.
CA-7.V515 s mmmm (dddd) ECB ADDRESS NOT on FULLWORD BOUNDARY

Explanation: The Event Control Block address must be on a fullword boundary. This address or
the ECB may be in error.
assistance.
CA-7.V516 s mmmm (dddd) BIT 0 OF ECB NOT 1 OR BIT 1 NOT 0

Explanation: The Event Control Block contains unexpected or invalid indicators.
assistance.
CA-7.V517 s mmmm (dddd) BITS 0 AND 1 OF ECB NOT ZERO

Explanation: The Event Control Block contains unexpected or invalid indicators.
assistance.
CA-7.V518 s mmmm (dddd) PARAMETER ECB SPECIFIED AND COUNT NOT 1

Explanation: A process requiring an ECB was requested without proper setup.
assistance.

CA-7.V519 –CA-7.V527
CA-7.V519 s mmmm (dddd) COUNT GREATER THAN NUMBER OF ENTRIES IN ECBLIST

Explanation: The parameters for event processing are invalid.
assistance.
CA-7.V520 s mmmm (dddd) ECB ALLOCATED ABOVE 16MB LINE

Explanation: An ECB has an address which cannot be accessed by this system.
assistance.
CA-7.V527 s mmmm (dddd) REQUESTED SIZE OF CELL POOL EXTENT EXCEEDS 16 MBYTES
Explanation: Module SASSVx90 has detected an attempt to build a cell pool with an excessively
large primary or secondary extent.
assistance.

CA-7.V601 –CA-7.V605
CA-7.V601 s mmmm (dddd) RC=xx REAS=yy GETMAIN FAILED

Explanation: A request for processor storage could not be completed.
User Response: Increase region size. Save console listings and logs. Contact your installation's
CA-7.V602 s mmmm (dddd) RC=xx REAS=yy BLDL FAILED FOR xxxxxxxx

Explanation: A request for BLDL service for a member of a partitioned data set had a fatal error.
assistance.
CA-7.V603 s mmmm (dddd) RC=xx REAS=yy GENCB FOR xxx FAILED, DSN=x...x
Explanation: A request to generate VSAM control block xxx failed.
assistance.
CA-7.V604 s mmmm (dddd) RC=xx REAS=yy SHOWCB FOR xxx FAILED, DSN=x...x
Explanation: A request to show data from VSAM control block xxx failed.
assistance.
CA-7.V605 s mmmm (dddd) RC=xx REAS=yy VSAM OPEN FAILED, DSN=x...x

Explanation: VSAM open failed for data set x...x. If RC=8, REAS may be one of the following:
128 - DD statement is missing
136 - insufficient storage
148 - no record in catalog
168 - DSN not on volume specified in DBPARMS
180 - probably wrong DSN on STEPCAT
assistance.
128 - may need IDCAMS delete as first step
136 - increase storage
148 - may require STEPCAT
168 - check DBPARMS
180 - check STEPCAT

CA-7.V606 –CA-7.V611
CA-7.V606 s mmmm (dddd) RC=xx REAS=yy VSAM OPEN NON-TERMINAL ERROR, DSN=x...x
Explanation: VSAM open warning message.
User Response: Run an IDCAMS verify against data set x...x. Save console listings and logs.
CA-7.V607 s mmmm (dddd) RC=xx REAS=yy VSAM GET FAILED FOR CALLID tttttttt
Explanation: An error occurred while attempting to read a record. Where:
xx is the return code
yy is the reason code
tttttttt is the program, system function or user terminal issuing the request
Message V607 is followed by message CA-7.V636 which identifies the data set and the key of the
failing request. Refer to IBM OS/VS Virtual Storage Access Method (VSAM) Programmers Guide
(GC26-3838), for a description of the return (RC) and reason (REAS) codes.
User Response: Correct the error indicated by the return and reason codes; then retry the request if
necessary.
CA-7.V608 s mmmm (dddd) RC=xx REAS=yy VSAM CLOSE FAILED, DSN=x...x

Explanation: VSAM CLOSE failed for data set x...x.
assistance.
CA-7.V609 s mmmm (dddd) RC=xx REAS=yy MODCB FOR xxx FAILED, DSN=x...x
Explanation: VSAM modify control block function failed for control block xxx.
assistance.
CA-7.V610 s mmmm (dddd) IDCAMS ABENDED, [S/xxx | U/nnnn]

Explanation: DBPARMS IDCAMS control statements defined by user were submitted to IDCAMS
during connection and IDCAMS ABENDED with a System or User abend code of xxx or nnnn.
User Response: Check IDCAMS control statements submitted in DBPARMS data set by submitting
them to IDCAMS independent of CA-7. If they are handled by IDCAMS correctly then save listings
and logs and contact your installation's CA-7 specialist for assistance. If IDCAMS gives errors or
abends when executed directly, then correct the control statement or call IBM IDCAMS support.
CA-7.V611 s mmmm (dddd) IDCAMS COMPLETED, RC=nnnn

Explanation: IDCAMS was called and completed the requested action with the return code shown.
User Response: If the return code (RC=nnnn) is not zero, an error occurred. See preceding and
following messages for more information. Correct any errors in IDCAMS control statements in
DBPARMS statements and retry. Contact your installation's CA-7 specialist for assistance.

CA-7.V612 –CA-7.V614
CA-7.V612 s mmmm (dddd) idcams message text

Explanation: Normal message returned by interface with IDCAMS. "idcams message text" will be
supplied by IDCAMS.
User Response: None unless "idcams message text" indicates an error. Refer to IBM Access
Method Services Manual or IBM Messages and Codes Manual for your operating system for details
on the message returned.
CA-7.V613 s mmmm (dddd) RC=xx REAS=yy VSAM PUT FAILED FOR CALLID tttttttt
Explanation: An error occurred while attempting to write a record. Where:
xx is the return code
yy is the reason code
tttttttt is the program, system function or user terminal issuing the request
Message V613 is followed by message CA-7.V636 which identifies the data set and the key of the
failing request. Refer to IBM OS/VS Virtual Storage Access Method (VSAM) Programmers Guide
(GC26-3838), for a description of the return (RC) and reason (REAS) codes.
Note: If RC=0 and REAS=0, the key is invalid.
If RC=8 and REAS=8, a duplicate key is detected.
If RC=8 and REAS=28, the VSAM data set is out of space.
User Response: Correct the error indicated by the return and reason codes; then retry the request if
necessary.
CA-7.V614 s mmmm (dddd) OUT OF SPACE on VSAM PUT FOR DATA TYPE xxxx
Explanation: An output operation detected insufficient space. Where:
xxxx is the type of data being output
This message is:
nonrollable until CA-7 terminates.
issued once per data type.
followed by messages CA-7.V613 which identifies the caller and CA-7.V636 which identifies the
data set and the key of the failing request.
User Response: The following steps are recommended:
1. Bring down CA-7.
2. Back up the database.
3. Increase the space allocated to file noted in message CA-7.V636.
4. Reload the database.
Note: If IDCAMS is used for backup and reload, be sure you adjust the DBPARMS definition to
match what was done with IDCAMS.

CA-7.V615 –CA-7.V621
CA-7.V615 s mmmm (dddd) RC=xx REAS=yy VSAM ENDREQ FAILED, DSN=x...x

Explanation: Error occurred processing a VSAM ENDREQ macro request. This error could cause
incomplete output/update processing or later hang conditions related to exclusive control being
retained.
User Response: Correct error conditions indicated by preceding IBM messages, if any. If hang
condition occurs, CA-7 must be shut down and restarted with TYPE=WARM or TYPE=ERST. If
condition recurs, save console listings and logs. Then contact your installation's CA-7 specialist for
assistance.
CA-7.V616 s mmmm (dddd) RC=xx REAS=yy DELETE MACRO FAILED FOR zzzzzzzz
Explanation: Module name zzzzzzzz could not be deleted after being used.
User Response: None; unless accompanied by IBM messages indicating severe error. If error per-
sists, save console listings and logs. Then contact your installation's CA-7 specialist for assistance.
CA-7.V617 s mmmm (dddd) RC=xx REAS=yy ATTACH MACRO FAILED FOR IDCAMS
Explanation: Unable to attach program IDCAMS as required to perform DELETE and DEFINE
functions during database reload. Most likely cause of failure is insufficient memory. This message
should be preceded by IBM messages identifying the exact cause of failure.
User Response: Try increasing region size and refer to the IBM messages and documentation for
more details. If problem persists, save console listings and logs. Then contact your installation's
CA-7.V618 s mmmm (dddd) SGETM MACRO FAILED

Explanation: A CA-7 storage control service routine failed.
assistance.
CA-7.V619 s mmmm (dddd) SBLDL MACRO FAILED FOR xxxxxxxx

Explanation: A request for BLDL service for a load library failed.
User Response: Be sure member exists on CA-7's Load library. If so, save console listings and
logs. Contact your installation's CA-7 specialist for assistance.
CA-7.V620 s mmmm (dddd) OSDELETE MACRO FAILED FOR xxxxxxxx

Explanation: A request to delete a module from storage could not be completed.
assistance.
CA-7.V621 s mmmm (dddd) RC=xx REAS=yy FREEMAIN MACRO FAILED

Explanation: An attempt to free processor storage could not be completed.
assistance.

CA-7.V622 –CA-7.V628
CA-7.V622 s mmmm (dddd) RC=xx REAS=yy CPOOL MACRO FAILED (GET)

Explanation: Module SASSVx70 failed in its attempt to allocate a cell from a cell pool through the
CPOOL macro.
assistance.
CA-7.V623 s mmmm (dddd) RC=xx REAS=yy LOAD MACRO FAILED FOR xxxxxxxx
Explanation: An attempt to load a program into memory failed.
assistance.
CA-7.V624 s mmmm (dddd) ERASE RPL= NOT ACCEPTED FOR CALLID=xxxxxxxx

Explanation: VSAM macro ERASE RPL= did not work.
assistance.
CA-7.V625 s mmmm (dddd) RC=xx REAS=yy ERASE RPL= RETURNED VSAM ERROR FOR CALLID
= xxxxxxxx
Explanation: VSAM macro ERASE RPL= returned an error condition.
assistance.
CA-7.V626 s mmmm (dddd) RC=xx REAS=yy POINT RPL= RETURNED VSAM ERROR FOR CALLID
= xxxxxxxx
Explanation: VSAM macro POINT RPL= returned an error condition.
assistance.
CA-7.V627 s mmmm (dddd) PUT MACRO FAILED.

Explanation: The LRECL of the Backup data set was exceeded by the length of the segment con-
taining the DBPARMS (VCTL) data. The write failed.
User Response: Change the DCB parameter in the backup data set to specify a larger LRECL.
CA-7.V628 s mmmm (dddd) OPEN FAILED FOR BACKUP DD

Explanation: An attempt to open the BACKUP data set failed.
User Response: Ensure that the BACKUP DD statement is correct in the execution JCL. Verify
that the proper parameters were specified on the EXEC statement. Correct and resubmit.

CA-7.V629 –CA-7.V634
CA-7.V629 s mmmm (dddd) RDJFCB FAILED FOR BACKUP DD

Explanation: An attempt to read the JFCB failed.
assistance.
CA-7.V630 s mmmm (dddd) BACKUP DD CLOSE FAILED.

Explanation: A request to close the BACKUP data set failed.
assistance.
CA-7.V631 s mmmm (dddd) GET MACRO FAILED.

Explanation: An end-of-data condition was detected (possibly unexpected) on the BACKUP data
set.
User Response: Verify that the data set being used as input to the database load is the proper
BACKUP data set. Save console listings and logs. Contact your installation's CA-7 specialist for
assistance.
CA-7.V632 s mmmm (dddd) DYNUNALLOC FAILED - RC=xxxx,ERRCD=xxxx, INFOCD=xxxx,DSN=x...x

Explanation: Attempt to unallocate data set x...x failed. The RC, ERRCD and INFOCD codes are
those returned by the IBM dynamic allocation macro call and can be checked in the IBM documenta-
tion for that macro.
User Response: Research IBM documentation for codes produced in this message. Save console
listings and logs. Contact your installation's CA-7 specialist for assistance if unable to resolve
problem.
CA-7.V633 s mmmm (dddd) NON-TERMINAL DYNUNALLOC ERROR - INFOCD=xxxx,DSN=x...x

Explanation: Attempt to unallocate data set x...x failed. The INFOCD code is that returned by the
IBM dynamic allocation macro call and can be checked in the IBM documentation for that macro.
User Response: Research IBM documentation for codes produced in this message. Save console
listings and logs. Contact your installation's CA-7 specialist for assistance if unable to resolve
problem.
CA-7.V634 s mmmm (dddd) RDJFCB FAILED FOR DDN=xxxxxxxx

Explanation: Could not read JFCB for DD statement xxxxxxxx. The probable cause of the error is
a missing DD statement.
User Response: Check that the DD statement is correct. Add the DD statement and try again. If
ance.

CA-7.V635 –CA-7.V636
CA-7.V635 s mmmm (dddd) I/O ERROR ABEND on BACKUP DD - Text

Explanation: An abnormal condition occurred while processing the backup data set.
User Response: Change the I/O device or volume and resubmit. Save console listings and logs.
CA-7.V636 s mmmm (dddd) DSN=x...x, KEY=y...y

Explanation: This message follows error messages CA-7.V607, CA-7.V613, or CA-7.614.
Message CA-7.V636 identifies the data set and the key for the failing request.
Note: The key is always displayed as characters even though it may be in binary format on the
database. If message V613 preceded this message and indicated an invalid key condition, the
key is displayed in hexadecimal format.
User Response: Follow the action recommended for the message that precedes V636.

CA-7.V701 –CA-7.V706
CA-7.V701 s mmmm (dddd) RC=xx REAS=yy ERROR RETURNED FROM DATABASE GOVERNOR
SASSV004
Explanation: Database governor, SASSV004, encountered an error condition.
User Response: Look up explanation of crux message preceding this message on console log. Save
CA-7.V702 s mmmm (dddd) RC=xx REAS=yy ERROR RETURNED FROM CONTROL CARD GET
ROUTINE SASSV001
Explanation: Control Card Get module, SASSV001, encountered an error condition.
CA-7.V703 s mmmm (dddd) RC=xx REAS=yy ERROR RETURNED FROM CONTROL CARD PARSE
ROUTINE SASSV002
Explanation: Control Card Parse module, SASSV002, encountered an error condition.
CA-7.V704 s mmmm (dddd) RC=xx REAS=yy ERROR RETURNED FROM CONTROL BLOCK BUILD
ROUTINE SASSV003
Explanation: Control Block Build module, SASSV003, encountered an error condition.
CA-7.V705 s mmmm (dddd) RC=xx REAS=yy ERROR RETURNED FROM LOAD CONNECTION
MODULE SASSV021
Explanation: Load Connection module, SASSV021, encountered an error condition.
CA-7.V706 s mmmm (dddd) RC=xx REAS=yy ERROR RETURNED FROM RELOAD CONNECTION
MODULE SASSV022
Explanation: Reload Connection module, SASSV022, encountered an error condition.

CA-7.V707 –CA-7.V712
CA-7.V707 s mmmm (dddd) RC=xx REAS=yy ERROR RETURNED FROM NORMAL CONNECTION
MODULE SASSV024
Explanation: Normal Connection module, SASSV024, encountered an error condition.
CA-7.V708 s mmmm (dddd) RC=xx REAS=yy ERROR RETURNED FROM BACKUP CONNECTION
MODULE SASSV023
Explanation: Backup Connection module, SASSV023, encountered an error condition.
CA-7.V709 s mmmm (dddd) RC=xx REAS=yy ERROR RETURNED FROM SASSV021 ATTEMPTING
TO OPEN BACKUP DD FOR OUTPUT
Explanation: Load Connection module, SASSV021, encountered an error attempting to open the
BACKUP DD data set for output.
TO DISCONNECT ACCESS TYPE
Explanation: Disconnect module, SASSV040, encountered an error attempting to disconnect an
access type.
TO RECONNECT ACCESS TYPE
Explanation: Connect module, SASSV020, encountered an error attempting to reconnect an access
type.
CA-7.V712 s mmmm (dddd) RC=xx REAS=yy DISCONNECT FAILED FOR ACCESS TYPE xxxxxx
Explanation: Disconnect module, SASSV040, encountered an error disconnecting access type
xxxxxx.

CA-7.V713 –CA-7.V719
CA-7.V713 s mmmm (dddd) RC=xx REAS=yy RECONNECT FAILED FOR ACCESS TYPE xxxxxx
Explanation: Connect module, SASSV020, encountered an error reconnecting access type xxxxxx.
CA-7.V714 s mmmm (dddd) RC=xx REAS=yy SVBACKUP FAILED DURING TERMINATION

Explanation: Backup processing failed during termination. Error causing this failing is described
by preceding error messages.
User Response: Take corrective action described for error messages preceding this one. Any
backup file created may be incomplete and should not be used for reload if another is available.
CA-7.V715 s mmmm (dddd) RC=xx REAS=yy SVEXTPUT FAILED DURING TERMINATION

Explanation: Put processing was in progress when termination occurred. Additional error messages
should precede this on giving a further description of the problem.
assistance.
TO OPEN BACKUP DD FOR INPUT
Explanation: Backup Connect module, SASSV021, encountered an error attempting to open
BACKUP DD for input.
CA-7.V717 s mmmm (dddd) RC=xx REAS=yy ERROR RETURNED FROM SASSV081 DURING
SPECIAL LOAD
Explanation: Special Load module, SASSV081, encountered an error during special load process.
CA-7.V718 s mmmm (dddd) RC=xx REAS=yy ERROR RETURNED FROM SASSV028 IDCAMS INTER-
FACE MODULE
Explanation: IDCAMS Interface module, SASSV028, encountered an error submitting IDCAMS
statements from DBPARMS to IDCAMS for execution during connection process.
CA-7.V719 s mmmm (dddd) RC=xx REAS=yy CALLID xxxxxxxx SVEXTGET FAILED

Explanation: SVEXTGET call internal to VSAM failed.

CA-7.V720 –CA-7.V722
CA-7.V720 s mmmm (dddd) RC=xx REAS=yy ERROR RETURNED FROM SASSV029 VCTL PUT
MODULE
Explanation: Call of module SASSV029 returned an error condition.
CA-7.V721 s mmmm (dddd) RC=xx REAS=yy ERROR IN MODULE xxxxxxxx FOR KEYNAME
xxxxxxxx
Explanation: Call of Status module, SASSV09x, failed while processing KEYNAME xxxxxxxx.
CA-7.V722 s mmmm (dddd) RC=xx REAS=yy CALLID xxxxxxxx SVEXTPUT TYPE=DELT FAILED
Explanation: SVEXTPUT call internal to VSAM failed.

CA-7.V801 –CA-7.V806
CA-7.V801 s mmmm (dddd) RC=xx REAS=yy ERROR IN PARAMETER LIST OR AGENDA

DETECTED BY REFORMATTER SASSVZ00
Explanation: An error occurred in the Reformatter subroutine module SASSVZ00.
CA-7.V802 s mmmm (dddd) RC=xx REAS=yy SVCHAIN FAILED ATTEMPTING TO CHAIN xxxx
CONTROL BLOCK
Explanation: The control block chain for control block xxxx is incorrect.
CA-7.V803 s mmmm (dddd) RC=xx REAS=yy SVCHAIN FAILED ATTEMPTING TO UNCHAIN xxxx
CONTROL BLOCK
Explanation: The control block chain for control block xxxx is incorrect.
CA-7.V804 s mmmm (dddd) RC=xx REAS=yy SVAGNPCB FAILED on ASSIGN

Explanation: The Assign PCB module, SASSVZ10, was unable to assign a new VPCB control
block as requested.
CA-7.V805 s mmmm (dddd) RC=xx REAS=yy SVAGNPCB FAILED on FIND

Explanation: The Assign PCB module, SASSVZ10, was unable to find an existing VPCB control
block as requested.
CA-7.V806 s mmmm (dddd) RC=xx REAS=yy SVAGNPCB FAILED on RELEASE

Explanation: The Assign PCB module, SASSVZ10, was unable to release an existing VPCB
control block as requested, probably because the control block chain was invalid.

CA-7.V807 –CA-7.V813
CA-7.V807 s mmmm (dddd) RC=xx REAS=yy SVAGNRPL FAILED on ASSIGN

Explanation: The Assign RPL module, SASSVZ20, was unable to assign a new VRPL control
block as requested.
CA-7.V808 s mmmm (dddd) RC=xx REAS=yy SVAGNRPL FAILED on RELEASE

Explanation: The Assign RPL module, SASSVZ20, was unable to release an existing VRPL
control block as requested, probably because the control block chain was invalid.
CA-7.V809 s mmmm (dddd) RC=xx REAS=yy SVRESRC FAILED on WAIT

Explanation: The Wait and Post Resource module, SASSVZ30, was unable to wait on requested
resource.
CA-7.V810 s mmmm (dddd) RC=xx REAS=yy SVRESRC FAILED on POST

Explanation: The Wait and Post Resource module, SASSVZ30, was unable to post the requested
resource.
CA-7.V811 s mmmm (dddd) RC=xx REAS=yy TRANSFER INTERFACE (SASSVZ60) FAILED

Explanation: An External module was called using an external macro call, but an error occurred
during transfer to the module.
CA-7.V812 s mmmm (dddd) RC=xx REAS=yy SVGETTYP FAILED

Explanation: The Get Type subroutine, SASSVZ40, was unable to return the requested data type.
CA-7.V813 s mmmm (dddd) RC=xx REAS=yy SVGETLEN FAILED

Explanation: The Get Length subroutine, SASSVZ80, was unable to return the requested record
length.

CA-7.V814 –CA-7.V815
CA-7.V814 s mmmm (dddd) RC=xx REAS=yy SVCVPARM FAILED

Explanation: The Convert Parameter subroutine, SASSVZ90, was unable to convert the requested
parameters.
CA-7.V815 s mmmm (dddd) RC=xx REAS=yy SVSEQCHK FAILED

Explanation: The Sequence Check module, SASSVZA0, was unable to verify the correct key
sequence.

CA-7.V901 –CA-7.V906
CA-7.V901 s mmmm (dddd) RC=xx REAS=yy SVGETCPL FAILED OBTAINING xxxx CELL POOL
Explanation: The Get Cell Pool module, SASSVx90, was unable to allocate the requested cell pool.
CA-7.V902 s mmmm (dddd) RC=xx REAS=yy SVGETCEL FAILED OBTAINING A xxxx CONTROL
BLOCK
Explanation: The Get Cell module, SASSVx70, was unable to obtain the requested cell from an
existing cell pool.
CA-7.V903 s mmmm (dddd) RC=xx REAS=yy SVLOAD DID NOT FIND MODULE xxxxxxxx
Explanation: The Load module, SASSVxD0, was unable to find the requested module in any
accessible load library.
User Response: Check that the module named is in the library referenced by STEPLIB or JOBLIB
DD statements. Look up explanation of crux message preceding this message on console log. Save
CA-7.V904 s mmmm (dddd) RC=xx REAS=yy SVLOAD FAILED FOR MODULE xxxxxxxx
Explanation: The Load module, SASSVxD0, was unable to load the requested module.
User Response: Replace module named in load library and try again. Look up explanation of crux
message preceding this message on console log. Save console logs and listings. Contact your instal-
CA-7.V905 s mmmm (dddd) RC=xx REAS=yy SVGETM FAILED FOR xxxx CONTROL BLOCK
Explanation: The GETMAIN module, SASSVx80, was unable to acquire the requested storage for
control block xxxx.
CA-7.V906 s mmmm (dddd) RC=xx REAS=yy SVGETM FAILED GETTING WORKING STORAGE
Explanation: The GETMAIN module, SASSVx80, was unable to acquire the requested storage.

CA-7.V907 –CA-7.V913
CA-7.V907 s mmmm (dddd) RC=xx REAS=yy SVGETM FAILED ACQUIRING DBPARMS DCB
Explanation: The GETMAIN module, SASSVx80, was unable to acquire the requested storage for
a VDCB for the DBPARMS data set.
CA-7.V908 s mmmm (dddd) RC=xx REAS=yy SVFRECEL FAILURE FOR xxxx CONTROL BLOCK
Explanation: The Free Cell module, SASSVx40, was unable to return the requested control block
to the free pool.
CA-7.V909 s mmmm (dddd) RC=xx REAS=yy SVFRECPL FAILURE FOR xxxx CELL POOL
Explanation: The Free Cell Pool module, SASSVx40, was unable to delete the requested cell pool.
CA-7.V910 s mmmm (dddd) RC=xx REAS=yy SVPUTM FAILURE RELEASING xxxx CONTROL
BLOCK
Explanation: The FREEMAIN module, SASSVx50, was unable to free the requested storage.
CA-7.V911 s mmmm (dddd) RC=xx REAS=yy SVPUTM FAILURE RELEASING WORKING STORAGE
Explanation: The FREEMAIN module, SASSVx50, was unable to free the requested storage.
CA-7.V912 s mmmm (dddd) RC=xx REAS=yy SVPUTM FAILURE RELEASING DBPARMS DCB
Explanation: The FREEMAIN module, SASSVx50, was unable to free the requested storage for
the DBPARMS VDCB.
CA-7.V913 s mmmm (dddd) RC=xx REAS=yy SVPOST MACRO FAILURE

Explanation: The Post module, SASSVxA0, was unable to post the requested ECB.

CA-7.V914 –CA-7.V918
CA-7.V914 s mmmm (dddd) RC=xx REAS=yy SVWAIT MACRO FAILURE

Explanation: The Wait module, SASSVxC0, was unable to set up the requested ECB.
CA-7.V915 s mmmm (dddd) RC=xx REAS=yy SVDELETE FAILED FOR MODULE xxxxxxxxx
Explanation: The Delete module, SASSVxE0, was unable to delete the requested module.
CA-7.V916 s mmmm (dddd) RC=xx REAS=yy SVLINK FAILED FOR MODULE xxxxxxxxx
Explanation: The Link module, SASSVxF0, was unable to link to the requested module.
CA-7.V917 s mmmm (dddd) RC=xx REAS=yy SVGETM FAILED

Explanation: The GETMAIN module, SASSVx80, was unable to allocate the requested storage.
CA-7.V918 s mmmm (dddd) RC=xx REAS=yy SVPUTM MACRO FAILED

Explanation: The SVPUTM macro returned an error condition.

3.14 CA-7.W Messages
CA-7.WTO –CA-7.WTO
3.14 CA-7.W Messages
CA-7.WTO xxxxx..........xxxxx
Explanation: This message appears at the OS console when a CA-7 terminal operator issues the
/WTO command. The xxxxx..........xxxxx is the message text entered by the operator issuing the
/WTO.

3.15 CA-7.X Messages
CA-7.XRAC-01 –CA-7.XRAC-06
CA-7.XRAC-01 INVALID PARAMETER LIST - @RSRCPL

Explanation: The VRM VSAM processing module SASSXRAC received an internal request for
service using an invalid parameter list. This message is associated with a user 100 abend.
CA-7.XRAC-02 VRM INTERNAL ERROR - INVALID REQUEST

Explanation: The VRM VSAM processing module SASSXRAC received an unidentified request
type. This message is associated with a user 101 abend.
CA-7.XRAC-03 VSAM RECD ERROR R15 = xx FDBK = xxxxxxxx FUNC = xx

Explanation: An I/O error has occurred in the VRM VSAM processing module SASSXRAC. Reg-
ister 15 is the return code and the FDBK field indicates the feedback code as a result of the I/O. If
R15=08, a duplicate record has been found.
User Response: Save the console messages associated with this message and contact your installa-
tion's CA-7 specialist for assistance.
CA-7.XRAC-04 VSAM SHOWCB ERROR

Explanation: An internal VSAM macro error has occurred in the VSAM processing module
SASSXRAC. This message is associated with a user 101 abend.
CA-7.XRAC-05 VSAM MODCB ERROR

CA-7.XRAC-06 RECORD KEY = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation: An error has occurred in the VRM VSAM processing module SASSXRAC. An
invalid record or record key was found.

CA-7.XRAC-07 –CA-7.XTM0
CA-7.XRAC-07 VSAM MACRO PROCESSING ERROR

CA-7.XSEC xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Explanation: This message is issued as part of tracing/debugging the CA-7 interface with external
security packages. The message is only activated when working with Computer Associates Technical
Support. The message text is variable.
User Response: This message is informational. No action is required.
CA-7.XTM0 SASSXTM0 initialization in progress

Explanation: Initialization of CCI terminal interface system environment has begun.
CA-7.XTM0 SASSXTM0 initialization complete

Explanation: This message reports successful initialization of CCI terminal interface system envi-
ronment.
CA-7.XTM0 CCI Interface initialized.

Explanation: The CCI INIT request was successful. CA-7 is ready to accept CCI terminal
requests.
CA-7.XTM0 CCI Interface initialization failed.

Explanation: The CCI INIT request failed. CA-7 cannot accept CCI terminal requests.
User Response: An additional message specifying the reason for the CCI INIT failure will be
issued. The most likely reason is that CCI is not active. If this is the case, start CCI. When CCI is
initialized then issue the following CA-7 command: /OPEN,GROUP=name-of-CCI-group. Refer to
the discussion of the /OPEN command in the CA-7 Commands Guide for additional information.
CA-7.XTM0 RECEIVE error; Data dropped.

Explanation: CA-7 could not allocate a buffer for an incoming CCI terminal request.

CA-7.XTM0 –CA-7.X003
CA-7.XTM0 Session started (nnnnnnnn) xx-xx

Explanation: A CCI terminal session started. nnnnnnnn is the CA-7 SCT name of the terminal
handling the request. The CCI node name of the session partner is reported at xx-xx.
CA-7.XTM0 Session ended (nnnnnnnn) xx-xx

Explanation: A CCI terminal session ended. nnnnnnnn is the CA-7 SCT name of the terminal
handling the request. The CCI node name of the session partner is reported at xx-xx.
CA-7.XTM0 Exceeded max num of RPLs.

Explanation: An internal limit on the number of concurrent CCI terminal session requests was
exceeded. One or more CCI terminal transactions may have failed.
User Response: If the condition persists, contact your installation's CA-7 technical specialist.
CA-7.XTM0 FFFF note: mm-mm (aabbccdd) nn-nn

Explanation: An exception was detected for a CCI function request. FFFF is the name of the CCI
function that was attempted such as 'SEND' or 'RECV'. mm-mm is the message in the CCI feedback
area. The FDBVRC codes from the CCI feedback area are reported at aabbccdd. nn-nn is the CCI
node name of the session partner.
CA-7.X001 NO xxxxxxxx VALUE SUPPLIED.

Explanation: The value supplied for a program parameter keyword is invalid. Default values are
supplied for these parameters in CA7CLIST.
User Response: Correct the parameter values and execute CA7CLIST again.
CA-7.X002 (xx yyyy) xxxxxxxx FAILED, R15=nnnnnnnn.

Explanation: The named Dialog Manager (xxxxxxxx) macro failed. The value in R15 is the return
code from the macro. Refer to appropriate IBM ISPF documentation.
User Response: Save ISPF log and list output for this session and contact Computer Associates
Technical Support.
CA-7.X003 INVALID ENTRY CODE, R1=nnnnnnnn.

User Response: The error may be transient. Attempt to reexecute CA7CLIST. If the error persists,
save all ISPF log and list output. Also collect any dumps that may have been produced and contact

CA-7.X004 –CA-7.X008
CA-7.X004 INVALID RETURN CODE, R15=nnnnnnnn.

User Response: The error may be transient. Attempt to reexecute CA7CLIST. If the error persists,
save all ISPF log and list output. Also collect any dumps that may have been produced and contact
CA-7.X005 (xx yyyy) SESSION TERMINATED DUE TO ERROR

Explanation: The CA-7 terminal session under ISPF has been terminated. The reasons for termi-
nation may be explained by previous error messages.
User Response: Refer to the previous error messages for information on the reason for termination.
Take the indicated action and attempt to execute CA7CLIST again. If the error persists, contact your
CA-7.X006 xxxxxxxx GENCB FAILED, R15 = nnnnnnnn

Explanation: A GENCB macro failed for the VTAM control block named. R15 contains the return
code from the GENCB. Refer to IBM ACF/VTAM Programming (SC27-0449).
User Response: Specific information on the reason for the failure will be found in the aforemen-
tioned publication. A common reason for a GENCB failure is an insufficient region size for the
ISPF session. If the error persists, contact your installation's CA-7 specialist for assistance.
CA-7.X007 SYNTAX ERROR PARSING ACB NAME FOR SESSION

Explanation: An internal error was encountered trying to parse the ACB name provided on the
SESSAPL keyword in CA7CLIST.
User Response: Make sure that the value supplied for the SESSAPL parameter matches the value
on the SLUACB keyword on the UCC7VTAM statement in the CA-7 initialization file. Also make
sure that the values conform to the naming conventions outlined in the CA-7 Systems Programmer
Guide. If the error persists, contact your installation's CA-7 specialist for assistance.
CA-7.X008 CONNECT ACB UNAVAILABLE OVER 10 SECONDS

Explanation: The ACB needed for CA-7/TSO-ISPF session establishment could not be OPENed
during the time period allowed. The ACB used for session establishment is the ACB name that ends
with 0000. Refer to the CA-7 Systems Programmer Guide for further information on the definition of
the ACBs.
Note: This message could be produced during a period of high activity when there are many users
attempting to establish CA-7 terminal sessions under TSO-ISPF.
User Response: If the message was produced during a period of high activity, simply wait a few
minutes and re-execute the CLIST. If an error condition seems possible then attempt to activate the
VTAM application where the ACBs are defined by issuing a
v net,id=APPL,act
APPL in this example should be replaced by the name of the appropriate VTAM application. If this
fails, review the installation steps outlined in the CA-7 Systems Programmer Guide pertaining to the

CA-7.X009 –CA-7.X014
definition of the VTAM ACBs for possible errors. If the error persists, contact your installation's
CA-7.X009 xxxxxxxx ACB OPEN FAILED, ACBOFLGS = nnnnnnnn

Explanation: A VTAM OPEN macro failed for the ACB named by xxxxxxxx. The ACBOFLGS
codes may provide information as to the reason for the failure. Refer to IBM ACF/VTAM Program-
ming (SC27-0449).
User Response: If the ACB named is the 0000 ACB, then this message will probably be accompa-
nied by a CA-7.X008 message. In that event, refer to the recommended action for that message.
Otherwise refer to the aforementioned IBM publication for information on the reasons why VTAM
failed the OPEN request. If the error persists, contact your installation's CA-7 specialist for assist-
ance.
CA-7.X010 RTNCD = xxxxxxxx, FDBK2 = yyyyyyyy

Explanation: This is an informational message which may be preceded by a message indicating an
RPL based VTAM macro failure. For information on the meaning of these codes, refer to IBM
ACF/VTAM Programming (SC27-0449).
User Response: None. This message is informational. Refer to action recommended for the
message specific to the macro failure.
CA-7.X011 SESSION USER LIMIT REACHED, TRY AGAIN LATER

Explanation: All of the VTAM ACBs defined for use with the CA-7/TSO-ISPF interface are cur-
rently in use by other ISPF sessions.
User Response: Wait a few minutes and try the interface again. If the problem persists, consider
increasing the number of VTAM ACBs.
CA-7.X012 xxxxxxxx TRANSLATION FAILED, R0 = nnnnnnnn

Explanation: An error occurred during the attempt to evaluate an address. xxxxxxxx is the internal
function name and R0 contains the return code from the function routine.
User Response: Note the sequence of events that resulted in the failure. Collect all ISPF log and
list output from the time frame when the failure occurred. Contact your installation's CA-7 specialist
for assistance.
CA-7.X013 SCREEN TRANSLATION ERROR

Explanation: An error occurred during the attempt to build ISPF output for a CA-7 screen. This
message may be accompanied by others which will give a reason for the error.
User Response: Refer to the action(s) recommended for any accompanying messages.
CA-7.X014 ERROR DETECTED IN EDITOR

Explanation: An error occurred during an ISPF edit session for CA-7. This message may be
accompanied by others which will give a reason for the error.
User Response: Refer to the action(s) recommended for any accompanying messages.

CA-7.X015 –CA-7.X020
CA-7.X015 xxxxxxxx FAILED, R0 = nnnnnnnn

Explanation: The VTAM macro named at xxxxxxxx failed. Refer to IBM ACF/VTAM Program-
ming (SC27-0449) for further information.
CA-7.X016 INVALID WRITE CONTROL CHARACTER - xx

Explanation: An invalid 3270 write control character was received from CA-7. xx is the hex value
of the character.
User Response: The problem may be transient. Reexecute the interface. If the problem persists,
CA-7.X017 INVALID 3270 DATASTREAM ORDER - xx

Explanation: An invalid 3270 datastream order character was received from CA-7. xx is the hex
value of the character.
User Response: The problem may be transient. Reexecute the interface. If the problem persists,
CA-7.X018 INVALID EDIT HEADER, EDIT SESSION TERMINATED

Explanation: Internal information needed to maintain Editor protocols between CA-7 and
TSO-ISPF was missing or invalid.
User Response: If the L2ISPFxx modules are accessed from a library other than the CA-7 pro-
duction load library, then make sure that all L2ISPFxx modules are running at the same maintenance
level as the modules that are executing in the CA-7 address space. If the problem persists, contact
CA-7.X019 UNABLE TO OPEN EDITOR WORK FILE

Explanation: The work file that was dynamically allocated for use in a CA-7/TSO-ISPF edit
session could not be opened.
User Response: This message may be accompanied by other messages, for example, CA-7.X026. If
so, refer to the action recommended for those messages. If this message is produced without accom-
panying messages, then simply reexecute the CA-7 CLIST.
CA-7.X020 UNABLE TO COMPLETE VTAM CONNECTION WITH CA-7

Explanation: A VTAM REQSESS macro was issued to establish a session with CA-7; however, no
response from CA-7 was received.
User Response: This message may be ignored if CA-7 was terminating during the attempt to
connect to CA-7 from ISPF. Reexecute the interface. If the condition persists, contact Computer
Associates Technical Support.

CA-7.X021 –CA-7.X025
CA-7.X021 NSEXIT CLEANUP REQUEST - LINK IS DOWN

Explanation: The VTAM link with CA-7 is no longer active. There are several possible explana-
tions for this condition. For example, a VTAM command may have been issued to inactivate the
application, or CA-7 may be down, or a /CLOSE may have been issued to close the CA-7 VTAM
ACB.
User Response: No CA-7 terminal sessions will be available under ISPF until the VTAM link is
reestablished. Determine the cause of the outage and reexecute the interface. If the error persists,
CA-7.X022 NSPE RU RECEIVED - SESSION TERMINATED

Explanation: The NSEXIT exit was entered for a Network Services Procedure Error. Refer to IBM
User Response: Reexecute the interface. If the error persists and no VTAM problem is indicated,
CA-7.X023 LOSTERM EXIT ENTERED - SESSION TERMINATED

Explanation: This exit may be entered under certain session outage conditions. Refer to IBM
CA-7.X024 TPEND EXIT ENTERED - SESSION TERMINATED

Explanation: The TPEND exit was entered for this ACB. This exit may be entered in response to
a VTAM HALT command, or may be entered if VTAM terminates.
User Response: No CA-7 session under ISPF will be available until the VTAM link between CA-7
and the ISPF sessions is reestablished. If the error persists and no problem can be detected in
VTAM, then contact your installation's CA-7 specialist.
CA-7.X025 INVALID RESPONSE FROM CA-7 TO REQUEST FOR SLU ACBNAME

Explanation: An ISPF session requested the assignment of an ACB name for use in establishing a
VTAM link. CA-7 returned a response not recognized by the requestor.
User Response: Review the following for possible error conditions:
1. Determine that the VTAM link is being attempted for the correct copy of CA-7. Make sure that
the ACB defined for that copy of CA-7 is named on the CA7APL keyword in CA7CLIST.
2. The value for the SESSAPL keyword in CA7CLIST must match the VTAM ACB definitions.
Correct any parameter values that may be in error, then reexecute the interface. If the error persists,

CA-7.X026 –CA-7.X033
CA-7.X026 SVC 99 ERROR, R15 = xxxxxxxx, R0 = yyyyyyyy

Explanation: An attempt to allocate an editor work file failed. The R15 and R0 values should
indicate the nature of the problem. Refer to IBM MVS/SPL Job Management (GC28-1303) for infor-
mation on the return codes from dynamic allocation.
User Response: Correct the problem that prevented the successful dynamic allocation and re-
execute the interface.
CA-7.X027 CA-7 SCRGET DISP=FIRST FAILED. EDIT TERMINATED

CA-7.X028 CA-7 SCRGET DISP=NEXTE FAILED, EDIT TERMINATED

CA-7.X029 ***WARNING*** LINK ENDED DURING EDIT. DATA NOT SAVED

Explanation: The VTAM link with CA-7 was terminated during the edit session. The CA-7 ter-
minal session ended and any data being edited was lost.
User Response: If the link ended because the TIMLIM value for the terminal expired, consider
increasing this value. If other messages indicate that the link ended due to error, consult the recom-
mendations accompanying those messages.
CA-7.X030 OPEN/CLOSE SUBTASK ENDED. TCBCMP= xxsssuuu

Explanation: The subtask that was created to handle OPEN and CLOSE requests for the VTAM
ACBs used for the CA-7 terminal session ended. A nonzero TCBCMP indicates an abnormal termi-
nation. In such a case, sss is the system abend code and uuu is the user abend code.
User Response: Collect any dumps that may have been produced and contact Computer Associates
Technical Support.
CA-7.X032 ERROR RETURN FROM SASSPCEJ. EDIT TERMINATED

Explanation: An error was encountered during the attempt to load the ISPF editor.
CA-7.X033 INVALID FOOTER CODE. EDIT TERMINATED

Explanation: Invalid data was received from CA-7 during the attempt to load the ISPF editor.

CA-7.X034 –CA-7.X040
CA-7.X034 CA-7 TERMINAL SESSION ENDED

Explanation: This message may be issued if one of the following conditions is true:
1. The VLOGOFF PF key was pressed.
2. CA-7 detected no terminal activity for a time period in excess of the value specified on the
TERM statement keyword, TIMLIM. CA-7 will not recognize any terminal activity during an
ISPF edit session.
3. A /CLOSE,T= command was issued for this terminal.
CA-7.X035 L2ISPF20 NSEXIT SHOWCB FAILED

Explanation: A SHOWCB macro failed in the VTAM NSEXIT that was established for the ACB
used in the VTAM link with CA-7.
User Response: This message is informational but may be helpful in debugging situations.
CA-7.X036 L2ISPF20 NSEXIT UNKNOWN RU TYPE

Explanation: An unknown request unit was received by the VTAM NSEXIT used in the link with
CA-7.
User Response: This message is informational but may be helpful in debugging situations.
CA-7.X037 L2ISPF20 NSEXIT CLEANUP REQUEST

Explanation: A CLEANUP request was received by the VTAM NSEXIT used in the link with
CA-7.
CA-7.X038 L2ISPF20 NSEXIT NSPE RU RECEIVED

Explanation: A Network Services Procedure Error RU was received.
CA-7.X039 L2ISPF20 LOSTERM EXIT ENTERED

Explanation: The LOSTERM exit associated with the ACB for this terminal session was entered.
The CA-7 terminal session will be terminated.
CA-7.X040 L2ISPF20 TPEND EXIT ENTERED

Explanation: The TPEND exit associated with the ACB for this terminal session was entered. The
CA-7 terminal session will be terminated. This exit may be entered in the event of a VTAM outage
or in response to certain VTAM operator commands. This exit will be entered in response to a
VARY NET,INACT for the application and will also be entered in response to a VTAM HALT
command.

CA-7.X041 –CA-7.X046
CA-7.X041 CHECK FAILED on xxxxxxxx

Explanation: A nonzero return was received for a CHECK macro issued in a VTAM RESP RPL
exit. xxxxxxxx indicates the macro that was issued using this RPL. This may result in session
termination.
contact Computer Associates Technical Support. If no other CA-7.Xnnn messages are produced at
the same time, this message can be ignored.
CA-7.X042 ERROR OCCURRED IN SCIP EXIT

Explanation: The VTAM SCIP exit for this terminal session's ACB encountered an error.
CA-7.X043 VTAM LOGICAL ERROR EXIT ENTERED

Explanation: The VTAM LERAD exit for this terminal session's ACB was entered.
CA-7.X044 VTAM SYNAD EXIT ENTERED

Explanation: The VTAM SYNAD exit for this terminal session's ACB was entered.
CA-7.X045 ERROR IN VGET FROM APPLICATION POOL

Explanation: An attempt to read a variable from the CA7 application profile failed.
CA-7.X046 VTAM APPL FOR CA-7 NOT ACTIVE OR NOT ACCESSIBLE

Explanation: The VTAM APPL named on the CA7APL parameter in the CA7CLIST is not cur-
rently active or is not accessible in this domain.
User Response: Make sure that the copy of CA-7 associated with the VTAM APPL named in the
CA7APL parameter is active and that the VTAM ACB is open. Make sure that this APPL is acces-
sible in the domain where the ISPF session is running.
CA-7.X046 LAST 4 CHARACTERS OF SESSAPL MUST BE NUMERIC

Explanation: An internal error was encountered on the SASSAPL keyword in CA7CLIST.
User Response: Make sure that the last four characters supplied for the SESSAPL parameter are
numeric.

CA-7.X047 –CA-7.X048
CA-7.X047 CA-7 UNRESPONSIVE FOR 16 SECONDS, SESSION TERMINATED

Explanation: The ISPF interface was invoked and timed out before the CA-7 logon screen could be
returned.
User Response: Check for performance problems on the system where the ISPF session was
invoked.
CA-7.X048 UNABLE TO DISPLAY PANEL CA7@PRIM, RC=xx

Explanation: An error occurred during an ISPF edit session for CA-7. The xx is the ISPF return
code from IBM.
User Response: Execute CA7CLIST again, if the error persists contact your installation's CA-7

Chapter 4. CA-7.000 - CA-7.999
This chapter contains the CA-7.000 through CA-7.999 messages.
Chapter 4. CA-7.000 - CA-7.999 4-1

4.1 CA-7.000 Through CA-7.094 Messages
CA-7.000 –CA-7.004
CA-7.000 Vx.y (gggg) EMERGENCY RESTART COMPLETE AT hh:mm:ss ON yy.ddd

Explanation: An emergency restart (ERST) of CA-7 has been successfully completed. Vx.y (gggg)
indicates the product version (x), installed release (y) and genlevel (gggg) of CA-7. Issued by
SASSCHDE.
CA-7.001 Vx.y (gggg) COLD START COMPLETE [AND QUEUES RELOADED] [FROM AN INCOM-
PLETE FILE] AT hh:mm:ss ON yy.ddd.
Explanation: COLD start initialization has been successfully completed. Vx.y (gggg) indicates the
product version (x), installed release (y) and genlevel (gggg) of CA-7. The first bracketed ([ ])
message appears whenever a MOVQ start is requested. The second bracketed ([ ]) message appears
if the file used to reload the CA-7 queues was not complete and corresponds to message INQB-02.
Issued by SASSINWC.
CA-7.002 Vx.y (gggg) RESTART COMPLETE AT hh:mm:ss ON yy.ddd

Explanation: Restart initialization of CA-7 has been successfully completed. Vx.y (gggg) indicates
the product version (x), installed release (y) and genlevel (gggg) of CA-7. Issued by SASSINWC.
CA-7.003 Vx.y (gggg) PHASE [(I)|(II)] SHUTDOWN IN PROGRESS AT hh:mm:ss ON yy.ddd

ALL SYSTEM FUNCTIONS COMPLETE
PHASE [(I)|(II)] SHUTDOWN COMPLETE AT hh:mm:ss
Explanation: Phase I or Phase II of the CA-7 shutdown process has been completed. Vx.y (gggg)
SASSCHDS or SASSSCM2.
CA-7.004 READY TO ACCEPT MODIFY (taskname)

Explanation: This WTO is issued when the MVS console is defined as a terminal to CA-7 and
opened. Replies must be entered in top line or batch command format and sequence. /LOGON must
be entered before commands are accepted and /LOGOFF should be entered when finished. The job
or started task executing CA-7 is identified by taskname. Issued by SASSRCSL.
User Response: Enter appropriate command to use console as terminal to CA-7, using OS
MODIFY commands.

CA-7.005 –CA-7.009
CA-7.005 Vx.y (gggg) OPERATOR IS LOGGED OFF

Explanation: This is the usual message that appears when an operator logs off a CA-7 terminal.
Vx.y (gggg) indicates the product version (x), installed release (y) and genlevel (gggg) of CA-7.
Issued by SASSCHDS.
CA-7.006 Vx.y (gggg) REQUESTED MODULE xxxxxxxx NOT FOUND

Explanation: The CA-7 module shown could not be found. Vx.y (gggg) indicates the product
version (x), installed release (y) and genlevel (gggg) of CA-7. Issued by SASSCHDS, SASSCHED,
SASSEMGR or SASSHALT.
User Response: Make sure the module is in the CA-7 Load library. Also check to ensure that there
is an APPLCTN statement in the CA-7 initialization file or in the SASSPROG module for the
module.
CA-7.007 Vx.y (gggg) REQUESTED FORMAT BLOCK xxxxxxxx NOT FOUND

Explanation: A format block was not found to process a message or screen. Vx.y (gggg) indicates
the product version (x), installed release (y) and genlevel (gggg) of CA-7. Issued by SASSCHDM or
SASSCHDS.
User Response: Check module SASSFMTH or SASSFMTA for the requested format block. Make
sure you have FMTBLK statements in the initialization file for SASSFMTH and SASSFMTA. Issue
a /RELINK,FM= command specifying the format block in the message if a module has already been
defined.
CA-7.008 Vx.y (gggg) INPUT FORMAT ERROR FOR APPLICATION xxxxxxxx FORMAT BLOCK
SFMxxxxx TERMINAL xxxxxxx
Explanation: An error occurred formatting the input to the application indicated. Vx.y (gggg) indi-
cates the product version (x), installed release (y) and genlevel (gggg) of CA-7. Issued by
SASSCHDS.
User Response: If problem recurs, do a /RELINK for both application and format block named. If
problem still continues, reassemble and link edit the format block, then do the /RELINK again. If all
else fails, contact your installation's CA-7 specialist for assistance.
Note: A condition code of 2 on a format block assembly is normal.
CA-7.009 Vx.y (gggg) OUTPUT FORMAT ERROR FOR APPLICATION xxxxxxxx FORMAT BLOCK
SFMxxxxx TERMINAL xxxxxxx
Explanation: An error occurred formatting the output from the application indicated. Vx.y (gggg)
SASSCHDM.
User Response: Same as for CA-7.008.
Chapter 4. CA-7.000 - CA-7.999 4-3

CA-7.010 –CA-7.013
CA-7.010 Vx.y (gggg) UNIDENTIFIED COMMAND, PLEASE RE-ENTER

Explanation: Either the command could not be identified as a valid CA-7 command or a shutdown
is in progress. Vx.y (gggg) indicates the product version (x), installed release (y) and genlevel
(gggg) of CA-7. Issued by SASSCHDS.
User Response: If a shutdown is not in progress, check for command spelling errors, correct and
retry. If a shutdown is in progress, no commands may be entered. If the /SHUTDOWN was entered
at your terminal, a /LOGOFF cannot be entered for your terminal.
CA-7.011 APPLICATION DWELL TIME EXCEEDED

Explanation: A value was supplied for the APDWELL parameter of the RESIDENT statement and
command processing has exceeded that time value. For a batch-only run, this value defaults to one
(1) hour.
User Response: Remove or increase the APDWELL value. Alternately, specify values on the
command effected to limit its processing and reduce the time required.
CA-7.012 REQUEST FOR rrrrrrrr ACCESS DENIED BY ssssssss.

---text---
Explanation: Access has been denied to the resource identified by rrrrrrrr. Resources can be:
CA-7
COMMAND
FUNCTION
DATA SET
JOB
Access was denied by security identified by ssssssss. Sources can be:
CA-7
SECURITY
USER EXIT
Further description of the access denial is provided by "text" which can be a message from a user
exit, feedback from external security or a clarification message from CA-7.
User Response: Review the message to determine which type of resource is involved and which
security is controlling access. To allow access, the security identified must be changed.
CA-7.013 Vx.y (gggg) OPERATOR IS NOT AUTHORIZED FOR APPLICATION xxxxxxxx

Explanation: Vx.y (gggg) indicates the product version (x), installed release (y) and genlevel
(gggg) of CA-7. If the application identified begins with SASS, the operator is not authorized for
any function of that application. In all other cases, the operator is authorized for the major applica-
tion but does not have a security level necessary to perform the identified function. Issued by
SASSCHDS.
User Response: Change the security module to give the operator access to that application or to a
higher security level. The actual security level required for a given function may be modified by
changing module SASSTRAN. The changes necessary should be evident. If no changes are made,
the operator will not be allowed to perform the attempted function. CA-7 must be reinitialized for
the changes to take effect.

CA-7.014 –CA-7.019
CA-7.014 Vx.y (gggg) UNRECOVERED ERROR ON TERM xxxxxxxx

Explanation: An unrecoverable I/O error occurred on the terminal indicated by xxxxxxxx. Vx.y
(gggg) indicates the product version (x), installed release (y) and genlevel (gggg) of CA-7. Issued by
SASSCHDM, SASSEMGR.
User Response: Check the hardware for problems. If terminals have been added or changed,
review the parameters coded in the initialization file for correctness. If BTAM, be sure that the
initialization file statements correspond to the DD statements in the CA-7 execution JCL. If the
hardware checks out and the error persists, contact your installation's CA-7 specialist for assistance.
If the terminal is a batch terminal, run SASSBEND and try again.
CA-7.015 Vx.y (gggg) UNKNOWN ERROR ON TERM xxxxxxxx

Explanation: Vx.y (gggg) indicates the product version (x), installed release (y) and genlevel
(gggg) of CA-7. An error has been detected by CA-7 on the terminal with ID number xxxxxxxx.
Issued by SASSCHDS.
User Response: If the terminal is a printer, a /START command may have been issued to it. Use
the /OPEN,T= command instead; otherwise, contact your installation's CA-7 specialist for assistance.
CA-7.016 TRAP PROGRAM FAILED

Explanation: The CA-7 trap facility has failed because of a program problem. Issued by
SASSTRA0.
CA-7.017 TWO ABENDS AND NO FIXES

Explanation: While already processing an abend, the trap facility encountered a second abend.
CA-7.016 message (issued by SASSTRA0) and a U0001 abend dump will accompany this message.
Issued by SASSTRA0.
CA-7.018 Vx.y (gggg) OS STOP INVALID, USE /SHUTDOWN

Explanation: An OS STOP command was entered at a console. However, CA-7 security requires
that an operator logon to the console terminal and issue a /SHUTDOWN.
User Response: If a shut down of CA-7 is desired, log on to the console with a valid ID then issue
the /SHUTDOWN command.
CA-7.019 Vx.y (gggg) CA7 CANCELED

Explanation: Normal informational response to /DUMP or /DMP1 command.
Chapter 4. CA-7.000 - CA-7.999 4-5

CA-7.020 –CA-7.022
CA-7.020 Vx.y (gggg) DISK QUEUE TABLE I/O ERROR

Explanation: An I/O error occurred while purging Disk Queue Table tracks or more than 256 pages
were built for an online terminal. Vx.y (gggg) indicates the product version (x), installed release (y)
and genlevel (gggg) of CA-7. Issued by SASSCHDM, SASSEMGR, SASSCHDS.
User Response: If a command could produce 256 or more pages of output, try requesting less
information or try input through a batch terminal.
CA-7.021 Vx.y (gggg) SPACE HAS BEEN EXCEEDED IN THE DISK QUEUE TABLE
Explanation: The Disk Queue Table is not large enough for the volume of messages and number of
terminals in use. This could be caused by a message loop. Vx.y (gggg) indicates the product
version (x), installed release (y) and genlevel (gggg) of CA-7. Issued by SASSCHDM.
User Response: Try increasing size of Disk Queue Table. The DMPQ/MOVQ process must be
done to increase the size of any queue. Contact your installation's CA-7 specialist for assistance, if
needed.
CA-7.022 Vx.y (gggg) LOGON FORMAT INCORRECT AT tttttttt

Explanation: An attempt was made to log on to a CA-7 terminal (tttttttt) and the format of the
logon was incorrect. Vx.y (gggg) indicates the product version (x), installed release (y) and genlevel
User Response: Correct the logon format and reissue the command. Also, if the CA-7 initialization
file SECURITY statement specifies APPL checking, this may have caused the failure.
CA-7.022 Vx.y (gggg) LOGON REJECTED BY CA-7 AT tttttttt

Explanation: An attempt was made to log on to CA-7 terminal tttttttt with a USERID that is not
defined to CA-7's internal security module. Vx.y (gggg) indicates the product version (x), installed
release (y) and genlevel (gggg) of CA-7.
User Response: Correct the logon USERID and reissue the command.
CA-7.022 Vx.y (gggg) LOGON REJECTED BY SECURITY AT tttttttt

Explanation: An attempt was made to log on to CA-7 terminal tttttttt with a USERID that has been
rejected by the external security package. Vx.y (gggg) indicates the product version (x), installed
User Response: The error message from the security package explains the reason for error. Take
the appropriate action based on the message.
CA-7.022 Vx.y (gggg) LOGON REJECTED BY USER EXIT AT tttttttt

Explanation: An attempt was made to log on to CA-7 terminal tttttttt with a USERID that was
rejected by your site's user exit (SASSXXLX). Vx.y (gggg) indicates the product version (x),
installed release (y) and genlevel (gggg) of CA-7.
User Response: Correct the logon and reissue the command.

CA-7.022 –CA-7.027
CA-7.022 Vx.y (gggg) LOGON REJECTED BY UNKNOWN AT tttttttt

Explanation: An attempt was made to log on to CA-7 terminal tttttttt with a USERID that is not
defined to CA-7's internal security module. Vx.y (gggg) indicates the product version (x), installed
User Response: Correct the logon USERID and reissue the command.
CA-7.023 Vx.y (gggg) OPERATOR IS LOGGED ON TO TERMINAL xxxxxxx AT hh:mm:ss ON yy.ddd

Explanation: This is the normal message that appears when an operator logs on to a CA-7 terminal.
xxxxxxx is the terminal name; hhmmss and yyddd indicate current time and date, respectively.
Issued by SASSCHDS.
CA-7.024 Vx.y (gggg) OPERATOR AT TERMINAL (tttttttt) LOGGED OFF AT

hh:mm:ss ON yy.ddd
Explanation: The /LOGOFF command was issued from the terminal tttttttt at date and time shown.
CA-7.025 Vx.y (gggg) APPLICATION MODULE xxxxxxxx REQUIREMENTS EXCEED POOL yyyy
Explanation: Application module xxxxxxxx attempted to perform some request that exceeded avail-
able space in storage pool yyyy. Vx.y (gggg) indicates the product version (x), installed release (y)
and genlevel (gggg) of CA-7. Issued by SASSCHED.
User Response: The probable cause of the error is setting JDPL or DSPL equal to zero (0) in the
initialization file RESIDENT statement.
1. Correct JDPL or DSPL entries for the type of database being used. See the CA-7 Systems Pro-
grammer Guide.
2. Check size of pool yyyy to assure sufficient resource for future requests.
CA-7.026 Vx.y (gggg) CA-7 SHUTDOWN COMPLETE

Explanation: The shutdown is complete and CA-7 has terminated. Vx.y (gggg) indicates the
product version (x), installed release (y) and genlevel (gggg) of CA-7. Issued by SASSHALT.
CA-7.027 Vx.y (gggg) FACILITY NOT AVAILABLE IN YOUR SYSTEM

Explanation: An attempt has been made to use a CA-7/RPT facility not available in your system.
Issued by SASSCHED, SASSCHDS.
Chapter 4. CA-7.000 - CA-7.999 4-7

CA-7.028 –CA-7.032
CA-7.028 Vx.y (gggg) UNIDENTIFIED TRANSACTION, PLEASE RE-ENTER

Explanation: The command entered was rejected because it could not be located in the system
tables. Vx.y (gggg) indicates the product version (x), installed release (y) and genlevel (gggg) of
CA-7. Issued by SASSCHDS.
User Response: Check for spelling error and retry.
CA-7.029 Vx.y (gggg) EXPECTED CONTINUATION CARD NOT RECEIVED BEFORE EOD TRANS-
ACTION IGNORED
Explanation: A batch execution of CA-7 encountered end-of-data when it expected continuation of
transaction input. Vx.y (gggg) indicates the product version (x), installed release (y) and genlevel
User Response: Check the format of the transaction for an incorrect continuation indicator. Correct
the error and retry.
CA-7.030 Vx.y (gggg) MESSAGE NUMBER 030 NOT DEFINED

Explanation: This message occurs when using the batch terminal interface and /LOGON is fol-
lowed by blanks instead of an operator ID. Vx.y (gggg) indicates the product version (x), installed
release (y) and genlevel (gggg) of CA-7. Issued by SASSEMGR.
User Response: The proper format of the logon is /LOGON opid. Correct and resubmit the batch
terminal interface.
CA-7.031 Vx.y (gggg) REQUEST COMPLETE

Explanation: Normal informational response to /RESET or /SWAP.
CA-7.032 Vx.y (gggg) APPLICATION MODULE xxxxxxxx REQUIREMENTS EXCEED POOL pppp
POOL SIZE ssssss SIZE REQUESTED rrrrrrrr SESSION CANCELED
Explanation: The application program identified by xxxxxxxx has requested more memory than is
defined to storage pool identified by pppp. The pool size is noted by ssssss. The requested memory
is noted by rrrrrrrr. The value of pppp can be one of the following:
RES Resident pool
JOB Job pool
DSN Dataset pool
APL Application pool
MSG Message pool
NSP Nonspecific pool
User Response: The size of the APL, JOB, and DSN pools are set using keywords on the RESI-
DENT statement in the initialization file. Try increasing the values on that statement. The size of
the other pools is determined by the region size where CA-7 is executing. Try increasing the region
or decreasing the values for CWORK or CABND.

CA-7.033 –CA-7.038
CA-7.033 Vx.y (gggg) APPLICATION MODULE xxxxxxxx RELEASED STORAGE FROM WRONG
POOL - SESSION CANCELED
Explanation: The program identified by xxxxxxxx violated storage controls by attempting to release
storage from one pool which belonged to a different pool.
User Response: Save all console output. Swap logs so the current log will be dumped. After log
dump is complete, request report HR02 for the terminal where the message was issued. About one
hour prior to when the message appeared should be adequate. Contact Computer Associates Tech-
nical Support and have the above information available.
CA-7.034 Vx.y (gggg) APPLICATION xxxxxxxx REQUESTED ssssss BYTES FROM POOL pppp POOL
SIZE ssssss SIZE REMAINING rrrrrrrr SESSION CANCELED
Explanation: The application program identified by xxxxxxxx has requested more memory than is
available in storage pool identified by pppp. The pool size is noted by ssssss. The requested
memory is noted by rrrrrrrr. The value of pppp can be one of the following:
RES Resident pool
JOB Job pool
DSN Dataset pool
APL Application pool
MSG Message pool
NSP Nonspecific pool
User Response: The size of the APL, JOB, and DSN pools are set using keywords on the RESI-
DENT statement in the initialization file. Try increasing the values on that statement. The size of
the other pools is determined by the region size where CA-7 is executing. Try increasing the region
or decreasing the values for CWORK or CABND.
CA-7.035 Vx.y (gggg) PAGES PURGED. TERMINAL HAS xxxx MESSAGES WAITING (TO
RETRIEVE NEXT MESSAGE ENTER /NXTMSG)
Explanation: The is the response to either the /NXTMSG or the /PURGPG command. When
/NXTMSG is issued and there are no messages waiting for the terminal, this message is returned
with xxxx set to NO. When /PURGPG is issued, this message is returned with xxxx set to the
number of messages waiting. If xxxx is not zero, the second line of the message appears.
CA-7.038 Vx.y (gggg) INVALID REQUEST FOR PAGE SERVICE

Explanation: A /PAGE command was issued from a batch terminal or when no pages existed.
Issued by SASSCHDS.
User Response: Delete /PAGE command from the batch terminal input.
Chapter 4. CA-7.000 - CA-7.999 4-9

CA-7.039 –CA-7.052
CA-7.039 Vx.y (gggg) MSG LOST-TERMINAL NOT AVAILABLE

Explanation: The terminal could not be found in CA-7's internal table of terminals and logical
terminals. Vx.y (gggg) indicates the product version (x), installed release (y) and genlevel (gggg) of
CA-7. Issued by SASSEMGR, SASSCHDM.
CA-7.042 Vx.y (gggg) SECURITY REQUIRES LOGON FOR THIS COMMAND.

Explanation: This message occurs when a command is used that requires security checking but the
terminal has not been logged on. Vx.y (gggg) indicates the product version (x), installed release (y)
and genlevel (gggg) of CA-7. Issued by SASSCHDS.
User Response: Issue the /LOGON command and then reenter the command.
CA-7.043 Vx.y (gggg) YOU ARE NOT AUTHORIZED FOR THIS COMMAND
Explanation: This message occurs when a command is issued that fails the operator's security
check. Vx.y (gggg) indicates the product version (x), installed release (y) and genlevel (gggg) of
CA-7. Issued by SASSCHDS.
User Response: None. If the operator should be able to issue this command, change either the
operator's security level or the security level for the command in the SASSDSCR module.
CA-7.050 CA-7 NOW LOGGING ON ALOGx

Explanation: This message indicates the current Log data set to which CA-7 is writing records of
its activity. If the primary log is being used, x will be 1; if the secondary log, then x will be 2.
Issued by SASSINWC.
CA-7.051 ENTER DUMP FOR ALOGl AND ALOG2

or
ENTER DUMP FOR ALOGx
Explanation: A job must be submitted to dump the primary Log data set (if x=1), the secondary
Log data set (if x=2), or both logs if so indicated. Issued by SASSINWC.
User Response: Submit the appropriate job to dump the specified Log data set. This must be done
before CA-7 can be initialized.
CA-7.052 LOG CONTROL FLAG IS INVALID

Explanation: An invalid log control flag was found in the Checkpoint record during initialization.
Issued by SASSINWC.

CA-7.053 –CA-7.060
CA-7.053 MASTER TERMINAL NOT DEFINED

Explanation: A Master Terminal has not been defined for CA-7.
User Response: Issued by SASSCHDE. Ensure that the CA-7 initialization file contains one
TERM statement with CONS=MASTR specified to designate a Master Terminal.
CA-7.060 xxxxx FAILED FOR BSAM DATASET, DDN=xxxxxxxxx (R15=nnnnnnnn)

Explanation: CA-7 is unable to open the Browse data set. R15 shows code as:
08 - DSN not found in catalog
0C - Data set not found on volume
10 - Invalid DSORG
14 - Invalid DCB attribute
18 - DASD volume not available
1C - Member not found
20 - Write I/O error
24 - Data set is password protected
28 - Data set is busy
2C - Member already exists
30 - New name already exists
34 - Store error
38 - Data set out of space
3C - Data set is date protected
40 - Invalid parameter data
54 - Data set is user-id protected or user-exit SASSXX07 denied access
58 - Invalid DDNAME specified
Issued by SASSDLOG.
User Response: If unable to resolve the problem, contact your installation's CA-7 specialist for
assistance.
Chapter 4. CA-7.000 - CA-7.999 4-11

CA-7.093 –CA-7.094
CA-7.093 CA-7/VTAM LOGON FOR xxxxxxx REJECTED. VTAM ID NOT DEFINED.

Explanation: A VTAM terminal with the node name xxxxxxx attempted log on to CA-7. The
logon was rejected because the VTAM terminal is not defined to CA-7 with a TERM statement in
the initialization file. Issued by SASSLGON. Another possibility is that all the CA-7 virtual termi-
nals (as defined in the initialization file - VTM#nnn) are already in use.
User Response: If the terminal should not have access to CA-7, no action is required. If the user
wishes to access CA-7 from the terminal, a TERM statement must be added to the initialization file
with other changes needed to add a terminal. If the problem is because all the virtual terminals are
in use, wait a few minutes until someone else logs off or increase the number of virtual terminals.
CA-7.094 TERMINAL BUSY/STOPPED.

Explanation: The terminal used to input the command is busy or has been stopped. Issued by
SASSW32V, SASSW32R.
User Response: The terminal can be started by issuing a /START,T= termname from another
authorized terminal.

CA-7.100 –CA-7.106
CA-7.100 LOAD DATA FOR JOB xxxxxxxx CREATED. (JOB FLUSHED)

Explanation: This is an information message issued by the CA-7 load step. The step is added to a
user's JCL stream to cause the addition or replacement of job records in the CA-7 database. The
message indicates that the records necessary to load a job into the database have been created. When
JOB FLUSHED appears in the message, a load-only run without actual execution of the user's job is
being performed. Following the execution of the CA-7 load step, all remaining JCL will be flushed.
Issued by SASSJJCL.
CA-7.101 COULD NOT READ JOB CONTROL TABLE - U0101

Explanation: CA-7's load step could not read the Job Control Table (JCT). Issued by SASSJJCL.
CA-7.102 PROGRAM SASSJJCL NOT FIRST STEP OF JOB - U0102

Explanation: The CA-7 load step was not inserted as the first step of the job being loaded. Issued
by SASSJJCL.
CA-7.103 COULD NOT WRITE JOB CONTROL TABLE - U0103

Explanation: The CA-7 load step was unable to write to the Job Control Table (JCT). Issued by
SASSJJCL.
CA-7.104 PROGRAM SASSJJCL ONLY STEP IN JOB - U0104

Explanation: The job being loaded contains only the CA-7 load step. Issued by SASSJJCL.
User Response: Review the JCL for the job; the job must have at least one step. Reload the job.
CA-7.105 EXPECTED STEP CONTROL TABLE NOT READ - U0105

Explanation: The CA-7 load step expected to read a Step Control Table (SCT) entry; the data
received was not an SCT. Issued by SASSJJCL.
CA-7.106 EXPECTED SIOT/JFCB RECORDS NOT READ - U0106

Explanation: The CA-7 load step expected to read a Step I/O Table (SIOT) entry or a Job File
Control Block (JFCB) entry; the data received was not a SIOT or JFCB. Issued by SASSJJCL.
Chapter 4. CA-7.000 - CA-7.999 4-13

CA-7.107 –CA-7.113
CA-7.107 UNKNOWN OPERATING SYSTEM - U0107

Explanation: The CA-7 load step was unable to determine the operating system in which it was
executing. Issued by SASSJJQM.
CA-7.108 QUEUE RECORD ID FROM JOB QUEUE NOT CORRECT - U0108

Explanation: The CA-7 load step encountered an incorrect queue record ID in the Job queue.
Issued by SASSJJQM.
User Response: Check the SVC number in ICMDSECT on CA-7's loadlib; otherwise, contact your
CA-7.109 BAD RETURN FROM JOB QUEUE MANAGER - U0109

Explanation: The CA-7 load step has detected an unknown return code from the Job Queue
Manager. Issued by SASSJJQM.
CA-7.110 BAD USER SVC - U0110

Explanation: The CA-7 load step has determined that the CA-7 SVC is bad. Issued by
SASSJJQM.
User Response: Check the SVC number in ICMDSECT on CA-7's loadlib; if the SVC number
appears to be correct, make sure ICOM is set to collect SMF data. Otherwise, contact your installa-
CA-7.111 UC07 MISMATCHED IN ICMDSECT

Explanation: The CA-7 load step has determined that the CA-7 module ICMDSECT is not correct
for the subsystem name.
User Response: Check the STEPLIB DD in the load step to be sure that there is not a conflict in
the version. For example, this message can be produced if a 2.9 load PROC is used for a 3.0 or
higher CA-7. Otherwise, contact CA-7 support for assistance.
CA-7.112 nnnnnnnn LOAD RECORDS CHANGED BY SASSXX12

Explanation: If the user exit SASSXX12 is used, it can modify records. This message indicates
how may records were changed.
CA-7.113 nnnnnnnn LOAD RECORDS DELETED BY SASSXX12

Explanation: If the user exit SASSXX12 is used, it can delete records. This message indicates how
may records were deleted.

CA-7.150 –CA-7.151
CA-7.150 CA-7 VRM ACTIVE RESOURCE RECORDS UNLOADED

Explanation: The VRM active resource records were successfully unloaded during DMPQ (Dump
queue) shutdown processing. Issued by SASINQD.
CA-7.151 NO ACTIVE RESOURCE RECORDS FOUND

Explanation: CA-7 found no VRM active resource records on the VRM database component to be
unloaded during DMPQ (Dump queue) shutdown processing.
Chapter 4. CA-7.000 - CA-7.999 4-15

CA-7.200 –CA-7.204
CA-7.200 BOTH LOG FILES ARE FULL,

DUMP LOG FILES,
THEN REPLY "LOGP" IF PRIMARY WAS DUMPED,
OR REPLY "LOGS" IF SECONDARY WAS DUMPED,
AWAITING REPLY: LOGP, LOGS, OR CANCEL
Explanation: Both Log data sets are full; at least one log must be dumped before CA-7 execution
can continue. This message could appear during initialization if CA-7 could not determine which log
file was last in use at shutdown. Issued by SASSBTMG.
User Response: The jobs to dump the Log data sets have been submitted (either manually or auto-
matically by CA-7) but have not run. Take required action to cause execution of one of the dump
jobs by submitting outside of CA-7. When the job has successfully completed, reply to the out-
standing WTOR with either LOGP (primary) or LOGS (secondary) to indicate which log was
dumped.
CA-7.201 CANCEL REQUESTED

Explanation: An operator replied CANCEL to the outstanding CA-7.200 WTOR. Issued by
SASSBTMG.
User Response: Dump the Log data sets and then restart CA-7.
CA-7.202 ERROR ON LOG DATA SET ERROR CODE = x

Explanation: There are two values for x:
1. If x=1, the audit flags indicate that both log files are active.
2. If x=2, the open for the Log data set failed.
Issued by SASSBTMG.
User Response: Obtain the dump and then contact your installation's CA-7 specialist for assistance.
CA-7.203 OUT OF SPACE IN INDEX DATA SET

Explanation: The CA-7 IDS is out of space. Issued by SASSBTMG, SASSVSM1, SASSSCM2.
User Response: Allocate more space to the data set after shutting down CA-7. Copy the data set
and reinitialize CA-7.
CA-7.204 OUT OF SPACE IN xxxxxx DATA SET DIRECTORY

Explanation: There is not enough space available in the data set directory indicated by xxxxxx.
This message only pertains to PDS data sets. Issued by SASSBTMG, SASSSCM2.
User Response: Shut down CA-7, allocate more directory blocks, copy the data set and reactivate
CA-7.

CA-7.205 –CA-7.253
CA-7.205 OUT OF SPACE IN xxxxxx DATA SET

Explanation: There is not enough available space in the Job or Dataset data set. Data set is indi-
cated by xxxxxx. Issued by SASSCHDB, SASSSCM2.
User Response: Allocate more space to the data set after shutting down CA-7. Copy the data set
and reinitialize CA-7.
CA-7.206 PDS DATA BASE MUST BE SINGLE EXTENT, PLEASE REALLOCATE

Explanation: An error condition occurred while trying to output to a PDS database file. The error
indicated a multiple extent PDS which is not supported by CA-7. The file in question must be
reallocated as a single extent PDS to avoid unpredictable errors. Issued by SASSDBMG.
User Response: Shut down CA-7, back up the database, reallocate the PDS files in the database as
single extent files, then reload the database and restart CA-7. An alternative to reallocating is to
convert to the ALLVSAM form of the database.
CA-7.250 I/O ERROR ON BATCH TERMINAL

Explanation: An I/O error has been detected on the batch input terminal. It is treated like an
end-of-file condition. Issued by SASSIBAT.
User Response: Verify that the program that put data into the input data set closed the file before
batch terminal processing began.
If the problem persists, contact your installation's CA-7 specialist for assistance.
CA-7.252 BATCH TERMINAL #n IN USE. REPLY WAIT, CANCEL OR RESET

Explanation: The control record in the Communications data set indicates the specified batch ter-
minal is already in use. The value of n denotes the batch terminal number being used. Issued by
SASSBSTR.
User Response: The status of the batch terminal can be determined by entering
/DISPLAY,T=batchtermname. Reply should be as follows:
WAIT if the batch terminal is truly busy.
CANCEL if the status display does not indicate that the terminal is BUSY (SKIP status) and
analyze the situation further.
RESET if the status display indicates the terminal is stopped. CA-7 will reset the status indicated
in the Communications data set allowing the job to run.
CA-7.253 ALL AVAILABLE BATCH TERMINALS IN USE. REPLY WAIT OR CANCEL

Explanation: This message is issued when the Dynamic BTI Management option is in use; but, all
terminals in the batch terminal pool have been busy for 5 minutes. Issued by SASSBSTR.
User Response: Reply WAIT to instruct the program to keep looking until a batch terminal
becomes available. Reply CANCEL to terminate the batch BTI job so that it can be resubmitted at a
later time.
Chapter 4. CA-7.000 - CA-7.999 4-17

CA-7.254 –CA-7.258
CA-7.254 IS CA-7 ACTIVE?? REPLY YES OR NO

Explanation: The control record in the Communications data set indicates that CA-7 is active but
60 seconds have elapsed and the batch terminal has not been started. Issued by SASSBSTR.
User Response: If CA-7 is active, reply YES; if not, reply NO. Check the JCL for the batch
terminal interface to make sure the correct Communications data set is being used.
CA-7.255 WAITING FOR CA-7 TO COME UP. REPLY 'END' TO TERMINATE BTI JOB.
Explanation: The CA-7 Communciations data set indicates the CA-7 address space is not active.
This WTOR allows you the opportunity to terminate the BTI job rather than having it wait for CA-7
to become active.
User Response: Take no action if you want the BTI job to wait for CA-7 to come up. When CA-7
becomes active, this WTOR is automatically deleted and the BTI job proceeds with normal proc-
essing. If CA-7 will be down for some time and you do not want the BTI job to wait for it, reply
END. The BTI step will terminate with a return code of 8.
CA-7.256 SYSPRINT DD STATEMENT MISSING

Explanation: The SYSPRINT DD was omitted from the batch terminal interface JCL. Issued by
SASSBSTR.
User Response: Correct the JCL and resubmit the job.
CA-7.256 UCC7OUT DD STATEMENT MISSING

Explanation: UCC7OUT DD was omitted and the file could not be opened. Issued by
SASSBTSO.
User Response: Correct and retry.
CA-7.257 BTERM FLAG RESET, CA-7 SHUTDOWN ASSUMED

Explanation: The control record in the Communications data set indicates the batch terminal is no
longer in use. CA-7 might have been shutdown immediately following batch terminal processing.
Or, a bad run of SASSBEND to clear the BTERM flags might have occurred. The shutdown case is
assumed. Issued by SASSBSTR.
User Response: If CA-7 has not been shut down, check to see if PGM SASSBEND or SASSICLR
was executed during this time frame. These programs should execute only if CA-7 or SASSBSTR
terminate abnormally (COND=ONLY).
CA-7.258 *WARNING* ERROR RECOVERY UNABLE TO FREE BTI TERMINAL #n *WARNING*

Explanation: This message is issued when the error recovery routines are unable to reset the usage
flags for a batch terminal in the CA-7 Communications data set. The specified batch terminal will
remain unavailable until these flags are reset. Issued by SASSBSTR.
User Response: Execute SASSBEND to reset the flags for the specified batch terminal.

CA-7.260 –CA-7.260
CA-7.260 I/O ERROR ON BATCH TERMINAL

Explanation: Batch terminal processing detected an I/O error on a batch data set. Issued by
SASSIBAT.
User Response: Check DCB specifications for batch data sets and retry. The BUFSIZE on the
LINE statement in the initialization file should be the same as the BLKSIZE of the batch input data
set.
Chapter 4. CA-7.000 - CA-7.999 4-19

4.4 CA-7.3XXX Through CA-7.378 Messages
CA-7.3XXX –CA-7.301
CA-7.3XXX CURRENT NUMBER OF SMF RECORDS IN CSA = XXXXX

Explanation: This message is produced if the number of chained SMF records in CSA is a multiple
of 1024.
CA-7.3XXX STOPPING CAPTURE OF SMF 0E RECORDS

Explanation: This message is produced for the first occurrence of an input data set SMF record
(type 14) when the number of chained SMF records is at least 1024. This message is a WTO which
is highlighted and non-scrollable.
User Response: In general, no action is required. The statistics reflected by GRAPHJ,ID=450 will
not include the SMF records that are skipped. In addition, the effects will be similar to using
PERFORM=1 in the INIT file.
CA-7.3XXX STOPPING CAPTURE OF SMF 0F RECORDS

Explanation: This message is produced for the first occurrence of an output data set SMF record
(type 15) when the number of chained SMF records is at least 4096. This message is a WTO which
is highlighted and non-scrollable.
User Response: Skipping the SMF output data set records can affect all data set postings and data
set triggering . Also, the statistics reflected by GRAPHJ,ID=460 will not include the SMF records
that are skipped.
CA-7.3XXX RESUMING CAPTURE OF SMF DATA

Explanation: This message is produced for the first occurrence of either an SMF type 14 or 15
record when the chained record count is reduced to 200 and the capturing of SMF type 14 or 15
records has been previously suspended.
CA-7.301 SASSEMGR - ERROR xxx OCCURRED DURING PROCESSING ERROR yyy

Explanation: Another error occurred while trying to process an error. The current session will be
canceled. Issued by SASSEMGR.
User Response: If xxx=007 and yyy=001, the FMTBLK statement may be missing in the initializa-
tion file or more than 32767 logical terminals may have been defined.
If xxx=009 and yyy=001, more than one terminal has been defined with the same name.
Enter the next command; contact your installation's CA-7 specialist for assistance.

CA-7.302 –CA-7.306
CA-7.302 SASSEMGR - SCT WITHOUT A TSRLIST

Explanation: No TSRLIST could be found for the SCT issuing the error message. Issued by
SASSEMGR.
CA-7.302 SASSSCM2 - SASSHALT SCT NOT FOUND

Explanation: A search of the SCTs for SASSHALT has failed. Issued by SASSSCM2.
CA-7.303 SASSSCM2 - SCT TO BE LOGGED OFF NOT FOUND

Explanation: The SCT for the terminal to be logged off cannot be found. Probable control block
error. Issued by SASSSCM2.
CA-7.303 SASSEMGR - SYSTEM SCT ERROR

Explanation: An invalid error message request has been received from a system SCT. Issued by
SASSEMGR.
User Response: Check the RESIDENT statement in the initialization file. Be sure that the param-
eter APGPL is coded and that it is large enough. The value should probably not be less than
204800. Check the LOGP and LOGS data sets. They must be allocated with at least 2 tracks.
Contact Computer Associates Technical Support for assistance.
CA-7.305 SCRATCH QUEUE SPACE EXHAUSTED - U0305

Explanation: All the Scratch queue (UCC7SCRQ) tracks have been allocated and there are no addi-
tional tracks available. Issued by SASSDAIO.
User Response: ERST start CA-7 (TYPE=ERST). All messages and scratch areas will be purged.
Note the Action for message CA-7.306, which should eliminate the abend.
CA-7.306 **WARNING** 80% xxxxxxx QUEUE UTILIZATION **WARNING**

Explanation: Eighty percent of the queue indicated by xxxxxxx has been allocated. Issued by
SASSDAIO.
User Response: If xxxxxxx indicates SCRATCH or DQTABLE, ....(current action....)
If xxxxxxx indicates TRAILER, verify the allocation of the queue with the command
/DISPLAY,Q=ALL. The trailer queue usage can be reduced by deleting retained JCL for jobs (refer
to PRRNJCL command) or by deleting jobs from the Request, Ready, or Active queues.
To prevent future space shortages, the queue indicated by xxxxxxx may need to be increased in size.
Chapter 4. CA-7.000 - CA-7.999 4-21

CA-7.307 –CA-7.373
CA-7.307 **xxxxxxx QUEUE TRACK SHORTAGE RELIEVED**

Explanation: The use of the queue indicated by xxxxxxx has dropped below 70 percent. This
message occurs after message CA-7.306 has been issued. Issued by SASSDAIO.
CA-7.360 LTERM=xxxxxxxx (yyyyyyyy) HAS nnnn MESSAGES QUEUED

Explanation: For information only. nnnn messages have been queued to the logical terminal
xxxxxxxx and physical terminal yyyyyyyy. Issued by SASSQMGO.
CA-7.370 BAD RESERVE - ENQUEUE MACRO RETURN

Explanation: A bad return code was received from the SCOMRD macro during a read of the Com-
munications data set. Issued by SASSCMGR.
User Response: A serious problem exists within CA-7. Contact your installation's CA-7 specialist
for assistance.
CA-7.371 I/O ERROR ON RBN0 READ

Explanation: An I/O error occurred while attempting to read the RBN0 control record in the Com-
Note: If error occurs during initialization, then the Communications data set may never have been
formatted.
User Response: This could be a serious problem. Contact your installation's CA-7 specialist for
assistance. If the Communications data set has never been initialized (formatted), the CDSI installa-
tion job must be run.
CA-7.372 COMM DATA SET NOT ENQUEUED

Explanation: A DEQUEUE was attempted during a write of a record that was not ENQUEUED.
Issued by SASSCMGR.
for assistance.
CA-7.373 BAD RELEASE/DEQUEUE MACRO RETURN

Explanation: A bad return code was received from the SCOMWR macro during a write of the
RBN0 control record in the Communications data set. Issued by SASSCMGR.
for assistance.

CA-7.374 –CA-7.378
CA-7.374 I/O ERROR ON WRITE

Explanation: An I/O error occurred while attempting to write the RBN0 control record in the Com-
User Response: This could be a serious problem. Contact your installation's CA-7 specialist for
assistance.
CA-7.375 SMF SCT NOT AVAILABLE - NO RECORD RETURNED

Explanation: An SCT for the SMF routines could not be located, resulting in a condition which
will not allow any SMF data to be processed. Issued by SASSCMGR.
for assistance.
CA-7.376 TRAILER LINE AREA NOT AVAILABLE - NO RECORDS RETURNED

Explanation: A line for the Trailer Step routines could not be located, resulting in a condition
which will not allow any Trailer commands to be processed. Issued by SASSCMGR.
User Response: A serious problem exists in CA-7. Contact your installation's CA-7 specialist for
assistance.
CA-7.377 UNABLE TO OPEN UCC7STAT FILE

Explanation: The Statistics data set could not be opened, possibly because of a missing DD state-
ment. Issued by SASSCMGR.
User Response: No action is needed for CA-7 to execute; however, no statistics can be gathered
and no graphing done. Add a DD statement to the execution JCL if statistics features are desired.
CA-7.378 I/O ERROR ON UCC7STAT FILE

Explanation: An I/O error occurred while attempting to write to the Statistics data set. Issued by
SASSCMGR.
User Response: If the Statistics data set has just been allocated (for new users), it must be initial-
ized by the SASSCDSI program before it can be used by CA-7. If it has been reallocated on another
pack, the old Statistics data set should be copied to the newly allocated data set. Contact your instal-
Chapter 4. CA-7.000 - CA-7.999 4-23

CA-7.400 –CA-7.404
CA-7.400 MAIN STORAGE MANAGER ERROR - U0400

Explanation: Invalid data was passed to the CA-7 main storage manager; a user 400 abend will
result. Issued by SASSMAIN, SASSF32V.
User Response: Restart CA-7 with a TYPE=ERST. Contact your installation's CA-7 specialist if
the condition persists.
CA-7.401 SCHEDULER INITIALIZATION REQUIRES MORE STORAGE

Explanation: Core was not available for a TSRLIST for Schedule Scan or for SASSCHED.
(SASSCHED's TSRLIST is used to write COLD/RESTART messages.) Issued by SASSCHED.
User Response: Increase the REGION size in CA-7's execution JCL and resubmit the job.
CA-7.402 SYSTEM ERROR. CODE = xxxx

Explanation: A system error occurred. This message is usually preceded by a CA-7.404 message.
Issued by SASSNUC.
User Response: Contact your installation's CA-7 specialist for assistance. Be sure to have any
CA-7.404 messages available.
CA-7.403 SASSxxxx-STORAGE MANAGEMENT ERROR - U0403

Explanation: An invalid return code was received from a request for core. Issued by SASSCHDB,
SASSCHDM, SASSCHDQ, SASSCHDS, SASSCHDW, SASSCHED.
User Response: For PDS/VSAM, check the Job data set block size. It must be 1024. Contact
CA-7.404 ATTACH FOR SASSBTMG FAILED. CODE = xxyyyyyy

Explanation: CA-7 was unable to attach the subtask manager. Issued by SASSNUC.
CA-7.404 SUBTASK xxxxxxxx TERMINATED. TCBCMP = xxyyyzzz

Explanation: CA-7 SUBTASK xxxxxxxx has terminated. yyy is the system abend code and zzz is
the user abend code. Both are in hex. Issued by SASSNUC.
User Response: If TCBCMP field is nonzero, contact your installation's CA-7 specialist for assist-
ance. If TCBCMP field is zero, the SUBTASK has completed normally and no action is required.
CA-7.404 IDENTIFY FAILED FOR SASSTCBC

Explanation: A failure occurred during subtask initialization. Issued by SASSNUC.

CA-7.405 –CA-7.413
CA-7.405 SASSCHDM - ERROR DURING ABEND DUMP - U0405

Explanation: CA-7 module encountered an error while putting out SNAP dump for an abend.
Issued by SASSCHDM.
CA-7.406 SASSCHDM - INVALID MESSAGE REQUEST - U0406

Explanation: An invalid SPUTMSG has been issued. Issued by SASSCHDM.
CA-7.406 MODULE xxxxxxxx COULD NOT BE LOADED

Explanation: The module specified by xxxxxxxx failed to load. Issued by SASSCHED.
User Response: Verify that the module has not been inadvertently deleted from the CA-7 Load
library and that the APPLCTN statement is present (and correct) in the CA-7 initialization file or in
module SASSPROG. If both checks are okay, contact your installation's CA-7 specialist for assist-
ance.
CA-7.407 SASSCHDM - MSG SWITCH ERROR - U0407

Explanation: No format block was available to output the SPUTMSG request. Possible module
load failure. Issued by SASSCHDM.
User Response: Verify that there are FMTBLK statements in the initialization file for both
SASSFMTA and SASSFMTH and that both specify ATTR=LOAD. If both are present, contact your
CA-7.410 UCC7DUMP DATA SET FAILED TO OPEN

Explanation: An attempt to OPEN the data set defined by the UCC7DUMP DD statement has
failed. Issued by SASSNUC.
User Response: Verify that the UCC7DUMP DD statement is present in the CA-7 JCL; if it is,
CA-7.412 ERROR WRITING CA-7 NUMBER TABLE - U0412

Explanation: An I/O error occurred while attempting to write a Checkpoint record for the CA-7
number table. CA-7 will abend. Issued by SASSNUC.
CA-7.413 ERROR USING SNAT - MUST HAVE A TSRLST

Explanation: An attempt was made to use the CA-7 Number Allocator Table without a TSR list.
Issued by SASSNUC.
Chapter 4. CA-7.000 - CA-7.999 4-25

CA-7.444 –CA-7.445
CA-7.444 (/DMP1)
(/DUMP) COMMAND ACCEPTED - U0444
Explanation: A /DUMP or /DMP1 request has been accepted for processing. Issued by
SASSSCM3.
CA-7.445 OUT OF SPACE ON LOG FILE

Explanation: During a batch-only run of CA-7, the primary Log file filled up and a swap was
attempted. Issued by SASSLOGM.
User Response: Increase the space allocation to the primary Log file, or assign the primary Log file
to a tape and start CA-7 again.

CA-7.500 –CA-7.512
CA-7.500 CHECKPOINT ERROR. REPLY Y TO CONTINUE WITHOUT CHECKPOINTING

Explanation: An error has occurred during CA-7 system checkpoint activity because:
1. The Checkpoint data set is on a device type different from the queues;
2. The Checkpoint data set was not allocated on a cylinder boundary; or,
3. Not enough space has been allocated to the Checkpoint data set.
4. I/O error.
Issued by SASSCKPT.
User Response: CA-7 will remain in a wait state until a reply of Y is done. CA-7 should be
recycled as soon as possible. Reply Y and shutdown CA-7 as soon as possible or cancel CA-7 with
a dump.
When Checkpointing is not done, Schedule Scan can rescan previous time frames bringing in jobs
which have already executed. Also, WLB definitions may not reflect current values. The queue data
sets may not show jobs that should be showing. All of these things can happen if CA-7 is not
recycled as soon as possible.
CA-7.510 CA-7 SHUTDOWN COMPLETE

Explanation: Self-explanatory. Issued by SASSHALT.
CA-7.511 BATCH TEST HAS EXCEEDED TIME - U0511

Explanation: The time limit imposed on batch execution of CA-7 has been exceeded. The default
is 1 hour. Issued by SASSHALT.
User Response: Increase the TIMLIM value on the INIT statement in the CA-7 initialization file
and resubmit the run. If the failure recurs, contact your installation's CA-7 specialist for assistance.
CA-7.512 COMDS IS BUSY SHUTDOWN IS WAITING

Explanation: CA-7 is attempting to update the RBN0 control record of the Communications data
set during shutdown. The update is waiting for the data set to become available. Issued by
SASSHALT.
User Response: No action is necessary unless the message persists, in which case, contact your
Chapter 4. CA-7.000 - CA-7.999 4-27

CA-7.514 –CA-7.560
CA-7.514 RBN-ZERO ERROR RETURN CODE = xx

Explanation: An invalid return code (indicated by xx) was received from an attempt to update the
RBN0 control record during shutdown. Issued by SASSHALT.
CA-7.554 I/O ERROR READING LOG DATA SET MUST COLD START
Explanation: An unrecoverable I/O error occurred while attempting to process the Log data set
during initialization. CA-7 will not be initialized. Issued by SASSINE1.
User Response: To attempt to recover without a COLD start, scratch and reallocate the Log data
set in error. If problem remains, CA-7 must be COLD started (TYPE=COLD).
CA-7.560 SASSMAIN - STORAGE NOT AVAILABLE, NO WAIT REQUESTED - U0560

Explanation: If a request for core cannot be satisfied and NCWT has been specified on the INIT
statement in the CA-7 initialization file, CA-7 will abend. Issued by SASSMAIN.
Note: This should never occur in online mode. NCWT should be omitted from the INIT statement,
thus allowing this wait during online execution.
CA-7.560 SASSMAIN - STORAGE NOT AVAILABLE. ZERO BYTES REQUESTED

Explanation: A request for 0 (zero) bytes of main storage has been received by the CA-7 main
storage manager. Issued by SASSMAIN.
User Response: If a WARM start of CA-7 fails, then a specific ERST start should be attempted. If
the problem persists, contact your installation's CA-7 specialist for assistance.
CA-7.560 SASSMA31 - STORAGE NOT AVAILABLE,NO WAIT REQUESTED - U560

Explanation: If a request for core cannot be satisfied and NCWT has been specified on the INIT
statement in the CA-7 initialization file, CA-7 will abend. Issued by SASSMA31.
User Response: This should never occur in online mode. NCWT should be omitted from INIT
statement to allow the wait during online execution.
CA-7.560 SASSMA31 - STORAGE NOT AVAILABLE. ZERO BYTES REQUESTED

Explanation: CA-7 cannot honor a request for zero bytes of storage above the 16 Mb line. Issued
by SASSMA31.

CA-7.570 –CA-7.575
CA-7.570 11 R=nnnnnnnn
Explanation: The CA-7 SVC was issued for status with an invalid entry code. The code is indi-
cated by nnnnnnnn which was passed from IGCS1XXX. Issued by IGCSEXXX.
User Response: Verify the installation of the SVC for CA-7. Also, verify the program which
issued the SVC.
CA-7.570 32 R=nnnnnnnn
Explanation: The CA-7 SVC was issued for SMF with an invalid entry code. The code is indi-
cated by nnnnnnnn which was passed from IGCS3XXX or IGCSMF30. Issued by IGCSEXXX.
User Response: If R=00000009 and NCF is installed, the wrong copy of IGCS3XXX is installed.
Module IGCSMF30 should be copied from the CA-7 Load library to LPALIB and renamed
IGCS3XXX.
CA-7.571 31 J=jobname D=ddname

Explanation: A blank data set name was encountered for a job submitted by CA-7. Where:
jobname follows J=
ddname follows D=
Issued by IGCSEXXX.
User Response: Unless the message appears frequently, no immediate action is required. If the
message does appear frequently, verify the installation of the SVC and SMF exits. Also, verify the
job creating the data set.
CA-7.574 (taskname) ENTER REQUEST FOR ICOM (xxxx)

Explanation: This is an outstanding WTOR for ICOM. Replies may be used to display control
blocks for ICOM processing or to shut down ICOM. The name of the job or started task executing
ICOM is indicated by taskname, and the subsystem used for CA-7 is noted by xxxx. Issued by
SASSICM1.
User Response: Enter the appropriate reply for the desired action. Refer to the CA-7 Systems Pro-
grammer Guide for reply formats. A MODIFY command may be used instead of a WTOR reply.
CA-7.575 SMF - aaaa(bbbb), cccccccc(dddddddd) xxx

TRL - aaaa(bbbb), cccccccc(dddddddd) xxx
DDNAME = nnn...n
Explanation: This is the response to a D=STAT reply to the CA-7.574 WTOR. The first line
provides SMF statistics, the second line provides Trailer Step statistics, and the third line indicates
the ddname used for submit.
aaaa Indicates current number of records chained.
bbbb Indicates maximum number of records chained since last IPL.
cccccccc Indicates current number of bytes used.
dddddddd Indicates maximum number of bytes used since the last IPL.
Chapter 4. CA-7.000 - CA-7.999 4-29

CA-7.576 –CA-7.579
xxx Will be either YES or NO to indicate if records are being collected.

Issued by SASSICM1.
CA-7.576 xxxxxx aaaaaaaa bbbbbbbb cccccccc

Explanation: This is the response to a D=DSECT reply to the CA-7.574 WTOR. Several lines
may be dumped showing the ICOM work area, ICMDSECT. The address of the core is indicated by
xxxxxx. Issued by SASSICM1.
CA-7.577 DDNAME ERROR. CANNOT SUBMIT JOB(S)

Explanation: An error occurred while attempting to use a Submit data set. Probable cause is a
missing DD statement. Issued by SASSASP, SASSHASP, SASSJES1, SASSJES2, SASSJES3.
User Response: If job submission by ICOM is necessary, ICOM must be stopped; the missing DD
statement for the Submit data set must be added to the ICOM JCL and resubmitted. If the error
CA-7.578 xxx...x SUBTASK ENDED. TCBCMP= ccc...c

Explanation: The subtask specified by xxx...x has terminated; the TCB completion code is given by
ccc...c. If ICOM was not being normally stopped, then an error has occurred. Issued by
SASSICM1.
User Response: If an abnormal subtask termination has occurred, ICOM should be canceled with a
dump. Contact your installation's CA-7 specialist when the dump is available.
CA-7.579 ICOM [(TRAILER)|(SUBMIT)|(SMF)] SUBTASK WAITING FOR xxxx SECONDS. CODE= y

Explanation: A subtask of ICOM has been waiting for xxxx seconds for the Communications data
set. The location in the subtask module where the wait occurred is indicated by y:
If y=A, ICOM is trying to get control of the Communications data set to submit a job.
If y=B, ICOM is trying to post to the Communications data set.
If y=0, the Communications DSN is busy.
If y=4, the Communications data set is full.
If y=8, the NCF Communications data set is busy.
Issued by SASSJES2 and SASSJES3.
User Response: This could indicate that the Communications data set is on a high-access disk pack;
better response is provided if it is on a low-access pack. If the message persists, cancel ICOM with
a dump. Contact Computer Associates Technical Support when the dump is available.

CA-7.580 –CA-7.583
CA-7.580 RJP INPUT QUEUE FULL

Explanation: More input commands have been entered than there is room for in the Communi-
cations data set. Issued by SASSICM1.
User Response: If CA-7 is not active, this could be completely normal. Otherwise, increase the
specification on the *CDSINIT* and reinitialize the Communications data set. (Do not reinitialize
the database.)
CA-7.581 BAD DATA. CODE= x

Explanation: The reply to the CA-7.574 WTOR was specified incorrectly. The x will indicate one
of the following:
A - Invalid command
B - Not enough data supplied
C - Invalid SUB command data
D - Invalid command
Issued by SASSICM1.
User Response: Reenter the reply to the WTOR specifying the correct data and format. Refer to
the CA-7 Systems Programmer Guide for reply format.
CA-7.582 ERROR RETURN CODE= xxxxxx

Explanation: A return code of 4 indicates an operator attempted to delete a chain of SMF records
(by a response to ICOM's outstanding WTOR) while ICOM had the chain enqueued. Issued by
SASSICM1.
User Response: Wait a few minutes then reenter the response.
CA-7.583 ANOTHER ICOM IS ACTIVE FOR xxxx

Explanation: Another copy of ICOM is already active on the CPU. The value of xxxx will indi-
cate the subsystem name for either the production (UC07) or test (UCT7) copy of CA-7. Issued by
SASSICMI.
User Response: Verify that the correct version of ICOM is active.
CA-7.583 ANOTHER CA-7 IS ACTIVE FOR xxxx

Explanation: Another copy of CA-7 is already active on the CPU. The value of xxxx will indicate
the subsystem name for either the production (UC07) or test (UCT7) copy of CA-7. Issued by
SASSISVC.
User Response: Verify that the correct version of CA-7 is active. If there is not another CA-7
active, use the RNAME keyword on the SVCNO statement of the initialization file to override UC07
or UCT7.
Chapter 4. CA-7.000 - CA-7.999 4-31

CA-7.584 –CA-7.588
CA-7.584 xxxx NOT MATCHED IN ICMDSECT

is used for enqueuing certain items, such a mismatch could cause system and data integrity problems.
Issued by SASSICMI or SASSISVC.
ICMDSECT is the wrong format (probably a wrong module) and should be reinstalled. If
ICMDSECT needs to be reinstalled, a REINIT(COLD) should be done. If the xxxx value is UC07 or
UCT7, the system was not initialized using CAIRIM, in which case, running CAIRIM to INIT or
REINIT should correct the problem.
CA-7.585 TASKNAME: jjjjjjjj

Explanation: This is the response to a D=EXTJOB reply to ICOM. Several lines may be listed
showing all of the entries in the current SASSEXTL table. This table is used to determine which
SMF data is to be collected for tasks submitted outside of CA-7. Issued by SASSICM1.
CA-7.586 ICOM COUPLING FACILITY MODE = xxxx

Explanation: This is the response to a CF=STAT reply to ICOM. The value of xxxx will be
NONE, READ or WRITE to reflect the current coupling facility mode.
CA-7.587 ICOM CF : CURRENT : SMF sssssss TRL ttttttt NCF nnnnnnn

ICOM CF : PROCESSED : SMF sssssss TRL ttttttt NCF nnnnnnn
Explanation: This is the response to a CF=STAT reply to ICOM if the current coupling facility
mode is READ or WRITE. The values are:
sssssss is the number of current/processed SMF records
ttttttt is the number of current/processed Trailer records
nnnnnnn is the number of current/processed NCF records
CA-7.588 INVALID ICOM COUPLING FACILITY PARAMETER

Explanation: The value specified for the ICOM Coupling Facility Mode in the ICOM execution
parameters was invalid. ICOM will not initialize.
User Response: Correct the parameters and restart ICOM. Refer to the Execution chapter of the
CA-7 Systems Programmer Guide for information on valid ICOM parameters.

CA-7.589 –CA-7.592
CA-7.589 INVALID ICOM PARM KEYWORD(S).

Explanation: One or more values specified in the ICOM execution parameters was invalid. ICOM
will not initialize.
CA-7 Systems Programmer Guide for information on valid ICOM parameters.
CA-7.590 XMONITOR= KEYWORD IGNORED: XCKPT DD NOT FOUND/DUMMIED

Explanation: The XMONITOR= keyword was specified in the ICOM execution parameters;
however, the required Cross-Platform Tracking Checkpoint file (XCKPT DD) was not found, or is a
DUMMY DD. ICOM will initialize without the Cross-Platform Tracker (XTRK).
CA-7 Systems Programmer Guide for information on valid ICOM parameters. Also, refer to the
CA-7 Interfaces Guide for information on the CA-7 Cross-Platform Tracker.
CA-7.591 ICOM SUBM/TASK I/O ERROR

Explanation: An I/O error was encountered in accessing the Communications data set. Issued by
SASSRJPO.
CA-7.592 XTRK TASK NOT ACTIVE UNDER ICOM

Explanation: An XTRK= command was issued for ICOM; however, the Cross-Platform Tracker
(XTRK) is not active as an ICOM sub-task at this time.
Chapter 4. CA-7.000 - CA-7.999 4-33

CA-7.601 –CA-7.616
CA-7.601 [(LIBRARIAN)|(PANVALET)] MODULE IN USE FOR 30 SECONDS

Explanation: The interface module for CA-Librarian or CA-Panvalet access has been in continuous
use for over 30 seconds. This probably means a wait or lockout condition has developed because of
access from some other activity in the host system. Issued by SASSLIBR, SASSPANV.
User Response: Determine the cause of the delay and correct.
CA-7.610 INVALID MESSAGE ID REQUESTED

Explanation: A module requested a WTO that has not been defined.
CA-7.611 ERROR OCCURRED DURING FIRST PASS

Explanation: A logic error occurred while counting groups, lines and terminals.
CA-7.612 RESIDENT STATEMENT MUST BE FIRST

Explanation: First statement was not a RESIDENT statement.
User Response: Provide a RESIDENT statement ahead of all others.
CA-7.613 INIT STATEMENT IS REQUIRED

Explanation: An INIT statement must be provided.
User Response: Provide and resubmit.
CA-7.614 SVCNO STATEMENT IS REQUIRED

Explanation: An SVCNO statement must be provided.
CA-7.615 APPLCTN STATEMENT IS REQUIRED

Explanation: At least 1 APPLCTN statement must be provided.
CA-7.616 FMTBLK STATEMENT IS REQUIRED

Explanation: At least 1 FMTBLK statement must be provided.

CA-7.617 –CA-7.625
CA-7.617 GROUP STATEMENT IS REQUIRED

Explanation: At least 1 GROUP statement must be provided.
CA-7.618 LINE STATEMENT IS REQUIRED

Explanation: At least 1 LINE statement must be provided.
CA-7.619 SECURITY STATEMENT IS REQUIRED

Explanation: A SECURITY statement must be provided.
CA-7.620 FORMAT STATEMENT IS REQUIRED

Explanation: FORMAT statement must be provided.
CA-7.621 DAIO STATEMENT IS REQUIRED

Explanation: A DAIO statement must be provided.
CA-7.622 UNKNOWN STATEMENT TYPE

Explanation: The statement is not a continuation of a previous statement and does not begin with a
valid statement ID.
User Response: Correct and resubmit.
CA-7.623 TERM STATEMENT IS REQUIRED

Explanation: At least 1 TERM statement must be provided.
CA-7.624 ONLY ONE OF THESE STATEMENTS ALLOWED

Explanation: Have already processed a statement of this type.
CA-7.625 ERROR OCCURRED WHILE SCANNING FOR A KEYWORD

Explanation: A logic error occurred looking for the next keyword.
Chapter 4. CA-7.000 - CA-7.999 4-35

CA-7.626 –CA-7.634
CA-7.626 UNKNOWN KEYWORD

Explanation: The keyword is not valid for this statement.
CA-7.627 Y, N, YES, NO ARE ONLY VALID VALUES

Explanation: Only the indicated values are valid.
CA-7.628 APPL KEYWORD IS REQUIRED

Explanation: The APPL keyword is required to provide the ID.
CA-7.629 GROUP COUNT EXCEEDS FIRST PASS COUNT

Explanation: A logic error occurred while counting groups, lines and terminals.
CA-7.630 GROUP NAME CANNOT EXCEED 7 CHARACTERS

Explanation: The name of the group must be 7 characters or less.
CA-7.631 UNRECOGNIZED VALUE

Explanation: The value is not valid for this keyword.
CA-7.632 UCC7VTAM STATEMENT WAS NOT PROVIDED

Explanation: The DEVICE value indicates VTAM terminals but no UCC7VTAM statement was
provided.
CA-7.633 NAME, LNAME, DEVICE KEYWORDS ARE REQUIRED

Explanation: The keywords must be provided.
CA-7.634 UNKNOWN PF/PA KEY ID

Explanation: Valid PF key IDs are 01-24; PA keys are 01-03.

CA-7.635 –CA-7.643
CA-7.635 VALUE MUST BE NUMERIC

Explanation: Value for this keyword must be numeric.
CA-7.636 VALUE MUST BE GREATER THAN ZERO

Explanation: Value must be numeric and greater than zero.
CA-7.637 VALUE MUST BE NO MORE THAN 255

Explanation: Value must not be greater than 255.
CA-7.638 NAME, TNAME KEYWORDS REQUIRED FOR VTAM

Explanation: These keywords are required for VTAM terminals.
CA-7.639 NAME, TNAME, BUFSIZE KEYWORDS REQUIRED FOR NON-VTAM

Explanation: These keywords are required for non-VTAM terminals.
CA-7.640 PRINTER DEVICE NOT ALLOWED AS A CONSOLE

Explanation: PRINTER=YES is not allowed with CONS=.
CA-7.641 YES IS ONLY VALID VALUE

Explanation: If used, must specify YES as the value.
CA-7.642 NON-ZERO SVC RETURN CODE FOR SVC IN ICMDSECT

Explanation: The SVC number defined in ICMDSECT is not properly defined to MVS.
User Response: Provide correct SVC number and resubmit.
CA-7.643 VIRTUAL TERM COUNT MUST AGREE WITH LINE STATEMENT

Explanation: VTM# value in LINE statement must be used here.
Chapter 4. CA-7.000 - CA-7.999 4-37

CA-7.644 –CA-7.652
CA-7.644 NAME, DEVICE, NLINE, LINLEN KEYWORDS REQUIRED

Explanation: The keywords are required.
User Response: Provide each and resubmit.
CA-7.645 ADRCHR KEYWORD REQUIRED FOR BTAM TYPE

Explanation: This keyword is required for BTAM terminals.
CA-7.646 INCORRECT NLGRP VALUE IGNORED

Explanation: Does not agree with number of GROUP statements.
User Response: None. For information only.
CA-7.647 INCORRECT NLINE VALUE IGNORED

Explanation: Does not agree with number of LINE statements.
CA-7.648 INCORRECT NLTERM VALUE IGNORED

Explanation: Does not agree with number of nonprinter terminals.
CA-7.649 INCORRECT NLPRT VALUE IGNORED

Explanation: Does not agree with number of terminals with PRINTER=YES.
CA-7.650 CUST ID CANNOT BE BLANK

Explanation: A value must be given for customer ID.
CA-7.651 CONFIG, TYPE KEYWORDS ARE REQUIRED

Explanation: These keywords are required on the INIT statement.
CA-7.652 SASSVC KEYWORD IS REQUIRED

Explanation: The indicated required keyword was not found.

CA-7.653 –CA-7.662
CA-7.653 VALUE HAS TOO MANY CHARACTERS

Explanation: No acceptable value has this many characters.
CA-7.654 VALUE HAS TOO FEW CHARACTERS

Explanation: No acceptable value has this few characters.
CA-7.655 APPLCTNS MUST BE GROUPED TOGETHER

Explanation: APPLCTN statements all reside together.
CA-7.657 NAME KEYWORD IS REQUIRED

CA-7.658 STN KEYWORD MUST BE LAST KEYWORD

Explanation: No other keywords can follow the STN keyword.
CA-7.659 VALUE IS TOO HIGH

Explanation: The value exceeds the allowable upper limit.
CA-7.660 RANGE END LESS THAN START

Explanation: The ending range value can not be lower than the starting value.
CA-7.661 STN KEYWORD IS REQUIRED

CA-7.662 STNCAL STATEMENT MUST FOLLOW STATIONS STATEMENT(S)

Explanation: STATIONS statements must occur in the initialization file before the STNCAL state-
ment.
User Response: Resequence and resubmit.
Chapter 4. CA-7.000 - CA-7.999 4-39

CA-7.663 –CA-7.671
CA-7.663 TRMID KEYWORD MUST BE FIRST

Explanation: The TRMID keyword must precede STANIDS or LTERM.
CA-7.664 STATION NAME ALREADY DEFINED

Explanation: Station names can only be defined once.
CA-7.665 PROGRAM ERROR BUILDING STATION ID LIST

Explanation: A program logic error has occurred.
CA-7.666 TRMID, STANIDS/LTERM KEYWORDS ARE REQUIRED

Explanation: Two keywords are required in STATIONS statements.
User Response: Provide both and resubmit.
CA-7.667 REQUIRED KEYWORD(S) MISSING

Explanation: At least 1 required keyword was not found.
CA-7.668 DDNAME NOT DEFINED IN THE JCL

Explanation: This DDNAME value does not exist in the JCL.
CA-7.669 DDNAME KEYWORD IS REQUIRED

CA-7.670 DISP KEYWORD IS REQUIRED

CA-7.671 DAIO STATEMENT MUST FOLLOW FORMAT STATEMENTS

Explanation: This statement can only reside after all FORMATs.

CA-7.672 –CA-7.680
CA-7.672 Y, YES, N, NO, A, ALL ARE ONLY VALID VALUES

Explanation: This keyword will only accept the indicated values.
CA-7.673 DASD KEYWORD IS REQUIRED

Explanation: This required keyword was not found.
CA-7.674 MAINID TABLE IS FULL

Explanation: The MAINID values in CPU statements have exceeded the total number allowed.
CA-7.675 TRM DEFINITION ERROR IN SECURITY MODULE

Explanation: An error exists in the defined TRM values in the security module.
User Response: Correct, reassemble and resubmit.
CA-7.676 DEFINED IN SECURITY MODULE BUT NO APPLCTN FOUND

Explanation: An application was defined in the security module but no APPLCTN statement was
provided.
User Response: Provide the APPLCTN statement and resubmit.
CA-7.677 APPL DIRECTORY HAS NOT BEEN BUILT

Explanation: The internal directory of applications was not built.
CA-7.678 NO TRMSECUR POINTER IN TRMDEF

Explanation: No address found for security in a terminal block.
User Response: Contact your installation's CA-7 specialist.
CA-7.679 OPER ID INDEX CANNOT BE ZERO

Explanation: Operator ID must not be zero.
CA-7.680 OPERID/APPLID DEFINITION ERROR

Explanation: An error exists in the defined OPID/APLID values in the security module.
User Response: Correct, reassemble and resubmit.
Chapter 4. CA-7.000 - CA-7.999 4-41

CA-7.681 –CA-7.688
CA-7.681 INDEX VALUE ALREADY DEFINED

Explanation: Each library must have a unique INDEX value.
User Response: Assign unique values and resubmit.
CA-7.682 FOUND U7 DDS BUT PERFORM OPTION 8 WAS NOT SPECIFIED

Explanation: The PERFORM option values conflict with the DD statements found in the JCL.
CA-7.683 ALT LIBRARY MUST BE DEFINED FIRST

Explanation: The ALT value must reference a library that is defined in the initialization file ahead
of the reference.
User Response: Resequence the JCL statements and resubmit.
CA-7.684 LIBRARY CANNOT BE ALTERNATE FOR ITSELF

Explanation: The ALT and INDEX values can not be the same.
CA-7.685 PARAMETER LIST IS INVALID

Explanation: The value indicated is either invalid or exceeds the maximum number of values
allowed in the list.
User Response: Correct the indicated value or reduce the number of values and resubmit.
CA-7.686 INVALID JCL LIBRARY NAME

Explanation: A JCL library name must consist of an ampersand (&) followed by up to 15 alphanu-
meric characters.
CA-7.688 PARM VALUES INCONSISTENT WITH SYMBOLIC DEFINITION

Explanation: An error was detected for a symbolic JCL library JCL statement. The following
conditions can cause this error:
DYN=2 was not specified.
DYN=2 was specified, but dynamic allocation is not enabled (see PERFORM keyword on INIT
statement).
DSORG=PDS was not specified or defaulted.
A value was specified for the MCD= keyword.

CA-7.699 –CA-7.710
CA-7.699 EXTERNAL SECURITY INTERFACE INSTALLED

Explanation: The SECURITY statement of the initialization file contained the EXTERNAL
keyword.
CA-7.699 INTERNAL SECURITY BEING USED.

Explanation: All security access will be handled by CA-7 internal security.
CA-7.699 NO DEFAULT ID SUPPLIED FOR XPS

Explanation: No default user ID was supplied for the SECURITY statement keyword XPSSID. All
XPS scheduling requests must include a valid user ID.
User Response: This is a warning message. Because no user ID was coded on the XPSSID
keyword, CA-7 will be unable to honor cross-platform scheduling requests that do not contain a user
ID.
We recommend that you supply a user ID as the value of the XPSSID keyword on the SECURITY
statement. This user ID will be used for any cross-platform scheduling request that does not contain
a user ID.
CA-7.700 I/O ERROR DURING WRITE OF TRACK TABLE - U0700

Explanation: An I/O error has occurred while writing to the track allocator table for the output
queue. Issued by SASSHALT, SASSQMG, SASSQMGO, SASSQMGQ.
CA-7.701 MAIN STORAGE REQUEST ERROR FROM SASSQMG - U0701

Explanation: An invalid return code was received from a request for core. Issued by SASSQMG.
CA-7.702 QUEUE MANAGER PAGE OUT ERROR - U0702

Explanation: An output page was found to contain less than four bytes of data. Issued by
SASSQMG.
CA-7.710 I/O ERROR IN xxx QUEUE

Explanation: An I/O error was encountered while attempting to read or write the queue data set
identified by xxx. Issued by SASSDAIO.
User Response: If the error is in the Trailer queue, message CA-7.INW3 may also be issued at the
OS console. This indicates a bad pointer in the queue. Refer to required action for CA-7.INW3.
Contact your installation's CA-7 specialist for assistance, especially if error is accompanied by IBM
error messages indicating chaining checks.
Chapter 4. CA-7.000 - CA-7.999 4-43

CA-7.711 –CA-7.730
If xxx is DQT, the user could have issued a generic type list or forecast command that caused over
255 pages of output. If this is the situation, run this using the Batch Terminal Interface.
If the queues have been moved to a different device type, be sure the DEVICE parameter on the
DAIO statement reflects the device change and that all queues and the Checkpoint data set are on the
same device type.
CA-7.711 IOB FOR COMPLETED ECB NOT FOUND - U0711

Explanation: A search for an I/O block for a completed I/O activity has failed. Issued by
SASSDAIO.
CA-7.714 WRITE ERROR nn hh

Explanation: An error has been detected writing to a batch terminal. The return code from the
write macro is indicated by nn; the CSW status from the job is indicated by hh. Issued by
SASSFBAT.
CA-7.730 CA-11 INACTIVE, DO YOU WANT JOBS SUBMITTED? (YES/NO/NO11)

Explanation: This WTOR is issued under these conditions:
The RESTART statement is present in the initialization file.
RMS=NO is not specified on the RESTART statement.
CA-11 is not active when CA-7 is started.
CA-11 terminates while CA-7 is active. In this case the WTOR is not issued until the next time
CA-7 attempts to communicate with CA-11 (for example XRST or CANCEL).
All CA-7 processing is suspended until a response is received.
User Response: Issue the appropriate response to the WTOR. If the reply is YES, CA-7 will
submit jobs and attempt to use the CA-11 interface as if CA-11 were active. Jobs that are defined
with INSERT-RMS=Y will have the CA-11 RMS step inserted when submitted. If the reply is NO,
any jobs that are defined with INSERT-RMS=Y will not be submitted (will remain in the Ready
queue) when their requirement count becomes zero. The restart functions of CA-7 will still attempt
to interface with CA-11.
If the reply is NO11, all jobs will be submitted without an inserted CA-11 RMS step. The restart
functions will not attempt to interface with CA-11. To activate the interface (after CA-11 is active),
the SUBMIT command must be issued.
If CA-11 is started after responding to the WTOR, the interface may be activated by issuing the
SUBMIT command or by canceling or restarting a job.

CA-7.731 –CA-7.736
CA-7.731 CA-7 WILL SUBMIT JOBS WITH THE CA-11 STEP

Explanation: The reply to the CA-7.730 WTOR was YES. After CA-7 completes initialization,
jobs will be submitted as if the CA-11 interface is active.
User Response: If CA-11 is started after responding to the WTOR, the interface may be activated
by issuing the SUBMIT command or by canceling or restarting a job.
CA-7.732 CA-7 WILL NOT SUBMIT CA-11 JOBS.

Explanation: The reply to the CA-7.730 WTOR was NO. CA-7 will not submit any jobs that are
defined as INSERT-RMS=Y. These jobs will remain in the Ready queue until the interface is avail-
able or the job is changed to not require the RMS step.
CA-7.733 CA-7 WILL STOP SUBMITTING CA-11 JOBS

Explanation: The reply to the CA-7.730 WTOR was NO. CA-7 will stop submitting any jobs that
are defined as INSERT-RMS=Y. These jobs will remain in the Ready queue until the interface is
available or the job is changed to not require the RMS step.
CA-7.734 CA-11 PROCEDURE NAME BLANK IN CA-11 OPTIONS TABLE.

Explanation: CA-11 was not fully initialized when CA-7 was started so the CA-11 options table
did not have the RMS procedure name filled in. Also, the PROCRMS keyword was not specified on
the RESTART statement in the initialization file.
User Response: Respond to the WTOR which follows. Only NO or NO11 will be accepted. If the
PROCRMS keyword was specified on the RESTART statement, this message would not be issued.
CA-7.735 INVALID REPLY, MUST BE "YES", "NO", OR "NO11".

Explanation: An invalid reply was made to the CA-7.730 WTOR.
User Response: The CA-7.730 WTOR is reissued, prompting for a valid reply.
CA-7.736 THE CA-11 INTERFACE IS NOW ACTIVE.

Explanation: The CA-7 interface with CA-11 was not active prior to this message but has now
been activated. The interface can be activated by issuing the SUBMIT command or, if the previous
WTOR reply was YES or NO, by canceling or restarting a job.
Chapter 4. CA-7.000 - CA-7.999 4-45

CA-7.737 –CA-7.744
CA-7.737 THE CA-11 INTERFACE HAS BEEN DEACTIVATED.

Explanation: The reply to the CA-7.730 WTOR was NO11. CA-7 will submit jobs without
inserting the CA-11 RMS step. The cancel and restart functions will not attempt to interface with
CA-11. This has the same effect as coding RMS=NO on the RESTART statement in the initializa-
tion file.
by issuing the SUBMIT command.
CA-7.740 CA-7 DORMANT START. REPLY "YES" TO TAKE OVER OR "STOP" TO END.
Explanation: TYPE=DORM.
User Response: None is required. To manually cause the dormant copy of CA-7 to complete
initialization, reply YES. To terminate the dormant CA-7 with a U0777 abend, reply STOP.
CA-7.741 INVALID WTOR REPLY

Explanation: This WTO is issued by SASSLINK when an invalid reply is entered for the CA-7.740
or CA-7.743 WTOR. The original WTOR is reissued.
User Response: Issue a valid reply for the reissued WTOR.
CA-7.742 CAN NOT INITIALIZE, ENQ HELD BY OTHER TASK

Explanation: A reply of YES was issued to the CA-7.740 WTOR but another CA-7 task is already
holding the ENQ. The dormant copy can not complete initialization without obtaining the ENQ.
Issued by SASSLINK.
User Response: Determine if there is another CA-7 running which already has the same ENQ
issued as the dormant CA-7. If the dormant CA-7 is supposed to take over, shutdown the other
CA-7 task.
CA-7.743 MAIN CA-7 INACTIVE - DORM WILL TAKE OVER UNLESS "STOP" REPLY.
Explanation: The dormant copy of CA-7 determined that the main copy is not active. This WTOR
indicates that the dormant copy will take over for the main copy unless a reply of STOP is received
within a specified number of seconds. This WTOR is issued by SASSLINK.
User Response: None required. If you do not want the dormant copy of CA-7 to take over, reply
STOP and it will terminate with a U0777 abend.
CA-7.744 RESUME INITIALIZATION PROCESS

Explanation: The dormant copy of CA-7 determined that the main copy is not active. This WTO
indicates that the dormant copy is going to complete initialization and take over the CA-7 functions
for the main CA-7. Issued by SASSLINK.

CA-7.750 –CA-7.799
CA-7.750 SASSLOGM - LOGGING ERROR x

Explanation: The following shows the values of x:
1- An error condition was encountered in the SLOG macro.
2- An invalid request has been issued for the SLOG macro.
3- An active buffer could not be found for the Log data set. Most likely the buffer status area of
memory has been overlaid.
4- An I/O error was encountered on the Log data set.
Issued by SASSLOGM.
User Response: When x equals:
1- Contact your installation's CA-7 specialist for assistance.
2- Contact your installation's CA-7 specialist for assistance.
3- Cancel CA-7 with a dump and then use the emergency restart (TYPE=ERST) procedure to
reinitialize CA-7. Contact your CA-7 specialist when the dump is available.
4- CA-7 abends with a U0750. If the I/O error is permanent, it is necessary to move the Log
data set. When the error has been corrected, CA-7 should be reinitialized using the emer-
gency restart (TYPE=ERST) procedure.
CA-7.777 REPLY WAS STOP, NOW TERMINATING

Explanation: A response of STOP was issued to the CA-7.740 or CA-7.743 WTOR. CA-7 will
terminate with a U0777 abend. Issued by SASSLINK.
CA-7.799 SVC DUMP BEING PRODUCED

Explanation: A CSA storage overlay was detected. An external source has overlaid a chain used
by CA-7. To assist in determining the cause of the overlay, CA-7 is scheduling an SVC dump. This
dump will only occur the first time an overlay is detected after CA-7's CAIRIM initialization. The
SVC dump title is CA-7 CSA INFO.
This WTO is followed by the CA-7.SVC3 or CA-7SVC4 WTO which indicates the CA-7 data that
might have been lost.
User Response: The SVC dump should be examined to try to determine the cause of the storage
overlay.
Chapter 4. CA-7.000 - CA-7.999 4-47

CA-7.800 –CA-7.823
CA-7.800 MONITOR TIMED OUT.

Explanation: While running ARTS or TIQ under CA-7, the session timed out after the number of
minutes specified on the MONLIM parameter on the TERM statement in the initialization file (the
default is 2 minutes). This will only occur if the session is inactive for this amount of time.
User Response: No action is required unless the limit is too small for the particular terminal. If the
limit is too small, then either add a MONLIM parameter to the TERM statement or increase the
present value.
CA-7.820 UNRECOVERED ERROR ON xxxxxxxx

Explanation: An unrecoverable I/O error has occurred on the terminal specified by xxxxxxxx. No
abend will occur; output for the terminal will be queued in the output queue. Issued by
SASSLMGR.
User Response: Verify that terminal name is defined in the initialization file. Terminal and line
should be checked out and restarted by someone responsible for TP network maintenance.
CA-7.821 UNKNOWN ERROR ON xxxxxxxx

Explanation: An I/O has completed for a terminal which cannot be found in the CA-7 control
blocks. No abend will occur. Issued by SASSLMGR.
CA-7.822 (xxxxxxxx) CLOSED

Explanation: If the message is for a batch terminal, then the batch terminal has completed proc-
essing of the batch input data. This message is for information only. Otherwise, the error limit for
the specified terminal has been reached and the terminal has been stopped. Issued by SASSCHDS,
SASSLMGR.
User Response: Terminal should be checked and/or restarted by someone responsible for TP
network maintenance.
CA-7.823 LINE (xxxxxxxx) CLOSED

Explanation: The error limit for the line specified by xxxxxxxx has been reached and the line has
been stopped. Issued by SASSLMGR.
User Response: Line should be checked out and/or restarted by someone responsible for TP
network maintenance.

CA-7.824 –CA-7.872
CA-7.824 INT REQ LINE= xxxxxxxx, TERM= xxxxxxxx, [S/S= xxxx | VTAM NODE=yyyyyyyy]
Explanation: Intervention is required on the line and/or terminal specified. Either the status sense
(S/S) or the VTAM NODE name is given. Issued by SASSI32R, SASSI32V.
User Response: Line and terminal should be checked and/or required action taken by someone
responsible for TP network maintenance.
CA-7.851 RJP TERMINAL NOT DEFINED

Explanation: The RJP or MCS terminal which entered the command is not defined or is incorrectly
defined in the initialization file. Issued by SASSIRJP.
User Response: Verify that the initialization file is correct.
CA-7.852 RJP TERMINAL HAS BEEN CLOSED

Explanation: The CA-7 Master Terminal Operator (MTO) has stopped this RJP/MCS terminal.
Issued by SASSIRJP.
User Response: Start the terminal to continue processing.
CA-7.853 REQUEST IGNORED - INPUT PENDING

Explanation: A second command has been entered before the first command completed. Issued by
SASSIRJP.
User Response: Reenter the command after the response to the original input has been received.
CA-7.860 I/O ERROR ON RJP OUTPUT

Explanation: An I/O error was encountered in accessing the Communications data set. Issued by
SASSRWTR.
CA-7.861 I/O ERROR ON RJP INPUT

Explanation: An I/O error has been encountered in accessing the Communications data set. Issued
by SASSRRDR.
CA-7.871 RJP LINE NOT DEFINED

Explanation: This CPU has not been defined as a line in the initialization file. Issued by
SASSRRDR.
User Response: Verify that the initialization file is correct.
CA-7.872 RJP LINE HAS BEEN CLOSED

Explanation: The CA-7 Master Terminal Operator (MTO) has stopped the line for this CPU.
Issued by SASSRRDR.
User Response: Start the line to continue processing.
Chapter 4. CA-7.000 - CA-7.999 4-49

CA-7.873 –CA-7.880
CA-7.873 RJP LINE IS BUSY

Explanation: A unique timing situation has caused the line to appear busy. Issued by SASSRRDR.
User Response: Reenter your command. If the problem persists, contact your installation's CA-7
CA-7.880 TRX INIT ERR CODE xx

Explanation: Initialization of TRX terminal(s) failed. If xx=08, probably no TRX terminals (or
more than 10) were specified in the initialization file, and ARF is being used.
User Response: Either add a TRX terminal (the maximum number of TRX terminals is 10) or
change the RESTART statement to use ARF=NO.

CA-7.900 –CA-7.905
CA-7.900 BLDL FAILED FOR MODULE NAME xxxxxxxx - U0900

Explanation: Module name xxxxxxxx is not on the CA-7 Load library or an I/O error has occurred.
This is a warning message if no dump is produced. Issued by SASSLINK.
User Response: If a U0900 abend is produced, contact your installation's CA-7 specialist for assist-
ance. Otherwise, no action is required.
CA-7.900 RPT MODULE SASSINRP NOT FOUND OR INTERFACE NOT INITIALIZED

Explanation: Module SASSINRP or SASSCHDR is not on CA-7's Load library, or the CA-7/RPT
interface could not be initialized. Issued by SASSLINK.
User Response: Check the load library (STEPLIB) for modules SASSINRP and SASSCHDR. If
the modules are present, check the initialization file SVCNO statement. SASSVC=YES must be
specified. Be sure CA-7/RPT is up before CA-7.
CA-7.901 INVALID APPLCTN/FMTBLK/CALBLK LOAD MODULE OF xxxxxxxx

Explanation: The load module xxxxxxxx specified in either an APPLCTN, FMTBLK or CALBLK
NAME parameter is invalid or does not exist on CA-7 Load library. Issued by SASSIFCA.
User Response: Verify that the name specified exists on CA-7 Load library. If the module exists,
check the assembly listing for a valid assembly and link edit. The last statement assembled must
specify ATTR=LAST.
CA-7.904 SASSQM51 MISSING OR IN ERROR, RESTART INTERFACE TO CA-11 DISABLED

Explanation: During initialization of the interface with CA-11, the module SASSQM51, which per-
forms restart and cancel interfacing, either was not found or the wrong version of the interface was
indicated. Issued by SASSIRST.
User Response: If the interface with CA-11 (for restarts) is desired, assemble and link edit module
SASSQM51. Be sure the CA-11 macro library precedes the CA-7 macro library in the assembly
step. The module must be linked into a load library included in the STEPLIB concatenation for
CA-7.
CA-7.905 VERIFY TYPE=xxxx START-UP OPTION. REPLY 'OK' OR NEW OPTION

Explanation: A cold type of start option is being attempted for CA-7 (COLD, FORM, MOVQ).
The operator must reply to allow CA-7 to initialize. Issued by SASSINIT.
User Response: A reply of OK will allow CA-7 to initialize with the startup option printed in the
message. A reply of WARM or ERST will cause CA-7 to initialize with that particular option. A
reply of COLD, FORM, or MOVQ will cause this WTOR to be reissued. Any other reply will also
cause this WTOR to be reissued.
Chapter 4. CA-7.000 - CA-7.999 4-51

CA-7.906 –CA-7.910
CA-7.906 LOAD FAILED FOR MODULE xxxxxxxx

Explanation: An attempt to load module xxxxxxxx failed. Either the module does not exist on the
CA-7 Load library or there is a program problem. Issued by SASSICRD, SASSISEC.
User Response: Make sure the module exists on the CA-7 Load library. If the load failed on a
USERID module, verify that the SECURITY statement in the initialization file has a USER param-
eter. Check that the last USERID macro has LAST=YES coded. If the load failed on the SECU-
RITY module, verify that the NAME parameter on the SECURITY statement points to the correct
member on the Load library.
If module xxxxxxxx is not a security module, verify that the module is defined to CA-7 by an
APPLCTN statement in the initialization file or in the SASSPROG module.
CA-7.907 INITIALIZATION REQUIRES MORE STORAGE

Explanation: Region size is too small.
User Response: Increase REGION size in CA-7 JCL and resubmit.
CA-7.908 SECURITY MODULE FORMAT ERROR, REASSEMBLE

Explanation: Format of security module is invalid. Internal controls for the operator IDs are in
error.
User Response: Correct and reassemble the security module in error or use another security
module. If the problem persists, contact your installation's CA-7 specialist.
CA-7.909 INITIALIZATION REQUIRES MORE CORE TO LOAD RESIDENT MODULES - U0909

Explanation: Core required to load CA-7 resident modules is not available. Issued by SASSLDDL.
User Response: Increase REGION size in CA-7 JCL and resubmit the job.
CA-7.910 ILLEGAL CARD OR SEQ. ERROR IN INIT DECK

Explanation: An invalid statement or a sequence error has been found in the CA-7 initialization
file. The statement in error will be listed following the message. Issued by SASSICRD.
User Response: Review the initialization file documentation and make all necessary changes.
CA-7.910 MASTER LTERM SPECIFICATION OMITTED

Explanation: One terminal must be defined as MASTER.
User Response: Define and resubmit.
CA-7.910 CUST,ID= STATEMENT IS REQUIRED

Explanation: A CUST statement with an ID parameter is required.
User Response: Provide the statement and resubmit.

CA-7.911 –CA-7.914
CA-7.911 VTNAME SPECIFIED BUT NOT USED

Explanation: A UCC7VTAM statement was provided, but no terminals were defined to use
VTAM.
CA-7.912 DDNAME UCC7IN FAILED OPEN

Explanation: An error occurred trying to open the UCC7IN data set.
User Response: Probable DD statement error. Correct and resubmit.
CA-7.912 DDNAME UCC7OUT FAILED OPEN

Explanation: An error occurred trying to open the UCC7OUT data set.
User Response: Probable DD statement error. Correct and resubmit.
CA-7.913 NETWORK TYPE CONFLICTS WITH GROUP STATEMENT

Explanation: The type of terminals defined in a GROUP statement disagrees with the NETWORK
value in the RESIDENT statement.
CA-7.914 GROUP COUNT CONFLICTS WITH RESIDENT NLGRP VALUE

Explanation: A logic error has occurred with GROUP statement processing.
CA-7.914 LINE COUNT CONFLICTS WITH RESIDENT NLINE VALUE

Explanation: A logic error has occurred with LINE statement processing.
CA-7.914 LOCATE FAILED FOR JCL DATA SET x...x

Explanation: The data set name specified in the JCL statement in the CA-7 initialization file is not
cataloged and no VOLSER parameter was given. Issued by SASSINWC.
User Response: Catalog the JCL data set or provide a VOLSER parameter.
CA-7.914 NUMBER OF xxxxxxxx CONFLICTS WITH RESIDENT SPECIFICATION

Explanation: The xxxxxxxx will either be GROUPS, LINES or TERMS. The message indicates
that the number of groups, lines or terminals (defined with statements in the initialization file) disa-
grees with the number specified on the RESIDENT statement. Issued by SASSICRD.
User Response: Correct the initialization file so that the number of GROUP, LINE and TERM
statements match the number given in the RESIDENT statement.
Chapter 4. CA-7.000 - CA-7.999 4-53

CA-7.914 –CA-7.919
CA-7.914 TERM COUNT CONFLICTS WITH RESIDENT NLTERM, NLPRT SUM

Explanation: A logic error has occurred with TERM statement processing.
CA-7.915 RDJFCB FAILED FOR JCL DATA SET ON VOL xxxxxx

Explanation: The volume indicated by xxxxxx is not defined with a DD statement in the CA-7
execution JCL. This prevented CA-7 from accessing a JCL data set on that volume. Issued by
SASSINWC.
User Response: Add a DD statement to the CA-7 JCL defining the volume. It will be necessary to
reinitialize CA-7 before the volume will be accessible.
CA-7.916 DSN x...x NOT ON VOL volume

Explanation: The format-1 label for the JCL data set indicated by x...x could not be found on the
volume indicated. Issued by SASSINWC.
User Response: Verify the system catalog entry and the VOLSER specified to CA-7. Make any
necessary corrections.
CA-7.917 JCL DATA SET(S) INVALID

Explanation: Error(s) were detected in the JCL statement(s) in the initialization file. Issued by
SASSINWC.
User Response: Correct the error(s) and resubmit the CA-7 job.
CA-7.918 TERMINAL - xxxxxxx HAS NO LTERM DESIGNATED.

Explanation: A TERM statement was found in the initialization file without a corresponding
LTERM designated in the STATIONS statement. Issued by SASSINTP. CA-7 will abend with a
U0918 code following this message.
User Response: Verify that there is a STATIONS statement in the initialization file for the TERM
xxxxxx, check that all STANIDS are unique, and that continuation statements are coded properly.
Refer to the CA-7 Systems Programmer Guide for the correct coding.
CA-7.919 TERMINAL - xxxxxxx HAS NO OPERATOR ID DESIGNATED

Explanation: A TERM statement for a terminal that can receive input was found in the initializa-
tion file without a corresponding operator from the module identified by the SECURITY statement.
Issued by SASSINTP.
User Response: Specify at least one operator as valid to use each terminal defined for input. Refer
to the SECURITY macro definition in the CA-7 Systems Programmer Guide.

CA-7.920 –CA-7.925
CA-7.920 I/O ERROR FORMATTING xxxxxxx

Explanation: An error occurred while formatting the queue identified by xxxxxxx. Issued by
SASSINIO.
User Response: Have dump and system log available when contacting Computer Associates Tech-
nical Support.
CA-7.921 DEVICE NOT SUPPORTED - U0921

Explanation: The DAIO statement in the CA-7 initialization file has an invalid device specification.
Issued by SASSINIO.
User Response: Specify a correct device type and resubmit. Refer to the CA-7 Systems Pro-
grammer Guide for valid device types.
CA-7.922 INITIALIZATION REQUIRES MORE CORE - U0922

Explanation: Core allocated for CA-7 has been exceeded by initialization. Issued by SASSINIO.
User Response: Increase the REGION size in the CA-7 JCL.
CA-7.923 INVALID SCT - SASSDAIO NOT FOUND - U0923

Explanation: The SCT control block for SASSDAIO could not be found. Issued by SASSINIO.
CA-7.924 QUEUE FORMAT INCORRECT - xxxxxxxx - U0924

Explanation: The queue specified by xxxxxxxx is not in the format expected by CA-7. The data
on the pack on which the queue resides may have been compressed, or the queue may have been
moved. Another symptom may be that CA-7 abended with a U0710 earlier, indicating an I/O error
in the queue. Issued by SASSINW3.
User Response: If any of the queues have been moved, a FORM start will be required. If not, a
COLD start may resolve the problem. If unable to initialize CA-7 with a COLD start, formatting of
the queues affected will be necessary. Refer to the CA-7 Systems Programmer Guide on recovery
aids which may be used to help to rebuild the queues.
CA-7.925 LOG DATASET AREAS INITIALIZED

Explanation: The buffers and control blocks for the Log data sets have been initialized. Issued by
SASSINLG.
CA-7.925 QUEUE xxxxxxxx NOT DEFINED IN INIT DECK - U0925

Explanation: The name of the queue file not defined in the CA-7 initialization file is indicated by
xxxxxxxx. Issued by SASSINW3.
User Response: Check the FORMAT statements in the initialization file, make any necessary cor-
rections, and then resubmit the CA-7 job.
Chapter 4. CA-7.000 - CA-7.999 4-55

CA-7.926 –CA-7.929
CA-7.926 I/O ERROR OR UNEXPECTED EOD ON QUEUE xxxxxxxx - U0926

Explanation: The name of the queue where an I/O error or unexpected end-of-data (EOD) was
encountered is indicated by xxxxxxxx. Issued by SASSINW3.
CA-7.926 NO CORE FOR LOG DCB AND BUFFERS

Explanation: Insufficient core was available for initialization of the Log data set work areas.
Issued by SASSINLG.
User Response: Increase the REGION size (in the CA-7 JCL) and resubmit the job to initialize
CA-7.
CA-7.927 LOG NOT ACTIVE

Explanation: The ALOG1/ALOG2 statements were omitted from the initialization file. No logging
will occur. Issued by SASSINLG.
User Response: If logging is desired, CA-7 must be shut down, the ALOG1/ALOG2 statements
added to the initialization file, and then CA-7 brought back up.
CA-7.927 UNABLE TO INVERSE PURGE TRACK CELL - U0927

Explanation: A problem was encountered in trying to reconstruct the queues during a WARM or
ERST start. Normally, this will be due to a queue file having been moved prior to the attempted
initialization. Issued by SASSINW3.
User Response: If the error occurred during a WARM start, then try ERST. If the error is in the
Scratch queue or Disk Queue Table queue, then ERST should resolve the problem. If ERST does
not work, contact your installation's CA-7 specialist for assistance. Refer to CA-7.INW3.
CA-7.928 LOG DATASET [(CLOSED)|(OPENED)]

Explanation: A Log data set has been successfully opened or closed. This occurs when the logs
are swapped and at CA-7 shutdown time. Issued by SASSBTMG.
CA-7.928 xxxxxxxx HAS nnnnnn AVAILABLE TRACKS.

Explanation: The queue file indicated by xxxxxxxx has the number of available tracks indicated in
the message text. This is an information message issued for WARM starts and emergency restarts
(ERSTs). Issued by SASSINW3.
CA-7.929 SASSINW3 REQUIRES MORE CORE FOR INITIALIZATION

Explanation: More core is required by the initialization module SASSINW3. Issued by
SASSINW3.
User Response: Increase the REGION size in the CA-7 execution JCL and resubmit the job.

CA-7.930 –CA-7.936
CA-7.930 TERMINAL CONTROL BLOCK INVALID - U0930

Explanation: Invalid information was specified on a TERM statement in the CA-7 initialization
file. If remote BTAM terminals (3270R) are being used, the LINE statement in the initialization file
probably contains an error. Issued by SASSINTP.
User Response: For 3270Rs, all terminal names with the same control unit addresses (first two
bytes of ADRCHR) must be contiguous in the TNAME parameter of the LINE statement. Correct
the error and resubmit.
CA-7.931 BLDL FAILED FOR MODULE NAME - xxxxxxxx

Explanation: The module specified by xxxxxxxx is not on the CA-7 Load library or an I/O error
has occurred. Issued by SASSINTP.
User Response: Verify that the module was not inadvertently deleted from the Load library. If
present, contact your installation's CA-7 specialist for assistance.

Explanation: The core allocated for initialization has been exceeded. Issued by SASSINTP.
CA-7.933 NO SCRATCH QUEUE SPACE....ALL MESSAGES PURGED

Explanation: CA-7 previously abended with all the Scratch queue space allocated (usually a U305
abend). All purged Scratch queue space is released, all messages are queued and scratch work areas
(active areas) are allocated at the time CA-7 came down last. Issued by SASSINW3.
CA-7.934 UNRECOVERABLE ERROR DURING QUEUE UNLOAD

Explanation: An unrecoverable error was detected while attempting to unload the CA-7 queue files.
This message will cause a U0934 abend. Issued by SASSINQD.
User Response: A WTO of INQD-xx will be issued. Refer to that message for the required action.
Do not attempt to start CA-7 with a MOVQ startup. CA-7 can be started with a TYPE=WARM or
ERST.
CA-7.935 UNRECOVERABLE ERROR DURING RELOAD

Explanation: An unrecoverable error was found during the CA-7 queue reload function. This
message will cause a U0935 abend. Issued by SASSINQB.
CA-7.936 QUEUES SUCCESSFULLY RELOADED

Explanation: The CA-7 queues have been successfully reloaded. Issued by SASSINQB.
Chapter 4. CA-7.000 - CA-7.999 4-57

CA-7.937 –CA-7.943
CA-7.937 QUEUES SUCCESSFULLY UNLOADED

Explanation: The CA-7 queues were successfully unloaded. Issued by SASSINQD.
CA-7.938 VRM ACTIVE RESOURCE RECORDS RELOADED

Explanation: The VRM active resource records found on the CA7VDMP dump queue file were
successfully reloaded.
CA-7.939 NO xxx ACTIVE RESOURCE RECORDS RELOADED

Explanation: CA-7 produces this message when ARF or VRM (indicated by the xxx) records are
being reloaded during a MOVQ operation. This message indicates no such records were found in the
input data to be reloaded.

Explanation: The core allocated for initialization has been exceeded. Issued by SASSINWC.
CA-7.941 HIJBNUM CANNOT BE CHANGED

Explanation: An attempt was made to change the highest allowable CA-7 job number (defined by
the HIJBNUM parameter of the initialization file SCHEDULE statement) during a WARM start or
emergency restart (ERST). This change is not valid except during cold type starts. COLD, MOVQ
or FORM. Issued by SASSINW2.
User Response: Reset HIJBNUM back to the original value or do a cold type start.
CA-7.942 NUMBER OF STATIONS CANNOT BE CHANGED

Explanation: An attempt was made to change the number of stations or logical terminal names
prior to initializing CA-7 with a WARM start. STATION statement changes require an ERST start
of CA-7. Issued by SASSINW2.
User Response: If STATION statement changes are required, an ERST or COLD start initialization
of CA-7 is necessary.
CA-7.943 ERROR READING NAT CHECKPOINT RECORD

Explanation: The Checkpoint record for the CA-7 Job Number Allocator Table could not be read
during initialization. Issued by SASSINW2.
User Response: A COLD start initialization of CA-7 must be done. If the Checkpoint data set has
been moved, it must be on the same device type with the queue data sets.

CA-7.944 –CA-7.949
CA-7.944 ERROR READING LTERM CHECKPOINT RECORD

Explanation: The logical terminal checkpoint record could not be read during initialization. Issued
by SASSINW2.
User Response: A COLD start initialization of CA-7 must be done. If the Checkpoint data set has
been moved, it must be on the same device type with the queue data sets.
CA-7.945 STATION NAME CANNOT CHANGE

Explanation: An attempt was made to change a station name or logical terminal name (defined by
the STANIDS parameter on the STATION statement in the initialization file) prior to a WARM start
of CA-7. Issued by SASSINW2.
User Response: If a station name or logical terminal name must be changed, it will be necessary to
do an ERST start initialization of CA-7.
CA-7.946 PREMATURE END DURING STATION MERGE

Explanation: An error was encountered while verifying that the station and logical terminal names,
specified in the initialization file, agreed with the contents of the Checkpoint record. Issued by
SASSINW2.
User Response: An ERST start should be attempted. If that fails, then a COLD start must be done.
CA-7.947 ERROR READING CHECKPOINT ID RECORD

Explanation: An unrecoverable I/O error occurred while reading the Checkpoint ID record during
User Response: A FORM start initialization of CA-7 must be done. If the Checkpoint data set or
one or more of the queue files has been moved, they must all reside on the same device type. The
Checkpoint data set must be allocated as one cylinder on a cylinder boundary.
If CA-7 was just taken down with a /SHUTDOWN,DMPQ then a MOVQ can be done instead of a
FORM start.
CA-7.948 ERROR READING CHECKPOINT RECORD

Explanation: An unrecoverable I/O error occurred while reading the Checkpoint record during
User Response: A FORM start initialization of CA-7 must be done. If the Checkpoint data set has
been moved, it must be on the same device type as the queues. The Checkpoint data set must be
allocated as one cylinder on a cylinder boundary.
If CA-7 was just taken down with a /SHUTDOWN,DMPQ then a MOVQ can be done instead of a
FORM start.
CA-7.949 WARM START ASSUMED

Explanation: This message indicates that a WARM start of CA-7 is possible and will be performed
even though emergency restart (ERST) was specified. Issued by SASSINW0.
Chapter 4. CA-7.000 - CA-7.999 4-59

CA-7.950 –CA7.955
CA-7.950 EMERGENCY RESTART ASSUMED

Explanation: This message indicates that an emergency restart (ERST) of CA-7 is necessary and
will be performed even though a WARM start was specified. Issued by SASSINW0.
CA-7.950 DDNAME xxxxxxxx NOT DEFINED - U0950

Explanation: The ddname xxxxxxxx for one of the CA-7 database data sets is not in the CA-7
JCL. Issued by SASSINDB.
User Response: Add the proper DD statement and resubmit.
CA-7.951 I/O ERROR READING DSN DIRECTORIES - U0951

Explanation: An I/O error occurred while attempting to read a database directory. Database may
not have been initialized using CDSI program. Issued by SASSINDB.
User Response: If error recurs, contact your installation's CA-7 specialist for assistance. If this is a
new installation, run job N030 from stage II installation and retry.

Explanation: The core allocated for initialization has been exceeded. Issued by SASSINDB.
CA-7.953 DATA SET INIT ERROR - U0953

DATA SET ZERO RECORD NOT FOUND FOR TYPE xx
Explanation: Unable to initialize one of the CA-7 database data sets. Control records were not
found on the Dataset data set. Type is DS, NW, PP, SI, SJ or SO. Data set may not have been
properly initialized. Issued by SASSINDB.
User Response: If data set was not initialized, use CDSI to do so; otherwise, use SASSBK00 to
backup and reload the database.
CA-7.954 DATA SET FAILED OPEN - DDNAME= xxxxxxxx - U0954

Explanation: The data set defined by ddname xxxxxxxx failed OPEN. Issued by SASSINDB,
SASSINWC.
User Response: Verify that the ddname is present in the CA-7 JCL. If the required DD statement
is present, contact your installation's CA-7 specialist for assistance.
CA7.955 VTAM ACB FAILED OPEN DURING INIT

Explanation: During CA-7's initialization, an attempt was made to open the VTAM ACB specified
on the UCC7VTAM statement in the initialization file. The open was not successful.
User Response: Verify that the ACB (APPL) for CA-7 is defined correctly to VTAM and that it is
active. After verifying the ACB, issue the command /OPEN,GROUP=(the first VTAM group in the
initialization file) from a non-VTAM CA-7 terminal to enable VTAM access to CA-7.

CA-7.955 –CA-7.959
CA-7.955 ALLVSAM ERROR ATTEMPTING TO INIT/CONN, RC=xxxx

Explanation: Errors occurred while attempting to connect or disconnect from the database. RC
value gives an error code which is further explained by WTO messages. Issued by SASSINDB.
CA-7.956 UNABLE TO LOAD xxxxxxxx - U0956

Explanation: VSAM/VTAM initialization is unable to load the module specified by xxxxxxxx.
Issued by SASSINVS, SASSINVT.
User Response: Verify the module exists on a CA-7 Load library.
CA-7.957 INITIALIZATION REQUIRES MORE CORE - U0957.

Explanation: Self-explanatory. Issued by SASSINVS, SASSINVT.
CA-7.958 INVALID SHOWCB RETURN CODE - U0958

Explanation: The SHOWCB issued during CA-7 initialization has received a nonzero return code.
Register 15 at the time of abend contains the return code. Issued by SASSINVT.
CA-7.958 INVALID VSAM SHOWCB RET CODE (xx) - U0958

Explanation: The SHOWCB issued during CA-7 initialization has received a nonzero return code.
Register 15 at the time of abend contains the return code which appears as xx in the message. Issued
by SASSINVS.
CA-7.958 GENCB ERROR - R15=xx , R0=yyy

Explanation: The GENCB macro failed while attempting to generate VTAM control blocks. CA-7
terminates with a ***HP2 U0958*EHP abend. Issued by SASSINVT.
User Response: Consult either the IBM manual OS/VS Virtual Storage Access Method (VSAM) Pro-
grammers Guide (GC26-3838) for the topic on GENCB errors or the IBM manual ACF/VTAM Macro
Language Reference Manual (SC38-0261) for the values of xx and yyy. Correct the error indicated
by the codes from the message, then retry. If the problem persists, contact Computer Associates
Technical Support.
CA-7.959 INVALID SASSDBMG (VSAM) ECFLIST - U0959

Explanation: CA-7's database manager ECFLIST control block is invalid for the Index data set.
Issued by SASSINVS.
Chapter 4. CA-7.000 - CA-7.999 4-61

CA-7.959 –CA-7.966
CA-7.959 INVALID SASSLMGR ECFLIST - U0959

Explanation: CA-7's line manager ECFLIST control block is invalid. Issued by SASSINVT.
CA-7.960 VTAM ID TABLE ERROR - U0960

Explanation: The VTAMID (node name) table built during initialization is not large enough.
Issued by SASSINVT.
CA-7.960 CHECKPOINT DATA SET FAILED OPEN - U0960

Explanation: Self-explanatory. Issued by SASSINCM.
User Response: Verify that the UCC7CKPT DD statement is in the CA-7 JCL.
CA-7.961 BLDL FAILED FOR MODULE NAME - xxxxxxxx - U0961

Explanation: This is a warning message unless a U0961 dump is produced. The BLDL failed for a
module, calendar block, or format blocks specified by an APPLCTN, FMTBLK or CALBLK initial-
ization file statement. The module should exist in the CA-7 Load library. Issued by SASSINAP.
User Response: Contact your installation's CA-7 specialist for assistance to ensure that missing
modules should not, in fact, be present.
CA-7.962 CA-7 REGION SIZE IS TOO SMALL - U0962

Explanation: Self-explanatory. Issued by SASSINAP.
CA-7.964 APPLCTN CARD MISSING FOR SASSxxxx

Explanation: The APPLCTN statement for the specified program module has been omitted from
the CA-7 initialization file. Issued by SASSINAP.
User Response: Add the missing APPLCTN statement to the initialization file or to the
SASSPROG module and reinitialize CA-7. If the xxxx does not refer to a valid name (for example,
contains blanks or special characters), then check the SASSTRAN load module.
CA-7.965 UID/RESOURCE TABLE LOADED - xxxxxxxx

Explanation: This message is issued during CA-7 initialization after loading the UID Resource
Table specified on the SECURITY statement, with the UID= parameter in the CA-7 initialization file.
CA-7.966 WORKLOAD BALANCING MODULE LOADED - UCC7Rxxx

Explanation: This message indicates that the Workload Balancing module UCC7Rxxx was loaded
as a default during CA-7 initialization. This message is informational only. Issued by SASSIOPT.

CA-7.967 –CA-7.972
CA-7.967 STORGAGE UNAVAILABLE FOR WLB MODULE - UCC7Rxxx

Explanation: An attempt was made to load a default Workload Balancing module UCC7Rxxx
during CA-7 initialization; however, the storage was not available. Issued by SASSIOPT.
User Response: Ensure that the module name specified on the CA-7 initialization file OPTIONS
statement, keyword DFLTWLB= is a valid Workload Balancing module. If the module is valid,
CA-7.968 WLB MODULE NAME FORMAT INCORRECT

Explanation: An attempt was made to load the Workload Balancing module UCC7Rxxx during
CA-7 initialization; however, the module name format was incorrect.
User Response: Workload Balancing modules have a naming requirement of UCC7Rxxx where xxx
can be specified by the user. Check the name specified on the OPTIONS statement, keyword
DFLTWLB= in the CA-7 initialization file.
CA-7.969 WLB MODULE NOT FOUND - UCC7Rxxx

Explanation: An attempt was made to load the Workload Balancing module UCC7Rxxx during
CA-7 initialization; however, the module was not found.
User Response: Ensure that the Workload Balancing module name is correct and that the module
resides in a Load library accessible by CA-7 during startup.
CA-7.970 DATE/TIME OR REPLY INVALID

Explanation: An error occurred while attempting to validate date/time values or an unknown value
was replied to the CA-7.973 WTOR. Issued by SASSINW0.
User Response: If CA-7.973 was not produced, disable the VALIDATE option in the initialization
file and retry.
If CA-7.973 was produced, it will be reissued. Refer to CA-7.973 for valid replies.
CA-7.971 LAST SSCAN - yy.ddd/hh:mm, LAST CKPT - yy.ddd/hh:mm:ss

Explanation: Date/time validation was requested and checkpoint information is outside the
requested range. This WTO will be followed by a request to verify system date and time. Issued by
SASSINW0.
CA-7.972 CURRENT SYSTEM DATE/TIME - yy.ddd/hh:mm:ss

Explanation: As part of date/time validation, the system values are displayed. Issued by
SASSINW0.
Chapter 4. CA-7.000 - CA-7.999 4-63

CA-7.973 –CA-7.978
CA-7.973 DATE/TIME VERIFICATION NECESSARY, REPLY.

'U' TO PROCEED OR
'NOSCAN' TO DISABLE SSCAN
Explanation: Date/time validation was requested and verification is required to continue startup.
Issued by SASSINW0.
User Response: Verify the system date and reply with one of the values indicated or cancel CA-7.
If system date as noted in CA-7.972 is correct and CA-7.971 was not produced, reply with U. If
system clock is incorrect, reset the date and time and then reply U. If in doubt or values in
CA-7.971 are questionable, reply NOSCAN and use the SSCAN command to establish scheduling
values for schedule scan after initialization.
CA-7.974 SCHEDULE SCAN HAS BEEN DISABLED

Explanation: NOSCAN was replied to CA-7.973. Issued by SASSINW0.
User Response: None. CA-7 will initialize without automatic scheduling. Use the SSCAN
command after CA-7 is initialized to set scheduling values for CA-7.
CA-7.975 READ ERROR ON CHECKPOINT TAT FOR xxxxxxxx QUEUE - U0975

Explanation: An unrecoverable I/O error occurred while attempting to read the checkpoint track
allocator table for the queue data set specified by xxxxxxxx. Issued by SASSINW1.
User Response: A COLD start initialization of CA-7 must be done. When a TYPE=COLD is
specified, the initialization file FORMAT statement for the queue in error must specify DISP=F. For
TYPE=FORM, no initialization file changes are needed.
CA-7.976 TRACK ALLOCATOR TABLE ERROR FOR QUEUE xxxxxxxx - U0976

Explanation: The checkpoint track allocator table for the queue specified by xxxxxxxx is invalid
for the queue data set currently referenced by the CA-7 JCL. Probable cause is changing queue data
set allocation without doing a FORM (or MOVQ) type of initialization of CA-7. Issued by
SASSINW1.
User Response: A FORM (or MOVQ) type of initialization of CA-7 must be done if the specified
queue has been reallocated. If the original queue is available, change the JCL to point to this data
set and do a WARM start initialization of CA-7. If a queue data set must be reallocated, shut down
CA-7 with a DMPQ and reinitialize with a MOVQ after the queue reallocation.
CA-7.977 SASSINW1 REQUIRES MORE CORE FOR INITIALIZATION - U0977

Explanation: The module does not have sufficient core for initialization. Issued by SASSINW1.
User Response: Increase the REGION size on the CA-7 execute statement and reattempt the initial-
ization.
CA-7.978 PRIOR RUN QUEUE IS BEING REUSED

Explanation: This message indicates that the Prior-run queue has been reinitialized and all data
previously collected by CA-7 has been scratched. Issued by SASSINW1.

CA-7.979 –CA-7.984
CA-7.979 UCC7TRLQ TAT INVALID FOR PRIOR RUN QUEUE - U0979

Explanation: The Trailer queue Track Allocator Table (TAT) is in error or the Trailer queue was
not defined in the initialization file. When the Prior-run queue is reinitialized and found to be avail-
able from the previous CA-7 execution, the Trailer queue must also be available. If the Trailer queue
has been reformatted, the Prior-run queue must also be reformatted. Issued by SASSINW1.
User Response: Specify the Trailer queue in the initialization file if it was missing. If not, specify
DISP=F for the Trailer queue and Prior-run queue and do a COLD start of CA-7 to reformat these
queues. A FORM start could also be done.
CA-7.980 xxxxxxxx DD SET UP FOR SUBMIT

Explanation: The Submit data sets have been set up and are ready to receive jobs. This message
will appear for each Submit data set. Issued by SASSINCM.
CA-7.981 xxxxxxxx DATA SET FAILED OPEN

Explanation: The data set specified by xxxxxxxx could not be opened. Issued by SASSINCM.
User Response: Verify that the DD statement is present and correct in the CA-7 JCL. If the
message is for the COMM data set, make sure it is allocated on a device type that is supported.
Note: For the Submit data set the file must be one contiguous extent. DCB attributes for the data
set must be: DCB=(RECFM=F,BLKSIZE=80,LRECL=80).
CA-7.982 xxxxxxxx DATA SET FAILED CLOSE

Explanation: The data set specified by xxxxxxxx could not be closed. Issued by SASSINCM.
CA-7.983 xxxxxxxx - NO CORE FOR DATA SET

Explanation: The Submit data set specified by xxxxxxxx could not be established due to insuffi-
cient core. Issued by SASSINCM.
CA-7.984 xxxxxxxx - SUBMIT DATA SET NOT AVAILABLE

Explanation: The Submit data set specified by ddname xxxxxxxx could not be found in the CA-7
JCL. CA-7 will be unable to submit JCL to this data set. The ddname is defined in the CA-7
initialization file with a CPU statement. Issued by SASSINCM.
User Response: To submit jobs to this data set, CA-7 must be shut down, the appropriate DD
statement added to the JCL and CA-7 reinitialized. If submission to that data set is not required, the
CPU statement defining the ddname may be changed (or omitted) prior to the next initialization of
CA-7.
Chapter 4. CA-7.000 - CA-7.999 4-65

CA-7.985 –CA-7.992
CA-7.985 CPU SUBMIT CONTROL TABLE NOT ACTIVE

Explanation: The CPU statement(s) was omitted from the initialization file or the RUNOPT field of
the INIT statement specified MAINT or REPT. No submitting will be done by CA-7. Issued by
SASSINCM.
User Response: If submitting is desired, the CPU statement(s) must be added to the initialization
file and CA-7 must be restarted with a RUNOPT other than REPT or MAIN.
CA-7.986 COMMUNICATION DATA SET IS NOT ACTIVE

Explanation: The Communications data set will not be used by CA-7. This is because of initializa-
tion with RUNOPT=REPT in the INIT statement in the CA-7 initialization file. Issued by
SASSINCM.
CA-7.987 MAINT OR REPT RUN - NO SUBMIT

Explanation: RUNOPT=MAIN or REPT was specified on the INIT statement in the initialization
file. No jobs will be submitted by CA-7. Issued by SASSSJC0.
User Response: If submission is desired, the initialization file must be changed and CA-7 must be
reinitialized.
CA-7.988 CA-7 MUST RUN APF AUTHORIZED - U0988

Explanation: This message is produced during CA-7 startup if one or more of the libraries in the
CA-7 STEPLIB concatenation are not APF authorized. CA-7 abends with a user 988 immediately
following this message.
User Response: Ensure all libraries in the CA-7 STEPLIB concatenation are APF authorized and
restart CA-7.
CA-7.990 SCT CHAIN IS INCORRECT - U0990

Explanation: Invalid System Control Table (SCT) chain. Issued by SASSNUC.
CA-7.991 BLDL/SLOAD FAILED FOR SASSLINK.

Explanation: An I/O error occurred or SASSLINK is not on a CA-7 Load library. Issued by
SASSNUC.
User Response: Check the CA-7 load library for the SASSLINK module. Contact Computer Asso-
CA-7.992 INITIALIZATION DESTROYED SCT CHAIN - U0992

Explanation: The SCT chain set up during initialization is not valid. Issued by SASSNUC.

CA-7.993 –CA-7.999
CA-7.993 CA-7 INITIALIZATION COMPLETE FOR xxxx

Explanation: Central Control System CA-7 initialization successfully completed. The value for
xxxx will indicate the subsystem name for the production (UC07) or test (UCT7) copy of CA-7.
Issued by SASSNUC.
CA-7.994 STORAGE POOLS NEED MORE STORAGE.

Explanation: Pool specifications are too large for REGION size. Issued by SASSNUC. CA-7 will
abend with a U0994 code following this message.
User Response: Increase REGION size or reduce the CWORK value.
CA-7.995 CA-7 Load library FAILED TO OPEN.

Explanation: Unable to open CA-7 Load library, possibly because of missing STEPLIB statement.
Issued by SASSNUC.
User Response: Check JCL and add a STEPLIB DD pointing to CA-7's Load library. The ddname
must be STEPLIB.
CA-7.996 STAE EXIT COULD NOT BE ESTABLISHED - U0996

Explanation: A STAE exit could not be set up during CA-7 initialization. Issued by SASSNUC.
CA-7.997 INVALID PARM DATA.

Explanation: Invalid PARM data has been specified in the CA-7 JCL. Issued by SASSNUC.
User Response: Verify the PARM values. Make any necessary corrections and resubmit the job.
CA-7.998 INITIALIZATION DECK EDIT COMPLETE

Explanation: Editing of the initialization file has completed without detecting any errors. Issued by
SASSNUC.
CA-7.999 EXTERNAL SECURITY REQUIRES LOGON

Explanation: Issued by SASSINAP when EXTERNAL= parameter detected but LOGON not speci-
fied. LOGON control is a prerequisite for any use of external security.
User Response: If external security is to be used include LOGON in the EXTERNAL= sublist on
the SECURITY statement.
Chapter 4. CA-7.000 - CA-7.999 4-67

CA-7.999 –CA-7.999
CA-7.999 UNABLE TO EXTRACT GLOBAL ID

Explanation: The CA-7 initialization file indicated that external security control was requested and
CAS9 SSF services failed to extract the USERID associated with CA-7. This message may be issued
if the external security system (for example, CA-ACF2, CA-Top Secret, or IBM RACF) is not active.
Modules involved in detecting and reporting this condition include SASSINAP, SASSXSEC and
CAS9SEC.
User Response: If EXTERNAL=(LOGON,...) is specified on the SECURITY statement in the CA-7
initialization file then ensure that the security system is active and restart CA-7.

Chapter 5. CDSI - RSCx
This chapter contains the CDSI through RSCx messages.
Chapter 5. CDSI - RSCx 5-1

5.1 CDSI Messages
CDSI-00 –CDSI-14
5.1 CDSI Messages
CDSI-00 INITIALIZATION COMPLETE.

nnnnnn SMF RECORDS nnnnnn TRAILER RECORDS
Explanation: The Communications data set has been successfully initialized. The number of SMF
records and trailer records created are indicated by nnnnnn.
Note: These are 1024-byte blocks and each block may contain multiple logical records.
CDSI-10 UCC7CMDS DD STATEMENT MISSING

Explanation: The DD statement defining the Communications data set was omitted from the initial-
ization JCL.
User Response: Add the required DD statement and resubmit the job.
CDSI-11 TOO MUCH INPUT DATA

Explanation: The number of *CPU* statements specified exceeds 11, which is the maximum per-
mitted.
User Response: Reduce the number of *CPU* statements to no more than 11 and resubmit the job.
CDSI-12 REQUIRED INPUT MISSING

Explanation: The first statement in the input stream must be *CDSINIT* and there must be at least
one *CPU* statement.
User Response: Correct the input data and resubmit the job.
CDSI-13 INVALID INPUT CARD

Explanation: The error is due to one of the following:
1. The first statement was not *CDSINIT*.
2. One of the statements following the *CDSINIT* was not a *CPU* statement.
3. A *CPU* statement had a blank in the first position of the ddname.
User Response: Correct the statement(s) in error and resubmit the job.
CDSI-14 INVALID NUMERIC DATA

Explanation: The trailer records value specified on the *CDSINIT* statement was invalid.
User Response: Correct the error and resubmit the job.

5.1 CDSI Messages
CDSI-15 –CDSI-32
CDSI-15 ICOM DATA SET TOO SMALL

Explanation: Not enough space was allocated for the Communications data set.
User Response: Increase the space allocation. Resubmit the job.
CDSI-16 ICOM DATA SET MUST BE SINGLE EXTENT

Explanation: The Communications data set was not allocated a single, contiguous extent.
User Response: Scratch and reallocate the data set with CONTIG specified in the JCL.
CDSI-21 UCC7STAT DD STATEMENT MISSING, STAT FILE NOT FORMATTED

Explanation: Self-explanatory.
User Response: None, unless STAT file formatting is desired, in which case add the UCC7STAT
DD statement and resubmit the job. This data set must be initialized before CA-7 is initialized for
the first time. After that, initialization of the Statistics data set should not be necessary.
CDSI-22 DATASET DATA SET CONTROL MEMBER FOUND BUT NOT REFORMATTED
Explanation: Initialization attempted for Dataset data set but control members were already there.
User Response: If reinitializing Dataset data set, scratch and reallocate the data set. Otherwise,
remove the UCC7DLIB DD statement from the execution JCL.
CDSI-31 ALLVSAM ERROR ATTEMPTING INIT/CONN/DISCON/FINISH, RC=xxxx

Explanation: Errors occurred while attempting to initialize, connect, disconnect or finish with an
CDSI-32 ALLVSAM ERROR ON DSDS, RC=xxxx

Explanation: Logic or I/O error occurred while accessing data set directory type entries. RC value
gives error code and WTO message gives specifics on error.

5.2 DPCH Messages
DPCH-01 –DPCH-06
5.2 DPCH Messages
This subsection contains the CA-7 DPCH messages. The messages are produced by
SASSDPCH. Each message is accompanied by a return code.
DPCH-01 FWLPDATA SET OPEN FAILURE

Explanation: An OPEN error occurred for ddname FWLPDATA. Probable missing or incorrectly
spelled ddname in the DD statement. A condition code of 8 is set.
User Response: Provide a correct DD statement and retry.
DPCH-02 DISPATCH DATA SET OPEN FAILURE

Explanation: An OPEN error occurred for ddname DISPATCH. Probable missing or incorrectly
spelled ddname in the DD statement. A condition code of 8 is set.
DPCH-03 NO YYDDD FOUND IN J RECORD

Explanation: The scheduled date, in Julian format, must immediately follow the J (in column 1) of
each record. A J record was found but without a valid 5-digit date in the next 5 positions. Probable
user error. Should not occur if input was provided by an FWLP command. A condition code of 8 is
set.
User Response: Correct the invalid date format and retry.
DPCH-04 DATE CONVERSION ERROR IN SASSHDAT

Explanation: SASSHDAT detected a Julian date error it was to convert to Gregorian format. Prob-
able user error. Should not occur if input was provided by an FWLP command. Should occur only
if a Julian day greater than the maximum for that year is found. A condition code of 8 is set.
User Response: Correct the invalid date and retry.
DPCH-05 ERROR FOUND DURING JOB NAME PROCESSING

Explanation: No job name was found in a J record. Probable user error. Should not occur if input
was provided by an FWLP command. Should occur only if at least one job name character does not
occur in column 9 of the J record. A condition code of 8 is set.
User Response: Correct the invalid job name and retry.
DPCH-06 ERROR FOUND PROCESSING TIME VALUES

Explanation: Did not find valid time fields in a J record. Probable user error. Should not occur if
input was provided by an FWLP command. Should occur only if at least one time value of four
characters is not found or if incorrect termination of the time parameters is found. A condition code
of 8 is set.
User Response: Correct the invalid time fields and retry.

5.2 DPCH Messages
DPCH-07 –DPCH-07
DPCH-07 NO FLWP DATA RECORDS PROCESSED

Explanation: Did not find any valid FWLP records in the FWLPDATA data set. Probably one of
the following user errors:
1. DD statement FWLPDATA pointed to the wrong data set.
2. No jobs were scheduled in the time period requested for the FWLP command issued to create
the data set.
3. A manually provided data set was empty.
A condition code of 4 is set.
User Response: Retry with the correct data set.

5.3 DTxx Messages
DT10-01 –DT10-24
5.3 DTxx Messages
DT10-01 INVALID PARM DATA STARTING WITH x IN POSITION nnn

Explanation: The PARM values contain an error beginning with the character shown in position
nnn of the PARM data. The first position of the PARM data is position 1.
User Response: Correct the error and rerun.
DT10-04 GETMAIN FAILED, CANNOT PROCESS

Explanation: Space for the Job table could not be obtained with the GETMAIN macro.
User Response: Increase the region and retry. If the problem persists, contact your installation's
DT10-08 CANNOT OPEN DDN=DT10CR01

Explanation: An error occurred trying to open the control report data set.
User Response: Examine the DD statement for correct values including the spelling of the ddname
DT10CR01.
DT10-12 CANNOT OPEN DDN=DT10IN

Explanation: An error occurred trying to open the input data set.
DT10IN.
DT10-16 CANNOT OPEN DDN=DT10OUT

Explanation: An error occurred trying to open the output data set.
DT10OUT.
DT10-20 BAD LSYS GROUP END, NOT SLIC-00

Explanation: The SLIC-nn message terminating the output produced for an LSYS command indi-
cates that an error occurred. That is, the nn value is not zero.
User Response: Correct the cause of the nonzero completion message in the previous BTI step and
rerun.
DT10-24 BAD LJOB GROUP END, NOT SLIA-00

Explanation: The SLIA-nn message terminating the output produced for an LJOB command indi-
cates that an error occurred. That is, the nn value is not zero.
User Response: Correct the cause of the nonzero completion message in the previous BTI step and
rerun.

5.3 DTxx Messages
DT10-28 –DT20-01
DT10-28 INTERNAL ERROR PROCESSING A JOB

Explanation: The program sets a flag when it starts to process the data generated by an LSYS
command. Another flag is set on for the processing of an LJOB command. These flags are reset
when their corresponding SLIx-nn termination message is encountered in the input. All other com-
mands will have been ignored. This message indicates the program has reached a point where either
one or the other of the two flags should have been set on but neither was set. It suggests that either
the program code or the input file has been tampered with.
User Response: Establish the integrity of the program code and/or the input data and rerun.
DT10-32 END OF FILE REACHED BUT /LOGON EXPECTED

Explanation: No /LOGON command could be found in the input data set.
User Response: Either the previous BTI step completed abnormally or the wrong data set was used
as input to SASSDT10. Ensure that CA-7 is active when the BTI step is rerun.
DT10-36 END OF FILE REACHED BUT SLIC-00 EXPECTED FOR LSYS GROUP
Explanation: The program reached end-of-file during processing of LSYS command output without
finding the SLIC-nn message which would indicate routine completion of the command. The output
data set being produced will be incomplete. Probably caused by exceeding the capacity of the
Batchout data set during the previous BTI step.
User Response: Increase the allocation for the Batchout data set and rerun the job.
DT10-40 END OF FILE REACHED BUT SLIA-00 EXPECTED FOR LJOB GROUP
Explanation: The program reached end-of-file during processing of LJOB command output without
finding the SLIA-nn message which would indicate routine completion of the command. The output
data set being produced will be incomplete. Probably caused by exceeding the capacity of the
Batchout data set during the previous BTI step.
DT10-44 NUMBER OF JOBS HAS EXCEEDED TABLE CAPACITY

Explanation: The number of unique job names requested exceeds the capacity of the internal job
name table. Refer to the CA-7 Database Maintenance Guide for a discussion of the design limita-
tions for this process.
User Response: Divide the commands into multiple runs or contact your installation's CA-7 spe-
cialist to enlarge the table capacity.


5.3 DTxx Messages
DT20-04 –DT20-28
DT20-04 GETMAIN FAILED FOR TABLES

Explanation: Space for all of the internal tables could not be obtained with the GETMAIN macro.
User Response: Increase the region and retry. If problem persists, contact your installation's CA-7
DT20-08 CANNOT OPEN DDN=DT20CR01

Explanation: An error occurred trying to open the output control report data set.
DT20CR01.
DT20-12 CANNOT OPEN DDN=DT20IN

DT20IN.
DT20-16 CANNOT OPEN DDN=DT20OUT

Explanation: An error occurred trying to open the output data set.
DT20OUT.
DT20-20 INVALID COMMAND IN INPUT

Explanation: SASSDT10 generates LJOB,JOB=xxxxxxxx LIST=mmmm commands in which
mmmm can be either STEPDD, TRIG, or RQMT. Only these three command variants can be
accepted by SASSDT20. Some other command was found in the input data. The control report will
provide an indication as to the last job and variant which was completed. The offending record will
not be printed.
User Response: If the file was corrupted manually, correct the error and rerun. Otherwise, contact

as input to SASSDT20.
DT20-28 END OF FILE REACHED BUT SLIA-00 EXPECTED FOR LJOB GROUP
Explanation: The program reached end-of-file during processing of LJOB command output and
without finding the SLIA-nn message which would indicate routine completion of the command.
The output data set being produced will be incomplete. Probably caused by exceeding the capacity
of the Batchout data set during the previous BTI step.

5.3 DTxx Messages
DT20-32 –DT30-08
DT20-32 NUMBER OF xxxxxxxx HAS EXCEEDED TABLE CAPACITY

Explanation: An internal table capacity has been exceeded. The specific table is indicated by
xxxxxxxx which will be either JOBS, SYSTEMS, NETWORKS, or DATASETS. Refer to the CA-7
Database Maintenance Guide for a discussion of the design limitations for this process.
User Response: Divide the requested workload into multiple smaller groups or contact your instal-
lation's CA-7 specialist to enlarge the table capacities.
DT20-36 WRONG SUBROUTINE ENTERED FOR COMMAND

Explanation: Each submodule tests the first record in the work file to ensure the driver (DT20)
called it correctly. This test will catch logic errors and any errors in accessing the work file. Erro-
neous use of DISP=MOD in the WORKFILE DD statement will also cause this error.
User Response: If the DISP is incorrect, make the necessary correction and rerun. Otherwise,
DT20-40 SUBROUTINE (DT2x) REACHED EOF ON TEMPFILE BUT NO 'SLIA-00'

Explanation: Submodules decrement a record counter (established by the driver SASSDT20) each
time a record is read from the work file. If the count of records left has reached zero when another
record is needed, this error message is generated. This is a probable logic error in the submodule
indicated. (If the DT20IN file did not contain the SLIA-nn message for the group, the driver would
have terminated with message DT20-28.)
DT20-44 FAILED TO OPEN OUTPUT DATASET FILE

Explanation: An error occurred trying to open the Dataset data set.
DATASET.

DT30-04 GETMAIN FAILED FOR TABLES

Explanation: Space for all of the internal tables could not be obtained using the GETMAIN macro.
User Response: Increase the region and retry. If problem persists, contact your installation's CA-7
DT30-08 CANNOT OPEN DDN=xxxxxxxx

Explanation: The xxxxxxxx represents the DDNAME of the file for which the open failed.
User Response: Examine the DD statement for correct values including the spelling of the ddname.

5.3 DTxx Messages
DT30-12 –DT30-40
DT30-12 FAILED TO OPEN INPUT FILE

DBMLISTS.

as input to SASSDT30.
DT30-32 NUMBER OF ENTRIES HAS EXCEEDED CAPACITY OF xxxxxxxx TABLE

Explanation: An internal table capacity has been exceeded. The specific table is indicated by
xxxxxxxx which will be either PROC NAME, JCL MEMBER, INLINEPROC or JCL LIBR. Refer
to the CA-7 Database Maintenance Guide for a discussion of the design limitations for the first three.
The limit for JCL LIBR is 254.
User Response: Divide the requested workload into multiple smaller groups or contact your instal-
lation's CA-7 specialist for assistance in enlarging the table capacities.
DT30-36 WRONG SUBROUTINE ENTERED FOR COMMAND

Explanation: Each submodule tests the first record on the work file to ensure the driver (DT30)
called it correctly. This test will catch logic errors and any errors accessing the work file. Erroneous
use of DISP=MOD on the WORKFILE DD statement will also cause this error.
User Response: If the DISP was incorrect, make the necessary correction and rerun. Otherwise,
DT30-40 SUBROUTINE (DT3xx) REACHED EOF ON TEMPFILE BUT NO 'mmmm-00'

Explanation: The submodules decrement a record counter (established by driver SASSDT30) each
time a record is read from the work file. If the count of records left has reached zero when another
record is needed, this error message is generated. The xx value identifies the submodule which
encountered the error condition. mmmm is the routine completion message prefix which was
expected to be found (for example, SLIA-00). (If the DBMLISTS file had not contained the
'mmmm-00' message, the driver would have generated one in an effort to continue.) This is probably
a logic error in the code.
This error can also result if the Batchout data set in the previous BTI run was too small. In that
case, message BSTR-17 will have been written as the last record. That is, the last record input to the
DT30 step.
User Response: If this did not result from a DASD space problem, contact your installation's CA-7

5.3 DTxx Messages
DT32-01 –DT35-40
DT32-01 DOES NOT RECOGNIZE PROS-TYPE. NO PROSE OUTPUT PROVIDED

Explanation: Submodule SASSDT32 could not find the PROS-TYPE heading in the input. The
message appears on the job SYSOUT listing only. An attempt is made by the driver to continue
with the remainder of the input file. One group of prose should be missing from the DBMADDS1
file for each occurrence of this message. This is a probable system error.
DT33-01 DS NUMBER MISSING FROM LDSN COMMAND -- OUTPUT SUPPRESSED

Explanation: Submodule SASSDT33 found LDSN command output which did not contain a data
set number. Probable system error.
DT34-01 DSORG ERROR - WILL TRY TO TREAT AS PDS, AT SEQ# xxxxxxxx

Explanation: Submodule SASSDT34 encountered a set of JCL for which the JCL library DSORG
value was something other than PDS, LIB or PAN. The program will try to process the data as if it
were PDS and continue. xxxxxxxx is the sequence number in the DBMADDS1 and DT30CR01 files
at which this batch of JCL can be found. Probable system error.
User Response: If the JCL is to be placed in a PDS, none. Otherwise, contact your installation's
DT35-01 JOBNAME MISSING FROM LJOB COMMAND -- OUTPUT IS SUPPRESSED

Explanation: Submodule SASSDT35 found LJOB command output which did not contain a job
name. Probable system error.
DT35-36 SUBMODULE T3xx REJECTS THIS FIRST RECORD

Explanation: The submodule identified in this message expected a particular record when it was
first entered, but that record was not found. Control will be returned to the main driver which will
issue DT30-36 before aborting. Probable system error.
DT35-40 SCAL NOT FOUND, JOB xxxxxxxx, SCHD NOT PROCESSED.

Explanation: Submodule SASST354 could not find the SCAL value while processing a job
schedule. Schedule processing for this job is skipped. The message also appears, followed by a line
of asterisks, on the DT30CR02 control report. Probable system error.

5.3 DTxx Messages
DT36-04 –DT36-40
DT36-04 NO INPUT LEFT FOR NTWK=xxxxxxxx SCHEDULES #2 nnnnnnnn

Explanation: Submodule SASSDT36 could find no schedules defined for the network indicated by
xxxxxxxx in the message. Control report DT30CR02, DATA BASE ADDS - PART 2, will reflect
the last command generated prior to this condition using sequence number nnnnnnnn as indicated.
Probable system error.
DT36-08 TYPE NOT INPUT NOR OUTPT FOR NTWK=xxxxxxxx

Explanation: Submodule SASSDT36 found a TYPE value other than INPUT or OUTPT within the
LNTWK data. Processing for this network is suspended without generating any commands to move
the network. This message also appears, followed by a line of asterisks, on the DT30CR02 control
report. Probable system error.
DT36-36 SUBMODULE T361 REJECTS THIS FIRST RECORD.

Explanation: Submodule SASST361 was given its first record to process and the record was not
the STATION NAMES section of LNTWK data. Control will be returned to the main driver which
will then issue message DT30-36. This is a probable system error.
DT36-40 DELETED WITHOUT ADDING, NW=xxxxxxxx RPT=y LINE=nnnnnnnn

Explanation: Submodule SASST361, having already generated a command to delete the indicated
network at the sending site, did not find the section of data titled SCHEDULES in the LNTWK data.
The value of y indicates the control report and nnnnnnnn indicates the command sequence number
where the condition was found. This message is written twice to SYSOUT to identify control report
and line number in each of the xxxDELTS and xxxADDS1 files where this condition occurred.
Probable system error.

5.4 EDTx Messages
EDTx-00 –EDTx-13
5.4 EDTx Messages
EDTx-00 COMMAND PROCESSED.

Explanation: The text editor command has been successfully processed.
EDTx-01 xx INVALID MACRO CALL RETURN CODE=nn.

Explanation: An unexpected macro return code has been received. xx is the macro location in the
program and nn is the return code from register 15.
EDTx-11 INVALID COMMAND, REENTER

Explanation: An invalid command has been entered. The following are some of the reasons for
invalid commands:
1. An invalid command name.
2. Non-numeric data specified for a numeric parameter.
3. A beginning sequence number greater than an ending sequence number.
4. Invalid or omitted EDIT delimiters.
5. Not enough or too many parameters specified on the command.
6. An invalid value specified for a numeric parameter.
User Response: Review the available commands and parameters, and reenter the command.
EDTx-12 ENTER COMMAND

Explanation: This is an information message displayed when the text editor has been entered from
one of the Database Maintenance functions. It indicates the text editor is available for processing the
Edit Work File (EWF).
EDTx-13 INVALID PASSED DATA

Explanation: The function invoking the text editor has passed invalid data into the Active Area.

5.4 EDTx Messages
EDTx-14 –EDTx-19
EDTx-14 LINE NOT FOUND IN RANGE

Explanation: There is no line(s) in the range of the parameter(s) specified on the command. For
example, you cannot delete lines 300 through 500 when there are no lines with sequence numbers
greater than 299 and less than 501 in the EWF.
User Response: Possible user error. Examine the sequence numbers specified on the command for
validity. Examine the contents of the EWF to verify condition.
EDTx-15 EWF EMPTY

Explanation: There are no lines in the EWF for the command to process.
EDTx-16 UNABLE TO LOAD xxxxxxxx RC=nn

Explanation: The text editor is unable to load module xxxxxxxx. nn is the return code from the
SLOAD macro.
User Response: Check module SASSPROG for the module name and APPLCTN macro. If they
are not located there, check the CA-7 initialization file for an APPLCTN statement for the module
xxxxxxxx. Verify that the module exists on CA-7's Load library. If the problem persists, contact
EDTx-17 NUMBER OF LINES EXCEEDS EWF SPACE

Explanation: The number of lines has exceeded the amount of space available for the EWF.
User Response: Examine the EWF contents. Lines may have been lost. The maximum number of
lines available in the EWF depend on:
1. The type of device on which the Scratch queue is allocated.
2. The amount of space allocated.
3. The SWFTRK parameter on the DAIO initialization file statement.
EDTx-18 ACTIVE FILE NOT IN SEQUENCE...XSEQ ASSUMED

Explanation: When the text editor was invoked, the Active Area was found to be out of sequence.
External sequence numbering has been assumed and the EWF has been sequenced using the system
default increment.
User Response: XSEQ OFF may be used to set external sequencing off. RENUM may be used to
resequence the EWF. If external sequencing is desired, no action is necessary.
EDTx-19 EDIT LIST MODE INVALID

Explanation: The edit list mode (EDIT LIST) command is valid for 3270-type terminals only.
User Response: Use other forms of the EDIT commands or perform the desired operations on a
3270-type terminal.

5.4 EDTx Messages
EDTx-20 –EDTx-20
EDTx-20 EDIT STRING NOT FOUND IN RANGE

Explanation: String l of the EDIT command was not found in the range lines specified.
User Response: This may occur under the following conditions:
The string was specified incorrectly.
The line number range is incorrect.
The edit scan columns are set improperly (via STATUS).

5.5 GRLA Through GRLX Messages
GRLA-01 –GRLP-03
GRLA-01 LOGSTATS DATA SET OPEN FAILURE

Explanation: An OPEN error occurred for ddname LOGSTATS. Probable missing or incorrectly
spelled ddname in the DD statement. A U0001 abend follows this message.
GRLA-02 ERROR RETURNED BY SASSHDAT

Explanation: An error occurred while trying to convert a Julian date to Gregorian format. Probable
user error. A U0001 abend follows this message.
User Response: Provide correct dates for FROM and THRU values and resubmit.
GRLP-01 INVALID PARM DATA STARTING WITH

error-condition-text
Explanation: An error was found in the specified parameters. A two-line message is produced with
the second line identifying the specific error found. The second line may be either of the following:
UNKNOWN KEYWORD IN POSITION nn
where the nn indicates the position in the parameter string in which the unknown keyword was
found. POSITION is relative to 1, with the first nonblank character entered being position 1, and
includes any commas between keywords. A U0001 abend follows this message.
INVALID VALUE FOR KEYWORD xxxx
where the value for xxxx indicates the keyword for which an invalid value was entered. A U0001
abend follows this message.
User Response: Correct the PARM data and retry.
GRLP-02 'FROM' VALUE NOT HIGHER THAN 'THRU'

Explanation: The selection date/time range was specified incorrectly. Value for keyword THRU
must be higher than the value for keyword FROM. A U0001 abend follows this message.
User Response: Provide a correct date/time range and retry.
GRLP-03 INVALID DATE/TIME RANGE LITERALS

Explanation: Values provided for FROM and THRU did not contain valid date/time values or
range literals. A U0001 abend follows this message.
User Response: Provide correct date/time range and retry.

GRLP-04 –GRLX-04
GRLP-04 NO PARM OR SYSIN DATA FOUND

WILL TAKE ALL DEFAULTS
Explanation: No PARM was provided and no data was found in the SYSIN data set. Will proceed
using default values. Will set a condition code of 0.
User Response: None required unless defaults were not desired. If defaults are not acceptable,
provide PARM or SYSIN input and retry.
GRLP-05 LOGSTATS DATA SET OPEN FAILURE

Explanation: An OPEN error occurred for ddname LOGSTATS. Probable missing or incorrectly
GRLX-01 LOGIN DATA SET OPEN FAILURE

Explanation: An OPEN error occurred for ddname LOGIN. Probable missing or incorrectly
GRLX-02 LOGOUT DATA SET OPEN FAILURE

Explanation: An OPEN error occurred for ddname LOGOUT. Probable missing or incorrectly
GRLX-03 LOGIN DATA SET OUT OF SEQUENCE

Explanation: A sequence error occurred in the LOGIN data set. Due to the way date/time range
logic is applied, the input data must be in ascending date/time sequence. A U0001 abend follows
this message.
This error can occur if an extract is attempted against an active Log data set; that is, one to which
CA-7 is currently writing. Since reading stops once the THRU value is reached, undetected sequence
errors may exist beyond that date/time.
User Response: Determine cause of sequence error, sort the data if necessary, and retry. If an
active log is needed, perform a /SWAP command to begin recording on the alternate Log, and run
again. Be sure to always use the SASSHIS5 program to dump the log files.
GRLX-04 NO RECORDS FOUND BETWEEN FROM AND THRU VALUES

Explanation: This is an informational message. No records were found with creation date/time
occurring between the FROM and THRU values requested by the user. A condition code of 4 is set.
User Response: Provide correct parameters and/or correct data set and retry.

5.6 HEDT Through HISx Messages
HEDT-01 –HE00-05
HEDT-01 xxxxxxxx SEVERITY SCALE NOT FOUND

Explanation: This message will appear whenever the required Severity Scale (used by SASSHR04
and SASSHR05) cannot be found.
User Response: The severity scale module name in the control statement must be on the CA-7
Load library. If it is there, be sure the module specified on the control card is the correct module
name.
HEDT-02 xxxxxxxx SEVERITY SCALE HAS INVALID SIGN

Explanation: This message will appear whenever one or more severity levels contain an invalid
sign (not a + or a -).
User Response: Correct the Severity Scale, assemble, link edit the module, and rerun the job.
HEDT-03 xxxxxxxx SEVERITY SCALE HAS NON-NUMERIC

Explanation: This message will appear whenever one or more severity levels contain a non-numeric
entry.
HEDT-04 xxxxxxxx SEVERITY SCALE HAS INVALID ID

Explanation: This message will appear whenever the ID code in the Severity Scale does not match
the last 2 characters of the module name of the Severity Scale.
HEDT-05 xxxxxxxx SEVERITY SCALE NOT IN SEQUENCE

Explanation: This message will appear whenever one or more severity entries in the Severity Scale
are not in ascending sequence by value.
HE00-04 I/O ERROR ON LOG INPUT...FORCED EOF.

Explanation: An I/O error occurred during a GET from the log data input.
HE00-05 INVALID RECORD LENGTH, RECORD SKIPPED.

Explanation: A record on the log, history or archive file has an invalid length. The record is
ignored and the program continues to read the next record.

HIS5-01 –HIS6-01
HIS5-01 PARM=
Explanation: This message will appear whenever the PARM option is used.
HIS5-02 ERROR FOUND - RUN HALTED

Explanation: This message will appear whenever an unrecoverable error is found to exist. This
message is always preceded by an explanation of the error(s).
HIS5-03 INVALID PURGE DATE

Explanation: This message will appear if the Julian date (yyddd) field in PARM is found to be in
error.
HIS5-04 INVALID SORT SIZE

Explanation: This message will appear if the Sort Size (nnnnn) field in PARM is found to be in
error.
HIS5-05 SORT COMPLETION INVALID, RC=nnnn

Explanation: An error was detected by the Internal Sort and a bad return code was issued.
HIS5-06 LOG HISTORY FILE SEQUENCE ERROR

Explanation: Log history records are not in the correct order.
User Response: May have been dumping the disk Log file currently in use or the previous dump
run was in error. Correct the error and resubmit.
HIS5-07 ERROR ON LOG DUMP FILE

Explanation: Error has occurred reading the disk Log file.
User Response: May have been dumping the disk Log file currently in use or the previous dump
run was in error. Correct the error and resubmit.
HIS6-01 PARM=PURGE=yyddd,yyddd
Explanation: This message will always appear to show the period of time for which log records are
to be deleted.

HIS6-02 –HIS8-04
HIS6-02 INVALID KEYWORD

Explanation: This message will appear if the first characters of PARM data are not PURGE.
User Response: Correct the PARM data and resubmit the job.
HIS6-03 FROM DATE NOT VALID

Explanation: This message will appear if the FROM date was found to be in error.
User Response: Correct the FROM date and resubmit the job.
HIS6-04 THRU DATE NOT VALID

Explanation: This message will appear if the THRU date was found to be in error.
User Response: Correct the THRU date and resubmit the job.
HIS6-05 FROM DATE IS GREATER THAN THRU DATE

Explanation: This message will appear if the FROM date is found to be greater than the THRU
date.
User Response: Correct the date field in error and resubmit the job.
HIS6-10 ERRORS FOUND - RUN ENDED

Explanation: This message will appear if one or more of the error messages HIS6-01 through
HIS6-05 are present.
HIS8-01 EDIT MODULE NOT FOUND

Explanation: The edit module SASSHSxx (xx=report ID) was not found in CA-7's Load library.
User Response: Make the required SASSHSxx module available to the system and rerun the job.
HIS8-02 EXTRACT MODULE NOT FOUND

Explanation: The extract module SASSHExx was not found in CA-7's Load library.
User Response: Make the required SASSHExx module available and rerun the job.
HIS8-03 REPORT MODULE NOT FOUND

Explanation: The report module SASSHRxx was not found in CA-7's Load library.
User Response: Make the required SASSHRxx module available and rerun the job.
HIS8-04 DUPLICATED CONTROL CARD

Explanation: The control card shown duplicates a previous one.
User Response: Change either the request ID or the report ID in the control cards involved to
eliminate the duplication and rerun the job.

HIS8-05 –HIS8-12
HIS8-05 E15 DRIVER SASSHE00 NOT FOUND

Explanation: The extract driver SASSHE00 was not found in the library.
User Response: Make sure this module is in CA-7's Load library, which must be referenced by the
STEPLIB DD in the SASSHIS8 JCL.
HIS8-06 E35 DRIVER SASSHR00 NOT FOUND

Explanation: The report driver SASSHR00 was not found in the library.
User Response: Make sure this module is in CA-7's Load library, which must be referenced by the
STEPLIB DD in the SASSHIS8 JCL.
HIS8-07 TOO MANY REPORTS REQUESTED

Explanation: More than 50 reports were requested.
User Response: Break up the run into multiple runs and rerun the job.
HIS8-08 SORT NOT SUCCESSFULLY COMPLETED

Explanation: The internal sort was not successful.
User Response: Determine the nature of the problem and correct it, if possible. If not possible to
correct, contact your installation's CA-7 specialist for assistance.
HIS8-09 NO ERRORS WERE DETECTED

Explanation: The control card has been accepted.
HIS8-10 ERRORS DETECTED - EXECUTION HALTED

Explanation: One of the messages (with the exception of HIS8-09) in this message list was issued.
User Response: Correct all the errors indicated and rerun the job.
HIS8-11 FROM TIME NOT VALID

Explanation: The FROM time is not valid.
User Response: Correct the FROM time or eliminate it and rerun the job.
HIS8-12 FROM DATE NOT VALID

Explanation: The FROM date is not valid.
User Response: Correct the FROM date or eliminate it and rerun the job.

HIS8-13 –HIS8-18
HIS8-13 THRU TIME NOT VALID

Explanation: The THRU time is not valid.
User Response: Correct the THRU time or eliminate it and rerun the job.
HIS8-14 THRU DATE NOT VALID

Explanation: The THRU date is not valid.
User Response: Correct the THRU date or eliminate it and rerun the job.
HIS8-15 FROM PERIOD GREATER THAN THRU PERIOD

Explanation: The FROM date and time combination is greater than the THRU date and time com-
bination.
User Response: Correct the date/time combinations or eliminate them and rerun the job.
HIS8-16 PARM= DATA IN ERROR

Explanation: The data entered in the PARM operand of the EXEC statement contains an error.
User Response: Correct the error and rerun the job.
HIS8-17 NO INPUT REPORT REQUESTS FOUND

Explanation: No requests for reports were found on control cards.
User Response: Correct control cards to specify reports desired.
HIS8-18 CONTROL CARD EDIT FINAL RESULTS.

Explanation: Edit results are provided after this message.

5.7 HLP0 Through HS0x Messages
HLP0-00 –HLP0-05
HLP0-00 HELP REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Explanation: The request has been successfully processed.
HLP0-01 text
Explanation: An error occurred while processing the HELP command as indicated by text. The
values for text are detailed under message SM50-14.
User Response: Verify that the Help data set was allocated during CA-7 installation, and that there
is a JCL statement in the initialization file that defines the data set with an INDEX=255. Verify that
the volume on which the data set resides is available to CA-7. Also, refer to message SM50-14 for
other possible actions.
HLP0-02 MEMBER ...membername WAS NOT FOUND ON PDS...datasetname, VOLSER=volume

Explanation: The indicated member was not found on the data set specified. The data set resides
on the volume noted.
User Response: Verify that the specified membername, datasetname, and volume are correct. If all
are correct, contact your installation's CA-7 specialist for assistance.
HLP0-03 THE JCL INDEX TABLE IS NOT AVAILABLE

Explanation: No JCL statements were defined in the initialization file for CA-7. The HELP
command requires the HELP data set to be defined on a JCL statement in the initialization file with
INDEX=255.
User Response: Add a JCL statement to the initialization file for the HELP data set using
INDEX=255; then reinitialize CA-7.
HLP0-04 THE HELP DATA SET IS NOT IN THE JCL INDEX TABLE
Explanation: An attempt was made to access the Help data set and the data set is not in the JCL
statements in the initialization file.
User Response: A JCL statement must be added to the initialization file with INDEX=255. This is
the index number reserved for the Help data set.
HLP0-05 function IS NOT A DEFINED APPLICATION OR COMMAND

Explanation: The function value specified is an incorrect request for the HELP command.
User Response: Correct the input request and try again. Refer to the CA-7 Commands Guide for
more information about the HELP command, its format, and the options available.

HLPM-00 –HS03-01
HLPM-00 ENTER VALUES, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Explanation: Awaiting your choice of HELP functions.
User Response: Select a tutorial by entering the desired values and pressing Enter. To transfer to
another menu or formatted input screen, enter the desired FUNCTION value. Otherwise, position the
cursor to the top line and enter a command.
HLPM-02 MUST SPECIFY INDEX, AN APPLICATION OR A COMMAND

Explanation: One of the indicated fields must be provided for any request.
User Response: Provide a field and retry.
HLPM-05 INVALID VALUE FOR FIELD: xxxxxxxx

Explanation: An error was detected with the contents of the indicated field. The cursor will be
positioned to that field.
HS01-01 INVALID SYSTEM ID

Explanation: The system ID contains an error.
User Response: Correct or eliminate this operand and rerun the job.
HS01-02 INVALID SORT SELECTION

Explanation: The sort parameters contain an invalid key value.
User Response: Correct and rerun the job.
HS02-01 INVALID OPERATOR ID CODE

Explanation: The operator ID contains an error.
HS02-04 INVALID SCREEN PAGING OPTION

Explanation: The screen paging option contains an invalid value.
HS02-05 INVALID BLANK LINE OPTION

Explanation: The screen paging option contains an invalid value.
HS03-01 INVALID RECORD TYPE

Explanation: The record type contains a value that is not valid.

HS03-02 –HS05-05

User Response: Correct the sort key in error and rerun the job.
HS04-01 INVALID JOB

Explanation: The JOB value contains an error.
HS04-02 INVALID CA-7 NUMBER

Explanation: The CA-7 number contains an error.

HS05-01 INVALID STATION

Explanation: The station contains an error.
HS05-02 INVALID JOB

Explanation: The job contains an error.
HS05-03 INVALID NETWORK

Explanation: The network contains an error.
HS05-04 INVALID SUB-ID

Explanation: The sub-ID contains an error.
HS05-05 INVALID CA-7 NUMBER

Explanation: The CA-7 number contains an error.

HS05-06 –HS07-04
HS05-06 INVALID SCALE

Explanation: The Severity Scale ID is invalid.
User Response: Correct or eliminate this operand. Elimination of the module name causes History
Reporting to default to the provided scale.

HS06-02 INVALID SYSTEM ID

Explanation: The system ID contains an error.
User Response: Correct and rerun the job.
HS06-05 INVALID JOB NAME

Explanation: The job name contains an error.

HS07-01 INVALID STATION

Explanation: The station contains an error.
HS07-02 INVALID NETWORK

Explanation: The network contains an error.
HS07-03 INVALID JOB

Explanation: The job contains an error.


5.8 INxx Messages
INQB-01 –INQB-04
5.8 INxx Messages
INQB-01 FILE CONTROL RECORD IS NOT FIRST RECORD

Explanation: The control record created during the CA-7 queue unload was not found as the first
record. This message is followed by CA-7.935.
User Response: Make sure the queues were successfully unloaded previously. Also be sure that the
correct file is being used as input.
INQB-02 FILE TO RELOAD QUEUES IS NOT COMPLETE

Explanation: The control record created during the CA-7 queue unload was not found to be the last
record.
User Response: None, this is only a warning.
INQB-03 I/O ERROR ON QUEUE FILE...x Q=y

Explanation: An I/O error was detected while attempting to reload the CA-7 queue. x is a return
code from a CA-7 internal macro. y is the queue number that was being accessed. This message is
followed by CA-7.935.
Q# Name
1 Preprocess queue
2 Request queue
3 Ready queue
4 Active queue
5 Postprocess queue
6 Prior-run queue
User Response: Check system console log for I/O error. May require reallocating the queue and
running the MOVQ again. If still unsuccessful contact your installation's CA-7 specialist for assist-
ance.
INQB-04 UNEXPECTED EOF ON QUEUE FILE

Explanation: The file space for reloading the CA-7 queues has been exhausted. This message is
followed by message CA-7.935.
User Response: Increase the space allocation for the CA-7 queue files and RESTART CA-7.

5.8 INxx Messages
INQB-05 –INQB-09
INQB-05 CA-7 HIJOBNM EXCEEDED xxxxxx TIMES

Explanation: During a MOVQ operation, at least one job was found in the CA-7 queues whose
CA-7 job number was greater than the HIJOBNM. xxxxxx is the number of jobs found with this
condition.
User Response: The HIJOBNM value has apparently been changed to a lower value. Any jobs
using the larger numbers will run all right. The numbers are not reused.
INQB-05 VRM VSAM RESOURCE FILE DD (CA7RSRC) NOT FOUND

Explanation: The VRM database file specified using the CA7RSRC DD was not found during
MOVQ (Move queue) startup processing.
User Response: Include the VRM database component in the CA-7 execution procedure using the
CA7RSRC DD statement and restart CA-7.
INQB-06 ERROR OPENING THE VRM RESOURCE FILE

Explanation: An error has occurred during MOVQ (Move queue) startup processing while
attempting to open the VRM VSAM database component.
User Response: Ensure that the correct file is specified under the CA7RSRC DD statement in the
CA-7 execution JCL procedure and restart CA-7.
INQB-07 ERROR OPENING THE VRM DUMP FILE DD (CA7VDMP)

Explanation: An error has occurred during MOVQ (Move queue) startup processing while
attempting to open the VRM Dump queue file ddname CA7VDMP.
User Response: Specify the VRM Dump queue file using the CA7VDMP DD statement in the
INQB-08 INVALID CONTROL RECORD FOUND IN VRM DUMP FILE DD - CA7VDMP

Explanation: The VRM control record must be the first record found when processing the VRM
Dump queue file during reload.
User Response: Verify that the correct file was specified under the CA7VDMP DD statement in the
INQB-09 CA-7 QUEUE DUMP FILE AND VRM DUMP FILE OUT OF SYNCH
Explanation: The CA-7 Dump queue file control record and the VRM Dump queue control records
have mismatching date and time stamps.
User Response: Verify that the correct file name was specified under the CA7VDMP DD statement
in the CA-7 execution JCL procedure and restart CA-7.

5.8 INxx Messages
INQB-10 –INQD-04
INQB-10 INVALID LRECL FOR VRM RESOURCE FILE

Explanation: An invalid record length was found for the VRM VSAM database component. Verify
that the data set was allocated using the correct IDCAMS control statements supplied in the CA-7
installation JCL library member name VRMDECK.
User Response: Verify that the correct file name was specified under the CA7RSRC DD statement
in the CA-7 execution JCL procedure and restart CA-7.
INQB-11 VSAM PROCESSING ERROR - FUNCTION = XX RC = XX FDBK = xxxxxxxx

Explanation: A VSAM I/O error has occurred during MOVQ (Move queue) startup processing.
INQB-25 ARF VSAM FILE DD (CA7ARFDB) NOT FOUND

Explanation: The ARF database DD statement could not be found.
User Response: You need to add the ARF database to the CA-7 JCL.
INQB-26 ERROR OPENING ARF RESOURCE FILE

Explanation: A nonzero return code was found during OPEN to the ARF database.
User Response: Check for messages on the console for VSAM errors.
INQD-01 CORE FOR WORK AREA UNAVAILABLE

Explanation: The module used to unload the CA-7 queues (SASSINQD) could not find enough
space for its required work area. This message is followed by message CA-7.934.
User Response: Retry with a larger region size for CA-7.
INQD-02 I/O ERROR ON QUEUE FILE...x Q=y

Explanation: An I/O error was detected while attempting to unload the CA-7 queue. x is a return
code from a CA-7 internal macro. y is the queue number that was being accessed. This message is
followed by message CA-7.934. See INQB-03 for queue numbers and names.
INQD-03 FILE SPACE FOR QUEUE UNLOAD EXCEEDED

Explanation: The file space on UCC7QDMP had been exceeded. This message is followed by
message CA-7.934.
User Response: Increase the space allocation for CA-7 QDMP. Bring CA-7 up with a WARM or
ERST type start and retry the DMPQ shutdown.
INQD-04 QDMP FILE OPEN FAILED

Explanation: An open failed on the file defined by the UCC7QDMP DD when dumping of queues
was requested during shutdown.
User Response: Check attributes and JCL for dump file, correct and retry.

5.8 INxx Messages
INQD-05 –INWC-01
INQD-05 QDMP (VRM) FILE OPEN FAILED

Explanation: While doing a CA-7 shutdown processing that includes a DMPQ, the OPEN to the
VRM dump queue data set (ddname of CA7VDMP) has failed.
User Response: If the CA7VDMP dd card is missing, change the CA-7 JCL to add it, and start
CA-7 (WARM or ERST). The CA-7 shutdown using DMPQ can now be done.
INQD-09 VSAM PROCESSING ERROR ON VRM FILE...XX RC = XX FDBK = XXXXXXXX

Explanation: A VSAM I/O error occurred during DMPQ (Dump queue) shutdown while processing
VRM active resource records.
INWC-01 SASSINQB (QUEUE RELOAD) MODULE NOT FOUND

Explanation: The module required for the MOVQ function was not found. This message is fol-
lowed by message CA-7.935.
User Response: Make sure SASSINQB exists on a load library referenced by the STEPLIB DD
statement in CA-7's online JCL.

5.9 JCKn Messages
JCK0-T1 –JCK0-04
5.9 JCKn Messages
JCK0-T1 LINK 1 COMPLETE

Explanation: First link of the interface is complete.
User Response: This is an informational message for testing purposes only.

Explanation: Second link of the interface is complete.

Explanation: Third link of the interface is complete.

Explanation: Fourth link of the interface is complete.
JCK0-01 INPUT DATA SET OPEN FAILURE

Explanation: Unable to open DD=INPUT. A condition code of 8 is set.
User Response: Check that DD=INPUT is correctly specified.
JCK0-02 SYSIN DATA SET OPEN FAILURE

Explanation: Unable to open DD=SYSIN. A condition code of 8 is set.
User Response: Check that DD=SYSIN is correctly specified.
JCK0-03 BAD RETURN FROM SASSBSTR, RC=xxxx

Explanation: Module SASSBSTR completed with a nonzero return code. The RC value gives the
error code. Refer to WTO messages for a further explanation of the error code.
User Response: Diagnose the problem using the WTO messages and take appropriate action.
JCK0-04 ERROR LINKING TO SASSBSTR, ABEND CODE=xxx

Explanation: The link to module SASSBSTR failed. The ABEND CODE value gives the error
code. Refer to the IBM MVS System Codes manual for a further explanation of the error code.
User Response: Diagnose the problem using the IBM MVS System Codes manual and take appro-
priate action.

5.9 JCKn Messages
JCK0-05 –JCK2-01
JCK0-05 ERROR LINKING TO SASSJCK1, ABEND CODE=xxx

Explanation: The link to module SASSJCK1 failed. The ABEND CODE value gives the error
priate action.
JCK0-06 ERROR LINKING TO SASSJCK2, ABEND CODE=xxx

Explanation: The link to module SASSJCK2 failed. The ABEND CODE value gives the error
priate action.

JCK1-02 SYSPRINT DATA SET OPEN FAILURE

Explanation: Unable to open DD=SYSPRINT. A condition code of 8 is set.
User Response: Check that DD=SYSPRINT is correctly specified.
JCK1-03 SYSIN DATA SET EMPTY

Explanation: DD=SYSIN is empty. No /LOGON record can be passed for the interface. A condi-
tion code of 8 is set.
User Response: Specify a /LOGON card as the first record in DD=INPUT.
JCK1-04 NO FORECASTED JOB OUTPUT

Explanation: No forecasted job output was available for the interface. A condition code of 8 is set.
This could be caused by all jobs that were selected being NON-EXEC jobs.
User Response: Check that the FJOB commands in DD=INPUT are correctly specified.
JCK1-05 NO /LOGON CARD FOUND

Explanation: The first record in DD=INPUT was not a /LOGON card. A condition code of 8 is
set.
User Response: Specify a /LOGON card as the first record in DD=INPUT.


5.9 JCKn Messages
JCK2-02 –JCK2-05
JCK2-02 SYSPRINT DATA SET OPEN FAILURE

Explanation: Unable to open DD=SYSPRINT. A condition code of 8 is set.
User Response: Check that DD=SYSPRINT is correctly specified.
JCK2-03 JCLCHECK DATA SET OPEN FAILURE

Explanation: Unable to open DD=JCLCHECK. A condition code of 8 is set.
User Response: Check that DD=JCLCHECK is correctly specified.
JCK2-04 ERROR LINKING TO SASSHDAT, ABEND CODE=xxx

Explanation: The link to module SASSHDAT failed. The ABEND CODE gives the error code.
Refer to the IBM MVS System Codes manual for a further explanation of the error code.
priate action.
JCK2-05 CA-7 AT PRE-V2.9 LEVEL

Explanation: The job selection interface between CA-7 and CA-JCLCHECK detected a code indi-
cating CA-7 is at a level before Version 2.9. This interface requires a Version 2.9 or later version of
CA-7.
User Response: Verify that CA-7 is at the correct version level and upgrade if necessary. If the
problem recurs, save all output and contact Computer Associates Technical Support.

5.10 L2xxx Messages
L2CCIIS –L2TROUTR
5.10 L2xxx Messages
L2CCIIS Task for xxxxxxxx ended, TCBADDR=nnnnnnnn, TCBCMP=nnnnnnnn

Explanation: The CA-7 subtask for the XPS ROUTER ended. The TCB address as well as the
completion code are reported.
User Response: If this message appears prior to CA-7 shutdown, then it is an error and should be
reported to your CA-7 technical specialist. This message is normally produced at CA-7 shutdown.
L2CCIIS EOT issued DETACH for xxxxxxxx, TCBADDR=nnnnnnnn, RC=nnnnnnnn

Explanation: The end-of-task issued a DETACH for the task that is ending.
L2CCILET CCI Listener for xxxxxxxx ended, TCBADDR=nnnnnnnn, TCBCMP=nnnnnnnn

Explanation: The CA-7 subtask for a CCI listener ended. The TCB address as well as the com-
pletion code are reported.
User Response: If this message appears prior to CA-7 shutdown, then it is an error and should be
reported to your CA-7 technical specialist. This message is normally produced at CA-7 shutdown.
L2CCILET EOT issued DETACH for xxxxxxxx, TCBADDR=nnnnnnnn, RC=nnnnnnnn

Explanation: The end-of-task issued a DETACH for the task that is ending.
L2TROUTR SDWA at nnnnnnnn

Explanation: The recovery routine for a CA-7 subtask detected an error. The SDWA address is
reported.
L2TROUTR PSW nnnnnnnn nnnnnnnn

Explanation: The recovery routine for a CA-7 subtask detected an error. The PSW is reported.
L2TROUTR ABEND CODE nnnnnnnn

Explanation: The recovery routine for a CA-7 subtask detected an error. The abend code is
reported.

5.10 L2xxx Messages
L2TROUTR –L2TROUTR
L2TROUTR ESTAE R15=nnnnnnnn R0=nnnnnnnn

Explanation: The recovery routine for a CA-7 subtask detected an error. The abend code is
reported.

5.11 MLRF Through MNU0 Messages
MLRF-00 –MLRF-12
MLRF-00 ENTER VALUES, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Explanation: Awaiting your choice of APA graphing functions.
User Response: Display a graph by entering the desired values and pressing Enter. To transfer to
MLRF-01 NOT ENOUGH INFORMATION

Explanation: The fields completed do not fully define a valid APA function.
User Response: Review documentation and enter fields required for whatever function is desired.
MLRF-02 AT LEAST 1 ID IS REQUIRED

Explanation: For function value G, at least one graph ID must be given.
User Response: Provide desired graph ID(s) and press Enter.
MLRF-06 GLINE VALUE IS INVALID FOR PRIM GRAPHS

Explanation: At least one of the graph IDs given is for a PRIM type of graph but the value entered
for GLINE is for a comparison type graph.
User Response: Correct graph ID(s) or GLINE value and press Enter.
MLRF-07 AT LEAST 1 ID HAS NO CALCULATION DEFINED

Explanation: At least one of the graph IDs given has no calculation value predefined for it and no
GLINE value entered. The cursor is positioned at the GLINE field.
User Response: Correct graph ID(s) or GLINE value and press Enter.
MLRF-11 INVALID VALUE ENTERED FOR FIELD: xxxxxxxx

Explanation: An invalid value was entered. The cursor will also be positioned at the field in
question.
User Response: Correct the value in the indicated field and press Enter.
MLRF-12 ID IS UNKNOWN
Explanation: An invalid graph ID was entered. The cursor will also be positioned at the ID in
question.
User Response: Correct the indicated ID field and press Enter.

MLRF-13 –MLRx-04
MLRF-13 INVALID DATE RANGE

Explanation: The specified FROM and/or THRU values are invalid. Any of the following will
cause this error:
- FROM date older than 2 years prior to today's date
- FROM date greater than today's date
- THRU date less than FROM date
User Response: Correct the date values and press Enter.
MLR0-00 ENTER FUNCTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Explanation: Awaiting your choice of APA graphing functions.
User Response: Select a category by entering the desired values and pressing Enter. To transfer to
MLR0-05 INVALID FUNCTION VALUE

Explanation: The value entered is unknown.
MLR0-09 YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Explanation: Security controls prohibit you from using the function you requested.
User Response: Contact your installation's security administrator if you need to gain authorization
for that function.
MLRx-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd.

Explanation: This is an information message indicating completion of request processing.
MLRx-03 REQUIRED INPUT MISSING

Explanation: Minimum input required to process the request was not given. Minimum input is
GRAPHc,ID= or GRAPHc,LIST=.
User Response: Correct by adding required data and retry.
MLRx-04 INVALID COMBINATION OF INPUT PARAMETERS.

Explanation: Mutually exclusive input parameters were used, and the module is unable to deter-
mine which type of request or option is to be processed.
User Response: Check input and delete one or more parameters that may conflict. (Check for LIST
specification; if used it must be the only parameter.)

MLRx-05 –MNU0-00
MLRx-05 INVALID OR OMITTED yyyyyyyy DATA

Explanation: Field identified by yyyyyyyy is invalid or missing.
User Response: Correct or enter data for field yyyyyyyy.
MLRx-08 LOAD ERROR FOR xxxxxxxx WITH RETURN CODE nn

Explanation: Module xxxxxxxx could not be loaded; nn is the code returned.
User Response: Check that the module named is on the Load library and that it was link edited
correctly. Also make sure the module is defined either by an APPLCTN macro in the module
SASSPROG or by an APPLCTN statement in the initialization file. If the problem persists, contact
MLRx-10 UNRECOGNIZABLE KEYWORD IN INPUT

Explanation: An undefined keyword was found in the input request.
MLRx-50 STAT RECORD DATE IN ERROR

Explanation: Internal error.
MLRx-51 GRAPH ID xxx NOT DEFINED

Explanation: The ID value xxx is not defined in the graph definition table specified.
User Response: Enter GRAPHc,LIST=HELP for a list of all valid graph identification numbers.
MLRx-52 UNABLE TO OPEN STATISTICS FILE

Explanation: Statistics file is not available.
User Response: Check to be sure a DD statement for UCC7STAT is in CA-7's JCL and that the
file was initialized with the SASSCDSI program.
MLRx-53 UNRECOVERABLE I/O ERROR ON STATISTICS FILE, UNABLE TO CONTINUE

Explanation: Probable hardware error.
User Response: Retry. If problem persists, contact your installation's CA-7 specialist for assistance.
MLRx-nn UNABLE TO DETERMINE ERROR CONDITION

Explanation: Probable internal error which module cannot diagnose.
User Response: Retry. If problem persists, contact your installation's CA-7 specialist for assistance.
MNU0-00 SPECIFY DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE.

User Response: Select a menu option.

MNU0-09 –MNU0-09
MNU0-09 YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Explanation: The request function cannot be done because the current security setup does not allow
it.
User Response: Change the security definition and retry the function.

5.12 QMxx Messages
QMxx-00 –QMxx-04
5.12 QMxx Messages
QMxx-00 JOB xxxxxxxx(nnnn) POSTED FOR NORMAL COMPLETION

Explanation: The indicated job's status has been changed to complete. Normal completion proc-
essing will begin.
QMxx-00 xxxxxxxx FUNCTION SUCCESSFUL

JOB POSTED FOR SUBMISSION
Explanation: The requested function has been successfully performed. If the second line appears,
the job is now ready for submission.
QMxx-00 ENTER VALUES, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Explanation: Describes the user options available.
QMxx-01 zz INVALID MACRO RETURN CODE yyyynnnn

Explanation: An error occurred on a formatted screen.
User Response: There are two major actions possible.
1. If QMxx=QM10, zz=BA and nnnn=0000, this indicates that the Scratch Work file was not large
enough to handle the command response. Check the DAIO statement in the initialization file
and increase the SCRTRK (or SWFTRK) parameter.
2. If QMxx=QM20 and zz=K2, there could be an error in the VTAM definitions. Check for
CA-7.V001 message on the system console. The PSERVIC value in a MODENT macro defi-
nition to VTAM may be incorrect.
QMxx-02 JOB NOT FOUND

Explanation: The job no longer exists in the queue with which you are working.
QMxx-04 CONFLICTING FUNCTIONS SPECIFIED

Explanation: Multiple function requests have been specified on the same screen. These functions
have implied conflicts.

5.12 QMxx Messages
QMxx-05 –QMxx-13
QMxx-05 INVALID OR OMITTED xxxxxxxx DATA

Explanation: The identified field contains invalid data or is a required field.
QMxx-05 INVALID VALUE ENTERED FOR FIELD: xxxxxxxx

Explanation: The identified field contains invalid data or is a required field.
QMxx-09 YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Explanation: The authorization to do this function has not been setup by your installation's security
administrator.
User Response: If this function is necessary for you to perform your duties, contact your installa-
QMxx-10 UNRECOGNIZABLE DATA IN INPUT

Explanation: An unrecognizable keyword and/or value was input.
User Response: Correct the command and reenter.
QMxx-10 *** ATTENTION ***JOB=xxxxxxxx(nnnn) HAS BEEN CANCELLED

Explanation: The appropriate LTERM is notified that a job has been canceled.
QMxx-12 FUNCTION ONLY AVAILABLE ON-LINE

Explanation: The Queue Maintenance functions are not available in batch mode.
User Response: Use an online terminal for these functions.
QMxx-13 NO RECORDS FOUND

Explanation: No queue records could be found meeting the criteria imposed by the input command.
QMxx-13 NO SUCH JOB(S) FOUND

Explanation: No queue records could be found meeting the criteria imposed by the input command.
QMxx-13 JOB NOT FOUND

Explanation: The job no longer exists in the queue with which you are working.

5.12 QMxx Messages
QMxx-13 –QMxx-30
QMxx-13 NO SUCH TASKS IN THE QUEUE

Explanation: No network tasks were found matching the selection criteria.
QMxx-14 CONFLICT IN JCLID AND JCLLIB FIELDS

Explanation: The JCL library for a job can only be specified by a JCLID or a JCLLIB, not both.
User Response: Specify either a JCLID or a JCLLIB and reenter.
QMxx-21 JOB ALREADY SUBMITTED TO HOST

Explanation: The requested function cannot be performed after the job has been submitted.
QMxx-22 FUNCTION INVALID FOR THIS QUEUE

Explanation: The requested function is not valid for the queue with which you are working.
QMxx-23 MUST USE 'CANCEL' FOR LOG DUMP JOBS

Explanation: An attempt was made to cancel the job that dumps the CA-7 Log file. This is not
allowed from this screen.
User Response: Use the CANCEL command for this job. If FORCE=YES is not specified, the job
will reappear in the Request queue.
QMxx-30 ALL REQUIREMENTS SATISFIED FOR xxxxxxxx(nnnn)

Explanation: You cannot post requirements for the identified job because the master count is zero.
User Response: If you wish to unpost requirements and the job has not been submitted, you may
hold the job. The request will then be honored.
QMxx-30 REF#=jjjjrrs JOB=xxxxxxxx NW=xxxxxxxx SUB=xxxxxxxx DESC=xxxxxxxx

STATION=xxxxxxxx HAS LOGGED IN
Explanation: This message is sent to the previous station whenever a station logs in work.

5.12 QMxx Messages
QMxx-31 –QMxx-42
QMxx-31 SKELETON RECORD FOUND

Explanation: Schedule Scan has not completed initial processing on the queue record.
User Response: Wait a few minutes and try again. Look for error messages concerning this job on
terminal defined as STANIDS=MASTER in the initialization file. The job may have to be canceled
using the CANCEL command with the FORCE=YES option. After the cancel has been done, the job
can be DEMANDed back into the Request queue. If problem persists, contact your installation's
QMxx-31 REF#=jjjjrrs JOB=xxxxxxxx NW=xxxxxxxx SUB=xxxxxxxx DESC=xxxxxxxx

STATION=xxxxxxxx HAS LOGGED OUT
Explanation: This message is sent to the next station whenever a station logs out work.
QMxx-32 REQUIREMENTS SCAN INCOMPLETE

Explanation: Schedule Scan has not completed initial processing on this queue record.
User Response: Wait a few minutes and try again. Look for error messages concerning this job on
terminal defined as STANIDS=MASTER in the initialization file. The job may have to be canceled
and DEMANDed to resolve the problem. If problem persists, contact your installation's CA-7 spe-
QMxx-33 JOB COMPLETE OR RESTART IN PROCESS

Explanation: The job is in purge or restart processing and cannot be updated.
QMxx-40 PROMPT HAS NOT BEEN RECEIVED

Explanation: An attempt has been made to acknowledge a prompt but no prompt has been sent.
QMxx-41 DEADLINE TIME MUST PRECEDE DUE-OUT TIME

Explanation: The deadline time specified is later than the due-out time. This is an invalid condi-
tion.
User Response: Correct the deadline and/or due-out time and retry.
QMxx-42 CA-11 RESTART KEYWORDS INVALID WITH SELECTED FUNCTION

Explanation: The RESUBMIT or FORCE COMPLETE function was selected but one or more of
the CA-11 RESTART/RERUN fields was supplied.
User Response: If a RESUBMIT or FORCE COMPLETE is to be done, clear the CA-11
RESTART/RERUN fields on the screen. If a restart is to be done, select the CA-11
RESTART/RERUN function.

5.12 QMxx Messages
QMxx-50 –QMxx-58
QMxx-50 //*UCC7RESTART CARD NOT FOUND IN JCL

Explanation: The execution JCL should contain a restart comment statement. For unexplained
reasons, the statement is no longer present.
User Response: The statement may be reinserted by using the QJCL screen to fetch the JCL,
correct it, and then save it. In any case, contact your installation's CA-7 specialist for assistance.
Try to write down the commands which resulted in this condition.
QMxx-51 ERROR TRYING TO UPDATE THE CA-11 CMT FILE

Explanation: While CA-7 was trying to write to the CA-11 CMT, an error was encountered.
User Response: Check the system console for CA-11 error messages. If the error is temporary, the
update should be attempted later.
QMxx-52 LOAD PROCESSING INCOMPLETE

Explanation: Job load processing is currently in process for this job.
User Response: Wait until load processing completes before attempting the requested function.
QMxx-53 JOB DOES NOT HAVE ABNORMAL STATUS

Explanation: The requested function is only valid for jobs with abnormal status.
QMxx-55 CAN NOT RESTART - NO JCL ATTACHED

Explanation: A restart is being attempted for a job that does not have any JCL. Because there is
not any JCL, a restart would be invalid. Usually the job is marked EXEC=NO in the database so
that it will not be submitted to execute.
User Response: If the job should have had JCL, it may be added using the QJCL facility. If the
job is not supposed to have JCL (that is, if EXEC=NO on the DB.1 screen) and has a restart require-
ment, it must be CANCELed and brought back into the Request queue without the restart require-
ment.
QMxx-57 COMMAND DISABLED BY SITE OPTION

Explanation: The line command character entered here has been disabled in the CA-7 initialization
file.
User Response: Use the equivalent top line command or contact your CA-7 specialist.
QMxx-58 CANNOT HOLD - JOB ALREADY SUBMITTED OR COMPLETE

Explanation: An attempt to place a job on Hold was rejected. The job was in the active queue, in
the ready queue and already submitted to the MVS host, or in the request queue in successful com-
pletion processing.
User Response: None. The job is not placed on Hold.

5.12 QMxx Messages
QM10-00 –QM2F-09
QM10-00 ENTER FUNCTION (C,F,H,I,O,P, OR R) IN 'F' FIELD OR ENTER A COMMAND ON THE

TOP LINE
Explanation: Describes the options available on the QM.6-X panel.
QM10-00 nn TRANSACTIONS PROCESSED, nn ERRORS DETECTED

Explanation: Describes the total number of line transactions processed, and the number of those
transactions that encountered an error.
User Response: For any errors, refer to the specific error reason in the REMARKS field for the
transaction(s) in error.
QM10-01 SCRATCH QUEUE ACCESS ERROR, RC=xxxxxxxx

Explanation: An error was encountered accessing the CA-7 scratch queue.
QM10-09 LAST ? SHOWN WAS SECURITY AUTHORIZATION FAILURE

Explanation: The last exception line transaction processed (? in 'F' field) encountered a security
authorization error.
QM2F-01 QUEUE ACCESS OR SORT ERROR: xxxx

Explanation: An error occurred while accessing the CA-7 queues, or, while sorting the selected
queue data. The specific error code is described by xxxx.
QM2F-08 YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Explanation: You do not have the proper security to access the target job.
QM2F-09 YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Explanation: The authorization to do this function has not been setup by your installation's security
administrator.

5.12 QMxx Messages
QM20-07 –QM20-51
QM20-07 UPDATE DENIED - SUBMIT CHECK FAILED

Explanation: An attempt was made to replace JCL for a Request queue job. The JCL contained a
USERID and the updater was not authorized to submit for that USERID.
User Response: If security access should be allowed for the updater, contact your local CA-7 Secu-
rity Administrator or log on with an authorized USERID and update the JCL.
QM20-08 QJCL FOR JOB xxxxxxxx(nnnn) BEING EDITED BY ANOTHER USER

Explanation: This message is returned whenever JCL editing is requested for a job in the Request
queue, but another CA-7 user already has the JCL for editing. The job name is indicated by
xxxxxxxx and the CA-7 job number is indicated by nnnn.
User Response: Wait for a few minutes for the other user to release the JCL then retry your
request.
QM20-24 USE 'CANCEL' COMMAND - JOB IN LOAD STATUS

Explanation: An attempt is made to cancel a job that is in the Request queue and is currently going
through LOAD processing. Also, refer to the explanation in message SPO6-11.
User Response: Wait a few minutes and try again. If the message persists and the job must be
canceled before LOAD completion processing finishes, use the top line CANCEL command with the
FORCE=YES option.
Note: This may cause invalid job data to be added to the database. It is best to wait for the LOAD
to complete before canceling the job.
QM20-34 ALL REQUIREMENTS SATISFIED EXCEPT RESTART

Explanation: Requirement posting (option X) was requested from the XQ, XQJ, XQM, or XQN
screen but only restart is needed; all other requirements are satisfied.
User Response: Use option F to transfer from the XQ, XQJ, XQM, or XQN screen to the QM.4
(XRST) screen and perform the restart. You could also use the top line RESTART command.
QM20-51 ERROR ACCESSING CA-11 CMT (xx)

Explanation: During the processing for a cancel function (C) from the XQ/XQJ/XQN screen, an
error occurred in the CA-7/CA-11 interface. The error code (xx) has the following meanings:
04 - unexpected end-of-data on the CMT.
08 - exclusive control CMT member not available.
0C - CMT member changed by another program during access.
10 - fatal error - CA-11 Database Address Space is down.
User Response: Verify status of job on CMT by using the ARTS monitor interface. If the job
shows in restart status, a PRE P command should be requested. Refer to CA-11 manuals for format
of online CA-11 (ARTS) commands and how to determine job status.

5.12 QMxx Messages
QM20-56 –QM30-00
QM20-56 MUST REQUE OR USE TOP-LINE CANCEL

Explanation: Cancel was requested for a job in the Ready or Active queue, but the CA-11 interface
is installed. Since the interface could cause the CA-11 database entry for this job to be reset, the job
should be requeued before it is canceled.
User Response: If the job is active or submitted to a CPU, use OS or JES cancel commands to
purge the job from the host system. This prevents duplicate runs. If the job is in the Ready queue
with JCLERR status or the host CPU is (or has been) down, REQUEUE the job before canceling. If
you must cancel without requeuing, use the top line CANCEL command with FORCE=YES.
QM20-60 CANNOT CANCEL - JOB HAS RESOURCES

Explanation: The job cannot be canceled because it still holds VRM resources.
User Response: Either use the PRSCF command to release the resources, or use the top line
CANCEL command with FORCE=YES.
QM20-61 CANNOT CANCEL - JOB HAS ACTIVE ARF

Explanation: This message is issued when a cancel is attempted while ARF is controlling recovery
for a job.
User Response: Wait until ARF recovery is complete for the job. The LARFQ command can be
used to track the progress of ARF recovery for the job.
If the cancel must be issued prior to the completion of ARF recovery, then the ARFP command can
be used to terminate ARF recovery processing for the job. After the ARFP command processing is
complete, the cancel may be issued.
QM20-62 XQ E NOT VALID FOR 7UNI JOBS WITHOUT MIXED CASE SUPPORT
Explanation: The XQ screen will not allow an E (edit) function for jobs that are set as 7UNI jobs
unless CA-7 mixed case support has been enabled.
User Response: If the JCL must be modified, then the job could be canceled, the JCL changed
outside of CA-7, and use the DEMAND command to bring the job in again.
QM20-63 CANNOT CANCEL - ERROR IN ARF PURGE

Explanation: An error occurred while trying to delete the ARF environment for a job.
User Response: Attempt an ARFP command. If this fails, contact your installation's CA-7 spe-
QM30-00 SET 'F' = 'X' TO POST OR ENTER A COMMAND ON TOP LINE

Explanation: Describes the options available on the QM.2-X panel.

5.12 QMxx Messages
QM50-51 –QM50-51
QM50-51 JOB NOT RESTARTABLE - USE RESUBMIT

[RMS STEP DID NOT COMPLETE]
[NCF INVOLVED BUT RMS NOT INSERTED BY CA-7]
Explanation: The job being displayed on the QM.4 (XRST) screen is not restartable. The
RESUBMIT option should be used instead of RESTART. This message appears if:
1. A job is not restartable according to the CMT flag settings.
2. The RMS procedure was inserted by CA-7, but did not complete.
3. The job executed at a remote site (NCF node), but RMS was not inserted by CA-7.
User Response: If the job is to be rerun, use the RESUBMIT option. If NCF and CA-11 are
involved but CA-7 is not inserting RMS, the JCL must be updated to set the RMS parameters.
QM50-51 CMT MEMBER NOT AVAILABLE - RETRY LATER

Explanation: Another user in the system has the CMT member for the job under exclusive control.
User Response: Wait a few minutes, then retry the request again. If the problem persists, contact
QM50-51 CMT CHANGED SINCE DISPLAYED - TRY AGAIN

Explanation: Between initial display and update request, the CMT member for the job was updated
by another user.
User Response: Recheck the displayed fields, correct and reenter.
QM50-51 FATAL ERROR - CA-11 MAY BE DOWN

Explanation: The CA-11 Database Address Space appears to be down.
User Response: Check status of CA-11 and reinitialize if necessary, then try the request again. If
problem persists, contact your installation's CA-7 specialist for assistance.
QM50-51 START STEP NOT FOUND IN CMT - TRY ANOTHER

Explanation: The requested starting step name for restart was not found in the CMT.
User Response: Use a different step name and try again. You may wish to check the CMT
member for the job using the CINQ command to CA-11 through the ARTS monitor.
QM50-51 END STEP NOT FOUND IN CMT - TRY ANOTHER

Explanation: The requested ending step name for restart was not found in the CMT.

5.12 QMxx Messages
QM50-51 –QM50-60
QM50-51 START STEP NOT RESTARTABLE - TRY ANOTHER

Explanation: The requested starting step for restart is flagged as not restartable on the CMT.
User Response: Specify an earlier starting step and retry. You may wish to check the CMT
member for the job using CINQ command to CA-11 through the ARTS monitor.
QM50-51 USAGE CODE MUST CHANGE - TRY AGAIN

Explanation: CA-11 options require the usage code to change between runs but the QM.4 (XRST)
screen field matches the CMT field.
User Response: Change the usage field on the QM.4 (XRST) screen and try again.
QM50-51 LRTCD STEP NOT FOUND IN CMT BEFORE START STEP

Explanation: A CA-11 restart was attempted, but the step name specified in the LRTCD field is
not prior to the step specified for the starting step.
User Response: Correct the step name(s) and the press Enter.
QM50-51 INVALID ERROR CODE - xx

Explanation: A CA-11 restart was attempted; however, an unknown return code was received from
CA-11. This may be caused by a mismatch between the version of CA-11 and the version of the
CA-7/CA-11 interface.
User Response: Check the CA-7 address space for CA-11 messages indicating invalid or out dated
parameter lists (such as U11-300). If these messages are present, upgrade your CA-7/CA-11 inter-
face to match the release of CA-11 you are executing.
QM50-52 JOB FOUND BUT LOAD PROCESSING INCOMPLETE

Explanation: A restart was attempted on a job that is in the LOAD process.
User Response: Allow the job to complete the LOAD process.
QM50-59 USE RESUBMIT OR SET PARM - NO CMT MEMBER

Explanation: A CA-11 Restart was specified for a job that does not have a CMT member which
CA-7 can access.
User Response: The 'RESUBMIT FOR PRODUCTION' or 'SET PARM DATA FOR RMS' may be
used to resubmit the job to the operating system. If the job is submitted to a remote site and tracked
using CA-7 NCF, the 'SET PARM DATA FOR RMS' field should be used to pass the correct CA-11
PARM in the JCL.
QM50-60 USING LRTCD REQUIRES A STARTING STEP NAME

Explanation: A step name was supplied in the LRTCD field, but the starting step name was left
blank.
User Response: Supply the appropriate starting step name and press Enter.

5.12 QMxx Messages
QM50-61 –QM70-62
QM50-61 UNABLE TO RESTART, ARF EVENTS PENDING

Explanation: This message is issued when a RESTART is attempted while ARF is controlling
recovery for a job.
If the RESTART must be issued prior to the completion of ARF recovery, then the ARFP command
can be used to terminate ARF recovery processing for the job. After the ARFP command processing
is complete, the RESTART may be issued.
QM70-10 *** ATTENTION *** JOB=xxxxxxxx (nnnn) HAS BEEN CANCELED

Explanation: Job xxxxxxxx, job number nnnn has been canceled by a user request.
QM70-62 CANNOT CANCEL, ARF RECOVERY IN PROGRESS

Explanation: This message is issued when a request to cancel a job is received while ARF is con-
trolling recovery for a job.
If the job must be canceled prior to the completion of ARF recovery, then the ARFP command can
be used to terminate ARF recovery processing for the job. After the ARFP command processing is
complete, then the cancel request may be issued.

5.13 RMS1 Messages
RMS1-00 –RMS1-82
5.13 RMS1 Messages
RMS1-00 ARTS ONLINE MONITOR ENDED

SYSTEM-CODE(xxxx) USER-CODE(nnnn)
Explanation: Normal completion of ARTS command occurred. xxxx is the system abend code and
nnnn is the user abend code. For normal completion, both xxxx and nnnn are zero.
User Response: If both xxxx and nnnn are zero, no action is required. See message RMS1-80. If
nnnn is 0999, the interface to CA-11 is not initialized.
RMS1-70 FUNCTION ONLY AVAILABLE FROM 3270 TERMINALS

Explanation: ARTS command was issued from a non-3270 terminal.
User Response: Use 3270 (online) terminal to issue ARTS commands.
RMS1-80 ARTS ONLINE MONITOR TERMINATED

Explanation: Abnormal completion of ARTS command occurred either due to a C request made by
operator or abend condition noted. xxxx is the system abend code and nnnn is user abend code.
User Response: Determine cause of error and correct.
RMS1-81 ATTACH UNSUCCESSFUL FOR xxxxxxxx

Explanation: ARTS command was attempting to attach the CA-11 control program identified by
xxxxxxxx, but the attach failed.
User Response: The following is recommended:
1. Verify program xxxxxxxx exists in a STEPLIB data set in the CA-7 execution JCL.
2. Concatenate the CA-11 Load library if it is missing.
3. Reinitialize CA-7.
4. Retry ARTS.
RMS1-82 BLDL FAILED FOR xxxxxxxx

Explanation: ARTS command was attempting to find the CA-11 interface module identified by
xxxxxxxx, but failed.
1. Verify program xxxxxxxx exists in a STEPLIB data set in the CA-7 execution JCL.
2. Concatenate the CA-11 Load library if it is missing.
3. Reinitialize CA-7.
4. Retry ARTS.

5.13 RMS1 Messages
RMS1-83 –RMS1-84
RMS1-83 LINKEDIT OF SASSRMS1 DOES NOT INCLUDE UCC11OCR

Explanation: CA-7 module SASSRMS1 has not been linked with CA-11 module UCC11OCR.
User Response: Follow linkage instructions in the CA-7 Systems Programmer Guide under Inter-
faces.
RMS1-84 ARTS ONLINE MONITOR TERMINATED

Explanation: Unusual completion for ARTS command. If the ARTS command is attempted while
CA-11 is not active, this message is issued.

5.14 RSCx Messages
RSC0-01 –RSCx-05
5.14 RSCx Messages
RSC0-01 VRM SUPPORT NOT ACTIVE

Explanation: VRM support has not been activated.
User Response: Verify that the CA-7 initialization file, DBASE statement includes the RSRC=YES
parameter to activate full Virtual Resource Management support.
RSC0-02 VRM MAINTENANCE SUPPORT ACTIVE

Explanation: The VRM Maintenance Support facility has been activated by specifying the
RSRC=MAINT parameter on the DBASE statement in the CA-7 initialization file.
RSCx-00 xxxxxxxx FUNCTION SUCCESSFUL

Explanation: The specified function was completed without error.
RSCx-01 INVALID MACRO RETURN CODE nn

Explanation: The SASSRSCx module has detected an error on return from a macro. The register
15 value (in hex) is given by nn.
RSCx-02 JOB NOT FOUND

Explanation: The requested job was not found on the CA-7 database.
User Response: Verify that you have specified the correct job name and reissue the request.
RSCx-04 NO RESOURCES DEFINED FOR JOB

Explanation: No virtual resources are connected to the specified job.
RSCx-05 INVALID OR OMITTED xxxxxxxx DATA

Explanation: xxxxxxxx is the parameter that is invalid or omitted.
User Response: Reissue the request with the correct data.

5.14 RSCx Messages
RSCx-08 –RSCx-15
RSCx-08 YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Explanation: A security violation occurred when a user attempted to access a job without proper
authorization (UID security).
User Response: Verify that the user requires access to the job, and if necessary, update the user's
security level to the appropriate level.
RSCx-09 YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Explanation: A security violation occurred when a user attempted a function without proper author-
ization.
User Response: Verify that the user requires access to the indicated function.
RSCx-10 UNRECOGNIZED DATA IN INPUT

Explanation: The input data contained unrecognizable keyword(s) and/or format(s) data for one or
more parameters.
User Response: Reissue the transaction with the correct parameter(s) data.
RSCx-14 ZERO AND NON-ZERO SCHID NOT ALLOWED

Explanation: An attempt was made to update a job to resource connection and an existing resource
already exists with a schedule-ID of zero. A schedule-ID of 0 (zero) applies to all schedule-IDs for a
job.
User Response: If you wish to add a job to resource connection which will only apply to a specific
job schedule-ID, use the add function to make the connection. You cannot update a job to resource
connection when the resource exists on the database with a schedule-ID of 0 (zero).
RSCx-15 DUPLICATE RESOURCE CONNECTED TO JOB

Explanation: An attempt was made to update a job to a resource connection, and a matching
resource connection is already defined.
User Response: Check the spelling of the resource name and the type of resource. Correct and
reissue the command if needed.

Chapter 6. SANx - SJR2
This chapter contains the SANx through SJR2 messages.
Chapter 6. SANx - SJR2 6-1

6.1 SANx Messages
SANx-00 –SANx-05
6.1 SANx Messages
SANx-00 ANALYZE REQUEST COMPLETED AT hh:mm:ss yy.ddd

Explanation: This is an informational message indicating the ANALYZE command has been suc-
cessfully processed.
SANx-01 xxxxxxxx IS AN INVALID FUNCTION

Explanation: An invalid ANALYZE function xxxxxxxx has been specified.
User Response: Check the possible ANALYZE functions in the CA-7 Database Maintenance Guide
and reenter the command.
SANx-02 INVALID OR OMITTED PARAMETER

Explanation: An invalid parameter has been specified or a required parameter has been omitted
from the command.
User Response: Verify the function and parameter values in the CA-7 Database Maintenance Guide
and reenter the command.
SANx-03 xxxxxxxx IS INVALID

Explanation: Keyword xxxxxxxx has an invalid value.
User Response: Verify the keyword values in the CA-7 Database Maintenance Guide and reenter
the command.
SANx-04 OUT OF SPACE ON DATA BASE

Explanation: An out-of-space condition occurred while processing the command.
User Response: Scan the system log for WTO messages identifying which data set is out of space.
Use the SASSBK00 program to back up the database, then expand the allocation for the affected data
set and reload the data set using SASSBK00.
SANx-05 JOB xxxxxxxx NOT FOUND

Explanation: An attempt was made to analyze job xxxxxxxx. This job was not found in the CA-7
database.
User Response: Verify that the job name was specified correctly on the input command. If not,
correct and reenter the command.

6.1 SANx Messages
SANx-06 –SANx-12
SANx-06 UNEXPECTED EOD WIP=xx

Explanation: An unexpected end-of-data occurred while processing the database. xx identifies
where the EOD was received.
SANx-07 SCRATCH WORK FILE SPACE EXCEEDED

Explanation: Scratch work file space has been exhausted in processing the request.
User Response: Review the initialization file DAIO statement, SWFTRK parameter.
SANx-08 READ ERROR HAS OCCURRED WIP=xx RETURN CODE=nn

Explanation: A read error has occurred while accessing the CA-7 database. xx is where the macro
call was issued in the program; nn is the return code from the call.
SANx-09 WRITE ERROR HAS OCCURRED WIP=xx RETURN CODE=nn

Explanation: A write error has occurred while processing the CA-7 database. xx is where the
macro call was issued in the program; nn is the return code from the call.
SANx-10 NO MATCH FOUND FOR GENERIC REQUEST xxxxxxxx

Explanation: In attempting to process a generic request, no matching jobs or data sets were found.
User Response: Verify that the generic name was specified correctly. If not, correct and reenter the
command.
SANx-11 SPACE EXCEEDED IN DATASET DATA SET

Explanation: All data set space has been used in the CA-7 Dataset data set.
User Response: The Dataset data set must be compressed before any new member(s) may be
added. Shut down CA-7 and compress the Dataset data set.
Note: The data set must not be compressed while CA-7 is active.
SANx-12 XREF TABLE SPACE EXCEEDED

Explanation: The incore table used to verify data set cross-reference entries has been exceeded.
User Response: The first 1000 entries will be processed and the command should be executed
again if more entries are to be "cleaned up."

6.1 SANx Messages
SANx-13 –SANx-20
SANx-13 UNMATCHED xxxxxxxx FOR DSnnnnnn, DSN=yyyyyyyy

AND HAS zz USING JOBS
or
AND HAS BEEN DELETED ...TEST RUN
Explanation: This message appears whenever a data set record does not have a proper corre-
sponding IDS entry. The second line of the message indicates the record has jobs using it. The third
line indicates that it has been deleted. TEST RUN indicates no deletion actually has been done
because UPDATE=NO was specified. The xxxxxxxx in the first line may indicate ORIGIN ERROR,
INDEX ENTRY, or DATASET MEMBER to further clarify where the discrepancy existed.
User Response: Using Database Maintenance functions, make the required corrections and delete
the data set record if necessary.
SANx-14 SCRATCH FILE SORT ERROR xx RETURN CODE= nn

Explanation: Error occurred while sorting information. A location code xx is followed by return
code nn from the sort.
User Response: Determine sort error and correct or contact your installation's CA-7 specialist for
assistance.
SANx-15 NODE NOT FOUND... xxxxxxxx

Explanation: A node from a data set name was being searched for on the CA-7 IDS and was not
found.
User Response: Determine whether the node is valid. If it is valid, establish the node on the IDS;
if not, see that it is deleted.
SANx-16 INDEX ERROR HAS OCCURRED WIP=xx RC=nn

Explanation: An error has occurred either in the attempt to TRIG process entries on the Index data
set (IDS) or to perform a TRIG command.
User Response: If xx=D4, the IDS may be full or it may need to be backed up and reloaded.
If xx=C4 and nn=01, check to make sure that the IDS contains at least one entry for each of the
following:
JDEP.
AUTO.
TRGD.
If one does not exist, add a dummy entry and reissue the command. For example, if there are no
data set trigger (AUTO.) entries, add a dummy entry and then try the TRIG command.
SANx-20 ERROR WHILE READ/WRITE OF JOB DATABASE, JOB=xxxxxxxx RC=nnnn WIP=w

Explanation: I/O or parameter error while accessing the CA-7 database. Where:
xxxxxxxx is the job name.
RC is the 4-digit return code.
w is the code identifying where in the program the error occurred.

6.1 SANx Messages
SANx-21 –SANx-40
User Response: Contact your installation's CA-7 specialist for assistance. If the RC is 0 or 4, then
there could be a bad entry for the job in the JOB data set. Do a DUMP,JOB=xxxxxxxx to get
documentation of the problem.
SANx-21 I/O ERROR OCCURRED WHILE PROCESSING JOB DATABASE, WIP= xx RETURN
CODE= nn
Explanation: An I/O error occurred while processing the Job database. xx is where the macro call
was issued in the program; nn is the return code from the call.
SANx-22 MAXJOBS= EXCEEDS LIMIT VALUE

Explanation: A number greater than the limit value in the program was entered.
User Response: Enter a smaller value or contact your installation's CA-7 specialist for assistance.
SANx-23 NUMBER OF JOBS IN QUEUES EXCEEDS MAXJOBS= nn

Explanation: Preliminary examination of the Request, Ready, and Active queues found more jobs
than allowed by the MAXJOBS value.
User Response: Retry with a larger MAXJOBS entry. If the limit value of 4000 was used, wait for
the number of jobs in the queues to decrease.
SANx-25 SECURITY UID MUST BE 255 FOR THIS COMMAND

Explanation: One of the database analyze commands was issued, but the current USERID does not
have a UID level of 255 (allowing access to all jobs).
User Response: Log on to CA-7 with a USERID that has a UID value of 255 and then reissue the
command.
SANx-30 ERROR ON R/W OF DSDS, JOB=xxxxxxxx, DSN=PPnnnnnnnn, RC=rrrr, WIP=w

Explanation: I/O error accessing the Dataset data set. The job referenced by xxxxxxxx refers to
the data set PPnnnnnnnn, but the record was not found. rrrr is the 4-digit return code; w is the code
identifying where in the program the error occurred.
User Response: Reload the job referenced in the message. If the LOAD is unsuccessful, run
UCC7DBVR for diagnostic information.
SANx-40 ERROR WHILE READ/WRITE OF SCRATCH FILE, RC=nnnn, WIP=w

Explanation: An I/O error occurred during access of the scratch queue. w is where the macro call
was issued in the program; nnnn is the return code from the call.
User Response: Verify that the scratch queue has sufficient space allocated. If the problem per-
sists, contact your installation's CA-7 specialist for assistance.

6.1 SANx Messages
SANx-99 –SANx-99
SANx-99 SORT I/O ERROR ON SCRATCH FILE, WIP= xx RETURN CODE= nn

Explanation: An I/O error occurred during a sort operation. xx is where the macro call was issued
in the program; nn is the return code from the call.

6.2 SATO Messages
SATO-01 –SATO-35
6.2 SATO Messages
SATO-01 xx INVALID MACRO RETURN CODE = nnnnnnnn

Explanation: The SASSSATO module has detected an error on return from a macro. The where-
in-program (WIP) value is specified by xx. The register 15 value (in hex) is nnnnnnnn. Values
xx=34, RC=4 indicate the Trailer queue may be full.

AUTO [(JOB=yyyyyyyy)|(DSNBR=zznnnnnn)]
Explanation: This message is issued to the CA-7 Master Station to indicate that job xxxxxxxx
entered the Request queue because of the creation of an AUTO (trigger) data set DSnnnnnn or a
triggering job yyyyyyyy, or the completion of input network NWnnnnnn.
SATO-19 JOB xxxxxxxx(nnnn) ENTERED INTO REQUEST 'Q' TO DUMP LOG FILE
Explanation: Job xxxxxxxx has been automatically scheduled into the Request queue because one
of the CA-7 Log data sets is full.

AUTO [(JOB=yyyyyyyy)|(DSN=bbbbbbbb)]
*** JCL RETRIEVED FROM SPECIAL OVERRIDE LIBRARY ***
Explanation: See SATO-15. The JCL for job xxxxxxxx was retrieved from the special JCL Over-
ride library (JCLID=254).
SATO-35 JOB xxxxxxxx(nnnn) NOT ENTERED INTO REQUEST 'Q'. JOB LOCKED ***
AUTO [(JOB=yyyyyyyy)|(DSNBR=bbbbbbbb)]
Explanation: The indicated job was triggered by creation of a data set, network or completion of a
job, but could not be entered into the Request queue because of a lock. (See message SATO-15.)
User Response: Determine why the job is locked using LLOCK. Make corrections if the job
should be scheduled.

6.2 SATO Messages
SATO-36 –SATO-38
SATO-36 JOB xxxxxxxx(nnnn) NOT ENTERED INTO REQUEST 'Q'.

JOB NOT FOUND ***
AUTO [(JOB=yyyyyyyy)|(DSNBR=bbbbbbbb)] CODE=xxxxyyzz
Explanation: The job was not entered into the Request queue because it was not found in the CA-7
Job data set. Or the job may not have been added to the Request queue because the HIJBNUM
(highest job number) has been reached. This means that CA-7 has no available job numbers to
assign to this job. (See also message SATO-15.)
CODE=xxxxyyzz will indicate the reason for the error. The xxxx is the WIP (Where In Program)
from SASSSCSR. The yy is the return code from a macro call. The zz is the return code from
SASSSCSR, generally this will be 08.
xxxx Description
0014 For yy=00, the Request queue may have filled up. Use /DISPLAY,Q=ALL to check
this.
0016 An error was returned attempting to issue a new CA-7 job number. Check the
HIJBNUM to see if it has been reached.
0044 For yyzz=0108, the CA-7 database probably has many CI/CA splits. REORG the CA-7
database by doing a backup and reload. Of course, CA-7 must be down during the
REORG.
0055 An error was returned attempting to add JCL to the TRLQ. This could indicate a lack of
available space in the TRLQ.
User Response: If the job is to be run, use the Queue Maintenance DEMAND function to cause the
job to be scheduled and submitted for database entries to be built. If the HIJBNUM has been
reached, refer to SPO7-02 for the action.
SATO-37 JOBxxxxxxxx(nnnn) NOT ENTERED INTO REQUEST 'Q'. CODE=cccccccc ***

Explanation: The job was not entered into the Request queue because of the indicated code. (See
also message SATO-15.)
SATO-38 JOB xxxxxxxx(nnnn) NOT ENTERED INTO REQUEST 'Q'. llkkkkjj JCL ***
Explanation: The job was not entered into the Request queue because an error was encountered
trying to process the JCL. The error may have been encountered while CA-7 was attempting to
attach the job's JCL. There may not be enough space in the Trailer queue. llkkkkjj is a return code
describing the error. A jj value of 1C indicates that JCL was not attached for the job. The kkkk
value is the reason code for the attach failure. See message SCNJ-18 for an explanation of this code.
(See also message SATO-15 for a description of the format of this message.)
User Response: Refer to message SCNJ-18 for the corrective action.

6.2 SATO Messages
SATO-39 –SATO-39
SATO-39 JOB xxxxxxxx(nnnn) NOT ENTERED INTO REQUEST 'Q'. llkkkjj JCL ***
Explanation: The job was not entered into the Request queue because an error was encountered
trying to process the JCL retrieved from the special JCL Override library (JCLID=254). llkkkkjj is a
return code describing the error. A jj value of 1C indicates that JCL was not attached for the job.
The kkkk value is the reason code for the attach failure. See message SCNJ-18 for an explanation of
this code. (See also message SATO-15 for a description of the format of this message.)
User Response: Review and correct the JCL from the special JCL Override library. Replace the
JCL member in the special library and then DEMAND the job.

6.3 SCMx Through SCM9 Messages
SCMx-00 –SCMx-10
SCMx-00 xxxxxxxx COMPLETED AT hh:mm:ss ON yy.ddd

Explanation: Command xxxxxxx was completed at the date and time noted.
SCMx-02 xxxxxxxx=yyyyyyyy NOT FOUND

Explanation: Value yyyyyyyy for keyword xxxxxxxx is not known to CA-7.
User Response: Correct and resubmit the command.
SCMx-03 REQUIRED INPUT MISSING

Explanation: A required input keyword is missing from the command.
User Response: Refer to command format in CA-7 Commands Guide or HELP facility to determine
required keywords for the command issued. Enter required input and reissue the command.
SCMx-04 CONFLICTING INPUT PARAMETERS

Explanation: Mutually exclusive keywords were input with the command.
User Response: Refer to command format in CA-7 Commands Guide or HELP facility to determine
required keywords for the command issued. Enter required input and reissue the command.
SCMx-05 INVALID OR OMITTED xxxxxxxx=yyyyyyyy

Explanation: Value yyyyyyyy for keyword xxxxxxxx is invalid or is required but was not speci-
fied.
SCMx-06 DCB/ACB FAILED OPEN/CLOSE, RC=

Explanation: The /OPEN or /CLOSE command for a GROUP failed. The return code (RC=) is the
contents of register 15 from CA-7's subtask after the open or close. (See also CA-7.V001.)
User Response: For VTAM groups, verify the APPL parameter of the UCC7VTAM initialization
file statement. Match the name of the APPL macro used to define CA-7 to VTAM. For other
groups, verify that proper DD statements have been specified.
SCMx-10 FUNCTION NOT AVAILABLE -- RETRY LATER

Explanation: A /WLB,SET=OFF command was entered.
User Response: Enter a /WLB,SET=ON command to reactivate workload balancing.

SCMx-22 –SCMK-06
SCMx-22 xxxxxxxx IS NOT LOGGED ON, MESSAGE NOT SENT

Explanation: The specified user is not logged on to CA-7 so the message was not queued to a
logical terminal.
SCMx-40 COMMAND xxxxxxxx IS NOT VALID FOR THIS TERMINAL.

Explanation: The command xxxxxxxx can not be used from the current CA-7 terminal. Certain
commands may only be entered from native VTAM access to CA-7.
User Response: To enter the command, you must use a terminal that supports that command.
SCMx-99 INVALID ERROR CODE

Explanation: An error code was specified by module SASSSCMx, but there is no error message
defined for that code.
SCMJ-00 nnnn MESSAGES PURGED FROM LTERM=xxxxxxxx

Explanation: A request to purge pages of queued output was successfully completed.
SCMJ-01 xx INVALID MACRO RETURN CODE hhhhhhhh

Explanation: An unexpected error occurred while processing the purge page request. The xx iden-
tifies the macro call and the hhhhhhhh is the return value in register 15.
SCMJ-15 NO PURGETERM=xxxxxxxx CONNECTED TO LTERM=yyyyyyyy

Explanation: An attempt was made to purge messages queued to a logical terminal while its phys-
ical terminal was being used by a different logical terminal.
User Response: Wait a few minutes and then reenter the command. If the response continues and
you can determine that the terminal is not in use, issue a /LOGOFF or a /STOP for the terminal and
then retry the PURGPG.
SCMK-06 DDNAME FAILED OPEN/CLOSE RC=8

Explanation: The ddname indicated has failed either an OPEN or CLOSE.
User Response: Try again. If the problem persists, contact your installation's CA-7 specialist for
assistance.

SCMK-07 –SCMP-49
SCMK-07 SUBSYSTEM THREAD CLEANUP COMPLETE xxx...x

Explanation: /OPEN request for SUBSYS forced thread cleanup with an attempt to establish sub-
system interface. Second line of message (xxx...x) is documented in CA-7 RPT Systems Programmer
Guide.
User Response: Refer to message documented in CA-7 RPT Systems Programmer Guide.
SCMK-11 INIT MODULE (SASSINRP) NOT FOUND

Explanation: /OPEN request for SUBSYS could not find initialization module SASSINRP.
User Response: Probable user error. Modules SASSINRP and SASSCHDR must be in a library in
the STEPLIB concatenation and the SVCNO statement in the initialization file must indicate
SASSVC=YES. If subsystem defined at your site, try shutdown and restart of CA-7. If problem
persists, contact your installation's CA-7 RPT specialist for assistance.
SCMK-11 SPECIFIED SUBSYS NAME NOT DEFINED

Explanation: /OPEN request for SUBSYS was issued but name did not match value specified from
initialization.
User Response: Verify SUBSYS parameter of DBASE statement in initialization file and then retry.
SCMO-02 OPERATOR ID NOT SPECIFIED

Explanation: The operator ID (ID=) keyword is required.
User Response: Specify the ID= keyword and reissue the command.
SCMP-00 PROCESSING COMPLETE FOR .... /pa or /pf command string .....
Explanation: The /PAnn or /PFnn command has been processed successfully.
User Response: None required. Issue /DISPLAY,ST=KEY to view your current session PA/PF key
settings.
SCMP-48 PROFILE RECORD NOT FOUND - NO ACTION TAKEN

Explanation: The requested action cannot be performed because no CA-7 profile record was found
in the database.
User Response: Use the /PROF command to define a CA-7 profile record. If you are using
/PROFS command, check to ensure you entered the correct CA-7 userid on the ID= keyword.
SCMP-49 NO PFKEYS DEFINED IN PROFILE - NO ACTION TAKEN.

Explanation: A /PROF(S),KEYS=PROFILE request cannot be satisfied because the CA-7 profile
record has no PA/PF key definitions.
User Response: Use the /PROF command to display the contents of your CA-7 profile. If you
wish to clear the PA/PF key settings in your current terminal session, use the /PF99 command.

SCMP-50 –SCMP-57
SCMP-50 ID= KEYWORD ONLY VALID WITH /PROFS COMMAND.

Explanation: A /PROF command was entered with the ID= keyword.
User Response: Use the /PROFS command if you wish to display or update another user's CA-7
profile.
SCMP-51 CURRENT SESSION REFRESHED WITH PFKEYS FROM PROFILE.

Explanation: The PA/PF key definitions for your current terminal session have been replaced with
the definitions in your CA-7 profile. If you are using the /PROFS,ID= format your keys have been
replaced by those in the ID= user's CA-7 profile.
User Response: None required. Use the /DISPLAY,ST=KEY command to view your current ter-
minal session PA/PF key settings.
SCMP-52 PROFILE RECORD UPDATED FOR XXXXXXXX

Explanation: The PA/PF key definitions and/or the UID resource name in the CA-7 profile for user
xxxxxxx have been successfully updated.
User Response: None required. Use the /PROF or /PROFS,ID= command to display the contents
of the CA-7 user profile.
SCMP-53 PROFILE RECORD DELETED FOR XXXXXXXX

Explanation: The CA-7 profile record for user xxxxxxxx has been deleted from the database. This
is in response to a /PROF(S),ST=DELETE command.
User Response: None required.
SCMP-54 KEYS= AND/OR R= KEYWORDS INVALID WITH STATUS=DELETE.

Explanation: A /PROF(S),ST=DELETE command was entered with the KEYS= and/or R=
keywords. These are conflicting options since, in effect, you are asking to both update and delete the
profile record.
User Response: If you wish to delete the profile record, use only the STATUS=DELETE operand.
If you wish to update or access the profile record, use the KEYS= and/or R= keywords.
SMCP-55 PROFILE I/O ERROR. USER=uuuuuuuu FUNC=ff RC=rr FDBK=kkkk

Explanation: A database error was encountered attempting to access or act on the CA-7 profile
record for user uuuuuuuu. The IO function (ff) return code (rr) and feedback code (kkkk) are listed.
User Response: Consult your CA-7 specialist.
SCMP-57 INVALID PA/PF KEY SPECIFIED.

Explanation: A /PA or /PF command was entered for an undefined PA or PF key.
User Response: Valid PA keys are PA01 - PA03. Valid PF keys are PF01 - PF24. The special
command /PF99 causes any PA/PF keys defined for the current terminal session to be deleted.

SCMP-58 –SCMQ-65
SCMP-58 MISMATCHED PARENTHESES ON MSG= OPERAND.

Explanation: A /PA or /PF command was entered with unbalanced parentheses in the text associ-
ated with the MSG= or M= keyword.
User Response: Ensure the parentheses on the MSG= parameter are balanced. The maximum
length of the MSG= parameter is 60 characters (including parentheses).
SCMP-59 MSG= VALUE INVALID. MAX LENGTH IS 60.

Explanation: A /PA or /PF command was entered with invalid data in the MSG= or M= parameter.
User Response: The maximum length of the MSG= parameter is 60 characters (including paren-
theses).
SCMP-60 NO PA/PFKEYS DEFINED FOR CURRENT TERMINAL SESSION.

USE KEYS=CLEAR TO DELETE.
Explanation: A /PROF(S) command was entered with the KEYS=SAVE parameter; however, there
are no PA or PF keys defined for the current terminal session.
User Response: If the intent is to clear the PA/PF key definitions in the profile record, use the
/PROF,KEYS=CLEAR command. If you wish to add PA/PF key definitions to the profile you must
first define them to your current terminal session using the /PA and/or /PF commands.
SCMP-61 MSG= KEYWORD REQUIRED WITH /PA OR /PF COMMAND.

Explanation: A /PA or /PF command was entered without any MSG= or M= keyword.
User Response: The MSG= (or M=) keyword is required. If you wish to get rid of a current
definition, use the MSG= keyword with no command text.
SCMP-62 KEYS= OPTION INVALID. VALID OPTIONS ARE: SAVE, PROFILE AND CLEAR.
Explanation: A /PROF(S) command was entered with the KEYS= (or K=) keyword, but the param-
eter is invalid.
User Response: The valid options for the KEYS= keyword are: SAVE, PROFILE, and CLEAR.
SCMP-63 PROGRAM LOGIC ERROR AT LABEL xxxxxxxx

Explanation: A program logic error occurred attempting to satisfy a /PF, /PA, or /PROF(S)
command at label xxxxxxxx.
SCMQ-65 ERROR: KEYWORD MISSING OR INVALID: xxxxxxxx

Explanation: Keyword xxxxxxxx was incorrectly specified, or is not allowed on the /JCL
command.
User Response: Correct the /JCL command and reenter.

SCMQ-66 –SCMQ-75
SCMQ-66 ERROR: ADD REQUESTED BY INDEX ALREADY DEFINED.

Explanation: An attempt was made to add a JCL library with an index which already exists.
User Response: Select a different index and reenter.
SCMQ-68 ERROR: UPD REQUESTED BUT INDEX NOT FOUND.

Explanation: An update or delete was attempted for a JCL library index does not exist.
User Response: Determine the correct JCL library index and reenter.
SCMQ-69 ERROR: VSAM I/O UNSUCCESSFUL. FUNC=xx RC=xxxx FDBK=xxxx

Explanation: An error occurred during I/O to the JCL library database.
SCMQ-71 ERROR: UPD REQUESTED BUT ENTRY IN USE.

Explanation: An update was attempted for a JCL library index which is currently allocated.
User Response: Wait until the requested JCL library index is not in use and reenter.
SCMQ-72 ERROR: DEL REQUESTED BUT ENTRY IN USE.

Explanation: A delete was attempted for a JCL library index which is currently allocated.
User Response: Wait until the requested JCL library index is not in use and reenter.
SCMQ-73 ERROR: INVALID OPERATION ON HELP LIBRARY

Explanation: The requested action is not valid on the HELP library.
SCMQ-74 WARNING! JCL INDEX DELETED IS REFERRED TO AS AN ALTERNATE.

Explanation: The /JCL command was used to delete a JCL library definition. Another JCL defi-
nition referred to the index as an alternate.
User Response: Review the JCL library definitions using /DISPLAY,ST=JCLVAR. Use /JCL to
remove ALT references to the deleted index.
SCMQ-75 CANNOT USE /JCL WITHOUT DYNAMIC ALLOCATION OF JCL LIBRARIES.

Explanation: The /JCL command was attempted, but dynamic allocation of JCL libraries is not
supported.
User Response: Change the PERFORM values on the INIT statement in the CA-7 initialization file
so that dynamic allocation will be used for JCL libraries. Refer to the CA-7 Systems Programmer
Guide for details.

SCM0-00 –SCM0-77
SCM0-00 MSG FROM TERM - xxxxxxxx

text...
Explanation: This message precedes free-form message text sent from terminal xxxxxxxx.
SCM0-11 [(TERM)|(LTERM)] = yyyyyyyy IS NOT AVAILABLE FOR OUTPUT

Explanation: Terminal yyyyyyyy is currently closed and cannot receive the message being sent or
copied.
User Response: To send output to the closed terminal, the terminal must be started using /START
command. Then reenter the original command.
SCM0-12 HARDCOPY DEVICE NOT FOUND.

Explanation: PF2 (Program Function key 2) or the /COPY command was used to copy a page of
output from a 3270 terminal to a hardcopy terminal. To use this facility, a hardcopy terminal must
be present on the same line as the terminal issuing the command.
User Response: If it is necessary to copy the page, the /COPY command must be used to indicate a
specific terminal where the page is to be sent.
SCM0-14 MESSAGE HAS BEEN QUEUED ON LTERM xxxxxxxx

Explanation: This message will be displayed at the sending terminal to indicate transfer of the
output was successful. The receiving terminal, however, is busy; the output has been queued for
review as soon as the receiving terminal is available.
SCM0-17 PROCESSING COMPLETE FOR /SWAP

Explanation: The /SWAP command processing was completed.
SCM0-22 xxxxxxxx IS NOT LOGGED ON, MESSAGE NOT SENT.

Explanation: The /MSG command was issued using ID=xxxxxxxx, but the USERID is not cur-
rently logged on.
SCM0-77 /FETCH SERVICE UNAVAILABLE

Explanation: Could not locate the SASSCMDM module.
User Response: Ensure that the SASSCMDM module resides in a load library accessible to CA-7.

SCM0-78 –SCM1-06
SCM0-78 NO COMMAND RING ESTABLISHED

Explanation: No command ring has been built for this terminal yet. This will occur if /FETCH is
entered immediately after a /LOGON.
User Response: /FETCH will not be stored in the command ring. Enter a command other than
/FETCH, /LOGON, /PAGE, or /ECHO to initialize the command ring.
SCM0-79 /FETCH STORAGE LIMIT EXCEEDED

Explanation: /FETCH exceeded an internal limit on the amount of storage allowed for the service.
User Response: This should not occur in normal operation. If the problem persists, contact your
SCM1-00 LINE=xxxxxxxx HAS BEEN [(STOPPED)|(STARTED)]

Explanation: The request to start or stop a line has been successfully completed.
SCM1-00 TERM=xxxxxxxx HAS BEEN [(STOPPED)|(STARTED)]

Explanation: The request to start or stop a specific real (physical) terminal has been successfully
completed.
SCM1-00 LTERM=xxxxxxxx HAS BEEN [(STOPPED)|(STARTED)]

Explanation: The request to start or stop a specific logical terminal has been successfully com-
pleted.
SCM1-00 LINE=xxxxxxxx TERM=yyyyyyyy HAS BEEN [(STOPPED)|(STARTED)]

Explanation: The request to start or stop a line and terminals on that line has been successfully
completed.
SCM1-00 PROMPTS FOR LTERM=xxxxxxxx HAVE BEEN [(STOPPED)|(STARTED)]

Explanation: Prompting for the logical terminal indicated by LTERM has been either stopped or
restarted by a /START or /STOP command with MSG=PROMPTS specified.
SCM1-06 SHUTDOWN IS IN PROGRESS CANNOT START

Explanation: Shutdown of CA-7 is in progress; the request to start a line, terminal, or logical ter-
minal cannot be honored.

SCM1-10 –SCM2-15
SCM1-10 STOP/START INVALID, CODE=y

Explanation: If y=A, an attempt was made to stop or start a terminal that was in the middle of
processing a command. Terminal may have been processing a CA-7 CA-11 interface command, such
as ARTS. If y=B, a /START was issued to a VTAM terminal not connected to CA-7.
User Response: If y=A, let the terminal complete its activity, then reissue the command. If the
problem resulted from the CA-7 CA-11 interface, the link of the SASSRMS1 and SASSRMS2
modules may not have been done correctly. If y=B, issue the /OPEN command first and then issue a
/START. If terminal does not connect, bring CA-7 down and then bring it back up with a
TYPE=ERST initialization.
SCM2-10 /SHUTDOWN MAY BE ENTERED FROM CA-7 MASTER TERMINAL ONLY.

/SHUTDOWN IGNORED.
Explanation: The CA-7 /SHUTDOWN command can be input at the CA-7 Master Terminal only.
User Response: Enter command from the Master Terminal.
SCM2-11 BATCH RUN IN PROGRESS

Explanation: CA-7 cannot be shut down while a batch terminal is in process.
User Response: Wait for the batch terminal run to complete and then reenter the /SHUTDOWN
command. The /DISPLAY,T=ALL command will provide status about the batch terminal. When it
shows "stopped," reenter the /SHUTDOWN command. Batch terminals may be ignored by using a
different shutdown option.
SCM2-12 TERMINAL xxxxxxxx IS BUSY /LOGOFF IGNORED

Explanation: Terminal xxxxxxxx is busy and cannot be logged off.
User Response: Wait a few seconds, then retry the logoff.
SCM2-13 TERMINAL xxxxxxxx IS ALREADY LOGGED OFF /LOGOFF IGNORED

Explanation: Terminal xxxxxxxx is already logged off.
SCM2-14 TERMINAL xxxxxxxx HAS BEEN LOGGED OFF

Explanation: The request to log off terminal xxxxxxxx has been processed.
SCM2-15 TERMINAL xxxxxxxx REQUIRED INTERVENTION /LOGOFF IGNORED

Explanation: Intervention is required to process previous output to terminal xxxxxxxx. The forced
logoff was ignored.
User Response: Place the device in "Ready." If the device still requires intervention, issue a
/STOP,T=xxxxxxxx to stop the terminal. If the device was made ready and is not a printer, the
/LOGOFF,T=xxxxxxxx may be reissued.

SCM2-16 –SCM2-30
SCM2-16 TERMINAL xxxxxxxx IS A BATCH TERMINAL. /LOGOFF IGNORED

Explanation: Terminal xxxxxxxx is a batch terminal and cannot be forced to log off.
SCM2-17 TERMINAL xxxxxxxx IS A PRINTER. /LOGOFF IGNORED

Explanation: Printer terminals cannot be forced to log off.
User Response: Place the device in "Ready." If the device still requires intervention, issue a
/STOP,T=xxxxxxxx to stop the terminal. If the device was made ready and is not a printer, the
/LOGOFF,T=xxxxxxxx may be reissued.
SCM2-18 /SHUTDOWN FORMAT INCORRECT

Explanation: An invalid shutdown option was entered. A /SHUTDOWN may be done with no
options or one of the following. DMPQ, Z1, Z2, Z3, Z4, or Z5.
User Response: Correct the /SHUTDOWN command and reenter.
SCM2-19 INVALID SHUTDOWN OPTION. /SHUTDOWN IGNORED

Explanation: An invalid option was entered from the /SHUTDOWN command. The command is
ignored.
User Response: Reenter the command correctly.
SCM2-20 INVALID COMMAND - MUST BE /SHUTDOWN

Explanation: After CA-7 is in shutdown mode, the terminal that entered the /SHUTDOWN cannot
enter most of the other commands. This message can also be produced if the /SHUTDOWN is
entered when CA-7 is already in the process of shutting down.
User Response: Reenter the /SHUTDOWN command or one of the other valid commands that are
allowed during shutdown. If the shutdown process is in progress, do not reenter the /SHUTDOWN.
SCM2-25 SHUTDOWN ALREADY IN PROGRESS

Explanation: Shutdown has already been entered from another terminal.
User Response: None - CA-7 will shut down shortly.
SCM2-30 SHUTDOWN TO BE DONE WITH THE FOLLOWING OPTIONS.

xxxxxx,xxxxxx,xxxxxx,xxxxxx
PRESS ENTER TO VERIFY
Explanation: The xxxxxx's indicate the options for the shutdown command entered. CA-7 is put in
shutdown mode.
User Response: If these are the shutdown options desired, press Enter and CA-7 will be shut
down. If different options are desired, reenter the command. You will receive this message until
Enter is pressed or two consecutive shutdown commands are entered with the same options.

SCM2-32 –SCM4-15
SCM2-32 /SHUTDOWN INVALID FROM APPLICATION VTAM TERMINAL

/SHUTDOWN IGNORED
Explanation: A /SHUTDOWN request from an ISPF session will not be honored.
User Response: None. This message is informational.
SCM2-33 /SHUTDOWN INVALID FROM TRAILER TERMINAL

/SHUTDOWN IGNORED
Explanation: A /SHUTDOWN request from U7SVC or SASSTRLR will not be honored.
SCM4-00 MAINID=xxx ASSIGNED TO CPU yyyyyyyy FROM CPU zzzzzzzz

Explanation: The request to change the assignment of a main ID from CPU zzzzzzzz to CPU
yyyyyyyy has completed successfully.
SCM4-00 LTERM=xxxxxxxx ASSIGNED TO TERM=yyyyyyyy FROM TERM=zzzzzzzz.

Explanation: The request to change the assignment of a logical terminal from one physical terminal
zzzzzzzz to another yyyyyyyy has completed successfully.
SCM4-13 LTERM=xxxxxxxx NOT ASSIGNED, DEVICE TYPE CONFLICT.

Explanation: The request to assign a logical terminal from one physical device to another cannot be
completed because the "from" and "to" devices are different types.
User Response: Reissue the /ASSIGN command specifying a "to" terminal of the same device type
as the real terminal to which the logical terminal is currently assigned.
SCM4-14 LTERM=xxxxxxxx NOT ASSIGNED, CONNECTION FIXED

Explanation: The logical terminal (LTERM) and the "from" physical terminal have the same name.
This is defined in the initialization file and is done to ensure that every physical terminal has at least
one logical terminal with which CA-7 can communicate.
SCM4-15 LTERM=xxxxxxxx NOT ASSIGNED, TERM=yyyyyyyy IS CONNECTED

Explanation: The terminal to be reassigned is currently busy.
User Response: Wait a few minutes and then retry the /ASSIGN. If the situation persists and the
terminal is not in use, it may be logged off and the /ASSIGN retried.

SCM5-00 –SCM7-00
SCM5-00 PRTY=nn FOR APPL=xxxxxxxx AT TERM=yyyyyyyy FOR OPERID=zzzzzzzz, CHANGED

TO PRTY=mm
Explanation: The request to change application function authority for the specified operator ID,
terminal and application has been successfully completed.
User Response: The operator must log on again for the change to become effective.
SCM5-00 USERID=nnn AT TERM=xxxxxxxx FOR OPERID=yyyyyyyy CHANGED TO USERID=mmm

Explanation: The request to change a UID for the specified operator ID and the terminal has been
successfully completed.
User Response: The operator must log on again for the change to become effective.
SCM5-12 OPERID-xxxxxxxx NOT AUTHORIZED FOR TERM=yyyyyyyy

Explanation: A request to change application function authorization or user ID cannot be completed
because operator ID xxxxxxxx is not authorized for terminal yyyyyyyy.
User Response: Verify that the operator ID and terminal name were specified correctly on the input
request. If not, correct and reenter the command. If the original command was correct, the CA-7
initialization file must be changed to authorize the operator ID for the terminal.
SCM5-13 APPL=xxxxxxxx NOT AVAILABLE TO OPERID=yyyyyyyy

Explanation: A request to change application function authorization cannot be completed because
operator ID yyyyyyyy is not authorized for application xxxxxxxx.
User Response: Verify that the operator ID and application name were specified correctly on the
input request. If not, correct and resubmit the command. If the original command was correct, the
CA-7 initialization file must be changed to authorize the operator ID for the application.
SCM5-14 /CHANGE NOT VALID FOR OPID WITH TRMID=**ALL**

Explanation: A /CHANGE command has been entered for an OPID that had global security
defined.
User Response: If you want to change security for OPID with a global security definition, use a
TERM (or T)=**ALL** on the /CHANGE command.
SCM6-00 /DISPLAY COMPLETED AT hh:mm:ss ON yy.ddd

Explanation: The input request was successfully completed.
SCM7-00 /LOG COMPLETED AT hh:mm:ss ON yy.ddd

Explanation: The input request was successfully completed.

SCM8-00 –SCM9-15
SCM8-00 xxxxxxxx=yyyyyyyy SET FOR RELINK, USE COUNT=nnn, BLDL NAME=zzzzzzzz

Explanation: The CA-7 application or format block (specified by yyyyyyyy) has been flagged as
ready for relinking. The new version will be loaded when the use count (nnn) is zero (that is, the old
version of the module is not in use by any program currently executing). The new version will be
loaded with the name specified by zzzzzzzz.
Note: If a user ID was specified on the /RELINK command, that value will be used as the first 2
characters of the BLDL name.
SCM8-02 INVALID TRANSACTION

Explanation: An attempt was made to do an online /RELINK of a module.
User Response: This module cannot be relinked online. CA-7 must be shut down and brought
back up with a TYPE=WARM to bring in a new copy of the requested module. A /RELINK cannot
be done for a module marked RESD, or PERM, nor a module that is part of the CA-7 nucleus.
SCM8-11 xxxxxxxx=yyyyyyyy IS PERMANENTLY RESIDENT

Explanation: The CA-7 application or format block to be relinked is either part of the CA-7
nucleus or is marked as permanently resident on the APPLCTN/FMTBLK statement in the CA-7
User Response: If the module is part of the CA-7 nucleus, then CA-7 must be relinked and CA-7
must be shut down and reinitialized. If marked as permanently resident in the initialization file, then
CA-7 must be restarted before the new version can be used.
SCM9-13 COMMAND INVALID FOR INTERNAL SECURITY.

Explanation: This message is issued when the /UID command is entered and external security is
not controlling CA-7 LOGON and COMMAND security.
User Response: Verify that your current external security environment is controlling CA-7 logons
and command security. Check the SECURITY statement, keyword EXTERNAL=, in the CA-7
initialization file for your current external security options.
SCM9-14 RESOURCE NAME IS REQUIRED

Explanation: The /UID command was issued without specifying a resource name.
SCM9-15 CA-7 RESOURCE TABLE NOT FOUND

Explanation: The /UID command was issued but a UID resource table was not specified or loaded
during CA-7 initialization. A UID resource table is required when using the /UID command.
User Response: Ensure that a resource table name was specified in the CA-7 initialization file on
the SECURITY statement using the UID= parameter.

SCM9-16 –SCM9-35
SCM9-16 INVALID FORMAT FOR CA-7 RESOURCE TABLE.

Explanation: An error was encountered when reading the CA-7 UID resource table.
User Response: A UID resource table is required when using the /UID command. Ensure that the
UID resource table specified in the initialization file was built using the CA7RTBL macro.
SCM9-17 RESOURCE (xxxxxxxx) NOT FOUND IN CA-7 RESOURCE TABLE

Explanation: The resource name specified on the /UID command was not found in the UID
resource table.
User Response: Reissue the command using a valid resource name that exists in the UID resource
table.
SCM9-18 ACCESS TO RESOURCE (xxxxxxxx) DENIED BY EXTERNAL SECURITY

Explanation: The user is not authorized to access the resource specified on the /UID command.
User Response: Ensure that the resource is defined to external security and determine if the user
should have access to the indicated resource.
SCM9-21 UID VALUE UPDATED

Explanation: The /UID command was processed and the user's CA-7 UID security level was
updated for this session in CA-7.
SCM9-32 UID RESOURCE TABLE REFRESHED

Explanation: The UID resource table has been successfully refreshed in storage using the
/REFRESH command.
SCM9-33 MODULE NAME REQUIRED FOR REFRESH.

Explanation: The /REFRESH command was issued without specifying a module name on the
command.
User Response: Reissue the command and specify a UID resource table module name. For
example: /REFRESH,MOD=XXXXXXXX.
SCM9-34 MODULE XXXXXXXX NOT FOUND FOR REFRESH

Explanation: The module name specified on the /REFRESH command could not be found.
User Response: Ensure that the module exists and resides in a library accessible to CA-7.
SCM9-35 NO STORAGE AVAILABLE FOR RESOURCE TABLE

Explanation: An attempt was made to refresh the in-storage UID resource table; however, the
storage for the new copy could not be obtained.

SCM9-36 –SCM9-36
SCM9-36 UNABLE TO FREE STORAGE DURING REFRESH

Explanation: An error occurred while freeing storage for the old copy of the UID resource table.

6.4 SCNI Through SCN0 Messages
SCNI-01 –SCNI-14
SCNI-01 xx INVALID SGET RETURN CODE=nn

Explanation: An error was encountered by SASSSCNI while issuing a CA-7 macro. The macro
statement where the error occurred is indicated by xx; nn is the return code from the call. This
message will be issued if the Preprocess queue is full. If the PREQ is full, the XPRE command can
be used to list and then cancel any unneeded input network stations.
SCNI-07 LOAD ERROR FOR xxxxxxxx WITH RETURN CODE nn

Explanation: An attempt to load the module indicated by xxxxxxxx has failed. The return code
from the SLOAD macro is indicated by nn; nn=04 indicates module not found; nn=12 indicates an
I/O error occurred.
User Response: Verify that the module indicated has not been inadvertently deleted from a
CA-7.LOADLIB, and that the APPLCTN statement is present (and correct) in the CA-7 initialization
file or in the SASSPROG module. If the problem persists, contact your installation's CA-7 specialist
for assistance.
SCNI-11 PRE-PROCESS SCHEDULE SCAN STARTED AT hh:mm:ss ON yy.ddd.

Explanation: Scanning of preprocess schedules has started for work to be performed during the
time interval being scanned.
SCNI-12 nnnn RECORDS ADDED TO THE PRE-PROCESS QUEUE.

Explanation: This is an informational message indicating the number of workstation records added
to the Preprocess queue during this scan interval.
SCNI-13 PRE-PROCESS SCHEDULE SCAN COMPLETED AT hh:mm:ss ON yy.ddd.

Explanation: This is an informational message indicating that the scan of preprocess schedules is
complete.
SCNI-14 NETWORK (nnnn) ENTERED INTO PRE-PROCESS 'Q' FOR mm STATIONS

Explanation: This is an informational message which will appear at the CA-7 Master Station for
each record entered into the Preprocess queue. nnnn is the CA-7 assigned job number for the pre-
process activity; mm is the number of stations for this network.

SCNI-40 –SCNJ-07
SCNI-40 SCHEDULE EXPIRED FOR NETWORK SCHD SIxxxxxx

Explanation: This message appears at the CA-7 Master Station for each network schedule that is
found to be expired. The messages are produced each time schedule scan runs. The xxxxxx is the
schedule number (DSNBR) of the network.
User Response: The network schedule should be resolved. The network name can be found by
doing an LSCHD,DSNBR=SIxxxxxx.
SCNI-41 TOTAL NETWORK SCHD EXPIRED = xxxx

Explanation: At least one SCNI-40 message has been produced, and this reflects the number of
them that were produced for this cycle of schedule scan. Only the first five expired schedules will be
shown with the SCNI-40 messages.
User Response: If xxxx is greater than 5, then do an LSCHD,DSNBR=SI*,ST=EXP to determine
which schedules need to be resolved.
SCNJ-01 xx INVALID SGET RETURN CODE=nn. JOB=yyyyyyyy

Explanation: The major reason for this error is a problem was encountered in trying to get a
member from the database.
xx - the macro statement where the error occurred.
nn is the return code from the call.
yyyyyyyy is the job that was being processed by Schedule Scan.
If xx=22 and nn=04, the HIJBNUM parameter on the SCHEDULE statement may have been reached.
1. If xx=22 and nn=04, refer to SPO7-02 for more details.
2. If xx=48, then a bad job member in the CA-7 Job data set was detected. The indicated job may
have to be deleted and and readded. It must be reloaded before the job can be run by CA-7.
Also, job prose, schedules, and JOBCONN connections may have to be reentered.
3. If xx=85, then the Trailer queue may be full.
SCNJ-07 LOAD ERROR FOR xxxxxxxx WITH RETURN CODE nn

Explanation: An attempt to load module xxxxxxxx has failed. The return code from the SLOAD
macro is indicated by nn; nn=4 indicates module not found; nn=12 indicates an I/O error.
User Response: Verify that the module has not been inadvertently deleted from CA-7.LOADLIB
and that the APPLCTN statement is present (and correct) in the CA-7 initialization file or in the
module SASSPROG. If the problem persists, contact your installation's CA-7 specialist.

SCNJ-11 –SCNJ-15
SCNJ-11 JOB SCHEDULE SCAN STARTED AT hh:mm ON yy.ddd.

Explanation: This is an informational message indicating that a scan of jobs has been started.
SCNJ-12 nnnn JOBS ADDED TO REQUEST QUEUE.

Explanation: This is an informational message indicating the number of job records (nnnn) which
were added to the Request queue during this scan.
SCNJ-13 JOB SCHEDULE SCAN COMPLETED AT hh:mm ON yy.ddd.

SCNJ-14 JOB xxxxxxxx (nnnn) ENTERED INTO REQUEST 'Q',

or
JOB xxxxxxxx (nnnn) ENTERED INTO REQUEST 'Q',
DUE-OUT ON yy.ddd AT hh:mm
Explanation: This is an informational message which will appear on the CA-7 Master Station for
each job added to the Request queue. The job name is indicated by xxxxxxxx and the CA-7 job
number is indicated by nnnn. If the JCL has been retrieved from the special JCL Override library
(JCLID 254), this will be indicated. The due-out date and time specifies when CPU processing must
be completed.
SCNJ-15 JOB xxxxxxxx NOT ENTERED INTO REQUEST 'Q'

***JOB LOCKED*** DUE-OUT ON yy.ddd AT hh:mm
Explanation: According to the job schedule member, the job's processing cycle has arrived and it
should be added to the Request queue. However, the job is in locked status and therefore cannot be
scheduled. The due-out time specifies when the job must be completed.
User Response: The LLOCK command should be used to determine why the job is in a locked
status. If scheduling is desired, the reason(s) for the lock must be corrected. Schedule Resolution
must be rerun if the schedule definition is altered. The job may have to be manually DEMANDed
into the queue for the current cycle, depending on the reason it is locked.

SCNJ-16 –SCNJ-18

***NXTCYC=SKP*** DUE-OUT ON yy.ddd AT hh:mm:ss
Explanation: Job xxxxxxxx is scheduled to start during the time span just searched by Schedule
Scan. It was not entered into the Request queue, however, because the next cycle flag indicates skip
one cycle.
User Response: None. The next cycle indicator will be reset automatically and the job will be
scheduled when its next processing cycle occurs.

***NXTCYC=OFF*** DUE-OUT ON yy.ddd AT hh:mm:ss
Explanation: Job xxxxxxxx is scheduled to start during the time span just searched by Schedule
Scan. It was not entered into the Request queue, however, because the next cycle flag indicates
normal scheduling is to be bypassed indefinitely.
User Response: None. The next cycle indicator must be manually reset before normal scheduling
will be resumed.

***JCL (kkkk)*** DUE-OUT ON yy.ddd AT hh:mm:ss
Explanation: The job was not entered into the Request queue because the JCL could not be
attached. kkkk indicates the reason, as follows:
0004 Empty member.
0008 Member not found on CA-7 CA-LIBRARIAN or CA-PANVALET libraries; or JCL INDEX
not specified. Also, if a CA-7 CA-LIBRARIAN or CA-PANVALET data set, it has been
unavailable for two minutes.
000C JCL data set not found on DASD volume.
0010 JCL data set is not a PDS - invalid DSORG.
0014 JCL data set has invalid DCB attributes.
0018 JCL data set resides on a DASD volume not accessible to CA-7.
001C JCL member not found in data set.
0020 READ I/O error was encountered.
0024 JCL data set is READ password protected.
0028 JCL data set is USERID protected or CA-7 does not have access to the JCL data set when
external security is used for data sets.
0054 Data set is busy.
005C Dynamic allocation for JCL data set failed.
0060 Error occurred during OPEN. The DCBABCOD field is nonzero.
007C JCLID is not in the CA-7 initialization file.
0080 Problem with interface to CA-LIBRARIAN or CA-PANVALET.

SCNJ-18 –SCNJ-18
0084 EOF reached in SQADD. The job may have too many lines of JCL for CA-7 to put in the
Trailer queue.
0088 Error on TRLQ.
008C Error loading module SASSPCEJ. Return code from SLOAD macro is in the first two char-
acters.
0090 Bad SLINK to SASSPCEJ. See also 0490 and 0890.
0094 SASSXX05 determined job should be canceled.
0098 Error in SASSXX05 - invalid return code.
009C Invalid data on # statement.
00A0 JCL attach rejected by user exit SASSXX11 with a return code of 4. Job will be flagged for
retry if the RETRY interval option is specified on the SCHEDULE statement in the initializa-
tion file. If the RETRY option is not specified, the job will be left in SKELETON status.
00A4 JCL attach rejected by user exit SASSXX11 with a return code other than 4. Job will be left
in SKELETON status.
0490 Error return from SASSPCEJ indicating invalid conversion request.
0588 Out of space in TRLQ.
0890 Error return from SASSPCEJ indicating invalid conversion request.
User Response: Determine the reason for the problem and correct it, if possible. If the job must
run this cycle, it must be DEMANDed unless the job's status is RETRY on an LQ display. The
following list shows corrective action for the messages keyed to the codes shown in the previous list.
0008 Try LLIB command for a more detailed error message and try JCL screen (DB.7 - fill in the
screen for a more detailed error message).
000C Verify that the data set in on the volume requested. Specify the correct volume if in error.
0010 Data set organization must be PS or PO. If PDS, the member name must be provided.
0014 Either BLKSIZE=0 or KEYLEN=0 or RECFM not = F or LRECL not = 80.
0018 No //U7volser DD statement exists for the volume where the data set resides. Supply a
//U7volser DD statement in the CA-7 execution JCL. The ALLOC command may be issued
to make the volume available.
001C Provide a valid member name.
0020 Try again. If problem persists, contact your installation's CA-7 specialist for assistance.
0024 This update would require a WTOR reply from the system operator's console which would
put CA-7 in a hard wait; that is, no terminal processing, job scheduling, job submittal, and so
forth, until the operator responded. Updates to such a data set are not allowed from CA-7.
The update must be made from outside of CA-7 by using TSO, batch, and so forth, so as not
to impede production scheduling.

SCNJ-18 –SCNJ-18
0028 1) This request has violated User Security as defined in the module referenced by the USER
keyword of the SECURITY statement in the CA-7 initialization file. Use a different operator
ID at logon time or change the USER ID Security module.
2) CA-7 does not have access to the JCL data set.
0054 Wait and try again. If problem persists, contact your installation's CA-7 specialist for assist-
ance.
005C Try to edit the JCL using the DB.7 screen. Error messages should be returned with codes
indicating the specific problem.
0060 Check the MVS console log for errors at the time the job came into the Request queue.
0080 Use the LJOB command to check the JCLID defined for the job then use /DISPLAY,ST=JCL
to verify the IDs defined to CA-7. Correct the job definition or add the JCL definition to the
initialization file and restart CA-7 using WARM.
0084 Try to demand the job identified by using DEMANDH so that it will be in HOLD status and
can be canceled if necessary. You may want to specify the SCHID and DOTM values if the
job needs to run. If the error repeats, the DEMAND command will produce messages to
explain the error.
0088 Take the same action as in code 0084 above.
008C Verify that module SASSPCEJ is in a library pointed to by STEPLIB. Take the same action
as in code 0084.
0090 Take same action as in code 008C above.
0094 If job is desired, use DEMAND command. You may want to check with your installation's
CA-7 specialist as to why the exit (SASSXX05) canceled the job.
0098 Take same action as in code 0094 above.
009C Use QM.5 screen to examine and correct any errors on Special Override (#) statements in the
JCL.
00A0 Probably none. If the JCL retry option is specified, JCL attach will be attempted at the next
retry interval. This will continue until the exit accepts the JCL attach or the job is canceled.
If the job must be scheduled, check with your installation's CA-7 specialist concerning the
SASSXX11 exit and why it is preventing JCL for this job to be attached.
00A4 Since the job is left in SKELETON status, it must be canceled to remove it from the Request
queue. If it must be scheduled, try using the DEMAND command. If the reason for JCL
attach rejection is not clear, you should check with your installation's CA-7 specialist con-
cerning the SASSXX11 exit.
0588 If the error occurred while attaching the JCL, issue a /DISPLAY,Q=TRL and check the space
availability. If the number of tracks is low, increase the size of the Trailer queue, at a con-
venient time, using the DMPQ/MOVQ shutdown and startup facility.

SCNJ-19 –SCNP-11
SCNJ-19 JOB xxxxxxxx NOT ENTERED IN REQUEST 'Q', *** JCL (kkkk) *** JCL RETRIEVED
FROM SPECIAL OVERRIDE LIBRARY *** DUE-OUT ON yy.ddd AT hh:mm
Explanation: See SCNJ-18. An attempt was made to retrieve the JCL for the job from the special
JCL Override library of ID 254.
User Response: Determine the reason for the problem and correct it, if possible. Replace the JCL
member in the special library. (This is required to indicate to the Job data set that next time JCL is
to be retrieved from this special library.) If job must be run this cycle, it must be DEMANDed.
SCNJ-40 SCHEDULE EXPIRED FOR JOB xxxxxxxx

Explanation: This message appears at the CA-7 Master station for each job schedule that is found
to be expired. The messages are produced each time schedule scan runs. The xxxxxxxx is the job
name.
User Response: The job schedule needs to be resolved.
SCNJ-41 TOTAL JOB SCHD EXPIRED = xxxx

Explanation: At least one SCNJ-40 message has been produced, and this reflects the number of
them that were produced for this cycle of schedule scan. Only the first five expired schedules will be
shown with the SCNJ-40 messages.
User Response: If xxxx is greater than 5, then do an LSCHD,DSNBR=SJ*,ST=EXP to determine
which schedules need to be resolved.
SCNP-11 JOB xxxxxxxx (nnnn) SYS=xxxxxxxx *** IS LATE ***

REQUIRED BY yy.ddd AT hh:mm, MUST START BY yy.ddd AT hh:mm
SCHID=xxx PROSE#=nnnnnnnn ERQD=nnn ENSAT=nnn IRQD=nnn
INSAT=nnn
MCNT=nnn FLAGS=xx/xx/xx/xx/xx/xx/xx
Explanation: This message is issued to the CA-7 Master Station to indicate that a job is behind
schedule. The fields in the message are as follows:
ERQD is a count of total external requirements.
ENSAT is a count of external requirements satisfied.
IRQD is a count of total internal requirements.
INSAT is a count of internal requirements satisfied.
MCNT is a master count of unsatisfied requirements.
FLAGS are hexadecimal values matching the following fields from the JQREC macro DSECT.
The fields are listed in order of appearance in the message.
JQFLG1
JQFLG2
JQJFLG1
JQJFLG2
JQJFLG3
JQJFLG4
JQJFLG5

SCNP-11 –SCN0-11
User Response: Determine why the job is late and take appropriate steps to correct the situation.
This message will continue to appear at every reprompt interval. To suspend the message, use the
RSVP command.
SCNP-11 xxxxxxxx STATION WORK (nnn,mmmm) REF=jjjjrrs ***IS LATE***

FOR NETWORK=xxxxxxxx [,SUBID=yyyyyyyy][,JOB=zzzzzzzz]
REQUIRED BY yy.ddd AT hh:mm:ss,
MUST START BY yy.ddd AT hh:mm:ss
PROSE #nnnnnnnn
Explanation: This message is issued to a station's terminal to indicate work is behind schedule.
User Response: Determine why the task is late and take appropriate action. This message will
continue to appear at every reprompt interval until action is taken. Use the RSVP command to
suspend the prompt.
SCNP-12 PROMPT COMPLETE AT hh:mm ON yy.ddd.

Explanation: Indicates end of a prompt or reprompt interval.
SCNP-50 RETRY CYCLE COMPLETE. xx RETRIED, yy ATTACHED.

Explanation: The RETRY cycle for JCL attach has completed. xx indicates the number of jobs
that were in the Request queue with R-RETRY status. yy indicates the number of jobs for which
RETRY was able to attach JCL. The RETRY cycle may occur on a time basis or if manually
specified with the SSCAN,SCAN=RET command.
SCNP-51 JOB xxxxxxx (nnnn) FAILED IN RETRY. CODE = zzzzzzzz

Explanation: When a retry attempt was done for job xxxxxxxx, a failure occurred other than
dynamic allocation.
User Response: The job is left in SKELETON status and needs to be canceled and, if needed,
DEMANDed back in. Refer to message SCNJ-18 to help in resolving the zzzzzzzz code.
SCN0-11 SCHEDULE SCAN STARTED AT hh:mm:ss ON yy.ddd.[(FORCED)]

***SCAN PERIOD OF yy.ddd AT hh.mm THRU yy.ddd AT hh:mm***
Explanation: This is an informational message indicating that Schedule Scan has been initiated and
is scanning for jobs and preprocess work whose schedules fall within the designated period of the
scan. All work found during the time period being scanned will be placed in the Preprocess or
Request queues as appropriate. If Schedule Scan is forced using the SSCAN,SCAN=SCH command,
the (FORCED) parameter is included in the message.

SCN0-12 –SCN0-15
SCN0-12 NEXT SCHEDULE SCAN WAKE-UP TIME IS yy.ddd AT hh:mm.

***** x...x *****
Explanation: This is an informational message notifying the user when Schedule Scan will next
begin (wake-up) to perform a time-dependent function. The function to be performed is indicated by
x...x. Current values for x...x are:
TO SCAN NEXT INTERVAL
FOR A REQ 'Q' PROMPT
FOR A POST 'Q' PROMPT
TO RE-PROMPT USER
Note: Due to dynamic activities within CA-7, Schedule Scan may be activated sooner than the
specified next wake up for a reason other than the function indicated in this message.
SCN0-13 SCHEDULE SCAN COMPLETED AT hh:mm:ss ON yy.ddd.

SCN0-14 *** ATTENTION: SCHEDULE SCAN ERROR ***

Explanation: The message indicates that errors have occurred causing Schedule Scan to end before
all jobs have been brought in.
User Response: Check error messages (possibly on the Browse data set) for error that occurred
during the Schedule Scan. When these errors are corrected, the next Schedule Scan will bring in any
jobs that were not brought in previously. Enter SSCAN,SCAN=SCH to force Schedule Scan to run
immediately rather than awaiting its next cycle.
SCN0-15 SCHEDULE SCAN NOT DONE: REASON -- DATE=0

Explanation: The message indicates that this cycle of schedule scan was not done because the scan
period start date was zero.
User Response: Use the SSCAN command to make the scan period start date a valid date.

6.5 SCO0 Through SCRJ Messages
SCO0-00 –SCO0-05
SCO0-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Explanation: Successful completion of input request.
SCO0-01 INVALID INPUT REQUEST

Explanation: Function code not DMP or ZAP.
User Response: Correct and resubmit command.

Explanation: The DMP command should specify one of the following:
SVT
MOD
ADR
JOB
DSN
DSNBR
TYPE should be DIR or MBR when dump request is JOB, DSN, or DSNBR.
User Response: Retry and specify one of the keywords noted. Check all keywords for proper
spelling or address.

Explanation: Error in OFFSET field.
User Response: Correct OFFSET value and resubmit command.

Explanation: Error in LENG field.
User Response: Correct LENG value and resubmit command.

Explanation: Module name in MOD=SASSxxxx does not begin with SASS.
User Response: Correct MOD parameter and resubmit command.

SCO0-06 –SCRJ-11

Explanation: Module name in MOD=SASSxxxx cannot be found, has not been loaded, or is not
resident.
User Response: If MOD was specified incorrectly, correct and resubmit command.

Explanation: Error on job request; job is probably not on database.
User Response: Check job name given; if incorrect, supply correct job name and resubmit
command.

Explanation: Error on DSN request; data set probably was not found.
User Response: Check data set name; if incorrect, supply correct data set name and resubmit
command.
SCO0-09 INVALID INPUT REQUEST, RC=xx

Explanation: Error attempting interface with CA-7 RPT. RC value clarifies error as follows:
01 - SUBSYS=RPT not specified on DBASE statement or RPT scheduling module
(SASSCHDR) not loaded or required input keyword missing.
02 - Invalid RPTID key requested.
03 - Invalid NAME key requested.
xx - Any other code denotes access error as documented in CA-7 RPT Systems Programmer
Guide under SRPT macro.
User Response: Verify and correct if SUBSYS, RPTID, or NAME values were incorrect. If xx
code is returned, refer to the CA-7 RPT Systems Programmer Guide for action.

Explanation: Input was received that was not recognized by the program.
User Response: Correct the input and retry.

Explanation: VSAM control block was requested and was either not found or had an error.
User Response: Check console log for CA-7.Vxxx messages and if found refer to that message for
explanation.
SCRJ-11 JOB xxxxxxxx (nnnn) FORCED COMPLETE

Explanation: This message is issued to the CA-7 Master Station to indicate when a job has been
forced complete with either the XRST screen or the top line RESTART command.

SCRJ-12 –SCRJ-29
SCRJ-12 JOB xxxxxxxx (nnnn) COMPLETED NORMALLY. ***COMPLETED***.

HIGHEST CONDITION CODE=nnnn.
Explanation: This message is issued to the CA-7 Master Station to indicate successful completion
of the specified job.
SCRJ-13 JOB xxxxxxxx (nnn) HAS JCL ERROR ***RESTART REQUIRED***

Explanation: Generally this message will not be issued for jobs that have been submitted and fail
with a JCLERR. For these jobs, the SMF0-18 message will be issued, and the possible SCRJ-13
messages will be suppressed. However, for a job that is DEMANDed with TYPE=RES, the SCRJ-13
message can be issued periodically until restart is begun. The NOPRMP command may be used to
suspend the message. The RSVP command may be used to suspend the message.
User Response: See message SMF0-18. Analyze the JCL to determine the problem and then restart
the job.
SCRJ-14 JOB xxxxxxxx(nnnn) ABNORMALLY TERMINATED ***RESTART REQUIRED***

FAILING CODE= [(S)|(U)] cccc. LAST STEP EXECUTED= yyyyyyyy.
Explanation: Refer to message SMF0-19. This message will reappear periodically until restart is
begun. The RSVP command may be used to suspend the message.
User Response: See message SMF0-19. The abend must be analyzed to determine what corrective
action is necessary. Job Restart must be used to resubmit the job. This message will reappear
periodically until restart is begun. The RSVP command may be used to suspend the message.
SCRJ-29 XPS JOB jjjjjjjj (nnnn) COMPLETED. (xxxxxxxx)

Explanation: A cross-platform job has completed. This job was scheduled with the
XPSSCHD=RUNREF option. One of the following status indicators will be provided at xxxxxxxx.
NORMAL The XPS job completed normally.
FCOMP The completion of the XPS job was forced.
CCFAIL The XPS job did not complete successfully because of a condition code exception.
JCLERR A JCL error was detected for the XPS job.
ABEND The XPS job abended.

SCRJ-30 –SCRJ-60
SCRJ-30 ARFJOB jjjjjjjj (nnnn) FOR yyyy COMPLETED. (xxxxxxxx)

Explanation: An ARF recovery job has completed. This job was scheduled by ARF to run on
behalf of an ARF monitored job for which an abnormal completion was detected. The CA-7 number
of the job that ARF monitored is yyyy. One of the following status indicators will be provided:
NORMAL The ARF recovery job completed normally.
FCOMP The completion of the ARF recovery job was forced.
CCFAIL The ARF recovery job did not complete successfully because of a condition code
exception.
JCLERR A JCL error was described for the ARF recovery job.
ABEND The ARF recovery job abended.
SCRJ-48 JOB xxxxxxxx (nnnn) COND CODE CHECK FAILED ***RESTART REQUIRED***
FAILING CODE=cccc. LAST STEP EXECUTED=yyyyyyyy.
Explanation: Refer to message SMF0-20. The specified job generated a condition code in one of
its steps, and the code failed the test defined in the CA-7 database. This message will reappear
periodically until restart is begun. The NOPRMP command may be used to suspend the message.
User Response: See message SMF0-20. The situation must be analyzed to determine the corrective
action. Job Restart must be used to resubmit the job.
SCRJ-55 JOB/DSN TABLE FULL (nnnnnnnn)

Explanation: An internal CA-7 table has filled up.
User Response: This is an informational message. Find the job(s) causing the message and mark
as MAINT=Y on the job screen. If the message occurs frequently, contact Computer Associates
SCRJ-60 JOB xxxxxxxx(nnnn) TO LOAD NEW WORK-LOAD BAL PARAMETER DEFN FAILED:
LOAD MODULE DOES NOT EXIST, OLD DEFN RETAINED
Explanation: The specified job does not have a corresponding Workload Balancing parameter defi-
nition in CA-7's Load library.
User Response: Create an appropriate load module.

6.6 SDxx Messages
SDAV-01 –SDM0-12
6.6 SDxx Messages
SDAV-01 xxx INVALID MACRO RETURN CODE = nnn...n

Explanation: The SASSSDAV module has detected an error on return from a macro. The Where-
In-Program (WIP) value is specified by xxx. The register 15 value (in hex) is given by nnn...n.
SDM0-00 SPECIFY DESIRED OPTION OR ENTER A COMMAND ON THE TOP LINE

Explanation: This is the prompt used for online selection of a major category. If an error is made
in the selection, you will again be requested to select a function.
SDM0-00 ENTER CA-7 TRANSACTION

Explanation: This is the reply to a DBM statement in batch. DBM is used in batch to exit Data-
base Maintenance mode.
User Response: Any command (Database Maintenance, inquiry, and so forth) may be entered in the
next statement.
SDM0-12 FUNCTION IGNORED FOR NON-3270 TERMINALS

Explanation: The function entered is not available in batch mode.
User Response: Reissue this function from a 3270-type terminal.

6.7 SFCx Messages
SFCW-00 –SFCY-02
6.7 SFCx Messages
This subsection contains the CA-7 messages beginning with SFC. These messages relate
to the forecast function.
SFCW-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Explanation: Input request has been successfully completed.
SFCW-01 I/O ERR DURING READ OF PROSE MEMBER FOR JOB xxxxxxxx RC=nn WIP=ww
MODULE=SFCW.
Explanation: Error occurred accessing prose for indicated job.
User Response: Use LPROS to verify that prose data exists for the job. If the prose exists, it may
need to be deleted and readded. Then retry the command that failed.
SFCW-02 I/O ERROR DURING READ OF REQUIREMENT ENTRY FOR JOB xxxxxxxx RC=nn
WIP=ww MODULE=SFCW
Explanation: Error occurred while reading requirement type records for job xxxxxxxx.
User Response: Try LJOB,LIST=RQMT for job xxxxxxxx. If error is produced from LJOB, try to
delete and add the problem requirement entry. Job may have to be deleted and then added.
SFCW-03 SCRATCH FILE READ ERROR RC=nn WIP=ww MODULE=SFCW

Explanation: Error occurred processing temporary data file in scratch queue.
SFCY-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

SFCY-02 I/O ERROR DURING READ OF SCRATCH-FILE-1, RC=nn, WIP=ww, MODULE=SFCY

Explanation: An I/O error occurred during the read operation of the Scratch file ID 1. Where:
nn is the return code from the CA-7 macro.
ww is the point in module SFCY where the I/O error occurred.

6.7 SFCx Messages
SFCY-03 –SFCY-08
SFCY-03 I/O ERROR DURING READ OF JOB DIRECTORY FOR JOB yyyyyyyy, RC=nn, WIP=ww,
MODULE=SFCY
Explanation: An I/O error occurred during the read operation of the Job data set. Where:
User Response: If problem persists, contact your installation's CA-7 specialist for assistance.
SFCY-04 I/O ERROR DURING READ OF JOB MEMBER FOR JOB yyyyyyyy, RC=nn, WIP=ww,
MODULE=SFCY
Explanation: An I/O error occurred during the read operation of the Job data set. Where:
SFCY-05 I/O ERROR DURING READ OF HEADER RECORDS FOR JOB yyyyyyyy, RC=nn,
WIP=ww, MODULE=SFCY
Explanation: An error has occurred while reading data from the CA-7 queues. Where:
SFCY-06 PROCESSING TERMINATED BY SYSTEM ERROR.

RC=nn, WIP=ww, MODULE=SM5C
Explanation: Error occurred attempting to write the WLP data as requested. Refer to message
SM50-14 for explanation of return code represented by nn. These return codes are given in decimal
representation and must be converted to hexadecimal when referring to the explanation under
message SM50-14.
User Response: Correct the indicated error and retry. Refer to message SM50-14 for corrective
action based on return code values. If the error persists, contact your installation's CA-7 specialist
for assistance.
SFCY-08 ERROR READING QUEUE REQUIREMENT SECTION FOR JOB=yyyyyyyy, RC=xx,

WIP=ww, MODULE=SFCY
Explanation: An error has occurred while reading data from the CA-7 queues. Where:

6.7 SFCx Messages
SFCY-09 –SFC0-09
SFCY-09 NOT ENOUGH SPACE AVAILABLE IN OUTPUT FILE

FILE CREATED BUT IS INCOMPLETE,
LAST JOB WRITTEN - yyyyyyyy DUE-OUT DATE yyddd/hhmm
Explanation: The data set specified by DDNAME has insufficient space available to contain all of
the WLP JOB and RES card information generated by the request.
User Response: Since the data produced is not in a predictable order, no assumptions can be made
about the contents of the file. Reallocate the file with a larger space allocation and retry the
command.
SFC0-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

SFC0-02 'xxxxxx' IS AN INVALID FUNCTION

Explanation: xxxxxx is an invalid function specified on the input command.
SFC0-03 LOAD ERROR FOR 'xxxxxxxx', RC=nn

Explanation: xxxxxxxx is the module to be loaded; nn is the return code from the SLOAD macro.
User Response: Verify the following:
1. Module xxxxxxxx exists in the CA-7 Load library; and
2. That there is an APPLCTN statement for xxxxxxxx in SASSPROG or in the initialization file.
SFC0-04 INVALID INPUT.

Explanation: Input data has unrecognizable keyword(s) and/or format(s) for one or more parame-
ters. This can result when a value is too big or too many entries are input.
User Response: Resubmit the command with correct parameter(s) and data.
SFC0-08 GENERIC JOBNAME NOT ALLOWED WITH FRJOB OR FRQJOB.

Explanation: Reverse job flow does not support generic jobname(s).
User Response: Respecify the command with one or more specific jobnames.
SFC0-09 MAX LEVEL HIT, SOME JOBS NOT LISTED

Explanation: While processing a forecast command, CA-7 found that the maximum level had been
reached and has terminated the command.
User Response: Check the output of the command to see if there may be a triggering loop defined
in the database. By default the maximum number of levels is 99. This may be changed by using the
LVL keyword on the command, or the FCMAXLEV keyword on the OPTIONS statement in the

6.7 SFCx Messages
SFC0-10 –SFC0-21
SFC0-10 INVALID OR OMITTED 'xxxxxxxx' DATA

Explanation: xxxxxxxx is the parameter that is invalid or has been omitted.
User Response: Resubmit the command with correct parameter and data.
SFC0-11 'xxxxxxxx' DATA NOT REQUIRED. ERROR.

Explanation: xxxxxxxx is the parameter that has been provided but is not required.
SFC0-12 REQUIRED INPUT 'xxxxxxxx' MISSING.ERROR

Explanation: xxxxxxxx is the parameter that is required but not provided.
SFC0-13 CONFLICTING PARAMETERS

Explanation: Mutually exclusive parameters have been specified on the input command (for
example, TO and SPAN).
User Response: Correct the invalid parameters and resubmit the command.
SFC0-19 STORAGE SHORTAGE, TRY COMMAND LATER

Explanation: The specified forecast needed more CA-7 storage to complete its process, but there
was not enough available.
User Response: Verify that the command was properly entered, especially that the time interval is
correct.
May need to increase the CA-7 region size.
If problem persists, contact your installation's CA-7 specialist for assistance.
SCF0-20 SCHEDULE ID REQUIRED FOR JOB xxxxxxxx (WITH NO SCHEDULE)

Explanation: Forecast was requested for a job with no schedule defined. To produce a forecast, a
schedule ID is required.
User Response: Retry the command with an appropriate SCHID value.
SFC0-21 I/O ERROR DURING READ OF JOB DIRECTORY FOR JOB xxxxxxxx, RC=nn, WIP=ww,
MODULE=GFCJ
Explanation: Job xxxxxxxx could not be read from the database. Where:
nn is the return code.
ww is the point in module GFCJ where the I/O error occurred.
User Response: Try LJOB,JOB= command to verify that the job is in the database; or run the
Database Verification Utility. Correct any errors reported by the command or the utility. Then
reissue the forecast command that failed.

6.7 SFCx Messages
SFC0-22 –SFC0-26
SFC0-22 I/O ERROR DURING SEQUENTIAL READ OF JOB DIRECTORY FOR THE FIRST
RECORD, RC=nn, WIP=A2, MODULE=GFCJ
Explanation: Some error has occurred while accessing the Job data set directory entries. Where:
A2 is the point in module GFCJ where the I/O error occurred.
User Response: Try LJOB command to verify that the job is in the database; or run the Database
Verification Utility. Correct any errors reported by the command or the utility. Then reissue the
forecast command that failed.
SFC0-23 I/O ERROR DURING SEQUENTIAL READ OF JOB DIRECTORY FOR THE LAST
RECORD WAS FOR JOB xxxxxxxx, RC=nn, WIP=A3, MODULE=GFCJ
Explanation: Some error has occurred while accessing the Job data set directory entries. Where:
A3 is the point in module GFCJ where the I/O error occurred.
User Response: Try LJOB,JOB= command to verify that the job is in the database; or run the
Database Verification Utility. Correct any errors reported by the command or the utility. Then
reissue the forecast command that failed.
SFC0-24 I/O ERROR DURING READ OF JOB MEMBER FOR JOB xxxxxxxx, RC=nn, WIP=A4,
MODULE=yyyy.
Explanation: The indicated job could not be read from the database. The module suffix is indi-
cated by yyyy.
User Response: If nn=00, the job will probably have to be deleted and readded to the CA-7 data-
base.
Run UCC7DBVR and look for 011 messages indicating no job entry record for a job member. If
found, delete and re-add those jobs.
SFC0-25 I/O ERROR DURING READ OF JOB SCHEDULE DIRECTORY FOR SJnnnnnn FOR JOB
xxxxxxxx, RC=nn, WIP=B1, MODULE=GFCJ
Explanation: The indicated schedule could not be read from the database. Where:
B1 is the point in module GFCJ where the I/O error occurred.
User Response: Delete the schedule and add it again. Then reissue the command.
SFC0-26 I/O ERROR DURING READ OF JOB SCHEDULE MEMBER FOR SJnnnnnn FOR JOB
xxxxxxxx, RC=nn, WIP=ww, MODULE=GFCJ
Explanation: The indicated schedule could not be read from the database. Where:

6.7 SFCx Messages
SFC0-27 –SFC0-29
User Response: Delete the schedule and add it again. Then reissue the command.
SFC0-27 I/O ERROR DURING READ OF CA-7 INDEX DATASET FOR TRGD.xxxxxxxx, RC=nn,
WIP=C1, MODULE=GFCJ
Explanation: An error occurred processing the IDS key starting with the characters TRGD. Where:
C1 is the point in module GFCJ where the I/O error occurred.
User Response: Issue the TRIG command to cleanup possible IDS entry errors. Then reissue the
forecast command which failed. If the problem persists, contact your installation's CA-7 specialist.
SFC0-28 I/O ERROR DURING READ OF CA-7 INDEX DATASET FOR INPUT NETWORK
xxxxxxxx, RC=nn, WIP=G0, MODULE=GFCN
Explanation: An error occurred accessing the IDS entry for NW.xxxxxxxx. Where:
xxxxxxxx is the network name.
G0 is the point in module GFCN where the I/O error occurred.
1. Verify the network requested is a valid network. Two methods of verification are available:
a. Enter the LNTWK command, or
b. Run the Database Verification Utility.
2. Correct any errors reported.
3. Reissue the forecast command which failed.
If the problem persists, contact your installation's CA-7 specialist.
SFC0-29 I/O ERROR DURING SEQUENTIAL READ OF CA-7 INDEX DATASET FOR THE FIRST
NODE NW., RC=nn, WIP=G1, MODULE=GFCN
Explanation: An error occurred trying to access the first NW. entry in the IDS. Where:
1. Verify that there are network entries in the database
or run the Database Verification Utility.

6.7 SFCx Messages
SFC0-30 –SFC0-32
SFC0-30 I/O ERROR DURING SEQUENTIAL READ OF CA-7 INDEX DATASET LAST ENTRY
READ WAS NW.xxxxxxxx, RC=nn, WIP=G2, MODULE=GFCN
Explanation: The error occurred while accessing the IDS. Where:
1. Run the Database Verification Utility.
SFC0-31 I/O ERROR DURING READ OF INPUT NETWORK DIRECTORY FOR NETWORK
xxxxxxxx (NWnnnnnn), RC=nn, WIP=H1, MODULE=GFCN
Explanation: The network specified probably has an entry in the IDS, but there is no corresponding
entry in the Dataset data set.
User Response: Try to delete the network to clear the IDS or contact your installation's CA-7 spe-
cialist.
SFC0-32 I/O ERROR DURING READ OF INPUT NETWORK MEMBER FOR NETWORK xxxxxxxx,
RC=nn, WIP=H2, MODULE=GFCN
Explanation: Error occurred while accessing member data for the network indicated. Where:
H2 is the point in module GFCN where the I/O error occurred.
1. Verify the network exists.
2. Delete and add the network if necessary.
3. Retry the command.
If problem persists, contact your installation's CA-7 specialist.

6.7 SFCx Messages
SFC0-33 –SFC0-35
SFC0-33 I/O ERROR DURING READ OF INPUT NETWORK SCHEDULE DIRECTORY FOR
SInnnnnn FOR NETWORK xxxxxxxx, RC=nn, WIP=H7, MODULE=GFCN
Explanation: Error occurred while accessing schedule data for the network indicated. Where:
nnnnnn is the input network schedule data set number.
1. Verify the schedule exists.
2. Delete and add the schedule if necessary.
SFC0-34 I/O ERROR DURING READ OF INPUT NETWORK SCHEDULE MEMBER FOR SInnnnnn
FOR NETWORK xxxxxxxx, RC=nn, WIP=ww, MODULE=GFCN
Explanation: Error occurred while accessing schedule data for the network indicated. Where:
nnnnnn is the input network schedule data set number.
ww is the point in module GFCN where the I/O error occurred.
1. Verify the schedule exists.
2. Delete and add the schedule if necessary.
SFC0-35 I/O ERROR DURING READ OF OUTPUT NETWORK DIRECTORY FOR NETWORK
xxxxxxxx CONNECTED TO JOB yyyyyyyy RC=nn, WIP=H1, MODULE=GFCN
Explanation: Job yyyyyyyy has network xxxxxxxx connected, but the network is not in the Dataset
data set or has caused an error. Where:
yyyyyyyy is the job name.
User Response: Verify the connection using the DB.3 (JOBCONN) screen to delete or add the
network. Then retry the command.

6.7 SFCx Messages
SFC0-36 –SFC0-38
SFC0-36 I/O ERROR DURING READ OF OUTPUT NETWORK MEMBER FOR NETWORK
xxxxxxxx CONNECTED TO JOB yyyyyyyy RC=nn, WIP=H2, MODULE=GFCN
Explanation: The network had an error with member data. Where:
User Response: The following actions are recommended:
1. Delete and add the network.
Note: The JOBCONN entries may need to be deleted and added as well.
SFC0-37 I/O ERROR DURING READ OF OUTPUT NETWORK SCHEDULE DIRECTORY FOR
SOnnnnnn FOR NETWORK xxxxxxxx CONNECTED TO JOB yyyyyyyy RC=nn, WIP=H3,
MODULE=GFCN
Explanation: Schedule probably does not exist for network indicated. Where:
nnnnnn is the output network schedule data set number.
User Response: The following steps are recommended:
1. Verify that the schedule exists for the network named.
2. If the schedule is missing, add the schedule.
SFC0-38 I/O ERROR DURING READ OF OUTPUT NETWORK SCHEDULE MEMBER FOR
SOnnnnnn FOR NETWORK xxxxxxxx CONNECTED TO JOB yyyyyyyy RC=nn, WIP=ww,
MODULE=GFCN
Explanation: Schedule member contained an error. Where:
nnnnnn is the output network schedule data set number.
ww is the point in module GFCN where the I/O error occurred.
User Response: Delete and add schedule for network named.

6.7 SFCx Messages
SFC0-39 –SFC0-42
SFC0-39 NOT FOUND CONDITION OCCURRED DURING READ OF CA-7 INDEX DATASET FOR
INPUT NETWORK xxxxxxxx, RC=01, WIP=G0, MODULE=GFCN
Explanation: The requested network was not found.
User Response: Add the network and then retry the command.
SFC0-41 I/O ERROR DURING READ OF xxxxx FOR HEADER RECORDS FOR JOB# nnnnnnnn,
RC=nn, WIP=A2, MODULE=SFCQ
Explanation: Error occurred reading from queue for job nnnnnnnn. Where:
xxxxx is the queue name.
nnnnnnnn is the job number.
A2 is the point in module SFCQ where the I/O error occurred.
1. Verify job is in queue xxxxx using LQ/LPRE/LPOST command.
2. Retry original command.
3. If problem persists, contact your installation's CA-7 specialist.
SFC0-42 I/O ERROR DURING SEQUENTIAL READ OF xxxxx FOR HEADER RECORDS FOR THE
FIRST RECORD, RC=nn, WIP=A3, MODULE=SFCQ
Explanation: Error occurred accessing queue xxxxx. Where:
User Response: The following action is recommended:
1. Retry the command before going to the next step.
2. If xxxxx is REQQ, RDYQ, or ACTQ, try the LQ command to check the error condition.
3. If xxxxx is PREQ, try the LPRE command.
4. If xxxxx is POSTQ, try LPOST command.
5. If no error is reported by the previous steps, retry the forecast command.
6. If error is detected, it may be necessary to perform a DMPQ/MOVQ operation or format the
queues.
7. If error persists, contact your installation's CA-7 specialist.

6.7 SFCx Messages
SFC0-43 –SFC0-44
SFC0-43 I/O ERROR DURING SEQUENTIAL READ OF xxxxx FOR HEADER RECORDS LAST
RECORD READ WAS FOR JOB yyyyyyyy, RC=nn, WIP=A4, MODULE=SFCQ
Explanation: Error occurred while accessing queue. Where:
User Response: The following action is recommended:
1. Retry the command before going to the next step.
2. If xxxxx is REQQ, RDYQ, or ACTQ, try the LQ command to check the error condition.
3. If xxxxx is PREQ, try the LPRE command.
4. If xxxxx is POSTQ, try LPOST command.
5. If no error is reported by the previous steps, retry the forecast command.
6. If error is detected, it may be necessary to perform a DMPQ/MOVQ operation or format the
queues.
7. If error persists, contact your installation's CA-7 specialist.
SFC0-44 I/O ERROR DURING SEQUENTIAL READ OF xxxxx FOR TRAILER RECORDS FOR JOB
yyyyyyyy, RC=nn, WIP=ww, MODULE=SFCQ
Explanation: Error occurred while reading requirement type records for the indicated job. Where:
xxxxx is the status queue name.
ww is the point in module SFCQ where the I/O error occurred.
The error condition could be temporary due to the job just entering the queues. An entry error could
have also occurred.
User Response: Use LQ command for indicated job to evaluate status. If status is SKELETON or
RQMT INC, the job may need to be canceled from the queue if the status does not clear up. If
status is not SKELETON or RQMT INC, reissue the forecast command. If problem persists, contact
your installation's specialist.

6.7 SFCx Messages
SFC0-51 –SFC0-61
SFC0-51 I/O ERROR DURING READ/WRITE OF SCRATCH-FILE-1, RC=nn, WIP=ww,

MODULE=xxxx
Explanation: Error occurred during the read or write operation of the Scratch file ID 1. Where:
ww is the point in module xxxx where the I/O error occurred.
xxxx is the module name.
SFC0-52 NOT ENOUGH SPACE ON SCRATCH-FILE-1, RC=nn, WIP=ww, MODULE=xxxx

Explanation: All Scratch file space for Scratch file ID 1 has been used while selecting job or
station data for the time interval and selection criteria given. Where:
xxxx is the name of the module executing at the time.
User Response: Two options are available:
1. Change the time interval or vary the selection criteria to reduce the number of jobs or stations
selected.
2. Increase the Scratch file space using the DAIO statement SCRTRK keyword in the CA-7 initial-
ization file. CA-7 must be reinitialized.

MODULE=xxxx

6.7 SFCx Messages
SFC0-62 –SFC0-72
SFC0-62 NOT ENOUGH SPACE ON SCRATCH-FILE-2, RC=nn, WIP=ww, MODULE=xxxx

selected.
2. Increase the Scratch file space using the SCRTRK keyword in the CA-7 initialization file.

MODULE=xxxx
SFC0-72 NOT ENOUGH SPACE ON SCRATCH-FILE-8, RC=nn, WIP=ww MODULE=xxxx

ww is the point where the CA-7 macro was issued.
selected.
ization file.

6.7 SFCx Messages
SFC0-81 –SFC0-91

MODULE=GFCJ
SFC0-82 NOT ENOUGH SPACE ON SCRATCH-FILE-7, RC=nn, WIP=ww, MODULE=GFCJ

selected.
ization file.
SFC0-86 NOT ENOUGH SPACE ON SCRATCH-FILE-6, RC=nn, WIP=ww, MODULE=GFCJ

selected.
ization file.
SFC0-91 ERROR DURING SORT OPERATION, RC=nn, WIP=ww, MODULE=xxxx

Explanation: ww is the point in the module (WIP) xxxx where the sort operation was being per-
formed on the Scratch file. nn is the return code from the SORT module. This is a CA-7 system
problem.

6.7 SFCx Messages
SFC0-96 –SFC1-00
SFC0-96 SCHEDULE SCAN IS ACTIVE. TRY LATER.

Explanation: To prevent degradation on scheduling activity, queue related forecasts, such as
FQJOB, are not allowed while Schedule Scan is processing.
User Response: Wait a few minutes. Then try the forecast again. If the problem persists, contact
SFC0-97 NOT ENOUGH SCRATCH SPACE AVAILABLE. PROCESSING TERMINATED

Explanation: No more tracks are available to allocate to the Scratch file, even though the number
of allocated tracks has not reached the maximum specified. This condition may have arisen because
of other activities in CA-7.
User Response: Try to run the command when there is less activity in CA-7. Alternately, shut
down CA-7 with a DMPQ, increase the space in the scratch queue, and reinitialize CA-7 with a
MOVQ startup.
SFC0-98 NOT ENOUGH SCRATCH SPACE SPECIFIED. PROCESSING TERMINATED

Explanation: All specified Scratch file space has been used and no more space is available for the
Scratch file operation.
selected.
2. Increase the Scratch file space using the SWFTRK keyword in the CA-7 initialization file DAIO
statement.
SFC0-99 SYSTEM ERROR, RC=nn, WIP=ww, MODULE=xxxx

Explanation: If nn=00 and xx=AA, and the command is FJOB,JOB=*, no SJ members were found.
Where:
ww is the point in the module where the I/O error occurred.
User Response: Contact your installation's CA-7 specialist. There must be at least one SJ member.
SFC1-00 REQUEST COMPLETED AT hh:mm:ss ON yy-ddd

Explanation: Request complete.

6.8 SFEx Messages
SFEO-14 –SFER-01
6.8 SFEx Messages
SFEO-14 NETWORK (nnnn) ENTERED INTO POST-PROCESS 'Q' FOR nn STATION

Explanation: This message is issued to the CA-7 Master Station to identify work added to the
postprocess queue as a result of a job being scheduled into the preprocess queue.
SFEP-11 xxxxxxxx STATION WORK (nnn,mmm) REF# jjjrrs

FOR NETWORK=xxxxxxxx, [SUB-ID=yyyyyyyy] , [JOB=zzzzzzzz],
DESC=dddddddd
REQUIRED BY yy.ddd AT hh:mm:ss, MUST START BY yy.ddd
AT hh:mm:ss
PROSE#=nnnnnnnn SYSTEM=ssssssss
****PROSE****
Explanation: This message is sent to the CA-7 terminal associated with the specified station to
notify personnel at that station that work has been scheduled. If no terminal is defined for the
station, the message is sent to the CA-7 Master Station. The only prose that appears is that desig-
nated with #QDESC for station xxxxxxxx.
SFEP-12 xxxxxxxx STATION WORK (nnn,mmm) END.

Explanation: This signifies the end of the preceding SFEP-11 message.
SFEP-13 ERROR ENCOUNTERED WIP=xx

Explanation: An error has occurred in the program. The WIP value indicates the location in the
program where the error occurred.
SFER-01 xx INVALID SGET RETURN CODE=nn

Explanation: An error has occurred in the processing of a CA-7 data set.
User Response: If xx=JJ, KK, LL or CC, the CA-7 Trailer queue might be full. Do a
/DISPLAY,Q=TRL to display status of the queue. If xx=EE, a data set member on the database
could not be read and the job must be reloaded. If xx=AA, there may be hex data in the job's JCL.

6.8 SFEx Messages
SFER-07 –SFER-15
SFER-07 LOAD ERROR FOR xxxxxxxx WITH RETURN CODE=nn

from the SLOAD macro is indicated by nn (nn=04 indicates module not found; nn=12 indicates an
I/O error occurred).
User Response: Verify that the module indicated has not been inadvertently deleted from the
CA-7.LOADLIB and that the APPLCTN statement is present (and correct) in the CA-7 initialization
for assistance.
SFER-08 JOB xxxxxxxx HAS MORE THAN 255 REQUIREMENTS

Explanation: A job has been brought into the REQ queue. The specified job has more than 255
requirements defined. Having more than 255 requirements defined for a job can lead to errors when
the job enters the Request queue because the master requirement count can only be a maximum of
256 before it resets.
User Response: None. The message is informational only.
SFER-14 JOB#nnnn NETWORK (xxxxxxxx) NOT ADDED TO POST 'Q'.CODE=nn

Explanation: The specified network was not added to the Postprocess queue.
User Response: The output network must have a schedule and the SCHID must be the same as the
job. If the problem persists, contact your installation's CA-7 specialist for assistance.
SFER-15 ERROR OCCURRED, DEBUG DATA=xxxxxxxx

Explanation: An invalid requirement entry for a job was encountered. The display (xxxxxxxx) is
in hexadecimal.

6.9 SIRx Messages
SIRA-01 –SIRD-11
6.9 SIRx Messages
SIRA-01 xx INVALID SGET RETURN CODE = nn

Explanation: An error was detected by SASSSIRA while issuing a CA-7 macro during job require-
ment checking. The macro statement where the error occurred is indicated by xx and the return code
is indicated by nn.
SIRD-01 xx INVALID SGET RETURN CODE=nn

Explanation: An error was detected by SASSSIRD while issuing a CA-7 application macro. The
macro statement where the error occurred is indicated by xx; nn is the return code from the call.
SIRD-11 **** JOB=xxxxxxxx (nnnn) EXECUTION REQUIREMENTS **** JCLID=nnn

SYSTEM=ssssssss DESC=d...d
DUE-OUT yy.ddd/hhmm DEAD-LINE yy.ddd/hhmm
SUBMIT yy.ddd/hhmm MAINID=xxx
SCHID=nnn PROSE#=pppppppp ERQD=nnn ENSAT=nnn IRQD=nnn
INSAT=nnn MCNT=nnn FLAGS=xx/xx/xx/xx/xx/xx/xx
*** REQUIREMENTS ***
*** JOB PROSE ***
Explanation: This message is issued to the CA-7 Master Station or to an alternate station (LTERM)
defined in the database entry for the job xxxxxxxx. The message is produced for each job when it
enters the Request queue due to calendar, trigger, or DEMAND scheduling. Input requirements and
their status will be described immediately following the REQUIREMENTS heading. Job prose, if
defined, is listed immediately following the JOB PROSE heading.
The status fields in the message are as follow:
DUE-OUT The date/time specified as when the job must complete execution.
DEAD-LINE The date/time calculated as when the job must begin execution to finish by
DUE-OUT time. The value is determined by subtracting the average runtime for the
job from DUE-OUT.
SUBMIT The date/time specified as a must-submit value in the schedule definition.
MAINID The system identifier. If present, MAINID indicates where the job should (or
should not) be submitted.
ERQD A count of total external requirements.
ENSAT A count of external requirements not satisfied.
IRQD A count of total internal requirements.
INSAT A count of internal requirements not satisfied.

6.9 SIRx Messages
SIRD-12 –SIR0-12
MCNT A master count of unsatisfied requirements for the job.

FLAGS Hexadecimal values matching the following fields from the JQREC macro DSECT.
The fields are listed in order of appearance in the message.
JQFLG1
JQFLG2
JQJFLG1
JQJFLG2
JQJFLG3
JQJFLG4
JQJFLG5
SIRD-12 END OF REQUIREMENTS FOR JOB=xxxxxxxx(nnnn).

Explanation: This message terminates the initial requirements display which followed the SIRD-11
message for the specified job.
SIR0-01 xx INVALID SGET RETURN CODE=nn

Explanation: An error was detected by SASSSIR0 while issuing a CA-7 macro. The macro state-
ment where the error occurred is indicated by xx; nn is the return code from the call.
SIR0-07 LOAD ERROR FOR xxxxxxxx WITH RETURN CODE=nn

from the SLOAD macro is indicated by nn (nn=04 indicates module not found; nn=13 indicates an
I/O error occurred).
User Response: Verify that module xxxxxxxx has not been inadvertently deleted from the
CA-7.LOADLIB and that the APPLCTN statement is present (and correct) in the CA-7 initialization
for assistance.
SIR0-11 INITIAL REQUIREMENTS SCAN STARTED AT hh:mm:ss ON yy.ddd.

Explanation: This message is issued to the CA-7 Master Station to indicate that initial requirements
scanning has started for jobs placed in the Request queue during the Schedule Scan interval. Input
requirements for all newly added jobs will be scanned and those already satisfied will be posted.
SIR0-12 INITIAL REQUIREMENTS SCAN COMPLETED AT hh:mm:ss ON yy.ddd.

Explanation: This message is issued to the CA-7 Master Station to indicate the completion of the
initial requirements scan activity.

6.9 SIRx Messages
SIR0-13 –SIR0-14
SIR0-13 REQUIREMENT LIST SUPPRESSED FOR JOB=xxxxxxxx(nnnn)

Explanation: User has indicated that the requirement list for the specified job is to be suppressed.
This may be set by job using the JOB screen. It may be globally set by using SSCAN,SCAN=ABR.
SIR0-14 jjjjjjjj(nnnn) detail-text

Explanation: An error occurred while trying to initiate ARF monitoring. jjjjjjjj is the name of the
job that had the error. nnnn is the CA-7 job number of the job. Descriptions of detail texts follow.
User Response: Refer to reason and action for detail message.
UNABLE TO LOCATE ARF TRAILER.
Detail Reason: The ARF segment on the TRAILER queue could not be found.
Detail Action: Cancel the job and resubmit. If the problem persists, contact Computer Associates
Technical Support.
ARF ENVIRONMENT ERROR.
Detail Reason: One or more ARF control areas could not be located.
Detail Action: Ensure that ARF=YES is coded on the RESTART statement for ARF monitoring.
Cancel the job and resubmit. If the problem persists, contact Computer Associates
Technical Support.
SQ ERROR AT nnnn ERR=xxxx
Detail Reason: An error occurred trying to issue a CA-7 queue access macro. nnnn is the
SASSARFA module offset and xxxx is the macro return code.
Technical Support.
#ARJI ERROR FOR ssssssss ERR=aaaa bbbb cccc
Detail Reason: An error occurred trying to issue a CA-7 ARF macro. ssssssss is the name of the
ARFSET. aaaa is the return code. bbbb is the reason code and cccc is an infor-
mation code.
Technical Support.
NO ARF TESTS FOR ssssssss
Detail Reason: An ARFSET was specified for ARF monitoring, but no tests were applicable for
this run.
Detail Action: None
ARF ATTACH COMPLETE - ssssssss

Explanation: ARF monitoring has begun for the job named. The ARFSET that will be used for
ARF monitoring is ssssssss.

6.10 SJC0 Messages
SJC0-00 –SJC0-15
6.10 SJC0 Messages
This subsection contains the CA-7 SJC0 messages. These messages relate to job sub-
mission.
SJC0-00 SUBMIT PROGRAM STARTED

Explanation: The job submission function of CA-7 has started.
SJC0-00 JCL SUBMIT COMPLETE nn JOBS SUBMITTED AT hh:mm:ss ON yy.ddd

Explanation: All jobs in the Ready queue that were to be submitted have been written to the
submit data set or internal reader. nn identifies the number of jobs submitted during this job sub-
mission cycle.
SJC0-11 ERROR - MOVE FROM REQUEST TO READY QUEUE

Explanation: An error occurred while attempting to move header records from the Request queue
to the Ready queue. The Ready queue may be full.
User Response: If the Ready queue is full, the job will be moved later. If not, contact your instal-
SJC0-13 ERROR - READ OF REQUEST QUEUE

Explanation: An error occurred while scanning the Request queue for jobs to move to the Ready
queue.
SJC0-14 ERROR - UPDATE OF REQUEST QUEUE

Explanation: A nonexecutable job was marked as processed, and an error occurred while
attempting to replace the entry in the Request queue.
SJC0-15 REQUEST QUEUE STOPPED

Explanation: The Request queue was stopped by the STOP,Q=REQ command. No jobs will be
moved from the Request queue to the Ready queue.
User Response: If job submission is desired, restart the Request queue using START,Q=REQ.

6.10 SJC0 Messages
SJC0-16 –SJC0-35
SJC0-16 READY QUEUE STOPPED - NO SUBMIT

Explanation: An attempt was made to submit jobs, but the Ready queue has been stopped by the
STOP,Q=RDY command.
User Response: If job submission is desired, restart the Ready queue using START,Q=RDY.
SJC0-21 ERROR - ON READ OF READY QUEUE

Explanation: An error occurred on the first GET reading the Ready queue for jobs to submit. A
problem exists in the Ready queue.
SJC0-22 ERROR - READY QUEUE GET NEXT

Explanation: An error occurred on a GETNEXT reading the Ready queue for jobs to submit. A
problem exists in the Ready queue.
SJC0-33 INVALID JOB CARD COLS 70-71 MUST BE BLANK

Explanation: Data was found in columns 70 and/or 71 of the JOB statement. These columns are
used by CA-7. The columns must be blank. When using CA-7 NCF or external security, column 69
may also need to be blank. Refer to Chapter 3 of the CA-7 Systems Programmer Guide.
User Response: Use the text editor to correct the JOB statement.
SJC0-34 INVALID JOB CARD

Explanation: This error may be caused by one of the following situations:
1. The JOB statement format in the execution JCL is actually invalid.
2. Check the DBASE statement for LDJOBNM. If the LDJOBNM parameter is used, the word
JOB does not begin in column 12 or later.
User Response: Use the text editor to correct the JCL in the queue. It may also be desirable to
change the execution JCL permanently.
SJC0-35 FIRST RECORD OF JCLMBR NOT A JOB CARD

Explanation: The first record in the JCL member containing the job's execution JCL is not a valid
JOB statement.
User Response: Use the text editor to correct the JCL in the queue. The execution JCL member
should also be permanently updated.

6.11 SJLx Messages
SJL0-00 –SJL0-01
6.11 SJLx Messages
This subsection contains the CA-7 messages beginning with SJL. These messages relate
to job load processing.
SJL0-00 JOB xxxxxxxx (nnnn) LOAD SUCCESSFUL ***JOB LOADED***

***LOAD ONLY, PURGED FROM REQUEST "Q".***
Explanation: The job has been successfully loaded.
SJL0-00 JOB xxxxxxxx (nnnn) RELOAD SUCCESSFUL ***JOB RELOADED***

Explanation: The job has been successfully reloaded.
SJL0-01 JOB xxxxxxxx (nnnn) WIP=xx INVALID MACRO RETURN CODE=xxxxxxxx.

*** LOAD UNSUCCESSFUL, JOB LOCKED. *** ***LOAD FAILED***
Explanation: An unexpected error has been detected by the LOAD program.
User Response: Run a SASSBK00 backup. Examine for error conditions. If errors are encount-
ered, contact your installation's CA-7 specialist for assistance.
SJL0-01 JOB xxxxxxxx (nnnn) WIP=xx INVALID MACRO RETURN CODE=xxxxxxxx.

DSN=x...........x
*** LOAD UNSUCCESSFUL, JOB LOCKED. *** ***LOAD FAILED***
Explanation: An unexpected error relating to the data set indicated has been detected by the LOAD
program.
User Response: If WIP=CY, member exists on IDS but not on the Dataset data set. Check for
conflicts related to the data set and correct, or contact your installation's CA-7 specialist for assist-
ance. If the data set name is not a valid OS data set name, reload the job, commenting out the DD
for the data set.
If WIP=CU and return code is 0, the SCRTRK value on the DAIO statement in the initialization file
may be too small.

6.11 SJLx Messages
SJL0-03 –SJL0-13
SJL0-03 OUT OF SPACE ON DATA BASE

*** LOAD UNSUCCESSFUL, JOB LOCKED. *** *** LOAD FAILED ***
Explanation: Insufficient space encountered while attempting to add a database entry during LOAD
processing for a job. If a DSN is listed, the job loaded but indicated data sets were not added to the
database. If no DSN is listed, the job itself was not added.
User Response: Check system log for WTO identifying the database file having an out-of-space
condition. After shutting down CA-7:
1. Backup the database.
2. Reallocate the affected file.
4. Reload all jobs for which this message appeared.
SJL0-11 DSN= x.....x RENAMED x.....x TO AVOID INDEX DS CONFLICT

Explanation: The DSNAME is already cataloged for a prose or network entry. For SVS users with
a VSAM master catalog, this message could result from the DSNAME having been cataloged in the
VSAM master.
User Response: If the data set is permanent, no action is necessary other than to mark it as PERM
on the DSN screen. All database references will be through the renamed value. The data set has
assumed a new name only in the CA-7 database. Your JCL remains unchanged. For nonpermanent
data sets, it may be necessary to restructure your entries to avoid this conflict.
SJL0-12 UNABLE TO ADD TO INDEX DS DSN=x.....x

(OUT OF SPACE ON DATA BASE)
Explanation: An error resulted from the attempt to enter the above DSN in the CA-7 IDS. There
may be no space in the Dataset data set or in the Index data set for adding the specified DSN. If an
out-of-space problem occurs, a WTO is issued.
User Response: Resolve the error and reload the job in question. If an out-of-space condition
exists, steps should be taken to increase the size of the data set.
SJL0-13 HAS INVALID OR NO LOAD DATA.

Explanation: An unexpected error has caused invalid or missing data for the job. The job may
have been canceled while CA-7 LOAD processing was occurring.
User Response: Rerun the load and if the problem recurs, contact your installation's CA-7 specialist
for assistance. If running two copies of CA-7, be sure a test version of the load procedure
CA07LOAD is changed to execute from the test CA-7 LOADLIB and the test copy of CA-7 speci-
fies the test load procedure in the initialization file.

6.11 SJLx Messages
SJL1-01 –SJL1-01
SJL1-01 JOB xxxxxxxx (nnnn) WIP=zz INVALID MACRO

RETURN CODE = yyyyyyyy
*** LOAD UNSUCCESSFUL, JOB LOCKED. ****** LOAD FAILED ***
Explanation: An attempted load failed. If zz=38 and yyyyyyyy=00000005, then the error was
encountered trying to load job information to the Job data set.
User Response: If the error persists, try doing a backup and reload. Check the CI and CA sizes of
the Job data set. The Job data set may require a larger allocation.

6.12 SJRx Messages
SJR0-12 –SJR0-20
6.12 SJRx Messages
SJR0-12 JOB NOT FOUND ON REQUEST QUEUE

Explanation: The job specified on the input command could not be found in the Request queue.
User Response: Verify the job name or CA-7 job number; correct and resubmit the command.
SJR0-14 *NOTE* - JOB RESTART NOT REQUIRED

Explanation: The job specified on the input command does not require a restart.
User Response: Verify the job name or CA-7 job number; correct and resubmit the command.
SJR0-15 xxxxxxxx RESULTED IN I/O ERROR...n

Explanation: The CA-7 macro being used when the I/O error occurred is indicated by xxxxxxxx as
follows:
SGET-DIR - Read the Job data set directory.
SGET-JOB - Read a job entry on the Job data set.
SGET-STEP - Read a step entry on the Job data set.
The I/O error return code is indicated by n.
SJR0-16 INVALID FUNCTION SPECIFIED

Explanation: The function specified on the input request was not LIST or RESTART.
SJR0-17 JOB= WAS NOT SPECIFIED OR INVALID

Explanation: The JOB parameter was either omitted from the input request or contained an invalid
CA-7 job number.
SJR0-19 FORCECOMP= IS NOT VALID

Explanation: The value given for the FORCECOMP parameter was not YES or NO.
SJR0-20 EXPRESS= IS INVALID

Explanation: The value given for the EXPRESS parameter was not YES.

6.12 SJRx Messages
SJR0-21 –SJR0-28
SJR0-21 SUP11STP= IS INVALID

Explanation: The value given for the SUP11STP parameter was not YES or NO.
SJR0-22 AN INVALID KEYWORD WAS ENTERED

Explanation: A keyword specified in the input command was invalid for the requested function.
SJR0-23 PROCESS - IS INVALID

Explanation: The CA-11 processing code, given by the PROCESS keyword, is invalid. Allowable
values are R, F or N.
SJR0-24 STPSTRT= MUST BE USED WITH PROCSTRT

Explanation: Whenever the PROCSTRT keyword is used to indicate a starting point within a spe-
cific PROC, then STPSTRT must also be used to supply the starting step within that PROC. This is
true even if the starting step is the first in the PROC.
SJR0-25 STPEND= MUST BE USED WITH PROCEND=

Explanation: Whenever the PROCEND keyword is used to indicate that processing is to end with a
specific PROC, then STPEND must also be specified to supply the ending step within that PROC.
This is true even if the ending step is the last in the PROC.
SJR0-26 LSTP= MUST BE USED WITH LPSTP=

Explanation: A procedure step name was specified without a corresponding step name.
User Response: Supply a valid procedure step name and then press Enter.
SJR0-27 LCC= REQUIRED AND MUST BE LESS THAN 4096

Explanation: If a LSTP value is specified, LCC must be used to specify the condition code for the
step.
User Response: Supply a valid condition code and then press Enter.
SJR0-28 USAGE= IS REQUIRED

Explanation: The CA-11 installation options require that a usage code be supplied for restarts.
User Response: Supply a valid usage and then press Enter.

6.12 SJRx Messages
SJR0-29 –SJR1-12
SJR0-29 STPSTRT= IS REQUIRED WITH LSTP=

Explanation: If a LSTP value is specified, the starting step name must also be supplied.
User Response: Add the desired step name and then press Enter.
SJR0-32 CONDCD= IS NOT VALID

Explanation: The value specified for the CONDCD keyword is invalid. Value must be numeric, 0
to 4095.
SJR0-33 FORCE= IS NOT VALID

Explanation: The value given for FORCE was not YES. This is the only valid value.
SJR0-34 PROSE= IS INVALID AS USED

Explanation: The value given for PROSE was not YES or NO.
SJR0-35 BYPGDG= IS NOT VALID

Explanation: The value given for BYPGDG was not YES, NO, VER, or CAT.
SJR0-36 REASON REQUIRED BUT MISSING

Explanation: A reason is required for restarts, as specified on the RESTART statement in the
initialization file, but one was not entered.
User Response: Reenter request and supply a REASON parameter.
SJR1-10 RESTART STEP LIST FOR JOB...xxxxxxxx (nnnn) yyyyyyyy aaaaaaaaa bbbbb
Explanation: This message is produced when LIST,JOB=nnnn is done. xxxxxxxx is the job name.
yyyyyyyy is the job prose number (and is 0 when there is no prose). aaaaaaaaa is the failure code
information. bbbbb is the JES job number.
SJR1-12 *NOTE* - JOB ALREADY CONTAINS CA-11 RESTART JCL

Explanation: This is an informational message indicating that the job to be restarted contains
CA-11 JCL, thus making a step restart possible.

6.12 SJRx Messages
SJR1-13 –SJR2-15
SJR1-13 *NOTE* - CA-11 IS NOT AVAILABLE IN CA-7 FOR RESTART

Explanation: The CA-7 initialization file option indicating CA-11 (RMS) availability is not present;
therefore, CA-7 cannot generate the RMS step JCL. If RMS JCL is already present in the job, it
may be used by supplying parameters with the text editor.
User Response: If CA-11 is available, the CA-7 initialization file should be changed. The
RESTART statement is required.
SJR1-14 *NOTE* - RESTART=NO AND CA-11 IS AVAILABLE

Explanation: INSERTRMS=NO is indicated on the Job screen for the job being restarted.
SJR1-15 *NOTE* - JOB RESTARTABLE BY CA-7 USING CA-11

Explanation: This is an informational message indicating the requested job is restartable and CA-11
is available for the restart.
SJR2-00 FORCED COMP - JOB xxxxxxxx(nnnn) COMPLETED AT hh:mm:ss ON yy.ddd

Explanation: The job has been forced to a completed status successfully by a FORCECOMP=YES
parameter.
SJR2-00 RESTART FOR JOB xxxxxxxx(nnnn) COMPLETED AT hh:mm:ss ON yy.ddd

RESTARTED FOR STEP yyyyyyyy (FIRST) THRU zzzzzzzz (LAST).
Explanation: Restart activity for the requested job has been completed. The step where the restart
began is indicated. The ending step (if other than the last step of the job) is also shown.
SJR2-13 STPEND PRECEDES STPSTRT IN JOB

Explanation: The specified ending step of the restart occurs before the specified starting step.
SJR2-14 STPSTRT OCCURS AFTER LAST SUCCESSFUL STEP COMPLETED (xxxxxxxx)

Explanation: The specified starting step for the restart occurs after the last successfully executed
step. This is not a valid restart point.
User Response: Correct and resubmit the command with a valid start step.
SJR2-15 STPSTRT=/STPEND= IGNORED, NO RESTARTABLE STEPS, *RERUN* ASSUMED

Explanation: STPSTRT and/or STPEND were specified but will be ignored because the job has no
restartable steps. A job rerun will be performed.

6.12 SJRx Messages
SJR2-16 –SJR2-22
SJR2-16 JOB *RERUN* IS REQUIRED, CA-11 IS NOT AVAILABLE

Explanation: An attempt was made to do a CA-11 step restart without CA-11. This is not allowed.
User Response: A total job rerun must be done, or the OS Step Restart facility must be used
through a JCL override.
SJR2-17 xxxxxxxx RESULTED IN I/O ERROR ...n

Explanation: The CA-7 macro being used when the I/O error occurred is indicated by xxxxxxxx as
follows:
SGET-DIR - Read the Job data set directory.
SGET-JOB - Read a job entry on the Job data set.
SGET-STEP - Read a step entry on the Job data set.
SQGET - Read a job on the Request queue.
The I/O error return code is indicated by n.
User Response: Resubmit the command. If the error recurs, contact your installation's CA-7 spe-
SJR2-18 xxxxxxxx IS NOT A RESTARTABLE STEP

Explanation: The step specified by STPSTRT is not a valid restart point.
User Response: Correct and reenter the command.
SJR2-20 //*UCC7RESTART CARD NOT FOUND IN JCL

Explanation: The JCL statement which CA-7 uses to communicate restart parameters to CA-11 is
not available.
User Response: If INSERT RMS=Y is specified in the database definition for the job, then a
problem exists with the CA-7 system. Contact your installation's CA-7 specialist for assistance.
SJR2-21 JOB HAS NO STEPS - CANNOT BE RESTARTED

Explanation: An attempt to restart a job failed because the job does not have any steps.
User Response: If the job is supposed to have steps in the JCL, they may be added using the QJCL
facility.
SJR2-22 CMT MEMBER NOT FOUND - USE STPSTRT=*RERUN*

Explanation: An attempt was made to restart the job using STPSTRT=*CMT*, but CA-7 could not
access a CMT member for the job.
User Response: The job should be restarted using the parameter STPSTRT=*RERUN* to rerun the
entire job.

6.12 SJRx Messages
SJR2-23 –SJR2-51
SJR2-23 *CMT* NOT VALID, JOB NOT SET FOR CA-11 RESTART.
Explanation: A RESTART command was issued with STPSTRT=*CMT* but the job was not set
for restart in the CA-11 CMT.
User Response: If the job is to be restarted, use STPSTRT=*RERUN* or supply the specific
starting and ending step names.
SJR2-25 UNABLE TO RESTART, ARF RECOVERY IN PROGRESS

Explanation: CA-7 issues this message when a RESTART command is attempted while ARF is
controlling recovery for a job.
User Response: Wait unitl ARF recovery is complete for the job. You can use the LARFQ
command to track the progress of ARF recovery for the job.
If you must issue the RESTART command prior to the completion of ARF recovery, you can issue
the ARFP command to terminate ARF recovery processing for the job. After the ARFP command
processing completes, you can issue the RESTART command.
SJR2-51 JOB IS NOT RESTARTABLE - USE *RERUN*

Explanation: According to CA-11, the job is not restartable.
User Response: Use the *RERUN* option to resubmit the job for rerun.
SJR2-51 CMT MEMBER NOT AVAILABLE - RETRY LATER

Explanation: Another user in the system has the CMT member for the job under exclusive control.
User Response: Wait a few minutes, then retry the request again. If the problem persists, contact
your installations CA-7 specialist for assistance.
SJR2-51 CMT CHANGED SINCE DISPLAYED - TRY AGAIN

Explanation: Between initial display and update request, the CMT member for the job was updated
by another user.
User Response: Recheck the displayed fields, correct and reenter.
SJR2-51 FATAL ERROR - CA-11 MAY BE DOWN

Explanation: The CA-11 Database Address Space appears to be down.
User Response: Check status of CA-11 and reinitialize if necessary, then try the request again. If
problem persists, contact your installation's CA-7 specialist for assistance.
SJR2-51 START STEP NOT FOUND IN CMT - TRY ANOTHER

Explanation: The requested starting step name for restart was not found in the CMT.

6.12 SJRx Messages
SJR2-51 –SJR2-52
SJR2-51 END STEP NOT FOUND IN CMT - TRY ANOTHER

Explanation: The requested ending step name for restart was not found in the CMT.
SJR2-51 USAGE CODE MUST CHANGE - TRY AGAIN

Explanation: CA-11 options require the usage code to change between runs but the XRST screen
field matches the CMT field.
User Response: Change the usage field on the XRST screen and try again.
SJR2-51 LRTCD STEP NOT FOUND IN CMT BEFORE START STEP

Explanation: A CA-11 restart was attempted, but the step name specified in the LRTCD field is
not prior to the step specified for the starting step.
User Response: Correct the step name(s) and then press Enter.
SJR2-52 JOB FOUND BUT LOAD PROCESSING INCOMPLETE

Explanation: A restart (or force complete) was attempted on a job that is in the LOAD process.
User Response: Allow the job to complete the LOAD process, and then retry the command.

Chapter 7. SLFA - SPOR
This chapter contains the SLFA through SPOR messages.
Chapter 7. SLFA - SPOR 7-1

7.1 SLFA Through SPOE Messages
SLFA-00 –SLIx-02
SLFA-00 ENTER VALUES, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Explanation: Awaiting your choice of functions.
User Response: Display catalog entries by entering the desired values and pressing Enter. To
transfer to another menu or formatted input screen, enter the desired FUNCTION value. Otherwise,
position the cursor to the top line and enter a command.
SLFA-05 INVALID VALUE ENTERED FOR FIELD: xxxxxxxx

Explanation: An error was detected with the contents of the indicated field. The cursor will be
positioned to that field.
SLIx-00 REQUEST COMPLETED AT hh:mm:ss ON yyddd

Explanation: The request completed at the date and time shown.
SLIx-01 aa INVALID SGET RETURN CODE=xx

Explanation: Where:
aa is the SGET macro statement where the error occurred.
xx is the return code from the macro.
If SLIx=SLIA, aa=38 and xx=01, a pointer from the Job data set points to a DSNBR not in the
Dataset data set.
If SLIx=SLIG, aa=B5, and xx=03, a schedule member cannot be read.
User Response: If SLIx=SLIA, aa=38 and xx=01, do another LOAD on the job.
If SLIx=SLIG, aa=B5, and xx=03, try the command again. If the problem persists, contact your
SLIx-02 JOB=xxxxxxxx NOT FOUND

[DSN= x....x)|(DSNBR= x...x)] NOT FOUND
NW=xxxxxxxx NOT FOUND
Explanation: In general, the job, data set name (or node), data set number (or generic), or network
cannot be found in the CA-7 database.
User Response: Verify that the requested job, data set name, data set number, or network is correct
and in the proper format. Format for data sets (by function) is:
LDSN - DSNBR= value must begin with DS.
LPROS - DSN=/DSNBR= value must begin with PP.

SLIx-03 –SLIx-08
In all cases DSN must be the fully qualified name or desired level of node(s).
SLIx-03 REQUIRED INPUT MISSING

Explanation: Either DSN or DSNBR is required for LDSN or LPROS. For other commands, a
required element was not specified.
SLIx-04 CONFLICTING INPUT PARAMETERS

Explanation: Mutually exclusive parameters were specified on the input request.
SLIx-05 INVALID 'LIST=' OPTION

Explanation: The LIST option specified is not allowable for the type of request (that is, LIST=ALL
may not be used with node or generic requests).
SLIx-05 INVALID 'ST=' OPTION

Explanation: The ST option specified is not allowable for the type of request (that is, conflicts with
another option such as LIST=ALL).
User Response: Correct and retry the request.
SLIx-07 INVALID GENERIC NAME OR NODE

Explanation: The format of the DSN node or DSNBR generic name is incorrect as specified.
There might be a bad job entry in the database.
User Response: Correct and resubmit the command. For LPROS, the DSN value must be
DSN=PP, at the least. If using DSNBR the value must be at least DSNBR=xx*, where xx=DS for
LDSN, xx=PP for LPROS, xx=NW for LNTWK or xx=SI/SJ/SO for LSCHD. If a bad job entry
exists, delete the job. This will also delete job schedules, triggers and prose.
SLIx-08 LOAD ERROR FOR xxxxxxxx WITH RETURN CODE nn

Explanation: Module xxxxxxxx failed to load; the return code from the SLOAD macro is specified
by nn.
User Response: If the module name begins with UCC7R, verify that the user-defined Workload
Balancing module was not deleted from the CA-7 load library. If the module is not a WLB module,
make sure it exists on the CA-7 load library and that there is an APPLCTN for the module in either
the initialization file or in the SASSPROG module. If it is present in the load library, contact your

SLIx-09 –SLIA-01
SLIx-09 SEGMENT/SUBSEGMENT NOT FOUND

Explanation: A prose segment and/or subsegment was requested but could not be found within the
prose member specified.
User Response: Reenter with correct values. Listing the entire member allows the correct
segment/subsegment contents to be reviewed.
SLIx-11 YOU ARE NOT AUTHORIZED TO ....text....

Explanation: A command or data access has been denied due to security definition.
User Response: If the command or data access should be allowed, contact your security adminis-
trator.
SLIx-16 JOB xxxxxxxx FOUND BUT NOT WITH OTHER VALUES ENTERED
Explanation: A job was requested and other selection parameters were specified. The job was
found in the database, but the other parameters did not match the values for the job.
User Response: Reenter with correct values or omit the other parameters.
SLIx-17 NO JOBS MATCH PARAMETERS ENTERED

Explanation: There were no jobs found to match the combination of selection parameters requested.
User Response: Reenter with new values if so desired.
SLIx-18 NO SCHEDULES MATCH PARAMETERS ENTERED

Explanation: There were no schedule records found to match the LSCHD parameters requested.
SLIx-19 NO QUEUE RECORDS MATCH PARAMETERS ENTERED

Explanation: Either the queue was empty or none of the records in the queue matched the selection
parameters specified on the command.
SLIX-21 INSUFFICIENT STORAGE - FURTHER QUALIFY THE DSN

Explanation: A listing request was issued which required too much storage to process the request.
User Response: The command should be reissued after qualifying the data set name further.
SLIA-nn Refer to the SLIx messages.

SLIA-01 aa INVALID SGET RETURN CODE=xx
Explanation: A problem was encountered in trying to get a member from the Job data set. If
aa=38 and xx=01, a pointer from the Job data set points to a DSNBR not in the Dataset data set.
User Response: To resolve the pointer, perform another LOAD on the job.

SLIA-07 –SLIE-14
SLIA-07 INVALID GENERIC NAME OR NODE

Explanation: An error was detected in reading the job record from the Job data set on an LJOB
command.
User Response: Delete the job from the DB.1 (JOB) screen. The job must then be added back to
CA-7, including schedules, triggers, prose and all related information.
SLIA-10 JOB= xxxxxxxx FOUND BUT NOT IN SYS= nnnnnnnn

Explanation: Job xxxxxxxx was found but not in system nnnnnnnn.
User Response: Determine if the job is in the system specified. If so, contact your installation's
SLIB-nn Refer to the SLIx messages.

SLIC-nn Refer to the SLIx messages.
SLIC-nn SYSTEM NAME xxxxxxxx NOT FOUND ****
Explanation: The application system ID specified by xxxxxxxx could not be found in the database.
User Response: Verify that the system ID requested is correct; if not, correct and resubmit the
command.
SLIC-nn ****FIRST RECORD OF MBR xxxxxxxx NOT A JOB ENTRY

Explanation: The first record in the database for the job member specified by xxxxxxxx is not a
job entry.
SLIC-nn ****SGETM ERROR****

Explanation: An invalid return code was received from a request for core.
SLIC-16 ****TP DATA SET TABLE IS FULL****

Explanation: More than 500 temporary data sets exist within a job. LSYS can only handle up to
500 temporary data sets in a single job.
SLID-nn Refer to the SLIx messages.

SLIE-nn Refer to the SLIx messages.
SLIE-14 *** OUT OF PAGING SPACE, TRUNCATED ***
Explanation: The data to be listed creates more than 255 online pages of output. The online limit
is 255 and this message indicates that the rest of the data is not listed.
User Response: If all of the data needs to be listed, then use the Batch Terminal Interface. Other-
wise, modify the command to produce less output.

SLIE-15 –SLIF-33
SLIE-15 SGETPDS ERROR - text

Explanation: An error occurred while processing the LJCL command. The error is detailed by text.
Refer to message SM50-14 for possible values for text.
User Response: Correct the error indicated and try again. Refer to message SM50-14 for a specific
text action match.
SLIE-16 EOD ON FIRST READ FOR PDS

Explanation: The JCL member entry in the database points to a null PDS.
User Response: Verify the JCL data set identification and correct if necessary.
SLIE-17 JCL DATA SET NOT FOUND FOR JCLID nnn

Explanation: The JCL data set indicated in the job's database entry is not defined with a JCL
statement in the CA-7 initialization file.
User Response: If the JCLID in the database entry is incorrect, it should be changed. Otherwise, it
will be necessary to add the appropriate JCL statement to the initialization file.
If the JCL for the job is contained in a CA-Librarian or CA-Panvalet file, do the following:
1. Try LLIB command for a more detailed error message.
2. Try a Fetch from the DB.7 (JCL) screen, for a more detailed error message.
SLIE-18 COULD NOT FIND MEMBER: mmmmmmmm

Explanation: The JCL member mmmmmmmm could not be found in the indicated JCL library.
SLIF-nn Refer to the SLIx messages.

SLIF-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd
Explanation: The input request has completed successfully.
SLIF-33 ERROR OCCURRED IN JCL CONVERSION RTN - SASSPCEJ

Explanation: System error.

SLIF-55 –SLIG-16
The following SLIF-55 error messages are concerned with I/O and sort operations. In all
cases, the required action is to contact your installation's CA-7 specialist for assistance.
SLIF-55 SCRGET10 ERROR OCCURRED ON SCRATCH FILE READ.

Explanation: An I/O error.

SLIF-55 SCRPUT25 ERROR OCCURRED ON SCRATCH FILE WRITE.

SLIF-55 SCRPUT30 ERROR OCCURRED ON SCRATCH FILE WRITE.



SLIF-55 SORT-55 ERROR OCCURRED DURING SORT.

Explanation: A sort error.
SLIG-nn Refer to the SLIx messages.

SLIG-16 SYS= INVALID WITH SPECIFIC JOB= REQUEST
Explanation: The SYS= parameter is not valid when the JOB= parameter does not refer to a
generic job name.
User Response: Remove the SYS= parameter and issue the command again.

SLIH-nn –SLIN-17
SLIH-nn Refer to the SLIx messages.

SLIJ-nn Refer to the SLIx messages.
SLIL-48 CRITICAL PATH MANAGEMENT SUPPORT NOT ACTIVE
Explanation: A FLOWL command was issued but the CPM feature is not active.
SLIL-49 NO FLOW RECORDS CHAINED

Explanation: A FLOWL command was issued but there are no active CPM flow records.
SLIL-50 NO FLOW RECORDS SELECTED

Explanation: A FLOWL command was issued but no active CPM flow records matched the speci-
fied selection criteria.
User Response: Check the spelling of the flow name argument and reissue the command.
SLIL-53 INVALID VALUE FOR xxxxxxx

Explanation: An invalid value was specified for the keyword xxxxxxxx.
User Response: Correct the value and reissue the command.
SLIM-nn Refer to the SLIx messages.

SLIN-14 *** OUT OF PAGING SPACE, TRUNCATED ***
Explanation: Refer to explanation for SLIE-14.
User Response: Refer to action recommended for SLIE-14.
SLIN-15 SGETPDS ERROR - text

SLIN-16 EOD ON FIRST READ FOR PDS

SLIN-17 JCL DATA SET NOT FOUND FOR JCLID nnn


SLIN-21 –SLIP-02
SLIN-21 SLOAD FAILED FOR SASSJCKI

Explanation: Unable to access the CA-7 CA-JCLCHECK interface module. The LIST=ONLY
option will be used.
User Response: Make sure SASSJCKI is in a library accessible from CA-7. Issue the
/DISPLAY,A=SASSJCKI command to ensure that there is an entry in the application directory for
the module.
SLIN-22 INTERFACE INTERNAL ERROR

Explanation: A severe error occurred in LJCK processing. A subtask abend may have been
produced.
User Response: Check for any prior messages indicating abnormal termination, collect all output
from the failing command including any dumps that may have been produced and contact your instal-
lation's CA-7 specialist for assistance. If the display indicates a DRIVER ALLOC ERROR, ensure
that all CA-Driver procedure libraries associated with this JCL library are accessible to CA-7.
SLIN-23 JJ01 DETECTED ERROR ON # CARD

Explanation: An attempt to evaluate scheduled overrides (for example, #JI/#JO statements) failed.
Probably a syntax error.
User Response: Check the JCL for any invalid # statements. Correct the JCL and try again.
SLIN-24 INVALID JCLLIB VALUE

Explanation: The value specified on the JCLLIB keyword is invalid. The value must conform to
the syntax described for the INDEX keyword on the JCL statement in the CA-7 initialization file.
The parameter must either be 1-3 numeric characters specifying a value between 0 and 255 or it must
begin with an ampersand and be followed by from 1-15 alphanumeric characters.
SLIN-25 CONFLICT IN JOB AND MEM

Explanation: Both JOB and MEM keywords were specified on the LJCK command. These
keywords are mutually exclusive.
User Response: Determine which keyword is appropriate for the command and re-enter.
SLIP-01 SQGET-DS QUE HDR. EC1=65 EC2=xx

Explanation: A processing error; xx is the return code.
User Response: If xx=01, then a job has probably changed queues during the processing of the LQ
command being done. Re-enter the command. If the error persists contact your installation's CA-7
SLIP-02 SQGET-DS QUE HDR. EC1=66 EC2=xx


SLIP-04 –SLIP-34
SLIP-04 xxxxxxxx PARAMETER IS NOT YET AVAILABLE

Explanation: Keyword xxxxxxxx is not valid for this command.
User Response: Omit the keyword and resubmit the command.
SLIP-08 SQG-NHDR SPECIFIC JOBNAME REQUIRED FOR Q=PRN

Explanation: Generic job name search is not allowed on Prior-run queue.
User Response: Reenter with correct values.
SLIP-13 SQG-FRQM QUE RQMT. EC1=71 EC2=xx SEGMENT.

SLIP-14 SQG-NRQM QUE RQMT. EC1=72 EC2=xx SEGMENT.

SLIP-21 SQG-NRQM QUE RQMT. EC=79 EC2=xx

SLIP-29 SQG-FJCL QUE JCL. EC1=81 EC2=xx

SLIP-30 SQG-NJCL QUE JCL. EC1=82 EC2=xx

SLIP-33 SQG-NJCL ERROR OCCURRED IN JCL CONVERSION RTN - SASSPCEJ

Explanation: Processing error. xx is the return code.
SLIP-34 SORT-xx ERROR OCCURRED DURING SORT.

Explanation: Sort error indicated by xx. Where xx can be one of the following:
04 - I/O error
08 - segment length error
12 - work space error

SLIP-81 –SLIR-05
SLIP-81 SCRGET-F SCR. EC1=51 EC2=xx

SLIP-82 SCRGET SCR. EC1=52 EC2=xx

SLIP-85 SCRPUT SCR. EC1=55 EC2=xx

User Response: If xx=00, check the DAIO statement in the initialization file. The
SCRTRK/SWFTRK parameter may need to be increased.
SLIP-97 SQG-FHDR QUE HDR. EC1=61 EC2=xx

SLIP-98 SQG-NHDR QUE HDR. EC1=62 EC2=xx

SLIR-02 xxxxxxxx FAILED FORMAT BLOCK EDIT.

Explanation: An error was found by the format routine for the keyword specified by xxxxxxxx.
SLIR-03 xxxxxxxx DATA SUBMITTED IS TOO LONG

Explanation: Keyword xxxxxxxx is not valid.
SLIR-04 xxxxxxxx PARAMETER IS NOT YET AVAILABLE

User Response: Correct the value or omit the keyword and resubmit the command.
SLIR-05 xxxxxxxx DATA VALUE SHOULD NOT BE USED


SLIR-06 –SLIR-52
SLIR-06 xxxxxxxx DATA VALUE IS NOT VALID

SLIR-07 xxxxxxxx IS A REQUIRED PARAMETER

Explanation: Keyword xxxxxxxx is required but was omitted from the input request.
User Response: Supply the missing keyword (with an appropriate value) and resubmit the
command.
SLIR-32 xxxxxxxx SEGMENT STATUS CONTAINS AN INVALID VALUE

Explanation: A program change caused an invalid segment status to be detected by the SASSSLIR
module, xxxxxxxx is the keyword.
SLIR-49 xxxxxxxx INVALID WITH THIS FUNCTION

Explanation: Keyword xxxxxxxx is a valid keyword, but it cannot be used with the current
command.
User Response: Determine if the command or the keyword is in error. Correct the error and
resubmit the command.
SLIR-50 xxxxxxxx ERROR. OUTAGE= and SPAN= ARE MUTUALLY EXCLUSIVE.

Explanation: Keyword xxxxxxxx is a valid keyword, but the OUTAGE and SPAN keywords
cannot both be used in the same command.
User Response: Specify either OUTAGE= or SPAN= and resubmit the command.
SLIR-51 xxxxxxxx START DATE OR DURATION IS REQUIRED.

Explanation: Keyword xxxxxxxx has a valid format, however, the first operand is omitted (start
date, or, duration). This parameter is required.
User Response: Specify either the start date, or a duration as the first parameter of the SPAN= or
OUTAGE= keyword and resubmit the command.
SLIR-52 xxxxxxxx ERROR. BAD ELEMENT IS yyyyyyyy

Explanation: Keyword xxxxxxxx has an error in the sublist. Parameter yyyyyyyy is the sublist
element in error.
Possible values for yyyyyyyy are:
START DATE
START TIME
END DATE
END TIME
User Response: Correct the keyword sublist to provide valid data for the command being used and

SLIR-53 –SLIT-03
SLIR-53 xxxxxxxx ERROR. IF DURATION, MUST BE ONLY VALUE.

Explanation: Keyword xxxxxxxx is either OUTAGE= or SPAN= and the parameter is specified as
a sublist. The first operand is specified as an absolute number rather than a Julian or Gregorian Start
Date.
User Response: Specify either the start date as the first parameter, or specify duration as the only
parameter and resubmit the command.
SLIR-54 xxxxxxxx ERROR. END DATE/TIME MUST BE GT START DATE/TIME.

Explanation: Keyword xxxxxxxx is either OUTAGE= or SPAN= and the parameter is specified as
a sublist of starting date/time (first two parameters) and ending date and time (second two parame-
ters). The ending date and time is equal to or less than the starting date and time which is a logical
error.
User Response: Correct the dates and times in the sublist and resubmit the command.
SLIR-55 xxxxxxxx ERROR. RANGE EXCEEDS MAXIMUM.

Explanation: Keyword xxxxxxxx is either OUTAGE= or SPAN=. The difference between the
starting date and time and the ending date and time cannot be greater than one year.
SLIR-56 xxxxxxxx ERROR. RANGE EXCEEDS MAXIMUM.

Explanation: Keyword xxxxxxxx is either OUTAGE= or SPAN=. The difference between the
starting date and time and the ending date and time is greater than one year which exceeds the
maximum range.
SLIR-56 xxxxxxxx ERROR. START DATE/TIME GT CURRENT DATE/TIME.

Explanation: Keyword xxxxxxxx is either OUTAGE= or SPAN=. The starting date and time spec-
ified on the keyword is greater than the current date and time which is a logical error.
SLIT-nn Refer to the SLIx messages.

SLIT-02 INVALID DATE CONVERT FIELD
Explanation: An error occurred in the date conversion.
SLIT-03 INVALID MODULE CODE

Explanation: An invalid internal module code has been detected during the use of the LWLB func-
tion.

SLIT-09 –SLIW-05
SLIT-09 INVALID MOD=VALUE

Explanation: The MOD= value on the LWLB command does not start with UCC7R.
User Response: Correct the MOD= value and retry.
SLIU-nn Refer to the SLIx messages.

SLIW-01 NO RECORDS MATCHED ARFSET=&ARFSET
Explanation: The entire ARF database was searched. Either the ARF database contains no ARF
Sets or there were no ARF Sets found that met the search criteria. Note that UID level security is
checked for each ARF Set Record. The terminal user must have UID security access to a given ARF
Set before that record can be displayed. &ARFSET is the ARFSET= value that was used for the
search.
SLIW-02 ARF IS NOT ACTIVE, ARF DB CANNOT BE ACCESSED

Explanation: The LARF command depends upon the internal ARF control block structure in order
to complete normally. ARF is not active in this execution of CA-7.
User Response: Ensure the CA-7 startup parameter input contains a 'RESTART,ARF=YES' or a
'RESTART, ARF=MAINT' control statement. If one was included, some error occurred during
startup that caused ARF to be disabled. Search the console log for CA-7 startup messages relating to
ARF.
SLIW-03 ARF DB INIT FAILED - RC=&RC RS=&RR

Explanation: The LARF command was attempting to access the ARF database, but an error was
detected before the database was accessed. &RC is the return code and &RR is the reason code.
User Response: Retry the command to ensure that a temporary shortage of system resources was
not the problem.
SLIW-04 ARF DB BEGIN SEQ FAILED - RC=&RC RS=&RR

Explanation: The LARF command was attempting to orient on the ARF Sets within the ARF data-
base, but an error was detected during the access. &RC is the return code and &RR is the reason
code.
not the problem. Review the console log for VSAM related error messages being produced by CA-7
itself.
SLIW-05 ARF DB GET NEXT FAILED - RC=&RC RS=&RR

Explanation: The LARF command was reading through the ARF Sets within the ARF database
when an unexpected error was detected. &RC is the return code and &RR is the reason code.
not the problem. Review the console log for VSAM related error messages being produced by CA-7
itself.

SLIW-xx –SLIW-xx
SLIW-xx ERROR WIP=&WIP RC=&RC RS=&RR, ARFDATA1 IS: &TEXT

Explanation: An unexpected internal error occurred. &WIP is the two byte internal WIP code.
&RC is the current internal return code. &RR is the current internal reason code. &TEXT is the
current text area being manipulated.
User Response: Present this information to the CA-7 support staff.

SLIY-01 –SLIY-xx
7.1.1 SASSSLIY Messages

SLIY-01 NO QUEUE ELEMENTS FOUND FOR JOB=&JOB
Explanation: The entire ARF queue was searched. Either the ARF queue is empty or there were
no ARF queue elements found that met the search criteria. Note that UID level security is checked
for each ARF queue element based on the UID associated with the ARF Set (rather than the job).
The terminal user must have UID security access to a given ARF queue element before that element
can be displayed. &JOB is the JOB= value that was used for the search.
SLIY-02 ARF IS NOT ACTIVE, ARF DB CANNOT BE ACCESSED

Explanation: The LARFQ command depends upon the internal ARF control block structure in
order to complete normally. ARF is not active in this execution of CA-7.
User Response: Ensure the CA-7 startup parameter input contains a 'RESTART,ARF=YES' or a
'RESTART, ARF=MAINT' control statement. If one was included, some error occurred during
startup that caused ARF to be disabled. Search the console log for CA-7 startup messages relating to
ARF.
SLIY-03 INVALID LIST OPTION - &LIST

Explanation: The LIST= option was specified on the LARFQ command. &LIST reflects the value
which was given on the command. This is not a valid choice. Refer to the command descriptions
for the valid choices.
User Response: Correct the LIST= specification and retry the command.
SLIY-04 INVALID JOB NAME/NBR GIVEN - &JOB

Explanation: The JOB= parameter was specified on the LARFQ command. &JOB reflects the
value which was given on the command. Either a specific CA-7 job number may be given here or a
job name (full or generic). The value given is not valid. Refer to the command descriptions for
details.
User Response: Correct the JOB= specification and retry the command.
SLIY-xx ERROR WIP=&WIP RC=&RC RS=&RR, ARFDATA1 IS: &TEXT

Explanation: An unexpected internal error occurred. &WIP is the two byte internal WIP code.
&RC is the current internal return code. &RR is the current internal reason code. &TEXT is the
current text area being manipulated.
User Response: Present this information to the CA-7 support staff.
SLI0-nn Refer to the SLIx messages.
SLI0-12 *xxxxxxxx* IS AN INVALID FUNCTION
Explanation: The function specified by xxxxxxxx is invalid.
User Response: Correct the function identifier and resubmit the command.

SLI0-13 –SLI0-17
SLI0-13 INPUT DATA IS NULL

Explanation: No input command was available.
User Response: Resubmit the command with input.
SLI0-14 INPUT DATA IS INCOMPLETE

Explanation: A partial input command was received. Not enough data available to process the
request.
User Response: Supply sufficient data to process the request and resubmit the command.
SLI0-15 TOO MUCH INPUT DATA

Explanation: Extraneous data was found on the input command.
SLI0-16 INVALID KEYWORD OR DATA IN INPUT

Explanation: An unknown keyword or other invalid input was detected.
SLI0-17 INVALID DATA FOUND FOR THE FOLLOWING FIELDS.

xxxxxxxx xxxxxxxx xxxxxxxx
Explanation: The keyword or name of the data found to be invalid is specified by xxxxxxxx.
Invalid data can be:
2. Nonalphabetic data specified for an alphabetic parameter.
3. Too much or too little data given for a parameter.
4. Invalid decimal point or sign (+/-) given for a parameter.

7.2 SMF0
SMF0-12 –SMF0-15
7.2 SMF0
SMF0-12 JOB xxxxxxxx (nnnn) ACTIVE ON MAIN.

Explanation: An SMF type 20 (job initiation) record has been received by CA-7, which indicates
that the job is now active on the CPU. If nnnn=0000, the job was resubmitted while active on
MAIN.
User Response: This is an informational message. No action is required.
SMF0-13 LOCATE FAILED FOR DSN=x...x

JOB=xxxxxxxx,STEP=yyyyyyyy,DD=zzzzzzzz
Explanation: An SMF type 14/15 (data set) record has been received by CA-7, but the data set is
not found in the CA-7 IDS. The jobname, stepname and ddname that referenced the data set are
shown as indicated.
User Response: None. This usually occurs only when a job is being loaded for the first time.
SMF0-14 BAD RECORD=x....x

Explanation: An invalid record type was found while processing CA-7 SMF records.
SMF0-15 JOB xxxxxxxx (nnnn) HAS BEEN PURGED FROM HOST SYSTEM.
**********
**********
**********
JOB xxxxxxxx (nnnn) IN RDY 'Q' MAY HAVE A JCL ERROR.
CHECK THE JOB'S SYSOUT AND REQUEUE THE JOB IF NECESSARY.
**********
**********
**********
Explanation: An SMF type 26 record was received by CA-7 for a job submitted by CA-7, and the
job name xxxxxxxx was found in the Ready queue.
User Response: If the type 26 record is for the current run of this job, then the job either had a
JCL syntax error or was possibly canceled in JES. If the job needs to be restarted, then it must be
requeued back to the Request queue. The type 26 record could be for a previous run of this job (for
example, yesterday's run) and it has just finished printing and is now going through JES purge. In
this case this message can be ignored and the condition will clear itself when the SMF Job Initiation
record is received for the job.
Many of these messages have been eliminated because CA-7 can check the JES job number.
However, there are some cases where the JES job number is not available while the job is in the
CA-7 RDYQ. (For example, if a submit data set is used instead to the INTRDR.)
Note: A JES inquiry by job name will show if the current run of the job is still in the JES Q.

7.2 SMF0
SMF0-16 –SMF0-21
SMF0-16 JOB xxxxxxxx HAS BEEN PURGED FROM HOST SYSTEM

Explanation: An SMF type 26 record was received by CA-7 for a job. This informational message
denotes that all printing is complete for a job.
SMF0-17 TYPE 99 RECORD REJECTED FROM JOB = xxxxxxxx DSN=x...x

Explanation: A pseudo-SMF record (type 99) and an SMF type 15 record were received by CA-7;
the job creating them was a CA-7 job not marked as maintenance. To avoid double posting, the
record was dropped.
User Response: The SCHID on the type 99 record may have been different than the SCHID of the
job creating the type 99. Check to make sure the proper jobs were triggered. Update the CA-7
database definition of the job to mark it as maintenance.
SMF0-18 JOB xxxxxxxx (nnnn) HAS JCL ERROR ***RESTART REQUIRED***

Explanation: The specified job was terminated by a JCL error.
User Response: Analyze the JCL to determine the problem; JCL errors may occur because of an
incorrect override. To correct the JCL error, overrides must be corrected or added in the Request
queue. Job Restart must then be used to resubmit the job.
SMF0-19 JOB xxxxxxxx(nnnn) ABNORMALLY TERMINATED,

***RESTART REQUIRED***
FAILING CODE=[(S)|(U)] cccc. LAST STEP EXECUTED= yyyyyyyy
Explanation: The specified job has abended. The system (S) or user (U) completion code is indi-
cated by cccc. The last step executed was yyyyyyyy.
User Response: The abend must be analyzed to determine what corrective action is necessary.
Once the appropriate steps have been taken, Job Restart must be used to resubmit the job.
SMF0-20 JOB xxxxxxxx (nnnn) COND CODE CHECK FAILED

***RESTART REQUIRED***
FAILING CODE=cccc. FAILING STEP=yyyyyyyy.
Explanation: The specified job generated a condition code in one of its steps, and the code failed
the test defined in CA-7's database. The condition code that failed the test is cccc. The last step
which executed is yyyyyyyy.
User Response: The situation must be analyzed to determine corrective action. Once the appro-
priate steps have been taken, Job Restart must be used to resubmit the job.
SMF0-21 JOB xxxxxxxx (nnnn) #SCC CHECK FAILED ***RESTART REQUIRED***

FAILING CODE=cccc. FAILING STEP={pppppppp.}yyyyyyyyy.
Explanation: The specified job generated a condition code in one of its steps, and the code failed
the test defined by the #SCC statements in the job's JCL. The condition code that failed the test is
cccc. The step which failed is yyyyyyyy (and optional procstepname of pppppppp).

7.2 SMF0
SMF0-22 –SMF0-33
SMF0-22 JOB xxxxxxxx (nnnn) #SCC CHECK FAILED ***RESTART REQUIRED***

STEP FLUSHED. STEPNAME={pppppppp.}yyyyyyyy.
Explanation: The specified job flushed one of its steps, and failed the test defined by the #SCC
statements in the job's JCL. The step which failed is yyyyyyyy (and optional procstepname of
pppppppp).
SMF0-30 JOB jjjjjjjj (nnnn) NOT ADDED, DUPLICATE JOB IN RDY/ACT QUEUE
Explanation: The job indicated by jjjjjjjj is an externally submitted job and was not added to the
Active queue because there was already a job by the same name in the Ready or Active queue.
CA-7 will not track this external job through job completion.
SMF0-31 JOB jjjjjjjj (nnnn) NOT ADDED TO ACTIVE QUEUE, SQADD ERROR
Explanation: The job indicated by jjjjjjjj is an externally submitted job and was not added to the
Active queue because there was an error while trying to add it.
User Response: Check the allocation of the Active queue to make sure there is adequate space.
The DMPQ/MOVQ process may be used to change queue allocations.
SMF0-32 JOB jjjjjjjj (nnnn) SECURITY SEGMENT NOT ADDED, SQADD ERROR
Explanation: An error occurred trying to build the security segment in the Trailer queue for an
externally submitted job. A record was added to the Active queue without a security segment. The
external job will be unable to propagate a security USERID to any triggered jobs.
User Response: Check the allocation of the Trailer queue to make sure there is adequate space.
The DMPQ/MOVQ process may be used to change queue allocations.
SMF0-33 JOB jjjjjjjj (nnnn) REQUEUED (IPL) *** RESTART REQUIRED ***
Explanation: The specified job was active on a system which was IPL'd, and the CA-7 AUTOREQ
option is in effect. The job is automatically moved to the REQUEST queue with a status of
R-REQUE and must be manually restarted.
User Response: The situation must be analyzed to determine whether or not corrective actions are
necessary. Once the appropriate steps have been taken, Job Restart must be used to resubmit the job.

7.2 SMF0
SMF0-34 –SMF0-34
SMF0-34 AUTO-REQUEUE FEATURE INACTIVE - IPL RECORDS IGNORED.

Explanation: An IPL of the system within the CA-7 complex was detected, and the AUTOREQ
option is not in effect. Any jobs active on systems at the point of an IPL will be left in the Active
queue. Jobs left in the Active queue following a system failure such as this must be manually
requeued to the Request queue (see the REQUEUE command). This message is displayed only once.
User Response: All jobs left stranded in the Active queue following the system failure must be
manually requeued to the Request queue (see the REQUEUE command).
To activate the Auto-Requeue feature, refer to the AUTOREQ keyword on the OPTIONS initializa-
tion statement in the CA-7 Systems Programmer Guide.

7.3 SMxx Messages
SM10-00 –SM11-03
7.3 SMxx Messages
SM10-00 SPECIFY OPTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Explanation: This is the prompt used to request selection of a prose type. If an error is made in
the selection, this message will be reissued.
SM11-00 ENTER INPUT DATA


Explanation: The requested function was successful.
SM11-00 xxxxxxxx FUNCTION SUCCESSFUL FOR PPnnnnnn

Explanation: The requested function was successful. The prose member affected is identified.
SM11-01 xx INVALID MACRO RETURN CODE nnnn.

Explanation: If xx=P1 and nnnn=0002, error can occur when saving a new member to the Dataset
data set. Indicates an existing DSNBR was assigned to the new member resulting in two members
with the same DSNBR. This can occur if the Dataset data set is reinitialized. The data set should
not be reinitialized once it is in use, even when moving, compressing, or expanding it. If xx=05, the
data set is out of space and it is necessary to compress the data set.
User Response: Contact your installation's CA-7 specialist. If it is determined that the Dataset data
set was reinitialized and if a backup of the entire database (Job, Dataset and Index data sets) is
available, do a restore.
SM11-02 xxxxxxxx NOT FOUND

Explanation: The identified member was not found.
User Response: Check for correct input. If there is an error, correct and retry.
SM11-03 OUT OF SPACE ON DATA BASE

Explanation: Part of the database is full. Refer to WTO on the system log to determine which file
had the error.
User Response: After shutting down CA-7:

7.3 SMxx Messages
SM11-04 –SM11-13

SM11-04 CONFLICT IN DSN AND DSNBR

Explanation: Both DSN and DSNBR were input, but these values are in conflict.
User Response: Correct or delete one specification (both are not required) and retry.
SM11-05 INVALID OR OMITTED xxxxxxxx DATA

Explanation: If the CA-7 Index data set is an OS catalog, there are possible restrictions on prose
member names. If User Prose has been defined using the job name as the User Prose name, then Job
Prose cannot be defined. This restriction does not apply when using a VSAM data set for the CA-7
Index data set.
User Response: Correct the field in error and retry.
SM11-07 PROSE MEMBER ALREADY EXISTS

Explanation: A SAVE function was entered for an existing prose member.
User Response: If you wish to change an existing prose member, use an REPL function.
SM11-08 YOU ARE NOT AUTHORIZED TO ACCESS THAT JOB

Explanation: An attempt was made to alter or add prose for a job that is not accessible due to UID
security.
User Response: If you need to change an existing prose member or to add a new one, contact your
SM11-09 YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

Explanation: A function was entered that the operator is not authorized to do.
User Response: If the operator should be allowed to enter the function, then the security adminis-
trator should be contacted.
SM11-10 UNRECOGNIZABLE DATA IN INPUT

Explanation: Input was received which was not recognized by the program.
SM11-13 NO SAVE -- ACTIVE FILE EMPTY

Explanation: An attempt was made to SAVE or REPL a prose member, but the Active Area con-
tains no lines of text.
User Response: Use the text editor to add line(s) of text to the Active Area. After the text lines
have been added, reissue the command.

7.3 SMxx Messages
SM2E-00 –SM20-02
SM2E-00 CHOOSE A FUNCTION OR ENTER A COMMAND ON THE TOP LINE

Explanation: Awaiting your choice of functions.
User Response: Transfer to another menu or formatted input screen by entering the desired FUNC-
TION value. Otherwise, position the cursor to the top line and enter a command.
SM20-00 ENTER FUNCTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Explanation: This is the prompt used to request input data online.

Explanation: This is the prompt to request input data in batch.
SM20-00 xxxxxxxx SUCCESSFUL [nnn DATASET(S) DELETED]

[,DEFAULTJOB USED FOR DEFAULT VALUES]
[,RESIDUALS PURGED.]
[WARNING: SOME RESIDUAL ELEMENTS COULD NOT BE DELETED.]
Explanation: The requested function was successful. If the DD or PURGE function was entered,
the number of data sets deleted is denoted by nnn. DEFAULTJOB USED FOR DEFAULT
VALUES will be appended, if an ADD function was performed and a job with the name
DEFAULTS was found in the database and was used to provide the default values for the job being
added.
If the PURGE function was entered, the text RESIDUALS PURGED will be appended if all elements
connected to the job were successfully removed. If any of these residuals could not be deleted, the
warning SOME RESIDUALS COULD NOT BE DELETED is present on the next line.
SM20-01 xx INVALID MACRO RETURN CODE nnnn

Explanation: An error has occurred in the processing of the Job data set.
User Response: IF xx=C2 and nnnn=0000, the Job data set may be out of space. If xx=82 and
nnnn=0000, the job member had an error which may have left prose, data set, and index entries for
this job even though the job and any triggers have been deleted. The job should be deleted from
CA-7's database. When any of these errors occur, it is recommended that commands TRIG, RQMT,
and XREF be executed to update the database and correct pointer errors; then run the Database Ver-
ification program to check for stranded members. This may require backing up and reloading the
database with SASSBK00.
SM20-02 JOB NOT FOUND

Explanation: The requested job was not found in the CA-7 database.

7.3 SMxx Messages
SM20-03 –SM20-10
SM20-03 OUT OF SPACE ON DATABASE

had the error.
SM20-05 INVALID OR OMITTED xxxxxxxx DATA [,REJECTED BY USER EXIT]

Explanation: The identified field contains invalid data or the SASSXX10 user exit has denied the
request.
User Response: If the command is being done through a batch terminal, and the message reads
INVALID OR OMITTED FUNCTION DATA, it may be a security violation, rather than a command
error. Check with your installation's CA-7 specialist to determine the security restrictions for the
batch terminal and operator. If the SASSXX10 user exit has rejected the request, then check with
your installation's CA-7 specialist for information regarding why the rejection occurred.
SM20-07 JOB ALREADY EXISTS

Explanation: An ADD function was entered, but the job already exists in the CA-7 database.
User Response: Use the UPD function to change existing job information if desired.

Explanation: An attempt was made to alter or add a job definition that is not accessible due to UID
security.
User Response: If you need to change an existing job or to add a new one, contact your security
administrator.



7.3 SMxx Messages
SM20-12 –SM30-02
SM20-12 USER NOT AUTHORIZED FOR OWNER ID

Explanation: An attempt was made to add or update the OWNER field for a job on the DB.1
(JOB) screen. The operator was not authorized to submit for the USERID in the OWNER field.
User Response: If security access should be allowed, authorize the operator for the USERID being
added or updated in the Job Owner field.
SM20-15 ARFSET NOT DEFINED

Explanation: An attempt was made to add or update the ARFSET field for a job on the DB.1
(JOB) screen. The ARFSET specified is not defined to CA-7.
User Response: Correct the ARFSET name, or define the ARFSET before connecting a job to it.



Explanation: The requested function was successful.

Explanation: If nnnn=0000, the Dataset data set may be out of space. If xx=33 and nnnn=04E6,
the error may have occurred while adding a DSN. The DS0 member of the Dataset data set may
have been lost. Check for this with the DUMP,DSNBR=DS0 command.
If xx=33 and nnnn=05E8, and the error persists, the DS0 member of the Dataset data set may contain
an invalid pointer. In this case, you should contact your installation's CA-7 specialist for assistance.
User Response: If you are installing CA-7, verify that the CDSI program in installation Job N030
ran successfully. Use SASSBK00 to back up and reload the CA-7 database.
SM30-02 DSN NOT FOUND

Explanation: The requested data set was not found in the CA-7 database.

7.3 SMxx Messages
SM30-03 –SM30-13

had the error.
1. Back up the database using SASSBK00.
2. Change DBPARMS.
4. Reload the database using SASSBK00.

Explanation: Both DSN and DSNBR were input, but these values are in conflict.
User Response: Correct or delete one specification (both are not required), and retry.

Explanation: The identified field contains invalid data.
User Response: Correct the field error and retry.
SM30-08 DSN ALREADY EXISTS

Explanation: An attempt was made to add a data set definition that is already in the CA-7 data-
base.
User Response: If you need to change an existing data set definition, use the UPD function.


SM30-13 DSN HAS USERS -- CANNOT DELETE

Explanation: An attempt was made to delete a data set which is still referenced by jobs in the
database. These references were created by loading a job or adding DSN requirements.
User Response: None. The data set name cannot be deleted from the database at this time.

7.3 SMxx Messages
SM30-14 –SM4x-03
SM30-14 CA-7 IDS FAILURE. RC=nnnnnnnn

Explanation: An unexpected error occurred while accessing or updating the CA-7 IDS. If the error
occurred during a LOAD of a job, this message could indicate a DSN that is not cataloged or had no
VOLSER specified in the JCL. If RC=0, the IDS is full and must be expanded.
User Response: If the error was a DSN not cataloged or no VOLSER specified, then either catalog
the DSN or add a VOLSER parameter to the JCL, and reissue the LOAD command. If RC=0:
1. Shut down CA-7.
2. Back up the entire database.
3. Reallocate the IDS.
4. Reload the database while CA-7 is down.
5. Bring up CA-7 with TYPE=ERST.


SM40-00 xxxxxxxx FUNCTION SUCCESSFUL FOR NWnnnnnn

Explanation: The requested function was successful. The network member affected is identified.
SM4x-01 ww INVALID MACRO RETURN CODE nnnn

Explanation: An error condition was detected by the program. If nnnn=0000, the Dataset data set
or Index data set may be out of space.
User Response: If nnnn=0000, check the system console for error messages and if the out-of-space
condition is indicated, increase the size of the failing data set. Otherwise, contact your installation's
SM4x-02 NETWORK NOT FOUND

Explanation: The requested network was not found in the CA-7 database.
SM4x-03 OUT OF SPACE ON DATA BASE

had the error.

7.3 SMxx Messages
SM4x-05 –SM4x-14
SM4x-05 INVALID OR OMITTED xxxxxxxx DATA

SM4x-06 COULD NOT ffffffff NETWORK CONTROL RECORD

Explanation: An error occurred trying to access the DS000000 record from the database. If ffffffff
is FIND, the record was not found. If ffffffff is UPDATE, the error occurred while trying to replace
the record.
SM4x-07 NETWORK ALREADY EXISTS

Explanation: An ADD function was entered, but the network already exists in the CA-7 database.
User Response: Use the UPD function to change existing network information if desired.
SM4x-09 YOU ARE NOT AUTHORIZED TO DO THAT FUNCTION

SM4x-10 UNRECOGNIZABLE DATA IN INPUT

SM4x-12 NETWORK TYPE CANNOT BE CHANGED

Explanation: A UPD function was specified attempting to change the network type from INPUT to
OUTPUT or vice versa. This cannot be done.
User Response: Correct or eliminate the network type data and retry.
SM4x-13 NUMBER OF STATIONS CANNOT BE CHANGED

Explanation: A UPD function indicated an increase or decrease in the number of stations. This
cannot be done if the network already has a schedule.
User Response: Delete the schedule, do the update, and then add an appropriate schedule.
SM4x-14 NETWORK HAS JOB REFERENCES AND CANNOT BE DELETED

Explanation: An attempt was made to delete a network which is currently connected to at least one
job.
User Response: The network must be disconnected from all jobs before it may be deleted.

7.3 SMxx Messages
SM4x-15 –SM50-00
SM4x-15 BAD RETURN FROM IDS FOR xxxxxxxxyyyyyyyy

Explanation: An error occurred while accessing or updating the CA-7 IDS. xxxxxxxx denotes the
element and yyyyyyyy denotes the return code.
SM4x-16 NETWORK IN CONFLICT WITH EXISTING STATION

Explanation: An attempt was made to add a network. This network name conflicts with an
existing station name. This causes an index conflict.
User Response: Select another name for the network and retry.
SM4x-17 STATION xxxxxxxx IN CONFLICT WITH EXISTING NETWORK

Explanation: The specified station name was used with an ADD or UPD function. This station
name conflicts with an existing network and causes an index conflict.
User Response: Select another name for the station identified and retry.



SM50-00 xxxxxxxx FUNCTION SUCCESSFUL [JOB SET FOR RELOAD]

Explanation: The requested function completed successfully. A replace has been done for a JCL
member and the corresponding job has been set to be reloaded on the next run.
User Response: If the changes are not to impact the database, set the RELOAD indicator to N by
using the DB.1 (JOB) screen of Database Maintenance. Otherwise, no action is necessary. Also, if
RELOAD of x is used for this job on the JOB screen, then the reload indication for the next run will
be ignored.
SM50-00 xxxxxxxx FUNCTION SUCCESSFUL xxxxxxxx(nnnn) ADDED TO THE REQ 'Q'

Explanation: The RUN or RUNH function completed successfully. The job name and the CA-7
assigned number are identified in the second line of the message.

7.3 SMxx Messages
SM50-00 –SM50-10
SM50-00 xxxx FUNCTION SUCCESSFUL (JCL SET FOR RETRIEVAL FROM OVERRIDE LIB)
Explanation: The requested function completed successfully. A new JCL member has been added
(through SAVE function) or replaced (through REPL function) in the JCL Override library of ID
254. The next time the job is executed (either by demand or through Schedule Scan functions), JCL
will come from this Override library.
SM50-01 xx INVALID MACRO RETURN CODE xxxxxxxx

Explanation: An unusual condition was detected by the program.
User Response: If xx=L5 and nn=00, an error probably occurred in the attempt to edit a large
member in the EWF. Increase the SWFTRK allocation on the DAIO statement in the initialization
file.
SM50-04 CONFLICT IN DSN, VOLSER, OR JCLID

Explanation: A combination of DSN, VOLSER, and JCLID were input, but their values were in
conflict.
User Response: Delete or clear the unnecessary fields and retry.



Explanation: Input received was not recognized by the program.
SM50-10 JOB (xxxxxxxx) ENTERED INTO REQUEST Q.

Explanation: This message is sent to the Master Station. Indicates that a job entered the Request
queue by a RUN or RUNH command from the DB.7 (JCL) screen.

7.3 SMxx Messages
SM50-12 –SM50-14
SM50-12 JCL FE NOT VALID FOR 7UNI JOBS WITHOUT MIXED CASE SUPPORT
Explanation: The JCL screen will not allow a FE function for members that have a #7UNI as the
first statement unless CA-7 mixed case editor support has been enabled.
User Response: If the JCL member must be modified, then use an external editor (for example,
TSO ISPF - not under CA-7).

Explanation: An attempt was made to SAVE or REPL a member, but the Active Area is empty.
User Response: After the Active Area is set to contain the desired data, retry.
SM50-14 text
Explanation: An error occurred while accessing or updating the data set. The message text should
be one shown on the following list. The list shows a return code in front of the message, but the
return code is not displayed. These return codes are shown in their hexadecimal representation.
08 - DSN NOT FOUND IN CATALOG
0C - DATASET NOT FOUND ON VOLUME
10 - INVALID DSORG
14 - INVALID DCB ATTRIBUTE
18 - DASD VOLUME NOT AVAILABLE
1C - MEMBER NOT FOUND
20 - READ I/O ERROR
20 - WRITE I/O ERROR
24 - DATASET IS PASSWORD PROTECTED or
CA-7 DOES NOT HAVE THE REQUIRED DSN ACCESS
28 - DATASET IS USERID PROTECTED
2C - MEMBER ALREADY EXISTS
30 - NEW NAME ALREADY EXISTS
34 - STOW ERROR
38 - DATASET OUT OF SPACE
3C - DATASET IS DATE PROTECTED
40 - INVALID PARM DATA
54 - DATASET IS BUSY
58 - INVALID DDNAME SPECIFIED
5C - SVC99 ERROR, RF=xxxxxxxx, S99ERROR=yyyyyyyy
60 - ABEND CONDITION DETECTED (xxx-yy)

7.3 SMxx Messages
SM50-14 –SM50-14
For JCL on a CA-Librarian or CA-Panvalet file, pseudo codes appear in front of the message ONLY
as a reference to action to be taken.
L1 - LIB** CA-LIBRARIAN FAIR HAS NOT BEEN LINKED WITH SASSLIB3
L2 - LIB** CA-LIBRARIAN INTERFACE BUSY FOR OVER 2 MINUTES
See message CA-7.601 for reason.
L3 - LIB** INVALID FAIR RESULT AREA - R15=nnnnnnnn
L4 - LIB** OPN - OPEN UNSUCCESSFUL - RES=bbbbbb
L5 - LIB** MOD - ERROR DURING MEMBER SEARCH - RES=bbbbbb
L6 - LIB** MOD - MEMBER NOT FOUND - RES=bbbbbb
L7 - LIB** REC - READ ERROR - RES=bbbbbb
L8 - LIB** REC - IMBEDDED INCLUDE NOT FOUND - RES=bbbbbb
L9 - LIB** CA-LIBRARIAN: DATE CONVERT ERROR - DATE=00yydddF
LA - LIB** CA-LIBRARIAN: SASSDCON LOAD ERROR - R0=nnnnnnnn
LB - LIB** CA-LIBRARIAN: MCD CODE ERROR - RES=bbbbbb-c
P1 - PAN**nnn PAM HAS NOT BEEN LINKED WITH SASSPANV
P2 - PAN**nnn CA-PANVALET INTERFACE BUSY FOR OVER 2 MINUTES
See message CA-7.601 for reason.
P3 - PAN**nnn OPEN UNSUCCESSFUL FOR PAN LIBRARY
P4 - PAN**nnn NAME NOT ALPHANUMERIC
P5 - PAN**nnn IMBEDDED INCLUDE MEMBER NOT FOUND
P6 - PAN**nnn MEMBER NOT FOUND IN PAN LIBRARY
P7 - PAN**nnn CA-PANVALET FILE READ ERROR
User Response: The following list shows corrective action for the messages keyed to the return
code shown in the previous list for non CA-Librarian or CA-Panvalet files. If the problem persists,
08 Supply a volume serial number for the request or catalog the data set.
0C Verify that the data set is on the volume requested. Specify the correct volume if in error.
10 Data set organization must be PS or PO. If PDS, the member name must be provided.
14 Either BLKSIZE=0 or KEYLEN=0 or RECFM not = F or LRECL not = 80.
18 No //U7volser DD statement exists for the volume where the data set resides. Supply a
//U7volser DD statement in the CA-7 execution JCL. The ALLOC command may be issued to
make the volume available.
1C Provide a valid member name.
20 Try again. If problem persists, contact your installation's CA-7 specialist for assistance.

7.3 SMxx Messages
SM50-14 –SM50-14
24 This update would require a WTOR reply from the system operator's console which would put
CA-7 in a hard wait; that is, no terminal processing, job scheduling, job submittal, and so forth,
until the operator responded. Updates to such a data set are not allowed from CA-7. The
update must be made from outside of CA-7 by using TSO, batch, and so forth, so as not to
impede production scheduling.
28 1) This request has violated User Security as defined in the module referenced by the USER
keyword of the SECURITY statement in the CA-7 initialization file. Use a different operator ID
at logon time or change the USER ID Security module.
2) CA-7 does not have access to the JCL data set. This can occur using external security for
data sets if CA-7 does not have authorized access to the data set.
2C Use REPL function instead of SAVE. If returning from the Editor, use SR instead of SS.
30 Either use a different NEWNAME for the RENAME function or delete the existing NEWNAME
member before doing the RENAME.
34 Check for sufficient directory space. Probably will require reallocating and copying the data set.
38 Try compressing the data set. It may require a reallocation and copy. CA-7 will not write on
the last track of any extent in the data set. If an attempt is made by CA-7 to do so, the
SAVE/REPL is terminated with this code.
3C Similar to return code 24. This request is rejected to prevent CA-7 from going into a hard wait
until an operator responds to the WTOR for the date override. This update must be made
outside of CA-7 through TSO, batch, and so forth, so as not to impede production scheduling.
40 Contact your installation's CA-7 specialist for assistance.
44 The necessary programs to interface with CA-7 are not available. Verify that the following
modules are in a CA-7 load library. If one or more modules are missing, contact your installa-
SASS6CPY
SASS6DEL
SASS6MOD
SASS6RNM
50 SASSSM5C detected an error. Values of x are:
3 - SNOTE failure.
4 - An attempt was made to write more data than the calculated allocation.
54 Wait and try again. If problem persists, contact your installation's CA-7 specialist for assistance.
58 Specify a ddname which exists in the execution JCL for CA-7. Check spelling and try again.
5C Dynamic allocation failed.
If xxxxxxxx=00000004, then:

7.3 SMxx Messages
SM50-14 –SM50-14
yyyyyyyy=020C0000
indicates a request for exclusive use of a shared data set failed. If this is a JCL data
set, try using the DYN=2 option on the appropriate JCL statement in the CA-7
yyyyyyyy=02100000
indicates that the requested data set is unavailable to CA-7 because another job has
exclusive use of the data set; for instance, another job has the data set allocated
DISP=OLD.
yyyyyyyy=02180000
indicates that the specified volume could not be mounted.
yyyyyyyy=17080002
indicates that the data set is not cataloged.
For other values of yyyyyyyy please refer to the IBM Manual MVS/SPL Job Management
(GC28-1303).
If xxxxxxxx=00000008,
then CA-7 is not running in an MVS environment and dynamic allocation is una-
vailable.
If xxxxxxxx=0000000C,
then a dynamic allocation internal error was detected. If the error persists, contact
then a DD statement for the data set was detected in CA-7's JCL. This DD state-
ment should be removed.
then the member is currently in use. Wait a few minutes and attempt the command
again.
then the data set is currently in use. Wait a few minutes and attempt the command
again.
60 Abend condition detected. xxx indicates the abend code while yy is the reason code. If
xxx=213 and yy=30, another task is updating the file; try again. If xxx=913, CA-7 may not be
authorized to access the data set; check with your security administrator. For any other abend
codes, refer to IBM manual GC38-1008 for further details.
For CA-Librarian or CA-Panvalet files, the following list shows the corrective action for the mes-
sages keyed to the pseudo code shown in the list under Action.

7.3 SMxx Messages
SM50-14 –SM50-14
L1 See CA-7 Systems Programmer Guide for instructions on installing the CA-Librarian interface.
L2 See message CA-7.601 for action.
L3 If this message persists, contact your installation's CA-7 specialist for assistance.
L4 For explanations of bbbbbb, see the CA-Librarian File Access Interface Routines manual for the
first six bytes of FAIROPN result area.
first six bytes of FAIRMOD result area.
L6 The member could not be found on the CA-Librarian file. Check the spelling of the member
and retry. If the error persists, contact your CA-7 specialist for assistance.
first six bytes of FAIRREC result area.
L8 The member on the -INC statement could not be found. For explanations of bbbbbb, see the
CA-Librarian File Access Interface Routines manual for the first six bytes of FAIRREC result
area.
L9 An invalid date was passed to the date conversion module. yy is the year, and ddd is day of the
year (this should be the current Julian date). If the date is not in the format indicated or if the
problem persists, contact your CA-7 specialist for assistance.
LA nnnnnnnn is the return code from the SLOAD macro. Make sure the module exists in the CA-7
load library. If it does, verify that the module is defined to CA-7 by an APPLCTN statement in
the initialization file or in the SASSPROG module.
LB For explanations of bbbbbb, see the CA-Librarian File Access Interface Routines manual for the
first six bytes of FAIROPN result area. For an explanation of c, see the CA-Librarian Software
Lock Facility for the FAIROPN result area that is for an MCD code.
*LIBR* OPN UNSUCCESSFUL
Check for a U7VOLVER DD in CA-7's PROC. Use the UT.11 screen or the ALLOC command
to allocate the volume if it is not in CA-7's PROC.
P1 See CA-7 Systems Programmer Guide for instructions on installing the CA-Panvalet interface.
P2 See message CA-7.601 for action.
P3 nnn is the return code from the POPEN routine in PAM. See the CA-Panvalet System Manage-
ment Manual for further explanation.
P4 nnn is the return code from the PREAD routine in PAM. Check the spelling of the member and
retry. See the CA-Panvalet System Management Manual for further explanation.
P5 nnn is the return code from the PREAD routine in PAM. The member on the ++INCLUDE
statement could not be found. See the CA-Panvalet System Management Manual for further
explanation.
P6 nnn is the return code from the PREAD routine in PAM. Check the spelling of the member and
retry. See the CA-Panvalet System Management Manual for further explanation.
P7 nnn is the return code from the POPEN routine in PAM. See the CA-Panvalet System Manage-
ment Manual for further explanation.

7.3 SMxx Messages
SM50-15 –SM50-22
The above Px errors may also be produced if the security has not been properly set up to allow CA-7
USERID access to the CA-Panvalet library. Refer to the appropriate security documentation for
additional information about security requirements for accessing CA-Panvalet libraries.
SM50-15 NO SUBMIT---EOD ON FIRST READ

Explanation: The member or sequential data set was empty.
User Response: Verify your input parameters. If in error, correct and retry.
SM50-16 INTERNAL READER BUSY--WAIT AND TRY AGAIN

Explanation: Someone at another terminal has also issued a SUBMIT command.
User Response: Wait 10 seconds and try again. If problem persists, contact your installation's
SM50-17 INTERNAL READER NOT AVAILABLE

Explanation: A //UCC7IRDR DD statement does not exist in the CA-7 execution JCL.
User Response: Add the proper DD statement so it will be available the next time CA-7 is started.
SM50-18 I/O ERROR ON INTERNAL READER

Explanation: An I/O error was detected while writing to the internal reader.
SM50-19 ERROR UPDATING JOB DS FOR JOB xxxxxxxx

JOB WAS RETRIEVED FROM JCL OVERRIDE LIB
Explanation: A delete function was done for a member from the override library and there was a
problem accessing the job information to turn off the USE-OVERRIDE field. Or, if external security
is used to insert USERIDs and a RUN function was entered, there was a problem accessing the job
information to find a USERID for job submission.
User Response: Try listing the job (using the LJOB command or LIST function from the DB.1
screen). If the problem persists, you may need to delete and readd the job.
SM50-22 SUBMIT DENIED BASED ON USERID IN JCL

Explanation: An attempt was made to RUN/RUNH a job for execution from the CA-7 JCL Library
Maintenance panel with the JCL containing a USERID which the requester is not authorized to
submit.
User Response: If security access should be allowed, contact your local CA-7 Security Adminis-
trator to authorize the user to submit for the USERID specified in the JCL.

7.3 SMxx Messages
SM50-23 –SM61-01
SM50-23 REPLACE DENIED BASED ON USERID IN JCL

Explanation: An attempt was made to replace JCL for a job which contained a USERID which the
user was not authorized to access.
trator to authorize the user to access the USERID which exists in the JCL.
SM50-24 CONFLICT IN JCLID AND JCLLIB FIELDS

SM60-00 SPECIFY OPTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Explanation: This is the prompt used to request selection of a predecessor/successor type. If an
error is made in this selection, you will again be requested to select a type.



SM61-00 xxxxxxxx FUNCTION SUCCESSFUL FOR NWnnnnnn

Explanation: The requested function completed successfully. The network member is also indi-
cated in the message.

Explanation: An error condition was detected by the program. If nnnn=0000, the Job data set may
be out of space.
User Response: If nnnn=0000, check the system console for error messages and if the out-of-space
condition is indicated, increase the size of the failing data set. Otherwise, contact your installation's

7.3 SMxx Messages
SM61-02 –SM61-07

Explanation: The field identified in the message was not found.
User Response: Correct the specification and retry.
Note: For a connected job or DSN, SCHIDs must match. For a network, SUBID and SCHID must
also match. These values may be determined by LJOB,JOB=jobname,LIST=RQMT. If they
are wrong, correct and retry.

had the error.
1. Back up database using SASSBK00.

Explanation: Both the DSN and DSNBR were input but they did not agree.
User Response: Correct or delete one specification and retry. Both parameters are not required.

SM61-06 BAD RETURN FROM MODULE xxxxxxxx, RC=hhhh

(FULL INDEX BLK, PRED NOT ADDED BUT UPD GOOD)
Explanation: An error was returned from module xxxxxxxx. The return code is identified by hhhh.
If the message in parentheses appears, either the Index data set is out of space or the 255 limit has
been reached for a PRED entry. Since the index entry is only used for listing references, the job
requirement update will be completed.
User Response: If the message in parentheses appears, try backing up and reloading the database.
You may want to increase the space for the Index data set. After reloading, try executing the RQMT
command to rebuild the index entries for job requirements.
If the message in parentheses did not appear, note the return code and check the system console for
error messages. Then contact your installation's CA-7 specialist for assistance.
SM61-07 REQUIREMENT ALREADY EXISTS

Explanation: An A (add) option was entered, but the requirement already exists in the CA-7 data-
base.
User Response: Use the U (update) option to change existing requirement information if applicable.

7.3 SMxx Messages
SM61-08 –SM70-00

Explanation: An attempt was made to alter or add a requirement to a job that is not accessible due
to UID security.
User Response: If you need to change an existing job requirement or add a new one, contact your


User Response: Correct the input and retry. If a user requirement is being added through an
external communicator, be sure that there is not a parenthesis, comma, or an apostrophe in the input.
SM61-13 NETWORK ALREADY USED BY JOB 255 TIMES

Explanation: The network is already connected to the job 255 times. This is the limit.
User Response: Consider adding a functionally identical network under another network name.
SM61-14 CANNOT HAVE RQMT FOR SCHID OF ZERO AND NON-ZERO

Explanation: An attempt has been made to establish a connection for a particular SCHID, when it
has already been established for all SCHIDs (zero), or vice versa. This is clearly a contradiction.
User Response: Verify that the existing connection is correct. If not, disconnect existing require-
ment then reenter the request that failed.
SM61-15 CONFLICT IN JOBNAME SPECIFICATION

Explanation: An attempt was made to delete a job requirement when the definition was for a nega-
tive requirement (or vice versa).
User Response: Correct the command and try it again.
SM70-00 ENTER OPTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

Explanation: This is the prompt used to request selection of a schedule type online. If an error is
made in the selection, this message will be reissued.
SM70-00 ENTER SCHEDULE TYPE

Explanation: This is the prompt used to request the schedule type in batch mode.
User Response: The next command should be JOB, INWK, ONWK, or TRGR.

7.3 SMxx Messages
SM70-05 –SM71-00

Explanation: The schedule type was incorrectly specified.
User Response: Correct the command and rerun batch input stream.




Explanation: The requested function completed successfully. The schedule member is identified.

SCHEDULE MUST BE RESOLVED
Explanation: The SAVE or REPL function for an input network or job schedule completed suc-
cessfully. Schedule resolution must be run against this schedule before it becomes effective.
User Response: When desirable, run schedule resolution (RESOLV) against this schedule.

7.3 SMxx Messages
SM71-01 –SM71-05

Explanation: The following explains the various situations:
1. If xx=67, nnnn=0004, and the error occurs as a result of adding or saving schedules, then the
probable cause is the absence of the ZERO member in the Dataset data set. This can occur if
the Dataset data set was reinitialized after the original installation of CA-7.
2. If xx=B7, nnnn=0001, and the error occurs as a result of fetching a schedule member with a
MEMBER NOT FOUND message, then this may relate to the absence of the ZERO member as
described above (xx=67, nnnn=0004).
3. If nnnn=0000, the Dataset data set may be out of space.
4. If xx=J7, nnnn=0A62, check that the Dataset data set has available space.
User Response: Use SASSBK00 to back up and reload the database. Check for the existence of
the ZERO member in the Dataset data set using DUMP,DSNBR=SJ0 (SI0, SO0). If the Dataset data
set has recently been reinitialized in error, do a restore of the database (Job, Dataset and Index data
set) to the most current, correct copies. If no backup exists, contact your installation's CA-7 spe-
cialist.

Explanation: The identified member was not found in the CA-7 database.

had the error.
SM71-04 CONFLICT IN STYPE AND NETWORK

Explanation: An attempt was made to reference an output network (SO type) while in INWK mode
(SI type) or vice versa.
User Response: Check for correct network specification. If in error, correct and retry. Otherwise,
transfer to the proper mode by entering the SCHD function and making the appropriate selection.


7.3 SMxx Messages
SM71-07 –SM72-00
SM71-07 SCHDMBR ALREADY EXISTS

Explanation: A SAVE function was entered, but the schedule member already exists in the CA-7
database.
User Response: Use the REPL function to change an existing schedule member if desired.

Explanation: An attempt was made to alter or add schedule information for a job that is not acces-
sible due to UID security.
User Response: If you need to change an existing schedule or add a new one, contact your security
administrator.


SM71-13 NO SAVE -- SCHID COUNT ZERO

Explanation: An attempt was made to SAVE or REPL a schedule but no SCHID data is available.
User Response: Use FETCH or schedule edit (SCHD EDIT) to build SCHIDs before the SAVE or
REPL is attempted.
SM71-14 NO SAVE -- STATION COUNT CONFLICT

Explanation: The currently available schedule data contains schedules for either more or less
stations than the number defined for the specified network.
User Response: Verify that the station specification is correct. If in error, correct and retry. Other-
wise, schedule edit (SCHD EDIT) must be used (specifying the correct network) to construct a
proper schedule.



7.3 SMxx Messages
SM72-00 –SM72-14
SM72-00 LIST FUNCTION SUCCESSFUL,

USE '/PAGE+1' COMMAND OR PFK EQUIVALENT FOR NEXT SCHID.
Explanation: The LIST function completed successfully. All SCHIDs may be reviewed by paging
through the output. Any SCHID may be updated by changing the function to REPL and updating
various fields on the appropriate screen.

Explanation: This indicates an unusual condition detected by the program.
SM72-02 SCHID NOT FOUND

Explanation: The requested schedule ID was not found.

User Response: Correct the appropriate data fields and retry. It may be necessary to reference the
CA-7 Database Maintenance Guide for correct syntax.
SM72-07 SCHID ALREADY EXISTS

Explanation: An ADD function was entered, but the SCHID already exists for this schedule
member.
User Response: Either use the REPL function to change the existing SCHID information or use a
different SCHID number.

SM72-13 ID-COUNT IS ZERO

Explanation: A LIST function was requested but there are currently no SCHIDs to list.
SM72-14 DEADLINE TIME PRECEDES PREVIOUS STATION DOTM

Explanation: The deadline time (due-out minus lead-time) of station n occurs before the DOTM of
station n-1. This is an erroneous condition.
User Response: Change the input to correct this situation and reenter. It is necessary to specify
DODY if processing extends past midnight.

7.3 SMxx Messages
SM72-15 –SM75-01
SM72-15 SCHID CONTAINS NO SCHEDULE ELEMENTS

Explanation: An attempt was made to ADD or REPL a SCHID but no processing days have been
specified.
User Response: Correct the input and reenter.
SM72-16 SCHEDULE TYPE INDICATOR MUST BE 'X' OR 'Y'

Explanation: A DAILY, WEEKLY, and so on, cycle was indicated with a character other than X
or Y.
SM72-17 TOO MANY SCHEDULE ELEMENTS -- MAX IS nn

Explanation: A limited number of internal schedule elements (ISEs) may apply to a single schedule
ID (SCHID). This maximum number is indicated in the message (nn). The formulas for calculating
ISEs are as follows:
1. If DAILY=Y, add 1.
2. If WEEKLY=Y, add 1 for each day of the week selected.
3. If MONTHLY=Y, add 1 for each week and add 1 for each RDAY.
4. If ANNUAL=Y, add 1 for each day.
5. If SYMETRIC=Y, add 1.
The total obtained cannot be greater than the maximum indicated.
User Response: Determine if any ISEs may be eliminated by defining the schedule differently. It
may be necessary to split this specification into two different SCHIDs.


ENTER INPUT FOR NEXT REQUEST


7.3 SMxx Messages
SM75-02 –SM75-07

Explanation: The job, DSN, or trigger definition specified was not found in the CA-7 database.
SM75-03 OUT OF SPACE ON DATABASE

Explanation: Not enough room in the IDS to contain the trigger definitions.
User Response: Need to reorganize the IDS. The size may need to be increased also.
SM75-04 CONFLICT IN NAME AND DSNBR

Explanation: Both DSN and DSNBR or NWK and DSNBR were input but do not agree with IDS
data.
User Response: Correct or delete one specification (both are not required) and retry.

SM75-06 ERROR FROM MODULE xxxxxxxx, RC=hhhh

(FULL INDEX BLK, DATA NOT ADDED FOR y...y)
Explanation: An error was returned from module xxxxxxxx. The return code is identified by hhhh.
If the message in parentheses appears, either the Index data set is out of space or the 255 entry limit
has been reached for a y...y entry.
User Response: If the second line of the message in parentheses appears, try backing up and
reloading the database. You may want to increase the space for the Index data set. After reloading,
try the entry that failed. If the same failure recurs, you have reached the limit of entries possible for
the indicated entry y...y and may not add any more.
If the message in parentheses did not appear, note the return code and y...y values. It is possible that
the job is being triggered by more than 255 different job/data set/network/SCHID combinations. In
this case there is no problem. The actual triggers are added, but the LJOB with LIST=TRIG will
only report the first 255.
SM75-07 TRIGGER ALREADY EXISTS

Explanation: An A (add) option was entered, but exactly the same trigger entry exists in the data-
base.
User Response: Use the U (update) option to change an existing trigger if applicable.

7.3 SMxx Messages
SM75-08 –SM75-16

Explanation: An attempt was made to alter or add a job trigger for a job that is not accessible due
to UID security.
User Response: If you need to change an existing job trigger or add a new one, contact your


Explanation: Input received was not recognized by the program.
SM75-11 UPDATE FINISHED BUT WITH EXCEPTIONS AS SHOWN

Explanation: The updating of job triggers has occurred excluding those entries that have comments
in the EXCEPTIONS column. If the message indicates ERROR FROM: SASSSM6D, there are
probably already 255 trigger definitions for the job. See the Trigger Scheduling Screens topic in
Chapter 3 of the CA-7 Database Maintenance Guide for more information.
User Response: Review and correct the reason(s) for the EXCEPTIONS and reenter.
SM75-14 NO TRIGGERS DEFINED

Explanation: No triggers are defined for the requested element.
SM75-14 NO TRIGGERED ENTRY FOUND FOR xxxxxxxx

Explanation: No trigger information currently exists for the indicated value.
User Response: Verify input. If in error, correct and retry.
SM75-15 TRGD-JOB AND SCHID COMBINATION NOT FOUND

Explanation: The TRGD-JOB and SCHID combination do not currently exist for the specified job
or DSN.
User Response: Verify input. If in error, correct and retry.
SM75-16 xxxxxxxx GREATER THAN MAXIMUM ALLOWED

Explanation: One of the time indicators in the input data is invalid.
User Response: Determine which field is in error. Correct and retry.

7.3 SMxx Messages
SM75-17 –SM80-01
SM75-17 SCHID 0 ALREADY EXISTS

Explanation: An A (add) option was entered for a job that is already triggered by SCHID 0. You
cannot add a SCHID 0 and a specific SCHID for the same triggered job.
User Response: If the job should be triggered by only specific SCHIDs, delete the entry for SCHID
of 0 and add the specific SCHIDs.
SM75-17 CANNOT TRIGGER JOB FOR SCHID OF ZERO AND NON-ZERO

Explanation: An attempt has been made to establish a job trigger based on a particular SCHID,
when it has already been established for all SCHIDs (zero), or vice versa. This is clearly a contra-
diction.
User Response: Verify that the existing relationship is correct. If not, delete it and reenter the
command.
SM75-18 DUE-OUT TIME AND QUEUE TIME CONFLICT

Explanation: Either due-out time or queue time must be specified, but not both.
User Response: Delete one of the specifications and retry.
SM75-19 INPUT NETWORK MUST BE SPECIFIED

Explanation: An output network cannot trigger a job.
User Response: Specify an input network.



Explanation: The requested function completed successfully. The schedule member is identified.


7.3 SMxx Messages
SM80-02 –SM80-17

Explanation: The identified member was not found in the CA-7 database.
SM80-04 SPECIFY EITHER JOB OR NETWORK -- NOT BOTH

Explanation: Either JOB or NETWORK may be specified, but not both.
User Response: Delete one specification and reenter.

User Response: Correct the value in error and retry.

Explanation: An attempt was made to alter a job's schedule that is not accessible due to UID
security.
User Response: If you need to modify the job's schedule, contact your security administrator.

SM80-14 NETWORK NOT INPUT TYPE

Explanation: Output network schedules are based on the job(s) to which the networks are con-
nected. Therefore, SCHDMOD does not apply.
SM80-15 JOB/NETWORK HAS NO SCHEDULE

Explanation: The requested job or network does not have an associated schedule.
User Response: Schedule must be added and resolved before it may be modified.
SM80-16 SCHEDULE HAS NOT BEEN RESOLVED

Explanation: A schedule must be successfully resolved before it may be modified.
User Response: Resolve the schedule and then make the desired modifications.
SM80-17 ENTIRE DAY MASK MUST BE 0'S AND 1'S

Explanation: An attempt was made to update a schedule but unrecognizable data appeared in the
day mask.

7.3 SMxx Messages
SM85-00 –SM85-07
SM85-00 cccccccc ffffffff SUCCESSFUL

Explanation: The requested function (ffffffff) for calendar cccccccc was completed successfully.
SM85-00 cccccccc ffffffff SUCCESSFUL RESOLVE MAY BE REQUIRED

Explanation: The requested function (ffffffff) for calendar cccccccc was completed successfully.
Since the function affected a standard CA-7 base calendar, a RESOLVE command may be needed in
order to update schedules which use this calendar.
User Response: If needed, RESOLVE any affected schedules.
SM85-01 CALENDAR NOT FOUND

Explanation: The requested calendar was not found.
User Response: Check the calendar name and retry the function.
SM85-02 INTERNAL DATE CONVERSION ERROR

Explanation: An error occurred in the internal processing of the calendar data.
User Response: Check the data specified for the calendar. If it is correct and the problem persists,
contact your CA-7 specialist.

Explanation: An error occurred processing the data for field xxxxxxxx.
User Response: Correct the field specified on the message and retry the function.
SM85-06 INVALID DAY SPECIFIED IN CALENDAR DAYS: DAY xxx

Explanation: An error occurred processing the data for the days of the months. The day in error is
described as the relative day of the year (xxx). For example, DAY 032 represents February 1st.
User Response: The most common cause for this message is specifying too many or too few days
for a particular month. For example, specifying 31 days in September would cause this error.
Correct the data and retry the function.
SM85-07 OPTION NOT VALID WITHOUT CALENDAR LIBRARY

Explanation: A REFRESH function was attempted, but there is no CA-7 Calendar PDS definition
in the CA-7 initialization file.
User Response: If you wish to use online calendars, refer to the CA-7 Systems Programmer Guide
for instructions on allocating and identifying the Calendar PDS.

7.3 SMxx Messages
SM85-07 –SM85-09
SM85-07 PREMATURE EOF REACHED ON SGETPDS

Explanation: An attempt was made to read a calendar from the CA-7 Calendar PDS, however, the
end of data was reached before the full calendar was read.
User Response: Check the CA-7 Calendar PDS to see if it has been corrupted. Also, check the
CA-7 initialization file to ensure that the CALENDAR statement specifies the correct data set name.
Contact your CA-7 specialist for further help.
SM85-07 LOAD FAILED

Explanation: The base calendar with a standard CA-7 calendar name which was the subject of a
LIST or REFRFESH function was not found in either the CA-7 Calendar PDS or the load libraries
available to the CA-7 address space.
User Response: Check the name of the calendar to ensure it is correct. If this is a batch calendar,
check to ensure it resides in a load library connected to the CA-7 address space and retry the func-
tion.
SM85-07 MEMBER NOT FOUND ON CALENDAR LIBRARY

Explanation: The calendar with a non-standard calendar name which was the subject of a LIST or
REFRFESH function was not found in the CA-7 Calendar PDS.
User Response: Check the name of the calendar to ensure it is correct and retry the function.
SM85-07 REFRESH FAILED

Explanation: A REFRESH function was attempted on a member with a nonstandard calendar name.
User Response: Load module versions of calendars must have a standard name format
(SCALyyxx). Ensure the calendar name was entered correctly and retry the command.
SM85-07 ACCESS TO CALENDAR xxxxxxxx DENIED BY EXTERNAL SECURITY

Explanation: The external security package denied an attempt to access CA-7 calendar xxxxxxxx.
This message can only occur if external security for calendar access has been enabled in the CA-7
User Response: Check with your external security administrator to define the proper access level.
SM85-07 text
Explanation: Check the SM50-14 message for a comparison of the text value.
User Response: Take the action as indicated for the SM50-14 message.


7.3 SMxx Messages
SM85-10 –SM90-05
SM85-10 INVALID DAY SPECIFIED FOR MONTH BEG/END : mm/dd

Explanation: An invalid date was entered for the beginning or ending date mm/dd.
User Response: Correct the field specified on the message and retry the function.
SM85-11 BEG/END DAYS NOT IN ASCENDING ORDER : mm/dd1 mm/dd2

Explanation: The beginning and ending dates are valid dates, however, mm/dd1 is a higher date
than mm/dd2.
User Response: Correct the field(s) specified on the message so that the beginning and ending dates
are in ascending sequence and retry the function.
SM85-12 SPECIFIED MEMBER IS NOT A VALID CA-7 CALENDAR

Explanation: A member was found in the calendar PDS matching the calendar name specified on
the screen. However, that member is not in the proper format for a CA-7 calendar.
User Response: Check to ensure that the name specified is correct. If it is correct and the problem
persists, contact your CA-7 specialist.


SM90-00 xxxxxxxx FUNCTION SUCCESSFUL FOR JOB xxxxxxxx

Explanation: The requested function completed successfully. The associated job name is printed.

SM90-02 JOB NOT FOUND

Explanation: The requested job was not found in the appropriate queues.


7.3 SMxx Messages
SM90-08 –SM90-17

Explanation: An attempt was made to access a job's QJCL that is not accessible due to UID secu-
rity.
User Response: If you need to edit the QJCL for this job, contact your security administrator.



Explanation: An attempt was made to replace the JCL for a Request queue job but the Active Area
contains no data.
User Response: Verify that the Active Area contains the desired JCL and retry.
SM90-15 SKELETON RECORD FOUND

Explanation: Schedule Scan has not completed initial job processing.
User Response: Wait a few minutes before trying the JCL request again. If problem persists for an
extended period, look for messages concerning this job on the Master Station. This message also
may be produced for jobs whose status is RETRY on an LQ display. If unable to resolve the
problem, contact your installation's CA-7 specialist for assistance.
SM90-16 NO SAVE -- JOB COMPLETED NORMALLY

Explanation: The requested job already completed successfully.
SM90-17 UPDATE DENIED - SUBMIT CHECK FAILED

Explanation: An attempt was made to replace JCL for a Request queue job. The JCL contained a
USERID; however, the user trying to update is not authorized to submit for that USERID.
User Response: If security access needs to be allowed, contact your local CA-7 Security Adminis-
trator or log on with an authorized USERID and update the JCL.

7.3 SMxx Messages
SM90-18 –SM90-19
SM90-18 QJCL FE/FETCH NOT VALID FOR 7UNI JOBS WITHOUT MIXED CASE SUPPORT
Explanation: The QJCL screen will not allow a FE (or FETCH) function for jobs that are set as
7UNI jobs unless CA-7 mixed case editor support has been enabled.
User Response: If the JCL must be modified, then the job could be canceled, the JCL changed
outside of CA-7, and the DEMAND command used to bring the job in again.
SM90-19 RUN LOG DATA NOT AVAILABLE THROUGH EDIT

Explanation: The QJCL screen will not allow a FPE function for CA-7 Run Log records.
User Response: Use the LRLOG command to list information from the CA-7 Run Log.

7.4 SPOx Messages
SPOA-00 –SPOA-05
7.4 SPOx Messages
SPOA-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

(JOB xxxxxxxx HAS BEEN POSTED FOR SUBMISSION)
(xxxx EXTERNAL INPUTS FORCED)
(xxxx INTERNAL INPUTS FORCED)
Explanation: The input request was completed successfully. If JOB was specified, the last three
information lines will be printed.
User Response: Acknowledge the message. It may be necessary to cancel incomplete tasks still in
the Preprocess queue.
SPOA-01 xxxxxxxx - INVALID

Explanation: Keyword xxxxxxxx is invalid. If required, it may have been omitted from the input
request.
SPOA-02 SKELETON RECORD FOUND

Explanation: Schedule Scan is still in the process of building queue records for the requested job.
may be produced for jobs whose status is RETRY on an LQ display. If unable to resolve the
SPOA-03 REQUIREMENTS SCAN INCOMPLETE

Explanation: Schedule Scan (Requirements Scan modules) is still in the process of determining the
job's requirements.
extended period, look for messages concerning this job on the Master Station. If unable to resolve
the problem, contact your installation's CA-7 specialist for assistance.
SPOA-04 JOB HAS ALREADY BEEN SUBMITTED

Explanation: The requested job has already been submitted for execution.
User Response: Verify the job number specified on the input request. If correct, no action is
required; if not, correct and resubmit the command.
SPOA-05 JOB NOT FOUND IN REQ OR RDY QUEUE

Explanation: The job specified on input could not be found in the Request or Ready queue.
User Response: Verify the job name specified on the input request; correct and resubmit the
command if wrong.

7.4 SPOx Messages
SPOA-06 –SPOB-01
SPOA-06 I/O ERROR RC=xxx

Explanation: An I/O error occurred while attempting to access the CA-7 queues.
SPOA-07 JCL SUBMISSION POSTED [(EXPRESS)]

Explanation: JCL submission has been posted as requested. If the EXPRESS=YES option was
specified, the EXPRESS notation is displayed.
SPOA-08 EXPRESS=YES INVALID WITH WLB

Explanation: The SUBMIT command parameter EXPRESS=YES is not valid if Workload Bal-
ancing is being used.
User Response: None. If desired, use the QM.3 (XUPD) screen to update the job's priority instead
of using EXPRESS=YES. To satisfy all requirements for the job, enter the SUBMIT command for
the job eliminating the EXPRESS=YES operand.
SPOB-00 JOB= xxxxxxxx (nnnn) SET FOR RESTART

REQUEST COMPLETED AT hh:mm:ss ON yy.ddd
Explanation: Job xxxxxxxx has been moved from the Ready or Active queue back to the Request
queue and flagged for restart.
User Response: Use restart to reactivate processing for the job.
SPOB-00 JOB= xxxxxxxx SCHD FLAG SET TO yyy

Explanation: A NXTCYC command has been successfully processed and normal scheduling will be
altered as requested with yyy.
SPOB-00 JOB xxxxxxxx(nnnn) - MAINID CHANGED TO yyy

Explanation: A DIRECT command has been successfully processed. The main ID for the job
specified by xxxxxxxx(nnnn) has been changed to redirect submission to the CPU designated by yyy.
SPOB-01 xxxxxxxx - INVALID

Explanation: Keyword xxxxxxxx is invalid for the specified command.

7.4 SPOx Messages
SPOB-02 –SPOB-06
SPOB-02 JOB nnnn NOT FOUND IN READY OR ACTIVE QUEUE

Explanation: An attempt was made to requeue a job to the Request queue. Job nnnn was not
found in the Ready or Active queue.
User Response: Verify that the correct CA-7 job number was specified. If necessary, correct and
SPOB-02 JOB nnnn NOT FOUND IN REQUEST OR READY QUEUE

Explanation: An attempt was made to direct a job to another CPU. Job nnnn was not found in the
Request or Ready queue.
User Response: Verify that the correct CA-7 job number was specified. If necessary, correct and
SPOB-02 JOB xxxxxxxx NOT FOUND IN JOB DATA SET

Explanation: The job name specified on a NXTCYC command was not found in the Job data set.
User Response: Verify the job name specified; correct and resubmit the command.
SPOB-03 JOB xxxxxxxx HAS ALREADY BEEN SUBMITTED

Explanation: An attempt was made to direct job xxx...x to another CPU. The job has already been
submitted and the request cannot be satisfied.
SPOB-04 QUEUE I/O ERROR, RC=nnn

Explanation: An I/O error occurred while attempting to access the queue.
User Response: Resubmit the command. If the problem persists, contact your installation's CA-7
SPOB-05 JOB MEETING SELECTION CRITERIA NOT FOUND

Explanation: An attempt was made to locate a job using a combination of parameters that could
not be satisfied.
User Response: Correct any parameters that require correction and retry.
SPOB-06 UNABLE TO REQUEUE, ARF EVENTS PENDING

Explanation: This message is issued when a REQUEUE is attempted while ARF is controlling
recovery for a job.
If the REQUEUE must be issued prior to the completion of ARF recovery, then the ARFP command
is complete, the REQUEUE may be issued.

7.4 SPOx Messages
SPOB-07 –SPOC-04
SPOB-07 CRITICAL PATH MANAGEMENT SUPPORT NOT ACTIVE.

Explanation: A FLOWD command was issued but the CPM feature is not active.
SPOB-08 NO FLOW RECORDS SELECTED FOR DELETION

Explanation: A FLOWD command was issued but no active flows matched the selection criteria
specified.
User Response: Check the spelling of the flow name argument and reissue the command.
SPOB-09 FLOW RECORD(S) DELETED : nnnn

Explanation: A FLOWD command was issued and one or more active CPM flow records were
deleted. The value nnnn indicates the number of flows deleted.
SPOB-10 VSAM ERROR : FUNC=ff RC=rrrr CC=cccc KEY=kkkkkkkk

Explanation: A FLOWD command was issued and a VSAM error was encountered attempting to
delete an active CPU flow record. The return code (rrrr) condition code (cccc) and record key
(kkkk...) are displayed.
SPOC-02 REF - INVALID.

Explanation: One of the following conditions exists:
1. The REF parameter was omitted.
2. A non-numeric reference number was entered.
3. More than 10 reference numbers were specified on one command.
4. A job number of 0 was specified.
5. A station number of 0 was specified.
User Response: Correct the error and reenter the command.
SPOC-04 xx INVALID MACRO RETURN CODE= xxxxxxxx

Explanation: An unexpected error condition was detected in the SASSSPOC module. The location
in the program and the hex value of the return code are given.

7.4 SPOx Messages
SPOD-01 –SPOE-02
SPOD-01 xx INVALID MACRO RETURN CODE=hhhhhhhh

Explanation: An unexpected error condition was returned from a macro call. The location in the
program where the error occurred is indicated by xx; the hex value of Register 15 is indicated by
hhhhhhhh.
SPOD-02 NO QUEUE RECORDS FOUND

Explanation: No entries were found in the CA-7 queue pertaining to a request.
User Response: Verify that the input request was correct. If not, correct the error and reenter the
command.
SPOD-03 REQUIRED INPUT MISSING

Explanation: A required keyword was not found on the input command.
SPOD-04 CONFLICTING INPUT PARAMETERS

Explanation: Mutually exclusive parameters were specified on the input command.
SPOD-05 xxxxxxxx - INVALID

Explanation: Keyword xxxxxxxx was specified incorrectly.
SPOE-00 JOB xxxxxxxx (nnnn) ADDED TO [(PRE/Q)|(POST/Q)]

FOR NETWORK= yyyyyyyy, [SUBID= zzzzzzzz]
REQUEST COMPLETED AT hh:mm:ss ON yyddd
Explanation: The DMDNW function completed successfully.
SPOE-01 xxxxxxxx -- INVALID OR OMITTED

Explanation: Keyword xxxxxxxx is invalid. If required, it may have been omitted from the input
request.
SPOE-02 NETWORK xxxxxxxx NOT FOUND

Explanation: Network xxxxxxxx was not found in the CA-7 database.
User Response: If input is in error, correct and retry.

7.4 SPOx Messages
SPOE-03 –SPOE-14
SPOE-03 NETWORK xxxxxxxx HAS LOCKED SCHEDULE

Explanation: The network's schedule is locked and it cannot be demanded.
User Response: Resolve the schedule and reissue the request.
SPOE-04 NETWORK xxxxxxxx HAS NO SCHEDULE

Explanation: The specified network does not have a schedule.
User Response: A schedule must be added for the network before it can be demanded.
SPOE-05 ERR/EOF ADDING NETWORK=nnnnnnnn TO THE {PREQ|POSTQ} CODE=xx

Explanation: The network station(s) could not be added to the specified queue because of an error
condition indicated by xx. If xx=00, the queue is probably full. If xx is not 00, there is a queue
access error.
User Response: If the queue is full, it must be enlarged or stations must be posted before additional
network stations can be added. It may be necessary to delete some stations if only part of the
network was added.
SPOE-06 UNABLE TO ASSIGN CA-7 NUMBER

Explanation: There are no CA-7 job numbers available to be assigned to the requested network
stations.
User Response: The HIJBNUM parameter on the SCHEDULE statement may be increased or the
network may be demanded after other stations have been posted or jobs have completed and freed
CA-7 job numbers.
SPOE-08 xx INVALID MACRO RETURN CODE yyyyyyyy

Explanation: An unexpected error was detected by the program.
SPOE-09 xx ACTIVE FILE EMPTY OR UNUSABLE. CODE= yyyyyyyy

Explanation: The Active file is probably empty.
User Response: Make sure that the Active file contains the REMIND data. The active file data can
be built using the text editor.
SPOE-10 ERROR TRYING TO CONVERT REMIND DATA. CODE=xx

Explanation: The Active file could not be internally converted.
SPOE-14 NETWORK (nnnn) ENTERED INTO [(PRE)|(POST)] - PROCESS 'Q' FOR nn STATION(S)
Explanation: This message is sent to the Master Station to indicate that a network has been added
to the queue.

7.4 SPOx Messages
SPOE-20 –SPOF-07
SPOE-20 REMIND DATA (RMD#xxxx) ENTERED INTO PRE/Q

Explanation: The REMIND command was successfully processed.
SPOF-00 JOB xxxx ARF REQUIREMENT PURGED

Explanation: The request to purge the ARF requirement completed successfully.
SPOF-01 INVALID KEYWORD

Explanation: An invalid keyword was entered.
SPOF-02 JOB xxxxxxxx NOT FOUND.

Explanation: The specified job name was not found in either the request, ready, or active queue.
SPOF-03 offset ARQM ERROR R15=return-code R1=reason-code R0=information-code

Explanation: An error occurred accessing the ARF queue record for this job.
SPOF-04 QUEUE FILE I/O ERROR, RC=xxx

User Response: Resubmit the command. If the error persists, contact your installation's CA-7 spe-
SPOF-05 NO STORAGE AVAILABLE FOR DUMMY JOB QUEUE RECORD.

Explanation: An error occurred while attempting to acquire storage for a CA-7 job queue record.
SPOF-06 NO ARF QUEUE ELEMENTS FOUND FOR JOB nnnn.

Explanation: No ARF queue element was found for job number nnnn which was the target of an
ARFP command.
User Response: Correct the job number and reissue the command.
SPOF-07 ARFP IS INVALID IN THIS MODE

Explanation: Someone attempted to issue the ARFP command, and the RESTART statement in the
initialization file does not have ARF=YES.
User Response: If you need to issue the ARFP command, use ARF=YES.

7.4 SPOx Messages
SPOR-32 –SPOR-41
SPOR-32 PRSCF UNSUCCESSFUL

RESOURCE : resource-name
NOT USED BY JOB xxxxxxxx
Explanation: This message indicates that the attempted PRSCF command failed because the
resource is not currently used by the job.
User Response: Use the RM.3 and RM.4 screens to confirm that the job is currently "using" the
resource.
SPOR-34 PRSCF UNSUCCESSFUL

DELETE ERROR FOR RESOURCE : resource-name
FOR JOB xxxxxxxx
Explanation: An error has occurred attempting to access the VRM definitions for the indicated job.
SPOR-35 PRSCF SUCCESSFUL

RESOURCE : resource-name
FREED FOR JOB - xxxxxxxx
Explanation: The resource has been freed.

ACTIVATED
Explanation: The CRQ resource has been successfully activated.
SPOR-40 PRSQD UNSUCCESSFUL

NOT FOUND.
Explanation: This message indicates that the attempted PRSQD command failed because the
resource could not be found.
User Response: Make sure the correct resource name is used and retry the command.

ALREADY ACTIVE
Explanation: This message indicates that the resource is already active.

Chapter 8. SPO0 - XTRK
This chapter contains the SPO0 through XTRK messages.
Chapter 8. SPO0 - XTRK 8-1

8.1 SPO0 Through SPO9 Messages
SPO0-00 –SPO0-06
SPO0-00 xxxxxxxx FUNCTION SUCCESSFUL REQUEST COMPLETED AT hh:mm:ss ON yy.ddd.

Explanation: The input request completed successfully.
SPO0-01 UNRECOGNIZABLE KEYWORD FOUND

User Response: Check for a misspelled keyword; correct and resubmit the command.
SPO0-02 xxxxxxxx INVALID OR MISSING

Explanation: Keyword xxxxxxxx is incorrect or is required but was not supplied.
User Response: Correct and resubmit the command. If the keyword is DATE and the SSCAN
command is being used, check to see if you are trying to set the DATE forward without first setting
it to zero.
SPO0-03 REQUIRED KEYWORD MISSING

Explanation: A required keyword has been omitted.
SPO0-04 xxxxxxxx - INVALID

Explanation: Keyword xxxxxxxx is invalid or does not pertain to the request.
SPO0-05 PROGRAM ERROR, WIP=xx

Explanation: A CA-7 program error has occurred. The Where-In-Program (WIP) location of the
error is indicated by xx.
SPO0-06 JOB NOT FOUND IN REQ/Q

Explanation: The job number specified on input was not found in the Request queue.
User Response: Verify that the proper job number was specified; if not, correct and resubmit the
command.

SPO0-07 –SPO1-00
SPO0-07 REQUIREMENTS SCAN INCOMPLETE

Explanation: Requirements Scan is still in the process of determining the job's requirements.
User Response: Wait a few minutes then resubmit the command. If the message persists and no
other pertinent messages can be found on the Master Station, contact your installation's CA-7 spe-
SPO0-08 Q ANALYSIS INCOMPLETE

Explanation: Schedule Scan is still in the process of adding the job to the queue.
User Response: Wait a few minutes and then resubmit the command. If the message persists and
no other pertinent messages can be found on the Master Station, contact your installation's CA-7
SPO0-12 INPUT RECEIVED FROM JOB=xxxxxxxx,STEP=xxxxxxxx ***TRAILER STEP***

Explanation: The message notifies the Master Station that CA-7 has received input from a Trailer
Step.
SPO1-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Explanation: The HOLD or RELEASE function was completed without errors. The action field
will contain one of the following:
HELD - The requested job is being held.
RELEASED - The requested job has been released.
NOT HELD - An attempt was made to release a job not being held.
ALREADY HELD - An attempt was made to hold a job that is already being held.
HELD BY JOB - The job was held on an individual basis; a RELEASE QUEUE will not cause
it to be released.
JOB ALREADY SUBMITTED - The HOLD is ignored for this job because it is already sub-
mitted.
NO STATION IN PROCESS - All workstations in the network that logged in have also logged
out. The network can no longer be held.
RQMTS SCAN REQUIRED - Requirements Scan has not completed determination of the job's
requirements.
Q ANALYSIS INCOMPLETE - Schedule Scan is still in the process of adding entries to the
queue.
User Response: Only the last two messages above require action. In both cases, wait a few
minutes then resubmit the command. If the message persists, contact your installation's CA-7 spe-

SPO1-03 –SPO2-04
SPO1-03 xxxxxxxx INVALID

Explanation: Keyword xxxxxxxx is invalid or missing.

Explanation: A required keyword was not specified on input.
SPO1-05 I/O ERROR, RC = xxxx

Explanation: An I/O error occurred while accessing the queues.
SPO1-06 JOB/STATION NOT FOUND

Explanation: The required job or workstation entry was not found in the queue.
User Response: Verify that the job or workstation number was specified correctly. If not, correct
and resubmit the command.
SPO2-00 xxxxxxxx FUNCTION SUCCESSFUL REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Explanation: The input request has been completed successfully.

Explanation: A keyword required for the function was omitted from the input.

Explanation: Keyword xxxxxxx is invalid or was omitted.
SPO2-03 STATION HAS BEEN PREVIOUSLY LOGGED IN

Explanation: An attempt was made to log in the status of a workstation that has already been
logged in.
User Response: Verify that input parameters were specified correctly. If correct, no action is
SPO2-04 NOT LOGGED OUT OF PREVIOUS STATION

Explanation: An attempt was made to log in a workstation before the preceding workstation had
logged out.
User Response: Check to see why the preceding workstation has not logged out.

SPO2-05 –SPO2-11
SPO2-05 ASSOCIATED JOB HAS NOT COMPLETED NORMALLY

Explanation: An attempt was made to log in a workstation in the Postprocess queue. The job
which produces the work for that workstation has not executed or it abended during execution.
User Response: Verify that the input command was correct. If input is accurate, check the status
of the job; if the command is invalid, correct and resubmit. A log in may be forced by specifying
FORCE=YES.
SPO2-06 STATION HAS NOT BEEN LOGGED IN

Explanation: An attempt was made to log out a workstation before that workstation had logged in.
User Response: Verify that the input command was correct. If it was, the station must first be
logged in before it can be logged out. If not, correct and resubmit the command.
SPO2-07 I/O ERROR, RC=xxx

Explanation: An I/O error was encountered while attempting to access the CA-7 queues.

Explanation: Schedule Scan has not finished building the queue records for the requested job.

Explanation: The requested job or workstation was not found in the Preprocess or Postprocess
queue.
User Response: Verify that the input command was correct. If not, correct and resubmit. If it was,
verify the job/workstation schedules.
SPO2-10 JOB HELD

Explanation: An attempt was made to log out a workstation. The job associated with the work-
station activity has been held in the CA-7 queue. The job must be released before the workstation
can be logged out.
User Response: Determine why the job is being held. If the reason for the hold has been satisfied,
release the job and then log out the workstation.
SPO2-11 STATION ALREADY LOGGED OUT

Explanation: An attempt was made to log out a workstation which has already been logged out.
User Response: Verify that the input was correct. If it was, no action is required. If not, correct

SPO3-00 –SPO3-07
SPO3-00 RESPONSE TO PROMPT ACKNOWLEDGED REQUEST COMPLETED AT hh:mm:ss ON

yy.ddd
Explanation: Response to a prompt has been acknowledged. No further prompting will occur.
SPO3-01 Q FILE I/O ERROR, RC=xxx


Explanation: A required keyword was omitted from the input.

Explanation: Keyword xxxxxxxx is invalid or missing.

Explanation: The requested job or workstation was not found in the specified queue.
User Response: Verify that the input was correct. If not, correct and resubmit the command.

Explanation: Schedule Scan has not completed building the queue records for the requested job.
User Response: Wait a few minutes and then resubmit the command. If problem persists for an

Explanation: Schedule Scan (Requirements Scan modules) has not completed determination of the
requested job's requirements.
User Response: Wait a few minutes before trying the request again. If problem persists for an
SPO3-07 NO PROMPT HAS BEEN RECEIVED

Explanation: An attempt was made to acknowledge a prompt when no prompt was issued.
User Response: Verify that the input was correct. If it was, no action is required. If not, correct

SPO4-00 –SPO4-05
SPO4-00 cccccccc SUCCESSFUL FOR JOB xxxxxxxx (nnnn)

(DSN=x...x)
(DEPJOB=yyyyyyyy)
(NW=wwwwwwww)
(USR=u...u)
REQUEST COMPLETED AT hh:mm:ss ON yy.ddd
Explanation: The input requirements have been satisfied or the job dependency has been added
successfully according to the command indicated by cccccccc.
SPO4-01 xxxxxxxx INVALID OR MISSING

Explanation: Keyword xxxxxxxx is invalid or was not included in the input.

Explanation: Keyword xxxxxxxx is invalid.
SPO4-03 CONFLICTING KEYWORDS SPECIFIED

Explanation: Mutually exclusive keywords were specified on the input request.
SPO4-04 JOB xxxxxxxx NOT FOUND IN REQ/Q

Explanation: The job name or job number specified on the input command was not found in the
request queue.
User Response: Verify the job name or job number; correct and resubmit the command.
SPO4-05 POST UNSUCCESSFUL FOR JOB xxxxxxxx(nnnn)

(DSN= x...x)
(DEPJOB= yyyyyyyy)
(NW=wwwwwwww)
(USR=u...u)
REQUIREMENT NOT FOUND
Explanation: An attempt was made to post the availability of a data set or the completion of a job.
The data set or job dependency indicated is not a requirement for the job being posted.
User Response: Verify the input; correct and resubmit the command if necessary. If it is a user
requirement that you are trying to post, check to be sure that the input does not contain a parenthesis,
comma, or an apostrophe. If it does, an online POST using the QM.2 (XRQ) screen will need to be
done.

SPO4-06 –SPO4-12
SPO4-06 POST UNSUCCESSFUL FOR JOB xxxxxxxx(nnnn)

(DSN= x...x)
(DEPJOB= yyyyyyyy)
(NW=wwwwwwww)
(USR=u...u)
REQUIREMENT ALREADY POSTED
Explanation: The requirement being posted has already been satisfied.
User Response: Verify the input; if necessary, correct and resubmit the command.
SPO4-07 POST UNSUCCESSFUL FOR JOB xxxxxxxx (nnn)

(DSN= x....x)
(DSN IS NOT INTERNAL)
Explanation: INTERNAL=YES was specified when attempting to post the availability of a data set.
The data set specified is not internal.
User Response: Verify the data set name. If correct, resubmit the command omitting
INTERNAL=YES.
SPO4-08 POST UNSUCCESSFUL FOR JOB xxxxxxxx (nnnn)

(DSN= x...x)
(DSN IS NOT EXTERNAL)
Explanation: INTERNAL=YES was not specified when attempting to post the availability of a data
set. The data set specified is internal.
User Response: Verify the data set name. If correct, resubmit the command with
INTERNAL=YES specified.
SPO4-11 I/O ERROR, RC= xxx

Explanation: An I/O error occurred while trying to access the CA-7 queues.
SPO4-12 POST UNSUCCESSFUL

JOB=xxxxxxxx -- MULTIPLE ENTRIES FOUND IN REQ/Q
Explanation: An attempt was made to post a job in the Request queue by job name. No post was
done because multiple entries were found for the job name specified.
User Response: Determine the 4-digit CA-7 job number of the entry to be posted and resubmit the
command using that number to identify the job.

SPO4-15 –SPO5-04
SPO4-15 INVALID ADDRQ/POST - JOB IN xxxxxxxx STATUS

Explanation: An ADDRQ or POST command was issued before all requirements for the job were
attached. The ADDRQ or POST cannot be done until requirements for the job are successfully
attached; that is, the job is not in SKELETON or RQMT-INC status. Where:
xxxxxxxx = SKELETON or RQMT-INC
If xxxxxxxx equals SKELETON, the JCL has not been attached. When xxxxxxxx=SKELETON, the
status on an LQ display may be either SKELETON or RETRY. If xxxxxxxx equals RQMT-INC, the
initial job requirements have not been attached.
User Response: Wait a few minutes, then try the ADDRQ or POST command again. If it still does
not work, check Master Station messages (Browse data set) to determine why the JCL or the require-
ments are not attached. The job may have to be canceled and manually DEMANDed.
SPO5-00 xxxxxxxx FUNCTION SUCCESSFUL REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

SPO5-01 CA-7 IDS AND SYSTEM CATALOG IN AGREEMENT

Explanation: A consolidation of the system catalog and the CA-7 IDS was requested. No action
was taken because the two catalogs were in agreement for the data set specified.
SPO5-02 ERROR IN INPUT DATA

Explanation: An error was detected in the parameter list passed to SASSSCTU.
SPO5-03 IDS INCONSISTENT WITH REQUEST

Explanation: An attempt was made to delete or replace an entry which does not exist in the CA-7
IDS.
User Response: Verify the input request. If necessary, correct and resubmit the command.
SPO5-04 ENTRY IS TOO LARGE FOR EXISTING STRUCTURE

Explanation: The CA-7 IDS contains entries for the three most current versions of a data set. The
entry structure is capable of controlling up to 251 volumes for the three versions and this number
was exceeded by the input request.
User Response: Verify that the input request is correct. If it is, the request cannot be honored due
to the large number of volumes. If not, correct and resubmit the command.

SPO5-05 –SPO6-00
SPO5-05 DSN NOT FOUND IN CA-7 IDS, RC=xxx

Explanation: The data set name specified on input could not be located in the CA-7 IDS. The
return code from the LOCATE is xxx.
User Response: Verify that the data set name in the input request is correct. If it is, contact your
installation's CA-7 specialist for assistance. If not, correct and resubmit the command.
SPO5-06 DSN NOT FOUND IN SYSTEM CATALOG, RC=xxx

Explanation: The data set name specified on the input request could not be located in the system
catalog. The return code from the LOCATE is xxx.
User Response: Verify that the data set name specified in the input request is correct. If it is, it
may be necessary to catalog the data set on the system catalog.
SPO5-07 UPDATE ERROR, RC=xxx

Explanation: An error was encountered when attempting to update the IDS entry for the data set.
The return code from the IDS is xxx.
User Response: Check the return code; it may be necessary to enlarge the CA-7 IDS.
SPO5-08 NOT ENOUGH AVAILABLE MEMORY

Explanation: Not enough core was available to process the input request.
User Response: Resubmit the command. If the error recurs it may be necessary to increase the
region size for CA-7.

Explanation: Keyword xxxxxxxx was invalid or was required but omitted from the input request.
SPO6-00 JOB xxxxxxxx(nnnn) HAS BEEN CANCELLED [AND CMT CLEARED]

[-*WARNING* CMT NOT CLEARED]
Explanation: The request to cancel a CPU job was successful. If noted, the CA-11 CMT was
cleared to prevent erroneous restarts. If a job is canceled after being submitted, but is still in the
Active or Ready queue, the CMT will not be cleared and this may need to be done manually.
User Response: If the job being canceled was in the Active queue, or had been submitted and was
in the Ready queue, then an OS cancel will also be required to terminate execution.
SPO6-00 JOB CANCELLED FROM PRE-PROCESS 'Q' JOB=xxxxxxxx, NW=yyyyyyyy

Explanation: The request to cancel preprocess work completed successfully.

SPO6-00 –SPO6-07
SPO6-00 RECORDS DELETED FROM POST-PROCESS 'Q', FOR JOB= xxxxxxxx(nnnn) [,NW=
yyyyyyyy] [,SUBID= zzzzzzzz]
Explanation: The request to cancel postprocess work completed successfully.
SPO6-02 INVALID OR OMITTED VALUE FOR: xxxxxxxx

Explanation: Keyword xxxxxxxx is invalid or is required but was omitted from the input request.
SPO6-03 NO QUEUE RECORDS FOUND

Explanation: No records were found in the CA-7 queues for the job name specified on the input
request.
User Response: Verify that the job name was specified correctly. If it was, no action is required
since the job has already been canceled. If not, correct and resubmit the command.
SPO6-04 JOB IS IN 'SKELETON' STATUS

Explanation: Either Schedule Scan is still in the process of adding the job to the CA-7 queue or the
job had some type of error when it entered the queue.
User Response: If Schedule Scan is still active, wait a few minutes before trying the request again.
If problem persists for an extended period, look for messages concerning this job on the Master
Station. If Schedule Scan is not still active, reenter with FORCE=YES. This message also may be
produced for jobs with a status of RETRY on an LQ display. If unable to resolve the problem,

Explanation: Schedule Scan (Requirements Scan modules) is still in the process of determining the
job's requirements.
SPO6-06 QUEUE FILE I/O ERROR, RC= xxx

User Response: Resubmit the command; if the error persists, contact your installation's CA-7 spe-
SPO6-07 CANNOT CANCEL '*CRDLOAD'

Explanation: An attempt was made to cancel *CRDLOAD from the Request queue. This is not
allowed.

SPO6-08 –SPO6-12
SPO6-08 MUST REQUEUE OR USE FORCE=YES

Explanation: Cancel was requested for a job in the Ready or Active queue, but the CA-11 interface
is installed. Since the interface could cause the CA-11 database entry for this job to be reset, the job
should be requeued before canceling.
User Response: If the job is active or submitted to a CPU, use OS or JES cancel commands to
purge it from the host system. This prevents duplicate runs. If the job is not active or submitted, the
host CPU is (or has been) down, or the job does not use CA-11, then use the FORCE=YES option to
issue the CANCEL.
SPO6-09 RESOURCE CHANGE COMPLETE

Explanation: The request to free tape drives has been successfully completed. The RESCHNG
command may have been issued in a Trailer Step.
User Response: None. Informational message only.
SPO6-10 ***ATTENTION*** STATION= xxx...x (nn)

FURTHER PROCESSING HAS BEEN CANCELLED FOR: REF #nnn...n
JOB= xxxxxxxx,NW= yyyyyyyy [,SUBID= zzzzzzzz]
Explanation: This message is sent to all workstations which have not completed their processing
for the job being canceled.
SPO6-10 *** ATTENTION *** JOB xxxxxxxx (nnnn) HAS BEEN CANCELED
Explanation: This message is sent to the appropriate logical terminal to notify personnel of the
canceled job.
SPO6-11 CANNOT CANCEL - LOAD NOT COMPLETE

Explanation: An attempt was made to cancel a job that is in the Request queue and is currently
going through LOAD processing.
User Response: Wait a few minutes and try again. If the message persists and the job must be
canceled before LOAD completion processing finishes, use the top line CANCEL command with the
FORCE=YES option.
Note: This may cause invalid job data to be added to the database. It is best to wait for the LOAD
to complete before canceling the job.
SPO6-12 CANNOT CANCEL JOB=xxxxxxxx - DUPLICATE JOBNAMES

Explanation: An attempt was made to cancel a job by job name, but there was more than one entry
in the Request queue with that name. The job name entered is indicated by xxxxxxxx.
User Response: The CANCEL command must be reissued using the CA-7 job number instead of
the job name.

SPO6-13 –SPO7-00
SPO6-13 REASON FOR CANCELING IS REQUIRED

Explanation: An attempt was made to cancel a job, but a reason was not supplied.
User Response: Issue the command again with the REASON parameter specifying the reason for
the cancel.
SPO6-14 CANNOT CANCEL - JOB IN COMPLETION STATUS

Explanation: An attempt was made to cancel a job which completed and is in CA-7 completion
processing or waiting for CA-7 completion processing.
User Response: Wait a short time, and the job should finish completion processing (clearing the
Request queue). If the job must be canceled, use the top line CANCEL command with the
FORCE=YES option.
SPO6-15 CANNOT CANCEL - CONNECTED RESOURCES. USE FORCE=YES.

Explanation: The job cannot be canceled because it still holds VRM resources.
User Response: Either use the PRSCF command to release the resources, or use the FORCE=YES
option.
SPO6-16 UNABLE TO CANCEL, ARF RECOVERY IN PROGRESS

Explanation: This message is issued when a CANCEL is attempted while ARF is controlling
recovery for a job.
If the CANCEL must be issued prior to the completion of ARF recovery, then the ARFP command
is complete, the CANCEL may be issued.
SPO7-00 JOB xxxxxxxx (nnnn) ADDED TO THE REQ/Q BY yyyyyyy

[*** JOB TRIGGERING WILL BE BYPASSED ***]
[*** CA-7 DATABASE UPDATES BYPASSED ***]
[*** NEXT SCHEDULED CYCLE WILL BE SKIPPED ***]
REQUEST COMPLETED AT hh:mm:ss ON yy.ddd.
Explanation: The job specified by xxxxxxxx has been successfully added to the Request queue.
The job number assigned by CA-7 is indicated by (nnnn). The command used to bring the job into
the Request queue is indicated by yyyyyyyy. If the SET=NTR option was specified, the trigger
bypass message will be displayed. If the SET=NDB option was specified, the database update
bypass message will be displayed. If the SET=SKP option was specified, the next scheduled cycle
message will be displayed.

SPO7-01 –SPO7-07

If xxxxxxxx=SET and SET=SKP is specified, then the job may not have a schedule. If
xxxxxxxx=DATE, then the value entered is incorrect or DATE may have been entered without TIME
or DOTM which is invalid.
SPO7-02 JOB xxxxxxxx NOT FOUND IN JOB DATA SET

Explanation: The requested job (member) may not have been found in the CA-7 Job data set.
User Response: Several conditions could cause this message to be issued:
1. Verify the job name specified on the input request. If it is invalid, correct and reenter the
command.
2. The Schedule statement may be missing from the initialization file and therefore jobs cannot be
submitted.
3. If there is a Schedule statement, check the HIJBNUM parameter. The high job number may
have been reached. If this is the case, CA-7 cannot add jobs (or networks) to the queue until a
number becomes available or the HIJBNUM value is increased. To increase the value, bring
CA-7 down with a DMPQ, change the value in the initialization file, and bring CA-7 back up
with a TYPE=COLD or MOVQ.
4. An operator may not have the correct user ID authorization to access the job.
5. There is not enough space in the Request queue to add the job.
SPO7-03 JOB xxxxxxxx IS LOCKED

Explanation: The requested job is in locked status.
User Response: Use the LLOCK command to determine why the job is locked and then correct. If
the schedule is locked, do a RESOLV on it. If the job is locked in LOAD status, use the LOAD
command to reload the job. If the LOAD is not successful, error messages will be produced at the
appropriate CA-7 terminal describing the problem.
SPO7-04 CONFLICTING INPUT PARAMETERS: xxxxxxxx / yyyyyyyy

Explanation: The command specified parameters that are mutually exclusive. The xxxxxxxx and
yyyyyyyy indicate the parameters in error.
User Response: Correct and reissue the command.
SPO7-07 xxxxxxxx ERROR RETURN, R15=yyyyyyyy

Explanation: A bad return code was received from the called module specified by xxxxxxxx.
User Response: If xxxxxxxx=SASSSFER and yyyyyyyy=04, then an output network which is con-
nected to a job may not have a schedule or the NWKSCHID from the JOBCONN screen is incorrect.
Use DB.2.3 (SCHD,ONWK) to set up a schedule for the output network or correct the NWKSCHID.
If R15=04 an out of space condition may have been encountered in the Trailer queue.

SPO7-08 –SPO7-13
SPO7-08 I/O ERROR, RC=xxx

User Response: Resubmit the command; if the error persists, contact your installation's CA-7 spe-
SPO7-09 SCHEDULE SCAN POSTED TO DUMP xxxxxxxx LOG FILE

Explanation: A DEMAND(H) or RUN(H) command was issued for the job that is used to dump
the log file indicated by xxxxxxxx.
SPO7-10 JOB xxxxxxxx (nnnn) ENTERED INTO REQUEST 'Q',

[*** CA7 DATABASE UPDATES BYPASSED ***]
[,DEPJOB=jobname2]
or
SPO7-10 JOB xxxxxxxx (nnnn) ENTERED INTO REQUEST 'Q',
[*** CA7 DATABASE UPDATES BYPASSED ***]
[,DEPJOB=jobname2]
Explanation: This message is sent to the CA-7 Master Station to indicate that a new job has been
added to the Request queue. If the JCL is retrieved from the special JCL Override library of ID 254,
it is indicated as such. The due-out date and time specifies when CPU processing must be complete.
If the job was a no database job (NDB), CA-7 database updating is bypassed. The DEPJOB require-
ment will be noted if one was specified.
SPO7-11 SCHEDULE SCAN POSTED TO DUMP [(PRIMARY)|(SECONDARY)] LOG FILE

Explanation: The job (specified in the CA-7 initialization file) which dumps a CA-7 Log data set
has been manually demanded. The data set for which the dump was requested is available and the
job has been scheduled into the Request queue.
Note: Dump jobs are normally scheduled automatically.
SPO7-13 UNABLE TO ATTACH JCL (kkkk) - JOB xxxxxxxx

Explanation: When trying to add a job to the Request queue, the JCL could not be retrieved from
the specified JCL data set. For some of the reason codes, a detailed explanation of the specific error
is displayed within a highlighted box following this message. (See also the SCNJ-18 message for
reason codes identified by kkkk.) xxxxxxxx is the job name.
User Response: Refer to message SCNJ-18.

SPO7-14 –SPO7-20
SPO7-14 UNABLE TO ATTACH JCL FROM OVERRIDE LIB (kkkk) - JOB xxxxxxxx
Explanation: When trying to add a job to the Request queue, the JCL could not be retrieved from
the special JCL Override library of ID 254. kkkk indicates the reason code, values of which are the
same as for message SPO7-13. xxxxxxxx is the job name.
User Response: Verify the input command is correct. If it is, verify that the desired member name
exists in the special Override library. After detecting the problem, either SAVE or REPL the JCL
member in the special library. This is required to indicate to the Job data set that on subsequent
executions, JCL is to be retrieved from this special library.
SPO7-15 xxxxxxxx IS NON EXECUTABLE -- NOT ADDED TO REQUEST 'Q'

Explanation: A nonexecutable job cannot go through the CA-7 load process.
User Response: Either ignore the message or make the job executable and try again. For nonexe-
cutable jobs, the LOAD process serves no purpose and can be ignored.
SPO7-16 SUBMIT DENIED BASED ON USERID IN JCL

Explanation: An attempt was made to DEMAND(H) or LOAD(H) a job and the jobs JCL con-
tained a USERID which the requester was not authorized to submit.
trator to authorize the user to submit for the USERID which exists in the JCL.
SPO7-17 SUBMIT DENIED BASED ON JOB OWNER ID

Explanation: An attempt was made to DEMAND(H) or LOAD(H) a job and the requestor was not
authorized to submit for the USERID in the Job Owner field associated with the job.
User Response: If security access should be allowed, contact your security administrator to
authorize the user to submit for the USERID in the Job Owner field on the DB.1 screen.
SPO7-18 SUBMIT DENIED BASED ON UPDATER ID

Explanation: Someone replaced the QJCL for the job, but did not have the authority to submit for
the USERID in the Job Owner field on the DB.1 screen.
User Response: If security access should be allowed, contact your security administrator to
authorize the user to submit for the USERID in the Job Owner field on the DB.1 screen.
SPO7-19 SUBMIT DENIED BASED ON GLOBAL ID

Explanation: An attempt was made to DEMAND(H) or LOAD(H) a job and the requestor was not
authorized to submit for the USERID associated with CA-7 (the Global ID).
trator to authorize the user to submit for the USERID associated with CA-7.
SPO7-20 CONFLICT IN JCLID AND JCLLIB FIELDS


SPO7-21 –SPO8-01
SPO7-21 JOB NOT DEFINED AND JCLID/JCLLIB NOT SPECIFIED

Explanation: An attempt was made to DEMAND(H) or LOAD(H) a job and the job is not defined
in the CA-7 database and no JCLID= or JCLLIB= keyword was specified to indicate where the JCL
for the job resides.
User Response: Confirm that the jobname was entered correctly. If so, specify a valid JCLID= or
JCLLIB= keyword to indicate where the JCL should be retrieved from.
SPO7-24 ARF REQUIREMENT OVERRIDDEN WITH ARFSET=xxxxxxxx

Explanation: The ARF requirement for this job has been overridden.
SPO7-25 ARF REQUIREMENT OVERRIDDE ERROR. JOB WILL RUN WITHOUT ARF OVER-
RIDE.
Explanation: An error occurred while attempting to override the ARF requirement for this job.
The job will run with its original ARF requirement.
SPO7-26 NO ARF RECOVERY WILL BE IN EFFECT FOR THIS JOB.

Explanation: The job was scheduled with ARFSET=**NONE** on the DEMAND or RUN
command. No ARF processing will be performed.
SPO7-27 JOB xxxxxxxx(nnnn) error

Explanation: An error occurred during ARF attach processing for this job.
SPO8-00 SUBMIT TIME UPDATED FOR JOB nnnn REQUEST COMPLETED AT hh:mm:ss ON
yy.ddd.
Explanation: The submit time has been successfully updated as requested.

Explanation: Keyword xxxxxxxx is invalid or is required but was omitted from the input
command.

SPO8-02 –SPO9-02
SPO8-02 SKELETON RECORD FOUND

Explanation: Schedule Scan is still in the process of building queue records for the requested job.
may be produced for jobs with a status of RETRY on an LQ display. If unable to resolve the
SPO8-04 JOB HAS ALREADY RUN

Explanation: An attempt was made to update the submit time for a job which has already run.
User Response: Verify the job name specified on the input request. If correct, no action is
SPO8-05 SUBTM IS NOT A REQUIREMENT

Explanation: An attempt was made to remove the submit time requirement for a job that does not
have submit time as a requirement.
SPO8-06 JOB NOT FOUND IN REQ/Q

Explanation: The job specified on input was not found in the Request queue.
User Response: Verify the job name on the input request; correct and resubmit command if wrong.
SPO8-07 QUEUE FILE I/O ERROR, RC=xxx

User Response: Resubmit the command; if the error recurs, contact your installation's CA-7 spe-
SPO9-00 REQUEST COMPLETE AT hh:mm:ss ON yy.ddd.


SPO9-02 JOB NOT FOUND IN xxx QUEUE

Explanation: The requested job was not found in the xxx queue.
User Response: Verify the job name in the input request; correct and resubmit the command if
wrong.

SPO9-03 –SPO9-03
SPO9-03 SASSSQM7 ERROR RETURN, R15=xxxxxxxx

Explanation: An error was encountered while attempting to process the input request.

8.2 SPRG Through SRC2 Messages
SPRG-01 –SPRG-17
SPRG-01 xx INVALID MACRO RETURN CODE-nnnnnnnn

Explanation: The SASSSPRG module has detected an error on return from a macro. The Where-
In-Program (WIP) value is specified by xx. The register 15 value (in hex) is specified by nnnnnnnn.
Refer to message SCNJ-18 for an explanation of the nnnnnnnn values.
If xx=4R and nnnnnnnn=1C, the JCL was saved in the Override library and has not been defined on
the DB.1 (JOB) screen, and SASSSPRG is trying to scratch the member in the Override (254)
library.
SPRG-02 JOB xxxxxxxx (nnnn) NOT FOUND. MAY HAVE BEEN CANCELED
Explanation: During a CA-7 job completion cycle, a job that was going through one of the com-
pletion phases is no longer in the Request queue.
User Response: Generally no action is required. The job was probably canceled.
SPRG-16 JOB xxxxxxxx (nnnn) PURGED FROM REQUEST 'Q'.

Explanation: This message is issued to the CA-7 Master Station to show jobs which have been
purged from the Request queue.
SPRG-17 JOB xxxxxxxx (nnnn) PURGED FROM REQUEST 'Q'.

*** JCL MEMBER DELETED FROM OVERRIDE LIBRARY ***
Explanation: This message is issued to the CA-7 Master Station to show a job purged from the
Request queue after its successful completion. It also indicates that the JCL member used for exe-
cuting the job has been deleted from the special JCL Override library.

SRC0-04 –SRC0-14
SRC0-04 CONFLICTING INPUT PARAMETERS

Explanation: Mutually exclusive parameters were specified on the input request. Parameter pairs
that may not be specified together are:
NW=keyword/JOB=keyword
PRINT function/JOB=keyword
PRINT function/NW=keyword
PRINT function/TEST=keyword
PRINT function/OLDYR=keyword
PRINT function/PRINT=keyword
SRC0-05 INVALID OR OMITTED xxxxxxxx DATA

Explanation: Parameter xxxxxxxx has been omitted or is invalid.
SRC0-06 INVALID GENERIC NAME OR NODE

Explanation: Either an NW node or a JOB generic name has been specified incorrectly.
SRC0-11 SECURITY VIOLATION

Explanation: The operator ID used in the /LOGON is not authorized for the function specified.
User Response: If the operator is to be authorized access to the specified function, the Security
macro for that operator ID in the security module must be changed.
SRC0-12
*xxxxxxxx* IS AN INVALID FUNCTION
Explanation: The function specified by xxxxxxxx is invalid.
SRC0-13 INPUT DATA IS NULL

Explanation: No input command was available for processing.
SRC0-14 INPUT DATA IS INCOMPLETE

Explanation: Not enough data was available on the input command to process the request.

SRC0-15 –SRC1-02
SRC0-15 TOO MUCH INPUT DATA

Explanation: Extraneous data was found on the input request.
SRC0-16 INVALID KEYWORD OR DATA IN INPUT

Explanation: An unrecognizable keyword was found in the input request.
SRC0-17 INVALID DATA FOUND FOR THE FOLLOWING FIELDS: xxxxxxxx xxxxxxxx xxxxxxxx
Explanation: The keyword or name of the data found to be invalid is specified by xxxxxxxx.
Invalid data is:
2. Nonalphabetic data specified for an alphabetic parameter.
3. Too much or too little data given for a parameter.
4. Invalid decimal point or sign (+/-) given for a parameter.
SRC1-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd.

Explanation: The input request has been successfully completed. If TEST=YES was in effect, the
schedule members were not updated. Any schedule member for which resolution was not completed
due to errors was not updated as well.
SRC1-01 aa INVALID SGET RETURN CODE=xx

Explanation: aa is the SGET statement where an error occurred. xx is the return code. If aa=20
and xx=01, it indicates that no job member was found to correspond to the schedule member being
resolved.
User Response: To determine which schedule member is in error, do a LSCHD,DSNBR=SJ*
(through the Batch Terminal, if available). The listing should stop at the last good schedule member.
Run the Database Verification program using the JOBSCHD parameter to identify schedule errors.
Then contact your installation's CA-7 specialist for assistance.
SRC1-02 (JOB=xxxxxxxx NOT FOUND)

(NW=xxxxxxxx NOT FOUND)
(NO JOB OR NETWORK SCHEDULES FOUND)
Explanation: The job or network specified on the input request cannot be found in the database.
User Response: Verify that the job or network name was specified correctly. Verify that there is at
least one network and/or job schedule in the CA-7 database. Correct any discrepancies and resubmit
the command.

SRC1-07 –SRC1-103
For a JOB NOT FOUND message, run DBVR (Database Verification) to check for schedule
members missing. If any are found, you can use the DB.2.1 screen and do a DELETE for the JOB.
This will "clean up" a bad schedule pointer. If the job should have a calendar schedule, it will have
to be re-added.
SRC1-07 LOAD ERROR FOR xxxxxxxx WITH RETURN CODE=nn

Explanation: The module specified by xxxxxxxx failed to load.
library. Also verify that an APPLCTN statement exists for the module in either the initialization file
or in the SASSPROG module. If the module is present, contact your installation's CA-7 specialist
for assistance.
SRC1-100 NO SCHEDULES TO RESOLVE FOR SCAL= AND OLDYR= GIVEN

Explanation: RESOLVE command parameters are incorrect.
User Response: Correct the SCAL and OLDYR parameters and reenter the RESOLVE command.
SRC1-101 nnnn SCHEDULES SELECTED FOR RESOLUTION

Explanation: The number of schedules selected for resolution is specified by nnnn. More informa-
tion regarding resolution activity for each schedule will follow this message.
SRC1-102 xx SCRATCH SPACE EXHAUSTED

Explanation: Scratch work file space is insufficient for the amount of data selected using the speci-
fied criteria. The location of the statement in the program being processed when space ran out is
specified by xx.
User Response: The scope of the selection criteria must be narrowed to reduce the number of
schedules selected. Redefine the selection criteria and resubmit the command.
SRC1-103 OUTPUT SCHEDULE MEMBER FOR NW= xxxxxxxx, DSNBR= SOnnnnnn WITH EXTRA-
NEOUS ID OF zzz
Explanation: An output schedule member (identified by SOnnnnnn) has a schedule ID (zzz) which
does not appear in the associated job's schedule definition. The output schedule member is for
network xxxxxxxx.
Note: This error means no updating will be done to the schedule member involved.
User Response: Either the extraneous ID in the output schedule must be omitted or the job
schedule must be updated to include that ID. The schedule may need to be deleted and readded.

SRC1-104 –SRC1-108
SRC1-104 OMITTED OUTPUT SCHEDULE ID OF zzz for NW=xxxxxxxx, DSNBR=SOnnnnnn

Explanation: An output schedule member (SOnnnnnn) does not have the schedule ID (zzz) defined
in the connected job's schedule member. The output schedule member is for network xxxxxxxx.
Output schedule definitions must have IDs which match the creating job's schedule IDs.
User Response: Either the output schedule must be updated to include the omitted ID, or the extra
ID must be removed from the job schedule.
SRC1-105 SCHEDULE RESOLUTION COMPLETE FOR xxnnnnnn, [SCAL=yyyy]

(JOB=xxxxxxxx)
(NW=xxxxxxxx)
Explanation: Indicates successful completion of schedule resolution for schedule member
xxnnnnnn. If TEST=NO was in effect, the member has been updated. The xx portion of the
schedule member name will be SI, SJ or SO for input, job and output, respectively; the nnnnnn
portion is the schedule number (assigned by CA-7). For SI and SJ schedules, the SCAL information
will be shown. For SO and SI schedules, the network name will be shown.
SRC1-106 OUTPUT SCHEDULE RESOLUTION STARTED

Explanation: This is an information only message indicating that output schedule resolution has
started for the job identified in the SRC1-110 message immediately preceding this SRC1-106.
SRC1-107 UNABLE TO COMPLETE RESOLUTION FOR xxnnnnnn, JOB=yyyyyyyy [,NW=zzzzzzzz]

,BECAUSE OF ABOVE ERRORS
Explanation: This message indicates that schedule resolution for xxnnnnnn has been terminated due
to errors. The errors are listed in the SRC1-nnn messages preceding this SRC1-107.
User Response: Correct all indicated errors using Database Maintenance and rerun schedule resol-
ution.
SRC1-108 INVALID RDAY

Explanation: The relative day specified in the schedule data is invalid in relation to the base cal-
endar. RDAY must not overlap into the preceding or following year(s) for months other than
January or December.
User Response: Correct the error using Database Maintenance and rerun schedule resolution.

SRC1-109 –SRC1-113
SRC1-109 NO SCHEDULE DAYS FOR SCHEDULE DATA GIVEN

Explanation: After applying all schedule information to the specified base calendar, no schedule
days were found to exist.
Note: This is a warning only; the schedule member involved will be updated unless other critical
errors are detected.
User Response: Check for a definition with only "not day" (/) specified or for "not day" (/) specifi-
cations which result in no schedule days being defined. Correct the schedule data using Database
Maintenance and rerun schedule resolution (RESOLV).
SRC1-110 *****SCHEDULE RESOLUTION STARTED FOR xxnnnnnn JOB= yyyyyyyy [,NW=xxxxxxxx]

*****
Explanation: This is an information only message indicating that schedule resolution has started for
member xxnnnnnn associated with job yyyyyyyy. If the schedule member is for an input network
(SI), the network name to which the schedule applies will also be shown.
SRC1-111 **SCHEDULE DATA:

Explanation: This message marks the beginning of the schedule data for the member being
resolved as defined in the database. Resolution messages will follow the listing of schedule data.
SRC1-112 mmmdd (DAY # nnn) FALLS ON A NON-SCHEDULE DAY, SCHEDULE DAY RETAINED
Explanation: The schedule day indicated by month (mmm) and day (dd, nnn) falls on a base cal-
endar nonschedule (nonprocessing) day. The ROLL option defined in the database schedule entry
specified that scheduling should occur on base calendar nonprocessing days (that is, do not
reschedule forward or backward).
User Response: The user should verify each of these days to ensure that scheduling on base cal-
endar nonprocessing days will produce the desired results. If schedule days are to stand as shown,
then no action is required. If scheduling is to be bypassed or rolled (forward or backward), the
schedule member must be changed and resolved again.
SRC1-113 mmmdd (DAY # nnn) ROLLED [(FORWARD)|(BACKWARD)] TO xxxyy (DAY # zzz)

Explanation: The schedule day indicated by month (mmm) and day (dd, nnn) falls on a base cal-
endar nonprocessing day and has been rolled, forward or backward, to the base calendar processing
day indicated by month (xxx) and day (yy, zzz). If the day that is rolled from or to is outside of the
year's span that is RESOLVed, the nnn or zzz value will be zero. The ROLL option in the database
schedule entry specified that scheduling should be rolled backward (ROLL=B) or forward (ROLL=F)
to the next base calendar processing day.
User Response: The user should verify that each rolled schedule day should be rolled. If not, the
schedule member must be changed and resolved again.

SRC1-114 –SRC1-117
SRC1-114 OUTPUT SCHEDULE RESOLUTION COMPLETED

Explanation: This is an information only message indicating that the resolution of a job's output
schedules are complete.
SRC1-115 mmmdd (DAY # nnn) FALLS ON A NON-SCHEDULE DAY, SCHEDULE DAY OMITTED
Explanation: The schedule day indicated by month (mmm) and day (dd, nnn) has fallen on a base
calendar nonschedule (nonprocessing) day. The ROLL option defined in the database schedule entry
specified that scheduling should be omitted on base calendar nonprocessing days.
User Response: The user should verify each of these days to ensure that bypassing normal sched-
uling will produce the desired results.
SRC1-116 mmmdd (DAY # nnn) UNABLE TO FIND A ROLL DAY

calendar nonprocessing day. The ROLL option specified in the database schedule entry was taken
but no base calendar processing day could be found.
User Response: The schedule data must be changed and the schedule resolved again.
SRC1-117 (W) ID MULTIPLE SCHEDULES AT LEAST ONE DAY

Explanation: At least one day scheduled by this ID is also scheduled by one or more other IDs
within the schedule definition. Also, this message can be caused by the ROLL option forcing one
day's schedule to be rolled forward or backward matching another day's schedule within the same ID.
Note: This is a warning only; the schedule member involved will be updated unless other critical
User Response: The user should verify that multiple processing of the job (or workstation activity)
in one day will produce the desired results. If not, the schedule member should be changed and
resolved again. It is possible, due to the way different calendars can be built, that the multiply
scheduled day is not within the forecastable time frame. Also, having calendars for the previous year
and the next year can sometimes alleviate this message. If this does not, check to see if the job is
scheduled more than once for the same day. To do this, issue command
FJOB,JOB=jobname,SPAN=8742 through the Batch Terminal Interface and check the output. If the
job does not forecast twice for the same day, this situation may clear itself up with the next time
frame's RESOLV.

SRC1-118 –SRC1-121
SRC1-118 mmmdd (DAY # nnn) ROLLED [(FORWARD)|(BACKWARD)] TO xxxyy (DAY # zzz)

DAY IS ALREADY SCHEDULED BY THIS ID
calendar nonprocessing day. The ROLL option was exercised and a new base calendar processing
day was found, as indicated by month (xxx) and day (yy, zzz). If the day that is rolled from or to is
outside of the year's span that is RESOLVed, the nnn or zzz value will be zero. However, the day
rolled to is already scheduled by this ID.
User Response: Determine if the job should be scheduled twice for the noted days; if so, another
SCHID must be used. If the ROLL day is valid, an additional ID must be included in the schedule
definition to allow for scheduling multiple runs on the same day. A "not day" (/) specification must
also be added to remove the original schedule day. The schedule must again be resolved after all
necessary changes are made.
SRC1-119 mmmdd (DAY # nnn) IS A DUE-OUT DAY, JOB STARTS ON A NON-SCHEDULE DAY
Explanation: The due-out day indicated by month (mmm) and day (dd, nnn) is a base calendar
processing day. However, the lead time specified requires that the job be scheduled on a previous
nonprocessing day.
User Response: The user should verify the scheduling of workstation activities on nonprocessing
days for the base calendar referenced by the associated job. Valid processing days for workstation
activities may vary from what are considered valid processing days for the job. If this is the case, a
separate base calendar should be defined for the workstations and the schedules should again be
resolved.
SRC1-120 mmmdd (DAY # nnn) IS SCHEDULE DAY FOR STATION #01,

STATION#ss FALLS ON NON-SCHEDULE DAY xxxyy (DAY #zzz)
Explanation: The schedule day for workstation number ss falls on the base calendar nonschedule
(nonprocessing) day indicated by month (xxx) and day (yy, zzz).
Note: This is a warning only. The schedule member involved will be updated unless other critical
resolved.
SRC1-121 mmmdd (DAY # nnn) IS A DUE-OUT DAY FOR STATION # ss, WORK STARTS ON A
NON-SCHEDULE DAY
Explanation: The due-out day indicated by month (mmm) and day (dd, nnn) for workstation
number ss is a valid processing day in the base calendar. However, the lead time specified in the
schedule definition requires the work to begin on a nonprocessing day.

SRC1-122 –SRC1-134
resolved.
SRC1-122 ** OUTPUT SCHEDULE RESOLUTION STARTED FOR xxnnnnnn, NW-xxxxxxxx**

Explanation: This is an information only message indicating that resolution has started on the
output schedule member specified.
SRC1-123 mmmdd (DAY # nnn) IS SCHEDULE DAY FOR STATION # ss, STATION # ss SCHEDULE
DAY IS NEXT YEAR
Explanation: The schedule day for station number ss falls into next year. CA-7 only maintains a
schedule mask for one year at a time.
errors are found.
User Response: The user should verify that this schedule will produce the desired processing
results. If this situation presents a problem, the schedule definition should be changed to eliminate
the day which falls in the next year. The schedule must then be resolved again.
SRC1-124 (W) mmmdd (DAY# nnn) IS DUE-OUT DAY, SUBTM IS FOR A NON-SCHEDULE DAY
Explanation: The due-out day indicated by month (mmm) and day (dd, nnn) is a valid processing
day in the base calendar. However, the submit time specified in the schedule definition will cause
the work to be submitted on a nonschedule day.
User Response: The user should verify the scheduling and submit time specified. If submittal
should not occur on a nonschedule day, the schedule should be corrected and resolved again.
SRC1-126 (E) mmmdd (DAY # nnn) UNABLE TO ADJUST FOR INDEX DAYS
Explanation: An error has been detected during the attempt to process the Index days.
SRC1-134 JOB|NETWORK nnnnnnnn NOT RESOLVED - CALENDAR SCALyyss NOT AVAILABLE

Explanation: The job or network nnnnnnnn was not processed by this RESOLV command because
the calendar SCALyyss was not available to CA-7 to be used.
User Response: Check the initialization file to make sure that there is a CALBLK statement
defining the calendar. Also, ensure that the calendar is available in the load library or calendar
library referenced by CA-7.

SRC1-135 –SRC1-02
SRC1-135 JOB|NETWORK nnnnnnnn NOT RESOLVED - CALENDAR SCALyyss NOT LOADED

Explanation: The job or network nnnnnnnn was not processed by this RESOLV command because
the calendar SCALyyss was not loaded when this job was selected for RESOLV. This can occur
when a schedule definition is modified while a RESOLV command is executing.
User Response: Reissue the RESOLV command for this job or network.
SRC1-136 JOB|NETWORK nnnnnnnn NOT RESOLVED - CALENDAR SCALyyss DENIED BY

EXTERNAL SECURITY
Explanation: The job or network nnnnnnnn was not processed by this RESOLV command. The
external security system did not allow access to the calendar SCALyyss.
User Response: If appropriate, update the external security system to allow your operator ID access
to the calendar listed.
SRC1-137W SCHEDULE IDS xxx AND yyy ARE BOTH SCHEDULED ON mmm dd
Explanation: This message is produced after SRC1-117 if the extended RESOLV message option is
enabled, or DUPDATE=YES is specified. A message will be produced for each pair of schedule IDs
(for example, 001 and 002) which have scheduled the job/network to run on the same day (for
example, JUL 10).
User Response: Refer to message SRC1-117.
SRC2-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

SRC1-02 UNABLE TO FETCH xxxxxxxx CLIO_RC=nn

Explanation: An error occurred while trying to retrieve the calendar named at xxxxxxxx. nn is the
return code from the SASSCLIO service.
User Response: Use the nn return code to determine your response:
nn Description
04 Parameter list error. Contact your installation's CA-7 specialist for assistance.
08 SGETPDS error. SGETPDS is a CA-7 service routine used for PDS access. Contact
12 X'0C' Unexpected EOF on calendar PDS. Contact your installation's CA-7 specialist for assist-
ance.
16 X'10' Load failed. The indicated calendar could not be located on the calendar PDS or in a
library in the STEPLIB concatenation. If the calendar is on the calendar PDS or in the
STEPLIB concatenation, contact your installation's CA-7 specialist for assistance.

SRC2-07 –SRC2-07
SRC2-07 LOAD ERROR FOR xxxxxxxx WITH RETURN CODE nn

Explanation: The module specified by xxxxxxxx failed to load. The return code from the SLOAD
macro is specified by nn.
library and that there is an APPLCTN statement for it in the initialization file or in the SASSPROG
module. If present, contact your installation's CA-7 specialist for assistance.

8.3 SSM0 Through SYS0 Messages
SSM0-0C –SSM0-08
SSM0-0C JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyy

Explanation: The job was not submitted to the SUBMIT data set indicated.
User Response: Check for other CA-7 messages giving explanations of why the job was not sub-
mitted. Or enter the top line SUBMIT command with no parameters to activate submission proc-
essing.
SSM0-00 JOB xxxxxxxx(nnnn) SUBMITTED TO yyyyyyyy SYn (USERID=zzzzzzzz)

Explanation: The job indicated by xxxxxxxx has been successfully submitted for execution. The
Submit data set to which the job was submitted is indicated by yyyyyyyy. The MAINID to which
the job was directed is SYn. If you are using external security, the userid with which the job is
submitted is zzzzzzzz.
SSM0-04 JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - SUBMIT BARRIER REACHED

Explanation: The job indicated by xxxxxxxx was not submitted because the barrier limit for the
number of CA-7 jobs submitted to yyyyyyyy has been reached.
User Response: Three courses of action are possible:
1. Wait for the number of jobs submitted to drop below the barrier limit and allow the job to be
submitted automatically.
2. Raise the barrier value using the /ASSIGN command and then either force job submission or
allow automatic submission to occur.
3. Change the main ID for the job to a CPU which is not at the barrier limit and then force job
submission.
SSM0-08 JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - DATA SET BUSY

Explanation: This message can be the result of a previous system crash or of particular failures by
ICOM or CA-7. It can also be caused by the normal processing of CA-7 when too many jobs are
submitted at one time.
User Response: If the condition does not clear up in a few minutes, it was probably caused by
failure. To resolve the problem, a reply of SUB=R (or SUB=F) should be made to ICOM's out-
standing WTOR. This is only valid if submit data sets are being used. Refer to the CA-7 Systems
Programmer Guide for valid ICOM WTOR replies. If the condition persists, contact your installa-
tion's CA-7 specialist.

SSM0-1C –SSM0-20
SSM0-1C JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy INVALID CONTROL INFORMATION

Explanation: An error condition exists within the CA-7 submit function.
User Response: If no SASSXX02 exit is coded, check for other CA-7 messages giving explanations
of why the job was not submitted. Otherwise, check the SASSXX02 user exit to ensure that it is not
changing or destroying information passed to it by CA-7.
SSM0-10 JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - PERM I/O ERROR

Explanation: A permanent I/O error has been detected on the Submit data set specified by
yyyyyyyy.
User Response: To regain use of the data set, it will be necessary to scratch and reallocate it in a
different location. CA-7 must be shut down and brought back up before the data set will be avail-
able. In a multi-CPU environment, jobs can be directed to another CPU using the /ASSIGN and
DIRECT commands until the problem can be corrected.
SSM0-14 JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - UNABLE TO OPEN DATA SET
Explanation: The Submit data set specified by yyyyyyyy could not be opened for submission of
jobs. This is an unlikely situation that will generally only occur after a WARM start initialization of
CA-7.
User Response: Verify that the Submit data set is defined by a DD statement in the CA-7 JCL and
by a CPU statement in the initialization file. If the data set is properly defined in both locations,
contact your installation's CA-7 specialist for assistance. In a multi-CPU environment, jobs may be
directed to another CPU using the /ASSIGN and DIRECT commands until the problem is resolved.
SSM0-16 READY QUEUE STOPPED - NO SUBMIT

Explanation: An attempt was made to submit jobs, but the Ready queue has been stopped by the
STOP,Q=RDY command.
User Response: If job submission is desired, restart the Ready queue using START,Q=RDY.
SSM0-18 JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - INVALID SEQ - NO 'M' CALL
Explanation: An error condition exists within the CA-7 submit function.
SSM0-20 JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy INVALID CONTROL BIT SETTING
Explanation: The status of the Submit data set was not acceptable for submitting the job.
User Response: The job will be automatically submitted when the Submit data set status indicates
availability. The CA-7 specialist at your installation should be notified when this error occurs.

SSM0-24 –SSM0-35
SSM0-24 JOB xxxxxxxx(nnnn) NOT SUBMITTED TO yyyyyyyy - CPU TABLE NOT SET UP
Explanation: The internal table required to control job submission was not built because CPU state-
ments in the CA-7 initialization file were omitted.
User Response: If CA-7 was initialized for batch-only type processing and no jobs are to be sub-
mitted, this message may be ignored. If automatic job submission is required, then the appropriate
CPU statements must be added to the initialization file and CA-7 must be shut down and reinitialized
with an ERST start.
SSM0-28 JOB xxxxxxxx (nnnn) NOT SUBMITTED TO yyyyyyyy - JOB IS TOO BIG FOR DATA SET
Explanation: The SUBMIT data set to which the job is to be submitted does not have enough free
space to hold the JCL.
User Response: None. The job will not be submitted at this time. If this or the SSM0-0C message
persists, the size of the Submit data set indicated by yyyyyyyy may need to be increased.

INVALID JOB CARD COLS 70-71 MUST BE BLANK.
HAS BEEN MOVED BACK TO REQUEST 'Q'
Explanation: Columns 70 and 71 of the first JOB statement are not blank and therefore CA-7
cannot track the job. If CA-7 NCF is being used, column 69 of the JOB statement must also be
blank for tracking purposes.
User Response: The job is moved back into the Request queue and flagged with a JCL error.
Correct the JOB statement and restart the job.

INVALID JOB CARD HAS BEEN MOVED BACK TO THE REQUEST 'Q'
Explanation: The length of the job name is greater than the number of characters in the JOB state-
ment where the job name is placed.
User Response: The job is moved back to the Request queue. Check the job name on the JOB
statement in the Request queue to be sure it is correct.
If the job is being loaded, check the DBASE statement LDJOBNM value. If it is being used, the
JOB statements must have room for an 8-character job name.
If the job has #J or #X statements, ensure that the # statements are not deleting all of the JCL for
that job. If this is the case, an SSM0-90 message will be produced with this message.

INVALID JOB CARD FIRST RECORD OF JCLMBR NOT A JOB CARD.
Explanation: The first record in the JCL member does not begin with //.
User Response: The job is moved back into the Request queue. Verify that the first JCL statement
begins with //. Correct and restart the job.

SSM0-36 –SSM0-40

INVALID #J OR #X OVERRIDE CARD
Explanation: A syntax error has been detected in a #J or #X control statement.
User Response: Correct the error and resubmit.
SSM0-37 JOB xxxxxxx (nnnn) NOT SUBMITTED TO yyyyyyyy.

NO UID SELECTED OR UID INVALID - JCL UPDATE REQUIRED
Explanation: An attempt was made to submit a job for execution, but the job's JCL did not contain
a valid USERID or a valid USERID was not available for JCL insertion. The job is moved back to
the Request queue with a status of R-NOUID.
These are some of the circumstances that can cause this message:
1. The SUBUID was coded on the SECURITY statement of the initialization file specifying a sub-
mission hierarchy, but there was not a valid USERID available for the job. SUBNOID=NO
would also have to be coded on the SECURITY statement.
2. JCLUID=NO is coded in the SECURITY statement of the initialization file and the job has a
USERID coded in the JCL.
3. The job has a USERID coded in the JCL but CA-7 does not have submit security access for the
USERID.
User Response: Edit the Request queue JCL. If there is an invalid USERID coded, correct the
USERID. If QJCL is specified on the SUBUID parameter, you may remove an invalid USERID (or
leave the JCL unchanged if there is not a USERID in the JCL) and then replace the Request queue
JCL.
SSM0-38 SECURITY SEGMENT ERROR - CANCEL JOB AND RESUBMIT

User Response: An internal error condition was detected while retrieving a security segment for a
job during submission. The job is moved back to the Request queue with a status of E-SEGERR.
User Response: Cancel and resubmit the job.

JOB MOVED BACK TO REQUEST QUEUE BY ARF.
Explanation: An IS condition for the job was detected by ARF.
User Response: None. The recovery actions defined for this condition will be executed.

ARF ERROR - UNABLE TO REQUEUE JOB.
Explanation: An IS condition for the job was detected by ARF, but the job could not be requeued
because of an internal error.

SSM0-41 –SVCA-01
SSM0-41 JOB xxxxxxxx (nnnn) NOT SUBMITTED TO qqqqqqqq CA-DRIVER ERROR - RC=xx HAS
BEEN MOVED BACK TO REQUEST 'Q'
Explanation: The job named in the message was not submitted because of an error in CA-Driver.
The CA-Driver procedure libraries may not have been accessible to CA-7.
User Response: Ensure that the CA-Driver procedure libraries associated with this job are acces-
sible to CA-7 and resubmit.
SSM0-90 SUBMIT ERROR FOR JOB xxxxxxxxx(nnnn) EC=wwxxyyzz

Explanation: The job is in Ready queue with no JCL attached.
User Response: Cancel the job and re-DEMAND. Check for the SASSxx05 user exit. It may have
deleted the JCL. Also check SASSxx02 for the same reason.
The JCL may have been deleted due to #J or #X statements. If this is the case, the job will be
requeued back to the request queue and the SSM0-34 message will be produced.
SSM3-25 JOB xxxxxxxx (nnnn) AND JOB yyyyyyyy (ALREADY SUBMITTED) ARE MUTUALLY
EXCLUSIVE
RQMT IGNORED BECAUSE OF MANUAL POSTING
Explanation: xxxxxxxx indicates the job in the Ready queue is to be submitted. nnnn is the job
number. yyyyyyyy is the name of a mutually exclusive job that has already been submitted. The
mutually exclusive requirement of job yyyyyyyy was manually posted and is no longer a requirement
for job xxxxxxxx.
User Response: None. Job xxxxxxxx will be submitted (the posting requirement will no longer be
honored) unless job xxxxxxxx has other mutually exclusive job requirements.
SSM3-26 JOB xxxxxxxx (nnnn) AND JOB yyyyyyyy (ALREADY SUBMITTED) ARE MUTUALLY
EXCLUSIVE
JOB xxxxxxxx (nnnn) HAS BEEN MOVED BACK TO REQ Q
Explanation: xxxxxxxx indicates the job in the Ready queue is to be submitted. nnnn is the job
number. yyyyyyyy is the name of a mutually exclusive job that has already been submitted.
User Response: None. Job xxxxxxxx will be moved back to the Request queue and the master
count will be increased by 1. Job xxxxxxxx will be submitted when job yyyyyyyy successfully
completes.
SVCA-01 (taskname) INVALID PARAMETERS AT ENTRY

Explanation: Invalid calling parameters were detected for the job, started task or TSO user identi-
fied by the taskname. The SASSSVCA program can only be called from another program which
must supply a correctly formatted parameter list, such as SASSTRLR or U7SVC. This is a critical
error which will cause a U0001 abend and dump.
User Response: Be sure that CA-7 modules in the STEPLIB or LINKLIST are at the same version
and generation levels to avoid possible incompatibilities. Save all output from the task and contact

SVCA-02 –SVCA-06
SVCA-02 (taskname) CONTROL MODULE NOT LOADED, SVC UNKNOWN

Explanation: The ICMDSECT control module address was not passed through parameters for the
job, started task or TSO user identified by the taskname. This is a critical error which will cause a
U0002 abend and dump.
User Response: Verify that CA-7 has been installed on the system and that CAIRIM has been run.
Also, check the STEPLIB being used to see if ICMDSECT (or ICMDSEC2 if the TEST subsystem is
specified) is found in that library. If the problem is not resolved, save all output from the task and
SVCA-03 (taskname) INVALID /LOGON FORMAT, DEFAULT OPID ASSIGNED

Explanation: An error was detected in the format of a /LOGON statement for the job, started task
or TSO user identified by the taskname. This is a minor error which will cause a return code of 4.
User Response: Since commands will not be passed without a security ID, the default ID of
CA7DUMMY is assigned to the commands. Refer to the CA-7 Security Guide for information about
extracting security IDs and the default used. It is assumed that the default ID is defined with
minimal authority.
SVCA-04 (taskname) SECURITY EXTRACT FAILED, DEFAULT OPID ASSIGNED

Explanation: An error was detected while trying to extract the security ID of the current user for
the job, started task or TSO user identified by the taskname. This is a minor error which will cause
a return code of 4.
User Response: Since commands will not be passed without a security ID, the default ID of
CA7DUMMY is assigned to the commands. Refer to the CA-7 Security Guide for information about
extracting security IDs and the default used. It is assumed that the default ID has been defined for
access to CA-7 with appropriate authority.
SVCA-05 (taskname) SUBMIT CHECK FAILED, SKIPPING INPUT UNTIL NEXT /LOGON
Explanation: A /LOGON was attempted for an ID other than the extracted security ID, but the
required authorization was not defined for the job, started task or TSO user identified by the
taskname. This is a serious error which will cause a return code of 16.
User Response: Since authorization failed for submitting this ID, all commands will be skipped
until the next /LOGON. Commands following the failing /LOGON will not be passed to CA-7.
However, a specially formatted /LOGON statement indicating the error is passed for reporting pur-
poses.
SVCA-06 (taskname) SUBMIT SECURITY NOT DEFINED, OPID CHECKING BYPASSED

Explanation: The security interface indicated that no security definitions exist for the SUBMIT
resource for the job, started task or TSO user identified by the taskname. This is a minor error
which will cause a return code of 4.
User Response: If the security system allows processing of undefined resources, this condition will
result in error messages only and the commands will be passed to CA-7. If the security system does
not allow processing of undefined resources, no commands will be passed to CA-7.

SVCA-07 –SVPR-50
SVCA-07 (taskname) BUFFER SIZE EXCEEDED, SKIPPING INPUT UNTIL NEXT /LOGON
Explanation: The commands between /LOGON statements have exceeded the allowable block size
for the job, started task or TSO user identified by the taskname. This is a serious error which will
cause a return code of 8.
User Response: Try inserting additional /LOGON statements in the command stream to force
blocking. Since the commands are passed in a variable record format, the number of commands that
will fit in a block are likewise variable. For large command streams, some experimentation may be
required. To have the current or defaulted security ID used, a blank /LOGON statement can be
inserted in the stream.
SVCA-99 (taskname) INVALID RETURN FROM CA-7 SVC, RC=hhhhhhhh

Explanation: An invalid return code has been detected from the CA-7 SVC while passing com-
mands for the job, started task or TSO user identified by the taskname. The return code from the
SVC is indicated in hexadecimal by hhhhhhhh. This is a serious error which will cause a return code
of 8.
User Response: Verify that the correct SVC number is being used. If the SVC appears to be in
order, save all output from the task and contact Computer Associates Technical Support.
SVPR-01 xx INVALID MACRO RETURN CODE nnnnnnnn

Explanation: The SASSSVPR module has detected an error on return from a macro. The Where-
In-Program (WIP) value is specified by xx. The register 15 value (in hex) is given by nnnnnnnn. If
xx=1G, issue the command /DISPLAY,Q=ALL to check the available space in the Prior-run queue.
SVPR-18 OUTPUT DSN=x...x NOT FOUND IN INDEX DATA SET

Explanation: An output data set was not found in the CA-7 IDS.
User Response: None. Usually occurs when a job is first loaded. If the data set was known to be
in the CA-7 IDS, contact your installation's CA-7 specialist for assistance.
SVPR-49 FOLLOWING INPUT REQUIREMENT NOT USED BY JOB=xxxxxxxx DSN=y...y

Explanation: A data set requirement for job xxxxxxxx was not opened.
User Response: None. Message is for user information only. If the data set was supposed to be
opened, contact your installation's CA-7 specialist for assistance. This condition can be caused by
using a DISP=(OLD,DELETE). May also get this message if the data set was opened, but the
ddname changed.
SVPR-50 TABLE OVERFLOW -- OUTPUT DSN x.......x NOT CAPTURED

Explanation: The internal table for completion processing has overflowed and the information
about the named data set was lost. Only this creation of the data set and possibly requirement
posting were lost.
User Response: The job that created this data set may need to be marked as a maintenance job
using the MAINT field on the DB.1 (JOB) screen. If requirement posting was lost, may require
manual posting. Contact your installation's CA-7 specialist for assistance.

SVPR-51 –SVPR-67
SVPR-51 INDEX DATA SET ERROR (aaaabbbb) -- OUTPUT DSN x............x NOT CAPTURED
Explanation: An error occurred while updating the CA-7 IDS with data about the data set whose
name appears in the message. The type of error is indicated by aaaabbbb.
User Response: Check for conflicting data set names in the IDS and correct if necessary. Also,
check system console for possible messages related to space or I/O errors on the IDS. If aaaa=0000
and bbbb=0007, then the CA-7 IDS is probably full. For the VSAM data set, all the control areas
are used and a RE-ORG should be sufficient.
SVPR-52 DSN=x.........x SUCCESSFULLY CREATED

Explanation: CA-7 received a type 99 record from the Batch Card Load Program (BCLP) or from
U7SVC for the data set noted. The CA-7 IDS has been updated, and any jobs in the Request queue
containing this data set as an input requirement have been appropriately posted.
SVPR-65 JOB JJJJJJJJ (nnnn) JOB MEMBER ACCESS ERROR, R15=xxxxxxxx

UNABLE TO RESET TEMPORARY REQUIREMENTS
Explanation: The indicated job has at least 1 requirement with a NEXT-RUN value of SKIP or
ONLY, but an error occurred while trying to read the database member record for the indicated job.
The return code is shown as the value for R15=. Job completion processing was not completed
successfully. The job was not added to the Prior-run queue. Input and output trailer processing was
not done. The SKIP and/or ONLY requirements were not reset.
User Response: If the error was not transient, the database will have to be corrected, probably by
your installation's CA-7 specialist. The SKIP or ONLY requirement must be reset manually with the
appropriate DB.3 function. Dependent tasks with this job as a predecessor requirement will have to
have that requirement posted manually. Triggered tasks must be demanded manually. This job will
have to be canceled from the Request queue.
SVPR-66 JOB jjjjjjjj (nnnn) REQUIREMENT ENTRY ACCESS ERROR, R15=xxxxxxxx

Explanation: This is the same condition as explained in message SVPR-65 except the error
occurred while reading a requirement record.
User Response: Same as in message SVPR-65 except some NEXT-RUN requirements may have
already been reset before the error occurred.
SVPR-67 JOB jjjjjjj (nnnn) REQUIREMENT ENTRY UPDATE ERROR, R15=xxxxxxxx

Explanation: This is the same condition as in message SVPR-65 except the error occurred while
rewriting a requirement record.
User Response: Same as in message SVPR-65 except some NEXT-RUN requirements may have
already been reset before the error occurred.

SYN1-00 –SYN1-36
SYN1-00 SYNTAX COMPLETED. PRESS PA1/ENTER TO CONTINUE mmm ERRORS FOUND

Explanation: The JCL syntax check has completed. The number of errors detected is listed.
User Response: Press the PA1 key or the Enter key to return to the edit mode.
SYN1-20 UNDEFINED OR MISSING OPERATION FIELD

Explanation: In the statement displayed, the operation field could not be located or was not defined
in SASSSYT1 or SASSSYT2. The syntax check continues with the next statement.
User Response: Correct and try again.
SYN1-21 EXPECTED CONTINUATION NOT RECEIVED

Explanation: In the statement displayed, the last statement ended in a comma but the next state-
ment was not a continuation. The statement is checked for other errors and the syntax check con-
tinues.
SYN1-22 OPERAND FIELD DOES NOT TERMINATE IN A COMMA OR BLANK

Explanation: A comma or blank was not encountered before reaching column 72. The statement is
checked for other errors and the syntax check continues.
SYN1-28 EXCESSIVE NUMBER OF DD STATEMENTS

Explanation: More than 1625 DDs were encountered in one job step. This message appears for
each DD encountered beyond 1625. The syntax check continues.
SYN1-29 JOB HAS NO STEPS

Explanation: There were no valid EXEC statements after the JOB statement.
SYN1-35 MISPLACED DD
Explanation: A DD statement, other than JOBLIB, JOBCAT or SYSCHK, was found between the
JOB statement and the first EXEC statement. The remainder of the statements are checked for
syntax errors.
SYN1-36 NO NAME ON THE FIRST DD CARD AFTER EXEC

Explanation: The first DD statement after an EXEC does not have a name. The remainder of the
statements are checked for syntax errors.

SYN1-37 –SYN1-50
SYN1-37 OVERRIDE NAME NOT ALLOWED WITH KEY WORD - keyword

Explanation: An override name is not allowed with the keyword displayed.
SYN1-41 UNBALANCED PARENTHESES IN FIELD-field

Explanation: An unbalanced parentheses condition was encountered. The last major keyword proc-
essed is displayed. Processing continues with the next major keyword.
SYN1-42 SOURCE TEXT CONTAINS ILLEGAL CHARACTER IN FIELD-field

Explanation: The statement displayed contains illegal characters in the field indicated. JCL state-
ments may contain only alphabetic, numeric, national or certain special characters. Processing con-
tinues.
SYN1-43 INCORRECT USE OF APOSTROPHE IN FIELD-field

Explanation: The statement displayed contains an incorrect use of an apostrophe. Special charac-
ters are enclosed by apostrophes. If a field contains an apostrophe as part of the character string, the
apostrophe must be expressed as a double apostrophe. The last major keyword processed is dis-
played in the message text. This message is also displayed if an apostrophe is missing. The syntax
check continues with the next statement.
SYN1-44 UNDEFINED KEYWORD-keyword

Explanation: The statement displayed contains a keyword not defined in SASSSYT1 or
SASSSYT2. The keyword may also be present in an undefined combination, such as SPACE with
an EXEC statement. The keyword in question is displayed with the error message. Processing con-
tinues with the next keyword.
SYN1-45 INVALID KEYWORD-keyword

Explanation: The statement displayed contains an invalid keyword. For example, a PROC state-
ment contains a symbolic keyword which is invalid with an EXEC statement. The invalid keyword
is displayed in the message text. Processing continues with the next keyword.
SYN1-50 INVALID OR MISSING NAME IN FIELD-field

Explanation: The statement displayed contains an invalid name or (if a name is required) is missing
a name. The name may be invalid due to length or it may violate the rules for a name. The last
major keyword processed is displayed in the message text. The remainder of the statement is
checked for syntax errors.

SYN1-51 –SYN1-61
SYN1-51 SUBLIST NOT ALLOWED IN FIELD-field

Explanation: The statement displayed contains a sublist with a field which does not allow a sublist.
The last major keyword processed is displayed in the message text.
SYN1-52 INCORRECT USE OF A PERIOD IN FIELD-field

Explanation: The statement displayed contains a period in a field which does not allow a period.
For example, a period is immediately preceded by a close parenthesis or is followed by a comma.
The last major keyword processed is displayed in the message text. Processing continues with the
next major keyword.
SYN1-53 INCORRECT USE OF LEFT PAREN IN FIELD-field

Explanation: The statement displayed contains a left parenthesis which is used incorrectly. For
example, a left parenthesis is immediately preceded by a quote or a right parenthesis. The last major
keyword processed is displayed in the message text. Processing continues with the next major
keyword.
SYN1-59 FORMAT ERROR IN FIELD-field

Explanation: The statement displayed contains one of the following format errors:
1. Zero length keyword (for example, =).
2. Positional parameter out of place.
3. Close parenthesis not followed by a blank, comma or another close parenthesis.
4. Symbolic outside the range of a procedure.
The last major keyword processed is displayed in the message text. Processing continues with the
next major keyword.
SYN1-60 FIELD EXCEEDS ALLOWABLE LENGTH IN FIELD-field

Explanation: The statement displayed contains a field which is too long. The last keyword proc-
essed is also displayed. Processing continues with the next field.
SYN1-61 INVALID NUMERIC IN FIELD-field

Explanation: The statement displayed contains a non-numeric character in a field which must be
numeric. The last keyword processed is also displayed. Processing continues with the next field.

SYN1-62 –SYN1-69
SYN1-62 NUMERIC EXCEEDS MAX ALLOWED VALUE IN FIELD-field

Explanation: The statement displayed contains a numeric field which is larger than the maximum
allowed for that field. The last keyword processed is also displayed. Processing continues with the
next field.
SYN1-63 INVALID VALUE IN FIELD-field

Explanation: The statement displayed contains an invalid value for a field. The last keyword proc-
essed is also displayed. Processing continues with the next field.
User Response: Check for misspelled values. Correct and try again.
SYN1-64 REQUIRED POSITIONAL PARAMETER MISSING IN FIELD-field

Explanation: A required positional parameter is not present. The last keyword processed is dis-
played. Processing continues with the next field.
SYN1-65 EXCESSIVE NUMBER OF POSITIONALS IN FIELD-field

Explanation: The operand field of the keyword displayed contains too many positional parameters.
Processing continues with the next keyword.
SYN1-66 MUTUALLY EXCLUSIVE FIELDS-fields

Explanation: The two keywords or values displayed are mutually exclusive. Processing continues
with the next field.
SYN1-67 INVALID CHARACTER IN FIELD-field

Explanation: The operand of the keyword displayed contains a character which is invalid for that
operand. Processing continues with the next field.
SYN1-68 INVALID PGM=/PROC=

Explanation: The EXEC statement displayed does not contain PGM, PROC or a valid procedure
name. The remainder of the statement is checked for errors.
SYN1-69 NUMBER OF NESTED IF STATEMENTS EXCEEDS ALLOWABLE MAXIMUM

Explanation: JCL IF statements can only be nested 15 levels. The JCL syntax checker found more
than 15 levels of IF statements.
User Response: Correct the JCL.

SYN1-70 –SYN1-89
SYN1-70 EXCESSIVE NUMBER OF ENDIF STATEMENTS

Explanation: The number of ENDIF statements should match the number of IF statements. This
message indicates too many ENDIF statements were found.
SYN1-71 INSUFFICIENT NUMBER OF ENDIF STATEMENTS SPECIFIED

Explanation: The number of ENDIF statements should match the number of IF statements. This
message indicates not enough ENDIF statements were found.
SYN1-72 UNABLE TO LOAD JCLCHECK INTERFACE

Explanation: An error occurred trying to load the interface module for CA-JCLCHECK. The inter-
face is terminated and will not be usable until the problem is corrected.
User Response: Check the console messages from CA-7 startup for possible error conditions.
Verify that module SASSJCKI exists in the CA-7 LOADLIB concatenation.
SYN1-79 JCLCHECK INTERFACE INTERNAL ERROR

Explanation: An invalid return code was received from the interface module.
User Response: Check the console for other messages from CA-7 or CA-JCLCHECK. Perform
any corrective actions indicated. Try the interface again. If problem continues, contact your installa-
SYN1-80 SYSIN STATEMENT WILL BE GENERATED

Explanation: The non-JCL statement was not preceded by a DD *. The message indicates that a
SYSIN DD * statement will be generated if the job is submitted. Processing continues.
User Response: Check for a missing DD * or an incorrect statement.
SYN1-81 ERROR DETECTED BY USER EXIT

Explanation: User exit SASSXX06 detected an error in the statement listed. Processing continues.
User Response: Check message from exit, correct error, and try again.
SYN1-89 PARSE AREA TOO SMALL

Explanation: The statement displayed was too large to complete syntax checking on it. Processing
continues with the next statement.
User Response: Remove nonessential parameters from the statement and try again. Contact your

SYN1-90 –SYN1-96
SYN1-90 INVALID INPUT FILE ID

Explanation: The input file ID posted from the editor was not a 6 or 7. The syntax check is
aborted.
SYN1-91 INPUT FILE EMPTY

Explanation: The input file passed did not contain any statements. The syntax check is aborted.
User Response: Ensure that the Edit Work file is not empty before requesting a syntax check.
SYN1-92 OUT OF SPACE ON FILE 1

Explanation: There was insufficient room in Scratch File 1 to contain JCL images and error mes-
sages. The syntax check is aborted.
User Response: If LIST was specified, retry the syntax check without the LIST option. If the
problem persists, increase the SCRTRK/SWFTRK value on the DAIO statement in the initialization
file, and then reinitialize CA-7.
SYN1-93 STATEMENT TOO BIG

Explanation: A statement which contained more than 2000 characters was encountered. The syntax
check is aborted.
User Response: Remove nonessential parameters from the statement and try again. Contact your
SYN1-94 ERROR ON FILE 1 - field

Explanation: An error was returned while attempting to write a statement image or an error
message. The syntax check is aborted.
SYN1-95 ERROR ON INPUT FILE

Explanation: An error was returned while attempting to read the statements to be checked. The
syntax check is aborted.
SYN1-96 SASSPCEJ ERROR - return code

Explanation: The return code displayed was returned from SASSPCEJ. The syntax check is
aborted.

SYN1-97 –SYS0
SYN1-97 # STATEMENT ERROR FOUND BY SASSJJ01 - return code

Explanation: Module SASSJJ01 detected an error in the syntax of a #X or #J statement. The
statement preceding the one in error is displayed ahead of this message. The return code displayed
was returned from SASSJJ01. The syntax check is aborted.
SYN1-98 JCL TABLE NOT FOUND - table

Explanation: The JCL table displayed was not found by LOAD. The syntax check is aborted.
User Response: Check CA-7 installation for errors. Ensure that SASSPROG has an entry for the
program. Contact your installation's CA-7 specialist for further assistance.
SYN1-99 INTERNAL ERROR

Explanation: A programming error was detected in the syntax checker. The syntax check is
aborted.
SYS0 INVALID INPUT - ERROR

Explanation: The input command contained invalid data.

8.4 TIQ1 Through Tnnn Messages
TIQ1-00 –TIQ5-00
TIQ1-00 TMS ONLINE MONITOR ENDED SYSTEM-CODE(xxxx) USER-CODE(nnnn)

Explanation: Normal completion of TIQ command occurred. Where:
xxxx is the system abend code.
nnnn is user abend code.
User Response: If both xxxx and nnnn are zero, no action is required.
TIQ1-70 FUNCTION ONLY AVAILABLE FROM 3270 TERMINALS

Explanation: TIQ/TIQU command was issued from a non-3270 terminal.
User Response: Use 3270 (online) terminal to issue the command.
TIQ1-91 ATTACH UNSUCCESSFUL FOR UCC1OCTL

Explanation: During the initialization of the CA-7 TIQ interface, a failure occurred while attaching
module UCC1OCTL.
User Response: Determine the reason for the failure by checking module UCC1OCTL in the CA-1
load library, and then try again. It may be necessary to assemble and link UCC1OCTL to correct the
error.
TIQ1-92 BLDL FAILED FOR xxxxxxxx

Explanation: During the initialization of the CA-7 TIQ interface, the module xxxxxxxx could not
be found.
User Response: Verify that the CA-1 library is concatenated to STEPLIB in the CA-7 JCL and that
the indicated module exists. Retry the interface.
TIQ1-93 CA-7 TIQ CANNOT INITIALIZE - PLEASE RETRY

Explanation: A problem was encountered when executing multiple TIQ commands through CA-7.
User Response: Try the TIQ command again. If problem persists, try using the LIST=RST option.
TIQ5-00 TMS ONLINE MONITOR ENDED SYSTEM-CODE(xxxx) USER-CODE(nnnn)

Explanation: Normal completion of TIQ command occurred. Where:
xxxx is the system abend code.
nnnn is user abend code.
User Response: If both xxxx and nnnn are zero, no action is required.

TIQ5-70 –TRLR-01
TIQ5-70 FUNCTION ONLY AVAILABLE FROM 3270 TERMINALS

Explanation: TIQ/TIQU command was issued from a non-3270 terminal.
User Response: Use 3270 (online) terminal to issue the command.
TIQ5-91 ATTACH UNSUCCESSFUL FOR TMSTOCTL

Explanation: During the initialization of the CA-7 TIQ interface, a failure occurred while attaching
module TMSTOCTL.
User Response: Determine the reason for the failure by checking module TMSTOCTL in the CA-1
load library, and then try again. It may be necessary to assemble and link TMSTOCTL TO correct
the error.
TIQ5-92 BLDL FAILED FOR xxxxxxxx

Explanation: During the initialization of the CA-7 TIQ interface, the module xxxxxxxx could not
be found.
User Response: Verify that the CA-1 library is concatenated to STEPLIB in the CA-7 JCL and that
the indicated module exists. Retry the interface.
TIQ5-93 CA-7 TIQ CANNOT INITIALIZE - PLEASE RETRY

Explanation: A problem was encountered when executing multiple TIQ commands through CA-7.
User Response: Try the TIQ command again. If problem persists, try using the LIST=RST option.
TRLR-00 TRLR-00 (TASKNAME) PROCESS {STARTING} JOBSTEP=SSSSSSSS,

PROCSTEP=pppppppp, NODE=nnnnnnnn, OPT=oooooooo
Explanation: This is an informational message indicating the start or completion of Trailer program
processing. The name of the job executing the program is indicated by taskname. The job step
name is indicated by ssssssss. The procedure step name is indicated by pppppppp. The NCF node
name, if present, is indicated by nnnnnnnn. Any PARM options are indicated by oooooooo.
TRLR-01 (taskname) UNABLE TO LOAD xxxxxxxx, NO INPUT PROCESSED

Explanation: The module xxxxxxxx could not be loaded by the Trailer program running under the
job, started task or TSO user identified by taskname. This is a serious error which will cause a
return code of 8.
User Response: Verify that the named module is available in STEPLIB or a LINKLIST library. If
module is present and problem persists, save job logs and contact Computer Associates Technical
Support.

TRLR-02 –TRLR-06
TRLR-02 (taskname) PARM=ACT REQUESTED BUT ICOM IS NOT ACTIVE

Explanation: The parameter value of ACT was specified but, the ICOM component was not active
on the CPU where taskname was executed. ICOM status is determined by examining flag bytes in
the global copy of ICMDSECT. This is a serious error which will cause a return code of 8.
User Response: Determine whether ICOM must really be active for the commands being processed.
If ICOM does not need to be active, remove the ACT parameter and rerun the job. If ICOM must be
active, verify that an ICOM is installed and active on the CPU in question. If ICOM is active, check
for the TEST parameter which requests communication with a test copy of CA-7 to verify that a test
copy of ICOM is active. If this does not work, save the job logs and contact Computer Associates
Technical Support.
TRLR-03 (taskname) DDN=CA7IN/SYSIN MISSING

Explanation: No DD statement was found to supply input to the Trailer program. The program
looks first for CA7IN then for SYSIN. Either ddname may be supplied, but only one will be used.
This is a serious error which will cause a return code of 8.
User Response: Check your JCL for the ddnames indicated. Verify that one or the other is speci-
fied.
TRLR-04 (taskname) DDN=CA7PRINT/SYSPRINT/SYSOUT MISSING

Explanation: No DD statement was found to supply output from the Trailer program. The program
looks first for CA7PRINT then for SYSPRINT and finally for SYSOUT. Either ddname may be
supplied, but only one will be used. This is a serious error which will cause a return code of 8.
User Response: Check your JCL for the ddnames indicated. Verify that one or the other is speci-
fied.
TRLR-05 (taskname) DDN=xxxxxxxx OPEN FAILED

Explanation: The ddname specified by xxxxxxxx could not be opened. This is a serious error
User Response: Verify that the JCL for the specified DD consists of the correct types of parameters
for the indicated name. Correct any errors and rerun the job.
TRLR-06 (taskname) SASSTRAN TABLE FORMAT ERROR, PROCESSING TERMINATED

Explanation: The SASSTRAN module had an invalid format. The SASSTRAN module is used to
screen commands by application area. Internal security levels are ignored for this purpose. This is a
serious error which will cause a return code of 8.
User Response: Verify that the STEPLIB points to a library for the current version level of CA-7.
Also, verify that no libraries in the STEPLIB concatenation contain old versions of SASSTRAN.

TRLR-07 –TRLR-11
TRLR-07 (TASKNAME) ERROR PROCESSING {PARM} INPUT

Explanation: An error occurred processing input indicated. The type of input will be indicated as
PARM or DATA depending on whether it came from PARM or DD input. This is a serious error
User Response: The PARM or DATA causing the error will be listed just before this message.
Correct the error and rerun.
TRLR-08 (taskname) NCF ROUTING REQUESTED BUT NCF NOT INSTALLED

Explanation: The NCFNODE= parameter was specified but NCF is not installed. This is a serious
error which will cause a return code of 8.
User Response: If NCF routing is not required, remove the NCFNODE= parameter and rerun the
job. If NCF routing is desired, verify the NCF installation. Refer to the CA-7 CA-ACTIVATOR 2.1
Supplement for information about installing and verifying the NCF component.
TRLR-09 (taskname) NCF ROUTING REQUESTED BUT NODE (xxxxxxxx) NOT FOUND
Explanation: NCF routing was requested using the NCFNODE= parameter but the node indicated
by xxxxxxxx was not found in the UCC7NODE table. This is a serious error which will cause a
return code of 8.
User Response: Verify the node name requested and check that it is in the UCC7NODE module
installed or initialized by CAIRIM.
TRLR-10 COMMAND NOT IN SPO0 APPLICATION

Explanation: The command listed immediately before this message is not in the SPO0 application
group and may not be issued. The specified command will NOT be passed to CA-7 for processing,
but any other commands in this stream will be passed. This is a minor error which will cause a
return code of 4.
User Response: Determine if another command will satisfy your purpose and change the command
accordingly or remove it from the input stream. If the command must be used, consider the U7SVC
program which is not restricted to SPO0 commands.
TRLR-11 (taskname) xxxx NOT MATCHED IN ICMDSECT

is used for enqueuing certain items (SVC chained data, and so on), such a mismatch could cause
system and data integrity problems. No data was processed.
value is UC07 or UCT7, the system was not initialized using the Version 3.0 or later version for
CAIRIM. To correct, run CAIRIM to INIT or REINIT using the Version 3.0 or later initialization
module.

TRLR-99 –T351-35
TRLR-99 (taskname) ERROR RETURN FROM SASSSVCA, RC=hhhhhhhh

Explanation: An invalid return code was returned from the SASSSVCA program. The code
returned is indicated in hexadecimal by hhhhhhhh. Error messages from SASSSVCA probably
precede this one and will detail the error. This is a serious error which will cause a return code
matching the one from SASSSVCA.
User Response: Refer to preceding messages for corrective action.
TRLR-nn (taskname) INPUT--> x...x

Explanation: This message will follow another error message concerning input errors, and lists the
input causing the error. The nn will be replaced by the message number which identifies the actual
error.
T351-35 BAD KEYWORD FOR JOB: xxxxxxxx

Explanation: While interrogating LJOB output for job xxxxxxxx, module SASST351 encountered
an unknown keyword. The record being interrogated is displayed below the message for debugging
purposes. A user 0035 abend is also issued.
User Response: Contact your installation's CA-7 specialist for assistance. This message indicates
an error in CA-7.

8.5 UTLx Messages
UTL0-05 –UTL1-02
8.5 UTLx Messages
UTL0-05 UNRECOGNIZABLE KEYWORD IN INPUT

Explanation: The input contains unrecognizable data.
User Response: Correct and reenter.
UTL0-05 INVALID OR OMITTED FUNCTION DATA

Explanation: The identified keyword data is either invalid or was required and not entered.
UTL0-11 DATASET IS USERID PROTECTED

Explanation: You are not authorized to use this function.
User Response: Verify that the data set name and userid protection are in the USERID security
module.
UTL0-67 CA-1 NOT ACTIVE ON THE SYSTEM

Explanation: CA-1 has not been initialized on the system.
User Response: If desired, initialize CA-1. Then repeat the command that resulted in this message.
UTL0-68 UNKNOWN CA-1 VERSION DETECTED ON THE SYSTEM

Explanation: The "eyecatcher" of a supposed CA-1 system does not match any of the CA-1 ver-
sions supported by CA-7.
UTL0-69 INTERNAL ERROR PROCESSING TIQ(U) REQUEST

Explanation: The proper CA-7 interface module for CA-1 could not be determined for your version
of CA-1.
UTL1-00 REQUEST COMPLETED AT hh:mm:ss ON yy.ddd

Explanation: The request completed at the time and date shown.
UTL1-02 func(rc) DATA SET NOT FOUND

Explanation: The requested data set was not found. The OS macro issued and its return code are
displayed.

8.5 UTLx Messages
UTL1-05 –UTL1-33
UTL1-05 INVALID OR OMITTED keyword DATA

Explanation: The keyword specified was omitted or incorrectly entered.
UTL1-12 func(rc) REQUIRED DASD VOLUME NOT AVAILABLE

Explanation: Either the required DASD is not online or a DD statement is not available to CA-7 to
access that volume. The OS macro issued and the return code are printed.
User Response: If desirable, insert a DD statement in the CA-7 execution JCL to access that
volume the next time CA-7 is initialized: or use the ALLOC command to dynamically allocate the
volume.
UTL1-13 LOC(rc) DATA SET NOT DASD OR MULTI-VOLUME

Explanation: Support is provided for single volume DASD data sets only.
UTL1-14 FIND(rc) MEMBER NOT FOUND

Explanation: The requested member was not found in the PDS.
UTL1-15 UNABLE TO OPEN DATA SET DUE TO reason

Explanation: The data set could not be opened because of the specified reason.
UTL1-16 END OF DATA REACHED

Explanation: An end-of-data condition was detected before the specified record was read.
UTL1-17 SYNAD EXIT ENTERED

Explanation: An I/O error occurred while reading the data set.
User Response: Determine cause and correct.
UTL1-33 LOAD ERROR FOR SASSDCON

Explanation: Failure occurred trying to load module SASSDCON.
User Response: Check that the module is in your CA-7 Load library. If missing or error continues,
reassemble and link the module.

8.5 UTLx Messages
UTL1-34 –UTL2-12
UTL1-34 DATE CONVERT ERROR; DATE ARG IS xxxxxxxx, MBR=yyyyyyyy

Explanation: Error occurred while converting what should be a date value indicated by xxxxxxxx
which is hexadecimal and should have format 0yymmdds. The member being processed when the
error occurred is noted by yyyyyyyy.
User Response: Determine why the data is in error and correct.
Note: It is assumed that directory entries have been formatted by TSO/ISPF or equivalent.
UTL1-35 ONLINE CALENDAR MAINTENANCE NOT ENABLED

Explanation: A request was made to list the base calendars in the CA-7 Calendar PDS. However,
the Calendar PDS has not been identified to CA-7 in the initialization deck.
User Response: If you wish to enable the CA-7 Online Calendar Maintenance facility, please refer
to the CALENDAR initialization statement in the CA-7 Systems Programmer Guide.
UTL1-99 function FAILED -- R15=rc FLAGS=xxxx

Explanation: Where:
function - either DMPDSN or LISTDIR
rc - return code value in register 15
xxxx - reason code
User Response: The indicated command has failed. The error codes for Dynamic Allocation can
be found in the IBM MVS/SPL Job Management manual, GC38-1303.
UTL2-02 func(rc) DATA SET NOT FOUND

Explanation: The requested data set was not found. The OS macro issued and its return code are
displayed.

UTL2-12 RDJF(rc) REQUIRED DASD VOLUME NOT AVAILABLE

volume the next time CA-7 is initialized; or use the ALLOC command to dynamically allocate the
volume.

8.5 UTLx Messages
UTL2-15 –UTL3-11
UTL2-15 UNABLE TO OPEN DATA SET DUE TO IO-ERROR

Explanation: An I/O error occurred on data set open.
User Response: Copy the data set to another volume. If that does not solve the problem, contact
UTL2-16 END OF DATA REACHED

Explanation: An end-of-data condition was detected before the specified record was read.
UTL2-17 SYNAD EXIT ENTERED

Explanation: An I/O error occurred while reading the data set.
User Response: Determine cause and correct.
UTL3-00 dsname SUCCESSFULLY CATALOGED [ON cvol]

Explanation: The data set specified is successfully cataloged.

UTL3-01 NO VOLUME ID IN TIOT

Explanation: The volume is not allocated to CA-7.
User Response: Allocate the volume by putting a //U7volser DD in CA-7's PROC, by using the
UT.11 screen or the ALLOC command.

UTL3-11 dsname NOT FOUND

Explanation: The requested data set was not found.

8.5 UTLx Messages
UTL3-12 –UTL4-00
UTL3-12 CVOL NOT ONLINE OR CONTAINS NO CATALOG

DSNAME INCONSISTENT WITH REQUEST
OUT OF SPACE IN CATALOG
I/O ERROR IN CATALOG
UNABLE TO COMPLETE REQUEST (rc)
Explanation: Your request could not be serviced because of one of the listed conditions. The last
message indicates an unexpected return (rc) from the CATALOG macro. The return code is printed.
The following is the correspondence between return code and message:
4 - CVOL NOT ONLINE OR CONTAINS NO CATALOG
8 - DSNAME INCONSISTENT WITH REQUEST
14 - OUT OF SPACE IN CATALOG
1C - I/O ERROR IN CATALOG
rc - UNABLE TO COMPLETE REQUEST (rc)
User Response: Correct the condition which caused the problem or abandon the request.
UTL3-32 COMMAND REJECTED BY USER EXIT

Explanation: User exit SASSXX03 rejected your request.
User Response: Contact your installation's CA-7 specialist for assistance in determining why the
request was rejected.

UTL4-00 dsname SCRATCHED FROM volume [AND UNCATALOGED]

Explanation: The data set name indicated was scratched from the specified volume. If indicated,
the data set was uncataloged as well.
UTL4-00 dsname SCRATCHED FROM volume BUT NOT UNCATALOGED (rc)

Explanation: The data set was scratched from the identified volume but could not be uncataloged
as indicated by the return code (rc).
UTL4-00 dsname ON volume RENAMED newname

Explanation: The data set has been renamed but not necessarily cataloged.

8.5 UTLx Messages
UTL4-00 –UTL4-13
UTL4-00 dsname ON volume RENAMED newname AND RECATALOGED

Explanation: The data set has been renamed. The old name has been deleted from the OS catalog
and the new name has been added.
UTL4-00 dsname ON volume RENAMED newname AND UNCTLGD, BUT NOT RECTLGD (rc)
Explanation: The data set has been renamed. The old name has been deleted from the OS catalog,
but the new name could not be cataloged as indicated by the return code (rc).
UTL4-00 dsname ON volume RENAMED volume BUT NOT UNCATALOGED (rc)

Explanation: The data set was renamed successfully, but the old name could not be uncataloged as
indicated by the return code (rc).
UTL4-00 dsname UNCATALOGED [FROM cvol]

Explanation: The data set is uncataloged.
UTL4-02 LOC(08) DATA SET NOT FOUND

Explanation: The requested data set was not found.

UTL4-12 SCR(01) DATASET NOT FOUND ON volume

SCR(03) DATASET IS DATE PROTECTED
SCR(04) VTOC I/O ERROR
SCR(rc) INVALID RETURN CODE
Explanation: An invalid return code was passed from the OS SCRATCH macro.
User Response: For (03), use the SCRATCHP command if desired. For (rc), contact your installa-
UTL4-13 REN(01) DATASET NOT FOUND ON volume

REN(03) NEWNAME ALREADY EXISTS ON volume
REN(04) VTOC I/O ERROR
REN(rc) INVALID RETURN CODE
Explanation: An invalid return code was passed from the OS RENAME macro.
User Response: For (rc), contact your installation's CA-7 specialist for assistance.

8.5 UTLx Messages
UTL4-14 –UTL5-00
UTL4-14 VOLUME volume NOT AVAILABLE TO CA-7

Explanation: There is no DD statement in the CA-7 execution JCL to allow access to the volume
identified.
User Response: Before your request can be processed, a DD statement for the requested volume
must be added to the execution JCL and CA-7 must be reinitialized, or the ALLOC command must
be entered to dynamically allocate the volume.
UTL4-15 UNCATALOG ERROR (rc)

Explanation: The uncatalog request could not be completed. The return code from the OS macro
is displayed.
User Response: If in error, correct the data set name and retry.


UTL5-00 INDEXES SUCCESSFULLY DELETED FOR nn LEVELS

Explanation: Information only message.
UTL5-00 GDG INDEX BUILT FOR nnn ENTRIES (FULL=action)

UTL5-00 DCONN FUNCTION SUCCESSFUL

UTL5-00 index CONNECTED TO volume


8.5 UTLx Messages
UTL5-05 –UTL5-15

UTL5-12 (08) CATALOG STRUCTURE INCONSISTENT WITH REQUEST

(20) OUT OF SPACE IN CATALOG
(28) I/O ERROR IN CATALOG
(rc) CATALOG MANAGEMENT ERROR
Explanation: Problem can occur while building and cataloging a dummy index.
User Response: CA-7 utilities cannot be used with VSAM or ICF catalogs. Use IDCAMS.
UTL5-13 (rc) CATALOG MANAGEMENT ERROR

Explanation: Problem can occur when uncataloging an index.
User Response: Be sure you are using the correct utility for database access method.
UTL5-14 (rc) CATALOG STRUCTURE INCONSISTENT WITH REQUEST

Explanation: Problem can occur when issuing the BLDG command on a VSAM catalog. Probable
causes are:
1. CA-7 is using IBM's CAMLIST Structure which is limited to use with CVOL catalogs.
2. The necessary index structure is not built.
User Response: There are several actions possible:
1. If the catalog is a VSAM catalog, use some other means outside of CA-7 to build the index, for
example, IDCAMS.
2. If attempting to do a BLDG for A.B.C, then do the following CA-7 commands:
CAT,DSN=A.B.X,VOL=A,DVC=00000000
BLDG,INDX=A.B.C, plus any other needed parameters
UNC,DSN=A.B.X

Explanation: Error occurred while processing a DCONN command.
example, IDCAMS.
UNC,DSN=A.B.X

8.5 UTLx Messages
UTL5-16 –UTL6-00

Explanation: Error occurred while processing a CONN command.
example, IDCAMS.
UNC,DSN=A.B.X
UTL5-17 (04) REQD VOLUME NOT AVAILABLE OR HAS NO CATALOG

(rc) CATALOG STRUCTURE INCONSISTENT WITH REQUEST
(12) INDEX IS ACTIVE AND CANNOT BE DELETED
(20) OUT OF SPACE IN CATALOG
(28) I/O ERROR IN CATALOG
(rc) CATALOG MANAGEMENT ERROR
Explanation: Your request could not be completed because of the listed condition. The OS macro
return code is printed in parentheses. These messages usually occur during a DLTX.
User Response: Correct the condition which caused the problem or abandon the request.
UTL5-18 VOL= MAY NOT BE SYSRES VOLUME

Explanation: A request was made to CONNect the SYSRES volume to itself. This is clearly in
error.
User Response: Correct the VOL parameter and reenter.
UTL5-19 INDEX NOT CONNECTED

Explanation: A request was made to list the connected volume for an index, but the index is not
connected.



8.5 UTLx Messages
UTL6-00 –UTL6-99
UTL6-00 dsname ALLOCATED ON volume AND SUCCESSFULLY CATALOGED | BUT UNABLE

TO CATALOG[(RC=rc)]
Explanation: The data set has been successfully allocated. Either the data was cataloged correctly
or could not be cataloged.
User Response: Determine why the data set could not be cataloged and take necessary action.

UTL6-12 RDJF(04) REQUIRED DASD VOLUME NOT AVAILABLE

volume the next time CA-7 is initialized, or use the ALLOC command to dynamically allocate the
volume.
UTL6-13 DYNAMIC ALLOCATION ONLY AVAILABLE FOR MVS

Explanation: ALLOC command was issued but the operating system is not MVS.
UTL6-14 DATASET ALREADY EXISTS ON VOLUME

OUT OF SPACE IN VTOC
I/O ERROR IN VTOC
INSUFFICIENT SPACE ON VOLUME
ALLOCATION ERROR (RC=rc)
Explanation: Only one message will be printed depending on the situation. For the last message,
the allocation return code is displayed. (See the Direct-Access Data Storage Management document.)
User Response: If possible, try to allocate the data set to another volume.

UTL6-99 [(ALLOC)|(DEALLOC)] FAILED -- R15=rc FLAGS=xxxxxxxxx

Explanation: An attempt was made to do an online allocation or a deallocation for a volume that is
already allocated/deallocated by a //U7volser DD statement in the CA-7 execution JCL.

8.5 UTLx Messages
UTL6-99 –UTL6-99
UTL6-99 [(ALLOC)|(DEALLOC)] SUCCESSFUL FOR DDNAME=//U7volume

Explanation: The indicated command completed successfully for the volume requested.

8.6 U7SVC Messages
U7SVC-00 –U7SVC-04
8.6 U7SVC Messages
U7SVC-00 (taskname) PROCESS {STARTING} JOBSTEP=ssssssss,

PROCSTEP=pppppppp, NODE=nnnnnnnn, OPT=oooooooooo
Explanation: This is an informational message indicating the start or completion of U7SVC
program processing. The name of the job executing the program is indicated by taskname. The job
step name is indicated by ssssssss. The procedure step name is indicated by pppppppp. The NCF
node name, if present, is indicated by nnnnnnnn. Any PARM options are indicated by oooooooo.
U7SVC-01 (taskname) UNABLE TO LOAD xxxxxxxx, NO INPUT PROCESSED

Explanation: A load was attempted for module name xxxxxxxx but failed. The name of the job,
started task or TSO user who invoked U7SVC is shown as taskname. This is a serious error which
will cause a return code of 8.
User Response: Verify that the named module is available in STEPLIB or a LINKLIST library.
Also, check CAIRIM which may be responsible for loading the module.
U7SVC-02 (taskname) DDN=CA7DATA/UCC7DATA MISSING AND NO PARM INPUT

Explanation: Neither of the ddnames indicated was found and no parameter input was present for
this execution of U7SVC. The name of the job, started task or TSO user who invoked U7SVC is
shown as taskname. This is a serious error which will cause a return code of 8.
User Response: Since no input was detected, no processing occurred. Supply PARM= input or DD
input using one of the ddnames indicated and rerun the job or reissue the request.
U7SVC-03 (taskname) DDN=xxxxxxxx OPEN FAILED, {NO} PARM DATA PROCESSED

Explanation: The DD indicated by xxxxxxxx could not be opened. If parameter data was proc-
essed, the value for NO will be blanked. This is a serious error which will cause a return code of 8
if no parameter data was processed. If parameter data was processed, it is considered a minor error
and will return a code of 4.
User Response: Verify the JCL parameters for the named DD statement. Correct any errors and
retry the request.
U7SVC-04 (taskname) ERROR PROCESSING xxxx INPUT

Explanation: An error occurred while processing input. The type of input (xxxx) will be indicated
as PARM or DATA depending on whether it came in from PARM or DD. This is a serious error
User Response: Examine the input listed for errors, correct and resubmit.

8.6 U7SVC Messages
U7SVC-05 –U7SVC-10
U7SVC-05 (taskname) NCF ROUTING REQUESTED BUT NCF NOT INSTALLED

Explanation: The NCFNODE= parameter was specified but NCF is not installed. This is a serious
error which will cause a return code of 8.
User Response: If NCF routing is not required, remove the NCFNODE= parameter and rerun the
job. If NCF routing is desired, verify the NCF installation. Refer to the CA-7 Getting Started for
information about installing and verifying the NCF component.
U7SVC-06 (taskname) NCF ROUTING REQUESTED BUT NODE (xxxxxxxx) NOT FOUND
Explanation: NCF routing was requested using the NCFNODE= parameter but the node indicated
by xxxxxxxx was not found in the UCC7NODE table. This is a serious error which will cause a
return code of 8.
User Response: Verify the node name requested and check that it is in the UCC7NODE module
installed or initialized by CAIRIM.
U7SVC-07 (taskname) DATASET NAME MISSING OR TOO LONG

Explanation: A D= command contained a data set name with too many characters. This is a minor
error which will cause a return code of 4. Only this D= command will be skipped.
User Response: Check the D= command and correct the data set name, then reissue the request.
U7SVC-08 (taskname) VOLSER ENTRY FOR DATASET INVALID

Explanation: A D= command contained a volume serial entry which is invalid. This is a minor
User Response: Check the D= command and correct the volume serial entry, then reissue the
request.
U7SVC-09 (taskname) SCHID ENTRY FOR DATASET INVALID

Explanation: A D= command contained a schedule ID entry which is invalid. This is a minor error
which will cause a return code of 4. Only this D= command will be skipped.
User Response: Check the D= command and correct the schedule ID entry, then reissue the request.
U7SVC-10 (taskname) LTERM ENTRY FOR DATASET INVALID

Explanation: A D= command contained a logical terminal entry which is invalid. This is a minor
User Response: Check the D= command and correct the logical terminal entry, then reissue the
request.

8.6 U7SVC Messages
U7SVC-11 –U7SVC-nn
U7SVC-11 (taskname) DATASET CREATE {REJECTED} BY SECURITY

Explanation: A security error occurred for a D= command. Depending on the security package
involved, the message will indicate that the request was REJECTED or IGNORED. The request may
be IGNORED if security is undefined or the data set is unprotected. Requests which are IGNORED
cause a return code of 4 and are considered as minor errors which are passed on to CA-7. Errors
which are REJECTED are considered as serious errors which are not passed to CA-7, but cause a
return code matching that returned by the security interface.
User Response: Correct any security definitions required before issuing the request again. Security
requires that the issuer have CREATE authority for the data set indicated.
U7SVC-12 (TASKNAME) XXXX NOT MATCHED IN ICMDSECT

is used for enqueuing certain items (SVC chained data, and so on), such a mismatch could cause
system and data integrity problems. No data was processed.
value is UC07 or UCT7, the system was not initialized using the Version 3.0 or later version for
CAIRIM. To correct, run CAIRIM to INIT or REINIT using the Version 3.0 or later initialization
module.
U7SVC-98 (taskname) ERROR RETURN FROM CA-7 SVC, RC=hhhhhhhh

Explanation: For the job, started task or TSO user identified by taskname, an invalid return code
has been detected from the CA-7 SVC while passing commands. The return code from the SVC is
indicated in hexadecimal by hhhhhhhh. This is a serious error which will cause a return code of 8.
User Response: Verify that the correct SVC number is being used. If the SVC appears to be in
order, save all output from the task and contact Computer Associates Technical Support.
U7SVC-99 (taskname) ERROR RETURN FROM SASSSVCA, RC=hhhhhhhh

Explanation: An invalid return code was returned from the SASSSVCA program. The code
returned is indicated in hexadecimal by hhhhhhhh. Error messages from SASSSVCA probably
precede this one and will detail the error. This is a serious error which will cause a return code
matching the one listed from SASSSVCA.
U7SVC-nn (taskname) INPUT--> x...x

Explanation: This message will follow another error message about input errors and lists the input
causing the error. The nn will be replaced by the message number which identifies the actual error.

8.7 WPxx Messages
WP00-10 –WP20-03
8.7 WPxx Messages
WP00-10 ERROR ENCOUNTERED IN EDITOR.

Explanation: SASSWP00, the batch WLP driver, has detected an error in the indicated SASSWPxx
module.
User Response: See WP20-xx or WP21-xx messages.
WP00-20 ERROR ENCOUNTERED IN SIMULATOR.

module.
User Response: See WP50-xx or WP51-xx messages.
WP00-30 ERROR ENCOUNTERED IN LOG SPLITTER.

module.
User Response: Check sort output messages for possible JCL error on job file SIMLOG or
UCC7LOG DD.
WP00-40 ERROR ENCOUNTERED IN REPORT GENERATOR.

module.
User Response: See WP80-xx message.
WP20-01 EXPECTED CONTINUATION NOT FOUND.

module.
User Response: Correct listed input record and resubmit.
WP20-02 MISSING REQUIRED PARAMETER.

module.
User Response: Check documentation for omitted parameter, correct and resubmit.
WP20-03 INVALID OPERATION FIELD.

module.
User Response: Correct control statement and resubmit.

8.7 WPxx Messages
WP20-04 –WP20-11
WP20-04 MISSING CONTROL CARD INFORMATION.

Explanation: Neither WLP1 nor WLP2 was specified as a PARM or in the WLPCC data set.
User Response: Insert either control statement, but not both, and resubmit.
WP20-05 MISSING RES OR JOB CARD.

Explanation: The editor completed processing the UCC7WLP DD data set without encountering at
least one RES and one JOB data statement. If a RES statement is not encountered, UCC7RDFL
cannot act as the default because a time factor must be indicated.
User Response: Resubmit with input containing at least one RES statement and one JOB statement.
WP20-06 WLPCC FILE NOT OPENED.

Explanation: No PARM value was specified on the EXEC statement of the JCL and no WLPCC
DD was included in the JCL.
User Response: Make sure that PARM information is supplied in the JCL on the EXEC statement,
or that a WLPCC DD points to an 80-character, card-image control statement.
WP20-07 UCC7WLP FILE NOT OPENED.

Explanation: The WLP1 command was specified and no UCC7WLP DD was included in the JCL.
User Response: Make sure that a UCC7WLP DD statement is included to point to resource and job
input information in 80-character, card-image format.
WP20-08 RESFILE FILE NOT OPENED.

Explanation: The work file necessary for WLP1 processing was not specified properly in the JCL.
User Response: Make sure RESFILE DD statement is included. It may refer to a temporary data
set.
WP20-09 JOBFILE FILE NOT OPENED.

Explanation: The work file necessary for WLP1 processing was not specified properly in the JCL.
User Response: Make sure JOBFILE DD statement is included for both WLP1 and WLP2. It may
refer to a temporary data set.
WP20-10 RES WORK FILE NOT SUCCESSFULLY SORTED.

Explanation: Invalid return code passed from SORT involved in WLP20.
User Response: Check SORT generated SYSOUT messages for errors.
WP20-11 JOB WORK FILE NOT SUCCESSFULLY SORTED.

Explanation: Invalid return code passed from SORT involved in WLP20.
User Response: Check SORT generated SYSOUT messages for errors.

8.7 WPxx Messages
WP20-12 –WP21-07
WP20-12 INVALID VALUE FOR SPAN

Explanation: The acceptable values for SPAN on the WLP2 statement are 01 to 99. Refer to the
CA-7 Reports Guide.
User Response: Correct the entry and try again.
WP20-13 INVALID DATE/TIME SPECIFIED

Explanation: DATE/TIME value for FROM or TO on the WLP2 statement is in error. FROM
must be less than TO. Values entered must be in the format of yyddd/hhmm. Refer to the CA-7
Reports Guide.
User Response: Correct the entry and try again.
WP21-01 EXPECTED CONTINUATION NOT FOUND.

Explanation: Editor detected continuation error in data statement record.
User Response: Correct indicated input statement and resubmit.
WP21-02 INVALID JOB NAME.

Explanation: Editor detected job name error in data statement record.
WP21-03 INVALID BLANK CARD.

Explanation: Editor detected blank statement error in data statement record.
User Response: Delete blank input statement and resubmit.
WP21-04 INVALID CARD.

Explanation: Editor detected error in data statement record.
WP21-05 INVALID OPERATION FIELD.

Explanation: Editor detected field error in data statement record.
WP21-06 INVALID DATE.

Explanation: Editor detected date error in data statement record.
WP21-07 INVALID KEYWORD xxxxxxxx.

Explanation: Editor detected keyword error in data statement record.

8.7 WPxx Messages
WP21-08 –WP21-16
WP21-08 INVALID VALUE FOR KEYWORD xxxxxxxx.

Explanation: Editor detected parameter error in data statement record.
WP21-09 MISSING VALUE FOR KEYWORD xxxxxxxx.

Explanation: Editor detected keyword error in data statement record.
WP21-10 INCOMPLETE OPERAND FIELD.

WP21-11 INVALID VALUE FOR SCHEDULE-ID.

Explanation: Editor detected schedule ID error in data statement record.
WP21-12 MISSING REQUIRED PARAMETER.

WP21-13 INVALID SUBPARAMETER.

WP21-14 INVALID COMMA.

Explanation: Editor detected comma error in data statement record.
WP21-15 BOTH OF MUTUAL EXCLUSIVE KEYWORDS "TO" AND "SPAN" SPECIFIED.

Explanation: Editor detected error on data statement record.
User Response: Correct indicated input statement and resubmit. Valid combinations are FROM,
FROM/TO, or FROM/SPAN.
WP21-16 DUPLICATE KEYWORD.


8.7 WPxx Messages
WP21-17 –WP50-20
WP21-17 KEYWORD "T" IS NOT THE 1ST PARAMETER FOLLOWING POSITIONAL PARAME-
TERS.
WP21-18 MISSING KEYWORD.

WP21-19 UNBALANCED PARENTHESIS FOR THE SUBPARAMETERS OF THE KEYWORD

xxxxxxxx.
Explanation: Editor detected parenthesis error in data statement record.
WP21-20 INVALID RESOURCE DEFINITION LOAD MODULE NAME.

User Response: Resource definition modules must begin with UCC7R. Correct indicated RES
statement and resubmit.
WP21-21 RESOURCE LOAD MODULE NOT FOUND

Explanation: The module requested was not found.
User Response: Verify module is on library referenced as STEPLIB. If the module is not there:
1. Create a copy of the module on the STEPLIB library; or,
2. Move a copy of the module to the STEPLIB library; or,
3. Concatenate the library containing the module to the STEPLIB library.
WP21-25 MORE THAN 999 DEPENDENCIES FOR A JOB

Explanation: A job was found that had more than 999 dependencies defined.
User Response: The program halts execution at the point where the problem is found. Decrease
the number of dependencies and resubmit the job.
WP50-10 ERROR ENCOUNTERED IN SASSWP51.

Explanation: Simulator driver module detected error in indicated SASSWP5x module.
User Response: System error. Contact your installation's CA-7 specialist for assistance.


8.7 WPxx Messages
WP50-30 –WP80-01
WP50-30 INVALID PRIORITY ALGORITHM SPECIFIED.

User Response: Correct ALG value on control statement and resubmit.



WP50-70 jobname - JOB WAS NOT SUBMITTED.

Explanation: All jobs that fit into the resources specified at the appropriate time would have been
submitted and the last RES statement is currently in effect. Each job that was not ready to be sub-
mitted when sufficient resources were available will generate this message. This is not an error
condition.
User Response: No action is necessary for WLP. Jobs could be rescheduled, however, to allow
resources to be available, or a different RES statement definition could be in effect at the appropriate
time.
WP51-10 INVALID JOB INDICATOR.

User Response: Internal system error. Contact your installation's CA-7 specialist for assistance.
WP51-20 INVALID D/M JOB RECORD GENERATION.

Explanation: The temporary data set produced by WP20 is incorrectly formatted.
WP80-01 NO JOB WAS FOUND DURING THE 8-HR PERIOD FROM yy.ddd/hh:mm TO
yy.ddd/hh:mm
Explanation: No jobs were found for processing during either of the following time spans:
1. For WLP1, the period between the lowest T value on the RES statements and the end of proc-
essing.
2. For WLP2, the period between the FROM and TO (or SPAN) values.
User Response: Not usually an error condition.

8.8 XREF Messages
XREF.003 –XREF.802
8.8 XREF Messages
XREF.003 SORT COMPLETION INVALID

Explanation: The sort returned a bad code.
User Response: Check for sort error messages. After making corrections, rerun the job.
XREF.800 INVALID RECORD TYPE CODE.

Explanation: An invalid database record type code was passed to SASSXREF reporting module. A
database record may be in error.
User Response: Save console listings, logs, and dumps. Contact your installation's CA-7 specialist
for assistance.
XREF.801 JOB DIRECTORIES AND MEMBERS OUT OF SEQUENCE.

Explanation: The directory records, which were written to a work file, were found to be out of
sequence with their corresponding member records on the database backup file.
User Response: Save console listings, logs, and dumps. Contact your installation's CA-7 specialist
for assistance.
XREF.802 SORT COMPLETION INVALID.

Explanation: The sort program used to produce the cross-reference report returned an unexpected
completion code to the calling program.
assistance.

8.9 XTRE Messages
XTRE-00 –XTRE-06
8.9 XTRE Messages
XTRE-00 NO CONTROL CARD ERRORS FOUND

Explanation: This is an informational message indicating that the control statement entered was
validated successfully.
XTRE-01 A JOBNAME IS REQUIRED

Explanation: A job name was not entered. It is required by the SASSXTRK program. A return
code of 13 is produced with this error message.
User Response: Enter a job name. It may be 1-8 characters in length. An asterisk (*) may be used
to provide a generic job specification. An asterisk (*) may not be used as the first character.
XTRE-02 THE FROM DATE IS GREATER THAN THE TO DATE

Explanation: The FROM DATE entered is greater than the TO DATE entered. A return code of
23 is produced with this error message.
User Response: Correct the input and resubmit.
XTRE-03 THE FROM DATE IS GREATER THAN yy366

Explanation: The FROM DATE was specified in the yyddd format. The ddd is greater than 366.
A return code of 33 is produced with this error message.
XTRE-04 THE TO DATE IS GREATER THAN yy366

Explanation: The TO DATE was specified in the yyddd format. The ddd is greater than 366. A
return code of 43 is produced with this error message.
XTRE-05 THE FROM TIME IS GREATER THAN 2400

Explanation: The FROM TIME that was entered is greater than 2400. 2400 is the largest value
that can be used. A return code of 53 is produced with this error message.
XTRE-06 THE TO TIME IS GREATER THAN 2400

Explanation: The TO TIME that was entered is greater than 2400. 2400 is the largest value that
can be used. A return code of 63 is produced with this error message.

8.9 XTRE Messages
XTRE-07 –XTRE-12
XTRE-07 THE FROM TIME IS GREATER THAN TO TIME

Explanation: This message is generated if the FROM and TO dates are the same and if the FROM
TIME is greater than the TO TIME specified. A return code of 73 is produced with this error
message.
XTRE-08 INVALID FORMAT FOR FROM/TO DATE

Explanation: This message is generated if the FROM and/or TO date that was specified did not
have all numeric input specified. A return code of 83 is produced with this error message.
XTRE-09 CONTROL CARD COLUMNS INCORRECT

Explanation: This message is generated if the control has nonblank characters in columns that
should be blank. Refer to the CA-7 Reports Guide for the required format of the input statement. A
XTRE-10 INVALID FORMAT FOR FROM/TO TIME

Explanation: This message is generated if the FROM and/or TO time that was specified did not
have all numeric input specified. A return code of 103 is produced with this error message
XTRE-11 FROM DATE REQUIRED FOR JOB=*

Explanation: An "*" was specified for the job name but the FROM DATE field was not supplied.
A return code of 113 is produced with this error message.
XTRE-12 TO DATE REQUIRED FOR JOB=*

Explanation: An "*" was specified for the job name but the TO DATE field was not supplied. A

8.10 XTRK Messages
XTRK-01 –XTRK-06
8.10 XTRK Messages
XTRK-01 xxxxxxxx DD NOT OPENED SUCCESSFULLY

Explanation: This message indicates that the open for the indicated DD statement failed (SYSIN or
LOGIN). Both of these ddnames are required for execution. This message is a WTO. A return
code of 01 is produced with this error message.
User Response: Ensure that both DD statements are present and resubmit the job.
XTRK-02 INVALID LRECL FOUND FOR LOGIN

Explanation: The LRECL for the LOGIN data set is not valid. A return code of 02 is produced
with this error message.
User Response: Check the JCL and resubmit the job.
XTRK-03 LOAD FAILED FOR SASSXTRE

Explanation: A LOAD was done for the module SASSXTRE and it was not found. A return code
of 03 is produced with this error message.
User Response: Ensure that the SASSXTRE module is in the STEPLIB for this job and resubmit
the job.
XTRK-04 JOBNAME LENGTH IS ZERO

Explanation: The job name that was entered on the control statement has an invalid length. A
User Response: Correct the control statement and resubmit the job.
XTRK-05 NO RECORDS SELECTED

Explanation: No records were found meeting the selection criteria. A return code of 05 is
produced with this error message.
XTRK-06 NO CONTROL CARD SPECIFIED

Explanation: No control card was used for SYSIN.
User Response: Add the control card and rerun the job.

Chapter 9. Database Verification (DBVR)
This chapter contains the database verification (DBVR) messages.
Chapter 9. Database Verification (DBVR) 9-1

9.1 000 Through 255 Messages
000 –007
000 INVALID MSG REQUEST.

Explanation: Indicates a program error.
User Response: Contact your installation's CA-7 specialist for assistance, who may wish to contact
001 INVALID PARM OPTION.

Explanation: Indicates a parameter error.
User Response: Check the PARM and/or DBVPARM DD input in the execution JCL for valid
keywords.
002 NO PARM INFORMATION GIVEN.

Explanation: Indicates a parameter error.
User Response: Add PARM or DBVPARM DD statement.
003 JOBDS DD STATEMENT MISSING.

Explanation: Indicates a misspelled or omitted DD statement.
User Response: Add the JOBDS DD statement.
004 DSDS DD STATEMENT MISSING.

Explanation: Indicates a misspelled or omitted DD statement.
User Response: Add the DSDS DD statement.
005 DSDS MEMBER OPEN PROBLEM.

Explanation: Could not open the Dataset data set for processing members.
User Response: Check to see if you have the correct data set name.
006 JOB MEMBER OPEN PROBLEM.

Explanation: Could not open the Job data set for processing members.
User Response: Check to see if you have the correct data set name.
007 TOO MANY INPUTS WERE SPECIFIED IN PARM OR DBVPARM.

Explanation: Only one input IDS type can be specified.
User Response: Submit with one input type of
INCTLG/INVSAM/PDSCVOL/PDSVSAM/ALLVSAM.

008 –013
008 NO INPUTS WERE SPECIFIED BUT ONE WAS NEEDED.

Explanation: An IDS input is required if IDSVERFY is specified.
User Response: Resubmit with an input type of INCTLG, INVSAM, or ALLVSAM.
009 TOO MANY OUTPUTS WERE SPECIFIED IN PARM OR DBVPARM.

Explanation: Only one IDS output type can be specified when converting the Index data set.
User Response: Resubmit with only one IDS output type of OUTCTLG or OUTVSAM for conver-
sion only.
010 DSDS DIRECTORY ENTRY HAS NO MEMBER DATA DIR xxnnnnnn.

Explanation: Indicates a bad Dataset data set entry.
User Response: If nnnnnn is zero, this message is informational and no real error exists. Other-
wise, contact your installation's CA-7 specialist for assistance, who may wish to contact Computer
Associates Technical Support. Before contacting CA-7 support, enter these commands using the
Batch Terminal Interface and have the output available: DUMP,DSNBR=xxnnnnnn, and an
LCTLG,DSN=AUTO.xxnnnnnn. Also, run SASSBK00 with the XREF parameter.
011 JOB MEMBER HAS NO JOB ENTRY RECORD TYPE JOB xxxxxxxx.
Explanation: Indicates a bad job entry.
Computer Associates Technical Support. Before contacting CA-7 support, enter these commands
using the Batch Terminal Interface and have the output available:
DUMP,JOB=xxxxxxxx,LIST=BYENT
012 INVALID RECORD TYPE IN JOB MEMBER JOB xxxxxxxx.

Explanation: Indicates a bad job entry.
Computer Associates Technical Support. Before contacting CA-7 support, enter these commands
using the Batch Terminal Interface and have the output available:
DUMP,JOB=xxxxxxxx,LIST=BYENT
013 INVALID 1ST CHARACTER OF THE MEMBER NAME ON THE DATA SET DATASET.
MEMBER -- nnnnnnnnnnnnnnnn.
Explanation: Invalid Dataset data set entry.
Computer Associates Technical Support. Before contacting CA-7 support, run SASSBK00 with the
XREF parameter and have the output available.

014 –020
014 INVALID 1ST CHARACTER OF THE MEMBER NAME ON THE JOB DATASET.
MEMBER -- nnnnnnnnnnnnnnnn.
Explanation: Invalid job entry.
Computer Associates Technical Support. Before contacting CA-7 support, run SASSBK00 with the
XREF parameter and have the output available.
015 PARAMETER CONFLICT FOR ALLVSAM DATA BASE.

Explanation: ALLVSAM cannot be specified in combination with any prior IDS type.
User Response: One of the following was specified with ALLVSAM; INCTLG, INVSAM,
OUTCTLG, OUTVSAM, PDSCVOL, PDSVSAM. Remove the conflicting parameter and resubmit.
016 ALLVSAM ERROR ATTEMPTING INIT/CONN/DISCON/FINISH, RC=xxxx.

Explanation: Errors occurred while attempting to initialize, connect, disconnect, or finish with an
017 ERROR ON JOB DIR, RC=xxxx.

Explanation: Logic or I/O error occurred while accessing job directory type entries. RC value
018 ERROR ON JOB MEM, RC=xxxx.

Explanation: Logic or I/O error occurred while accessing job member type entries. RC value gives
error code and WTO message gives specifics on error.
019 ERROR ON DSDS DIR, RC=xxxx.

Explanation: Logic or I/O error occurred while accessing data set directory type entries. RC value
020 ERROR ON DSDS MEM, RC=xxxx.

Explanation: Logic or I/O error occurred while accessing data set member type entries. RC value

021 –053
021 ERROR ON IDS, RC=xxxx.

Explanation: Logic or I/O error occurred while accessing index type entries. RC value gives error
code and WTO message gives specifics on error.
050 DATA SET DS- NETWORK DIR. HAS NO ASSOCIATED IDS ENTRY -
NW-DIR-NWnnnnnn,IDS-KEY-NW.network name.
Explanation: Invalid network entry in Dataset data set.
Computer Associates Technical Support. Before contacting Computer Associates Technical Support,
enter these commands using the Batch Terminal Interface and have the output available:
LNTWK,DSNBR=NWnnnnnn,LIST=ALL and an LCTLG,DSN=NW.network name
051 DATA SET DS-NETWORK DIR. INDICATES AN INPUT SCHEDULE - NONE WAS
FOUND. - NW-DIR-NWnnnnnn,SCH-DIR-SInnnnnn.
Explanation: Invalid schedule pointer.
LNTWK,DSNBR=NWnnnnnn,LIST=ALL and an LCTLG,DSN=NW.network name
052 DATA SET DS-NETWORK DIR. INDICATES AN OUTPUT SCHEDULE - NONE WAS
FOUND. - NW-DIR-NWnnnnnn,SCH-DIR-SOnnnnnn.
LNTWK,DSNBR=NWnnnnnn,LIST=ALL and an LSCHD,DSNBR=SOnnnnnn
053 DATA SET DS- JOB SCH.DIR. HAS NO ASSOCIATED JOB DIR. MEMBER - SJ-DIR
SJnnnnnn,JOB-DIR-xxxxxxxx.
LJOB,JOB=xxxxxxxx and an LSCHD,DSNBR=SJnnnnnn

054 –059
054 DATA SET DS- JOB SCH.DIR. POINTS TO A JOB DIR. BUT DOESN'T POINT BACK
SJ-DIR-SJnnnnnn,JOB-DIR-xxxxxxxx.
055 DATA SET DS- PROSE DIR. HAS NO ASSOCIATED IDS ENTRY - PP-DIR-PPnnnnnn
IDS-KEY-PP.dsname.
Explanation: Invalid prose pointer.
LPROS,DSNBR=PPnnnnnn and an LCTLG,DSN=PP.dsname.
056 JOB DS- JOB DIR. INDICATES IT TRIGGERS OTHER JOBS. - NO IDS ENTRY WAS
FOUND - JOB-DIR-xxxxxxxx,IDS-KEY-JDEP.dsname.
User Response: If there should be triggers, rebuild them on the DB.2.4 (SCHD,JTRG) screen. If
there should not be any triggers, add a dummy trigger on the DB.2.4 (SCHD,JTRG) screen and then
delete the dummy trigger.
057 JOB DS- JOB DIR. INDICATES IT HAS A JOB SCHEDULE. - NONE WAS FOUND
-JOB-DIR-xxxxxxxx,SJ-DIR-SJnnnnnn.
Explanation: Invalid job pointer.
User Response: Delete the schedule on the DB.2.1 (SCHD,JOB) screen.
058 JOB DS- JOB DIR. POINTS TO A JOB SCHEDULE BUT IT DOESN'T POINT BACK -
JOB-DIR-xxxxxxxx,SJ-DIR-SJnnnnnn.
059 DATA SET DS- DATA SET MBR. INDICATES -AUTO- IDS ENTRY NOT FOUND
-DS-MBR-DSnnnnnn.
Explanation: Invalid data set pointer.
User Response: If there should be triggers, rebuild them on the DB.2.6 (SCHD,DTRG) screen. If
there should not be any triggers, add a dummy trigger on the DB.2.6 (SCHD,DTRG) screen and then

060 –065
060 DATA SET DS- DATA SET MBR. HAS NO ASSOCIATED IDS ENTRY -
DS-MBR-DSnnnnnn - IDS-KEY-dsname.
Explanation: Invalid data set pointer.
LDSN,DSNBR=DSnnnnnn and an LCTLG,DSN=dsname.
062 DATA SET DS- DATA SET MBR. MEMBER NAME DOESNT MATCH DIRECTORY
MEMBER NAME - DS-MBR-DSnnnnnn, DS-DIR-DSmmmmmm.
Explanation: Invalid data set entry.
User Response: If nnnnnn is zero, then the message is only informational and no real error exists.
Otherwise, contact your installation's CA-7 specialist, who may wish to contact Computer Associates
Technical Support. Before contacting Computer Associates Technical Support, enter these commands
using the Batch Terminal Interface and have the output available: DUMP,DSNBR=DSnnnnnn,
DUMP,DSNBR=DSmmmmmm,
LDSN,DSNBR=DSnnnnnn,LIST=ALL,
LDSN,DSNBR=DSmmmmmm,LIST=ALL and run SASSBK00 with the XREF parameter.
063 DATA SET DS- NETWORK MBR. INDICATES -AUTO- IDS ENTRY NOT FOUND -
NW-MBR-NWnnnnnn,IDS-KEY-AUTO.network name.
Explanation: Invalid network pointer.
User Response: If there should be triggers, rebuild them on the DB.2.5 (SCHD,NTRG) screen. If
there should not be any triggers, add a dummy trigger on the DB.2.5 (SCHD,NTRG) screen and then
064 DATA SET DS- NETWORK MBR. HAS NO ASSOCIATED IDS ENTRY -
NW-MBR-NWnnnnnn, IDS-KEY-NW.network name.
Explanation: Invalid network entry.
LCTLG,DSN=NW.network name,
LNTWK,DSNBR=NWnnnnnn,LIST=ALL, and
LCTLG,DSN=NW.station name(from the LNTWK command).network name for all stations.
065 DATA SET DS- INPUT NW. SCHED. MBR. HAS NO ASSOCIATED IDS ENTRY
SI-MBR-SInnnnnn,IDS-KEY-NW.network name.
LCTLG,DSN=NW.network name, LNTWK,NW=network name, and LSCHD,DSNBR=SInnnnnn.

066 –070
066 DATA SET DS- INPUT NW. SCHED.MBR. POINTS TO AN IDS ENTRY. NO NETWORK
WAS FOUND - SI-MBR-SInnnnnn,IDS-KEY NW.network name.
LCTLG,DSN=NW.network name, LNTWK,NW=network name, and LSCHD,DSNBR=SInnnnnn.
067 DATA SET DS- INPUT NW. SCHED. MBR. POINTS TO A NETWORK BUT DOES NOT
POINT BACK - SI-MBR-SInnnnnn,MEMBER-NWmmmmmm.
LNTWK,DSNBR=NWmmmmmm, and LSCHD,DSNBR=SInnnnnn.
068 DATA SET DS- OUTPUT NW. SCHED. MBR. HAS NO ASSOCIATED IDS ENTRY -
SO-MBR-SOnnnnnn,IDS-KEY-NW.network name.
LNTWK,NW=network name and LSCHD,DSNBR=SOnnnnnn.
069 DATA SET DS- OUTPUT NW. SCHED. MBR. POINTS TO AN IDS ENTRY. NO
NETWORK WAS FOUND - SO-MBR-SOnnnnnn, IDS-KEY NW.network name.
LNTWK,NW=network name and LSCHD,DSNBR=SOnnnnnn.
070 DATA SET DS- OUTPUT NW. SCHED. MBR. POINTS TO A NETWORK BUT DOES NOT
POINT BACK - SO-MBR-SOnnnnnn,MEMBER-NWmmmmmm.
LNTWK,DSNBR=NWnnnnnn and LSCHD,DSNBR=SOnnnnnn.

071 –104
071 DATA SET DS- PROSE MBR. HAS NO ASSOCIATED IDS ENTRY - PP.xxxxxxxx
PP-MBR-PPnnnnnn.
Explanation: Invalid prose entry.
LPROS,DSNBR=PPnnnnnn and LPROS,DSN=PP.xxxxxxxx.
073 DATA SET DS- PROSE MBR. POINTS TO A DS. MBR. NONE WAS FOUND - PP-MBR-
PPnnnnnn,DS-MBR-DSmmmmmm.
LPROS,DSNBR=PPnnnnnn and LDSN,DSNBR=DSmmmmmm.
074 DATA SET DS- PROSE MBR. POINTS TO A DS. MBR. NO IDS ENTRY WAS FOUND -
PP-MBR-PPnnnnnn - IDS-KEY-PP.dsname.
LPROS,DSNBR=PPnnnnnn, LPROS,DSN=PP.dsname and LCTLG,DSN=PP.dsname.
101 RESERVED - AN INTERNAL ERROR.

Explanation: Program problem.
102 TOTAL NUMBER OF EDITS PERFORMED ON THE NETWORK DIRECTORIES - nnnn

TOTAL ERRORS - xxxx.
Explanation: Totals, not an error.
103 TOTAL NUMBER OF EDITS PERFORMED ON THE PROSE DIRECTORIES - nnnn



105 –112
105 TOTAL NUMBER OF EDITS PERFORMED ON THE JOB SCHEDULE DIRECTORIES -

nnnn TOTAL ERRORS - xxxx.

107 TOTAL NUMBER OF EDITS PERFORMED ON THE JOB DIRECTORIES nnnn TOTAL
ERRORS xxxx.

109 TOTAL NUMBER OF EDITS PERFORMED ON THE DATA SET MEMBERS - nnnn
110 TOTAL NUMBER OF EDITS PERFORMED ON THE NETWORK MEMBERS - nnnn

111 TOTAL NUMBER OF EDITS PERFORMED ON THE PROSE MEMBERS - nnnn TOTAL
ERRORS xxxx.
112 TOTAL NUMBER OF EDITS PERFORMED ON THE INPUT NETWORK SCHEDULE

MEMBERS - nnnn TOTAL ERRORS xxxx.

113 –202

114 TOTAL NUMBER OF EDITS PERFORMED ON THE OUTPUT NETWORK SCHEDULE

MEMBERS - nnnn TOTAL ERRORS xxxx.


117 TOTAL NUMBER OF EDITS PERFORMED ON THE JOB ENTRY MEMBERS - nnnn
118-132 RESERVED - AN INTERNAL ERROR

200 IDS ENTRY SUCCESSFULLY BUILT ON VSAM/CVOL RECORD KEY -- dsname.

Explanation: Tracking message, not an error.
201 A BAD RETURN FROM VSAM - GENCB BLK-ACB.

Explanation: VSAM problem.
User Response: Check the IBM manual OS/VS Virtual Storage Access Method (VSAM) Program-
mers Guide on return codes from GENCB macros for a description of the problem.
202 A BAD RETURN FROM VSAM - GENCB BLK-RPL - OPT-DIR.


203 –210
203 CAN NOT OPEN VSAM FILE --- ERROR CODE - nnn.
mers Guide on return codes from OPEN macros for a description of the problem.
204 A BAD RETURN FROM GET VSAM -- RETURN-nnn, FUNCTION-mmm, FDBK-xxx.

mers Guide on return codes from REQUEST macros for a description of the problem.
205 A BAD OPEN ON DDNAME - DBVTRACE.

Explanation: JCL error.
User Response: Add the DBVTRACE DD to the JCL.
206 A BAD OPEN FOR VSAM FILE ON DDNAME - IDSOUT.

User Response: Add the IDSOUT DD to the JCL.
207 A BAD OPEN ON DDNAME - DSDS.

User Response: Add the DSDS DD to the JCL.
208 A BAD OPEN ON DDNAME - JOBDS.

User Response: Add the JOBDS DD to the JCL.
209 WARNING MESSAGE FROM OPEN VSAM -- REG. 15-n ---ERROR CODE - xxx.
mers Guide on return codes from OPEN macros for a description of the problem. If error code=116
and REG 15=4, run an IDCAMSS VERIFY against the data set.
210 COULD NOT DO LOCATE ON OS CVOL BECAUSE OUTPUT RETURN AREA WAS TOO
SMALL -- YOU MUST INCREASE AREA SIZE.
Explanation: Area size problems.

211 –219
211 A BAD JFCB READ ON OUTPUT OS CVOL DDNAME - IDSOUT.

Explanation: JCL problem.
User Response: Add the IDSOUT DD to the JCL.
212 A BAD JFCB READ ON INPUT OS CVOL DDNAME - IDSIN.

User Response: Add the IDSIN DD to the JCL.
213 A BAD RETURN FROM VSAM - GENCB BLK-EXLST.

214 A BAD RETURN FROM VSAM - GENCB BLK-RPL - OPT-SEQ.

215 A BAD OPEN ON DDNAME - SYSPRINT.

User Response: Add the ddname SYSPRINT to the JCL.
216 A BAD RETURN FROM A LINK TO IEHLIST.

Explanation: IBM's IEHLIST must be in one of your system Load libraries.
User Response: If not, concatenate the library under STEPLIB.
217 A BAD RETURN FROM A OS CVOL BY CAMLIST REG. 15-nnn.

Explanation: CAMLIST problem.
mers Guide on exceptional return codes for a description of the problem.
218 IDS OUT OF SEQUENCE. IDS RECORD DELETED. DSN- DSNAME.

Explanation: The input IDS was out of sequence. All records are deleted until it is back in
sequence.
User Response: Check the messages in DBVTRACE to see what causes it to go out of sequence.
219 TOTAL IDS RECORDS WRITTEN - nnnnnn.


220 –255
220 TOTAL IDS RECORDS WITH ONE VCB. ENTRY - nnnnnn.

221 TOTAL IDS RECORDS WITH SEVEN VCB. ENTRIES - nnnnnn.

222 AVERAGE IDS LRECL - nnnnnn.

223 MAX. IDS LRECL - nnnn.

255 INTERNAL ERROR.


S806 –SB0A
Appendix A. Abend Codes
This appendix contains the abend codes for the NCF VTAM application. An explanation
of the code and corrective action are also provided.
S806
Explanation: The node table was not found. The error message CA-7.NC107 should indicate the
name of the table not found. The level of this error is catastrophic.
Operator Response: Notify the local CA-7 NCF specialist.
Programmer Response: Ensure that the node table was assembled and linked correctly and that the
library that contains the table is accessible.
S80A
Explanation: There is not enough storage for initialization. The VTAM application creates a
number of control blocks for each node in the table and there was not enough storage to accommo-
date this. The level of this error is catastrophic.
Programmer Response: To calculate the storage requirements based on the number of nodes in the
network, refer to the system requirements in the "NCF" chapter in the CA-7 Interfaces Guide.
Increase the region size and resubmit. Also ensure that X'20' bit is turned on at offset 06 in
ICMDSECT.
SB0A
Programmer Response: To calculate the storage requirements based on the number of nodes in the
network, refer to the system requirements in the "NCF" chapter in the CA-7 Interfaces Guide.
Increase the region size and resubmit. Also ensure that the X'20' bit is turned on at offset 06 in
ICMDSECT.
U3313 (X'CF1')
Explanation: The node table was not found. See also error message CA-7.NC107. The level of
this error is catastrophic.
Appendix A. Abend Codes A-1

Programmer Response: Ensure that the node table was assembled and linked correctly and that the
library that contains the table is accessible.
U3314 (X'CF2')
Explanation: The node table contains more nodes than the installation is authorized to operate.
Programmer Response: Decrease the nodes in the table to the authorized number. Contact Com-
puter Associates Technical Support to increase the nodes authorized.
U3315 (X'CF3')
Programmer Response: Refer to the "Planning and System Requirements" chapter in this guide to
calculate the storage requirements based on the number of nodes in the network. Increase the region
size and resubmit.
U3316 (X'CF4')
Explanation: Unsuccessful VTAM ACB open. Refer to message CA-7.NC202 for specific infor-
mation regarding the type of error. The level of this error is catastrophic.
Programmer Response: Review the reason for the error in message CA-7.NC202 and try to
resolve the problem. If it continues, contact Computer Associates Technical Support.
U3317 (X'CF5')
Explanation: Data set I/O error. The message preceding the abend indicates which data set had the
problem. The level of this error is catastrophic.
Operator Response: Ensure that the data set exists and is specified correctly in the JCL.
Programmer Response: Determine if the data set has been corrupted. Correct the problem and
resubmit. Contact the Computer Associates Technical Support if assistance is required.
A-2 CA-7 3.3 Message Guide

U3318 (X'CF6')
Explanation: An internal logic error has been detected. The level of this error is catastrophic.
Programmer Response: Review any error messages which were issued prior to the abend, save all
listings and the dump and contact Computer Associates Technical Support.
U3319 (X'CF7')
Explanation: An NCF system initialization error has occurred.
Programmer Response: This abend is accompanied by error message CA-7.NC113 or
CA-7.NC114. Refer to the appropriate message for further action.
Appendix A. Abend Codes A-3

A-4 CA-7 3.3 Message Guide

CA7 33 Messages

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

CA7 33 Messages

Transféré par

Droits d'auteur :

Formats disponibles

CA-7®

THIS DOCUMENTATION MAY NOT BE COPIED, TRANSFERRED, REPRODUCED, DISCLOSED, OR

The manufacturer of this documentation is Computer Associates International, Inc.

First Edition, September 2000

 1988-2000 Computer Associates International, Inc.

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Chapter 2. AR - CA7M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Chapter 3. CA-7.A - CA-7.X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Chapter 4. CA-7.000 - CA-7.999 . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Chapter 5. CDSI - RSCx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Chapter 6. SANx - SJR2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Chapter 7. SLFA - SPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Chapter 8. SPO0 - XTRK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

iv CA-7 3.3 Message Guide

Chapter 9. Database Verification (DBVR) . . . . . . . . . . . . . . . . . . . . . . 9-1

Appendix A. Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Chapter 1. Introduction 1-1

1.1 Summary of Revisions

This topic explains changes to both CA-7 and to the documentation.

1.1.1 Product Changes

1-2 CA-7 3.3 Message Guide

Display Duplicate Days for RESOLVe

Chapter 1. Introduction 1-3

Prior Run Queue Expansion

1-4 CA-7 3.3 Message Guide

1.1.2 Documentation Changes

Chapter 1. Introduction 1-5

1.2 New or Changed Messages at Version 3.3

1.2.1 Chapter 1 - AR through CA7Mxxxx

Message number Message

1-6 CA-7 3.3 Message Guide

Message number Message

Chapter 1. Introduction 1-7

Message number Message

1-8 CA-7 3.3 Message Guide

Message number Message

Chapter 1. Introduction 1-9

Message number Message

1-10 CA-7 3.3 Message Guide

Message number Message

Chapter 1. Introduction 1-11

Message number Message

1.2.2 Chapter 2 - CA-7.A through CA-7.X

Message number Message

1-12 CA-7 3.3 Message Guide

Message number Message

Chapter 1. Introduction 1-13

Message number Message

1.2.3 Chapter 3 - CA-7.000 through CA-7.999

Message number Message

1-14 CA-7 3.3 Message Guide

Message number Message

1.2.4 Chapter 4 - CDSI through RSCx

Message number Message

Chapter 1. Introduction 1-15

Message number Message

1.2.5 Chapter 5 - SANx through SJR2

Message number Message

1-16 CA-7 3.3 Message Guide

Message number Message

1.2.6 Chapter 6 - SLFA through SPOR

Message number Message

Chapter 1. Introduction 1-17