CA Scheduler Job Management For VSE

Unicenter CA-Scheduler /
 
CA-Driver

Job Management for VSE
Messages Guide
r7.3
K01167-1E
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
International, 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 documentation is proprietary information of CA and protected by the copyright
laws of the United States and international treaties.
Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for
their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only
authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the
license for the software are permitted to have access to such copies.
This right to print copies is limited to the period during which the license for the product remains in full force and
effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced
copies or to certify to CA that same have been destroyed.
To the extent permitted by applicable law, CA provides this documentation “as is” without warranty of any kind,
including without limitation, any implied warranties of merchantability, fitness for a particular purpose or
noninfringement. In no event will CA be liable to 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.
 2005 Computer Associates International, Inc.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
Contents
Chapter 1. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 Message IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.2 CACM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.3 CACO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43
1.4 CACR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61
1.5 CACU Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-111
Chapter 2. CICS Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Contents iii
Chapter 1. Messages
This guide lists all Unicenter CA-Scheduler and Unicenter CA-Driver

Job Management for VSE messages, the reasons for their appearance, and
appropriate remedial action.
Chapter 1. Messages 1-1

1.1 Message IDs
1.1 Message IDs

All messages begin with four letters followed by three numbers. There are
four different types of letters that a message may have:
CACM These messages provide information on the Unicenter CA-Scheduler
Monitor.
CACO These messages relate to Job/Schedule control.
CACR These messages relate to Unicenter CA-Driver.
CACU These messages relate to CAIJxxxx file initialization and
maintenance.
Some messages end with a one-letter code at the end of each message number
giving you additional information.
The Code Means

A You must perform a specific action before continuing.
D You must make a decision before continuing. (You must
reply to this message.)
E An error has occurred.
I This message is for information only.
P The currently running task has stopped. An operator
command is required.
S An error has occurred. A return code is set.
T An error has occurred. The task is terminated.
W Warning message. Something has gone wrong, but it is not
serious enough to stop processing.
1-2 Unicenter CA-Scheduler/CA-Driver Message Guide

1.2 CACM Messages
CACM001 –CACM008
1.2 CACM Messages

CACM001 INVALID COMMAND
Explanation: The Utility program was passed an invalid command.
User Response: Correct command and reissue.
CACM002 INVALID COMMAND OBJECT

Explanation: The token immediately following the command verb was incorrect.
User Response: Check command syntax, correct the command and reissue.
CACM003 TALTER JOB xxxxxxx INVALID KEYWORD

Explanation: The syntax for the designated keyword parameter is incorrect.
User Response: Correct the keyword and reissue the command.
CACM004 NOT ENOUGH GETVIS IN POWER PARTITION

Explanation: Not enough storage in POWER partition.
User Response: Enlarge the GETVIS size in the POWER partition. If necessary, enlarge
the entire POWER partition.
CACM005 DUPLICATE NAME IN SUPVR XECBTAB

Explanation: There is either an internal logic error or a conflicting name has been used
by both Unicenter CA-Scheduler and another software product.
User Response: Contact Computer Associates Technical Support.
CACM006 SUPVR XECBTAB IS EXHAUSTED

Explanation: The supervisor is not generated with enough XECBs (VSE/2 only).
User Response: Request your systems personnel to increase the value for the XECB
keyword parameter on the FOPT supervisor generation macro.
CACM007 INVALID KEYWORD VALUE LENGTH

Explanation: The length of a value exceeded the expectation of the Utility program. For
example, NAME=WEEKLYPAY is invalid on a DEFINE JBR command because the
NAME keyword parameter accepts only eight characters in this context.
User Response: Correct parameter and reissue command.
CACM008 INCOMPLETE COMMAND

Explanation: The end of the command stream was encountered before the command
string was completed. That is, the expected continuation was not received.

1.2 CACM Messages
CACM009 –CACM019
CACM009 DUPLICATE KEYWORD

Explanation: The designated keyword appeared more than once in the command.
User Response: Remove the redundant parameter and reissue command.
CACM010 INVALID KEYWORD

Explanation: A command was issued with a keyword (that is KEYWORD=) which is not
acceptable for this command verb.
User Response: Check the syntax of this command to determine which keywords may
be specified. Correct and reenter command.
CACM011 INVALID LIST SYNTAX

Explanation: A parameter list must take the form of one or more values separated from
each other by commas and enclosed within a set of parentheses.
User Response: Correct the parameter list and reenter command.
CACM012 KEYWORD VALUE MISSING

Explanation: A keyword was specified without a value.
User Response: Supply a value and reenter command.
CACM013 INVALID KEYWORD VALUE TYPE

Explanation: The format of a value specified for a particular keyword did not agree
with the requirements for the keyword parameter. For example, JNO=A is illegal
because the value for the JNO keyword parameter must be either a one- or two-digit
number.
User Response: Correct the parameter value and reenter command.
CACM014 KEYWORD 'xxxxxxxx' MUST BE SPECIFIED

Explanation: A required keyword parameter is absent from the command.
User Response: Code the parameter and reissue command.
CACM016 xxxxxxxx NOT FOUND

Explanation: The record/member referred to in command could not be located.
User Response: Correct the command and reenter.
CACM019 KEYWORD VALUE MUST BE A LIST

Explanation: The syntax for the designated keyword parameter demands that the values
be specified in a list format.
User Response: Correct the parameter and reissue command.

1.2 CACM Messages
CACM022 –CACM028
CACM022 xxxxxxxx STILL ACTIVE

Explanation: An attempt has been made to purge or run a job/schedule which has not
completed.
User Response: Allow the job/schedule to complete or cancel it first.
CACM023 NO JOBS DEFINED

Explanation: The RUN command has been issued for a schedule which does not contain
any jobs.
User Response: DEFINE jobs for this schedule.
CACM024 HAS TO WAIT FOR STORAGE

Explanation: A RUN command was issued for a job or schedule but no more room
existed in the Monitor tables to process this job or schedule.
User Response: Allow completion of some jobs/schedules before reissuing the RUN
command. (Note: Completed jobs/schedules will automatically be purged by the
subsequent RUN command.) Or, request your systems personnel to increase the value
for the DJOB parameter of the CAIJGEN macro if this is a recurring situation.
CACM025 xxxxxxxx NOT ACTIVE

Explanation: Produced by several different commands indicating, for example, that an
attempt has been made to hold a completed job or schedule.
User Response: Recheck the status of the object. Correct and reenter the command.
CACM026 SCHEDULER MONITOR IS IN THE SHUTDOWN PERIOD

Explanation: A request has been made to terminate the Monitor so that various
housekeeping functions may be performed.
User Response: No action required.
CACM027 AUTOSCAN CANNOT BE PERFORMED IN THE SHUTDOWN PERIOD

Explanation: An attempt was made to perform the AUTOSCAN function while Monitor
was being terminated.
User Response: Wait for Monitor to terminate, then reactivate Monitor so that the
AUTOSCAN function can be performed.
CACM028 TOO MANY OCCURRENCES

Explanation: Too many parameter values have been specified in a parameter list.
User Response: Correct the list and reissue the command.

1.2 CACM Messages
CACM029 –CACM035
CACM029 CANNOT RERUN JOB

Explanation: Only jobs which have abended, interrupted, or failed can be rerun.
User Response: Use the RUN command for a new, completed, or canceled job.
CACM030 SYSTEM IS NOT GENNED FOR MULTIPLE CPU

Explanation: The MOVE command was used on a system that was not generated as
multiple CPUs.
User Response: Either do not use the MOVE command, or change the CAIJGEN macro
to specify multiple CPUs.
CACM031 COMMAND SENT TO SYSID: xxxx

Explanation: A command was issued for a job or schedule that is controlled by another
system (xxxx).
CACM032 CANNOT COMP. A CPU JOB

Explanation: COMPLETE commands are illegal for jobs running at the CPU station
because the Monitor automatically detects the completion of such jobs.
User Response: Wait for the job to end. It will be automatically posted as having
completed.
CACM033 jjjjjjjj IS NOT A CPU JOB

Explanation: Only a CPU job may be staged.
User Response: Ensure that this job has been defined at the CPU station. Correct and
reenter the command.
CACM034 xxxxxxxx uuuuuuuu IS NOT AUTHORIZED

Explanation: An unauthorized user has entered a restricted command, where xxxxxxx is
the command and uuuuuuu is the user who issued it.
User Response: Check with your system administrator to determine your authorization
level.
CACM035 IS NOT WAITING FOR COMP. CMD

IS NOT WAITING FOR START CMD
Explanation: Command issued is not appropriate at this time.
User Response: Make sure you use the correct job name or correct command.

1.2 CACM Messages
CACM037 –CACM043
CACM037 AUTOSCAN WAS PERFORMED AT hh:mm FOR SYSID xxxx

Explanation: Monitor is being brought up in the middle of a daily cycle. The
AUTOSCAN function was performed during a successful run earlier that day (generally
at midnight).
CACM039 SUPPORT FOR JCL LIBRARY xxxxxxxx IS NOT GENERATED

Explanation: A job was defined as residing in a particular type of library (for example,
PANVALET). The support for this library was not generated at installation time by the
systems personnel.
User Response: Ask your systems personnel to check the CAIJGEN options for this
particular library type (xxxxxxxx).
CACM040 JCL IS NOT IN READER QUEUE

Explanation: A job was defined as residing in the reader (or input) queue, but Monitor
could not locate the job at run time. Monitor will periodically attempt to locate the job in
the input queue as designated in the CAIJGEN macro. It is assumed that in the near
future, the job will be submitted manually by an operator (or CMS user, etc.) with the
HOLD option specified on the job statement.
User Response: Submit the job to the reader queue with DISP=H or DISP=L. Make
certain you include the * SCSTART and * SCEND statement in the job stream.
CACM041 JOB SUBMISSION FAILURE FROM LIBRARY xxxxxxxx RC=cccc

Explanation: A job was defined as residing in the xxxxxxxx library (LIBRARIAN, for
instance); but it could not be located in the library, or the library could not be referenced
properly.
User Response: Ensure that the library is in the correct format and that the job is stored
in the library. Issue the FORCE command for the job after the problem has been
corrected.
CACM042 DUPLICATE KEYWORD LIST VALUES

Explanation: A particular value appears more than once in a list of values.
User Response: Correct the redundant specification and reissue command.
CACM043 WAITING FOR VOLUMES vvvvvv,vvvvvv

WAITING FOR nnn TAPE DRIVES
Explanation: Produced in response to a STATUS command.

1.2 CACM Messages
CACM044 –CACM046
CACM044 SCHEDULE ssssssss DID NOT START

Explanation: A FORCE command was issued for a job in a schedule which has not
started.
User Response: Start the schedule.
CACM045 PLEASE VERIFY IPL DATE,IPL DATE = yy/mm/dd,LAST DATA BASE ACCESSED
DATE = yy/mm/dd,ENTER YOUR INITIALS TO CONTINUE,OR EOB TO CANCEL
CA-SCHEDULER MONITOR.
Explanation: An inconsistency was discovered in the system date/time when Monitor
was being brought up. Either the current date/time is earlier than the last recorded
date/time, or a wider than normal gap exists between the current date/time and the last
recorded date/time at which Monitor was up and running.
User Response: Either:
1. Enter your initials to indicate that the message was received and understood if the
current date/time are acceptable and any gap can be explained (an extended holiday,
etc.), or
2. Issue a null reply to terminate this session of Monitor if the current date or time is
not correct. Correct the date/time and reactivate Monitor.
CACM046 CMS READ ERROR. SENSE INFO = xxxxxxxxxxxxxxxx

Explanation: An error occurred while attempting to read the virtual statement reader
while running Unicenter CA-Scheduler under VM.
User Response: Be sure that the statement reader is defined to the VM machine where
VSE is running, and that the reader is not started by POWER.

1.2 CACM Messages
CACM050 –CACM053
CACM050 AUTOSCAN IN PROGRESS FOR SYSID xxxx

Explanation: At the designated AUTOTIM, or upon receipt of the AUTOSCAN
command, Monitor begins to scan the database searching for jobs that are scheduled to
be run during this cycle (day). Until the AUTOSCAN is completed, Monitor will only be
able to respond to inquiry commands. However, any jobs scheduled to begin
immediately are started during this process.
User Response: Informational message. No action required. Message CACM051
AUTOSCAN COMPLETED will appear when autoscan is complete.
CACM051 AUTOSCAN COMPLETED

Explanation: Monitor has completed its search of the database. The tracking file has
been updated. The STATUS command will show all the schedules and jobs selected to
be run today.
User Response: Informational message. No action required.
CACM052 COMMAND TOO LONG

Explanation: The command contains too many characters.
User Response: Correct and resubmit.
CACM053 AUTO RECOVERY COMPLETED

Explanation: This informational message indicates that Unicenter CA-Scheduler has
completed automatic recovery following initialization.

1.2 CACM Messages
CACM054 –CACM054
CACM054 (variable text)

Explanation: Normal response to the STATUS command. All lines of the STATUS
display are preceded by this message number.
WHAT THE STATUS DISPLAY SHOWS
SCHEDULE The schedules you selected, in alphabetical order or in order of priority.

Jobs added using the ADD command are identified by the schedule
name $DYNxxxx unless a schedule is defined for them.
JOB NAME The jobs in each schedule, alphabetically or in order of priority.
JNO The occurrence of the job that day.
ST Each station where the job is scheduled.
RC The reason why the job was selected:
If RC is this number
01 - 79 Corresponds to the position of the reason on the criteria statement that was
defined for this job or schedule.
80 Indicates that it was selected because today's date corresponds to a
workday on the CALENDAR that was defined for this job or schedule.
84 Indicates that it is selected by default every day because no selection
criteria were defined.
88 Indicates that it was added to today's schedule by the online RUN
command.
92 Identifies a schedule that is being run because a job abended. (This
schedule was defined on the ABEND option as an alternate schedule in
case of abend).
94 Identifies that the job originates from another node.
95 Indicates that it was added to today's schedule by the online ADD
command.
96 Indicates that this job was a backout job that was submitted for an abended
job that specified ABEND=BACKOUT.
JCNT The number of jobs in the schedule.

SYSID For a schedule, this indicates the SYSID that the schedule is controlled
from. For a job, this indicates the SYSID where the job is to be run, is
now running, or has been run.
STATUS The current status of the schedule or job.

1.2 CACM Messages
CACM054 –CACM054
WHAT THE STATUS MEANS
ABENDED A CPU job canceled with this cancel code can be rerun using the RERUN
or SUBMIT command.
AT=nodeid This is used in conjunction with another status to indicate that a job has
been received, submitted, started, ended, abended, failed, interrupted or
canceled at another node.
AUTO RECVRY HELD
The job or schedule was put on hold as part of automatic recovery
following a system crash. It must be released using the RELEASE
command.
AUTO STRTED
This is a non-CPU job that was defined with the AUTO START=YES
option. The job was automatically started when its early start time was
reached and all of its predecessor conditions were satisfied. Therefore,
you can process the job without posting START. After processing, use
the COMPLETE command to end the job.
user ID CANCLD
The job or schedule was canceled using the Unicenter CA-Scheduler
CANCEL command and can be purged from the status display using the
PURGE command or started again using the RUN, SUBMIT, or RERUN
command. The user ID identifies who canceled the job or schedule; for
example, OPERATOR CANCLD.
ENDED (COMPLETED in prior releases)
The job or schedule has ended with this completion code, and can be
purged from the status display using the PURGE command or started
again using the RUN command.
FAILED The job ended with an MAXRC that exceeded the FAILCODE threshold.
It can be rerun using the RERUN or SUBMIT command.
FM=nodeid This is used in conjunction with another status to indicate that a job
which originated at another node has been received, submitted, started,
ended, abended, failed, interrupted or canceled at this node.
user ID HELD The job or schedule was held using the HOLD command. It will not be
considered for processing until it is released using the RELEASE
command. The user ID identifies who held the job or schedule; for
example, OPERATOR HELD.
INTRPTD This appears on jobs defined with INTERRUPT=Yes. The job must be
manually ended using the COMPLETE command. It can be rerun using
the RERUN or SUBMIT command.

1.2 CACM Messages
CACM054 –CACM054
NO BACKLOG CNCL
The job was canceled at the end of the day because it had not been
submitted or started and it was defined as BACKLOG=NO. You see this
only if another job in the same schedule is still running at autoscan. If a
job is still running, the rest of the schedule cannot be purged. Therefore,
the rest of the jobs that have not yet started are given this status to
indicate that they are not really being carried over to the next day in
backlog, they will be purged when the schedule ends.
NOT REQUESTED (INACTIVE and run if) (requested queues)
This job or schedule has been selected and put into the inactive queue in
case it is requested, but it will only be processed if it is activated by the
REQUEST or SREQ command.
RC= Shows the return code for certain status displays, such as ABENDED,
FAILED, and ENDED.
RECEIVD Tells the originating node that the job has been received at the
destination node, and has not yet started.
SHUTDOWN HELD
The SHUTDOWN DELAY command has been issued and the shutdown
will start as soon as the jobs currently running at the CPU come to an
end.
STARTED A schedule has been started, a CPU job is executing, or a non-CPU job
has been started using the START command. For a CPU job, the status
display shows the POWER job number and the partition it is running in.
SUBMIT IN PROGRESS
Unicenter CA-Scheduler is retrieving a job's JCL from the library where
it is stored and submitting it to the operating system. It cannot be held
at this point.
SUBMIT FAILED
Unicenter CA-Scheduler tried to submit a job and failed. You can
resubmit the job by using the FORCE, RERUN, or SUBMIT command
when the cause of failure is corrected. A four-character code tells you the
source of the error and the reason why the submission failed.

1.2 CACM Messages
CACM054 –CACM054
The first two characters identify the source of the error:
Code Source of Error

04 PROC library
08 ICCF library
0C Unicenter CA-Driver library
10 Unicenter CA-Driver expansion interface
14 SLI library
18 AllFusion CA-Vollie library
1C PANVALET library
20 AllFusion CA-Librarian library
24 CMS member
28 OWL library
34 Non-standard library (requires user interface)
38 Dummy TESTLIB used during testing
3C Internal to Unicenter CA-Scheduler
40 During staging retrieval
44 During staging add
48 The CMS service machine
50 CONDOR library
54 JCLMAN library
The last two characters tell you why the submission failed:
Code For Error

04 The member could not be found
10 A file opening failed
18 Support was not generated for this library
1C A READ failed
20 Internal CATMAN I/O error
24 Internal to Unicenter CA-Scheduler
28 Job name is invalid
2C Internal to Unicenter CA-Scheduler

1.2 CACM Messages
CACM054 –CACM054
Code For Error

34 Class is invalid
3C PRI is invalid
40 SYSID is invalid
44 Unicenter CA-Scheduler ran out of storage
48 POWER communication error - IDENT
4C POWER communication error - CONNECT
50 POWER communication error - SENDR
54 POWER communication error - REQUEST
58 A logic error has occurred
5C Appendage error/CTLSPOOL error
60 An error from the CMS SUBMIT
64 The member is empty (no records)
68 AllFusion CA-Vollie SUBMIT no librarian support
6C AllFusion CA-Vollie INCLUDE not found
70 AllFusion CA-Librarian/Panvalet INCLUDE not found
74 Too many nested INCLUDEs
78 Error on INCLUDE statement
7C LIB link error (bad VCON)
80 The CMS service machine is not logged on
84 The CMS service machine is not receiving
88 CMS service machine access error
8C CMS service machine punch error
90 The CLOSE failed
94 PFIX failed
98 Unicenter CA-Scheduler/Unicenter CA-Driver variable resolution error
9C CMS service machine invalid record length
A0 CMS service machine error unpacking file
A4 JCLMAN member not found or syntax error
A8 eTrust CA-Top Secret user ID not signed on

1.2 CACM Messages
CACM054 –CACM054
SUBMITD The JCL has been submitted to the operating system for execution and
has not started. For a CPU job, the status display shows the POWER job
number.
UNKNOWN This job was either started or submitted when the system failed. It was
not in a job execution queue when Unicenter CA-Scheduler started up
again; therefore it was assigned this status. It can be resubmitted by
issuing a FORCE, RERUN, or SUBMIT command. It can also be canceled
or posted as completed.
WAITING FOR CPU JOB
This job will not start at a post-CPU station until it has ended at the CPU
station.
WAITING FOR PRED
The job or schedule has reached its early start time and is waiting for
one or more of its predecessor conditions to be satisfied. These
predecessor conditions include the start or end of another job or
schedule, the close of a data set, or the satisfaction of a global variable.
(You can specify Y to find out what this job or schedule is waiting for.)
This job or schedule will not run until all of its predecessor conditions
are satisfied, unless it is forced using the FORCE command.
WAITING FOR RESOURCES
The job has reached its early start time and all of its predecessor
conditions have been satisfied. Now it is waiting for a DASD volume to
be mounted, for a data set to close (SEPDSN), or for jobs from which it is
separated to complete. (You can specify Y to find out what resources
this job is waiting for.) It will not run until these resources are available
unless it is forced using the FORCE command.
WAITING FOR START TIME
The job or schedule is waiting for its early start time. It will not be
available for processing until then unless it is forced using the FORCE
command.
WAITING NON-CPU START
This is a non-CPU job that was defined as AUTOSTRT=NO. It is now
available and must be manually started using the START command.
WAITING PRE-CPU JOB
All of the predecessors have been satisfied except the same job at a
pre-CPU station. It will not be submitted at the CPU station until it has
ended at all of the pre-CPU stations in its path.
WAITING USER SUBMIT
Unicenter CA-Scheduler tried to release a job and failed because the JCL
has not yet been manually submitted to the RDR queue. The job must
be manually submitted with DISP=H or DISP=L specified in the JECL
Job statement. Unicenter CA-Scheduler will try at regular intervals to
release the job. This status only occurs when the job is defined with
LIBTYPE=RDRQ.

1.2 CACM Messages
CACM055 –CACM064
CACM055 NO SCHEDULES CURRENTLY IN QUEUE

Explanation: A request was made to display the status of one or more schedules, but
the tracking file contains no schedules at this time. Either all schedules have been
purged or none have been scheduled.
User Response: Run a schedule/job or issue the AUTOSCAN command to cause the
automatic selection process to be initiated.
CACM060 COMPLETED AT hh.mm.ss CODE:xxxxx

Explanation: Indicates that a job or schedule has completed. In the case of a job, the
final completion code is displayed. This message is preceded by a header message.
CACM061 FAILED AT hh.mm.ss CODE:xxxxx

Explanation: Indicates that a job has failed. A number of conditions can produce this
situation; for instance, the job's completion code exceeded the designated FAIL threshold
or the job encountered a run time JCL error. This message is preceded by a header
message.
CACM062 ABENDED AT hh.mm.ss CODE:xxxxx

Explanation: Indicates that a job has abended. This message is preceded by a header
message.
CACM063 INTERRUPTED AT hh.mm.ss CODE:xxxxx

Explanation: Indicates that a job has been interrupted. The job has completed at the
CPU, but Unicenter CA-Scheduler is awaiting an explicit COMPLETE command to post
the job as having been completed, thus making available any successors to this job. This
message is preceded by a header message.
User Response: Issue the COMPLETE command for the job manually.
CACM064 DID NOT START BY MUST TIME hh.mm.ss

DID NOT COMPLETE BY DEADLINE hh.mm.ss
WILL NOT COMPLETE BY DEADLINE hh.mm.ss
EXCEEDED MAXTIME dd/hh:mm
Explanation: Indicates that a job or schedule has not or will not meet one of its
scheduling criteria. This message is preceded by a header message.
User Response: Evaluate the schedule to determine why the job or schedule is late.
Adjust the TIME parameters accordingly if necessary.

1.2 CACM Messages
CACM066 –CACM072
CACM066 PARMS INDICATES NO AUTOSCAN

Explanation: The user has requested, using the UPSI bits, that the AUTOSCAN function
not be performed automatically when Monitor is initialized.
User Response: Issue the AUTOSCAN command manually when ready.
CACM067 CA-SCHEDULER MULTI-CPU SUBTASK INITIALIZED AND ACTIVE

CA-SCHEDULER VM-READER SUBTASK INITIALIZED AND ACTIVE
Explanation: The task which handles communications between the host CPU and other
CPUs has begun functioning.
CACM068 CA-SCHEDULER MULTI-CPU SUBTASK ABENDED

CA-SCHEDULER VM-READER SUBTASK ABENDED
Explanation: The task which handles communications between the host CPU and other
CPUs has abended. If no other subtask has abended, Monitor may be able to continue
processing. However, it will not be informed of activity at other CPUs.
User Response: Terminate and reactive Monitor if this is a critical function.
CACM069 JOB STARTED AT hh.mm.ss

Explanation: A job has started. This message is preceded by a header message.
CACM070 NOT HELD

Explanation: Only jobs or schedules in HOLD status can be released.
User Response: Recheck the current status of the job or schedule.
CACM071 MESSAGE SENT TO xxxxxxxx

MESSAGE BROADCASTED
Explanation: This is the response to SENDMSG command.
CACM072 SCHEDULE STARTED AT hh.mm.ss

Explanation: A schedule has started. This message is preceded by a header message.

1.2 CACM Messages
CACM073I –CACM076I
CACM073I PROGRAM CHECK IN CA-SCHEDULER xxxxxxx AT:aaaaaa

Explanation: A program interrupt has been intercepted, and Unicenter CA-Scheduler
Monitor will be terminated. xxxxxxx may be either MONITOR or SUBMIT. This message
is followed by CACM073D requesting a dump.
User Response: Enter the appropriate AR DUMP commands. When the dumps are
complete, respond to the outstanding reply. Contact Computer Associates Technical
Support for assistance.
CACM073D DUMP SUP,SVA AND SCHED MONITOR PARTITION

Explanation: A program interrupt has been intercepted, and Unicenter CA-Scheduler
Monitor will be terminated. This message follows CACM073I and requests a dump at this
time, before Monitor has a chance to clean up storage locations which may be critical
when solving the problem.
User Response: Enter the appropriate AR DUMP commands. When the dumps are
complete, respond to the outstanding reply. Contact Computer Associates Technical
Support for assistance.
CACM074 GBLA01=nnnn GBLA02=nnnn...

GBLB01=nnnn GBLB02=nnnn...
GBLC01=nnnn GBLC02=nnnn...
Explanation: The values for the global variables are displayed in response to the GBL
command.
CACM075 INSTRUCTIONS FOR JOB:jjjjjjjj IN SCHEDULE:ssssssss

DISPKEY:kkkkkkk
Explanation: This message precedes the instructions for a job.
User Response: Read and follow instructions for the setup and operation of the job.
CACM076I SHUTDOWN DELAYED BECAUSE OF nnnnnnnn RUNNING JOBS

Explanation: A SHUTDOWN DELAY command was issued. The shutdown request was
accepted, but a shutdown cannot occur until the number of jobs indicated by nnnnnnnn
complete.
User Response: No action is necessary. If it is preferable to shut down immediately and
not wait until the running jobs complete, issue the SHUTDOWN RECOVER command.
However, with the SHUTDOWN RECOVER command, Unicenter CA-Scheduler may lose
track of those jobs currently running. When the system is brought up again, those jobs
that were running when SHUTDOWN RECOVER occurred will have to be manually
posted, resubmitted, or canceled. To get a list of those jobs currently running when the
SHUTDOWN DELAY command was issued, issue the STATUS START STATION=40
command.

