Skip to content

Integrating a Desktop Workspace with ZMF

Java Perspective Integration

Mass Download and Mass Checkin:

ZMF for Eclipse integrates ChangeMan ZMF with the Java perspective of the workbench and Java projects in the desktop workspace using the Team menu of the Package Explorer view. As part of the support for this integration, mass download and mass upload with automatic change control at the application level have been added to ZMF for Eclipse. This enables development of mainframe Java code on the desktop, where you can take advantage of powerful GUI Java editors and the many open-source code libraries, code generators, developer toolkits, debuggers, documentation generators, and more that are available for Java. At the same time, ChangeMan ZMF retains control of software assets.

Automated Library Mapping:

Dynamic integration between the Java perspective and ChangeMan ZMF4ECL relies on automated library mapping between desktop workspace directories and mainframe software repository libraries. Customers configure the desired library mappings in the ECLIPSE member of the ZDDOPTS parameter library for ChangeMan ZMF. These mappings ensure that file types and desktop filename extensions correspond in a one-to- one fashion with the ZMF library types defined for an application.

Desktop workspaces must be structured in accordance with the relevant library mappings for automated component checkout, checkin, and lock to work as intended.

Best Practices for ZMF Desktop Workspaces

Any folder on the desktop can be defined as a workspace to Eclipse or IDz. To use such as folder as a personal development library with ChangeMan ZMF, the following best practices are recommended.

  • Dedicate a workspace to the exclusive use of ZMF applications. Always switch to the ZMF workspace before working with components managed by ChangeMan ZMF.

Tip

If you frequently work with ZMF applications, you may wish to make the ZMF workspace the default workspace for the workbench.

  • Organize the workspace by ZMF application, then by file type (binary, source, HTML, and so on) within application. For example:

  • All files in the same folder must be of the same file type. This is necessary so that conversions between ASCII and EBCDIC character formats proceed properly across systems (for example, excluding binaries but including text files), and so that ZMF build jobs treat different object types correctly.

    Tip

    If you frequently work with ZMF applications, you may wish to make the ZMF workspace the default workspace for the workbench.

Enabling Library Mapping in ZDDOPTS

Library Mapping Prerequisites:

Library mapping between mainframe library types in the ZMF repository and their corresponding desktop file types and folders is managed automatically by ZMF for Eclipse if the necessary library maps exist on the ZMF server. Library maps must be defined in the ECLIPSE member of ZDDOPTS for each ZMF server. Different library type-to-folder mappings may be specified for different ZMF applications.

For details about all ZDDOPTS members, see Appendix A, "ZDDOPTS Parameter Reference" on page 65.

Add to Workspace Option:

If library mapping is not enabled in ZDDOPTS, the Add to Workspace option will be grayed out in the contextual menus for the relevant applications in Serena Explorer.

Library Mapping Parameter Syntax***

ZDDOPTS Syntax:

All parameters in ZDDOPTS are defined using XML. The ECLIPSE member of ZDDOPTS contains one or more application mapping profiles. Each mapping is defined by a element that identifies the relevant application in its application attribute. Individual library mappings within an application are defined using the element, which may be repeated.

A library map for a given application has the following general form:

<profile application="aaaa">

<libtype name="bbb"
{eclipsefolder="bbb"|"c...c"|""}
{binary="Y|N" }
{root="Y|N" } />

...

</profile>

where

  • one <profile> tag is required for each ZMF application that allows checkout to a desktop workspace development library.

  • any number of <libtype> subtags are allowed within a tag.

ZDDOPTS Library Mapping Example

<profile application="APP1">
<libtype name="ECL" eclipsefolder=""
binary="N" root="Y" />
<libtype name="JV1" eclipsefolder="src"
binary="N" root="N" />
<libtype name="JIN" eclipsefolder="lib"
binary="Y" root="N" />
<libtype name="WSD" eclipsefolder="wsdl"
binary="N" root="N" />
<libtype name="WIN" eclipsefolder="htdocs"
binary="Y" root="N" />
<libtype name="JCT" eclipsefolder="JCT"
binary="N" root="N" />
<libtype name="WCT" eclipsefolder="WCT"
binary="N" root="N" />
</profile>

XML Elements and Attributes for Library Mapping

Element or Attribute Name Usage Data Type Allowed Values &Comments
1 - n Required Complex
  • One per ZMF application
  • Unbounded per ZMF site
application Required 1-4 bytes,character ZMF application name
1 - n Required Complex
  • One per ZMF library type
  • Unbounded within ZMF application
name Required 3 bytes,character Name of ZMF library type to be mapped to a desktop workspace folder
binary Optional 1 byte,character
  • Y = Yes, binary objects (executables, graphics,compressed data) should be excluded from ASCII/EBCDIC conversion
  • N = No, source or text object should not be excluded from conversion default)
eclipsefolder Optional 0-n bytes,character
  • Name of desktop workspace folder to associate with ZMF library type. All objects in a desktop folder will have the same filename extension as the folder name.
  • NOTES:
  • Defaults to same value as name attribute.
  • Must be set to null if root="Y".
root Optional 1 byte,character
  • Y = Yes, objects in ZMF library should be copied to root directory (Java only)
  • N = No, objects in ZMF library should not be copied to root directory (default)
  • NOTES:
  • Non-Java applications must use "N".
  • If "Y", must set value of eclipsefolder="".
Back to top