2. PSP LIBRARY REFRESH AND CHECKLISTS › 2.2 PSP Refresh Process and Checklists › 2.2.1 PSP Refresh Checklist (Panel Driven - Tape/PAX)
2.2.1 PSP Refresh Checklist (Panel Driven - Tape/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. For example:
- if your site is licensed for a CA MICS product that
is not yet installed
or
- 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 of this document.
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). Verify that
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. Verify that sharedprefix.MICS.TAPELOAD.CNTL exists.
If it does not, create
sharedprefix.MICS.TAPELOAD.CNTL using the following
parameters:
SPACE UNITS ===> BLOCK
PRIMARY QUANTITY ===> 250
SECONDARY QUANTITY ===> 50
DIRECTORY BLOCKS ===> 25
RECORD FORMAT ===> FB
RECORD LENGTH ===> 80
BLOCK SIZE ===> 6160
___ 7. 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 are 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.
If PSPOVER does not exist, copy it from
sharedprefix.MICS.SOURCE into
sharedprefix.MICS.TAPELOAD.CNTL.
___ 8. Recall all migrated PSP libraries. Verify 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.
___ 9. Set up and execute the PSP load JCL to refresh the
PSP libraries.
This step uses a panel-driven process to generate the
JCL to load your PSP DASD data sets. It combines
parameters you provide on MWF panels with parameters
that were specified during the complex-level JCLGEN
and generates the JCL to load the PSP data sets.
__ 10a. Determine the mode you want to use for the load
job's initial execution.
If your site restricts the allocation of new data
sets to specific DASD administrators, you should
execute the load job with MODE specified as RPT.
See the description of the MODE parameter below.
___ 10b. Go to PSP Online and select the Submit the PSP
TAPELOAD Job With Dynamic Allocation panel
(MWF;5;2;3;2).
___ 10c. Complete the following options and parameters on the
panel:
From When the incoming PSP distribution files are
Tape 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 name of the tape device on which the
UNIT CA MICS distribution tape is to be mounted.
From When the incoming PSP distribution files are
ESD- from ESD PAX, specify YES. Otherwise,
DASD 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 common
Level to all the incoming PSP distribution files
Qualif- on DASD. It corresponds to "yourHLQ" used
ier in the ESD PAX UNZIPJCL job.
PSP is the volume serial number of the direct
VOLSER 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. If the "SMS JCL Tailoring" option
(below) is "YES", this parameter is
ignored.
Release specifies whether or not unused space will
space be released from the PSP data sets. RLSE
will cause the job to release unused space.
If you want to retain the unused space,
blank this out.
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.
We recommend that a class be used that does
not have the PARTIAL_RELEASE=YES_IMMED
attribute.
DSNTYPE 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.
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.
Region is the region for each step. The default
size of 4096 KB should be adequate.
Warn specifies whether or not to abend with
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 will be 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 is either RPT or DASD.
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. Then 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.
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
___ 10d. When your parameters are complete, press END to
continue or type CANCEL and press enter to stop
the process.
___ 10e. (Required for JES2 sites only)
If you pressed END when the Edit generated JCL field
was specified as YES, then you will see a temporary
data set containing the generated load job.
Review the JCL and ensure it conforms to your site's
standards. Then press END to submit the job.
If you pressed END when the Edit generated JCL field
was specified as NO, you will not be able to edit the
generated load JCL and the job will be submitted
automatically.
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 (VCC),
then 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.
Skip step 10f and go to step 10g.
___ 10f. (Required for JES3 sites only)
If you pressed END to continue, then you will see a
temporary data set containing the generated load
jobs.
Delete the &PSPJOB2, &PSPJOB3, and &PSPJOB4
statements.
Review the JCL and verify that it conforms to your
site's standards. Press END to submit the jobs.
After the first job runs, release the second job.
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 (VCC),
then 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.
___ 10g. After the job finishes, check the condition codes.
The step DMABEND must complete with a condition code
of zero.
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.
___ 10h. Review the PSP LOG in the PSPLOG SYSOUT data set from
the PSPEXEC step. Note the ISPF version on the line
"YOUR ISPF ENVIRONMENT IS:". This will be referenced
in Step 11.
___ 10i. 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.
___ 10j. If you submitted the job with MODE specified as DASD,
proceed to Step 11.
If you submitted the job with MODE specified as 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 10a for more information on the
MODE parameter.
If you want to refine your data set allocation, you
have two choices: override individual parms by
repeating this procedure beginning at Step 7; or
override the default PSP allocation parms by
repeating this procedure beginning at Step 10b.
When you are satisfied with the contents of the
report, return to Step 10a, change MODE to specify
DASD, and resubmit the load job.
___ 11. Optionally, review the product change texts for all
product changes and upgrades 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.
___ 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. *
*************************************************************
