IO17853: NETSCAPE/SUNONE CHANGELOG MCHANGENUMBER IS STORED EVEN THOUGH THE CONNECTOR HAS NOT SUCCESSFULLY READ A CHANGELOG ENTRY

APAR status

• Closed as program error.

Error description

• Netscape/SunOne Changelog mChangenumber is stored even though
  the
  connector has not successfully read a changelog entry.
  
  
  A communications error occurred during the getNextEntry()
  operation and
  the Connector logged the error and incremented the 'change
  number'
  counter.
  
  The incremented change number was stored ahead of the actual
  changelog number.
  
  Then , for each next change, it was one change number too high,
  and
  could not return any more changes.
  
  WORKAROUND:  You have to stop the AL and manually realign the
  change
  number.
  
  NEXT ISSUE (can happen when the wrong change number is stored)
  In the  getNextEntry() the Connector reads, then increments the
  change
  number, and then tries to parse the Entry.
  If that fails, it logs the error for the wrong change number.
  
  Desired Behavior: Change numbers are stored correctly when
  communication
  error has occured.
  
  Environment:  TDI 7.1.1 FP1
  

Local fix

• 1772
  

Problem summary

• Problem with Netscape/Sunone changelog Connector.
  

Problem conclusion

• This is bug in TDI code and has been fixed, formal fix will be
  made avialable in 7.1.1-TIV-TDI-FP0003.
  

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:

Fix information

• Fixed component name

  ITDI MULTIPLATF

• Fixed component ID

  5724D9960

Applicable component levels

• R711 PSY

     UP