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



The behaviour is as expected - but there is certainly no need to pass a second parameter or indeed to use Op descriptors.

Not sure what you did with varying but that should give you the answer you seek.

In the called routine define the string as 32000 varying and add the keyword CONST instead of varsize.

By doing that you enable the compiler to copy the string and in doing so it will set the length of the varying field received by the caller to the length of the original field.

If you always want the string trimmed then you could add the Trim option to the proto and that will take care of that for you.

What you lose with Const of course is the ability to modify the string but you don’t mention that as a requirement.


On Oct 28, 2015, at 11:49 AM, Dan <dan27649@xxxxxxxxx> wrote:

I've tried a couple of variations on the code snippet below, but this is
the only one that compiled. In the example below, TEXT50 is a 50-char
length variable. Once inside the ExtractSpecs proc, LongString shows the
value of TEXT50 in the first 50 columns, but is followed by "junk".

My (apparently incorrect) understanding of Options(*Varsize) is that the
ExtractSpecs proc would "see" only the value in LongString up to the length
of the variable passed to it. The compile fails if Options(*Varsize) is
not specified. Ditto if I used the VARYING keyword.

My kludgy, hopefully temporary, workaround is to capture the length of the
first parameter and pass it as the second parameter.

Ideas / advice / specific RTFM references appreciated!

d ExtractSpecs pr
d LongString 32000a Options( *VarSize )
...
ExtractSpecs( TEXT50 ) ;
...
p ExtractSpecs b
d ExtractSpecs pi
d LongString 32000a Options( *VarSize )

- Dan
--
This is the RPG programming on the IBM i (AS/400 and 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.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com


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.