The CA 1® Tape Management Scratch Pool Management feature allows you to protect defined ranges of tapes in the TMC by restricting nonspecific output access. Access can be resticted based on data set name, SMS Management Class name, creating job name, creating unit name, expiration date, temporary file status, or by specifying the pool name in the JCL.
Many applications require tapes with specific physical characteristics, such as tape length, quality of tape, reel size, type of container, and so on. Such requirements can be imposed by government agencies or internal business procedures or simply for operating convenience. The multiple scratch pool management capabilities of CA 1® Tape Management provide the necessary support to satisfy these requirements in a fully automated manner.
Each scratch pool can optionally be defined as a sub-pool that allows real-time stacking. While file stacking is common, real-time stacking is different. With real-time stacking, there is little control over what file sequence number or which volume within the scratch sub-pool the file is added to.
The READONLYnnnnn subpool definition is also allowed. If the first eight characters of the subpool name are READONLY (followed by any five characters), the tapes in that subpool can open for READ processing only. No output is allowed. A TMONSMxx rule should never point to a READONLYnnnnn subpool. Use this function when testing a peer-to-peer (grid) configuration of a virtual tape system and you do not want to allow any production tapes to be updated while at DR.
Note: Apart from READONLYnnnn subpooling, CA 1® Tape Management does not support scratch subpooling in an OAM managed robotic environment. If READONLYnnnnn is used with an OAM managed OAM robot, all tapes in the same category must be part of the same subpool.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|