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


  1.  Home
  2. RPG400-L
  3. June 2014

Re: Weirdness with EXTDESC, EXTFILE, EXTMBR, and a CPF5152

On 16-Jun-2014 15:31 -0500, James H. H. Lampert wrote:
<<SNIP>> Here's a simplified source:
FMIMEBODY O E DISK USROPN EXTDESC('MERCURY/QCLSRC')
F EXTFILE('QTEMP/MIMEBODY')
F EXTMBR('DFT')
D CRTMIMEBODY S 32A INZ('CRTSRCPF QTEMP/MIMEBODY +
D MBR(DFT)')
D CHGMIMEBODY S 35A INZ('CHGPF QTEMP/MIMEBODY +
D LVLCHK(*YES)')
C CALL 'QCMDEXC'
C PARM CRTMIMEBODY
C PARM 32 CMDLEN 15 5
C CALL 'QCMDEXC'
C PARM CHGMIMEBODY
C PARM 35 CMDLEN 15 5
C OPEN MIMEBODY
C EVAL SRCDTA = 'Scheduled Activity Information'
C WRITE QCLSRC
C SETON LR

It seems that in the real program, a WRITE QCLSRC will, for no
apparent reason, and after several successful WRITE QCLSRC statements
were already executed (otherwise it wouldn't have gotten that far),
it will throw a CPF5152. <<SNIP>>

For an externally described file, make the above inline changes to the RPG source, to expose the origin for the condition at open-time, instead of the condition being diagnosed only later [if ever].


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.