Using manual customization

This topic describes how to manually perform the customization steps for MainView for Linux — Servers.

Following table summarizes the data set member names containing the sample JCL that is included on the tape and the corresponding customization step. These JCL samples are located in the BBPARM and the BBSAMP data sets on the tape.

Summary of BBPARM and BBSAMP JCL data sets and corresponding manual customization step

Task

Description

Data set member

Data set

1

Customize the BMC AMI Ops online environment.

N/A

N/A

2

Create the RTSERVER JCL startup procedure.

RTSRVJCL

BBSAMP

3

Customize the RTSERVER command parameters member.

RTSRVCM

STDCM

4

Create the MainView for Linux — Servers PAS SYSIN data set.

MMLPRM00

BBPARM

5

Create MainView for Linux — Servers PAS image data set.

MMLIMG

BBSAMP

6

Create MainView for Linux — Servers Rules data set.

MMLRUL

BBSAMP

7

Create the MainView for Linux — Servers history data set.

MMLHST

BBSAMP

8

Create the MainView for Linux — Servers PAS startup procedure.

MMLPAS

BBSAMP

9

Customize the MainView for Linux — Servers data server installation script.

MMLDINST

BBSAMP

10

Create MainView for Linux — Servers job to FTP data server installation script to a Linux system.

MMLFTP

BBSAMP

11

Create MainView for Linux — Servers job to FTP z/VM data server installation script.

MMLVINST

BBSAMP

12

Create MainView for Linux - Servers job to FTP z/VM installation script to a z/VM system.

MMLFTPVM

BBSAMP

Task 1— Customizing the BMC AMI Ops online environment

Refer to Customizing after installation.

Note

Because of library allocations, MainView for Linux — Servers manual customization cannot be performed until you have completed manual customization for the BMC AMI Ops online environment

Task 2 — Creating the RTSERVER JCL startup procedure

The RTServer is the communication server for MainView for Linux — Servers. The RTServer startup procedure creates the startup task for the communication server for MainView for Linux — Servers

A sample RTSERVER JCL startup procedure is provided with the distribution tape in member hilevel.BBSAMP(RTSRVJCL).

To create the RTSERVER JCL startup procedure

  1. Select hilevel.BBSAMP member RTSRVJCL.

    //*---------------------------------------------------------------------
    //* RTSERVER STARTED TASK
    //*Change Log:
    //*
    //*   Created by ?USER on ?DATE at ?TIME
    //* BPN0125 Add RTTIMESTAMPOUTPUT parm to put time on messagesJMW
    //*
    //*--------------------------------------------------------------------

    //RTSERVER PROC HLQ='BB.XTST1',
    //  PRM='',
    //  ENV='=RTHOME=BB.XTST1'
    //*
    //RTSERVER EXEC PGM=RTSERVER,TIME=1440,REGION=0M,
    //PARM='&PRM &ENV =RTTIMESTAMPOUTPUT=1'
    //*
    //STEPLIBDD DISP=SHR,DSN=&HLQ..PGMLIB
    //DD DISP=SHR,DSN=&HLQ..BBLINK
    //RTSLIB DD DISP=SHR,DSN=&HLQ..PGMLIB //MSGFILE
    DD DISP=SHR,DSN=&HLQ..STDTXT(MESSAGE) //*
    //SYSTERMDD SYSOUT=*,DCB=(RECFM=VBA,LRECL=137)
    //SYSPRINT DD SYSOUT=*,DCB=(RECFM=VBA,LRECL=137)
    //STDOUTDD SYSOUT=*,DCB=(RECFM=VBA,LRECL=137)
    //STDERRDD SYSOUT=*,DCB=(RECFM=VBA,LRECL=137)
    //SRVOUTDD SYSOUT=*,DCB=(RECFM=VBA,LRECL=137)
    //RTSERVER DD SYSOUT=*,DCB=(RECFM=VBA,LRECL=137)

    ******************************** Bottom of Data *************************
  2. Copy the member to hilevel.UBBSAMP.
  3. Change ?BBCHILV to the high-level qualifier of the product libraries.

  4. Change ?RTHOME to a high-level qualifier, such as MVLNX.RTHOME (rthome).

    Note

    The ?RTHOME high-level qualifier can be a maximum of two levels. The RTServer uses this high-level qualifier to find the run-time data sets.

  5. Allocate two new data sets at the rthome high-level qualifier:
    • rthome.STANDARD.CM
    • rthome.STANDARD.TXT
  6. Copy all members from hilevel.STDCM to rthome.STANDARD.CM.
  7. Copy all members from hilevel.STDTXT to rthome.STANDARD.TXT.
  8. In hilevel.STANDARD.CM, rename RTSRVCM member to RTSERVER.
  9. Edit the rthome.STANDARD.CM data set TCPNAME member to contain the name of the TCP/IP address space.
  10. Copy hilevel.UBBSAMP data set member RTSRVJCL to your system procedure library as RTSERVER.
  11. To start the procedure automatically when you IPL the system, add the RTSERVER procedure to your system startup parameter library, for example, SYS1.PARMLIB(COMMNDxx).

