VSI OpenVMS Wiki - User contributions [en]

COBOL light-weight IntelliSense

2019-11-20T08:00:40Z

Andrey.logachev:

{| style="border-style: none;"
|-
|rowspan="1"| [[File:Cobol-intellisense-1.png|frame|left|COBOL syntax highlighting]]
|style="vertical-align:top; padding-left: 20px;" |

===Features===
* Symbols definition on hover over
* Symbols navigation
* Symbols renaming
* Scope resolution
* Code completion
* Syntax highlighting

===Limitations===
* '''REPLACE''' statement is not supported
* '''COPY''' statement handles only local files without '''REPLACING'''
* '''EXTERNAL''' symbols resolved only for local files (including dependent local COBOL projects)
* Operand types are not checked (planned)
|}

[[Category:VMS IDE]]

COBOL light-weight IntelliSense

2019-11-20T07:58:50Z

Andrey.logachev: /* Limitations */

{| style="border-style: none;"
|-
|rowspan="1"| [[File:Cobol-intellisense-1.png|frame|left|COBOL grammar]]
|style="vertical-align:top; padding-left: 20px;" |

===Features===
* Symbols definition on hover over
* Symbols navigation
* Symbols renaming
* Scope resolution
* Code completion
* Syntax highlighting

===Limitations===
* '''REPLACE''' statement is not supported
* '''COPY''' statement handles only local files without '''REPLACING'''
* '''EXTERNAL''' symbols resolved only for local files (including dependent local COBOL projects)
* Operand types are not checked (planned)
* Some syntax errors may not be highlighted (and not all highlighted words are in error state)
|}

[[Category:VMS IDE]]

File:Force-sync-1.png

2019-11-20T07:44:30Z

Andrey.logachev: Andrey.logachev uploaded a new version of File:Force-sync-1.png

Force-sync-1

VMS IDE Tips

2019-11-20T07:42:47Z

Andrey.logachev:

== Tip & Tricks ==

; Force synchronized status
: When VS Code opens a project, the source code is in '''undefined''' synchronization state. If you are sure your code on the VMS system is the same as on your PC, you may run the '''Force synchronized status''' command.
: This command operates only with the project selected in the '''Project explorer'''.
: [[File:Force-sync-1.png|800px|thumb|none|Force-sync]]

[[Category:VMS IDE]]

Fortran syntax highlighting

2019-11-20T07:38:01Z

Andrey.logachev:

{| style="border-style: none;"
|-
|rowspan="1"| [[File:Fortran-1.png|Fortran-syntax-example|frame|left]] [[File:Fortran-2.png|frame|left|Syntax check]]
|style="vertical-align:top; padding-left: 20px;" |

===Features===
; Autocomplete : Code autocompletion helps you write valid code in a more efficient way.
; Error checking : Checks syntax errors in real-time.
; Jump to definition (variables, routines) : Code navigation lets you quickly navigate Fortran projects (context menu).
:* Go to Definition (<code>F12</code>) - Go to the source code of a symbol definition.
:* Peek Definition (<code>Alt+F12</code>) - Bring up a Peek window that shows the definition of a symbol.
:* Peek References (<code>Shift+F12</code>) - Bring up a Peek window that shows all references to a symbol.
:* Find All References (<code>Shift+Alt+F12</code>) - Show all references to a symbol.

; Rename (variables, routines) : Rename feature lets you quickly rename symbols in Fortran projects (context menu).
: Press <code>F2</code> to rename the symbol under the cursor across your Fortran project.

; Hover information : Hover over a Fortran symbol to quickly see its type information.
: You can also show the hover info at the current cursor position with the <code>Ctrl+K Ctrl+I</code> keyboard shortcut.

|}

[[Category: VMS IDE]]

COBOL light-weight IntelliSense

2019-11-20T07:37:44Z

Andrey.logachev:

{| style="border-style: none;"
|-
|rowspan="1"| [[File:Cobol-intellisense-1.png|frame|left|COBOL grammar]]
|style="vertical-align:top; padding-left: 20px;" |

===Features===
* Symbols definition on hover over
* Symbols navigation
* Symbols renaming
* Scope resolution
* Code completion
* Syntax highlighting

===Limitations===
* REPLACE statement is not supported
* COPY statement handles only local files without REPLACING
* EXTERNAL symbols resolved only for local files (including dependent local COBOL projects)
* Procedure parameters are not checked (planned)
* Operand types are not checked (planned)
* Some syntax errors may not be highlighted (and not all highlighted words are in error state)
|}

[[Category:VMS IDE]]

Fortran syntax highlighting

2019-11-20T07:34:08Z

Andrey.logachev:

VMS IDE supports syntax highlighting for Fortran.

{| style="border-style: none;"
|-
|rowspan="1"| [[File:Fortran-1.png|Fortran-syntax-example|frame|left]] [[File:Fortran-2.png|frame|left|Syntax check]]
|style="vertical-align:top; padding-left: 20px;" |

===Features===
; Autocomplete : Code autocompletion helps you write valid code in a more efficient way.
; Error checking : Checks syntax errors in real-time.
; Jump to definition (variables, routines) : Code navigation lets you quickly navigate Fortran projects (context menu).
:* Go to Definition (<code>F12</code>) - Go to the source code of a symbol definition.
:* Peek Definition (<code>Alt+F12</code>) - Bring up a Peek window that shows the definition of a symbol.
:* Peek References (<code>Shift+F12</code>) - Bring up a Peek window that shows all references to a symbol.
:* Find All References (<code>Shift+Alt+F12</code>) - Show all references to a symbol.

; Rename (variables, routines) : Rename feature lets you quickly rename symbols in Fortran projects (context menu).
: Press <code>F2</code> to rename the symbol under the cursor across your Fortran project.

; Hover information : Hover over a Fortran symbol to quickly see its type information.
: You can also show the hover info at the current cursor position with the <code>Ctrl+K Ctrl+I</code> keyboard shortcut.

|}

[[Category: VMS IDE]]

COBOL light-weight IntelliSense

2019-11-20T07:20:07Z

Andrey.logachev:

{| style="border-style: none;"
|-
|rowspan="1"| [[File:Cobol-intellisense-1.png|frame|left|COBOL grammar]]
|style="vertical-align:top; padding-left: 20px;" |

'''Features'''
* Symbols definition on hover over
* Symbols navigation
* Symbols renaming
* Scope resolution
* Code completion
* Syntax highlighting

'''Limitations'''
* REPLACE statement is not supported
* COPY statement handles only local files without REPLACING
* EXTERNAL symbols resolved only for local files (including dependent local COBOL projects)
* Procedure parameters are not checked (planned)
* Operand types are not checked (planned)
* Some syntax errors may not be highlighted (and not all highlighted words are in error state)
|}

[[Category:VMS IDE]]

VMS IDE Change Log

2019-11-19T16:47:21Z

Andrey.logachev:

=== 1.3.0 ===
* Light-weight IntelliSense for Fortran and Cobol.

=== 1.2.6 ===
* Fixed the issue when the extension crashed when opening a C project.
* Fixed duplicating algorithms in SSH settings.

=== 1.2.3 - 1.2.5 ===
* Added function breakpoints.
* Added data breakpoints (without user interface).

=== 1.2.2 ===
* Fix the issue with display/set unicode string in '''Java''' debugger.
* JVM Debugger can now collect fields of Java classes.

=== 1.2.1 ===
* Fix issues with templates in '''Java'''.

=== 1.2.0 ===
* Added support for '''Java''', '''Kotlin''' and '''Scala''' languages.
* One output channel for all extension messages.

=== 1.1.0 ===
* '''Pascal''' syntax highlighting.
* OpenVMS specific '''COBOL''' grammar support.

=== 1.0.2 ===
* Allow users to skip signature verification in SSH (cause: Visual Studio Code 1.36.1 issue).

=== 1.0.1 ===
* Fix: parsing compiler errors that occurred on the same line of source code.
* OpenVMS specific '''Pascal''' grammar basic support.
* Debugger: skip querying symbols with invalid names.

[[Category:VMS IDE]]

VMS IDE

2019-11-19T16:44:53Z

Andrey.logachev:

'''VMS IDE''' is an integrated development environment that enables you to quickly and easily develop comprehensive applications for OpenVMS system. It provides a set of tools for developing, building, and debugging OpenVMS projects.

=Features=
[[File:Vms ide.png|800px|thumb|none|VMS IDE]]
* Source code '''synchronization''' between the local machine and OpenVMS system.
* '''SSH connection''' setup to the remote OpenVMS system.
* '''Projects Explorer''' as a simple and convenient way to manage OpenVMS projects.
* '''Debugger''' for OpenVMS and JVM projects.
* '''Highlighting''' for '''MMS''', '''CLD''', '''MSG''', '''Pascal''', '''Fortran''' and '''Cobol''' source files.
* '''Light-weight IntelliSense''' for '''CLD''', '''MSG''', [[Pascal syntax highlighting|'''Pascal''']], '''Fortran''' and [[COBOL light-weight IntelliSense|'''Cobol''']].
* Supported languages for '''debugging''': '''C''', '''C++''', '''Fortran''', '''Cobol''', '''Pascal''', '''Basic''', '''Bliss''', '''Java''', '''Kotlin''', '''Scala'''.

=Restrictions=
* The '''VMS IDE''' extension can only be used in conjunction with ODS-5 OpenVMS file systems; it cannot be used with ODS-2 file systems.
* Do not use the minus sign ("-") in file names. This may prevent the debugger from finding the source file.

=Getting Started=
This guide will help you install the VMS IDE extension and start working on your projects.

===Quick Start===
* [[VMS_IDE_Installation|Installing VMS IDE]]
* [[VMS_IDE_Project_Configuration|Setting up a VMS Project]]
* [[VMS_IDE_Developing|Working on a VMS Project]]

===Settings===
* [[Project Settings]]
* [[SSH Settings]]
* [[Synchronize Configuration|Synchronize Settings]]
* [[Build Configurations]]

===Commands===
* [[VMS_IDE_Commands|VMS IDE Commands]]

===Components===
* [[VMS_IDE_Project_Explorer|Project Explorer]]
* [[VMS_IDE_Debugger|Debugger]]

=Changelog=
[[VMS IDE Change Log]]

[[Category:VMS IDE]]

VMS IDE Change Log

2019-09-10T10:09:01Z

Andrey.logachev:

=== 1.2.6 ===
* Fixed the issue when the extension is crashed while opening a C project.
* Fixed duplicating algorithms in SSH settings.

=== 1.2.3 - 1.2.5 ===
* Added function breakpoints.
* Added data breakpoints (without user interface).

=== 1.2.2 ===
* Fix the issue with display/set unicode string in '''Java''' debugger.
* JVM Debugger can now collect fields of Java classes.

=== 1.2.1 ===
* Fix issues with templates in '''Java'''.

=== 1.2.0 ===
* Added support for '''Java''', '''Kotlin''' and '''Scala''' languages.
* One output channel for all extension messages.

=== 1.1.0 ===
* '''Pascal''' syntax highlighting.
* OpenVMS specific '''COBOL''' grammar support.

=== 1.0.2 ===
* Allow users to skip signature verification in SSH (cause: Visual Studio Code 1.36.1 issue).

=== 1.0.1 ===
* Fix: parsing compiler errors that occurred on the same line of source code.
* OpenVMS specific '''Pascal''' grammar basic support.
* Debugger: skip querying symbols with invalid names.

[[Category:VMS IDE]]

VMS IDE Change Log

2019-09-04T17:34:48Z

Andrey.logachev: /* 1.2.2 */

=== 1.2.3 - 1.2.5 ===
* Function breakpoints.
* Data breakpoints without UI.

=== 1.2.2 ===
* Fix for display/set unicode string in '''Java''' debugger.
* Ability to collect fields of Java classes.

=== 1.2.1 ===
* Fix issues with templates in '''Java'''.

=== 1.2.0 ===
* Support for '''Java''', '''Kotlin''' and '''Scala''' languages.
* One output channel for all extension messages.

=== 1.1.0 ===
* '''Pascal''' syntax highlighting.
* OpenVMS specific '''COBOL''' grammar support.

=== 1.0.2 ===
* Allow users to skip signature verification in SSH (cause: Visual Studio Code 1.36.1 issue).

=== 1.0.1 ===
* Fix: parsing compiler errors that occurred on the same line of source code.
* OpenVMS specific '''Pascal''' grammar basic support.
* Debugger: skip querying symbols with invalid names.

[[Category:VMS IDE]]

VMS IDE Change Log

2019-09-04T17:32:40Z

Andrey.logachev: /* 1.2.3 */

=== 1.2.3 - 1.2.5 ===
* Function breakpoints.
* Data breakpoints without UI.

=== 1.2.2 ===
* Fix for display/set unicode string in '''Java''' debugger, collecting fields of java classes.

=== 1.2.1 ===
* Fix issues with templates in '''Java'''.

=== 1.2.0 ===
* Support for '''Java''', '''Kotlin''' and '''Scala''' languages.
* One output channel for all extension messages.

=== 1.1.0 ===
* '''Pascal''' syntax highlighting.
* OpenVMS specific '''COBOL''' grammar support.

=== 1.0.2 ===
* Allow users to skip signature verification in SSH (cause: Visual Studio Code 1.36.1 issue).

=== 1.0.1 ===
* Fix: parsing compiler errors that occurred on the same line of source code.
* OpenVMS specific '''Pascal''' grammar basic support.
* Debugger: skip querying symbols with invalid names.

[[Category:VMS IDE]]

VMS IDE Change Log

2019-09-02T18:30:43Z

Andrey.logachev:

=== 1.2.3 ===
* Function breakpoints.
* Data breakpoints without UI.

=== 1.2.2 ===
* Fix for display/set unicode string in '''Java''' debugger, collecting fields of java classes.

=== 1.2.1 ===
* Fix issues with templates in '''Java'''.

