OMEGAMON XE for OS/400 User's Guide, Version...

User’s GuideOMEGAMON® XE for OS/400

Version 300

GC32-9314-00

March 2002

Candle Corporation201 North Douglas Street

El Segundo, California 90245

2 OMEGAMON XE for OS/400 User’s Guide, Version 300

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/PERFORMER, AF/REMOTE, Availability Command Center, Candle, Candle Command Center, Candle Direct logo, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, Candle Technologies, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CT, CT/Data Server, CT/DS, DELTAMON, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness Institute, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW, OMEGAVIEW II, PQEdit, Solutions for Networked Applications, Solutions for Networked Businesses, and Transplex.Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, Candle CIRCUIT, Candle eDelivery, CandleLight, CandleNet, CandleNet 2000, CandleNet Command Center, CandleNet eBP, CandleNet eBP Access, CandleNet eBP Administrator, CandleNet eBP Broker Access, CandleNet eBP Configuration, CandleNet eBP Connector, CandleNet eBP File Transfer, CandleNet eBP Host Connect, CandleNet eBP Object Access, CandleNet eBP Object Browser, CandleNet eBP Secure Access, CandleNet eBP Service Directory, CandleNet eBP Universal Connector, CandleNet eBP Workflow Access, CandleNet eBusiness Assurance, CandleNet eBusiness Exchange, CandleNet eBusiness Platform, CandleNet eBusiness Platform Administrator, CandleNet eBusiness Platform Connector, CandleNet eBusiness Platform Connectors, CandleNet eBusiness Platform Powered by Roma Technology, CandleNet eBusiness Platform Service Directory, CandleNet Portal, CCC, CCP, CEBA, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW, Command & Control, Connect-Notes, Connect-Two, CSA ANALYZER, CT/ALS, CT/Application Logic Services, CT/DCS, CT/Distributed Computing Services, CT/Engine, CT/Implementation Services, CT/IX, CT/Workbench, CT/Workstation Server, CT/WS, �DB Logo, �DB/DASD, �DB/EXPLAIN, �DB/MIGRATOR, �DB/QUICKCHANGE, �DB/QUICKCOMPARE, �DB/SMU, �DB/Tools, �DB/WORKBENCH, Design Network, DEXAN, e2e, eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo, eBusiness Exchange, eBusiness Institute, eBX, End-to-End, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation, Enterprise Reporter Plus, EPILOG, ER+, ERPNet, ESRA, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, MessageMate, Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NetGlue, NetGlue Extra, NetMirror, NetScheduler, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON Management Center, OSM, PC COMPANION, Performance Pac, PowerQ, PQConfiguration, PQScope, Response Time Network, Roma, Roma Application Manager, Roma Broker, Roma BSP, Roma Connector, Roma Developer, Roma FS/A, Roma FS/Access, RomaNet, Roma Network, Roma Object Access, Roma Secure, Roma WF/Access, Roma Workflow Access, RTA, RTN, SentinelManager, Somerset, Somerset Systems, Status Monitor, The Millennium Alliance, The Millennium Alliance logo, The Millennium Management Network Alliance, TMA2000, Tracer, Unified Directory Services, Volcano and ZCopy.Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere are registered trademarks of International Business Machines Corporation. SAP is a registered trademark and R/3 is a trademark of SAP AG. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd. HP-UX is a trademark of Hewlett-Packard Company. SunOS is a trademark of Sun Microsystems, Inc. All other company and product names used herein are trademarks or registered trademarks of their respective companies.

Copyright © March 2002, Candle Corporation, a California corporation. All rights reserved. International rights secured.

Threaded Environment for AS/400, Patent No. 5,504,898; Data Server with Data Probes Employing Predicate Tests in Rule Statements (Event Driven Sampling), Patent No. 5,615,359; MVS/ESA Message Transport System Using the XCF Coupling Facility, Patent No. 5,754,856; Intelligent Remote Agent for Computer Performance Monitoring, Patent No. 5,781,703; Data Server with Event Driven Sampling, Patent No. 5,809,238; Threaded Environment for Computer Systems Without Native Threading Support, Patent No. 5,835,763; Object Procedure Messaging Facility, Patent No. 5,848,234; End-to-End Response Time Measurement for Computer Programs, Patent No. 5,991,705; Communications on a Network, Patent Pending; Improved Message Queuing Based Network Computing Architecture, Patent Pending; User Interface for System Management Applications, Patent Pending.

NOTICE: This documentation is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions set forth in the applicable license agreement and/or the applicable government rights clause.This documentation contains confidential, proprietary information of Candle Corporation that is licensed for your internal use only. Any unauthorized use, duplication, or disclosure is unlawful.

Contents 3

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Contents of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . 12

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Chapter 1. Introducing OMEGAMON XE for OS/400 . . . . . . . . . . . . . . . . 17OMEGAMON XE for OS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Features of OMEGAMON XE for OS/400 . . . . . . . . . . . . . . . . . . . . . 22

Chapter 2. OMEGAMON XE for OS/400 Attributes. . . . . . . . . . . . . . . . . . 27Using Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Types of Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Accounting Journal (OS400_Acct_Jrn) Attributes . . . . . . . . . . . . . . . 39Alert Notification (OS400_Alert) Attributes . . . . . . . . . . . . . . . . . . . . 45Communications (OS400_Comm) Attributes. . . . . . . . . . . . . . . . . . . 50Controller Description (OS400_Controller) Attributes . . . . . . . . . . . . 71Database Member (OS400_DB_Member) Attributes . . . . . . . . . . . . . 74Device Description (OS400_Device) Attributes . . . . . . . . . . . . . . . . . 78Disk Unit (OS400_Disk_Unit) Attributes . . . . . . . . . . . . . . . . . . . . . . 82I/O Processor (OS400_I/O_Processor) Attributes . . . . . . . . . . . . . . . . 87Job (OS400_Job) and Job Queue (OS400_Job_Queue) Attributes . . 90Line Description (OS400_Line) Attributes . . . . . . . . . . . . . . . . . . . . 109Message (OS400_Message) Attributes . . . . . . . . . . . . . . . . . . . . . . . 112Tips and Techniques for Using the OS/400 Message Attributes . . . . 117Network (OS400_Network) Attributes . . . . . . . . . . . . . . . . . . . . . . . 121

Contents


Object (OS400_Object) Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 127Storage Pool (OS400_Storage_Pool) Attributes . . . . . . . . . . . . . . . . 137Subsystem (OS400_Subsystem) Attributes . . . . . . . . . . . . . . . . . . . 142Security Journal (OS400_Security_Jrn) Attributes . . . . . . . . . . . . . . 146Authority Failure (AuthFail) Journal Entries . . . . . . . . . . . . . . . . . . . 149General Security (AuditJrn) Attributes . . . . . . . . . . . . . . . . . . . . . . . 154Change Authority (ChgAuth) Journal Entries . . . . . . . . . . . . . . . . . 156User Profile Change (CP) Journal Entries . . . . . . . . . . . . . . . . . . . . 161Job Description (JobDesc) Attributes . . . . . . . . . . . . . . . . . . . . . . . . 164Network Attribute Change (Network) Journal Entries . . . . . . . . . . . 166Ownership Change (ChgOwner) Journal Entries . . . . . . . . . . . . . . . 169Program Adopt (ProgAdopt) Journal Entries . . . . . . . . . . . . . . . . . . 171Profile Swap (ProfSwap) Journal Entries . . . . . . . . . . . . . . . . . . . . . 173Password (Password) Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . 175Restoring Job Description (RestoreJob) Journal Entries. . . . . . . . . . 177Restoring Program (RestoreProg) Journal Entries . . . . . . . . . . . . . . 179System Value (SYSVAL) Journal Entries . . . . . . . . . . . . . . . . . . . . . 181Spool File (OS400_Spool_File) Attributes . . . . . . . . . . . . . . . . . . . . 183System Status (OS400_System_Status) Attributes . . . . . . . . . . . . . . 189System Values (OS400_System_Values) Attributes . . . . . . . . . . . . . 191End Notes for Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Chapter 3. OMEGAMON XE for OS/400 Product-provided Solutions . . .217Understanding Product-provided Solutions . . . . . . . . . . . . . . . . . . . 218OMEGAMON XE for OS/400 Product-provided Solutions . . . . . . . 219

Chapter 4. Using OMEGAMON XE for OS/400 Predefined Workspaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225OMEGAMON XE for OS/400 Predefined Workspaces. . . . . . . . . . . 226Using CandleNet Portal to Work with Predefined Workspaces . . . . . 227Types of Information Available for OMEGAMON XE for OS/400 . . 234If You Are a CMW User Who is Learning to Use CandleNet Portal . 238

Chapter 5. Other Features and Considerations . . . . . . . . . . . . . . . . . . . . .247About CandleNet Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Exploring Other Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Contents 5

OMEGAMON XE for OS/400 Performance Considerations . . . . . . . 251Performance Overhead When Monitoring for Situations . . . . . . . . . 254Maintaining OMEGAMON XE for OS/400 Performance . . . . . . . . . 256Performance Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Monitoring for Files that Are Inactive . . . . . . . . . . . . . . . . . . . . . . . . 260Tuning QAUTOMON Subsystem Jobs. . . . . . . . . . . . . . . . . . . . . . . 264Attribute Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Appendix A. Guide to Candle Customer Support . . . . . . . . . . . . . . . . . . . .269Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Customer Support Contact Information. . . . . . . . . . . . . . . . . . . . . . 278

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279


List of Tables 7

Table 1. Contents of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Table 2. Examples of Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Table 3. Attribute Location and Operational Area . . . . . . . . . . . . . . . . . . . . . . 35Table 4. Commands owned by QSYS with *PUBLIC *EXCLUDE . . . . . . . . . 38Table 5. QUADLVL Values and Entry Types . . . . . . . . . . . . . . . . . . . . . . . . . 146Table 6. Valid Numeric Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Table 7. Codes Returned When Jobs are Running . . . . . . . . . . . . . . . . . . . . 214Table 8. Definition of Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Table 9. Tabs for Changing Properties in CandleNet Portal . . . . . . . . . . . . . . 232

Table 10. Relationship of the Icons to Items in the Navigator . . . . . . . . . . . . . 239Table 11. Comparison of Tasks in the CMW and CandleNet Portal . . . . . . . . . 240Table 12. Relationship of Reports to Predefined Workspaces . . . . . . . . . . . . . 241Table 13. Performance Impact by Attribute Group . . . . . . . . . . . . . . . . . . . . . 254

List of Tables


Preface 9

Preface

Introduction

This user’s guide introduces you to the OMEGAMON® XE for OS/400. An agent supports a specific platform environment. This guide describes the attribute groups, attributes, predefined workspaces, and product-provided solutions for OMEGAMON XE for OS/400. This guide is designed to help you

� understand the CandleNet Command Center™ (CCC) environment and how OMEGAMON XE for OS/400 works in the environment

� anticipate and detect problems in using your database management application

� access specific information about events in your environment

This guide is designed to help you understand the OMEGAMON XE for OS/400 and how the agent works with CandleNet Portal™.

Who should use this guideThis guide serves the following audiences.

� database administrators

� operators

� system administrators

� network administrators

� Candle sales force and field support

P

Contents of This Guide


Contents of This Guide

OverviewThis unit describes the contents of each major section of this guide. Use the following table to understand the organization and contents of this guide.

Table 1. Contents of This Guide

Chapter Name Content

“Introducing OMEGAMON XE for OS/400” on page 17

This chapter introduces the features of the OMEGAMON XE for OS/400 and how this product can enhance the performance of your system.

“OMEGAMON XE for OS/400 Attributes” on page 27

This chapter provides the definitions and values for the attributes used in OMEGAMON XE for OS/400.

“OMEGAMON XE for OS/400 Product-provided Solutions” on page 217

This chapter describes how you can use product-provided solutions to begin monitoring your system (such as the situations provided with the CCC interface you are using). Additionally, this chapter lists names and descriptions of the situations provided with the CCC interface you are using.

“Using OMEGAMON XE for OS/400 Predefined Workspaces” on page 225

This chapter describes the OMEGAMON XE for OS/400 the predefined workspaces provided with CandleNet Portal

This chapter also contains instructions for working with predefined workspaces.

“Other Features and Considerations” on page 247

This chapter explores additional features of OMEGAMON XE for OS/400 including� historical data collection� simple automation or “Take Action”

Preface 11

Documentation Set

Documentation Set

IntroductionCandle provides a complete set of documentation for OMEGAMON XE for OS/400. Each manual in this documentation set contains a specific type of information to help you use the product.

In addition to this OMEGAMON XE for OS/400 User’s Guide, you should refer to the following documents that provide information for the CandleNet Command Center:

� Administering OMEGAMON Products: CandleNet Portal

Provides information about administering CandleNet Portal.

� Candle Management Workstation Administrator’s Guide

Provides detailed instructions for setting up the Candle Management Workstation to permit users to monitor their enterprise.

Also, refer to the online help for CandleNet Portal.

Comments Candle welcomes your comments and suggestions for changes or additions to the documentation set. A user comment form, located at the back of each manual, provides simple instructions for communicating with the Candle Information Development department.

Ordering additional product documentationTo order additional product manuals, contact your Candle Support Services representative.

Adobe Portable Document Format



Printing this bookCandle supplies documentation in the Adobe Portable Document Format (PDF). The Adobe Acrobat Reader will print PDF documents with the fonts, formatting, and graphics in the original document. To print a Candle document, do the following:

1. Specify the print options for your system. From the Acrobat Reader Menu bar, select File > Page Setup… and make your selections. A setting of 300 dpi is highly recommended as is duplex printing if your printer supports this option.

2. To start printing, select File > Print... on the Acrobat Reader Menu bar.

3. On the Print pop-up, select one of the Print Range options for� All� Current page� Pages from: [ ] to: [ ]

4. (Optional). Select the Shrink to Fit option if you need to fit oversize pages to the paper size currently loaded on your printer.

Printing problems?The print quality of your output is ultimately determined by your printer. Sometimes printing problems can occur. If you experience printing problems, potential areas to check are:� settings for your printer and printer driver. (The dpi settings for both your

driver and printer should be the same. A setting of 300 dpi is recommended.)

� the printer driver you are using. (You may need a different printer driver or the Universal Printer driver from Adobe. This free printer driver is available at www.adobe.com.)

� the halftone/graphics color adjustment for printing color on black and white printers (check the printer properties under Start > Settings > Printer). For more information, see the online help for the Acrobat Reader.

� the amount of available memory in your printer. (Insufficient memory can cause a document or graphics to fail to print.)

For additional information on printing problems, refer to the documentation for your printer or contact your printer manufacturer.

Preface 13


Contacting AdobeIf additional information is needed about Adobe Acrobat Reader or printing problems, see the Readme.pdf file that ships with Adobe Acrobat Reader or contact Adobe at www.adobe.com.

http://www.adobe.com





What’s New 15

What’s New

IntroductionThis section details the enhancements for the Version 300 of OMEGAMON XE for OS/400.

Candle monitoring agents have a new name Candle's intelligent monitoring agents that comprise the OMEGAMON XE suite of products and use the CandleNet Portal user interface have been renamed. You will see the new names in the product help and documentation.

Within the application, some of the panel names do not reflect the new product name. However, all of the intelligent functionality of OMEGAMON XE is available for these agents. The new product names will be added to the applications in a subsequent release.

Highlights for Version 300 of the OMEGAMON XE for OS/400OMEGAMON XE for OS/400 Version 300 has been modified to

� support the different threads available with the releases of OS/400

� monitor for files that are inactive

� incorporate the functionality of CandleNet Portal

Details about the types of threads supportedOMEGAMON XE for OS/400 Version 300 has been modified to support threads. If you are using OS/400 V4R3 or V4R4, OMEGAMON XE for OS/400 uses native threads (also called kernel threads).

W


Details about monitoring for files that are inactive OMEGAMON XE for OS/400 provides a program that you can use to monitor for files that have had no activity. If the files are inactive for the amount of time you specify, the program sends a message to the message queue. You can then check the message queue or create a situation and alert that notifies you when a message is received.

For example, if your site has files that must be updated on a schedule, you can use OMEGAMON XE for OS/400 to monitor the files and verify that the changes occur.

Highlights for CandleNet PortalCandleNet Portal helps you monitor your enterprise network and its applications, so that they run smoothly and well. For fast identification of problem areas, colored indicators overlay the icons of the affected systems. As you move the mouse pointer over an indicator, a flyover list opens to show what caused the alert.

Introducing OMEGAMON XE for OS/400 17

Introducing OMEGAMON XEfor OS/400

IntroductionThis chapter introduces OMEGAMON XE for OS/400 and the features of OMEGAMON XE for OS/400.

Chapter ContentsOMEGAMON XE for OS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Features of OMEGAMON XE for OS/400 . . . . . . . . . . . . . . . . . . . . . . . . . 22

1

OMEGAMON XE for OS/400



Overview As part of the CandleNet Command Center (CCC) for distributed systems, OMEGAMON XE for OS/400 offers a comprehensive systems management tool for monitoring OS/400 systems in your network.

What is OMEGAMON XE?OMEGAMON XE is a suite of products that assists you in monitoring your mainframe and distributed systems on a variety of platforms using a variety of workstations.

It provides a way to monitor the availability and performance of all the systems in your enterprise from one or several designated workstations. It provides many useful reports you can use to track trends and understand and troubleshoot system problems. You can use OMEGAMON XE to

� establish your own performance thresholds� create situations, which are conditions to monitor� create and send commands to systems in your managed enterprise by

means of the Take Action feature. (Take Action enables you to, for instance, restart a process that is not functioning properly or send a message.)

� create comprehensive reports about system conditions� monitor for alerts on the systems and platforms you are managing� trace the causes leading up to an alert

� define your own queries, using the attributes provided to monitor conditions of particular interest to you



Components of the environmentThe client-server-agent implementation includes

� a client, that can be

– a CandleNet Portal workstation

– a Candle Management Workstation® (CMW™), used primarily for performing user administration tasks

� a server, known as the Candle Management Server® (CMS™)

� a CandleNet Portal server that performs common CandleNet Portal functions and serves to lighten the CandleNet Portal client

� monitoring agents that collect and distribute data to a CMS.

What is CandleNet Portal?CandleNet Portal is the user interface into your OMEGAMON XE product set. It provides a view of your enterprise from which you can drill down to more closely examine components of your systems environment. Its application window consists of a Navigator that shows all the systems in your enterprise where Candle agents are installed, and a workspace that includes table and chart views of system and application conditions.

CandleNet Portal runs situations at regular intervals to check that your applications and system resources are running, and running well. A failed test causes event indicators to appear in the Navigator.

CandleNet Portal offers two modes of operation: desktop and browser. In desktop mode, the application software is installed on your system. In browser mode, the system administrator installs the application on the web server and you start CandleNet Portal from your browser. In browser mode, the software is downloaded to your system the first time you log on to CandleNet Portal, and thereafter only when there are software updates.

What is the CMW?You use the CMW to perform user administration functions.



Further Information about the CMW and CandleNet PortalFor further information about CandleNet Portal, refer to the product’s online Help and to Administering OMEGAMON Products: CandleNet Portal.

What is OMEGAMON DE?The OMEGAMON DE feature package for CandleNet Portal offers a dashboard view of your enterprise. This feature provides a single point of control from which you can manage the resources your business-critical applications rely on, including a range of operating systems, servers, databases, mainframes, and Web components. It enables you to pull together the data and functionality built into all the Candle monitoring solutions, such as OMEGAMON XE for OS/400. OMEGAMON DE provides all the capability of OMEGAMON XE, plus these additional capabilities:

� Multiple applications can be displayed in one workspace.

In a single workspace, you can build a table or chart with data from one type of monitoring agent, and another table or chart with data from a different agent. Within that workspace, you can show views from as many different agent types as are included on that branch of the Navigator.

� You can link application workspaces.

You can define a link from a workspace associated with one type of monitoring agent to a workspace associated with another type of agent.

� You can define enterprise-specific Navigator views.

The Navigator physical view shows the hierarchy of your managed enterprise by operating platform and type of Candle agent. The Navigator business view shows the hierarchy of any managed objects defined through the CMW. You can also define Navigator views for any logical grouping, such as a departmental or site hierarchy.

� You can define a graphic view.

The graphic view enables you to retrieve and display real-time monitoring data from Candle agents. Using the graphic view, you can create a background image or import one, then place objects (Navigator items) on the image or have it done automatically using geographical coordinates. You can zoom in and you can add such graphics as floor plans and organization charts.



� You can integrate information provided by Candle’s Universal Integrator.

Candle’s Universal Integrator is an agent you can configure to monitor any data you collect. It lets you integrate data from virtually any platform and any source, such as custom applications, databases, systems, and subsystems. Your defined data providers are listed in the Navigator, and default workspaces are automatically created.

Detailed information about OMEGAMON DE is provided in the CandleNet Portal online Help.

About the Workflow EditorIf your product supports the use of the Workflow Editor, you can find information about its use in CandleNet Portal Help and Administering OMEGAMON Products: CandleNet Portal. The Workflow Editor permits you to create new policies or modify any predefined policies for your product or policies created using the Candle Management Workstation.

BenefitsOMEGAMON XE for OS/400 helps ensure that hardware capacity is in sync with your applications, giving you an effective way to detect and prevent slowdowns.

From a single workstation, you can monitor multiple servers and set rules and thresholds for managed servers.

Use OMEGAMON XE for OS/400 to

� monitor your enterprise from a single, graphical workstation

� view detailed reports containing information gathered from OS/400 objects

� quickly and easily define status alerts and corrective actions through an advanced visual programming technology

� intergroup with other CCC solutions– including Windows NT, MVS, UNIX, NetWare, OS/2 and OMEGAVIEW IITM for the Enterprise.

Features of OMEGAMON XE for OS/400



OverviewSystem administrators face increasing challenges in today’s changing technical environment. Candle Corporation developed the CCC and OMEGAMON XE for OS/400 to help you meet these challenges and better manage complexity of your network and many aspects of each OS/400 system in that network.

Using OMEGAMON XE for OS/400 and CandleNet Command CenterOMEGAMON XE for OS/400 offers a central point of management for OS/400 systems; it provides a comprehensive means for gathering exactly the information you need to detect problems early and prevent them. Information is standardized across all distributed systems so you can monitor and manage hundreds of servers from a single workstation.

The CCC for Distributed Systems lets you easily collect and analyze OS/400– specific information, including

� operating system and CPU performance

� OS/400 disk information and performance analysis

� user, system, wait and idle CPU time

� network performance and information, such as topology and status

� virtual and physical memory statistics

� disk and database capacity

� paging information and swap statistics

� multiple nodes and platforms from a single view

� historical data collection for trend analysis and capacity planning



The following table lists the tasks that can be accomplished using OMEGAMON XE for OS/400 alone, in a network and in combination CandleNet Portal.

Table 2. Examples of Tasks

Task OMEGAMON XE for OS/400

User Action CandleNet Portal

Detect library growth �

Detect auxiliary storage pool growth

�

Detect security violations �

Detect bad response time �

Send alerts when specified system conditions are detected

�

Delete unused files � �

Prioritize local jobs � �

Limit local use to users temporarily

� �

Control local job flow � �

Take backup on a scheduled basis

� �

Provide real-time graphical display of resource utilization problems

�

Distribute situations and policies

�

View and edit a situation graphically

�

Specify user action to be taken

�

Start a situation from the central site

� �

Manage remote jobs � �



OMEGAMON XEs are intelligent, remote monitoring agents that reside on managed systems. They assist you in anticipating trouble and warn system administrators when critical events take place on their systems. With OMEGAMON XE for OS/400, system administrators can set threshold levels as desired and flags to alert them when the system reaches these thresholds.

OMEGAMON XEs provide several benefits.

� Simplify application and system management—by managing applications, platforms and resources across your system.

� increase profits—by providing you with real-time access to reliable, up-to-the-minute data that allows you to make faster, better informed operating decisions.

� Enhance system performance—by letting you integrate, monitor, and manage your environment, networks, console, and mission-critical applications. OMEGAMON XE for OS/400 alerts CandleNet Portal when conditions in your environment meet threshold-based conditions. These alerts notify your system administrator to limit and control system traffic. You can view data gathered in reports and charts, informing you of the status of managed systems.

� Enhance efficiency—by monitoring diverse platforms and networks. Depending on your CCC configuration, you can collect and monitor data across platforms. OMEGAMON XE for OS/400 gathers and filters status information at the managed system rather than at the Hub, eliminating unnecessary data transmission and sending only data that is relevant to

Check the OMEGAMON XE for OS/400 log

�

Automate remote configuration changes

� �

Verify remote fix levels � �

Centralize monitoring of network conditions

�

Table 2. Examples of Tasks

Task OMEGAMON XE for OS/400

User Action CandleNet Portal



changes in status conditions. OMEGAMON XE for OS/400 helps you monitor and gather consistent, accurate, and timely information you need to effectively perform your job.

Advanced monitoring facilitiesOMEGAMON XE for OS/400 includes advanced monitoring facilities, such as

� user-defined, and product-provided solutions based on thresholds to raise different types of alerts: critical, warning, and others

� ability to run real-time workspaces at any time

� capability to simultaneously monitor multiple servers from one or more centralized workstations, including servers on various platforms



OMEGAMON XE for OS/400 Attributes 27

OMEGAMON XE forOS/400 Attributes

IntroductionThis chapter provides information about OMEGAMON XE for OS/400 attributes and attribute groups.

