Currently, IBM i runs Workload Automation 5.1.1. These pages provide information for that version.

Workload Automation for IBM i - Customization

(For information on applying product licenses to installed Workload Automation 5 for IBM i components, see IBM i Installation - Licensing.)

Modify the IPL Start-up Program

Modify the IPL Start-up Program so that the Universal Broker subsystem (UNVUBR511) is started at IPL time.

The subsystem start command is:

The IPL Start-up program name is displayed by:

Refer to the AS/400 publication AS/400e series: Basic System Operation, Administration, and Problem Handling for complete details on modifying the IPL Start-up program.

Multiple-Installation Implementation

Workload Automation for IBM i provides the ability to install, configure, and test a new release prior to placing it into production.

You can keep an older release available during this initial production phase in case problems occur. This allows you to manually merge component files, configuration files, and exit programs without having to save copies of those files and programs prior to installation of the newer release.

When initially installed, the names of the Workload Automation commands in the QSYS library are tagged with the *v*ersion / *r*elease / *m*odification number, 511. This renaming allows currently installed pre-5.1.1 releases to remain fully functional without modifying production code until pre-production testing is completed.

When you are ready to bring the newly installed release into production, run the UCHGRLS (Change Release Tag) Program to untag the 5.1.1 command names and tag the pre-5.1.1 command names with that pre-5.1.1 release number.

After running UCHGRLS, check the job log for errors because missing objects do not result in program termination. There will generally be one or more missing commands flagged; only those commands included with the installed release present a problem if they are missing.

Universal Broker

For the Universal Broker, both a job queue (*JOBQ) and a class (*CLS) were added; they are both named UBROKER and are located in the product library, UNVPRD511.

The UNVUBR511 subsystem and Workload Automation job descriptions use the UNVPRD511 / UBROKER class and job queue instead of the QGPL / QBATCH class and job queue.

To revert back to the QGPL / QBATCH class:

Step 1	Invoke the CHGRTGE command using SBSD(UNVPRD511 / UNVUBR511), SEQNBR(10), and CLS(QGPL / QBATCH).
Step 2	Invoke the CHGPJE command using SBSD(UNVPRD511 / UNVUBR511), PGM(QSYS / QP0ZSPWP), JOB(UCMSINIT), and CLS(QGPL / QBATCH).
Step 3	Invoke the CHGPJE command using SBSD(UNVPRD511 / UNVUBR511), PGM(QSYS / QP0ZSPWT), JOB(UNVSRV), and CLS(QGPL / QBATCH).
Step 4	Use the RMVJOBQE command with SBSD(UNVPRD511 / UNVUBR511) and JOBQ(UNVPRD511 / UBROKER) to remove the job queue entry from the UNVUBR511 subsystem.

To revert back to the QGPL/QBATCH job queue, invoke the CHGJOBD command specifying JOBQ(QGPL / QBATCH) for the UNVPRD511 / UBROKER, UNVPRD511 / UCMSINIT, and UNVPRD511 / UNVSRV job descriptions.

Active Jobs

Whereas the QGPL / QBATCH job queue entry for the QBASE subsystem limits the maximum active jobs to only six (by default), the UNVUBR511 / UBROKER job queue has no limit. Thus, it allows many additional Workload Automation jobs to run in parallel. Using the new settings, the Universal Broker RUNNING_MAX configuration option controls the maximum number of components allowed to run simultaneously.

For consistency with earlier releases, the initial settings of the UNVUBR511 class is the same as the QGPL / QBATCH class. Using the new class and job description, you may better tune your systems without affecting those jobs running under the default QGPL / QBATCH class and job description.

Universal Broker Customization

Configuration

Configuration options for Universal Broker are stored in configuration file UNVCONF(UBROKER), in product library UNVPRD511.

See the Universal Broker 7.2.x Reference Guide for details on configuring Universal Broker.

The file can be edited using the Source Entry Utility (SEU).

System Initialization

Universal Broker runs as a job, UBROKER, in the Universal Broker subsystem (UNVUBR511) located in product library UNVPRD511.

To start Universal Broker, enter the following on the command line: STRSBS UNVPRD511/UNVUBR511. There are two sets of pre-start jobs initiated: UNVSRV and UCMSINIT:

UNVSRV is the pre-start job for any of the Workload Automation servers.
UCMSINIT is the pre-start job for the UCMSINIT program.

The Universal Command Server initiates UCMSINIT, which initiates and monitors the command originated from either the Universal Command Manager or the exec command under the Universal Data Mover Manager.

Universal Command Manager Customization

Configuration

Configuration options for Universal Command Manager are stored in its configuration file, member UNVCONF(UCMD) in product library UNVPRD511.

