Table Management (Subsystem 108)
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| E0701 Volume II | |
| E0300 Volume I | |
| E0300 Volume II | |
| E0300 Volume III ♥ | |
| E0394 Volume I | |
| E0796 Volume II | |
| E0494 Volume III |
- 50
- MESSAGE
The entry size is less than the minimum entry size.
- CAUSE
The entry size parameter is too small.
- ACTION
Correct the parameter.
- 51
- MESSAGE
The header is invalid.
- CAUSE
Two words at the beginning of the header should point back to the header.
- ACTION
Take a system dump.
- 53
- MESSAGE
The entry size is greater than the maximum size.
- CAUSE
The entry size is greater than the pool size in a variable entry size table.
- ACTION
Correct the parameter.
- 54
- MESSAGE
The initial size is greater than the maximum size.
- CAUSE
The pool initial size is greater than the maximum size.
- ACTION
Correct the parameter.
- 58
- MESSAGE
The last free entry is less than the first free entry.
- CAUSE
There are bad table creation parameters.
- ACTION
Correct the parameters.
- 59
- MESSAGE
The free link offset is greater than the entry size.
- CAUSE
There are bad table creation parameters.
- ACTION
Correct the parameters.
- 63
- MESSAGE
There is no entry in the pool.
- CAUSE
The pool does not contain any more entries.
- ACTION
Create the table with a larger primary or secondary pool of entries.
- 64
- MESSAGE
There are no entries in the entire table.
- CAUSE
Both primary and secondary pools are empty.
- ACTION
Create the table with more entries.
- 69
- MESSAGE
Attempted to return entry to full pool.
- CAUSE
More entries were returned than were originally in the pool.
- ACTION
Check the logic which gets and returns entries.
- 70
- MESSAGE
The increment size is greater than the maximum pool size.
- CAUSE
There are bad table creation parameters.
- ACTION
Correct the parameters.
- 71
- MESSAGE
The configured free entries are greater than the initial size.
- CAUSE
There are bad table creation parameters.
- ACTION
Correct the parameters.
- 72
- MESSAGE
Single object header/body with inconsistent allocation.
- CAUSE
Body and header must both be allocated or not allocated initially.
- ACTION
Correct the parameters.
- 73
- MESSAGE
The primary and secondary pools overlap in unified pool.
- 74
- MESSAGE
The negative parameter value is illegal.
- CAUSE
There are bad table creation parameters.
- ACTION
Correct the parameters.
- 75
- MESSAGE
Table semaphore type is out of range.
- CAUSE
The semaphore specification is not valid.
- ACTION
Correct the parameter.
- 76
- MESSAGE
The entry number is not in the free list.
- CAUSE
Monotonic table entry number is outside the range of the free list.
- ACTION
Correct the parameter.
- 78
- MESSAGE
The entry has not yet been allocated.
- CAUSE
The desired entry number is either less than zero or greater than the number of entries now in the body.
- ACTION
Correct the parameter.
- 79
- MESSAGE
Space management WRITE disk error.
- CAUSE
sm_write returned an error to post_table.
- ACTION
Take a system dump.
- 80
- MESSAGE
Posting requires a single object.
- CAUSE
An attempt was made to create a table with posting requested, but not with a single object.
- ACTION
Correct the parameter.
- 81
- MESSAGE
There are no allocated entries.
- CAUSE
Call to entry_allocated with wrong entry number, or call to get_next_allocated_entry with a bad start number, or call to get_next_allocated_entry and entry not found.
- ACTION
Take a system dump.
- 82
- MESSAGE
The allocated entry list does not exist.
- CAUSE
Call to entry_allocated, but tbl_allocated_list not in header options.
- ACTION
Correct the parameter.
- 83
- MESSAGE
The variable table can not have an allocated list.
- CAUSE
There are bad table creation parameters.
- ACTION
Correct the parameter.
- 84
- MESSAGE
Can not lock the table semaphore.
- CAUSE
An attempt was made to lock the table semaphore while on the Interrupt Control Stack (ICS), or the cb_lock procedure failed, or the wait failed if tbl_dont_lock was used in the header options.
- ACTION
Take a system dump.
- 85
- MESSAGE
Can not mix the allocated list and the variable table.
- CAUSE
There are bad table creation parameters.
- ACTION
Correct the parameters.
- 86
- MESSAGE
Posting requires a permanent object.
- CAUSE
An attempt was made to create a table with the tbl_post_object procedure without also using the tbl_permanent_object procedure.
- ACTION
Correct the parameters.
- 87
- MESSAGE
The PUT WAIT queue requires the table to be locked.
- CAUSE
While in the block_on_resource procedure, the table semaphore was either unlocked or locked by another process.
- ACTION
Take a system dump.
- 92
- MESSAGE
Bad allocated list option.
- CAUSE
Incompatible options were used with the tbl_allocated list.
- ACTION
Correct the parameters.
- 98
- MESSAGE
The variable initial size is not 4-byte aligned.
- CAUSE
There are bad table creation parameters.
- ACTION
Correct the parameters.
- 99
- MESSAGE
The variable increment size is not 4-byte aligned.
- CAUSE
There are bad table creation parameters.
- ACTION
Correct the parameters.
- 107
- MESSAGE
Out of disk space.
- CAUSE
The attempt to expand the table ran out of disk space.
- ACTION
Free up disk space.
- 157
- MESSAGE
Large Object cannot be created.
- CAUSE
A create object request was received that exceeded the maximum object size supported. This maximum is currently 128GB.
- ACTION
Request a smaller object size that is within legal limits.
- 158
- MESSAGE
Virtual Space cannot be deallocated.
- CAUSE
An error occurred during the deallocation of an object which prevented the virtual address space from being recovered.
- ACTION
No immediate action need be taken. However, if this situation happens over a long enough period, available virtual address space may become scarce. In this case, a reboot of the system is required to clear the problem.
- 159
- MESSAGE
Prefetch size exceeded max_prefetch_size (4GB).
- CAUSE
A prefetch request was received which exceeded the maximum prefetch size, which is currently 4GB.
- ACTION
Request a smaller size that is within the legal limits.
- 160
- MESSAGE
SR5 Objects cannot exceed 1GB.
- CAUSE
A request to create an object in SR5 short address space was received that exceeded the architected maximum SR5 address space of 1GB.
- ACTION
Create a smaller object, or create the object in long pointer space.
|
Chapter 5 Error Messages |
TermDSM |