CA SYSVIEW Performance Management Scenarios, How to Articles, Videos, and Online Help Topics

Transcription

1 CA SYSVIEW Performance Management Scenarios, How to Articles, Videos, and Online Help Topics Date: 10-Oct-2016

2

3 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2016 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. 10-Oct /354

4 Table of Contents Profiles How to Set Profile Keyword Values to Have No Value How to Set Profile Keywords Back to the Default Value Hierarchical Profile Settings Alerts Exception Definition Best Match Rules Summarizing Exception Alerts Command Syntax WTO Console Exception Messages Modify Threshold, State, and Monitor Definitions How To Direct SNMP Trap Event Notifications Write Log Messages to a DD name Execute REXX IMOD on an Exception Event Capture on an Exception How To Articles How to Automatically Update Screen Displays How To Cancel an Address Space or TCB How to Compile a MIB for MIB Browsing Commands How to Create a Predefined PLOT Member How to Create a List of Predefined PLOT Members How Implicit Commands Work How Threshold and State Definitions Work Threshold Rule Types State Rule Types How to Define ISPF or TSO Applications How to Display Cross System Data from Multiple Systems How To Dump Storage Using the Point-and-Shoot Method How to Enter Command Parameters with Lowercase or Embedded Blanks How to Enter Long Commands How to Find Abended IMS Transactions Scenarios, How to Articles, Videos, and Online Help Topics 4

5 How to Find IMS Threshold Exceptions How to Find Multiple Occurrences of a Module How to Increase the Command Input Area How to Recall or Retrieve a Previous Command How to Scroll Command Displays How to View Available Line Commands View the Line Command Assist Display Execute a Line Command for a Command Access Help from LCASSIST Change the Default Cursor Line Command How to Verify APF Authorization for a Data Set How to Subset a Display Using the SELECT Command Command Syntax Parameters How to Find Help for a Specific Topic (FINDHELP) Online Help Topics CICS Help CICS Common Storage Area Panel Auxiliary Temporary Storage Panel Temporary Storage Panel EIBRESP Response Codes Panel CICS Global User Exits Panel Automatic Initiate Descriptors Panel CICS Transaction Logging Log Only CICS transaction with Exceptions Log Only CICS transaction with Exceptions by Transaction ID Line Commands Block Line Commands Enter Multiple Line Commands Line Command Assist Special Line Commands REXX Add the REXX API Environment Convert the REXX Library to Variable Blocked Delete the REXX API Environment REXX Functions Summary Option for CICS Help Assign a User ID to the GSVI CICS Transaction How is the GSVI Transaction Started? Scenarios, How to Articles, Videos, and Online Help Topics 5

6 How Can a User ID be Assigned to the Transaction? CICS Data Collection Abnormal Termination CICS State Metrics and Possible Values DB Control DB2 Connection Files IP Connections CICS Max Task Condition CICS Pipelines Programs CICS Remote Connections CICS TCP/IP Connection TCP/IP Services CICS Terminals CICS Transactions Transient Data Queues CICS VTAM Connection CICS Web Interface WebSphere MQ Connections Define CICS Transaction IDs What Transaction IDs are Needed? Can Transaction IDs be Changed? Why Do I Want to Change the Transaction IDs? How Do I Change the Transaction IDs? Can the Dynamic Transaction Scan be Avoided? CICS Transaction Data Collection Data, Statistics, and Measurements Transaction Detail Record Configuration Options that Control Transaction Data Collection Collecting Program Usage Information Collecting File Usage Information Collecting EXEC CICS Requests Setting Options for Multiple CICS Regions Connect to a CICS Logger Data Set Allocation Display Currently Active CICS Address Spaces Dump Processing Architecture Overview Installation Extended CPU Monitoring Map CICS File Requests Transaction Lifetime, Response time, and Runtime Explained Transactions Required to be Active Scenarios, How to Articles, Videos, and Online Help Topics 6

7 How can I specify a list of required transactions? CICS Data Collection Start Mode - WARM or COLD The Difference Between Start Mode Types How to Specify the Start Mode CICS Data Collection Transaction Syntax Starting the CICS Data Collector Stopping the CICS Data Collector Restarting the CICS Data Collector Initialization Options Parameters CICS Monitor Activation Initialization Termination CICS Monitor Exit Interface Requirements Programming Resources Monitor Exit Interface Functions Return Codes Migration Programming Ideas CA SYSVIEW Base Product Address Spaces API Return Codes Audit Events AMRF_ACTION APFLIST_MODIFY ASID_ACTION CICS_CEMT CICS_EI_TRACE_MODIFY CICS_MONITOR_SHUTDOWN CICS_MONITOR_START CICS_STATE_MODIFY CICS_THRESHOLD_MODIFY CICS_TRAN_CANCEL CICS_TRANCANCEL_MODIFY CICS_TRANOPTS_MODIFY CICS_TSQUEUE_MODIFY COMMAND_PRIMARY COMMAND_SUBCOMMAND CONSOLE_COMMAND DATASET_SERVICES DATASET_ZAP DUMPDS_MODIFY Scenarios, How to Articles, Videos, and Online Help Topics 7

8 DYNEXIT_MODIFY ESRTABLE_MODIFY IDMS_TASK_CANCEL IMS_COMMAND IMS_SPOC_COMMAND JES_JOB_MODIFY JES_OUTDES_MODIFY JES_OUTPUT_MODIFY LGSTREAM_ACTION LGSTREAM_DRO LINKLIST_MODIFY LINKSET_MODIFY LPA_MODIFY METRIC_ALERT_ALTER MQ_CHANNEL_MODIFY MQ_COMMAND MQ_QUEUE_MODIFY MQ_TOPIC_MODIFY PERF_MONITOR_MODIFY PERF_STATE_MODIFY PERF_THRESHOLD_MODIFY PPT_MODIFY REGPROD_MODIFY SESSION_LOGOFF SESSION_LOGON SET_DISPATCH_PRIORITY SET_EXTENDED_PRIVATE SET_GRANDE_PRIVATE SET_SCHENV_RESOURCE STORAGE_ALTER SUBSYSTEM_MODIFY SVCTABLE_MODIFY SYSVIEW_MODIFY SYSVIEW_SHUTDOWN SYSVIEW_START TASK_STOP TASK_START TSOTABLE_MODIFY USER_EVENT_MESSAGE WTOR_REPLY CA OPS/MVS Audit Event Notification Enabling Event Notification CA SYSVIEW Library Caching Scenarios, How to Articles, Videos, and Online Help Topics 8

9 Why Do I Want to Cache Library Members? Does Everyone have to Participate in Library Caching? How do I View the Contents of the Library Cache? How do I Maintain the Contents of the Library Cache? How do I Delete a Member from the Library Cache? How do I Compress unused Members from the Library Cache? How do I Remove all Members from the Library Cache? How do I Set which Library Types are to be Cached? CA SYSVIEW Server CA SYSVIEW SMF Records View SMF Records Online Configuration Options Specifying Record Types Record Layouts CA SYSVIEW Start Mode - WARMSTART or COLDSTART What is the Difference between a WARM and COLD Start? How is the Start Mode Specified? Main Services Address Space Main Services Tasks CA SYSVIEW System Configuration Options Data Set Location Member Naming Conventions Multiple Product Installations Configuration Caching Options and Descriptions CLIST or CLISTLIB Member, What is the Difference? Console Interface Communication Requirements Installation of Console Interface Using the Console Interface Customization Convert CA SYSVIEW REXX Library to Variable Blocked Cross-System Communications with Multiple Servers Cross-System Data Servers Cross-System Session Servers Cross-System Session Connections Any Setup or Configuration Required to Connect all Systems? Can Cross-System Connections be Secured by userid? Can Connections between Systems be Controlled or Rejected? Cross-System Session Logons What User ID is used when a Cross-System Session is Created? What do I do if my User ID is Different on a Remote System? Scenarios, How to Articles, Videos, and Online Help Topics 9

