|
At one time where I work--long before the present enlightened group of managers <g>--the convention for CL source was to begin the name with "CL." I don't know how long it was before people noticed that there was something wrong. It was more than a couple of days. > -----Original Message----- > From: VWilliamson@xxxxxxxxxxx [mailto:VWilliamson@xxxxxxxxxxx] > Sent: Wednesday, March 26, 2003 3:10 PM > To: RPG programming on the AS400 / iSeries > Subject: RE: Naming conventions - was ->RE: Replacing *entry plist > > > > Couldn't let this one slide without making a comment. > > Coming from a S36 using that wonderful tool called 'POP', it was only > logical for us to want to see all related source on 1 screen when we > started using PDM way back in 1990. All our source is in one > source file > called QSOURCE. Each source has a standard suffix that we > use for each > type of source. The only other type of source file we use is > QDDSSRC in > which we keep only master file source. Finally got rid of > the last S36 > source file last year. > > > > Valene M. Williamson > IBM Certified Specialist > vwilliamson@xxxxxxxxxxx > 972-448-8018 > > > _______________________________________________ NOTICE: All e-mail sent to or from this e-mail address will be received or otherwise recorded by The Sharper Image corporate e-mail system and is subject to archival, monitoring, review by and/or disclosure to Sharper Image security and other management. This message is intended only for the use of the addressee and may contain information that is privileged and confidential. The contents of this message may contain personal views which are not the views of The Sharper Image. If you are not the intended recipient, dissemination of this communication is prohibited.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.