There's a mention of DUPL_JOB in the OS/390 V1R3 JES2 Init & Tuning
Reference, SC28-1792-02, but only in a sample JES parameter deck in
Appendix A. The parm isn't mentioned in the book's JOBDEF parameter
description section.
JOBDEF ACCTFLD=OPTIONAL, /* Accounting field optional ohwnc */
DUPL_JOB=DELAY, /* Don't allow jobs with duplicate */
/* names to execute concurrently onc */
/* (added OS130) */
It shows up in the parameter descriptions in the next version of the
book, SC28-1792-03 for V2R4-V2R6. Looks like the the earlier book's
author may have unintentionally pre-announced a feature that was still
in development!
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Ed Jaffe
Sent: Wednesday, May 01, 2013 11:32 AM
To: [email protected]
Subject: Re: Check whether job still running
On 5/1/2013 8:43 AM, Ed Jaffe wrote:
> On 5/1/2013 8:24 AM, Ed Gould wrote:
>> I am somewhat surprised that you indicate that duplicate jobnames are
>> to be allowed. I have worked in a few shops that job naming stand is
>> frozen and it would wreek havoc if a duplicate jobname were to be
>> allowed running at the same time.
>
> Not sure what to say. This long-standing customer requirement was
> implemented in JES2 over six years ago.
Wow! Time flies when you're getting old. ;)
Research suggests this feature was introduced to JES2 in OS/390 V2R6 ca.
1998!
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
