|
At 07:13 AM 8/16/2001, you wrote: <snip> >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. <snip> this is what I have used in my scan message application, along with notes on the original IBM Apar: D Offset S Like(QMHOMRTN) RTVM0300 offsets * Set offset to correct values as a circumvention to OS/400 API bug for * versions prior to V4R3. Ref APAR# SA77067. If Offset of Default reply * is 105, the following offsets are off by 1 (1 to many) * Offset of default reply * Offset of message * Offset of message help * Offset of substitution variable formats * To correct for versions prior to V4R3, subtract 1 from the offset returned * by this API for format RTVM0300. C If QMHORT = 105 Deflt reply offset C Eval Offset = QMHOMRTN C Else C Eval Offset = QMHOMRTN + 1 C Endif C Eval SourceRcd = %Subst(RTVM0300 : C Offset : Offset to Msg data C QMHLMRTN04 ) Length of Msg data Hope this helps. Apologies if this is sent twice. I have been having trouble sending to the lists and am changing some of my email settings. Dave Murvin DRM Enterprises, Inc. davem@drme.com
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.