4. Operation › 4.3 Operations Reference › 4.3.11 Abend Codes and Corrective Action
4.3.11 Abend Codes and Corrective Action
This section documents abend codes you may encounter with
CA MICS processing. Refer to other sections in this guide
for more information on restarting CA MICS operational jobs.
SUMMARY
User
Abend Code Termination Condition/Reason
---------- ------------------------------------------------
100 Database marked non-updatable.
101 Database marked non-updatable; aging in
progress when failure occurred.
110 Internal step restart failed; required files
are missing or corrupted.
120 Internal step restart failed; saved work files
missing or corrupted.
130 Stand-alone AUDIT, HISTW, and/or HISTM archive
tape processing job not yet executed.
300 Input data file was empty.
310 The original system identifier in the input data
was not defined in the SYSID parameter when the
last run of ALLPGEN or BASPGEN occurred.
320 Zone was not defined in ZONE parameter when the
last ALLPGEN or BASPGEN job was run.
400 Invalid checkpoint record encountered.
410 Limit of ORGSYSID/COMPONENT entries is exceeded
in the Checkpoint File.
420 Invalid FORCE or SELECT range was specified.
425 Invalid SYSPARM value was specified.
430 INPUTRDR end-of-file routine was not entered
after the last input record.
440 SAS version is not compatible with CA MICS
version.
User
Abend Code Termination Condition/Reason
---------- ------------------------------------------------
450 PREFIX in the Checkpoint File does not match the
PREFIX used in the update procedure.
460 Checkpoint File initialization failed or the
checkpoint routine initial update processing
failed.
470 Exit did not return control properly.
500 Execution date less than previous date.
510 YEAR is not in the range of years defined to
CA MICS.
600 CA MICS JCL delimiter missing.
800-899 Codes reserved for user.
998 Runtime error with explanatory text.
999 RSTATUS found non-updatable database
or
SAS System abend.
1310 Insufficient memory.
System
Abend Code Termination Condition/Reason
---------- ------------------------------------------------
S337 Less than expected number of records in
Checkpoint File.
SA13-10 Tape files cannot be written because prior file
does not exist.
S0C1 Batch ISPF dialog processing failure.
S122 CA Common Services for z/OS and OS/390 not
installed or operational.
ABEND CODES AND CORRECTIVE ACTION
User
Abend Code Termination Condition and Corrective Action
---------- ------------------------------------------------
100 Database marked non-updatable.
Probable causes:
First, if a job is executed and its previous
execution did not complete successfully, the job
will not be allowed to continue.
Second, if any other standard job's last run was
unsuccessful, this job will not be allowed to
continue.
Third, if a RESTART specification was not
removed after a previous run, the job will not
be allowed to start at the specified restart
step.
Corrective Action:
Identify the job that unsuccessfully terminated,
correct or eliminate the problem causing the
abend, and restart the job, ensuring its
successful completion.
101 Database marked non-updatable; aging in
progress when failure occurred.
Contact CA Technical Support for assistance.
Have available the SAS log for the abended run
and PROC DATASETS reports for the DETAIL, DAYS,
WEEKS, MONTHS, and YEARS files.
110 Internal step restart failed; required files
are missing or corrupted.
One or more SAS files required for internal step
restart are missing or corrupted.
Corrective Action:
Specify SYSPARM=NORESTART on the JCL EXEC for
the failing step and restart the job.
120 Internal step restart failed; saved work files
missing or corrupted.
One or more intermediate work files on the
cccXWORK and WORKnn data sets are missing or
corrupted. These files are required to restart
this processing phase.
Corrective Action:
Specify SYSPARM=NORESTART on the JCL EXEC for
the failing step and restart the job.
130 Stand-alone AUDIT, HISTW, and/or HISTM archive
tape processing job not yet executed.
You enabled stand-alone archive audit and/or
history processing, but the archive processing
from the previous WEEKLY or MONTHLY job has not
yet executed.
Corrective Action:
Review the MICSLOG for the abending step to
determine which archive tape processing job
(AUDIT, HISTW, and/or HISTM) must be executed
before you can resume today's scheduled
processing. Determine why that job has not yet
executed and complete that processing before
restarting the abending operational job step.
300 Input data file was empty.
Probable causes:
A DAILY step's input file was read and the input
file was empty or all input records were
rejected for some reason. The MICSLOG output
provides additional information as to the reason
why the data was rejected.
The duplicate data checks used in input
processing excluded all but 10 of the records
due to Checkpoint File date range checking.
A _USRSEL (User Select) Exit caused all input
records to be rejected.
Corrective Action:
Determine whether or not there should be input
data. It is possible that no data is available,
for example in the case of a CICS update step
run for a day when CICS was not up. If a U300
abend occurs and no data is expected, specify
SYSPARM=NODATA on the JCL EXEC statement for the
failing step and restart the job.
If data is expected, determine what happened to
the input data. When it is located, restart the
DAILY job.
310 The original system identifier in the input data
was not defined in the SYSID parameter when the
last run of ALLPGEN or BASPGEN occurred.
Corrective Action:
Add the undefined system identifier to the SYSID
and any other necessary parameter members, run
BASPGEN, and restart the abended job.
or
Specify the UNDEFINEDSYSID EXCLUDE computing
system control parameter at either the complex
level or unit level, run the corresponding
parameter generation job, and restart the
abended job.
or
Temporarily specify a
EXCLUDEORGSYSIDS UNDEFINEDSYSID statement in the
prefix.MICS.PARMS(EXECDEF) member and restart
the abended job.
320 Zone was not defined in ZONE parameter when the
last CPLXGEN, ALLPGEN, or BASPGEN job was run.
Corrective Action:
If this unit is using the complex-level zone
definition, add the undefined zone to the
complex-level CPLXZONE PARMS member and run
CPLXGEN. Otherwise, add the undefined zone to
the unit ZONE PARMS member and run BASPGEN.
Then restart the abended job.
400 Invalid checkpoint record encountered.
The Checkpoint File's first record contains an
invalid step number or run completion date for
one of the jobs tracked by this record, or an
embedded blank line was found in the
ORGSYSID/COMPONENT section of the database
update time range records of the checkpoint data
set.
Corrective Action:
Correct the checkpoint file and restart the
abended job.
410 Limit of ORGSYSID/COMPONENT entries is exceeded
in the Checkpoint File.
Either there are the maximum number of database
update time range records in the Checkpoint File
data set or the checkpoint data set was
inadvertently line numbered. Checkpoint size is
specified by the CKPTCNT parameter in
prefix.MICS.PARMS(SITE).
Corrective Action:
If the checkpoint data set was line numbered and
the sequence numbers are in columns 193-200 of
each record, remove the sequence numbers and
restart the job.
If any other reason caused this abend, contact
CA Technical Support.
420 Invalid Force or Select range was specified.
Force or Select time ranges in other than SAS
DATETIME 19.2 format.
Corrective Action:
Refer to the MICSLOG for more details. Correct
the time range and restart the job.
425 Invalid SYSPARM value was specified.
A value specified for the SYSPARM symbolic
parameter on the JCL EXEC statement is not
recognized by CA MICS or is invalid for the job
step being executed.
Corrective Action:
Refer to the MICSLOG for more details. Correct
the SYSPARM value and restart the job. Note
that a comma is not a valid delimiter within the
SYSPARM value.
430 INPUTRDR end-of-file routine was not entered
after the last input record.
This condition can be symptomatic of a bug in an
exit routine or CA MICS parameter library
member.
Corrective Action:
Contact CA Technical Support.
440 SAS version is not compatible with CA MICS
version.
Have the SAS version, printed at the top of the
SAS log (ddname FT11F001) at hand and contact CA
Technical Support.
450 PREFIX in the Checkpoint File does not match the
PREFIX used in the update procedure.
This abend is usually caused by changing CA MICS
library data set names.
Corrective Action:
Contact CA Technical Support.
460 Checkpoint File initialization failed or the
checkpoint routine initial update processing
failed.
Checkpoint File initialization fails if the
Checkpoint File has already been used (data
range records exist in the Checkpoint File).
Job CKPTINIT should not be forced to run.
Contact CA Technical Support.
Checkpoint routine initial update processing
fails if two or more database update time range
records have identical ORGSYSID/COMPONENT
identifiers. This can happen if you edit the
Checkpoint File incorrectly. Contact CA MICS
Product Support.
470 Exit did not return control properly
The Exit Check Routine issues this abend when
the code of the user exit named in the abend
message prevents program control from returning
to the statement that follows the invocation of
the exit.
Corrective Action:
Review the code in the user exit. See the Notes
on Coding CA MICS Parameters section in this
guide.
500 Execution date less than previous date
This abend is issued by the SCHEDULE job. If
the SCHEDULE job detects that today's date of
execution is less than any of the step
completion dates maintained in the Checkpoint
File, this abend is generated and prohibits the
execution of SCHEDULE. Either today's date is
wrong in MVS or it was incorrectly carried by
MVS on a previous day.
Corrective Action:
If today's date is incorrect, reset the MVS
date. If previous dates are incorrect, change
them in the Checkpoint File and restart the
SCHEDULE job.
510 YEAR is not in the range of years defined to
CA MICS.
This abend only occurs when the 13MONTHYEAR
option is specified in prefix.MICS.PARMS(SITE)
or sharedprefix.MICS.PARMS(CPLXDEF). It occurs
if a year is encountered which was not defined
to CA MICS for the YEAR derivation routine.
Corrective Action:
Update the 13MONTHYEAR statement in
sharedprefix.MICS.PARMS(CPLXDEF), run the
CPLXGEN job, and then run the BASPGEN job.
or
Update the 13MONTHYEAR statement in
prefix.MICS.PARMS(SITE) and run the BASPGEN job.
or
Update the sharedprefix.MICS.SOURCE members
$DWMYnn and #DWMYnn for special fiscal
calendars. See the prefix.MICS.PARMS(SITE)
13MONTHYEAR statement for member names.
600 CA MICS JCL delimiter missing
The standard CA MICS JCL procedures (DAILY,
WEEKLY, MONTHLY, YEARLY, and BACKUP) have a
special delimiter following their job cards,
which is used by Operational Status and Tracking
and the SCHEDULE batch job. The delimiter is:
//* START OF JCL
Corrective Action:
Check each of the five procedures in the
prefix.MICS.CNTL library to ensure that the
//* START OF JCL statement follows the job card
and related JES parameter (e.g., JOBPARM), then
rerun the SCHEDULE job.
800-899 Codes reserved for user
998 Runtime error with explanatory text
A CA MICS runtime routine found an error
condition which causes processing to stop.
Further processing might damage the database if
this abend occurs during an operational job. A
description of the condition is printed in
either the CA MICS log or SAS log (check the
CA MICS log first).
Corrective Action:
Correct the problem according to the explanatory
text and restart the job.
999 RSTATUS found non-updatable database
or
SAS System abend.
The Run Status Report (RSTATUS) has found the
database in non-updatable condition. See the
printed Run Status Report for details or use the
online Operational Status and Tracking facility
to research the problem.
or
SAS abended this job due to a processing problem
that is identified in the SAS log.
Corrective Action:
For a non-updatable database, correct the
problem described in the Run Status Report and
restart the job.
For a SAS system abend, correct the problem
reported in the SAS log and restart the job.
1310 Insufficient memory.
The job that is being executed requires more
memory than is available.
Corrective Action:
Increase the REGION size on the job step. If
the REGION is at its maximum value, break the
job into multiple steps and include a REGION
parameter on each step.
System
Abend Code Termination Condition and Corrective Action
---------- ------------------------------------------------
S337 Less than expected number of records in
Checkpoint File
The Checkpoint File has been edited and one or
more lines deleted. The Checkpoint File must
have exactly 1 more record than the value
specified for the CKPTCNT parameter in
prefix.MICS.PARMS(SITE). For example, the
default CKPTCNT specification is 100, meaning
that the checkpoint data set should contain
exactly 101 records.
Corrective Action:
Contact CA Technical Support.
SA13-10 Tape files cannot be written because prior file
does not exist
Corrective Action:
Determine why the previous file was not written,
then call CA Technical Support for help in
correcting the problem.
S0C1 Batch ISPF dialog processing failure.
MICF inquiry production reporting and other
batch ISPF dialog jobs must generate a S0C1
abend to cause the batch job step to end with a
non-zero return code. The S0C1 abend and the
associated batch job step RC=12 indicate that a
batch ISPF dialog process has failed.
Corrective Action:
Review the CA MICS log and ISPLOG outputs to
determine the reason for batch ISPF dialog
termination. Be sure to have the MICSLOG,
ISPLOG, and other batch job outputs available if
you need to call CA Technical Support for help
in correcting the problem.
S122 CA Common Services for z/OS not installed or
operational.
Either the CA Common Services for z/OS LMP
service is not installed and operational, or the
console operator cancelled the job requesting a
dump.
CA LMP is one of the CA Common Services for
z/OS. CA LMP provides a standardized and
automated approach to the tracking of licensed
software. It must be installed and operational
before you can install or run CA MICS.
For more information on how LMP works with CA
MICS, see Section 3.2.2 in the PIOM. For a full
description of the procedure for defining the CA
LMP execution key to the CAIRIM parameters, see
the section on CA LMP in the CA Common Services
for z/OS and OS/390 Administrator Guide.
