Variables for using the zpmt command to enable existing z/OS deployment managers for the feature pack

The zpmt command uses the values that you specify for the variables defined in a response file to create customization data and instructions for augmenting an existing deployment manager with the feature pack or the SDO feature.

Action

augment

Profile information

Profile name (profileName)
Name assigned to the generated customization jobs
Profile path (profilePath)
Profile path
Template path (templatePath)
Template path

Target dataset information

Target operating system (targetOS)
Target operating system
High-level qualifier (zTargetHLQ)
High-level qualifier for the target z/OS® data sets that will contain the generated jobs and instructions
When a customization definition is uploaded to the target z/OS system, the customization jobs and files are written to a pair of partitioned datasets. While is it possible to reuse these datasets, it is safest to create separate datasets for each WebSphere® Application Server for z/OS configuration. The best practice is to use the customization dataset name prefix (sometimes referred to as "config_hlq") to indicate the version and release of WebSphere Application Server for z/OS, the task that you are performing, and the cell (as well as the node name in some cases) that you are configuring. For example, you might use the following dataset name prefix for configuring a standalone WebSphere Application Server cell named TESTCELL for Version 7.0:
SYSPROG1.WAS70.TESTCELL.APPSERV
In this example, the following two datasets will be created when the customization definition is uploaded to the target z/OS system:
SYSPROG1.WAS70.TESTCELL.APPSERV.CNTL
SYSPROG1.WAS70.TESTCELL.APPSERV.DATA
The CNTL dataset will be a partitioned dataset (PDS) with fixed block 80-byte records that will contain the customization jobs. The DATA dataset will be a PDS with variable length data to contain the other customization data.
Rule: The high-level qualifier can consist of multiple qualifiers (up to 39 characters).
The generated batch jobs and instructions will be uploaded to two z/OS partitioned datasets:
HLQ.CNTL
Partitioned dataset with fixed block 80-byte records to contain customization jobs
HLQ.DATA
Partitioned dataset with variable-length data to contain other data contained in the customization definition
Tip: A multilevel high-level qualifier can be specified as the dataset high-level qualifier.

Configuration file system customization

Mount point (zConfigMountPoint)
Read/write file system directory mount point where application data and environment files are written

The customization process creates this mount point if it does not already exist.

Directory path name relative to mount point (zWasServerDir)
Name of the directory where WebSphere Application Server for z/OS files reside after installation

Product file system information

Product file system directory (zSmpePath)
Name of the directory where WebSphere Application Server for z/OS files reside after installation

Feature-pack file system information

Product file system directory (zScaSmpePath or zSdoSmpePath)
Name of the directory where feature-pack files reside after installation
Intermediate symbolic link? (zEnableScaIntermediateSymlink or zEnableSdoIntermediateSymlink)
Specify true to set up an intermediate symbolic link, and specify the path name of that link if you select it.

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.

The default value is true.

Intermediate symbolic link (zScaIntermediateSymlink or zSdoIntermediateSymlink)
The default value is the zConfigMountPoint value appended by /fpscasmpe or /fpsdosmpe.

Target Node Administrative Security

Target node is managed by a z/OS security product? (zAdminSecurityType)
Specify zAdminSecurityType=websphereForZos if the target node is managed by a z/OS security product
SAF profile prefix (zSAFProfilePrefix)
Valid SAF profile prefix

This parameter is only valid for augmenting an existing standalone application server with the feature pack; it is not valid for augmenting an existing standalone application server with the SDO feature.

Rule: Prefix must be eight or fewer characters.

Job statement customization

Job statement 1 (zJobStatement1)
Job statement 2 (zJobStatement2)
Job statement 3 (zJobStatement3)
Job statement 4 (zJobStatement4)
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: May 16, 2013 11:33:12 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=rins_defvar3def_fp_cmdl_enable
File name: rins_defvar3def_fp_cmdl_enable.html