|
Jim, I stand corrected. During our transition phase we were calling RPG400 and CLP programs from RPGII without problems. I've always heard the "a program is a program" mantra for years, but never tried going the other way. But I have another solution that may or may not fit this situation. AKAIK (and you know how far that got me last time <g>) The difference between an RPGII program and a RPG400 program with program described files is minimal unless it's an interactive program, but even then it's not insurmountable. In most cases you remove the core size to execute and the program name. If you use /COPY members, like we do, they will be in source PF QS36SRC in whatever library name you specified in the /COPY entry. Just copy them to a source PF that is the same name as the old library name. Jim Franz wrote: > > James Kilgore wrote: AFAIK, a CALL is a CALL and a program is a program > tried it and failed rpg9971 RPG program NO026 must run from a S/36 > environment job.
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.