Hi all, thanks for your help. But I mixed up my definitions between OSA2 and OSA3. I mixed definitions for a z990/OSA2 and z10/OSA3. What I found in the manuals and now understand hopefully is on an OSA2 all Names have to be the same, exept for OSA3. Those names must be unique. The problem is resolved.
Thanks and Regards Ralph -----Original Message----- From: IBM TCP/IP List [mailto:[EMAIL PROTECTED] On Behalf Of Maarten Slegtenhorst Sent: Tuesday, December 09, 2008 8:11 AM To: [EMAIL PROTECTED] Subject: Re: [IBMTCP-L] X'302C' Ralph, Based on Chris's information: Check if the portname in your VTAM TRL major node is the same as the devicename in your TCP/IP-profile. Also keep in mind that all LPAR's that use the same OSA-port have to use the same portname. If LPAR 3 and 12 both use port X then both need to have the same portname for port X. LPAR 3 : DEVICE OSAGE003 for port X LPAR 12 : DEVICE OSAGE012 for port X Doesn't work! -- Maarten -----Oorspronkelijk bericht----- Van: IBM TCP/IP List [mailto:[EMAIL PROTECTED] Namens MASON Chris Verzonden: maandag 8 december 2008 14:05 Aan: [EMAIL PROTECTED] Onderwerp: Re: [IBMTCP-L] X'302C' Marcel Thanks for alerting us all to this package of development "fixes/enhancements", specifically D144571. It would appear it is just "a good idea" to install the PTF for APAR OA25064 since it looks like "pure goodness". Assuming I have understood D144571, if D144571 does apply in this case, the "enhancement" is better to be informed what mistake in specifying the portname parameter is. The following is the text following the, so-called, "Problem conclusion" for D144571. <quote> D144571 ======= The failure is usually due to the portname parameter being incorrect. CONN$$MF, IUTLLCS1, IUTLLDMG, IUTLLDRQ, IUTLLSCT, IUTLLSIP, IUTSTAFD, OOTYPE, SAP, and SAP$$$IN have been changed to issue new Data Link Control status codes that specifically indicate that the portname parameter is incorrect, and why. This defect includes a publication change. To z/OS Communications Server IP and SNA Codes (SC31-8791-08), Chapter 3, Data Link Control (DLC) status codes, add the following: X'31nn' OSA-Express rejection of an attempt to activate a Port Explanation: Codes starting with X'31' are specific to OSA-Express QDIO Mode activation attempts. It indicates the OSA has rejected an activation attempt. The nn indicates the reason for the rejection. Specific nn codes are listed below. If a code is received that is not listed below, contact IBM Service. X'311B' Duplicate Portname Explanation: An attempt was made to activate an OSA-Express3 port in QDIO mode. The Portname for this activation attempt was already in use on the other port belonging to that CHPID. Two ports on the same CHPID cannot have the same Portname. X'3150' Wrong Portname Explanation: An attempt was made to activate an OSA-Express port in QDIO mode. The Portname for this activation attempt did not match the Portname already assigned to this port by a previous user. All z/OS users of that port must activate with the same Portname. </quote> So it would appear that, where the problem is one of the two above relating to the port name - and this seems very possible given that the "device name" is required to be the port name and "device names" have been changed - the enhancement introduced by the APAR is to clarify the problem. The APAR is *not*, as APARs usually are and as implied by your post, a fix to resolve the problem but is possibly to advance the analysis of the problem. It may be the major benefit in knowing about this APAR - in the context of Ralph's problem - is the awareness that code 302C relates nonintuitively to an error with the port name. Chris Mason ----------------------------------------------------------------- ATTENTION: The information in this electronic mail message is private and confidential, and only intended for the addressee. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it. Messages and attachments are scanned for all viruses known. If this message contains password-protected attachments, the files have NOT been scanned for viruses by the ING mail domain. Always scan attachments before opening them. ----------------------------------------------------------------- ---------------------------------------------------------------------- For IBMTCP-L subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO IBMTCP-L
