PK66596: LTERMS DEFINED AS PRINTERS HAVE INCORRECT NAME AFTER QCF RELOAD

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• - LTERMs (CNTs) defined as printers in ETO Support are not
  getting the correct USER (SPQB) name after reloading the
     IMS message queues using QCF.
     After using QCF to reload the IMS message queues following
     an IMS cold start, the USER (SPQB) name is the same as the
     LTERM (CNT) rather than the IMS NODE name.
     ETO Support options data set sample:
     Printer LTERM = PRT01
     NODE name     = NODE01
     Expected results:
     LTERM (CNT)  = PRT01
     USER  (SPQB) = NODE01
     Blocks in error after QCF reload:
     LTERM (CNT)  = PRT01
     USER  (SPQB) = PRT01
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All ETO Support V3.1 users.                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: LTERMS defined as printers have         *
  *                      incorrect name after QCF RELOAD.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  LTERMs (CNTs) defined as printers in ETO Support are not
  getting the correct USER (SPQB) name after reloading the
  IMS message queues using QCF.
  After using QCF to reload the IMS message queues following
  an IMS cold start, the USER (SPQB) name is the same as the
  LTERM (CNT) rather than the IMS NODE name.
  ETO Support options data set sample:
     Printer LTERM = PRT01
     NODE name     = NODE01
     Expected results:
     LTERM (CNT)  = PRT01
     USER  (SPQB) = NODE01
     Blocks in error after QCF reload:
     LTERM (CNT)  = PRT01
     USER  (SPQB) = PRT01
  

Problem conclusion

• The reason for the problem is QCF inserts messages using the
  "forced create" option, and ETO Support expects the "forced
  create" to be used only for messages destined to the IOPCB
  so it does not search its printer LTERM table.
  Prior to APAR PK49316 ETO Support searched the printer LTERM
  table even when the "forced create" bit was set.  APAR PK49316
  attempted to resolve a problem where an ISRT in a backend
  system caused a printer LTERM to be built with autologon data.
  This APAR will address both issues:
  Issue 1:  Printer LTERM table not searched when "forced create"
  used.
  ETO Support will return to the way it worked prior to
  PK49316.  It will check the printer LTERM table even when
  the "forced create" option is used.
  Issue 2:  Autologon data built when ISRTing messages in a
  backend system.
  ETO Support will check for a reserved DD name (IZTBKEND)
  that will identify an IMS as a backend system.  When this DD
  name is present ETO Support will not return autologon
  data if the LTERM is found in the printer LTERM table.
  

Temporary fix

Comments

APAR Information

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

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

  UK38011

Modules/Macros

• IZTINSXA IZTINSX7 IZTINSX8 IZTINSX9 IZTINTXZ
  

Fix information

• Fixed component name

  IMS ETO SUPPORT

• Fixed component ID

  5655E1200

Applicable component levels

• R310 PSY UK38011

     UP08/07/11 P F807

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.