[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

2070.0. "Whats an "associated mailbox"?" by SNUFF::KNOCH (Oh Captain my Captain!) Thu Jan 18 1990 10:37

When starting an application from Fileview I get a Work in Progress 
message that says the application is pending. Then a window pops up 
and informs me:


                   The task could not be started
                  because of the following error:

 Terminal has associated mailbox - terminate image and then SPAWN.



I can run applications just fine when they are started from 
DECterm or from the Applications menu from the Session Manager.

What is going on!??? Any thoughts as to what needs "adjusting"?

Thanks!
Lee

Note: System is a VS2/GPX with 16 MB memory and VMS V5.3 (new installation) 
T.RTitleUserPersonal
Name
DateLines
2070.1Any answer for this one ?PRFECT::PALKAFri Mar 02 1990 10:534
    I have the same problem, also with VMS V5.3. It used to work before I
    upgraded. Does anyone have any ideas ?
    
    Andrew
2070.2DECWIN::FISHERBurns Fisher 381-1466, ZKO3-4/W23Tue Mar 06 1990 15:4513
    You can look up "associated mailbox" in the VMS I/O user's guide.  It
    is a VMS concept that allows stuff like termaination messages,
    broadcast messages, etc from a terminal to be sent to a mailbox.  When
    there is a mbx associated with a terminal, there are odds and ends of
    things you can't to do the terminal (like destroy it, maybe?).
    
    How this all relates to FileView, I don't know.  Try a QAR.
    
    You might also try stuff like autogen, and increasing the process
    quota on the account.
    
    Burns
    
2070.3Process Limit fixed mine.DELNI::MHARRISNetwrk Integ'n ProjectsThu Mar 15 1990 11:509
    I too had the same problem under VMS V5.3
    
    The fix was to use AUTHORIZE to bump up the Proc Limit from 2
    to 8.
    
    Works fine now.
    
    M