[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

45.0. "Is it soup yet?" by RDGENG::LESLIE (Andy ��� Leslie, CSSE VMS) Fri Jan 27 1989 10:27

    When I ran VWS, I could test for the existence of a logical,
    UIS$FILL_PATTERNS, to tell me that VWS had arrived and, as a batch
    or detached process, I could go do things now.
    
    What is the euivalent for DECWindows?
    
    Andy
    -----------------------------------------------
$ v = 'f$verify(0)'
$ if p1 .eqs. "" then p1 = "UIS$FILL_PATTERNS"
$10:
$ if f$trnlnm(p1,"lnm$system") .nes. "" then goto 20
$ wait 00:00:10
$ write sys$output "waiting for ''p1'..."
$ goto 10
$20:
$ exit 1+(f$verify(v)*0)
T.RTitleUserPersonal
Name		DateLines
45.1Try try again DECWIN::FISHERBurns Fisher 381-1466, ZKO3-4/W23Mon Jan 30 1989 17:1911
Are you talking about system startup time and waiting for DECwindows to get
started?  YOu could problably look at the DECW$SERVER process and wait for it
to go into HIB, but that is not very reliable.  Besides, it does not tell you
if the user has logged in, and it does not work on a node that is remote from
the server.

Why not just try to connect?  If you succeed fine; if you fail, well try
again.  This is what loginout does.

Burns
45.2Why I want thisLESLIE::LESLIEAndy ��� Leslie, CSSE / VMSTue Jan 31 1989 01:056
    I discovered that DW takes much longer to start up of my batch job to
    set known nods all was running. So I wanted to waut until DWS had
    started before pressing ahead.
    
    Andy
45.3Just don't tell VMS...WJG::GUINEAUWed Feb 01 1989 17:235
Take the SET KNOWN NODES ALL out of STARTNET.COM and submit it as a batch job
with a /AFTER="+0-00:10:00)".

John
45.4This works for usAKO455::SHEPROB-I-Biky-bi B-O-BoThu Feb 02 1989 08:1839
    When upgrading to VMS 5.0-2 or 5.1 (I forgot which), we were told
    by various sources not to fold, spindle, or mutilate STARTNET.COM
    
    Submit or start a detached process of STARTNET.COM and while it
    is running, check for the existance of a system logical name, SYS$NODE.
    
    If it exists, for all intends and purposes, DECNET has started and
    the SET KNOWN NODES ALL is probably running by this time.
    
$!
$!
$ NETNODE_UPDATE :== SYS$MANAGER:NETNODE_UPDATE.COM
$ IF F$SEARCH(NETNODE_UPDATE) .NES. "" THEN @'NETNODE_UPDATE'
$ RUN/DETACH SYS$SYSTEM:LOGINOUT.EXE /PROCESS=STARTNET -
      /INPUT=SYS$MANAGER:STARTNET.COM/OUTPUT=SYS$MANAGER:STARTNET.LOG 
$ X = 0
$CHECK_FOR_SYS$NODE:
$ WRITE SYS$OUTPUT "WAITING FOR DECNET TO START....."
$ WAIT 00:00:10
$ X = X + 1
$ IF X .EQ. 30 THEN GOTO NET_PROBLEM
$ NET_STARTED = F$TRNLMN("SYS$NODE")
$ IF NET_STARTED .EQS. "" THEN GOTO CHECK_FOR_SYS$NODE
$ @SYS$STARTUP:LTLOAD.COM
$!
$!
$!
$! start layered products here
$!
$!
$ EXIT
$!
$!
$NET_PROBLEM:
$ MAIL/SUBJECT="Problem starting Decnet on ''NODE'" NL: SYSTEM
$ REPLY/BELL "Problem starting Decnet on ''NODE'" 
$ EXIT
45.5The correct way is to wait for the NET: device to show up....IO::MCCARTNEYJames T. McCartney III - DTN 381-2244 ZK02-2/N24Thu Feb 02 1989 18:0118
The code that I lifted from STARTNET.COM to wait for the network is:

$ !
$ !   Make sure NETACP is finished initializing before continuing.
$ !
$ WAIT_FOR_NETACP_COUNTER = 0
$WAIT_FOR_NETACP:
$ IF .NOT. F$GETDVI("_NET0","EXISTS") THEN GOTO LOADNET_FAILURE
$ IF F$GETDVI("_NET0","MNT") THEN GOTO NETACP_INITIALIZED
$ WAIT_FOR_NETACP_COUNTER = WAIT_FOR_NETACP_COUNTER + 1
$ IF WAIT_FOR_NETACP_COUNTER .EQ. 120 THEN GOTO LOADNET_FAILURE
$ WAIT 0:0:1
$ GOTO WAIT_FOR_NETACP
$NETACP_INITIALIZED:
$ !
$ !   Do what ever you were waiting for the network to get started for....
$ !