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.
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.