Dutch,
... I have to say it....
It's Simple. Don't call them Procedures....
Explain that IBM has a new kind of subroutine that you can pass parameters
to....
Refer to them as "Parameter Subroutines" or maybe "Psubroutiners".
Kidding aside, Sorry man, I feel your pain.
Charlie
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of RPGLIST
Sent: Friday, December 27, 2013 11:00 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Need some ammunition (Procedures vs. Sub-routines)
I won't go into the entire lengthy and boring conversation I just had with
upper management, but I was basically told that under no circumstances am
I to add procedures to certain applications. The justification is that
by doing so, we will be required to re-test the entire system, payroll,
dispatch, load balancing, AP, AR, etc.
I however was provided an opportunity to make my case, and I have a list of
reasons, but I need every bit of ammunition I can come up, so any help from
ya'll would be cool.
Dutch
--
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.