Terminal Initialisation

This indicates that the system control block, UCB for z/OS or PUB for VSE, could not be found for the CUU address $2 for the TID or LID number $3 as defined in the TIBTAB.

Com-plete initialisation is aborted.

Verify that the CUU address as specified in the TIBTAB is correct.

This message is associated with Com-plete TIBTAB initialisation and indicates that the TIBTAB identified an unsupported device for TID/LID $.

Com-plete initialisation is abnormally terminated.

Correct the TIBTAB definition or link edit Com-plete to include the device support modules for the device specified in TIBTAB.

Notify the Com-plete system programmer of the problem and/or start Com-plete specifying a different TIBTAB.

During TIBTAB processing, Com-plete attempted to allocate the indicated device, however, it was unsuccessful because the device was already allocated somewhere else.

The line or tid will be left deleted.

Determine where the line or tid is allocated. If the device can be made available, issue the 'ADD' operator command to cause Com-plete to c attempt to allocate it again.

This message is associated with Com-plete TIBTAB initialisation. It indicates that the TIBTAB is in error. The TID shown does not have an LGCB defined for it.

Com-plete initialisation is terminated.

The listed remote TID is not listed in any LGCB in the current TIBTAB.

Notify the Com-plete system programmer and/or start Com-plete with a different TIBTAB.

This message is associated with Com-plete TIBTAB initialisation to indicate that there is insufficient space in the region or partition for the TIBTAB.

Com-plete initialisation is abnormally terminated.

Increase the size of the region or partition.

TIBTAB processing is complete. If the TIBTAB was loaded, the following will appear....

TIBTAB tttttttt LOADED Where 'tttttttt' is the TIBTAB to be loaded.

If the TIBTAB is built dynamically, the following will appear....

This message is associated with Com-plete TIBTAB initialisation. It indicates that the requested TIBTAB was not found in any library.

Com-plete initialisation is abnormally terminated.

Specify a valid TIBTAB name in the TIBTAB startup parameter.

This message is associated with Com-plete TIBTAB initialisation. The probable cause is an attempt to run an earlier version of Com-plete l TIBTAB instead of a tibtab for the current version of Com-plete . OM-PL Another possible cause is that the module is not a TIBTAB.

Com-plete initialisation is abnormally terminated.

Check the last assembly and link edit of the specified TIBTAB.

This message is associated with Com-plete initialisation and indicates that the requested load for the TIBTAB failed.

Com-plete initialisation is terminated.

Execute Com-plete again. If this fails, notify the Com-plete system programmer.

If applymod 74 is NOT on, Com-plete will attempt to page fix the TIBTAB. This indicates that the page fix has failed for some reason.

Com-plete continues processing without a page fixed TIBTAB.

Determine why the page fix failed. The most likely cause would be due to a shortage of real storage at the moment when the page fix was issued.

Com-plete attempted to allocate the indicated device, however, this failed because the device was offline.

The line or tid will be deleted in Com-plete .

When the device is online to the system again, issue the 'ADD' operator command to cause Com-plete to attempt to allocate it again.

Com-plete attempted to allocate the device, however, the allocate failed. There will have been a previous message indicating why the allocate failed. Please refer to this for more details.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.