SNAX/HLS Management Programming Manual

Event Message Descriptions
Event Management
8–32 104708 Tandem Computers Incorporated
ZHLS–TKN–TCB–SIZE
conveys the amount of memory, in bytes, required in the current implementation
of SNAX/HLS to have vital information for each session. It is used to explain why
allocation attempts fail. The value of this token corresponds to the value <5> in
the text message. This value is subject to change from release to release, or IPM to
IPM.
ZHLS–TKN–POCB–SIZE
conveys the amount of memory in bytes, required in the current implementation
of SNAX/HLS to have vital information for each open. It is used to explain why
allocation attempts fail. The value of this token corresponds to the value <4> in
the text message. This value is subject to change from release to release, or IPM to
IPM.
ZHLS–TKN–MAX–TBLS
conveys the upper limit, in bytes, of the amount of storage that can be dedicated to
the combined open and session tables in SNAX/HLS. The value in this token may
change from release to release. The value of this token corresponds to the value
<6> in the text message.
Cause. The number of opens and sessions requested, while individually within legal
bounds, collectively require the allocation of too much memory.
Effect. SNAX/HLS terminates abnormally. Because this event is detected before the
backup is started, no takeover occurs.
Recovery. Correct the configuration parameters. This might require you to redistribute
the load to additional copies of SNAX/HLS.