× 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.



In V4R4 the following will not compile:

D  array2                      S                      dim(%elem(array1))
like(array1)
D  array1                      S            7P  2  dim(12)

Prior to V5R1, the argument of a built in function used on the DIM, OCCURS,
OVERLAY, or PERRCD keywords in D-specs must have been previously defined in
the source.  That is the first time we have had serial dependence of
definition in RPG.  That restriction has been eliminated as of V5R1.

Charles L.Massoglia, President
Massoglia Technical Consulting, Inc.
cmassoglia@voyager.net
In MI 517-676-9700 or in NC 919-363-9395


----- Original Message -----
From: "J Michael Smith" <JMichael.Smith@arch.com>
To: <rpg400-l@midrange.com>
Sent: Thursday, 07 March, 2002 18:03
Subject: DIM question (Was MOVE/MOVEL and %Scan)


> Barbara,
>
> Could you provide an example of "The parameter DIM, OCCURS and PERRCD
> keywords no longer needs to be previous defined."
>
> Thanks
>
> Michael Smith
>
> -----Original Message-----
> From: bmorris@ca.ibm.com [mailto:bmorris@ca.ibm.com]
> Sent: March 07, 2002 02:17 PM
> To: rpg400-l@midrange.com
> Subject: Re: MOVE/MOVEL and %Scan
>
>
>
> >Date: Thu, 07 Mar 2002 03:53:52 -0500
> >From: "Nicolay, Paul" <paul_nicolay@merck.com>
> >
> >I guess I once tested MOVEL on a VARYING field, and got the result that
it
> >also overwrote the first two bytes containing the length of the VARYING
> >field ?  Has this ever been the case, or is my memory really failing ?
> > ...
>
> I don't recall that ever being the case, but my memory may be failing.
> Maybe you're recalling a problem with the debugger - it didn't handle
> varying fields very well, at first.
>
> >I also encountered another issue that seems to be running fine now ?  In
> the
> >past when I was doing a %Scan and the search argument was bigger than the
> >actual VARYING string, the program crashed.  If I now try this...
> everything
> >goes fine (and it returns 0... as it should be in my opinion).  Again, am
> I
> >getting old ?
>
> Paul, you remember correctly.  This is one of the changes listed in the
> "What's new in this release" section of the V5R1 ILE RPG Programmer's
> Guide.
> Point 4 in Other enhancements: "The search string in a %SCAN operation
> can now be longer than string being searched. (The string will not be
> found, but this will no longer generate an error condition.)"  It was
> your question about this behaviour, maybe on this mailing list, that
> prompted the change.
>
>
http://publib.boulder.ibm.com/pubs/html/as400/v5r1/ic2924/books/c092507307.h
> tm#HDRRELV5R1
>
> Barbara Morris
>
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com
> 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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com
> 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.