Chapter ContentsUsing Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Types of Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Accounting Journal (OS400_Acct_Jrn) Attributes . . . . . . . . . . . . . . . . . . . 39Accounting Journal (OS400_Acct_Jrn) Attributes . . . . . . . . . . . . . . . . . . . 39Alert Notification (OS400_Alert) Attributes . . . . . . . . . . . . . . . . . . . . . . . . 45Communications (OS400_Comm) Attributes . . . . . . . . . . . . . . . . . . . . . . 50Controller Description (OS400_Controller) Attributes . . . . . . . . . . . . . . . . 71Database Member (OS400_DB_Member) Attributes. . . . . . . . . . . . . . . . . 74Device Description (OS400_Device) Attributes . . . . . . . . . . . . . . . . . . . . . 78Disk Unit (OS400_Disk_Unit) Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 82I/O Processor (OS400_I/O_Processor) Attributes. . . . . . . . . . . . . . . . . . . . 87Job (OS400_Job) and Job Queue (OS400_Job_Queue) Attributes . . . . . 90Line Description (OS400_Line) Attributes. . . . . . . . . . . . . . . . . . . . . . . . 109Message (OS400_Message) Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . 112Tips and Techniques for Using the OS/400 Message Attributes . . . . . . . . 117Network (OS400_Network) Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . 121Object (OS400_Object) Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Storage Pool (OS400_Storage_Pool) Attributes. . . . . . . . . . . . . . . . . . . . 137Subsystem (OS400_Subsystem) Attributes . . . . . . . . . . . . . . . . . . . . . . . 142

2


Security Journal (OS400_Security_Jrn) Attributes . . . . . . . . . . . . . . . . . 146Spool File (OS400_Spool_File) Attributes . . . . . . . . . . . . . . . . . . . . . . . . 183System Status (OS400_System_Status) Attributes. . . . . . . . . . . . . . . . . . 189System Values (OS400_System_Values) Attributes . . . . . . . . . . . . . . . . . 191End Notes for Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213


Using Attributes

Using Attributes

Background about OMEGAMON XE for OS/400 attributesAttributes represent the properties of managed systems or networks, and are used to create situations. These situations define conditions to which you want to be alerted, so you can possibly take some corrective action.

For example, you can create situations to alert you to excessive central processing unit (CPU) utilization or disk storage unit usage. OMEGAMON XE for OS/400 allows you to set the limits and precise conditions you want to watch for in your environment. You can be specific by grouping attributes together. Therefore, you can be accurate and precise in what data you want OMEGAMON XE for OS/400 to return.

OMEGAMON XE for OS/400 attributes are grouped by the type of monitoring they provide. Each group monitors in one or more operational areas of the OS/400 system. This type of information is provided with each attribute group, as is a description of each individual attribute in the grouping.

These attributes are also used by OMEGAMON XE for OS/400 to provide reports, which allow you to quickly analyze usage and identify trends, locate problems and decide which situations you want to create.

Types of Attributes


Types of Attributes

OverviewThis section discusses the two types of attributes: notification and sampled.

Notification attributes Notification attributes are attributes that describe characteristics of an occurrence on the system. For example, the alert (OS400_Alert) attributes are notification attributes because they describe the characteristics of the occurrence of alerts on the system. Because occurrences on the system do not exist over a period of time, notification attributes usually are used with a monitor interval of 0. This causes an event to occur as soon as a notification arrives.

Note: The message notification (OS400_Message) attributes are an exception. If you use one or more message notification attributes only in a situation definition, the minimum monitor interval is 30 seconds. If one or more messages occur that satisfy the situation, the situation is evaluated as true at the monitor interval and an event is raised.

Sampled attributes Sampled attributes are attributes that describe characteristics of items that exist over a period of time. For example, the object (OS400_Object) attributes are sampled attributes because they describe the characteristics of objects on the system. Objects exist on the system until they are deleted. For performance reasons, sampled attributes are sampled at each monitor interval.


Types of Attributes

Single-instance attributes Single-instance attributes are attributes that gather only one set of data. For example, the system status (OS400_System_Status) attributes are single-instance attributes because there is only one set of values for the system at any given time.

The OMEGAMON XE for OS/400 attributes are grouped together by the type of information they gather. Each attribute within one of these groups has the same prefix. For example, the attributes that gather data about communications are grouped together and are called OS400_Comm.

Whenever you specify an attribute, OMEGAMON XE for OS/400 gathers the value of that attribute. It also gathers the values of the other attributes in the same group. For example, if you use the OS400_Subsystem.Name attribute, OMEGAMON XE for OS/400 gathers data for all of the attributes that begin with OS400_Subsystem.

For some types of attributes (for example, the OS400_Job attributes), OMEGAMON XE for OS/400 returns only the attributes specified in the situation definition and a few other related attributes. This is to maintain good system performance. To guarantee that OMEGAMON XE for OS/400 returns the attribute that you want, include the attribute in the situation definition.

Multiple-instance attributes Multiple-instance attributes are attributes that can gather multiple sets of data. For example, the job queue (OS400_Job_Queue) attributes are multiple-instance attributes because they can return one set of data for each job queue that exists on the system. If you have three job queues on your system, OMEGAMON XE for OS/400 gathers data for all three job queues, but returns only data that satisfies the situation. In other words, OMEGAMON XE for OS/400 evaluates the data it gathers against the conditions specified in the situation definition and returns only the data that satisfies the situation. For example, you define a OS400_Job_Queue.Status situation to monitor for job queues that are released and congested. Only the job queue that satisfies this situation definition is reported on. Therefore, even though three job queues exist on your system, data is only returned for those that are released and congested. If you display the status of a situation after an event has been raised, you see the values of all of the returned attributes.

Types of Attributes


Combining attributes Multiple-instance attributes with in different attribute groups cannot be used together in the same situation definition.

Note: In the special case of the OS400_Security_Jrn attributes, the prefix extends to the second "_". For instance, OS400_Security_Jrn_AuthFail attributes cannot be combined with OS400_Security_Jrn_ChgAuth attributes.

Single-instance attributes can be used with any other attribute (sampled or notification) in the same situation definition.

The collection interval The frequency with which OMEGAMON XE for OS/400 internally gathers data for attributes is the collection interval. For most attributes, the collection interval is the same as the monitor interval. That is, for these attributes, OMEGAMON XE for OS/400 gathers data and evaluates it at the monitor interval specified in the situation. For some attributes, OMEGAMON XE for OS/400 gathers data with respect to the collection interval but does not evaluate the data until the monitor interval. Therefore, data that you see may be collected at a different interval than you specify and you may see data that is older than expected.

In order to effectively use the attributes provided with OMEGAMON XE for OS/400, you need to develop a monitoring strategy. This includes

� deciding what conditions or problems occur on your system of which you want to be notified

� determining if the OMEGAMON XE for OS/400 can detect these conditions or problems

� using a product-provided situation definition that detects these conditions or create a situation definition of your own

� considering security requirements


Types of Attributes

Scenarios

Scenario 1: Use of processing unit by interactive jobs

Problem: Interactive users on your system use too much of the processing unit. You would like to be notified when interactive jobs use more than 60% of the processing unit.

Solution: For OMEGAMON XE for OS/400 to monitor for this condition, there must be attributes that monitor the appropriate data. Check the situation definitions listed in “OMEGAMON XE for OS/400 Product-provided Solutions” on page 217 to see if any of the situation provided with the product will work. As none of the situation definitions can be used for this example, you must create your own situation.

You decide that you need to use the OS400_Job attributes located in “Job (OS400_Job) and Job Queue (OS400_Job_Queue) Attributes” on page 90. You find two OS400_Job attributes that monitor the data you want

� job type (OS400_Job.Type)

� processing unit utilization (OS400_Job_Percent)

You can monitor for this condition by creating a situation definition (call it HIGH_INT_CPU) that samples the

� OS400_Job.Type attribute

� OS400_JobU_Percent attribute

You decide to sample these attributes every five minutes. When the processing unit is being used more than 60%, you can have OMEGAMON XE for OS/400 send a message (or alert) and log the occurrence of the condition.

Types of Attributes


Scenario 2: Degraded performance of batch jobs

Problem: Batch jobs are slowed down by high use of the processing unit by interactive jobs. You would like to be notified when this happens so you can do something about it. Specifically, you want to be notified when batch job queues get too long.

Solution: You can monitor for this condition by creating a situation definition (call it BATCH_DEGRADED) that samples the appropriate attribute. For example, the number-of-queued-jobs (OS400_Job_Queue.Number_Jobs) attribute measures the number of jobs in a queue. As with the previous example, you can decide to monitor these attributes at regular intervals and send a message (or alert) when the condition occurs.

Scenario 3: Degraded performance of batch jobs at night

Problem: Degraded batch processing is only a problem during the night shift. You want to be notified when this occurs.

Solution: You can monitor for this condition only during specific hours by using job schedule entries. For example, specify

� one job schedule entry to start monitoring for the BATCH_DEGRADED situation at 6:00 P.M.

� another job schedule entry to end the monitoring for the BATCH_DEGRADED situation at 6:00 A.M.

As with the previous example, you can decide to send a message (or alert) when the condition occurs and log the occurrence of the condition. For more information on job schedule entries, see the OS/400 manual Work Management Guide.


Types of Attributes

Determining data that can be monitored OMEGAMON XE for OS/400 monitors data using attributes. These attributes are grouped together logically by the type of data they monitor. For example, the OS400_Job attributes collect data about active jobs. All the OMEGAMON XE for OS/400 attributes are listed in this chapter.

The attributes are also grouped by operational area. An operational area is a logical grouping of attributes based on similar tasks.

Operational areas are helpful in identifying a specific attribute. They also identify possible attributes that monitor for certain conditions. For example, all the attributes that deal with system values are in the configuration operational area.

The column headings in the table indicate the operational areas configuration (CF), change management (CH), communications (CO), output (O), performance (PF), problem analysis (PA), security (SC), storage (ST), user (US), and work management (WM). For example, if you are interested in the communications operational area, you can use this table to easily identify which attribute groups contain attributes that monitor communications data.

Table 3. Attribute Location and Operational Area

Attribute Description and Location

CF CH CO O PF PA SC ST US WM

Accounting Journal

(OS400_Acct_Jrn)�

Alert

(OS400_Alert)� �

APPN Topology

(OS400_APPN_Topology)� �

Asynchronous Communications

(OS400_Comm_Async)� �

Binary Synchronous Communications

(OS400_Comm_Bisync)

� � �

Types of Attributes


Controller Description

(OS400_Controller)� �

Device Description

(OS400_Device)� �

Disk Unit

(OS400_Disk_Unit)� �

Ethernet

(OS400_Comm_Ethernet)� � �

Database Member

(OS400_DB_Member)� �

I/O Processor

(OS400_I/O_Processor)� � �

Job Queue

(OS400_Job_Queue)�

Job Resource and Information

(OS400_Job)� �

Line Description

(OS400_Line)� �

Message

(OS400_Message)�

Network Value

(OS400_Network)� � �

Object

(OS400_Object)� �

Security Journal

(OS400_Security_Journal)�

Table 3. Attribute Location and Operational Area (continued)




Types of Attributes

Spool File

(OS400_Spool_File)�

Storage Pool

(OS400_Storage_Pool)� � �

Subsystem

(OS400_Subsystem)�

Synchronous Data Link Control

(OS400_Comm_SDLC)� � �

System Status

(OS400_System_Status)� �

System Value

(OS400_System_Value)�

Token Ring

(OS400_Comm_Token_Ring)� � �

X.25 (OS400_Comm_X25) � � �

Table 3. Attribute Location and Operational Area (continued)



Types of Attributes


OMEGAMON XE for OS/400 command security considerations When OMEGAMON XE for OS/400 is started, you can use the associated CL commands. The table shows the group profiles that are authorized to these commands by default when OMEGAMON XE for OS/400 is first installed. A � in a column indicates that users associated with that group profile can use the command.

To determine which group profile a user is associated with, use the Display User Profile (DSPUSRPRF) command. The group profile to which the user is associated is listed in the group profile field.

Table 4. Commands owned by QSYS with *PUBLIC *EXCLUDE

Command QSRV QSRVBAS QSYSOPR QPGMR

CFGOMA �

DSPOMALOG � � � �

ENDOMA � �

STROMA � �


Accounting Journal (OS400_Acct_Jrn) Attributes


OverviewThe OS/400 accounting journal attributes are notification attributes in the operational area of work management.

The attributes have these considerations.

� The attributes can only be used if the accounting level system value (QACGLVL) is set to *JOB.

� When you start monitoring for a situation using the accounting journal (OS400_Acct_Jrn) attributes, the accounting journal receiver is locked. While the journal receiver is locked, you cannot detach it from the journal, save it, or delete it.

� Coding specific compare values for Job_Name, and User attributes reduces the amount of data OMEGAMON XE for OS/400 has to handle and improves performance. Under certain circumstances (especially on large systems), failing to specify one or more of these attributes may overload OMEGAMON XE for OS/400 and result in the situation not being evaluated.

� In order to use the OS400_Acct_Jrn attributes, the OS/400 Accounting Journal, QACGJRN, must exist in library QSYS. In addition, you must have created some journal receivers and attached them to the Accounting journal. Refer to the IBM manual Work Management for information on Accounting journal management.

� Changing the system value QDATE and QTIME will affect exactly when OS400_Acct_Jrn attributes are picked up.

For example, if you change the system values to a future date or time, such as the year 2000, then any journal entries that occur are marked with this future date. When you change the system values back to the current date, any subsequent journal entries are correctly marked with the current date. Modifying the system value in this way results in having older journal entries marked with a more recent date.

If you start a journal situation, it returns all journal entries that have a date and time equal to or greater than the current date. If it finds an older entry



that is pre-dated with the year 2000 date, the situation returns all entries following the year 2000 entry. Some of these entries would have occurred before the situation was started. If a large number of these journal entries exist, they could cause the situation to time out. To avoid this problem, remove the current journal receiver or receivers from the JRN and create and attach a new one.

The attributes are listed in alphabetical order.

OS400_Acct_Jrn.Accounting_ CodeThe accounting code assigned to the job by the system. As the job is processed, the system uses the accounting code to collect statistics on the system resources used by the job.

Valid Values� alphanumeric

� maximum 15 characters

OS400_Acct_Jrn.Completion_CodeThe two digit code that indicates how the job ended.

Valid Values

00—Normal completion

10—Normal completion during controlled end or controlled subsystem end

20—Job exceeded end severity

30—Job ended abnormally

40—Job ended before becoming active

50—Job ended while active

60—Subsystem ended abnormally while job was active

70—System ended abnormally while job was active

80—Job completed in the time limit

90—Job forced to complete after the time limit has ended



99—Accounting entry caused by CHGACGCDE command

Usage

The attribute can be used with the *AVG, *MAX, *MIN, and *SUM functions.

OS400_Acct_Jrn.CPU_TimeThe processing time used by the job (in seconds).

Valid Values � decimal number

� in the range 0.000-2147483647.000

OS400_Acct_Jrn.Database_I/O_OperationsThe total number of database read, write, update, delete, FEOD, release, commit, and rollback operations.

Valid Values � integer

� in the range 0-2147483647

OS400_Acct_Jrn.Date_and_TimeThe date and time when the job entered the system. For batch jobs, this is the date and time the job was placed in a job queue.

Valid Values

Date and time in the format CYYMMDDHHmmSSmmm (For example, 0961002103000000 indicates a century bit of 0, a date of October 2, 1996, and a time of 10:30:00:000.)

OS400_Acct_Jrn.Job_NameThe name of the job.

Valid Values



� alphanumeric


OS400_Acct_Jrn.Job_NumberThe number the system assigned to the job.

Valid Values � alphanumeric


OS400_Acct_Jrn.Job_TypeIndicates the type of job.

Valid Values

A—Autostart job

B—Batch job (includes communications and MRT)

I—Interactive job

M—Subsystem monitor

R—Spooling reader

W—Spooling writer

OS400_Acct_Jrn.ORIGINNODEThe host name for the monitored system.

Valid Values � simple text string

� alphanumeric

� maximum length 64 characters



OS400_Acct_Jrn.Start_Date_and_TimeThe date and time when the job started. For batch jobs, this is the date and time the job left a job queue and started running.

Valid Values

Date and time in the format CYYMMDDHHmmSSmmm. For example, 0961002103000000 indicates a century bit of 0, date of October 2, 1996, and time of 10:30:00:000.

OS400_Acct_Jrn.Start_TimeThe time when the job started. For batch jobs, this is the time the job left a job queue and started running.

Valid Values

Time in the format HHMMSS (For example, 103000 is a time of 10:30:00 a.m.)

OS400_Acct_Jrn.TimeThe time when the job entered the system. For batch jobs, this is the time the job was placed on the job queue.

Valid Values

Time in the format HHMMSS (For example, 103000 indicates a time of 10:30:00 a.m.)

OS400_Acct_Jrn.Transaction_NumberThe number of transactions executed by the job.


� in the range 0-2147483647

OS400_Acct_Jrn.Transaction_TimeTotal transaction time (in seconds).




� in the range -1-2147483647

OS400_Acct_Jrn.UserThe user of the job.




Alert Notification (OS400_Alert) Attributes


OverviewThe OS400 alert attributes are notification attributes in the operational areas of problem analysis and work management. These attributes can be used only if the OS/400 network attributes are set to enable alerts.

Use the OS/400 Display Network Attributes (DSPNETA) command to view the network attributes. The OS/400 network attributes should not be confused with OMEGAMON XE for OS/400 network (OS400_Network) commands.

The attribute are listed in alphabetical order.

OS400_Alert.Analysis_AvailableSpecifies whether or not problem analysis is available for a message.

Valid Values

*YES—Problem analysis is available for this problem or the alert is for a problem analysis message.

*NO—The message is not for problem analysis.

OS400_Alert.DelayedSpecifies whether an alert has been delayed.

Valid Values

*YES—The alert was delayed.

*NO—The alert has never been delayed.

OS400_Alert.DescriptionThe description of the alert. The text is found in the QALRMSG message file in the QSYS library. The prefix for the message ID is ALD, and the suffix is the value of this field.

Valid Values



� alphanumeric


OS400_Alert.First_CauseThe most probable cause for the alert.



OS400_Alert.HeldSpecifies whether an alert has been held.

Valid Values

*YES—The alert was held for the purpose of sending to the focal point.

*NO—The alert has never been held.

OS400_Alert.IDIdentifier assigned to the alert.



OS400_Alert.LocalSpecifies whether the alert has been locally generated or received by another system.

Valid Values

*YES—The alert is a locally generated alert.

*NO—The alert is a received alert.



OS400_Alert.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Alert.Message_IDThe ID of the message causing an alert. The higher the number, the more severe the error.



OS400_Alert.Message_SeverityThe severity of the message causing an alert. The higher the number, the severe the error.


� in the range 0-99

OS400_Alert.Operator_GeneratedSpecifies whether or not the alert was generated by an operator.

Valid Values

*YES—The alert was generated by an operator.

*NO—The alert was not generated by an operator.



OS400_Alert.Origin_SystemThe system where the associated problem entry occurred.



� If the field is blank, there is no problem log entry is associated with the alert.

OS400_Alert.Problem_IDThe ID of the problem associated with the alert. If no problem log entry is associated with the alert, this field is blank.



� if the field is blank, there is no problem log entry is associated with the alert

OS400_Alert.ResourceThe name of the resource that detected the error condition.



OS400_Alert.Resource_TypeThe type of resource that detected the error condition. The failing resource is the lowest resource in the resource hierarchy.





OS400_Alert.TypeThe type of alert. The text for the code point is found in the QALRMSG message file in the QSYS library. The prefix for the message ID is ALT, and the suffix is the value of this field followed by 00.



Communications (OS400_Comm) Attributes



OverviewThe OS/400 communications attributes are sampled attributes in the operational areas of performance and communications. Please note the following additional operational areas for the different types (groups) of communications attributes.

� The Asynchronous Communications (OS400_Async) attributes OS400_Comm_AsynLine_Description and OS400_Comm_AsynError_Percent are also in the problem analysis operational area.

� The Binary Synchronous Communications (OS400_Bisync) attributes OS400_Comm_BisynLine_Description, OS400_BisynReceive_Error_Percent, and OS400_Comm_BisynSend_Error_Percent are also in the problem analysis area.

� The Ethernet Communications (OS400_Ethernet) attribute OS400_Comm_Ethernet.Line_Description is also in the problem analysis area.

� The Synchronous Data Link Control Communications (OS400_Comm_SDLC) attributes OS400_Comm_SDLLine_Description, OS400_Comm_SDLSend_Error_Percent and OS400_Comm_SDLReceive_Error_Percent are also in the problem analysis area.

� The Token Ring Communications (OS400_Comm_Token_Ring) attribute OS400_Comm_Token_Ring.Line_Description is also in the problem analysis area.

� The X.25 Communications (OS400_Comm_X.25) attributes OS400_Comm_X25.Line_Description, OS400_Comm_X25.Send_Error_Percent, and OS400_Comm_X25.Receive_Error_Percent are also in the problem analysis area.

� An APPN topology event can consist of node or transmission group changes.




OS400_Comm_Async.Error_PercentThe percent of protocol data units received with errors during the last monitor interval. This value can indicate congestion on the communications line or that the quality of the communications line is poor.


� in the range 0.0-100.0

Usage


OS400_Comm_Async.IOP_Bus_AddressThe IOP bus address.



OS400_Comm_Async.IOP_Bus_NumberThe IOP bus number.



OS400_Comm_Async.IOP_NameThe system resource name associated with the IOP that controls the disk unit.





OS400_Comm_Async.Line_DescriptionThe name of the description for this line.



OS400_Comm_Async.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Comm_Async.Utilization_PercentThe percent of the capacity of the line that was used during the last interval (measured in bits or bytes per second)



Usage


OS400_Comm_Bisync.IOP_Bus_AddressThe IOP bus address. Possible values are 0 through 31.

OS400_Comm_Bisync.IOP_Bus_NumberThe IOP bus number. The valid values are 0 through 7.



OS400_Comm_Bisync.IOP_NameThe system resource name associated with the IOP on which this protocol runs.



OS400_Comm_Bisync.Line_DescriptionThe name of the line description for this line.



OS400_Comm_Bisync.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Comm_Bisync.Receive_Error_PercentThe percent of data characters received that contained errors. This value can indicate congestion on the communication line or that the quality of the communications line is poor.



Usage




OS400_Comm_Bisync.Send_Error_PercentThe percent of data characters transmitted that had to be retransmitted. This value can indicate congestion on the communications line or that the quality of the communications line is poor.



Usage


OS400_Comm_Bisync.Utilization_PercentThe percent of the capacity of the line that was used during the last interval (measured in bits or bytes).



Usage


OS400_Comm_Ethernet.IOP_Bus_AddressThe IOP bus address.





OS400_Comm_Ethernet.IOP_Bus_NumberThe IOP bus number.



OS400_Comm_Ethernet.IOP_NameThe system resource name associated with the IOP that controls the disk unit



OS400_Comm_Ethernet.Local_RNR_PercentThe percent of information (I) frames received that resulted in a receive-not-ready (RNR) frame being transmitted from the local system to the remote controller or system. This is often indicates congestion at the local system.



Usage


OS400_Comm_Ethernet.Line_DescriptionThe name of the line description for this line.





OS400_Comm_Ethernet.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Comm_Ethernet.Remote_RNR_PercentThe percent of information (I) frames transmitted that resulted in a receive-not-ready (RNR) frame being returned by the remote controller or system. This is often indicates congestion at the remote system or controller.



Usage


OS400_Comm_Ethernet.Response_Time_PercentThe percent of total frames transmitted that resulted in a time out of the response (TI) timer of the local area network.



Usage




OS400_Comm_Ethernet.Utilization_PercentThe percent of the capacity of the line that was used during the last interval (measured in bits or bytes per second).



Usage


OS400_APPN_Topology.CPNAMEThe control point name for the node.



OS400_APPN_Topology.Date_and_TimeThe date and time that the job entered the system.

Valid Values


OS400_APPN_Topology.NETIDThe network ID for the node.





OS400_APPN_Topology.Node_CongestionIndicates whether or not there is congestion for a node (indicates excessive traffic or excessive usage).

Valid Values

*YES —There is congestion for the node.

*NO—The node is not congested.

OS400_APPN_Topology.Node_TypeThe type of APPN node.

Valid Values

*EN—Node is low entry networking or and APPN end node.

*NN—Node is an APPN networking node.

*VN—Node is an APPN virtual node.

OS400_APPN_Topology.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_APPN_Topology.TransGroup_Controller_NameThe name of the controller description object for the transmission group.



� If the field is blank, if the transmission group is not associated with the local node.



OS400_APPN_Topology.TransGroup_DestNode_CPNAMEThe APPN transmission group control point name for the destination node.



OS400_APPN_Topology.TransGroup_DestNode_NETIDThe APPN transmission group network ID for the destination node.



OS400_APPN_Topology.TransGroup_NumberThe APPN transmission group number that is used to identify a unique logical link between 2 nodes.


� in the range 0-2147483647

OS400_APPN_Topology.TransGroup_OperationalThe APPN transmission group status between two nodes

Valid Values

*YES—Operational status between 2 nodes is yes.

*NO—Operational status between 2 nodes is no.

OS400_APPN_Topology.TimeThe time that the job entered the system.



Valid Values


OS400_APPN_Topology.Update_TypeControls how the topology information is collected.

Valid Values

*CURRENT—Topology existed at the time the situation is first evaluated. Topology data is returned on the first evaluation only.

