Looking behind the curtain to keep a close eye on disk space—especially in a multi-partition environment—can have its challenges, but every good admin can have an ace up their sleeve.
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
2. HelpSystems LLC. All rights reserved.
YOUR HOSTS
Chuck Losinski
Director of Automation Technology
HelpSystems
Broadcasting live from Eden Prairie in Minnesota USA
Sara Williams
System Engineer
HelpSystems
3. HelpSystems LLC. All rights reserved.
SUITE OF MONITORING WEBINARS
Stop Feeding IBM i Performance Hogs
SQL Based Monitoring
Real Time Disk Monitoring for IBM i
IBM i Monitoring by the Dashboard Light
4. HelpSystems LLC. All rights reserved.
with Robot Monitor
REAL-TIME DISK MONITORING
5. HelpSystems LLC. All rights reserved.
Hot-shot system administrators!
DISK SPACE INVESTIGATORS
6. HelpSystems LLC. All rights reserved.
A little bit stressed when disk space disappears...
DISK SPACE INVESTIGATORS
7. HelpSystems LLC. All rights reserved.
AGENDA
• What Is Consuming Disk Space?
• What Does Robot Monitor Check?
• How Will You Get Notified?
• Live Demo
• Tips
8. HelpSystems LLC. All rights reserved.
It can be a mystery
WHERE DOES DISK SPACE GO?
9. HelpSystems LLC. All rights reserved.
And where you need to look..
• Objects in libraries
• Files in IFS
• QTEMP
• Temporary storage
• Spooled files (reports)
WHERE DISK SPACE GOES
11. HelpSystems LLC. All rights reserved.
LARGEST LIBARIES AND OBJECTS
Robot Monitor checks every few minutes rather than once per day (or never)!
12. HelpSystems LLC. All rights reserved.
Other targeted objects
• Focus on a single object in a library
• Focus on journal receivers for a particular journal (think HA)
• Disk space used by QTEMP objects
• Disk space used by temporary storage
• Number of spooled files in an output queue (think QEZJOBLOG)
YOUR DISK, IN REAL TIME, ALL PARTITIONS
13. HelpSystems LLC. All rights reserved.
Notification
YOUR DISK, IN REAL TIME, ALL PARTITIONS
14. HelpSystems LLC. All rights reserved.
Easy setup
YOUR DISK, IN REAL TIME, ALL PARTITIONS
15. HelpSystems LLC. All rights reserved.
Libraries and directories once per day
DISK SPACE ANALYSIS
16. HelpSystems Corporate Overview. All rights reserved.
• Types of disk space monitoring
• Setup
• Exception notification
• Analysis
LIVE DEMO
17. HelpSystems LLC. All rights reserved.
“Someday…all this will be so easy..”
NOW I’VE GOT ROBOT MONITOR
19. HelpSystems LLC. All rights reserved.
RECAP
Questions, comments, suggestions?
• What Is Consuming Disk Space?
• What Does Robot Monitor Check?
• How Will You Get Notified?
• Live Demo
• Tips
20. HelpSystems LLC. All rights reserved.
Thank you for attending!
Contact Information
Website:
www.helpsystems.com
Telephone:
800-328-1000 sales
+1 952-933-0609 support
Presenters:
chuck.losinski@helpsystems.com
sara.williams@helpsystems.com
Editor's Notes
Intro: Chuck
Load polling question
Setup: Academy/Wisdom Rmonitor GUI, Green screen to both systems.
Copy file chuck/datamart into QTEMP
Chuck has introduction; Include that his is the first in a series of Robot Monitor performance monitoring webinars!
Chuck has introduction; Include that his is the first in a series of Robot Monitor performance monitoring webinars!
More introduction
Reminds me of a 1980’s cop show with Angie Dickenson or Mike Sellek. Chuck and Sara!
Is this you? the disk space sleuth running reports, spreadsheets and running PRTDSKINF reports to determine where your disk space went?
OPEN POLLING QUESTION HERE
What are the main uses for disk space in an IBM i environment?
If you leave out some of the stuff “on the side”—such as the space used by the Licensed Internal Code itself, main storage dumps, and so on—you arrive at a picture like this. Mind you, the size of each component you see here varies greatly between systems. But, in our experience, these are the main consumers of disk space:
Objects in libraries, so your normal old files, journal receivers, program objects and so on
Streamfiles in the IFS
Temporary storage
And spooled files.
Let’s take a closer look at these…
1. This one is the easiest to understand. Objects in libraries, so your normal physical and logical files & tables, journal receivers, program objects and so on, residing in normal libraries. Of course they use … disk space.
2. Streamfiles in the integrated file system or IFS. This is where image files, java apps, web data, and so on is stored. This area can be a real black hole for most administrators.
3. Objects in QTEMP libraries. Each job has its own QTEMP library. The objects in QTEMP libraries are normal objects except when the job ends, they are all deleted. Objects in QTEMPs use up space like any other object, but it is a lot trickier to find out how much disk space they use.
4. Temporary storage. This isn’t the same as objects in QTEMP. It is not even “objects” in the usual sense. Temporary storage is just storage that has been allocated by a job. For instance if a C++ program does an “allocate”, then that causes temporary storage to be allocated for the job. Or if a Java program uses its heap space, it is using temporary storage. (also IBM has released a lot of PTFs for temporary storage problems in IBM i itself.)
5. And spooled files. Spooled files in output queues and are very useful to end users and a big pain to system operators . Do users ever delete the spooled files they no longer use? Very rarely! In many cases, users are not even aware that old spooled files still exist.
CHUCK
Many of the monitors that come with Robot Monitor help you track, identify and remediate disk space challenges. Today we’ll speak to a few of them and show you how they work.
SHARE POLLING RESULTS
Focus on a single object in a library.
Focus in journal receivers for your HA tool.
Focus on QTEMP objects for batch processes.
Focus on number of spool files across your applications out queues.
And get notified if there is a storage or other issue with IBMi.
Setting up monitors and notification across multiple partitions is a real breeze.
Also Rmonitor does a once per day disk summary of library and IFS storage so you’ll see where you are now, yesterday, last week, last month or as long as you want to keep the statistics. The stats are a summary for each library and directory.
Start with:
An overview of what Rmonitor does, architecture (Academy, Production, All Systems)
Dashboard contents
Grouping monitors together, hierarchy
Largest Libraries, with Show Details
Show how you can investigate library growth using disk summary.
Largest Objects, with Show Details (MMLOGP record count– ADD to root/SHOW thresholds)
Journal Receiver Size
Show targeting particular objects QAUDJRN *JRNRCV in QGPL. Show all of a particular journal receiver (THINK HA!!!)
QTEMP Object Size, copying a large object to my session’s QTEMP (SHOW DETAILS)
Temp Storage, letting a job allocate 2GB of temp storage (program ALLOC in lib THOMASK on USCCS003), showing it in the Monitor, and causing an escalation; consider escalating out to emails of attendants
High Disk I/O Jobs view (but for the temp storage example); in some cases, this can be an indication of jobs eating up disk storage
“One day in the future, I don’t know when, but I am sure it will happen, you know, technology will catch up and then we will be able to find out what is going on with the disk and which application is doing this.”
Ananshee says:
Mike and Ananshee are chatting about their daily work, and Mike is saying:
Seed questions:
How can you be notified of an object exceeding a certain size.
Are there IFS monitoring options?
How often will the top 10 libraries and objects be checked?
Can the dashboard contain disk metrics from multiple systems?