Upgrading smart manager for mainframe, Related topics – HP XP Command View Advanced Edition Software User Manual
Page 279
3.
If the user SVC has been registered by using the
IEASVCxx
parmlib member, remove the linkage
of the
HPQYLPAT
load library for LPALIB. (This step is unnecessary if the user SVC was registered
by using the
YKALCSVC
command.)
• If the load library for LPALIB has been statically linked by defining it in the
LPALSTxx
parmlib
member, delete the definition.
• If the load library for LPALIB has been dynamically linked to LPALST by using the
SETPROG
LPA
command, use the
SETPROG LPA
command to remove the linkage.
To apply the removal of static linkages, you must perform re-IPL specifying the
CLPA
parameter.
Perform re-IPL at the end of the preparation for upgrading.
Upgrading Smart Manager for Mainframe
The procedure for upgrading Smart Manager for Mainframe is the same as for a new installation
except the following.
When upgrading Smart Manager for Mainframe:
•
You do not need to register a user SVC if the currently enabled user SVC version satisfies the
conditions for the user SVC that are prerequisites for Smart Manager for Mainframe.
•
If the license of the version before migration can be used and there are no licenses to be added,
you do not need to register a license for Smart Manager for Mainframe.
NOTE:
•
If a task requiring re-IPL was performed during preparation for upgrading, always perform re-IPL
before starting the procedure for upgrading.
•
If sample JCL
HPQKT2DF
, which defines the distribution library and target library, terminated
abnormally during installation using SMP/E and
GIM35601E ** DATASET SUBENTRY WAS
NOT ADDED BECAUSE IT ALREADY EXISTS.
was output, change the
ADD
command in
HPQKT2DF
to the
REP
command, and then execute
HPQKT2DF
again.
Related topics
User Guide
279