*UPDATED—A node or transmission group record was updated.

*DELETED—A node or transmission group was deleted. This situation raises only after the node has been deleted for at least 21 days.

*INSERTED—A new node or transmission group was added.

OS400_Comm_Token_Ring.IOP_Bus_AddressThe IOP bus address.



OS400_Comm_Token_Ring.IOP_Bus_NumberThe IOP bus number.



OS400_Comm_Token_Ring.IOP_NameThe system resource name associated with the IOP that controls the disk unit.





OS400_Comm_Token_Ring.Line_DescriptionThe name of the line description for this line.



OS400_Comm_Token_Ring.Local_RNR_PercentThe percent of information (I) frames received that resulted in a receive-not ready (RNR) frame being transmitted from the local system to the remote controller or system. This often indicates congestion at the local system.

Valid Values� decimal number


Usage




OS400_Comm_Token_Ring.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Comm_Token_Ring.Remote_RNR_PercentThe percent of information (I) frames transmitted that resulted in a receive-not-ready (RNR) frame being returned by the remote controller or system. This often indicates congestion at the remote system or controller.



Usage


OS400_Comm_Token_Ring.Response_Time_PercentThe percentage of the total frames transmitted that resulted in a time out of the response (TI) timer of the local area network



Usage




OS400_Comm_Token_Ring.Utilization_PercentThe percentage of the capacity of the line that was used during the last interval (measured in bits or bytes).



Usage


OS400_Comm_X25.Average_Utilization_Percent Average of these 2 attributes

� Comm_X25.Send_Utilization_Percent

� Comm_X25.Receive_Utilization_Percent

Valid Values

Integer in the range 0-100 or one of these values

� *GUIDELINE

� *THRESHOLD

Usage


OS400_Comm_X25.IOP_Bus_AddressThe IOP bus address.





OS400_Comm_X25.IOP_Bus_NumberThe IOP bus number.



OS400_Comm_X25.IOP_NameThe system resource name associated with the IOP that controls the disk unit.



OS400_Comm_X25.Line_Description The name of the line description for this line.



OS400_Comm_X25.Local_RNR_PercentThe percent of information (I) frames received that resulted in a receive-not-ready (RNR) frame being transmitted from the local system to the remote controller or system. This often indicates congestion at the local system.

Valid Values� integer


Usage




OS400_Comm_X25.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Comm_X25.Receive_Error_Percent The percent of data characters received that contained errors. This value can indicate congestion on the communication line or that the quality of the communications line is poor.



OS400_Comm_X25.Receive_Utilization_PercentThe percentage of the capacity of the line to receive that was used during the last monitor interval.



Usage


OS400_Comm_X25.Remote_RNR_PercentThe percent of information (I) frames transmitted that resulted in a receive-not-ready (RNR) frame being returned by the remote controller or system. This often indicates congestion at the remote system or controller.





Usage


OS400_Comm_X25.Send_Error_PercentThe percent of data characters transmitted that had to be retransmitted. This value can indicate congestion on the communications line or that the quality of the communications line is poor.



Usage


OS400_Comm_X25.Send_Utilization_PercentThe percentage of the capacity of the line to send that was used during the last monitor interval.



Usage


OS400_Comm_SDLC.Controller_Poll_PercentThe percentage of the active line spent by the line polling inoperative controllers during the sample interval.





Usage


OS400_Comm_SDLC.IOP_Bus_AddressThe IOP bus address.



OS400_Comm_SDLC.IOP_Bus_NumberThe IOP bus number.



OS400_Comm_SDLC.IOP_NameThe system resource name associated with this IOP.


� maximum of 10 characters

OS400_Comm_SDLC.Local_RNR_PercentThe percent of information (I) frames received that resulted in a receive-not-ready (RNR) frame being transmitted from the local system to the



remote controller or system. This often indicates congestion at the local system.



Usage


OS400_Comm_SDLC.Line_DescriptionThe name of the line description for this line.



OS400_Comm_SDLC.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Comm_SDLC.Receive_Error_PercentThe percent of data characters received that contained errors. This value can indicate congestion on the communication line or that the quality of the communication line is poor.





Usage


OS400_Comm_SDLC.Remote_RNR_PercentThe percent of information (I) frames transmitted that resulted in a receive-not-ready (RNR) frame being returned by the remote controller or system. This often indicates congestion at the remote system or controller.



Usage


OS400_Comm_SDLC.Send_Error_PercentThe percent of data characters transmitted that had to be retransmitted. This value can indicate congestion on the communications line or that the quality of the communications line is poor.



Usage


OS400_Comm_SDLC.Utilization_PercentThe percent of the capacity of the line that was used during the last interval (measured in bits or bytes per second).





Usage



Controller Description (OS400_Controller) Attributes


OverviewThe OS/400 controller description attributes are sampled attributes in the operational areas of communications and configuration.

OS400_Controller.CategoryThe category for the controller description.

Valid Values

Alphanumeric name with a maximum of 10 characters or one of these values

� *APPC

� *ASYNC

� *BSC

� *FNC

� *HOST

� *LWS

� *NET

� *RTLFNC

� *RWS

� *TAP

� *VWS

OS400_Controller.NameA name for the controller.






OS400_Controller.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Controller.StatusIndicates the state or condition (status) of a controller.

Valid Values

00—VARIED OFF

10—VARY OFF PENDING

20—VARY ON PENDING

30—VARIED ON

40—CONNECT PENDING

50—SIGNON DISPLAY

60—ACTIVE

63—ACTIVE READER

66—ACTIVE WRITER

70—HELD

75—POWERED OFF

80—RCYPND

90—RCYCNL

95—SYSTEM REQUEST

100—FAILED



103—FAILED READER

106—FAILED WRITER

110—DIAGNOSTIC MODE

111—DAMAGED

112—LOCKED

113—UNKNOWN

Database Member (OS400_DB_Member) Attributes



OverviewThe OS/400 database attributes are sampled attributes in the operational areas of storage and work management.

Coding specific compare values for DB_Member.Member, DB_Member.File and DB_Member.Library reduces the amount of data OMEGAMON XE for OS/400 has to handle. This improves system performance. Failing to specify one or more of these attributes will overload OMEGAMON XE for OS/400, which results in situations not being evaluated.

Note: You can not use the OR function between any of the predicates when building situations using this group of attributes.


OS400_DB_Member.FileThe name of the file from which the member list was retrieved.



OS400_DB_Member.File_AttributeThe type of file found.

Valid Values

PF—Physical file

LF—Logical file

OS400_DB_Member.Increments_LeftThe remaining number of increments that can be automatically added to the member size. This value applies only to physical files The value for logical files is 0.




� in the range 0-2147483647

Usage


OS400_DB_Member.LibraryThe name of the library that contains the object.


� maximum10 characters

OS400_DB_Member.MemberThe name of the member whose description is being retrieved.



OS400_DB_Member.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_DB_Member.Percent _Delete_RecordsThe percentage of the current number of records that have been deleted. This applies to data files only.





Usage


OS400_DB_Member.Percent_UsedThe percentage of the capacity of the member that is currently being used.



Usage


OS400_DB_Member.Records_Unused The number of records that are not being used.


� in the range 0-2147483647

Usage


OS400_DB_Member.Records_UsedThe number of records used.


� in the range 0-2147483647



Usage


OS400_DB_Member.Source_File_FlagIndicates whether the file is a source file or a data file.

Valid Values

*DATA—File is a data file.

*SOURCE—File is a source file.

OS400_DB_Member.Source_Member_TypeIf this is a source file, this is the type of source member.



OS400_DB_Member.SQL_TypeThe type of Structured Query Language (SQL) file.

Valid Values

Blank—The file is not an SQL file.

TABLE—The file is a non-keyed physical file that contains field characteristics.

VIEW—The file is a logical file over one or more tables or views. This SQL file type provides a subset of data in a particular table or a combination of data from more than one table or view.

INDEX—The file is keyed logical file over one table. The keyed logical file is used whenever access to records in a certain order is requested frequently.

Device Description (OS400_Device) Attributes



OverviewThe OS/400 device description attributes are sampled in the operational areas of communication and configuration.

If you do not specify a category using the OS400_Device.Category attribute, it will default to *CMN.


OS400_Device.CategoryThe category of the device description.

Valid Values


� *APPC

� *ASYNC

� *BSC

� *CMN

� *DKT

� *DSP

� *FNC

� *HOST

� *INTRA

� *MLB

� *NET

� *OPT

� *PRT

� *RTL



� *SNPT

� *SNUF

� *TAP

OS400_Device.Job_NameThe name of the job associated with an active device, if applicable.


� maximum 10 characters (Do not use * values.)

OS400_Device.Job_NumberThe job number portion of a full qualified job name.



OS400_Device.Job_UserThe user name portion of a full qualified job name.



OS400_Device.NameA name or identifier describing a device.





OS400_Device.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Device.Passthru_DeviceThe name of an upstream device used to complete a pass-through session (if applicable).



OS400_Device.StatusThe status returned indicating the state or condition of a device (such as printers, modems, and tapes).

Valid Values

00—VARIED OFF



30—VARIED ON


50—SIGNON DISPLAY

60—ACTIVE

63—ACTIVE READER

66—ACTIVE WRITER



70—HELD

75—POWERED OFF

80—RCYPND

90—RCYCNL

95—SYSTEM REQUEST

100—FAILED

103—FAILED READER

106—FAILED WRITER

110—DIAGNSTIC MODE

111—DAMAGED

112—LOCKED

113—UNKNOWN

Disk Unit (OS400_Disk_Unit) Attributes



OverviewThe OS/400 disk unit attributes are sampled attributes in the operational areas of storage and performance.

Disk Unit attributes allow you to collect data based on the cumulative value of disk unit counters.


OS400_Disk_Unit.Arm_NumberUnique identifier for the disk unit.



OS400_Disk_Unit.Aux_Storage_Pool_NumberThe auxiliary storage pool (ASP) to which the disk unit is currently allocated.

Valid Values

0—The disk unit is not allocated.

1—The disk unit is allocated to the system ASP.

2–16—The disk unit is allocated to the user ASP.

OS400_Disk_Unit.Average_Queue_LengthThe sum of the number of I/O operations awaiting service (including any operation in progress) at the end of each collection interval, divided by the number of collections taken during the last monitor interval.




� in the range 0–2147483647

OS400_Disk_Unit.Average_Service_Time The average service time (in seconds) during the last monitor interval. The program calculates the number by dividing the percentage of samples where the disk arm is busy by the sum of read data commands and write data commands.


� in the range 0-2147483647

Usage


OS400_Disk_Unit.Checksum_Number Specifies the checksum set to which this unit is currently allocated.

Valid Values

0—The number is not currently assigned to a checksum value.

1 - 16—Checksum is set.

OS400_Disk_Unit.Drive_Capacity The capacity of the drive in Kilobytes. The total number of bytes of auxiliary storage provided on the unit for the storage of objects and internal machine functions when the auxiliary storage pool (ASP) containing it is not under checksum protection.


� in the range 0-2147483647

Usage




OS400_Disk_Unit.Drive_Type The type of disk drive.



OS400_Disk_Unit.IOP_Bus_Address The IOP bus address.



OS400_Disk_Unit.IOP_Bus_Number The IOP bus number.



OS400_Disk_Unit.IOP_NameThe system resource name associated with the IOP that controls this disk unit.



OS400_Disk_Unit.ORIGINNODE The host name for the monitored system.

Valid Values



� simple text string

� alphanumeric


OS400_Disk_Unit.Percent_Busy The percentage of time that the actuator for the disk unit is busy during the last monitor interval. An actuator moves the read and write heads within an auxiliary storage device.



Usage


OS400_Disk_Unit.Percent_Permanent_Used Percent of permanent disk capacity used (checksum case).



Usage


OS400_Disk_Unit.Percent_Used Percentage of the capacity of the member that is currently being used





Usage



I/O Processor (OS400_I/O_Processor) Attributes


OverviewThe OS/400 I/O processor attributes are sampled attributes in the operational areas of performance, storage, and communications.


OS400_I/O_Processor.Comm_Percent The percentage of the total IOP processor time that was used by communications tasks during the last monitor interval. This field only applies to communications and multifunction IOPs. Otherwise, it is set to 0.



Usage


OS400_I/O_Processor.Disk_Percent The percentage of the total IOP processor time that was used by disk tasks during the last monitor interval. This applies only to multifunction IOPs. Otherwise, it is set to 0.



Usage




OS400_I/O_Processor.IOP_Bus_Address The IOP bus address.



OS400_I/O_Processor.IOP_Bus_Number The IOP bus number.



OS400_I/O_Processor.Name The system resource name associated with this IOP that controls the disk unit.



OS400_I/O_Processor.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_I/O_Processor.Type The type of IOP.



Valid Values

*COMM—IOP is a communications IOP.

*DISK—IOP is a disk IOP.

*WKSTN—IOP is a local workstation IOP.

*MLTFUN—IOP is a multifunction IOP.

OS400_I/O_Processor.Utilization_Percent The percentage of the total IOP processor time that the IOP was busy and not idle during the last monitor interval.


� in the range 0.0 to 100.0

Usage


Job (OS400_Job) and Job Queue (OS400_Job_Queue) Attributes



OverviewThe OS/400 job attributes are sampled. attributes in the operational areas of performance and work management.

The OS/400 job attributes allow you to collect performance data about started jobs, running jobs, and jobs that end during the monitor interval.

Note: Only active system request jobs, group jobs and disconnected jobs are monitored.

The attributes are in alphabetical order.

OS400_Job.Acct_Code An identifier assigned to the job by the system to collect resource use information for the job when job accounting is active. This attribute monitors in the operational areas of performance and work management.



OS400_Job.Acct_Status The status of the job. A job displays only 1 status and the attribute can be used to monitor in the operational area of performance.

Valid Values

Blank—A blank status field represents a job that is in transition or is not active.

BSCA —The job is waiting in a pool activity level for the completion of an I/O operation to a binary synchronous device.

BSCW —The job is waiting for the completion of an I/O operation to a binary synchronous device.



CMNA—The job is waiting in a pool activity level for the completion of an I/O operation to a communications device.

CMNW—The job is waiting for the completion of an I/O operation to a communications device.

CMTW—The job is waiting for the completion of save-while-active checkpoint processing in another job.

CPCW—The job is waiting for the completion of a CPI communications call.

DEQA—The job is waiting in the pool activity level for completion of a dequeue operation.

DEQW—The job is waiting for completion of a dequeue operation. For example, QSYSARB and subsystem monitors generally wait for work by waiting for a dequeue operation.

DKTA—The job is waiting in a pool activity level for the completion of an I/O operation to a diskette unit.

DKTW—The job is waiting for the completion of an I/O operation to a diskette unit.

DLYW—The job is delayed. The Delay Job (DLYJOB) command delays the job for a time interval to end, or for a specific delay end time. The function field shows either the number of seconds the job is to delay (999999), or the specific time when the job is to start running again.

DSC—The job is disconnected from a workstation display.

DSPA—The job is waiting in a pool activity level for input from a workstation display.

DSPW—Waiting for input from a workstation display.

END—The job has been ended with the *IMMED option, or its delay time has ended with the *CNTRLD option.

EOFA—Waiting in the activity level to try a read operation again on a database file after the end-of-file has been reached.

EOFW—Waiting to try a read operation again on a database file after the end-of-file has been reached.



EOJ—Ending for a reason other than running the End Job (ENDJOB) or End Subsystem (ENDSBS) command, such as SIGNOFF, End Group Job (ENDGRPJOB), or an exception that is not handled.

EVTW—Waiting for an event. For example, QLUS and SCPF generally wait for work by waiting for an event.

GRP—The job is suspended by a Transfer Group Job (TFRGRPJOB) command.

HLD—The job is held.

ICFA—The job is waiting in a pool activity level for the completion of an I/O operation to an intersystem communications function file.

ICFW—The job is waiting for the completion of an I/O operation to an intersystem communications function file.

INEL—The job is ineligible and not currently in the pool activity level.

LCKW—The job is waiting for a lock.

MLTA—The job is waiting in a pool activity level for the completion of an I/O operation to multiple files.

MLTW—The job is waiting for the completion of an I/O operation to multiple files.

MSGW—The job is waiting for a message from a message queue.

MXDW—The job is waiting for the completion of an I/O operation to a mixed device file.

OS/W—The job is waiting for the completion of an OSI Communications Subsystem/400 OSLISN, OSRACS, OSRACA, OSRCV, or OSRCVA operation.

PRTA—The job is waiting in a pool activity level for output to a printer to complete.

PRTW—The job is waiting for output to a printer to be completed.

PSRW—A prestart job waiting for a program start request.

RUN—The job is currently running in the pool activity level.

SRQ—The job is the suspended half of a system request job pair.



SVFA—The job is waiting in a pool activity level for completion of a save file operation.

SVFW—The job is waiting for completion of a save file operation.

TAPA—The job is waiting in a pool activity level for completion of an I/O operation to a tape unit.

TAPW—The job is waiting for completion of an I/O operation to a tape unit.

TIMA—The job is waiting in a pool activity level for a time interval to end.

TIMW—The job is waiting for a time interval to end.

OS400_Job.Async_I/O The rate of physical asynchronous database and nondatabase read and write operations per second during the last monitor interval.



Usage


OS400_Job.Client_Access_Application Indicates whether or not the job is a Client Access for OS/400 application job. The attribute monitors in the operational area of performance.

Valid Values

*YES—The job is a Client Access for OS/400 application job.

*NO—The job is not a Client Access for OS/400 application job.

OS400_Job.CPU_Percent The percentage of the processing unit used by this job during the last monitor interval. This attribute monitors in the operational area of performance.





Usage


OS400_Job.CPU_Time The processing time used by the job (in seconds) This attribute monitors in the operational area of performance.


� in the range 0.000-2147483647.000

Usage


OS400_Job.CPU_Time_Overall The total processing unit time used by the job (in seconds) This is the total since the job started. This attribute monitors in the operational area of performance.


� in the range 0.000-2147483647.000

Usage


OS400_Job.DDM_Target Indicates whether or not the job is a distributed data management (DDM) job flag. The attribute monitors in the operational area of performance.



Valid Values

*YES—The job is a target DDM job.

*NO—The job is not a target DDM job.

OS400_Job.Emulation_Active Indicates whether or not the job has an emulation active job flag. The attribute monitors in the operational area of performance.

Valid Values

*YES—The job is an emulation job.

*NO—The job is not an emulation job.

OS400_Job.End_Status Indicates whether or not the system issued a controlled cancellation. The attribute monitors in the operational area of work management.

Valid Values

*ACTIVE—The system, subsystem, or job is not canceled.

*ENDING—The system, the subsystem in which the job is running, or the job itself is cancelled.

*INACTIVE—The job is not running.

OS400_Job.Function_Name The name of the function and additional information (as described in the function type field) about the function the job is currently performing. The program updates the information only when a command is processed.





OS400_Job.Function_Type Indicates the type of function and whether or not the job is performing a high-level function.

Valid Values

Blank—The system is not doing a logged function.

C—A command is running interactively, it is a batch stream, or it was rerequested from a system menu. Commands in CL programs or REXX procedures are not logged.

D—The job is processing a delay job command.

G—The Transfer Group Job (TRFGRPJOB) command suspended the job.

I—The job is rebuilding an index (access path). The Function Name field contains the group job name for the field.

L—The system logs history information in a database file. The Function Name filed contains the name of the file. QHST is the only log currently supported.

M—The job is a multiple requester terminal (MRT) job i the job type of BATCH and the subtype is MRT, or it is an interactive job attached to an MRT job if the job type is interactive.

N—The job is currently at a system menu. The Function Name field contains the name of the menu.

O—The job is a subsystem monitor that is performing I/O operations to a workstation. The Function Name field contains the name of the workstation device to which the subsystem is performing an I/O operation.

P—The job is running a program. The Function Name filed contains the name of the program.

R—The job is running a procedure. The Function Name field contains the name of the procedure.

*—This does a special function. For this value, the Function Name field contains one of these values



ADLACTJOB (Auxiliary storage is being allocated for the number of active jobs specified in the QADLACTJ system value. This may indicate that the system value for the initial number of active jobs is too low.)

ADLTOTJOB (Auxiliary storage is being allocated for the number of jobs specified in the QADLTOTJ system value.)

CMDENT (The command Entry display is being used.)

DIRSHD (Directory shadowing is occurring.)

DLTSPLF (The system is deleting a spooled file.)

DUMP (A dump is in process.)

JOBLOG (The system is producing a job log.)

Passthru (The job is a pass-through job.)

RCLSPLSTG (The empty spooled database members are being deleted.)

SPLCLNUP (The spool cleanup is in process.)

OS400_Job.Job_Queue The name of the job queue that the job is currently in, or that the job was in when it became active. The attribute monitors in the operational area of work management.

Valid Values

For jobs with a status of

� *JOBQ or *ACTIVE, an alphanumeric name with a maximum of 10 characters

� *OUTQ, the field is blank

OS400_Job.Job_Queue_Library The name of the library where the job queue is located. The attribute monitors in the operational area of work management.





OS400_Job.Job_Queue_Priority The scheduling priority of the job in the job queue. The attribute monitors in the operational area of work management.

Valid Values

For jobs with a status of

� *JOBQ or *ACTIVE, 0-9 (0 is the highest and 9 is the lowest.)

� *OUTQ, the field is blank

OS400_Job.Message_Queue The name of the message queue where the system sends a completion message when a batch job ends. This attribute monitors in the operational area of work management.

Valid Values� If the job has a submitter, an alphanumeric name with a maximum of 10

characters.

� If the job has no submitter, the filed is blank.

OS400_Job.Message_Queue_Library The name of the library that contains the message queue. The default is QSYS. The attribute monitors in the operational area of work management.



OS400_Job.Mode The mode name of the advanced program-to-program communications (APPC) device that started the job. The attribute monitors in the operational are of performance.





OS400_Job.Multiple_Request_Terminal_Job Multiple requester terminal (MRT) active job flag. The attribute monitors in the operational area of performance.

Valid Values

*YES—The active job is an MRT job.

*NO—The active job is not an MRT job.

OS400_Job.Name The name of the job. The attribute monitors in the operational areas of performance and work management.



Usage � For interactive jobs, the system assigns the job the name of the

workstation where the job started.

� For batch jobs, you specify the name in the command when you submit the job.

OS400_Job.Number The system assigned to the job. The attribute monitors in the operational areas of performance and work management.





Usage

If you substitute OS400_Job.Number into a CL command that requires an alphanumeric or character parameter, enclose the job number in apostrophes. For example, use ‘000123’ so that the CL command uses it as a character parameter.

OS400_Job.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Job.Passthru_Source Pass-through source-job flag. The attribute monitors in the operational area of performance.

Valid Values

*YES—The job is a pass-through source job.

*NO—The job is not a pass-through source job.

OS400_Job.Passthru_Target Pass-through target-job flag. The attribute monitors in the operational area of performance.

Valid Values

*YES—The job is a pass-through target job.

*NO—The job is not a pass-through target job.

OS400_Job.Pool Indicates the pool in which the job ran or is running. The attribute monitors in the operational area of performance.





OS400_Job.Priority Indicates the run priority over other jobs. The attribute monitors in the operational area of performance.


� in the range 1 (highest priority) to 9 (lowest priority)

OS400_Job.Response_Time The average transaction time (or average response time of the job) during the last monitor interval. The attribute monitors in the operational area of performance.


� in the range 0.0-2147483647.0

Usage


OS400_Job.Response_Time_Overall The average response time (in seconds) for interactive jobs. The program calculates the value by dividing OS400_Job.Transaction_Time_Overall by OS400_Job.Transaction_Count_Overall. The attribute monitors in the operational area of performance.


� in the range 0.0-214748364.7



Usage


OS400_Job.Submit_Date_and_Time The date and time the job left the job queue and started running. as put in the job queue. The attribute monitors in the operational area of work management.

Valid Values � If the job was not in the job queue, this field is blank.

� If the job was in the job queue, a date and time in the format CYYMMDDHHmmSSmmm (For example, 09610021030000000 indicates a century bit of 0, date of October 2, 1996 and a time of 10:30:00:000.)

OS400_Job.Submit_Time The time the job was put on this job queue. This attribute monitors in the operational area of work management.

Valid Values � If the job was in the job queue, a time in the format HHMMSS (For

example, 103000 is a time of 10:30:00 a.m.)

� If the job was not in the job queue, the field is blank.

OS400_Job.Subsystem The name of the subsystem that can retrieve the job from the queue. The attribute monitors in the operational areas of work management and performance.

Valid Values

For a job with a status of

� *ACTIVE, an alphanumeric name with a maximum of 10 characters

� *OUTQ or *JOBQ, the field is blank.



OS400_Job.Signed_On_User Indicates whether or not the job is to be treated like a user signed on to the system. The attribute monitors in the operational area of performance.

Valid Values

*YES—The job should be treated like a signed-on user.

*NO—The job should not be treated like a signed-on user.

OS400_Job.Start_Date_and_Time The date and time the job started. For batch jobs, this is the date and time the job left the queue and started running. This attribute monitors in the operational area of performance.

Valid Values � If the job became active, the date and time is in the format

CYYMMDDHHmmSSmmm. (For example, 9610021030000000 indicates a century bit of 0, date of October 2, 1996 and time of 10:30:00:000.)

� If the job did not become active, the field is blank.

OS400_Job.Start_Time The time the job started. The attribute monitors in the operational area of performance.

Valid Values � If the job became active, the time is in the format HHMMSS. (For

example, 10:30:00:000 indicates a time of 10:30:00:000.)

