Installation package name prefix changed from unv- to sb-.

Universal Products are bundled together into a single distributed unit referred to as a Universal Products Package.

Universal Agent 6.4.x for z/OS installation package is delivered as an DFDSS backup. This significantly reduces the number of files that need to be transferred during the installation process. A zip version of the installation package also is provided.

D-04266: FMID TUAG520 is not selected by SMP/E APPLY when upgrading a CSI with TUAG510 install.

D-02817: Upgrade from 3.x or 4.x did not allocate UAG model data set.

Universal Automation Center Agent (UAG) is installed as FMID TUAG510. UAG provides agent services for an Opswise Automation Center Controller, enabling it to schedule workload, transfer files, and monitor events on the agent system.
 
UAG replaces Universal Automation Center Registration Server (UAR), introduced in Stonebranch Solutions 4.3.0.
 

Universal Automation Center Registration Server (UAR) is installed as FMID TUAR430. UAR provides the ability to register the Universal Broker with Opswise Automation Center 1.6 and 1.7.

The Universal Broker and Universal Enterprise Controller STCs can now use user profiles with non-zero UID values instead of UID 0 as required in previous releases. See Converting STC User Profiles to a Non-Zero UID for details on how to convert the STC user profiles from UID 0 to a non-zero UID value.

UPI-589: SE37 ABEND occurs on the SMPWRK6 ddname in the UNVSMPE JCL procedure during APPLY processing. PTF PU35001 has an SMP/E HOLD with instructions on modifying the UNVSMPE JCL procedure to avoid the SE37 ABEND.

Product configuration files have been moved from SMP/E target libraries SUNVCONF and SUNVCOMP to non-SMP/E product libraries UNVCONF and UNVCOMP. The change allows for remote configuration capability of z/OS configuration members. Configuration members are delivered in the SMP/E SUNVSAMP library and copied to the appropriate library in an installation job.
 
All SMP/E target and distribution libraries have been changed from PDS to PDSEs. This includes the load libraries SUNVLOAD and AUNVLOAD. The installation upgrade jobs include steps to convert existing libraries to PDSE format.

DF03150: LMOD elements UCMSCPST, UCMSS000 and UCMSR000 were not defined correctly. Their JCLIN did not account for implicitly defined modules used in the CSSLIB. This fix updates their JCLIN and adds a DDDEF for CSSLIB.

Package size has increased significantly as the Universal Broker and Server components are now included as FMIDs. Product SMP/E target library SUNVLOAD and SMP/E distribution library AUNVLOAD space allocation should be increased to meet the new space requirements. Additionally, SMP/E SMPLTS and SMPPTS data sets and SMPTLIB DDDEF space requirements have increased.

Products are packaged in the new Universal Products package. Starting with Universal Products 2.2.0, SMP/E target and distribution libraries are now shared between all products in order to make maintenance and administration easier.
 
Product target and distribution data set names have changed. All products in the Universal Products package use UNV as the three character product identifier. As such, the last qualifier of the target libraries start with SUNV and the last qualifier of the distribution libraries start with AUNV.

Start with Universal Command 2.1.0, the SMP/E target and distribution libraries SUCMNLS, AUCMNLS, SUCMCONF, and AUCMCONF have changed their record format from variable block to fixed block.

Starting with Universal Command 1.2.0, the SMP/E target and distribution library names have changed. The product name qualifier has been changed to the three-character product identifier, and the version, release, modification qualifier (V1R1M0) has been removed. The changes comply with the IBM naming conventions for SMP/E libraries. Also, the absence of the version qualifier will make future upgrades much simpler and trouble-free.

UPI-588: SMP/E distribution library AUNVHBIN was incorrectly allocated with record format undefined in the 3.2.0.0 package. A new distribution library AUNVHBN2 must be allocated and a DDDEF defined. PTF PU42001 has an SMP/E HOLD with instructions on how to allocate and define the DDDEF for AUNVHBN2.
 
UPI-590: Maintenance JCL members UNVMTRCV, UNVMTAPL and UNVMTACC in the INSTALL library do not specify the six USS FMIDs to be received, applied and accepted. The list of FMIDs specified in the FORFMID parameter in each job needs to have the following USS FMIDs included: UUNV320, UUBR320, UUCM320, UUDM320, UUEM320, and UUTL320. An example of the FORFMID parameter with a complete list of z/OS and USS FMIDs follows: FORFMID(TUNV320,TUTL320,TUBR320,TUCM320,TUEC320,TUDM320,TUXD320,TUSD320,TUSP320,TUEM320,UUNV320,UUBR320,UUCM320,UUDM320,UUEM320,UUTL320).

Universal Products for z/OS USS 3.2.0 was the first release where USS components were packaged as an SMP/E installation. Prior versions were installed with a product installation script. There is no automatic upgrade path to 3.2.0. Any previously installed version must be manually un-installed.
 
If the 3.2.0 version will be installed in the same directories as the previous version, the previous version must be un-installed before the 3.2.0 version is installed. If the 3.2.0 version will not be installed in the same directories, the previous version can be un-installed after the 3.2.0 version is installed.
 
