|
|
|
|
|
|
  |
 |
OpenVME Version 7 is due to be released in August 2007 and is the last version of OpenVME that will be released to run on Trimetra NOVA systems. Subsequent versions of OpenVME will only be licensed for superNOVA.
As with all previous OpenVME releases the facilities that it contains are covered by three categories:
• facilities requested by customers
• facilities that improve the support of OpenVME and thus are of benefit to both its users and Fujitsu
• facilities that assist Fujitsu in providing on-going continuation engineering support of OpenVME.
This document is structured in a similar manner.
1.2. Secure Category from Historic Plex
1.3. Secure Category - Long Filenames
1.5. New command GIVE_FILE_DETAILS
1.6. Switch DNS Resolver Task journal
1.7. New command CANCEL_USE_RECOVERY_FILE
1.8. Enhancements to Display Commands
1.9. TCP/IP Privileged Socket Permissions
2. Supportability/Diagnosability Features
2.1. Displaying SAP hierarchies
2.3. Improved handling of Emergency Store Dumps
2.4. Enhanced System Diagnostics
2.5. Catalogue Plex Consistency
The new SCL command FIND_FILES allows files to be located by matching a filename using a wildcard pattern. The syntax used for the filename pattern-matching is compliant with the POSIX 1003.1 specification, for example '?' and '*' in a supplied filename are replaced and expanded into all existing filenames matching the given pattern.
FIND_FILES enables users to list those files to which they have access, that match a wildcard pattern supplied as the FILE_SPECIFICATION parameter. The files to be searched are specified by the COMPONENTS parameter and the amount of information required is specified using the LEVEL parameter. Output may be directed to one or more of the job journal, the interactive device (MAC environment only) or a named file.
[ Return to List of Facilities ]
OpenVME Version 7 provides a significant improvement in guaranteeing the usability of data backups and enhances the capability to run high availability systems.
Prior to OpenVME Version 7, when using SECURE_CATEGORY it was necessary to schedule a time when there was no write access to the files in the category being secured. If this was not possible SECURE_ACTIVE_CATEGORY could be used at the risk of having inconsistent or unusable data.
OpenVME Version 7 provides a method for:
• archiving a single category, or multiple categories that form a coherent set
• drastically reducing the time that write access is not permitted to the category (to less than 10 seconds times the number of partitions in the category) by making use of filestore multiplexing.
The new command SET_PARTITION_PLEXES_TO_HISTORIC makes extra plexes for all affected categories HISTORIC. SECURE_CATEGORY can then be called to read from the historic plexes instead of the established partition. Write access is not allowed during the short period while the plexes are made historic but is allowed during the rest of the backup.
The benefits of using the new facility are:
• Reduced backup window
• Guaranteed consistency of security copies
• Loss of a tape device no longer means that a scheduled archive runs for too long or has to be aborted
These benefits should be balanced against the following factors:
• Extra disc filestore may be required if insufficient unused filestore is available
• There is extra load on the OCP and disc controllers for plex restoration and multiplex working
• Amendments to utilities and operating procedures will be required if this feature is to be used
Note that if the system is regressed to a previous release of OpenVME and it has plexes with state HISTORIC, they will be left unchanged and will not be used as input when writing security copies. HISTORIC plexes can be restored explicitly by calling RESTORE_PARTITION_PLEX, so the system is ready for a call to SET_PARTITION_PLEXES_TO_HISTORIC when the system is moved forward to OpenVME Version 7 again.
[ Return to List of Facilities ]
The recovery of a disc category is simplified where a security copy does not contain all the information necessary to fully re-catalogue some of the files. This includes files with long filenames. It is no longer necessary to take specific action to fully re-catalogue each of these.
This feature makes use of the existing facility to export and import categories while securing and recovering a disc category.
There is no change to the function of existing commands unless explicitly requested. If the new facility is requested using the command CHANGE_DISC_CATEGORY_DETAILS it is not necessary to change any existing calls that secure and recover disc categories. If, however, there is compiled code that uses these commands and specifies the response parameter by position, it will be necessary to make changes to the code before it is recompiled.
[ Return to List of Facilities ]
Improvements and enhancements have been made to FTP support on OpenVME in the following areas:
• The three FTP client commands CWD, CDUP and PWD are now supported in the FTP responder (server). These allow a working directory to be set up allowing greater ease of use when initiating FTP transfers. These facilitate the use of a wider range of FTP client software to connect to OpenVME's FTP responder. A number of third party products use these FTP commands to navigate the filestore structure of the target system.
• There are changes to the use of the commands EPSV, PASV and PORT. These enable FTP file transfers through firewalls where OpenVME is an initiator or responder. The OpenVME initiator will use EPSV by default and only if the responder's reply indicates that EPSV is not supported will OpenVME try using PASV. If PASV is not supported by the responder then OpenVME will issue a PORT command. The OpenVME responder will also recognise these commands. The reply to EPSV will be success only if the address is for IPv4.
• The FTP responder supports the FTP client commands MKD and RMD allowing a new directory to be created (Make Directory) and an existing directory to be deleted (Remove Directory). The directory within OpenVME can be a group or a library.
• A QUOTE facility is provided, allowing sophisticated users to supply extra FTP commands to a remote FTP server, thereby permitting further customisation of file transfers. This includes the facility to supply user-defined FTP commands with no associated transfer so that only the user-defined FTP commands are executed.
With the changes described above, all mandatory FTP commands listed in RFC1123 Requirements for Internet Hosts - Application and Support, are implemented with the exception of STAT.
[ Return to List of Facilities ]
A new command GIVE_FILE_DETAILS is provided as part of the OpenVME System Programming Option. This is added to the set of GIVE-style commands that enable information generally available though the DISPLAY-style commands to be available in a machine-readable form convenient for software.
Note that this command has the short form GFD which has also been used by the 'Goodies' command GIVE_FCR_DETAILS. Usernames that have the Goodies library on their default loading library list (above ICLSTDSW) will not be able to use GFD for GIVE_FILE_DETAILS.
[ Return to List of Facilities ]
The DNS Resolver task can now be instructed to switch to a new journal using the command TELL, without closing the task. It closes the existing journal, if there is one, and opens a new journal to capture all new messages.
This will be of use when tracing, or a dump, is required for diagnosis of a problem. The system manager can switch on tracing or request a dump of the task, using the TELL interface. When the required output is complete the system manager can instruct the task to switch to use a new, tidy journal. In this way diagnostic information can be captured and isolated to be sent as evidence with a bug report, and the file can be tidied, while the service is still running.
[ Return to List of Facilities ]
Multiple RECMAN database files can share the same after-looks file. This relationship will have been established using the command USE_RECOVERY_FILE. OpenVME Version 7 provides the means to remove the recovery relationship between a particular main file and an after-looks file without affecting the after-looks for other main files that are using the same after-looks file. This is achieved using the new command CANCEL_USE_RECOVERY_FILE. The command can also be used to remove a recovery relationship between an after-looks file and an archive file.
[ Return to List of Facilities ]
The output produced by various Display commands is clarified and enhanced.
The commands changed are:
DISPLAY_INSTALLATION_DETAILS (DINSTD)
• START_FROM and STOP_AFTER implemented for all components (especially unique to installation objects - such as tasks and profiles)
DISPLAY_USER_DETAILS (DUD)
• START_FROM and STOP_AFTER implemented for all components (especially unique to installation objects - such as tasks and profiles)
DISPLAY_PERSON_DETAILS (DPRSD)
• Will display person's full name (not just short form)
DISPLAY_SAP_DETAILS (DSAPD)
• The ability to display SAP hierarchies has been enhanced. See Displaying SAP hierarchies for more information.
DISPLAY_UNIT_DETAILS (DUND)
• The ability to display SAP hierarchies has been enhanced. See Displaying SAP hierarchies for more information.
DISPLAY_UNIT_DESCRIPTION_DETAILS (DUNDD)
• Revised list of items displayed for each LEVEL
• Allow display of unit description from a library
• Display TLD items in hexadecimal and decimal
• Decode meanings of TLD items where a standard meaning exists.
[ Return to List of Facilities ]
The System Manager is given greater control over the permissions associated with reserved TCP/IP (TCP and UDP) ports (1 to 1023). Specific reserved ports can be associated with particular INET services and their use can be controlled by the permissions given to the services.
Users that currently have 'D' (declare) access (to the service ICL9NINET) will continue to have access to all reserved ports. A System Manager may choose to use other INET services to limit access to reserved ports from native OpenVME applications that call the Sockets interface or the XTI.
If the system is regressed to a previous version of OpenVME the association of particular users with INET services will not be considered when finding an INET service. It would be necessary to give ICL9NINET 'D' permissions to be able to use reserved ports.
This facility will not be available for VME-X users and services.
[ Return to List of Facilities ]
The transfer between different OpenVME systems of information held on magnetic tape is simplified by enhancements to the existing command CORRELATE_TAPES.
A report can be produced giving details of the files and libraries held on a set of VME format tapes and the files and libraries can be automatically catalogued on the host system. Information is produced to assist the user to copy files and libraries down from tape onto the host system. Prior to OpenVME Version 7 tape correlation was only available on ISO format tapes.
Note that the report file for VME format tapes differs from that for ISO format tapes. Any existing utility that processes the report file for ISO tapes will need to be changed if it is to handle reports for VME tapes.
[ Return to List of Facilities ]
An unattended full load of OpenVME is now supported. If you request a full load and do not log in to the Master Operator, an unattended session will ensue.
You are advised to consult existing documentation if you have not run in unattended mode before. The limited (L, LB) and emergency (E, EB) degraded variants of a full load will not run as unattended sessions.
[ Return to List of Facilities ]
The facilities available to display upwards through a SAP hierarchy are currently provided by DISPLAY_UNIT_DETAILS, which lists the SAPs (if any) associated with the unit, and by DISPLAY_SAP_DETAILS, which provides details of any SERVICE above a DISAP.
Changes have been made to extend the display facilities to show SAP hierarchies in both an upwards and downwards direction. The displays are intended to simplify the identification of incorrectly catalogued networks and hence improve the resolution of network problems.
A new value, UPSAPHIER, has been provided for the COMPONENTS, C_COMPONENTS and C_C_COMPONENTS parameters to the display functions. This will provide a similar function to that currently provided by SAPHIER. SAPHIER lists the hierarchy of SAPs and units beneath the SAP in the hierarchy. UPSAPHIER will list the hierarchy of SAPs and services above a specified SAP or unit in the hierarchy.
[ Return to List of Facilities ]
Changes have been made to various diagnostic traces, particularly during the load sequence. These will improve the chances of resolving problems that occur during and after these sequences.
Improvements to the diagnostics in MAMPHY were provided as a set of repairs on OpenVME Version 6 (see ION S194). These improvements are now documented in OptICL as part of the documentation for OpenVME Version 7.
[ Return to List of Facilities ]
Prior to OpenVME Version 7 in extremely rare circumstances, it has been possible to lose an Emergency Store Dump following a system failure. At OpenVME Version 7 Emergency Store Dumps will not be lost.
Note that until all system loadsets have been upgraded to OpenVME Version 7, this feature will not work fully.
[ Return to List of Facilities ]
A mechanism has been put into place to enable OpenVME to reduce the number of occasions where a crash is required in order to obtain diagnostics. This mechanism is only available when advised by OpenVME support staff.
[ Return to List of Facilities ]
Previously in extremely rare circumstances it has been possible for OpenVME to load on an out-of-date plex of the catalogue. In OpenVME Version 7 the possibility of OpenVME restoring an out-of-date plex over an up-to-date one has been eliminated. The possibility of OpenVME choosing an out-of-date plex has also been minimised, an operator can now ensure that OpenVME chooses the up-to-date plex.
System operators will need to be made aware of the actions to take when a plex is FROZEN, even on sites that do not regularly use OpenVME multiplexing.
It is no longer essential to take a new checkpoint after moving or adding a plex to a checkpointed partition. However, it is still advised that, when convenient, a new checkpoint should be taken since OpenVME, on restart, looks first for the discs recorded in the checkpoint.
[ Return to List of Facilities ]
The current load process logs an item in the Master Operator journal to indicate load complete, this log is used as a trigger for various system actions. However there are situations where systems are loaded and run work without such an operator logging in (such as unattended Checkpoint/Restart).
Changes have been made to the load sequence to provide appropriate triggers for all of the required actions without the need to log in the Master Operator (MOP).
[ Return to List of Facilities ]
At this release SAM will be identified as a generic version of OSAM. Future releases of SAM will merely be maintenance releases of this generic OSAM. The changes to facilitate this have been incorporated as part of the OpenVME 7 upgrade process.
[ Return to List of Facilities ]
 |
|
|