Appendix A. MESSAGES
This appendix lists the messages generated by the CA MICS
Analyzer Option for VM/CMS. 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, thus making it easier to
see whether or not a job or job step completed as expected.
If the MICSLOG message does not provide enough information,
see this appendix for more information about the message or
the SAS log to help debug the problem.
The format of a MICSLOG message is
hh:mm:ss.hs cccnnnnns ttttttttttttttttttttttttttttttttttt
hh:mm:ss.hs is the time that the message was issued.
cccnnnnns is the message identifier, which consists of
three parts:
ccc three letter component identifier
nnnnn the message number
s the severity identifier, I is an
informational message, W indicates a
warning, and E indicates an error
ttt...ttt is the message text. If the text spans more
than one line, the message identifier is
repeated.
The remainder of this appendix shows the MICSLOG messages
produced for the CA MICS Analyzer Option for VM/CMS. In
addition to the message identifier and text, this section
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.
+----------+
| VMC00001 |
+----------+
TEXT: INPUT: DSN=dataset.name VOL=SER=volser
TYPE: Information
REASON: A new input file was started.
ACTION: None required.
REFERENCES: VMCPGEN
+----------+
| VMC00002 |
+----------+
TEXT: INPUT: SPECIFIED SYSTEM ID: xxxxxxxx IS
MORE THAN 4 CHARACTERS IN LENGTH.
TYPE: Error
REASON: The ORGSYSID specified in SYSID statement is
too long.
ACTION: Correct the ORGSYSID definition in SYSID.
NOTE: This error will occur only if the
SYSID member has not been validated by
BASPGEN.
REFERENCES: VMCPGEN
+----------+
| VMC00003 |
+----------+
TEXT: SPECIFIED CPU MODEL NUMBER: xxxxxx IS MORE
THAN FOUR CHARACTERS IN LENGTH.
TYPE: Error
REASON: The processor model on an OPTIONS or ALTCPU
statement is too long.
ACTION: Correct the processor model in VMCOPS.
REFERENCES: VMCPGEN
+----------+
| VMC00004 |
+----------+
TEXT: SPECIFIED CPU MODEL NUMBER: xxxxxx IS NOT
NUMERIC.
TYPE: Error
REASON: The processor model on an OPTIONS or ALTCPU
statement contains a non-numeric character.
ACTION: Correct the processor model in VMCOPS.
REFERENCES: VMCPGEN
+----------+
| VMC00005 |
+----------+
TEXT: SCP FOR orgsysid IS NOT A VM SYSTEM.
TYPE: Warning
REASON: The SCP definition for an ORGSYSID specified
in SYSID is not identified as a VM system.
This is determined by comparing the first two
characters of the SCP definition with the
characters 'VM'.
ACTION: None required. This is a consistency check
only.
REFERENCES: VMCPGEN
+----------+
| VMC00006 |
+----------+
TEXT: SYSID AND VMCOPS CPU MODEL FOR orgsysid DO
NOT MATCH.
TYPE: Warning
REASON: The CPU model specified in SYSID and the CPU
model specified in VMCOPS for the ORGSYSID
are not the same.
ACTION: None required. This is a consistency check
only. If your site uses the MIPS values
specified in SYSID, this message may
indicate an out-of-date value for MIPS.
REFERENCES: VMCPGEN
+----------+
| VMC00007 |
+----------+
TEXT: MORE THAN ONE OPTIONS STATEMENT FOR ORGSYSID
xxxx FOUND IN VMCOPS.
TYPE: Error
REASON: Only one OPTIONS statement per ORGSYSID is
allowed.
ACTION: Delete the extra OPTIONS statement or change
it to ALTCPU.
REFERENCES: VMCPGEN
+----------+
| VMC00009 |
+----------+
TEXT: AN OBSOLETE KEYWORD HAS BEEN SPECIFIED. IT
WILL BE IGNORED. TO PERFORM SCHEDULER DATA
SELECTION, CODE MACRO USRSSCH IN
prefix.USER.MICS.SOURCE(#VMCEXIT).
TYPE: Warning
REASON: More than three parameters were found on an
OPTIONS statement.
ACTION: None required. Delete the extra parameters
to prevent the message. If your site is
using SCHEDULE class data, review the USRSSCH
macro.
REFERENCES: VMCPGEN
+----------+
| VMC00010 |
+----------+
TEXT: ORIGINAL SYSID: xxxx HAS BEEN PREVIOUSLY
DEFINED.
TYPE: Error
REASON: An ORGSYSID was detected more than once in
SYSID.
ACTION: Correct SYSID.
NOTE: This error should not occur if SYSID
has been validated by BASPGEN.
REFERENCES: VMCPGEN
+----------+
| VMC00011 |
+----------+
TEXT: THE MAXIMUM SYSID LIMIT HAS BEEN REACHED.
CONTACT CA MICS PRODUCT SUPPORT GROUP.
TYPE: Error
REASON: More than 50 ORGSYSIDs have been defined in
SYSID.
ACTION: Delete extraneous systems from SYSID. If
your site needs 50 or more ORGSYSIDs, contact
Technical Support at http://ca.com/support
for assistance.
REFERENCES: VMCPGEN
+----------+
| VMC00012 |
+----------+
TEXT: SPECIFIED DDNAME: xxxxxxxx IS MORE THAN
EIGHT CHARACTERS IN LENGTH.
TYPE: Error
REASON: A DDNAME specification on a MONITOR, ACCOUNT,
or COMMON statement is too long.
ACTION: Correct the DDNAME specification.
REFERENCES: VMCPGEN
+----------+
| VMC00013 |
+----------+
TEXT: THIS ORIGINAL SYSID: xxxx AND DATA SOURCE
xxxxxxxx HAVE ALREADY BEEN DEFINED.
TYPE: Error
REASON: An ACCOUNT or MONITOR statement for the
ORGSYSID has been found more than once in
VMCOPS.
ACTION: Delete the extraneous statement.
REFERENCES: VMCPGEN
+----------+
| VMC00014 |
+----------+
TEXT: SPECIFIED ORIGINAL SYSID: xxxx HAS NOT BEEN
DEFINED ON A PREVIOUS OPTIONS STATEMENT.
TYPE: Error
REASON: The OPTIONS statement for an ORGSYSID must
precede the ACCOUNT and/or MONITOR statement
for the ORGSYSID.
ACTION: Add or move the OPTIONS statement into the
correct position in VMCOPS.
REFERENCES: VMCPGEN
+----------+
| VMC00015 |
+----------+
TEXT: SUBPARAMETER: xxxxxxxx IS NOT VALID ON A
xxxxxxxx STATEMENT.
TYPE: Error
REASON: An invalid parameter was found on a statement
in VMCOPS.
ACTION: Correct the specified statement and
parameter.
REFERENCES: VMCPGEN
+----------+
| VMC00016 |
+----------+
TEXT: KEYWORD: xxxxxxxx IS NOT RECOGNIZED.
TYPE: Error
REASON: An invalid statement was found in VMCOPS.
ACTION: Correct or delete the specified statement.
REFERENCES: VMCPGEN
+----------+
| VMC00017 |
+----------+
TEXT: END OF MEMBER xxxxxxxx INPUT.
TYPE: Information
REASON: End-of-file was reached on an input file.
ACTION: None required.
REFERENCES: VMCPGEN
+----------+
| VMC00018 |
+----------+
TEXT: REQUIRED STATEMENT MISSING: xxxxxxxx
TYPE: Error
REASON: A parameter statement required in VMCOPS was
not found.
ACTION: Add the required statement.
REFERENCES: VMCPGEN
+----------+
| VMC00019 |
+----------+
TEXT: ERROR(S) ENCOUNTERED IN VM UNIT PARAMETER
DEFINITIONS, MACRO GENERATION ABORTED.
CORRECT THE ERRORS AND RE-EXECUTE VMCPGEN.
TYPE: Error
REASON: Errors were found during VMCOPS parameter
analysis.
ACTION: Correct the previously flagged errors and
resubmit VMCPGEN.
REFERENCES: VMCPGEN
+----------+
| VMC00020 |
+----------+
TEXT: DUPLICATE DDNAMES NOT ALLOWED: ddname
TYPE: Error
REASON: A DDNAME entered on the current statement was
used on a previous statement,
ACTION: Change the DDNAME specification.
REFERENCES: VMCPGEN
+----------+
| VMC00021 |
+----------+
TEXT: COMMON INPUT DD NOT ALLOWED FOR: datatype
TYPE: Error
REASON: An asterisk ('*') was coded as the DDNAME on
the parameter statement.
ACTION: Change the DDNAME to an explicit
specification.
REFERENCES: VMCPGEN
+----------+
| VMC00022 |
+----------+
TEXT: COMMON INPUT DD FOR datatype HAS ALREADY BEEN
DEFINED.
TYPE: Error
REASON: A COMMON statement for the named data source
has already been read.
ACTION: Delete the extraneous statement.
REFERENCES: VMCPGEN
+----------+
| VMC00023 |
+----------+
TEXT: MEMBER member IS EMPTY OR CONTAINS NO DD
STATEMENTS.
TYPE: Error
REASON: An input member was found to contain no
parameters. In the case of INPUTVMC, no DD
statements were found.
ACTION: Create or correct the member indicated.
REFERENCES: VMCPGEN
+----------+
| VMC00024 |
+----------+
TEXT: DDNAME ddname NOT FOUND IN INPUTVMC.
TYPE: Error
REASON: A DDNAME specified on an ACCOUNT, MONITOR, or
COMMON statement in VMCOPS was not found on a
DD statement in INPUTVMC.
ACTION: Correct or create INPUTVMC.
REFERENCES: VMCPGEN
+----------+
| VMC00025 |
+----------+
TEXT: INPUTVMC DDNAME ddname NOT REFERENCED IN
VMCOPS.
TYPE: Warning
REASON: A DDNAME specified in INPUTVMC was not
referred to in VMCOPS.
ACTION: None required. This is a consistency check
only.
REFERENCES: VMCPGEN
+----------+
| VMC00026 |
+----------+
TEXT: WORK FILE SPECIFICATION: nnn IS NOT IN THE
RANGE: 0<nnn<=max
TYPE: Error
REASON: The number of work data sets specified on the
WORK statement was greater than the allowable
maximum.
ACTION: Correct the WORK statement.
REFERENCES: VMCPGEN
+----------+
| VMC00027 |
+----------+
TEXT: EXCEPTION SUMMARIZATION SUPPORT IS NOT
AVAILABLE FOR FILE iiifff
TYPE: Error
REASON: The DSUM member for the specified file is not
defined in the sharedprefix.MICS.SOURCE.
ACTION: Create the DSUM member #fffDSUM
REFERENCES: VMCPGEN
+----------+
| VMC00028 |
+----------+
TEXT: INVALID DATA IN SPIN STATEMENT: fff
TYPE: Error
REASON: The specified file is not recognized as a
SPIN file.
ACTION: Correct the filename in the SPIN statement.
REFERENCES: VMCPGEN
+----------+
| VMC00029 |
+----------+
TEXT: INPUTVMC DDNAME: ddname IS MORE THAN EIGHT
CHARACTERS IN LENGTH
TYPE: Error
REASON: A DDNAME specified in INPUTVMC is too long.
ACTION: Correct the DDNAME in INPUTVMC.
REFERENCES: VMCPGEN
+----------+
| VMC00030 |
+----------+
TEXT: LESS THAN n PARAMETERS SPECIFIED AT xxxxxxxx
STATEMENT
TYPE: Error
REASON: The specified statement in VMCOPS requires at
least n parameters.
ACTION: Correct the statement in VMCOPS.
REFERENCES: VMCPGEN
+----------+
| VMC00031 |
+----------+
TEXT: ORGSYSID orgsysid IS NOT DEFINED IN
PARMS(SYSID)
TYPE: Error
REASON: The specified ORGSYSID is not found in
PARMS(SYSID).
ACTION: Create the ORGSYSID indicated in PARMS(SYSID)
or correct VMCOPS.
REFERENCES: VMCPGEN
+----------+
| VMC00032 |
+----------+
TEXT: SPECIFIED CPU SERIAL NUMBER: xxxxxx IS MORE
THAN SIX CHARACTERS IN LENGTH
TYPE: Error
REASON: The specified CPU serial number on an OPTIONS
or ALTCPU statement is too long.
ACTION: Change the CPU serial number in
prefix.MICS.PARMS(VMCOPS).
REFERENCES: VMCPGEN
+----------+
| VMC00033 |
+----------+
TEXT: SPECIFIED CPU SERIAL NUMBER: xxxxxx IS NOT
HEXADECIMAL.
TYPE: Error
REASON: The CPU serial number on an OPTIONS or ALTCPU
statement contains a non-hexadecimal
character.
ACTION: Correct the CPU serial number in VMCOPS.
REFERENCES: VMCPGEN
+----------+
| VMC00050 |
+----------+
TEXT: INTERNAL ERROR: RETURN TO TOP OF DATA STEP
OCCURRED DURING datatype INPUT. REPORT THIS
ERROR TO CA MICS PRODUCT SUPPORT GROUP.
TYPE: Error
REASON: A condition that caused _N_ to exceed the
value 1 occurred.
ACTION: Contact Technical Support at
http://ca.com/support with the dump
information provided in the DAY080 listing.
REFERENCES: DAY080
+----------+
| VMC00051 |
+----------+
TEXT: VM datatype RECORDS READ FROM DD: ddname
TYPE: Information
REASON: An end-of-file condition was encountered.
ACTION: None required.
REFERENCES: DAY080
+----------+
| VMC00052 |
+----------+
TEXT: record type : count
TYPE: Information
REASON: This message accompanies VMC00051. It
contains input counts by record type.
ACTION: None required.
REFERENCES: DAY080
+----------+
| VMC00053 |
+----------+
TEXT: orgsysid: UNKNOWN RECORD TYPE ENCOUNTERED:
datatype: record type
TYPE: Information
REASON: An input record not recognized by VMC was
read.
ACTION: None required. A summary message is produced
at the end of data step.
REFERENCES: DAY080
+----------+
| VMC00054 |
+----------+
TEXT: orgsysid: DATA SET: ddname = dataset.name
TYPE: Information
REASON: A change in input data set occurred.
ACTION: None required.
REFERENCES: DAY080
+----------+
| VMC00056 |
+----------+
TEXT: orgsysid: SHORT RECORD FROM ddname dsname :
RECORD NUMBER nnnn, TYPE xxxx,
LENGTH nn
TYPE: Warning
REASON: An input record was shorter that expected.
ACTION: Verify that the input data is correct. This
may indicate a problem in VM.
REFERENCES: DAY080
+----------+
| VMC00058 |
+----------+
TEXT: CPU MODEL SPECIFIED IN PARMS(VMCOPS) DOES NOT
MATCH CPU MODEL IN MONITOR HEADER. OPTION
VERIFY=ABORT SPECIFIED IN VMCOPS.
TYPE: Error
REASON: The VM Monitor header record contains a CPU
identifier different from that specified in
VMCOPS for this ORGSYSID.
ACTION: Verify that the correct data is provided in
the DDNAME indicated in message VMC00054.
Correct VMCOPS and submit VMCPGEN if
necessary. ABEND U997 accompanies this
message.
REFERENCES: DAY080
+----------+
| VMC00059 |
+----------+
TEXT: CPU MODEL SPECIFIED IN PARMS(VMCOPS) DOES NOT
MATCH CPU MODEL IN MONITOR HEADER. OPTION
VERIFY=NOABORT SPECIFIED IN VMCOPS.
TYPE: Error
REASON: The VM Monitor header record contains a CPU
identifier different from that specified in
VMCOPS for this ORGSYSID.
ACTION: Verify that the correct data is provided in
the DDNAME indicated in message VMC00054.
Correct VMCOPS and submit VMCPGEN if
necessary. Processing continues.
REFERENCES: DAY080
+----------+
| VMC00060 |
+----------+
TEXT: CURRENT DATE: date/time RUN_DT FROM
CHECKPOINT ROUTINE: date/time
TYPE: Information
REASON: To provide consistency verification status.
ACTION: None required.
REFERENCES: DAY080
+----------+
| VMC00063 |
+----------+
TEXT: orgsysid: DOMAIN 1 RECORD 9 CONFIGURATION
RECORD MISSING!
TYPE: Error
REASON: Domain 1 Record 9 configuration record is not
found in the input monitor data because of
one of the following:
o The size of configuration area in the
monitor saved segment is not large enough
to store configuration records.
o Record is dropped from the ESAWRITE extract
to CA MICS if using Velocity Software'S
ESAWRITE utility.
o Record is dropped during record selection
in the VMT Transfer program.
o A monitor suspend event occurred. MICSLOG
will display warning message VMC00314W.
o You are using user exit %USRSEL to drop
monitor records, and this monitor record is
being dropped.
ACTION: Take the following action depending on the
reason:
o Notify the VM systems programmer to check
size of the configuration area in the
monitor saved segment. To ensure the
configuration area is large enough to store
all configuration records, it is
recommended to allocate the configuration
area 30% larger than required.
o Review the record selection criteria for
the ESAWRITE extract file to CA MICS if you
are using Velocity Software to ensure the
Domain 1 Record 9 is being written and not
excluded.
o See Section 7.2.3 of the VMT Transfer
Program guide, review record selection, and
check to see if 01/09 is excluded.
o See explanation of message VMC00314W.
o Check code in %USRSEL to ensure you are not
dropping these records.
Contact Technical Support at
http://ca.com/support with the information
provided in the MICSLOG.
We recommend that you do not take any of the
following actions to override the U997 abend
before the problem is diagnosed.
1. Remove the input data set from the
offending VM system in the DAY080 step JCL
and rerun. Substitute DD DUMMY on the
DDNAME of the data set you want to remove.
See MICSLOG VMC00054I that displays the
DDNAME in the DAY080 MICSLOG. Be sure you
remove the DD DUMMY from the DAY080 step
JCL after DAY080 completes.
2. Add the SYSPARM 'NODATA NOD1R9' override
to the EXEC DAY080 SYSPARM= JCL card and
rerun.
CAUTION! Use of this override should be
restricted. Be aware that use of this
override will have full database impact
with missing observations and invalid data
values if you allow the data to process.
MICSLOG message VMC00064I will be
displayed when the rerun is complete. Be
sure you remove the 'NODATA NOD1R9' from
the SYSPARM parameter after DAY080
completes.
REFERENCES: DAY080
+----------+
| VMC00064 |
+----------+
TEXT: PROCESSING CONTINUES DUE TO SYSPARM='NODATA
NOD1R9' IS SPECIFIED
TYPE: Information
REASON: U997 abend is overridden when the monitor
sample record (Domain 1 Record 9) is missing
in the monitor input data. This message
follows VMC00063 if NOD1R9 is specified in
the SYSPARM parameter.
ACTION: Use of NOD1R9 should be restricted. We
recommend removal of NOD1R9 from SYSPARM
immediately after a DAILY run. If left for
an indefinite period of time, dropped
observations from some database files and
invalid data element values could go
undetected.
REFERENCES: DAY080
+----------+
| VMC00065 |
+----------+
TEXT: DD STATEMENT: ddname IS EMPTY.
TYPE: Warning
REASON: The input data set referenced by the
indicated DDNAME was found to contain no
data.
ACTION: Verify that this condition is expected.
REFERENCES: DAY080
+----------+
| VMC00066 |
+----------+
TEXT: orgsysid: LONG RECORD FROM: ddname dsname :
RECORD NUMBER xxxx, TYPE x/xx, LENGTH
xxx
TYPE: Warning
REASON: The length of the input record indicated is
longer than expected.
ACTION: This may indicate new fields added to the
record. Contact Technical Support at
http://ca.com/support with the information
provided in the listing.
REFERENCES: DAY080
+----------+
| VMC00067 |
+----------+
TEXT: sysid: CONFIGURATION RECORD FOR PROCESSOR xx
IS MISSING!
TYPE: Error
REASON: The configuration record (Domain 1 Record 5)
for the processor specified is missing in the
input monitor data because of one of the
following:
o A processor was VARIED online during
monitoring. MONITOR EVENT PROCESSOR was set
to DISABLE in the monitor profile for event
data collection.
o The size of configuration area in the
monitor saved segment is not large enough
to store configuration records.
o Record is dropped from the ESAWRITE extract
to CA MICS if using Velocity Software'S
ESAWRITE utility.
o Record is dropped during record selection
in the VMT Transfer program.
o A monitor suspend event occurred. MICSLOG
will display warning message VMC00314W.
o You are using user exit %USRSEL to drop
monitor records, and this monitor record is
being dropped.
ACTION: Take the following action depending on the
reason:
o Notify the VM systems programmer to check
if the monitor event profile for event data
collection of the offending VM system is
disabled. "MONITOR EVENT DISABLE
PROCESSOR"
o Notify the VM systems programmer to check
size of the configuration area in the
monitor saved segment. To ensure the
configuration area is large enough to store
all configuration records, it is
recommended to allocate the configuration
area 30% larger than required.
o Review the record selection criteria for
the ESAWRITE extract file to CA MICS if you
are using Velocity Software to ensure the
Domain 1 Record 5 is being written and not
excluded.
o See Section 7.2.3 of the VMT Transfer
Program guide, review record selection, and
check to see if 01/05 is excluded.
o See explanation of message VMC00314W.
o Check code in %USRSEL to ensure you are not
dropping these records.
Contact Technical Support at
http://ca.com/support with the information
provided in the listing and the record dump
in the SASLOG.
We recommend that you not code NOXACFG in the
SYSPARM to override the U997 abend before the
problem is diagnosed.
REFERENCES: DAY080
+----------+
| VMC00068 |
+----------+
TEXT: PROCESSING CONTINUES DUE TO SYSPARM=NOXACFG
SPECIFIED
TYPE: Information
REASON: U997 abend is overridden when the
configuration record of a processor is
missing in the VM Monitor data. This message
follows VMC00067 if NOXACFG is specified in
the SYSPARM parameter.
ACTION: Use of NOXACFG should be restricted to those
times when it is absolutely essential. We
recommend removal of NOXACFG from SYSPARM
immediately after a DAILY run. If left for
an indefinite period of time, it is
conceivable that some problems could go
undetected.
REFERENCES: DAY080
+----------+
| VMC00069 |
+----------+
TEXT: sysid: SYSTEM CONFIGURATION RECORD IS
MISSING!
TYPE: Error
REASON: The system configuration record (Domain 1,
Record 4) for the SYSID indicated is missing
in the VM Monitor data.
REASON: Domain 1 Record 4 configuration is not found
in the input monitor data because of one of
the following:
o The size of configuration area in the
monitor saved segment is not large enough
to store configuration records.
o Record is dropped from the ESAWRITE extract
to CA MICS if using Velocity Software'S
ESAWRITE utility.
o Record is dropped during record selection
in the VMT Transfer program.
o A monitor suspend event occurred. MICSLOG
will display warning message VMC00314W.
o You are using user exit %USRSEL to drop
monitor records, and this monitor record is
being dropped.
ACTION: Take the following action depending on the
reason:
o Notify the VM systems programmer to check
size of the configuration area in the
monitor saved segment. To ensure the
configuration area is large enough to store
all configuration records, it is
recommended to allocate the configuration
area 30% larger than required.
o Review the record selection criteria for
the ESAWRITE extract file to CA MICS if you
are using Velocity Software to ensure the
Domain 1 Record 4 is being written and not
excluded.
o See Section 7.2.3 of the VMT Transfer
Program guide, review record selection, and
check to see if 01/04 is excluded.
o See explanation of message VMC00314W.
o Check code in %USRSEL to ensure you are not
dropping these records.
Contact Technical Support at
http://ca.com/support with the information
provided in the listing and the record dump
in the SASLOG.
REFERENCES: DAY080
+----------+
| VMC00070 |
+----------+
TEXT: CPU MODEL IN MONITOR HEADER DOES NOT MATCH
ANY CPU MODELS IN PARMS(VMCOPS) FOR SYSTEMS
FROM COMMON DD: ddname
TYPE: Error
REASON: The VM Monitor header record read from the
DDNAME indicated contains a CPU identifier
different from any systems that are specified
in VMCOPS for this COMMON DDNAME.
ACTION: Verify that correct data is provided in the
DDNAME indicated. Correct VMCOPS if
necessary. Abend 310 accompanies this
message.
REFERENCES: DAY080
+----------+
| VMC00071 |
+----------+
TEXT: INVALID NETWORK DEVICE TYPE ENCOUNTERED IN
TYPE 0C RECORD. NETWORK DEVICE TYPE HEX
VALUE =%NETTYPE. THIS MESSAGE WILL ONLY BE
WRITTEN A MAXIMUM OF FIVE TIMES.
TYPE: Warning
REASON: The CP accounting record Type 0C encountered
an invalid device type.
ACTION: Value must be either x'00', x'01', or x'02'.
Advise your VM systems programmer of the
invalid network types in the type 0C account
record.
Records will be not be processed.
REFERENCES: DAY080
+----------+
| VMC00098 |
+----------+
TEXT: >>> process HAS COMPLETED.
TYPE: Information
REASON: A process in a VMC job has completed.
ACTION: None required.
REFERENCES: DAY080
+----------+
| VMC00099 |
+----------+
TEXT: free form text
TYPE: Information
REASON: An input record from a parameter file is
being echoed to the log file. This message
may be used to provide diagnostic
information.
ACTION: None required.
REFERENCES: May be used by any program.
+----------+
| VMC00200 |
+----------+
TEXT: VM EXCEPTIONS REPORTED FROM dbfile: count
TYPE: Information
REASON: Status on number of exceptions found in the
named VMC database file.
ACTION: None required.
REFERENCES: DYVMCEXC
+----------+
| VMC00250 |
+----------+
TEXT: FILE xxx IS NOT TURNED ON IN tttttt TIMESPAN
FOR MBO REPORTING
NO REPORTS FROM THE FILE xxx WILL BE PRODUCED
TYPE: Warning
REASON: To produce MBO reports from the file xxx
requires that the file be turned on in the
timespan requested for reporting.
ACTION: Turn on the file in VMCGENIN if MBO reports
from the specified file are needed. Then run
VMCCGEN. Otherwise, ignore the message.
REFERENCES: DYVMCMBO, MNVMCMBO, WKVMCMBO
+----------+
| VMC00300 |
+----------+
TEXT: MONITOR INITIALIZATION DATA DOES NOT OCCUR AT
THE BEGINNING OF INPUT FOR SYSTEM sysid.
THIS DATA IS REQUIRED FOR CORRECT PROCESSING
OF VM MONITOR FILES. FIRST INPUT RECORD:
record type
TYPE: Error
REASON: Domain 1 Record 1 Event Profile configuration
record is not found at the beginning of the
input monitor data because of one of the
following:
o The input monitor may have not been
processed by the VM Data Transfer Program.
Record format is invalid for CA MICS to
process.
o The size of configuration area in the
monitor saved segment is not large enough
to store configuration records.
o Record is dropped from the ESAWRITE extract
to CA MICS if using Velocity Software'S
ESAWRITE utility.
o Record is dropped during record selection
in the VMT Transfer program.
o A monitor suspend event occurred. MICSLOG
will display warning message VMC00314W.
o You are using user exit %USRSEL to drop
monitor records, and this monitor record is
being dropped.
ACTION: Take the following action depending on the
reason:
o Check the format of the monitor file from
the offending VM (ISPF 3.4 then I) system.
If the format is FB and not V or VB the
data is invalid. Run the VMT Transfer
program and send the file again.
o Notify the VM systems programmer to check
size of the configuration area in the
monitor saved segment. To ensure the
configuration area is large enough to store
all configuration records, it is
recommended to allocate the configuration
area 30% larger than required.
o Review the record selection criteria for
the ESAWRITE extract file to CA MICS if you
are using Velocity Software to ensure the
Domain 1 Record 1 is being written and not
excluded.
o See Section 7.2.3 of the VMT Transfer
Program guide, review record selection, and
check to see if 01/04 is excluded.
o See explanation of message VMC00314W.
o Check code in %USRSEL to ensure you are not
dropping these records.
REFERENCES: VMCMXA
+----------+
| VMC00301 |
+----------+
TEXT: VM MONITOR INITIALIZATION
AT: time
SYSTEM : orgsysid
SYSTEM LEVEL: VvvRrMm SERVICE LEVEL: nnnn
TYPE: Information
REASON: Monitor configuration data has been read.
ACTION: None required.
REFERENCES: VMCMXA
+----------+
| VMC00302 |
+----------+
TEXT: CPU : serial# model#
TYPE: Information
REASON: A processor configuration record has been
read.
ACTION: None required.
REFERENCES: VMCMXA
+----------+
| VMC00303 |
+----------+
TEXT: DOMAINS ENABLED:
EVENT : domain list
SAMPLE : domain list
H.F. : domain list
TYPE: Information
REASON: Monitor configuration data has been read.
ACTION: None required.
REFERENCES: VMCMXA
+----------+
| VMC00304 |
+----------+
TEXT: CURRENT INPUT DATA SET DOES NOT START WITH
INITIALIZATION DATA
FIRST INPUT RECORD: record type
ORGSYSID: orgsysid IS ASSUMED
TYPE: Warning
REASON: The input data set containing VM Monitor data
does not have monitor initialization (Domain
1 Record 1) information in the first record.
The first data set for the specified system
does contain initialization data, but the
current data set does not. The data set of
missing initialization data is assumed for
the specified system. This can happen
because:
o The input monitor may have not been
processed by the VM Data Transfer Program.
Record format is invalid for CA MICS to
process.
o The size of configuration area in the
monitor saved segment is not large enough
to store configuration records.
o Record is dropped from the ESAWRITE extract
to CA MICS if using Velocity Software'S
ESAWRITE utility.
o Record is dropped during record selection
in the VMT Transfer program.
o A monitor suspend event occurred. MICSLOG
will display warning message VMC00314W.
o You are using user exit %USRSEL to drop
monitor records, and this monitor record is
being dropped.
ACTION: Take the following action depending on the
reason:
o Check the format of the monitor file from
the offending VM (ISPF 3.4 then I) system.
If the format is FB and not V or VB the
data is invalid. Run the VMT Transfer
program and send the file again.
o Notify the VM systems programmer to check
size of the configuration area in the
monitor saved segment. To ensure the
configuration area is large enough to store
all configuration records, it is
recommended to allocate the configuration
area 30% larger than required.
o Review the record selection criteria for
the ESAWRITE extract file to CA MICS if you
are using Velocity Software to ensure the
Domain 1 Record 1 is being written and not
excluded.
o See Section 7.2.3 of the VMT Transfer
Program guide, review record selection, and
check to see if 01/04 is excluded.
o See explanation of message VMC00314W.
o Check code in %USRSEL to ensure you are not
dropping these records.
REFERENCES: VMCMXA
+----------+
| VMC00305 |
+----------+
TEXT: UNRECOGNIZED VM SYSTEM LEVEL: PRODUCT BIT
MAP = xxxxxxxxxxxxxxxx. CONTACT MICS
PRODUCT SUPPORT GROUP.
TYPE: Warning
REASON: The program product bit map in the monitor
configuration record indicates that the VM
system's release level is not recognized as
belonging to any known VM system. This may
be caused by a transmission error that
occurred on the network or by processing
data from an unsupported VM system.
ACTION: Contact Technical Support at
http://ca.com/support with the message text.
REFERENCES: VMCMXA
+----------+
| VMC00306 |
+----------+
TEXT: UNRECOGNIZED CPU MODEL VERSION CODE: xxxx
for CPU MODEL nnnn
TYPE: Warning
REASON: The CPU model version code in the monitor
configuration record is not recognized as
belonging to the specific CPU model in the
message text. This may be caused by
processing data from a new CPU model version
or from a new CPU model that is not currently
supported.
ACTION: Contact Technical Support at
http://ca.com/support with the message text.
REFERENCES: VMCMXA
+----------+
| VMC00310 |
+----------+
TEXT: UNRECOGNIZED CONTROLLER: type AT ADDRESS:
nnnn
TYPE: Information
REASON: A domain 6, type 4 record was read for a
cache controller that is not recognized by
the CA MICS Analyzer Option for VM/CMS.
ACTION None required. Contact Technical Support at
http://ca.com/support for assistance.
REFERENCES: VMCMXA, step CACHE
+----------+
| VMC00311 |
+----------+
TEXT: UNRECOGNIZED CP AREA TYPE: type
TYPE: Information
REASON: A domain 1, type 8 or domain 3, type 7 record
was read that referenced a CP volume area
that is not recognized by CA MICS.
ACTION None required. Contact Technical Support at
http://ca.com/support for assistance.
REFERENCES: VMCMXA, step ACF1.
+----------+
| VMC00312 |
+----------+
TEXT: RECORD TYPE 4/03 IS NOT FOLLOWED BY RECORD
TYPE 4/04 FOR USERID: user
TYPE: Warning
REASON: A domain 4, type 3 record for the specified
user is not followed by a domain 4, type 4
record for the same userid in the VM Monitor
data. This may be caused by the data being
truncated due to lack of monitor sample
segment space to store all the sample data
for a given interval.
ACTION: Check the exception file (VMCVXC) for
occurrences of EXC08064. If there are any,
advise your VM systems programmer to increase
the monitor saved segment space.
REFERENCES: VMCMXA
+----------+
| VMC00313 |
+----------+
TEXT: orgsysid: sample/event DATA TRUNCATION
OCCURRED AT time DUE TO INSUFFICIENT MONITOR
SEGMENT SPACE
TYPE: Warning
REASON: This exception is detected when the target
message type of the IUCV parameter list in
the VM Monitor control record contains an
indicator of insufficient space in the
monitor saved segment.
ACTION: Advise the VM systems programmer of the need
to increase the monitor saved segment space.
REFERENCES: VMCMXA
+----------+
| VMC00314 |
+----------+
TEXT: orgsysid: MONITOR EVENT DATA SUSPENSION
STARTED FROM date/time TO date/time
RECORD LOST: count
TYPE: Warning
REASON: A VM Monitor domain 1 type 03 record was
read. Receipt of this message indicates the
loss of event data due to monitor suspension.
Monitoring is suspended either because the
event portion of the monitor saved segment is
full or the IUCV path to the receiving
virtual machine has been quiesced.
ACTION: Notify the VM systems programmer of this
message. This may indicate a requirement to
increase the event portion of monitor saved
segment size. Another reason is MONWRITE or
if using Velocity Software, ESAWRITE may have
been in a race condition and missed the IUCV
interrupt when the MONITOR signaled data was
ready to write.
If the DAY080 update step abends with U997
error message VMC00067E refer to Section
6.2.4 to avoid interruption to your DAILY
processing.
REFERENCES: VMCMXA
+----------+
| VMC00400 |
+----------+
TEXT: UNKNOWN VELOCITY SOFTWARE ESALPS RELEASE
%CASUPREL ENCOUNTERED IN DOMAIN C RECORDS.
COUNT RECORDS REJECTED.
ORGSYSID: %ORGSYSID
HIGHEST ESALPS RELEASE KNOWN TO CA MICS:
%CASUPLVL
CONTACT CA MICS SUPPORT
TYPE: Warning
REASON: Domain C records from an unsupported CA
release of Velocity Software ESALPS product
have been encountered and skipped.
ACTION: Contact Technical Support at
http://ca.com/support and inform them of the
release value that was encountered in the
Domain C records.
REFERENCES: None
