Storage Initialisation

During initialisation processing, storage was not available for the purpose indicated in the message. This value will be self explanatory when it appears.

Depending on whether the storage is necessary or not, Com-plete may continue processing, however, it is possible that further problems with storage may occur later in the initialisation process or the Com-plete run.

Refer to the Com-plete System Programmer's Manual for information about how to calculate the amount of storage required by Com-plete. Following this either the Com-plete Sysparm or the region size must be adjusted.

This message is associated with Com-plete initialisation processing in a virtual storage environment. The Com-plete storage initialisation routine was unable to page fix the threads or the tibtab due to a shortage of available real-page frames.

If R is replied to the outstanding message number, the page fix will be retried. If E is replied to the outstanding message number, Com-plete initialisation will terminate the message ZIM00003.

This is a severe error. Restart Com-plete when more real storage is available or decrease the size and/or number of threads.

Reply R to retry the page fix, E to terminate Com-plete initialisation.

This message is associated with Com-plete's bufferpool administration.

Com-plete initialisation continues.

The message is issued when Com-plete is unable to expand a bufferpool due to lack of storage in the region/partition.

This message is informational only. No action is necessary.

This message is associated with Com-plete main storage initialization. It is issued once for every thread being initialized. The value $1 indicates the thread number. The values $2 and $3 indicate the storage size allocated to the thread below and above the 16 Mbyte line respectively. The value $4 indicates the storage protect key (in hexadecimal) assigned to the thread. $5 indicates whether usage of the thread is limited.

Com-plete initialisation continues.

The size, storage protect keys, and number of threads are determined by the THREADS, THSIZEABOVE, and PROTECTKEYS initialisation parameters. For more information on these items, refer to the Com-plete System Programmer's Manual.

This message is informational only. No action is necessary.

This indicates the amount of storage that has been allocated for the purpose shown in the message. In a system where storage can reside above the line, when the word (ABOVE) appears at the end of the message, it indicates that all the storage (or in some cases the majority of storage) has been gotten above the 16 meg line.

Self-explanatory message.

A subpool with the shown number, has been allocated for the displayed buffer pool with the indicated element size, element number and total size. In a system where storage can reside above the line, if the buffer subpool is allocated above the line, 'ABOVE' will appear at the end of the message.

An active WTO table was found and will be used. (z/OS only.)

Initialisation continues.

Self-explanatory message.

Self-explanatory message.

This will occur under OS operating systems and indicates that the subsystem entry 'COMP' was found and all associated processing completed successfully.

Under OS operating systems, a feature is available in Com-plete to provide more detailed information in the UQ M display. If this is required, a subsystem must be defined to the operating system called $1. This message indicates that the named subsystem could not be found and therefore the facility will not be active.

The extended information will not be available so the standard copy of the master console will be presented when the UQ M function is used.

Ignore this message unless you wish the extended feature within UQ M to be active. If you want it active, check that the subsystem name has not been misspelled in the OS definitions and that OS actually built a subsystem entry. Please refer to the Com-plete system programmers Manual for more details.