IBM Explorer For Z - OS - Client Configuration Guide

IBM Explorer for z/OS IBM
Client Configuration Guide

Version 3 Release 0
SC27-8435-01
IBM Explorer for z/OS IBM
Client Configuration Guide

Version 3 Release 0
SC27-8435-01
Note
Before using this information, be sure to read the general information under Notices on page 57.
Second edition (September, 2016)

This edition applies to IBM Explorer for z/OS Version 3.0.1 (program number 5655-EX1) and to all subsequent
releases and modifications until otherwise indicated in new editions.
Order publications by phone or fax. IBM Software Manufacturing Solutions takes publication orders between 8:30
a.m. and 7:00 p.m. eastern standard time (EST). The phone number is (800) 879-2755. The fax number is (800)
445-9269. Faxes should be sent Attn: Publications, 3rd floor.
You can also order publications through your IBM representative or the IBM branch office serving your locality.
Publications are not stocked at the address below.
IBM welcomes your comments. You can send your comments by mail to the following address:
IBM Corporation
Attn: Information Development Department 53NA
Building 501 P.O. Box 12195
Research Triangle Park NC 27709-2195
USA
You can fax your comments to: 1-800-227-5088 (US and Canada)
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
Copyright IBM Corporation 2016.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . v Setting preferences for client certificate
authentication . . . . . . . . . . . . 35
About this document . . . . . . . . vii Setting preferences for configuration updates . . 37
Setting preferences for MVS Files subsystems . . 37
Who should read this book . . . . . . . . . vii
Setting preferences for Remote z/OS Search . . 39
Tracing . . . . . . . . . . . . . . . 40
Chapter 1. Client configuration overview 1 z/OS Solutions preferences . . . . . . . . 41
| Chapter 2. Value Unit client licensing Chapter 6. Configuring non-RSE

| considerations . . . . . . . . . . . . 3 system connections . . . . . . . . . 43
Configuring a z/OS FTP system connection . . . 43
Chapter 3. Planning a push-to-client Configuring a proxy server . . . . . . . . . 45
environment . . . . . . . . . . . . . 5 Configuring a z/OSMF system connection . . . . 46
Defining connection credentials. . . . . . . . 47
Chapter 4. Distribution of updates by Connecting to a system that is already defined . . 48
Connecting to a system from the Host
using push-to-client . . . . . . . . . 7 Connections view . . . . . . . . . . . 48
Distributing product updates . . . . . . . . . 9 Connecting to a system by using Signon. . . . 49
Updating the installation configuration file . . . 10 Connecting to a system from the connection
Updating the key mapping file . . . . . . . 13 status bar . . . . . . . . . . . . . . 49
Properties in pushtoclient.properties that affect Connecting automatically at startup . . . . . . 50
product updates . . . . . . . . . . . . 14 Using shared connections. . . . . . . . . . 51
How reject.product.updates affects Updating a system connection . . . . . . . . 52
installedVersion and forcedUpgradeVersion . . 14 Exporting connections . . . . . . . . . . . 53
Creating and distributing configuration files . . . 15 | Removing a default setting from a category or
Creating a master workspace for push-to-client connection. . . . . . . . . . . . . . . 54
configuration . . . . . . . . . . . . . 16 Deleting a system connection . . . . . . . . 55
Defining connections, configuration files, and Disconnecting from a system . . . . . . . . 55
preferences for push-to-client configuration . . . 17
Exporting push-to-client configuration files . . . 27
Resetting workspace configuration files . . . . 29
Notices . . . . . . . . . . . . . . 57
Key mapping file . . . . . . . . . . . 31
Copyright license . . . . . . . . . . 61
Chapter 5. Configuring individual
workbench settings . . . . . . . . . 33 Trademark acknowledgments . . . . . 63
Updating workspace configurations and preferences 33
Setting preferences for z/OS tools . . . . . . . 35 Index . . . . . . . . . . . . . . . 65
Copyright IBM Corp. 2016 iii

iv IBM Explorer for z/OS: Client Configuration Guide
Tables
1. Relationship between installedVersion and 3. Global configuration files . . . . . . . . 18
reject.product.updates . . . . . . . . 15 4. System configuration files . . . . . . . . 19
2. Relationship between forcedUpgradeVersion 5. Examples of wildcard patterns in data set
and reject.product.updates . . . . . . . 15 mappings . . . . . . . . . . . . . 25
Copyright IBM Corp. 2016 v

vi IBM Explorer for z/OS: Client Configuration Guide
About this document
This document discusses the configuration of IBM Explorer for z/OS. It includes
instructions on how to configure push-to-client, how to configure individual
workbench settings and how to configure non-RSE system connections.
The following names are used in this manual:

v IBM Explorer for z/OS is called z/OS Explorer.
v Remote System Explorer is called RSE.
v z/OS UNIX System Services is called z/OS UNIX.
v IBM Developer for z Systems (previously known as Rational Developer for z Systems)
is called IDz.
This document is part of a set of documents that describe the installation and
configuration of z/OS Explorer client. For the installation of z/OS Explorer client,
see IBM Explorer for z/OS Client Installation Guide (SC27-8434).
Who should read this book

This document is intended for programmers who are configuring IBM Explorer for
z/OS client Version 3.0.
It describes how to configure push-to-client, individual workbench settings, and

non-RSE system connections.
Copyright IBM Corp. 2016 vii

viii IBM Explorer for z/OS: Client Configuration Guide
Chapter 1. Client configuration overview
System administrators can configure system and global settings and distribute
these settings throughout the development organization. Individual developers can
configure the local workbench client.
Configuring and distributing system and global settings

v Chapter 3, Planning a push-to-client environment, on page 5
v Chapter 4, Distribution of updates by using push-to-client, on page 7
v Distributing product updates on page 9
v Creating and distributing configuration files on page 15
v Exporting push-to-client configuration files on page 27
Configuring individual workbench settings1

v Updating workspace configurations and preferences on page 33
v Setting preferences for z/OS tools on page 35
1. For IDz users, bidirectional languages and enabling firewall are also supported. For more information, search for Supporting
bidirectional languages and Enabling firewall support in IDz KC.
Copyright IBM Corp. 2016 1

2 IBM Explorer for z/OS: Client Configuration Guide
|
| Chapter 2. Value Unit client licensing considerations

| z/OS Explorer client enables Value Unit (VU) client licensing for licensed products
| that are installed with z/OS Explorer version 3.0.1 and later.
| z/OS Explorer VU generates a Universally Unique Identifier (UUID) to support

| licensed clients that are installed with z/OS Explorer. When VU licensed client
| images are centrally created and distributed to multiple client machines or machine
| images, a new UUID needs to be generated on each machine or machine image.
| The UUID is required to maintain the correct licensed client count. To generate a
| UUID for each client image distributed in this manner, specify the
| -DUUID.reset=true option in the eclipse.ini file. After a new UUID is generated
| in the client, remove the -DUUID.reset=true option in the eclipse.ini file.

Chapter 3. Planning a push-to-client environment
The IBM Explorer for z/OS 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 take either of two approaches to creating a development environment with
the IBM Explorer for z/OS product:
v You can allow a decentralized environment in which developers create their own
connections to remote systems; set preferences for their workspaces; and manage
other aspects of the environment.
v 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.
By using the push-to-client feature, you can distribute the following configuration
files:
v Global configuration files2:
Eclipse preferences
Remote system connections
Installation configuration
v System configuration files3
z/OS file system mappings
In a push-to-client environment, these configuration files are stored on a remote

system. When a workspace connects to the remote system, the configuration files
are downloaded to the workspace. In this way, you can define a set of Eclipse
preferences, for example, that is automatically downloaded when a connection is
made. If you update the configurations between connections, developers are
prompted to update their workspaces when they connect.
In a decentralized environment, developers still have the opportunity to share

configurations by exporting them from one workspace and importing them into
another workspace.
For more information about the push-to-client feature and about migrating
configurations from one workspace to another, see the related topics.
Related concepts:
2. For IDz users, global configuration files also include the settings of Database connections, Software Analyzer Configurations,
Menu Manager files, and Snippets. For more information about theses settings, search for Defining connections, configuration files,
and preferences for push-to-client configuration in IDz KC.
3. For IDz users, system configuration files also include the settings of Property groups, Host-based projects, Remote index locations
and Default values. For more information about these settings, search for Defining connections, configuration files, and preferences for
push-to-client configuration in IDz KC.

Chapter 4, Distribution of updates by using push-to-client, on page 7
You can configure IBM Explorer for z/OS to automatically distribute product
updates and updates to configuration files, preference settings, and remote system
connections when client workstations connect to a remote system. This feature is
called push-to-client. By using it, you can store workspace configurations in a
central location and push them to client workstations so that your developers have
a consistent workspace environment.

Chapter 4. Distribution of updates by using push-to-client
Push-to-client overview
Implementing a push-to-client environment involves several tasks: some on the

z/OS system and some on a client workstation. The following is an overview of
how to implement a push-to-client environment. It defines some of the terms and
resources that are used in this environment. The details for implementing
push-to-client are described in subtopics.
1. Configure push-to-client on z/OS.
Each remote system from which you intend to distribute product updates and
configurations must be set up to support push-to-client.
a. One z/OS system must be defined as the primary system. The primary
system is the controlling system in a push-to-client environment. Only one
z/OS system can be defined as primary. The primary system stores global
configuration files, which apply to all systems in the push-to-client
environment, and system configuration files, which apply only to the
primary system itself. The global configurations are product updates,
Eclipse preferences, and remote system connections.
b. Other z/OS systems can be enabled for push-to-client as non-primary
systems. Non-primary systems define only system configurations, which
apply only to the non-primary system itself. System configurations are file
mappings.
The starting point for configuring push-to-client on a z/OS system is a root file
that is called pushtoclient.properties, which is in the /etc/zexpl/ directory
on the z/OS system. This file contains entries that specify configuration
parameters, such as:
v Whether the function is enabled for product updates: indicated by setting
product.enabled=true.
v Whether the function is enabled for configuration updates: indicated by
setting config.enabled=true.
v Whether the current system is the primary system, that is, the system that
controls the push-to-client feature: indicated by specifying
primary.system=true|false.
v Where to find the main configuration file, keymapping.xml: indicated by
setting pushtoclient.folder=/var/zexpl/pushtoclient, the default location.
The key mapping file contains pointers to a set of files that contain the
application-related settings. These pointers are created from a IBM Explorer
for z/OS client as part of the configuration file export process, described in
step 3 on page 8.
v Whether group-level control of product and configuration updates is
enabled: indicated by setting an access control attribute for certain
configuration parameters in the pushtoclient.properties file. This feature
allows a system administrator to create client groups and provide product

and configuration updates that are specific to each group. For example, to
enable group control of product updates through RACF, specify
product.enabled=saf. To enable group control of product updates through
LDAP, specify product.enabled=ldap.
For information about preparing z/OS systems for push-to-client configuration,
see (Optional) pushtoclient.properties, the host-based client control in the Host
Configuration Guide (SC27-8437).
For information about setting up LDAP access groups and SAF-based access
groups, see these topics:
v Push-to-client developer groups in the Host Configuration Reference Guide
(SC27-8438)
v Push-to-client considerations in the Host Configuration Reference Guide
(SC27-8438)
2. Configure a master workspace with settings that you want to push out to other
workspaces when they connect to the z/OS system.
After the remote system is set up, you can begin configuring the IBM Explorer
for z/OS settings you want to push out to the rest of the organization. For
most settings, such as Eclipse preferences, remote system connections, and file
system mappings, this task is accomplished by updating the settings locally on
a client. Some settings, such as product updates, must be configured manually
on the z/OS system.
If group-level control of product and configuration updates is enabled for the
push-to-client servers, then the master 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 master workspace for each
push-to-client group defined on the servers.
3. Export the workspace settings to the z/OS system by using the IBM Explorer
for z/OS configuration export wizard.
The export wizard uploads the local configuration files (Eclipse preferences,
remote system connections, and file system mappings) from the master
workspace to the z/OS system. Only users who have authority to write files to
the folder that contains the key mapping file on the remote system can export
settings. After the settings are exported, users who connect to the z/OS system
are prompted to update their workspaces with these settings.
For information about configuring and exporting the IBM Explorer for z/OS
settings you want to push out to client workstations, see the remaining topics that
are linked to in the following section.
Creating and distributing updates
The IBM Explorer for z/OS push-to-client function can distribute the following
types of updates:4
v Product installation updates. IBM Explorer for z/OS provides tools for system
administrators to create product installation updates and prompt client
workstations to install the updates when they connect to a remote system. This
type of update supports only modification-level updates. You can use
push-to-client to update clients from version 2.1 to version 2.1.1, for example,
4. For more information about the push-to-client function, search for Solving problems with push-to-client configuration and
implementation in IDz KC.

