×
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.
ASC (now part of Help Systems) used to sell a product called AnyDate
that would do this. We used it when doing Y2K remediation. Don't know
if they still offer it.
Adam Glauser <adamglauser@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/07/2008 04: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?
As an Amazon Associate we earn from qualifying purchases.
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.