|
Yes, Mike, exactly! -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of QSCANFSCTL Sent: Monday, October 30, 2006 10:53 AM To: 'Midrange Systems Technical Discussion' Subject: RE: Saving the IFS What directory was it processing when it failed? Was it '/QOpenSys/QOpenSys/QOpenSys ....' ? There are recursive links in the IFS that windows applications don't handle very well ... Mike Grant Bytware, Inc. 775-851-2900 http://www.bytware.com
-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Don Cavaiani Sent: Monday, October 30, 2006 5:19 AM To: Midrange Systems Technical Discussion Subject: RE: Saving the IFS This was rolling along nicely until I received the "insufficient memory" error - caused by the excessive length of the directory structure for a given file's location. Is there a way around this other than to exclude that particular directory? ______________________________________________________________ __________ _ Create a share for the IFS root directory. Then create this batch file: NET USE Z: \\iseries\root password /USER:userid ECHO QSYS.LIB > %TEMP%\OMITLIST XCOPY Z:*.* C:\ISERIESBACKUP /H/I/C/K/E/R/Y/D /EXCLUDE:%TEMP%\OMITLIST DEL %TEMP%\OMITLIST Where "iseries" is the domain name or IP address of your iSeries, "userid" is user profile on the iSeries with sufficient authority to read the IFS, and "password" is the password for userid. -------------------------------------------------------------- ---------- ------------------- This is pretty much the procedure I am trying now and which appears to
be working fine! All of the suggestions sounded logical, and I appreciate the input of each expert who responded. Thanks! -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jones, John (US) Sent: Thursday, October 26, 2006 7:47 AM To: Midrange Systems Technical Discussion Subject: RE: Saving the IFS Create a share for the IFS root directory. Then create this batch file: NET USE Z: \\iseries\root password /USER:userid ECHO QSYS.LIB > %TEMP%\OMITLIST XCOPY Z:*.* C:\ISERIESBACKUP /H/I/C/K/E/R/Y/D /EXCLUDE:%TEMP%\OMITLIST DEL %TEMP%\OMITLIST Where "iseries" is the domain name or IP address of your iSeries, "userid" is user profile on the iSeries with sufficient authority to read the IFS, and "password" is the password for userid. If you want to exclude other directories in addition to QSYS.LIB, add additional ECHO commands _after_ the first one as follows: ECHO dirname >> %TEMP%\OMITLIST The >> is intentional and means append to the file. I have not tested the above in total, however the NET USE works and I use XCOPY with the listed parms sans the /EXCLUDE all the time. That said, this may not capture everything so be sure to watch for messages. Also, this does an incremental backup - anything on the source that is
newer or newly exists is copied to the target. That way you're not copying the entire IFS dir structure every time; just the changes. The first time you run it the batch will copy everything, after that it should be much quicker. John A. Jones, CISSP Americas Information Security Officer Jones Lang LaSalle, Inc. V: +1-630-455-2787 F: +1-312-601-1782 john.jones@xxxxxxxxxx -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Don Cavaiani Sent: Thursday, October 26, 2006 7:20 AM To: Midrange Systems Technical Discussion Subject: RE: Saving the IFS Lukas, I guess I am thinking that this would be done from the Windows side - with just a xcopy command which would access (by drive letter) and copy all of the IFS '\'. Just not sure what the exact format/procedure would be. Wondering if anyone has already tried that? Thanks, Don -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lukas Beeler Sent: Thursday, October 26, 2006 6:02 AM To: Midrange Systems Technical Discussion Subject: RE: Saving the IFS Hi Don, Your question isn't as easy to answer as it might seem. There's the SAV command, which can be used to save IFS objects to a save file. I'm not sure if you can create save files on the QNTC filesystem, which would allow you to access a remote windows pc (without any special software installed, the SMB Server is standard with every windows install). Using SAV would probably be the most complete way to generate a backup off your files. There are other options, like creating tar or zip archives using the tar or jar command respectively in the Q-Shell environment (started with the command STRQSH). You could save these directly to the QNTC filesystem, but you would lose authorities etc. on your files if you choose this route. What do you want to achieve? I would recommend doing a Save 21 at least weekly, which includes a save of the IFS (to tape). Hope this helps, Lukas -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Don Cavaiani Sent: Thursday, October 26, 2006 12:51 PM To: midrange-l@xxxxxxxxxxxx Subject: Saving the IFS Is there a single command which will copy the entire IFS onto a PC hard drive (as a backup)? Would I need Client Access installed on the
PC? Don F. Cavaiani IT Manager Amerequip Corp. 920-894-7063 'Treat every person with kindness and respect, even those who are rude
to you. Remember that you show compassion to others not because of who
they are but because of who you are.'--Andrew T. Somers "When faced with the choice of being 'right' or being 'kind', choose the kind option every time." -- 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. This email is for the use of the intended recipient(s) only. If you have received this email in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this email without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but
we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. The information contained in this communication may be confidential and may be subject to the attorney-client privilege. If you are the intended recipient and you do not wish to receive similar electronic messages from us in the future then please respond to the sender to this effect. -- 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 message and any attachment to this e-mail message contain information that may be privileged and confidential. This e-mail and any attachments are intended solely for the use of the individual or entity named above (the recipient) and may not be forwarded to or shared with any third party. If you are not the intended recipient and have received this e-mail in error, please notify us by return e-mail or by telephone at 775-851-2900 and delete this message. This notice is automatically appended to each e-mail message leaving Bytware, Inc. -- 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
