Configuration variables for migrating a z/OS deployment manager by using the zmmt command

Response-file variables

create

Required keyword to indicate the creation of a new migration definition

intermediateSymlinkPreference

Whether to set up an intermediate symbolic link

If you specify an intermediate symbolic link, symbolic links are created from the configuration file system to the intermediate symbolic link; otherwise, they are created directly to the product file system.

IntermediateSymlink

Path name of intermediate symbolic link

This link is created by the customization jobs, pointing to the product file system directory.

profileName

Name of the profile that is created during migration

This is always "default" on the z/OS platform.

profilePath

Fully qualified path where the generated migration definition output is written

templatePath

Template path

One of the following values:

• zos-migDmgr

  Migrate a deployment manager

• zos-migFederated

  Migrate a federated node

• zos-migStandalone

  Migrate a stand-alone application server

zConfigHfsName

Name of the MVS™ dataset that contains the configuration file system

This name is used as input to the migration job that creates the configuration file system.

zConfigHfsPrimaryCylinders

Number of primary cylinders that are allocated to the configuration file system

In an application server, the total space that is needed for this dataset increases with the size and number of installed applications.

Recommendation: The minimum suggested size is 420 cylinders.

zConfigHfsSecondaryCylinders

Number of secondary cylinders that are allocated to the configuration file system

Recommendation: The minimum suggested size is 100 cylinders.

zConfigHfsVolume

DASD volume serial number to contain the dataset, or "*" to let SMS select a volume

Using "*" requires that SMS automatic class selection (ACS) routines be in place to select the volume. If you do not have SMS set up to handle dataset allocation automatically, list the volume explicitly.

zmbStorageClass

The name of the SMS storage class for the configuration file system. If you do not assign a name, the value will be determined by the automatic class selection routines established by your storage administrator.

zmbManagementClass

The name of the SMS management class for the configuration file system. If you do not assign a name, the value will be determined by the automatic class selection routines established by your storage administrator.

zmbDataClass

The name of the SMS data class for the configuration file system. If you do not assign a name, the value will be determined by the automatic class selection routines established by your storage administrator.

zConfigMountPoint

File system directory mount point where application data and environment files are written

The configuration file system is where the configuration for the node that is being migrated is physically stored. You can choose to use an existing Version 9.0 file system if you already have an appropriate file system on the node that is being migrated. If you choose to use an existing Version 9.0 file system, you need to ensure that the mount point that you specify here is present before you run the migration jobs that are created by using this tool. If you choose to create a new Version 9.0 file system on the node that is being migrated, the creation of the new file system does not occur until you run the optional BBOMDHFS or BBOMDZFS job during the actual migration process. In any case, you must specify the correct value here for the mount point.

zFilesystemType

Type of file system

One of the following values:

• HFS

  Allocate and mount your configuration file system dataset by using the Hierarchical File System

• ZFS

  Allocate and mount your configuration file system dataset by using the zSeries File System

zJobStatement1 . . . n

Customizable JOB statements that are used for the generated migration jobs

All the migration jobs that are tailored for you need a job statement. Enter a valid job statement for your installation. The migration creation process updates the job name for you in all the generated jobs, so you do not need to be concerned with that portion of the job statement. If continuation lines are needed, replace the comment lines with continuation lines.

zTargetHLQ

High-level qualifier for the target z/OS datasets that contain the generated jobs and instructions

Note: A multilevel high-level qualifier can be specified as the dataset high-level qualifier.

zmbAdminUserid

User ID of an administrator that is used to manage the node that is being migrated

This is required to perform required administrative actions during the migration process.

zmbAdminPassword

Password for the user ID of the administrator that is used to manage the node that is being migrated

This is required to perform required administrative actions during the migration process.

zmbAppMigrationPreference

How you would like to migrate your installed applications

One of the following values:

• D

  Install user enterprise applications in the default application installation directory as part of the migration

• Y

  Install user enterprise applications in a directory that is specified in the following variables as part of the migration

  zmbAppInstallDirLine1

  zmbAppInstallDirLine2

  Location where WebSphere Application Server installs your enterprise applications

  This location is used when you specify that you want to migrate and install applications as your application migration preference. You can choose a customized environment-specific location or use the default location.

  If the location path length exceeds 60 characters, then it must be specified on two lines as shown; but it cannot exceed a total length of 120 characters.

  Leave these two fields blank unless you specify Y for zmbAppMigrationPreference.

