Skip to Content
Information
Space announcement We are no longer updating this version of the documentation for the infrastructure components (DBC, LGC, and NGL).  You can no longer leave comments on it. For the latest version of the documentation, see Common Mainframe Infrastructure 2022 release.

Modifying the DBC started task

Running the DBC$STC started task procedure starts the DBC subsystem.

Before you begin

The DBC SSID referenced in the started task procedure must match what you are using for this LPAR. You can use the same started task member on each LPAR by specifying the SSID value in the startup command.

The following figure illustrates that the DBC SSID is also used for the NGL REGISTRY name, as a method to keep it unique per DBC task, but this is not a requirement.

Example of DBC started task

//DBC    PROC  ACC=4111,                          
//             SSID=DC01,       ====> SSID             
//             G=FDR1PLEX,      ====> GROUP        
//             T=NO,            ====> TRACE       
//             TIM=1440         ====>             
//*                                               
//DBC      EXEC PGM=DBCMAIN,REGION=0M,ACCT=&ACC,TIME=&TIM,       
//         PARM='SSID=&SSID,GROUP=&G,TRACE=&T'                   
//STEPLIB  DD DSN=BMCPERF.TEST.BMCLINK,  
//            DISP=SHR                                    
//DBCPRINT  DD SYSOUT=*,RECFM=VA                                 
//SYSPRINT  DD SYSOUT=*,RECFM=VA                                 
//BMCPSWD   DD DISP=SHR,                                         
//          DSN=BMCPERF.TEST.BMCLINK            
//SYSTSPRT  DD SYSOUT=*                                          
//SYSTERM   DD SYSOUT=*,RECFM=VA                                 
//DBCPARMS  DD DISP=SHR,                                         
//          DSN=BMCPERF.TEST.UBMCSAMP($DBC&SSID)
//DBCSECUR  DD DISP=SHR,                                         
//          DSN=BMCPERF.TEST.UBMCSAMP($SEC&SSID)
//REGISTRY  DD DISP=SHR,                                         
//          DSN=BMCPERF.TEST..&SSID.NGLRGRY         
//DOMTMPLT  DD DISP=SHR,                                         
//          DSN=BMCPERF.TEST.BMCTMPLT           
//DOMPARMS  DD DISP=SHR,                                         
//          DSN=BMCPERF.TEST.BMCPARM
Warning

Note

The DOMTMPLT and DOMPARMS DD statements are used only by System and SQL Performance products. These DD statements might be missing or commented out if you do not have those products.

To modify the DBC started task

  1. (optional) Change the ACC= value at the top of the PROC (if necessary) for accounting information.

  2. (optional) Add a step in the PROC to APF authorize anything in your STEPLIB, as shown in the following example:

    //AUTH1    EXEC  PGM=JTHAPF00,ACCT=&ACC,PARM='DBC,STEPLIB'

To setup another DBC

The DBC$STC started task references two members for the DBC SSID:

  • $DBC&ssid
  • $SEC&ssid
  1. Replicate the members in the appropriate user or runtime data set to use the naming convention for the DBC SSID for this LPAR.

  2. Edit the $DBC&ssid member to make the DBC Repository unique for each LPAR, perform one of the following tasks:

    • Change the DBC repository name for this LPAR

    • Use the &SSID symbolic for the repository name in that member. The SSID value is resolved to be the DBC SSID from the SSID parameter in the DBC$STC PROC.

      <name>BMCPERF.&SSID..DBCREPOS</name>
    Warning

    Note

    The $SEC&ssid member contains only one parameter. If you want this parameter to be the same for all DBC subsystems in this DBC group, hard code the member name and share it among all DBC subsystems.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Common mainframe infrastructure 2016 release