RE: Procedure names vs. production support

[<Rick.Chevalier@xxxxxxxxxxxxxxx>]

Thanks for the input.  Rather than individual replies I'm going to try and 
address each reply in one e-mail.

Bob,

Why not option 2?  I'm asking because that is what appears to be the choice of 
others in the department I have discussed this with. 

The idea of HTML-based documentation sounds good.  We do have a homegrown 
application for tracking production issues and resolutions.  It has been 
mentioned that the service programs could be documented there.  It's not web 
enabled (yet) but its a start.

Scott,

Interesting idea.  I hadn't thought about using the service program name as a 
prefix.  It could make for some long names, but I don't think that is much of 
an issue anymore.

Joe and Bruce,

I don't think Hawkeye goes to the procedure level unfortunately.  It shouldn't 
be hard to create a module cross-reference and schedule a job to refresh it on 
a regular basis.  The difficulty would be in getting support staff to look at 
it.

Good ideas.  Thanks again.

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.