10 How Can we Require a User to Log on to a Remote System? Dashboards Display Why Create a Dashboard? What Data can I put into a Dashboard? Where are Dashboards Defined? How do I Display a Dashboard? Do I Need a Specific Screen Size to Display Dashboards? Where Can I See a List of Defined Dashboards? Do I Need to Know REXX or any Other Language to Define Dashboards? What Does a Dashboard Window Pane Look Like? What is the Syntax for Creating a Dashboard? Are There any Tips to Consider when Defining and Using Dashboards? What are Widgets? What are the Types of Widgets? How do I Generate a Widget? What Metrics can be Displayed using a Value Oriented Widget? What Metrics can be Displayed using a Status Oriented Widget? Notifications on Exceptions or Thresholds Commands to Set Exception Actions Event Capture Definition Fields Parameters Passed to Event Capture Event Capture Members Templates Groups Step-by-Step Instructions GSVXBAT Batch Interface User ID for the Batch Session Initialization Parameters DD Statements SYSIN Input Card Keywords Rules Help Member Control Keyword Statements Help Member Display Attributes Help Topic Naming Conventions Commands Messages Information Topics Installation Topics How To Topics Included Members Help Using Hyperlinks Special Keywords Special Characters Scenarios, How to Articles, Videos, and Online Help Topics 10

11 Implementing External Security (SAF) Create Test User Group Run the SAF Generator Utility Determine Entity Types to Bypass Using Command Groups Command Field Checking Bypassing Job Name Checking Action Codes Enabling WARN Mode Review SAF Statistics Library Concatenation - USER, SITE, and SYSTEM Why do I Want to Define SITE and USER Data Sets? Are USER, SITE, and SYSTEM Data Sets Required? What Parmlib Members are Eligible for USER Data Sets? What Data Sets are Currently Defined? Where do I Define SYSTEM Data Sets? Where do I Define SITE Data Sets? Where do I Define USER Data Sets? Can Multiple Users Share a Common USER Data Set? Does the CICS Data Collector use USER, SITE, and SYSTEM Data Sets? What are the Data Set DCB Attributes Required for Each Library Type? Symbolic Substitution Variables for Data Set Name What Control Statements are Available to Customize Parameter Members? How do I Create My Own Menu? How do I Augment the Primary Menu? Logical Groups Usage Definition Source Maintaining Definitions Migration Migration From Releases Prior to CA SYSVIEW CICS Logical Group Migration Concerns Conversion Utility - GSVYLGCV Logical Group Types Menu Customization Defining Available Menus in the MENU Parmlib Member Defining Menu Panels Information Line Keywords Menu P anel Definition Errors Persistent Data Store Introduction Architecture Overview Scenarios, How to Articles, Videos, and Online Help Topics 11

12 Installation DATALIB Architecture Administration Migration Security How to Copy, Delete, or Rename Objects User Replaceable Modules GSVBSSID - Default SYSVIEW Subsystem ID GSVBUXLT - User Translate Tables RXDISP Formatting Extentions Stack Data Summary Text Record Summary Control Statement Summary Control Statement Syntax Control Statement Parameters Attribute Definition Records Field Definition Records Info Field Definition Records SMF Records - How to Create a Formatting Routine Specifying The Subsystem Identifier (SSID) Started Tasks Local 3270 Interface ISPF Interface TSO Interface CICS Interface Batch API Rexx API CA Global Subsystem (GSS) CA Roscoe Monitor CA Roscoe SYSVIEW User Session CICS Data Collection Supported Software z/os and JES JES CICS DB IMS WebSphere MQ CA Datacom CA Datacom CICS Services CA IDMS CA Vantage GMI Interface CA Cross-Enterprise APM Scenarios, How to Articles, Videos, and Online Help Topics 12

13 CA Chorus Infrastructure Management for Networks and Systems System Condition Monitor IMODS - SCM System Linkage Index and ASID Reuse System Linkage Index Reuseable ASIDs System Overview Information Template Members UNIQFLDS Command Command Syntax Parameters User-Defined Commands Where are the User Commands Defined? Where are the User Commands Defined? Where can I Find the Syntax for Creating a Definition? User-Defined Health Check Drill-Down Commands Where Are the Drill-Down Commands Defined? Where Can I See a List of Active Definitions? Where Can I Find the Syntax for Creating a Definition? User-Defined Line Commands Where are the Line Commands Defined? Where Can I see a List of Active Definitions? Where can I find Example Definitions? What is the Syntax for Creating a Definition? WTO Console Messages Related Configuration Options XSystem Component Logical Group Usage CA SYSVIEW for CICS Data Collection Simplified How a Data Collection Abnormal Termination is Restarted How a CICS Transaction Detail Record is Logged How the Retention Period Determines Exception Logging How Logical Groups Simplify Data Collection Start and Stop Data Collection CICS Data Collection Shutdown and Restart Methods Manual Shutdown Manual Shutdown with Automatic Restart Automatic Shutdown at CICS Termination Scenarios, How to Articles, Videos, and Online Help Topics 13

14 IMSMON User Exit Tailor Logstream-Related Commands Using the Filter Display Glossary A B C D E F G H I J K L, M N, O, P Q, R S T U V W X Y, Z CA Cross-Enterprise APM CA Cross-Enterprise APM - CICS Transaction Trace Integration CA Cross-Enterprise APM - Dashboard Integration CA Cross-Enterprise APM - IMS Transaction Trace Integration Systems Information Decimal and Hexadecimal Suffixes Scenarios, How to Articles, Videos, and Online Help Topics 14

15 IEASYSxx System Parmlib Member Parameters Operating System Names Phonetic Alphabet PSW Command - Program Status Word WTO Descriptor Codes WTO Route Codes WebSphere MQ Tuning the MQ Buffer Pool TCP/IP Diagnosing Problems with TCP/IP based applications Security Considerations for TCP/IP Resources What are the security requirements for the server address space? What are the security requirements for the NETSTAT menu items? What are the security requirements for the TCP/IP commands? What are the security requirements for the CSM commands? Should NETSTAT be removed from the TSO AUTHCMD table? CA SYSVIEW Data Collection Control Data Collection Using the Event Scheduler Where the Scheduler Runs Data Collection Administration Migrating the Event Scheduler Data Collection Events Enable and Disable Data Collection Metrics Install CA Datacom CICS Service Facility Data Collection CAICCI Setup Considerations CA ROSCOE Monitor Installation Enable CA SYSVIEW Displays on a System Console Log Streams Scenarios, How to Articles, Videos, and Online Help Topics 15

16 MVS System Logger Overview Common MVS System Logger terms Writing to a DASD-only Log Stream Defining a DASD-only Log Stream When is log data or an offload data set physically deleted? How to size an offload data set? Processing Log Streams Can all application programs use the LOGR subsystem? How can I view the contents of the log streams? Can a log stream be used as file input to a batch program? How can I copy the contents of a log stream to a sequential file? Does the exit program display any information about the log stream? What is the syntax for the SUBSYS parameters? Any installation or setup required? Sizing of Log Streams Sizing offload data sets Get Statistics on the Contents of a Log Stream Usage of MVS Log Streams Log Stream Definitions Log Data Types Configuration Options Security Requirements Videos Getting Started Videos Using CA SYSVIEW to Manage CICS Videos Using CA SYSVIEW to Manage IMS Videos Scenarios, How to Articles, Videos, and Online Help Topics 16

