02.05.2013 Views

Description - Mks.com

Description - Mks.com

Description - Mks.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

For details on development paths and variant sandboxes, see the si createsandbox reference<br />

page.<br />

--cpid=ID<br />

--changePackageId=ID<br />

identifies a change package that is notified of this action, for example, 1452. Note the following about<br />

using this option:<br />

❍ This option can only be specified if change packages are enabled.<br />

❍ You must specify this option if you have requested to obtain a lock and TrackLocks is enabled,<br />

and/or it is mandatory to specify a change package.<br />

❍ If it is not mandatory to specify a change package, or if no change package is applicable, you<br />

must specify --changePackageId=:none.<br />

❍ The next time you are prompted for a change package ID, the last used change package ID is<br />

displayed by default, if :none was specified or at least one change package was successfully<br />

updated from the last operation.<br />

--issueId=ID<br />

identifies an MKS Integrity Manager issue that is notified of this action. This option is another way of<br />

adding members to a change package. If you have an issue assigned to you that contains one open<br />

change package, you can specify the issue ID instead of the change package ID. See the Integrity<br />

Server Administration Guide or your administrator for details on using the Integrity Manager integration.<br />

-l<br />

--[no]lock<br />

controls whether to create locks on members.<br />

--[no|confirm]lockOnFreeze<br />

controls whether to lock the specified member even if it is frozen.<br />

--lockOnFreeze means always do it.<br />

--nolockOnFreeze means never do it.<br />

--confirmlockOnFreeze means always ask before doing it.<br />

--[no|confirm]merge<br />

controls whether to merge changes from the working file in your sandbox into the working file that will<br />

be created upon check out.<br />

--merge means always do it.<br />

--nomerge means never do it.<br />

--confirmmerge means always ask before doing it.<br />

Note: By default, Source Integrity prompts you for the type of merge (manual or automatic) to perform<br />

and what action to take if a conflict is encountered.<br />

--onLock=[confirm|branch|makewritable|branchconfirm|makewritableconfirm|cancel]<br />

controls whether to make the working file writable, create a branch, or cancel the operation.<br />

--onLock=confirm means always ask whether to make the working file writable, create a branch, or<br />

cancel the operation.<br />

69 of 457

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!