RE: New Machine, QSECOFR not authorized

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

I don't understand this... it says you can ALWAYS sign on as QSECOFR at the
system console.

I don't know if I'm being entirely clear on my situation.

I have NO devices attached other than the 3489.  I am trying to use the 3489
as the system console.  I thought that DSP01 was the default name of the
system console, but I've seen the name "QCONSOLE" mentioned.  Is QCONSOLE
the default name of the console device?

If DSP01 is not the system console, then perhaps I have the console attached
incorrectly.  IBM shipped an 8-port twinax brick with a DB25 connector,
which I connected to the bottom connector on the back of the 270 (the
connector is labeled 2746).  I connected the Infowindow to Address 0 of the
brick.  It connects as DSP01.  Perhaps that bottom connector is not Port
0???  But the only OTHER DB25 connector is marked "DEBUG" on the upper right
of the box, and I can't imagine that's the console.

So I guess the question is, do I have the Infowindow hooked up to Port 0?  I
know it's address 0, but perhaps not Port 0.

In the meantime, I'll look into getting DST to work.

Joe

> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Alex A Moore
> Sent: Saturday, March 24, 2001 9:48 AM
> To: MIDRANGE-L@midrange.com
> Subject: RE: New Machine, QSECOFR not authorized
>
>
> Joe,
>
>       On a new box, QSECOFR is normally not authorized to the
> system console.
> See:
> 3.1.8 Limit Security Officer (QLMTSECOFR)
>
> The QLMTSECOFR system value controls whether a user with all-object
> (*ALLOBJ) or service (*SERVICE) special authority can sign on to any
> workstation. Limiting powerful user profiles to certain well-controlled
> workstations provides security protection.
> The QLMTSECOFR system value is only enforced at security level 30 and
> higher. "Security and Workstations" in topic 6.2 provides more information
> about the authority required to sign on at a workstation.
>
> You can always sign on at the system console with the QSECOFR, QSRV, and
> QSRVBAS profiles, no matter how the QLMTSECOFR value is set.
>
> this is out of the OS/400 Security reference.
>
> I would recommend
> http://publib.boulder.ibm.com/html/as400/v4r5/ic2924/index.htm
> to start a new system.
>
>       Alex
> BTW if all you have is a console, you IPL if you vary it off.
> -
>
> 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
+---