Upgraded FMIDs can include new product features that introduce configuration changes
(such as new product configuration parameters in RKANPARU(KppENV), or new RK*
runtime members). Typically, these types of configuration changes caused by new product versions are
delivered as benign, and IBM-supplied configuration defaults are supplied, so you do not need to
customize the configuration profiles to incorporate them. However, you do need to stage the changes
by refreshing the work environment and recreating the runtime members and
jobs.
About this task
This scenario involves the following steps:
- Refreshing the work libraries.
- Regenerating the RTE members and jobs.
- Submitting the jobs that complete the setup of the RTE.
At a minimum, you need to copy the SMP/E target libraries to the read-only runtime libraries
(KCIJPLOD) and the updated work libraries to the user libraries (KCIJPCPR and KCIJPW2R). You might
need to run additional jobs, depending upon product-specific requirements indicated in ++HOLD
data.
Tip: Each site has different change-control procedures. Certain sites deploy these
types of changes by renaming the current production RK* libraries to a backup set like
RK*.Dyymmdd, then renaming the latest WK* set to RK*. Sample deployment and
backup jobs WKANSAMU(KCIJcCPY) and WKANSAMU(KCIJcW2R) provide
helpful samples.
To stage the new configuration parameters, complete the following
procedure.
Procedure
- Refresh the PARMGEN work environment.
This
step update interim libraries and recreates the configuration profiles
with any new parameters.
- On the main Workflow panel, specify the name of the
runtime environment to which you want to apply maintenance.
- From the Workflow - Primary Options Menu, select Set
up PARMGEN work environment for an RTE.
The
following message is displayed:
KCIP@MSG ---------------- PARMGEN MESSAGES --------------------------
Command ===>
While configuring an existing RTE profile, you have asked to
navigate to the KCIJPCFG option to review or make changes to the
KCIJPCFG job, which was run with highest condition code RC= 00000
on 2017/07/27. In most cases, if you change any KCIJPCFG
parameters, you will have to rerun the KCIJPCFG job and certain
subsequent PARMGEN configuration jobs.
Press ENTER to continue with KCIJPCFG changes.
Press F3 to abort.
- Press Enter to continue.
The first
setup panel (KCIP@PG1) is displayed.
- Press Enter to continue through the following screens.
On the Include Products in this PARMGEN RTE panel, change
the Confirm ==> N field to Confirm
==> Y to continue.
The following
panel is displayed:
KCIP@BAK IMPORTANT - REFRESH THE LPAR RTE USER AND IBM PROFILES --------
Command ===>
If you changed any JVM RTE configuration values on the
"SET UP/REFRESH PARMGEN WORK ENVIRONMENT" KCIJPCFG navigation
panels, or changed the configured product mix or upgraded product
versions, then you must regenerate/resubmit the KCIJPCFG/KCIJPPRF jobs.
You must also refresh the PARMGEN profiles.
Specify a backup member name for the LPAR RTE to automate the
resubmission and refresh process. A default backup member is provided.
Blank-out the field if you do not want to refresh the profiles.
DEMO Backup member name ===> ________ (Required for KCIJPPRF)
PARMGEN automatically backs up the RTE profile in
TDITN.IDTST.PARMGEN.WCONBACK, refreshes templates in IK* datasets,
rebuilds the profiles with the new values, merges in the profiles values
from the backed-up LPAR RTE user profile, and generates a delta report.
Press F1 for information about the automated process.
- Enter a name for the profile backup member.
The modified KCIJPCFG job is displayed.
- Submit the job.
The KCIJPCFG job creates
new RTE profiles that contains the new parameters, then runs the KCIJPPRF
job. The KCIJPPRF job updates the interim libraries and merges the
current values from the backed up profile into the new profiles. Return
to the main Workflow panel. Wait until both KCIJPCFG and KCIJPPRF
have completed before proceeding to the next step. No return code
is displayed on the Workflow main panel until both jobs have completed.
- Regenerate the RTE members and jobs.
- Select Create the RTE members and jobs.
The $PARSE /$PARSESV: Create the RTE Members
and Jobs panel is displayed.
- Select option 1 to submit the composite job.
If the updates affect only one set of libraries, you
can submit the library-specific job instead of the composite job.
Press F5 to create runtime members and jobs in an individual library
(WKANCMDU, WKANPARU, or WKANSAMU).
The $PARSE
job takes the product templates from the %RTE_PLIB_HILEV%.%RTE_NAME%.
IK* staging libraries, applies the customized values from the configuration
profiles, and creates the runtime members in the work libraries (WK*).
- Return to the main Workflow panel.
- Submit the jobs to complete the setup of the RTE.
- Select Submit batch jobs to complete PARMGEN setup.
The Submit Batch Jobs to Complete PARMGEN Setup menu is displayed.
KCIP@SUB -------- SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP -----------------
Option ===>
Select option 1 to SUBMIT the composite jobs in WKANSAMU for SYSA RTE.
Tip: Review the SUBMIT commands in the KCIJPSUB composite job.
Alternatively, select other options (2-12) to submit each job individually.
Enter ns (1s-12s) for detailed job/task status.
Description REQ Job Name Status Date
--------------------------------------- ----- -------- --------- ----------
More: +
1. Composite SUBMIT job (See JCL comments) KCIJPSUB
** or **
2. Allocate runtime RO and RW datasets (Yes) KCIJPALO
3. Copy SMP/E mbrs from TK*->RK* RO libs (Yes) KCIJPLOD
4. Run product security steps (Yes) KCIJPSEC
5. Update variable-named runtime mbrs (No ) KCIJPUPV
6. (Re)Create USS runtime mbrs in RKANDATV (Yes) KCIJPUSP
7. Create USS dirs./ (Re)Copy USS files (Yes) KCIJPUSS
8. Copy runtime mbrs to SYS1-type libs (Caution) KCIJPSYS
9. Run post-SMP/E RKANMODU ASM/LINK steps (Yes) KCIJPLNK
10. Verify the configuration jobs (Tip) KCIJPIVP
11. Back-up RK* product execution user libs (Tip) KCIJPCPR
12. Copy runtime mbrs from WK*->RK* RW libs (Yes) Enter 12 for details.
Press F1=Help for more information. Type UTIL to access utility menu.
- Submit the following jobs and any other jobs indicated
by a Yes in the REQ column.
- KCIJPLOD
- This required job copies members of the target libraries that
were installed by SMP/E to the read-only RK* libraries.
- KCIJPW2R/KCIJPW1R
- These jobs (Option 12) copies the WK* work output
libraries to the respective production RK* runtime libraries. If you run either of these jobs, run
KCIJPCPR to back up the RK* production libraries. KCIJPW2R is run by default when the composite
submit job KCIJPSUB is run. KCIJPW2R replaces all RK* members with members from WK*. It will leave
non-PARMGEN managed members in RK* libraries. KCIJPW1R deletes all RK* members except for the ones
that are added in the IBM provided WKANSAMU(KCI$IW2R) and user defined WCONFIG(KCI$XW2R) exclude
lists, and then copies WK* members to RK* libraries. You must add members they want saved to their
RTE WCONFIG(KCI$XW2R) member.
You might have to submit one or more of the following
jobs:
- KCIJPSEC (if upgrade introduces changes in security) to create
security-related members (load modules, encryption key, and other
elements) based on the product security requirements
- KCIJPALO (if the upgrade introduces new data sets are introduced)
- KCIJPUSP and KCIJcUSS (if upgrade introduces changes in z/OS®
UNIX System Services requirements)
- KCIJPLNK (if OMEGAMON® for IMS on z/OS is installed)
- KCIJPSYS (if upgrade introduces new started tasks or nodes)
Results
The new product features are implemented and the defaults
are in effect.