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



The output of HPT is usually some flavor of ASCII. Maybe that's why it looks like "gibberish" to you?

Possibly you just need to mark the IFS file with a proper CCSID after it's done, and tools like DSPF or EDTF will view it properly?

Regarding your change... are you certain that the data is null-terminated? In my experience with the HPT API, it normally is not, it's just raw binary data. You should not be using %STR here... unless I'm misunderstanding.


On 4/20/2014 6:00 PM, Jack Tucky wrote:
I downloaded a program called Spl2Stmf that uses the spool file API's to
read a spool file and write an IFS file.

I'm trying to modify so I can just read the spool file in RPG to look for
some keywords.

I changed this line which wrote the STMF:

EVAL bytesw = write(fd : xbufspc_p : hptxbuflena)
To this:
String = %str(xbufspc_p : hptxbuflena);

But I only see gibberish in the String. I'm guessing that the write command
in the original example did some conversion when it wrote to the IFS.

Any ideas what I'm doing wrong? Maybe I need to strip out the HPT
completely as I'm just reading the spool file in the program? The original
download save file link is broken however.

http://homepage1.nifty.com/uzaemon/#download

Now that I think more this is overkill and I just need something to open and
read the spool file.

\

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.