Professional Documents
Culture Documents
Recommendations
Article Number:000051197 Version:1
Key Information
Audience: Level 30 = Customers Article Type: Break Fix
Last Published: Thu May 30 22:11:43 GMT 2013 Validation Status: Final Approved
Summary:
Article Content
Impact: Mainframe Gatekeeper Rules, Requirements and Recommendations
Environment: OS: Mainframe
OS: z/OS
EMC SW: EMC Mainframe Enablers
EMC SW: ResourcePak Base for z/OS
EMC SW: Consistency Group for z/OS
EMC SW: AutoSwap for z/OS
EMC SW: SRDF Host Component for z/OS
EMC SW: TimeFinder/Mirror for z/OS
EMC SW: TimeFinder Clone Mainframe SNAP Facility for z/OS
EMC SW: SRDF/STAR for z/OS
EMC SW: ResourcePak Extended for z/OS
EMC SW: GDDR
Change: Installation or implementation of EMC Mainframe software products.
Resolution: This Knowledgebase solution is divided into eight sections:
1. What is a Gatekeeper?
2. What kinds of Gatekeepers are there?
3. How should I configure a Gatekeeper?
4. What are Command Gatekeepers"?
5. What are Software Gatekeepers"?
6. Are there special considerations for Gatekeepers used with Consistency Groups?
7. How do I verify the current Gatekeeper usage?
8. What software components utilize Gatekeepers?
1. What is a Gatekeeper?
Mainframe Enabler (and Solutions Enabler on open systems) are EMC software components used to control the storage array features of
Symmetrix arrays.
They receive user requests and generate low-level commands (syscalls) that are transmitted into the Symmetrix array for action.
Gatekeeper devices are Symm Devices that act as the target of command requests to Enginuity-based functionality. These commands arrive in
the form of disk I/O requests (and so a 'disk' must be named by the host as the 'address' or target of that command). The more commands that
are issued from the host, and the more complex the actions required by those commands, the more array processor (and channel) resources that
are required to handle those requests in a timely manner. Also, these syscall I/Os are also subject to device queuing, as with any other kind of
I/O operation.
Mainframe enabler selects Gatekeepers, and looks for small devices or devices that are not heavily loaded. If it cannot find optimal choices, it
will service the command request by selecting some device. It is also possible to issue so many requests and/or requests that involve complex
operations, such as over-the-link operations or performance data acquisition, that applications on that channel or using those array facilities can
be impacted. It is important that Gatekeeper usage be monitored against application or system activity to ensure there are no conflicts or
operational impacts.
Application, system and Gatekeeper traffic conflicts can lead to application performance impacts and or Symmetrix command delays or
failures. Some Symmetrix commands such as MSC trips, etc., can be seriously limited in their effectiveness if such performance issues are
encountered.
2. What kinds of Gatekeepers are there?
EMC Mainframe software uses two types of gatekeepers:
2.1) Command gatekeepers to issue local or remote commands, i.e.
SRDF/Host Component for z/OS
TimeFinder/Mirror for z/OS
TimeFinder/Clone for z/OS
Consistency Group for z/OS
Quality of Service Utility for z/OS
Symmetrix Priority Control
Dynamic Cache Partition
2.2) Software gatekeepers: Used by software components like
SCF (EMC Symmetrix Control Facility)
CSC (Cross System Communication)
MSC (Multi-Session Control)
CG (Consistency Groups)
ASY (SRDF/A monitor)
DSE (Delta Set Extension)
3. How should I configure a Gatekeeper?
3.1 The attributes for all gatekeeper types are the same: required
Local (non-SRDF, actually not included in ANY replication process)
OFFLINE and unused from all lpars, a minimum of two online paths recommended
Unique 1 (no shared use between any software or command gatekeepers)
Unique 2 (not shared between lpars, not used by multiple lpars)
Not the first addressable device in a DMX/Symmetrix
Minimum size hypervolumes are sufficient and recommended.
Gatekeepers require only a small amount of space, 3 MB (3 cyl) for Enginuity levels 57xx, 58xx and higher, and 3 MB (6 cyl) for Enginuity levels of
56xx and lower.
Users are encouraged to not build Gatekeepers in larger sizes as the small size can be used as characteristic to locate Gatekeepers.
3.2 Other considerations include:
There is no specific local protection requirement for a gatekeeper (they can be mirrored, RAID5, RAID6, )
If no OFFLINE-to-all-systems device is available at all, low I/O profile devices should be used
Devices that are candidates for Reserves should be avoided for the following reasons:
Reserve penetration may not be in effect for all Syscall I/Os
An EMC Syscall I/O (using Reserve Penetration) may queue on the UCB behind an application I/O that is Start Pending in the channel
subsystem for the chosen device (Reserved to another system)
3.3 This is a list of attributes the gatekeepers must have: NOT
SRDF/A Device
R1 Device
R2 Device
Virtual Device
Virtual Save Device
BCV Device
Meta Device
3.4 What else should I keep in mind when configuring Gatekeepers for the Mainframe?
The first addressable CKD device in a DMX can be configured as a hypervolume with minimum size
Plan for sufficient gatekeepers, especially in a multi-lpar and/or multi-sysplex environment
For command gatekeepers, the Syslog, EMC RDF STC log and/or batch job output should be reviewed.
For SCF.GATEKEEPERs and SCF.CSC.GATEKEEPERs there are commands available to verify the current gatekeeper usage:
This command should be issued per locally attached controller on each lpar. F EMCSCF,DEV,DIS,CNTRL(xxxxx)
SCF0341I DEV,DIS,CNTRL(02092)
SCF4011I CONTROLLER 0001901-02092 is currently
using CCUU EC8F as its SCF gatekeeper.
SCF0361I Gate Keeper Devices EC8F EC8E
F EMCSCF, CSC,DIS HOST CNTRL(ALL) This command should be issued on each lpar.
SCF0663I CSC,DIS HOST CNTRL(ALL)
SCF0660I CSC HOST DISPLAY 614
CONTROLLER SERIAL NUMBER : 0001901-02405
GATEKEEPER MVS DEVICE : 5C82 SYM DEVICE : 1CF2
CONTROLLER SERIAL NUMBER : 0001901-02092
GATEKEEPER MVS DEVICE : EC81 SYM DEVICE : 0CF1
After changing gatekeeper definitions for SCF.GATEKEEPER and/or SCF.CSC.GATEKEEPER the following sequence activates these
changes.
This command sequence should be issued on each lpar:
Modify the INI parms for EMCSCF (to specify the changed gatekeepers)
F EMCSCF,INI,REFRESH (to re-read the INI parms)
F EMCSCF,DEV,REFRESH,GATEKEEPERS (to actually refresh the SCF.GATEKEEPERs)
F EMCSCF,CSC,REFRESH (to actually refresh the SCF.CSC.GATEKEEPERs)
SCF0663I CSC,REFRESH
SCF0666I CSC REFRESH SCHEDULED FOR 2 CONTROLLERS
SCF0652I CSC (0001901-02092) AREA:00010000/00030000, GATEKEEPER:EC81
(SYMM07/5X72/00000/F8)
SCF0652I CSC (0001901-02405) AREA:00010000/00030000, GATEKEEPER:5C82
(SYMM07/5X72/00000/F8)
8. What software components utilize Gatekeepers?
Mainframe Enablers
AutoSwap for z/OS
Consistency Group for z/OS
GDDR
ResourcePak Base for z/OS
SRDF/Host Component for z/OS
SRDF/STAR for z/OS
TimeFinder Clone for z/OS
Mainframe SNAP Facility for z/OS
TimeFinder/Mirror for z/OS