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



Folks:

A bit more than a year ago I reported problems using the CPYTOSTMF command
running on a machine in the UK
(http://archive.midrange.com/midrange-l/200109/msg01241.html).

Well, I'm back to investigating the problem ... and I've seen some odd
behaviors, and I was wondering if anyone has ever seen this before.

To summarize the situation ... I've got a CL program running on a V5R1
system.  The CL program copies a source physical file member into a stream
file.  It then invokes a Java program that reads the stream file and
processes the records.  For some reason, when the source pf contains a
dollar sign "$", it gets translated incorrectly.

When we use STMFCODPAG(437), the $ gets translated into a single quote "'",
if we use STMFCODPAG(*PCASCII), it gets translated into a cents symbol "¢"
(no jokes about the system making commentary on the financial situation) ...
I don't know what the result would be if we used STMFCODPAG(*STDASCII), but
I've requested that this test be run also.

I absolutely didn't expect the incorrect translation when we used *PCASCII.
The fact that a dollar sign is being translated into a cents sign makes me
suspicious.

Anyone know what might be causing this?  Is it possible that the standard
translation table on the 400 was changed?  Anyone know how you can TELL if
the standard translation tables were changed?

Thanks!

david






As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.