Neal The list where topics involving the Communications Server product, typically the IP component but not necessarily since the SNA component is also prominent, very often involving Enterprise Extender, is the following:
For IBMTCP-L subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO IBMTCP-L > Can somebody shed some light on this? Yes! > Is what I am trying to do legal? Yes. It's the way you are trying to do it that is "illegal"! > The explanation of '3150' does not make sense to me in a single system > context. When you mention the explanation of a message or code you have looked up, it saves a lot of time and traffic if you include the explanation in your post and what aspect of the explanation you found troublesome. The explanation of message EZZ4310I is as follows: <quote> 4.39 EZZ4310I EZZ4310I ERROR: CODE=error_code REPORTED ON DEVICE device_name. DIAGNOSTIC CODE: internal_diagnostic_code Explanation: The Link Layer detected an error during operation of the device. The error was reported asynchronous to execution of any Link Control function. error_code is the status code for the link layer. device_name is the name of the device. internal_diagnostic_code is the internal diagnostic code for use by IBM. System Action: TCP/IP marks the device inactive. Operator Response: VTAM message IST1578I might be issued in conjunction with this message. See the Data Link Control (DLC) status codes in z/OS Communications Server: IP and SNA Codes for a description of the status code for the link layer. If applicable, correct the hardware problem and restart the device. System Programmer Response: Perform the action described in z/OS Communications Server: IP and SNA Codes for the indicated status code. </quote> The explanation of code 3150 is as follows: <quote> | X'3150' | Incorrect port name | Explanation: An attempt was made to activate an | OSA-Express port in QDIO mode. The port name for this | activation attempt did not match the port name already | assigned to this port by a previous user. All z/OS users | of that port must activate with the same port name. </quote> > The explanation of '3150' does not make sense to me in a single system > context. I can't see why. You may have multiple instances of the IP component of Communications Server (CS) accessing the same OSA feature port. - Anyhow enough messing about with the definitions you were essaying. > I should be able to ... add a DEVICE and LINK statement to TCPIP. The way you add additional IP addresses to be supported by an OSA feature port is to use virtual IP addresses. So you were right up to the point you thought about using DEVICE and LINK statements which can be used to create a *static* VIPA if it's a static IP address you want. > I should be able to define another TRL for a different set of addresses on > the OSA port range, ... No, the existing TRLE - not TRL - is sufficient. That sort-of explains the need to use the same port name but not in the context of a single instance of CS IP. You simply ensure that the IP address defined for the VIPA lies in the same address range as applies to the (V)LAN to which the IP address assigned by the defining statements belongs. Incidentally, these days you should be thinking about migrating to an IPv4 QDIO INTERFACE statement to replace the DEVICE etc. statements. There are a number of threads in the IBMTCP-L list which deal with this topic. I've been battling with a slow system and experiencing "more haste, less speed"! Here are a couple of web pages I found which allude to the function and should get you started: The wrong network device (OSA) is listed as the VipaOwner http://www-01.ibm.com/support/docview.wss?uid=swg21430261 Network device (OSA) being reported in the wrong LAN group http://www-01.ibm.com/support/docview.wss?uid=swg21430256 There is another similar page supposedly addressing what the "LAN Group Summary" NETSTAT DEVLINKS inserts are all about but it's a "curate's egg" in being as much confusing as elucidating. If you need more help, I recommend IBMTCP-L. Chris Mason On Mon, 26 Sep 2011 14:21:24 -0500, Neal Eckhardt <neckha...@cnyric.org> wrote: >Hi, > >We need to add another IP address to z/OS 1.11. I hit upon the idea that since >each OSA port is defined with 16 addresses, I should be able to define another >TRL for a different set of addresses on the OSA port range, and add a DEVICE >and LINK statement to TCPIP. Is looks like this: > >VTAM: > >OSAB400 VBUILD TYPE=TRL >OSAB400P TRLE LNCTL=MPC, > READ=B400, > WRITE=B401, > DATAPATH=(B402), > PORTNAME=(OSAB400), > MPCLEVEL=QDIO >* >OSAB408P TRLE LNCTL=MPC, > READ=B408, > WRITE=B409, > DATAPATH=(B40A), > PORTNAME=(OSAB408), > MPCLEVEL=QDIO > >TCPIP: > >DEVICE OSAB400 MPCIPA >LINK OSALB400 IPAQENET OSAB400 >DEVICE OSAB408 MPCIPA >LINK OSALB408 IPAQENET OSAB408 > >I get the following when starting the LINK: > >EZZ4310I ERROR: CODE=80103150 REPORTED ON DEVICE OSAB408. DIAGNOSTIC >CODE: 03 >EZZ4315I DEACTIVATION COMPLETE FOR DEVICE OSAB408 >EZZ4313I INITIALIZATION COMPLETE FOR DEVICE OSAB400 > >The explaination of '3150' does not make sense to me in a single system >context. Can somebody shed some light on this? Is what I am trying to do legal? > >Thanks, >Neal ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
