Is there a technique, statement or utility that will cause a program or
jobstep to "see" a different timezone? I recall you could do this in VSE. I
looked at the CBT tape and did not find anything. Is there a programming
technique that would work? The politics are such that writing code is a more
acceptable solution than a vendor product.

Here is the sort of solution I need or picture. Approach 1:

//STEP1 EXEC PGM=RUNTIME,PARM='parms for REALPROG'
//RUNTIME DD *
REALPROG PDT or REALPROG -9
/*
// DD statements for REALPROG

Where RUNTIME LINKs to REALPROG first having modified z/OS control blocks
such that REALPROG (only -- not other programs in the system) "sees" the
timezone as PDT, UTC-9.

Approach 2:

//STEP1 EXEC PGM=RUNTIME,PARM='PDT' or PARM='-9'

and subsequent steps in the job -- but not other programs in the LPAR --
"see" the timezone as PDT, UTC-9.

Was there some sort of technique to do this developed during the Y2K
excitement?

What do shops do that have LPARs that serve users in multiple time zones --
some one-off homegrown solution that works (only) for them?

Thanks,

Charles 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to