I think that this is something that is a future intent. You need to get
off of unsupported releases of OS. This would be a stepping stone to
something that just has to be coming. See these in DSPJOB on 6.1:
Job date . . . . . . . . . . . . . . . . . . . . : 05/12/2009
...
Job time:
Current date . . . . . . . . . . . . . . . . . : 05/12/2009
Current time . . . . . . . . . . . . . . . . . : 11:00:32
Day of week . . . . . . . . . . . . . . . . . . . : *TUE
Time zone . . . . . . . . . . . . . . . . . . . . : QN0500EST3
Current offset . . . . . . . . . . . . . . . . : -04:00
Full name . . . . . . . . . . . . . . . . . . . : Eastern Daylight
Time
Abbreviated name . . . . . . . . . . . . . . . : EDT
Currently this is not in CHGJOB, CHGJOBD or CRTJOBD but it sure sounds
like IBM is trying to phase this in.
Format of Time Zone Information
Retrieve Job Information (QUSRJOBI) API
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/apis/qusrjobi.htm#HDRTZE
Work around:
Most people do not use the "accounting code" in the user profile as
intended. We use it to store employee number to tie back to email, etc.
You could store your time zone in there and code your applications
accordingly. Again, when retrieving job information, either via api or
psds, ensure that you use the 'active' user and not the job user. For
example, if the job is a C/S or web job running under QUSER but serving
ROB use ROB and not QUSER.
Rob Berendt
midrange.com
