z/OS DFSMSrmm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Setting up parallel processing

z/OS DFSMSrmm Implementation and Customization Guide
SC23-6874-00

When you are converting to DFSMSrmm, you might want to run two versions of your installation exits at the same time. The CBRUXENT exit, the CBRUXEJC exit, and the IGXMSGEX exit provide support that enables your existing exits to control processing before DFSMSrmm gains control. You can set up parallel processing using an SMP/E USERMOD or outside of SMP/E.

The CBRUXENT exit and the CBRUXEJC exit samples shipped with DFSMSrmm can ensure that the DFSMSrmm processing is run after your existing exits are run and that DFSMSrmm records any information modified by your existing exits. The tape management decisions made by your existing exits are used instead of any tape management decisions that DFSMSrmm might make.

The IGXMSGEX exit includes support that enables your existing exit to perform processing before DFSMSrmm gains control. You use the IGXMSGEX exit to update tape drive displays. You only need either one system or the other to be updating the drive display. As long as you use the same scratch pool names on both systems, either your existing exit or DFSMSrmm can be used to update the drive display.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014