2. PSP LIBRARY REFRESH AND CHECKLISTS › 2.2 PSP Refresh Process and Checklists › 2.2.3 PSP Refresh Checklist (Batch Driven - PAX)
2.2.3 PSP Refresh Checklist (Batch Driven - PAX)
*************************************************************
* Note: Complete these instructions only after your *
* CA MICS system meets the standard PSP refresh *
* requirements identified earlier in this chapter. *
*************************************************************
___ 1. Review the cover letter.
Review the cover letter and associated product
maintenance letters (PML) for the latest important
technical information.
___ 2. Plan for CA MICS products for which you are licensed,
but are not applying maintenance. Here are examples:
o If your site is licensed for a CA MICS product that
is not yet installed.
o If you have a component that has not had
maintenance applied to it in over two years.
Note: The PSP refresh job will abend if the result
of running the job would be that unapplied
maintenance is lost.
If either of the above conditions is true, plan to do
the following:
o Exclude the product from PSP processing using the
PSPOVER feature that is documented in Appendix A.2.
o Refresh your PSP libraries.
o After the PSP libraries are refreshed, you can
install the excluded product. See the PIOM,
Section 3.8.6. You will need the same PSP
distribution files as you used in the PSP refresh
job. You will also need the product's three-letter
code.
___ 3. Check the Product Change Status table.
Do this by displaying PSP Online's Select Product
Changes for Apply menu (MWF;5;2;2). Ensure there are
no product changes displayed with the letter "A"
beneath the "Line CMD" column. The "A" indicates
that the product change is in APPLYING status. This
means it was selected for application, but failed to
successfully complete. Determine the cause, correct
the failure, and apply the product change before
proceeding.
If JCL for a product change has to be submitted, exit
MWF and repeat this step until there are no more
product changes in APPLYING status.
___ 4. Using your site's utilities, compress all complex
level libraries.
___ 5. Using your site's utilities, back up all existing
complex level and PSP libraries. By default, these
begin with the qualifiers:
sharedprefix.MICS (complex level libraries)
sharedprefix.MICS.PSP (PSP libraries)
___ 6. Ensure that the data sets listed below do not exist.
If they do exist, you must delete them.
sharedprefix.MICS.TAPELOAD.CNTL and
sharedprefix.MICS.TAPELOAD.LOAD
___ 7. Copy the installation libraries from the PSP
distribution medium.
*****************************************************
* C A U T I O N *
* *
* The library needed for PSP library refresh is *
* loaded with IEBCOPY. You MUST use the JCL as *
* it is written in the following step. *
* *
* This PSP library refresh process creates two *
* utility data sets. *
* *
* You must name these data sets as specified in *
* the JCL: *
* *
* sharedprefix.MICS.TAPELOAD.CNTL *
* sharedprefix.MICS.TAPELOAD.LOAD *
* *
*****************************************************
Create the JCL listed below. Complete the JOB card
and parameters and submit the job.
//jobname JOB ..........
//LOAD EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//#CNTL DD DISP=SHR,
// DSN=yourHLQ.CAI.MICSESD.TAPELOAD.CNTL
//#LOAD DD DISP=SHR,
// DSN=yourHLQ.CAI.MICSESD.TAPELOAD.LOAD
//CNTL DD DSN=sharedprefix.MICS.TAPELOAD.CNTL,
// DISP=(,CATLG,DELETE),UNIT=______,
// VOL=SER=______,SPACE=(6160,(400,30,20))
//LOAD DD DSN=sharedprefix.MICS.TAPELOAD.LOAD,
// DISP=(,CATLG,DELETE),UNIT=______,
// VOL=SER=______,SPACE=(6160,(14,7,1))
//SYSIN DD *
COPY INDD=#CNTL,OUTDD=CNTL
COPY INDD=#LOAD,OUTDD=LOAD
/*
yourHLQ on the #CNTL and #LOAD statements specifies
the high level qualifier of the ESD PAX data sets
and should be replaced with the "yourHLQ" used in
the ESD PAX UNZIPJCL job.
sharedprefix on the CNTL and LOAD statements
completes the name of the installation data sets
and should be replaced with your CA MICS high-level
qualifier.
UNIT and VOL=SER on the CNTL and LOAD statements
specify the unit name of the direct access device
and the volume serial number of the volume on which
the installation libraries are to be allocated.
Ensure that the job completes with a condition code
of zero.
___ 8. Optionally, review the product change texts for all
product changes that are new with this PSP. Do this
by browsing the PCTEXT member in
sharedprefix.MICS.TAPELOAD.CNTL.
To print PCTEXT, edit the PRPCTEXT member in
sharedprefix.MICS.TAPELOAD.CNTL. Provide a JOB
statement, complete the sharedprefix parameter on the
SYSUT1 DD statement, and submit the job. It is
printed with ASA carriage control characters.
___ 9. Optionally, edit sharedprefix.MICS.TAPELOAD.CNTL,
member PSPOVER, and override the PSP data set
allocation parameters.
Use this option if any one of the following
conditions is true:
o Your PSP data sets are to be allocated on more
than one VOLSER.
o You have specific data set attributes that you
want to modify.
o Your PSP library names do not conform to the
default names. See Appendix A.1 for an explanation
and instructions.
If PSPOVER does not exist, copy it from
sharedprefix.MICS.SOURCE into
sharedprefix.MICS.TAPELOAD.CNTL.
___ 10a. Required for JES2 sites only:
Edit sharedprefix.MICS.TAPELOAD.CNTL(ESDyymmL),
where yymm is the PSP distribution being processed.
This is the CNTL data set that was loaded from the
PSP distribution medium in step 7 of these
instructions.
If upgrades were added to this medium they will be
automatically loaded, provided your site is licensed
for them.
___ 10b. Required for JES3 sites only:
You will have to submit the following jobs in
sequential order:
sharedprefix.MICS.TAPELOAD.CNTL(ESDJES3A)
sharedprefix.MICS.TAPELOAD.CNTL(ESDJES3B)
ESDJES3A checks for prerequisites, analyzes space of
existing data sets, reports on them, then allocates
them if the mode is specified as DASD.
ESDJES3B loads the PSP libraries and records the
event.
If upgrades were added to this medium they will be
automatically loaded, provided your site is licensed
for them.
___ 11a. Provide a JOB statement. Although the required CPU
time for the job is unpredictable because of
varying processor types and product configurations,
5 CPU minutes should be adequate. A region of 4096K
should be adequate.
___ 11b. The number of lines that will be output is
unpredictable, but a safe estimate is 30 KB. Sample
JES2 and JES3 parameter statements have been
provided. Use the one appropriate for your site and
delete the other.
___ 11c. The first step of the job executes a CA
MICS-generated PROC called MICSDM. Check to see if
your site has the MICSDM PROC in
sharedprefix.MICS.PROCLIB.
Two possible reasons that the PROC name may not be
MICSDM are:
o A test version was created. See section 5.1.1 in
the PIOM.
o Your site's PROC naming conventions have forced
MICSDM to be renamed.
___ 11d. If required at your site, provide the name of the
procedure library that contains the MICSDM PROC.
See step 11c.
___ 11e. If you do not execute the MICSDM PROC, find the
character string:
//MICSDM EXEC MICSDM
Change MICSDM to identify the PROC as described in
step 11c.
___ 11f. Find the following character string:
sharedprefix.MICS.TAPELOAD.CNTL(PSPBATC1)
Change sharedprefix.MICS to identify the data set
that you are editing. Do not change the member
name.
Find the following character string:
sharedprefix.MICS.TAPELOAD.CNTL(PSPMAT)
Change sharedprefix.MICS to identify the data set
that you are editing. Do not change the member
name.
___ 11g. If you want this job to use any non-default PSP
data set names (you may have specified these to PSP
Online using option 1 - Define the PSP Libraries),
change the default name of each of those libraries
to the non-default name.
___ 11h. Determine the MODE you want to use for the load
job's initial execution.
When MODE is specified as RPT, the load job analyzes
existing PSP data sets, produces a report, and
terminates with an ABEND code of U0100. The report
that is produced will tell you how much DASD space
is required for each PSP data set. It will also
tell you whether the existing PSP data sets are too
small or whether they contain enough space and
directory blocks to accommodate the distribution
files when they are loaded to DASD.
When MODE is specified as DASD, the load job
analyzes existing PSP data sets, reports on them (as
with RPT), dynamically deletes PSP data sets that
are too small, dynamically allocates new data sets,
and allows the job to continue loading the PSP data
sets.
If your site restricts the allocation of new data
sets to specific DASD administrators, you should
execute the load job with MODE=RPT. Provide the
report to your DASD administrator and ask that the
DASD administrator allocate all PSP data sets that
cannot be reused.
Note regarding sharedprefix.MICS.PSP.PC.TEXT: When
this data set must be manually re-allocated, make
sure that the contents of the old data set are
copied to the new data set.
After the new data sets are allocated, execute the
load job again with MODE=RPT to verify that the
allocations were correct. After you have allocated
the new data sets to the correct size, execute the
load job with MODE=DASD to load the PSP data sets.
You will specify the MODE in the next step.
___ 11i. Complete the following parameters on the LOADPSP
EXEC statement and not on the PROC statement:
//***********************************************************
//LOADPSP EXEC PSPPROC, *
//* ------------------ *
// RSIZE='4M', <--- REGION FOR ALL STEPS *
// YOURHLQ='_____________' <--- YOURHLQ FROM UNZIPJCL JOB *
// SPREFIX='_____________' <--- SHAREDPREFIX *
// SMICS='MICS.', ,<--- SHARED MICSLEVEL *
// SASPFX='___________', <--- SAS SYSTEM LIBRARY PREFIX *
// SASNAME='ENTRY', <--- SAS PROGRAM NAME *
//* SAS FOR SAS V9 *
//* SASXAL FOR SAS V8 *
//* SASENV='TKMVSENV(TKMVSENV)', <-- ENVIRONMENT FILE *
//* SAS >= 9.1.3 *
//* UNCOMMENT IF YOU HAVE THIS *
//* SAS LIBRARY. IF YOU DO *
//* NOT HAVE THIS LIBRARY YOU *
//* MUST COMMENT THE TKMVSENV *
//* DD STATEMENTS AS THIS DD *
//* MUST REFER TO THE ACTUAL *
//* LIBRARY OR THIS JOB WILL *
//* ABEND *
// LANG1='', <--- SAS V9 LANGUAGE *
//* EN = ENGLISH *
//* BLANK IF V8 *
// LANG2='', <--- SAS V9 ENCODING VALUE *
//* W0. = EBCDIC (1047) *
//* MUST HAVE TRAILING . *
//* BLANK IF V8 *
// PSPUNIT='_____', <--- UNIT FOR NEW PSP D/SETS *
// PSPVOL=, <--- VOLUME FOR NEW PSP D/SETS *
// PSPSTORC=, <--- STORCLAS FOR NEW PSP D/SETS*
// PSPDATAC=, <--- DATACLAS FOR NEW PSP D/SETS*
// PSPMGMTC=, <--- MGMTCLAS FOR NEW PSP D/SETS*
// PSPDSNT=, <--- ENTER LIBRARY FOR PDSE *
// WKUNIT=SYSDA, <--- WORK DASD UNIT *
// WARN=YES, <--- YES OR NO *
// MODE=____, <--- RPT OR DASD *
// RLS=RLSE, <--- RLSE OR LEAVE BLANK *
// LOADER=IEWLDRGO <--- YOUR SITE'S LOADER NAME *
//***********************************************************
RSIZE is the region for each step. The default of
4M should be adequate.
YOURHLQ on the #CNTL and #LOAD statements specifies
the high level qualifier of the ESD PAX data
sets and should 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 specifies whether MICS is used in the name
of the CA MICS libraries. If you used MICS
in the data set names, you must terminate
it with a period. If you omitted MICS from
the data set names, you must change SMICS
to null (that is, '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
SASHELP - SAS help library
SASMSG - SAS message library
Review the data set names specified in the
DDs. If they are not correct, edit in the
correct 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 specifies the name of the SAS environment
file. The TKMVSENV file is used to make
a list of pseudo environment variables.
Option values in SAS configuration files
can contain symbolic references. The
values of these symbolic references are
resolved from a variable that is set in
the TKMVSENV file.
If your installation uses symbolic
references in your SAS configuration
files, uncomment this parameter and verify
that the low level qualifier and member
name are correct.
If your installation does not use symbolic
references, manually delete 6 occurrences
of the TKMVSENV DD in the PSP load job.
LANG1 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 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 a 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=,').
We recommend that a class be used that does
not have the PARTIAL_RELEASE=YES_IMMED
attribute.
PSPDSNT can be either blank or LIBRARY. Specify
LIBRARY to allocate new or reallocated 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.
WKUNIT specifies the unit name for a direct access
work device.
WARN specifies whether or not to abend with a
U0998 based on the status of your product
changes.
If WARN=YES and your complex has an
unapplied product change that is no longer
available on this PSP distribution, the job
will abend before the PSP libraries are
refreshed. Existing PSP data sets will not
be touched.
If WARN=NO, the job will execute even if
there are unavailable product changes that
have not been applied to the CA MICS system.
Note: If you specify WARN=NO, all unapplied
and unavailable maintenance will be
permanently deleted from your PSP libraries.
MODE can be either RPT or DASD. See step 11h for
an explanation of this parameter.
RLS specifies whether or not unused space will
be released from the PSP data sets. The
default, RLSE, will cause the job to release
unused space. If you want to retain the
unused space, change RLS to null (that is,
'RLS=,').
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.
___ 11j. If your site requires that your sort program load
library be explicitly identified, continue with
this step. Otherwise, skip to step 11k.
Find the first occurrence of //SORTLIB. The last DD
is reserved for the sort library name. Fill in the
names as appropriate. If you do not fill in a name,
the default will permit normal operation of the
load job.
___ 11k. Recall all migrated PSP libraries. Ensure that no
PSP libraries are allocated to any user. The load
job will dynamically allocate all PSP libraries as
OLD. If any PSP libraries are allocated to another
user, the job will fail with a dynamic allocation
error.
___ 11l. Refresh the PSP libraries by reading and completing
the following.
Note: Modules are written to disk by executing the
program named LPEBLDD, which 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 Option
(VCC), the load job will fail with an S913 ABEND
while trying to write an authorized VCC load module.
To prevent this ABEND, ask your security
administrator to permit LPEBLDD to write authorized
load modules.
Submit the load job.
Since this job allocates
sharedprefix.MICS.TAPELOAD.CNTL with a DISP=OLD, it
is important that you end all editing now and ensure
this data set is not allocated to your interactive
session.
___ 11m. After the job finishes, check the condition codes.
Steps DMABEND and MICSVRAB are normally bypassed
(flushed).
The step #PCHFND may complete with a condition code
of 2 as part of normal operation.
If the job was submitted with MODE=RPT, then the
PSPEXEC step must abort with an ABEND code of U0100.
If the job was submitted with MODE=DASD, PSPEXEC and
all subsequent steps must complete with a condition
code of zero.
If the job abends or if a step completes with an
unexpected condition code (greater than 2), take
corrective action and resubmit the job. See
Appendix C for a list of commonly experienced errors
and their corrective actions.
___ 11n. Review the Product Change Status Report in the
PSPRPT SYSOUT data set from the PSPEXEC step. The
report identifies the PSP levels that will be
loaded to the PSP data sets. See Appendix B for
details.
__ 11o. If you submitted the job with MODE=DASD, proceed
to step 12.
If you submitted the job with MODE=RPT, review the
"Information for PSP Data Sets Before Allocation"
report in the PSPLOG SYSOUT data set. It identifies
all the PSP data sets, their attributes, and whether
they will be deleted, allocated, or reused. See step
11h for more information on the MODE parameter.
You can refine your data set allocation parameters
by modifying them for individual data sets as
explained in Appendix A.1, or for all PSP data sets
by using JCL parameters as explained in step 11i.
Once the desired changes have been made, return to
step 11k and resubmit the load job.
When you are satisfied with the contents of the
report, change MODE=RPT to MODE=DASD and resubmit
the job.
___ 12. Optionally, print or view the CA MICS System
Administrator Guide (SAG).
To print it, edit sharedprefix.MICS.CNTL(DOCUMENT)
and specify BS after MANUAL=. Then submit the job.
To view it through CA MICS Document Access, first run
the job in sharedprefix.MICS.CNTL(DOCAGEN). Then you
can browse the SAG using MWF 1;1.
___ 13. Retain sharedprefix.MICS.TAPELOAD.CNTL. It will be
reused in all future CA MICS tape loads for both PSP
and Optional Products.
___ 14. Receive the new distribution tables. See Appendix D.2
in this guide for the steps.
___ 15. Use PSP Online for change review, problem analysis,
and product change application. See Chapter 3 and
Appendix E in this guide.
*************************************************************
* This completes refreshing your PSP libraries. *
*************************************************************
