|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
HP-UX series 800 10.X patch digest
From: IT Resource Center (support_feedback
us-support2-mail.external.hp.com)
Date: Sun Jun 15 2003 - 07:33:43 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
HP Support Information Digests
===============================================================================
o IT Resource Center World Wide Web Service
---------------------------------------------------
If you subscribed through the IT Resource Center and would
like to be REMOVED from this mailing list, access the
IT Resource Center on the World Wide Web at:
http://support.itrc.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Support Information Digests (located under
Maintenance and Support). You may then unsubscribe from the
appropriate digest.
To download a patch referenced below, access the
IT Resource Center on the World Wide Web at:
http://support.itrc.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly HP-UX series 800 10.X patch digest
Created: Sun Jun 15 6:05:02 EDT 2003
Table of Contents:
Document ID Title
--------------- -----------
PHSS_29237 s700_800 10.20 ISEE EMS event too large error
PHSS_28460 s700_800 10.20 OV OST3.0 Cumulative A.03.00 patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_29237
Date Loaded: 20030612
Title: s700_800 10.20 ISEE EMS event too large error
Patch Name: PHSS_29237
Patch Description: s700_800 10.20 ISEE EMS event too large error
Creation Date: 03/05/28
Post Date: 03/06/12
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
Isee_EmsListener.ISEE-EMSLSTNR 02.50 03.00
Filesets:
Isee_EmsListener.ISEE-EMSLSTNR,A.10.01.00
Isee_EmsListener.ISEE-EMSLSTNR,A.10.01.01
Isee_EmsListener.ISEE-EMSLSTNR,A.10.01.02
Isee_EmsListener.ISEE-EMSLSTNR,A.10.01.03
Isee_EmsListener.ISEE-EMSLSTNR,A.10.01.04
Isee_EmsListener.ISEE-EMSLSTNR,A.10.01.05
Isee_EmsListener.ISEE-EMSLSTNR,A.10.02.00
Isee_EmsListener.ISEE-EMSLSTNR,A.10.02.01
Isee_EmsListener.ISEE-EMSLSTNR,A.10.02.02
Isee_EmsListener.ISEE-EMSLSTNR,A.10.02.03
Isee_EmsListener.ISEE-EMSLSTNR,A.10.02.04
Isee_EmsListener.ISEE-EMSLSTNR,A.10.02.05
Isee_EmsListener.ISEE-EMSLSTNR,A.10.02.06
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_29237
Symptoms:
PHSS_29237:
If the EMS subsystem sends an event that is larger than
10K bytes ISEE will generate an EMS listener error, and
will not be able to provide any information regarding the
actual hardware error
Defect Description:
PHSS_29237:
ISEE does not accept any EMS event whose size is greater
than the specified EMS limit of 10K bytes
SR:
8606282936
Patch Files:
/./opt/hpservices/contrib/emsListener/bin/rstlistener
what(1) Output:
/./opt/hpservices/contrib/emsListener/bin/rstlistener:
$Header: /PHSS_29237/PHSS_29237.doc 1 2003/06/05 09:
33:10 -0600 fisher $
$Header: /PHSS_29237/PHSS_29237.doc 1 2003/06/05 09:
33:10 -0600 fisher $
cksum(1) Output:
1602855326 45056 /./opt/hpservices/contrib/emsListener/bin/
rstlistener
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_29238:
s800: 11.00
Patch Package Size: 70 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_29237
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_29237.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_29237. 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_29237.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_29237.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_29237------------------------------------------
Document ID: PHSS_28460
Date Loaded: 20030610
Title: s700_800 10.20 OV OST3.0 Cumulative A.03.00 patch
Patch Name: PHSS_28460
Patch Description: s700_800 10.20 OV OST3.0 Cumulative A.03.00 patch
Creation Date: 03/06/09
Post Date: 03/06/10
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
HP OpenView OmniStorage A.03.00.00
Filesets:
OMS.f_server,A.03.00.00 OMS.f_client,A.03.00.00
OMS.common,A.03.00.00 OMS.f_gui,A.03.00.00
OMS.f_fs,A.03.00.00 OMS.manpages,A.03.00.00
OMS.documents,A.03.00.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_28460
Symptoms:
PHSS_28460:
1. Id = NSMex04921
There are 2 problems noticed when using OmniStorage
migout command in next case: "migout -m VolumeSpec
files(s)":
- Files are not migrated on specified volume.
They are migrated on some other volumes.
- If the file is divided in chunks, only first
chunk is properly migrated on specified
volume. All other chunks are migrated on
some other volumes.
2. Id = NSMbb29322
It would be useful to have OmniStorage "zdu" command
implemented. It should return the real disk-space in
use (magnetic + nearline) per file. HP-UX command
"du" returns only magnetic part.
3. Id = NSMbb37713
It would be useful to have new option for OmniStorage
"listp" command implemented. With it, "listp" should
display additional information about media like real
ID and barcode.
4. Id = NSMex02040
Configuring new box using OmniStorage
"installchanger" command should be easier.
The only way of choosing hardware path, box type or
drive is using copy/paste functionality.
5. Id = NSMex02294
There is an error message in "jlog" file:
"ERROR (27353): 04/08/1999 16:50:20 [CHSM230501]
Virtual free went below 0 unexpectedly for volume
618bc7 on a size request of 7927."
6. Id = NSMex03223
On OmniStorage client-server system, with configured
MO device, "exportlog" file fills up with following
messages:
"exportfs error: /jmd_mnt/<VolumeSpec>: Invalid
argument"
7. Id = NSMbb37708
OmniStorage "jmdrestore" command as an output only
shows if restore finished successfully or not.
It would be useful to have additional status line for
each media.
8. Id = NSMbb29373
GUI "Outstanding Requests" graph slowly shows orange
band over 4 days that keeps growing and never resets.
It would be better to see real time requests and not
cumulative, or allow a way to reset that graph.
9. Id = JOSqa00321
It seems that "ager" parameters "AGER_ACTIVELIMIT"
and "AGER_BULKLIMIT" are redundant.
10.Id = JOSqa00306
Migration fails if "jmd" does not export secondary
media.
11.Id = JOSqa00233
Multiple "importp -i StorageSlot" command fail when
drive is empty.
If some platters are manually imported in device
(from the control panel), and then added under
OmniStorage control (with "importp" command), there
is an error message:
"Specified slot is empty".
12.Id = JOSqa00217
It would be useful to have implemented OmniStorage
command for creating a new Migration File System
(MFS).
13.Id = JOSqa00128
OmniStorage command "jmd -c" does not provide correct
information about supported devices.
14.Id = NSMex02664
"bkup_vbfs" command (full backup of Migration File
System) does not work on pure server and pure client.
15.Id = JOSqa00202
"xhsmmonitor" and "qqr -g" OmniStorage commands (GUI
and CLI commands) show a proper number of outstanding
"migin" requests, but "qqr" command does not show
them.
16.Id = NSMex02622
Restore of a single file fails if it is executed
through GUI.
17.Id = NSMex02033
If a system has a lot of migration requests in the
queue, "qqr" reports overflows and does not return
complete list of outstanding requests.
18.Id = JOSqa00275
Execution of "vsadm -l vs_name" command causes memory
leak.
19.Id = NSMbb37707
"exportp" command through GUI works with a wrong
parameter.
20.Id = NSMex04278
OmniBack-OmniStorage integration does not work
properly. OmniBack backup session started on
OmniStorage Migrating File System fails with
following error:
"Got unexpected close from vbda".
21.Id = NSMbb29360
If transition link /bin -> /usr/bin is missing
installation of OmniStorage related shell scripts
fails.
22.Id = NSMbb37710
On OmniStorage system with Grau Silo device used
media listed through GUI is unsorted.
23.Id = JOSqa00341
During inactive aging, percentage of free space on
second device layer is not moved down to specified
"VS_ILWM" value.
24.Id = NSMex01986
It would be useful to have an automatic zombie
cleaner in "ded".
25.Id = JOSqa00337
"consolidate" fails for third migration layer.
26.Id = HSLco36039
"rebuild" functionality does not handle SIGUSR1,
SIGUSR2, SIGTSTP signals.
27.Id = HSLco35959
"unloadp" command cannot always unload platter.
28.Id = NSMex05500
Migration (partially) failing.
29.Id = NSMex05712
There is a huge number of "jmd" zombie processes
present on OmniStorage system.
30.Id = HSLco20183
Unsafe memory allocation calls.
31.Id = JOSqa00146
"hsm_session" command should allow killing of
immortal sessions.
32.Id = HSLco38068
"zls" command for zero-length file does not show
correct output.
33.Id = NSMex05709
Database is wrongly updated in case of a failing
unload.
34.Id = NSMex05578
OmniStorage should have possibility to automatically
unload a tape.
35.Id = HSLco37497
"qqr" command shows duplicate "migin" requests.
36.Id = NSMex05736
If "migin" and "migout" commands are run at the same
time, migration getting slow.
37.Id = NSMex06066
"SyncDirty" flag should be updated when mirror is
reformatted.
38.Id = NSMbb48254
If we try to migrate out a file larger than one side
of a WORM media, the migration process starts with
the first free media and does not stop until all
free/available medias are used.
39.Id = JOSqa00117
When doing large numbers of "migin" requests then
"qr" spends too much time checking if requests still
need to be done. This makes the migins (and
forwarding of "migin" requests to child) extremely
slow.
40.Id = NSMbb49679
Size calculation problems for WORM media.
PHSS_25370:
1. Id = NSMex04098
'par' command fails when the source platter
has more blocks than the destination platter.
2. Id = NSMex04227
'listp -B' shows wrong number of rawblocks for
tape device after migration is started.
'listp' man page needs rework to specify full
detail for '-B' and '-S' options.
3. Id = NSMex04140
The system hangs/panics when a big number
of files, migrated to MOs, are deleted.
4. Id = NSMbb38043
After about 307,000 files, further migration
(migout) to a 5.2GB MO was not possible.
The 'ager' was able to run and to find migration
candidates, but the physical 'migout' failed.
5. Id = NSMbb41618
The 'qqr' output does not have any request in
the queue, although some of the requests in the
truncation lists
(from /var/opt/omnistorage/data/qr directory)
are not completed yet. If we restart the 'qr',
it checks if there are some truncation requests
left and starts with their processing.
6. Id = HSLco27922
'par' attempts to assign guest IDs to platters.
After it fails, it displays an error message:
'Unable to set guest flag for volume fa11.
JMD error: Volume belongs to a volume set'
7. Id = NSMex04573
'listp' always shows the wrong free space for
Worm media after migration and after
performing an 'exportp/importp' command.
8. Id = NSMex04421
'listp' always shows less space on the mirror
platter, after 'sync_media' finished.
9. Id = NSMex03489
'sync_media' does not work when media is hpufs
and it is write protected.
10.Id = HSLco28605
SIDF API fails to write file set and volume
trailer.
11.Id = JAGad49998
There was no logging during the manual execution
of the 'exportp/importp' commands.
12.Id = NSMbb29315
Logging not resumed after space was freed in
'/var'.
13.Id = NSMbb29275
Keep track or warn user if a platter is manually
mounted/loaded.
14.Id = NSMbb29271
'vsbind' allows to bind foreign volume sets to
a MFS.
15.Id = NSMbb41726
If the 'jmd' is killed while the 'qr' queue is
filled up, the used platter volume remains mounted.
16.Id = NSMex04451
'qr' fails to mount platters file system through
NFS.
Error reported in qr log:
"jmountv() failed, jerrno 'Can't mount volume's
filesystem'"
"The qr could not mount/load the volumes and the
jmd is remote. Fix: Check jmd's remote database."
17.Id = NSMbb29294
Lack of media caused a filled file system and core
dump.
18.Id = HSLco30178
man page for 'consolidate' command should be
changed
19.Id = HSLco23197
In /etc/opt/omnistorage/ directory there is
no 'agercfg' file. Some configuration files
need update of documentation.
PHSS_22743:
1. Id = NSMex03222
The device files created by installchanger for DLT
devices are incorrect.
2. Id = NSMex03959
zls showing 100% magnetic while only last block of
chunk on magnetic.
3. Id = NSMex03925
Free space on sidf media is not very well
managed/calculated.
4. Id = NSMex04140
Ager and other OMS commands are just hanging while
going through the list of mounted file systems.
5. Id = NSMex03844
Second tape is never loaded in stacker mode.
6. Id = NSMex04154
migout -m switch didn't work as described in man
page.
7. Id = NSMex04098
Write a par archive to MO volume exits with error
"Can't erase the remaining media start = ..."
PHSS_21065:
1. Id = HSLco20318
Consolidate: purify reports FNH error
2. Id = HSLco19774
jmd dumps core if jukebox is not connected
3. Id = NSMex03366
jmdbackup/jmdrestore fails in case of Grau or
barcode-name boxes
4. Id = NSMex03260
Free space on mirror smaller then original
5. Id = HSLco18392
zstartup and zshutdown scripts don't work correctly
in case that OMS server and client are on different
machines
6. Id = NSMex03037
An attempt to get id of other side of media 10000
failed
7. Id = NSMex03020
Last volume from GRAU didn't pass to jmd database
8. Id = NSMex02823
The migin performance dropped significantly after an
upgrade to 3.0. This problem appears in case of
WORM media
9. Id = JAGab76149, NSMex02958
rpc number problem
10. Id = NSMex02745, NSMex03270
Migout from the client system doesn't work.
The behavior we see is that the request is just
staying in the queue forever and there is no error
message logged anywhere.
11. Id = JOSqa00342
problem with add_vol man page and some errors in log
files
12. Id = NSMex02672
The qr hangs on trying to migrate zero length files
13. Id = NSMex02653
Confusing messages on CLEANUP
14. Id = NSMex02636
wt-check hangs when processing files with size 0
15. Id = NSMex02627
The man page has no list of supported JB devices
16. Id = NSMex02624
Massive migouts failing
17. Id = HSLco20623
Installchanger doesn't show us possible HW address
18. Id = HSLco20331
Purified jmd reports free memory read error.
After reviewing code found out that license removal
was completely wrong.
19. Id = NSMex03270
qr can't start because jmd can't give license to
qr. Reports an error message that there is no
license for that machine.
20. Id = JOSqa0034
Consolidate coredump, run out of memory
21. Id = NSMex03473
jmdrestore will never restore onsite volumes.
22. Id = NSMex03121
When ded check free space on /usr dir
(from /etc/fstab mount config file)
system panic occur.
23. Id = HSLco21464
Fibre Channel data transfer not supported
24. Id = HSLco21524
mediaset and mediaformat tools not available
for OmniStorage 3.0.
25. Id = NSMex03537
Rebuild doesn't work properly if both paths
in the dual path mount point have an
underscore.
An extra path appears when we have a dual
path mount point.
26. Id = NSMbb37517
OMS delete guest media from database (DB)
while inventory is performed.
27. Id = HSLco21556
what(1) command of some OMS binaries still
shows OmniStorage_0210
28. Id = NSMex03564
starting jmdrestore command, message 'not fully
implemented' was shown
29. Id = NSMex03588
hsm_session -ka doesn't work as documented
PHSS_19038:
1. Id = NSMex02262
ager writes annoying "logging started/stopped"
messages into agerlog
2. Id = JOSqa00325
resid man page is not understandable
3. Id = JOSqa00324
rebuild man page examples have old syntax
4. Id = NSMex02367
multi level migration doesn't free space on
secondary layer
5. Id = JOSqa00327
zls -l shows wrong output
6. Id = NSMex02401
consolidate problems
7. Id = JOSqa00328
Consolidation of tapes - full until physical EOT
failed
8. Id = NSMex02450, NSMex02335, NSMex02478, NSMex0243
qr drops migout request for files in bulk mode
9. Id = NSMex02452
jmdrestore -f 99Jun01.1 fails if set of platters
is owner 10
10. Id = JOSqa00331
Bad format detected for JMD_MEDIA_IN_ERROR
and MIGIN_NO_SUCH_PLATTER
11. Id = NSMex02469
License problem when '0' in IP Address
12. Id = NSMex02508
Request to have a tool to read metadata from
nearline storage
13. Id = JOSqa00332
jlog and qrlog log messages incomplete
14. Id = JOSqa00336
license manager (jmd) gets confused if
license.use file remained on disk
15. Id = NSMex02483
A5711310 - Consolidate: Can't open file by inode :
Error 0 (0)
PHSS_17476:
1. Id = NSMex02018
man page for ager : AGER_MAXSIZE is 1.000.000,
should be 128.000.000
2. Id = NSMex02015, NSMex02016
hsm_session display format problem
3. Id = NSMex02026
Bulk ager complains about wrong process id
4. Id = JOSqa00314
Add detailed Info to iocfg for performance config
5. Id = JOSqa00313
Add detailed Info to brapicfg for performance config
6. Id = JOSqa00307, NSMex02253
copyp does NOT work in OMS 3.0
7. Id = JOSqa00298
qrlog ERROR - no space available
8. Id = JOSqa00309
5.2 GB MO Jukebox not supported
9. Id = JOSqa00312
wrong mail format FREEPOOLVS_PROBLEM_MAIL
10. Id = NSMex02038
hsm_admin -I additional information needed in
installation guide
11. Id = JOSqa00308
copyp - documentation change
12. Id = NSMbb21706
agerlog message logging is consuming disk space
(SR #1653276659, SR #1653276667)
13. Id = NSMex01976
Lack of information when using vsadm -l
14. Id = NSMex02088, NSMex02177
STK direct connect tape library, jmd core dump
15. Id = NSMex01992, NSMex01191
jmd: No drive number in jlog if media is set
to error state
16. Id = NSMex01975
Active mode ager continuously submitted migout
requests not stopping at ALWM
17. Id = NSMex01969
volsets not created if TMPDIR environment variable
is set
18. Id = NSMex00837, NSMex00371, NSMex01141
Rebuild fails to rebuild
(SR #5003409540)
19. Id = JOSqa00315
remigration of a file to a full platter fails
20. Id = NSMex02031
Enhancement request to disable timeout on bulk ager
21. Id = NSMex02099
ager in bulk mode runs longer than expected.
22. Id = JOSqa00320
creation of a<fsid>/b<fsid> file by ager needs
redesign
23. Id = JOSqa00318
forever licenses will not be granted
24. Id = JOSqa00316
migout large files to sidf tape failed
25. Id = JOSqa00319
jmdrestore does not restore large number of bytes
26. Id = NSMex0219
while performing an inventory jmd dies through
segmentation violation
27. Id = NSMex02328
Abnormally stop sync_media leaves media in
inconsistent state
28. Id = JOSqa00322
Migout request remains in Qr queue although file has
been migrated out
29. Id = NSMex02349
Migration to 8x WORM media does not access next
medium with available space
Defect Description:
PHSS_28460:
1. Id = NSMex04921
During execution of "migout -m VolumeSpec" command,
some necessary flags are not set into migration
request on the "qr" side.
Resolution:
For specified volume, set needed flags to migration
request.
2. Id = NSMbb29322
OmniStorage "zdu" command did not exist before.
Resolution:
New OmniStorage command is now implemented.
3. Id = NSMbb37713
None of existing "listp" options did provide all
information about real ID and barcode with only one
option.
Resolution:
For OmniStorage "listp" command, new option is
Implemented: - "w".
4. Id = NSMex02040
The only way of choosing offered "installchanger"
options is using copy/paste functionality.
Resolution:
A new way of choosing offered "installchanger"
options is now implemented (number selection).
5. Id = NSMex02294
Appearance of this error message in "jlog" file is
normal, but it is not an error. It should be
implemented as a warning.
Resolution:
Error statement is changed into warning statement.
6. Id = NSMex03223
Unmounting of the platter is performed before its
been exported.
Resolution:
Implemented that exporting of the platter is
performed before its unmounted.
7. Id = NSMbb37708
Output of "jmdrestore" command shows only one line
- succeeded or not.
Resolution:
New command's output is implemented. It provides
additional status information for each media.
8. Id = NSMbb29373
This is caused by huge number of requests that cannot
be executed.
Resolution:
New option is added in GUI's "Dialog" menu. The name
of this option is "Reset_outstanding", and it enables
resetting of outstanding requests.
9. Id = JOSqa00321
"ager" parameters "AGER_ACTIVELIMIT" and
"AGER_BULKLIMIT" are not really redundant. Mistake is
in "ager" man page. It contains wrong directory path
for ager's active and bulk mode lists.
Resolution:
In paragraph "ASSOCIATED FILES AND DIRECTORIES" of
"ager" man page, path directory of ager's lists is
changed from /opt/omnistorage/data/ager to
/var/opt/omnistorage/data/ager.
10.Id = JOSqa00306
One of the features of OmniStorage is that all
file data transfers go via the "io_server", i.e. RPC
data channel. So, exporting of secondary
hpufs formatted media on the OmniStorage server and
mounting it via NFS on the OMS client for
migout/migin actions is not necessary at all.
Resolution:
We avoid this exporting (on the server side), and
mounting (on the client side). It is also implemented
part of code where client's side sends a
platter's mountpoint, used by "io-server", to the
server side.
11.Id = JOSqa00233
OmniStorage starts to count device's slots from 0,
but they are really counted from 1.
Resolution:
"SlotId" is decremented for 1. It is entered from the
command line.
12.Id = JOSqa00217
Implementation of new OmniStorage command is
necessary.
Resolution:
New OmniStorage command "create_mfs" is implemented.
13.Id = JOSqa00128
Information in fields "Jukeboxes supported:" and
"Drives supported:" are not up-to-date.
Resolution:
Implemented update of these "jmd -c" fields, and now
they contain all needed information.
14.Id = NSMex02664
During backup session, OmniStorage server does not
ever resolve communication with its remote clients.
It checks only local clients.
Resolution:
During backup session for Migrating File Systems,
OmniStorage server checks all its clients, local and
remote.
15.Id = JOSqa00202
The problem is caused by memory leaks appeared during
handling of "migin" requests. Leaks were detected
using "purify" tool.
Resolution:
Memory leaks are resolved by freeing used memory,
occupied by a pointer.
16.Id = NSMex02622
During the backup or restore of single file absolute
path needs to be used.
Resolution:
GUI help is updated with this information.
17.Id = NSMex02033
Interface with a "qr" daemon does not support buffers
larger than 48k. Size of "socket send buffer",
"socket receive buffer" and "application buffer" is
limited to 48 k.
Resolution:
New interface between "qr" and "qqr" is implemented.
It supports reports larger than 48k.
18.Id = JOSqa00275
Some memory allocated for "vsadm" command was not
ever properly freed.
Memory leak appears during the execution of "vsadm"
command in following cases:
- vsadm -l
- vsadm -L
- vsadm -l vs_name
- vsadm -L vs_name
Resolution:
Allocated memory is properly freed.
19.Id = NSMbb37707
This problem appears in the GUI and only in case when
mail slot is not configured.
Resolution:
A "pop-up" error window is added.
20.Id = NSMex04278
During the OmniBack backup process of an OmniStorage
Migrating File Systems, there was an error:
"Got unexpected close from vbda".
Resolution:
Problem is fixed within OmniBack (nvbda and nvrda)
binaries. Unnecessary error message is avoided on the
OmniStorage side.
21.Id = NSMbb29360
OmniStorage shell scripts depend on transition link:
/bin -> /usr/bin.
If transition link /bin -> /usr/bin is removed then
real path of "bin" directory can not be found and all
OmniStorage related shell scripts fail.
Resolution:
Absolute path is changed from /bin to /usr/bin.
22.Id = NSMbb37710
Currently implemented sorting algorithm does not sort
Grau Silo media properly.
If there is no information about "slotid", media is
sorted in following order:
platter_1/side_A, platter_2/side_A, ..., platter_1/
side_B, platter_2/side_B.
Resolution:
Sorting algorithm is changed into platter_1/side_A,
platter_1/side_B, platter_2/side_A,
platter_2/side_B,...
23.Id = JOSqa00341
There is a problem with requeueing when migration is
started from second to the third layer. The regular
pair of source platters could not be found in the
list of queued platters.
Resolution:
For proper migration from second to the third layer
OmniStorage needs pairs of platters (source and
destination). This connection between two platters in
the pair is made with the implementation of a new
OmniStorage flag.
24.Id = NSMex01986
Abnormal stopping of OmniStorage processes, like
using Ctrl-C keys, leaves the session undestroyed in
memory and not connected to a specified process.
Those sessions are "mortal zombie" sessions.
Resolution:
Improved signal handling for OmniStorage processes
ensures normal exit in all cases.
25.Id = JOSqa00337
"consolidate" fails for files placed on the third
migration layer. This is caused as a result of
finding 0 for inode value for these files.
Resolution:
This is resolved since inode value can be obtained
with system call.
26.Id = HSLco36039
During the execution of "rebuild" command signals
SIGUSR1, SIGUSR2, SIGTSTP can leave "mortal zombie"
sessions in the "hsm_sessions" output.
Resolution:
Added handling for these three signals.
27.Id = HSLco35959
During the execution of "unloadp" command, flags
(flags&JUNLOCK) were not set correctly.
Resolution:
These flags are changed and now "unloadp" works
correctly in all cases.
28.Id = NSMex05500
If file is migrated out (divided in a few chunks)
and then migrated in and appended, then if we change
"CHUNK_MAX_SIZE" parameter from a higher to a lower
value, it could not be possible to migrated out again
this added part of file in few chunks with lower
size.
Resolution:
After additionally implementation it is
possible to migrate file in chunks with lower size
than it was in the previous session.
29.Id = NSMex05712
Zombie processes are not handled correctly in some
situations.
Resolution:
Calling signal after fetching the child's termination
status.
30.Id = HSLco20183
The problem is in calling memory allocation functions
(malloc, realloc, calloc). Returned values were not
checked. This could result in memory core dumps or
segment violation problems.
Resolution:
New memory allocation functions (OMS_malloc,
OMS_calloc and OMS_realloc) are implemented and each
call of malloc, realloc or calloc function in
OmniStorage source code (except deamons: qr, jmd, ios
and ager) was replaced with this new safe function.
31.Id = JOSqa00146
With "hsm_session" command only mortal sessions can
be killed.
Resolution:
Now it is possible to kill Immortal Zombie (IZ)
sessions with "hsm_session".
32.Id = HSLco38068
For zero-length file "zls" output shows like file was
migrated out and then migrated in. This is not true
since this file cannot be migrated at all.
Resolution:
This is changed and "zls" now shows correct output
for zero-length files.
33.Id = NSMex05709
Whenever a move action in the library is executed,
OmniStorage trusts the database without checking all
involved library elements.
Resolution:
OmniStorage checks current state of used resources
(drive, mail, slot) before any operation within a box
(move platter from a slot to a drive, ..).
After this checking current and real status of
resources will be known and operation will be
performed only in case where all needed resources are
available. In all cases database will be updated
properly.
34.Id = NSMex05578
Unload time needs to be specified in OmniStorage
configuration file.
Resolution:
New configuration parameter is implemented.
"JMD_UNLOAD_TIMEOUT" parameter in the "jmcfg" file
specifies time (in seconds) after which "jmd" will
start unloading of unused drives. Default value is 0.
If this parameter is set to 0 then drive will not be
unloaded automatically.
35.Id = HSLco37497
If "migin" command is executed several times for the
same file(s) (files are already in the queue for
migration), "qqr" output shows these requests as
duplicates.
Resolution:
Criteria for creating "migin" list in "qqr" output is
changed.
36.Id = NSMex05736
Migrations getting slow when "migin" and "migout" run
at the same time for file that is larger than 40% of
Migrating File System size and the LOG_LEVEL is set
to d2. Also, if we start some migins and migouts
at the same time, migration problems appear.
Resolution:
Problem is in the logging procedure since one "dmapi"
integer parameter was read with string instead of
integer format. Additionally handling was implemented
and now migration problems are resolved.
37.Id = NSMex06066
When a mirror tape or platter is reformatted, the
"SyncDirty" flag will not be set to 1 in the data
base. If the reformatted mirror is used as a new
original again, a "sync_media" will fail as the
"SyncDirty" flag is still 0.
Resolution:
A new logic was implemented so that the "SyncDirty"
flag will be updated from 0 to 1 after reformatting
of a mirror media.
38.Id = NSMbb48254
By default, OMS will not divide file into chunks and
all information (data + sidf overhead information)
need to reside on one side of platter. If free space
on Worm is less than that value (file size + sidf
overhead information) file can not be migrated out.
Resolution:
Implementing additional calculation of space that
needs to be reserved for file and free space on
platter. Also, additional messages were added to
suggest to the customer potential actions that should
be performed. Administrator's Guide is also updated.
39.Id = JOSqa00117
This is an enhancement request.
Resolution:
Forwarding of "migin" requests from qr-parent to qr-
child is now implemented in bulk mode (by using
buffers instead of forwarding these requests one by
one).
40.Id = NSMbb49679
When "listp -S" command is used, some WORM media show
a "strange" total capacity and the free size has the
same numerical value as that capacity. GUI also shows
the same WORM as 100% free.
Resolution:
New check for Worm media is implemented. If the end
of media is reached free space in the "jmd" database
is set to 0.
There is one more restriction added:
If during the migration to the sidf media "jmd"
notices that we are reaching EOM, then setting of
"strange" capacity is avoided for WORM.
PHSS_25370:
1. Id = NSMex04098
'par' command works with ioctl system call. Error
comes when source has more blocks than destination,
and in that case ioctl gets wrong parameters
(wrong number of blocks).
Resolution:
Add checking if destination space (blocks) is less
than source space.
2. Id = NSMex04227
When migration is started, 'listp -B' shows default
number of rawblocks, but not the number of rawblocks
of a formatted media.
Resolution:
Fixed 'listp' so now 'listp -B' shows correct number
of rawblocks, after migration is started for tape
device.
3. Id = NSMex04140
'rm' is handled as asynchronous request and the
dm event queue is filled up with requests, which
uses up all system resources and the system
hangs/panics.
Resolution:
'zrm' is created. 'zrm' is an OMS wrapper around the
standard 'rm' command which checks the number of
events for the 'OMS_QRASYNC' session in the kernel
outqueue ('qrasyninf' returns the number),
and pauses it if the number of events is higher
than 1000.
4. Id = NSMbb38043
The reason for wasted space on MOs (small files are
migrated) is the organization of the HFS file
systems.
If the size of a file is less than the logical
block size of the FS on MOs, then HFS includes
fragmentation for better file system space
utilization.
Small files are then able to utilize these
fragments with the following restrictions:
- The fragments are only used at the end of the
file
- All fragments are contiguous
- All fragments come from the same block
When the files are smaller or equal than half the
size of the logical blocks, then the last two rules
allow to have more than one file in one logical
block. If the files are larger than half the size of
the logical blocks, then the total number of small
files, which can be migrated to the MO media, is
equal to the total number of logical blocks in that
FS.
Resolution:
When this situation happens (number of logical block
is 0), do not consider this MO as candidate any more;
mark it as full instead. The free space will be set
to 0 (zero) for these media.
5. Id = NSMbb41618
The only time when the 'qr' checks if there are
unprocessed truncation lists, is after restarting.
If the 'qr' has to handle requests with a higher
priority (like 'migin/migout') while processing
truncations, truncation requests are left
unprocessed in the qr lists.
Resolution:
Added part of code where, after some other requests
are completed, 'qr' checks if there are unprocessed
truncation requests and starts with their
processing. We do not have to wait on restart of the
'qr' anymore.
6. Id = HSLco27922
During the restore process, 'par' is used to restore
platters. If restore goes to the same platter that
has been used as source in backup process, 'par' will
attempt to assign a guest ID to that platter. This
happens because the 'restore_vbfs' script doesn't set
'-g' flag on the par CLI.
Resolution:
Set '-g' flag so that the 'par' command can perform
copying without assigning of a guest ID flag to
the destination platter.
7. Id = NSMex04573
This problem is related to HSLco28479.
Updating of the free space after migration was
not calculated correct. But the free space
was correct after export/import of the media.
Resolution:
We added a call for updating the free space
after migration, like it is performed for
the 'importp' command.
8. Id = NSMex04421
This problem is related to HSLco29297.
The free space for mirrored media was not updated
correctly.
Resolution:
A call was added for updating the free space on
the mirror, like it is already performed for the
source media.
9. Id = NSMex03489
The handling of 'write protected' MO source media
(hpufs) was not fully implemented and 'sync_media'
failed though.
Resolution:
Some logic was added to the 'fstask' file to enable
the mounting of write-protected media.
10.Id = HSLco28605
The problem is caused by the SIDF data handling.
The additionally required space for the file set
header/trailer information was not taken into
account when choosing the target media for
migration; but only the required space for the
user data. The data migration then failed as the
meta data could not be written to the chosen
media.
Resolution:
The 'jmd' will ask for extra free space if it
detects that one of the potential candidates is
SIDF formatted.
The SIDF API was modified to perform an extra check
before attempting to write the buffer.
It will check for 1 free block in addition to the
size of the buffer.
11.Id = JAGad49998
During the exporting/importing of media (MO, WORM
and Tape), when 'jlog' is set to WARNING, nothing
was logged.
Resolution:
We added a logging, after the 'exportp/importp'
commands are performed.
12.Id = NSMbb29315
After the '/var' directory was filled to some high
value, and after space was freed, logging was not
resumed.
Resolution:
After performing some changes in the source code,
logging is stopped if '/var' is filled up more
than 90% until space is freed. After space is
freed, logs are adding regulary.
13.Id = NSMbb29275
After manually loading/mounting volumes, migration
will not finish until manually unloading/unmounting
the volumes again. These actions required adding
a warning in a log file.
Resolution:
We added a warning in a 'jlog' log file and some
variables to prevent messages from showing in the
log more than once.
14.Id = NSMbb29271
'vsbind' does not include checking for IDs of volume
sets and migrating file systems.
Resolution:
New function was added for checking of IDs for
migrating file systems and volume sets.
15.Id = NSMbb41726
To 'unmount' and then 'unload' platters with active
requests in the 'qr' queue, we should kill the
'io_server' first and in that way force the 'jmd'
to 'unmount' used platter.
Resolution:
Performing suspension of the MFSs and then killing
'jmd.'
16.Id = NSMex04451
The problem is caused by bad conversion of
filesystem IDs to string.
Resolution:
OmniStorage uses the 'statfs()' system call to
determine file system specific data.
According file system type string representation has
been copied into a field of the 'port_fs' structure.
This is replaced by the 'statvfs()' system call.
This system call already returns a string
representation of the file system type, so any
additional conversion is not necessary any more.
17.Id = NSMbb29294
When starting 'sync_media' from 'crontab' and the
mirror media wasn't in the library or when one of
the attributes (owner, group or state) was not set
properly for the mirror media, the '/var' directory
(from mail or from log file) was filled up
continually. This was the reasone that 'sync_media'
core dumps.
Resolution:
This error is now handled, so if this case happens,
mail will be shown only once and be time stamped.
In this case, execution of 'sync_media' will be
aborted.
18.Id = HSLco30178
Changing information about kernel parameters
('maxdsiz' or 'maxdsiz_64bit').
Resolution:
New info is added in the 'consolidate' man page.
19.Id = HSLco23197
Prototype of 'agercfg' file is not included
in packaging procedure.
Resolution:
'agercfg' file is included in packaging procedure.
Man pages and AdminGuide is updated with information
about configuration files.
PHSS_22743:
1. Id = NSMex03222
Minor numbers were ending on 4, that is
correct only for DLT2000. But what actually is
required is to have a 'best density' device file
for DLT2000/4000/7000, which means the minor
number needs to end on a 0.
Resolution:
Invoke DEN_M_BEST in installport.H file (value 0).
2. Id = NSMex03959
Problem was that 'zls' shows that the whole last
chunk is on magnetic.
Actually, only last block is on magnetic.
Resolution:
'zls' now shows the right percentage of magnetic
when the last block of chunk is there, and new filed
in output message is added.
3. Id = NSMex03925
Problem was that during migration out on sidf media
calculation of free space was not done correctly.
Actually, shown free space is much less than it is.
Resolution:
Changed file: QmigoutData.C
Free space is calculated correct.
4. Id = NSMex04140
Problem was that while the attribute inode of /usr is
locked, it needs to access a catalog file on this
file system to handle an error situation and this is
how it's getting into a deadlock situation.
Rresolution:
Exclude locking of attribute inode of /usr.
5. Id = NSMex03844
Problem was that in stacker mode first tape is never
unmounted, so second tape couldn't be mounted.
Resolution:
First tape is unmounted.
6. Id = HSLco26541
When started migration with -m switch if volume
doesn't exist or volume is full migration won't
start
Resolution:
Fixed migout to check if volume is full or volume
doesn't exist so migration will go to best platter
for migration
7. Id = NSMex04098
Par command fail when source platter has more blocks
then destination platter
Resolution:
Par command works with ioctl system call. Error comes
when source has more blocks than destination in that
case ioctl gets wrong parameters (wrong number of
blocks).
That problem is resolved.
PHSS_21065:
1. Id = HSLco20318
Tried to deallocate non-heap memory
Resolution:
Wrong source line commented out
2. Id = HSLco19774
If jukebox is not connected and you perform
migout command the jmd will core dump, because
it use a NULL pointer which is not tested.
Resolution:
Test NULL pointer.
3. Id = NSMex03366
First error
When jmdrestore restore volume data it tries
to restore names (aliases) too, and this is
perform by removing old names and setting new one.
The problem occurs if you have a box with
barcode-name, because the names can't be removed.
In GRAU SILO or STK are no slots information
and OMS use names for manipulating volumes.
Second error
"Cannot verify identity of volume: 2b (2a)"
This message occurs if you had some volumes
formatted for mirroring and had not properly
configured yet (if owner was not 10).
Resolution:
If we avoid removing/restoring names for
bar-coded boxes then command must work.
Do not read media by Real ID.
4. Id = NSMex03260
There is no free space problem at the time of
sync_media, but the original media have wrong free
space calculated. How this could happen?
By the time of exportp importp or full inventory
the media's attributes are completely reread.
The free space of media too, but after first miguot
new free space of media became, as is only file
from last migout on media. Why?
OMS use one variable for storing free space and
another for space and another for storing used
space, and in our case the used space was not
recalculate by the time of importp.
This happened only on MO sidf formatted media.
Resolution:
Set variable which contain used media space on
proper value.
5. Id = HSLco18392
It is not correct to check if qr and ded are running
on server side of OMS.
Also, on server side mfs shouldn't be checked.
At the other hand, on client side it is not correct
to check if jmd is running.
This will be changed.
Resolution:
Change scripts to check if it is running on server
or client side and then show appropriate message.
6. Id = NSMex03037
Intention of this fix is wrong mapping a system
set ID into a box and slots Ids with GRAU
SILO box. This happened only with double-sided
media in GRAU SILO box when sync_media
command is performed.
Where was the bug:
------------------
The problem lay in function, which transform
system set ID into box and slot ID, but GRAU
SILO box doesn't have a slot IDs and a slot
ID is set to -2.
Unfortunately transformation function was not
prepared to this situation.
Algorithm for decode sys ID was wrong, because
it didn't consider that slot could be negative.
So, at decode time box ID became one less then
proper.
There was another error cause of wrong type
conversion from signed to unsigned integer.
The reason was negative slot number again.
Resolution:
Check if slot became negative then increase
box ID by one.
Customize unsigned int type to signed.
7. Id = NSMex03020
Jmd couldn't access to other side of last platter
in box, because the last media was not set to
database at full inventory.
Resolution:
Bug was in file top/src/lm/lib/lm_sl/lm_grau.c
function volIterate.
The last iteration doesn't return appropriate value
from volserinfoP variable.
Actually, the variable volserinfoP is set to right
value, but in the same sentence counter myvolcount
is incremented and after that it was checked again
if it was exceeded the nActualCount.
This last check is always true and procedure return
NULL_VOLINF_PTR instead of volserinfoP.
8. Id = NSMex02823
After upgrading to OMS 3.0 (from OMS 2.2) the migin
performance for WORM's dropped remarkable. The
reason was a function, which was introduced when
the migout has been redesigned. One part of the
function was really necessary for migout but was
even executed for migin requests.
Resolution:
SeqMediaService: PrepareMigoutContexts only necessary
for migout
9. Id = JAGab76149, NSMex02958
ONC RPC Program number for rpc.kill was not reserved
program number but it was from user-defined range.
The same program number was used by some other
applications.
Resolution:
Implement rpc.kill that uses reserved ONC RPC program
number.
10. Id = NSMex02745,NSMex03270
Problem is in doing migout from client with 2 LAN
cards. Communication Server/Client doesn't work.
All OMS executables do not support 2 LAN cards on
a host. Until now OMS called the function
gethostname() to determine the IP address for
communication between executables.
If the customer has 2 LAN cards on one machine there
is no possibility to take the other one.
Resolution:
A new config file /etc/omslancfg was introduced. It's
content looks like this:
OMS_HOSTNAME=myhostname
Next steps have to be done on server and client
machines:
server:
add the name of oms client in file
/etc/opt/omnistorage/jhosts
client:
add jmcfg entry of the server machine
JMD_MACHINE=myserverhostname
11. Id = JOSqa00342
add_vol -v option: from man page user could conclude
that -v option is used for mirroring by default.
There was fatal error message in jlog file:
FATAL (19561):
08/30/1999 10:33:31 Bad format detected for
JMD_NO_OPEN_HD.
Resolution:
man page for add_vol command was changed
log entries were corrected
12. Id = NSMex02672
The migmv command 'migmv -R ...' traverses the
directories and creates qr-requests for each file.
The qr hangs when files of size=0 occurs.
Resolution:
The migmv checks the file size and avoids to
create a qr requests when file size is zero.
13. Id = NSMex02653
Former OMS cleanup utility is cleanp from 3.0 on
because there is a HP-UX command cleanup.
Some error messages still use CLEANUP.
Resolution:
Change the error messages from cleanup to cleanp
14. Id = NSMex02636
wt-check hangs and didn't come to end when processing
files with zero length.
The qrlog shows:
WARNING (13787):
07/27/1999 17:32:03 QmigoutIoC.C[368] ASSERT(3)
FAILED
Resolution:
Since the wt-check simply uses a system call for
'zfind' it is easy to insert the '! -size 0' into
the source file of 'wt-check'.
15. Id = NSMex02627
There could not be found details on the new
configurations in the jmcfg man page.
E.g. What is HP_ODL, HP_ODL_DUAL_PICKER ...
The manual says: Run jmd -c, but this is not
updated neither.
Resolution:
Entries have been made within the explanation of the
parameter JMD_BOX in the man page of jmcfg.
The part dealing with Boxtypes now reads like:
Boxtype is the box type number or name.
For a list of boxes supported by a specific server,
run jmd -c.
To inform about all supported MO disk and Tape
library types please refer to the "HP OpenView
OmniStorage Version A.03.00 Software Release Notes
& Installation Guide", chapter 4, "Configuring
OmniStorage Devices".
16. Id = NSMex02624
There is a wrong call to the function 'jsetvolsize'
in `the source 'QmigoutSupport.jmd.C' where the
qrlog message points to.
One of the parameters of 'jsetvolsize' is a 64bit
value but should be only a 32int value.
This was changed.
Resolution:
There is a wrong call to the function 'jsetvolsize'
in the source 'QmigoutSupport.jmd.C' where the
qrlog message points to.
One of the parameters of 'jsetvolsize' is a 64bit
value but should be only a 32int value.
This was changed.
17. Id = HSLco20623
Installchanger doesn't show HW path for robotic in
case that machine is 800 and robotic driver is sctl.
Resolution:
Currently, installchanger determines name of robotic
driver, regarding machine model. If machine is 800,
it set robotic driver to spt, and if is 700,it set
robotic driver to sctl. This is wrong. It is
possible to have 800 machine and sctl driver (for
D, R or K). I have changed installchanger to grep
output of ioscan and if there is a line like:
ctl 0 8/16/5.7.0 sctl CLAIMED DEVICE Initiator
robotic driver is set to sctl. Otherwise, it is set
to spt.
18. Id = HSLco20331
License removal was completely wrong.
Resolution:
Change was made in function jmrelclicense().
Algorithm for removal of node license info was
wrong. Pointer of deleted node was used.
Current status: if node with license info is
found it will be deleted.
But after that traversing will be stopped.
19. Id = NSMex03270
When OMS server and/or client has two lan cards,
it is not just problem with licenses.
All OMS executables do not support 2 lan cards
on a host.
Resolution:
The new configuration file /etc/omslancfg was
introduced on machine that has two LAN cards.
In this file, OMS_HOSTNAME variable
should be set to name that we want to use
in OMS. Than on server, we need to add license for
IP address of the name that we want to use in OMS,
the same as value of OMS_HOSTNAME variable.
20. Id = JOSqa0034
Memory was used without checking. Memory wasn't
deallocated.
Resolution:
Checking memory before using. Deallocating memory
that is not used any more.
21. Id = NSMex03473
I believe that jmdrestore is supposed to restore
volume and volume set information in case the
media database got corrupted for one or another
reason. Now, the behavior is a little strange,
because volumes have to be available in
the media database as a prerequisite to be restored
by jmdrestore. This means that jmdrestore is only
able to restore attributes like state and ownership
to volumes which are already current in the media
database.
The functionality which seems to be missing is a
restore of volumes which are currently not in the
database. Let's suppose the following scenario.
Several volumes are in state onsite while a
jmdbackup is created. Then the database gets
corrupted or we are loosing it. After an inventory,
the onsite volumes are not listed anymore. That's
normal. But why can't we restore them in the
database with jmdrestore?
Resolution:
Add new option to force restoring missing media in
database. Improve searching media.
22. Id = NSMex03121
When ded check free space on mount point first make
a lock on that mount point, then check if mount point
is MFS, if it is then ded get attributes from MFS and
after release lock. Ded never check if lock is really
released.
Resolution:
Ded have to check just MFS mount points, not all
mount points.
23. Id = HSLco21464
Fibre Channel data transfer not supported
Resolution:
intallchanger changed to correctly handle Fibre
Channel hardware path
24. Id = HSLco21524
mediaset and mediaformat tools not available for
OmniStorage 3.0.
Resolution:
Include mediaset, mediaformat and their man pages to
OmniStorage 3.0.
25. Id = NSMex03537
An extra path rebuilds since the mount path is not
stripped off correctly.
Problem with double underscores was a problem with
length of mount point.
In case that size of mount point was greater than
size of defined arrays, rebuild failed.
Resolution:
Mount path is stripped off correctly.
Size of arrays that are used to store name of mount
point and additional information were increased.
26. Id = NSMbb37517
This behavior come from old versions because importp
or inventory hadn't been able to manage such a media.
It could happen that you had more than one record in
DB for one media, cause importp didn't find proper
record in DB, which was stored as ONSITE.
It just used new id. New version can manage this
problem quite well. Some forgotten-copied media in
box could still make problem, but in normal use is
all managed.
Resolution:
Add new global variable into
/etc/opt/omnistorage/jmcfg file to allow or not
allow delete guest media from DB while inventory.
The JMD_NO_DELETE_GUEST_MEDIA_ON_INVENTORY let it be
a variable name.
If is set to TRUE then inventory set guest media as
ONSITE instead of delete guest media from DB.
27. Id = HSLco21556
what(1) command output shows wrong information about
OmniStorage version
Resolution:
Source files were changed so that information about
OmniStorage version is correct.
28. Id = NSMex03564
message 'not fully implemented' was shown when we
start jmdrestore in case we have GRAU library
Resolution:
in case we have GRAU library and start jmdrestore,
only in case we set verbose mode,
message 'not fully implemented' should be shown
29. Id = NSMex03588
hsm_session -ka doesn't kill all mortal sessions.
Only mortal zombie sessions are killed with this
command.
Resolution:
Change man pages for hsm_session.
File hsm_session.8.mif has been changed.
PHSS_19038:
1. Id = NSMex02262
When starting up the ager in active as well as in
bulk mode dumps lots of "Logging started" /
"Logging stopped" messages into agerlog.
This is redundant and is caused by an incomplete
implementation to realize a MFS specific logging.
Resolution:
Remove redundant calls of the Logging() function
and introduce a separate config file -agercfg-
to be able to modify ager logging behavior
without modifying the qr logging facility.
2. Id = JOSqa00325
The man page of the resid command is
not understandable. The resid usage differs from
the resid man page and has to be conform.
Resolution:
The man page of resid has been changed by
removing the effects which led to misunderstanding.
At the beginning of section OPTIONS an explanation
concerning indications in SYNOPSIS has been added.
The USAGE of resid has been conformed to the
SYNOPSIS in the man page.
3. Id = JOSqa00324
The examples in the man page are still in the old
syntax of rebuild. Option -d is not implemented
any longer.
Resolution:
Man page of rebuild has been changed by removal
of option -d and the EXAMPLES have been corrected.
4. Id = NSMex02367
Performing a volumeset bulk aging or running
'migmv' correctly copies files from second to
third layer, but doesn't free space on second
layer. The created orphaned chunks on second
layer can only be removed with 'cleanp'.
Resolution:
Remove the orphaned chunks on second layer if a
multi level migration request finished
successfully and the extended attributes have
been attributes have been updated correctly.
5. Id = JOSqa00327
zls -l shows 0 blocks on secondary media for
chunks in bulk mode (migrated, not modified and
have a copy on magnetic).
These chunks don't have the DM_REGION_READ managed
region flag set, which causes extent_check_region()
function to return 0 as the number of blocks that
reside on secondary media.
Resolution:
Print the number of magnetic blocks as the number
of nearline blocks for chunks in bulk mode in the
zls -l output.
6. Id = NSMex02401
ERROR messages in consollog appear for each
deleted file on tape.
Resolution:
A source code change was done. A handle was freed
twice in this case.
The ERROR messages do not appear any more.
7. Id = JOSqa00328
When the outward migration had bumped at EOT-a
rest of a chunk resides on this tape. This leads
to an error.
Resolution:
Log a warning in this case and handle the
situation there are no more images to copy.
8. Id = NSMex02450, NSMex02335, NSMex02478, NSMex0243
While trying to free space on disk the ager
submits migout requests to the qr. If a request
references a chunk in bulk mode (migrated,
not dirty and has a copy on magnetic) and this
chunk resides on a full secondary media the qr
drops the migout request because it recognizes
that the corresponding secondary volume has no
free space for migration, but it doesn't
recognize that it only needs to erase the
magnetic copy of that chunk.
Resolution:
Let the bulk ager free the magnetic portion of
that chunk itself as implemented in the active
ager or the migout command.
This prevents network communication and improves
performance.
9. Id = NSMex02452
jmdrestore fails for mirror volumes which are
guests and have the same real Id as their
sources. The volume was opened by its real Id
until now.
Resolution:
jmdrestore opens mirror volumes by the id now.
10. Id = JOSqa00331
If media is set to ERROR state, no volume and
drive appears in the JMD_MEDIA_IN_ERROR and
MIGIN_NO_SUCH_PLATTER message
Resolution:
Place jmdmsg.Eng and qrmsgs.Eng into
/opt/omnistorage/lib/Eng
11. Id = NSMex02469
The jmd failed to decode a valid license string
for a system that has a '0' in its IP-address
due to a bug in the ovkey API.
Resolution:
Use latest ovkey API version which has the
corresponding fix in it.
12. Id = NSMex02508
Currently OmniStorage doesn't offer a tool that
can be used to determine which data images reside
on secondary storage by reading not extended
attribute information, but the metadata as
written to secondary media.
Resolution:
Support some kind of preview mode for the 'rebuild'
command, that only traverses the secondary media
and displays the found metadata information.
13. Id = JOSqa00332
While verifying customer qrlog file some of the
messages appeared incompletely, caused by
existing line feeds in the message text.
The used *.m to *.c/*.h compiler 'msgproc'
considers a line feed to be the end of a message
text. This leads to incomplete log message,
especially debug messages which makes it often
more difficult to determine the root cause of a
problem.
Resolution:
The qrmsgs.m and jmdmsg.m files were checked to
remove needless <CR>'s from the contents of the
$English parts responsible for the entries in
log messages.
14. Id = JOSqa00336
Stopping the jmd abnormally can leave the license
usage cash file '/var/opt/omnistorage/license.use'
on disk. This will cause the jmd to get confused
about available and used licenses which might
cause license requests to fail.
Resolution:
Remove the license usage cash file at jmd startup.
Correct its location to
/var/opt/omnistorage/data/jmd/license.use.
15. Id = NSMex02483
After consolidate the temporary files .omst**
created by pvlib were not deleted.
A customer had set the TMPDIR environment variable.
Resolution:
The c standard function tempnam was replaced by
tmpnam. The hpux manpage of tempnam is wrong.
The new consolidate works now.
PHSS_17476:
1. Id = NSMex02018
ager(1) and netcfg(4) man pages are inconsistent
regarding an explanation for the AGER_MAXSIZE
parameter.
Resolution:
update ager(1) man page
2. Id = NSMex02015, NSMex02016
o hsm_session output contains a message about a
non decodable session.
o the output is not aligned due to very long session
names
Resolution:
fix session name length
3. Id = NSMex02026
Running the ager in bulk mode causes the following
ERROR message in the agerlog file:
ager ERROR (26557): 01/28/1999 08:49:11
pvro_inlines.h(35) wrong process id for
session pid=67bd, created by 67bb
This ERROR message occurs by calling a pv* service
routine in an ager child process which doesn't have
the pv* services initialized.
Resolution:
Initialize pv* services in ager child process
4. Id = JOSqa00314
Make migration options
IOS_TAPE_MAX_FILES_PER_FILESET and
IOS_TAPE_MAX_DATA_PER_FILESET for better
performance configuration.
Resolution:
add comments to iocfg file
5. Id = JOSqa00313
The backup options IOS_BUFFER_SIZE and
IOS_WAIT_FOR_CLOSE need more description for better
performance configuration.
Resolution:
add comments to brapicfg file
6. Id = JOSqa00307, NSMex02253
The cause of the copyp failure is a "Large File"
problem. The system command "lseek" now using the
64 bit type of off_t for the offset value goes
wrong.
Resolution:
The solution is the right cast of the offset value.
The concerned function which uses the lseek system
call is retry_lseek().
7. Id = JOSqa00298
When migrating big files (>40% of disk cache) to
tape all but the first chunk would fail because
the jmd could not find space in the volume set
although there is enough space in the volume set.
Resolution:
The qr now calls MigOutReqVS() instead of
MigOutReq() which takes care of volumesets
bound to a certain MFS to correctly determine
available space for migration.
8. Id = JOSqa00309
Trying to migrate a chunk bigger than 2 GB to a MO
fails (the cache disk must be bigger than 5 GB for
that to occur).
Resolution:
Inserted new check for maximum possible chunk size
on nearline volume.
This restricts chunk size to 2GB-8k on MO hfs
formatted volumes.
9. Id = JOSqa00312
If a freepool is specified , but does not exist the
following mail appears:
Bad format detected for FREEPOOLVS_PROBLEM_MAIL.
Resolution:
Now the correct message [CHSM410514] appears in the
mail output.
10. Id = NSMex02038
When enabling migration with hsm_admin on an already
existing file system, the manual should document the
extra space used to do this, also that this can take
several hours on large file systems.
Resolution:
Additional entries into the concerning man page and
the Release Notes have been performed.
11. Id = JOSqa00308
After using of copyp, the listp command shows the
same size like before.
So the customer could assume the copyp command
didn't affect in any way. The right size for
mirror_volume will be shown after the first mount
of the mirror_volume.
The mirror_volume will be mounted during a full
inventory, or if the mirror_volume is replaced with
the source_volume.
Resolution:
An entry into the man page of copyp was made
accordingly.
12. Id = NSMbb21706
Every time the ager was started in active mode, but
aging was disabled, the qrlog was filled with
constantly repeated log messages like:
qr WARNING (26410): 01/12/1999 14:07:03
[CHSM410544]
The ager could not start in active mode for
FS_ID(0xc100) because aging is disabled in the
netcfg file. Please fix the netcfg file and restart
the ager.
Without (re)enabling aging this message occurred
every 30s which caused a space wasting log file.
Resolution:
Two flags, bAgerDisabledLogged and
bAgerEnabledLogged, were added to control the
logging to only write one log message for a
corresponding switch from disabled to enabled
or vice versa.
13. Id = NSMex01976
vsadm does not offer an option to print all
volumesets along with their members in one step.
Resolution:
A new option -L was added.
14. Id = NSMex02088, NSMex02177
Coredump of the jmd with STK9710 and BARCODE_NAMES
The STK9710 uses a different length for barcodes in
its SCSI-read-element-page.
Resolution:
STK9710 SCSI connection works now with barcodes.
15. Id = NSMex01992, NSMex01191
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.
16. Id = NSMex01975
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.
17. Id = NSMex01969
Defining TMPDIR env variable might cause the jmd
to fail when reading the volume set database at
startup. The jmd renames the original 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.
18. Id = NSMex00837, NSMex00371, NSMex01141
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.
19. Id = JOSqa00315
If you have a file migrated out on MO and you
change the file, you will get a partially
resident file. If now the volume is full and
you try to migrate out this file it will fail.
Resolution:
Now the request fails but is requeued to
another volume.
20. Id = NSMex02031
Ager -bulk should have a no timeout option of
zero the same as does the rebuild command.
Resolution:
Treat a given timeout of 0 as MAX_ALARM which
is at least 31 days.
21. Id = NSMex02099
While the ager was running in bulk mode it
didn't recognize the given timeout at the
correct time.
Resolution:
Implement timeout handling based on SIGALRM.
22. Id = JOSqa00320
The way the bulk mode ager filled a- and
b<fsid> lists didn't fulfill the requirement
of establishing lists containing migration
candidates to allow the active ager to fast
free space without walking the file tree to
determine migration candidates.
Resolution:
Redesign and implement a- and b<fsid> list
creation
23. Id = JOSqa00318
Permanent license will not be granted by the
jmd because it will not be checked if the
expiration date as encrypted in the license
key corresponds to the so called forever date.
Resolution:
Call OVLICisForever() to verify if a license
never expires by handling license requests.
24. Id = JOSqa00316
While migrating out files to sequential
(SIDF-) media (tape, WORM) the free space
would not be updated correctly.
When the end of tape is reached (either because
the free space was updated incorrectly or
because the tape had been formatted with a too
high capacity or both) the capacity of the tape
would be set to a wrong value and the tape might
even be set into error state.
Resolution:
The updating of used space was fixed and the
treatment of I/O-errors (especially EOT) was
changed completely.
Due to the asynchronous handling of write
requests the error condition 'end of tape' is
not always detected at the same spot, so the
finally detected size of a tape (after we hit
EOT) might differ from each other and also
from the capacity given by the manufacturer
(but this may also result from the really
different lengths of tapes).
25. Id = JOSqa00319
jmdrestore does not restore large number of
bytes for BlocksUsed and BlocksStale,
e.g. for DLT tapes 20GB
Resolution:
It now restores large numbers of bytes for
BlocksUsed and BlocksStale int64 data type
is used
26. Id = NSMex0219
During the inventory of a jukebox
"odetics_acl_452" the jmd dies.
Resolution:
The jmd now uses a more flexible method to
read the element status of library elements
(slots).
27. Id = NSMex02328
Abnormally stop a running 'sync_media',
e.g. by Ctrl-C, will leave platters in maintenance
and the original media keep flagged as being
sync'ed.
Resolution:
Improve sync_media's signal handling to ignore INT,
QUIT and TERM signals, but receipt the received
signal in an entry in synclog.
28. Id = JOSqa00322
Migrating a chunk which has all of its blocks on
nearline, but also some of its blocks modified on
magnetic causes the qr migout child process to
terminate abnormally with an assertion. This will
leave a kdm_user_thread process in memory.
The migout request will be requeued, but fails again
for the same reason, leaving a kdm_user_thread in
memory and so on until the system cannot fork
further processes.
The problem is caused by the wrong assumption that
and whole chunk will always be migrated. In fact the
reused space on nearline is smaller than the chunk
which leads to a wrong calculation of the real used
space on nearline before and after the migration.
Resolution:
Correct the number of bytes that will really be
reused on nearline.
29. Id = NSMex02349
When hitting end of media while migrating a file to
8x WORM media the media capacity as well as the free
space was wrongly calculated because the media
dependent sector size of 2048 bytes was not noticed.
This caused the qr parent to requeue the request
always to the same, already full media.
Resolution:
Use the media dependent sector size to calculate the
number of used media blocks when updating the jmd
database.
SR:
H555009278 H555008864 5003377333 H555007779 H555008986
B555005342 B555005703 B555005821 B555005705 B555005742
B555005823 B555005707 B555005743 H555003064 B555005744
B555008255 B555005627 B555005781 B555005745 H555009321
B555008257 B555005783 B555005666 B555005585 B555005784
B555008259 B555005668 B555005669 H555006932 B555005787
B555005789 H555009927 5003461475 H555008956 H555008959
1653302786 B555005714 B555005750 B555008261 B555005715
B555005670 B555005634 B555005716 B555005554 B555005636
B555005637 B555005718 B555005754 B555005835 B555005836
B555005639 B555005796 B555005798 H555008564 B555005601
B555005324 B555005325 B555005604 B555005641 B555005723
B555005328 B555005607 B555005644 B555005329 B555005726
B555005727 B555005566 B555005809 H555008611 B555005729
B555005769 H555008698 B554000620 B555005332 B554000347
B554000348 B555005730 H555010342 B555005650 B555005732
B555005651 B555005735 B555005771 B555005573 B555005575
B555005818 B555005694 B555005577 B555005658 B555005695
H555008583 8606180777 1653294041 H555006531 H555006036
B555008509 1653236059 H555006570 B555011105 H555006075
H555006318 1653224865 H555006049 1653275834 B555011027
H555005817 H555005774 H555003786 H555005676 H555004409
H555005024 H555003919 H555005055 H555005380 H555005379
H555005030 B554000604 H555003202 B555005800 B554000717
B555005801 8606106767 H555003104 B555005704 B555005722
B554000666 B554000693 B554000387 H555003108 B555005770
B554000398 B554000497 B555005725 H555003381 B555007915
B555005764 B555005755 H555003366 B555005748 B555005649
B555005829 H555003385 B555005758 B555005749 H555002918
1653299552 1653276667 1653276659 5003409540
Patch Files:
/opt/omnistorage/lbin/vsclose
/opt/omnistorage/lbin/vshdr
/opt/omnistorage/lbin/vsopen
/opt/omnistorage/lbin/vsread
/opt/omnistorage/lbin/vswrite
/opt/omnistorage/lbin/vsread.sh
/opt/omnistorage/sbin/sync_media
/opt/omnistorage/sbin/io_server
/opt/omnistorage/sbin/jmd
/opt/omnistorage/sbin/ager
/opt/omnistorage/sbin/qr
/opt/omnistorage/sbin/installchanger
/opt/omnistorage/sbin/jconvert
/opt/omnistorage/sbin/removechanger
/opt/omnistorage/sbin/rpc.niod
/opt/omnistorage/sbin/rpc.kill
/opt/omnistorage/sbin/rc.server
/opt/omnistorage/sbin/remote-launch
/opt/omnistorage/bin/xhsmbackup
/opt/omnistorage/bin/xhsmmgr
/opt/omnistorage/bin/xhsmmonitor
/opt/omnistorage/bin/xhsm
/opt/omnistorage/bin/copyp
/opt/omnistorage/bin/jmdbackup
/opt/omnistorage/bin/jmdrestore
/opt/omnistorage/bin/par
/opt/omnistorage/bin/vsadm
/opt/omnistorage/bin/omslic
/opt/omnistorage/bin/cleanp
/opt/omnistorage/bin/consolidate
/opt/omnistorage/bin/convert_media
/opt/omnistorage/bin/restore_file
/opt/omnistorage/bin/zfind
/opt/omnistorage/bin/migin
/opt/omnistorage/bin/migmv
/opt/omnistorage/bin/migout
/opt/omnistorage/bin/migsever
/opt/omnistorage/bin/qqr
/opt/omnistorage/bin/rebuild
/opt/omnistorage/bin/resid
/opt/omnistorage/bin/getfsid
/opt/omnistorage/bin/vsbind
/opt/omnistorage/bin/vsdbcheck
/opt/omnistorage/bin/wt-check
/opt/omnistorage/bin/zb
/opt/omnistorage/bin/zmdump
/opt/omnistorage/bin/zmrestore
/opt/omnistorage/bin/zdf
/opt/omnistorage/bin/zls
/opt/omnistorage/bin/aliasp
/opt/omnistorage/bin/chgowner
/opt/omnistorage/bin/chgstate
/opt/omnistorage/bin/exportp
/opt/omnistorage/bin/formatp
/opt/omnistorage/bin/fsckp
/opt/omnistorage/bin/importp
/opt/omnistorage/bin/inventory
/opt/omnistorage/bin/listp
/opt/omnistorage/bin/loadp
/opt/omnistorage/bin/mediaformat
/opt/omnistorage/bin/mediaset
/opt/omnistorage/bin/mountp
/opt/omnistorage/bin/qjmd
/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/zerrmsg
/opt/omnistorage/bin/zshutdown
/opt/omnistorage/bin/zstartup
/opt/omnistorage/bin/qrasyninf
/opt/omnistorage/bin/zrm
/opt/omnistorage/bin/restore_vbfs
/opt/omnistorage/bin/zdu
/opt/omnistorage/bin/create_mfs
/opt/omnistorage/bin/bkup_vbfs
/opt/omnistorage/bin/restore_vol
/opt/omnistorage/bin/add_vol
/opt/omnistorage/bin/par.sh
/opt/omnistorage/bin/mif.sh
/opt/omnistorage/bin/rebuild.sh
/opt/omnistorage/bin/restore_file.sh
/opt/omnistorage/bin/zmdump.sh
/opt/omnistorage/bin/zmrestore.sh
/opt/omnistorage/bin/hsm_admin
/opt/omnistorage/bin/hsm_session
/opt/omnistorage/newconfig/iocfg.proto
/opt/omnistorage/newconfig/jmcaps.proto
/opt/omnistorage/newconfig/agercfg.proto
/opt/omnistorage/newconfig/rpc.kill.txt
/opt/omnistorage/newconfig/massmediacfg.proto
/opt/omnistorage/newconfig/io_server.inetd
/opt/omnistorage/newconfig/rpc.niod.txt
/opt/omnistorage/newconfig/logcommand.proto
/opt/omnistorage/newconfig/jmcfg.proto.libman
/opt/omnistorage/lib/Eng/agermsgs.Eng
/opt/omnistorage/lib/Eng/qrmsgs.Eng
/opt/omnistorage/lib/Eng/jmdmsg.Eng
/opt/omnistorage/lib/libcheyhsm.sl
/opt/omnistorage/lib/liblmgrau.sl
/opt/omnistorage/lib/guimsg.ehdb
/opt/omnistorage/man/man1m/copyp.1m
/opt/omnistorage/man/man1m/vsadm.1m
/opt/omnistorage/man/man1m/hsm_admin.1m
/opt/omnistorage/man/man1m/add_vol.1m
/opt/omnistorage/man/man1m/mediaformat.1m
/opt/omnistorage/man/man1m/hsm_session.1m
/opt/omnistorage/man/man1m/consolidate.1m
/opt/omnistorage/man/man1m/create_mfs.1m
/opt/omnistorage/man/man1/ager.1
/opt/omnistorage/man/man1/rebuild.1
/opt/omnistorage/man/man1/resid.1
/opt/omnistorage/man/man1/mediaset.1
/opt/omnistorage/man/man1/listp.1
/opt/omnistorage/man/man1/qjmd.1
/opt/omnistorage/man/man1/qqr.1
/opt/omnistorage/man/man1/zdu.1
/opt/omnistorage/man/man4/jmcfg.4
/opt/omnistorage/man/man4/logcfg.4
/opt/omnistorage/man/man4/agercfg.4
/opt/omnistorage/man/man4/massmediacfg.4
/opt/omnistorage/man/man4/consolcfg.4
/opt/omnistorage/man/man4/synccfg.4
/opt/omnistorage/man/man4/netcfg.4
/opt/omnistorage/man/man4/dedcfg.4
/opt/omnistorage/man/man4/jmcaps.4
/opt/omnistorage/man/man4/iocfg.4
/opt/omnistorage/man/man4/brapicfg.4
/opt/omnistorage/man/man4/VScfg.4
/opt/omnistorage/man/man4/agerconfig.4
/opt/omnistorage/man/man4/jhosts.4
/opt/omnistorage/doc/AdminGuideA4.ps
/opt/omnistorage/doc/AdminGuideUS.ps
/opt/omnistorage/doc/ReleaseNotesA4.ps
/opt/omnistorage/doc/ReleaseNotesUS.ps
/etc/opt/omnistorage/brapicfg
/sbin/init.d/OMSclient
/sbin/ded
what(1) Output:
/opt/omnistorage/lbin/vsclose:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/lbin/vshdr:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/lbin/vsopen:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/lbin/vsread:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/lbin/vswrite:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/lbin/vsread.sh:
None
/opt/omnistorage/sbin/sync_media:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
/opt/omnistorage/sbin/io_server:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
/opt/omnistorage/sbin/jmd:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
%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
$
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
%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/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 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
/opt/omnistorage/sbin/qr:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
/opt/omnistorage/sbin/installchanger:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/sbin/jconvert:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/sbin/removechanger:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/sbin/rpc.niod:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/sbin/rpc.kill:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/sbin/rc.server:
None
/opt/omnistorage/sbin/remote-launch:
None
/opt/omnistorage/bin/xhsmbackup:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
OSF/Motif Version 1.2.5
/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 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
OSF/Motif Version 1.2.5
/opt/omnistorage/bin/xhsmmonitor:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
OSF/Motif Version 1.2.5
/opt/omnistorage/bin/xhsm:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/copyp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/jmdbackup:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/jmdrestore:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/par:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/vsadm:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/omslic:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/cleanp:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/consolidate:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
/opt/omnistorage/bin/convert_media:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/restore_file:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
/opt/omnistorage/bin/zfind:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
$Revision: 59.1 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/migin:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/migmv:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/migout:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/migsever:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/qqr:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/rebuild:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
/opt/omnistorage/bin/resid:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/getfsid:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/vsbind:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/vsdbcheck:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/wt-check:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/zb:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
/opt/omnistorage/bin/zmdump:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
/opt/omnistorage/bin/zmrestore:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
/opt/omnistorage/bin/zdf:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/zls:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/aliasp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/chgowner:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/chgstate:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/exportp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/formatp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/fsckp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/importp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/inventory:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/listp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/loadp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/mediaformat:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
/opt/omnistorage/bin/mediaset:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
/opt/omnistorage/bin/mountp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/qjmd:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/rkill:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/rmplat:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/setgrp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/unaliasp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/unloadp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/unmountp:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/zerrmsg:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/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/bin/qrasyninf:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/zrm:
None
/opt/omnistorage/bin/restore_vbfs:
None
/opt/omnistorage/bin/zdu:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/create_mfs:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/bkup_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/add_vol:
None
/opt/omnistorage/bin/par.sh:
None
/opt/omnistorage/bin/mif.sh:
None
/opt/omnistorage/bin/rebuild.sh:
None
/opt/omnistorage/bin/restore_file.sh:
None
/opt/omnistorage/bin/zmdump.sh:
$Release: zmdump.src OMS.02.10.04$
/opt/omnistorage/bin/zmrestore.sh:
None
/opt/omnistorage/bin/hsm_admin:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/bin/hsm_session:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
/opt/omnistorage/newconfig/iocfg.proto:
None
/opt/omnistorage/newconfig/jmcaps.proto:
$Release: jmcaps.proto OMS.02.11.00$
/opt/omnistorage/newconfig/agercfg.proto:
None
/opt/omnistorage/newconfig/rpc.kill.txt:
None
/opt/omnistorage/newconfig/massmediacfg.proto:
None
/opt/omnistorage/newconfig/io_server.inetd:
None
/opt/omnistorage/newconfig/rpc.niod.txt:
None
/opt/omnistorage/newconfig/logcommand.proto:
None
/opt/omnistorage/newconfig/jmcfg.proto.libman:
None
/opt/omnistorage/lib/Eng/agermsgs.Eng:
None
/opt/omnistorage/lib/Eng/qrmsgs.Eng:
None
/opt/omnistorage/lib/Eng/jmdmsg.Eng:
None
/opt/omnistorage/lib/libcheyhsm.sl:
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
$Id: mm/lib/misc/portamap.c/main/oms_2.2_dev_uid/1
97/08/12 15:38:50 $
/opt/omnistorage/lib/liblmgrau.sl:
None
/opt/omnistorage/lib/guimsg.ehdb:
None
/opt/omnistorage/man/man1m/copyp.1m:
None
/opt/omnistorage/man/man1m/vsadm.1m:
None
/opt/omnistorage/man/man1m/hsm_admin.1m:
None
/opt/omnistorage/man/man1m/add_vol.1m:
None
/opt/omnistorage/man/man1m/mediaformat.1m:
None
/opt/omnistorage/man/man1m/hsm_session.1m:
None
/opt/omnistorage/man/man1m/consolidate.1m:
None
/opt/omnistorage/man/man1m/create_mfs.1m:
None
/opt/omnistorage/man/man1/ager.1:
None
/opt/omnistorage/man/man1/rebuild.1:
None
/opt/omnistorage/man/man1/resid.1:
None
/opt/omnistorage/man/man1/mediaset.1:
None
/opt/omnistorage/man/man1/listp.1:
None
/opt/omnistorage/man/man1/qjmd.1:
None
/opt/omnistorage/man/man1/qqr.1:
None
/opt/omnistorage/man/man1/zdu.1:
None
/opt/omnistorage/man/man4/jmcfg.4:
None
/opt/omnistorage/man/man4/logcfg.4:
None
/opt/omnistorage/man/man4/agercfg.4:
None
/opt/omnistorage/man/man4/massmediacfg.4:
None
/opt/omnistorage/man/man4/consolcfg.4:
None
/opt/omnistorage/man/man4/synccfg.4:
None
/opt/omnistorage/man/man4/netcfg.4:
None
/opt/omnistorage/man/man4/dedcfg.4:
None
/opt/omnistorage/man/man4/jmcaps.4:
None
/opt/omnistorage/man/man4/iocfg.4:
None
/opt/omnistorage/man/man4/brapicfg.4:
None
/opt/omnistorage/man/man4/VScfg.4:
None
/opt/omnistorage/man/man4/agerconfig.4:
None
/opt/omnistorage/man/man4/jhosts.4:
None
/opt/omnistorage/doc/AdminGuideA4.ps:
None
/opt/omnistorage/doc/AdminGuideUS.ps:
None
/opt/omnistorage/doc/ReleaseNotesA4.ps:
None
/opt/omnistorage/doc/ReleaseNotesUS.ps:
None
/etc/opt/omnistorage/brapicfg:
None
/sbin/init.d/OMSclient:
$Id: install/hpdmig/OMSclient.sh/main/oms_2.2_dev_
uid/5 97/10/06 15:01:55 $
/sbin/ded:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP aC++ B3910B A.01.30 Classic Iostream Library
HP aC++ B3910B A.01.30 Language Support Library
HP OmniStorage $Release: A.03.00.06 PHSS_28460 $
HP OmniStorage $Date: Thu Jun 5 20:08:50 METDST 200
3$
libovsnmp
PATCH-PHCO_25640 for 10.20; for 10.30, 11.x compatib
ility libc.a_ID/main/r10dav/libc_dav/libc_
dav_cpe//1
/ux/core/libs/libc/archive_pa1/libc.a_ID
Nov 30 2001 06:30:28
cksum(1) Output:
3722444055 219186 /opt/omnistorage/lbin/vsclose
1783750371 219187 /opt/omnistorage/lbin/vshdr
569127309 219189 /opt/omnistorage/lbin/vsopen
3262281590 219186 /opt/omnistorage/lbin/vsread
97501846 219188 /opt/omnistorage/lbin/vswrite
1983822056 2224 /opt/omnistorage/lbin/vsread.sh
1824663633 758793 /opt/omnistorage/sbin/sync_media
2208137633 1115034 /opt/omnistorage/sbin/io_server
2777839959 1478805 /opt/omnistorage/sbin/jmd
3815018974 735816 /opt/omnistorage/sbin/ager
152859809 1398087 /opt/omnistorage/sbin/qr
2063440559 90821 /opt/omnistorage/sbin/installchanger
4269417329 73956 /opt/omnistorage/sbin/jconvert
393769138 124125 /opt/omnistorage/sbin/removechanger
2024501295 57829 /opt/omnistorage/sbin/rpc.niod
317457879 24686 /opt/omnistorage/sbin/rpc.kill
3692920396 136 /opt/omnistorage/sbin/rc.server
348237598 2128 /opt/omnistorage/sbin/remote-launch
1084505053 3029958 /opt/omnistorage/bin/xhsmbackup
2758425335 3845429 /opt/omnistorage/bin/xhsmmgr
2918597155 2823734 /opt/omnistorage/bin/xhsmmonitor
1702328015 561734 /opt/omnistorage/bin/xhsm
493245595 190335 /opt/omnistorage/bin/copyp
3467057404 260752 /opt/omnistorage/bin/jmdbackup
700695773 256645 /opt/omnistorage/bin/jmdrestore
2116792291 194464 /opt/omnistorage/bin/par
3698116378 181874 /opt/omnistorage/bin/vsadm
2153856668 70069 /opt/omnistorage/bin/omslic
2920177085 372124 /opt/omnistorage/bin/cleanp
2480489724 820561 /opt/omnistorage/bin/consolidate
1289160773 371849 /opt/omnistorage/bin/convert_media
2373585795 762617 /opt/omnistorage/bin/restore_file
1103918354 454978 /opt/omnistorage/bin/zfind
2294622642 252076 /opt/omnistorage/bin/migin
3120674909 392744 /opt/omnistorage/bin/migmv
2756399884 430004 /opt/omnistorage/bin/migout
228513028 243885 /opt/omnistorage/bin/migsever
2807509110 161526 /opt/omnistorage/bin/qqr
4002597393 899633 /opt/omnistorage/bin/rebuild
2543375020 189960 /opt/omnistorage/bin/resid
4207260958 177627 /opt/omnistorage/bin/getfsid
1864066596 396821 /opt/omnistorage/bin/vsbind
3665364996 388642 /opt/omnistorage/bin/vsdbcheck
3820139120 194181 /opt/omnistorage/bin/wt-check
3517103895 923559 /opt/omnistorage/bin/zb
3517103895 923559 /opt/omnistorage/bin/zmdump
3517103895 923559 /opt/omnistorage/bin/zmrestore
2137621846 268774 /opt/omnistorage/bin/zdf
3382230885 206548 /opt/omnistorage/bin/zls
2477388506 149004 /opt/omnistorage/bin/aliasp
3494091602 148998 /opt/omnistorage/bin/chgowner
1830023601 148999 /opt/omnistorage/bin/chgstate
474622020 149000 /opt/omnistorage/bin/exportp
2007517469 198505 /opt/omnistorage/bin/formatp
2293973059 149000 /opt/omnistorage/bin/fsckp
1014474778 149000 /opt/omnistorage/bin/importp
2750985429 161434 /opt/omnistorage/bin/inventory
1186869625 165441 /opt/omnistorage/bin/listp
2477235529 149002 /opt/omnistorage/bin/loadp
3977862588 396191 /opt/omnistorage/bin/mediaformat
697149823 396179 /opt/omnistorage/bin/mediaset
3655578619 149000 /opt/omnistorage/bin/mountp
2091110861 173825 /opt/omnistorage/bin/qjmd
3933398507 24693 /opt/omnistorage/bin/rkill
1640606946 148999 /opt/omnistorage/bin/rmplat
1230330068 148999 /opt/omnistorage/bin/setgrp
3748751698 148999 /opt/omnistorage/bin/unaliasp
2424589318 149013 /opt/omnistorage/bin/unloadp
2926184281 149000 /opt/omnistorage/bin/unmountp
4193476559 24702 /opt/omnistorage/bin/zerrmsg
3083265485 7535 /opt/omnistorage/bin/zshutdown
1975454536 8159 /opt/omnistorage/bin/zstartup
587875299 53643 /opt/omnistorage/bin/qrasyninf
2152958652 1949 /opt/omnistorage/bin/zrm
1942698548 33587 /opt/omnistorage/bin/restore_vbfs
222530965 189969 /opt/omnistorage/bin/zdu
2516622597 400985 /opt/omnistorage/bin/create_mfs
768384207 16493 /opt/omnistorage/bin/bkup_vbfs
2176330846 9582 /opt/omnistorage/bin/restore_vol
309206322 6426 /opt/omnistorage/bin/add_vol
1738367116 2731 /opt/omnistorage/bin/par.sh
1625899037 5244 /opt/omnistorage/bin/mif.sh
744207412 2054 /opt/omnistorage/bin/rebuild.sh
299318103 2639 /opt/omnistorage/bin/restore_file.sh
859115479 2885 /opt/omnistorage/bin/zmdump.sh
4080875339 3113 /opt/omnistorage/bin/zmrestore.sh
2659983754 111495 /opt/omnistorage/bin/hsm_admin
2153217786 99140 /opt/omnistorage/bin/hsm_session
3720023498 1611 /opt/omnistorage/newconfig/iocfg.proto
3641731285 6114 /opt/omnistorage/newconfig/jmcaps.proto
4022074553 159 /opt/omnistorage/newconfig/agercfg.proto
3222915936 241 /opt/omnistorage/newconfig/rpc.kill.txt
1072766274 87 /opt/omnistorage/newconfig/massmediacfg.proto
3408806248 130 /opt/omnistorage/newconfig/io_server.inetd
4029151925 160 /opt/omnistorage/newconfig/rpc.niod.txt
4283349164 718 /opt/omnistorage/newconfig/logcommand.proto
2681174985 5098 /opt/omnistorage/newconfig/
jmcfg.proto.libman
1372942154 8673 /opt/omnistorage/lib/Eng/agermsgs.Eng
2128401290 75750 /opt/omnistorage/lib/Eng/qrmsgs.Eng
1676311338 37910 /opt/omnistorage/lib/Eng/jmdmsg.Eng
154997931 1308115 /opt/omnistorage/lib/libcheyhsm.sl
4063894488 53426 /opt/omnistorage/lib/liblmgrau.sl
4267316345 579928 /opt/omnistorage/lib/guimsg.ehdb
1603428761 4039 /opt/omnistorage/man/man1m/copyp.1m
2306588393 6784 /opt/omnistorage/man/man1m/vsadm.1m
2013184783 3900 /opt/omnistorage/man/man1m/hsm_admin.1m
4133577231 5663 /opt/omnistorage/man/man1m/add_vol.1m
612297124 8021 /opt/omnistorage/man/man1m/mediaformat.1m
1951007000 3072 /opt/omnistorage/man/man1m/hsm_session.1m
3817423328 3492 /opt/omnistorage/man/man1m/consolidate.1m
920557184 1776 /opt/omnistorage/man/man1m/create_mfs.1m
1268301407 13126 /opt/omnistorage/man/man1/ager.1
1990998109 5659 /opt/omnistorage/man/man1/rebuild.1
78451485 9598 /opt/omnistorage/man/man1/resid.1
1035280907 6678 /opt/omnistorage/man/man1/mediaset.1
2877711286 10033 /opt/omnistorage/man/man1/listp.1
1999080253 3143 /opt/omnistorage/man/man1/qjmd.1
3752066247 4916 /opt/omnistorage/man/man1/qqr.1
3788733706 2686 /opt/omnistorage/man/man1/zdu.1
1198260509 11337 /opt/omnistorage/man/man4/jmcfg.4
2311896509 4308 /opt/omnistorage/man/man4/logcfg.4
2857300603 1149 /opt/omnistorage/man/man4/agercfg.4
1314356960 747 /opt/omnistorage/man/man4/massmediacfg.4
3234179563 696 /opt/omnistorage/man/man4/consolcfg.4
762911741 696 /opt/omnistorage/man/man4/synccfg.4
268087052 15742 /opt/omnistorage/man/man4/netcfg.4
4028711401 734 /opt/omnistorage/man/man4/dedcfg.4
1810448857 11228 /opt/omnistorage/man/man4/jmcaps.4
613684390 1498 /opt/omnistorage/man/man4/iocfg.4
1085833323 1234 /opt/omnistorage/man/man4/brapicfg.4
947712447 4678 /opt/omnistorage/man/man4/VScfg.4
2086203876 1122 /opt/omnistorage/man/man4/agerconfig.4
2851594121 2769 /opt/omnistorage/man/man4/jhosts.4
648292786 3122534 /opt/omnistorage/doc/AdminGuideA4.ps
2408126949 3078715 /opt/omnistorage/doc/AdminGuideUS.ps
896633125 549092 /opt/omnistorage/doc/ReleaseNotesA4.ps
2145327512 533564 /opt/omnistorage/doc/ReleaseNotesUS.ps
1493699325 1038 /etc/opt/omnistorage/brapicfg
3208855787 4526 /sbin/init.d/OMSclient
667148076 976685 /sbin/ded
Patch Conflicts: None
Patch Dependencies:
s700: 10.20: PHKL_20096
s800: 10.20: PHKL_20097
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_17476 PHSS_19038 PHSS_21065 PHSS_22743 PHSS_25370
Equivalent Patches: None
Patch Package Size: 14360 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_28460
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_28460.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_28460. 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_28460.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_28460.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_28460:
This patch includes the following Site Specific Patches:
SSPOMS_29
SSPOMS_30
SSPOMS_32
SSPOMS_33
SSPOMS_34
SSPOMS_36
SSPOMS_37
SSPOMS_38
SSPOMS_39
SSPOMS_40
SSPOMS_41
SSPOMS_42
SSPOMS_43
SSPOMS_44
SSPOMS_45
SSPOMS_46
SSPOMS_47
SSPOMS_48
SSPOMS_49
SSPOMS_50
SSPOMS_51
SSPOMS_52
SSPOMS_53
SSPOMS_54
SSPOMS_55
SSPOMS_56
SSPOMS_57
This patch updates /etc/opt/omnistorage/iocfg,
/etc/opt/omnistorage/jmcaps, /etc/opt/omnistorage/agercfg,
/etc/opt/omnistorage/massmediacfg,
/etc/opt/omnistorage/jmcfg, /etc/opt/omnistorage/brapicfg,
/etc/opt/omnistorage/logcommand configuration files.
This might fail due to merge conflicts. Please scan
the log file /var/adm/sw/swagent.log for corresponding
WARNING messages and follow the listed instructions.
Installation Instructions:
1> Become root user
2> Stop OmniStorage application with 'zshutdown(1M)'
OmniStorage command
3> Install this patch following the above outlined
Installation Instructions using 'swinstall(1M)'
4> Start OmniStorage application with 'zstartup(1M)'
OmniStorage command
Use 'zstartup -m all' to also mount of all MFS's
NOTE: To successfully kill the 'rpc.kill' processes
from the command line, you should first kill the
'inet daemon' with the 'inetd -k' command.
-----End of Document ID: PHSS_28460------------------------------------------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]