When you request a local syntax check for a remote COBOL
or PL/I file, Developer for System z® searches the remote system for all dependencies (such as copybooks
and include files) and caches these files in a temporary location
in your workspace. The list of files is also stored as a property
of the remote file. This search and temporary caching enables Developer
for System z to complete
a syntax check without requiring you to add the dependent files to
your MVS™ subproject.
Before checking syntax locally, you may need to set local
build options. You need to do this action only once and only if you
want to override the default values.
Note: This procedure outlines
the default behavior for local syntax check. You can override this
default behavior and request that Developer for System z look only in your subproject for
dependent files. To override this default behavior, select the Syntax
Check option in the Preferences window. See the related
tasks for more information.
To do a local syntax check of a remote
file from the LPEX editor, follow these steps:
- Select the file that contains the code you want to check.
- Right-click and select Open With > System z
LPEX Editor.
- In the content area of the editor, right-click and select Syntax
Check - Local or Save and Syntax Check - Local if
the file has been changed. The Check Dependencies
window opens, prompting you to refresh dependencies for the remote
file.
- Optional: If you have reason to believe that
the dependencies have changed since the last syntax check, click Refresh
dependencies and then perform a syntax check. Otherwise,
click Syntax check only. To review
the list of dependencies before proceeding, click Dependent
files. The window expands to show the list of dependent
files and the date and time of the last refresh.
Note: The Dependent
files button is present only if you have previously requested
a refresh dependencies for the file.
- Click OK. The local
compiler is started to perform the syntax check.
Note: Unless you
select Save and Syntax Check - Local, your
file is not automatically saved before initiating the syntax check.
When
the syntax check is completed, any errors are displayed in the Remote
Errors List. If there are no errors, control is returned to you and
you can continue working.
The following error messages represent some common problems
with local syntax check of remote files. These messages may appear
in the Refresh Dependencies Problems window. Click the
Details button
to display the specific error message.
- JES subsystem is not connected. Connect to the subsystem
and retry the operation. This message may appear if the JES
subsystem is not connected.
- The submitted job has ended with a JCL error. Check the
build properties and retry the operation. This message may
appear if, for example, you have specified a PDS in the SYSLIB that
does not exist.