A coworker mentioned Informatica recognizes it like PIC S9(9)V9(2) COMP-3
, and so I had to defined the field with Prec 11
- Scale 2
, and I did that, but once data gets loaded in Stage table in SQL, then some fields show strange symbols for some columns, and other columns show expected values.">
I'm working in PowerCenter Designer on a Cobol Mainframe VSAM sourcefile and need to know what values in Prec
and Scale
should I use to get a PIC S9(9)V99 COMP-3
..
A coworker mentioned Informatica recognizes it like PIC S9(9)V9(2) COMP-3
, and so I had to defined the field with Prec 11
- Scale 2
, and I did that, but once data gets loaded in Stage table in SQL, then some fields show strange symbols for some columns, and other columns show expected values.
48 Mainframe Informatica ETL Developer jobs available on Indeed.com. Cs go for pc. Apply to ETL Developer, Senior Informatica Developer. Experience working with Mainframe VSAM files Required 2. Enterprise Data Warehouse is seeking a motivated candidate to fulfil the Responsibilities of supporting.
I also tried adding an Expression transformation for dividing by 100 the resulting value gotten from the Normalizer, but it didn't work as expected either.
You can import PowerExchange data maps for nonrelational data sources into Informatica Developer (the Developer tool) as nonrelational data objects. You can then use the tables that the nonrelational data object contains in mappings, mapplets, and profiles. Install PowerExchange server on Informatica server machine. Create a datamap for COBOL in PowerExchange Navigator tool. Launch Developer Tool/Client. Open the Connection Explorer. Configure connections. S elect Non-Relational. Select either Sequential or VSAM depending on how the datamap was configured in step-3 above. Informatica Informatica Advance Concepts Normalizer transformation (Working with VSAM source) Normalizer transformation (Working with VSAM source). How can i preview data of VSAM file from Informatica as we do for flat files through source definition of flat file. I am changing a established mapping where it is throwing up errors while. Currently we are processing COBOL file (VSAM) in INFA 10.1 smoothly. The files are getting pushed from upstream system to INFA server directly. Now we need to process the same COBOL file (VSAM) in BDM (10.2). VSAM file access modes given in this post to handle VSAM files in COBOL modules. Opening a VSAM file in Rational Developer for System z without File Manager installed is not supported. File Manager is a prerequisite for opening a VSAM file in Rational. VSAM (Virtual Storage Access Method). Using VSAM, an enterprise can. Many corporations run both old and new applications on mainframes that access VSAM files.
Do you have any idea about how could it be handled?
Giulio CaccinThe 'pic s9(9)V99 COMP-3
' is interpreted as follows:
s -- signed.9(9) nine number digits.V the implied decimal point.99 -- two numeric digits comp-3 -- packed decimal.
In informatica this would be 'prec 11 scale 2
'.Cannot remember how you tell Power Center its packed decimalbut I know you can.
Packed Decimal: two decimal digits in each byte with a special sign character in the last nibble.So +123456 is stored as hexadecimal '0123456C'.
( +123.456 would be stored as exactly the same hex string -- you just have to know what the scale you are expecting!)
Remember that a comp-3 field means that the value is compressed, so if you open with a text editor will show you those strange characters not the specific numberyou can saw those values with the extension PowerExchange
Be the first to see new Mainframe Informatica ETL Developer jobs |