17 Scenarios, How to Articles, Videos, and Online Help Topics This section includes the following scenarios, how to articles, and online help topics: Profiles (see page 18) Alerts (see page 20) How To Articles (see page 43) Online Help Topics (see page 74) CA SYSVIEW for CICS Data Collection Simplified (see page 274) CICS Data Collection Shutdown and Restart Methods (see page 277) IMSMON User Exit - Help (see page 280) Tailor Logstream-Related Commands Using the Filter Display (see page 281) Glossary (see page 283) CA Cross-Enterprise APM (see page 290) Systems Information (see page 295) WebSphere MQ (see page 310) TCP/IP (see page 312) CA SYSVIEW Data Collection (see page 318) Install (see page 327) Log Streams (see page 332) Videos (see page 353) 10-Oct /354

18 Profiles This section contains information and tips about the profiles. How to Set Profile Keyword Values to Have No Value (see page 18) How to Set Profile Keywords Back to the Default Value (see page 18) Hierarchical Profile Settings (see page 19) How to Set Profile Keyword Values to Have No Value Setting profile keyword values so they have no value For certain profile keywords you can use the value NONE to set a value in your profile that will indicate the keyword should have no value. This prevents the keyword from reverting back to the default value. Check the documentation for a keyword to see if it allows the NONE value. Example: The DEFAULT profile has a value of S defined for the ACTIVITY CSRLINECMD keyword and you do not want to have a value defined for CSRLINECMD. To change the default profile value, set the value of the ACTIVITY CSRLINECMD to NONE. This will prevent the value of the ACTIVITY CSRLINECMD value from reverting back to the default. To set the value of ACTIVITY CSRLINECMD back to the default value, set the ACTIVITY CSRLINECMD value to DEFAULT. How to Set Profile Keywords Back to the Default Value You can use a value of DEFAULT to set the value of a profile keyword back to the default value. The default value can be: A value in the GENERAL section of your profile The value in the DEFAULT profile The default value for the keyword defined in the documentation For instance: If you set the value of PF1 to DEFAULT for the MTT command, the value will revert back to the value of PF1 in the GENERAL section of your profile. 10-Oct /354

19 If you do not have a value defined in the GENERAL section of your profile and the DEFAULT profile has a value defined for PF1, it will be the value of PF1 in the DEFAULT profile. If there is not a value defined in the DEFAULT profile for PF1, it will revert back to the default value for PF1 which is HELP. Hierarchical Profile Settings The user settings stored in the CA SYSVIEW Performance Management profile are hierarchical. Settings can be stored in the user profile of an individual or in a site specific DEFAULT profile. If a user has not altered or specified a value for a specific profile setting, the setting for the item will be retrieve in the following hierarchical order User profile Site DEFAULT profile 3. Global internal defaults 10-Oct /354

20 Alerts This section contains information and tips about Alerts. Exception Definition Best Match Rules (see page 20) Summarizing Exception Alerts (see page 21) WTO Console Exception Messages (see page 23) Modify Threshold, State, and Monitor Definitions (see page 27) How To Direct SNMP Trap Event Notifications (see page 28) Write Log Messages to a DD name (see page 32) Execute REXX IMOD on an Exception (see page 36) Event Capture on an Exception (see page 39) Exception Definition Best Match Rules CA SYSVIEW Performance Management evaluates data collection metrics to determine if a metric has exceeded a limit or triggered an exception. CA SYSVIEW Performance Management uses a best match process to determine which exception definition, if any, to use for evaluating a metric. Only one definition is used. The default sort order in which the definitions display indicates how the best match process is evaluated. When viewing the definitions in order, the last definition that matches all criteria is used to evaluate the metric. A match is determined using the following definition attributes: Metric name Resources State Rule type Day of week Active days of week Time of day Time range of definition Start time End time Preference is given to the following items: 10-Oct /354

21 Definitions with more specific resource arguments Definitions with fewer active days. For example, weekdays (Mon-Fri) are better than Everyday (Sun-Sat). Definitions with smaller time range. For example, time range of 2 hours is better than 24 hours. Definitions with active days later in the week. For example, if today is Wednesday, WED-THU is better than TUE-WED. Definitions with later start times. For example, if the current time is 12:00 noon, 12:00 to 14:00 is better than 10:00 to 12:00. Summarizing Exception Alerts CA SYSVIEW Performance Management has over 1,000 variable metrics that can be used to monitor system resources or resources from subsystem components such as: CICS IMS WebSphere MQ TCP/IP CA SYSVIEW Performance Management typically monitors several 100,000 resources. You can create exception alerts for each and every resource or metric. The command ALERTSUM is available to summarize and organize the monitoring of resources and metrics. Example commands and displays: Alert summarization menu Alert summary by owner Alert summary by owner and resource Alert summary by owner and instance Alert summary by owner, instance and resource The monitored exception alerts can be summarized at several different levels: 10-Oct /354

22 Owner Display a single summary data row for each owner. If the owner has multiple child instances, the the alert information is rolled-up into the owner summary data row. Possible owners: SYSTEM MVS CICS IMS TCP/IP WebSphere MQ Owner Display a single summary data row for each owner. Display a single data row for each /Resour resource summary group that is associated with the owner. ce If the owner has multiple child instances, the alert information is rolled-up into the owner summary data row and the summary resource resource data rows. Instanc e Resour ce Display a single summary data row for each owner. Display a single data row for each instance that summarizes any associated resource summary groups that are associated with the owner. Display a single summary data row for each owner. Display a single data row for each instance that summarized any associated resource data rows. Display a data row for each resource associated with the instance. Logical groups display by default on modes: INSTANCE RESOURCE Logical groups do NOT display on modes: OWNER OWNERRSCE Command syntax parameters control whether logical groups will display: "GROUPS NOGROUPS" Command Syntax ALERTSUM { MODE OWNER } { OWNERRSCE } { INSTANCE } { RESOURCE } { SYSTEM } { MVS } { CICS } < -owners { IMS } { TCP } 10-Oct /354

23 { WEBMQ } { ACTive INACTive } { GROUPS NOGROUPS } { INSTANCE instance >group } { GROUPTYPE grptype } { RESOURCE resource } { NOXSDATA XSDATA } { NOXSYSTEM XSYSTEM } GROUPS Display data rows for defined logical groups. Defined logical groups will be displayed as a separate instance. Logical group entries are not rolled up into the owner entries. Logical groups will be displayed for the following modes: Mode INSTANCE RESOURCE Owner Logical Group Type CICS CICSPLEX IMS IMSID TCP TCPID WEBMQ MQQMGR NOGROUPS Do not display defined logical groups WTO Console Exception Messages When an exception alert within SYSVIEW is triggered based on a defined threshold or state rule, a WTO message can be written to the console and job log. MVS - WTO message format Parameter Contents Max Length 01 Exception type 9 02 Metric subgroup 8 03 Metric name 8 04 Resource 8 05 New metric status 8 06 Metric value V=value 07 Exception warning limit W=warning Oct /354

24 Parameter Contents Max Length 08 Exception problem limit P=problem 09 Exception rule type 8 10 Elapsed time since notification 8 11 ASID 4 12 JES job ID 8 13 'Desc=' 5 14 'description' 'Policy=' 7 16 Policy 8 If the metric is job related, (subgroup = 'JOB') then the parameters ASID and JOBID will contain data from the job being monitored. If the metric is not job related, the parameters ASID and JOBID will contain '*'. WebSphere MQ - WTO message format Parameter Contents Max Length 01 Exception type 9 02 Metric subgroup 8 03 Metric name 8 04 Queue manager 4 05 Resource New metric status 8 07 Metric value V=value 08 Exception warning limit W=warning 09 Exception problem limit P=problem 10 Exception rule type 8 11 Elapsed time since notification 8 12 'Desc=' 5 13 'description' 'Policy=' 7 15 Policy Oct /354

25 IMS - WTO message format Parameter Contents Max Length 01 Exception type 9 02 Metric subgroup 8 03 Metric name 8 04 IMS subsystem ID 4 05 Resource 8 06 New metric status 8 07 Metric value V=value 08 Exception warning limit W=warning 09 Exception problem limit P=problem 10 Exception rule type 8 11 Elapsed time since notification 8 12 'Desc=' 5 13 'description' 'Policy=' 7 15 Policy Oct /354

