To those who have been attracted by this discussion - such as Jerry, This thread started because Radoslaw Skorupka had been reading earlier threads and, like a kitten, started playing with them. This in order to introduce the English saying "Curiosity killed the cat." in a - to be taken as homourous - reference to his last comment. <g> - actually you'll remember the Cheshire Cat dissolved into just a grin. But enough of these merrymaking puns.
The key thread that attracted Radoslaw's attention is probably the one which directed readers to the following article: http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TD102151 dating from the 13 October - if I can trust Google Group's handing of posts. If you are not already the VTAM man/woman in your organisation, you will need to ask him/her to convert you - and maybe your colleagues as well - to what I used to call while teaching "The Unspecified Screen Size Bind". As mentioned this means finding or creating a suitable logmode table entry which contains X'03' in the penultimate byte of the PSERVIC operand of the MODEENT macro with X'00' in the preceding 4 bytes - although that may only be a matter of neatness since they should be ignored. If your shop relies on the IBM-supplied default logmode table ISTINCLM, then one of the logmode entries described in this thread, which includes the D4C32XX3 logmode mentioned in the article referenced above, can be used. As a matter of completeness the significance of the letter mentioned by Ray takes us back to the days of the 3274 when the "C" model was the link-attached SNA model, the "B" model was the channel-attached non-SNA model and the "D" model was another channel-attached non-SNA model - if my memory serves me correctly. Well, it always pays to check. I couldn't find a D3D32XX3 probably because, if there were one, it would look just like D3B32XX3 and, indeed, the comment reads "3274 MODEL 1B/1D (LOCAL NON-SNA)". There is, in fact, also a D3A32XX3, where the "A" refers to the channel-attached SNA model. Why two SNA models? Well, for some reason maybe known only to the designers of the 3274, there was a maximum outbound RU size limit of 1536, corresponding to the RUSIZES code X'C7', for the "A", channel-attached, model which did not apply to the "C", link-attached, model which, as I remember, had no documented limit. In case the user would like an outbound RU size larger that 1536, the D3C32XX3 logmode entry has X'F8' as the outbound RUSIZES value which corresponds to 3840 0 - for no good reason other than that value appealed to the guy who created these, essentially, sample logmode entries. Or does someone out there have the real reason. Incidentally I used to work next to that guy - twice - although he never confessed precisely to that whim. As William says, which of these or some suitable bespoke logmode entry created for you you use is a matter for your local VTAM specialist to sort out. Chris Mason ----- Original Message ----- From: "George, William (DHS-ITSD)" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <IBM-MAIN@BAMA.UA.EDU> Sent: Friday, 23 December, 2005 12:44 AM Subject: Re: 3270 screen size limit > You have to logon with the appropriate logmode too. > LOGMODE(D4C32XX3)in most cases. How you go about that depends on your > sites setup. > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Jerry Vernon > Sent: Thursday, December 22, 2005 3:08 PM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: 3270 screen size limit > > I guess I'm not sure how this works with PCOMM because I did what you > said > and I didn't see any difference in my screen size. Am I missing > something? ---------------------------------------------------------------------- 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
