z/OS DFSMS DFM Guide and Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


How Distributed FileManager DataAgent Works

z/OS DFSMS DFM Guide and Reference
SC23-6848-00

The DFM DataAgent function allows workstation users to invoke remote procedures that run as extensions or agents of DFM. This expands the capability of this mode of access by providing access to functions or data sets not ordinarily supported by DFM and by allowing workstations greater control over processing on the z/OS® server.

DFM DataAgent allows the workstation user of SdU to invoke user-written, IBM-written, or vendor-written DFM DataAgent routines using:
  • TSO commands, CLISTs, or REXX execs
  • DFM DataAgent routines through the remote file access feature of SdU.

The DFM DataAgent is an extension to the DFM component of DFSMSdfp and to the remote DDM application of SdU that provides the ability for remote callers to invoke the DFM DataAgent function to execute specified routines on z/OS. The functions that may be performed using this facility include the execution of TSO and REXX commands as well as user-written programs. Samples are provided that show specific uses of this function. The DFM DataAgent enhancement represents a significant extension of the functionality of the remote DDM application beyond basic data access.

A sample DataAgent is provided to invoke TSO functions, such as TSO CLISTs, REXX execs, or TSO commands. Another sample DataAgent is provided to invoke SORT.

The following is an example of how the DFM DataAgent expands the capability of the remote DDM application onz/OS. Before the DataAgent, the remote application was able to create and delete files, and read, write, update, and delete data contained in files on z/OS. With the DataAgent, this capability is broadened significantly by the ability to execute remote procedures on z/OS. A DataAgent job could be invoked to preprocess data on z/OS by retrieving it from the files or other repositories and place it in the file that the application will access. The DDM application could then process the data in the intermediate file. When the DDM application has finished, a second DataAgent could be invoked to take the data in the intermediate file and distribute the changes to the permanent files.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014