but not from version 2.1 to version 3.0 and not from version 3.0 to version 3.1.
For more information about distributing product updates, see Distributing
product updates.
v Product configuration updates. IBM Explorer for z/OS provides tools for system
administrators to define remote system connections, define configuration files,
and set client workstation preferences from a central location. These connection
definitions, configuration files, and preferences can be distributed to individual
client workstations automatically when they connect to a remote system. For
more information about distributing configuration updates, see Creating and
distributing configuration files on page 15.
Distributing product updates

The IBM Explorer for z/OS push-to-client feature provides tools for system
workstations to install the updates when they connect to a remote system.
Before you begin

This type of update supports only modification-level updates. You can use
push-to-client to update clients from version 3.1 to version 3.1.1, for example, but
not from version 3.1 to version 4.0 and not from version 4.0 to version 4.1.
You can distribute product updates after the IBM Explorer for z/OS servers are
installed and configured on a remote system. To complete the push-to-client tasks,
the IBM Explorer for z/OS pushtoclient.properties file must be configured to
distribute product updates. For information about push-to-client configuration, see
(Optional) pushtoclient.properties, the host-based client control in the Host
Configuration Guide (SC27-8437).
While you complete these tasks, you might need to create or update the following
files. These procedures explain how to update the files.
v An IBM Installation Manager response file. For instructions for creating a
response file, see Silent installation in the Client Installation Guide (SC27-8434).
v An IBM Installation Manager product activation kit file. If the product update
requires a product activation kit, you can place the kit in a network location and
refer to the location from the response file.
v A key mapping file. This file defines the location of other files, such as installation
response files and configuration files, that are distributed automatically to client
workstations. The key mapping file is called keymapping.xml. Its default location
on the z/OS system is /var/zexpl/pushtoclient.
v An installation configuration file. This file defines the product offering IDs, a range
of IBM Explorer for z/OS versions, and the name of the response file that
installs the product update. The push-to-client feature scans the installation
configuration file for an applicable product offering ID and installed version. If
found, it starts Installation Manager with the specified response file. The
installation configuration file is called installconfig.xml and is in the path
indicated by the <fileId>com.ibm.ftt.resources.zos.install.configuration</
fileId> tag of the key mapping file.
v A push-to-client properties file, called pushtoclient.properties. This file defines
the location of the key mapping file. The default location of the
pushtoclient.properties file on the z/OS system is /etc/zexpl/. For more
information about the pushtoclient.properties file, see (Optional)
pushtoclient.properties, the host-based client control.
Chapter 4. Distribution of updates by using push-to-client 9

About this task
When a client workstation connects to a remote system that is configured to

distribute product updates, the push-to-client feature compares the client product
version with a range of versions that are defined in the installation configuration
file. If the installed version is in this range, the IBM Explorer for z/OS workbench
shuts down and starts the IBM Installation Manager product by using a response
file that is downloaded from the remote system.
Procedure
To create and distribute product updates:

1. Create an IBM Installation Manager response file for the product installation
that you want to distribute. For instructions for creating a response file, see
Silent installation.
Important: If user authentication is required to access the code repository for

the update, then users must save their user IDs and passwords in IBM
Installation Manager.
2. Create or update the installation configuration file to indicate the range of
product versions that triggers an update and the response file for installing the
update. For instructions for creating or updating the installation configuration
file, see Updating the installation configuration file.
3. Update the key mapping file to point to the installation configuration file and
the response file. For instructions for updating the key mapping file, see
Updating the key mapping file on page 13.
Related concepts:
Related tasks:
Installing client updates

Related reference:
How reject.product.updates affects installedVersion and
forcedUpgradeVersion on page 14
The behavior that is triggered by the installedVersion and forcedUpgradeVersion
attributes is affected by the reject.product.updates parameter of the
pushtoclient.properties file.
Properties in pushtoclient.properties that affect product updates on page 14
Several properties that are specified in the pushtoclient.properties file work
together to determine how product updates are delivered by the push-to-client
feature.
Updating the installation configuration file

Create or update the installation configuration file.

About this task
This type of update supports only modification-level updates. You can use
push-to-client to update clients from version 3.1 to version 3.1.1, for example, but
not from version 3.1 to version 4.0 and not from version 4.0 to version 4.1.
Procedure
1. Create or edit the installconfig.xml file. If this file exists, you can add entries
for the installation to this file. If the file does not exist, you can copy the
sample installation configuration file that is shown at the end of this procedure,
modify it for your installation, and save it to the z/OS server. The installation
configuration file is a UTF-8 encoded XML file.
2. Include the <installedOffering> tag to identify the offering ID of the product
you want to distribute updates for. The <installedOffering> tag has the
following syntax:
<installedOffering id="installedOfferingID">
You can specify an offering ID for any product that is installed in the same
package group as the IBM Explorer for z/OS product. The offering ID is stored
in the <offering> tag of the response file. The following is an example of the
<offering> tag:
<offering id=com.ibm.zos.explorer.v30 version=3.0.0.20151002_1738 profile=IBM Software Delivery Platform features=listOfInstalledFeatures/>
Specify the value in the id attribute of the <offering> tag for the id attribute in
<installedOffering id="installedOfferingID">.
3. Include an <install> tag with one of the following attributes to specify a range
of product versions to be updated and the name of the response file to install
the product update. Only one of the following attributes can be defined for
each installed offering ID in the installation configuration file. If both attributes
are specified, the installedVersion attribute takes precedence over the
forcedUpgradeVersion attribute.
Important: The behavior that is triggered by the installedVersion and

forcedUpgradeVersion attributes is further defined by the
reject.product.updates parameter of the pushtoclient.properties file. For
more information about how these attributes are affected by the
reject.product.updates parameter, see the related topics.
v An installedVersion attribute. If the version currently installed on a client
workstation is within the installedVersion range, a confirmation window
opens and the client can accept or refuse the update. When the update is
accepted, Installation Manager starts with the response file specified in the
responseFile attribute to update the client.
<install installedVersion="[minimumVersionInclusive, maximumVersionInclusive] | (minimumVersionExclusive, maximumVersionExclusive)" responsefile="fileName">
v A forcedUpgradeVersion attribute. If the version currently installed on a

client workstation is within the forcedUpgradeVersion range, a confirmation
window opens, but the client cannot reject the update. If the version is
outside of the range, the client is not prompted with a confirmation window
and cannot be updated.
<install forcedUpgradeVersion="[minimumVersionInclusive,maximumVersionInclusive] | (minimumVersionExclusive, maximumVersionExclusive)" responsefile="fileName">
You can specify the value for installedVersion and forcedUpgradeVersion as

an inclusive, exclusive, or mixed range:
v To specify a range of product versions that includes the minimum and
maximum versions, use square brackets. For example,

installedVersion="[3.0.1, 3.0.2]" prompts an installation update for
product versions 3.0.1, 3.0.2, and all versions between this range.
v To specify a range of product versions that excludes the minimum and
maximum versions, use parentheses. For example,
installedVersion="(3.0.1, 3.0.2)" prompts an installation update for
product versions greater than 3.0.1 but less than 3.0.2.
v You can mix brackets and parentheses to specify a range that includes one
end of the range but excludes the other:
For example, installedVersion="(3.0.1, 3.0.2]" prompts an installation
update for product versions greater than 3.0.1 but less than or equal to
3.0.2.
For example, installedVersion="[3.0.1, 3.0.2)" prompts an installation
update for product versions greater than or equal to 3.0.1 but less than
3.0.2.
For either of these attributes, the version numbers must include at least the
major version number. It can include minor version, micro version, and
qualifier: major[.minor[.micro[.qualifier]]] The following examples show valid
version numbers for the installedVersion and forcedUpgradeVersion
attributes:
3
3.0
3.0.0
3.0.0.201510140202
4. Place the installation configuration file and the response file on the z/OS server
and point to that location in the key mapping file.
Example
The installation configuration file is a UTF-8 encoded XML file. It contains one or
more sets of <installedOffering> tags that define a target product offering ID and
one or more pairs of installed version ranges and response file names. The
push-to-client feature processes the following sample installation configuration file
as follows:
v Scans the file until it finds a product offering ID that matches the ID of any
product that is installed in the same package group as the currently running
IBM Explorer for z/OS version. For example, if a client is running the IBM
Explorer for z/OS product in the same package group as the Rational Team
Concert product, then the matching offering ID can be either
com.ibm.team.install.rtc.client.eclipse or
com.ibm.zos.explorer.v30
v If the current product version of the matching offering ID falls within the range
that is provided in any of the pairs of <installedVersion> and <responseFile>
attributes, Installation Manager starts by using the response file. If the Rational
Team Concert version, for example, is greater than or equal to 3.0.0 and less than
3.0.1, Installation Manager starts by using the response file
update_rtc_from_600_to_601.xml.
<?xml version="1.0" encoding="UTF-8"?>
<installConfig>
<installedOffering id="com.ibm.zos.explorer.v30">
<install
installedVersion="[3.0.1, 3.0.2)"
responseFile="update_zxpl_from_301_to_302.xml">
</install>
<install

responseFile="update_zxpl_from_310_to_311.xml">
</install>
</installedOffering>
<installedOffering id="com.ibm.team.install.rtc.client.eclipse">
<install
responseFile="update_rtc_from_600_to_601.xml">
</install>
</installedOffering>
</installConfig>
Updating the key mapping file

You can update the key mapping file by using the export wizard or by editing it
manually.
About this task
For instructions for using the export wizard, see Exporting push-to-client
configuration files on page 27.
Procedure
To update the key mapping file by editing it manually, do these steps:

1. The Export operation creates a default keymapping.xml file and uploads it to the
location indicated by the pushtoclient.folder property of the
pushtoclient.properties file. The default keymapping.xml file includes entries
for the product update. You can add entries for the product update to this file.
The key mapping file is a UTF-8 encoded XML file.
2. Include one set of <location> tags for each installation configuration file and
each response file you want to point to.
3. Specify the following values for the tags:
<fileId>
Specify com.ibm.ftt.resources.zos.install.configuration for the
installation configuration file and
com.ibm.ftt.resources.zos.install.response for the response file.
<containerPath>
Specify the location of the installation configuration file or response file
on the z/OS server.
<fileMask>
Specify the name of the installation configuration file or response file.
<encoding>
Specify the encoding of the installation configuration file or response
file.
4. Save the key mapping file to the location indicated by the pushtoclient.folder
property of the pushtoclient.properties file.
Example
The key mapping file is a UTF-8 encoded XML file that stores the names, locations,
and character encodings of configuration files that are used in a IBM Explorer for
z/OS push-to-client configuration environment. In the following sample key
mapping file, the administrator placed installconfig.xml in the
/var/zexpl/pushtoclient/install directory and the response files in the
/var/zexpl/pushtoclient/install/responsefiles directory of the z/OS server.

<configuration-system>
<location-list>
<location>
<fileId>com.ibm.ftt.resources.zos.install.configuration</fileId>
<containerPath>/var/zexpl/pushtoclient/install</containerPath>
<fileMask>installconfig.xml</fileMask>
<encoding>UTF-8</encoding>
</location>
<location>
<fileId>com.ibm.ftt.resources.zos.install.response</fileId>
<containerPath>/var/zexpl/pushtoclient/install/responsefiles</containerPath>
<fileMask>update_*.xml</fileMask>
</location>
</location-list>
</configuration-system>
Properties in pushtoclient.properties that affect product

