Closed as suggestion for future release.
Steps to reproduce: 1) Checkout files in test_vob (A Unix Vob) 2) Run cleartool lsco in the snapshot view cd'd into th vob C:\sue_snap\test_vob>cleartool lsco 21-Jun.18:00 sme checkout version "foo.txt" from \main\2 (reserved) 21-Jun.18:00 sme checkout version "new.txt" from \main\3 (reserved) 3) Run cleartool lsco -cview -avobs from the same location C:\sue_snap\test_vob>cleartool lsco -cview -avobs 21-Jun.17:51 sme checkout version "C:\sue_snap\persistent\co.txt" from \main\1 (reserved) NOTE: THE CHECKOUTS FOR THE UNIX VOB NO LONGER SHOW UP 4) CD into the view only and run ct lsco -cview -avobs - same results as step3 above: C:\sue_snap>ct lsco -cview -avobs 21-Jun.17:51 sme checkout version "C:\sue_snap\persistent\co.txt" from \main\1 (reserved) 5) Run ct lsco -avobs (NOTE: the checkouts from test_vob still do not appear) C:\sue_snap>ct lsco -avobs 18-Jun.11:50 sme checkout version "C:\sue_snap\persistent\test.txt" from \main\6 (reser ved) 21-Jun.17:51 sme checkout version "C:\sue_snap\persistent\co.txt" from \main\1 (reserve d)
Do not use lsco -cview -avobs. You needs to run cleartool lsco while cd'd in each Unix vob in the Windows snapshot view
One can cd in the unmounted VOB via a snapshot view. The UNIX Vobs behaved exactly in the same way as the Windows ones: if they were mounted, lsco -avobs was showing their checkouts, if not, they were skipped. Closing this defect since this works as intended.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following: