Home
Working with File Manager
File Manager Service Provider for z/OS® Connect Enterprise Edition
File Manager Service Provider for IBM® z/OS® Connect Enterprise Edition enables client applications to access IBM Z data sources using z/OS Connect.
Using the Build Toolkit plug-in
z/OS® Connect provides a Build Toolkit (zconbt) for creating service archive (SAR) files. SAR files are used during z/OS Connect API creation to associate APIs with service providers such as File Manager Service Provider.
zconbt command line utility
The zconbt utility expects as input a properties file and generates as output a SAR file.

Working with File Manager
- File Manager overview
- Getting started with File Manager
- Viewing and changing data sets
  To view data stored in a supported data set, use the View Utility or the Edit Utility.
- Creating and editing templates
  For many tasks performed with File Manager, you can manipulate your view of a data set by applying a template.
- Working with the Template List
  Display a list of templates and perform actions on them.
- Filtering records with templates
- Managing data sets
- Using File Manager utilities
- Tape Specific Functions
- Disk/VSAM Data Functions
- OAM Functions
- Using UNIX™ System Services and the Hierarchical File System
- Introduction to programming with File Manager functions
- Enhancing File Manager processing
  You can enhance normal processing of a number of File Manager tasks by supplying a procedure that runs in conjunction with the File Manager process.
- Redefines criteria
  Redefines criteria can be specified for a field with a REDEFINES clause, or a field that is the target of a REDEFINES clause.
- Enhanced ISPF: Reference List, Search, Change, and PDSE Workbench
  File Manager provides several enhancements to the basic facilities that are available in an ISPF session: Enhanced Reference List, Enhanced Search, Enhanced Change, and PDSE Workbench.
- File Manager Service Provider for z/OS® Connect Enterprise Edition
  File Manager Service Provider for IBM® z/OS® Connect Enterprise Edition enables client applications to access IBM Z data sources using z/OS Connect.
  - Methods for accessing IBM Z data sources
    File Manager Service Provider supports two methods for accessing data: generic and specific.
  - Single reads versus multiple reads
    Regardless of which method for accessing data is used (generic or specific), the File Manager Service Provider starts a File Manager “view” session to read records from a given data resource.
  - Requests and responses
    The File Manager Service Provider expects JSON payloads from z/OS® Connect-defined APIs representing requests, and passes back JSON payloads as responses to these requests.
  - Creating z/OS® Connect APIs
    Installing the z/OS® Connect EE API Editor into your Eclipse environment adds a perspective that allows you to create a z/OS Connect EE API Project.
  - Using the Build Toolkit plug-in
    z/OS® Connect provides a Build Toolkit (zconbt) for creating service archive (SAR) files. SAR files are used during z/OS Connect API creation to associate APIs with service providers such as File Manager Service Provider.
    - zconbt command line utility
      The zconbt utility expects as input a properties file and generates as output a SAR file.
    - Build Toolkit plug-in properties
      This topic describes the properties expected by the File Manager Build Toolkit plug-in.
    - Deploying SAR files
      Service archives (SAR files) created using the zconbt command-line utility must be deployed to your z/OS® Connect WLP environment.
    - Configuring File Manager SAR files
      Each SAR file that was built using the zconbt command and the File Manager Build Toolkit plug-in identifies a connection ID (connid).
    - Modifying templates
      If you create a SAR file based on a template and later change the template, the response schema of your SAR file might be out of sync with the data returned by File Manager Service Provider.
  - Swagger documentation
    The z/OS® Connect API Editor automatically generates Swagger documentation during API creation. A swagger.json file is created within the API project.
  - Security
    The File Manager Service Provider for z/OS® Connect EE requires an API caller to pass an HTTP Basic Authorization header that identifies the user ID and password of the caller.
  - Troubleshooting
    Use this information to troubleshoot File Manager API request failures.
  - Example scenarios
    The following examples illustrate the sequence of File Manager Service Provider REST API calls used to process some common file types under different scenarios.
- Function and panel reference lists

zconbt command line utility

The zconbt utility expects as input a properties file and generates as output a SAR file.

The input and output file names are passed as parameters to the utility. For example:

> zconbt -p=customer1.properties -f=customer1.sar

The File Manager Build Toolkit plug-in expects the properties file to nominate a data resource (file) and a matching File Manager template, view, or copybook. The plug-in uses this information to build the SAR file. For example:

name=customer1 
version=1.0 
provider=filemanager 
host=10.1.1.2 
port=9043 
userid=admin 
passwd=s3cr3t 
file=FMN.CUSTOMER.KSDS 
template=FMN.TEMPLATE(CUST1) 
connid=default

As with all SAR files, the name must be unique. For File Manager, the provider must be filemanager. The host, port, userid and passwd properties are used during SAR file creation to connect to a z/OS® system to access the template which is used to generate the SAR file’s JSON response schema.

The z/OS® system must be running the ADFzCC server (IPVSRV) on the host and port number provided. The user ID must have read access to the template, view, or copybook file. The connid property associates the generated SAR file with a configuration element in the server.xml of the z/OS® Connect WLP server. For example:

<FileManager_Connection>
    id="default" runport="2800" max_timeout="1800"
</FileManager_Connection>

Once a SAR file has been created, it can be used to build z/OS Connect APIs using the z/OS Connect API Editor. See Creating z/OS Connect APIs for more information.