PQ14588: INCORRECT LOGMODE ENTRY BEING USED TO ESTABLISH RELAY OR PASS MODE SESSIONS, INITOTHER REQUEST LOGMODE AREA CONTAINS ZEROES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Netview Access Services 2.1.1, selection of an application from
  the NVAS application selection panel results in a successful
  session setup, but using the incorrect logmode entry to setup
  the relay mode or passmode session.  User will logon to nvas
  using some type of terminal logmode (dynamic, mod5, mod4, mod3)
  and select an application from the application selection panel.
  In relay mode, nvas should compare the terminal logmode session
  characteristics and choose a matching logmode type from the nvas
  logmode table EMSMODE.  It appears that nvas is not loading the
  logmode name into the INITOTHER request, bytes 9 through 16,
  that it sends to vtam requesting a session with the selected
  application.  Rather than the logmode name being chosen these
  fields contains hex zeroes.  Thus, the default logmode is taken,
  which in many cases appears to be the first logmode from the
  EMSMODE table.  Thus, in many cases session characteristics are
  lost and the session is setup using SNA32772 mod 2 attributes.
  Extended attributes, color, screen sizes etc... appear to be
  lost.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All NV/AS users.                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: Starting an application session,        *
  *                      as in relay mode as in pass mode,       *
  *                      NVAS doesn't use, for the established   *
  *                      session, a right logmode reflecting     *
  *                      that used to log NVAS on from the       *
  *                      real terminal.                          *
  *                      The used logmode is always a not        *
  *                      queriable 24x80.                        *
  *                      This not correct behaviour has had      *
  *                      some and various symptoms:              *
  *                      -1) the command PD (Problem             *
  *                      Determination), from the Application    *
  *                      Selection panel, shows blanks in the    *
  *                      MODNAME field;                          *
  *                      -2) in some cases, some applications    *
  *                      took long time in their processing      *
  *                      maybe due to a smaller used ru size.    *
  *                      In the VTAM buffer trace of the process *
  *                      the initother ru x810680 has always     *
  *                      zeroes in the logmode name field.       *
  ****************************************************************
  * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR               *
  ****************************************************************
  As described in the "Logmode Considerations" of the shipped
  Customization book, at application session establishment time
  NVAS basically selects a logmode equivalent to that used for
  the real terminal session, by using the specific modetab table
  EMSMODE.
  In the failing case, NVAS looks like to use somewhat logmode
  like the first entry in EMSMODE, about the sessions features
  (pservic, etc), even if the logmode name is set up to zero.
  

Problem conclusion

• The analysis of the code processing the set up of the logmode
  for the application session discovered a wrong logic in some
  checks related to the processing of new feature of the
  application logmode overriding.  Those checks affected the
  right logmode setup for the appl session to be established.
  Now, a new correct logic has been implemented to avoid the not
  correct logmode setup.
  

Temporary fix

• Aparfix sent to customer for fields tests.
  

Comments

• Aparfix sent to customer for fields tests.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UQ18274

Modules/Macros

• EMSEJSEL
  

Fix information

• Fixed component name

  NVAS/ESA MVS 2.

• Fixed component ID

  569503601

Applicable component levels

• R111 PSY UQ18274

     UP98/06/04 P F806 Ž

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.