RE: Override a system value

Nope. It's got to be the run time, and we have no source code. I've already
told the client to not get his hopes up, and that he'll need to teach the
folks on the Left Coast to calculate the time differences in their heads.

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
smorrison@xxxxxxxxxxxxxxxxxxx
Sent: Monday, January 07, 2008 3:18 PM
To: Midrange Systems Technical Discussion
Subject: Re: Override a system value

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?