Endevor Storage Related Abends

Products

• Endevor
• Endevor Natural Integration

Issue/Introduction

Storage related abends such as S878-10 can occur when compilers invoked in a processor are configured to claim all the storage that is available in the private region, by using SIZE(MAX).

Resolution

Storage related abends such as S878-10 can occur when compilers invoked in a processor are configured to claim all the storage that is available in the private region, by using SIZE(MAX).

If a compiler running in a processor is configured such that the compiler obtains all the private storage available in the region, S878 or S80A type of abends can occur.

Endevor, after invoking the compiler, has his own storage requirements, but no storage would be left if the compiler requests all the storage that is available in the region.

An example is the PL/I for MVS & VM compiler; when running with compiler option SIZE(MAX), it will obtain all the memory that is available. The same or similar options also exist with other language compilers.

A solution in the PL/I case was to use the compiler option SIZE(-512K); this negative form specifies that the compiler releases 512K after it has acquired all it could.

If you are still running into abends of type S878 or S80A with compilers, and above options have been checked, and REGION variations do not help also, it is best to take a SVCDUMP via a SLIPTRAP set via both SLIP SET,COMP=878,END and SLIP SET,COMP=80A,END, and have the resulting SVCDUMP reviewed either by your staff, or by CA Endevor support.

If you need to open an issue with support, you can do this via support online or call you local support center. In the case a support issue is opened, you will need to TRSMAIN or AMATERSE the dump before you FTP it in binary mode to the directory that will be created for the issue. Also please accompany the dump with the full output/sysout from the failing Endevor job.