RE: HELP!! DLYJOB command (fwd)

[Neil Palmer <neil@xxxxxxxxxxxxxx>]

---------- Forwarded message ----------
Date: Tue, 22 Apr 1997 23:30:11 -0400 (EDT)
From: Neil Palmer <neil@systemetrix.ca>
To: Bob Clarke 3rd x4502 <clarke@teri.org>
Subject: RE: HELP!! DLYJOB command

Bob,
You can either use CHGMSGQ for the workstation message queue at the console
to assign a Break Handling Program, or (this one is probably easier) in the
backup CL program, where you are doing the CHGMSGQ to *HOLD mode for QSYSOPR
(& as I mentioned in a previous reply, you should probably include the 
*WRKSTN & *USRPRF message queues), you can include a:    
CHGJOB BRKMSG(*NOTIFY)   or   CHGJOB BRKMSG(*HOLD)


On Tue, 22 Apr 1997, Bob Clarke 3rd x4502 wrote:

> 
> Tom Huntington wrote:
> 
> > Do you have any other scheduled events that send break messages like a
> > sndbrkmsg?  In the past this has caused our utility not to work, because 
> 
> > someone had a job scheduled in Robot to send a break message 1 hour
> > before going into a restricted state.
> 
> > My experience is that the resume time works just great.  We use it in
> > several of our products at various times.   My idea on the time range is 
> 
> > simply to prevent a catastrophe from occurring outside of the desired
> > time range.
> 
> Gee ... now that you mention it ... yes, there is a scheduled job at 10:00pm 
> that sends a message via sndbrkmsg to all workstations advising them that 
> batch production is about to begin and to log off.  I hadn't thought about 
> that before.  Could this be the culprit?  Though it does beg the question .. 
> 'why didn't the operators see or tell me about the message?', but that's 
> between me and them I guess (unless the console does not receive break 
> messages?).  I hadn't really understood until now that sndbrkmsg messages 
> are not held up by the chgmsgq *hold option.  I'm not really up on that 
> stuff.  I'll plan on testing the delay both with and without a sndbrkmsg 
> message thrown in.  Of course you can all see the next question coming, 
> can't you ....
> 
> If this is in fact the cause of all my woes, is there a way to keep sending 
> that message out to all users without interfering with this delayed backup 
> job?
> 
> Thanks kindly!
> 
> Regards,
> 
> Bob Clarke
>    
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * This is the Midrange System Mailing List!  To submit a new message,   *
> * send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
> * this list send email to MAJORDOMO@midrange.com and specify            *
> * 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
> * should be directed to the list owner / operator: david@midrange.com   *
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> 

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *