Previous Topic: A.1 VCA Component MessagesNext Topic: Appendix B: DATA DICTIONARY


A.2 HSM Component Messages


This appendix lists all messages generated by the HSM
component of the CA MICS Space 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
                 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 Space 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
                 product.  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
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.  For example, message HSM00016 reads as
follows:
 
   TEXT:  >>>>> SYSID NOT 1 TO 4 CHARACTERS IN LENGTH.
            SYSID=%TOKEN2.
 
A possible version of the printed message in the MICSLOG
might be:
 
   TEXT:  >>>>> SYSID NOT 1 TO 4 CHARACTERS IN LENGTH.
            SYSID=SYS008.
 
+-----------------+
| H S M 0 0 0 0 1 |
+-----------------+
 
   TEXT:  HSM PARAMETER GENERATION STARTED.
 
   TYPE: Information
 
   REASON: This message indicates the start of the HSMPGEN
           process.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 0 0 2 |
+-----------------+
 
   TEXT:  HSM PARAMETER GENERATION COMPLETED SUCCESSFULLY.
 
   TYPE:  Information
 
   REASON: This message indicates the completion of the
           HSMPGEN process.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 0 1 0 |
+-----------------+
 
   TEXT:  ---- HSMOPS MEMBER:
 
   TYPE:  Information
 
   REASON: This message precedes the printing of the contents
           of the HSMOPS member.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 0 1 1 |
+-----------------+
 
   TEXT:  %LINE
 
   TYPE: Information
 
   REASON: This message lists the contents of the HSMOPS
           member.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 0 1 5 |
+-----------------+
 
   TEXT:  >>>>> KEYWORD NOT RECOGNIZED  KEYWORD=%TOKEN1.
 
   TYPE:  Error
 
   REASON: An invalid keyword has been specified in HSMOPS.
 
   ACTION: Specify a valid keyword and resubmit HSMPGEN.
 
   REFERENCES:  Section 7.3.2
 
+-----------------+
| H S M 0 0 0 1 6 |
+-----------------+
 
   TEXT:  >>>>> SYSID NOT 1 TO 4 CHARACTERS IN LENGTH.
            SYSID=%TOKEN2.
 
   TYPE:  Error
 
   REASON: The SYSID value specified on the OPTIONS statement
           is greater than 4 characters in length. SYSID must
           be between 1 and 4 characters in length.
 
   ACTION: Specify a valid value for SYSID and resubmit
           HSMPGEN.
 
   REFERENCES:  Section 7.3.2
 
+-----------------+
| H S M 0 0 0 1 7 |
+-----------------+
 
   TEXT:  >>>>> INTERVAL TIME VALUE MUST BE 1-999 HOURS.
            VALUE=%TOKEN3.
 
   TYPE:   Error
 
   REASON: The interval time specified on the OPTIONS
           statement is not between 1 and 999.
 
   ACTION: Specify a value between 1 and 999 and resubmit
           HSMPGEN.
 
   REFERENCES:  Section 7.3.2
 
+-----------------+
| H S M 0 0 0 2 0 |
+-----------------+
 
   TEXT:  ---- END OF HSMOPS MEMBER.
 
   TYPE:   Information
 
   REASON: This message is issued after the contents of
           HSMOPS has been printed.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 0 2 4 |
+-----------------+
 
   TEXT:  OPTIONS STATEMENT MISSING. ASSUMING DURATION OF 24
            HOURS AND ACCEPTANCE OF INPUT FROM ANY SYSID.
 
   TYPE:  Information
 
   REASON: The options statement was not found in HSMOPS.
           A default interval of 24 hours is used and
           the HSM component will process data from
           any SYSID.
 
   ACTION: None
 
   REFERENCES:  Section 7.3.2
 
+-----------------+
| H S M 0 0 0 2 7 |
+-----------------+
 
   TEXT:  ACCOUNTING STATEMENT MISSING. ASSUMING
          COMPUTATION OF STORAGE COST AT -DAYS- TIME SPAN.
 
   TYPE:   Information
 
   REASON: The ACCOUNTING statement has not been specified in
           HSMOPS. If you use the CA MICS Accounting and
           Chargeback Option, the storage cost computation
           for the HSM component will be performed at the
           DAYS timespan.
 
   ACTION: None
 
   REFERENCES:  Section 7.3.2
 
