DBC startup parameter
The DBC subsystem uses the DBCSECUR startup parameters. These parameters relate specifically to security customization. You identify these parameters through the DBCSECUR DD statement. DBC maintains the security parameters as a discrete set of parameters so that you can implement a different level of data set security for these parameters, if needed. For more information, see DBC-security.
The following figure shows an example of the started task JCL with parameters.
//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.
//* DBCPARMS – DBC SUBSYSTEM INITIALIZATION PARAMETERS. DBCPARMS IS
//* BEING DEPRECATED. SPECIFY THE DD AND DATASET(MEMBER)
//* FROM YOUR EXISTING DBC UNTIL ALL PRODUCTS ARE MIGRATED
//* FROM USING THE DBC REPOSITORY METHOD AND THE FOLLOWING
//* MESSAGE APPEARS IN THE DBCPRINT INDICATING THAT THE DBC
//* REPOSITORY CAN BE DELETED: BMCDBC0323I All product
//* definitions are removed from DBC repository dsname
//*
//* 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=&HLQ..&&G..DC&&SYSCLONE..DBCENV
//DBCSECUR DD DISP=SHR,
// DSN=&&DVUSUHLQ..&DVSAMPUL($SEC&&SSID)
//DOMTMPLT DD DISP=SHR,
// DSN=BMCPERF.TEST.BMCTMPLT
//DOMPARMS DD DISP=SHR,
// DSN BMCPERF.TEST.BMCPARM
// 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.
//* DBCPARMS – DBC SUBSYSTEM INITIALIZATION PARAMETERS. DBCPARMS IS
//* BEING DEPRECATED. SPECIFY THE DD AND DATASET(MEMBER)
//* FROM YOUR EXISTING DBC UNTIL ALL PRODUCTS ARE MIGRATED
//* FROM USING THE DBC REPOSITORY METHOD AND THE FOLLOWING
//* MESSAGE APPEARS IN THE DBCPRINT INDICATING THAT THE DBC
//* REPOSITORY CAN BE DELETED: BMCDBC0323I All product
//* definitions are removed from DBC repository dsname
//*
//* 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=&HLQ..&&G..DC&&SYSCLONE..DBCENV
//DBCSECUR DD DISP=SHR,
// DSN=&&DVUSUHLQ..&DVSAMPUL($SEC&&SSID)
//DOMTMPLT DD DISP=SHR,
// DSN=BMCPERF.TEST.BMCTMPLT
//DOMPARMS DD DISP=SHR,
// DSN BMCPERF.TEST.BMCPARM
Related topic
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*