Wiki Markup | |
---|---|
Panel | |
|
Introduction
Opswise Universal Agent 5.2.0
...
consists
...
of
...
a
...
family
...
of
...
components
...
that
...
address
...
distributed
...
systems
...
management
...
and
...
automation.
...
The
...
components
...
are
...
packaged
...
together
...
as
...
product
...
installation
...
packages.
...
Product
...
installation
...
packages
...
are
...
provided
...
for
...
a
...
variety
...
of
...
operating
...
systems
...
and
...
hardware.
...
Stonebranch
...
provides
...
product
...
maintenance
...
in
...
the
...
form
...
of
...
updated
...
product
...
installation
...
packages
...
that
...
contained
...
the
...
latest
...
maintenance
...
levels
...
of
...
product
...
components.
...
These
...
pages
...
list
...
the
...
product
...
installation
...
package
...
and
...
component
...
maintenance
...
history
...
for
...
Opswise
...
Universal
...
Agent
...
5.2.0.
...
Product Packaging
Agent components are bundled together into product installation packages, referred to simply as packages in these pages. Each package is identified with a package version number and each component within a package is identified with a component version number.
Each package and component maintenance level is identified with a version number (see Versioning, below). The component maintenance level is incremented whenever a new component is made available that contains defect fixes or feature enhancements. A package maintenance level is incremented when a product component within the package changes or the package installation changes.
Package maintenance levels are not necessarily made available for all platforms. Package maintenance may be released for a subset of supported platforms. For example, Opswise Universal Agent 5.2.0 for z/OS and UNIX may be at maintenance level 5.2.0.1,
...
but
...
Opswise
...
Universal
...
Agent
...
5.2.0
...
for
...
Windows
...
may
...
be
...
at
...
5.2.0.0.
...
Stonebranch
...
changes
...
product
...
version,
...
release,
...
or
...
modification
...
identifiers
...
at
...
its
...
discretion
...
when
...
it
...
deems
...
an
...
appropriate
...
number
...
of
...
enhancements
...
or
...
capabilities
...
have
...
been
...
introduced
...
to
...
warrant
...
the
...
change.
...
Anchor | ||||
---|---|---|---|---|
|
Package version numbers are comprised of four numeric identifiers: version, release, modification level, and maintenance level.
For example, for Opswise Universal Agent 5.2.0.1:
...
- 5
...
- =
...
- Version
...
- 5
...
- 2
...
- =
...
- Release
...
- 2
...
- 0
...
- =
...
- Modification
...
- Level
...
- 0
...
- 1
...
- =
...
- Maintenance
...
- Level
...
- 1
...
Product
...
component
...
version
...
numbers
...
are
...
similar
...
to
...
the
...
package
...
version
...
numbers.
...
Each
...
product
...
component
...
within
...
the
...
package
...
is
...
identified
...
with
...
the
...
same
...
version,
...
release,
...
and
...
modification
...
level
...
as
...
the
...
package,
...
and
...
with
...
a
...
maintenance
...
level
...
that
...
is
...
independent
...
of
...
the
...
maintenance
...
level
...
of
...
the
...
package
...
or
...
other
...
components
...
in
...
the
...
package.
...
For
...
example,
...
within
...
an
...
Opswise
...
Universal
...
Agent
...
5.2.0.1
...
package,
...
there
...
could
...
be
...
a
...
Universal
...
Command
...
5.2.0.0
...
component:
...
- 5
...
- =
...
- Version
...
- 5
...
- 2
...
- =
...
- Release
...
- 2
...
- 0
...
- =
...
- Modification
...
- Level
...
- 0
...
- 0
...
- =
...
- Maintenance
...
- Level
...
- 0
Packaging Methods
Packaging methods vary among platforms based on the installation conventions and vendor recommendations for the platform. The purpose of this section is to describe the packaging and distribution methods used for the Workload Automation package on its supported platforms.
z/OS | The Opswise Universal Agent 5.2.0 |
---|
...
package |
...
is |
...
an |
...
SMP/E |
...
install |
...
consisting |
...
of |
...
multiple |
...
FMIDs. |
...
The |
...
package |
...
is |
...
composed |
...
of |
...
a |
...
set |
...
of |
...
FMIDs |
...
for |
...
MVS |
...
components |
...
and |
...
a |
...
set |
...
of |
...
FMIDs |
...
for |
...
UNIX |
...
System |
...
Services |
...
(USS) |
...
components. |
...
The |
...
MVS |
...
components |
...
are |
...
required |
...
and |
...
the |
...
USS |
...
components |
...
are |
...
optional. |
...
| |||||||||
Windows | All packages are created with the InstallShield Windows packaging tool. The package is installed with Microsoft’s Windows Installer (file extension .msi). | ||||||||
---|---|---|---|---|---|---|---|---|---|
| There are two installation methods supported on UNIX platforms, both of which are initiated from a Stonebranch script:
|
...
IBM i | The package is an IBM i Licensed Program and installed with the IBM i RSTLICPGM command. By default, all product and dependent product identifiers are installed. | ||||||
---|---|---|---|---|---|---|---|
HP NonStop | On the HP NonStop platform, Universal Command 2.1.1 product is packaged by itself. No other products are included in the distribution file.
Product maintenance is packaged as an updated installation package. The installation process upgrades the current install to the latest product maintenance level. |
Maintenance Releases
For detailed information on the maintenance releases, including the initial release, for all Opswise Universal Agent 5.2.0 platforms and components, see All Maintenance Releases - Agent 5.2.0.