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

//DBC    PROC  ACC=,                               
//             SSID=DCSA,       ====>> SSID
//             G=DBCPLEX1,      ====>> GROUP
//             T=NO,            ====>> TRACE      
//             TIM=1440         ====>>            
//*                                                
//*********************************************************************     
//*                                                                         
//* DESCRIPTION:                                                             
//*   BMC SOFTWARE DBC SUBSYSTEM STARTUP JCL PROCEDURE.                     
//*                                                                         
//* REQUIRED DD STATEMENTS:                                                 
//*   DBCPRINT - DBC SUBSYSTEM MESSAGES
//*   DBCENV   - DBC SUBSYSTEM ENVIRONMENT INFORMATION  (PDSE)                                 
//*                                                                          
//* OPTIONAL DD STATEMENTS:                                                 
//*   STEPLIB  - OPTIONAL ONLY IF THE DBC LOAD LIBRARY IS IN THE SYSTEM     
//*              LINK LIST.                                                  
//*   DBCSECUR - DBC SUBSYSTEM SECURITY OPTIONS                             
//*   SYSPRINT - RECOMMENDED WITH RECFM=VA                  
//*   REGISTRY – NGL REGISTRY WHICH IS DEPRECATED.  IF PRESENT, DATA WILL
//*              BE MIGRATED TO THE NEW PIID REGISTRY.
//*   DOMTMPLT – TEMPLATE DATA SET USED BY THE DOM AGENT (IF PRESENT).
//*   DOMPARMS – PARMS DATA SET USED BY THE DOM AGENT (IF PRESENT).               
//*  
//*                                                                         
//* CONFIGURATION STEPS:                                                     
//*   - COPY THIS PROC TO YOUR SYSTEM PROCLIB  
//*   - ENSURE THAT THE STEPLIB DATA SETS AND ANY LOADLIB DATA   
//*     SETS USED BY THE DBC AGENTS ARE APF AUTHORIZED.          
//*                                                                
//*     FIRST CHECK THE PPPOPTS MEMBERS IN THE DBCENV DATA SET   
//*     REFERENCED IN THE DBC$STC STARTED TASK (WHERE PPP IS THE
//*     3-CHARACTER PRODUCT CODE).  IF THE KEYWORD USELOADLIB=NO
//*     IS SET FOR ALL OF THE PPPOPTS MEMBERS, THEN ONLY THE     
//*     STEPLIB OF THE DBC$STC NEEDS TO BE APF AUTHORIZED AND    
//*     SHOULD CONTAIN THE PRODUCT LOAD MODULES OR THEY SHOULD   
//*     BE IN LINKLIST.  IF THE KEYWORD EXEC-LOADLIB IS         
//*     SPECIFIED (AND USELOADLIB IS MISSING OR SET TO YES), THEN THOSE  
//*     DATA SETS NEED TO BE APF AUTHORIZED.          
//*                                                               
//*     IF NEITHER OF THOSE KEYWORDS IS PRESENT, THEN CHECK THE   
//*     PPPVVRM MEMBERS IN THE DBCENV DATA SET WHERE PPP IS THE  
//*     3-CHARACTER PRODUCT CODE AND VVRM IS THE VERSION,        
//*     RELEASE, MAINTENANCE LEVEL OF THE PRODUCT.  ANY LOADLIB  
//*     KEYWORD VALUES WILL NEED TO BE APF AUTHORIZED.  (THESE   
//*     CAN BE OVERRIDDEN BY SPECIFYING EXEC-LOADLIB IN THE     
//*     PPPOPTS MEMBER.  SEE COMMENTS IN THAT MEMBER FOR MORE    
//*     INFORMATION.)                                            
//*                                                                                             
//*   - START THE DBC ADDRESS SPACE.  FOR EXAMPLE:                          
//*       /S DBC$STC
//*   - TO STOP THE DBC ADDRESS SPACE, ISSUE ONE OF THESE CONSOLE COMMANDS:
//*       /SSID STOP
//*       /P SSID
//*     WHERE SSID IS THE DBC SUBSYSTEM ID.                                                       
//*                                                                          
//* REUSING AN EXISTING DBC:                                                
//*   IF YOU HAVE AN EXISTING DBC$STC PROC THAT IS IN USE,                  
//*   YOU SHOULD UPDATE THE EXISTING PROC TO USE THE NEW                     
//*   LIBRARIES AND NEW DD’S FROM THIS INSTALL.
//*                                                         
//*   IT IS NO LONGER NECESSARY TO SPECIFY A ZDBCSSID DD IN THE
//*   DBC STARTED TASK.  HOWEVER, PRODUCT CLISTS THAT INVOKE THE
//*   LGC MENU WILL STILL REQUIRE THAT THE ZDBCSSID BE ALLOCATED
//*   IF THERE IS MORE THAN ONE DBC IN A DIFFERENT DBC GROUP    
//*   WITH THE LGC AGENT ACTIVE ON THE SAME LPAR OR IN THE SAME
//*   SYSPLEX WHEN THE RTCS SYSTEM REGISTRY IS SHARED.  SEE THE
//*   BMC INFRASTRUCTURE ADMINISTRATION GUIDE FOR MORE          
//*   INFORMATION.                                              
//*         
//*                                                                         
//* 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      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.BMCPSWD                                   
//SYSTSPRT  DD SYSOUT=*                                     
//SYSTERM   DD SYSOUT=*,RECFM=VA
//DBCENV    DD DISP=SHR,
//          DSN=BMCPERF.&G..DC&SYSCLONE..DBCENV                         
//DBCSECUR  DD DISP=SHR,                                   
//          DSN=BMCPERF.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

BMCPSWD

Data set containing the product license keys

DBCENV

Data set containing information such as start up parameters for products that run in the DBC

DBCPRINT

Data set to dynamically write DBC messages

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

STEPLIB

DBC load library

Note: The DBC STEPLIB load library must be APF authorized.

SYSPRINT

Data set to write potential non-DBC product application messages


Related topic

Working-with-the-DBC-subsystem


 

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