...
Step 1 | Stop the Universal Broker STC if it is running.
|
|---|
Step 2 | Change the user profile UBRUSR UID value to 5001 with the following command:
| Panel |
|---|
| Html bobswift |
|---|
<pre>
ALTUSER UBRUSR OMVS(UID(5001))
</pre>
|
|
|---|
Step 3 |
| Note |
|---|
| Some parts of this step are optional starting with Universal Agent 6.5.0.0. Running with access to all the profiles below is still supported in that release, but the only resource the Broker user must have READ access to is BPX.JOBNAME. Running without BPX.SUPERUSER and BPX.DAEMON access does limit the Universal Agent's feature set, but only as it applies to z/OS Unix group membership and configuring the Agent to switch user contexts without prior authentication. |
Permit the user profile UBRUSR READ access to the required resource profiles with the following commands:
| Panel |
|---|
html-bobswift |
|---|
<pre>
PE BPX.SUPERUSER CLASS(FACILITY) ID(UBRUSR) ACCESS(READ)
PE BPX.JOBNAME CLASS(FACILITY) ID(UBRUSR) ACCESS(READ)
SETR RACLIST(FACILITY) REFRESH
</pre>
|
The user profile UBRUSR should already have READ access to BPX.DAEMON in the FACILITY class based on Universal Broker installation requirements prior to 4.2.0. If UBRUSR does not have READ access to BPX.DAEMON, the following commands will permit appropriate access:
| Panel |
|---|
| Html bobswift |
|---|
<pre>
PE BPX.DAEMON CLASS(FACILITY) ID(UBRUSR) ACCESS(READ)
SETR RACLIST(FACILITY) REFRESH
</pre>
|
For detailed information regarding Universal Broker security requirements, see z/OS Configuration - Started Tasks. |
|---|
Step 4 | Universal Broker databases are maintained in USS HFS or zFS data sets. The database files have an owner attribute that is based on the UID value of the Universal Broker STC user profile. The database files, the root directory, and administration files must have their owner attribute changed from UID 0 to the new non-zero UID value 5001.
When running with UID 0 or with READ access to the BPX.SUPERUSER profile, the Universal Broker STC will dynamically mount the USS data sets in the /tmp directory. Assuming the USS data set names are UNV.UNVDB and UNV.UNVSPOOL, their mount point would be directory /tmp/UNV.UNVDB and /tmp/UNV.UNVSPOOL. If a different mount point must be used, its location can be changed with the MOUNT_POINT configuration option inside the &HLQ.UNV.UNVCONF(UBRCFG00) member. If necessary, adjust the commands below to the appropriate directory names.
If the Universal Broker STC has never run with UID 0 or with READ access to the BPX.SUPERUSER profile, the databases must be mounted manually as described in Universal Agent Database Configuration.
From the z/OS UNIX shell prompt, execute the following commands:
| Panel |
|---|
html-bobswift |
|---|
<pre>
su
cd /tmp/UNV.UNVDB
chown -R 5001 *
chown 5001 .
chown 5001 .inited
cd /tmp/UNV.UNVSPOOL
chown -R 5001 *
chown 5001 .
chown 5001 .inited
exit
</pre>
|
The first command, su, changes to the superuser ID. The user ID used to execute the above commands will need either a UID of 0 or READ access to the BPX.SUPERUSER profile in the FACILITY class. If the user ID has UID 0, the su command is not necessary.
The .inited file must exist in each directory and must be owned by the Universal Broker user. If the Broker has not run in this environment, it will be necessary to manually create this file, so its ownership can be set as instructed above. There are no content requirements for this file, so an empty file will suffice. |
|---|
Step 5 | Universal Broker spawns Universal Agent server components via external links that reside on the z/OS UNIX file system (USS). These links must point to names that match load modules installed into the SUNVLOAD load library.
UDM Manager also can spawn UCMD and USAP in response to an exec or execsap command, following the same external link approach used by Universal Broker. The Broker provides these links to UDM during registration.
If the Broker runs as UID 0 (or as a user with READ access to BPX.SUPERUSER), it will format and create each of these external links at start-up in the location specified by the TMP_DIRECTORY configuration option.
If the Broker does not run with superuser authority, each of these links must be created manually and their locations must be identified in the appropriate component definitions and configuration files.
To create external links for Universal Agent server components and have them recognized by Universal Broker: | Html bobswift |
|---|
<ul>
<li>
| Panel |
|---|
| Html bobswift |
|---|
<pre>
su
cd /tmp
ln -e UAGSRV ubroker.stc.uagsrv
ln -e UCMSRV ubroker.stc.ucmsrv
ln -e UCTSRV ubroker.stc.uctsrv
ln -e UDMSRV ubroker.stc.udmsrv
</pre> | html-bobswift |
The directory and name (for example, <code>ubrokerubroker.stc.
uagsrv</code>uagsrv)
can be any desired, but the link must point to the name of the load module in <code>&HLQ.UNV.
SUNVLOAD</code>.
<br><br>
If the SUNVLOAD.
If the TMP_DIRECTORY
| Html bobswift |
|---|
configuration option - defined inside <code> configuration option - defined inside &HLQ.UNV.UNVCONF(UBRCFG00) </code> - was changed from its default value of <code>/
tmp</code>tmp,
place the external links in the location specified by the mount point value.
<li> <code>UNVCOMP</code> <code>/tmp</code> with the configured -
/tmp with the configured tmp_directory
<ul>
<li>UAGSRV: Set - UAGSRV: Set start_command
<code>uagsrv</code>
<li>UCMSRV <code>ucmsrv</code>
<li>UCTSRV <code>uctsrv</code>
<li>UDMSRV <code>udmsrv</code>
</ul>
</ul>To create external links used by UDM to execute UCMD and USAP, execute the following z/OS Unix commands
| Panel |
|---|
html-bobswift |
|---|
<pre>
su
cd /tmp
ln -e UCMD ubroker.stc.ucmd
ln -e USAP ubroker.stc.usap
</pre> |
Update the UCMD_PATH and USAP_PATH Universal Broker configuration options in &HLQ.UNV.UNVCONF(UBRCFG00) to point to the absolute path of those links.
If you expect to stop components from Universal Broker using UCTL, create a link for it as well (for example, In -e UCTL ubroker.stc.uctl) and update the UCTL_PATH option in &HLQ.UNV.UNVCONF(UBRCFG00).
If you expect to launch started tasks (STCs) via UCMD using a COMMAND_TYPE value of stc or via the UDM exec stc= command, execute the following z/OS Unix commands to create an external link to the UCMD Server STC Command Processor, UCMSCPST.
| Panel |
|---|
| Html bobswift |
|---|
<pre>
su
cd /tmp
ln -e UCMSCPST ucmd.stc
</pre> |
Update the UCMSCPST_PATH UCMD Server configuration option in &HLQ.UNV.UNVCONF(UCSCFG00) to point to the absolute path of this new link. |
|---|
Step 6 | Start the Universal Broker STC. |
|---|
...
An ICH804I message issued by a Universal Server component may look like this:
| Panel |
|---|
html-bobswift |
|---|
<pre>
ICH408I USER(UBRTRP ) GROUP(UBRGRP ) NAME(####################)
BPX.SUPERUSER CL(FACILITY)
INSUFFICIENT ACCESS AUTHORITY
ACCESS INTENT(READ ) ACCESS ALLOWED(NONE )
</pre> |
In this instance, the Broker was running with account UBRTRP, which does not have READ access to the BPX.SUEPRUSER resource of the FACILITY RACF class.
...
Step 1 | Stop the UEC STC if it is running.
|
|---|
Step 2 | Change the user profile UECUSR UID value to 5002 with the following command:
| Panel |
|---|
| Html bobswift |
|---|
<pre>
ALTUSER UECUSR OMVS(UID(5002))
</pre>
|
|
|---|
Step 3 | Optional: Permit the user profile UECUSR READ access to the required resource profiles with the following commands:
| Panel |
|---|
| Html bobswift |
|---|
<pre>
PE BPX.SUPERUSER CLASS(FACILITY) ID(UECUSR) ACCESS(READ)
SETR RACLIST(FACILITY) REFRESH
</pre>
|
|
|---|
Step 4 | UEC databases are maintained in a USS HFS or zFS data set. The database files have an owner attribute that is based on the UID value of the UEC STC user profile. The database files, the root directory, and administration files must have their owner attribute changed from UID 0 to the new non-zero UID value 5002.
When running with UID 0 or with READ access to the BPX.SUPERUSER profile, the Universal Enterprise Controller STC will dynamically mount the USS data set in the /tmp directory. Assuming the USS data set name is UNV.UECDB, its mount point would be directory /tmp/UNV.UECDB. If a different mount point must be used, its location can be changed with the MOUNT_POINT configuration option inside the &HLQ.UNV.UNVCONF(UECCFG00) member. If necessary, adjust the following commands to reflect the correct mount point location.
If the UEC STC has never run with UID 0 or with READ access to the BPX.SUPERUSER profile, the databases must be mounted manually as described in Universal Agent Database Configuration.
From the z/OS UNIX shell prompt, execute the following commands:
| Panel |
|---|
html-bobswift |
|---|
<pre>
su
cd /tmp/UNV.UECDB
chown -R 5002 *
chown 5002 .
chown 5002 .inited
exit
</pre>
|
The first command, su, changes to the superuser ID. The user ID used to execute the above commands will need either a UID of 0 or READ access to the BPX.SUPERUSER profile in the FACILITY class. If the user ID has UID 0, the su command is not necessary.
The .inited file must exist in each directory and must be owned by the UEC user. If the UEC STC has not run in this environment, it will be necessary to manually create this file, so its ownership can be set as instructed above. There are no content requirements for this file, so an empty file will suffice. |
|---|
Step 5 | Start the UEC STC. |
|---|
...
