|
I don't see IBM changing the naming convention for native objects anytime soon. The number of things that would be screwed up would be immense. 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 "DeLong, Eric" <EDeLong@Sallybeaut To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com> y.com> cc: Sent by: Subject: RE: Client Access vs CAE owner-midrange-l@mi drange.com 05/31/01 12:20 PM Please respond to MIDRANGE-L That's just for passwords? Any idea if this will extend to user profiles as well? Of course I see the problem there as QSYS naming conventions are by default 10 character object names, though I thought I'd heard that IBM has objects under the hood that are referenced by longer-than-10-character names. I'm probably mixing these recollections all up.... Also, are the new passwords still using the same encryption facilities as the old passwords? I seem to recall Lief complaining about how weak the encryption was. Eric DeLong Sally Beauty Company MIS-Sr. Programmer/Analyst 940-898-7863 or ext. 1863 -----Original Message----- From: barsa@barsaconsulting.com [mailto:barsa@barsaconsulting.com] Sent: Thursday, May 31, 2001 10:20 AM To: MIDRANGE-L@midrange.com Subject: RE: Client Access vs CAE There's a new system value for password length, QPWDLVL. Briefly (this is somewhat oversimplified, but good enough for this forum) there are two choices. Old passwords (10 characters long - non case sensitive) or new passwords (128 characters long - case sensitive). Unfortunately, DST/SST now has it's own user profiles (you can create your own users too) that have passwords that are 128 characters long, case sensitive, and expire every 180 days. The DST/SST user profiles have no relationship with the OS/400 user profiles, except when you use then new LPAR API's, in which case the passwords must match. 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 "DeLong, Eric" <EDeLong@Sallybeaut To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com> y.com> cc: Sent by: Subject: RE: Client Access vs CAE owner-midrange-l@mi drange.com 05/31/01 09:05 AM Please respond to MIDRANGE-L IF you are running a version of WinBlows that in fact allow access to network resources using a different userid/password. Win95, Win98, WinME are all unable to access netserver shares under a different id. WinNT, Win2K, etc. are ok with this. I think I heard that V5R1 supports userids and passwords longer than 10 character, but I can't say for sure if that's correct. Eric DeLong Sally Beauty Company MIS-Sr. Programmer/Analyst 940-898-7863 or ext. 1863 -----Original Message----- From: Eric Sundell PMI [mailto:ESundell@pmi.delta.org] Sent: Wednesday, May 30, 2001 6:43 PM To: 'MIDRANGE-L@midrange.com' Subject: RE: Client Access vs CAE Netserver is separate from CAE, you set up shares in Navigator to only the folders and printers you want to share. There is lots of info at IBM's Netserver site, In the scenario below it would prompt you for the password, when you map a drive to Netserver you can specify a different user name. CAE also has RUNRMTCMD so you shouldn't have a problem. Eric Sundell AS400/PC Specialist -----Original Message----- From: Wills, Mike N. (TC) [mailto:MNWills@taylorcorp.com] Sent: Wednesday, May 30, 2001 3:29 PM To: 'MIDRANGE-L@midrange.com' Subject: Client Access vs CAE We are thinking about changing over to CAE but we have a few questions regarding changing over. Any answers would be appreciated. We have heard that Client Access support is going away soon. 1) How have you guys handled security using the Netserver? 1a) What would happens in this scenario? Username on the 400: JohnDoeSmi Username on the network: JohnDoeSmith 2) We have some programs automatically upload data to a PC by using the RUNRMTCMD and some batch files on the PC. Will this work in CAE? If not, how much work is it to change, and what needs to be done to do it? Thanks in advance for your help. Mike Wills +--- | 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 +---
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
