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 forum but no clues yet...
DS-Version 7.5.1 on Windows Server 2003 using Scheduling tool GECS
Try clearing out the contents of the &PH& project subdirectory and re-running the job, then looking at the text files to see if there is additional error information visible.
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 contains 1219 lines ? Any other place to look then the RT_BP-folder to find the code actually executed by DSD.RUN? Or am i missing something here...
The error occurred in the DSD.RUN program, not in your generated code. If you know how to get to the TCL prompt, then you could try "VLIST DSD_BP DSD_RUN.B" and post 15 lines before and after 2156 and someone here might point you at the possible cause.
Since it is a DataStage program, it cannot be fixed but the error might be being caused somewhere in your program.
The error occurred in the DSD.RUN program, not in your generated code. If you know how to get to the TCL prompt, then you could try "VLIST DSD_BP DSD_RUN.B" and post 15 lines before and after 2156 and someone here might point you at the possible cause.
Since it is a DataStage program, it cannot be fixed but the error might be being caused somewhere in your program.
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 the job being called expects encrypted environment variables....
I'll give it a go without the environment variables being passed to the UtilityRunJob-call (it's useless anyway)... so one moment....