Sidebar

Watch Your System with the New Job Watcher Monitor

System Administration
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Are performance problems on your iSeries causing you stressful days and sleepless nights? They aren't for me anymore. That's because I'm running the new Job Watcher monitor on my critical systems. I no longer worry about whether or not a performance problem occurs and whether or not I will be able to capture the necessary data. The Job Watcher monitor captures the data for me 24x7.

Let me tell you about Job Watcher. If you've never heard about Job Watcher, it's about time someone starts to spread the good news. Job Watcher is included under the iDoctor suite of tools. It's a great tool for detecting job waits, seizes, and other types of contention. Job Watcher allows you to watch a specific job, a set of jobs, or all the jobs on your system. Watching all the jobs on your system is especially useful when you aren't sure which jobs are having performance problems or when you just want an overview of how your entire system is performing.

Job Watcher returns real-time information, and you don't have to wait until all the data is collected before you start your analysis. You can start looking at the data almost immediately. The data is displayed in an easy-to-view graphical format. Job Watcher also gives you drill-down capability to determine the impact that a wait condition is having on the entire system or on a particular job. Even if you are not a performance expert and are not able to completely interpret the results, it will at least enable you to pinpoint a particular problem and lead you in the right direction to get additional assistance if needed. Job Watcher collects the data from the jobs, threads, and tasks you're watching in a manner that does not affect other jobs on the system while it is collecting, so it won't add to your performance problems.

As if Job Watcher didn't have enough great features, a Job Watcher monitor function has now been added (available for release V5R3 and above), which you can run 24x7 on your system. It includes all the great features of Job Watcher but gives you the added capability of running Job Watcher collections continuously rather than for just a specific period of time. I can't tell you how effective this has been in helping me solve a considerable number of performance problems and issues that I would not have been otherwise able to resolve.

Let me explain to you how it works and then give you some examples of how the Job Watcher monitor was able to help me resolve some performance problems. The Job Watcher monitors can be started via the GUI or by using traditional 5250 green-screen commands. Monitors must be manually ended; however, an IPL will also end a monitor. Monitors must be manually restarted after an IPL. We simply added code to our startup program by using the available green-screen commands to ensure that the monitors automatically restart after an IPL. The Job Watcher monitor will keep a predefined number of historical collections, and collections can overlap so no activity is lost.

After you've downloaded and installed Job Watcher, click on the iDoctor for iSeries icon on your desktop. This will automatically pick up any iSeries Navigator connections you already have established and display them.

If you don't have any connections or need to add a new one, right-click anywhere within the window and select Add Connection.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020600.png

Enter the name of your iSeries server and give a brief description (not required). Then click on OK to add the new connection to the list.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020601.png

In your list of connections, double-click on the system of your choice. This will bring up the sign-on display for the iSeries system. Your profile should automatically be displayed. Type in your password and press OK to get the list of iDoctor components that are currently installed on this particular system. Ensure that the Job Watcher component is highlighted and click on Launch or double-click on Job Watcher.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020602.png

This brings you to the main Job Watcher display.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020603.png

To start the monitors via the GUI, right-click on Job Watcher. Then select Work with Monitors.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020604.png


A new window is created where all previous Job Watcher monitors, active or not, will be listed. If no Job Watcher monitors are available on your system, the new window will be empty. In this example, one Job Watcher monitor, JOBWMON, is already active.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020605.png

Right-click anywhere in the new window and click on Start New Monitor. In this example, our system already has an active monitor. By right-clicking on the active monitor, you will get different options than if you right-click anywhere else in the new window. With an existing monitor, you can view the current collections, hold a monitor, end it immediately, end it after the current collection, or delete a monitor.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020606.png

Before starting a new monitor, you need to fill out a few details specific to your monitor. Give your monitor a name and decide which library you want the collected data to be stored in. In the example that follows, we will call our monitor JWMON, and we will store the collected data in library JWMONLIB.

How long do you want each collection to run? In this example, each collection will run for 60 minutes. How many collections do you want to keep? In this example, five historical collections will be kept. So in this example, you will be collecting data for one hour and keeping five of these collections as historical data. If there was a performance problem, you would be able to go back five hours in time. After five hours, the oldest collection is overlaid and new data is collected in its place. You have to decide if this is enough historical data for you to keep. If you typically have customers who don't call you for several hours or until the next day, maybe you want to keep more than five historical collections. This will allow you to go back further in time to resolve performance issues. Do you see where I'm going with this? On our more critical systems, I have two-hour collections and I keep 14 of these so I can go back 28 hours in time. This amount of data allows me to go back far enough to find the problem. Be aware that storing this much data takes a fair amount of DASD . However, we don't have a storage problem, so I am being allowed to keep this much data. In the future, though, this might not be the case.

In this example, there is a collection overlap of 30 seconds. So 30 seconds before the current collection ends, the new collection will start so you don't lose any data.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020607.png


You also need a Job Watcher definition. A definition gives Job Watcher the specific details of what you want collected. You can use an existing definition by clicking on View. If there are existing definitions, they will appear here. You can also create a new definition or use one that has been predefined. To create a new Job Watcher definition, you need to give it a name. In this example, we call our definition JWMONDEF.

Now, decide how long you want each of your individual collections to run. You can select up to 1440 minutes for your collection duration. You probably don't want your collections too large. This really depends on the size of your system. Very large systems can collect a large amount of data in a fairly short amount of time.

The interval duration is the amount of time in between the Job Watcher collection snapshots. The smaller the interval duration, the more information you will be able to collect and have available to you. If a seize or object lock only lasts for one second and you have your collection interval set to five seconds, you may miss it. So be sure to set your interval duration accordingly.

What other information do you want included? Make sure you include call stacks. This is one of the great features of Job Watcher and is especially useful when you are drilling down into a particular problem. You want to make sure you are including this information.

