• Subject: RE: Message queue &1 allocated to another job.
  • From: Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>
  • Date: Tue, 1 May 2001 09:58:44 -0400

Nick Runnalls wrote:

>On sign on if a user is already signed on at another 
>session, we get a CPF2451 Message queue &1 
>is allocated to another job.

This is because the message queue is in *BREAK mode.  If you change the user
profile or initial program to have the user's message queue in *NOTIFY or
*HOLD mode you won't see these messages.  Of course, messages sent to that
user won't break anymore either.  You get to choose which is less desirable.

>We also have problems with following screen.
>                       Attempt to Recover Interactive Job
>Previous interactive job was interrupted due to a device 
>error at the work station.

This is due to the workstation cutting the connexion without signing off
first.  Also, there is a system value and a job setting for device recovery
action that controls the system's behaviour when the disconnect occurs.
Your jobs are set to *DSCMSG.  Look at the help for WRKJOB option 2
parameter DEVRCYACN for a brief overview.

Hope that helped,
Buck Calabro
Commsoft; Albany, NY
"Nothing is so firmly believed as
 that which we least know" -- Michel Montaigne
Visit the Midrange archives at http://www.midrange.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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.