Initialisation Main Processing

This message is associated with Com-plete initialisation processing. Com-plete has received control from the operating system and is proceeding with normal initialisation. The Com-plete version is displayed in the message along with the operating system under which Com-plete is running.

Com-plete continues with normal initialisation processing.

This is an informational message. No action is necessary.

Com-plete has attempted to attach a task for the indicated subtask, however, the attach has failed with the printed return code.

Com-plete initialisation is aborted.

Determine why the attach failed. The printed return code is that received from the ATTACH macro indicating that it had failed.

This message is associated with Com-plete initialisation processing. A serious error identified in a previous message occurred during initialisation of Com-plete.

Com-plete discontinues initialisation, terminating normally.

The error condition responsible for initialisation failure was identified by a previous message on the operator's console. Correct the error condition and restart Com-plete.

Notify the Com-plete system programmer of this error condition.

During subtask startup, Com-plete attempts to establish a recovery environment for the subtask. This indicates that the establishment of the environment failed for a subtask.

The subtask is terminated with a bad return code, however, the results for Com-plete will be unpredictable due to the loss of the subtask.

Determine the reason why the environment could not be established. In an MVS environemnt, it simply indicates that ESTAE processing has failed. Check the possible reasons why this can happen in the IBM manuals.

Inform you system programmer immediately and terminate the Com-plete system to avoid unpredictable results.

This indicates the size of the necleus to date. This includes the Com-plete linked nucleus plus all modules loaded to build the nucleus at start up (including user exits). The second figure will only be present on a system where modules can reside above the line and shows the size of the modules, in bytes, loaded above the line. In this case the sum of the two figures is the total size of the Com-plete nucleus.

The program name displayed in the message was specified as INIT-PGM in the Com-plete Sysparms. It was called on that basis and abended. Com-plete has recovered from the abend and is giving the operator the chance to continue initialisation albeit without this INIT-PGM having run successfully.

Com-plete will wait for a reply to the message. If any character other than 'Y' is replied to the message, Com-plete initialisation will be aborted. When the reply is 'Y', Com-plete initialisation continues with the next INIT-PGM specification if any.

Determine the reason for the abend of the program from the dump that will have been produced and correct the error. Otherwise, the specification should be removed to avoid abends with each initialisation of Com-plete.

Depending on whether the system can run successfully without the running of the particular INIT-PGM, reply 'Y' or 'N' and inform the system programmer.

The patch character specified in the Sysparms and displayed in this message is in use by another Com-plete on the same system.

Com-plete initialisation is aborted.

The 'PATCHAR' Com-plete Sysparm must be unique for EACH Com-plete in the system, as this is used to uniquely identify the various Com-pletes. Either choose another patch character or determine which other Com-plete is using this particular patch character and why.

Depending on various things in the system, the Com-plete nucleus load may take some time. To ensure that this is obvious, a message will be issued every six seconds or so. The first will tell you that the load is 'STARTING', while the second and subsequent messages will indicate that it's 'IN PROGRESS'. This can and often does appear more than once and is therefore not an error, simply an information message.

The operation indicated in the message failed for the named module due to the displayed reason code. The following are the reason codes depending on the operation.

Operation - Reason code

BLDL - R0 contents after failed BLDL

LOAD - Abend code with which the load would have abended if the program hadn't specified an error exit.

Depending on the necessity or otherwise of the named module, Com-plete will continue processing.

Determine why this module is being loaded and if there's a valid reason that it should be loaded, why the load is failing.

This message is associated with Com-plete initialisation processing. The Com-plete main initialisation routine could not locate the module indicated. $ is the module name.

Com-plete discontinues initialisation.

This is a serious error and may indicate corruption of the Com-plete load library. Examine the library to ensure that the specified module is present. It may be necessary to restore that module or the entire library. This error usually means that a module has been inadvertantly deleted from the library and does not, in general, indicate any physical error.

Notify the Com-plete system programmer of this error.

The nucleus named in the message is not at the expected version/ release level as per the initialisation module used.

Com-plete initialisation processing is terminated.

