Re: CL programming standards

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

I see a need for adding to the *LIBL all the time - server jobs just 
don't have the same setup as interactive jobs, so you need to take care 
of that kind of thingl

HTH
Venr

On 4/26/2012 3:03 PM, Stone, Joel wrote:
> What are some of the CL programming standards that your shop has found valuable?
>
> I would think that a few standards are NEVER have the following in production CL:
>
>   - never have a library name in CL (OK allow QTEMP)
>
>   - never have even a variable library name in CL
>
>   - never have a person's name or email address in CL (OK in author comments)
>
>
>
> Would a library in CL ever be necessary?  I would think that good coding would allow the *libl to do the work of choosing the correct lib in almost all cases.
>
> Comments and additional good practices?
>
>
>
> ______________________________________________________________________
> This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________