Search found 215 matches

by nick.bond
Mon Oct 08, 2007 12:12 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Control Job Aborts Unexpectedly - DSD.WriteLog
Replies: 13
Views: 14143

Thanks for replies. I will check these ideas when I get back to work.

Regards, Nick.
by nick.bond
Sun Oct 07, 2007 2:58 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Control Job Aborts Unexpectedly - DSD.WriteLog
Replies: 13
Views: 14143

I can get the name of the program with

Code: Select all

LIST VOC "DSD.WriteLog" F2 F3
and the column F2 is
DSD_BP.O/DSD_WriteLog.B
But using different variations of the second command you provided I can't get the desired output. Can anyone help with the correct syntax?

Thanks, Nick.
by nick.bond
Sun Oct 07, 2007 1:44 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Control Job Aborts Unexpectedly - DSD.WriteLog
Replies: 13
Views: 14143

Craig,

We are performing a migration for the client, up until now we have performed many practice runs successfully and now that we are performing the migration for real we have this issue.
by nick.bond
Sun Oct 07, 2007 1:42 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Control Job Aborts Unexpectedly - DSD.WriteLog
Replies: 13
Views: 14143

This code has not changed since we ran a full system regression test last Wednesday with exactly the same code taken from version control. As this is the production cutover I can't run trials in other projects so can't check if it is just this project or not. There are many jobs (multi-instance) tha...
by nick.bond
Sun Oct 07, 2007 9:42 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Control Job Aborts Unexpectedly - DSD.WriteLog
Replies: 13
Views: 14143

Control Job Aborts Unexpectedly - DSD.WriteLog

Hi, We have a job "ExecJobJC" which calls a routine ExecJob to run other jobs. It has been working fine for a very long time and suddenly as we are performing the real migration it is falling over when trying to call some jobs. It is intermittent, if the the job is restarted after the abor...
by nick.bond
Wed Aug 29, 2007 4:21 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Common Memory performance - read/write
Replies: 12
Views: 3028

I had adapted the code you provided to add the new sequences onto the end of the array anyway, INS vSequenceName BEFORE vSeqArray<1,-1> INS 0 BEFORE vSeqArray<2,-1> INS 0 BEFORE vSeqArray<3,-1> LOCATE vSequenceName IN vSeqArray<1> SETTING vPos Then GoTo GetNextSeqRange but I am still not sure that t...
by nick.bond
Tue Aug 28, 2007 10:46 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Common Memory performance - read/write
Replies: 12
Views: 3028

Excellent thanks, I will try it with the array as you specified. I don't think there is any need to lock the array though because it is only available to the current process. If multiple jobs are using the routine, each process will have it's own version of the array with a different range of cached...
by nick.bond
Tue Aug 28, 2007 8:59 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Common Memory performance - read/write
Replies: 12
Views: 3028

Thanks Ken. I have now added the file handle into COMMON as you had in your routine. The one limitation of your routine is that it doesn't handle more than one sequence being used in the same transformer/process. I have tried to handle this by using an array that holds all the sequences being access...
by nick.bond
Tue Aug 28, 2007 1:34 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Common Memory performance - read/write
Replies: 12
Views: 3028

I did remove that on purpose because I thought the file was being opened every time a new range was required anyway. Was I incorrect in this? I had added some debug statements to show what was happening and they reported that the file was being opened each time anyway even with the memory statements...
by nick.bond
Mon Aug 27, 2007 6:11 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Common Memory performance - read/write
Replies: 12
Views: 3028

Thanks for the help - it turns out there was nothing wrong with my design or routine, it was simply that I had left a statement in there which was getting the process ID through DSGetJobInfo. This is why the performance was so bad and nothing to do with reading from shared memory. Once I had removed...
by nick.bond
Tue Jul 17, 2007 4:01 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Memory problem - Routine value - Abnormal termination
Replies: 10
Views: 3430

There is only one value for ULIMIT in uvconfig, but a few values for ulimit at the unix/user level. What does the ULIMIT in uvconfig control? If I set the value in uvconfig higher than the corresponding value of root's ulimit will I the increase the ulimit value at runtime? or does this only work fo...
by nick.bond
Tue Jul 17, 2007 1:06 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Memory problem - Routine value - Abnormal termination
Replies: 10
Views: 3430

Yep - the ulimit values are coming from root so I'll have to try and get them changed.

Thanks for all your help.
by nick.bond
Tue Jul 17, 2007 12:57 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Memory problem - Routine value - Abnormal termination
Replies: 10
Views: 3430

Thanks, smat is handy! * MFILES = 1500 * T30FILE = 2500 * GLTABSZ = 150 * RLTABSZ = 150 * SYNCALOC = 0 * MAXRLOCK = 149 * UDRBLKS = 0 * IMPERSONATION = 1 * INSTANCETAG = ade We performed a non-root install but seem to be running in Impersonation mode. I''l try and get the ulimt of root.
by nick.bond
Tue Jul 17, 2007 12:07 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Memory problem - Routine value - Abnormal termination
Replies: 10
Views: 3430

We are using HP-UX 11.1
by nick.bond
Tue Jul 17, 2007 12:03 am
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Memory problem - Routine value - Abnormal termination
Replies: 10
Views: 3430

When run from the jobs the ulimit result is quite different: DEV time(seconds) unlimited file(blocks) unlimited data(kbytes) 4063168 stack(kbytes) 131072 memory(kbytes) unlimited coredump(blocks) 4194303 nofiles(descriptors) 4000 PROD time(seconds) unlimited file(blocks) unlimited data(kbytes) 38020...