Highlighted
Trusted Contributor.
Trusted Contributor.
1435 views

2 VC for Eclipse questions on remote environment

Jump to solution

Hi all,

1) Is it possible to change the Listing directory created by Visual COBOL on the Remote environnement?
2) Because we are able to regenerate all the application programs on the remote target server, we use a directives configuration file.

I've tried to set it in the Project Settings -> COBOL -> Additional directives 
USE"visual_cobol_directives.cfg"
But in this case, an red error mark appears in the COBOL Text editor (with message COBCH0189S Directives file visual_cobol_directives.cfg not found). This error is not fatal for the compilation step. 

Thanks in advance.

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: 2 VC for Eclipse questions on remote environment

Jump to solution

1) You can use the LISTPATH directive to set a different location for the Listing directory.  This will then override the directory named 'Listing' where the list files will be put by default if you just click the 'Generate Listing File' checkbox.

The LISTPATH directive takes a path name, either relative or absolute to the directory you want the listing files ot be placed in.  

2) The USE(configname.cfg) directive will tell the checker which directives file to use for additional directives.  This can obviously be a relative or absolute path.

When working with remote projects you have to remember that while the compilation will be occuring on the remote machine, any background parsing in the editor will be occuring on the local Windows machine.  This means that any files referenced in the USE directive on the remote Linux/Unix won't be found from the Windows machine.

Ideally, any directives would be added into the respective 'additional directives' boxes where the IDEs know about them and we can correctly call the compiler on both the LInux and WIndows platforms.

View solution in original post

0 Likes
2 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: 2 VC for Eclipse questions on remote environment

Jump to solution

1) You can use the LISTPATH directive to set a different location for the Listing directory.  This will then override the directory named 'Listing' where the list files will be put by default if you just click the 'Generate Listing File' checkbox.

The LISTPATH directive takes a path name, either relative or absolute to the directory you want the listing files ot be placed in.  

2) The USE(configname.cfg) directive will tell the checker which directives file to use for additional directives.  This can obviously be a relative or absolute path.

When working with remote projects you have to remember that while the compilation will be occuring on the remote machine, any background parsing in the editor will be occuring on the local Windows machine.  This means that any files referenced in the USE directive on the remote Linux/Unix won't be found from the Windows machine.

Ideally, any directives would be added into the respective 'additional directives' boxes where the IDEs know about them and we can correctly call the compiler on both the LInux and WIndows platforms.

View solution in original post

0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

RE: 2 VC for Eclipse questions on remote environment

Jump to solution

Thanks for yours answers...  

I will use your solution for the first answer.

The second one will be discussed with our customer because of theirs constraints:

- global compilation process,

- multiple developers...

may be an enhancement?

Franck.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.