Specifying a z/OS deployment manager migration configuration in the zmmt command response file: Worksheet
Before you migrate a WebSphere® Application Server for z/OS® Version 7.0 or later node to Version 9.0, you must create Job Control Language (JCL) jobs (CNTL and DATA datasets) that you run on z/OS during the migration. You can use the zmmt command with a response file to create the appropriate migration jobs. Print this worksheet, and use it when you collect and specifying information about the WebSphere Application Server for z/OS deployment manager migration configuration variables in the zmmt command response file.
Before you begin
This topic is about profile configuration migration. To migrate your applications to the latest version, use the WebSphere Application Server Migration Toolkit.
Procedure
- Enter create.
-
Specify values for the name and location.
Table 1. Name and location . Enter your values. Variable Response-file variable Example value Your value Profile name profileName Default Profile directory profilePath /AppServer/profiles Template path templatePath zos-migDmgr -
Specify values for the target datasets.
Table 2. Target datasets . Enter your values. Variable Response-file variable Example value Your value High-level qualifier (HLQ) zTargetHLQ DMR -
Specify values for the dataset names, product directory, and intermediate symbolic link.
Table 3. Dataset names, product directory, and intermediate symbolic link Variable Response-file variable Example value Your value JCL procedure library dataset name zmbProclibName SYS1.PROCLIB WebSphere Application Server product directory zmbSMPEHome /usr/lpp/WebSphere/AppServer/V9R0 Intermediate symbolic link: Create intermediate symbolic link intermediateSymlinkPreference Y Path name of intermediate symbolic link IntermediateSymlink /V9/symlink -
Specify values for the configuration file system.
Table 4. Configuration file system Variable Response-file variable Example value Your value Mount point zConfigMountPoint /wasv9config Name zConfigHfsName OMVS.WAS90. CONFIG.HFS Volume, or '*' for SMS zConfigHfsVolume * Primary allocation in cylinders zConfigHfsPrimaryCylinders 420 Secondary allocation in cylinders zConfigHfsSecondaryCylinders 100 File system type: Hierarchical File System (HFS) zFilesystemType HFS File system type: zSeries File System (ZFS) zFilesystemType HFS Storage class name (optional) zmbStorageClass ZSTORCLS Management class name (optional) zmbManagementClass ZMGMTCLS Data class name (optional) zmbDataClass ZDATACLS -
Specify values for server customization.
If you specify a clone migration, you must specify true for Replace Started Procedure Command Names and provide unique procedure names for the new environment. The new environment requires unique procedure names to coexist with the old environment.
Table 5. Server customization Variable Response-file variable Example value Your value Source configuration location: Mount point zmbFromConfigRoot /WebSphere/V7R0 Source configuration location: Home directory zmbFromWASHomeDir DeploymentManager Target configuration location: Mount point zmbToConfigRoot /WebSphere/V9R0 Target configuration location: Home directory zmbToWASHomeDir DeploymentManager Daemon procedure name zmbDaemonProcName BBO8DMN Controller procedure name zmbControllerProcName BBO8DCR Servant procedure name zmbServantProcName BBO8DSR Replace started procedure command names zmbReplaceStartedProcedure Names True WebSphere administrator's user ID zmbAdminUserid user WebSphere administrator's password zmbAdminPassword pa$$ Table 6. Server customization Variable Response-file variable Example value Your value Disable previous deployment manager. If you specify a clone migration, this variable must be set to False
.zmbDisableDmgr True Application migration preference: Migrate applications and use the default application installation directory (D) zmbAppMigrationPreference Y Application migration preference: Migrate and generate administrative scripts to install applications later (S) zmbAppMigrationPreference Y Application migration preference: Migrate applications and use the previous application installation directory (P) zmbAppMigrationPreference Y Application migration preference: Do not migrate applications (N) zmbAppMigrationPreference Y Application migration preference: Migrate applications and use the specified application installation directory (Y) zmbAppMigrationPreference Y Application migration preference: Application installation directory zmbAppInstallDirLine1 /wasv9config/AppServer/profiles/default/installedApps Application migration preference: Application installation directory zmbAppInstallDirLine2 Apps Migrate administrative console customized "My tasks" settings: Migrate the settings for "My tasks" saved in the default workspace user root location (D) zmbWorkspaceRoot Preference D Migrate administrative console customized "My tasks" settings: Migrate the settings for "My tasks" saved in a user defined workspace root location (U) zmbWorkspaceRoot Preference D Migrate administrative console customized "My tasks" settings: User defined workspace root location zmbUserWorkspaceRoot -
Specify values for migration process options.
Table 7. Migration process options Variable Response-file variable Example value Your value Migration trace options: Enable script tracing zmbEnableScriptingTrace False Migration trace options: Enable profile creation tracing zmbEnableProfileTrace False Migration trace options: Enable pre-upgrade tracing zmbEnablePreUpgradeTrace False Migration trace options: Enable post-upgrade tracing zmbEnablePostUpgradeTrace False JVM options for migration processes: Initial heap size (MB) zmbInitialHeapSize 512 JVM options for migration processes: Maximum heap size (MB) zmbMaxHeapSize 768 Other options: Temporary directory location zmbTempDirectory /tmp/migrate Other options: Migration definition identifier zmbTimestamp 05124043 Other options: Java™ temporary directory location zmbJavaTempDirectory /tmp -
Specify how to set port values and resolve port conflicts.
If you specify a clone migration, the useOld option is not valid. Cloned profiles require ports to be unique between the old and new environments.
Table 8. Port values Variable Response-file variable Example value Your value Setting ports: Use the same ports that the old profile used (useOld) zmbSetPorts useOld Setting ports: Select ports manually (generateNew) zmbSetPorts useOld Setting ports: Generate new ports, incrementing from a common starting port value (startingPort) zmbSetPorts useOld Setting ports: Generate new ports: Starting port value zmbStartingPort 1024 Port conflict resolution: Increment from the conflicted port value (incrementCurrent) zmbResolvePortConflicts incrementCurrent Port conflict resolution: Increment from a common starting port value (startingPort) zmbResolvePortConflicts incrementCurrent Port conflict resolution: Starting port value zmbStartingPort 1024 -
Specify value for clone migration.
Table 9. Name and location . Enter your values: Variable Response-file variable Example value Your value Clone migration zmbCloneMigration
False -
If you specified true for a clone migration, specify values for new short
names.
Table 10. Name and location . Enter your values: Variable Response-file variable Example value Your value New cell short name zmbCellShortName
MIGRCELL New node short name zmbNodeShortName
MIGRNODE New server short name zmbServerShortName
MIGRSVR Cluster short prefix zmbClusterShortPrefix
V9C Daemon job name zmbDaemonJobName
BBODMNC -
Specify values for job statement definition.
Table 11. Job statement definition . Enter your values: Variable Response-file variable Example value Your value //jobname JOB zJobStatement1 (ACCTNO,ROOM),'USERID', CLASS=A,REGION=OM //* zJobStatement2 //* //* zJobStatement3 //* //* zJobStatement4 //*