JR50283: THE FIXTOOL IS INCORRECTLY REPORTING NO LINKS EXIST TO BUFFER.

APAR status

• Closed as program error.

Error description

• Details on errors are shown when the -logging option is used;
  for example:
  
  $ fixtool -file RT_CONFIG167 -logging -logpath /tmp
  $ cat /tmp/log.RT_CONFIG167/LOGFILE
  Start
  Filename: RT_CONFIG167/OVER.30  Primary Buffer: 0
  Secondary Buffer: 3    Record In Group: 0       Buffer Address:
  0x1800   - No links exist to buffer.
  Filename: RT_CONFIG167/OVER.30  Primary Buffer: 0
  Secondary Buffer: 4    Record In Group: 0       Buffer Address:
  0x2000   - No links exist to buffer.
  Complete
  

Local fix

Problem summary

• fixtool incorrectly reports errors on a dynamic file when the
  last record in a primary group contains oversized data.
  

Problem conclusion

• Ensure fixtool processes oversized data buffers in final records
   in primary groups.  This prevents fixtool from reporting that
  no links exist to buffers in OVER.30.
  

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

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R850 PSY

     UP