• <GetStart>
  • CSPro User's Guide
    • The CSPro System
    • Data Dictionary Module
    • The CSPro Language
    • Data Entry Module
    • Batch Editing Applications
    • Tabulation Applications
    • Data Sources
    • CSPro Statements and Functions
    • Text Templates
    • Templated Reporting System
    • HTML, Markdown, and JavaScript Integration
    • Action Invoker
    • Appendix
      • Appendix A - Installation
      • Appendix B - Keys Summary
      • Appendix C - Menu Summary
      • Appendix D - Toolbar Summary
      • Appendix E - Application Properties
      • Appendix F - Converting Within IMPS or ISSA
      • Appendix G - Errors in Censuses and Surveys
      • Appendix H - File Types
        • File Types
        • JSON Specification Files
        • SQLite Use in CSPro
        • Importing Data to CSPro Format
        • Locking Application Files
        • Temporary Data File
        • CSPro DB File Format
        • Files Description
          • Data Dictionary File (.dcf)
          • Data Entry Application File (.ent)
          • Forms File (.fmf)
          • Logic File (.apc)
          • Message File (.mgf)
          • Question File (.qsf)
          • Application Properties File (.csprops)
          • Program Information File (.pff)
          • Binary Data Entry Application File (.pen)
          • Index File (.csidx)
          • Notes File (.csnot)
          • Status File (.sts)
          • Paradata Log File (.cslog)
          • Operator Statistics File (.log)
          • Listing File
          • Frequencies File
          • Batch Edit Application File (.bch)
          • Edit Order File (.ord)
          • Saved Arrays File (.sva)
          • Tabulation Application File (.xtb)
          • Table Specifications File (.xts)
          • Tables File (.tbw)
          • Area Names File (.anm)
          • Table Matrices File (.tab)
          • Table Matrices Index File (.tabidx)
          • Frequency Specification File (.fqf)
      • Appendix I - JSON Representations
  • <CSEntry>
  • <CSBatch>
  • <CSTab>
  • <DataManager>
  • <TextView>
  • <TblView>
  • <CSFreq>
  • <CSDeploy>
  • <CSPack>
  • <CSDiff>
  • <CSConcat>
  • <Excel2CSPro>
  • <CSExport>
  • <CSIndex>
  • <CSReFmt>
  • <CSSort>
  • <ParadataConcat>
  • <ParadataViewer>
  • <CSCode>
  • <CSDocument>
  • <CSView>
  • <CSWeb>

Listing File

The listing file contains information about how an application was run and contains the results of the program's operations. It gives the following information:
  • The names of the files used.
  • The start and end time of the run.
  • Any error messages, both user and system messages, which occurred during the run.
The listing file associated with a batch edit application is often the primary output of the application. For most other applications and tools, the listing file is a secondary output. For data entry applications, this file can be useful for monitoring the work of keyers in training and identifying problem keyers.
Listing File Formats
The traditional CSPro listing file is a text file with the extension .lst. However, you may find it useful to change the listing file output based on the kind of analysis you are conducting. There are several listing file formats, with CSPro choosing which type to output based on the extension of the listing file name.
FormatExtensionResults Viewer
Text.lstText Viewer
HTML.html / .htmDefault Internet browser
JSON.jsonDefault JSON viewer
Excel.xlsxMicrosoft Excel (or other application associated with Excel files)
CSV.csvApplication associated with .csv files (often Microsoft Excel)
CSPro Data.csdb / .datData Manager
Using any extension not in the table above will result in a text listing file.
The Excel, CSV (comma-separated values), and CSPro Data listing files can only be used with applications that contain an input dictionary so they are not suitable for some tabulation applications.
Whereas the text and HTML listing files display keys of cases that had errors in text format, the JSON, Excel, CSV, and CSPro Data listing files output these keys as separate columns/items (e.g., "0901" vs. PROVINCE: 9 / DISTRICT: 1).
Error messages that occur outside of a case (for example during the application procedure) are written to all listing file formats except for CSPro Data, which only contains information about case-related errors. When using the CSPro Data listing file, a dictionary that describes the data file will be output using the name of the listing file with the added extension .dcf.
A data entry application's listing file is appended to any existing listing file, whereas listing files for batch and most tabulation applications are created from scratch for the program's run. JSON and Excel listing files do not support append mode so they may not be a suitable format for data entry or tabulation applications.