|
This is a FAQ. Basically, you have to pass in all parameter positions or
you'll get junk in the parameters.
Matt
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Glenn Gundermann
Sent: Monday, June 11, 2007 11:21 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Problems with parameter passing
It's Monday morning and the brain hasn't warmed up yet. Any help would
be
appreciated.
Here is a prototype I've done:
D CAFWTBLEML pr
D TrRptId 10a const
D TrRptDes 50a const
D TrDlyMth 1a const
D TrFile 1000a const
If I call this from the command line using:
===> call cafwtbleml parm('A' 'B' 'C' '/home/subdirectory/long file
name
goes here.csv')
I get some funny results for 2 of the parameters:
1st parameter: fine
2nd parameter: %len(trimr(TrRptDes) = 34, value of TRRPTDES = 'B (32
blanks) C (16 blanks) '
3rd parameter: fine
4th parameter: %len(trimr(TrFile) = 689, value of TrFile = value passed
plus a lot of garbage
Tks,
Glenn Gundermann
ggundermann@xxxxxx
(647) 272-3295
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.