I am setting the initial value of a stage variable to Macro DSJobStartTimestamp.
I am having an issue where the value updates intermitantly. It will be the same for three executions (command line), then update on the next run.
Has anyone run into a similar scenario.
Of lesser concern, I am interested where this timestamp is derived. It does not appear to be from the Server.
Thanks
DSJobStartTimestamp value not updating
Moderators: chulett, rschirm, roy
From the DSINCLUDE file in your project, the JobControl.h record:
The macro is a call to the DSGetJobInfo function from within the job for the job start timestamp. I couldn't tell you why multiple independent runs would have the same value, as the logic shows this is probably not possible. Ultimately, you may need to call this in to Tech Support.
Code: Select all
LIST.ITEM DSINCLUDE 11:06:25am 23 Feb 2006 PAGE 28
353 $IfNDef DSJobStartTimestamp
354 $Define DSJobStartTimestamp DSGetJobInfo(DSJ.ME, DSJ.JOBSTARTTIMESTAMP)
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
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
If you initialize the stage variable, and don't provide a derivation expression, it will retain its initial value throughout the job run.
Whether you initialize it from the macro, or from the expression, is up to you. Incidentally there's a typo in the previous post; a right bracket is missing in the date conversion specification. It should be
Note also that this expression can be used in a job sequence, but not in a parallel job, where the Oconv() function is not available. Did IBM mention that? You have to calculate in a job sequence and pass to the job as a job parameter.
Whether you initialize it from the macro, or from the expression, is up to you. Incidentally there's a typo in the previous post; a right bracket is missing in the date conversion specification. It should be
Code: Select all
Oconv(@DATE,"D-YMD[4,2,2]"):" ":Oconv(@TIME,"MTS:")
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.