Path: utzoo!utgpu!water!watmath!clyde!burl!codas!mtune!icus!gil
From: gil@icus.UUCP (Gil Kloepfer Jr.)
Newsgroups: comp.os.vms
Subject: Re: SYS$ANNOUNCE/WELCOME length
Summary: Just use a file I think...
Message-ID: <267@icus.UUCP>
Date: 25 Feb 88 18:19:26 GMT
References: <8802231609.AA21202@ucbvax.Berkeley.EDU>
Reply-To: gil@icus.UUCP (Gil Kloepfer Jr.)
Organization: Bowne Management Systems, Inc, Mineola, NY
Lines: 28

In article <8802231609.AA21202@ucbvax.Berkeley.EDU> RAND@merrimack.EDU ("Rand P. Hall") writes:
>Can anyone provide a rational for SYS$ANNOUNCE and SYS$WELCOME's limit
>of 63 characters? 
>
>Rand P. Hall                         rand@merrimack.edu (csnet)

I've never seen the limit you speak of (therefore, I can't provdide a
a rationale for it) .. but I do know if you define SYS$ANNOUNCE and SYS$WELCOME
to point to a file:

	$ DEFINE/SYSTEM/EXEC SYS$WELCOME "@SYS$MANAGER:WELCOME.TXT"

I never had a problem with a limit this way.  If you need more than 63
characters, try this.

Note though that the description generated by LATCP for your decservers
for that computer's service name will be messed-up unless you specifically
specify one (not use the default of the message in the SYS@WELCOME string).

+====================================+========================================+
| Gil Kloepfer, Jr.                  | Net-Address:                           |
| Senior Programmer                  | {boulder,ihnp4,talcott}!icus!gil       |
| Bowne Management Systems, Inc.     | Voice:  Home: (516) 968-6860           |
| 235 E. Jericho Turnpike            |         Office: (516) 248-6840 x796    |
| Mineola, New York  11501           | Internet: gil@icus.UUCP                | 
+====================================+========================================+
| Disclaimer: My employers know I'm right, but will never admit to it...      |
+=============================================================================+