RQMv4.0.2 Retire vs Lock
Currently the retired behaves like locked in such a way that a retired test case can be linked to a test plan and a TCER can be generated and executed. Isn't it retired? It will not surpprise me if this happens to a locked.
But by 'retired' I expect that the test case should not appear in the search result if not specified purposely, and it should not be allowed for new TCERs/execution unless it is unretired.
Am I understanding it properly?
Accepted answer
Yes, retired (see http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m5/topic/com.ibm.rational.test.qm.doc/topics/r_test_artifact_states.html) and locked (http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m5/topic/com.ibm.rational.test.qm.doc/topics/t_lock_test_artifact.html) test artifacts are both read-only. However, they are fully functional test artifacts, meaning they can used/referenced with/by other test artifacts. You can filter table views/pickers to only display non-retired test artifacts. If the retired test artifact is no longer required, you should delete it. Once deleted, you can restore it (RQM 4.0.5+) and all references to the deleted test artifact remain intact (see http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m5/topic/com.ibm.rational.test.qm.doc/topics/c_deleting_artifacts.html).