On Tuesday, 01/04/2011 at 10:58 EST, Malcolm Beattie <beatt...@uk.ibm.com>
wrote:
> Alan Altmark writes:
> > As others have said, the problem is in the logmode associated with the
> > non-SNA 3270 LU. For some reason, VTAM sysprogs keep using ancient
> > logmodes for reasons they can't actually articulate except "that's the
way
> > we've always done it." For almost a quarter century, the correct
logmode
> > for any 3270 has been D4A3290 (local SNA) or D4B3290 (non-SNA).
>
> I was unable to get these logmode names to work and they don't appear
> in the z/OS 1.9 Comms Server SNA Resource Definition Reference Manual.
>
> However, the manual does document logmodes D4A32XX3 and D4B32XX3 in
> the "Default logon mode table (ISTINCLM)" in Appendix A and their
> behaviour closely matches your description....
>From ISTINCLM ASSEMBLE:
FLAG REASON RELEASE DATE ORIGIN FLAG DESCRIPTORS
---- ------ ------- ------ ------ ----------------
$01= VM39614 VM330 900117 042852: CORRECT ERRORS IN THE PSERVIC OF
D4C3290, D4B3290, D4A3290
$03= VM46183 VM340 910402 810410: INCLUDE LOGMODE ENTRIES
D4B32XX3 AND D4C32XX3.
$04= VM46559 VM340 910819 914077: INCLUDE LOGMODE ENTRY D4A32XX3
Perhaps the 3290 versions are specific to z/VM. It wouldn't be the first
time that VM accidentally got Good Stuff that MVS didn't. It apparently
took an additional release cycle to create the properly-named 32XX
versions common to both MVS and VM.
Alan Altmark
z/VM and Linux on System z Consultant
IBM System Lab Services and Training
ibm.com/systems/services/labservices
office: 607.429.3323
alan_altm...@us.ibm.com
IBM Endicott