1.2 CACM Messages
CACM077 –CACM080
CACM077 COMMAND SENT TO NODE: nnnnnnnn

Explanation: A command was issued using RO= and sent to the node indicated by
nnnnnnnn.
CACM078 INVALID OR NOT ATTACHED NODEID, nnnnnnnn

Explanation: A command was issued using RO= to route a command to the indicated
node name, but the node name is either incorrect or the node is not currently connected.
User Response: Check the spelling of the node name to be sure it is valid. Issue the
STATUS DISPLAY NETWORK command to verify that the node is connected. Correct
the problem and resubmit the command.
CACM079 STORAGE LIMIT EXCEEDED FOR VTAM STACK xxxxxxxx

Explanation: Unicenter CA-Scheduler sets a limit on the storage that can be used by
VTAM communication. This limit has been exceeded and may indicate a problem internal
to Unicenter CA-Scheduler.
CACM080 VTAM vvvvv, ERROR detected; RC=rc FB=fb-aaaaaaaa R0=xx RPLREQ=xx

SNSI xxxxxxxx SNSO xxxxxxxx
Explanation: A VTAM error has occurred, with vvvvv indicating the type of error.
RC The return code from VTAM that was returned in register 15.
FB The feedback field passed back from VTAM.
aaaaaaaa The VTAM APPLID.
R0 The contents of register 0.
RPLREQ The RPL request to VTAM that indicates which macro the VTAM request
came from if the request was RPL based.
SNSI, SNSO The sense input and sense output fields from the RPL.
User Response: This message is normal and requires no action if the specified APPLID
that VTAM is trying to communicate with is not available at the moment because when
the node becomes available, the connection will occur automatically, or if Unicenter
CA-Scheduler is initializing before VTAM.
Determine whether the problem can be fixed by reading the IBM manual Advanced
Communications Function for VTAM Programming. If the problem can be corrected, do so
and reactivate the session using the VARY command. For instance, if the error code and
feedback code indicate that the VTAM line is down, that incorrect setup has occurred, or
the APPLID or NODE ID is not correctly defined, correct the error and use the VARY
command to reactivate the session.

1.2 CACM Messages
CACM081 –CACM085
CACM081 SCHEDULER VTAM SHUTDOWN IN PROGRESS

Explanation: Scheduler VTAM is shutting down in response to a request to terminate
Unicenter CA-Scheduler or in response to the VARY INACT command.
CACM082 SCHEDULER SESSION END xxxxxxxx yyyyyyyyyy

Explanation: This indicates that the Scheduler session for APPLID xxxxxxxx has ended.
This message is a normal response to the VARY INACT command, or when Unicenter
CA-Scheduler is shutting down on another node and the VTAM session is disconnecting,
or if there is a problem on the other node, such as a VTAM line going down.
yyyyyyyyyy indicates that an error condition has occurred.
User Response: If the message is issued in response to a VARY INACT command, or
Unicenter CA-Scheduler shutting down at another node, correct the problem at the other
node and use the VARY command to reactivate the session. If an error condition has
occurred, look for message CACM080, which should accompany this message, and follow
the instructions under that message.
CACM083 SCHEDULER SESSION START xxxxxxxx yyyyyyyyyy

Explanation: This indicates that the Unicenter CA-Scheduler session for APPLID
xxxxxxxx has started. This message is a normal response to the VARY ACTIVE
command, or when Unicenter CA-Scheduler is starting up on another node and the
VTAM session is connecting. yyyyyyyyyy indicates that an error condition has occurred.
User Response: If the message is issued in response to a VARY ACTIVE command, or
Unicenter CA-Scheduler starting up at another node, no action is required. If an error
condition has occurred, look for message CACM080, which should accompany this
message, and follow the instructions under that message.
CACM084 VTAM MACRO ERROR ppppppp aaaaaaaa majorerr minorerr R15=xx

R0=xx tttttt
Explanation: This indicates that a VTAM macro error has occurred in program
pppppppp for APPLID aaaaaaaa with a Major Error of majorerr and a Minor Error of
minorerr. R15 and R0 are registers 15 and 0 returned from the VTAM macro and tttttt
indicates the macro where the error occurred or the type of error that occurred. This is a
normal message in response to a failure at another node.
User Response: Check the IBM Manual Advanced Communications Function for VTAM
Programming to determine if the error is occurring at this node or at another node. If the
error is occurring at another node, determine the failure and correct the problem at the
other node. No action is required at this system. If the error is due to errors on this node,
contact Computer Associates Technical Support, as this may indicate internal problems.
CACM085 LOGON PROCEEDING FOR APPL=aaaaaaaa

Explanation: The specified VTAM APPLID is in the process of establishing a session.

1.2 CACM Messages
CACM086 –CACM098
CACM086 aaaaaaaa APPLID FAILED ON SEND/RECEIVE OPERATION - pppppppp

Explanation: This indicates that there is a problem with APPLID aaaaaaaa in program
pppppppp at another node due to a failed SEND or RECEIVE operation.
User Response: Correct the problem at the other node.
CACM087 VTAM NETWORK TABLE ERROR FOR APPL=aaaaaaaa

Explanation: The VTAM APPLID does not match the APPLID specified in CAIJNET.
The same CAIJNET must be used by all nodes in the network.
User Response: Make sure that all nodes are using the same CAIJNET.
CACM088 xxxxxxxxxx INVALID FOR APPL=aaaaaaaa eeeeeeee nnnnnnnnnnnnnnnnnn

Explanation: This indicates that the xxxxxxxxxx (VARY ACT or VARY INACTIVE)
command is invalid for APPLID aaaaaaaa. eeeeeeee indicates the error type, and
nnnnnnnnnn indicates the current status of the APPLID.
User Response: Correct the invalid command and resubmit.
CACM089 VTAM/SCHEDULER ADAPTER ERROR: RTC=xx

Explanation: An unrecoverable error occurred from the ADAPTER.
CACM092 AUTOSCAN TIME INVALID RELATIVE TIME VALUE

Explanation: An invalid RELATIVE TIME value was given. RELATIVE TIME should be
specified in the format nnx where nn is the number of hours difference (01 to 23) and x is
either plus (+ ahead) or minus (-behind) the data center's local time.
User Response: Correct the RELATIVE TIME value and resubmit.
CACM096 WRONG ECB POSTED FOR COMMAND

Explanation: The wrong routine in Monitor was requested to respond to a particular
command. There is an internal error.
CACM097 SCHEDULER MONITOR TERMINATED

Explanation: Monitor has terminated in response to a request for it to do so.
User Response: Reinitialize Monitor whenever it is appropriate to do so.
CACM098 NO MORE DYNAMIC STORAGE AVAILABLE, PROGRAM TERMINATED

Explanation: A dynamic request for storage failed. The DJOB value specified in the
CAIJGEN macro may be inappropriate. The higher the value of DJOB, the more virtual
storage is required.
If the message appears during AUTOSCAN, auto recovery, or daily processing (for
example, after a RUN command), then one or both of the following reasons may apply:

1.2 CACM Messages
CACM099 –CACM106
■ the DJOB value is too low

■ storage is insufficient
If the message appears during Unicenter CA-Scheduler monitor initialization (prior to
AUTOSCAN or auto recovery messages), then storage is insufficient. (In addition, the
value of DJOB may be too high.)
User Response: Adjust the value of DJOB and/or increase the storage available to
satisfy the request. (If the value of DJOB is adjusted, the storage may have to be
increased as well.) For storage guidelines, see the Unicenter CA-Scheduler Installation
Guide. For an explanation of DJOB, see the Unicenter CA-Scheduler Systems Programmer
Guide.
CACM099 ERROR CODE = zzyy aaaa dddddddd rrrr xxxx

Explanation: An unrecoverable error has occurred within the Unicenter CA-Scheduler
Monitor during processing. The characters stand for:
aaaa 4-character suffix identifying the module producing the error.
dddddddd ddname/dtfname of the file causing the problem.
rrrr logical record being processed.
xxxx key of record being processed, variable length.
zzyy 4-digit error code.
For a description of the codes, see the chapter "Catalog Management Return Codes" in
the CA Common Services Message Guide..
User Response: In all cases except for 080C, contact Computer Associates Technical
Support with these details. If 080C errors persist after increasing storage, then contact
Computer Associates Technical Support for help. Certain preventive and corrective
measures can be taken using the above information that will allow the Unicenter
CA-Scheduler Monitor to be brought up and most of the production schedule run. RRRR
and XXXX will identify the record causing the problem. Check the definitions using the
online utility. Deleting and re-adding the record may avoid the problem. Also, try taking
the affected schedule/job out of the day's workload. If this happened when a RUN
Schedule or Job command was issued, do not use that command with the schedule/job
until the problem has been fixed.
CACM105 TRACKING FILE CLEAN UP IN PROGRESS

Explanation: The tracking file is being cleaned up before an autoscan. Clean up involves
backlogging and purging schedules and jobs.
CACM106 TRACKING FILE CLEAN UP COMPLETED

Explanation: The tracking file clean up is completed and autoscan can begin.

1.2 CACM Messages
CACM107 –CACM113
CACM107 TRACKING FILE ACCESS ERROR

Explanation: An I/O error has occurred accessing the tracking file.
User Response: Check your JCL for the DLBL statement for CAIJTRK. Ensure that it
points to the correct data set name.
CACM108 INVALID RANGE USE 800:899

Explanation: An invalid MNO value was specified. All user message numbers specified
by the MNO keyword must be between 800 and 899.
User Response: Correct the MNO value to be between 800 and 899 and resubmit.
CACM109 IMMEDIATE MANUAL AUTOSCAN REQUESTED, REPLY OK|TERM

nnn+/- CHANGE OF AUTOSCAN REQUESTED, REPLY OK|TERM
Explanation: The AUTOSCAN command has been issued.
User Response: Reply OK to do the autoscan, or reply TERM to cancel the AUTOSCAN
command request.
CACM110 POST xxx NO LOCAL SUCCESSOR FOUND

Explanation: A POST command was issued, but no successors waiting for the event
were found on the local node.
User Response: Check for spelling errors if there were successors waiting for that event.
CACM111 FORCE xxxx NOT FORCIBLE

Explanation: The current job or the schedule status does not allow the FORCE
command.
User Response: Make sure that you are forcing the correct job or schedule, or use the
RUN, RERUN, or SUBMIT commands.
CACM112 TALTER xxxx NOT ALLOWED FOR STAGED JOBS

Explanation: The TALTER command was issued to alter LIBTYPE and the JCL for the
job has been staged previously.
User Response: Cancel, purge, and dynamically add the job with a new LIBTYPE.
CACM113 AUTO RECOVERY IN PROGRESS FOR SYSID xxxx

Explanation: This informational message indicates that Unicenter CA-Scheduler is in the
process of automatic recovery at initialization time.

1.2 CACM Messages
CACM114 –CACM203
CACM114 INVALID n SYSID, NOT IN CAIJGEN LIST

Explanation: An attempt was made to process a job whose SYSID does not match any of
the values specified in the CAIJGEN macro.
User Response: ALTER the JBR to correct the job's SYSID, or have your systems
personnel add the SYSID to the CAIJGEN options and reassemble the macro.
CACM115 CALENDAR xxxxxxxx FOR YEAR nn MONTH nn IS NOT DEFINED

DATETABLE xxxxxxxx FOR YEAR nn MONTH nn IS NOT DEFINED
Explanation: During AUTOSCAN, Monitor encountered a job or schedule record which
refers to a calendar or date table that cannot be located.
User Response: Alter the JBR or SBR, or define the calendar or date table.
CACM116 command object nnnnnnnn DONE

Explanation: The command 'command' has been executed.
User Response: None required. Informational message. Correct the ddname and
resubmit.
CACM129 INITIALIZATION PARMS ERROR - MONITOR TERMINATING

Explanation: Unicenter CA-Scheduler has found errors in the parameters specified at
initialization.
User Response: Restart Unicenter CA-Scheduler with the correct parameters.
CACM200 *** CA-SCHEDULER MONITOR IS ACTIVE ALREADY ***

Explanation: The Unicenter CA-Scheduler Monitor component is active and operating.
User Response: None, unless you are sure that the Unicenter CA-Scheduler monitor is
not active. See the topic Handling Abends in the chapter "Performance Considerations"
in the Unicenter CA-Scheduler VSE Systems Programmer Guide..
CACM201 SCHEDULER COMMAND PROCESSOR BUSY

Explanation: Another command is being processed at this moment.
User Response: Reenter the command.
CACM202 *** POWER IS NOT ACTIVE ***

Explanation: Initialization has been attempted while VSE/POWER was not active.
User Response: Initialize VSE/POWER and run CAJMINTA.
CACM203 SCHEDULER STATUS PROCESSOR BUSY

Explanation: Another command is being processed at this moment.
User Response: Reenter the command.

1.2 CACM Messages
CACM204 –CACM209
CACM204 PHASE xxxxxxxx CANNOT BE LOCATED. INITIALIZATION TERMINATED

Explanation: A required Monitor phase cannot be found. The LIBDEF is incorrect or the
phase has been deleted from the core library.
User Response: Check the partition JCL LIBDEF statements for the correct core image
(CL) search chain in that partition.
CACM205 UNABLE TO PAGE FIX REQUIRED STORAGE R/C=n

Explanation: There is insufficient real storage allocated to the partition in which
initialization is running.
User Response: See the PFIX Macro in the DOS/VSE Advance Function Macro Reference
Guide for the return code indicated.
CACM206 CA-SCHEDULER xxxxxxxx FILE IS NOT AVAILABLE.

Explanation: The jobmaster database, tracking file documentation file, or staging file
cannot be found (Monitor will not initialize). The file has not been formatted or is not
assigned in the partition, or DLBL/EXTENTs are not in system standard labels, or the file
has been physically destroyed.
User Response: Make sure that the catalogs are formatted and that labels are available
in the partition. If the file has been destroyed, restore the latest backup tape and
manually recover any changes made since the backup.
CACM207 CA-SCHEDULER MONITOR ATTACH FAILED R/C=n

Explanation: Monitor cannot be attached to POWER.
User Response: See the ATTACH Macro in the DOS/VSE Advance Function Macro
Reference Guide for the return code indicated.
CACM208 GETVIS FOR WORK AREAS UNSUCCESSFUL

Explanation: The initialization partition does not have sufficient GETVIS storage to
support Unicenter CA-Scheduler.
User Response: Allocate more storage and run CAJMINTA.
CACM209 CA-SCHEDULER IS NOT ACTIVE. STARTUP TERMINATED

Explanation: Unicenter CA-Scheduler was not installed properly. Either the library was
not in the LIBDEF search string at the time CASAUTIL was executed, or the product has
been disabled.
User Response: Put the library in the search string and reexecute CASAUTIL or enable
product.

1.2 CACM Messages
CACM210 –CACM215
CACM210 INSUFFICIENT GETVIS IN POWER PARTITION

INSUFFICIENT GETVIS IN POWER PARTITION nnnnK ADDITIONAL REQUIRED
Explanation: The POWER partition does not have sufficient partition GETVIS storage to
support Unicenter CA-Scheduler.
User Response: Allocate more partition GETVIS storage in the POWER partition, or, if
virtual storage is sufficient, execute POWER with a size parameter. Run CAJMINTA.
CACM211 PHASE mmmmmmmm CANNOT BE LOCATED. xxxxxxxx SUPPORT RESET.

Explanation: The CAIJGEN options designate the presence of the xxxxxxxx library type
(for example, PANVALET), but the mmmmmmmm phase which supports this function
was not generated at Unicenter CA-Scheduler installation time.
User Response: Monitor will proceed as if this library type were not designated in the
CAIJGEN options. Therefore, ignore this message if it is not required. If it is required,
link edit the phase. (See the Unicenter CA-Scheduler Installation Guide.)
CACM212 SHARE GENERATION OPTION AND SHARED FILE OPTION DISAGREE FOR
xxxxxxxx FILE
Explanation: The CAIJGEN SHARE option does not agree with the SHARE option
specified when this file was formatted.
User Response: Correct the CAIJGEN macro or reformat the file by executing CAJUTIL0
with the FORMAT command.
CACM213 SCHEDULER xxxxxxxx FILE IS LOCKED REPLY RETRY OR CANCEL

Explanation: One of the Unicenter CA-Scheduler files was enqueued, even after waiting
for a reasonable period of time. The console operator is asked if continued attempts to
access the database are warranted. If not, Monitor will be terminated.
User Response: Try to determine who owns the enqueue. If you reply RETRY, an
attempt is made to obtain the enqueue again. The attempt will be successful provided the
previous owner has released the enqueue. If you reply CANCEL, Unicenter CA-Scheduler
Monitor is terminated.
CACM214 INVALID VERSION (v.m) OF CAJAGENA

Explanation: An invalid version of CAJAGENA was found in the library chain searched
by CASAUTIL.
User Response: Delete CAJAGENA phase and reassemble the CAIJGEN macro.
CACM215 SUPERVISOR DOES NOT CONTAIN JA SUPPORT. RUN CANCELED

Explanation: The DOS/VSE Supervisor was generated without job accounting support.
User Response: Regenerate the Supervisor with job accounting support.

1.2 CACM Messages
CACM216 –CACM220
CACM216 DRIVER SUB-SYSTEM PHASE xxxxxxxx NOT FOUND.

Explanation: A required Monitor phase cannot be found. The LIBDEF is incorrect or the
phase has been deleted from the core library.
CACM217 DRIVER SUB-SYSTEM PHASE xxxxxxxx MUST BE SVA RES.

Explanation: A required Unicenter CA-Driver phase was not loaded into the SVA.
User Response: No SDL entries are required for Unicenter CA-Driver.
CACM218 DRIVER SUB-SYSTEM PHASE xxxxxxxx MUST NOT BE SVA RES.

Explanation: This Unicenter CA-Driver phase was loaded into the SVA.
User Response: No SDL entries are required for Unicenter CA-Driver.
CACM219 CATALOG ACCESS ERROR OCCURRED F/C=n A/C=n R/C=n

Explanation: During roll call for required startup files, a record was not found for a file.
This means that this file is not accessible by the users of the access method. Possible
causes are:
■ The file is allocated but not formatted.
■ The file migrated, but the Adapter was not brought down and up again.
■ There is not enough storage for the catalog management buffers.
If this message is displayed with F/C=04, A/C=04, and R/C=041C, this could mean that
the user has assembled 'CAJAGENA' as part of the installation procedure. Even though
the assembly is correct and causes no errors, a 'STDOPT' of 'NOALIGN' causes a
mapping (DSECT) problem between the generated code and what the programs expect.
User Response: In general, you should:
1. Bring the Adapter down and up again to ensure that it points to the correct file.
2. Make sure that enough storage is available - CAJAGENx (xxxBUFN * xxxCISZ) for
the file in error. Increase the partition by this amount.
3. If you are sure you have enough storage, and the Adapter points to the correct file,
you may assume that the file has been destroyed, and must be reformatted.
If this message is displayed with F/C=04, A/C=04, and R/C=041C, insert a '// OPTION
ALIGN' JCL statement within the assembly JCL of CAJAGENA. Reassemble and relink
the phase, then IPL.
CACM220 SAVER ERROR OCCURRED R/C=n

Explanation: An internal logic error occurred.

1.2 CACM Messages
CACM221 –CACM228E
CACM221 CA-SCHEDULER ATTACH FAILED R/C=n, SUPPORT RESET.

Explanation: Could not attach CMS reader or multiple CPU subtask.
User Response: See the ATTACH Macro in the DOS/VSE Advance Function Macro
Reference Guide for the return code indicated.
CACM222 INSUFFICIENT STORAGE FOR PARTITION CONTROL BLOCKS.

Explanation: The SVA does not have sufficient GETVIS storage to support Unicenter
CA-Scheduler.
User Response: Allocate more SVA.
CACM223 CARCTBL0 HAS NOT BEEN LOADED IN THE SVA

Explanation: Phase not included in the SET SDL.
User Response: Run SET SDL for this phase.
CACM225 Unicenter CA-Scheduler xxxxxxxx PROGRAM LOAD ERROR RC=nn

Explanation: The Unicenter CA-Scheduler initialization program issued a CDLOAD for
the program xxxxxxxx and received return code nn. This message usually means that
either the program cannot be found within the libraries mentioned in the LIBDEF, or
there is not enough GETVIS available to load the program.
User Response: For return codes from the CDLOAD macro, see the DOS/VSE Macro
Reference Guide.
CACM226 XPOST XECB ERROR RC=nn

Explanation: An error occurred during Unicenter CA-Scheduler initialization.
User Response: Check the DOS/VSE Macro Reference Guide for return codes from the
XPOST macro. If you require further assistance, contact Computer Associates Technical
Support.
CACM227E CA-SCHEDULER INITIALIZATION HAS ABENDED

Explanation: A program check occurred during Unicenter CA-Scheduler initialization.
CACM228E CANNOT LOCATE SCHEDULER INIT XECB

Explanation: Unicenter CA-Scheduler cannot locate the initialization XECB.
User Response: Make sure that CASAUTIL was executed before POWER, and that
OPEN intercepts have not been disabled in the POWER partition.

1.2 CACM Messages
CACM229E –CACM290E
CACM229E CA-SCHEDULER INITIALIZATION XPCC ERROR OCCURRED F/C=nn R/C=nn,nnnn

Explanation: An error occurred during Unicenter CA-Scheduler initialization.
User Response: Make sure that CASAUTIL was executed before POWER, and that
OPEN intercepts have not been disabled in the POWER partition. If you require further
assistance, contact Computer Associates Technical Support.
CACM230D ENTER COMMAND OR EOB FOR NORMAL INITIALIZATION

Explanation: UPSI 01 has been specified for CAJMINTA.
User Response: See the topic Handling Abends in the chapter "Performance
Considerations" in the Unicenter CA-Scheduler Systems Programmer Guide..
CACM231 CA-SCHEDULER AUTO-REPLY INITIALIZATION FAILED

Explanation: The AUTOMATIC CONSOLE REPLY facility was unable to successfully
complete its initialization.
CACM232 CA-SCHEDULER AUTO-REPLY SUPPORT IS ACTIVE

Explanation: The AUTOMATIC CONSOLE REPLY facility was successfully initialized.
User Response: None required. Informational message.
CACM233 CA-SCHEDULER AUDIT TASK INITIALIZATION FAILED

Explanation: The AUDIT facility was unable to successfully complete its initialization.
CACM234 CA-SCHEDULER AUDIT SUPPORT IS ACTIVE

Explanation: The AUDIT facility was successfully initialized.
CACM235 PRODUCT NOT INSTALLED OR NOT SUPPORTED IN THIS ENVIRONMENT

Explanation: Unicenter CA-Scheduler VSE ESA feature is needed for VSE/ESA
exploitation.
User Response: Resubmit the command with a valid command parameter.
Note: As of Service Pack 3, the ESA options feature is included with the base version of
the product. Upgrade to Service Pack 3 or higher to implement ESA options.
CACM290E INVALID SCHEDULER COMMAND PARAMETER SPECIFIED

Explanation: An invalid Unicenter CA-Scheduler command was issued.
User Response: Resubmit the command with a valid command parameter.

1.2 CACM Messages
CACM291 –CACM405
CACM291 COMMAND SUBMISSION CANCELLED.

Explanation: The processor is busy.
User Response: Reenter the command later.
CACM293 CONTINUE COMMAND:

Explanation: The previous entry, a comma, indicated a continuation was to follow.
User Response: Continue entering command operands.
CACM400 REPLY OK OR TERM

Explanation: Requests the console operator to respond to the displayed memo which
was defined for the job.
User Response: Reply OK to allow the job to proceed, or TERM to interrupt the job
startup process.
CACM401 SCEND CARD ENCOUNTERED WITH NO MATCHING SCSTART CARD

Explanation: A Unicenter CA-Scheduler SCEND statement was found in job steps
without a correct Unicenter CA-Scheduler SCSTART statement.
CACM402 SYSTEM ADAPTER ERROR OCCURRED F/C=function R/C=rr

Explanation: A call to a system adapter function produced a non-zero return code.
CACM403 TRACKING FILE I/O ERROR OCCURRED R/C=rrrrrrrr F/C=ff A/C=aa

Explanation: An I/O error occurred while trying to access the TRACKING FILE.
CACM404 TRACKING FILE NO RECORD FOUND

Explanation: A matching tracking file record was not found for a Unicenter
CA-Scheduler controlled job.
CACM405 INSUFFICIENT STORAGE FOR $$JOBEXIT/CAJIJXTA'

INSUFFICIENT STORAGE FOR $$JOBACCT/CAJIACTA'
INSUFFICIENT STORAGE FOR $$BCLOSE/CAJICLSA'
Explanation: The job exit, accounting, or data set close intercept could not get sufficient
storage for its work area.
User Response: Increase Partition GETVIS and resubmit.

1.2 CACM Messages
CACM406 –CACM553E
CACM406 Unicenter CA-Scheduler xxxxx PROGRAM LOAD ERROR. R/C=rr

Explanation: Initialization error.
User Response: Look up the return code in the DOS/VSE Advanced Function Macro
Reference Guide.. Find the error codes listed for the CDLOAD macro and take the
appropriate action.
CACM407 POWER COMMAND FAILURE COMMAND=xxxxxxx. R/C=rr

Explanation: There is an error in this command.
CACM408 HOLD READER QUEUE COMMAND HAS BEEN ISSUED

Explanation: Unicenter CA-Scheduler is coming up in recovery mode.
CACM409 CA-SCHEDULER INITIALIZATION JOB xxxxxxxx NOT FOUND IN RDR QUEUE.

ENTER NEW JOB NAME OR EOB.
Explanation: The job specified in the PARTJOB option of the CAIJGEN macro cannot be
found.
User Response: Enter a new name or press EOB to continue without automatic
initialization of Monitor.
CACM410E ERROR FROM APPENDAGE ROUTINE

Explanation: The power interface has detected an error.
CACM411E ERROR FROM GETSPOOL

Explanation: The power interface has detected an error.
CACM551E xxxx...SYNTAX ERROR IN FUNCTION CALL

Explanation: Invalid syntax in function call.
CACM553E xxxxxxxxx...FUNCTION CALL IS UNDEFINED

Explanation: Job not submitted through Unicenter CA-Scheduler.
User Response: Resubmit job through Unicenter CA-Scheduler.

1.2 CACM Messages
CACM556E xxxx nth ARGUMENT IS MISSING

Explanation: Missing required argument.
CACM600 NETWORK SUPPORT IS NOT GENERATED

Explanation: NJE=NO in CAIJGEN macro.
CACM600E GLOBAL AREA NOT FOUND

Explanation: Unicenter CA-Scheduler and Unicenter CA-Driver are not communicating.
User Response: Verify the installation of Unicenter CA-Scheduler. If problem persists,
contact Computer Associates Technical Support.
CACM601E NO STORAGE AVAILABLE

