Page 1 of 1

Datastage Jobs is not seeing compiled when imported to prod

Posted: Mon Jan 27, 2020 11:24 pm
by devesh_ssingh
Hi All,

We are facing some environmental issue as described below so any input would be great help .

During our monthly deployment , we create data stage packages in lower environment with all the sequencer, param-set , server jobs in compiled stated

as soon as our ops team import using istools and check status it shows in complied state but when we execute it failed with different reasons every time.

as remedial action, all jobs recompiled in prod and get executed successfully.

the errors thrown is

1) Error calling DSRUNJobs as jobs are not in runnable state
2) parameter set does not pick local path as defined in PROJDEF.

on searching the forum is see some responses pointed to T30FILES and UVCONFIG files
Setting or Xmeta lock
or some patching needs to be done

as we lack any DS admin support also with limited access its hard to debug beyond any job design and basic checks.

So far all the occurred issues has been sorted just by re-compiling failed job and rerun so any issue in job design is not susceptible.

Any pointers which can lead us toright direction.

Thank you.

Posted: Tue Jan 28, 2020 4:16 am
by qt_ky
What version are you on?

We ran into an issue on version 11.3.x. Not sure if this might be related to your issue or not, but it was unusual and took a fair amount of time to debug. It's similar in that if we recompiled, then the jobs would always run fine, but if we had changed an encrypted job parameter value, like a password, without recompiling, the jobs would abort.

JR53246 Fixed problem with rescheduling and encrypted job parameters

Posted: Tue Jan 28, 2020 11:28 am
by chulett
Also... topic marked as Parallel but you only mentioned Sequence and Server jobs... :?: