>Subject: Re: User error causes most z/OS production job failures
>
>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
>

JOBSCAN, JCLCHECK or some equivalent could not beat JOL because it normally
did not cause any failures. It was a product that was ahead of its time and
all it really needed to succeed was a larger support organisation and better
marketing, which is the minimum that any product requires to be successful,
as any of us who have put a product onto the market will confirm.

I have not examined the current free release of JOL, but I would expect
similar error free results from its execution.

I confess that I have a slight bias toward JOL as I started learning
assembler on shift, using the JOL assembler as a model, in the very early
seventies and always recall the comment that read.

"I should never get here, but in case I do I better do something about it".

That reminds me of MVS error handling.

I will respond to the JCL generation comment "or the total lack of JCL" when
I have had a chance to test the current version of JOL.

Beers,
Paul Gillis

----------------------------------------------------------------------
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

Reply via email to