DSCOPY (or NFT) with HFS is not yet supported on 5.0. The current plan is for NFT to not support transfers into hierarchical space. There is already an SR to include support for that. That's the reason you're getting the errors doing a dscopy involving HFS names. Hope that helps! yuhsin -- my opinions do not reflect those of hp's response center ______________________________ Reply Separator _________________________________ Subject: Re: DSCOPY: Target file cannot reside in a heirarchial Author: Non-HP-HP3000-L ([log in to unmask]) at HP-Singapore,mimegw30 Date: 8/2/96 9:51 PM ---------- From: John Korb Sent: Friday, August 02, 1996 9:16 AM To: Multiple recipients of list HP3000-L Subject: DSCOPY: Target file cannot reside in a heirarchial directory(nft /3000 err 114) OK, there MUST be a good reason for this restriction, as someone went to all the trouble to create a special error message for it. So what's the reason? None that I can think of. Here's an example. FEPC [8]: dscopy phlpsds.temp;/COMM/TEMP/test.html,cda9[manager/.comm/];rep Source file: PHLPSDS.TEMP.COMM Target file: /COMM/TEMP/test.html TARGET FILE CANNOT RESIDE IN A HEIRARCHIAL DIRECTORY (NFT/3000 ERR 114) UNABLE TO CREATE OR OPEN TARGET FILE. (NS/NFTERR 33) END OF SUBSYSTEM FEPC [9]: If FTP were as reliable as DSCOPY, I'd use FTP, but FTP on the WAN is a "cross your fingers and pray" situation. John, I've never had any luck dealing with HFS and DSCOPY - I've always used FTP. As a matter of fact, we do more FTP now than DSCOPY over the WAN...and not had any problems unless the remote machine was down...which I think, has happened once in the last eight months... When you say "cross your fingers and pray situation" - what's happening? Joe Geiser