26 TCP/IP - WTO message format Parameter Contents Max Length 01 Exception type 9 02 Metric subgroup 8 03 Metric name 8 04 TCP/IP jobname of stack 8 05 Resource 8 06 New metric status 8 07 Metric value V=value 08 Exception warning limit W=warning 09 Exception problem limit P=problem 10 Exception rule type 8 11 Elapsed time since notification 8 12 'Desc=' 5 13 'description' 'Policy=' 7 15 Policy Oct /354

27 CICS - WTO message format Parameter Contents Max Length 01 Exception type 8 02 Metric subgroup 8 03 Metric name 8 04 Resource Resource Old metric status 8 07 New metric status 8 08 'V=' 2 09 Metric value 'W=' 2 11 Exception warning limit 8 12 'P=' 2 13 Exception problem limit 8 14 Exception rule type 8 15 Elapsed time since notification 8 16 CICS jobname 8 17 Transaction ID 4 18 Task number 8 19 Terminal ID 8 20 Userid 8 21 'Desc=' 5 22 'description' 'Policy=' 7 24 Policy 8 Modify Threshold, State, and Monitor Definitions SYSVIEW threshold, state and monitor definitions can be dynamically added or modified using on-line commands or via a MODIFY command to the SYSVIEW Main Services address space SYSVQAA. If the modify command is used, the modify needs to be directed to the specific subsystem data collector. 10-Oct /354

28 Update definitions using online commands Command THRESH STATES MONITOR MQTHRESH MQSTATES MQMON IMSTHRSH IMSSTATE IMSMON TCPTHRSH TCPSTATE TCPMON CTHRESH CSTATES Description MVS threshold definitions MVS state definitions MVS monitor definitions WebSphere MQ threshold definitions WebSphere MQ state definitions WebSphere MQ monitor definitions IMS threshold definitions IMS state definitions IMS monitor definitions TCP/IP threshold definitions TCP/IP state definitions TCP/IP monitor definitions CICS threshold definitions CICS state definitions Reload definitions using the MODIFY interface MODIFY SYSVQAA,MODIFY MVSDATA, RELOAD member MODIFY SYSVQAA,MODIFY MQSDATA, RELOAD member MODIFY SYSVQAA,MODIFY IMSDATA, RELOAD member MODIFY SYSVQAA,MODIFY TCPDATA, RELOAD member Reload definitions on all systems using the MODIFY interface ROUTE *ALL,F SYSVQAA,MODIFY taskname,reload member How To Direct SNMP Trap Event Notifications When an exception alert within CA SYSVIEW Performance Management is triggered based on a defined threshold or state rule, multiple actions can be taken. One action is to send an SNMP Trap event notification: SNMP traps are sent using the CA Common Services for z/os Event Notification Facility (ENF). The threshold or state rule TrapDest specifies the name of a logical group that contains a list of IP addresses or names that correspond to entries in the SNMPCNFG parmlib member of ENF. To direct a trap to a specific port: Define the node in the SNMPCNFG parmlib with the specific port. 10-Oct /354

29 If you already have the node specified in your SNMPCNFG parmlib and you do not want to modify its port, then: Define a new node name in your DNS. Add an entry in your parmlib member with the new DNS name and port. Define the new node in your SYSVIEW TrapDest group. Review the following SNMP Trap Fields: Enterprise OID Trap type - 6 (enterprise) Specific type - 1 SNMP Trap OID SNMP MIB - The SYSVIEW MIB contains definitions for SNMP traps only. The following member contains the MIB definition: sysview.cnm4bsam(gsvxmib) MVS SNMP Trap Alert Format Parameter Contents Max Length 01 Message ID - 'CAGSVX01' 8 02 Plex name 8 03 System name 8 04 Subsystem - 'MVS' 8 05 Jobname 8 06 Metric group 8 07 Metric subgroup 8 08 Exception rule type 8 09 Metric name 8 10 Resource Old metric status 8 12 New metric status 8 13 Elapsed time since notification 8 14 Metric value Exception warning limit 8 16 Exception problem limit 8 17 ASID 4 18 JES job ID 8 19 Policy ID 8 20 Description - 'description text' Oct /354

30 If the metric is job related, (subgroup = 'JOB') then the parameters JOBNAME, ASID and JOBID will contain data from the job being monitored. If the metric is not job related, the parameters JOBNAME, ASID and JOBID will contain '*'. CICS SNMP Trap Alert Format Parameter Contents Max Length 01 Message ID - 'CAGSVX02' 8 02 Plex name 8 03 System name 8 04 Subsystem - 'CICS' 4 05 Jobname 8 06 ASID 4 07 JES job ID 8 08 Exception type Possible Values: SYSTEM TRANDYN TRANEND TRANSYS STATE TRANSUMM TIMER 09 Metric group 8 10 Metric subgroup 8 11 Exception rule type 8 12 Metric name 8 13 Resource Resource Old metric status 8 16 New metric status 8 17 Elapsed time since notification 8 18 Metric value Exception warning limit 8 20 Exception problem limit 8 21 Transaction ID 4 22 Task number 8 23 Terminal ID 4 24 Userid 8 25 Policy ID Description - 'description text' Oct /354

31 WebSphere MQ SNMP Trap Alert Format Parameter Contents Max Length 01 Message ID - 'CAGSVX03' 8 02 Plex name 8 03 System name 8 04 Subsystem - 'MQSeries' 8 05 Queue manager 8 06 Metric group 8 07 Metric subgroup 8 08 Exception rule type 8 09 Metric name 8 10 Resource Old metric status 8 12 New metric status 8 13 Elapsed time since notification 8 14 Metric value Exception warning limit 8 16 Exception problem limit 8 17 '*' 4 18 '*' 8 19 Policy ID 8 20 Description - 'description text' 40 IMS SNMP Trap Alert Format Parameter Contents Max Length 01 Message ID - 'CAGSVX04' 8 02 Plex name 8 03 System name 8 04 Subsystem - 'IMS' 8 05 IMS subsystem ID 8 06 Metric group 8 07 Metric subgroup 8 08 Exception rule type 8 09 Metric name 8 10 Resource Old metric status 8 12 New metric status 8 10-Oct /354

32 Parameter Contents Max Length 13 Elapsed time since notification 8 14 Metric value Exception warning limit 8 16 Exception problem limit 8 17 '*' 4 18 '*' 8 19 Policy ID 8 20 Description - 'description text' 40 TCP/IP SNMP Trap Alert Format Parameter Contents Max Length 01 Message ID - 'CAGSVX05' 8 02 Plex name 8 03 System name 8 04 Subsystem - 'TCP' 8 05 TCP/IP jobname of stack 8 06 Metric group 8 07 Metric subgroup 8 08 Exception rule type 8 09 Metric name 8 10 Resource Old metric status 8 12 New metric status 8 13 Elapsed time since notification 8 14 Metric value Exception warning limit 8 16 Exception problem limit 8 17 '*' 4 18 '*' 8 19 Policy ID 8 20 Description - 'description text' 40 Write Log Messages to a DD name When an exception alert within SYSVIEW is triggered based on a defined threshold or state rule, a log message can be written to a specific ddname. 10-Oct /354

33 MVS - Log message format Jobname - SYSVIEW Main Services address space DDname - GSVXMVS Parameter Contents Max Length 01 Date - yyyy/mm/dd Time - hh:mm:ss 8 03 Metric group 8 04 Metric subgroup 8 05 Metric name 8 06 Resource Resource Old metric status 8 09 New metric status 8 10 Elapsed time since notification 8 11 Metric value Exception warning limit 8 13 Exception problem limit 8 14 Exception rule type ASID 4 16 JES job ID 8 17 Trap sent indicator 6 18 Policy 8 19 Description 40 If the metric is job related, (subgroup = 'JOB') then the parameters ASID and JOBID will contain data from the job being monitored. If the metric is not job related, the parameters ASID and JOBID will contain '*'. WebSphere MQ - Log message format Jobname - SYSVIEW Main Services address space DDname - GSVXMQS Parameter Contents Max Length 01 Date - yyyy/mm/dd Time - hh:mm:ss 8 03 Metric group 8 04 Metric subgroup 8 05 Metric name 8 06 Queue manager 4 07 Resource Oct /354

