Joined: 26 Apr 2004 Posts: 4650 Location: Raleigh, NC, USA
The best way I know of is to convert your existing compile/link-edit job to CLIST or REXX. Then, once that is working correctly, create an ISPF EDIT macro that invokes your CLIST or REXX directly from the program source code. For any non-zero return-code situations, write the output to a temporary (VIO) dataset and use an ISPF BROWSE command to review the errors.
And, I know I'll get flamed for saying this, but don't most shops already do all of their code load-and-go testing in the foreground anyway?