|
>from: MWalter@xxxxxxxxxxxxxxx >subject: Replacing *entry plist >Checked the archives on this and can't believe that it hasn't come up >before. But currently when calling an RPG module that contains cycle code >from a CLLE module, and needing to pass parameters to the RPG, I still use >*entry plist. Since upgrading to V5R2, I've been trying to use Free Form >RPG. Realizing that there is no free form version of *entry plist, is there >a way to create another type of parameter interface that CLLE could use? Hi Mark I did this once, lemme see if I remember the steps... Procedure Interfaces are supposed to be the new version of the PLIST. You should be able to bracket the RPG code with Procedure specs, add PI and PR definitions in place of the PLIST, re-compile the RPG code as a module, and bind that module into a service program (well you don't have to do the service program, but I like it). You'll have to change your CLLE to use the CALLPRC command where it now does a CALL, create a CLLE module from the source, and do a CRTPGM with the CLLE module, referencing the new service program. -Doc __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.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.