Explanation: An error was detected during an attempt to acquire storage for processing
of a Unicenter CA-Scheduler/Unicenter CA-Driver function.
User Response: Try increasing partition GETVIS. If the problem persists, contact
Computer Associates Technical Support.
CACM602E xxxxxxxx - IS AN UNKNOWN SCHEDULER FUNCTION

Explanation: The specified function is not a valid Unicenter CA-Scheduler/Unicenter
CA-Driver function.
User Response: Correct the Unicenter CA-Driver procedure and rerun the job.
CACM603E xDATETAByyyy - DATE TABLE NOT FOUND

Explanation: Year being accessed for DATETAB with prefix x is missing at date table
defined for year yyyy.
User Response: Three years' worth of date tables must be defined for each unique date
table name. Correct and resubmit.
CACM604E CAM I/O ERROR WHILE READING DATE TABLE

Explanation: A logical I/O error was detected while reading the date table from the
master file.
User Response: REORG the master file. If the problem persists, contact Computer
Associates Technical Support.
CACM605E DATE TABLE OVERFLOW OR UNDERFLOW

Explanation: The function tried to go before the beginning or after the end of the date
table.
User Response: Define more date tables.

1.2 CACM Messages
CACM606E END OF PERIOD CAN NOT BE FOUND

Explanation: The function could not locate the end of the period in the date table.
User Response: Correct the date table.
CACM607E ILLEGAL CYCLE PREFIX OR PREFIX NOT SPECIFIED

Explanation: The date table prefix was omitted or an invalid prefix was specified for a
Date cycle function.
User Response: Specify a valid prefix and resubmit the job.
CACM608E NOT IN RANGE 1 TO 365/366

Explanation: Unicenter CA-Driver/Unicenter CA-Scheduler date functions have found
an error.
User Response: Correct error and rerun job.
CACM610E - RELATIVE DAY NOT NUMERIC

Explanation: The first parameter of a Unicenter CA-Scheduler/Unicenter CA-Driver
function is not numeric.
CACM611E VARIABLE NOT FOUND BY CA-DRIVER

Explanation: A variable substitution could not be made because the variable parameter
had not been defined.
User Response: Correct the Unicenter CA-Driver procedure to specify a DSET command
or a default value (on the PROC statement) and rerun the job.
CACM612E xxxxx - IS AN INVALID JULIAN DATE

Explanation: The second parameter of a Unicenter CA-Scheduler/Unicenter CA-Driver
function must be a valid five-character Julian date.
CACM613E INTERNAL ERROR IN DATE PROCESSING

Explanation: An error occurred in a date-processing function.
CACM614E ALLOWED RANGE IS 1-36600

Explanation: The first parameter of a date function is invalid.
User Response: Correct the parameter and resubmit.

1.2 CACM Messages
CACM615E ALLOWED RANGE IS 1-1200

CACM616E NOT A POSITIVE NUMERIC INTEGER

CACM620E ERROR DURING STORAGE ALLO/DEALLO

Explanation: An error was detected during an attempt to release storage after
processing a Unicenter CA-Scheduler/Unicenter CA-Driver function.
CACM650E VARIABLE UNDEFINED OR NULL VALUE

Explanation: A variable parameter used in a date function is undefined or null.
User Response: Check whether the correct parameter was specified and if so, whether a
value was assigned to it.
CACM651E ...SYNTAX ERROR IN FUNCTION CALL

Explanation: A date function was syntactically incorrect.
User Response: Correct the syntax and resubmit.
CACM652E ...LOAD FAILURE

Explanation: A program load failed.
User Response: Increase partition GETVIS and retry. Ensure that the Unicenter
CA-Scheduler library is included in the LIBDEF list.
CACM653E ...FUNCTION CALL IS UNDEFINED

Explanation: An invalid date function was specified.
User Response: Specify the correct date function and resubmit.
CACM654E ...ARGUMENT LENGTH ERROR

Explanation: The third parameter of a Unicenter CA-Scheduler/Unicenter CA-Driver
function is a date table, which is seven characters or fewer. Too many characters were
entered.

1.2 CACM Messages
CACM655E –CACM748I
CACM655E ...ARGUMENT MUST BE NUMERIC

Explanation: A non-numeric argument was specified in a date function.
User Response: Specify numeric arguments and retry.
CACM656E ARGUMENT IS MISSING

Explanation: A required argument is missing in a date function.
User Response: Specify all the required auguments for the invoked date functions and
resubmit.
CACM657E ...ARGUMENT MUST BE ALPHANUMERIC

Explanation: A non-alphanumeric argument was specified in a date function.
User Response: Specify alphanumeric arguments and retry.
CACM658E ...ARGUMENT MUST BE ALPHABETIC

Explanation: A non-alphabetic argument was specified in a date function.
User Response: Specify alphabetic arguments and retry.
CACM659E VARIABLE NAME IS INVALID

Explanation: An invalid variable parameter name was specified in a date function.
User Response: Specify a valid name and retry.
CACM660E RELATIVE DAY EXCEEDS MONTH RANGE

Explanation: The relative day argument in the date function is invalid for the specified
month.
User Response: Inspect the date function and correct the invalid argument (month or
relative day).
CACM747E CICS SHUTDOWN REQUEST INVALID FROM BATCH.

Explanation: The CAJUCMD0 program does not allow for CICS shutdown from batch.
CACM748I xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Explanation: The text shown in the message is the actual CI command being issued
from CAJUCMD0. It is only issued on SYSLOG and only if there are no syntax errors in
the CI command.

1.2 CACM Messages
CACM750 –CACM757
CACM750 CA-SCHEDULER MONITOR IS NOT ACTIVE. CAJUCMD0 CANCELED

Explanation: The Monitor was not active.
User Response: Bring up the Monitor.
CACM751 UNRECOGNIZABLE COMMAND

Explanation: An unrecognized command prefix was encountered.
CACM752 COMMAND IS TOO LONG FOR BUFFER.

Explanation: POWER or Unicenter CA-Scheduler command was too big to fit in the
buffer.
CACM753 ERROR OCCURRED IN SCHEDULER COMMAND EXECUTION R/C=nnnnnnnn

Explanation: The Unicenter CA-Scheduler command processor detected an
unrecoverable error.
CACM754 MACHINE MUST BE RUNNING UNDER VM CONTROL TO ENTER CP

COMMANDS.
Explanation: VM commands can only be issued in operating systems running under VM
control.
User Response: Do not use command unless running under VM.
CACM755 NO COMMAND WAS FOUND IN INPUT.

Explanation: No input.
CACM756 AN INVALID GLOBAL/SCHEDULE/JOB NAME HAS BEEN ENCOUNTERED

Explanation: When processing a Unicenter CA-Scheduler IF command, invalid input
was encountered.
CACM757 A DOUBLE NEGATIVE WAS FOUND ON SCHEDULER IF STATEMENT

Explanation: When processing a Unicenter CA-Scheduler IF command, a NOT followed
by another NOT was encountered.

1.2 CACM Messages
CACM758 –CACM764
CACM758 AN INVALID MAJOR CONDITION HAS BEEN ENCOUNTERED

Explanation: When processing a Unicenter CA-Scheduler IF command, an unrecognized
condition was encountered.
CACM759 AN INVALID MINOR CONDITION HAS BEEN ENCOUNTERED

Explanation: When processing a Unicenter CA-Scheduler IF command, an unrecognized
condition was encountered.
CACM760 AN AND/OR WAS EXPECTED AND NOT FOUND

Explanation: When processing a Unicenter CA-Scheduler IF command, an AND or OR
was expected but not found.
CACM761 UNRECOGNIZABLE OPERAND OR SYNTAX ERROR HAS OCCURRED ON A

SCHEDULER IF STATEMENT
was encountered.
CACM762 INCORRECT USAGE OF A KEYWORD/CONDITION HAS BEEN ENCOUNTERED

was encountered.
CACM763 SCHEDULE sname WAS NOT FOUND ON TRACKING FILE

Explanation: When processing a Unicenter CA-Scheduler IF command, a condition to a
schedule was encountered but the corresponding record on the tracking file could not be
located.
CACM764 JOB jname jno st sname WAS NOT FOUND ON TRACKING FILE
Explanation: When processing a Unicenter CA-Scheduler IF command, a condition to a
job was encountered but the corresponding record on the tracking file could not be
located.

1.2 CACM Messages
CACM765 –CACM773
CACM765 UTILITY IS NOT UNDER CA-SCHEDULER CONTROL.

Explanation: This program was not run as part of a job under Unicenter CA-Scheduler
control.
CACM766 COMMAND AUTHORIZATION LIST COULD NOT BE LOCATED

Explanation: The Unicenter CA-Scheduler Batch Command Processor could not locate
the list of valid commands.
User Response: Correct JCL and resubmit.
CACM767 COMMAND DISABLED BY DEFINITION

Explanation: The command you entered is not included on the command authorization
list, so it cannot be executed in batch mode.
User Response: Correct the command list or discontinue use of command.
CACM768 COMMAND DISABLED BY MASK SECURITY

Explanation: The command you entered is not included on the command authorization
list, so it cannot be executed in batch mode.
User Response: Correct the command list or discontinue use of command.
CACM769 TOO MANY CONTINUATION CARDS

Explanation: The command you entered spans more than 10 input statements.
CACM770 INSUFFICIENT STORAGE FOR COMMAND EXECUTION

Explanation: Insufficient storage.
CACM772 ERROR HAS OCCURRED DURING EXECUTION OF ABOVE COMMAND

R/C=nnnnnnnn
Explanation: An unrecoverable error has occurred.
CACM773 SCHEDULER STATUS PROCESSOR BUSY

Explanation: The Unicenter CA-Scheduler Batch Command Processor could not
communicate with the Unicenter CA-Scheduler Monitor Command Processor.
User Response: Resubmit.

1.2 CACM Messages
CACM774E –CACM781
CACM774E KEYWORD xxxxxxxx INVALID ON DM COMMAND

Explanation: An invalid keyword 'xxxxxxxx' was used on the CAJUCMD0 DM
command.
CACM775 SYSTEM ADAPTER ERROR OCCURRED FUNCTION=fname R/C=nn

Explanation: An unrecoverable error occurred.
CACM776 'USER TEXT'

Explanation: A Unicenter CA-Scheduler Batch Command Processor MO command was
encountered.
CACM777E OBJECT OF KEYWORD 'xxxxxxxx' INVALID ON DM COMMAND.

Explanation: The value given for keyword 'xxxxxxxx' is not valid for that keyword. This
message can occur as a result of an invalid DM or CI command in CAJUCMD0.
CACM778 MESSAGE TEXT IS TOO LONG TO DISPLAY.

Explanation: The message to be sent to the system operator is greater than 76 characters.
CACM779 CP HAS RETURNED MESSAGE DMKCFMnnn

Explanation: VM has returned an error condition.
User Response: Verify the error in the VM manual. Then correct and resubmit.
CACM780 SCHEDULER IF COMMAND IS FALSE

SCHEDULER IF COMMAND IS TRUE
Explanation: The result of a Batch Command Processor IF statement is shown.
CACM781 TRACKING FILE I/O ERROR OCCURRED R/C=nnnn,nnnnnnnnn F/C=nn A/C=nn

Explanation: An error has occurred while accessing the tracking file.
User Response: For an explanation of R/C=nnnn, see the chapter "Catalog Management
Return Codes" in the CA Common Services Message Guide.

1.2 CACM Messages
CACM783 –CACM793E
CACM783 COULDN'T LOCATE MAINLINE COMMAND PROCESSOR (CAJCCMD0)

Explanation: The Unicenter CA-Scheduler Batch Command Processor could not locate
its main processing phase.
User Response: Check LIBDEFs to ensure phase is accessible. Correct and resubmit.
CACM786E UNRECOGNIZABLE OPTION ON OPTION STATEMENT.

Explanation: The OPTION control statement for CAJUCMD0 contains an invalid
keyword.
CACM787E OBJECT OF OPTION STATEMENT 'xxxxxxxx' IS INVALID.

Explanation: The value given for keyword 'xxxxxxxx' on the OPTION control statement
for CAJUCMD0 is invalid.
CACM789E DOCUMENTATION MEMBER COULD NOT BE FOUND.

Explanation: The documentation member specified on the DM control statement for
CAJUCMD0 could not be located in the documentation file.
CACM791E INVALID OR MISSING TRANSACTION ID ON CI COMMAND

Explanation: The CICS transaction ID on the CI control statement for CAJUCMD0 is
either missing or is not valid for CICS.
CACM792E CANNOT LOCATE SPECIFIED CICS OR NO CICS ACTIVE

Explanation: The CAJUCMD0 program is attempting to issue a CICS command, but
cannot locate the CICS partition.
User Response: Ensure that CICS is active and that there are no errors in the
CAJUCMD0 CI commands being used.
CACM793E CA-SCHEDULER CICS TRANSACTION IS NOT ACTIVE.

Explanation: The CAJUCMD0 program cannot locate phase CAJOCCEA.
User Response: Ensure that Unicenter CA-Scheduler is up and running and that the
CICS startup includes the PLT for CAJOCCEA.

1.2 CACM Messages
CACM794E –CACM905
CACM794E INVALID TERM ADDRESS SPECIFIED.

TRANSACTION ID INVALID.
Explanation: Either the termid as specified in the CAJUCMD0 CI command is invalid or
the transaction ID is invalid.
CACM796E XPCC ERROR OCCURED FC=xx,R/C=xx,xxxx

Explanation: An XPCC error has occured while processing a CI command within
CAJUCMD0.
CACM798 xxxxxxxx REQUESTED POWER COMMAND=yyyyy...

Explanation: When an update type is encountered, a POWER command is issued from
the Scheduler POWER interface and this message is displayed on the console. xxxxxxxx
is the user ID issuing the POWER command, and yyyyy... is the POWER command
issued.
CACM799 MAX WAIT EXPIRED, COMMAND CANCELLED

Explanation: The Unicenter CA-Scheduler Monitor is not able to process the command
entered in the time specified.
User Response: Make sure that the Monitor is active, or increase the time specified in
the CMSMXWT parameter of the CAIJGEN macro, which is described in the Unicenter
CA-Scheduler Systems Programmer Guide..
CACM851E I/O ERROR R15=nn CC=nn ERROR=nn

Explanation: This message indicates that there are no records on the Unicenter
CA-Scheduler Autoreply database.
User Response: If you do not wish to use the Unicenter CA-Scheduler Autoreply
feature, set AUTRPYL=NO in the CAIGFEN macro; assemble, linkedit, and reload phase
CAJAGENA with the CASAUTIL program. Then reinitialize the Unicenter CA-Scheduler
monitor. To make use of this feature, add a record to the AUTOREPLY database online
or with CAJUTIL0, then reinitialize the Unicenter CA-Scheduler monitor.
CACM905 CAIAUDIT ERROR OCCURRED R/C='rrrr' LOGGING FAILED

Explanation: CAIAUDIT was unable to log the requested buffer. The record is lost.

1.2 CACM Messages
CACM994W –CACM999
CACM994W INTERNAL TRACE TURNED OFF - INCREASE DJOBS

Explanation: The storage set aside for tracking jobs in the Unicenter CA-Scheduler
address space has been used up. The storage for internal tracking has been freed, and
will be used for job tracking. The internal trace table is normally used only by Unicenter
CA-Scheduler support.
User Response: Increase the DJOB value on the CAIJGEN macro. See the chapter
"Installation Options" in the Unicenter CA-Scheduler Systems Programmer Guide..
CACM995 I/O ERROR ON TRACKING FILE FOR JOB jname

Explanation: An I/O error occurred while trying to access the tracking file for the
specified job. Unicenter CA-Scheduler may lose track of this job.
User Response: Manual posting or cancelling of the job is required if Unicenter
CA-Scheduler has lost track of the job. Contact Computer Associates Technical Support to
determine why the I/O error occurred.
CACM996 SCHEDULER'S MONITOR NOT ACTIVE NOW, COMMAND IGNORED

Explanation: Monitor was not up, was in the process of being brought up, or was in the
process of being brought down.
User Response: Reissue command when Monitor is fully up and running.
CACM997 CA-SCHEDULER xxxxxxxx SUBTASK IS SHUTTING DOWN

Explanation: The named subtask is shutting down.
CACM998 CA-SCHEDULER xxxxxxxx SUBTASK INITIALIZED AND ACTIVE

Explanation: The named subtask is initialized and is now active.
CACM999 CA-SCHEDULER xxxxxxxx SUBTASK ABENDED

Explanation: The named subtask has abended.

1.3 CACO Messages
CACO100E –CACO106E
1.3 CACO Messages

CACO100E CA-SCHEDULER PRODUCT TABLE NOT FOUND
Explanation: Unicenter CA-Scheduler was not initialized by System Adapter.
User Response: Add Unicenter CA-Scheduler to CASAUTIL initialization list.
CACO101E PRODUCT NOT INSTALLED OR NOT SUPPORTED IN THIS ENVIRONMENT

exploitation.
User Response: The ESA feature is required for VSE/ESA exploitation.
CACO102E DISPLAY KEY IS INVALID

Explanation: An invalid display key has been entered for a documentation member.
User Response: Reenter a valid key.
CACO103E CHANGE NOT VALID IN DISPLAY MODE

Explanation: A change request was attempted while in DISPLAY mode.
User Response: Enter change request from ALTER mode.
CACO104E DEFINE/COPY REQUIRES NEW NAME

Explanation: There are two possible reasons for this message:
1. A new member has been requested, but no new name has been supplied.
2. A documentation member is being edited and a DEFINE or COPY is issued.
User Response: There are two corresponding actions to the previous reasons:
1. Supply a new name and reissue the FILE/SAVE.
2. Supply the keys for the documentation member in the following order:
DSP-KEY (D=)
SCHEDULE NAME (S=)
JOB NAME (J=)
JOB NUMBER (JN=)
STATION NUMBER (ST=)
CACO106E INVALID KEYWORD

Explanation: A keyword parameter is invalid.
User Response: Correct the keyword parameter and reenter.

1.3 CACO Messages
CACO107E JOB NAME IS INVALID

Explanation: An invalid job name was entered.
User Response: Correct the job name and reenter.
CACO109E JOB NUMBER INVALID, MUST BE 01 TO 99

Explanation: The job number must be numeric, in the range of 01 to 99.
User Response: Correct the job number and reenter.
CACO112E SCHEDULE NAME IS INVALID

Explanation: An invalid schedule name was entered.
User Response: Correct the schedule name and reenter.
CACO113E STATION ID INVALID, MUST BE 01 TO 99

Explanation: The station ID must be numeric, in the range 01 to 99.
User Response: Correct the station ID and reenter.
CACO122E ALTER IS NOT ALLOWED

Explanation: An ALTER was attempted by a user without manager authority.
CACO124E AT LEAST 1 NAME PARAMETER REQUIRED

Explanation: The edited member does not have a name assigned to it.
User Response: Give the member a name and reissue the SAVE/FILE.
CACO131E BUFFER STORAGE REQUEST FAILED

Explanation: An attempt was made to acquire storage out of the SVA, and none was
available.
User Response: Contact your systems programmer to research and analyze the SVA
GETVIS storage.
CACO135E CATALOG CONTROL RECORD INDICATES NON-SHARED CATALOG

Explanation: The Unicenter CA-Scheduler system was generated with a non-shared
catalog. CMS requires a shared catalog.
User Response: To support CMS, the generation option must be changed.
CACO136E I/O ERROR R/C=xxxx,ccccxxxx F/C=xx A/C=xx xxx xxxxxxx

Explanation: An I/O error has occurred.
User Response: For an explanation of R/C=xxxx, see the chapter "Catalog Management
Return Codes" in the CA90s Services Message Guide..

1.3 CACO Messages
CACO139E CICS SUPPORT NOT GENERATED

Explanation: The generation parameters indicate that CICS support was not requested.
User Response: Contact your systems programmer to have the option changed.
CACO140E FUNCTION REQUIRES CALENDAR NAME

Explanation: A calendar name was not included with the request.
User Response: Request the function again, along with the calendar name.
CACO141E CREATE NOT ALLOWED

Explanation: A CREATE was attempted by a user without manager authority.
CACO143E DATA BUFFER TOO LARGE FOR ICCF REL 2

Explanation: The request to be passed to ICCF is too long.
User Response: Shorten the request.
CACO145E DATABASE LOCKED, PRESS ENTER TO RETRY

Explanation: The database is currently being accessed by another user.
User Response: Press ENTER to cause a retry of the access.
CACO146E DATETABLE ALREADY EXISTS

Explanation: An attempt has been made to CREATE a new date table with a name of an
existing date table.
CACO147E DEFINE NOT ALLOWED

Explanation: A DEFINE was attempted by a user without manager authority.
CACO148E DELETE IS NOT ALLOWED

Explanation: A DELETE was attempted by a user without manager authority.
CACO149E DELETE REQUIRES SCHEDULE NAME

Explanation: When deleting a job, the schedule name is required.
User Response: Resubmit the command with a schedule name.

1.3 CACO Messages
CACO150E ONLY YOUR OWN USERID CAN BE ALTERED

Explanation: You are only allowed to ALTER your own user ID.
CACO153E EDITOR NOT FOUND

Explanation: The Computer Associates editing system could not be loaded.
CACO154E ERROR DETECTED IN PROGRAM xxxxxxxx RC=xxxx CANNOT CONTINUE

Explanation: The listed program could not be invoked.
User Response: Check the install and contact Computer Associates Technical Support.
CACO155E ERROR TRYING TO ENQUEUE DATABASE

Explanation: An error occurred while trying to gain exclusive control of the master file.
User Response: Retry command. If the problem persists, contact Computer Associates
Technical Support.
CACO156E FILE COMMAND IGNORED FROM DISPLAY FUNCTION

Explanation: A FILE command requires UPDATE mode.
CACO157E xxx FOUND-REQUEST CHANGED TO ALTER

Explanation: A DEFINE request was made for an existing record type.
CACO160E FUNCTION NOT ALLOWED FOR THIS USERID

Explanation: A function was entered which is not valid for the current user ID.
CACO161E FUNCTION REQUIRES JOB NAME

Explanation: This function requires the inclusion of the job name.
User Response: Request the function again, along with the job name.
CACO162E FUNCTION REQUIRES SCHEDULE NAME

Explanation: This function requires the inclusion of the schedule name.
User Response: Request the function again, along with the schedule name.

1.3 CACO Messages
CACO163E JOB INFORMATION INCOMPLETE - REENTER

Explanation: This function requires the job name, job number, and schedule name.
User Response: Complete the required information and reenter.
CACO164E GENERATION PARAMETERS INDICATE NON-SHARED CATALOG

SHARED CATALOG REQUIRED FOR CMS, CANNOT CONTINUE
Explanation: The Unicenter CA-Scheduler system was generated with a non-shared
catalog. CMS requires a shared catalog.
User Response: To support CMS, the generation option must be changed.
CACO170E INVALID COMMAND

Explanation: An unacceptable or invalid command was entered.
User Response: Correct and reenter the command. If the problem persists, contact
CACO171E INVALID COMMAND MODIFICATION

Explanation: The attempted command modification is invalid where entered.
User Response: Enter the command modification from the correct screen.
CACO172E INVALID COMMAND OR FUNCTION REQUESTED

Explanation: An invalid command or function was entered.
User Response: Correct and reenter.
CACO173E INVALID CONNECT STATION

Explanation: An invalid station ID was entered.
CACO174E INVALID PROTOTYPE NAME, YEAR NOT NUMERIC

Explanation: The prototype calendar name does not end with a valid two-character
year.
User Response: Correct and reenter the prototype name.
CACO175E INVALID RECORD TYPE - REENTER

Explanation: An ALTER request has been issued for an invalid record type.
CACO176E INVALID SCHEDULER COMMAND

Explanation: An unacceptable or invalid command was entered.
User Response: Correct and reenter the command.

1.3 CACO Messages
CACO177E JOB NOT FOUND - REENTER

Explanation: Either an invalid job name was entered or the job was not found on the
tracking file.
CACO181E LOGON DENIED BY USER SECURITY EXIT-1

Explanation: The logon was denied by a user security exit.
CACO182E MASTER USERID CANNOT BE DELETED

Explanation: The master user ID must not be deleted.
CACO183I MESSAGE FOR JOB=xxxxxxxx IN SCHEDULE:xxxxxxxx AT STATION:xx

Explanation: A message has been issued for the named job.
CACO184I MESSAGE FOR SCHEDULE=xxxxxxxx

Explanation: A message has been issued for the named schedule.
CACO185E FUNCTION REQUIRES UPDATE MODE

Explanation: A function requiring an UPDATE was issued while in DISPLAY mode.
User Response: Log on with a write password and retry the function.
CACO186I MSG FROM USER:xxxxxxxx

Explanation: A message from a user ID has been received.
CACO187I NAME CHANGED

Explanation: The requested name change has been completed.
CACO188E NEW MEMBER ALREADY EXISTS - NAME MUST BE CHANGED

Explanation: The requested name change is to an existing member.
User Response: Give the member a new name and reissue the SAVE/FILE.

1.3 CACO Messages
CACO189E NEW NAMES NOT ALLOWED FOR STAGING

Explanation: The name of a member in the staging library cannot be changed.
CACO190I NO MESSAGES FOR USER:xxxxxxxx

Explanation: There are no messages for the specified user ID.
CACO192E NOT AUTHORIZED FOR REQUESTED STATION

Explanation: The user attempted to connect to a station for which the user ID is not
authorized.
CACO196E PUN INCORRECTLY SPOOLED TO USERID=xxxxxxxx

Explanation: The CMS transaction has attempted to spool the punch to an incorrect user
ID.
CACO197E PASSWORD REQUIRED ENTER USERID,PASSWORD

Explanation: This function requires a user ID and password.
User Response: Reenter with the correct user ID and password.
CACO198E PASSWORD REQUIRED ENTER WORKSTN,PASSWORD

Explanation: This function requires a work station number and password.
User Response: Reenter the correct work station number and password.
CACO199E PASSWORD VERIFICATION FAILURE

Explanation: The password is incorrect.
User Response: Enter the correct password.
CACO200I POWER INTERFACE DISABLED

Explanation: The generation parameters indicate that POWER support was not
requested.
User Response: Contact your systems programmer to have the option changed.
CACO203E RC=xx AUTHORIZE FAILED

Explanation: The CMS transaction attempted to establish connection to the Unicenter
CA-Scheduler system but has received an error from VM.

1.3 CACO Messages
CACO204E RC=xx CLOSE PUN FAILED

Explanation: The CMS transaction has attempted to close the punch file and VM has
returned an error.
CACO205E RECEIVING SYSTEM xxxxxxxx NOT LOGGED on

Explanation: The CMS transaction has attempted to spool the punch to user ID
xxxxxxxx and the user ID is not logged on.
User Response: Bring up the indicated system.
CACO206I REPORT WORK FILE IN USE - RETRY LATER

Explanation: The report work file is being used by another task.
User Response: Try again later.
CACO207E MEMBER CURRENTLY IN USE

Explanation: The member is currently in use by another task.
User Response: Try again later. Someone may be altering the record. If no one is
accessing the criteria record, issue an RCR command next to the job base record or an R
next to the documentation record or the staged record.
CACO208E REQUESTED MEMBER DOES NOT EXIST