� If the job did not become active, the field is blank.

OS400_Job.Subtype Indicates the subtype of the job. This attribute monitors in the operational area of performance.

Valid Values



Blank—No special subtype *BCI—Immediate *EVK—Evoke job *PJ—Prestart job *PDJ—Print driver job *MRT—Multiple requester terminal (MRT) job *ALTSPLUSR—Alternate spool user

OS400_Job.Synch_I/O The rate of physical synchronous database and nondatabase read and write operations per second during the last monitor interval. This attribute monitors in the operational area of performance.


� 0-1000000

Usage


OS400_Job.S36_Environment Indicates whether or not the job is a System/36 environment job. This attribute monitors in the operational area of performance.

Valid Values

*YES—The job is a System/36 environment job.

*NO—The job is not a System/36 environment job.

OS400_Job.Timeslice The job time slice value (in seconds). This attribute monitors in the operational area of performance.




� in the range 0-2147483647

Usage


OS400_Job.Transaction_Count The number of transactions performed by the job during the last monitor interval. This attribute monitors in the operational area of performance.


� in the range 0-2147483647

Usage


OS400_Job.Transaction_Count_Overall Total number of interactive transactions performed by the job since the start of the job. This attribute monitors in the operational area of performance.


� in the range 0-2147483647

Usage


OS400_Job.Transaction_Time Transaction time (in seconds) accrued during the last monitor interval. The attribute monitors in the operational area of performance.




� in the range 0-2147483647

Usage


OS400_Job.Transaction_Time_Overall Total interactive job transaction time since the start of the job (in seconds). This attribute monitors in the operational area of performance.


� in the range 0-2147483647

Usage


OS400_Job.Type Indicates the type of job or task. This attribute monitors in the operational areas of performance and work management.

Valid Values

*ASJ—Autostart job *BATCH—Batch job Blank—No special type *HLIC—Horizontal Licensed Internal Code (HLIC) (tasks only) *INT—Interactive job *SBS—Subsystem monitor job *RDR—Spooled reader job *SYSTEM—System job *VLIC—Vertical Licensed Internal Code (VLIC) (tasks only) *WRITER—Spooled writer job *SCPF—Start-control-program-function (SCPF) system job



OS400_Job.User The user of the job. The user name is the same as the user profile name and can come from several different sources depending on the type of job. The attribute monitors in the operational areas of performance and work management.



OS400_Job_Queue.Library The name of the library that contains the job queue.



OS400_Job_Queue.Name The name of the job queue.



OS400_Job_Queue.Number_Jobs The number of jobs in the queue.



Usage




OS400_Job_Queue.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Job_Queue.Status The status of the job queue.

Valid Values

RELEASED—The job has been released.

HELD—The job is held.

OS400_Job_Queue.Subsystem The name of the subsystem that can retrieve jobs from the queue. The attribute monitors in the operational areas of work management and performance.

Valid Values � For a job with a status of *ACTIVE, an alphanumeric name with a

maximum of 10 characters.

� For a job with a status of *OUTQ and *JOBQ, the field is blank.


Line Description (OS400_Line) Attributes


OverviewThe OS/400 line description attributes are sampled attributes in the operational areas of communications and configuration.


OS400_Line.Category The category for the line description.

Valid Values


� *ASYNC

� *BSC

� *DDI

� *ELAN

� *ETH

� *FAX

� *FR

� *IDLC

� *NET

� *SDLC

� *TDLC

� *TRLAN

� *WLS

� *X25



OS400_Line.Name The name or identifier that describes the line.



OS400_Line.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Line.Status The status that indicates the status of the line.

Valid Values

00—VARIED OFF



30—VARIED ON


50—SIGNON DISPLAY

60—ACTIVE

63—ACTIVE READER

66—ACTIVE WRITER

70—HELD

75—POWERED OFF



80—RCYPND

90—RCYCNL

100—FAILED

103—FAILED READER

106—FAILED WRITER

110—DIAGNOSTIC MODE

111—DAMAGED

112—LOCKED

113—UNKNOWN

Message (OS400_Message) Attributes



OverviewThe OS/400 message attributes are notification attributes. These attributes refer to message queues. If you do not specify a value for the OS400_Message.Message_Queue attribute, it will default to QSYSOPR. If you do not specify a value for OS400_Message.Message_Queue_Library, it will default to QSYS. These attributes are in the operational area of work management. However, depending on the message they receive, they can have an impact on operational areas other than work management.


OS400_Message.Data Message help with substitution text. The text of a predefined message with the message data included. If an immediate message is listed, this field contains the immediate message text.



OS400_Message.Date_and_Time The date and time the message arrived in the message queue. When using the attribute, the event data is returned for all messages that satisfy the situation definition including those messages that arrived prior to when the monitoring for the situation.

Valid Values

Date and time in the format CYYMMDDHHmmSSmmm (For example, 096100210300000.)



OS400_Message.Help_Data Message help with the substitution text (The message help for the message is listed, including the message data. If an immediate message is listed, this field contains blanks.)



OS400_Message.ID The identifying code of the message received. If an immediate message is received, this field is blank.



OS400_Message.Key The key to the message received. The message key is a unique string of characters that identifies a particular instance of a message in a queue. The key is assigned by the command or attribute that sends the message. If the message-action parameter specifies *REMOVE, this field is blank.

Valid Values � hexadecimal number

OS400_Message.Message_Queue The name of the message queue. You cannot monitor the QHST message queue. QSYSOPR is the default.





OS400_Message.Message_Queue_Library The name of the library that contains the message queue. The default is QSYS.



OS400_Message.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Message.Select Filters by specifying the criteria for the type of message listed. The attribute allows you to do early filtering by specifying selection criteria for which types of messages are listed. Failing to specify this attribute may overload OMEGAMON XE for OS/400 and the situation will not evaluate. If this is the case, you are notified by a message in the OMEGAMON XE for OS/400 log that the situation did not evaluate. To view the message log, use the DSPOMALOG command.

Valid Values

*ALL—Displays all messages (default value).

* MNNR—Displays messages that do not require a reply are listed (This includes informational, completion, diagnostic, request notify, escape, reply, answered inquiry, answered sender’s copy messages.)

*MNR—Displays messages that need a reply (This includes unanswered inquiry messages.)

*PAR—Displays messages that have had a problem analysis run



*SCNR—Displays sender's copy messages requiring a reply (This includes only unanswered sender's copy messages.)

OS400_Message.Send_Job_Name The name of the job that sent the message.



OS400_Message.Send_Job_Number The number of the job that sent the message.



OS400_Message.Send_User The name of the user profile of the job that sent the message being received.



OS400_Message.Severity The severity level of the message received. The higher the number, the more severe the message.





OS400_Message.Time The time the message arrived in the message queue. (Messages received prior to the time when the situation is started will not be returned.)

Valid Values

A time in the format HHMMSS (For example, 103000 indicates a time of 10:30:00 a.m.)

OS400_Message.Type Indicates or identifies the type of message received.

Valid Values

01—Completion 02—Diagnostic 04—Informational 05—Inquiry 06—Sender's copy 08—Request 10—Request with prompting 14—Notify 15—Escape 21—Reply, not validity checked 22—Reply, validity checked 23—Reply, message default used 24—Reply, system default used 25—Reply, from system reply list


Tips and Techniques for Using the OS/400 Message Attributes


Overview You can use the OMEGAMON XE for OS/400 Message attributes to

� reply to inquiry messages using the Reflex Automation feature

� monitor for messages with specific IDs

� monitor for messages with specific words in the message text using the *SCAN function

Replying to inquiry messages using Reflex Automation

Background

There is a CL program (RPYMSG) that is packaged with the OMEGAMON XE for OS/400 that calls the SNDRPY command to reply to a specific inquiry message.

Using the Reflex Automation feature, you can call the RPYMSG program to send replies to inquiry messages.

Replying to inquiry messages using the Reflex Automation feature

1. Create a situation to monitor for inquiry message. To set up a situation to automatically reply to an inquiry message, first you need to create a situation using these message attributes.

OS400_Message.Type

OS400_Message.ID

If you specify a value equal to 05 for type and a value equal to CPA5305 for ID, you will monitor for the CPA5305 inquiry message in the QSYSOPR queue in the library QSYS. (This is the default queue which is always used unless another queue and library queue are specified.) To monitor another queue, add the Message Queue Name value and the Message Queue Library Name value as predicates for this situation.



For example, to monitor for an inquiry message with the ID CPA5305 create the following situation.

*IF *VALUE OS400_Message.Type *EQ 05 and *VALUE OS400_Message.ID *EQ CPA5305

CPA5305 is Record not added. Member <member_name> is full. This message requires either a c (cancel) or i (ignore and increment size).

2. Add Reflex Automation to reply to the messages. In the Situation Editor, after you have selected your situation predicates to monitor for inquiry messages, use the Action icon to display the Action window. In the Action window, call the RPYMSG program using the CALL command.

For example, specify the following command and parameters in the Action window.

CALL QUATOMON/RPYMSG PARM(‘&OS400_Message.Key’’&OS400_Message.Message_Queue’ ’&OS400_Message.Message_Queue_Library’ ‘c’).

The c indicates the reply text to send in the reply. The reply text can be any value that is expected by this message as a reply.

The Action window will automatically put spaces around each attribute name inside the single quotes. To use this command, you must

� remove the space inside the single quotes

� enclose the parameters single quotes

� put a space between each parameter enclosed in single quotes

Before closing the Action window, click on the Advanced button and select these radio buttons.

� Take action on each item (The command will reply to each message that is returned.)

� Take action in each interval (The command will reply to each message that is returned.)

� Execute the Action at each Managed System (by agent) (The RPYMSG command is on the same system as the agent.)

3. Customize the RPYMSG program.



The RPYMSG program is in the QAUTOMON library on the system on which the OMEGAMON XE for OS/400 is installed. You can retrieve this source and customize it by using this command on the OS/400 command line.

RTVCLSRC PGM(QAUTOMON/RPYMSG) SRCFILE(<your_library>/<your_source_file>)

Where <your_library> is the library that contains the source file in which to copy the CL source, and <your_source_file> is the name of the source file in which to copy the CL source.

The parameters for the RPYMSG program are

� Message Key (char[10])

� Message Queue Name (char[10])

� Message Queue Library Name (char[10])

� Reply Text (char[1])

Monitoring for message with specific IDs The OMEGAMON XE for OS/400 Message attributes can be used to monitor for critical messages by specifying the message IDs in the predicates of a situation. This type of situation can be used to monitor for any critical system message or group of messages such as security, operations, system processor, or disk. For example, the following situation would monitor for critical security messages.

*IF *VALUE OS400_Message.ID *EQ CPF1393 *OR *VALUE OS400_Message.ID *EQ CPF1397 *OR *VALUE OS400_Message.ID *EQ CP12283 *OR *VALUE OS400_Message.ID *EQ CP11393 *OR *VALUE OS400_Message.ID *EQ CP12209 *OR *VALUE OS400_Message.ID *EQ CP12284

Filtering messages using the *SCAN function The *SCAN function can be used in the predicate of a situation to filter which messages will cause the situation to become true. This can be used to monitor for critical messages that relate to a particular subsystem, job, or any other OS/400 object. The following formula is an example of how to use the *SCAN function.



*IF *VALUE OS400_Message.ID *EQ CPA5305 *AND *SCAN OS400_Message.Data *EQ KA4PFJOB

The situation will fire when the member KA4PFJOB is full. This situation is helpful if you are collecting historical data for the KA4PFJOB attribute group, and you want to make sure that KRARLOFF is being run before the member is full.


Network (OS400_Network) Attributes


Overview The OMEGAMON XE for OS/400 network attributes are sampled attributes in the operational area of communications. The OS400_Network.Alert attributes are also in the problem analysis operational area.


OS400_Network.Alert_Backup_Focal_Point Identifies the system that provides alert focal-point services if the local system is unavailable and ALRPRIFP is *YES. The backup focal point is only used by systems in the primary sphere of control.


� maximum 16 characters (The first 8 characters are the control point name and the last 8 characters are the network ID.)

� *NONE (indicates no backup focal point is defined)

OS400_Network.Alert_Controller The name of the controller to be used for alerts in a system service control point–physical unit (SSCP-PU) session. The controller is ignored if the system has a focal point, the node is in the control of another system.



� *NONE (indicates that no alert controller is defined)

OS400_Network.Alert_Default_Focal_Point Specifies whether or not the system is an alert default focal point.





OS400_Network.Alert_Filter The name of the filter object that is used by the alert manager when processing alerts.


� maximum 20 characters (The first 10 characters are the filter name, and the last 10 characters are the library name.)

� *NONE (indicates that no alert filter is being used)

OS400_Network.Alert_Hold_Count The maximum number of alerts to be created before the alerts are sent over the system service control point–physical unit (SSCP-PU) session. The system holds alerts until the number of alerts is created. If the Alert Controller (ALTCTLD) attribute is used to send alerts using the SSCP-PU session, alerts are sent automatically, regardless of the ALRHDCNT attribute, when a switched connection is made for other reasons.

Valid Values

*NOMAX or value with these characteristics

� integer

� in the range 0ϑ32767

OS400_Network.Alert_Log_Status Specifies which alerts are to be logged

Valid Values

*ALL—Both locally created alerts and incoming alerts are logged.



*LOCAL—Only locally created alerts are logged.

*NONE—No alerts are logged.

*RCV—Only alerts received from other nodes are logged.

OS400_Network.Alert_Primary_Focal_Point Specifies whether or not the system is an alert primary focal point.

Valid Values

*YES—The network is an alert primary focal point.

*NO—The network is not an alert primary focal point.

OS400_Network.Alert_Request_Focal_Point Specifies the name of the system that is requested to provide focal point services. If a focal point is already defined for the entry point, it is taken away when the new focal point is requested.



� *NONE (indicates no focal point is requested)

OS400_Network.Alert_Status Indicates how the alerts are created.

Valid Values

*OFF—Alerts are not created by the system.

*ON—Alerts are created by a system for all changeable conditions except unattended conditions.

*UNATTEND—Alerts are created by the system for all alert conditions including those that have the alert indicator in the message description set to *UNATTEND.



OS400_Network.APPN_Node_Type The type of advanced peer-to-peer networking (APPN) node.

Valid Values

*ENDNODE—The node does not provide network services to other nodes, but it may participate in the APPN network by using the services of an attached network server, or it may operate in a peer environment similar to migration end nodes.

*NETNODE—The node provides intermediate routing, route selection services, and distributed directory services for local users and to the end nodes and migration end nodes that it serves.

OS400_Network.Current_System_Name The name of the system that is currently being used.



OS400_Network.Defaut_Local_Location_Name The name of the default local location for the system.



OS400_Network.Default_Mode The name of the default mode for the system.





OS400_Network.Local_CPNAME The name of the local control point for the system.



OS400_Network.Local_NETID The ID assigned to the local network for the system.



OS400_Network.Max_Intermediate_Sessions The maximum number of advanced program-to-program communications (APPC) intermediate sessions for an Advanced Peer-to-Peer Networking (APPN) node type of *NETNODE.



OS400_Network.Message_Queue The name of the message queue used for messages

� received through the SNA distribution services (SNADS) network

� sent for users who have no message queue specified in their user profile, or users whose message queue is not available




� maximum 20 characters (The first 10 characters are the message queue name, and the last 10 characters are the library name.)

OS400_Network.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Network.Output_Queue The name of the output queue used for spooled files

� received through the SNA distribution services (SNADS) network

� sent for users whose output queue is not available


� maximum 20 characters (The first 10 characters are the output queue name and the last 10 characters are the library name.)

OS400_Network.Pending_System_Name If a change is pending, this is the pending system's name. A blank indicates that no change is pending.




Object (OS400_Object) Attributes


OverviewThe OS/400 object attributes are sampled attributes in the operational areas of storage and work management. These attributes retrieve object usage information for automation of auxiliary storage utilization. These attributes are in the operational areas of storage and work management.

Coding specific compare values for OS400_Object.Name, OS400_Object.Type and OS400_Object.Library reduces the amount of data OMEGAMON XE for OS/400 has to handle, which improves performance. Failing to specify one or more of these attributes will overload OMEGAMON XE for OS/400, which may result in situations not being evaluated. If this happens, a message in the OMEGAMON XE for OS/400 log will notify you that the situation did not evaluate. You can view the OMEGAMON XE for OS/400 log using the DSPOMALOG command.

Note: You can not use the OR function between any of the predicates when building situations using this group of attributes.


OS400_Object.Change_Date_and_Time The date and time the object was last changed.

Valid Values


OS400_Object.Change_Time The time the object was last changed.

Valid Values




OS400_Object.Compress_Status Indicates whether or not the object is compressed.

Valid Values

Y—The object is compressed.

N—The object is decompressed permanently and can be compressed.

X—The object is decompressed permanently and cannot be compressed.

T—The object is temporarily decompressed.

F—The compression status cannot be determined (storage freed when saved)

OS400_Object.Create_Date_and_Time The date and time the object was created.

Valid Values


OS400_Object.Create_Time The time the object was created.

Valid Values


OS400_Object.Extended_Attribute The extended attribute for the object such as the program or file type that further describes the object. For example, an object type of *PGM may have a value of RPG (RPG program) or CLP (CL program), and an object type of *FILE may have a value of PF (physical file), LF (logical file), DSPF (display file), or SAVF (save file).

Valid Values



� alphanumeric


OS400_Object.Last_Used_Date_and_Time The date the object was last used, with the time (HHMMSS) set to 0. If the object has no last used date, the field is blank.

Valid Values


OS400_Object.Last_Used_Time The time the object was last used.

Valid Values


OS400_Object.Library The name of the library containing the object.



OS400_Object.Licensed_Program If the object is part of a licensed program, the name, release level, and modification level of the licensed program. (The filed is blank if the retrieved object is not part of a licensed program.)

Valid Values



The 7-character name starts in character position 1, the version number starts in position 8, the release level starts in position 11, and the modification level starts in position 14.

OS400_Object.Name The name of the object.



OS400_Object.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Object.Owner The name of the user profile that owns the object.



OS400_Object.Percent_Days_Used The percentage of days that the object was actually used since the days-used count was last reset to 0.





Usage


OS400_Object.PTF_Number The number of the program temporary fix (PTF) that caused this object to be replaced. This field is blank if the object was not changed because of a PTF.



OS400_Object.Operating_System_Level The level of the operating system when the object was created.

Valid Values

A value in the format VvvRrrMmm (The V is followed by a 2-character version number, the R is followed by a 2-character release level, and the M is followed by a 2-character modification level.)

OS400_Object.Restore_Date_and_Time The date and time at which the object was restored. If the object has never been restored, the field is blank.

Valid Values

Date and time in the format CYYMMDDHHmmSSmmm (For example, 0961002103000000 indicates a century bit of 0, a date of October 2, 1996, and a time of 10:30:000.)

OS400_Object.Restore_Time The time the object was restored. If the object has never been restored, the field is blank.



Valid Values


OS400_Object.Save_Command The command used to save the object. The field is blank if the object was not saved.



OS400_Object.Save_Date_and_Time The date and time at which the object was last saved. If the object has never been saved, the field is blank.

Valid Values


OS400_Object.Save_Device_Type The type of device to which the object was last saved.

Valid Values

Blank—The object was not saved

*SAVF—The object was saved to a save file

*DKT—The object was saved to a diskette

*TAP—The object was saved to a tape

OS400_Object.Save_File If the object was saved to a save file, the name of the save file. The field is blank if the object was not saved to a save file.





OS400_Object.Save_Library If the object was not saved to the save file, the name of the library that contains the save file. The field is blank if the object was not saved.



OS400_Object.Save_Time The time the object was last saved. If the object has never been saved, the field is blank.

Valid Values


OS400_Object.True_Size The approximate size of the object. If the object is smaller than 1,000,000,000 bytes, the value is exact. The value is within 1024 larger than the actual size if the object is larger than 1,000,000,000 bytes.


� in the range 0-2147483647

Usage




OS400_Object.Type The type of the object.

Valid Values

*ALRTBL—Alert table *AUTL—Authorization list *BNDDIR—Binding directory *CFGL—Configuration list *CHTFMT—Chart format *CLD—C description *CLS—Class *CMD—Command *CNNL—Connection list *COSD—Class-of-service description *CSI—Communications Side Information *CSPMAP—Cross System Product map *CSPTBL—Cross System Product table *CTLD—Controller description *DEVD—Device description *DOC—Document *DTAARA—Data area *DTADCT—Data dictionary *DTAQ—Data queue *EDTD—Edit description *FCT—Forms control table *FILE—File *FLR—Folder *FNTRSC—Font resources *FORMDF—Form definition *FTR—Filter *GSS—Graphics symbol set *IGCDCT—Double-byte character set (DBCS) conversion dictionary *IGCSRT—Double-byte character set (DBCS) sort table *IGCTBL—Double-byte character set (DBCS) font table *JOBD—Job description *JOBQ—Job queue *JOBSCD—Job schedule *JRN—Journal



*JRNRCV—Journal receiver *LIB—Library *LIND—Line description *MENU—Menu description *MODD—Mode description *MODULE—Compiler unit *MSGF—Message file *MSGQ—Message queue *NODL—Node list *NWID—Network interface description *OUTQ—Output queue *OVL—Overlay *PAGDFN—Page definition *PAGSEG—Page segment *PDG—Print Descriptor Group *PGM—Program *PNLGRP—Panel group definition *PRDAVL—Product availability *PRDDFN—Product definition *PRDLOD—Product load *QMFORM—Query management form *QMQRY—Query management query *QRYDFN—Query definition *RCT—Reference code translation table *SBSD—Subsystem description *SCHIDX—Information search index *SPADCT—Spelling aid dictionary *SRVPGM—Service program *SQLPKG—Structured Query Language package *SSND—Session description *S36—System/36 machine description *TBL—Table *USRIDX—User index *USRPRF—User profile *USRQ—User queue *USRSPC—User space *WSCST—Workstation customizing object



OS400_Object.Use_Reset_Date_and_Time The date and time the days-used count was last reset to 0. If the days-used count was not reset, the date and time is blank.

Valid Values


OS400_Object.Use_Reset_Time The time when the days-used count was last reset to 0. If the days-used count was not reset, the time is blank.

Valid Values



Storage Pool (OS400_Storage_Pool) Attributes


OverviewThe OS/400 storage pool attributes are sampled attributes in the operational areas of performance and storage. These attributes allow you to collect information about pool performance based on the cumulative values of storage pool counters. These attributes are in the operational areas of performance, work management, and storage.


OS400_Storage_Pool.Activity_Level The maximum number of processes that can be active in the pool at the same time.



Usage


OS400_Storage_Pool.Active_to_Ineligible For the processes assigned to this pool, this attribute is the rate of active-to-ineligible transitions per second during the last monitor interval. (Such a transition results when a transaction does not complete during a single time slice.)


� in the range 0ϑ2147483647

Usage




OS400_Storage_Pool.ATI_ATW_Ratio The ratio from OS400_Storage_Pool.Active_to_Ineligible to OS400_Storage_Pool.Active_to_Wait.



OS400_Storage_Pool.Database_Fault The rate of interruptions to processes per second. The interruptions were required to transfer data into the pool, which permitted work to be done on the database function during the last monitor interval.


� in the range 0-214743647

Usage


OS400_Storage_Pool.Number The unique identifier for the storage pool.



Usage




OS400_Storage_Pool.Nondatabase_Fault The rate of interruptions to processes per second. The interruptions were required to transfer data into the pool, which permitted work to be done on the nondatabase function during the last monitor interval.


� in the range 0-2147483647

Usage


OS400_Storage_Pool.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Storage_Pool.Size The amount of main storage assigned to the pool (in kilobytes)


� in the range 0-2147483647

Usage




OS400_Storage_Pool.Total_Fault Total number of interruptions to processes per second required to transfer data into the pool to permit work to continue on both database and nondatabase functions. The attribute is the sum of these values

� OS400_Storage_Pools.Database_Fault

� OS400_Storage_Pool.Nondatabase_Fault


� in the range 0-2147483647

Usage


OS400_Storage_Pool.Wait_to_Ineligible For the processes assigned to this pool, this attribute is the rate of wait-to-ineligible transitions per second during the last monitor interval. Such a transition results when a job is leaving a wait state but there is no available activity level.


� in the range 0-2147483647

Usage


OS400_Storage_Pool.WTI_ATW Ratio The ratio of OS400_Storage_Pool.Wait_to_Ineligible to OS400_Storage_Pool.Active_to_Wait




� in the range 0.0-32767.0

Subsystem (OS400_Subsystem) Attributes



OverviewThe OS/400 subsystem attributes are sampled attributes in the operational area of work management. Using these attributes all subsystems are monitored, not just active ones.


OS400_Subsystem.Current_Jobs_Active The number of jobs currently active in the subsystem. This number includes held jobs, but it excludes jobs that are disconnected or suspended because of a transfer secondary job or transfer group job.



Usage


OS400_Subsystem.Description_Library The name of the library where the subsystem description is stored.



OS400_Subsystem.Max_Jobs_Active The maximum number of jobs that can run or use resources in the subsystem at one time. If the subsystem description specifies *NOMAX, indicating that there is no maximum, the value is -1.

Valid Values



� integer


Usage


OS400_Subsystem.Name The name of the subsystem about which information is being returned.



OS400_Subsystem.Number_Pools The number of storage pools defined for the subsystem.



