|
Do, No. QLMTSECOFR being set to '1' requires that any user with *ALLOBJ and *SERVICE authority be authorized to any device (other than the console) to sign on, but QPGMR and authorize the user to the device typically. Most people change this system value to '0', unfortunately. This is one of the new "lockable" system values from SST in V5R2. If you not familiar with this function, there is a session given at COMMON that covers this... Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Don <dr2@xxxxxxxxxxxx> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> Sent by: cc: midrange-l-bounces@x Subject: Re: QSECOFR can only login to the System Console idrange.com 02/26/2003 11:34 PM Please respond to Midrange Systems Technical Discussion Al, isn't there a sysval that says QSECOFR can only sign on to the console? I'm brain dead this evening, but seems like I recall that from my scrounging and sitting in your sysval session... Don in DC ------------------------ On Wed, 26 Feb 2003, Al Barsa wrote: > > It is plausible that all of the profiles have been *DISABLED, however > QSECOFR can always sign on to the console. This is just an educated guess. > > Al > > Al Barsa, Jr. > Barsa Consulting Group, LLC > > 400>390 > > 914-251-1234 > 914-251-9406 fax > > http://www.barsaconsulting.com > http://www.taatool.com > > > > > > > "Tom" > <tomh@xxxxxxxxx> To: midrange-l@xxxxxxxxxxxx > Sent by: cc: > midrange-l-bounces@x Subject: QSECOFR can only login to the System Console > idrange.com > > > 02/25/2003 05:45 PM > Please respond to > Midrange Systems > Technical Discussion > > > > > > > In setting up a new 9406-270, I find that the QSECOFR (or any other secofr > profile) can only log in to the system console. I've checked system value > QLMTSECOFR and it's set to '0'. What else should I be looking at in order > to allow secofr profiles to log in at other than the system console? > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
