Log Files

The .cmd script can be run from Command Prompt, or can be executed simply by double clicking it. Each time a script is run, two outputs will be created:

1. A Log File
2. A Subset Report.

Logs are useful for checking that an Action has been performed successfully. They provide an overview of the steps performed as part of each Action, and the parameters from the Control Spreadsheet that informed these actions. If you subsequently edit your Control Spreadsheet, log files in your “output_archive” folder therefore provide a history of past Subset Actions.

The below example shows a Log File after the TABLES and GETKEYS action have been run:

Actions produce different logs. Information is therefore provided for each Log in the Knowledge Base articles relevant to each Action.

Actions produce different logs. Information is therefore provided for each Log in the Knowledge Base articles relevant to each Action.

If you execute the Action using the VIP Server Controller, the location of the Log file is specified in the “Log Directory” field of the “Run Flow” tab. The file is called log.log by default. The Log and Subset Report will be overwritten each time in the . The most recent Log will be appended to the log.log file indefinitely. You can copy Logs and Subset Reports to a new directory to prevent them being overwritten. Once a Subset job is exposed to the self-service web portal, Logs will be kept for each executed job.

If running Actions from the Command Line, the Log file will be created in an “Output” folder. The “Output” folder is created automatically by the automated Subset Action, and is in the directory specified by the -logDir parameter.

The “Output” folder stores only the latest log file. If you run multiple scripts using the same directory, the automation will automatically create an “output_archive” folder: