> -----Ursprungligt meddelande----- > Från: IBM Mainframe Discussion List > [mailto:[email protected]] För Ed Gould > Skickat: den 19 mars 2009 03:09 > Till: [email protected] > Ämne: Re: COBOL and dynamic allocation (my two cents) > > > I disagree, Ed. Reading a list of > > destinations from a "parmlib"-type dataset can be the easiest, and > > best way, to handle this situation. But updates to this > dataset should > > be controled and audited, just like a PROCLIB or any other > > control-related library. Make provision for comments in the > > destination list and it doesn't have to degenerate into a > boar's nest,
> > > > -- Rick > -----SNIP-------------- > > Rick: > Yes you can do that I didn't say you couldn't the issue is > (albeit a side issue and important IMO none the less) > associating the contents back to the step that is using it > *AND* if you then move it out of lets say proclib for > discussion here, there is and always will be "oops" I forgot > that this had to be updated. Plus you have the side issue of > "when" the change occurs. usually its another department that > handles the update so scheduling it is a matter of what can > go wrong will go wrong. I am a pessimist and I have rarely > seen it where departments can actually depend on an update to > occur when it should. This is not to say "your" installation > is better but more times than not it doesn't happen. > > There is also another side issue I have experienced myself. > in the it is extremely common to search proclib for a > dest=xxxx (for production and non production) chances are > with your way moving it to parmlib type dataset this scan > will miss the destination you are looking for. > As i see it, it is about how You do the application maintenance. This is really no different than other applications, although other may be implemented in COBOL or other programming languages and this is maybe at JCL level "programming". In the same way as You secure future maintenance of COBOL programs You do for this case. (Application "librarys", production installation routines etc.) Everything in these cases is about code and data storage; COBOL and DB2, JCL and parmlib, ASM and QSAM, etc... Same base routines, rules and quality verification etc. Regards, Thomas Berg __________________________________________ Thomas Berg Specialist IT-U SWEDBANK ---------------------------------------------------------------------- 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
