Appendix A. ERROR MESSAGES
The first part of this appendix lists the messages that may
appear on the MICSLOG report after a StorageMate report has
been executed. These messages are one of three types:
o Information. This message usually indicates no error, and
is usually issued to document information that existed
about the environment when the report was run.
o Warning. A minor error was detected that may cause all or
part of the output to be invalid. Examine the error
message text and the output reports to see if they are
usable.
o Error. A severe error has occurred that caused processing
to terminate immediately. The results produced by the
report, if any, will probably not be valid.
+-----------------+
|S T G 0 0 0 0 1 |
+-----------------+
TEXT: NO DATA IN <file> FILE AFTER DATA FILTERING.
CHECK INPUT SPECIFICATIONS AND VALUES SPECIFIED
FOR FILTERING.
PROCESSING WILL BE ABORTED.
TYPE: Error
REASON: After performing data filtering, one of the files
used to produce this report contained no data, and no
reports can be produced. In the message text, <file> is
replaced by the name of the SAS file that is empty.
ACTION: Processing aborts with a U998 abend. Verify the
Cycle Number(s) and filtering criteria you have specified.
Try removing all filtering criteria and specifying a known
cycle number.
REFERENCES: None.
+-----------------+
|S T G 0 0 0 0 2 |
+-----------------+
TEXT: NO DATA IN <file> FILE AFTER DATA FILTERING.
CHECK INPUT SPECIFICATIONS AND VALUES SPECIFIED
FOR FILTERING.
PROCESSING WILL CONTINUE, BUT SOME REPORTS MAY
NOT BE PRODUCED.
TYPE: Warning
REASON: At least one file used to produce output from this
analysis was found to be empty. In the message text, <file>
is replaced by the SAS name of the empty file.
ACTION: Processing continues, but one or more requested
reports may not be produced. Verify the options specified
during report specification to make sure they are correct.
REFERENCES: None.
+-----------------+
|S T G 0 0 0 0 3 |
+-----------------+
TEXT: DYNAMIC ALLOCATION FAILURE FOR DATA SET: <dsname>
MEMBER: <member> / ERROR CODE: <error> /
INFO CODE: <info>
VERIFY THAT THE DATA SET NAME AND MEMBER NAME ARE
CORRECT FOR THIS OPERATION.
TYPE: Error
REASON: An attempt to dynamically allocate one of the data
sets needed by this facility was not successful. In the
message text, <dsname> represents the data set name for
which the allocation was attempted, <member> represents the
member name within the data set, <error> and <info>
represent error and information codes from the MVS dynamic
allocation facility.
ACTION: Processing aborts with a U998 abend. Make sure the
data set name shown represents an existing cataloged data
set that is not allocated to another user.
REFERENCES: Refer to a list of dynamic allocation error
codes in IBM manuals or the ISPF tutorial.
+-----------------+
|S T G 0 0 0 0 4 |
+-----------------+
TEXT: TRKCALC FAILURE FOR DATA SET: <dsname>
VOLUME: <volser> / DEV-BLK-KEY: <parm> / RETURN
CODE: <code>.
VERIFY THAT THE DEVICE TYPE, BLOCK SIZE, AND KEY
LENGTH FOR THIS DATA SET ARE VALID.
TYPE: Warning
REASON: An attempt to use the IBM TRKCALC service for this
data set failed. In the message text, <dsname> is replaced
by the data set name, <volser> by the serial number, <parm>
by the parameter list passed to TRKCALC, and <code> by the
error code returned.
ACTION: Processing continues, but some of the statistics
computed for this data set will not be valid. The first
eight characters of the parameter field are the device type,
the next five are the block size, and the final three are
the key length. Make sure these are valid. Error code 1
represents an error in TRKCALC itself, error code 2
indicates an invalid parameter list, and error code 3
represents an unknown device type. Verify that the device
type in the first part of the parameter is correct, and that
your operating system supports this type of device.
REFERENCES: None.
+-----------------+
| S T G 0 0 0 0 5 |
+-----------------+
TEXT: DATA SET CATALOG STATUS NOT AVAILABLE FOR DATA
SETS ON SYSID: <system>,
VERIFY THAT CATALOG STATUS COLLECTION WAS
REQUESTED WHEN THE DATA WAS GATHERED ON THIS
SYSTEM.
NO CATALOG ERRORS WILL BE DETECTED FOR ANY OF
THESE DATA SETS.
TYPE: Warning
REASON: Catalog status was not collected for all of the
data sets that reside on the indicated system. In the
message text, <system> is replaced by the name of the system
that had no status.
ACTION: Processing continues, but no catalog status errors
will be detected for any of the data sets on the indicated
system. Verify that the control statements used to run
CA MICS data collection on the indicated system specify that
catalog status is to be collected.
REFERENCES: CA MICS DASD Space Collector User Guide.
+-----------------+
|S T G 0 0 0 0 6 |
+-----------------+
TEXT: INVALID DATA SET NAME MASK FOUND: <mask> / ERROR
CODE: <code>.
VERIFY THAT THE MASK SHOWN FOLLOWS THE RULES
FOR VALID DATA SET NAME MASKS.
THIS STATEMENT WILL BE IGNORED AND PROCESSING
WILL CONTINUE.
TYPE: Warning
REASON: One of the data set pattern masks in the pattern
file you created is invalid. In the message text, <mask> is
replaced by the pattern mask in error, and <code> is
replaced by an error code of 2 or 3.
ACTION: Processing continues, but the entry shown will be
ignored. If the error code is 2, the pattern violates the
syntax rules for pattern masks, and should be corrected. If
the error code is 3, an internal logic error occurred.
REFERENCES: Online report tutorials. CA MICS StorageMate
Guide, Section 4.3.
+-----------------+
|S T G 0 0 0 0 7 |
+-----------------+
TEXT: THE INTERNAL MAXIMUM OF <level> SUMMARIZATION
LEVELS HAS BEEN EXCEEDED FOR THIS REPORT.
MODIFY INPUT, FILTERING, OR SUMMARIZATION
OPTIONS TO CREATE FEWER LEVELS.
PROCESSING WILL CONTINUE, BUT ANY REMAINING
DATA WILL NOT BE INCLUDED IN THE OUTPUT.
TYPE: Warning
REASON: The number of summary levels created has exceeded
the internal limit for the report. In the message text,
<level> is replaced by the number of summary levels
supported.
ACTION: Processing continues, but all summary levels past
the limit shown will be ignored. Modify your report options
to include less data in the analysis or to otherwise reduce
the number of reporting levels.
REFERENCES: None.
+-----------------+
|S T G 0 0 0 0 8 |
+-----------------+
TEXT: THE FOLLOWING BLANK ENTRY WAS FOUND WITHIN THE
DATA SET GROUP TABLE:
<entry>
PROCESSING WILL CONTINUE, BUT THIS STATEMENT
WILL BE IGNORED.
TYPE: Warning
REASON: Record positions 1-72 of the Data Set Group Table
entry shown were found to contain all spaces. In the
message text, <entry> is replaced by the image of the entry
that is in error.
ACTION: Table processing will continue, but will issue a
U998 abend after all statements have been processed. Remove
the incorrect statement or change it to a comment by adding
an asterisk. You should leave sequence numbers in columns
73-80 of each table entry to help identify these errors.
REFERENCES: CA MICS StorageMate Guide, Section 3.5.
+-----------------+
|S T G 0 0 0 0 9 |
+-----------------+
TEXT: THE DSNAME PORTION OF THIS DATA SET GROUP TABLE
ENTRY EXCEEDS 44 CHARACTERS:
<entry>
PROCESSING WILL CONTINUE, BUT THIS STATEMENT
WILL BE IGNORED.
TYPE: Warning
REASON: The statement shown from your Data Set Group Table
in invalid. The data set portion of the statement exceeds
the maximum size of 44 characters. In the message text,
<entry> is replaced by the image of the entry that is in
error.
ACTION: Table processing will continue, but will issue a
U998 abend after all statements have been processed.
Correct the statement that is in error or remove it from the
Data Set Group Table. You should leave sequence numbers in
columns 73-80 of each table entry to help identify these
errors.
REFERENCES: CA MICS StorageMate Guide, Section 3.5.
+-----------------+
|S T G 0 0 0 1 0 |
+-----------------+
TEXT: EMBEDDED ASTERISK FOUND WITHIN THE DSNAME PORTION
OF THIS DATA SET GROUP TABLE ENTRY:
<entry>
PROCESSING WILL CONTINUE, BUT THIS STATEMENT
WILL BE IGNORED.
TYPE: Warning
REASON: A syntax error was detected in the statement shown
from your Data Set Group Table. If the data set name
portion of the entry contains an asterisk, it must be the
last character. In the message text, <entry> is replaced by
the image of the entry that is in error.
ACTION: Table processing will continue, but will issue a
U998 abend after all statements have been processed.
Correct the statement that is in error or remove it from the
Data Set Group Table. You should leave sequence numbers in
columns 73-80 of each table entry to help identify these
errors.
REFERENCES: CA MICS StorageMate Guide, Section 3.5.
+-----------------+
|S T G 0 0 0 1 1 |
+-----------------+
TEXT: GROUP NAME MISSING FROM THE FOLLOWING DATA SET
GROUP TABLE ENTRY:
<entry>
PROCESSING WILL CONTINUE, BUT THIS STATEMENT
WILL BE IGNORED.
TYPE: Warning
REASON: The statement shown from your Data Set Group Table
contained a syntax error. No valid group assignment was
found as the second operand on the statement. In the
message text, <entry> is replaced by the image of the entry
that is in error.
ACTION: Table processing will continue, but will issue a
U998 abend after all statements have been processed.
Correct the statement that is in error or remove it from the
Data Set Group Table. You should leave sequence numbers in
columns 73-80 of each table entry to help identify these
errors.
REFERENCES: CA MICS StorageMate Guide, Section 3.5.
+-----------------+
|S T G 0 0 0 1 2 |
+-----------------+
TEXT: GROUP NAME FROM THE FOLLOWING DATA SET GROUP TABLE
ENTRY EXCEEDS 40 CHARACTERS:
<entry>
PROCESSING WILL CONTINUE, BUT THIS STATEMENT
WILL BE IGNORED.
TYPE: Warning
REASON: The statement shown from your Data Set Group Table
contained a syntax error. The group assignment specified as
the second operand on the statement exceeds the maximum
limit of 40 characters. In the message text, <entry> is
replaced by the image of the entry that is in error.
ACTION: Table processing will continue, but will issue a
U998 abend after all statements have been processed.
Correct the statement that is in error or remove it from the
Data Set Group Table. You should leave sequence numbers in
columns 73-80 of each table entry to help identify these
errors.
REFERENCES: CA MICS StorageMate Guide, Section 3.5.
+-----------------+
|S T G 0 0 0 1 3 |
+-----------------+
TEXT: NO VALID STATEMENTS WERE FOUND WITHIN THE
SPECIFIED DATA SET GROUP TABLE.
THIS MAY BE CAUSED BY AN EMPTY TABLE OR BY
PREVIOUS ERRORS.
PROCESSING WILL BE ABORTED.
TYPE: Error
REASON: A Data Set Group Table was specified for use by
this report, but no valid entries were found within it.
ACTION: Processing Terminates with a U998 ABEND. Refer to
the Work Data Set and Data Set Group Table names shown in
message STG00024. Verify that the indicated table in the
indicated data set contains valid Data Set Group entries.
Correct the errors or specify a different table name.
REFERENCES: CA MICS StorageMate Guide, Section 3.5.
+-----------------+
|S T G 0 0 0 1 4 |
+-----------------+
TEXT: THE FOLLOWING BLANK ENTRY WAS FOUND WITHIN THE
VOLUME GROUP TABLE:
<entry>
PROCESSING WILL CONTINUE, BUT THIS STATEMENT
WILL BE IGNORED.
TYPE: Warning
REASON: Record positions 1-72 of the Volume Group Table
entry shown were found to contain all spaces. In the
message text, <entry> is replaced by the image of the entry
that is in error.
ACTION: Table processing will continue, but will issue a
U998 abend after all statements have been processed. Remove
the statement that is in error or change it to a comment by
adding an asterisk. You should leave sequence numbers in
columns 73-80 of each table entry to help identify these
errors.
REFERENCES: CA MICS StorageMate Guide, Section 3.4.
+-----------------+
|S T G 0 0 0 1 5 |
+-----------------+
TEXT: THE VOLUME PORTION OF THIS VOLUME GROUP TABLE
ENTRY EXCEEDS 6 CHARACTERS:
<entry>
PROCESSING WILL CONTINUE, BUT THIS STATEMENT
WILL BE IGNORED.
TYPE: Warning
REASON: The statement shown from your Volume Group Table in
invalid. The volume portion of the statement exceeds the
maximum size of six characters. In the message text,
<entry> is replaced by the image of the entry that is in
error.
ACTION: Table processing will continue, but will issue a
U998 abend after all statements have been processed.
Correct the statement that is in error or remove it from the
Volume Group Table. You should leave sequence numbers in
columns 73-80 of each table entry to help identify these
errors.
REFERENCES: CA MICS StorageMate Guide, Section 3.4.
+-----------------+
|S T G 0 0 0 1 6 |
+-----------------+
TEXT: EMBEDDED ASTERISK FOUND WITHIN THE VOLUME PORTION
OF THIS VOLUME GROUP TABLE ENTRY:
<entry>
PROCESSING WILL CONTINUE, BUT THIS STATEMENT
WILL BE IGNORED.
TYPE: Warning
REASON: A syntax error was detected in the statement shown
from your Volume Group Table. If the volume name portion of
the entry contains an asterisk, it must be the last
character. In the message text, <entry> is replaced by the
image of the entry that is in error.
ACTION: Table processing will continue, but will issue a
U998 abend after all statements have been processed.
Correct the statement that is in error or remove it from the
Volume Group Table. You should leave sequence numbers in
columns 73-80 of each table entry to help identify these
errors.
REFERENCES: CA MICS StorageMate Guide, Section 3.4.
+-----------------+
|S T G 0 0 0 1 7 |
+-----------------+
TEXT: GROUP NAME MISSING FROM THE FOLLOWING VOLUME GROUP
TABLE ENTRY:
<entry>
PROCESSING WILL CONTINUE, BUT THIS STATEMENT
WILL BE IGNORED.
TYPE: Warning
REASON: The statement shown from your Volume Group Table
contained a syntax error. No valid volume group assignment
was found as the second operand on the statement. In the
message text, <entry> is replaced by the image of the entry
that is in error.
ACTION: Table processing will continue, but will issue a
U998 abend after all statements have been processed.
Correct the statement that is in error or remove it from the
Volume Group Table. You should leave sequence numbers in
columns 73-80 of each table entry to help identify these
errors.
REFERENCES: CA MICS StorageMate Guide, Section 3.4.
+-----------------+
|S T G 0 0 0 1 8 |
+-----------------+
TEXT: GROUP NAME FROM THE FOLLOWING VOLUME GROUP TABLE
ENTRY EXCEEDS 8 CHARACTERS:
<entry>
PROCESSING WILL CONTINUE, BUT THIS STATEMENT
WILL BE IGNORED.
TYPE: Warning
REASON: The statement shown from your Volume Group Table
contained a syntax error. The volume group assignment
specified as the second operand on the statement exceeds the
maximum limit of eight characters. In the message text,
<entry> is replaced by the image of the entry that is in
error.
ACTION: Table processing will continue, but will issue a
U998 abend after all statements have been processed.
Correct the statement that is in error or remove it from the
Volume Group Table. You should leave sequence numbers in
columns 73-80 of each table entry to help identify these
errors.
REFERENCES: CA MICS StorageMate Guide, Section 3.4.
+-----------------+
|S T G 0 0 0 1 9 |
+-----------------+
TEXT: NO VALID STATEMENTS WERE FOUND WITHIN THE
SPECIFIED VOLUME GROUP TABLE.
THIS MAY BE CAUSED BY AN EMPTY TABLE OR BY
PREVIOUS ERRORS.
PROCESSING WILL BE ABORTED.
TYPE: Error
REASON: A Volume Group Table was specified for use by this
report, but no valid entries were found within it.
ACTION: Processing terminates with a U998 abend. Refer to
the Work Data Set and Volume Group Table names shown in a
previous message. Verify that the indicated table in the
indicated data set contains valid Volume Group entries.
Correct the errors or specify a different table name.
REFERENCES: CA MICS StorageMate Guide, Section 3.4.
+-----------------+
|S T G 0 0 0 2 0 |
+-----------------+
TEXT: DYNAMIC ALLOCATION FAILURE ATTEMPTING TO FREE
DDNAME: <ddname>
ERROR CODE: <error> / INFO CODE: <info>.
PROCESSING WILL CONTINUE, BUT THE DATA SET WILL
REMAIN ALLOCATED.
TYPE: Warning
REASON: An attempt to dynamically free one of the data sets
previously allocated by this facility was not successful.
In the message text, <ddname> represents the allocated
ddname for which the free was attempted, <error> and <info>
represent error and information codes from the MVS dynamic
allocation facility.
ACTION: Processing continues, but the data set allocated to
the ddname shown remains allocated. For a batch job, this
allocation will probably be freed at job termination. TSO
users may want to free the allocation manually using the TSO
FREE command.
REFERENCES: Refer to a list of dynamic allocation error
codes in IBM manuals or the ISPF tutorial.
+-----------------+
|S T G 0 0 0 2 1 |
+-----------------+
TEXT: WARNING: THE DATA SET GROUP TABLE JUST CREATED
CONTAINS <count> ENTRIES.
A TABLE THIS SIZE MAY CAUSE PERFORMANCE
PROBLEMS OR SAS MEMORY SIZE ERRORS.
EDIT THE TABLE TO REDUCE THE NUMBER OF ENTRIES
TO A MANAGEABLE NUMBER.
TYPE: Warning
REASON: The Data Set Group Table just created contains a
large number of entries. A large table may cause slow
report performance or may even cause SAS errors or memory
size errors when running reports. In the message text,
<count> is replaced by the number of table entries.
ACTION: You should reduce the table size by creating the
table again with different options or by editing the table
to combine entries.
REFERENCES: CA MICS StorageMate Guide, Section 3.5.
+-----------------+
|S T G 0 0 0 2 2 |
+-----------------+
TEXT: A VOLUME GROUP TABLE HAS BEEN CREATED IN MEMBER
<member> OF DATA SET <dsname>.
CREATED BY JOBNAME/USERID <user> ON <date> AT
<time>.
THE TABLE CONTAINS <count> UNIQUE VOLUME
ENTRIES.
TYPE: Information
REASON: This report created a new Volume Group Table in
your Work Data Set. In the message text, <dsname> indicates
the Work Data Set name, <member> represents the table name
created, <user> indicates the TSO user or batch job that
created the table, <date> and <time> indicate when the table
was created, and <count> indicates the number of non-comment
entries in the table.
ACTION: Remember to edit this table (using the CA MICS
StorageMate option facility) to tailor it to your needs
before attempting to use it.
REFERENCES: CA MICS StorageMate Guide, Section 3.4.
+-----------------+
|S T G 0 0 0 2 3 |
+-----------------+
TEXT: A DATA SET GROUP TABLE HAS BEEN CREATED IN MEMBER
<member> OF DATA SET <dsname>.
CREATED BY JOBNAME/USERID <user> ON <date> AT
<time>.
THE TABLE CONTAINS <count> UNIQUE DATA SET
GROUP ENTRIES.
TYPE: Information
REASON: This report created a new Data Set Group Table in
your Work Data Set. In the message text, <dsname> indicates
the Work Data Set name, <member> represents the table name
created, <user> indicates the TSO user or batch job that
created the table, <date> and <time> indicate when the table
was created, and <count> indicates the number of non-comment
entries in the table.
ACTION: Remember to edit this table (using the CA MICS
StorageMate option facility) to tailor it to your needs
before attempting to use it.
REFERENCES: CA MICS StorageMate Guide, Section 3.5.
+-----------------+
|S T G 0 0 0 2 4 |
+-----------------+
TEXT: VOLUME GROUP TABLE <dsname(table)> WAS SPECIFIED
FOR THIS INQUIRY.
TYPE: Information
REASON: As part of the report options for this inquiry a
Volume Group Table was specified, to be used in volume
grouping. In the message text, <table> represents the
specified table name, and <dsname> specifies the Work Data
Set in which the table should reside.
ACTION: None.
REFERENCES: CA MICS StorageMate Guide, Section 3.4.
+-----------------+
|S T G 0 0 0 2 5 |
+-----------------+
TEXT: DATA SET GROUP TABLE <dsname(table)> WAS
SPECIFIED FOR THIS INQUIRY.
TYPE: Information
REASON: As part of the report options for this inquiry a
Data Set Group Table was specified, to be used in data set
grouping. In the message text, <table> represents the
specified table name, and <dsname> specifies the Work Data
Set in which the table should reside.
ACTION: None.
REFERENCES: CA MICS StorageMate Guide, Section 3.5.
+-----------------+
|S T G 0 0 0 2 6 |
+-----------------+
TEXT: THE VOLUME PORTION OF THIS VOLUME GROUP TABLE
ENTRY IS MISSING A VOL= PREFIX:
<entry>
PROCESSING WILL CONTINUE, BUT THIS STATEMENT
WILL BE IGNORED.
TYPE: Warning
REASON: The statement shown from your Volume Group Table in
invalid. The volume portion of the statement does not
contain the required prefix of VOL=. In the message text,
<entry> is replaced by the image of the entry in error.
ACTION: Table processing will continue, but will issue a
U998 abend after all statements have been processed.
Correct the statement in error or remove it from the Volume
Group Table. You should leave sequence numbers in columns
73-80 of each table entry to help identify these errors.
REFERENCES: CA MICS StorageMate Guide, Section 3.4.
+-----------------+
|S T G 0 0 0 2 7 |
+-----------------+
TEXT: THE DSNAME PORTION OF THIS DATA SET GROUP TABLE
ENTRY IS MISSING A DSN= PREFIX:
<entry>
PROCESSING WILL CONTINUE, BUT THIS STATEMENT
WILL BE IGNORED.
TYPE: Warning
REASON: The statement shown from your Data Set Group Table
in invalid. The data set portion of the statement does not
contain the required prefix of DSN=. In the message text,
<entry> is replaced by the image of the entry in error.
ACTION: Table processing will continue, but will issue a
U998 abend after all statements have been processed.
Correct the statement in error or remove it from the Data
Set Group Table. You should leave sequence numbers in
columns 73-80 of each table entry to help identify these
errors.
REFERENCES: CA MICS StorageMate Guide, Section 3.5.
+-----------------+
|S T G 0 0 0 2 8 |
+-----------------+
TEXT: ONE OR MORE ERRORS WERE FOUND IN VOLUME GROUP
TABLE <dsname(table)>.
PROCESSING WILL BE ABORTED.
CORRECT THE ERRORS AND RETRY, OR SPECIFY A
DIFFERENT TABLE.
TYPE: Error
REASON: At least one syntax error occurred when processing
the entries in the Volume Group Table you specified as input
for this report. These errors should have been identified
with previous error messages. In the message text, <table>
is replaced with the table name you indicated, and <dsname>
represents the Work Data Set from which it was read.
ACTION: Processing aborts with a U998 abend. Correct the
errors identified in previous messages or specify a
different table name.
REFERENCES: CA MICS StorageMate Guide, Section 3.4.
+-----------------+
|S T G 0 0 0 2 9 |
+-----------------+
TEXT: ONE OR MORE ERRORS WERE FOUND IN DATA SET GROUP
TABLE <dsname(member)>.
PROCESSING WILL BE ABORTED.
CORRECT THE ERRORS AND RETRY, OR SPECIFY A
DIFFERENT TABLE.
TYPE: Error
REASON: At least one syntax error occurred when processing
the entries in the Data Set Group Table you specified as
input for this report. These errors should have been
identified with previous error messages. In the message
text, <table> is replaced with the table name you indicated,
and <dsname> represents the Work Data Set from which it was
read.
ACTION: Processing aborts with a U998 abend. Correct the
errors identified in previous messages or specify a
different table name.
REFERENCES: CA MICS StorageMate Guide, Section 3.5.
+-----------------+
|S T G 0 0 0 3 0 |
+-----------------+
TEXT: THE FOLLOWING SPACE MANAGEMENT SIMULATION VALUES
WERE SPECIFIED:
<values>
TYPE: Information
REASON: This message indicates the simulation values you
specified for this execution of the report. In the message
text, <values> is replaced by up to four keywords indicating
the simulation values that were specified. Those values for
which no value was coded will not appear in the message.
ACTION: None.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
|S T G 0 0 0 3 1 |
+-----------------+
TEXT: A SAMPLE JOBSTREAM TO CORRECT VOLUME PROBLEMS HAS
BEEN CREATED IN THE FOLLOWING DATA SET:
<dsname(member)>
PLEASE REVIEW THIS JOB CAREFULLY
BEFORE SUBMITTING IT FOR EXECUTION.
TYPE: Information
REASON: At your request, a jobstream has been created in
your Work Data Set that will correct some of the problems
detected by this report. In the message text, <dsname>
identifies your Work Data Set, and <member> identifies the
name of the member that was created.
ACTION: Review the specified member carefully, then use it
to correct some of the problems identified on the report.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
|S T G 0 0 0 3 2 |
+-----------------+
TEXT: A SAMPLE JOBSTREAM TO CORRECT DATA SET PROBLEMS
HAS BEEN CREATED IN THE FOLLOWING DATA SET:
<dsname(member)>
PLEASE REVIEW THIS JOB CAREFULLY
BEFORE SUBMITTING IT FOR EXECUTION.
TYPE: Information
REASON: At your request, a jobstream has been created in
your Work Data Set that will correct some of the problems
detected by this report. In the message text, <dsname>
identifies your Work Data Set, and <member> identifies the
name of the member that was created.
ACTION: Review the specified member carefully, then use it
to correct some of the problems identified on the report.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
|S T G 0 0 0 3 3 |
+-----------------+
TEXT: THE FOLLOWING PATTERN FILE WAS SPECIFIED AS INPUT
FOR THIS ANALYSIS:
<dsname(member)>
TYPE: Information
REASON: This message documents the name of the pattern file
you specified to be used as input for this simulation. In
the message text, <dsname> identifies the name of your Work
Data Set, and <member> identifies the name of the pattern
file that was used.
ACTION: None.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
|S T G 0 0 0 3 4 |
+-----------------+
TEXT: A SAMPLE ACS ROUTINE HAS BEEN CREATED IN MEMBER
<member> OF DATA SET <dsname>.
CREATED BY JOBNAME/USERID <user> ON <date> AT
<time>.
TYPE: Information
REASON: At your request, this report created a sample ACS
routine, and placed it in your Work Data Set. In the
message text, <dsname> indicates the Work Data Set name,
<member> represents the ACS routine created, <user>
indicates the TSO user or batch job that created the
routine, and <date> and <time> indicate when the routine was
created.
ACTION: Remember to inspect and modify this routine to
tailor it to your needs before attempting to use it as a
true ACS routine.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
|S T G 0 0 0 3 5 |
+-----------------+
TEXT: A LIST OF DASD-TO-TAPE CANDIDATES HAS BEEN CREATED
IN THE FOLLOWING DATA SET:
<dsname(member)>
TYPE: Information
REASON: At your request, this report created a list of data
sets that may be good candidates for movement from DASD to
tape, and placed it in your Work Data Set. In the message
text, <dsname> indicates the Work Data Set name, and
<member> represents the member name used to contain the
list.
ACTION: Inspect the created list and modify it to meet your
needs. Then use it to create jobstreams or user exits that
will move the desired data sets to tape.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
|S T G 0 0 0 3 6 |
+-----------------+
TEXT: THE FOLLOWING EXTERNAL TAPE FILE WAS SPECIFIED AS
INPUT FOR THIS ANALYSIS:
<dsname(TAPEDATA)>
THIS SAS DATA SET SHOULD CONTAIN TAPE-RELATED
DATA IN THE FORMAT DESCRIBED IN THE
DOCUMENTATION.
TYPE: Information
REASON: The inquiry you executed obtained tape-related
information from a non-CA MICS SAS data set that you
specified. This message documents the name of the data set
that you specified using the StorageMate and MICF options
facility. In the message text, <dsname> identifies the name
of the data set that was specified.
ACTION: None.
REFERENCES: CA MICS StorageMate Guide, Appendix C.
+-----------------+
|S T G 0 0 0 3 7 |
+-----------------+
TEXT: A LIST OF TAPE-TO-DASD CANDIDATES HAS BEEN
CREATED IN THE FOLLOWING DATA SET:
<dsname(member)>
TYPE: Information
REASON: At your request, this report created a list of data
sets that may be good candidates for movement from tape to
DASD, and placed it in your Work Data Set. In the message
text, <dsname> indicates the Work Data Set name, and
<member> represents the member name used to contain the
list.
ACTION: Inspect the created list and modify it to meet your
needs. Then use it to create jobstreams or user exits that
will move the desired data sets to DASD.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
|S T G 0 0 0 3 8 |
+-----------------+
TEXT: DATA SET NOT FOUND IN DATA SET GROUP TABLE:
<dsname>
TYPE: Information
REASON: For this inquiry, you specified that a Data Set
Group Table should be used for data set grouping. In the
process of doing that grouping, a data set was found that
did not match any of the entries in the table. In the
message text, <dsname> represents the name of the data set
that was not found in the table. This message is only
produced if you have set the &STGDEBUG option to a value of
Y (Yes).
ACTION: The specified data set is assigned a group name of
'(UNKNOWN)', and processing continues. Verify that the
table you specified (identified in a previous message) was
correct. Create a new table, or add entries for the
identified data set(s) to your existing table.
REFERENCES: CA MICS StorageMate Guide, Section 3.5.
+-----------------+
| S T G 0 0 0 3 9 |
+-----------------+
TEXT: SMSUSE KEYWORD FOUND WITHIN THE VOLUME ENTRIES FOR
THIS VOLUME GROUP TABLE.
IF THIS KEYWORD IS PRESENT, IT MUST PRECEDE ANY
VOLUME ENTRIES.
CORRECT THE TABLE AND RESTART THIS REPORT.
TYPE: Error
REASON: If an SMSUSE keyword appears in the Volume Group
Table, it must appear before any of the volume
entries.
ACTION: Processing terminates. Modify the Volume Group
Table to place the SMSUSE keyword before any
volume entries.
REFERENCES: CA MICS StorageMate Guide, Section 3.4.
+-----------------+
| S T G 0 0 0 4 0 |
+-----------------+
TEXT: INVALID SMSUSE KEYWORD FOUND WITHIN THIS VOLUME
GROUP TABLE.
VALID OPTIONS ARE SMSUSE=YES OR SMSUSE=NO.
CORRECT THE TABLE AND RESTART THIS REPORT.
TYPE: Error
REASON: An SMSUSE keyword with an invalid option was found
within the Volume Group Table you specified. The
keyword must be followed by an equal sign, and
then the word YES or NO. No spaces should
separate the keyword and its assigned value.
ACTION: Processing terminates. Edit the specified Volume
Group Table and change the SMSUSE keyword to meet
the standards specified above.
REFERENCES: CA MICS StorageMate Guide, Section 3.4.
+-----------------+
| S T G 0 0 0 4 1 |
+-----------------+
TEXT: THE MICF FILE FILTERING ROUTINE ENDED
WITH AN ERROR CODE OF <errcode>.
MAKE SURE THE FILES NEEDED BY THIS REPORT ARE
AVAILABLE IN THE UNIT DATABASES (DBIDS)
SPECIFIED.
REPORT EXECUTION IS TERMINATED.
TYPE: Error
REASON: The MICF routine called to drop uninstalled files
from the inquiry completed with an unexpected error. In the
message text, <errcode> is replaced by the error code
returned from the routine.
ACTION: Processing terminates. See Section 4.3 of this
guide to determine the files used by this report, and make
sure those files are available in the unit databases
(DBIDs) specified.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 4 2 |
+-----------------+
TEXT: A REQUIRED FILE (NAME = <file>) COULD NOT BE FOUND
IN THE SPECIFIED UNIT DATABASE ID LIST.
MODIFY THE UNIT DATABASE ID LIST TO INCLUDE THE
UNIT WHERE THIS FILE RESIDES.
REPORT EXECUTION IS TERMINATED.
TYPE: Error
REASON: One of the required files for this report could not
be found in the unit database ID list you supplied. In the
message text, <file> identifies the name of the file that
could not be located.
ACTION: Processing terminates. Verify that the required
files for this report are installed in a unit. Change the
database list to include the databases where required
files are located.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 4 3 |
+-----------------+
TEXT: A REQUIRED FILE WAS NOT FOUND IN ANY UNIT OF
THE SPECIFIED/DEFAULT UNIT DATABASE ID LIST.
DBID LIST: <dbidlst> / RETURN CODE: <retcode>.
REPORT EXECUTION IS TERMINATED.
TYPE: Error
REASON: A required file could not be located within the
unit database ID list that you supplied or were provided by
MICF as a default. In the message text, <dbidlst> is
replaced by the list of DBIDs, and <retcode> is the return
code from the MICF validation routine.
ACTION: Processing terminates. Make sure the required
files for the report you are executing are
installed in a CA MICS unit. Change the DBID
specification to include all required units.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 4 4 |
+-----------------+
TEXT: THE SPECIFIED/DEFAULT UNIT DATABASE ID LIST
DOES NOT CONTAIN ALL REQUIRED FILES FOR THIS
REPORT.
AN ATTEMPT WILL BE MADE TO CONSTRUCT A NEW UNIT
LIST USING ALL VALID UNITS IN THIS COMPLEX.
REPORT EXECUTION CONTINUES.
TYPE: Warning
REASON: The default or supplied unit database ID list for
this report did not include units containing all the files
needed for this report.
ACTION: MICF will attempt to build a new list from all
available units. If that attempt is successful, processing
will continue. Otherwise, additional messages will be
issued, and processing will fail.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 4 5 |
+-----------------+
TEXT: UNEXPECTED ERROR DETECTED BY THE MICF DBID
VALIDATION ROUTINE. RETURN CODE IS
<retcode>.
EXAMINE THE UNIT DATABASE ID LIST
SPECIFIED OR DEFAULTED FOR THIS REPORT.
REPORT EXECUTION IS TERMINATED.
TYPE: Error
REASON: The MICF routine used to validate unit databases
(DBIDs) encountered an unexpected error. In the message
text, <retcode> is replaced with the error code returned
from MICF.
ACTION: Processing terminates. Validate the unit database
ID list used by this report. Make sure it still represents
valid CA MICS units in your complex.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 4 6 |
+-----------------+
TEXT: THE FOLLOWING UNIT DATABASE ID LIST VALUES
CONTAIN NONE OF THE FILES USED BY THIS REPORT:
<dbidlst>.
THE SPECIFIED VALUES WILL BE IGNORED.
REPORT EXECUTION CONTINUES.
TYPE: Warning
REASON: One or more of the values in the unit database ID
list specified or defaulted for this report will be ignored,
as it contains none of the files used by the report. In the
message text, <dbidlst> contains the list of ignored DBIDs.
ACTION: Processing continues. If the ignored DBIDs were
supplied by you, remove them from the specification.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 4 7 |
+-----------------+
TEXT: THE FOLLOWING REQUIRED FILES WERE NOT FOUND IN ANY
OF THE DEFAULT/SPECIFIED UNITS: <filelist>.
CORRECT THE UNIT DATABASE ID LIST TO INCLUDE AT
LEAST ONE UNIT CONTAINING THE SPECIFIED FILES.
REPORT EXECUTION IS TERMINATED.
TYPE: Error
REASON: Files that were required for this report to execute
were not found in the unit database ID list that was
supplied or defaulted. In the message text, <filelist> is
replaced with the names of the file(s) that could not be
located.
ACTION: Processing terminates. Make sure the required
files are installed in at least one unit within
your complex. Modify the DBID specification for
the report.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 4 8 |
+-----------------+
TEXT: NO CYCLE VALUES HAVE BEEN SPECIFIED FOR THIS
REPORT.
SPECIFY AT LEAST ONE VALID CYCLE VALUE WHEN
SELECTING THIS REPORT FOR EXECUTION.
REPORT EXECUTION IS TERMINATED.
TYPE: Error
REASON: This message is issued by the MICF Production
Reporting option. A valid cycle value was not specified, or
could not be defaulted for this report.
ACTION: Processing terminates. Specify a valid cycle number
when selecting this report for MICF Production Reporting.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 4 9 |
+-----------------+
TEXT: THIS REPORT ALLOWS ONLY ONE CYCLE VALUE, BUT A
CYCLE RANGE HAS BEEN SPECIFIED OR DEFAULTED.
ONLY THE STARTING CYCLE NUMBER WILL BE USED.
REPORT EXECUTION CONTINUES.
TYPE: Warning
REASON: The report you are executing within the MICF
Production Reporting facility supports data from only one
cycle, but you have specified a range of cycles.
ACTION: The range is ignored, and only the first number
specified will be used. Change the selection specification
to contain only one cycle number.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 5 0 |
+-----------------+
TEXT: TEST CASE MEMBER <memname> FOUND IN THE TEST
RESULTS REPORT BUT NOT IN THE TEST CASE LIBRARY.
MAKE SURE THE REPORT FILE YOU SPECIFIED WAS
GENERATED FROM THE TEST CASE LIBRARY YOU
SPECIFIED.
REPORT EXECUTION CONTINUES, BUT THIS TEST CASE
WILL BE DROPPED FROM FURTHER REPORTS.
TYPE: Warning
REASON: A test case member identified in the ACS testing
output report could not be found in the test case library
you specified. In the message text, <memname> is replaced
by the member name that could not be located.
ACTION: The specified member is ignored, and will be
excluded from all future reports. Make sure the test case
library and the ACS output report file you specified to this
report represent the same data. The ACS output file should
have been produced from ACS testing using the test case
library you specified as input.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 5 1 |
+-----------------+
TEXT: THE FOLLOWING UNEXPECTED VALUE WAS FOUND IN THE
CYCLE REQUIREMENTS INDICATOR: <ind>.
MAKE SURE NO USER CHANGES HAVE BEEN MADE TO
THIS MICF INQUIRY, THEN CONTACT TECHNICAL
SUPPORT.
REPORT EXECUTION IS TERMINATED.
TYPE: Error
REASON: The report you attempted to execute under the MICF
Production Reporting facility had an invalid value in the
cycle requirements indicator. In the message text, <ind> is
replaced by the value found to be in error.
ACTION: Processing terminates. Make sure the inquiry you
attempted to execute has not been modified.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 5 2 |
+-----------------+
TEXT: RESULTS MAY NOT BE MEANINGFUL BECAUSE ONLY ONE
DATE WAS FOUND IN THE INPUT DATA FOR THIS REPORT.
CONSIDER RUNNING THIS REPORT AGAIN WITH A RANGE
OF INPUT CYCLES SPECIFIED.
REPORT EXECUTION CONTINUES.
TYPE: Warning
REASON: The report you have selected to execute is more
meaningful if data representing multiple days is processed,
but only one date was found in the input data you specified.
ACTION: Processing continues, but some of the output
produced may not be meaningful. Specify a range of input
cycles when requesting this report. If a range was
specified, make sure the requested cycles are present and
contain valid data.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 5 3 |
+-----------------+
TEXT: ONLY THE FIRST 36,000 DATA SETS WITH THE PREFIX
<dsnpref> WILL BE INCLUDED IN THE OUTPUT.
CONSIDER ALTERNATE INPUT OR FILTERING OPTIONS TO
REDUCE THE AMOUNT OF DATA SELECTED. REPORT
EXECUTION CONTINUES.
TYPE: Warning
REASON: The member name index structure used when building
ACS test cases has a limitation of 36,000 data sets with the
same 3-character prefix, and this limitation has been
exceeded. In the message text, <dsnpref> is the prefix
being processed when the error was detected.
ACTION: Processing continues, but all remaining data sets
with this prefix will be ignored. Change the selection,
filtering, or subsetting values you specified so that fewer
data sets are selected with this prefix. In most cases,
this number of test cases would be unmanageable anyway, and
should be reduced.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 5 4 |
+-----------------+
TEXT: A JOBSTREAM TO CREATE AND POPULATE AN ACS TEST
CASE LIBRARY HAS BEEN BUILT IN THE FOLLOWING DATA
SET:
<dsname(member)>
PLEASE REVIEW AND THEN SUBMIT THIS JOBSTREAM TO
BUILD THE ACS TEST CASE LIBRARY.
TYPE: Information
REASON: A jobstream has been successfully created and
placed in your Work Data Set. When this jobstream is
submitted, it will allocate an ACS test case library and
populate it with test cases. In the message text, <dsname>
represents your Work Data Set and <member> represents the
member created to contain the jobstream.
ACTION: Submit the specified member.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 5 5 |
+-----------------+
TEXT: THE FOLLOWING ACS TESTING REPORT FILE WAS
SPECIFIED AS INPUT FOR THIS ANALYSIS:
<dsname>(NONE)
TYPE: Information
REASON: This message documents the name of the ACS testing
output report data set that you specified as input to this
analysis. The data set should have been created by the ACS
testing facility, when testing a test case library you
previously built. In the message text, <dsname> is replaced
with the name of the report file you supplied.
ACTION: None.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 5 6 |
+-----------------+
TEXT: THE FOLLOWING ACS TEST CASE DATA SET WAS SPECIFIED
AS INPUT FOR THIS ANALYSIS:
<dsname>(ZZZINDEX)
THIS DATA SET SHOULD HAVE BEEN CREATED
PREVIOUSLY AND THEN SPECIFIED TO THE ISMF ACS
TESTING FACILITY.
TYPE: Information
REASON: Specifies the ACS test case library that was
specified as input to this report. The test case library is
needed to cross reference the material in the original test
cases with the information in the testing report. It is
important that these two data sets represent the same data.
In the message text, <dsname> represents the name of the
test case library you specified.
ACTION: None.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 5 7 |
+-----------------+
TEXT: THE REQUESTED ANALYSIS REPORT(S) CANNOT BE
PRODUCED BECAUSE THE STORAGE CLASS ACS ROUTINE WAS
NOT TESTED.
EXECUTE THE ISMF ACS TEST FACILITY AND SPECIFY
THAT THE STORAGE CLASS ACS ROUTINE
BE TESTED.
PROCESSING CONTINUES, BUT THIS REPORT WILL NOT
BE PRODUCED.
TYPE: Warning
REASON: You specified that one or more of the analysis
reports should be produced, yet SMS Storage Class was not
tested by the ACS testing facility. You have to have
specified Storage Class testing in the IBM ACS test facility
in order to produce the analysis reports, as they are based
on the results of the tests.
ACTION: Processing continues, but the analysis reports will
not be produced. Either invoke the ACS test facility again,
this time testing the storage class ACS routine, or do not
request the analysis reports.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 5 8 |
+-----------------+
TEXT: MORE THAN 9 ELEMENTS HAVE BEEN SPECIFIED FOR THE
SAME CHART IN PLOT GROUP: <grpid>.
RESPECIFY ELEMENT SELECTION SO THAT A MAXIMUM
OF 9 VALUES APPEAR IN ANY ONE GROUP.
PROCESSING CONTINUES; SOME ELEMENTS WILL BE
DROPPED FROM THE OUTPUT CHARTS.
TYPE: Warning
REASON: SAS permits a maximum of nine elements to be
plotted on the same graph, but you have exceeded that limit.
You specify elements that should be grouped together by
selecting them with the same alphabetic character on the
selection panel. In the message text, <grpid> represents
the character used to select the elements in this group.
ACTION: Processing continues, but all elements over the
stated limit will be ignored. Either specify fewer elements
to appear on this graph, or use a different selection
character for some elements, so they will appear on a
separate graph.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 0 0 5 9 |
+-----------------+
TEXT: <type> HSM SPACE REPORTING IS IN EFFECT FOR THIS
REPORT EXECUTION.
TYPE: Information
REASON: There are three different types of space values
available for data sets under the control of HSM, and this
message indicates which of those options will be used. In
the message text, <type> contains the value PRIMARY (space
allocated on primary volume), ACTUAL (space allocated on the
HSM volume), or ESTIMATED (space estimate if moved back to
primary). These options can be changed from the StorageMate
and MICF Options panel.
ACTION: None.
REFERENCES: CA MICS StorageMate Guide, Section 3.9.
+-----------------+
| S T G 0 0 0 6 0 |
+-----------------+
TEXT: MORE THAN 2 MEASUREMENT SAMPLES HAVE BEEN DETECTED
FOR AT LEAST ONE INPUT DATE.
DETAILED REPORTING WILL BE DONE FOR THIS REPORT
EXECUTION.
TYPE: Information
REASON: The report logic has detected more than two
measurement samples for at least one volume on at least one
day. This means that the CA MICS DASD Collector was
probably run multiple times on the same day to collect
storage information at different times throughout the day.
ACTION: The report logic is changed to use detailed
reporting mode, rather than daily mode. Each graph or
report will be used to represent one day with the different
measurement times being used as entries on each page. If
this is not what was desired, use different CA MICS data
without multiple measurements for the same day.
REFERENCES: CA MICS StorageMate Guide, Section 4.3.
+-----------------+
| S T G 0 2 0 0 0 |
+-----------------+
TEXT: "STGMSG"
TYPE: Informational
REASON: Multi-use generic message
ACTION: none.
REFERENCES: none.
+-----------------+
| S T G 0 2 0 1 0 |
+-----------------+
TEXT: "STGMSG"
TYPE: Informational
REASON: Multi-use generic message; future use
ACTION: none.
REFERENCES: none.
+-----------------+
| S T G 0 2 0 5 0 |
+-----------------+
TEXT: "PHASE": "_PGMTTL" BEGINNING EXECUTION...
TYPE: Informational
REASON: Processing phase _PGMTTL is starting
ACTION: none.
REFERENCES: none.
+-----------------+
| S T G 0 2 0 6 0 |
+-----------------+
TEXT: NEUGENTS MODEL "_FUNCT" PHASE BEGINNING...
TYPE: Informational
REASON: Neugents internal phase _FUNCT starting
ACTION: none.
REFERENCES: None.
+-----------------+
| S T G 0 2 0 7 0 |
+-----------------+
TEXT: "PHASE": "_PGMTTL" ENDING EXECUTION...
TYPE: Informational
REASON: Processing phase _PGMTTL ending.
ACTION: none.
REFERENCES: None.
+-----------------+
| S T G 0 2 0 7 5 |
+-----------------+
TEXT: "PHASE": "_PGMTTL" ABNORMALLY TERMINATING
TYPE: Error.
REASON: Processing _PGMTTL abnormally terminated.
ACTION: Neugents processing job will end.
REFERENCES: None.
+-----------------+
| S T G 0 2 0 8 0 |
+-----------------+
TEXT: "V1" FILE CONTAINS "N" RECORDS SELECTED FOR
PROCESSING.
TYPE: Informational
REASON: N records have been selected for processing
from file V1.
ACTION: none.
REFERENCES: None.
+-----------------+
| S T G 0 2 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 data value errors or unmatched
observations among files. Modeling results may
be impacted and should be examined in light of
this message.
ACTION: none.
REFERENCES: None.
+-----------------+
| S T G 0 2 0 9 0 |
+-----------------+
TEXT: NO FORECAST FILE ENTRY FOUND FOR "V1" ENTRY:
TYPE: Warning.
REASON: An observation in the Primary STG file was not
matched in the alternate input file.
ACTION: The original observation is not used in further
processing. See message STG02095 for additional
details.
REFERENCES: None.
+-----------------+
| S T G 0 2 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.
+-----------------+
| S T G 0 2 1 0 0 |
+-----------------+
TEXT: REPORT: "V1" BEING CURRENTLY GENERATED ON
DDNAME //"V1"
TYPE: Informational
REASON: Generation of report V1 has started.
ACTION: The report will be written out on DDNAME V1.
This message will only be issued if the MICF
environment is not being used. Message STG02105
will normally be issued instead.
REFERENCES: None.
+-----------------+
| S T G 0 2 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 out to the SASLIST DD.
REFERENCES: None.
+-----------------+
| S T G 0 2 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.
+-----------------+
| S T G 0 2 1 2 0 |
+-----------------+
TEXT: GRAPH: "V1" BEING CURRENTLY GENERATED ON DDNAME
//"V1"
TYPE: Informational
REASON: Generation of graph V1 has started.
ACTION: The graph will be written out on DDNAME V1.
This message will only be issued if the MICF
environment is not being used. Message STG02125
will normally be issued instead.
REFERENCES: None.
+-----------------+
| S T G 0 2 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 out to the SASLIST DD.
REFERENCES: None.
+-----------------+
| S T G 0 2 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.
+-----------------+
| S T G 0 2 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 not used in further
processing. Report "BADTRAIN" will contain a
list of observations that were dropped.
REFERENCES: None.
+-----------------+
| S T G 0 2 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 will be written out on DDNAME
MODLSTAT. This message will only be issued if
the MICF environment is not being used. Message
STG02165 will normally be issued instead.
REFERENCES: None.
+-----------------+
| S T G 0 2 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 out to the SASLIST DD.
REFERENCES: None.
+-----------------+
| S T G 0 2 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.
+-----------------+
| S T G 0 2 3 0 0 |
+-----------------+
TEXT: MACRO "PHASE" BEGINNING EXECUTION...
TYPE: Informational
REASON: Macro PHASE is starting execution. This macro
is used to provide linkage to Neugents
technology.
ACTION: None.
REFERENCES: None.
+-----------------+
| S T G 0 2 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.
ACTION: Neugents processing will be terminated.
REFERENCES: None.
+-----------------+
| S T G 0 2 3 2 0 |
+-----------------+
TEXT: MACRO GLOBALS MISSING REQUIRED OPERAND
"MODNAME", EXECUTION TERMINATING.
TYPE: Error.
REASON: An internal error has occured. This message
should never occur except during product
development.
ACTION: Processing terminates.
REFERENCES: None.
+-----------------+
| S T G 0 2 3 2 5 |
+-----------------+
TEXT: MACRO GLOBALS MISSING REQUIRED OPERAND
"MODTITLE", EXECUTION TERMINATING.
TYPE: Error
REASON: An internal error has occured. This message
should never occur except during product
development.
ACTION: Processing terminates.
REFERENCES: None.
+-----------------+
| S T G 0 2 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 STG02310 or STG02590.
ACTION: Neugents processing terminates.
REFERENCES: None.
+-----------------+
| S T G 0 2 3 9 5 |
+-----------------+
TEXT: MACRO "PHASE" ENDED WITH RETURN CODE "RC"
TYPE: Informational
REASON: The macro PHASE ended execution, with return
code RC.
ACTION: None.
REFERENCES: None.
+-----------------+
| S T G 0 2 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 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.
+-----------------+
| S T G 0 2 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 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.
+-----------------+
| S T G 0 2 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 will execute 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 will be written out on DDNAME MODLSTAT.
This message will only be issued if the MICF
environment is not being used. Message STG02435
will normally be issued instead.
REFERENCES: None.
+-----------------+
| S T G 0 2 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 will execute 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 out to the SASLIST DD.
REFERENCES: None.
+-----------------+
| S T G 0 2 5 0 0 |
+-----------------+
TEXT: OPEN ISSUED FOR "STD" FILE. RETURN CODE IS:
"RC"
TYPE: Informational
REASON: An open was issued for file with DDNAME "STD".
Such files are used by Neugents processing for
passing data between Neugents and the Capacity
Planning applications, or are required by USS
for internal use. The return code from open
processing is displayed as "RC".
ACTION: None.
REFERENCES: None.
+-----------------+
| S T G 0 2 5 1 0 |
+-----------------+
TEXT: OPEN FAILED FOR "STD" FILE. SYSTEM ERROR
MESSAGE IS "SYSMSG" EXECUTION TERMINATED.
TYPE: Error
REASON: An open was issued for file with DDNAME "STD".
Such files are used by Neugents processing for
passing data between Neugents and the Capacity
Planning 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 will cause
processing to be terminated.
ACTION: Review the specific system message for action.
REFERENCES: None.
+-----------------+
| S T G 0 2 5 9 0 |
+-----------------+
TEXT: ERROR TEXT FROM NEUGENTS PROCESSING "ERRMSG"
EXECUTION TERMINATED.
TYPE: Error
REASON: Any error text returned by USS in the STDERR
dataset will be displayed herein.
ACTION: Review specific error message for action.
REFERENCES: None.
