GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- question on dd command
Operating System - HP-UX
1846559
Members
1356
Online
110256
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
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
Go to solution
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-29-2000 08:17 AM
09-29-2000 08:17 AM
I have a simple ksh script that dd's a file to tape. My company then actually ships the tape to a customer. (Yes, via US Post Office) This script has been around for 2years, hasn't changed and works fine. Now the customer has approached me insisting that the tape must have an "IBM label" on it otherwise they can't read the data. Does anyone know if it is possible to shove an IBM label on the tape??
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2000 08:29 AM
09-29-2000 08:29 AM
Solution
Yes you could do it, it consists of (in UNIX terms) several files at the start and end of tape:-
VOL1 label
HDR1 label
HDR2 label
data
EOF2 label
EOF1 label
EOV label
I can't remember the full details but it will be a pain trying to write them yourself.
The problem is that the various labels contain information pertinent to the data and you would probably have to convert it all to EBCDIC. I guess that there must be a utility out there to do it for you.
However, I would query their statement that they can't read it. What have they changed to make this so. If they have an IBM mainframe then it will be perfectly capable of reading an unlabelled tape.
VOL1 label
HDR1 label
HDR2 label
data
EOF2 label
EOF1 label
EOV label
I can't remember the full details but it will be a pain trying to write them yourself.
The problem is that the various labels contain information pertinent to the data and you would probably have to convert it all to EBCDIC. I guess that there must be a utility out there to do it for you.
However, I would query their statement that they can't read it. What have they changed to make this so. If they have an IBM mainframe then it will be perfectly capable of reading an unlabelled tape.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2000 06:00 PM
10-01-2000 06:00 PM
Re: question on dd command
IBM labeled tapes are almost like ANSI labeled tapes except that they are recorded in EBCDIC format. However, IBM mainframes can read ANSI labels (which are plain ASCII but the mainframe shop may need to write some JCL). The header records are all 80 characters wide and there are several fields in each header that must be filled in. They tell the mainframe what the record length and blocking factors are.
In the world of Unix, fixed records and blocking factors are totally foreign as there are no tools to read or write them. And storing files on tape in Unix format (ASCII variable length) may require a program on the mainframe to read the records and convert to the IBM format on disk. So you will have to make each ASCII record the same length as mainframe variable length records are nothing like Unix. If the data is pure binary, then the dd solution will work OK.
Your best bet is to ask the mainframe shop for an IBM Tape Labels Reference manual. You can usually get by with a VOL1, HDR1, HDR2 record prepended to the data file and append EOF2, EOF1 and EOV at the end of the file. This must be repeated for each additional file.
BTW: Any IBM mainframe shop worth their salt can handle unlabeled tapes. Labeled tapes makes it easier to hand the tape to an untrained operator but with appropriate JCL, any tape can be usually be read on any mainframe.
Bill Hassell, sysadmin
In the world of Unix, fixed records and blocking factors are totally foreign as there are no tools to read or write them. And storing files on tape in Unix format (ASCII variable length) may require a program on the mainframe to read the records and convert to the IBM format on disk. So you will have to make each ASCII record the same length as mainframe variable length records are nothing like Unix. If the data is pure binary, then the dd solution will work OK.
Your best bet is to ask the mainframe shop for an IBM Tape Labels Reference manual. You can usually get by with a VOL1, HDR1, HDR2 record prepended to the data file and append EOF2, EOF1 and EOV at the end of the file. This must be repeated for each additional file.
BTW: Any IBM mainframe shop worth their salt can handle unlabeled tapes. Labeled tapes makes it easier to hand the tape to an untrained operator but with appropriate JCL, any tape can be usually be read on any mainframe.
Bill Hassell, sysadmin
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 2026 Hewlett Packard Enterprise Development LP