RE: Alternative to CPY for Optical

That may be how the CPY command is structured on optical. I've never run
CPY with a wildcard against optical. Your poor performance makes me
think that the command is going back and recreating the directory table
of contents after each file is copied. Fetching the directory table of
contents is hugely expensive on optical. This may be why FTP is better
than the wildcard transfer; FTP fetches the list once.

The target can be a problem, too. Are you copying to a Windows Network
Share through QNTC or an NFS mount? We've found that Windows starts to
bog hugely when you put more than 50,000 or so files in a single
directory path. This is because Windows searches the entire path table
of contents for duplicate names, beginning to end, for every file.

If these are Content Manager images, the paths for all the images are in
EKD0310. Construct the path as /QOPT/OPTVOL/OFLNAM/OSUBDIR/DOCID

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
sodonnell@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Sent: Monday, February 08, 2010 2:22 PM
To: Midrange Systems Technical Discussion
Subject: RE: Alternative to CPY for Optical

Apparently your hardware is a lot newer or faster than ours because 4
hours would be a miracle here. 4 Days is closer to what we are getting
in response times per platter.

I did just try using FTP and it looks like that is faster than CPY...but
the problem (always a new problem waiting to fill in the gaps...) now is
that the file names (images) stored on the platters all start with a
number, rather than a letter, and FTP is telling me that this is not a
valid character for a file name.

Yes, I did use NAMEFMT 1. Perhaps I will try bringing them to the PC
via
FTP and see if that gets around this limitation that the iSeries is
imposing.

Results to follow when I have them...

Four hours per platter is about what I get with CPY when I issue CPY
for each file on the platter. I have a database table that has a
record for each file on the platter. I have an application that sorts
the records by optical path and issues CPY for each one.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wayne McAlpine
Sent: Monday, February 08, 2010 1:15 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Alternative to CPY for Optical

I had a project last year to transfer ninety platters to DASD and ran
up against the same problem with the CPY command. The fastest
solution by far was to do an automated FTP transfer. Platters that
took a full day using CPY ran in a blazingly fast(!) four hours using

FTP.

One caveat: FTP will not create subdirectories automatically, so you
have to dump the directory tree structure first and then build your
FTP script with the necessary MD commands in it. I'd be happy to
share the script programs with you off-list if you're interested.

On 2/8/2010 11:08 AM, sodonnell@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:

Hi,

I need a way to copy images from a 3595 Optical drive (think it's
3595...the model numbers do not stick in my head) to DASD.

I've been using they CPY command like this:

CPY OBJ('qopt/F0105A/*') TODIR('/newdir') SUBTREE(*ALL) REPLACE(*YES)

And this works, but it's really slow. It can take, literally, days
to

copy a single platter of data.

Is there another method, even commercial, that someone can point me
to, that would allow me to perform this copy faster?

I've got something like 140 platters to copy and a small time window
to get it completed in.

Thanks!

--
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.