Your configuration may vary from this setup and may require additional 

resources. 

We have configured and started the SNMP daemon on this system. This in effect 

ensures that the SNMP daemon is installed and autostarted on each of the 

dynamically provisioned clones without any additional work. 

We configured a static virtual network address for our network adapter on this 

system as evidenced by the NICDEF statement in Example 32. 

Example 32   SAPDI directory entry

USER SAPDI XXXXXXXX 512M 1024M G 

PROFILE IBMDFLT 

  SPOOL 000C 2540 READER * 

  SPOOL 000D 2540 PUNCH A 

  SPOOL 000E 1403 A 

  CONSOLE 009 3215 T 

  LINK MAINT 0190 0190 RR 

  LINK MAINT 019D 019D RR 

  LINK MAINT 019E 019E RR 

  LINK MAINT 0402 0402 RR 

  LINK MAINT 0401 0401 RR 

  LINK MAINT 0405 0405 RR 

   IPL CMS 

   MACHINE ESA 

   NICDEF C200 TYPE QDIO LAN SYSTEM LAN1 MACID 009999 

*  0201 IS SWAP 3

*  0202 IS /BOOT 3

*  0203 IS / (ROOT) 3

*  0204 IS / (BOOT) 

   MDISK 0191 3390 1021 20 515U1R MR 

   MDISK 0C01 3390 1 3338 DK8223 MR 

   MDISK 0C02 3390 1 400 DK8224 MR 

   MDISK 0C03 3390 1 3338 DK8225 MR 

   MDISK 0C04 3390 1 3338 DK8226 MR 

Disk drive layout for SAPDI

The SAP Dialog Instance was installed as a normal SAP installation. The VM 

user direct entry depicted in Example 32 shows that we defined one VM minidisk 

for the guest 191 A disk, and four disk drives to hold the Linux file system and the 

SAP file system. Access to additional data was accomplished by mounting 

required disk drives from the SAPCI instance via NFS. 

The first Linux on zSeries disk is 0C01, and it is assigned as the swap partition. 

Disk 0C02 is assigned to /boot. Disks 0C03 and 0C04 are assigned to /root. This 

makes up the base Linux file systems needed to start Linux.

48 

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