See the Universal Command 7.2.x Reference Guide for details on configuring Universal Command Manager.

The file can be edited using the Source Entry Utility (SEU).

Universal Command Server Customization

Configuration

Configuration options for Universal Command Server are stored in configuration file UNVCONF(UCMDS), in product library UNVPRD511.

See the Universal Command 7.2.x Reference Guide for details on configuring Universal Command Server.

Universal Command Server runs as a component managed by Universal Broker. It provides a component definition file that Universal Broker uses to start the Server and establish its runtime environment. The component definition file, UNVCOMP(UCMD), is located in product library UNVPRD511.

Universal Command Server uses the Universal Access Control List (UACL) configuration file as a level of product security. The UACL file is located in UNVCONF(UACL), in product library UNVPRD511. See the Universal Agent Security for information on how Universal Command Server utilizes the UACL file.

The file can be edited using the Source Entry Utility (SEU).

Universal Control Manager Customization

Configuration

Configuration options for Universal Control Manager are stored in configuration file UNVCONF(UCTL), in product library UNVPRD511.

See the Universal Agent Utilities 7.2.x Reference Guide for details on configuring Universal Control Manager.

The file can be edited using the Source Entry Utility (SEU).

Universal Control Server Customization

Configuration

Configuration options for Universal Control Server are stored in configuration file UNVCONF(UCTLS), in product library UNVPRD511.

See the Universal Agent Utilities 7.2.x Reference Guide for details on configuring Universal Control Server.

Universal Control Server runs as a component managed by Universal Broker. It provides a component definition file that Universal Broker uses to start the Server and establish its runtime environment. Component definition file UNVCOMP(UCTL) is located in library UNVPRD511 by default

Universal Control Server uses the Universal Access Control List (UACL) configuration file as a level of product security. The UACL file UNVCONF(UACL) is located in product library UNVPRD511. See the Universal Agent Security for information on how Universal Control Server utilizes the UACL file.

The file can be edited using the Source Entry Utility (SEU).

Universal Data Mover Manager Customization

Configuration

Configuration options for Universal Data Mover Manager are stored in its configuration file, member UNVCONF(UDM) in product library UNVPRD511.

See the Universal Data Mover 7.2.x Reference Guide for details on configuring Universal Data Mover Manager.

The file can be edited using the Source Entry Utility (SEU).

Universal Data Mover Server Customization

Configuration

Configuration options for Universal Data Mover Server are stored in configuration file UNVCONF(UDMS), in product library UNVPRD511.

See the Universal Data Mover 7.2.x Reference Guide for details on configuring Universal Data Mover Server.

Universal Data Mover Server runs as a component managed by Universal Broker. It provides a component definition file that Universal Broker uses to start the Server and establish its runtime environment. Component definition file UNVCOMP(UDM) is located in product library UNVPRD511.

Universal Data Mover Server uses the Universal Access Control List (UACL) configuration file as a level of product security. The UACL file is located in UNVCONF(UACL) in product library UNVPRD511. See the Universal Agent Security for information on how Universal Data Mover Server utilizes the UACL file.

The file can be edited using the Source Entry Utility (SEU).

Universal Query Customization

Configuration

Configuration options for Universal Query are stored in configuration file UNVCONF(UQRY), in product library*UNVPRD511*.

See the Universal Agent Utilities 7.2.x Reference Guide for details on configuring Universal Query.

The file can be edited using the Source Entry Utility (SEU).

National Language Customization

The default IBM i CCSID value (QCCSID) is pre-set to 65535 or *HEX, both of which mean: Do not interpret data unless specifically required. You can set QCCSID to a value consistent with your country CCSID.

However, Workload Automation configuration files contain non-invariant characters (such as #, which marks the start of a comment). Some CCSIDs, such as 278, result in the translation of these characters into characters that the Workload Automation software cannot recognize. As a result, Workload Automation components, including Universal Broker, fail to start.

To resolve this, either:

Use a Universal Broker job CCSID of 65535. Both the Workload Automation configuration files and the internal Universal Broker code are CCSID 037-based. Start Universal Broker and check the job log output to verify the correct translation.
Use 037 as the CCSID for the Universal Broker user profile (UNVUBR511). This sets the CCSID of the associated Universal Broker job to 037. The job's 37 CCSID forces compatibility with the configuration files and the internal program CCSID value of 037, which is consistent with standard IBM i development practice.

The CRTPGM command sets the program CCSID to 65535, which allows the program to inherit the job CCSID. Writing to the job log should result in the correct translation of characters between the job CCSID and the system CCSID.

Browser not supported