RE: Program Call Parameters

["Clapham, Paul" <pclapham@xxxxxxxxxxxxx>]

I can't quite tell if you're shouting at me, but I'm guessing that you are.
I thought that you suggested the RPG program should be rewritten to have a
single data structure parameter, but please feel free to shout at me again
(or clarify your suggestion) if that was not what you meant.  Let's assume
that the RPG program is indeed unchangeable, which it quite likely is if it
has that many parameters.  Then it would be easy to write a wrapper program
with a single data structure parameter.  It would break down the data
structure into the 35 parameters and call the unchangeable RPG.

By the way, I'm one of the authors of our monolithic program with
60-something parameters.  I proposed about two years ago that it should be
rewritten in a modular (ILE) fashion.  This would make it more maintainable,
more useful, and even more efficient.  That hasn't happened yet, there are
more important things to do (and I agree with that assessment).  So I
understand that programs can be unchangeable.

PC2

-----Original Message-----
From: Richard Jackson [mailto:richardjackson@richardjackson.net]
Sent: October 17, 2000 08:57
To: JAVA400-L@midrange.com
Subject: RE: Program Call Parameters


-|Have you ever seen a Java method with 35 parameters?

No and it sounds horrible.  Why do you want to have so many?

-|Better design -- for a monolithic program.  My company's "pricing -|black
box" program is designed in just this way, and had over 60 -|parameters last
time I looked.

I did not prescribe the number of parameters or tell the OP that he should
or can break it down.  Maybe he cannot have fewer parameters for his
existing design and cannot change the design.  Maybe he has to do it this
way now then go back later and do it correctly.  Would you have me tell him,
"F**k off, you can't do it and you're stupid to try"?   Or should I give him
the best solution within the stated parameters?

What is your problem?

Richard Jackson
mailto:richardjackson@richardjackson.net
http://www.richardjacksonltd.com
Voice: 1 (303) 808-8058
Fax:   1 (303) 663-4325

-|-----Original Message-----
-|From: owner-java400-l@midrange.com
-|[mailto:owner-java400-l@midrange.com]On Behalf Of Clapham, Paul
-|Sent: Tuesday, October 17, 2000 8:55 AM
-|To: JAVA400-L@midrange.com
-|Subject: RE: Program Call Parameters
-|
-|
-|Better design -- for a monolithic program.  My company's "pricing
-|black box"
-|program is designed in just this way, and had over 60 parameters
-|last time I
-|looked.  But it really needs to be rewritten as a collection of
-|modules that
-|would have no more than 6 parameters each.  Have you ever seen a
-|Java method
-|with 35 parameters?
-|
-|-----Original Message-----
-|From: Richard Jackson [mailto:richardjackson@richardjackson.net]
-|Sent: October 16, 2000 16:41
-|To: JAVA400-L@midrange.com
-|Subject: RE: Program Call Parameters
-|
-|
-|create a structure, copy the data into the structure, call the RPG program
-|with a pointer to the structure.  One parameter - better design.
-|
-|Richard Jackson
-|mailto:richardjackson@richardjackson.net
-|http://www.richardjacksonltd.com
-|Voice: 1 (303) 808-8058
-|Fax:   1 (303) 663-4325
-|
-|-|-----Original Message-----
-|-|From: owner-java400-l@midrange.com
-|-|[mailto:owner-java400-l@midrange.com]On Behalf Of Kumar, Santha
-|-|Sent: Monday, October 16, 2000 1:05 PM
-|-|To: JAVA400-L@midrange.com
-|-|Subject: Program Call Parameters
-|-|
-|-|
-|-|Hello,
-|-|
-|-|The program call class in JT/400 allows a Java program to call an
-|-|AS/400 RPG
-|-|program. However there is a maximum restriction of 35 parameters.
-|-|One way to
-|-|overcome this limitation of 35 parms is to call a stored procedure which
-|-|then calls the RPG Program. Is there any other easy way to directly call
-|-|those programs that have more than 35 parameters ?.
-|-|
-|-|Thanks in advance
-|-|
-|-|-Santha Kumar
-|-|+---
-|-|| This is the JAVA/400 Mailing List!
-|-|| To submit a new message, send your mail to JAVA400-L@midrange.com.
-|-|| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
-|-|| To unsubscribe from this list send email to
-|-|JAVA400-L-UNSUB@midrange.com.
-|-|| Questions should be directed to the list owner: joe@zappie.net
-|-|+---
-|
-|+---
-|| This is the JAVA/400 Mailing List!
-|| To submit a new message, send your mail to JAVA400-L@midrange.com.
-|| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
-|| To unsubscribe from this list send email to
-|JAVA400-L-UNSUB@midrange.com.
-|| Questions should be directed to the list owner: joe@zappie.net
-|+---
-|+---
-|| This is the JAVA/400 Mailing List!
-|| To submit a new message, send your mail to JAVA400-L@midrange.com.
-|| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
-|| To unsubscribe from this list send email to
-|JAVA400-L-UNSUB@midrange.com.
-|| Questions should be directed to the list owner: joe@zappie.net
-|+---

+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---