Using parameter lists to pass information to the DFSMSrmm API

You can write your application program to include this processing:

Serially or concurrently process subcommands.
Use single parameter lists or multiple parameter lists for each subcommand. For example, your application program can use one parameter list for a SEARCH type of subcommand and another parameter list for a CHANGE type of subcommand.
Reuse resources (tokens).

You can use variations of parameter lists and tokens in your application program to meet your application requirements.

Table 1. Types of parameter lists
Variation	Guidelines	Reference
Single parameter list and a single token area	Only one subcommand request can be active at a time. An active subcommand request must be completed before beginning another subcommand request.	Coding a single parameter list, single token area
Single parameter list and multiple token area	More than one subcommand request can be active at a time. Only one subcommand request can be processed at any given time.	Coding a single parameter list, multiple token areas
Multiple parameter lists with a single token area	Only one subcommand can be active at a time. Different parameter lists can be used for these tasks: Begin subcommand requests. Continue subcommand requests. Release resources. Starting a new subcommand request ends any previous subcommand request.	Coding multiple parameter lists, single token area.
Multiple parameter lists and multiple token area	More than one subcommand request can be active at a time. More than one active subcommand request can be processed at a time. Different parameter lists can be used to: Begin subcommand requests. Continue subcommand requests. Release resources.	Coding multiple parameter lists, multiple token areas

For illustrative purposes, the examples use inline code segments with shortened code lines.