Usage notes

1. Before you use the aopstart command, your installation might need to customize the aopstart EXEC. For information, see z/OS Infoprint Server Customization.
2. To use the aopstart command, you must either be a member of the RACF® AOPOPER group or have an effective UID of 0. You can use the z/OS UNIX su command to switch to an effective UID of 0 if you have access to the BPX.SUPERUSER profile in the RACF FACILITY class.
3. IBM strongly suggests that you use the AOPSTART procedure to run the aopstart command instead of entering the aopstart command. For more information about this guideline, see "Customizing startup and shutdown commands and procedures" in z/OS Infoprint Server Customization.
4. Make sure that TCP/IP has finished initialization before you start the LPD (aoplpd), the IPP Server daemon (aopippdxp), the IP PrintWay™ extended mode daemons (aopoutd and aopwsmd), or the z/OS SNMP agent. You do not have to start TCP/IP to start other daemons.
5. Start the Printer Inventory Manager daemons before you start IP PrintWay basic mode or a NetSpool task. Also, start the Printer Inventory Manager daemons before you start PSF if PSF uses the Printer Inventory.
6. Start the z/OS SNMP agent (osnmpd) before you start the Infoprint Server SNMP subagent daemon (aopsnmpd). For information about how to start osnmpd, see z/OS Communications Server: IP Configuration Reference.
7. Before you start Infoprint Server daemons, you might need to increase the maximum size of memory that is available. This table shows the minimum storage required by Infoprint Server daemons:

   Daemon	Minimum MB
   PostScript to AFP and PDF to AFP transform	42 MB (256 MB is suggested)
   IPP Server	200 MB

   To make sure that sufficient memory is available, either set the MAXASSIZE parameter in the BPXPRMxx member of SYS1.PARMLIB or enter the SETOMVS command from the console. For example, to set the maximum size to 256 MB, enter:

   SETOMVS MAXASSIZE=268435456

   For more information about setting the MAXASSIZE parameter in the BPXPRMxx member, see z/OS Infoprint Server Customization.

   The security administrator might have specified a maximum region size for your user ID in the RACF ASSIZEMAX parameter. The ASSIZEMAX parameter overrides the MAXASSIZE parameter.

   If you start Infoprint Server daemons from the OMVS shell under TSO, the SIZE parameter on your TSO/E logon determines the amount of memory available. If you use data stream transforms, set SIZE=42000 or larger. IBM® suggests that you set SIZE=256000 (or larger) so that you can transform large or complex data streams. If you start the IPP Server daemon, set SIZE=200000 (or larger).

8. From ISPF, you can use the TSO oshell or omvs command to run the aopstart command. On the ISPF Command Shell panel (ISPF option 6), type one of these commands:
   • oshell aopstart
   • omvs

     Then, on the OMVS command line, type aopstart

9. You can use the TSO ishell command to enter the aopstart command. You must, however, type the full path name of the aopstart command because the z/OS® ISPF shell does not use environment variables set in the /etc/profile profile. For example, if the aopstart command is in the default directory, run this command:

   /usr/lpp/Printsrv/bin/aopstart

10. To request that Infoprint Server validate internal databases, set the AOPVALIDATEDB environment variable to any value (for example, AOPVALIDATEDB=1) either in the aopstart EXEC or in the environment. IBM suggests that you validate internal databases if Infoprint Server ended abnormally or if you specified the force option when you stopped Infoprint Server daemons. The AOPVALIDATEDB environment variable applies only when the Printer Inventory Manager daemons start. When you specify the AOPVALIDATEDB environment variable, Infoprint Server takes a few extra minutes to start.
11. The aopstart command can end with abend EC6 (reason code FFFF) or abend 33E. These abends do not indicate an error. Your installation can suppress these abends in the IEASLP00 member of SYS1.PARMLIB.