RE: TFRJOB quirk -Reply -Reply -Reply

Rich,

>>Sorry to jump in late here, but I believe the message queue must not
>>really be in *hold mode.  Perhaps the initial program is changing it to
>>*notify or *break?

I forgot in the original post to mention that these are JDEdwards users
and JDE has a break message handling program run.  So the users are in
fact not in *HOLD status.

>> my system, I just created a user profile CRTUSRPRF TEST1
>>DLVRY(*HOLD). No initial program has been specified.  Upon sign on, I
>>did a WRKOBJLCK TEST1 *MSGQ, and it shows no locks on the
>>message queue.  I did a couple TFRJOBs, signed on multiple times, and
>>no messages have appeared.

I signed on without the the J98iinita program and I get the same result as
you.  Unfortunately the users wouldn't take too kindly to me removing their
app on them :)

>>What version and release? I doubt it, but perhaps IBM has changed the
>>behavior?

One system is 3.6, one at 3.7 and I had a friend do same on 4.2 so you
are right again there.  Instead of eliminating the messages themselves, I
am really trying to eliminate them being displayed to the users.  

Thx,
John
John W. Cirocco
Manager, Data Center Operations
Computer Task Group, Inc.
700 Delaware Ave.
Buffalo, NY  14209
Phone (716) 888-3566
Pager 1-800-283-2255 Pin 12029
John.Cirocco@ctg.com
+---
| 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
+---