pidu command

pidu [-qv] [-c "command; …"]… [filename]… 

The pidu command lets you specify one or more of the PIDU commands to manage objects in the Printer Inventory. You can specify PIDU commands in the -c option or in a file. The pidu command writes a report of errors to standard error (stderr) and writes informational messages and command output to standard output (stdout).

-c "command; …"

Specifies one or more PIDU commands. Enclose the commands in single or double quotation marks, and end each statement with a semicolon. If a command contains a value that requires single quotation marks, such as a hexadecimal value, enclose the commands in double quotation marks. You can repeat the -c option.

If you do not specify the -c option or the name of a file, pidu reads the commands from standard input (stdin), which can be either keyboard data or output from another command.

You can specify these PIDU commands:

• create
• delete
• display
• dump
• export
• force-create
• list
• modify
• rename

-q

Suppresses informational messages that the pidu command writes to stdout.

-v

Writes the name of the Printer Inventory to stderr. Also provides more informational messages.

filename

The name of a UNIX file or sequential MVS™ data set that contains the commands. You can repeat this option.

If the data set is an MVS data set, specify // before the file name. If you specify a fully qualified data set name, also enclose the data set name in single quotation marks and specify a backslash before each single quotation mark. For example, if the output file is named USERID.MYFILE, enter:

//\'USERID.MYFILE\'

If you want your TSO user ID prefixed to the data set name, specify:

//MYFILE

To specify commands from stdin, omit the file name and the -c option.

• You can specify PIDU commands interactively from your keyboard.
• When you specify PIDU commands in a UNIX file (such as a z/FS file) or an MVS data set, you can:
  • Start comments with a number sign (#).
  • Include blank lines, if wanted.
  • Specify the PIDU command names, attribute names, and attribute values on separate lines:
    • In a UNIX file, an attribute value can span lines if all lines other than the last line end with a backslash. Be sure that no blank characters are present after the backslash. For example:

      attribute1 = 
      'A very, very, very long \
      value'

    • In an MVS data set, the entire attribute value must be on one line. To specify a long attribute value, allocate a data set that has a logical record length of 255 (LRECL=255) and a variable blocked record format (RECFM=VB). Then, specify the entire value on one line. For example:

      attribute1 = 
      'A very, very, very long value'

AOPCONF

Names the Infoprint Server configuration file. The file that is named in this variable takes precedence over the user-specific configuration file ($HOME/.aopconf) and the system default configuration file (/etc/Printsrv/aopd.conf).

LIBPATH

The path that is used to locate dynamic link libraries (DLL).

NLSPATH

Lists the directory where the Infoprint Server message catalogs are located.

PATH

Lists the directory where the Infoprint Server executable files are located.

$HOME/.aopconf

Contains the user-specific Infoprint Server configuration file. This file takes precedence over /etc/Printsrv/aopd.conf.

/etc/Printsrv/aopd.conf

The default Infoprint Server configuration file.

0

The PIDU commands were done successfully.

>0

An error occurred that prevented one or more PIDU commands from being done successfully.