Re: CPY command error

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

There aren't any symbolic links involved, perchance?   I know Windows 
doesn't support them, and thus you get a "Function not supported by file 
system" error when you try to copy them over Windows Networking.

IBM's error reporting is rather pitiful. (I hate debugging by trial and 
error, I like to know _what_ the problem _is_ so that I know that I'm 
really fixing it.)

I guess this could be a CCSID issue, but not because of the 819 vs 37 
thing.... because Windows doesn't have the notion of a CCSID.  It 
understands the notion of a codepage, but doesn't assign a separate one to 
each file.  It's the application's job to know what's in the files, rather 
than the OS -- there's just a codepage for the user interface, not for 
files (at least, that's been my experience...  I'm not much of a Windows 
person, so someone who's a little more Windows-oriented could certainly 
know something that I don't...)

I'd try removing the TOCCSID(*PCASCII) from your CPY command.  It doesn't 
really make sense anyway, since the files are already on a PC and are 
already in ASCII.  Just do a binary copy.

If that doesn't work, all I can suggest is writing your own copy utility 
that provides better error messages -- I'm half-kidding.  It seems 
ludicrous to suggest this, but then, it's probably what I'd do in your 
situation.

---
Scott Klement  http://www.scottklement.com

On Tue, 3 Jan 2006, Jeff Crosby wrote:

> I used this CPY command to test whether I can automate this:
>
> CPY OBJ('/Invoices/2006-01') TODIR('/qntc/ReportSvr/Shared Files/Invoices')
> TOCCSID(*PCASCII) SUBTREE(*ALL)
>
> The result was:
>
> 143 objects copied.  305 objects failed.
>
> All the failed objects had a .pdf extension.  All the copied objects were
> either a directory or some extension other than .pdf.  The joblog has, for
> each failed object:
>
> Message ID . . :   CPFA0AD     Severity . . :   40
> Message type . :   Diagnostic
> Date sent  . . :   01/03/06    Time sent  . :   12:36:12
>
> Message . . . . :   Function not supported by file system.
> Cause . . . . . :   An attempt was made to use a function which was not
>  supported by the file system for path /qntc/ReportSvr/Shared
>  Files/Invoices/2006-01/03/9116700.PDF.  The path selected may not be valid
>  for the function, or it may not be in the same file system.
> Recovery  . . . :   Check the path name for accuracy.  You may need to use
>  another path for the operation.  Check the job log for possible additional
>  messages.
>
> The target (ReportSvr) is a Win XP Pro machine.  Every month I have been
> doing this in Win explorer on that PC via drag and drop and wanted to
> automate it.  The .pdf files copy just fine via that method.  I don't
> understand the 'function not supported'.  Could it be an authority thing?  I
> have the same user id and password on the i5 and that PC.
>
> Ah!  I just checked and the CCSID on the .pdf files is 37 and on the other
> files is 819.  Suppose that's it?  Then how does my drag and drop work?