Re: Client Access file transfer error

[Simon Coulter <shc@xxxxxxxxxxxxxxxxx>]

On 01/08/2010, at 2:23 PM, Gary Kuznitz wrote:

> I tried option 2 even though that option isn't listed and it deleted  
> the file.  Option 5 is
> Next Level.  I'm guessing these options are different on a later  
> version of the OS.

You must on a pre-V5 (i.e. ancient) release. Options don't have to be  
visible to be functional. Notice the ellipses (...) after the options.  
F23 will show you the additional options. I don't recall 2 being  
remove--it might have been move in which case the entry is not deleted  
but will be found in your current directory.

> I think you are correct.  I don't know why I was thinking it was CA  
> file transfer.
>
> So the problem is how to get NetServer to translate into ASCII.

NetServer is a stupid piece of software. Never mind the crap  
implementation of SMB/CIFS but it has to be told what to do. By  
default it won't translate anything. You need to tell it to convert  
the data for the XML files. You do that by telling it to convert based  
on file extension. Support for this was added at VRM440 but I don't  
recall if it made it into Navigator at that release. I found old e- 
mail from you in the trash that suggests your host is on 440 so you  
may be in luck.

You have two choices:

	1) Use CPY to convert the XML files into code page 819 (or a similar  
suitable code page). Note that you'll need to use code page values  
because CCSID support wasn't added to stream files until VRM510.

or
	2) Tell NetServer to convert all files in the XML share with whatever  
extension those file have. Go into File Systems->File Shares then  
right click on the XML share and open Properties. You should see a  
window with two tabs: General and Text Conversion. Then check "Allow  
text conversion", choose a conversion type, code page, and whether all  
files or only specific extensions should be converted. Save and try to  
read the file again. You may need to end and restart NetServer to have  
the conversion take effect.

If you take option 1) then you might also want to ensure future XML  
files are generated in the appropriate ASCII code page instead of  
EBCDIC.


Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         OS/400, i5/OS Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 2 6657 8251   Mobile: +61 0411 091 400        /"\
   Fax:   +61 2 6657 8251                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------