=== 1.2.0 ===
* Support for '''Java''', '''Kotlin''' and '''Scala''' languages.
* One output channel for all extension messages.

=== 1.1.0 ===
* '''Pascal''' syntax highlighting.
* OpenVMS specific '''COBOL''' grammar support.

=== 1.0.2 ===
* Allow users to skip signature verification in SSH (cause: Visual Studio Code 1.36.1 issue).

=== 1.0.1 ===
* Fix: parsing compiler errors that occurred on the same line of source code.
* OpenVMS specific '''Pascal''' grammar basic support.
* Debugger: skip querying symbols with invalid names.

[[Category:VMS IDE]]

VMS IDE for Java (Kotlin, Scala)

2019-09-02T18:16:41Z

Andrey.logachev:

'''Note: support for JVM based languages (Java, Kotlin, Scala) will be available soon'''

== Working on a Java, Kotlin or Scala project ==

=== Creating and building a project ===
The general development process includes the following steps:
# Change project settings:
#* '''project type''' - specify ''java'', ''scala'' or ''kotlin''
#* '''project name'''
#* '''root folder'''
#* '''source''', '''headers''', '''resource''', and '''listing''' masks
# Write code
# Create MMS
# Upload source files
# Build the project
# Collect Java classes. This step is required for debugging.
# Run the project

=== Restrictions ===
Because the project target is compiled by one command for all source files, do not mix Kotlin, Scala, and Java source files in one project.

=== Abilities ===
A Java, Scala or Kotlin project may depend on other Java, Scala or Kotlin projects.

== Debugging ==

=== Before starting debug ===
To be able to use breakpoints during debugging, run '''Collect Java classes''' after editing and building the project.

=== Running VMS JVM Debugger ===
<ol>
<li> To start Debugger, press <code>F5</code>. If no debug configuration is selected, the ''Select environment'' dropdown will be shown. [[File:Jvm-dbg-select.png|dbg-select]]</li>
<li> Choose '''VMS JVM Debugger'''. If all java classes are collected successfully, the ''entry class'' QuickPick popup will be shown. [[File:Jvm-dbg-select-main.png|select-main]]</li>
<li> Select one and debugging will start. </li>
</ol>

=== Creating Debug Configurations ===
You can configure 'launch.json' to start predefined debug configuration. To do this,
<ol>
<li> Click 'Configure or Fix...' button on the DEBUG panel. 
[[File:Jvm-dbg-configure-or-fix.png|dbg-configure-or-fix]] </li>
<li> The next step depends on whether the '''launch.json''' file exists or not:
<ul>
<li> If there is no '''launch.json''' file, the '''Select environment''' dropdown is displayed. Choose '''VMS JVM Debugger'''.</li>
<li> If the '''launch.json''' file exist, click '''Add Configuration''' button in the bottom-right corner of the VS Code and select '''VMS IDE: Launch JVM'''.</li>
</ul>
<li> Edit the ''launch.json'' file
<pre>
{
"type": "vms jvm debugger",
"request": "launch",
"name": "Launch JVM",
"classpath": "${command:FillClassPath}",
"class": "${command:FillClassName}",
"port": "5005-5105",
"arguments": "",
"stopOnEntry": true
}
</pre>
* Do not change '''type''' and '''request'''
* Specify the '''name'''
* Set the class path - ''A colon-separated list of directories, JAR archives, and ZIP archives where to search for class files in''. In case of "${command:FillClassPath}" class path will be taken from project settings.
* Enter full class name with the static '''main''' method. In case of "${command:FillClassName}" the 'select executable class' QuickPick will be displayed when debugging is started.
* '''port''' is range of ports for JDB.
* '''arguments''' is a string with arguments passed to the program.
* '''stopOnEntry''' indicates whether do stop or not on the program entry.
</li>f
</ol>

=== Breakpoints ===
Breakpoints are shown grayed until the corresponding class is loaded into memory. Also, they are grayed if no Java class information collected.

==== Function breakpoints ====
To add a function breakpoint:
# Click '+' in the Breakpoints view.
# Enter the function name using ''<full_class_path>.<method>(<arg_type1>, <arg_type2>...)'' format. You can omit any part of the function name. QuickPick popup with available functions will appear. Then select the required one.
# If no dialog appears, click '''Activate Breakpoints'''.

==== Data breakpoints ====
There is no specific UI for data breakpoints.

To create a data breakpoint, type '''watch all <class>.<field>''' in the debugging console input while the program is paused.
To remove data breakpoints, type '''unwatch all <class>.<field>'''.

'''Note:''' This feature does not catch the changing of particular variables. It catches all changes to the <field> of all instances of <class>. Also, it does not work for local variables.

=== Displaying/Setting variables ===
A string variable is displayed ''as is'', without escaping. 
Char variable is escaped if its value is less than 0x20 or greater than 0x7f. 
To set the value of a string or char variable, you can write an escaped string (using Java rules). Enclosing quotes are not required.

=== Debugging console ===
When a program is running, anything that you type to the debugging console is sent to the program.
When a program is paused, anything that you type to the debugging console is sent to the debugger.

Note this to avoid issues with breaking the debugger. For example, 'eval a=100' will change the value of variable ''a'' and this will not be caught by the extension.

[[Category: VMS IDE]]

VMS IDE for Java (Kotlin, Scala)

2019-09-01T20:55:05Z

Andrey.logachev:

'''Note: support for JVM based languages (Java, Kotlin, Scala) will be available soon'''

== Working on a Java, Kotlin or Scala project ==

=== Creating and building a project ===
The general development process includes the following steps:
# Change project settings:
#* '''project type''' - specify ''java'', ''scala'' or ''kotlin''
#* '''project name'''
#* '''root folder'''
#* '''source''', '''headers''', '''resource''', and '''listing''' masks
# Write code
# Create MMS
# Upload source files
# Build the project
# Collect Java classes. This step is required for debugging.
# Run the project

=== Restrictions ===
Because the project target is compiled by one command for all source files, do not mix Kotlin, Scala, and Java source files in one project.

=== Abilities ===
A Java, Scala or Kotlin project may depend on other Java, Scala or Kotlin projects.

== Debugging ==

=== Before starting debug ===
To be able to use breakpoints during debugging, run '''Collect Java classes''' after editing and building the project.

=== Running VMS JVM Debugger ===
<ol>
<li> To start Debugger, press <code>F5</code>. If no debug configuration is selected, the ''Select environment'' dropdown will be shown. [[File:Jvm-dbg-select.png|dbg-select]]</li>
<li> Choose '''VMS JVM Debugger'''. If all java classes are collected successfully, the ''entry class'' quickpick popup will be shown. [[File:Jvm-dbg-select-main.png|select-main]]</li>
<li> Select one and debugging will start. </li>
</ol>

=== Creating Debug Configurations ===
You can configure 'launch.json' to start predefined debug configuration. To do this,
<ol>
<li> Click 'Configure or Fix...' button on the DEBUG panel. 
[[File:Jvm-dbg-configure-or-fix.png|dbg-configure-or-fix]] </li>
<li> The next step depends on the '''launch.json''' file existance:
<ul>
<li> If there is no '''launch.json''' file, the '''Select environment''' dropdown is displayed. Choose '''VMS JVM Debugger'''.</li>
<li> If the '''launch.json''' file exist, click '''Add Configuration''' button in the bottom-right corner of the VS Code and select '''VMS IDE: Launch JVM'''.</li>
</ul>
<li> Edit the ''launch.json'' file
<pre>
{
"type": "vms jvm debugger",
"request": "launch",
"name": "Launch JVM",
"classpath": "${command:FillClassPath}",
"class": "${command:FillClassName}",
"port": "5005-5105",
"arguments": "",
"stopOnEntry": true
}
</pre>
* Do not change '''type''' and '''request'''
* Specify the '''name'''
* Set the class path - ''A colon-separated list of directories, JAR archives, and ZIP archives where to search for class files in''. In case of "${command:FillClassPath}" class path will be taken from project settings.
* Enter full class name with the static '''main''' method. In case of "${command:FillClassName}" the 'select executable class' quickpick will be displayed when debugging is started.
* '''port''' is range of ports for JDB.
* '''arguments''' is a string with arguments passed to the program.
* '''stopOnEntry''' indicates whether do stop or not on the program entry.
</li>
</ol>

=== Breakpoints ===
Breakpoints are shown grayed until the corresponding class is loaded into memory. Also, they are grayed if no Java class information collected.

==== Function breakpoints ====
To add a function breakpoint:
# Click '+' in the Breakpoints view.
# Enter the function name using ''<full_class_path>.<method>(<arg_type1>, <arg_type2>...)'' format. You can omit any part of the function name. QuickPick popup with available functions will appear. Then select the required one.
# If no dialog appears, click '''Activate Breakpoints'''.

==== Data breakpoints ====
There is no specific UI for data breakpoints.

To create a data breakpoint, type '''watch all <class>.<field>''' in the debugging console input while the program is paused.
To remove data breakpoints, type '''unwatch all <class>.<field>'''.

'''Note:''' This feature does not catch the changing of particular variables. It catches all changes to the <field> of all instances of <class>. Also, it does not work for local variables.

=== Displaying/Setting variables ===
A string variable is displayed ''as is'', without escaping. 
Char variable is escaped if its value is less than 0x20 or greater than 0x7f. 
To set the value of a string or char variable, you can write an escaped string (using Java rules). Enclosing quotes are not required.

=== Debugging console ===
When a program is running, anything that you type to the debugging console is sent to the program.
When a program is paused, anything that you type to the debugging console is sent to the debugger.

Note this to avoid issues with breaking the debugger. For example 'eval a=100' will change the value of variable ''a'' and this will not be caught by the extension.

[[Category: VMS IDE]]

VMS IDE Project Explorer

2019-09-01T20:22:24Z

Andrey.logachev:

The '''Project Explorer''' view helps to manage OpenVMS projects, their dependencies, and settings. It is also possible to build, rebuild, and clean the project using the '''Project Explorer''' context menu.

