The GLVSHAREDFILE parameter relates to the OPSHFI command processor and shared file support. The OPSHFI command processor provides you with the capability to store global variable records on an external VSAM key-sequenced data set that can be shared among systems. Using various OPSHFI keywords, you can WRITE variable records to the VSAM file, or READ or DELETE variable records from the VSAM file.
The GLVSHAREDFILE parameter specifies the name of the VSAM key-sequenced file that CA OPS/MVS should use for OPSHFI requests. The VSAM file must not be in the load state.
For a sample IDCAMS definition of the file, see the OPAMSVDB member of the SYS1.OPS.CCLXCNTL data set. The key of the VSAM file is:
|
This part of the key… |
Contains… |
|---|---|
|
Beginning with position 1 of the key and continuing for the entire key length, minus the last 4 characters of the key |
The variable name |
|
The last 4 characters of the key |
Either the SMF ID of the owning system, or blank for variables that are shared across systems |
Note: If you need to perform emergency maintenance on or a reorganization of the real VSAM file, change the value of the GLVSHAREDFILE parameter to NULLFILE or DUMMY. Then use the OPSHFI command processor to issue a dummy file request. Doing this deallocates the VSAM file so that you can repair or reorganize it. When the file is ready to use again, reset the GLVSHAREDFILE parameter to the name of the VSAM file.
For related information, see the description of the OPSHFI command processor in the Command and Function Reference.
NULLFILE
All file requests become null operations and process no variables.
The z/OS cluster name of the VSAM file
DUMMY
All file requests become null operations and process no variables.
Anytime
Example: GLVSHAREDFILE
This function specifies that all OPSHFI requests should become null operations and process no variables.
OPSPRM('SET','GLVSHAREDFILE','NULLFILE')
|
Copyright © 2014 CA.
All rights reserved.
|
|