When you work with a remote COBOL project, most of the processing such as program compilation and debugging takes place on the remote server. However, background parsing takes place on your local client machine and this architecture might result in parsing errors due to differences in local and remote environments.
These parsing errors do not affect the program build. However, you can remedy the problem depending on the nature of the parsing error. For example, if you encounter parsing errors when using copybooks, you can create a softlink to the copybook on the remote machine.
From a command line prompt on the remote machine do the following:
ln -s $COBDIR/cpylib/ cpylib
ln -s $COBDIR/cpylib/copybook.cpy copybook.cpy
This happens only to files that are already opened and are being edited in the COBOL Editor. The background parsing is not triggered (in all cases). Sometimes it shows errors that do not exist or hides existing ones.
No error will be displayed in the editor until background parser is triggered for CobolClass1 (when you edit CobolClass1 or reopen it).