Skip to content

System Files

Thoroughbred Basic can run under a variety of hardware and firmware environments. To ensure portability across hardware and firmware platforms, the Thoroughbred Basic system insulates applications developed in Thoroughbred Basic from environmental concerns. If an application does not explicitly depend on a given hardware and software configuration, you can easily port the application to a new platform.

However, the Thoroughbred Basic system is not free from environmental concerns. It must interact with a given set of hardware and firmware. This chapter describes how Thoroughbred Basic works with the resident operating system to obtain the services it needs and how to use system files to make full use of hardware and firmware:

  • For a brief description of operating system services that Thoroughbred Basic uses, and a discussion of how Thoroughbred Basic runs under an operating system that uses windows, please refer to Environmental Considerations.
  • The TCONFIGW, TCONFIG8, and TCONFIG files contain terminal specifications that describe how a terminal will interact with Thoroughbred Basic and the resident operating system. For more information on these files, please refer to TCONFIG Files.
  • The TERMINAL file contains a list of the port name, operating system window, or network node name for each Thoroughbred Basic task. For a description of the TERMINAL file, please refer to Terminal File.
  • The TERM.MAP file enables you to associate terminal definitions with task IDs. For a description of the TERM.MAP file, please refer to TERM.MAP File.
  • The TSI.INI file is where you enable or disable features available in the TS Environment for
    Windows. For more information on this file, please refer to TSI.INI File.
  • The SERVER.MAP file enables you to establish the interface between Thoroughbred products and ORACLE, MS SQL Server and MySQL databases, enables you to establish the interface between Thoroughbred products and ODBC-compliant databases, or enables new or existing applications to share data across a network. For a description of the SERVER.MAP file, please refer to SERVER.MAP File.
  • The IPLINPUT file is an initial program load (IPL) file that contains environmental information. IPLINPUT is loaded into memory whenever a user starts Thoroughbred Basic unless the user specifies a different IPL file. For more information on the IPLINPUT file, and for more information on how to create customized IPL files, please refer to IPLINPUT File.

From the Customization and Tuning Guide: System Files, version 8.9.1. Open this page in the PDF