Task 3—Customizing the RTServer command parameters member

The RTServer is the communication server for MainView for Linux – Servers. This task is only required if port 5101 is in use, and you must specify an unused port number.

Before you begin

A sample RTServer command parameters member is provided with the distribution tape in member hilevel.STDCM (RTSRVCM). This member was copied to rthome.STANDARD.CM(RTSERVER) in Task 2 — Creating the RTSERVER JCL startup procedure.

Note

RTServer program libraries require APF authorization. RTServer started task requires RACF OMVS authorization for using TCP/IP. If you have an External Security Manager (ESM) other than RACF, consult the product documentation for information about this requirement.

  1. Select rthome.STANDARD.CM member RTSERVER.

    ************************* Top of Data ***************************
    setopt default_protocols tcp
    setopt conn_names tcp
    setopt server_names UNKNOWN
    setopt max_client_conns 512
    setopt conn_names tcp:_node:5101
    ************************ Bottom of Data *************************
  2. Change 5101 to a port number that is not in use.
  3. Save the member.

Task 4—Creating the MainView for Linux — Servers product address space (PAS) SYSIN member

In this task, you will provide the PAS startup parameters.

To customize MainView for Linux — Servers, you must specify the following information:

  • network host name of the communication server (RTServer)
  • port number of the communication server (RTServer)
  • CAS subsystem ID
  • PAS subsystem ID
  • member name of the of the UBBPARM data set where this information is saved

    Following table describes the parameters for the information that you must provide.

PAS SYSIN parameters

Parameter keyword

Description

Parameter values

Default

SUBSYSID

PAS subsystem ID

4-character (alphanumeric)

This value must be unique; it cannot be the same as the CAS.

MML0

SUBSTR

specifies how to derive the image name from the host name

The host name can be many characters in length, but the image name is restricted to only 8 characters. This parameter specifies how the image name is derived from the host name.

1st position
numeric value of 1–60 that indicates where to start scanning in the host name

(1,8,B)

2nd position

numeric value of 1–8 that indicates the length of the image target name

3rd position
B indicates start scanning from the beginning of the host name
E indicates start scanning from the end of the host name

RTHOST

network host name that is running the RTServer

host name or IP address

NA

RTPORT

network port number on which the RTServer is listening

5101

SSID

CAS Subsystem ID

4-character (alphanumeric)

This value must be unique; it cannot be same as PAS.

BBCS

LOGLEVEL

level of PAS communication subtask information logging

100 provides severe messages

400

200 provides error and severe messages

300 provides warning, error, and severe messages

400 provides informational, warning, error, and severe messages

MXCMMWT

maximum amount of delay time when refreshing a view

numeric value (in milliseconds)

1000


