DSXchange

02133 0500E : 0A4 gosub 0522C: 02134 05014 : 06E eq ErrorMsg "" => $R246 02134 0501C : 2DE testfw $R246 0502A: 02135 05024 : 0F8 move Decoded => DECRYPTED.VALUE 02135 0502A : 0C2 jump 05036: 02138 05030 : 0F8 move PARAM.VALUE => DECRYPTED.VALUE 02141 05036 : 06E eq DECRYPTED.VALUE "$...

Never old enough to learn...

Hmm that didn't solve the problem... I'm now skipping all encrypted parameters when passing the paramlist to the UtilityRunJob...

So the problem seems to be elsewhere...

Any proper way to catch the VLIST DSD_BP DSD_RUN.B output ? retyping 30 lines of code does not appeal to me that much....

Hmmm seems to be somewhere around the Environment variable passing... "Job parameter is not encrypted, but environment variable definition is encrypted...." We are in fact using the UtilityRunJob in this specific sequence to fire of jobs... And the paramlist is build as a string, though th...

That narrowed down the problem.... A file was created in the &PH& project subdirectory containing a phantom: DataStage Job 277 Phantom 4400 Program "DSD.RUN": Line 2156, Variable previously undefined. Zero length string used. But then again... the generated code in RT_BP277 only co...

Yes. Unfortunately no extra info was logged.

thanks,

William

Hi all, any clues on return code 96 ('Job was stopped by some indeterminate action') ?! Can't think of any indeterminate actions.... :( According to the director log the sequence finished ok but the scheduling software receives return code 96.... Happens for multiple sequences... Tried searching the...

We worked around the problem bij doing the count on the lookup table first (with the same key values). If count > 1 we log the key. Not the cleanest solution imho, but it does the job... So any real solutions are still welcome....

Ray, thanks for the reply. As a matter of fact that's exactly the way we currently figure it out at a runtime 'incident'. But what we are actually trying to achieve is that the (keys of) the row(s) causing the warning, also come forward in the Director warning log automatically, so no manual SQL is ...

All,

is there a simple generic way to capture the rows causing the 'Reference lookup generated X rows'-warning. Logging the current keys used for the lookup would do...

thanks,

William