Recommended: Click here to run a Free driver update scan »
A new level of freedom and flexibility to monitor objects that could impact DASDgives operators fresh insight into system resource use. For example, shops runningHigh Availability solutions can now monitor journal receivers (such as the auditjournal) in real-time and attach a threshold that will alert them if levels arebreached. Similarly, important physical files in third party applications, such aspayroll, can now be monitored. Data queues, distribution queues, object sizes aswell as file record counts, deletions and percentages now give new scope toreal-time problem identification.
Object monitoring helps operators to guard against problems that could arise aroundspecific objects and impact system resource if left unchecked. V12Â's ASP andtemporary storage monitoring takes care of unforeseen DASD issues that could degradeperformance and impact users without the time consuming requirement of interrogatingindividual jobs on the system. Without close monitoring of ASPÂ's, overflow into acentral ASP, caused by an undetected problem on the system, could leave dataunprotected and at risk of being lost altogether should the system crash. Independent ASPÂ's, which are unable to overflow into another ASP, can also bemonitored to detect when they are reaching maximum desired capacity. At a glancemonitoring of ASPÂ's and physical disk units can be defined in several ways withreal-time monitoring of the percentage of ASP Busy Unit; number of ASP Busy Unit;ASP Space Free; ASP Space Used and ASP Status, to name a few - this makes thepinpointing and resolution of problems a speedy process.
Typically, even innocent system changes can cause the auxiliary storage to surgewithout immediate understanding as to what has caused the surge. Seemingly smallsecurity changes that so often follow an audit, such as revoking access to aparticular file, can cause a job to loop, generate spool files and ultimately sendthe auxiliary storage soaring. These situations, whilst not unavoidable altogether,are able to be identified in real-time before they have an opportunity to impact onresource and users.
Temporary storage issues can be overcome by creating a dedicated group monitor. Thiscan be as simple as a single bar in the online monitor that will alert operators ofthreshold breaches requiring investigation. In this case, clicking on the bar willshow the individual subsystems and the total MB usage of each. Operators can thenimmediately create a new group monitor to detect all the jobs running in that subsystem and view the temporary storage usage of each. By  floatingÂ' the view, anynumber of jobs that reside in that subsystem can be easily viewed and sorted intohigh usage order for immediate problem identification. This entire process pinpointsproblems in a couple of minutes, ensuring operators can be pro-active to theirtemporary storage issues. Prior to this new flexibility in QSystem MonitorÂ's V12,operators had no simple means of reporting through OS/400 to show temporary storageusage and were forced to investigate a painstaking one-by-one analysis of what couldbe hundreds of jobs in any particular sub system. The flexibility of V12 givesoperators the option to monitor temporary storage by job, user, subsystem or eventhe entire system.
QSystem MonitorÂ's disk monitoring capabilities form part of the overall performancesolution that also covers system monitoring, network monitoring, job monitoring andavailability monitoring to complete V12Â's core performance monitoring and reportingcomponents.