+-----------------+
| H S M 0 0 0 2 8 |
+-----------------+
 
   TEXT:  INVALID PARAMETER FOR %TOKEN1 KEYWORD. SPECIFY
            %CHOICE1 OR %CHOICE2.
 
   TYPE:  Error
 
   REASON: For the ACCOUNTING statement, the valid keywords
           are DETAIL and DAYS.
 
   ACTION: Specify either DETAIL or DAYS on the ACCOUNTING
           statement and resubmit HSMPGEN.
 
   REFERENCES:  Section 7.3.2
 
+-----------------+
| H S M 0 0 0 3 0 |
+-----------------+
 
   TEXT:  >>>>> ERROR(S) ENCOUNTERED IN HSMOPS PARM
            DEFINITIONS.
          >>>>> $HSMMSTR GENERATION ABORTED.
          >>>>> CORRECT ERROR(S) AND EXECUTE AGAIN.
 
   TYPE:  Error
 
   REASON: One or more errors were encountered during the
           HSMPGEN process.
 
   ACTION: Correct the errors and resubmit HSMPGEN.
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 1 0 0 |
+-----------------+
 
   TEXT:  --------------- BEGIN PHASE 1 ---------------
 
   TYPE:   Information
 
   REASON: This message is issued during Phase 1 of the
           DAY095 step of the DAILY job.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 1 0 1 |
+-----------------+
 
   TEXT:  AT LEAST ONE RECORD WITH SYSID NOT DEFINED IN
            HSMOPS (%ORGSYSID).
          -- THE DEFAULT DURATION FROM PARMS(HSMOPS) WILL
            BE USED
          -- WHEN AN HSM INVENTORY IS COLLECTED FOR THE
            FIRST TIME.
 
   TYPE:  Information
 
   REASON: An undefined SYSID has been encountered during
           the processing of the DAY095 step.  A default
           duration value from HSMOPS will be assigned.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 1 0 2 |
+-----------------+
 
   TEXT:  AT LEAST ONE RECORD READ WITH BAD VCH RECORD ID.
            (%VCHID).  SUCH RECORDS ARE DELETED.
 
   TYPE:   Warning
 
   REASON: Records were found with a record ID that is
           invalid. The record ID must be VCH.  The records
           are deleted, and the option-deleted counter is
           incremented.
 
   ACTION: Check to see if invalid data is being input to
           the DAY095 step.
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 1 0 3 |
+-----------------+
 
   TEXT:  VCH VERSIONS PRIOR TO %VER ARE NO LONGER SUPPORTED
 
   TYPE:  Error
 
   REASON: The input data being processed is from a version
           of the HSM data collector that is not supported.
 
   ACTION: Ensure that the version of the HSM data collector
           being used is supported.
 
   REFERENCES: None
 
 
+-----------------+
| H S M 0 0 1 0 4 |
+-----------------+
 
   TEXT:  FIRST INPUT TIMESTAMP IS FROM SYSID (%ORGSYSID)
          -- VERSION (%VER) DATA CREATED ON %ENDTS.
          -- COMPUTED DURATION = %TIME
          -- BASED ON A PREVIOUS COLLECTION ON %PREVTS
 
   TYPE:   Information
 
   REASON: The message identifies the first input timestamp,
           SYSID, version of the data, computed duration,
           and the last time the collection was done.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 1 1 0 |
+-----------------+
 
   TEXT:  HSM INVENTORY TRAILER RECORD <<%COND>> FOR
            SYSID (%ORGSYSID)
          -- VERSION (%VER) DATA CREATED ON %ENDTS.
 
   TYPE:  Information
 
   REASON: This message flags the presence or absence of the
           HSM inventory trailer record.  The value of the
           variable COND can take on the values of FOUND or
           MISSING. If the trailer record is missing, then
           HSM00116W is issued.  This may cause input data to
           be deleted.
 
   ACTION: If the HSM inventory trailer record is missing,
           then refer to HSM00205W.
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 1 1 1 |
+-----------------+
 
   TEXT:  RECORD-TYPE CODE    COUNT
            INCOMING
 
   TYPE:   Information
 
   REASON: This message is issued when the HSM inventory
           trailer record has been found.  This message is
           followed by HSM00112I.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 1 1 2 |
+-----------------+
 
   TEXT:  -- %RECTYPE     %RECCODE  %RECCNT %ENDTS
            %COND
 
   TYPE:   Information
 
   REASON: This message is issued when the HSM inventory
           trailer record has been found.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 1 1 6 |