Explanation: The member requested does not exist.
User Response: Recheck the name requested or display the directory for the correct
name.
CACO209E REQUESTED MEMBER HAS BEEN DELETED

Explanation: The member requested has been deleted.
CACO210E RESOURCE NOT FOUND - REENTER

Explanation: A request for a nonexistent resource was entered.
User Response: Correct the resource number and reenter.
CACO212E CA-SCHEDULER POWER INTERFACE CANNOT BE LOCATED

Explanation: This is an installation problem.

1.3 CACO Messages
CACO213E SCHEDULE NOT FOUND - REENTER

Explanation: A request for a nonexistent schedule was entered.
User Response: Correct the name and reenter.
CACO215E SCHEDULER OPTIONS TABLE (IE CAIJGEN MACRO ASSEMBLY)

CANNOT BE LOCATED,CANNOT CONTINUE.
Explanation: Unicenter CA-Scheduler cannot determine the location of the required
resource.
User Response: Contact your systems programmer.
CACO216I SCHEDULER PARAMETERS HAVE BEEN UPDATED,

MONITOR SHUTDOWN REQUIRED
Explanation: Unicenter CA-Scheduler parameters have been changed, but will not be
put into effect until the Unicenter CA-Scheduler Monitor has been recycled.
User Response: Shutdown and restart the Unicenter CA-Scheduler Monitor.
CACO218E SCHEDULER MONITOR NOT ACTIVE.

Explanation: A command requiring the monitor has been issued while the monitor is
not active.
User Response: Activate the monitor and reissue the command. If the monitor is active,
see the topic Handling Abends in the chapter "Performance Considerations" in the
Unicenter CA-Scheduler Systems Programmer Guide..
CACO220E STATION ID NOT NUMERIC

Explanation: A nonnumeric station ID was entered.
CACO222E STATION NOT FOUND

Explanation: The requested station was not found.
User Response: Check the work station directory to find the correct station number and
reenter.
CACO223I STATUS FROM NODE:xxxxxxxx

Explanation: A status from the specified node has been received.
CACO225E UPDATE DISABLED FOR ALL BUT MASTER-READ ONLY

Explanation: Only the master user ID is allowed to make online updates.

1.3 CACO Messages
CACO226E –CACO238I
CACO226E USER NOT AUTHORIZED FOR THIS JOB

Explanation: This user is not authorized to DISPLAY or ALTER the specified job.
CACO228E USER NOT AUTHORIZED FOR REQUESTED STATION

Explanation: This user is not authorized to connect to the specified station.
CACO229E USER NOT AUTHORIZED FOR THIS SCHEDULE

Explanation: This user is not authorized to DISPLAY or ALTER the specified schedule.
CACO233E USER NOT CONNECTED TO JCL STAGING STATION

Explanation: The user attempted to access the staging station without being connected
to it.
CACO234E USERID ALREADY LOGGED on

Explanation: The user attempted to log on to a user ID which is currently in use.
User Response: Check whether user is signed on elsewhere. If not, issue the F,user ID
command.
CACO235I USERID HAS NO WRITE PASSWORD-READ ONLY

Explanation: The user ID is authorized for read access only.
CACO236E DRIVER SUPPORT IS NOT GENERATED

Explanation: DRIVER=NO in CAIJGEN macro.
CACO237E USERID NOT FOUND

Explanation: The user ID entered is invalid.
CACO238I WRITE PASSWORD VERIFICATION FAILED-READ ONLY

Explanation: The write password is invalid.

1.3 CACO Messages
CACO239E XECB DEFINITION ERROR

Explanation: An XECB (cross partition communication) definition function has failed.
CACO240E XECB DELETE FAILED

Explanation: An XECB (cross partition communication) delete function has failed.
CACO241E XWAIT FAILED

Explanation: An XECB (cross partition communication) wait function has failed.
CACO246I xxxxxxxx REQUESTED POWER COMMAND=

Explanation: The POWER command from xxxxxxxx has been passed to the POWER
interface for execution.
CACO248E ILLEGAL PREFIX -- REENTER

Explanation: The entered prefix for the date table is not allowed.
CACO249E MONTH INVALID -- REENTER

Explanation: The entry was not a valid month.
CACO250E WORK WEEK MUST BE 5, 6, OR 7 -- REENTER

Explanation: A character other than five, six, or seven was entered.
CACO251E YEAR INVALID -- REENTER

Explanation: The calendar year specified is not a valid year.
User Response: Reenter with a valid year specification.
CACO253E REQUESTED MEMBER NOT FOUND

Explanation: The requested member does not exist.
User Response: Check the member name or display a directory list for the correct
member.

1.3 CACO Messages
CACO255I –CACO266E
CACO255I CALENDAR xxxxxxxx FOR YEAR xxxx WAS SUCCESSFULLY DELETED

Explanation: The calendar name specified for the year specified has been successfully
deleted.
CACO256E CALENDAR xxxxxxxx FOR YEAR xxxx NOT FOUND - REENTER

Explanation: An unknown calendar name or year was entered.
User Response: Determine correct calendar name or year and reenter.
CACO257E COMMAND REQUIRES UPDATE MODE

Explanation: A command requiring an UPDATE was issued while in DISPLAY mode.
User Response: Logon with a valid write password and retry the command.
CACO258I DATETABLE xxxxxxxx FOR YEAR xxxx WAS SUCCESSFULLY DELETED

Explanation: The date table name for the year specified has been successfully deleted.
CACO259E DATETABLE CREATE REQUIRES NAME

Explanation: A date table CREATE command was issued without a name entry.
User Response: Reissue the command with the desired name.
CACO260E DATETABLE xxxxxxxx FOR YEAR xxxx NOT FOUND - REENTER

Explanation: An unknown date table name or year was entered.
User Response: Determine the correct date table name or year and reenter.
CACO264E INVALID MONTHLY ENTRY

Explanation: The monthly calendar entry is incorrect.
User Response: Correct the entry and reenter.
CACO265E MONTHLY DAY NOT IN DAY RANGE OF ALL MONTHS

Explanation: The monthly calendar day is too large for some months. For example, 31 is
too large for February.
User Response: Correct the entry and reenter.
CACO266E COMMAND NOT ALLOWED

Explanation: This command is not allowed by Unicenter CA-Scheduler.

1.3 CACO Messages
CACO267E PUN INCORRECTLY SPOOLED TO USERID=xxxxxxxx

Explanation: The punch has been spooled to user ID xxxxxxxx, instead of to the DOS
guest machine.
User Response: Correct the VM spool command in the startup EXEC.
CACO268E SECURITY VIOLATION -- NO MESSAGE SUPPLIED

Explanation: The user security exit has denied access for this function without returning
a message.
CACO274E USERID NOT AUTHORIZED

Explanation: You are not authorized to access this member.
CACO276E WEEKLY DAY OF WEEK INVALID

Explanation: The entry is not a valid day of the week.
CACO277E A GET STORAGE REQUEST HAS FAILED

Explanation: There is not enough storage in the online partition.
User Response: Increase the size of the online partition.
CACO278E A FREE STORAGE REQUEST HAS FAILED

Explanation: A problem has occurred with a free storage request.
CACO279E CALENDAR NAME IS INVALID

Explanation: The name entered is not a valid calendar name.
CACO280E PROCEDURE NAME IS INVALID

Explanation: The name entered is not a valid procedure name.
CACO281E PROCEDURE NAME MAY NOT BE CHANGED

Explanation: A name change was entered from the ALTER or DEFINE screen.

1.3 CACO Messages
CACO282E COMMAND IS INVALID

Explanation: An invalid command was entered.
CACO283E COPY REQUIRES NEW PROCEDURE NAME

Explanation: A new name was not specified for the procedure copy.
User Response: Enter p=xxxxx, where xxxxx is the new procedure name.
CACO284E COMMAND INVALID FROM DISPLAY FUNCTION

Explanation: A change command was entered while in DISPLAY mode.
CACO285E INSUFFICIENT STORAGE FOR COMMAND

Explanation: The editor could not acquire enough storage to pass the command back to
the online transaction.
User Response: Increase the amount of storage available to the transaction.
CACO286I PROCEDURE xxxxxxxx HAS BEEN RELEASED

Explanation: The lock on the procedure has been removed.
CACO287E NEW PROCEDURE NAME ALREADY EXISTS - NAME NOT CHANGED

Explanation: The new procedure name already exists.
User Response: Reenter a name that does not already exist.
CACO288I REQUESTED MEMBER HAS BEEN RELEASED

Explanation: The lock on the requested member has been removed.
CACO289I PROCEDURE NAME HAS BEEN CHANGED

Explanation: The procedure name has been changed.
CACO290E NEW PROCEDURE NAME IS TOO LONG

Explanation: The procedure name is longer than eight characters.

1.3 CACO Messages
CACO300E SECURITY VIOLATION

Explanation: An attempt was made to modify an edited member while in display mode.
User Response: If modification is desired, QUIT the editor session and reenter in alter
mode instead of display mode.
CACO301E UNABLE TO PROCEED

Explanation: A critical processing error due to insufficient storage occurred while
editing a member.
User Response: Under CICS, increase the partition size or the SIZE parameter, or retry
when more CICS storage is available.
Under CMS, increase USERID storage.
Under ICCF, increase pseudo-partition size.
CACO305E I/O ERROR

Explanation: An I/O error occurred while reading or writing an edited member.
CACO306E SYNTAX ERROR

Explanation: Invalid syntax was used issuing an editor command.
User Response: See the appendix "Advantage CA-Earl Source Members" in the Unicenter
CA-Scheduler Reference Guide, Part 2
for proper syntax. Then, reissue the command.
CACO307E PARAMETER TOO LARGE

Explanation: The parameter length used to set a PF key function exceeds the allowable
maximum.
User Response: Reissue the command with a shorter parameter.
CACO309E INVALID LINE COMMAND(S)

Explanation: An invalid editor line (for example, prefix area) command was issued.
User Response: See the appendix "Advantage CA-Earl Source Members" in the Unicenter
CA-Scheduler Reference Guide, Part 2
for proper syntax. Then, reissue the command.
CACO310E UNKNOWN PF KEY

Explanation: The PF key selected to set a function is not defined in the CASOPFK
macro.
User Response: Select a valid PF key and reissue the command or recode the macro.

1.3 CACO Messages
CACO311E LINE OUT OF TEXT

Explanation: The number of lines specified in the editor command exceeds the member's
size.
User Response: Reissue the command with a smaller number of lines.
CACO312E COLUMN OUT OF TEXT

Explanation: The column number requested for the editor command exceeds the
member's size.
User Response: Reissue the command using a valid column number.
CACO313E TARGET LINE WITHIN RANGE OF COPIED LINES

Explanation: The number of lines requested for the editor command exceeds the range
given.
User Response: Reissue the command using a valid number of lines.
CACO314I COMMAND COMPLETED

Explanation: The editor command has completed successfully.
CACO315I xxxxxxxx NOT FOUND

Explanation: The search argument was not located in the edited member.
CACO317E INSUFFICIENT EDITOR STORAGE AVAILABLE

Explanation: The editor command requires more storage than is available.
User Response: Under CICS, increase the partition size and/or the SIZE parameter, or
retry when more CICS storage is available.
Under CMS, increase USERID storage.
Under ICCF, increase pseudo-partition size.
CACO320E UNABLE TO LOAD MODULE xxxxxxxx

Explanation: The listed program could not be located.
CACO325E NO SAVED COPY OF MEMBER TO RECALL

Explanation: No prior DEXPAND command was issued to save the edited member.
User Response: Issue DEXPAND (without the NOSAVE option) to expand Unicenter
CA-Driver procedures and save the currently displayed data. RECALL may be issued
thereafter to restore the previously saved copy.

1.3 CACO Messages
CACO327I QUIT|SAVED|FILED STG|DOC J=xxxxxxxx

Explanation: The listed command was issued while editing a staging or documentation
member.
CACO328E DRIVER EXPANSION ERROR HAS OCCURRED

Explanation: An error has occurred while invoking Unicenter CA-Driver from the
editor.
User Response: See the message explanation for the line in error.
CACO350E KEY CHANGES NOT ALLOWED FROM STAGING

Explanation: An attempt to change a key from staging was made.
CACO351E PASSWORD IS INVALID

Explanation: An invalid password was entered.
CACO352E PASSWORD HAS BEEN ADDED|CHANGED

Explanation: The password has been added or changed.
CACO353E KEY CHANGES NOT ALLOWED FOR JOB MAINTENANCE

Explanation: An attempt was made to change a key field during job maintenance.
CACO354W xxx NOT FOUND

Explanation: A display or alter was requested for a nonexistent record (xxx). For an
alter, create is assumed and the message text is expanded with "- FILL IN TO CREATE."
User Response: For an alter, fill in the information and press Enter to create a new
record or press Clear to cancel the operation. For a display, ensure that you request an
existing record.
CACO355E AUTO-REPLY --> SYSTEM ERROR RC=xx

Explanation: An error was detected while calling the Auto-Reply subsystem.

1.3 CACO Messages
CACO360I AUTO-REPLY RECORD ADDED

Explanation: This message confirms that a record has been added.
CACO361I AUTO-REPLY RECORD UPDATED

Explanation: This message confirms that a record has been updated.
CACO362I AUTO-REPLY RECORD DELETED

Explanation: This message confirms that a record has been deleted.
CACO369I PRESS ==> PF5 <== TO CONFIRM DELETE

Explanation: This message instructs you to press PF5 to verify what you intend to
delete.
User Response: Press PF5 to confirm the deletion on the Automatic Reply Maintenance
Panel.
CACO371E AUTO-REPLY SUPPORT NOT GENERATED

Explanation: AUTRPLY=NO in CAIJGEN macro.
CACO372I UPDATE FIELDS AND PRESS ENTER

Explanation: Fields in the Automatic Reply Maintenance panel need to be updated.
User Response: Enter updated information in the appropriate fields.
CACO380E CAIAUDIT INTERFACE ERROR HAS OCCURRED R/C=X'rr'

Explanation: An error has occurred calling the CAIAUDIT interface.
CACO666E MAINTENANCE PROGRAM LOAD FAILED-xxxxxxxx

Explanation: The listed program could not be located.
CACO799E MAX WAIT EXPIRED-COMMAND CANCELLED

Explanation: The CMS transaction was trying to communicate with the guest machine
and the guest machine did not respond in the allotted time.
User Response: Verify that the guest machine is up and running and that Unicenter
CA-Scheduler is active.

1.4 CACR Messages
CACR002E –CACR008I
1.4 CACR Messages

CACR002E MOUNTED TAPE IS NOT A CA-DRIVER BACKUP TAPE
Explanation: A restore function is being performed, but the tape that CARUTIL is
reading is not a library save tape.
User Response: Mount the correct tape and reexecute restore function.
CACR003I BACKUP TAPE CREATED MM/DD/YY HH.MM.SS

Explanation: A restore function is being performed, and CARUTIL is reporting the
creation date and time of the save tape being used.
CACR004E RESTORE ALL REQUEST FROM A SELECT SAVE TAPE

Explanation: A -RESTORE ALL function is being performed using a save tape that was
created with a SAVE SELECT rather than a -SAVE ALL function.
User Response: The job is canceled. Ensure that the correct save tape is being used.
CACR005E xxxxxxxx NOT FOUND ON BACKUP TAPE

Explanation: The selected procedure was not found on the save tape. The requested
procedure is not restored.
User Response: Investigate and correct the -RESTORE selection.
CACR006E xxxxxxxx NOT RESTORED SINCE IT ALREADY EXISTS

Explanation: The displayed procedure was to be restored, but it already exists in the
procedure library, and the restore did not specify the REPLACE option. The specified
procedure is not restored.
User Response: Ensure that the correct tape is mounted or specify the REPLACE option
to restore this procedure.
CACR007I xxxxxxxx MEMBER RESTORED

Explanation: CARUTIL restored the displayed procedure from the -SAVE tape.
CACR008I ******** RESTORE SUCCESSFULLY COMPLETED ********

Explanation: The restore function was successfully completed, except for any specific
procedures not restored due to prior error messages.

1.4 CACR Messages
CACR009E –CACR015E
CACR009E THE PRECEDING CONTINUATION IS OUT OF ORDER. STATEMENT IGNORED.

Explanation: A statement beginning with CARUTIL continuation character was
encountered, but the previous statement did not indicate continuation. The continuation
statement is ignored.
User Response: Correct the statements that are in error.
CACR010E COULD NOT PROCESS CONTINUATION DUE TO CONTROL END OF FILE

Explanation: A continuation statement was expected, but CARUTIL encountered end of
file. The continuation indication is ignored.
User Response: Correct the statements in error.
CACR011E CONTINUATION EXPECTED, NONE FOUND

Explanation: A statement indicating continuation was followed by a statement that did
not begin with the continuation character. The continuation indication is ignored.
User Response: Correct the statements in error.
CACR012E BLANK CONTINUATION STATEMENT. IGNORED.

Explanation: A continuation statement was found to contain all blanks. The
continuation statement is ignored.
User Response: Correct the statement.
CACR013E SYNTAX ERROR

Explanation: Two consecutive field delimiters were found (not character string
delimiters). Editing of the statement continues. If the error is found to be severe enough,
the statement will be ignored.
User Response: Correct the syntax error. Valid field delimiters are commas, blanks,
equal signs, and parentheses.
CACR014E THE PRECEDING STATEMENT IS INVALID OR OUT OF ORDER. IGNORED.

Explanation: The system expected a CARUTIL control statement or continuation
statement but found neither. The encountered statement is ignored.
CACR015E PARAMETER LENGTH ERROR

Explanation: The referenced word is longer than eight characters. The parameter is
ignored. If the parameter is critical to the function, the statement will be ignored.
User Response: Correct the word.

1.4 CACR Messages
CACR016I –CACR022I
CACR016I MEMBER xxxxxxxx DELETED

Explanation: The displayed procedure was, by request, deleted from the procedure
library.
CACR017E MEMBER xxxxxxxx CURRENTLY ENQUEUED, PROCESSING BYPASSED

Explanation: The requested member is currently being updated by another CARUTIL
user. CARUTIL bypasses the function requesting this member.
User Response: Initiate the function again later. If you are sure that no one else is
updating the member, use the RELEASE command to free it.
CACR018W MEMBER xxxxxxxx CURRENTLY IN USE, PROCESSING CONTINUES

Explanation: This nonupdate function has requested a member that is being updated by
another user. The member is processed, and the job continues.
CACR019W NO MEMBERS DEFINED FOR THIS LIBRARY

Explanation: A library -DISPLAY function has been requested, but this library directory
contains no procedure members. No -DISPLAY function is performed.
User Response: Place procedures in the library before requesting a -DISPLAY function.
CACR020E NAMED PROCEDURE HAS A SAVED MEMBER.

DELETE/REPLACE IGNORED
Explanation: Because of an online update failure, the changes that were entered were
placed in a save member.
User Response: Correct the failure and file the procedure online. Then repeat the batch
function.
CACR021I SAVED MEMBER xxxxxxxx DELETED.

Explanation: The deletion of the saved member completed successfully.
CACR022I MEMBER xxxxxxxx RELEASE COMPLETE.

Explanation: The release of the enqueued member completed successfully.

1.4 CACR Messages
CACR023E MEMBER xxxxxxxx RELEASE INVALID.

Explanation: The RELEASE command that was issued on the displayed member was
not successful. The member was not enqueued, or the name was misspelled.
User Response: Ensure that the member name is spelled correctly, and resubmit if
desired.
CACR028E NO INPUT STATEMENTS ENTERED

Explanation: CARUTIL encountered end of file on the first read. Either there was no
input or the input given was in error and ignored. The job terminates abnormally.
User Response: Correct the situation and resubmit the job.
CACR029T NOT ENOUGH GETVIS. ALLOCATE MORE GETVIS AND RESUBMIT

Explanation: CARUTIL required more partition GETVIS storage than was available.
The job is canceled.
User Response: Allocate a larger partition size, run CARUTIL in a partition with more
virtual memory, or decrease the size parameter value on the EXEC statement.
CACR030E SECURITY UNLOCK FAILED

Explanation: An unauthorized password was given in an attempt to override password
security. The job is canceled.
User Response: Supply the correct master password.
CACR032E MASTER KEY NOT GIVEN TO OVERRIDE LIBRARY SECURITY.

Explanation: This file has password protection against overwriting. Unicenter
CA-Driver redisplays the menu.
User Response: Access the procedure with the write password.
CACR033I MASTER KEY ELIMINATED

Explanation: A request to eliminate the master password was successful.
CACR034E ABEND HAS OCCURRED AT xxxxxxxx

Explanation: Unicenter CA-Driver has abended.
User Response: Rerun the job with the -DEBUG ENABLE SYSTEM. If you are running
in a DOS, DOS/VS, or DOS/VSE environment, include ,DUMP in the -DEBUG
command. Then contact Computer Associates Technical Support.

1.4 CACR Messages
CACR035E SRAM ERROR HAS OCCURRED

Explanation: CA-SRAM has returned an error.
User Response: Ensure that you have sufficient GETVIS space and that there is a label
for the CA-SRAM Services work file (WORK1). Contact Computer Associates Technical
Support if the problem persists.
CACR037E SECURITY VIOLATION

Explanation: An incorrect or missing password was supplied.
User Response: Correct the password.
CACR038I PASSWORD PROTECTION ELIMINATED.

Explanation: Read and write passwords have been removed from the procedure.
CACR039I PASSWORD PROTECTION ADDED

Explanation: Read and write passwords have been added to the procedure.
CACR040I WRITE PASSWORD HAS BEEN CHANGED

Explanation: The write password for this procedure has been changed.
CACR041I READ PASSWORD ELIMINATED

Explanation: The read password for this procedure has been removed.
CACR042I READ PASSWORD HAS BEEN CHANGED

Explanation: The read password for this procedure has been changed.
CACR043E xxxxxxxx IS AN INVALID RESTORE PARAMETER

Explanation: The displayed keyword was found on a -RESTORE command, but is an
invalid parameter for the RESTORE function. The keyword is ignored. Editing of the
statement continues.
User Response: Resubmit with a correct parameter. The only valid keywords for the
-RESTORE function are ALL, NEWLIB, REPLACE, and SELECT.

1.4 CACR Messages
CACR045E xxxxxxxx IS AN INVALID SAVE PARAMETER

Explanation: The displayed keyword parameter is invalid for a -SAVE function. The
parameter is ignored.
User Response: Resubmit with a correct parameter. The only valid parameters are ALL
and SELECT.
CACR046E MEMBER NAME IS MISSING

Explanation: The procedure name did not follow the command on the -PROC statement.
Editing of the statement continues, but the statement will not be processed.
User Response: Correct the -PROC statement.
CACR047E PARM xxxxxxxx IS NOT ALPHANUMERIC

Explanation: The displayed variable parameter is not made up of only alphabetic and
numeric characters. Editing of the statement continues.
User Response: Correct the variable parameter.
CACR048E xxxxxxxx IS AN INVALID -PROC KEYWORD

Explanation: The displayed parameter is invalid for a -PROC statement. The keyword
is ignored. Editing of the statement continues.
User Response: Correct the keyword.
CACR049E xxxxxxxx IS NOT NUMERIC

Explanation: The specified operand should be numeric, but it is not. Editing of the
User Response: Correct the operand.
CACR050E ARRAY DIMENSION IS INVALID OR GIVEN AS ZERO

Explanation: The variable parameter array dimension must be a positive integer.
Editing of the statement continues.
User Response: Correct the variable parameter array dimension.
CACR051E xxxxxxxx IS AN INVALID OPTION. IGNORED.

Explanation: Unicenter CA-Driver produces this message for one of several reasons:
■ The -LIB function specifies an option other than PRINT, PUNCH, REPORT, SCAN,
INCLUDE or EXCLUDE.
■ The -LIB correction function specifies an option other than COR, INCLUDE or
EXCLUDE.
■ The -PROC statement option is invalid.
User Response: Correct the function or statement in error and resubmit the job for
processing.

1.4 CACR Messages
CACR052E PARM NAME LENGTH ERROR. NAME TRUNCATED.

Explanation: The variable parameter name is longer than the allowable maximum of
seven characters. The variable parameter name is truncated to seven characters, and
editing of the statement continues.
User Response: Change the variable parameter name's length to seven characters or less.
CACR053E PARM DEFAULT LENGTH GREATER THAN xxxxxxxx DEFAULT TRUNCATED.

Explanation: The default value for a variable parameter is greater than 64 characters.
The value is truncated to 64 characters, and editing of the statement continues.
User Response: Keep within the limits.
CACR054E MORE THAN xxxxxxxx VARIABLES GIVEN. NO MORE ACCEPTED.

Explanation: More than 80 variable parameters were specified for the procedure. The
first 80 variable parameters are accepted; the rest are ignored.
CACR055E ARRAY DIMENSION IS GREATER THAN xxxxxxxx

Explanation: A variable parameter array may have a maximum of 80 elements. The
variable parameter had more than 80 elements specified. The dimension is ignored.
CACR056E # OF ARRAY VALUES EXCEEDS ARRAY DIMENSION DEF. NO MORE

ACCEPTED.
Explanation: More default values were specified for a variable parameter array than
there are elements of the array. The dimension is ignored. Editing of the statement
continues.
CACR057E AN EQUAL SIGN MUST FOLLOW THE KEYWORD PARM

Explanation: An equal sign must separate a keyword from its operands. Editing of the
User Response: Place an equal sign after the keyword parameter.
CACR058E RIGHT PARENTHESIS DOES NOT CLOSE DIMENSION SPECIFICATION

Explanation: The variable parameter array dimension specification is not enclosed in
parentheses. Editing of the statement continues.
User Response: Close the dimension specification with a right parenthesis.

1.4 CACR Messages
CACR059E SPECIFICATION MUST BE A VALUE OR DELETE

Explanation: A variable parameter default value specification must be either a value or
the word DELETE. The specification is ignored. Editing of the statement continues.
User Response: Specify a value or DELETE for the variable parameter default value
specification.
CACR060E COMMA MUST SEPARATE ARRAY VALUES

Explanation: Default values for a variable parameter array must be separated by
commas. Editing of the statement continues.
User Response: Separate the default values with commas.
CACR061W xxxxxxxx IS AN INVALID yyyyyyyy OPTION. NO ASSUMED.

Explanation: A print or punch (yyyyyyyy is either PRINT or PUNCH) keyword
parameter must be specified as either YES or NO. The operand is assumed to be NO.
User Response: Specify either YES or NO on the option statement.
CACR062E COR ARGUMENT FIELD LENGTH ERROR. COR IGNORED.

Explanation: The global correction scan field is greater than 40 characters. The global
correction is ignored.
User Response: Stay within 40 characters for the scan field.
CACR063E COR CORRECTION FIELD LENGTH ERROR. COR IGNORED.

Explanation: The global scan correction field is greater than 40 characters. The global
correction is ignored.
User Response: Stay within 40 characters for the scan field.
CACR064E KEYWORD SYNTAX ERROR