Include SQL statements if your users or applications typically use SQL functions. This will allow Job Watcher to capture the SQL statement (along with host variables) and you can view it later if you think the SQL statement is causing performance problems.

You can also include communications data if you want; however, currently there are no packaged Job Watcher queries, graphs, or reports related to communications data.

Force first interval means all jobs and tasks will be included in the first interval. Normally, only jobs and tasks that use CPU during an interval would be included. If you are starting Job Watcher when a problem is already in progress, it's a good idea to include idle jobs and tasks. But if you are starting Job Watcher prior to a problem occurring (for example, as a monitor), there is no need to include all jobs and tasks.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020608.png

These are some of the predefined iDoctor-supplied definitions. If you aren't sure how to set up your first monitor definition, try some of these and decide if they work for you. You can always change your monitor later using a different definition.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020609.png

If you have some existing Job Watcher monitor definitions already created and you can't remember the details, you can click on View. This will show you the details for an existing definition.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020610.png

Now, you are ready to start the monitor. Click on Start Monitor. If the library you specified does not exist, you will be prompted with the following message:

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020611.png

You will see the newly-created monitor with a status of Active.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020612.png

Right-click on the active JWMON monitor and select View Collections.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020613.png

This brings up the library that contains your stored collections.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020614.png

Double-click on the library name, JWMONLIB, to view the collections. Since we just started the monitor, there is only one collection available. Notice that this collection is called JWMON01. Subsequent collections will be named JWMON02, JWMON03, JWMON04, etc. After the maximum number of historical collections is reached, the oldest collection will be deleted and a new collection created.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020615.png

Double-click on JWMON01 to see the available graphs and output files.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020616.png

In this example, there are 13 historical collections with one current collection in progress. When JOBWMON50 is created, JOBWMON36 (the oldest collection) will be deleted.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020617.png

Several Job Watcher green-screen commands are available, and these can be found in library QIDRWCH.

  • ADDJWDFN—Add Job Watcher Definition
  • STRJWMON—Start a Job Watcher Monitor
  • HLDJWMON—Hold a Job Watcher Monitor
  • RLSJWMON—Release a Job Watcher Monitor
  • ENDJWMON—End a Job Watcher Monitor
  • RSTJWMON —Restore a Job Watcher Monitor
  • ENDJWCOL—End a Job Watcher Collection
  • DLTJWMON—Delete a Job Watcher Monitor

Now that your Job Watcher monitor is active and collecting data, you can relax, sit back, and let the performance problems begin. When your customer calls and says there was a problem at 1:00 this afternoon, you can confidently go to your Job Watcher collected data and start investigating. Unfortunately, without the Job Watcher monitor, you may have to tell your customer that the problem needs to reoccur before you can capture the right data. Don't get me wrong. The Performance Tools LPP (5722PT1) provides some great reports, and there are some other real-time performance commands—like WRKSYSACT (Work with System Activity), WRKACTJOB (Work with Active Jobs) and WRKSYSSTS (Work with System Status)—that can give you some great information. But no tool captures job waits, seizes, and other object contention like Job Watcher. So now that you know how to start your Job Watcher monitor, let me show you what it can do for you.

Job Watcher provides you with a large amount of graphs. If you don't know where to start, go to the Wait Graphs by Interval and click on Collection overview time signature. This graph gives you a good overview of what's happening on your system, and it's a very good starting place.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020618.png

One day as I was leisurely browsing through my Job Watcher collections, I started with the Collection overview time signature. This graph happened to show a high amount of DASD page faults (indicated by the light brown color in the graph). If you didn't already know this, you could look at the legend that is associated with the graph and displayed on the right side or use your mouse to fly over the graph and see the interval details. The customer hadn't reported any problems or issues; but because I was using the Job Watcher monitor, I was able to look through the data on my own time and at a relaxed pace.

In this example, each of the intervals is two seconds. So each bar you see here represents a two-second interval. You can set this collection interval to any value between .1 and 3600 seconds. But remember, the smaller the collection interval, the more detailed information you will be able to see. If a seize or object lock lasts for only one second and you have your collection interval set to five seconds, you may miss it.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020619.png

From this graph, I was able to drill down into any one of these different intervals by right-clicking on one of them and selecting DASD page faults graph by job.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020620.png

By drilling down into the collected Job Watcher data, I was able to see a list of all the jobs ranked by DASD page faults for that particular interval.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020621.png

From here, I was able to drill down even further into each one of these jobs by double-clicking on the horizontal bar graph following a particular job. By looking at this Interval Details screen, I was able to determine that each of these jobs with the highest DASD page faults was occurring in the same pool and the same subsystem.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020622.png


Upon further investigation on the iSeries system itself, I noticed that these jobs were running in a subsystem that had originally been set up with a private pool. This private pool size may have been sufficient in the past; however, the customer had recently been adding more and more jobs to this subsystem, and the size of the private pool was no longer big enough to handle the workload. I was able to change the pool for this subsystem to a shared pool (but not being used by any other subsystems), and the performance adjuster (system value QPFRADJ) was then able to adjust the size of the pool according to the workload. DASD page faults were drastically reduced. All of this was done proactively before the customer even detected or reported any type of slowdown or performance issue.

After the change was made, I was able to go back to my Job Watcher data and see the difference. As you can see from this graph, there are still some intervals with DASD page faults but they have been significantly reduced. Next problem, please.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020623.png

Here's where Job Watcher really shines. A problem was reported to me, and I was also given the timeframe in which the problem occurred. This helped me narrow my search through the collected data. I was able to go directly to the collection that occurred over this timeframe. Since I still wasn't sure what I was looking for, I went to the Wait graphs by interval and then clicked on the Collection overtime time signature graph. When I reached the problem timeframe, it was very obvious by looking at the Job Watcher data. The purple in this graph indicated a seize contention problem. In this example, you can see the problem started in interval 2179 and just continued to build.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020624.png

In this example, I drilled down into interval 2179 to see what was going on. I right-clicked on interval 2179 in the purple area and clicked on Seize contention graph by job.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020625.png

