Gil,
The batch processing was tested with both IKJEFT* and IRXJCL, presenting the
same results.
Here follows the result of "echo $TZ; env" for batch processing :
Tue Feb 1 17:12:14 2022 <=== blank
line_=/bin/env Tue Feb 1 17:12:14 2022
And in TSO OMVS, i got the following :
GMT+2 MAIL=/usr/mail/ZR17
_BPX_TERMPATH=OMVS
PATH=/bin:.
SHELL=/bin/sh PS1=$LOGNAME:$PWD: >
COLUMNS=137
_=/bin/env
LOGNAME=ZR17 STEPLIB=none
LANG=C
LIBPATH=/lib:/usr/lib:.
TERM=dumb HOME=/u/zr17
LINES=42
TZ=GMT+2
MANPATH=/usr/man/%L
NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat
Regards
Ituriel
Em terça-feira, 1 de fevereiro de 2022 13:31:52 BRT, Paul Gilmartin
<[email protected]> escreveu:
On Tue, 1 Feb 2022 14:53:07 +0000, Ituriel do Neto wrote:
> The TZ is set in /etc/profile.Are there definitions for TZ variable also for
> batch ?
>
How are you testing in batch? IRXJCL: IKHEFT*? Other?
You could probe by adding "echo $TZ; env;" to your COMMAND.
POSIX allows the effect of an unset TZ to be implementation dependent.
The majority of UNIX/Linux systems use as a default some value of system
local time, often a symlink, /etc/localtime. z/OS defaults to UTC. IBM
gives the rationale, "for compatibility with AIX"‽
Conway's Law. Rather, there should be a single point of control; one line
in PARMLIB or HMC which an admin could edit to a POSIX (even better,
IANA) format TZ to to govern the setting of CVTDTO (and Daylight Saving
transitions) and TZ for UNIX processes.
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
