Running jobs during Daylight Savings Time
Moderators: chulett, rschirm, roy
Running jobs during Daylight Savings Time
We are running control jobs written in Basic where we call GUI jobs sequentially. This is similar to Job Sequencer but not written in GUI which allows us to restart from specific step in case of abend. Whenever this job hits Daylight Saving Time it stops right after the current step is completed. No abend is issued. Did anybody expirience similar problem?
That depends on what you're doing in your custom job control logic. Is it polling in a loop the jobs it is executing, or it is infinitely hung with a DSWaitForJob API call? If it's in a polling loop, do you have any time logic going on, such as monitor job execution time?
As for running jobs during a system clock change, I haven't heard of any problems except those that are self-inflicted.
As for running jobs during a system clock change, I haven't heard of any problems except those that are self-inflicted.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
By "hits daylight savings time" you mean the system clock changes while the transformation job and batch job are running?
If that's the case you should contact tech support.
If the DSWaitForJob API is hanging that needs to be determined. That infinite wait is only satisfied by the transformation job actually finishing. If the transformation job completes successfully and it's actually the DSGetJobInfo that hanging, you need to determine that by looking in the job control log and see if theres a completed message back from the API. You should put some DSLogInfo messaging inbetween each API call so that you can see what statement is truly hanging.
If that's the case you should contact tech support.
If the DSWaitForJob API is hanging that needs to be determined. That infinite wait is only satisfied by the transformation job actually finishing. If the transformation job completes successfully and it's actually the DSGetJobInfo that hanging, you need to determine that by looking in the job control log and see if theres a completed message back from the API. You should put some DSLogInfo messaging inbetween each API call so that you can see what statement is truly hanging.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle