Re: Y2K Blowup - ADK

Ata,

In a message dated 1/19/99 12:32:11 AM Eastern Standard Time, Ata510@aol.com
writes:

> I agree that SYS903B is a good thing to call if you want to be using the JOB
>  DATE, but SYS903B does not return the actual system date, so be careful and
>  realize that if the job runs over a midnight, the date will stay the same
>  (which is desireable in some cases, and may not be in others). 

We had this same problem, and used the following "work around".  CRTDUPOBJ on
program SYS900B to a new name (SYS900BX in our case) in the BPCSUSR library of
your choice.  Create a CL program that accepts the same parameters as SYS900B
that retrieves the job date (RTVJOBA) and system date (RTVSYSVAL) and compares
them.  Should the job and system dates not match, perform a CHGJOB
DATE("system value").  Then call your renamed SYS900B with the inbound
parameters, and return control to the calling program.  Works like a champ,
but beware of trying to test programs (e.g., Y2K) by merely changing the job
date after implementation!  Also watch out, as SYS900B is one of the KRSO
objects -- we didn't adequately document this methodology in the code, and our
RISC upgrade was "interesting"...

HTH,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@aol.com

"Experience is the name everyone gives his mistakes." -- Elbert Hubbard
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---