Problem summary
****************************************************************
* USERS AFFECTED: All Content Manager OnDemand for z/OS 10.1 *
* and above customers *
****************************************************************
* PROBLEM DESCRIPTION: When calling 31-bit arsusec and *
* arsuperm, there is no DB2 connection *
* established when the exit is invoked. *
****************************************************************
Although not documented as part of the arsusec and arsuperm
APIs, it so happened in 9.5 and below that the exits were
invoked with a DB2 connection. The support in 10.1 for calling
the 31-bit exits did not invoke the exits with a DB2 connection.
In order to ease the process of upgrading, support is being
added to allow the arsuperm and arsusec exits with a DB2
connection established.
Problem conclusion
A new ars.cfg setting, ARSMVS_EXIT31_DB2_SECPERM, is being
provided. If specified as ARSMVS_EXIT31_DB2_SECPERM=1, the
arsusec and arsuperm exits will be invoked with an ODBC DB2
connection. Note that these will be additional DB2 batch
connections above that implied by ARS_NUM_DBSRVR.