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.

Started task for the DBC subsystem

Normally, you start the DBC subsystem as a z/OS started task.

Warning

When performing an IPL, wait until after OMVS initialization has completed to start the DBC. OMVS is the task that initializes z/OS Unix System Services (USS). If DBC detects that USS is not initialized, it waits up to 30 minutes for the initialization to complete. For every minute that it waits for USS initialization, DBC issues message BMCDBC0315W:

BMCDBC0315W 10.33.23 WAITING ON UNIX SYSTEM SERVICES

After waiting for 30 minutes for USS initialization, DBC terminates with message BMCDBC0316E

BMCCDB0316E 11.03.27 UNIX SYSTEM SERVICES NOT AVAILABLE

You should add the JCL procedure for the started task into a system procedure library.

Note

For testing or trial installations, you can also start the DBC subsystem as a batch job. However, the JES initiator will be busy for the life of the DBC subsystem. BMC does not recommend this approach for non-trial installations.

The following figure shows an example of the started task for DBC.

JCL procedure for the DBC started task

//*********************************************************************
//*                                                                     
//* Description:                                                        
//*   BMC Software DBC subsystem JCL procedure for the started task.    
//*                                                                     
//* Customization Steps:                                                
//*   - Modify the DBC subsystem initialization parameters in the       
//*     member DBC$PARM that the DBCPARMS DD statement identifies.      
//*   - Modify the DBC subsystem security parameters in the member      
//*     DBC$SECU that the DBCSECUR DD statement identifies.             
//*   - Allocate Registry data set for products running under DBC       
//*     Sample define:                                                      
//*       DEFINE CLUSTER (NAME(BMCDBC.ssid.REGISTRY) -                    
//*        LINEAR CYL(25 10) SHAREOPTIONS(1,3) STORCLAS(xxxxxx))        
//*   - Add this JCL procedure to a system procedure library.           
//*   - APF authorize the DBC STEPLIB data set.                         
//*                                                                     
//* Notes:                                                              
//*   The DBC subsystem is a long-running-service address space that    
//*   normally remains active for the life of an IPL. Therefore, BMC    
//*   does not recommend starting the DBC subsystem as a batch job.     
//*   Doing so causes the JES initiator to be busy for the life of      
//*   the DBC subsystem. If you want to run the DBC as a batch          
//*   job, replace the PROC statement with a valid JCL job card.        
//*                                                                     
//*********************************************************************
//DBC      PROC SSID=,GRP=,REPMODE=
//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)
//DOMTMPLT  DD DISP=SHR,                                         
//          DSN=BMCPERF.TEST.BMCTMPLT           
//DOMPARMS  DD DISP=SHR,                                         
//          DSN=BMCPERF.TEST.BMCPARM

The following table describes DD statements that you define within the started task.

DD statements for the DBC started task

DD statement

Identifies the

STEPLIB

DBC load library

Note

The DBC STEPLIB load library must be APF authorized.

DBCPRINT

Data set to dynamically write DBC messages

SYSPRINT

Data set to write potential non-DBC product application messages

BMCPSWD

Data set containing the product license keys

DBCPARMS

DBC initialization parameters file

For more information, see DBC-startup-parameters.

DBCSECUR

Security parameters file

For more information, see DBC-security-parameters.

DOMTMPLT

(for System and SQL Performance products only) Data set that contains advisor text

DOMPARMS

(for System and SQL Performance products only) Data set that contains parameters for advisors



 

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