RE: New Machine, QSECOFR not authorized -- MIDRANGE-L

I don't understand this: on my model 170, I have two devices, QCONSOLE and
DSP01.  They look as follows:

                           Display Device Description

 Device description . . . . . . . . :   QCONSOLE
 Option . . . . . . . . . . . . . . :   *BASIC
 Category of device . . . . . . . . :   *DSP

 Device class . . . . . . . . . . . :   *LCL
 Device type  . . . . . . . . . . . :   3487
 Device model . . . . . . . . . . . :   HG
 Port number  . . . . . . . . . . . :   0
 Switch setting . . . . . . . . . . :   0
 Shared session number  . . . . . . :   0
 Online at IPL  . . . . . . . . . . :   *NO
 Attached controller  . . . . . . . :   QCTL
 Keyboard language type . . . . . . :   USB
 Character identifier . . . . . . . :   *KBDTYPE
 Allow blinking cursor  . . . . . . :   *YES
 Print device . . . . . . . . . . . :   *SYSVAL

 Press Enter to continue


                           Display Device Description

 Device description . . . . . . . . :   DSP01
 Option . . . . . . . . . . . . . . :   *BASIC
 Category of device . . . . . . . . :   *DSP

 Device class . . . . . . . . . . . :   *LCL
 Device type  . . . . . . . . . . . :   3487
 Device model . . . . . . . . . . . :   HC
 Port number  . . . . . . . . . . . :   0
 Switch setting . . . . . . . . . . :   0
 Shared session number  . . . . . . :   0
 Online at IPL  . . . . . . . . . . :   *YES
 Attached controller  . . . . . . . :   CTL01
 Keyboard language type . . . . . . :   USB
 Character identifier . . . . . . . :   *KBDTYPE
 Allow blinking cursor  . . . . . . :   *YES
 Print device . . . . . . . . . . . :   *SYSVAL

 Press Enter to continue

To me, other than the model, they look exactly the same.  But my console is
varied off:

     DSP01       3487    Sign-On display
     DSP02       3487    Powered off or not yet available
     DSP03       3487    Powered off or not yet available
     DSP04       3487    Sign-On display
     QCONSOLE    3487    Unavailable (use Opt 1)

Above is the status of my various devices.  When I hit Alt-Jump on my 3486,
I bounce back and forth between DSP01 and DSP04.  I guess that my console is
varied off on the model 170, and I'm instead using DSP01.  When I look at
the system value QCONSOLE, it says DSP01.
----

Okay, that's the moel 170 and the 3486.  I guess I understand them well
enough.  But what's with my model 270?  Could it be that my system console
is varied off on the new box, but nobody set DSP01 to be accessible to
QSECOFR?

If so, how in the world do I fix it?

Joe


> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Neil Palmer
> Sent: Saturday, March 24, 2001 1:33 PM
> To: MIDRANGE-L@midrange.com
> Cc: Joe Pluta
> Subject: RE: New Machine, QSECOFR not authorized
>
>
> Bingo,
>
> The 8 slots are labelled 0 to 7.  Make sure your cable is plugged into
> port 0.
> Assuming auto-config is turned off, just power off your console and power
> on and it should auto-config.
> DSP01 doesn't mean it's the console - just the first device that
> configured.  System value QCONSOLE automatically updates with the system
> console device name (Port 0 Address 0).
> TO avoid confusion I would suggest, after you're up, renaming
> from WRKDEVD
> *DSP using another session, so the system console IS DSP01.
>
> ...Neil
>
>
>
>
>
>
> "Joe Pluta" <joepluta@PlutaBrothers.com>
> Sent by: owner-midrange-l@midrange.com
> 2001/03/24 13:34
> Please respond to MIDRANGE-L
>
>
>         To:     <MIDRANGE-L@midrange.com>
>         cc:
>         Subject:        RE: New Machine, QSECOFR not authorized
>
>
> Wait a second here... there are eight slots on the brick... are those PORT
> numbers?  And then I have to configure the TERMINAL to an address???
>
> If so, how the heck do I configure the 3489?
>
> (Shows how long it's been since I've done any twinax)
>
> Joe
>
> > -----Original Message-----
> > From: owner-midrange-l@midrange.com
> > [mailto:owner-midrange-l@midrange.com]On Behalf Of Neil Palmer
> > Sent: Saturday, March 24, 2001 12:24 PM
> > To: MIDRANGE-L@midrange.com
> > Cc: Joe Pluta
> > Subject: Re: New Machine, QSECOFR not authorized
> >
> >
> > I would suspect the twinax screen isn't configured for addres 0.
> >
> > Neil Palmer      DPS Data Processing Services Canada Ltd.
> > 50 Acadia Avenue, Ste.102                   AS/400~~~~~
> > Markham, Ontario, Canada.   ____________          ___  ~
> > Phone:(905) 474-4890 x303   |OOOOOOOOOO| ________  o|__||=
> > Cell.:(416) 565-1682 x303   |__________|_|______|_|______)
> > Fax:  (905) 474-4898         oo      oo   oo  oo   OOOo=o\
> > mailto:NeilP@DPSlink.com  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > http://www.DPSlink.com     iSeries 400  The Ultimate Business Server
> >
> >
> >
> >
> >
> >
> > "Joe Pluta" <joepluta@PlutaBrothers.com>
> > Sent by: owner-midrange-l@midrange.com
> > 2001/03/24 09:56
> > Please respond to MIDRANGE-L
> >
> >
> >         To:     <MIDRANGE-L@midrange.com>
> >         cc:
> >         Subject:        New Machine, QSECOFR not authorized
> >
> >
> > I just plugged in a brand new machine, a model 270.  I connected the
> coax
> > connector and the power plug, and turned the machine on.  I have a 3489
> > Infowindow II attached to Port 0, and it comes up as "DSP01" in QBASE.
> So,
> > I figure everything is cool.
> >
> > I log on as QSECOFR/QSECOFR, and I get CPF1110 Not Authorized to
> > Workstation!  How can this be?  I tried QSYSOPR and QSECADM, neither of
> > which would log on, and now I'm at the dreaded CPF1116 Next Unsuccessful
> > Attempt Varies Off Device.
> >
> > I am in a quandary.  How do you initially make DSP01 available to sign
> on
> > as
> > QSECOFR?  There aren't a whole lot of manuals, but I do have the
> > InfoCenter
> > disks - is the information there?  Do I have to go through a special
> > signon?
> > (I seem to recall there was a special service signon - is that what I
> have
> > to do?  And if so, how do I do it?)
> >
> > As a second question, what do you do if you DO manage to vary off DSP01?
> > How do you get it back?
> >
> > Any help greatly appreciated.
> >
> > Joe
> >
> >
> >
> >
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> > MIDRANGE-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator:
> > david@midrange.com
> > +---
> >
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
>
>
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---