Scott > ... CICS, aka kicks, was the Plu
And your point is ... Just to be clear, in the case of a session between CICS and a "device-type" LU of which a 3270 system display or printer is an example, these being the types of LU appearances supported by a TELNET server as appears to be Greg Shirey's concern, CICS is always the primary LU and the "device-type" LU is the secondary LU. However, when CICS is supporting SSCP-independent LU 6.2, CICS can be either the primary LU or the secondary LU. Thus CICS is not invariably the primary LU. If you had addressed your comment to Greg, I could have deduced that you were wanting to point out that the APPL statement definition had a gross error in it - one that is present in the SEZAINST VTAMLST sample to the eternal shame of the Communications Server IP developer who created the sample and all who have reviewed it since but one that VTAM just ignores - that AUTH=NVPACE can apply *only* to the representation of an LU which becomes the primary LU in the session. And, of course, if CICS is the primary LU, the SNA-oriented TELNET server APPL statement must represent the secondary LU and operand AUTH=NVPACE is utter nonsense! Incidentally, the only APPL statement operands which have any merit are EAS=1 for the purposes of conserving storage and SESSLIM=YES mentioned in an APAR apparently to resolve a problem detected in times gone by but also just logical. What is missing is REGISTER=NO since the LU represented by these APPL statements will always be an "origin" LU and never a "destination" LU. Chris Mason On Mon, 23 Jul 2012 23:33:15 -0400, Scott Ford <scott_j_f...@yahoo.com> wrote: >Chris, > >My VTAM is old but I seem to Remember that CICS, aka kicks, was the Plu > >Scott ford >www.identityforge.com > >On Jul 23, 2012, at 6:47 PM, Chris Mason <chrisma...@belgacom.net> wrote: > >> Greg >> >> You still need a pool even if it has only one entry. >> >> I checked the IP and SNA Codes manual and it is misleading. When the first 4 >> bytes of the sense code are X'0000' it's a sense code invented by the VTAM >> logic which emulates a "pre/non-SNA" channel-attached 3270, originally 3277s >> supported through the 3272 control unit. >> >> As a matter of interest, with what sort of a 3270 does CICS think it is >> working? What mode table entry name is being used in both cases. Is CICS >> using autoinstall? Does CICS care about the LU name, the real SNA/VTAM LU >> name? Note that the SNA-oriented TELNET server (TN3270) LU name is, as a >> starting position, internal to TN3270. >> >> This is just a quick response, I'll look more at it tomorrow. It's after >> midnight and I got up early - yesterday! >> >> You might like to post on IBMTCP-L if you haven't doe so yet. >> >> Chris Mason >> >> P.S. I hope casual readers of your post, unfamiliar with the SNA-oriented >> TELNET server, understand that we are using correct abbreviations here! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