• S

  Prepare user enterprise applications for installation in the WebSphere Application Server Version 9.0 installableApps directory without installing them during migration

  Scripts that can be used to install these applications are generated and saved in the migration backup directory. For WebSphere Application Server for z/OS, the location of this backup directory is relative to the temporary directory that you specify for the zmbTempDirectory variable. The location of the backup directory is also determined by the derived migration identifier and the type of node that is being migrated. If you specify /tmp/migrate as the temporary directory and the derived migration identifier is 55449, for example, then the location of the generated scripts is:

  /tmp/migrate/55449/nodetype_backup/

  where nodetype is dmgr, fed, or base, depending on the type of node that you are migrating.

  You can then run these files at any point and in any combination after migration completes. You can also reorganize and combine these files for better application installation efficiency. Read the "Wsadmin tool" article in the documentation for additional information.

• P

  Install user enterprise applications as part of the migration, and keep the same application installation directories as the previous version

  Restrictions: If you select this option, the location is shared by the existing WebSphere Application Server Version 7.0 installation and the Version 9.0 installation. If you keep the migrated applications in the same locations as those applications of the previous version, the following restrictions apply:

  • The WebSphere Application Server Version 9.0 mixed-node support limitations must be followed. This means that the following support cannot be used when you evoke the wsadmin command:
    • Precompile JSP
    • Use Binary Configuration
    • Deploy EJB
  • You risk losing the migrated applications unintentionally if you later delete applications from these locations when administering (uninstalling for example) your Version 7.0 installation.
  • Any application that is installed relative to a Version 7.0 variable is installed relative to the location that is assigned to that variable in Version 9.0. The absolute location is not preserved; the application is migrated to the relative location within the new Version 9.0 environment.
    If the binaries URL in the deployment.xml file for an application that is to be migrated has a path that is relative to WebSphere Application Server, which means it begins with $(APP_INSTALL_ROOT), $(WAS_INSTALL_ROOT), and so on, the new WebSphere Application Server variable value is used to resolve the path when the application is installed in the new location. This leads to the following results when you select this option:

    • Any application that is installed in a directory location relative to a WebSphere Application Server variable is installed under that variable value in Version 9.0.
    • Any application that is installed in a directory location that is not relative to a WebSphere Application Server variable is migrated and overwritten in that same directory. If an application is installed in the /employee_records/retrieval_Apps directory, for example, the application is migrated and overwritten in the /employee_records/retrieval_Apps directory.
• N

  Do nothing with user enterprise applications

Note: WebSphere Application Server system applications will migrate regardless of the value set here.

zmbControllerProcName

Name of the JCL started procedure that is used to start the migrated controllers

When you migrate to Version 9.0, you must upgrade your JCL started procedures. A new started procedure is generated for you during migration. You can specify a new name for the controller procedure or use the old one.

zmbServantProcName

Name of the JCL started procedure that is used to start the migrated servants

When you migrate to Version 9.0, you must upgrade your JCL started procedures. A new started procedure is generated for you during migration. You can specify a new name for the servant procedure or use the old one.

zmbDaemonProcName

Name of the JCL started procedure that is used to start the migrated daemon

When you migrate to Version 9.0, you must upgrade your JCL started procedures. A new started procedure is generated for you during migration. You can specify a new name for the daemon procedure or use the old one.

zmbReplaceStartedProcedureNames

Whether to update the START commands in the configuration with the new names specified (true) or to preserve the same names (false).

If you specified new names for your JCL procedures, then the corresponding START commands in the WebSphere Application Server configuration must be updated to match the new procedure names. Specify true for this variable to perform this configuration update. You must provide unique names and specify true if you specified a clone migration. The new environment requires unique procedure names to coexist with the old environment.

If you choose to use the same procedure names, then specify false for this variable. If you are not using consistent procedure names for all the servers of a given process type (all servants for example) for the node that you are migrating, then it is recommended that you specify false for this variable. In this case, you need to keep the same START commands and manually replace the procedures by using the procedure that is generated during migration as a template.

Notes:

• Your Version 9.0 configuration must use different JCL procedures from those procedures that are used by your Version 7.0 configuration. The migration process creates new Version 9.0 JCL procedures by using the procedure names specified here.
• If you use the same names as you used in your Version 7.0 configuration, the migration process overlays the existing procedures. If you are using the same names, make sure that you back up the existing Version 7.0 procedures before you run the migration jobs in case you need to roll back later.

zmbDisableDmgr

Whether (true) or not (false) to disable the previous deployment manager during migration

If the Version 7.0 deployment manager is not disabled, you can continue to use it while the migration is completed.

