HP3000-L Archives

January 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Michael D. Hensley" <[log in to unmask]>
Reply To:
Date:
Tue, 12 Jan 1999 11:09:55 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Allan Chalmers asked:

> altho on the 3000 for over 20 years, my company doesn't have a "job ran
> OK? - delete STDLIST" routine in jobs and I can't remember the drill for
> doing this. Can anyone refresh my age clouded memory?  Tnx.

Well, the "job ran OK?" part is up to you (your programs need a way,
typically by setting a JCW, to let the job know that everything is ok).

Assuming you create a JCW named JOBOK, and that if it is set to 0 everything
is find, add the following to the end of the job:

!IF JOBOK=0 THEN
!   SET STDLIST=DELETE
!ENDIF

Note: may people seem unaware that you can also do things like (assuming
MYPROG1 sets the JCW JOBOK to -1 for fatal-error-abort-the-job conditions):

!RUN MYPROG1
!IF JOBOK = -1 THEN
!   EOJ
!ENDIF
!
!RUN MYPROG2
...


---
Michael D. Hensley       | mailto:[log in to unmask]
Allegro Consultants Inc. | Visit scenic http://www.allegro.com
408/252-2330             | "Support Bill of Rights Enforcement"

ATOM RSS1 RSS2