Version 3.1
This file contains information that became available too late for inclusion
in the publications or the online help. This file also contains important
support information.
1.0 Syntax Check
2.0 Host Session related problems
3.0 Server Element Spirit Options
1.0 Syntax Check
- Some dependency information is stored as part of
cached SCLM project information. When cached project information is
refreshed, you might need to refresh the dependencies for members that
are checked out.
- SCLM Developer Toolkit saves checked out and cached
files in an Eclipse project called SCLMConfigProject. If you are
experiencing compilation errors that do not appear to reflect the current
contents of members that are not checked out, clear the download cache using
the Syntax Check context menu item and refresh the dependencies for the
member being syntax checked. If this does not fix the problem, you might
have obsolete files in the SCLMConfigProject project. You can either check
in all of your checked out files and delete that project, or you can
manually delete any files you know are not checked out.
2.0 Host Session related problems
- RSE users: (Rational Developer for System z only) If
communications with the host appear to stop or unexpected file in use
messages occur, it might be necessary to manually stop some of the host
processes that are running on behalf of the SCLM Developer Toolkit user. To
do this:
- If possible, first use the Remove Host session option available
from the project node in the package explorer view or the location node in the
SCLM view.
- If this does not fix the problem, disconnect entirely from RSE.
- If the problem reoccurs after reconnecting to RSE, use the SCLM
preferences page to deselect the Reuse ISPF session.
- If this still does not correct the problem, you may need to manually
cancel the processes on the z/OS host. This can be done through a system
monitor program such as the PS display of SDSF.
- In order to be able to cancel host processes (Rational Developer for System z only),
the SCLM Developer Toolkit user must have authority to use the kill command to
cancel his or her Unix processes. If the kill commands fail, an attempt is made to
issue a CANCEL command using SDSF.
3.0 Server Element Spirit Options
A new feature is available that may reduce server-side memory consumption. This feature is
the concept of a "spirit" element. A spirit element is an element which has been deleted from
the server cache so that the host no longer keeps track of it, while it remains on the client.
The element on the client is marked as "spirited", so that if a command needs to be called on
the element, the spirited element is recreated on the server.
TThis is available in SCLMDT over RSE with customizations done in the Rational Developer
for System z rsed.envvars configuration file.
Rational Developer for System z must be at the latest service level. Being at the latest
service level will also pre-define the parameters needed to (de)activate this feature.
This feature is set with the following parameters in rsed.envvars:
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DDSTORE_SPIRIT_ON=true"
_RSE_JAVAOPTS="$_RSE_JAVAOPTS -DSPIRIT_EXPIRY_TIME=6"
If -DDSTORE_SPIRIT_ON is true, this feature will be used by the resources that support it.
If it is false, the feature will not be used and the other option has no effect.
The -DSPIRIT_EXPIRY_TIME parameter is a number that indicates, in seconds, how long the
server waits after an element is queued for spiriting before actually doing so.
(C) Copyright IBM Corporation 2007. All Rights Reserved.