+-----------------+
 
   TEXT:  DATA WITH THIS ENDTS WILL BE PURGED TO AVOID
            DUPLICATION
          -- BY A LATER RERUN OF A COMPLETED INVENTORY.
 
   TYPE:   Warning
 
   REASON: A HSM inventory trailer record has not been found
           for the data being processed.  This usually means
           that a partial HSM inventory took place. These
           records are purged as they are from a partial
           inventory to avoid duplicate data situations.
 
   ACTION: See HSM00205I for action that may be needed.
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 2 0 0 |
+-----------------+
 
   TEXT:  --------------- BEGIN PHASE 2 ---------------
 
   TYPE  : Information
 
   REASON: This message is issued during Phase 1 of the
           DAY095 step of the DAILY job.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 2 0 5 |
+-----------------+
 
   TEXT:  FOLLOWING RECORDS PURGED FROM (%FILE) FILE -
            SYSID (%SYSID)
          -- INVENTORY FROM %ENDTS IS BEING DISCARDED.
 
   TYPE:   Warning
 
   REASON: Records have been purged from the indicated file
           because the complete inventory has not been input
           to the DAY095 step.  This situation happens for
           two main reasons:
 
           o If the CA MICS HSM component records are being
             written to SMF and an unexpected failure caused
             the Space Collector scan job to abend, a partial
             output is written to SMF.  When the job is
             restarted and completes successfully, a complete
             output is produced.  If both the partial output
             and the complete output are input to the DAY095
             step, this message will be issued.
 
           o If the Space Collector job is running and SMF
             dumping takes place, only a partial output is
             written to tape. The rest of the output will be
             written the next time SMF dumping is done. This
             will cause the DAY095 to reject these records.
 
   ACTION: If the second scenario is the reason for this
           message, then schedule the Space Collector job so
           that the HSM inventory completes before SMF
           dumping is done at your site.
 
   REFERENCES:
 
+-----------------+
| H S M 0 0 2 0 6 |
+-----------------+
 
   TEXT:  D A T A   S E T   N A M E
 
   TYPE:  Information
 
   REASON: Appears before HSM00207I and is preceded by
           HSM00205I
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 2 0 7 |
+-----------------+
 
   TEXT:  %DSNAME
 
   TYPE:  Information
 
   REASON: The data set record is being purged from the HSM
           file.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 2 0 8 |
+-----------------+
 
   TEXT:  ....SUPPRESSING FURTHER DISPLAY OF REJECTED
            RECORDS.....
 
   TYPE:   Information
 
   REASON: This message is issued after the limit of
           HSM00207I is reached. The current limit is set to
           40.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 2 0 9 |
+-----------------+
 
   TEXT:  >>>>> %RECNUM RECORDS DELETED FROM %FILE.
 
   TYPE:   Information
 
   REASON: The total number of records deleted from the file
           indicated is given.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 2 1 6 |
+-----------------+
 
   TEXT:  VOLSER  COLLECTION-DATE
 
   TYPE:  Information
 
   REASON: Appears before HSM00207I and is preceded by
           HSM00205I.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 2 1 7 |
+-----------------+
 
   TEXT:  %VOLSER  %ENDTS
 
   TYPE:   Information
 
   REASON: This message indicates the Volume record that is
           being purged from the file indicated in the
           HSM00209I message.
 
   ACTION: See HSM00205I for action to take.
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 3 0 0 |
+-----------------+
 
   TEXT:  SORTING DETAIL DATA INTO DAYS TIME-SPAN SEQUENCE
            FOR FILE:
          -- %WRKNAME
          -- (EITHER) DAYS SEQUENCE IS NOT A SUBSET OF
            DETAIL.
          -- (OR) MULTIPLE ENDTS VALUES ARE PRESENT IN
            THE INPUT DATA.
 
   TYPE:   Information
 
   REASON: The sort sequence for the DAYS file is not a
           subset of the DETAIL file, or there are multiple
           ENDTS values in the data. This means a sort has to
           be performed. If the sort sequence for the DAYS
           file is a subset of the DETAIL file, then this
           sort can be avoided, thus speeding up DAY095
           processing.
 
   ACTION: None
 
   REFERENCES: None
 
+-----------------+
| H S M 0 0 9 9 9 |
+-----------------+
 
   TEXT:  ------- BEGIN SUMMARIZATION AND AGING -------
 
   TYPE:   Information
 
   REASON: This message indicates that the summarization
           process that summarizes the data into higher
           timespans is starting.
 
   ACTION: None
 
   REFERENCES: None