This indicates that the Com-plete nucleus name loaded at initialisation by the initialisation module, does not reflect the version/release level at which the initialisation module was assembled indicating a mismatch. Check that the module you think you are loading is really the module that you are loading. The Version/Release level of the nucleus we have loaded should help you to identify which level of Com-plete nucleus we've loaded, while the second will tell you which level the initialisation module is at.

Self-explanatory message.

Com-plete has attempted to generate the $1 buffer pool. The create request has returned a status of $2. $2 is the hex representation of the status returned from the buffer pool management routines. The first two bytes are the return code from the request and the second two bytes are the reason code. These are described in the section 'Fixed buffer pool manager return codes' in the messages manual.

When the return code is '4' processing continues. When the return code is greater than '4', it indicates that the buffer pool has not been built. If the buffer pool is the 'workpool' buffer pool, this is required for Com-plete execution and therefore initialisation will fail. For any other buffer pool, initialisation will continue, however, the buffer pool will not be available for use.

Generally this should only happen due to a shortage of storage. For the meaning of the status code, please, refer to the APSBPM group of messages.

Various Com-plete nucleus routines or nucleus user exit routines need to be coded reentrant and linked with the RENT option in order to guarantee integrity of the Com-plete system.

Module $1 was found NOT to be reentrant and therefore may result in loss of integrity or nucleus abends.

Initialization continues.

Ensure module $1 is reentrant.

During initialisation, Com-plete adds various resources to the general resource pool for use at a later stage. In this case the add for resource $1 failed with return code $2 and feedback code $3. These codes are documented in the section Resource Manager Return Codes.

Initialisation will terminate.

This indicates logic error in the Com-plete initialisation. Report the contents of the message and the circumstances which cause it to appear to your local support centre.

While attempting to delete the buffer pool $1, a status of $2 was returned.

Processing continues, however, storage may be lost if the delete request actually failed. Failure is indicated in the first halfword of the status $2. When this is x'0008' or greater, it indicates that the delete request failed.

This indicates that an unexpected situation has occurred. $2 represents the return code and feedback code from the BPDELETE request. This, along with any other messages at the time of the error, should be reported to your local support centre.

Com-plete has encountered a logic error in module $1 at offset $2.

Report the error and the circumstances surrounding the error to your local support centre.

Self-explanatory message.

TLSPSVC found in the SVA ist not from APS33x.

Run COMSIP with the correct libraries (including the latest fixpack).

COMSIP loaded TLSPSVC from an older APS Fixpack than the one from with TLINSP is currently loaded.

The job isn't started.

Use the latest APS Fixpacks in the LIBDEF chain for COMSIP.

Self-explanatory message.

Run COMSIP to load our SVC handler.

You are trying to start Com-plete un an unsupported z/VSE version.

Check the Installation Manual and IBM documentation for supported z/VSE versions.

Self-explanatory message.

Initialization is aborted.

Call SAG Support

Self-explanatory message.

Initialization is aborted.

Contact Software AG support

Self-explanatory message.

Initialization is aborted.

Contact Software AG support

Self-explanatory message.

Initialization is aborted. Inform SAG.

Rename the module TLSPPREX on the APS Libraries and restart Com-plete

Informational message

The existing PRODEXIT is deleted and another DEFINE issued.

Self-explanatory message.

Initialization is aborted.

Contact Software AG support

Self-explanatory message.

Initialization is aborted.

Contact Software AG support

Self-explanatory message.

Initialization is aborted.

Contact Software AG support

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Initialization is aborted.

Contact Software AG support

Informational message.

Shutdown continues

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

TLSPSUP1 could not be loaded

Initialization is aborted.

Contact Software AG support

Self-explanatory message.

Informational message.

Shutdown continues

Informational message

Shutdown continues

Self-explanatory message.

Initialization is aborted.

Contact Software AG support

Self-explanatory message.

Initialization is aborted.

Contact Software AG support

Self-explanatory message.

Initialization is aborted.

Contact Software AG support

Self-explanatory message.

Initialization is aborted.

Contact Software AG support

Self-explanatory message.

Initialization is aborted.

Contact Software AG support

Informational message

Initialization continues

Informational message.

Initialization continues.

Informational message.

Initialization continues

Informational message.

Initialization continues

Informational message.

Initialization continues