|
There is a problem with qualified data structures in RPG-IV on releases prior to V5R4. The SQL-RPG interpreter on those releases doesn't understand some of the nuances of RPG-IV, like free-format code and qualified data structures. If you're using V5R3 or earlier you might have do it with prefixed data structures. ----- Original Message ----- From: Ken Sims To: rpg400-l@xxxxxxxxxxxx Sent: Thursday, August 24, 2006 11:45 PM Subject: Re: RPG III and DS Hi Wes - >I'm converting a RPG program to SQLRPG due to OPNQRY file performance. In >the program the same file is opened three times. The first two file are >logical and the third is a join file. Based on the PF, there is a DS (DS1). >I tried to create an extrenally defined DS(DS2) based on the logical file >but kept getting an error: > > * QRG4072 Severity: 30 Number: 140 > Message . . . . : Subfield-Name specified already defined as > Subfield-Name. Specification line ignored. > > >then I tried to create the second DS based on the first, but I'm still >getting the same error. My question is: is it possible to have a one DS as a >subset of another DS? The same field name cannot appear in more than one data structure. In RPG IV you could use prefixes or qualified data structures though. I don't know how well they would work with SQL though, since I don't use SQL in RPG. Ken http://www.kensims.net/ Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind. -- 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 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.