Workaround: The lscm Command on z/OS Reports Local File System Out of Sync

Michael Valenta
Last Updated: May 24, 2012
Build Basis: Rational Team Concert 4.0

Summary

When using the lscm command on z/OS to perform operations that update the local file system, the command will fail and report that the local file system is out of sync. The scm command does not fail in the same way.

More Information

Using the lscm command on z/OS to perform operations that update the local file system results in a crash of the Java VM in the following situation: when a call to SocketChannel.close() is made from the lscm command to the background process (the SCM File System Daemon) that is used to manage the local data associated with a repository workspace.

There are two possible workarounds for this issue:

1. Start the scm daemon manually before running lscm. You can start the daemon by opening a command prompt and entering “scm daemon start”
2. Pipe the output of the ‘lscm’ script through ‘tee’. Piping the output to tee as a means of avoid this problem requires editing the ‘scm’ script that is packaged in the z/OS scmtools. Change the following line in the script:
   
   from

      exec "$JAVA_HOME/bin/java" -Dscm.show.own.errors=true -Xquickstart -Xmx512m -Dosgi.requiredJavaVersion=1.6       -jar "$PRGPATH/plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar" -os zos       -data "@noDefault" -configuration $WRKPATH/scmtools "$@"   

   to

      exec "$JAVA_HOME/bin/java" -Dscm.show.own.errors=true -Xquickstart -Xmx512m -Dosgi.requiredJavaVersion=1.6       -jar "$PRGPATH/plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar" -os zos       -data "@noDefault" -configuration $WRKPATH/scmtools "$@" | tee /dev/null      

Related Information

The following links point to related information:

• 205494: lscm on z/OS: after a share, there is the Local file system which is out of sync.