Installation considerations for MainView AutoOPERATOR 8.2
This section contains technique-specific installation considerations for migrating from previous versions of MainView AutoOPERATOR to MainView AutoOPERATOR version 8.2.
Getting new passwords
MainView AutoOPERATOR version 8.2 uses BMC Software Product Authorization passwords. For a description of the Product Authorization utility and information about obtaining and applying passwords, see the Installation System User Guide.
The following table shows how the product component name (AOOPTION) for earlier MainView AutoOPERATOR versions correlates to the new password codes.
List of MainView AutoOPERATOR password product codes
MainView AutoOPERATOR product component name
MainView AutoOPERATOR AOOPTION
MainView AutoOPERATOR password product code
MainView AutoOPERATOR Access NV
MainView AutoOPERATOR TapeShare
MainView AutoOPERATOR for CICS
MainView AutoOPERATOR for IMS
MainView AutoOPERATOR for MQ
MainView AutoOPERATOR for z/OS
MainView for CICS Management
MainView for IMS Management
MainView for Networks
MainView Message Management
Even if you are migrating from an earlier version of MainView AutoOPERATOR or changing from one CPU to another CPU, you must acquire new BMC Software Product Authorization passwords to use any version MainView AutoOPERATOR version 6.4 or later.
If you want to use these passwords in multiple PASs, but you want only certain product options to be active within a specific PAS, you can install the individual MainView AutoOPERATOR component passwords into separate password library data sets or use the AOOPTION parameter in BBPARM member AAOPRMxx to limit the components that are activated in the PAS.
After this process is complete, concatenate together the password library data sets for the specific product options that you want active for the PAS. For example, your concatenation might look like the following example where the two product components that are activated for this PAS are :
MainView AutoOPERATOR for CICS (CAO)
MainView AutoOPERATOR for z/OS (MAO)
//BMCPSWD DD DISP=SHR,DSN=AAO.BMCPSWD.CAO (CAO ONLY) // DD DISP=SHR,DSN=AAO.BMCPSWD.MAO (MAO ONLY)
In the following example, the first line of the concatenation shows that all of the MainView AutoOPERATOR product components, with the exception of TapeSHARE, are included. This exception is because you can run TapeSHARE in only one PAS per LPAR (the first one that is started with that password). Therefore, you should include the TapeSHARE password in the JCL of only one BBI-SS PAS.
Example of specifying passwords for all MainView AutoOPERATOR product components
//BMCPSWD DD DISP=SHR,DSN=AAO.BMCPSWD (ALL AAO No/TapeSHARE) //* DD DISP=SHR,DSN=AAO.BMCPSWD.ALL (ALL AAO) //* DD DISP=SHR,DSN=AAO.BMCPSWD.ANV (ANV ONLY) //* DD DISP=SHR,DSN=AAO.BMCPSWD.CAO (CAO ONLY) //* DD DISP=SHR,DSN=AAO.BMCPSWD.IAO (IAO ONLY) //* DD DISP=SHR,DSN=AAO.BMCPSWD.MAO (MAO ONLY) //* DD DISP=SHR,DSN=AAO.BMCPSWD.MQS (MQS ONLY) //* DD DISP=SHR,DSN=AAO.BMCPSWD.SHA (SHA ONLY) //* DD DISP=SHR,DSN=AAO.BMCPSWD.TSH (TSH ONLY)
To create a universal JCL, you can use symbolics with the &SSID within the data set name. Parameters that are passed to the PROC statement allow you to select one set of passwords to use; see the following example:
Example of using symbolics for passwords for MainView AutoOPERATOR product components
//BMCPSWD DD DISP=SHR,DSN=AAO.&SS..BMCPSWD (Set for this PAS)
When the SS PAS JCL passes the parameter SS=SYSA to the PROC, this example shows that AA0.&SS..BMCPSWD resolves to AAO.SYSA.BMCPSWD, which is the data set that contains the passwords to use for PAS.
Re-implement JES2MAO exit
If you are migrating by a using Standard installation with the BMC Installation System and you are replacing any MainView AutoOPERATOR version, and all of the following statements are true, you must implement the JES2MAO exit again:
Your site is licensed for the MainView AutoOPERATOR for z/OS option.
You elected to implement the JES2MAO exit.
The JES2MAO exit is linked to the existing system’s BBLINK library.
Installing MainView AutoOPERATOR into an existing zone that includes other BMC products
Ensure all of the other BMC products in the target zone are currently supported versions before installing MainView AutoOPERATOR into the same zone. MainView AutoOPERATOR does not support coexistence with earlier, unsupported versions of BMC products.
MainView AutoOPERATOR also requires that all products running within the same BBI-SS PAS are installed into the same zone and executed out of the same libraries. MainView AutoOPERATOR does not support concatenation of product libraries in BBILOAD or STEPLIB.
When MainView AutoOPERATOR is installed into a zone with other products, it is important to note that MainView AutoOPERATOR shares the use of some FMIDs with other products. Therefore, installing a new version of one product can impact other products. For example, when installing a new version of MainView AutoOPERATOR into a zone where both MainView AutoOPERATOR for CICS and MainView for CICS are running, the new version MainView AutoOPERATOR version might impact MainView for CICS.