Cache Magic/VM Magic Download Form

1. Unzip
   Unzip the download file using your favorite zip utility. The zip file contains the following files:

SDI CPXLOAD 
SDICFC TEXT
SDIPRODS EXEC 
SDIVDB TEXT
SDILNK TEXT
SDIDRVXA TEXT
SDIIOS TEXT
SDIISU TEXT

2. Upload
   Upload the extracted files to your mainframe using a terminal emulation program file transfer facility or FTP. The files are binary files. (Do not specify ASCII translation or CRLF for the transfers. The record type is fixed length with a logical record length of 80.)
   
3. Logon
   Logon to the VM/ESA maintenance machine (usually Maint) and IPL CMS.
   
4. Uninstall
   Uninstall any currently installed SDI products.
   
   1. Stop all caching (Cache Magic only)
      
      sdic disable all     (stops all automatic caches)
      sdic stop all (save  (stops all user defined caches)
      
   2. Remove any links to VM Magic virtual disks (VM Magic only)
      
   3. Determine the CPXLOAD identification number assigned to the SDI product by entering:
      
      query cpxload epname sdiios
      Loaded as identifier loadid
      ...
      File SDI CPXLOAD fm
      Ready; T=n.nn/n.nn hhmmmss
      
   4. Issue the CPXUNLOAD command.
      
      cpxunload id loadid synchronous
      
      Where:
      loadid is the CPXLOAD identification number.
      
      
5. Create a minidisk for the SDI files
   
   1. Create a minidisk for the SDI product code. SDI recommends that you add a userid to your directory exclusively for the SDI product code. The minidisk should be 1 cylinder or 400 FBA blocks in size. Use the following as a guide:
      USER SDIvmm NOLOG
      MDISK 191 devtype start number volid RR pr pw pm
      
   2. Update the current directory.
      directxa fn direct fm
      
   3. Format the minidisk.
      link SDIvmm 191 999 w pw
      format 999 z


6. Copy the uploaded files to the SDI minidisk
   Use the copyfile command to copy the uploaded files to the SDI minidisk.
   
   link SDIvmm 191 999 w pw
   access 999 z
   copyfile sdi* * a = = z
   
   
7. Load the SDI Software into Memory
   Load the SDI software into memory and attach it to CP. Ensure that the OPTION statement for the virtual machine CP directory entry includes OPTION LNKStabl. This is to allow the CPACCESS command to function correctly.
   
   cpaccess sdivmm 191 fm rr synchronous
   cpxload sdi cpxload control sdicpint
   cprelease fm
   enable command sdimagic
   enable command sdilevel
   enable command sdidasd (VM Magic only)
   enable command sdidasd (Cache Magic only)
   sdimagic license wwww-xxxx-yyyy-zzzz
   
   Where:
   

   vmm	is the SDI product release level
   fm	is an unused CP filemode. Issue "QUERY CPDISKS" to determine what CP filemodes are available.
   wwww-xxxx-yyyy-zzzz	is the product license code supplied by SDI.



8. Update the IPL Process
   Update your IPL process so that the SDI software is loaded each time you IPL your system. Ensure that the OPTION statement for the AUTOLOG1 virtual machine CP directory entry includes OPTION LNKStabl. Then add the following statements to your AUTOLOG1 profile exec:
   
   cpaccess sdivmm 191 fm rr synchronous
   cpxload sdi cpxload control sdicpint
   cprelease fm
   enable command sdimagic
   enable command sdilevel
   enable command sdidasd (VM Magic only)
   enable command sdicache (Cache Magic only)
   sdimagic license wwww-xxxx-yyyy-zzzz
   
   Where:
   

   vmm	is the SDI product level
   fm	is an unused CP filemode. Issue "QUERY CPDISKS" to determine what CP filemodes are available.
   wwww-xxxx-yyyy-zzzz	is the product license code supplied by SDI.