Re: Need some ammunition (Procedures vs. Sub-routines)

One solution, since this is primarily a political issue, is to resign yourself to a long haul approach. Are the other programmers there willing to try new stuff, or is their only concern where to hang their jacket so they can be in the parking lot first when the day is over?

Maybe....? don't talk about the procedure, but about how it is used? "dayOfWeek = getDayOfWeek(someDate); " is really tantalizing for most RPG programmers. Showing them how to do it for themselves might bring them on your side so the boss is not getting push back from them? Asking them for permission to put one of their favorite routines into a procedure, so they get an example that they have a connection with might help them like the idea? They may be feeling lift behind. There may be a way to help them see a future that includes them.

Maybe an educational conference for them is possible?

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