Configuration variables for migrating a z/OS stand-alone application server 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 stand-alone application server.

Este artigo trata da migração da configuração de perfil. Para migrar seus aplicativos para a versão mais recente, use o Kit de Ferramentas de Migração do WebSphere Application Server. Para obter mais informações, consulte o Kit de ferramentas de migração no WASdev.
sptcfgResponse-file variables
- Required keyword to indicate the creation of a new migration definition
- 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.
- Path name of intermediate symbolic link
This link will be created by the customization jobs, pointing to the product file system directory.
- Path name of intermediate symbolic link
- Name of the profile created during migration
This is always "default" on the z/OS platform.
- Fully qualified path where the generated migration definition output should be written
- Template pathOne of the following values:
- 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.
- 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. - Number of secondary cylinders that will be allocated to the configuration
file systemRecommendation: The minimum suggested size is 100 cylinders.
- 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.
- File system directory mount point where application data and environment
files are written
The configuration file system is where the configuration for the node being migrated is physically stored. You can choose to use an existing Versão 9.0 file system if you already have an appropriate file system on the node being migrated. If you choose to use an existing Versão 9.0 file system, you need to ensure that the mount point that you specify here is present before running the migration jobs that are created using this tool. If you choose to create a new Versão 9.0 file system on the node being migrated, the actual creation of the new file system will not occur until you run the optional BBOMBHFS or BBOMBZFS job during the actual migration process. In any case, you must specify the correct value here for the mount point.
- Type of file systemOne 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
- HFS
- 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.
- High-level qualifier for the target z/OS datasets
that will contain the generated jobs and instructionsNote: A multilevel high-level qualifier can be specified as the dataset high-level qualifier.
- How you would like to migrate your installed applications
One of the following values:Note: WebSphere Application Server system applications will migrate regardless of the value set here.
- Name of the JCL started procedure used to start the migrated controllers
When migrating to Versão 9.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.
- Name of the JCL started procedure used to start the migrated servants
When migrating to Versão 9.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.
- Name of the JCL started procedure used to start the migrated daemon
When migrating to Versão 9.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.
- Name of the JCL started procedure used to start the migrated adjunct
When migrating to Versão 9.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.
- 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: - Enable (true) or disable (false) trace during the WASPostUpgrade process
- Enable (true) or disable (false) trace during the WASPreUpgrade process
- Enable (true) or disable (false) trace during profile creation
- Enable (true) or disable (false) trace of the home creation, profile and migration tooling invocation, and final processing phases of migration
- Mount point of the configuration from which you are migrating
- Home directory of the configuration from which you are migrating
- The initial memory allocated for the JVM heap.
- Install the default application that contains the Snoop, Hello, and HitCount servlets
- Specify whether to deploy the sample applications.Note: These applications are not supported in a WebSphere Application Server, Network Deployment cell.
Install the sample applications to use the application server and evaluate the latest technological advancements. The sample applications are not recommended for deployment to production application server environments.
- A Java temporary directory that is used by the Java virtual machine to create and story temporary files during migration.
- Indicates whether the source profile is registered to an administrative agent.
- The maximum heap size that can be allocated for the JVM heap.
- The host name of the source administrative agent.
- If security is enabled, the administrative security password for the source administrative agent.
- The file system path of the source administrative agent.
- The port that the source administrative agent used for SOAP connections.
- If security is enabled, the user name for the source administrative agent.
- The host name of the target administrative agent.
- If security is enabled, the administrative security password for the target administrative agent.
- The file system path of the target administrative agent.
- The port that the target administrative agent uses for SOAP connections.
- If security is enabled, the user name for the target administrative agent.
- Existing procedure library to which the WebSphere Application Server for z/OS cataloged procedures are to be copied
- Define how to handle port conflicts by specifying one of the following values.
- Define which port values to use in the new profile by specifying one of the following values.
- Location of your WebSphere Application Server Versão 9.0 installed product file system
- 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.
- Identifier that will be used to create a directory under the temporary directory that will contain the temporary migration datasets and backup configuration data
- Mount point of the configuration to which you are migrating
This is the same value that is specified for the zConfigMountPoint variable.
- Home directory of the configuration to which you are migrating
- 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)
- User-defined workspace root location
- 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.
- Path name of intermediate symbolic link
This link will be created by the customization jobs, pointing to the product file system directory.
- Path name of intermediate symbolic link
Sample of a response file for migrating a stand-alone application server
create
EnableIntermediateSymlink=false
EnableJavaTmpDir=true
intermediateSymlinkPreference=N
profileName=default
profilePath=<root>/profiles/ZMigSASrv01
templatePath=<root>/profileTemplates/zos-migStandalone
zConfigHfsName=OMVS.WAS90.CONFIG.HFS
zConfigHfsPrimaryCylinders=420
zConfigHfsSecondaryCylinders=100
zConfigHfsVolume=*
zConfigMountPoint=/wasv9config
zFilesystemType=HFS
zJobStatement1=(ACCTNO,ROOM),'USERID',CLASS=A,REGION=0M
zJobStatement2=//*
zJobStatement3=//*
zJobStatement4=//*
zTargetHLQ=SAS
zmbAdjunctProcName=BBO9CRA
zmbAppInstallDirLine1=/wasv9config/AppServer/profiles/default/installedApps
zmbAppInstallDirLine2=
zmbAppMigrationPreference=D
zmbControllerProcName=BBO9ACR
zmbDaemonProcName=BBO9DMN
zmbEnablePostUpgradeTrace=0
zmbEnablePreUpgradeTrace=0
zmbEnableProfileTrace=0
zmbEnableScriptingTrace=0
zmbFromConfigRoot=/WebSphere/V7R0
zmbFromWASHomeDir=AppServer
zmbInitialHeapSize=512
zmbInstallDefaultApp=false
zmbInstallSamples=false
zmbJavaTempDirectory=/tmp
zmbManagedBaseNode=true
zmbMaxHeapSize=768
zmbNewAdminAgentHostname=localhost
zmbNewAdminAgentProfilePath=/WebSphere/V9R0/AdminAgent
zmbNewAdminAgentSoapPort=8880
zmbOldAdminAgentHostname=localhost
zmbOldAdminAgentProfilePath=/WebSphere/V7R0/AdminAgent
zmbOldAdminAgentSoapPort=8879
zmbProclibName=SYS1.PROCLIB
zmbReplaceStartedProcedureNames=true
zmbResolvePortConflicts=incrementCurrent
zmbSMPEHome=/usr/lpp/WebSphere/AppServer/V9R0
zmbServantProcName=BBO9ASR
zmbSetPorts=useOld
zmbTempDirectory=/tmp/migrate
zmbTimestamp=05160419
zmbToConfigRoot=/wasv9config
zmbToWASHomeDir=AppServer
zmbWorkspaceRootPreference=D