|
On Feb 5, 2020, at 4:13 PM, Paul Nicolay <paul.nicolay@xxxxxxxxxx> wrote:
Hi,
No idea if this question/issue fits in the RPG mailing list but I doubt a VisualAge RPG one still exists.
The issue is that on a project we still use IBM VisualAge RPG but after we moved to a new system the compiles fail on missing fields which is caused by improper importing the copy members. These show up on the compile listing as follows;
34 D/COPY *REMOTE *LIBL/QVRPGSKCOP,ALPROGDS 000033
*--------------------------------------------------------------------------------------------*
* RPG member name . . . . . : ALPROGDS * 2
* External name . . . . . . : *LIBL/QVRPGSKCOP(ALPROGDS) * 2
*--------------------------------------------------------------------------------------------*
35+ * * Program data-structure * D ProgDs SDS D PDCompName *P ?
As you notice the compiler can read the remote copy member but has everything on a single line as it doesn't understand the carriage returns ? So far I have no clue what is causing this, just hoping someone has experienced the same issue many years ago :-)
Manually inserting the copy member in the source itself removes the compile errors which proves that it doesn't import the copy member despite I can see it.
Any tips are welcome.
Thanks,
Paul
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.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.