This gave me a list of the jobs ranked by seize contention. From here, I could drill down even further by double-clicking on any one of the horizontal bar graphs. In this example, I drilled down into the first job.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020626.png

This screen gave me all the details for this particular job during this interval (2179). You can see the job name, the subsystem and pool it was running in, priority, etc. It also showed me the Current or last wait, which was Seize: shared. This screen showed that the job was waiting on object AMFSRVC, and it also identified the holder of the object. If I didn't know what AMFSRVC was, I could click on the Object waited on tab, and it would show me the object type. In this case, it was a library. As I continued to look at the other jobs on the previous screen, I started to see a pattern. All the jobs were waiting on the same object, and it was being held by the same job.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020627.png

To further investigate, I clicked on the Call stack tab to see the call stack of the waiting job. In this example, the waiting job was opening a file, as indicated by QDMCOPEN.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020628.png

From here, I was able to look at the call stack of the holder job by clicking on Show Holder. From the call stack of the holding job, I was able to tell that it was doing an ENDJRNPF (End Journal Physical File) as indicated by the QJOENDJN program in the call stack. It was also doing a CHGPF as indicated by the QDBCHGFI before the QJOENDJN. So what do ENDJRNPF and CHGPF have to do with seize problems? Well, I may not know the exact answer to that question, but at least I know what's happening, so now I can work with the appropriate people to determine how to fix this situation and prevent it from happening again.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020629.png

See how easy that was? As you can see from these examples, Job Watcher is a very powerful tool for solving your performance problems, particularly job waits and seize conditions. When you add in the Job Watcher monitor capabilities, it becomes even more powerful.

So how do you get started using Job Watcher? If you do not already have Job Watcher installed on your iSeries or i5 server, you can obtain a 45-day trial version by filling out and submitting a trial agreement form. For the trial agreement form, you must provide the serial number of your iSeries or i5 system and your OS/400 (i5/OS) version and release level.

After the form is submitted, you should receive a reply email within 24 hours that will contain
a temporary access code. The access code can be added either during the installation of Job Watcher or after Job Watcher has been installed. The access code must be entered before you can start a Job Watcher monitor or collection or analyze an existing Job Watcher collection that has been restored from another iSeries or i5 system.

Sandi Chromey is an Advisory IT/Architect with IBM Global Services. She provides iSeries performance support to both internal and external customers within IBM Global Services. Sandi has been with IBM for 24 years, with 13 of those years being in IT. She also has experience in iSeries development and component test.





Are performance problems on your iSeries causing you stressful days and sleepless nights? They aren't for me anymore. That's because I'm running the new Job Watcher monitor on my critical systems. I no longer worry about whether or not a performance problem occurs and whether or not I will be able to capture the necessary data. The Job Watcher monitor captures the data for me 24x7.

Let me tell you about Job Watcher. If you've never heard about Job Watcher, it's about time someone starts to spread the good news. Job Watcher is included under the iDoctor suite of tools. It's a great tool for detecting job waits, seizes, and other types of contention. Job Watcher allows you to watch a specific job, a set of jobs, or all the jobs on your system. Watching all the jobs on your system is especially useful when you aren't sure which jobs are having performance problems or when you just want an overview of how your entire system is performing.

Job Watcher returns real-time information, and you don't have to wait until all the data is collected before you start your analysis. You can start looking at the data almost immediately. The data is displayed in an easy-to-view graphical format. Job Watcher also gives you drill-down capability to determine the impact that a wait condition is having on the entire system or on a particular job. Even if you are not a performance expert and are not able to completely interpret the results, it will at least enable you to pinpoint a particular problem and lead you in the right direction to get additional assistance if needed. Job Watcher collects the data from the jobs, threads, and tasks you're watching in a manner that does not affect other jobs on the system while it is collecting, so it won't add to your performance problems.

As if Job Watcher didn't have enough great features, a Job Watcher monitor function has now been added (available for release V5R3 and above), which you can run 24x7 on your system. It includes all the great features of Job Watcher but gives you the added capability of running Job Watcher collections continuously rather than for just a specific period of time. I can't tell you how effective this has been in helping me solve a considerable number of performance problems and issues that I would not have been otherwise able to resolve.

Let me explain to you how it works and then give you some examples of how the Job Watcher monitor was able to help me resolve some performance problems. The Job Watcher monitors can be started via the GUI or by using traditional 5250 green-screen commands. Monitors must be manually ended; however, an IPL will also end a monitor. Monitors must be manually restarted after an IPL. We simply added code to our startup program by using the available green-screen commands to ensure that the monitors automatically restart after an IPL. The Job Watcher monitor will keep a predefined number of historical collections, and collections can overlap so no activity is lost.

After you've downloaded and installed Job Watcher, click on the iDoctor for iSeries icon on your desktop. This will automatically pick up any iSeries Navigator connections you already have established and display them.

If you don't have any connections or need to add a new one, right-click anywhere within the window and select Add Connection.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020600.png

Enter the name of your iSeries server and give a brief description (not required). Then click on OK to add the new connection to the list.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020601.png

In your list of connections, double-click on the system of your choice. This will bring up the sign-on display for the iSeries system. Your profile should automatically be displayed. Type in your password and press OK to get the list of iDoctor components that are currently installed on this particular system. Ensure that the Job Watcher component is highlighted and click on Launch or double-click on Job Watcher.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020602.png

This brings you to the main Job Watcher display.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020603.png

To start the monitors via the GUI, right-click on Job Watcher. Then select Work with Monitors.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020604.png


A new window is created where all previous Job Watcher monitors, active or not, will be listed. If no Job Watcher monitors are available on your system, the new window will be empty. In this example, one Job Watcher monitor, JOBWMON, is already active.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020605.png

