|
Yes, you need to prototype the second module as a procedure. The CALL opcode will only access a program object, not a service program (which contains procedure modules) nor a bound in module. As for the CALLB, can't tell from the info you supplied what is going on there. The CALLP should be using a literal to identify the program, if you are using a variable to id the procedure, then that variable must be a procedure pointer type that has been set to the address of the desired procedure. In other words, there are no "dynamic" procedure calls that are not pointer based. -----Original Message----- From: JFinney@omnia.co.za <JFinney@omnia.co.za> To: RPG400-L@midrange.com <RPG400-L@midrange.com> Date: Monday, November 08, 1999 10:04 AM Subject: ILE Question >I have two modules. The first performs screen validations & then calls the >second module with a CALL opcode. The second module performs printing. Now >the two modules are bound into a program using CRTPGM cl command. A service >program containing two modules (one of which contains mupltiple procs >[NOMAIN] ) is also bound into the pgm at the time of CRTPGM. The problem >I'm sitting with is the point at which the first pgm calls the second, an >error occurs. It seems as if a program object is being sought. I tried >changing the CALL to a CALLB but then received a compilation error >(something about procedure pointer call). > >What am I doing wrong here? Do I have to prototype/create a procedure form >the second module? Is there a correct way of doing what I'm currently >trying to achieve? > +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.