All the Harvest command line utilities write their results to a log file rather than to the screen. By default, the log file has the same name as the command with a .log file extension, and is written to the current working directory. The one exception is if you don't have permission to create or update files in the current working directory you don't get the log file.
To override the default, you would add the "-o" option or the "-oa" option and a file name. "-o" creates a new file, or overwrites the file if it exists, and "-oa" creates a new file or appends the result to the file if it already exists.
Here's where you can read more about "-o" and "-oa":
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/business-management/harvest-scm/13-0/command-reference/get-started-with-ca-harvest-scm-commands.htmlLet me know if this helps. :)
------------------------------
Melinda Skelton
------------------------------
Original Message:
Sent: 10-11-2019 05:53 PM
From: Patrice Sharp
Subject: Re: Is there a tool to migrate source code from CA harvest to TFS ?
Melinda,
once you have run the hsv command, how do you view the list?
Original Message:
Sent: 08-07-2018 12:21 PM
From: Melinda Skelton
Subject: Re: Is there a tool to migrate source code from CA harvest to TFS ?
I am not familiar with how TFS is structured, so don't have a recommendation for how best to do this. If keeping reports of the changes would be sufficient as a reference point, just checking out the latest versions from production and checking those into TFS would create a good "starting from here" point.
The other end of the spectrum would be to create a script that would check out from Harvest and check into TFS one version at a time. You could use the "hsv" command to create your list of all versions of all files in the production state, then just go through the list and do a Harvest check out - TFS check in for each row in the list.
Let me know if this helps.