This phase begins by appending SMS data extracted during Phase 1 to that extracted during Phase 3. This SMS data is then sorted and merged with the VCAVOA, VCADAA, and EXTDAA work files in order to create the detail level of the DAA file. DSNODES 1 through 5 and DSNODEL are created for use by the VCAACRT Accounting routine. Various error conditions are checked, such as a missing DFSMS Information Cell, or a mismatch of VVDS Data to the VTOC. If any such errors are detected, the DFSMS Exception Report/VTOC Restart Report is written to the MICSLOG Sysout data set (see Figure 9-6 for an example of this report). Checks are also made in this phase for DFHSM-owned structures in order to set the element DAADSTYP (data set type) to 'HS' or 'HV' and element DAACSTAT (Catalog Status) to 'HSM' so that duplicate billing for HSM occupied DASD space can be avoided. That is, the VCAACRT account routine can ignore this space if it is billed by the HSMACRT account routine. The VCAACRT routine is invoked to cost each DAA observation as needed. The DFSMS storage group name obtained from the VOA file is propagated to each data set observation and the user exit USRSDAA is invoked. If EXTENTDETAIL was requested for VSAM data sets having more than 16 extents (see Section 7.3.1), multiple observations are output describing each set of 16 extents. At the end of this phase, the work data sets are deleted and the final version of the DAA file is re-sorted and written to the CA MICS database.
------------------------------------------------------------- MICSLOG ------------------------------- 19:00 SATURDAY, MAY 11, 1991 19.04.28 VCA00601I DFSMS EXCEPTION REPORT / VTOC RESTART REPORT 19.04.28 VCA00601I 19.04.28 VCA00601I 19.04.28 VCA00601I THIS REPORT IDENTIFIES SEVERAL POSSIBLE ERROR CONDITIONS WHICH STEM FROM PROBLEMS IN THE VCC 19.04.28 VCA00601I COLLECTION PROCESS --- OR --- DFSMS FLAG INCONSISTENCIES AT THE VOLUME OR THE DATA SET LEVEL. 19.04.28 VCA00601I 19.04.28 VCA00601I FOR MESSAGE GROUP VCA00602W, EITHER: 19.04.28 VCA00601I (1) SMS MANAGED VOLUME CONTAINS DATA SETS WHICH ARE NOT SMS-MANAGED (MISSING SMS CELL), OR, 19.04.28 VCA00601I (2) FORMAT-1 DSCB FIELDS RESERVED FOR USE BY DFSMS HAVE BEEN USED BY NON-IBM CODE RESULTING 19.04.28 VCA00601I IN A FALSE INDICATION OF AN SMS-MANAGED DATA SET. 19.04.28 VCA00601I ACTION: OBSERVATION IS WRITTEN WITH SMS DATA ELEMENTS MISSING. 19.04.28 VCA00601I 19.04.28 VCA00601I FOR MESSAGE GROUP VCA00607W: 19.04.28 VCA00601I (1) VCC DATA COLLECTION FOR THE SPECIFIED VOLUME DID NOT COMPLETE PROPERLY. THE CAUSE IS 19.04.28 VCA00601I SHOWN IN THE VCCSTATS REPORT. 19.04.28 VCA00601I ACTION: OBSERVATION IS DISCARDED FROM THE VCADAA FILE (SINCE VCAVOA OBSERVATION IS MISSING). 19.04.28 VCA00601I -- -------------------------------------------- --------------------------------------------- 19.04.28 VCA00602W >>>>> VOLUME=TSU020 - SYSID=PRD1 10MAY91:15:31:52.57 - ERRORS MATCHING VVDS (DFSMS CELL) DATA TO VTOC 19.04.28 VCA00602W 19.04.28 VCA00603W OS TDKPE22.ASXJES3.LNK DFSMS INFORMATION CELL MISSING 19.04.29 VCA00603W OS IAM.IAMED.LOGDATA DFSMS INFORMATION CELL MISSING 19.04.29 VCA00603W OS SMSTEST.EDITEST DFSMS INFORMATION CELL MISSING 19.04.29 VCA00602W >>>>> VOLUME=TSU021 - SYSID=PRD1 10MAY91:15:31:52.57 - ERRORS MATCHING VVDS (DFSMS CELL) DATA TO VTOC 19.04.29 VCA00602W 19.04.29 VCA00603W VS ATM.DIST.AOI20.ADMIN2.DATA DFSMS INFORMATION CELL MISSING 19.04.29 VCA00606W ?? TDKWFVA.SMPWRK3.T1822070.D91039.OBJ MANAGED DATA SET IN VVDS BUT NOT PRESENT IN VTOC 19.04.30 VCA00602W >>>>> VOLUME=TSU022 - SYSID=PRD1 10MAY91:15:31:52.57 - ERRORS MATCHING VVDS (DFSMS CELL) DATA TO VTOC 19.04.30 VCA00602W 19.04.30 VCA00603W OS DPO.QFS25.LOAD DFSMS INFORMATION CELL MISSING 19.04.31 VCA00603W OS TNG0807.ISPFXA.ISPPROF DFSMS INFORMATION CELL MISSING 19.04.33 VCA00607W >>>>> VOLUME=TSU026 - SYSID=PRD1 10MAY91:15:31:52.57 - VOL. NOT SUCCESSFULLY PROCESSED 19.04.33 VCA00607W 19.04.33 VCA00606W ?? TDKDSUK.ISR0002.BACKUP MANAGED DATA SET IN VVDS BUT NOT PRESENT IN VTOC 19.04.36 VCA00607W >>>>> VOLUME=TSU028 - SYSID=PRD1 10MAY91:15:31:52.57 - VOL. NOT SUCCESSFULLY PROCESSED 19.04.36 VCA00607W 19.04.36 VCA00606W ?? TDK179.HST9104C.TEMP1.CNTL MANAGED DATA SET IN VVDS BUT NOT PRESENT IN VTOC 19.04.36 VCA00602W >>>>> VOLUME=TSU029 - SYSID=PRD1 10MAY91:15:31:52.57 - ERRORS MATCHING VVDS (DFSMS CELL) DATA TO VTOC 19.04.36 VCA00602W 19.04.36 VCA00603W OS TDKMG11.SMF.DATA DFSMS INFORMATION CELL MISSING 19.04.37 VCA00603W OS TDK081.JCL.CNTL DFSMS INFORMATION CELL MISSING 19.04.37 VCA00602W >>>>> VOLUME=TSU030 - SYSID=PRD1 10MAY91:15:31:52.57 - ERRORS MATCHING VVDS (DFSMS CELL) DATA TO VTOC 19.04.37 VCA00602W 19.04.37 VCA00603W OS BACKUP.DATASETS.SETS1.LIST.G0059V00 DFSMS INFORMATION CELL MISSING 19.04.38 VCA00603W OS TDKKR11.BUNTRACE DFSMS INFORMATION CELL MISSING 19.04.55 VCA00608W >>>>> 0 DATA SETS IGNORED FROM 2 VOLUMES.
Figure 9-6. DAY090 MICSLOG DFSMS Exception / VTOC Restart Report
|
Copyright © 2014 CA.
All rights reserved.
|
|