Creating the message configuration file (aopmsg.conf)

These steps show the z/OS® UNIX commands to use to create the message configuration file (aopmsg.conf) in the /etc/Printsrv directory, which is the default directory for Infoprint Server configuration files.

To edit an existing aopmsg.conf file, follow the steps in Editing the message configuration file (aopmsg.conf).

Note: If dynamic configuration is enabled, do not create this file. Instead, specify the attributes in the system configuration definition in the Printer Inventory.

Before you begin: You must have permission to create files in the /etc/Printsrv directory. If you did not change the owner and permissions for /etc/Printsrv after installation, you must have an effective UID of 0 to create files in this directory.

To create the message configuration file:

On the z/OS UNIX command line, switch to an effective UID of 0:
```
su
```
To use the su command, you must be authorized to the BPX.SUPERUSER profile in the FACILITY class in RACF®.
Copy the sample message configuration file, /usr/lpp/Printsrv/samples/aopmsg.conf, to /etc/Printsrv/aopmsg.conf:
```
cp /usr/lpp/Printsrv/samples/aopmsg.conf  /etc/Printsrv/aopmsg.conf
```
Tips:
1. If you copy the sample configuration file to a different location, specify the full path name of the configuration file in the AOPMSG_CONF environment variable in the /etc/profile file and the aopstart EXEC. For information, see Setting environment variables for the Printer Inventory Manager.
2. You can use the sample job that is provided in SYS1.SAMPLIB(AOPCPETC) to copy all Infoprint Server sample configuration files, including the message configuration file, from /usr/lpp/Printsrv/samples to the /etc/Printsrv directory. Review the comments in the sample job to determine which configuration files you require. A user with an effective UID of 0 must run this job.
Change the owner of the file to UID 0:
```
chown 0 /etc/Printsrv/aopmsg.conf
```
Change the group owner to AOPADMIN. AOPADMIN is the suggested RACF group name for Infoprint Server administrators. However, you can use a different name for this group (see AOPADMIN and AOPOPER groups).
```
chgrp AOPADMIN /etc/Printsrv/aopmsg.conf
```
Change the permissions of the file so that it is readable by everyone and writable only by UID 0 and members of the AOPADMIN group.
```
chmod 664 /etc/Printsrv/aopmsg.conf
```
Edit the message configuration file with your preferred editor and save your changes. For example, enter:
```
oedit /etc/Printsrv/aopmsg.conf
```
Edit this file by using the IBM-1047 code page. For the syntax rules for editing the file, see "Syntax rules".
If you switched to an effective UID of 0 in step 1, switch back to your own UID:
```
exit
```
If Infoprint Server is running, stop and restart all Infoprint Server daemons. Be sure to wait for all daemons to stop before you restart. For example, enter these MVS™ commands to run the AOPSTOP and AOPSTART JCL procedures:
```
START AOPSTOP
START AOPSTART
```

Syntax rules: When you edit this file, follow these syntax rules:

Use lowercase characters for the attribute names. Use uppercase or lowercase characters for the values.
Use blank characters before or after the equal sign, if wanted.
Start comments with the # symbol.
Include blank lines, if wanted.

Related information: For information about:

All the attributes that you can specify in the aopmsg.conf file, see aopmsg.conf -- Infoprint Server message configuration file.
How to edit an existing aopmsg.conf file, see Editing the message configuration file (aopmsg.conf).
How to edit the system configuration definition, see Steps for editing the system configuration definition.