RE: Re: Sixpack 1.2: how to log in two users?

I don't have the six pack but I get get 2 x model 2 and 2 x model 4 devices
connected on the five pack... 

Dave Wade G4UGM
Illegitimi Non Carborundum



> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Fran Hensler
> Sent: 11 August 2010 22:16
> To: [email protected]
> Subject: Re: [H390-VM] Re: Sixpack 1.2: how to log in two users?
> 
> 
> Bob -
>  
> I have not installed the 1.2 beta SixPack.
>  
> I have in DMKRIO:
>        RDEVICE ADDRESS=(2C0,7),DEVTYPE=3278,MODEL=4
> and my SixPack.conf has:
>  
> # Console Printers
>  
> 0009    3215-C  NOPROMPT
> 000A    1052    NOPROMPT
>  
> # Display Terminals
>  
> 02C0    3270
> 02C1    3270
> 02C2    3270
> 02C3    3270
> 02C4    3270
>  
> When I do a CP Q 2C0-2C7 I get:
> GRAF 2C0 LOGON  AS MAINT
> GRAF 2C1 ENABLED
> GRAF 2C2 ENABLED
> GRAF 2C3 ENABLED
> GRAF 2C4 ENABLED
> GRAF 2C5 OFFLINE
> GRAF 2C6 OFFLINE
> GRAF 2C7 OFFLINE
>  
> The 5 terminals I have in the conf file were all ENAbled when 
> VM came up.
>  
> I can connect to all 5 enabled terminals.
>  
> I have no Model-2 terminals in my CONF.
> Perhaps that is the key.
>  
> /Fran Hensler at Slippery Rock University of Pennsylvania USA 
> for 47 years
>     mailto:[email protected]  http://zvm.sru.edu/~fjh  +1.724.738.2153
>               "Yes, Virginia, there is a Slippery Rock"
> --------------------------------------------------------------
> ------------
>  
> On Wed, 11 Aug 2010 05:48:50 -0000 Robert O'Hara said:
> >Mike,
> >
> >Well, you have just exposed me as a noob regarding DMKRIO, 
> which is the 
> >file that defines CP's I/O configuration.  The VM Sixpack DMKRIO 
> >ASSEMBLE is on MAINT 94, and has the following lines for 
> terminals and 
> >their controllers:
> >
> >RCTLUNIT ADDRESS=018,CUTYPE=3215
> > RDEVICE ADDRESS=004,DEVTYPE=3215
> > RDEVICE ADDRESS=005,DEVTYPE=3215
> > RDEVICE ADDRESS=006,DEVTYPE=3215
> > RDEVICE ADDRESS=007,DEVTYPE=3215
> > RDEVICE ADDRESS=008,DEVTYPE=3215
> > RDEVICE ADDRESS=009,DEVTYPE=3215
> > RDEVICE ADDRESS=00A,DEVTYPE=3215
> > RDEVICE ADDRESS=(01F),DEVTYPE=3215
> >
> >RDEVICE ADDRESS=(010,7),DEVTYPE=3277
> >
> >RCTLUNIT ADDRESS=0C0,CUTYPE=3272,FEATURE=32-DEVICE
> > RDEVICE ADDRESS=(0C0,32),DEVTYPE=3277
> >
> >RCTLUNIT ADDRESS=1C0,CUTYPE=3272,FEATURE=16-DEVICE
> > RDEVICE ADDRESS=(1C0,7),DEVTYPE=3277
> > RDEVICE ADDRESS=(1C7),DEVTYPE=3284
> > RDEVICE ADDRESS=(1C8,7),DEVTYPE=3277
> > RDEVICE ADDRESS=(1CF),DEVTYPE=3284
> >
> >RCTLUNIT ADDRESS=2C0,CUTYPE=3272,FEATURE=16-DEVICE
> > RDEVICE ADDRESS=(2C0,7),DEVTYPE=3278,MODEL=4
> > RDEVICE ADDRESS=(2C7),DEVTYPE=3284
> > RDEVICE ADDRESS=(2C8,7),DEVTYPE=3277
> > RDEVICE ADDRESS=(2CF),DEVTYPE=3284
> >
> >RCTLUNIT ADDRESS=3C0,CUTYPE=3272,FEATURE=16-DEVICE
> > RDEVICE ADDRESS=(3C0,7),DEVTYPE=3277
> > RDEVICE ADDRESS=(3C7),DEVTYPE=3284
> > RDEVICE ADDRESS=(3C8,7),DEVTYPE=3277
> > RDEVICE ADDRESS=(3CF),DEVTYPE=3284
> >
> >The configuration file as currently shipped with the SixPack 
> does not 
> >define this many terminals.  If I expand it to match the above, it 
> >looks like this:
> >
> >0009    3215-C  NOPROMPT
> >000A    1052    NOPROMPT
> >
> >00C0.32 3270
> >01C0.7  3270
> >01C8.7  3270
> >02C0.7  3270
> >02C8.7  3270
> >03C0.7  3270
> >03C8.7  3270
> >
> >With the above configuration, I can connect many 3278-2 (24 line) 
> >terminals. They come in at 0C0 and go up from there.
> >
> >Also, I can connect a 3278-4 (40 line) terminal at 2C0.  But 
> I cannot 
> >connect a second 3278-4.
> >
> >Does anyone know what is amiss here?
> >
> >Thanks, Bob
> >
> >
> >
> >--- In [email protected], Mike Voss <mike@...> wrote:
> >>
> >> Now for an *actual* noob question:
> >>
> >> terminals 0C0-0C2 are defined in hercules, but I can only open a 
> >> session and
> >connect to CP through 0C0. 0C1 just sits at the Hercules banner.
> >>
> >> I've heard the term directory, how does that interact with or 
> >> substitute for
> >VM's IOGEN? Where do I find either of these entities? -Or does this 
> >have nothing at all to do with that?
> >>
> >> A two-or-three-sentence primer on VM I/O targeted to an MVSer will 
> >> probably
> >kickstart me suitably. I know MVS sysgens but this seems to 
> come at me 
> >a little bit sideways. I'll wager that at the end of the day 
> it's more 
> >familiar than I think.
> >> I always secretly wanted to be a DOS/VM guy but none of my 
> employers 
> >> ever
> >wanted to, er, "re-size" their existing MVS installation. At my very 
> >first shop we were bringing the systems in-house from a 
> service bureau, 
> >and all the VM manuals had arrived, and I was burning through those 
> >when they changed their minds and I had to learn instead to support 
> >MVS/SP. Can't complain, it just would have been fun... -and 
> >retrospectively, the right call for a company of that size. 
> IBM sales 
> >was just too darn good.
> >>
> >
> >
> >
> 
> 
> ------------------------------------
> 
> Yahoo! Groups Links
> 
> 
>