A possibility is that the "some terminals" are in a state affected by a prior CICS transaction. Most likely if you are using partition support and setting the presentation space incorrectly. For some terminal types CICS will not reset terminal state between transactions and inheriting unexpected state will cause an invalid map size error intermittently. Long shot, but might be worth checking the transaction sequences for the error terminals, if you see nothing wrong with the failing transaction source code.
On Fri, Feb 11, 2022 at 9:16 AM Massimo Biancucci <mad4...@gmail.com> wrote: > John, > > in the past I saw something similar. > That time it was a "magic binary string" application sent to the terminal. > It was a kind of "dirty character" into a DB. > > Hope this helps. > Max. > > Il giorno gio 10 feb 2022 alle ore 15:57 John McKown < > john.archie.mck...@gmail.com> ha scritto: > > > According to a programmer, relaying a user error, we are "all of a > sudden" > > getting an INVMPSZ error on _some_ terminals, but not others, when > > displaying a mod5 screen using BMS SEND MAP. None of the SENDs use the > > ALTERNATE option. All the terminals are dynamically installed using the > > same model, which hasn't changed since 2009. > > > > Any thoughts on this? > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
