×
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.
It compiles because you're using the CONST keyword.
My understanding is that this keyword automagically casts the passed
parameter to the correct type and length.
HTH,
Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we. Futile is resistance, assimilated will you be.
-----
David FOXWELL <David.FOXWELL@xxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
29/11/2007 10:45
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
To
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
cc
I wanted to know more about the D spec OPTIONS ( *VARSIZE )
So I coded this simple example to pass a shorter length parameter to my
procedure than expected by that procedure.
I haven't achtually put the *VARSIZE in yet. My question is, why does my
pgm compile as I am passing a shorter length parameter?
What difference will it make if I add *VARSIZE ?
D gPr1 S 1
D gPr2 S 50
D ChgPr PR
D P1 50 CONST
D P2 50
/FREE
gPr1 = 'S';
ChgPr ( gPr1 : gPr2 );
/END-FREE
P chgPr B
D PI
D APrIn 50 CONST
D APrOut 50
/FREE
APrOut = APrIn;
/END-FREE
P chgPr E
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.
midrange.com
