Disaster Recovery (Backup Site) for Printers

There are two situations where a backup site for printing is essential.

• In data centers with only one or a few AFP printers (main printer). For example, situations when the printer is out of order in the middle of the night during end-of-month processing can and do occur.
• Data centers that have peak periods but normally print lower amounts of output may prefer to do some of their peak day printing at another site. This method avoids the need to purchase more printers that are used only on peak days.

Without AFP, in order to print at a backup site, a copy of the SYS1.IMAGELIB dataset had to exist at the backup site. However, only one SYS1.IMAGELIB dataset is allowed per CPU and each CPU must have a SYS1.IMAGELIB dataset. The backup site also has a SYS1.IMAGELIB of its own. If even one definition (for example, font shape) is not identical for both sites, then the backup site cannot be used for printing. What generally occurred to avoid this restriction was that the resident SYS1.IMAGELIB dataset was temporarily replaced, which was inconvenient and less than productive.

AFP, however, does not require the use of SYS1.IMAGELIB. AFP printing characteristics can be defined in any number of libraries on a single system. In addition, different libraries can be defined to different printers, using the same PSF procedure. A copy of the AFP libraries is all that is required at the backup site.

Using the JES OFFLOAD facility, Control-D bundles can be downloaded to tape or cartridge retaining all printing characteristics and the correct sequence of the bundle. Reports can be printed on a backup site printer, regardless of whether or not Control-D is installed at the backup site.