[comp.os.vms] SYS$ANNOUNCE/WELCOME length

RAND@merrimack.EDU ("Rand P. Hall") (02/18/88)

Can anyone provide a rational for SYS$ANNOUNCE and SYS$WELCOME's limit
of 63 characters? 

Rand P. Hall                         rand@merrimack.edu (csnet)
Director, Academic Computing         617.683.7111
Merrimack College
315 Turnpike Rd.                     "There is elegance in simplicity."
North Andover, Mass. 01845                      - Kimball S. Maddocks

helen@uhccux.UUCP (Helen Rapozo) (02/24/88)

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)
>Director, Academic Computing         617.683.7111
>Merrimack College
>315 Turnpike Rd.                     "There is elegance in simplicity."
>North Andover, Mass. 01845                      - Kimball S. Maddocks

No idea as to why the 63 character limit, but it is a logical and
you can point it to a file by putting a '@' before the text.  For
example:

	DEFINE/SYSTEM SYS$ANNOUNCE @SYS$MANAGER:ANNOUNCE.TXT



-- 

"No sweat, parts are parts"

gil@icus.UUCP (Gil Kloepfer Jr.) (02/26/88)

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...      |
+=============================================================================+

rrk@byuvax.bitnet (02/26/88)

The fact that you can specify "@sys$manager:welcome.txt" as your definition
of SYS$WELCOME and then put the real text in a file makes that limit OK.

seibel@cgl.ucsf.edu (George Seibel%Kollman) (02/26/88)

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? 

I for one sure hate to sit around watching 1000 bytes of somebody's
dumb welcome message scroll by at 1200 baud...  maybe someone's trying
to tell us something.

George Seibel
UCSF

cfchiesa@bsu-cs.UUCP (Sir Xetwnk) (02/27/88)

In article <10721@cgl.ucsf.EDU>, seibel@cgl.ucsf.edu (George Seibel%Kollman) writes:
> 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? 
> 
> I for one sure hate to sit around watching 1000 bytes of somebody's
> dumb welcome message scroll by at 1200 baud...  maybe someone's trying
> to tell us something.
> 
> George Seibel
> UCSF

George, you might find THIS trick handy; I do the following for the very
reason you mention -- too-long welcome text on too-slow terminals:

Enter your username as usual.
Enter your password as usual, but IMMEDIATELY after pressing return, press
CONTROL O ("oh," not "zero").  If you catch it fast enough you can turn
the *OUTPUT OFF* before any welcome text spews out at you.  This disables
ALL output until you are actually logged in; output resumes somewhere be-
tween that point and execution of the system LOGIN.COM (basically, what I
mean is that any output in YOUR login.com will come out as always, and that
by the time you get to type anything, output will have been restored for you).

Chris Chiesa
Ball State University

-- 
<><><><><><><><><><><><><><><><><><><><><><><><><><><><> Chris Chiesa <><><><><>
<> {ihpn4|seismo}!{iuvax|pur-ee}!bsu-cs!cfchiesa                              <>
<> cfchiesa@bsu-cs.UUCP                                                       <>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>