To add: Someone (whom I highly respect) contacted me off-list and said this
came in with z2 mode (z/OS 1.2). What am I missing??
I did this on a sandbox z/OS 1.13 LPAR, which of course has to be
z11 mode.
$TJOBDEF,RANGE=(1,9999999)
$HASP003 RC=(08),T 749
$HASP003 RC=(08),T JOBDEF RANGE (HIGH) - VALUE IS OUTSIDE
$HASP003 NUMERICAL RANGE, RANGE IS (11-999999)
$DACTIVATE
$HASP895 $DACTIVATE 751
$HASP895 JES2 CHECKPOINT MODE IS CURRENTLY Z11
I also checked the z/OS 1.13 commands manual:
RANGE=(nnnnnn,mmmmmm)
The range of job numbers (1-999999) that JES2 uses to assign JOBIDs to jobs
originating on the local node.
nnnnnn The lowest number (1-999989) that is assigned as a JES2 job
identifier for jobs originating at the local node.
mmmmmm The highest number ((nnnn+10)-999999) that is assigned as a JES2
job identifier for jobs originating at the local node. The value
specified for the highest number (mmmmmm) must be equal to the
lowest number (nnnnnn) or at least 10 greater than the value used for
the lowest number (nnnnnn).
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://expertanswercenter.techtarget.com/
On Thu, 29 Mar 2012 10:31:32 -0500, Mark Zelden <m...@mzelden.com> wrote:
>Okay, I guess I'm being dense today and without looking thought that this
>was a change to z/OS 1.13 that I missed. But even looking at a z/OS 1.13
>manual the JOBDEF range states 1-999999. I looked at the summary
>of changes for 1.13 and didn't see it mentioned and I also looked at
>the 1.12 changes (which I missed working with so far) and don't
>see it there either.
>
>So when did a 7 digit range come in and how many years have you
>been running with it?
>
>Regards,
>
>Mark
>--
>Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
>mailto:m...@mzelden.com
>Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
>Systems Programming expert at http://expertanswercenter.techtarget.com/
>
>
>
>
>On Thu, 29 Mar 2012 16:41:48 +0200, Vernooij, CP - SPLXM
><kees.verno...@klm.com> wrote:
>
>>We implemented this years ago, and so did many others, so I would be
>>surprised if an issue like this will pop up only now.
>>
>>Kees.
>>
>>
>>"Mark Zelden" <m...@mzelden.com> wrote in message
>>news:<1805395092283981.wa.markmzelden....@bama.ua.edu>...
>>> On Wed, 28 Mar 2012 17:28:10 -0500, Dave Barry <dba...@ups.com> wrote:
>>>
>>> >We recently changed JES2 on a development z/OS LPAR to use
>>seven-digit instead of five-digit job numbers. A coworker pointed out
>>to me what appeared to be an increase in initiator input queue time on
>>the LPAR after the change. My suspicion is that the increase was
>>coincidental, but I have no way of conducting a true benchmark.
>>> >
>>> >Has anybody on the list noticed such an effect after converting to
>>seven-digit job numbers?
>>> >
>>> >Thanks in advance for your comments.
>>> >
>>>
>>> Nope, but it wouldn't shock me if it was related. You are treading
>>new territory
>>> here and new function like this may work in the lab but issues like
>>this can crop
>>> up in the real world.
>>>
>>> I would open a PMR with IBM JES2 support and see what advise they have
>>> for you.
>>>
>>> Regards,
>>>
>>> Mark
>>> --
>>> Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
>>> mailto:m...@mzelden.com
>>> Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
>>> Systems Programming expert at
>>http://expertanswercenter.techtarget.com/
>>>
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
