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.
This article 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.
sptcfgThis is always default on the z/OS platform.
This name is used as input to the migration job that creates the configuration file system.
In an application server, the total space needed for this dataset increases with the size and number of installed applications.
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.
Allocate and mount your configuration file system dataset using the Hierarchical File System
Allocate and mount your configuration file system dataset using the zSeries® File System
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.
This is required to perform required administrative actions during the migration process.
This is required to perform required administrative actions during the migration process.
When migrating to Version 8.5, 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.
When migrating to Version 8.5, 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.
When migrating to Version 8.5, 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.
When migrating to Version 8.5, 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.
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.
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.1 configuration definitions, for example, you might want to specify true for this variable.
If you want to use a cell that contains Version 6.1 nodes, you must specify true for this variable.
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.
This is the same value that is specified for the zConfigMountPoint variable.
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.
This link will be created by the customization jobs, pointing to the product file system directory.
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.5
zmbServantProcName=BBO7ASR
zmbTempDirectory=/tmp/migrate
zmbTimestamp=30083908
zmbToConfigRoot=/wasv8config
zmbToWASHomeDir=AppServer
zmbWorkspaceRootPreference=D
intermediateSymlinkPreference=Y
IntermediateSymlink=/V80SMPE/symblink