• Subject: RE: Re[2]: TFRJOB quirk -Reply -Reply -Reply -Reply
  • From: "Rich Duzenbury" <rduz@xxxxxxxx>
  • Date: Thu, 23 Jul 1998 15:45:44 -0500
  • Importance: Normal
  • In-Reply-To: <s5b6ed2f.073@gw.ctg.com>

If possible, fix the initial program to leave the message queue in *hold
mode.  This is the only mode that won't allocate the *msgq and cause the
annoying message.

As it seems that the original request to eliminate the message was due to
unnecessary help desk calls, the only other suggestion I can offer is to
change the first level text of the message (CPF2451) to 'PRESS ENTER TO
CONTINUE'.  This as you are no doubt aware, has it's own set of
ramifications.

Regards,
Rich

============================================
Rich Duzenbury
http://rich.dyn.ml.org
http://vpsolutions.com
============================================


> The users run JDE's J98INITA program which does a CHGMSGQ and
> adds a break message handling program.  So in the first signon, the msgq
> will become allocated and in the second, the line fails because the first
> job has the lock.  The second signon gets the error Message Queue
> allocated to another job Priior to running the initial program
> and when the
> job is transferred with TFRJOB, it displays the error, again, before the
> initial program starts.

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


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].