5. Maintenance › 5.1 Create an Alternate CA MICS Environment › 5.1.1 Create a CA MICS Complex from an Existing Complex
5.1.1 Create a CA MICS Complex from an Existing Complex
************************* Important *************************
* *
* Read this entire section before you attempt to build an *
* alternate complex from an existing complex. Follow the *
* instructions carefully. *
* *
* Ensure that each job submitted throughout this checklist *
* completes with a condition code of zero. If MICSLOG is *
* present, ensure that it does not contain any error *
* messages. *
* *
* If you intend to maintain this alternate complex, it is *
* highly recommended that you complete any CA MICS product *
* changes that are in the PSP Online 'applying' state *
* before proceeding.
*
**************************************************************
__ 1. Duplicate Data Sets and HFS Directory
Duplicate each of the following data sets and the HFS
directory using different sharedprefix and
$NeuMICSROOT names:
HFS DIRECTORIES AND FILES
$NeuMICSROOT/*
INSTALLATION AND MAINTENANCE FILES
sharedprefix.MICS.TAPELOAD.CNTL
sharedprefix.MICS.TAPELOAD.LOAD
COMPLEX-LEVEL DATA SETS
sharedprefix.MICS.ASM
sharedprefix.MICS.BIN
sharedprefix.MICS.CAPACITY (if CAP is installed)
sharedprefix.MICS.CIMANAGE (if CIM is installed)
sharedprefix.MICS.CLIST
sharedprefix.MICS.CNTL
sharedprefix.MICS.DIC.TEXT
sharedprefix.MICS.DOC.TEXT
sharedprefix.MICS.DTF.INDEX (if DTF is used)
sharedprefix.MICS.GENLIB
sharedprefix.MICS.HOLD.PARMS
sharedprefix.MICS.HOLD.USER.SOURCE
sharedprefix.MICS.INC.TEXT
sharedprefix.MICS.INCLLIB
sharedprefix.MICS.ISPHLIB
sharedprefix.MICS.ISPMLIB
sharedprefix.MICS.ISPPLIB
sharedprefix.MICS.ISPSLIB
sharedprefix.MICS.ISPTLIB
sharedprefix.MICS.LOAD
sharedprefix.MICS.LOCALMOD.CNTL
sharedprefix.MICS.MACAUTOS
sharedprefix.MICS.MACLIB
sharedprefix.MICS.MCOLIB
sharedprefix.MICS.MQR.TEMPLATE
sharedprefix.MICS.MWFPDS.DATA
sharedprefix.MICS.MWFSAS.DATA
sharedprefix.MICS.OBJ
sharedprefix.MICS.PARMS
sharedprefix.MICS.PROCLIB (if user PROCLIB employed)
sharedprefix.MICS.PROTOLIB
sharedprefix.MICS.PSP.ASM
sharedprefix.MICS.PSP.BIN
sharedprefix.MICS.PSP.CLIST
sharedprefix.MICS.PSP.CNTL
sharedprefix.MICS.PSP.DIC.TEXT
sharedprefix.MICS.PSP.DOC.TEXT
sharedprefix.MICS.PSP.GENLIB
sharedprefix.MICS.PSP.INC.TEXT
sharedprefix.MICS.PSP.INCLLIB
sharedprefix.MICS.PSP.ISPHLIB
sharedprefix.MICS.PSP.ISPMLIB
sharedprefix.MICS.PSP.ISPPLIB
sharedprefix.MICS.PSP.ISPSLIB
sharedprefix.MICS.PSP.ISPTLIB
sharedprefix.MICS.PSP.LOAD
sharedprefix.MICS.PSP.MACAUTOS
sharedprefix.MICS.PSP.MACLIB
sharedprefix.MICS.PSP.OBJ
sharedprefix.MICS.PSP.PARMS
sharedprefix.MICS.PSP.PC.TEXT
sharedprefix.MICS.PSP.PROTOLIB
sharedprefix.MICS.PSP.SASFLS
sharedprefix.MICS.PSP.SOURCE
sharedprefix.MICS.PSP.USOURCE
sharedprefix.MICS.SASFLS
sharedprefix.MICS.SCREENS
sharedprefix.MICS.SOURCE
sharedprefix.MICS.TABLES
sharedprefix.MICS.TEST.INCLLIB
sharedprefix.MICS.TEST.LOAD
sharedprefix.MICS.TEST.SOURCE
sharedprefix.MICS.USER.SOURCE
Note: $NeuMICSROOT is the name of the CA MICS root
directory, as specified in the
sharedprefix.MICS.PARMS(JCLDEFC) keyword HFSROOT.
__ 2. Duplicate CA MICS SAS Libraries with Alternate Names
To create an alternate complex with SAS data libraries
from the data in the production complex SAS data
libraries, use SAS PROC COPY to duplicate the
following data sets with the alternate sharedprefix
names:
COMPLEX-LEVEL DATA SETS
sharedprefix.MICS.MCOLIB
sharedprefix.MICS.MWFSAS.DATA
sharedprefix.MICS.TABLES
sharedprefix.MICS.SCREENS
sharedprefix.MICS.CIMANAGE
sharedprefix.MICS.CAPACITY
NOTE: For the rest of this checklist, any references
to sharedprefix libraries are directing you to
the alternate sharedprefix libraries.
__ 3. Delete ISPTLIB and PARMS Members
Use ISPF Option 3.1, Library Utility, to delete these
members from sharedprefix.MICS.ISPTLIB:
ICFDBTDB ICFDBTDD ICFDSI MAF$DB MAFDBCx MAFIHTx
MAFOJTx MAFRST MAFRSTx MWF$PLB MWF$SITE
(where x is the unit database ID for each installed
unit database).
__ 4. Create an MWF Logon Procedure (Alternate Complex)
Create a MWF CLIST or TSO logon procedure for the
alternate complex using the CLIST or logon procedure
from the production complex as an example. Be sure to
change data set names to reflect the alternate
sharedprefix libraries.
__ 5. Invoke MWF CLIST (Alternate Complex)
Supply initialization parameter information by
invoking the CA MICS Workstation Facility (MWF) CLIST
for the alternate complex. The first time you enter
MWF in the alternate complex, you must select and
supply parameters for each of the first four
initialization options listed on the CA MICS
Administrator Facility (MAF) Parameters menu. The
first three options are straightforward and require
the standard CA MICS complex related information. The
fourth menu option, which enables you to customize the
user data set names allocated by MWF, MSAS, and MICF,
is discussed further.
If you need additional information about any of the
parameters, use the HELP command for each panel.
__ Select Option 4 from the CA MICS Administrator
Facility Parameters menu (5;0;4 from the CA MICS
Workstation Facility (MWF) main menu) and specify a
unique data set suffix for the user table library
allocated for each MWF user (the TABLES entry).
For example, you may include the word ALT1 in the
alternate sharedprefix user table library name to
distinguish it from the production userid user
table library names:
production complex .... MICS.PROD.USER.TABLES
alternate complex ..... MICS.ALT1.USER.TABLES
Caution: If you do not change the suffix of the
user table library name, you will corrupt
the production version of the user table
library.
__ Also from Option 4, specify a unique suffix for all
of the MICF user data sets. The following example
is a partial listing of the data sets available.
CAPACITY ........ MICS.ALT1.USER.CAPACITY
DTFINDEX ........ MICS.ALT1.USER.DTF.INDEX
DTFOUT .......... MICS.ALT1.USER.DTFOUT
LOG ............. MICS.ALT1.USER.LOG
OUTPUT .......... MICS.ALT1.USER.OUTPUT
REPORT .......... MICS.ALT1.USER.REPORT
USER ............ MICS.ALT1.USER.DATA
Caution: If you do not change the suffix of a MICF
user data set, you will corrupt the
production version of that MICF user data
set.
__ (OPTIONAL) When you exit from the MAF Options
dialog, MICF will ask you to confirm allocation of
the alternate and unique
userid.MICS.ALT1.USER.TABLES data set you defined.
Press the ENTER key to allocate
userid.MICS.ALT1.USER.TABLES.
__ 6. Edit sharedprefix.MICS.PARMS(JCLDEFC)
Change the keywords to reflect the alternate complex.
In particular check:
o The SHAREDPREFIX keyword value to reflect the
alternate sharedprefix for your alternate complex.
o If you have a user PROCLIB facility, change the
PROCLIB parameter to specify the PROCLIB data set
for the alternate complex. You may also want to
change the value of the NOTIFY and JOBNAME
keywords.
o If specified, change HFSROOT keyword value to
reflect the alternate CA MICS Root Directory.
+-------------------------------------------------+
|Reference(s): Section 5.7 (Root Directory) |
+-------------------------------------------------+
__ 7. Edit sharedprefix.MICS.PARMS(USERJCL)
Change the old sharedprefix references to the
alternate sharedprefix name. If you have a user
PROCLIB facility, code the appropriate PROCLIB
statement.
__ 8. Edit sharedprefix.MICS.PARMS(JCLNAMES)
Change the old sharedprefix references to the
alternate sharedprefix name.
+----------------------------------------------------+
| Reference(s): Section 2.3.3.3.2.3 (JCLNAMES) |
+----------------------------------------------------+
CA MICS lets you supply a unique name for CA MICS JCL
procedures. This capability is beneficial for sites
sharing a single PROCLIB data set. If the CA MICS
PROCs for the production complex must coexist with
those from the alternate complex, you must rename the
PROC names for the alternate complex to prevent
accidental replacement.
If you do not have a user PROCLIB facility, you must
use the alternate sharedprefix.MICS.PARMS(JCLNAMES) to
define unique procedure names. The following is an
example of statements that appear in
sharedprefix.MICS.PARMS(JCLNAMES):
MICSASM MICTASM
MICSCOM MICTCOM
MICSDB MICTDB&PROCIDENTIFIER
MICSDM MICTDM
MICSDOC MICTDOC
MICSDOCH MICTDOCH
MICSDU MICTDU&PROCIDENTIFIER
MICSGT MICTGT
MICSGU MICTGU
MICSNDB MICTNDB&PROCIDENTIFIER
MICSRPTS MICTRPTS
MICSSHR MICTSHR&PROCIDENTIFIER
*********************** WARNING *****************************
* *
* Ensure that any PROCLIB references maintained in job *
* submission panels under MWF refer to the correct complex *
* name before submitting jobs from the online dialogs. *
* *
* USING THE INCORRECT PROCEDURE UNDER THESE CONDITIONS *
* COULD DAMAGE YOUR PRODUCTION COMPLEX. *
* *
*************************************************************
__ 9. Edit sharedprefix.MICS.GENLIB(DBTABLE)
Delete all existing entries and insert a single line
beginning in column 1 that reads:
*::
__ 10. Edit and Execute JCLGEN0
__ Edit sharedprefix.MICS.CNTL(JCLGEN0) and change the
old sharedprefix references to the alternate
sharedprefix name.
__ Submit the following job for the alternate complex:
'sharedprefix.MICS.CNTL(JCLGEN0)'
__ 11. Execute PROCJOB1
Submit the following job:
'sharedprefix.MICS.CNTL(PROCJOB1)'
__ 12. (CONDITIONAL) Edit sharedprefix.MICS.PARMS(MQRPARMS)
Modify sharedprefix.MICS.PARMS(MQRPARMS)
if you plan to use CA MICS Q&R Workstation.
In particular,
o the MQRMSN parameter. If left unchanged, the
alternate complex will be using the same Q&R
Mainframe Server as the original complex. Modify
this parameter to define a unique name if you
plan to use a separate Q&R Mainframe Server for the
alternate complex.
+---------------------------------------------------+
|Reference(s): Q&R Workstation Administration Guide |
+---------------------------------------------------+
__ 13. (CONDITIONAL) Edit sharedprefix.MICS.PARMS(MQRUTAB)
Modify sharedprefix.MICS.PARMS(MQRUTAB)
if you plan to use CA MICS Q&R Workstation.
Verify the parameters in this file are compatible with
the settings you specified in
sharedprefix.MICS.PARMS(MQRPARMS) for this alternate
complex. The MQRPARMS MQRSEC= parameter controls what
definitions must exist in this file.
+---------------------------------------------------+
|Reference(s): Q&R Workstation Administration Guide |
| Chapter 2 |
+---------------------------------------------------+
__ 14. (CONDITIONAL) Execute JCLGEN1
If Accounting and Chargeback is installed, submit the
following job:
'sharedprefix.MICS.CNTL(JCLGEN1)'
__ 15. (CONDITIONAL) Execute JCLGEN3
Submit sharedprefix.MICS.CNTL(JCLGEN3)
if you plan to use the CA MICS Q&R Workstation
application.
This job will generate the default templates necessary
for Q&R query execution.
+---------------------------------------------------+
|Reference(s): Q&R Workstation Administration Guide |
+---------------------------------------------------+
__ 16. (CONDITIONAL) Execute TMPLTJOB
Submit sharedprefix.MICS.CNTL(TMPLTJOB)
if you plan to use CA MICS Q&R Workstation.
This job will copy the templates generated by JCLGEN3
to your sharedprefix.MICS.MQR.TEMPLATE library.
+---------------------------------------------------+
|Reference(s): Q&R Workstation Administration Guide |
+---------------------------------------------------+
__ 17. (CONDITIONAL) Protect Production Complex.
If the production complex has any Production Reporting
definitions, remove all of them from the alternate
complex in order to protect the production complex.
After executing the job below, any and all Production
Reporting definitions must be re-entered on the
alternate complex, using the unique high-level
qualifiers for the data set names.
Add a job card, specify the correct PROCLIB library,
and submit the following JCL. If you changed the name
of the MICSDM procedure in Step 7 of this checklist,
be sure to make the same name change in this JCL.
//EXEC MICSDM
//SYSTSIN DD *
ISPSTART PGM(MACTL) NEWAPPL(MWF) +
PARM(MADA LF=MWFBATCH,ADDLOGIC=MWFMFT,+
PANEL=ICFCOCL0,NONDISPL,DISPLAY,+
IF<?RC,EQ,0>,EXIT,ERROR)
Caution: DO NOT run this job against your production
complex or you will lose your MICF
production reporting definitions and will
not be able to recover without restoring
sharedprefix.MICS.ISPTLIB.
__ 18. (OPTIONAL) Back Up All Libraries (Alternate Complex)
The code and text for the products on the PSP
distribution medium are copied directly to your
sharedprefix.MICS and sharedprefix.MICS.PSP libraries.
To avoid potential space problems, compress your
sharedprefix.MICS and PSP libraries before loading the
new product.
__ 19. Review Security Requirements (Alternate Complex)
Review your security requirements for the alternate
complex. You may want to consider data set security,
as well as, authorization levels in MWF.
+----------------------------------------------------+
|Reference: Chapter 4 (Authorization Levels in MWF) |
+----------------------------------------------------+
