Getting started with IBM Developer for z/OS push-to-client

How To

Summary

The IBM Developer for z/OS® (IDz) product offers the push-to-client feature for administering and sharing connections, preferences, properties, and configurations so that developers have a consistent and centralized development environment.

You can centralize and automate the creation and distribution of connections, preferences, properties, and configurations so that developers’ workspaces are consistent across the site and settings are downloaded to workspaces automatically when developers connect to a remote system. The push-to-client feature provides the tools that you need to create a centralized and automated development environment.

Objective

This example shows the push to three groups of users:

the default group
the dark group for users who want the dark theme, a database connection, the default UNIX System Services code page IBM-1047, and a property group.
the light group for users who want the default light theme and a host-based project.

The IDz administrator will:

Enable and configure push-to-client on the host
Create and export the required configurations (z/OS connection, database connection, code pages, preferences, themes, property groups, etc.) for the three groups.
Configure one host-based project for one user.

An IDz user connects to the host and receives the available configuration.

Steps

1) Configure the server

1.1) Enable push-to-client

Push-to-client is enabled in the file, pushtoclients.properties.

This example uses SAF groups:

config.enabled=saf
pushtoclient.folder=/sandbox/idz/v150/test/var/pushtoclient

The configuration is stored under pushtoclient.folder.

mkdir /sandbox/idz/v150/test/var/pushtoclient

1.3) Configure groups (optional)

You can push different configurations to different groups of users.

Push-to-client supports a mapping with LDAP or z/OS SAF groups.

If you do not configure groups, then there is only one configuration for all users.

The configuration is stored directly under pushtoclient.folder.

Under the pushtoclient.folder, create a subdirectory named "grouping".

cd /sandbox/idz/v150/test/var/pushtoclient/grouping/
mkdir grouping
mkdir grouping/dark
mkdir grouping/light

Enable XFACILIT class in rse.env:

# use XFACILIT to support more than 39 characters
_RSE_FEK_SAF_CLASS=XFACILIT

Define the push-to-client groups dark and light as RACF groups IDZDARK and IDZLIGHT on the z/OS system named MVS011:

RDEFINE XFACILIT (FEK.PTC.CONFIG.ENABLED.MVS011.DARK) UACC(NONE)
PERMIT FEK.PTC.CONFIG.ENABLED.MVS011.DARK CLASS(XFACILIT) ID(IDZDARK) ACCESS(READ)
RDEFINE XFACILIT (FEK.PTC.CONFIG.ENABLED.MVS011.LIGHT) UACC(NONE)
PERMIT FEK.PTC.CONFIG.ENABLED.MVS011.LIGHT CLASS(XFACILIT) ID(IDZLIGHT) ACCESS(READ)
SETROPTS RACLIST(XFACILIT) REFRESH

Users, who are not part of groups dark or light, receive the default configuration.

Start the RSE started task.

2) Configuring a client workspace

2.1) Configure the default workspace

Start IBM Explorer for z/OS or IBM Developer for z/OS client in a new workspace like

C:\mydata\workspaces\idz1504.default

2.2) Configure the dark workspace

Start IBM Explorer for z/OS or IBM Developer for z/OS client in a new workspace like

C:\mydata\workspaces\idz1504.dark

Configure it with the Dark theme, database connection, remote connection, property group, and any other required settings.

2.3) Configure the light workspace

Start IBM Explorer for z/OS or IBM Developer for z/OS client in a new workspace like

C:\mydata\workspaces\idz1504.light

3) Export the client workspace configurations

3.1) Export the dark workspace

Start IBM Explorer for z/OS or IBM Developer for z/OS client with the dark workspace

C:\mydata\workspaces\idz1504.dark

Connect to the host.

Then select menu:

File > Export > IBM z/OS Explorer > Configuration Files

Export all configurations to group "Dark"

Click Finish

Click OK

Configuration is stored on the host:

3.2) Export the default and light workspaces

Repeat the same steps with:

the default workspace and export it to the "Default" group.

the light theme workspace and export it to the "light" group.

4) Configuring host-based projects (optional)

Make sure the directories (r-x permission) and files (r-- permission) are accessible to the users who need these projects.

To push the following project to user ID=USER1:

Create the following directories and files:

4.1) USER1/project1.hbpin

<PROJECT-INSTANCE>
<WSED-VERSION>15.0.1.0</WSED-VERSION>
<PROJECT>
 <PROJECT-NAME>oneProject1ForMe</PROJECT-NAME>
 <PROJECT-DEF-PATH>projectdef/project1</PROJECT-DEF-PATH>
