Re: [OpenVMS Alpha V7.3-2] Batch/Print Job Numbering

AEF wrote:

David J Dachtera wrote:
Peter 'EPLAN' LANGSTOEGER wrote:

In article <43F6A30C.BCF5B109@xxxxxxxxxxx>, David J Dachtera <djesys.nospam@xxxxxxxxxxx> writes:
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.

Not at all. I only have a lot of (equally named) logfiles and I need
to find out why entry x failed (and hangs around retained on error).
Searching with the entry number (and the date) is not enough because
there are more than one entry number x per day. Thats all folks.

Well, SHOW ENTRY/FULL on a retained entry shows the time the job
completed. So, DIRECTORY/MODIFIED using /SINCE and /BEFORE should be
able to narrow it down:

DJAS01::DDACHTERA$ dir/noprot/nosize/date=(cre,mod) login.com;

Directory DKA0:[DDACHTERA]

LOGIN.COM;1 3-SEP-1997 16:24:35.65 28-NOV-1998 21:25:44.81

Total of 1 file.
DJAS01::DDACHTERA$ dir/mod/sin="28-NOV-1998 21:25"/bef="28-NOV-1998
21:26" login
.com

Directory DKA0:[DDACHTERA]

LOGIN.COM;1 1/9 3-SEP-1997 16:24:35.65
(RWED,RWED,RE,)

Total of 1 file, 1/9 blocks.

Sorry, didn't have a queue entry handy to use as an example, but that's
what I mean: bracket the target time using /SINCE and /BEFORE values
with MODIFIED and less granular sample time for each qualifier should
give you everything in that range.

That said, let me ask this: can you modify whatever SUBMITs the jobs?

If you can, try this:

$ SUBMIT/qualifier(s) filespec/HOLD
$ JENTRY = F$FAO( "!7ZL", '$ENTRY' )
$ SET ENTRY '$ENTRY'/LOG=[ddcu:<dir>]filename_'JENTRY'.LOG/NOHOLD

That will produce fewer logs to sift through since you can then get a
listing of every entry number used for that job in ascending order by
entry number.

Personally, though, I agree with Michael: if the job is retained on
error, that entry number won't be re-used so long as that queue remains
retained.

That's not his problem. Imagine his queue numbers run from 1 to 1000.
His system runs 3000 jobs one day. Now he has found that entry 442 has
been retained on error. Now which of the 3 log files that contain 442
is the one that was retained in the queue??? Even though job 442 may be
reatined in the queue, that same number may have been used earlier in
the day.

How many times has that entry number been re-used?

If the job's entry number:

$ enbr = F$GETQUI("DISPLAY_JOB","AFTER_TIME",,"THIS_JOB")

....is output to the log file, that will help naarow it down, but not
pin-point the target log.

Interesting thing about /RETAIN: if a job is retained, even when a queue
is set /RETAIN=ALWAYS, /DELETE of the log file doesn't take effect until
the entry is itself is DELETEd.

So, one other possible solution might be to SET the QUEUE /RETAIN=ERROR
and specify a "null" queue as the default print destination for batch
logs, then SUBMIT the jobs using /NOKEEP explicitly (to over-ride any
defaults due to symbols, etc.). That way, the only batch logs that will
remain on disk are those where the entry was retained due to the queue's
current SETtings.

That narrows it down even further. SHOW ENTRY/FULL or the appropriate
F$GETQUI() calls to automate the task for an entry would then be useful
to get down even closer to the target log using the completion time of
the job and the RDTs of the log files on disk.

It would be most helpful, of course, if the queue manager would update
the entry with the actual target filespec for the log file. Then again,
given that there does not seem to be a way to retrieve that outside of a
great deal of VMS "black magic", that may not even be possible right
now. It would likely require considerable enhancement to
LOGINOUT.EXE(?).

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

Relevant Pages

  • Re: [OpenVMS Alpha V7.3-2] Batch/Print Job Numbering
    ... $ SUBMIT/qualifierfilespec/HOLD ... listing of every entry number used for that job in ascending order by ... that entry number won't be re-used so long as that queue remains ... ...is output to the log file, that will help naarow it down, but not ...
    (comp.os.vms)
  • Re: [OpenVMS Alpha V7.3-2] Batch/Print Job Numbering
    ... $ SUBMIT/qualifierfilespec/HOLD ... listing of every entry number used for that job in ascending order by ... Imagine his queue numbers run from 1 to 1000. ... ...is output to the log file, that will help naarow it down, but not ...
    (comp.os.vms)
  • Re: [OpenVMS Alpha V7.3-2] Batch/Print Job Numbering
    ... David J Dachtera wrote: ... to find out why entry x failed. ... Sorry, didn't have a queue entry handy to use as an example, but that's ... Unofficial OpenVMS Hobbyist Support Page: ...
    (comp.os.vms)
  • Re: Help - (getting intermittent 404s)- This sites my last hope!
    ... The entry below that looks funny, ... However, as Robear mentioned, you really need to post your HJT log file to one of the forums he mentioned to have a real expert interpret it. ... You said that tool can help me to fix things but I need to know really, ... I end up with a damaged IP stack (Dont think its the browser itself as Opera ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: [OpenVMS Alpha V7.3-2] Batch/Print Job Numbering
    ... $ SUBMIT/qualifierfilespec/HOLD ... listing of every entry number used for that job in ascending order by ... Imagine his queue numbers run from 1 to 1000. ... ...is output to the log file, that will help naarow it down, but not ...
    (comp.os.vms)