Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Any issues with having an EVA present a 4 digit (1001, 1102, 1205) LUN ID to OpenVMS?

 
tom_cornell
Occasional Visitor

Any issues with having an EVA present a 4 digit (1001, 1102, 1205) LUN ID to OpenVMS?

Need to set up a couple sets of a dozen disk volumes in an EVA or two that can be switched from one VMSCluster to another.  Would like to use 4 digit device unit numbers to make this crystal clear in the SHOW DEVICE readouts.

So, the device unit #'s need to be unique across the several VMSClusters (5) on which these transient devices may appear.

 

Easiest solution would be to set aside the 1000 series and the 1100 series.

 

Any issues with having an EVA present 4 digit device unit numbers to OpenVMS V8.3/Alpha and V8.3-1H1/IA64?

 

What are the issues?  (i.e. will the EVA just plain not do it?  Or does VMS not like it?)

 

EVAs in play are an 8000, an 8100, and a brand-new (last year) 8400.

 

Tom.

2 REPLIES 2
Hoff
Honored Contributor

Re: Any issues with having an EVA present a 4 digit (1001, 1102, 1205) LUN ID to OpenVMS?

Issues?  Beyond being slow and expensive, and where the typical fibre channel user interfaces from most any vendor making the DECnet-Plus NCL user interface appear to be the paragon of simplicity, clarity and ease of use?

 

As for your core question, in that cited unit number range, no.  You should be OK.  Unit numbers above 32K can get dicy.

 

tom_cornell
Occasional Visitor

Re: Any issues with having an EVA present a 4 digit (1001, 1102, 1205) LUN ID to OpenVMS?

Thanks, Hoff.   Got what I needed and the ball is rolling...