VM Systems Management Server settings
The VM Systems Management Server must be defined, configured, and active at
all times for the dynamic provisioning operations. The authorization control files
of the VM Systems Management Server must be customized.
Example 21 shows our VM Systems Management Server directory entry.
Example 21 VSMSERVE directory definition
USER VSMSERVE XXXXXXXX 32M 32M ABCDEFG
D8ONECMD FAIL
IPL CMS
IUCV ANY MSGLIMIT 255
MACHINE ESA
OPTION DIAG88 MAINTCCW LNKS LNKE
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
LINK MAINT 0193 0193 RR
LINK MAINT 0CF1 0CF1 MD
LINK MAINT 0CF2 0CF2 MD
LINK TCPMAINT 0591 0591 RR
LINK TCPMAINT 0592 0592 RR
MDISK 0191 3390 1818 025 515RES MR READ WRITE MULTIPLE
Authorization control files for the VM Systems Management API must be
customized to grant the administrative user (IDADM in our case) proper
authorization access to the VMAPI functions. These authorization control files
reside on the 191 minidisk of the VSMSERVE user ID and are named VMSERVE
AUTHLIST and VSMSERVE NAMELIST. The administrative user ID must to be
authorized to perform the following group of functions for
all
user IDs:
QUERY_FUNCTIONS
It also must be authorized to perform this group of functions for all user IDs
defined to be used during the provisioning operation (IDADM00X user IDs in our
case):
DM_CONTROL
DM_IMAGE_CONTROL
IMAGE_OPERATION
IMAGE_DEVICES
IMAGE_CONNECT
36
Dynamic Provisioning of SAP Environments using IBM DI for mySAP and Tivoli Provisioning
<
New Page 1
Web Hosting SSH