updates
Several properties that are specified in the pushtoclient.properties file work
together to determine how product updates are delivered by the push-to-client
feature.
product.enabled
Indicates whether push-to-client is used to deliver product updates. Valid
values are TRUE, FALSE, SAF, and LDAP:
v TRUE - product updates are enabled for all users.
v FALSE - product updates are disabled.
v SAF - product updates are enabled based on permission to security
profiles.
v LDAP - product updates are enabled based on membership in LDAP
groups.
For information about setting up LDAP access groups and SAF-based
access groups, see these topics:
v Push-to-client developer groups in the Host Configuration Reference Guide
(SC27-8438)
v Push-to-client considerations in the Host Configuration Reference Guide
(SC27-8438)
reject.product.updates
Indicates whether clients are allowed to reject product updates that are
delivered by the push-to-client feature. The default is FALSE.
accept.product.license
Indicates whether the product license is automatically accepted during
updates that are initiated by push-to-client. If this property is set to FALSE,
push-to-client does not attempt to distribute any product updates. If it is
true, push-to-client attempts to deliver product updates and adds the
-acceptLicense argument to the Installation Manager invocation. The
default is FALSE.
How reject.product.updates affects installedVersion and

forcedUpgradeVersion
The behavior that is triggered by the installedVersion and forcedUpgradeVersion
attributes is affected by the reject.product.updates parameter of the
pushtoclient.properties file.
Relationship between installedVersion and
The following table shows the relationship between the installedVersion attribute
of the installation configuration file and the reject.product.updates parameter of
the pushtoclient.properties file.
Table 1. Relationship between installedVersion and reject.product.updates
reject.product.updates=false reject.product.updates=true
If the client version is out of The client is not prompted The client is not prompted
range of installedVersion and cannot install the and cannot install the
product update. product update.
If the client version is in The client is prompted but The client is prompted and
range of installedVersion cannot reject the updates. can reject the updates.
Relationship between forcedUpgradeVersion and

The following table shows the relationship between the forcedUpgradeVersion

attribute of the installation configuration file and the reject.product.updates
parameter of the pushtoclient.properties file.
Table 2. Relationship between forcedUpgradeVersion and reject.product.updates
reject.product.updates=false reject.product.updates=true
If the client is out of range of The client is not prompted The client is not prompted
forcedUpgradeVersion and not updated to the and not updated to the
specified version. specified version.
If the client is in range of The client is prompted and The client is prompted and
forcedUpgradeVersion cannot reject the updates. cannot reject the updates.
Related tasks:
Distributing product updates on page 9
The IBM Explorer for z/OS push-to-client feature provides tools for system
workstations to install the updates when they connect to a remote system.
Creating and distributing configuration files

The push-to-client feature provides tools for system administrators to define
remote system connections, define configuration files, and set client workstation
preferences from a central location. These connection definitions, configuration
files, and preferences can be distributed to individual client workstations
automatically when they connect to a remote system. Product updates can also be
pushed to client workstations when they connect to a remote system.
Before you begin
To create and distribute remote connection definitions, configuration files, and

preferences from a central location, the server must be configured to enable
push-to-client updates. For information about configuring push-to-client updates,
see (Optional) pushtoclient.properties, the host-based client control.

About this task
When a user connects to the primary remote system or to another remote system
for which system configuration files are defined, the configuration files that are
stored on that system are compared to the configuration files on the workstation. If
updates are available, users are prompted to install them.
files:
Eclipse preferences
Procedure
To create and distribute configuration files, do these steps. Each of these steps links
to more information about completing the step.
1. Create a workspace that serves as the master workspace for the configurations
and preferences to be distributed.
2. From the master workspace, create connections to the primary remote system
from which you intend to distribute global and system configurations and to
each remote system from which you intend to distribute system configurations.
3. Configure remote system connections, configuration files, and preferences in the
master workspace.
4. Export the configuration files that are to be distributed to other client
workspaces.
Related concepts:
Creating a master workspace for push-to-client configuration

A master workspace is a IBM Explorer for z/OS workspace from which you create
the remote system connections, configuration files, and preference settings to be
distributed to other client workstations.
6. For IDz users, system configuration files also include the settings of Property groups, Host-based projects, Remote index locations
and Default values. For more information about these settings, search for Defining connections, configuration files, and preferences for
push-to-client configuration in IDz KC.

About this task
Creating a master workspace for push-to-client configurations is no different from

creating any other IBM Explorer 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 master
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 IBM Explorer for z/OS
configuration export wizard.

push-to-client servers, then the master 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 master workspace for each
push-to-client group defined on the servers.
Procedure
v For information about creating a workspace, see Switching workspaces.
v For information about group-level control of configurations, see these topics:
Push-to-client developer groups
Push-to-client considerations
Defining connections, configuration files, and preferences for

push-to-client configuration
To set up connections, configuration files, and preferences for distribution in a
push-to-client environment, define global and system configuration files.
Global configuration files
Global configuration files are managed on the primary remote system. The primary
remote system is a z/OS system that is defined during host installation and
configuration as the controlling system for push-to-client configuration.

Table 3. Global configuration files. The global configuration files include these settings.
File Type Description More Information
Eclipse Preferences These configuration files are Eclipse Preferences
exported from the settings in
z/OS Preferences
the Window > Preferences
user interface of a workspace
that is connected to the
primary remote system. The
push-to-client feature uses
the base Eclipse export
mechanism for preferences,
which saves only changes to
default values. Eclipse also
exports different preferences
to various discrete .pref
files. The result is that the
push-to-client feature exports
and distributes only those
Eclipse preference files that
contain nondefault values.
Remote System Connections These configuration files are Creating a connection to a
exported from the Remote z/OS system on page 19
Systems view of a workspace
that is connected to the
primary remote system. They
include all remote system
connections that are defined
in this view.
Installation Configuration These configuration files are Distributing product
Files created manually. The define updates on page 9
product updates to be
installed on a client
workstation when it connects
to a remote system.
System configuration files
System configuration files are managed on the primary remote system and on other
remote systems to which users can connect.

Table 4. System configuration files. The system configuration files include the following
setting.
File Type Description More Information
z/OS File System Mapping These configuration files are Mapping data sets and
Configuration Files exported from the z/OS File partitioned data set
System Mapping view of a members on page 23
workspace that is connected
to the primary remote
system. They include all
that are defined for each
remote system that is defined
in the Remote Systems view.
The push-to-client feature
can export the following
types of z/OS file system
mapping configuration files:
v MVS Files - System
Mapping files are defined
for a remote system.
v MVS Files - Resource
Mapping files are defined
for specific data sets on a
remote system.
Creating a connection to a z/OS system

Before you can connect to a remote system from the IBM Explorer for z/OS client,
you must define a connection for it and specify connection properties.
About this task
Restriction: Define only one connection to a particular remote system in each

workspace. If you define multiple connections to a single remote system, and your
site uses the push-to-client function to distribute updates to remote system
connections, then all connections to the remote system are updated. The IBM
Explorer for z/OS product does not support different configurations of the same
remote system in a single workspace.
Procedure
1. In the Remote Systems view, expand New Connection and double-click z/OS.
2. In the New Connection window, select a profile name from the list.
Tip: If you are creating a connection for the first time, you are prompted to
create a profile before you can create the new connection. After you create the
connection, you can share this profile to allow other users to have this
connection in their Remote Systems view.
3. Enter the following values in the fields on this window.
Host name
The TCP/IP address of the remote system.
Connection name
The short name to call the system. For example, MYSYSTEM.
Description
A description of the connection.

Verify host name
Select this check box to verify that the host name is valid before you
connect.
4. To define the connection with default values for the MVS Files, z/OS UNIX
Files, and z/OS UNIX Shells subsystems, click Finish. To set properties for
these subsystems, click Next. The wizard opens a properties window for each
subsystem. These pages display the properties of the underlying services that
are used by each subsystem. For more information about the properties you
can set for a subsystem, see the related topics.
Results
The Remote Systems view displays the short name of the new connection with five
nodes under the connection name:
v z/OS UNIX Files is the z/OS UNIX file subsystem. This node contains two
folders: My home and Root. You can create more z/OS UNIX file folders by
adding new filters to this node.
v z/OS UNIX Shells is a command subsystem. When you open a z/OS UNIX
command shell, its name is displayed under this node.
v MVS Files is the MVS file subsystem. This node contains three folders: My Data
Sets displays MVS files that match the filter userid.* in which userid is the user
ID with which you connected to the remote system. You can create more MVS
file folders by adding filters to this node. You can change the sort order of data
sets by using the MVS Files preference page. Retrieved Data Sets displays data
set names searched for and added by using the Retrieve Data Sets action or by
allocating a data set. My Search Queries displays search queries that you ran
and saved in the Remote z/OS Search view.
v TSO Commands is a command subsystem. When you open a TSO command
shell, its name is displayed under this node.
v JES is the JES subsystem. This node contains two folders: My Jobs displays jobs
that are submitted under the user ID with which you connected to the remote
system. You can create more job folders by adding new filters to this node.
Retrieved Jobs displays jobs searched for and added by using the Retrieve Job
action.
What to do next
Connecting to a remote system. After you connect to the remote system, you can
control the contents that are displayed under JES, MVS Files, and z/OS UNIX
Files by defining filters for these subsystems. You can add search queries to the
MVS Files folder by running and saving remote z/OS searches. For instructions,
see the related topics.
Related information:
Quick task: Creating a connection to a remote system
Remote-to-local file mapping

When you define a remote system, you map (associate) the lowest level qualifier in
each MVS data set name to a file name extension for the related workstation file.

IBM Explorer for z/OS includes a set of defined remote-to-local file mappings. The
**COBOL file mapping, for example, maps MVS files with a low-level qualifier
COBOL to workstation files with the .cbl file name extension.7
Mapping
A mapping indicates how IBM Explorer for z/OS processes file transfers between
z/OS and the workstation; specifically, the mapping indicates whether file transfers
are based on an exchange of text (in which case ASCII/EBCDIC conversions occur)
or on an exchange of binary data. A mapping also helps you to know, at a glance,
the general purpose of a particular file.
If you use the same low-level qualifier for several data sets, the same mappings
affect file transfers for each of those data sets. Given the mappings that are
included in IBM Explorer for z/OS, for example, you can transfer members of the
partitioned data sets USER01.COBOL and USER01.TEST.COBOL to and from
workstation-based files that have the extension .cbl.8
You can see remote-to-local file mappings in the z/OS File System Mapping view
of the RSE perspective perspective. The following screen capture shows this view.
You can customize these mappings to match the naming conventions on your
remote system either through the z/OS File System Mapping view or on the
Mapping page of the Properties window. For more information about customizing
these mappings, see Mapping data sets and partitioned data set members on
page 23. For more information about the properties of file mappings, see the
remaining sections of this topic.
7. For IDz users, you can define an alternative logical NOT symbol in a file mapping definition. For more information, search for
Specifying an alternative logical NOT symbol in IDz KC.
8. In the workbench, a preference that is related to the z Systems LPEX Editor causes workstation-based files of a particular type to
be treated in a particular way. In accordance with this preference, for example, a file of type .cbl is presented with the syntax
highlighting that is appropriate to a COBOL source file. However, when the editor processes a z/OS-based data set, the mapping
of a qualifier (like COBOL) to a file name extension (like .cbl) determines how the data set is processed.

Workstation file extension
The type of a file is indicated by its workstation file extension. In the mappings
that are shown in the screen capture, a .cbl extension, for example, is considered
to be a COBOL source file. Each file can have only one file type. JCL with
embedded COBOL source, for example, is not supported. The default workstation
file extension for a new mapping is undefined.
Transfer mode
The transfer mode can be either text, indicating that a conversion between ASCII
and EBCDIC occurs, or binary. The default transfer mode for a new mapping is
text.
Code page
Each file can have only one code page, but you can specify a group of files as
having the same code page. When you specify code pages, specify both a local and

a host code page and keep them consistent. The default host and local code pages
for a new mapping are inherited from the system properties of the remote and
local file systems.
For a list of supported host code pages, see Supported host code pages on page
27. The availability of local code pages is based on the text file encodings that are
supported by the Eclipse text editor. Be sure to specify code pages to be consistent
with the compiler settings of your files.
Priority
If a file matches more than one file mapping, the mapping with the highest
priority is the one that applies. In the following example, a file named
MYUSERID.SOURCE.COBOL matches both of these file mapping definitions. Because the
**COBOL mapping has the higher priority, its properties are applied during a file
transfer between the remote and local systems. It is transferred to the workstation
with these file transfer properties: .cbl file extension, text transfer mode, inherited
workstation code page.
Workstation
Mapping File Transfer Host Code Local Code
Criterion Extension Mode Page Page Priority
**COBOL .cbl default (text) default default 1
(inherited) (inherited)
**COBOL* default binary default default 2
(undefined) (inherited) (inherited)
Related concepts:
File encoding, code page conversion, and inheritance on page 25
When you copy a file between a remote system and the workstation, the file is
converted to a code page appropriate to its destination. File code pages are
inherited from the system or folder that contains them.
Related tasks:
Mapping data sets and partitioned data set members
A data set mapping associates the lowest level qualifier in each MVS data set to a
file name extension that is used for the related workstation-based file. One
mapping, for example, associates the z/OS-based qualifier COBOL with the
workstation-based file extension .cbl.
Mapping data sets and partitioned data set members:
About this task
The IBM Explorer for z/OS product provides a set of default mappings, but you
can create more mappings.
Procedure
To add a data set mapping:

