Description: You can give your monitor a description here. Note: This option only applies when the Submit new JW collections on early collection end or failure is checked. Max resubmits: Use this option to indicate how many times additional Job Watcher collections will attempt to be created on each iteration of the monitor. In some situations like if a system save is occurring (which can cause the STRJW command to fail) using this option will minimize gaps in the data collected. Submit new JW collections on early collection end or failure: If the Job Watcher monitor detects that new collections are not being created, this option will allow additional attempts to create collections to happen. Keep in mind that in some cases this runs SQL statements that could be resource intensive (CPU/disk) so you may not want to do this on production systems. The default analyses are the most commonly used analyses and can be identified by using the Analyses -> Analyze collection menu on a collection and looking at the Run all default column in the window. Run analyses automatically: This option if checked will automatically run all default idoctor analyses on each collection created by the monitor. You will want to set this value high enough so the data is available when needed but not too high that you are consuming a lot disk space unnecessarily. Maximum historical collections: How many collections do you want keep? The JW monitor allows you to keep up to 999 historical collections. The next monitor won t start until the Maximum collection duration is reached. If the amount of data collected exceeds this value in a collection, the collection will end prematurely and there will be gaps in the monitor data. 2ħ Maximum collection size: This parameter indicates the maximum size (disk space) for each collection in the monitor. Within Job Watcher, expand the Job Watcher icon and then (left) click Monitors in order to work with the monitors available on the current system as shown in figure 2.
#IDOCTOR FOR MAC REVIEW HOW TO#
This example will show how to start a Job Watcher monitor. If you need to add a connection to your system first, then right-click the list of connections and choose the Add Connection menu. Starting a Monitor You first want to start the idoctor GUI and launch one of the components that support monitors by doubleclicking the desired system as shown in figure 1. The support for Job Watcher, Disk Watcher and PEX Monitors is available in IBM i version V5R3M0 and higher. Multiple monitors can be active at the same time. In this document we are going to focus on using the idoctor GUI, in appendix A there will be samples of the green screen commands. Can be started, paused, resumed, and ended using either the idoctor GUI or by using traditional green screen commands.
Users can define the number of historical collections retained. Collections can overlap so no activity is lost. The following are some key features that I think makes Monitors a key tool in performance analysis: 1. Updated for latest changes (RSTJWMON removed) Updated for latest changes 1Ģ Introduction The purpose of this document is to demonstrate how to define and start an idoctor Monitor. Added Appendix B (describes modification of system startup program to automatically restart a monitor after an IPL). Added max collection size parameter at Feb 2009 Added comments on restarting monitors for scheduling or after an IPL. Added mention of new support for PEX Analyzer Monitors at 6.1. Changes 19 June 2006 Initial Creation Updated to match GUI changes. Monitors provide 24x7 collection support of Job Watcher, Disk Watcher and PEX statistics for detailed performance investigation data when you need it most. Abstract Guide to running the idoctor Monitors. 1 IBM idoctor for IBM i Development Team 11 October 2016 IBM idoctor for IBM i idoctor Monitors Guide Licensed Materials - Property of IBM Copyright International Business Machines Corporation 2010, All rights reserved.
0 kommentar(er)
