That seems like it may work. I'm heading home now, but I will try it on Wednesday (holiday tomorrow!). Probably I would have an empty library as the first one, so I could always include it but not have to have the main production library as the first concatentation.
Thanks for the idea!! Frank On Mon, 10 Nov 2008 20:14:15 -0500, Lizette Koehler <[EMAIL PROTECTED]> wrote: >I was wondering (though I might be wrong) if the use of INCLUDE statements >might not help. > >Inside the PROC itself you could have > >//IGYCW PROC >//COMPILE EXEC PGM=xxxxx >// INCLUDE MEMBER=DEVEL1 Developers Copylib Dataset >// INCLUDE MEMBER=APPL1 Specific Application Copylib Dataset >// INCLUDE MEMBER=SYSLIB1 System specific Copylib Dataset > >Then in your PROCLIB dataset you would have coded for each member > >Member DEVEL1 >//SYSLIB DD DISP=SHR,DSN=DEVELP.COPYLIB a data set always used. > >Member APPL1 >//* > >Member SYSLIB1 >// dd disp=shr,dsn=sys1.igycopy1 >// dd disp=shr,dsn=sys1.copylib > > >The expansion should look like > >//COMPILE EXEC PGM=xxxxx >//SYSLIB DD DISP=SHR,DSN=DEVELP.COPYLIB >//* >// DD DISP=SHR,DSN=SYS1.IGYCOPY1 >// DD DISP=SHR,DSN=SYS1.COPYLIB ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
