Have you looked at your line description? You should have it set for full
duplex, whatever the card speed might be.

Paul Nelson
Cell 708-670-6978
Office 512-392-2577

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Sent: Monday, October 01, 2007 1:49 PM
To: midrange-l@xxxxxxxxxxxx
Subject: IFS and FTPing libraries

Hello everyone,

I would like to copy/save libraries from my IFS to a backup server we
have. This will replace the SAVLIB and SAVCHGOBJ we are currently using
for backupsk to tape.

What is the syntax I should use to copy a library from my IFS to the
Server? I haven't used the IFS much, we do most everything with QDLS. I
know, it's slower than dirt, but I am trying to learn more about the IFS
right now, after 25 years of programming.

Here is what I am currently trying to use to FTP the SAVF file I create
nightly. AMFLIB below is a SAVF that has my data in it. As stated above,
I would like to just copy the library from the IFS to the server, without
doing the "Save" stuff, to cut the down time for my Users. It works, but
extremely slow. About 2 1/2 hours for a SAVLIB for this library (Save
through FTP completion).

USER amapics password1
namefmt 0
cd Monday

Also, during my testing I can only get about 1Mg/sec transfer rate. My
Network guy thinks I should be getting about 10 Mg/sec. With my tape
drive, it is rated or about 7 Mg/sec. No one is on the System, nor
network, when this runs.

Thanx for any suggestions you can give me.

We have an AS/400e 9406-620 at V4R5.



Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct (320) 679-6683
Toll free (800) 388-2155 ext. 6683
Fax (320) 679-4516

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].