Draft Document for Review February 7, 2020 3:15 pm 8464ch03_business requirements.fm GLYPH<SM590000> Another main item to consider is how the drives are managed across the different  systems, and which systems share which drives. This is typically handled through a tape  device sharing product.  GLYPH<SM590000> Storage management subsystem (SMS) constructs and constructs on the TS7700 must  match. If not, new constructs in SMS lead to new constructs in the TS7700 that are  created with default parameters. To avoid the uncontrolled buildup of constructs in the  TS7700, SMS should be controlled by a single department. GLYPH<SM590000> SMS constructs used by different workloads need to use unique names when the TS7700  behavior is expected to be different. This enables each unique application’s behavior to be  tuned within the TS7700. If the behavior is common across all shared workloads, the  same construct names can be used. GLYPH<SM590000> Ensure that the single defined set of constructs within the TS7700 are configured with a  behavior that is acceptable to all users. If not, different constructs must be used for  those customers. GLYPH<SM590000> Control of the TS7700 Management Interfaces (MIs), TS3500 GUI, and TS4500 GUI must  be allowed only to a single department that controls the entire environment. Control must  not be given to a single customer.  GLYPH<SM590000> Review the IBM RACF statements for the  Devserv  and  Library  commands on all LPARs.  These commands must be protected. In a multiple-client environment, the use of Library  commands must be restricted. When independent sysplexes are involved, the device ranges and corresponding volume  ranges can be further protected from cross-sysplex access through the SDAC feature.  When device partitioning is used, consider assigning the same number of devices per cluster  per sysplex in a grid configuration so that the availability for a given sysplex is equal across all  connected clusters. Override policies set in the TS7700 apply to the whole environment and cannot be enabled or  disabled by an LPAR or client.  For more considerations, see the  Guide to Sharing and Partitioning IBM Tape Library Data ,  SG24-4409. Note:  Some parameters can be updated by the  Library Request  command. This  command changes the cluster behavior. This is not only valid for the LPAR where the  command was run, but for all LPARs that use this cluster. Ensure that only authorized personnel can use the  Library Request  command. If you share a library for multiple customers, establish regular performance and resource  usage monitoring. For more information, see 3.4, “Features and functions available only for  the TS7700T” on page 126. Note:  With APAR OA49373 (z/OS V2R1 and later), the individual IBM MVS LIBRARY  command functions (EJECT, REQUEST, DISPDRV, and so on) can be protected using a  security product such as RACF. This APAR adds security product resource-names for each  of the LIBRARY functions. 120  IBM TS7700 Release 5.0 Guide