Full System Replacement or Software Upgrade, which should I choose?

The major differences are:

Full System Replacement:

  • Replaces existing master catalog
  • Creates new operational data sets
  • Does not support indirect cataloging
  • Merges existing aliases and user catalogs at the end of the install process

Software Upgrade:

  • Uses existing master catalog
  • Reuses operational data sets
  • Supports indirect and extended indirect cataloging
  • Existing aliases and user catalogs are available throughout the install process

For additional information refer to the ServerPac: Using the Installation Dialog SA23-2278 document.


Are there any hints that I should know about to make my SystemPac install simpler?

Yes!

  • If you save your previous configuration, you can merge it forward into your next SystemPac so you don't have to re-enter in all the information.
  • You can merge data sets together in Modify System Layout, if you do that at your installation. Just use the M line command.
  • You can easily convert your PDS to PDSEs, using the CHANGE DSNTYPE command.
  • Use the Recommended System Layout if you need a basic system configuration.
  • If you want to use your existing master catalog, and don't want ServerPac to provide you with operational data sets, use Software Upgrade instead of Full System Replacement.

After the installation, the owner of all files in the file system is not what I expected. What happened?

After restoring the file system, the User ID (UID) of the files will be the UID that IBM used to build your order, which will be correct. UNIX System Services will display a FILE OWNER based on the name your security product provides. The security for the file(s) uses the UID value, and not the FILE OWNER name that may be displayed.

 

When mounting an HFS or zFS data set I receive a mount failure with ERRNO=6F and ERRNOJR=5B220107 or RC=6F and Reason Code=5B220107. What is wrong?

Provide update access to the data set for the userid associated with the OMVS started task.


I am running out of space on the RESTORE job. What can I do?

If you are using the SMPWKDIR DD statement, verify there is the correct amount of space in the file system as specified in the CustomPac Variable SMPWKDIR NAME (FA00PQ05). ServerPac now provide an option to allocate the SMPWKDIR file system through the dialog. If you are not using the SMPWKDIR DD statement, it allows you to specify additional workspace outside of your package directory.


I noticed that when the RESTORE job ran that all of the tapes supplied in my order were not used. The job ended with a return code zero. Any idea what went wrong?

Your order may contain blank tapes. So, as long as the job completes with condition code 0 you can proceed.

 

Do I need to run RACFDRV and RACFTGT jobs?

IBM provides the RACFDRV and RACFTGT jobs to help you complete the security setup for your environment.

The RACFDRV job establishes the RACF® profiles needed on the driving system, to run the other driving system installation jobs.

The RACFTGT job creates RACF profiles required to use the new target system, such as profiles for each high level qualifiers in the order, SSA qualifiers and started procedures.

If you have an existing RACF setup or use an OEM security product, IBM recommends that you do not run the jobs. Instead, you should supply the jobs to your Security administrator to verify that all the required security in the jobs is implemented in your existing environment.


My CALLLINK job is failing with message:
GIM54701E ** ALLOCATION FAILED FOR SMP00010
IKJ56232I DATASET xxx.xxxx NOT ON VOLUME AS INDICATED IN THE CATALOG OR VOL PARAMETER.
We do not have xxx (IMS/CICS/DB2) in our environment. How do I resolve this?

For CALLLINK processing the CALLLIB allocation must succeed. In the variables panel section CALLLIB DSN, you need to blank out the DSN if you do not have the product(s).

Since the UPDDDD job has run you can either:

  • Modify the variables, reselect the UPDDDD job and rerun step UPDDDD.
  • Allocate an empty data set and point the affected DD(s) to it.

I received one of the following errors:
1. FAILING JOB OR PANEL NAME Receive ERROR MESSAGE CPP061600 MESSAGE TEXT CPP0616005S LIBRARY (CPPCENUO) Version Reference to Member CPPE626M, Which DOES NOT EXIST
2. IEC149I 813-04, IFG0195H, myjobname, STEP01, INPUT7, tape_unit,tape_volser, SYS1.orderid.LOADLIB
What happened?

Prior to executing the RECEIVE job, you need to update your existing dialogs. Refer to the section titled "Required Migration Step" in the ServerPac: Using the Installation Dialog SA23-2278 document. This step only needs to be performed once. All future releases will update the dialogs automatically if required.

 

How do I raise the 85% full volume threshold when using the Recommended System Layout?

You cannot change the 85% threshold value for Recommended System Layout. To resolve the over-allocated condition refer to the section titled: "Resolving over-allocated volume conditions" in the ServerPac: Using the Installation Dialog SA23-2278 document.


I encounter error CPP9999996S, where the contents of the ISPEXEC buffer was:
/*0038*/LIBDEF ISPSLIB DATASET
ID('SYS06333.T114558.RA000.ABCSMAC3.R0209481' ,'XX.SERVPAK.SCPPSENU')
What happened?

The CustomPac dialogs find your ISPPROF DD and then concatenate the masterhlq.SCPPSENU to the profile data set. But in your case, it's finding SYS06333.T114558.RA000.ABCSMAC3.R0209481 as your ISPPROF data set.

Modify your ISPPROF to a non-temporary data set.


Why is SDFHLOAD pointing to SYS1.LINKLIB?

This is because you blanked out the variable pointing to “CICS SDFHLOAD DSN” in the CALLLIB DSN variables section of the CustomPac Dialogs. If you use CICS, you should have specified the correct SDFHLOAD data set name. If not, and you blanked out the variable, CustomPac assigns a default of SYS1.LINKLIB. If you do not want the DDDEF to point to SYS1.LINKLIB, modify variable “DFLT CALLLIB DSN” to point to an alternate library. It will not be updated by the calllib processing.