 |
Newsletter 18 |
Exploitation of ESCON Manager / System Automation Functions
What Is New in HCD for OS/390 Version 2 Release 5
HCD has a few functions that exploit ESCON Manager functionality and, therefore, prereqs either ESCON Manager 1.3 or System Automation for OS/390 (SA OS/390) for these functions. These functions are:
- Migrating a switch configuration (port matrix) from a saved switch configuration file or from the active switch configuration of an ESCON Director to the IODF.
- Writing the active switch configuration to or saving a switch configuration on an ESCON Director.
- Collecting data (including physical identification data) from the currently active I/O configuration for priming the IODF or for a comparison with the defined IODF (I/O Path List/Report).
SA OS/390 as the successor product of ESCON Manager is comprised of the integration of three established licensed programs:
- AOC/MVS
- TSCF
- ESCON Manager.
Customers that have been using ESCON Manager but none of the predecessor products of SA OS/390, may decide to stage their exploitation of SA OS/390. As the first stage, they can continue to use the functions they were already using in ESCON Manager. Over time they can plan subsequent stages to extend that exploitation to include the automation, remote operations, and other functions of SA OS/390.
The situation may be similar if they were not using ESCON Manager yet, but desire to enable the HCD exploitation of the above mentioned functions by using only the I/O operations functions in SA OS/390 in a first stage. If installing only the I/O operations part of SA OS/390, the installation and customization process is simpler and faster than the normal full installation as described in the 'System Automation for OS/390 Planning and Installation' manual. It is then possible to complete the full customization process at some later point in time.
For this partial install of SA OS/390, NetView is *NOT* a prerequisite, i.e. the installation and function of SA OS/390 I/O operations (at the level of function that ESCON Manager had) is possible without having NetView installed. For more information about this staged installation of SA OS/390 please see the System Automation for OS/390 web home page
HCD supports the following new processors:
- S/390 Parallel Enterprise Server Generation 4 (9672 R5 models)
- S/390 Coupling Facility 9674 Model C05
- S/390 Application StarterPak (Type 3000 models)
The verify function, which compares the definitions in an IODF with the sensed I/O data, is now available as an action on the HCD activate dialog.
From the HCD activate dialog the verify function is performed as an action for a specified single system or partition. You can choose to compare the sensed system data against the active IODF or against the target IODF of an activate request. Prereq is ESCON Manager or System Automation installed and running.
If the verify function is invoked via the dialog, the output is presented on a new panel, the I/O Path List. For each channel path defined in the IODF the sensed data and the IODF data are listed. In addition, the list contains the following information:
- Indication of discrepancies,
- Information on whether a sensed path is online or offline, and
- Information on whether a sensed device is online or offline.
A filter facility allows the list to be reduced to the entries of interest. These can then be saved into a data set and subsequently printed.
From a production IODF individual CONFIGxx members can be built. Existing CONFIGxx members can be updated or replaced.
For systems which are members of a sysplex, CONFIGxx members can be verified against selected systems. Responses are displayed in a message list.
Within large enterprises IODFs describing the entire I/O configuration may become too big for an effective management. To remedy this problem, while preserving the benefits of keeping a single repository for all I/O definitions, HCD can now build subset IODFs based on configuration packages from a centrally administered master IODF. Configuration packages define subsets of the master IODF, which allows selective distribution of I/O data to target systems, while keeping the processor token in sync. Configuration packages also allow configuration changes made at a remote system to be merged back into the master IODF.
It is now possible to opt for IODFs to be stored in a data space, relieving constraints to the IODF space imposed by user address space limitations.
Ports and coupling facility CHPIDs already connected in another IODF can now be shown as occupied. The HCD dialog does not permit occupied ports to be connected, thus avoiding inadvertent conflicting connections. The user can add or remove the occupied indicator using the dialog.
For all attributes that can be primed prompts have been provided on the object definition panels, e. g. for the serial number and port names on the control unit or switch definition panels. (Prereq is ESCON Manager or System Automation installed and running.)
The channel path list has been improved in design by showing the partitions according to their image numbers. Up to 15 partitions can now be shown on the panel.
The device list has been extended by an extra two columns where the number of operating systems and processors accessing the device are stated. If called from the processor list, it is stated how many partitions of the selected processor are accessing the device.
Figure 1. Changed I/O Device List panel
+--------------------------------------------------------------------------------+
! Goto Filter Backup Query Help !
!-------------------------------------------------------------------------- !
! I/O Device List Row 1 of 14 More: > !
!Command ===> ___________________________________________ Scroll ===> PAGE !
! !
!Select one or more devices, then press Enter. To add, use F11. !
! !
! -------Device------- --#-- --------Control Unit Numbers + -------- !
!/ Number Type + PR OS 1--- 2--- 3--- 4--- 5--- 6--- 7--- 8--- Base !
!_ 0001 3278-3 3 2 00E1 ____ ____ ____ ____ ____ ____ ____ !
!_ 0002 3279-2 3 4 ____ ____ ____ ____ ____ ____ ____ ____ !
!_ 0098 9033 2 0098 ____ ____ ____ ____ ____ ____ ____ !
!_ 0099 9032 2 0099 ____ ____ ____ ____ ____ ____ ____ !
!_ 00C1 3480 2 1 00C1 ____ ____ ____ ____ ____ ____ ____ !
!_ 01D1 3390 2 1 00D1 ____ ____ ____ ____ ____ ____ ____ !
!_ 01D2 3390 2 00D1 ____ ____ ____ ____ ____ ____ ____ !
!_ 01D3 3390 2 00D1 ____ ____ ____ ____ ____ ____ ____ !
!_ 01D4 3390 2 1 00D1 ____ ____ ____ ____ ____ ____ ____ !
! !
! F1=Help F2=Split F3=Exit F4=Prompt F5=Reset F7=Backward !
! F8=Forward F9=Swap F10=Actions F11=Add F12=Cancel F13=Instruct !
!F20=Right F22=Command !
+--------------------------------------------------------------------------------+
|
- HCD profile options no longer need to be located in a cataloged dataset. For batch jobs, profile options can now also be defined inline.
- When processors are repeated, HCD now also copies related coupling facility connections, as well as switches not present in the target IODF. Device preference values for user defined generics are now copied when repeating operating systems.
- HCD can now be used to create OS and switch configuration control statements. HCD extended migration allows these to be migrated back into the IODF.
- JES3 initialization stream checker data can now be created using a batch utility. A batch utility function is provided which allows creating a work IODF from a production IODF.
HCD / HCM home page
|
