--- manual: IM 36K10R20-01EN title: Setup File Editor edition: 4th Edition, Feb. 2026 (first written from the 3rd Edition, Sep. 2023) version: R1.05 (first written for R1.03) status: from docs; launcher, file location and metadata keywords checked read-only on the R1.03 test system (2026-09-30) and on the R1.05 test server (2026-10-08); editor GUI checked on R1.03 only (R1.05 awaiting user verification, ISS-113) --- # Setup File Editor (R1.05) What setup files are, how the Setup File Editor shows and changes them, and the comment keywords (metadata) inside a setup file that the editor reads to build its forms. Section numbers refer to the manual. **R1.03 to R1.05 (full text diff, 2026-10-08):** there is no R1.04 edition; the 4th Edition (R1.05) only adds contact information (one punctuation change). Section numbering unchanged. Installed software: the launcher `fsuedit.cmd` starts the same Java class and only adds `tls\exe\lib\*` to the class path; the installed setup files use exactly the same set of metadata keywords and the same seven argument kinds as in R1.03. ## 1. Setup files (§1) - CI Server reads its setup files (`*.sup`) **at startup**. Installed files hold the default values; change a value, then **restart CI Server** for it to take effect. - Location: `%TLS_ROOT_PATH%\tls\sup` (about 200 files on the R1.03 test system and on the R1.05 test server). Plain text. - Lines starting with `!` are comments/metadata; the other lines are the active settings, normally `KEYWORD = value[, value…]`. - The editor does not handle non-ASCII text (it is shown garbled), so labels cannot be localised. ## 2. Using the editor (§2) - Start: Start menu *CI Server → Setup File Editor* (on the R1.03 and R1.05 test systems this runs `%TLS_ROOT_PATH%\tls\com\fsuedit.cmd`, a Java program). - Main window: tabs *Setup Files* and *Templates* (the latter not in the manual, ISS-016); the list shows file name, description and status: *Default* when the active values equal the file's `!DEFAULT` block, *Changed* when any differs (ISS-016). - Double-click a file (or *File → Edit Setup File*) to open its form: one tab per group of entries, with *OK*, *Cancel* and *Help* (help text of the entries). A field whose value differs from its default has a **blue** label. The manual says *OK* keeps changes in memory until *Exit*; in R1.03 **OK writes the file at once** (ISS-016). R1.03 also shows *Undo Field* and *Reset Field*. *Reset Field* is enabled when the cursor is in a changed field and sets it back to its `!DEFAULT` value; *OK* then saves. - A keyword that may repeat (`!TIMES = INF`, e.g. `PROXY_ENTRY` in `jwuiisg.sup`) is shown as a frame (its `!LABEL`) with one input per argument and an *Add* button, a table with one row per active line and one column per argument, and icon buttons beside the table (apparently delete, update selected row, move up, move down; not in the manual, seen in R1.03). - *File* menu: *Edit Setup File*; *Open File* (opens the raw file in Notepad); *Print…* (preview, then print); *Refresh* (re-read the list, e.g. after changing metadata); *Exit* (per the manual, asks whether to save unsaved changes). - *Edit* menu: *Reset to Default* (only for files that define defaults); *Edit Description* (not usable); *Toggle Read Only* (locks a file against editing in the editor; toggle again to unlock). - *Help* menu: editor help. Most commands are also on the right-click menu of the list. - Unavailable commands are greyed out for a given file. ## 3. Metadata keywords (§3) The editor builds its forms from comment lines in the setup file. All start with `!`. **File level (§3.1)** | Keyword | Purpose | |---|---| | `!DESCRIPTION = ` | Description in the file list (first one wins; missing → "(Unknown)") | | `!INFO` … `!ENDINFO` | Text for an *Information* tab | | `!TAB =