7. RETURN CODES AND MESSAGES › 7.2 Messages Description › 7.2.8 VCCXHSM Messages
7.2.8 VCCXHSM Messages
VCCHS02I
--------
PREVIOUS DATA COLLECTION (MIGRATE DATA) yyddd hh:mm:ss
(BACKUP DATA) yyddd hh:mm:ss
The Julian date and time of day when this DFHSM data was
gathered previously. The span of time between each inventory
measurement forms the DURATION data element in the CA MICS
Data Base that, in turn, is the basis for all "space*time"
calculations and a foundation for storage occupancy
accounting applications. Usually, an inventory of the
migrate data will be taken at the same time as the inventory
of the backup data but because the HSMMIGRATE and HSMBACKUP
keywords allow you to vary the collection intervals of each
type of data, each previous time stamp is shown on the
report.
VCCXHSM action: These time stamps are obtained from the HSM
control record in the VCCNTROL file. The
appropriate time stamp is stored in each
type 'M' and type'B' record written by
VCCXHSM to either SMF or to the VCCXHSM
data set.
VCCHS03I
--------
STARTING DATA COLLECTION: yyddd hh:mm:ss
The Julian date and time of day when this DFHSM data
collection commenced. A TIME macro is issued just prior to
calling ARCUTIL.
The span of time between this inventory and the previous time
forms the DURATION data element.
VCCXHSM action: This time stamp is stored in the HSM
control record in the VCCNTROL file. On the
subsequent run with HSM=Y, this time
becomes the PREVIOUS time stamp and a
perpetual recalculation of DURATION is
therefore possible.
VCCHS04I
--------
ENDING DATA COLLECTION: yyddd hh:mm:ss
The Julian date and time of day when this DFHSM data
collection ended. A TIME macro is issued upon return from
ARCUTIL.
This time stamp is shown for the purpose of understanding the
contribution to total VCC run-time caused by the DFHSM
inventory process.
VCCXHSM action: This time stamp is not stored in any file
nor placed in the VCCHSM records. It is
displayed and used to calculate the elapsed
time shown in the VCCHS05I message.
VCCHS05I
--------
ELAPSED TIME FOR THIS RUN: yyddd hh:mm:ss
The calculated elapsed time spent in the VCCXHSM subtask
including the time required by ARCUTIL is shown. It can be
compared to the elapsed time for the VTOC and catalog scans
done asynchronously by other functions of VCC.
VCCXHSM action: None.
VCCHS06I
--------
NUMBER OF TYPE "M" RECORDS IN --ML2-- READ: nnnnnnnn
NUMBER OF TYPE "M" RECORDS IN --ML1-- READ: pppppppp
NUMBER OF TYPE "M" RECORDS IN -SDSP-- READ: ssssssss
The count and location of type "M" (migrate) records are
shown for informational purposes. Note that any records
found in a Small Data Set Packing (SDSP) data set are also
a part of ML1 (therefore the value for ssssssss above is
a subset of pppppppp). As an audit, the value of nnnnnnnn
+ pppppppp should equal the number of MIGRATE records
written as shown in the VCCHS07I message.
VCCXHSM action: Messages produced at end of processing.
VCCHS07I
--------
NUMBER OF HSM -- tttttttt -- RECORDS PROCESSED: nnnnnnnn
The type and count of records returned by ARCUTIL are shown
for auditing purposes. Values for tttttttt are as follows:
MIGRATE
BACKUP
DASD-CP
TAPE-CP
VCCXHSM action: Messages produced at end of processing.
VCCHS11E
--------
BLDL FAILED FOR ARCUTIL. HSM=N IS FORCED.
The required data collection program, ARCUTIL, could not be
found in the STEPLIB or LNKLST concatenation. This would
suggest that either DFHSM is not installed at the required
version and release level or is installed in a STEPLIB that
is not in the concatenation with VCC.
VCCXHSM action: Control is returned immediately to VCCNTRL
and VTOC and catalog scanning continues.
VCCHS12E
--------
ARCUTIL RETURN CODE = hh REASON CODE = ii.
ARCUTIL detected some sort of environmental error and the
return code (hh) and the reason code (ii) are displayed in
decimal. Refer to IBM publication SH35-0084-4, DFHSM
Installation and Customization Guide, for descriptions of
codes. Your action should be guided by the return code:
RC Action
0 Successful run; no action required.
4 Internal error in VCCXHSM; contact CA MICS Product
Support.
8 Probable missing DD statement. See message VCCHS14E.
12 Probable hardware error. See message VCCHS15E.
16 Probable hardware error. See message VCCHS16E.
20 Abnormal termination in ARCUTIL. See message
VCCHS16E.
24 Internal processing error. See messages VCCHS26E
and VCCH27E.
VCCXHSM action: Control is returned immediately to VCCNTRL
and VTOC and catalog scanning continues.
Problem Determination
---------------------
Most of the remaining messages attempt to supplement the
basic return code and reason code information in VCCHS12E.
The intent is to echo for your convenience what you would
find by examining the DFHSM Installation and Customization
Guide.
Direct Invocation of ARCUTIL
----------------------------
If an error occurs with the VCC interface to DFHSM, you
should run ARCUTIL directly to see if you get the same return
code. If ARCUTIL results are the same as with the VCC
execution, you should follow appropriate debugging techniques
in IBM documentation for DFHSM and/or call IBM for technical
support.
To run ARCUTIL by itself, modify the following example as
needed:
//S1 EXEC PGM=ARCUTIL,PARM='DCOLLECT MIGD CAPD BACD MSERR'
//ARCSNAP DD SYSOUT=*
//ARCTEST DD SYSOUT=*
//ARCDATA DD DSN=prefix.ARCUTIL.BATCH.TEST,
// DISP=(,CATLG,DELETE),UNIT=SYSALLDA,
// SPACE=(CYL,(100,30),RLSE)
//MCDS DD DSN=prefix.MCDS,DISP=SHR
//BCDS DD DSN=prefix.BCDS,DISP=SHR
Because ARCUTIL does not compress output records like the VCC
interface does, the space requirements for ARCDATA can be
very significant.
More information about running ARCUTIL by itself can be found
in Chapter 16 of the DFHSM Installation and Customization
Guide.
VCCHS13E
--------
UNABLE TO OPEN DDNAME - VCCHSM
VCCXHSM requires this file to write data records unless
HSMSMF=Y is coded.
If HSMSMF=Y is coded, then a small amount of space (perhaps a
few tracks) is required as a work file.
VCCXHSM action: Control is returned immediately to VCCNTRL
and VTOC and catalog scanning continues.
VCCHS14E
--------
ERROR OPENING DFHSM CONTROL DATA SET. xxxx DDNAME IS MISSING
OR INVALID.
ARCUTIL requires this file to obtain records from the xxxx
(MCDS/BCDS) control data set.
VCCXHSM action: Control is returned immediately to VCCNTRL
and VTOC and catalog scanning continues.
VCCHS15E
--------
ERROR READING DFHSM xxxx DATA SET. OVER 1% OF RECORDS
REQUIRED CANNOT BE READ.
xxxx is substituted with MCDS or BCDS.
Investigate the cause of the READ errors and rerun the job.
Consider running ARCUTIL by itself as described by VCCHS12E.
VCCXHSM action: Control is returned immediately to VCCNTRL
and VTOC and catalog scanning continues.
VCCHS16E
--------
ERROR WRITING TO 'VCCHSM'' DATA SET. REGISTER 1 CONTENT FROM
'SYNADAF' MACRO = hhhhhhhh.
An I/O error occurred writing DFHSM data to the output file
defined by the VCCHSM DD statement. ARCUTIL has intercepted
this error by means of a SYNAD exit.
The content of register 1 associated with ARCUTIL error
handling is substituted for hhhhhhhh in the message.
Investigate the cause of the WRITE errors. You may have to
reallocate the VCCHSM to a different and perhaps larger
location, then rerun the job.
Consider running ARCUTIL by itself as described by VCCHS12E.
VCCXHSM action: Control is returned immediately to VCCNTRL
and VTOC and catalog scanning continues.
VCCHS17E
--------
ABNORMAL TERMINATION OCCURRED IN 'ARCUTIL'.
ABEND CODE = hhhhhhhh.
An abend has occurred within ARCUTIL processing. The abnormal
termination code is substituted for hhhhhhhh in the message
text.
Consider running ARCUTIL by itself as described by VCCHS12E.
If possible, correct the error and resubmit the job. If this
is not possible, contact CA MICS Product Support and/or IBM
customer support. You may be able to reproduce this error by
running DCOLLECT with an equivalent set of collection options
and JCL statements.
VCCXHSM action: Control is returned immediately to VCCNTRL
and VTOC and catalog scanning continues.
VCCHS18E
--------
ABNORMAL TERMINATION OCCURRED DURING HSM=Y PROCESSING.
ABEND COMPLETION CODE = hhhhhh
An abend has occurred within VCCXHSM or possibly within
ARCUTIL. The abend code is placed in the message.
Consider running ARCUTIL by itself as described by VCCHS12E.
Contact CA MICS Product Support. If possible, have the dump
on SYSUDUMP available.
VCCXHSM action: Control is returned immediately to VCCNTRL
and VTOC and catalog scanning continues.
VCCHS22I
--------
SKIPPING RECORD TYPE 'x' DUE TO INVALID DATA. ID = dsname
A validity check on the length of the record (to avoid abend
S002-18) has trapped an invalid record that will be skipped
(not written to the output destination). If it is a type 'M'
or type 'B' record, the data set name will be placed in the
message to help identify this error.
VCCXHSM action: The record is skipped and the skip counter
is updated. The number of skipped records
is reported at the end of the job.
VCCHS23I
--------
NUMBER OF RECORDS SKIPPED BY THIS INTERFACE: zzzzzzz
The count of records found to have an invalid record length
or other detectable error is reported.
VCCXHSM action: None.
VCCHS25E
--------
ERROR READING DFHSM CONTROL DATA SET. POSITION ERROR TO
xxxx RECORD OCCURRED.
xxxx is substituted with MCDS or BCDS.
Consider running ARCUTIL by itself as described by VCCHS12E.
VCCXHSM action: Control is returned immediately to VCCNTRL
and VTOC and catalog scanning continues.
VCCHS26E
--------
INTERNAL ERROR. ARCSNAP DD NOT AVAILABLE.
Consider running ARCUTIL by itself as described by VCCHS12E.
VCCXHSM action: Control is returned immediately to VCCNTRL
and VTOC and catalog scanning continues.
VCCHS27E
--------
INTERNAL ERROR. ESTAE CANNOT BE ESTABLISHED.
Consider running ARCUTIL by itself as described by VCCHS12E.
VCCXHSM action: Control is returned immediately to VCCNTRL
and VTOC and catalog scanning continues.
VCCHS28I
--------
NUMBER OF TYPE "M" RECORDS ON ML2 SKIPPED: nnnnnnnn
This message refers to a "filter" that occurs when VCC is
executing in "ASTEX mode" only. All type "M" records for data
sets migrated to ML2 before the implementation date of the
ASTEX Migration Manager are skipped and a count of those
records thus filtered out is shown in this message as
nnnnnnnn. This filter is to improve performance since the
records would have been discarded later by Migration Manager
post-processor steps.
VCCXHSM action: None.
