On Dec 16, 2007, at 9:37 AM, Kenneth E Tomiak wrote:
You could pay them to use it. Why would any shop want to convert
off JCL to
a single person supported product because they had a JCL error?
They could
bring in a product like JOBSCAN which checks JCL before it runs.
They can use
other products hooked in to the job scheduler that run through JCL
before the
job is submitted as well. And these are supported by companies, not
one man
shows. If all JOL does is create JCLK, then they have the same
problem,
something needs to check the JCL will work, not just for syntax
errors.
Kenneth,
Its been a few years but we had JOBSCAN and indeed it did help. BUT
we still had JCL errors (a lot fewer mind you) but we still had them.
I would recommend the product but it is not fool proof. We had on
site production support 7x24x365 and they kept themselves fairly
busy. The number of production runs a day was 2-3K at two sites (1
was a DR site).
I cannot remember specifically what the errors were that JOBSCAN did
not catch.
It will never catch all but it did catch most.
Ed
----------------------------------------------------------------------
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
