IBM File Manager for z/OS User's Guide and Reference Ver 14.1

Generic method examples

The following examples demonstrate the generic method for data access.

z/OS® Connect can map as little or as much of the JSON request payload as required during API creation. In these examples, nothing is mapped, so the API caller passes all relevant parameters.

Example 1: Read an MVS data set sequentially
In the following example, File Manager Service Provider REST API calls are issued to start a persistent session to read records in an MVS™ data set, using a template to map fields in each record.
Example 2: Read a keyed record from a CICS VSAM data set
In the following example, File Manager Service Provider REST API calls are issued to access a CICS® VSAM data set using a template, and read one record from a specified key position.
Example 3: Read the entire contents of a USS file
In the following example, File Manager Service Provider REST API calls are issued to read all records in a USS file without using a template or copybook.
Example 4: Read an IMS database sequentially
In the following example, File Manager Service Provider REST API calls are issued to start a persistent IMS session to read segments from an IMS database, using an FM/IMS view to map fields in each segment.
Example 5: Read from a position within an IMS database
In the following example, File Manager Service Provider REST API calls are issued to position within an IMS database and then read a segment at that position.
Example 6: Read a Db2 database sequentially
In the following example, File Manager Service Provider REST API calls are issued to start a persistent Db2® session to read rows from a Db2 table, using a File Manager template to map fields in each row.
Example 7: Apply a WHERE clause to a Db2 table
In the following example, File Manager Service Provider REST API calls are issued to limit the result table using a Db2 WHERE clause, then read the first row in the result table.

Parent topic: Example scenarios

Feedback