Run aopsetup

Description

When migrating to z/OS V2R2 Infoprint Server, you must run the aopsetup shell script to establish the correct file permissions for Infoprint Server directories and files.

Table 1 provides more details about this migration action. Use this information to plan your changes to the system.

Table 1. Information about this migration action
Element or feature:	z/OS Infoprint Server.
When change was introduced:	General migration action not tied to a specific release.
Applies to migration from:	z/OS V2R1 and z/OS V1R13.
Timing:	After the first IPL of z/OS V2R2.
Is the migration action required?	Yes.
Target system hardware requirements:	None.
Target system software requirements:	None.
Other system (coexistence or fallback) requirements:	None.
Restrictions:	None.
System impacts:	None.
Related IBM® Health Checker for z/OS® check:	None.

Steps to take

Run the aopsetup shell script from an rlogin shell, from an OMVS session, or with the BPXBATCH command. Specify the names of the RACF groups that you defined for Infoprint Server operators and administrators as arguments to aopsetup. For example, if you defined group AOPOPER for operators and group AOPADMIN for administrators, enter:

/usr/lpp/Printsrv/bin/aopsetup AOPOPER AOPADMIN

Rule: You must run aopsetup from a user ID with a UID of 0. You can use the su command to switch to an effective UID of 0 if you have READ access to the BPX.SUPERUSER profile in the RACF FACILITY class.

Tip: You can run aopsetup from the driving system (instead of the target system) if all of these are true:

You have the target system's /var/Printsrv directory accessible.
You reference the target system's /usr/lpp/Printsrv directory mounted under a /service directory as described in the comments at the beginning of the aopsetup shell script.
The RACF database groups for operators and administrators are the same on the driving and target system.

Reference information

For information about running aopsetup, see z/OS Infoprint Server Customization.