Mounting a CMS Version Control Filesystem

Within NetBeans, mounting a CMS Version Control Filesystem consists of specifying the location in Explorer [Filesystems] that you want to put under source control and supplying the location of your CMS source library.

Note Before you begin these instructions, your OpenVMS CMS library must be set up.

Set up the CMS configuration

1. Select Mount Version Control from the Versioning menu and choose Generic VCS.

Alternatively:

From the NetBeans File menu, select Mount Filesystem to open the New Wizard (Choose Template page).

Then select Generic VCS and click Next.

-or-

Right-click the Filesystems root in Explorer [Filesystems] to open the context menu and select Mount.

Then select Generic VCS from the Version Control menu.

 

2. Select Version Control from the Mount menu and select Generic VCS from the Version Control menu.

3. On the New Wizard - Generic VCS Profile page, select CMS (OpenVMS) from the Version Control System Profile list.

4. You are now ready to specify your personal CMS Profile properties by typing or browsing for the following directory specifications.

Recommendation Use the Browse feature to ensure properly formed UNIX-style syntax.

Working Directory
This is where you would like to store remote files. It can be your user or project directory or another location of your choice. (The working directory must be at a level higher than the relative mount point.)

Important: The working directory and the CMS library can be located on different remote systems, but they must be accessible to each other.

Relative Mount Point
This is typically the root directory of your project directory. The directory specification of the mount point is additive, meaning the Working Directory specification is assumed.

Usage Note If you mount a CMS filesystem at a level higher than the Java package root, you can set a relative mount point so that the Java classes are handled properly.

(For more information about relative mount points, refer to NetBeans Core IDE Help: Using VCS Groups: Setting a Relative Mount Point).

CMS Library
This specifies the location of your existing (already configured) OpenVMS CMS library.


After selecting CMS (OpenVMS) as the VCS profile, you specify the profile properties.

Saving VCS Profiles
The capability of saving a Version Control System Profile is applicable to the advanced options. This feature does not preserve the directory specifications you specify.

6. Click Finish to close the wizard.

(Click Next only if you need to set advanced VCS properties or you want to customize CMS commands or variables. You can also do this after mounting the filesystem.)

The CMS filesystem appears in the Explorer as a separate tree with a VCS icon . You can now view the contents and status of the remote filesystem from your selected mount point.

The sample directory, including the Clock example
application, are under the CMS Filesystem mount point.

If the directory you specified for the relative mount point does not exist, the following message appears. The CMS module assumes that you have files to populate this directory in the CMS library.

If, in fact you made an error in the specification of the mount point, you can correct it now by right-clicking on the VCS icon and choosing the Customize command to open the Profile tab of the Customizer dialog box.

Note about [CMS] directories

CMS creates directories under the mount point of each CMS filesystem. These are hidden in the CMS filesystem but are visible in a remotely mounted filesystem or from an interactive OpenVMS session. [CMS] directories are used by CMS for temporary and context file storage. Never change the contents of this directory,

Next Step What You See in the Explorer