Preparing for threshold member cloning

The OMEGAMON enhanced 3270 user interface provides the capability to clone threshold members. Before you can clone a threshold member, you must prepare by performing administrative steps.

Before you begin

Threshold cloning can be used to customize the standard threshold members that are delivered with the enhanced 3270 user interface.

The cloning process copies a standard product-provided threshold member from a configuration runtime environment data set to a user threshold member data set. The runtime environment data set is a read-only data set; the user threshold member data set is a writeable data set. The user that wants to clone a threshold member must have the authority to create new members in the user threshold member data set. The default user threshold member data set name is <hilev>.<rtename>.RKANPARU.

About this task

In preparation for threshold member cloning by an enhanced 3270 user interface user, complete the following administrative steps.

Procedure

  1. Ensure that the user who wants to clone a threshold member has the required authority.

    The user must have the authority to create new members in the user threshold member data set. The default user threshold member data set name is <hilev>.<rtename>.RKANPARU.

    Note: For security reasons, you might not be able to grant users write or update authorization to the <hilev>.<rtename>.RKANPARU data set. In that case, complete the following steps:
    1. Create an alternative data set with attributes that match the <hilev>.<rtename>.RKANPARU data set attributes.
    2. Change the enhanced 3270 user interface started task JCL to include the alternative data set in the UKANPAR DD statement data set concatenation.
    3. Grant users authorization to this data set.
    4. Create the user ID custom threshold members in this data set.
  2. Ensure that the user threshold member data set is the first data set that is specified in the RKANPAR DD statement. The user threshold member data set is the data set that is pointed to by the enhanced 3270 user interface started task JCL RKANPARU DD statement.
    If you ensure that it is the first data set, threshold member testing is facilitated when customization changes are applied.
    Important: Be sure that you specify the same <hilev>.<rtename>.RKANPARU or alternative data set first in both the UKANPARU DD and RKANPAR DD statements.
  3. Minimize potential disruptions to other enhanced 3270 user interface users.
    Because the cloning and customization process modifies product provided thresholds, it must be done in a configuration that is not disruptive to ongoing normal usage of the enhanced 3270 user interface. For example, a separate enhanced 3270 user interface address space with a unique instance of the user threshold member data set might be used during the customization and testing process. After the customization and testing, the changes might be deployed to a shared development or production configuration by copying the customized threshold members into a corresponding data set that is specified in the shared development or production configuration enhanced 3270 user interface started task JCL.