Previous Topic Next topic Print topic

Micro Focus Enterprise Developer 2.3 Update 2 for Eclipse > General Reference > Application Workflow Manager > Workflow Manager Modeling Guide > Function Packages > MVS Function Package > Tool Types for the MVS Function Package > Get Data Sets

Get Data Sets

Function:

This tool is used to get a list of data sets corresponding to a given filter.

Tool Attribute:

Attribute Type Meaning
Dataset Matchname String The match name that should be used for returned data sets. Default value is MVSDATASET.

Parameters:

Parameter No I/O Type Meaning
1 [M] I String Data Set Filter. Data set filters can be specified in the same way as under z/OS ISPF. The reference variable userid can be used in the filter string. Valid filter specifications are for example:

&userid., &userid.*, SYS1.PROC*, &userid..TEST.*, &userid..TES%.*

* is a substitute for any number of characters; % is a substitute for exactly one character.

It is possible to specify more than one dataset filter separated by a semicolon.

2 [M] O File References the file contained in the Data Set List.

The output file descriptor (Data Set List) should be of type InputStream and have the following structure:

No Target ID
1 [M] Name of the Data Set
2 [M] Type of the Data Set
3 [M] Organization of the Data Set
4 [M] Record Format of the Data Set
5 [M] Record Length of the Data Set
6 [M] Space Units of the Data Set
7 [M] Primary Quantity of the Data Set
8 [M] Secondary Quantity of the Data Set
9 [M] Total Quantity of the Data Set
10 [M] Volume Serial of the Data Set
11 [M] Block Size of the Data Set
12 [M] SMS Managed of the Data Set
13 [M] Whether the Data Set  is accessible
14 [M] Suffix of the Data Set
15 [M] Whether the Data Set  is browsable
16 [M] Whether the Data Set  is editable
17 [M] Matchname identifying the Data Set Element Type

When defining the file descriptor you must make sure you define a unique delimiter used to separate the dataset properties. The MVS Explorer uses the delimiter "/%/$/".

The match name specified under "Dataset Matchname" must correspond with a match name defined for an element type in the model.

A reasonable modelling scenario could be that MVS data sets of a different type or organization should be modelled as different AWM element types (for example: ELE_MVS_PO, ELE_MVS_PS, ELE_MVS_LIBRARY) to model different icons or context menu actions for each data set type.

The following modelling rules must be observed so that the result of the "Get Data Sets" tool is properly mapped to the corresponding element types:

  • Define element types for each MVS data set type in the AWM model.
  • The match name of the element type should map the value returned using the "Get Data Sets" tool for the data set type or data set organization, see supported values below.
  • The property in which the data set type or data set organization is returned should be defined as special property Element_Type. Only one Element_Type property can be supported in the returned element list. This means it is only possible to differentiate the data sets based on the data set type or data set organization property.
  • The last parameter of the output file descriptor of the "Get Data Sets" tool (Matchname identifying the Data Set Element Type) must be omitted.

Supported values for the data set type are:

  • LIBRARY
  • HFS
  • PDS
  • LARGE
  • BASIC
  • EXTREQ
  • EXTPREF
  • SEQ
  • VSAM
  • GDG
  • NONE

Supported values for the data set organization are:

  • PS
  • PO
  • DA
  • KSDS
  • ESDS
  • RRDS
  • UNKNOWN (if data set is migrated)
Parent topic: Tool Types for the MVS Function Package
Previous Topic Next topic Print topic