|
For DST password, please try Login :QSECOFR Password : 222222 > -----Original Message----- > From: Ken Slaugh [SMTP:ken.slaugh@cm-inc.com] > Sent: Tuesday, March 02, 1999 11:35 AM > To: 'MIDRANGE-L@midrange.com' > Subject: RE: V4R3 Operations Console and DST user id/password > > QSECOFR cannot be used from a remote logon without changing at least one > system value. The more straightforward and secure way to do this is to > sign on a 'green screen' terminal as QSECOFR and create a user profile > with CRTUSRPRF command. Then, go MAIN, option 11. Client Access tasks, > optoin 21. Enroll CA/400 Users. Enroll the new user, do not enroll > QSECOFR as other variables will keep it from working anyways. > > Ken Slaugh > Senior Programmer/System Analyst > AS/400 Professional Network Administrator/MSE > Specialist - Client Access/400 > Chouinard & Myhre, Inc. > > > -----Original Message----- > > From: Bob Luebbe [SMTP:bluebbe@conn2000.com] > > Sent: Monday, March 01, 1999 3:56 PM > > To: MIDRANGE-L@midrange.com > > Subject: V4R3 Operations Console and DST user id/password > > > > We are running the V3R2 version of Client Access against a model 150 > > running > > V4R3. When trying to connect using the operations console, it prompts > > me > > for the DST user id and password. I tried QSECOFR for the user id and > > QSECOFR for the password. I also tried QSECOFR for the user id and > > the > > regular password we set up for QSECOFR. But it still comes up with an > > error > > message validating the security information. > > > > I ran CHGDSTPWD *DEFAULT, but it still fails. > > > > What is the difference between a DST user id and a regular user id? > > Any ideas on how to get me past this is appreciated. > > > > Thanks, > > > > Bob Luebbe > > > > > > +--- > > | 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 +---
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.