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



If I replace the prefix('PT.') with prefix('PT_') it does compile, but the data record isn't read into the qualified 'PT' datastructure.

Tom

Carel Teijgeler said the following on 1/25/2005 3:04 PM:
Tom,

Is this not a name checking error? Theprefix contains a dot. If you replace it 
with an underscore, will it compile then?

Regards,
Carel Teijgeler

*********** REPLY SEPARATOR  ***********

On 25-1-05 at 11:40 Tom Hightower wrote:


(OS/400 V5R2)

Here's the full source of a failing test program:

fPATMST    if   e           k disk    prefix('PT.')
dPT             e ds                  extname(patmst) qualified

/free
 if PT.PAGE > 65;
   *inlr = *inlr;
 endif;
 *inlr = *on;
/end-free

The compile is failing at this point:

   65=IPTREC
       *--------------------------------------------------------
       * Data structure . . . . . . :  PT
       * External format  . . . . . :  PTREC : FILES/PATMST
       * Format text  . . . . . . . :  PATIENT MASTER
       *--------------------------------------------------------
<snipped several fields>
   74=I                             P   48   49 0PT.PAGE

(there are other fields after this one defined in the file, but the compile stops at this field)


This is the error message on the compile listing:

Compilation stopped. Internal failure occurred. Error code is 1.


Am I missing a PTF?

Tom


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.