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



assuming you are doing CALL MYPROG ('/home' '3') from the command line...

You are running into the well known 32-character default length issue of
the command interpreter.

Basically, the system doesn't know '/home' should be placed into a variable
255 bytes long.

Best fix is to build a command front end which would allow you to tell the
system how big the parm is.

You could pad out the value, but you'd actually need to pad it out to 256
and the 256th character needs to be non-blank. Otherwise the system trims
it back to '/home' and you are back where you started.

HTH,
Charles


On Wed, Jun 12, 2013 at 2:33 PM, Robert Clay <zreclay@xxxxxxxxx> wrote:

This is really weird.

I'm creating a new SQLRPGLE program and it needs two entry parms. I set
up the entry procedure PR and PI like this:

d Main PR ExtPgm('MYPROG')
d 255
d 3

d Main PI
d InputDir 255
d InputDays 3

Walking it thru debug, with parm values '/home' and '3', InputDir shows
this:

> EVAL InputDir
INPUTDIR =
....5...10...15...20...25...30...35...40...45...50...55...60
1 '/home 3 '
61 ' '
121 ' '
181 ' '
241 ' '

Why are both parameters being passed in a single parm?

Are there limits to the length of input parms? I've searched but I can
find no reference to any limits. I'd guess that there are some. I've
changed InputDir to be as small as 10 (which won't work in practice) but
I still get the combined values being passed in together.

This is V6R1M0 with all current PTFs.

I've signed out and back in with no joy.

The PR/PI are last, just before the first free-form C-spec.

Creating the Main PR/PI like this has worked in the past but I'm stumped
as to why it isn't working this time.

Any ideas?

Thanks,
Robert

--
"Contrariwise, if it was so, it might be; and if it were so, it would
be; but as it isn't, it ain't. That's logic."--Tweedledee
--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.