|
Our change management system actually has a standard temp lib that we use to put these dummy files. However, it has the following problem: 1) Sometime two programs have same made up DDM name but refer to two different logicals. 2) Some developers dup the file to this temp lib and forgot to remove them after they are thru. Guess what happen when the next developer change the actual file and did a recompile on program? Mr. CPF4131 shows up. 3) Our document software (Hawkeye) is not able to pick up the relationship on made up file name. -----Original Message----- From: rpg400-l-bounces+lim.hock-chai=arch.com@xxxxxxxxxxxx [mailto:rpg400-l-bounces+lim.hock-chai=arch.com@xxxxxxxxxxxx]On Behalf Of Steve Morrison If you are using PDM, check the options under F18. You can specify a job description to use for your batch jobs. You could create a special job description for use by PDM, with a library list that includes a set of dummy files for your DDM files. If you are using WDSCi, use the same technique of specifying a special job description to be used for your compiles.
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.
midrange.com
