SPIE/STXIT Services

This message is associated with the SPIE (OS) or STXIT (VSE) SVC and indicates the parameter list passed that contains invalid addresses.

The user program is abnormally terminated with a Com-plete online dump.

This message indicates an error in the application program.

R1 should contain the address of the PICA used for the SPIE macro.

This message is associated with STXIT PC services. It indicates that the resume address in the user STXIT PC is not within the thread or machine.

The program is cancelled; an online dump is generated.

Check the STXIT PC information specified. specified.

While emulating the an operating SPIE/ESPIE request, Com-plete internally issues an ABEXIT request to set and reset a Com-plete abend exit. Either the set or reset of this failed.

The user program is abnormally terminated with a Com-plete online dump.

Report the error to your system administrator.

This may occur because there is insufficient storage to process the ABEXIT request. Increase the thread size and attempt to recreate the problem to determine if this is the cause. If the problem still occurs, report the problem to your local support centre.

This indicates that the spool file is 80% full. If any more data is written, more messages may be issued or the spool file may go 100% full.

The system continues processing normally.

If this is unexpected, please refer to message ZSP00100 for more information on possible causes for the spool file filling.

This indicates that the spool file is 90% full. If any more data is written to it it may become 100% full and no more printouts can be generated until space is made available.

The system continues processing normally.

If this is an unexpected situation, please refer to message ZSP00100 for reasons as to why the spool space may be filling up.

The application program was attempting to write to the Com-plete spool, however, the spool was 100% full and therefore no more records can be written.

The user program is terminated and the spool file to which the user was writing is closed.

Contact the person responsible for this application or your systems programmer.

This could be either an application error ie. a loop, or the spool file is not large enough to handle the amount of printout being spooled to it. It could also be due to the fact that a printer is in error and printouts are still being queued to it. To relieve the situation in the short term, start any halted printers or purge printout from the spool. In the long term, the requirements for spool space must be

If the printout being produced appears to be larger than expected, check to see what is being output which shouldn't be and correct the logic which produces this code in the application program.