ACT Auditing DASD Charges
MICS Accounting and Chargeback
Option draws data from the MICS Space Analyzer Option
's VCADAA file and, (Optional) from the VCA_VS file or HFSDIR. The VCADAA file contains both VSAM and non-VSAM data sets. The data is based on information obtained from the VTOCs. The VCA_VS file also contains VSAM data sets, but the data in this file is obtained from the ICF VSAM catalogs. Both files contain SMS data sets as well as non-managed data sets. The HFSDIR file is obtained from IBM's OS/390 UNIX Systems Services HFS File System.rm
MICS Accounting and Chargeback
Option draws data from the MICS Space Analyzer Option
's VCADAA file and, (Optional) from the VCA_VS file or HFSDIR. The VCADAA file contains both VSAM and non-VSAM data sets. The data is based on information obtained from the VTOCs. The VCA_VS file also contains VSAM data sets, but the data in this file is obtained from the ICF VSAM catalogs. Both files contain SMS data sets as well as non-managed data sets. The HFSDIR file is obtained from IBM's OS/390 UNIX Systems Services HFS File System.The VCA data is charged in one or more of the following four
MICS Accounting and Chargeback
Option journal files:- ACTJDA (DASD Journal File)
- ACTJMS (SMS Journal File)
- ACTJVS (VSAM Journal File)
- ACTJHF (HFS Journal File)
The journal files are created from the VCA files at either the DETAIL or DAYS timespan as determined by the ACCOUNTING DETAIL or ACCOUNTING DAYS statement in the VCAOPS member of prefix.MICS.PARMS.
The ACTJDA and ACTJMS journal files are always derived from the VCADAA file. The ACTJVS journal file is derived from the VCA_VS file and the ACTJHF journal file is derived from HFSDIR file.
HSM (Hierarchical Storage Manager) migrated data sets can be excluded from the ACTJDA and ACTJVS journal files using the HSM option on the General Installation Accounting Specifications panel. HSM data sets are identified by a value of 'HS' or 'HV' in the DAADSTYP variable.
This section explains how to audit the journal files that you are using against the VCADAA, VCA_VS, and HFSDIR FILEs.
- If only the ACTJDA DASD journal file is active:All data is obtained from the VCADAA file, but any observations in which all quantities being charged are less than or equal to zero are dropped from the journal file. The following SAS code can be used to audit the ACTJDA file against the VCADAA file.%INCLUDE SOURCE(#ACTOPTS); DATA WORK.JDA; SET &dVCAt..VCADAA01; (where d is the unit identifier, and t is either DETAIL or DAYS) IF DAADSTYP NE: "&HSMOPT"; IF quantity > 0; (where quantity is the name of the charging element) RUN;The WORK.JDA file should contain the same number of observations as the DETAIL.ACTJDA01 journal file, unless you are doing journal file prorating on this file.
- If the ACTJDA DASD and the ACTJMS SMS journal files are active:All data is obtained from the VCADAA file. Any observations in which all quantities being charged are less than or equal to zero are dropped from the journal files. SMS data sets are charged in the ACTJMS journal file and non-managed data sets are charged in the ACTJDA journal file. The following SAS code can be used to audit the journal files against the VCADAA file.%INCLUDE SOURCE(#ACTOPTS); DATA WORK.JDA WORK.JMS; SET &dVCAt..VCADAA01; (where d is the unit identifier, and t is either DETAIL or DAYS) IF quantity > 0; (where quantity is the name of the charging element) IF STORSTGC = ' ' THEN DO; IF DAADSTYP NE: "&HSMOPT" THEN OUTPUT WORK.JDA; END; ELSE OUTPUT WORK.JMS; RUN;The WORK.JDA and WORK.JMS files should contain the same number of observations as the DETAIL.ACTJDA01 and the DETAIL.ACTJMS01 journal files, respectively, unless you are doing journal file prorating on these files.
- If the ACTJDA DASD, the ACTJMS SMS, and the ACTJVS VSAM journal files are active:The data in the ACTJDA and ACTJMS journal files is obtained from the VCADAA file. The data in the ACTJVS journal file is obtained from the VCA_VS file. Any observations in which all quantities being charged are less than or equal to zero are dropped from the journal files.SMS data sets (VSAM and non-VSAM) are charged in the ACTJMS journal file; non-managed non-VSAM data sets are charged in the ACTJDA journal file, and non-managed VSAM data sets are charged in the ACTJVS journal file. The following SAS code can be used to audit the journal files against the VCADAA and VCA_VS files.%INCLUDE SOURCE(#ACTOPTS); DATA WORK.JDA WORK.JMS; SET &dVCAt..VCADAA01; (where d is the unit identifier, and t is either DETAIL or DAYS) IF quantity > 0; (where quantity is the name of the charging element) IF STORSTGC NE ' ' THEN OUTPUT WORK.JMS; ELSE IF (DAADSTYP = 'OS') OR (DAADSTYP = 'HS') THEN DO; IF DAADSTYP NE: "&HSMOPT" THEN OUTPUT WORK.JDA; END; RUN; DATA WORK.JVS; SET &dVCAt..VCA_VS01; (where d is the unit identifier, and t is either DETAIL or DAYS) IF quantity > 0; (where quantity is the name of the charging element) IF DAADSTYP NE: "&HSMOPT"; IF STORSTGC = ' ' THEN OUTPUT WORK.JVS; RUN;The WORK.JDA, WORK.JMS, and WORK.JVS files should contain the same number of observations as the DETAIL.ACTJDA01, the DETAIL.ACTJMS01, and the DETAIL.ACTJVS01 journal files, respectively, unless you are doing journal file prorating on these files.
- If the ACTJDA DASD and the ACTJVS VSAM journal files are active:The data in the ACTJDA journal files is obtained from the VCADAA file. The data in the ACTJVS journal file is obtained from the VCA_VS file. Any observations in which all quantities being charged are less than or equal to zero are dropped from the journal files.Non-VSAM data sets are charged in the ACTJDA journal file, and VSAM data sets are charged in the ACTJVS journal file. The following SAS code can be used to audit the journal files against the VCADAA and VCA_VS files.
%INCLUDE SOURCE(#ACTOPTS); DATA WORK.JDA; SET &dVCAt..VCADAA01; (where d is the unit identifier, and t is either DETAIL or DAYS) IF quantity > 0; (where quantity is the name of the charging element) IF (DAADSTYP = 'OS') OR (DAADSTYP = 'HS') THEN DO; IF DAADSTYP NE: "&HSMOPT" THEN OUTPUT WORK.JDA; END; RUN; DATA WORK.JVS; SET &dVCAt..VCA_VS01; (where d is the unit identifier, and t is either DETAIL or DAYS) IF quantity > 0; (where quantity is the name of the charging element) IF DAADSTYP NE: "&HSMOPT"; OUTPUT WORK.JVS; RUN;
The WORK.JDA and the WORK.JVS files should contain the same number of observations as the DETAIL.ACTJDA01 and the DETAIL.ACTJVS01 journal files, respectively, unless you are doing journal file prorating on these files.
- If the ACTJHF HFS journal file is active:All data is obtained from the HFSDIR file, but any observations in which all quantities being charged are less than or equal to zero are dropped from the journal file. The following SAS code can be used to audit the ACTJHF file against the HFSDIR file.%INCLUDE SOURCE(#ACTOPTS); DATA WORK.JHF; SET &dHFSt..HFSDIR01; (where d is the unit identifier, and t is either DETAIL or DAYS) IF DAADSTYP NE: "&HSMOPT"; IF quantity > 0; (where quantity is the name of the charging element) RUN;The WORK.JHF file should contain the same number of observations as the DETAIL.ACTJHF01 journal file, unless you are doing journal file prorating on this file.Although theMICS Accounting and ChargebackOption product supports HFS data for billing, we strongly discourage the use of the HFSDIR file for accounting due to the following:
- Only mounted file systems are scanned and contribute file information to the HFSDIR file.
- The space allocated for individual file(s) and/or directory(ies) does not account for the unused but allocated space in the file system.