IBM WebSphere Developer for zSeries Version 6.0 Readme for Common Access Repository Manager WD/z Client Contents 1.0 Release notes 2.0 Limitations 3.0 Known issues -------------------------------------------------------------------------------- 1.0 Release notes -------------------------------------------------------------------------------- This is the technology preview release of the Common Access Repository Manager (CARMA) WD/z client. The CARMA WD/z client must be installed on top of Websphere Developer for zSeries (WD/z) version 6.0. The default installation directory for the WD/z CARMA client is: /CARMA All CARMA plugins are installed to this installation directory. No registry information is created by the installer. -------------------------------------------------------------------------------- 2.0 Limitations -------------------------------------------------------------------------------- - The installer does not support non-English languages. - The uninstaller may skip files if the workbench has not been shut down. - The PDS RAM currently supports extracting files, uploading content, and replacing files only for content with a record format of "Fixed Block". - The PDS RAM currently does not support the following tasks: Lock, Unlock, Check Out, and Check In. -------------------------------------------------------------------------------- 3.0 Known issues -------------------------------------------------------------------------------- - The refresh operation, if performed multiple times in quick sucession, may display duplicate content. Simply perform the refresh operation a single time to remove the duplicate content from the view. - If performing CARMA operations results in a "420" error, attempt to reconnect to the host. If you are unable to reconnect, it may be the case that the CARMA host has crashed. (Currently, if a CARMA host crashes, connected clients will not be automatically disconnected). - If the network fails during an active connection to a CARMA host, any attempt to execute CARMA operations will simply be ignored (will not produce errors on the client). To resolve this problem, cancel the operation, explicitly disconnect from the CARMA host, and reconnect to the host.