To create the MainView for Linux — Servers PAS SYSIN member 

  1. Select hilevel.BBPARM member MMLPRM00.

    *------------------------------------------------------------------
    - * Change Log:
    *Created by ?USER on ?DATE at ?TIME
    *-------------------------------------------------------------------
    SUBSYSID=?PASSSID,PAS subsystem name (default=MML0)
    SUBSTR=(1,8,B),How to form image names from host names
    RTHOST=?HOST,RTServer host name
    RTPORT=?PORT,RTServer port number
    SSID=?BBCS,CAS subsystem id to connect to
    LOGLEVEL=400,Communication sub-task logging level
    MXCOMMWT=1000,Communication sub-task max wait (ms)
    ENDEnd configuration parameters
    ************************** Bottom of Data **************************
  2. Copy the member to hilevel.UBBPARM.

  3. Verify that SUBSTR=(1,8,B) will work in your environment.
    The SUBSTR parameter identifies how you want to specify your image names. The host names can be many characters in length; however the image names are limited to eight characters. You can specify the image name starting from any character in the character string. The default, (1,8,B), should work in most environments; however, if you have a naming convention where the unique characters are at the end of the character string, and the character string is longer than eight characters, you may want to specify the last characters as the image name.

    For example, your environment could have the following Linux host names:

    • ABCCOMPANYLINUX010
    • ABCCOMPANYLINUX123

    • ABCCOMPANYLINUX965

      Following table describes some of the different image names that are possible if you have a host name of ABCCOMPANYLINUX010.

    Host name

    SUBSTR=

    Image name

    ABCCOMPANYLINUX010

    (1,8,B)

    ABCCOMPA

    ABCCOMPANYLINUX010

    (6,4,E)

    NUX0

    ABCCOMPANYLINUX010

    (8,8,E)

    LINUX010

    ABCCOMPANYLINUX010

    (9,8,B)

    NYLINUX0

  4. Change ?PASSSID to the PAS subsystem ID (MML0).

  5. Change ?HOST to the host name or IP address of the system running the RTServer.

    If you are running the RTServer and the MainView for Linux - Servers PAS on the same host, you can change ?HOST to localhost or 127.0.0.1.

  6. Change ?PORT to 5101 (the port number of the RTServer).

    Note

    The value that you enter for the ?PORT number must match the port number that you entered in step 2 for Task 3—Customizing the RTServer command parameters member

  7. Change ?BBCS to the CAS subsystem ID (default=BBCS).

Task 5—Allocating the MainView for Linux — Servers image data set

In this task, you will allocate the MainView for Linux — Servers image data set. This data set contains information about automatically discovered Linux systems.

To customize the MainView for Linux — Servers data server installation script

  1. Select hilevel.BBSAMP member MMLDINST.

    //*-----------------------------------------------------------------
    //*   Change log:
    //*         Created by ?USER on ?DATE at ?TIME
    //*-----------------------------------------------------------------
    //IEFBR14 EXEC  PGM=IEFBR14
    //DELETE   DD   DISP=(MOD,DELETE),
    //              DSN=?BBCHILV.MML.?PASSSID.IMAGE,
    //              SPACE=(TRK,0)
    //*-----------------------------------------------------------------
    //* Write a single blank line to the dataset
    //*-----------------------------------------------------------------
    //IEBGENER EXEC PGM=IEBGENER
    //SYSPRINT DD   SYSOUT=*
    //SYSUT2   DD   DISP=(NEW,CATLG),
    //              DSN=?BBCHILV.MML.?PASSSID.IMAGE,
    //              DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120,DSORG=PS),
    //              UNIT=SYSDA,SPACE=(TRK,(2,1)),VOL=SER=?BBVOL
    //SYSIN DD       *
      GENERATE MAXFLDS=2
      RECORD FIELD=(40,1,,1),FIELD=(40,1,,41)
    //SYSUT1 DD    *
    ************************** Bottom of Data **************************
  2. Copy the member to hilevel.UBBSAMP.
  3. Edit the JOB statement to specify the appropriate system parameters. 
  4. Change ?BBCHILV to the high-level qualifier of the product libraries.
  5. Change ?PASSSID to the PAS subsystem ID (MML0). 

  6. Change ?BBVOL to a specific DASD volume.

    Note

    If you do not want the DASD to run on a specific volume, you can remove the VOL=SER=?BBVOL statement.

  7. Submit the JCL to run the job and allocate the data sets.

Task 6—Allocating the MainView for Linux — Servers rules data set

