Conversion Strategy of All Files which require special consideration as per OHC TRAMS history File Partitions Action

Item: Conversion Team to partition T A!S history as follows a" setting up S#S$ parameters %" creating T A!S inde& CHTI' file %y running the (T)*+,,, program and c" creating CHTH partitions %y running the (TCT$A T program from -ase Segment File. GRS1 / GRS3 files Action Item: Conversion Team to create the ( S files %y running the ( )+/, program FAS Log File Extension Action Item: Conversion Team 011) 0OT underta2e any conversion on the same as FAS 3og files are not in scope of Conversion. !oreover post OHC implementation FAS 3og file e&tents will %e esta%lished once Building of conversion. Action Item: Conversion Team to create all the Cross eference programs. eference files %y e&ecution the OHC Cross R!SS Referen"e Files # Cross reference files to %e %uilt as part of

Building the GRMR$% files & ( ! 4' files to %e %uilt as part of conversion. Action Item: Conversion Team to create the ( ! 4' files %y running the ( 567, program GFML' File( 1)* days Auth 'istory File In !e&ico 68, days Auth History data is present in HF!A5 file. As a part of *.9 upgrade (F!3H file will provide the 68, days auth history data with complete OF,6:S information. So e&isting HF!A5 file as it is we cannot use for creating new (F!3H file. It needs to %e %uilt using F-3( and HF!A5 information. In order to

achieve this; we require F-3( which have data for 68, days along with HF!A5 file which would populate some of the fields for (F!3H file. Currently the F-3( file generation limit is 6,. So in order to %uild (F!3H Auth History file with 68, days data the production support team needs to increase the limit of the F-3( ()(<s to around 66, from the %eginning of 0ovem%er 8,,/; 2eeping in view that the implementation is around !arch=8,6,; so that this data along with data from HF!A5 file could %uild (F!3H file for 68, days Auth History. AME File # This file needs to %e accordingly %uilt in the Conversion flow.

Action Item: As this file is not used in $!-,; Conversion Team can simply initiali>e the same during Conversion. 'istory Files & AS!?Footprints?Transactions?Statements files need to %e converted accordingly. Action Item: Conversion modules need to %e developed for the A!HS?( !@H?A!3)?A!S3 files as these files need to %e converted. ontrol Re"ord 'istory Files & H-!' -usiness need to ta2e a decision whether they need to carry the history of the control record changes Afiles li2e (!HI; (!HF; and (!H etc" to the new region. Action Item: After discussion with H-!'; Conversion modules need to %e developed accordingly. GRMR+ File( Glo,al Re-ort +es"ri-tion File Occurrences of this file have %een increased from 78 to 8+,. 1&isting -5 specific reports are still holds good with respective to the Occurrences. As this file is at Org level the occurrences will not %e pro%lem %ecause of the Chile clustering. As the Chile will have its own org record setup. -ut for the Similar (lo%al reports to get split Form code needs to %e updated differently for !e&ico and Chile. This can %e ta2en care %y Chile when they are actually setting up their control records.