×
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.
Steve,
I see the issue now, I'm compiling back to V5R1 (for customer
compatibility reasons). I just need to compile to a more current level
and I should be fine. Thanks for pointing me in the right direction ....
it is what this list is best at.
Rich Loeber
Kisco Information Systems
http://www.kisco.com
--------------------------------------------------------------------------
smorrison@xxxxxxxxxxxxxxxxxxx wrote:
Here's what I found from a quick google search:
http://www.itjungle.com/fhg/fhg032404-story01.html
PARAMETER PASSING
IBM has made some changes to the Program (PGM), CALL, Call Procedure
(CALLPRC), and Transfer Control (TFRCTL) commands. In V5R2, you are
allowed to list up to 40 positional parameters in the PARM parameter of
the PGM command. However, in V5R3, you may list up to 255 parameters. CALL
and TFRCTL accept up to 255 parameters, up from the V5R2 limits of 99 and
40 respectively.
Steve
Steven Morrison
Fidelity Express
Rich Loeber <rich@xxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/13/2009 10:05 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
Subject
CPD0063 - CL PARM Limits?
I'm getting this error on a CLLE program with 43 parameters (from a
command) .... I was not aware of any limits. Does anyone know of the
limits on a CL program?
Rich Loeber
midrange.com
