× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I tried to do this, but i get a message

File QSYSINC/QRPGLESRC does not have output file capability.

What do i need to do  to give output file capability to the file in
the QSYSINC library.

Thanks

Krish


On Mon, 22 Nov 2004 20:54:56 -0600, Bob Cozzi <cozzi@xxxxxxxxx> wrote:
> Yes I've had that problem too.
> You go into the include member and delete those fields and then you're fine.
> But you DO NOT physically delete them. Do this instead:
>       /IF DEFINED(*V5R2M0)
>      DQUSICCSW              477    492P 0
>       /ENDIF
> 
> IBM should have done this; it is a crime that they don't know how to use
> their very own system. So it is up to you to do what's best.
> -Bob
> 
> 
> 
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Krish Thirumalai
> Sent: Monday, November 22, 2004 11:01 AM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: 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.
> 
> Thanks
> 
> Krish
> --
> 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.
> 
> --
> 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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.