Now you get to play with one of the most powerful and unique features of the Remote System Explorer - the Program Verifier. Before you compile your code on an iSeries, you can make certain that there are no errors by invoking the Program Verifier. The verifier checks for semantic (compile) errors on your workstation so that you can guarantee a clean compile on the iSeries. Think of the host cycles you'll save. It is especially handy when you are writing code but you are disconnected from an iSeries. You can do this because Remote System Explorer ported the parsing and checking code from the iSeries system compilers to the workstation. The iSeries Error List view lists the errors that are found and their severity, inserts the error messages directly into the source and helps you to navigate between the errors.
To invoke the verifier:
After a moment the verifier will display an iSeries Error List below the
Editor window.
The error list shows you:
Fixing errors
Next you will fix the errors in your source.
To fix an error in your source go to the error list:
You are automatically brought back into the Editor window to the line where
the error occurred. The error on line 365 is a typo. The
variable EMES should be EMESS. One good way of finding the correct name
is the content assist.
If the variable starts correctly the selection presented contains the correct name.
Another way to find the variable name is to use the Outline view and see
what variables are declared.
The next error is a RNF7030 as well.
Make the appropriate change.
The next error is actually RNF7018 but it is related to the one you just fixed and can be ignored. It shows the same line number, which is an indication that both errors are related.
Error RNF7515 is related to the first error you fixed. It has the same line number. You can ignore it. The only serious remaining error is RFN5178. This error is caused by a missing ENDSR.
You can use the Tab key to quickly move to the appropriate column.
All the non-informational errors are now fixed.
You can filter out messages according to these severities by using the
filter menu.
Saving the source member
Now before you loose any of your changes, it's a good idea to save them. Make sure the member is selected. You then verify the source again to make sure that all the errors are fixed.
You can save the member using one of these ways:
Changes are uploaded to the iSeries.
Everything should be ok. You should see only severity 0 messages. You are ready to compile the program.
You have verified your source and fixed any errors and now you are ready to begin Exercise 4.2: Compiling source remotely.
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.