That is what documentation is for. There is nothing magic about COBOL records, but there are things that need to be taken care of when they are extracted. Since he is being given an extract file presumably pulled via a progam, chances are most issues are resolved.

Any file or table from where we can extract the data in PowerCenter is referred to as the Source. You can import or create the source definition.When you. Mar 26, 2017. Informatica basic study. Sorter Transformation Can sort data from relational tables or flat files Sort takes place on the Informatica. Informatica PowerExchange. Today's IT organizations face growing demand for timely access to critical operational data stored in VSAM files on IBM. Informatica PowerCenter. Processing VSAM sources with OCCURS and REDEFINES statements requires knowledge of how the PowerCenter Normalizer transformation object handles VSAM data. The VSAM source in this example includes data about four different suppliers, each stored in the same record. The source file contains.

As for OCCURS clauses, there is always a fixed number of occurances. If a record contains an OCCURS.VARYING array, there can only be one and it must be the last set of fields in the record (that is the rule and COBOL enforces it).

So for those you simply define (in the input record definition) the maximum number of occurances. Occurances that are not in the input will be null. Redefines are only a problem if the output file contains more than one record format. Download Finacle Banking Software. In which case there is usually a leading field that contains a code that identifies the record type. A simple preprocess mapping to split the records up by type can make handling these types of files very simple. -----Original Message----- Cobol data are complex, it includes occurs and redefine kind of thing,so if your source sequential file is direct extract from cobol source,you can't determine which data you need to load, and which data is therefor occurs or redefine.So if you go for flat file load directly properdata will not be loaded.

Cobol data are complex, it includes occurs and redefine kind of thing, so if your source sequential file is direct extract from cobol source, you can't determine which data you need to load, and which data is there for occurs or redefine.So if you go for flat file load directly proper data will not be loaded. ________________________________ From: sreedhar.raju via informatica-l [mailto:informatica-l@Groups.ITtoolbox.com] Sent: Wednesday, February 20, 2008 8:07 PM To: Das, Sucharita (Cognizant) Subject: RE: [informatica-l] Problem with VSAM Source extraction Posted by ysreedharraju on 09:40:00 AM I have a basic question.If client is providing data in form of sequential files using cobol extract scripts,Still i need to use copy book or i can directly treat that sequential file as flat file and import definition same as flat file? ________________________________ From: eranti via informatica-l [mailto:informatica-l@Groups.ITtoolbox.com] Sent: Wed 2/20/2008 3:47 PM To: Sreedhar Raju Y (WT01 - ENERGY & UTILITIES) Subject: Re: [informatica-l] Problem with VSAM Source extraction We have include some headers and footers for the copy book for uploadinginto the designer.And care should be taken about datatypes.For example *Header is like this*** identification division. Environment division. Select FC8RNSR assign to 'FC8RNSR'. Data division. File section.