SCF Reference Manual for the Kernel Subsystem

TIME_ZONE_OFFSET [ + | - ] [h]h[:mm]
specifies an offset of standard civil time (SCT) from Greenwich mean time (GMT) in hours and
minutes, where hh is in the range 00 through 23 hours and mm is in the range 0 through 59
minutes. The default is 0. SCT does not include daylight-saving time (DST).
See also the procedure “Changing the System Name or System Number (H-Series RVUs)”
(page 30). Changes to this attribute take effect at the next Manual Reload or Hard Reset of
the system.
Some examples of time-zone offsets are:
TIME_ZONE_OFFSET 0:00 !London
TIME_ZONE_OFFSET + 01:00 !Paris
TIME_ZONE_OFFSET + 05:30 !Bombay
TIME_ZONE_OFFSET + 09:00 !Tokyo
TIME_ZONE_OFFSET - 05:00 !New York
TIME_ZONE_OFFSET - 8:00 !California
When you load the system the first time after changing the TIME_ZONE_OFFSET value, you
must enter a TACL SETTIME command to correct the system time, which is incorrect by the
amount of the change to the TIME_ZONE_OFFSET value.
TNSMISALIGN { FAIL | NOROUND }
controls the behavior of TNS and accelerated TNS programs when compatibility traps from
odd-byte misalignment occur.
FAIL
causes the system to immediately generate an INSTRUCTIONFAILURE interrupt in the process
when an erroneous odd-byte extended address is used in a context that caused round-downs
on RVUs before G06.17. The interrupt abends the program or sends it into a debugger if
the program has no ARMTRAP error handler.
Use the FAIL option for testing and debugging. Do not use it on a production system if the
EMS log shows any misalignment events in any programs.
NOROUND
causes the system to complete all misaligned data operations at the given starting address,
without round downs or INSTRUCTIONFAILURE traps. This NOROUND behavior matches
the behavior of native mode programs. Former TNS cases that caused rounddowns on
RVUs before G06.17 are counted and traced in the EMS log.
Some uncorrected old TNS programs depend on round-down, and may misbehave if you
specify NOROUND. No INSTRUCTIONFAILURE trap is generated.
The FAIL option affects only some uses of erroneous odd-byte pointers. Other uses of erroneous
odd-byte pointers always complete without trap or round down and are never counted or traced
in the EMS log.
To use this attribute, see “Changing Data Misalignment Attribute” (page 34).
TLE_LIMIT n
specifies the limit on the number of TLEs that a process is allowed to use.
TIME LIST ELEMENT (TLE) is a kernel structure that keeps track of a timer started by a process
or the time limit specified by a process when it initiates a nowaited I/O. When the time-limit
expires, the NonStop Kernel performs a task. The task performed by the operating system in
response to a TLE expiration depends on the type of TLE and its parameter. TLEs are system
resources configured during system generation.
As of the J06.09, H06.20, and G06.32.01 RVUs, you can configure a limit on the number
of TLEs (Time List Elements) that can be allocated by a process. For previous H and J-series
RVUs, there was no such limit and an errant application could consume all, or nearly all, the
TLEs.
ALTER Command (Sensitive Command) 95