Re: [OpenVMS Alpha V7.3-2] Batch/Print Job Numbering
- From: David J Dachtera <djesys.nospam@xxxxxxxxxxx>
- Date: Fri, 17 Feb 2006 22:31:08 -0600
Peter 'EPLAN' LANGSTOEGER wrote:
We have a couple of batch jobs here (more than 1000 per day) and so we have
sometimes at lot of entries (pending, holding, executing, retained, timed, ...)
around.
It seems that normally the entry number falls back to 1 at ~2000 here.
It also seems that sometimes the entry numbers are not only 1-4 digits
but also 7 digit ones (I can't check right now, but I think I already
saw 7 digit entry numbers). No 5-6 digit ones ?
Does anybody know where this is documented ? I don't think it is.
Does anybody know a (supported) way of increasing the entry numbers
to not fallback that early (sometimes twice a day)...
Hoff once wrote that there is a guarantee, that there will be no duplicates.
I do believe that this is correct. But we have batch job logfiles where
you can see, that the same entry number is used more than once per day.
And this is very annoying...
Anybody ? Hoff ?
Well, if I understand the issue, it sounds like you may be trying to
track batch jobs by their entry number.
There are a number of pitfalls to that approach, and I don't really
recommend it, though it may be useful/suitable in specific cases.
However, there is a method or two that may be helful, if a bit labor
intensive. Here's one possibility:
If you SET QUEUE/RETAIN=ALWAYS on all your execution queues, this will
ensure that entry numbers do not get reused until you release them. If
this would be helpful, there's some code available in my freeware
archive to clear out retained entries based on a date.
Get http://www.djesys.com/freeware/vms/4038_freeware.zip and look for
RM_RET_ENT.COM. Now, this was never intended for huge numbers of
entries, and DCL may choke due to the limits of CLISYMTBL, so perhaps a
week may be too long for retention (for some sites, even a day or so may
be too long!). The proc. was developed prior to V7.3-2, and so allows
for shorter maximum string lengths.
For example:
$ @RM_RET_ENT * BATCH -0
....will attempt to delete all retained entries on all batch queues up to
and including the time when the proc. is invoked.
$ @RM_RET_ENT * BATCH "-1-"
....will attempt to delete all retained entries on all batch queues up to
and including the time when the proc. is invoked, minus one day.
A bit clumsy, maybe, but it may help. Creative ways to automate that are
possible, I'm sure. The proc. itself can probably be enhanced, and
likely will be by someone, though I may never know.
Just a suggestion...
(4038 was the session number of my first DCL Programming Hands-on
Session at HPworld-2004. That's where the number comes from. The
symposium wanted session-related files to be named like that, and I
haven't renamed it since I posted the original back then.)
--
David J Dachtera
dba DJE Systems
http://www.djesys.com/
Unofficial OpenVMS Marketing Home Page
http://www.djesys.com/vms/market/
Unofficial Affordable OpenVMS Home Page:
http://www.djesys.com/vms/soho/
Unofficial OpenVMS-IA32 Home Page:
http://www.djesys.com/vms/ia32/
Unofficial OpenVMS Hobbyist Support Page:
http://www.djesys.com/vms/support/
.
- Follow-Ups:
- Re: [OpenVMS Alpha V7.3-2] Batch/Print Job Numbering
- From: Peter 'EPLAN' LANGSTOEGER
- Re: [OpenVMS Alpha V7.3-2] Batch/Print Job Numbering
- References:
- [OpenVMS Alpha V7.3-2] Batch/Print Job Numbering
- From: Peter 'EPLAN' LANGSTOEGER
- [OpenVMS Alpha V7.3-2] Batch/Print Job Numbering
- Prev by Date: Re: F$GETSYI to get cluster's founding node name
- Next by Date: Re: A gripe just posted to HP's VMS ITRC forum (for those with a foot in both camps)
- Previous by thread: Re: [OpenVMS Alpha V7.3-2] Batch/Print Job Numbering
- Next by thread: Re: [OpenVMS Alpha V7.3-2] Batch/Print Job Numbering
- Index(es):
Relevant Pages
|
