Determine library owner

When you plan your application installation, you must first decide the user profiles and installation values for each application.

Determining user profiles and installation values for applications: Before you install an application that was created on another system, you may need to create one or more user profiles. The user profile that owns the application libraries and objects should exist on your system before you load the libraries on your system. Record the profiles you need to create for each library and what parameters the profiles need on the Application installation form.

To determine the installation values necessary, ask your programmer or application provider the following questions and record their answers on the Application installation form: Find out whether your programmers or application provider have created any authorization lists for the application. Prepare an Authorization list form for each created authorization list or ask your programmer for information about the list. You can determine whether you should change any installation values.

Changing installation values for applications: Compare the information from the Application installation form with your resource security plan for the library on the Library description form. If they are different, you need to decide what changes to make after the application is installed.

Changing application ownership: If your programmer or application provider has created a special profile to own the application libraries and objects, consider using that profile, even if it does not match your naming conventions.

Transferring ownership of objects can take a long time and should be avoided. If one of the IBM-supplied group profiles, such as QSECOFR or QPGMR, owns the application, you should transfer ownership to another profile after you install the application. Sometimes programmers design applications to prevent changes in object ownership. Try to work within the restrictions and still meet your own requirements for managing security. However, if an IBM-supplied profile, such as QSECOFR, owns the application, you and your programmer or application provider need to develop a plan to change ownership. Ideally, you should change ownership before you install the application.

Changing public authority: When you save objects, you also save their public authority with them. When you restore an application library to your system, the library and all its objects will have the same public authorities they had when they were saved. This is true even if you saved the library on another system. The CRTAUT value for a library (public authority for new objects) does not affect objects that are restored. They are restored with their saved public authority, regardless of the CRTAUT for the library.

You should change the public authority of libraries and objects to match your plan on the Library description form. To ensure that you have planned your application installation completely, you should: After you finished these planning tasks, you are ready to set up your user security.