HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Omni Back mma, lbin file
Operating System - HP-UX
1833052
Members
2422
Online
110049
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2000 03:33 PM
09-19-2000 03:33 PM
Omni Back mma, lbin file
I am trying to write a script that scans several tape drives to verify the external numbers match the internal ones. Doing this from the gui works well but of course can't be scripted. The commands it uses is "mma". everytime I try to capture the command with ps -ef, the comman gets cut off at the end because its too long. Does anyone know how i can see the entire command? or better yet does anyoneknow of the syntax that i could use with the mma command to scan a drive?
I know of the omnimlist command but the info it presents is too verbose.
I know of the omnimlist command but the info it presents is too verbose.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2000 04:17 PM
09-19-2000 04:17 PM
Re: Omni Back mma, lbin file
Hi:
ps reports only a subset of the command line since only a limited amount is saved by the kernel; as much of the command line will be displayed as is available -- about 40-characters.
...JRF...
ps reports only a subset of the command line since only a limited amount is saved by the kernel; as much of the command line will be displayed as is available -- about 40-characters.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2000 05:49 AM
09-20-2000 05:49 AM
Re: Omni Back mma, lbin file
Hi, you can use the utility TapeAnalyser ie:
/opt/omni/sbin/utilns/TapeAnalyser -device /dev/rmt/#m -summary -header
You will get something like this:
=============== MEDIUM START BLOCK ===============
6e4e4253 41424344 0 0 0 0 0 MA_BLK_START MA_BLK_NULL 0 8192 236
medDateInitialized = Thu Nov 5 11:02:01 1998
medDateLastAccess = Thu Nov 5 11:02:01 1998
medDateLastWrite = Thu Nov 5 11:02:01 1998
medDateLastOverwrite = Thu Nov 5 11:02:01 1998
medNumWrites = 0
medNumOverwrites = 0
devInfoLength = 24
devInfoOffset = 288
medID = bf020402:36417799:34d5:0001
medLabel = NML0170
medLocation =
poolLabel = DLT7000
devCapacity = 0
medFmtVersion = 1
DEVICE INFO STRUCTURE:
devType = UNKNOWN
devBlkSize = 65536
woeStartPos = 0
woeEndPos = 0
segNum = 0
Number of blocks in the segment = 2
=================================
FILE MARK
=================================
=================================
FILE MARK
=================================
Of course if you have a library you have to insert the tape with ie. the uma(1M) utility.
Regards
Andrew
/opt/omni/sbin/utilns/TapeAnalyser -device /dev/rmt/#m -summary -header
You will get something like this:
=============== MEDIUM START BLOCK ===============
6e4e4253 41424344 0 0 0 0 0 MA_BLK_START MA_BLK_NULL 0 8192 236
medDateInitialized = Thu Nov 5 11:02:01 1998
medDateLastAccess = Thu Nov 5 11:02:01 1998
medDateLastWrite = Thu Nov 5 11:02:01 1998
medDateLastOverwrite = Thu Nov 5 11:02:01 1998
medNumWrites = 0
medNumOverwrites = 0
devInfoLength = 24
devInfoOffset = 288
medID = bf020402:36417799:34d5:0001
medLabel = NML0170
medLocation =
poolLabel = DLT7000
devCapacity = 0
medFmtVersion = 1
DEVICE INFO STRUCTURE:
devType = UNKNOWN
devBlkSize = 65536
woeStartPos = 0
woeEndPos = 0
segNum = 0
Number of blocks in the segment = 2
=================================
FILE MARK
=================================
=================================
FILE MARK
=================================
Of course if you have a library you have to insert the tape with ie. the uma(1M) utility.
Regards
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2000 06:11 AM
09-20-2000 06:11 AM
Re: Omni Back mma, lbin file
Hi,
did you tried omnimm -media_info MEDIA?
Here you can see the internal Label called Medium ID (this is unique and is in hex) and the external Label called Medium Label. The external Label can be changed with the gui or with omnimm -modify_medium.
This command will read the catalogdb. If you have your tapes inside a lib you shoul rescan this before (omnimm -repository_barcode_scan or omnimm -repository_update) Take care if you don't have barcodes, the repository_update will take some time because it will rescan your complete lib.
If you have further question contact me.
Regards
Frank
did you tried omnimm -media_info MEDIA?
Here you can see the internal Label called Medium ID (this is unique and is in hex) and the external Label called Medium Label. The external Label can be changed with the gui or with omnimm -modify_medium.
This command will read the catalogdb. If you have your tapes inside a lib you shoul rescan this before (omnimm -repository_barcode_scan or omnimm -repository_update) Take care if you don't have barcodes, the repository_update will take some time because it will rescan your complete lib.
If you have further question contact me.
Regards
Frank
Train stops at trainstations, bus stops at busstations... What happens at WORKSTATIONS?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP