Section 2, Task 2: Create Your Production PDB
Action 3: Create your production PDB
  1. Create your empty production PDB.

    You can do this interactively or in batch.

    1. Interactively:

      From the main window, follow this path:

      PDB Admin -> Manage PDBs/Switch PDB -> Actions -> Create/Add

      Type in the name of the (high-level qualifiers of the) production PDB and then select OK and OK. IT Service Vision displays the PDB Allocation window. Enter your space estimates and make any other changes as needed.

      To allocate your production PDB, select Run.

      To return to your list of known PDBs, select Goback. Your new PDB is now in your list of known PDBs.

      Activate the new PDB by selecting the PDB and then selecting:

      ItemActions -> Activate -> WRITE access -> OK

    2. Batch:

      Review the ALLOC job step in the following code:

      //CMQSTART JOB (accounting info),'ITSV Quick Start',               #1
//       MSGLEVEL=(1,1),TIME=20,REGION=32M,NOTIFY=
               .
               .                                                   #2
               .
//*******************************************************************
//*                                                                **
//* Delete the old PDB data libraries, to make this job re-runnable.*
//*                                                                **
//*******************************************************************
//CLEANUP EXEC PGM=IDCAMS                                          #3
//SYSPRINT DD SYSOUT=*
//SYSIN DD DATA,DLM='$$'
  DELETE 'YOUR.NEWPDB.*'
  SET MAXCC=0
$$
//*******************************************************************
//*                                                                **
//* Allocate IT Service Vision for MVS Performance Data Base data  **
//* libraries.                                                     **
//*                                                                **
//*******************************************************************
//ALLOC   EXEC PGM=IEFBR14                                         #4
//DETAIL   DD DSN=YOUR.NEWPDB.DETAIL,DISP=(NEW,CATLG,DELETE),
//            SPACE=(CYL,(120,20)),UNIT=SYSDA                      #5       
//DAY      DD DSN=YOUR.NEWPDB.DAY,DISP=(NEW,CATLG,DELETE),
//            SPACE=(CYL,(99,25)),UNIT=SYSDA
//WEEK     DD DSN=YOUR.NEWPDB.WEEK,DISP=(NEW,CATLG,DELETE),
//            SPACE=(CYL,(30,25)),UNIT=SYSDA
//MONTH    DD DSN=YOUR.NEWPDB.MONTH,DISP=(NEW,CATLG,DELETE),
//            SPACE=(CYL,(99,10)),UNIT=SYSDA
//YEAR     DD DSN=YOUR.NEWPDB.YEAR,DISP=(NEW,CATLG,DELETE),
//            SPACE=(CYL,(20,5)),UNIT=SYSDA
//ADMIN    DD DSN=YOUR.NEWPDB.ADMIN,DISP=(NEW,CATLG,DELETE),
//            SPACE=(TRK,(15,10)),UNIT=SYSDA
//COLLECT  DD DSN=YOUR.NEWPDB.COLLECT,DISP=(NEW,CATLG,DELETE),
//            SPACE=(CYL,(9,9)),UNIT=SYSDA
//PDBWORK  DD DSN=YOUR.NEWPDB.PDBWORK,DISP=(NEW,CATLG,DELETE),
//            SPACE=(CYL,(180,80)),UNIT=SYSDA

      Notes:

      1. The JCL job card, which will need to be changed as appropriate for your site.

      2. The comments explaining the job and listing the customization instructions. Omitted for the sake of brevity.

      3. The CLEANUP job step, which invokes IDCAMS to delete the datasets for the PDB that you will allocate. If you need to rerun the job, this job step makes certain that the previous PDB is out of the way before you allocate a new one with the same name.

        Be certain that the PDB names in the CLEANUP job step and ALLOC job step match. In the remainder of this document, the PDB will be referred to as the 'quick-start' PDB or test PDB.

        Warning: This will delete all datasets that started with this prefix, so be sure that you have no other datasets that begin with the same qualifiers!

      4. The ALLOC job step, which invokes IEFBR14 to allocate the datasets for the PDB.

      5. You may need to adjust the SPACE= parameter and/or the UNIT= parameter for the PDB datasets.

  1. Copy your test PDB's structure, setting, and data to your production PDB.

    Set up and submit a batch job with a SAS job step (using JCL like that used in the LOAD job step in the CMQSTART job, except that you can remove the definition of the SMF ddname). In the job step, include the following macro calls:

       %CPSTART(MODE=BATCH SYSTEM=MVS,
            ROOT='itsv.prefix.',
            PDB='your.test.pdb',
            DISP=OLD,SHARE=N/A,
            MXGSRC=('MXG.USERID.SOURCLIB' 'MXG.MXG.SOURCLIB'),
            MXGLIB=MXG.MXG.FORMATS
	    );

   %CPDBCOPY(your.test.pdb, your.production.pdb);

    where your.production.pdb is the high-level qualifiers of your production PDB and the other values are as described in Section 1, Task 3: Create a Test PDB and Process, Reduce, and Report on Your Data.