Error when compiling job with "Occurs" clause

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
maheshalways
Participant
Posts: 13
Joined: Tue Jan 25, 2005 12:07 am
Location: Mumbai,India

Error when compiling job with "Occurs" clause

Post by maheshalways »

We have an Error "when checking composite operator: Output from subprocess: CC: Fatal error in ccfe: Segmentation Fault (core dumped)" when compiling job.We have flattened metadata using Sequential File Stage, there are 3880 fields.The cobol metadata used by the file contains Occurs clause which repeats 200 times.The Job has an input file, a parallel transformer and an output file.The transformation is straight forward with most of the values hard-coded.When we compile the job,we get the above error.

Possible Outcomes:

1) Is this from DataStage Side ?
Since there are 3880 fields,DataStage trying to write in Directory Structure or Core file and failing due to space issues

2) Is this from UNIX side ?
As we have core dump error during compilation.

Has anybody faced this before ? This has become a "show stopper" for us,any help on this would be highly appreciated.
Regards,
Mahesh (MP)
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Exactly how are you "flattening" the file with a Sequential File stage? As far as I am aware the Complex Flat File stage is the preferred stage for handling an OCCURS clause.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
maheshalways
Participant
Posts: 13
Joined: Tue Jan 25, 2005 12:07 am
Location: Mumbai,India

Post by maheshalways »

ray.wurlod wrote:Exactly how are you "flattening" the file with a Sequential File stage? As far as I am aware the Complex Flat File stage is the preferred stage for handling an OCCURS clause.
Mahesh:
Please refer the part of cobol format from the file,Ray,we had used complex flat file too,but here "BEC-ENTDETS", "BEC-SVCDETS" and "BEC-SUBBCH-USE" fields are created in the Metadata and they need to be mapped / or assigned value in the transformer.If we specify default values for these fields or remove them from the Meta-data it still gives compilation error.So we had used Seqential Flat file,with flattened meta-data in this case the above fields do not appear in Metadata and hence do not need mapping or assigning default values.

10 BEC-ENTDETS OCCURS 200 TIMES.
15 BEC-ENTVOL-BCUT-DEF PIC S9(11) COMP-3.
15 BEC-ENTVOL-ACUT PIC S9(11) COMP-3.
15 BEC-ENT-ACLEV-PRICE PIC S99V999 COMP-3.
15 BEC-ENT-ZERO-PRICE PIC S9 COMP-3.
10 BEC-SVCDETS OCCURS 300 TIMES.
15 BEC-SVC-VOL-ACHG PIC S9(11) COMP-3.
15 BEC-SVC-AMT-ACHG PIC S9(9)V99 COMP-3.
15 BEC-SVC-VOL-TBCHG PIC S9(11) COMP-3.
15 BEC-SVC-AMT-TBCHG PIC S9(9)V99 COMP-3.
15 BEC-SVC-AMTNO-TBCHG PIC S9(11) COMP-3.
15 BEC-SVCQTR-ATT PIC S9 COMP-3.
15 BEC-SVCOS-NOS PIC S9 COMP-3.
15 BEC-SVC-ACLEV-PRICE PIC S99V999 COMP-3.
15 BEC-SVC-ZERO-PRICE PIC S9 COMP-3.
10 BEC-FIRST-CR-INT-DATE PIC XX.
10 BEC-LSTGRP-STDATE PIC XX.
10 FILLER2 PIC XX.
10 BEC-LST-DR-DATE PIC XX.
10 BEC-LST-CR-DATE PIC XX.
10 BEC-SAME-DAY-ENT PIC S9(11) COMP-3.
10 BEC-SUBBCH-USE PIC S999 COMP-3 OCCURS 50 TIMES.
10 BEC-LEND-FEES OCCURS 60 TIMES.
15 BEC-LF-AT-THE-TIME PIC S9(9)V99 COMP-3.
15 BEC-LF-QTLY-OFFSET PIC S9(9)V99 COMP-3.
Regards,
Mahesh (MP)
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Mahesh,

is the core file generated from the compiler or from DataStage? (you can use dbx or mdb or get your System Administrator to tell you). There is little Ascential can do if it is the compiler coring out.
maheshalways
Participant
Posts: 13
Joined: Tue Jan 25, 2005 12:07 am
Location: Mumbai,India

Post by maheshalways »

ArndW wrote:Mahesh,

is the core file generated from the compiler or from DataStage? (you can use dbx or mdb or get your System Administrator to tell you). There is little Ascential can do if it is the compiler coring out.
ArndW,

Thanks for your reply.Can you please elaborate on dbx or mdb ?? What should I request the UNIX System Administrator to do to solve the problem ?
Regards,
Mahesh (MP)
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Mahesh,

a core file can give detailed information on why a program aborted. The two programs I listed can be used to analyze core files; but they are quite complex and since you haven't used them before I wouldn't recommend starting now. Either your Administrator knows how to analyze them or not. But you you always look at the text part of the core file (use dd) to see if it was generated from the compiler or from DS to narrow down the source of your problem.
Post Reply