× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



It depends on how the program gets dates. If it uses %timestamp or the
TIMSTP opcode, the date and time will be the system date and time, not hte
job's date and time. That is the way we write all of our programs. However,
many of them do have from/to date prarmeters for just that reason. Our shop
standard is to never, ever, use UDATE (or U-anything else).


On Jan 7, 2008 3:18 PM, <smorrison@xxxxxxxxxxxxxxxxxxx> wrote:

Will changing the Job Date work for you?
CHGJOB DATE(010207)
before issuing the call to your program. The format of job date needs to
match the job date defined on your system.

Steve

Steven Morrison
Fidelity Express




Adam Glauser <adamglauser@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/07/2008 03:06 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Override a system value






I am trying to recreate a problem from a job that ran last week. I
don't have the job log anymore. I've tried running the job in the same
environment (same JOBD, no changes to the major driving files that I can
find) and I get the expected results.

The one difference between the my test run and the failed run is that
I'm specifying the date this time,
CALL PGM(PGMA) PARM('2007-01-02')

instead of
CALL PGM(PGMA) PARM(' ')

which is the usual way of calling the program. When no parameter is
supplied, the current date ( %date() ) is used.

I was wondering if there a way to override the system time for a given
job. I've checked the archives, 'GO CMDOVR' and the Infocentre's API
finder, and I'm not sure where else to look. Is this a loony idea, or
does someone know of a way to do this?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.