D20R2-06/99 ...a component of the PerformanceWorks for MVS and OS/390 solution suite Features include the NaviGate communications interface System Administrator’s Guide Version 2.
The Monitor for MVS Version 2.0 – a component of the PerformanceWorks for MVS and OS/390 solution suite. Features include the NaviGate communications interface. System Administrator’s Guide This manual applies to The Monitor for MVS (TMON for MVS), a proprietary software product of Landmark Systems Corporation. In North America, Landmark markets and supports TMON for MVS. Internationally, TMON for MVS is marketed and supported by a network of software marketing firms.
Contents Using this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Organization of this Guide Notational Conventions . . Related Documentation . . Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii iii iv vi Chapter 1: Installation Verification Procedure . . . . . . . . . . . .
Contents ii
Using this Guide The Monitor for MVS System Administrator’s Guide includes information on the TMON for MVS installation verification procedure as well as support and maintenance procedures. It also includes information on security, the TMON for MVS Performance Database, NaviGate, and the distributed sample library. The audience for this guide includes both technicians and managers in systems, programming, capacity planning, operations, and security. A basic understanding of MVS is assumed.
Related Documentation Using this Guide Notation Description ’=,()+-*/ These special characters punctuate commands and command options. The characters must be entered exactly as shown. {} Braces surround required command parameters. [] Brackets surround command options. | Vertical bars separate command options. Choose one option from the list. ➥ An arrow identifies a cursor-selectable field or line.
Using this Guide Related Documentation • The Monitor for MVS Release Guide, which familiarizes TMON for MVS users with the features in the product. • PerformanceWorks for MVS and OS/390 Installation Guide, which includes everything you need to know to install PerformanceWorks for MVS and OS/390. It describes the installation procedures designed to enable you to get PerformanceWorks up and running as quickly and smoothly as possible.
Comments Using this Guide Comments If you find an error or have any suggestions on how this publication can better meet your needs, either send an e-mail to Customer Services at its@landmark.com or call them at 1-800-775-LMRK (5675). When reporting a documentation error, include the name of the publication, chapter number, section name, and a detailed description of the error.
Chapter 1: Installation Verification Procedure After you have successfully installed TMON for MVS, as described in PerformanceWorks for MVS and OS/390 Installation Guide, follow the installation verification procedure (IVP) documented in this chapter to ensure the base TMON for MVS product is properly installed and functioning in your environment. IVP Checklist The following checklist indicates the TMON for MVS components you will verify during the IVP.
IVP Steps Chapter 1: Installation Verification Procedure ◊ Enter the option number in the SELECTION field. ◊ Cursor-select the option number. ◊ Enter =n, where “n” is the option number. 2. Verify the Activity Monitor. a. Select Option 1, Activity Monitor, from the Primary Menu to display the Activity Monitor Menu. b. Select Option 1, System Activity, to display the System Activity Monitor Menu. c. Select Option 1, CPU Activity Display, to display the CPU Activity Display screen.
Chapter 1: Installation Verification Procedure IVP Steps o. Select Option 5, Common Storage Summary, to display the Common Storage Summary screen. It shows information about the allocation and use of common storage areas. p. Press END or the PF3 key three times to return to the Activity Monitor Menu. q. Select Option 5, Performance Parameters, to display the Performance Parameters Menu. r. Select Option 2, Logical Swap Constants, to display the Logical Swap Constants screen.
IVP Steps Chapter 1: Installation Verification Procedure b. Cursor-select the CPU BUSY field to display the CPU History Activity Menu. c. Enter MAINMENU or = on the command line to return to the Primary Menu. 6. Verify Supertrace. a. Select Option 5, Supertrace, from the Primary Menu to display the Supertrace Menu. b. Select Option 4, System Memory Profile, to display the System Memory Profile screen. It shows information on storage usage by address space during the last interval. c.
Chapter 1: Installation Verification Procedure IVP Steps “TMV”). Your site-specified SLU APPLID PREFIX remains on the screen. d. If the applids defining other Landmark PerformanceWorks MVS products have been modified at your site, select the appropriate line, overtype the applid, and cursor-select ADD. You will receive the following message.
IVP Steps Chapter 1: Installation Verification Procedure k. Select Option 1, File/DB Activity, to display the TMON for CICS File/DB Activity Selection Menu. l. Tab to the SUMMARIZE BY field, overtype the “1” with a “2” and press ENTER. The TMON for CICS File/DB Activity screen is displayed. m. Cursor-select any active volume listed in the VOLSER column to display the Device Detail Selection Menu. The following message appears on the screen. TMVS18879I - I/O PROFILE SUCCESSFULLY STARTED Press ENTER.
Chapter 1: Installation Verification Procedure IVP Steps e. Select Option 4, Active Job Summary, to display the TMON for MVS Job Execution Monitor screen. f. Press the PF3 key to display the TMON for MVS Primary Menu. g. Press the PF3 key to display the TMON for DB2 Primary Menu. h. Press the PF3 key to display the TMON for MVS Job Execution Monitor screen.
Chapter 1: Installation Verification Procedure 1-8
Chapter 2: Security Definitions You can secure access to your Landmark PerformanceWorks MVS product and its individual functions using three different methods: External Security, User Exit Security, and Internal Security. You also can choose not to secure product functions at all. Use the Security Definitions Menu to select the particular type of security you want.
How Product Security Works Chapter 2: Security Definitions following table identifies the sample library member you should use for each Landmark PerformanceWorks MVS product. Member Sample Library TCECRS TMON for CICS/ESA TMON8CRS TMON for CICS/MVS TDBCRS TMON for DB2 TDCCRS TMON for DBCTL TMQCRS TMON for MQSeries TMVRSTOR TMON for MVS How Product Security Works This section describes how product security components interact. Figure 2-1 depicts the interaction of the security components.
Chapter 2: Security Definitions How Product Security Works When a user tries to use a secured function, a security authorization call is made to verify that the user has the necessary security clearance. The following information is used in the security check: • User ID • Password (for a sign-on attempt only) • Function ID • Access, or authorization, level (NONE, READ, UPDT, CNTL, or ALTR) of the user ID for the function. Access levels are described in “Detail Profile Definition,” later in this chapter.
Tracing Security Problems Chapter 2: Security Definitions Access level: READ Primary resource: DEV* and TEST* Secondary resource: None Tracing Security Problems Regardless of which type of security you choose to implement (External, Internal, or User Exit), you may need to trace security processing and resolve a security problem. Landmark provides a trace facility for Landmark security processing.
Chapter 2: Security Definitions Using External Security use External Security for access to product functions, you also must use External Security for logon access. If you want to use External Security for logon and Internal or User Exit Security for functions, you can bypass the RACF, CA-TOP SECRET, and CA-ACF2 instructions we supply. Read “External Security Simplified Sign-On,” later in this section.
Using External Security Chapter 2: Security Definitions applid.SIGNON UACC(NONE) where “applid” is the product application ID defined during installation and “SIGNON” is the function name that controls user access and logon to the product. Review the function code table, later in this chapter, for more information about product functions. The default user access level should be NONE (no access to the product), as shown in the UACC parameter in the model.
Chapter 2: Security Definitions Using External Security 9. Identify the profile that should be used by each product user ID. You can use two methods to identify the profile that should be used for each user ID. a. For each product user ID defined to RACF, specify the following RACF installation data in RACF: LMRK(profile) where “profile” is the name of an Internal Security profile. b.
Using User Exit Security Chapter 2: Security Definitions 1. Ensure that IBM’s system authorization facility (SAF) is active. SAF always is active if you are using RACF, but you may need to perform a manual step to activate SAF with other software packages. For example, to activate SAF in CA-ACF2, the SAF bit needs to be turned on in the CA-ACF2 global system options. 2. Define product user IDs to your external security product.
Chapter 2: Security Definitions Using Internal Security 2. Specify the program name of your user exit in the USEREXIT startup parameter.
Using Internal Security Supplied User IDs and Profiles Chapter 2: Security Definitions Internal Security is distributed with a predefined master user ID and password for each Landmark PerformanceWorks MVS product. The following table lists the master user ID and password provided for each product.
Chapter 2: Security Definitions TMON for DB2 TMON for DBCTL The Monitor for MVS 2.0 System Administrator’s Guide Using Internal Security User ID Profile ID Description TMONCICS $MASTER Master user ID and default profile ID. This profile grants user ID TMONCICS the ability to do everything in TMON for CICS/ESA. Do not change or delete this user ID and profile. This ensures that you always can update your Internal Security definitions.
Using Internal Security TMON for MQSeries TMON for MVS Implementing Internal Security Chapter 2: Security Definitions The following table lists the supplied user IDs and profiles for TMON for MQSeries. User ID Profile ID Description APPPROG $DEFAULT User ID and default profile ID for an applications programmer. MQADM $MQADMIN User ID and default profile ID for an MQSeries administrator. SYSADM $SYSADM User ID and default profile ID for the TMON for MQSeries system administrator.
Chapter 2: Security Definitions Using Internal Security 2. Define your product users to Internal Security. Use the supplied user IDs or add your own. Read “User Profiles Directory” and “User Definition,” later in this chapter, for further information on adding, updating, and deleting user IDs. 3. Activate Internal Security.
Security Definitions Menu Chapter 2: Security Definitions Security Definitions Menu JOBNAME: SYSID : THE MONITOR FOR MVS VERSION: 2.
Chapter 2: Security Definitions Fields Security Definitions Menu CURRENT USERS Displays the current number of users of this product system. FACILITIES Specifies the security type used to protect product functions. Specify one of the options in the following table. Value Description I Specify I to use Internal Security. This is the default. N Specify N if you do not want product functions to be secured. No security checking is performed. U Specify U to use User Exit Security.
User Profiles Directory Chapter 2: Security Definitions User Profiles Directory JOBNAME: SYSID : THE MONITOR FOR MVS VERSION: 2.0 USER PROFILES DIRECTORY DATE: TIME: COMMAND: TO "CHANGE" OR "DELETE" : CURSOR SELECT USER ID OR PROFILE ID. TO "ADD" : CURSOR SELECT ANY USER ID OR PROFILE ID.
Chapter 2: Security Definitions User Profiles Directory ➥ USER ID Displays the 1- to 8-character user ID for the product. Cursor-select this field to add, update, or delete a user definition in the control file. Once you have cursor-selected a user ID, the User Definition screen is displayed. USER NAME Shows the complete name of the user to whom the specified user ID and its associated profile ID are assigned. The name can be up to 34 characters long and is used only for documentation and identification.
User Definition Chapter 2: Security Definitions User Definition JOBNAME: SYSID : THE MONITOR FOR MVS VERSION: 2.
Chapter 2: Security Definitions User Definition Primary Commands Enter the following commands on the command line. ADD Adds user definitions to the control file. Type over the appropriate fields (PASSWORD, PROFILE, USER FULL NAME, or USERID) to identify the new user or profile ID; then enter this command (or cursor-select the ADD field). DELETE Deletes user definitions from the control file. You also can cursor-select the DELETE field to perform this function.
User Definition Chapter 2: Security Definitions USER FULL NAME Displays the complete name of the user to whom the specified user ID and its associated profile ID are assigned. The name can be up to 34 characters long. USERID Displays a 1- to 8-character user ID for the product.
Chapter 2: Security Definitions Secured Functions Directory Secured Functions Directory JOBNAME: SYSID : THE MONITOR FOR MVS VERSION: 2.
Secured Functions Directory Chapter 2: Security Definitions CODE Shows the 3-digit internal identifier of the function. DESCRIPTION Displays the 1- to 30-character text description of the function. FUNCTION Displays the 1- to 8-character name of the facility within the product. All functions are listed in the function code table, later in this chapter. PRIMARY Shows the primary resource type for which a function can be secured.
Chapter 2: Security Definitions Note Secured Functions Directory Value Description V The function can be secured by tape or DASD volume. Only J types currently are used by TMON for CICS. Only J and T types currently are used by TMON for DB2, TMON for DBCTL, and TMON for MVS. Only D types currently are used by TMON for MQSeries. SECONDARY Shows the secondary resource type for which a function can be secured. TMON for DB2 secondary resources are DB2 plan or package names.
Function Code Table Chapter 2: Security Definitions Function Code Table The following table describes every product secured function for Landmark PerformanceWorks MVS products. It is sorted by function (the second column). You cannot change these functions; they are predefined by each product. Note TMON for CICS, TMON for DBCTL, TMON for MQSeries, and TMON for MVS do not use secondary resources.
Chapter 2: Security Definitions Function Code Table Product Function Code Primary Resource TMON for MVS CSMONOPT 098 none Controls access to the Common Storage Monitor Options screen. TMON for DB2 CSTGSDSP 195 none Controls access to the Database Common Storage Summary screen. CICS DATADCTS DB2 DBCTL MQSeries MVS 222 222 222 222 222 none none none none none Controls access to data dictionary screens.
Function Code Table Chapter 2: Security Definitions Code Primary Resource TMON for MQSeries EXCPTDEF TMON for MVS 154 130 none none For TMON for MQSeries, controls the ability to add and update exceptions. For TMON for MVS, controls access to the Exception Definition Menu. TMON for DB2 TMON for DBCTL EXCPVIEW 073 073 none none Controls the ability to view the Exception Monitor screens. TMON for DB2 EXPLAIN 210 DB2 subsystem Controls access to the DB2 EXPLAIN Utility.
Chapter 2: Security Definitions Function Code Table Code Primary Resource TMON for DB2 JOBSUMM TMON for DBCTL TMON for MQSeries 196 196 196 none none none Controls access to the Active Job Summary screen. TMON for CICS LOGOSCRN TMON for MQSeries TMON for MVS 004 004 004 none none none Controls access to the sign-on screen; TMON for CICS/ESA does not support this function. TMON for MVS MDFPRSM 176 none Controls access to the Domain and LPAR Summary screens.
Function Code Table Chapter 2: Security Definitions Code Primary Resource 246 246 246 246 246 none none none none none Controls access to the Detail Profile Definition screen. TMON for MQSeries PRTAUTOF TMON for MVS 093 093 none none Controls the ability to use the PRINTOFF command. TMON for MQSeries PRTAUTON TMON for MVS 092 092 none none Controls the ability to use the PRINTON command.
Chapter 2: Security Definitions Function Code Table Product Function Code Primary Resource Secondary Resource Description TMON for DBCTL RSR 055 none Controls access to remote site recovery functions. TMON for DB2 SAVESQL 216 none Controls the ability to export SQL data from the DB2 EXPLAIN Utility to a sequential or partitioned data set.
Function Code Table Chapter 2: Security Definitions Primary Resource Secondary Resource Description 040 DB2 subsystem DB2 plan name TMON for MQSeries STGCAUTH 123 job name Controls access to storage class functions. TMON for DBCTL STGPOOLS 210 none Controls access to storage class functions. TMON for CICS STORANAL 106 none Controls access to the Storage Analysis menu. TMON for CICS TMON for MVS STORTCBS 221 221 none none Controls access to the Address Space TCB Map screen.
Chapter 2: Security Definitions Function Code Table Code Primary Resource TMON for MQSeries THRDAUTH 156 job name Controls command functions for threads. TMON TMON TMON TMON TMON for for for for for CICS USERCMDS DB2 DBCTL MQSeries MVS 208 208 208 208 208 none none none none none Controls access to the User Command Definitions screen.
Function Code Table Chapter 2: Security Definitions Product Function Code Primary Resource TMON for DB2 TMON for DBCTL UTILMON 051 051 none none Controls access to the Current System Statistics menu. TMON for MVS UTILMSTG 152 none Controls access to the MVS Storage Displays Menu. TMON for MVS UTILMVSB 166 none Controls display of the MVS Control Blocks screen. TMON for MVS UTILSRMB 167 none Controls access to the SRM Control Blocks screen.
Chapter 2: Security Definitions Profiles/Resources Directory Profiles/Resources Directory JOBNAME: SYSID : THE MONITOR FOR MVS VERSION: 2.0 PROFILES/RESOURCES DIRECTORY DATE: TIME: COMMAND: TO "CHANGE" OR "DELETE" : CURSOR SELECT USER ID OR PROFILE ID. TO "ADD" : CURSOR SELECT ANY USER ID OR PROFILE ID.
Profiles/Resources Directory Chapter 2: Security Definitions Product Action Displays TMON for DBCTL On the command line, enter =M.1.3. Profiles/Resources Directory TMON for MQSeries On the command line, enter =8.1.3. Profiles/Resources Directory TMON for MVS On the command line, enter =S.2.3.
Chapter 2: Security Definitions TMON for CICS, TMON for DBCTL, TMON for MQSeries, and TMON for MVS do not use secondary resources. Profiles/Resources Directory TMON for DB2 secondary resources are DB2 plan or package names. Secondary resources qualify security within the limits of the primary resource. For example, you can restrict the user plans that can be reviewed by DB2 subsystem name and by plan name within DB2 subsystem using the PLANSUMM function.
Detail Profile Definition Chapter 2: Security Definitions Detail Profile Definition JOBNAME: SYSID : THE MONITOR FOR MVS VERSION: 2.
Chapter 2: Security Definitions Detail Profile Definition Product Action Displays TMON for DBCTL On the command line, enter =M.1.3. Profiles/Resources Directory Cursor-select a profile definition. Detail Profile Definition TMON for MQSeries On the command line, enter =8.1.3. Profiles/Resources Directory Cursor-select a profile definition. Detail Profile Definition TMON for MVS On the command line, enter =S.2.3. Profiles/Resources Directory Cursor-select a profile definition.
Detail Profile Definition Chapter 2: Security Definitions DESCRIPTION Displays the 1- to 30-character description of the function. You cannot change this field. FUNCTION Displays the 1- to 8-character name of the facility within the product. You cannot change this field. LO-ACCESS LEVELS-HI Displays the level of access assigned this profile for each secured function. Enter X under the access level appropriate for the function and the profile. Access levels vary in meaning depending on the function.
Chapter 2: Security Definitions Detail Profile Definition beginning with the characters “PROD.” If you specify an asterisk alone, all values of the primary resource are used. If you want to specify more primary resources than this screen allows (even after using pattern matching), add other definitions for the profile using the other primary resources.
Detail Profile Definition Chapter 2: Security Definitions resources are included in the security for resource functions. For example, you can restrict the user plans that can be reviewed by DB2 subsystem name and plan name within DB2 subsystem using the PLANSUMM function. ➥ UPDATE Updates a profile definition in the control file. Type over the information you want to change; then cursor-select this field to update the definition in the control file.
Chapter 2: Security Definitions Function Access Level Table Function Access Level Table This section shows the minimum access level required to use each product function within your Landmark PerformanceWorks MVS product. If more than one access level is indicated for a function (in other words, if more than one access level column has an X in it), the various access levels provide access to different aspects of the function.
Function Access Level Table Chapter 2: Security Definitions Minimum Level Required 2-42 Function Code CONSOLE N U 230 X X READ (or higher) lets users view console displays. UPDT (or higher) is required to enter commands on console displays.
Chapter 2: Security Definitions Function Access Level Table Minimum Level Required Function Code SECURITY C A Notes R U 240 X X SHUTDOWN 003 X SIGNON 001 X STORANAL 106 X STORTCBS 221 X STORTIOT 220 X STRGALTR 211 X Works with the STRGNPRV and STRGPRV functions. To alter private storage, READ access must be specified for STRGALTR and UPDT must be specified for STRGPRV.
Function Access Level Table Chapter 2: Security Definitions Minimum Level Required Function Code USERCMDS USERDEF N R U 208 X X 242 X X USERDIR 241 X USERPROF 244 X TMON for DB2 C A Notes READ (or higher) lets users view user command definitions. UPDT (or higher) lets users add and modify user command definitions. X READ (or higher) lets users view their own user ID definitions and passwords. UPDT (or higher) lets users review and update their own user ID definitions and passwords.
Chapter 2: Security Definitions Function Access Level Table Minimum Level Required Function Code JOBSUMM 196 X MONCNTL 160 X N R MONINIT 163 X ONLINANL 090 X OPENMAIN 217 X PFKDEF 250 X PFKEYS 233 X PGSETDSP 101 X PLANSUMM 212 X PROFDTL 246 X RESRCDSP 190 X RMTPTDEF 209 X RMTPTSEL 207 X SAVESQL 216 X SECFUNCS 243 X SECFUNDF 245 X SECURITY 240 X SELUSRID 006 X SETAUTH 012 X SHDWFRSH 044 X SHIFTDEF 175 X SHUTDOWN 002 X SIGNON 001 X SQL
Function Access Level Table Chapter 2: Security Definitions Minimum Level Required 2-46 Function Code STRGALTR 211 X Works with the STRGNPRV and STRGPRV functions. To alter private storage, READ access must be specified for STRGALTR and UPDT must be specified for STRGPRV. To alter nonprivate storage, READ access must be specified for STRGALTR and UPDT must be specified for both STRGPRV and STRGNPRV. STRGDSPY 137 X Works with the STRGNPRV and STRGPRV functions.
Chapter 2: Security Definitions TMON for DBCTL Function Access Level Table The following table shows the minimum access level required to use each product function for TMON for DBCTL.
Function Access Level Table Chapter 2: Security Definitions Minimum Level Required 2-48 Function Code RMTPTDEF N R U 209 X X RMTPTSEL 207 X RSR 055 X SECFUNCS 243 X SECFUNDF 245 X SECURITY 240 X X C A Notes X READ (or higher) lets users view the remote session definitions. UPDT (or higher) lets users change remote session definitions and the SLU session ID prefix. ALTR lets users add and delete remote session definitions.
Chapter 2: Security Definitions Function Access Level Table Minimum Level Required Function Code USERCMDS 208 N R U X X USERDEF 242 X USERDIR 241 X USERPROF 244 X UTILMON 051 X TMON for MQSeries C A Notes READ (or higher) lets users view user command definitions. UPDT (or higher) lets users add and modify user command definitions. X The following table shows the minimum access level required to use each product function for TMON for MQSeries.
Function Access Level Table Chapter 2: Security Definitions Minimum Level Required 2-50 Function Code PFKDEF N R U 250 X X PROCAUTH 122 X PRODPSWD 202 X PROFDTL 246 X PRTAUTOF 093 X PRTAUTON 092 X C A Notes X READ (or higher) lets users view function key settings. UPDT (or higher) lets users change function key settings for their user ID. ALTR lets users change function key settings for any user ID.
Chapter 2: Security Definitions Function Access Level Table Minimum Level Required Function Code SHIFTDEF N U 175 X X SHUTDOWN 003 X SIGNON 001 X STGCAUTH 123 X STRGALTR 211 X Works with the STRGNPRV and STRGPRV functions. To alter private storage, READ access must be specified for STRGALTR and UPDT must be specified for STRGPRV. To alter nonprivate storage, READ access must be specified for STRGALTR and UPDT must be specified for both STRGPRV and STRGNPRV.
Function Access Level Table Chapter 2: Security Definitions Minimum Level Required Function Code UTILMENU 150 TMON for MVS N R U C A Notes X The following table shows the minimum access level required to use each product function for TMON for MVS. Minimum Level Required 2-52 Function Code ADVFUNCS 203 X CCWTRACE 142 X N R CNTLFILE 238 X CONSOLE 230 X CSMON 099 X CSMONDET 097 X CSMONOPT 098 X U C A Notes X READ (or higher) lets users view console displays.
Chapter 2: Security Definitions Function Access Level Table Minimum Level Required Function Code HLPFLDIR N U 236 X X READ (or higher) lets users view the Field-Level Help Directory screen. UPDT (or higher) is required to change the ACTIVE VERSION field on the Field-Level Help Directory screen. HLPFLDTL 237 X HLPMSDIR 253 X X READ (or higher) lets users view the Message-Level Help Directory screen.
Function Access Level Table Chapter 2: Security Definitions Minimum Level Required Function 2-54 Code N R U X C A Notes X READ (or higher) lets users view the remote session definitions. UPDT (or higher) lets users change remote session definitions and the SLU session ID prefix. ALTR lets users add and delete remote session definitions.
Chapter 2: Security Definitions Function Access Level Table Minimum Level Required Function Code STRGPRV 116 N R U X X SVCDUPD 180 SYSADM 178 X USERCMDS 208 X X USERDEF 242 X X C A Notes Works with the STRGDSPY and STRGALTR functions. See the above notes on these functions for the authorization required to display and alter private storage. X USERDIR 241 X USERPROF 244 X UTILAPFL 155 X UTILASMB 169 X READ (or higher) lets users view user command definitions.
Function Access Level Table Chapter 2: Security Definitions Minimum Level Required 2-56 Function Code UTILSRMB 167 X UTILSSVC 151 X N R UTILSWAP 163 X UTILVMNT 162 X UTILVOLU 173 X UTILVSMB 168 X WKLDDEF 179 X XCFMON 096 X U X C A Notes READ (or higher) lets users view workload definitions. UPDT (or higher) is required to update and activate definitions.
Chapter 3: Landmark Product Communication A performance problem in any address space in your network can affect performance throughout the system. The ability to monitor the complete system enables you to locate and solve system problems quickly and easily. You can use Landmark product communication to define a network between products and monitor address spaces anywhere in the network. The following PerformanceWorks MVS products support Landmark product communication.
Access Methods Chapter 3: Landmark Product Communication • TMON for DBCTL has implicit pass-through connections to other TMON for DBCTL products on any processor complex. • TMON for MQSeries has implicit pass-through connections to other TMON for MQSeries products on any processor complex. • TMON for MVS has implicit pass-through connections to other TMON for MVS products on any processor complex.
Chapter 3: Landmark Product Communication Setting Up Landmark Product Communication with these messages, refer to the messages and codes manual for the appropriate product. Setting Up Landmark Product Communication Before you can use Landmark product communication with any of the Landmark PerformanceWorks MVS products, you must complete these steps. (Each step is described in more detail following the checklist.) Step 1. Verify that all local VTAM applids are installed. Step 2.
Setting Up Landmark Product Communication Chapter 3: Landmark Product Communication Product Step 3 Applid System Set up cross-domain communications to support remote applids. Set up cross-domain communications to support each of the remote applids listed in Step 2. Use adjacent system services control point (SSCP) tables, dynamic cross-domain resource (CDRSC) definitions, or hard-coded CDRSC definitions. For complete information on customizing VTAM, read IBM’s VTAM Installation & Resource Definition.
Chapter 3: Landmark Product Communication Setting Up Landmark Product Communication number−remote−users × number−remote−sessions = total−SLUs You should define a minimum of 10 SLUs. A maximum of 999 SLUs can be defined.
Setting Up Landmark Product Communication Chapter 3: Landmark Product Communication Product Description TMON for MQSeries Specify the SLUCOUNT startup parameter in member TMQSPARM of the data set identified by ddname TMQSPRMS in the TMON for MQSeries startup JCL. TMON for MVS Specify the SLUCOUNT startup parameter in member TMVSPARM of the data set identified by ddname TMVSPRMS in the TMON for MVS startup JCL. Use the following template when coding your SLU definitions.
Chapter 3: Landmark Product Communication VTAM Logon Mode Table Considerations Setting Up Landmark Product Communication The DLOGMOD parameter of the APPL macro specifies the name of the entry in the VTAM logon mode table that contains the parameters used in a session. If you have SNA type-2 logical units and your logon mode table is working, continue to use it. If you have problems, however, create your own logon mode table with the following entry.
Setting Up Landmark Product Communication Step 6 Chapter 3: Landmark Product Communication Set up network requirements for non-SNA terminals. This section primarily applies if you intend to log onto the Landmark PerformanceWorks MVS product from a non-SNA terminal that either is remote or will be in cross-domain session with the product. It also may apply to SNA sessions if the outbound RUSIZE in the BIND is very large or is not specified.
Chapter 3: Landmark Product Communication Step 8 Setting Up Landmark Product Communication Adjust the local SLU session ID prefix and all the session definitions. Use the Remote Sessions Directory and Remote Session Definition screens to adjust the local SLU session ID prefix and all the session definitions of Landmark PerformanceWorks MVS products in the network that you want to be able to access. The following table indicates how to access these screens from each Landmark product.
Using Explicit Pass-Through Chapter 3: Landmark Product Communication For all security types, verify that the user IDs you want to use Landmark product communication are authorized to use functions in the Landmark product communication network. Read the chapter on Landmark product communication in each product’s documentation to identify that product’s connection points and the functions it accesses by linking to other products. Step 10 Verify that the correct product releases are installed.
Chapter 3: Landmark Product Communication JUMP Command Using Explicit Pass-Through Use the JUMP command to access the primary applid of a Landmark product. You identified primary applids in Step 7 and defined them in Step 8 of “Setting Up Landmark Product Communication,” earlier in this chapter. The syntax of the JUMP command is: JUMP=code where “code” is one of the following product identifiers.
Using Implicit Pass-Through Chapter 3: Landmark Product Communication product you accessed explicitly from TMON for DBCTL, you return to TMON for DBCTL. Using Implicit Pass-Through Implicit access is product-to-product communication initiated automatically by the system. It occurs only between address spaces of the same product (for example, TMON for CICS to TMON for CICS) and can occur between products in the same or different processor complexes.
Chapter 3: Landmark Product Communication Usage Notes Using NaviGate Any security limitations set up for your user ID when you access the product directly are active when you access the product implicitly. If your user ID is not authorized to use the product, implicit access does not occur. If you are to be able to access other Landmark PerformanceWorks MVS systems remotely, their security systems must be the same.
Using NaviGate Chapter 3: Landmark Product Communication From this screen: Cursor-select: To access this screen: CICS MQSeries Summary MQ_SERIES QMGR NAME field (available for only CICS Transaction Server 1.
Chapter 3: Landmark Product Communication Using NaviGate From this screen: Cursor-select: To access this screen: Sequential File Statistics (when summarized by file/DB on the File/DB Activity Selection Menu) file number in the FILE# field TMON for MVS Device Detail Selection Menu TMON for DB2 The following table shows where the NaviGate connections to other Landmark PerformanceWorks MVS products occur in TMON for DB2.
Using NaviGate Chapter 3: Landmark Product Communication From this screen: Cursor-select: To access this screen: Primary Menu Option 4 (ACTIVE JOB SUMMARY) TMON for MVS Job Execution Monitor PSB Detail CICS TKN field TMON for CICS/ESA Detail Transaction Data Thread Detail RECVRY TOKEN field TMON for CICS/ESA Task Details VSAM Data Set Information VOLUME field TMON for MVS Device Detail Selection Menu TMON for MQSeries The following table shows where the NaviGate connections to other Landma
Chapter 3: Landmark Product Communication Using NaviGate You may receive error messages from a Landmark product you are trying to access using NaviGate. Usually this happens when an error occurs during the access attempt. For help with these messages, refer to the messages and codes manual for the appropriate product. When you log off of a product you accessed using a NaviGate connection from one of the Landmark PerformanceWorks MVS products, you return to the same Landmark product.
Remote Sessions Directory Chapter 3: Landmark Product Communication Remote Sessions Directory JOBNAME: SYSID : THE MONITOR FOR MVS VERSION: 2.
Chapter 3: Landmark Product Communication Fields Remote Sessions Directory ➥ APPLID Displays the applid of a Landmark product defined in the control file. All applids defined in the control file are shown. Cursor-select an applid if you want to update or delete it or if you want to use it as a template for a new applid. The Remote Session Definition screen is displayed. DESCRIPTION Displays a brief description of the session definition. PRODUCT Displays the product for this session definition.
Remote Sessions Directory Chapter 3: Landmark Product Communication • The product session is active and can perform Landmark NaviGate functions (in other words, its modification level is correct). • At least one Landmark product communication link has been made to the product session.
Chapter 3: Landmark Product Communication Remote Session Definition Remote Session Definition JOBNAME: SYSID : THE MONITOR FOR MVS VERSION: 2.
Remote Session Definition Chapter 3: Landmark Product Communication product session; then enter this command (or cursor-select the ADD field). DELETE Deletes a remote session definition from the control file. You also can cursor-select the DELETE field to perform this function. UPDATE Updates a remote session definition in the control file. Type over the information you want to change; then enter this command (or cursor-select the UPDATE field).
Chapter 3: Landmark Product Communication Remote Session Definition Value Description Y Indicates that the product session is the primary session PRODUCT Shows the product for this session definition. The following table lists valid identifiers.
Remote Sessions Logon Chapter 3: Landmark Product Communication Remote Sessions Logon JOBNAME: SYSID : THE MONITOR FOR MVS VERSION: 2.
Chapter 3: Landmark Product Communication Remote Sessions Logon DESCRIPTION Displays a brief description of the product with the applid shown in the corresponding APPLID field. PRODUCT Displays the product for this session definition. The following table lists valid identifiers.
Chapter 3: Landmark Product Communication 3-26
Chapter 4: Support and Maintenance The goal of Landmark’s Customer Services team is to help you solve any problems or answer any questions that arise as you use Landmark products or documentation.
Year 2000 Compliance Warranty Chapter 4: Support and Maintenance Your License Agreement Our Credit Policy Permanent License or Lease/Purchase You will receive a credit for two month’s maintenance on your next annual maintenance invoice. Rental You will receive a credit for one month’s rental upon renewal. Year 2000 Compliance Warranty Landmark Systems Corporation warrants that its licensed programs are Year 2000 compliant.
Chapter 4: Support and Maintenance Before Contacting Landmark Product Support You should define your problem, assign it a severity level according to the guidelines in this section, and gather any appropriate supporting documentation before you contact Landmark for product support. When defining your problem, be prepared to describe it as completely as possible and outline the sequence of events that preceded it. Use the following criteria to assign the problem a severity level.
Product Support Error Diagnostic Screen Chapter 4: Support and Maintenance The Error Diagnostic Screen enables you to recover from an internal error. It also provides us with the information we need to diagnose the problem. ERROR DIAGNOSTIC SCREEN COMMAND: AN ERROR HAS BEEN ENCOUNTERED IN PROGRAM $PGMCTL !!! ANY MESSAGE INFORMATION ABOVE MAY BE RESIDUAL. SELECT AN OPTION BELOW TO CONTINUE OR TERMINATE.
Chapter 4: Support and Maintenance Product Support • If you licensed this product through an authorized reseller, report any problems or concerns directly to the reseller. • If you licensed this product directly from Landmark in the U.S. or Canada, contact Landmark Customer Services at one of the following numbers: – In the United States, the U.S. Virgin Islands, and Canada, 1-800-775-LMRK (or 1-800-775-5675) – 1-703-464-1300 Standard operating hours are Monday through Friday from 8 a.m. to 6 p.m.
Product Support Chapter 4: Support and Maintenance • Assigns an activity number to the problem. Be sure you record the activity number and use it during follow-up communication to ensure efficient handling of your problem. During subsequent communication, we use your activity number to route the communication appropriately.
Chapter 4: Support and Maintenance Note Changing the Priority of an Activity Product Support If a Landmark technician requests your supporting documentation and does not receive it within two weeks, your activity is closed automatically.
Product Maintenance Premium Sunset Support Policy Chapter 4: Support and Maintenance Supporting sunsetted releases is a costly practice and is impossible for Landmark to do when the operating system or subsystem Landmark products require to provide support are no longer supported by their respective vendors. Between the time Landmark sunsets a product and the time it becomes impossible to support the release, you can request a price for premium sunset maintenance.
Chapter 4: Support and Maintenance Product Maintenance Landmark assigns to each tape an identifier that indicates the level of service applied. These identifiers appear on the physical tape in either ETyyvn or PSyyvn format, as described in the following table. Identifier Part Description ET An early test tape that is created only for Alpha and Beta products. PS A base tape containing products that are generally available. yy The 2-digit year in which the tape was created.
Configuration Changes and Disaster Recovery Chapter 4: Support and Maintenance System User’s Guide, which is included in every product’s documentation set. Proactive Maintenance Policy If you do not want to wait until you have a problem, you have the option of receiving product maintenance automatically. Landmark will proactively ship new maintenance to you on a CUM tape as soon as it is published.
Chapter 4: Support and Maintenance Configuration Changes and Disaster Recovery New or Replacement Processors Landmark requires written notification when new CPUs are installed and new CPU serial IDs are assigned. We should receive notification on company letterhead, describing the change to occur, when it will occur, and the new CPU identification information. Customers outside the U.S. and Canada should notify their local Landmark representative.
Chapter 4: Support and Maintenance 4-12
Appendix: TMON for MVS Sample Library This appendix lists the members in the TMON for MVS 2.0 sample library, in alphabetical order. A brief description of each member is provided. For a list of members in the Strategic Services sample library, see “Appendix C: Strategic Services Sample Library” in PerformanceWorks for MVS and OS/390 Installation Guide.
Appendix: TMON for MVS Sample Library A-2 Contents Description TMVRWS05 Maximum and Average Batch Users TMVRWS06 System reports TMVRWSEL Dummy select member TMVSASWG SAS workload manager goal mode reports for monitoring velocity and response time TMVSASWK SAS workload manager compatibility mode report for monitoring velocity and response time TMVSCNTL Job stream to copy select key ranges from one control file to another TMVSRMIS Diagnostic program TMVTSDOC Documentation for CA-Top Secret
Index Numbers and Special Characters $DEFAULT profile, 2-7 to 2-8 $LMRKTMR resource class, 2-5 $RACFCDT member, 2-5 $RACFRTB member, 2-5 $TRACEOFF command, 2-4 $TRACEON command, 2-4 $USRPRMS member, 2-8 A Access levels, 2-38, 2-41 Access methods, 2-15 ACF2DOC member, 2-4 ACTIVE status, 3-19, 3-25 Activity Monitor installation verification, 1-2 Activity number, 4-6 ACTIVMON function, 2-24 ACTVLOG function, 2-24 ACTVMON function, 2-24 ADD command, 2-19, 2-37, 3-21 ADD field, 2-19, 2-37, 3-22 Address of Landm
Index TMQSPRMS, 3-6 TMVSPRMS, 3-6 Delay Monitor installation verification, 1-4 DELETE command, 2-19, 2-37, 3-22 DELETE field, 2-19, 2-37 session definition, 3-22 DESCRIPTION field, 2-22, 2-38 product, 3-25 product session, 3-22 session definition, 3-19 Detail Profile Definition screen, 2-36 to 2-40 Directories Profiles/Resources, 2-33 to 2-35 Remote Sessions, 3-18 to 3-20 Secured Functions, 2-21 to 2-23 User Profiles, 2-16 to 2-17 Distributed sample library, A-1 DLYGRP function, 2-25 DLYGRPG function, 2-25
Index I J I access method, 2-15 Implicit pass-through defined, 3-1 description, 3-12 using, 3-12 valid product releases, 3-1 see also Landmark product communication INACT status, 3-19, 3-25 Installation sample library members, A-1 verification procedure checklist, 1-1 see also PerformanceWorks for MVS and OS/390 Installation Guide Installation verification procedure (IVP) Activity Monitor, 1-2 checklist, 1-1 Collection Analysis, 1-3 Delay Monitor, 1-4 Exception Monitor, 1-3 Graphic Monitor, 1-3 Remote Se
Index MAXUSER command, 2-15 MDFPRSM function, 2-27 Members LMRKMTB, 3-7 TCEVTAM, 3-5 to 3-6 TDBCPRMS, 3-5 TDBCVTAM, 3-6 TDBPARM, 3-5 TMDBVTAM, 3-6 TMON8VTM, 3-5 to 3-6 TMONAPPL, 3-6 TMQSPARM, 3-6 TMQSVTAM, 3-6 TMVSPARM, 3-6 MODSTOR function, 2-27 MODTAB option, 3-7 MONCNTL function, 2-27 MONINIT function, 2-27 MSGAUTH function, 2-27 MVSCONTN function, 2-27 N N access method, 2-15 N function type, 2-22 NAMLAUTH function, 2-27 NaviGate accessing all screens, 3-17 available product connections, 3-2 connectio
Index listing in Internal Security, 2-33 multiple resources, 2-33, 2-36 specifying ID, 2-36 viewing user IDs associated with, 2-17 PROFILES/RESOURCES DIRECTORY option, 2-14 Profiles/Resources Directory screen, 2-33 to 2-35 PRTAUTOF function, 2-28 PRTAUTON function, 2-28 PRTCLOSE function, 2-28 PRTCMD function, 2-28 PRTDFDSN function, 2-28 PRTDFSYS function, 2-28 PRTDFVTM function, 2-28 PRTMENU function, 2-28 PRTSTART function, 2-28 PRTSTOP function, 2-28 PS tapes, 4-9 PSERVIC operand, 3-7 PTF service, 4-8
Index valid type combinations, 2-1 see also External, Internal, and User Exit Security Security Definitions Menu screen, 2-14 to 2-15 SECURITY function, 2-29 SECURITY METHOD ACTIVE field, 2-15 SELUSRID function, 2-29 SETAUTH function, 2-29 SEV1 severity level, 4-3 SEV2 severity level, 4-3 SEV3 severity level, 4-3 SEV4 severity level, 4-3 Severity 1 problems, 4-3 Severity 2 problems, 4-3 Severity 3 problems, 4-3 Severity 4 problems, 4-3 Severity levels changing, 4-7 defined, 4-3 SHADOWREFRESH command, 2-29
Index TSDOC member, 2-4 TSPROF operand, 3-7 TYPE field, 2-23 TYPE VALUES field, 2-23 U U access method, 2-15 UACC parameter, 2-6 UNITSZ parameter, 3-8 UNKNWN status, 3-19, 3-25 UPDATE command, 2-19, 2-37, 2-40, 3-22 UPDATE field, 2-19, 2-40, 3-23 UPDT access level, 2-38 User Definition screen, 2-18 to 2-20 User Exit Security activating, 2-8, 2-13 description, 2-8 steps to implement, 2-8 user exits, 2-8 valid combinations with other methods, 2-15 USER FULL NAME field, 2-20 USER ID field, 2-17 User IDs assi
Index Index-8
