Example 5-49 Using the RACF SMF Unload Utility Input panel to generate XML files from SMF data RACF SMF Unload Utility - Input Panel . Virtual address of input SMF data minidisk 0301 . Virtual address of output minidisk 0191 . Filename and filetype of sequential output file . Filename and filetype of XML easily readable ________ ________  output file . Filename and filetype of XML compressed RACFADU1 XML_____  output file PF1 = Help PF2 = Execute PF3 = Quit ENTER = Verify input fields Enter CP/CMS Commands below: ====>  <xml version='1.0' encoding='ISO8859-l'> <securityEventLog xmlns='http://www.ibm.com/xmlns/zOS/IRRSchema'> <rdf:Description rdf:about='' xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#' xmlns:dc='http://purl.org/dc/elements/1.1/'> <dc:creator> RACF for z/VM SMF Unload (HRF6030)</dc:creator> <dc:subject>RACF Security Event Log 2016-06-23 13:37:39</dc:subject> <dc:language>en</dc:language> </rdf:Description> </securityEventLog> </xml> Example 5-51 Correcting the XML close tag Example 5-50 Changing the XML header At the bottom of the file, it is missing the close tag for the XML, and some browsers might  encounter problems opening the file. In this case, add the missing tag, as shown in  Example 5-51. After the file is created, use the IBM Personal Communications program or any other method  available on your installations to download the file from the A disk to the desktop in  text  mode.  After you download the file, open it with an editor and change the encoding value and XML  syntax error on the first line, as shown in Example 5-50 (and as documented in  RACF  Security Server Auditor’s Guide , SC24-6311). This step is required because of the mismatch  between the z/VM use of EBCDIC versus the PC that uses ASCII.  Chapter 5. Security policy management on IBM z/VM  149