Screen space and profile data set concatenation
OMEGAMON® for IMS reads screen spaces from the data sets referenced by the RKOIPROC DD statement in the OMEGAMON for IMS procedure. OMEGAMON for IMS writes screen spaces that you create or modify to the data set referenced by the RKOIPCSV DD statement. OMEGAMON for IMS reads profiles from the data set referenced by the RKOIPROF DD statement and writes profiles, both installation and user-defined, to the data set referenced by the RKOIPFSV DD statement.
Screen spaces
Screen space that OMEGAMON for IMS provides, which are used in the menu and command interfaces, are stored in the rhilev.RKOIPROC data set. To create, modify, or delete screen spaces for your use without modifying either the standard screens or screens of other users, create one or more additional data sets called cccccccc.RKOIPCSV, where the cccccccc prefix can be for your site or for an individual user. The PARMGEN configuration tool allocates one RKOIPCSV data set for each IMS ID, rhilev.imsid.RKOIPCSV.
OMEGAMON for IMS writes the members that you change to the data set that the DD statement RKOIPCSV references. If you want OMEGAMON for IMS to use those members, your cccccccc.RKOIPCSV data set must be concatenated with the rhilev.RKOIPROC data set on the RKOIPROC DD statement.
//* OMEGAMON for IMS saves screen spaces in the RKOIPCSV data set
//RKOIPCSV DD DISP=SHR,DSN=rhilev.imsid.RKOIPCSV
//* OMEGAMON for IMS reads screen spaces from the RKOIPROC data sets
//RKOIPROC DD DISP=SHR,DSN=rhilev.imsid.RKOIPCSV
// DD DISP=SHR,DSN=rhilev.RKOIPROC Profiles
When you save an installation-defined or user-defined profile, OMEGAMON for IMS writes the profile to the data set referenced by the RKOIPFSV DD statement in the OMEGAMON for IMS procedure. The PARMGEN configuration tool allocates one RKOIPFSV data set for each IMS ID, rhilev.imsid.RKOIPFSV. OMEGAMON for IMS reads profiles from the data sets referenced by the RKOIPROF DD statement.
In many cases, the RKOIPROF and RKOIPFSV DD statements can reference the same data set, for example, rhilev.imsid.RKOIPFSV. However, you might want to restrict users from updating the installation-defined profile by placing it in a separate data set that is concatenated in the RKOIPROF DD statement. Alternatively, you can implement security so that general users cannot issue the IOPT and IPRF commands. You can also implement security for specific commands to restrict users from being able to change selected parameters in their own user-defined profiles, but allow them to customize others.