Munif, Since I do not know your site, this is just a suggestion. And you need to verify that it would work for your shop.
In JES2 Deck you create 2 PROCLIB statements PROCLIB00 is for PRODUCTION and requires no JCL changes. So SYS1.PROCLIB and (for example) PROD.PROCLIB are defined there. You do not have any Development Procs in this concatenation. Next in PROCLIB01 you have SYS1.PROCLIB and DEV.PROCLIB. This only contains the procs for your development jobs. You would now require your Development users to code /*JOBPARM PROC=01 Then if they do not use the correct JCL and Proc name, their jobs should get a JCL error. Any production jobs would not require a /*JOBPARM statement and would default to PROCLIB00 This does not work well if you do not have a controlled environment where the production procs are protected. If a user submits a job with a production proc name, that would have to be protected. I am not sure if this would work in your shop but could be a potential process. Lizette > > Munif, > > When you have a shared JES MAS, the job can be converted on any LPAR. So > there is > no guarantee that a job submitted on LPAR1 will convert on LPAR1. > > So, the only option would be to use JCLLIBs and use Symbolics in the names. > > However, you could use an exit like IKJEFT10 for TSO or a converter or JES2 > exit to > insert the correct JCL JCLLIB statements in the JCL. That would require a > convention > that allows you to identify DEV vs. PROD jobs. This could be via an > accounting code or > Job naming standard. > > Or if you have a Change Control product (Changeman or Endevor) or a JCL > product like > PROJCL or JCL Plus, an exit might be your only option. > > Do you have control over the JOB Card (Name or Accounting Field)? Do you > have a > change control product? Do you have any work that enters your system via NJE > or > FTP? > > Your other option would be to use a JOBPARM card in the JCL pointing to > specific > PROCLIB concatenations in JES DECK (PROCLIB statements) > > > > Lizette > > > > > > Hello Listers > > > > Jobs are submitted using WLM initiators form Production and > > Development systems in our shared JES2 MAS. Our development system > > becomes Part production during night batch. > > > > Is there an easy way we can have different PROCLIB concatenation for > > our Production and Development systems either based on system from > > where the job has been submitted and what time or based on the job > > class > > > > Modifying jobs to have JCLLIB ORDER is not an valid option unless > > it can be automated. > > > > Regards > > Munif. > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
