Abend Processing

Prior to a system dump being taken, this message is printed once for every allocated 16 bytes of storage around the abend PSW and register set. It consists of the address of the storage being printed, followed by the 16 bytes of information pointed to by the address in hex and character formats.

These messages can be of interest to your support personnel when you are reporting a problem. They should be kept as a part of a diagnostic summary of an abend unless the problem is known and diagnostics are no longer required for the problem in question.

This error message will normally be issued as part of a diagnostic set of abend messages from Com-plete. When they occur, these messages should be kept along with any other ABE messages from the job and passed to the system programmer.

This indicates that a Com-plete subtask has abended with the system abend code and/or user abend code indicated. This message will be followed with one or more ABE messages with diagnostic data for the abend.

This is normally the first message from the Com-plete nucleus when a Com-plete abend occurs for which a dump will be taken. It will be followed by one or more ABE messages containing diagnostic information from the abend which will be required should the error be reported as a problem to your local support centre.

Inform your system programmer about the message.

During abend processing, the Com-plete abnormal termination/recovery routines determined that the MVS SDWA control block, normally available during abend processing, was not available for this particular abend. In this case, only a minimum of diagnostic information can be printed.

Com-plete continues processing according to the other ABE messages printed.

This indicates that for some reason, the IBM recovery routines could not build an SDWA for a Com-plete abend. This will normally indicate a shortage of storage in the Com-plete region but this does not necessarily have to be the case. Refer to the various IBM publications as to the possibilities why Com-plete could not be provided with a SDWA and correct the situation.

Inform your system programmer about the message.

A Com-plete abend has occurred and Com-plete has determined that a dump should be taken for the particular Com-plete task.

This indicates that Com-plete will attempt via recovery or termination processing to take a dump for the particular subtask mentioned in the message.

Inform your system programmer.

A Com-plete subtask has abended and Com-plete has determined that recovery may be possible and therefore will be attempted. If this is preceeded by ZAB00004, then the recovery may take some time due to the fact that the dump must be taken before recovery can actually take place.

Under normal circumstances, recovery will always be attempted unless a recursive loop has ocurred. If this is detected, no other recovery will be attempted. If it is not detected, the results will be unpredicatable. In some cases, it may be necessary to use the operating system functions to terminate Com-plete, however, this should never occur.

This message contains more diagnostic information about the Com-plete abend which has occurred. The first two fullwords contain the PSW for the abend. The second two fullwords contain the 'PSW2' contents at the time of the abend.

Abend diagnostics showing the contents of registers '0' (zero) to '3' (three) at the time of a Com-plete abend.

Abend diagnostics showing the contents of registers '4' (four) to '7' (seven) at the time of a Com-plete abend.

Abend diagnostics showing the contents of registers '8' (eight) to 'b' (eleven) at the time of a Com-plete abend.

Abend diagnostics showing the contents of registers 'c' (twelve) to 'f' (fifteen) at the time of a Com-plete abend.

While attempting to print the storage areas around the Com-plete PSW and register set, the storage location in the message was found to be either not allocated or paged out at the time the abend was taken. For this reason the storage could not be printed.

This is not an error, it simply indicates that the storage could not be addressed during dump processing. If the storage exists and was simply paged out, it will still appear in the actual dump if a dump is taken.

An error occurred in Com-plete causing the recovery routines to attempt to create a dump, however, the $1 processing for this failed. The reason code $2 indicates why the function failed.

Possible values for $1:

The system will continue processing if recovery is successful.

Using the reason code and any system messages, try to establish the reason for the failure. If the error is system dependant, correct the error. If the error appears to be software dependant, contact your local support centre.

A logic error occurred processing TID $1 with luname $2. This will be followed by one or more ZAB messages which will dump diagnostic information to the console.

Processing continues, however, the TID in question may be lost. It MAY be recoverable using the LOGOFF and/or FORCE operator commands.

This indicates a logic error within the Com-plete nucleus. Any messages before this message plus the diagnostics which are issued after this message should be provided to your local support centre.

Self-explanatory message.

Self-explanatory message.