Explanation: The syntax of the statement is in error. One or more of the following errors
may be present:
1. An equal sign does not separate a keyword from its value.
2. Variable parameter definitions are not separated by commas.
3. Variable parameter definitions are not enclosed in parentheses.
4. A keyword is not followed by an operand.
5. A comma immediately follows the equal sign following a keyword.
User Response: Correct the syntax errors.

1.4 CACR Messages
CACR065E UNBALANCED DELIMITERS. IGNORED.

Explanation: The delimiters around a character string do not match. Editing of the
User Response: Correct the delimiters.
CACR066E ZERO LENGTH CHARACTER STRING. IGNORED.

Explanation: A character string is incorrectly specified as two consecutive delimiters.
User Response: Correct the character string.
CACR067E COR ARGUMENT IS ALL BLANKS

Explanation: The global correction scan field is all blanks, or there are more than five
COR statements. The global correction is ignored.
User Response: Place something in the scan field or remove any COR statements that
exceed the maximum allowed (five).
CACR068E MEMBER NAME DOES NOT BEGIN WITH AN ALPHA CHARACTER

Explanation: The first character of a member name must be an alphabetic character.
User Response: Begin the member's name with an alphabetic character.
CACR069W xxxxxxxx IS AN INVALID SAVE/RESTORE OPTION. IGNORED.

Explanation: An invalid option was specified for -SAVE or -RESTORE. The invalid
option is ignored and processing continues.
User Response: Specify a valid option. REPLACE and DELETE are the only valid
options.
CACR070W xxxxxxxx IS AN INVALID SAVE/RESTORE KEYWORD. IGNORED.

Explanation: The displayed keyword is not valid for a -SAVE or -RESTORE function.
The invalid keyword is ignored and processing continues.
User Response: Specify a valid keyword.
CACR071E PARM = xxxxxxxx DELETE REQUEST INVALID FOR A CREATE RUN

Explanation: A variable parameter value was specified as DELETE to remove the
variable parameter definition, but the procedure is being created with OPTION =
CREATE. The DELETE request is ignored.
User Response: Remove the DELETE request, or verify that the member is to be created
and not replaced.

1.4 CACR Messages
CACR072E xxxxxxxx IS A DUPLICATE PARM DEFINITION

Explanation: The displayed variable parameter has already been defined for this
procedure. The variable parameter definition request is ignored.
User Response: Correct the parameter definition.
CACR073W RENAME IS INCOMPATIBLE WITH A xxxxxxxx OPTION

Explanation: The RENAME keyword is invalid in conjunction with a CREATE or
DELETE request. xxxxxxxx is either CREATE or DELETE. The RENAME parameter is
ignored. Processing continues.
User Response: Remove the RENAME keyword.
CACR074W GLOBAL CORRECTION IS INCOMPATIBLE WITH A xxxxxxxx OPTION

Explanation: The COR parameter of the -PROC statement is valid only for OPTION =
SELECT. xxxxxxxx is either CREATE or DELETE. The correction request is ignored.
User Response: Remove the COR parameter.
CACR075E MEMBER xxxxxxxx NOT FOUND

Explanation: The displayed procedure was selected for a -SAVE function, but it was not
found in the procedure library. The displayed procedure was not selected. The -SAVE
function continues processing.
User Response: Investigate and correct the situation as desired.
CACR076E CREATE FUNCTION FAILED SINCE MEMBER xxxxxxxx ALREADY EXISTS

Explanation: An attempt is being made to create a procedure that already exists. The
create request is ignored.
User Response: If you are trying to alter an existing procedure, use REPLACE. If you
are trying to create a new procedure, give it a unique name.
CACR077E CTL STMNT NOT 1ST CARD AFTER xxxxxxxx STMNT

Explanation: A CARUTIL control statement must be the first statement after a -PROC
statement with OPTION=SELECT (-ADD, -REP, -DEL, -COR). All statements until the
next control statement are ignored.
User Response: Change the job stream and resubmit.
CACR078E THE PRECEDING IS NOT A VALID CARUTIL STATEMENT

Explanation: A statement beginning with the CARUTIL control character was
encountered, but the command was not -PROC, -DISPLAY, -SAVE, -RESTORE, or -LIB.
The statement is ignored.

1.4 CACR Messages
CACR079E THE PRECEDING STATEMENT IS INVALID OR OUT OF ORDER

Explanation: CARUTIL is processing a -PROC statement, and expects another -PROC
statement or an -END statement. The statement is ignored.
User Response: Reorder or change the statements in error.
CACR080W MULTIPLE -SAVE / -RESTORE STATEMENTS. IGNORED.

Explanation: More than one -SAVE or -RESTORE request was made in the same
execution of CARUTIL; only one is allowed. All -SAVE and/or -RESTORE requests other
than the first are ignored.
User Response: Specify only one -SAVE or -RESTORE per execution of CARUTIL.
CACR081I PARM DEFINITION xxxxxxxx IS UNREFERENCED

Explanation: The displayed variable parameter was defined for the procedure, but is not
referenced anywhere in the procedure.
CACR082I MEMBER xxxxxxxx SELECTED

Explanation: The displayed procedure was selected successfully. Processing continues
normally.
CACR083W CONDITIONAL EXPANSION STEP xxxxxxxx IS UNREFERENCED

Explanation: The displayed conditional expansion step was defined on a -STEP
statement, but no reference to the step name was found in the procedure. Processing
continues normally. This may or may not be an error condition.
CACR084E ERROR FOUND WHILE PROCESSING MEMBER xxxxxxxx REQUESTED

OPERATIONS NOT PERFORMED
Explanation: One or more errors were encountered that were sufficiently severe to
prevent the requested operation from being performed. No procedure library updating
remains in effect for the displayed procedure.
User Response: Correct the errors.
CACR085I MEMBER xxxxxxxx CREATED

Explanation: The displayed procedure was created.

1.4 CACR Messages
CACR086E CONDITIONAL EXPANSION STEP xxxxxxxx IS UNDEFINED

Explanation: A reference was found in the procedure for an undefined conditional
expansion step name. The procedure is not created, replaced, or updated, depending
upon the option selected.
User Response: Either remove the reference or define the conditional expansion step
name.
CACR087W CONDITIONAL EXPANSION STEP xxxxxxxx IS UNDEFINED

Explanation: The specified variable step name has been referenced in a -GOTO
statement, but has not been defined in a -STEP statement. The statement is processed
normally. This is only a warning of a potential problem.
User Response: Correct the statement if desired.
CACR088I MEMBER xxxxxxxx REPLACED

Explanation: The displayed procedure was completely replaced due to
OPTION=REPLACE on the -PROC statement.
CACR089E CARUTIL RUN TWICE WITH THE SAME INPUT

Explanation: The internal hash totals maintained by CARUTIL for procedure updates
were the same as the last update of the procedure. The update is not processed.
User Response: If the same update is not being processed twice, then the override
facility must be used to process the job stream which resulted in duplicate hash totals.
CACR090W USER OVERRIDE. REQUESTED OPERATIONS PERFORMED.

Explanation: The override facility was invoked to update a procedure.
CACR091I OLD MEMBER NAME xxxxxxxx HAS BEEN DELETED

Explanation: A rename operation has been performed. The old procedure name no
longer exists in the procedure library.
CACR092E RENAME FAILED SINCE MEMBER xxxxxxxx ALREADY EXISTS

Explanation: A requested rename operation cannot be performed because the new name
already exists in the procedure library.
User Response: If you are trying to rename the procedure, choose a different name.

1.4 CACR Messages
CACR093I –CACR101E
CACR093I MEMBER xxxxxxxx HAS BEEN RENAMED yyyyyyyy

Explanation: A successful rename operation has renamed procedure xxxxxxxx as
yyyyyyyy.
CACR094I MEMBER xxxxxxxx HAS BEEN UPDATED

Explanation: Procedure xxxxxxxx has been updated successfully.
CACR095E NO MEMBER REQUESTED FOR A SELECT RUN

Explanation: A selective -SAVE function was indicated, but no -PROC statements
naming the procedures to be saved were found. The job is terminated.
User Response: Correct the job stream and resubmit.
CACR096I MEMBER xxxxxxxx SAVED

Explanation: The displayed procedure was saved on the backup tape.
CACR097I ******** BACKUP COMPLETED SUCCESSFULLY ********

Explanation: The save function was performed.
CACR098W REPLACE OPTION REQUESTED FOR MEMBER xxxxxxxx ; MEMBER NOT FOUND
CREATE OPTION USED
Explanation: An OPTION=REPLACE was specified in the -PROC statement to replace
the specified procedure. However, the procedure could not be found. CARUTIL
converted the OPTION=REPLACE to an OPTION=CREATE and created a new procedure
of the specified name.
User Response: Make sure the specified procedure was spelled correctly. If it was, take
no further action. If it was not, delete the newly created procedure and and resubmit the
job with the procedure name spelled correctly.
CACR101E NO INPUT GIVEN FOR THE CREATE RUN

Explanation: A procedure was to be created (OPTION=CREATE), but no procedure
contents were found. The job is terminated.
User Response: Correct the situation and resubmit.

1.4 CACR Messages
CACR102E CTL STATEMENT IS INVALID IN A CREATE RUN. IGNORED.

Explanation: A procedure is being created, and update statements were encountered
(ADD, DEL, REP, COR). The update statements are ignored.
User Response: Correct the situation and resubmit.
CACR103I PARM DEFINITION xxxxxxxx HAS BEEN DELETED

Explanation: The displayed variable parameter was deleted successfully.
CACR104E VARIABLE IS NOT A SYMBOLIC PARAMETER OR NUMERIC NEAR POSITION xx

Explanation: A numeric subscript or substring position/length field was expected, or a
variable parameter to be used as such was expected, but neither was found. Editing of
the statement continues.
User Response: Correct the situation.
CACR105W POSSIBLE UNDEFINED VARIABLE PARAMETER NEAR POSITION xx

Explanation: What appears to be a variable parameter was detected within the body of
a procedure (begins with ampersand), but the variable parameter was not defined as
such. The apparent variable parameter is treated as part of the text of the procedure, not
as a variable parameter.
User Response: Correct the situation.
CACR106E PARM xxxxxxxx EXCEEDS THE MAXIMUM ALLOWABLE DEFINITIONS

Explanation: In excess of 64 variable parameters or elements in an array have been
defined. Only the first 64 parameters or elements are accepted.
User Response: Stay within the limits.
CACR107E INCOMPLETE CONDITIONAL EXPANSION STATEMENT

Explanation: A conditional expansion statement is missing some required parameters or
operators. The statement is ignored.
CACR108I PARM DEFINITION xxxxxxxx HAS BEEN REPLACED

Explanation: The default value for the displayed variable parameter has been updated.
CACR109I PARM DEFINITION xxxxxxxx HAS BEEN ADDED

Explanation: The displayed variable parameter definition has been added to the
procedure.

1.4 CACR Messages
CACR110E SYMBOLIC PARAMETER REFERENCE SYNTAX ERROR NEAR POSITION xx

Explanation: A substring notation specification is not enclosed in parentheses, or one of
the required two fields is missing. The substring notation is ignored.
User Response: Correct the syntax error.
CACR111E SYMBOLIC PARAMETER SYNTAX ERROR NEAR POSITION xx

Explanation: A variable parameter was expected, but a single ampersand was found
instead. Editing of the statement continues.
User Response: Correct the syntax error.
CACR112I NO ADDITIONS GIVEN

Explanation: An -ADD control statement was found, but it was not followed by any
statements to be added. The -ADD statement is ignored. The procedure is not updated.
User Response: Submit a correct job stream.
CACR113W NO MATCH ON THE GIVEN CORRECTION STRING

Explanation: The scan argument on a -COR statement was not located within the
specified range of statements. The -COR statement is ignored.
User Response: Verify that the correct scan was given to CARUTIL.
CACR114E EXCEEDS THE NUMBER OF ALLOWABLE GLOBAL COR STATEMENTS

Explanation: More than five concurrent global COR statements were encountered.
Excess statements are ignored.
User Response: Submit the ignored statements in a new job stream.
CACR115E NO REPLACEMENTS GIVEN

Explanation: A -REP control statement was not followed by any statements to be added.
The -REP statement is ignored. The procedure is not updated.
CACR116E THE PRECEDING IS NOT A CONTROL STATEMENT

Explanation: A CARUTIL statement was expected but not found. All statements until
the next control statement are bypassed.
CACR117E SEQ REFERENCE IS OUTSIDE THE MEMBER LIMITS

Explanation: A sequence number specified in an update statement was greater than the
highest sequence number in the procedure. The statement is ignored. The procedure is
not updated.

1.4 CACR Messages
CACR118W –CACR124E
CACR118W -END DOES NOT TERMINATE THE -PROC CONTROL STATEMENTS

Explanation: An -END statement was expected to terminate a set of statements begun
with a -PROC statement, but no -END statement was found. CARUTIL assumes an
-END statement.
CACR119E SYMBOLIC PARAMETER GREATER THAN xxxxxxxx CHARACTERS, NEAR

POSITION xx
Explanation: A variable parameter name greater than seven characters was found. The
variable parameter is ignored. The procedure is not updated.
User Response: Correct the parameter and resubmit the job.
CACR120E SYMBOLIC PARAMETER IS UNDEFINED NEAR POSITION xx

Explanation: An update on an undefined variable parameter was attempted. The
variable parameter update request is ignored.
User Response: Define the parameter and resubmit.
CACR121E xxxxxxxx IS AN INVALID CONTROL REQUEST

Explanation: A statement was found to begin with the CARUTIL control character, but
the command was not valid. The statement is ignored.
User Response: Correct the request.
CACR122E THE PRECEDING STATEMENT CONTAINS NO SEQUENCE #

Explanation: A control statement requiring a sequence number was found, but no
sequence number was specified (-ADD, -REP, -DEL, -COR). The statement is ignored. The
procedure is not updated.
User Response: Place a sequence number and resubmit.
CACR123E THE PRECEDING STATEMENT IS OUT OF SEQUENCE

Explanation: A control statement sequence error has occurred. For example, an -ADD
occurred before a -PROC statement. CARUTIL flushes to the next control statement.
User Response: Correct the statement sequence.
CACR124E SEQ# 2 IS NOT GREATER THAN SEQ# 1

Explanation: The second sequence number on an update statement must be greater than
the first. CARUTIL flushes to the next control statement. The procedure is not updated.
User Response: Put the sequence numbers in order.

1.4 CACR Messages
CACR125E NO CORRECTION STRING GIVEN

Explanation: The second (replacement) character string on a -COR statement is missing.
CARUTIL flushes to the next control statement. The procedure is not updated.
User Response: Correct the -COR statement.
CACR126E COR ARGUMENT FIELD LENGTH ERROR

Explanation: The scan string of a -COR statement is longer than 40 characters. The
-COR statement is ignored. The procedure is not updated.
CACR127E COR ARGUMENT IS ALL BLANKS

Explanation: The scan field of a -COR statement is all blanks. CARUTIL flushes to the
next control statement. The procedure is not updated.
CACR128E COR CORRECTION FIELD LENGTH ERROR

Explanation: The replacement field on a -COR statement exceeds the maximum of 40
characters. CARUTIL flushes to the next control statement. The procedure is not updated.
User Response: Reduce the length of the replacement field.
CACR129E ARRAY SUBSCRIPT IS NOT 1 - xxxxxxxx NEAR POSITION xx

Explanation: An array subscript value must be in the range 1 to 80. Editing of the
statement continues. The procedure is not updated.
User Response: Put the array subscript within range.
CACR130E SUBSTRING FIELD POSITION IS NOT 1 - xxxxxxxx NEAR POSITION xx

Explanation: A substring position specification must have a value in the range of 1 to
64. Editing of the statement continues. The procedure is not updated.
User Response: Put the substring position specification within range.
CACR131E STATEMENT OUT OF SEQUENCE

Explanation: The CARUTIL control statement is out of sequence. CARUTIL flushes to
the next control statement.
User Response: Correct the sequence.
CACR132E SUBSTRING FIELD LENGTH IS NOT 1 - xxxxxxxx NEAR POSITION xx

Explanation: A substring length specification must have a value in the range 1 to 64.
Editing of the statement continues. The procedure is not updated.
User Response: Put the substring length specification within range.

1.4 CACR Messages
CACR133E SUBSCRIPT REFERENCING A VARIABLE THAT IS NOT AN ARRAY, NEAR

POSITION xx
Explanation: A variable parameter was followed by a subscript, but the variable
parameter was not defined as a variable parameter array; therefore, no subscript may be
used when referencing the variable parameter. Editing of the statement continues. The
procedure is not updated.
User Response: Correct the statement and resubmit the procedure.
CACR134E SUBSTRING REFERENCE OUTSIDE MAX LEN OF xxxxxxxx, NEAR POSITION xx

Explanation: The substring position specification plus the length specification exceeds
64, which is the maximum length of a variable parameter. Editing of the statement
continues. The procedure is not updated.
User Response: Put the substring reference within range.
CACR135E SUBSCRIPT/SUBSTRING MAY NOT REFERENCE AN ARRAY, NEAR POSITION xx

Explanation: A variable parameter used in subscripting or used in substring notation
may not itself be defined as a variable parameter array. Editing of the statement
User Response: Correct the situation and resubmit the job.
CACR136E WRITE PASSWORD IS REQUIRED

Explanation: The supplied password for this procedure is not correct. The procedure is
not selected.
User Response: Correct the password and resubmit.
CACR137I MASTER PASSWORD HAS BEEN ADDED

Explanation: A master password has been added successfully.
CACR138I MASTER PASSWORD UPDATED

Explanation: The master password has been updated successfully.
CACR140E INVALID ARITHMETIC OPERATOR OR TOO MANY OPERANDS

Explanation: A -SET statement containing an arithmetic expression has an arithmetic
operator that is invalid (valid operators are +, -, *, /), or more than two arithmetic
operations have been requested. The statement is ignored. The procedure is not updated.
User Response: Correct the statement in error and resubmit.

1.4 CACR Messages
CACR141W –CACR147W
CACR141W STATEMENT IGNORED

Explanation: The last input statement is in error.
User Response: Correct the statement and resubmit the job for processing.
CACR142E NUM OR LEN ATTRIBUTE TEST MUST COMPARE TO A POSITIVE NUMBER

Explanation: The comparand of a number of elements or length attribute test must be a
positive integer (T'&VAR or N'&VAR). The statement in error is ignored.
CACR143E xxxxxxxx IS NOT NUMERIC

Explanation: The displayed operand must have a numeric value but does not. Editing
of the statement continues. The procedure is not updated.
User Response: Correct the operand and resubmit the job for processing.
CACR144E UNBALANCED DELIMITERS

Explanation: A character string is not properly terminated with the same delimiter that
begins the string. Editing of the statement continues. The procedure is not updated.
User Response: Correct the delimiters and resubmit the job for processing.
CACR145E ZERO LENGTH CHARACTER STRING

Explanation: Two consecutive character string delimiters were found; no character string
was found. Editing of the statement continues. The procedure is not updated.
User Response: Correct the character string and resubmit the job.
CACR146W POSSIBLE LITERAL FOUND IN A CORRECTED STATEMENT

Explanation: CARUTIL, as a result of a global or limited correction, changed a statement
that appears to have a character string contained within it. Processing continues
normally.
User Response: Verify that the statement was correctly modified without affecting the
character string.
CACR147W CORRECTION HAS CAUSED TRUNCATION. CORRECTION IGNORED.

Explanation: Correction of a statement would cause the data on the statement to be
shifted further than position 80 during a shift to the right. The statement is not changed.
User Response: Replace the statement rather than modifying it with the correction
facilities.

1.4 CACR Messages
CACR148E THE COMPARAND OF AN IF STATEMENT MAY NOT BE AN ATTRIBUTE

REFERENCE
Explanation: The comparand of an -IF statement cannot be T'&VAR or N'&VAR or
L'&VAR attribute referenced. The -IF statement is ignored. The procedure is not
updated.
User Response: Correct the situation and resubmit the job for processing.
CACR149E AN EQUAL SIGN (=) MUST FOLLOW THE 1ST OPERAND

Explanation: The first and second operands of a -SET statement must be separated by
an equal sign without a blank on either side of the equal sign. The statement is ignored.
The procedure is not updated.
User Response: Correct the syntax and resubmit the job for processing.
CACR150E 1ST OPERAND OF A -SET MUST BE A SYMBOLIC VARIABLE

Explanation: Only a variable parameter (&VAR) may be set using a -SET statement.
The -SET statement is ignored.
User Response: Correct the -SET statement and resubmit the job for processing.
CACR151E xxxxxxxx IS INVALID DURING A PRINT/PUNCH RUN

Explanation: Only the -SEL statement is valid when performing a print or punch of the
library. The statement in error is ignored.
CACR152E SYMBOLIC VARIABLE MISSING, UNDEFINED OR OUT OF PLACE

Explanation: The first operand of an -IF statement must be a variable parameter. The
statement in error contains an unknown operand as the first parameter. The statement is
ignored. The procedure is not updated.
CACR153E RELATIONAL OPERATOR IS MISSING OR OUT OF PLACE

Explanation: A relational operator on an -IF statement was expected, but no valid
operator was found. Valid operators are LT, LE, GE, GT, EQ, NE, =, <, >. Editing of the
statement continues. The procedure is not updated.
User Response: Correct the statement and resubmit the job for processing
CACR154E LITERAL LENGTH ERROR

Explanation: A character string exceeds 64 characters. Editing of the statement
User Response: Correct the character string and resubmit the job for processing.

1.4 CACR Messages
CACR155E TYPE ATTRIBUTE TEST MUST COMPARE TO N, M, C, OR O