34 Parameter Contents Max Length 08 Old metric status 8 09 New metric status 8 10 Elapsed time since notification 8 11 Metric value Exception warning limit 8 13 Exception problem limit 8 14 Exception rule type 8 15 Trap sent indicator 6 16 Policy 8 17 Description 40 IMS - Log message format Jobname - SYSVIEW Main Services address space DDname - GSVXIMS Parameter Contents Max Length 01 Date - yyyy/mm/dd Time - hh:mm:ss 8 03 Metric group 8 04 Metric subgroup 8 05 Metric name 8 06 IMS subsystem ID 4 07 Resource 8 08 Old metric status 8 09 New metric status 8 10 Elapsed time since notification 8 11 Metric value Exception warning limit 8 13 Exception problem limit 8 14 Exception rule type 8 15 Trap sent indicator 6 16 Policy 8 17 Description 40 TCP/IP - Log message format Jobname - SYSVIEW Main Services address space DDname - GSVXTCP 10-Oct /354

35 Parameter Contents Max Length 01 Date - yyyy/mm/dd Time - hh:mm:ss 8 03 Metric group 8 04 Metric subgroup 8 05 Metric name 8 06 TCP/IP jobname of stack 8 07 Resource 8 08 Old metric status 8 09 New metric status 8 10 Elapsed time since notification 8 11 Metric value Exception warning limit 8 13 Exception problem limit 8 14 Exception rule type 8 15 Trap sent indicator 6 16 Policy 8 17 Description 40 CICS - Log message format Jobname - CICS region DDname - GSVCXLOG Parameter Contents Max Length 01 Date - yyyy/mm/dd Time - hh:mm:ss 8 03 Exception type 8 04 Metric group 8 05 Metric name 8 06 Resource Resource Old metric status 8 09 New metric status 8 10 Metric value Exception warning limit 8 12 Exception problem limit 8 13 Exception rule type 8 14 Elapsed time since notification 8 10-Oct /354

36 Parameter Contents Max Length 15 CICS jobname 8 16 Transaction ID 4 17 Task number 8 18 Terminal ID 4 19 Userid 8 20 Policy Description 40 Execute REXX IMOD on an Exception When an exception alert within SYSVIEW is triggered based on a defined threshold or state rule, a REXX IMOD can be executed. MVS - Parameters passed to the REXX IMOD Parameter Contents Max Length 01 System name 8 02 Subsystem - 'MVS' 8 03 Jobname 8 04 ASID 4 05 JES job ID 8 06 Metric group 8 07 Metric subgroup 8 08 Exception rule type 8 09 Metric name 8 10 Resource Resource Old metric status 8 13 New metric status 8 14 Elapsed time since notification 8 15 Metric value Exception warning limit 8 17 Exception problem limit 8 18 Description - 'description text' 40 If the metric is job related, (subgroup = 'JOB') then the parameters JOBNAME, ASID and JOBID will contain data from the job being monitored. If the metric is not job related, the parameters JOBNAME, ASID and JOBID will contain '*'. 10-Oct /354

37 WebSphere MQ - Parameters passed to the REXX IMOD Parameter Contents Max Length 01 System name 8 02 Subsystem - 'MQSeries' 8 03 Queus Manager 8 04 '*' 4 05 '*' 8 06 Metric group 8 07 Metric subgroup 8 08 Exception rule type 8 09 Metric name 8 10 Resource Resource Old metric status 8 13 New metric status 8 14 Elapsed time since notification 8 15 Metric value Exception warning limit 8 17 Exception problem limit 8 18 Description - 'description text' 40 IMS - Parameters passed to the REXX IMOD Parameter Contents Max Length 01 System name 8 02 Subsystem - 'IMS' 8 03 IMS subsystem ID 8 04 '*' 4 05 '*' 8 06 Metric group 8 07 Metric subgroup 8 08 Exception rule type 8 09 Metric name 8 10 Resource Resource Old metric status 8 13 New metric status 8 14 Elapsed time since notification 8 10-Oct /354

38 Parameter Contents Max Length 15 Metric value Exception warning limit 8 17 Exception problem limit 8 18 Description - 'description text' 40 TCP/IP - Parameters passed to the REXX IMOD Parameter Contents Max Length 01 System name 8 02 Subsystem - 'TCP' 8 03 TCP/IP jobname of stack 8 04 '*' 4 05 '*' 8 06 Metric group 8 07 Metric subgroup 8 08 Exception rule type 8 09 Metric name 8 10 Resource Resource Old metric status 8 13 New metric status 8 14 Elapsed time since notification 8 15 Metric value Exception warning limit 8 17 Exception problem limit 8 18 Description - 'description text' 40 CICS - Parameters passed to the REXX IMOD Parameter Contents Max Length 01 System name 8 02 Subsystem - 'CICS' 4 03 Jobname 8 04 ASID 4 05 JES job ID 8 06 Exception type Possible Values: SYSTEM TRANDYN 8 10-Oct /354

39 Parameter Contents Max Length TRANEND TRANSYS STATE TRANSUMM TIMER 07 Metric group 8 08 Metric subgroup 8 09 Exception rule type 8 10 Metric name 8 11 Resource Resource Old metric status 8 14 New metric status 8 15 Elapsed time since notification 8 16 Metric value Exception warning limit 8 18 Exception problem limit 8 19 Transaction ID 4 20 Task number 8 21 Terminal ID 4 22 Userid 8 23 Description - 'description text' 40 Event Capture on an Exception When an exception alert within SYSVIEW is triggered based on a defined threshold or state rule, an Event Capture can be requested. MVS - Parameters passed to the Event Capture process Parameter Contents Max Length 01 System name 8 02 Subsystem - 'MVS' 8 03 Jobname 8 04 ASID 4 05 JES job ID 8 06 Metric group 8 07 Metric subgroup 8 10-Oct /354

40 Parameter Contents Max Length 08 Exception rule type 8 09 Metric name 8 10 Resource Resource Old metric status 8 13 New metric status 8 14 Elapsed time since notification 8 15 Metric value Exception warning limit 8 17 Exception problem limit 8 18 Description - 'description text' 40 If the metric is job related, (subgroup = 'JOB') then the parameters JOBNAME, ASID and JOBID will contain data from the job being monitored. If the metric is not job related, the parameters JOBNAME, ASID and JOBID will contain '*'. WebSphere MQ - Parameters passed to the Event Capture process Parameter Contents Max Length 01 System name 8 02 Subsystem - 'MQSeries' 8 03 Queue Manager 8 04 '*' 4 05 '*' 8 06 Metric group 8 07 Metric subgroup 8 08 Exception rule type 8 09 Metric name 8 10 Resource Resource Old metric status 8 13 New metric status 8 14 Elapsed time since notification 8 15 Metric value Exception warning limit 8 17 Exception problem limit 8 18 Description - 'description text' 40 IMS - Parameters passed to the Event Capture process 10-Oct /354

41 Parameter Contents Max Length 01 System name 8 02 Subsystem - 'IMS' 8 03 IMS subsystem ID 8 04 '*' 4 05 '*' 8 06 Metric group 8 07 Metric subgroup 8 08 Exception rule type 8 09 Metric name 8 10 Resource Resource Old metric status 8 13 New metric status 8 14 Elapsed time since notification 8 15 Metric value Exception warning limit 8 17 Exception problem limit 8 18 Description - 'description text' 40 TCP/IP - Parameters passed to the Event Capture process Parameter Contents Max Length 01 System name 8 02 Subsystem - 'TCP' 8 03 TCP/IP jobname of stack 8 04 '*' 4 05 '*' 8 06 Metric group 8 07 Metric subgroup 8 08 Exception rule type 8 09 Metric name 8 10 Resource Resource Old metric status 8 13 New metric status 8 14 Elapsed time since notification 8 15 Metric value Oct /354

