--- On Tue, 3/17/09, Elardus Engelbrecht <[email protected]> wrote:
> From: Elardus Engelbrecht <[email protected]> > Subject: Re: COBOL and dynamic allocation (my two cents) > To: [email protected] > Date: Tuesday, March 17, 2009, 2:00 AM > 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? I wrote earlier about this issue the semi hidden file. It is not a practical thing as people leave the company and forget about this hidden file (more like undocumented). I truly like JCL as JCL is in a proclib where everybody can use file aid (or whatever) to scan. KISS methodolgy is this case for the it. ---------------------------------------------------------------------- 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