Right-click anywhere in the new window and click on Start New Monitor. In this example, our system already has an active monitor. By right-clicking on the active monitor, you will get different options than if you right-click anywhere else in the new window. With an existing monitor, you can view the current collections, hold a monitor, end it immediately, end it after the current collection, or delete a monitor.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020606.png

Before starting a new monitor, you need to fill out a few details specific to your monitor. Give your monitor a name and decide which library you want the collected data to be stored in. In the example that follows, we will call our monitor JWMON, and we will store the collected data in library JWMONLIB.

How long do you want each collection to run? In this example, each collection will run for 60 minutes. How many collections do you want to keep? In this example, five historical collections will be kept. So in this example, you will be collecting data for one hour and keeping five of these collections as historical data. If there was a performance problem, you would be able to go back five hours in time. After five hours, the oldest collection is overlaid and new data is collected in its place. You have to decide if this is enough historical data for you to keep. If you typically have customers who don't call you for several hours or until the next day, maybe you want to keep more than five historical collections. This will allow you to go back further in time to resolve performance issues. Do you see where I'm going with this? On our more critical systems, I have two-hour collections and I keep 14 of these so I can go back 28 hours in time. This amount of data allows me to go back far enough to find the problem. Be aware that storing this much data takes a fair amount of DASD . However, we don't have a storage problem, so I am being allowed to keep this much data. In the future, though, this might not be the case.

In this example, there is a collection overlap of 30 seconds. So 30 seconds before the current collection ends, the new collection will start so you don't lose any data.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020607.png


You also need a Job Watcher definition. A definition gives Job Watcher the specific details of what you want collected. You can use an existing definition by clicking on View. If there are existing definitions, they will appear here. You can also create a new definition or use one that has been predefined. To create a new Job Watcher definition, you need to give it a name. In this example, we call our definition JWMONDEF.

Now, decide how long you want each of your individual collections to run. You can select up to 1440 minutes for your collection duration. You probably don't want your collections too large. This really depends on the size of your system. Very large systems can collect a large amount of data in a fairly short amount of time.

The interval duration is the amount of time in between the Job Watcher collection snapshots. The smaller the interval duration, the more information you will be able to collect and have available to you. If a seize or object lock only lasts for one second and you have your collection interval set to five seconds, you may miss it. So be sure to set your interval duration accordingly.

What other information do you want included? Make sure you include call stacks. This is one of the great features of Job Watcher and is especially useful when you are drilling down into a particular problem. You want to make sure you are including this information.

Include SQL statements if your users or applications typically use SQL functions. This will allow Job Watcher to capture the SQL statement (along with host variables) and you can view it later if you think the SQL statement is causing performance problems.

You can also include communications data if you want; however, currently there are no packaged Job Watcher queries, graphs, or reports related to communications data.

Force first interval means all jobs and tasks will be included in the first interval. Normally, only jobs and tasks that use CPU during an interval would be included. If you are starting Job Watcher when a problem is already in progress, it's a good idea to include idle jobs and tasks. But if you are starting Job Watcher prior to a problem occurring (for example, as a monitor), there is no need to include all jobs and tasks.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020608.png

These are some of the predefined iDoctor-supplied definitions. If you aren't sure how to set up your first monitor definition, try some of these and decide if they work for you. You can always change your monitor later using a different definition.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020609.png

If you have some existing Job Watcher monitor definitions already created and you can't remember the details, you can click on View. This will show you the details for an existing definition.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020610.png

Now, you are ready to start the monitor. Click on Start Monitor. If the library you specified does not exist, you will be prompted with the following message:

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020611.png

You will see the newly-created monitor with a status of Active.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020612.png

Right-click on the active JWMON monitor and select View Collections.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020613.png

This brings up the library that contains your stored collections.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020614.png

Double-click on the library name, JWMONLIB, to view the collections. Since we just started the monitor, there is only one collection available. Notice that this collection is called JWMON01. Subsequent collections will be named JWMON02, JWMON03, JWMON04, etc. After the maximum number of historical collections is reached, the oldest collection will be deleted and a new collection created.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020615.png

Double-click on JWMON01 to see the available graphs and output files.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020616.png

In this example, there are 13 historical collections with one current collection in progress. When JOBWMON50 is created, JOBWMON36 (the oldest collection) will be deleted.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020617.png

Several Job Watcher green-screen commands are available, and these can be found in library QIDRWCH.

  • ADDJWDFN—Add Job Watcher Definition
  • STRJWMON—Start a Job Watcher Monitor
  • HLDJWMON—Hold a Job Watcher Monitor
  • RLSJWMON—Release a Job Watcher Monitor
  • ENDJWMON—End a Job Watcher Monitor
  • RSTJWMON —Restore a Job Watcher Monitor
  • ENDJWCOL—End a Job Watcher Collection
  • DLTJWMON—Delete a Job Watcher Monitor

Now that your Job Watcher monitor is active and collecting data, you can relax, sit back, and let the performance problems begin. When your customer calls and says there was a problem at 1:00 this afternoon, you can confidently go to your Job Watcher collected data and start investigating. Unfortunately, without the Job Watcher monitor, you may have to tell your customer that the problem needs to reoccur before you can capture the right data. Don't get me wrong. The Performance Tools LPP (5722PT1) provides some great reports, and there are some other real-time performance commands—like WRKSYSACT (Work with System Activity), WRKACTJOB (Work with Active Jobs) and WRKSYSSTS (Work with System Status)—that can give you some great information. But no tool captures job waits, seizes, and other object contention like Job Watcher. So now that you know how to start your Job Watcher monitor, let me show you what it can do for you.

Job Watcher provides you with a large amount of graphs. If you don't know where to start, go to the Wait Graphs by Interval and click on Collection overview time signature. This graph gives you a good overview of what's happening on your system, and it's a very good starting place.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020618.png

