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


  1.  Home
  2. RPG400-L
  3. April 2011

Varying(4) bug ?

Hi,



I'm introducing Varying(4) into my programs as I need to handle more data, but I'm experiencing something strange.



I have a procedure that accepts a Varying(4) which is defined with the Const keyword. If I now call this procedure, passing a normal Varying... the first two bytes of the string itself are dumped in position 3 and 4 of the Varying(4) field ? See dump data below, ie. the "He" or x'C885' gets into byte 3 and 4 ?



Shouldn't "Const" not solve this issue ?



Example:



H DftActGrp(*No) ActGrp(*Caller)

DMyProc PR 100 Varying(4)
D Var4 100 Varying(4) Const

Ds S 100 Varying

/free
s = 'Hello world.';
s = MyProc(s);

*INLR = *On;
Return;
/end-free
**********************************
* MyProc *
**********************************
PMyProc B Export

DMyProc PI 100 Varying(4)

D Var4 100 Varying(4) Const
**********************************
* Main *
**********************************
/free

// Dump 000CC885 93939640 A6969993 844B0000 - ..Hello world...
Return Var4;
/end-free
P E



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.