Don't swap an archiving issue for a storage issue. QMessage Monitor notifies you if files grow too large—and can take action before storage becomes a problem.
A proactive approach to system monitoring offers many benefits, but there still are tasks that, despite your best efforts in making proactive choices, ultimately swap one problem for another. A good example is message archiving. Archiving messages from the message log in QMessage Monitor (QMM) using the MMARCLOG command is a great way to maintain your message history, allowing you to export parts of the log into separate files. However, if ignored, the number of these files on IBM i can grow substantially, possibly causing an issue with the space they use.
Not to worry! You can easily create an Object Count monitor in QSystem Monitor (QSM) V13, which will notify you when the number of files is reaching a limit that you define. To create the Object Count monitor, follow the steps below.
Step 1: Open or create an All Systems view window.
Figure 1: Here's an example of the All Systems view window.
Step 2: Right-click in the All Systems view window and select Group > Properties for Bar Group.
Figure 2: You'll find the Properties for Bar Group option in the Group dropdown menu.
Step 3: From the Bar Group Properties window, select Data Selection, and click the Add button. With Data Collection highlighted, select Object Count in the Monitor Type dropdown box. Fill in the parameter fields as follows:
Object Name—LA*
Library Name—MM (MM installed library name)
Object Type—*File
Click OK to populate the All Systems window with the new Object Count monitor.
Figure 3: Create the Object Count monitor.
Figure 4: Your new Object Count monitor is in the All Systems view.
Step 4: Create a Global Threshold for the new Object Count monitor.
With your mouse positioned over one of the new Object Count bars, right-click and select Change LA* Properties, which opens the Data Definition window. Select Global Threshold from the left column and click Create a Copy. Highlight the Default Threshold for Object Count and click OK.
Figure 5: Create a Global Threshold for the new Object Count monitor.
Step 5: Modify the Default Threshold Description and Values.
Modify the description field at the top to be more meaningful (such as LA* Files in Library MM - Global Threshold). Now, modify the Value fields at the bottom, starting with the Default Threshold. Double-click the No Threshold value, which opens the Threshold Detail Record box. Make the following changes:
Short Translation—&v
Long Translation—Number of LA* files in &2 library on &S is &v
Click OK.
Figure 6: The Default Threshold has been modified.
Step 6: Create a copy of the Default Threshold to become your new Global Threshold.
The threshold you create now will be the one to alert and notify you whenever the number of QMM Archive files (LA*) has exceeded the number you'll define in the following steps:
Right-click the No Threshold value that you modified in the previous step, select Copy, and click OK.
Figure 7: The Default Threshold becomes the new Global Threshold.
The Threshold Detailed Record box is presented, allowing you to define the new record with the following changes:
Value—XX (The number of MM archive files that you want to trigger the alert)
Severity—XX (The higher the severity number, the worse the situation is. The monitor uses severity to make decisions, such as which threshold to display when multiple thresholds are selected in a group and which elements to display when filtering is being used.)
Color—The Color button allows you to select a color to make it something distinguishable.
Short Translation—&v
Long Translation—Number of LA* files in &2 library on &S is &v
Send Message on iSeries—Checking this box causes the monitor program to send a MON0079 message to message queues MONTHR and MONTHRLC.
Click OK twice after making those changes.
Figure 8: This is the process of defining the new record with changes.
You'll see the modified All Systems view with the new Object Count monitors on the right, showing that the number of QMM Archive Files has exceeded the user-defined value.
Figure 9: The All Systems view with new Object Count monitor shows that your threshold has been exceeded.
Ready to set up your Object Count monitor? Request a free trial of QSystem Monitor and QMessage Monitor to ensure your archiving issues don't turn into storage nightmares.
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
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. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) 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:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? 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:
LATEST COMMENTS
MC Press Online