Micro Focus Enterprise Developer 2.3 Update 1 for Eclipse > General Reference > Application Workflow Manager > Workflow Manager Modeling Guide > Setting up the Application Workflow Model > Setting up and Configuring AWM > Master Configuration > Master Configuration on z/OS

Master Configuration on z/OS

Note: This feature is only supported if EDc, EDz or RDz is installed.

If a z/OS system should be attached, the master configuration file will be read by a REXX procedure that must be located under the SYSEXEC or SYSPROC allocation. The name of this REXX procedure is TAUZCAPP.

Note: If AWM is used in RDz with an IBM RSED connection type, the name of the REXX procedure is TAULAPPL instead of TAUZCAPP.

If the user attaches a new remote system to the Tree View, the new system entry will receive the name returned from the master configuration file. The REXX procedure will also be called up to determine or update all AWM model entries which are listed in the master configuration file. At this time a specific AWM model is not loaded.

This REXX procedure is also called each time the user carries out an action for the first time during an Eclipse session that requires a link to the remote system. The following checks run at this call-up:

REXX procedure found?
Could this REXX procedure be found on the remote system? If not, the action will be cancelled with an error message.
Master configuration file present and consistent?
The REXX procedure checks the consistency of the master configuration file. If any error is detected here, they will be communicated to the user in an error dialog. Warnings will be written into the Eclipse .log file.

The dataset name of the master configuration file is specified in TAUZCAPP and TAULAPPL. Both REXX procedures have to be adapted after the z/Server installation, other the mainframe server will not be able to find the master configuration file. See the z/Server Installation Guide for details.