[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

1728.0. "V5.3 doesn't start Decwindows for me ??" by DOPEY::DICKENS (What are you pretending not to know ?) Mon Nov 13 1989 12:22

In VMS V5.2, STARTUP.COM took over responsibility for starting Decwindows.
I had to remove the code I had in my startup procedure to start Decwindows.

Now I just installed V5.3, and it doesn't seem to be interested in starting
decwindows for me.  I did SEARCH SYS$SYSTEM:STARTUP.COM DECW and got nothing.
There was no reference to this change in the V5.3 release notes.

What's the deal ?  Should I take care of starting decwindows from the startup
procedure, ala V5.1 ?

						-Jeff
T.RTitleUserPersonal
Name
DateLines
1728.1DOPEY::DICKENSWhat are you pretending not to know ?Mon Nov 13 1989 12:312
I did the search command I mentioned in .0 on a V5.2 system, and found nothing
there either.  Still, on V5.2 it started Decwindows for me, and now it won't.
1728.2Look at WINDOW_SYSTEMDECWIN::FISHERBurns Fisher 381-1466, ZKO3-4/W23Mon Nov 13 1989 13:334
Perhaps your AUTOGEN changed the WINDOW_SYSTEM sysgen parameter.  It should be
1.  If it is not, put it in your MODPARAMS.DAT file and re-autogen.

Burns
1728.3STAR::MCLEMANJeff McLeman, VMS DevelopmentMon Nov 13 1989 14:164
You do have a valid VMS license, right? If the license loaded has expired
or is invalid, DECwindows will not come up.

Jeff
1728.4DOPEY::DICKENSWhat are you pretending not to know ?Mon Nov 13 1989 15:196
Yes, I do.  Damn, this is a p-i-t-a....

No license problem, window system is set to 1, etc. etc.


Also the seen map of this conference is trashed again.............
1728.5LESLIE::LESLIEAndy ��� LeslieMon Nov 13 1989 16:052
    The seen/unseen map is trashed for before 30-Oct. Let me know by mail
    any specific problems you are having.
1728.6Try DECnetAGBEAR::HORNERA.G.Bear, Old fashion teddy bearTue Nov 14 1989 08:116
    One thing that just happened here was a system that had an expired
    DECnet license after the upgrade.  As a result, DECnet wouldn't start.
    If DECnet doesn't start, DECwindows won't start.  Check and make sure
    that DECnet is successfully starting on your system.

               Dave
1728.7found the problemDOPEY::DICKENSWhat are you pretending not to know ?Tue Nov 14 1989 09:3413
Well, I figured it out.  It was a licence problem, but not so simple.

I have RSM (remote system manager) maintain the license database on my systems,
so the licenses were being loaded from RSM$C_PROCEDURES:RSM$LICENSE.LDB, which
gets loaded near the beginning of SYSTARTUP_V5.COM.  I guessed that the startup
procedure was checking for the license before it ran SYSTARTUP.  I copied RSM's
ldb to SYS$SYSTEM:LMF$LICENSE.LDB, and away it went.

This is new behavior.  It's works just fine without LMF$LICENSE.LDB on V5.2.

caveat emptor, RSM users.

						-Jeff
1728.8DECW$STARTUP.COM fails under stress ...DEMON::BAHNThe 1st 2000 lifetimes are toughest!Sun Nov 26 1989 01:1029
    Since I installed VMS V5.3 and DECwindows V2.0 on my MI Cluster, I have
    a related problem.  Under "normal" conditions ... 1 or 2 DECwindows
    satellites rebooting into a running cluster ... DECwindows starts up
    correctly.  However, under a full cluster reboot (after a power failure,
    for example), DECW$STARTUP.COM doesn't seem to function correctly. 

    Near the end of SYSTARTUP_V5.COM, I submit a command file named 
    SYSTARTNET.COM to batch.  This command file submits a couple of other 
    batch jobs, defines some logicals, etc., then runs STARTNET.COM.  This 
    worked fine under VMS V5.2.

    Now, as SYSTARTUP_V5.COM ends, I get the expected "DECwindows waiting 
    for DECnet to start" message, but it doesn't wait long enough ... I get 
    the "DECwindows cannot start without DECnet" message and must rerun 
    DECW$STARTUP.COM manually.

    To work around the problem, I've added the command:

            $ IF F$GETSYI("WINDOW_SYSTEM") .EQ. 1 THEN WAIT 00:02

    to the end of SYSTARTUP_V5.COM.  The 2 minute wait seems to do the 
    trick, but is not a very elegant solution.  Am I stuck with this or am I 
    overlooking something?  Did something change between VMS V5.2 and VMS 
    V5.3 that would explain this behavior?

    Thanks,
    Terry

1728.9LESLIE::LESLIEAndy ��� LeslieMon Nov 27 1989 09:373
    Put this line in your SYLOGICALS.COM.
    
$DEFINE/SYS/EXEC DECW$IGNORE_DECNET "TRUE"
1728.10Will any functions be lost?DEMON::BAHNThe 1st 2000 lifetimes are toughest!Thu Nov 30 1989 00:0913
    
    >>> $DEFINE/SYS/EXEC DECW$IGNORE_DECNET "TRUE"

        That line is in SYSTARTUP_V5.COM but the instructions 
        indicate that it should be commented out if you are, in fact, 
        using DECnet.

        If DECW$IGNORE_DECNET is true, will the satellites still be 
        able to use DECnet (for whatever DECwindows uses DECnet) 
        after NETACP gets started?

    Terry