DSXchange

ok thanks,

i'll contact ibm to find out what the cost will be for just the WsPack.

thnaks for your help,

steve

chulett wrote:From IBM. In exchange for money.

craig,

thanks - i did not realize this was a separately purchasable item. Does it only come as part of the RTI option?

thanks,

steve

from reading postings here, i gather i need to install the WSPack inorder for a datastage job to act as a webservices (soap) client.

where do i get the WsPack from?

DS 7.5.2, suse linux.

thanks a lot,

steve

Craig, i used -local so that i could override the environment variables by putting them in my script if the need arose (this was a generic script). it never occurred to me that this option may be affecting the operation of the '-wait' parameter ans so never tested that. and no, i did not go to IBM o...

ray.wurlod wrote:Status 0 can also mean that the job is already running. which also explains why an approach involving polling was required.

but the whole problem is that the '-wait' did not wait in the first place - that's why we had to resort to polling

thanks,

steve

tcs wrote:If you have to use "-local", one work around is to have your shell script loop and poll for the job status, effectively coding the -jobstatus function yourself.

That's basically what we had to do. The polling seems to be working - it was just a pain that we had to do it.

thanks,

steve

Is this the bug that evans036 mentions a patch being available for? It might be related. I was specifically using the 'external filter' which i can imagine would have common functionality. in your case though, parallelism would force your csv file to be read in its entirety once for each parallel s...

what i thought was a generic problem with datastage (ie not trapping fatal errors) turned out to be a specific datastage/oracle problem that occurs when oracle rebuilds indexes. IBM gave me a fix yesterday which is to set the following parameter in the DataStage Administrator and run the job again. ...

APT_LOOKUP_VERBOSE Causes the lookup operator to print some information when it has completed loading a lookup table into memory. APT_PM_PLAYER_MEMORY Causes each player process to use APT_LOGMSG to report the process heap memory allocation when returning from runLocally(). thankyou very much, i'll...

Have you tried to force the lookup to be partitioned? Maybe you will be able to spread your data across nodes and therefore minimize your overall volume.... that is a good idea and will likely work in most cases. This is an excercise where i am trying to understand what memory constraint is causing...

sanjay,

this particular lookup is built on a unique key - so in this case it would not help.

btw, are dups not 'allowed' in lookups?

thanks,

steve

are you getting 32 bit limits.try using file less than 2GB . that's a good question. i did try a file size of about 1.5GB and that did not work. anything under 1GB seems to work. so i am assuming its not a 32 bit limitation. IBM are saying its shared memory. bumping up the shared memory max & r...

Those ulimit values look good. Are you using the same dataset in 2 or more lookups in your job? no. the job is like this: dataset -> transformer -> lookup btw, i logged a case with IBM. They are saying it is a shared memory shortage. The lookup dataset is about 3GB and the SHMMAX is set to 1GB so t...

Can you add a call in your before-job to issue a "ulimit -a" and see what the actual runtime values are? excellent idea. the output yielded this: BLCreateLUFS..BeforeJob (ExecSH): Executed command: ulimit -a *** Output from command was: *** core file size (blocks, -c) 0 data seg size (kby...

thanks for the reponse. scratch pool has about 300GB watching process memory of LUT_CreateOp using command: pmap -x all i see is 45MB of memory used by that process throughout job execution. maybe i'm looking in the wrong place? here is 'ps' output: 1 R evans036 27205 27202 99 85 0 - 11279 - 22:09 ?...