|
Brad, To make a long story short, I'm writing an RPG subprocedure in a service program to retrieve a message from a message file using the QMHRTVM API. I used your SCNMSGF article in News/400 from Feb/1998 as a guide. The message text always has an extra character in front of what should be the actual message text. A search of the midrange archives found the LSTFFD thread where you spoke about a change in the API (which was actually a PTF for V4R2 and prior) specifically addressing the single byte offset. I downloaded your SCNMSGF (for V4R3 and later) utility and tried it. It was correct, so you obviously got it changed so it works right. However, there is no source code so I don't know what you changed, and I can't determine the problem based on the Infocenter description of the API. If I change this statement: Eval RtnText = %Subst(MsgText:1:LMsgR) to this: Eval RtnText = %Subst(MsgText:2:LMsgR) it works. But that's 'cheating'. <g> What exactly did you change? Thanks. -- -Jeff The opinions expressed are my own and not necessarily the opinion of my company. Unless I say so.
As an Amazon Associate we earn from qualifying purchases.
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.