In this task, you will allocate the MainView for Linux — Servers monitor rules data set.

  1. Select hilevel.BBSAMP member MMLRUL.

    //*-----------------------------------------------------------------
    //*   Change log:
    //*          Created by ?USER on ?DATE at ?TIME
    //*-----------------------------------------------------------------
    //IEFBR14  EXEC PGM=IEFBR14
    //DELETE    DD  DISP=(MOD,DELETE),DSN=?BBCHILV.MML.DATA,
    //              SPACE=(TRK,0)
    //*-----------------------------------------------------------------
    //ALLOCDS EXEC PGM=IEFBR14
    //SYSUT2   DD  DISP=(NEW,CATLG),DSN=?BBCHILV.MML.DATA,
    //            DCB=(RECFM=FB,LRECL=512,BLKSIZE=30720,DSORG=PO),
    //            UNIT=SYSDA,SPACE=(TRK,(5,1,5)),VOL=SER=?BBVOL
    /*
    ************************** Bottom of Data **************************
  2. Copy the member to hilevel.UBBSAMP.
  3. Edit the JOB statement to specify the appropriate system parameters. 
  4. Change ?BBCHILV to the high-level qualifier of the product libraries.

  5. Change ?BBVOL to a specific DASD volume. 

    If you do not want the DASD to run on a specific volume, you can remove the VOL=SER=?BBVOL statement.

  6. Submit the JCL to run the job and allocate the data set.

Task 7—Allocating the MainView for Linux — Servers history data set

In this task, you will create the data set that contains the output from the historical data recorder.

  1. Select hilevel.BBSAMP member MMLHST.

    //*-----------------------------------------------------------------
    //*   Change log:
    //*          Created by ?USER on ?DATE at ?TIME
    //*-----------------------------------------------------------------
    //DELETE     EXEC PGM=IDCAMS,REGION=4M
    //SYSPRINT   DD   SYSOUT=*
    //SYSIN      DD   *
       DELETE     ?MMLVHLQ.?MMLPASID.HISTDS00 -
                         PURGE
       DELETE     ?MMLVHLQ.?MMLPASID.HISTDS01 -
                         PURGE
       DELETE     ?MMLVHLQ.?MMLPASID.HISTDS02 -
                         PURGE
       SET MAXCC=0
    //*
    //*
    //DEFINE   EXEC PGM=IDCAMS,REGION=4M
    //SYSPRINT DD   SYSOUT=*
    //SYSIN    DD   *
     DEFINE  CLUSTER (NAME(?MMLVHLQ.?MMLPASID.HISTDS00) -
                     RECORDSIZE(4200 32000) -
                     VOLUMES(?VOLUME) -
                     KEYS(28 24) -
                     SHR(3,3) -
                     REUSE) -
            DATA -
                   (NAME(?MMLVHLQ.?MMLPASID.HISTDS00.DATA) -
                   CYLINDERS(?CYL)) -
           INDEX -
                   (NAME(?MMLVHLQ.?MMLPASID.HISTDS00.INDX) -
    CISZ(4096) -
     CYLINDERS(1))

     DEFINE CLUSTER (NAME(?MMLVHLQ.?MMLPASID.HISTDS01) -
     RECORDSIZE(4200 32000) -
     VOLUMES(?VOLUME) -
     KEYS(28 24) -
     SHR(3,3) -
     REUSE) -
     DATA -
     (NAME(?MMLVHLQ.?MMLPASID.HISTDS01.DATA) -
         CYLINDERS(?CYL)) -
     INDEX -
     (NAME(?MMLVHLQ.?MMLPASID.HISTDS01.INDX) -
     CISZ(4096) -
     CYLINDERS(1))
     /*
     //*
     //SEED    EXEC PGM=IDCAMS,REGION=4M
     //SYSPRINT DD SYSOUT=*
     //IN       DD DISP=SHR,DSN=?BBCHILV.BBILIB(@@YZZ052)
     //SYSIN    DD *
        REPRO  INFILE   (IN) -
               OUTDATASET(?MMLVHLQ.?MMLPASID.HISTDS00)
        REPRO  INFILE (IN) -
               OUTDATASET(?MMLVHLQ.?MMLPASID.HISTDS01)
        REPRO INFILE (IN) -
     OUTDATASET(?MMLVHLQ.?MMLPASID.HISTDS02)
     /*
    //
    ************************* Bottom of Data **************************
  2. Copy the member to hilevel.UBBSAMP.
  3. Edit the JOB statement to specify the appropriate system parameters. 

  4. Change ?MMLVHLQ to the high-level qualifier of the VSAM data sets you create for MainView for Linux — Servers.

    Note

    You can make ?MMLVHLQ the same value as ?BBCHILV.

  5. Change ?MMLPASID to the name of the PAS subsystem ID that was created in a previous task. See Task 3—Customizing the RTServer command parameters member for more information.
  6. Submit the JCL to run the job and allocate the data set.

History interval

If you have allocated the historical data sets, historical reporting begins as soon as the PAS is initialized. Data is recorded at the interval that is specified in the hilevel.BBPARM data set member MMLTIR00. The default length of the recording interval is 15 minutes.

Intervals are usually synchronized on the hour (SYNCVAL=0). For example, if the interval value (INTVAL) is specified as 15 minutes and extraction begins at 09:49 A.M., the first interval lasts 11 minutes until 10:00 A.M. Successive intervals are 10:00 to 10:15, 10:15 to 10:30, and so on.

A sample of the MMLTIR00 is shown below.

<INTERVAL INTVAL="15" SYNCVAL="0"/>

Task 8—Creating the MainView for Linux — Servers product address space (PAS) JCL startup procedure

In this task, you will create the MainView for Linux — Servers PAS startup procedure.

To run the MainView for Linux — Servers PAS, you must create a procedure in your system procedure library.

Note

The PAS program library requires APF authorization. The PAS started task requires RACF OMVS authorization for using TCP/IP.

To customize the MainView for Linux — Servers PAS JCL startup procedure

  1. Select hilevel.BBSAMP member MMLPAS.

     //*----------------------------------------------------------------
     //*  Change Log:
     //*        Created by ?USER on ?DATE at ?TIME
     //*----------------------------------------------------------------
     //*  Note: Any region size greater than 16MB and less than
     //*  32MB, causes MVS to make available all storage below
     //* the 16MB line and 32MB of storage (the IBM default)
     //* above the line.
     //*----------------------------------------------------------------
     //MMLPAS   PROC  REG=46,
     //    BBCHILV='?BBCHILV',
     //            BBLINK='?BBLINK',
     //            UBBPARM='?UBBPARM',
     //            PASID='?MMLPASID',
     //            MMLSYSIN='?MMLPRM',
     //            MMLIMAGE='?MMLIMG',
     //            MMLRULES='?MMLRUL',
     //            MMLVHLQ='?MMLVHLQ'
     //*----------------------------------------------------------------
     //MML9DSP4 EXEC PGM=MML9DSP4,REGION=&REG.M
     //*
     //STEPLIB  DD  DISP=SHR,DSN=&BBLINK
     //BBILINK  DD  DISP=SHR,DSN=&BBLINK
     //*
     //* Action definition tables.
     //*
     //BBACTDEF DD DISP=SHR,DSN=&BBCHILV..BBACTDEF
     //*
     //* View definitions.
     //*
     //BBVDEF   DD DISP=SHR,DSN=&BBCHILV..BBVDEF
     //*
     //* Parameter definitions.
     //*
     //BBIPARM  DD DISP=SHR,DSN=&UBBPARM
     //         DD DISP=SHR,DSN=&BBCHILV..BBPARM
     //*
     //* Customized security definitions.
     //*
     //BBSECURE DD DISP=SHR,DSN=&BBCHILV..BBSECURE
     //*
     //* History file definitions (need unique DSNames per PAS)
     //* &PASID can be the same value used for SUBSYSID= in SYSIN.
     //*
     //HISTDS00 DD DISP=SHR,DSN=&MMLVHLQ..&PASID..HISTDS00
     //HISTDS01 DD DISP=SHR,DSN=&MMLVHLQ..&PASID..HISTDS01
     //HISTDS02 DD DISP=SHR,DSN=&MMLVHLQ..&PASID..HISTDS02
     //*
     //* Product license password.
     //*
     //BMCPSWD  DD DISP=SHR,DSN=&BBCHILV..BMCPSWD
     //*
     //* Product input parameters.
     //*
     //SYSIN    DD DISP=SHR,DSN=&UBBPARM(&MMLSYSIN)
     //*
     //* Automatically discovered systems
     //*
     //MMLIMAGE DD DISP=SHR,DSN=&MMLIMAGE
     //*
     //* Monitor rules.
     //*
     //MMLDATA  DD DISP=SHR,DSN=&MMLRULES
     //*
     //* Communication Sub-task message log
     //*
     //MMLERRLG DD SYSOUT=*
     //*
     //* History Sub-task message log
     //*
     //MMLHERLG DD SYSOUT=*
     //*
     //SYSUDUMP DD SYSOUT=*
     //SYSTERM  DD SYSOUT=*
     //STDOUT   DD SYSOUT=*
     //SYSOUT   DD SYSOUT=*
     //SYSPRINT DD SYSOUT=*
    ************************* Bottom of Data **************************
  2. Copy the member to hilevel.UBBSAMP.
  3. Change ?BBCHILV to the high-level qualifier of the MainView for Linux — Servers product libraries.
  4. Change ?UBBPARM to data set name hilevel.UBBPARM (see step 1 of To create the MainView for Linux — Servers PAS SYSIN member).
  5. Change ?BBLINK to hilevel.BBLINK.
  6. Change ?MMLPRM to MMLPRM00, (see step 2 of To create the MainView for Linux — Servers PAS SYSIN member).
  7. Change ?MMLIMG to the image data set name (hilevel.MML.passsid.IMAGE) that you allocated in a previous task. See Task 5—Allocating the MainView for Linux — Servers image data set for more information.
  8. Change ?MMLRULE to the rules data set name (hilevel.MML.DATA) that you allocated in Task 6—Allocating the MainView for Linux — Servers rules data set.

  9. Change ?MMLVHLQ to the high-level qualifier of the VSAM data sets that you created for MainView for Linux — Servers (see Task 7—Allocating the MainView for Linux — Servers history data set).

    Note

    You can make ?MMLVHLQ the same value as ?BBCHILV.

  10. Copy the MMLPAS member to your system procedure library.
  11. To start the procedure automatically when you IPL the system, add the MMLPAS procedure to your system startup parameter library, for example, SYS1.PARMLIB(COMMNDxx).

Task 9—Customizing the MainView for Linux — Servers Linux data server installation script

In this task, you will customize the MainView for Linux — Servers data server installation script that runs on a Linux system.

To customize the MainView for Linux — Servers data server installation script

  1. Select hilevel.BBSAMP member MMLDINST.

    000002 #------------------------------------------------------------
    000003 # Configuration parameters for MAINVIEW for Linux Data Server
    000004 #------------------------------------------------------------
    000005 # DSNHILV : The MVS DSN hi-level qualifier to obtain
    000006 # <DSNHILV>.RPMS files. (Default=BMC.MVLNX)
    000007 # MVSHOST : The MVS host name to obtain RPMS files.
    000008 # MVSUSER : The MVS user name to obtain RPMS files.
    000009 # RTHOST  : The MVS host name where the RTServer is running.
    000010 # RTPORT  : The port number where the RTServer is listening.
    000011 #    (Default=5101)
    000012 # DSUSER  : The MML data server user name to run under.
    000013 #    (Default=mmldusr)
    000014 # DCVEND  : The data collecter vendor (B=BMC,V=Velocity)
    000015 #    (Default=B)
    000016 #------------------------------------------------------------
    000017 DSNHILV=?DSNHILV
    000018 MVSHOST=?MVSHOST
    000019 MVSUSER=?MVSUSER
    000020 RTHOST=?RTHOST
    000021 RTPORT=?RTPORT
    000022 DSUSER=?DSUSER
    000023 DCVEND=?DCVEND
    000024 #------------------------------------------------------------
    000025 # Do not change anything below this comment block.
    000026 #------------------------------------------------------------
  2. Copy the member to hilevel.UBBSAMP.
  3. Change ?DSNHILV to the DSN high-level qualifier for RPMS data set (default=BMC.MVLNX).
  4. To FTP the RPMS data set files, make the following changes:
    1. Change ?MVSHOST to MVS host name.
    2. Change ?MVSUSER to MVS user name.
  5. Change ?RTHOST to the RTServer host name.
  6. Change ?RTPORT to the RTServer port number (default=5101).

  7. Change ?DSUSER to an existing nonroot Linux user name.

    The default ?DSUSER value is mmldusr. If mmldusr does not already exist, the installation process creates it by using the useradd mmldusr Linux command. BMC Performance Assurance Data Collector (bgscollect) product, version 7.4 and later, is installed by using the ?DSUSER user name, and the user name must be specified as a nonroot name.

    When the mmldsrv program is started during system bootup from the root user account, the program switches to the ?DSUSER user name and starts the bgscollect program if the data collector vendor is BMC. Note that the mmldusr does not need an associated password or home directory because the mmldsrv program is always started from root.

    If you do not specify an existing nonroot user name, you might want to run the useradd mmldusr Linux command before running the mmldinst script in case you need to override any of the defaults that are specified in the /etc/default/useradd file.

  8. Change ?DCVEND to the Linux data collector vendor (default=BMC).

    If Velocity is selected, the BMC Performance Assurance Data Collector (bgscollect) product is not installed and will not be started when the mmldsrv program runs.

Task 10—Creating a job to FTP the Linux data server installation files

In this task, you will FTP the data server installation script to a Linux system.

  1. Select hilevel.BBSAMP member MMLFTP.

    *-------------------------------------------------------------------
    //*
    //*    Change log:
    //*
    //*          Created by ?USER on ?DATE at ?TIME
    //*
    //*    NOTE:
    //*      If this job fails because the linux FTP server is not running
    or
    //* allowed, an alternate method is to run ftp get command from the
    //* linux machine. Here's an example of a linux ftp session to get
    the
    //* install file from the MVS UBBSAMP dataset:
    //*
    //* # cd /tmp
    //* # ftp ?MVSHOST
    //* Name: <mvs_username>
    //* Password: <mvs_password>
    //* ftp> ascii
    //* ftp> cd '?DSNHILV.UBBSAMP'
    //* ftp> get MMLDINST mmldinst
    //* ftp> quit
    //* # chmod 755 mmldinst
    //*
    //*-----------------------------------------------------------------
    //STEP1    EXEC PGM=FTP,PARM='(EXIT',REGION=2048K
    //SYSPRINT DD SYSOUT=*
    //OUTPUT   DD SYSOUT=*
    //INPUT    DD *
    ?LNXHOST
    ?USERNAME
    ?PASSWORD
    TYPE A
    cd /tmp
    LCD '?DSNHILV.UBBSAMP'
    PUT MMLDINST mmldinst
    SITE chmod 755 mmldinst
    QUIT
    /*
    /************************* Bottom of Data **************************
  2. Copy the member to hilevel.UBBSAMP.
  3. Change ?DSNHILV to the high-level qualifier of the product libraries.
  4. Change ?LNXHOST to the host name of the Linux system where you will install the data server.
  5. Change ?USERNAME to a valid logon ID of the Linux system.
  6. Change ?PASSWORD to the password of the logon ID that you entered in step 5.
  7. Submit the JCL to run the job and FTP the files to the Linux system.
  8. Repeat step 4 through step 7 to send the files to other Linux systems (if necessary). For more information, see Installing-the-data-server-on-a-Linux-system.

Task 11—Customizing the MainView for Linux — Servers z/VM data server installation script

In this task, you will customize the MainView for Linux — Servers z/VM data server installation script that runs on a z/VM system.

  1. Select hilevel.BBSAMP member MMLVINST.

    000003 +----------------------------------------------------------------------+
    000004 | Configuration parameters for BMC MainView z/VM Data Server           |
    000005 +----------------------------------------------------------------------+
    000006 | cfg_dsnhilv     :   The MVS DSN hi-level qualifier to obtain         |
    000007 |  <dsnhilv>.RPMS (VMARC) files. (Default=BMC.MVLNX)|
    000008 | cfg_mvshost     :   The MVS host name to obtain VMARC files.         |
    000009 | cfg_mvsuser     :   The MVS user name to obtain VMARC files.         |
    000010 | cfg_rthost      :   The MVS host name where the RTServer is running. |
    000011 | cfg_rtport      :   The port number where the RTServer is listening. |
    000012 |                     (Default=5101)   |
    000013 | cfg_monvend     :   The z/VM monitor vendor (B=BMC,I=IBM,V=Velocity) |
    000014 |                     (Default=B)                                      |
    000015 | cfg_monid       :   The CMS userid of the z/VM monitor which you are |
    000016 |                     using to collect your monitor data.              |
    000017 |                     (BMC Default=VMMAVMSR)                           |
    000018 |                     (IBM Default=PERFSVM)                            |
    000019 |                     (Vel Default=ESASERVE)                           |
    000020 | cfg_vmlinks     :   Some z/VM monitors, such as BMC VM Monitor Reader|
    000021 |                     and Velocity Software's ESAMON, require you to   |
    000022 |                     link to their software minidisk for access.      |
    000023 |                     Enter the CMS userid and virtual address for     |
    000024 |                     each minidisk required.                          |
    000025 |                     (BMC default=TCPMAINT:592;VMMAVMSR:191)          |
    000026 |                     (IBM default=TCPMAINT:592;5VMPTK10:201)          |
    000027 |                     (Vel default=TCPMAINT:592;ESAMON:196;ESAMON:198) |
    000028 | Configuration parameters for BMC MAINVIEW VM Monitor Reader(if used) |
    000029 | cfg_mondcss     :   The DCSS name for the BMC z/VM Monitor Reader.   |
    000030 |                     (Default=MONDCSS)                                |
    000031 +---------------------------------------------------------------------*/
    000032 cfg_dsnhilv='?DSNHILV'
    000033 cfg_mvshost='?MVSHOST'
    000034 cfg_mvsuser='?MVSUSER'
    000035 cfg_rthost='?RTHOST'
    000036 cfg_rtport='?RTPORT'
    000037 cfg_monvend='?MONVEND'
    000038 cfg_monid='?MONID'
    000039 cfg_vmlinks='?VMLINKS'
    000040 cfg_mondcss='?MONDCSS'
    000041 /*---------------------------------------------------------------------+
    000042 | Do not change anything below this comment block.                     |
    000043 +---------------------------------------------------------------------*/
  2. Copy the member to hilevel.UBBSAMP.
  3. Change ?DSNHILV to the DSN high-level qualifier for RPMS data set (default=BMC.MVLNX).
  4. To FTP the VMARC files, make the following changes:
    1. Change ?MVSHOST to MVS host name. 
    2. Change ?MVSUSER to MVS user name.
  5. Change ?RTHOST to the RTServer host name.
  6. Change ?RTPORT to the RTServer port number (default=5101).
  7. Change ?MONVEND to the z/VM monitor vendor.
    You can specify one of the following possible values: 
    • B (the default) specifies that the BMC z/VM Monitor Reader is installed.
    • I specifies that the Performance Toolkit by IBM is installed.
    • V specifies that the ESAMON or zMON products by Velocity Software are installed.

      For information about installing the IBM Performance ToolKit product or the Velocity Software ESAMON or z/MON product, refer to the documentation for those products.
  8. Change ?MONID to the CMS userid of the z/VM monitor (default=VMMAVMSR).
  9. Change ?VMLINKS to the CMS userid and virtual address for each required minidisk:

    (BMC_default=TCPMAINT:592;VMMAVMSR:191
    IBM_default=TCPMAINT:592;5VMPTK10:201
    Velocity_default=TCPMAINT:592;ESAMON:196;ESAMON:198)

  10. Change ?MONDCSS to the DCSS name for the BMC z/VM Monitor Reader (default=MONDCSS).

