OpenMake Meister

Customizing File Type Extensions

Because not all z/OS installations use the same naming standards for datasets, it may be necessary to update the Rules and Methods of the z/OS Build Types to use different names for the TYPE qualifier.

For example, instead of using:

.COBOL(member) compiled into .LOAD(member)

The names should be:

.COB(member) compiled into .LOADLIB(member)

In order to use new dataset names for a particular Build Type, the Rules and Methods associated to the Build Type must be updated.

The Web Client is used to update the Build Rules.  In order to update the Build Rules, you must be an Administrator or have Group Privileges to access the Build Type.  

To update a Build Rule go to the “Build Types and Rules” main menu option from the Web Client and select the z/OS operating system.  This will display each of the Rules associated to the Build Type.  The Build Rules indicate the names of the Type qualifier for the source dependency libraries and the Type qualifier name for the load libraries. 

If your Type qualifier names are different, you will need to edit the Rule.  For “Dependency File Extension” Type qualifier names, simply add the new name to the Dependency File Extension list.  For “Intermediate” or “Final Target File Extension” Type qualifiers, you will need to change the name. This is because multiple Type qualifiers can be used as input to the compile step; however only one load library can be specified. Multiple load modules cannot be created for a single compile step.

Once you have updated your Rules, you will also need to update the corresponding Methods.  When updating the Rule, the associated Build Method will be displayed in the "Command to Execute" field on the Build Rule Detail Screen.  Take note of which Methods you will need to update when you change the Build Rule File Extension Types.