1. Open the z/OS File System Mapping view. This view displays all remote z/OS
systems and the data set mappings that are defined on them. When there are
multiple definitions for a data set or member name pattern, the order in which
a mapping is displayed in the table determines its priority: the higher it is on
the list, the higher the priority.
2. From the System list, select the remote system that you want to modify
mappings for.
3. To add a data set mapping, right-click the table and select Add Data Set
Mapping. The Add Data Set Mapping window opens.
4. To add a member mapping, right-click a data set mapping in the z/OS File
System Mapping view and select Add Member Mapping. The Add Member
Mapping window opens.
5. Specify a string in the Mapping criterion field. Data sets and members with
names that match this string are included in the mapping.
v Use ** as a wildcard for matching one or more data set name segments or
qualifiers:
**COBOL matches <any high-level qualifier>.<any middle qualifier>.COBOL.
These sample data set names match this mapping:
- USER.COBOL
- USER.A.COBOL
- USER.A.B.C.COBOL
- USER.A.B.C.MYCOBOL
**ERROR** matches <any high-level qualifier>.ERROR.<any low-level
qualifier>. These sample data set names match this mapping:
- USER.ERROR.TEST
- USER.A.B.MYERROR.ABC
- USER.A.B.MYERROR2.ABC
v Use * as a wildcard for matching within a data set name segment or
qualifier. For example, USER**COB* matches the following names:
USER.A.COB
USER.A.B.COBOL
USER.A.B.ACOBCOPY
v You can also use a period as a delimiter in a mapping:
USER.*.TEST matches USER.A.TEST, but not USER.A.B.TEST
USER.**TEST matches USER.A.TEST, USER.A.B.TEST, and
USER.A.B.CTEST.
For more examples of wildcard patterns and matching data set names, see
Table 5 on page 25.
6. In the Workstation file extension group, click Default or click Other and type
the file name extension that you want to associate with the data set matching
string.
7. Use the remaining fields to choose a file transfer type and local and remote
code pages. For more information about other file mapping options, see the
related topics.
8. Click OK. The new mapping is displayed in the table. Member mappings are
added as children of the data set mapping that you selected before you click
Add Member Mapping. You can sort this table by any of the headings that are
shown in the view (such as Mapping Criterion, Workstation File Extension, and
Transfer Mode). To sort the table, click a table heading.

9. Optional: You can override these system-wide mappings by defining mappings
for specific data sets or members:
a. Right-click the data set or member in the Remote Systems view and click
Properties.
b. Click Mapping in the list on the left. The Mapping pane opens on the right.
This pane is similar to the Add Data Set Mapping window.
c. Leave the option to inherit values selected for each of the values you want
to cascade from a higher level.
Example
The following table provides further examples of wildcard patterns and the strings
that match and do not match them.
Table 5. Examples of wildcard patterns in data set mappings. Wildcard patterns are listed
across the top of the table, and sample data set names are listed down the first column of
the table. The remaining cells indicate whether the sample data set name and the wildcard
pattern match.
Wildcard Patterns
Data set names KENYA**COBOL KENYA**COBOL* KENYA.**COBOL KENYA.**.COBOL KENYA.*COBOL KENYA.*.COBOL KENYA.*.*.COBOL
KENYA.COBOL Match Match Match Do not match Match Do not match Do not match
KENYA.A.COBOL Match Match Match Match Do not match Match Do not match
KENYA.A.B.COBOL Match Match Match Match Do not match Do not match Match
KENYA.XYCOBOL Match Match Match Do not match Match Do not match Do not match
KENYA.A.XYCOBOL Match Match Match Do not match Do not match Do not match Do not match
KENYA.XCOBOLY Do not match Match Do not match Do not match Do not match Do not match Do not match
Related concepts:
Remote-to-local file mapping on page 20
File encoding, code page conversion, and inheritance
Related tasks:
Creating a connection to a z/OS system on page 19
Before you can connect to a remote system from the IBM Explorer for z/OS client,
you must define a connection for it and specify connection properties.
Related reference:
Supported host code pages on page 27
These host code pages are supported. The default value is IBM-037 (mixed-case
English).
File encoding, code page conversion, and inheritance:

File system default encoding
You can determine the default file encoding on a local or remote file system by
setting a property in the Remote Systems view. Two options are available:
Default from remote system
The default file encoding is inherited from the local or remote system.
Other You can select the default file encoding from a list of available choices.
IBM Explorer for z/OS uses the International Components for Unicode
(ICU) for file encoding. You can learn more about ICU at International
Components for Unicode.
To choose a default file encoding for a local or remote system:

1. If you are connected to the remote system, disconnect. You can change the
default file encoding for a remote system only when you are disconnected.
2. In the Remote Systems view, select a local or remote system.
3. Right-click and select Properties. The Properties window opens.
4. In the categories list, click Host.
5. Choose one of the file encoding options, and then click OK.
Code page conversion
IBM Explorer for z/OS uses remote-to-local file mapping to determine how file
encodings are converted between local and remote code pages during file transfers.
For more information about remote-to-local file mapping, see Remote-to-local file
mapping on page 20.
Code page inheritance
When you transfer a file between a local and remote file system, the file inherits
the code page setting from the destination container. This inheritance sometimes
results in a file encoding that is different from or incompatible with the original
file encoding. To ensure correct file encoding during a file transfer, make sure that
the code page for the destination container is set correctly.
To set the code page for a file or container:

1. Select the file or container. To set the code page for the MVS Files subsystem of
a z/OS connection, for example, select MVS Files.
2. Right-click and select Properties.
3. From the category list, select Code Pages.
4. Select host and local code pages from the list.
Related concepts:
Remote-to-local file mapping on page 20
Related tasks:

Mapping data sets and partitioned data set members on page 23
Supported host code pages:
These host code pages are supported. The default value is IBM-037 (mixed-case
English).
IBM-037 IBM-273 IBM-274 IBM-277 IBM-278

UTF-8 UTF-16 UTF16BE UTF-16LE
Exporting push-to-client configuration files

After you configure remote system connections, configuration files, and preferences
for push-to-client configurations, you can export them to the remote system for
distribution to client workspaces.
Before you begin
To export system or global configuration settings to the remote system, you must
have write access to the push-to-client configuration files on the remote system.
File permissions can be set for three types of users: owner, group, and other. File
permissions for the push-to-client directory on the remote system are set by using
the file.permission directive in the pushtoclient.properties file. The default
setting allows read and write for owner (the user ID who created a file) and group,
and read for other. For more information about push-to-client file permissions and
configuring push-to-client support on z/OS, see (Optional) pushtoclient.properties,
the host-based client control.
About this task
Exporting configurations for push-to-client distribution generates configuration

files and transfers them to the remote system. After the files are exported, they are
automatically downloaded to client workstations when they connect to the remote
system.
files:

Eclipse preferences
Note: Some configuration files, such as installation configuration files, are created
manually on the remote system and not exported from the workstation.
Procedure
To export push-to-client configuration files:
1. Switch to the master workspace as described in Creating a master workspace
for push-to-client configuration on page 16.
push-to-client servers, then the master 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 master
workspace for each push-to-client group defined on the servers.
2. Connect to the remote system to which you want to export configuration files:
a. Select the remote system in the Remote Systems view.
b. Click Connect on the menu.
Remember: The push-to-client function supports only one primary system.

Before you attempt to export configuration files, verify that you are connected
to only one primary system. If you are exporting to a primary system that is
different from the primary system to which you last exported configuration
files (for example, if your site uses one primary system for testing and another
for production), a window prompts you to verify that you are connected to
the correct primary system.
3. From the workspace menu bar, click File > Export. The Export window opens.
4. In the Export window, click + to expand z/OS Explorer.
5. Select Configuration Files.
6. Click Next.
v If the remote system is the primary system, the Global Configuration Files
window opens.
v If the remote system is not the primary system, the System Configuration
Files window opens.
Each of these windows contains two sections:
v Global configuration or System configuration lists configuration files that
can be exported from the workstation to the remote system.
v Key mapping update lists configuration files that are created on the remote
system. You cannot export these files from the workstation.
If the product is configured to support configuration groups, this window
might also include a Configuration group list. Configuration groups are
12. For IDz users, system configuration files also include the settings of Property groups, Host-based projects, Remote index
locations and Default values. For more information about these settings, search for Defining connections, configuration files, and
preferences for push-to-client configuration in IDz KC.

controlled on the remote system. For more information about configuration
groups, see Push-to-client considerations.
7. If the push-to-client environment is configured to support configuration
groups, select the configuration group to which you want to export the
configuration files. If the master workspace is not bound to a group, you can
select a group from this list. If the workspace is bound to a group, the group
name is displayed in this field and you cannot select a different group. Some
configurations, such as Eclipse Preferences, offer you the opportunity to select
specific configuration files to export.
8. Optional: To see the list of configuration files, expand the configuration.
9. Optional: To display the default locations and names of the configuration files
on the remote system, select Show export properties. The following export
properties are displayed:
v Export Path: The location on the remote system to which the configuration
file is to be exported.
v File Mask: The file name pattern for the configuration file, which is useful
when many configuration files are saved in the same container.
v Encoding: The encoding of the configuration file on the remote system.
10. Select the check box next to the configuration files you want to export and
click Next or Finish. The configuration files are uploaded to the remote
system. Some configurations might offer you the opportunity to select specific
configuration files to export. If you selected a configuration that provides this
option, a window that lists available configuration files opens.
11. Optional: Select the files that you want to export and click OK.
Related concepts:
Related reference:
Key mapping file on page 31
The key mapping file is generated when you export configuration files. It stores
the names, locations, and character encodings of configuration files that are used in
a push-to-client configuration environment.
Resetting workspace configuration files

You can reset the workspace configuration files that you downloaded from the
remote system by clearing the cached files.
About this task

Remote configuration files are stored in your workspace in a folder named
workspacePath\RemoteConfigurationFiles. This folder contains the following
subfolders:
v A folder that is named global, which contains global configurations. Global
configurations are defined on the primary push-to-client server.
v One folder for each remote system to which you connect and that is enabled for
push-to-client.

Clear Cached Files on the Configuration Files preference page deletes some of the
contents of the RemoteConfigurationFiles folder.
You might consider clearing the cached files in the following circumstances:
v If you are the push-to-client administrator, and you discover that you set
preferences or configured features in a way that you did not intend to export to
the remote system or group with which the workspace is associated.
If you discover that you exported configurations that you did not intend to
export, then you can clear the cached files, reconfigure the workspace, and then
export the configurations again. Clear Cached Files provides a way to start over
with workspace configurations.
v If you downloaded configurations that you did not intend to download when
you connected to a remote system.
When you connect to a remote system, the push-to-client feature prompts you
with a list of recent configuration updates. From this list, you can select the
specific configurations that you want to download. If you select a configuration
by mistake, you can clear the cached files, disconnect from the remote system,
and then connect again to choose the configurations you want to download.
Important: If you changed configurations that are downloaded from a remote

system and you clear the cached files, then any local changes you made to the
downloaded configurations are overwritten the next time you connect to the
remote system.
Configurations that you create locally are saved in a folder that is called client
and are not deleted when you clear the cached files.
Procedure
To reset downloaded configuration files:

1. Click Window > Preferences and select Remote Systems > Configuration
Files.
2. Click Clear Cached Files. The next time that you connect to any of the remote
systems that are enabled for push-to-client, you are prompted to accept
configuration changes.
Results
Clearing the cached files affects your workspace in the following ways:
v Eclipse preferences: No change. The preferences that you set are left as they
were even after the cache is cleared. The Eclipse preferences are managed by the
Open RSE base program, which has its own repository for the preferences.
Clearing the cached files deletes only the local files in the
RemoteConfigurationFiles folder.
v Remote connections: No change. The remote connections are managed by the
Open RSE base program, which has its own repository for the remote
connections.
v Mappings: The imported mappings are deleted.
Related concepts:

