Appendix A: MESSAGES › Messages
Messages
This appendix lists all messages generated by the CA MICS
Batch and Operations Analyzer. Some messages are generated
during the processing of the control statements, while others
are caused by various conditions in the data found during the
processing. The messages are listed in ascending numerical
sequence and include the full text of the message, the type,
the reason for the message, appropriate user action, and
applicable references to documentation.
The following type codes are used to categorize the messages:
Information Designates a note that documents a CA MICS
SMF option or potentially important feature
in the data.
Warning Designates a condition in either the date or
the control statements that does not affect
the CA MICS Batch and Operation Analyzer's
operation, but that may lead to unexpected
results.
Error Designates that a problem has been
encountered with a control statement that
will prevent a successful run of the
component. Execution is stopped after all
control statements are processed.
The message text often includes references to information
that is contained in a control statement or values of
permanent or temporary variables created during CA MICS SMF
processing. In the description below, the message text
contains a word beginning with a percent sign (%), which
indicates that a value will be substituted into the text at
execution time.
+----------+
| SMF00005 |
+----------+
TEXT: DEVICE CLASS TABLE OVERFLOW IN UWUMAIOF ROUTINE.
THIS IS CAUSED BY A MALFORMATTED SMF TYPE 30
STEP/INTVL REC. YOU MUST DELETE THE BAD RECORD
BEFORE RESTARTING DAY030. EXAMINE THE SASLOG TO
SEE HOW MANY RECORDS WERE PROCESSED. THE LAST
RECORD PROCESSED IS INVALID. FORCE DAY030 TO
DELETE THE BAD RECORD WITH THE _USRSEL MACRO IN
sharedprefix.MICS.SOURCE(#BASEXIT):
IF ROUTINE="DYSMFFMT" AND _N_=nnn THEN SKIP_REC=1;
DO NOT FORGET TO REMOVE THE EXIT CODE AFTER DAY030
EXECUTES.
TYPE: Error
REASON: This message is generated when an SMF type 30
record is processed that has corrupted data
fields in the EXCP segments. CA MICS will abend
with a S0C4 if the corrupted record fields force
the internal DEVICE CLASS table to overflow.
ACTION: Examine the SASLOG and determine how many SMF
records were processed. This will be stated with
a SAS note:
Note: nnn records were read from the infile ...
Code the following statement in the _USRSEL macro
in sharedprefix.MICS.SOURCE(#BASEXIT):
IF ROUTINE='DYSMFFMT' AND _N_=nnn THEN
SKIP_REC=1;
Then restart DAY030. CA MICS will delete the bad
record and continue processing.
WARNING! After DAY030 completes, delete the
statement from the _USRSEL macro, or CA MICS will
continue to delete record number nnn during each
daily update.
REFERENCES: None
+----------+
| SMF00050 |
+----------+
TEXT: prefix.MICS.PARMS(SMFOPS)
SYSLISTACTION REJECT STATISTICS
ORGSYSID REJECTED
TYPE: Information
REASON: This message is generated during execution of the
daily update DAY030 step when data is encountered
from a system not listed in a SYSLIST statement,
and SYSLISTACTION REJECT is specified in
prefix.MICS.PARMS(SMFOPS).
ACTION: Review SYSLIST statements in
prefix.MICS.PARMS(SMFOPS), and add SYSIDs to a
SYSLIST statement if you want to prevent future
rejection of any data.
REFERENCES: Section 7.3.1
+----------+
| SMF00051 |
+----------+
TEXT: %VAR1 %VAR2
TYPE: Information
REASON: This message accompanies SMF00050. It contains
record counts by ORGSYSID.
ACTION: None
REFERENCES: Section 7.3.1
+----------+
| SMF00052 |
+----------+
TEXT: prefix.MICS.PARMS(SMFOPS)
SYSLISTACTION ABORT STATISTICS
DATA CONTAINING RECORDS PROCESSED BY THE SMF
ANALYZER HAVE BEEN ENCOUNTERED FROM AN ORGSYSID
NOT LISTED IN THE SYSLIST PARAMETER IN
prefix.MICS.PARMS(SMFOPS).
THE ORGSYSID VALUE(S) ARE:
TYPE: Information
REASON: This message is generated during execution of the
daily update DAY030 step when data is encountered
from a system not listed in a SYSLIST statement
and SYSLISTACTION ABORT is specified in
prefix.MICS.PARMS(SMFOPS).
ACTION: Review SYSLIST statements in
prefix.MICS.PARMS(SMFOPS) and add SYSIDs to a
SYSLIST statement if you want to prevent future
abends.
REFERENCES: Section 7.3.1
+----------+
| SMF00053 |
+----------+
TEXT: %VAR1
TYPE: Information
REASON: This message accompanies SMF00052. It contains
a list of ORGSYSIDs.
ACTION: None
REFERENCES: Section 7.3.1
+----------+
| SMF00054 |
+----------+
TEXT: TOTAL NUMBER OF EXCP SEGMENTS SKIPPED WHEN
SKIP_EXCP=1 IN USER EXIT USRDMAP: %VAR1
TYPE: Information
REASON: This message is issued when the SKIP_REC option
is used to skip EXCP segments in the SMF type 30
record. Provides a count of the number of EXCP
segments that were skipped.
ACTION: None
REFERENCES: None
+----------+
| SMF00055 |
+----------+
TEXT: THE BATWDA FILE HAS BEEN ACTIVATED IN THE DETAIL
TIMESPAN. THIS FILE HAS THE POTENTIAL OF BECOMING
VERY LARGE AND COULD CAUSE OUT OF SPACE
CONDITIONS IN YOUR DATABASE. MODIFY USER EXIT
USRSWDA USING THE SKIP_REC OPTION TO REDUCE THE
NUMBER OF OBSERVATIONS.
TYPE: Information
REASON: This message is issued when the BATWDA file is
activated in the DETAIL timespan.
ACTION: None
REFERENCES: None
+----------+
| SMF00122 |
+----------+
TEXT: NOT ALL SMF OPTIONS ARE DEFINED.
TYPE: Error
REASON: An OPTION statement keyword is missing in
shared.prefix.MICS.GENLIB(SMFGENIN).
ACTION: Add the missing keyword and rerun SMFCGEN.
REFERENCES: Section 7.3
+----------+
| SMF00123 |
+----------+
TEXT: %KEYWORD is an obsolete keyword in the OPTION
statement in
sharedprefix.MICS.GENLIB(SMFGENIN). %KEYWORD
was detected and is ignored.
TYPE: Warning
REASON: The displayed keyword is no longer supported in
sharedprefix.MICS.GENLIB(SMFGENIN). If this
OPTION statement keyword is detected, it is
ignored and processing continues.
ACTION: Delete the keyword and rerun SMFCGEN.
REFERENCES: Section 7.3
+----------+
| SMF00401 |
+----------+
TEXT: %LINE
>ERR> KEYWORD NOT RECOGNIZED. KEYWORD=%KEYWORD1
TYPE: Error
REASON: An invalid keyword was encountered in the line
printed with the error message.
ACTION: Correct the invalid keyword and rerun SMFPGEN.
REFERENCES: Section 7.3
+----------+
| SMF00402 |
+----------+
TEXT: %LINE
>ERR> SYSID NOT 1 TO 4 CHARACTERS IN LENGTH.
SYSID=%KEYWORD2
TYPE: Error
REASON: The SYSID specified was greater than four
characters in length in the SMFOPS OPTIONS or
DEFAULT statement.
ACTION: Correct the invalid SYSID in
prefix.MICS.PARMS(SMFOPS) and rerun SMFPGEN.
REFERENCES: Section 7.3.1.1
+----------+
| SMF00403 |
+----------+
TEXT: %LINE
>ERR> THE MAXIMUM OPTION/DEFAULT SYSID LIMIT HAS
BEEN REACHED. PLEASE CONTACT THE CA MICS SUPPORT
GROUP.
TYPE: Error
REASON: The number of unique SYSID specifications exceeds
the maximum allowed in the SMFOPS statements.
ACTION: Contact CA Technical Support for assistance.
REFERENCES: Section 7.3.1.1
+----------+
| SMF00405 |
+----------+
TEXT: %LINE
>ERR> SMFTSO OPTION MUST BE "SMFTSO" OR
"NOSMFTSO". "%VARX" IS INVALID.
TYPE: Error
REASON: The second option specified in a SMFOPS OPTIONS
statement must be "SMFTSO" or "NOSMFTSO." The
character string shown in the error message was
found instead.
ACTION: Correct the invalid OPTION specification in
prefix.MICS.PARMS(SMFOPS) and rerun SMFPGEN.
REFERENCES: Section 7.3.1.1
+----------+
| SMF00408 |
+----------+
TEXT: %LINE
>ERR> WDA OPTION MUST BE "WDA" OR "NOWDA".
"%VARX" IS INVALID.
TYPE: Error
REASON: The fifth option specified in a SMFOPS OPTIONS
statement must be "WDA" or "NOWDA." The
character string shown in the error message was
found instead.
ACTION: Correct the invalid OPTION specification in
prefix.MICS.PARMS(SMFOPS) and rerun SMFPGEN.
REFERENCES: Section 7.3.1.1
+----------+
| SMF00410 |
+----------+
TEXT: %LINE
>ERR> THE DEFAULT BLKSIZE FOR "%VARX" IS NOT
SPECIFIED.
TYPE: Error
REASON: The SMFOPS DEFAULT statement printed with the
error message was missing at least one default
blocksize.
ACTION: Add all of the required default blocksizes in the
DEFAULT statement in prefix.MICS.PARMS(SMFOPS)
and rerun SMFPGEN.
REFERENCES: Section 7.3.1.1
+----------+
| SMF00411 |
+----------+
TEXT: %LINE
>ERR> THE DEFAULT BLKSIZE FOR "%VARX" IS NOT
NUMERIC. VALUE=%VARX2
TYPE: Error
REASON: The SMFOPS DEFAULT statement printed with the
error message had a non-numeric blocksize
specified.
ACTION: Correct the invalid blocksize in the DEFAULT
statement in prefix.MICS.PARMS(SMFOPS) and rerun
SMFPGEN.
REFERENCES: Section 7.3.1.1
+----------+
| SMF00412 |
+----------+
TEXT: %LINE
>ERR> THE DEFAULT BLKSIZE FOR "%VARX" IS NOT IN
RANGE 1 - %VARX2. VALUE=%VALUE
TYPE: Error
REASON: The SMFOPS DEFAULT statement printed with the
error message has an invalid blocksize. The
default blocksize specified for the device
category printed with the error message was not
within the acceptable range.
ACTION: Correct the invalid blocksize in the DEFAULT
statement in prefix.MICS.PARMS(SMFOPS) and rerun
SMFPGEN.
REFERENCES: Section 7.3.1.1
+----------+
| SMF00413 |
+----------+
TEXT: >ERR> REQUIRED STATEMENT NOT FOUND. STATEMENT
TYPE=OPTIONS
>ERR> REQUIRED STATEMENT NOT FOUND. STATEMENT
TYPE=DEFAULT
TYPE: Error
REASON: The SMFOPS member of the PARMS library must
contain at least one OPTIONS and one DEFAULT
statement.
ACTION: Add the required OPTION and DEFAULT statements to
prefix.MICS.PARMS(SMFOPS) and rerun SMFPGEN.
REFERENCES: Section 7.3.1.1
+----------+
| SMF00414 |
+----------+
TEXT: OPTIONS STATEMENT NOT FOUND FOR ORGSYSID %VARX.
GLOBAL SETTINGS ARE BEING USED.
TYPE: Information
REASON: The OPTIONS statement for the ORGSYSID printed
with the message was not found. The GLOBAL
OPTIONS parameter values are used. This message
is only displayed when a DEFAULT statement is
coded for a ORGSYSID without an OPTIONS statement
in prefix.MICS.PARMS(SMFOPS) for a ORGSYSID.
ACTION: None
REFERENCES: Section 7.3.1.1
+----------+
| SMF00415 |
+----------+
TEXT: DEFAULT STATEMENT NOT FOUND FOR ORGSYSID %VARX.
DEFAULT SETTINGS ARE BEING USED.
TYPE: Information
REASON: The DEFAULT statement for the ORGSYSID printed
with the message was not found. The GLOBAL
DEFAULT parameter values are used. This message
is only displayed when an OPTIONS statement is
coded for a ORGSYSID without a DEFAULT statement
in prefix.MICS.PARMS(SMFOPS) for a ORGSYSID.
ACTION: None
REFERENCES: Section 7.3.1.1
+----------+
| SMF00416 |
+----------+
TEXT: >>>>> ERROR(S) ENCOUNTERED IN SMFOPS PARM
DEFINITIONS
>>>>> SMFPGEN ABORTED
>>>>> CORRECT ERROR(S) AND EXECUTE AGAIN
TYPE: Error
REASON: At least one error was encountered during
validation of the SMFOPS member of the PARMS
library.
ACTION: Correct the errors listed in other messages in
the MICSLOG and rerun SMFPGEN.
REFERENCES: Section 7.3.1
+----------+
| SMF00417 |
+----------+
TEXT: >>>>> SMFOPS VALIDATION COMPLETED SUCCESSFULLY
TYPE: Information
REASON: This message is generated at the successful
completion of the SMFOPS PARMS member validation
process.
ACTION: None
REFERENCES: Section 7.3.1
+----------+
| SMF00418 |
+----------+
TEXT: >>>>> VALIDATING PARM MEMBER JOBGROUP
TYPE: Information
REASON: This message is generated when the validation of
prefix.MICS.PARMS(JOBGROUP) begins.
ACTION: None
REFERENCES: Section 7.3.2
+----------+
| SMF00419 |
+----------+
TEXT: %LINE
>ERR> KEYWORD IS NOT RECOGNIZED. KEYWORD=%VARX
TYPE: Error
REASON: While validating a "TURNTIME" statement
definition in the JOBGROUP member of the PARMS
library, an unrecognized keyword was encountered.
ACTION: Correct the keyword in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.2
+----------+
| SMF00420 |
+----------+
TEXT: %LINE
>ERR> NO TURNAROUND TIME DATA ELEMENTS
SPECIFIED
TYPE: Error
REASON: The required turnaround time values are missing
from the JOBGROUP member statement printed with
the error message.
ACTION: Add turnaround time values to the statement in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.2
+----------+
| SMF00421 |
+----------+
TEXT: %LINE
>ERR> NO ENDING DEADLINE TIME DATA ELEMENT
SPECIFIED
TYPE: Error
REASON: The "DEADLINE" turnaround time specification
requires two timestamp indicators. The second
timestamp indicator is missing in the line
printed with the error statement.
ACTION: Add the missing timestamp indicator to the
DEADLINE statement in prefix.MICS.PARMS(JOBGROUP)
and rerun SMFPGEN.
REFERENCES: Section 7.3.2.2
+----------+
| SMF00422 |
+----------+
TEXT: >ERR> TURNAROUND TIME IS NOT NUMERIC. VALUE=%VARN
TYPE: Error
REASON: The turnaround time element indicators in the
"TURNTIME" statement must be numeric. The value
printed with the error statement was found
instead.
ACTION: Correct the non-numeric time element in the
DEADLINE statement in prefix.MICS.PARMS(JOBGROUP)
and rerun SMFPGEN.
REFERENCES: Section 7.3.2.2
+----------+
| SMF00423 |
+----------+
TEXT: %LINE
>ERR> TURNAROUND TIME NOT IN RANGE 1 TO 8.
VALUE=%VARN
TYPE: Error
REASON: The turnaround timestamp indicator values must
be in the range from 1 to 8. The value printed
with the error message was found instead.
ACTION: Correct the invalid indicator value in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.2
+----------+
| SMF00424 |
+----------+
TEXT: %LINE
>ERR> STARTING VALUE FOR DEADLINE MUST BE 1, 2,
OR 3. VALUE=%VARN
TYPE: Error
REASON: The timestamp indicator specified for the "IN
BY" value of a "DEADLINE" JOBGROUP must be 1, 2,
or 3. The value printed with the error message
was found instead.
ACTION: Correct the invalid indicator value in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.2
+----------+
| SMF00425 |
+----------+
TEXT: %LINE
>ERR> ENDING VALUE FOR DEADLINE MUST BE 3, 6,
7, OR 8. VALUE=%VARN
TYPE: Error
REASON: The timestamp indicator specified for the "OUT
BY" value of a "DEADLINE" JOBGROUP must be 3, 6,
7, or 8. The value printed with the error
message was found instead.
ACTION: Correct the invalid indicator value in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.2
+----------+
| SMF00426 |
+----------+
TEXT: %LINE
>ERR> ONLY A STARTING AND ENDING VALUE MAY BE
SPECIFIED FOR DEADLINE JOBGROUPS
TYPE: Error
REASON: Only two timestamp indicators are allowed in the
statement defining a "DEADLINE" JOBGROUP. At
least three values were used in the statement
printed with the error message.
ACTION: Remove the extra timestamp value in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.2
+----------+
| SMF00427 |
+----------+
TEXT: %LINE
>ERR> MORE THAN 8 TIME ELEMENTS SPECIFIED
TYPE: Error
REASON: More than eight time intervals were specified in
the JOBGROUP "TURNTIME" statement. A maximum of
eight intervals are allowed.
ACTION: Correct the "TURNTIME" statement in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.2
+----------+
| SMF00428 |
+----------+
TEXT: %LINE
>ERR> DEADLINE VALUES MUST BE ASCENDING
TYPE: Error
REASON: The "DEADLINE" timestamp values indicated in the
"TURNTIME" statement were not in ascending order.
ACTION: Put the "DEADLINE" timestamp values in ascending
order in prefix.MICS.PARMS(JOBGROUP) and rerun
SMFPGEN.
REFERENCES: Section 7.3.2.2
+----------+
| SMF00429 |
+----------+
TEXT: %LINE
>ERR> DUPLICATE TURNTIME STATEMENTS FOUND
TYPE: Error
REASON: Duplicate "TURNTIME" statements were found in the
JOBGROUP member of the PARMS library.
ACTION: Remove or change the duplicate entry in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.2
+----------+
| SMF00430 |
+----------+
TEXT: %LINE
>ERR> TARGET TIME MUST BE EXPRESSED IN MINUTES,
RANGING FROM 1 TO 10080 (7 DAYS). VALUE=%VALUE
TYPE: Error
REASON: The turnaround target time in a GROUP definition
statement was out of the acceptable range of 1 to
10080 minutes.
ACTION: Correct the out-of-range target time value in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.3
+----------+
| SMF00431 |
+----------+
TEXT: %LINE
>ERR> TARGET TIMES MUST BE GREATER THAN THE
TARGET TIME SPECIFIED FOR THE PREVIOUS JOB
GROUP DEFINITION
>ERR> TARGET=%VALUE, LAST=%LASTTM
TYPE: Error
REASON: The GROUP statements in the JOBGROUP member must
be coded with the quickest turnaround time first,
followed by the next fastest, etc., with the
longest turnaround GROUP specified last. The
line printed with the error message had a
turnaround target time less than the previously
processed GROUP.
ACTION: Make the turnaround target time values fall in
ascending order in the GROUP statements defined
in prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.3
+----------+
| SMF00432 |
+----------+
TEXT: %LINE
>NOTE> TARGET TIME IS EQUAL TO PREVIOUS TARGET
TIME
TYPE: Information
REASON: The turnaround target time was equivalent for two
consecutive GROUP statements.
ACTION: Check to make sure this is what was intended in
prefix.MICS.PARMS(JOBGROUP). If not, correct
the invalid target time and rerun SMFPGEN.
Otherwise, no action is necessary.
REFERENCES: Section 7.3.2.3
+----------+
| SMF00433 |
+----------+
TEXT: %LINE
>ERR> DEADLINE SUBMIT HOUR MUST BE NUMERIC,
WITH VALUE RANGING FROM 00 TO 23. VALUE=%VALUE
TYPE: Error
REASON: The JOBGROUP "DEADLINE" statement "submit by"
hour was out of range. Must be 0 to 23.
ACTION: Correct the out-of-range "submit by" hour in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.4
+----------+
| SMF00434 |
+----------+
TEXT: %LINE
>ERR> DEADLINE SUBMIT MINUTE MUST BE NUMERIC,
WITH VALUE RANGING FROM 00 TO 59. VALUE=%VALUE
TYPE: Error
REASON: The JOBGROUP "DEADLINE" statement "submit by"
minute was out of range. Must be 0 to 59.
ACTION: Correct the out-of-range "submit by" minute in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.4
+----------+
| SMF00435 |
+----------+
TEXT: %LINE
>ERR> DEADLINE PROCESS HOUR MUST BE NUMERIC,
WITH VALUE RANGING FROM 00 TO 23. VALUE=%VALUE
TYPE: Error
REASON: The JOBGROUP "DEADLINE" statement "complete by"
hour was out of range. Must be 0 to 23.
ACTION: Correct the out-of-range "complete by" hour in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.4
+----------+
| SMF00436 |
+----------+
TEXT: %LINE
>ERR> DEADLINE PROCESS MINUTE MUST BE NUMERIC,
WITH VALUE RANGING FROM 00 TO 59. VALUE=%VALUE
TYPE: Error
REASON: The JOBGROUP "DEADLINE" statement "complete by"
minute was out of range. Must be 0 to 59.
ACTION: Correct the out-of-range "complete by" minute in
in prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.2.4
+----------+
| SMF00437 |
+----------+
TEXT: %LINE
>ERR> PURGE TIME SPECIFIED MUST BE GREATER THAN
ASSOCIATED SUBMIT TIME, WHEN NUMBER OF DAYS
SPANNED IS 1
TYPE: Error
REASON: This message is generated because the "submit by"
time is later than the "done by" time for the
"DEADLINE" statement printed with the error
message. The number of days spanned is 1,
meaning that both times apply to the same day.
ACTION: Either increase days spanned or make the submit
time earlier than the end time on the "DEADLINE"
statement in prefix.MICS.PARMS(JOBGROUP); then
rerun SMFPGEN.
REFERENCES: Section 7.3.2.4
+----------+
| SMF00438 |
+----------+
TEXT: %LINE
>ERR> DEADLINE DAYS SPANNED MUST BE NUMERIC.
WITH VALUE RANGING FROM 0 TO 7. VALUE=%VALUE
TYPE: Error
REASON: The "DEADLINE" JOBGROUP statement printed with
the error message has an invalid days-spanned
value. Days spanned must be numeric with a value
from 0 to 7.
ACTION: Correct the invalid days-spanned value on the
"DEADLINE" statement in
prefix.MICS.PARMS(JOBGROUP); then rerun SMFPGEN.
REFERENCES: Section 7.3.2.4
+----------+
| SMF00439 |
+----------+
TEXT: %LINE
>ERR> JOB GROUP NUMBER IS NOT NUMERIC.
VALUE=%TOKEN2
TYPE: Error
REASON: The JOBGROUP statement printed with the error
message has a non-numeric job group number.
ACTION: Correct the non-numeric job group number on the
statement printed with the error message from
prefix.MICS.PARMS(JOBGROUP); then rerun SMFPGEN.
REFERENCES: Section 7.3.2.4
+----------+
| SMF00440 |
+----------+
TEXT: %LINE
>ERR> JOB GROUP NUMBER NOT IN RANGE 1 TO 149.
VALUE=%VALUE
TYPE: Error
REASON: The "GROUP" statement uses job group numbers
that range from 1-149. The "GROUP" statement
printed with the error message has a job group
number out of range.
ACTION: Use a job group number within the range of 1-149
on the "GROUP" statement in
prefix.MICS.PARMS(JOBGROUP); then rerun SMFPGEN.
REFERENCES: Section 7.3.2.3
+----------+
| SMF00441 |
+----------+
TEXT: %LINE
>ERR> JOB GROUP NUMBER NOT IN RANGE 150 TO 179.
VALUE=%VALUE
TYPE: Error
REASON: The "DEADLINE" statement uses job group numbers
that range from 150-179. The "DEADLINE"
statement printed with the error message has a
job group number out of range.
ACTION: Use a job group number within the range of 150-
179 on the "DEADLINE" statement in
prefix.MICS.PARMS(JOBGROUP); then rerun SMFPGEN.
REFERENCES: Section 7.3.2.4
+----------+
| SMF00442 |
+----------+
TEXT: %LINE
>ERR> JOB GROUP NUMBER NOT IN RANGE 180 TO 195.
VALUE=%VALUE
TYPE: Error
REASON: The "OPEN" statement uses job group numbers that
range from 180-195. The "OPEN" statement printed
with the error message has a job group number out
of that range.
ACTION: Use a job group number within the range of 180-
195 on the "OPEN" statement in
prefix.MICS.PARMS(JOBGROUP); then rerun SMFPGEN.
REFERENCES: Section 7.3.2.5
+----------+
| SMF00443 |
+----------+
TEXT: %LINE
>ERR> %VALUEN IS NOT NUMERIC. VALUE=%VALUEC
TYPE: Error
REASON: The value printed with the error message must be
numeric.
ACTION: Correct the invalid value and rerun SMFPGEN.
REFERENCES: Section 7.3.2
+----------+
| SMF00444 |
+----------+
TEXT: %LINE
>ERR> JOB GROUP SERVICE FACTOR IS REQUIRED
BEFORE THE TITLE
TYPE: Error
REASON: The JOBGROUP service factor is missing in the
line printed with the error message.
ACTION: Add the service factor to the statement in
prefix.MICS.PARMS(JOBGROUP); then rerun SMFPGEN.
REFERENCES: Section 7.3.2
+----------+
| SMF00445 |
+----------+
TEXT: %LINE
>ERR> JOB GROUP SERVICE FACTOR IS NOT NUMERIC.
VALUE=%VALUEC
TYPE: Error
REASON: The JOBGROUP service factor is non-numeric in the
line printed with the error message.
ACTION: Correct the invalid service factor on the
statement in prefix.MICS.PARMS(JOBGROUP); then
rerun SMFPGEN.
REFERENCES: Section 7.3.2
+----------+
| SMF00446 |
+----------+
TEXT: %LINE
>ERR> JOB GROUP SERVICE FACTOR IS NOT IN RANGE
.1 TO 99.9. VALUE=%JGPFCTR
TYPE: Error
REASON: The JOBGROUP service factor is out-of-range in
the line printed with the error message. The
range is from .1 to 99.9.
ACTION: Correct the out-of-range service factor on the
statement in prefix.MICS.PARMS(JOBGROUP); then
rerun SMFPGEN.
REFERENCES: Section 7.3.2
+----------+
| SMF00447 |
+----------+
TEXT: %LINE
>ERR> JOB GROUP NAME IS NOT ENCLOSED IN QUOTES
TYPE: Error
REASON: The JOBGROUP descriptive name must be enclosed in
quotes.
ACTION: Enclose the descriptive name in quotes on the
statement in prefix.MICS.PARMS(JOBGROUP); then
rerun SMFPGEN.
REFERENCES: Section 7.3.2
+----------+
| SMF00448 |
+----------+
TEXT: %LINE
>ERR> JOB GROUP PREVIOUSLY DEFINED. NAME=%JG
TYPE: Error
REASON: Duplicate JOBGROUP numbers detected. Each
statement must use a unique JOBGROUP number.
ACTION: Change or delete the duplicate JOBGROUP number on
the statement in prefix.MICS.PARMS(JOBGROUP);
then rerun SMFPGEN.
REFERENCES: Section 7.3.2
+----------+
| SMF00449 |
+----------+
TEXT: >ERR> ALL FOUR TURNTIME COMBINATIONS MUST BE
DEFINED:
>>>>> TURNTIME STANDARD LOCAL
>>>>> TURNTIME STANDARD REMOTE
>>>>> TURNTIME DEADLINE LOCAL
>>>>> TURNTIME DEADLINE REMOTE
TYPE: Error
REASON: All four "TURNTIME" statements must be defined in
the JOBGROUP PARMS member. Either one or more
"TURNTIME" statements is missing or in error.
ACTION: Include all four "TURNTIME" statements in
prefix.MICS.PARMS(JOBGROUP); then rerun SMFPGEN.
REFERENCES: Section 7.3.2.2
+----------+
| SMF00450 |
+----------+
TEXT: >WARN> NO GROUP STATEMENTS WERE FOUND IN THE
JOBGROUP PARM MEMBER
TYPE: Warning
REASON: This warning is generated because no GROUP
statements were encountered while processing the
JOBGROUP PARM member.
ACTION: None, if no "GROUP" statements were intended.
Otherwise, add "GROUP" statements as needed to
prefix.MICS.PARMS(JOBGROUP); then rerun SMFPGEN.
REFERENCES: Section 7.3.2.3
+----------+
| SMF00451 |
+----------+
TEXT: >>>>> ERROR(S) ENCOUNTERED IN JOBGROUP PARM
DEFINITIONS
>>>>> #JOBGP SAS MACRO GENERATION ABORTED
>>>>> CORRECT ERROR(S) AND EXECUTE AGAIN
TYPE: Error
REASON: This message is generated at the completion of
validation of the JOBGROUP PARM member. At least
one fatal error was encountered.
ACTION: Fix the errors shown in the other messages
printed in the MICSLOG for
prefix.MICS.PARMS(JOBGROUP); then rerun SMFPGEN.
REFERENCES: Section 7.3.2
+----------+
| SMF00452 |
+----------+
TEXT: >>>>> JOBGROUP VALIDATION COMPLETED SUCCESSFULLY
TYPE: Information
REASON: This message is generated at the successful
completion of the prefix.MICS.PARMS(JOBGROUP)
member validation.
ACTION: None
REFERENCES: Section 7.3.2
+----------+
| SMF00453 |
+----------+
TEXT: >ERR> TURNAROUND TIME VALUES 4, 5, AND 6 CANNOT BE
>ERR> SPECIFIED WITH TURNAROUND TIME VALUE 9.
>ERR> 4, 5, AND 6 ARE MUTUALLY EXCLUSIVE WITH 9.
TYPE: Error
REASON: Time intervals 4, 5, and 6 are mutually exclusive
with time interval 9 in the JOBGROUP "TURNTIME"
statement.
ACTION: Correct the "TURNTIME" statement in
prefix.MICS.PARMS(JOBGROUP) and rerun SMFPGEN.
REFERENCES: Section 7.3.5
+----------+
| SMF00454 |
+----------+
TEXT: %LINE
>ERR> SYSID GREATER THAN FOUR CHARACTERS IN
LENGTH
TYPE: Error
REASON: The SYSID specified in the line printed with the
error message was greater than four characters
in length.
ACTION: Correct the invalid SYSID and rerun SMFPGEN
REFERENCES: Sections 7.3.5, 7.3.6
+----------+
| SMF00455 |
+----------+
TEXT: %LINE
>ERR> DEFAULT STATEMENT HAS MORE THAN 5 BLOCKSIZE
PARAMETERS SPECIFIED
TYPE: Error
REASON: The number of blocksize values specified in the
printed line with the error message was greater
than five.
ACTION: Carefully review the line(s) in error and delete
the extraneous parameter.
REFERENCES: Sections 7.3.1.1
+----------+
| SMF00470 |
+----------+
TEXT: %LINE
>ERR> SPOOL FILE HOLD CYCLES "SPLLIMIT" IS NOT
NUMERIC
>ERR> "%VARX" IS INVALID
TYPE: Error
REASON: The SPLLIMIT option statement requires a numeric
operand in the range from 0 to 10. The non-
numeric operand printed with the error statement
was found instead.
ACTION: Add a numeric operand after the SPLLIMIT
statement and rerun SMFPGEN.
REFERENCES: Section 7.3.1.3
+----------+
| SMF00471 |
+----------+
TEXT: %LINE
>ERR> SPOOL FILE HOLD CYCLES "SPLLIMIT" MUST BE A
NUMBER
>ERR> FROM 0 TO 10, "%VARX" IS OUT OF RANGE.
TYPE: Error
REASON: The SPLLIMIT option statement requires a numeric
operand in the range from 0 to 10. The value
printed with the error statement was out of
range.
ACTION: Change the SPLLIMIT operand to a number within
the range 0 to 10 and rerun SMFPGEN.
REFERENCES: Section 7.3.1.3
+----------+
| SMF00472 |
+----------+
TEXT: %LINE
>ERR> ACCOUNTING HOLD FILE CYCLES "SFHLIMIT" MUST
BE A NUMBER
>ERR> FROM 0 TO 20, "%VARX" IS OUT OF
RANGE.
TYPE: Error
REASON: The SFHLIMIT option statement requires a numeric
operand in the range from 0 to 20. The value
printed with the error statement was out of
range.
ACTION: Change the SPLLIMIT operand to a number within
the range 0 to 20 and rerun SMFPGEN.
REFERENCES: Section 7.3.1.4
+----------+
| SMF00473 |
+----------+
TEXT: %LINE
>ERR> ACCOUNTING HOLD FILE CYCLES "SFHLIMIT" IS NOT
NUMERIC
>ERR> "%VARX" IS INVALID
TYPE: Error
REASON: The SFHLIMIT option statement requires a numeric
operand in the range from 0 to 20. The non-
numeric operand printed with the error statement
was found instead.
ACTION: Add a numeric operand after the SFHLIMIT
statement and rerun SMFPGEN.
REFERENCES: Section 7.3.1.4
+----------+
| SMF00474 |
+----------+
TEXT: >>>>> "SPLLIMIT" OPTION CARD MISSING
>>>>> DEFAULT OF "SPLLIMIT 0" USED
TYPE: Information
REASON: This message is generated when SMFOPS does not
contain an SPLLIMIT option statement. The
message displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.3
+----------+
| SMF00475 |
+----------+
TEXT: >>>>> "SFHLIMIT" OPTION CARD MISSING
>>>>> DEFAULT OF "SFHLIMIT 0" USED
TYPE: Information
REASON: This message is generated when SMFOPS does not
contain an SFHLIMIT option statement. The
message displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.4
+----------+
| SMF00476 |
+----------+
TEXT: >>>>> "NJEJOB"/"NONJEJOB" OPTION CARD MISSING
>>>>> DEFAULT OF "NONJEJOB" USED
TYPE: Information
REASON: This message is generated when SMFOPS does not
contain an NJEJOB/NONJEJOB option statement. The
message displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.6
+----------+
| SMF00477 |
+----------+
TEXT: >>>>> "LATEJOB"/"NOLATEJOB" OPTION CARD MISSING
>>>>> DEFAULT OF "NOLATEJOB" USED
TYPE: Information
REASON: This message is generated when SMFOPS does not
contain an LATEJOB/NOLATEJOB option statement.
The message displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.5
+----------+
| SMF00478 |
+----------+
TEXT: >>>>> "SUSPENDNJE"/"NOSUSPENDNJE" OPTION CARD
MISSING
>>>>> DEFAULT OF "SUSPENDNJE" USED
TYPE: Information
REASON: This message is generated when SMFOPS does not
contain a SUSPENDNJE/NOSUSPENDNJE option
statement. The message displays the default
value used.
ACTION: None
REFERENCES: Section 7.3.1.5
+----------+
| SMF00479 |
+----------+
TEXT: >ERR> MULTIPLE "SPLLIMIT" OPTION CARDS FOUND
>ERR> ONLY ONE "SPLLIMIT" OPTION CARD ALLOWED,
%VARX CARDS FOUND
TYPE: Error
REASON: Only one SPLLIMIT option statement is allowed.
More than one SPLLIMIT option statement was
encountered. The number of SPLLIMIT option
statements found is printed in the error message.
ACTION: Delete the extra SPLLIMIT statements and rerun
SMFPGEN.
REFERENCES: Section 7.3.1.3
+----------+
| SMF00480 |
+----------+
TEXT: >ERR> MULTIPLE "SFHLIMIT" OPTION CARDS FOUND
>ERR> ONLY ONE "SFHLIMIT" OPTION CARD ALLOWED,
%VARX CARDS FOUND
TYPE: Error
REASON: Only one SFHLIMIT option statement is allowed.
More than one SFHLIMIT option statement was
encountered. The number of SFHLIMIT option
statements found is printed in the error message.
ACTION: Delete the extra SFHLIMIT statements and rerun
SMFPGEN.
REFERENCES: Section 7.3.1.4
+----------+
| SMF00481 |
+----------+
TEXT: >ERR> MULTIPLE "NJEJOB"/"NONJEJOB" OPTION CARDS
FOUND
>ERR> ONLY ONE "NJEJOB"/"NONJEJOB" OPTION CARD
ALLOWED, %VARX CARDS FOUND
TYPE: Error
REASON: Only one NJEJOB/NONJEJOB option statement is
allowed. More than one NJEJOB/NONJEJOB option
statement was encountered. The number of
NJEJOB/NONJEJOB option statements found is
printed in the error message.
ACTION: Delete the extra NJEJOB/NONJEJOB statements and
rerun SMFPGEN.
REFERENCES: Section 7.3.1.6
+----------+
| SMF00482 |
+----------+
TEXT: >ERR> MULTIPLE "LATEJOB"/"NOLATEJOB" OPTION CARDS
FOUND
>ERR> ONLY ONE "LATEJOB"/"NOLATEJOB" OPTION CARD
ALLOWED, %VARX CARDS FOUND
TYPE: Error
REASON: Only one LATEJOB/NOLATEJOB option statement is
allowed. More than one LATEJOB/NOLATEJOB option
statement was encountered. The number of
LATEJOB/NOLATEJOB option statements found is
printed in the error message.
ACTION: Delete the extra LATEJOB/NOLATEJOB statements and
rerun SMFPGEN.
REFERENCES: Section 7.3.1.5
+----------+
| SMF00483 |
+----------+
TEXT: >ERR> MULTIPLE "SUSPENDNJE"/"NOSUSPENDNJE" OPTION
CARDS FOUND
>ERR> ONLY ONE "SUSPENDNJE"/"NOSUSPENDNJE" OPTION
CARD ALLOWED, %VARX CARDS FOUND
TYPE: Error
REASON: Only one SUSPENDNJE/NOSUSPENDNJE option statement
is allowed. More than one
SUSPENDNJE/NOSUSPENDNJE option statement was
encountered. The number of
SUSPENDNJE/NOSUSPENDNJE option statements found
is printed in the error message.
ACTION: Delete the extra SUSPENDNJE/NOSUSPENDNJE
statements and rerun SMFPGEN.
REFERENCES: Section 7.3.1.2
+----------+
| SMF00484 |
+----------+
TEXT: >ERR> "NJEJOB" OPTION CARD DETECTED, BUT
"SUSPENDNJE" OPTION CARD ALSO FOUND
>ERR> "SUSPENDNJE" NOT ALLOWED WITH "NJEJOB"'
>ERR> "NOSUSPENDNJE" CARD MUST BE USED
TYPE: Error
REASON: When an NJEJOB statement is specified, a
NOSUSPENDNJE statement must be included as well.
You have NJEJOB and SUSPENDNJE option statements
specified.
ACTION: You must replace the SUSPENDNJE option statement
with a NOSUSPENDNJE option statement if you want
the NJEJOB option to be in effect. You should
also review the sections referenced below to make
sure that you understand the relationship between
the NJEJOB and SUSPENDNJE/NOSUSPENDNJE option
statements.
REFERENCES: Sections 7.3.1.2 and 7.3.1.6
+----------+
| SMF00485 |
+----------+
TEXT: >ERR> "NJEJOB" OPTION CARD DETECTED, BUT
"NOSUSPENDNJE" OPTION CARD NOT FOUND
>ERR> "NOSUSPENDNJE" MUST BE USED WITH "NJEJOB"
TYPE: Error
REASON: When an NJEJOB option statement is specified, a
NOSUSPENDNJE option statement must be included as
well. You have an NJEJOB option statement, but
have not included a NOSUSPENDNJE option
statement.
ACTION: If you want the NJEJOB option to be in effect,
you must add a NOSUSPENDNJE option statement as
well. You should also review the sections
referenced below to make sure that you understand
the relationship between the NJEJOB and
SUSPENDNJE/NOSUSPENDNJE option statements.
REFERENCES: Sections 7.3.1.2 and 7.3.1.6
+----------+
| SMF00486 |
+----------+
TEXT: >>>>> "APPCJOB"/"NOAPPCJOB" OPTION CARD MISSING
>>>>> DEFAULT OF "NOAPPCJOB" USED
TYPE: Information
REASON: This message is generated when SMFOPS does not
contain an APPCJOB/NOAPPCJOB option statement.
The message displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.7
+----------+
| SMF00487 |
+----------+
TEXT: >>>>> "STCJOB"/"NOSTCJOB" OPTION CARD MISSING
>>>>> DEFAULT OF "NOSTCJOB" USED
TYPE: Information
REASON: This message is generated when SMFOPS does not
contain an STCJOB/NOSTCJOB option statement. The
message displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.8
+----------+
| SMF00488 |
+----------+
TEXT: >>>>> "TSOJOB"/"NOTSOJOB" OPTION CARD MISSING
>>>>> DEFAULT OF "NOTSOJOB" USED
TYPE: Information
REASON: This message is generated when SMFOPS does not
contain an TSOJOB/NOTSOJOB option statement. The
message displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.9
+----------+
| SMF00489 |
+----------+
TEXT: >ERR> MULTIPLE "APPCJOB"/"NOAPPCJOB" OPTION CARDS
FOUND
>ERR> ONLY ONE "APPCJOB"/"NOAPPCJOB" OPTION CARD
ALLOWED, %VARX CARDS FOUND
TYPE: Error
REASON: Only one APPCJOB/NOAPPCJOB option statement is
allowed. More than one APPCJOB/NOAPPCJOB option
statement was encountered. The number of
APPCJOB/NOAPPCJOB option statements found is
printed in the error message.
ACTION: Delete the extra APPCJOB/NOAPPCJOB statements and
rerun SMFPGEN.
REFERENCES: Section 7.3.1.7
+----------+
| SMF00490 |
+----------+
TEXT: >ERR> MULTIPLE "STCJOB"/"NOSTCJOB" OPTION CARDS
FOUND
>ERR> ONLY ONE "STCJOB"/"NOSTCJOB" OPTION CARD
ALLOWED, %VARX CARDS FOUND
TYPE: Error
REASON: Only one STCJOB/NOSTCJOB option statement is
allowed. More than one STCJOB/NOSTCJOB option
statement was encountered. The number of
STCJOB/NOSTCJOB option statements found is
printed in the error message.
ACTION: Delete the extra STCJOB/NOSTCJOB statements and
rerun SMFPGEN.
REFERENCES: Section 7.3.1.8
+----------+
| SMF00491 |
+----------+
TEXT: >ERR> MULTIPLE "TSOJOB"/"NOTSOJOB" OPTION CARDS
FOUND
>ERR> ONLY ONE "TSOJOB"/"NOTSOJOB" OPTION CARD
ALLOWED, %VARX CARDS FOUND
TYPE: Error
REASON: Only one TSOJOB/NOTSOJOB option statement is
allowed. More than one TSOJOB/NOTSOJOB option
statement was encountered. The number of
TSOJOB/NOTSOJOB option statements found is
printed in the error message.
ACTION: Delete the extra TSOJOB/NOTSOJOB statements and
rerun SMFPGEN.
REFERENCES: Section 7.3.1.9
+----------+
| SMF00493 |
+----------+
TEXT: >>>>> "OEJOB"/"NOOEJOB" OPTION CARD MISSING
>>>>> DEFAULT OF "NOOEJOB" USED
TYPE: Information
REASON: This message is generated when SMFOPS does not
contain an OEJOB/NOOEJOB option statement. The
message displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.10
+----------+
| SMF00494 |
+----------+
TEXT: >ERR> MULTIPLE "OEJOB"/"NOOEJOB" OPTION CARDS
FOUND
>ERR> ONLY ONE "OEJOB"/"NOOEJOB" OPTION CARD
ALLOWED, %VARX CARDS FOUND
TYPE: Error
REASON: Only one OEJOB/NOOEJOB option statement is
allowed. More than one OEJOB/NOOEJOB option
statement was encountered. The number of
OEJOB/NOOEJOB option statements found is printed
in the error message.
ACTION: Delete the extra OEJOB/NOOEJOB statements and
rerun SMFPGEN.
REFERENCES: Section 7.3.1.10
+----------+
| SMF00495 |
+----------+
TEXT: >>>>> "SAJOB"/"NOSAJOB" OPTION CARD MISSING
>>>>> DEFAULT OF "NOSAJOB" USED
TYPE: Information
REASON: This message is generated when SMFOPS does not
contain a SAJOB/NOSAJOB option statement. The
message displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.10
+----------+
| SMF00496 |
+----------+
TEXT: >ERR> MULTIPLE "SAJOB"/"NOSAJOB" OPTION CARDS
FOUND
>ERR> ONLY ONE "SAJOB"/"NOSAJOB" OPTION CARD
ALLOWED, %VARX CARDS FOUND
TYPE: Error
REASON: Only one SAJOB/NOSAJOB option statement is
allowed. More than one SAJOB/NOSAJOB option
statement was encountered. The number of
SAJOB/NOSAJOB option statements found is printed
in the error message.
ACTION: Delete the extra SAJOB/SAOEJOB statements and
rerun SMFPGEN.
REFERENCES: Section 7.3.1.10
+----------+
| SMF00497 |
+----------+
TEXT: >>>>> "PGMALL"/"NOPGMALL" OPTION CARD MISSING
>>>>> DEFAULT OF "NOPGMALL" USED
TYPE: Information
REASON: This message is generated when SMFOPS does not
contain a PGMALL/NOPGMALL option statement. The
message displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.15
+----------+
| SMF00498 |
+----------+
TEXT: >ERR> MULTIPLE "PGMALL"/"NOPGMALL" OPTION CARDS
FOUND
>ERR> ONLY ONE "PGMALL"/"NOPGMALL" OPTION CARD
ALLOWED, %VARX CARDS FOUND
TYPE: Error
REASON: Only one PGMALL/NOPGMALL option statement is
allowed. More than one PGMALL/NOPGMALL option
statement was encountered. The number of
SAJOB/NOSAJOB option statements found is printed
in the error message.
ACTION: Delete the extra PGMALL/NOPGMALL statements and
rerun SMFPGEN.
REFERENCES: Section 7.3.1.15
+----------+
| SMF00499 |
+----------+
TEXT: SUSPEND LIMIT NOT IN 1 TO 10 DAY RANGE
DEFAULT OF 10 DAYS IS USED
%VARX IS OUT OF RANGE
TYPE: Warning
REASON: The SUSPENDLIMIT option statement requires a
numeric operand in the range of 1 to 10. The
value printed with the warning statement was out
of range.
ACTION: If another SUSPENDLIMIT is desired, change the
SUSPENDLIMIT operand to a number within the range
of 1 to 10 and rerun SMFPGEN.
REFERENCES: Section 7.3.1.16
+----------+
| SMF00500 |
+----------+
TEXT: SUSPEND LIMIT VALUE IS MISSING
SUSPENDLIMIT IS SET TO 10 DAYS
TYPE: Warning
REASON: The SUSPENDLIMIT option statement requires a
numeric operand in the range of 1 to 10. The
value of SUSPENDLIMIT is set to the default of 10
days.
ACTION: If another SUSPENDLIMIT is desired, change the
SUSPENDLIMIT operand to a number within the range
of 1 to 10 and rerun SMFPGEN.
REFERENCES: Section 7.3.1.16
+----------+
| SMF00501 |
+----------+
TEXT: INCIDENT RETENTION LIMIT NOT IN 0-366 DAY RANGE
DEFAULT OF 120 DAYS IS USED
%VARX IS OUT OF RANGE
TYPE: Warning
REASON: The INCIDENTLIMIT option statement requires a
numeric operand in the range of 0 to 366. The
value of INCIDENTLIMIT is set to the minimum of
120 days.
ACTION: If another INCIDENTLIMIT is desired, change the
INCIDENTLIMIT operand to a number within the
range of 0 to 366 and rerun SMFPGEN.
REFERENCES: Section 7.3.1.17
+----------+
| SMF00502 |
+----------+
TEXT: CONFIG RETENTION LIMIT NOT IN 0-366 DAY RANGE
DEFAULT OF 120 DAYS IS USED
%VARX IS OUT OF RANGE
TYPE: Warning
REASON: The CONFIGLIMIT option statement requires a
numeric operand in the range of 0 to 366. The
value of CONFIGLIMIT is set to the minimum of 120
days.
ACTION: If another CONFIGLIMIT is desired, change the
CONFIGLIMIT operand to a number within the range
of 0 to 366 and rerun SMFPGEN.
REFERENCES: Section 7.3.1.18
+----------+
| SMF00503 |
+----------+
TEXT: >ERR> NUMBER OF DAYS FOR %KWX
>ERR> IS NOT NUMERIC OR MISSING
%VARX IS OUT OF RANGE
TYPE: Error
REASON: The specified option statement requires a numeric
operand.
ACTION: Change the option statement operand to a number
within a valid range for the option statement and
rerun SMFPGEN.
REFERENCES: Section 7.3.1.17 or
Section 7.3.1.18
+----------+
| SMF00504 |
+----------+
TEXT: >ERR> MULTIPLE "SUSPENDLIMIT" OPTION CARDS FOUND
>ERR> ONLY ONE "SUSPENDLIMIT" OPTION CARD ALLOWED
%VARX CARDS FOUND
TYPE: Error
REASON: Only one SUSPENDLIMIT option statement is allowed
in prefix.MICS.PARMS(SMFOPS). More than one
SUSPENDLIMIT option statement was encountered.
The number of SUSPENDLIMIT option statements
found is printed in the error message.
ACTION: Delete the extra SUSPENDLIMIT statements and
rerun SMFPGEN.
REFERENCES: Section 7.3.1.16
+----------+
| SMF00505 |
+----------+
TEXT: >ERR> MULTIPLE "INCIDENTLIMIT" OPTION CARDS FOUND
>ERR> ONLY ONE "INCIDENTLIMIT" OPTION CARD ALLOWED
%VARX CARDS FOUND
TYPE: Error
REASON: Only one INCIDENTLIMIT option statement is
allowed in prefix.MICS.PARMS(SMFOPS). More than
one INCIDENTLIMIT option statement was
encountered. The number of INCIDENTLIMIT option
statements found is printed in the error message.
ACTION: Delete the extra INCIDENTLIMIT statements and
rerun SMFPGEN.
REFERENCES: Section 7.3.1.17
+----------+
| SMF00506 |
+----------+
TEXT: >ERR> MULTIPLE "CONFIGLIMIT" OPTION CARDS FOUND
>ERR> ONLY ONE "CONFIGLIMIT" OPTION CARD ALLOWED
%VARX CARDS FOUND
TYPE: Error
REASON: Only one CONFIGLIMIT option statement is allowed
in prefix.MICS.PARMS(SMFOPS). More than one
CONFIGLIMIT option statement was encountered.
The number of CONFIGLIMIT option statements
found is printed in the error message.
ACTION: Delete the extra CONFIGLIMIT statements and
rerun SMFPGEN.
REFERENCES: Section 7.3.1.18
+----------+
| SMF00507 |
+----------+
TEXT: >>>>> "SUSPENDLIMIT" OPTION CARD MISSING
>>>>> DEFAULT OF "SUSPENDLIMIT 5" USED
TYPE: Information
REASON: This message is generated when
prefix.MICS.PARMS(SMFOPS) does not contain an
SUSPENDLIMIT option statement. The message
displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.16
+----------+
| SMF00508 |
+----------+
TEXT: >>>>> "INCIDENTLIMIT" OPTION CARD MISSING
>>>>> DEFAULT OF "INCIDENTLIMIT 30" USED
TYPE: Information
REASON: This message is generated when
prefix.MICS.PARMS(SMFOPS) does not contain an
INCIDENTLIMIT option statement. The message
displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.17
+----------+
| SMF00509 |
+----------+
TEXT: >>>>> "CONFIGLIMIT" OPTION CARD MISSING
>>>>> DEFAULT OF "CONFIGLIMIT 30" USED
TYPE: Information
REASON: This message is generated when
prefix.MICS.PARMS(SMFOPS) does not
contain an CONFIGLIMIT option statement. The
message displays the default value used.
ACTION: None
REFERENCES: Section 7.3.1.18
+----------+
| SMF00510 |
+----------+
TEXT: SUSPENDLIMIT OR CONFIGLIMIT OR INCIDENTLIMIT
SPECIFICATIONS WERE FOUND IN
prefix.MICS.PARMS(EXECDEF). OPTIONS SHOULD BE
SPECIFIED IN prefix.MICS.PARMS(SMFOPS). YOU SHOULD
UPDATED prefix.MICS.PARMS(SMFOPS) AND RUN
prefix.MICS.CNTL(SMFPGEN).
TYPE: Error
REASON: This message is generated when
prefix.MICS.PARMS(EXECDEF) contains either a
SUSPENDLIMIT, INCIDENTLIMIT, or CONFIGLIMIT
statement.
ACTION: Copy the SUSPENDLIMIT, INCIDENTLIMIT, CONFIGLIMIT
statements to prefix.MICS.PARMS(SMFOPS); then
delete options from prefix.MICS.PARMS(EXECDEF),
and submit prefix.MICS.CNTL(SMFPGEN).
REFERENCES: Section 7.3.1
+----------+
| SMF00511 |
+----------+
TEXT: MUST HAVE ONE SET OF ???? OPTIONS AND DEFAULT
STATEMENTS WHEN USING ???? OPTIONS AND DEFAULT
STATEMENTS IN prefix.MICS.PARMS(SMFOPS)
TYPE: Error
REASON: This message is generated when there is a missing
OPTIONS ???? statement or missing DEFAULT ????
statement when OPTIONS ???? and DEFAULT ????
statements are specified. This message is also
generated when more than one set of OPTIONS ????
and DEFAULT ???? statements are detected.
ACTION: Make sure both OPTIONS ???? and DEFAULT ????
statements are specified when using OPTIONS ????
and DEFAULT ???? statements in
prefix.MICS.PARMS(SMFOPS). When reviewing the
SMFOPS member, if more than one set of ????
OPTIONS and DEFAULT statement is found, delete
the unwanted set of ???? OPTIONS and DEFAULT
statements and submit prefix.MICS.PARMS(SMFPGEN).
REFERENCES: Section 7.3.1
+----------+
| SMF00512 |
+----------+
TEXT: SYSLISTACTION %VAR1 FOUND IN
prefix.MICS.PARMS(SMFOPS) WHICH MEANS
%MSG
TYPE: Information
REASON: This message is generated to provide notification
of action to be taken during the next execution
of the daily update DAY030 step.
Depending on the prefix.MICS.PARMS(SMFOPS)
SYSLISTACTION statement specification, this
message contains the following:
SYSLISTACTION ABORT
SYSLISTACTION ABORT FOUND IN
prefix.MICS.PARMS(SMFOPS) WHICH MEANS
DAY030 WILL ABEND WHEN DATA FROM UNDEFINED
ORGSYSIDs IS PROCESSED
SYSLISTACTION REJECT
SYSLISTACTION REJECT FOUND IN
prefix.MICS.PARMS(SMFOPS) WHICH MEANS DATA FROM
UNDEFINED ORGSYSIDs WILL BE REJECTED
ACTION: None
REFERENCES: Section 7.3.1
+----------+
| SMF00513 |
+----------+
TEXT: MISSING OPTIONS OR DEFAULT STATEMENT FOR %VAR1. AN
OPTIONS STATEMENT OR DEFAULT STATEMENT MUST BE
SPECIFIED FOR EVERY ORGSYSID LISTED IN THE SYSLIST
STATEMENT WHEN NO OPTIONS ???? AND DEFAULT ????
STATEMENTS ARE SPECIFIED IN
prefix.MICS.PARMS(SMFOPS)
TYPE: Error
REASON: This message is generated when an ORGSYSID that
was specified in the SYSLIST has no explicit
OPTIONS or DEFAULT statements, and no OPTIONS
???? or DEFAULT ???? statement are specified.
If an ORGSYSID is listed in SYSLIST with no
OPTIONS ???? or DEFAULT ???? statements
specified, there must be explicit OPTIONS and
DEFAULT statements for each of the specified
ORGSYSIDs
ACTION: Add one pair of OPTIONS ???? and DEFAULT ????
statements, or specify explicit OPTIONS and
DEFAULT statement pairs for every ORGSYSID listed
in this error message. Update
prefix.MICS.PARMS(SMFOPS) with these changes and
rerun prefix.MICS.CNTL(SMFPGEN).
REFERENCES: Section 7.3.1
+----------+
| SMF00514 |
+----------+
TEXT: MISSING %VAR3 STATEMENT WHEN %VAR4 IS SPECIFIED in
prefix.MICS.PARMS(SMFOPS)
TYPE: Error
REASON: When using analyzer-level control of the
systems(ORGSYSIDs) to provide input into the
daily update DAY030 step, SYSLIST and
SYSLISTACTION must both be specified.
ACTION: Add the missing statement in
prefix.MICS.PARMS(SMFOPS) and submit
prefix.MICS.CNTL(SMFPGEN).
REFERENCES: Section 7.3.1
+----------+
| SMF00515 |
+----------+
TEXT: %VAR1 IS SPECIFIED IN AN OPTIONS OR DEFAULT
STATEMENT BUT IS MISSING IN SYSLIST STATEMENT
in prefix.MICS.PARMS(SMFOPS)
TYPE: Error
REASON: This message is generated when an ORGSYSID is
specified in an explicit OPTIONS statement or
DEFAULT statement but is not listed in a SYSLIST
statement.
ACTION: Add the ORGSYSID displayed in the message to a
SYSLIST statement in prefix.MICS.PARMS(SMFOPS)
and submit prefix.MICS.CNTL(SMFPGEN).
REFERENCES: Section 7.3.1
+----------+
| SMF00516 |
+----------+
TEXT: INVALID OR MISSING ARGUMENT FOR SYSLISTACTION
STATEMENT IN prefix.MICS.PARMS(SMFOPS), MUST BE
FOLLOWED BY REJECT, OR ABORT
TYPE: Error
REASON: This message is generated when SYSLISTACTION
statement is specified, but is not followed by
REJECT OR ABORT.
ACTION: Add or change SYSLIST statement in
prefix.MICS.PARMS(SMFOPS) and submit
prefix.MICS.CNTL(SMFPGEN).
REFERENCES: Section 7.3.1
+----------+
| SMF00517 |
+----------+
TEXT: MULTIPLE "SYSLISTACTION" STATEMENTS FOUND
ONLY ONE "SYSLISTACTION" STATEMENT ALLOWED
%VARX STATEMENT FOUND IN prefix.MICS.PARMS(SMFOPS)
TYPE: Error
REASON: This message is generated when multiple
SYSLISTACTION statements are found in
prefix.MICS.PARMS(SMFOPS)
ACTION: Delete the unwanted SYSLISTACTION statement in
prefix.MICS.PARMS(SMFOPS) and submit
prefix.MICS.CNTL(SMFPGEN).
REFERENCES: Section 7.3.1
+----------+
| SMF00518 |
+----------+
TEXT: MISSING A %VAR1 STATEMENT FOR ORGSYSID %VARX WHEN A
%VAR1 ???? STATEMENT IS MISSING. ADD A %VAR1
STATEMENT FOR %VARX OR ADD A %VAR1 ???? STATEMENT
IN prefix.MICS.PARMS(SMFOPS).
TYPE: Error
REASON: An OPTIONS ORGSYSID statement requires
a corresponding DEFAULT ORGSYSID statement or a
DEFAULT ???? statement. A DEFAULT ORGSYSID
statement requires a corresponding OPTIONS
ORGSYSID statement or an OPTIONS ???? statement.
ACTION: If the intent is to not specify an explicit
OPTIONS or DEFAULT statement for an ORGSYSID, you
must specify an OPTIONS ????? or DEFAULT ?????
statement. Otherwise add the missing statement
for the ORGSYSID displayed in this message. After
updates have been made in
prefix.MICS.PARMS(SMFOPS), submit
prefix.MICS.CNTL(SMFPGEN).
REFERENCES: Section 7.3.1
+----------+
| SMF00519 |
+----------+
TEXT: SYSLIST STATEMENT NOT FOUND IN
prefix.MICS.PARMS(SMFOPS). ALL SYSTEMS WILL BE
PROCESSED. ORGSYSID UNIT-LEVEL AND COMPLEX-LEVEL
PARAMETERS WILL BE USED TO CONTROL INPUT DATA.
TYPE: Information
REASON: This message is generated as notification when
the next daily update DAY030 step is executed.
ORGSYSID unit-level and complex-level controls
will be used when processing input data.
ACTION: None
REFERENCES: Section 7.3.1
+----------+
| SMF00520 |
+----------+
TEXT: MISSING OPTIONS ???? and DEFAULT ???? STATEMENTS
IN prefix.MICS.PARMS(SMFOPS) WHEN ALL SYSTEMS HAVE
BEEN SELECTED TO BE PROCESSED BY THE SMF ANALYZER.
OPTIONS ???? and DEFAULT ???? STATEMENTS ARE
REQUIRED WHEN NO SYSLIST STATEMENT IS SPECIFIED.
TYPE: Error
REASON: This message is generated when there are missing
OPTIONS ???? and DEFAULT ???? statements, if
SYSLIST is not specified. OPTIONS ???? and
DEFAULT ???? statements are required when SYSLIST
is not specified.
ACTION: Add OPTIONS ???? and DEFAULT ???? statements in
prefix.MICS.PARMS(SMFOPS) and submit
prefix.MICS.CNTL(SMFPGEN).
REFERENCES: Section 7.3.1
+----------+
| SMF00521 |
+----------+
TEXT: NO ORGSYSIDs LISTED IN SYSLIST STATEMENT
IN prefix.MICS.PARMS(SMFOPS).
TYPE: Error
REASON: This message is generated when there are no
ORGSYSIDs specified in the SYSLIST statement.
ACTION: Update SYSLIST statement to include ORGSYSIDs to
be processed in prefix.MICS.PARMS(SMFOPS), and
submit prefix.MICS.CNTL(SMFPGEN).
REFERENCES: Section 7.3.1
+----------+
| SMF00522 |
+----------+
TEXT: ALL ORGSYSIDs LISTED IN SYSLIST STATEMENT
WILL BE ASSIGNED ???? OPTIONS/DEFAULT SETTINGS
TYPE: Information
REASON: This message is generated when there are no
explicit OPTIONS and DEFAULT statements found for
all ORGSYSIDs listed in the SYSLIST statement.
ACTION: None
REFERENCES: Section 7.3.1
+----------+
| SMF00523 |
+----------+
TEXT: DEFAULT STATEMENTS ARE OBSOLETE IN
prefix.MICS.PARMS(SMFOPS).
n DEFAULT STATEMENTS WERE FOUND IN SMFOPS
ALL DEFAULT STATEMENTS ARE IGNORED
TYPE: Warning
REASON: The DEFAULT statement is no longer supported in
prefix.MICS.PARMS(SMFOPS). If any DEFAULT
statements are detected, they are ignored and
processing continues.
ACTION: To prevent this message from displaying in the
MICSLOG, remove the DEFAULT statement(s) and
rerun SMFPGEN.
REFERENCES: Section 7.3.1
+----------+
| SMF01002 |
+----------+
TEXT: INVALID ACCOUNT FIELD STRUCTURE DETECTED
SMF RECORD TYPE="%SMFRTYPE" ORGSYSID="%ORGSYSID"
INPUT FILE RECORD NUMBER="%_N_"
ACCOUNT FIELD "%NUM" OF "%NUMACT" INDICATES A FIELD
LENGTH OF "%LEN" WHICH, IF READ, WOULD CAUSE A
SAS STOPOVER ABEND.
A HEX DUMP OF THE RECORD IS FOUND IN YOUR SASLOG
TYPE: Warning
REASON: The job statement account information in the raw
data is recorded as a series of field lengths
followed by a data field. One of the field
lengths implies a data field that exceeds the
length of the raw record.
ACTION: Review the record dump in your SASLOG to verify
the problem. Probable cause is code in an MVS
SMF exit routine.
REFERENCES: None
+----------+
| SMF01003 |
+----------+
TEXT: AT LEAST 10 SMF RECORDS WERE FOUND TO CONTAIN
CORRUPTED ACCOUNT FIELDS.
THE FIRST 10 RECORDS WERE HEX DUMPED TO YOUR SASLOG
THIS PROBLEM COULD AFFECT ACCOUNTING IF YOU DEPEND
ON JOB CARD ACCOUNT FIELDS.
YOU SHOULD INVESTIGATE THE DUMPED RECORDS TO
DETERMINE THE PROBLEM.
NO FURTHER DUMPS OR MESSAGES WILL OCCUR.
TYPE: Warning
REASON: This message is generated after 10 instances of
message SMF01002 have been written.
ACTION: Follow the directions in message SMF01002 to
resolve the SMF record problem.
REFERENCES: None
+----------+
| SMF01004 |
+----------+
TEXT: MALFORMATTED TYPE 30 RECORD WITH INVALID EXCP
SECTION DEVICE CLASS DETECTED. DATA FROM THAT
SECTION HAS BEEN DROPPED. THE SMF RECORD HAS BEEN
WRITTEN TO THE SASLOG. A MAXIMUM OF 5 RECORDS WILL
BE DUMPED.
TYPE: Warning
REASON: A SMF record containing an invalid device class
in an EXCP section has been detected.
ACTION: Review the record dump in your SASLOG to
determine the problem.
REFERENCES: None
+----------+
| SMF01005 |
+----------+
TEXT: MISSING SMF6JBID / JOBTYPID DETECTED
NON-STANDARD TYPE 6 RECORD DOES NOT HAVE SMF6JBID
NEEDED TO SET PGMTYPE.
PGMTYPE WILL DEFAULT TO 1 (BATCH).
REVIEW SASLOG FOR SAS DUMP OF RECORD.
THIS MESSAGE WILL ONLY BE WRITTEN A MAXIMUM OF 5
TIMES.
TYPE: Warning
REASON: SMF6JBID was not present in the TYPE 6 record
that was processed, which typically occurs in a
nonstandard TYPE 6 record; that is, those
created by products such as CA Spool, CA View,
and CA Dispatch. Consequently we were unable to
identify the PGMTYPE (program type) corresponding
to this SYSOUT record. PGMTYPE has been
defaulted to 1. You can override or change this
value using the _USRSSFW exit and setting
PGMTYPEW to a value.
ACTION: Review the record dump in your SASLOG to
determine the origin of this TYPE 6 record to
assist in determining what PGMTYPE should be.
Useful fields include SMF6UIF and JOB.
REFERENCES: Section 6.3.4.5.2.
+----------+
| SMF01007 |
+----------+
TEXT: %REJIDMS CA-IDMS SMF TYPE 30 RECORDS WERE
ENCOUNTERED AND REJECTED. A MAXIMUM OF 5 RECORDS
WERE DUMPED. REVIEW SASLOG FOR SAS DUMP OF
RECORDS.
TYPE: Warning
REASON: CA-IDMS SMF type 30 records were encountered in
the input data set and rejected. The records are
generated by the CA-IDMS Performance Monitor.
The format of records is outdated and so cannot
be processed by CA MICS.
ACTION: Review the record dump in your SASLOG and then
contact the CA-IDMS administrator to determine if
the records can be deactivated by setting the
#PMOPT option SMFTYPE30=NO.
REFERENCES: CA IDMS Performance Monitor System
Administration Guide, Section 2.2 Modifying
#PMOPT Parameters
+----------+
| SMF01010 |
+----------+
TEXT: AT LEAST %SMF105 BATSPL OBSERVATIONS WERE ASSIGNED
A DEFAULT PGMTYPE OF 1. YOU MAY RESET PGMTYPE IN
THE USRSSFW EXIT IF DESIRED. REVIEW THE SMF01005
MESSAGE FOR DETAILS.
TYPE: Warning
REASON: This message accompanies the SMF01005W message
and provides the number of times the SMF01005W
condition was detected.
ACTION: Review the record dump in your SASLOG written as
a result of the SMF01005W message to determine
the origin of this TYPE 6 record to assist in
determining what PGMTYPE should be. Useful
fields include SMF6UIF and JOB.
REFERENCES: Section 6.3.4.5.2.
+----------+
| SMF01015 |
+----------+
TEXT: SYSID OF UNKN HAS BEEN DETECTED ON THE BATREN FILE.
SYSID WAS NOT PROVIDED. THIS MESSAGE WILL
ONLY BE WRITTEN 5 TIMES. SYSID MUST BE RESET.
MESSAGE FOR DETAILS.
TYPE: Warning
REASON: For Multisystem Enclave activity, the SYSID is
not provided by IBM. A default of 'UNKN' has
been set by CA MICS. If the value of 'UNKN' is
detected, the SYSID on the BATREN has not been
reset.
ACTION: Determine a valid SYSID by mapping the system
name from the BATREN, field RENSYSNM, to a valid
SYSID at your data center. Use exit _USRSSRE to
reset SYSID on the BATREN.
REFERENCES: Section 5.2.16.3
+----------+
| SMF01017 |
+----------+
TEXT: APPARENT OVERFLOW OF SMF SOURCE FIELD FOR ELEMENT
%OFELEMT DETECTED %OFVALUE TIMES
TYPE: Warning
REASON: There was an overflow condition detected that was
caused by a negative value when the corresponding
SMF type 30 subtype 6 fields overflowed their
counters.
ACTION: None
REFERENCES: None
+----------+
| SMF01020 |
+----------+
TEXT: %SMF102 OBSERVATIONS HAVE DEFAULT SYSID OF UNKN ON
THE BATREN FILE. YOU MUST RESET SYSID IN THE
_USRSSRE EXIT. REVIEW THE SMF01015 FOR DETAILS.
MESSAGE FOR DETAILS.
TYPE: Warning
REASON: This message accompanies the SMF01015W message
and provides the number of times the SMF01015W
condition was detected.
ACTION: Determine a valid SYSID by mapping the system
name from the BATREN, field RENSYSNM, to a valid
SYSID at your data center. Use exit _USRSSRE to
reset SYSID on the BATREN.
REFERENCES: Section 5.2.16.3
+----------+
| SMF01024 |
+----------+
TEXT: >>>>> STATEMENT IN ERROR.
%INLINE
TYPE: Error
REASON: There was an invalid keyword specification in
sharedprefix.MICS.PARMS(SMFDEVS). This error
message will sometimes accompany SMF01025.
ACTION: Correct errors and execute again.
REFERENCES: Section 7.2.5
+----------+
| SMF01025 |
+----------+
TEXT: >>>>> ERROR(S) ENCOUNTERED IN
SP.MICS.PARMS(SMFDEVS) DEFINITION.
>>>>> SMFCGEN ABORTED
>>>>> CORRECT ERROR(S) AND EXECUTE AGAIN
TYPE: Error
REASON: There was an invalid keyword specification in
sharedprefix.MICS.PARMS(SMFDEVS).
ACTION: Correct errors and execute again.
REFERENCES: Section 7.2.5
+----------+
| SMF01030 |
+----------+
TEXT: INVALID DEVICECLASS SPECIFICATION, %CLASSDEF.
TYPE: Error
REASON: This message is generated due to an invalid
specification in the DEVICECLASS keyword
statement.
ACTION: Correct the invalid keyword specification and
rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01031 |
+----------+
TEXT: DEVICEADDRESS KEYWORD IS DEFINED BUT IS NOT
SPECIFIED.
TYPE: Error
REASON: This message is generated due to the SMFDEVS
optional keyword, DEVICEADDRESS, which was
defined but not specified.
ACTION: Correct the missing DEVICEADDRESS specification
and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01032 |
+----------+
TEXT: NOT ENOUGH ROOM ON LINE FOR ARGUMENT. ADD ANOTHER
DEVICEADDRESS SPECIFICATION.
TYPE: Error
REASON: This message is generated when an end of line
condition is reached, causing an incomplete
DEVICEADDRESS specification.
ACTION: Correct the DEVICEADDRESS specification and rerun
SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01033 |
+----------+
TEXT: DETAIL TIMESPAN MUST BE ACTIVATED WHEN A HIGHER
TIMESPAN IS ACTIVATED.
TYPE: Error
REASON: This message is generated when the DETAIL
timespan is set to inactive (N) and a higher
timespan is set to active (Y).
ACTION: Correct the TIMESPANS specification and rerun
SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01034 |
+----------+
TEXT: INVALID FILES SPECIFICATION.
TYPE: Error
REASON: There was an invalid FILES keyword specification,
or JOB was specified alone in a FILES keyword
specification in
sharedprefix.MICS.PARMS(SMFDEVS).
ACTION: Correct the FILES specification and rerun
SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01035 |
+----------+
TEXT: INVALID KEYWORD, %OPCODE.
TYPE: Error
REASON: This message is generated due to an invalid
keyword.
ACTION: Correct sharedprefix.MICS.PARMS(SMFDEVS) and
rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01036 |
+----------+
TEXT: NO DEVICE ACTIVITY DATA ELEMENTS WERE GENERATED.
TYPE: Information
REASON: This message is generated when no keywords are
defined in sharedprefix.MICS.PARMS(SMFDEVS).
ACTION: None
REFERENCES: Section 7.2.5
+----------+
| SMF01037 |
+----------+
TEXT: DUPLICATE ELEMENTDEF SPECIFICATION FOUND.
TYPE: Error
REASON: This message is generated when an ELEMENTDEF
specification was previously specified in another
set of I/O device activity statements.
ACTION: Remove the duplicate entry in
sharedprefix.MICS.PARMS(SMFDEVS) and rerun
SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01038 |
+----------+
TEXT: MISSING REQUIRED KEYWORD FOR A SET OF I/O DEVICE
ACTIVITY STATEMENTS.
TYPE: Error
REASON: This message is generated when a required keyword
is missing for a set of device activity
statements.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01039 |
+----------+
TEXT: MISSING SEMI-COLON (;) OR DUPLICATE KEYWORD FOUND
FOR A SET OF DEVICE ACTIVITY STATEMENTS.
TYPE: Error
REASON: This message is generated when a semicolon is
missing, and a duplicate keyword entry is found
for a set of device activity statements.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01040 |
+----------+
TEXT: DATA ELEMENT ALREADY EXISTS. CHANGE ELEMENTDEF
KEYWORD SPECIFICATION.
TYPE: Error
REASON: This message is generated when a set of
device activity data elements were previously
defined in SMFGENIN.
ACTION: Change the ELEMENTDEF keyword specification and
rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01041 |
+----------+
TEXT: BOTH DEVICETYPE AND DEVICEADDRESS KEYWORDS ARE
DEFINED FOR A SET OF DEVICE DEFINITION STATEMENTS.
TYPE: Error
REASON: This message is generated if both DEVICETYPE and
DEVICEADDRESS keywords were specified for a set
of I/O device activity statements.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01042 |
+----------+
TEXT: ELEMENTDEF SPECIFICATION IS MISSING.
TYPE: Error
REASON: This message is generated due to a missing
ELEMENTDEF specification.
ACTION: Correct errors and rerun SMFPGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01043 |
+----------+
TEXT: DEVICETYPE SPECIFICATION IS MISSING.
TYPE: Error
REASON: This message is generated due to a missing
DEVICETYPE specification.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01044 |
+----------+
TEXT: TIMESPANS SPECIFICATION IS MISSING.
TYPE: Error
REASON: This message is generated when TIMESPANS is
defined but the specification is missing.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01045 |
+----------+
TEXT: LABEL SPECIFICATION IS MISSING.
TYPE: Error
REASON: This message is generated when LABEL is defined
but the specification is missing.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01046 |
+----------+
TEXT: INVALID LENGTH FOR %OPCODE SPECIFICATION.
TYPE: Error
REASON: This message is generated when a keyword
specification is not the required length.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01047 |
+----------+
TEXT: MORE THAN FIVE DEVICEADDRESS KEYWORDS FOUND FOR A
SET OF I/O DEVICE ACTIVITY STATEMENTS.
TYPE: Error
REASON: This message is generated when more than five
DEVICEADDRESS keyword statements are found for a
single set of I/O Device Activity statements.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01048 |
+----------+
TEXT: HYPHEN IS MISSING IN DEVICEADDRESS RANGE
SPECIFICATION
TYPE: Error
REASON: This message is generated when a hyphen (-) is
missing in a DEVICEADDRESS range specification.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01049 |
+----------+
TEXT: BEGINNING DEVICEADDRESS IS NOT LESS THAN ENDING
DEVICEADDRESS IN DEVICE RANGE SPECIFICATION.
TYPE: Error
REASON: This message is generated when the beginning
DEVICEADDRESS specification is equal to or
greater than the ending DEVICEADDRESS
specification.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01050 |
+----------+
TEXT: MAXDEF SPECIFICATION IS MISSING.
TYPE: Error
REASON: This message is generated when MAXDEF is defined
but the specification is missing.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01051 |
+----------+
TEXT: MAXDEF SPECIFICATION IS AN 'X'. 'X' NOT ALLOWED.
TYPE: Error
REASON: AN X cannot be used as the last character of the
fffMX* data element name, because X is reserved
for the fffMXZ#X alias dictionary data element
names.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01052 |
+----------+
TEXT: DUPLICATE MAXDEF SPECIFICATION FOUND.
TYPE: Error
REASON: This message is generated when a MAXDEF
specification was previously specified in another
set of I/O device activity statements.
ACTION: Remove the duplicate entry in
sharedprefix.MICS.PARMS(SMFDEVS) and rerun
SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01053 |
+----------+
TEXT: INVALID LENGTH FOR MAXDEF SPECIFICATION.
TYPE: Error
REASON: MAXDEF specification is greater than one
character in length.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
+----------+
| SMF01054 |
+----------+
TEXT: ELEMENTDEF SPECIFICATION IS 'XXX'. 'XXX' NOT
ALLOWED.
TYPE: Error
REASON: XXX cannot be used as the last 3 characters of
the fff#Z* data element name, because XXX is
reserved for the fff#ZXXX alias dictionary data
element names.
ACTION: Correct errors and rerun SMFCGEN.
REFERENCES: Section 7.2.5
Copyright © 2014 CA.
All rights reserved.
|
|