- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- VMS V8.3 Sysgen> DEVICE_NAMING parameter
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО11-07-2006 09:36 AM
тАО11-07-2006 09:36 AM
VMS V8.3 Sysgen> DEVICE_NAMING parameter
Saw what could be intersting behaviour the other day. On an 8.3 machine with the Device_Naming parameter set to the default zero, there were oodles of _TNA: device with 5 digit names that started annoying a whole lot of code that expected a maximum of 9999.
To me, it looks like a bug 'cos bit 1 is not set so the "new" rules should not come into affect but, going forward, would setting Device_Naming to 4 or 5 solve the problem?
Cheers Richard Maher
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2006 04:39 PM
тАО11-07-2006 04:39 PM
Re: VMS V8.3 Sysgen> DEVICE_NAMING parameter
DEVICE_NAMING
(Alpha and I64) DEVICE_NAMING is a bit mask indicating whether
port allocation classes are used in forming SCSI device names.
this parameter has nothing to do with TNA devices. TCPIP V5.6 introduced the higher limit (from the V5.6 release notes):
1.11 TELNET Server Device Limit
The TELNET server is no longer limited to 9999 sessions or
TN devices.
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2006 11:06 PM
тАО11-07-2006 11:06 PM
Re: VMS V8.3 Sysgen> DEVICE_NAMING parameter
As device drivers that support 5 digit (or up to 32767 devices) appear to be being trickled thru by HP as releases come along, you may wish to consider setting this parameter to 4 until you know if there is an issue.
Regards Richard Maher
$ mc sysgen
SYSGEN> HELP SYS_P DEVICE_NAM
Sys_Parameters
DEVICE_NAMING
(Alpha and I64) DEVICE_NAMING is a bit mask indicating whether
port allocation classes are used in forming SCSI device names.
Following is the bit definition:
Bit Definition
0 If 1, enable new naming.
1 Must be 0. This bit is reserved for use by HP.
2 If 1, cloned device unit numbers wrap after 9999.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-11-2006 09:07 AM
тАО11-11-2006 09:07 AM
Re: VMS V8.3 Sysgen> DEVICE_NAMING parameter
TCP/IP version 5.6 uses sysgen param
DEVICE_NAMING, bit 2, aka "10K bit", to determine when device numbers wrap. This is true for both TNA and BG devices.
So yes, setting it to 4 or 5 will restore
the original behavior. You could argue that the sense of the bit is wrong, but someone must have decided that more people would be glad than would be upset (about having more devices).
The is a _completly unsupported_ way to set the highest BG unit number:
$ type TCPIP$ETC:sysconfigtab.dat
..........
net:
ovms_unit_maximum=0x7ffff
..........
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-28-2007 01:27 AM
тАО01-28-2007 01:27 AM
Re: VMS V8.3 Sysgen> DEVICE_NAMING parameter
As a workaround: set DEVICE_NAMING = 4, which will limit TNA (and other device) unit numbers to 9999 and prevent this problem from happening.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2007 01:52 AM
тАО01-29-2007 01:52 AM
Re: VMS V8.3 Sysgen> DEVICE_NAMING parameter
"In the past, OpenVMS would never create more than 10,000 cloned device units, and unit numbers would wrap after 9999. This had become a limitation for some devices, such as mailboxes or TCP/IP sockets.
Starting with OpenVMS Version 7.3-2, OpenVMS will create up to 32,767 devices if the DEV$V_NNM bit is clear in UCB$L_DEVCHAR2 and if bit 2 is clear in the DEVICE_NAMING system parameter. This does not require any device driver change. However, programs and command procedures that are coded to assume a maximum device number of 9999 may need to be modified."
I'll toss some text into the next edition of the FAQ, as Mr Maher isn't the only one that has commented on this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2007 02:03 AM
тАО01-29-2007 02:03 AM
Re: VMS V8.3 Sysgen> DEVICE_NAMING parameter
The 'new naming' mentioned in the SYSGEN help only applies to SCSI devices and port allocation classes and this is only controlled by bit 0.
Bit 2 is the '10k' bit and is not related to the setting of bit 0.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-14-2008 01:32 AM
тАО11-14-2008 01:32 AM
Re: VMS V8.3 Sysgen> DEVICE_NAMING parameter
can anyone know vax phone problem in openvms8.3?
Vax phone utility doesn't work with TNA devices after 9999.
In 8.3,By default, bit 2 is cleared, and this allows the increase unit number to wrap at 32K.
If you want openvms phone utility you must wrap after 9999.
if you try to use the phone after 9999 the following error messages are coming..
*The persons terminal cannot be used as a telephone.
*%SYSTEM-W-NOSUCHDEV, no such device available
In 7.3-2 also having this problem if you have not wrap after 9999. By default it automatically wraps.
some more information abt this parameter please find the enclosed document.....
Regds,
Acullise
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-14-2008 01:44 AM
тАО11-14-2008 01:44 AM
Re: VMS V8.3 Sysgen> DEVICE_NAMING parameter
if you have a support contract with HP, please report this problem with the PHONE utility (probably as a low-priority call).
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2008 07:34 PM
тАО11-16-2008 07:34 PM
Re: VMS V8.3 Sysgen> DEVICE_NAMING parameter
I have already logged a call regarding this issue. They didnt give a solution for that and they told me to set the DEVICE_NAMING to 5.\
Regds,
Acullise.