Profile viewing and cloning
You can use the OMEGAMON enhanced 3270 user interface to view and clone user profiles.
Use Profile viewing and cloning to customize the standard user profiles that are delivered with the enhanced 3270 user interface.
Preparing for profile cloning
- Ensure that the user has the required authority.
The cloning process copies a standard product-provided profile from a configuration runtime environment data set to a user profile data set. The runtime environment data set is a read only data set, the user profile data set is a writeable data set. The user that wants to clone a profile must have the authority to create new members in the user profile data set. The default user profile name is
<hilev>.<rtename>.UKOBDATF. - Ensure that the user profile data set is the first data set that
is specified in the
RKOBPROF DDstatement. The user profile data set is the data set that is pointed to by the enhanced 3270 user interface started task JCLUKOBDATF DDstatement.If you ensure that it is the first data set, it facilitates profile testing when customization changes are applied.Important: Be sure that you specify the same<hilev>.<rtename>.UKOBDATFdata set in both theUKOBDATF DDandRKOBPROF DDstatements. - Minimize potential disruptions to other enhanced 3270 user interface
users.
Because the cloning and customization process modifies product provided profiles, 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 profile 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 profiles into a corresponding data set that is specified in the shared development or production configuration enhanced 3270 user interface started task JCL.