Previous Topic: 1.4 Files OverviewNext Topic: 2. PLANNING


1.5 Product Prerequisites


 The CA MICS Space Collector Option runs on any operating
 system from MVS/ESA (OS/390 V2R10) through z/OS V1R13.
 Both the standard and the HFS VCC collection programs must
 run from an APF-authorized library in order to perform
 certain authorized system functions, such as opening system
 catalogs, writing records to SMF, and running as
 non-swappable.

 Since the CA MICS Space Collector Option runs multiple
 subtasks for efficiency, it may require a larger region size
 than your standard default. The number of subtasks can be
 user-controlled to allow flexibility in environments that are
 virtual storage constrained.

 The VCC HFS collection batch job must be authorized to read
 all of the files created within a Hierarchical File System.
 To do this, VCC uses UID 0. Ensure that your External
 Security Product allows VCC to switch to UID 0, and has read
 access to the Hierarchical File Systems. In order to
 function properly, VCC HFS collection must have authority to
 access the BPX.SUPERUSER resource in the FACILITY class.
 This will allow the required SETUID(0) to function
 successfully.