IBM Virtual Machine Facility/370: Planning and System Generation Guide 2
Page356(356 of 522)
CP SYSTEM RESIDENCE WORK AREA CPGEN'S 191 Figure 35. System Support Plan A Virtual for Updating VM/370 -- ..... (' 195 '- 1 ....... --.",· I RSCS I SYSTEM DISK I I (RSCS 191 I I LINKED I l AS 195) J ....... ---' CMS SOURCE AND MACROS CIV\S TEST NUCLEUS -----..,. ( 195 '- 1 ...... --..",- 1 IPCS I 1 SYSTEM I I (IPCS 191 I I LINKED I l AS 195) ,) ...... _-..". Part 5. Updating 325
A Virtual Machine for Updating VM/370 Accessing Disks When you are using the VM/370 procedures to apply updates to system modules, update file identifiers may be duplicated on more than one disk; there may be updates that are located in several different places. You should always be sure that you have the correct disks accessed, and that you have accessed them with an appropriate search order. You may find it convenient to create EXEC procedures that perform the links and accesses necessary to perform a particular update. For example to update a CP module, from files located on MAINT's 191 and 294, your EXEC procedure might look like the following: ACCESS 191 A ACCESS 294 B/A ACCESS 394 CIA This search order ensures that if a control file or auxiliary control tha the 191 ?QU i on the 191 is used. When updates are made to RSCS the 191 disks provided for these virtual machines can be linked to and accessed in read/write status, for example link rscs 191 195 w wpass access 195 a 326 IBM VM/370 Planning and System Generation Guide