RE: TFRJOB quirk -Reply -Reply

[Pete Hall <peteh@xxxxxxxxxx>]

At 15:06 07/21/98 -0500, Rich Duzenbury wrote:
>> 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 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?
>
>On 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.
>
>What version and release? I doubt it, but perhaps IBM has changed the
>behavior?

J98INITA uses CHGJOB to change the job INQMSGRPY handling to *SYSRPYL. This 
causes certain messages that JDE has determined are inconsequential to be 
responded to. However, messages that are not in the system reply list then 
require a reply. When J98INITA ends, it puts things back the way it found them.


Pete Hall
peteh@inwave.com 
http://www.inwave.com/~peteh/

+---
| 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
+---