RE: TFRJOB quirk -Reply -Reply

On Tuesday, July 21, 1998 11:24 AM, John Cirocco 
[SMTP:JCirocco@gw.ctg.com] wrote:
> >>Chances are that the USRPRF has MSGQ(blahblah) DLVRY(*BREAK).
> >>If you  were to make it (*HOLD), then the message queue would not be
> >>allocated to  any jobs.  Of course, then it won't *BREAK, either...
>
> Not true.  In the original post I said I had tried that.  For some 
reason
> the
> "*HOLD" still wants to allocate the message queue somehow.

Sorry.  I should have gone back to the original note.

The "but" here is that if I start interactive job A, chgmsgq buck *hold, 
then start interactive job B, chgmsgq buck *hold, tfrjob qctl I do not get 
any of the 3 messages.  I just tried it.  If I chgmsgq buck *break in job 
A, then in job B do a tfrctl qctl, I get all three messages.  This is the 
behaviour I'm used to from S/38 days (as in I don't think this is a PTF 
level issue.)  Is it possible that program J98INITA is changing it back to 
*BREAK?  Is OV/400 the culprit?

> >>Users aren't  complete idiots: they should be able to understand the
> >>difference between informational messages and inquiry messages,
> >>don't you think?
>
> I received calls from over 10% of my users.  We have 700 active user
> profiles going here.  My help desk wants to $#%@*&)+= me.

John, I can completely 1000% sympathise with you.  I spent over 5 years in 
the de facto position of help desk.  Some of the users are so...script 
driven (go exactly by "the Book") that any small change in keystrokes 
throws them off.  I used to arm them and their supervisors with print 
screens of the changes a week before the change was made live, and also 
the night before (just to keep it fresh in their minds.)  No, it didn't 
eliminate the calls, but it cut them down.  They complain about the 
changes, sure - you can't stop that.  But it *was* better (after a while) 
when the folks on the line felt like we in MIS were thinking about them.

Buck Calabro
Commsoft, Albany, NY
mailto:mcalabro@commsoft.net

--I'm not a complete idiot: several important parts are still missing!

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---