Enterprise PL/I's LISTVIEW(SOURCE) Compile Option Support for taking code coverage in IDz

・Request for user interface improvement when conducting interactive debug using IBM Developer for z/OS Client

In case of LISTVIEW(AFTERALL), debugging is done against source which include the output source text by PL/I preprocessor
Because our customer don't want to debug the output source text by PL/I preprocessor, please support LISTVIEW(SOURCE) in IDz

<Our Customer's program information>

- Below is an example of the program customer debugs.
- The number of lines our customer wants to debug is 300.
- The number of lines our customer don't want to debug (which are the output source text by PL/I preprocessor) is 8500.

・Decrease DISK usage when taking code coverage of processes which runs many PL/I programs

The number of our customer's programs is 40,000. Therefore the code coverage taking process uses massive DISK .
Compared to the current option LISTVIEW(AFTERALL) used in IDz, the size of SYSDEBUG decreases 30% by using LISTVIEW(SOURCE) for customer environment.
By using LISTVIEW(SOURCE) we think we can decrease DISK usage, please support LISTVIEW(SOURCE) in IDz


・Decrease E-private usage when taking code coverage of processes which runs many PL/I programs

When we take code coverage, E-private usage for the address space used by z/OS Debugger increases depending on the number of running program.
Therefore when we take code coverage of processes which run many programs, the code coverage taking process ends abnormally due to lack of region space.
It is impossible for customer to take code coverage of such processes.
Compared to the current option LISTVIEW(AFTERALL) used in IDz, the size of SYSDEBUG decreases by using LISTVIEW(SOURCE).
By using LISTVIEW(SOURCE) we think we can decrease E-private usage, please support LISTVIEW(SOURCE) in IDz

<Our Customer's program information>
- The largest number of programs included into one load module is 1,400.
- E-private usage limit is 1,200 MB.