5.79 TZOFFSET (TOD c
lock offset from GMT)

5.79.1 Function

TZOFFSET is used to define the offset of the TOD clock from the current system time. For GMT use the
default value (0000). For time zones west of Greenwich specify a negative value (example: -0500 for US
Eastern Standard Time, -0800 for US Pacific Standard Time). For time zones east of Greenwich, specify
a positive value (example: +0100 for Central European Time, +0930 for South Australian Time).

5.79.2 Syntax

Descriptive

+hhmm -hhmm

Diagram

¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ

+hhmm ¬¬¬«

-hhmm

5.79.3 Parameter

0000

GMT time (0000 is the default value). Please note that this is also the correct set-
ting if your system time (the time of the operating system on which Hercules is run-
ning) is set to local time rather than GMT.

hhmm

Use a positive time in hours and minutes for time zones east of Greenwich.

hhmm

Use a negative time in hours and minutes for time zones west of Greenwich.

5.79.4 Examples

Example 1:

Set the offset of the TOD clock from the current system time to Central European Time.

TZOFFSET +0100

5.80 XPNDSIZE (Expanded storage size)

5.80.1 Function

XPNDSIZE specifies the expanded storage size. Storage is allocated in megabytes, unless a specific unit
is specified. The actual upper limit of the expanded storage is determined by the host system's architec-
ture, operating system, and on some systems the amount of physical memory and paging space you
have available. The lower limit is 0.

The practical limit depends on the maximum amount of storage that can be obtained by “malloc” (usually
around 1 GB on 32-bit platforms; on 64-bit platforms the value should only be limited by available paging
space).

An additional optional argument determines the locking state of the allocated memory (page lock by host
operating system). The LOCKED option indicates that the memory is to be locked into storage while UN-
LOCKED (the default) indicates that the memory is not locked into the storage.

Please note that Hercules preserves the last locking state of XPNDSIZE. Once storage is locked, any
subsequent change to the expanded storage size will honor the existing lock state of memory unless the
lock state is specified again on the XPNDSIZE command.

Caution: Do not lock expanded storage unless sufficient real memory is available to back up the request.
Failure to do so may require the host system to be rebooted.

5.80.2 Syntax

Descriptive

xsize[ ] [

Diagram

~¬¬¬ ¬¬¬®
~¬¬¬ CK ¬¬¬®

Êʬ¬¬ ¬¬
xsize ¬¬¦¬¬¬¬¬¬¬¬¬¦¬¬¬¦¬¬¬¬¬¬¬¬¬¬¬¬¬¬¦¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ

¬¬¬«
LOCK

¬¬¬
T ¬¬¬

5.80.3 Parameter

size

The value of xsize must be a valid decimal number. The actual upper limit is deter-
mined by the host system’s architecture, the operating system and on some sys-
tems the amount of physical memory and paging space that is available.

Storage sizes not on a 1M boundary are rounded up to the next 1M boundary. The
lower limit and default is 0.

M

‘M’ determines that the number given is specified in megabytes (multiplier 2**20).
This is the default if no unit is appended.