(ZOS) Optimized local adapters client-side code relocated to common storage
With WebSphere Application Server v8.0.0.1, the amount of optimized local adapters code that needs to be loaded in the external client address space on behalf of the optimized local adapters APIs is reduced significantly.
Prior to WAS v8.0.0.1, the optimized local adapters OLAMODS dataset, which contains the optimized local adapters API calling vector modules, had to be present in a job's STEPLIB DD or in the z/OS system link list concatenation. With optimized local adapters in WAS v8.0.0.1, this is no longer required. The optimized local adapters BBOA1* and BBGA1* API calling stubs have been enhanced to locate the optimized local adapters calling vector in z/OS common storage, which is located off the WAS global BGVT. Once the application binds in the optimized local adapters API stubs, it no longer requires the BBOACALL optimized local adapters transfer vector module in the STEPLIB.
When the first WAS v8.0.0.1 cell, node or server is started, and the optimized local adapters module vector is loaded into common storage, applications that use the V8.0.0.1 calling stubs can exploit this new capability. WAS z/OS initialization code is enhanced to load a new copy of the common storage-based optimized local adapters module vector only when it detects a level of the vector higher than the one that was already active.
Use of the optimized local adapters API stubs (BBOA1* modules) shipped prior to V8.0.0.1 is still supported on V8.0.0.1. However, use of the V8.0.0.1 stubs on WAS versions prior to V8.0.0.1 is not supported. When we begin using the V8.0.0.1 optimized local adapters calling stubs, ensure that they are used to interact with WAS v8.0.0.1 and newer servers only.
The new optimized local adapters lightweight stubs are supported in the batch, Customer Information Control System (CICS ), IMS™, and USS environments. For CICS, the requirement for placing the OLAMODS dataset in the CICS DFHRPL DD concatenation remains. For IMS, the requirement for placing the OLAMODS dataset in the DFSESL DD concatenation also remains.
Related:
Optimized local adapters for z/OS APIs Optimized local adapters for z/OS usage scenarios Optimized local adapters environment variables Calling existing IMS transactions with optimized local adapters over OTMA z/OS: Use optimized local adapters for inbound support z/OS: Use optimized local adapters for outbound support Accessing data using Java EE Connector Architecture connectors Enable the server environment to use optimized local adapters Extensions to data access APIs