OK - I should never write "never".
I read the article. You are talking about a very rare, non-production, system type CL.
I am referring to everyday applications that run the business - not managing the OS.
Anyone know where I can find "best practices" info on CL?
I have how-to books by Greg Veal and others; they are great on syntax, but not much on style and best practices used out in the field.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of sjl
Sent: Friday, April 27, 2012 8:57 AM
Subject: Re: CL programming standards
Some reasons for qualifying the library in a CL program:
I have other reasons, will reply later with additional information.
Hint: There are some very good reasons for qualifying the IBM commands used
in certain CL programs to QSYS.
What are some of the CL programming standards that your shop has found
I would think that a few standards are NEVER have the following in
- 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
Comments and additional good practices?