|
I wish IBM Upgrades the iSeries Navigator soon.
Haase, Justin C. wrote:
What about doing a user copy using iSeries Navigator? May not get the passwords, but heck of a lot easier than doing green-screen copies with output files (if it works). Not sure if it can do release to backlevel release copies tho - have to try it out and see.
Justin C. Haase - iSeries System Administrator IBM Certified Systems Expert - eServer i5 Kingland Systems Corporation email - justin.haase@xxxxxxxxxxxx
-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Al Barsa Sent: Wednesday, March 02, 2005 9:34 AM To: Midrange Systems Technical Discussion Subject: Re: Users from v5.2 to v5.1
SAVSECDTA can only go to the current or a future release. Do you have a SAVSECDTA, or A SAVSYS OMIT(*NONE or *CFG) from V5R1?
Your next alternative is to do DSPUSRPRF to output files, bring them back to the V5R1 system, and rebuild (*UGLY). Needless to say you will never get passwords.
Al
Al Barsa, Jr. Barsa Consulting Group, LLC
400>390
"i" comes before "p", "x" and "z" e gads
Our system's had more names than Elizabeth Taylor!
914-251-1234 914-251-9406 fax
http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com
Raul Jager
<raul@xxxxxxxxxx>
Sent by:
To midrange-l-bounce MIDRANGE-L@xxxxxxxxxxxx
s@xxxxxxxxxxxx
cc
Subject 03/02/2005 12:03 Users from v5.2 to v5.1
PM
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
I'm working normaly in V5.2, but now I need to set up a V5.1 model 270 with the same users. I used the SAVSEC command, in the V5.2 I can display the directory of the savefile, but in the V5.1 computer I only got "Invalid savefile" message. I didn't find a "*PRV" option in the SAVSEC, as there is in SAVOBJ.
Is there a way to transfer all my users, other than creating each profile in the 270?
TIA, Raul.
-- 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.
CONFIDENTIALITY NOTICE: This e-mail communication, including attachments, is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential, and may be legally privileged. If you are not the intended recipient or believe you received this communication in error, please reply to the sender indicating that fact and delete the copy you received. In addition, retention, dissemination, distribution, copying, or otherwise use of the information contained in this communication is strictly prohibited. Thank you.
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.