|
|
|
The CA MICS Database may contain one or more database
units. This section provides a worksheet on which you can
define the database units for the complex which you are
planning to install. This worksheet is not used by CA MICS
in the installation process, but is meant as a reference for
you. Some of the information contained on this worksheet is
repeated in other parameter members, and is included here for
convenience. The definitions on this worksheet are made when
the complex is first installed, and then reviewed and
modified any time the complex is changed.
The worksheet for defining the Database Complex is contained
in Figure 2-4. One set of definition statements should be
completed for each database unit that you plan to install.
The statements are explained below. Most of the information
provided in these statements is also used in a parameter
member. When this is the case, a reference to the section
discussing the parameter member is listed in parentheses
after the description. More detailed discussions of the
information requested may be found in the referenced section.
Sharedprefix: The name used to form the data set names for
data sets shared by all database units in the complex.
The SHAREDPREFIX must be different from all PREFIXes and
TAPEPREFIXes. (2.3.3.2.1.1)
Database Name: A 1 to 8 character name used to identify the
database unit during installation.
(section 2.3.3.2.1.1)
Database Identifier: A 1 character (alphanumeric) ID used
to form a unique name for JCL procedures, CLISTs, and
macro names which are generated for each database unit.
(2.3.3.2.1.1)
Database Type: PRIMARY, UNIT, or TEST. The first unit
installed should be a TEST unit. The first production
unit installed should be designated the PRIMARY unit.
Other production units are given a type of UNIT. TEST
is treated differently by the JCL generation process and
by CA MICS Accounting and Chargeback. (2.3.3.2.1.1)
Components: The list of components to be installed in this
unit. The list is based on the products your site is
licensed for. Note that the Base Component must always
be installed. (2.3.3.2.1.1)
ORGSYSIDs: The original (SMF) sysid of the input data.
(2.3.2.2)
LOGSYSIDs: A logical system ID. It is mapped back to the
ORGSYSID. Most CA MICS files are organized with this ID
as the highest sort key. (2.3.2.2)
Prefix: The name used to form the data set names for data
sets associated with a database unit. The PREFIX must
be different from all other PREFIXes, and SHAREDPREFIXes.
(2.3.3.2.1.1)
Tapeprefix: The name used to form the data set names for all
of the tape data sets associated with a database unit.
The TAPEPREFIX must be different from all other
TAPEPREFIXes, and SHAREDPREFIXes. (2.3.3.2.1.1)
Archiving: Indicate the types of archiving you wish
performed for each database unit. (2.3.3.2.1.3)
+--------------------------------------------------------------------------+ | INSTALLATION PREPARATION WORKSHEET: Database Complex Definition | | | | | | Reference Sections: 2.3.1.4 | +--------------------------------------------------------------------------+ | | | Sharedprefix: ______________ (Maximum of 14 characters) | | | | | | | | Database Name: ________ (max of 8 characters) | | Database Identifier _ (A - Z, 0 - 9, blank not allowed) | | Database Type: _______ (PRIMARY, UNIT, SPECIAL, OR TEST) | | Components: ___ ___ ___ ___ ___ ___ ___ ___ | | ORGSYSIDs: ____ ____ ____ ____ ____ ____ ____ ____ | | LOGSYSIDs: ____ ____ ____ ____ ____ ____ ____ ____ | | Prefix: ______________ (Maximum of 14 characters) | | Tapeprefix: ______________ (Maximum of 14 characters) | | Archiving: Audit Archiving: ___ (YES/NO) | | Weekly History Archiving: ___ (YES/NO) | | Monthly History Archiving: ___ (YES/NO) | | | | | | Database Name: ________ (max of 8 characters) | | Database Identifier _ (A - Z, 0 - 9, blank not allowed) | | Database Type: _______ (PRIMARY, UNIT, SPECIAL, OR TEST) | | Components: ___ ___ ___ ___ ___ ___ ___ ___ | | ORGSYSIDs: ____ ____ ____ ____ ____ ____ ____ ____ | | LOGSYSIDs: ____ ____ ____ ____ ____ ____ ____ ____ | | Prefix: ______________ (Maximum of 14 characters) | | Tapeprefix: ______________ (Maximum of 14 characters) | | Archiving: Audit Archiving: ___ (YES/NO) | | Weekly History Archiving: ___ (YES/NO) | | Monthly History Archiving: ___ (YES/NO) | | | | | | | | | +--------------------------------------------------------------------------+ | ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. | +--------------------------------------------------------------------------+
Figure 2-4. Database Complex Definition Worksheet
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |