CDBM–database control interface
à ð
CDBM CICS-DBCTL IMS Responses Screen 1
Responses 1 to 18
More: +
DATABASE TYPE TOTAL UNUSED TOTAL UNUSED ACC CONDITIONS
ACCUNTDB UP STOPPED, NOTOPEN, NOTINIT
ADMIDX1 UP STOPPED, NOTOPEN, NOTINIT
ADMOBJ1 UP STOPPED, NOTOPEN, NOTINIT
ADMOBJ2 UP STOPPED, NOTOPEN, NOTINIT
ADMOBJ3 UP STOPPED, NOTOPEN, NOTINIT
ADMSYSDF UP STOPPED, NOTOPEN, NOTINIT
BE1CHKPT DL/I UP NOTOPEN
BE1PARTA UP STOPPED, NOTOPEN, NOTINIT
BE1PARTB UP STOPPED, NOTOPEN, NOTINIT
BE1PARTC UP STOPPED, NOTOPEN, NOTINIT
BE1PARTS UP STOPPED, NOTOPEN, NOTINIT
BE2ORDER DL/I UP NOTOPEN
BE2ORDRX DL/I UP NOTOPEN
BE2PARTS DL/I UP NOTOPEN
BE2PCUST DL/I UP NOTOPEN
BE3ORDER DL/I UP NOTOPEN
BE3ORDRX DL/I UP NOTOPEN
More...
F1=Help F3=Exit F4=Top F6=Bottom F7=Bkwd F8=Fwd F9=Retrieve F12=Cancel
á
ñ
Figure 9. CICS-DBCTL IMS responses
|DFHDBFK - The CDBM GROUP command
|file
| Before you can use the /GROUP command CDBM requires a
| file in which all your predefined commands can be stored.
| This file, DFHDBFK, is the CDBM GROUP command file. It
| is a VSAM KSDS.
| The DFHDBFK file is not required until you first attempt to
| use the /GROUP command.
| Sample JCL to enable you to define this file and optionally to
| place some of your group definitions within it is provided in
| the

CICS System Definition Guide

. The example given there
| also shows you how to batch load this file if you want to do
| so.
| You may load many definitions in this way, or load none. You
| may use whatever means you prefer to define this file and
| and to maintain its content. One method of maintainting the
| content once the file is defined is provided by CDBM which
| offers a Maintenance function for the DFHDBFK file.
| To use the the /GROUP command functions of the CDBM
| transaction, add the data set name of the group command
| file to the definition of the DFHDBFK file within the
| DFHDBCTL group. For information about how to do this, see
| the
CICS Resource Definition Guide
manual.
|Record layout in the CDBM GROUP
|command file
| Each record in the DFHDBFK file may be up to 1428
| characters long, as follows:
|The MAINTENANCE panel for DFHDBFK
| If you press the Maintenance key (PF2) on the main CDBM
| panel, you get the panel shown in Figure 10 on page 17.
|field|length|content|description
|1|12|Group|a 12-character field containing
|your chosen name for this group.
|The acceptable characters are
|A-Z 0-9 $ @ and #. Leading or
|embedded blanks are not
|allowed, but trailing blanks are
|acceptable.
|2|10|IMS
|Command
|a 10-character field containing
|any of the IMS command verbs
|that are valid for CDBM (see the
|
CICS IMS Database Control
|
Guide
for details). Leading or
|embedded blanks are not
|allowed, but trailing blanks are
|acceptable.
|Note: The validity of the IMS
|command verb is not
|checked by CDBM.
|Invalid values will be
|reported by IMS when
|the command is
|attempted.
|3|1406|IMS
|Command
|parameters
|Up to 1406 characters of
|parameters appropriate to the
|chosen IMS command verb.
|(This will often consist of lists of
|databases.)
|Note: Wildcard characters may
|not be used in the
|parameters stored in the
|CDBM Group command
|file. This is unlike the
|other functions of the
|CDBM transaction which
|permit the use of
|wildcard characters to
|describe multiple similarly
|named databases.
16 CICS Supplied Transactions