|
Now that you've gotten this far, you should be able to create the things necessary to provide a LODRUN OPT01 capability. > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. > -- > [ Picked text/plain from multipart/alternative ] > Thanks to all for their replies. I believe that I have found an elegant > solution. Here are the instructions we'll be giving to our customers. I hope > someone else out there finds this information useful! > > > 1. Receive patch from our website on a PC with a CD burner. > > 2. Copy the file to a CD, being certain to specify a Volume ID and filename > in ALL UPPERCASE. (For this example, a Volume ID of "VOLUME" has been used) > > 3. Load the CD into the AS/400. > > 4. Determine the AS/400 filename of the file on the CD by using the WRKLNK > command as follows: > > WRKLNK OBJ('/QOPT') > > Select option 5 next to QOPT > Select option 5 next to the Volume ID > Note the filename > (For this example, a filename of C1P250~1.SVF has been used) > > 5. Create a savefile on the AS/400 (For this example, LIBRARY/SAVF is the > name of the savefile) > > 6. Run the CPYFRMSTMF command as follows: > > CPYFRMSTMF FROMSTMF('/QOPT/VOLUME/C1P250~1.SVF') > TOMBR('/QSYS.LIB/LIBRARY.LIB/SAVF.FILE') MBROPT(*REPLACE) > > Replace VOLUME with your Volume ID > Replace C1P250~1.SVF with your filename > Replace LIBRARY with the library name that your savefile is in > Replace SAVF with the name of your savefile > > 7. RSTOBJ from the savefile as per the standard patch installation > instructions. > > > > -----Original Message----- > From: John Ross [mailto:jross-ml@netshare400.com] > Sent: Wednesday, September 11, 2002 5:35 PM > To: midrange-l@midrange.com > Subject: Re: Getting a SAVF to a system without TCP/IP > > > Look > at http://archive.midrange.com/midrange- l/199912/threads.html#01499 I > like the REXX suggestion :) but I would have to say the SNDNETF, if you > they have SNADS running would be better. > > John Ross > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > NOTICE: This E-mail may contain confidential information. If you are not > the addressee or the intended recipient please do not read this E- mail and > please immediately delete this e-mail message and any attachments from your > workstation or network mail system. If you are the addressee or the intended > recipient and you save or print a copy of this E-mail, please place it in an > appropriate file, depending on whether confidential information is contained > in the message. > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > -- Paul Nelson 630-327-8665
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.