I am a big fan or Pro/JCL. Especially the feature that lets you simulate the execution of an entire job stream. It’s an easy way to check that your DSNs are consistent from job to job, without actually running them.
On Fri, Mar 12, 2021 at 15:28 Mitch Mccluhan < [email protected]> wrote: > Folks, > As an FYI, J-MAN makes it possible to work on a "reference model", from > which the tool automatically creates as many target environments as you > need, based on "rules" that describe how to modify the jobs to make them > effective for the specific target environments. Every single keyword of the > job, every file name, every parameter can be automatically changed, > including the structure itself of the job can be changed. > Mitch > > > -----Original Message----- > From: Jeffrey Holst <[email protected]> > To: [email protected] > Sent: Fri, Mar 12, 2021 6:45 am > Subject: Re: JCL checkers? > > Like several others we use JCLCHECK from Broadcom/CA. We were using > JCLSCAN, but we had a new requirement that we be able to check JCL intended > to run on a different sysplex. (We create our production JCL on a test > sysplex.) JCLCHECK has a feature that does this. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
