RE: QSYSINC/QUSLFLD usage in RPG in V5R2

You could, of course, also physically copy the source into your program
(instead of doing a /copy).  While I really like /copy for prototypes
and constants, I don't frequently put Datastructures into /copy
members.  

I suppose I'll get beat up because this isn't very modular-ish, but I
like to have the actual definitions right in my source code. Had this
been the case, the program would not have ceased functioning... Of
course, I also only have one copy of this DS because I encapsulated the
API functionality into a single service program.

http://www.rpgnext.com/docs/rnbquslfld/

Joel
http://www.rpgnext.com

On Tue, 2004-11-23 at 14:55, John Brandt Sr. wrote:
> How about a different option. Create your own libraries like I did to keep
> the older versions intact.
> 
> /if defined( *V4R5M0 )
> D/COPY MSYSV4R5/QRPGLESRC,QUSLFLD
> /endif
> /if defined( *V5R1M0 )
> D/COPY MSYSV5R1/QRPGLESRC,QUSLFLD
> /endif/if defined( *V5R2M0 )
> D/COPY QSYSINC/QRPGLESRC,QUSLFLD
> /endif
> 
> 
> John Brandt 
> iStudio400.com 
> (903) 523-0708 
> Home of iS/ODBC - MSSQL access from iSeries and RPG. 
> 
> 
> 
> 
> -----Original Message-----
> From: Steve Richter [mailto:stephenrichter@xxxxxxxxx]
> Sent: Tuesday, November 23, 2004 8:46 AM
> To: RPG programming on the AS400 / iSeries
> Subject: Re: QSYSINC/QUSLFLD usage in RPG in V5R2
> 
> 
> > 
> > We just recently upgraded our OS to V5R2 and we had a program that was
> > using the QUSLFLD
> > 
> > D/COPY QSYSINC/QRPGLESRC,QUSLFLD
> > 
> > We have always compiled to a previous release, when creating the
> > program. We are now seeing a compile error for around 8 fields that
> > are in the copy book. One of the errors is with this field below.
> > 
> > QUSICCSW              477    492P 0
> >                                            IC Curr Start With
> > 
> > RNF0503 - Length of numeric item QUSICCSW00 is greater than 30
> > digits; defaults to 30.
> > 
> > The problem is that IBM decided to add 31 byte numeric fields to the
> > end of the record formats QUSL0100, and now we cannot get these
> > programs to compile after we introduced a small change, unless we
> > decide to set the targer compile release to V5R2.
> > 
> > Has anyone encountered this problem and how has it been handled other
> > than deciding to not use QSYSINC any more.
> 
> what about adding some conditional compile stmts to the QUSLFLD source
> member?
>  
>  /if defined( *V5R2M0 )
>  QUSICCSW              477    492P 0
>  /endif
> 
> -Steve
> --
> 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.
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.792 / Virus Database: 536 - Release Date: 11/9/04
>  
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.799 / Virus Database: 543 - Release Date: 11/19/04
>  
> --
> 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.