I would not expect GDDM to work with logmode DYNAMICB. Have you looked into Attila Fogarasi's suggestion about R/R unit sizes?
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Alexander Huemer [[email protected]] Sent: Sunday, December 12, 2021 11:34 PM To: [email protected] Subject: Re: VTAM LU coding for 3192G display The DLOGMOD setting I had previously was D4C32XX3, which is defined as: D4C32XX3 MODEENT LOGMODE=D4C32XX3,FMPROF=X'03',TSPROF=X'03',PRIPROT=X'B* 1',SECPROT=X'90',COMPROT=X'3080',RUSIZES=X'87F8',PSERVIC* =X'028000000000000000000300',APPNCOS=#CONNECT *@KGC* EDS capability is set, according to the description of the bytes I found at [1]. Terminal behavior is identical with D4C32XX3 and DYNAMICB. The latter doesn't have X'80' set. MODEENT LOGMODE=DYNAMICB, X APPNCOS=#CONNECT, D409262 X COS=INTERACT, X FMPROF=X'02', X TSPROF=X'02', X PRIPROT=X'71', X SECPROT=X'40', X COMPROT=X'2000', X RUSIZES=X'0000', X PSERVIC=X'00C000000000000000000300' I am out of ideas. -Alex [1] https://www.ibm.com/docs/en/zos/2.1.0?topic=devices-pservic-operand-modeent-macroinstruction On Mon, Dec 13, 2021 at 02:49:26AM +0000, Seymour J Metz wrote: > Take a look at D4A32XX3, D4B32XX3 and D4332XX3. What is important is that > they all have BINDFLAG set tp BINSEDS (X'80'), indicating support for > extended data stream. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [[email protected]] on behalf of > Alexander Huemer [[email protected]] > Sent: Sunday, December 12, 2021 10:14 AM > To: [email protected] > Subject: Re: VTAM LU coding for 3192G display > > In VTAM there are several LUs defined, all equal. Only displays, no > printers. On the 3174 there is no special provisioning either. > I know of the existence of PSERVIC in the LOGMODE macros, but not how to > craft PSERVIC values. > GDDM is working e.g. on the 3290. > > -Alex > > On Sun, Dec 12, 2021 at 09:57:29PM +1100, Attila Fogarasi wrote: > > I just remembered that unrelated devices on the same controller can affect > > what are valid values for the bind for 3192g. For example if there is a > > 3287 (printer) defined on the same controller, then the max RU size is > > reduced even for the 3192g (so what would have been a valid bind with no > > 3287 configured becomes invalid). This is the reason the otherwise very > > capable 3270 architecture became abandoned :) All of this varies with > > specific device types, of course, once you get out of mainstream devices. > > Good luck getting GDDM working. > > > > On Sun, Dec 12, 2021 at 9:42 PM Attila Fogarasi <[email protected]> wrote: > > > > > Logmode is invalid for the physical device, sense 0821 means that the bind > > > was rejected due to having invalid parameters (which come from the logmode > > > entry). You might want to check the PSERVIC value. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
