Runtime considerations for the DBRC API

There are various considerations that you must address while the DBRC API is running such as DSPAPI and RECON access and how the API operates in an IMSplex.

DSPAPI macro access
In order to provide DBRC API (DSPAPI) macro access, your application must allocate IMS.SDFSRESL as either a JOBLIB or STEPLIB in your program's JCL because the DSPAPI is distributed with IMS.
RECON data set access
While the DBRC API is running, it uses up to three RECON data sets, which are allocated using the DD names RECON1, RECON2, and RECON3, or their respective alternate DD names. MDA members must be created for the data sets before the DBRC API can allocate RECONs.
RECON access authority
You can set three levels of access control for DBRC. Each level provides different permissions to users that access the RECON data sets.
Time stamp format for DBRC requests
Time stamps that are associated with DBRC requests (either input or output) follow a packed decimal UTC time format. DBRC ignores the value of the offset field in time stamps that are provided on Query requests.
How DBRC uses the output data set
While running under the DBRC API, DBRC might output messages and other information to a data set defined by the DD name SYSPRINT, or by a DD name you specify. If your program already uses the DD name SYSPRINT, you can specify an alternate DD name for the API to use.
Wildcard support for name parameters for Query requests
For more flexible Query requests, you can use a wildcard (an asterisk) in several keyword parameters that specify names. This wildcard support enables you to specify a name pattern for your query, expanding some queries and filtering others.

Parent topic: DBRC API