9 Legend

 • 

20.4K Posts

November 21st, 2007 10:00

can you run this and post output:

symcfg list -ssid -sid 1234

6 Posts

November 21st, 2007 11:00

symcfg list -ssid -sid 0110

Symmetrix ID: 00038772xxxx
Sub System Information:

Sub System ID : 0x0001
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 256

Sub System ID : 0x0140
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 180

Sub System ID : 0x0141
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 228

Sub System ID : 0x0142
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 90

Sub System ID : 0x0150
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 219

Sub System ID : 0x0151
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 216

Sub System ID : 0x0152
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 90

Sub System ID : 0x0002
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 256

Sub System ID : 0xFBA0
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 256

Sub System ID : 0xFBA1
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 256

Sub System ID : 0xFBA2
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 256

Sub System ID : 0xFBA3
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 192

Sub System ID : 0x0003
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 256

Sub System ID : 0xFBA4
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 240

Sub System ID : 0x0004
Maximum Number of Devices Allowed : 256
Number of Devices Currently Present: 238



Thanks so much for the quick reply!

4 Operator

 • 

2.1K Posts

November 21st, 2007 11:00

Just be sure to find out which values are being used by your mainframe folks so when you add your next one you don't get into conflict with them.

While I'm glad I can share our DMX with the mainframe side of my team, I hate having to track the SSIDs :-( I guess it is the price we pay for sharing the cost of the arrays.

6 Posts

November 21st, 2007 11:00

That is exactly what I need to know. Thanks!

9 Legend

 • 

20.4K Posts

November 21st, 2007 11:00

here is excerpt from "Symmetrix Array control cli" document


Subsystem IDs for mainframe systems
 
Subsystem identifiers (SSID) are used by z/OS (MVS) mainframe systems to locate
physical disk controllers. In a Symmetrix array that is configured to support only
open systems hosts, the SSID value is not required. On Symmetrix arrays that service
both mainframe (CKD devices) and open system hosts (FBA devices), the SSID
parameter is required when creating new devices. The SSID parameter is also
required when removing a mirror from a device, which results in the mirror
becoming a new independent device.
Depending on the type of CKD emulation that is configured, the maximum number
of SSID counts may change. It is recommended that you contact EMC Customer
Support and ask which SSID was last used and what would be the next
recommended ID to use along with how many devices can be placed behind it before
you are required to increment the value to the next major range.
To obtain a list of SSIDs that are currently in use, use the following form:
 
symcfg list -ssid -sid SymmID



so in your box looks like you could create 16 more devices using "mvs_ssid=FBA4" option.

113 Posts

November 27th, 2007 06:00

Allen,

Good suggestion for JZR and anyone that has a mixed environment. CKD and FBA. You want to avoid any SSID conflicts.

Michael
No Events found!

Top