Hi, Is anyone on Endevor r17 using COBOL V5.2? If so, have you experienced any problems? Thanks!
Is anyone able to offer any guidance on this question?
So at the AppDev conference we talked about the BSTXCOPY utility is required to convert the PDS load datasets to PDS/e datasets.
see this post on Endevor COBOL exits:
COBOL Endevor Exits
We have not tried COBOL 5.2 with R17, but we did do some testing with R16. The biggest thing to be aware of is the expanded number of work files needed by COBOL 5.2 and the storage requirements. Best guess is that it takes close to 300 Meg to compile a program. As we do a high percentage of compiles in TSO foreground, you need to be aware that the user's TSO profile must allow for that much storage. For other reasons, we backed away from COBOL 5.2 temporarily, but it is in our plan to implement in the near future.
We just started to test Cobol 5.2 with Endevor V16, and we have had a few issues with Storage. Had to update 2 Skeletons (C1SB3000 and ENDES000) and increase the Region size to 600M for Batch submits. Tried 300M and that wasn't enough. We have V17 loaded on our test system and are just getting started with that testing as well.