|
IBM United States
Software Announcement 202-189 August 13, 2002 IBM System Automation for OS/390 V2.2 Provides Comprehensive Parallel Sysplex Management and Automation Functions
(Corrected on September 3, 2002)
The Technical Information section is revised.
At a GlanceSystem Automation for OS/390 (SA OS/390), a Project eLiza foundation, provides policy-based self-healing:
For ordering, contact: Your IBM representative, an IBM Business Partner, or IBM Americas Call Centers at 800-IBM-CALL (Reference: LE001). OverviewSystem Automation for OS/390® (SA OS/390) plays an important role in building the end-to-end automation of Project eLiza. The unique functions of SA OS/390 V2.2 can help customers with single z/OS™ or OS/390 systems and Parallel Sysplex® clusters to ease management, help reduce costs, and increase application availability. SA OS/390 is designed to automate I/O, processor, and system operations. It includes "canned" automation for IMS™, CICS®, Tivoli® Workload Scheduler, and DB2®. Parallel Sysplex Application Automation: SA OS/390 V2.1 introduced extremely powerful new concepts, including sysplex-wide grouping of resources, dependencies, and goals that make Parallel Sysplex automation a reality. You can manage any number of stand-alone systems and clusters from a single point-of-control, even from an easy-to-use Java™-based GUI. In addition, you can move applications and related timers inside a sysplex. Policy-Based Self-Healing: Automation policy can be shared or cloned across the enterprise, which can reduce complexity, implementation time, coding, and support effort. You can add new resources or systems without rewriting scripts. The policy can now be built more easily using more cloning variables and more predefined and self-configured message rules.
Processor Operations (ProcOps) and I/O Operations:
SAP R/3 High-Availability Automation: The integrated SA OS/390 solution combines the concepts of automation, high availability, and transparent failover. Today's complex environment offers the SAP systems administrator significant monitoring and management challenges. This solution covers the current SAP and related components that run on z/OS. Key PrerequisitesThe target system can run in any IBM and non-IBM hardware environment that supports one of the following:
For a detailed description of the hardware and software prerequisites, refer to the Technical Information section. DescriptionSA OS/390 V2.2 Highlights
Integrated Automation:
SA OS/390 V2.2 and NetView for OS/390 V1.4, or higher, enable
unique, seamless automation of both system and network resources. To
help reduce installation and maintenance effort, the system and network
automation can run in a single NetView address space. Managers such as
TBSM can act as status observer for SA-monitored resources, which can
help reduce the effort to implement monitoring and associated overhead
while increasing monitoring accuracy.
More Automation
UNIX System Services Automation
Today's business environment requires multitiered applications that span
z/OS and z/OS UNIX system services. SA OS/390 can automate such
e-business applications as if they were running on just one platform. A
new automation infrastructure can start, stop, monitor, and recover z/OS
UNIX applications and resources like TCP/IP ports and UNIX files.
SAP R/3 High-Availability AutomationToday's complex environment offers the SAP systems administrator significant monitoring and management challenges. IBM delivers an integrated high-availability solution using SA OS/390 that combines the concepts of automation, high availability, and transparent failover.
This solution covers all SAP and related components that currently run on z/OS. This new high-availability solution uses SA OS/390 code base together with a redesign of the SAP central instance concept. It exploits Automation Resource Manager, Dynamic Virtual IP Addresses, shared Hierarchical File System, and DB2 data sharing to provide minimum system outages along with maximum automation. For more information, visit: Easier Automation
Improved Automation Control
ProcOps
Remote zSeries systems can now be controlled via SNMP without additional
PC or networking other than an existing processor LAN. The ProcOps PC
has been removed. Integration into customization dialogs makes ProcOps
customization easier. ProcOps determines the processor type, model, and
processor serial number of machines in the zSeries and S/390® CMOS
processor families at run time. This eliminates the need to specify the
explicit machine type. ProcOps supports Linux target systems running on
zSeries and S/390 processors in LPAR or basic mode.
I/O Operations
I/O Operations can support Dynamic CHPID management and manage FICON
directors.
msys for Operations — The z/OS Built-in Self-Healingz/OS Managed System Infrastructure for Operations (msys for Operations), a z/OS base element, incorporates well-proven automation technology provided by NetView and SA OS/390 into z/OS. All msys for Operations functions are also available to SA OS/390 customers:
Critical resources in a sysplex that are provided with these self-healing mechanisms are CDS, System Logger, or Write to Operator (WTO) buffers. With msys for Operations, you can easily manage all the systems in a Parallel Sysplex cluster, coupling facilities (CF) and their structures, and CDS. By automating typical operator tasks and events in a Parallel Sysplex, it reduces operations complexity and improves system recovery, enhancing the availability of Parallel Sysplex clusters. Distinct displays of relevant information allow greater operational awareness, providing ease of manageability. With one interactive command, you can also back up a coupling facility to a spare CF:
Additionally, msys for Operations resolves situations such as WTO buffer shortages or system logger failures through its built-in automation technology. For more information, visit: Project eLizaWith systems that self-optimize, self-configure, self-heal, and self-protect, Project eLiza helps you to start removing the complexity of ever-expanding e-business infrastructures and overcome systems management challenges. SA OS/390 contributes to the foundation Project eLiza by providing policy-based self-healing and building the base for msys for Operations. msys for Operation is a built-in z/OS self-healing component. The unique automation technology of SA OS/390 plays a key role in building the end-to-end automation of Project eLiza. For additional information, visit: Fewer PrerequisitesTo address requirements for lower prerequisites, SA OS/390 can run in a sysplex environment to use Cross-System Coupling Facility (XCF) only (without MQSeries®) for communication between the automation manager and the automation agents. Running SA OS/390 without MQSeries is only recommended when you reenter lost requests and increased recovery time can be tolerated. Therefore, IBM recommends the use of MQSeries V5.2 with Shared Queue support for highest reliability of the automation environment. Product PositioningWith SA OS/390 V2.2, IBM continues to deliver systems management products for single z/OS or OS/390 systems and Parallel Sysplex clusters that can help you increase your competitiveness by increasing your business application availability and help reduce operations and systems management costs. SA OS/390 V2.2 is especially valuable if you have one or more of the following needs:
Hardware and Software Support ServicesSmoothStart™/Installation ServicesIBM Installation Services are provided for SA 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 Information
Trademarks
Technical InformationHardware RequirementsSA OS/390® V2.2 runs in a virtual storage environment on any IBM or Non-IBM system configuration with sufficient storage that supports OS/390 or z/OS™. SA OS/390 Processor Operations: SA OS/390 Processor Operations supports monitoring and control functions for:
SA OS/390 Processor Operations supports logical partitioning of any of these processors that also support logical partitioning. SA OS/390 System Operations: The SA OS/390 System Operations base program can run on any processor supported by NetView® for OS/390 or Tivoli® NetView for z/OS. SA OS/390 I/O Operations: The SA OS/390 I/O Operations base program can run on:
ESCON Multiple Image Facility is required for enhanced status support.
Software RequirementsThis section defines the minimum programming requirements for SA OS/390 V2.2 and its operating environments. Specific functions of SA OS/390 may require additional products or higher levels of the products listed below. SA OS/390 is executed as an application on the OS/390 or z/OS operating system. SA OS/390 support is provided at the listed levels or subsequent levels that are upward-compatible, unless otherwise stated. Upward compatibility means that functions provided by the earlier releases are still supported Programming Requirements for All Functions
OS/390 or z/OS Optional Priced Features: Hardware Configuration Manager for the I/O operations GUI
Withdrawal: Processor Operation — PC is withdrawn beginning with SA OS/390 V2.2 and is no longer available. Remote zSeries systems can now be controlled via SNMP without any additional PC or networking other than an existing processor LAN. Integration into customization dialogs makes ProcOps customization easier. Compatibility: SA OS/390 V2.2 is upwardly compatible with SA OS/390 V2.1 (5645-006) and SA OS/390 V1.3 (5645-005). The single point of control is supported in this mixed environment. Automation Control Files (ACF) from AOC/MVS can be migrated. Policy databases back to AOC/MVS R2 can be converted automatically. The generated backlevel 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.2 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 (now called 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 V2R2 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. User Group Requirements: This announcement satisfies or partially satisfies requirements from one or more of the worldwide user group communities:
Requirements satisfied include:
Requirement Description
MR00011009 IMSAO AOI EXIT
MR00020858 IMSAO message types inconsistent
with AOC and MVS(TM) standards
MR00041883 OPCAO Enhancements for SDF tape
mount displays
MR00044729 Provide NGMF support for IMSAO
MR00064641 Permit CONSOLE and AUTH parms on
AOFRGCON
MR00073344 Need an extra aofcnmask
MR0108012935 Support for DATE= on OPCACAL
MR0116011131 IEF378I
MR0122016830 AOC/OPC Support for time dependant
workstations
MR0209015619 Increase AOCCLONE variables per
System
MR0222016719 AOC/IMS(TM) Tower Error Messages
Misleading
MR0226016021 Trapping reply from OPCACAL
MR0315004654 AOC/CICS(R) Feature to support VTAM(R)
model Major Node
MR0323014119 OPCALIST, OPCACAL, OPCACMD and
OPCAMOD enterprise wide
MR0326014827 APAR OW48829 addresses the need
to expose variables
MR0405016632 IMS FEATURE requires that its
own DFSAOUE0
MR0724013138 AOC/CICS Feature supports VTAM
model Major Node definition
MR0905016741 Clone Support for System
Automation 2.1
MR0913004517 AOC/CICS Feature supports VTAM
model Major Node definition
MR0926014452 Migrating UETs from SA OS/390
R3 to SA OS/390 V2.1
MR1218004914 IMSCMD should support a period
in the command string
Planning InformationCustomer Responsibilities: For an easy-to-use automation guide, refer to Redbook Automation Using Tivoli NetView OS/390 V1.3 and System Automation OS/390 V1.3 (SG24-5515). You can also download the guide at: 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:
SA OS/390 V2.2 will be shipped on one SMP/E installable tape, which
makes up the basic package. The tape includes SA OS/390 V2.2.
System IntegrityIBM will accept APARs where the installation of this licensed program causes an exposure to the system integrity of OS/390 and/or z/OS. This program is intended to run unauthorized.
OS/390 and z/OS 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 and Tivoli Netview for z/OS. 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 or Tivoli Netview for z/OS to protect SA 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. Ordering InformationSA OS/390 V2.2 Collection (BookManager® and PDF)The SA OS/390 V2.2 Collection contains the SA OS/390 V2.2 product books in both BookManager and PDF softcopy formats on CD-ROM. If this collection is refreshed three months after planned availability, an updated collection will be automatically sent to SA OS/390 V2.2 licensees. To upload BookManager softcopy and create softcopy repositories, the SoftCopy Librarian is the strategic tool for uploading and managing BookManager files on a z/OS or OS/390 host or server, and on LANs and workstations. SoftCopy Librarian, a free program provided on the softcopy tools disk of the CD-ROM collections, outperforms the previous Softcopy Receiver Tool for uploading books and also provides you with management functions for your bookshelves and book files. Because the Softcopy Receiver Tool is no longer supported, you should migrate to the SoftCopy Librarian now. SoftCopy Librarian runs on Windows® 95, or later, and Windows NT® 4.0, or later. The latest versions of the SoftCopy Librarian can be downloaded from the following site:
The following publications are contained in the OS/390 CKit CD (SK2T-6700).
Order
Title Number
System Automation for OS/390 V2.2
Licensed Program Specification SC33-7037
Planning and Installation SC33-7038
Customization and Programming SC33-7035
Defining Automation Policy SC33-7039
User's Guide SC33-7040
Messages and Codes SC33-7041
Operator's Commands SC33-7042
Programmer's Reference SC33-7043
Program Directory GI10-9748
Memorandum to Licensees GI10-9757
Order
Title Number
System Automation for OS/390 V2.2
CICS Automation Programmer's SC33-7044
Reference and Operator's Guide
IMS Automation Programmer's SC33-7045
Reference and Operator's Guide
OPC Automation Programmer's SC33-7046
Reference and Operator's Guide
Current Licensees
Current licensees of SA OS/390 V2.1 will be sent a program reorder form
that can be returned directly to IBM Software Delivery and Fulfillment.
Reorder forms are scheduled to be mailed by two weeks after planned
availability. Reorder forms returned to IBM Software Delivery and
Fulfillment will be processed within 10 work days of receipt. When the
new release is available, the previous release will no longer be
available.
New LicenseesShipment will begin on the planned availability date:
New users of SA OS/390 V2.2 should specify machine type/model 5645-006. Basic License: To order a basic license specify the program number and feature number 9001 for asset registration. Specify 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. 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 and PSLC Level B, and PSLC Level C, and PSLC Level 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.
PSLC PSLC Basic License
Machine Feature MLC Feature
MSU Capacity Number Description
1 0001 PSLC Base, 1 MSU
2 0002 PSLC Base, 2 MSUs
3 0003 PSLC Base, 3 MSUs
4 to 45 0004 PSLC Level A, 1 MSU
0005 PSLC Level A, 42 MSUs
46 to 175 0006 PSLC Level B, 1 MSU
0007 PSLC Level B, 10 MSUs
0008 PSLC Level B, 50 MSUs
176 to 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:
Workload License Charge (WLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Also, specify the feature number of the desired distribution medium. Variable Workload License Charge Features
VWLC VWLC Feature Feature Description Number Base, Level 1 includes 45 MSUs 0460 Additional qty, Level 1 up to 175 MSUs 0480 Registration Base, Level 1 incl 1 MSU 3702 Registration additional quantity Level 1 up to 175 MSUs 3703 Additional qty, Level 2 176 -- 315 MSUs 3704 Registration additional quantity Level 2 176 -- 315 MSUs 3705 Additional qty, Level 3 316 -- 575 MSUs 3706 Registration additional quantity VWLC VWLC Feature Feature Description Number Level 3 316 -- 575 MSUs 3707 Level 3, Per 50 MSUs for machine capacity of 316 -- 575 MSUs 3708 Level 3, Per 50 MSUs for machine Registration of 316 -- 575 MSUs 3709 Additional qty, Level 4 576 -- 875 MSUs 3980 Registration additional quantity Level 4 576 -- 875 MSUs 0019 Level 4, Per 50 MSUs for machine capacity of 576 -- 875 MSUs 0020 Level 4, Reg. for 50 MSUs for machine capacity of 576 -- 875 MSUs 0021 Additional qty, Level 5 876 and up MSUs 4401 Level 5, Per 50 MSUs for machine capacity of 876 and up MSUs 4402 Registration additional quantity Level 5 876 and up MSUs 4403 Level 5, Reg. for 50 MSUs for machine capacity of 876 and up MSUs 4404 Growth Opportunity License Charge (GOLC) To order a 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 Category Feature Number H30 0015 H50 0016 H70 0017 zSeries Entry License Charge (zELC): To order zELC software, specify the program number, feature number 9001 for asset registration, and the zELC monthly charge feature number from the table below. Also, specify the feature number for the desired distribution medium.
zELC
Feature
z800 Models Number
0A1 -- 1 engine 4001
0B1 -- 1 engine 4002
0C1 -- 1 engine 4003
001 -- 1 engine 4004
0A2 -- 2 engines 4005
002 -- 2 engines 4006
003 -- 3 engines 4007
004 -- 4 engines 4008
Single Version Charging: To elect single version charging, the customer must notify and identify to IBM the prior program and replacement program and the designated machine the programs are operating on. Basic Machine-Readable Material
Feature Distribution
Environment Number Medium
OS/390 5801 6250-bpi distribution tape
OS/390 5802 3480 cartridge uncompressed
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)
Ship documentation only (suppresses 3471
initial shipment of media)
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 memorandum and program directory are supplied automatically with the basic machine-readable material:
Order
Title Number
SA OS/390 V2R2 Licensed Program SC33-7037
Specification
SA OS/390 V2R2 Program Directory GI10-9748
SA OS/390 V2R2 Memorandum to Licensees GI10-9757
One copy of the following publications are supplied automatically with the basic machine-readable material on CD-ROM:
Order
Title Number
SA OS/390 V2R2 Customizing & SC33-7035
Programming
SA OS/390 V2R2 Planning and SC33-7038
Installation
SA OS/390 V2R2 Defining Automation SC33-7039
Policy
SA OS/390 V2R2 User's Guide SC33-7040
SA OS/390 V2R2 Messages and Codes SC33-7041
SA OS/390 V2R2 Operator's Commands SC33-7042
SA OS/390 V2R2 Programmer's Reference SC33-7043
Displayable Softcopy Publications: SA OS/390 V2.2 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.
Customized OfferingsMost product media is shipped only via Customized Offerings (that is, CBPDO, ServerPac, Systempac®). Non-customized items (CDs, diskettes, source media, media kits) will continue to be shipped via the stand-alone product. Terms and ConditionsThe terms for SA OS/390 as previously announced in Software Announcement 200-355 , dated September 3, 2000, are licensed under the IBM Customer Agreement and are unaffected by this announcement. Order Now
Use Priority/Reference Code: LE001
Phone: 800-IBM-CALL
Fax: 800-2IBM-FAX
Internet: ibm_direct@vnet.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 systems can now be controlled via Simple Network
Management Protocol (SNMP) without any additional PC or networking other
than an existing processor LAN.