System variables are special values that the operating system, database, or runtime environment sets for you to describe the current system, user, or execution context. Here are clear examples in different areas.

Classic OS / environment system variables

Common examples you’ll see on Windows, macOS, and Linux:

  • PATH – List of directories the system searches for programs so you can run python or node without typing their full path (like C:\Python\python.exe).
  • HOME (or USERPROFILE on Windows) – Path to the current user’s home directory where personal files and configs live.
  • TEMP / TMP – Directory used to store temporary files created by apps and the OS.
  • OS – Name/identifier of the operating system (for example, Windows_NT).
  • USERNAME / USER – Name of the currently logged‑in user account.
  • SHELL (Unix-like systems) – The user’s default shell (for example, /bin/bash).
  • LANG / LC_ALL – Current language/locale settings that control things like date and number formatting.

These are often called environment or system variables and are read by many programs at startup.

System variables in databases

Many databases have their own system variables that describe configuration or the current session:

  • Current date and time variables used in display or compute statements (for example, variables representing today’s date or current time in a Natural program).
  • Execution-related variables in workflow/datapipeline tools (like row count, status, project ID) that are automatically filled after a component runs.

For instance, a data orchestration tool can expose:

  • A variable like .environment.name – name of the environment where a pipeline runs.
  • .project.id – ID of the current project.
  • .thisComponent.rowCount – number of rows processed by the current step in a pipeline.

These are read‑only and updated automatically to reflect the current run.

System variables in automation / workflow tools

Modern automation platforms define system variables to help with logging, error handling, and tracking:

  • Scenario or workflow ID , name , and URL to track where an error happened.
  • Job or workflow class (like a JOBCLASS variable on a mainframe workflow) that is substituted into job control statements.
  • Execution metrics such as number of operations used or whether a job exceeded some quota.

Example: in a pipeline tool, you might check a system variable for row count and branch the workflow if more than 1,000 rows were processed.

Why system variables matter (quick recap)

  • They give programs context : user, OS, environment, paths, or run statistics.
  • They are usually set by the system , not by your code, and often read‑only.
  • They help write generic scripts and apps that adapt to different machines and environments without hard‑coding values.

TL;DR: Examples include PATH, HOME, TEMP, OS, USERNAME at the OS level, and things like environment name, project ID, row count, and workflow IDs in databases and automation tools.