HP XP P9500 Storage - Manual (Page 208)

To apply the deletion of the user SVC, perform re-IPL by specifying the CLPA parameter. Perform re-IPL
at the end of the preparation for version updating.
CAUTION:
A user SVC is shared by Smart Manager for Mainframe and Business Continuity Manager. Therefore,
in a system where Business Continuity Manager is installed, make sure that Business Continuity
Manager is not running before deleting the user SVC.
Related topics
• Prerequisite user SVC versions for Smart Manager for Mainframe , page 56
• KTINSCHK , page 117
Removing the library linkage
Remove all the links to libraries that were established during setup.
1. Remove the linkage of the HPQYPRCT cataloged procedure library.
• If the cataloged procedure library has been statically linked to the
IEFPDSI
DD name in the
MSTJCLxx parmlib member, remove the linkage.
• If the KTALCSVC , KTSETENV , and KTDSPENV members have been copied from the cataloged
procedure library to the user's PROCLIB, delete those members.
2. Remove the linkage of the HPQYLNKT load library for LINKLIB.
• If the load library for LINKLIB has been statically linked by adding it to the PROGxx parmlib
member, delete the load library from the member.
• If the load library for LINKLIB has been dynamically linked to LNKLST by using the SETPROG
LNKLST command, use the SETPROG LNKLST command to remove the linkage.
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 version updating.
Updating the version of Smart Manager for Mainframe
The procedure for updating the version of Smart Manager for Mainframe is the same as for a new
installation except the following.
When updating the version of 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.
Version Updating 208