Conference bulova::decw_jan-89_to_nov-90

2485.0. "problem interactively kick off DECterm/Fileview" by GIDDAY::SHCHIU () Tue Mar 20 1990 23:47

I have a  customer site  with the following configuration:

MVAX3400, MVAX2000, MV3100 s. V5.3  forming a LAVC cluster.

before they upgraded to v5.3, the DECwindow worked just fine.

under V5.3, when user tried to interactively kick off either  DECterm or
Fileview from application menu bar of the session manager ,

The message of Starting  session DECterm or Fileview,
appear under session manager, but there is no window created.
The handled process(s)    create DECterm or Fileview changed
theirs  state to COM then to HIB state.

I went into SDA , look at the process, there are shortage of 
process quota.

User had have tried:
1. rename everyone of DECW$*default.* and recreate a new set of files.
2. Autogen getdata reboot initial.
3. increase BYTLM to 64000, 
            WSDEFAULT 1024,WSQUO = 4096 , WSEXTENT 6000
            PGFLQUOTA  25000

It does not work.

I check sysgen parameters:

GBLSECTION  650,  250 USED,
GBLPAGES 55498.

FREE_GBLPAGES 41712,  CONT_GBLPAGES 41710.

There are plenty of pool space.

The strange thing is if Fileview or DECterm fired up by BAtch or
detached process then it just work fine.

I can't reproduce the problem on my own machines.


May be someone have a better idea what to look for ?

Thanks for any suggestion !


/Stanley





    

    
    Sounds like maybe you're running into the famous "if you're doing an
    INQUIRE or READ from SYLOGIN.COM or LOGIN.COM your process won't
    start but we're not going to tell you why" problem.
    
    In version 2 of DECwindows, Session Manager was changed in the way
    it starts processes.  What it basically does is run LOGINOUT and
    passes it the commands to create the process.  Your SYLOGIN and LOGIN
    are being executed twice .. once by LOGINOUT and once by the created
    process (DECterm, VUE etc).  When LOGINOUT runs, if it encounters
    an attempt to solicit input from ... it kindly aborts.  
    
    A reasonable workaround is to have LOGIN.COM get the terminal device
    for the process and if it is an MBA device, don't do the inquire.
    It should be MBA for all (most) non-DECterm processes. For example:
    
    $TERM = F$GETJPI("","TERMINAL")
    $IF F$LOCATE("MBA",TERM) .NE. F$LENGTH(TERM) THEN GOTO SKIP_INQUIRE
    $INQUIRE JUNK "GIVE ME SOME JUNK  "
    $SKIP_INQUIRE:
    
    
    Donna

        General Solution:

	LOGIN.COM should handle processes that have a mailbox terminal 
	the same as they handle NETWORK, BATCH, and OTHER processes.

	Kevin

    
    
    thanks for the help !
    
    /Stanley