RE: Procedure names vs. production support

Hehe.  Yep.

And no wimpy 26 ouncer either.  40 or better.

Ron Power
Programmer
Information Services
City Of St. John's, NL
P.O. Box 908
St. John's, NL
A1C 5M2
Tel: 709-576-8132
Email: rpower@xxxxxxxxxx
Website: http://www.stjohns.ca/
___________________________________________________________________________
Success is going from failure to failure without a loss of enthusiasm. - 
Sir Winston Churchill




rob@xxxxxxxxx 
Sent by: rpg400-l-bounces+rpower=stjohns.ca@xxxxxxxxxxxx
18/02/2005 12:17 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
cc

Subject
RE: Procedure names vs. production support






No, it's simply "buy a bottle..."

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Holden Tommy <Tommy.Holden@xxxxxxxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
02/18/2005 10:41 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx>
cc

Subject
RE: Procedure names vs. production support






<snip>

3) Buy a bottle of aspirin and take some when necessary.
</snip>

I thought this was requirement for programming in general....LOL

Thanks,
Tommy Holden


-----Original Message-----
From: Lim Hock-Chai [mailto:Lim.Hock-Chai@xxxxxxxxxxxxxxx]
Sent: Friday, February 18, 2005 9:02 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Procedure names vs. production support


We ran into the same situation here.

My experience tells me that nor matter what YOU said or what kind of tool
YOU present to help identify the service program, it is not going to be 
good
enough.  Because that basic argument that you are facing is this "when a
program blew up in the middle of the night, I don't want the on-call
programmer to have to go thru all kind of hoops to research the problem".

Notice I said what YOU say or do is not good enough.  From experience, 
this
is what I'll do:
1) Send in a formal request to management team for what you try to 
achieve.
Be sure to attach a few articles that written by well known experts that
describe the advantages of using service program.  (This seems to be the
best way to get management team to accept that service program is  good.
After all, who dares to argue with the expert.) 

2) If management team agreed that service program is good.  The next
obstacle is probably the question about other programmers might not be 
able
to support it.  In that case, request to have an expert on site to train
other programmers on service program and other new programming techniques.
(We have Jon Paris and Susan done the training on site for us.  They were
great. :)).

3) Buy a bottle of aspirin and take some when necessary.


Now, only if we can get Scott to present an article about the service
program naming convention in the NEWS/400, ...


Good luck. 
 


-----Original Message-----
From: rpg400-l-bounces+lim.hock-chai=arch.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+lim.hock-chai=arch.com@xxxxxxxxxxxx]On Behalf
Of Rick.Chevalier@xxxxxxxxxxxxxxx
Sent: Thursday, February 17, 2005 10:31 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Procedure names vs. production support



I'm trying to advance development in our shop to using procedures for
specific business logic and combining them into service programs.  The 
issue
I'm coming up against involves how to name the procedures.  If an error
occurs in a production run the message will identify the procedure 
receiving
the error, which may or may not be the name of the source member, causing
confusion and delaying problem resolution.  I have listed the options I 
have
come up with so far.

Option 1 is to give the procedures descriptive names so that developers 
can
more easily identify what the procedure does.  For example, WrtPmtRec if 
the
procedure writes a payment record.  This is the option I'm trying to sell
but I'm having trouble coming up with a documentation method that would
solve the production support issue.

Option 2 is to name the procedure the same as the actual source member
(currently 1 procedure = 1 module = 1 source member) so that the person on
call can more easily identify the source member of the procedure in error.
For example, the WrtPmtRec procedure would become SP4351M.  This is the
counter proposal I have received.  It solves the production support issue
but I think it will make development harder as the names have become
cryptic.

Option 3 is to use descriptive names for both the procedure and the source
member.  I like this one but over time I think we would run into naming
conflicts with similar procedures.

I'd like to hear opinions on these options and how others on the list have
resolved this situation in their environment.

TIA,

Rick


Privileged and Confidential.  This e-mail, and any attachments there to, 
is
intended only for use by the addressee(s) named herein and may contain
legally privileged or confidential information.  If you have received this
e-mail in error, please notify me immediately by a return e-mail and 
delete
this e-mail.  You are hereby notified that any dissemination, distribution
or copying of this e-mail and/or any attachments thereto, is strictly
prohibited.
-- 
This is the RPG programming on the AS400 / 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.


-- 
This is the RPG programming on the AS400 / 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.
-- 
This is the RPG programming on the AS400 / 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.


-- 
This is the RPG programming on the AS400 / 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.