|
on 10/21/97at 12, the Great and Grand Wazir James Turnbull <jamest@UTC.COM.AU> said: I find the data area method is often dangerous. You have to take care when you update the data area in the job and that the job runs perfectly every time. Which it should. But everyone is aware of the operational problems that can arise: upgrades, program changes, legacy code, all mean that the data area method should be treated with caution and if you are going to use it the document your data areas and what they do when you document the code. On the other hand, if there is a problem it should be sorted out before the problem cascades and propagates all over the barnyard. Whenever one builds a lock one should also provide the unlock and it's associated business rules. One shouldn't use an automatic unlock anymore than they'd use an automatic MONMSG(CPF0000) (or is it MONMSG(9999)?). ---------------------------------------------------- Booth Martin --------------------------------------------------- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.