42 Parameter Contents Max Length 16 Exception warning limit 8 17 Exception problem limit 8 18 Description - 'description text' 40 CICS - Parameters passed to the Event Capture process Parameter Contents Max Length 01 System name 8 02 Subsystem - 'CICS' 4 03 Jobname 8 04 ASID 4 05 JES job ID 8 06 Exception type Possible Values: SYSTEM TRANDYN TRANEND TRANSYS STATE TRANSUMM TIMER 07 Metric group 8 08 Metric subgroup 8 09 Exception rule type 8 10 Metric name 8 11 Resource Resource Old metric status 8 14 New metric status 8 15 Elapsed time since notification 8 16 Metric value Exception warning limit 8 18 Exception problem limit 8 19 Transaction ID 4 20 Task number 8 21 Terminal ID 4 22 Userid 8 23 Description - 'description text' Oct /354

43 How To Articles This section contains information and tips about using CA SYSVIEW Performance Management. How to Automatically Update Screen Displays (see page 43) How To Cancel an Address Space or TCB (see page 44) How to Compile a MIB for MIB Browsing Commands (see page 45) How to Create a Predefined PLOT Member (see page 46) How to Create a List of Predefined PLOT Members (see page 47) How Implicit Commands Work (see page 49) How Threshold and State Definitions Work (see page 50) How to Define ISPF or TSO Applications (see page 55) How to Display Cross System Data from Multiple Systems (see page 55) How To Dump Storage Using the Point-and-Shoot Method (see page 56) How to Enter Command Parameters with Lowercase or Embedded Blanks (see page 56) How to Enter Long Commands (see page 57) How to Find Abended IMS Transactions (see page 58) How to Find IMS Threshold Exceptions (see page 58) How to Find Multiple Occurrences of a Module (see page 59) How to Increase the Command Input Area (see page 59) How to Recall or Retrieve a Previous Command (see page 61) How to Scroll Command Displays (see page 61) How to View Available Line Commands (see page 63) How to Verify APF Authorization for a Data Set (see page 66) How to Subset a Display Using the SELECT Command (see page 67) How to Find Help for a Specific Topic (FINDHELP) (see page 70) How to Automatically Update Screen Displays You can use the UPDATE command to specify: An automatic refresh interval for a display How long to stay in the automatic refresh mode Note: The UPDATE command is not supported in the CICS and batch interfaces. Command Syntax: UPDATE <interval><,duration><,command><off> 10-Oct /354

44 Notes interval Sets the refresh interval, in seconds, for the current display. The default is specified in your security group, and the interval cannot be set below the default. Specifying 0 (zero) seconds turns the update facility off. duration Sets the duration, in minutes, of automatic refresh mode. The default is specified in your security group, and the duration cannot be set above the default. Specifying 0 (zero) turns on automatic update mode indefinitely. Automatic update mode remains in effect until the duration value expires or you turn off update mode. command A scrolling or function command. If specified, then the command is executed at the update interval. If not specified, then a null response (Enter key) is simulated at the update interval. OFF Turns the update facility off. If you issue UPDATE within the TSO, or VTAM interface, then only the command and parameter lines accept input. If you issue UPDATE within the ISPF or ROSCOE/ETSO interface, then input is not accepted; the keyboard is locked. To turn off UPDATE on an SNA terminal press the ATTN key. To turn off UPDATE on a non-sna terminal, press Reset and then PA1. If you are in the VTAM interface on an SNA terminal and you enter data on the command or parameter line, then UPDATE is disabled until you press ENTER. To turn off UPDATE from the VTAM interface, press the PA1 key. The ATTN key is not supported in the VTAM interface. Issuing the UP, DOWN, TOP, or BOTTOM commands while UPDATE is turned on turns UPDATE off. UPDATE mode is turned off if a message is displayed that is equal to or greater than the level specified by the SET option UPDENDMSGLVL. Active UPDATE mode can be indicated by either highlighting the time field in the screen title line or by displaying the UPDATE keyword in the statusline. The highlighting of the screen title time field is controlled by the setting of the SET HLUPDATETIME keyword. The display of the status line is controlled by the setting of the SET STATUSLINE keyword. Follow this hyperlink for more status line display information. How To Cancel an Address Space or TCB MVS rules are enforced when you cancel an address space. The following command displays support canceling an address space: ACTIVITY - System activity ASLIST - Address space list 10-Oct /354

45 Cancel an address space: Issue a CANCEL command for an address space prior to issuing a FORCE command. A KILL command can be issued at any time. However, first use the CANCEL and FORCE commands before using the KILL command. ASCANCEL command - Cancel an address space ASFORCE command - Force an address space ASKILL command - Kill an address space CANCEL command - Uses the MVS CANCEL command. FORCE command - Uses the MVS FORCE command. Requires the CANCEL command to be issued first. KILL command - Uses the CALLRTM service to terminate memory with a completion code of x'a22'. Cancel a TCB (task) within an address space: You can cancel any TCB within an address space through the use of the CANCEL and CDUMP line commands on the TASK display. This also uses CALLRTM to cancel the TCB with completion codes of x'222' and x'122' respectively. The following command display supports canceling a TCB: TASK - Task structure How to Compile a MIB for MIB Browsing Commands Compiling a MIB for use with the set of MIB browsing commands Use the MIB browsing commands to communicate with any SNMP compatible device or product. To communicate with the desired device or product: The definitions supplied by a MIB are required The MIB must be compiled The output from the MIB compiler must be saved in the sysview.cnm4bmib data set The compiled definitions are used as input by the set of MIB browsing commands. A sample job to compile a user supplied MIB can be found in the data set sysview.cnm4bsam (MIBCOMP). 10-Oct /354

46 How to Create a Predefined PLOT Member The PLOT command allows for up to eight metrics to display. The PLOT command supports many parameters and values. As an option, the parameters and values that can be specified on the PLOT command can be saved in a predefined PLOT member. The complexity of specifying many parameters and values on the PLOT command itself is reduced. Use predefined plot members to: Define commonly used plots Combine a PLOT with multiple metrics Example: PLOT command syntax using a predefined member: PLOT USING member Predefined PLOTLIB Member Examples: *=====================================================================* * Predefined Plot Member * *=====================================================================* TITLE 'System Resource Utilization' *=====================================================================* * Source Variable Resource Resource PLOT1A MVS CPU% PLOT2A MVS SYSIOR PLOT3A MVS PAGERATE PLOT4A MVS STGUICA TITLE 'New Plot Member' JOBASID LEGEND * Source Variable Resource Resource Scale PLOT1A MVS JOBCPU% &jobname PLOT1B PLOT2A MVS CPU% * * 100 PLOT2B PLOT3A PLOT3B PLOT4A PLOT4B Predefined PLOTLIB Definition Syntax Keywords and Options: Keywords Descriptions * The comment line, This keyword must be in column one. TITLE LEGEND NOLEGEN D Defines the title to display with the plot, Enclose the title description in quotes. Displays the LEGEND at the top of the screen, Does not display the LEGEND. JOBNAME Issue a memory switch command to the specified JOBNAME. ASID Issue a memory switch command to the specified ASID. 10-Oct /354

