John Any VTAM program knows its own name since this is fed to the ACB before it is opened. Since you are talking about receiving the CINIT, the program must be acting as the PLU in the session, so the name used to OPEN the ACB is the PLU name - the unqualified version if my reading of the manual is correct.
The NetID which is associated with the VTAM in which the OPEN was processed is one of the pieces of information made available from a pointer within the ACB after OPEN. You have already discovered that the fully-qualified SLU name is carried in the CINIT. This is made available in the LOGON exit. Thus you have all the needed information. If the program understands that names are network-qualified, it tells VTAM how clever it is with an option specified in the ACB: PARMS=(NQNAMES=YES). I'm not all that familiar with the RACF interface but it would seem to be necessary to allow for supporting VTAM programs unaware of network- qualified names by setting up a 3-part APPCLU name and to allow for supporting VTAM programs aware of network-qualified names by setting up a 4-part APPCLU name. I'm glad you referred to manuals in the plural since you need to check the basics in the SNA Programming manual and the VTAM APPC API in the SNA Programmer's LU 6.2 Guide and SNA Programmer's LU 6.2 Reference manuals. I couldn't find how VTAM builds the presumably RACROUTE call but you may have better luck! I'd be inclined to take it on trust! Chris Mason On Thu, 29 Jan 2009 14:19:19 -0600, Chase, John <[email protected]> wrote: >> -----Original Message----- >> From: IBM Mainframe Discussion List On Behalf Of Chris Mason >> >> [ snip ] >> >> > Network Job Entry Formats and Protocols ? >> >> I must say I can't find any clue in John's post that he had the >slightest >> interest in NJE!!! > >Not today, anyway. ;-) > >> Since I have been following John's VTAM-related posts of late, I >expect he is >> probably wanting to work out how encrypted data used to assure the >identity >> of the session partners is carried in the BIND request, the BIND >response and >> the FMH12 which completes the 3-way flow. This information, as >up-to-date >> as it needs to be given we are dealing quite correctly with >slow-moving >> architecture, can only be found in the "SNA Formats" manual which had >> a "level 0" in 1977[1] and a proud "level 20" as recently as 2004. > >And thanks to the URL somebody provided "direct" to _SNA Formats_, I >found what I was looking for (the SLU name is in the CINIT, not the >BIND). The only piece still "missing" is how VTAM constructs the APPCLU >resource name from which to extract the SESSKEY value. That might be >"buried" in one of the SNA Programming manuals, but if so I haven't >found it yet. > > -jc- ---------------------------------------------------------------------- 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
