Just as with IBM® COBOL and DB2®, there are no particular changes required to PL/I source for use of embedded SQL in the z/OS® Batch Runtime environment. Since the RRSAF attachment is acquired by the runtime prior to the application receiving control, it is not necessary for any application code to initialize a DB2 RRSAF local attachment (identify, create thread, etc RRS protocal). Any such code should either be removed or recognize an existing attachment. Normal RRSAF pre-compilation or DB2 coprocessor is sufficient to establish the correct runtime linkage to DB2. See the the sample DB2 “phone” application DSN8BP3 provided and built with DSNTEJ2P in the hlqprefix.SDSNSAMP library provided with your DB2 installation. Simply include DSNRLI in the bind step of your program to get the correct RRSAF linkage. This sample application is described in the DB2 for z/OS Application Programming & SQL Guide SC18-9841 in the “DB2 sample applications and data” chapter.

For Transactional VSAM, once the TVS environment is established there are no required changes for the VSAM RLS (Record Level Sharing) APIs used in the application program. Transactional VSAM is a systems programmer only setup with correct TVS server, RLS server, VSAM dataset, and Logger definitions. The z/OS Batch Runtime provided RRS commit and rollback operations initiate any 2-phase commit processing required of the TVS server. Good references are z/OS DFSMStvs Planning and Operating Guide SC26-7348-00 and z/OS DFSMStvs Administration Guide GC26-7483-00.