George This looks very clear - including the sense code[1] - dare I say, for once! Perhaps you have misunderstood some aspect of the OMEGAMON documentation regarding the PARSESS operand.
The PARSESS=YES operand is used by a program using the VTAM API for the purposes of identifying the partner in certain calls/macros. Programs not capable of parallel sessions necessarily use can use the "symbolic name" field of the NIB control block (NIBSYM) in order to provide the LU name of the partner. Programs capable of parallel sessions necessarily use the "communication identifier" (CID) field of the NIB control block (NIBCID) in order specifically to identify the session. I believe the CID is used only within a particular VTAM and is not "seen" in the session itself and so whether a program using the VTAM API uses the NIBSYM field or the NIBCID field is a matter of interest only to that program and that VTAM. However, very clearly, only when the NIBCID field is used, can there be more than one session at a time with a particular partner LU. > If one partner in an LU-LU session is PARSESS=YES, I would think both partners would need to be or if not at least the PLU would need to be. Thus, where there are going to be so-called parallel sessions supported by programs both using the VTAM API, the relevant APPL statements must both specify PARSESS=YES - unless the PARSESS operand defaults to PARSESS=YES as when APPC=YES is also specified. Where there are *not* going to be so-called parallel sessions supported by programs both using the VTAM API, the relevant APPL statement of the program which only ever uses a single session with any partner LU must specify PARSESS=NO because those VTAM API calls/macros for which the PARSESS operand is important always use the NIBSYM field. You can check on this point by examination of the Communications Server SNA Programming manual searching with PARSESS. The documentation of the VTAM program should indicate that PARSESS=YES where it is appropriate because the developers wrote the program to use the VTAM API in a way which requires PARSESS=YES. If the documentation of the VTAM program does not indicate that PARSESS=YES is required, I think - check the manual very carefully - you could cause problems if PARSESS=YES is specified. - [1] <quote> Sense code 0805 Session limit exceeded: The requested session cannot be activated, as one of the NAUs is at its session limit, for example, the LU-LU session limit or the (LU, mode) session limit. This sense code applies to ACTCDRM, INIT, BIND, and CINIT requests. Bytes 2 and 3 following the sense code contain sense-code-specific information. 000B The request was rejected because a session already exists between the same LU pair, and at least one of the LUs does not support parallel sessions. </quote> - Chris Mason On Wed, 30 Mar 2011 18:26:44 -0400, George Henke <gahe...@gmail.com> wrote: >Is it possible to have such a config? > >I am getting VTAM sense code 0805000B Session Setup Error in an >OMEGAMON VTAM Terminal Pool for APPL defined with PARSESS=YES when the PLU >has PARSESS=NO. > >VTAM tries to start a session with a duplicate SLU APPL and gets the >0805000B. I suspect it is because it thinks there can be more than one >session for the SLU APPLs when in fact there cannot. > >If one partner in an LU-LU session is PARSESS=YES, I would think both >partners would need to be or if not at least the PLU would need to be. > >George Henke ---------------------------------------------------------------------- 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