Task 12—Creating a job to FTP the z/VM installation files

In this task, you will create JCL to FTP the z/VM installation files to a z/VM system at a later time.

  1. Select hilevel.BBSAMP member MMLFTPVM.

    //*-----------------------------------------------------------------
    //* Change log:
    //* Created by ?USER on ?DATE at ?TIME
    //*
    //* NOTE:
    //*  If this job fails because the FTP server is not running or
    //* allowed, an alternate method is to run ftp get command from the
    //* z/VM userid. Here's an example of a VM ftp session to get the
    //* install file from the MVS UBBSAMP dataset:
    //*
    //* Ready;
    //* ftp ?MVSHOST
    //* USER: ?MVSUSER
    //* Password: <mvs_password>
    //* Command: type e
    //* Command: mode b
    //* Command: cd '?DSNHILV.UBBSAMP'
    //* Command: get MMLVINST mmlvinst.exec.a
    //* Command: quit
    //*
    //*----------------------------------------------------------------
    //STEP1    EXEC PGM=FTP,PARM='(EXIT',REGION=2048K
    //SYSPRINT DD SYSOUT=*
    //OUTPUT   DD SYSOUT=*
    //INPUT    DD *
    ?ZVMHOST
    ?USERNAME
    ?PASSWORD
    TYPE E
    MODE B
    ACCT ?DISKPASS
    LCD '?DSNHILV.UBBSAMP'
    PUT MMLVINST mmlvinst.exec.a
    QUIT
    /*
    ***************************** Bottom of Data **********************
  2. Copy the member to hilevel.UBBSAMP.
  3. Change ?DSNHILV to the DSN high-level qualifier for UBBSAMP data set. (default=BMC.MVLNX).
  4. Change ?ZVMHOST to the host name of the z/VM data server.
  5. Change ?USERNAME to MMLVSRV.
  6. Change ?PASSWORD to the valid password of the BMC z/VM data server virtual machine.

  7. Save the JCL member.

    Note

    You will need to submit the job after you create the MMLVSRV data server userid on z/VM (see Installing-the-data-server-on-a-z-VM-system).

After performing manual customization, This describes additional tasks that you need to perform:

Task

Component

See

installing and customizing a data server
on a Linux system

Linux data server

installing and customizing a data server
on a Virtual Machine (z/VM)

z/VM data server

Related topic

Customizing-after-installation

 

  • 1.5
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*