.scan [-v][-i <ignorepattern>] baseline | checkpoint
.scan baselineStores a list of all files in the step's working directory. The system displays the list as a category in the BOM for the job. You can have multiple baseline commands in a job, but each one resets the list to the state of the step's working directory when the .baseline command executes. The final BOM displays only one baseline category.
.scan checkpointStores a list of all new, changed, and deleted files since the last .scan baseline or .scan checkpoint command in the job. As with the .scan baseline command, the system displays the list in the BOM, but each checkpoint command creates a new category in the BOM. You must issue a .scan baseline command before the first .scan checkpoint command in your job. A .scan checkpoint command that precedes a .scan baseline command is ignored.
The command has two options:
The -v, or verbose, option causes the system to record a copy of the change information in the job log.
The -i option allows the command to ignore directories that match the supplied pattern (a match at the beginning, end, or any directory portion of the path). Use this option to eliminate source control directories from the change listings. For example, you can use .scan -i CVS checkpoint to keep CVS directories out of the reports, or .scan -i .svn baseline to ignore Subversion directories. Note that the system still logs changes to these directories if you use the -v option, but they are not included in the BOM.
For more information on using these commands, see Using the Bill of Materials.