Related tasks:
Setting preferences for configuration updates on page 37
Use the Configuration Files preference page to set options for automatically
updating your workspace when you connect to a remote system.
Updating workspace configurations and preferences on page 33
The server can be configured to automatically download configuration and
preference updates to the client. When updates are available, the client is prompted
to install the updates when you connect to a remote system.
Key mapping file

The key mapping file is generated when you export configuration files. It stores
the names, locations, and character encodings of configuration files that are used in
a push-to-client configuration environment.
The key mapping file is a UTF-8 encoded XML file that is named keymapping.xml.
Its default location on the z/OS system is /var/zexpl/pushtoclient/
keymapping.xml. This location is defined in the pushtoclient.folder property of
the /etc/zexpl/pushtoclient.properties file. For more information about the
pushtoclient.properties file, see the IBM Explorer for z/OS Host Configuration
Guide (SC27-8437).
The key mapping file contains the following tags for each configuration file13:
<fileId>
Identifies the configuration file. This tag can contain the following values,
described here by using the label that is displayed on the Export window
for each file:
v com.ibm.ftt.resources.zos.install.configuration Install
Configuration Files - Version Configuration
v com.ibm.ftt.resources.zos.install.response Install Configuration Files
- Response Files
v com.ibm.ftt.configurations.RSEConnections Remote System
Connections
v com.ibm.ftt.configurations.EclipsePreferences Eclipse Preferences
v com.ibm.ftt.resources.zos.mapping.specificmapping z/OS File System
Mapping Configuration Files - MVS Files - Resource Mapping
v com.ibm.ftt.resources.zos.mapping.genericmapping z/OS File System
Mapping Configuration Files - MVS Files - System Mapping
Note: Installation, Remote System Connections, and Eclipse Preferences

configuration files are stored only on the primary system.
<containerPath>
Specifies the location of the configuration file on the z/OS system. The
default container path for each configuration file is either the folder that
13. For IDz users, search for Key mapping file in IDz KC.

contains the key mapping file or a subfolder. Subfolders are used to reduce
the number of files in the parent folder and to group similar sets of files,
such as Eclipse preference files.
<fileMask>
Specifies the name of the configuration file. Some export operations, such
as Eclipse Preferences and RSE Connections, generate multiple files. For
these operations, the value for the file mask uses wildcard characters such
as *.xml and *.zip.
<encoding>
Specifies the character encoding of the configuration file.
Sample key mapping file
The following sample key mapping file points to configuration files stored in the
/var/zexpl/pushtoclient path of the z/OS system.
<configuration-system>
<location-list>
<location>
<fileId>com.ibm.ftt.resources.zos.install.configuration</fileId>
<containerPath>/var/zexpl/pushtoclient/install</containerPath>
<fileMask>installconfig.xml</fileMask>
</location>
<location>
<fileId>com.ibm.ftt.resources.zos.install.response</fileId>
<containerPath>/var/zexpl/pushtoclient/install/responsefiles</containerPath>
<fileMask>*.xml</fileMask>
</location>
<location>
<fileId>com.ibm.ftt.configurations.EclipsePreferences</fileId>
<containerPath>/var/zexpl/pushtoclient/preferences</containerPath>
<fileMask>*.pref</fileMask>
<encoding>IBM-1047</encoding>
</location>
<location>
<fileId>com.ibm.ftt.configurations.RSEConnections</fileId>
<containerPath>/var/zexpl/pushtoclient/connections</containerPath>
<fileMask>*.zip</fileMask>
</location>
<location>
<fileId>com.ibm.ftt.resources.zos.mapping.genericmapping</fileId>
<containerPath>/var/zexpl/pushtoclient/mappings</containerPath>
<fileMask>zossys.xml</fileMask>
</location>
<location>
<fileId>com.ibm.ftt.resources.zos.mapping.specificmapping</fileId>
<fileMask>zoshlq_*.xml</fileMask>
</location>
<location>
<fileId>com.ibm.ftt.resources.zos.mapping.bct</fileId>
<fileMask>*.bct</fileMask>
</location>
</location-list>
</configuration-system>

Chapter 5. Configuring individual workbench settings
Configure tools for your workspace.
Updating workspace configurations and preferences

The server can be configured to automatically download configuration and
preference updates to the client. When updates are available, the client is prompted
to install the updates when you connect to a remote system.
About this task
If updates for IBM Explorer for z/OS configurations and preferences are available
when you connect to a remote system, the Updates Available window opens with
one of the following messages:
v CRRZI0520I Updates to your IBM Explorer for z/OS configuration and
preferences are available. Select the configuration files to update and
click OK to accept them.
v CRRZI0531I IBM Explorer for z/OS has been configured to require users to
install all available configuration and preference updates. Click OK to
update your configuration files and preferences.
If the server is configured to support product and configuration groups, this

message might also include a Configuration group list. Configuration groups and
the ability to select or refuse updates are controlled by parameters in the
pushtoclient.properties file on the remote system. For more information about
this file, see (Optional) pushtoclient.properties, the host-based client control. This
window lists the updates that are available for installation. The following
configurations and preferences can be enabled for automatic update:
v Eclipse settings. These configuration files update the settings in the Window >
Preferences user interface. For general information about Eclipse workbench
preferences, see Preferences. For specific information about IBM Explorer for
z/OS preferences, see Setting preferences for z/OS tools on page 35.
Attention: Code templates are among the Eclipse preferences that can be
exported to a remote system and distributed to clients by using the
push-to-client feature. Before you create or edit code templates, be sure that you
know which templates are local (created on your workstation) and which are
remote (delivered to your workstation by using push-to-client). If you edit a
remote template but do not give it a unique name, your edits might be
overwritten when you connect to the remote system.
For more information about how the push-to-client feature merges local and
remote templates, see Code templates in a push-to-client environment in IDz KC.
v Remote system connections. These configuration files update the remote system
connections that are defined in the Remote Systems view. For information about
remote system connections, see Creating a connection to a z/OS system on
page 19.
v z/OS file system mappings. These configuration files update the z/OS file
system mappings that are defined for the remote system. For information about

file system mappings, see Mapping data sets and partitioned data set
members on page 23. The following z/OS file system mapping configuration
files is available14:
System mappings are defined for a remote system.
Procedure
To install the configuration updates:

1. If you are prompted to choose a Configuration group, select one from the list.
The choice that you make sets the configuration group for the workspace. After
you choose a configuration group, you cannot change it. On subsequent remote
system connections, you can download configurations from the default group
or from the group you select the first time you connect to the remote system. If
you must access and download configurations from another configuration
group, you must connect by using a different workspace. For more information
about creating a workspace, see Switching workspaces.
2. If you are required to install all updates, click OK. The configuration files and
preferences are updated.
3. If you are allowed to select or refuse updates, do these steps:
a. Select the check box next to the configuration files you want to update. To
update all files that are shown, click Select All. Some configurations, such
as Eclipse Preferences, offer you the opportunity to select specific
configuration files to export. To see the list of configuration files, expand the
configuration.
b. Optional: To prevent future notifications of configuration and preference
updates, select the check box next to Do not notify me of future updates. If
you select this option, you can reverse this choice and begin receiving
updates again by setting an option on the Configuration Files preference
page. For more information about this preference page, see the related
topics.
c. Click OK. The selected configuration files and preferences are updated.
Results
Unless you select the Do not notify me of future updates option, the
push-to-client feature handles future updates according to the preference setting on
the Configuration Files preference page:
v Notify me of all updates: When this option is set, you are prompted to update
any available configurations and preferences each time you connect to the
remote system. If you do not select all of the updates or if any new updates
become available, you are prompted to install them.
v Notify me of updates that I have not rejected: When this option is set, you are
not prompted to update previously rejected configurations the next time you
connect, even if they are updated on the server.
v Do not notify me of updates: When this option is set, you are never notified of
updates. Selecting the Do not notify me of future updates option on the
Updates Available window sets this preference option.
14. For IDz users, the configuration files of menu Manager menus and actions is also available. For more information, search for
Creating custom pop-up menus in IDz KC.

Example
As an example, assume that the push-to-client feature prompts you to update the
following configurations when you connect to the remote system.
v Eclipse Preferences
v z/OS File System Mapping Configuration Files
If you choose to update the Eclipse Preferences, but not the z/OS File System
Mapping Configuration Files, then the next time you connect, the Updates
Available window prompts you according to the Configuration Files preference:
Configuration Files preference Updates Available actions

Notify me of all updates The window opens and prompts you to
install z/OS File System Mapping
Configuration Files (because you did not
update them previously) and any other
newly updated configurations.
Notify me of updates that I have not The window opens if any new updates exist,
rejected except for z/OS File System Mapping
Configuration Files. The window does not
prompt update for z/OS File System
Mapping Configuration Files.
Do not notify me of updates The window does not open.
Related tasks:
Setting preferences for configuration updates on page 37
Setting preferences for z/OS tools

Access IBM Explorer for z/OS preferences by clicking Window > Preferences.
About this task
The following preference categories directly affect z/OS application development.

Select the links in this list for more information about these preference settings.15
v Client Certificates
v Remote Systems > z/OS
MVS Files
v Tracing on page 40
v z/OS Solutions
Setting preferences for client certificate authentication

Use the Client Certificates preference page to specify preferences for client
certificate authentication.
15. For IDz users, you can set preference for CICS Debug Configuration and DB2 and IMS Debug Configuration. For more
information, search for Setting preferences for z/OS tools in IDz KC.
Chapter 5. Configuring individual workbench settings 35

About this task
With client certificate authentication, you can authenticate with remote systems by
using a security device such as an integrated circuit card (like a smart card). IBM
Explorer for z/OS relies on the Java Cryptographic Service Provider (Java CSP)
for the retrieval of the certificates. The certificates are used solely for client
certificate authentication. All updates to the certificates are outside the scope of
IBM Explorer for z/OS.
Procedure
To set up client certificates on your workstation:

1. Specify values for these fields:
Java Cryptography Extension (JCE) provider
Specify the name of the security provider as provided by the vendor
that supplies the cryptography software that is used to access the
certificates.
Keystore type
Specify the keystore type that the Java CSP uses for retrieving the
certificates that are stored in the Microsoft Cryptography API
(MS-CAPI) keystore. Use the name of the keystore that the security
provider gives.
hostIdMappings object identifier (OID)
Specify the hostIdMappings OID. Do not change the value that is
specified on the preferences page from the default value of
1.3.18.0.2.18.1 unless instructed otherwise by the systems administrator.
The hostIdMappings extension (Object Identifier 1 3 18 0 2 18 1) is an
IBM extension that is also available for public use. The security
software on the remote system (such as RACF) automatically maps a
valid certificate to the RACF user ID that is provided in the extension.
Changing this value might cause the certificate authentication to fail.
2. To ensure that each keystore has a unique alias, select the Ensure unique
aliases check box.
Note: Select this option only when you are using the Sun MSCAPI Java
Cryptography Extension (JCE) Provider and only when the aliases are not
unique. Do not select this option for other JCE providers.
3. To filter certificates by key usage, select one or more of these check boxes that
are listed under Certificate key usage:
__ Digital signature
__ Non-repudiation
__ Key encipherment
__ Data encipherment
__ Key agreement
__ Certificate signing
__ CRL Signing
__ Encipher only
__ Decipher only
For information about the types of key usage, see Key usage extensions and
extended key usage.

Tip: You can filter by key usage alone or combined with filtering by
hostIdMappings OID.
Related information:
Key usage extensions and extended key usage
Setting preferences for configuration updates

About this task

Restriction: The IBM Explorer for z/OS system administrator has the ability to
prevent users from rejecting configuration updates. If the remote system has been
configured to prevent you from rejecting updates, the options on this page are not
available and all configurations and preferences must be updated when you
connect to the remote system.
Procedure
1. Click Window > Preferences.
2. Click + to expand Remote Systems.
3. Click Configuration Files.
4. Select one of the following options:
v Notify me of all updates Each time you connect to the remote system you
are notified of all available updates. Notifications continue until you install
the updates.
v Notify me of updates that I have not rejected Each time you connect to the
remote system, you are notified of available updates for the configurations
and preferences you have updated previously. If, on previous connections,
you have rejected any updates, you are no longer notified of them.
v Do not notify me of updates IBM Explorer for z/OS never notifies you that
configuration and preference updates are available.
v Clear Cached Files: Click this button to reset the configuration settings for
the current workspace. This action is helpful if the configuration files become
corrupted or out-of-sync with the remote system. Clearing the cache allows
new settings to be imported from the remote system to the current
workspace.
Clear Cached Files is intended primarily for push-to-client administrators to
use when they are preparing a push-to-client environment. It can also be
used by non-administrators to resynchronize downloaded configurations
with the remote system or group from which you downloaded them. For
more information about resetting workspace configuration files, see the
related links.
5. Click OK to save the settings.
Related tasks:
Resetting workspace configuration files on page 29
You can reset the workspace configuration files that you downloaded from the
remote system by clearing the cached files.
Setting preferences for MVS Files subsystems

Use the MVS Files page to set preferences for the MVS Files subsystem in the
Remote Systems view.

Procedure
To set preferences for MVS Files:

1. To open the MVS Files preference page, click Window > Preferences, then
expand Remote Systems > z/OS and click MVS Files.
2. Use the MVS Files page to set the following preferences16:
Large Partitioned Data Set The options in this area determine how large
partitioned data sets are handled in the Remote Systems view.17
v Show warning message on expansion: Select this check box to display a
warning message when expanding large partitioned data sets, which can take
a long time.
v Maximum number of members expanded without warning: If you select
the Show warning message on expansion option, use this field to set the
number of members to allow before the warning is displayed. The default
value is 5000.
v Maximum results for Find Member: Specify the maximum number of search
results to return with the Find Member action. The default value is 1000
members.
Generation Data Set Label: There are two options for displaying generation
data sets:
v Absolute generation and version numbers (Relative generation number):
Shows the absolute generation and version numbers followed by the relative
generation number, such as G0005V00(-1).
v Relative generation number (Absolute generation and version numbers):
Shows the relative generation number followed by the absolute generation
and version number, such as -1(G0005V00).
Sort Order for Data Sets: The options in this area determine the order of data
sets in the Remote Systems view 18:
v By type: Select this option to list partitioned data sets followed by sequential
data sets.
v By name: Select this option to list all data sets in alphabetical order,
regardless of data set type.
Default expansion page size for filters and data sets: Specify the number of
data sets or data set members to show in the Remote Systems view when you
expand a filter or partitioned data set. All other entries remain hidden until
you bring them into view. You can override this number for a particular filter
or data set. The default value is 50.
Show warning message on deleting alias: Select this check box to display a
warning message when you delete a data set alias.
Process member aliases on module copy: Select this check box to enable the
primary load module and all its aliases to be copied together.
16. For IDz users, you can also set preferences for Show missing property group warning message on opening files. For more
information, search for Setting preferences for MVS Files subsystems in IDz KC.
17. For IDz users, you can also see the following options in this area:
v Show warning message on adding to subproject: Select this check box to display a warning message when adding large
partitioned data sets to a subproject.
v Maximum number of members added to subproject without warning: If you select the Show warning message on adding
to subproject option, use this field to set the number of members to allow before the warning is displayed. The default value
is 50.
18. For IDz users, this area also determines the order of data sets in the z/OS Projects view.

Show warning when number of returned data sets exceeds limit: Select this
check box to display a warning message when the number of results that MVS
data set filters return exceeds limit.
Show members with non-standard name: Select this check box to enable the
Remote Systems view to display members with lowercase names or names
containing nonstandard character sets. This option is disabled by default.
Enable editing of files with control codes: Select this check box to allow MVS
text files that contain control codes to be opened in edit mode. When this check
box is selected, UTF-8 is used as the default local code page mapping for new
connections. Connections that exist are not affected.
Default action for opening MVS files: Choose the action to be executed when
you double-click a sequential data set name or partitioned data set member
name in the Remote Systems view:
v Open - Opens the file for editing in the default editor. This setting is the
default.
v View - Opens the file for editing, without locking the file, in the default
editor.
v Browse - Opens the file in read-only mode in the default editor.
For more information about each of these actions, see the related topics.
Restriction: Dragging a file from the Remote Systems view to the editor opens
the file in edit mode in the default editor that is associated with the file
extension. Setting the Default action for opening MVS Files preference does
not change this behavior.
Default action for opening copybooks: Choose the action to be executed when
you double-click a copybook name or choose the Open Declaration action for a
copybook.
Enable logical NOT symbol conversion in COBOL source: Select this check
box to specify an alternative logical NOT symbol for COBOL files. This
preference is disabled by default.
| Lock sequential data sets when in browse mode: Select this check box to
| emulate the ISPF locking behavior for sequential data sets in browse mode.
Setting preferences for Remote z/OS Search

Use the Remote z/OS Search preferences page to set options for remote z/OS
search results.
About this task
The Remote z/OS Search view provides controls that help you work with search
results more efficiently:
v A search operation can return search results incrementally so that you can begin
working with search results before all results are returned. You can specify how
frequently the search results are updated.
v The Remote z/OS Search view can show you a preview of file contents in a
pop-up window. This preview helps you better understand what is in a file
before opening it in an editor. You can specify the timing and size of the
preview window.

Procedure
1. To open the Remote z/OS Search preference page, click Window > Preferences,
then expand the Remote Systems > z/OS section and click Remote z/OS
Search.
2. Specify the following options:
Result update frequency: To specify how frequently search results are updated,
slide the control to a higher setting for more frequent updates or to a lower
setting for less frequent updates. A higher frequency returns a smaller result set
with each update and a lower frequency returns a larger result set with each
update.
Preview contents in Remote z/OS Search view: To enable the preview
window, select the check box. To disable the preview window, clear this check
box. When this check box is selected, the remaining fields in the Search result
preview group are enabled.
Time in miliseconds until preview is activated: To control the timing of the
preview window, type a number in this field. This field controls how quickly
the preview window opens after you place the mouse pointer over a result
string. The higher the number, the slower the response time.
Number of lines before current line and Number of lines after current line:
To control the size of the preview window, select a number in these fields. You
can select a number between 1 and 9.
3. Click OK to save the preference settings.
Tracing
You can set varying tracing levels for specific IBM Explorer for z/OS components.
About this task
During execution, trace entries are produced and placed in the

workspace\.metadata\.trace file. The number of entries and the amount of detail
that is generated is determined by the setting of the tracing level for various tracers.
The tracers are listed on the Tracing preference page. A tracing level is specified for
each tracer, and, if tracing is enabled, the .trace file is populated with entries that
contain a level equal to or less than the specified level. A trace shows the flow of
the execution of a program and can help with troubleshooting and debugging
problems.
Procedure
To set tracing levels for IBM Explorer for z/OS components, do these steps:
1. Click Window > Preferences.
2. In the list of preference pages, click Tracing. The Tracer Name list displays
components for which tracing is available. The default is NONE, which means
that no tracing is done for the component. Other available tracing levels
include the following values:
v FINE - records trace data for basic debugging information such as input and
output date.
v FINER - records trace data such as conversion data and traps that are to be
ignored.
v FINEST - records trace data such as entry and exit data for methods.

3. To include trace entries regardless of their levels, change the tracing level to
FINEST. The volume of data generated is greater, but might provide the
information that is required to solve some problems.
4. Click Restore Defaults after the trace is captured.
z/OS Solutions preferences

Use the z/OS Solutions preference page to set general preferences for z/OS files.19
Purpose
You can set the following preference on this page.20

Show warning message on opening files
Opening large files can cause out-of-memory errors and a forced shutdown
of the workbench. Select this option to check the size of any file that is
being opened (sequential data sets, partitioned data set members, or local
files) and display a warning if it is larger than the specified threshold. This
warning gives you the option to cancel the file open operation or continue
it. This option is enabled by default, and the default threshold is 2500 KB.
To specify a different threshold, enter a value in the Maximum file size to
open without warning (in KB) field.
19. For IDz users, you can also use the z/OS Solutions preference page to set general preferences for z/OS projects and subprojects.
20. For IDz users, you can set more preference on this page. For more information, search for z/OS Solutions preferences in IDz KC.

Chapter 6. Configuring non-RSE system connections
Before you can start to use z/OS Explorer, you must define a connection credential
and create a system connection. You can find additional information about system
connections in this chapter. The example tasks in this chapter illustrate how you
can configure and change your system connections.
Configuring a z/OS FTP system connection

You must have an FTP or z/OSMF connection to use the views in the z/OS
perspective.
Before you begin
You must have at least one connection credential before you can connect to a
system. A credential is a repository for a user ID and password combination. For
more information, see Defining connection credentials.
Note: For z/OS Explorer to successfully obtain the required spool files, the
FTP.DATA configuration file for the server must specify JESINTERFACELEVEL 2.
For more information about the JESINTERFACELEVEL parameter, see z/OS
Communications Server: IP Configuration Reference.
About this task
By default, the z/OS FTP connection initiates a passive FTP mode connection. You
can specify that the connection initiates an active FTP mode connection when you
add or edit a z/OS FTP connection. For example, you might do this if your system
restricts passive FTP mode connections.
Procedure
1. Click Window > Manage Connections from the main menu for the workbench.
The Host Connections view is displayed.
If your connections are preconfigured, the connections are listed under the
categories in the view. If not, the categories are empty. Each z/OS FTP
connection is associated with a credential (but not the z/OSMF connection).
The credential is shown in parentheses after the connection name.
2. In the Connections section, select the z/OS FTP category and click Add.
3. In the Add z/OS FTP Connection window, enter the FTP host name of your
server in the Host name field. As you type, the characters up to the end of the
first qualifier are inserted in the Name field. For example, if you enter
myserver.example.ibm.com in Host name, myserver is displayed in Name.
4. Optional: To specify a different name, type the name that you require in Name.
5. Optional: To use active FTP mode, select the Active Transfer mode check box.
| 6. Optional: Select the local and remote character sets to use during file transfer.
| Use these character sets to override the conversion table defaults of the FTP
| server when transferring untagged files in ASCII transfer mode. When you save
| tagged files, if specified, the local code page overrides the default setting for
| the local encoding. You can also select the file translation table that is located in
| a data set or z/OS UNIX file. For more information about FTP translation
| tables, see SBDATACONN (FTP client and server) statement.

7. Optional: You can choose to associate a credential with the connection now.
Right-click the connection name and hover over Set Credentials to show the
credentials available. Click the credential that you want to use for the
connection.
8. Complete the other fields for your organization.
9. Click Save and Close to save the configuration without connecting or click
Save and Connect to save the configuration and connect immediately. If you
click Save and Connect, the Signon window is displayed, where you must
select an existing credential to use with this connection, or define a new
credential.
Results
The connection and associated credential are displayed in the Host Connections
view.
What to do next
When you connect, z/OS Explorer tries to connect to the system that you
configured.
If the connection is successful, the connection name is displayed in the workbench

window next to a green icon.
If the connection is not successful, the connection name is displayed in workbench

window next to a red icon. An error message is displayed in the workbench status
bar providing a reason for the failure. Check the values in the fields, correct any
errors, and try to connect again.
Related concepts:
Connecting to a system that is already defined on page 48
When you have defined your system connections there are a number of ways in
which you can activate a connection to a system.
Related tasks:
Configuring a z/OSMF system connection on page 46
The z/OS Management Facility (z/OSMF) is a product for z/OS that provides
support for a modern, web-based management console for z/OS, and extends the
functions of the z/OS Explorer. You must have a z/OSMF connection to use the
features of z/OSMF. When you define a z/OSMF system, z/OS Explorer attempts
to create an FTP connection at the same time. z/OS Explorer then chooses the
connection that is most suitable for the task you are performing.
Exporting connections on page 53
You can export one or more connections to an external file to back them up or to
share with other users. If you save the connection file on a shared disk, or upload
it to a web server, users can load the connection details into their z/OS Explorer.
Any changes to the shared connection file are picked up automatically the next
time the user starts z/OS Explorer.
Using shared connections on page 51
As an alternative to defining your own connections, you can share a set of
connections that are stored in a central location. You can load or import the shared
connections into your copy of z/OS Explorer. Sharing connections means that the
connections can be managed centrally, and any changes to the connections file are
picked up automatically the next time z/OS Explorer starts.

Configuring a proxy server
Service updates for the z/OS Explorer are available on a pre-configured download
site on the internet. Your organization might require you to connect to the internet
through a proxy server. You can use the Preferences dialog to define a proxy
server.
Before you begin
Before proceeding, ensure that you have all the details including the address and
port number for your proxy server.
Note: Proxy bypass does not work if you have configured a SOCKS proxy server.
Procedure
1. Use the appropriate method to open the Preferences window:
v Windows or Linux: Click Window > Preferences on the workbench menu
bar.
v OS X: Click IBM Explorer for z/OS > Preferences on the main menu.
2. Expand General and click Network Connections. The Network Connections
pane is displayed in the Preferences window.
3. Select the schema for the proxy type, HTTP, HTTPS, you want to configure and
click Edit.
4. Type the address of the proxy, and the port number, in the dialog. If the proxy
server requires authentication, select the Enable proxy authentication check
box and enter your user name and password. Click OK to close the dialog.
5. Optional: If you have defined a proxy but one or more of the servers you are
connecting to does not use the proxy, you must configure a proxy bypass. Click
Add Host to open the Proxy bypass hosts dialog. Enter the server host name,
for example; mvs23.production.com and click OK. All connections to the
configured server will now go direct and not use the proxy.
6. Click Apply to save the configuration.
7. The Active Provider field indicates whether the proxy is used. Select the
appropriate setting. There are three choices that can be selected:
Native
Any settings that were discovered in the OS are used. Native is the
default setting. When this option is active, no proxy check boxes are
selected.
Manual
Any proxy servers defined in this view are used. When this option is
active, all proxy check boxes are selected.
Direct All connections are opened without using proxy servers. When this
option is active, no proxy check boxes are selected.
8. Click OK to close the dialog.
What to do next
If you selected Manual in the Active Provider field, the next time z/OS Explorer
connects to the internet the connection will go through the proxy server.
Chapter 6. Configuring non-RSE system connections 45

Configuring a z/OSMF system connection
Before you begin
z/OSMF in z/OS Explorer uses the z/OS jobs REST interface. For details of the
RACF authorizations that are required, see the "Required authorizations" section in
the z/OS jobs REST interface in IBM z/OS Management Facility Programming Guide.
You must have at least one connection credential before you can connect to a host
system. A credential is a repository for a user ID and password combination. For
more information, see Defining connection credentials.
Procedure
1. Click Window > Manage Connections from the workbench menu bar. The
Host Connections view is displayed.
If your connections are preconfigured, you see the connections that are listed
under the categories in the view. If not, the categories are empty. In the Host
Connections view, one connection is defined in each category type. Each
connection is associated with a credential, except for the z/OS FTP connection.
The credential is shown in brackets after the connection name.
2. In the Connections section, select the z/OSMF category and click Add. The
Add Connection window opens.
3. In the Host name field, enter the host name of your z/OSMF server. As you
type, the characters up to the end of the first qualifier are inserted in the Name
field. So if your host name is myserver.example.ibm.com then the name would
display as myserver.
4. Enter the port number. As you type, the port number is appended to the Name
field, so the name is displayed as something like myserver:20332.
5. Optional: You can specify a different name by over typing the name in the
Name field.
6. By default the z/OSMF connection also sets up an FTP connection on port 21.
If you previously defined a different FTP connection, select it from the FTP
Connection list.
7. Complete the other fields for your organization, and click OK.
8. Click Save and Close to save the configuration without connecting or click
Save and Connect to save the configuration and connect immediately. If you
click Save and Connect, you are presented with the Signon window, where you
must select an existing credential to use with this connection, or define a new
credential.
Results
The connection and associated credential are displayed in the Host Connections
view.

What to do next
When you connect, the z/OS Explorer tries to connect to the system that you
configured.
If the connection is successful, the connection name is displayed in the workbench

window next to a green icon.
If the connection is not successful, the connection name is displayed in workbench

window next to a red icon. An error message is displayed in the workbench status
bar providing a reason for the failure. Check the values in the fields, correct any
errors, and try to connect again.
Related concepts:
Related tasks:
Configuring a z/OS FTP system connection on page 43
perspective.
Exporting connections on page 53
Defining connection credentials

When you connect to a system, your credentials, that is, your user ID and
password or pass phrase, are sent to the system for authentication. After you
define a credential, you can use it on all systems that share the credential without
reentering the details every time. You must have at least one credential before you
can connect to a system.
Before you begin
Ensure that you have all your system connection details and that you have the
correct level of authorization to connect to your system.
Procedure
1. On the main menu for the workbench, click Window > Manage Connections.
The Host Connections view opens. The available categories in the Host
Connections view depend on the plug-ins that are installed in the z/OS
Explorer.
2. Click Add in the Credentials section to add a new credential. The New
Credentials window opens.

3. Enter your credential details and provide a credential name. The name can be
anything that you like, and is used only to help you distinguish between
different credentials. If you do not type a name, then the default name that is
used is the same as the User ID. Select the Save Password check box to save
the password.
Note: You might have a single user ID, but use different passwords for
different systems. In this case, you can define multiple credentials, each one
having the same user ID but with a different credential name and password or
pass phrase. Alternatively you can choose to define one credential, but not to
save the password or pass phrase, in which case you are required to enter them
when you connect to a system.
4. Click OK to save the credential or Cancel to cancel the process and close the
window without saving the credential.
What to do next
You can click Add in the Connections section of the Host Connections view to
configure a system connection.
Connecting to a system that is already defined

Connecting to a system from the Host Connections view

After you define your system connections, you can activate a connection from the
Host Connections view.
Before you begin
Before you connect to a system, you must have at least one connection configured.
Procedure
1. If the Host Connections view is not open, click Window > Manage
Connections on the main menu for the workbench to open the view.
2. In the Host Connections view, expand the tree in the Connections section and
locate the system that you want to connect to.
For a default connection in a connection category, you can just locate the
connection category. For more information about default connections, see
Connecting automatically at startup on page 50.
3. Either select the system, then click Connect, or right-click the system, then click
Connect on the menu.
To connect to a default connection in a connection category, either select the
connection category, then click Connect, or right-click the connection category,
then click Connect on the menu.
z/OS Explorer attempts to connect to the system you select. If you were
already connected to the system you selected, z/OS Explorer reconnects.
4. Optional: If you did not previously enter your password or pass phrase, use
the dialog to enter it, then click OK.

What to do next
If the connection is successful, the connection name is displayed in the connection

status bar in the lower-right corner of the workbench. For an SSL connection, the
Secure Connection icon is displayed. For a non-SSL connection, the Connected
icon is displayed.
If the connection is not successful, the connection name is displayed in the

connection status bar and the Disconnected icon is displayed. An error message is
displayed in the workbench status bar that provides a reason for the failure.
Correct any errors as indicated and retry the procedure.
Related tasks:
Updating a system connection on page 52
If any system connection settings change, you must update the connection details
in the Host Connections view to reflect the changes.
Connecting to a system by using Signon

When your system connections are defined, you can activate a connection by using
Signon in the Explorer menu.
Before you begin
Before you can connect to a system, you must have at least one connection
configured. The Signon option connects to the system name shown in the
connection status bar, which is in the lower-right corner of the workbench. If the
system name to which you want to connect is not showing in the connection status
bar, select the system name from the list.
Procedure
1. Click File > Signon on the main menu for the workbench. z/OS Explorer
attempts to connect to the system indicated in the connection status bar.
Results
status bar. For an SSL connection, the Secure Connection icon is displayed. For a
non-SSL connection, the Connected icon is displayed.

displayed in the workbench status bar that provides a reason for the failure. Check
the values in the fields, correct any errors in the connection details, and click
Connect to test the corrections.
Connecting to a system from the connection status bar

connection status bar.

Before you begin
Before you connect to a system, you must have at least one connection configured.
The currently selected system name is shown in the connection status bar, which is
in lower-right corner of the workbench.
Procedure
1. Activate the connection in one of the following ways:
v If the system name that you want to connect to is displayed in the
connection status bar, click the icon by the system name.
v If the system name that you want to connect to is not displayed in the
connection status bar, click the arrow by the icon, then click the system that
you require.
z/OS Explorer attempts to connect to the system shown in the connection
status bar.
Results
status bar. For an SSL connection, the Secure Connection icon is displayed. For a
non-SSL connection, the Connected icon is displayed.

displayed in the workbench status bar that provides a reason for the failure. Check
the values in the fields, correct any errors in the connection details, and click
Connect to test the corrections.
Connecting automatically at startup

You can set one connection in each connection category as the default. You can
then connect to the default connection for a category, or use these default
connections for automatic connection when you start z/OS Explorer.
About this task
You can set one or more connections as the default, then set whether to connect
automatically to the default connections when you start z/OS Explorer.
z/OS Explorer has a single connection category of z/OS, which includes two
connection types: z/OS FTP and z/OSMF. You can set one connection in this
category as the default.
When additional plug-ins are installed, the corresponding additional connection

categories are available and you can set one default connection in each connection
category that is shown.
Procedure
Connections from the workbench menu to open the view.
locate the connection you want to set as default.

3. Right-click the connection, then click Set as default connection. Default is
shown in parentheses after the connection name and the credentials, and the
connection name is shown in parentheses after the connection category.
4. Repeat the previous two steps for each additional connection in a different
category that you want to set as default.
5. To connect to the default connections automatically when you start z/OS
Explorer, click the Automatically connect to defaults on startup icon in the
toolbar of the view.
Results
Your change is effective the next time that you start z/OS Explorer.
What to do next
You can stop using a connection automatically at startup in two ways:

v Remove the default setting from the connection.
v Click the Automatically connect to defaults on startup icon to stop automatic
connection to all default connections.
Related tasks:
Connecting to a system from the Host Connections view on page 48
Host Connections view.
| Removing a default setting from a category or connection on page 54
If a connection is set as default, you can remove that default setting so that it is
not used for automatic connection when you start z/OS Explorer.
perspective.
Using shared connections

About this task
Typically, a system administrator uses z/OS Explorer to define shared connections

and export them to a central location where other users can access them. The
exported file must have a file type of .pref, for example, connections.pref. Any
user with access to the file location can load or import the connections in their
copy of z/OS Explorer.

When you load connections, a link is created to an external connections file, and
the connections are shown in the Host Connections view. You can view the
connections but you cannot change them. If the shared connections file changes,
those changes are reflected next time z/OS Explorer starts. If the shared
connections file is deleted or moved, the connections are lost from z/OS Explorer.
When you import connections, the connections are copied into your local
workspace and the connections are shown in the Host Connections view. If any
details of the connection change, you must update them locally. If you import a
connection that already exists in z/OS Explorer and is associated with a credential,
only the existing connection details are updated; the credential is unchanged.
Procedure
1. Start from the Host Connections view. To open this view, click Window >
Manage Connections on the main menu for the workbench.
2. Click the Load Connections from file or URL icon in the toolbar of the view.
3. In the Load Connections window, type, or browse for, the location of the
connections file that you want to load or import. The connection file must have
a file type of .pref, and the location can be a file path or a URL.
4. Select Load or Import and click OK. The connections are loaded or imported.
What to do next
You can now use the loaded or imported connections to connect to a host system.
You must have a credential defined before you can connect. If you have not
defined any credentials, you are prompted to create one when you attempt to
connect. For more information, see the related links.
Related concepts:
Related tasks:
Defining connection credentials on page 47
When you connect to a system, your credentials, that is, your user ID and
password or pass phrase, are sent to the system for authentication. After you
define a credential, you can use it on all systems that share the credential without
reentering the details every time. You must have at least one credential before you
can connect to a system.
Updating a system connection

If any system connection settings change, you must update the connection details
in the Host Connections view to reflect the changes.
Before you begin
Ask your system administrator for the changed connection details for the system to
which you want to connect, and then use the following procedure.
Procedure
1. If the Host Connections view is not already open, click Window > Manage
Connections on the main menu for the workbench.

click the connection that you want to update. Click Edit.
3. In the Edit Connection window, change the information as required, and click
OK to save the changes. If the connection you changed is your current
connection, z/OS Explorer attempts to connect to the system with the changed
details. If you did not previously enter your password or pass phrase, you are
asked to enter it at this time.
If the connection you have changed is not your current connection, you must
click Connect to connect.
Results
If the connection is successful, the connection name appears in the connection

status bar, which is in the lower-right corner of the workbench. The connection
status icon is green, indicating a successful connection.
If the connection is not successful, the connection name appears in the connection
status bar, which is in the lower-right corner of the workbench. The connection
status icon is red, indicating that the connection was not successful. An error
message is displayed in the workbench status bar providing a reason for the
failure. Check the values in the fields, correct any errors, and click Connect to test
the corrections.
Exporting connections
About this task
You can export some or all of your connections to an external file. You can export
connections that you created locally, and connections that you have imported. The
file can be used by an individual user, or shared among many users.
Procedure
1. Start from the Host Connections view. To open this view, click Window >
Manage Connections on the main menu of the workbench.
2. Click the Export Connections to File icon in the toolbar of the view.
3. In the Export Connections to File window, select the connections that you want
to export from the list of locally created and statically imported connections.
You can expand and collapse the list, and use the following icons and buttons:
v Expand All icon. Expand the connection types and show all the connections.
v Collapse All icon. Collapse the connections and show only the connection
types.
v Show Links icon. Show the connections that are loaded from an external
connections file.
v Select All. Select all the connections.
v Deselect All. Deselect all the connections.

4. Optional: Type, or browse for, a location and file name for the exported file in
File Location. By default, the file is named my_connections.pref and is saved
in your current workspace. You must use a file type of .pref.
5. Click OK. The selected connections are exported as an XML file with a file type
of .pref. The file is saved at the specified location.
What to do next
You can now share your connections with other users. If you place the file in a
central location, other users can load or import the connections into their copy of
z/OS Explorer.
It is possible, but not advisable, to edit the file in a text editor. If you change the
connection information in the file, you must maintain the structure, otherwise the
import, or load might fail. The connection IDs are generated and used by z/OS
Explorer, and any changes to the IDs might cause the connections to fail.
Related tasks:
| Removing a default setting from a category or connection

If a connection is set as default, you can remove that default setting so that it is
not used for automatic connection when you start z/OS Explorer.
About this task
One connection in each connection category can be set as the default. You can
remove the default setting from a connection so that it is not used for automatic
connection when you start z/OS Explorer.
Procedure
Connections from the workbench menu to open the view.
| locate the connection category or connection that is currently set as default.
| 3. Right-click the connection category or connection, then click Remove from
default connections. Default is no longer shown in parentheses after the
connection name and the credential.
4. Repeat the previous two steps for each additional connection in a different
category that you want to remove the default setting from.
Results
The connection and its associated credentials remain, but it is no longer the default
connection for that connection category. Any other connections in a different
category that are set as default are unaffected.
Related tasks:

Connecting automatically at startup on page 50
You can set one connection in each connection category as the default. You can
then connect to the default connection for a category, or use these default
connections for automatic connection when you start z/OS Explorer.
perspective.
Deleting a system connection

If you no longer need one of your system connections, you can delete it
permanently from the z/OS Explorer. You can delete only connections that you
have created or imported into z/OS Explorer. You cannot delete connections that
are loaded from a shared connection definition file.
Procedure
1. If the Host Connections view is not already open, click Window > Manage
Connections on the main menu of the workbench. The Host Connections view
is displayed.
2. Expand the tree in the Connections section and click the connection you want
to delete.
3. Click Delete.
Results
The connection is removed from the list of connection names.
Disconnecting from a system

To disconnect the z/OS Explorer from your current system connection, you can use
the connection status bar or the main menu of the workbench.
Procedure
To disconnect the z/OS Explorer from the current system connection, choose one
of the following methods:
v Click the icon in the connection status bar, which is in lower-right corner of the
workbench. The icon is green for a non-SSL connection, or a padlock for an SSL
connection.
v Click File > Signoff on the main menu of the workbench.
What to do next
The z/OS Explorer is disconnected from the system and the icon in the connection
status bar, which is in the lower-right corner of the workbench, changes to a red
square. To reconnect, or connect to another system, see the related link.
Related concepts:


Notices
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted
by GSA ADP Schedule Contract with IBM Corp.
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte character set (DBCS) information,

contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM websites are provided for
convenience only and do not in any manner serve as an endorsement of those
websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
Intellectual Property Dept. for Rational Software

IBM Corporation
Silicon Valley Lab
555 Bailey Avnue
San Jose, CA 95141-1003
U.S.A.
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

Copyright license
This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
(your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. Copyright IBM Corp. 1992, 2016.
If you are viewing this information in softcopy, the photographs and color
illustrations may not appear.
Privacy policy considerations
IBM Software products, including software as a service solutions, (Software

Offerings) may use cookies or other technologies to collect product usage
information, to help improve the end user experience, to tailor interactions with
the end user or for other purposes. In many cases no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings
can help enable you to collect personally identifiable information. If this Software
Offering uses cookies to collect personally identifiable information, specific
information about this offerings use of cookies is set forth below.
This Software Offering does not use cookies or other technologies to collect
personally identifiable information.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the web at Copyright and
trademark information at www.ibm.com/legal/copytrade.shtml.
Terms and conditions for product documentation
Applicability
These terms and conditions are in addition to any terms of use for the IBM
website.
Personal use
Notices for IBM Explorer for z/OS 59

You may reproduce these publications for your personal, noncommercial use
provided that all proprietary notices are preserved. You may not distribute, display
or make derivative work of these publications, or any portion thereof, without the
express consent of IBM.
Commercial use
You may reproduce, distribute and display these publications solely within your
enterprise provided that all proprietary notices are preserved. You may not make
derivative works of these publications, or reproduce, distribute or display these
publications or any portion thereof outside your enterprise, without the express
consent of IBM.
Rights
Except as expressly granted in this permission, no other permissions, licenses or

rights are granted, either express or implied, to the publications or any
information, data, software or other intellectual property contained therein.
IBM reserves the right to withdraw the permissions granted herein whenever, in its
discretion, the use of the publications is detrimental to its interest or, as
determined by IBM, the above instructions are not being properly followed.
You may not download, export or re-export this information except in full
compliance with all applicable laws and regulations, including all United States
export laws and regulations.
IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE

PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED AS-IS AND WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING
BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,
NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

Copyright license
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.

Trademark acknowledgments
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at www.ibm.com/legal/
copytrade.shtml.
Adobe and PostScript are trademarks of Adobe Systems Incorporated.
Cell Broadband Engine - Sony Computer Entertainment Inc.
Rational is a trademark of International Business Machines Corporation and

Rational Software Corporation, in the United States, other countries, or both.
Intel, Intel Centrino, Intel SpeedStep, Intel Xeon, Celeron, Itanium, and Pentium
are trademarks of Intel Corporation in the United States, or other countries, or
both.
IT Infrastructure Library is a trademark of Central Computer and

Telecommunications Agency
ITIL is a trademark of The Minister for the Cabinet Office
Linear Tape-Open, LTO, and Ultrium are trademarks of HP, IBM Corp., and
Quantum
Linux is a trademark of Linus Torvalds
Microsoft, Windows, and the Windows logo are trademarks or registered

trademarks of Microsoft Corporation in the United States, or other countries, or
both.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other
countries.

Index
C G push-to-client configuration 15
defining configurations 17
clear cached files 29 global configuration files 17 exporting configurations 27
client key mapping file 31
configuration 1 master workspace 17
client certificates
preferences 36
H pushtoclient.properties 9, 15
hostIdMappings OID 36 product updates 14
code pages 21, 27
conversion 26
inheritance 26
compare editor 41 I R
configuration Importing connections 51 reject.product.updates 9, 15
client 1 incremental search results 39 remote z/OS search results
configuration and preference updates 33 increments 39 preferences 39
preferences 37 installation configuration file 11, 15 remote-to-local file mapping 21
configuration files installconfig.xml 11, 15 resetting configuration files 29
resetting 29 installedVersion 9, 15
configurations 5
configure S
workbench settings 33
zIDE tools 33
J setting
Java Cryptography Extension 36 preferences for z/OS solutions 35
Configuring an FTP system connection setting tracing levels 40
Java CSP 36
FTP 43, 50, 54 Sharing connections 51
JCE provider 36
Configuring an z/OSMF system Signoff 55
connection Signon 49
z/OSMF 46
Connecting to a system 48 K system configuration files 17
system name 41
Connecting to a system from the key mapping file 13, 31
connection status bar 50 keystore type 36
Connecting to a system using Signon 49
Connection status bar 50 T
connection to a z/OS system
creating 19
M tracing levels
setting 40
mapping transfer types 21
connections 5
remote to local file 21 Tutorial 43
Microsoft Cryptography API 36
MS-CAPI 36
D MVS Files
U
data sets preferences 38
mapping 23 updating
default encoding 26 configurations and preferences 33
Defining connection credentials 47
Deleting a system connection 55
P Updating connection configurations 52
planning a push-to-client environment 5

dependent files 41
preferences 5
Disconnecting from a system 55
client certificates 36 Z
distributing product and configuration z/OS Solutions preferences 41
compare editor 41
updates 7
dependent files 41
distributing product updates 9
MVS files 38
remote z/OS search results 39
setting for z/OS solutions 35
E system name 41
Exporting connections 53 z/OS Solutions 41
preview search results 39
primary system 17
F product updates
pushtoclient.properties 14
file system encoding 26
properties 5
file types 21
Proxy server
forcedUpgradeVersion 9, 15
Defining 45
push-to-client 7
resetting workspace configuration
files 29

IBM Explorer For Z - OS - Client Configuration Guide

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

IBM Explorer For Z - OS - Client Configuration Guide

Transféré par

Droits d'auteur :

Formats disponibles

IBM Explorer for z/OS IBM

Client Configuration Guide

Client Configuration Guide

Second edition (September, 2016)

| Chapter 2. Value Unit client licensing Chapter 6. Configuring non-RSE

Copyright IBM Corp. 2016 iii

Copyright IBM Corp. 2016 v

The following names are used in this manual:

Who should read this book

It describes how to configure push-to-client, individual workbench settings, and

Copyright IBM Corp. 2016 vii

Configuring and distributing system and global settings

Configuring individual workbench settings1

Copyright IBM Corp. 2016 1

| Chapter 2. Value Unit client licensing considerations

| z/OS Explorer VU generates a Universally Unique Identifier (UUID) to support

Copyright IBM Corp. 2016 3

In a push-to-client environment, these configuration files are stored on a remote

In a decentralized environment, developers still have the opportunity to share

Copyright IBM Corp. 2016 5

6 IBM Explorer for z/OS: Client Configuration Guide

Implementing a push-to-client environment involves several tasks: some on the

Copyright IBM Corp. 2016 7

Creating and distributing updates

8 IBM Explorer for z/OS: Client Configuration Guide

Distributing product updates

Before you begin

Chapter 4. Distribution of updates by using push-to-client 9

When a client workstation connects to a remote system that is configured to

To create and distribute product updates:

Important: If user authentication is required to access the code repository for

Installing client updates

Updating the installation configuration file

10 IBM Explorer for z/OS: Client Configuration Guide

Important: The behavior that is triggered by the installedVersion and

v A forcedUpgradeVersion attribute. If the version currently installed on a

You can specify the value for installedVersion and forcedUpgradeVersion as

Chapter 4. Distribution of updates by using push-to-client 11

12 IBM Explorer for z/OS: Client Configuration Guide

Updating the key mapping file

About this task

To update the key mapping file by editing it manually, do these steps:

Chapter 4. Distribution of updates by using push-to-client 13

Properties in pushtoclient.properties that affect product

How reject.product.updates affects installedVersion and

Relationship between forcedUpgradeVersion and

The following table shows the relationship between the forcedUpgradeVersion

Creating and distributing configuration files

Before you begin

To create and distribute remote connection definitions, configuration files, and

Chapter 4. Distribution of updates by using push-to-client 15

Creating a master workspace for push-to-client configuration

16 IBM Explorer for z/OS: Client Configuration Guide

Creating a master workspace for push-to-client configurations is no different from

If group-level control of product and configuration updates is enabled for the

Defining connections, configuration files, and preferences for

Global configuration files

Chapter 4. Distribution of updates by using push-to-client 17

System configuration files

18 IBM Explorer for z/OS: Client Configuration Guide

Creating a connection to a z/OS system

About this task

Restriction: Define only one connection to a particular remote system in each