From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 19-JAN-1990 07:30
To:	MRGATE::"ARISIA::EVERHART"
Subj:	A Better (?) sys$welcome method.

Received: From UCBVAX.BERKELEY.EDU by CRVAX.SRI.COM with TCP; Thu, 18 JAN 90 16:39:22 PDT
Received: by ucbvax.Berkeley.EDU (5.61/1.41)
	id AA14774; Thu, 18 Jan 90 16:33:45 -0800
Received: from USENET by ucbvax.Berkeley.EDU with netnews
	for info-vax@kl.sri.com (info-vax@kl.sri.com)
	(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 18 Jan 90 20:17:31 GMT
From: zaphod.mps.ohio-state.edu!uwm.edu!fps!brodie@tut.cis.ohio-state.edu
Organization: Medical College of Wisconsin, Milwaukee, WI
Subject: A Better (?) sys$welcome method.
Message-Id: <3323.25b5de0c@fps.mcw.edu>
Sender: info-vax-request@kl.sri.com
To: info-vax@kl.sri.com

I posted this quite some time ago, but am doing so again in case some folks
missed it the first time around.  What I've done is create a multi-line
sys$welcome message that is based on a LOGICAL, not a file.  This is done
via the f$fao directive.  The reason this particular logical setup works
so well is that the system type, node name, and operating system are all
displayed.  No matter what your system, or how often you upgrade, the
login welcome notice automatically changes with it.

(one less thing to remember to change, I guess...)

I chose this particiular format because of the second line.  The welcome
message EXPLICITLY removes the word 'Welcome to....' (the DEC default!)
and the notice is changed to reflect a warning to unauthorized users.

The following segment, therefore, should be used to define sys$welcome.
(in systartup_v5.com, of course)


$!
$! Define sys$welcome as informative, yet important note.
$!
$ lineone = "Company ''f$getsyi("HW_NAME") (node ''f$getsyi("NODENAME")') " + -
  "running VAX/VMS ''f$edit(f$getsyi("VERSION"),"TRIM")'. " 
$ linetwo = "Unauthorized access to this system is prohibited."
$ assign/system "''f$fao("!_!AS!/!_!AS",lineone,linetwo)'" sys$welcome
$!

The prededing would create a welcome message that reads like

	Company VAX 6320 (node MYNODE) running VAX/VMS V5.1-1
	Unauthorized access to this system is prohibited.

In the above, change the word "Company" to reflect your company's name.
If your company name is real long, then you may want to change it to
look like---

$ lineone = "Yoyodyne mechinical instruments, Incorporated"
$ linetwo = "''f$getsyi("HW_NAME") (node ''f$getsyi("NODENAME")') " + -
  "running VAX/VMS ''f$edit(f$getsyi("VERSION"),"TRIM")'. " 
$ linethree = "Unauthorized access to this system is prohibited."
$ assign/system "''f$fao("!_!AS!/!_!AS!/!_!AS",lineone,linetwo,linethree)'" sys$welcome

which yields

	Yoyodyne mechinical instruments, Incorporated
	VAX 6320 (node MYNODE) running VAX/VMS V5.1-1
	Unauthorized access to this system is prohibited.

Of course, there's tons of ways to tdo this, and everyone has their
own preference.  I like it because it's DYNAMIC, informative, and
makes the user well aware that they better be legal.  There was some
discussion a while back about the legal principles involved with having
the word 'Welcome' in the login notice, this hopefully avoids that problem.

And, in large clusters, the nodename/systemtype thing kind of helps,
especially if you machine-hop like I do...

Since you will obviously want to test this out to some degree,
(tempoarily) change the last line to read

$ write sys$output "''f$fao("!_!AS!/!_!AS",lineone,linetwo)'"

and just execute the bugger.   Have fun.

-------------------------------------------------------------------------------
Kent C. Brodie - Systems Manager		brodie@fps.mcw.edu
Medical College of Wisconsin			+1 414 778 4500
     ____         ____    _____
    /   /)       /   /)__/ ____)
  /__ /  )     /__ /  ____/ 
 (   )  /     (   )  /         "How to tell a cat from a meatloaf"
 (___)/       (___)/            _CATS_  (B. Kliban)