Creating a model workspace for push-to-client configuration

A model workspace is a Developer for z/OS® workspace from which you create the remote system connections, configuration files, and preference settings to be distributed to other client workstations.

About this task

Creating a model workspace for push-to-client configurations is no different from creating any other Developer for z/OS workspace. It is good practice to dedicate a workspace to configuration so that other development activities do not alter the remote system connections, configuration files, and preference settings that are intended for general distribution. The purpose of using a model workspace is for the workspace owner (or push-to-client administrator) to set up preferences, system connections, and configurations the way ordinary users must have them in their workspaces. Set up the workspace by using the product user interface and then export those settings by using the Developer for z/OS configuration export wizard.

If group-level control of updates is enabled for the push-to-client servers, then the model workspace is bound to a particular group when you export configurations to the server. Binding a workspace to a group means that the workspace defines configuration and preferences settings for that group only. Therefore, you need to define one model workspace for each push-to-client group defined on the servers.

Procedure

For information about creating a workspace, see Switching workspaces.
For information about group-level control of configurations, see Push-to-client considerations in the Host Configuration Reference.