HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- VCB$B_BLOCKFACT on OpenVMS VAX 6.2 with 18GB disk
Operating System - OpenVMS
1828217
Members
1863
Online
109975
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-05-2006 05:58 AM
09-05-2006 05:58 AM
VCB$B_BLOCKFACT on OpenVMS VAX 6.2 with 18GB disk
Anyone know of an (un)official ECO/patch for this problem:
The issue is that VCB$B_BLOCKFACT should be set to 01, because on the issue it is set to 00. This causes the number of cylinders to be
truncated from 10F47 to 0F47 and VMS is unable to map the total blocks on the drive.
The issue is that VCB$B_BLOCKFACT should be set to 01, because on the issue it is set to 00. This causes the number of cylinders to be
truncated from 10F47 to 0F47 and VMS is unable to map the total blocks on the drive.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2006 05:58 PM
09-05-2006 05:58 PM
Re: VCB$B_BLOCKFACT on OpenVMS VAX 6.2 with 18GB disk
Russ,
we recently had a related discussion about big SCSI disks (> 9 GB) here in ITRC:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1050010
Looks like the change to set VCB$B_BLOCKFACT to a minimum of 1 has been done around OCT-2000 in the MOUNT96 facility. There are no MOUNT-related patches available for OpenVMS VAX V6.2 from after that date.
You would need to have a PVS (Prior Version Support) contract with HP to ask for a patch from OpenVMS engineering.
As this is a VAX, you could probably look up the instructions from the source listings and develop a patch for MOUNTSHR.EXE
Volker.
we recently had a related discussion about big SCSI disks (> 9 GB) here in ITRC:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1050010
Looks like the change to set VCB$B_BLOCKFACT to a minimum of 1 has been done around OCT-2000 in the MOUNT96 facility. There are no MOUNT-related patches available for OpenVMS VAX V6.2 from after that date.
You would need to have a PVS (Prior Version Support) contract with HP to ask for a patch from OpenVMS engineering.
As this is a VAX, you could probably look up the instructions from the source listings and develop a patch for MOUNTSHR.EXE
Volker.
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP