KB Article 9298
2011/08/30

Close
X
Contact Tech Support

 Email Tech Support
 (250) 655-1766
 [7:30 - 5:00 PST]
Your Meeting ID will be Provided by a Rep.
Tech Support
Tech Support Home
Software Updates
Knowledge Base Search
Recent KB Articles
Product FAQs
Code Samples
Documentation
Tech Blog
System Requirements
Installation Instructions
Support Testimonials
Contact us to...
Create a Ticket
Request a Free Demo
Suggest a New Feature
Submit Feedback
Upload a Large File
Other Services
Software Training
Professional Services

What are the basic steps for using Docu-Mint?

Product: Docu-Mint 2.3 Type: Frequently Asked Question

While Docu-Mint has many options and nuances in how you set things up, in most cases the process for getting started with the tool is quite simple. Here is a quick outline of the steps (assuming you have already installed the software and have a valid license key).
 
Launch
To start Docu-Mint, add DM#LIB to your library list and run the STRDOC command. You should see the Work with System Libraries screen, listing the libraries you have available to work with.
 
Mark Libraries
In order to run any cross reference reports, Docu-Mint first needs to build its internal database of all the file and program relationship. To build those cross reference records, you need to first flag libraries for analysis, then run the analysis.
 
From the Work with System Libraries screen, use option 8 to mark your libraries.
 
Run the Analysis
After marking a library to be analyzed, you can run the analysis. You can do this with option 6 or the STRLIBANZ command.
 
We suggest you start with a library that has a few hundred objects and gauge how long it takes to run the analysis and how much of an impact the job has on your system. On a reasonably fast system the job should just take a few minutes for a medium sized library.  You can press F5 on the Work with System Libraries screen after submitting the analysis, and you should see the library showing a status of *ACTIVE until the analysis completes. When it is complete, the list  will show the last analyzed date and time.
 
In cases where an object doesn't have a hard-coded reference in your program, Docu-Mint will search for that item in your library list. So you can play with the library list of the job that runs the analysis to make sure you're getting the most useful and relevant results.
 
Check for Errors
When Docu-Mint analyzes your files and objects it will attempt to track down all the relevant source members and referenced objects, but if you have moved your source after the last time the object was compiled (for example) or the source has been deleted, you may get analysis errors. You can review these using option 10 from the Work with System Libraries screen.
 
You can attempt to resolve these errors by defining alternate source references - a list of alternate locations for Docu-Mint to look for source members when they are not found in the location expected by the object.
 
After defining a rule, you can re-run your analysis (it will only attempt to analyze objects not fully analyzed in the first pass, so the job should run quickly). You can keep repeating this process until your analysis is as complete as possible.
 
Review your Results!
After completing your analysis as cleanly as possible, use option 1 at the Work with System Libraries screen to work with the objects in the library. Most customers are looking for either the files used by a particular program or a list of the programs that use a particular file. These pieces of information are accessible with options 8 (Work Where Used) and 9 (Work with Used Objects) from the Work with Analyzed Objects screen.
 
With any of these commands or options, use the help text to learn more!

Rate This Article

Did this example help you to achieve your goal?
 Yes  No  Don't Know

Enter additional comments below.   If you want to hear back from us, include your contact information.

Email Address:
Comments:
Please enable JavaScript in order to rate this page.