Add new IMBED directives to include a member with PROCESS directive(s)

This will make it easier to get options out of the source file and easier to change the options for a set of programs (if they have all specify the same file to imbed some options, I need change only that file). delivered in the 6.1 release this May

This will make it easier to get options out of the source file and easier to change the options for a set of programs (if they have all specify the same file to imbed some options, I need change only that file)

If you want 1), you can freeze the compiler options via IBMZIOP, what we do for some of the options too, but since Enterprise PL/I there are so many options, e.g. RULES options, which should be used to develop new and modern code.

2) and 3) are no option for us, as our developers do not have any other solution than the PROCESS statement to use because the compile JCL is fully generated by ChangeMan.

1) Users should not ever be allowed to override compiler options

2) The compiler already shows the *process options in the listing, and if you use "+DD" it will show them in separate sections.

3) And if you want to let users shoot themselves in the foot, I do not see any advantage of using this method to the far more normal method of defining site-specific options, and using JCL that includes these for every compilation, i.e. something like this

//IBMZPLI EXEC PGM=IBMZPLI,
// REGION=0M,
// PARM=('+DD:OVER +DD:USER +DD:NOOVER')
//*
//OVER DD DSN=&DATA(PXOVR&PLIVER.Z),
// DISP=SHR
//*
//USER DD *
//*
//NOOVER DD DSN=&DATA(PXALL&PLIVER.Z),
// DISP=SHR

where
- DD:OVER + PXOVR53 has over-ridable options for EPLI 5.3,
- DD:USER allows users to shoot themselves in the foot, via a procedural override andm
- DD:NOOVER + PXALL53 has options that cannot be changed (of course they can by power-users...)