×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I'm creating an XML file in \TMP on the IFS.
I have DAZzle running on a PC to print endicia postage from the XML files.
The AS/400 crashed yesterday with a few critical storage messages saying the system
was full. The system has been running for years at 74%. I found hundreds of messages
relating to QZLSFILE which handles the Client Access file transfers. DAZzle is a new
application. I'm thinking DAZzle has been trying to get the XML files and has been
erroring out. When I try to view the XML files on the 400 the viewer show them fine
saying they are in EBCDIC. I have the system value QCCSID = 37.
I put a file called CWBTFR.INI in C:\Windows
[Client Access Data Transfer]
ForceTranslation=1;
And re-booted the PC trying to force the translation to ASCII.
When I copy the XML file from \TMP to the PC and look at it with an editor it's all
garbage.
It looks to me like DAZzle is getting the file in EBCDIC and causing an error in Client
Access which creates an joblog and fills up the system with logs.
If I put the XML files in a different folder on the IFS will it convert to ASCII? If so
which folder?
The PC is running Win7
AS/400 is v4r4
Client Access is v5r1
One example of hundreds of joblogs is here
http://pastebin.com/MtMJTE4H
Thanks,
Gary Kuznitz
midrange.com
