Re: CL/Supersession and APPN
PAT, We included a default COS definition in our startup options (APPNCOS=#CONNECT) and now everything is working great! The information you provided was very helpful. Thanks a million. Regards, John Au -- 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
Re: CL/Supersession and APPN
Chris, Your assessment is correct. We have private mode tables built without the correct COS parameters. We will go through the process of cleaning up our old definitions and add the proper COS definition so we don't rely on the default APPNCOS start option per your suggestion. Thanks for the advice. Regards, John Au -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Chris Mason Sent: Tuesday, June 09, 2009 12:33 PM To: IBM-MAIN@bama.ua.edu Subject: Re: CL/Supersession and APPN John I'm glad you've got over the problem. It might be best if each specific problem is presented, sense codes and all. is what I said last time. I am very well aware of the problem which is solved by specifying a value for the APPNCOS start option. Why? Because I had to solve the identical problem myself a few months ago - actually - and you may find some encouragement in this - the *only* problem that I had to solve in the migration. Incidentally, the product just happened to be NetView FTP trying to set up a session with another NetView FTP with the problem showing itself when there was an attempt to set up a file transfer. The reason you - for now - solved your problem by specifying the APPNCOS start option is that you - or some predecessor - had a rush of blood perhaps long ago and actually set up a private mode table entry with a subarea COS name - having first, of course, set up a subarea COS table and stored it in VTAMLIB. If one's assessment of a customer site is that they are unlikely to have been sufficiently adventurous to establish COS entries - as it was in my case having seen some private mode table entries which lacked COS operands - it doesn't seem necessary to worry about the APPNCOS start option. Another excuse not to have changed the APPNCOS start option value from NONE, the default, to something like #CONNECT, is to leave a trap for just the problem about which we would have read had you actually described your problem in detail. Having detected such a problem the change to the private mode table entry could then be made in order to ensure that an APPNCOS operand was added which had the same significance as the existing subarea COS operand. I could guess that the subarea COS operand that caused your problem mapped to a virtual route number which you - or your predecessor - intended always to be used for interactive traffic - I'm relying here on the fact that the application was Supersession - and also to a transmission priority of 2, the highest of the subarea transmission priorities. All that being so, I would advise that you locate the offending private mode table entry in the source of the private mode table - wherever it is! - add an appropriate APPNCOS operand such as #INTER, assemble and linkage edit the table overriding the existing mode table in your VTAMLIB. You can then reset the APPNCOS start option to NONE ready for the next similar problem - with which you now know how to deal. Let's see if I can reconstruct the problem you were having - and what you should have presented as your problem. If I remember correctly, we first had to track down a log of the VTAM where the problem in the NetView FTP was manifest and check messages at the appropriate time. There was one of those message sequences where the SSCPs tried in the subarea serial search are listed with the sense code returned from each. One of the SSCPs, a pseudo-SSCP, was ISTAPNCP which indicates the point at which the search entered the APPN part of the network at that particular VTAM node. The sense code returned was 80140002, essentially, APPN COS not found. This was caused because there was a(n unexpected) subarea COS specified as COS=WHATEVER on the MODEENT macro for the mode table entry used by NetView FTP. Since there was no APPNCOS operand specified on the MODEENT macro for this mode table entry, VTAM obliges itself to assume that the name to use for the APPNCOS operand is the same as the name used for the COS operand.[1] Since there is no APPN COS table entry WHATEVER, VTAM is about to give up when it remembers there is one last chance, namely the name specified in the APPNCOS start option put there as what in English schoolboy cricket is the long stop fielding position for when the wicket keeper makes a mess of things - he might be excused as a very fine third man if the title long stop was considered too undignified! Seriously, the APPNCOS start option is obviously a very crude tool to employ in order to select a route and set transmission priority since there is no distinction between different types of session with different requirements. I have already indicated that you probably would want to use #INTER for sessions involving Supersession. If you also had had the same problem that I did with NetView FTP, I would then have advised you to specify #BATCH as the value of the APPNCOS operand - horses
Re: CL/Supersession and APPN
Chris, Thanks for confirming the compatibility of Supersession and APPN. Is it possible to get contact information for your customer that successfully set this up? I would like to get our VTAM systems programmer to work with your customer if possible. I passed the information you provided in setting up APPN/EE to him and he was able to get APPN working, but now he is struggling with CL/Supersession. Any help you can provide would be most appreciated. Regards, John Au -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Chris Mason Sent: Monday, June 01, 2009 4:43 PM To: IBM-MAIN@bama.ua.edu Subject: Re: CL/Supersession and APPN John The customer with which I work from time to time uses Supersession. It has continued to work without any difficulties while we changed the underlying SNA architecture from subarea (cross-domain) to APPN without any difficulties whatsoever. Do you have any specific concerns? Incidentally, a systems programmer there has even researched using VTAM generic resources with Supersession with success. We hope to put that into production in the near future all in support of the general objective of introducing redundancy in support of continuous availability. It's not down to luck but understanding and planning! Chris Mason On Mon, 1 Jun 2009 14:21:05 -0500, John Au john...@paccar.com wrote: We are trying to get CL/Supersession to work with APPN and not using the VTAM Cross Domain facilities. We would like to phase out our Front end processor (3745). Has anyone had any luck doing this? -- 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 -- 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
Re: CL/Supersession and APPN
Pat, Do you remember if you had to convert all the APPLIDs to use APPC=YES? It appears when we knocked down the Cross Domains and attempt using APPN; VTAM is searching through ISTAPNCP first then the Cross Domain definitions for the APPLIDs. Since we didn't define anything in ISTAPNCP it can't locate the APPLID. We're not exactly sure if definitions are dynamically built in ISTAPNCP or whether we have to manually define them. Any help in pointing us in the right direction would be appreciated. P.S. Mark Yuhas says HI! Regards, John Au -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Patrick O'Keefe Sent: Tuesday, June 02, 2009 12:30 PM To: IBM-MAIN@bama.ua.edu Subject: Re: CL/Supersession and APPN On Tue, 2 Jun 2009 09:23:52 -0700, John Au john...@paccar.com wrote: ... he was able to get APPN working, but now he is struggling with CL/Supersession. Any help you can provide would be most appreciated. ... I haven't been in a shop with Supersession for over 5 years but I had no trouble getting it to work over APPN connections in my previous shop, and we have TPX (another session manager) working over APPN at my current shop. Do you have other cross domain sessions working over APPN? I can think of no reason there would be a problem with only Supersession. Pat O'Keefe -- 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 -- 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
CL/Supersession and APPN
We are trying to get CL/Supersession to work with APPN and not using the VTAM Cross Domain facilities. We would like to phase out our Front end processor (3745). Has anyone had any luck doing this? -- 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
Re: Configuring APPN using Hipersockets
and start option and set appropriate values for your configuration. Also note that, I have set DISCNT=NO in the DYNTYPE=VN model so that, when a connection is established dynamically on demand, it is *not* disconnected after use, this being sensible behaviour for a small number of nodes but not necessarily for a large number of nodes with infrequent internode traffic over the connections established dynamic. It is very highly recommended to specify the TGP operand so a possibly appropriate profile name has been suggested wherever it is relevant. The value of the CAPACITY characteristic strongly affects the start-up performance of Rapid Transport Protocol (RTP) connections. The LIVTIME operand shown does not have the default values. The values given may be considered as they exploit the possibility to reduce the frequency of connectivity testing over the connectionless IP network. The SRQRETRY and SRQTIME operands shown also do not have the default values. The values given are more appropriate for short distances over fast media with few or no intervening router nodes. Note that DWACT and DWINOP operands have been set to YES in order automatically to initiate connections and maintain connections, where possible. In addition REDIAL operand has been set to FOREVER so that the attempt to establish a connection is continuous with the interval given by the value of the REDDELAY operand. The RTP model is relevant because Enterprise Extender necessarily uses High Performance Routing (HPR) and, hence, RTP connections. The only relevant operands have been shown with defaults for the DISCNT and LIMRES operands. These defaults can be discerned only with some difficulty in the manuals! Of the relevant start options shown, CONNTYPE and DYNADJCP have the default setting but CPCP and DYNLU do not and therefore need to be specified in order to match the minimal definitions in these samples. - Chris Mason On Tue, 19 May 2009 11:04:24 -0700, John Au john...@paccar.com wrote: Chris, Thanks for the info. I'll direct my attention to setting up Enterprise Extenders for both LPARs. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Chris Mason Sent: Monday, May 18, 2009 11:17 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Configuring APPN using Hipersockets John Yes, it's confusing but then it's IBM! The DYNAMICXCF parameter of the IPCONFIG statement was originally set up as a way of creating an interface connected to a sort of LAN switch managed by the sysplex logic so that an interface in a Communications Server (CS) IP instance in one sysplex member LPAR can connect to a CS IP instance in another sysplex member LPAR using just one IP address per instance. However it has been extended to cover two other situations: 1. Interfaces to connect a CS IP instance to another CS IP instance running within the same LPAR (IUTSAMEH)[1] 2. Interfaces to connect a CS IP instance running within the one LPAR to another CS IP instance running within another LPAR within the same physical machine aka Central Electronic Complex (CEC) (HiperSockets) In neither of these cases is the XCF part of the name DYNAMICXCF relevant, hence the confusion. Continuing with the LAN switch concept: in 1 the switch is managed by the CS IP instances working together with the z/OS image within the LPAR; in 2 the switch is managed by the HiperSockets logic. You can confirm the various uses of the DYNAMICXCF parameter of the IPCONFIG statement in the following CS IP Configuration Guide sections: - HiperSockets concepts and connectivity in Chapter 2, IP configuration overview - Dynamic XCF in Chapter 8, TCP/IP in a sysplex You should go carefully through the whole of the second reference in order to find examples of exactly what the DYNAMICXCF parameter of the IPCONFIG statement does in various configurations. It is only at the end of this section that HiperSockets is covered. - The CS SNA component, that is VTAM, has remained true to the strict meaning of XCF, as it were, since allows for the automatic creation of connections only within a sysplex. Thus, in order to get the benefit of HiperSockets, you are obliged to set up SNA connections using Enterprise Extender definitions. Chris Mason [1] Actually this may not have been so much an extension as also having been provided originally. Perhaps some alert participant can confirm or deny this. On Mon, 18 May 2009 16:51:15 -0700, John Au john...@paccar.com wrote: Chris, I thought dynamicxcf would not work when connecting from 2 separate base sysplexes. I been attempting to connect using TRLE definitions via MPC and local major nodes for each LPAR without any luck. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Chris Mason Sent: Monday, May 18, 2009 12:59 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Configuring APPN using Hipersockets John Yes - you are obliged
Re: Configuring APPN using Hipersockets
Chris, Thanks for the info. I'll direct my attention to setting up Enterprise Extenders for both LPARs. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Chris Mason Sent: Monday, May 18, 2009 11:17 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Configuring APPN using Hipersockets John Yes, it's confusing but then it's IBM! The DYNAMICXCF parameter of the IPCONFIG statement was originally set up as a way of creating an interface connected to a sort of LAN switch managed by the sysplex logic so that an interface in a Communications Server (CS) IP instance in one sysplex member LPAR can connect to a CS IP instance in another sysplex member LPAR using just one IP address per instance. However it has been extended to cover two other situations: 1. Interfaces to connect a CS IP instance to another CS IP instance running within the same LPAR (IUTSAMEH)[1] 2. Interfaces to connect a CS IP instance running within the one LPAR to another CS IP instance running within another LPAR within the same physical machine aka Central Electronic Complex (CEC) (HiperSockets) In neither of these cases is the XCF part of the name DYNAMICXCF relevant, hence the confusion. Continuing with the LAN switch concept: in 1 the switch is managed by the CS IP instances working together with the z/OS image within the LPAR; in 2 the switch is managed by the HiperSockets logic. You can confirm the various uses of the DYNAMICXCF parameter of the IPCONFIG statement in the following CS IP Configuration Guide sections: - HiperSockets concepts and connectivity in Chapter 2, IP configuration overview - Dynamic XCF in Chapter 8, TCP/IP in a sysplex You should go carefully through the whole of the second reference in order to find examples of exactly what the DYNAMICXCF parameter of the IPCONFIG statement does in various configurations. It is only at the end of this section that HiperSockets is covered. - The CS SNA component, that is VTAM, has remained true to the strict meaning of XCF, as it were, since allows for the automatic creation of connections only within a sysplex. Thus, in order to get the benefit of HiperSockets, you are obliged to set up SNA connections using Enterprise Extender definitions. Chris Mason [1] Actually this may not have been so much an extension as also having been provided originally. Perhaps some alert participant can confirm or deny this. On Mon, 18 May 2009 16:51:15 -0700, John Au john...@paccar.com wrote: Chris, I thought dynamicxcf would not work when connecting from 2 separate base sysplexes. I been attempting to connect using TRLE definitions via MPC and local major nodes for each LPAR without any luck. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Chris Mason Sent: Monday, May 18, 2009 12:59 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Configuring APPN using Hipersockets John Yes - you are obliged to use Enterprise Extender. In the Communications Server IP component, you should rely on the IPCONFIG statement DYNAMICXCF parameter in order to establish IP interfaces to HiperSockets. If you need sample for setting up Enterprise Extender, please post again. If you do post again, please say more about your configuration. Chris Mason On Mon, 18 May 2009 12:43:59 -0500, John Au john...@paccar.com wrote: Is there a way to connect APPN Network Nodes on separate LPARs and separate base sysplexes within the same CEC using Hipersockets? If so, are there some sample configurations, I can take a look at. Everything I've tried gets me to a status of Pending request connections. Any info on this would be most appreciated. -- 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 -- 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
Configuring APPN using Hipersockets
Is there a way to connect APPN Network Nodes on separate LPARs and separate base sysplexes within the same CEC using Hipersockets? If so, are there some sample configurations, I can take a look at. Everything I've tried gets me to a status of Pending request connections. Any info on this would be most appreciated. -- 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
Re: HTTP servers on z/OS
Information Builders has one ('iWAY Full Function Server').
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Steve Comstock
Sent: Monday, May 18, 2009 10:40 AM
To: IBM-MAIN@bama.ua.edu
Subject: HTTP servers on z/OS
I'd like to compile a list of available HTTP servers
for z/OS. I'm aware of these:
* the free HPPT server V5R3 that comes with z/OS
based on the old CERN technology (but still a
viable server)
* the version of Apache server that comes with WAS
* the new free version of Apache, which comes free
without WAS (but I believe it actuall the same
version of Apache as the one that comes with WAS)
* the BEA product, whose name escapes me at the moment
But I seem to recall there are others. Anyone aware
of additional HTTP servers for z/OS?
Thanks.
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
303-393-8716
http://www.trainersfriend.com
z/OS Application development made easier
* Our classes include
+ How things work
+ Programming examples with realistic applications
+ Starter / skeleton code
+ Complete working programs
+ Useful utilities and subroutines
+ Tips and techniques
== Check out the Trainer's Friend Store to purchase z/OS ==
== application developer toolkits. Sample code in four==
== programming languages, JCL to Assemble or compile, ==
== bind and test. ==
== http://www.trainersfriend.com/TTFStore/index.html==
--
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
--
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
Re: Configuring APPN using Hipersockets
Chris, I thought dynamicxcf would not work when connecting from 2 separate base sysplexes. I been attempting to connect using TRLE definitions via MPC and local major nodes for each LPAR without any luck. -- 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
Re: Configuring APPN using Hipersockets
Chris, I thought dynamicxcf would not work when connecting from 2 separate base sysplexes. I been attempting to connect using TRLE definitions via MPC and local major nodes for each LPAR without any luck. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Chris Mason Sent: Monday, May 18, 2009 12:59 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Configuring APPN using Hipersockets John Yes - you are obliged to use Enterprise Extender. In the Communications Server IP component, you should rely on the IPCONFIG statement DYNAMICXCF parameter in order to establish IP interfaces to HiperSockets. If you need sample for setting up Enterprise Extender, please post again. If you do post again, please say more about your configuration. Chris Mason On Mon, 18 May 2009 12:43:59 -0500, John Au john...@paccar.com wrote: Is there a way to connect APPN Network Nodes on separate LPARs and separate base sysplexes within the same CEC using Hipersockets? If so, are there some sample configurations, I can take a look at. Everything I've tried gets me to a status of Pending request connections. Any info on this would be most appreciated. -- 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 -- 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
