I personally think its also a matter of setting standards. If there is no standard like always code destination in JCL or like always code destination in parameter dataset or there is no force to always use the parameter dataset both approaches will never be successful. I find the setting of standards and enforcing their usage is usually a bigger problem than the implementation itself.
Denis. -----Original Message----- From: Elardus Engelbrecht <[email protected]> To: [email protected] Sent: Tue, 17 Mar 2009 8:00 am Subject: Re: COBOL and dynamic allocation (my two cents) Ed Gould wrote: >Personally I find it abhorrent to hard code anything like destination in any programs. JCL is the ONLY way to go. It can be searched with multiple utilities (FILEAID and others) rather easily. This issue is that when (I did not say IF) a destination changes you must remember to recompile the program. What about writing the COBOL (or any other language) program so that destination(s) and other variable changes can be read from a dataset instead of hardcoding it or writing such things in JCL? There is thus only one compile/test action and many changes in the 'parameter' dataset on as needed base. Any better ideas? Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
