Using and Administering

lldcegrpmaint - LoadLeveler DCE group Maintenance Utility

Purpose

This command extracts the names of the DCE groups associated with the DCE_ADMIN_GROUP and DCE_SERVICES_GROUP keywords from the LoadLeveler configuration file. It will create these groups if they do not already exist. This command also adds the DCE principal names of the LoadLeveler daemons to the group specified by the DCE_SERVICES-GROUP keyword.

Syntax

lldcegrpmaint [-?] [-H] [-v] config_pathname admin_pathname

Flags

-?
Provides a short usage message.

-H
Provides extended help information.

-v
Outputs the name of the command, release number, service level, service level date, and operating system used to build the command.

config_pathname
Pathname of the LoadLeveler configuration file.

admin_pathname
Pathname of the LoadLeveler administration file.

Description

The lldcegrpmaint command is available to DCE administrators who have logged in to DCE as cell_admin. The command performs the following functions:

  1. Extracts the names of the DCE groups associated with the DCE_ADMIN_GROUP and DCE_SERVICES_GROUP keywords from the LoadLeveler global configuration file. These groups are known generically as the LoadL-admin group and the LoadL-services group. The LoadL-admin group contains the DCE principal names of users who have administrative authority for LoadLeveler. The LoadL-services group contains the DCE principal names of all the LoadLeveler daemons which run in the current LoadLeveler cluster. The lldcegrpmaint command will create these groups if they do not already exist.
  2. Populates the LoadL-services group with the DCE principal names of the LoadLeveler daemons. These names are derived from the DCE hostnames associated with the dce_host_name keyword in the LoadLeveler administration file, and LoadLeveler related information defined in the /usr/lpp/ssp/config/spsec_defaults file. In order for this step to work, the machine stanzas in the administration file must contain the DCE hostnames of the all the machines in the LoadLeveler cluster. The llextSDR command can be used to retrieve the DCE hostnames.

Before running the lldcegrpmaint command, a DCE administrator should make sure that basic DCE Security setup steps have been performed. If SMIT panels are used, the steps under the "RS/6000 SP Security" panel should be performed in sequence (from top to bottom) to properly update the DCE Registry. This measure is important for LoadLeveler, and for any other function that exploits DCE Security on the SP. For the purposes of the lldcegrpmaint command, the important actions are: (1) "Create dcehostnames" and (2) "Configure SP Trusted Services to use DCE Authentication."

Note: lldcegrpmaint does not add the names associated with the LOADL_ADMIN keyword in the configuration file to the LoadL-admin group. It is the administrator's responsibility to add appropriate DCE principals to this group.

Examples

In this example, it is assumed that the DCE cell name is /.../c163.ppd.pok.ibm.com and that LoadLeveler configuration and administration files are named /u/loadl/LoadL_config and /u/loadl/LoadL_admin, respectively, and contain the statements: 

 DCE_ENABLEMENT=TRUE
 DCE_ADMIN_GROUP=LoadL-admin4
 DCE_SERVICES_GROUP=LoadL-services4

and 

 c163n02.ppd.pok.ibm.com:  type = machine central_manager = true
 machine_mode = general
 schedd_host = true
 dce_host_name = c163n02.ppd.pok.ibm.com
 
 c163n03.ppd.pok.ibm.com:  type = machine central_manager = false
 machine_mode = general
 schedd_host = true
 dce_host_name = c163n03.ppd.pok.ibm.com

It is also assumed that there is no override specification in the file /spdata/sys1/spsec/spsec_overrides and that the file /usr/lpp/ssp/config/spsec_defaults contains the following: 

 SERVICE:LoadL/Master:kw:root:system
 SERVICE:LoadL/Negotiator:kw:root:system
 SERVICE:LoadL/Schedd:kw:root:system
 SERVICE:LoadL/Startd:kw:root:system
 SERVICE:LoadL/Starter:kw:root:system
 SERVICE:LoadL/Kbdd:kw:root:system
 SERVICE:LoadL/GSmonitor:kw:root:system

Executing the command: 

 lldcegrpmaint /u/loadl/LoadL_config /u/loadl/LoadL_admin

results in:

  1. The creation of the DCE groups: 
    /.../c163.ppd.pok.ibm.com/LoadL-admin4
/.../c163.ppd.pok.ibm.com/LoadL-services4
  2. The population of the DCE group LoadL-services4 with the DCE principals: 
    /.../c163.ppd.pok.ibm.com/LoadL/c163n02.ppd.pok.ibm.com/Master
/.../c163.ppd.pok.ibm.com/LoadL/c163n02.ppd.pok.ibm.com/Negotiator
/.../c163.ppd.pok.ibm.com/LoadL/c163n02.ppd.pok.ibm.com/Schedd
/.../c163.ppd.pok.ibm.com/LoadL/c163n02.ppd.pok.ibm.com/Startd
/.../c163.ppd.pok.ibm.com/LoadL/c163n02.ppd.pok.ibm.com/Starter
/.../c163.ppd.pok.ibm.com/LoadL/c163n02.ppd.pok.ibm.com/Kbdd
/.../c163.ppd.pok.ibm.com/LoadL/c163n02.ppd.pok.ibm.com/GSmonitor
/.../c163.ppd.pok.ibm.com/LoadL/c163n02.ppd.pok.ibm.com/Master
/.../c163.ppd.pok.ibm.com/LoadL/c163n03.ppd.pok.ibm.com/Negotiator
/.../c163.ppd.pok.ibm.com/LoadL/c163n03.ppd.pok.ibm.com/Schedd
/.../c163.ppd.pok.ibm.com/LoadL/c163n03.ppd.pok.ibm.com/Startd
/.../c163.ppd.pok.ibm.com/LoadL/c163n03.ppd.pok.ibm.com/Starter
/.../c163.ppd.pok.ibm.com/LoadL/c163n03.ppd.pok.ibm.com/Kbdd
/.../c163.ppd.pok.ibm.com/LoadL/c163n03.ppd.pok.ibm.com/GSmonitor

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]