Using and Administering

Migration Considerations

This section describes some differences between LoadLeveler 1.3.0 and LoadLeveler 2.1.0. See the LoadLeveler Installation Memo for more information on migration.

Resource Manager Functions Now in LoadLeveler

The following functions were previously part of the Parallel System Support Programs (PSSP) Resource Manager and are now part of LoadLeveler.

Table 1. New LoadLeveler Functions Previously Part of the Resource Manager

Resource Manager Function	LoadLeveler Function
Support for pools	The pool_list keyword in the machine stanza.
Specifying batch, interactive, or general use for nodes	The machine_mode keyword in the machine stanza.
Enabling SP exclusive use accounting for parallel jobs	The sp_excluse_enable keyword in the machine stanza.
Controlling user logins	LoadLeveler does not directly interact with the Login Control Facility. LoadLeveler logs into nodes as root and switches to the user's ID. root is never blocked on a node.
Providing node and adapter information for SP nodes	The llextSDR extracts information from the SDR that you can use in administration file stanzas.
Requesting dedicated use of nodes	The node_usage keyword in the job command file.
Requesting dedicated use of adapters	The usage operand on the network keyword in the job command file.
Displaying job information with the jm_status -j command	The llq command.
Displaying pool information with the jm_status -P command	The llstatus -l command.

Also, the LoadLeveler rm_host keyword in the machine stanza is no longer needed.

Keywords Supported for Parallel Jobs

LoadLeveler 2.1.0 includes a new scheduler, the Backfill scheduler, in addition to the default scheduler which existed in LoadLeveler 1.3.0. See Table 4 for a list of which keywords associated with parallel jobs are supported by each scheduler.

Migrating Your Existing Adapter Requirements Statements

If you are running the Backfill scheduler with job_type=parallel, you should use the 2.1.0 network job command file keyword to request adapters. However, if you use the 1.3.0 Adapter requirement in a job command file, the requirement is converted to the 2.1.0 network statement. Only those requirement statements with one Adapter keyword and that use the "==" operator are converted; all other Adapter requirements are not allowed.

Table 2 shows how the network type value in an Adapter requirement statement is converted. The left column represents the network types you can request using the Adapter requirement. The right hand column represents the resulting network statement generated by LoadLeveler 2.1.0.

Table 2. How the Backfill Scheduler Handles the Adapter Requirement

Network Type Adapter Requirement	Resulting network Statement
hps_ip	css0,shared,IP
hps_user	css0,shared,US
ethernet	en0,shared,IP
fddi	fi0,shared,IP
tokenring	tr0,shared,IP
fcs	fcs0,shared,IP

Note that any adapter name in a resulting network statement must be specified in the administration file.

Changes in LoadLeveler Command Output

The following are changes in the output produced by LoadLeveler Version 2 Release 1 commands:

• The llq -l -x command output now includes task and node information for parallel jobs. For more information, see Results.

• The llstatus -l command output includes the following changes:

  • The order of the output fields displayed has changed.

  • The first and last line of output has changed.

  • Job classes are now grouped together and are followed by the number of class instances. For example, small(2) POE(3) refers to two small class jobs and three POE class jobs.

  • The Adapter line now contains expanded information.

  For more information, see Results.

Changes in the LoadLeveler Release Directory

The LoadLeveler release directory has changed as follows:

• /usr/lpp/LoadL/nfs is now /usr/lpp/LoadL/full.

• /usr/lpp/LoadL/nfs_so is now /usr/lpp/LoadL/so.

The LoadLeveler release directory is set by the RELEASE_DIR keyword in the sample LoadLeveler configuration file and the sample program Makefiles.

Changes in the GUI Resource File

The following new resources have been added to Xloadl, the GUI resource file:

• New resources ending in _label allow you to specify the titles of the columns on the Jobs and Machines windows.

• Additional resources ending in _len allow you to add new fields to the Jobs and Machines windows and to specify the size of these fields.

• New resources are available for "widgets," such as the Job Type cascading menu, and the Nodes, Network, and PVM buttons and windows.

For more information, see /usr/lpp/LoadL/full/lib/Xloadl, the GUI resource file.