47 Keywords Descriptions JOBASID JOBASIDC ICS Displays the current jobname and ASID in the information section. Displays the current jobname, ASID, and CICS. NOJOBASI Does not display the current jobname, ASID, and CICS version in the information section. D DEVICE NODEVIC E DSN NODSN END Plot Definitions: Displays the current device number, volser, and unit in the information section. Does not display the current device number, volser, and unit in the information section. Displays the data set and member name of the PLOT definitions member in the information section. Does not display the data set and member name of the PLOT definitions member in the information section. Logical end of file. Keyword Description PLOTnA Defines the target jobname, variable, and resource. n = 1, 2, 3, or 4 The A variable is the default plot if only one variable within a quadrant is being used. The A plot uses the left vertical scale. PLOTnB Defines the target jobname, variable, and resource. n = 1, 2, 3, or 4 The B variable is typically used if two plots are desired within a plot quadrant. The B plot uses the right vertical scale. SCALEnA Defines the maximum vertical scale value for plot n variable A. n = 1,2,3 or 4 SCALEnB Defines the maximum vertical scale value for plot n variable B. n = 1,2,3 or 4 Sample Variable Substitution &JOBNAME - The current jobname &ASID - The current ASID &SYSNAME - The system name &USERID - The userid &VOLUME - The current DASD volume How to Create a List of Predefined PLOT Members Defining a PLOTLIST member 10-Oct /354

48 The PLOTLIST command displays a list of predefined plot definition members. The PLOTLIST command can be entered specifying a member name. The member name specified is a member that contains a list of predefined plot definition members. PLOTLIST command syntax examples: PLOTLIST member dsname( member) The PLOT command allows for up to 8 metrics to be displayed. The PLOT command supports many parameters and values. As an option, the parameters and values that can be specified on the PLOT command can be saved in a predefined PLOT member. This reduces the complexity of specifying many parameters and values on the PLOT command itself. Predefined plot members can be used to: Define commonly used plots Combine a PLOT with multiple metrics PLOT command syntax example using a predefined member: PLOT USING member PLOTLIST Example: TITLE 'Sample Plotlist Member' DSN JOBASIDCICS PLOTDASD TEST Test plot member for DASD PLOTJOBS TEST Test plot member for JOBS PLOTSYS TEST Test plot member for MVS system information END PLOTLIST Definition Syntax: Keywords and Options Description * Comment line. TITLE NODSN DSN JOBASID JOBASIDCICS JOBASIDIMS JOBASIDMQS NOJOBASID Defines the title to be displayed with the PLOTLIST. Enclose the title description in quotes. Title limit = 32 characters Does not display the data set name in the information section when displaying the PLOTLIST. Displays the data set name in the information section when displaying the PLOTLIST. Displays the current jobname and ASID in the information section. Displays the current jobname, ASID,and CICS version in the information section. Displays the current jobname, ASID,and IMS version in the information section. Displays the current jobname, ASID, and MQSeries version in the information section. 10-Oct /354

49 Keywords and Options DEVICE NODEVICE INTERNAL Description Does not display the current jobname, ASID, and CICS version in the information section. Displays the current device number, volser, and unit in the information section. Does not display the current device number, volser, and unit in the information section. Equivalent to the following: NODSN NODEVICE NOJOBASID Definition Entry: Column Description 01:08 Plot member name. 1 to 8 characters left justified and blank padded. 10:17 Class name. 1 to 8 characters left justified and blank padded. 19:73 Plot list description. How Implicit Commands Work CA SYSVIEW Performance Management supports issuing SET, USERCMD, INVOKE, ISPF, and TSO commands as extensions to the normal set of CA SYSVIEW Performance Management commands. The SYSVIEW profile contains options that allow the user to issue these command strings without the "SET", "USERCMD", "INVOKE", "ISPF" or "TSO" command keyword. This is referred to as the implicit command options. When a user enters a command in the primary command area, the search order is as follows: Standard internally defined SYSVIEW commands Command synonyms defined via the user profile SET keywords If the user profile option IMPLICTSET is set to YES External USER Command Definitions Source: user.parmlib(usercmds) The user profile option IMPLICITUCMD must be set to YES 5. External SYSTEM or SITE Command Definitions Source: sysview.cnm4bprm(usercmds) The user profile option IMPLICITUCMD must be set to YES 10-Oct /354

50 INVOKE keywords If the user profile option IMPLICTINVK is set to YES ISPF commands If the user profile option IMPLICTISPF is set to YES TSO commands If the user profile option IMPLICTTSO is set to YES Example: How the implicit SET command option operates With implicit SET off: SET COLOR ON With implicit SET on: COLOR ON -or- COLOR The following help topics provide more information on a specific implicit command option: IMPLICITSET - Implicit SET command option IMPLICITUCMD - Implicit USERCMD command option IMPLICITINVK - Implicit INVOKE command option IMPLICITISPF - Implicit ISPF command option IMPLICITTSO - Implicit TSO command option How Threshold and State Definitions Work Threshold Rule Types (see page 51) State Rule Types (see page 54) Several alert mechanisms or actions are available for alerting purposes. You can set threshold or state definitions to raise an exception or an alert when resource usage is outside a defined range or the resource is not in the desired state. Thresholds and states are different: Threshold definitions assign numeric warning and problem limit values to a metric or resource. Thresholds are always numeric. State definitions assign a status to a specific condition of a metric or resource. States always have character values. Some examples of states include: ACTIVE 10-Oct /354

51 INACTIVE ONLINE OFFLINE Threshold Rule Types Threshold rule types define the algorithm that is used to determine when a collected metric has exceeded the allowable resource usage. Multiple rule types or checks can be defined for a single metric: UPPER LOWER CHANGE Rule type: UPPER An UPPER limit rule type defines the upper warning and problem limit values that a collected metric can use. If the metric value exceeds the warning or problem limit values, defined actions can be triggered that are associated with the definition. Algorithm: IF value >= problemlimit THEN status = PROBLEM ELSE IF value >= warninglimit THEN status = WARNING ELSE status = NORMAL END END Example: The CPU percent busy is 93%. Defined limit values: Warning - 80% Problem - 90% Using the algorithm above, the status that is assigned to the metric is PROBLEM. The value (93%) is greater than the defined problem limit value of 90%. Rule type: LOWER A LOWER limit rule type defines the lower warning and problem limit values that a collected metric can use. If the metric value falls below the warning or problem limit values, defined actions can be triggered that are associated with the definition. 10-Oct /354

52 Algorithm: IF value <= problemlimit THEN status = PROBLEM ELSE IF value <= warninglimit THEN status = WARNING ELSE status = NORMAL END END Example: The amount of free Common Storage is 128K Defined limit values: Warning - 256K Problem - 64K Using the algorithm above, the status that is assigned to the metric is WARNING. The value (128K) is less than the defined warning limit value (256K), but is not less than the problem limit (64K). Rule type: CHANGE Workload and resource consumption can be very unpredictable. For this reason, creating a "baseline" of expected values for resource consumption can be very difficult. Creating a baseline value for a metric is simply the expected value of resource consumption for a known time period. Workload must be predictable or must be a recurring event for the baselining approach to work. Workload is not as predictable as it was in the past, largely due to workload arriving from internet and global applications.since workload is unpredictable, a different or smarter detection method for analyzing exceptions is needed. A CHANGE limit rule type defines the amount that a metric can change. This change can be in an upward or downward direction. The CHANGE rule does not require specific values for a metric to be specified. The change is measured in terms of the number of standard deviations from the historical average. If the change in the metric exceeds the defined warning or problem limit values, defined actions can be triggered that are associated with the definition. The change in the metric value can be an upward or downward change. Within the CHANGE rule type definition, the warning and problem limit value is defined as the number of standard deviations that must be exceeded for the metric to be assigned the status of WARNING or PROBLEM. Generally speaking, we assume that if a data value is within one standard deviation of the mean, its status is considered NORMAL. Standard Deviation (stddev) Standard deviation is a measure of the variability or distribution of a set of data values. If a set of data has a low standard deviation, this indicates that all the data values are very close to the average or mean of the set. A high standard deviation value indicates that the data is spread out over a wide range of data values. 10-Oct /354

