Manual customization
This topic describes the tasks for customizing the MainView environment manually. You can also use this information as a reference when configuring MainView products during installation.
You can use manual customization for all MainView products and MainView Infrastructure, which includes MainView Alarm Management, Alert Manager, and MainView Logger.
Note
During installation, you select whether to use runtime libraries or SMP/E libraries. If you use runtime libraries, your customized library names will start with BMC. If you use SMP/E libraries, your customized library names will start with BB, UBB, or TOSZ. A few library names start with IBB or SBB for runtime or SMP/E libraries. For a list of data set names, see Product library customization summary.
The documentation uses the BB*, UBB*, and TOSZ* data set names, but your names might start with BMC*.
This section contains the following topics:
- Overview of manual customization tasks
- Specifying jobcards and other operational defaults
- Generating JCL to run the installation verification program
- Implementing Katakana terminal support
- Apply passwords with the Product Authorization Utility
- Creating site data sets
- Creating site security data set
- Adding the BMC load library to your system APF list
- Adding the BMC load library to your system link list
- Creating a CLIST for invoking MainView products
- Adding TSF authorization for products to run under ISPF
- Configure RTCS
- Creating the CAS startup procedure
- Allocating the CASPERM registry data set
- Creating the MainView host server startup procedure
- Allocating the MainView Infrastructure common registry
- Defining Alert Manager initialization parameters
- Allocating Alert Manager journal logs
- Allocating Alert Manager DIV data set
- Creating an Alert Manager startup procedure
- Verification of MainView Logger data sets
- Creating MainView Logger BBPARM member LOGGERxx
- Creating MainView Logger BBPARM member MVINGIxx
- Creating the started task for the DBC address space
- Defining Next Generation Logger and Logger agents
- Setting up a product-specific logspace
- Allocating historical data set BBILIB member @@YZZ051
- Creating a z/OS PAS PARMFILE data set
- Creating the z/OS PAS startup procedure
- Creating a BBI-SS PAS PARMFILE data set
- Defining BBI-SS PAS suffixes and target system parameters
- Defining configuration members to BBI-SS PAS
- Defining BBI-SS PAS interval services parameters
- Setting the BBI-SS PAS historical recording interval
- Allocating BBI-SS PAS journal and image logs
- Allocating MainView Total Object Manager data sets
- Allocating MainView AutoOPERATOR data sets
- Creating a BBI-SS PAS startup procedure
- Adding the CICS EXCI library to the BBI-SS startup procedure
- Creating the MainView Total Object Manager start procedure
- Creating automatic BBI-SS PAS log handling procedures
- Defining terminal session parameters
- Define cross-system communication
- Specifying product initialization within a BBI-SS PAS
- Enabling Automatic Restart Manager (ARM) support
- Adding the CAS ID to the BBI-SS PAS
- Adding extended function data sets to the BBI-SS PAS startup procedure
- Update command processor table
- Specifying product initialization within the z/OS PAS
- Historical data set determination
Related reference
Was this page helpful? Yes No
Submitting...
Thank you
Comments
Log in or register to comment.