HP 3000 Manuals HP 3000 Manuals
TurboSTORE/iX Changes by Harvey Skinner, Jim Nissen, and Laura Fischer Commercial Systems Division For this MPE/iX release, TurboSTORE/iX has undergone some internal low level renovation to provide a better code base for future enhancements. Although the majority of the changes are completely internal and are not visible to you, a few of the changes are noticeably different from previous versions of TurboSTORE. In addition to the internal changes, a new utility for use when backing up to Hewlett-Packard Magneto-Optical devices (which requires the purchase of TurboSTORE/iX II products HP36397 or HP36398) is also available with the MPE/iX Release 5.0 of TurboSTORE/iX II. Free Trial Period of Advanced Features The first difference that you may notice is an automatically enabled "trial period" for some of the advanced features of TurboSTORE/iX. If the version of STORE/TurboSTORE on your system does not include support for the ONLINE, COMPRESS, INTER, STORESET, or RESTORESET options, then use of all these options will be available to you for a trial period of 90 days. This replaces the TurboSTORE Demo product (B2492A) available on MPE/iX Release 4.0.
NOTE Any tapes created with any of the "trial" features can be restored with ANY version of STORE/TurboSTORE after the trial period has expired. You can distinguish whether the free trial period is active on your system by looking at the product banner when doing a STORE or RESTORE. If after the product banner a second banner stating "FREE TRIAL PERIOD" is also displayed as in the following example, then you can use all the advanced options until the trial period expires.
Example of "FREE TRIAL PERIOD" banner: >> TURBO-STORE/RESTORE/VSTORE VERSION D.50.02 HP31900A << =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= = TurboSTORE - FREE TRIAL PERIOD - EXPIRES TUE, MAR 22, 1994 = =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= If you would like to continue to use any of the "trial" options after the trial period is over, please contact your Hewlett-Packard Sales Representative for information on purchasing the correct product of TurboSTORE/iX before the trial period expires. New Utility for Magneto-Optical Backup If you have purchased TurboSTORE/iX II products (part numbers HP36397 or HP36398) that support STORE and RESTORE of data on HP Magneto-Optical devices, you will receive a new utility with MPE/iX Release 5.0. Because Magneto-Optical media is still quite costly when compared to magnetic tape media, we have developed a new utility, STORCOPY, that allows you to copy TurboSTORE/iX store data from Magneto-optical media to magnetic tape media. For more information on the STORCOPY utility and its use please refer to the "Appendix" of the STORE and TurboSTORE/iX Manual (30319-90001, second edition) which discusses use of STORCOPY. Special Wildcarded Name Translation for HFS File Backups To allow backup of Hierarchical File System (HFS) (POSIX name style) files and directories to be more integrated with backup of MPE files, STORE/TurboSTORE translates wildcarded MPE syntax names to include all files (all MPE files and all HFS files and directories) as follows: @.group.account => /ACCOUNT/GROUP/ (all files under GROUP.ACCOUNT) @.@.account => /ACCOUNT/ (all files under ACCOUNT) @.@.@ => / (all files on the system) @.@ => /logon account/ (all files under logon account) @ => ./ (all files under current directory) This translation only applies to inclusion file sets. It does not apply to exclusion or negative file sets (those preceded by a "-"). Specifying "?@" in the filename part of a file set causes STORE/TurboSTORE to select only MPE syntax filenames. Differences You May Notice STORE and TSTORE Program Files are the Same. In the past, standard FOS level STORE and the purchased product level of TurboSTORE resided in two different program files in PUB.SYS, STORE and TSTORE. Because the level of functionality was different in the two programs, this did not allow other system level utilities such as DBSTORE/DBRESTOR and SYSGEN to access the highest level of STORE/RESTORE functionality that was available on the system. With MPE/iX Release 5.0, the two program files, STORE.PUB.SYS and TSTORE.PUB.SYS are identical and both have the appropriate product level of functions purchased. When you run the STORE or TSTORE program file, both will give you the same STORE/TurboSTORE product banner and have the same level of features available. When using DBSTORE/DBRESTOR, the appropriate level of purchased features can now be used also. The reason that both files are still available is to avoid interruptions to users who are running the TSTORE program file directly in their system operations. Multi-process Differences. As part of the low level changes in the way TurboSTORE works, one of the key changes to Release 5.0 is to have each parallel STORESET/RESTORESET device pool owned and controlled by a separate process. Previous versions of TurboSTORE had a single process owning and controlling all I/O to all the backup devices being used. The new multi-process structure of TurboSTORE/iX Release 5.0 allows greater I/O concurrency with multiple STORESETs/RESTORESETs and allows better utilization of system resources, especially in a multi-processor environment. Because Release 5.0 of TurboSTORE/iX uses multiple processes whenever multiple STORESETs/RESTORESETs are used, these additional processes are also visible when issuing a SHOWPROC or SHOWQ command, or using a utility to view process activity. For STORE, there are a minimum of three processes (parent, surrogate, and one child) at all times. For each additional parallel set (STORESET), there is an additional child process. For RESTORE, there are a minimum of two processes (a parent and one child) , plus one additional process for each additional parallel set (RESTORESET). Operator Request Differences. Now that TurboSTORE/iX may use multiple processes to control the backup devices, the way that the operator requests appear also changes slightly. In previous versions of TurboSTORE, since one process owned all the backup devices, including those in different STORESET/RESTORESET pools, the PIN number associated with each of the operator requests was the same. Since multiple processes are now used, one for each STORESET/RESTORESET, the PIN numbers for operator requests are not always the same and may be issued at the same time. File Listing Differences. With TurboSTORE on MPE/iX Release 4.5, a new file list format was introduced for cases when the STORE/RESTORE included a HFS format file. The additional file list format is needed to allow enough space to display the potentially much longer HFS style filename. As of Release 4.5 of TurboSTORE, any time the STORE/RESTORE fileset includes an HFS format file, the resulting file listing is in the HFS style format. In addition to the HFS style file list format, there is another slight change which affects the listing order of files for TurboSTORE/iX Release 5.0 due to the multi-process enhancement. When doing a parallel set (RESTORESET) RESTORE with SHOW from a store set of tapes created with the INTERleave option, and there are more store sets to be restored than there are restore devices, the listings of files at the end of the restore are displayed by set. Each set is sorted within itself, but the order of the sets when printed depends on which device the sets were restored from, and the order in which the sets were restored. Using $NULL as a STORE Device When using the storefile parameter of Release 5.0 of STORE and TurboSTORE, it can now refer to the actual file designator $NULL. The MPE/iX FILE command should be used to set up a file equation prior to running store. For example: FILE N=$NULL Doing so causes STORE to use $NULL as its output device. The command line is parsed, the input file set scanned, all files are read from disk, and all output is displayed as normal. The only real difference is that the data is not actually being written to an output device. This feature can be useful when trying to determine which files will be stored by STORE, as a trial run. It can also be used, with EXTREME caution, with the ;PURGE option, to remove all specified files. When using this feature, keep in mind that your files are NOT being stored to any kind of device, so the data has not been saved anywhere. Notification of File Availability In Release 5.0 STORE, a new option, NOTIFY, has been added to help automate the backup process, particularly for an online store. When specified in conjunction with a user-specified job stream, NOTIFY streams a job at the time when the files being backed up are available for full user access (including writing and purging). For an online store, the job is streamed once the attach phase has completed. Currently, a message is printed to the system console indicating that the files are free. It is then up to the user or operator to perform some action based on seeing that message. The backup process can be automated by placing the tasks that need to be performed into a job stream, and letting STORE stream the job for you. For a non-online backup, the job would be streamed at the end of a successful store operation. To use the NOTIFY option, first use the FILE command to set up a file equation for the formal file designator NOTIFY. For example, FILE NOTIFY=MYJOB.PUB.SYS This should be done before the store job is run. Then, issue the STORE command, specifying the NOTIFY option: STORE @.@.@;*T;SHOW;ONLINE;NOTIFY If STORE is being run from a session, and the job file requires passwords to be entered, STORE prompts you at the terminal, and waits for the passwords to be entered. If a job stream needs passwords, and STORE is being run from a job, then the job fails to stream. These errors, and all errors and output resulting from streaming the job, are sent to $STDLIST. STORE Console Messages In Release 5.0 STORE, there has been a slight change in the operation of certain console messages issued by STORE. The messages affected are the ones issued when RESTORE is skipping over the SLT of a combined SLT/STORE set, and the message issued during an online store when all files have been attached to the shadow log. Previously, these messages went exclusively to the system console. In Release 5.0, these messages are sent to your terminal if STORE or RESTORE is being run from a session. The messages are still sent to the system console. This allows individual users of store to have better information on the tasks that STORE and RESTORE are performing for them. Specifying STORE Output Devices When specifying output devices for STORE, the recommended method was to define a FILE equation for the device, and then use it as the storefile parameter to store, or as an argument to the STORESET option. However, this policy was not strictly enforced. This meant that you could specify a dereferenced file equation for a STORE output device without defining it first, and STORE would accept this and prompt the operator to mount the unlabeled tape of the same name. This behavior has changed in 5.0 STORE. Now, it is required that you specify a FILE equation for a device before using it in a STORE command. For example, you must do something like: :FILE T;DEV=TAPE :STORE @.@.@;*T;SHOW Not specifying any device for the single store device still results in a default device name based on your user name. You may not specify a file equation to override that default device name. This restriction also applies to devices specified for RESTORE and VSTORE. STORE File Warning Messages Some warning messages generated by STORE when it is unable to store a file have been suppressed. There are two warnings that fall into this class. When a file is specified more than once on the STORE command line, STORE no longer prints the message: ! WARNING: THIS FILE IS ALREADY LOCKED BY A STORE PROCESS Instead, STORE keeps track of how many files are specified multiple times, and at the end of the STORE operation, prints a summary message of the total number of files not stored because of this reason. FILES REDUNDANTLY SPECIFIED : ## If a file really is locked by a separate STORE process, the original warning is printed for the file, and the file is not stored. The other warning that has been suppressed is: ! NOT STORED : FILE IS NOT ARCHIVABLE. This message was printed for all files that have their non-archive bit set in the file label. (They show a NOBACKUP label in a LISTF,3.) Now, a running count of the number of non-archivable files is kept, and a summary message is printed at the end of store. FILES NOT ARCHIVABLE : ## There are quite a few files on Release 5.0 that are not archivable, and this change should help to make STORE listings more readable, by removing a large number of warnings. Expanded RENAME functionality With Release 5.0 of STORE and TurboSTORE, the RENAME option has been expanded to handle HFS-named files as well as MPE-named files. HFS files and directories can be moved to new locations in the directory structure, and their creators can be modified. These new file attributes can be specified at STORE time by using the RENAME option in conjunction with an expanded file set syntax specification. Renaming HFS files can be more complicated than renaming MPE files, so for full details in using RENAME with HFS named files, consult the STORE and TurboSTORE/iX Manual (30319-90001, second edition).