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



On Thu, Jun 18, 2009 at 4:04 PM, Charles Wilt <charles.wilt@xxxxxxxxx>wrote:

Here's one issue that may byte you with the hash....

When you have the data on the i, you're dealing with EBCDIC, on the Windows
server the data will be ASCII.

You'd need to convert the data to ASCII on the i before calculating the
hash
if you expect it to match the has calculated on Windows.

Having said that, you might for instance consider a program that runs in
PASE to produce the hash. Since PASE is ASCII, I believe the system will
translate the data for you automatically.


Thanks Charles. I did a small test using the same string on the i as well
as in a text file in Windows, and got the same MD5 value. I suspect the
service program might already be converting the input data:
// Get conversion table for 819 from 37
Qtqcvrt(Ccsid1:St1:StartMap:L1:Ccsid2:St2:Gccasn:L2:To819:L3:L4:Fb);
// Change message to ccsid 819 (ascii).
Convert(Inputdata:%Addr(To819):InputLength);
This is from the link I provided in my original post.

Unfortunately, I just tried it on a larger file, one of the smallest I'll
need to be able to test, and got RNQ0425:
The length requested for storage allocation is out of range.

I guess I need to figure out if I can allocate more than 16776704 bytes.
FWIW, we're running on V5R4.

- Dan

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.