We don't run such, but we are quite small. In an earlier life, we were
with a much larger shop that did not permit programmers to run final
tests using live data. The promoted job stream was, therefore, always
untested. Of course, JCL errors were common.
IMHO, the need for such is rooted in site security policies and the
change control process. I think perhaps final promotion that occurs
*after* the production process is fully tested might be something to
think about.
HTH and good luck.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Howard Brazee
Sent: Friday, September 30, 2005 10:34 AM
To: [email protected]
Subject: Re: Are there any mainframe sites out there that don't use
JCLCHECK/JCLPREP or equivalent?
On 30 Sep 2005 07:32:56 -0700, "sekisho" <[EMAIL PROTECTED]> wrote:
>Despite massive user objection, we've just de-installed JCLCHECK and
>are now back in the 1980's dark days of TYPRUN=SCAN. Apparantly we
>don't need JCL checking software. Are we now the only z/os site in the
>world that doesn't have JCL checking software?
I never figured out what the advantage of JCLCHECK was. It's part of
the procedure before jobs get migrated, but new jobs find a bunch of
errors anyway as it doesn't find stuff in their post-migration
locations.
Testing should find errors before it gets to this stage. What kind
of error will JCLCHECK find that matter?
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
