Provides an address. host:port specifies the actual known address of the cache agent. useCA either can be used in the context of a known cache agent address port or turns on autolocate.

For example, if the default root folder path is c:\stardraw, then the command co -p "Administrator:Adiministrator@localhost:49201"/StarDraw -is -frp checks out the entire folder tree recursively to c:\stardraw.

If the path is overridden using the -rp command, such as co -p "Administrator:Adiministrator@localhost:49201"/StarDraw -is -rp "c:\temp" -frp, the entire stardraw folder tree gets checked out to c:\temp.

-frp does nothing if the entire folder tree is already relative to the root folder.

However, consider the StarDraw example. If the sub-folder Source Code default path is set to a mapped drive on a machine, for example, e:\\StarDraw or a UNC path (\\MicroFocus Build Server\) and you run the command line on a different machine from where the mapped drive or the UNC path is unreachable, the co command without -frp will throw an exception.

With -frp, the command will succeed, the Source Code folder and all descendant sub-folders are created relative to its parent, and the files in the folder hierarchy are checked out.

If -attached is not specified, its default value is always false.

-attached used in conjunction with -vl "label name" alters the fundamental behavior of the co command.

If -attached is false (the default), the files to be checked out are identified by the file(s) pattern specified by the co command, -vl specifies the revisions of the subset of files attached to the label.

If specified, the checkout is based on a committed change package, with the specified view member ID.

All files attached to that change package are checked out at the revisions they were at when the change package was committed. A change package checkout is a targeted sub-set of files checked out from history, at a revision timestamp equal to the change package commit time.

Exclude files or folders whose names match a pattern (or set of patterns). You can either specify the pattern inline -exclude <pattern> or you can specify a set of patterns in a file -exclude#patternFile.

A pattern can be an exact file or folder name or it may contain wildcard characters (e.g., '*.class').

To specify a folder name, precede the pattern name with a forward-slash (e.g., '/ bin'). A single pattern can be provided with -exclude. Alternatively, one or more patterns can be specified on separate lines of the given <pattern file> (prefixed with # ).

Pattern file names may be fully qualified with their path on the file system, e.g. #"c:\temp\patternfile.txt" or relative to the current folder e.g. #"patternfile.txt".

In all cases, the # symbol precedes the double quotes and pattern file names must be enclosed in double quotation marks "…".

In all cases, you must have a space between the # and the pattern file path. For example: -exclude # "c:/temp/exlcudefile.txt"

If the pattern matches a folder path, then all files in that folder path will be excluded.

Finally, a pattern may also be a fully or partially qualified path to a file in StarTeam without wildcards, e.g. /StarDraw/External Resources/StarDraw.ico

If the pattern matches an exact file name, then all instance of that file name, no matter where they are in the folder tree, will be excluded.

In this case, only the file that exactly matches the parent folder path will be excluded.

-f NCO is ignored if -filter is used.

-f NCD is ignored if -filter is used.

Additionally, with per folder status repository in use on the local machine, if files are checked out to empty working folders, empty .sbas folders will not be left on disk.

Be aware that the file statuses may never be known, even if you use the update-status command later. You can do a force check out without the -fs option to obtain current files with correct statuses.