Configuration variables for migrating a z/OS federated node using the zmmt command

Before you migrate WebSphere® Application Server for z/OS®, you must create Job Control Language (JCL) jobs (CNTL and DATA datasets) that you will run during the actual migration. You can use the zmmt command with a response file to create the appropriate migration jobs. The migration response file contains a set of configuration variables that you use to create jobs for migrating a federated node.

Supported configurations Supported configurations:

This topic is about configuration migration, such as migrating deployment managers and federated nodes in a network deployment environment. The Application Migration Toolkit for WebSphere Application Server provides support for migrating applications from previous versions of WebSphere Application Server to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.

sptcfg

Response-file variables

create
Required keyword to indicate the creation of a new migration definition
profileName
Name of the profile created during migration

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

profilePath
Fully qualified path where the generated migration definition output should be 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 will contain 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 will be allocated to the configuration file system

In an application server, the total space 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 will be allocated to the configuration file system
Recommendation: The minimum suggested size is 100 cylinders.
zConfigHfsVolume
DASD volume serial number to contain the above 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.

zConfigMountPoint
File system directory mount point where application data and environment files are written
zFilesystemType
Type of file system
One of the following values:
  • HFS

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

  • ZFS

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

zJobStatement1 . . . n
Customizable JOB statements that will be used for the generated migration jobs

All the migration jobs that will be tailored for you will need a job statement. Enter a valid job statement for your installation. The migration creation process will update 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 will 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.

zmbControllerProcName
Name of the JCL started procedure used to start the migrated controllers

When migrating to Version 8.0, you must upgrade your JCL started procedures. A new started procedure will be 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 used to start the migrated servants

When migrating to Version 8.0, you must upgrade your JCL started procedures. A new started procedure will be 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 used to start the migrated daemon

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

zmbAdjunctProcName
Name of the JCL started procedure used to start the migrated adjunct

When migrating to Version 8.0, you must upgrade your JCL started procedures. A new started procedure will be generated for you during migration. You can specify a new name for the adjunct 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.

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 will need to keep the same START commands and manually replace the procedures using the procedure that is generated during migration as a template.

Notes:
  • Your Version 8.0 configuration must use different JCL procedures from those used by your Version 6.x configuration. The migration process creates new Version 8.0 JCL procedures using the procedure names specified here.
  • If you use the same names as you used in your Version 6.x configuration, the migration process overlays the existing procedures. If you are using the same names, make sure that you back up the existing Version 6.x procedures before running the migration jobs in case you need to roll back later.
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
zmbEnableScriptCompatibility
Whether (true) or not (false) to migrate to support script compatibility
This specifies whether or not migration should create the following Version 6.x configuration definitions:
  • Transport
  • ProcessDef
  • Version 6.x SSL
  • Version 6.x ORB service threadpool
instead of the following Version 8.0 configuration definitions:
  • Channels
  • ProcessDefs
  • Version 8.0 SSL
  • Version 8.0 ORB service threadpool

Choose to migrate to support script compatibility if you want to minimize impacts to existing administration scripts. If you have existing wsadmin scripts or programs that use third-party configuration APIs to create or modify the Version 6.x configuration definitions, for example, you might want to specify true for this variable.

If you want to use a cell that contains Version 6.x nodes, you must specify true for this variable.

Note: This is meant to provide a temporary transition until all of the nodes in the environment are at the Version 8.0 level. When they are all at the Version 8.0 level, you should perform the following actions:
  1. Modify your administration scripts to use all of the Version 8.0 settings.
  2. Use the convertScriptCompatability command to convert your configurations to match all of the Version 8.0 settings.

    Read convertScriptCompatibility command for more information.

zmbFromConfigRoot
Mount point of the configuration from which you are migrating
zmbFromWASHomeDir
Home directory of the configuration from which you are migrating
zmbProclibName
Existing procedure library to which the WebSphere Application Server for z/OS cataloged procedures are to be copied
zmbSMPEHome
Location of your WebSphere Application Server Version 8.0 SMPE installed product file system
zmbTempDirectory
The directory where the backup of your previous configuration and the migration trace are 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 just replace the /tmp portion with another path, /myTemp/migrate for example.

zmbTimestamp
Identifier that will be used to create a directory under the temporary directory that will contain 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 saved in the default workspace user root location (D) or to migrate the settings saved in a user-defined workspace root location (U)
zmbUserWorkspaceRoot
User-defined workspace root location
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 will be created by the customization jobs, pointing to the product file system directory.

Example

create
profileName=default
profilePath=/zmmt/workspace/.metadata/.plugins/com.ibm.ws390.mmt.config/profiles/ZMigFed01
templatePath=zos-migFederated
zConfigHfsName=OMVS.WAS80.CONFIG.HFS
zConfigHfsPrimaryCylinders=420
zConfigHfsSecondaryCylinders=100
zConfigHfsVolume=*
zConfigMountPoint=/wasv8config
zFilesystemType=HFS
zJobStatement1=(ACCTNO,ROOM),'USERID',CLASS=A,REGION=0M
zJobStatement2=//*
zJobStatement3=//*
zJobStatement4=//*
zTargetHLQ=FED
zmbAdjunctProcName=BBO7CRA
zmbAdminPassword=XXXXXXXX
zmbAdminUserid=XXXXXXXX
zmbControllerProcName=BBO7ACR
zmbDaemonProcName=BBO7DMN
zmbEnablePostUpgradeTrace=false
zmbEnablePreUpgradeTrace=true
zmbEnableProfileTrace=false
zmbEnableScriptCompatibility=true
zmbEnableScriptingTrace=true
zmbFromConfigRoot=/WebSphere/V5R1M0
zmbFromWASHomeDir=AppServer
zmbProclibName=SYS1.PROCLIB
zmbReplaceStartedProcedureNames=true
zmbSMPEHome=/usr/lpp/zWebSphere/Version 8.0
zmbServantProcName=BBO7ASR
zmbTempDirectory=/tmp/migrate
zmbTimestamp=30083908
zmbToConfigRoot=/wasv8config
zmbToWASHomeDir=AppServer
zmbWorkspaceRootPreference=D
intermediateSymlinkPreference=Y 
IntermediateSymlink=/V80SMPE/symblink



Related tasks
Specifying a z/OS federated node migration configuration in the zmmt command response file: Worksheet
Preparing to migrate a z/OS federated node using the zmmt command
Related reference
convertScriptCompatibility command
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 6, 2014 11:54:51 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-zos&topic=cmig_zmmt_cmd_fednodevar
File name: cmig_zmmt_cmd_fednodevar.html