OS400_Subsystem.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Subsystem.Pool_Activity_Level The maximum number of jobs that can be active in the pool at one time. If the pool name indicated a system-defined pool, the number returned is 0.




� in the range 0ϑ��

OS400_Subsystem.Pool_Name The name of the pool for the subsystem.

Valid Values


� *USERPOOL

� *BASE

� *INTERACT

� *NOSTG

� *SHRPOOL1

� *SHRPOOL2

� *SHRPOOL3

� *SHRPOOL4

� *SHRPOOL5

� *SHRPOOL6

� *SHRPOOL7

� *SHRPOOL8

� *SHRPOOL9

� *SHRPOOL10

� *SPOOL

OS400_Subsystem.Status The status of the subsystem.

Valid Values



*ACTIVE—The status is active (default value).

*INACTIVE—The status is inactive.

Security Journal (OS400_Security_Jrn) Attributes



OverviewThe OS/400 security journal attributes are in the security operational area. The attributes in the following section receive audit journal entries.

Note: Note: In order to use the OS400_Security_Jrn attributes the Auditing journal, QAUDJRN, must exist in library QSYS. In addition, you must have created some journal receivers and attached them to the Auditing journal.

The OS400_Security_Jrn attributes are broken down into Entry Type categories. For example, the OS400_Security_Jrn_ChgAuth attributes are in the change authority failure journal. The OS400_Security_ChgOwner deal with ownership change. What Entry Type auditing is occurring is determined by QAUDLVL System Value. This means if you start a situation monitoring for OS400_Security_AuthFail_User, you need to include *AUTFAIL in the QAUDLVL System Value and set QAUDCTL System Value to *AUDLVL. The following table lists the values in QAUDLVL and Entry Types for which they turn on monitoring.

Table 5. QUADLVL Values and Entry Types

QUADLVL Value Auditing for Entry Type

*ALL YR

ZR

*AUTFAIL AF

PW

*CHANGE YC

ZC

*CMD CD

*CREATE CO

*DELETE DO

*JOBDTA JS



*OBJMGT OM

*OFCSRV ML

SD

*PGMADP AP

*PGMFAIL AF

PTRDTA PO

*SAVRST OR

RA

RJ

RO

RP

RU

*SECURITY AD

CA

CP

DS

JD

NA

OW

PA

PS

SE

SV

*SERVICE ST

*SPLFDTA SF

*SYSMGT SM

Table 5. QUADLVL Values and Entry Types

QUADLVL Value Auditing for Entry Type



Effects of changes to QDATE and QTIMEChanging the system value QDATE and QTIME will affect when OS400_Security_Jrn events are picked up.

For example, if you change the system values to a future date or time, such as the year 2000, then any journal entries that occur are marked with this future date. When you change the system values back to the current date, any subsequent journal entries are correctly marked with the current date. Modifying the system value in this way results in having older journal entries marked with a more recent date.

If you start a journal situation, it returns all journal entries that have a date and time equal to or greater than the current date. If it finds an older entry that is pre-dated with the year 2000 date, the situation returns all entries following the year 2000 entry. Some of these entries would have occurred before the situation was started. If a large number of these journal entries exist, they could cause the situation to time out. To avoid this problem, remove the current journal receiver or receivers from the JRN and create and attach a new one.

Predicates for the OS400_Security _Jrn attributesSituations based on the OS400_Security_Jrn attributes should contain at least one predicate with an attribute that does not begin with OS400_Security_Jrn_Audit_Jrn. If a situation is started that contains only audit journal attributes, the amount of data that OMEGAMON XE for OS/400 must process will be too large. This will degrade performance and the situation may be ended with an error.

Note: Note: You must specify the OS400_Security_Jrn.AuditJrn.Entry_Type attribute when you create a situation using the OS400_Security_Jrn.AuditJrn attribute group.

Refer to the OS/400 manual Security-Reference for more information on auditing journal management.


Authority Failure (AuthFail) Journal Entries


OverviewAuthority failure (AuthFail) journal entries describe authority failures.


OS400_Security_Jrn_AuthFail.Job_Name The name of the job.



OS400_Security_Jrn_AuthFail.Job_Number The number the system assigned to the job.



OS400_Security_Jrn_AuthFail.Object The name of the object.



OS400_Security_Jrn_AuthFail.Object_Library The name of the library that contains the object.





OS400_Security_Jrn_AuthFail.Object_Type The type of object.

Valid Values

*ALRTBL—Alert table *AUTL—Authorization list *BNDDIR—Binding directory *CFGL—Configuration list *CHTFMT—Chart format *CLD—C description *CLS—Class *CMD—Command *CNNL—Connection list *COSD—Class-of-service description *CSI—Communications Side Information *CSPMAP—Cross System Product map *CSPTBL—Cross System Product table *CTLD—Controller description *DEVD—Device description *DOC—Document *DTAARA—Data area *DTADCT—Data dictionary *DTAQ—Data queue *EDTD—Edit description *FCT—Forms control table *FILE—File *FLR—Folder *FNTRSC—Font resources *FORMDF—Form definition *FTR—Filter *GSS—Graphics symbol set *IGCDCT—Double-byte character set (DBCS) conversion dictionary *IGCSRT—Double-byte character set (DBCS) sort table *IGCTBL—Double-byte character set (DBCS) font table *JOBD—Job description *JOBQ—Job queue



*JOBSCD—Job schedule *JRN—Journal

*JRNRCV—Journal receiver *LIB—Library *LIND—Line description *MENU—Menu description *MODD—Mode description *MODULE—Compiler unit *MSGF—Message file *MSGQ—Message queue *NODL—Node list *NWID—Network interface description *OUTQ—Output queue *OVL—Overlay *PAGDFN—Page definition *PAGSEG—Page segment *PDG—Print Descriptor Group *PGM—Program *PNLGRP—Panel group definition *PRDAVL—Product availability *PRDDFN—Product definition *PRDLOD—Product load *QMFORM—Query management form *QMQRY—Query management query *QRYDFN—Query definition *RCT—Reference code translation table *SBSD—Subsystem description *SCHIDX—Information search index *SPADCT—Spelling aid dictionary *SRVPGM—Service program *SQLPKG—Structured Query Language package *SSND—Session description *S36—System/36 machine description *TBL—Table *USRIDX—User index *USRPRF—User profile *USRQ—User queue *USRSPC—User space



*WSCST—Workstation customizing object

OS400_Security_Jrn_AuthFail.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Security_Jrn_AuthFail.User The name of the user that caused the audit journal entry.



OS400_Security_Jrn_AuthFail.Validation_Value The type of cyclic redundancy check (validation value), which is set only if the violation type is C.

Valid Values

A—A changed object that may violate security was restored. B—All authority revoked when object was restored. C—A copy was restored of the program that was translated. D—The security requested that the changed object was restored. E—Detection of a system install-time error.

OS400_Security_Jrn_AuthFail.Violation_Type The type of security violation that occurred.

Valid Values

A—A user attempted to perform an operation or access an object without the required authority.



B—A restricted machine interface instruction was run by a program.

C—A program was restored that failed the restore-time program validation checks. Information about the failure is in the Validation Value Violation Type field of the record. (See Security_Jrn_AuthFail.Validation_Value)

D—A program attempted to access an object using an interface that is not supported or a callable program that is not in the callable API list.

J—A submitter without *USE authority for a user profile attempted to submit or schedule a job using the user profile. Submitter did not have *USE authority to the user profile.

P—The use was attempted of a profile handle that is not valid on the QWTSETP API.

R—An update was attempted to an object that is read only. (Enhanced hardware storage protection is logged only at security level 40.)

S—A sign-on was attempted without a user ID and password.

General Security (AuditJrn) Attributes



OverviewThe OS/400 security audit journal entries track all changes relating to system security. The attributes in this section apply to all audit journal entries.


OS400_Security_Jrn_AuditJrn.Entry_Type The type of entry written to the audit journal.

Note: Note: You must specify the OS400_Security_Jrn.AuditJrn.Entry_Type attribute when you create a situation using the OS400_Security_Jrn.AuditJrn attribute group. If you do not use the attribute in a predicate, the program stops the situation.

Valid Values

AF—Authority failure CA—Authority changes CP—User profile changes, created, or restored DS—DST security password reset JD—Change to user parameter of a job description NA—Network attribute changed OW—Object ownership changed PA—Program changed to adopt authority PS—Profile swap PW—Password not valid RA—Authority change during restore RJ—Restoring job description with user profile specified RO—Change of object owner during restore RP—Restoring adopted authority program RU—Restoring user profile authority



SE—Subsystem routing entry change SV—System value changed

OS400_Security_Jrn_AuditJrn.Job_Name The name of the job that caused the entry to be written in the audit journal.



OS400_Security_Jrn_AuditJrn.Job_Number The job number of the job which caused the entry to be written in the audit journal.



OS400_Security_Jrn_AuditJrn.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Security_Jrn_AuditJrn.User_Profile The name of the current user profile associated with the job.



Change Authority (ChgAuth) Journal Entries



OverviewChange authority (ChgAuth) journal entries describe changes to authorization lists or object authority.


OS400_Security_Jrn_ChgAuth.ADD Indicates whether or not there has been a change to add authority.

Valid Values

*YES—ADD authority granted or revoked

*NO—The authority has not changed.

OS400_Security_Jrn_ChgAuth.Auth_List_Name The name of the authorization list.



OS400_Security_Jrn_ChgAuth.AUTLMGT Indicates whether or not there has been a change to *AUTLMGT or *AUTL public authority.

Valid Values

*YES—AUTLMGT authority or *AUTL public authority has been granted or revoked.

*NO—There has been no change to authority.



OS400_Security_Jrn_ChgAuth.Command_Type Indicates the type of command used.

Valid Values

GRT—Grant

RVK—Revoke

OS400_Security_Jrn_ChgAuth.DLT Indicates whether or not there has been a change to delete authority.

Valid Values

*YES—DLT authority has been granted or revoked.




OS400_Security_Jrn_ChgAuth.EXCLUDE Indicates whether or not there has been change to exclude authority.

Valid Values

*YES—EXCLUDE authority has been granted or revoked.


OS400_Security_Jrn_ChgAuth.Job_User The name of the user profile whose authority is being granted or revoked.



OS400_Security_Jrn_ChgAuth.Object_Name The name of the object.



OS400_Security_Jrn_ChgAuth.OBJEXIST Indicates whether or not there has been a change to object authority.

Valid Values

*YES—OBJEXIST authority has been granted or revoked.


OS400_Security_Jrn_ChgAuth.Object_Library_Name The name of the library that contains the object.

Valid Values



� alphanumeric


OS400_Security_Jrn_ChgAuth.OBJMGT Indicates whether or not there has been a change to object management authority.

Valid Values

*YES—OBJMGT authority granted or revoked.


OS400_Security_Jrn_ChgAuth.OBJOPR Indicates whether or not *OBJOPR authority has been changed.

Valid Values

*YES—OBJOPR authority has been granted or revoked.


OS400_Security_Jrn_ChgAuth.Object_Type The type of object.



OS400_Security_Jrn_ChgAuth.ORIGINNODEThe host name for the monitored system.


� alphanumeric




OS400_Security_Jrn_ChgAuth.READ Indicates whether or not there has been a change to read authority.

Valid Values

*YES—READ authority has been granted or revoked.


OS400_Security_Jrn_ChgAuth.UPDATE Indicates whether or not there has been a change to update authority.

Valid Values

*YES—UPD authority has been granted or revoked.



User Profile Change (CP) Journal Entries


OverviewUser profile change (ChgUserProf) journal entries describe a create, change, or restore operation to the user profile.


OS400_Security_Jrn_ChgUserProf.ALLOBJ Indicates whether or not all object authority has been changed. All object authority allows users to work with system resources, such as applying program temporary fixes (PTFs).

Valid Values

*YES—ALLOBJ special authority has been granted or revoked.

*NO—The authority has no changed.

OS400_Security_Jrn_ChgUserProf.Command_Type The type of command used.

Valid Values

CRT—Create User Profile (CRTUSRPRF) command

CHG—Change User Profile (CHGUSRPRF) command

RST—Restore User Profile (RSTUSRPRF) command

DST—Change Dedicated Service Tools Password (CHGDSTPWD) command

OS400_Security_Jrn_ChgUserProf.JOBCTL Indicates whether or not job control authority has been changed. Job control authority allows user to work with jobs, such as changing, holding, and cancelling.

Valid Values

*YES—JOBCTL special authority has been granted or revoked.




OS400_Security_Jrn_ChgUserProf.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Security_Jrn_ChgUserProf.Password_Changed Indicates whether or not the password has changed for the user profile.

Valid Values

*YES—Indicates the password for the user profile has changed.

*NO— Indicates there has been no change to the password for the user profile.

OS400_Security_Jrn_ChgUserProf.Password_Expired Indicates whether or not a password has expired

Valid Values

*YES—Password is expired.

*NO—Password did not expire.

OS400_Security_Jrn_ChgUserProf.SAVSYS Indicates whether or not save system authority has been changed. Save system authority allows users to save, restore, and free storage for system objects.

Valid Values

*YES—SAVSYS special authority has been granted or revoked.




OS400_Security_Jrn_ChgUserProf.SECADM Indicates whether or not security administrator authority has been changed. A security administrator can create, change or delete user profiles.

*YES—SECADM special authority has been granted or revoked.


OS400_Security_Jrn_ChgUserProf.SERVICE Indicates whether or not service authority has been changed. Service authority allows users to perform service functions, such as working with the problem log.

Valid Values

*YES—SERVICE special authority has been granted or revoked.


OS400_Security_Jrn_ChgUserProf.SPLCTL Indicates whether or not spool control authority has been changed. Spool control authority allows users to perform all spool-related functions.

Valid Values

*YES—SPLCTL special authority has been granted or revoked.


OS400_Security_Jrn_ChgUserProf.USER The name of the user profile that was changed.



Job Description (JobDesc) Attributes



OverviewThe job description security journal entries describe changes to job descriptions and job owners.

OS400_Security_Jrn_JobDesc.Job_Description Indicates that a change to the name of the job description was logged to the audit journal.



OS400_Security_Jrn_JobDesc.New_User Indicates the new name of the user profile specified for the USER parameter that was logged to the audit journal.



OS400_Security_Jrn_JobDesc.Old_User Indicates the old name of the user profile specified for the USER parameter that was logged to the audit journal.



OS400_Security_Jrn_JobDesc.ORIGINNODEThe host name for the monitored system.




� alphanumeric


Network Attribute Change (Network) Journal Entries



OverviewNetwork attribute change (Network) journal entries describe changes to network attributes.


OS400_Security_Jrn_Network.Changed_Attribute Indicates a change to the named network attribute was logged to the audit journal.

Valid Values

SYSNAME—Current system name

PNDSYSNAME—Pending system name

LCLNETID—Local network ID

LCLCPNAME—Local control point name

LCLLOCNAME—Local location name

DFTMODE—Default mode name

NODETYPE—APPN node type

DTACPR—Current level of data compression

DTACPRINM—Current level of intermediate node data compression

MAXINTSSN—Maximum number of intermediate sessions

RAR—Route addition resistance

NETSERVER—List of network node servers

ALRSTS—Alert status

ALRPRIFP—Alert primary focal point

ALRDFTFP—Alert default focal point

ALRLOGSTS—Alert logging status



ALRBCKFP—Name of the system that provides alert focal point services if the primary focal point is unavailable

ALRRQSFP—Name of the system that is requested to provide alert focal point services

ALRCTLD—Name of the controller through which alert messages are sent on a SSCP-PU session

ALRHLDCNT—Maximum number of alerts that are created before the alerts are sent over the alert controller session (ALRCTLD network attribute)

ALRFTR—Name of the active alert filter

ALRFTRLIB—Name of the library that contains the alert filter definition

MSGQ—Name of the system-default network message queue

MSGQLIB—Name of the library that contains the system-default message queue

OUTQ—Name of the system-default network output queue

OUTQLIB—Name of the library that contains the system-default network message queue

JOBACN—Current job action for job streams received through the network

MAXHOP—Maximum number of times in the SNADS network that a distribution queue originating at this node can be received and rerouted on the path to its final destination

DDMACC—Current system action for DDM requests from other systems

DDMACCLIB—Name of the library that contains the DDM access program

PCSACC—Current system action for Client Access for OS/400 requests

PCSACCLIB—Name of the library that contains the Client Access for OS/400 access program

DFTNETTYPE—System default value for the Integrated Services Digital Network (ISDN) network type

DFTCNNLST—System default value for the ISDN connection list



OS400_Security_Jrn_Network.New_Attribute_Value The value of the network attribute after it was changed.



OS400_Security_Jrn_Network.Old_Attribute_Value The value of the network attribute before it was changed.



OS400_Security_Jrn_Network.ORIGINNODEThe host name for the monitored system.


� alphanumeric



Ownership Change (ChgOwner) Journal Entries


OverviewOwnership change (ChgOwner) journal entries indicate changes to object ownership.


OS400_Security_Jrn_ChgOwner.New_Owner The new owner of the object who logged a change in ownership to the audit journal.



OS400_Security_Jrn_ChgOwner.Object_Name The name of the object.



OS400_Security_Jrn_ChgOwner.Object_Library The name of the library that contains the object.



OS400_Security_Jrn_ChgOwner.Object_Type The type of object.





OS400_Security_Jrn_ChgOwner.Old_Owner The previous owner of the object that logged a change in ownership to the audit journal.



OS400_Security_Jrn_ChgOwner.ORIGINNODEThe host name for the monitored system.


� alphanumeric



Program Adopt (ProgAdopt) Journal Entries


OverviewProgram adopt (ProgAdopt) journal entries indicate that a program has been changed to adopt owner authority.


OS400_Security_Jrn_ProgAdopt.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Security_Jrn_ProgAdopt.Owner The name of the owner who logged a program adopt change to the audit journal.



OS400_Security_Jrn_ProgAdopt.Program_Name The name of the program.





OS400_Security_Jrn_ProgAdopt.Program_Library The name of the library where the program is found.




Profile Swap (ProfSwap) Journal Entries


OverviewThe following section lists profile swap (ProfSwap) journal entry attributes, which indicate that a user or job has changed user profiles while performing system operations.


OS400_Security_Jrn_ProfSwap.Entry_Type The type of entry.

Valid Values

A—Profile swap during pass-through

H—Profile handle generated by the Get Profile Handle (QSYGETPH) API

OS400_Security_Jrn_ProfSwap.New_Target A new pass-through target user profile logged to the audit journal.



OS400_Security_Jrn_ProfSwap.Old_Target The original pass-through target user profile logged to the audit journal.



OS400_Security_Jrn_ProfSwap.ORIGINNODEThe host name for the monitored system.




� alphanumeric


OS400_Security_Jrn_ProfSwap.Source_Location The pass-through source location logged to the audit journal.



OS400_Security_Jrn_ProfSwap.User_Profile User profile name.




Password (Password) Journal Entries


OverviewPassword (Password) journal entries indicate that an incorrect password or an incorrect user ID was entered.


OS400_Security_Jrn_Password.Device_Name The name of the device where the password or user ID was entered.



OS400_Security_Jrn_Password.Job_User The system name of the person using the job.



OS400_Security_Jrn_Password.ORIGINNODEThe host name for the monitored system.


� alphanumeric




OS400_Security_Jrn_Password.Violation_Type Indicates whether the security violation was the result of an invalid user ID or password.

Valid Values

P—Password is not valid

U—User ID is not valid.


Restoring Job Description (RestoreJob) Journal Entries


OverviewRestoring job description (RestoreJob) journal entries indicate that a job description containing a user profile name has been restored.


OS400_Security_Jrn_RestoreJob.Job_Description The name of the job description that was restored and logged to the audit journal.



OS400_Security_Jrn_RestoreJob.Job_Description_Library The name of the library to which the job description was restored.



OS400_Security_Jrn_RestoreJob.ORIGINNODEThe host name for the monitored system.


� alphanumeric




OS400_Security_Jrn_RestoreJob.User The name of the user profile specified in the job description.




Restoring Program (RestoreProg) Journal Entries


OverviewRestoring program (RestoreProg) journal entries indicate that a job adopting owner authority has been restored.


OS400_Security_Jrn_RestoreProg.ORIGINNODEThe host name for the monitored system.


� alphanumeric


OS400_Security_Jrn_RestoreProg.Program The name of the restored program.



OS400_Security_Jrn_RestoreProg.Program_Library The name of the library where the program is found.



OS400_Security_Jrn_RestoreProg.Program_Owner The name of the owner of the program.






System Value (SYSVAL) Journal Entries


OverviewSystem value (SYSVAL) journal entries indicate that a system value has been changed.


OS400_Security_Jrn_SYSVAL.New_Value The value of the system value after it was changed.



OS400_Security_Jrn_SYSVAL.Old_Value The value of the system value before it was changed.



OS400_Security_Jrn_SYSVAL.ORIGINNODEThe host name for the monitored system.


� alphanumeric




OS400_Security_Jrn_SYSVAL.System_Name The name of the system value that was changed and logged to the audit journal.




Spool File (OS400_Spool_File) Attributes


OverviewThe OS/400 spool file attributes are sampled attributes in the operational are of output.

Coding these specific compare values for together reduces the amount of data OMEGAMON XE for OS/400 has to handle, which improves performance.

� OS400_Spool_File.Output_Queue_Name

� OS400_Spool_File.Output_Queue_Library

� OS400_Spool_File.Form_Type

� OS400_Spool_File.User_Data

� OS400_Spool_File.Job_User Under

Certain circumstances (especially on large systems), failing to specify one or more of these attributes may overload OMEGAMON XE for OS/400. The result is that OMEGAMON XE for OS/400 will not evaluate the situation. In this case, you are notified by a message in the OMEGAMON XE for OS/400 message log that the situation did not evaluate. To view the OMEGAMON XE for OS/400 message log, use the DSPOMALOG command.


OS400_Spool_File.Copies The remaining number of copies to be produced on the printer. (The page number may be lower or higher than the page number actually being printed because of buffering done by the system.)



Usage




OS400_Spool_File.Current_Page The page number or record number currently being written. The page number may be lower or higher than the page number actually being printed because of buffering done by the system. The page number shown may be zero if

� The printer file is routed to a diskette unit.

� The writer is currently printing job or file separators for the file.



Usage


OS400_Spool_File.Date_and_Time The date and time that the file was opened.

Valid Values


OS400_Spool_File.Device The name of the device file used to create the spooled file.



OS400_Spool_File.Form_Type The type of form to be loaded in the printer to print this file.





OS400_Spool_File.Job_Name The name of the job that created the spooled file.



OS400_Spool_File.Job_Number The number of the job that created the spooled file.



Usage


OS400_Spool_File.Job_User The name of the user that created the spooled file.



OS400_Spool_File.ORIGINNODEThe host name for the monitored system.

Valid Values



� simple text string

� alphanumeric


OS400_Spool_File.Output_Queue_Name The name of the output queue where the file is located.



OS400_Spool_File.Output_Queue_Library The name of the library that contains the output queue.



OS400_Spool_File.Page The number of pages this printer file contains.



Usage


OS400_Spool_File.Priority The priority of the spooled file (or importance of printing order).

Valid Values



� integer

� in the range 1 (highest priority) to 9 (lowest priority).

OS400_Spool_File.Status Indicates the status of the file.

*CLOSED—The program completely processed the file but SCHEDULE(*JOBEND) was specified and the job that produced the file has not yet finished.

*HELD—The file is held.

*MESSAGE—The file has a message requiring a reply or an action.

*OPEN—The file was not completely processed and is not ready for a writer.

*PENDING—The file is waiting to be printed.

*PRINTER—The complete file was sent to the printer but a print complete status was not sent back.

*READY—The file is available to be written.

*SAVED—The file was written and is saved. This file remains saved until it is released.

*WRITING—The writer is writing the file on a diskette or a printer device.

OS400_Spool_File.Time The time that the file was opened.

Valid Values

Time in the format HHMMSS (For example 102000 indicates a time of 10:30:00 a.m.)

OS400_Spool_File.User_Data The ten characters of user-specified data that describe the file.






System Status (OS400_System_Status) Attributes


OverviewThe OS/400 system status attributes are sampled attributes in the operational areas of performance and work management.


OS400_System_Status.AuxStorPool_Percent_Used The percentage of the system storage pool currently in use. When checksum protection is in effect, this percentage refers only to protected storage currently in use. Otherwise, it is the percentage of the total system storage pool currently in use.


� in the range 0.0000-100.0000

OS400_System_Status.CPU_Percent The average percent of the elapsed time during which the processing units were in use.



OS400_System_Status.ORIGINNODEThe host name for the monitored system.


� alphanumeric




OS400_System_Status.Perm_Address_Percent_Used The percentage (in thousandths) of the maximum possible addresses for permanent objects that have been used. The range is 0.000 to 100.000.


� in the range 0.000-100.000

OS400_System_Status.Temp_Address_Percent_Used The percentage (in thousandths) of the maximum possible addresses for temporary objects that have been used.


� in the range 0.000-100.000

OS400_System_Status.Total_Job_Count The total number of user jobs and system jobs that are currently in the system. The total includes all jobs on job queues waiting to be processed, all jobs currently being processed, and all jobs that have completed running but still have output on output queues to be Tproduced.




System Values (OS400_System_Values) Attributes


OverviewThe OS/400 system values attributes are sampled attributes in the operational area of configuration. These attributes monitor a subset of OS/400 system values. For more information on about OS/400 system values or to change a system value, see the OS/400 manual Work Management.


OS400_System_Values_Acct.QABNORMSW Indicates the status of a previous end of a system.