One day as I was leisurely browsing through my Job Watcher collections, I started with the Collection overview time signature. This graph happened to show a high amount of DASD page faults (indicated by the light brown color in the graph). If you didn't already know this, you could look at the legend that is associated with the graph and displayed on the right side or use your mouse to fly over the graph and see the interval details. The customer hadn't reported any problems or issues; but because I was using the Job Watcher monitor, I was able to look through the data on my own time and at a relaxed pace.

In this example, each of the intervals is two seconds. So each bar you see here represents a two-second interval. You can set this collection interval to any value between .1 and 3600 seconds. But remember, the smaller the collection interval, the more detailed information you will be able to see. If a seize or object lock lasts for only one second and you have your collection interval set to five seconds, you may miss it.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020619.png

From this graph, I was able to drill down into any one of these different intervals by right-clicking on one of them and selecting DASD page faults graph by job.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020620.png

By drilling down into the collected Job Watcher data, I was able to see a list of all the jobs ranked by DASD page faults for that particular interval.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020621.png

From here, I was able to drill down even further into each one of these jobs by double-clicking on the horizontal bar graph following a particular job. By looking at this Interval Details screen, I was able to determine that each of these jobs with the highest DASD page faults was occurring in the same pool and the same subsystem.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020622.png


Upon further investigation on the iSeries system itself, I noticed that these jobs were running in a subsystem that had originally been set up with a private pool. This private pool size may have been sufficient in the past; however, the customer had recently been adding more and more jobs to this subsystem, and the size of the private pool was no longer big enough to handle the workload. I was able to change the pool for this subsystem to a shared pool (but not being used by any other subsystems), and the performance adjuster (system value QPFRADJ) was then able to adjust the size of the pool according to the workload. DASD page faults were drastically reduced. All of this was done proactively before the customer even detected or reported any type of slowdown or performance issue.

After the change was made, I was able to go back to my Job Watcher data and see the difference. As you can see from this graph, there are still some intervals with DASD page faults but they have been significantly reduced. Next problem, please.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020623.png

Here's where Job Watcher really shines. A problem was reported to me, and I was also given the timeframe in which the problem occurred. This helped me narrow my search through the collected data. I was able to go directly to the collection that occurred over this timeframe. Since I still wasn't sure what I was looking for, I went to the Wait graphs by interval and then clicked on the Collection overtime time signature graph. When I reached the problem timeframe, it was very obvious by looking at the Job Watcher data. The purple in this graph indicated a seize contention problem. In this example, you can see the problem started in interval 2179 and just continued to build.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020624.png

In this example, I drilled down into interval 2179 to see what was going on. I right-clicked on interval 2179 in the purple area and clicked on Seize contention graph by job.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020625.png

This gave me a list of the jobs ranked by seize contention. From here, I could drill down even further by double-clicking on any one of the horizontal bar graphs. In this example, I drilled down into the first job.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020626.png

This screen gave me all the details for this particular job during this interval (2179). You can see the job name, the subsystem and pool it was running in, priority, etc. It also showed me the Current or last wait, which was Seize: shared. This screen showed that the job was waiting on object AMFSRVC, and it also identified the holder of the object. If I didn't know what AMFSRVC was, I could click on the Object waited on tab, and it would show me the object type. In this case, it was a library. As I continued to look at the other jobs on the previous screen, I started to see a pattern. All the jobs were waiting on the same object, and it was being held by the same job.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020627.png

To further investigate, I clicked on the Call stack tab to see the call stack of the waiting job. In this example, the waiting job was opening a file, as indicated by QDMCOPEN.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020628.png

From here, I was able to look at the call stack of the holder job by clicking on Show Holder. From the call stack of the holding job, I was able to tell that it was doing an ENDJRNPF (End Journal Physical File) as indicated by the QJOENDJN program in the call stack. It was also doing a CHGPF as indicated by the QDBCHGFI before the QJOENDJN. So what do ENDJRNPF and CHGPF have to do with seize problems? Well, I may not know the exact answer to that question, but at least I know what's happening, so now I can work with the appropriate people to determine how to fix this situation and prevent it from happening again.

http://www.mcpressonline.com/articles/images/2002/Watch%20Your%20System%20with%20the%20New%20Job%20Watcher%20MonitorV4--08020629.png

See how easy that was? As you can see from these examples, Job Watcher is a very powerful tool for solving your performance problems, particularly job waits and seize conditions. When you add in the Job Watcher monitor capabilities, it becomes even more powerful.

So how do you get started using Job Watcher? If you do not already have Job Watcher installed on your iSeries or i5 server, you can obtain a 45-day trial version by filling out and submitting a trial agreement form. For the trial agreement form, you must provide the serial number of your iSeries or i5 system and your OS/400 (i5/OS) version and release level.

After the form is submitted, you should receive a reply email within 24 hours that will contain
a temporary access code. The access code can be added either during the installation of Job Watcher or after Job Watcher has been installed. The access code must be entered before you can start a Job Watcher monitor or collection or analyze an existing Job Watcher collection that has been restored from another iSeries or i5 system.

Sandi Chromey is an Advisory IT/Architect with IBM Global Services. She provides iSeries performance support to both internal and external customers within IBM Global Services. Sandi has been with IBM for 24 years, with 13 of those years being in IT. She also has experience in iSeries development and component test.





BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

