To Share or Not to Share
Just because you are in a data sharing environment does not mean all the data must be shared. Some data can be dedicated to one subsystem. These non-shared objects are defined unique to one member. They can also reside/remain on non-shared DASD if you want (Figure 9.2). It is easy to leave objects dedicated to one subsystem; you simply put the object in a virtual buffer pool that is not backed by a group buffer pool in the coupling facility.
Figure 9.2. Sharing Data
Note
Not sharing data between members may be a consideration if the application is not suited for data sharing or there is no requirement for data to be shared ...
Get DB2® Universal Database for OS/390® Version 7.1 Certification Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.