Using LUA in Optim z/OS to run LOOKUP functions using the optim.mask() function call

Answer

If a user has Optim for z/OS release 11.3 installed, along with the Optim Data Privacy feature, a user can call many of the Optim Data Privacy Providers using a LUA Column Map procedure. With the application of fixes for APAR PI53583 in FMID HAI8B30 (PTF UI34470), and APAR PI53387 in FMID HAEYB30 (PTF UI34471), users can now call LOOKUP and its variants using the Optim Data Privacy functions. This was not possible before because Optim Data Privacy function normally uses a form of accessing DB2 tables that are different and incompatible from how Optim for z/OS accesses DB2 data. There is a new parameter value in the LOOKUP definition statement that tells Optim Data Privacy to use embedded SQL interface, the same interface Optim for z/OS uses. Users would add the parameter and value “lib=DB2ZOSSQL” to their lookup syntax in the optim.mask() call as well as doing a DB2 Bind of a Collection that will be added to the current DB2 plan being used. This also contains documentation describing new syntax available from PTF UI34470 which contains updates matching maintenance on other platforms described as Fixpack 04.