Valid Values

*YES—Previous end of system was abnormal.

*NO—Previous end of system was normal.

OS400_System_Values_Acct.QACGLVL The accounting level of the system.

Valid Values

*NONE—Indicates that no accounting information is written to a journal.

*JOB—Indicates that job resource use is written to a journal.

*PRINT—Indicates that resource use for spooled and nonspooled print files is written to a journal.

OS400_System_Values_Acct.QACTJOB The initial number of active jobs for which auxiliary storage is to be allocated during an initial program load (IPL).





OS400_System_Values_Acct.QADLACTJ Indicates the additional number of active jobs for which auxiliary storage is to be allocated when the initial number of active jobs (the system value *QACTJOB) is reached.



OS400_System_Values_Acct.QADLSPLA Indicates the additional storage to add to the spooling control block



OS400_System_Values_Acct.QADLTOTJ Indicates the additional number of jobs for which auxiliary storage is to be allocated when the initial number of jobs (system value QTOTJOB) is reached.



OS400_System_Values_Acct.QAUDCTL This system value that controls whether auditing is done for objects and users' actions. It also allows you to specify the level to be performed.

Valid Values

*NONE—These changes are not audited.

– object

– user actions



– QAUDLVL

*OBJAUD—Objects selected by the Change Object Auditing Value (CHGOBJAUD) command are audited.

*AUDLVL—*QAUDLVL system value and CHGUSRAUD (AUDLVL) changes are audited.

OS400_System_Values_Acct.QAUDENDACN Indicates the action to be taken if auditing data cannot be written to the security auditing journal.

Valid Values

*NOTIFY— A journal entry was not written to the security auditing journal and a message was sent to the QSYSOPR and QSYSMSG message queues. The action that caused the audit to be attempted continues.

*PWRDWNSYS—If sending the audit data to the security audit journal fails, the system is ended with a system reference code (SRC). The system is then started in a restricted state on the following IPL.

OS400_System_Values_Acct.QAUDLVL The security auditing level. The system values specifies the level of security auditing that should occur on the system.

Valid Values

*NONE—There is no auditing.

*AUTFAIL—These failures are audited.

– all access failures (sign-on)

– incorrect password or user IDs entered from a device

*CREATE—These objects are audited. (Objects created in the QTEMP library are not audited.)

– new objects

– objects created to replace existing objects



*DELETE—All delete operations of external objects on system. (Objects deleted from QTEMP are not audited.)

*JOBDTA—These actions are audited.

– job start and job stop data

– hold, release, change, disconnect, end, end abnormally, PSR (program start request) attached to prestart job entries, change to another user profile

*OBJMGT—These actions are audited.

– moves of objects

– renames of objects

*OFCSRV—These Office Vision for OS/400 tasks are audited.

– changing the system distribution directory

– opening a mail log for a different user

*PGMADP—Adopting authority from a program owner is audited.

*PGMFAIL—Integrity violations are audited (blocked instruction, validation value failure, domain violation).

*PRTDTA—These printing functions are audited.

– printing a spooled file.

– printing with parameter SPOOL(*NO).

*SAVRST—These save and restore functions are audited. Restores for

– objects

– programs that adopt the user profile for the owner

– job descriptions that contain user’s names

– objects with changed ownership and authority

– authority for user profiles

*SECURITY—These security functions are audited. Changes to

– object authority

– profiles



– object ownership

– programs that will now adopt the profile for the owner

– system values

– network attributes

– subsystem routing

– QSECOFR passwords reset to the value shipped by DST

– DST security officer password is requested to be defaulted

*SERVICE—These commands for system service tools are audited.

– Dump Object (DMPOBJ)

– Dump System Object (DMPSYSOBJ)

– Dump Document Library Object (DMPDLO)

– Start Copy Screen (STRCPYSCN)

– Start Communications Trace (STRCMNTRC)

– End Communications Trace (ENDCMNTRC)

– Print Communications Trace (PRTCMNTRC)

– Delete Communications Trace (DLTCMNTRC)

– Print Error Log (PRTERRLOG)

– Print Internal Data (PRTINTDTA)

– Start Service Job (STRSRVJOB)

– Start System Service Tools (STRSST)

– Trace Internal (TRCINT)

*SPLFDTA—These actions for spooled files are audited.

– create

– delete

– display

– copy



– get data

– hold

– release

– change

*SYSMGT—These tasks for system management are audited.

– changes for Operational Assistant* functions

– operations with network files

– changes to the system reply list

– changes to HFS registration

– changes to the DRDA* relational database directory

OS400_System_Values_Acct.QBASACTLVL The base-storage-pool activity level. The value indicates how many system and user jobs can simultaneously compete for storage in the base storage pool.



OS400_System_Values.ORIGINNODEThe host name for the monitored system.


� alphanumeric




OS400_System_Values.QAUTOCFG Indicates whether or not the system will automatically configure devices that are added to the system.

Valid Values

*YES—Devices are automatically configured.

*NO—Devices are not automatically configured.

OS400_System_Values.QAUTOVRT The system value for the number of virtual devices to be automatically configured.



OS400_System_Values.QBASPOOL The minimum size of the base storage pool specified in kilobytes. The base pool contains all the main storage not allocated by other pools.


� in the range 32-2147483647

OS400_System_Values.QDSCJOBITV Indicates the length of time, in minutes, an interactive job can be disconnected before it is ended.

Valid Values

A number in the range 5–1440—The number of minutes that can be specified for the disconnect interval.

*NONE—There is no disconnect interval.



OS400_System_Values.QMODEL The model number for the system.



OS400_System_Values.QPWEXPITV Allows you to specify the minimum number of days a problem is kept in the problem log.



OS400_System_Values.QPWDEXPITV System value for the password expiration interval. The value controls the number of days that passwords are valid by specifying the frequency that they may or should be changed.)

Valid Values

*NOMAX—No maximum number of days is set for the password.

A number in the range 1-366—Maximum number of days the password can be used.

OS400_System_Values.QPWRRSTIPL Specifies whether the system should automatically perform an IPL when utility power is restored after a power failure.

Valid Values

*YES—If the power fails, there is no auto-IPL after the power is restored.

*NO—If the power fails, there is not an auto-IPL after the power is restored.



OS400_System_Values.QRCLSPLSTG The system value for the reclaim spool storage. It allows for the automatic removal of empty spool database members.

Valid Values

*NOMAX—The maximum retention interval is used.

*NONE—There is no retention interval.

A number in the range 1 – 366—Number of days empty spool database members are kept for new spooled file use.

OS400_System_Values.QRMTSIGN Specifies how the system handles remote sign-on requests. The user can specify a program and library to decide which remote sessions are allowed and which user profiles can automatically sign on from which locations. The first 10 characters contain the program name, and the last 10 characters contain the library name.

Valid Values

*FRCSIGNON—Normal sign-on processing is required for all remote sign-on processing.

*SAMEPRF—For remote sign-on attempts, sign-on may be bypassed for remote sign-on attempts.

*VERIFY—For users with access to the system, the user is allowed to bypass the sign-on after access is verified.

*REJECT—No remote sign-ons are allowed.

OS400_System_Values.QSECURITY Indicates the level of system security.

Valid Values

10—No password is required to access all system resources.

20—A password is required at sign-on and user has access to all system resources.



30—A password is required at sign-on and user is required to have authority to access objects and system resources.

40— A password is required at sign-on and user is required to have authority to access objects and system resources. Programs that use unsupported interfaces to access objects fail.

50—A password is required at sign-on and user is required to have authority to access objects and system resources. Security and integrity is enforced for the QTEMP library and user domain objects. Security and integrity of the QTEMP library and user domain (*USR_xxx) objects are enforced. Use system value QALWUSRDMN to change the libraries that allow *USR_xxx objects. Programs fail if they try to pass unsupported parameter values to supported interfaces, or if they try to access objects through unsupported interfaces.

Note: Note: If this system value has been changed since the last IPL, this is not the security level the system is currently using. This value will be in effect after the next IPL.

OS400_System_Values.QSFWERRLOG Specifies whether or not software errors should be logged by the system.

Valid Values

An alphanumeric string with a maximum of 10 characters or one of these values

� *LOG (Software errors are logged.)

� *NOLOG (No logging occurs.)

OS400_System_Values.QSRLNBR The serial number for the system.





OS400_System_Values.QUPSMSGQ The name of the message queue and library that is to receive uninterrupted power supply messages.


� maximum 20 characters (The first 10 characters indicate the name of the message queue and the last 10 characters indicate the name of the library.)

OS400_System_Values_Device.QDEVNAMING The device naming convention. This value specifies what naming convention is used when the system automatically creates device descriptions.

Valid Values

*NORMAL—Naming conventions should follow current system standards.

*S36— Naming conventions should follow System/36 standards.

*DEVADR—Device names are derived from the device address.

OS400_System_Values_Device.QDEVRCYACN Specifies what action to take when an I/O error occurs on the workstation for an interactive job.

Valid Values

*MSG—Signals the I/O error message to the user's application program.

*DSCENDRQS—Disconnects the job. When signing-on again, a cancel request function is performed to return control of the job back to the last request level.

*DSCMSG—Disconnects the job. When signing-on again, an error message is sent to the user's application.

*ENDJOB—Ends the job. A job log is produced for the job.

*ENDJOBNOLIST—Ends the job. A job log is not produced for the job.



OS400_System_Values_IPL.QABNORMSW Indicates the status of the previous end of a system.

Valid Values

*YES—Previous end of system was abnormal.

*NO—Previous end of system was normal.

OS400_System_Values_IPL.QIPLDATTIM The system value for the date and time that specifies when an automatic IPL of the system should occur.

Valid Values

Numeric date and time (*NONE indicates that an automatic IPL is scheduled.)

OS400_System_Values_IPL.QIPLSTS The IPL status indicator. This value indicates what type of IPL occurred last.

Valid Values

*OPR—Operator panel IPL

*AUTO—Automatic IPL after power restored

*RESTR—Restart IPL

*TOD— Time-of-day IPL

*RMT—Remote IPL

OS400_System_Values_IPL.QIPLTYPE Indicates the type of IPL to perform. This value specifies the type of IPL performed when the system is powered on manually with the key in the normal position.

Valid Values

*UNATTEND—The IPL is unattended.

*DST—The IPL is attended with dedicated service tools.



*DBG—The IPL is attended with console in debug mode.

OS400_System_Values_IPL.QPWRRSTIPL Specifies whether the system should automatically perform an IPL when utility power is restored after a power failure.

Valid Values

*YES—If the power fails, there is an auto-IPL after the power is restored.

*NO—If the power fails, there is not an auto-IPL after the power is restored.

OS400_System_Values_IPL.QRMTIPL The remote power on and IPL indicator.

Valid Values

*YES—A telephone line can be used for a remote power on.

*NO—A telephone line cannot be used for a remote power on.

OS400_System_Values_Perf.QHSTLOGSIZ The maximum number of records for each version of the history log.



OS400_System_Values_Perf.QINACTIV Specifies the inactive job time-out interval in minutes. It specifies when the system takes action on inactive interactive jobs.

Valid Values

*NONE—The system does not check for inactive interactive jobs.

A number in the range 5–300—The value indicates the number of minutes that job can be inactive before the action is taken.



OS400_System_Values_Perf.QINACTMSGQ The system value for the inactive message queue.

Valid Values

Specify one of these values

� an alphanumeric string with a maximum of 20 characters or one of these values (The list can contain up to 2 10-character values where the first is the message queue name and the second is the library name.)

� *DSCJOB (The interactive job and any jobs associated with are disconnected.)

� *ENDJOB (The interactive job and any jobs associated with it are ended.)

Valid Values

DSCJOB—The interactive job is disconnected, as is any secondary or group job associated with it.

ENDJOB—The interactive job is ended, along with any secondary job and any group job associated with it.

OS400_System_Values_Perf.QMAXSGNACN Specifies the action taken when the maximum number of consecutive incorrect sign-on attempts is reached.

Valid Values

*DEV—If limit is reached, varies off device.

*PRF—If limit is reached, disables user profile.

*DEVPRF—If limit is reached, varies off device and disables user profile.

OS400_System_Values_Perf.QMAXSIGN Indicates the maximum number of incorrect sign-on attempts allowed.

Valid Values

*NOMAX—There is no maximum number of sign-on attempts.



A number in the range 1–25—Number that indicates the maximum number of sign-on attempts allowed.

OS400_System_Values_Perf.QMCHPOOL The size of the machine storage pool (in kilobytes). The machine storage pool contains shared machine programs and licensed programs.


� in the range 256-2147483647

OS400_System_Values_Perf.QMAXACTLVL The maximum activity level of the system. This is the number of jobs that can compete at the same time for main storage and processor resources.

Valid Values

*NOMAX—There is no maximum level for the system.

A number in the range 0-32767—Number that indicates the maximum activity level for the system.

OS400_System_Values_Perf.QPRFADJ Indicates whether the system should adjust values during IPL and adjust values dynamically for system pool sizes and activity levels.

Valid Values

*NONE—No performance adjustment.

*IPL—Performance adjustment at IPL.

*DYNAMIC—Performance adjustment at IPL and dynamically.

*IPLDYN—Dynamic performance adjustment.



OS400_System_Values_Perf.QSRVDMP Specifies whether or not service dumps are created for unmonitored escape messages. You can also specify to create service dumps for system jobs and user jobs only.

Valid Values

*DMPALLJOB—Service dumps for unmonitored escape messages are created for all jobs.

*DMPSYSJOB—Service dumps for unmonitored escape messages are created only for system jobs, not user jobs.

*DMPUSRJOB—Service dumps for unmonitored escape messages are created only for user jobs and not system jobs. System jobs include the system arbiter, subsystem monitors, LU services process, spool readers and writers, and the start–control–program–function (SCPF) job.

*NONE—Service dumps are not done.

OS400_System_Values_Perf.QSTRPRTWTR Specifies whether printer writers are started at IPL.

Valid Values

*YES—Start printer writers.

*NO—Do not start printer writers.

OS400_System_Values_Perf.QSTRUPPGM Indicates the name of the startup program called from san autostart job when the controlling subsystem is started.

Valid Values

*NONE or a value with these characteristics

� alphanumeric

� maximum 20 characters (The first 10 characters contain the program name, and the last 10 characters contain the library name.)



OS400_System_Values_Perf.QTOTJOB Indicates the initial number of jobs for which auxiliary storage is allocated during IPL.



OS400_System_Values_Perf.QTSEPOOL The time-slice end pool. This value specifies whether interactive jobs should be moved to another main storage pool when they reach time-slice end.

Valid Values

*NONE—When time-sloe end is reached, jobs are not moved tot he base storage pool.

*BASE—When time-slice end is reached, jobs are moved to the base pool.

OS400_System_Values_Prob.QPRBFTR Indicates the name of the filter object that the service activity manager uses when processing problems.

Valid Values

*NONE or a value with these characteristics

� alphanumeric

� maximum 20 characters (The list can consist of up to two 10-character values where the first value is the problem filter name, and the second value is the library name.)

OS400_System_Values_Prob.QPRBHLDITV Indicates the minimum number of days a problem is kept in the problem log.





OS400_System_Values_User.QCCSID The system value for coded character set identifiers.



OS400_System_Values_User.QCHRID The default character set and code page. The system value is retrieved as a single-character value.


� maximum 20 characters (The first 10 characters contain the character-set identifier right-justified, and the last 10 characters contain the code-page identifier right-justified.)

OS400_System_Values_User.QCMNRCYLMT The system value for communications recovery limits.


� maximum 20 characters (The first 10 characters contain the count limit right-justified, and the last 10 characters contain the time interval.)

OS400_System_Values_User.QCNTRYID The system value for the country identifier. This value specifies the country identifier to be used as the default on the system.





OS400_System_Values_User.QCTLSBSD The description for the controlling subsystem. The controlling subsystem is the first subsystem to start after an IPL.


� maximum 20 characters (The list can consist of up to two 10-character values, where the first value is the subsystem description name, and the second value is the library name.)

OS400_System_Values_User.QDATE The system date.

Valid Values

A value in the format CYYMMDD (C is the century (0 for the twentieth century, 1 for the twenty-first century), YY is the year, MM is the month, DD is the day.)

OS400_System_Values_User.QDATEFMT The system date format.

Valid Values

A date in the format YMD, MDY, DMY, or JUL (Julian format), where Y is the year, M is the month, and D is the day

OS400_System_Values_User.QDAY The day of the month.


� in the range 1-31 (If the value for QDATFMT is Julian, the range 1-366.)



OS400_System_Values_User.QHOUR The system value for the hour of the day based on a 24 hour clock.



OS400_System_Values_User.QMINUTE The system value for the minute of the hour.



OS400_System_Values_User.QMONTH The system value for the month of the year. This field is blank if the Julian (JUL) date format is specified in system value QDATFMT.


� in the range 1-12 (If the value for QDATFMT is Julian, the field is blank.)

OS400_System_Values_User.QSECOND The system value for seconds.



OS400_System_Values_User.QSYSLIBL The system part of the library list. The list can contain as many as 15 library names.





OS400_System_Values_User.QTIME The system value for the time of day, represented in hours (*QHOUR), minutes (*QMINUTE), and seconds (*QSECOND).

Valid Values � consists of QHOUR, QMINUTE, and QSECOND

OS400_System_Values_User.QUPSDLYTIM Amount of time that elapses before the system automatically powers down following a power failure. When a change in power activates the uninterruptible power supply, messages are sent to the UPS message queue (the system value QUPMSGQ). This system value is only meaningful if your system has a battery power unit or an uninterrupted power supply attached.

A change to this system value takes effect the next time a power failure occurs. The shipped value is *CAL.

Valid Values

*BASIC—Powers only the PRC, IOP cards, and Load Source direct-access storage device. The appropriate wait time, in seconds, is calculated. (This should be used only if you have the battery power unit or an uninterrupted power supply without every rack being connected.)

Note: All other values indicate an uninterrupted power supply on all racks.

*CALC—The appropriate wait time is calculated.

*NOMAX—The system does not start any action on its own.

0—The system automatically powers down when system utility power fails.

1– 99999—The delay time specified in seconds before the system powers down.

The value is in a 2 item list that consists of



� first, the value specified using the Change System Value (CHGSYSVAL) command

� second, the delay time (The delay time is either specified by the user or calculated using *CALC or *BASIC.).

OS400_System_Values_User.QUSRLIBL The default for the user part of the library list. The list can contain as many as 25 names.



OS400_System_Values_User.QUTCOFFSET The system value that indicates the difference in hours and minutes between Universal Time Coordinated (UTC), also known as Greenwhich mean time, and the current system time (local).



OS400_System_Values_User.QYEAR The system value that specifies the last 2 digits for the year.




End Notes for Attributes


Table 6. Valid Numeric Values The table contains the valid numeric values for these attributes.

� OS400_Controller.Status

� OS400_Device.Status

� OS400_Line.Status

Numeric Status Meaning

0 VARIED OFF10 VARY OFF PENDING20 VARY ON PENDING30 VARIED ON40 CONNECT PENDING50 SIGNON DISPLAY60 ACTIVE63 ACTIVE READER66 ACTIVE WRITER70 HELD75 POWERED OFF80 RCYPND90 RCYCNL95 SYSTEM REQUEST100 FAILED103 FAILED READER106 FAILED WRITER110 DIAGNOSTIC MODE111 DAMAGED112 LOCKED113 UNKNOWN



Note: You may use any of the following logical operators:

� *GT—Greater than� *GE—Greater than or equal to� *LT—Less than� *LE—Less than or equal to� *EQ—Equal to� *NE—Not equal to

Table 7. Codes Returned When Jobs are Running

Code Description

blank The system is not performing a logged function.

C A command is running interactively - or it is in a batch stream - or it was requested from a system menu. Commands in CL programs or REXX procedures are not logged.

D The job is processing a delay job command. The function name contains the number of seconds the job is delayed (up to 999999 seconds) - or the time the job is to resume processing (HH:MM:SS) - depending on how you specified the command.

G The Transfer Group Job (TFRGRPJOB) command suspended the job. The function name field contains the group job name for that field.

I The job is rebuilding an index (access path). The function name field contains the name of the logical file whose index is rebuilt.