</PROJECT>
</PROJECT-INSTANCE>

4.2) projectdef/project1.hbppd

<PROJECT-STRUCTURE>
  <WSED-VERSION>15.0.1.0</WSED-VERSION>
  <PROJECT>
    <PROJECT-NAME>oneProject1</PROJECT-NAME>
    <PROJECT-TYPE>zos-project</PROJECT-TYPE>
    <SUBPROJECT-LIST>
      <SUBPROJECT>
        <SUBPROJECT-FULL-PATH>subprojectdef/oneSubproject1</SUBPROJECT-FULL-PATH>
      </SUBPROJECT>
    </SUBPROJECT-LIST>
  </PROJECT>
</PROJECT-STRUCTURE>

4.3) subprojectdef/oneSubproject1.hbpsd

<SUBPROJECT-STRUCTURE>
  <WSED-VERSION>15.0.1.0</WSED-VERSION>
  <SUBPROJECT>
    <SUBPROJECT-NAME>oneSubproject1</SUBPROJECT-NAME>
    <SUBPROJECT-NATURE-LIST>
      <SUBPROJECT-NATURE>com.ibm.ftt.projects.zos.zosnature</SUBPROJECT-NATURE>
    </SUBPROJECT-NATURE-LIST>
    <SUBPROJECT-PROPERTIES-LOCATION>cobolBuild</SUBPROJECT-PROPERTIES-LOCATION>
    <SUBPROJECT-TYPE>zos-subproject</SUBPROJECT-TYPE>
    <FOLDER-LIST>
      <FOLDER>
        <FOLDER-NAME>DEMO.SRC.COBOL</FOLDER-NAME>
        <FOLDER-TYPE>pds</FOLDER-TYPE>
        <FOLDER-STATE>
          <STATE-IS-OFFLINE>false</STATE-IS-OFFLINE>
          <PHYSICAL-FOLDER>
           <FOLDER-NAME>DEMO.SRC.COBOL</FOLDER-NAME>
            <FOLDER-PHYSICAL-PATH>DEMO.SRC.COBOL</FOLDER-PHYSICAL-PATH>
            <FOLDER-TYPE>pds</FOLDER-TYPE>
          </PHYSICAL-FOLDER>
        </FOLDER-STATE>
      </FOLDER>
    </FOLDER-LIST>
    <FILE-LIST>
      <FILE>
        <FILE-NAME>DBCNTBLD.jcl</FILE-NAME>
        <FILE-EXTENSION>jcl</FILE-EXTENSION>
        <FILE-NAME-NO-EXTENSION>DBCNTBLD</FILE-NAME-NO-EXTENSION>
        <FILE-TYPE>pds-member</FILE-TYPE>
        <FILE-STATE>
          <STATE-IS-OFFLINE>false</STATE-IS-OFFLINE>
          <PHYSICAL-FILE>
            <FILE-NAME>DBCNTBLD.jcl</FILE-NAME>
            <FILE-PHYSICAL-PATH>DEMO.SRC.JCL/DBCNTBLD.jcl</FILE-PHYSICAL-PATH>
            <FILE-TYPE>pds-member</FILE-TYPE>
          </PHYSICAL-FILE>
        </FILE-STATE>
      </FILE>
    </FILE-LIST>
  </SUBPROJECT>
</SUBPROJECT-STRUCTURE>

5) Importing the configuration

A user can now connect to the host and receive the configuration.

If the user is a member of multiple groups, then, he can choose which configuration to receive:

For the dark theme to take effect, the user has to restart his IDz client.

Whether a user can reject the push or part of it depends on parameter reject.config.updates set to true or false in the configuration in file pushtoclients.properties.

If set to false, then the user sees the configuration as disabled and cannot select it.

Related Information

Configuring the server: pushtoclient.properties

Configuring the server: SAF groups

Configuring host-based projects

Exporting push-to-client configuration files

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSTRMM","label":"IBM Developer for z\/OS"},"ARM Category":[{"code":"a8m0z00000009MSAAY","label":"IDz Family-\u003EPush to Client"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Product Synonym

IDz

Was this topic helpful?

Document Information

Modified date:
06 May 2022

UID

ibm16565325

Tips

Getting started with IBM Developer for z/OS push-to-client

How To

Summary

Objective

Steps

Related Information

Document Location

Product Synonym

Was this topic helpful?

Document Information

UID

Share your feedback

Need support?