3. Installation › 3.8 Installation Checklists › 3.8.6 Loading New Products
3.8.6 Loading New Products
************************ BACKGROUND *************************
* *
* The CA MICS tape or ESD PAX file includes code and *
* documentation for all CA MICS products. It also *
* delivers maintenance and enhancements for your licensed *
* CA MICS products as part of the CA MICS Product Service *
* Pack (PSP). *
* *
* Use these instructions to install newly licensed CA MICS *
* products into an existing CA MICS complex. Since product *
* installation may need the most current CA MICS *
* maintenance, the installation process will check to *
* ensure that the most recent PSP maintenance has been *
* loaded from the distribution medium. *
* *
* CA LMP keys are required for each product you install. *
* You must ensure that the keys for new products have been *
* installed on each CPU on which the new products will be *
* installed. *
* *
*************************************************************
To load the new product, complete the following steps:
__ 1. Ensure Libraries are Cataloged
Make sure that the following libraries are cataloged.
If they are not, contact Technical Support at
http://ca.com/support.
The libraries are:
sharedprefix.MICS.PSP.CNTL
sharedprefix.MICS.PSP.PC.TEXT
sharedprefix.MICS.PSP.ISPTLIB
sharedprefix.MICS.TAPELOAD.CNTL
__ 2. Ensure Libraries are Not Migrated
Ensure your sharedprefix.MICS and
sharedprefix.MICS.PSP libraries are not migrated.
Their data set names begin with the following
qualifiers:
sharedprefix.MICS (complex libraries)
sharedprefix.MICS.PSP (PSP libraries)
__ 3. Compress Libraries
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.
__ 4. Back Up Complex and PSP Libraries
Create a backup of all sharedprefix, prefix, and
sharedprefix.MICS.PSP libraries.
__ 5. Ensure PSP Libraries have been Refreshed
Ensure that your Product Support Program (PSP)
libraries have been previously refreshed from the most
recently available PSP distribution. If not, it would
be best to refresh your PSP libraries before
continuing.
__ 6. Ensure MWF is Initialized
Refer to the "How to Use the PSP" guide for detailed
instructions on initializing the CA MICS Workstation
Facility (MWF) and using PSP Online to apply product
changes.
__ 7. Review the Cover Letter
Review the cover letter and associated product
maintenance letters (PML) for the latest important
technical information.
__ 8. Install LMP Keys for New Products
You are required to obtain and install a CA LMP key
for each CA MICS product. One key is required for
each CPU that the product will be loaded to. Refer to
section 3.2.2 for more information. If there are
questions about CA LMP keys, contact Technical
Support at http://ca.com/support.
__ 9. Load Optional Products
Optional products can be loaded from either tape or
ESD PAX. There are two ways to load the products,
either via the panel-driven load process or via
pre-existing JCL. Select one of the following
substeps to load the product:
Step 9a. - Panel-driven process that supports tape
and ESD PAX.
Step 9b. - ESDPLD1 - JCL supporting ESD PAX
Step 9c. - PRODLD1 - JCL supporting tape
__ 9a. Load Optional Products Using MWF
This step uses a panel-driven process to generate the
JCL to load your optional products to DASD. It
combines parameters you provide on MWF panels with
parameters that were specified during the
complex-level JCLGEN, and generates the JCL to
load from the PSP distribution data sets.
__ Select the MWF panel called Select New Products and
Submit the Product Load Job (MWF;5;2;3;4).
__ Type the following parameters on the panel:
SR is the new product being loaded. Type the
three-letter code of the new product.
If you are loading more than one new
product, each code must be separated by a
blank.
Note: Only specify your NEW products! If
you specify products that are already
installed, they will be overlayed. This
can critically impact your CA MICS
database.
Use the MWF CONFIG command to help you
determine which CA MICS products are
installed.
From When the incoming PSP distribution files
Tape are on a tape, specify YES. Otherwise,
specify NO or leave this blank. Note that
this option is mutually exclusive with the
"From ESD-DASD" option below.
Tape is the volume serial number of the PSP
VOLSER distribution tape that you want to load.
Tape is the expiration date for a foreign tape
EXPDT if your tape management system requires
one.
Tape is the unit name of the tape device on
which the CA MICS distribution tape is to
be mounted.
From When the CA MICS distribution files come
ESD- from an ESD PAX file, specify YES.
DASD Otherwise, specify NO or leave this blank.
Note that this option is mutually exclusive
with the "From Tape" option above.
High is the high level data set qualifier(s)
Level that are common to all the incoming PSP
Qualif- distribution files on DASD. It corresponds
ier to "yourHLQ" used in the ESD PAX UNZIPJCL
job.
PSP is the volume serial number of the
VOLSER direct access storage device to be used to
store the new PSP libraries. This will be
used as the default VOLSER for allocation
of new PSP data sets. It can be overridden
for individual data set names by modifying
entries in PSPOVER as described in Appendix
A.1 of the How To Use The PSP guide. If
the "SMS JCL Tailoring" option (below) is
YES, this parameter is ignored.
PSP is the unit name of the direct access
UNIT storage device to be used to store the new
PSP data sets. This will be used as the
default unit for allocation of new PSP data
sets. It can be overridden for individual
data set names by modifying entries in
PSPOVER as described in Appendix A.1. If
the "Omit UNIT & VOL=SER from JCL" option
(below) is YES, this parameter is ignored.
PSP is the SMS STORCLAS to be used to store the
STOR- new PSP data sets. This will be used as
CLAS the default STORCLAS for allocation of new
PSP data sets. It can be overridden for
individual data set names by modifying
entries in PSPOVER as described in Appendix
A.1.
PSP is the SMS DATACLAS to be used to store the
DATA- new PSP data sets. This will be used as
CLAS the default DATACLAS for allocation of new
PSP data sets. It can be overridden for
individual data set names by modifying
entries in PSPOVER as described in Appendix
A.1.
PSP is the SMS MGMTCLAS to be used to store the
MGMT- new PSP data sets. This will be used as
CLAS the default MGMTCLAS for allocation of new
PSP data sets. It can be overridden for
individual data set names by modifying
entries in PSPOVER as described in Appendix
A.1.
PSP can be either blank or LIBRARY. Specify
DSNTYPE LIBRARY to allocate new PSP data sets as
partitioned data set extended (PDSE) data
sets. It can be overridden for individual
data set names except for the PSP LOAD
library by modifying entries in PSPOVER as
described in Appendix A.1.
PSP is the disposition of all PSP libraries
DISP except sharedprefix.MICS.PSP.CNTL,
PSP.PC.TEXT, and PSP.ISPTLIB.
If the libraries listed below exist,
specify "OLD,KEEP". If the libraries do
not exist, specify "NEW,CATLG,DELETE".
sharedprefix.MICS.PSP.ASM
sharedprefix.MICS.PSP.BIN
sharedprefix.MICS.PSP.CLIST
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.LOAD
sharedprefix.MICS.PSP.MACAUTOS
sharedprefix.MICS.PSP.MACLIB
sharedprefix.MICS.PSP.OBJ
sharedprefix.MICS.PSP.PARMS
sharedprefix.MICS.PSP.PROTOLIB
sharedprefix.MICS.PSP.SASFLS
sharedprefix.MICS.PSP.SOURCE
sharedprefix.MICS.PSP.USOURCE
If your site does not have its PSP
libraries, new PSP libraries will be
allocated as part of the INSTALL steps.
These PSP libraries will contain all
product changes required to install your
new products. For more information about
the PSP libraries, see the How To Use The
PSP guide.
PSP is the block size that will be used to
BLOCK- allocate your new PSP data sets. Do not
SIZE override the default of 6160 unless
required by your site.
Loader specifies the program name of the IBM
Loader at your site. This is typically
IEWLDRGO, HEWLDRGO, or LOADER. If in doubt,
contact your system programmer.
Region specifies the region size for each step.
Size The default of 4096K should be adequate.
Omit will cause the JCL to be generated without
UNIT & "VOL=SER=" or "UNIT=" parameters in DD
VOL=SER statements for temporary disk data sets or
From for allocating new PSP data sets. If the
JCL System Managed Storage (DFSMS)
implementation at your site requires that
UNIT= and VOL=SER= parameters be omitted,
then specify YES, otherwise, specify NO.
Edit is either YES or NO. If YES, then you will
gener- be given an opportunity to edit the load
ated JCL before it is submitted.
JCL
__ When your parameters are complete, do one of the
following:
__ Press END to continue
OR
__ Type CANCEL and press ENTER to stop the process.
__ If you pressed END and if Edit generated JCL was
YES, then you will see a temporary data set
containing the generated tape load job.
__ Review the JCL and verify that it conforms to
your site's standards. Make a copy of the JCL
in a permanent data set for future reference.
__ Press END to submit the job.
Note: Modules are written to disk by executing the
program named LPEBLDD. It runs as a
"non-authorized" program. Some mainframe security
systems, such as CA Top Secret, have a feature that
restricts non-authorized programs from writing
authorized load modules. (An authorized load module
is link-edited with an attribute of AC(1).) If your
site has this security feature activated and is
licensed for the CA MICS Space Collector (VCC),
then the load job will fail with an S913 ABEND
while trying to write an authorized VCC load
module. To prevent this ABEND, request your
security administrator to permit LPEBLDD to write
authorized load modules.
__ Exit PSP Online. Do this by pressing END until the
CA MICS Administrator Facility panel is displayed.
__ After the job finishes, check the return codes.
All steps must have a return code of zero except
the following:
COMPABND must not execute. It only executes if the
PSP refresh requirement is not met. It will force
the job to ABEND.
PSPCHK2 may be 0 or 4.
#ASCOPY2 and PSPUPDTE must be 0 when PSPCHK2 is 4.
#ASCOPY2 and PSPUPDTE will not execute when PSPCHK2
is 0. This is normal.
Any other return codes are errors. If there is an
error, you must correct it and resubmit the job.
If the error persists, contact Technical Support.
__ Proceed to Step 10.
__ 9b. Load Optional Products Using ESDPLD1
This step supports loading your optional products to
disk from an ESD PAX file.
******************************************************
* CAUTION: Do NOT execute step 9b if you have *
* already completed step 9a or Step 9c. *
******************************************************
__ Edit sharedprefix.MICS.TAPELOAD.CNTL(ESDPLD1).
Provide a JOB statement and complete the following
symbolic JCL parameters on the LOADPROD EXEC
statement:
//LOADPROD EXEC LOADPROC,
// YOURHLQ='______________',
// SPREFIX='______________',
// SMICS='MICS.',
// SASPFX='_______________',
// SASNAME='entry',
//* SASENV='TKMVSENV(TKMVSENV)',
// SASCFG1='config',
//* SASCFG2='CONFIG(COMMON)',
//* SASCFG3='CONFIG(ENW0)',
//* SASCFG4='CONFIG(SITE)',
// LANG1='',
// LANG2='',
// PSPVOL=,
// PSPDSP='________',
// PSPUNIT=,
// PSPSTORC=,
// PSPDATAC=,
// PSPMGMTC=,
// PSPDSNT=,
// BLOCK=6160,
// WKUNIT=SYSDA ,
// SR='___',
// LOADER=IEWLDRGO
You must complete the following parameters on the
LOADPROD EXEC statement, not those on the PROC
statement:
YOURHLQ specifies the high level qualifier of the
ESD PAX data sets. It must be replaced with
the "yourHLQ" used in the ESD PAX UNZIPJCL
job.
SPREFIX is the standard CA MICS sharedprefix. Do
not end the sharedprefix with a period (.).
SMICS is the MICS level for the sharedprefix.MICS
and sharedprefix.MICS.PSP libraries.
Specify this parameter with a trailing
period. If you have specified NOMICSLEVEL
on the sharedprefix statement in the
JCLDEFC member of sharedprefix.MICS.PARMS,
you must change SMICS to null (SMICS=,).
SASPFX specifies the common data set name prefix
for your SAS libraries. Note that this name
is specified with no trailing period. This
prefix is used in the following DDs to form
the names of your site's SAS libraries used
for CA MICS:
STEPLIB - SAS load library
TKMVSENV- SAS environment file
CONFIG - SAS CNTL library that holds a
SAS system configuration file
SASHELP - SAS help library
SASMSG - SAS message library
Review the data set names specified in the
DDs. If they are incorrect, correct the
names and comment out SASPFX.
SASNAME specifies the program name of the SAS
Program Product in the load library
specified in the STEPLIB DD.
SASENV is the name of the SAS environment file.
This file is needed only if you have this
SAS library. If you do not, you must
comment out all TKMVSENV DD statements.
SASCFG1 provides the library name suffix and
member name of your SAS configuration
file.
For SAS version 9.1.3, normally the
library is the SAS CNTL data set and the
member is BATW0.
For SAS version 9.2 and above, normally the
library is the SAS CONFIG data set and the
member is BATCH.
SASCFG2 provides the library name suffix and
member name of an additional configuration
file needed for SAS versions 9.2 and
above. Normally this is a member of the
SAS CONFIG data set and the name is
COMMON.
SASCFG3 provides the library name suffix and
member name of an additional configuration
file needed for SAS versions 9.2 and
above. Normally this is a member of the
SAS CONFIG data set and the name is ENW0.
SASCFG4 provides the library name suffix and
member name of an additional configuration
file needed for SAS versions 9.2 and
above. Normally this is a member of the
SAS CONFIG data set and the name is SITE.
LANG1 is the language code required with SAS
Versions 9 and higher, for example, EN
stands for English. The value is blank for
SAS Version 8.
LANG2 is the encoding value required with SAS
Version 9 and higher. The value for
EBCDIC is W0 and must have a trailing
period (.). The value is blank for SAS
Version 8.
PSPUNIT specify the unit name and volume serial
and number of the direct access storage device
PSPVOL to be used to store the new PSP libraries.
These parameters will be used as default
parameters for allocation of new PSP data
sets. They can be overridden for individual
data set names by modifying entries in
PSPOVER as described in Appendix A.1. If
you do not need to specify a parameter for
PSPUNIT, code it as null (that is,
'PSPUNIT=,'). Likewise, if you do not need
to specify a parameter for PSPVOL, code it
as null (that is, 'PSPVOL=,').
PSP is the SMS STORCLAS to be used to store the
STORC new PSP libraries. This will be used as
the default STORCLAS for allocation of new
PSP data sets. It can be overridden for
individual data set names by modifying
entries in PSPOVER as described in Appendix
A.1. If you do not need to specify a
parameter for PSPSTORC, code it as null
(that is, 'PSPSTORC=,').
PSP is the SMS DATACLAS to be used to store the
DATAC new PSP libraries. This will be used as
the default DATACLAS for allocation of new
PSP data sets. It can be overridden for
individual data set names by modifying
entries in PSPOVER as described in Appendix
A.1. If you do not need to specify a
parameter for PSPDATAC, code it as null
(that is, 'PSPDATAC=,').
PSP is the SMS MGMTCLAS to be used to store the
MGMTC new PSP libraries. This will be used as
the default MGMTCLAS for allocation of new
PSP data sets. It can be overridden for
individual data set names by modifying
entries in PSPOVER as described in Appendix
A.1. If you do not need to specify a
parameter for PSPMGMTC, code it as null
(that is, 'PSPMGMTC=,').
PSP can be either blank or LIBRARY. Specify
DSNT LIBRARY to allocate new PSP data sets as
partitioned data set extended (PDSE) data
sets. It can be overridden for individual
data set names except for the PSP LOAD
library, by modifying entries in PSPOVER
as described in Appendix A.1.
PSPDSP is the disposition of all PSP libraries
except sharedprefix.MICS.PSP.CNTL,
PSP.PC.TEXT, and PSP.ISPTLIB. If the
following libraries exist, use the value
'OLD,KEEP'. If the following libraries do
not exist, use the value
'NEW,CATLG,DELETE'. Verify that you have
the sharedprefix.MICS.PSP.CNTL,
PSP.PC.TEXT, and PSP.ISPTLIB libraries
already allocated.
sharedprefix.MICS.PSP.ASM
sharedprefix.MICS.PSP.BIN
sharedprefix.MICS.PSP.CLIST
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.LOAD
sharedprefix.MICS.PSP.MACAUTOS
sharedprefix.MICS.PSP.MACLIB
sharedprefix.MICS.PSP.OBJ
sharedprefix.MICS.PSP.PARMS
sharedprefix.MICS.PSP.PROTOLIB
sharedprefix.MICS.PSP.SASFLS
sharedprefix.MICS.PSP.SOURCE
sharedprefix.MICS.PSP.USOURCE
WKUNIT specifies the unit name for a direct access
work device.
BLOCK is the block size value used for the new
PSP libraries. Do not override the default
of 6160 unless required by your site.
SR is the three-letter code for the new product
being loaded.
If you are loading more than one new
product, each code must be separated by a
blank.
Note: Only specify your NEW products! If
you specify products that are already
installed, they will be overlayed. This
can critically impact your CA MICS
database.
Use the MWF CONFIG command to help you
determine which CA MICS products are
installed.
LOADER specifies the program name of the IBM
Loader at your site. This is typically
IEWLDRGO, HEWLDRGO, or LOADER. If in doubt,
contact your system programmer.
__ Submit 'sharedprefix.MICS.TAPELOAD.CNTL(ESDPLD1)'.
Note: Modules are written to disk by executing the
program named LPEBLDD. It runs as a
"non-authorized" program. Some mainframe security
systems, such as CA Top Secret, have a feature that
restricts non-authorized programs from writing
authorized load modules. (An authorized load
module is link-edited with an attribute of AC(1)).
If your site has this security feature activated
and is licensed for the CA MICS Space Collector
(VCC), then the load job will fail with an S913
ABEND while trying to write an authorized VCC load
module. To prevent this ABEND, request your
security administrator to permit LPEBLDD to write
authorized load modules.
__ After the job finishes, check the return codes.
All steps must have return codes of zero except the
following:
COMPABND must not execute. If it does execute, the
PSP refresh level requirement has not been met and
it will force the job to ABEND.
PSPCHK2 might be 0 or 4.
#ASCOPY2 and PSPUPDTE must be 0 if PSPCHK2 is 4.
#ASCOPY2 and PSPUPDTE will not execute if PSPCHK2
is 0. This is normal.
Any other return codes are errors. If there is an
error, you must correct it and resubmit the job.
If the error persists, contact Technical Support at
http://ca.com/support.
__ Proceed to Step 10.
__ 9c. Load Optional Products Using PRODLD1
This step supports loading your optional products to
disk from a magnetic tape.
******************************************************
* CAUTION: Do NOT execute step 9c if you have *
* already completed step 9a or Step 9b. *
******************************************************
__ Edit sharedprefix.MICS.TAPELOAD.CNTL(PRODLD1).
Provide a JOB statement and complete the following
symbolic JCL parameters on the LOADPROD EXEC
statement:
//LOADPROD EXEC LOADPROC,
// SPREFIX='______________',
// SMICS='MICS.',
// SASPFX='_______________',
// SASNAME='entry',
//* SASENV='TKMVSENV(TKMVSENV)',
// SASCFG1='config',
//* SASCFG2='CONFIG(COMMON)',
//* SASCFG3='CONFIG(ENW0)',
//* SASCFG4='CONFIG(SITE)',
// LANG1='',
// LANG2='',
// TUNIT='____',
// TVOL=______,
// TEXPDT=98000,
// PSPVOL=,
// PSPDSP='________',
// PSPUNIT=,
// PSPSTORC=,
// PSPDATAC=,
// PSPMGMTC=,
// PSPDSNT=,
// BLOCK=6160,
// WKUNIT=SYSDA,
// SR='___',
// LOADER=IEWLDRGO
You must complete the following parameters on the
LOADPROD EXEC statement, not those on the PROC
statement:
SPREFIX is the sharedprefix for the shared CA MICS
and PSP libraries. Note that this is
specified with no trailing period (for
example, DB1.SP rather than DB1.SP.).
SMICS is the MICS level for the
sharedprefix.MICS and
sharedprefix.MICS.PSP libraries. Specify
this parameter with a trailing period. If
you have specified NOMICSLEVEL on the
sharedprefix statement in the JCLDEFC
member of sharedprefix.MICS.PARMS, you
must change SMICS to null (SMICS=,).
SASPFX is the common data set name prefix for
your SAS libraries. Note that this name
is specified with no trailing period.
This prefix is used in the following DDs
to form the names of your site's SAS
libraries for CA MICS:
STEPLIB - SAS load library
TKMVSENV- SAS environment file
CONFIG - SAS CNTL library that holds a
SAS system configuration file
SASHELP - SAS help library
SASMSG - SAS message library
Review the data set names specified in the
DDs. If they are incorrect, correct the
names and comment out SASPFX.
SASNAME is the program name of the SAS Program
Product in the load library specified in
the STEPLIB DD.
SASENV is the member name of your SAS
configuration file. Normally this is a
member of the SAS CNTL data set. For SAS
Versions 7 and 8, the member name is
usually BATCH and BATW0 for Versions 9 and
above.
SASCFG1 is the language code required with SAS
Versions 9 and higher, for example, EN
stands for English. The value is blank for
SAS Version 8.
For SAS version 9.1.3, normally the
library is the SAS CNTL data set and the
member is BATW0.
For SAS version 9.2 and above, normally the
library is the SAS CONFIG data set and the
member is BATCH.
SASCFG2 provides the library name suffix and
member name of an additional configuration
file needed for SAS versions 9.2 and
above. Normally this is a member of the
SAS CONFIG data set and the name is
COMMON.
SASCFG3 provides the library name suffix and
member name of an additional configuration
file needed for SAS versions 9.2 and
above. Normally this is a member of the
SAS CONFIG data set and the name is ENW0.
SASCFG4 provides the library name suffix and
member name of an additional configuration
file needed for SAS versions 9.2 and
above. Normally this is a member of the
SAS CONFIG data set and the name is SITE.
LANG1 is the language code required with SAS
Versions 9 and higher, for example, EN
stands for English. The value is blank for
SAS Version 8.
LANG2 is the encoding value required with SAS
Version 9 and higher. The value for
EBCDIC is W0 and must have a trailing
period (.). The value is blank for Sas
Version 8.
TUNIT is the unit name of the tape device on
which the CA MICS distribution tape is to
be mounted.
TVOL is the volume serial number of the CA MICS
distribution tape as it appears on the "CA
MICS Encryption Parameters."
TEXPDT is the tape expiration date, if your
site uses a tape management system.
PSPVOL is the name of the DASD volume where the
new PSP libraries will be located. If
they already exist, code this parameter as
null (that is, PSPVOL=,).
PSPDSP is the disposition of all PSP libraries
except sharedprefix.MICS.PSP.CNTL,
PSP.PC.TEXT, and PSP.ISPTLIB. If the
following libraries exist, use the value
'OLD,KEEP'. If the following libraries do
not exist, use the value
'NEW,CATLG,DELETE'. Verify that you have
the sharedprefix.MICS.PSP.CNTL,
PSP.PC.TEXT, and PSP.ISPTLIB libraries
already allocated.
sharedprefix.MICS.PSP.ASM
sharedprefix.MICS.PSP.BIN
sharedprefix.MICS.PSP.CLIST
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.LOAD
sharedprefix.MICS.PSP.MACAUTOS
sharedprefix.MICS.PSP.MACLIB
sharedprefix.MICS.PSP.OBJ
sharedprefix.MICS.PSP.PARMS
sharedprefix.MICS.PSP.PROTOLIB
sharedprefix.MICS.PSP.SASFLS
sharedprefix.MICS.PSP.SOURCE
sharedprefix.MICS.PSP.USOURCE
PSPUNIT is the unit name of the DASD volumes where
the new PSP libraries will be located. If
PSP libraries already exist, code this
parameter as null (that is, PSPUNIT=,).
PSP is the SMS STORCLAS to be used to store
STORC the new PSP libraries. This will be used
as the default STORCLAS for allocation of
new PSP data sets. It can be overridden
for individual data set names by modifying
entries in PSPOVER as described in
Appendix A.1. If you do not need to
specify a parameter for PSPSTORC, code it
as null (that is, 'PSPSTORC=,').
PSP is the SMS DATACLAS to be used to store
DATAC the new PSP libraries. This will be used
as the default DATACLAS for allocation of
new PSP data sets. It can be overridden
for individual data set names by modifying
entries in PSPOVER as described in
Appendix A.1. If you do not need to
specify a parameter for PSPDATAC, code it
as null (that is, 'PSPDATAC=,').
PSP is the SMS MGMTCLAS to be used to store
MGMTC the new PSP libraries. This will be used
as the default MGMTCLAS for allocation of
new PSP data sets. It can be overridden
for individual data set names by modifying
entries in PSPOVER as described in
Appendix A.1. If you do not need to
specify a parameter for PSPMGMTC, code it
as null (that is, 'PSPMGMTC=,').
PSPDSNT can be either blank or LIBRARY. Specify
LIBRARY to allocate new PSP data sets as
partitioned data set extended (PDSE) data
sets. It can be overridden for individual
data set names except for the PSP LOAD
library, by modifying entries in PSPOVER
as described in Appendix A.1.
BLOCK is the block size value used for the new
PSP libraries.
WKUNIT is the unit name for a direct access work
device.
SR is the three-letter code for the new
product being loaded.
If you are loading more than one new
product, each code must be separated by a
blank.
Note: Only specify your NEW products! If
you specify products that are already
installed, they will be overlayed! This
can critically impact your CA MICS
database.
Use the MWF CONFIG command to help you
determine installed CA MICS products.
LOADER is the program name of the IBM Loader at
your site. This is typically IEWLDRGO,
HEWLDRGO, or LOADER. If in doubt, contact
your system programmer.
__ Submit the following job:
'sharedprefix.MICS.TAPELOAD.CNTL(PRODLD1)'
Note: Modules are written to disk by executing the
program named LPEBLDD. It runs as a
"non-authorized" program. Some mainframe security
systems, such as CA Top Secret, have a feature that
restricts non-authorized programs from writing
authorized load modules. (An authorized load module
is link-edited with an attribute of AC(1)). If your
site has this security feature activated and is
licensed for the CA MICS Space Collector (VCC),
then the load job will fail with an S913 ABEND
while trying to write an authorized VCC load
module. To prevent this ABEND, request your
security administrator to permit LPEBLDD to write
authorized load modules.
__ After the job finishes, check the return codes.
All steps must have return codes of zero except the
following:
COMPABND must not execute. If it does execute, the
PSP refresh level requirement has not been met and
it will force the job to abend.
PSPCHK2 might be 0 or 4.
#ASCOPY2 and PSPUPDTE must be 0 if PSPCHK2 is 4.
#ASCOPY2 and PSPUPDTE will not execute if PSPCHK2
is 0. This is normal.
Any other return codes are errors. If there is an
error, you must correct it and resubmit the job.
If the error persists, contact Technical Support at
http://ca.com/support.
__ Proceed to the next step.
__ 10. Receive New Tables
NOTE: This step is ESSENTIAL for product installation!
Use PSP Online to receive new product tables. Select
the Product Support Online Services panel (MWF;5;2).
The Receive New PSP Tables dialog will be displayed.
Respond to the prompts to ensure that the tables are
received and saved.
__ 11. Complete Optional Product Installation
Note: This step is ESSENTIAL for product installation.
Use PSP Online to complete product installation.
The ccc0000 job, which you are about to execute, helps
ensure that required product maintenance is applied.
It also copies product parameters, account routines,
and MICF inquiries to their required libraries. This
must be done for the product to execute correctly.
Use PSP Online to select and print product change
ccc0000 (where "ccc" is the three-character identifier
listed in your new product shipment letter).
Note: When the ccc0000 product change is selected, all
unapplied prerequisite and corequisite product changes
will be selected as well. You must ALSO print the
checklists for these product changes.
If you are reinstalling an optional product and
ccc0000 does not appear on the Select Product Changes
for Apply panel in PSP Online, perform the following
steps to select the product change:
__ Type "X ccc0000" on the command line and press
ENTER.
__ Type "R" on the line next to ccc0000 and press
ENTER.
__ Type "S" on the line next to ccc0000 and press
ENTER.
__ If you experience difficulty with this process,
contact Technical Support.
Note: Review all PC text documents for requisite
product changes and for possible local
modification conflicts before applying any
product changes.
Apply the product change. You must ensure that
the ccc0000 installation job ends with a
condition code of zero.
For assistance, contact Technical Support at
http://ca.com/support.
__ 12. Complete Checklists for Each Optional Product
You must ensure that ALL checklists, including those
used for the optional product's installation and its
prerequisite and corequisite product changes, are
completed in the following order:
__ Each prerequisite product change
__ The ccc0000 product change
__ Each corequisite product change
__ 13. Back Up System
Create a backup copy of all sharedprefix and prefix
libraries.
__ 14. Retain Distribution Tape
Retain your CA MICS distribution files. They may be
used to install other CA MICS optional products.
Copyright © 2014 CA.
All rights reserved.
|
|