The SCLM Developer Toolkit lets you view the contents of SCLM controlled libraries through the SCLM Developer Mode and SCLM Explorer Mode views. The SCLM Developer Mode provides a list of the members in the SCLM hierarchy where the list contains one node per SCLM type and that node shows members of all groups in the hierarchy. The SCLM Explorer Mode displays each individual group within the list. The Explorer mode shows a representation of the SCLM hierarchy whereas the Developer mode shows a view that hides some of the structure. The Developer mode is similar to the SCLM member lists in the host based interface. To switch between SCLM Explorer Mode and SCLM Developer Mode, right click in the current mode and select Switch View Mode or use the Switch View button on the SCLM View tool bar.
SCLM functions such as check out, check in, build and promote are available by using the context menus within the SCLM View.
When you edit a member that is checked out or browse a member that is not checked out, the default editor is used. The default editor is determined by the file name extension of the workstation file that is used to store the member when the file is downloaded to the workstation.
Language extensions must be defined to use several SCLM functions and it is recommended that you configure language extensions prior to using any SCLM functions. To set up default extensions for the languages defined in your SCLM projects, select Window->Preferences->Team->SCLM Preferences->Language Extension. Click New to create a new language extension pattern, or click Infer to automatically configure common extensions. To define the default editor associated with each extension, use the Eclipse editor preference pages.
If you are using the SCLM Developer Toolkit with Rational® Developer for z and writing COBOL or PL/I programs, you can use some of the local and remote syntax check functions of Rational Developer for z from within the SCLM Views.
The syntax check functions of Rational Developer for z are available only for members that have been checked out from SCLM.
To use Remote Syntax Check function or the associated Refresh Dependencies function, you must specify default compiler options and a job card using the RSE view. Create a filter to display the real data set that contains the group and types that hold the COBOL or PL/I source in your development group. Display your development group data sets within the RSE view and use the context menu to specify the job card and COBOL or PL/I compile options. If you are using DB2® or CICS®, you must have a level of the COBOL or PL/I compiler that supports the integrated preprocessor facilities. SCLM Developer Toolkit does not support use of separate preprocessor steps. Within the property page for the data set, you do not need to define SYSLIB data sets because SCLM determines these automatically. If your installation uses customized JCL procedures, get the necessary information about these procedures from your system administration personnel.
Remote Syntax Check performs a compile on the host and displays the errors in the Remote Errors view within Eclipse. It does this by uploading your checked out files to a work data set in MVS™ and then submits JCL that references the work data set and all of the files SCLM would normally access during the compile process. If you want to reduce the number of files that SCLM uploads during a remote syntax check, you should use the refresh dependencies function. The refresh dependencies function tells SCLM Developer Toolkit which files are actually used during the compilation. As files change within your system, you should occasionally refresh the dependencies to be sure that SCLM Developer Toolkit has current information.