RESOURCE CENTER

  • WHITE PAPERS

  • WEBCAST

  • TRIAL SOFTWARE

  • Mobile Computing and the IBM i

    SB ASNA PPL 5450Mobile computing is rapidly maturing into a solid platform for delivering enterprise applications. Many IBM i shops today are realizing that integrating their IBM i with mobile applications is the fast path to improved business workflows, better customer relations, and more responsive business reporting.

    This ASNA whitepaper takes a look at mobile computing for the IBM i. It discusses the different ways mobile applications may be used within the enterprise and how ASNA products solve the challenges mobile presents. It also presents the case that you already have the mobile programming team your projects need: that team is your existing RPG development team!

    Get your copy today!

  • Automate IBM i Operations using Wireless Devices

    DDL SystemsDownload the technical whitepaper on MANAGING YOUR IBM i WIRELESSLY and (optionally) register to download an absolutely FREE software trail. This whitepaper provides an in-depth review of the native IBM i technology and ACO MONITOR's advanced two-way messaging features to remotely manage your IBM i while in or away from the office. Notify on-duty personnel of system events and remotely respond to complex problems (via your Smartphone) before they become critical-24/7. Problem solved!

    Order your copy here.

  • DR Strategy Guide from Maxava: Brand New Edition - now fully updated to include Cloud!

    SB Maxava PPL 5476PRACTICAL TOOLS TO IMPLEMENT DISASTER RECOVERY IN YOUR IBM i ENVIRONMENT

    CLOUD VS. ON-PREMISE?
    - COMPREHENSIVE CHECKLISTS
    - RISK COST CALCULATIONS
    - BUSINESS CASE FRAMEWORK
    - DR SOLUTIONS OVERVIEW
    - RFP BUILDER
    Download your free copy of DR Strategy Guide for IBM i from Maxava today.

     

  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things


    Read Node.js for Enterprise IBM i Modernization Now!

     

  • 2020 IBM i Marketplace Survey Results

    HelpSystems

    This year marks the sixth edition of the popular IBM i Marketplace Survey Results. Each year, HelpSystems sets out to gather data about how businesses use the IBM i platform and the IT initiatives it supports. Year over year, the survey has begun to reveal long-term trends that give insight into the future of this trusted technology.

    More than 500 IBM i users from around the globe participated in this year’s survey, and we’re so happy to share the results with you. We hope you’ll find the information interesting and useful as you evaluate your own IT projects.

  • AIX Security Basics eCourse

    Core Security

    With so many organizations depending on AIX day to day, ensuring proper security and configuration is critical to ensure the safety of your environment. Don’t let common threats put your critical AIX servers at risk. Avoid simple mistakes and start to build a long-term plan with this AIX Security eCourse. Enroll today to get easy to follow instructions on topics like:

    • Removing extraneous files
    • Patching systems efficiently
    • Setting and validating permissions
    • Managing service considerations
    • Getting overall visibility into your networks

     

  • Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.

    Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    HelpSystemsIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact

     

  • IBM i Resources Retiring?

    SB HelpSystems WC GenericLet’s face it: IBM i experts and RPG programmers are retiring from the workforce. Are you prepared to handle their departure?
    Our panel of IBM i experts—Chuck Losinski, Robin Tatam, Richard Schoen, and Tom Huntington—will outline strategies that allow your company to cope with IBM i skills depletion by adopting these strategies that allow you to get the job done without deep expertise on the OS:
    - Automate IBM i processes
    - Use managed services to help fill the gaps
    - Secure the system against data loss and viruses
    The strategies you discover in this webinar will help you ensure that your system of record—your IBM i—continues to deliver a powerful business advantage, even as staff retires.

     

  • Backup and Recovery Considerations for Security Data and Encrypted Backups

    SB PowerTech WC GenericSecurity expert Carol Woodbury is joined by Debbie Saugen. Debbie is an expert on IBM i backup and recovery, disaster recovery, and high availability, helping IBM i shops build and implement effective business continuity plans.
    In today’s business climate, business continuity is more important than ever. But 83 percent of organizations are not totally confident in their backup strategy.
    During this webinar, Carol and Debbie discuss the importance of a good backup plan, how to ensure you’re backing up your security information, and your options for encrypted back-ups.

  • Profound.js: The Agile Approach to Legacy Modernization

    SB Profound WC GenericIn this presentation, Alex Roytman and Liam Allan will unveil a completely new and unique way to modernize your legacy applications. Learn how Agile Modernization:
    - Uses the power of Node.js in place of costly system re-writes and migrations
    - Enables you to modernize legacy systems in an iterative, low-risk manner
    - Makes it easier to hire developers for your modernization efforts
    - Integrates with Profound UI (GUI modernization) for a seamless, end-to-end legacy modernization solution

     

  • Data Breaches: Is IBM i Really at Risk?

    SB PowerTech WC GenericIBM i is known for its security, but this OS could be more vulnerable than you think.
    Although Power Servers often live inside the safety of the perimeter firewall, the risk of suffering a data leak or data corruption remains high.
    Watch noted IBM i security expert Robin Tatam as he discusses common ways that this supposedly “secure” operating system may actually be vulnerable and who the culprits might be.

    Watch the webinar today!

     

  • Easy Mobile Development

    SB Profound WC GenericWatch this on-demand webinar and learn how to rapidly and easily deploy mobile apps to your organization – even when working with legacy RPG code! IBM Champion Scott Klement will demonstrate how to:
    - Develop RPG applications without mobile development experience
    - Deploy secure applications for any mobile device
    - Build one application for all platforms, including Apple and Android
    - Extend the life and reach of your IBM i (aka iSeries, AS400) platform
    You’ll see examples from customers who have used our products and services to deliver the mobile applications of their dreams, faster and easier than they ever thought possible!

     

  • Profound UI: Unlock True Modernization from your IBM i Enterprise

    SB Profound PPL 5491Modern, web-based applications can make your Enterprise more efficient, connected and engaged. This session will demonstrate how the Profound UI framework is the best and most native way to convert your existing RPG applications and develop new modern applications for your business. Additionally, you will learn how you can address modernization across your Enterprise, including databases and legacy source code, with Profound Logic.

  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.

    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).

  • 5 New and Unique Ways to Use the IBM i Audit Journal

    SB HelpSystems ROBOT GenericYou must be asking yourself: am I doing everything I can to protect my organization’s data? Tune in as our panel of IBM i high availability experts discuss:


    - Why companies don’t test role swaps when they know they should
    - Whether high availability in the cloud makes sense for IBM i users
    - Why some organizations don’t have high availability yet
    - How to get high availability up and running at your organization
    - High availability considerations for today’s security concerns

  • Profound.js 2.0: Extend the Power of Node to your IBM i Applications

    SB Profound WC 5541In this Webinar, we'll demonstrate how Profound.js 2.0 enables you to easily adopt Node.js in your business, and to take advantage of the many benefits of Node, including access to a much larger pool of developers for IBM i and access to countless reusable open source code packages on npm (Node Package Manager).
    You will see how Profound.js 2.0 allows you to:

    • Provide RPG-like capabilities for server-side JavaScript.
    • Easily create web and mobile application interfaces for Node on IBM i.
    • Let existing RPG programs call Node.js modules directly, and vice versa.
    • Automatically generate code for Node.js.
    • Automatically converts existing RPGLE code into clean, simplified Node.js code.

    Download and watch today!

     

  • Make Modern Apps You'll Love with Profound UI & Profound.js

    SB Profound WC 5541Whether you have green screens or a drab GUI, your outdated apps can benefit from modern source code, modern GUIs, and modern tools.
    Profound Logic's Alex Roytman and Liam Allan are here to show you how Free-format RPG and Node.js make it possible to deliver applications your whole business will love:

    • Transform legacy RPG code to modern free-format RPG and Node.js
    • Deliver truly modern application interfaces with Profound UI
    • Extend your RPG applications to include Web Services and NPM packages with Node.js

     

  • Accelerating Programmer Productivity with Sequel

    SB_HelpSystems_WC_Generic

    Most business intelligence tools are just that: tools, a means to an end but not an accelerator. Yours could even be slowing you down. But what if your BI tool didn't just give you a platform for query-writing but also improved programmer productivity?
    Watch the recorded webinar to see how Sequel:

    • Makes creating complex results simple
    • Eliminates barriers to data sources
    • Increases flexibility with data usage and distribution

    Accelerated productivity makes everyone happy, from programmer to business user.

  • Business Intelligence is Changing: Make Your Game Plan

    SB_HelpSystems_WC_GenericIt’s time to develop a strategy that will help you meet your informational challenges head-on. Watch the webinar to learn how to set your IT department up for business intelligence success. You’ll learn how the right data access tool will help you:

    • Access IBM i data faster
    • Deliver useful information to executives and business users
    • Empower users with secure data access

    Ready to make your game plan and finally keep up with your data access requests?

     

  • Controlling Insider Threats on IBM i

    SB_HelpSystems_WC_GenericLet’s face facts: servers don’t hack other servers. Despite the avalanche of regulations, news headlines remain chock full of stories about data breaches, all initiated by insiders or intruders masquerading as insiders.
    User profiles are often duplicated or restored and are rarely reviewed for the appropriateness of their current configuration. This increases the risk of the profile being able to access data without the intended authority or having privileges that should be reserved for administrators.
    Watch security expert Robin Tatam as he discusses a new approach for onboarding new users on IBM i and best-practices techniques for managing and monitoring activities after they sign on.

  • Don't Just Settle for Query/400...

    SB_HelpSystems_WC_GenericWhile introducing Sequel Data Access, we’ll address common frustrations with Query/400, discuss major data access, distribution trends, and more advanced query tools. Plus, you’ll learn how a tool like Sequel lightens IT’s load by:

    - Accessing real-time data, so you can make real-time decisions
    - Providing run-time prompts, so users can help themselves
    - Delivering instant results in Microsoft Excel and PDF, without the wait
    - Automating the query process with on-demand data, dashboards, and scheduled jobs

  • How to Manage Documents the Easy Way

    SB_HelpSystems_WC_GenericWhat happens when your company depends on an outdated document management strategy?
    Everything is harder.
    You don’t need to stick with status quo anymore.
    Watch the webinar to learn how to put effective document management into practice and:

    • Capture documents faster, instead of wasting everyone’s time
    • Manage documents easily, so you can always find them
    • Distribute documents automatically, and move on to the next task

     

  • Lessons Learned from the AS/400 Breach

    SB_PowerTech_WC_GenericGet actionable info to avoid becoming the next cyberattack victim.
    In “Data breach digest—Scenarios from the field,” Verizon documented an AS/400 security breach. Whether you call it AS/400, iSeries, or IBM i, you now have proof that the system has been breached.
    Watch IBM i security expert Robin Tatam give an insightful discussion of the issues surrounding this specific scenario.
    Robin will also draw on his extensive cybersecurity experience to discuss policies, processes, and configuration details that you can implement to help reduce the risk of your system being the next victim of an attack.

  • Overwhelmed by Operating Systems?

    SB_HelpSystems_WC_GenericIn this 30-minute recorded webinar, our experts demonstrate how you can:

    • Manage multiple platforms from a central location
    • View monitoring results in a single pane of glass on your desktop or mobile device
    • Take advantage of best practice, plug-and-play monitoring templates
    • Create rules to automate daily checks across your entire infrastructure
    • Receive notification if something is wrong or about to go wrong

    This presentation includes a live demo of Network Server Suite.

     

  • Real-Time Disk Monitoring with Robot Monitor

    SB_HelpSystems_WC_GenericYou need to know when IBM i disk space starts to disappear and where it has gone before system performance and productivity start to suffer. Our experts will show you how Robot Monitor can help you pinpoint exactly when your auxiliary storage starts to disappear and why, so you can start taking a proactive approach to disk monitoring and analysis. You’ll also get insight into:

    • The main sources of disk consumption
    • How to monitor temporary storage and QTEMP objects in real time
    • How to monitor objects and libraries in real time and near-real time
    • How to track long-term disk trends

     

     

  • Stop Re-keying Data Between IBM I and Other Applications

    SB_HelpSystems_WC_GenericMany business still depend on RPG for their daily business processes and report generation.Wouldn’t it be nice if you could stop re-keying data between IBM i and other applications? Or if you could stop replicating data and start processing orders faster? Or what if you could automatically extract data from existing reports instead of re-keying? It’s all possible. Watch this webinar to learn about:

    • The data dilemma
    • 3 ways to stop re-keying data
    • Data automation in practice

    Plus, see how HelpSystems data automation software will help you stop re-keying data.

     

  • The Top Five RPG Open Access Myths....BUSTED!

    SB_Profound_WC_GenericWhen it comes to IBM Rational Open Access: RPG Edition, there are still many misconceptions - especially where application modernization is concerned!

    In this Webinar, we'll address some of the biggest myths about RPG Open Access, including:

    • Modernizing with RPG OA requires significant changes to the source code
    • The RPG language is outdated and impractical for modernizing applications
    • Modernizing with RPG OA is the equivalent to "screen scraping"

     

  • Time to Remove the Paper from Your Desk and Become More Efficient

    SB_HelpSystems_WC_GenericToo much paper is wasted. Attempts to locate documents in endless filing cabinets.And distributing documents is expensive and takes up far too much time.
    These are just three common reasons why it might be time for your company to implement a paperless document management system.
    Watch the webinar to learn more and discover how easy it can be to:

    • Capture
    • Manage
    • And distribute documents digitally

     

  • IBM i: It’s Not Just AS/400

    SB_HelpSystems_WC_Generic

    IBM’s Steve Will talks AS/400, POWER9, cognitive systems, and everything in between

    Are there still companies that use AS400? Of course!

    IBM i was built on the same foundation.
    Watch this recorded webinar with IBM i Chief Architect Steve Will and IBM Power Champion Tom Huntington to gain a unique perspective on the direction of this platform, including:

    • IBM i development strategies in progress at IBM
    • Ways that Watson will shake hands with IBM i
    • Key takeaways from the AS/400 days

     

  • Ask the RDi Experts

    SB_HelpSystems_WC_GenericWatch this recording where Jim Buck, Susan Gantner, and Charlie Guarino answered your questions, including:

    • What are the “hidden gems” in RDi that can make me more productive?
    • What makes RDi Debug better than the STRDBG green screen debugger?
    • How can RDi help me find out if I’ve tested all lines of a program?
    • What’s the best way to transition from PDM to RDi?
    • How do I convince my long-term developers to use RDi?

    This is a unique, online opportunity to hear how you can get more out of RDi.

     

  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using NodeRun.com as a pre-built development environment

     

     

  • Inside the Integrated File System (IFS)

    SB_HelpSystems_WC_GenericDuring this webinar, you’ll learn basic tips, helpful tools, and integrated file system commands—including WRKLNK—for managing your IFS directories and Access Client Solutions (ACS). We’ll answer your most pressing IFS questions, including:

    • What is stored inside my IFS directories?
    • How do I monitor the IFS?
    • How do I replicate the IFS or back it up?
    • How do I secure the IFS?

    Understanding what the integrated file system is and how to work with it must be a critical part of your systems management plans for IBM i.

     

  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.

     

     

  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • How to Meet the Newest Encryption Requirements on IBM i

    SB PowerTech WC GenericA growing number of compliance mandates require sensitive data to be encrypted. But what kind of encryption solution will satisfy an auditor and how can you implement encryption on IBM i? Watch this on-demand webinar to find out how to meet today’s most common encryption requirements on IBM i. You’ll also learn:

    • Why disk encryption isn’t enough
    • What sets strong encryption apart from other solutions
    • Important considerations before implementing encryption

     

     

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.

     

     

  • Fight Cyber Threats with IBM i Encryption

    SB PowerTech WC GenericCyber attacks often target mission-critical servers, and those attack strategies are constantly changing. To stay on top of these threats, your cybersecurity strategies must evolve, too. In this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

     

     

     

  • 10 Practical IBM i Security Tips for Surviving Covid-19 and Working From Home

    SB PowerTech WC GenericNow that many organizations have moved to a work from home model, security concerns have risen.

    During this session Carol Woodbury will discuss the issues that the world is currently seeing such as increased malware attacks and then provide practical actions you can take to both monitor and protect your IBM i during this challenging time.

     

  • How to Transfer IBM i Data to Microsoft Excel

    SB_HelpSystems_WC_Generic3 easy ways to get IBM i data into Excel every time
    There’s an easy, more reliable way to import your IBM i data to Excel? It’s called Sequel. During this webinar, our data access experts demonstrate how you can simplify the process of getting data from multiple sources—including Db2 for i—into Excel. Watch to learn how to:

    • Download your IBM i data to Excel in a single step
    • Deliver data to business users in Excel via email or a scheduled job
    • Access IBM i data directly using the Excel add-in in Sequel

    Make 2020 the year you finally see your data clearly, quickly, and securely. Start by giving business users the ability to access crucial business data from IBM i the way they want it—in Microsoft Excel.

     

     

  • HA Alternatives: MIMIX Is Not Your Only Option on IBM i

    SB_HelpSystems_WC_GenericIn this recorded webinar, our experts introduce you to the new HA transition technology available with our Robot HA software. You’ll learn how to:

    • Transition your rules from MIMIX (if you’re happy with them)
    • Simplify your day-to-day activities around high availability
    • Gain back time in your work week
    • Make your CEO happy about reducing IT costs

    Don’t stick with a legacy high availability solution that makes you uncomfortable when transitioning to something better can be simple, safe, and cost-effective.

     

     

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    SB HelpSystems SC 5413Robot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    SB HelpSystems SC 5413Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.

  • ACO MONITOR Manages your IBM i 24/7 and Notifies You When Your IBM i Needs Assistance!

    SB DDL Systems 5429More than a paging system - ACO MONITOR is a complete systems management solution for your Power Systems running IBM i. ACO MONITOR manages your Power System 24/7, uses advanced technology (like two-way messaging) to notify on-duty support personnel, and responds to complex problems before they reach critical status.

    ACO MONITOR is proven technology and is capable of processing thousands of mission-critical events daily. The software is pre-configured, easy to install, scalable, and greatly improves data center efficiency.