MESSAGES › Appendix A: Messages
Appendix A: Messages
This appendix lists the messages generated by the CA MICS
Analyzer Option for IMS. The messages are printed in both
the MICSLOG and SAS log data sets. When reviewing the output
of a job, first look at the MICSLOG data set because it will
contain fewer lines of information, making it easier to
determine whether a job or job step completed as expected.
If the MICSLOG message does not provide enough information,
consult this appendix for more information about the message.
If you still need more information, consult the SAS log to
help debug the problem.
The format of a MICSLOG message is:
hh:mm:ss.hs cccnnnnns ttttttttttttttttttttttttttttttt
where:
hh:mm:ss.hs The time the message was issued.
cccnnnnns The message identifier. The message
identifier consists of three parts:
ccc Component identifier
nnnnn Message number
s Severity identifier:
I = Information
W = Warning
E = Error
ttt...ttt The message text. If the text spans
more than one line, the message
identifier is repeated.
In addition to the message identifier and text, this appendix
presents the reason for the message, suggests actions to take
to resolve the problem, and refers you to additional sources
of information to help you understand the problem and its
resolution.
The CA MICS Analyzer Option for IMS gives other messages not
printed on MICSLOG. The SAS log, or the MAPRINT DD in LDE
output, contains output printed by one (or more) of the Log
Data Reduction (LDR) programs (listed in section 10.3 of the
CA MICS Analyzer Option for IMS Guide). This output is
particularly interesting for analyzing the actions performed
when processing the IMS log. The report indicates which
monitor source was selected (BMC MAINVIEW for IMS Online or
not) and the types of IMS log records input, records dropped,
and transaction records created or passed.
Under catastrophic circumstances, LDE or a Log Data
Reduction program may abend with a user 001 or 200 abend
code. These abends are always accompanied by information on
the SAS log or MAPRINT DD that indicates the cause of the
problem and corrective action.
*********
* U0001 *
*********
A U0001 abend can be issued by MALDEXIT or IMSLOGV6.
The MAPRINT data set provides corrective actions, like the
following:
o IMS VERSION ON THE PARM IS WRONG
The LDEPARM data set is coded incorrectly. Possible
errors resulting in this message are:
- The version is not 61, 71, 81, 91, 10, or 11.
- The positional parameters are in the wrong columns.
o NOT ENOUGH MEMORY
The REGION size specified on the JOB or EXEC card is too
small. Increase the REGION size and rerun the job.
o SPANNED RECORDS ON LOG INPUT
IMS does not write the log file using RECFM=VBS (Variable
Blocked Spanned). To ensure that LDE and IMS Analyzer
users input an IMS log data set (as opposed to an SMF
data set) the code checks for spanned records. If this
abend occurs, correct the input data set and rerun the
job.
*********
* U0200 *
*********
A U0200 abend can be issued by MALDEXIT or IMSLOGV6.
When MALDEXIT issues the message, either the release or
option specified in a LDEPARM member is incorrect.
When IMSLOGV6 issues the message, either a short or long
message table overflowed or the Fastpath EMHB table
overflowed.
The MAPRINT data set provides corrective actions like the
following:
xxxxxxxx TABLE OVERFLOW,
CORRECT PARMS(IMSOPS) TABLES STMT,
RERUN IMSPGEN BEFORE DAILY RESTART
The 'xxxxxxxx' in this message identifies the LDE TABLE
that was specified as being too small. See the IMSOPS
documentation in Chapter 7 of the Analyzer Option for IMS
Guide for more information about the IMSOPS TABLES
statement. If you are running at a non-CA MICS site,
contact Technical Support at http://ca.com/support.
In addition, the SAS program can produce extended record
count statistics, useful in debugging some data source
problems. The report is controlled by a SAS macro variable
called DEBUG. The DEBUG variable may be set by adding the
following line to prefix.MICS.PARMS(EXECDEF):
USERDEF IMSDEBUG YES
+-----------------+
| I M S 0 0 1 0 0 |
+-----------------+
TEXT: ---------------------------------------------
Record Type Summary for DDNAME: IMSE
Records Records
Log Record Added Deleted
---------------------------------------------
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
headers for the data that follows.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 0 1 |
+-----------------+
TEXT: 01-Input Message........: %LOGC01 %LOGD01
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of input messages processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 0 2 |
+-----------------+
TEXT: 02-System Reconfig......: %LOGC02 %LOGD02
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of system-reconfiguration actions
processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 0 3 |
+-----------------+
TEXT: 03-Output Message.......: %LOGC03 %LOGD03
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of output messages processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 0 6 |
+-----------------+
TEXT: 06-Log Open or Close....: %LOGC06 %LOGD06
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of log-open or log-close actions
processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 0 7 |
+-----------------+
TEXT: 07-Appl Terminate.......: %LOGC07 %LOGD07
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of region-start and
application-termination actions processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 0 8 |
+-----------------+
TEXT: 08-Appl Schedule........: %LOGC08 %LOGD08
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of application-schedule actions
processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 1 0 |
+-----------------+
TEXT: 0A-CPI-CI Start/Term....: %LOGC0A %LOGD0A
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of application-schedule actions for
explicit APPC transactions processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 1 6 |
+-----------------+
TEXT: 10-Security Violation...: %LOGC10 %LOGD10
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of terminal-security violations
processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 2 0 |
+-----------------+
TEXT: 14-Dial-Up Disconnect...: %LOGC14 %LOGD14
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of dial-up disconnected actions
processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 2 1 |
+-----------------+
TEXT: 15-Dial-Up Connected....: %LOGC15 %LOGD15
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of dial-up connected actions
processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 2 2 |
+-----------------+
TEXT: 16-Sign On/Off Event....: %LOGC16 %LOGD16
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of terminal signon and signoff records
processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 3 2 |
+-----------------+
TEXT: 20-Database Open........: %LOGC20 %LOGD20
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of database-open actions processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 3 3 |
+-----------------+
TEXT: 21-Database Close.......: %LOGC21 %LOGD21
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of database-close actions processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 3 6 |
+-----------------+
TEXT: 24-Database I/O Error...: %LOGC24 %LOGD24
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of database I/O errors processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 4 9 |
+-----------------+
TEXT: 31-Message Get Unique...: %LOGC31 %LOGD31
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of GUs on the message queue.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 5 3 |
+-----------------+
TEXT: 35-Message Enqueue......: %LOGC35 %LOGD35
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of message enqueues.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 5 4 |
+-----------------+
TEXT: 36-Message Dequeue......: %LOGC36 %LOGD36
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of dequeue save or delete messages
processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 6 4 |
+-----------------+
TEXT: 40-Checkpoint Records...: %LOGC40 %LOGD40
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of checkpoint records processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 6 5 |
+-----------------+
TEXT: 41-Batch Checkpoint.....: %LOGC41 %LOGD41
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of application checkpoints processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 6 6 |
+-----------------+
TEXT: 42-Log Buffer Control...: %LOGC42 %LOGD42
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of new log tapes used.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 6 9 |
+-----------------+
TEXT: 45-IMS Statistics.......: %LOGC45 %LOGD45
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of checkpoint-pool-statistic records
processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 1 7 6 |
+-----------------+
TEXT: 4C-Database Start/Stop..: %LOGC4C %LOGD4C
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of database started or stopped
actions processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 2 0 5 |
+-----------------+
TEXT: 69-Unauthorized Dial-Up.: %LOGC69 %LOGD69
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of unauthorized dial-up actions
processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 2 4 9 |
+-----------------+
TEXT: F9-CIMS Program Acct....: %LOGCF9 %LOGDF9
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of BMC MAINVIEW for IMS Online program
records processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 2 5 0 |
+-----------------+
TEXT: FA-CIMS Transaction.....: %LOGCFA %LOGDFA
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of BMC MAINVIEW for IMS Online
transaction records processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 2 5 4 |
+-----------------+
TEXT: FE-SMQ Front-End........: %LOGCFE %LOGDFE
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of shared-message-queue front-end
transactions generated.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 2 5 5 |
+-----------------+
TEXT: FF-LDR Synchronizer.....: %LOGCFF %LOGDFF
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
number of LDE Synchronizer records that were
passed from the Log Data Reduction Utility.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 2 5 6 |
+-----------------+
TEXT: ---------------------------------------------
Totals...............: %LOGCTOT %LOGDTOT
---------------------------------------------
TYPE: Information
REASON: Printed at the end of IMS DAILY processing if
the DEBUG data element is set. Shows the
total numbers of added and deleted records.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 3 0 0 |
+-----------------+
TEXT: DYIMSFMT Processing input data:
FileSet = %CTLFILE
DDName = %CTLDDN
Data set = %CTLDSN
SYSID = %CTLSYS
IMSID = %CTLIMS
OrgIMS = %CTLORG
IMSplex = %CTLPLX
Monitor = %CTLMON
Version = %CTLVER
Source = %CTLSRC
TYPE: Information
REASON: Printed at the beginning of each input DD
processed to describe the input options
specified in IMSOPS.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 3 0 1 |
+-----------------+
TEXT: IMS SYSTEM %CTLIMS RECORD COUNT = %RECOUNT
TYPE: Information
REASON: The CTLIMS and RECORD COUNT shown in the
message show the type of data input and the
number of records processed.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 3 0 2 |
+-----------------+
TEXT: INVALID TRANTYPE= %TRANTYPE FOR PSBNAME=
%PSBNAME TRANSACT= %TRANSACT
EXPECTING TRANTYPE=S, M, L, C, OR X.
TYPE: Warning
REASON: An invalid transaction type was returned by
the IMSRLRT user exit. Valid types are S, M,
L, C, and X.
ACTION: Correct prefix.MICS.PARMS(IMSRLRT) to assign
TRANTYPE to a value of S, M, L, C, or X.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.3
+-----------------+
| I M S 0 0 3 0 3 |
+-----------------+
TEXT: DYIMSFMT PROCESSING INPUT DATA FROM:
DDNAME= %CTLDDN
SYSID= %CTLSYS
IMSID= %CTLIMS
MONITOR= %CTLMON
VERSION= %CTLVER
SOURCE= %CTLSRC
TYPE: Information
REASON: Printed at the beginning of each input DD
being processed to describe the input options
specified in IMSOPS.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 3 0 4 |
+-----------------+
TEXT: %LOGUTMSG
TYPE: Information
REASON: Display of various information messages
produced by the Log Data Reduction programs.
Normally contains termination statistics.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 3 0 5 |
+-----------------+
TEXT: %LOGUTMSG
TYPE: Error
REASON: Display of various error messages produced by
the Log Data Reduction programs. Will
display reasons and suggested actions for
abnormal terminations.
ACTION: Follow recommendation in termination text.
REFERENCES: None
+-----------------+
| I M S 0 0 3 0 6 |
+-----------------+
TEXT: The IMS Log Infile User Exit processed:
%MSGGET GET requests and %MSGPUT PUT requests
TYPE: Information
REASON: Printed at the end of each input DD being
processed whose source is not LDE. Displays
the input and output requests processed by
the IMS log IFUE.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 3 0 7 |
+-----------------+
TEXT: %RECOUNT Records processed for system %CTLIMS
TYPE: Information
REASON: Printed at the end of each input DD processed
regardless of source. Displays the count of
records processed for each IMSID.
ACTION: None
REFERENCES: None
+-----------------+
| I M S 0 0 3 0 8 |
+-----------------+
TEXT: >>>>> DYIMSFMT ABNORMAL TERMINATION <<<<<
IMS VERSION ON PARM IS WRONG
TYPE: Error
REASON: The IMS version specified on the OPTIONS
statement in prefix.MICS.PARMS(IMSOPS) does
not match the IMS version in use on the
system.
ACTION: Correct the OPTIONS statement and rerun
IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 0 4 0 0 |
+-----------------+
TEXT: IMS AutoDetection Facility
TYPE: Information
REASON: Printed at the beginning of AutoDetection
LookAhead processing.
ACTION: None
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 0 4 0 1 |
+-----------------+
TEXT: IMF LookAhead processing results for:
FileSet = %FILESET
DDName = %DDNAME
Dataset = %DSNAME
OrgSYS = %ORGSYS
OrgIMS = %ORGIMS
CtlIMS = %CTLIMS
OrgVER = %LNGVER
IMS4510 = %GEN4510
IMS4571 = %GEN4571
IMS4551 = %GEN4551
TYPE: Information
REASON: Printed for each CA MICS Analyzer Option for
IMS data source that has caused invocation of
the AutoDetection LookAhead facility. This
displays information about the data
processed.
ACTION: None
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 0 4 0 2 |
+-----------------+
TEXT: >>> DYIMSFMT Abnormal Termination <<<
AutoDetect failed for DDname=%DDNAME
No records containing %AUTOFLD detected.
TYPE: Error
REASON: This indicates that AutoDetection LookAhead
processing failed to detect any of the
requested CA MICS Analyzer Option for IMS
OPTIONS fields during LookAhead processing.
The possible fields are being searched for
include ORGSYSID, ORGIMSID, and/or IMS
version information.
ACTION: None
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 0 4 0 3 |
+-----------------+
TEXT: >>> DYIMSFMT Abnormal Termination <<<
AutoDetection found an invalid IMS version.
Valid versions are 6.1 through 13.1,
version detected=%LNGVER
TYPE: Error
REASON: This indicates that AutoDetection LookAhead
processing found an unsupported IMS version
value during processing of the IMS data
source.
ACTION: Remove the IMS log data with the unsupported
version from the input stream and rerun the
DYIMSFMT job step.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 0 4 0 4 |
+-----------------+
TEXT: IMS LookAhead processing results for:
FileSet = %FILESET
DDName = %DDNAME
Dataset = %DSNAME
OrgSYS = %ORGSYS
OrgIMS = %ORGIMS
CtlIMS = %CTLIMS
OrgVER = %LNGVER
IMS4510 = %GEN4510
IMS4571 = %GEN4571
IMS4551 = %GEN4551
TYPE: Information
REASON: Printed for each CA MICS Analyzer Option for
IMS data source that has caused invocation of
the AutoDetection LookAhead facility. This
displays information about the data
processed.
ACTION: None
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 0 4 0 6 |
+-----------------+
TEXT: LDE LookAhead processing results for:
FileSet = %FILESET
DDName = %DDNAME
Dataset = %DSNAME
OrgSYS = %ORGSYS
OrgIMS = %ORGIMS
CtlIMS = %CTLIMS
OrgVER = %LNGVER
IMS4510 = %GEN4510
IMS4571 = %GEN4571
IMS4551 = %GEN4551
TYPE: Information
REASON: Printed for each CA MICS Analyzer Option for
IMS data source that has caused invocation of
the AutoDetection LookAhead facility. This
displays information about the data
processed.
ACTION: None
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 0 0 0 |
+-----------------+
TEXT: IMSPGEN GENERATION STARTED.
TYPE: Information
REASON: The IMSPGEN process has entered its main
program.
ACTION: None
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 0 0 1 |
+-----------------+
TEXT: USING %VALUE FAST PATH WORK FILE PAIRS.
TYPE: Information
REASON: This identifies work file allocation for
Fastpath transaction detail processing.
ACTION: None
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 0 0 2 |
+-----------------+
TEXT: USING %VALUE FULL FUNCTION WORK FILE PAIRS.
TYPE: Information
REASON: This identifies work file allocation for
full-function transaction detail processing.
ACTION: None
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 0 0 3 |
+-----------------+
TEXT: NOTE: IMF DATA REDUCTION STATUS IS %KEYWORK
TYPE: Information
REASON: This identifies whether BMC MAINVIEW for IMS
Online processing will be ACTIVE or INACTIVE
in CA MICS DAILY IMS processing.
ACTION: None
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 0 0 4 |
+-----------------+
TEXT: NOTE: NON-IMF DATA REDUCTION STATUS IS
%KEYWORK
TYPE: Information
REASON: This identifies whether non-BMC MAINVIEW for
IMS Online processing will be ACTIVE or
INACTIVE in CA MICS DAILY processing.
ACTION: None
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 0 1 0 |
+-----------------+
TEXT: IMSOPS INPUT LINE--> %LINE
TYPE: Information
REASON: This prints the image of an input line from
the prefix.MICS.PARMS(IMSOPS) member.
ACTION: None
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 0 9 8 |
+-----------------+
TEXT: IMSPGEN GENERATION ABNORMALLY TERMINATED.
CORRECT ERRORS NOTED ABOVE AND EXECUTE AGAIN.
TYPE: Error
REASON: This message closes the MICSLOG output of the
IMSPGEN if specification errors have
occurred.
ACTION: Make the changes identified by previous
MICSLOG messages and resubmit the IMSPGEN
job. Note that more than one error may have
been identified in previous messages and ALL
OF THE ERRORS must be corrected before
successfully completing IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 0 9 9 |
+-----------------+
TEXT: IMSPGEN COMPLETED SUCCESSFULLY.
TYPE: Information
REASON: This identifies successful completion of the
IMSPGEN process and successful generation of
all necessary material.
ACTION: Continue any checklist you may be following.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 1 0 1 |
+-----------------+
TEXT: PARMS(INPUTIMS) DDNAME SPECIFIED MORE THAN
ONCE, DDNAME=%KEYWORK
TYPE: Error
REASON: A ddname in the INPUTIMS member has been
defined two or more times. While this may
not cause the CA MICS IMS DAILY job to
abnormally terminate, it is incorrect.
ACTION: Either comment out or remove the incorrect
JCL statements for the listed ddname in
INPUTIMS; then resubmit the IMSPGEN job.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 1 0 2 |
+-----------------+
TEXT: PARMS(INPUTIMS) NO VALID DDNAMES SPECIFIED.
TYPE: Error
REASON: No valid JCL DD statements were found in the
INPUTIMS member. While this may not cause
the CA MICS IMS DAILY job to abnormally
terminate with a JCL error, it will cause
DAILY SAS logic to abend.
ACTION: Install DD statements into INPUTIMS to
identify the input file for every ddname used
in an OPTIONS statement in
prefix.MICS.PARMS(IMSOPS); then resubmit the
IMSPGEN job.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 0 1 |
+-----------------+
TEXT: PARMS(IMSOPS) KEYWORD NOT RECOGNIZED,
KEYWORD=%KEYWORK
TYPE: Error
REASON: A keyword has been misspelled.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 0 2 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=WORK ERROR FOUND:
FAST PATH WORK FILE PAIRS NOT IN RANGE 0-20,
SPECIFICATION=%KEYWORD2
TYPE: Error
REASON: The specification either is not a number or
is a number less than zero or greater than
20.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 0 3 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=WORK ERROR FOUND:
NORMAL WORK FILE PAIRS NOT IN RANGE 1-20,
SPECIFICATION=%KEYWORD3
TYPE: Error
REASON: The specification either is not a number or
is a number less than one or greater than 20.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 1 0 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=RESP ERROR FOUND:
RESPONSE VALUE NUMBER %K NOT SPECIFIED.
TYPE: Error
REASON: Exactly seven numbers must be specified on
the RESP statement.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 1 1 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=RESP ERROR FOUND:
RESPONSE VALUE NUMBER %K MUST BE POSITIVE,
LESS THAN 3600. SPECIFICATION=%KEYWORK
TYPE: Error
REASON: The response distribution threshold specified
either is not a number or is not within the
indicated bounds.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 1 2 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=RESP ERROR FOUND:
RESPONSE VALUE NUMBER %K MUST BE GREATER THAN
PREVIOUS VALUE.
SPECIFICATION=%KEYWORK PREVIOUS
VALUE=%LASTVAL
TYPE: Error
REASON: The response distribution threshold limit
printed is out of order. The limit numbers
must be specified in ascending value.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 1 3 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=RESP ERROR FOUND:
MORE THAN 7 RESPONSE VALUES SPECIFIED.
TYPE: Error
REASON: More than seven parameter words were found on
the RESP statement. Since only seven limits
are supported, the IMSPGEN is aborted rather
than accepting an eighth limit as a confusing
comment.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 2 0 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=TABLES ERROR FOUND:
LESS THAN 7 PARAMETER VALUES SPECIFIED.
TYPE: Error
REASON: The TABLES statement has too few values.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 2 1 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=TABLES ERROR FOUND:
LONG DRRN TABLE COUNT MUST BE 1-999999.
SPECIFICATION=%KEYWORD3
TYPE: Error
REASON: The value specified either is not a number or
is not within the indicated bounds.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 2 2 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=TABLES ERROR FOUND:
SHORT DRRN TABLE COUNT MUST BE 1-999999.
SPECIFICATION=%KEYWORD4
TYPE: Error
REASON: The value specified either is not a number or
is not within the indicated bounds.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 2 3 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=TABLES ERROR FOUND:
EMHB TABLE COUNT MUST BE 1-999999.
SPECIFICATION=%KEYWORD4
TYPE: Error
REASON: The value specified either is not a number or
is not within the indicated bounds.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 2 4 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=TABLES ERROR FOUND:
RT TABLE COUNT MUST BE 1-999999.
SPECIFICATION=%KEYWORD5
TYPE: Error
REASON: The value specified either is not a number or
is not within the indicated bounds.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 2 6 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=TABLES ERROR FOUND:
RT TABLE COUNT MUST BE GREATER THAN 0 IF
ANY IMS RELEASE IS EQUAL TO 6.1
TYPE: Error
REASON: The OPTIONS statement indicates that data
is from IMS release 6.1, but the TABLES
statement indicates that data is from a
release other than 6.1.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 3 0 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS ERROR FOUND:
ORIGINAL SYSID LENGTH MUST BE 1-4.
SPECIFICATION=%KEYWORD2
TYPE: Error
REASON: The value specified is longer than the
maximum allowable length of 4 characters.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 3 1 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS ERROR FOUND:
IMSID LENGTH MUST BE 1-4.
SPECIFICATION=%KEYWORD3
TYPE: Error
REASON: The value specified is longer than the
maximum allowable length of four characters.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 3 2 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS ERROR FOUND:
ORGSYSID IMSID COMBINATION MUST ONLY APPEAR
ON ONE OPTIONS STATEMENT.
SPECIFIED ORGSYSID=%KEYWORD2 IMSID=%KEYWORD3
TYPE: Error
REASON: The combination of original SYSID and IMSID
has been found on two or more OPTIONS
statements. This may be due to inadvertent
duplication of a statement or typographical
errors in the specified names of other
OPTIONS statements.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 3 3 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS ERROR FOUND:
MAXIMUM OPTIONS STATEMENTS PROCESSED, CONTACT
CA MICS PRODUCT SUPPORT.
TYPE: Error
REASON: The current maximum number of OPTIONS
statements is 50. More than 50 OPTIONS
statements were found in this IMSOPS member.
Some OPTIONS statements must be removed.
This may require installing other IMS
database units, which will improve the
overall performance of IMS data reduction by
providing parallel processing of high volume
data.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 3 4 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS ERROR FOUND:
DDNAME MUST ONLY APPEAR ON ONE OPTIONS
STATEMENT.
SPECIFICATION=%KEYWORD5
TYPE: Error
REASON: Two or more OPTIONS statements have the same
input ddname. This is not allowed because
the IMS log does not have the original SYSID
available and does not have the IMSID
available in all record types. Thus, CA MICS
associates these identifiers with input data
by assigning the identifiers to all data read
from a single input source.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 3 5 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS ERROR FOUND:
DDNAME NOT SPECIFIED IN PARMS(INPUTIMS).
SPECIFICATION=%KEYWORD5
TYPE: Error
REASON: The ddname specified is not defined in the
JCL for input data definition. The SAS daily
logic will not find that INFILE identifier
and will abend.
ACTION: Either correct the statement to the correct
ddname or add that ddname to the JCL in the
INPUTIMS member; then rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 3 6 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS ERROR FOUND:
DDNAME LENGTH MUST BE 1-8, NAME FORMAT.
SPECIFICATION=%KEYWORD5
TYPE: Error
REASON: The ddname specified either is too long or is
not a proper ddname (that is, does not begin
with a letter or national character).
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 3 7 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=OPTIONS warning:
IMS release specified is not supported,
OPTIONS statement will be bypassed.
Specification=%TOKEN4
TYPE: Warning
REASON: There is a typographical error in the IMS
version specification, or the version is no
longer supported or is not yet supported by
CA MICS. For example, IMS version 1.2 is no
longer supported by the CA MICS Analyzer
Option for IMS. The OPTIONS statement
containing the error is bypassed by IMSPGEN
and no code is generated to process the IMS
data specified by the OPTIONS statement.
ACTION: Either correct the statement in error and
rerun IMSPGEN or remove the OPTIONS statement
to avoid future warning messages.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 3 8 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS ERROR FOUND:
MONITOR SPECIFIED MUST BE IMF2 OR NOCIMS.
SPECIFICATION=%KEYWORD7
TYPE: Error
REASON: An incorrect monitor selection has been
specified.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 3 9 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS ERROR FOUND:
COLLECTION TIME INTERVAL MUST BE 1-60
MINUTES.
SPECIFICATION=%KEYWORD6
TYPE: Error
REASON: The value specified either is not a number or
is not within the indicated bounds.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 4 0 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS ERROR FOUND:
FAST PATH SWITCH MUST BE FP, MM OR NOFP.
SPECIFICATION=%KEYWORD8
TYPE: Error
REASON: A selection other than those listed was
specified.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 4 1 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS ERROR FOUND:
BMP COLLAPSE SWITCH MUST BE BMP OR NOBMP.
SPECIFICATION=%KEYWORD9
TYPE: Error
REASON: A selection other than those listed was
specified.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 4 2 |
+-----------------+
TEXT: PARMS(IMSOPS) OPTIONS STATEMENT REQUIRED BUT
NOT SPECIFIED.
TYPE: Error
REASON: No OPTIONS statement was recognized in the
IMSOPS member processed. At least one
OPTIONS statement is required.
ACTION: Add the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 4 3 |
+-----------------+
TEXT: PARMS(IMSOPS) RESP STATEMENT REQUIRED BUT NOT
SPECIFIED.
TYPE: Error
REASON: No RESP statement was recognized in the
IMSOPS member processed. One RESP statement
is required.
ACTION: Correct the statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 4 4 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS ERROR FOUND:
DDNAME IMSDUMMY IS A RESERVED NAME.
CHANGE THE DDNAME AND RERUN IMSPGEN.
TYPE: Error
REASON: The ddname IMSDUMMY is a reserved name for
internal use and is not allowed to be used in
IMSOPS.
ACTION: Change the ddname and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 4 5 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=TABLES Warning:
TRAN cell count parameter missing.
Using default=%TRTBL
TYPE: Warning
REASON: The TRAN cell count size parameter value is
missing from the TABLES statement. This is a
warning that the default value of 10,000 will
be used.
ACTION: The TRAN value setting may be added to the
TABLES statement and IMSPGEN can be rerun.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 4 6 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=OPTIONS error found:
Invalid optional parameter, keyword=%PNUM,
specification=%KEYWORK
TYPE: Error
REASON: The keyword parameter specified in the
message is in error. The specification
value is invalid and must be corrected.
ACTION: Correct the specified parameter value on the
OPTIONS statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 4 7 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=WFI error found:
AutoFlush Horizon must be 1-65535
Specification=%KEYWORD1
TYPE: Error
REASON: The WFI AutoFlush Horizon value is invalid.
The value must be within the range of 1 to
65535.
ACTION: Change the WFI AutoFlush Horizon value and
rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 4 8 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=OPTIONS error found:
WFI AutoFlush Horizon value invalid
keyword=%PNUM specification=%KEYWORK
AutoFlush Horizon must be 1-65535
TYPE: Error
REASON: The WFI AutoFlush Horizon value is invalid.
The value must be within the range of 1 to
65535.
ACTION: Change the WFI AutoFlush Horizon value and
rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 4 9 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=IMSDUPS error found:
Invalid parameter specification on statement.
Valid values are "ALLOW" or "DISALLOW".
TYPE: Error
REASON: IMSPGEN detected an invalid option value on
the IMSDUPS parameter statement.
ACTION: Correct the IMSDUPS value on the parameter
statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 5 0 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=IMSALIAS error found:
ORGIMSID positional parameter is missing.
TYPE: Error
REASON: The ORGIMSID parameter value was omitted on
the IMSALIAS statement. It is a required
parameter.
ACTION: Add the ORGIMSID value on the IMSALIAS
statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 5 1 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=IMSALIAS error found:
Length of ORGIMSID value .gt. 4 characters.
Specification=%KEYWORD2
TYPE: Error
REASON: The length of the ORGIMSID parameter on the
IMSALIAS statement was greater than the
maximum allowed 4 characters.
ACTION: Correct the ORGIMSID value on the IMSALIAS
statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 5 2 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=IMSALIAS warning:
Duplicate ORGIMSID value was encountered.
First alias set values will be in effect.
Specification=%KEYWORD2
TYPE: Warning
REASON: A duplicate ORGIMSID parameter value was
detected on an IMSALIAS statement. The
warning is issued because, if allowed to
exist, only the first encountered alias
specification will be used for region
mapping.
ACTION: If the duplicate specification is, in fact,
an error, correct the ORGIMSID parameter
value and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 5 3 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=IMSALIAS error found:
IMSID positional parameter is missing.
TYPE: Error
REASON: The IMSID parameter value was omitted on the
IMSALIAS statement. It is a required
parameter.
ACTION: Add the IMSID value on the IMSALIAS statement
and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 5 4 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=IMSALIAS error found:
Length of IMSID value .gt. 4 characters.
Specification=%KEYWORD3
TYPE: Error
REASON: The length of the IMSID parameter on the
IMSALIAS statement was greater than the
maximum 4 characters allowed.
ACTION: Correct the IMSID value on the IMSALIAS
statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 5 5 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=IMSALIAS error found:
Duplicate IMSID value was encountered.
Possible conflict/corruption of database
could result.
Specification=%KEYWORD3
TYPE: Error
REASON: A duplicate IMSID parameter value was
detected on an IMSALIAS statement. The error
is issued because mapping of two or more IMS
regions to the same logical IMSID could cause
undesired corruption of the database files.
ACTION: Correct the duplicate IMSID value on the
IMSALIAS statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 5 6 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=OPTIONS error found:
Invalid parameter combination was specified.
AutoDetection may only be specified with the
IMF2 monitor.
TYPE: Error
REASON: AutoDetection processing was requested for
one or more parameters on the OPTIONS
statement. This facility is only supported
for BMC MAINVIEW for IMS Online transaction
data.
ACTION: Correct the "monitor" parameter on the
OPTIONS statement and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 5 8 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=OPTIONS error found:
Continuation character is not the last value
on the statement.
TYPE: Error
REASON: The continuation character, a plus (+) sign,
was detected on an OPTIONS statement set.
When specified, the continuation character
must be the last value on a given line.
ACTION: Correct the placement of the continuation
character on the OPTIONS statement and rerun
IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 5 9 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=OPTIONS error found:
Expected continuation not found. A control
keyword was encountered during parsing.
Specification=%KEYWORD9
TYPE: Error
REASON: During execution of continuation processing
on an OPTIONS statement, a control command
was encountered. Parsing will terminate for
the continued statement and the encountered
control command will be processed.
ACTION: Correct the continuation specification on the
OPTIONS statement in error and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 6 2 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=OPTIONS error found:
SKIPLOG value must be 0-999999999.
Parameter=n, Specification=n
TYPE: Error
REASON: The value of the SKIPLOG parameter is greater
than the maximum allowed.
ACTION: Correct the value specified for the SKIPLOG
parameter on the OPTIONS statement in error
and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 2 6 3 |
+-----------------+
TEXT: PARMS(IMSOPS) Statement=OPTIONS error found:
ENDLOG value must be 0-999999999.
Parameter=n, Specification=n
TYPE: Error
REASON: The value of the ENDLOG parameter is greater
than the maximum allowed.
ACTION: Correct the value specified for the ENDLOG
parameter on the OPTIONS statement in error
and rerun IMSPGEN.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 5 0 0 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=WORK/OPTIONS WARNING:
NO OPTIONS STATEMENTS SPECIFY NOCIMS.
NUMBER OF FAST PATH WORK FILES RESET TO ZERO.
TYPE: Warning
REASON: All OPTIONS statements specify IMF2 as the
monitor data source, so the IMS_IS and IMS_IA
files will contain no data. A non-zero
number of Fastpath work files was specified
on the WORK statement, but has been reset to
zero (work files are not used when BMC
MAINVIEW for IMS Online is the data source)
to improve the DASD allocation performance of
the daily process.
ACTION: No action is required, but you should review
the specifications to make sure the intended
configuration is accurately specified.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 5 0 1 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=WORK/OPTIONS WARNING:
NO OPTIONS STATEMENTS SPECIFY FP.
NUMBER OF FAST PATH WORK FILES RESET TO ZERO.
TYPE: Warning
REASON: All OPTIONS statements specifying NOCIMS as
the monitor method also specify NOFP or MM.
Thus, Fastpath EMHB transactions will not be
passed to the CA MICS Analyzer Option for
IMS, and the IMS_IS and IMS_IA files will
contain no data. A non-zero number of
Fastpath work files was specified on the WORK
statement; if generated, the work files would
not be used. Therefore, the number of work
files has been reset to zero, improving the
DASD allocation performance of the daily
process.
ACTION: No action is required, but you should review
the specifications to make sure the intended
configuration is accurately specified.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 5 0 2 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=WORK/OPTIONS WARNING:
OPTIONS STATEMENTS SPECIFIES NOCIMS AND FP.
NUMBER OF FAST PATH WORK FILES RESET TO ONE.
TYPE: Warning
REASON: One or more OPTIONS statements specifying
NOCIMS as the monitor method also specified
FP. Thus, Fastpath EMHB transactions will be
passed to the CA MICS Analyzer Option for
IMS, and the IMS_IS and IMS_IA files may
contain data. Zero Fastpath work files were
specified on the WORK statement, but if
generated would not prevent Fastpath EMHB
transaction data from populating those
database files. Thus, the number of work
files has been set to one, enabling data to
flow into those files.
ACTION: No action is required, but you should review
the specifications to make sure the intended
configuration is accurately specified.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
+-----------------+
| I M S 0 3 5 0 3 |
+-----------------+
TEXT: PARMS(IMSOPS) IMSCGEN AGREEMENT WARNING:
THE IMS_IS AND IMS_IA FILES ARE INACTIVE.
NUMBER OF FAST PATH WORK FILES RESET TO ZERO.
TYPE: Warning
REASON: The IMS_IS and IMS_IA files have been
tailored to inactive in the IMSCGEN process,
and thus will contain no data. A non-zero
number of Fastpath work files was specified
on the WORK statement, but if generated would
not be used and would expend considerable
work DASD resource allocations. Thus, the
number of work files has been set to zero,
improving the DASD allocation performance of
the daily process.
ACTION: No action is required, but you should review
the specifications to make sure the intended
configuration is accurately specified. This
includes the possibility of tailoring the IMS
database specifications in GENLIB(IMSGENIN).
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
System Modification Guide, Chapter 6
+-----------------+
| I M S 0 3 5 0 4 |
+-----------------+
TEXT: PARMS(IMSOPS) IMSCGEN AGREEMENT WARNING:
ALL OPTIONS STATEMENTS SPECIFY IMF2. THE
IMS_IS OR IMS_IA FILES ARE ACTIVE BUT UNUSED
FOR IMF. REVIEW OPTIONS STATEMENTS IN
IMSOPS, OR TAILOR THE IMS_IS AND IMS_IA FILES
TO INACTIVE STATUS.
TYPE: Warning
REASON: All OPTIONS statements specify IMF2 as the
monitor data source. Thus, the IMS_IS and
IMS_IA files will contain no data. One or
both of these files are still active in
component generator file tailoring. These
files cannot be populated, so may be tailored
to inactive. This will save some resources
during the DAILY IMS processing and will save
some database space.
ACTION: No action is required, but you should review
the specifications to make sure the intended
configuration is accurately specified. This
includes the possibility of tailoring the IMS
database specifications in GENLIB(IMSGENIN).
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
System Modification Guide, Chapter 6
+-----------------+
| I M S 0 3 5 0 5 |
+-----------------+
TEXT: PARMS(IMSOPS) IMSCGEN AGREEMENT WARNING:
THE IMS_IA OR IMS_IS FILE IS ACTIVE BUT THE
NUMBER OF FAST PATH WORK FILES IS SET TO
ZERO. REVIEW OPTIONS STATEMENTS IN IMSOPS,
OR TAILOR THE IMS_IS AND IMS_IA FILES TO
INACTIVE STATUS.
TYPE: Warning
REASON: No OPTIONS statements that specify NOCIMS as
the monitor data source also specify FP to
activate Fastpath processing. Thus the
IMS_IS and IMS_IA files will contain no data.
One or both of these files are still active
in component generator file tailoring. These
files cannot be populated, so may be tailored
to inactive. This will save some resources
during the DAILY IMS processing, and will
save some database space.
ACTION: No action is required, but you should review
the specifications to make sure the intended
configuration is accurately specified. This
includes the possibility of tailoring the IMS
database specifications in GENLIB(IMSGENIN).
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
System Modification Guide, Chapter 6
+-----------------+
| I M S 0 3 5 0 6 |
+-----------------+
TEXT: PARMS(IMSOPS) STATEMENT=OPTIONS WARNING:
NO OPTIONS STATEMENT FOUND WITH
DDNAME=%KEYWORK WHICH WAS DEFINED IN
PARMS(INPUTIMS).
TYPE: Warning
REASON: A ddname has been defined in INPUTIMS for the
purpose of allocating a data set during the
DAILY processing of IMS data. However, no
corresponding ddname appears in an OPTIONS
statement in IMSOPS. This may be intentional
(in support of some user modification to the
process) or it may be unintentional,
indicating, for example, that a newly-removed
IMS system OPTIONS statement has had its
input allocation left in the JCL.
ACTION: No action is required, but you should review
the specifications to make sure the intended
configuration is accurately specified.
REFERENCES: CA MICS Analyzer Option for IMS Guide,
Section 7.3.4
Copyright © 2014 CA.
All rights reserved.
|
|