IJ36575: VIOSBR AUTOBACKUP : ERROR- BACKUP XML FILE IS NOT WELL FORMED

APAR status

• Closed as program error.

Error description

• viosbr autobackup failure with error: ERROR- Backup XML
  file is not well formed.
  
  ./backup_trace.out
  30671274:Dec  1 2021, 07:00:25 backup.c
  1.11.1.95 5633  backup_vioscfg:Checking the integrity of
  the XML file:
  /home/ios/DFO_SSP.29884700/DFO_SSPMTM9080-M9S027839EF8P1.
  xml
  30671274:Dec  1 2021, 07:00:25 saxParser_utils.c
  1.8.1.46 5277  checkXMLIntegrity:START
  30671274:Dec  1 2021, 07:00:25 saxParser_utils.c
  1.8.1.46 5296  checkXMLIntegrity:ERROR- Failed to create
  XML Parser context
  30671274:Dec  1 2021, 07:00:25 saxParser_utils.c
  1.8.1.46 5300  checkXMLIntegrity:END. rc=-1
  30671274:Dec  1 2021, 07:00:25 backup.c
  1.11.1.95 5637  backup_vioscfg:XML validation of
  /home/ios/DFO_SSP.29884700/DFO_SSPMTM9080-M9S027839EF8P1.
  xml failed. rc = -1
  30671274:Dec  1 2021, 07:00:25 backup.c
  1.11.1.95 5639  backup_vioscfg:ERROR- Backup XML file is
  not well formed. Please contact IBM Support.
  30671274:Dec  1 2021, 07:00:25 backup.c
  1.11.1.95 5671  backup_vioscfg:END, rc=-1.
  30671274:Dec  1 2021, 07:00:25 virtualcfg.c
  1.7.5.10 591   main:END, rc=-1
  

Local fix

• n/a
  

Problem summary

• viosbr autobackup could fail checkXMLIntegrity() and output
  "ERROR- Backup XML file is not well formed." if the XML was
  marked to be cleaned up.
  

Problem conclusion

• Check if XML was removed or not before calling
  checkXMLIntegrity().
  

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

  VIRTUAL I/O SER

• Fixed component ID

  5765G3400

Applicable component levels