Art.

The most important is to give each new version of the program a version
level (i.e. v01.01a).  Include it in the modification history.

Also print the program name and version (PROGNAME v01.01a) whenever the
program is executed if possible.

~~~~~
Next, and additional option for the files is read & write.

All data bases with their open mode and the datasets used or something
like it for Relational DB's.

~~~~~
Library names and program locations could be listed.

~~~~~
Maybe, last but not least, have a variable keep track of where the
programs is (Mainprog, SubrtnA, Subrtnb...).  This is useful for
debugging reasons or when a controlled (programmed) error occurs.

~~~~~
I hope I was of some help.

Olav Kappert.
IOMIT International (HP Applications Development Specialist).
Art Bahrs wrote:

>Hi All :)
>   Ok... I left this on topic cause it fits alot of what a lot of you/us
>do....
>
>   What standards and/or practices does you / your shop follow when it
>comes to languages like Perl, Python, XML, HTML and similar newer
>languages?
>
>   I am working a really sharp guy here and I am trying to get him to see
>that using a skeleton for each program/subroutine and documenting heavily
>throughout a program/script/job stream is a good thing and a habit to get
>into...
>
>   What do you all think?  I have included a copy of the skeleton I am
>developing / going to propose as a standard for Perl for our shop.  I have
>taken out some white space to save on the email...
>
>Thanks,
>Art "I think I am getting old... They don't even know of VTOC's anymore!
>hehe" Bahrs
>
>=======================================================
>Art Bahrs, CISSP           Information Security          The Regence Group
>(503) 553-1425              FAX (503) 553-1453
>
>
>#*****************************************************************************
># Title:
># Author:
># Date:
># Purpose:
>#
># Program Overview:
>#
># Compilation/File Redirect Instructions
>#
># Program Dependancies
>#
>#==============   M O D I F I C A T I O N  H I S T O R Y
>===================
>#
># Date      Who   What
>#+---------+---+--------------------------------------------------------------
># dd Mmm yy xxx Creation
>#
>#*****************************************************************************
>
>#--------------------   U S E  S T A T E M E N T S
>-------------------------
>
>use strict;
>
># ====================== C O N F I G U R A T I O N
>===========================
>
># ------------------------- F I L E S  I N P U T
>-----------------------------
>
># ------------------------ F I L E S  O U T P U T
>----------------------------
>
># ---------------------------- V A R I A B L E S
>-----------------------------
>
># ===================== I N I T I A L I Z A T I O N
>==========================
>
>
># Subroutine Declaration Block (Remove this line when Used)
>#*****************************************************************************
># Sub Title:
># Author:
># Date:
># Purpose:
>#
>#
># Parameters:
># (1)
>#
># Return Value:
>#
>#*****************************************************************************
>
># ====================== C O N F I G U R A T I O N
>===========================
>
># ------------------------- F I L E S  I N P U T
>-----------------------------
>
># ------------------------ F I L E S  O U T P U T
>----------------------------
>
># ---------------------------- V A R I A B L E S
>-----------------------------
>
># ===================== I N I T I A L I Z A T I O N
>==========================
>
>###
># End of Sub {Sub Name here}
>###
>
># ========================   M A I N    B L O C K
>==========================
>
>###
># End of Program
>###
>
>
>==============================================================================
>IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed.  If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited.  Nothing in this email, including any attachment, is intended to be a legally binding signature.
>==============================================================================
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *