|
In the same sort of situation, I have taken big if-endif blocks and made them subroutines. Use Ctrl-M, cut,and paste, to make sure you get paired blocks. This solution results in a mainline that is small enough to handle. Additionally the subroutines become easier to maintain and debug. --------------------------------- Booth Martin http://www.martinvt.com --------------------------------- -------Original Message------- From: Websphere Development Studio Client for iSeries Date: 08/20/04 15:34:32 To: Websphere Development Studio Client for iSeries Subject: RE: [WDSCI-L] RNF5177 - ENDyy operation missing for .... I wonder why complier is able to tell me the block of code that has missing end statement but wdsc is not able to do the same thing. I'm changing a very big program, it is really hard to spot the missing end statement with indent. -----Original Message----- From: wdsci-l-bounces+lim.hock-chai=arch.com@xxxxxxxxxxxx [mailto:wdsci-l-bounces+lim.hock-chai=arch.com@xxxxxxxxxxxx]On Behalf Of Paul Weyer That is normal. The verifier cannot identify where the ENDyy opcode is missing, just that there is a mismatch between the number of scope-terminated opcodes and their associated scope terminator. The way to find out where the missing ENDyy scope terminator is to be inserted is by performing an indented view of the source. Paul Weyer _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-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.