OA38223: BAD TEMPLATE RECORDS CAN CAUSE AN ABEND IN FTO STAGE II

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Approver Initials:    RB
  
   PROBLEM DESCRIPTION:
  
  An abend occurs on the MIRROR HUB during FTO stage II when a
  record in the TEMPLATE table contains a blank value for the NAME
  column.
  
  RECREATE INSTRUCTIONS:
  - Create a record in the TEMPLATE table at the primary HUB that
  contains a blank value for the NAME column. It is unknown how
  these records got into the customer's table, so you may have to
  SQL to create this
  record.
  - Start the MIRROR HUB
  - An abend should occur at the MIRROR during the MIRROR's FTO
  stage II processing.
  
  Secondary symptom: One customer experienced a flood of
  
  "sequence number overflow, reusing 999"
  
  at hundreds of times a second. The TEMS was virtually unusable.
  

Local fix

• Delete the bad records. The following SQL can be used to list
  the records in the table:
  
  
    SELECT TEMPLATE, NAME, STATE, TYPE, LOCFLAG
      FROM O4SRV.TTMPLSIT;
  
  The following SQL can be used to delete a bad record in the
  table:
  
    DELETE FROM O4SRV.TTMPLSIT
      WHERE TEMPLATE = 'XXXXX' AND NAME = " ";
  
  Replace the "XXXXX" value with the record's value in the
  TEMPLATE
  column.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All TEMS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: AN ABEND MAY OCCUR ON THE MIRROR HUB    *
  *                      MONITORING SERVER DURING FTO STAGE II   *
  *                      PROCESSING OR FLOODING OF MESSAGE       *
  *                      "SEQUENCE NUMBER OVERFLOW, REUSING      *
  *                      999".                                   *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF.                               *
  ****************************************************************
  An abend can occur on either the primary or secondary
  management servers during FTO stage II when a record in the
  TEMPLATE table contains a blank value for the NAME column.
  

Problem conclusion

• The monitoring server now prevents the abend if an invalid
  record is encountered. A message will be written to the RAS1
  log, and the record will be dumped to the log.
  

Temporary fix

Comments

APAR Information

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

  IV07524

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

Modules/Macros

• KDSMAIN
  

Fix information

• Fixed component name

  MGMT SERVER DS

• Fixed component ID

  5608A2800

Applicable component levels

• R622 PSY UA63440

     UP11/12/17 P F112

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.