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



Rick,

I continued today my tests andf found out the real problem:

If in a key list a character field is positioned before a numeric field, the
compiler fails. Otherwise it works well.

Here my example:
 This version fails: 
 A          R TESTR                 
 A            FLDCHAR       10A     
 A            FLDNUM         8S 0   
 A          K FLDCHAR                
 A          K FLDNUM               

 This version works: 
 A          R TESTR                 
 A            FLDCHAR       10A     
 A            FLDNUM         8S 0   
 A          K FLDNUM                
 A          K FLDCHAR      

This is the test program:

 FTEST      IF   E           K Disk                          
 D Main            PR                  ExtPgm('TESTE')       
 D k$T             DS                  LikeRec(TESTR:*key)   
 D Main            PI                                        
  /free                                                      
   k$T.FLDCHAR = '12345';                                    
   k$T.FLDNUM  = 20030217;                                   
   Chain %kds(k$T) TESTR;                                    
   If %found(TEST) or not %found(TEST);                      
      *inlr    = *on;                                        
      Return;                                                
   EndIf;                                                    
  /end-free                                                  

I pass it now as service request to IBM.

Regards,

Werner Noll


-----Ursprüngliche Nachricht-----
Von: Chevalier, Rick [mailto:Rick.Chevalier@xxxxxxxxxxxxxxx]
Gesendet: Freitag, 14. Februar 2003 18:09
An: 'RPG programming on the AS400 / iSeries'
Betreff: RE: RPG compiler error


Werner,

I checked with our operations group and the PTF is loaded but not applied
yet.  They will try to IPL this weekend.

I wonder if it is related somehow to the file.  I used it last week in
another program (also free form) with no issues.  I compared code, and
except for the file name it's identical.

Rick

-----Original Message-----
From: Werner Noll [mailto:werner.noll@xxxxxxxxx]
Sent: Friday, February 14, 2003 11:03 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: AW: RPG compiler error

Rick,

it obviously occurs, if you use 2 files with the same record format, where
one of them is renamed in the file specs.
I keep you informed what will happen after installing the new kum PTF.

Regards,

Werner Noll

-----Ursprüngliche Nachricht-----
Von: Chevalier, Rick [mailto:Rick.Chevalier@xxxxxxxxxxxxxxx]
Gesendet: Freitag, 14. Februar 2003 17:37
An: 'RPG programming on the AS400 / iSeries'
Betreff: RE: RPG compiler error


Werner,

That's it.  I figured it out about the time your message arrived.
Interestingly, this is not the first time I've used %KDS.  This is the first
one not to work though.

Thanks,

Rick

-----Original Message-----
From: Werner Noll [mailto:werner.noll@xxxxxxxxx]
Sent: Friday, February 14, 2003 10:20 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: AW: RPG compiler error

Rick,

I got the same problem when I compile a program in free-format and when I
use for file access the new %KDS function.
I called IBM's service and they have send me the latest kum PTF (C2344520).
I'll install it this weekend.
The actual error is shown in the joblog:
MCH3601    Escape                  40   14.02.03  17:01:08,074224  QRN4MAIN
QRPGLE      *STMT    QRN4MAIN    QRPGLE  
                                     From module . . . . . . . . :
GRPFGCXS                                            
                                     From procedure  . . . . . . :
store_operand                                       
                                     Statement . . . . . . . . . :   15

                                     To module . . . . . . . . . :
GRPFGCXS                                            
                                     To procedure  . . . . . . . :
store_operand                                       
                                     Statement . . . . . . . . . :   15

                                     Message . . . . :   Zeiger für
angegebene Position nicht gesetzt.                   
                                     Ursache  . . . . :   Es wurde ein
Zeiger, entweder direkt oder als ein              
                                       Basiszeiger verwendet, für den keine
Adresse festgelegt worden war.               

If the kum PTF does not fix it, I already ordered additional PTFs for APAR
SE08901. They will be issued about next week.

Regards,
Werner Noll
 

-----Ursprüngliche Nachricht-----
Von: Chevalier, Rick [mailto:Rick.Chevalier@xxxxxxxxxxxxxxx]
Gesendet: Freitag, 14. Februar 2003 16:36
An: RPG400 Mailing List (E-mail)
Betreff: RPG compiler error


Has anyone encountered this error compiling an ILE program?

* * * * *   E N D   O F   A D D I T I O N A L   D I A G N O S T I C   M E S
S A G E S   * * * * *
Compilation stopped. Internal failure occurred. Error code is  1.


There are no other errors in the program.  I don't know where to start with
this one but I'm guessing it's something in the way I put the code together.
I haven't been able to find it yet though.  Any suggestions?

I can send the code if anyone wants to see it.  It's rather long so I didn't
want to include it here.

Rick Chevalier
Sr. Programmer Analyst

(817) 525-7178
rick.chevalier@xxxxxxxxxxxxxxx

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.