IBM Support What's New?

Invalid configuration location when launching CICS Explorer from shared network drive

Technote (troubleshooting)


When starting CICS Explorer, you see a Pop-up box that says 'Invalid configuration location'. The pop-up indicates that "a common reason is the file system or Runtime Environment does not support file locking for that location." You have CICS Explorer on a shared network drive so that multiple users can launch it from the remote drive.


This is the complete text within the pop-up titled 'Invalid configuration location':

Locking is not possible in the directory "<shared drive id>; \CICS_Explorer\configuration\org.eclipse.osgi". A common reason is the file system or Runtime Environment does not support file locking for that location. Please choose a different location, or disable file locking passing "-Dosgi.locking=none" as a VM agent.
<shared drive id>:\CICS_Explorer\configuration\org.eclipse.osgi\.manager\.fileTableLock
(Access is denied.)


Multi-user install on shared network drive is not configured correctly for Eclipse.

Diagnosing the problem

!ENTRY org.eclipse.osgi 4 0 2012-12-03 14:49:37.466
!MESSAGE Error reading configuration: T:
(Access is denied.)
!STACK 0 T:\CICS_Explorer\configuration\org.
eclipse.osgi\.manager\.fileTableLock (Access is denied.)
at Method)
at org.eclipse.core.runtime.internal.adaptor.Locker_JavaNio.lock
at org.eclipse.osgi.storagemanager.StorageManager.lock(StorageManager.
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.initFileManager
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.initialize
at org.eclipse.osgi.baseadaptor.BaseAdaptor.initializeStorage
at org.eclipse.osgi.framework.internal.core.Framework.initialize
at org.eclipse.osgi.framework.internal.core.Framework.<init>(Framework.
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
at sun.reflect.DelegatingMethodAccessorImpl.invoke
at java.lang.reflect.Method.invoke(
at org.eclipse.equinox.launcher.Main.invokeFramework(
at org.eclipse.equinox.launcher.Main.basicRun(

Resolving the problem

Review the CICS information center topic Installing on a remote network drive.

Review Eclipse documentation on Eclipse multi user installs.

Re-deploy the shared install by following these steps.

  1. Unzip a fresh copy of CICS Explorer into the install directory
  2. Run <install_directory>\cicsexplorer.exe -initialize (this initializes the basics of the configuration area without any real user-specific data)
  3. Make <install_directory> read only for all your end users

At this point each user that starts Explorer will get their own workspace in <userdir>\.cicsexplorer and their own configuration area in <userdir>\.eclipse\...

If you want the workspace or configuration area to be in a different place (for instance n:\.cicsexplorer_workspace and n:\.cicsexplorer_configuration) then you can add a -data option to your cicsexplorer.ini file as per usual, or -Dosgi.configuration.area=... to the cicsexplorer.ini file *after* the -vmargs line. You would need to edit the cicsexplorer.ini file before you made the install directory read-only!

Product Alias/Synonym

CICS/TS CICS TS CICS Transaction Server

Document information

More support for: CICS Transaction Server

Software version: 4.2

Operating system(s): z/OS

Reference #: 1620316

Modified date: 2013-03-02