File name conversions for MVS

TeamConnection ®le names are modi®ed by the MVS build server according to the following rules:

vThe directory path of a ®le name is not used. All characters of a ®le name up to and including the rightmost slash (/ or \) are thrown away.

vLowercase characters are converted to uppercase characters.

vThe ®le extensions are stripped from the right, up to and including the leftmost period. The extension, minus the period, is used by the MVS build tool to direct the ®le to particular data sets according to user-speci®ed syntax in the MVS build scripts.

vThe remaining name is truncated from the left, to a maximum of 8 characters.

vNames must contain characters that are valid in MVS. MVS allows the following characters:

0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ$@#

However, the name must begin with an alphabetic character.

vUnderscore characters (_) in a base name are converted to at signs (@).

The following are examples of how a TeamConnection name is converted:

vA TeamConnection ®le name of src\build\fhbldobj.C is converted to FHBLDOBJ on MVS.

vA TeamConnection ®le name of src/build/fhbtruncate.c is converted to FHBTRUNC on MVS.

In both of these examples, the .C or .c is split away. The MVS build server uses the resulting extension to resolve and possibly allocate the MVS data sets needed for the build process. The extensions are required for parts that participate in an MVS build.

A TeamConnection ®le name of src\build\fhbtest.c.old is converted to FHBTEST, and c.old becomes the extension.

Passing parameters to an MVS build script

To pass parameters to your build script, specify them in the Parameters attribute of the builder. These are passed to MVS through the combination of the PARM keyword parameter on an EXEC card and the &TCPARM variable.

Note: Take extra care to use no single or double quotes in the Parameters attribute of the MVS builder de®nition. This rule follows standard JCL syntax for parameter substitution in the PARM keyword parameter of an EXEC statement.

You can use the &TCPARM variable in your MVS build scripts. This variable is substituted with any parameters that were speci®ed using the -parameter attribute of the builder command or the Parameters ®eld on the Create Builder window when the builder was created.

You can also use the following TeamConnection variables in writing MVS build scripts:

164User's Guide

Page 184
Image 184
IBM SC34-4499-03 manual File name conversions for MVS, Passing parameters to an MVS build script