Running a collection

Because metadata may change, you should run collections on a regular basis so any changes are reflected in the repository. You may want to occasionally review the collection settings and make adjustments if necessary.

To run a collection

1. Do one of the following to run a collection:
   • Select the collection from the Entities view of the Metadata Analyzer window. Then, do one of the following:
     • • From the Tools menu, select Run Collection.

       • Right-click the entity and select Run Collection.

   • At a Command prompt, type the following, then press Enter:

     RunCollector <Metadata Server host name> <Metadata Server port number> <collection name>

   • This can be done manually or by using a scheduler program to start the collection.

     Note

     Use the machine name and port number of the Metadata Server you installed 

     DevEnterprise

     from and that houses the repository that you access.

     Before running a source, DDIO, CICS, IMS, or JCL collection, the Metadata Analyzer checks whether the source files exist. If any of the specified datasets are missing the collection is stopped and a FATAL error message is added to the Collector log. Dataset validation is not applicable to DB2 collections.

2. After the collection has run, check whether it ran successfully. The Collector run log is written to the console and to a text file located in a Logs directory on the machine on which the collection was run in the UserDataPath specified during the installation (which is available in the About dialog box). (Users who are remote to the server where the logs are located must use the UNC path which is \\<machine name>\DevEnterpriseLogs by default.
   You can also check whether it ran successfully by viewing the collection status. If a collection fails, the collection's Properties view will show Status property of Failed. Any entities collected before the failure are added to the repository, however, to collect entities that were not yet collected, the collection must be rerun and source must be downloaded (if this option was selected). First, take the steps necessary to resolve the failure, then rerun the collection. See the collection log for possible help in determining the cause of the collection failure.

To schedule a collection

Schedule a collection to run by using a program (such as Microsoft Task Scheduler) that invokes the following:

To schedule multiple collections to run, create a .BAT file with the following format. The call before each collection causes a collection start after the previous collection completes.

To delete all entities tied to a collection before the collection process starts

Technical Support might instruct you to use this process to correct a collection problem.

At a Command prompt, type the following, then press Enter: