OpenTP1 Version 7 Messages

[Contents][Index][Back][Next]

KFCA02894-E

shared memory area used by the TAM service cannot be allocated. (memory attribute: aa...aa, reason code: bb...bb required memory size: cc...cc)

Upon startup of the TAM service, allocating the shared memory to be used by the TAM service failed.
aa...aa: Attributes of the shared memory that could not be allocated
dynamic: The area could not be allocated from OpenTP1 dynamic shared memory.
rm_shm: Shared memory for the TAM service could not be allocated.
bb...bb: Reason code that indicates the contents of the error (up to 10 numeric digits of troubleshooting information)
-1779: The calculation for the required shared memory resulted in an error because an incorrect value is specified in the TAM service definition.
-20012: The available data space is insufficient for allocating the shared memory pool.
-20022: The size of shared memory exceeded the upper limit of the system.
-20024: The number of shared memory segments attached exceeds the allowable attach count for shared memory defined in the system.
-20028: The shared memory identifier exceeds the allowable number of shared memory identifiers defined in the system.
cc...cc: The size of the area that could not be allocated
S: Stops the TAM server start processing.
O:
When the memory attribute is dynamic:
The dynamc_shmpool_size value in the system environment may be insufficient.
When the memory attribute is rm_shm:
  • An error occurred for the size of shared memory for the system. See the reason code in bb...bb.
  • The shared memory for the TAM service exceeds 2,147,483,647 bytes.
  • The product of tam_max_tblnum value and tam_max_filesize value of the TAM service definition exceeds 2,147,483,647 bytes.
  • The relationship between the value of tam_max_tblnum or tam_max_filesize and the tamtable command definition clause is invalid.
  • If cc...cc indicates a negative value, the number of specified tamtable command is more than the value of the tam_max_tblnum operand in the TAM service definition.
For other than above: 0 is output.
Countermeasure: Contact the OpenTP1 administrator. The OpenTP1 administrator must check the system and OpenTP1 definitions.