Thomas, I thought we were making progress - until I got to the last paragraph. This looks as if it might be a PC user who is trying to access an SNA application on the AS/400 (and need to access the AS/400 through the mainframe?) - or - who is trying to access a mainframe application using the AS/400 as an intermediary.
Now I'm really lost. I'm glad to hear the 3745 is still there and doing sterling work - although you're going to have to deal with the issue of replacing it before too long - maybe not you personally. If one of the steps in this task is to arrange for another AS/400 to be connected in SNA terms to the mainframe through the 3745 token-ring facilities, you are going to need another switched PU statement definition in one of the active switched major nodes[1] You probably want to define it in much the same way as you define your other AS/400s. You are obliged to use CPNAME if you want to be up-to-date - for about 10 years or more now. There is an alternative characterised by the IDBLK and IDNUM operands but that is, in essence, a step back in time of 30 years[2]. [1] I guess it's some version of that peculiar AS/400 terminology that causes you to describe a switched PU statement in VTAM as "a SWNET application". But then I expect some of the VTAM terminology is equally odd to the AS/400 world. [2] However, support of "internal" DLUR - which is quite modern - requires IDBLK/IDNUM - just to confuse everybody. <g> I assume the way you use these switched PU statement definitions is by initiating the connection from the AS/400. If you were initiating the connection from VTAM/NCP (the latter running in the 3745), you would have a PATH statement and that would have some identification of the AS/400 link station which included the MAC and SAP addresses. Using the techniques I mentioned in the last post, the IP address can sort-of replace the MAC and SAP addresses. (Actually with Enterprise Extender, there's also a SAP address.) I'm sorry but we seem to have moved further away from knowing how that IP address fits into the picture. Well, let me have another stab at it. It's possible that the mainframe and the 3745 do not need to be in the picture. It may be that the PC person can access the AS/400 directly using the IP network but doesn't know how. Perhaps he/she is only dimly aware of having been assigned an IP address. You need to find out what this PC person really wants to do and take it from there. Chris Mason ----- Original Message ----- From: "Thomas Lawrence" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Thursday, 20 April, 2006 7:41 PM Subject: Re: Need Help defining an AS400 with an IP address to the mainframe > Perhaps I need to explain further. To put your fears at rest, our 3745 is > alive and well. We have several other AS400's defined and still functioning > through the 3745. They are all defined as SWNET type applications. Even the > AS400 which is being replaced is still defined there, however it is/has > been/will be replaced. I think we defined these SWNET appls about 10 years > ago. I may have defined them myself, maybe not. Anyway, it's been awhile. > > Be that as it may, I was given the task to allow access to the new AS400 and > was only given an ip address in the form of n.n.n.n as an identifier. What I > think I need to do is define this new AS400 using the IP address in some > fashion instead of CPNAME. Not really sure about this but I was hoping to > get some pointers. As far as Anynet and MTPN go, no we do not use that, AFAICT. > > Are there any questions that I need to ask the originator of this request? > Bear in mind, he or she is probably PC computer knowledgeable but probably > not mainframe knowledgeable. > > Thanks for your reply. > > TL ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
