Plan Your ATV Manager Implementation (ATV)

To plan the ATV Manager implementation in your area, consider the following:

1. Before building tests destined for production, decide how to share your master index file(s).
   • ATVs indexed by a master index can be hidden from view using Performance Test security settings on your ATVs.
   • Normal dataset security rules are enforced for ATV datasets.
2. Create one or more master indexes for your group.
   • Will individual users have their own vehicles for their own testing purposes?
     Users can create their own master indexes, if desired.
   • Will a group of software developers build their application unit test cases in a single ATV, leveraging each other’s test assets (test files, test programs, JCL, etc.) as much as possible?
     If so, create a master index this development group will use. At completion of the development project this ATV would become a regression vehicle for the newly developed application.
   • Is security an issue?
     You may find it optimal to create ATV master index files for very small groups of users or for each individual ATV to easily segregate access to vehicles.
   • How large are Master Index Files?
     Master index files can be quite small. They contain one record (approximately 100 bytes) for each ATV created.
   • What permissions need to be set for ATV creators and users?
     Users who will be creating vehicles must have ALTER access to the master index file. Users who will work within a vehicle only need read access to the master index file.
   • How do I give individual users access to more than one index?
     If an individual needs to access more than one index, simply set up multiple profiles, each one addressing a different master index.