Conference bulova::decw_jan-89_to_nov-90

2470.0. "window crashes & mail link failures - V5.3-1" by FDCV07::MAURER (Tyrrany - Taxation w/o Representation) Mon Mar 19 1990 15:38

    Since installing V5.3-1, I've been seeing some strange errors on my
    VAXstation, some of which I can reproduce but some of which are
    transitory. Only once, just now, have I seen a meaningful error message
    on the screen as a pointer. I list below some of the symptoms and ask
    for advice for a cure.
    
    Configuration:  VAXstation II/GPX, 16Mb, VMS V5.3-1, DECwindows V2.0.
    		    Other details on request.
    
    Symptoms:
    
    1. Occaisionally, when preparing to send VAXmail using DECwindows EVE
    editor for the second time since MAIL startup, the whole mail utility
    (not just the create-send window) will crash. Starting it up from the
    session manager window works fine until the same conditions apply.
    
    2. Occaisionally, people sending VAXmail to me will get the
    "insufficient resources at remote node" error message, even when there
    are very few links in existence or tyasks in progress.
    
    3. Sometimes, when starting a second DECterm window, the startup never
    completes to the point that I get a DCL prompt. On hitting the return
    key with input focus on that window, it crashes. Only once has it given
    me an error message at this point; the message read "Error Creating
    Application  No PCB Available". I suspect this error relates to all of
    the symptoms listed here but cannot find any detailed help in any of
    the manuals sets I've looked at.
    
    4. When the second window opens correctly, the command "set host 0" and
    the subsequent login complete properly but after logging out of the
    'set-hosted' session (with or without any command activity having taken
    place in the meantime), a subsequent "set host 0" gives the error 
    "%JBC-F-PRCREAT, error creating process"
    "%REM-S-END, control returned to node ...."
    
    I'm looking for help on this. Anyone ?
    
    Thanks,
    
    Jon

Sounds like you need to up your process slots.
Run @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS FEEDBACK

    Thanks Jeff, seems to have done the trick. I'll make a point to run
    this every few weeks from now on, just to keep me 'honest'.
    
    Cheers,
    
    jon