Be aware that the VM/ESA OSA/SF apar and ptf database
is shared with OS/390 apar and ptf database.
This allows an OSA and/or OSA/SF apar/ptf
to be shared across different platforms.
Ref item 5 in the VMOSASF220 PSP bucket.
(Added 01/03/01)
For an OSA card to function, it needs both an
OSA Address Table (OAT Table)
and an IMAGE loaded onto the card.
Some OSA cards also require a CONFIGURATION file as well.
A few of the models of
the OSA cards ship with a DEFAULT
OAT Table and TCP/IP Passthru IMAGE already installed.
There are different types of OSA2 cards, some with 1 port and some
with 2 ports...and even some with 'logical ports'!
So there are too many options to not want an OSA2 card.
You CAN use your OSA2 card without the OSA/SF facility
installed, providing you use TCP/IP connections only and the
default device addresses.
All of the OSA2 cards (except the OSA2 ATM)
are shipped with TCP/IP Passthru mode
as the default mode. If you are going to run with default
unit addresses/ports in TCP/IP Passthru mode
then you do not need to do any customization
to the OSA2 by OSA/SF.
Default Unit Addresses for Port 0 are 00,01
Default Unit Addresses for Port 1 are 02,03
From a VM TCP/IP point of view, each OSA2 card
port is viewed as a
LAN Channel Station (LCS) device.
TCP/IP requires 2 device numbers/addresses per port...1 for
Read/Receive, and 1 for Write/Send.
OSA/SF installation is needed if you are ever going to try and
communicate with the OSA2 card.
OSA/SF runs with a Service Virtual Machine and has
associated client userids for requesting OSA/SF functions and
to execute the IOACMD commands:
OSASF
OSA/SF production server machine
OSADMIN1
Administration userid 1
OSADMIN2
Administration userid 2
OSADMIN3
Administration userid 3
OSAMAINT
OSA/SF Maintenance machine
2VMVMV20
OSA/SF Installation userid
Entering IOACMD from OSADMINx userid will guide
you through the command options and syntax
(you can also refer to the OSA/SF Users Guide for commands and/or
syntax).
Use the
BACK button to return to
OSA/SF Home Page.
