z/TPF Program Management - IBM

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
version (for example, .evspec.xml descriptor for business event processing),
each descriptor file must contain a unique key.
You can use the E-type loader to load and activate new versions of deployment
descriptors. These new versions have the same file name and must have the
same key, type, and version as the previously loaded versions.
IBM uses the following conventions for schemas that define deployment descriptors
that use common deployment:
v Include the unique file extension of the deployment descriptor in the schema
name and use the following naming convention: tpf-function_unique_name.xsd,
where function_unique_name is the unique name for the deployment descriptor.
v IBM-delivered schemas are placed on Linux in relative directory
base/tpf-fdes/schema/.
v Schema files must be loaded to the /sys/tpf_pbfiles/tpf-fdes/schema/
directory on the z/TPF system.
Related reference:
Deployment descriptors
Use this information as a reference guide to deployment descriptors that are
supported by the z/TPF system.
Common deployment configuration file
38 z/TPF Program Management
The z/TPF system uses a configuration file to identify each function or component
that uses common deployment.
The common deployment configuration file is a comma-separated values (.csv) file
that is delivered with the z/TPF product code. The file name and location of the
configuration file, as delivered from IBM, is base/tpf-fdes/fdes-config.csv. To use
common deployment, the fdes-config.csv configuration file must be loaded to the
/sys/tpf_pbfiles/tpf-fdes/ directory on the z/TPF system with the image loader.
For more information about the image loader, see “z/TPF loaders” on page 19.
Each row of the common deployment configuration file identifies one type of
deployment descriptor, as described in Table 3.
Table 3. Common deployment configuration file format
Field Description
1 Unique file extension for the deployment descriptor.
2 4-character name of the function-unique processing program.
3 Automatic deployment indicator, where:
YES
Automatically deploys the deployment descriptor the first time that it is loaded
and activated on the system. You can use the ZMDES command with the
UNDEPLOY parameter specified to undeploy the deployment descriptor.
If an existing deployment descriptor is loaded and activated again to make a
change to the descriptor, the existing deployment status is used.
NO Does not automatically deploy the deployment descriptor. Use the ZMDES
command with the DEPLOY parameter specified to deploy the deployment
descriptor.