Installing the data server on a z/VM system

Whether you use customization during installation or manual customization to customize MainView for Linux — Servers, you must install the z/VM data server on all of the z/VM systems that you want to monitor.

Before you begin

You must FTP the z/VM data server installation script to the z/VM system where you want to install the z/VM data server (see Task 12—Creating a job to FTP the z/VM installation files).

Verify that you have the VMARC utility installed.
Note
The VMARC utility is available for download from the IBM website.

Create the following VM/CMS userids:

USERID	Component	Notes
VMMAVMSR	BMC z/VM Monitor Reader	Create this userid only if you are using the BMC z/VM Monitor Reader to collect z/VM performance data. A sample user directory entry is located in the data set hilevel.BBSAMP(VMMVMNDR). See below. You might need to adjust the virtual machine storage size for VMMAVSR depending on the virtual address and size of the MONDCSS shared segment.
MMLVSRV	z/VM data server	A sample user directory entry is located in the data set hilevel.BBSAMP(MMLVDRCT). See BBSAMP member MMLVDRCT

The following figure shows a sample user directory entry that is located in the data set hilevel.BBSAMP(VMMVMNDR).

000001 USER VMMAVMSR password 64M 99M BEG
000002 *----------------------------------------------------
000003 * Sample directory entry for CP Monitor Reader
000004 * virtual machine.
000005 *----------------------------------------------------
000006 IUCV *IDENT RESANY LOCAL REVOKE
000007 IUCV ALLOW
000008 IUCV *MONITOR MSGLIMIT 255
000009 NAMESAVE MONDCSS
000010 OPTION QUICKDSP
000011 MACHINE ESA
000012 SHARE RELATIVE 300
000013 IPL CMS
000014 CONSOLE 0009 3215 T OP
000015 SPOOL 000C 2540 READER *
000016 SPOOL 000D 2540 PUNCH A
000017 SPOOL 000E 1403 A
000018 LINK MAINT 190 190 RR
000019 LINK MAINT 19D 19D RR
000020 LINK MAINT 19E 19E RR
000021 *----------------------------------------------------
000022 * Standard CMS mdisk for code, log, local files, etc.
000023 * You must CMS FORMAT this disk.
000024 * Allow MMLVSRV to update disk during install.
000025 *----------------------------------------------------
000026 MDISK 191 3390 start-cyl 10 volser MR ALL ALL

The following figure shows a sample user directory entry that is located in the data set hilevel.BBSAMP(MMLVDRCT).

000001 USER MMLVSRV password 64M 99M ABCEG
000002 *-------------------------------------------------------
000003 * Sample directory entry for MAINVIEW for Linux
000004 * VM Data Server virtual machine.
000005 *-------------------------------------------------------
000006 * NOTE:
000007 * Class "A" is required for FORCE and SET SHARE.
000008 * Class "B" is required for XAUTOLOG.
000009 * Class "C" is required for CP SEND.
000010 *-------------------------------------------------------
000011 * Use LNKNOPAS to allow Data Server to access any MDISK
000012 * OPTION QUICKDSP LNKNOPAS
000013 *-------------------------------------------------------
000014 OPTION QUICKDSP
000015 MACHINE ESA
000016 SHARE RELATIVE 300
000017 IPL CMS
000018 CONSOLE 0009 3215 T OP
000019 SPOOL 000C 2540 READER *
000020 SPOOL 000D 2540 PUNCH A
000021 SPOOL 000E 1403 A
000022 LINK MAINT 190 190 RR
000023 LINK MAINT 19D 19D RR
000024 LINK MAINT 19E 19E RR
000025 *-------------------------------------------------------
000026 * Standard CMS mdisk for code, log, local files, etc.
000027 * You must CMS FORMAT this disk.
000028 *-------------------------------------------------------
000029 MDISK 191 3390 start-cyl 20 volser MR rpass wpass mpass

You must FTP the z/VM data server installation script, MMLVINST EXEC, to the z/VM system where you want to install the z/VM data server (see Task 12—Creating a job to FTP the z/VM installation files).
MainView for Linux — Servers requires one of the following z/VM monitors for viewing z/VM performance data:
- BMC z/VM Monitor Reader
- ESAMON or zMON by Velocity Software
- Performance Toolkit by IBM

The BMC z/VM Monitor Reader is packaged with this version of MainView for Linux — Servers. The MMLVINST EXEC will install and configure the BMC z/VM monitor if you choose to use it. For information about installing the IBM product Performance ToolKit or the Velocity Software product ESAMON or z/MON, refer to the documentation for those products.

