Job Date, System Date

This Q&A forum allows users to post and respond to "How Do I Do ....." questions. Please do not use to report (suspected) errors - you must use your regional help desk for this. The information contained in this forum has not been validated by LANSA and, as such, LANSA cannot guarantee the accuracy of the information.
Post Reply
Joerg Hamacher
Posts: 48
Joined: Thu Feb 11, 2016 12:01 am

Job Date, System Date

Post by Joerg Hamacher » Fri Jul 12, 2019 1:08 am

Hi,

we are using *MONTH / *DAY / *YYYYC / *TIME for writing protocol files into IFS from inside a batch job.
Problem is that *MONTH / *DAY / *YYYYC seem to be the job values of the day when the batch job was started.
When the job runs overnight these values do not change - *TIME is always correct.

So when the batch job starts today (11th of July) and runs until tomorrow morning a file created 10 minutes after midnight will be named
2019_07_11_000010 instead of 2019_07_12_000010...

Are there other system values that we should use instead of *MONTH / *DAY / *YYYYC ?

Best regards,
Joerg

atostaine
Posts: 395
Joined: Wed Jan 20, 2016 7:38 am

Re: Job Date, System Date

Post by atostaine » Fri Jul 12, 2019 4:17 am

#STD_DTIMX.now will give you the correct time stamp. You could extract the values from there.

Or #Std_Datex.now and #std_Timx.now
Art Tostaine

Post Reply