Appendix A: MESSAGES › Messages
Messages
This appendix lists all messages generated by the CA MICS
Performance Manager Option. Most messages are caused by
various conditions in the data. The messages are listed in
ascending numerical sequence and include the full text of the
message, the type, the reason for the message, the action you
should take, and applicable document references.
Four type codes are used to categorize the messages:
l. Information: A note that documents a CA MICS Performance
Manager Option or potentially important
feature in the data.
2. Warning: A condition of either the data or the
inquiry options that does not affect the
operation of the CA MICS Performance
Manager Option, but that can lead to
unexpected results.
3. Error: An indication that a problem has been
encountered with an inquiry option that
will prevent a successful run of the
product. Execution is stopped after all
inquiry options have been processed.
4. Termination: An indication that a critical problem has
been encountered with the data that
requires the product to terminate
processing immediately.
The message texts often include references to information
contained in an inquiry option or values of variables. In
these cases, the message text contains a string in double
quotes indicating that a value will be substituted into the
text at execution time.
+-----------------+
| P E R 0 0 1 2 1 |
+-----------------+
TEXT: CPU SERVICE FACTOR IS NOT DEFINED FOR:
PRSMCEC: "prsmcec"
SYSPLEX: "sysplex"
SYSID: "sysid"
CPU MODEL:"cpu model"
NUMBER OF PROCESSORS:"number"
PLEASE UPDATE THE MSU CONVERSION TABLE.
TYPE: Warning
REASON: The CPU service factor for the CPU model from
which the HARCPU data originated is not
available.
ACTION: None required.
REFERENCES: Section 2.1.5, Requirements
+-----------------+
| P E R 0 1 1 4 9 |
+-----------------+
TEXT: "number" OBSERVATIONS WERE DELETED DUE TO
MISSING VALUES.
TYPE: Information
REASON: The identified number of observations were
deleted from the analysis due to the
specifications from the control panel.
ACTION: None required.
REFERENCES: Section 3.3, Data Clustering Analysis
+-----------------+
| P E R 0 1 1 5 0 |
+-----------------+
TEXT: NO OBSERVATIONS MET SELECTION CRITERIA.
EXECUTION TERMINATES.
TYPE: Termination
REASON: The selection criteria defined via the control
panel resulted in no observations being selected
for analysis.
ACTION: Examine the selection criteria specified on the
control panel, as well as the input data.
Modify the selection criteria or select from a
different CA MICS data source and resubmit.
REFERENCES: Section 3.3, Data Clustering Analysis
+-----------------+
| P E R 0 1 1 5 1 |
+-----------------+
TEXT: NUMBER OF CLUSTERS GENERATED EXCEEDS 99 - USE
FEWER VARIABLES FOR CLUSTERING.
TYPE: Error
REASON: The variables specified for the analysis based
on options on the inquiry panel resulted in more
than the maximum of 99 clusters being generated.
ACTION: Specify a fewer number of variables and
resubmit.
REFERENCES: Section 3.3, Data Clustering Analysis
+-----------------+
| P E R 0 2 0 0 1 |
+-----------------+
TEXT: NO DATA HAS PASSED THROUGH INITIAL SELECTION.
CHECK FILE AND SELECTION CRITERIA VALIDITY. RUN
TERMINATES WITH A USER 998 CONDITION CODE.
TYPE: Error
REASON: All data from the requested input files was
either rejected by selection specifications, or
the required files contained no observations
to select.
ACTION: Run terminates with a user 998 abend. Verify the
contents of the required files, alter selection,
input specifications, or both as required, and
resubmit.
REFERENCES: None
+-----------------+
| P E R 0 2 0 0 2 |
+-----------------+
TEXT: THE WEEKS LEVEL HARDVA FILE IS NOT SEQUENCED BY
HOUR. HARDVA RELATED MEASUREMENTS ARE
UNAVAILABLE. RESPONSE TIME CANNOT BE REPORTED
ON.
TYPE: Information
REASON: ASM inquiries at the WEEKS timespan, with
by-the-hour reporting specified, cannot obtain
HARDVA information by the hour, because the
HARDVA File in the WEEKS timespan is not
sequenced by hour.
ACTION: The report-by-hour is still produced, but all
report elements obtained from the HARDVA File
are set to missing values. You can run the
report without the by-hour option to generate a
report with no missing values.
REFERENCES: Section 2.3, Auxiliary Storage Management
Analysis
+-----------------+
| P E R 0 2 0 0 3 |
+-----------------+
TEXT: MORE THAN NINE DOMAINS FOUND IN INPUT. FIRST
NINE DOMAINS WILL BE PLOTTED.
TYPE: Warning
REASON: The inquiry routines allow up to nine domains to
be plotted on a single page, but more than nine
domains have been found in the input data. Only
the first nine domains appear.
ACTION: Use the selection options on the inquiry panel
to limit the number of selected domains to nine.
REFERENCES: None
+-----------------+
| P E R 0 2 0 0 4 |
+-----------------+
TEXT: NO VALID TRACE DATA FOUND, PLOTS CANNOT BE
PRODUCED. REPORT ELEMENTS DERIVED FROM TRACE
DATA ARE UNAVAILABLE.
TYPE: Warning
REASON: No RMF Trace data (CA MICS SCPTRC File) was
found. Without this data, significant portions
of the IPS output reports will be missing.
ACTION: Activate the CA MICS collection of RMF Trace
data and resubmit the inquiry. Contact your
CA MICS system administrator for assistance.
REFERENCES: None
+-----------------+
| P E R 0 2 0 0 5 |
+-----------------+
TEXT: MORE THAN 5 CLASSES WERE FOUND FOR ONE OR MORE
INITIATORS - THE REDUCED BACKLOG MODEL WILL BE
USED.
TYPE: Information
REASON: More than five job classes were specified for at
least one of the batch initiators. Because of
software restrictions, a reduced backlog model
is used when this condition is found.
ACTION: If the reduced backlog model is not acceptable,
change the inquiry so that no initiator
specifies more than five job classes.
REFERENCES: Section 3.1.6, Component Operation
+-----------------+
| P E R 0 2 0 0 6 |
+-----------------+
TEXT: JOBPRTY HAS BEEN FOUND MISSING. IT WILL BE SET
TO ZERO.
TYPE: Warning
REASON: At least one of the observations selected for
processing had no valid JOBPRTY (Job Priority).
The routines continue processing, but assign a
JOBPRTY of zero to this job.
ACTION: None required.
REFERENCES: Section 3.1.6, Component Operation
+-----------------+
| P E R 0 2 0 0 7 |
+-----------------+
TEXT: NO JOBS SELECTED. SIMULATION WILL NOT BE DONE.
TYPE: Information
REASON: The simulation software cannot continue because
no observations were selected for processing.
ACTION: Examine the selection criteria specified on the
inquiry panel to make sure it is correct. Make
sure the specified input source contains valid
data. Resubmit the inquiry.
REFERENCES: Section 3.1.6, Component Operation
+-----------------+
| P E R 0 2 0 0 8 |
+-----------------+
TEXT: THE CLOCK STEP HAS BEEN SET TO "value" SECONDS.
TYPE: Information
REASON: The inquiry routines use a clock step value
equal to that shown in the message.
ACTION: If the value in the message is not acceptable,
you can specify an alternate value by using the
Extended Options Menu panel of the inquiry.
REFERENCES: Section 3.1.6, Component Operation
+-----------------+
| P E R 0 2 0 0 9 |
+-----------------+
TEXT: JOBQ SIZE EXCEEDED - JOB INPUT STOPPED AT
"value".
TYPE: Termination
REASON: More jobs were read into the simulation than
could be handled by the default internal array
sizes. In the message text, "value" represents
the number of jobs read before the error was
detected.
ACTION: Increase the number of classes specified for one
of the initiators to at least six. If the
problem persists, contact CA Technical Support
at http://ca.com/support.
REFERENCES: Section 3.1.6, Component Operation
+-----------------+
| P E R 0 2 0 1 0 |
+-----------------+
TEXT: RUNAWAY LOOP DETECTED IN JOB-SELECTION MODULE.
TYPE: Termination
REASON: A logic error resulted in a program loop in the
job selection portion of the simulation routine.
ACTION: Contact CA Technical Support at
http://ca.com/support.
REFERENCES: Section 3.1.6, Component Operation
+-----------------+
| P E R 0 2 0 1 1 |
+-----------------+
TEXT: JOB "job", STEP NUMBER "step", PROGRAM "program"
ALLOCATED BOTH 3480 AND NON-3480 DRIVES. MOUNT
TIME ADJUSTMENT IS GLOBAL IN NATURE. ADJUSTMENT
WILL OCCUR.
TYPE: Warning
REASON: The inquiry routines determined that the job
specified in the error message used both 3420
and 3380 tape drives. The adjustment for mount
time is not as accurate as if only one type of
device had been used.
ACTION: None required.
REFERENCES: Section 2.4.7, Tape Drive Simulation Analysis
Inquiry
+-----------------+
| P E R 0 2 0 1 2 |
+-----------------+
TEXT: AT LEAST ONE TYPE 30 INTERVAL RECORD HOLDING THE
TAPE DRIVE ALLOCATION TOTALS WAS DROPPED.
TYPE: Information
REASON: A CA MICS observation representing an SMF Type
30 interval record showed no tape drives were
allocated (PGMMXNTA=0) but tape EXCPs were
recorded (PGMETAPE not 0). The invalid record
is dropped from the analysis.
ACTION: None. If you get an excessive number of these
messages, you may want to investigate the reason
for the invalid data.
REFERENCES: Section 2.4.7, Tape Drive Simulation Analysis
Inquiry
+-----------------+
| P E R 0 2 0 1 3 |
+-----------------+
TEXT: CONNECT TIME CANNOT BE ADJUSTED IN MORE THAN ONE
FASHION IN THE SAME STEP RECORD. NO ADJUSTMENT
WILL OCCUR FOR JOB "job" STEP "step".
TYPE: Information
REASON: Only one type of connect time adjustment is
possible in one step records. Adjustment is
bypassed for the indicated job and step due to a
multiple adjustment attempt.
ACTION: Examine your inquiry options to make sure only
one adjustment is occurring per step.
REFERENCES: Section 2.4.7, Tape Drive Simulation Analysis
Inquiry
+-----------------+
| P E R 0 2 0 1 4 |
+-----------------+
TEXT: RECORDS WITH MISSING START TIMESTAMPS WERE
DROPPED FROM THE ANALYSIS, BAD RECORDS =
"count".
TYPE: Information
REASON: The number of observations shown in the message
were dropped from the simulation because they
did not contain a valid start date and time.
ACTION: None. If you get an excessive number of these
messages, you may want to investigate the reason
for the invalid data.
REFERENCES: Section 2.4.7, Tape Drive Simulation Analysis
Inquiry
+-----------------+
| P E R 0 2 0 1 5 |
+-----------------+
TEXT: RECORDS WITH MISSING END TIMESTAMPS WERE DROPPED
FROM THE ANALYSIS, BAD RECORDS = "count".
TYPE: Information
REASON: The number of observations shown in the message
were dropped from the simulation because they
did not contain a valid end date and time.
ACTION: None. If you get an excessive number of these
messages, you may want to investigate the reason
for the invalid data.
REFERENCES: Section 2.4.7, Tape Drive Simulation Analysis
Inquiry
+-----------------+
| P E R 0 2 0 1 6 |
+-----------------+
TEXT: THE VOLSER - "volume" IS THE ONLY VOLUME IN DAY
-"day" AT "timespan". CONTENTION INDICES
CANNOT BE COMPUTED FOR THIS TIME FRAME, RECORD
DROPPED FROM ANALYSIS.
TYPE: Information
REASON: Only one volume was selected from the day and
timespan shown in the message. A contention
index cannot be computed using just one
observation. The observation is dropped.
ACTION: None required.
REFERENCES: Section 2.4.6, DASD Multiple Volume Analysis
Inquiry
+-----------------+
| P E R 0 2 0 1 7 |
+-----------------+
TEXT: MULTIPLE VOLUME ANALYSIS ASSUMES GROUPS OF
"number" DEVICES WILL BE ONLINE DURING THE SAME
TIME FRAME. FOR THE LAST "value" GROUPS THIS
WAS NOT THE CASE, THESE GROUPS ARE DROPPED FROM
THE REPORT.
TYPE: Information
REASON: The number of online volumes found during a
reporting interval was not an even multiple of
the number specified for this n-way analysis.
Some devices are dropped from the analysis.
ACTION: Either ignore the message or change the volumes
specified in the inquiry to avoid the problem.
REFERENCES: Section 2.4.6, DASD Multiple Volume Analysis
Inquiry
+-----------------+
| P E R 0 2 0 1 8 |
+-----------------+
TEXT: MULTIPLE VOLUME ANALYSIS PLOTS ARE DONE WHEN
CONTENTION INDEX GT 5 OR SUMMATION INDEX GT 25.
GROUP "number" DID NOT QUALIFY FOR PLOTTING.
TYPE: Information
REASON: To reduce the output produced, a plot for a
volume group is produced only if the group has a
contention index greater than 5 or a summation
index greater than 25. A plot was not produced
for the group indicated in the message.
ACTION: None required.
REFERENCES: Section 2.4.6, DASD Multiple Volume Analysis
Inquiry
+-----------------+
| P E R 0 2 0 1 9 |
+-----------------+
TEXT: NO SUMMARIZED OBSERVATIONS HAVE PASSED THE
SPECIFIED FILTERING PROCESS. REPORT CANNOT BE
PRODUCED. TEST WAS "statement".
TYPE: Error
REASON: You specified a usage qualification to apply
against the observations in the inquiry that
caused all observations to be deleted from the
inquiry. No output can be produced.
ACTION: Remove or modify the usage qualification
specified on the inquiry panel so that some data
is selected for reporting.
REFERENCES: Section 2.4 - I/O Configuration Analysis
+-----------------+
| P E R 0 2 0 2 0 |
+-----------------+
TEXT: REPORT CANNOT BE RUN. A NON-XA RMF LEVEL HAS
BEEN FOUND AND THE "file(s) are/is" NOT
AVAILABLE.
TYPE: Error
REASON: Because the input data being processed is from a
non-XA system, certain additional input files
are needed to produce the requested inquiry.
The message indicates that one or more of these
files cannot be found.
ACTION: Use a different source of input data or
determine why the listed files are not
available.
REFERENCES: Section 2.4.5, DASD Skew Analysis Inquiry
+-----------------+
| P E R 0 2 0 2 1 |
+-----------------+
TEXT: THE LINES PER PAGE WAS SET TO LESS THAN 30, THIS
REPORT REQUIRES A MINIMUM PAGE SIZE OF 30, PAGE
SIZE SET TO 30.
TYPE: Information
REASON: Your MICF options specify a page size of less
than 30 lines per page, but this report requires
at least 30 lines per page for acceptable
output. The page size has been set to 30 lines
for this report.
ACTION: Change your MICF options to use a page size of
at least 30.
REFERENCES: None
+-----------------+
| P E R 0 2 0 2 2 |
+-----------------+
TEXT: WARNING THE EFFECTS OF SHARED DASD MAY NOT BE
CORRECTLY EVALUATED WHEN SYSID SELECTION IS IN
EFFECT.
TYPE: Information
REASON: To be effective, a shared DASD report must
consider all systems that share a DASD device.
The inquiry being run specified that input data
be selected by SYSID. This could cause the
report output to be inaccurate if not all
systems are considered.
ACTION: Evaluate the reasons why some systems are being
excluded. Change the inquiry options if
necessary.
REFERENCES: Section 2.4.3, Shared DASD Analysis Inquiry
+-----------------+
| P E R 0 2 0 2 3 |
+-----------------+
TEXT: NO PR/SM LPAR DATA FOUND IN HARLPC FILE(S).
REPORT CANNOT BE PRODUCED UNTIL PR/SM DATA IS
PROCESSED BY CA MICS. RUN TERMINATES WITH A USER
998 CONDITION CODE.
TYPE: Error
REASON: An attempt was made to produce a report for
PR/SM LPAR analysis, but no PR/SM data has yet
been processed into the CA MICS database by the
standard update jobs.
ACTION: Run terminates with a user 998 abend. Check with
your system administrator as to when PR/SM data
will be available.
REFERENCES: Section 2.6, PR/SM LPAR Analysis
+-----------------+
| P E R 0 2 0 2 4 |
+-----------------+
TEXT: ALLOCATING MMG WORK DATA SET. DDNAME: MMGWRKLD/
DATA SET: "data set name"
TYPE: Information
REASON: An MMG workload data set was specified for a
graphic analysis inquiry. The system
dynamically allocates the data set and parses
the table in order to group together homogeneous
workload types. If subsequent error messages
indicate some sort of allocation problem, this
message shows the data set name that was being
allocated.
ACTION: Unless a subsequent error message indicates an
allocation problem, this message can be ignored.
REFERENCES: Section 2.7.6.3, Workload Groupings
+-----------------+
| P E R 0 2 0 2 5 |
+-----------------+
TEXT: DYNAMIC ALLOCATION ERROR FOR DATA SET: "data set
name" / ERROR CODE: "nnnn" / INFO CODE: "yyyy"
TYPE: Error
REASON: An attempt was made to allocate an MMG work data
set for a graphic analysis inquiry. The system
was unable to successfully allocate the data
set.
ACTION: Run terminates with a user 998 abend. Check the
spelling of the data set name. If the name is
spelled correctly, and the data set exists and
is cataloged, there can be a more serious system
problem. If so, contact your CA MICS system
administrator.
REFERENCES: Section 2.7.6.3, Workload Groupings
+-----------------+
| P E R 0 2 0 2 6 |
+-----------------+
TEXT: DYNAMIC ALLOCATION FAILURE ATTEMPTING TO FREE
DDNAME: "ddname", / ERROR CODE: "nnnn" / INFO
CODE: "yyyy". PROCESSING WILL CONTINUE.
TYPE: Warning
REASON: An attempt was made to free the MMG work data
set that was previously allocated dynamically.
Since the original allocation was successful,
this error does not affect the processing of the
current inquiry, and it is allowed to proceed.
ACTION: You can check that the MMG workload data
set is still accessible. No other action is
required.
REFERENCES: Section 2.7.6.3, Workload Groupings
+-----------------+
| P E R 0 2 0 2 7 |
+-----------------+
TEXT: THE LINES PER PAGE WAS SET TO LESS THAN 40, THIS
REPORT REQUIRES A MINIMUM PAGE SIZE OF 40, PAGE
SIZE SET TO 40.
TYPE: Information
REASON: Your MICF options specify a page size of less
than 40 lines per page, but this report requires
at least 40 lines per page for acceptable
output. The page size has been set to 40 lines
for this report.
ACTION: Change your MICF options to use a page size of
at least 40.
REFERENCES: None
+-----------------+
| P E R 0 3 0 0 0 |
+-----------------+
TEXT: GENERIC INFORMATIONAL MESSAGE
TYPE: Information
REASON: This message is used for many reasons.
ACTION: No action required.
REFERENCES: None
+-----------------+
| P E R 0 3 0 1 0 |
+-----------------+
TEXT: GENERIC MESSAGE USED TO GENERATE TWO BLANK LINES
TYPE: Information
REASON: Generic message used to generate line spacing on
MICSLOG entries.
ACTION: No action required.
REFERENCES: None
+-----------------+
| P E R 0 3 0 1 2 |
+-----------------+
TEXT: GENERIC MESSAGE USED TO GENERATE ONE BLANK LINE
TYPE: Information
REASON: Generic message used to generate line spacing on
MICSLOG entries.
ACTION: No action required.
REFERENCES: None
+-----------------+
| P E R 0 3 0 5 0 |
+-----------------+
TEXT: "PHASE": "_PGMTTL" BEGINNING EXECUTION...
TYPE: Information
REASON: Processing phase _PGMTTL is starting.
ACTION: None.
REFERENCES: None
+-----------------+
| P E R 0 3 0 6 0 |
+-----------------+
TEXT: NEUGENTS MODEL "_FUNCT" PHASE BEGINNING...
TYPE: Information
REASON: Neugents technology internal phase _FUNCT
starting.
ACTION: None.
REFERENCES: None
+-----------------+
| P E R 0 3 0 7 0 |
+-----------------+
TEXT: "PHASE": "_PGMTTL" ENDING EXECUTION...
TYPE: Information
REASON: Processing phase _PGMTTL ending.
ACTION: None.
REFERENCES: None
+-----------------+
| P E R 0 3 0 7 5 |
+-----------------+
TEXT: "PHASE": "_PGMTTL" ABNORMALLY TERMINATING
TYPE: Error
REASON: Processing _PGMTTL abnormally terminated.
ACTION: Neugents technology processing job ends.
REFERENCES: None
+-----------------+
| P E R 0 3 0 8 0 |
+-----------------+
TEXT: "V1" FILE CONTAINS "N" RECORDS SELECTED FOR
PROCESSING.
TYPE: Information
REASON: N records have been selected for processing from
file V1.
ACTION: None.
REFERENCES: None
+-----------------+
| P E R 0 3 0 8 5 |
+-----------------+
TEXT: DATA FROM FILE "V1" WILL BE EXCLUDED, YOUR
RESULTS MAY BE NEGATIVELY AFFECTED.
TYPE: Warning.
REASON: Some observations from file VI were excluded,
either due to data value errors or unmatched
observations among files. Modeling results can
be affected and should be examined because of
this message.
ACTION: None.
REFERENCES: None.
+-----------------+
| P E R 0 3 0 9 0 |
+-----------------+
TEXT: NO FORECAST FILE ENTRY FOUND FOR "V1" ENTRY:,
TYPE: Warning.
REASON: An observation in the primary PER file was not
matched in the alternate input file.
ACTION: The original observation is discarded from
further processing. See message PER03095 for
additional details.
REFERENCES: None.
+-----------------+
| P E R 0 3 0 9 5 |
+-----------------+
TEXT: %FNAME %FDATA
TYPE: Warning.
REASON: One of the key values of the unmatched
observation is displayed. FNAME is the name of
the key variable; FDATA is the data value of
the key variable.
ACTION: None.
REFERENCES: None.
+-----------------+
| P E R 0 3 1 0 0 |
+-----------------+
TEXT: REPORT: "V1" BEING CURRENTLY GENERATED ON
DDNAME //"V1"
TYPE: Informational
REASON: Generation of report V1 has started.
ACTION: The report is written on ddname V1. This
message is only issued if the MICF environment
is not being used. Message PER03105 is normally
issued instead.
REFERENCES: None.
+-----------------+
| P E R 0 3 1 0 5 |
+-----------------+
TEXT: REPORT: "V1" BEING CURRENTLY GENERATED.
TYPE: Informational
REASON: Generation of report V1 has started.
ACTION: Reports generated within the MICF environment
are normally written to the SASLIST DD.
REFERENCES: None.
+-----------------+
| P E R 0 3 1 1 0 |
+-----------------+
TEXT: REPORT: "V1" BEING CURRENTLY GENERATED VIA CSV
FILE.
TYPE: Informational
REASON: Generation of report V1 has started and will be
created using a CSV file.
ACTION: This option is used to create MQR-compatible
CSV files.
REFERENCES: None.
+-----------------+
| P E R 0 3 1 2 0 |
+-----------------+
TEXT: GRAPH: "V1" BEING CURRENTLY GENERATED ON DDNAME
//"V1"
TYPE: Informational
REASON: Generation of graph V1 has started.
ACTION: The graph is written on ddname V1. This
message is only issued if the MICF environment
is not being used. Message PER03125 is normally
issued instead.
REFERENCES: None.
+-----------------+
| P E R 0 3 1 2 5 |
+-----------------+
TEXT: GRAPH: "V1" BEING CURRENTLY GENERATED.
TYPE: Informational
REASON: Generation of graph V1 has started.
ACTION: Graphs generated within the MICF environment
are normally written to the SASLIST DD.
REFERENCES: None.
+-----------------+
| P E R 0 3 1 3 0 |
+-----------------+
TEXT: GRAPH: "V1" BEING CURRENTLY GENERATED VIA CSV
FILE.
TYPE: Informational
REASON: Generation of graph V1 has started and will be
created using a CSV file.
ACTION: This option is used to create MQR compatible
CSV files.
REFERENCES: None.
+-----------------+
| P E R 0 3 1 5 0 |
+-----------------+
TEXT: INVALID DATA VALUES DETECTED IN "V1" FILE,
"_PGMTTL" CANNOT PROCESS SUCCESSFULLY, WHEN
DATA VALUES ARE MISSING OR INVALID. SEE
BADTRAIN REPORT FOR DETAILS.
TYPE: Warning
REASON: Missing or zero values were detected in data
elements in one or more observations.
ACTION: The observations are discarded from further
processing. Report BADTRAIN contains a
list of observations that were dropped.
REFERENCES: None.
+-----------------+
| P E R 0 3 1 6 0 |
+-----------------+
TEXT: MODEL SUMMARY STATISTICS HAVE BEEN CREATED ON
DDNAME //MODLSTAT
TYPE: Informational
REASON: The Model Summary Statistics report is being
created.
ACTION: The report is written on ddname MODLSTAT. This
message is only issued if the MICF environment
is not being used. Message PER03165 is normally
issued instead.
REFERENCES: None.
+-----------------+
| P E R 0 3 1 6 5 |
+-----------------+
TEXT: MODEL SUMMARY STATISTICS HAVE BEEN CREATED.
TYPE: Informational
REASON: The Model Summary Statistics report is being
created.
ACTION: Reports generated within the MICF environment
are normally written to the SASLIST DD.
REFERENCES: None.
+-----------------+
| P E R 0 3 1 7 0 |
+-----------------+
TEXT: "_FORTYP" FORECASTING OPTION SELECTED -, "V1"
"V2" OF PREDICTED DATA WILL BE GENERATED.
BEGINNING WITH "X_SDATE".
TYPE: Informational.
REASON: For forecasting option _FORTYP, V1
months/weeks/days of data were selected for
processing, beginning with X_DATE. This
message defined the time frame of the modeling
study.
ACTION: None.
REFERENCES: None.
+-----------------+
| P E R 0 3 3 1 0 |
+-----------------+
TEXT: MACRO "PHASE" FAILED WITH RETURN CODE "RC"
TYPE: Error.
REASON: A non-zero return code value was detected upon
return from Neugents technology.
ACTION: Neugents technology processing is terminated.
REFERENCES: None.
+-----------------+
| P E R 0 3 3 2 0 |
+-----------------+
TEXT: MACRO GLOBALS MISSING REQUIRED OPERAND
"MODNAME", EXECUTION TERMINATING.
TYPE: Error.
REASON: An internal error has occurred. This message
should never occur except during product
development.
ACTION: Processing terminates.
REFERENCES: None.
+-----------------+
| P E R 0 3 3 2 5 |
+-----------------+
TEXT: MACRO GLOBALS MISSING REQUIRED OPERAND
"MODTITLE", EXECUTION TERMINATING.
TYPE: Error
REASON: An internal error has occurred. This message
should never occur except during product
development.
ACTION: Processing terminates.
REFERENCES: None.
+-----------------+
| P E R 0 3 3 9 0 |
+-----------------+
TEXT: MACRO "PHASE" TERMINATING, ABORT REQUESTED.
TYPE: Error.
REASON: A terminal error condition was detected in
macro PHASE. This message is preceded by
either message PER03310 or PER03590.
ACTION: Neugents technology processing terminates.
REFERENCES: None.
+-----------------+
| P E R 0 3 4 1 0 |
+-----------------+
TEXT: MODEL TRAINING PHASE COMPLETED SUCCESSFULLY.
TRAINING STATISTICS ARE SUMMARIZED ON DDNAME
//DELTASTS, AND ARE INCLUDED BELOW:
NUMBER OF CASES USED FOR TRAINING: "N",
AVERAGE MODEL ERROR MEASURED: "V1",
AVERAGE MODEL RMS ERROR MEASURED: "V2",
(GOODNESS OF FIT) FOR MODEL: "V3"
TYPE: Informational
REASON: Neugents Technology Value Prediction models
first execute a training phase and produce
several statistics used to evaluate the model.
These statistics are displayed in the message.
ACTION: The client should review the statistics before
deciding on the validity of the model.
REFERENCES: None.
+-----------------+
| P E R 0 3 4 2 0 |
+-----------------+
TEXT: MODEL FORECASTING PHASE COMPLETED SUCCESSFULLY.
FORECASTING STATISTICS ARE SUMMARIZED ON DDNAME
//CONSFCS, AND ARE INCLUDED BELOW:
NUMBER OF CASES USED FOR FORECASTING: "N",
(GOODNESS OF FIT) FOR MODEL: "V1"
TYPE: Informational
REASON: Neugents Technology Value Prediction models
secondly execute a consulting phase and produce
additional statistics used to evaluate the
model. These statistics are displayed in the
message.
ACTION: The client should review the statistics before
deciding on the validity of the model.
REFERENCES: None.
+-----------------+
| P E R 0 3 4 3 0 |
+-----------------+
TEXT: LINEAR REGRESSION PHASE COMPLETED SUCCESSFULLY.
MODEL STATISTICS ARE SUMMARIZED ON DDNAME
//MODLSTAT, AND ARE INCLUDED BELOW: NUMBER OF
CASES USED FOR MODELING: "V1",
SLOPE OF REGRESSION LINE: "V2",
INTERCEPT VALUE FOR IND. ELEMENT: "V3",
(GOODNESS OF FIT) FOR MODEL: "V4"
TYPE: Informational
REASON: Workload Forecasting executes a simple linear
regression operation when a single file is
specified and only a forecasting element is
provided. Regression models produce various
statistics used to evaluate the model. These
statistics are displayed in the message.
ACTION: The client should review the statistics before
deciding on the validity of the model. The
report is written on ddname MODLSTAT. This
message is only issued if the MICF environment
is not being used. Message PER03435 is normally
issued instead.
REFERENCES: None.
+-----------------+
| P E R 0 3 4 3 5 |
+-----------------+
TEXT: LINEAR REGRESSION PHASE COMPLETED SUCCESSFULLY.
MODEL STATISTICS ARE SUMMARIZED ON DDNAME
//SASLIST AND ARE INCLUDED BELOW: NUMBER OF
CASES USED FOR MODELING: "V1",
SLOPE OF REGRESSION LINE: "V2",
INTERCEPT VALUE FOR IND. ELEMENT: "V3",
(GOODNESS OF FIT) FOR MODEL: "V4"
TYPE: Informational
REASON: Workload Forecasting executes a simple linear
regression operation when a single file is
specified and only a forecasting element is
provided. Regression models produce various
statistics used to evaluate the model. These
statistics are displayed in the message.
ACTION: The client should review the statistics before
deciding on the validity of the model. Reports
generated within the MICF environment are
normally written to the SASLIST DD.
REFERENCES: None.
+-----------------+
| P E R 0 3 5 1 0 |
+-----------------+
TEXT: OPEN FAILED FOR "STD" FILE. SYSTEM ERROR
MESSAGE IS "SYSMSG" EXECUTION TERMINATED.
TYPE: Error
REASON: An open was issued for files with ddname STD.
Such files are used by Neugents technology
processing for passing data between Neugents
technology and the CA MICS Performance Manager
Option applications, or are required by USS for
internal use. The return code from open
processing is displayed as RC. Generally, a
non-zero return code value causes processing to
be terminated.
ACTION: Review the specific system message for action.
REFERENCES: None.
+-----------------+
| P E R 0 3 5 9 0 |
+-----------------+
TEXT: ERROR TEXT FROM NEUGENTS PROCESSING
"ERRMSG" EXECUTION TERMINATED.
TYPE: Error
REASON: Any error text returned by USS in the STDERR
data set is displayed herein.
ACTION: Review specific error message for action.
REFERENCES: None.
+-----------------+
| P E R 0 3 6 0 0 |
+-----------------+
TEXT: DATA FOUND IN THE BATMUG FILE FOR SYSID: LP01
-NO CORRESPONDING DATA WAS FOUND IN THE HARCPU
FILE. REPORTING WILL EXCLUDE SYSID: LP01
TYPE: Warning
REASON: Product usage data was found in the BATMUG file
for the given SYSID, but no corresponding SYSID
found in the HARCPU file. The problem may be
caused because the systems data may not be
processed into the RMF unit selected for
reporting.
ACTION: Verify that all SYSIDs represented in the
BATMUG file are processing into the RMF unit
selected for reporting.
REFERENCES: None.
+-----------------+
| P E R 0 3 6 0 5 |
+-----------------+
TEXT: SYSID: LP01 OBSERVATIONS FOUND IN THE HARCPU
FILE WITH NO CORRESPONDING DATA IN THE BATMUG
FILE. - OBSERVATION WILL BE DROPPED FROM
ANALYSIS.
TYPE: Informational
REASON: Data was found in the HARCPU file that did not
correspond with any BATMUG data based on the
merge by of SYSID YEAR MONTH DAY HOUR. This
indicates that data from a given day or hour is
missing from the HARCPU file.
ACTION: Verify that the HARCPU file cycle retention is
equal to the number of cycles kept for the
BATMUG file.
REFERENCES: None.
+-----------------+
| P E R 0 3 6 1 0 |
+-----------------+
TEXT: SYSID: LP01 OBSERVATIONS FOUND IN THE BATMUG
FILE WITH NO CORRESPONDING DATA IN THE HARCPU
FILE. - OBSERVATION WILL BE DROPPED FROM
ANALYSIS.
TYPE: Informational
REASON: Data was found in the BATMUG file that did not
correspond with any HARCPU data based on the
MERGE BY of SYSID YEAR MONTH DAY HOUR. This
indicates that data from a given day or hour is
missing from the BATMUG file.
ACTION: Verify that the BATMUG file cycle retention is
equal to the number of cycles kept for the
HARCPU file.
REFERENCES: None.
+-----------------+
| P E R 0 3 6 2 0 |
+-----------------+
TEXT: SYSID: XE09 FROM THE HARCPU FILE HAS MISSING
VALUES FOR CPUAVLAC.
- DATA WILL BE INCLUDED IN REPORTING, BUT WILL
NOT CONTRIBUTE TO THE TOTAL SYSTEM USAGE.
TYPE: Informational
REASON: Data was found in the HARCPU file that has
missing values for the Long-Term Average of CPU
Service in MSUs (CPUAVLAC). There can be
several reasons for this element to have
missing values. See ACTION below to begin.
ACTION: Review the data dictionary for a detailed
explanation of CPUAVLAC and review its settings
in RMFGENIN.
REFERENCES: None.
+-----------------+
| P E R 0 3 6 3 0 |
+-----------------+
TEXT: NO DATA FOUND IN BATMUG THAT MATCHED YOUR
VENDOR SETTING OF:" vendor name"
QUERY TERMINATING ...
TYPE: Error
REASON: No data selected from the BATMUG file had a
Vendor/Owner (MUOWNER) equal to the Vendor
setting on the query composition panel.
ACTION: Remove the Vendor setting on the composition
panel. Turn on the frequency reports and turn
off the other reports. Execute the query and
review the "Frequency Report of MUOWNER:
Vendor/Owner" for a list of vendors represented
in your data. Note the Vendor you wish to
report on and reset the Vendor setting on the
composition panel with the correct vendor name.
Activate the reports you want to see and submit
the query.
REFERENCES: None.
+-----------------+
| P E R 0 3 6 3 5 |
+-----------------+
TEXT: SYSID: LPAR OBSERVATIONS FOUND IN THE BATMUG
FILE WITH MORE THAN 16 CONFIGURED CPU.
THE 16TH CPU CAPABILITY ADJ. FACTOR, CAPMAF16,
WILL BE USED IN THE SU CONVERSION FACTOR
CALCULATION.
TYPE: Informational
REASON: Although it is possible to have more than 16
configured CPs, the SMF-89 record only provides
CPU adjustment factors for up to 16 processors.
ACTION: In case more than 16 configured processors are
encountered in the data, the CPU adjustment
factor for 16 processors will be used in the SU
conversion factor calculation.
REFERENCES: None.
+-----------------+
| P E R 0 3 8 0 0 |
+-----------------+
TEXT: FILE/TIMESPAN VALIDATION ERROR: The "FILE"
file must be active at the "TIMESPAN" timespan.
Review the GENLIB settings for the "FILE" file.
TYPE: Error
REASON: The CA MICS file used in this query was not
active at the given timespan.
ACTION: Review the GENLIB settings for the indicated
file.
REFERENCES: None.
+-----------------+
| P E R 0 3 9 0 0 |
+-----------------+
TEXT: CA MICS Performance Manager Threshold
Reporting And Alerting Initiated.
MSU Consumption Rate and Soft Capping Analysis
Threshold Exceptions.
Soft Capping percentage has exceeded 07% for
the following LPARs in one or more reporting
intervals:
SYSPLEX SYSID LPAR_NAME EXCEPTION_DATA_TIME
------- ----- --------- -------------------
PLEX0A MJ01 MJ01 15JUNyyyy:16:14:00
PLEX0B MJ02 MJ02 15JUNyyyy:16:14:00
TYPE: Informational
REASON: The Soft Capping percentage threshold set in
the extended options has been exceeded for one
or more LPARs in one or more reporting
intervals.
ACTION: Look for the eye catcher "<- EXCEEDED 05%" in
the MSU Consumption Rate and Soft Capping
Report to see all the LPARs and time intervals
that exceeded the specified threshold.
If Threshold Alerting is active, see the
MICSLOG message BAS63099 to verify that the
alert was generated successfully.
REFERENCES: None.
+-----------------+
| P E R 0 3 9 2 0 |
+-----------------+
TEXT: Defined Group Capacity Reports Not Generated.
No LPARs found with a Defined Group Capacity.
TYPE: Informational
REASON: The Defined Group Capacity Reports can not be
generated because there were no LPARs in the
input data source with a defined group
capacity.
ACTION: Confirm that the SYSIDs used as input have a
group capacity defined.
REFERENCES: None.
Copyright © 2014 CA.
All rights reserved.
|
|