Running the PIDU program from TSO

You can run the PIDU program from TSO by using the AOPBATCH utility, which IBM® recommends, or the BPXBATCH utility program. Name the file that contains the Printer Inventory definition statements created by the migration program in the STDIN DD statement.

If you use the AOPBATCH utility, specify the PATH environment variable; specify the LIBPATH and NLSPATH environment variables only if your installation did not install Infoprint Server files in the default directories. If you use the BPXBATCH utility, specify the LIBPATH, NLSPATH, and PATH environment variables.

When you use either the AOPBATCH or the BPXBATCH utility, also specify the AOPCONF environment variable if your Infoprint Server configuration file, aopd.conf, is not in the default directory; see z/OS Infoprint Server Customization for information about how to set these environment variables.

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

//AOPPIDU  JOB ,'pidu'
//*------------------------------------------------------------------
//*
//*  Sample JCL for running pidu in batch.
//*
//*  This JCL will use the AOPBATCH utility to run the pidu program
//*  to process Infoprint Server inventory definitions.
//*
//*  Replace hlq with the appropriate value.  Use the aopmigrt or
//*  aopmigrx job to create the hlq.invdefs data set.  You may
//*  edit the definitions in the data set as needed.
//*
//*  STDIN may also point to a sequential dataset containing other
//*  Printer Inventory Definition Utility (PIDU) statements.
//*
//*------------------------------------------------------------------
//*
//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.
//*        Built in values will work for the default installation.
//*STDENV   DD  DSN=environment,DISP=SHR