IBM Support

Why am I getting s13e ABEND during an SCLM COBOL build?

Question & Answer


Question

Most of our COBOL programs build without error, but some of the largest programs are failing with an S13E.

Answer

The S13E ABEND was most likely SCLM DETACHing the compiler's task since it completed with a space ABEND. The system recovery processes did not have enough storage to allow SCLM to continue after that point. Try the following:

  • SYSPRINT VIO could be exceeding its allocation. Try increasing the RECNUM value on the FLMALLOC for SYSPRINT

  • Increase the job's region size

  • Make sure that the SIZE option on the compiler is not set to MAX, or left to default. MAX will cause the compiler to reserve almost all of the available above-the-line storage, which means that other system usage of that (including recovery and SCLM) cannot obtain any space. Add SIZE(xxxxK) to the OPTIONS list on the FLMTRNSL statement.

  • If there is an E37 ABEND as well, you might need the PTFs for COBOL APAR PI16359

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSAU5Z","label":"COBOL Compilers"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCVRUA","label":"SCLM for z\/OS"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
20 July 2021

UID

dwa1301431