|
IBM United States
Software Announcement 200-355 October 3, 2000 IBM System Automation for OS/390 Version 2 Release 1 Automates Parallel Sysplex Applications
At a GlanceSystem Automation for OS/390 Version 2.1 (SA OS/390) can help customers with single OS/390 or z/OS systems and Parallel Sysplex clusters to:
For ordering, contact: Your IBM representative, an IBM Business Partner, or IBM Americas Call Centers at 800-IBM-CALL (Reference: LE001). OverviewThe unique and rich functions of System Automation for OS/390® (SA OS/390) V2.1 can ease z/OS and OS/390 management, reduce costs, and increase application availability. SA OS/390 automates I/O, processor, and system operations and includes "canned" automation for IMS™, CICS®, Tivoli® OPC, and DB2®. Its focus is on Parallel Sysplex® automation, including multi- and single-system configurations, and on integration with Tivoli enterprise solutions, like the Tivoli Enterprise Console® (TEC). With the new manager/agent design, it is now possible to automate Parallel Sysplex applications by virtually removing system boundaries for automation. Parallel Sysplex Application Automation A Parallel Sysplex application can be automated as a whole, no matter how many resources it consists of and where they are. Resources can have complex dependencies, can be started as required, and can be moved to other systems. Simpler Operations through Goal-Driven Automation The automation manager decides when and where resources need to be made available or unavailable using its awareness of status, dependencies, and location of all resources and prioritized operator requests and policy goals specified by the automation administrator. This goal-driven automation greatly simplifies operations: operators just request what they want, and SA OS/390 takes care of any dependencies and resolution of affected or even conflicting goals. Reduction of Complexity with Groups Sysplex-wide grouping of resources and definition of aggregate or business applications can greatly reduce the complexity of automation definition and operations. Groups free operators from knowing the various pieces of the application. The Graphical User Interface (GUI) The system operations GUI is based on Tivoli NetView® for OS/390. The easy to implement, flexible GUI displays comprehensive system and application information including dependencies and offers point-and-shoot operation with easy-to-use context sensitive command menus. The I/O operations GUI is based on OS/390 HCM V2R9 to achieve maximum I/O configuration integration. Key Prerequisites
DescriptionThe main goal of System Automation for OS/390 (SA OS/390) V2.1 is to make a Parallel Sysplex cluster no more difficult to operate or manage than a large single system. The previous version (1.3) offered unique sysplex automation functions like enterprise-wide single point of control, sysplex-wide single system image, and the Parallel Sysplex Operation Center. Version 2.1 includes all this and much more. To automate Parallel Sysplex applications, new concepts are required to handle cross-system dependencies, reduce complexity, increase availability, ease operations, and model your configuration (refer to the Supplemental Information for details). SA OS/390 V2.1 introduces these required new concepts and makes automation of true Parallel Sysplex applications a reality by offering:
Elements of the automation engine have been separated in SA OS/390 2.1. Those that observe, react, and take action remain within the NetView address space. This portion is known as the automation agent and must be present on every system to be automated. The coordinating, decision-making, and controlling elements are grouped into a single new address space known as the automation manager. It is loaded with a model of all the automated resources defined across the entire Parallel Sysplex cluster. The automation manager communicates with the automation agents on each system via XCF (Cross-System Coupling Facility) and MQSeries for OS/390 V5.2 shared queues. It receives updates about the status of resources in its automation model and sends orders to the agents when various conditions within the model are encountered.
The real beauty of this design is that multiple systems can be automated
from a shared automation policy that is maintained in a central location.
For the first time, a true single S/390® automation instance is
possible.
Group and ConquerFor SA OS/390 V2.1, a group is a collection of resources that can be distributed within a Parallel Sysplex cluster. A group can be a part of any dependency or other group. Resources can be members of multiple groups and are referred to by a sysplex- or system-wide unique name. Exploiting groups is beneficial in many ways:
Powerful Dependency SupportResources can have complex dependencies of different kinds in and outside of an application. SA OS/390 V2.1 gives you the power to define these dependencies, so that applications always get what they need, are started in the right order as quickly as possible, and are shut down fast without interference. Thus definitions for resource dependencies can involve:
Goal-Driven AutomationIn SA OS/390 V2.1, the emphasis has also switched from purely command-driven automation to goal-driven automation. Automation programmers now define the default behavior of the systems and application components in terms of dependencies, triggering conditions, and scheduled requests. The automation manager works to keep systems in line with these goals and prioritized operator requests by using its awareness of status, dependencies, and location of all resources to decide what resources need to be made available or unavailable, when, and where. The number of checks and decisions it has to make can be very high. A human simply can't do the same as fast and reliably as the automation manager.
Goal-driven automation greatly simplifies operations. Operators just say
what they want, and automation takes care of any dependencies and
resolution of affected or even conflicting goals. Sysplex-wide
automation also can remove the need for specifying extra configurations
for backup purposes. Instead, cross-system dependencies and server and
system goals can be used to decide which backup system is to be chosen.
Graphical User InterfacesThe system operations GUI for SA OS/390 2.1 is based on the platform-independent NetView Management Console of Tivoli NetView for OS/390. It displays comprehensive system and application information, including dependencies, and offers point-and-shoot operation with easy-to-use, context-sensitive command menus. Problem management functions allow resource marking to indicate to other operators that a problem is being handled. Exceptions can be created dynamically out of NetView messages and can be added to the graphical interface for visual correlation.
The I/O operations GUI of SA OS/390 is based on OS/390 Hardware
Configuration Manager (HCM) V2R9. New functions in OS/390 HCM V2R9
provide visual displays of the I/O operations status for the active S/390
I/O configuration. HCM now cooperates with the SA OS/390 I/O operations
component to display color-coded status information and active switch
paths directly on the existing HCM configuration diagram. OS/390
operators also can retrieve detailed node element information and issue
I/O operations connectivity commands while working at the HCM
workstation. These enhancements provide powerful new tools for fast and
effective problem resolution.
Year 2000
This product is Year 2000 ready. When used in accordance with its
associated documentation, it is capable of correctly processing,
providing, and/or receiving date data within and between the twentieth
and twenty-first centuries, provided that all products (for example,
hardware, software, and firmware) used with the product properly exchange
accurate date data with it.
Euro CurrencyThis program is not impacted by euro currency. Product PositioningWith System Automation for OS/390, Version 2 Release 1, IBM continues to deliver OS/390 systems management products that can help you increase your competitiveness by increasing your business application availability and by reducing operations and systems management costs. Its unique enterprise and Parallel Sysplex support helps you to reduce complexity and to increase manageability. SA OS/390 V2.1 can be a part of your enterprise-wide systems management solution because it exploits Tivoli's OS/390 event integration and also can provide data for Tivoli Business Systems Manager. SA OS/390 V2.1 integrates and extends the function of three established licensed programs: Automated Operations Control/MVS (AOC/MVS), Enterprise Systems CONnection (ESCON®) Manager, and Target System Control Facility (TSCF). Such integration also allows for simpler and more consistent installation, customization, maintenance, and automation. SA OS/390 lets you reconfigure a processor's partitions, perform power-on reset, IML processors, IPL operating systems (even automatically), investigate and respond to I/O configuration errors, (re)start and stop applications, and monitor resources. SA OS/390 has a broad coverage of the resources of the Parallel Sysplex cluster, providing you with a wealth of information on those resources, a rich set of control functions, and means to access all those functions through user interfaces as well as automation. SA OS/390 V2.1 contains important capabilities to help in the management of Parallel Sysplex clusters but is also valuable if you have not yet implemented a Parallel Sysplex cluster. Hardware and Software Support ServicesSmoothStart™/Installation ServicesIBM Installation Services are provided for System Automation for OS/390 by IBM Global Services or your IBM Business Partner at an additional cost. For additional information, contact your IBM representative and ask for Installation Services. Reference InformationRefer to:
Trademarks
Conceptual OverviewSA OS/390® 2.1 presents a new and advanced approach for automating the resources of your enterprise to ensure comfortable resource maintenance and high availability of systems and applications. Key aspects of the new design are:
In SA OS/390 2.1, you must define all automation policies using the customization dialog, thus creating a policy database, and then use the appropriate functions of the customization dialog to build the automation configuration (that is, the system operations control files). Because the processing of automation is distributed between a sysplex automation manager and its automation agents on the systems (and so are the various system operations control files), it is absolutely necessary to build these files in one coherent process. SA OS/390 checks the consistency of the automation information stored on the automation manager and the automation agents. You can consider this process as a sysplex-wide, consistent automation configuration refresh. Application move refers to the process of stopping an active set of resources and starting an alternative set in a coordinated fashion. The move functions that you can specify against a group are:
Automation ConceptsIn SA OS/390, the automation function is split up:
You define the resources that you want to automate with SA OS/390 using the customization dialog. Thus the automation manager contains a model of all of the automated resources within the sysplex. The automation agents are the automation manager's eyes and arms. They feed the automation manager with status information and perform the actions that the automation manager tells them to. The automation manager is the brain of automation. It does all of the decision making that involves interaction between one or more resources. The automation manager provides sysplex-wide automation. So its main purpose is to provide one central point of bookkeeping of all resources within a sysplex, that is, the automation manager knows:
According to the available information, the automation manager makes decisions and instructs the corresponding automation agent where the resource is located to put the resource into the desired state. The automation manager knows five different statuses from each of the resources:
Decision-making is done by the automation manager with the help of
so-called "goals." Goals are either defined by the automation programmer
who defines permanent automation policy using the customization dialog,
or created interactively by operators who issue commands to define goals.
Goal-Driven AutomationA basic concept of SA OS/390 is to distinguish between the desired state of a resource, which is either AVAILABLE or UNAVAILABLE, and (broadly speaking) its actual state. The desired state, which is also called the automation goal, can be different from the actual state; a resource whose desired state is to be running (AVAILABLE), can actually be down. SA OS/390 always tries to keep the actual state in line with the desired state, but sometimes this is not possible. SA OS/390 is called goal driven because all requests that can be made to it from the outside refer to the desired state of the target resource. When an operator passes a start request for a resource to SA OS/390, what he or she does in fact require is to set the desired state of the resource to AVAILABLE. It is up to SA OS/390 to decide whether (1) this is at all possible and, if so, whether (2) the actual state can be modified accordingly:
A request is persistent until it is either processed, overridden, or revoked. A command in earlier releases was either successfully processed immediately or unsuccessfully rejected. If a resource is started by an operator outside of SA OS/390, but its SA OS/390 goal is defined as being unavailable, then it is stopped again by SA OS/390.
One of the main tasks of system automation when starting or stopping a
resource is to consider the dependencies that exist between the resource
to be started or stopped and other resources. Certain resources can be
started only when certain other resources are already running (start
dependencies), and certain resources can be stopped only when certain
other resources are already down (stop dependencies). Such dependencies
can be specified in the policy database. The only restriction is that
the dependent and the supporting resource must belong to the same sysplex
(they need not reside on the same system). SA OS/390 takes dependencies
into account when it is requested to start or to stop a resource. By
default, it will try to start or stop all resources on which the target
resource of the request directly or indirectly depends.
Application Groups
Modern applications often consist of more than one component, and these
different components can be distributed among different systems. SA
OS/390 provides the possibility to combine different components of an
application on one or more systems within a sysplex into an application
group. This allows you to start and stop a complex application by a
single command, and to integrate it into automation processes as a whole.
Feature Integration
CICS®/IMS™ Automation is integrated into SA OS/390. The feature code
is automatically installed with the base code and resides in the same set
of libraries. CICS and IMS regions must be defined in the policy
database as subsystems by linking CICS/IMS applications to systems in
order to be available to CICS/IMS Automation. Triggers and service
periods for CICS/IMS regions are also defined as for any other
application.
NMCThe NetView Management Console (NMC) is part of the Tivoli® NetView for OS/390 product and is used for monitoring and controlling network resources. As SA OS/390 is based on NetView, it also exploits the graphical capabilities of the NMC. You can monitor and control your whole enterprise by means of NMC. It is also possible to monitor your enterprise from a single workstation (single point of control). This holds for system operations as well as for processor operations. The communication between SA OS/390 and the NMC is maintained by the SA OS/390 topology manager. An SA OS/390 topology agent on each target system retrieves the enterprise data from the automation manager. The SA OS/390 topology manager on the focal point provides the information into RODM. GMFHS takes care that the information in RODM gets converted to graphical information on the NMC workstation. The following sketches the main tasks of the SA OS/390 topology manager for system operations. For processor operations, the mode of operation is similar. The retrieved information includes all resources, for example, applications, application groups, systems, and groups of systems, with their mutual dependencies and relationships. The SA OS/390 topology manager stores these resources together with their dependency information within RODM.
The SA OS/390 topology manager calls BLDVIEWS to build the views that are
necessary for these resources to be displayed on the NMC. The
definitions for the views must be supplied by the users. On the NMC
workstation, you can see the graphical visualization of what is automated
in system operations and processor operations. For system operations,
the automation manager knows about the configuration of the sysplex and
the resources running in it. For processor operations, it is the
processor operations focal point that knows about the processor
operations configuration. In order to issue a command against a
resource, click on this resource with the right mouse button to open a
context menu. This menu contains only those system operations or
processor operations commands that are applicable to the respective
resource. Some SA OS/390 commands are not provided because they cannot
be reasonably connected to a resource. When the state of the resource is
affected by the command, the state information (event component of the
label, color of the icon) is actualized on the NMC.
Topology
The automation manager is introduced as a separate address space. An
installation needs one primary automation manager and may have one or
more backups. The automation manager is loaded with a model of the
sysplex when it initializes. It then communicates with the automation
agents on each system, receiving updates to the status of the resources
in its model, and sending orders out to the agents as various conditions
within the model become satisfied. For reasons of high availability, SA
OS/390 offers the concept of the primary and secondary automation manager
(PAM and SAM), where the SAM can take over the work of the PAM without
loss of any information or without any requests being processed twice.
Secondary automation managers are able to take over the function whenever
a primary automation manager fails. In a sysplex, the automation agents
communicate with each other using XCF. Automation managers communicate
with the automation agents using MQSeries®.
Processor Operations PCSA OS/390 V2.1 is the last release providing the processor operations PC component including the SA workstation with its ProcOps LAN Passthru function. This PC is used for remote operator console access and for the system console of pre-CMOS processors. Operator console access is now being provided by:
Processor operations continues to provide console automation for
processors supporting the Operations Command Facility (OCF).
More InformationFor more details about System Automation for OS/390, visit: For more details about MQSeries, visit: Note: MQSeries offers a PRPQ at 15% of the SA OS/390 price titled "Restricted MQSeries for OS/390 V2 for use with other nominated IBM products." For more details about Tivoli NetView for OS/390, visit: Technical InformationSpecified Operating EnvironmentHardware RequirementsThe target system can run in any hardware environment that supports the required software. IBM System Automation for OS/390 Processor Operations: IBM System Automation for OS/390 processor operations supports monitoring and control functions for both screen-oriented processors (9121, 9021, 3090™, 308x, and 4381) and S/390® microprocessor-based processors (such as 9672, 9674, 2003, or 3000) and all CMOS processors that can be operated via Operations Command Facility (OCF). IBM System Automation for OS/390 processor operations supports logical partitioning of any of these processors that also support logical partitioning. IBM System Automation for OS/390 System Operations: The IBM System Automation for OS/390 system operations base program can run on any processor supported by NetView. IBM System Automation for OS/390 I/O Operations: The IBM System Automation for OS/390 I/O operations base program can run on:
ESCON Multiple Image Facility (EMIF) is required for enhanced status
support.
Software RequirementsFunctional Requisites: One of the following:
OS/390 Base Elements or Optional Features:
Other Program Products:
Workstation Requisites:
Compatibility: System Automation for OS/390, Version 2.1 is upwardly compatible with System Automation for OS/390, Version 1.3 (5645-005). The single point of control is supported in this mixed environment. Even Automation Control Files (ACF) from AOC/MVS can be migrated. Policy databases back to AOC/MVS, Release 2, can be converted automatically. The generated backlevel Automation Control File (ACF) can be used by:
The recommended migration starts with the automatic conversion of your policy database and its usage also for backlevel systems. You can then implement SA OS/390 V2.1 on one system and expand it system by system without having two policy databases, thus avoiding integrity and productivity issues. The gateway processing, including SDF and SENDCMD, which now is INGSEND, is also compatible back to AOC/MVS. For easy migration, SA OS/390 can interoperate with ESCON Manager. Also the ESCON Manager API and commands are still supported. For more information refer to Appendix E of System Automation for OS/390 V2R1 Planning and Installation (SC33-7038). Performance Considerations: Compiling the REXX CLISTs, which are part of the product, will improve performance. The REXX compiler must be ordered separately.
Description Requirement
Improve flexibility of monitors REQ00004117
Provide the ability for flexible REQ00010234
start commands REQ00010234_1
REQ00012500
Provide GROUP definitions similar REQ00041071
to CICS/IMS features. Enhance REQ00041071_1
shutdown command and provide
startup command. Applications
must be stopped and started
individually this is time
intensive for the operators.
Many applications need to be
manipulated in groups. The group
status is an aggregate of its
members' status.
Add VFY=YES/NO to SETSTATE REQ00045827
command
Enterprise reports to not contain REQ00048732
any automation policy
Reduce AOC/MVS initialization time REQ00049916
One-time JES2 cold start capability REQ00054119
(Note: Can be accomplished by
means of the flexible start
command support.)
Save last BUILDF run-time options REQ00054839
for next time
Enhance the sysplex automation REQ00056611
aspects of AOC/MVS product REQ00056611_1
Multiple parent support REQ00059277
(more than six parents)
Introduce option to avoid REQ00060188
expiration of AOC Gateway operator
password
Provide closer ARM integration REQ00061437
(policy sharing)
Enhancement to ACF command to REQ00061831
show date/time that the current REQ00062438
control file is built and loaded
Audit trail for SHUTSYS command REQ00062378
REQ00062378_1
Description Requirement
Alternate/Exceptional startup REQ00062435
Want a form of semi-automation to REQ00062244
AOF603D like AON
Ability to dynamically move REQ00064415
applications and groups from one REQ00073541
system to another system in the
sysplex.
Need to have the ability to REQ00064416
automate resources that have
cross-system relationships and
requirements.
Startup/shutdown groups of REQ00064417
applications.
Ability to define, startup, and
shutdown application in groups.
Fewer definitions are needed, such
as timers, when managing groups.
Enhance BUILDF process to allow REQ00064418
build of ACF for a system or
sysplex (partially)
Make SA OS/390 smart enough REQ00064428
to do a cold start after a
partial BUILDF
Permit CONSOLE and AUTH parms REQ00064641
on AOFRGCON invocation
ACFname and SYSname should REQ00064782
be the same
Nonalphabetical startup of children REQ00064963
More robust ACF command for 7/24 REQ00065074
operations
Dynamic Dump dataset &EHKVAR1 REQ00065947
IEA611I ...
ACF reload should interpret REQ00066831
AOFACFMP member
Queue OPC requests while reloading REQ00066833
ACF
Shorter navigation path through REQ00066836
installation dialogs (partially)
Provide programming interface to REQ00067240
change start type of subsystem
ACF MEMBER= should be REQ00068237
nondisruptive
Extend SA OS/390 command length REQ00069057
fields in the cust. dialogs REQ00069064
Provide user option from AOC REQ00070229
command (AOFPOPER panel)
Timer length restriction in policy REQ00070390
must be removed
Description Requirement
SA OS/390 should "out of the box" REQ00070469
better exploit NGMF --
BUILDVIEWS
Make NGMF a usable operational REQ00070472
interface for command control
Need fast system shutdown REQ00070475
(Note: Can be accomplished by
means of the grouping support or
by exploiting shutdown dependency
"MakeUnavailable.")
AOCTRACE needs to be able to list REQ00070503
current traced REXX clists.
IPL only commands REQ00070640
SETSTATE command: Enhance REQ00071107
message when task is already
in the state requested
AOFRSD0G -- Group JES2 resources REQ00071223
on message AOF570
Allow GMT parm for TIMER REQ00071252
definitions
No console names on customization REQ00071432
panels for sysplex
AOFRSCMD requires update to obtain REQ00071451
SUBSSPARM task globals
Enhance support for parent/child REQ00071534
relationship to restart an abended
child that is normally started by
its parent.
Externalize Common Global variable REQ00071541
AOFSTARTTYP
Improve BUILD Function for RODM REQ00071559
SETSTATE to AUTODOWN and ENDED REQ00071631
Provide function to determine the REQ00071807
release of the AOC/IMS feature
Allow INITSTART REQ00071958
AUTO=N,EXIST=xxxx in the
customization dialog
ISSUECMD/ISSUEREP to pass REQ00072017
information to a subsequent
called clist
Incorrect shutoptions parent must REQ00072331
be detected at build time
Path complete message from REQ00072395
autotable via ISSUECMD to called
REXX clist
ISPF Dialogs Batch Build option for REQ00073005
RODM Loader File
ACFPLOAD does not honor REQ00073800
objectclass so we need delete
ability
Description Requirement
DISPFLGS needs wildcard ability REQ00074275
and a tune up
Provide LOCATE command in cust. REQ00075250
dialog selection panels
Enhancements to AOFTREE REQ00075835
AOCCICS need the ability to select REQ022400210
a domain, ...
Planning InformationCustomer Responsibilities: For an easy to use and understand automation guide, refer to Redbook SG24-5515, Automation Using Tivoli NetView OS/390 V1R3 and System Automation OS/390 V1R3 . Direct Customer Support: Direct customer support is provided by IBM Support Line. This fee service can enhance your productivity by providing voice and electronic access into the IBM support organization. IBM Support Line will help answer questions pertaining to usage, how to, and suspected software defects for eligible products. Installation and technical support is provided by IBM Global Services. For more information on services, call 800-IBM-4YOU (426-4968). Packaging: System Automation for OS/390, Version 2.1 will be shipped on one SMP/E installable tape which makes up the basic package. The tape includes:
System Integrity
IBM will accept APARs where the installation of this licensed program
causes an exposure to the system integrity of OS/390. This program is
intended to run unauthorized. OS/390 System Integrity Applies: Yes.
Security, Auditability, and ControlThe announced program uses the security and auditability features you have selected in Tivoli Netview for OS/390. This is either inside Tivoli Netview itself or in the SAF you have implemented. You can then use security and auditability features of Tivoli Netview for OS/390 to protect System Automation for OS/390 commands. The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities. Customer FinancingIBM Global Financing offers attractive financing to credit-qualified commercial and government customers and Business Partners in more than 40 countries around the world. IBM Global Financing is provided by the IBM Credit Corporation in the United States. Offerings, rates, terms, and availability may vary by country. Contact your local IBM Global Financing organization. Country organizations are listed on the Web at: Ordering InformationThe following publications are available now. To order, contact your IBM representative.
Order
Title Number
System Automation for OS/390 V2R1 GC33-7036
General Information
System Automation for OS/390 V2R1 SC33-7037
Licensed Program Specification
System Automation for OS/390 V2R1 SC33-7038
Planning and Installation
System Automation for OS/390 V2R1 SC33-7035
Customization and Programming
System Automation for OS/390 V2R1 SC33-7039
Defining Automation Policy
System Automation for OS/390 V2R1 SC33-7040
User's Guide
System Automation for OS/390 V2R1 SC33-7041
Messages and Codes
System Automation for OS/390 V2R1 SC33-7042
Operator's Commands
System Automation for OS/390 V2R1 SC33-7043
Programmer's Reference
System Automation for OS/390 V2R1 GI10-9748
Program Directory
System Automation for OS/390 V2R1 GI10-9757
Memo to Licensees
System Automation for OS/390 V2R1 SC33-7044
CICS Automation Programmer's
Reference and Operator's Guide
System Automation for OS/390 V2R1 SC33-7045
IMS Automation Programmer's
Reference and Operator's Guide
System Automation for OS/390 V2R1 SC33-7046
OPC Automation Programmer's
Reference and Operator's Guide
The above documentation is also contained in the OS/390 CKit which can be
ordered via SK2T-6700.
New LicenseesOrders for new licenses can be placed now. Shipment will not occur before the availability date. New users of System Automation for OS/390 Version 2.1 should specify:
Type Model
5645 006
Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the feature number for "PSLC Base, 1 MSU" for a monthly license charge (MLC). When a new release is available, prior releases will no longer be available. Entry Support License (ESL): To order an ESL, specify the program number, feature number 9001 for asset registration, and the applicable ESL one-time charge (OTC) feature number. Also specify the feature number of the desired distribution medium.
ESL
One-Time
Charge
Program Feature
Number Description Number
5645-006 System Automation 0018
for OS/390
ESL machines can be determined by referring to the IBM Entry End User/390 Attachment (Z125-4379). Parallel Sysplex® License Charge (PSLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the PSLC Base feature. If applicable, specify the PSLC Level A, B, C, and D features and quantity. If there is more than one program copy in a Parallel Sysplex, the charge for all copies is associated to one license by specifying the applicable PSLC feature numbers and quantity represented by the sum of the Service Units in Millions (MSUs) in your Parallel Sysplex. For all other program copies, specify the PSLC No-Charge (NC) Identifier feature on the licenses. Also, specify the feature number of the desired distribution medium.
Machine PSLC PSLC Basic License
MSU Feature MLC Feature
Capacity Number Description
1 0001 PSLC Base, 1 MSU
2 0002 PSLC Base, 2 MSUs
3 0003 PSLC Base, 3 MSUs
4 -- 45 0004 PSLC Level A, 1 MSU
0005 PSLC Level A, 42 MSUs
46 -- 175 0006 PSLC Level B, 1 MSU
0007 PSLC Level B, 10 MSUs
0008 PSLC Level B, 50 MSUs
176 -- 315 0009 PSLC Level C, 1 MSU
0010 PSLC Level C, 10 MSUs
0011 PSLC Level C, 50 MSUs
316 or more 0012 PSLC Level D, 1 MSU
0013 PSLC Level D, 50 MSUs
NA 0014 PSLC NC Identifier
Example 1: For a single machine with 11 MSUs, the PSLC features would be:
Example 2: For two machines in a Parallel Sysplex, which have an aggregation of 60 MSUs, the PSLC features would be:
Variable Workload License Charge (VWLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the WLC Base feature. If applicable, specify the WLC Level 1, 2, 3, and 4 features with the appropriate quantity. Also, specify the feature number of the desired distribution medium.
VWLC Aggregation:
When z/OS is installed on two or more IBM Whether there is only one license or more than one license of the program in the sysplex, the charge for all licenses is associated to the "aggregation license" by specifying the applicable WLC feature numbers and quantity represented by the sum of the MSUs (millions of service units) in the sysplex. The "aggregation license" is an additional program license which is ordered and serialized, although there is no shipment associated with it. For the actual licenses, the charge is reflected as $0.00 by specifying the applicable "registration" VWLC feature numbers and the quantity equal to the MSUs of that license running on the designated machine.
Usage Pricing
WLC WLC Basic License
MSU Feature Monthly License Charge
Capacity Number Feature Description
0 -- 45 0460 WLC Base, 45 MSUs
46 -- 175 0480 WLC Level 1, 1 MSU
176 -- 315 3704 WLC Level 2, 1 MSU
316 -- 575 3706 WLC Level 3, 1 MSU
3708 WLC Level 3, 50 MSUs
576 or more 3980 WLC Level 4, 1 MSU
0020 WLC Level 4, 50 MSUs
WLC Reg WLC Basic License
Feature No-Charge Registration
MSU Capacity Number Feature Description
0 -- 1 3702 WLC Base, 1 MSU Reg
2 -- 175 3703 WLC L1, 1 MSU Reg
176 -- 315 3705 WLC L2, 1 MSU Reg
316 -- 575 3707 WLC L3, 1 MSU Reg
3709 WLC L3, 50 MSUs Reg
576 or more 0019 WLC L4, 1 MSU Reg
0021 WLC L4, 50 MSUs Reg
Example 1: For a single machine with the program running at 220 MSUs, the Variable WLC features would be:
Example 2: If there are two machines in a sysplex, and a program is running on machine #1 at 190 MSUs and on machine #2 at 140 MSUs, the VWLC feature numbers and quantities to be ordered would be:
Growth Opportunity License Charge (GOLC): To order GOLC software, specify the program number, feature number 9001 for asset registration, and the GOLC monthly charge feature number from the table below. Also, specify the feature number for the desired distribution medium.
GOLC
GOLC Feature
Category Number
H30 0015
H50 0016
H70 0017
Single Version Charging: To elect single version charging, the customer must notify IBM and identify the prior program and replacement program and the designated machine the programs are operating on. Basic Machine-Readable Material
Feature
Environment Number Distribution Medium
OS/390 5801 6250-bpi Distribution Tape
OS/390 5802 3480 Cartridge Uncompressed
OS/390 6236 4-mm Data Cartridge;
Modified; 2 GB
Customization Options: Select the appropriate feature numbers to customize your order to specify the delivery options desired. These features can be specified on the initial or MES orders. Example: If publications are not desired for the initial order, specify feature number 3470 to ship media only. For future updates, specify feature number 3480 to ship media updates only. If, in the future, publication updates are required, order an MES to remove feature number 3480; then, the publications will ship with the next release of the program.
Feature
Description Number
Initial Shipments
Serial Number Only (suppresses shipment 3444
of media and documentation)
Ship Media Only (suppresses initial 3470
shipment of documentation)
Feature
Description Number
Ship Documentation Only (suppresses 3471
initial shipment of media)
Entry Server Offering 3490
Satellite Electronic Delivery 3450
Update Shipments
Ship Media Updates Only (suppresses 3480
update shipment of documentation)
Ship Documentation Only (suppresses 3481
update shipment of media)
Suppress Updates (suppresses update 3482
shipment of media and documentation)
Expedite Shipments
Local IBM Office Expedite 3445
(for IBM use only)
Customer Expedite Process Charge 3446
($30 charge for each product)
Expedite shipments will be processed to receive 72-hour delivery from the time IBM Software Delivery and Fulfillment (SDF) receives the order. SDF will then ship the order via overnight air transportation. Unlicensed Documentation: A memo, a program directory, and one copy of the following publications are supplied automatically with the basic machine-readable material:
Order
Title Number
System Automation for OS/390 V2R1 GC33-7036
General Information
System Automation for OS/390 V2R1 SC33-7037
Licensed Program Specification
System Automation for OS/390 V2R1 SC33-7038
Planning and Installation
System Automation for OS/390 V2R1 SC33-7039
Defining Automation Policy
System Automation for OS/390 V2R1 SC33-7042
Operator's Commands
System Automation for OS/390 V2R1 GI10-9748
Program Directory
System Automation for OS/390 V2R1 GI10-9757
Memo to Licensees
Displayable Softcopy Publications: System Automation for OS/390, Version 2.1 manuals are offered in displayable softcopy form. All unlicensed manuals are included except for:
The displayable manuals are part of the basic machine-readable material. The files are shipped on CD-ROM. These displayable manuals can be used with the BookManager® READ licensed programs in any of the supported environments. Terms and conditions for use of the machine-readable files are shipped with the files. Subsequent updates (technical newsletters or revisions between releases) to the publications shipped with the product will be distributed to the user of record for as long as a license for this software remains in effect. A separate publication order or subscription is not needed. Terms and ConditionsLicensing: IBM Customer Agreement Workload License Charges Apply: Yes, refer to the Attachment for zSeries Workload License Charges (Z125-6323). Indexed Monthly License Charge (IMLC) Applies: No Educational Allowance Available: Yes, a 15% education allowance applies to qualified education institution customers. Products Eligible for Single Version Charging
Replaced Program Replacement Program Program Program Program Program Number Name Number Name 5645-005 SA OS/390 V1 5645-006 SA OS/390 V2
Licensed Program Materials Availability
Testing Period: Two months (basic license only) Satisfaction Guarantee: Two months for basic licenses Starts: 10 days after IBM ships, or on the day a non-DSLO additional license is authorized
Support Center Applies: Yes
Access available through
the IBM Support Center
Available until Discontinued: 12 months' written notice
APAR Mailing Address: IBM Entwicklung GMBH
c/o Rita Berg (secretary)
ATT. C/T programmer
Dept. 3151 Bldg. 71032-14
Schoenaicherstrasse 220
71032 Boeblingen
Germany
Order Now
Use Priority/Reference Code: LE001
Phone: 800-IBM-CALL
Fax: 800-2IBM-FAX
Internet: ibm_direct@us.ibm.com
Mail: IBM Atlanta Sales Center
Dept. LE001
P.O. Box 2690
Atlanta, GA 30301-2690
You can also contact your local IBM Business Partner or IBM representative. To identify them, call 800-IBM-4YOU.
Note: Shipments will begin after the planned availability date.
Trademarks
|
zSeries machines comprising a sysplex, VWLC aggregation applies to z/OS
and the S/390 software programs that have VWLC.