HP3000-L Archives

February 1996, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John Korb <[log in to unmask]>
Reply To:
John Korb <[log in to unmask]>
Date:
Wed, 28 Feb 1996 23:55:14 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
After asking around, I've received the following suggestions (regarding limits).
 
1)  Increase the CI command length.  What about 512 characters?  768?  POSIX
    file names, redirection, INFO= strings, etc. can yield some very long
commands.
 
2)  Increase the record width for NS VT sessions so that file equations can
override
    the defined record width (ie so that NS VT sessions work like serial
sessions).
 
<GRIPE>
NS VT's 80 byte hard and fast limit is horrible!  You can run a program that
generates a 132 column display fine locally, but try to run it over NS.
What you get is a mess because the lines are chopped at 80 bytes.
Reconfigure your devices for 66 word records you say.  Done.  Now do a LISTF
,1 and you'll see just ONE of the side effects.  On a serial session you can
use a file equation to redefine the terminal device record width.
Unfortunately, using file equations where NS VT is involved is useless - the
file equations are ignored.
</GRIPE>
 
John
--------------------------------------------------------------
John Korb                            email: [log in to unmask]
Innovative Software Solutions, Inc.
 
The thoughts, comments, and opinions expressed herein are mine
and do not reflect those of my employer(s), or anyone else.

ATOM RSS1 RSS2