53 Mean (mean) The average value for the entire set of data. Duration Average (duravg) The average value for the most current "n" intervals of data where "n" is the interval or duration in minutes. Duration Change (durchg) The difference between the duration average and the mean. durchg = duravg - mean Warning Limit Value (warninglimit) The actual warning limit value is calculated dynamically during the threshold checking or evaluation process. The warning limit value must be calculated dynamically because it is based on the mean and standard deviation of the data. warninglimit = warning * stddev Problem Limit Value (problemlimit) The actual problem limit value is calculated dynamically during the threshold checking or evaluation process. The problem limit value must be calculated dynamically because it is based on the mean and standard deviation of the data. problemlimit = problem * stddev Algorithm: IF durchg >= problemlimit THEN status = PROBLEM ELSE IF durchg >= warninglimit THEN status = WARNING ELSE status = NORMAL END END Example: Metric: CPU percent busy The 60 minute mean or average: 40% The standard deviation: 12 The duration average: 55 The duration change: 15 (duravg - mean) The duration change stddev: (durchg / stddev) A simple analysis of the mean and standard deviation indicates that the CPU percent busy average has been typically in the range of 28% to 52%. -1 stddev mean +1 stddev Oct /354

54 28% 40% 52% Defined limit values (number of standard deviations): Warning Problem The warning and problem limit values that are used during the check process is calculated dynamically as follows: warninglimit = warning * stddev 12 = * 12 problemlimit = problem * stddev 24 = * 12 The defined limit values have the following meaning: If the "duration change value (15)" is greater than 24, the assigned status is PROBLEM. If the "duration change value (15)" is greater than 12, the assigned status is WARNING. Using the algorithm above the status assigned to the metric is WARNING. The duration change value (15) is greater than the warning limit value (12), but is less than the problem limit value (24). State Rule Types States do not have multiple rule types. State exception processing assigns a status to the current state of a metric or resource. Example: The current state of a CPU process is OFFLINE. DEFINE CPUSTAT RSCE = STATE ONLINE STATUS NORMAL DEFINE CPUSTAT RSCE = STATE OFFLINE STATUS WARNING DEFINE CPUSTAT RSCE = STATE PARKED STATUS HIGH Based on the example definitions, the status WARNING is assigned to a CPU in the state OFFLINE. Notifications and actions Multiple methods of notification and actions can be taken when an exception occurs: Write a message to the log Write a message to the console Send an SNMP alert trap Send an event notification to CA OPS/MVS Request an Event Capture 10-Oct /354

55 Execute a pre-defined REXX EXEC or IMOD Cancel a CICS transaction How to Define ISPF or TSO Applications You can define any ISPF or TSO application to CA SYSVIEW Performance Management as an externally callable program. This allows CA SYSVIEW Performance Management to link to commonly used applications or products. Externally callable applications or products are defined in the parameter library member INVOKE. The format of the data: Columns Description INVOKE command keyword. 1 to 8 characters left justified and blank padded. 10 The minimum length required to match the INVOKE keyword. 1 numeric digit from 0 to 8 or blank. A value of blank, 0, or 8 all imply that the full keyword must be specified ISPF interface parmlib member name TSO interface parmlib member name Product description. Example parmlib member INVOKE: *Command T ISPF-Mbr TSO-Mbr Description * QUICKREF 5 XISPQWRF MVS/Quick-Ref from Chicago-Soft How to Display Cross System Data from Multiple Systems Selected product commands can display data that is gathered from remote systems. To gather data from a remote system, there must be a product data server active on the remote system and the system must be reachable through the CCI communication network. Review the following SET keywords that are used to control the display of cross system data. See the SET keyword help for more information. SET Keywords XSData XSDUmmyinput XSGroup Description Controls the gathering and displaying of xsystem data. Controls the display of dummy input fields in xsystem data. Controls which system xsystem data is gathered from. 10-Oct /354

56 SET Keywords XSHome XSLimit XSMsglvl XSRemdup XSStatusline XSUseridsave Description Controls the display of home system data in xsystem data. Controls the amount of data that is returned from a remote system. Controls the level of xsystem error message displayed. Controls the removal of duplicate data from the display. Controls the display of the xsystem status info line. Controls the saving of authenticated user IDs. An easier way to control the xsystem data display for a command is to use the XSCMDS command display. How To Dump Storage Using the Point-and-Shoot Method The DUMP command displays the contents of virtual and real storage for any job in the system, and virtual storage residing in data spaces. When you enter DUMP without any parameters and the cursor is positioned in the body lines of any display, then the data pointed to by the cursor is used as the address. All address fields are defined as dummy input fields, which enables you to TAB to the address field. To increase your efficiency, assign a PF key to invoke the LINK DUMP command. Follow these steps SET PF n DEFAULT ALL Ensure the selected PF key is not in use by any command. SET PF n 'LINK DUMP' GENERAL Sets the selected PF key to save the current environment and LINK to the DUMP command from all screens. SET PF n DUMP DUMP Sets the selected PF key to DUMP for use from the DUMP screen. How to Enter Command Parameters with Lowercase or Embedded Blanks Some commands allow or require parameter strings to be entered with the command. These strings may need to be entered in lowercase format or the string can contain embedded blanks. 10-Oct /354

57 Most commands automatically uppercase any included parameter strings. A blank character is interpreted as a separator during command parsing. To enter a string that is case sensitive, specify the string using one of the following examples: C'string' C'AbCdeFg' C'Upper and LowerCase String' To enter a string that contains embedded blanks, specify the string using one of the following examples: 'STRING WITH BLANKS' 'STRING WILL BE UPPERCASED' Using only the character delimiter "'" does not ensure case sensitivity. How to Enter Long Commands You begin entering a command on the command line and discover that your command is longer than the command line. You can continue entering long command strings using one of the following methods: Use the command: LONGCMD Use the following continuation characters: Use a hyphen (-) or plus (+) continuation character as the last nonblank character. If the continuation character is a hyphen, then all leading blanks on the next command are NOT ignored. If the continuation character is a plus, then all leading blanks on the next command ARE ignored. The total command length must not exceed 256 characters. When a command is entered that ends with a continuation character, you receive the following message: GSVX515A Command input pending - Continue and Enter or hit any PFK to clear The current command input string ended with the command continuation character. Any data entered has been added to the pending command string. Continue to enter the rest of the command or use any PF key to discard the entire command. 10-Oct /354

58 How to Find Abended IMS Transactions Abended IMS transactions are logged in the IMS Transaction log stream. Follow these steps: 1. Enter the command IMSTLOG FILTER. 2. Enter the equal symbol (=), or whatever your variable length masking character is, in the CCODE field of the resulting panel, and then press PF3. The resulting display includes all abended IMS transactions contained in the current log stream display window, where the window size is determined by the start date/time, period, lines, limit, and cushion settings. Alerts for abended IMS transactions can be generated by setting up a threshold definition using variable IMTRABND from the IMSTHRSH command. Or, by coding a threshold definition in the IMSTHRSH PARMLIB member if you are doing cold starts of IMSDATA from the SYSVIEW PARMLIB member. The sample IMSTHRSH display shows a generic IMTRABND definition that matches for all transactions and all IMS subsystems: Abended IMS Transaction Alerts How to Find IMS Threshold Exceptions IMS threshold exceptions are logged in the exception log stream. You need to look at exceptions for a specific IMS subsystem. Follow these steps 1. Issue the IMSLIST command. The IMS Control Regions display. 2. Enter the XLOG line command on the row containing the IMS ID you are interested in: Cmd Jobname Status ID IMS1CTLR ACTIVE IMS1 XLOG IMS2CTLR ACTIVE IMS2 The resulting display contains the exception log summary data for the IMS ID selected using your default XLOG options for LINES, LIMIT, PERIOD, and so on. To modify your default options, see the HELP for the XLOG command. 10-Oct /354