Timothy Better late than never, here is the correct answer - or at least a more accurate answer.
The full answer - in all its infamy - is given in the following post in the IBMTCP- L list: Subject: A Gross TN3270 Inconsistency in the z/OS V1R12 Communications Server Announcement http://www2.marist.edu/htbin/wlvtype?IBMTCP-L.44870 > I don't think any session managers support what you're asking due to a current VTAM limitation. Interestingly enough the "VTAM limitation" to which you refer here is not, as you probably assumed and anyone reading your post would probably assume, "technical" but "authorial"! In fact *no* session manager would be able to offer support for passing through CV64 information in a supported program - unless the vendor was IBM with private access to the necessary API information. > However, now that IBM has lifted the veil a little on z/OS 1.12, I can tell you that IBM plans to include a VTAM enhancement in 1.12 which is relevant to delivering this functionality. The "functionality" has been there since APARs OW31454 and PQ12574 to OS/390 V2R5 in 1998, it just hasn't hitherto been documented in the z/OS Communications Server SNA Programming manual - although presumably accidentally hinted at in a presentation in 2005! You just need to ask yourself how did VTAM get to know the information in the first place (A), recall that applications like TSO or CICS have access to the information (B), then concatenate B to A and you have the "functionality" for a session manager to support passing the information in relay mode. QED. > Then IBM plans to enhance IBM Session Manager (5697-N61) with code changes in the CINIT call when starting a VTAM session so that the inbound TN3270/TN3270E client address will be passed on and through to TSO. One "code change" will be to add a SETLOGON OPTCD=START call - the API element finally revealed after 12 and a half years, let's not forget the March to September - shortly after starting the session in order to pass the CV64 which can be accessed, another "code change", in the LOGON exit of the concatenated session in the CINIT *request unit image*. In other words there is no such thing as a "CINIT call". What I have said is probably an unravelling of some chinese whispers! Incidentally, there's no reason why the final application has to be TSO. It could be CICS or IMS or whatever supports a 3270 session. It's true that both TSO and CICS know how to do something with the CV64 information but I guess other applications might in time if they haven't already, the CV64 information having been available in the LOGON exit since OS/390 V2R10. Chris Mason On Mon, 22 Feb 2010 16:24:42 -0500, Timothy Sipples <[email protected]> wrote: >Shmuel, I asked around inside IBM, hence I'm replying about 10 days after >you asked your question. Sorry for the delay. > >I don't think any session managers support what you're asking due to a >current VTAM limitation. However, now that IBM has lifted the veil a little >on z/OS 1.12, I can tell you that IBM plans to include a VTAM enhancement >in 1.12 which is relevant to delivering this functionality. Then IBM plans >to enhance IBM Session Manager (5697-N61) with code changes in the CINIT >call when starting a VTAM session so that the inbound TN3270/TN3270E client >address will be passed on and through to TSO. > >IBM expects to make z/OS 1.12 generally available in September, so the >earliest you can expect this function in Session Manager is toward the end >of the year. (Insert standard disclaimers here about IBM plans, I don't >speak officially for IBM, etc.) You can ask your friendly IBM >representative for more (and official) information on Session Manager. > >- - - - - >Timothy Sipples ---------------------------------------------------------------------- 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
