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



If the CL can't or it is undesirable to be changed, then the next best might be to define the RPG parm field a zoned. Assuming the lengths match and you can guarantee that there will only be digits 0-9 passed, that should work just fine.

-mark

On 1/19/2021 10:06 AM, Joep Beckeringh via RPG400-L wrote:
Simple: make sure the data types match.

When you pass parameters from CL to RPG, the RPG program receives pointers to storage that is defined by the CL program. If the CL defines character variables and the RPG interprets them as numeric (what kind of numeric? Zoned, packed, integer, float?) the content obviously looks like junk to the RPG program.

Joep Beckeringh


Op 18-1-2021 om 14:31 schreef techie21 IT:
Hi,

I have two fields let's say fld1,fld2(date field) and having their data
types in CL program as Character but in RPG program they are as numeric so
the problem is happening when we are passing these parameters from CL to
RPG program for example if we pass fld2(having date value in it) to a RPG
program then up on debug it's known that it captures some junk value and
same happens for fld1( which is character in CL program) and when same is
passed in RPG then it gets some junk value in it i have seen these junk
values while debugging both the programs they are passed well from CL but
the moment they come in RPG becomes junk values.how can we prevent
this from happening?

Any suggestions please?


Thanks..

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.