We no longer need to insert a "bad command". There is the command "ESCAPE" that
will do this







Tony Summers <[log in to unmask]> on 12/21/99 09:09:15 AM

Please respond to Tony Summers <[log in to unmask]>








 To:      [log in to unmask]

 cc:      (bcc: Leonard Berkowitz/CORP/HPHC)



 Subject: Re: [HP3000-L] Message from Job









Extend the logic a little - here's what I mean

Before

!JOB TESTJOB,MY.ACCT
!a BAD COMMAND
!EOJ

Where the 2nd line will cause the job to flush

After

!JOB TESTJOB,MY.ACCT
!SETVAR HPAUTOCONT TRUE
!SETVAR CIERROR 0
!a BAD COMMAND
!IF CIERROR <> 0
!    Do whatever you need
!    EOJ
!ENDIF
!EOJ

>>> "Koren, Noam" <[log in to unmask]> 21/12/99 13:40:40 >>>
Thats works great - I learned something, but I need something that will not
change Job behavior. I mean that if the fob should flush - let it flush...

        Regards,
        Noam Koren
        BMC/New Dimension Software
        voice: 972-3-7664508    fax: 972-3-6451100
        [log in to unmask]
>       bmcsoftware


-----Original Message-----
From: Tony Summers [mailto:[log in to unmask]]
Sent: Tuesday, December 21, 1999 3:26 PM
To: [log in to unmask]
Subject: Re: Message from Job


Try including the following in the job stream after the job card

!SETVAR HPAUTOCONT TRUE

The job won't then flush if an error occurs.

>>> Noam Koren <[log in to unmask]> 21/12/99 13:21:50 >>>
Hello all.

I would like to know if there is a way to be informed when a Job starts or
ends NOT to the console but to another application (i.e. a way to ask the OS
to invoke something when the job starts or ends).

I currently use a command that I insert into the Job itselt at the beggining
and the end of the job file.
But - I have a problem when something in the job goes wrong and the Job is
Flushed - the last command is not invoked so that I dont get a notice.

Example:
!job jjj,us.ac
!jobmsg.bin.acc                      <-- send message through tcp/ip
!
! other commands

oops - ERROR - Job flushed
!
! other commands
!
!jobmsg.bin.acc                      <-- send message through tcp/ip actualy
!EOJ                                     not invoked


Is there a solution for this?
TIA for any idea.

Noam