Michael,
I have found that self-examining jobs pick up the desired string from the
very command used to self-examine.
How do you avoid that?
========================
Leonard S. Berkowitz
mailto:[log in to unmask]
phone: (617) 972-9400 ext. 3250
fax: (617) 923-5555
Michael A <[log in to unmask]> on 09/17/98 11:41:11 AM
Please respond to Michael A <[log in to unmask]>
To: [log in to unmask]
cc: (bcc: Leonard Berkowitz/THP)
Subject: Re: [HP3000-L] clean running STORE jobs
Hi,
You could examine the stdlist with qedit or other tools to find the
errors.
example a :
file stlist = !hp.out.hpspool { I can't remember the hp variable
that point to spoolid }
run qedit.pub.robelle
/t stlist
/holdqj 'CIERROR' { append to the hold file all errors you are
interesed }
/holdqj 'FATAL'
/holdqj ....
/t hold
/list all
/{ this is all error you are interested }
example b:
/t stlist
/{ find a string in the listing that appears on all normal listting }
/holdq 'c:' (nomatch)
/t hold
/{this is all abnormal listings}
I hope this helps
Michael Abootorab
Date: Thu, 17 Sep 1998 11:15:56 -0400
Reply-To: "Stigers, Greg ~ AND" <[log in to unmask]>
Sender: HP-3000 Systems Discussion <>
From: "Stigers, Greg ~ AND" <[log in to unmask]>
Subject: Re: clean running STORE jobs
Content-Type: text/plain
I'm telling myself that due to the repeated postings of old messages,
this got only one response, and if I repost, someone can offer
suggestions for how to do this, off list or on.
I am looking for some way to have either the daily differential STORE
job, or another job determine whether or not the results of the daily
differential were "normal" - everything got backed up except for the
normal set of files that are "OPEN FOR WRITING". Hacks welcome. I also
realize that this could be very prone to getting broken by normal
changes to the box. But even that would be better than nothing, because
nothing is what we have right now. None of the staff available at 3AMish
will manually check the STDList, but we can code to TELLOP or ESCAPE so
that our scheduler (Nobix JobPak) will process an aborted job, and that
will get checked and responded to.
> -----Original Message-----
> From: Stigers, Greg ~ AND
> Sent: Tuesday, September 08, 1998 2:27 PM
> To: HP3K-L (E-mail)
> Subject: clean running STORE jobs
>
> I would like to get our daily differential STORE job to 'run clean' on
> a normal day, and abort on an abnormal day. Then the aborted job will
> be handled with Nobix JobPak, because timely, intelligent human
> intervention is apparently not an option. I am pretty sure that I'm
> not the first list member to want to do this, but I don't find any
> traffic on this subject.
>
> One of the obstacles I know about is that some number of files will be
> "OPEN FOR WRITING". Now, some of these, I could have excluded in an
> indirect file, but others are for instance the various logs that
> remain open. I can think of ways to hack up such a list, but none that
> I care for. What other challenges does this offer?
>
> Since there has not been much traffic on this, I assume it would be
> best to send to me off list, and I can compile and repost the results.
> Thanks.
|