Verifying the z/VM data server installation script

After the z/VM data server install script is on the z/VM System, verify the configuration parameters by viewing the MMLVINST EXEC install script with the XEDIT command as shown below.

XEDIT MMLVINST EXEC A
MMLVINST EXEC A1 V 130 Trunc=130 Size=660 Line=0 Col=1 Alt=0
====>
00000 * * * Top of File * * *
00001 /*---------------------------------------------------------------------+
00002 | Copyright 2007 BMC Software, Inc. All rights reserved.               |
00003 +----------------------------------------------------------------------+
00004 | Configuration parameters for BMC MainView z/VM Data Server           |
00005 +----------------------------------------------------------------------+
00006 | cfg_dsnhilv       : The MVS DSN hi-level qualifier to obtain         |
00007 |                     <dsnhilv>.RPMS (VMARC) files. (Default=BMC.MVLNX)|
00008 | cfg_mvshost       : The MVS host name to obtain VMARC files.         |
00009 | cfg_mvsuser       : The MVS user name to obtain VMARC files.         |
00010 | cfg_rthost        : The MVS host name where the RTServer is running. |
00011 | cfg_rtport        : The port number where the RTServer is listening. |
00012 |                     (Default=5101) |
00013 | cfg_monvend       : The z/VM monitor vendor (B=BMC,I=IBM,V=Velocity) |
00014 |                     (Default=B)                                      |
00015 | cfg_monid         : The CMS userid of the z/VM monitor which you are |
00016 |                     using to collect your monitor data.              |
00017 | (BMC Default=VMMAVMSR) |
00018 | (IBM Default=PERFSVM)      |
00019 | (Vel Default=ESASERVE)                           |
00020 | cfg_vmlinks       : Some z/VM monitors, such as BMC VM Monitor Reader|
00021 | and Velocity Software's ESAMON, require you to   |
00022 | link to their software minidisk for access.      |
00023 | Enter the CMS userid and virtual address for     |
00024 | each minidisk required.                          |
00025 | (BMC default=TCPMAINT:592;VMMAVMSR:191)          |
00026 | (IBM default=TCPMAINT:592;5VMPTK10:201)          |
00027 |(Vel default=TCPMAINT:592;ESAMON:196;ESAMON:198) |
00028 |Configuration parameters for BMC MAINVIEW z/VM Monitor Reader(if used)|
00029 | cfg_mondcss       : The DCSS name for the BMC VM Monitor Reader.     |
00030 |                     (Default=MONDCSS)                                |
00031 +----------------------------------------------------------------------*/
00032 cfg_dsnhilv='BMC.MVLNX'
00033 cfg_mvshost='MVS1'
00034 cfg_mvsuser='MVSUSR1'
00035 cfg_rthost='MVS1'
00036 cfg_rtport='5101'
00037 cfg_monvend='B'
00038 cfg_monid='VMMAVMSR'
00039 cfg_vmlinks='TCPMAINT:592;VMMAVMSR:191'
00040 cfg_mondcss='MONDCSS'
00041 /*---------------------------------------------------------------------+
00042 | Do not change anything below this comment block.                     |
00043 +---------------------------------------------------------------------*/

Use XEDIT to make any changes. After you have verified the configuration parameters, type the following command on the z/VM system to install the data server:

