Search found 5 matches

by mpathak66
Sat Feb 28, 2015 11:09 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Compilation Issue in Parallel Job
Replies: 15
Views: 7757

Looks like its not a trial version since IBM agreed Warranty Support for an year.
by mpathak66
Sat Feb 28, 2015 10:40 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Compilation Issue in Parallel Job
Replies: 15
Views: 7757

Below are the requested details: Compiler Verison: /apps/ptadm/dstage/IBM/InformationServer/Server/DSEngine ->/usr/vacpp/bin/xlC -qversion IBM XL C/C++ for AIX, V11.1 (5724-X13) Version: 11.01.0000.0000 Compiler Edition: /apps/ptadm/dstage/IBM/InformationServer/Server/DSEngine ->lslpp -l | grep -i v...
by mpathak66
Sat Feb 28, 2015 12:47 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Compilation Issue in Parallel Job
Replies: 15
Views: 7757

1. Before 02/20, we could able to compile any parallel job and run. From 02/22, we cannot able to compile any parallel job with Transformer. Except adding UNLOCK Entry to VOC file(Project level), there was no other change. IBM too confirmed that there is no relation with UNLOCK entry and compiler er...
by mpathak66
Sat Feb 28, 2015 1:21 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Compilation Issue in Parallel Job
Replies: 15
Views: 7757

Hi Mike, Once we did force compile, we cannot able to compile any parallel job with Transformer. Earlier it was working. Below are the current Compiler Parameters: $APT_COMPILEOPT=-O -q64 -c $APT_COMPILER=/usr/vacpp/bin/xlC_r $APT_LINKER=/usr/vacpp/bin/xlC_r $APT_LINKOPT=-G -q64 I have tested the co...
by mpathak66
Fri Feb 27, 2015 1:16 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Compilation Issue in Parallel Job
Replies: 15
Views: 7757

Re: Compilation Issue in Parallel Job

We tried running one sample c program and its able to compile and generate the .o file. SO, it seems there is no issue with the compiler. When we checked the RT_BP_XXX.o folder after compilation where the the .o file will be generated, we did not see the .o file. So, its not able generate the .o fil...