Discover how to personalize your PowerOn Pro user experience.
PowerOn Pro ships with a number of configurable settings to personalize your VS Code experience as you develop.
Auto Associate PowerOn Workspace
If more than 50% of your active workspace has known PowerOn file extensions, a file association for poweron on the path will be added automatically.
Auto Deploy `#INCLUDE` Files
Controls how #INCLUDE files are deployed when deploying a PowerOn (only for non-Remote Syms).
Controls when your active Sym connection should automatically disconnect.
Controls when the language server runs PowerOn validation. Useful if you like to validate your PowerOn file each time you save.
Batch related configuration options specific to the SSH connection type.
The maximum time to wait (min) for the completion of a batch PowerOn run.
The batch queue number to use when poweronPro.batch.queueSelection is set to override.
Controls how the batch queue is selected for a batch PowerOn run. The available options will either use the first available queue, prompt you to select a queue, or use the override value set by the setting.
Controls where batch reports are displayed.
The maximum time (sec) to wait for the initialization of the Symitar CLI workers which is only used with an SSH connection type to Symitar.
Enables debug logging for the @libum-llc/symitar library. The logs will appear in the PowerOn Pro output channel.
Real-time diagnostics configuration options which are triggered when the PowerOn changes in an active text editor.
Plus Shows incorrect variable assignments and invalid data type declarations as errors for PowerOn files.
Plus Warns when a constant is reassigned in PowerOn files.
Plus Shows undefined variables or procedures as errors for PowerOn files.
Plus Validates operator and operand type compatibility in expressions for PowerOn files.
Plus Validates field mnemonics against their record types. For example, using a SHARE field mnemonic in a context that expects an ACCOUNT field will be flagged as an error.
Plus Validates function names and parameter counts. Unknown function names and incorrect numbers of arguments will be flagged as errors.
Plus Validates FMPERFORM and TRANPERFORM statements, including record type compatibility, allowed operations, TARGETFILE keyword usage, and transaction codes.
Plus Shows syntax errors detected by the PowerOn parser. These are structural issues in your PowerOn code such as missing keywords, unexpected tokens, or malformed statements.
Plus Shows unused variables as dimmed for PowerOn files.
Plus Shows an N references CodeLens above defined variables and procedures.
Configuration options for the PowerOn code formatter.
Align = signs in DEFINE sections for table-like readability.
Align logical operators (AND, OR) vertically at the end of each line in multi-line conditions. Forces line breaks at each operator.
Expand parenthesized expressions onto multiple lines with opening/closing parentheses on their own lines and content indented.
Automatically format PowerOn files when saving.
Number of spaces per indentation level (or tab width when useTabs is enabled).
Casing for PowerOn keywords, database records, and fields (e.g., TARGET, ACCOUNT, CLOSEDATE).
Maximum consecutive blank lines to preserve within divisions.
Maximum line length for PowerOn code before wrapping.
Number of blank lines between major divisions (TARGET, DEFINE, SETUP, SELECT, SORT, PRINT, TOTAL, PROCEDURE).
Add space after comma delimiters in function parameters (e.g., FUNC(a, b) vs FUNC(a,b)).
Add spaces around all operators: assignment (=), arithmetic (+, -, *, /), and comparison (<>, <, >, <=, >=). Logical operators (AND, OR,
Comma-separated list of statement types to exclude from space-around-operators formatting for the = operator (e.g., COL,DATASIZE).
Use tabs instead of spaces for indentation.
Uppercase all identifiers (variable names, procedure names). PowerOn is case-insensitive; some shops prefer all-caps for mainframe consistency.
Additional absolute directory paths to search for #INCLUDE files. These directories will be searched in addition to the directory of the PowerOn file being processed.
Plus The root path where your local Sym directories are synchronized. This is a required field for the feature and it's recommended to set as a path not directly in a typical folder structure for projects.
Controls whether a randomly named PowerOn is created, uploaded for validation, then deleted.
Controls the case of keywords, functions, variables, and records. Additionally, you'll see this reflected in other relevant areas such as hovers and snippets.
Plus Enables analyzer-driven semantic syntax highlighting with distinct tokens for variables, records, fields, procedures, constants, and literals.
Plus The number of files to download simultaneously when using SFTP sync (used by Remote Syms and Reports).
Plus Controls how Remote Syms are synchronized with the Symitar server.
sftp: Use SFTP for synchronization (no external dependencies required)
rsync: Use rsync for synchronization (requires WSL on Windows, rsync and sshpass installed)
Configuration options for the Symitar Explorer Reports feature.
Plus Background sync interval in minutes for reports. Set to 0 to disable background syncing.
Plus Number of days of reports to keep locally synced.
The port to use when connecting to the Symitar host. For almost all cases this should be 22 but if you have port-forwarded and need the flexibility to use SSH over a different port, this is how you'd do it.