Explanation: The comparand of an -IF statement checking a type attribute (T'&VAR)
must be either N, M, C, or O. The statement is ignored. The procedure is not updated.
User Response: Correct the -IF statement and resubmit the job for processing.
CACR156E TOO MANY ARITHMETIC OPERATIONS REQUESTED

Explanation: A -SET statement may have a maximum of two arithmetic operations. The
statement is ignored. The procedure is not updated.
CACR157E FLUSH IS A RESERVED WORD AND MAY NOT BE USED AS A STEP NAME
Explanation: The word FLUSH cannot be used as a step name since it has special
meaning when used as a GOTO parameter. The statement is ignored. The procedure is
not updated.
User Response: Use a different step name and resubmit the job for processing.
CACR158E THIS STEP HAS EXCEEDED THE MAXIMUM ALLOWABLE

Explanation: Only 256 steps may be defined within any one procedure. No more -STEP
statements will be accepted.
User Response: Keep within product limits.
CACR159E DUPLICATE STEP NAME

Explanation: The same step name has already been defined on a -STEP statement. The
statement is ignored. The procedure is not updated.
User Response: Change step names and resubmit the job for processing.
CACR160E 1ST OPERAND OF A -SET MUST NOT BE AN ATTRIBUTE REFERENCE

Explanation: An attribute reference (T'&VAR, N'&VAR, L'&VAR) may not be the first
parameter on a -SET statement. The attribute of a variable parameter cannot be changed
explicitly. The statement is ignored. The procedure is not updated.
CACR161E INCOMPLETE CONDITIONAL EXPANSION STATEMENT

Explanation: The listed conditional expansion statement does not contain all required
components. The statement is ignored. The procedure is not updated.

1.4 CACR Messages
CACR163E 1ST OPERAND OF A -SET MUST NOT CONTAIN SUBSTRING NOTATION

Explanation: A portion of a variable parameter cannot be changed. Only the entire
variable parameter can be changed. The statement is ignored. The procedure is not
updated.
CACR164E LCTR MAY NOT HAVE A ZERO VALUE

Explanation: An -LCTR statement specified a loop counter of zero. The counter value
must be greater than zero. The statement is ignored.
User Response: Correct the -LCTR statement.
CACR165E UNDEFINED VARIABLE PARAMETER NEAR POSITION xx

Explanation: The specified variable parameter has not been previously defined. The
variable parameter is treated as data.
User Response: Define the variable parameter.
CACR166E GOTO STEP NAME MAY NOT BE AN ATTRIBUTE REFERENCE

Explanation: A GOTO step name may be a variable parameter but cannot be an
attribute reference. The statement is ignored.
User Response: Correct the GOTO step name.
CACR167E GOTO STEP NAME MUST NOT CONTAIN SUBSTRING NOTATION

Explanation: A GOTO step name may be a variable parameter but not a substring
reference of a variable parameter. The statement is ignored.
User Response: Correct the GOTO step name.
CACR168E -WTO CONTAINS NO MESSAGE

Explanation: The -WTO command cannot be used to write a blank line to the console.
User Response: Put a message on the -WTO line.
CACR169E OPERAND OF -REPLY MUST BE A VARIABLE

Explanation: The only valid operand of a -REPLY statement is a variable parameter.
User Response: Use a variable parameter as an operand.

1.4 CACR Messages
CACR170E OPERAND OF A -REPLY MUST NOT BE AN ATTRIBUTE REFERENCE

Explanation: A variable parameter attribute reference cannot be used as the operand of
a -REPLY statement. The statement is ignored.
User Response: Remove the variable parameter attribute reference from the -REPLY
statement.
CACR171E OPERAND OF A -REPLY MUST NOT CONTAIN SUBSTRING NOTATION

Explanation: Substring notation cannot be used for a variable parameter being used as
the operand of a -REPLY statement. The statement is ignored.
User Response: Remove the substring notation from the variable parameter.
CACR172E WTO MSG GTR 50 CHAR OR INVALID DELIMITER

Explanation: The longest message that can be written to the console is 50 characters.
User Response: Correct the -WTO statement.
CACR177E xxxxxxxx IS AN INVALID LIB OPTION

Explanation: The only valid options for the -LIB function are PRINT, PUNCH, REPORT,
SCAN, INCLUDE, and EXCLUDE. The invalid option is ignored.
User Response: Correct the option.
CACR178W NOHDR REQUIRES PUNCH. NOHDR IS IGNORED.

Explanation: NOHDR is only valid when PUNCH is specified. NOHDR is ignored.
User Response: Correct the specification.
CACR179E ERROR(S) ENCOUNTERED. REQUESTED OPERATIONS NOT PERFORMED.

Explanation: One or more errors were encountered that prohibit the operation from
continuing. None of the requested operations are performed.
User Response: Correct the specified errors.
CACR181E THE PRECEDING CARD IS AN INVALID PRINT/PUNCH CTL CARD

Explanation: The only allowable statements for a -LIB run are -SEL, -RPG, and -SCAN.
The invalid statement is ignored.
User Response: Correct the invalid statement and resubmit the job for processing.
CACR182E NO SCAN STRING GIVEN

Explanation: A -SCAN statement was found with no scan character string specified.
User Response: Correct the invalid -SCAN statement.

1.4 CACR Messages
CACR183E –CACR190W
CACR183E SCAN STRING LENGTH ERROR

Explanation: The character string specified on a -SCAN statement exceeds 71 characters.
CACR184E SCAN STRING IS ALL BLANKS

Explanation: The scan facility cannot be used to scan for an all-blank field. The SCAN
CACR185W EXCEEDED MAXIMUM # OF ALLOWABLE SCAN STATEMENTS

Explanation: A maximum of 64 SCAN statements may be supplied. Only the first 64
SCAN statements are accepted.
User Response: Stay within product limits.
CACR186W EXCEEDED MAXIMUM # OF ALLOWABLE SEL STATEMENTS

Explanation: A maximum of 256 SEL statements may be supplied. Only the first 256
SEL statements are accepted.
User Response: Stay within product limits.
CACR187E NO SIZE PARAMETER SPECIFIED ON THE // EXEC CARD

Explanation: CARUTIL requires GETVIS storage. The job is canceled.
User Response: DOS/VS users must specify a size parameter on the DOS EXEC
statement to provide GETVIS. Place size parameter on EXEC statement and resubmit the
job.
CACR188E THIS PROGRAM IS BEING RUN REAL. IT MUST RUN VIRTUAL WITH A SIZE
Explanation: CARUTIL is being executed real, but must execute virtual. The job is
canceled.
User Response: Remove the real parameter from the EXEC statement, and replace it
with a size parameter.
CACR189E INSUFFICIENT GETVIS FOR PROGRAM EXECUTION

Explanation: CARUTIL requires more GETVIS storage than is available.
User Response: Increase the GETVIS available, or run this program in a larger partition.
CACR190W SCAN REQUEST(S) FOUND. SCAN OPTION ASSUMED

Explanation: One or more scan parameters were found, but the SCAN option was not
specified on the -LIB control statement. The SCAN option is assumed. The job continues.
User Response: Correct the control statement error.

1.4 CACR Messages
CACR191E –CACR197T
CACR191E SCAN OPTION SPECIFIED, NO SCAN STATEMENTS FOUND

Explanation: The SCAN option was found on the -LIB control statement, but no -SCAN
statements were found. The SCAN option is ignored.
User Response: Remove the SCAN option from the -LIB statement, or insert -SCAN
statements.
CACR192E SEL REQUEST(S) FOUND, NO INCLUDE/EXCLUDE REQUESTED

Explanation: One or more -SEL statements were encountered, but the -LIB statement
does not contain either the INCLUDE or the EXCLUDE option. The -SEL select
statements are ignored.
User Response: Remove the -SEL statements, or add INCLUDE or EXCLUDE options to
the -LIB statement.
CACR193E INCLUDE/EXCLUDE OPTION REQUESTED, NO SEL STMNTS FOUND

Explanation: The INCLUDE or EXCLUDE option was specified on the -LIB statement,
but no -SEL statements were found. The INCLUDE or EXCLUDE option of the -LIB
User Response: Remove the INCLUDE and EXCLUDE options from the -LIB statement,
or add -SEL statements.
CACR194E INCLUDE AND EXCLUDE ARE MUTUALLY EXCLUSIVE

Explanation: Both the INCLUDE and the EXCLUDE options were specified on a -LIB
statement. Only one of the two may be specified on any -LIB statement. Editing of the
statement continues. The function is not performed.
User Response: Remove one option and resubmit the job for processing.
CACR195W SCAN OPTION REQUIRES PRINT SPECIFICATION. PRINT ASSUMED

Explanation: The -LIB statement specified the SCAN option, but the PRINT option was
not specified. The PRINT option is required for a scan function. The PRINT option is
assumed.
CACR196E -SEL NAME DOES NOT BEGIN WITH AN ALPHABETIC CHARACTER

Explanation: The first character of the procedure name on a -SEL statement must be an
alphabetic character. The statement is ignored.
User Response: Correct the procedure name and resubmit the job for processing.
CACR197T SYSTEM ERROR, CODE=xxxx NOTIFY YOUR CA REP.

Explanation: An unrecoverable logic error has occurred.

1.4 CACR Messages
CACR198E -RPG CTL STMT REQUIRES -LIB REPORT SPECIFICATION.

Explanation: An -RPG statement was encountered without a preceding -LIB REPORT
statement. The statement is ignored.
User Response: Correct and resubmit the job for processing.
CACR199E THE PRECEDING CARD IS AN INVALID -RPG CARD

Explanation: A syntax error has been detected on the specified statement. The
CACR200E NO VALID -RPG STMT SUPPLIED FOR THIS RUN

Explanation: Either all -RPG statements were invalid, or none were supplied following
-LIB REPORT statement. The statement is ignored.
User Response: Correct the statements in error and resubmit the job for processing.
CACR202I STMT= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation: This statement from the member named in message CACR203E is invalid.
CACR203E PROC=xxxxxxxx IS INVALID, RECORD SKIPPED

Explanation: The statement shown in message CACR202I is invalid.
CACR204E xxxxxxxx IS AN INVALID COR OPTION.

Explanation: The only valid option on the -LIB COR function is INCLUDE or
EXCLUDE.
User Response: Correct the option and resubmit the job for processing.
CACR205E THE PRECEDING CARD IS AN INVALID CORRECTION CTL CARD

Explanation: The only allowable statements for a -LIB correction run are -SEL and
-COR. The invalid statement is ignored.
CACR206E NO MEMBERS DEFINED IN LIBRARY

Explanation: The procedure library is empty. The requested operations cannot be
performed.
User Response: Verify that the last restore was successful.

1.4 CACR Messages
CACR209E SCHDPARM NOT FOUND

Explanation: Unicenter CA-Scheduler generation parameters were not found.
User Response: Check to make sure that a generation macro was assembled.
CACR210E INVALID DOC KEYWORD

Explanation: An invalid keyword was found in a -DOC control command.
CACR211E xxxxxxxx INVALID OR MISSING KEYWORD

Explanation: The displayed keyword is is invalid or missing.
CACR212E AN EQUAL SIGN MUST FOLLOW A KEYWORD

Explanation: The keyword was not followed by an equal sign.
CACR213E DOES NOT BEGIN WITH AN ALPHA CHARACTER

Explanation: Member names must start with alphabetic characters.
CACR214E INVALID KEYWORD VALUE

Explanation: The keyword value is out of range or invalid.
User Response: Correct the keyword value and resubmit the job for processing.
CACR215I xxxxxxxx RETURN CODE= xxxx

Explanation: The displayed return code (xxxx) has been returned from the displayed
statement or procedure (xxxxxxxx). The return codes are explained below:
00 successful execution
04 warning has been issued, but the function is successful
08 function is unsuccessful
12 function cancels
16 abend occurs
User Response: Review the job stream, correct any statements in error, and resubmit the
job for processing.

1.4 CACR Messages
CACR216I xxxxxxxx RETURN CODE= xxxx, CSECT NAME/LOC= xxxxxxxx / xxxxxx

Explanation: The displayed return code (xxxx) has been returned from the displayed
statement or procedure (xxxxxxxx). The displayed CSECT name and location are used by
Computer Associates Technical Support to diagnose problems. The return codes are
explained below:
00 successful execution
04 warning has been issued, but the function is successful
08 function is unsuccessful
12 function cancels
16 abend occurs
User Response: Review the job stream, correct any statements in error, and resubmit the
job for processing.
CACR217E DATA BASE ERROR; CPL ADDRESS= xxxxxx RC= xx xx xx

Explanation: An internal error has occurred.
User Response: Contact Computer Associates Technical Support. Be prepared to
communicate the exact content of this message to Computer Associates Technical
Support.
For an explanation of R/C= xxxx, see the chapter "Catalog Management Return Codes" in
the CA90s Services Message Guide.
CACR218I DEBUG INFORMATION xxxxxxxx xxxxxxxx = xxxxxxxx

Explanation: The displayed information results from the -DEBUG option.
User Response: Review the displayed information and take the appropriate action.
CACR219I CA-DRIVER DEBUG HAS BEEN xxxxxxxx

Explanation: The -DEBUG option of CARUTIL has been enabled or disabled (xxxxxxxx).
CACR220E FUNCTION INVALID FOR ONLINE EXECUTION

Explanation: The requested function is invalid in an online environment.
User Response: Correct the statement in error and resubmit the job for processing.
CACR221E CA-DRIVER 'AR' COMMAND IS INVALID.

Explanation: The 'AR' command is not known to Unicenter CA-Driver.
User Response: Reenter a valid Unicenter CA-Driver command.

1.4 CACR Messages
CACR290I CA-DRIVER 'AR' COMMAND IS INVALID

Explanation: The previously entered command is not recognizable as a valid Unicenter
CA-Driver AR command.
CACR300E I/O ERROR ON DRIVER PROCEDURE LIBRARY F/C=xx A/C=xx R/C=xxxx,xxxxxxxx

RECID=xxx
Explanation: An I/O error occurred while trying to access the the Unicenter CA-Driver
procedure library.
CACR301E RDR CLASS NOT DEFINED FOR THIS PARTITION

Explanation: A job is being processed in this partition under the control of Unicenter
CA-Driver, but no alphabetic class code was defined for this partition in the CLASS=
parameter of the CARGEN installation macro.
User Response: Each partition which is to run jobs under the control of Unicenter
CA-Driver must have a class code defined in the CARGEN installation macro. The
system must be regenerated if jobs are to be run in this partition.
CACR302E POWER INTERFACE FAILURE R/C=xx

Explanation: An error was returned to Unicenter CA-Driver from an execution of a
POWER segment macro.
User Response: For the return code contained in this message, see the chapter "Segment
Macro" in the VSE/POWER Installation And Operations Guide.
CACR303E INVALID SYNTAX

Explanation: This may be caused by:
1. An equal sign does not separate the operands of a // SET statement.
2. Two consecutive commas were encountered on a // COPTION statement.
3. Two consecutive commas were encountered on a // PROC statement.
CACR304E INVALID RELATIONAL OPERATOR

Explanation: The comparison operator on an // IF statement is not valid. This operator
must be GE, LE, LT, GT, EQ, or NE.

1.4 CACR Messages
CACR305E STATEMENT NOT COMPLETE

Explanation: The statement does not contain all of the required operands. Check for
violation of Unicenter CA-Driver continuation rules, as it is likely a parameter and its
associated value are not on the same statement.
CACR306E PROC = xxxxxxxx DATA-NAME = yyyyyyyy DOES NOT MATCH

EOD-NAME = zzzzzzzz
Explanation: The data verification name (DATA-NAME = yyyyyyyy) in the displayed
procedure does not match the verification name supplied on the null PROC statement
(EOD-NAME = zzzzzzzz).
User Response: Correct the data verification name and resubmit the job for processing.
CACR307E PROC = xxxxxxxx EXCEEDS MAXIMUM NESTED PROCS

Explanation: The displayed procedure is a nested procedure which has exceeded the
number of allowable nests, as specified in the NEST= parameter of the CARGEN
installation macro. The nested PROC statement is ignored.
User Response: Enter CANCEL to cancel the job, or press END or ENTER to continue,
and ignore the statement. Correct the problem by removing the nested PROC statement
from calling procedure, or increase the number of allowable nests by regenerating the
system after changing the CARGEN macro.
CACR308E PROC = xxxxxxxx END OF JOB WITHOUT PROC END-OF-DATA STATEMENT

Explanation: The end of the job set (DOS or POWER job) has been reached during the
data inclusion process, without having encountered a null PROC statement.
User Response: A null PROC statement is assumed as the last statement of the job set.
Data inclusion terminates normally. Ensure that data inclusion terminated in the correct
place. Correct the job stream by placing a null PROC statement (// PROC,) after the
data to be included.
CACR309E PROC = xxxxxxxx NOT FOUND

Explanation: The displayed procedure was not found in the procedure library, or the
procedure was misspelled.
User Response: Correct the procedure library or the spelling of the procedure, and
resubmit the job for processing.
CACR310E PROC = xxxxxxxx CONTINUATION EXPECTED, NONE FOUND

Explanation: Continuation is indicated because the last parameter on a PROC or
subsequent continuation statement is followed by a comma, but the next statement does
not begin with a plus sign (+).

1.4 CACR Messages
CACR311W PROC = xxxxxxxx BLANK CONTINUATION. STATEMENT IGNORED.

Explanation: A continuation statement begins with a plus sign (+), but the remainder of
the statement is blank. The continuation statement is ignored. The job is processed.
User Response: Correct the failing job stream to avoid further error messages.
CACR312E INVALID CONDITION PARAMETER

Explanation: The first operand of a // SET statement or an // IF statement is not
valid. The statement is ignored.
User Response: Press END or ENTER to continue, or respond CANCEL to cancel the
job. For valid formats and operands, see the chapter "Conditional Execution" in the
Unicenter CA-Driver Reference Guide.
CACR313E UNRECOGNIZABLE OR INCOMPATIBLE VALUE SPECIFICATION

Explanation: The value operand of an // IF statement (the operand after the
comparison operator) is not valid, or it is incompatible with the first operand (such as
comparing the system variable SYS to an 8-byte data field). The statement is ignored.
User Response: Press End or Enter to continue or respond CANCEL to cancel the job.
Correct the statement in error after referring to the section on conditional execution
statements in the Unicenter CA-Driver Reference Guide.
CACR314E INVALID VALUE PARAMETER

Explanation: The value operand of an // IF or // SET statement is not valid. The
User Response: Press End or Enter to continue, or respond CANCEL to cancel the job.
Correct the statement in error after referring to the section on conditional execution
statements in the Unicenter CA-Driver Reference Guide.
CACR315E PROC = xxxxxxxx PARM = yyyyyyyy zzzzzzzzzzzzzzz

Explanation: zzzzzzzzzzzzzzz is a message which indicates one of the following errors:
1. NOT DEFINED - the displayed parameter was found on a PROC statement, but it is
not defined as a variable parameter in the procedure.
2. NO OVERRIDE GIVEN - the displayed parameter was found on a PROC statement,
but no value followed the parameter.
3. UNBALANCED OVERRIDE DELIMITERS - an opening character string delimiter
was found, but the closing delimiter was not found.
4. REQUIRED OVERRIDE NOT GIVEN - the displayed parameter is referenced during
procedure expansion; it has no default value, and no overriding value was supplied
on the calling PROC statement.
5. INVALID SYNTAX - the syntax of the calling PROC statement is not correct. Check
for multiple consecutive commas or improper continuation.

1.4 CACR Messages
6. NONSUBSCRIPTED PARM REFERENCING AN ARRAY - a reference to a variable

parameter array was made with no subscript (index) following the variable parameter
to indicate which element of the variable parameter array is being referenced.
7. SUBSCRIPTED PARM DOES NOT REF AN ARRAY - a subscript (index) was found
following a variable parameter that was not defined as a variable parameter array.
8. OVERRIDE EXCEEDS ARRAY DIMENSION - more override values were supplied
on the PROC statement than there are elements defined in the variable parameter
array.
9. SUBSCRIPT IS NOT POSITIVE NUMBER - the value of the subscript was not a
positive number.
10. OVERRIDE OF GLOBAL NOT ALLOWED - an attempt was made to override a
global.
The job is canceled.
User Response: Correct the error and resubmit the job for processing.
CACR316E PROC = xxxxxxxx, STATEMENT NO=nnnnn yyyyyyyyyyyyyyy

Explanation: yyyyyyyyyyyyyyy is a message which indicates one of the following
errors:
1. PARM OVERRUN - The replacement of a variable parameter with its associated
value has caused the contents of the statement to be shifted past position 80.
2. SUBSCRIPT EXCEEDS ARRAY LIMITS - a variable parameter array is being
referenced using a subscript that is larger than the number of elements in the array.
3. SUBSTRING POSITION OUTSIDE VARIABLE SIZE - the substring notation used on
the statement references a past position greater than the length of the variable
parameter value.
4. SUBSTRING LENGTH OUTSIDE VARIABLE SIZE - the substring notation length
field specification exceeds the maximum length for a variable parameter value.
5. SUBSTRING POS OUTSIDE RANGE OF VALUE - the substring position specification
is not within the boundary of the size assigned to the variable parameter.
6. SUBSTRING LEN OUTSIDE RANGE OF VALUE - the substring length specification
plus the starting position is not within the boundary of the size value assigned to the
variable parameter.
7. SET ARITHMETIC FIELD NOT NUMERIC - a field being used in an arithmetic
expression on a -SET statement is not a numeric field.
8. SET ARITHMETIC OVERFLOW EXCEPTION - the result of an arithmetic expression
on a -SET statement is larger than 65535.
9. SET STATEMENT DIVISION BY ZERO - an attempt was made to divide by zero in a
-SET statement arithmetic expression.
10. SUBSCRIPT VARIABLE IS NOT A POSITIVE NUMBER - a variable parameter being
used as a subscript (index) does not have an assigned value that is a positive number.

1.4 CACR Messages
11. SUBSCRIPT VARIABLE VALUE OMITTED - a variable parameter being used as a

subscript (index) has no associated value.
12. SUBSTRING POSITION NOT A POSITIVE NUMBER - the variable parameter being
used as the position field in substring notation has a value that is not a positive
number.
13. SUBSTRING POSITION VALUE OMITTED - the variable parameter being used as
the position field in substring notation has no associated value.
14. SUBSTRING LENGTH NOT A POSITIVE NUMBER - the variable parameter being
used as the length field in substring notation has a value that is not a positive
number.
15. SUBSTRING LENGTH VALUE OMITTED - a variable parameter being used as the
length field in substring notation has a value that is not a positive number.
16. VARIABLE MUST BE NUMERIC - a variable parameter is being used in a manner
that requires it to have a numeric value, and it does not.
17. VARIABLE MUST NOT BE ZERO - a variable parameter is being used in a manner
that requires it to have a nonzero value, yet its value is zero.
18. VARIABLE MUST BE A POSITIVE NUMBER - a variable parameter is being used in
a manner that requires it to have a positive integer value, and it does not.
19. LCTR IS NOT A POSITIVE NUMBER - the -LCTR statement is being used to set the
step counter, but the value to be used for the counter is not a positive integer.
20. REFERENCED VARIABLE HAS NO VALUE - a variable parameter is being
referenced, but no value has been supplied for the variable parameter. A variable
parameter cannot be referenced unless it has an associated value. It may have a null
value, but a null value must be explicitly stated.
21. VALUE OF REFERENCED VARIABLE TOO LONG - the value referenced exceeds
the length allowed for this type of statement.
User Response: Correct the problem and resubmit the job for processing.
CACR317E COPTION = xxxxxxxx IS UNRECOGNIZABLE

Explanation: The operand of a // COPTION statement is not valid. Valid operands are
SLOG, NOSLOG, FLUSH, and NOFLUSH.
CACR318E MORE THAN 10 COPTIONS GIVEN

Explanation: More than 10 operands were found on a // COPTION statement; only 10
are allowed.
User Response: Correct the // COPTION statement in error and resubmit the job for
processing.

1.4 CACR Messages
CACR319E FLUSH IS A RESERVED WORD

Explanation: A // STEP statement was encountered with a step name of FLUSH.
FLUSH is not a valid step name.
User Response: Change the step name to something other than FLUSH if it is to be
referenced. Then resubmit the job for processing.
CACR320E WORD GREATER THAN 8 CHARACTERS

Explanation: A user-supplied keyword, step name, parameter name, or option exceeds
eight characters.
CACR321E USER PARAMETER IS INVALID

Explanation: A user variable was referenced, but the user variable does not exist in this
Unicenter CA-Driver system.
CACR322I A POWER JOB/EOJ CARD FOUND WHILE SUBMITTING DRIVER PROCEDURE

FROM Scheduler
Explanation: POWER JOB and EOJ statements are not allowed in Unicenter CA-Driver
procedures submitted from Unicenter CA-Scheduler. The statement is commented and
ignored.
User Response: Remove the statement from the procedure.
CACR324E INSUFFICIENT STORAGE FOR EXECUTION

Explanation: A GETVIS request by the preprocessor resulted in a bad return code,
indicating insufficient GETVIS storage.
User Response: Increase the partition size of the partition in error. (Example: Unicenter
CA-Driver preprocessor EXEC with a size of 24K.)
CACR325E NO PROC NAME GIVEN

Explanation: A PROC statement was encountered with no procedure name specified,
and data inclusion is not in operation.
CACR326E STEP xxxxxxxx IN PROC yyyyyyyy HAS EXCEEDED THE LOOP COUNTER
Explanation: The displayed step has been referenced in excess of the number of times
allowed by the value of the loop counter (-LCTR value). Procedure expansion is
terminated, and the job is canceled.
User Response: Correct the logic error that caused the problem or, if none exists,
increase the value of the loop counter using the CARUTIL -LCTR statement.

1.4 CACR Messages
CACR327E STEP TABLE HAS BEEN EXCEEDED IN PROC xxxxxxxx

Explanation: There are too many steps defined in the procedure, or the value of the
CARSTEP parameter of the CAIRGEN macro is too small.
User Response: Increase the value of CARSTEP, or break the procedure into multiple
procedures.
CACR328E COULD NOT LOCATE CARCTBLO SVA PHASE

Explanation: The Unicenter CA-Driver Partition Table Handler is not resident in the
SVA.
User Response: Load CARCTBLO into the SVA.
CACR329E NO CLOSING PAREN FOR PASSWORD ON PROC CARD

Explanation: The password for a procedure did not have a closing parenthesis.
CACR330E EXPECTED CONTINUATION NOT FOUND ON PROC CARD

Explanation: The -PROC statement expected another statement, and the card read was
not a continuation.
CACR331E INVALID SYNTAX ON PROC CARD

Explanation: The -PROC statement contains a syntax error.
CACR337E PASSWORD SYNTAX ERROR

Explanation: The password on the -PROC statement is invalid.
User Response: Correct the password and resubmit the job for processing.
CACR338W NO SECURITY PROTECTION. PASSWORD NOT REQUIRED.

Explanation: A password was provided when it was not required. The password is
ignored; the procedure is expanded as if the password had not been supplied.
User Response: Remove the password from the -PROC statement.
CACR339E NO PASSWORD GIVEN. PROC FLUSHED.

Explanation: No password was supplied on a -PROC statement calling a procedure that
is password-protected. The procedure is not expanded.
User Response: Supply the correct password to retrieve the procedure.

1.4 CACR Messages
CACR340E INCORRECT PASSWORD FOR PROC= xxxxxxxx

Explanation: The supplied password for the procedure is incorrect. The procedure is
not expanded.
User Response: Supply the correct password on the calling -PROC statement to retrieve
the procedure.
CACR341E INVALID OR MISSING SUBMIT OPTION(S)

Explanation: A keyword parameter other than JOB, CLASS, or PRI was found on a //
SUBMIT statement.
CACR342E SUBMIT JOB NAME GREATER THAN 8 CHARACTERS

Explanation: The job name parameter is longer than the maximum allowable eight
characters.
User Response: Correct the job name parameter and resubmit the job for processing.
CACR343E SUBMIT CLASS GREATER THAN 1 CHARACTER

Explanation: The class parameter of the SUBMIT statement was more than the allowed
one character.
User Response: Correct the class parameter and resubmit the job for processing.
CACR344E SUBMIT PRI GREATER THAN 1 CHARACTER

Explanation: The PRI parameter of the SUBMIT statement was not a single character
(numeric only).
User Response: Correct the PRI parameter and resubmit the job for processing.
CACR345E SUBMIT CLASS IS NOT A-Z

Explanation: The SUBMIT statement class parameter must be specified as a single
alphabetic character, but this was not the case.
User Response: Correct the class parameter on the SUBMIT statement and resubmit the
job for processing.
CACR346E SUBMIT PRIORITY IS NOT 0-9

Explanation: The SUBMIT statement PRI= parameter must be specified as a single
numeric character in the range zero to nine.
User Response: Correct the PRI= parameter on the SUBMIT statement and resubmit the
job for processing.

1.4 CACR Messages
CACR347E SUBMIT END OUT OF SEQUENCE

Explanation: A // SUBMIT END statement was encountered, but no prior SUBMIT
statement to begin automatic job submission was encountered.
CACR348E SUBMIT CTL ERROR FOUND.

Explanation: This message follows any one of several error messages regarding SUBMIT
statement errors.
CACR349E END OF INPUT WITHOUT END OF SUBMIT

Explanation: Job submission was initiated with a SUBMIT statement, but the end of the
job set was encountered before finding a // SUBMIT END statement.
CACR350E INVALID JOB NAME ON // SUBMIT STATEMENT

Explanation: The job name on the SUBMIT control statement is invalid.
User Response: Correct the job name and resubmit the job for processing.
CACR351E DISP PARM OF // SUBMIT STATEMENT TOO LONG

Explanation: The DISP parameter on the SUBMIT control statement must be one
character in length.
User Response: Correct the DISP parameter and resubmit the job for processing.
CACR352E DISP SPECIFICATION INVALID ON // SUBMIT STATEMENT

Explanation: The DISP parameter on the SUBMIT control statement is not a valid
POWER disposition.
User Response: Correct the DISP parameter and resubmit the job for processing.
CACR353E SYSID PARM OF // SUBMIT STATEMENT TOO LONG

Explanation: The SYSID parameter on the SUBMIT control statement must be one
character in length.
User Response: Correct the SYSID parameter and resubmit the job for processing.
CACR354E SYSID SPECIFICATION INVALID ON // SUBMIT STATEMENT

Explanation: The SYSID parameter on the SUBMIT control statement must be a single
digit integer from one to nine inclusive.
User Response: Correct the SYSID parameter and resubmit the job for processing.

1.4 CACR Messages
CACR355E SSL CALL LEVEL EXCEEDS 20, EXPANSION TERMINATED

Explanation: -INPUT statements are nested more than 20 levels.
CACR356E SSL MEMBER A.xxxxxxxx NOT FOUND, EXPANSION TERMINATED

Explanation: The SSL member on the -INPUT statement could not be located.
CACR357E INVALID -INPUT STATEMENT FORMAT

Explanation: The -INPUT statement parameters are not recognized.
User Response: Correct the parameters in error and resubmit the job for processing.
CACR358E ERROR HAS OCCURRED DURING SSL CALL F/C=xx R/C=yyyy

Explanation: An error occurred during the reading of an SSL member.
User Response: Check the return codes and the spelling of the member name.
CACR359E STEP xxxxxxxx IN PROC xxxxxxxx WAS NOT FOUND

Explanation: The step name is either misspelled or has been left out of the member.
User Response: Correct the step name that is in error or insert the missing step name.
Then, reprocess the job.
CACR360E INVALID VM STATEMENT FORMAT

Explanation: The // VM statement is not formatted properly.
CACR361E CP COMMAND xxxxxxxx NOT ACCEPTED

Explanation: The specified CP command is not allowed.
User Response: Remove the statement in error.
CACR362I A CP COMMAND IS ABOUT TO BE ISSUED TO VM

Explanation: Indicates a CP command will be executed. This message is issued
immediately prior to every execution of a CP command.
CACR363E DYNAM SYSTEM NOT ACTIVE - DYNAM CPUID IS NOT VALID

Explanation: DYNAM has not been activated or is not on the system.
User Response: Remove the request for the CPUID or enable the CA-Dynam family.

1.4 CACR Messages
CACR364E LDEST PARM OF // SUBMIT STATEMENT TOO LONG

Explanation: The LDEST parameter on the SUBMIT control statement cannot be longer
than 20 characters.
User Response: Correct the LDEST parameter and resubmit the job for processing.
CACR365E LDEST SPECIFICATION INVALID ON // SUBMIT STATEMENT

Explanation: The LDEST parameter on the SUBMIT control statement is invalid.
CACR366E PDEST PARM OF // SUBMIT STATEMENT TOO LONG

Explanation: The PDEST parameter on the SUBMIT control statement cannot be longer
than 20 characters.
User Response: Correct the PDEST parameter and resubmit the job for processing.
CACR367E PDEST SPECIFICATION INVALID ON // SUBMIT STATEMENT

Explanation: The PDEST parameter on the SUBMIT control statement is invalid.
CACR370I .......... BEGIN PROC ====> xxxxxxxx EXPANSION

Explanation: Procedure expansion has begun during procedure modeling. xxxxx=
Procedure name.
CACR371I END PROCEDURE xxxxxxxx EXPANSION

Explanation: Procedure expansion has ended during procedure modeling.
CACR372I BEGIN DATA xxxxxxxx INCLUSION

Explanation: Data inclusion has begun during procedure modeling.
CACR373I END DATA xxxxxxxx INCLUSION

Explanation: Data inclusion has ended during procedure modeling.
CACR390E INTERNAL LOGIC ERROR HAS OCCURRED

Explanation: An irrecoverable condition has occurred during Unicenter CA-Driver
preprocessor execution.

1.4 CACR Messages
CACR391E PLEASE ISSUE AR DUMP COMMAND FOR THIS PARTITION THEN REPLY 'EOB'
TO THIS MESSAGE
Explanation: An internal logic error has occurred.
User Response: Perform an AR partition dump. Enter 'EOB.' Then contact Computer
CACR397I 'STOP' IS NOT A VALID REPLY AT THIS TIME

Explanation: Replying 'STOP' to this message is not valid at this time.
CACR398I xxxxxxxx - USER DEFINED MESSAGE

Explanation: A -WTO command has been issued for procedure xxxxxxxx.
User Response: The action is dependent upon user-defined text.
CACR399R ENTER REPLY

Explanation: A -REPLY request has been issued from a procedure.
User Response: The action is dependent upon the previous -WTO.
CACR400I CA-DRIVER IS xxxxxxxxxxxx JOB nnnnnnnnnn -START-/-END-

Explanation: Informational message that tells the user that this job is
MODELING/PUNCHING Job nnnnnnnnnnnn. There is a message at the -START- and at
the -END-.
CACR401I FLUSHED TO STEP xxxxxxxx

Explanation: The JCL has been flushed to the displayed step during conditional
execution.
CACR402I STEP xxxxxxxx HAS BEEN BYPASSED

Explanation: The displayed step has been bypassed during conditional execution.
CACR403I ALL STEPS FLUSHED

Explanation: All steps have been bypassed during conditional execution.

1.4 CACR Messages
CACR404I STEP xxxxxxxx NOT FOUND. ALL STEPS FLUSHED.

Explanation: The JCL was flushed at EOJ because the requested step was not found
during conditional execution.
CACR405I STEP xxxxxxxx

Explanation: The requested step was found during conditional execution. (Step logging
must be in effect.)
CACR406I CA-DRIVER HAS BEEN DISABLED FOR THIS JOB.

Explanation: Informational message that tells the user that this job has had Unicenter
CA-Driver disabled.
CACR407E CA-DRIVER HAS DETECTED AN ERROR IN CARURDRA.

Explanation: Unicenter CA-Driver has detected an error in CARURDRA. Take an 'AR'
Dump at the console reply.
User Response: Perform an 'AR' dump.
CACR408E CA-DRIVER GENERATION PHASE IS NOT AT REQUIRED LEVEL. PLEASE

REGENERATE.
Explanation: The Unicenter CA-Driver generation macro has not be reassembled with
the current release.
User Response: Reassemble generation macro and re-IPL.
CACR450E TLBL VOL SER LENGTH INCORRECT

Explanation: The BrightStore CA-Dynam/TLMS interface has detected an error in the
TLBL VOL SER field.
User Response: Correct the field and resubmit the job for processing.
CACR451E TLBL GENERATION NUMBER NOT NUMERIC

TLBL generation number.
User Response: Correct the number and resubmit the job for processing.
CACR452E TLBL GENERATION NUMBER TOO LONG

TLBL generation number.

1.4 CACR Messages
CACR453E TLBL VOLUME SEQUENCE NUMBER NOT NUMERIC

TLBL volume sequence number.
CACR454E TLBL VOLUME SEQUENCE NUMBER TOO LONG

TLBL volume sequence number.
CACR455E CARMSG PARAMETER INVALID ON TLBL DSN=xxxxxxxx

TLBL CARMSG parameter.
User Response: Correct the parameter and resubmit the job for processing.
CACR456E CARMSG NUMBER OF TAPES INCORRECT DSN=xxxxxxxx

TLBL CARMSG NUMBER OF TAPES parameter.
User Response: Correct the parameter and resubmit the job for processing.
CACR457E I/O ERROR WHILE TRYING TO ACCESS THE DYNAM/T CATALOG

F/C=xxxx R/C=yyyyyyyy RECID=zzzz
Explanation: An I/O error has occurred while while trying to access the DYNAM/T
catalog.
CACR458E DYNAM/T IS NOT ACTIVE

Explanation: The BrightStore CA-Dynam/TLMS interface has been requested, but
BrightStore CA-Dynam/TLMS is not active in the system.
User Response: Determine why BrightStore CA-Dynam/TLMS is not active, or remove
the Dynam/T option in the Unicenter CA-Driver generation options.
CACR459E REQUESTED DSN VERSION IS NOT A TAPE DATASET

Explanation: The BrightStore CA-Dynam/TLMS interface has been requested, but the
requested DSN is not a tape DSN.
User Response: Correct the request and resubmit the job for processing.

1.4 CACR Messages
CACR500I Unicenter CA-Driver RELEASE v.m GENLEVEL vmyymmrdvmn HAS BEEN

INITIALIZED
Explanation: Unicenter CA-Driver has been initialized.
CACR501I CA-DRIVER HAS BEEN ENABLED FOR PP PARTITION

ENABLED
DISABLED FOR PP PARTITION(S)
DISABLED
PP = Partition ID
Explanation: Unicenter CA-Driver has been enabled for PP partition. Where PP is the
partition ID. All JCL processed in that partition will be scanned for any Unicenter
CA-Driver control statements.
Unicenter CA-Driver has been disabled for PP partition. Where PP is the partition ID.
All JCL processed in that partition will not be scanned for any Unicenter CA-Driver
control statements.
Unicenter CA-Driver has been disabled for ALL partitions. All JCL processed for all
partitions will not be scanned for any Unicenter CA-Driver control statements.
User Response: This is an informative message only, indicating the status of the
Unicenter CA-Driver reader exit processing. These messages are displayed in response to
the following
// CARCTL JCL or the DR AR command:
// CARCTL command DR command

// CARCTL ENABLE,pp DR ENABLE,pp
// CARCTL ENABLE, DR ENABLE
// CARCTL DISABLE,pp DR DISABLE,pp
// CARCTL DISABLE, DR DISABLE
// CARCTL OFF
CACR502E NO MORE STORAGE FOR RDR TABLES - INPUT FLUSHED

Explanation: The number of VSE RDRs exceeds the available amount of GETVIS storage
in the partition.
User Response: Add more GETVIS storage in partition.
CACR503E CA-DRIVER SUBMIT TABLE NOT FOUND.

Explanation: Unicenter CA-Driver was unable to find CARCTBLO.
User Response: Make sure that CARCTBLO is in one of the libraries that is in your
LIBDEF search.

1.4 CACR Messages
CACR504E END OF TASK ADR NOT FOUND

Explanation: The address of $IJBSEOT could not be located during Unicenter CA-Driver
initialization.
User Response: Correct and re-IPL.
CACR506I CA-DRIVER CONDITIONAL EXECUTION DISABLED

Explanation: CA-DRIVER conditional execution has been disabled. Refer to the error
message that precedes this one for the specific reason.
User Response: See the error message that precedes this one for a specific action.
CACR507E CDLOAD FAILURE FOR PHASE 'xxxxxxxx' R/C=yy

Explanation: The displayed phase could not be loaded.
User Response: See the VSE/Advanced Functions Macro Reference.. Look in the CDLOAD
section for the displayed return code (yy) to determine the appropriate action.
CACR509E NO GETVIS FOR USER EXIT xxxxxxxx INCREASE SIZE AND RE-IPL
Explanation: An attempt was made to load the user's POWER reader exit, but there was
insufficient GETVIS in the POWER partition.
User Response: Increase the GETVIS in the POWER partition and re-IPL.
CACR512I CA-DRIVER PARTITION PP - STATUS xxxxxx

Explanation: Unicenter CA-Driver displays the current status of all partitions that have
had any activity.
pp = Partition ID
xxxxx = ENABLE partition is available for Unicenter CA-Driver processing.
DISABLE partition has been disabled. No Unicenter CA-Driver processing
will occur.
RUNNING partition is processing a Unicenter CA-Driver controlled job.
User Response: These are informative messages indicating the status of the Unicenter
CA-Driver controlled partitions.
CACR513E CA-DRIVER CAIRGEN RELOAD FAILURE

Explanation: Unicenter CA-Driver reloaded the CAIRGEN macro or CA-DRIVER was
unable to reload the CAIRGEN macro for one of the following reasons:
1. Cannot delete old CAIRGEN macro from system.
2. Cannot reload Unicenter CA-Driver controlled partitions running.
3. CAIRGEN macro was not removed from the SDL list.
User Response: Correct error and retry function or contact Computer Associates
Technical Support.

1.4 CACR Messages
CACR513I CA-DRIVER CAIRGEN RELOAD SUCCESSFUL

Explanation: Unicenter CA-Driver reloaded the CAIRGEN macro.
1. Deleted old CAIRGEN macro from system.
2. Reloaded Unicenter CA-Driver controlled partitions running.
3. CAIRGEN macro was removed from the SDL list.
User Response: None
CACR514I CA-DRIVER AVERAGE BUFFERS=bbbbbbb JOBS=jjjjjjjjjj TOTAL BUFFERS=tttttttttt

MAX BUFFER=nnnnnnn
Explanation: This is a response to the DR BUFSTATS command, where bbbbbbb equals
the number of records currently held in the temporary JCL file at job end, jjjjjjjjjj is the
number of jobs Unicenter CA-Driver has processed since IPL, tttttttttt is the total number
of records used by all jobs, and nnnnnnn is the highest number of buffers used.
CACR520E CARCTBL FUNCTION ERROR, FUNCTION=xxxxx

Explanation: The Unicenter CA-Driver partition handler (CARCTBL0) detected an error
while trying to perform function xxxxx. Functions are RUN, INFO, ENABLE.
User Response: Try disabling and then enabling the partition in error. If that does not
correct the problem, contact Computer Associates Technical Support for assistance.
CACR600E
GLOBAL AREA NOT FOUND
NO STORAGE AVAILABLE
xxxxx - IS UNKNOWN SCHEDULER FUNCTION
xxxxx - DATE TABLE NOT FOUND
CAM I/O ERROR WHILE READING DATE TABLE
DATE TABLE OVERFLOW OR UNDERFLOW
END OF PERIOD CANNOT BE FOUND
ILLEGAL CYCLE PREFIX OR PREFIX NOT SPECIFIED
NOT IN RANGE 1 TO 365/366
RELATIVE DAY NOT NUMERIC
NOT FOUND BY CA-DRIVER
IS AN INVALID JULIAN DATE
ERROR IN DATE PROCESSING
ALLOWED RANGE IS 1-36600
ALLOWED RANGE IS 1-1200
NOT A POSITIVE INTERGER
IS AN INVALID DATE
ERROR DURING STORAGE ALLO/DEALLO
VARIABLE UNDEFINED OR NULL VALUE
...SYNTAX ERROR IN FUNCTION CALL
...LOAD FAILURE
...FUNCTION CALL IS UNDEFINED
...ARGUMENT IS TOO LONG/OR NULL
...ARGUMENT MUST BE NUMERIC

1.4 CACR Messages
CACR601D –CACR607E
ARGUMENT IS MISSING
...ARGUMENT MUST BE ALPHANUMERIC
...ARGUMENT MUST BE ALPHABETIC
VARIABLE NAME IS INVALID
RELATIVE DAY EXCEEDS MONTH RANGE
Explanation: Unicenter CA-Driver/Unicenter CA-Scheduler date functions have found
an error.
User Response: Correct error and rerun job.
CACR601D ENTER NEW DRIVER OPTIONS OR (EOB, LIST OR LIST=PRINT)

Explanation: This is an invitation for operator response.
User Response: Enter a new DRIVER option, EOB to terminate, or enter LIST or
LIST=PRINT to list existing options on the console or system printer respectively.
CACR602E INVALID PARAMETER - USE LIST COMMAND FOR FORMAT

Explanation: The entered request was in error.
User Response: Use the LIST command to determine the correct format. Then reenter
the request.
CACR603I REQUESTED CHANGE COMPLETED

Explanation: The requested parameter change has been made and will be in effect for
the next program execution.
CACR604I CHANGE WILL BE IN EFFECT WHEN POWER IS RESTARTED

Explanation: The requested parameter change has been made and will be in effect after
POWER is brought down and restarted.
CACR605I CHANGE WILL BE IN EFFECT WHEN SCHEDULER MONITOR IS RESTARTED

Explanation: The requested parameter change has been made and will be in effect after
the Unicenter CA-Scheduler monitor is brought down and restarted.
CACR607E PARAMETER CHANGE REQUEST NOT ACCEPTED

Explanation: A request was made to change a parameter which cannot be changed.

1.4 CACR Messages
CACR608E DRIVER NOT ACTIVE

Explanation: The Unicenter CA-Driver system is not active. CA-DRIVER must be active
for changes to be made.
User Response: Initialize the Unicenter CA-Driver system.
CACR701E INVALID CTL KEYWORD

Explanation: A keyword on a // CTL CARCOM statement was other than CLASS,
NAME, PRI, DISP, SYSID, LDEST, or PDEST. The statement is ignored.
User Response: Enter a correct // CTL statement from the console.
CACR702E NO CTL PARAMETERS GIVEN

Explanation: A // CTL statement was entered with no parameters. The statement is
ignored.
User Response: Enter a // CTL statement with at least one valid keyword parameter, if
a // CTL statement is needed.
CACR703E CLASS IS NOT A SINGLE ALPHABETIC A-Z

Explanation: The value for the class parameter was not a single letter A-Z. The class
User Response: The // CTL statement must be reentered with a correct class parameter.
CACR704E PRI IS NOT A SINGLE NUMERIC 0-9

Explanation: The PRI parameter value was not a single digit 0-9. The PRI parameter is
ignored.
User Response: The // CTL statement must be reentered with a correct priority, if
needed.
CACR705E SYNTAX ERROR

Explanation: An equal sign does not separate a keyword parameter from its value, or a
keyword does not have a specified value. The // CTL statement in error is ignored.
User Response: Reenter the // CTL statement correctly.
CACR706E POWER INTERFACE FAILURE, RET-CODE=xx.

Explanation: POWER S.A.S has passed an abnormal return code. The job is canceled.
User Response: For further explanation of the return code, see the IBM DOS/VSE
POWER Installation Guide and Reference Manual. Ensure that all PUTSPOOL requirements
are met. If no valid reason can be determined for the abnormal return code, contact
Computer Associates Technical Support for assistance.

1.4 CACR Messages
CACR707E SYSIPT IS UNASSIGNED WITH DATA INCLUSION

Explanation: A // DATA statement has been encountered and SYSIPT is not assigned.
User Response: Correct the assignments in error and resubmit the job for processing.
CACR708E SYSPCH IS UNASSIGNED

Explanation: SYSPCH must be assigned to a punch device (controlled by POWER) when
executing CARCOM. The job is canceled.
User Response: Assign SYSPCH to a punch device controlled by POWER, then execute
CARCOM again.
CACR709I END OF DATA INCLUSION

Explanation: Data inclusion has ended.
CACR710A ENTER CARCOM STATEMENT

Explanation: CARCOM has been executed, and is calling for input from the console. A
read is issued to the system console.
User Response: Enter the statements desired, then press END or ENTER. CARCOM is
terminated by entering an // END statement.
CACR711E SYSID IS NOT A SINGLE NUMERIC 0-9

Explanation: The SYSID parameter value was not a single digit 0-9. The SYSID
User Response: The // CTL statement must be reentered to specify a correct SYSID, if
needed.
CACR712E DISP IS NOT A SINGLE ALPHABETIC A-Z

Explanation: The value for the DISP parameter was not a single letter A-Z. The DISP
User Response: The // CTL statement must be reentered to specify a correct DISP
parameter.
CACR713E PUTSPOOL ENQUEUE HAS TIMED OUT

Explanation: CARCOM attempted to establish communication with POWER through the
PUTSPOOL interface and could not establish a connection after multiple retries.
User Response: Investigate why PUTSPOOL was not available.

1.4 CACR Messages
CACR715E XECTTAB TYPE=DELETE ERROR HAS OCCURRED R/C=xx

Explanation: An error occurred when the PUTSPOOL communication ECB was deleted.
User Response: See the VSE/Advanced Functions Macro Reference.. Look for the displayed
return code (xx) in the XECB Macro section to determine the appropriate action.
CACR716E LDEST PARM IS INVALID

Explanation: An error was detected in the LDEST parameter of the CARCOM // CTL
statement.
CACR717E PDEST PARM IS INVALID

Explanation: An error was detected in the PDEST parameter of the CARCOM // CTL
statement.
CACR900E INITIALIZATION NOT ALLOWED, CA-SCHEDULER MONITOR IS ACTIVE

Explanation: Initialization cannot be performed when the Unicenter CA-Scheduler
monitor is active.
User Response: Rerun the job when the monitor has been brought down.
CACR901A IS CA-SCHEDULER/DRIVER ACTIVE ON ANY OTHER CPU

Explanation: In a shared environment this message is displayed to determine whether
Unicenter CA-Scheduler or Unicenter CA-Driver is active on any other CPU.
User Response: Answer YES if either is active and NO if both are not.
CACR902E INVALID OR MISSING CONTROL CARD

Explanation: A control statement is either missing or in error.
User Response: Add or correct the control statement and resubmit.
CACR903A INITIALIZE xxxxxxxx DATABASE (YES/NO) ?

Explanation: This informational message ensures that you are aware that the DRIVER
library is about to be used. xxxxxxxx represents the database name.
User Response: Answer YES to initialize the library and NO to stop the initialization.
CACR904I DATABASE xxxxxxx HAS BEEN INITIALIZED

DATABASE xxxxxxxx WAS NOT INITIALIZED
Explanation: This message acknowledges your reply to message CACR903A. xxxxxxxx
represents the database name.

1.4 CACR Messages
CACR905W INSUFFICIENT DISK SPACE ALLOCATED FOR xxxxxxxx.

Explanation: The initialization program has determined that there might not be enough
space for all the requested procedures. xxxxxxxx represents the database name.
User Response: Examine the requirements for the procedure library, and disregard this
message if you think you have sufficient space for your needs.
CACR905E INSUFFICIENT DISK SPACE ALLOCATED FOR xxxxxxxx.

Explanation: Note that the text of this message is the same as the previous message
except that an E, not a W, is present at the end of the message ID. The initialization
program has determined that there is not enough space for all the requested procedures.
xxxxxxxx represents the database name.
User Response: Increase the size of the procedure library or decrease the value of
NJOBS.
CACR906E PREMATURE EOF ON INPUT. CONTROL CARD IS NECESSARY TO INITIALIZE

CA-DRIVER LIBRARY
Explanation: A control statement is missing.
User Response: Ensure that the control statement is present and resubmit.
CACR908E I/O ERROR HAS OCCURRED F/C=xx A/C=yy R/C=zzzz,zzzzzzzz

Explanation: An error has occurred while trying to access the procedure library after
initialization.
User Response: See the chapter "Catalog Management Return Codes" in the CA90s
Services VSE Message guide.
CACR909E CANNOT LOCATE DRIVER LIBRARY DESCRIPTION TABLE

Explanation: The Unicenter CA-Driver procedure library description table was not
found.
User Response: Make sure that you have re-IPLed after installing Unicenter CA-Driver
or that you had the Unicenter CA-Driver library in your LIBDEF search string before you
initialized the CA System Adapter (CASAUTIL).
CACR910E CACNINTO ERROR HAS OCCURRED R/C=xxxx

Explanation: The catalog management initialization program has detected an error from
which it cannot recover.
CACR911E CACRTBL0 ERROR HAS OCCURRED R/C=xxxx

Explanation: An error has occurred calling program CARCTBL0.

1.5 CACU Messages
CACU001 –CACU008
1.5 CACU Messages

CACU001 INVALID COMMAND
Explanation: The Utility program was passed an invalid command.
CACU002 INVALID COMMAND OBJECT

Explanation: The token immediately following the command verb was incorrect.
User Response: Check command syntax, correct command and reissue.
CACU003 INVALID KEYWORD

Explanation: Message produced by the Utility program.
User Response: Check command syntax, correct command and reissue.
CACU004 INVALID LIST SYNTAX

Explanation: A parameter value which should appear in a list format was specified
incorrectly.
CACU005 KEYWORD VALUE MISSING

Explanation: The value for a keyword parameter is not present in the command.
User Response: Specify a value for the parameter and reissue command.
CACU006 INVALID KEYWORD VALUE TYPE

Explanation: The value specified for a keyword parameter is inappropriate. For
example, job names cannot have a numeric first character.
CACU007 INVALID KEYWORD VALUE LENGTH

Explanation: The length of a value exceeded the expectation of the Utility program. For
example, NAME=WEEKLYPAY is invalid on a DEFINE JBR command because the
NAME keyword parameter accepts only eight characters in this context.
CACU008 INCOMPLETE COMMAND

Explanation: The end of the command stream was encountered before the command
string was completed. An expected continuation was not received.

1.5 CACU Messages
CACU009 –CACU017
CACU009 DUPLICATE KEYWORD

Explanation: The designated keyword appeared more than once in the command.
User Response: Remove the redundant parameter and reissue command.
CACU011 INVALID JNO

Explanation: An incorrect value for JNO was specified; that is, JNO=0.
User Response: Correct the JNO parameter and reissue the command.
CACU012 INVALID STATION ID

Explanation: An incorrect value for STATION was specified; that is, STATION=CPU.
User Response: Correct the STATION parameter and reissue command.
CACU013 RECORD IS LOCKED

Explanation: A particular record on a shared file is being updated by another user or
program.
User Response: Reissue command later.
CACU014 KEYWORD 'xxxxxxxx' MUST BE SPECIFIED

Explanation: A required keyword parameter is absent from the command.
User Response: Code the parameter and reissue command.
CACU015 DUPLICATE RECORD/DUPLICATE RECORD REPLACED (OVERLAY=YES)

Explanation: An attempt has been made to DEFINE (add) a record which already exists.
The duplicate record has been replaced as shown since the overlay option was set to YES
for restore.
User Response: Correct command and reissue. Informational only.
CACU016 PROTOTYPE RECORD NOT FOUND

Explanation: The command refers to a prototype job, schedule, or other record which
has not been defined previously.
User Response: Define the prototype record or change the PROTO specification.
CACU017 NOT FOUND

Explanation: Produced by a number of commands when the object of the command
cannot be located.
User Response: Correct the command and reissue.

1.5 CACU Messages
CACU018 –CACU023
CACU018 xxxxxxx yyyyyyyy HAS BEEN zzzzzzzz

Explanation: Information only; the command is complete.
CACU019 KEYWORD VALUE MUST BE A LIST

Explanation: The syntax for the designated keyword parameter demands that the values
be specified in a list format.
CACU020 INVALID SYSID, NOT IN CAIJGEN LIST

Explanation: The specified system identifier does not match any of the values listed in
the CAIJGEN options.
User Response: Correct the SYSID parameter in the DEFINE or ALTER command or
add the new SYSID to the CAIJGEN list.
CACU021 NO RECORD FOUND

Explanation: The record referred to in the command could not be located.
CACU022 INVALID TIMEZONE VALUE

Explanation: An invalid TIMEZONE value was given. TIMEZONE should be specified
in the format nnx. nn is the number of hours difference (01 to 23) and x is either plus
(+ ahead) or minus (- behind) the Data Center's local time.
User Response: Correct the TIMEZONE value and resubmit.
CACU023 SYNTAX xxxxxxxx UNSUPPORTED LIBRARY TYPE FOR SYNTAX CHECKING

Explanation: This message appears for one of these reasons:
1. The JCL library type specified in the SBR/JBR Definition has not been specified in the
Unicenter CA-Scheduler Generation Macro.
2. You asked Unicenter CA-Scheduler to check JCL syntax but the JCL library defined
for this job does not permit syntax checking (for example, RDRQ).
User Response: The action depends upon the reason. Follow the action with the same
number as the reason which applies to you.
1. Verify your generation options and specify the correct JCL library type.
2. None required.

1.5 CACU Messages
CACU024 –CACU031
CACU024 LIBRARY INTERFACE NOT FOUND FOR SYNTAX CHECKING

Explanation: A syntax check was requested for a job defined to a library for which there
is no library interface, because the CAIJGEN macro specified NO for that type of library
support.
User Response: Either change the CAIJGEN macro to specify YES for that type of
library support, or do not attempt to check syntax on jobs for that library type.
CACU025 ILLEGAL PREFIX USED IN A VOCABULARY KEYWORD

Explanation: An illegal date table prefix was used for a criteria accounting vocabulary
word.
User Response: See the Unicenter CA-Scheduler Reference Guide
for valid prefixes, and change the illegal prefix to a valid one.
CACU026 NO MORE DYNAMIC STORAGE AVAILABLE, PROGRAM TERMINATED

Explanation: Dynamic storage is exhausted.
User Response: Enlarge the area from which requests for dynamic storage are satisfied.
CACU027 ERROR OCCURRED, RET CODE= nnnnnnnn ERR CODE= nnnnnnnn PGM
TERMINATED
Explanation: An I/O error has occurred.
CACU028 TOO MANY OCCURRENCES

Explanation: Too many parameter values have been specified in a parameter list.
User Response: Correct the list and reissue the command.
CACU030 INVALID LIBRARY TYPE

Explanation: A command referred to a type of library which Unicenter CA-Scheduler
does not support.
User Response: Correct the library type and reissue command.
CACU031 INITIALIZE ff...ff DATABASE (YES/NO)?

Explanation: In response to a FORMAT command, the Utility program requests
confirmation from the console operator as to whether it should proceed.
User Response: Reply YES if the file (ff...ff) is to be formatted (that is, cleared and
initialized). Reply NO if the file is to be left as is (intact, with previous contents
unchanged).

1.5 CACU Messages
CACU032 –CACU041
CACU032 DATABASE xxxxxxxxxxxxxxxxxxxxxxxx HAS BEEN INITIALIZED

DATABASE xxxxxxxxxxxxxxxxxxxxxxxx WAS NOT INITIALIZED
DATABASE xxxxxxxxxxxxxxxxxxxxxxxx HAS BEEN RESTORED
Explanation: The designated file was initialized in response to a FORMAT command
and the operator's confirmation. The file is now ready for use in an empty state. If the
message reads '... WAS NOT INITIALIZED', the operator either responded NO to
message CACU031 or YES to message CACU061.
User Response: If the file is initialized, there is no action required. If the file is not
initialized, correct the job and resubmit.
CACU034 JOB DEPENDENT on ITSELF

Explanation: The criteria for this job contains itself as a predecessor.
User Response: Change the criteria so that the job is not dependent upon itself.
CACU035 ERLYTIME GREATER MUSTTIME

Explanation: The ERLYTIME (earliest time a job/schedule may begin) parameter value
is later than the MUSTTIME (time a job/schedule must begin) parameter value.
User Response: Correct one of these parameters and reissue command.
CACU036 MUSTTIME GREATER DEADLINE

Explanation: The MUSTTIME parameter value designates a time that is later than the
DEADLINE (time the job/schedule must end) parameter value.
User Response: Correct one of these parameters and reissue command.
CACU038 NOT DEFINED

Explanation: The ANALYZE command discovered references to records which have not
yet been defined.
User Response: DEFINE record to which this entry refers before attempting to initiate
the selection process.
CACU040 ssssssss jjjjjjjj nn st DEADLOCK WITH PREDECESSOR ssssssss jjjjjjjj nn st

Explanation: The ANALYZE command discovered that two jobs/schedules are
dependent upon each other, resulting in an unbreakable deadlock at execution time.
ssssssss is the schedule name. jjjjjjjj is the job name. nn is the Unicenter CA-Scheduler
job number. st is the station number.
User Response: Correct so that only one job is dependent on the other.
CACU041 NO JOBS DEFINED

Explanation: The ANALYZE command has located a schedule for which no jobs have
been defined.
User Response: Define jobs for this schedule.

1.5 CACU Messages
CACU042 –CACU052
CACU042 DUPLICATE KEYWORD LIST VALUES

Explanation: A particular value appears more than once in a list of values.
User Response: Correct the redundant specification and reissue command.
CACU043 INSUFFICIENT DISK SPACE ALLOCATED FOR XXX

Explanation: A FORMAT or RESTORE operation has failed due to inadequate disk
space.
User Response: Increase the allocation or reduce the value specified for the NJOB
parameter in the command or in the CAIJGEN macro, if not in the command.
CACU046 INVALID SUBSCRIPT LENGTH

Explanation: A subscripted Unicenter CA-Driver parameter has a bad subscript.
User Response: Correct subscript and reissue command.
CACU047 INVALID SUBSCRIPT VALUE

Explanation: A subscripted Unicenter CA-Driver parameter has a bad subscript.
User Response: Correct subscript and reissue command.
CACU048 INVALID PARAMETER NAME VALUE

Explanation: The keyword name of a Unicenter CA-Driver parameter is invalid.
User Response: Correct the keyword and reissue command.
CACU049 INVALID PARAMETER NAME LENGTH

Explanation: A Unicenter CA-Driver parameter keyword exceeds seven characters.
User Response: Correct the keyword and reissue command.
CACU050 PARAMETER VALUE LENGTH INVALID

Explanation: The value for a Unicenter CA-Driver parameter exceeds the maximum
length (62 characters).
User Response: Correct the value and reissue command.
CACU051 PARAMETER VALUE INVALID

Explanation: The value for a Unicenter CA-Driver parameter is invalid. For example, it
contains special characters but is not enclosed in quotation marks.
User Response: Correct the value and reissue command.
CACU052 COMMAND TOO LONG

Explanation: The length of the command exceeds the allowable limits.

1.5 CACU Messages
CACU053 –CACU060
CACU053 DUPLICATE DRIVER PARAMETER

Explanation: A keyword parameter appears more than once in the list of Unicenter
CA-Driver (or restart) parameters.
CACU054 NOT ALLOWED, CA-SCHEDULER MONITOR IS ACTIVE

Explanation: FORMAT and RESTORE commands are not permitted while Monitor is
up. They adversely effect the integrity of Monitor files.
User Response: Ensure Monitor is shut down before reissuing command.
CACU055 SHARE OPTION DOES NOT MATCH GENERATION SHARE OPTION

Explanation: The FORMAT or RESTORE command includes a SHARE option which
does not agree with the corresponding specification in the CAIJGEN installation macro.
User Response: Correct the command or update CAIJGEN.
CACU056 <record description> TAPE RECORDS READ | WRITTEN =

Explanation: In a file backup or restore, statistics are displayed.
CACU057 xxxxxxxx FUNCTION COMPLETED SUCCESSFULLY/xxxxxxxx OUTPUT FILE IS

EMPTY
Explanation: xxxxxxxx can be RESTORE, FORMAT, REORG, or BACKUP. Either the
displayed function ended successfully or the output file is empty.
CACU058 INVALID INPUT TAPE. xxxxxxx TERMINATED

Explanation: xxxxxxx can be RESTORE or CONVERT. The tape being used as input to
a RESTORE or CONVERT operation was not produced by a BACKUP operation.
User Response: Use the correct tape as input.
CACU059 TAPE ERROR HAS OCCURRED-xxxxxxx TERMINATED

Explanation: xxxxxxx can be RESTORE or CONVERT. An error has been detected while
reading an input tape during a RESTORE or CONVERT function. The file has become
unusable.
User Response: Use another BACKUP tape and try to RESTORE or CONVERT again.
CACU060 BAD RECORD TYPE on INPUT TAPE-RESTORE TERMINATED

Explanation: A bad record was encountered while reading an input tape during a
RESTORE function. The file has become unusable.
User Response: Use another BACKUP tape and try to RESTORE again.

1.5 CACU Messages
CACU061 –CACU070
CACU061 IS CA-SCHEDULER MONITOR ACTIVE on ANY OTHER CPU(S)?

Explanation: The Utility program asks the operator if Monitor is active on any CPUs
other than the host CPU. (The Utility automatically detects when Monitor is active on the
host CPU.) The operation about to be performed requires that Monitor not be up at any
of the CPUs in the network.
User Response: Reply accurately to the message (with YES or NO) to prevent damage
to the files.
CACU062 ABNORMAL TERMINATION FOR CAJUTIL0/CATA AT xxxxxx

Explanation: An abend occurred in the Utility program.
User Response: Check for obvious problems (such as an operator cancelation). Contact
CACU063 USERID IS LOGGED on

Explanation: This user ID is currently logged on and therefore cannot be deleted.
User Response: Reissue the DELETE USERID command after the user ID logs off.
CACU064E XXXXXX REPORT NOT ALLOWED IN THIS ENVIRONMENT.

Explanation: The error message occurs if:
■ you are not running VSE/SP and above,
■ there is no TWA, or
■ there is a Unicenter CA-Scheduler/Adapter problem.
User Response: Check the TWA and the VSE levels. If the problem persists, contact
Computer Associates Technical Support for assistance.
CACU065 USERID NOT FOUND IN CUI DATABASE

Explanation: AUDTSEC=YES was specified in CAIJGEN macro.
User Response: Add user ID to CAICUI database or specify AUTOSEC=NO to bypass
CAICUI security checking.
CACU066E ERROR ACCESSING AUTOMATIC REPLY DATABASE RC=X'00' VSAM RC=00

VSAM EC=00
Explanation: An error occurred while accessing the Automatic Reply Database.
User Response: Check the return code in the IBM VSE/VSAM Messages and Codes Guide.
If the problem persists, contact Computer Associates Technical Support for assistance.
CACU070 NAME TOO LONG

Explanation: While defining a criteria record, more than eight bytes were used for a job
or a schedule name.
User Response: Correct the job or schedule name.

1.5 CACU Messages
CACU071 –CACU078
CACU071 NO PAIRED PARENTHESES

Explanation: A list was defined with no paired parentheses.
CACU072 aaaaaaaa bbbbbbbb cccccccc INVALID SYNTAX

Explanation: A criteria record was probably misdefined and AND or OR has been
omitted.
CACU073 INVALID DATA SET NAME

Explanation: A data set name was defined by more than 44 characters, or was not
enclosed in quotes.
User Response: Correct and resubmit
CACU074 INVALID JOB/SCHEDULE NAME

Explanation: A job or schedule name was defined with special characters imbedded.
CACU075 CALENDAR=cccccccc AND <criteria> ARE MUTUALLY EXCLUSIVE

Explanation: A calendar name was specified along with calendar keywords on the
criteria record.
CACU076 TOO MANY PREFIXES

Explanation: More than one prefix was specified.
CACU077 GENERATION OPTION TABLE 'CAJAGENA' IS NOT FOUND

Explanation: The phase that is the result of assembling and linking the CAIJGEN
installation options macro could not be located.
User Response: Check with your systems group.
CACU078 'WRITPASS' INCORRECT

Explanation: An incorrect write password was entered while attempting to DELETE a
USERID record.
User Response: Correct the password.

1.5 CACU Messages
CACU081 –CACU089
CACU081 ALPHANUMERIC TRT TABLE 'CAJCTRT0' IS NOT FOUND

Explanation: The module that the Utility program uses as its numeric test table could
not be located.
User Response: Check with your Systems group.
CACU083 SELECTION KEYWORD VOCABULARY 'CAJCVCB0' IS NOT FOUND

Explanation: The module that the Utility program uses as its selection keyword
vocabulary list could not be located.
CACU084 INVALID RECORD ID. ID EXPECTED=xxx ID ENCOUNTERED=yyy

Explanation: A type of record expected to be at this location in the file was not found
and the index has been corrupted.
User Response: Take appropriate action. The file may be damaged.
CACU085 SYSTEM ADAPTER ERROR OCCURRED FUNCTION='ffffffff' F/C=ff R/C=rrrr

Explanation: A call to System Adapter function returned a non-zero return code.
User Response: Check the System Adapter return code against its associated function
code. (See the chapter "Return Codes" in the CA90s Services Message Guide.) If you are
unable to resolve the problem with the return code information, contact Computer
CACU086 NAME NOT FOUND IN SCHDPARM

Explanation: There is a possible discrepancy in the version of CAIJGEN macro.
CACU087 TOO MANY NO OF DEVICES MAX 255

Explanation: More than 255 devices were specified in a command.
CACU088 INVALID TYPE | SYNTAX

Explanation: A global variable was tested against an inconsistent data type.
CACU089 CISIZE MUST BE A MULTIPLE OF 512

Explanation: The CISIZE specified in the xxxCISZ operand of the CAIJGEN installation
macro is not a multiple of 512. xxx is either MST, STG, TRK, or DCM for MASTER,
STAGING, TRACKING, or DOCUMENT, respectively.
User Response: Correct the xxxCISZ and recreate the CAIJGEN macro.

1.5 CACU Messages
CACU090 –CACU099W
CACU090 COMMAND DENIED BY SECURITY EXIT

Explanation: The specified command is denied by the user security exit. This message
should be accompanied by messages from the security exit that further explain the error.
User Response: Either do not use the command, or check with your security
administrator to obtain authorization to use the command.
CACU091 .... NOT TO BE SELECTED on GIVEN DATE

Explanation: A successor chain list was requested for a job or a schedule with the
DATE=date option, but the job or the schedule was not to be selected on the given date.
User Response: Make sure that the correct date was entered.
CACU094 .... Scheduler MONITOR NOT ACTIVE

Explanation: A current successor chain list was requested for for a job or a schedule, but
the Unicenter CA-Scheduler monitor was not active.
User Response: Reissue the command after the Unicenter CA-Scheduler Monitor has
been activated.
CACU095W DYNAMIC ALLOCATION FAILED FOR xxxxxxx, RC=xxx

Explanation: The dynamic allocation of the work file has failed for the reason indicated
in the RC field. The RC field is documented under Error Reason Codes in the SPL: Job
Management Guide..
User Response: Take the appropriate action based on the RC field. Execution continues,
using the real master file.
CACU096W DTFNAME xxxxxxxx COULD NOT BE OPENED, COPY FAILED

Explanation: The dtfname indicated in xxxxxxxx could not be opened for some reason.
Execution continues, using the real master file.
User Response: Ensure that the file is allocated in the step.
CACU097W ENCOUNTERED INVALID KEYWORD ARGUMENT, COPY FAILED

Explanation: The SIMWORK keyword value is not valid.
User Response: Specify a generic/esoteric unit name or NO. Execution continues, using
the real master file.
CACU099W COULD NOT OBTAIN CAIJMST CCR RECORD, COPY FAILED

Explanation: The master file control record could not be located.
User Response: Ensure that System Adapter is up and pointing at the correctly
formatted master file. Execution continues, using the real master file.

1.5 CACU Messages
CACU100W –CACU106
CACU100W COULD NOT CALC SPACE REQUIREMENTS, COPY FAILED

Explanation: The master file control record may have been corrupted, or else it has been
stored on an unsupported device type. Execution continues, using the real master file.
User Response: Document the device type being used for the master database and
contact Computer Associates Technical Support.
CACU101W STORAGE ALLOCATION FAILURE, COPY FAILED

Explanation: The requested buffer storage was not available.
User Response: Increase the partition size or decrease the SIZE parameter on the EXEC
statement and try again. This buffer size is calculated based on the track capacity of the
device where the master file is stored. Execution continues, using the real master file.
CACU102W CAIJMST DOES NOT MATCH CATALOG, COPY FAILED

Explanation: The master file allocated in this step is not the same one that the System
Adapter is pointing to. Execution continues, using the real master file.
User Response: Make sure the data set name for the master file ddname in this step
matches the data set name of the master file specified in the Unicenter CA-Scheduler
startup procedure.
CACU103W COPY RETRY INTERVAL EXHAUSTED, COPY FAILED

Explanation: The master file is being updated and is growing in size at such a rate that
the space calculation for the work file cannot be resolved. Execution continues, using the
real master file.
User Response: Try again when less database maintenance is going on.
CACU104W DEQ FAILURE on CAIJMST, COPY FAILED

Explanation: A dequeue of the master file did not successfully complete.
User Response: If you are waiting to enqueue a file and it is owned by this job, run a
FORCEDEQ on the master file.
CACU105 CA-SCHEDULER PRODUCT TABLE NOT FOUND

Explanation: Unicenter CA-Scheduler not initialized by System Adapter.
User Response: Add Unicenter CA-Scheduler to CASAUTIL initialization list.
CACU106 PRODUCT NOT INSTALLED OR NOT SUPPORTED IN THIS ENVIRONMENT

exploitation.
User Response: The ESA feature is required for VSE/ESA exploitation.

1.5 CACU Messages
CACU600 –CACU606
CACU600 INSUFFICIENT STORAGE FOR SIMULATION/FORECAST

Explanation: Not enough storage to execute the SIMULATE or FORECAST command.
User Response: Increase size of GETVIS area.
CACU601 ERROR OCCURRED on SIMULATION/FORECAST INPUT STATEMENT.

SIMULATION/FORECAST CANCELLED
Explanation: An error occurred on the SIMULATE or FORECAST input statement.
User Response: See the previous error message to find out what the error was. Correct
and resubmit.
CACU602 DATA BASE ACCESS ERROR OCCURRED F/C=ff A/C=aa

R/C=rrrr,rrrrrrrr,rrrrrrrr
Explanation: An I/O error occurred while program was trying to access the Unicenter
CA-Scheduler database. This can be due to a concurrent update of a specific record or
record type.
User Response: If the first part of R/C=0008 and the next four characters are any one of
the following: 0854, 085C, 0874, 08A4, or 08B4, then rerun the job. In most cases it will
run to normal completion. If not, contact Computer Associates Technical Support.
CACU603 ERROR IN OVERRIDE COMMAND R/C=rr

Explanation: An error occurred on the simulation override command. If R/C=01, you
were trying to override one device type with a different device type. If R/C=02, there
was no station defined for the device you were trying to override.
CACU604 INVALID OVERRIDE COMMAND ATTEMPTED R/C=rr STN=nn SYSID=ssss

TYPE=device OST=dd/hh:mm OET=dd/hh:mm
Explanation: Simulation could not allow the override that was attempted.
CACU605 UNRECOVERABLE ERROR HAS OCCURRED-SAVE DUMP

Explanation: Simulation has encountered an error from which it cannot recover.
CACU606 PST OR PET MAY NOT BE SPECIFIED WITH OST OR OET SPECIFICATION
IGNORED
Explanation: PST or PET may cannot be specified with OST or OET specification
ignored

1.5 CACU Messages
CACU607 –CACU614
CACU607 CALENDAR 'cccccccc,mm/yyyy' NOT FOUND FOR SCHEDULE=ssssssss

CALENDAR 'cccccccc,mm/yyyy' NOT FOUND FOR SCHEDULE=ssssssss
JOB=jjjjjjjj-nn AT STATION=nn
Explanation: During simulation job selection, a calendar for a month and year was not
defined in the database.
User Response: Define calendar.
CACU608 JOB SELECTION ERROR OCCURRED F/C=ff R/C=rrrrrrrr

Explanation: A simulation job selection error occurred.
CACU609 SYSTEM ADAPTER ERROR OCCURRED FUNCTION='ffffffff' F/C=ff R/C=rrrrrrrr

Explanation: A call to a system adapter function returned a non-zero return code.
CACU610 DATE TABLE 'datetable,yyyy' NOT FOUND FOR SCHEDULE=ssssssss

DATE TABLE 'datetable,yyyy' NOT FOUND FOR SCHEDULE=ssssssss
JOB=jjjjjjjj-nn AT STATION=nn
Explanation: During simulation job selection, a date table for year was not defined in
the database.
User Response: Define calendar.
CACU611 NO RESOURCES DEFINED FOR THIS SIMULATION. R/C=r

Explanation: R/C=1 indicates that a station was defined. R/C=2 indicates that there
were no units defined.
User Response: Define your resources.
CACU612 SORT ERROR OCCURRED F/C=ff R/C=rr

Explanation: A sort I/O error occurred.
CACU613 INVALID REPORT NAME 'report' IN EXCLUDE LIST

Explanation: The displayed report name is invalid.
CACU614 INVALID TRACE OPTION 'traceopt'

Explanation: The displayed trace option is invalid.

1.5 CACU Messages
CACU615 –CACU621
CACU615 SCHEDULE COULD NOT BE FOUND FOR JOB SPECIFIED IN PREVIOUS

COMMAND
Explanation: No schedule was found for the job named in the command.
CACU616 PST OR PET MAY NOT BE SPECIFIED WITH 'option' SPECIFIED AS 'NULL'
Explanation: You cannot specify PST or PET with a NULL option.
CACU617 xxxxxxxx COULD NOT BE LOADED RC=rr

Explanation: TAPEPULL LIST initialization error.
User Response: Look up the return code in the DOS/VSE Advanced Function Macro
Reference Guide.. Find the error codes listed for the CDLOAD macro and take the
appropriate action.
CACU618 NO SCHEDULES/JOBS SELECTED FOR ddmmyy

Explanation: No jobs were scheduled for this day; therefore no simulation or forecast
reports could be generated.
User Response: Change the date and resubmit.
CACU619 'MONTHOF' PARAMETER IS INVALID

Explanation: MONTHOF keyword must be coded as mmyy.
CACU620 JOB jobname jno IN SCHEDULE schdname AT STATION st STARTED AT

dd/hh:mm:ss INSTEAD OF dd/hh:mm:ss
Explanation: This EXPERROR message generated for revised simulation indicates that
the named job was not able to be started by simulation at the time specified in the
tracking file. It started at the later indicated time.
CACU621 JOB jobname jno IN SCHEDULE schdname AT STATION st DID NOT START
AT dd/hh:mm:ss
Explanation: This EXPERROR message generated for revised simulation indicates the
named job was supposed to start at the specified date and time, but did not start by the
current time of day in simulation.

1.5 CACU Messages
CACU622 –CACU629
CACU622 TRACKING FILE ACCESS ERROR OCCURRED F/C=ff A/C=aa RC=rrrr,

rrrrrrrr,rrrrrrrr
Explanation: An error has occurred while accessing the tracking file.
CACU623 DOCUMENT FILE ACCESS ERROR OCCURRED F/C=ff A/C=AA R/C=rrrr,

rrrrrrrr,rrrrrrrr
Explanation: An error has occurred while accessing the documentation file.
CACU624 CAJUSIO0 CALL ERROR RC=rr

Explanation: A TAPEPULL LIST error occurred while accessing CAIJNI file.
CACU625 jjjjjjjj nn ssssssss ERROR PUNCHING MEMBER RC=rrrr

Explanation: A TAPEPULL LIST error occurred punching a member.
User Response: Check submission fail codes described in message CACM054I or
STATUS command in the Unicenter CA-Scheduler Reference Guide Part 1..
CACU626 llllllll UNSUPPORTED LIBRARY TYPE FOR TAPEPULL LIST

Explanation: The library type described in the message is not supported for TAPEPULL
LIST.
CACU627 TAPE MANAGEMENT SYSTEM NOT FOUND/ACTIVE

Explanation: BrightStore CA-Dynam/TLMS is not installed/active.
CACU628 rrr jjjjjjjj nn ssssssss NOT FOUND

Explanation: JBR/JTR or SBR/STR not found in Master or Tracking files.
User Response: Check for correct Job and Schedule names in TAPEPULL command.
CACU629 ERROR LOCATING CAJCPQMA

Explanation: System Adapter was unable to locate phase CAJCPQMA.

1.5 CACU Messages
CACU630 –CACU666E
CACU630 CA-SCHEDULER MONITOR NOT ACTIVE

Explanation: Unicenter CA-Scheduler Monitor must be active if NJE=YES is defined in
the CAIJGEN macro.
User Response: Initialize the Unicenter CA-Scheduler Monitor or change NJE=NO in
CAIJGEN macro.
CACU631 ERROR PUNCHING TAPEPULL LIST INITIAL CARDS RC=rrrr

ERROR PUNCHING TAPEPULL LIST END OF DATA CARDS RC=rrrr
Explanation: A TAPEPULL LIST error occurred punching initial/eod statements.
User Response: Check submission fail codes described in message CACM054I or
STATUS command in Unicenter CA-Scheduler Reference Guide Part 1..
CACU666E MAINTENANCE PROGRAM LOAD FAILED - xxxxxxxx

Explanation: An attempt to automatically load program xxxxxxxx has failed. Either the
program could not be located, or there was insufficient storage to load the program.
User Response: Check to make sure program xxxxxxxx is in the appropriate product
library, and that the library is in the proper search chain for the partition in question.
Also check to ensure that there is adequate storage in the partition (including partition
GETVIS).

Chapter 2. CICS Abend Codes
The following CICS abend codes may be received from the Computer
Associates online interface:
Code Reason Action

CATR The online interface was Correct and retry.
initiated without a valid
TRANSID code. Valid codes are
currently DYNT, SCHD and
SNTL.
CAPR The online interface was Consult the appropriate
initiated but not all required online interface
programs were in the CICS PPT. documentation, correct
the PPT and retry.
CAST There is insufficient CICS Increase the size of the
subpool storage to satisfy the CICS subpool and retry.
online interface's storage request.
CALG An internal logic error has Contact Computer
occurred. Associates Technical
Support.
CAXT An error was encountered Contact Computer
during a CICS SETEXIT request. Associates Technical
Support.
CAAB The Catalog Access Subtask has Retrive the dump
abended. produced on SYSLST and
contact Computer
Associates Technical
Support.
SN01 The length operand of the CICS See the eTrust CA-Top
exec link program (CASE071) is Secret Systems Programmer
not connected. Guide for more
information.
Chapter 2. CICS Abend Codes 2-1

CA Scheduler Job Management For VSE

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CA Scheduler Job Management For VSE

Uploaded by

Copyright:

Available Formats

Unicenter CA-Scheduler /

Job Management for VSE

 2005 Computer Associates International, Inc.

Chapter 1. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Chapter 2. CICS Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

This guide lists all Unicenter CA-Scheduler and Unicenter CA-Driver

Chapter 1. Messages 1-1

1.1 Message IDs

The Code Means

1-2 Unicenter CA-Scheduler/CA-Driver Message Guide

1.2 CACM Messages

CACM002 INVALID COMMAND OBJECT

CACM003 TALTER JOB xxxxxxx INVALID KEYWORD

CACM004 NOT ENOUGH GETVIS IN POWER PARTITION

CACM005 DUPLICATE NAME IN SUPVR XECBTAB

CACM006 SUPVR XECBTAB IS EXHAUSTED

CACM007 INVALID KEYWORD VALUE LENGTH

CACM008 INCOMPLETE COMMAND

Chapter 1. Messages 1-3

CACM009 DUPLICATE KEYWORD

CACM010 INVALID KEYWORD

CACM011 INVALID LIST SYNTAX

CACM012 KEYWORD VALUE MISSING

CACM013 INVALID KEYWORD VALUE TYPE

CACM014 KEYWORD 'xxxxxxxx' MUST BE SPECIFIED

CACM016 xxxxxxxx NOT FOUND

CACM019 KEYWORD VALUE MUST BE A LIST

1-4 Unicenter CA-Scheduler/CA-Driver Message Guide

CACM022 xxxxxxxx STILL ACTIVE

CACM023 NO JOBS DEFINED

CACM024 HAS TO WAIT FOR STORAGE

CACM025 xxxxxxxx NOT ACTIVE

CACM026 SCHEDULER MONITOR IS IN THE SHUTDOWN PERIOD

CACM027 AUTOSCAN CANNOT BE PERFORMED IN THE SHUTDOWN PERIOD

CACM028 TOO MANY OCCURRENCES

Chapter 1. Messages 1-5

CACM029 CANNOT RERUN JOB

CACM030 SYSTEM IS NOT GENNED FOR MULTIPLE CPU

CACM031 COMMAND SENT TO SYSID: xxxx

CACM032 CANNOT COMP. A CPU JOB

CACM033 jjjjjjjj IS NOT A CPU JOB

CACM034 xxxxxxxx uuuuuuuu IS NOT AUTHORIZED

CACM035 IS NOT WAITING FOR COMP. CMD

1-6 Unicenter CA-Scheduler/CA-Driver Message Guide

CACM037 AUTOSCAN WAS PERFORMED AT hh:mm FOR SYSID xxxx

CACM039 SUPPORT FOR JCL LIBRARY xxxxxxxx IS NOT GENERATED

CACM040 JCL IS NOT IN READER QUEUE

CACM041 JOB SUBMISSION FAILURE FROM LIBRARY xxxxxxxx RC=cccc

CACM042 DUPLICATE KEYWORD LIST VALUES

CACM043 WAITING FOR VOLUMES vvvvvv,vvvvvv

Chapter 1. Messages 1-7

CACM044 SCHEDULE ssssssss DID NOT START

CACM046 CMS READ ERROR. SENSE INFO = xxxxxxxxxxxxxxxx

1-8 Unicenter CA-Scheduler/CA-Driver Message Guide

CACM050 AUTOSCAN IN PROGRESS FOR SYSID xxxx

CACM051 AUTOSCAN COMPLETED

CACM052 COMMAND TOO LONG

CACM053 AUTO RECOVERY COMPLETED

Chapter 1. Messages 1-9

CACM054 (variable text)

SCHEDULE The schedules you selected, in alphabetical order or in order of priority.

JCNT The number of jobs in the schedule.

1-10 Unicenter CA-Scheduler/CA-Driver Message Guide

CACM200 * CA-SCHEDULER MONITOR IS ACTIVE ALREADY *