WDSc Verify issue

[taherte]

(This was mentioned in another thread I started on another topic but may have been overlooked due to the subject, so I am starting a new thread.)

I am trying to use the Verify function in WDSc 7.0.0 and don't understand why the verifier finds errors but the program compiles clean and runs properly. The errors are RNF7030's and the fields are display file and physical/logical file fields. What is puzzling is that the error isn't for every field in the display file or in the physical/logical file. How can that be? Is this a caching issue?

[Scott Klement]

Can you tell us how to reproduce (or try to reproduce) the error on our own machines?

[jtaylor]

Have you tried Source=>Verify (Prompt)... and marked "Refresh cache" under Cache?

[taherte]

I'm not sure how to reproduce the problem because I don't know what combination of things is causing it. I tried Verify on a different program and it worked fine.

I tried Source=>Verify (Prompt) and selected "Refresh Cache". Verify produced the following results:

• RNF0401 An error occurred during communication with the host
  RNF2120 External descriptions for file xxxxxxx (display file) not found

As expected, it also appears that every field in the display file is not found. The physical file file field that it didn't like before did not display as an error in the error list.

Just before running Verify Connection to see if there is a communication problem I ran Verify again with refresh cache without making any other changes and it ran clean. I then ran a regular Verify and it was clean.

How often do I have to refresh the cache if I want to use Verify instead of Compile? What is it caching?

[Scott Klement]

I'm curious about the "RNF0401 An error occurred during communication with the host" error.

I suspect that's causing the other errors. It's using the cached copy because it can't communicate with the host.

[jtaylor]

A Google search for "RNF0401 " returned this:
http://archive.midrange.com/wdsci-l/.../msg00182.html

[jtaylor]

In the prior thread (http://forums.systeminetwork.com/isn...ad.php?t=89761), you thought that it was working and then it wasn't. Were you using Verify against the same source member?

[taherte]

All of the errors I am getting are on the same source member. I checked the DDS and verified that it doesn't use INDARA or ROLLxxx keywords.

We've got a user running an IT developed web query that is taking a lot of system resources. I noticed that it was taking longer than usual to compile a program so I suspect that may be what caused the communication issue the first time I tried to run Verify with refresh cache selected. I presume the original errors I was getting was because it was using outdated cached files.

Under normal circumstances, does Verify use the actual files on the host system or does it normally use cached files? Which files does it cache? When does it do the caching?

[jtaylor]

AFAIK, Verify downloads the data to cache the first time it needs it, and then then only refreshes cache if "Refresh cache" is selected. I assume if the cache was gone, it would download the data on the next Verify.

Did you check out the midrange.com link I posted? Does that describe your problem?

[taherte]

The link you provided does not seem to apply to the problem because my display file does not contain the INDARA or ROLLxxx keywords.

I'll be more careful about using the refresh cache option. Thanks for pointing out where that is.