su to root, make sure VCC has shut down and install the VCC gmcstars support by issuing:

The installation script will install the necessary files in the proper directories.

Verify that the snmptrapd daemon is running by issuing:

pgrep should respond with snmptrapd's pid.

Exit root authority by issuing:

Log in to VCC and use the VCC Main Window Administration → Configuration → System to modify your system configuration.

1. If you are currently running WATCHMVS as your MVS agent, change the entries for all MVS OSs that will be running GMCSTARS by deleting the

   mvsagent=agent
   

   line.

2. If you are currently running WATCHMVS, change the version of all MVSAgents that will be running GMCSTARS to

   version=3
   

   If you are not running WATCHMVS, add an MVSAgent entry for every MVS LPAR that will be running GMCSTARS. The entries should look like:

   Figure 3.3. Sample MVSAgent Clause

   [MVSAgent mvs-system]
   number=390
   password=0x0123456789abcdef
   version=3
   release=1
   retrytime=30
   ipaddress=system-IP-address
   ipport=2769
   networkdelay=60
   

   Where “mvs-system” is the MVS system name you want indicated as the source on any alerts created. system-IP-address is the dotted IP address, hostname or fully qualified domain name of the MVS system.

   At this point in time there may be warnings issued by the VCC configuration checker that version=3 is an unknown version. Ignore them.

Use the VCC Main Window Administration → Shutdown… to stop VCC.

Start vcc, by issuing:

or issuing

as a vcc user.

Login as vcc or su to vcc.

Use the VCC Main Window Script → Execute to start the gmcstars.scx script. Only one copy of the script can be run on each VCC Linux server.

If you are an existing watchMVS user, please refer to the Administration section of this guide about migrating your existing customizations to GMCSTARS.