Transparency is a term we selected to describe the strongest feature of the mvToolbox. Simply put, wherever you are at in a work session, because of the many features of mvToolbox that allow you to "look outside the box", the boundaries that normally hedge you in have become transparent. A similar concept we use is Mobility.
In a work session, you are usually being presented with questions: what is done in a called subroutine, what does the data in a file look like, what is the dictionary format for an attribute, where have I seen this code before... With standard utilities you usually need to interrupt what you are currently doing to find the answer.
This generally means making notes for yourself so you can return to where you are at, exiting whatever you are doing, and searching for the answer. In mvToolbox, that is not necessary. From wherever you might be at, you can answer the question from that precise point. In a complex problem, significant amounts of time are wasted going in and out of the standard editor, re-selecting lists, and keeeping track of where you are. If the questions you are asking yourself come too fast, you can get totally lost.
- QSRCH multiple files from within the editor
- LX or LU to search the entire program and every INCLUDE, CALL, PERFORM, or EXECUTE that comes out of that program
- SF to sort a sample of a file
- LD to list a dictionary for a file
- POP to analyze what attributes are populated
Last Updated: 07/30/08
