Creating Multiple Format Flat File
Posted: Fri Apr 18, 2014 4:34 pm
Im working on a project for an insurance firm where they want to use Datastage to generate a Multi Format Flat File . Currently this is being done programatically on a Mainframe platform [ using COBOL of course ]
but they want to now source the data from an Open systems Oracle DB and create the same file using Datastage [ Server Edition ] .
The File has 7 records types in the data payload itself , and has 3 types of header records [ 1 per file] and one trailer record. so totally 11 record types. As if this was not enough there are dependencies between the 7 data record types between policy and agentr ecord for example and party and party address record etc - based on policy number and other link key columsn . I knwo with workarounds - we can do it in Datastage Server edition - although it would be quite a pain to maintain, but is there a good justification of pushing this requirement out of Datastage to some other programmatic language for this requirement ?
Im not quite convinced that using Datastage is the best way to satisfy this requirement. Here is the looping diagram that describes the file & record structure itself
but they want to now source the data from an Open systems Oracle DB and create the same file using Datastage [ Server Edition ] .
The File has 7 records types in the data payload itself , and has 3 types of header records [ 1 per file] and one trailer record. so totally 11 record types. As if this was not enough there are dependencies between the 7 data record types between policy and agentr ecord for example and party and party address record etc - based on policy number and other link key columsn . I knwo with workarounds - we can do it in Datastage Server edition - although it would be quite a pain to maintain, but is there a good justification of pushing this requirement out of Datastage to some other programmatic language for this requirement ?
Im not quite convinced that using Datastage is the best way to satisfy this requirement. Here is the looping diagram that describes the file & record structure itself
Code: Select all
10 - Submitting Header - Mandatory - 1 - occurrence required for each file.
12 - Contra Header - Mandatory - 1 - occurrence for each contra party sent.
[+] 13/Seq01 - Contract Record - Mandatory - (99,999,999 occurrences per Contra Header, at least one is required.)
13/Seq02 - Contract Valuation Record - Optional - (20 occurrences per Contract Record)
[+] 13/Seq03 - Contract Underlying Assets Record - Optional - (999 occurrences per Contract Record)
13/Seq04 - Contract Band/Guaranteed Loop with Underlying Assets Record - Optional -
(999 occurrences per Contract Underlying Assets Record) (If 13/04 is present, then 13/03 is required)
[+] 13/Seq05 - Contract Agent Record - Optional - (25 occurrences per Contract Record)
13/Seq06 - Contract Dates Record - Optional - (1 occurrence per Contract Record)
[+] 13/Seq07 - Contract Events Record - Optional - (2 occurrences per Contract Record)
[+] 13/Seq09 - Contract Party Record - Optional - (99 occurrences per Contract Record)
13/Seq10 - Contract Party Address Record - Optional - (1 occurrence per Contract Party Record)
[+] 13/Seq11 - Contract Annuitization Payout Record - Optional - (10 occurrence per Contract Party Record)
[+] 13/Seq15- Service Feature Record - Optional - (99 occurrences per Contract Record)
(1) (2) (3) (4) (5) (6)