Converting Production Batch Procedures As you may know, DBA-ES supports and maintains hundreds of production batch procedures, some of which are run daily, weekly, monthly, annually, and on request.  Examples include (but are not limited to) creating/changing an ADABAS file(s), backing up ADABAS, reordering ADABAS files into one extent, file archive procedures, annual database reorders, and so on. DBA-ES is in the midst of an extended project to convert our batch procedures to better standardize them.  This will ultimately improve their reliability and reduce the incidence of ‘down time’ to wait on a file restore following a failed ADABAS Utility process or other application process, such as a file archive failure. Batch procedures are being modified in such a way that organizes them into procs (where it makes sense), rather than in-stream JCL that normally would require many JCL changes when a ‘global’ type change needs implemented. All DBA procedures are being modified to run with the database active and ‘file lock’ steps have been added to prevent the file from being used during maintenance. All of these changes will enable us to get closer to a true 24/7 operation, but for now will allow us to keep our database active even beyond the ‘announced’ hours of availability. In addition, automatic restores of files are being added to the processes that may need to be automatically backed out due to failure.  This should help minimize any potential down time and ensure the file is available for all advertised hours of availability. Finally, we’re taking a look at some processes that we usually run on an adhoc basis and making them scheduled production procedures.

Printer friendly view