"Open Declaration" should actually open the declaration

When doing a "Open Declaration" on an externally defined procedure or field, RDi simply jumps to the line in the existing source where the procedure or field is imported. This is the easy way out and is not very helpful.

In the case of copy books, the IDE knows which copy book contains the declaration, and all the capabilties to open copy book and jump to the declaration are already part of RDi. Instead of showing the line where the copy book is imported, the IDE should open the copy book and jump to the the ACTUAL declaration.

The same could be done for fields declared in external files. Most user created objects on the system have the source code location as part of their service-related attributes. The command RTVOBJD is able to obtain the source location from the object (when available). It seems to me that RDi should be taking advantage of this. If the object definition contains a valid source location, it seems like the IDE should be smart enough to open a READ ONLY version of that source and jump to the line where the field is ACTUALLY declared. The IDE already retrieves the the fields that are defined in the various external files. It seems that grabbing the source code location for the object during that processing should be possible.

One issue is that SQL tables, views, and indexes will not have a source location defined in their service-level attributes. If an object's source is not found, but the SQL source is retreivable, you COULD give the user the option to retrieve the SQL. I would consider that an optional feature, but it is certainly a feasible work around for objects created using DDL.