Patch Name: PHSS_17474 Patch Description: s700_800 10.10 OV OST2.X cumulative A.02.10 patch Creation Date: 99/05/03 Post Date: 99/05/12 Hardware Platforms - OS Releases: s700: 10.10 s800: 10.10 Products: HP OpenView OmniStorage A.02.10 Filesets: OMS.f_server OMS.f_client OMS.common OMS.f_gui OMS.f_fs OMS.manpages Automatic Reboot?: Yes Status: General Release Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_17474 Symptoms: PHSS_17474: 1 Rebuilding magnetic cache from nearline volumes gene- rates massiv error messages (CHSM710008/CHSM710008) in dedlog file. (ddts: NSMex01055) 2 zb: data corruption w/ part resident files (ddts: JOSqa00295) 3 CHSM410281 errors in qrlog and outward migration fails (ddts: NSMex01740) 4 the ager starts stops in loop (ddts: NSMex01757, JOSqa00253) 5 AGEWEIGHT SIZEWEIGHT confuses customers (ddts: NSMex01991) 6 VBFS API error code (219) / [CHSM160046] (ddts: NSMex01384, NSMex01768, NSMbb22049) 7 Write a par archive to MO volume exits with error "Can't erase the remaining media start = ..." (ddts: JOSqa00302) 8 [CHSM230183] Out of memory in function jcom_alloc() need 416 (ddts: NSMex01821) 9 restore_vbfs has problems to restore "spaced" file names (ddts: NSMex01824) 10 fsck -y could lead to data loss and cause panics at startup (ddts: NSMex01899, JOSqa00305, JOSqa00292, NSMbb19445) 11 Application hangs, if needed data are on secondary media and this volume was manually ejected (not using the OMS command exportp). (ddts: NSMex01772) 12 formatp on blank MO fails sometimes if sidf is specified (ddts: NSMex00814) 13 [CHSM230562] jmd: Media set to error state; volume = c00073 (ddts: NSMex01992, NSMex01191) 14 Active mode ager continously submitted migout requests not stopping at ALWM (ddts: NSMex01975) 15 volsets not created if TMPDIR environment variable is set (ddts: NSMex01969) 16 Rebuild fails to rebuild (ddts: NSMex00837, NSMex00371, NSMex01141 SR #5003409540) 17 listp -a could be better, command scrolls over screen with CR's (ddts: NSMex01057) 18 Panic after installing patch PHSS_15817 (ddts: NSMex01909, NSMex01777) PHSS_15817: 1 Migout-request is created and finished, but the file remains on the MFS. qrlog shows ERROR [CHSM410337]. (ddts: NSMex01536) 2 Zb does not accept "q" to quit if one tape is completely filled with data. (ddts: NSMbb15681, SR: 1653225896) 3 Shutdown hangs after installing PHSS_15452/PHSS_14839 (ddts: JOSqa00248) 4 The Unmount entry in mig-log file shows a wrong platter. (ddts: JOSqa00092) 5 If an application wants to read data and these data are on secondary media which state is not INTERNAL, then the application hangs. (ddts: NSMbb14671, SR: 5003383265) 6 Qr must be restarted after import media. (xddts: NSMex00928) 7 Bkup_vbfs and restore_vbfs hang if more than one tape is necessary and user wants to abort backup / restore pro- cedure with 'q' or 'Q'. (xddts: NSMbb15742) 8 Bkup_vbfs picks up all platters of a MFS with state INTERNAL or EXPORTABLE. (ddts: NSMbb10845, NSMex00576) 9 Restore_vbfs restores files during rebuild which have been deleted before. (ddts: NSMbb15885) 10 Qr core dump on qqr with long file names. (xddts: JOSqa00124) 11 IOS: unable to read files with strlen(path) > 255 (xddts: JOSqa00243) 12 Migration to WORM does not complete. Io_server consuming large amounts of CPU time doing nothing. (xddts: NSMex01476) 13 Tape errors caused by DLT drives. (xddts: NSMex01330) PHSS_14839: 1 After running cleanup freshly formatted platters in the freepool are not completely free anymore. (ddts: NSMex00360) 2 Customer request for a common device type. (ddts: NSMex00485) 3 Sync_vbfs fails to set side A or B in state maintenance. (ddts: NSMex00689) 4 Potential data loss because of dropped locks on migins caused by writes. (ddts: NSMex00750) 5 OMS client with two lan cards cannot connect to OMS server. (ddts: NSMex00872, JOSqa00207) 6 Migout -R /dir/* migrates only a part of the directory content. (ddts: NSMex00879) 7 CAPS file densities not available for DLT7000. (ddts: NSMex00948) 8 Zmrestore has a memory leak. (ddts: NSMex00968) 9 OmniBackII path used in OmniStorage GUI refers to 9.x path. (ddts: NSMex01022) 10 Format media with imbedded "mediainit" fails. (ddts: NSMex01105) 11 Reading data from secondary media fails with error "early end encountered". (ddts: NSMex01149) 12 Active ager runs for ever, not moving bulked aged files. (ddts: NSMex01168) 13 OMS integration with OBII has poor performance. (ddts: NSMex01187) 14 Sync_vbfs fails processing large numbers of files. (ddts: NSMex01265) 15 Active ager will migrate all bulk aged files. (ddts: NSMex01274) 16 Recovering single files from a former backup of a migrating file system fails. (ddts: NSMbb16955) 17 Xhsmmgr fails formatting media with duplicate id for syncing. (ddts: NSMbb17328) 18 Bkup_vbfs failed after installation of PHSS_13436. Bkup_vbfs calls sync_media instead of sync_vbfs. Bkup_vbfs cannot access error -/status files on remote client host. (ddts: JOSqa00206) 19 Qr: slows down with large numbers of migin requests. Ager waits for all requests to complete, not just its own. (ddts: JOSqa00211) 20 LMOpenSlotVS fails if jukeboxes are numbered 1 and 2, sync_vbfs fails. (ddts: JOSqa00232) 21 Restore_vol using multiple drives causes a system panic (ddts: NSMex01226) 22 Sync_vbfs fails with WORM media. (ddts: NSMex00776, NSMex00871, NSMex01127, NSMex01133, NSMex01353) 23 Chgstate does not accept more than 50 volumes (ddts: JOSqa00230) 24 WORM media not recognized on series 700 machine (ddts: JOSqa00228) 25 Vsbind shows old binding which cannot be deleted (ddts: NSMbb13455) 26 OMS needs to be year 2000 compliant (ddts: JOSqa00234) 27 File system 100% full, cannot be aged because no space left (ddts: JOSqa00155) 28 Bulk mode ager memory usage increases (ddts: NSMex01195) 29 OMS 02.10 kernel part needs to be updated to latest vxfs patch level (ddts: JOSqa00236, NSMex01302) 30 Patch conflict between PHKL_13281 and OmniStorage. (ddts: NSMex01433) 31 Qr and jmd slow with large numbers of truncates, migouts (more volumes than drives). (ddts: JOSqa00235) PHSS_13436: 1 Ager/migout -R not moving all data from magnetic to storage media (xddts: NSMbb16620) 2 listp -B not consistent with listp -S (xddts: NSMbb15784) 3 Some aliases are not resolved by listp or loadp (xddts: JOSqa00190) 4 jmdrestore fails - external bar-code is stored in alias (xddts: JOSqa00129) 5 qr aborts migin request because size of request is too large (xddts: JOSqa00186) 6 Wording within error messages / documentation / log files inconsistant (xddts: NSMbb14815) 7 STK_SILO JMD database and ACSLS gets out of sync (xddts: JOSqa00174) 8 Panic: aging large numbers of files (xddts: JOSqa00178) 9 sync_vbfs does not work correctly for MO/UFS media (xddts: NSMbb16925) 10 formatp GUI tape capacity list needs entries for STK SILO tapes (xddts: JOSqa00072) 11 Qr: migin : early end encounted (xddts: JOSqa00169) 12 STK SILO - installchanger / removechanger does not show ACSLS drive path (xddts: JOSqa00194) 13 new options listp -a and jmdrestore -a (xddts: JOSqa00195) 14 poor performance with duplicate read requests from tape (xddts: NSMex00836) 15 invalid start/size on qr requests can put media in error state (xddts: JOSqa00152) 16 wrong displayed usage in case of misused zmdump/ zmrestore (xddts: NSMbb16966) 17 problems with zmdump in production environment (xddts: NSMbb16926, NSMex00575) 18 after migin -m, most hsm utilities fail on the file (xddts: JOSqa00182) 19 incorrect statement in man page for zb (xddts: NSMex00762) 20 Capacity of Tape is very small when writing to EOT (xddts: JOSqa00185) 21 migins from MO are slow (xddts: NSMex00789, JOSqa00168) 22 A4619113 - restore_vbfs coredump or hangs (xddts: NSMex00453, NSMex00731) 23 Migsever fails with bus error & core dump (xddts: NSMex00731, JOSqa00166) 24 jmdrestore fails if media database does not exist (xddts: NSMex00691) 25 removechanger does not update ./data/jmd, listp is inconsistent (xddts: NSMbb15240) 26 File System GUI is accepting ANY value for the maximum file size. (xddts: NSMbb15876) 27 Data on re-imported ONSITE media not accessible (xddts: NSMbb15536) 28 poor performance because of DM_NO_TOKEN usage (xddts: JOSqa00173) 29 hsm_admin -I accepts wrong fsid -- no error message (xddts: JOSqa00075) 30 Qr: truncates are extremely slow (xddts: JOSqa00131) 31 xhsmmonitor shows outstanding requests, qqr does not (xddts: NSMbb14801) 32 qr dumped core after truncate and forward requests (xddts: JOSqa00170) 33 Formatp calculates different size after installation of patch PHSS_12402 (xddts: NSMex00714) 34 copyp fails with platters formatted after installation of patch PHSS_12402 (xddts: NSMex00716) PHSS_12814: 1 PHSS_12402 doesn't install zmdump/zmrestore correctly (xddts: JOSqa00167) PHSS_12402: 1 backup with OB creates thousands of defunct kdm_user_thread processes (xddts: JOSqa00094) 2 Stale space is increased when media freshly formatted (xddts: JOSqa00116) 3 zls shows non-resident files as 100% magnetic (xddts: JOSqa00122) 4 Mirroring WORM platters causes sync_vbfs to fail (xddts: NSMbb14126, JOSqa00127) 5 zmrestore dumps core (xddts: NSMbb14835) 6 Error: Cannot convert string "unspecified_pixmap" to type Pixmap (xddts: NSMex00402, SR 1653207746) 7 When importing a WORM the free space is 637040 although the media is full (xddts: NSMex00498) 8 zmrestore runs out of phase by restoring a 02.10 zmdump archive. (xddts: JOSqa00150) 9 OmniBack fails to backup MFS after patch PHSS_10679 is installed (xddts: NSMex00671) PHSS_10679: fixes in jfs/dmapi 1 Panic when mfs is used very heavely by many jobs (xddts: NSMex00442) 2 Adapt OmniStorage to jfs patch level (xddts: JOSqa00074) 3 Killing kdm_user_thread processes during shutdown panics the system (xddts: NSMex00342, NSMex00372, NSMex00438) fixes in OmniStorage 4 zshutdown does not always unmount migrating filesystems (xddts: NSMbb11960, SR 5003357608) 5 convert_media replies "Can't communicate with the jmd" (xddts: NSMbb12012, SR B700027755) 6 Add DLT Library to jmcaps config file (xddts: NSMbb12337) 7 zstartup does not check if the ded is running (xddts: JOSqa00062) 8 [CHSM230562] jmd: Media set to error state (xddts: NSMbb12945) 9 jlog file entries show mismatch between drive# and box# (xddts: NSMbb13652) 10 bkup_vbfs fails for directories with spaces in its names (xddts: JOSqa00078) 11 A4470058 - Old files not cleaned up on optical (xddts: NSMex00358) A4484422 space retained on MO after file deleted (xddts: NSMex00364) OMS A.02.10 does not always release space on MO after rm (xddts: NSMbb11931, SR 5003356048) 12 A4471041 - writes to migrating filesystem hang (xddts: NSMex00356) 13 A4500125 - Files not getting migrated out. (xddts: NSMex00359, SR 5003354993) 14 W3691246 - BCS - migin hangs (xddts: NSMex00466) Incomplete files on platter found (xddts: NSMex00362) 15 write to a file corrupts data (xddts: JOSqa00040) 16 qr connection to ded refused after reboot (xddts: JOSqa00047) 17 WORM not recognized (xddts: NSMbb11956) 18 tape handling at the end of tape not correct (xddts: JOSqa00068) 19 par fails while writing to a WORM (xddts: JOSqa00082) 20 copyp of WORM fails (xddts: JOSqa00097) 21 par command fails to read WORM media (xddts: NSMex00494) 22 formatp fails to format an MO in jukeboxes with drives of type S6300.650A (xddts: NSMex00530) 23 importp and inventory do not read platters correctly (xddts: NSMex00531) PHSS_10238: 1 ager dumps core. (xddts: JOSqa00056) 2 kdm_user_thread processes swamp system 3 zstartup does not mount Migrating File Systems, but zshutdown does unmount. zstartup mounts all file systems on the system. (xddts: NSMbb10663, NSMbb10868) 4 zshutdown(1M) manpag 5 Under certain conditions (many qr migout processes, write access to a file which is migrating out at this time) the qr hangs. Access to the qr is impossible (qqr hangs), zls access to a Migrating File System hangs too. Hanging processes cannot be killed, even kill -9 shows no effect.e PHSS_10098: same as PHSS_10097 PHSS_10097: fixes in jfs 1 system panics in kdm_k_query_session() function (SR 5003357210) 2 problems, which were fixed with jfs Patch PHKL_7906: On NFS clients, customers may find that when one of the exported filesystems becomes full, the "vx_nospace" message is displayed through the system message buffer and the writing process keeps retrying the write. This leads to problems when all of the nfs daemons are in this state and are therefore unable to service new incoming requests. Until one or more of the VxFS writes succeeds, the NFS server is effectively down. 3 problems, which were fixed with jfs Patch PHKL_9709: Each time edquota -t is invoked for a VxFS file system, it resets the previously defined file system time limit back to default (7 days). Omnistorage fixes 4 convert_media -m states that the given mount point is not a Migrating File System (xddts: NSMbb11082, SR 1653200170) 5 vsadm -l shows incorrect output vsadm -u exits with wrong exit code (xddts: JOSqa00010) 6 restore_vbfs fails running a selective restore restore_vbfs calls formatp incorrectly (xddts: NSMbb10986, JOSqa00046) 7 "Q_MIG_LOG_OPTIONS in" does not include the file name in the log entry (xddts: NSMbb10827) 8 The qr will not properly shut down during system shut down. (xddts: NSMbb10877, SR 1653195420) PHSS_9583: 1 qrlog contains FATAL entries opening pqd device (xddts: NSMbb10802 SR: B700027532) 2 restore_vbfs asks for extra tape (xddts: NSMbb10801) 3 qr fork gets errno12 trying to mount volumes (xddts: NSMbb10787) 4 Automount of vxfs fails (xddts: NSMbb10789) 5 kdm_usr_thread procs swamp system (xddts: NSMbb10639 SR: 1653190389) 6 xhsm won't connect to client from server (xddts: NSMbb10708) 7 hsm_admin cannot re-mount filesystem (xddts: NSMbb10791 SR: B700027524) 8 Omniback cannot restore vbfs attributes (ERR 12) 9 append to nearline w/ NBLOCKS corrupts file (xddts: NSMbb10784 SR: B700027573) 10 can't configure all drives of 12-drive jukebox (xddts: NSMbb10684) 11 restore_vol missing (xddts: NSMbb10790) Defect Description: PHSS_17474: 1 Scenario for requesting, testing and use a free inode includes creating a tmp-file. Because this tmp-file has no extended file attributes, removing the file causes the ded to write an error message (wrong attribute ver- sion). Level of these messages was changed from error to note, because it is not really an error message. Resolution: This solution prevents massiv error messages during the rebuild command in /var/opt/omnistorage/log/dedlog. 2 Backing up a partial resident file having its first blocks in secondary media, followed by some blocks on magnetic cache, and closed by further blocks on secondary media causes data corruption. This is caused by read_media() by seeking inside the data image buffer only once, when the data image buffer will be created. The position inside the buffer will not be updated by further calls to read_media(). Resolution: Seek inside data image in read_media() function. 3 The qr core dumps on SIGSEGV cause it grew larger than MAXDSIZE due to about 25.000 requests in its request queue. The ager submits an unlimited number of requests to the qr after a timeout of 24 hours even if the qr did not allow it to do that. jmd list handling requires too many comparisons for volume set iteration. Resolution: Decrease size of communication data and optimize search for volume to migrate to. 4 Due to possible inconsistent configuration settings of AGER_HWM, BLOCK_CREATES_WM and BLOCK_CREATES_REMAINING_BLOCKS the ded was blocking file creation as long as these inconsistencies were corrected. The following inconsistent configurations could occur: a) BLOCK_CREATES_REMAINING_BLOCKS > total file system blocks In that case no file system object could be created, even the file system was newly created. b) (100 - BLOCK_CREATES_REMAINING_BLOCKS in percent) < AGER_HWM && used space < AGER_HWM In that case the ded blocked further file creation and forced the ager to start in active mode, but the ager didn't find migration candidates, because the AGER_HWM was not reached. Resolution: Correct watermark inconsistencies during runtime. 5 agerlog shows error messages like ager ERROR ( 2825): 01/13/1999 19:07:02 [CHSM310057] The value for the AGEWEIGHT parameter was invalid; 1 will be used instead. ager ERROR ( 2825): 01/13/1999 19:07:02 [CHSM310058] The value for the SIZEWEIGHT parameter was invalid; 0 will be used instead. Resolution: The if condition for checking the return value of ReadAgerConfigWithFallback() was modified to verify against == 1 instead of != 0. 6 When running a backup based on 'zb' or BRAPI (OB-OMS-Integration) the 'io_server' mounts an hpufs formatted secondary media under "/tmp". This is a potential safeness problem for all data that reside on secondary media. The behaviour was changed to either use the defined JMD_MNTDIR parameter value from /etc/opt/omnistorage/jmcfg or if not defined "/jmd_mnt" as the default. Resolution: The behaviour was changed to either use the defined JMD_MNTDIR parameter value from /etc/opt/omnistorage/jmcfg or if not defined "/jmd_mnt" as the default. 7 Par writes all former read and archived blocks from MO to a destination MO. At the end of writing all remai- ning blocks at the destination will be erased. But if there are no remaining blocks no block has to be erased. Error in the compare instruction of the current block and the total number of blocks causes the problem. Although par exited with error the MO is usable. But par is used by restore_vbfs and this command aborts if par exits with error. Resolution: If there are no remaining free blocks after restoring a MO (number of blocks in the par archive is equal to the number of blocks on MO) then no blocks have to be erased. 8 The jmd is not reporting the errno set by failing malloc(). Resolution: The errno is reported back to the log message. 9 In the case you use files with special characters in their names it is necessary to create an include_ file instead of typing a filespec for selective file restoring. Resolution: A necessary addition under option -f of the "restore_vbfs" man page regarding special characters in a file name has been included. 10 Forcing a file system check on secondary media by the jmd due to mount failures calls 'fsck' with the -y option, which causes an automatically repaired file system, but potential data loss without any possibility to manually intervent. Although 'fsck' repaired the file system and set the clean flag of the superblock to state FS_OK, or FS_CLEAN, a following mount paniced the system. Resolution: Changing the fsck use from option -y to -P instead will have the following effects: - clear indication on file systems which cannot be repaired automatically without potential data loss. Corresponding media will be set to state 'Error'. - no further mount operations will be performed on these media. 11 If OMS detected an empty slot, although there should be a volume in this slot, then the mount request was requeued until the media was available. Now OMS sets the missing volume to state ONSITE, the mount request will fail and the application will get an error code (errno 2). Furthermore there are error mes- sages in the qr and jmd log file and an email to root of the system will be sent. Resolution: Data access to missing secondary media causes an error message to the calling application and set the system errno to 2. 12 A SIDF formatp on MO failes if the MO is a blank one. The formatp command tries to read the label (which consists of '000...' and interpretes this as file system type. Resolution: Prevent the formatp command from erronously interpreting blank labels. 13 If a media was set to state 'Error' due to access problems the corresponding ERROR log message only shows the volume ID, but no drive number. The drive number is helpful when searching the root cause of the problem, i.e. is either the media itself or the drive causing the problem. Resolution: The drive number was added to the log message. 14 The ager running in active mode did not stop to submit migout requests at the AGER_ALWM. Additionally the agerlog showed an error message like: ager WARNING ( 2329): 01/08/1999 18:46:55 [CHSM310090] The active mode ager was unable to move the file system /test down to the ALWM (76%). The current level is 5%. This was caused by a wrong calculation due to a data range overflow. Resolution: Use larger data types for calculation. 15 Defining TMPDIR env variable might cause the jmd to fail when reading the volume set database at startup. The jmd renames the orginal volsets file into a temporary name. The temporary file name is created using the tempnam() HP-UX library routine. Unlike tempnam(3S) man page this routine always uses TMPDIR env variable if it's defined and has a valid value. If the temporary name points to a volume different from /var renaming the original volsets file into a temporary name fails and all volumeset information is missing. Resolution: The tmpnam() library routine is used instead. 16 o rebuild dumps core on 21st volume o rebuild leaks memory o rebuild output doesn't reflect progress Resolution: A progress indicator was implemented and memory leaks removed. 17 'listp -a' displays alias for platters, but when there are no aliases it prints '', which is annoying. Resolution: Prevent printing of '' in the case no alias is available. 18 Heavy file creation on Migrating File Systems in parallel could cause system panics. Resolution: Incorporate bug fixes of PHKL_1621[67] into OmniStorage vxfs kernel libraries. Fix deadlock problems for HSM special code paths. PHSS_15817: 1 The problem is related to problems with some MO-device drivers to handle the verify-after-write correctly. The migout is processed properly if either the verify- after-write function is switched off or the immediate_ report function of the scsi-MO-device is turned off using the HP-UX-command scsictl. Having both parameters turned ON will lead to failing migrations. Therefore the new Omnistorage jmd parameter 'JMD_MO_WORM_SET_VERIFY_WRITE' is set to OFF in the jmcfg configuration file. 2 Zb does not except "q" to respond on the request to either insert a new tape, or to provide a new device path, or to quit the operation. This was caused by a mistype in the source code. The read user input was compared to '1' instead of 'q'. 3 The system hangs during shutdown after all user processes were killed when unmounting file systems of type vxfs, because the system generates a DM_EVENT_PREUNMOUNT event while no OmniStorage event daemon process responds to that event. A modification of /usr/sbin/killall script which excludes the ded from being killed during shutdown solves the problem. The OmniStorage event daemon stays alive and responds to generated events. The original version of the script will be saved as /usr/sbin/killall.save. The system panics after all file systems were successfully unmounted, or during all user processes were killed. This was caused by killing a kdm_user_thread process, which holds a DMAPI token which was never responded to. 4 Printf instruction for log writing gave false value of an array. 5 If a mount request for a secondary media cannot be per- formed because the media is not in state INTERNAL, then the causal migin request was requeued until the media can be mounted. Only a mail to the user root and a log message for the qr were given. Now the qr returns with an error code to the applica- tion. Mail to root and qr log message give an explana- tion about the error code. Error code errno is 2. 6 Platter status check routine is now the same at qr starting time and before submitting migin/migout/trun- cation requests. 7 If end of tape is reached then omnistorage ejects the tape and asks for the next. When then 'q' or 'Q' for 'quit' was entered, Omnistorage tried to close the write/read process, but the tape was already ejected. The tape had to be inserted again. Now the tape handling has been changed. Because a close operation depends on the decision (quit or continue) the user will be asked at first for "quit" or "continue" and then for the next tape. 8 Only platters with state Internal should be backed up. If there are platters belonging to the MFS and have a state which is not INTERNAL, then the user will be asked for continueing or to quit at the beginning of the backup session. With option "-y" a backup can be forced if there are media with a state different to INTERNAL. 9 Under certain circumstances this is a normal behaviour. Therefore the restore_vbfs man page was completed by a caution note. 10 Qr could have memory corruption creating the response to a qqr request. 11 Io_server was saving incorrect string length information for pathnames longer than 255 characters (relative to the mountpoint). And would cause an error when attemp- ting to read the data by the qr. 12 Kernel parameter maxfiles_lim was larger than expected, and used incorrectly, causing the io_server, and clients to overwrite fixed size buffers used in select(). 13 DLT tapes sometimes have invalid file mark directories, and goto end of data will sometimes fail. Add valida- tion and retries. Some performance improvements with positioning tape. Add search performance improvements to allow seeking directly to large images (by writing more filemarks). Two parameters are added to the iocfg for tape: IOS_TAPE_MAX_FILES_PER_FILESET 1023 IOS_TAPE_MAX_DATA_PER_FILESET 20480 PHSS_14839: 1 During cleanup, the ODM filesystem structure is written to an empty platter. This leads to not recognizing the media being available for the freepool anymore. 2 Add a common device type "DLT" as a backup device for bkup_vbfs for using DLT4000/DLT7000. 3 Sync_vbfs was setting each volume (both sides of a platter) back to internal when syncing was completed for that volume. The other side of the platter still needed to be synced. 4 Sometimes write requests cause inward-migration, the qr was not verifying that the data was still resident be- fore setting dirty indications. 5 All OMS client hosts are known to the OMS server by their entry in /etc/opt/omnistorage/jhosts. If the client's host name is followed by an IP-address (of the second lan card), then exporting of file systems of secondary media from the server to the client will be done via the special IP-address otherwise via the default IP-address (first lan card). OMS server exports file systems of secondary media and client trys to mount it via the default IP-address (first lan-card). 6 Under certain circumstances a false tree was passed for generating migout requests so that the request was dropped. Decision tree was corrected. 7 Jmd device capability database completed with infor- mation for DLT 7000. 8 If zmrestore restores inode information and extended attributes of a file that was migrated out at the time the backup archive was created, 100 byte of allocated memory remain unfreed. If zmrestore restores about 600.000 files the amount of unfreed memory hits the standard MAXDSIZE ( 64MB ) and the system hangs. 9 Starting OmniBack from the OmniStorage GUI is failing. When the button is clicked, you get the message: "/usr/omni/bin/xomni: No such file or directory" 10 We substituted the scsi-format_mo by introducing the UNIX-command 'mediainit'. 11 - Creating a new chunk sometimes fails to properly set a dirty flag for the newly created chunk. A new chunk should always be marked dirty. - A new chunk should not have the same mediaid, and fileid as another chunk. - Added some verification to ensure that a image on MO/UFS is not 'grown' by using lseek. lseek() must be used to skip over valid data. - Disabled interrupting because of volume timeouts. This makes migration to MO/UFS media consistent with WORM or tape. The errors where not caused by the interrupts, but appeared more often because of the interrupts. - qr incorrectly causes an error on migin when its volume time slice has expired. The error status on unlock masks the timeout status, and causes the early end message. This fix is only for 'Early End encoun- tered' preceeded by a 'pv_unlock failed' message. 12 Ager was incorrectly locking an invalid range of a file. Preventing the file from being freed from magnetic. 13 Io_server was using 8K block sizes for MO/UFS media. Increased to 32K blocks for default. Allow setting buffer sizes up to 1 meg. ODM endpoint was incorrectly handling read errors. New parameters were added to /etc/opt/omnistorage/brapicfg. The defaults are IOS_WAIT_FOR_CLOSE true IOS_BUFFER_SIZE 32768 14 For every query to the jmd to determine the other side of a volume, a LMServer handle was opened, and not closed. After a number of volumes, the process had too many file descriptors open and was unable to communicate to the jmd. 15 Active mode ager counted number of blocks freed from magnetic in 8K blocks. It should have been counting using 1K blocks. Falls counting causes the ager to migrate out more files as needed. 16 Problem was caused by different errors: - Missing destination directory creation for file recovering. - Incorrect directory creation of temp directories. - Incorrect media state of scratch media during file recovering. 17 Xhsmmgr produces an error message saying format failed because id is already in use. The format did succeed as requested. The lmapi library was inappropriately assigning an error if the id returned after format was not the id requested. Because duplicate volume ids are necessary for syncing now a note will be given. Producing an error message is unsuitable. 18 Program name sync_vbfs was changed to sync_media (OMS 2.20), but unified source code of bkup_vbfs did not pay attention to it. Creation of temp directories on remote clients for bkup_vbfs was incorrect. 19 The parent qr is checking each migin request if it can be responded to (sometimes a client read 'catches up' to readahead and generates a migin event). It does this each time through its main event loop. It checks even migin requests that are generated by 'migin', or qr child attempting to migout part resident chunks. 20 Jmd code was assuming boxes were numbered consecutively starting with 0. If box numbering started with 1, then box 0 was missing and programs had to fail. 21 Restore_vol calls the OmniStorage rebuild command. During the rebuild step inodes will be requested. If there was parallel rebuilds for the same migrating file system, it could occur, that an inode was assigned twice, what caused a system panic. Now multiple restore_vol processes are possible. The first process which calls rebuild causes the other restore_vol to wait until the first one is ready with rebuild. 22 - The io_server was failing to read the data portion of zero-length files (which are not normally migrated). - The io_server was returning a incorrect image id on gotoLastImage() if end-of-media was encountered during write. - The io_server was writing an incorrect File Set Identifier when repairing an incomplete write caused by an early termination of a previous io_server. - The io_server also caused sync_vbfs to fail on the copy of last image, because the cscEnd was encountered by the reader, and the writer attempted to close the short image. - Omnistorage was turning off Verify Writes. Added variables to iocfg to set scsi options for verify writes, write without erase, and exclusive. Correct C cast error. - Error on close of fileset was forgotten. Fix error handling. Part of SSPOMS_7. 23 Chgstate had a limit of 50 for argc (about 48 volumes), more argumets produce an Usage Error message. Now number of arguments is limited by system parameters (command line, buffer size etc.). 24 A switch case contains two break statements, and mo_check_mediatype() is not reached. 25 Command vsdbcheck checks volume set bindings und updates database 26 OmniStorage logging functions write 2 digit year numbers when writing log messages. The OmniStorage ITO Integration product collects water- mark statistic data by calling the omstrmXC monitor template once every hour. Each line of the collected data contains the current date. The year number is written as a 2 digit number. 27 File could be created, written, and migrated in until the filesystem has 0 blocks free. The ded now checks water marks (instead of the qr) and will block creation of file system objects if the file system is above BLOCK_CREATES_WM=98. If file system is filled until 98 %, then the active ager starts to migrate out files to secondary media. Free 2 % can be used to write extended attributes of files, which are to be migrated out. A tunable nospace event generation presumes latest available vxfs/dmapi patches which add two new kernel parameters, vx_nwriters, and vx_enospace_factor. They will be set to defaults by the /sbin/init.d/OMSclient script to make them persistent across reboots. 28 Bulk mode ager had a memory leak. Part of SSPOMS_1. 29 VxFS kernel libraries used and delivered by the Omni- Storage A.02.10 product must be upgraded to the latest available official vxfs patch level PHKL_12858 / PHKL_12859. Part of SSPOMS_5. 30 Bundled patch PHKL_13281 contains not only fixes for SCSI problems but also vxfs fixes, which conflicts with OmniStorage. vxfs fixes of PHKL_13281 are part of this OmniStorage patch. Part of SSPOMS_15. 31 Qr was requesting information from jmd for every request even if drives where unavailable. PHSS_13436: 1 If qr handles several migout requests for more than one Migrating File System, then sometimes change from shared_file_handle to exclusive_file_handle (necessary for file locking) failed. Migration of the file failed with error "file busy". 2 listp -B shows the wrong number of blocks for tape sidf media. The capacity for tape sidf is set after format time. Now the number of blocks is set after format time too for this media. listp shows a warning now, when -B and -f option are used together. 3 Hexadecimal aliases are not resolved by the following jmd utils: chgowner, chgstate, copyp, exportp, formatp, fsckp, listp, loadp, mountp, rmplat, setgrp, unloadp, unmountp. They are needed e.g. for barcodes of tapes stored in alias names. 4 For some storage libraries the external barcode is stored in the volume name. It cannot be deleted or changed. For these cases a new option " -a " for jmdrestore is created. If the option -a is set, the volume names are not recovered. 5 Some part of the HSM system adjusts 0 length migin request to the size of file, should adjust it to size of chunk or a file is truncated to a smaller size since the request was submitted. qr was insensitive, and would fail the request. 6 In the case of failing to set extended attributes for a file that gets restored by zb/zmrestore, the command logs an error message which uses wrong terms, "migrate priority" instead of "residence priority" and "migrate- ahead strategy" instead of "read-ahead strategy". 7 If a media is in drive with reference count 1 and the jmd is shutdown then JMD database and ACSLS database get out of sync. Now an inventory is performed for this media - when jmd starts. 8 Aging a large number of files and other stress operations where qr and/or ager were involved could result in the situation that two processes (qr parent and child or ager) would try to access one file using the same (session, token), the pv_current_session/token. (This is heavily used since the migin performance changes.) Change: Every process which uses pvlib has to open its own pv_session now. 9 After syncing, original and sync copies do not show same free space. Files were not being deleted off the copy. Some messages were promoted to warning level. After removing files, sync_vbfs did nothing. The qr was not marking media as being dirty after processing destroy events (handled as list of truncates). Also, list of truncates did not cause truncate requests. 10 New tape capacities: 3490 400MB (compressed 1.2GB), 3490E 800MB (compressed 1.8MB) are added to the list in the GUI, Format Media dialog. 11 The qr, ager, and migout may punch a hole even if the file chunk has modified data. The problem seems especially evident with bulk aged files. The region map contains a truncate/write detection beyond end of file. Sometimes regions get merged, that means the last region includes part of the file. Events were not set properly on this last region. 12 The currently installed boxes show now additionally (acs.lsm.panel.transport) for drives in removechanger and installchanger if a STK silo is installed. 13 listp did not show volume aliases. New option -a lets display the alias name (external bar-code ID's for STK Silo) in place of the Omnistorage volume ID. jmdrestore has a new -a option which does not restore the alias name field in the Omnistorage volume database where the external bar-code ID is stored for STK Silo. 14 qr opens data image before determining if data is resident and the request needs no migration. At ENOSPC, qr responds to event expecting it to be requeued. 15 For sequential media, media would sometimes end up in error state when a migout request was processed that was larger than the file is currently. 16 The man page, the command usage, displayed in the case of missuse, and the list of options which can be added to the zmdump/zmrestore command are inconsistent. 17 The default zmdump/zmrestore implementation supports 512 byte block size only, which means a poor performance when writing to tape drives. 18 If a file has been grown by writing, then a migin -m occured, truncate events are not enabled for the new region of the file. 19 zb fails to restore files from an archive to a non- Migrating File System. All files are restored, but only with a size of 0 bytes, although the zb(1) man page states: "zb works on standard (non-Migrating File System) file systems as well as on Migrating File Systems." This is not correct. On HP-UX 10.x zb supports Migrating File Systems only. 20 At end of tape , when the physical EOT was detected, the capacity (listp -S ) was very small. Migin of a file leads to "Error" state of the tape. 21 Using 8k block size for reading from MO, and writing to the file system limits access to migrated files. 22 zmrestore error message "Out of phase--get help" The zmrestore failed by reading the header information of the first element in the zmdump archive. The reason were incorrect data type changes in the binary_hdr structure. zb error message "Writing incorrect data for " This problem occured if zb backs up twice a migrated file. The problem was caused by a missing close of the IOS_DataImage object. 23 If calling the restore_vol utility the migsever execut- able failed due to a read access in the NULL page, core was dumped. It behaved that way because wrong parameters were passed to certain function calls. 24 jmdrestore fails when the media file not exists. jsyncdata was changed, mediafile is created in this case and a syncall is performed. 25 removechanger changes the jmcfg file only. Now at the beginning of jmd the volume database and the list of configured boxes are compared. All volumes for which the box is not configured are set to state "Onsite" - so they can be deleted by rmplat if the user wants it. A warning appears in jlog: WARNING (19971): 10/14/97 10:59:25 Volumes of box %d are in database but not configured - set to Onsite. 26 The accepting conditions was restricted to following MinFileSizeDefault=0 <= MinFileSize <= MaxFileSize <= MaxFileSizeDefault=4000000= If the valid range will be overwritten, the default values from the netcfg file will be used. 27 qr is not receiving signals from jmd because signals are blocked. 28 OmniStorage creates many kdm_user_threads (usage of DM_NO_TOKEN). This can cause system to run out of memory and it takes much time (system performance). 29 If hsm_admin is called with the -I option followed by a file system Id (FSID) the command does not check if the given Id is valid. If the file system Id is wrong, hsm_admin sets it to 0x0, which causes later migration to fail. 30 Handling of large numbers of truncates is extremely slow qr child processes do not share resources. 31 Request counting in different places leads to mishand- ling of request counting. 32 Freeing memory twice after truncate and forward requests causes the qr to core dump 33 The jmd formats MO platters using the HP-UX mkfs com- mand. Its version contained in PHSS_12402 calls mkfs with a changed minfree value (5% instead of the default of 10%) which results in a different calculated size after a MO was formatted. 34 The jmd formats MO platters using the HP-UX mkfs com- mand. Its version contained in PHSS_12402 / PHSS_12814 calls mkfs with a changed minfree value (5% instead of the default of 10%) which results in a different cal- culated size after a MO was formatted. This leads to failing operations like copyp, par, and sync_vbfs. PHSS_12814: 1 PHSS_12402.depot doesn't contain the information about the need to hard link the zb executable to zmdump and zmrestore. If PHSS_12402 gets installed it updates the zb command correctly, but leaves zmdump and zmrestore unchanged, i.e. they remain on the previous patch level ( PHSS_10679 ). Using these commands results in corrup- ted zmdump archives, which are not restorable with zmrestore of the current and higher OmniStorage releases. PHSS_12402: 1 Backing up data on Migrating File Systems using OmniBack produces lots of defunct kdm_user_thread processes fil- ling up the systems process table. The system is not usable anymore. This problem only occurs if many nvbda processes back up many Migrating File Systems in paral- lel. Adding a configurable pause in BRRead() in libcheyhsm.sl gives the system time to remove these defunct processes from the process table. See brapicfg(4) for details on how to modify configurable values. 2 After removing files from the filesystem which are migrated out to sidf media the stale space of this media is increased. See listp -S. 3 After migout of a multichunk file, zls shows parts of the file 100% magnetic and clean, even if the chunks are not resident. 4 Mirroring WORM platters fails with error CHSM110045. The code in the io_server sidf endpoint was not imple- mented to handle creating an image with a specific data image identifier for block addressable media. It was implemented for tape and the WORM was trying to use the same code. 5 The zmrestore command dumps core if it runs on a Migrating File System on which files for restore already exist. The reason are locally defined, but not initia- lized pointers of type pv_fh_t. 6 Opening the OmniStorage GUI at the time other appli- cations using a GUI are up and running which request graphical resources OmniStorage shows the error message "Error: Cannot convert string "unspecified_pixmap" to type Pixmap". In this case now default values are used. 7 When a WORM platter is imported via importp the size of free data space is not updated. All space is free and for a 2x platter the space is 637040. The behaviour of the importp was changed. If a WORM media is imported into a jukebox it will be scanned and the free space will be calculated. 8 zmrestore fails to restore an archive which was created by zmdump showing an "Out of Phase -- get help" message. Reading the archive header of the first archive element zmrestore determines a wrong length of its name. When trying to find the beginning of the next archive element it fails. The reason for the problem were wrong data types used in the structure which receives the header information of each archive element when creating an archive using zmdump. 9 After Installation of patch PHSS_10679 OB just aborted the backup session without one file backed up. (Unexpected close from NVBDA). This was due to a ulimit() call in libcheyhsm.sl which wasn't resolved at run time. The problem could be fixed by linking libcheyhsm.sl with libc.1. PHSS_10679: fixes in jfs/dmapi 1 Under certain conditions _vxoms_log() writes behind log buffer boundaries, and overwrites data of the kernel semaphore buffer which causes the system to panic. 2 OmniStorage needs to be adapted to HP-UX kernel patches. [S700] [S800] PHKL_10170 PHKL_10171 PHKL_9413 PHKL_9414 PHKL_10170 supersedes PHKL_10134. PHKL_10171 supersedes PHKL_10135. PHKL_9413 supersedes PHKL_8311, and PHKL_8733. PHKL_9414 supersedes PHKL_8312, and PHKL_8734. 3 Under certain conditions a system panics by killing kdm_user_thread processes, e.g. during system shutdown due to a problem in HP-UX 10.10. fixes in OmniStorage 4 Under certain conditions - the qr may have files open, and the device is still busy - umount of Migrating File Systems will fail. To prevent this the call order of zshutdown was changed to first shutdown OmniStorage daemons, and then umount currently mounted Migrating File Systems. The command returns 1 if shutdown of one or more of the OmniStorage daemons fails, or if umount of one or more of the Migra- ting File Systems fails. If all performed actions were successful it returns 0. If qr shutdown fails the com- mand will not attempt to umount Migrating File Systems. 5 In order to find chunked files, convert_media walks through the file system. At changing from a lower directory to the parent directory opendir() fails and chunked file searching aborts. Above described error message is misleading and false. 6 OmniStorage didn't support HP DLT libraries until now because there were some necessary entries missing in the jmcaps file. 7 zstartup does not check if the ded is running, or not. If the script would try to mount a Migrating File System when the ded is not running the mount would cause to mark the file system as dirty, and fsck would be neces- sary. zstartup now checks for a running ded, and if the ded is not running it exists with value 1. In this case mounts of Migrating File Systems, and starts of Omni- Storage daemons will not be performed. Additionally the call order of mounting Migrating File Systems, and starting OmniStorage daemons was changed to first mount Migrating File Systems, and then start OmniStorage daemons. 8 The problem concerns WORM media. If data is migrated out to the WORM media the capacity of this media reported by listp -f decreases. As soon as a file from this media was migrated in (e.g. head, cat or other reading com- mands) the capacity reported in the column Free is set to 100 % of the media capacity. If the WORM media is filled near 100% and such a migin occures due to any reading operation the next migout operation can fail. As a result of such a failure the state of the WORM media will be set to "Error state". To prevent this some changes were made in the io_server. 9 If the jmd fails to request drive licenses it logs either the JMD_NO_DRIVE_LICENSE, or the JMD_DRIVE_LIC_REQ_FAILS error in the jlog log file. In both cases the corresponding arguments for drive, or box number resp. were given in the wrong order. 10 bkup_vbfs fails to backup migrating file systems containing directories with spaces in its names. The handling of the directory names was changed and now it is possible to backup such migrating file systems with bkup_vbfs. 11 The problem consists of 4 parts: - Files with more than 5 chunks: after each file proces- sing (append) a new chunk is created. Thus the number of 5 is easily reached. The workaround is to avoid a higher number of chunks. - The second reason is a problem of the queuer. If there the difference between the number of received trunca- tion requests and the number of the executed trunca- tion requests exceeds 100 then all incoming truncation requests are stored temporarily on magnetic disc in the file /var/opt/omnistorage/data/qr . The two dif- ferent processes had access to this file, and the file was cut. Thus a lot of truncation requests vanished. - The MO-file-structure(ODM) is based on Inventory-files in each hash-directory. Older Inventory-file entries still remained. This works good but the Inventory-file could grow when a lot of files are created and removed frequently. The Inventory-file is now maintained correctly. - The 'listp -f'-command didn't show the correct free space available on MO. Only after unmount/mount the real free space was displayed. Now the correct space is showed immediately. 12 This problem has two issues. First it is caused by a deadlock in the qr. If the qr migouts a file, and the timeslice scheme causes the cor- responding qr process to requeue the file with the main qr, a deadlock condition may occur because the main qr may also be accessing the same file. Second the rpc clnt_call() does not return after the given timeout is reached due to a possible problem in the HP-UX RPC library. To prevent this the qr uses an alarm timer for receiving a signal if the timeout is reached. 13 The migration of a file to an MO will fail due to a bug in the calculation of the size of that part of the file which will be migrated out. The calculated size is to large, and the operation fails. 14 The chunk creation is not correct when a file is migra- ted out and there is no single MO which has enough free space for the total file. Thus the file has to be chunked to be placed on several platters. When the file is split into more than 2 chunks the migrated file is corrupt. Sometimes it caused a hang. When this corrupted file is going to be migrated in the qr goes into a loop. 15 Writes or reads beyond the end of a file (EOF) caused never ending migin requests if the last 8k block of a file is only partial used and marked clean. Correspon- ding flags for the last managed region of a file are not set correctly. Truncation requests are not handled. After migout the file cannot be read from secondary media. The fix enables the correct setting of managed region flags, and eliminates code that assumes that there must be at least two managed regions associated with every file that has ever been migrated. 16 If an OMS client using NIS reboots the qr cannot establish it's communication with the ded because the ded starts before any NIS service is available. To prevent communication problems the ded restarts auto- matically after the qr was started during system startup procedure. 17 WORM's are not recognized as such on s700 and s800 (D class) machines. Formatting of such a media is also not possible. The reasons for this error are the dif- ferent types of SCSI busses. The handling of this dif- ferent busses was modified and now WORM's are recog- nized on s700 and s800 (D class) machines. 18 When a tape media was filled up to 100% a following migin of a file from that tape caused OMS to show an increased tape capacity. A further migout followed by an additional migin increases the tape capacity again, and the tape gets into state Error. 19 par is not able to write to a WORM and the exit code is 0. The behaviour of par was changed. In the case of an error a value not equal to 0 will be returned. Also writing to a WORM media with par is now possible. To write a par archive to a WORM media via par one has to use a new unformatted WORM as destination for the writing. 20 copyp of WORM is not possible. An error is reported when trying to copy a WORM via copyp. The behaviour of copyp was changed. Now copyp with WORMs is possible. To make a copy of a WORM media via copyp one has to use a new unformatted WORM as destination because also the header information is copied from the source to the destination WORM. 21 par is not able to read a WORM. An error is reported "Read error attempting to read block 637039". The read errors occure when par tries to read the last written block on the media. The handling of reading operations in areas of a WORM where nothing was written to was false. The par command was modified and now it is able to read a WORM. 22 The command formatp fails on older jukeboxes. The problem was that the jmd was not able to handle the drive type S6300.650A. 23 When a platter is imported using importp -m 0 0, a guest id was assigned and the format type was "Inval". The problem was that the jmd was not able to handle the drive type S6300.650A. The jmd is changed and is now able to handle this drive type. All platter operations are possible. PHSS_10238: 1 The ager dumps core when running in bulk mode. The reason are failed malloc() calls if the system runs out of memory when the ager creates lists of files for outward migration. 2 Reading from a file across chunk boundaries creates a lot of kdm_user_thread processes if the chunks are on different media (MO). The kdm_user_threads were created because DmComplexEvent() function attempted to reply before the second chunk was completed because the second chunk was flagged as ASYNC. 3 zstartup mounts all file systems by calling mount -a. In some released versions of zstartup the corresponding lines for mounting are changed to comments, i.e. zstartup does not mount anything. zstartup now accepts -m option to give one or more mount points to be mounted. It only mounts Migrating File Systems. The zstartup(1M) manpage was updated to describe the changed command behaviour. 4 The zshutdown(1M) manpage containes invalid references to files which do not longer exist on HP-UX 10.x . 5 It is caused by a deadlock in the qr. If the qr migouts a file, and the timeslice scheme causes the corresponding qr process to requeue the file with the main qr, a deadlock condition may occur because the main qr may also be accessing the same file. PHSS_10098: same as PHSS_10097 PHSS_10097: fixes in jfs 1 under certain conditions the index of an array was not defined in kdm_k_query_session(). This causes the system to panic. 2 VxFS calls vx_nospace() to print a message on the console that the file system is out of space. For the 10.01 and 10.10 versions of VxFS, vx_nospace() sleeps for 2 seconds before returning to avoid flooding the console with messages. If the NFS client sends a write request and doesn't receive a reply in 2 seconds, the request times out and it sends another request. When the first request comes back with ENOSPC, it discards the message. Thus, the client gets stuck in a loop. The fix was to change the sleep time to 100ms. 3 VxFS quota routine vx_getquota() resets the time limit for root because it thinks root should not have a quota limit. Somehow it ignores the fact that the timelimit fields in root's dqblk structure are used to store the file system time limit. Omnistorage fixes 4 Running convert_media on a Migrating File System with option -m fails with the message that the given mount point is not a Migrating File System. The cause for this behaviour is that the convert_media doesn't call pv_init() function. 5 vsadm -l didn't show the owner and the group of volumeset members although is is described in the manpage vsadm(1M) vsadm -u exits with 1 although it was properly running. 6 restore_vbfs fails running a selective restore because restore_file doesn't call pv_init() function 7 If the Q_MIG_LOG_OPTIONS in the netcfg file is set with parameter "in" the entries for migin logs does not contain the file name of the inward migrated files. 8 The /sbin/init.d/OMSclient script doesn't determine pid's of one or more running qr processes and fails to shut down the qr porperly. PHSS_9583: 1 Errorlog was removed since pqd is not relevant for vxfs fileystems with DMAPI 2-4 fixed code 5 changed event generation for read-ahead 6 Old 9.* path was replaced 7-9 fixed code 10 configure all drives of 12-drive jukebox now possible 11 restore_vol is shipping with this patch SR: 5003357210 1653200170 1653195420 B700027532 B700027524 1653190389 B700027573 5003360925 B700027755 5003354993 5003354993 1653208470 5003356048 5003357608 1653207746 B700028456 B700028506 1653207514 1653261206 1653259788 1653247734 1653225896 5003383265 5003409540 Patch Files: /etc/opt/OV/share/conf/OVLicense/forms/omnistorage/ evaluation /etc/opt/OV/share/conf/OVLicense/forms/omnistorage/ omnistorage.template /etc/opt/OV/share/conf/OVLicense/forms/omnistorage/product /etc/opt/OV/share/conf/OVLicense/forms/omnistorage/ product_update /etc/opt/OV/share/conf/OVLicense/forms/omnistorage/ server_move /etc/opt/omnistorage/brapicfg /etc/opt/omnistorage/dedcfg /etc/opt/omnistorage/sbin/ded /opt/omnistorage/DOC_REPLY /opt/omnistorage/bin/add_vol /opt/omnistorage/bin/aliasp /opt/omnistorage/bin/bkup_vbfs /opt/omnistorage/bin/chgidp /opt/omnistorage/bin/chgowner /opt/omnistorage/bin/chgstate /opt/omnistorage/bin/cleanup /opt/omnistorage/bin/consolidate /opt/omnistorage/bin/convert_media /opt/omnistorage/bin/copyp /opt/omnistorage/bin/exportp /opt/omnistorage/bin/formatp /opt/omnistorage/bin/fsckp /opt/omnistorage/bin/getfsid /opt/omnistorage/bin/hsm_admin /opt/omnistorage/bin/hsm_session /opt/omnistorage/bin/hsm_version /opt/omnistorage/bin/importp /opt/omnistorage/bin/inventory /opt/omnistorage/bin/jmdbackup /opt/omnistorage/bin/jmdrestore /opt/omnistorage/bin/listp /opt/omnistorage/bin/loadp /opt/omnistorage/bin/mif.sh /opt/omnistorage/bin/migin /opt/omnistorage/bin/migmv /opt/omnistorage/bin/migout /opt/omnistorage/bin/migsever /opt/omnistorage/bin/mountp /opt/omnistorage/bin/par /opt/omnistorage/bin/par.sh /opt/omnistorage/bin/qjmd /opt/omnistorage/bin/qqr /opt/omnistorage/bin/rebuild /opt/omnistorage/bin/rebuild.sh /opt/omnistorage/bin/resid /opt/omnistorage/bin/restore_file /opt/omnistorage/bin/restore_file.sh /opt/omnistorage/bin/restore_vbfs /opt/omnistorage/bin/restore_vol /opt/omnistorage/bin/rkill /opt/omnistorage/bin/rmplat /opt/omnistorage/bin/setgrp /opt/omnistorage/bin/unaliasp /opt/omnistorage/bin/unloadp /opt/omnistorage/bin/unmountp /opt/omnistorage/bin/vsadm /opt/omnistorage/bin/vsbind /opt/omnistorage/bin/vsclose /opt/omnistorage/bin/vsdbcheck /opt/omnistorage/bin/vshdr /opt/omnistorage/bin/vsopen /opt/omnistorage/bin/vsread /opt/omnistorage/bin/vsread.sh /opt/omnistorage/bin/vswrite /opt/omnistorage/bin/wt-check /opt/omnistorage/bin/xhsm /opt/omnistorage/bin/xhsmbackup /opt/omnistorage/bin/xhsmmgr /opt/omnistorage/bin/xhsmmonitor /opt/omnistorage/bin/zb /opt/omnistorage/bin/zdf /opt/omnistorage/bin/zerrmsg /opt/omnistorage/bin/zfind /opt/omnistorage/bin/zls /opt/omnistorage/bin/zmdump /opt/omnistorage/bin/zmdump.sh /opt/omnistorage/bin/zmrestore /opt/omnistorage/bin/zmrestore.sh /opt/omnistorage/bin/zshutdown /opt/omnistorage/bin/zstartup /opt/omnistorage/lib/agermsgs.Eng /opt/omnistorage/lib/errmsgs /opt/omnistorage/lib/guimsg.ehdb /opt/omnistorage/lib/jmdmsg.Eng /opt/omnistorage/lib/libTuw.sl /opt/omnistorage/lib/libXmwit.sl /opt/omnistorage/lib/libXtwit.sl /opt/omnistorage/lib/libaspm.sl /opt/omnistorage/lib/libcheyhsm.sl /opt/omnistorage/lib/libd.sl /opt/omnistorage/lib/libteleuse.sl /opt/omnistorage/lib/qrmsgs.Eng /opt/omnistorage/man/man1/ager.1 /opt/omnistorage/man/man1/aliasp.1 /opt/omnistorage/man/man1/chgidp.1 /opt/omnistorage/man/man1/chgowner.1 /opt/omnistorage/man/man1/chgstate.1 /opt/omnistorage/man/man1/cleanup.1 /opt/omnistorage/man/man1/exportp.1 /opt/omnistorage/man/man1/formatp.1 /opt/omnistorage/man/man1/fsckp.1 /opt/omnistorage/man/man1/getfsid.1 /opt/omnistorage/man/man1/importp.1 /opt/omnistorage/man/man1/inventory.1 /opt/omnistorage/man/man1/listp.1 /opt/omnistorage/man/man1/loadp.1 /opt/omnistorage/man/man1/migin.1 /opt/omnistorage/man/man1/migmv.1 /opt/omnistorage/man/man1/migout.1 /opt/omnistorage/man/man1/mountp.1 /opt/omnistorage/man/man1/qjmd.1 /opt/omnistorage/man/man1/qqr.1 /opt/omnistorage/man/man1/rebuild.1 /opt/omnistorage/man/man1/resid.1 /opt/omnistorage/man/man1/restore_file.1 /opt/omnistorage/man/man1/rmplat.1 /opt/omnistorage/man/man1/setgrp.1 /opt/omnistorage/man/man1/unaliasp.1 /opt/omnistorage/man/man1/unloadp.1 /opt/omnistorage/man/man1/unmountp.1 /opt/omnistorage/man/man1/wt-check.1 /opt/omnistorage/man/man1/xhsm.1 /opt/omnistorage/man/man1/zb.1 /opt/omnistorage/man/man1/zdf.1 /opt/omnistorage/man/man1/zerrmsg.1 /opt/omnistorage/man/man1/zfind.1 /opt/omnistorage/man/man1/zls.1 /opt/omnistorage/man/man1m/add_vol.1m /opt/omnistorage/man/man1m/bkup_vbfs.1m /opt/omnistorage/man/man1m/consolidate.1m /opt/omnistorage/man/man1m/convert_media.1m /opt/omnistorage/man/man1m/copyp.1m /opt/omnistorage/man/man1m/hsm_admin.1m /opt/omnistorage/man/man1m/hsm_session.1m /opt/omnistorage/man/man1m/hsm_version.1m /opt/omnistorage/man/man1m/installchanger.1m /opt/omnistorage/man/man1m/jmd.1m /opt/omnistorage/man/man1m/jmdbackup.1m /opt/omnistorage/man/man1m/jmdrestore.1m /opt/omnistorage/man/man1m/par.1m /opt/omnistorage/man/man1m/qr.1m /opt/omnistorage/man/man1m/reconfig.1m /opt/omnistorage/man/man1m/removechanger.1m /opt/omnistorage/man/man1m/restore_vbfs.1m /opt/omnistorage/man/man1m/restore_vol.1m /opt/omnistorage/man/man1m/sync_vbfs.1m /opt/omnistorage/man/man1m/vsadm.1m /opt/omnistorage/man/man1m/vsbind.1m /opt/omnistorage/man/man1m/vsclose.1m /opt/omnistorage/man/man1m/vshdr.1m /opt/omnistorage/man/man1m/vsopen.1m /opt/omnistorage/man/man1m/vsread.1m /opt/omnistorage/man/man1m/vswrite.1m /opt/omnistorage/man/man1m/zmdump.1m /opt/omnistorage/man/man1m/zmrestore.1m /opt/omnistorage/man/man1m/zshutdown.1m /opt/omnistorage/man/man1m/zstartup.1m /opt/omnistorage/man/man4/VScfg.4 /opt/omnistorage/man/man4/agerconfig.4 /opt/omnistorage/man/man4/brapicfg.4 /opt/omnistorage/man/man4/dedcfg.4 /opt/omnistorage/man/man4/iocfg.4 /opt/omnistorage/man/man4/jhosts.4 /opt/omnistorage/man/man4/jmcaps.4 /opt/omnistorage/man/man4/jmcfg.4 /opt/omnistorage/man/man4/logcfg.4 /opt/omnistorage/man/man4/netcfg.4 /opt/omnistorage/man/man4/zb.4 /opt/omnistorage/newconfig/consolcfg.proto /opt/omnistorage/newconfig/ded.inittab /opt/omnistorage/newconfig/dmapi /opt/omnistorage/newconfig/io_server.inetd /opt/omnistorage/newconfig/iocfg.proto /opt/omnistorage/newconfig/jmcaps.proto /opt/omnistorage/newconfig/jmcfg.proto.libman /opt/omnistorage/newconfig/jmcfg.proto.migman /opt/omnistorage/newconfig/libdmapi.700.a /opt/omnistorage/newconfig/libdmapi.800.a /opt/omnistorage/newconfig/libvxfs_adv.700.a /opt/omnistorage/newconfig/libvxfs_adv.800.a /opt/omnistorage/newconfig/libvxfs_base.700.a /opt/omnistorage/newconfig/libvxfs_base.800.a /opt/omnistorage/newconfig/logcommand.proto /opt/omnistorage/newconfig/netcfg.proto /opt/omnistorage/newconfig/rpc.kill.txt /opt/omnistorage/newconfig/rpc.niod.txt /opt/omnistorage/newconfig/synccfg.proto /opt/omnistorage/newconfig/vscfg.proto /opt/omnistorage/sbin/ager /opt/omnistorage/sbin/installchanger /opt/omnistorage/sbin/io_server /opt/omnistorage/sbin/jconvert /opt/omnistorage/sbin/jmd /opt/omnistorage/sbin/qr /opt/omnistorage/sbin/rc.server /opt/omnistorage/sbin/remote-launch /opt/omnistorage/sbin/removechanger /opt/omnistorage/sbin/rpc.kill /opt/omnistorage/sbin/rpc.niod /opt/omnistorage/sbin/sync_vbfs /sbin/init.d/OMSclient /sbin/init.d/OMSserver /usr/lib/X11/app-defaults/XHsm what(1) Output: /etc/opt/OV/share/conf/OVLicense/forms/omnistorage/ evaluation: None /etc/opt/OV/share/conf/OVLicense/forms/omnistorage/ omnistorage.template: None /etc/opt/OV/share/conf/OVLicense/forms/omnistorage/product: None /etc/opt/OV/share/conf/OVLicense/forms/omnistorage/ product_update: None /etc/opt/OV/share/conf/OVLicense/forms/omnistorage/ server_move: None /etc/opt/omnistorage/brapicfg: None /etc/opt/omnistorage/dedcfg: None /etc/opt/omnistorage/sbin/ded: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ PATCH/10_10 PHCO_14254 $Revision: 76.162.1.14.1.65 $ /opt/omnistorage/DOC_REPLY: None /opt/omnistorage/bin/add_vol: None /opt/omnistorage/bin/aliasp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/bkup_vbfs: None /opt/omnistorage/bin/chgidp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/chgowner: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/chgstate: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/cleanup: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/consolidate: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/convert_media: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/copyp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/exportp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/formatp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/fsckp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/getfsid: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/hsm_admin: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/hsm_session: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/hsm_version: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ /opt/omnistorage/bin/importp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/inventory: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/jmdbackup: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/jmdrestore: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/listp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/loadp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/mif.sh: None /opt/omnistorage/bin/migin: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/migmv: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/migout: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/migsever: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/mountp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/par: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/par.sh: None /opt/omnistorage/bin/qjmd: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/qqr: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/rebuild: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/rebuild.sh: None /opt/omnistorage/bin/resid: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/restore_file: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/restore_file.sh: None /opt/omnistorage/bin/restore_vbfs: None /opt/omnistorage/bin/restore_vol: $Id: bm/etc/backup/restore_vol.sh@@/main/oms_2.2_dev _uid/2 97/07/01 14:37:31 $ /opt/omnistorage/bin/rkill: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/rmplat: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/setgrp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/unaliasp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/unloadp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/unmountp: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/vsadm: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/vsbind: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/vsclose: $Release: DB.c,v: OmniStorage_0210$ $Release: st.c,v: OmniStorage_0210$ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/vsdbcheck: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/vshdr: $Release: DB.c,v: OmniStorage_0210$ $Release: st.c,v: OmniStorage_0210$ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/vsopen: $Release: DB.c,v: OmniStorage_0210$ $Release: st.c,v: OmniStorage_0210$ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/vsread: $Release: DB.c,v: OmniStorage_0210$ $Release: st.c,v: OmniStorage_0210$ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/vsread.sh: None /opt/omnistorage/bin/vswrite: $Release: DB.c,v: OmniStorage_0210$ $Release: st.c,v: OmniStorage_0210$ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/wt-check: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/xhsm: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/xhsmbackup: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/xhsmmgr: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Id: gui/lib/widgets/cheytreeelem.c@@/main/oms_2.2_d ev_uid/1 97/08/12 14:57:38 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/xhsmmonitor: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/zb: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: hpux_util.c,v: OmniStorage_0210$ $Id: mm/etc/zb/hpux_util.c@@/main/oms_2.1_fix/3 97/0 7/25 17:55:26 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/zdf: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/zerrmsg: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/zfind: $Revision: 59.1 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/zls: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/zmdump: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: hpux_util.c,v: OmniStorage_0210$ $Id: mm/etc/zb/hpux_util.c@@/main/oms_2.1_fix/3 97/0 7/25 17:55:26 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/zmdump.sh: $Release: zmdump.src OMS.02.10.04$ /opt/omnistorage/bin/zmrestore: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: hpux_util.c,v: OmniStorage_0210$ $Id: mm/etc/zb/hpux_util.c@@/main/oms_2.1_fix/3 97/0 7/25 17:55:26 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/bin/zmrestore.sh: None /opt/omnistorage/bin/zshutdown: $Id: etc/zshutdown.sh@@/main/oms_2.2_dev_uid/3 97/07 /01 14:12:14 $ $Release: OMS.02.20.00 $ /opt/omnistorage/bin/zstartup: $Id: etc/zstartup.sh@@/main/oms_2.2_dev_uid/4 97/08/ 12 17:20:10 $ $Release: zstartup.sh OMS.02.20.00 $ /opt/omnistorage/lib/agermsgs.Eng: None /opt/omnistorage/lib/errmsgs: None /opt/omnistorage/lib/guimsg.ehdb: None /opt/omnistorage/lib/jmdmsg.Eng: None /opt/omnistorage/lib/libTuw.sl: Telesoft AB 1989, 1990, 1991 /opt/omnistorage/lib/libXmwit.sl: None /opt/omnistorage/lib/libXtwit.sl: None /opt/omnistorage/lib/libaspm.sl: libaspm 2.3 10/25/94 Cheyenne Software, Inc. /opt/omnistorage/lib/libcheyhsm.sl: $Id: mm/lib/dslib/dm2pv.c@@/main/oms_2.1_fix/1 97/06 /02 18:05:58 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date$ $Id: mm/lib/misc/openpqd.c@@/main/oms_2.1_fix/1 97/0 6/02 18:06:27 $ $Id: mm/lib/misc/Volume.C@@/main/oms_2.1_fix/2 97/06 /02 18:06:19 $ $Id: mm/lib/misc/fsidparse.c@@/main/oms_2.1_fix/1 97 /06/02 18:06:20 $ $Id: mm/lib/misc/getvolset.c@@/main/oms_2.1_fix/1 97 /06/02 18:06:22 $ $Id: mm/lib/misc/nevermigrate.c@@/main/oms_2.1_fix/1 97/06/02 18:06:26 $ $Id: mm/lib/misc/pqd-io.c@@/main/oms_2.1_fix/1 97/06 /02 18:06:31 $ $Id: mm/lib/misc/portamap.c@@/main/oms_2.1_fix/1 97/ 06/02 18:06:29 $ /opt/omnistorage/lib/libd.sl: Telesoft 1989, 1993 Telesoft AB 1989, 1990, 1991 Telesoft AB 1989, 1990, 1991 Telesoft AB 1989, 1990, 1991 Telesoft AB 1989, 1990 dl_rttype.c 1.20 4/11/90 Telesoft AB 1989, 1990, 1991 Telesoft AB 1989, 1990, 1991 Telesoft AB 1989, 1990, 1991 Telesoft AB 1989, 1990, 1991 Telesoft AB 1989, 1990, 1991 Telesoft AB 1989, 1990, 1991 Telesoft AB 1989, 1990, 1991 /opt/omnistorage/lib/libteleuse.sl: Alsys Inc TeleUSE 3.0 CaOS Library 1990-93 /opt/omnistorage/lib/qrmsgs.Eng: None /opt/omnistorage/man/man1/ager.1: None /opt/omnistorage/man/man1/aliasp.1: None /opt/omnistorage/man/man1/chgidp.1: None /opt/omnistorage/man/man1/chgowner.1: None /opt/omnistorage/man/man1/chgstate.1: None /opt/omnistorage/man/man1/cleanup.1: None /opt/omnistorage/man/man1/exportp.1: None /opt/omnistorage/man/man1/formatp.1: None /opt/omnistorage/man/man1/fsckp.1: None /opt/omnistorage/man/man1/getfsid.1: None /opt/omnistorage/man/man1/importp.1: None /opt/omnistorage/man/man1/inventory.1: None /opt/omnistorage/man/man1/listp.1: None /opt/omnistorage/man/man1/loadp.1: None /opt/omnistorage/man/man1/migin.1: None /opt/omnistorage/man/man1/migmv.1: None /opt/omnistorage/man/man1/migout.1: None /opt/omnistorage/man/man1/mountp.1: None /opt/omnistorage/man/man1/qjmd.1: None /opt/omnistorage/man/man1/qqr.1: None /opt/omnistorage/man/man1/rebuild.1: None /opt/omnistorage/man/man1/resid.1: None /opt/omnistorage/man/man1/restore_file.1: None /opt/omnistorage/man/man1/rmplat.1: None /opt/omnistorage/man/man1/setgrp.1: None /opt/omnistorage/man/man1/unaliasp.1: None /opt/omnistorage/man/man1/unloadp.1: None /opt/omnistorage/man/man1/unmountp.1: None /opt/omnistorage/man/man1/wt-check.1: None /opt/omnistorage/man/man1/xhsm.1: None /opt/omnistorage/man/man1/zb.1: None /opt/omnistorage/man/man1/zdf.1: None /opt/omnistorage/man/man1/zerrmsg.1: None /opt/omnistorage/man/man1/zfind.1: None /opt/omnistorage/man/man1/zls.1: None /opt/omnistorage/man/man1m/add_vol.1m: None /opt/omnistorage/man/man1m/bkup_vbfs.1m: None /opt/omnistorage/man/man1m/consolidate.1m: None /opt/omnistorage/man/man1m/convert_media.1m: None /opt/omnistorage/man/man1m/copyp.1m: None /opt/omnistorage/man/man1m/hsm_admin.1m: None /opt/omnistorage/man/man1m/hsm_session.1m: None /opt/omnistorage/man/man1m/hsm_version.1m: None /opt/omnistorage/man/man1m/installchanger.1m: None /opt/omnistorage/man/man1m/jmd.1m: None /opt/omnistorage/man/man1m/jmdbackup.1m: None /opt/omnistorage/man/man1m/jmdrestore.1m: None /opt/omnistorage/man/man1m/par.1m: None /opt/omnistorage/man/man1m/qr.1m: None /opt/omnistorage/man/man1m/reconfig.1m: None /opt/omnistorage/man/man1m/removechanger.1m: None /opt/omnistorage/man/man1m/restore_vbfs.1m: None /opt/omnistorage/man/man1m/restore_vol.1m: None /opt/omnistorage/man/man1m/sync_vbfs.1m: None /opt/omnistorage/man/man1m/vsadm.1m: None /opt/omnistorage/man/man1m/vsbind.1m: None /opt/omnistorage/man/man1m/vsclose.1m: None /opt/omnistorage/man/man1m/vshdr.1m: None /opt/omnistorage/man/man1m/vsopen.1m: None /opt/omnistorage/man/man1m/vsread.1m: None /opt/omnistorage/man/man1m/vswrite.1m: None /opt/omnistorage/man/man1m/zmdump.1m: None /opt/omnistorage/man/man1m/zmrestore.1m: None /opt/omnistorage/man/man1m/zshutdown.1m: None /opt/omnistorage/man/man1m/zstartup.1m: None /opt/omnistorage/man/man4/VScfg.4: None /opt/omnistorage/man/man4/agerconfig.4: None /opt/omnistorage/man/man4/brapicfg.4: None /opt/omnistorage/man/man4/dedcfg.4: None /opt/omnistorage/man/man4/iocfg.4: None /opt/omnistorage/man/man4/jhosts.4: None /opt/omnistorage/man/man4/jmcaps.4: None /opt/omnistorage/man/man4/jmcfg.4: None /opt/omnistorage/man/man4/logcfg.4: None /opt/omnistorage/man/man4/netcfg.4: None /opt/omnistorage/man/man4/zb.4: None /opt/omnistorage/newconfig/consolcfg.proto: None /opt/omnistorage/newconfig/ded.inittab: None /opt/omnistorage/newconfig/dmapi: None /opt/omnistorage/newconfig/io_server.inetd: None /opt/omnistorage/newconfig/iocfg.proto: None /opt/omnistorage/newconfig/jmcaps.proto: $Release: jmcaps.proto OMS.02.10.04$ /opt/omnistorage/newconfig/jmcfg.proto.libman: None /opt/omnistorage/newconfig/jmcfg.proto.migman: None /opt/omnistorage/newconfig/libdmapi.700.a: $Id: kernel/vxfs/vx_oms_dmattr.c@@/main/4 97/09/09 1 7:23:04 $ $Release: vx_oms_dmattr.c PHSS_10679 (vxomslogbuf us ed) $ $Id: kernel/dmapi/kdm_core.c@@/main/6 97/09/09 17:18 :26 $ $Release: kdm_core.c PHSS_10679 $ vx_kdmi.c OMS A.02.10 PHSS_17474 /opt/omnistorage/newconfig/libdmapi.800.a: $Id: kernel/vxfs/vx_oms_dmattr.c@@/main/4 97/09/09 1 7:23:04 $ $Release: vx_oms_dmattr.c PHSS_10679 (vxomslogbuf us ed) $ $Id: kernel/dmapi/kdm_core.c@@/main/6 97/09/09 17:18 :26 $ $Release: kdm_core.c PHSS_10679 $ vx_kdmi.c OMS A.02.10 PHSS_17474 /opt/omnistorage/newconfig/libvxfs_adv.700.a: $Release: vx_reorg.c PHSS_14839 (PHKL_12606) $ vx_dio.c OMS A.02.10 PHSS_17474 (1.3.89.13 == PHKL_1 6216) /opt/omnistorage/newconfig/libvxfs_adv.800.a: $Release: vx_reorg.c PHSS_14839 (PHKL_12607) $ vx_dio.c OMS A.02.10 PHSS_17474 (1.3.89.13 == PHKL_1 6217) /opt/omnistorage/newconfig/libvxfs_base.700.a: vx_vnops.c Omnistorage 2.10 A.02.10.02 PHSS_10097 (P HKL_9567) $Date: 97/02/10 17:37:48 $ vx_vm.c OMS.02.10.07 PHSS_14839 (PHKL_11504) $Date: 98/05/28 09:40:15 $ vx_vfsops.c OMS.02.10.07 PHSS_14839 (PHKL_11469) $Da te: 98/05/28 09:30:38 $ vx_rdwri.c OMS A.02.10 PHSS_17474 (1.3.89.20 == PHKL _16216) vx_mount.c OMS.02.10.07 PHSS_14839 (PHKL_8349) (PHKL _12858) $Date: 98/05/28 10:15:47 $ vx_inode.c OMS.02.10.07 PHSS_14839 (PHKL_8349) (PHKL _11209) $Date: 98/05/28 08:35:36 $ vx_iflush.c OMS.02.10.07 PHSS_14839 (PHKL_11209) $Da te: 98/05/28 08:46:32 $ vx_dirl.c OMS A.02.10 PHSS_17474 (1.3.89.5 == PHKL_8 349) vx_chain.c OMS A.02.10 PHSS_17474 (1.3.89.11 == PHKL _16509) vx_bsdquota.c OMS.02.10.07 PHSS_14839 (PHKL_9709) (P HKL_11469) (PHKL_12563) $Date: 98/05/28 09:5 0:48 $ vx_bio1.c OMS A.02.10 PHSS_17474 (1.3.89.12 == PHKL_ 16508) vx_bio.c OMS A.02.10 PHSS_17474 (1.3.89.14 == PHKL_1 6508) vx_alloc.c Omnistorage 2.10 A.02.10.02 PHSS_10097 (P HKL_7906) $Date: 97/02/07 17:09:57 $ /opt/omnistorage/newconfig/libvxfs_base.800.a: vx_vnops.c Omnistorage 2.10 A.02.10.02 PHSS_10098 (P HKL_9568) $Date: 97/02/10 17:37:48 $ vx_vm.c OMS.02.10.07 PHSS_14839 (PHKL_11505) $Date: 98/05/28 09:40:15 $ vx_vfsops.c OMS.02.10.07 PHSS_14839 (PHKL_11470) $Da te: 98/05/28 09:30:38 $ vx_rdwri.c OMS A.02.10 PHSS_17474 (1.3.89.20 == PHKL _16217) vx_mount.c OMS.02.10.07 PHSS_14839 (PHKL_8349) (PHKL _12859) $Date: 98/05/28 10:15:47 $ vx_inode.c OMS.02.10.07 PHSS_14839 (PHKL_8350) (PHKL _11210) $Date: 98/05/28 08:35:36 $ vx_iflush.c OMS.02.10.07 PHSS_14839 (PHKL_11210) $Da te: 98/05/28 08:46:32 $ vx_dirl.c OMS A.02.10 PHSS_17474 (1.3.89.5 == PHKL_8 350) vx_chain.c OMS A.02.10 PHSS_17474 (1.3.89.11 == PHKL _16509) vx_bsdquota.c OMS.02.10.07 PHSS_14839 (PHKL_9710) (P HKL_11470) (PHKL_12564) $Date: 98/05/28 09:5 0:48 $ vx_bio1.c OMS A.02.10 PHSS_17474 (1.3.89.12 == PHKL_ 16509) vx_bio.c OMS A.02.10 PHSS_17474 (1.3.89.14 == PHKL_1 6509) vx_alloc.c Omnistorage 2.10 A.02.10.02 PHSS_10098 (P HKL_7907) $Date: 97/02/07 17:09:57 $ /opt/omnistorage/newconfig/logcommand.proto: None /opt/omnistorage/newconfig/netcfg.proto: None /opt/omnistorage/newconfig/rpc.kill.txt: None /opt/omnistorage/newconfig/rpc.niod.txt: None /opt/omnistorage/newconfig/synccfg.proto: None /opt/omnistorage/newconfig/vscfg.proto: None /opt/omnistorage/sbin/ager: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Id: mm/lib/misc/portamap.c@@/main/oms_2.2_dev_uid/1 97/08/12 15:38:50 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/sbin/installchanger: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/sbin/io_server: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/sbin/jconvert: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/sbin/jmd: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: VSDB.x,v: OmniStorage_0210$ $Id: VSDB.x,v 59.1 95/10/04 00:18:49 Cheyenne OmniSt orage_0210 $ %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % $Release: lm_acs.c,v: OMS_Silo - OMS.02.11.03$ $Id: lm/lib/port/lm_acs.c@@/main/1 97/11/13 14:44:30 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_eject/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_lock_dr/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_query_ac/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_query_ca/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_query_dr/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_query_mo/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_query_vo/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_response/2.1.2 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_status/2.0A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_set_access/2.1.1 % %rel ease: % %date_created: Mon Aug 1 10:03:45 1994 % (c) 1994 StorageTek %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsapi/csrc/acs_unlock_dr/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsutl/csrc/acs_get_resp/2.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acslm/cdk2.1 % %full_name: acsutl/csrc/acs_send_req/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acslm/cdk2.1 % %full_name: acsutl/csrc/acs_vary_res/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsutl/csrc/acs_query_res/2.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsutl/csrc/acs_resp_audf/2.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsutl/csrc/acs_cvt_v2_v3/2.01A % %full_name: acsutl/csrc/acs_cvt_v2_v3/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acslm/cdk2.1 % %full_name: acsutl/csrc/acs_cvt_v3_v4/2.01A % %full_name: acsutl/csrc/acs_cvt_v3_v4/2.01A % %full_name: h/incl/acslm/cdk2.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsutl/csrc/acs_cvt_v4_v3/2.1 % %full_name: acsutl/csrc/acs_cvt_v4_v3/2.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acslm/cdk2.1 % %full_name: acsutl/csrc/acs_cvt_v3_v2/2.01A % %full_name: acsutl/csrc/acs_cvt_v3_v2/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acslm/cdk2.1 % %full_name: acsapi/csrc/acs_get_pktver/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % acs_ipc_read.c 2.1.3 1/3/95 (c) 1994 STK %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsipc/csrc/acs_error/2.1 % %full_name: acsipc/csrc/acs_ipc_write/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsipc/csrc/acs_sel_input/2.1 % %full_name: acsipc/csrc/acs_verify_ssi/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % %full_name: acsipc/csrc/acs_get_sock/2.01A % %full_name: h/incl/acsapi/2.1.1 % %full_name: h/incl/apidef/2.1.2 % %full_name: h/incl/apipro/2.1.1 % %full_name: h/incl/acsapi_pvt/2.1.1 % cl_ipc_read.c 5.5 2/7/94 (c) 1994 STK cl_ipc_creat.c 1.1 1/10/94 (c) 1989-1994 STK cl_ipc_write.c 1.1 1/10/94 (c) 1989-1994 STK cl_defs.c 1.1 1/10/94 (c) 1989-1994 STK ml_api.c 1.1 1/10/94 (c) 1989-1994 STK cl_status.c 1.2 1/13/94 (c) 1994 StorageTek cl_el_log_register.c 1.1 1/10/94 (c) 1989-1994 STK cl_el_log.c 1.1 1/10/94 (c) 1989-1994 STK cl_log.c 1.1 1/10/94 (c) 1993-1994 StorageTek cl_trace.c 1.1 1/10/94 (c) 1989-1994 STK cl_ipc_send.c 1.1 1/10/94 (c) 1989-1994 STK cl_ipc_open.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_init.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_qcreat.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_qdelet.c 1.1 1/10/94 (c) 1989-1994 STK dv_api.c 1.1 1/10/94 (c) 1989-1994 STK cl_inform.c 1.1 1/10/94 (c) 1989-1994 STK cl_chk_input.c 1.1 1/10/94 (c) 1989-1994 STK cl_ipc_xmit.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_macces.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_mcreat.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_mdelet.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_mlocat.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_data.c 1.1 1/10/94 (c) 1989-1994 STK cl_type.c 1.2 1/11/94 (c) 1994 StorageTek cl_qm_create.c 1.1 1/10/94 (c) 1989-1994 STK cl_qm_find.c 1.1 1/10/94 (c) 1989-1994 STK cl_select_in.c 1.1 1/10/94 (c) 1989-1994 STK /opt/omnistorage/sbin/qr: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/sbin/rc.server: None /opt/omnistorage/sbin/remote-launch: None /opt/omnistorage/sbin/removechanger: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/sbin/rpc.kill: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/sbin/rpc.niod: $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /opt/omnistorage/sbin/sync_vbfs: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ $Release: OMS.02.10.08 ( HP OmniStorage A.02.10, pat ch level 08, PHSS_17474 ) $ $Date: Wed Apr 21 14:12:08 EDT 1999$ /sbin/init.d/OMSclient: $Id: install/hpdmig/OMSclient.sh@@/main/oms_2.1_fix/ 6 97/10/06 14:55:36 $ /sbin/init.d/OMSserver: None /usr/lib/X11/app-defaults/XHsm: None cksum(1) Output: 4197275965 2760 /etc/opt/OV/share/conf/OVLicense/forms/ omnistorage/evaluation 3672594871 3983 /etc/opt/OV/share/conf/OVLicense/forms/ omnistorage/omnistorage.template 2759368312 2854 /etc/opt/OV/share/conf/OVLicense/forms/ omnistorage/product 882258516 2899 /etc/opt/OV/share/conf/OVLicense/forms/ omnistorage/product_update 3608932933 3089 /etc/opt/OV/share/conf/OVLicense/forms/ omnistorage/server_move 2513829219 443 /etc/opt/omnistorage/brapicfg 3458585536 178 /etc/opt/omnistorage/dedcfg 180854591 596909 /etc/opt/omnistorage/sbin/ded 2114063841 4718 /opt/omnistorage/DOC_REPLY 939108331 6422 /opt/omnistorage/bin/add_vol 3875408247 119519 /opt/omnistorage/bin/aliasp 2221507509 16469 /opt/omnistorage/bin/bkup_vbfs 3471989199 37059 /opt/omnistorage/bin/chgidp 561736192 119513 /opt/omnistorage/bin/chgowner 1653616248 119515 /opt/omnistorage/bin/chgstate 1899954214 342045 /opt/omnistorage/bin/cleanup 2881743587 1015650 /opt/omnistorage/bin/consolidate 3654416944 350081 /opt/omnistorage/bin/convert_media 3351603624 156633 /opt/omnistorage/bin/copyp 2879604162 119516 /opt/omnistorage/bin/exportp 3535841064 123611 /opt/omnistorage/bin/formatp 1584169742 119516 /opt/omnistorage/bin/fsckp 2426613644 185258 /opt/omnistorage/bin/getfsid 2789549510 139974 /opt/omnistorage/bin/hsm_admin 1172289383 239557 /opt/omnistorage/bin/hsm_session 1070460079 49511 /opt/omnistorage/bin/hsm_version 2880964647 119516 /opt/omnistorage/bin/importp 1924982654 131885 /opt/omnistorage/bin/inventory 1977558973 201725 /opt/omnistorage/bin/jmdbackup 2108965031 197616 /opt/omnistorage/bin/jmdrestore 3243901319 131858 /opt/omnistorage/bin/listp 1259344360 119517 /opt/omnistorage/bin/loadp 1423560381 5236 /opt/omnistorage/bin/mif.sh 3560351196 214104 /opt/omnistorage/bin/migin 2182577240 358345 /opt/omnistorage/bin/migmv 26547224 391335 /opt/omnistorage/bin/migout 3026599540 238827 /opt/omnistorage/bin/migsever 4113208882 119516 /opt/omnistorage/bin/mountp 3117382951 156634 /opt/omnistorage/bin/par 2895316150 2723 /opt/omnistorage/bin/par.sh 1568411341 123611 /opt/omnistorage/bin/qjmd 1634354613 131969 /opt/omnistorage/bin/qqr 734305542 1168274 /opt/omnistorage/bin/rebuild 309829242 2046 /opt/omnistorage/bin/rebuild.sh 2196899248 193471 /opt/omnistorage/bin/resid 3874642293 825251 /opt/omnistorage/bin/restore_file 3802126793 2631 /opt/omnistorage/bin/restore_file.sh 3528359270 33542 /opt/omnistorage/bin/restore_vbfs 1655337232 9578 /opt/omnistorage/bin/restore_vol 822112578 20543 /opt/omnistorage/bin/rkill 3741997660 119515 /opt/omnistorage/bin/rmplat 2800190818 119515 /opt/omnistorage/bin/setgrp 1917406727 119515 /opt/omnistorage/bin/unaliasp 529234046 119520 /opt/omnistorage/bin/unloadp 3580590359 119516 /opt/omnistorage/bin/unmountp 3040657336 152437 /opt/omnistorage/bin/vsadm 468972250 358346 /opt/omnistorage/bin/vsbind 4275467852 185455 /opt/omnistorage/bin/vsclose 3136772409 1346392 /opt/omnistorage/bin/vsdbcheck 3016429947 185456 /opt/omnistorage/bin/vshdr 13657870 189555 /opt/omnistorage/bin/vsopen 2794245531 185455 /opt/omnistorage/bin/vsread 2108721819 2211 /opt/omnistorage/bin/vsread.sh 3762821774 185458 /opt/omnistorage/bin/vswrite 947196467 197624 /opt/omnistorage/bin/wt-check 3857255415 523466 /opt/omnistorage/bin/xhsm 3501231690 1576192 /opt/omnistorage/bin/xhsmbackup 2239551629 2572983 /opt/omnistorage/bin/xhsmmgr 2371559827 1329139 /opt/omnistorage/bin/xhsmmonitor 2768902006 956956 /opt/omnistorage/bin/zb 1336340795 255337 /opt/omnistorage/bin/zdf 747468856 24669 /opt/omnistorage/bin/zerrmsg 2177397693 407969 /opt/omnistorage/bin/zfind 3010566465 209960 /opt/omnistorage/bin/zls 2768902006 956956 /opt/omnistorage/bin/zmdump 2380844518 2877 /opt/omnistorage/bin/zmdump.sh 2768902006 956956 /opt/omnistorage/bin/zmrestore 2385830771 3105 /opt/omnistorage/bin/zmrestore.sh 1066883690 5992 /opt/omnistorage/bin/zshutdown 2905593586 6679 /opt/omnistorage/bin/zstartup 877989818 8161 /opt/omnistorage/lib/agermsgs.Eng 4168496969 542521 /opt/omnistorage/lib/errmsgs 2396668980 579704 /opt/omnistorage/lib/guimsg.ehdb 3644515984 36763 /opt/omnistorage/lib/jmdmsg.Eng 3595513558 495616 /opt/omnistorage/lib/libTuw.sl 2676968777 356352 /opt/omnistorage/lib/libXmwit.sl 1162527178 45056 /opt/omnistorage/lib/libXtwit.sl 1047426750 1216512 /opt/omnistorage/lib/libaspm.sl 3869983359 1375735 /opt/omnistorage/lib/libcheyhsm.sl 1673514177 675840 /opt/omnistorage/lib/libd.sl 39025655 491520 /opt/omnistorage/lib/libteleuse.sl 1718563918 50070 /opt/omnistorage/lib/qrmsgs.Eng 1143750573 10418 /opt/omnistorage/man/man1/ager.1 1476529581 1260 /opt/omnistorage/man/man1/aliasp.1 2603371226 755 /opt/omnistorage/man/man1/chgidp.1 1126934827 2202 /opt/omnistorage/man/man1/chgowner.1 716297371 2752 /opt/omnistorage/man/man1/chgstate.1 4165784075 2252 /opt/omnistorage/man/man1/cleanup.1 59459585 3274 /opt/omnistorage/man/man1/exportp.1 3235475233 5848 /opt/omnistorage/man/man1/formatp.1 846375468 1658 /opt/omnistorage/man/man1/fsckp.1 2495533396 972 /opt/omnistorage/man/man1/getfsid.1 2706173976 2500 /opt/omnistorage/man/man1/importp.1 2181198348 2511 /opt/omnistorage/man/man1/inventory.1 1022675217 8844 /opt/omnistorage/man/man1/listp.1 2892090468 2246 /opt/omnistorage/man/man1/loadp.1 3901634508 1576 /opt/omnistorage/man/man1/migin.1 3591541160 866 /opt/omnistorage/man/man1/migmv.1 3446775530 3523 /opt/omnistorage/man/man1/migout.1 1507967923 1845 /opt/omnistorage/man/man1/mountp.1 477784172 2785 /opt/omnistorage/man/man1/qjmd.1 4021448129 4475 /opt/omnistorage/man/man1/qqr.1 2092703252 5375 /opt/omnistorage/man/man1/rebuild.1 599244889 9179 /opt/omnistorage/man/man1/resid.1 3229646283 2803 /opt/omnistorage/man/man1/restore_file.1 2479172449 907 /opt/omnistorage/man/man1/rmplat.1 175472764 1859 /opt/omnistorage/man/man1/setgrp.1 3775927644 799 /opt/omnistorage/man/man1/unaliasp.1 3040877824 872 /opt/omnistorage/man/man1/unloadp.1 3332158967 813 /opt/omnistorage/man/man1/unmountp.1 2458551642 1119 /opt/omnistorage/man/man1/wt-check.1 2220990685 830 /opt/omnistorage/man/man1/xhsm.1 4073510987 11335 /opt/omnistorage/man/man1/zb.1 1638612182 3094 /opt/omnistorage/man/man1/zdf.1 434979837 3081 /opt/omnistorage/man/man1/zerrmsg.1 3750817200 3610 /opt/omnistorage/man/man1/zfind.1 307066351 6177 /opt/omnistorage/man/man1/zls.1 3819569649 4738 /opt/omnistorage/man/man1m/add_vol.1m 900268984 7608 /opt/omnistorage/man/man1m/bkup_vbfs.1m 2627032022 3136 /opt/omnistorage/man/man1m/consolidate.1m 2841044466 2701 /opt/omnistorage/man/man1m/convert_media.1m 2181052567 3674 /opt/omnistorage/man/man1m/copyp.1m 1570561520 3558 /opt/omnistorage/man/man1m/hsm_admin.1m 4098492572 3193 /opt/omnistorage/man/man1m/hsm_session.1m 3588124607 1843 /opt/omnistorage/man/man1m/hsm_version.1m 3131294103 1091 /opt/omnistorage/man/man1m/installchanger.1m 393050762 3305 /opt/omnistorage/man/man1m/jmd.1m 1061414322 3144 /opt/omnistorage/man/man1m/jmdbackup.1m 3124734706 1587 /opt/omnistorage/man/man1m/jmdrestore.1m 3866337422 2534 /opt/omnistorage/man/man1m/par.1m 3977664500 5380 /opt/omnistorage/man/man1m/qr.1m 3186186688 1830 /opt/omnistorage/man/man1m/reconfig.1m 1786415196 890 /opt/omnistorage/man/man1m/removechanger.1m 3250195936 11323 /opt/omnistorage/man/man1m/restore_vbfs.1m 1672878799 2876 /opt/omnistorage/man/man1m/restore_vol.1m 3080443798 2911 /opt/omnistorage/man/man1m/sync_vbfs.1m 2794057395 6608 /opt/omnistorage/man/man1m/vsadm.1m 4233487303 5865 /opt/omnistorage/man/man1m/vsbind.1m 2215037622 884 /opt/omnistorage/man/man1m/vsclose.1m 2291001608 2823 /opt/omnistorage/man/man1m/vshdr.1m 502844870 4363 /opt/omnistorage/man/man1m/vsopen.1m 189395727 1284 /opt/omnistorage/man/man1m/vsread.1m 2209570797 2072 /opt/omnistorage/man/man1m/vswrite.1m 1236136388 4263 /opt/omnistorage/man/man1m/zmdump.1m 2076356077 6542 /opt/omnistorage/man/man1m/zmrestore.1m 3505784678 733 /opt/omnistorage/man/man1m/zshutdown.1m 1922208699 1356 /opt/omnistorage/man/man1m/zstartup.1m 2792023719 4620 /opt/omnistorage/man/man4/VScfg.4 477153755 1003 /opt/omnistorage/man/man4/agerconfig.4 130775081 1228 /opt/omnistorage/man/man4/brapicfg.4 3801769037 733 /opt/omnistorage/man/man4/dedcfg.4 3699421890 553 /opt/omnistorage/man/man4/iocfg.4 1066884475 2715 /opt/omnistorage/man/man4/jhosts.4 4075518325 10437 /opt/omnistorage/man/man4/jmcaps.4 1079597756 6948 /opt/omnistorage/man/man4/jmcfg.4 784791901 4096 /opt/omnistorage/man/man4/logcfg.4 1703685993 12592 /opt/omnistorage/man/man4/netcfg.4 3190941223 3975 /opt/omnistorage/man/man4/zb.4 819433222 82 /opt/omnistorage/newconfig/consolcfg.proto 2439923803 91 /opt/omnistorage/newconfig/ded.inittab 3840006758 4014 /opt/omnistorage/newconfig/dmapi 3461492041 132 /opt/omnistorage/newconfig/io_server.inetd 632870657 1231 /opt/omnistorage/newconfig/iocfg.proto 3543865059 5213 /opt/omnistorage/newconfig/jmcaps.proto 888199609 2505 /opt/omnistorage/newconfig/jmcfg.proto.libman 3273881640 510 /opt/omnistorage/newconfig/jmcfg.proto.migman 1447411434 110336 /opt/omnistorage/newconfig/libdmapi.700.a 1193978497 110336 /opt/omnistorage/newconfig/libdmapi.800.a 1120011385 63476 /opt/omnistorage/newconfig/ libvxfs_adv.700.a 819221188 63476 /opt/omnistorage/newconfig/libvxfs_adv.800.a 3308757163 523444 /opt/omnistorage/newconfig/ libvxfs_base.700.a 1768514276 523360 /opt/omnistorage/newconfig/ libvxfs_base.800.a 359842242 714 /opt/omnistorage/newconfig/logcommand.proto 845954341 1947 /opt/omnistorage/newconfig/netcfg.proto 3938738897 167 /opt/omnistorage/newconfig/rpc.kill.txt 1302875731 173 /opt/omnistorage/newconfig/rpc.niod.txt 4110174012 82 /opt/omnistorage/newconfig/synccfg.proto 1615835744 519 /opt/omnistorage/newconfig/vscfg.proto 3614488511 771467 /opt/omnistorage/sbin/ager 2691670012 169439 /opt/omnistorage/sbin/installchanger 907346552 1627034 /opt/omnistorage/sbin/io_server 3706963011 69725 /opt/omnistorage/sbin/jconvert 138817580 1454098 /opt/omnistorage/sbin/jmd 2801024955 1617140 /opt/omnistorage/sbin/qr 3741092173 135 /opt/omnistorage/sbin/rc.server 3439341820 2124 /opt/omnistorage/sbin/remote-launch 1329875905 198368 /opt/omnistorage/sbin/removechanger 1474237575 20549 /opt/omnistorage/sbin/rpc.kill 25661219 49455 /opt/omnistorage/sbin/rpc.niod 2995279841 979138 /opt/omnistorage/sbin/sync_vbfs 2280091561 2460 /sbin/init.d/OMSclient 4196960252 1370 /sbin/init.d/OMSserver 2407436376 19081 /usr/lib/X11/app-defaults/XHsm Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_9583 PHSS_10097 PHSS_10098 PHSS_10238 PHSS_10679 PHSS_12402 PHSS_12814 PHSS_13436 PHSS_14839 PHSS_15817 Equivalent Patches: PHSS_17475: s700: 10.20 s800: 10.20 Patch Package Size: 34270 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_17474 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_17474.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHSS_17474.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_17474. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHSS_17474.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_17474.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: Please note that all required HP-UX patches and the Test Product need to be installed prior to installing the product patch. Patch includes the following SSP patches: SSPOMS_1 SSPOMS_5 SSPOMS_7 SSPOMS_12 SSPOMS_14 SSPOMS_15 SSPOMS_18 SSPOMS_19 SSPOMS_21 SSPOMS_23 SSPOMS_25 SSPOMS_27 SSPOMS_31 Installation Instructions: 1> Become root user 2> Install this patch by running swinstall. swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_17474.depot \ PHSS_17474 NOTE: Because of defect number 1 the 'JMD_MO_WORM_SET_VERIFY_WRITE' parameter for SCSI drives is set to OFF. Do not change this value unless instructed to do so by an HP Support engineer.