Stopping Infoprint Server with the AOPSTOP JCL procedure

The AOPSTOP procedure stops all Infoprint Server daemons or only the specified daemons.

After you run the AOPSTOP procedure, you see one or more messages in the STDOUT or STDERR data set, or in the console log. The messages can include:

AOP044I Shutdown complete. (program:daemon)
AOP078W Daemon daemon is not running.
AOP079I A shutdown of daemon daemon has been initiated.
AOP135I An abrupt shutdown of daemon daemon has been initiated.
AOP136I A destructive shutdown of daemon daemon has been initiated.

When all Infoprint Server daemons have ended, you see this message:

$HASP395 AOPD  ENDED

To stop Infoprint Server daemons with the AOPSTOP JCL procedure, enter this MVS™ START command:

START AOPSTOP,[OPTIONS='-d daemon... [now] [force]']

-d daemon

Specifies the daemon to stop. If you omit this option, all active daemons are stopped, including the Printer Inventory Manager daemons (aopd, aophinvd, aoplogd, and aopsdbd). You can specify one of these values:

ippd

Stops the Internet Printing Protocol daemon, aopippdxp.

lpd

Stops the line printer daemon, aoplpd.

netd

Stops the NetSpool daemon, aopnetd.

outd

Stops the IP PrintWay™ extended mode daemons, aopoutd and aopwsmd. When you start IP PrintWay again, any IP PrintWay printers that were stopped return to the started state, and any printers that were redirected to other printers are no longer redirected.

snmpd

Stops the SNMP subagent daemon, aopsnmpd.

ssid

Stops the Infoprint Central daemon, aopssid.

subd

Stops the Print Interface subsystem daemon, aopsubd.

xfd

Stops the Infoprint Server Transform Manager daemon, aopxfd.

now

Stops the daemons immediately. If work is in progress, incorrect output or data loss might result. If this option is not specified, the daemons stop after current activity completes.

force

Stops the daemons immediately using a “destructive” shutdown. If work is in progress, incorrect output or data loss might result. For daemons that manage a database, such as aopd, aophinvd, or aopsdbd, the database might be corrupted. If this option is not specified, the daemons stop after current activity completes.

Notes:

1. Use this command with extreme caution.
2. Before you use this command, use the export command to backup the Printer Inventory (if Infoprint Server is running).
3. After you stop daemons using this option, specify the AOPVALIDATEDB environment variable to validate internal databases when you start Infoprint Server daemons again. You can specify AOPVALIDATEDB=1 either in the aopstart EXEC or in the AOPSTART STDENV data set. If databases are corrupted, you might need to restore the Printer Inventory and the search databases.

Examples:

1. To stop all daemons after current activity ends, enter this MVS START command. The Print Interface component of Infoprint Server stops accepting new print requests and completes all work in progress before shutting down.

   START AOPSTOP

2. To stop the Infoprint Server Transform Manager and line printer daemons, enter this MVS START command:

   START AOPSTOP,OPTIONS='-d xfd -d lpd'

3. To stop all daemons immediately, enter this MVS START command. Documents that are being processed might be lost.

   START AOPSTOP,OPTIONS='now'

4. To stop all daemons immediately using a “destructive” shutdown, enter this MVS START command. Documents that are being processed might be lost. For daemons that manage a database, such as aopd, aophinvd, or aopsdbd, the database might be corrupted. Use this command with extreme caution.

   START AOPSTOP,OPTIONS='force'

Guidelines:

1. Before you run the AOPSTOP procedure, your installation might need to customize it. For information, see z/OS Infoprint Server Customization.
2. Before you stop all daemons, stop other programs that are using the Printer Inventory, such as NetSpool, IP PrintWay basic mode, and PSF.
3. Before you stop Infoprint Server, back up the Printer Inventory if you have made changes to it since the last backup. For information about how to back up the Printer Inventory, see z/OS Infoprint Server Customization.
4. The AOPSTOP procedure can end with abend EC6 (reason code FFFF) or abend 33E. These abends do not indicate an error. You can suppress these abends in the IEASLP00 member of SYS1.PARMLIB.