[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::hackers_v1

Title:-={ H A C K E R S }=-
Notice:Write locked - see NOTED::HACKERS
Moderator:DIEHRD::MORRIS
Created:Thu Feb 20 1986
Last Modified:Mon Aug 03 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:680
Total number of notes:5456

406.0. "SET host/dte input from a file?" by AMIGO::MULLEN (Dan Mullen) Wed Feb 11 1987 10:08

$ SET HOST   will take input from a file but $ SET HOST/DTE  won't.
Is there a way to fool SET HOST/DTE into taking input from a file.
My reason for trying this is that I'm trying to get up to LTA1000
on my �Vax in an attempt to reproduce a bug reported.  I have
borrowed a DECserver 100 from comminications and have my a �VAX hooked
up to it (via tta1).   $ Set Host/Dte/nolog TTA1 gets me to the
DECserver and I can get to other machines from there.

A regular set host isn't good enough to reproduce the problem as
you can't get 1000 users on a system and lower RTAnnn's get reused
if you logout. Lower LTAnnn's don't get reused.  Our cluster never
stays up long enough to get up that high and munging the data structure
that holds the device name was shot down in an earlier note.

I don't like the thought of logging in manually 1000 times to
do this so a command file that repeats it for me is what I'm getting
at but I've failed to make /DTE work.

Any help is appreciated,

..Dan

ps. there is a note in the LAT conference asking about going
directly to LTA1000.

pps. The problem
              <<< CLT::ULTRIX$:[NOTES$LIBRARY]VAX_BASIC.NOTE;1 >>>
                         -< Discussions on VAX BASIC >-
================================================================================
Note 199.0                    LTA1000, INVDEVNAM                      No replies
WATNEY::ROARK "Kelly Roark"                           5 lines   5-JAN-1987 18:55
--------------------------------------------------------------------------------

I've had a customer report a INVDEVNAM error when trying a generic PRINT
statement after logging into an LTA device greater than LTA999.  Has anyone
seen this before and is there a fix coming 'round the pike?

Kelly

T.RTitleUserPersonal
Name
DateLines
406.1MOTHRA::DUTKONestor Dutko, VMS/VAXclusters CSSEWed Feb 11 1987 11:2822
    Hmmm...  I think I may know what is wrong.  Note the change in device
    name?  Well, if you have the device before LTA999, the process has
    reserved in the PCB seven bytes for the device name.  Therefore,
    the device will appear as LTA999:.  Note that once you get to the
    devices in the thousands, there is a *problem*.  Now you still have
    the seven bytes reserved for the terminal (PCB$T_TERMINAL), but
    the colon is omitted.  
    
    If your application is trying to do anything peculiar where it assumes
    the device, and there is no colon, that is where the problem would
    occur.
    
    Sorry, about this not addressing the problem with getting up to
    unit 1000, but perhaps you may get some information from the above
    description and not have to do the reproduction of problem.  
    
    BTW, I believe that you could have used LATCP and created an additional
    port LTA1000, and logged into it as an appklication and gone from
    there, instead of trying to get VMS and LTDRIVER to incrementally
    increase the unit numbers that high...
    
    -- Nestor