VSAM Performance Enhancement › Activating and Deactivating VPE on Your System

Activating and Deactivating VPE on Your System

The VPE Operating System interfaces are installed and removed by running the VPEHINST program. The interface programs can be installed in an activated or deactivated state. When deactivated, the programs are still installed in the operating system but are nonfunctional.

The VPEHINST program typically runs as part of your IPL sequence to install the VPE Operating System interfaces. The JCL required to run this program is as follows:

//VPEJOB JOB ...
 //STEP1  EXEC PGM=VPEHINST,
 //      PARM='ACTION=actionname[,RESTRICT=jobname']
 //

The valid values for actionname are:

ACTION=STATUS

Directs VPEHINST to display the status of the VPE Operating System interfaces on the system console.

ACTION=INSTALL

Directs VPEHINST to install the VPE Operating System interfaces.

ACTION=INSTALLD

Directs VPEHINST to install the VPE Operating System interfaces in deactivated state.

ACTION=ACTIVATE

Directs VPEHINST to activate the VPE Operating System interfaces which are currently installed and deactivated.

ACTION=DEACTV

Directs VPEHINST to deactivate the VPE Operating System interfaces which are currently installed and activated.

ACTION=DELETE

Directs VPEHINST to remove the VPE OPEN interface, but to leave the VPE CLOSE interface installed and active. This is desirable when there are jobs currently running with open VSAM data sets and you want the VPE CLOSE interface to gather statistics on them when the CLOSE occurs.

ACTION=FORCDEL

Directs VPEHINST to immediately remove both the VPE OPEN and CLOSE interfaces, even if statistics are lost on any currently open VSAM data sets.

RESTRICT= jobname

Directs VPE to only operate on the job specified. This restriction always takes precedence over the scope of operation specified in the VPE Rules Table and/or the VPE Control DD statements. This parameter is useful when you want to test VPE prior to implementing it for production use. The following VPEHINST example installs the VPE Operating System interfaces such that they only operate when the job name is 'TESTJOB1':

//VPEINST JOB ...
 //STEP1   EXEC PGM=VPEHINST,
 //       PARM='ACTION=INSTALL,RESTRICT=TESTJOB1'
//