Shmuel I am supported in not suggesting that SNA Architecture allows a negotiable BIND for LU type 2 (and LU types 1 and 3) by Table 9-8, "BIND Parameter Checking for LU Types 1, 2, and 3" in section 4.1.14.2, "BIND Check" of "3174 Establishment Controller, Functional Description", GA23-0218-11:
http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/cn7a7003 You will see that a secondary LU type 2 will reject a BIND which proposes negotiation in byte 1 of the BIND request data. You took the quote for your second point out of context. The quoted sentence comes from the section headed by the following text: <quote> Here's the explanation of how it is/used to be when one set of dimensions were to be used for some subapplications (the second set below) and another set of dimensions, typically, 24 rows and 80 columns, were to be used for other subapplications, typically subapplications designed for the ubiquitous original dimensions (the first set below) (also late-70's): </quote> I seem to recall I was careful about my text in that header paragraph, "typically" was added because the "Query Reply" allows for both sets of dimensions, default and alternate, to be specified - see Table 3-48, "Implicit Partition Sizes for Display Stations" in section 2.2.4.12, "Query Reply (Implicit Partition)" - and so an emulator (or simulator), for example, could permit the specification of all 4 numbers. I believe you are talking about dimensions you set using the X'7F' code in the penultimate byte of the PSERVIC operand. You also could be thinking of cases where you have used the X'7E' code in the penultimate byte of the PSERVIC operand and so whether the application uses "Erase Write" or "Erase Write Alternate", the operational dimensions will be the same. Chris Mason ----- Original Message ----- From: "Shmuel Metz (Seymour J.)" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <IBM-MAIN@BAMA.UA.EDU> Sent: Tuesday, 22 August, 2006 3:13 PM Subject: Re: >27x132? > In <[EMAIL PROTECTED]>, on 08/22/2006 > at 05:24 AM, Chris Mason <[EMAIL PROTECTED]> said: > > >3. The 3270 emulator must be happy to accept X'03' and the "query" > >bit in the BIND. > > >4. Following sending the BIND, the PLU sends a "query"[1] request to > >the SLU and the SLU responds with configured presentation space > >dimensions (rows and columns) - as well as other information. > > Are you sure that TSO and VTAM don't also support a negotiated BIND, > where the SLU sends back a different BIND image from what the PLU > sent? That's only relevant, of course, if your 3270 simulators has the > capability of doing so. > > >In the case of 3270 controller microcode[6], the first set of > >dimensions is 24 rows and 80 columns > > That's true for 3271/3275/3276/3278/3279 devices, but for more recent > devices the number of rows for primary need not be 24. In particular, > the 3180 and and the 3192 work just fine with a primary size of 43x80. > > -- > Shmuel (Seymour J.) Metz, SysProg and JOAT > ISO position; see <http://patriot.net/~shmuel/resume/brief.html> > We don't care. We don't have to care, we're Congress. > (S877: The Shut up and Eat Your spam act of 2003) ---------------------------------------------------------------------- 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
