z/OS Infoprint Server Printer Inventory for PSF
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


Using AOPBATCH

z/OS Infoprint Server Printer Inventory for PSF
SA38-0694-00

Using AOPBATCH

You can invoke AOPBATCH in JCL with this EXEC statement:

//stepname EXEC PGM=AOPBATCH,PARM='pidu [-v] [-q]'

-q
Suppresses informational messages that the pidu command writes to the output data set named in the STDOUT DD statement.
-v
Writes the name of the Printer Inventory to the output data set named in the STDERR DD statement. Also provides additional informational messages.

You can specify these DD statements:

STDENV
Specifies environment variables that PIDU uses. You can specify the environment variables in-stream or in a UNIX file or MVS™ data set. When you use AOPBATCH, you need to specify the PATH, LIBPATH, and NLSPATH environment variables only if your installation did not install Infoprint Server files in the default directories. Specify the AOPCONF environment variable if the Infoprint Server configuration file is not in /etc/Printsrv/aopd.conf or in $HOME/.aopconf. Specify the environment variables in the format variable = value.
STDERR
Specifies a SYSOUT data set, a UNIX file, or an MVS data set. PIDU writes error messages to this file or data set.
STDIN
Specifies PIDU commands in-stream or names a UNIX file or MVS data set that contains the commands.

Tip: If any attribute value is greater than 80 characters, you cannot specify the PIDU commands in-stream because an attribute value cannot span lines and the SYSIN DD * statement lets you specify a maximum of 80 characters on one line. Instead, specify the PIDU commands in an MVS data set that has a logical record length (LRECL) of 255 and a variable blocked (VB) blocksize (BLKSIZE).

STDOUT
Specifies a SYSOUT data set, a UNIX file, or an MVS data set. PIDU writes its output and informational messages to this file or data set.

IBM® provides sample JCL in the AOPPIDU member of SYS1.SAMPLIB for running PIDU using the AOPBATCH utility. Figure 4 shows member AOPPIDU.

Figure 4. Sample JCL for running PIDU as a batch job — SYS1.SAMPLIB(AOPPIDU)
//AOPPIDU  JOB ,'pidu'
//*
//PIDU     EXEC PGM=AOPBATCH,PARM='pidu'
//*
//STDIN    DD  DSN=hlq.INVDEFS,DISP=SHR
//*
//STDOUT   DD  SYSOUT=*
//STDERR   DD  SYSOUT=*
//*
//* STDENV may point to a dataset containing environment variables.
//*        Builtin values will work for the default installation.
//*STDENV   DD  DSN=environment,DISP=SHR

Example

This example lists all FSA and FSS definitions, and specifies environment variables in-stream in the JCL:

//AOPPIDU  JOB ...
//PIDU     EXEC PGM=AOPBATCH,PARM='pidu'
//STDIN    DD  *
list fsa;
list psf-fss;/*
//STDOUT   DD  SYSOUT=*
//STDERR   DD  SYSOUT=*
//STDENV   DD *
PATH=/usr/mylib/Printsrv/bin
LIBPATH=/usr/mylib/Printsrv/lib
NLSPATH=/usr/mylib/Printsrv/%L/%N:/usr/mylib/Printsrv/En_US/%N
/*
Tip:
If your installation installed Infoprint Server files in default directories, you can omit the STDENV DD statement.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014