Starting Infoprint Server with JCL startup procedures

These JCL procedures start Infoprint Server daemons:

AOPSTART: Starts one or multiple daemons. See AOPSTART JCL procedure.
AOPDEMON: Starts one daemon. See AOPDEMON JCL procedure.
AOPSTAR2: Starts one or multiple daemons. See AOPSTAR2 JCL procedure.

Start of change AOPDEMON and AOPSTAR2 are used only when dynamic configuration is enabled and the Operating mode field is set to z/OS 2.2 on the ISPF System Configuration panel. You can use the AOPSTAR2 procedure to start all daemons in the same way you use the AOPSTART procedure. End of change

Guidelines:

If you specify a z/OS® UNIX file or an MVS™ data set in a DD statement in the AOPSTART or AOPDEMON procedure, the user ID associated with the startup procedure must be authorized to:
- Read the data set or file specified in the STDENV or VARFILE DD statement, if used.
- Read and write to the data set or file specified in the STDOUT and STDERR DD statements (not required if these DD statements point to SYSOUT).
Make sure that TCP/IP finished initialization before you start the LPD (aoplpd), the IPP server daemon (aopippd), or the IP PrintWay™ extended mode daemons (aopoutd and aopwsmd). You do not have to start TCP/IP to start other daemons.
Start the Printer Inventory Manager daemons before you start IP PrintWay basic mode or the NetSpool task. Also, start the Printer Inventory Manager daemons before you start PSF if PSF uses the Printer Inventory.
To request that Infoprint Server validate internal databases, set the AOPVALIDATEDB environment variable to any value (for example, AOPVALIDATEDB=1). 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 daemon starts. When you specify the AOPVALIDATEDB environment variable, Infoprint Server takes a few extra minutes to start.
The startup procedure 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.