1156
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Description: In z/OS V1R11, object access |method (OAM) introduces 2 GB object support for tape media as well |as archive retention enhancements. You must run the CBRSMR1B job to |perform the migration from the z/OS V1R10 version of the object storage |database to the z/OS V1R11 version. The job will add columns ODSTATF, |ODRETDT, and ODINSTID to the existing object directory tables. Even |if you do not take advantage of the new function added in this release, |if you use OAM object support you must run the CBRSMR1B job to add |the new columns to the tables.
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: All with OnDemand for z/OS V7R1M0. *
****************************************************************
* PROBLEM DESCRIPTION: Currently, ARSLOAD/ARSADMIN uses TCP/IP *
* to communicate with the server. This *
* APAR provides a means for *
* ARSLOAD/ARSADMIN to perform the server *
* functions directly. That is, it will *
* directly interact with DB2 and VSAM/OAM *
* instead of routing requests to the *
* server. *
* *
* The ARSLOG exit can get invoked for *
* messages even though the System *
* Parameters window of the Administrative *
* Client does not have anything checked *
* for User Exit Logging. This is by *
* design. In order to allow an *
* installation that is not using the *
* ARSLOG exit to indicate that no *
* attempt is to be made to call ARSLOG, *
* a new ars.cfg entry is provided to *
* disable this. *
* *
* For a given load, the logoff message *
* (message number 32) can appear twice *
* in the OnDemand system log. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Currently, ARSLOAD/ARSADMIN uses TCP/IP to communicate with the
server. This APAR provides a means for ARSLOAD/ARSADMIN to
perform the server functions directly. That is, it will
directly interact with DB2 and VSAM/OAM instead of routing
requests to the server.
The ARSLOG exit can get invoked for messages even though the
System Parameters window of the Administrative client does not
have anything checked for User Exit Logging. This is by design.
In order to allow an installation that is not using the ARSLOG
exit to indicate that no attempt is to be made to call ARSLOG,
a new ars.cfg entry is provided to disable this.
A flag was not getting set to indicate that a logoff message
should not be put in the OnDemand System log.