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.
- Function and panel reference lists

Specifying a remote resource

For functions in the File Manager ISPF interface that support remote resources you can prefix the resource name as follows:

RM:remote_id:resource_name

Where:

remote_id: Is the 1-8 character remote connection definition. A generic pattern is supported but you must specify a non-blank resource name.

resource name: Any data set, path or CICS® resource name can be specified.
Note: Quotes are invalid when specifying a remote data set name. You must specify the fully qualified name. Generic names are supported but avoid using ** and * as that may result in long catalog searches on the remote system.