It's all about the answers!

Ask a question

[closed] RTC 4.0.4 zOS SCM CLI - why will share not work?


Donald Poulin (2249118107) | asked Dec 20 '13, 12:52 p.m.
edited Oct 11 '17, 10:10 a.m. by David Lafreniere (4.7k7)

I created a zOS omvs shell script to use the rtc command line interface to create new repository workspace, a  component , load the workspace , create a new folder and files under the folder and share out the new project. So far I have note been able to successfully share that new project (folder). I believe i need to share it out to the component before I can do a deliver. Here are the steps

1. lscm login
2. create repository workspace
3. create component
4. add component to workspace
5. load repository workspace
6. create new folder and files within loaded workspace area
7. share out the new folder

I have repeated this a few times and have not be able to do a successful share. Any help would be greatly appreciated. I have been using this reference as a guide - http://www.ibm.com/developerworks/rational/library/rational-team-concert-command-line-reference/


Here is the share error - and there is no other process running at the time this ran. Each time I execute and get an error I end up wth a "hanging" STC that needs to be cancelled. At the time of this specific run all "hanging" STCs had been cancelled and I had shutdown and restarted the bfagent.

com.ibm.team.filesystem.client.CopyFileAreaLockedByOtherProcess: Status INFO: com.ibm.team.filesystem.client code=0 Unable to lock file /u/hfsload/.jazz5/.jazzlock null
    at com.ibm.team.filesystem.client.internal.core.SharingMetadata2.ensureExclusiveCFAAccess(SharingMetadata2.java:3218)
    at com.ibm.team.filesystem.client.internal.core.SharingMetadata2.<init>(SharingMetadata2.java:1704)
    at com.ibm.team.filesystem.client.internal.core.SharingMetadataFactory.getSharingMetadata(SharingMetadataFactory.java:45)
    at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaManager.createSharingMetadata(CopyFileAreaManager.java:167)
    at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaManager.createCopyFileAreas(CopyFileAreaManager.java:235)
    at com.ibm.team.filesystem.client.internal.SharingManager.register(SharingManager.java:1306)
    at com.ibm.team.filesystem.rcp.core.internal.rest.FilesystemRestClient.postRegisterSandboxes(FilesystemRestClient.java:1919)
    at com.ibm.team.filesystem.rcp.core.internal.rest.FilesystemRestClient.postShare(FilesystemRestClient.java:792)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at com.ibm.team.filesystem.client.daemon.JSONHandler.handle(JSONHandler.java:322)
    at com.ibm.team.filesystem.client.internal.http.HttpConnection.readNextRequest(HttpConnection.java:628)
    at com.ibm.team.filesystem.client.internal.http.HttpConnection$1.run(HttpConnection.java:470)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
    at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.decodeExceptions(MarshallerUtil.java:328)
    at com.ibm.team.repository.common.serialize.internal.JSONDeserializer.deserializeErrorObj(JSONDeserializer.java:955)
    at com.ibm.team.filesystem.client.internal.marshalling.ExceptionHandlingJSONDeserializer.deserializeErrorObj(ExceptionHandlingJSONDeserializer.java:128)
    at com.ibm.team.repository.common.serialize.internal.JSONDeserializer.deserializeException(JSONDeserializer.java:933)
    at com.ibm.team.filesystem.client.internal.marshalling.EObjectJSONDeserializer.deserializeError(EObjectJSONDeserializer.java:71)
    at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeRequest(RestInvocationHandler.java:267)
    at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeAndReturnResult(RestInvocationHandler.java:221)
    at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invokeInternal(RestInvocationHandler.java:368)
    at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invoke(RestInvocationHandler.java:311)
    at com.sun.proxy.$Proxy1.postShare(Unknown Source)
    at com.ibm.team.filesystem.cli.client.internal.sharecommand.ShareCmd.run(ShareCmd.java:188)
    at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)
    at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:535)
    at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:349)
    at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:125)
    at com.ibm.team.filesystem.cli.client.internal.daemon.CommandLineClient.handleRequest(CommandLineClient.java:186)
    at com.ibm.team.filesystem.client.internal.http.ProtocolSwitchingHttpHandler.handle(ProtocolSwitchingHttpHandler.java:46)
    at com.ibm.team.filesystem.client.internal.http.HttpConnection.readNextRequest(HttpConnection.java:628)
    at com.ibm.team.filesystem.client.internal.http.HttpConnection$1.run(HttpConnection.java:470)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Problem running 'share':
Share attempt failed.



Comments
Shashikant Padur commented Dec 23 '13, 3:43 a.m. | edited Dec 24 '13, 1:09 a.m.
JAZZ DEVELOPER

When you run the share command, are you within the sandbox (that is where you have loaded the repository workspace)? If not, specify the sandbox location with the -d/--directory option to the share command.

The question has been closed for the following reason: "Problem is not reproducible or outdated" by daviddl Oct 11 '17, 10:10 a.m.