We also defined four minidisks to be used as the source drives for the IBM 

Dynamic Infrastructure for mySAP cloning process. They have the same naming 

convention as above except they begin with the number 1 instead of 0 (1C01, 

1C02, 1C03, 1C04). The drives are also coded for access 

MR

.

To minimize the amount of disk utilized for this project, the SAP specific file 

systems for this dialog instance are also contained within these four disk drives 

that hold the standard Linux operating system.

Example 34   SAPCM directory entry

USER SAPCM XXXXXXXX 512M 1024M G 

   PROFILE LINDFLT 

   CLASS G 

   STORAGE 512M 

   MAXSTORAGE 2047M 

   IPL C02 

   IUCV ALLOW 

   MACHINE ESA 

   CONSOLE 0009 3215 T 

   SPOOL 000C 2540 READER * 

   SPOOL 000D 2540 PUNCH A 

   SPOOL 000E 1403 A 

   LINK MAINT 0190 0190 RR 

   LINK MAINT 019D 019D RR 

   LINK MAINT 019E 019E RR 

   IPL CMS 

   MACHINE ESA 

   NICDEF C200 TYPE QDIO LAN SYSTEM LAN1 MACID 010000 

*  0C01 IS SWAP 

*  0C02 IS /BOOT 

*  0C03 IS / (ROOT) 

*  0C04 IS / (ROOT) 

   MDISK 0191 3390 1001 20 515U1R MR 

   MDISK 1C01 3390 1 3338 DK8227 MR 

   MDISK 1C02 3390 1 400 DK8228 MR 

   MDISK 1C03 3390 1 3338 DK8236 MR 

   MDISK 1C04 3390 1 3338 DK8237 MR 

We wrote and installed the bash script to enable automatic modification of 

system HOSTNAME and TCP/IP address based on the name of the VM Guest. 

Note that this will occur only once, at first load time, due to the logic in the script. 

Additional customization is possible in this script and other boot scripts, as well 

as with the workflows provided by the IBM Dynamic Infrastructure for mySAP 

automation package. If we had had more time, we would have also looked into 

the ability to use the scripts mentioned in 

IBM Dynamic Infrastructure Enterprise 

50 

Dynamic Provisioning of SAP Environments using IBM DI for mySAP and Tivoli Provisioning