=Description=
{| style="border-style: none;"
|-
|rowspan="2"| [[File:Project-explorer.PNG|frame|left|Project Explorer]]
|style="vertical-align:top; padding-left: 20px;" |
==Project Dependencies==

====Project types====
* ''executable'' - executable image is created
* ''library'' - object library (OLB) is created
* ''shareable'' - shareable image is created
* ''java'' - project contains only Java files
* ''kotlin'' - project contains only Kotlin files
* ''scala'' - project contains only Scala files

====Context Menu====
* '''Add to dependencies of selected''' - add the project you right-clicked to the previously selected project as a dependency
* '''Remove project from dependencies''' - remove the selected project from dependencies of the main project
* '''Build only this project''' - build the current project
* '''Build with dependencies''' - build the current project and all its dependencies
* '''Clean this only''' - clean current project only
* '''Rebuild only this project''' - rebuild the current project
* '''Rebuild with dependencies''' - rebuild the current project and all its dependencies

====Creating MMS Files====
'''VMS IDE''' can create '''MMS''' files automatically based on the project type and the types of its dependencies. 
For ''shareable'' images, an options ('''OPT''') file is created, but the universal symbol vector must be edited manually. 
If the project depends on some shareable images, a '''COM''' file is created with ''logicals'' required for running the project.

==Project Description==
When a project is selected in the Project Dependencies panel, its description is shown.
* '''Local'''
** ''folder'' - [[VMS IDE Project Configuration|Workspace folder name]]
** ''buildName'' - currently selected [[Build Configurations|build configuration]] (right-click and select '''Change''' to choose another one)
** ''sourceState'' - current state of source files
*** ''unknown'' - no synchronization or upload was performed or there were changes to the Project or SSH settings
*** ''modified'' - there are changes that need to be synchronized
*** ''synchronized'' - project files on the local machine and OpenVMS are synchronized
** ''buildState'' - current state of the build (''Built'' or ''Not built''). State is linked to the build configuration.
** ''masters'' - projects which depend on the currently selected project
* '''SSH'''
** ''host'' - OpenVMS host to synchronize and build with
* '''Project'''
** ''projectName'' - the name of the project
** ''projectType'' - [[#Project types|the type of the project]]
** ''root'' - project root on OpenVMS
|}

[[Category:VMS IDE]]

Project Settings

2019-09-01T19:13:47Z

Andrey.logachev:

=Project Configuration Example=
<pre>
{
"project": {
"break": "C",
"builders": "*.{mms,com}",
"exclude": "**/{node_modules,.vscode}/**",
"headers": "*.h",
"listing": "*.lis",
"outdir": "out",
"projectName": "project",
"projectType": "executable",
"resource": "**/resource/**",
"root": "project",
"source": "*.{cpp,c}",
"addLibraries": "sys$library:IMAGELIB.OLB,sys$library:RDBMSGS.OLB",
"addIncludes": "sys$library"
}
}
</pre>

=Project Settings Description=
* <code>'''Break'''</code> - Keyboard key to pause debugging in VMS IDE debugger. The extension uses combination <code>CTRL+Key</code> to pause debugging when user press '''Pause''' or <code>F6</code>.
* <code>'''Builders'''</code> - Mask for files used for building the project. Default is "*.{mms,com}".
* <code>'''Exclude'''</code> - Folders excluded from synchronization with OpenVMS system.
* <code>'''Headers'''</code> - Header files. Default is "*.{h,hpp}".
* <code>'''Listing'''</code> - Listing files that will be downloaded after the project is built for debugging purpose.
* <code>'''Outdir'''</code> - Output directory where object, listing and executable files will be stored when built. Is also used for temporary files. '''NOTE''': Should be only the name of the folder, not a full or relative path.
* <code>'''Project Name'''</code> - Name for the executable file, auto-generated '''MMS''' file for builder, OPT file for linker, and COM file for defining logical names. '''NOTE''': Use one word only; do not use spaces or special characters.
* <code>'''Project Type'''</code> - Type of the project. '''Note:''' the building method depends on the type of the project and its dependencies. Available types:
** '''executable''', '''library''' or '''shareable''' for classic languages;
** '''java''', '''kotlin''' or '''scala''' for JVM based projects.
* <code>'''Resource'''</code> - Files required for the project, but are not involved in the build process.
* <code>'''Root'''</code> - Directory of the project on the remote OpenVMS machine in UNIX format relative to the home folder.
* <code>'''Source'''</code> - Mask for the source files, e.g. "*.{c,cpp}".
* <code>'''Additional libraries'''</code> - list of libraries in ODS-5 format, separated by commas.
* <code>'''Additional include folders'''</code> - list of folders in ODS-5 format, separated by commas.

=Adjusting Project Settings=
# Set the <code>'''Root'''</code> directory. For example, if the project is located in '''WORK:[USER.DEMOS.SIMPLE]''' and the home directory is '''WORK:[USER]''', set the parameter value to '''demos/simple'''.
# Select the <code>'''Project Type'''</code> that you need.
# Specify the <code>'''Project Name'''</code>. '''NOTE''': do not use spaces or special characters.
# Check <code>'''Builders'''</code>. These files will be synchronized.
# Check <code>'''Headers'''</code>. These files will be synchronized and included into the [[Auto-generating MMS|auto-generated MMS]] file as header files. Changing any of them will result in full project rebuild.
# Check <code>'''Source'''</code>. These files will be synchronized and included into the [[Auto-generating MMS|auto-generated MMS]] file as source files.
# Check <code>'''Resource'''</code>. These files will be synchronized but not included into the [[Auto-generating MMS|auto-generated MMS]] file.
# Adjust the <code>'''Exclude'''</code> field value to list the files similar to the described above but not to be synchronized and compiled.
# Check <code>'''Listing'''</code>. These files will be downloaded after building the project. Files "*.lis,*.map" are required for debugger.
# If the project depends on already installed libraries, specify the in the <code>'''Additional libraries'''</code> and <code>'''Additional include folders'''</code>

[[Category:VMS IDE]]

Pascal syntax highlighting

2019-09-01T19:08:57Z

Andrey.logachev:

VMS IDE supports syntax highlighting for Pascal.

{| style="border-style: none;"
|-
|rowspan="1"| [[File:Pascal-syntax-1.png|Pascal-syntax-example|frame|left]] [[File:Pascal-syntax-2.png|frame|left|Syntax check]]
|style="vertical-align:top; padding-left: 20px;" |

'''Features'''
* Dynamic syntax check
* Symbol source in a popup
* Jump to symbol definition (<code>F12</code>)
* [https://code.visualstudio.com/docs/editor/editingevolved#_peek Peek] definition (<code>Alt-F12</code>)
* Find all references (<code>Shift-Alt-F12</code>)
* Rename symbol (<code>F2</code>)
|}

[[Category: VMS IDE]]

VMS IDE

2019-08-21T14:08:10Z

Andrey.logachev:

'''VMS IDE''' is an integrated development environment that enables you to quickly and easily develop comprehensive applications for OpenVMS system. It provides a set of tools for developing, building, and debugging OpenVMS projects.

=Features=
[[File:Vms ide.png|800px|thumb|none|VMS IDE]]
* Source code '''synchronization''' between the local machine and OpenVMS system.
* '''SSH connection''' setup to the remote OpenVMS system.
* '''Projects Explorer''' as a simple and convenient way to manage OpenVMS projects.
* '''Debugger''' for OpenVMS projects.
* '''Syntax highlighting''' for '''MMS''', '''CLD''', and '''MSG''' files.
* '''Code auto-completion''' for '''MSG''' and '''CLD''' files.
* Supported languages: '''C''', '''C++''', '''Fortran''', '''Cobol''', '''Pascal''', '''Basic''', '''Bliss'''.

=Restrictions=
* The '''VMS IDE''' extension can only be used in conjunction with ODS-5 OpenVMS file systems; it cannot be used with ODS-2 file systems.
* Do not use the minus sign ("-") in file names. This may prevent the debugger from finding the source file.

=Getting Started=
This guide will help you install the VMS IDE extension and start working on your projects.

===Quick Start===
* [[VMS_IDE_Installation|Installing VMS IDE]]
* [[VMS_IDE_Project_Configuration|Setting up a VMS Project]]
* [[VMS_IDE_Developing|Working on a VMS Project]]

===Settings===
* [[Project Settings]]
* [[SSH Settings]]
* [[Synchronize Configuration|Synchronize Settings]]
* [[Build Configurations]]

===Commands===
* [[VMS_IDE_Commands|VMS IDE Commands]]

===Components===
* [[VMS_IDE_Project_Explorer|Project Explorer]]
* [[VMS_IDE_Debugger|Debugger]]

=Changelog=
[[VMS IDE Change Log]]

[[Category:VMS IDE]]

Synchronize Configuration

2019-08-21T14:00:14Z

Andrey.logachev:

=Synchronize Configuration Example=
<pre>
{
"synchronize": {
"downloadNewFiles": "edit",
"keepAlive": false,
"preferZip": false,
"forceLocalTime": true,
"purge": false,
"setTimeAttempts": 3,
"setTimeByShell": true,
"unzipCmd": ""
}
}
</pre>

=Settings Description=
* <code>'''downloadNewFiles'''</code> - Strategy for downloading remote files which are newer than local copies.
** '''overwrite''' - remote files will overwrite local files.
** '''skip''' - remote files will not be downloaded but an appropriate warning message will be shown.
** '''edit''' - remote files will be downloaded into memory and the edit-merge window will be opened to allow the user decide what changes to save.
* <code>'''keepAlive'''</code> - Shell and SFTP connections will not be closed after synchronization is done and will be reused for the next synchronization.
* <code>'''preferZip'''</code> - Prefer ZIP for uploading source files.
* <code>'''forceLocalTime'''</code> - Set local time instead of UTC for archived files. Used when synchronizing via ZIP.
* <code>'''purge'''</code> - Execute <code>PURGE</code> command after uploading source.
* <code>'''setTimeAttempts'''</code> - The maximum number of attempts to set file time. '''NOTE''': the first attempt to set file time may be rejected because the file is busy. VMS IDE will re-try to set time again.
* <code>'''setTimeByShell'''</code> - If the SFTP server on the OpenVMS host did not set the file time, VMS IDE can use DCL commands to do this.
* <code>'''unzipCmd'''</code> - Is used to run a user-defined command to unzip archive on the remote side; default is <code>unzip -oo "-D"</code> and file name added at the end of the command.

If you have the full project on OpenVMS and want to download it to your local machine, set <code>'''downloadNewFiles'''</code> to '''overwrite'''. 
If you have the full project on your local machine and use OpenVMS only for compiling and debugging, set <code>'''downloadNewFiles'''</code> to '''skip'''. 
If the project on OpenVMS can be changed outside and may be newer than the local copy, set <code>'''downloadNewFiles'''</code> to '''edit'''. 

[[Category:VMS IDE]]

SSH Settings

2019-08-21T13:54:37Z

Andrey.logachev: /* Terminal */

An SSH connection to an OpenVMS machine is required for syncing source code files, building, running, and debugging projects. 
Depending on the type of configuration, SSH connection settings can be edited either in the '''vmssoftware.ssh-helper-settings.json''' file located in ''/.vscode'' directory or via '''Visual Studio Code''' settings page.

=SSH Settings Template=
<pre>
{
"connection": {
"host": "",
"keyFile": "",
"password": "",
"port": 22,
"username": "",
"skipSignatureVerification": false,
},
"host-collection": {
"hosts": []
},
"timeouts": {
"cmdTimeout": 0,
"feedbackTimeout": 0,
"welcomeTimeout": 0
},
"terminal": {
"command": "ssh -oHostKeyAlgorithms=+ssh-dss ${keyFile?-i ${keyFile}} ${username?${username}@}${host}"
}
}
</pre>

=Connection=
The '''connection''' section sets the current connection details.
* <code>'''host'''</code> - IP-address or name of an OpenVMS machine or the label of a predefined connection from the '''host collection''' section
case, all other fields are ignored.
* <code>'''port'''</code> - The port number to use for the SSH connection. Default is 22.
* <code>'''username'''</code> - User account that will be used for the SSH connection.
* <code>'''password'''</code> - User password that will be used for the SSH connection.. If it is omitted a password input box will be shown on connection attempt.
* <code>'''keyFile'''</code> - Path to SSH private key file. For details on how to configure connection using SSH key, see [https://raymii.org/s/blog/SSH_public_key_authentication_on_OpenVMS.html SSH public key authentication on OpenVMS]
* <code>'''skipSignatureVerification'''</code> - Skip signature verification. Set it to 'true' if an error 'Handshake failed: signature verification failed' occurs.

Required fields are:
* <code>'''host'''</code>
* <code>'''username'''</code>

You may use either password or key file to establish connection:
* <code>'''keyFile'''</code>
* <code>'''password'''</code>

If '''keyFile''' is not set, '''password''' is used. If neither '''password''' nor '''keyFile''' is specified, you will be prompted to enter your password during the connection attempt.

=Host Collection=
If you need to connect to different servers when working on your project, it makes sense to create a list of required connections to be able to quickly connect to any of them.
You can do this by adding all the required connections to the '''Host Collection''' list.

=== Adding a new host to collection ===
To add a new host to the collection:
<ol>
<li>Copy the ssh connection template to '''host-collection.hosts''' array:</li>
<pre>"host-collection": {
"hosts": [
{
"host": "<First>",
"keyFile": "",
"password": "",
"port": 22,
"username": "",
"skipSignatureVerification": false
}
]
}</pre>
<li>Specify connection parameters</li>
<li>Make sure that '''label''' parameter is set.</li>
</ol>

===Selecting which connection to use===
To use one of connections from the '''host collection''' section, copy the value of ''label'' and paste it in angle brackets ('''<label>''') to the '''host''' field in the '''connection''' section.

=== Example ===
<pre>
{
"connection": {
"host": "<MySSHConnection>",
"keyFile": "",
"password": "",
"port": 22,
"username": "",
"skipSignatureVerification": false
},
"host-collection": {
"hosts": [
{
"host": "10.10.6.1",
"keyFile": "",
"password": "myPassword",
"port": 22,
"username": "user",
"skipSignatureVerification": true,
"label": "MySSHConnection"
}
]
}
}
</pre>

'''NOTE''': If you use VSC type of configuration, you will not be able to specify host collection in UI. Instead, you need to click "Edit in settings.json" and specify them in the '''settings.json''' file.

[[File:Ssh collection hosts.png|Ssh collection hosts.png]]

=Timeouts=
You can define SSH connection timeouts in this section.
* <code>'''cmdTimeout'''</code> - Timeout for command response. If a command is sent to the OpenVMS system and the OpenVMS system does not a send response for the specified period of time, it will be considered as rejected.
* <code>'''feedbackTimeout'''</code> - If the SSH connection does not send feedback for the specified interval, the password will be considered as invalid.
* <code>'''welcomeTimeout'''</code> - If the SSH shell prompt is not received within this interval, the shell will be closed.

'''NOTE''': Value "0" means, that timeout is not used.

'''WARN''': Do not change timeout settings unless necessary.

===Example===
<pre>
"timeouts": {
"cmdTimeout": 0,
"feedbackTimeout": 0,
"welcomeTimeout": 0
}
</pre>

=Terminal=
Specifies command to start the shell in the VS Code integrated terminal.
* <code>'''Command'''</code> - command to start the shell.

'''NOTE:''' It is possible to use variables in the command. The syntax is: <code>${variable}</code> or <code>${varable?<text if variable isn't empty>}</code>. Supported variables: '''host''', '''port''', '''username''', '''password''', and '''keyFile'''.
'''NOTE:''' password may come from settings or UI prompt that is shown if the password is not specified in settings. Passwords entered in the terminal are not saved.

===Example===
<pre>
"terminal": {
"command": "ssh -oHostKeyAlgorithms=+ssh-dss ${keyFile?-i ${keyFile}} ${username?${username}@}${host}"
}
</pre>

[[Category:VMS IDE]]

SSH Settings

2019-08-21T13:53:38Z

Andrey.logachev:

An SSH connection to an OpenVMS machine is required for syncing source code files, building, running, and debugging projects. 
Depending on the type of configuration, SSH connection settings can be edited either in the '''vmssoftware.ssh-helper-settings.json''' file located in ''/.vscode'' directory or via '''Visual Studio Code''' settings page.

=SSH Settings Template=
<pre>
{
"connection": {
"host": "",
"keyFile": "",
"password": "",
"port": 22,
"username": "",
"skipSignatureVerification": false,
},
"host-collection": {
"hosts": []
},
"timeouts": {
"cmdTimeout": 0,
"feedbackTimeout": 0,
"welcomeTimeout": 0
},
"terminal": {
"command": "ssh -oHostKeyAlgorithms=+ssh-dss ${keyFile?-i ${keyFile}} ${username?${username}@}${host}"
}
}
</pre>

=Connection=
The '''connection''' section sets the current connection details.
* <code>'''host'''</code> - IP-address or name of an OpenVMS machine or the label of a predefined connection from the '''host collection''' section
case, all other fields are ignored.
* <code>'''port'''</code> - The port number to use for the SSH connection. Default is 22.
* <code>'''username'''</code> - User account that will be used for the SSH connection.
* <code>'''password'''</code> - User password that will be used for the SSH connection.. If it is omitted a password input box will be shown on connection attempt.
* <code>'''keyFile'''</code> - Path to SSH private key file. For details on how to configure connection using SSH key, see [https://raymii.org/s/blog/SSH_public_key_authentication_on_OpenVMS.html SSH public key authentication on OpenVMS]
* <code>'''skipSignatureVerification'''</code> - Skip signature verification. Set it to 'true' if an error 'Handshake failed: signature verification failed' occurs.

Required fields are:
* <code>'''host'''</code>
* <code>'''username'''</code>

You may use either password or key file to establish connection:
* <code>'''keyFile'''</code>
* <code>'''password'''</code>

If '''keyFile''' is not set, '''password''' is used. If neither '''password''' nor '''keyFile''' is specified, you will be prompted to enter your password during the connection attempt.

=Host Collection=
If you need to connect to different servers when working on your project, it makes sense to create a list of required connections to be able to quickly connect to any of them.
You can do this by adding all the required connections to the '''Host Collection''' list.

=== Adding a new host to collection ===
To add a new host to the collection:
<ol>
<li>Copy the ssh connection template to '''host-collection.hosts''' array:</li>
<pre>"host-collection": {
"hosts": [
{
"host": "<First>",
"keyFile": "",
"password": "",
"port": 22,
"username": "",
"skipSignatureVerification": false
}
]
}</pre>
<li>Specify connection parameters</li>
<li>Make sure that '''label''' parameter is set.</li>
</ol>

===Selecting which connection to use===
To use one of connections from the '''host collection''' section, copy the value of ''label'' and paste it in angle brackets ('''<label>''') to the '''host''' field in the '''connection''' section.

=== Example ===
<pre>
{
"connection": {
"host": "<MySSHConnection>",
"keyFile": "",
"password": "",
"port": 22,
"username": "",
"skipSignatureVerification": false
},
"host-collection": {
"hosts": [
{
"host": "10.10.6.1",
"keyFile": "",
"password": "myPassword",
"port": 22,
"username": "user",
"skipSignatureVerification": true,
"label": "MySSHConnection"
}
]
}
}
</pre>

'''NOTE''': If you use VSC type of configuration, you will not be able to specify host collection in UI. Instead, you need to click "Edit in settings.json" and specify them in the '''settings.json''' file.

[[File:Ssh collection hosts.png|Ssh collection hosts.png]]

=Timeouts=
You can define SSH connection timeouts in this section.
* <code>'''cmdTimeout'''</code> - Timeout for command response. If a command is sent to the OpenVMS system and the OpenVMS system does not a send response for the specified period of time, it will be considered as rejected.
* <code>'''feedbackTimeout'''</code> - If the SSH connection does not send feedback for the specified interval, the password will be considered as invalid.
* <code>'''welcomeTimeout'''</code> - If the SSH shell prompt is not received within this interval, the shell will be closed.

'''NOTE''': Value "0" means, that timeout is not used.

'''WARN''': Do not change timeout settings unless necessary.

===Example===
<pre>
"timeouts": {
"cmdTimeout": 0,
"feedbackTimeout": 0,
"welcomeTimeout": 0
}
</pre>

=Terminal=
Specifies command to start the shell in the VS Code integrated terminal.
* <code>'''Command'''</code> - command to start the shell.

'''NOTE:''' It is possible to use variables in the command. The syntax is: ${variable} or ${varable?<text if variable isn't empty>}. Supported variables: '''host''', '''port''', '''username''', '''password''', and '''keyFile'''.
'''NOTE:''' password may come from settings or UI prompt that is shown if the password is not specified in settings. Passwords entered in the terminal are not saved.

===Example===
<pre>
"terminal": {
"command": "ssh -oHostKeyAlgorithms=+ssh-dss ${keyFile?-i ${keyFile}} ${username?${username}@}${host}"
}
</pre>

[[Category:VMS IDE]]

Build Configurations

2019-08-20T10:40:14Z

Andrey.logachev:

A project build configuration defines how the project should be built. You can have multiple build configurations for a project so that you can build the same code for different purposes. 
By default, there are two build configurations:
* '''DEBUG''', which is necessary for debugging
* '''RELEASE''', which produces binaries for your project deployment.
If necessary, you can add custom build configurations for your project.

== Working with build configurations ==
=== Editing build configurations ===
You can edit the list of build configurations the same way you edit the project settings:
# Press ''F1'' and run the ''VMS-IDE: Edit VMS project settings'' command or use the [[VMS_IDE_Project_Explorer|Project Explorer]] view
# Find the ''builds'' section
# Make the required changes

=== Changing current build configuration ===
To change the current build configuration:
# Open the [[VMS_IDE_Project_Explorer|Project Explorer]] view
# In the ''PROJECT DESCRIPTION'' section, right-click the ''buildName'' parameter, then select ''Change''
# In the popup list select the required configuration.

== Build configuration parameters ==
Each build configuration includes the following parameters:
* '''label''' - unique name of the build configuration. Note: the label is also used as the name of the output folder.
* '''description''' - description of the build configuration
* '''command''' - command (MMS or COM file) to build or clean the project
* '''parameter''' - parameter to pass over to the command

=== Default build configuration ===
If the command is empty, the default [[Auto-generating MMS|auto-created MMS]] file is used to build the project. The '''parameter''' value is used to specify the type of the build: ''DEBUG'' or ''RELEASE''.

=== Custom build configurations ===
If the user defined command is an '''MMS''' file, it is processed via "MMS/EXTENDED_SYNTAX/DESCR=<MMS file> ''parameter''" command. The ''parameter'' value is treated as a target. 

If the user defined command is a '''COM''' file, it is executed with "@<COM file> ''parameter''" command.

'''NOTE:''' It is recommended that the user-defined build procedure creates resulting files in '''<project root>/<output folder>/<build label>''' directory.

=== Example ===
<pre>
"builds": {
"configurations": [
{
"label": "DEBUG",
"description": "DEBUG",
"command": "",
"parameter": "DEBUG"
},
{
"label": "RELEASE",
"description": "RELEASE",
"command": "",
"parameter": "RELEASE"
},
{
"label": "myOwnRelease",
"description": "My own build release",
"command": "executable.mms",
"parameter": ""
},
{
"label": "myOwnDebug",
"description": "My own build debug",
"command": "build.com",
"parameter": "DEBUG"
}
]
}
</pre>

[[Category:VMS IDE]]

Auto-generated MMS

2019-08-20T10:30:15Z

Andrey.logachev:

The default MMS file generated by <code>VMS-IDE: Create MMS</code> command includes the following operations:
# Collect the list of header files
# Collect the list of source files
# Add header files list as '''INCLUDES'''
# Add source files list as '''SOURCES'''
# Define the main target depending on the project type
# Define object dependencies

'''NOTE''': For some languages the compilation order is important. To change the order in which objects are compiled, reorder the object files in the main target definition.

'''NOTE:''' Variables '''DEBUG''', '''OUTDIR''' and '''CONFIG''' will be defined by the VMS IDE extension during compilation.

==Example==
<pre>
! header !auto
! Do not modify this file. It may be overwritten automatically. !auto
! includes !auto
INCLUDES= !auto
! sources !auto
SOURCES= - !auto
myprog.cob !auto
! dependencies !auto
.FIRST !auto
!auto
! compiler/linker options !auto
.IF DEBUG !auto
COMPILEFLAGS = /DEBUG/NOOP/LIST=$(MMS$TARGET_NAME)/OBJECT=$(MMS$TARGET) !auto
LINKFLAGS = /DEBUG/MAP=$(MMS$TARGET_NAME)/EXECUTABLE=$(MMS$TARGET) !auto
.ELSE !auto
COMPILEFLAGS = /OBJECT=$(MMS$TARGET) !auto
LINKFLAGS = /EXECUTABLE=$(MMS$TARGET) !auto
.ENDIF !auto
! directives !auto
.SILENT !auto
OUT_DIR = .$(OUTDIR).$(CONFIG) !auto
OBJ_DIR = $(OUT_DIR).obj !auto
.SUFFIXES !auto
.SUFFIXES .OBJ .CPP .C .CLD .MSG .BLI .COB .PAS .BAS .F77 .F90 .FOR .B32 .CBL !auto
.CPP.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
$(CXX) $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.C.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
$(CC) $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.CLD.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
SET COMMAND/OBJECT=$(MMS$TARGET) $(MMS$SOURCE) !auto
!auto
.MSG.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
MESSAGE /OBJECT=$(MMS$TARGET) $(MMS$SOURCE) !auto
!auto
.BLI.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
BLISS $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.B32.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
BLISS $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.COB.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
COBOL $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.CBL.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
COBOL $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.PAS.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
PASCAL $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.BAS.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
BASIC $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.F77.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
FORTRAN $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.F90.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
FORTRAN $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.FOR.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
FORTRAN $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.DEFAULT !auto
! Source $(MMS$TARGET) not yet added !auto
!auto
! main target !auto
[$(OUT_DIR)]$(NAME).EXE : - !auto
[$(OBJ_DIR)]myprog.obj !auto
CXXLINK $(LINKFLAGS) $(MMS$SOURCE_LIST) !auto
!auto
! objects !auto
[$(OBJ_DIR)]myprog.obj : myprog.cob $(INCLUDES) !auto

</pre>

[[Category: VMS IDE]]

VMS IDE Project Explorer

2019-08-18T15:47:55Z

Andrey.logachev: /* Description */

The '''Project Explorer''' view helps to manage OpenVMS projects, their dependencies, and settings. It is also possible to build, rebuild, and clean the project using the '''Project Explorer''' context menu.

=Description=
{| style="border-style: none;"
|-
|rowspan="2"| [[File:Project-explorer.PNG|frame|left|Project Explorer]]
|style="vertical-align:top; padding-left: 20px;" |
==Project Dependencies==

====Project types====
* ''executable'' - executable image is created
* ''library'' - object library (OLB) is created
* ''shareable'' - shareable image is created

====Context Menu====
* '''Add to dependencies of selected''' - add the project you right-clicked to the previously selected project as a dependency
* '''Remove project from dependencies''' - remove the selected project from dependencies of the main project
* '''Build only this project''' - build the current project
* '''Build with dependencies''' - build the current project and all its dependencies
* '''Clean this only''' - clean current project only
* '''Rebuild only this project''' - rebuild the current project
* '''Rebuild with dependencies''' - rebuild the current project and all its dependencies

====Creating MMS Files====
'''VMS IDE''' can create '''MMS''' files automatically based on the project type and the types of its dependencies. 
For ''shareable'' images, an options ('''OPT''') file is created, but the universal symbol vector must be edited manually. 
If the project depends on some shareable images, a '''COM''' file is created with ''logicals'' required for running the project.

==Project Description==
When a project is selected in the Project Dependencies panel, its description is shown.
* '''Local'''
** ''folder'' - [[VMS IDE Project Configuration|Workspace folder name]]
** ''buildName'' - currently selected [[Build Configurations|build configuration]] (right-click and select '''Change''' to choose another one)
** ''sourceState'' - current state of source files
*** ''unknown'' - no synchronization or upload was performed or there were changes to the Project or SSH settings
*** ''modified'' - there are changes that need to be synchronized
*** ''synchronized'' - project files on the local machine and OpenVMS are synchronized
** ''buildState'' - current state of the build (''Built'' or ''Not built''). State is linked to the build configuration.
** ''masters'' - projects which depend on the currently selected project
* '''SSH'''
** ''host'' - OpenVMS host to synchronize and build with
* '''Project'''
** ''projectName'' - the name of the project
** ''projectType'' - [[#Project types|the type of the project]]
** ''root'' - project root on OpenVMS
|}

[[Category:VMS IDE]]

VMS IDE

2019-08-18T15:40:24Z

Andrey.logachev: /* Quick Start */

'''VMS IDE''' is an integrated development environment that enables you to quickly and easily develop comprehensive applications for OpenVMS system. It provides a set of tools for developing, building, and debugging OpenVMS projects.

=Features=
[[File:Vms ide.png|800px|thumb|none|VMS IDE]]
* Source code '''synchronization''' between the local machine and OpenVMS system.
* '''SSH connection''' setup to the remote OpenVMS system.
* '''Projects Explorer''' as a simple and convenient way to manage OpenVMS projects.
* '''Debugger''' for OpenVMS projects.
* '''Syntax highlighting''' for '''MMS''', '''CLD''', and '''MSG''' files.
* '''Code auto-completion''' for '''MSG''' and '''CLD''' files.
* Supported languages: '''C''', '''C++''', '''Fortran''', '''Cobol''', '''Pascal''', '''Basic''', '''Bliss'''.

=Restrictions=
* The '''VMS IDE''' extension can only be used in conjunction with ODS-5 OpenVMS file systems; it cannot be used with ODS-2 file systems.
* Do not use the minus sign ("-") in file names. This may prevent the debugger from finding the source file.

=Getting Started=
This guide will help you install the VMS IDE extension and start working on your projects.

===Quick Start===
* [[VMS_IDE_Installation|Installing VMS IDE]]
* [[VMS_IDE_Project_Configuration|Setting up a VMS Project]]
* [[VMS_IDE_Developing|Working on a VMS Project]]

===Commands===
* [[VMS_IDE_Commands|VMS IDE Commands]]

===Components===
* [[VMS_IDE_Project_Explorer|Project Explorer]]
* [[VMS_IDE_Debugger|Debugger]]

[[Category:VMS IDE]]

VMS IDE

2019-08-18T15:39:34Z

Andrey.logachev: /* Features */

'''VMS IDE''' is an integrated development environment that enables you to quickly and easily develop comprehensive applications for OpenVMS system. It provides a set of tools for developing, building, and debugging OpenVMS projects.

=Features=
[[File:Vms ide.png|800px|thumb|none|VMS IDE]]
* Source code '''synchronization''' between the local machine and OpenVMS system.
* '''SSH connection''' setup to the remote OpenVMS system.
* '''Projects Explorer''' as a simple and convenient way to manage OpenVMS projects.
* '''Debugger''' for OpenVMS projects.
* '''Syntax highlighting''' for '''MMS''', '''CLD''', and '''MSG''' files.
* '''Code auto-completion''' for '''MSG''' and '''CLD''' files.
* Supported languages: '''C''', '''C++''', '''Fortran''', '''Cobol''', '''Pascal''', '''Basic''', '''Bliss'''.

=Restrictions=
* The '''VMS IDE''' extension can only be used in conjunction with ODS-5 OpenVMS file systems; it cannot be used with ODS-2 file systems.
* Do not use the minus sign ("-") in file names. This may prevent the debugger from finding the source file.

=Getting Started=
This guide will help you install the VMS IDE extension and start working on your projects.

===Quick Start===
* [[VMS_IDE_Installation|Installation]]
* [[VMS_IDE_Project_Configuration|Setting up a VMS Project]]
* [[VMS_IDE_Developing|Working on a VMS Project]]

===Commands===
* [[VMS_IDE_Commands|VMS IDE Commands]]

===Components===
* [[VMS_IDE_Project_Explorer|Project Explorer]]
* [[VMS_IDE_Debugger|Debugger]]

[[Category:VMS IDE]]

Build Configurations

2019-08-18T15:34:23Z

Andrey.logachev: /* Important notes */

A project build configuration defines how the project should be built. You can have multiple build configurations for a project so that you can build the same code for different purposes. 
By default, there are two build configurations:
* '''DEBUG''', which is necessary for debugging
* '''RELEASE''', which produces binaries for your project deployment.
If necessary, you can add custom build configurations for your project.

== Working with build configurations ==
=== Editing build configurations ===
You can edit the list of build configurations the same way you edit the project settings:
# Press ''F1'' and run the ''VMS-IDE: Edit VMS project settings'' command or use the [[VMS_IDE_Project_Explorer|Project Explorer]] view
# Find the ''builds'' section
# Make the required changes

=== Changing current build configuration ===
To change the current build configuration:
# Open the [[VMS_IDE_Project_Explorer|Project Explorer]] view
# In the ''PROJECT DESCRIPTION'' section, right-click the ''buildName'' parameter, then select ''Change''
# In the popup list select the required configuration.

== Build configuration parameters ==
Each build configuration includes the following parameters:
* '''label''' - unique name of the build configuration. Note: the label is also used as the name of the output folder.
* '''description''' - description of the build configuration
* '''command''' - command (MMS or COM file) to build or clean the project
* '''parameter''' - parameter to pass over to the command

=== Default build configuration ===
If the command is empty, the default [[Auto-generating MMS|auto-created MMS]] file is used to build the project. The '''parameter''' value is used to specify the type of the build: ''DEBUG'' or ''RELEASE''.

=== Custom build configurations ===
If the user defined command is an '''MMS''' file, it is processed via "MMS/EXTENDED_SYNTAX/DESCR=<MMS file> ''parameter''" command. The ''parameter'' value is treated as a target. 

If the user defined command is a '''COM''' file, it is executed with "@<COM file> ''parameter''" command.

'''NOTE:''' It is recommended that the user-defined build procedure creates resulting files in '''<project root>/<output folder>/<build label>''' directory.

=== Important notes ===
'''NOTE:''' if you use the '''task2cmd''' to build your projects, use the build configuration label to set the task ''parameter'' value.

=== Example ===
<pre>
"builds": {
"configurations": [
{
"label": "DEBUG",
"description": "DEBUG",
"command": "",
"parameter": "DEBUG"
},
{
"label": "RELEASE",
"description": "RELEASE",
"command": "",
"parameter": "RELEASE"
},
{
"label": "myOwnRelease",
"description": "My own build release",
"command": "executable.mms",
"parameter": ""
},
{
"label": "myOwnDebug",
"description": "My own build debug",
"command": "build.com",
"parameter": "DEBUG"
}
]
}
</pre>

[[Category:VMS IDE]]

Build Configurations

2019-08-18T15:32:31Z

Andrey.logachev: /* Important notes */

A project build configuration defines how the project should be built. You can have multiple build configurations for a project so that you can build the same code for different purposes. 
By default, there are two build configurations:
* '''DEBUG''', which is necessary for debugging
* '''RELEASE''', which produces binaries for your project deployment.
If necessary, you can add custom build configurations for your project.

== Working with build configurations ==
=== Editing build configurations ===
You can edit the list of build configurations the same way you edit the project settings:
# Press ''F1'' and run the ''VMS-IDE: Edit VMS project settings'' command or use the [[VMS_IDE_Project_Explorer|Project Explorer]] view
# Find the ''builds'' section
# Make the required changes

=== Changing current build configuration ===
To change the current build configuration:
# Open the [[VMS_IDE_Project_Explorer|Project Explorer]] view
# In the ''PROJECT DESCRIPTION'' section, right-click the ''buildName'' parameter, then select ''Change''
# In the popup list select the required configuration.

== Build configuration parameters ==
Each build configuration includes the following parameters:
* '''label''' - unique name of the build configuration. Note: the label is also used as the name of the output folder.
* '''description''' - description of the build configuration
* '''command''' - command (MMS or COM file) to build or clean the project
* '''parameter''' - parameter to pass over to the command

=== Default build configuration ===
If the command is empty, the default [[Auto-generating MMS|auto-created MMS]] file is used to build the project. The '''parameter''' value is used to specify the type of the build: ''DEBUG'' or ''RELEASE''.

=== Custom build configurations ===
If the user defined command is an '''MMS''' file, it is processed via "MMS/EXTENDED_SYNTAX/DESCR=<MMS file> ''parameter''" command. The ''parameter'' value is treated as a target. 

If the user defined command is a '''COM''' file, it is executed with "@<COM file> ''parameter''" command.

'''NOTE:''' It is recommended that the user-defined build procedure creates resulting files in '''<project root>/<output folder>/<build label>''' directory.

=== Important notes ===
'''NOTE:''' when using the '''task2cmd''' to build your projects, use the build configuration label to set the task ''parameter'' value.

=== Example ===
<pre>
"builds": {
"configurations": [
{
"label": "DEBUG",
"description": "DEBUG",
"command": "",
"parameter": "DEBUG"
},
{
"label": "RELEASE",
"description": "RELEASE",
"command": "",
"parameter": "RELEASE"
},
{
"label": "myOwnRelease",
"description": "My own build release",
"command": "executable.mms",
"parameter": ""
},
{
"label": "myOwnDebug",
"description": "My own build debug",
"command": "build.com",
"parameter": "DEBUG"
}
]
}
</pre>

[[Category:VMS IDE]]

Build Configurations

2019-08-18T15:32:12Z

Andrey.logachev: /* Custom build configurations */

A project build configuration defines how the project should be built. You can have multiple build configurations for a project so that you can build the same code for different purposes. 
By default, there are two build configurations:
* '''DEBUG''', which is necessary for debugging
* '''RELEASE''', which produces binaries for your project deployment.
If necessary, you can add custom build configurations for your project.

== Working with build configurations ==
=== Editing build configurations ===
You can edit the list of build configurations the same way you edit the project settings:
# Press ''F1'' and run the ''VMS-IDE: Edit VMS project settings'' command or use the [[VMS_IDE_Project_Explorer|Project Explorer]] view
# Find the ''builds'' section
# Make the required changes

=== Changing current build configuration ===
To change the current build configuration:
# Open the [[VMS_IDE_Project_Explorer|Project Explorer]] view
# In the ''PROJECT DESCRIPTION'' section, right-click the ''buildName'' parameter, then select ''Change''
# In the popup list select the required configuration.

== Build configuration parameters ==
Each build configuration includes the following parameters:
* '''label''' - unique name of the build configuration. Note: the label is also used as the name of the output folder.
* '''description''' - description of the build configuration
* '''command''' - command (MMS or COM file) to build or clean the project
* '''parameter''' - parameter to pass over to the command

=== Default build configuration ===
If the command is empty, the default [[Auto-generating MMS|auto-created MMS]] file is used to build the project. The '''parameter''' value is used to specify the type of the build: ''DEBUG'' or ''RELEASE''.

=== Custom build configurations ===
If the user defined command is an '''MMS''' file, it is processed via "MMS/EXTENDED_SYNTAX/DESCR=<MMS file> ''parameter''" command. The ''parameter'' value is treated as a target. 

If the user defined command is a '''COM''' file, it is executed with "@<COM file> ''parameter''" command.

'''NOTE:''' It is recommended that the user-defined build procedure creates resulting files in '''<project root>/<output folder>/<build label>''' directory.

=== Important notes ===
''''NOTE:''' when using the '''task2cmd''' to build your projects, use the build configuration label to set the task ''parameter'' value.

=== Example ===
<pre>
"builds": {
"configurations": [
{
"label": "DEBUG",
"description": "DEBUG",
"command": "",
"parameter": "DEBUG"
},
{
"label": "RELEASE",
"description": "RELEASE",
"command": "",
"parameter": "RELEASE"
},
{
"label": "myOwnRelease",
"description": "My own build release",
"command": "executable.mms",
"parameter": ""
},
{
"label": "myOwnDebug",
"description": "My own build debug",
"command": "build.com",
"parameter": "DEBUG"
}
]
}
</pre>

[[Category:VMS IDE]]

Build Configurations

2019-08-18T15:31:22Z

Andrey.logachev:

A project build configuration defines how the project should be built. You can have multiple build configurations for a project so that you can build the same code for different purposes. 
By default, there are two build configurations:
* '''DEBUG''', which is necessary for debugging
* '''RELEASE''', which produces binaries for your project deployment.
If necessary, you can add custom build configurations for your project.

== Working with build configurations ==
=== Editing build configurations ===
You can edit the list of build configurations the same way you edit the project settings:
# Press ''F1'' and run the ''VMS-IDE: Edit VMS project settings'' command or use the [[VMS_IDE_Project_Explorer|Project Explorer]] view
# Find the ''builds'' section
# Make the required changes

=== Changing current build configuration ===
To change the current build configuration:
# Open the [[VMS_IDE_Project_Explorer|Project Explorer]] view
# In the ''PROJECT DESCRIPTION'' section, right-click the ''buildName'' parameter, then select ''Change''
# In the popup list select the required configuration.

== Build configuration parameters ==
Each build configuration includes the following parameters:
* '''label''' - unique name of the build configuration. Note: the label is also used as the name of the output folder.
* '''description''' - description of the build configuration
* '''command''' - command (MMS or COM file) to build or clean the project
* '''parameter''' - parameter to pass over to the command

=== Default build configuration ===
If the command is empty, the default [[Auto-generating MMS|auto-created MMS]] file is used to build the project. The '''parameter''' value is used to specify the type of the build: ''DEBUG'' or ''RELEASE''.

=== Custom build configurations ===
If the user defined command is an '''MMS''' file, it is processed via "MMS/EXTENDED_SYNTAX/DESCR=<MMS file> ''parameter''" command. The ''parameter'' value is treated as a target. 

If the user defined command is a '''COM''' file, it is executed with "@<COM file> ''parameter''" command.

'''NOTE:''' it is recommended that the user-defined build procedure creates resulting files in '''<project root>/<output folder>/<build label>''' directory.

=== Important notes ===
''''NOTE:''' when using the '''task2cmd''' to build your projects, use the build configuration label to set the task ''parameter'' value.

=== Example ===
<pre>
"builds": {
"configurations": [
{
"label": "DEBUG",
"description": "DEBUG",
"command": "",
"parameter": "DEBUG"
},
{
"label": "RELEASE",
"description": "RELEASE",
"command": "",
"parameter": "RELEASE"
},
{
"label": "myOwnRelease",
"description": "My own build release",
"command": "executable.mms",
"parameter": ""
},
{
"label": "myOwnDebug",
"description": "My own build debug",
"command": "build.com",
"parameter": "DEBUG"
}
]
}
</pre>

[[Category:VMS IDE]]

VMS IDE Developing

2019-08-18T15:22:31Z

Andrey.logachev: /* Building */

==Loading Existing Project==
If you start working on an existing project that resides on your OpenVMS machine, you need to download the source files to your local machine. Use the '''Synchronizer''' tool as described below to download the source files.
# Change the [[Synchronize Configuration#Settings Description|'''downloadNewFiles''']] option to ''overwrite''.
# Run the <code>VMS-IDE: Synchronize project files with VMS</code> command.
# After all project files are downloaded, change the '''downloadNewFiles''' option to ''skip'' or ''edit'' to prevent silent overwriting of local files.

==Managing Project Source Files==
You can view and edit all project files from the Visual Studio Code '''Explorer'''. Refer to Visual Studio Code [https://code.visualstudio.com/docs/getstarted/userinterface documentation] to learn more about '''Explorer''' view features.

The OpenVMS project structure may look like shown below:
[[File:Vms ide explorer.png|200px|thumb|none|VMS IDE Explorer]]

==Managing the Project==
You can manage your OpenVMS project from the [[VMS_IDE_Project_Explorer|'''Project Explorer''']] view. To open the view, click ''Project Explorer'' icon on the Activity Bar.

===Managing Dependencies===
If you work on a complex project and you need to add dependencies, use the '''PROJET DEPENDENCIES''' section. 
Assuming that you want to add "Project B" to "Project A" dependencies, 
# Select "Project A" in the '''PROJET DEPENDENCIES''' panel.
# Right-click "Project B", and select ''Add to dependencies of selected'' item from the context menu.
 
To remove a project from dependencies
# Open the '''PROJET DEPENDENCIES''' section.
# Right-click the project, then select ''Remove from dependencies''.

=Building=

===Build Configurations===
To build your projects you can use a default build configuration or create a custom one. See [[Build Configurations]] for details.

===Build MMS===
Before building your project, create the '''MMS''' file by pressing <code>F1</code> and running <code>VMS-IDE: Create MMS</code>. See [[Auto-generated MMS]] for more information.

===Building VMS Project===
To build a project in VMS IDE:
# Open the [[VMS_IDE_Project_Explorer|'''Project Explorer''']] view.
# Select the project you want to build in the '''PROJECT DEPENDENCIES''' section.
# In the '''PROJECT DESCRIPTION''' section, choose the required [[Build Configurations|build configuration]] by right-clicking the '''buildName''' parameter and selecting '''Change'''.
# Right-click the project and select ''Build with dependencies'' from the context menu.

If there are any changes to the project, the updated files will be uploaded to the OpenVMS system. Previously created object and listing files (.OBJ, .LIS) will be removed from the OpenVMS system. This guarantees that up-to-date files are uploaded to the OpenVMS system.

'''NOTE''': you can manually upload all new and updated files by using the [[VMS_IDE_Commands|'''VMS-IDE: Upload all''']] command.

=Debugging=
Use [[VMS_IDE_Debugger|'''Debugger''']] view to debug OpenVMS projects.

'''NOTE''': Before running the debugger, make sure that you have actual DEBUG builds on the OpenVMS system.

To start a debugging session, press <code>F5</code>. If there is no "launch.json" file in the project directory, you will be asked to select the environment. Select <code>VMS Debugger</code> from the popup list.
The '''launch.json''' file will be created and filled with the required information. There are two types of launch configuration - '''DEBUG''' and '''RUN'''.
<pre>"configurations": [
{
"type": "vms_dbg",
"request": "launch",
"name": "Debug",
"program": "",
"arguments": "",
"stopOnEntry": true,
"typeRun": "DEBUG"
}
]
</pre>
For the '''program''' field, specify the relative path to the executable, for example <code>[.project.bin.release]hello.exe</code>.
If the field is empty, '''VMS IDE''' will try to fill it with data from the project settings.

To choose which configuration to use, go to "Debug" (<code>Ctrl-Shift-D</code>) and select the appropriate configuration from the drop-down list.
Press <code>F5</code> again to run debugger.

[[Category:VMS IDE]]

Auto-generated MMS

2019-08-18T15:06:01Z

Andrey.logachev:

The default MMS file generated by <code>VMS-IDE: Create MMS</code> command includes the following operations:
# Collect the list of header files
# Collect the list of source files
# Add header files list as '''INCLUDES'''
# Add source files list as '''SOURCES'''
# Define the main target depending on the project type
# Define object dependencies

'''Note''': For some languages the compilation order is important. To change the order in which objects are compiled, reorder the object files in the main target definition.

Variables '''DEBUG''', '''OUTDIR''' and '''CONFIG''' will be defined by the VMS IDE extension during compilation.

==Example==
<pre>
! header !auto
! Do not modify this file. It may be overwritten automatically. !auto
! includes !auto
INCLUDES= !auto
! sources !auto
SOURCES= - !auto
myprog.cob !auto
! dependencies !auto
.FIRST !auto
!auto
! compiler/linker options !auto
.IF DEBUG !auto
COMPILEFLAGS = /DEBUG/NOOP/LIST=$(MMS$TARGET_NAME)/OBJECT=$(MMS$TARGET) !auto
LINKFLAGS = /DEBUG/MAP=$(MMS$TARGET_NAME)/EXECUTABLE=$(MMS$TARGET) !auto
.ELSE !auto
COMPILEFLAGS = /OBJECT=$(MMS$TARGET) !auto
LINKFLAGS = /EXECUTABLE=$(MMS$TARGET) !auto
.ENDIF !auto
! directives !auto
.SILENT !auto
OUT_DIR = .$(OUTDIR).$(CONFIG) !auto
OBJ_DIR = $(OUT_DIR).obj !auto
.SUFFIXES !auto
.SUFFIXES .OBJ .CPP .C .CLD .MSG .BLI .COB .PAS .BAS .F77 .F90 .FOR .B32 .CBL !auto
.CPP.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
$(CXX) $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.C.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
$(CC) $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.CLD.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
SET COMMAND/OBJECT=$(MMS$TARGET) $(MMS$SOURCE) !auto
!auto
.MSG.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
MESSAGE /OBJECT=$(MMS$TARGET) $(MMS$SOURCE) !auto
!auto
.BLI.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
BLISS $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.B32.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
BLISS $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.COB.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
COBOL $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.CBL.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
COBOL $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.PAS.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
PASCAL $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.BAS.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
BASIC $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.F77.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
FORTRAN $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.F90.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
FORTRAN $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.FOR.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
FORTRAN $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.DEFAULT !auto
! Source $(MMS$TARGET) not yet added !auto
!auto
! main target !auto
[$(OUT_DIR)]$(NAME).EXE : - !auto
[$(OBJ_DIR)]myprog.obj !auto
CXXLINK $(LINKFLAGS) $(MMS$SOURCE_LIST) !auto
!auto
! objects !auto
[$(OBJ_DIR)]myprog.obj : myprog.cob $(INCLUDES) !auto

</pre>

[[Category: VMS IDE]]

Auto-generating MMS

2019-08-18T13:39:28Z

Andrey.logachev: Andrey.logachev moved page Auto-generating MMS to Auto-generated MMS

#REDIRECT [[Auto-generated MMS]]

Auto-generated MMS

2019-08-18T13:39:28Z

Andrey.logachev: Andrey.logachev moved page Auto-generating MMS to Auto-generated MMS

The order of default MMS creation:
# Collect header files list
# Collect source files list
# Put header files list as '''INCLUDES''' into default MMS content
# Put source files list as '''SOURCES''' into default MMS content
# Define main target depending on type of project
# Define object dependencies

'''Note''': For some languages the order of compilation is important. To do this just reorder object files in main target definition.

Variables '''DEBUG''', '''OUTDIR''' and '''CONFIG''' will be defined by extension at the moment of compilation.

==Example==
<pre>
! header !auto
! Do not modify this file. It may be overwritten automatically. !auto
! includes !auto
INCLUDES= !auto
! sources !auto
SOURCES= - !auto
myprog.cob !auto
! dependencies !auto
.FIRST !auto
!auto
! compiler/linker options !auto
.IF DEBUG !auto
COMPILEFLAGS = /DEBUG/NOOP/LIST=$(MMS$TARGET_NAME)/OBJECT=$(MMS$TARGET) !auto
LINKFLAGS = /DEBUG/MAP=$(MMS$TARGET_NAME)/EXECUTABLE=$(MMS$TARGET) !auto
.ELSE !auto
COMPILEFLAGS = /OBJECT=$(MMS$TARGET) !auto
LINKFLAGS = /EXECUTABLE=$(MMS$TARGET) !auto
.ENDIF !auto
! directives !auto
.SILENT !auto
OUT_DIR = .$(OUTDIR).$(CONFIG) !auto
OBJ_DIR = $(OUT_DIR).obj !auto
.SUFFIXES !auto
.SUFFIXES .OBJ .CPP .C .CLD .MSG .BLI .COB .PAS .BAS .F77 .F90 .FOR .B32 .CBL !auto
.CPP.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
$(CXX) $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.C.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
$(CC) $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.CLD.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
SET COMMAND/OBJECT=$(MMS$TARGET) $(MMS$SOURCE) !auto
!auto
.MSG.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
MESSAGE /OBJECT=$(MMS$TARGET) $(MMS$SOURCE) !auto
!auto
.BLI.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
BLISS $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.B32.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
BLISS $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.COB.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
COBOL $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.CBL.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
COBOL $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.PAS.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
PASCAL $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.BAS.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
BASIC $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.F77.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
FORTRAN $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.F90.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
FORTRAN $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.FOR.OBJ !auto
pipe create/dir $(DIR $(MMS$TARGET)) | copy SYS$INPUT nl: !auto
FORTRAN $(COMPILEFLAGS) $(MMS$SOURCE) !auto
!auto
.DEFAULT !auto
! Source $(MMS$TARGET) not yet added !auto
!auto
! main target !auto
[$(OUT_DIR)]$(NAME).EXE : - !auto
[$(OBJ_DIR)]myprog.obj !auto
CXXLINK $(LINKFLAGS) $(MMS$SOURCE_LIST) !auto
!auto
! objects !auto
[$(OBJ_DIR)]myprog.obj : myprog.cob $(INCLUDES) !auto

</pre>

[[Category: VMS IDE]]

VMS IDE Debugger

2019-08-13T20:01:45Z

Andrey.logachev:

'''VMS IDE''' uses Visual Studio Code built-in debugger and supports all of its features.

=Features=
[[File:Vms-ide-debugger.png|900px|none|none|VMS IDE Debugger]]

; [1] VARIABLES : Shows local variables. If the panel is collapsed, variables are not requested. When debugging, you can set variable values by double-clicking them and typing a new value.
; [2] WATCH: You can add variable names (expressions) to set watchpoints:
: * Expression without braces "()" - request variable value (local or global);
: * Expression with empty braces "()" - enable watchpoint, for example <code>x()</code>;
: * Expression with conditional expression in braces "(when ...)" - enable watchpoint with condition, for example <code>x(when (x<5))</code>.
; [3] CALL STACK : Shows stack frames. Variables and expressions listed in VARIABLES and WATCH sections are relative to the selected stack frame.
; [4] BREAKPOINTS : Shows breakpoints set for the current project.
; [5] DEBUG TOOLBAR : Provides standard debugging actions. Edit field '''stopOnEntry''' in the launch.json file:
:* Set field "stopOnEntry" = true to enable stop on entry.
:* Set field "stopOnEntry" = false to disable stop on entry.
; [6] EDITOR :
: * Breakpoints can be toggled by clicking on the '''Editor''' margin or using <code>F9</code> on the current line.
: * Variable values can be seen by hovering over variables in the code.
; [7] DEBUG CONSOLE : Shows debugging output. Opens automatically as soon as debugging session starts. All program output will be on this screen. If the program requires data input, enter it in the Debug Console REPL.

=Important Notes=
If you cannot set breakpoints in the source file please check the language mode of the source file (see image).
[[File:Lang-mode.png|200px|thumb|none|Language mode]]

== Supported Languages ==
Only the following languages are supported (case sensitive):
* c
* cpp
* cobol
* fortran
* pascal
* bliss
* vms-basic

According to the '''breakpoints''' section in the 'package.json' file:
<pre>
"breakpoints": [
{
"language": "c"
},
{
"language": "cpp"
},
{
"language": "bliss"
},
{
"language": "vms-basic"
},
{
"language": "cobol"
},
{
"language": "pascal"
},
{
"language": "fortran"
}
]
</pre>

=Additional Information=
Please view [https://code.visualstudio.com/docs/editor/debugging Visual Studio Code documentation] to learn more about Debbuger view and debugging process in Visual Studio Code. 

[[Category:VMS IDE]]

VMS IDE Commands

2019-08-13T19:35:01Z

Andrey.logachev:

To invoke the commands, press <code>F1</code> in the Visual Studio Code editor and start typing the command.
[[File:Vms-ide-commands.png|800px|thumb|none|VMS IDE Commands]]

=Commands=
* <code>'''VMS-IDE: Edit VMS project settings'''</code> - Edit project settings. [[Project Settings]]
* <code>'''VMS-IDE: Build on VMS'''</code> - Build project on VMS with its dependencies.
* <code>'''VMS-IDE: Build only this project'''</code> - Build only the selected project on VMS (Ctrl+Alt+F7).
* <code>'''VMS-IDE: Change CR/LF for all source files'''</code> - Change CRLF to LF for all source files.
* <code>'''VMS-IDE: Clean project'''</code> - Clean project, delete files from output folder.
* <code>'''VMS-IDE: Create MMS'''</code> - Create default MMS. [[Auto-generating MMS]]
* <code>'''VMS-IDE: Download system headers'''</code> - Download system headers from VMS.
* <code>'''VMS-IDE: Edit ssh-helper settings'''</code> - Edit connection settings. [[SSH Settings]]
* <code>'''VMS-IDE: Force built status'''</code> - Force built status.
* <code>'''VMS-IDE: Force synchronized status'''</code> - Force synchronized status.
* <code>'''VMS-IDE: Quick uploading'''</code> - Upload the changes made to the source code on the the local machine since the start of the extension or the last upload/synchronization to the remote machine.
* <code>'''VMS-IDE: Re-build on VMS'''</code> - Re-build project on VMS with its dependencies.
* <code>'''VMS-IDE: Re-build only this project'''</code> - Re-build only the selected project on VMS.
* <code>'''VMS-IDE: Synchronize project file with VMS'''</code> - Synchronize project files with VMS.
* <code>'''VMS-IDE: Terminal'''</code> - OpenVMS terminal (<code>Ctrl+F6</code>)
* <code>'''VMS-IDE: Upload all'''</code> - Upload all new and updated files from local machine to VMS. '''NOTE''': If '''preferZip''' is set to true, the ''whole'' project will be uploaded as a ZIP file.
* <code>'''VMS-IDE: Upload all via Zip'''</code> - Upload project files using Zip

[[Category:VMS IDE]]

File:Vms-ide-commands.png

2019-08-13T19:23:35Z

Andrey.logachev: Andrey.logachev uploaded a new version of File:Vms-ide-commands.png

== Summary ==
VMS IDE Commands

Project Settings

2019-08-13T19:09:09Z

Andrey.logachev:

=Project Configuration Example=
<pre>
{
"project": {
"break": "C",
"builders": "*.{mms,com}",
"exclude": "**/{node_modules,.vscode}/**",
"headers": "*.h",
"listing": "*.lis",
"outdir": "out",
"projectName": "project",
"projectType": "executable",
"resource": "**/resource/**",
"root": "project",
"source": "*.{cpp,c}",
"addLibraries": "sys$library:IMAGELIB.OLB,sys$library:RDBMSGS.OLB",
"addIncludes": "sys$library"
}
}
</pre>

=Project Settings Description=
* <code>'''Break'''</code> - Keyboard key to pause debugging in VMS IDE debugger. The extension uses combination <code>CTRL+Key</code> to pause debugging when user press '''Pause''' or <code>F6</code>.
* <code>'''Builders'''</code> - Mask for files used for building the project. Default is "*.{mms,com}".
* <code>'''Exclude'''</code> - Folders excluded from synchronization with OpenVMS system.
* <code>'''Headers'''</code> - Header files. Default is "*.{h,hpp}".
* <code>'''Listing'''</code> - Listing files that will be downloaded after the project is built for debugging purpose.
* <code>'''Outdir'''</code> - Output directory where object, listing and executable files will be stored when built. Is also used for temporary files. '''NOTE''': Should be only the name of the folder, not a full or relative path.
* <code>'''Project Name'''</code> - Name for the executable file, auto-generated '''MMS''' file for builder, OPT file for linker, and COM file for defining logical names. '''NOTE''': Use one word only; do not use spaces or special characters.
* <code>'''Project Type'''</code> - Type of the project. Available types: '''executable''', '''library''' or '''shareable'''. The building method depends on the type of the project and its dependencies.
* <code>'''Resource'''</code> - Files required for the project, but are not involved in the build process.
* <code>'''Root'''</code> - Directory of the project on the remote OpenVMS machine in UNIX format relative to the home folder.
* <code>'''Source'''</code> - Mask for the source files, e.g. "*.{c,cpp}".
* <code>'''Additional libraries'''</code> - list of libraries in ODS-5 format, separated by commas.
* <code>'''Additional include folders'''</code> - list of folders in ODS-5 format, separated by commas.

=Adjusting Project Settings=
# Set the <code>'''Root'''</code> directory. For example, if the project is located in '''WORK:[USER.DEMOS.SIMPLE]''' and the home directory is '''WORK:[USER]''', set the parameter value to '''demos/simple'''.
# Select the <code>'''Project Type'''</code> that you need.
# Specify the <code>'''Project Name'''</code>. '''NOTE''': do not use spaces or special characters.
# Check <code>'''Builders'''</code>. These files will be synchronized.
# Check <code>'''Headers'''</code>. These files will be synchronized and included into the [[Auto-generating MMS|auto-generated MMS]] file as header files. Changing any of them will result in full project rebuild.
# Check <code>'''Source'''</code>. These files will be synchronized and included into the [[Auto-generating MMS|auto-generated MMS]] file as source files.
# Check <code>'''Resource'''</code>. These files will be synchronized but not included into the [[Auto-generating MMS|auto-generated MMS]] file.
# Adjust the <code>'''Exclude'''</code> field value to list the files similar to the described above but not to be synchronized and compiled.
# Check <code>'''Listing'''</code>. These files will be downloaded after building the project. Files "*.lis,*.map" are required for debugger.
# If the project depends on already installed libraries, specify the in the <code>'''Additional libraries'''</code> and <code>'''Additional include folders'''</code>

[[Category:VMS IDE]]

VMS IDE Project Configuration

2019-08-13T18:53:29Z

Andrey.logachev:

=Workspace=
When starting working on a project in the '''VMS IDE''', you need to configure your workspace, set project folders, and select the type of configuration that will be used.

==Project folder==
Use '''Explorer''' view to manage source code, resources, and settings files for your projects.
{| style="border-style: none;"
|-
|rowspan="2"| [[File:Vms ide explorer.png|200px|thumb|none|VMS IDE Explorer]]
|style="vertical-align:top; padding-left: 20px;" | The project folder will store project settings and source files. To add a project folder
# Create a folder on your local machine.
# In Visual Studio Code, click the ''Explorer'' icon (<code>Ctrl+Shift+E</code>) in the Activity Bar
# Click ''Open Folder'' and select the previously created folder.
 
If you are working on a complex project with dependencies, you will likely need to add other projects to the current workspace. 
For this, just add another project folder as shown below.
# Create another folder that will store files of the second project
# In Visual Studio Code, select ''File > Add folder to workspace'' and select the folder you created.
|}

==End of line==
Specify the End of Line character that will be used across all source files. '''You must use <code>LF</code>'''.
# Open Visual Studio Code settings (<code>Ctrl+,</code>)
# Navigate to ''Text Editor > Files > Eol'' (the default end of line character) and set it to ''\n''.

==Type of configuration==
Select the type of configuration for your project. The recommended type is '''FS'''.
# Open Visual Studio Code settings (<code>Ctrl+,</code>)
# Navigate to ''Extensions > VMS-IDE > Config-helper › Settings: Using'', and select one of the options:
#* '''FS''' - save settings in local JSON files.
#* '''VFS''' - save setting in VS Code virtual file system.
#* '''VCS''' - manage settings using VS Code provided API.
# Press <code>F1</code> and run the ''Reload window'' command or close Visual Studio Code and open it again.

{| style="border-style: none;"
! FS and VFS
! VCS
|-
|style="padding-right: 20px;" | [[File:Syncronizer-settings-fs.png|600px|none|thumb|]]
|style="padding-left: 20px;" | [[File:Syncronizer-settings-vsc.png|600px|thumb|none|]]
|-
|style="padding-right: 20px; text-align: center" | Settings are stored in a JSON file that can be easily modified in the editor.
|style="padding-left: 20px; text-align: center" | Settings can be adjusted using Visual Studio Code settings page.
|}

'''NOTE''': Changing the type of configuration does not copy existing settings from one location to another.

=SSH Configuration=
The SSH connection to an OpenVMS machine is required for syncing source files, building, and debugging projects. There are two ways of managing SSH connection settings.

; Command : Press <code>F1</code> and run the <code>VMS-IDE: Edit ssh-helper settings</code> command.

; Project Explorer :
:# Open [[VMS_IDE_Project_Explorer|'''Project Explorer''']]
:# Select your project from the list
:# In the ''PROJECT DESCRIPTION'' section, right-click ''SSH > host'' and select ''Edit''.

==SSH Settings description==
See [[SSH_Settings|''SSH settings'']] for more details.

=Project Configuration=
To open the project settings, press <code>F1</code> and run the <code>VMS-IDE: Edit VMS project settings</code> command or use the [[VMS_IDE_Project_Explorer|'''Project Explorer''']] view.

==Adjusting Settings==
The project configuration procedure varies depending on the selected type of configuration.

; FS or VFS : The Edit command loads current settings from memory and saves them to '''vmssoftware.synchronizer-settings.json''', then opens the file for editing.
; VCS : The Edit command opens Workspace settings. Navigate to '''Synchronizer''' section and adjust the settings.

==Settings description==
The settings are split into three sections:
* [[Project_Settings|''Project'']] - general project settings
* [[Synchronize_Configuration|''Synchronize'']] - synchronizer specific settings
* [[Build_Configurations|''Builds'']] - build configurations for the project
[[Category:VMS IDE]]

Project Settings

2019-08-13T18:34:54Z

Andrey.logachev:

COBOL grammar

2019-08-13T17:55:51Z

Andrey.logachev:

Grammar works mostly for /NOANSI_FORMAT

{| style="border-style: none;"
|-
|rowspan="1"| [[File:Cobol example 1.png|frame|left|COBOL grammar]]
|style="vertical-align:top; padding-left: 20px;" |

'''Highlighting'''
* Divisions
* Sections
* Sentences
* Keywords
* Required words
* Optional words
* Reserved words
* Literals
* Operators
|}
[[Category:VMS IDE]]

VMS IDE Project Explorer

2019-08-13T17:36:00Z

Andrey.logachev:

The '''Project Explorer''' view helps to manage OpenVMS projects, their dependencies, and settings. It is also possible to build, rebuild, and clean the project using the '''Project Explorer''' context menu.

=Description=
{| style="border-style: none;"
|-
|rowspan="2"| [[File:Project-explorer.PNG|frame|left|Project Explorer]]
|style="vertical-align:top; padding-left: 20px;" |
==Project Dependencies==

====Project types====
* ''executable'' - executable image is created
* ''library'' - object library (OLB) is created
* ''shareable'' - shareable image is created

====Context Menu====
* '''Add to dependencies of selected''' - add the project you right-clicked to the previously selected project as a dependency
* '''Remove project from dependencies''' - remove the selected project from dependencies of the main project
* '''Build only this project''' - build the current project
* '''Build with dependencies''' - build the current project and all its dependencies
* '''Clean this only''' - clean current project only
* '''Rebuild only this project''' - rebuild the current project
* '''Rebuild with dependencies''' - rebuild the current project and all its dependencies

====Creating MMS Files====
'''VMS IDE''' can create '''MMS''' files automatically based on the project type and the types of its dependencies. 
For ''shareable'' images, an options ('''OPT''') file is created, but the universal symbol vector must be edited manually. 
If the project depends on some shareable images, a '''COM''' file is created with ''logicals'' required for running the project.

==Project Description==
When a project is selected in the Project Dependencies panel, its description is shown.
* '''Local'''
** ''folder'' - [[VMS IDE Project Configuration|Workspace folder name]]
** ''buildName'' - currently selected [[Build Configurations|build configuration]] (right-click and select '''Change''' to choose another one)
** ''sourceState'' - current state of source files
*** ''unknown'' - no synchronization or upload was performed or there were changes to the Project or SSH settings
*** ''modified'' - there are changes that need to be synchronized
*** ''synchronized'' - project files on the local machine and OpenVMS are synchronized
** ''buildState'' - whether the project is built or not (''Built'' or ''Not built'')
** ''masters'' - projects which depend on the currently selected project
* '''SSH'''
** ''host'' - OpenVMS host to synchronize and build with
* '''Project'''
** ''projectName'' - the name of the project
** ''projectType'' - [[#Project types|the type of the project]]
** ''root'' - project root on OpenVMS
|}

[[Category:VMS IDE]]

Build Configurations

2019-08-13T17:21:13Z

Andrey.logachev:

A project build configuration defines how the project should be built. You can have multiple build configurations for a project so that you can build the same code for different purposes. 
By default, there are two build configurations:
* '''DEBUG''', which is necessary for debugging
* '''RELEASE''', which produces binaries for your project deployment.
If necessary, you can add custom build configurations for your project.

== Working with build configurations ==
=== Editing build configurations ===
You can edit the list of build configurations the same way you edit the project settings:
# Press ''F1'' and run the ''VMS-IDE: Edit VMS project settings'' command or use the [[VMS_IDE_Project_Explorer|Project Explorer]] view
# Find the ''builds'' section
# Make the required changes

=== Changing current build configuration ===
To change the current build configuration:
# Open the [[VMS_IDE_Project_Explorer|Project Explorer]] view
# In the ''PROJECT DESCRIPTION'' section, right-click the ''buildName'' parameter, then select ''Change''
# In the popup list select the required configuration.

== Build configuration parameters ==
Each build configuration includes the following parameters:
* '''label''' - unique name of the build configuration. Note: the label is also used as the name of the output folder.
* '''description''' - description of the build configuration
* '''command''' - command (MMS or COM file) to build or clean the project
* '''parameter''' - parameter to pass over to the command

=== Default build configuration ===
If the command is empty, the default [[Auto-generating MMS|auto-created MMS]] file is used to build the project. The '''parameter''' value is used to specify the type of the build: ''DEBUG'' or ''RELEASE''.

=== Custom build configurations ===
If the user defined command is an '''MMS''' file, it is processed via "MMS/EXTENDED_SYNTAX/DESCR=<MMS file> ''parameter''" command. The ''parameter'' value is treated as a target. 

If the user defined command is a '''COM''' file, it is executed with "@<COM file> ''parameter''" command.

'''NOTE:''' it is recommended that the user-defined build procedure creates resulting files in '''<project root>/<output folder>/<build label>''' directory.

=== Clean operation ===
To run the '''CLEAN''' operation, use the default command (empty value) and set the '''parameter''' value to "CLEAN".

=== Important notes ===
Changes in '''task2cmd''': parameter for any build and clean command must be named build configuration label.

=== Example ===
<pre>
"builds": {
"configurations": [
{
"label": "DEBUG",
"description": "DEBUG",
"command": "",
"parameter": "DEBUG"
},
{
"label": "RELEASE",
"description": "RELEASE",
"command": "",
"parameter": "RELEASE"
},
{
"label": "myOwnRelease",
"description": "My own build release",
"command": "executable.mms",
"parameter": ""
},
{
"label": "myOwnDebug",
"description": "My own build debug",
"command": "build.com",
"parameter": "DEBUG"
}
]
}
</pre>

[[Category:VMS IDE]]

VMS IDE Project Configuration

2019-08-11T06:51:02Z

Andrey.logachev: /* Settings description */

=Workspace=
When starting working on an OpenVMS project in the '''VMS IDE''', you need to configure your workspace, set project folders, and select the type of configuration that will be used.

==Project folder==
Use '''Explorer''' view to manage source code, resources, and settings files for your projects.
{| style="border-style: none;"
|-
|rowspan="2"| [[File:Vms ide explorer.png|200px|thumb|none|VMS IDE Explorer]]
|style="vertical-align:top; padding-left: 20px;" | The project folder will store project settings and source files. To add a project folder
# Create a folder on your local machine.
# In Visual Studio Code, click the ''Explorer'' icon (<code>Ctrl+Shift+E</code>) in the Activity Bar
# Click ''Open Folder'' and select the previously created folder.
 
If you are working on a complex project with dependencies, you will likely need to add other projects to the current workspace. 
For this, just add another project folder as shown below.
# Create another folder that will store files of the second project
# In Visual Studio Code, select ''File > Add folder to workspace'' and select the folder you created.
|}

==End of line==
Specify the End of Line character that will be used across all source files. '''You must use <code>LF</code>'''.
# Open Visual Studio Code settings (<code>Ctrl+,</code>)
# Navigate to ''Text Editor > Files > Eol'' (the default end of line character) and set it to ''\n''.

==Type of configuration==
Select the type of configuration for your project. The recommended type is '''FS'''.
# Open Visual Studio Code settings (<code>Ctrl+,</code>)
# Navigate to ''Extensions > VMS-IDE > Config-helper › Settings: Using'', and select one of the options:
#* '''FS''' - save settings in local JSON files.
#* '''VFS''' - save setting in VS Code virtual file system.
#* '''VCS''' - manage settings using VS Code provided API.
# Press <code>F1</code> and run the ''Reload window'' command or close Visual Studio Code and open it again.

{| style="border-style: none;"
! FS and VFS
! VCS
|-
|style="padding-right: 20px;" | [[File:Syncronizer-settings-fs.png|600px|none|thumb|]]
|style="padding-left: 20px;" | [[File:Syncronizer-settings-vsc.png|600px|thumb|none|]]
|-
|style="padding-right: 20px; text-align: center" | Settings are stored in a JSON file that can be easily modified in the editor.
|style="padding-left: 20px; text-align: center" | Settings can be adjusted using Visual Studio Code settings page.
|}

'''NOTE''': Changing the type of configuration does not copy existing settings from one location to another.

=SSH Configuration=
The SSH connection to an OpenVMS machine is required for syncing source files, building, and debugging projects. There are two ways of managing SSH connection settings.

; Command : Press <code>F1</code> and run the <code>VMS-IDE: Edit ssh-helper settings</code> command.

; Project Explorer :
:# Open [[VMS_IDE_Project_Explorer|'''Project Explorer''']]
:# Select your project from the list
:# In the ''PROJECT DESCRIPTION'' section, right-click ''SSH > host'' and select ''Edit''.

==SSH Settings description==
See [[SSH_Settings|''SSH settings'']] for more details.

=Project Configuration=
To open the project settings, press <code>F1</code> and run the <code>VMS-IDE: Edit OpenVMS project settings</code> command or use [[VMS_IDE_Project_Explorer|'''Project Explorer''']] view.

==Adjusting Settings==
The project configuration procedure varies depending on the selected type of configuration.

; FS or VFS : The Edit command loads current settings from memory and saves them to '''vmssoftware.synchronizer-settings.json''', then opens the file for editing.
; VCS : The Edit command opens Workspace settings. Navigate to '''Synchronizer''' section and adjust the settings.

==Settings description==
The settings are split into three sections:
* [[Project_Settings|''Project'']] - general project settings
* [[Synchronize_Configuration|''Synchronize'']] - synchronizer specific settings
* [[Build_Configurations|''Builds'']] - build configurations for the project
[[Category:VMS IDE]]

VMS IDE Developing

2019-04-14T14:13:47Z

Andrey.logachev: /* Building */

==Loading Existing Project==
If you start working on an existing project that resides on OpenVMS machine, you need to download source files to your local machine. Use the '''Synchronizer''' tool as described below to download the source files.
# Change the [[Synchronize Configuration#Settings Description|'''downloadNewFiles''']] option to ''overwrite''.
# Run <code>VMS-IDE: Synchronize project files with VMS</code> command.
# After all project files are downloaded, change the '''downloadNewFiles''' option to ''skip'' or ''edit'' to prevent silent overwriting of local files.

==Managing Project Source Files==
You can view and edit all project files from the Visual Studio Code '''Explorer'''. Refer to Visual Studio Code [https://code.visualstudio.com/docs/getstarted/userinterface documentation] to learn more about '''Explorer''' view features.

The OpenVMS project structure may look like shown below:
[[File:Vms ide explorer.png|200px|thumb|none|VMS IDE Explorer]]

==Managing the Project==
You can manage your OpenVMS project from the [[VMS_IDE_Project_Explorer|'''Project Explorer''']] view. To open the view, click ''Project Explorer'' icon on the Activity Bar.

===Managing Dependencies===
If you work on a complex project and you need to add dependencies, use the '''PROJET DEPENDENCIES''' section. 
Assuming that you want to add "Project B" to "Project A" dependencies, 
# Select "Project A" in the '''PROJET DEPENDENCIES''' panel.
# Right-click "Project B", and select ''Add to dependencies of selected'' item from the context menu.
 
To remove a project from dependencies
# Open the '''PROJET DEPENDENCIES''' section.
# Right-click the project, then select ''Remove from dependencies''.

=Building=

===Build MMS===
Before building the project, create the '''MMS''' file by pressing <code>F1</code> and running <code>VMS-IDE: Create MMS</code>.

===Building VMS Project===
To build a project in VMS IDE:
# Open the [[VMS_IDE_Project_Explorer|'''Project Explorer''']] view.
# Select the project you want to build in the '''PROJET DEPENDENCIES''' section.
# In the '''PROJET DESCRIPTION''' section, select the required build type (<code>DEBUG</code> or <code>RELEASE</code>) by clicking the '''buildType''' parameter.
# Right-click the project and select ''Build with dependencies'' from the context menu.

If there are any changes to the project, the updated files will be uploaded to the OpenVMS system. Previously created object and listing files (.OBJ, .LTS) will be removed from the OpenVMS system. This guarantees that up-to-date files are uploaded to the OpenVMS system.

'''NOTE''': you can manually upload all new and updated file by using [[VMS_IDE_Commands|'''VMS-IDE: Upload all''']] command.

===Building with Custom Procedure===
To build a project using a custom build procedure, edit the ''task.json'' file
<pre>{
"type": "task2cmd",
"command": "vmssoftware.synchronizer.buildProject",
"extension": "vmssoftware.synchronizer",
"parameter": "build.com",
"label": "Build Procedure",
"problemMatcher": []
}</pre>
where
* '''parameter''' is the name of your build procedure (COM file)
* '''label''' meaningful task name
All other parameters must be as shown in example.

'''NOTE''': see Visual Studio Code [https://code.visualstudio.com/docs/editor/tasks documentation] for more information on '''tasks'''.

=Debugging=
Use [[VMS_IDE_Debugger|'''Debugger''']] view to debug OpenVMS projects.

'''NOTE''': Before running debugger, make sure that you have actual DEBUG builds on the OpenVMS system.

To start debugging session, press <code>F5</code>. If there is no "launch.json" file in the project directory, you will be asked to select the environment. Select <code>VMS Debugger</code> from the popup list.
The '''launch.json''' file will be created and filled with the required information. There are two types of launch configuration - '''DEBUG''' and '''RUN'''.
<pre>"configurations": [
{
"type": "vms_dbg",
"request": "launch",
"name": "Debug",
"program": "",
"arguments": "",
"stopOnEntry": true,
"typeRun": "DEBUG"
}
]
</pre>
For the '''program''' field, specify the relative path to the executable, for example <code>[.project.bin.release]hello.exe</code>.
If the field is empty, '''VMS IDE''' will try to fill it with data from the project settings.

To choose which configuration to use, go to "Debug" (<code>Ctrl-Shift-D</code>) and select the appropriate configuration from the drop-down list.
Press <code>F5</code> again to run debugger.

[[Category:VMS IDE]]

VMS IDE Project Explorer

2019-04-14T14:12:58Z

Andrey.logachev: /* Project Description */

The '''Project Explorer''' view helps to manage OpenVMS projects, their dependencies, and settings. It is also possible to build, rebuild, and clean the project using the '''Project Explorer''' context menu.

=Description=
{| style="border-style: none;"
|-
|rowspan="2"| [[File:Project-explorer.PNG|frame|left|Project Explorer]]
|style="vertical-align:top; padding-left: 20px;" |
==Project Dependencies==

====Project types====
* ''executable'' - executable image is created
* ''library'' - object library (OLB) is created
* ''shareable'' - shareable image is created

====Context Menu====
* '''Add to dependencies of selected''' - add the project you right-clicked to the previously selected project as a dependency
* '''Remove project from dependencies''' - remove the selected project from dependencies of the main project
* '''Build only this project''' - build the current project
* '''Build with dependencies''' - build the current project and all its dependencies
* '''Clean this only''' - clean current project only
* '''Rebuild only this project''' - rebuild the current project
* '''Rebuild with dependencies''' - rebuild the current project and all its dependencies

====Creating MMS====
'''VMS IDE''' can create '''MMS''' files automatically based on the project type and types of its dependencies. 
For ''shareable'' images, an '''OPT''' file is created, but the universal symbol vector must be edited, so that other images could link to this image. 
If the project depends on some shareable images, a '''COM''' file is created with ''logicals'' required for running the project.

==Project Description==
When a project is selected in the Project Dependencies panel, its description is shown.
* '''Local'''
** ''folder'' - [[VMS IDE Project Configuration|Workspace folder name]]
** ''buildType'' - the type of build: ''DEBUG'' or ''RELEASE'' (click to change)
** ''sourceState'' - current state of source files
*** ''unknown'' - no synchronization or upload was performed or there were changes to the Project or SSH settings
*** ''modified'' - there are changes that needs to be synchronized
*** ''synchronized'' - project files on the local machine and OpenVMS are synchronized
** ''buildState'' - ''built'' or ''not built''
** ''masters'' - projects which depend on the currently selected project
* '''SSH'''
** ''host'' - OpenVMS host to synchronize and build with
* '''Project'''
** ''projectName'' - the name of the project
** ''projectType'' - [[#Project types|the type of the project]]
** ''root'' - project root in OpenVMS
|}

[[Category:VMS IDE]]

VMS IDE Commands

2019-04-14T13:22:41Z

Andrey.logachev: /* Commands */

To invoke the commands, press <code>F1</code> in the Visual Studio Code editor and start typing the command.
[[File:Vms-ide-commands.png|800px|thumb|none|VMS IDE Commands]]

=Commands=
* <code>'''VMS-IDE: Terminal'''</code> - Open VMS terminal (<code>Ctrl+F6</code>)
* <code>'''VMS-IDE: Edit ssh-helper settings'''</code> - Edit connection settings
* <code>'''VMS-IDE: Edit OpenVMS project settings'''</code> - Edit project settings
* <code>'''VMS-IDE: Change CR/LF for all source files'''</code> - Change CRLF to LF for all source files
* <code>'''VMS-IDE: Create MMS'''</code> - Create default MMS
* <code>'''VMS-IDE: Build on VMS'''</code> - Build project on VMS with its dependencies
* <code>'''VMS-IDE: Re-build on VMS'''</code> - Rebuild project on VMS with its dependencies
* <code>'''VMS-IDE: Clean project'''</code> - Clean project, delete files from output folder
* <code>'''VMS-IDE: Upload all'''</code> - Upload all new and updated files from local machine to VMS. '''NOTE''': If '''preferZip''' is set to true, the ''whole'' project will be uploaded as a ZIP file.
* <code>'''VMS-IDE: Synchronize project file with VMS'''</code> - Syncronize project files with VMS
* <code>'''VMS-IDE: Force synchronized status'''</code> - Force synchronized status
* <code>'''VMS-IDE: Force built status'''</code> - Force built status
* <code>'''VMS-IDE: Upload all via Zip'''</code> - Upload project files using Zip
* <code>'''VMS-IDE: Download system headers'''</code> - Download system headers from VMS

[[Category:VMS IDE]]

VMS IDE Project Configuration

2019-03-31T08:37:21Z

Andrey.logachev:

=Workspace=
When starting working on an OpenVMS project in '''VMS IDE''', you need to configure your workspace, set project folders, and select the type of configuration that will be used.

==Project folder==
Use '''Explorer''' view to manage source code, resources, and settings files of your projects.
{| style="border-style: none;"
|-
|rowspan="2"| [[File:Vms ide explorer.png|200px|thumb|none|VMS IDE Explorer]]
|style="vertical-align:top; padding-left: 20px;" | Project folder will store project settings and source files. To add a project folder
# Create a folder on your machine.
# In Visual Studio Code, click the ''Explorer'' icon (<code>Ctrl+Shift+E</code>) in the Activity Bar
# Click ''Open Folder'' and select the previously created folder.
 
If you are working on a complex project with dependencies, you will likely need to add other projects to the current workspace. 
For this, just add another project folder as shown below.
# Create another folder that will store files of the second project
# In Visual Studio Code, select ''File > Add folder to workspace'' and select the folder you created.
|}

==End of line==
Specify the End of Line character that will be used across all source files. '''You must use <code>LF</code>'''.
# Open Visual Studio Code settings (<code>Ctrl+,</code>)
# Navigate to ''Text Editor > Files > Eol'' (The default end of line character) and set it to ''\n''.

==Type of configuration==
Select type of configuration for your project. Recommended type is '''FS'''.
# Open Visual Studio Code settings (<code>Ctrl+,</code>)
# Navigate to ''Extensions > VMS-IDE > Config-helper › Settings: Using'', and select one of the options:
#* '''FS''' - save settings in local JSON files.
#* '''VFS''' - save setting in VS Code virtual file system.
#* '''VCS''' - manage settings using VS Code provided API.
# Press <code>F1</code> and run ''Reload window'' command or close Visual Studio Code and open it again.

{| style="border-style: none;"
! FS and VFS
! VCS
|-
|style="padding-right: 20px;" | [[File:Syncronizer-settings-fs.png|600px|none|thumb|]]
|style="padding-left: 20px;" | [[File:Syncronizer-settings-vsc.png|600px|thumb|none|]]
|-
|style="padding-right: 20px; text-align: center" | Settings are stored in a JSON file that can be easily modified in the editor.
|style="padding-left: 20px; text-align: center" | Settings can be adjusted using Visual Studio Code settings page.
|}

'''NOTE''': Changing the type of configuration does not copy existing settings from one location to another.

=SSH Configuration=
The SSH connection to an OpenVMS machine is required for syncing source files, building and debugging projects. There are two ways of managing SSH connection settings.

; Command : Press <code>F1</code> and run <code>VMS-IDE: Edit ssh-helper settings</code> command.

; Project Explorer :
:# Open [[VMS_IDE_Project_Explorer|'''Project Explorer''']]
:# Select your project from the list
:# In the ''PROJECT DESCRIPTION'' section, right-click ''SSH > host'' and select ''Edit''.

==SSH Settings description==
See [[SSH_Settings|''SSH settings'']] for more details.

=Project Configuration=
To open the project settings, press <code>F1</code> and run <code>VMS-IDE: Edit OpenVMS project settings</code> command or use [[VMS_IDE_Project_Explorer|'''Project Explorer''']] view.

==Adjusting Settings==
The project configuration procedure varies depending on the selected type of configuration.

; FS or VFS : The Edit command loads current settings from memory and saves it to '''vmssoftware.synchronizer-settings.json''' file, then opens the file for editing.
; VCS : The Edit command opens Workspace settings. Navigate to '''Synchronizer''' section and adjust the settings.

==Settings description==
The settings are split into two sections:
* [[Project_Settings|''Project'']] - general project settings
* [[Synchronize_Configuration|''Synchronize'']] - synchronizer specific settings

[[Category:VMS IDE]]