Can the PROTSYM file handle secondary extend space by using like STOPx37 third party product?
In order for the PROTSYM to be loaded with symbolic listings of compiled programs it first needs to defined using IDCAMS.
The file then needs to be initialized using the utility program IN25UTIL.
During the initialization process the utility program IN25UTIL assigns numbers to the records in the file.
Essentially you are record 1, you are record 2 etc., until it reaches the end of file based on the primary DASD allocation.
The product STOPx37 intercepts the end of file condition trying to eliminate x37 abend and overrides the no secondary allocation and allows the secondary allocations to occur.
Exclude the PROTSYM file from STOPx37 so secondary extents are not allocated when the end of file has been satisfied for the primary allocation.