To un-install a previous version, simply remove all z/OS UNIX file system product directories. Refer to the previous version's Installation Guide for a list of product directories.
 
Product configuration files have been moved from the /etc/universal directory to the non-SMP/E product library UNVCONF. The change allows for remote configuration capability of z/OS USS configuration members. Configuration members are delivered in the SMP/E SUNVSAMP library and copied to the appropriate library in an installation job.

DF02871: Readme file incorrectly referred to starting the ubrokerd daemon.

Starting with Universal Products 3.1.0, the Universal Broker and Servers are no longer provided in the USS package. The Universal Broker and Servers are now part of the z/OS SMP/E installation.

B-03882: Add Opswise Controller Command Line Interface (CLI) program as an optionally installed component.
 
B-04014: Add support for Broker user domain accounts during installation.
 

D-0300: New Broker will not start if trace_directory in ubroker.conf points to directory removed during 32- to 64-bit crossgrade.

Universal Command Agent for SOA added.

DF03398: Deselecting server component products during an upgrade does not remove the component definitions resulting in component start errors.
 
DF03489: If upgrading Universal Command and Universal Command Server is not currently installed, an error occurs trying to move the server component database.
 
DF03599: The ./UcmdMgr, ./UcmdSrv and ./Ueld installation directories were defined with too restrictive ACL's preventing user accounts in the Power User group from running ucmd and ueld commands.

DF03119: Location dependent registry values (for example, NLS directory) were not updated to account for potentially different installation directories upon an upgrade.

B-02799: Add support for multiple, parallel installations and user mode installation method. (Not valid for MP-RAS.)
 
B-03712: Add support for user verification in unvinst for group membership assigned by Windows Active Directory.
 
B-03904: Add Opswise Controller Command Line Interface (CLI) program as an optionally installed component. (Not valid for MP-RAS.)

B-02851: Initial 5.1.0 delivery for z/Linux 64-bit.

D-02508: Solaris install package scripts unnecessarily stop ubrokerd processes running on all zones, not just the one zone on which the package is being installed. The faulty scripts are included in packages prior to 4.2.0.2. When these packages are uninstalled or upgraded, they will stop all ubrokerd processes.

Universal Command Agent for SOA added.

CR02373: Verify Linux installation script is running as root since rpm package installation requires root access.
 
DF02465: Linux installation script unvinst.sh did not set the exit code properly upon an rpm error.
 
DF02647: Linux installation log was written to /opt/universal directory instead of the current working directory.
 
DF02877: The set-userid-on-exec flag was unnecessarily set for some executable programs.
 
DF02904: Upgrading Universal Products for Linux from 3.1.0 to 3.1.1 did not start the ubrokerd daemon. This change will correct the problem for the next maintenance level, but not for this maintenance level.
 
DF02973: HP-UX output from swlist showed the umet UNV.umeexec version as blank.
 
DF02978: Upgrading Universal Products for Linux from 3.1.1.0 to 3.1.1.3 did not remove the 3.1.1.0 package. This change will correct the problem for the next maintenance level, but not for the application of this maintenance level.
 
DF03094: Add support for Solaris 10's zone configuration.
 
DF03113: Upgrading Universal Products for Linux from 3.1.0 to 3.1.1 does not update the inittab entry for the ubrokerd daemon. The 3.1.0 script is still called.
 
DF03115: All AIX files /etc/*.conf were moved to /etc/universal upon upgrade to 3.1.1.

DF03074: Installation of Universal Products for AIX 3.1.1.1 fails due to missing requisite UDM 3.1.1.0.

All configuration files (for example, ucmd.conf and ubroker.conf) are updated and not replaced. Local modifications to the configuration files are preserved.
 

 
With the AIX, HP-UX, Solaris, and Linux installs, the previous installation directories are removed when the native installer has detected that additional directories or files have not been added to the original installation directories. If they have been modified, the directories will remain; they can be reviewed and removed when desired by your Administrator.

Starting with Universal Command 2.2.0, the generic Universal Products for UNIX installation script is no longer used for AIX, HP-UX, Solaris, and Linux installs. The native operating system vendor-recommended packaging methods are used on these operating systems. All other UNIX operating systems continue to use the generic installation script.
 
All Universal Products now use the Filesystem Hierarchy Standard (FHS) 2.2 for product directory names and locations. This conforms to most vendor directory implementations. Consequently, the installation directory is /opt/universal, the variable files directory is /var/opt/universal, and the configuration files directory is /etc/universal.
 
Executable files from versions prior to Universal Command 2.2.0 (ucmd, uctl, uquery, umet, uencrypt) require manual removal from their default installation directory, /usr/local/bin. Previous releases of Universal Command copied executable programs to the /usr/local/bin directory by default.
 
The installation methods obtain the location where the configuration files for Universal Products are stored. Configuration files will be moved from their current location to the /etc/universal directory.

The IBM i package contains Universal Products components for Universal Command, Universal Broker, Universal Data Mover, and Universal Encrypt. Previously, the package contained only Universal Command.