Caution: Use this option with care. The reason that WebSphere Application Server Version 7.0 deployment managers normally are stopped and disabled is to prevent multiple deployment managers from managing the same nodes. You must stop the Version 7.0 deployment manager before you start by using the Version 9.0 deployment manager. Deselecting this option means that any configuration changes made in the old configuration during migration might not be migrated.

If you have specified true for zmbCloneMigration, you must specify false for this option. The old deployment manager must remain enabled during a clone migration.

zmbEnablePostUpgradeTrace

Enable (true) or disable (false) trace during the WASPostUpgrade process

zmbEnablePreUpgradeTrace

Enable (true) or disable (false) trace during the WASPreUpgrade process

zmbEnableProfileTrace

Enable (true) or disable (false) trace during profile creation

zmbEnableScriptingTrace

Enable (true) or disable (false) trace of the home creation, profile and migration tooling invocation, and final processing phases of migration

zmbFromConfigRoot

Mount point of the configuration from which you are migrating

zmbFromWASHomeDir

Home directory of the configuration from which you are migrating

zmbInitialHeapSize

The initial memory that is allocated for the JVM heap.

zmbJavaTempDirectory

A Java™ temporary directory that is used by the Java virtual machine to create and story temporary files during migration.

zmbMaxHeapSize

The maximum heap size that can be allocated for the JVM heap.

zmbProclibName

Existing procedure library to which the WebSphere Application Server for z/OS cataloged procedures are to be copied

zmbResolvePortConflicts

Define how to handle port conflicts by specifying one of the following values.

• incrementCurrent

  If a port conflict is detected, the port value is incremented from the conflicting port to the next available port value.

• startingPort
  If a port conflict is detected, the port value is incremented from the specified value to the next available port value.

  Note: If both zmbResolvePortConflicts and zmbSetPorts are set to startingPort, the zmbResolvePortConflicts variable is ignored.

  zmbStartingPort

  The starting port value from which new ports are generated.

zmbSetPorts

Define which port values to use in the new profile by specifying one of the following values.

• useOld

  Reuse the port values that are defined in the source profile. This value is not valid if zmbCloneMigration is set to true. The new profile must have different ports from the old profile after a clone migration.

• generateNew

  Set custom values for each port in the target profile.

• startingPort

  Generate new ports by incrementing from the specified port value. Conflicting ports are automatically resolved.

  zmbStartingPort

  The starting port value from which new ports are generated.

zmbSMPEHome

Location of your WebSphere Application Server Version 9.0 installed product file system

zmbTempDirectory

The directory where the backup of your previous configuration and the migration trace is written.

During migration, a backup copy of the previous version's configuration is required. The default location of this backup is /tmp/migrate. If the /tmp file system does not have adequate space to store the backup configuration, you can specify another location. If you choose to override the default location of the backup copy, the best practice is to keep the same naming convention and replace the /tmp portion with another path, /myTemp/migrate for example.

zmbTimestamp

Identifier that is used to create a directory under the temporary directory that contains the temporary migration datasets and backup configuration data

zmbToConfigRoot

Mount point of the configuration to which you are migrating

This is the same value that is specified for the zConfigMountPoint variable.

zmbToWASHomeDir

Home directory of the configuration to which you are migrating

zmbWorkspaceRootPreference

Whether to migrate the administrative console customized "My tasks" settings that are saved in the default workspace user root location (D) or to migrate the settings that are saved in a user-defined workspace root location (U)

zmbUserWorkspaceRoot

User-defined workspace root location

zmbCloneMigration

Specifies whether to perform a clone migration, true, or standard migration, false, of the old profile. If you intend to clone the nodes that are managed by this deployment manager, you must also clone this deployment manager.

zmbCellShortName

The short name of the new cell. Required if zmbCloneMigration is set to true. Not used if zmbCloneMigration is set to false.

zmbNodeShortName

The short name of the new deployment manager node. Required if zmbCloneMigration is set to true. Not used if zmbCloneMigration is set to false.

zmbServerShortName

The short name of the deployment manager server. Required if zmbCloneMigration is set to true. Not used if zmbCloneMigration is set to false.

zmbClusterShortPrefix

A prefix, up to 3 characters, used to generate unique short names for clusters and node groups in the new profile. Required if zmbCloneMigration is set to true. Not used if zmbCloneMigration is set to false.

zmbDaemonJobName

A name for the location services daemon in the new environment. The name must be different from the daemon in the old environment. Required if zmbCloneMigration is set to true. Not used if zmbCloneMigration is set to false.