Search found 733 matches
- Thu Dec 13, 2018 10:50 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Read Binary file from AS400
- Replies: 9
- Views: 7927
The z/OS stage still requires a connection channel which your source platform must support, and on which they must grant your application access. FTP, however, is simpler. All they need to do is grant your ftpid authority to logon to their system, and give it access to the file you need. FTP Enterpr...
- Fri Dec 07, 2018 10:05 am
- Forum: General
- Topic: Sequence Job Activity Trigger for OK and another for Failed
- Replies: 2
- Views: 2646
Is this 18 jobs that run one at a time sequentially, or do they kick off simultaneously, or in groups? In any case, what is your job recovery requirement? Do you rerun jobs that already completed okay, or do you want to skip them? Terminator stages are part of the mix. If you want spot recoverabilit...
- Wed Nov 28, 2018 10:19 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: COBOL file without copybook
- Replies: 98
- Views: 48587
- Wed Nov 28, 2018 9:20 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: COBOL file without copybook
- Replies: 98
- Views: 48587
At this point, I have an unhelpful observation to make: you are not dealing with standard COBOL formatting. You are dealing with undisciplined formatting out of COBOL coding. They have set for you an impossible obstacle: reading a file with inconsistent record lengths. One more thing you might check...
- Tue Nov 27, 2018 12:15 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: COBOL file without copybook
- Replies: 98
- Views: 48587
- Tue Nov 27, 2018 10:54 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: How to create COBOL file with OCCURS clause?
- Replies: 5
- Views: 2950
I suppose a transformer loop would be a good approach. You need to do several things here. You have to know how many instances of the OCCURS you need to use for each input row. Will it always be the same number? Is there a direct link between the number of address columns in the .csv file and the ou...
- Tue Nov 27, 2018 10:44 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: COBOL file without copybook
- Replies: 98
- Views: 48587
Assumptions: Input record length is 16336 bytes. First 10 bytes is record type indentifier. Every record is consistently of that length. You must preserve the EBCDIC character set. Sample table definition: REC_TYPE Char(10). DATA_COLUMN Binary(16326). You can use Sequential File stage for this. Set ...
- Mon Nov 26, 2018 10:18 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: COBOL file without copybook
- Replies: 98
- Views: 48587
- Mon Nov 26, 2018 7:06 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: COBOL file without copybook
- Replies: 98
- Views: 48587
Rumu, There's too much going on here for you to keep up with the details. I strongly recommend sitting with your mainframe developer and going through an exercise in simplification. On the copybook, as they created it, get help with flattening the groups manually. Edit the copybook before importing ...
- Fri Nov 23, 2018 7:35 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: COBOL file without copybook
- Replies: 98
- Views: 48587
Rumu, Please confirm that the following is accurate: FROM TO FIELD LENGTH PICTURE 1 75 CHD-RECORD 75 X(75) 76 77 CHD-NO-SEG 2 S9(4)V COMP 78 79 CHD-ALP-SEG 2 S9(4)V COMP If it is accurate, those are not packed decimal fields. They are binary numeric fields that are sql type integer or double or of t...
- Tue Nov 20, 2018 11:17 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: COBOL file without copybook
- Replies: 98
- Views: 48587
The reference you found is incorrect. COMP-3 storage length -- the bytes it takes up on the file -- is number of integer places divided by two and add one, round up for odd number of places. PIC S9(4) COMP-3: 4 divided by 2, add 1, storage length is 3. Storage, hexadecimal representation: 1,234 (or ...
- Tue Nov 20, 2018 10:35 am
- Forum: General
- Topic: Automated deployments using Team Foundation Server?
- Replies: 4
- Views: 4832
Novak, our protocol as an example: Code and unit test in DEV, export design only. Import design to INT (integration), compile and test. Export design and executable from INT. Import design and executable to SAT/CAT (test). Run final tests. Export design and executable from SAT/CAT (or, with no test ...
- Tue Nov 20, 2018 10:29 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: COBOL file without copybook
- Replies: 98
- Views: 48587
Rumu, Read the using mainframe FAQ linked below for details on handling packed decimal. Your column length for PIC S9(4)V COMP-3 is 3 bytes: counting the integer places you would see in the file 01 23 4F. As for parsing, you can define the file stage input single column as Char, even though it doesn...
- Tue Nov 20, 2018 8:55 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: COBOL file without copybook
- Replies: 98
- Views: 48587
- Mon Nov 19, 2018 1:25 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: COBOL file without copybook
- Replies: 98
- Views: 48587