Running the PIDU program using the pidu command
Format
pidu [-qv] [-c "command; ..."]... [filename]...
Description
The pidu command lets you specify one or
more of the PIDU commands shown in Table 37 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).
Options
- -c 'command; ...'
- -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
- display-fully
- dump
- export
- force-create
- list
- modify
- rename
For detailed information about these commands, see PIDU commands.
- -q
- Suppresses informational messages that the pidu command
writes to stdout.
- -v
- Writes the name of the Printer Inventory to stderr.
Also provides additional informational messages.
Operands
- 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.
Usage notes
- You can specify PIDU commands interactively from your keyboard.
For an example, see Entering PIDU commands interactively.
- When you specify PIDU commands in a UNIX file
(such as a z/FS file) or an MVS data
set:
- Start comments with a pound sign (#).
- Include blank lines if desired.
- You can specify the PIDU command names, attribute names, and attribute
values on separate lines.
- In a UNIX file, an attribute value can span
lines provided that 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 very 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'
Examples -- pidu
Entering PIDU commands interactively
To enter one or more PIDU commands interactively from your keyboard:
- On the z/OS UNIX command
line, type pidu and press Enter.
_______________________________________________________
- Type a PIDU command and press Enter. For example, to create a
printer definition, type:
create printer lp1 description="Default printer"
location="Printer room" printer-type=ip-printway dcf-routing=yes
destination=LP1 printer-ip-address=printer1.boulder luname=LUPRT001
lu-classes={2} include-allocation=printway
include-processing = pcl_printer include-printway-options=pcl_land_17cpi
include-netspool-eof-rules=bracket include-netspool-options=pcl
include-protocol=lpr_options ; For an explanation of this create command, see Creating an IP PrintWay printer
definition for a PCL printer with LPR protocol.
_______________________________________________________
- After the command is processed, type another command and press
Enter. For example, to display the attributes of the printer definition
just created, enter:
display printer lp1;
_______________________________________________________
- After the command is processed, use Ctrl-D or
type exit to end the pidu command.
_______________________________________________________
Specifying PIDU commands on the command line
To specify two PIDU list commands with the -c option, enter:
pidu -c "list printer; list printer-pool;"
Specifying PIDU commands in a file
To specify a UNIX file named pidu.commands that
contains PIDU commands, enter:
pidu pidu.commands
To specify a fully-qualified MVS data
set named MARY.PIDU.CMDS, enter:
pidu //\'MARY.PIDU.CMDS\'
To
prefix your TSO user ID to the data set name, enter:
pidu //PIDU.CMDS
File pidu.commands (or data set PIDU.CMDS)
contains the PIDU commands. For example:
create printer lp1 description="Default printer"
location="Printer room" printer-type=ip-printway dcf-routing = yes destination=LP1
printer-ip-address=printer1.boulder 1uname = LUPRT001 lu-classes={ 2 }
include-allocation=printway include-processing=pcl_printer
include-printway-options=pcl_land_17cpi include-netspool-options=pcl
include-netspool-eof-rules=bracket include-protocol=lpr_options ;
list printer; # List all printer definitions
Specifying PIDU commands with hexadecimal values
To specify a PIDU create command containing the line-termination
attribute, enter:
pidu -c "create printer lp2 line-termination=X'0D25';"
Environment variables
- AOPCONF
- Names the Infoprint Server
configuration file. The file 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 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 executables are
located.
Files
- $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.
Exit values
- 0
- The PIDU commands were done successfully.
- >0
- An error occurred that prevented one or more PIDU commands from
being done successfully.
|