Parallel test results will not match if BATfff suspend files are not initialized with data from the old unit. This will result in differences in the database numbers that are not related to product upgrades.
Initialize the test database by copying all database timespans (DETAIL, DAYS, WEEKS, MONTHS) from the old unit to the new unit before running the first parallel test. If you do not have space to copy the full databases, copy the DETAIL suspend files and the cycle 00 WEEKS and MONTHS files to the new unit. Here is a sample of code to copy the suspend files from one unit to the other.
//COPY EXEC MICSNDBx (WHERE x IS THE UNIT DATABASE ID) //ODETAIL DD DSN=oldprefix.DETAIL,DISP=SHR EXISTING (PROD) UNIT //NDETAIL DD DSN=newprefix.DETAIL,DISP=OLD NEW (TEST) UNI //SYSIN DD * PROC COPY IN=ODETAIL OUT=NDETAIL; SELECT BAT_JS01 BATSFI01 BATSFS01 BATSFW01 BATSFP01 BATSFA01 BATSF601 ;
Contact CA MICS Technical Support if you need assistance with this code or assistance copying the CYCLE 00 files for WEEKS and MONTHS.
The data should be copied the day before the parallel test is planned.
Release: MICSAC00200-12.8-MICS-Resource Management-Accounting and Chargeback Opt