PX Job Compilation Error

myotoo · Post by **myotoo** » Tue Jan 30, 2007 10:51 pm

Hi All,

I'm getting C Compiler error on compiling PX job. Can't find compiler /usr/vacpp/bin/xlC_r as mentioned in configuration file. How can I find C compiler? Is it in PX installer?

Thanks,

Output from transformer compilation follows:

##I TFCN 000001 11:17:08(000) <main_program>
Ascential DataStage(tm) Enterprise Edition 7.5.1A
Copyright (c) 2004, 1997-2004 Ascential Software Corporation.
All Rights Reserved

##I TUTL 000031 11:17:08(001) <main_program> The open files limit is 2000; raising to 2147483647.
##I TOSH 000002 11:17:08(002) <main_program> orchgeneral: loaded
##I TOSH 000002 11:17:08(003) <main_program> orchsort: loaded
##I TOSH 000002 11:17:08(004) <main_program> orchstats: loaded
##I TFSC 000001 11:17:08(007) <main_program> APT configuration file: /home/dsadm/Ascential/DataStage/Configurations/default.apt
##W TCOS 000049 11:17:09(000) <main_program> Parameter specified but not used in flow: DSPXWorkingDir
##E TBLD 000000 11:17:09(002) <main_program> Error when checking composite operator: Subprocess command failed with exit status 32,512.
##E TFSR 000019 11:17:09(003) <main_program> Could not check all operators because of previous error(s)
##W TFCP 000000 11:17:09(004) <transform> Error when checking composite operator: The number of reject datasets "0" is less than the number of input datasets "1".
##W TFCP 000025 11:17:09(005) <transform> Error when checking composite operator: Converting ustring to string using codepage ibm-1162.
##W TFCP 000000 11:17:09(006) <transform> Error when checking composite operator: Implicit conversion from source type "UString" to result type "String".
##W TBLD 000000 11:17:09(007) <main_program> Error when checking composite operator: Output from subprocess: sh: /usr/vacpp/bin/xlC_r: not found

##I TFCP 000000 11:17:09(008) <transform> Error when checking composite operator: /usr/vacpp/bin/xlC_r -O -I/home/dsadm/Ascential/DataStage/PXEngine/include -O -c -qspill=32704 /home/dsadm/Ascential/DataStage/Projects/PXTRAIN/RT_BP3.O/V1S5_jGIF_GLOBAL_VEH_2227_Trn3.C -o /home/dsadm/Ascential/DataStage/Projects/PXTRAIN/RT_BP3.O/V1S5_jGIF_GLOBAL_VEH_2227_Trn3.tmp.o.
##E TCOS 000029 11:17:09(009) <main_program> Creation of a step finished with status = FAILED. (jGIF_GLOBAL_VEH_2227.Trn3)

*** Internal Generated Transformer Code follows:
0001: //
0002: // Generated file to implement the V1S5_repos_Trn3 transform operator.
0003: //
0004:
0005: // define our input/output link names
0006: inputname 0 Lkp_Trn3;
0007: outputname 0 Global_Vehicle_Suspense_Write;
0008:
0009: initialize {
0010: // define our row rejected variable
0011: int8 RowRejected0;
0012:
0013: // define our null set variable
0014: int8 NullSetVar0;
0015:
0016: // declare our intermediate variables for this section
0017: string InterVar0_0;
0018:
0019: // initialise constant values which require conversion
0020: InterVar0_0 = "N";
0021: }
0022:
0023: mainloop {
0024: // initialise our row rejected variable
0025: RowRejected0 = 1;
0026:
0027: // declare our intermediate variables for this section
0028: string InterVar0_1;
0029:
0030: // evaluate columns (no constraints) for link: Global_Vehicle_Suspense_Write
0031: Global_Vehicle_Suspense_Write.SQUISH_VIN = Lkp_Trn3.SQUISH_VIN;
0032: if (null(Lkp_Trn3.VEH_IDENT_NBR_1)) {
0033: Global_Vehicle_Suspense_Write.STATUS_CD = InterVar0_0;
0034: } else {
0035: InterVar0_1 = Lkp_Trn3.STATUS_CD;
0036: Global_Vehicle_Suspense_Write.STATUS_CD = InterVar0_1;
0037: }
0038: //;
0039: writerecord 0;
0040: RowRejected0 = 0;
0041: }
0042:
0043: finish {
0044: }
0045:
*** End of Internal Generated Transformer Code

DSguru2B · Post by **DSguru2B** » Tue Jan 30, 2007 10:56 pm

Its the APT_COMPILER and APT_LINKER environment variables. Check in the datastage administrator for its values and verifty whether the compiler exists. Plus the error is also due to implicit conversion between data types. Use the appropriate data type function for the conversion.

myotoo · Post by **myotoo** » Wed Jan 31, 2007 12:08 am

[quote="DSguru2B"]Its the APT_COMPILER and APT_LINKER environment variables. Check in the datastage administrator for its values and verifty whether the compiler exists. Plus the error is also due to implicit conversion between data types. Use the appropriate data type function for the conversion.[/quote]

I cannot find compiler in /usr/vacpp/bin/xlC_r which is defined in Configuration file APT_COMPILER and APT_LINKER. How should i get this compiler?

Thanks

ray.wurlod · Post by **ray.wurlod** » Wed Jan 31, 2007 12:13 am

The compiler must be separately purchased, typically from your operating system vendor.

DSguru2B · Post by **DSguru2B** » Wed Jan 31, 2007 8:15 am

I asked you to check for those env. variables in DataStage Administrator and not the configuration file.
Is this a new installation? Did you ever get a job to compile with transformer as part of the design?

myotoo · Post by **myotoo** » Thu Feb 01, 2007 11:16 pm

Both APT_COMPILER and APT_LINKER env. variable hold "/usr/vacpp/bin/xlC_r" and cannot find compiler in this location. This is first time we develop PX job with transformer.

Thx

ray.wurlod · Post by **ray.wurlod** » Fri Feb 02, 2007 1:28 am

You must have a compatible C++ compiler to compile jobs containing Transformer and Build stages.

Do you have a C++ compiler?

None installs with DataStage - you must provide it yourself.

DSguru2B · Post by **DSguru2B** » Fri Feb 02, 2007 7:47 am

myotoo wrote:This is first time we develop PX job with transformer.

No wonder your error. More than likely, its what Ray has diagnosed. Get your architect or someone at a higher level involved and bring this to his/her attention. You need a compatible C compiler. Search this website for more specifics.