I think, there is some misunderstanding here.
First, basics:
DAS - Direct Attached Storage - a disk connected directly, like your HDD
in your PC. This model can be used in mainframe world - DASD array
connected over FICON links to the host. No switches/directors between.
SAN - In this case there is some switch/director between host and DASD
array.
Now, the switch - let's think about Ethernet switch. You plugged the
following devices: PC #1, PC #2, printer, laptop. Usually any device can
talk to any another device. Of course this is Ethernet level, maybe PC
#2 won't accept any "Hello" from laptop.
If fact SAN switch works very similar - any port can talk to any other
port. No, not a port - device attached to the port. What device? follow
the cable and you fill find something of the other end - it can be DASD
array port or z15 CHPID or some tape controller, etc.
Now we have zoning. By default "any can talk to any", so there is no
zoning. And let's be honest: should you block communication between tape
controller and DASD? Why? Or maybe CPC A should not see CPC B?
However you may create zones. However my experience is zoning may
provide you troubles only.
Of course things may be more complex, but this is topic for SAN specialist.
HTH
--
Radoslaw Skorupka
(looking for new job)
Lodz, Poland
W dniu 10.05.2021 o 17:09, Jake Anderson pisze:
Hi
So from the mainframe perspective zoning is done even if the connectivity
passes through SAN ? Sorry if my understanding is incorrect ?
Jake
On Mon, 10 May, 2021, 2:32 pm Radoslaw Skorupka, <[email protected]>
wrote:
W dniu 10.05.2021 o 06:36, Jake Anderson pisze:
Hello All,
Good evening
I am trying to understand on how the ZONING part works when the
connectivity to storage box or the tape device goes through a SAN switch.
How does the ZONING is done and is there any documentation with an
example
to understand better. I am trying to google to see if I can find the one
am
looking but I am not successful yet.
Is there any pointer or example if someone can help me with ? It will be
of
a big help to proceed further.
Zoning is needed for distributed systems world and "discovery" of
storage devices connected to the SAN. It is just to isolate/hide devices
not intended to use with given server.
In CKD world there is IODF/IOCDS configuration file which says what is
accessible to given LPAR or OS Config.
Of course your SAN can be used for various purposes like ISL, DASD array
remote copy (usually FC, not FICON) and maybe some FCP devices and servers.
--
Radoslaw Skorupka
(looking for new job)
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
