Please share your thoughts as per your experience for how the mainframe applications are designed for if they are demanded running on MONTHLY LAST BUSINESS DAY OF THE MONTH.
I see some of the jobs which are defined in scheduler like MONTHLY LAST BUSINESS DAY OF THE MONTH and they run during non free MIPS time and really take considerable MIPS.They provide feed to dataware house and it could be difficlut in convincing them for any sort of data compromises with any change of these jobs.
Joined: 06 Jun 2008 Posts: 8280 Location: Dubuque, Iowa, USA
and they run during non free MIPS time and really take considerable MIPS.
Terminology note: this is not true. MIPS is a value for the entire machine and cannot be applied to individual jobs. You can say the job runs during heavy load and consumes a lot of CPU time. It is absolutely wrong, however, to say any job "takes considerable MIPS" -- because jobs cannot take MIPS, cannot use MIPS, cannot even be measured with MIPS. Jobs can use cycles (aka CPU time), require tapes, require disk data sets, but they cannot "use MIPS".
The business rationale for end-of-the-month (EOM) processing is usually based on accounting cycles and maintaining historical records. While EOM processing can be a pain, it is usually difficult if not impossible to reschedule the jobs due to cyclic requirements.
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
Depending on the type of data (and the volume) needed to load into the warehouse, it might be possible to make some kind of high-speed backup of this data and then run the "heavy" process when the system resources are not so constrained. This would also depend on how quickly the warehouse must become "current".
As Robert mentioned, it may be difficult or even impossible to have the schedule changed.