In this checklist, it is assumed
that you have already installed CICS® Transaction Server for z/OS®, Version 3 Release 1 and IMS™, and
have read the program directory for each product to check for any
PTFs or APARs that you may need, as advised in the CICS Transaction Server for z/OS Installation Guide. This checklist is an example
to help you develop your own procedures for installing DBCTL, depending
on the DBCTL facilities you want to use. When developing your own
checklist, refer to the IMS Installation Guide and the IMS System Definition Reference manual manual or IMS Installation Volume 2: System Definition and Tailoring for
further guidance on IMS installation and system definition.
CICS supplies a DBCTL installation verification
procedure, DFHIVPDB. For more information
about this IVP, see the CICS Transaction Server for z/OS Installation Guide.
Using DBCTL instead of local DL/I simplifies installation, because
you do not have to perform a partial system generation of CICS to
use DL/I resources. Also, you do not have to do a partial system generation
if you use remote DL/I support.
- Prepare a PDIR that does not specify
PSBs for an application that is to be migrated to DBCTL for testing.
(See PSB directories (PDIRs).)
- Perform DBCTL startup. (See Starting DBCTL, DLISAS, and DBRC.)
- Update system procedure libraries; for example, SYS1.PROCLIB,
with the startup procedures for DBCTL, DLISAS, DBRC, and the IRLM
(if you are using it). (These startup procedures are in the IMS.PROCLIB
library.)
- Check that DBCTL has been fully installed, integrated with MVS™,
and that all required online data sets have been allocated and initialized,
where applicable. (For further guidance on doing this, see the IMS Installation Guide.)
- Perform an ACB generation to create members of the IMS.ACBLIB,
if you have not done this already.
An ACB generation should have
been performed when CICS with local DL/I was migrated
to IMS 3.1 or later. DBCTL can use ACBs generated
for a local DL/I (IMS 3.1) environment, but you should
not simply include existing ACBLIBs in the DBCTL and DLISAS JCL. Use
a pair of new, separate, ACBLIBs, which will enable you to use the IMS online
change facility. You can copy them from,
say, CICS.LOCAL.ACBLIB into a DBCTL.ONLINE.ACBLIBA and
DBCTL.ONLINE.ACBLIBB but, if you do this, be aware that you might
copy some invalid (that is, pre-IMS 3.1) ACBs. To avoid this, start
with empty ACBLIBA and ACBLIBB libraries, and regenerate ACBs as required.
- If you intend to use dynamic allocation, create DFSMDA members.
(See IMS dynamic allocation macro (DFSMDA).)
- Start DBCTL. DBCTL will issue a start command for DLISAS and DBRC.
This requires the DLISAS and DBRC JCL procedures to be in SYS1.PROCLIB.
(See Starting DBCTL, DLISAS, and DBRC.)
- Test DBCTL, for example by using the DBCTL operator command /DISPLAY
to verify that DBCTL recognizes the PSBs and DBDs you defined in the
DBCTL generation. (See Finding out current status of DBCTL activities.)
- Check your log archiving setup works before doing any more testing.
(See Log control with DBRC.) If it does not, the IMS logs
may eventually fill and stall the system.
- Assemble a DRA that will enable CICS to
connect to DBCTL. (See Defining the IMS DRA startup parameter table.)
- Start CICS and test the connection to DBCTL, using the
CDBC transaction. (See CDBC transaction for connect and disconnect.)
- Generate an initialization PLT, so that CICS can
connect to DBCTL automatically at startup time. (See Connecting DBCTL to CICS automatically.)
- Test the application(s) you defined to DBCTL.
- Set up and test recovery and restart of CICS and
DBCTL, and database recovery. (See Recovery and restart operations for DBCTL.)

[[ Contents Previous Page | Next Page Index ]]