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


Restoring the Printer Inventory from a GDG

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

Restoring the Printer Inventory from a GDG

You can restore the Printer Inventory from a generation data group (GDG). These steps show how to restore the latest data set in the GDG.

Rule: Do not use copy commands to restore the Printer Inventory because the copy might contain inconsistent data that makes the Printer Inventory unusable.

Before you begin: Make sure that you are a member of the AOPADMIN group and have UPDATE access to the AOP.ADMINISTRATOR resource profile in the PRINTSRV class.

To restore the Printer Inventory from a GDG:

  1. Stop Infoprint Server. For example, enter this MVS™ command to run the AOPSTOP JCL procedure:
    START AOPSTOP

    _______________________________________________________

  2. Move the /var/Printsrv/master.v2db, /var/Printsrv/jestoken. v2db, and pwjestoken.v2db files to another directory. Save these files until you have restored the Printer Inventory, restarted Infoprint Server, and run with the restored Printer Inventory for a few days.

    _______________________________________________________

  3. Start Infoprint Server. For example, enter this MVS command to run the AOPSTART JCL procedure:
    START AOPSTART
    Do the next step immediately after you start Infoprint Server.

    _______________________________________________________

  4. Use one of these methods to restore the Printer Inventory from the most recent generation data set of a GDG named hlq.INV.BACKUPS:
    • Run the pidu command as a batch job:
      //AOPRINV  JOB  MSGLEVEL=(1,1)
      //STEP1    EXEC PGM=AOPBATCH,PARM='/pidu //DD:INVENT'
      //INVENT   DD   DISP=SHR,DSN=hlq.INV.BACKUPS(0)
      //STDOUT   DD   SYSOUT=*
      //STDERR   DD   SYSOUT=*
      //STDENV   DD   *
      NLSPATH=/usr/lpp/Printsrv/En_US/%N
      AOPCONF=/etc/Printsrv/aopd.conf
      /*
       
      If Infoprint Server files are located in the default locations, you can omit the STDENV DD statement.
    • Run the pidu command from the sh command:
      1. Create a file to contain a short shell script, such as /u/userid/do.restore. Your login user ID is userid. This example shows how to restore the Printer Inventory from the most recent generation data set of a GDG named hlq.INV.BACKUPS. This example uses the UNIX redirection symbols (> for stdout and 2> for stderr) to redirect command output to file pidu.output and command errors to file pidu.errors:
        pidu //\'hlq.INV.BACKUPS\(0\)\' >pidu.output 2>pidu.errors  

        _______________________________________________________

      2. Run the sh command to restore the Printer Inventory by running the pidu command in the /u/userid/do.restore shell script:
        sh /u/userid/do.restore
        Tip: Use the sh command to run the pidu command in the /u/userid/do.restore shell script instead of running the pidu command directly. GDG relative generations are maintained for the duration of the UNIX shell created when you log in to z/OS UNIX System Services. Using the sh command to create a new shell ensures that the current generation is always 0. For example, these commands create a new generation data set and then display the generation data set prior to the newly created data set:
        pidu -c "export //\'hlq.INV.BACKUPS\(\+1\)\';"
        cat //\'hlq.INV.BACKUPS\(0\)\'
        To create a new generation data set and then display that data set, you would need to run this command:
        pidu -c "export //\'hlq.INV.BACKUPS\(\+1\)\';"
        cat //\'hlq.INV.BACKUPS\(\+1\)\'  

    _______________________________________________________

Related information:

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014