Tom,
The job to remove the temporary catalog alias (aka SSA) and rename the data
sets to prepare for an IPL is done during the z/OSMF Deployment (not in the
Post Deploy Workflow), and is found in the Software Management provided job,
IZUD05RN - that's the name that my generated job was, and it was job #5 out of
6 jobs that were provided for my configuration.
It looks like this in Software Management. Sorry for the horrible formatting,
but you can see it with the "5" below:
-----
4 IZUD04UZ Unzip Data Sets: Extract the target software instance
data sets from the portable software instance archive files, into the location
defined by the deployment configuration, using temporary and unique data set
names. AQFT
Complete
MWALLEZO JOB20193 CC 0256 U
5 IZUD05RN Rename Data Sets: Rename the target software instance
data sets from their temporary and unique names to their true names defined by
the deployment configuration, and update catalog entries for the data sets as
needed. AQFT
Complete
MWALLEZO JOB26729 CC 0008 U
6 IZUD06UC Update CSI Data Sets: Update the entries within the
SMP/E CSI data sets to reflect the target software instance zone names, data
set names and locations, and UNIX directory prefixes. AQFT
Complete
MWALLEZO JOB28159 CC 0000 U
----
In that 5th job, I can see that the rename is happening like this. Note
"ZS25VBNM" is my temporary catalog alias (SSA):
----
LISTCAT -
ENTRY(ZS25VBMW.SYS1.LINKLIB) -
CATALOG(MWALLE.VB25.MCAT)
IF LASTCC = 0 THEN DO
ALTER -
ZS25VBMW.SYS1.LINKLIB -
NEWNAME(SYS1.LINKLIB) -
CATALOG(MWALLE.VB25.MCAT)
END
----
What might be happening, is that during the configuration of your deployment,
you entered in the names of the final data sets WITH a temporary high level
qualifier yourself. If that is so, then you have indicated that that
"temporary" HLQ is the final name you wanted. This is something that we've
seen experienced CustomPac people do, as they assume they need to handle the
temporary HLQ themselves which is not the case in z/OSMF. You can see that
z/OSMF will be adding(and removing) the temporary HLQ itself, if you look at
the Configuration sample for the data set, so that you will know you don't have
to handle the temporary HLQ yourself.
Here's the spot in Configure Deployment of Software Management, in Modify where
you can see that (see NEWMCAT below as the sample temporary HLQ), and that your
name should not attempt to add a temporary HLQ:
----
Enter the data set name or qualifiers to use for the selected data sets.
Common data set qualifiers: Example data set name:
From: SYS1.LINKLIB SYS1.LINKLIB
To:
SYS1.LINKLIB
SYS1.LINKLIB
NEWMCAT.SYS1.LINKLIB ( Target data set name with temporary catalog alias )
z/OSMF automatically adds the temporary catalog alias to reference the target
data set from the driving system catalog. "NEWMCAT" is the default temporary
catalog alias and can be updated in the Catalogs step of the Deployment
Configuration.
-----
If indeed, you did add your "own temporary" final name to the data sets, you
will need to go back and remove it. You can either go back into the same
deployment and do that to backtrack, or if that Deployment is Complete you can
start a new Deployment.
For a Completed Deployment, you can copy that configuration to do another
Deployment which is nice as the pre-defined configuration is reused. It is
under Actions -> Copy. It will be grayed out if if the Deployment is not
Complete. I duplicate my Deployments often to save time, and only change
small things, like the target system, or volumes.
-Marna WALLE
z/OS System Install and Upgrade
IBM Poughkeepsie
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
