/var/Printsrv directory

The /var/Printsrv directory contains the Printer Inventory and other Infoprint Server files. You can change the name of this directory in the base-directory attribute in the Infoprint Server configuration file (aopd.conf).

Tip: The aopsetup shell script creates the /var/Printsrv directory (or the directory that is named in the base-directory attribute) and sets the appropriate permissions for it. For information about how to run aopsetup in a later step, see Setting permissions for directories and executable files -- aopsetup

Guidelines:

Mount a separate file system at the /var/Printsrv mount point because some subdirectories can become large. If your system is part of a sysplex, the /var/Printsrv file system must be system-specific and designated NOAUTOMOVE in the BPXPRMxx parmlib member.
Example: This example shows a sample BPXPRMxx member in SYS1.PARMLIB:
```
MOUNT FILESYSTEM('my.var.printsrv.filesystem')
      TYPE(ZFS) 
      MODE(RDWR) 
      NOAUTOMOVE 
      MOUNTPOINT('/&SYSNAME./var/Printsrv') 
```
The /var/Printsrv directory can be in a Hierarchical File System (HFS) or a z/OS® File System (zFS) that is HFS-compatible. Because a zFS has higher performance characteristics than an HFS and is the strategic file system for z/OS, you need to allocate a zFS rather than an HFS. For information about zFS, see z/OS Distributed File Service zFS Administration.
Make sure that the file system that contains the /var/Printsrv directory has enough space. For information about how much space is required, see Calculating DASD space requirements for the /var/Printsrv directory.
Do not change the owner or permissions of the /var/Printsrv directory after it is created. For a secure environment, this directory must be:
- Owned by UID of 0
- Readable and writable only by users with an effective UID of 0 or members of the AOPADMIN group
- Executable by everyone
The /var/Printsrv directory is a working directory for Infoprint Server. Do not place any user directories or files in the /var/Printsrv directory.

Infoprint Server creates the Printer Inventory files automatically the first time the administrator uses the Infoprint Server ISPF panels or the Printer Inventory Definition Utility (PIDU) to create objects in the Printer Inventory, such as printer definitions. The Printer Inventory files also contain objects that the administrator does not create. For example, Print Interface creates objects for each job processed. These job objects are deleted when the data sets to which they correspond are deleted from the JES spool.

The Printer Inventory consists of files in the /var/Printsrv directory with file extension .v2db. For example, these Printer Inventory files are in the /var/Printsrv directory:

master.v2db
jestoken.v2db
pwjestoken.v2db

Other Printer Inventory files with the .v2db extension are in /var/Printsrv subdirectories.

Note: Printer Inventory files with extension .v2db are in Version 2 format. Printer Inventory files with extension .db are in Version 1 format. If you upgraded to Infoprint Server V2R2 from Start of change

V1R11 or

an earlier release, the /var/Printsrv directory might contain Printer Inventory Version 1 and Version 2 files. Infoprint Server V2R2 does not read or update Printer Inventory Version 1 files. You can delete the Version 1 files (extension .db).