Section 1, Task 3: Create a Test PDB and Process, Reduce, and Report on Data Action 2: Add or create table and variable definitions Step b: Process the staged data into PDB

Use part of STEP02 from the CMDCOLLD member of your CPMISC PDS, and edit it as follows:

 %CPSTART(MODE=BATCH,                                    #1
           ROOT='your.itsv.',
           SITELIB='your.itsv.sitelib',
           PDB='your.fax.pdb.',
           DISP=OLD,
           MXGSRC=('mxg.userid.sourclib' 'mxg.mxg.sourclib'),
           MXGLIB=mxg.mxg.formats,
           _RC=CPSTRC
           );
  %PUT CPSTART return code is &CPSTRC;                    #2
  %INCLUDE FAXES.SAS;                                     #3
  %FAXES;                                                 #3
  RUN;                                                    #3

  %CPPROCES(COLLECTR=GENERIC,TOOLNM=SASDS,GENLIB=WORK,    #4
            _RC=CPPRRC);
  %PUT CPPROCES return code is &CPPRRC;                   #5

  

Notes:

1. Invokes the IT Service Vision %CPSTART macro and references your PDB for DCOLLECT data. The PDB= parameter is set to the name (high-level-qualifiers) that you used for the new PDB. The MXG SRC= parameter and the MXGLIB= parameter are not required for this job, because your data is not from SMF.
   
   
2. This prints the value of the %CPSTART macro's return code, stored in CPSTRC.
   
   
3. The code for staging the fax data is invoked next. In this example, the code is available in the %FAXES macro.
   
   
4. The %CPPROCES macro executes to process the generic collector’s staged data into the detail level of the PDB. In this example, the macro processes data to the UFAXES table from the FAXES data set (named as the UFAXES table’s external name) in the WORK library. (By default, the COLLECTR= parameter is set to GENERIC in the %CPPROCES macro.) The COLLECTOR=GENERIC and TOOLNM= SASDS parameters are not required because these are the default values for the %CPROCES macro. For more about the %CPPROCESS macro and its parameters, see the Macro Reference documentation for IT Service Vision.

   Note that this execution of the %CPPROCES macro will process data into all tables in your active PDB that are associated with the generic collector and have a Kept status of Yes. If you want to limit this execution to just fax tables, code the table names specifically as a parameter of %CPPROCES. For an example:

   %CPPROCESS (UFAXES, COLLECTOR=GENERIC,
   TOOLNM=SASDS, GENLIB=WORK, _RC=CPPRRC);

5. This prints the value of the %CPPROCES return code, stored in CPPRRC.