Appendix A. MESSAGES
This appendix lists all messages generated by the CA MICS
VAX/VMS Analyzer. Some messages are generated during the
processing of the control statements, while others are caused
by various conditions in the data found during the
processing. The messages are listed in ascending numerical
sequence and include the full text of the message, the type,
the reason for the messages, appropriate user action, and
applicable references to documentation.
The following type codes are used to categorize the messages:
Information designates a note that documents a CA MICS
VAX/VMS Analyzer option or potentially
important feature in the data.
Warning designates a condition in either the data or
control statements that does not affect the
CA MICS VAX/VMS Analyzer's operation but
that may lead to unexpected results.
Error designates that a problem has been
encountered with a control statement that
will prevent a successful run of the CA MICS
VAX/VMS Analyzer. Execution is stopped
after all control statements are processed.
The message text often includes references to information
that is contained in a control statement or values of
permanent or temporary variables created during CA MICS
VAX/VMS Analyzer processing. In the description below, the
message text contains a word beginning with a percent sign
(%), which indicates that a value will be substituted into
the text at execution time.
+---------+
| DEX0001 |
+---------+
TEXT: INPUT: DSN=%X VOL=SER=%PVOL
TYPE: Information
REASON: Logs the name of each input parameter read
by the DEXPGEN process.
ACTION: None
REFERENCES: Section 7.3.3
+---------+
| DEX0002 |
+---------+
TEXT: DEXOPS OPTIONS SYSTEM ID: %KEYWORD2 IS MORE
THAN 4 CHARACTERS IN LENGTH
TYPE: Error
REASON: The indicated SYSID on the DEXOPS OPTIONS
statement was longer than the 4-character
maximum allowed.
ACTION: Shorten the SYSID name on the OPTIONS
statement in prefix.MICS.PARMS(DEXOPS).
REFERENCES: Section 7.3.1
+---------+
| DEX0003 |
+---------+
TEXT: SYSID PARM CPU MODEL NUMBER: %KEYWORD3 IS
MORE THAN 4 CHARACTERS IN LENGTH
TYPE: Warning
REASON: The indicated CPU model number in SYSID was
longer than the 4-character maximum
expected.
ACTION: Check the CPU model number on the statement
in prefix.MICS.PARMS(SYSID).
REFERENCES: - Section 7.4
- PIOM Guide 2.3.2.2
- see also Administrative Newsletter,
"Guidelines for Coding SYSID Parms"
+---------+
| DEX0004 |
+---------+
TEXT: DEXOPS DEFAULT DURATION VALUE: %KEYWORD4 IS
NOT A POSITIVE NUMERIC VALUE, AS REQUIRED.
TYPE: Error
REASON: The default duration value for a DEXSUS data
statement is not a valid numeric value or is
missing entirely.
ACTION: Correct the default duration value on the
DEXSUS statement in
prefix.MICS.PARMS(DEXOPS).
REFERENCES: Section 7.3.1
+---------+
| DEX0005 |
+---------+
TEXT: SCP SPECIFIED IN SYSID FOR %KEYWORD2 IS NOT
A VAX/VMS SYSTEM.
VALID VALUES ARE *, VMS, OR VAXVMS.
TYPE: Warning
REASON: The SCP name in SYSID is not specified
correctly or the field is missing entirely.
ACTION: Provide a recognized VAX/VMS SCP name on
the statement in prefix.MICS.PARMS(SYSID).
REFERENCES: - Section 7.4
- PIOM Guide 2.3.2.2
- see also Administrative Newsletter,
"Guidelines for Coding SYSID Parms"
+---------+
| DEX0006 |
+---------+
TEXT: DEXOPS NODE NAME MISSING FOR %KEYWORD2 ENTRY
TYPE: Error
REASON: The indicated entry on the DEXOPS OPTIONS
statement was missing a node name entry to
map to the ORGSYSID listed as %KEYWORD2.
ACTION: Specify the VAX node name that is to be
mapped to the ORGSYSID, on the OPTIONS
statement in prefix.MICS.PARMS(DEXOPS).
REFERENCES: Section 7.3.1
+---------+
| DEX0007 |
+---------+
TEXT: MORE THAN ONE OPTIONS STATEMENT FOR ORGSYSID
%KEYWORD2 FOUND IN DEXOPS
TYPE: Error
REASON: More than one OPTIONS statement was included
in the DEXOPS member for the same ORGSYSID.
ACTION: Review prefix.MICS.PARMS(DEXOPS) and correct
or remove the inappropriate OPTIONS
statement.
REFERENCES: Section 7.3.1
+---------+
| DEX0008 |
+---------+
TEXT: INVALID NUMERIC DATA: %CVAL
TYPE: Error
REASON: Value in parameter line is not a valid
numeric value.
ACTION: Review prefix.MICS.PARMS(DEXOPS) and correct
the indicated statement.
REFERENCES: Section 7.3.1
+---------+
| DEX0010 |
+---------+
TEXT: ORIGINAL SYSID: %KEYWORD1 HAS BEEN
PREVIOUSLY DEFINED.
TYPE: Error
REASON: The ORGSYSID has been defined more than once
in the SYSID parameter.
ACTION: Review prefix.MICS.PARMS(SYSID) and correct
the inappropriate ORGSYSID definition.
REFERENCES: - Section 7.4
- PIOM Guide 2.3.2.2
- see also Administrative Newsletter,
"Guidelines for Coding SYSID Parms"
+---------+
| DEX0011 |
+---------+
TEXT: THE MAXIMUM SYSID LIMIT HAS BEEN REACHED.
PLEASE CONTACT CA MICS PRODUCT SUPPORT.
TYPE: Error
REASON: More than 100 entries were specified in
prefix.MICS.PARMS(SYSID).
ACTION: Contact CA MICS Product Support.
REFERENCES: - Section 7.4
- PIOM Guide 2.3.2.2
- see also Administrative Newsletter,
"Guidelines for Coding SYSID Parms"
+---------+
| DEX0012 |
+---------+
TEXT: SPECIFIED DDNAME: %KEYWORD3 IS MORE THAN 8
CHARACTERS IN LENGTH.
TYPE: Error
REASON: DDnames cannot be more than 8 characters in
length.
ACTION: Reduce the length of the DDname on the
statement indicated (MONITOR, ACCOUNT, or
COMMON) in prefix.MICS.PARMS(DEXOPS). Also
ensure that the INPUTDEX PARMS member
specifies a corresponding DD statement.
REFERENCES: Sections 7.3.1 and 7.3.2
+---------+
| DEX0013 |
+---------+
TEXT: THIS ORGSYSID: %KEYWORD2 AND DATA SOURCE:
%KEYWORD1 HAVE ALREADY BEEN DEFINED.
TYPE: Error
REASON: For a given ORGSYSID, only one MONITOR and
one ACCOUNT statement may be defined.
ACTION: Review prefix.MICS.PARMS(DEXOPS) and correct
the inappropriate MONITOR or ACCOUNT
statement so that you are not attempting to
assign two different input DDnames to the
same ORGSYSID for the same data type.
REFERENCES: Section 7.3.1
+---------+
| DEX0014 |
+---------+
TEXT: SPECIFIED ORGSYSID: %KEYWORD2 HAS NOT BEEN
DEFINED ON A PREVIOUS OPTION STATEMENT
TYPE: Error
REASON: The ORGSYSID named on the MONITOR or ACCOUNT
statement must first be defined on an
OPTIONS statement.
ACTION: Review prefix.MICS.PARMS(DEXOPS) and add
correct the appropriate OPTIONS statement.
REFERENCES: Section 7.3.1
+---------+
| DEX0015 |
+---------+
TEXT: SUBPARAMETER: %KEYWORD2 IS NOT VALID ON A
%KEYWORD1 STATEMENT
TYPE: Error
REASON: The subparameter is not a recognized entry
for the indicated statement.
ACTION: Review prefix.MICS.PARMS(DEXOPS) and correct
the indicated statement.
REFERENCES: Section 7.3.1
+---------+
| DEX0016 |
+---------+
TEXT: KEYWORD: %KEYWORD1 IS NOT RECOGNIZED
TYPE: Error
REASON: The keyword statement is not a recognized
entry for DEXOPS.
ACTION: Review prefix.MICS.PARMS(DEXOPS) and correct
the indicated statement.
REFERENCES: Section 7.3.1
+---------+
| DEX0017 |
+---------+
TEXT: END OF MEMBER %PMEM INPUT
TYPE: Information
REASON: Indicates end of each input parameter read
by the DEXPGEN process.
ACTION: None
REFERENCES: Section 7.3.3
+---------+
| DEX0018 |
+---------+
TEXT: REQUIRED STATEMENT MISSING: %STYP
TYPE: Error
REASON: The keyword statement is a required entry
for DEXOPS.
ACTION: Review prefix.MICS.PARMS(DEXOPS) and supply
the required statement.
REFERENCES: Section 7.3.1
+---------+
| DEX0019 |
+---------+
TEXT: ERROR(S) ENCOUNTERED IN DEXOPS UNIT
PARAMETER DEFINITIONS, MACRO GENERATION
ABORTED. CORRECT THE ERROR(S), AND
RE-EXECUTE DEXPGEN
TYPE: Error
REASON: At least one fatal error was encountered
while processing DEXOPS.
ACTION: Correct the error(s) and resubmit the
DEXPGEN job.
REFERENCES: Section 7.3.1, 7.3.2, and 7.3.3
+---------+
| DEX0020 |
+---------+
TEXT: DUPLICATE DDNAMES NOT ALLOWED: %KEYWORD3
TYPE: Error
REASON: The DDname has already been specified for
use with another MONITOR or ACCOUNT input
source.
ACTION: Review prefix.MICS.PARMS(DEXOPS) and supply
a unique DDname for use with this input data
source.
REFERENCES: Sections 7.3.1 and 7.3.2
+---------+
| DEX0021 |
+---------+
TEXT: COMMON INPUT DD NOT ALLOWED FOR: %KEYWORD1
TYPE: Error
REASON: COMMON input requested a data source (e.g.,
ACCOUNT) that does not contain system
identification information. COMMON cannot
support this data source because SYSID can
not be determined.
ACTION: Supply a unique DDname in the indicated
statement in prefix.MICS.PARMS(DEXOPS), and
provide a corresponding DD statement in
prefix.MICS.PARMS(INPUTDEX).
REFERENCES: Sections 7.3.1, 7.3.2, and 9.4
+---------+
| DEX0022 |
+---------+
TEXT: COMMON INPUT DD FOR %KEYWORD1 HAS ALREADY
BEEN DEFINED.
TYPE: Error
REASON: Only one common DD is supported for a given
data type (i.e., MONITOR).
ACTION: Use the common DD already defined or supply
a unique DDname in the indicated statement
in prefix.MICS.PARMS(DEXOPS). Check the
corresponding DD statements in
prefix.MICS.PARMS(INPUTDEX).
REFERENCES: Sections 7.3.1 and 7.3.2
+---------+
| DEX0023 |
+---------+
TEXT: MEMBER %PMEM IS EMPTY OR CONTAINS NO DD
STATEMENTS
TYPE: Error
REASON: No active DD statements were found in the
indicated member in prefix.MICS.PARMS. The
DDnames used in DEXOPS require matching DD
statements in the input JCL.
ACTION: Review prefix.MICS.PARMS member and supply
the appropriate DD statements.
REFERENCES: Section 7.3.2
+---------+
| DEX0024 |
+---------+
TEXT: DDNAME %KEYWORD3 NOT FOUND IN INPUTDEX
TYPE: Error
REASON: No matching DD statement was found in
prefix.MICS.PARMS(INPUTDEX). The DDnames
used in DEXOPS require matching DD
statements in the input JCL.
ACTION: Review prefix.MICS.PARMS(INPUTDEX) and
prefix.MICS.PARMS(DEXOPS) and correct the
discrepancy in the use of DDnames.
REFERENCES: Sections 7.3.1 and 7.3.2
+---------+
| DEX0025 |
+---------+
TEXT: INPUTDEX DDNAME: %Y NOT REFERENCED IN
DEXOPS
TYPE: Warning
REASON: DDnames are not processed by the DAILY job
unless they are specified for use in
prefix.MICS.PARMS(DEXOPS).
ACTION: Check prefix.MICS.PARMS(INPUTDEX) to ensure
that the presence of the unreferenced DDname
is intentional.
REFERENCES: Section 7.3.2
+---------+
| DEX0029 |
+---------+
TEXT: INPUTDEX DDNAME: %X IS MORE THAN 8
CHARACTERS IN LENGTH.
TYPE: Error
REASON: DDnames longer than 8 characters will cause
the DAILY job to end with a JCL error.
ACTION: Correct the invalid DDname in
prefix.MICS.PARMS(INPUTDEX).
REFERENCES: Section 7.3.2
+---------+
| DEX0031 |
+---------+
TEXT: ORGSYSID %KEYWORD2 IS NOT DEFINED IN
PARMS(SYSID).
TYPE: Error
REASON: The ORGSYSID has not been defined in the
SYSID parameter, or BASPGEN may need to be
run.
ACTION: Review prefix.MICS.PARMS(SYSID) and add the
appropriate ORGSYSID definition if needed.
Run BASPGEN and then re-run DEXPGEN (or
simply run ALLPGEN).
REFERENCES: - Section 7.4
- PIOM Guide 2.3.2.2
- see also Administrative Newsletter,
"Guidelines for Coding SYSID Parms"
+---------+
| DEX0032 |
+---------+
TEXT: MORE THAN ONE DISKACCT STATEMENT FOUND IN
DEXOPS.
TYPE: Error
REASON: No more than one DISKACCT statement should
be specified in the DEXOPS member. This
option applies to the entire unit and cannot
be specified separately for different input
systems.
ACTION: Review prefix.MICS.PARMS(DEXOPS) and remove
the inappropriate DISKACCT statement.
REFERENCES: Section 7.3.1
+---------+
| DEX0041 |
+---------+
TEXT: >>> START OF DEXACT MODULE PROCESSING <<<
TYPE: Information
REASON: Indicates start of input format processing
for VMS ACCOUNTING data.
ACTION: None
REFERENCES: Section 9.2.2
+---------+
| DEX0042 |
+---------+
TEXT: >>> END OF DEXACT MODULE PROCESSING <<<
TYPE: Information
REASON: Indicates end of input format processing for
VMS ACCOUNTING data.
ACTION: None
REFERENCES: Section 9.2.2
+---------+
| DEX0043 |
+---------+
TEXT: >>> START OF DEXSUSA MODULE PROCESSING <<<
TYPE: Information
REASON: Indicates start of input format processing
for CA MICS DEXSUS data.
ACTION: None
REFERENCES: Section 9.2.2
+---------+
| DEX0044 |
+---------+
TEXT: >>> END OF DEXSUSA MODULE PROCESSING <<<
TYPE: Information
REASON: Indicates end of input format processing for
CA MICS DEXSUS data.
ACTION: None
REFERENCES: Section 9.2.2
+---------+
| DEX0046 |
+---------+
TEXT: >>> START OF DEXMON MODULE PROCESSING <<<
TYPE: Information
REASON: Indicates start of input format processing
for VMS MONITOR data.
ACTION: None
REFERENCES: Section 9.2.2
+---------+
| DEX0047 |
+---------+
TEXT: >>> END OF DEXMON MODULE PROCESSING <<<
TYPE: Information
REASON: Indicates end of input format processing for
VMS MONITOR data.
ACTION: None
REFERENCES: Section 9.2.2
+---------+
| DEX0054 |
+---------+
TEXT: ORGSYSID= %ORGSYSID DDNAME= %DDNAME DATASET
NAME= %DSNAME
TYPE: Information
REASON: Describe each input file processed from the
VMS ACCOUNTING data source. Message is
issued before first input from each data
set.
ACTION: None
REFERENCES: None
+---------+
| DEX0055 |
+---------+
TEXT: START OF INPUT FROM DDNAME= %DDNAME DATASET
NAME= %DSNAME
TYPE: Information
REASON: Describe each input file processed from the
VMS MONITOR and CA MICS DEXSUS data sources.
Message is issued before first input from
each data set.
ACTION: None
REFERENCES: None
+---------+
| DEX0056 |
+---------+
TEXT: ORGSYSID CANNOT BE DETERMINED. RUN ABORTED
TYPE: Error
REASON: Issued during VMS MONITOR data source input
processing when SYSTEM IDENTIFICATION record
(type 129) is not present. Also issued
during CA MICS DEXSUS data source input
processing when SYSTEM INFORMATION records
(type 01) are not present. Indicates an
incomplete and possibly erroneous input data
file. May also be issued from VMS
ACCOUNTING input if DEXOPS COMMON EXIT code
is in effect.
ACTION: Locate missing records, or reconstruct the
input file. If you are using COMMON EXITS
in DEXOPS, check the logic that assigns
VAXID and ORGSYSID in your exit code.
REFERENCES: Sections 6.3.2, 6.4.2, 9.2.1, and 9.4
+---------+
| DEX0057 |
+---------+
TEXT: TYPE 128 RECORD READ. RECORD WILL NOT BE
KEPT. MONITOR START= %WRK_DTM1 DURATION=
%DEXDUR
TYPE: Information
REASON: Provide the file header information for each
input file processed from the VMS MONITOR
data source. Record is discarded and
therefore not included in further record
counts.
ACTION: None
REFERENCES: Sections 6.3.1 and 9.2.1
+---------+
| DEX0058 |
+---------+
TEXT: NODE NAME: %NODID FROM PARMS(DEXOPS) DOES
NOT MATCH NODE NAME: %ZORGID IN MONITOR 129
REC. DEXPGEN MAY BE REQUIRED. OPTION
VERIFY=ABORT SPECIFIED IN DEXOPS.
TYPE: Error
REASON: Cannot determine correct ORGSYSID to assign
to the data because the VAX node name found
in the input data does not agree with node
name information generated for the input
DDname from DEXOPS.
ACTION: Check the VAX node name that is to be mapped
to the ORGSYSID on the OPTIONS statement in
prefix.MICS.PARMS(DEXOPS). Compare to the
node information given in this message.
Determine if discrepancy is due to wrong
input file, incorrect DEXOPS specification,
or requirement for DEXPGEN.
If you are using COMMON EXITS in the DEXOPS
parameter, check the logic that assigns
(reads) VAXID in your exit code. You can
recognize this case if the message indicates
a node name of *DEXINPM* from PARMS(DEXOPS).
REFERENCES: Sections 6.3.2, 7.3.1, 7.3.3, and 9.4
+---------+
| DEX0059 |
+---------+
TEXT: NODE NAME: %NODID FROM PARMS(DEXOPS) DOES
NOT MATCH NODE NAME: %ZORGID IN MONITOR 129
REC. DEXPGEN MAY BE REQUIRED. OPTION
VERIFY=NOABORT SPECIFIED IN DEXOPS.
TYPE: Warning
REASON: Cannot determine correct ORGSYSID to assign
to the data because the VAX node name found
in the input data does not agree with node
name information generated for the input
DDname from DEXOPS.
ACTION: Check the VAX node name that is to be mapped
to the ORGSYSID on the OPTIONS statement in
prefix.MICS.PARMS(DEXOPS). Compare to the
node information given in this message.
Determine if discrepancy due to wrong input
file, incorrect DEXOPS specification, or
requirement for DEXPGEN.
If you are using COMMON EXITS in the DEXOPS
parameter, check the logic that assigns
(reads) VAXID in your exit code. You can
recognize this case if the message indicates
a node name of *DEXINPM* from PARMS(DEXOPS).
REFERENCES: Sections 6.3.2, 7.3.1, 7.3.3, and 9.4
+---------+
| DEX0060 |
+---------+
TEXT: TYPE 129 RECORD READ. RECORD WILL NOT BE
KEPT. ORGSYSID= %ORGSYSID IDENTIFIES NODE=
%ZORGID SYSTEM BOOT TIME= %WRK_DTM1
TYPE: Information
REASON: Provide the SYSID information for each input
file processed from the VMS MONITOR data
source. Record is discarded and therefore
not included in further record counts.
ACTION: None
REFERENCES: Sections 6.3.2 and 9.2.1
+---------+
| DEX0061 |
+---------+
TEXT: ORGSYSID= %ORGSYSID
FIRST INPUT TIME= %WRK_DTM1'
TYPE: Information
REASON: Provide the SYSID and TIMESTAMP information
for the first measurement data record of
each input file processed from the VMS
MONITOR data source.
ACTION: None
REFERENCES: Section 9.2.1
+---------+
| DEX0062 |
+---------+
TEXT: TYPE 129 RECORD FOUND BEFORE TYPE 128
RECORD. UNEXPECTED RECORD SEQUENCE. CHECK
INPUT DATA.
TYPE: Error
REASON: Implies that VMS MONITOR version and other
header record (type 128) data will not be
available to the CA MICS VAX/VMS Analyzer.
Because record layouts are unknown for an
unrecognized version, processing is aborted.
ACTION: Ensure that the correct input file has been
provided, and if so, contact CA MICS Product
Support.
REFERENCES: Sections 6.3.1 and 9.2.1
+---------+
| DEX0063 |
+---------+
TEXT: NO TYPE 129 RECORD FOUND FOLLOWING TYPE 128
UNEXPECTED RECORD SEQUENCE. CHECK INPUT
DATA.
TYPE: Error
REASON: Implies that VMS MONITOR System Information
header record (Type 129) data will not be
available to the CA MICS VAX/VMS Analyzer.
Because this record is needed to tie the
nodeid to the sysid, processing is aborted.
ACTION: Ensure that the correct input file has been
provided, and if so, contact CA MICS Product
Support.
REFERENCES: Sections 6.3.2 and 9.2.1
+---------+
| DEX0066 |
+---------+
TEXT: UNKNOWN MONITOR VERSION: %ZZMONVR , RUN
ABORTED.
TYPE: Error
REASON: Indicates a VMS MONITOR version found in a
header record (type 128) that is not
recognized by the CA MICS VAX/VMS Analyzer.
Because record layouts are unknown for an
unrecognized version, processing is aborted.
ACTION: Ensure that the correct input file has been
provided, and if so, contact CA MICS Product
Support.
REFERENCES: Sections 6.3.1 and 9.2.1
+---------+
| DEX0071 |
+---------+
TEXT: TYPE 00 RECORD READ. RECORD WILL NOT BE
KEPT. DEXSUS START= %WRK_DTM1 MAINTLVL=
%DEXTMPML
TYPE: Information
REASON: Provide the file header information for each
input file processed from the CA MICS DEXSUS
data source. The record is discarded and
therefore not included in further record
counts.
ACTION: None
REFERENCES: Section 6.4.1
+---------+
| DEX0072 |
+---------+
TEXT: UNKNOWN MAINTLVL: %DEXTMPML , RUN ABORTED.
TYPE: Error
REASON: Indicates a CA MICS DEXSUS version and
maintenance level found in a header record
(type 00) that is not recognized by the
CA MICS VAX/VMS Analyzer. Because record
layouts are unknown for an unrecognized
version, processing is aborted.
ACTION: Ensure that the correct input file has been
provided, and if so, contact CA MICS Product
Support.
REFERENCES: Sections 6.4.1 and 9.2.1
+---------+
| DEX0073 |
+---------+
TEXT: UNKNOWN VMS VERSION: %SYUVMSVR, RUN ABORTED.
TYPE: Error
REASON: Indicates the VMS version found in the first
data record following a system information
separator record (type 01) does not match
any VMS version recognized by the CA MICS
VAX/VMS Analyzer. Because record layouts
are unknown for an unrecognized version,
processing is aborted.
ACTION: Ensure that the correct input file has been
provided, and if so, contact CA MICS Product
Support.
REFERENCES: Sections 6.4.2
+---------+
| DEX0074 |
+---------+
TEXT: NODE NAME: %NODID FROM PARMS(DEXOPS) DOES
NOT MATCH NODE NAME: %DEXNODE IN DEXSUS
01-VAX/VMS REC. DEXPGEN MAY BE REQUIRED.
OPTION VERIFY=ABORT SPECIFIED IN DEXOPS.
TYPE: Error
REASON: Cannot determine correct ORGSYSID to assign
to the data because the VAX node name found
in the input data does not agree with node
name information generated for the input
DDname from DEXOPS.
ACTION: Check the VAX node name that is to be mapped
to the ORGSYSID on the OPTIONS statement in
prefix.MICS.PARMS(DEXOPS). Compare to the
node information given in this message.
Determine if the discrepancy is due to the
wrong input file, incorrect DEXOPS
specification, or requirement for DEXPGEN.
If you are using COMMON EXITS in the DEXOPS
parameter, check the logic that assigns
(reads) VAXID in your exit code. You can
recognize this case if the message indicates
a node name of *DEXINPS* from PARMS(DEXOPS).
REFERENCES: Sections 6.4.2, 7.3.1, 7.3.3, and 9.4
+---------+
| DEX0075 |
+---------+
TEXT: NODE NAME: %NODID FROM PARMS(DEXOPS) DOES
NOT MATCH NODE NAME: %DEXNODE IN DEXSUS
01-VAX/VMS REC. DEXPGEN MAY BE REQUIRED.
OPTION VERIFY=NOABORT SPECIFIED IN DEXOPS.
TYPE: Warning
REASON: Cannot determine correct ORGSYSID to assign
to the data because the VAX node name found
in the input data does not agree with node
name information generated for the input
DDname from DEXOPS.
ACTION: Check the VAX node name that is to be mapped
to the ORGSYSID on the OPTIONS statement in
prefix.MICS.PARMS(DEXOPS). Compare to the
node information given in this message.
Determine if discrepancy due to wrong input
file, incorrect DEXOPS specification, or
requirement for DEXPGEN.
If you are using COMMON EXITS in the DEXOPS
parameter, check the logic that assigns
(reads) VAXID in your exit code. You can
recognize this case if the message indicates
a node name of *DEXINPS* from PARMS(DEXOPS).
REFERENCES: Sections 6.4.2, 7.3.1, 7.3.3, and 9.4
+---------+
| DEX0076 |
+---------+
TEXT: TYPE 01 RECORDS READ. RECORDS WILL NOT BE
KEPT.
ORGSYSID= %ORGSYSID IDENTIFIES NODE=
%DEXNODE
SHOW SYSTEM RECORDS TIME= %WRK_DTM1
TYPE: Information
REASON: Provide the SYSID information for each input
file processed from the VMS MONITOR data
source. The record is discarded and
therefore not included in further record
counts.
ACTION: None
REFERENCES: Sections 6.4.2
+---------+
| DEX0077 |
+---------+
TEXT: TYPE 01 RECORD FOUND BEFORE TYPE 00 RECORD.
UNEXPECTED RECORD SEQUENCE. CHECK INPUT
DATA.
TYPE: Error
REASON: Implies that DEXSUS version and maintenance
level and other data found in a header
record header record (type 00) data will not
be available to the CA MICS VAX/VMS
Analyzer. Because record layouts are
unknown for an unrecognized version,
processing is aborted.
ACTION: Ensure that the correct input file has been
provided, and if so, contact CA MICS Product
Support.
REFERENCES: Section 6.4.1
+---------+
| DEX0078 |
+---------+
TEXT: SYSTEM BOOT TIME= %WRK_DTM1
TYPE: Information
REASON: Provide the BOOT TIME information from the
type 13 separator record of each input file
processed from the CA MICS DEXSUS data
source.
ACTION: None
REFERENCES: Section 6.4.5
+---------+
| DEX0079 |
+---------+
TEXT: TYPE 99 RECORD READ. DEXSUS FILE EOF RECORD.
DEXSUS END= %WRK_DTM1
TYPE: Information
REASON: Provide the file trailer information for
each input file processed from the CA MICS
DEXSUS data source. When this record is
encountered, the input format routine writes
a record to the System Status File (DESSYU),
and therefore the record is included in step
record counts.
ACTION: None
REFERENCES: Section 6.4.12
+---------+
| DEX0080 |
+---------+
TEXT: NODE NAME: %DEXTMPNN FROM SYS$NODE DOES NOT
MATCH NODE NAME: %DEXNODE FROM SHOW SYSTEM.
TYPE: Warning
REASON: Conflicting information has been identified
in the DEXSUS type 01 records identifying
the VAX node name. This is the result of a
comparison of the SHOW SYSTEM node name
output field to the F$TRNLNM("NODENAME")
lexical function. The SHOW SYSTEM value
will be assumed unless it is blank.
ACTION: Check the VAX node name that is to be mapped
to the ORGSYSID on the OPTIONS statement in
prefix.MICS.PARMS(DEXOPS). Compare to the
node information given in this message. If
an error situation arises, this message will
be followed by other messages with specific
corrective actions.
REFERENCES: Section 6.4.2
+---------+
| DEX0081 |
+---------+
TEXT: >>>>> DISKACCT OPTION IN EFFECT: %DEXXACT
TYPE: Information
REASON: Provide the DISKACCT setting information in
effect for processing the DESDKU file data
into accounting journal file records. The
value for %DEXXACT should be either DETAIL
or DAYS. This setting originates from the
DEXOPS member or is set by default to DETAIL
if not specified in DEXOPS.
ACTION: None
REFERENCES: Sections 2.2.1 and 7.3.1
+---------+
| DEX0082 |
+---------+
TEXT: >>>>> ERROR: DISKACCT SETTING IS INVALID
TYPE: Error
REASON: Indicates that the value for the DISKACCT
setting was neither DETAIL or DAYS. This
setting originates from the DEXOPS member or
is set by default to DETAIL if not specified
in DEXOPS. Because the intended processing
path is unknown for an unrecognized setting,
and because this will impact the journal
entry recording for DESDKU data, processing
is aborted.
This error should not occur regardless of
the DISKACCT setting in DEXOPS. The message
is issued as a safety check during DEXSUS
processing to ensure that journal data is
written either to DETAIL or DAYS.
ACTION: Check to make sure that DEXPGEN has been run
successfully, and if so, contact CA MICS
Product Support.
REFERENCES: Section 7.3.1
+---------+
| DEX0098 |
+---------+
TEXT: >>>>%PROCESS HAS COMPLETED
TYPE: Information
REASON: Indicate that process has run to completion.
ACTION: None
REFERENCES: None
+---------+
| DEX0099 |
+---------+
TEXT: %LINE
TYPE: Information
REASON: Display a line of parameter input.
ACTION: None
REFERENCES: None