MMLVINST (V

Note

The option V (verbose) allows you to view the installation progress.

See below for an example of output that results from running the mmlvinst installation script.

MMLVINST (V
MMLVINST: FTP latest VMARC files from MVS ...
MMLVINST: Enter TSO password for MVSUSR1 on MVS1, or nothing to exit :DASD
0122 DETACHED
DMSVML2060I TCPMAINT 592 linked as 0122 file mode C
VM TCP/IP FTP Level 540
Connecting to MVS1 172.19.164.166, port 21
220-DC$FTSRV IBM FTP CS V1R7 at mvs1.BMC.COM, 18:18:45 on 2008-09-02.
220 Connection will close if idle for more than 30 minutes.
Using the file: NETRC DATA A
>>>USER MVSUSR1
331 Send password please.
>>>PASS ********
230 MVSUSR1 is logged on. Working directory is "BMC.MVLNX.".
Command:
>>>TYPE a
200 Representation type is Ascii NonPrint
Command:
>>>PORT 172,19,164,203,5,197
200 Port request OK.
>>>RETR 'BMC.MVLNX.BBSAMP(MMLVINST)'
125 Sending data set BMC.MVLNX.BBSAMP(MMLVINST) FIXrecfm 80
250 Transfer completed successfully.
26551 bytes transferred in 0.017 seconds. Transfer rate 1561.82 Kbytes/sec.
Command:
>>>PORT 172,19,164,203,5,198
200 Port request OK.
>>>RETR 'BMC.MVLNX.BBSAMP(MMLVPROF)'
125 Sending data set BMC.MVLNX.BBSAMP(MMLVPROF) FIXrecfm 80
250 Transfer completed successfully.
2003 bytes transferred in 0.002 seconds. Transfer rate 1001.50 Kbytes/sec.
Command:
>>>PORT 172,19,164,203,5,199
200 Port request OK.
>>>RETR 'BMC.MVLNX.BBSAMP(MMLVINI)'
125 Sending data set BMC.MVLNX.BBSAMP(MMLVINI) FIXrecfm 80
250 Transfer completed successfully.
440 bytes transferred in 0.003 seconds. Transfer rate 146.67 Kbytes/sec.
Command:
>>>PORT 172,19,164,203,5,200
200 Port request OK.
>>>RETR 'BMC.MVLNX.BBSAMP(MMLVTEST)'
125 Sending data set BMC.MVLNX.BBSAMP(MMLVTEST) FIXrecfm 80
250 Transfer completed successfully.
1275 bytes transferred in 0.012 seconds. Transfer rate 106.25 Kbytes/sec.
Command:
>>>PORT 172,19,164,203,5,201
200 Port request OK.
>>>RETR 'BMC.MVLNX.UBBSAMP(MMLVPROF)'
550 Request nonexistent member BMC.MVLNX.UBBSAMP(MMLVPROF) to be sent.
Command:
>>>PORT 172,19,164,203,5,202
200 Port request OK.
>>>RETR 'BMC.MVLNX.UBBSAMP(MMLVINI)'       550
Request nonexistent member BMC.MVLNX.UBBSAMP(MMLVINI) to be sent.
Command:
>>>PORT 172,19,164,203,5,203
200 Port request OK.
>>>RETR 'BMC.MVLNX.UBBSAMP(MMLVTEST)' 550
Request nonexistent member BMC.MVLNX.UBBSAMP(MMLVTEST) to be sent.
Command:
>>>PORT 172,19,164,203,5,204
200 Port request OK.
>>>RETR 'BMC.MVLNX.BBSAMP(VMMINST)'
125 Sending data set BMC.MVLNX.BBSAMP(VMMINST) FIXrecfm 80    250
Transfer completed successfully.
17917 bytes transferred in 0.007 seconds. Transfer rate 2559.57 Kbytes/sec.
Command:
>>>PORT 172,19,164,203,5,205
200 Port request OK.
>>>RETR 'BMC.MVLNX.BBSAMP(VMMPROF)'
125 Sending data set BMC.MVLNX.BBSAMP(VMMPROF) FIXrecfm 80        250
Transfer completed successfully.
1825 bytes transferred in 0.003 seconds. Transfer rate 608.33 Kbytes/sec.
Command:
>>>PORT 172,19,164,203,5,206
200 Port request OK.
>>>RETR 'BMC.MVLNX.BBSAMP(VMMCFG)'
125 Sending data set BMC.MVLNX.BBSAMP(VMMCFG) FIXrecfm 80        250
Transfer completed successfully.
371 bytes transferred in 0.049 seconds. Transfer rate 7.57 Kbytes/sec.
Command:
>>>PORT 172,19,164,203,5,207
200 Port request OK.
>>>RETR 'BMC.MVLNX.UBBSAMP(VMMPROF)'        550
Request nonexistent member BMC.MVLNX.UBBSAMP(VMMPROF) to be sent.
Command:
>>>PORT 172,19,164,203,5,208
200 Port request OK.
>>>RETR 'BMC.MVLNX.UBBSAMP(VMMCFG)'        550
Request nonexistent member BMC.MVLNX.UBBSAMP(VMMCFG) to be sent.
Command:
>>>TYPE i
200 Representation type is Image
Command:
>>>PORT 172,19,164,203,5,209
200 Port request OK.
>>>RETR 'BMC.MVLNX.RPMS(MMLUVCMS)'                                                     125
Sending data set BMC.MVLNX.RPMS(MMLUVCMS)                                              250
Transfer completed successfully.
2671360 bytes transferred in 0.584 seconds. Transfer rate 4574.25 Kbytes/sec.
Command:
>>>PORT 172,19,164,203,5,210
200 Port request OK.
>>>RETR 'BMC.MVLNX.RPMS(VMMSVCMS)'                                                     125
Sending data set BMC.MVLNX.RPMS(VMMSVCMS)                                              250
Transfer completed successfully.
370000 bytes transferred in 0.083 seconds. Transfer rate 4457.83 Kbytes/sec.
Command:
>>>QUIT
221 Quit command received. Goodbye.
MMLVINST: Configuring VMMINST EXEC B file from VMMINST EXECSAMP A file.
VMMINST: Removing VMM INSTLIST B file list...
VMMINST: Unpacking VMM VMARC A ...
VMMINST: Copied VMMAVMSR CONFIG B to VMMAVMSR CFGOLD B file.
VMMINST: Configuring VMMAVMSR CONFIG B file from VMMAVMSR CFGSAMP A file.
VMMINST: Configuring PROFILE EXEC B file from VMMPROF EXEC A file.
VMMINST: BMC z/VM Monitor Reader installed.
MMLVINST: Starting BMC z/VM Monitor Reader ...
Command accepted
AUTO LOGON *** VMMAVMSR USERS = 40
HCPCLS6056I XAUTOLOG information for VMMAVMSR: The IPL command is verified by the
IPL command processor.
09/02/08 13:20:54 VMMSRV9565I VM CP Monitor Data Reader (VMMAVMSR) has
initialized.
MMLVINST: Removing MML INSTLIST A file list...
MMLVINST: Unpacking MML VMARC A ....
MMLVINST: Copied MMLVSRV INI A to MMLVSRV INIOLD A file.
MMLVINST: Configuring MMLVSRV INI A file from MMLVSRV INISAMP A file.
MMLVINST: Configuring PROFILE EXEC A file from MMLVPROF EXEC A file.
MMLVINST: Start BMC z/VM Data Server? (y/n)
y
MMLVSRV -L0003
MMLVSRV: z/VM Monitor: VMMAVMSR version: 1.2.00 fixlevel: BPN1131
09/02/08 13:21:13 001 284002 - mml0dcmn: main : MAINVIEW for Linux Data Server
program mmlvsrv is starting - version 1.4.00 fixlevel BPN1202
09/02/08 13:21:13 400 284002 - MMLVMDataManager::initialize :
09/02/08 13:21:13 400 284002 - Data source is VMMAVMSR
09/02/08 13:21:13 400 284017 - MMLCosServerConnectionManager::connect :
09/02/08 13:21:13 400 284017 - Connecting to RTServer on MVS1 port 5101
09/02/08 13:21:13 400 284017 - MMLCosServerConnectionManager::connect :
09/02/08 13:21:13 400 284017 - Connection successful

To verify your installation of the z/VM data server installation

Verify that the MMLVSRV data server has the correct VMLINK connections defined to a supported z/VM monitor by entering a z/VM monitor command from the MMLVSRV user ID.
The following list contains the z/VM monitor command for each of the supported z/VM monitors:
- For the BMC z/VM Monitor Reader, type VMMAVMCL GETVERSN.
- For the Velocity Software monitor, type ESAMON or ZMON.
- For the IBM product Performance Toolkit, type VMCX PERFSVM.
The following example shows a sample of the output you might receive from the VMMAVMCL GETVERSN command for the BMC z/VM Monitor Reader:
Ready; T=0.03/0.03 10:56:40
VMMAVMCL GETVERSN
VMM=1.2.00
PTF=BPN1131
VM=z/VM Version 5 Release 4.0, service level 0801 (64-bit)

VMMRCL9418I GETVERSN completed successfully.
Ready; T=0.02/0.02 11:00:51
To verify that the MMLVSRV data server can connect to the selected z/VM monitor (cfg_monid from the MMLVINST EXEC), enter the following command from the MMLVSRV userid:
MMLAVV20 <cfg_monid>
The following example shows a sample of the output using the default BMC z/VM monitor, VMMAVMSR:
Ready; T=0.02/0.02 11:00:51
MMLAVV20 VMMAVMSR
ietm=1.22459539E+9!clnm=VMMAVMSR !clvr=1.2.00!clfl=BPN1131!
Ready; T=0.01/0.01 11:03:44

Uninstalling the z/VM data server

Type the following command on any z/VM systems where the MMLVINST EXEC script was run:

"MMLVINST (REMOVE"