How-tos
How-tos provide some best practices and instructions for performing specific
tasks. The topics in this section tell you how to perform these tasks. These
instructions are meant to help you complete commonly used processes.
How to: Convert an existing static hub monitoring environment to a high-availability hub environment
To convert an existing hub environment to a high-availability (HA) hub runtime environment (RTE), you create a new RTE with an HA hub and then either create a new RTE with a remote monitoring server or convert the existing hub RTE to a remote and configure it and any other remotes to connect to the new HA.
How to: Convert a full RTE to a sharing RTE
To convert a full runtime environment (RTE) to a sharing RTE, you change the type to SHARING and provide the appropriate values for the high-level qualifier and the name of the shared RTE. If the shared RTE is a base RTE that does not already exist, you do not have to create it separately. PARMGEN sets up both the sharing runtime data sets and members and the set of shared base libraries.
How to: Convert a sharing-with-SMP/E RTE to sharing-with-base
To convert a sharing-with-SMP/E RTE to a sharing-with-base RTE, leave the type set to SHARING and add the appropriate values for the high-level qualifier and the name of the shared base RTE. If the shared RTE is a base RTE that does not already exist, you do not have to create it separately. PARMGEN sets up both the sharing runtime data sets and members and the set of shared base libraries.
How to: Clone customized data from an existing RTE
If you have cloned an existing runtime environment (RTE) or upgraded an RTE by pointing to new libraries, you might have customized data that you want to copy to the new RTE. For example, you might have customized data such as monitoring situations stored in VSAM data sets; OMEGAMON workspace definitions, profiles, and thresholds; or Enhanced 3270 user interface workspace definitions and profiles.
How to: Merge predefined variables into configuration profiles
Using variables makes it much easier to change operational values, such as storage-related values or port numbers, that affect multiple products and runtime environments. You can change the resolution values of the variables without recreating the runtime environments. IBM provides a set of system variables and user-defined variables that you can import into your configuration profiles. The variable symbols automatically replace the values for the corresponding parameters so you do not have to edit the parameters individually.
How to: Change SMP/E target libraries
If you want to install maintenance or upgrades while leaving your current CSI to support your production environment, install the new software into a new CSI and then change the SMP/E target libraries to upgrade the runtime environments (RTEs).
How to: Switch base read-only libraries using a user-defined variable
To leave started tasks running from one set of base read-only libraries while you apply maintenance or upgrades to a second set, use a user-defined symbol for the name of the base runtime environment (RTE) and create a second set of read-only libraries. Then, after you successfully apply and test the changes, you can point the STCs to the second set either by editing the value of the symbol in the RTE's variables profile, or by modifying the composite STC (IBMSSTRT by default).
How to: Change PDS file count and file size
After you have been collecting and displaying historical data for a while, you might find it that you need to adjust the amount of data that you store. To change the amount of data, you adjust the number and size of files used in the persistent data store.
How to: Reallocate PDS files
If the persistent data store files fill up or become corrupted, new historical data cannot be collected. To correct this problem, the data sets must be reallocated.
How to: Avoid refreshing shared read-only base libraries multiple times
Running the KCIJPLOD load job is part of most maintenance scenarios. For sharing-with-base environments, this job loads both the LPAR-unique libraries and the common shared base libraries by default. The RTE_LOAD_SHARED_LIBS parameter in the configuration profile of each runtime environment controls whether or not the base libraries are loaded. If you have multiple runtime environments sharing the same base libraries, to avoid loading the base libraries multiple times designate one environment to load the base libraries by leaving its flag set to Y , and disable loading of base libraries in all the others.
How to: Use KOBSUPDT security exits with PARMGEN
When using a PARMGEN configuration, you can use KOBSUPDT OMEGAMON security command table exits for the PARMGEN KCIJPSEC composite security job.
How to: Configure passphrase and MFA support in the OMEGAMON 3270 Classic interface
In addition to using a regular password, you can also log on securely to the OMEGAMON 3270 Classic interface using a password phrase (passphrase) and multi-factor authentication (MFA). Some configuration steps are necessary to enable passphrase and MFA support for the OMEGAMON 3270 Classic interface.
How to: Override the currently configured default storage limit within the RKANPARU(KppSYSIN) startup member
In general, when in PARMGEN mode, any storage-related parameters are available for customization and overrides. Defaults are set using the IBM-supplied values. In this scenario, you change the storage limit parameter reflected in the Kpp SYSIN start up member.
How to: Connect agents on local RTE and agents on remote RTEs to the HUB TEMS
Agents on different RTEs can be configured to report to the same HUB TEMS.
How to: Remove SNA protocol from an RTE
After you set up the RTE, you might find that the SNA protocol is no longer needed. You can remove the SNA protocol by changing corresponding parameters.
How to: Configure the z/OS Remote TEMS for Fault Toleration Option (FTO)
The Remote TEMS in your RTE can be configured to participate in Hot Standby configuration between distributed Hub TEMS for FTO.
How to: Collect diagnostic information by running the problem determination data collection tool KCIPDCOL
Use the WCONFIG(KCI$SPDC) KCIPDCOL imbed of the KCIJPCOL PDCOLLECT job to collect diagnostic information from the computer on which the product address spaces are executed.
How to: Configure an autonomous agent to send SNMP events
Customize the autonomous agent parameters in the product-specific WCONFIG(Kpp$PENV) imbed for the agent to send SNMP events.
How to: Remove subsystems from an RTE
To remove a subsystem from a particular runtime environment, clear out all the runtime members that are no longer used in your production libraries.
How to: Configure an RTE created by another user
To take over the configuration of an RTE from another user, you need to supply the GBL_USER_JCL , the RTE high-level qualifier, and your preferred jobcard information.
How to: Enable new parameters in Kpp$* user imbeds that are introduced by PARMGEN PTFs
Advanced parameters that are introduced by the PARMGEN PTFs are customized via the parameters in the Kpp $*
user imbeds.
How to: Validate PARMGEN profile parameter values
The KCIJPVAL job validates the parameter values in PARMGEN profile. The job can be run either as a standalone job from the Utilities panel, or be invoked from $PARSE or $PARSESV job in the WCONFIG library.
How to: Write a message to the console for a situation
You can use the Take Action command ZOSWTO (z/OS WTO) to write a message to the z/OS operator console for a situation.
How to: Create an HTTP request for a situation
You can use the Take Action command HTTPRQ (HTTP Request) to create an HTTP request for a situation.