L The system logs history information in a database file. The function name field contains the name of the file. (QHST is the only log currently supported.

M The job is a multiple requester terminal (MRT) job if the job type is BATCH and the subtype is MRT - or it is an interactive job attached to an MRT job if the job type is interactive.

N The job is currently at a system menu. The function name field contains the name of the menu.

O The job is a subsystem monitor that is performing input/output (I/O) operations to a work station. The function name field contains the name of the work station device to which the subsystem is performing an input/output operation.



P The job is running a program. The function name field contains the name of the program.

R The job is running a procedure. The function name field contains the name of the procedure.

* This performs a special function. For this value, the function name field contains one of the following:

ADLACTJOB— Auxiliary storage is being allocated for the number of active jobs specified in the QADLACTJ system value. This may indicate that the system value for the initial number of active jobs is too low.

ADLTOTJOB— Auxiliary storage is being allocated for the number of jobs specified in the QADLTOTJ system value.

CMDENT— The Command Entry display is being used.

DIRSHD— Directory shadowing.

DLTSPLF— The system is deleting a spooled file.

DUMP— A dump is in process.

JOBLOG— The system is producing a job log.

PASSTHRU— The job is a pass-through job.

RCLSPLSTG— Empty spooled database members are being deleted.

SPLCLNUP— Spool cleanup is in process.

Table 8. Definition of Pools

Value Meaning

*USERPOOL user-defined pool

*BASE system base pool

*INTERACT a shared pool for interactive jobs

*NOSTG a pool with no storage size and activity assigned to it

*SHRPOOL1 shared pool 1

Table 7. Codes Returned When Jobs are Running

Code Description












*SPOOL shared spool for printing

Table 8. Definition of Pools

Value Meaning

OMEGAMON XE for OS/400 Product-provided Solutions 217

OMEGAMON XE for OS/400Product-provided Solutions

IntroductionThis chapter provides descriptions of OMEGAMON XE for OS/400 product-provided solutions.

Chapter ContentsUnderstanding Product-provided Solutions. . . . . . . . . . . . . . . . . . . . . . . 218

3

Understanding Product-provided Solutions


Understanding Product-provided Solutions

OverviewWhen you install the OMEGAMON XE for OS/400 product, you will automatically install a set of situations that are already defined and ready to use. When you configure the OMEGAMON XE for OS/400 product, this set of situations is ready to start monitoring on your OS/400 system.

These predefined situations can be used

� as they are shipped to begin monitoring right away

� as models that you can modify and then use

� imbeds that you can insert in other situations

� a reference as you learn how to create your own situations

Whether you decide to use the situations depends on your environment and your particular needs. For instructions on using the situations, see the online help in CandleNet Portal.

Auto-start situationsSeveral of the situations are auto-started, which means they are enabled as soon as you start the product.

If you do not want the auto-start situations to start automatically, you must cancel them. For more information about how to cancel an auto-start situation, see the Situations topic in the table of contents in the online help.

The auto-start situations are

� OS400_Perm_Address_Warning

� OS400_Temp_Address_Warning

� OS400_System_ASP_Warning


OMEGAMON XE for OS/400 Product-provided Solutions


OverviewThis section lists the product-provided solutions and provides a description of the conditions they monitor.

You can begin using the benefits and features of OMEGAMON XE for OS/400 almost immediately by using the predefined situations.

You can use the situations shipped with the product in a variety of ways. The situations shipped with OMEGAMON XE for OS/400 were developed as a result of customer feedback based on typical OS/400 customer environments.

Situation listing The following information lists the OMEGAMON XE for OS/400 situations provided with CandleNet Portal.

OS400_Network_Attribute_Changed

Raises an alert when any changes to network attributes are logged in the audit journal. This is useful for alerting you to changes that may affect or compromise the security of your system and/or network. Journaling must be active on your OS/400 system to run this situation. You must also specify a value for Entry Type.

OS400_System_Value_Changed

Raises an alert when any changes to system values are logged in the audit journal. This is useful for monitoring changes that affect how your system and operating environment are set. Journaling must be active on your OS/400 system to run this situation.

OS400_Snads_Job_Missing

This situation monitors the system or systems and raises an alert when the QROUTER job is not detected.

OS400_Snads_Ended



This situation monitors QSYSOPR for message CPF0927, which indicates the QSNADS subsystem has ended. The QSNADS subsystem must be active for SNA distributions to work.

OS400_Snads_Router_Failed

This situation monitors for message CPC8803 (Snads Router Ended Abnormally) and raises an alert when this message is detected. This is useful for indicating potential interruptions and limitations in SNA distributions.

OS400_Snads_Critical

This situation raises an alert when either of these situations raises an alert.

� OS400_Snads_Ended

� OS400_Snads_Router_Failed

OS400_Disk_Util_Critical

This situation tracks the percentage of time the actuator for the disk is busy during the monitor interval and raises a critical warning when usage is greater than or equal to 60 percent. Extremely high disk utilization can negatively impact system performance and cause unpredictable interruptions to system operations.

The OS400_Disk_Util_Critical.Arm_Number attribute is specified as a display item so that you can display all the events for the situation , even if the situation has triggered an event and is already displayed in the Events window.

OS400_Disk_Util_Warning

This situation monitors the percentage of time the actuator for the disk is busy during the monitor interval and raises a warning alert when usage is greater than or equal to 40 percent. High disk utilization is a possible cause of poor system performance.

The OS400_Disk_Util_Warning.Arm_Number attribute is specified as a display item so that you can display all the events for the situation, even if the situation has triggered an event and is already displayed in the Events window.

OS400_Pool_Transitions_High



This situation monitors for any pool active-to-ineligible transitions. These transitions occur when a transaction does not complete during a single time slice. This situation may help to isolate performance problems. It may be necessary to adjust the system pool to improve performance and prevent thrashing. For more information, see the OS/400 manual, Work Management Guide.

OS400_Job_Avg_Response_Time_High

This situation watches interactive jobs for periods of poor response time. Using this situation, you can determine the causes and redirect jobs to different queues or submit them for processing at different time intervals.

OS400_Comm_IOP_Util_Warning

This situation monitors the total IOP processor time that was used by communications tasks during the monitor interval. A warning alert is sent when the level is equal to or greater than 25 percent. This situation can signal you to potential slow-downs when there is excess traffic on communications lines.

OS400_CPU_Util_Warning

This situation monitors for extended periods of high CPU utilization. A warning alert is sent when the usage is equal to or greater than 95 percent. By recognizing when the CPU reaches this threshold level, you can detect and further prevent serious slow downs in your operations. Extended or repeated occurrences may indicate the need to submit jobs during off-peak hours or obtain additional CPU resources.

OS400_Disk_IOP_Util_Warning

This situation monitors for the percentage of IOP processor time that was used by disk tasks during the monitor interval. A warning alert occurs when the disk IOP processor time is equal to or greater than 25 percent.

OS400_Pool_Faulting_Warning

This situation monitors for high pool faulting rates and issues a warning alert when the rate is equal to or greater than 30 percent. High pool faulting rates may indicate a need for performance tuning on your system.



OS400_Interactive_Jobs_CPU_High

Watches for interactive jobs that are using 20 percent or more of system CPU time. Using this amount or more of processor time limits the amount available for other jobs. By identifying jobs requiring large CPU time usage, you could suggest that these jobs be run during off-peak hours and/or in batch mode.

OS400_Disk_Capacity

This situation monitors for potential disk capacity problems and raises a critical alert when disk capacity is equal to or greater than 90 percent. Running a system with disk space at near-capacity limits the amount available for other storage. This situation can help you avoid lost or corrupted data due to lack of space.

The OS400_Disk_Capacity.Arm_Number attribute is specified as a display item so that you can display all the events for the situation, even if the situation has triggered an event and is already displayed in the Events window.

OS400_Perm_Address_Warning

This situation monitors for the percentage (in thousandths) of the maximum possible addresses for permanent objects that have been used. A warning alert will be issued when the number used is equal to or greater than 95 percent.

OS400_Temp_Address_Warning

This situation monitors for the percentage (in thousandths) of the maximum possible addresses for temporary objects that have been used. A warning alert will be sent when the number used is equal to or greater than 95 percent.

OS400_System_ASP_Warning

This situation monitors the auxiliary storage pool’s use and issues a warning alert when usage is greater than or equal to 95 percent.

OS400_Address_Critical

This situation raises an alert when any of these situations raises an alert.

� OS400_Temp_address_Warning

� OS400_ASP_Warning



� OS400_Perm_Address_Warning

OS400_Communications_Line_Failed

This situation monitors for messages that indicate the failure of a communications line. The situation raises an alert when either of these messages are reported to QSYSOPR.

� CPA58CC (line failure due to a hardware problem)

� CPA58CD (line failure due to a communications subsystem problem)

This is particularly useful for early detection and correction of line problems or early intermittent hardware failures.

OS400_OMA_Message_Log

This situation monitors for messages arriving in QAUTOMON/KMSOMLOG, which is the OMEGAMON XE for OS/400 message log. This situation allows you to view messages arriving that are related to OMEGAMON XE for OS/400 operations. You can modify the situation to monitor for specific messages that require your attention.



Using OMEGAMON XE for OS/400 Predefined Workspaces 225

Using OMEGAMON XEfor OS/400 Predefined

Workspaces

IntroductionThis chapter provides information about the predefined workspaces provided with OMEGAMON XE for OS/400.

Chapter ContentsOMEGAMON XE for OS/400 Predefined Workspaces . . . . . . . . . . . . . . 226Using CandleNet Portal to Work with Predefined Workspaces. . . . . . . . . 227Types of Information Available for OMEGAMON XE for OS/400 . . . . . . 234If You Are a CMW User Who is Learning to Use CandleNet Portal . . . . . 238

4

OMEGAMON XE for OS/400 Predefined Workspaces


OMEGAMON XE for OS/400 Predefined Workspaces

Overview When you install the OMEGAMON XE for OS/400 product, you will receive a collection of predefined workspaces.The predefined workspaces display data collected on an interval basis.

Using this feature of OMEGAMON XE for OS/400, you can

� monitor system and resource usage and availability

� determine what and when you want to monitor using situations

� locate problems that may affect system availability

� prevent problems that result from overuse of certain system resources

� view messages that provide useful information and/or may require a response

� integrate with other CandleNet Command Center products for an enterprise-wide view of multiple systems from a single workstation

A direct relationship exists between the predefined workspaces and the attribute groups.


Using CandleNet Portal to Work with Predefined Workspaces


OverviewThis unit provides a high-level overview of working with workspaces while using CandleNet Portal. For the most current in-depth information, refer to the online Help provided with CandleNet Portal.

The workspace is the working area in which CandleNet Portal presents information. As you select items, the workspace presents views pertinent to your selection. Each workspace has at least one view.

Every workspace has a set of properties associated with it. You can customize the workspace by working in the Properties editor to change the style and content of each view.

Be aware that the changes you make to the workspace are lost when you switch to another workspace unless you Save them first.

Another way to customize the workspace is to change the type of view or to add views to the workspace.



Formats for CandleNet Portal informationCCC information can be presented to you in any of the views below:

� Table view

� Pie chart view

� Bar chart view

� Plot chart view

� Needle gauge view

� Thermometer gauge view

� Notepad view

� Event console view, that shows the status of the situations associated with the system.

� Take Action view, that is used to send a command to the system.

� Terminal view, that enables you to start a 3270 or 5250 work session.

� Browser view, that permits you to open a browser to see HTML pages and Web sites.

Opening a workspace

Opening the default workspace

Most items in the Navigator has a default workspace associated with the item. Some items have multiple workspaces you can open, although only one workspace can be open in the CandleNet Portal application window at one time. To open the default workspace, in the Navigator, click the item name or its icon.

Opening multiple workspaces

CandleNet Portal enables you to have multiple workspaces for an item. If the Navigator item has more than one workspace associated with it, use the View menu > Workspace command to see and select from a list of alternate workspaces.



Refreshing or reloading a workspaceOnce a workspace is open, it is not refreshed automatically. Rather, CandleNet Portal refreshes the table and chart views in the workspace only when you manually request they be refreshed or when the workspace is reloaded. You can, however, choose to automate the refresh at specified intervals. When choosing automatic refresh for a workspace, you should consider the impact of the refresh on system resources.

To define automatic refresh for a workspace:

1. Open the View menu, then point to Refresh Every.

2. Click 5, 10, 15, 30, or 60 seconds, or On Demand.To refresh a workspace manually with the latest information, click Refresh.

To manually reload the saved workspace and refresh the monitoring data, click Reload. Note that, if you made any changes to the workspace properties without saving them, the changes will be lost when a reload occurs.

Suspending or stopping a workspaceCandleNet Portal receives monitoring data from the agents at timed intervals and, if you have defined automatic refresh for the workspace, refreshes the table and chart views in the workspace. The refreshes use system resources. You can control when the views are refreshed by suspending the refresh. You can also stop loading the workspace if it is not what you want or you plan to change it.

To stop refreshing, click Suspend. You can then manually refresh the workspace, or you can click Resume to resume automatic refresh.

To stop loading a workspace, click theCandleNet Portal Stop icon. Note that clicking your browser’s Stop icon will not stop the loading of a CandleNet Portal workspace.



Editing a workspaceYour CandleNet Portal product comes with a set of predefined workspaces for every item in the Navigator's physical map. You can edit any of these workspaces to suit your environment.

The changes you can make to a workspace include the following:

� Split a view horizontally or vertically into two separate views.

� Change the dimensions of the views by dragging the borders between them.

� Change a view to a different type, such as from a pie chart to a thermometer gauge.

� Edit the properties of any view to change the data displayed and how the view is styled.

� Build a link to another workspace so that you can link to the other workspace from this one at any time.

� Remove a view from the workspace. The adjacent view enlarges to fill the gap.

When you are finished editing a workspace you must save your changes either as the current workspace or as a new workspace. If you do not save your changes, they will be lost when you open another workspace or end your work session.

Any changes you make to a workspace are available to all other users on the network having the same ID.



Saving the workspaceWhatever changes you make to the workspace properties, such as adding or editing a view, are only temporary. They will be lost when you open another workspace or exit CandleNet Portal, unless you save the workspace. You can also save multiple workspaces for the same Navigator item.

Click Save to replace the original workspace with the current workspace. If you do not want to replace the original workspace, save the current workspace under a new name.

If this is a new workspace:

1. Open the File menu and select Save Workspace As.

2. Type a name for the new workspace in the text box and click OK.Result: The workspace is saved with the name you specify, and is available to all of your managed systems of the same managed system type.

Note: Note: The saved workspace is associated with your CandleNet Portal user ID. Users with a different ID will not see your changes. If you have edited the workspace but don't want to save your workspace, you can reload the saved workspace as described on page 229.

Linking workspacesSome of your product’s predefined workspaces may be linked to other related workspaces. Linking workspaces is a quick method for going from one workspace to another related workspace quickly.

� You can link from one workspace to another from the Navigator. Simply right-click on a workspace and then select the workspace to link to from the pop-up menu that is presented.

� While using a workspace’s table view, you can right-click within a cell in the table to display existing links to other related workspaces.

You can define your own links using the Link Wizard by following the directions in CandleNet Portal’s online Help. Once a link is defined, you can link to the subject workspace from another workspace, edit the link, or remove a link definition. Note that the link will not be saved until the subject workspace is saved.



Defining workspace propertiesEvery workspace has properties for its views. You can right-click in an open view or any item in the Navigator to select and open the Properties editor.

The Properties tree has a Views folder with folders for each type of view in the workspace.

To edit the properties of a view, click its icon in the Properties tree.

The properties open in the right frame with some or all of the following tabs:

Table 9. Tabs for Changing Properties in CandleNet Portal

Configuration Specifies the script to run or the connection to make whenever you open the terminal view.

Filters Refines the view by filtering out unwanted data from the chart or table.

Query Specifies what data should go in the chart or table.

Style Changes the behavior and appearance of the view.

Thresholds Establishes threshold values and color indicators for a table view.



Opening an event workspaceWhen the conditions of a situation have been met, an event indicator appears in the Navigator. You can investigate the event by opening its workspace.

1. In the Navigator move the mouse pointer over the alert indicator to open a flyover listing of the event (or events if the item has more than one true situation).

2. In the flyover listing click a situation name to open its workspace.Result: The Navigator moves to the event location and shows the situation name, and its event workspace opens.

The event workspace shows two table views, one with the values of the attributes when the situation fired, and the other with their current values. It can also display a text view with any expert advice written by the situation's author, and the Take Action view so you can send a command to the application started on that system.

Types of Information Available for OMEGAMON XE for OS/400



Types of information in reports and predefined workspacesYou can display the following categories of information in workspaces and reports.

Communications The reports and workspaces in this category show you specific information about your communications connections. Each report or workspace shows you data such as IOP name, IOP bus address, IOP bus number, line description, utilization percentages, and error information.

OS/400 Communications contains several different reports or workspaces. For some of the communications available with OS/400, you can display data for

� X.25

� Ethernet

� Token-Ring

� Asynchronous (Async)

� Bisynchrous (Bisync)

� Synchronous Data Link Control (SDLC)

Configuration The reports and workspaces in this category show configuration information for your system communications. These reports and workspaces contain information for

� line description

� controller description

� device description

� network attributes



Use the information to pinpoint inactive communication sessions and quickly summarizing system network configuration.

Database and objects The reports and workspaces in this category

� provide access to information about libraries, physical files, and member details

� show object details, which include save, change, create, restore and usage information. (In addition, you can also view information about your operating system, license programs and PTFs. )

Disk and I/OThe reports and workspaces in this category

� show descriptive and usage information about your I/O processor, such as type and percent utilization.

� are useful for seeing the percentage of utilization of storage devices. The reports and workspaces contain information for

– disk unit

– system status

Jobs and queues The reports and workspaces in this category display information about your OS/400 jobs and queues.The reports and workspace contain information for

– job queue

– job resource information

– subsystem information

The data returned includes the name, status and usage information for job queues, CPU utilization, priority and other detailed information about OS/400 jobs and job queues.



Messages and spool You can use the reports and workspaces in this category to display information about

� the messages logged during the interval you specify

� spools spool files, including creation and usage data (Other data provided includes name, number, status, priority, job usage and output queue information.)

You can display the messages logged in one of these locations.

� System Operator’s Message Queue (QSYSOPR)

� product log for OMEGAMON XE for OS/400

� product log for the CMS for OS/400 (If a CMS is not installed on the managed system, the report for the managed system does not contain data.)

The report has these advantages. You can use the report to:

� reduce the number of times you need to access the message log to see what messages have been received

� give you a quick awareness of any recent and/or urgent conditions

System The reports and workspaces in this category

� show you a summary of CPU, auxiliary storage pool, and permanent and temporary address usage

� provide detailed information in a variety of system value areas such as:

– accounting

– IPL

– device

– performance

– problem

– user



This information can help understand and manipulate how the operating system functions. For example, one value that will be included provides the format in which the system date and time are stored.

If You Are a CMW User Who is Learning to Use CandleNet Portal



Introduction This unit provides information about

� the relationship of the report icons in the CMW to the items in the Navigator in CandleNet Portal

� the relationship of the reports provided in the CMW to the predefined workspaces provided in CandleNet Portal

For example, if you are CMW customer who is now using CandleNet Portal, you will find this useful for locating the type of information you are familiar with in the CMW.

Background about the relationships Candle Management Workstation and CandleNet Portal collect and provide the same types of information.

� In the CMW, the information is displayed in a report that contains a single table.

� In CandleNet Portal, the information is displayed in predefined workspaces that can contain more than one table, and in some cases, an additional view (such as another table view or bar chart).



Relationship of Icons in the CMW to the Items in the Navigator in CandleNet Portal

The following table shows the relationship of the icons in the CMW main window to the items displayed in the CandleNet Portal Navigator.

Table 10. Relationship of the Icons to Items in the Navigator

Icon in the CMW Main Window Equivalent Item in the CandleNet Portal Navigator

OS/400 Communications Communications

OS/400 Configuration Configuration

OS/400 Database Database and Objects

OS/400 Disk Disk and I/O

OS/400 I/O Processor Disk and I/O

OS/400 Jobs and Queues Jobs and Queues

OS/400 Objects Database and Objects

OS/400 Operator Messages Messages and Spool

OS/400 Output Spool Messages and Spool

OS/400 Storage Pools System

OS/400 System Status System



Tasks in the CMW and Equivalent Methods in CandleNet PortalThe following table shows some common tasks for displaying data. The table also shows the method you use in the CMW to accomplish the task and the equivalent method to use in CandleNet Portal.

Table 11. Comparison of Tasks in the CMW and CandleNet Portal

Task Method to Use in the CMW Method to Use in CandleNet Portal

Display a specific category of information for your system (such as information about communications)

Select the icon for the report group in the Reports - Icons window. Then, you select the OS/400 system for which you want the information.

For the OS/400 system, select the item for the category in the Navigator

Display the different types of information in the category (such as display information about X.25 communications)

In the report, right-click on an OS/400 system and select a command on the pop-up menu

There are 2 methods. � Right click on the item in

the Navigator and select Link To. Then select the command on the drop-down menu.

� On the menu bar, select the View and the Workspaces command. Then, select the command on the drop-down menu.

Display more detailed information about a row (such as details about a specific job resource)

In the report, right-click on a row and select a command on the pop-up menu.

In the table view of a workspace, right-click on a row and select Link To. Then, select the name of the command on the drop-down menu.

Tables that you can link from will display the following icon next to the row.



Historical data in the Candle Management Workstation and CandleNet Portal

In CandleNet Portal, there are no predefined workspaces that display historical data. The following table that shows the relationships does not include the names of the historical reports.

You can, on the other hand, use an equivalent feature to store historical data. For information about storing historical data, see the online help for CandleNet Portal.

Relationship of Reports to Predefined Workspaces The following table shows the relationship of the reports available in the CMW to the predefined workspaces available in CandleNet Portal. The table also shows method to use to access the workspace beginning with item to select in the Navigator and then the method to use using the menu bar. The table does not include:

� the names of the historical reports available in the CMW

� the names of the reports displayed when you select the icon for the report group, such as OS/400 Communications (In CandleNet Portal, you select the name of the system in the Navigator instead.)

Table 12. Relationship of Reports to Predefined Workspaces

Report in the CMW Workspace in CandleNet Portal

Access Method Using the Navigator and Menu Bar

Activity System Values Included as a table view in the System Values workspace

Select System > View menu > Workspace command > System Values command.

APPN Topology Included as a table view in the Communications workspace

Select Communications.

Asynchronous Communications

Asynchronous Select Communications > View menu > Workspace command > Asynchronous command.



Binary Synchronous Communications

Binary Synchronous Select Communications > View menu > Workspace command > Binary Synchronous command.

CMS for OS/400 Logs Managed Systems and CMS for OS/400 Logs

Select Messages and Spool > View menu > Workspace command > Managed Systems and CMS for OS/400 Logs command.

Controller Description Included as a table view in the Configuration workspace

Select Configuration.

Database File Database Files Select Database and Objects > right-click on row in table > Link To command > Database and Files command.

Database Library Included as a table view in the Database and Objects workspace

Select Database and Objects.

Database Member File Members Select Database and Objects > right-click on row in table > Link To command > Database and Files command > right-click on row in table > Link To command > File Members command.

Device Description Included as a table view in the Configuration workspace


Device System Values Included as a table view in the System Values workspace






Disk Unit Included as a view in the Disk and I/O workspace

Select Disk and I/O.

Ethernet Ethernet Select Communications > View menu > Workspace command > Ethernet command.

I/O Processor Included as a table view in the Disk and I/O workspace


IPL System Values Included as a table view in the System Values workspace


Job Queue Included as a table view in the Jobs and Queues workspace

Select Jobs and Queues.

Job Resource Information

Included as a table view in the Jobs and Queues workspace


Job Resource Information Detail

Job Detail Select Jobs and Queues > right-click on a row in the Job Resource Information table view > Link To command > Job Resource Details command.

Line Description Included as a table view in the Configuration workspace


Managed Systems for OS/400 Logs

Managed Systems and CMS for OS/400 Logs

Select Messages and Spool > View menu > Workspace command > Managed Systems and CMS for OS/400 Logs command.

Network Attribute Included as a table view in the Configuration workspace






Object Library Included as a table view in the Database and Objects workspace

Select Database and Objects.

Object Library Detail Object Library Details Select Database and Objects > right-click on a row in the Database/Objects table view > Link To command > Object Library Details command.

Operator Messages Included as a table view in the Messages and Spool workspace

Select Messages and Spool.

Output Queue Output Queues Select Messages and Spool > right-click on a row in the Spool File Library table view > Link To command > Output Queues command.

Performance System Values

Included as a table view in the System Values workspace


Problem System Values

Included as a table view in the System Values workspace


Subsystem Information

Subsystem Information Select System > View menu > Workspace command > Subsystem Information command.

System Status System Select System.

SDLC SDLC Select Communications > View menu > Workspace command > SDLC command.

Spool File Detail N/A (An equivalent workspace is not included in CandleNet Portal.)





Spool File Library Included as a table view in the Messages and Spool workspace

Select Messages and Spool.

Storage Pool Included as a table view in the Disk and I/O workspace


Subsystem Information

Included as a table view in the Jobs and Queues workspace


System Values Included as a table view in the System Values workspace


Token Ring Token Ring Select Communications > View menu > Workspace command > Token Ring command.

User System Values Included as a table view in the System Values workspace


X.25 X25 Select Communications > View menu > Workspace command > X25 command.





Other Features and Considerations 247

Other Featuresand Considerations

IntroductionThis chapter introduces several features of OMEGAMON XE for OS/400. In addition, this chapter includes important information about performance considerations with OMEGAMON XE for OS/400.

Chapter ContentsAbout CandleNet Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Exploring Other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249OMEGAMON XE for OS/400 Performance Considerations . . . . . . . . . . 251Performance Overhead When Monitoring for Situations . . . . . . . . . . . . . 254Maintaining OMEGAMON XE for OS/400 Performance . . . . . . . . . . . . . 256Performance Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Monitoring for Files that Are Inactive . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Tuning QAUTOMON Subsystem Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . 264Attribute Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

5

About CandleNet Portal


About CandleNet Portal

Overview CandleNet Portal helps you monitor your enterprise network and its applications, so that they run smoothly and well. For fast identification of problem areas, colored indicators overlay the icons of the affected systems. As you move the mouse pointer over an indicator, a flyover list opens to show what caused the alert.

Build custom workspaces for each information groupCandleNet Portal retrieves monitoring data at regular intervals and sends the results to the workspace in the form of charts and tables. You can start monitoring activity and system status immediately with the predefined workspaces. You can tailor your own workspaces to look at specific conditions, display critical threshold values in red, and filter incoming data so you see only what matters.

Set up conditional alerts with the Situation editorYou can write comparisons with threshold values that CandleNet Portal tests against monitored data. When it finds a matching value (or one within a range), it displays an indicator to alert you. You can have CandleNet Portal also send a command to the system.

Get a broader picture with historical reportingLook over what happened hours, days, or weeks ago to find a pattern. Filter out unwanted data to see specific areas of interest. Get a quick history to see data from previous refreshes; or define a historical chart or table that you can open any time to see historical data for a set period.

Interact with systems from your consoleThe Take Action feature lets you enter a command or stop or start a process at any system in your network where one or more Candle agents are installed.


Exploring Other Features


OverviewAfter learning how to create situations, access workspaces, and use product–provided solutions, you can explore the other features of OMEGAMON XE for OS/400. Understanding these tools or features can help complete you monitoring strategy. These tools include:

� historical data collection

� Take Action

� Non–programmable terminal (NPT) interface to OMEGAMON XE for OS/400

Taking Action Simple automation, or “Take Action”, provided with OMEGAMON XE for OS/400 allows you to associate an action with a situation. For example, you can specify that OS/400 lower the job priority when it detects an interactive job that is using more processing unit resource than what you have determined is reasonable or allowable. You associate this action with the situation by choosing an OS/400 command to run or execute when CPU utilization reaches a specified percentage.

Actions run under the user profile of the person who created, or last changed/modified the situation. Within OMEGAMON XE for OS/400, these actions are controlled by individual user profiles or the QAUTOMON user profile. Which one will be used is determined by how OMEGAMON XE for OS/400 was configured. These values are set in OS/400 from the non–programmable terminal interface using the CFGOMA command or the Configure OMEGAMON XE option from the OMEGAMON XE main menu.

The user profile under which user action should be taken is specified on the Configure OMA (CFGOMA) menu with the Action user Profile field.

Since action is taken based on user profiles, do not sign on to CandleNet Portal with the following system user profiles to create, change, or start an action situation



� QDBSHR� QDOC� QLPAUTO� QLINSTALL� QRJE� QSECOFR� QSPL� QDFTOWN� QTSTRQS� QYSYS

These user profiles are not supported.

Action is taken on OS/400 using a command interface. This interface is specified and accessed using the Action tab available on the Situation(s) dialog displayed when you are creating a situation

Non-programmable terminal interfaceYou must use the OS/400 non-programmable terminal interface to install, configure, start and stop OMEGAMON XE for OS/400. This interface is also used to view the OMEGAMON XE for OS/400 message log.

To access the non-programmable terminal interface, type

GO OMA

on an OS/400 command line. This command takes you to the main menu of OMEGAMON XE which contains options for starting, configuring and stopping the agent and for viewing the OMEGAMON XE for OS/400 message log. Online help is available while you are using this interface.

The documentation provided with your OS/400 system provides more detail on command and menu interfaces and working with message logs.


OMEGAMON XE for OS/400 Performance Considerations


OverviewCertain OMEGAMON XE for OS/400 usage patterns can impact product performance. For example, the number of active situations, specified user actions, and the monitor interval can have an impact on the overall performance of your system and OMEGAMON XE for OS/400.

Your OS/400 system should be tuned with processor, memory, communication and disk I/O balanced. If you are using CandleNet Portal, the personal computer should at least be of the recommended size.

All monitoring will cause some performance overhead.

This section contains information about how you can minimize performance overhead by

� optimizing the monitor intervals

� limiting the amount of data sets gathered

� monitoring only what is needed

� minimizing the starting and stopping of monitoring

� using embedded situations

This section also contains information about minimizing performance overhead when creating situations and specifying Take Action.



Monitor intervalUse the monitor interval carefully. The monitor interval that is too frequent degrades performance. The monitor interval that is too infrequent defeats the purpose of the situation. In most cases, you can specify the monitor interval based on how often a system operator would manually check for the situation.

The monitor interval has significant influence on performance overhead. In general, you should use the longest interval possible for the situation being monitored.

For attributes that use a collection interval, specifying a monitor interval that is a multiple of one of the collection of intervals will cause less performance overhead.

Each situation definition that is started adds to the system performance overhead, since situations must be evaluated at each monitor interval. Using one situation definition with multiple predicates will cause less overhead than defining and starting a separate situation for each attribute or compare value to be checked. For example, if there are several messages for which you are monitoring, they can be combined into one situation definition.

AttributesMultiple-instance attributes are attributes that can gather multiple sets of data. For example, the spool file (OS400_Spool_file) attributes are multiple-instance attributes because they can return one set of data for each output queue on the system.

Some multiple-instance attributes can cause a very large number of sets of data to be gathered. Specifying predicates for additional attributes in the same attribute group may reduce the amount of data that needs to be collected. For example, specifying compare values for the OS400_Object.Library, OS400_Object.Name, and OS400_Object.Type attributes can reduce the overhead for collecting auxiliary storage attribute data. For more information and examples, see“Attribute Grouping” on page 265.



Autostart situationsAvoid starting more situations than necessary. The situations when AUTOSTART is specified as *YES are automatically started when the OS/400 system starts. You can avoid this by using AUTOSTART *NO when you create a new situation.

Performance Overhead When Monitoring for Situations



OverviewMonitoring of the different operational areas will cause different performance overhead as some areas require more resources than others.

Performance impact by attribute groupIn the following table, some commonly used attributes have been divided into three impact categories: high, medium and low. The multiple-instance attributes have been classified at the lowest level. That is, the performance overhead will increase if you do not specify compare values for one or more key values.

Table 13. Performance Impact by Attribute Group

Attribute Group High Medium Low

OS400_Acct_Jrn �

OS400_Alert �

OS400_APPN_Topology �

OS400_Comm_Async �

OS400_Comm_Bisync �

OS400_Comm_Ethernet �

OS400_Comm_SDLC �

OS400_Comm_Token_Ring �

OS400_Comm_X25 �

OS400_Controller �

OS400_Device �

OS400_Disk_Unit �

OS400_DB_Member �



OS400_I/O_Processor �

OS400_Job �

OS400_Job_Queue �

OS400_Line �

OS400_Message �

OS400_Network �

OS400_Object �

OS400_Security_Jrn �

OS400_Spool_File �

OS400_Storage_Pool �

OS400_Subsystem �

OS400_System_Status �

OS400_System_Values �

Table 13. Performance Impact by Attribute Group (continued)

Attribute Group High Medium Low

Maintaining OMEGAMON XE for OS/400 Performance



OverviewThis section contains information about how you can optimize OMEGAMON XE for OS/400 performance.

Creating situationsAn important consideration in designing situations is to minimize the conditions being monitored. This reduces the amount of system resources being used for monitoring.

Often there is a single symptom that signals a number of potential problems. If you monitor for that system only (and, when it is detected, activate monitors for the potential problems), significant resources can be saved over monitoring for all of the potential problems.

To demonstrate this design approach, suppose a situation monitors the line utilization for a given communication line. If the line utilization goes to 0 during a period in which this should not happen, the event could indicate any of the following possibilities

� The application using the line may have encountered an error and ended.

� The application may have completed normally.

� A communication hardware error may have brought down the link.

� An inquiry message may need a reply for processing to continue.

By monitoring only the line utilization and reacting with other monitors when the utilization goes to 0, you can save resources.



Minimizing the starting and stopping of monitoringWhen a situation raises an event, monitoring for the conditions does not stop. Attribute data is collected as long as the situation is active.

If monitoring has not been started for a situation named in an *EVALUATE_SITUATION activity monitoring program, monitoring starts when the *EVALUATE_SITUATION activity starts. Monitoring ends when the activity program has analyzed the conditions in the situation.

When possible, use embedded situations rather than the *EVALUATE_SITUATION activity program. If you want to use the *EVALUATE_SITUATION activity program, start the situation before the *EVALUATE_SITUATION activity begins to lessen performance impact.

Considerations for taking actionThe flow of activities specified with Take Action is controlled by the OMEGAMON XE for OS/400 jobs running in the QAUTOMON subsystem. These jobs compete for system resources along with other jobs in your system. Because of this, there may be a delay between the completion of one activity and the start of the successor activity.

If you want to minimize delays in execution of your user action choices, you can increase the priority of the OMEGAMON XE for OS/400 jobs. To change the priority of jobs, use the Change Class (CHGCLS) command to change the run priority of the QAUTOMON class.

Note: Remember that increasing the priority of the OMEGAMON XE for OS/400 jobs may increase the impact of situation monitoring and policy execution on other jobs in your system.

Response time for Take ActionSome of the Take Action commands must communicate with the jobs running in the QAUTOMON subsystem. The response time of these commands can be affected by the monitoring and automation tasks that are currently active.



Monitor what is neededMonitor only those attributes that you need and only when you need them. Monitoring a night batch job during daytime or monitoring interactive user jobs during the night is a waste of system resource. You probably will have a set of situations for the daytime and another set for nighttime.


Performance Problems

Performance Problems

Monitoring for performance problemsIf you experience long response times when working with OMEGAMON XE for OS/400 in an NPT, use the Work with Active Jobs (WRKACTJOB) command and look at the status of the jobs in subsystem QAUTOMON. If one or more of the jobs have a status ineligible (INEL), the activity level for the pool the jobs are running in is too small. To avoid this, you can do one or more of the following changes

� increase the activity level for the pool

� increase the pool size

� create another pool for all the QAUTOMON jobs

Monitoring for Files that Are Inactive



Overview The OMEGAMON XE for OS/400 provides a program that you can use to monitor for files that have had no activity. If the files are inactive for the amount of time you specify, the program sends a message to the message queue. You can then check the message queue or create a situation and alert that notifies you when a message is received.

For example, if your site has files that must be updated on a schedule, you can use OMEGAMON XE for OS/400 to monitor the files and verify that the changes occur.

Prerequisites for using the program You must be using OS/400 V4R2 or later.

Broad overview of the process To monitor for files that are inactive, you must perform these broad steps.

1. On the system for the OMEGAMON XE for OS/400, you must change the data areas for the program (such as the file you want to monitor and the library that contains the file).

2. You must create a situation that includes an action to start the program.

3. If you want to monitor the message queue for messages sent by the program, create a situation that monitors for the message.



Changing the data areas for the program If you want to use the program to monitor one file, you must change these data areas in the CANDLEWS library.

� maximum length of time that the file can be inactive (EXPLIMIT)

� name of the file you want to monitor (MONFILE)

� name of the library that contains the file you want to monitor (MONLIB)

For example, if you do not want the DBREQ file in the SWUS library to be inactive for more than 120 minutes, you would specify the following CHGDTAARA commands.

CHGDTAARA DTAARA(CANDLEWS/EXPLIMIT) VALUE(120)

CHGDTAARA DTAARA(CANDLEWS/MONFILE) VALUE(DBREQ)

CHGDTAARA DTAARA(CANDLEWS/MONLIB) VALUE(SWUS)



Creating a situation that starts the program Once you have changed the data areas for the program, you must u create a situation that starts the program.

When you create the situation, specify the action CALL CANDLEWS/WS0010 using the Action tab available on the Situation(s) dialog displayed when you are creating a situation.

For example, the following situation created using CandleNet Portal checks for the local time. You then select the Action tab on the dialog to specify the command that starts the program.

For additional information about creating situations , see in the online help.



Creating a situation to monitor for the message If you want to monitor the CCC message queue in the CANDLEWS library for CCC1000, create a situation that monitors for the message. For example, you can create a situation that uses

� the OS400_Message.ID attribute to monitor for the CCC1000 message

� the OS400_Messgae.Message_Queue attribute to monitor the CCC messages queue

� the OS400_Message.Message_Library attribute to specify that the CCC message queue is in the CANDLEWS library

For additional information about creating situations and specifying actions, see the online help.

Tuning QAUTOMON Subsystem Jobs


Tuning QAUTOMON Subsystem Jobs

OverviewThe subsystem QAUTOMON uses the *BASE pool. Thus, you may need to tune some parameters related to the *BASE pool if you experience performance problems with OMEGAMON XE for OS/400.

Performance problems with OMEGAMON XE for OS/400 can appear in various forms

� long response time when working with OMEGAMON XE for OS/400 on an NPT

� long process time for activating or deactivating situations

� long process time for starting or stopping activity programs

� connection problems between the managing and managed systems

� connection problems between the managing system and the CCC interface

When you see one of the above problems, use the Work with Active Jobs (WRKACTJOB) command and look at the status of the jobs in subsystems QAUTOMON. If one or more of the jobs have status ineligible (INEL), the activity level for the pool may be too small. To avoid this, you can make one or more of these changes.

� increase the activity level of the *BASE pool.

� increase *BASE pool size.

� create another pool for the QAUTOMON jobs.


Attribute Grouping

Attribute Grouping

OverviewSome multiple-instance attributes can cause a very large number of sets of data to be gathered. Specifying predicates for additional attributes in the same attribute group may reduce the amount of data that needs to be collected and reduce the performance impact.

Below you will find a list of key attributes that should be specified to each functional area.

Accounting Journal Notification (OS400_Acct_Jrn) attributesOne or more of these attributes should be specified.

� OS400_Acct_Jrn.Job_Name

� OS400_Acct_Jrn.User

File Member (OS400_DB_Member) attributesOne or more of these attributes should be specified.

� OS400_DB_Member.Member

� OS400_DB_Member.File

� OS400_DB_Member.Library

Object (OS400_Object) attributesOne or more of these attributes should be specified.

� OS400_Object.Library

� OS400_Object.Name

� OS400_Object.Type

Attribute Grouping


Spooled file (OS400_Spool_File) attributesOne or more of these attributes should be specified.

� OS400_Spool_File.Form_Type

� OS400_Spool_File.User_Data

� OS400_Spool_File.Job_User

� OS400_Spool_File.Output_Queue_Name

� OS400_Spool_File.Output_Queue_Library


Disk Space Requirements


Monitoring space requirementsThe disk space required depends on the size and work load of your system. Important factors are the number of

� active jobs on the system

� jobs

� spool files

� objects on the system

� communication lines

� messages

� active situations

� active policies

Library QAUTOTMP contains the temporary data collected by OMEGAMON XE for OS/400. The library could be empty if OMEGAMON XE for OS/400 has not been started. Display the library to see the current size of the temporary data.



Guide to Candle Customer Support 269

Guide to CandleCustomer Support

IntroductionCandle Corporation is committed to producing top-quality software products and services. To assist you with making effective use of our products in your business environment, Candle is also committed to providing easy-to-use, responsive customer support.

Precision, speed, availability, predictability—these terms describe our products and Customer Support services.

Included in this Guide to Candle Customer Support is information about the following:

Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271– Telephone Support

– eSupport

– Description of Severity Levels

– Service-level objectives

– Recording and monitoring calls for quality purposes

– Customer Support Escalations

– Above and Beyond

Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276– Assigned Support Center Representative (ASCR)

– Maintenance Assessment Services (MAS)

– Multi-Services Manager (MSM)

A


Customer Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . 278– Link to Worldwide Support Telephone and E-mail information


Base Maintenance Plan


OverviewCandle offers a comprehensive Base Maintenance Plan to ensure that you realize the greatest value possible from your Candle software investments. We have more than 200 technicians providing support worldwide, committed to being responsive and to providing expedient resolutions to support requests. Technicians are available worldwide at all times during the local business day. In the event of an after-hours or weekend emergency, our computerized call management and forwarding system will ensure that a technician responds to Severity One situations within one hour. For customers outside of North America, after-hours and weekend support is provided in English language only by Candle Customer Support technicians located in the United States.

Telephone supportCandle provides consistently reliable levels of service—thanks to our worldwide support network of dedicated experts trained for specific products and operating systems. You will always work with a professional who truly understands your problem.

We use an online interactive problem management system to log and track all customer-reported support requests. We give your support request immediate attention by routing the issue to the appropriate technical resource, regardless of geographic location.

Level 0 Support is where your call to Candle Customer Support is first handled. Your support request is recorded in our problem management system, then transferred to the appropriate Level 1 support team. We provide Level 0 manual interaction with our customers because we support more than 170 products. We feel our customers would prefer personal interaction to a complex VRU or IVR selection menu.

Level 1 Support is the service provided for initial support requests. Our Level 1 team offers problem determination assistance, problem analysis, problem resolutions, installation assistance, and preventative and corrective service information. They also provide product usage assistance.



Level 2 Support is engaged if Level 1 cannot provide a resolution to your problem. Our Level 2 technicians are equipped to analyze and reproduce errors or to determine that an error is not reproducible. Problems that cannot be resolved by Level 2 are escalated to Candle’s Level 3 R&D support team.

Level 3 Support is engaged if a problem is identified in Candle product code. At Level 3, efforts are made to provide error correction, circumvention or notification that a correction or circumvention is not available. Level 3 support provides available maintenance modifications and maintenance delivery to correct appropriate documentation or product code errors.

eSupportIn order to facilitate the support process, Candle also provides eSupport, an electronic full-service information and customer support facility, via the World Wide Web at www.candle.com/support/. eSupport allows you to open a new service request and update existing service requests, as well as update information in your customer profile. New and updated service requests are queued to a support technician for immediate action. And we can respond to your request electronically or by telephone—it is your choice.

eSupport also contains a continually expanding knowledge base that customers can tap into at any time for self-service access to product and maintenance information.

The Candle Web Site and eSupport can be accessed 24 hours a day, 7 days a week by using your authorized Candle user ID and password.

Description of Candle severity levelsResponses to customer-reported product issues and usage questions are prioritized within Candle according to Severity Code assignment. Customers

http://www.candle.com/support/



set their own Severity Levels when contacting a support center. This ensures that we respond according to your individual business requirements.

Candle has established the following service-level objectives:

Severity 1 Crisis

A crisis affects your ability to conduct business, and no procedural workaround exists. The system or application may be down.

Severity 2High

A high-impact problem indicates significant business effect to you. The program is usable but severely limited.

Severity 3Moderate

A moderate-impact problem involves partial, non-critical functionality loss or a reasonable workaround to the problem. A “fix” may be provided in a future release.

Severity 4Low

A low-impact problem is a “how-to” or an advisory question.

Severity 5Enhancement Request

This is a request for software or documentation enhancement. Our business units review all requests for possible incorporation into a future release of the product.

Call Status Severity 1 Goal

Severity 2 Goal

Severity 3 Goal

Severity 4 Goal

Severity 5Goal

First Call Time to Answer

90% within one minute

Level 1 Response(Normal Business Hours)

90% within 5 minutes

90% within one hour

Level 2 Response(Normal Business Hours)

Warm Transfer

90% within two hours

90% within eight hours

The above information is for guideline purposes only. Candle does not guarantee or warrant the above service levels. This information is valid as of October 1999 and is subject to change without prior notice.



Scheduled follow-up (status update)

Hourly or as agreed

Daily or as agreed

Weekly or as agreed Notification is made when an enhancement is incorporated into a generally available product.

Notification is made when a fix is incorporated into a generally available product.

Call Status Severity 1 Goal

Severity 2 Goal

Severity 3 Goal

Severity 4 Goal

Severity 5Goal

The above information is for guideline purposes only. Candle does not guarantee or warrant the above service levels. This information is valid as of October 1999 and is subject to change without prior notice.



Recording and Monitoring Calls for Quality PurposesCandle is committed to customer satisfaction. To ensure that our customers receive high levels of service, quality and professionalism, we'll monitor and possibly record incoming and outgoing Customer Support calls. The information gleaned from these calls will help us serve you better. If you prefer that your telephone call with Candle Customer Support in North America not be monitored or recorded, please advise the representative when you call us at (800) 328-1811 or (310) 535-3636.

Customer Support EscalationsCandle Customer Support is committed to achieving high satisfaction ratings from our customers. However, we realize that you may occasionally have support issues that need to be escalated to Candle management. In those instances, we offer the following simple escalation procedure:

If you experience dissatisfaction with Candle Customer Support at any time, please escalate your concern by calling the Candle support location closest to you. Ask to speak to a Customer Support manager. During standard business hours, a Customer Support manager will be available to talk with you or will return your call. If you elect to hold for a manager, you will be connected with someone as soon as possible. If you wish a return call, please tell the Candle representative coordinating your call when you will be available. After contacting you, the Customer Support manager will develop an action plan to resolve your issue. All escalations or complaints received about support issues are logged and tracked to ensure responsiveness and closure.

Above and BeyondWhat differentiates Candle's support services from our competitors? We go the extra mile by offering the following as part of our Base Maintenance Plan:

� Unlimited multi-language defect, installation and operations support� eSupport using the World Wide Web� Regularly scheduled product updates and maintenance provided at no

additional charge� Over 200 specialized technicians providing expert support for your

Candle products

Enhanced Support Services



OverviewOur Base Maintenance Plan provides a high level of software support in a packaged offering. However, in addition to this plan, we have additional fee-based support services to meet unique customer needs.

The following are some examples of our added-value support services:

� Assigned Support Center Representative Services (ASCR)

– An assigned focal point for managing support escalation needs– Proactive notification of available software fixes– Proactive notification of product version updates– Weekly conference calls with your ASCR to review active problem

records– Monthly performance reviews of Candle Customer Support service

levels– Optional on-site visits (extra charges may apply)

� Maintenance Assessment Service (MAS)

– On-site assessment services– Advice about product maintenance and implementation– Training your staff to develop efficient and focused procedures to

reduce overall cost of ownership of your Candle software products– Analysis of your Candle product environment: versions, updates,

code correction history, incident history and product configurations– Reviews to ensure that purchased Candle products and solutions are

used effectively

� Multi-Services Manager (MSM)

Multi-Services Manager provides highly valued services to customers requiring on-site full time expertise to complement their technical resources.

– Dedicated on-site Candle resource (6 months or one year) at your site to help ensure maximum use and effectiveness of your Candle products



– Liaison for all Candle product support activities, coordination and assistance with implementation of all product updates and maintenance releases

– Works with your staff to understand business needs and systems requirements

– Possesses technical and systems management skills to enhance your staff’s knowledge and expertise

– Other projects as defined in Statement of Work for MSM services

Customer Support Contact Information


Customer Support Contact Information

Link to Worldwide Support Telephone and E-mail informationTo contact Customer Support, the current list of telephone numbers and e-mail addresses can be found on the Candle Web site, www.candle.com/support/.

Select Support Contacts from the list on the left of the page.

http://www.candle.com/support/

Index 279

Index

Aaccounting journal attributes 39, 44Adobe portable document format 12alert notification attributes 45, 49ASCR

assigned support center representative 276

assigned support center representativeASCR 276

attributesaccounting journal (OS400_Acct_Jrn) 39,

44alert notification (OS400_Alert) 45, 49collection interval 32combining 32communications (OS400_Comm) 50, 69controller description

(OS400_Controller) 71database member

(OS400_DB_Member) 74device description (OS400_Device) 78,

80disk unit (OS400_Disk_Unit) 82, 85I/O processor (OS400_I/O_Processor) 87,

89Job (OS400_Job) 90, 108Job Queue (OS400_Job_Queue) 90–108Line Description (OS400_Line) 109message (OS400_Message) 112, 116multiple instance 31, 252network (OS400_Network) 121, 126notification 30object (OS400_Object) 127, 136sampled 30, 31security journal

(OS400_Security_Jrn) 146, 182single-instance 31spool file (OS400_Spool_File) 183, 187

storage pool (OS400_Storage_Pool) 137, 140

subsystem (OS400_Subsystem) 142, 144system status

(OS400_System_Status) 189, 190system values

(OS400_System_Values) 191, 212types of 30–31

auto-start 218auto-start situations 218

CCandle Management Server 19CandleNet Command Center 22CandleNet Portal

benefits 19formats for information 228

CandleNet Portal server 19collection interval 32combining attributes 32command security 38communications 234communications attributes 50, 69components of CCC 19configuration 234contents of this guide 10controller description attributes 71creating multiple workspaces 228customer service

telephone support 271customer support

base maintenance plan 271contact information 278enhanced support services 276eSupport 272severity levels 272


Ddata

monitoring 35database member attributes 74databases and objects 235device description attributes 78, 80Disk and I/O 235Disk and I/O workspace 235disk unit attributes 82, 85documentation set 11

Eedit a workspace 230eSupport

customer support 272event

investigating 233Event workspace, opening 233

Ffeatures

non-programmable terminal interface 250user action 249

features of OMEGAMON XE for OS/400 22, 249–250

Gguide contents 10

II/O processor attributes 87, 89I/O Processor Report 235investigating an event 233

Jjob attributes 90, 108job queue attributes 90–108jobs and queues 235Jobs and Queues workspace 235

Lline description 109linking workspaces 231

Mmaintenance assessment service

MAS 276MAS

maintenance assessment service 276message attributes 112, 116Messages and Spool workspace 236monitor interval 252monitoring agents 19monitoring strategy

examples 35MSM

multi-services manager 276multiple-instance attribute 252multiple-instance attributes 31multi-services manager

MSM 276

Nnetwork (OS400_Network) attributes 121,

126non-programmable terminal interface 250notification attribute 30

Oobject (OS400_Object) attributes 127, 136OMEGAMON 22OMEGAMON XE

definition 18OMEGAMON XE for OS/400

advanced monitoring facilities of 25features 249–250performance considerations 251–267tasks 23using with CCC 22

OMEGAMON XE for OS/400 featuresnon-programmable terminal interface 250

Index 281

user action 249OMEGAMON XE OS/400

benefits of 24open a workspace 228operational area

definition of 35OS/400 Communications Report 234OS/400 Configuration Report 234OS/400 Database Report 235OS/400 Disk Report 235OS/400 Jobs and Queues Report 235OS/400 Objects Report 235OS/400 Operator Messages Report 236OS/400 Output Spool Report 236OS/400 Storage Pool Report 236OS/400 System Status Report 236OS400_Acct_Jrn (accounting journal)

attributes 39–44OS400_Alert (alert notification)

attributes 45–49OS400_Comm (communications)

attributes 50–69OS400_Controller (controller description)

attributes 71OS400_DB_Member (database member)

attributes 74OS400_Device (device description)

attributes 78–80OS400_Disk_Unit (disk unit) attributes 82–

85OS400_I/O_Processor (I/O processor)

attributes 87–89OS400_Job (job) attributes 90–108OS400_Job_Queue (job queue)

attributes 90–108OS400_Line (line description)

attributes 109OS400_Message (message) attributes 112–

116OS400_Network (network) attributes 121–

126OS400_Object (object) attributes 127–136OS400_Security_Jrn (security journal)

attributes 146–182OS400_Spool_File (spool file)

attributes 183–187OS400_Storage_Pool (storage pool)

attributes 137–140OS400_Subsystem (subsystem)

attributes 142–144OS400_System_Status (system status)

attributes 189–190OS400_System_Values (system values)

attributes 191–212

Pperformance

attributes 252autostart situations 253CandleNet Portal usage 256monitor interval 252monitoring situations 254overhead 254

performance considerations 251–267predefined situations 219predefined workspaces 226printing problems 12product-provided situations 223

descriptions of 223properties

defining for a workspace 232

Rrefresh a workspace 229reload a workspace 229reports

OS/400 Communications Report 234OS/400 Configuration Report 234OS/400 Database Report 235OS/400 Disk Report 235OS/400 Jobs and Queues Report 235OS/400 Operator Messages Report 236OS/400 System Status Report 236OS/400 System Values Report 236


Ssampled attribute 30saving a new workspace 231saving a workspace 231security 38security journal (OS400_Security_Jrn)

attributes 146, 182server, CandleNet Portal 19severity levels

customer support 272single-instance attribute 31situations 223

auto-start 218OS400_Address_Critical 222OS400_Comm_IOP_Utilization_High 22

1OS400_Communications_Line_Failed 22

3OS400_CPU_Util_Warning 221OS400_Disk_Capacity_Critical 222OS400_Disk_IOP_Util_Warning 221OS400_Disk_Util_Critical 220OS400_Disk_Util_Warning 220OS400_Interactive_Jobs_CPU_High 222OS400_Job_Avg_Response_Time_High

221OS400_Network_Attribute_Changed 219OS400_OMA_Message_Log 223OS400_Permanent_Address_Warning 22

2OS400_Pool_Faulting_Warning 221OS400_Pool_Transitions_High 220OS400_Snads_Critical 220OS400_Snads_Ended 219OS400_Snads_Job_Missing 219OS400_Snads_Router_Failed 220OS400_System_ASP_Warning 222OS400_System_Value_Changed 219OS400_Temp_Address_Warning 222predefined 219

situations, predefined 218spool file (OS400_Spool_File)

attributes 183, 187stop a workspace 229storage pool (OS400_Storage_Pool)

attributes 137, 140subsystem (OS400_Subsystem)

attributes 142, 144suspend a workspace 229system status (OS400_System_Status)

attributes 189, 190system values (OS400_System_Values)

attributes 191, 212System workspace 236

Ttelephone support

customer service 271This 219types of attributes 30–31

Uuser action 249using attributes 29using OMEGAMON XE for OS/400

workspaces 227

VV300

new features 15

WWhat’s New in V300 15When 218workspace

creating multiple 228defining properties 232linking 231opening 228refreshing 229reload 229saving 231saving new 231

Index 283

stop 229suspend 229

workspace, editing 230workspace, Event

opening 233workspaces 227

accessing 227Communications 234Configuration 234Databases and Objects 235disk and I/O 235Jobs and Queues 235relationship to attributes 226System 236using 227

workspacesMessages and Spool 236


Date post:	29-Apr-2018
Category:	Documents
Upload:	lamcong
View:	237 times
Download:	5 times

OMEGAMON XE for OS/400 User's Guide, Version...

Documents