OS/2 Professional Developers Kit 1992 November/Disc01/Disc01.mdf/runnable/ibmwf/help/dde3wf.hlp

OS/2 Help File | 1992-08-27 | 142.7 KB | 6,023 lines

ΓòÉΓòÉΓòÉ 1. Special Notices ΓòÉΓòÉΓòÉ

References in this help to IBM products, programs, or services do not imply
that IBM intends to make these available in all countries in which IBM
operates.

Any reference to an IBM licensed program in this help is not intended to state
or imply that only IBM's licensed program may be used. Any functionally
equivalent product, program, or service that does not infringe any of IBM's
intellectual property rights may be used instead of the IBM product, program,
or service.

Evaluation and verification of operation in conjunction with other products,
except those expressly designated by IBM, is the user's responsibility.

IBM may have patents or pending patent applications covering subject matter in
this help. The furnishing of this help does not give you any license to these
patents.

The following terms, denoted by an asterisk (*) in this help, are trademarks of
the IBM Corporation in the United States and/or other countries:

 C/2
 C Set/2
 IBM
 OS/2
 Operating System/2
 Presentation Manager
 WorkFrame/2.

 The following terms used in this publication are trademarks of Microsoft
 Corporation. They are denoted by a double asterisk (**) when they appear in
 the text.

 Microsoft
 Windows.

 This help contains examples of data and reports used in daily business
 operations. To illustrate them as completely as possible, the examples include
 the names of individuals, companies, brands, and products. All of these names
 are fictitious and any similarity to the names and addresses used by an actual
 business enterprise is entirely coincidental.


ΓòÉΓòÉΓòÉ 2. IBM WorkFrame/2* Concepts ΓòÉΓòÉΓòÉ

The IBM WorkFrame/2* program (also referred to as the WorkFrame/2*) provides a
programming environment that lets you:

 o Manage a group of files as a project .
 o Associate a language profile with your project to describe the compiler,
   linker, debugger, and make utility to use.
 o Integrate your own tools.
 o Use a mouse to directly manipulate items.
 o Customize the environment to suit your own needs.

 These features help to streamline the development cycle under the WorkFrame/2*
 product.


ΓòÉΓòÉΓòÉ 2.1. Projects ΓòÉΓòÉΓòÉ

Instead of working with individual files and directories, the WorkFrame/2*
product uses projects.

A project consists of a collection of related files within a directory and its
characteristics. These characteristics include a set of options for compiling,
linking, making, debugging, and running your program, as well as a language
profile.

To begin actual development using the WorkFrame/2* product, the first thing you
must do is create a project. Use the Project Control option from the File
pulldown to display the Project Control window. Use the New pushbutton to
create a new project.

You can create two types of projects: base and composite. A base project is
generally used to group the set of files used to build a single executable
module or DLL. A composite project is simply a collection of other base and/or
composite projects that allow you to build more complex applications involving
multiple executable modules or DLLs.

You can create several projects with the same project directory and target
file, and vary other characteristics to tailor each project to a different
stage of the program's development.  For example, you can associate a different
set of options to each project to create a debugging version, a test version,
and a finished version of the same program.


ΓòÉΓòÉΓòÉ 2.2. Language Profiles ΓòÉΓòÉΓòÉ

Each base project you develop must have an associated language profile. The
language profile defines a number of things, including:

 o The compiler, linker, debugger, and make utility to be used with the
   project.
 o The files (DLLs) that provide options for the above tools.
 o The default argument string used when invoking the make and debug tools.
 o The include and library search paths.

 Language profiles can be identified by the .PRF file extension.

 Use the Language profile management option from the Tools pulldown to create
 and modify your language profiles.

 The WorkFrame/2* product provides a default language profile that you can
 modify for use with most compilers. Some products may provide their own
 language profiles.


ΓòÉΓòÉΓòÉ 2.3. The Development Cycle ΓòÉΓòÉΓòÉ

This section presents an overview of how you use the WorkFrame/2* to develop an
application.

Notes

 o Before you begin creating applications, you should first decide how your
   existing files and directories will map into WorkFrame/2* projects, both
   base and composite.
 o To perform the steps outlined in this section, you must have a compiler,
   linker, debugger, and make utility installed. You must also have a language
   profile that specifies each of these tools.

  1. The first step is to create a project. If the Project Control window is
     not already displayed, select Project Control from the File pulldown.
     Click on New from the Project Control window, and specify the
     characteristics you want to associate with the project.

  2. When you have specified the project characteristics, click on OK in the
     Create window. The new project name appears in the Project Control window.
     Then click on Cancel to close the New Project window.

  3. To open or display your new project, select the project name and then
     click on Open, or double-click on the project name. If the project is a
     base project, a window appears with a list of the project files.  If the
     project is a composite project, the window contains a list of the
     subprojects that make up the composite project. The following steps assume
     the project is a base project.

  4. If your project already contains some files, you can proceed to the next
     step. If you want to create a new source file, click on New from the
     project window. You are prompted for a file name, and the editor is
     invoked automatically. Once you have saved and closed your file, click on
     Refresh to refresh the project window (the window is not automatically
     refreshed after every action is completed).

  5. Use the Actions pulldown to create your target file. You can select Build
     or Make to create the file in one step, or use Compile and Link to compile
     and link separately. A monitor window displays the messages and results of
     the action.

     If you are compiling, linking, or building, select the file or files in
     the base project window before performing the action.

     Note:  The invocation of the Make action requires a make file.  If a make
            file does not exist for the project and you want to create one,
            select Make File Creation from the Tools pulldown. You can specify
            the actions you want the make file to perform, and the compile and
            link options you want to use. If you do not specify any options
            here, the make file uses the options associated with the project.

  6. Run your application by selecting Run from the Actions pulldown, or by
     double-clicking on the executable file in the project window.

  7. Use Debug from the Actions pulldown to invoke the debugger and debug your
     target file if it is an executable program.

     Note:  If your compiler or linker has options to generate debug
     information, you must set them on to be able to debug your program if it
     is an executable file.

  8. If the application is a tool, you can then use the Configure pulldown to
     add it to the Tools pulldown. You can drag the project from the Project
     Control window to the New Tool window to initialize some of the settings.

  9. When the tool or application is no longer needed, you can delete it from
     the Tools list, and then delete the project itself from the Project
     Control window.


ΓòÉΓòÉΓòÉ 2.4. Customizing the Environment ΓòÉΓòÉΓòÉ

You can change the WorkFrame/2* appearance to fit your own needs.  Use your
mouse or keyboard to change the size, shape, and positions of both the main
window and title bar and of the secondary windows.

Use the Configure pulldown menu to further customize your environment. You can
specify the editor you want to use, the tools you want in your Tools list, and
the sessions to include in the Switch List.

You can change the client area to a different color or to a bitmap, and set the
colors and fonts for the different list boxes.

You can also customize the sound and animation features, how you want tools and
monitor windows to appear, and when your window positions are saved.

You can save your customized changes with the Save Settings pulldown item.


ΓòÉΓòÉΓòÉ 2.5. Integrating Tools ΓòÉΓòÉΓòÉ

Use the Tools option from the Configure pulldown to add or delete tools in the
Tools pulldown.

You can also use this option to change the characteristics assigned to existing
tools.


ΓòÉΓòÉΓòÉ 2.6. Hints on Using Your Mouse ΓòÉΓòÉΓòÉ

The WorkFrame/2* interface offers some features that are ideal for mouse users.
In most windows, you can double-click on an item to perform actions. For
example, double-click

 o On a source file to invoke the editor.
 o On an executable to run the program.
 o On an object file within the LIB utility window to show details of the
   object module.

 You can use dragging to copy and delete files, or to copy the characteristics
 of a project or tool to another project or tool.  For example, you can delete
 a file by dragging it to the Waste icon.

 You can also change the size of a window by dragging its borders, or move the
 window by dragging the title bar.


ΓòÉΓòÉΓòÉ 3. Action Log ΓòÉΓòÉΓòÉ

Use the Action Log to see the events that have happened during this session.

A typical message starts with the name of the project, file, or tool, and
states the event that happened to it and the time and date of the event.

This window cannot be closed while the WorkFrame/2* session is open. The log is
not saved between sessions.

To save memory, print the log or erase it occasionally.  You can also save the
log contents to the clipboard or to a file.

Note:  Saving the contents does not erase the log.


ΓòÉΓòÉΓòÉ <hidden> Action Log ΓòÉΓòÉΓòÉ

This list box shows the events that have happened during this session. You can
see the processes that have finished and their return codes.

A typical message starts with the name of the project, file, or tool, and
states the event that happened to it and the time and date of the event.


ΓòÉΓòÉΓòÉ <hidden> Print ΓòÉΓòÉΓòÉ

Use the Print pushbutton to print the log.


ΓòÉΓòÉΓòÉ <hidden> Save ΓòÉΓòÉΓòÉ

Use the Save pushbutton to save the log to a file or to the clipboard. The log
contents are not erased from the Action Log window.


ΓòÉΓòÉΓòÉ <hidden> Erase ΓòÉΓòÉΓòÉ

Use the Erase pushbutton to erase the log.


ΓòÉΓòÉΓòÉ 4. File ΓòÉΓòÉΓòÉ

Use this pulldown to:

 o Create, change, open, or delete projects in the Project Control window.

 o Manipulate files and create temporary projects in the File Control window.

 o Copy projects or files from one window to another.

 o Save settings of the WorkFrame/2* profile and/or window positions.

 o Open the  Deletion Window to delete items.


ΓòÉΓòÉΓòÉ <hidden> Project Control ΓòÉΓòÉΓòÉ

Select this pulldown item to open the Project Control window.

Use the Project Control window to create, change, open, or delete projects.


ΓòÉΓòÉΓòÉ 4.1. Project Control ΓòÉΓòÉΓòÉ

This window displays all the existing base, composite, and temporary projects.

You can create new projects and open, change, or delete existing projects.

The directory shown at the top of this window is the installation directory.
All project control (.PRJ) files are stored in this directory. Press F8 to view
the control project file names in the list box. Pressing F8 a second time
returns you to the list of project descriptions.

To create a project, select the New pushbutton.

To open one or more projects, select the projects from the Project list list
box and click on the Open pushbutton, or double-click on the titles with mouse
button 1. A window displays for each project that is open.

To change one or more projects, select the projects from the Project list list
box and click on the Change pushbutton. A Change window displays for each
project that is selected.

To delete one or more projects, select the projects from the Project list list
box and click on the Delete pushbutton, or drag them to the Deletion window.


ΓòÉΓòÉΓòÉ 4.1.1. Project List ΓòÉΓòÉΓòÉ

This list box displays the names of all existing base, composite, and temporary
projects.

Press F8 to view the project control (.PRJ) file names in the list box.
Pressing F8 a second time returns you to the list of project descriptions.

Use this list box to select the projects you want to perform the action on. You
can select up to 500 projects to copy or delete.

To select a project, click on the project with mouse button 1.  To select all
projects in the list box, double-click with mouse button 1 on the
installationdirectory name above the list box.

To deselect a project, click on the highlighted project with mouse button 1.
To deselect all currently selected projects, double-click with mouse button 2
on the installation directory name.


ΓòÉΓòÉΓòÉ 4.1.2. Open ΓòÉΓòÉΓòÉ

Use the Open pushbutton to open the selected projects.

Opening a base project displays a window listing the project directory, the
language profile name, and the files that match the file mask specified in the
project control file.

Opening a composite project displays a window listing its subprojects.

Up to 15 base and composite projects can be open at the same time.


ΓòÉΓòÉΓòÉ 4.1.3. New ΓòÉΓòÉΓòÉ

Use the New pushbutton to create a project.


ΓòÉΓòÉΓòÉ 4.1.4. Delete ΓòÉΓòÉΓòÉ

Use the Delete pushbutton to delete the currently selected projects.

You will be prompted to confirm the deletion.


ΓòÉΓòÉΓòÉ 4.1.5. Change ΓòÉΓòÉΓòÉ

Use the Change pushbutton to change the properties of the currently selected
projects. If the project is already open, close it first.

If the project is already open, you must close it before changing the project.


ΓòÉΓòÉΓòÉ 4.2. New Project ΓòÉΓòÉΓòÉ

This is the first of two windows you use to specify the information for a new
project.

To create a new project:

  1. Enter a title for the new project in the Project description field.

  2. Enter the name of the project control file in the Project file name field.

  3. Select the type of project you want to create: a base project or a
     composite project.

  4. Click on More to continue to the next window.

 Note:  If you are creating a project that will have characteristics similar to
        a project that already exists, you can select the existing project in
        the Project control window and drag it to the New project  window. The
        fields in the New project window and the following window will then
        have the same values as those in the existing project. Note that you
        will probably need to change some of these values, such as the Project
        description field.

 The project control files, which contain the information about the projects,
 are located in the installation directory.


ΓòÉΓòÉΓòÉ 4.2.1. Project Description ΓòÉΓòÉΓòÉ

Use this entry field to enter a title for the project.

The title identifies the project in window headings, messages, pulldowns, and
list boxes. Make it meaningful and unique.

It can be up to 100 bytes long.

You can drag a description from the Project Control window to this entry field.


ΓòÉΓòÉΓòÉ 4.2.2. Project File Name ΓòÉΓòÉΓòÉ

Use this entry field to enter a file name for the project control file.

Enter a file name without an extension. Do not specify a path.

The WorkFrame/2* appends the extension .PRJ and places the file in the
installation directory.


ΓòÉΓòÉΓòÉ 4.2.3. Project Type ΓòÉΓòÉΓòÉ

Use these radio buttons to indicate whether you want to create a base project
or a composite project.


ΓòÉΓòÉΓòÉ 4.2.4. More ΓòÉΓòÉΓòÉ

Use the More pushbutton to continue to the next window after you have completed
the fields in this window.

The next window contains entry fields for more information about the project.


ΓòÉΓòÉΓòÉ 4.3. Create a Base Project ΓòÉΓòÉΓòÉ

Use this window to create a base project.

To create a base project:

  1. Enter the complete path of the directory to contain the project's files.

     If the directory does not already exist, the WorkFrame/2* product can
     create it for you.

  2. Enter the name of the file to be made by your project in the Target file
     name entry field.

  3. Enter the name of the make file to be used by the project. The make file
     does not need to exist yet.

  4. Use the following pushbuttons to display windows where you can specify the
     corresponding options for this project:

    o Compile options
    o Link options
    o Run options
    o Debug options
    o Make options.

     You do not have to specify these options now. You can set the options
     later using the Options pulldown. You can also specify Link and Compile
     options from the Create make file window.

     If you do not specify any options, the defaults are used.

  5. Select a language profile from the Languages combination box.

  6. Click on the OK pushbutton to create the project.

     The project will appear in the Project control window.


ΓòÉΓòÉΓòÉ 4.3.1. OK ΓòÉΓòÉΓòÉ

Use the OK pushbutton to create the project and return to the New Project
window.


ΓòÉΓòÉΓòÉ 4.3.2. Directory ΓòÉΓòÉΓòÉ

Use this entry field to specify the directory to contain the files of this
project. Type the full path name of the directory.

If the directory does not exist, a message appears and asks if you want to
create the directory. You can have the WorkFrame/2* product create the
directory for you, create the directory yourself, or return to the window and
change the directory name.


ΓòÉΓòÉΓòÉ 4.3.3. Target File Name ΓòÉΓòÉΓòÉ

Use this entry field to specify the file that your project will build.
Typically, this is either an executable file or a dynamic link library.

Do not specify a path. This file will be created and maintained in the project
directory.

The file you name is used when you select the Run, Debug, Build,  or Make from
the Actions pulldown.


ΓòÉΓòÉΓòÉ 4.3.4. Make File Name ΓòÉΓòÉΓòÉ

Use this entry field to specify the name of the make file for this project. Do
not specify the file path.

This make file will be created and maintained in the project directory.

Note:  You only need the make file if you want to perform the Make action.
However, you must specify a name in this entry field.

If the make file already exists, it must be in the project directory. It will
be used when you select Make from the Actions pulldown.

If the file does not exist, you can later use the Create make file window to
define the file's contents.


ΓòÉΓòÉΓòÉ 4.3.5. File Mask ΓòÉΓòÉΓòÉ

Use this entry field to specify the default file masks when your project is
opened.

You can use the wildcard characters such as * or ? to list files with similar
characteristics. For example:

 *.c displays all files in the project directory that have an extension of .c.

 file?.c displays all files with the name file followed by one character and
 the extension .c.

 *.? displays all files in the project directory that have an extension of one
 character or less, for example, include.h or code.


ΓòÉΓòÉΓòÉ 4.3.6. Languages ΓòÉΓòÉΓòÉ

Use this combination box to select the language profile you want to associate
with the project.

To see the list of profiles you can choose from, click on the arrow beside the
box with mouse button 1.  Then click on the language profile you want with
mouse button 1.


ΓòÉΓòÉΓòÉ 4.4. Create a Composite Project ΓòÉΓòÉΓòÉ

Use this window to create a composite project.

To create a composite project:

  1. Specify the base and/or composite projects you want to be part of this
     composite project. Add them in the order that you want them to be made.
     There are two ways of adding projects:

    o Enter the name of the project control file (for example, project1.prj )
      in the Subproject to add field. Then click on the Add pushbutton.

    o Select projects from the Project Control window and drag them to the
      Subproject list.

  2. To delete a subproject from the list, select the subproject and click on
     the Delete pushbutton.

  3. In the Subproject list, click on the project that creates the target file
     you want to be used when Run or Debug is selected from the Actions
     pulldown. That project appears as the Run/debug project at the top of this
     window.

  4. Click on OK to create the new composite project.


ΓòÉΓòÉΓòÉ 4.4.1. Subproject To Add ΓòÉΓòÉΓòÉ

Use this entry field to enter the name of a project you want to add to the list
of subprojects.

The name you enter is the name of the project control (.PRJ) file, not the
project description.

Then click on the Add pushbutton to add the project.


ΓòÉΓòÉΓòÉ 4.4.2. Add ΓòÉΓòÉΓòÉ

Use this pushbutton to add the project shown in the Subproject to add entry
field.


ΓòÉΓòÉΓòÉ 4.4.3. Delete ΓòÉΓòÉΓòÉ

Use this pushbutton to delete the selected subprojects shown in the list box.


ΓòÉΓòÉΓòÉ 4.4.4. Subproject List ΓòÉΓòÉΓòÉ

This list box shows you which subprojects you have chosen to be part of the
composite project. Up to 500 items can be listed.

You can drag a project from the Project Control window to this list box.


ΓòÉΓòÉΓòÉ 4.5. Change a Base Project ΓòÉΓòÉΓòÉ

Use this window to change the characteristics of a project.

Note:  You cannot change the project type from base to composite without first
       deleting the project and the creating it again.

 To change a base project:

  1. Change any of the fields as required.

     Note:  If you change the Project directory, the project's files are not
            copied to it automatically.

  2. Press any of the following pushbuttons to specify the corresponding
     default options for this project:

    o Compile options
    o Link options
    o Run options
    o Debug options
    o Make options.

     You don't have to specify these options now. You can set them later using
     the items under the Options pulldown.

     The Link and Compile options may also be specified using the Create make
     file window.

  3. Select OK to change the project and remove the window.


ΓòÉΓòÉΓòÉ 4.5.1. Change ΓòÉΓòÉΓòÉ

Use the Change pushbutton to change the properties of the project.


ΓòÉΓòÉΓòÉ 4.6. Change a Composite Project ΓòÉΓòÉΓòÉ

Use this window to change the characteristics of a composite project.

To change the project's description, change the text in the Project description
field.

To change the project used for running and debugging, select the project's name
in the Subprojects list.

You can add or delete projects in the same manner indicated for the Create a
composite project window.

To delete a subproject from the list, select the subproject and press the
Delete pushbutton.

Select Change to save the changed composite project.


ΓòÉΓòÉΓòÉ 4.6.1. Subprojects ΓòÉΓòÉΓòÉ

This list box shows you which subprojects make up the composite project.

Up to 500 items can be listed in this list box.


ΓòÉΓòÉΓòÉ 4.7. Base Project ΓòÉΓòÉΓòÉ

This window shows you:

 o The name of your project (in the window's title bar).

 o The directory containing your project.

 o The files matching the File mask in the directory.

 o The language profile associated with the project.

 When a project is opened, it becomes the Current project.

 Use this window to add new files to the project, edit files, and run
 executable files. You can also copy files to another window by selecting their
 file names in the  Files list box and selecting Copy from the File pulldown.
 Double-click on the directory path to select and deselect all the files.

 To edit a file, double-click with mouse button 1 on its name in the list box.
 Or select the file name and select the Process pushbutton. To edit a group of
 files, select their names and then select the Process pushbutton or
 double-click on one of them.

 Note:  The number of selected files that will be edited depends on the
        capabilities of the current editor and its invocation string.

 To run a file, double-click with mouse button 1 on its name in the list box.
 Or select the file name and select the Process pushbutton. If more than one
 item is selected, the first selected item will be run. You can only run files
 containing executable code. You will be prompted for any input parameters. The
 program will be run from the project directory. The program type is determined
 from the header of the executable file.

 To create a new file for the project, select New and enter the file name in
 the action window.

 To update the Files list box, select the Refresh pushbutton. You can update
 the list box if you have added or deleted files or selected actions which
 create new files.


ΓòÉΓòÉΓòÉ 4.7.1. Files ΓòÉΓòÉΓòÉ

This list box shows the files, matching the file masks, that make up the
project.


ΓòÉΓòÉΓòÉ <hidden> Directory ΓòÉΓòÉΓòÉ

The directory which contains the files that make up the project.


ΓòÉΓòÉΓòÉ 4.7.2. Process ΓòÉΓòÉΓòÉ

If the selected file is an executable file, select this pushbutton to run the
file.

If the selected file is a file containing source code or text, select this
pushbutton to edit the file.


ΓòÉΓòÉΓòÉ 4.7.3. Refresh ΓòÉΓòÉΓòÉ

Use the Refresh pushbutton to update the Files list box.


ΓòÉΓòÉΓòÉ 4.7.4. New ΓòÉΓòÉΓòÉ

Use the New pushbutton to invoke the editor to create a new file.


ΓòÉΓòÉΓòÉ 4.7.5. Delete ΓòÉΓòÉΓòÉ

Use the Delete pushbutton to delete the selected files.


ΓòÉΓòÉΓòÉ 4.8. Composite Project ΓòÉΓòÉΓòÉ

This window displays all the subprojects which are part of the composite
project.

Use this window to

 o Open a project window
 o Make one or more of the subprojects which make up the composite project.

 To open a subproject, select it and select the Open pushbutton. Or, just
 double click with mouse button 1.

 To make the project, select Make from the Actions pulldown.

 When you have finished using this window, select the Close pushbutton.


ΓòÉΓòÉΓòÉ 4.8.1. Open ΓòÉΓòÉΓòÉ

Use the Open pushbutton to open the selected project window.


ΓòÉΓòÉΓòÉ <hidden> File Control ΓòÉΓòÉΓòÉ

Select this pulldown item to display the File control window.


ΓòÉΓòÉΓòÉ 4.9. File Control ΓòÉΓòÉΓòÉ

Use this window to:

 o Edit, copy, or delete files
 o Run an executable file by double-clicking on its name.
 o Open a temporary project.

 To perform an action, you need to display the appropriate files in the Files
 list box:

  1. Note the path indicated next to the Directory field.

     If this directory is not the directory you want, use the Directories list
     box to move to the correct directory. The Directory string shows what
     directory you are in. If this string becomes too long to fit in the field,
     only its first and last parts are shown.

  2. As you move from directory to directory, the Files list box refreshes to
     show what files in the directory match the File mask.

     To change the mask, type over the present mask and press Enter. The file
     mask is saved for the next WorkFrame/2* session.

 Editing files

 You can edit any nonexecutable file.

 To edit a file, select its name and select the Process pushbutton. Or, just
 double-click on its name.

 To edit a group of files, select their names and select the Process
 pushbutton.

 Note:  The number of selected files that will be edited depends on the
        capabilities of the current editor and its invocation string.

 Copying and deleting files

 You can copy files to and from the Files listbox by selecting the files in the
 source list box an dragging them to the target list box.

 To delete files, select them and then select the Delete pushbutton.

 Running files

 You can only run files containing executable code.

 To run a file, select its name and select the Process pushbutton. Or, just
 double-click on its name.


ΓòÉΓòÉΓòÉ 4.9.1. Directories ΓòÉΓòÉΓòÉ

This list box lets you move from directory to directory by selecting the
directory name.

The list of files can be refreshed by clicking on the current drive.


ΓòÉΓòÉΓòÉ 4.9.2. Files ΓòÉΓòÉΓòÉ

This list box shows you which files in the directory match the file mask.

Editing files

You can edit any nonexecutable file.

To edit a file, select its name and select the Process pushbutton. Or, just
double-click on its name.

To edit a group of files, select their names and select the Process pushbutton.

Note:  The number of selected files that will be edited depends on the
       capabilities of the current editor and its invocation string.

 Copying and deleting files

 You can copy files to and from the Files listbox by selecting the files in the
 source list box an dragging them to the target list box.

 To delete files, select them and then select the Delete pushbutton.

 Running files

 You can only run files containing executable code.

 To run a file, select its name and select the Process pushbutton. Or, just
 double-click on its name.

 The list of files can be refreshed by clicking on the current drive in the
 Directories list box.


ΓòÉΓòÉΓòÉ 4.9.3. File Mask ΓòÉΓòÉΓòÉ

Use this entry field to specify the files to be displayed in the Files list
box.

You can enter wildcards such as * or ? to list files with similar
characteristics. For example:

 *.c will display all files in the project directory which have an extension of
 c.

 *.? will display all files in the project directory that have a one letter
 extension such as include.h or code.c.

 More than one file mask can be entered.


ΓòÉΓòÉΓòÉ 4.9.4. Temporary Project ΓòÉΓòÉΓòÉ

Use this pushbutton to create a temporary project containing the files
specified in the File control window.

Temporary projects provide a quick way of creating a project. Suppose you had a
directory which contained several files that you wanted to become part of a new
project. Here's how you could create the new project.

  1. Using the File Control window, move to the directory containing the files.

  2. Select the Temporary Project

     The newly created temporary project would show up in the Project Control
     window.

  3. Select New in the Project Control window to open the New Project window.

  4. Drag the name of the temporary project from the Project Control window to
     the New Project window.

     The controls in the New Project

  5. Change the Project description and Project file name to identify the new
     project. You can also change the other options as required.

  6. Select OK

 You can also use a temporary project to manipulate the files in a directory as
 if they were part of a permanent project.

 If you select a file with the extension OBJ, LIB, DLL, or EXE, that file
 becomes the target file.

 If the file did not have any of these extensions, the target file will have
 the same name as the first selected file but the extension EXE.

 The make file will have the same name as the target file but with the
 extension MAK.

 If more than one file is selected, the name of the first selected file is used
 for the naming convention.

 If no files were selected, the target file is named TEMP.EXE and the make file
 is named MAKEFILE.

 The language profile is the one specified as the Default language in the
 Preferences window.


ΓòÉΓòÉΓòÉ 4.9.5. Process ΓòÉΓòÉΓòÉ

Use the Process pushbutton to edit the selected files that contain
non-executable code.

Note:  The number of selected files that will be edited depends on the
       capabilities of the current editor and its invocation string.

 If the first selected file is executable code, it will be run.


ΓòÉΓòÉΓòÉ 4.10. Edit New File ΓòÉΓòÉΓòÉ

Use this window to invoke the editor to edit a new file or to edit existing
files.

To create a file:

  1. Enter its name. If you do not specify a path, it is created from the
     directory specified in the window.

  2. Press Enter or select OK to edit the file with editor.

 To edit an existing file, enter its path and name (for example, C:\WORK\C.FIL)
 and press Enter or select OK.


ΓòÉΓòÉΓòÉ 4.10.1. File Name ΓòÉΓòÉΓòÉ

Enter the name of the file you want to create or edit.


ΓòÉΓòÉΓòÉ 4.10.2. OK ΓòÉΓòÉΓòÉ

Use the OK pushbutton to create the new project file or edit the file if it
already exists.

To create a file:

  1. Enter its name. If you do not specify a path, it is created from the
     directory specified in the window.

  2. Press Enter or select OK to edit the file with editor.

 To edit an existing file, enter its path and name (for example, C:\WORK\C.FIL)
 and press Enter or select OK.


ΓòÉΓòÉΓòÉ 4.11. Copy ΓòÉΓòÉΓòÉ

Select this pulldown item to display the Copy window.

Use the Copy window to copy files from the current project to any other project
that has been opened.

You can copy items whether you are using a keyboard or a mouse.

To copy files from one project to another:

  1. Select the files you want to copy.

     Note:  You can use the list box control techniques available with the
            WorkFrame/2* to select and deselect which files you want to copy.

  2. Select Copy from the File pulldown.

  3. Select the window (or windows) listed in the Projects list box you want to
     copy the files to.

  4. Select the OK pushbutton.


ΓòÉΓòÉΓòÉ 4.12. Copy ΓòÉΓòÉΓòÉ

Use the Copy window to copy files from the current project to any other project
that has been opened.

You can copy items whether you are using a keyboard or a mouse.

To copy files from one project to another:

  1. Select the files you want to copy.

     Note:  You can use the list box control techniques available with the
            WorkFrame/2* to select and deselect which files you want to copy.

  2. Select Copy from the File pulldown.

  3. Select the window (or windows) listed in the Projects list box you want to
     copy the files to.

  4. Select the OK pushbutton.


ΓòÉΓòÉΓòÉ 4.12.1. Target Windows ΓòÉΓòÉΓòÉ

Use this list box to select the window you want to copy the files to.

You can only copy to windows that have been opened.


ΓòÉΓòÉΓòÉ 4.12.2. OK ΓòÉΓòÉΓòÉ

Use the OK pushbutton to copy the previously selected files to the selected
window.


ΓòÉΓòÉΓòÉ 4.13. Save Settings ΓòÉΓòÉΓòÉ

Use Save settings to save the WorkFrame/2*'s profile information if you have
modified it. When Profile is selected, the following information is saved:

 o Fonts and colors for list box text

 o Background colors and bitmaps

 o Last project worked on

 o Current editor

 o Tools you added

 o Settings in the Preferences window.

 When Window Positions is selected, the layout of the windows at the time of
 closing is recorded. That way, when the WorkFrame/2* product is started the
 next time it looks much like the way when it was closed.

 When Both is selected, all the above information is saved.


ΓòÉΓòÉΓòÉ 4.13.1. Profile ΓòÉΓòÉΓòÉ

Use Save settings to save the WorkFrame/2*'s profile information if you have
modified it. When Profile is selected, the following information is saved:

 o Fonts and colors for list box text

 o Background colors and bitmaps

 o Last project worked on

 o Current editor

 o Tools you added

 o Settings in the Preferences window.

 When Window Positions is selected, the layout of the windows at the time of
 closing is recorded. That way, when the WorkFrame/2* product is started the
 next time it looks much like the way when it was closed.

 When Both is selected, all the above information is saved.


ΓòÉΓòÉΓòÉ 4.13.2. Window Positions ΓòÉΓòÉΓòÉ

Use Save settings to save the WorkFrame/2*'s profile information if you have
modified it. When Profile is selected, the following information is saved:

 o Fonts and colors for list box text

 o Background colors and bitmaps

 o Last project worked on

 o Current editor

 o Tools you added

 o Settings in the Preferences window.

 When Window Positions is selected, the layout of the windows at the time of
 closing is recorded. That way, when the WorkFrame/2* product is started the
 next time it looks much like the way when it was closed.

 When Both is selected, all the above information is saved.


ΓòÉΓòÉΓòÉ 4.13.3. Both ΓòÉΓòÉΓòÉ

Use Save settings to save the WorkFrame/2*'s profile information if you have
modified it. When Profile is selected, the following information is saved:

 o Fonts and colors for list box text

 o Background colors and bitmaps

 o Last project worked on

 o Current editor

 o Tools you added

 o Settings in the Preferences window.

 When Window Positions is selected, the layout of the windows at the time of
 closing is recorded. That way, when the WorkFrame/2* product is started the
 next time it looks much like the way when it was closed.

 When Both is selected, all the above information is saved.


ΓòÉΓòÉΓòÉ 4.14. Deletion window ΓòÉΓòÉΓòÉ

Select this pulldown item to display the Deletion Window window.


ΓòÉΓòÉΓòÉ 4.15. Deletion window ΓòÉΓòÉΓòÉ

Use the Deletion window to delete projects, project files, library object
modules, and tools. You can delete single items or groups of items.

Note:  You need a mouse to use this window. To delete items with the keyboard,
       select the Delete pushbutton in the window showing those items.

 To delete items:

  1. Select the items you want to delete.

     Note:  You can use the list box control techniques available with the
            WorkFrame/2* product.

  2. Drag the items from the list box to the Deletion Window (or to the icon if
     the window is minimized).

  3. Release mouse button 2.

     You will be asked to confirm that you want the items deleted.

 The Animation and Sound that accompany the Delete action can be toggled on and
 off from the Preferences window.


ΓòÉΓòÉΓòÉ 4.16. Confirm Deletion ΓòÉΓòÉΓòÉ

Use this window to verify you the deletion of all the items shown.

Note:  When a project or a tool is deleted, it is removed from the list of
       items known to the WorkFrame/2*. The files comprising the project or
       tool remain in their directories but are not known to the WorkFrame/2*.

 Select the OK pushbutton to delete all the items shown in the window.

 If you decide not to delete some of the selected items, deselect those items.
 Then select the OK pushbutton to delete the selected files.

 Select Cancel to return without deleting any items.


ΓòÉΓòÉΓòÉ 4.16.1. Items ΓòÉΓòÉΓòÉ

Use this list box to select the items you want to delete.

Note:  When a project or a tool is deleted, it is removed from the list of
       items known to the WorkFrame/2*. The files comprising the project or
       tool remain in their directories but are not known to the WorkFrame/2*.

 Select the OK pushbutton to delete all the items shown in the window.

 If you decide not to delete some of the selected items, deselect those items.


ΓòÉΓòÉΓòÉ 4.16.2. OK ΓòÉΓòÉΓòÉ

Use the OK pushbutton to confirm deleting the items in the list box.


ΓòÉΓòÉΓòÉ 5. Options ΓòÉΓòÉΓòÉ

Use the Options pulldown to specify the options used when you want to:

 o Compile

 o Link

 o Make

 o Debug

 o Run
 your project.

 The options you choose only apply to the currently selected base project and
 are stored in the project's control file. Therefore, you can use a different
 set of options for each project.

 You cannot specify options for a composite project.

 In some windows, you may have the opportunity to use substitution variables.


ΓòÉΓòÉΓòÉ 5.1. Compile Options ΓòÉΓòÉΓòÉ

Select this item to open the Compile options window. Use that window to select
which of the compiler's options you will use to compile or build the source
files of the current project.

The options you choose only apply to the currently selected base project and
are stored in the project's control file. Therefore, you can use a different
set of options for each project.

You cannot specify options for a composite project.

The name of the executable file of the compiler and the dynamic link library
used to specify its options are defined in the language profile.


ΓòÉΓòÉΓòÉ 5.2. Link Options ΓòÉΓòÉΓòÉ

Select this item to open the Link options window.

Use that window to select which of the linker's options you will use to link or
build the objects modules of the current project.

The options you choose only apply to the currently selected base project and
are stored in the project's control file. Therefore, you can use a different
set of options for each project.

You cannot specify options for a composite project.

The name of the executable file of the linker and the dynamic link library used
to specify its options are defined in the language profile.


ΓòÉΓòÉΓòÉ 5.3. Make Options ΓòÉΓòÉΓòÉ

Select this item to open the Make options window.

Use that window to select the options used with the make utility.

The options you choose only apply to the currently selected base project and
are stored in the project's control file. Therefore, you can use a different
set of options for each project.

You cannot specify options for a composite project.

The name of the executable file of the make utility and the dynamic link
library used to specify its options are defined in the language profile.


ΓòÉΓòÉΓòÉ 5.4. Run Options ΓòÉΓòÉΓòÉ

Select this item to open the Run options window.

Use that window to select the options to be used when the target file is run.

The options you choose only apply to the currently selected base project and
are stored in the project's control file. Therefore, you can use a different
set of options for each project.

You cannot specify options for a composite project.


ΓòÉΓòÉΓòÉ 5.5. Debug Options ΓòÉΓòÉΓòÉ

Select this item to open the Debug options window.

Use that window to select the options used when running the language debugger.

The options you choose only apply to the currently selected base project and
are stored in the project's control file. Therefore, you can use a different
set of options for each project.

You cannot specify options for a composite project.

The name of the executable file of the debugger and the dynamic link library
used to specify its options are defined in the language profile.


ΓòÉΓòÉΓòÉ 6. Actions ΓòÉΓòÉΓòÉ

Use the Actions pulldown to:

 Compile

 Link

 Build
 the selected files of the current project.

 You can also use it to:

 Make

 Debug and

 Run
 the current project.

 For information on a specific action, select its name in the list above.


ΓòÉΓòÉΓòÉ 6.1. Compile ΓòÉΓòÉΓòÉ

Select this action to invoke the compiler for all the selected source files of
the current project. If you specified options using the Compile options window,
these options will be used by the compiler.

A monitor window displays output from the compiler.

The name of the executable file of the compiler and the dynamic link library
used to specify its options are defined in the language profile.

Each file is compiled individually.

Note:  If the compile options are set to invoke the linker as well as the
       compiler, the object files will be linked as well.


ΓòÉΓòÉΓòÉ 6.2. Link ΓòÉΓòÉΓòÉ

Select this action to invoke the linker for all the selected source files of
the current project. If you specified options using the Link options window,
these options will be used by the linker.

A monitor window displays output from the linker.

The executable file produced by the linker will have the name selected for the
targetfile of the project.

The name of the executable file of the linker and the dynamic link library used
to specify its options are defined in the language profile.


ΓòÉΓòÉΓòÉ 6.3. Build ΓòÉΓòÉΓòÉ

Select this action to build your program.

All selected files in the current project window and the project's compile and
link options will be used to build the target file.

The build utility starts the compiler, linker, and resource compiler to build
the project.

The project is built in the following manner:

  1. Source code files (identified by the list of file extensions defined as
     valid source in the language profile) are compiled into object code.

     Note:  Be sure that the compile options cause the compiler to create an
            object file.

  2. Resource script files (with the extension .rc) are compiled by the
     resource compiler into a resource file (with the extension .res).

  3. The object code is linked to create an executable file.

  4. The resource files (those with the extension  .res). are bound to the
     executable file.


ΓòÉΓòÉΓòÉ 6.4. Make ΓòÉΓòÉΓòÉ

Select this action to run the make process for the current project. If a make
file does not yet exist for the project, use the Create make file tool to build
one.

If the project is a base project, a monitor window displays so you can watch
the progress of the make process.

If the project is a composite project, then the Composite Make window displays.

The name of the executable file of the make utility and the dynamic link
library used to specify its options are defined in the language profile.


ΓòÉΓòÉΓòÉ 6.5. Composite Make ΓòÉΓòÉΓòÉ

Use this window to use the make utility to make a composite project.

To make a composite project:

  1. Select the base projects, from the Base project list that you want to be
     made.

     Since all the base projects are shown as selected when this window is
     opened, just deselect those projects that you do not want to be made. You
     can also choose to make the subprojects in groups. For example, you could
     select the first two subprojects, make them, and then make the next three,
     and so on.

  2. To make each project one at a time, select the Sequential execution check
     box.

     Note:  If Sequential execution is selected, the projects in the Base
            project list will be made in the order they are displayed.

     To reorder the Base project list, close the Composite Make window and the
     project's window, and select Change from the Project Control window.

  3. If you want the make utility to continue even if an error occurs, select
     the Continue if error check box.

  4. As each base project is being made, a monitor window shows the output of
     each process. When a process finishes successfully, its monitor window
     remains open unless you select the Close monitor windows check box.

  5. Select the Start pushbutton to run the make utility.

     Note:  If the Minimize monitor check box in the Preferences window was
            selected, the monitors display as icons.

  6. To stop the composite make process, select the Stop item from the
     Composite Make window or system menu pulldown.


ΓòÉΓòÉΓòÉ 6.5.1. Base Projects ΓòÉΓòÉΓòÉ

Use this list box to select which base projects will be made.

The list box shows all the base projects which make up the composite project.

Since all the base projects are shown as selected when this window is opened,
just deselect those projects that you do not want to be made.


ΓòÉΓòÉΓòÉ 6.5.2. Sequential Execution ΓòÉΓòÉΓòÉ

If this check box is selected, each selected base project will be made, one at
a time, in the order they are shown in the list box. Monitor windows will be
opened and closed sequentially.

If this check box is not selected, the make utility will be started for each
selected project without waiting for the previous make process to finish.


ΓòÉΓòÉΓòÉ 6.5.3. Continue If Error ΓòÉΓòÉΓòÉ

If this check box is selected, then non-zero return codes will be ignored and
the next make process will be started.

If this check box is not selected then the composite make process will stop
after the first non-zero return code.

This option is only available if Sequential execution is specified.


ΓòÉΓòÉΓòÉ 6.5.4. Close Monitor Windows ΓòÉΓòÉΓòÉ

If this check box is selected, each monitor window will be removed if the make
process associated with it finished with a return code of zero. for that
project. Monitor windows associated with a make action which ended with a
non-zero return code are not closed.


ΓòÉΓòÉΓòÉ 6.5.5. Completion Status ΓòÉΓòÉΓòÉ

Use this list box to see the status of the make processes.


ΓòÉΓòÉΓòÉ 6.5.6. Start ΓòÉΓòÉΓòÉ

Use this pushbutton to start making the selected base projects.


ΓòÉΓòÉΓòÉ 6.5.7. Stop ΓòÉΓòÉΓòÉ

Use this item to halt the making of base projects. All make processes will be
stopped if possible and an abnormal termination may occur.


ΓòÉΓòÉΓòÉ 6.6. Debug ΓòÉΓòÉΓòÉ

Select this action to debug the target file of the current project.

The target file of the current project is used as the source for the language
debugger. The options selected with the Debug options window are used when the
debugger is started .

The name of the executable file of the debugger and the dynamic link library
used to specify its options are defined in the language profile.


ΓòÉΓòÉΓòÉ 6.7. Run ΓòÉΓòÉΓòÉ

Select this action to run the target file of the current project.

The options selected with the Run options window are used when the target file
is run.


ΓòÉΓòÉΓòÉ 7. Configure ΓòÉΓòÉΓòÉ

Use this pulldown to tailor the WorkFrame/2* window. You can customize the
following items:

 o Configure Editor

   Use this option to switch among editors or change how the editor is started.

 o Tools

   You can add or delete tools available under the Tools pulldown. And you can
   change attributes assigned to existing tools.

 o Switch list pulldown

   Tailor the list of sessions in the Switch list pulldown.

 o Background

   Select which color or bitmap you want to display in the client area of the
   WorkFrame/2* window.

 o List box fonts and colors

   Choose the colors and fonts of list boxes used in the WorkFrame/2* window.

 o Preferences

   Use this option to tailor how the WorkFrame/2* window works.


ΓòÉΓòÉΓòÉ <hidden> Editor ΓòÉΓòÉΓòÉ

Select this item to display the Configure Editor window.


ΓòÉΓòÉΓòÉ 7.1. Configure Editor ΓòÉΓòÉΓòÉ

Use this window to switch to another editor or change the way it is started.

To switch to another editor:

  1. Change the path and file name in the Current editor field to correspond to
     the new editor.

  2. Enter the parameters you want to invoke the editor in the Editor
     invocation string field.

  3. If you want to send compiler errors to the editor, check the Send compiler
     errors check box.

  4. Select the OK pushbutton.

 To change the invocation string:

  1. Enter the new string in the Editor invocation string entry field.

  2. Select OK.


ΓòÉΓòÉΓòÉ 7.1.1. Current Editor ΓòÉΓòÉΓòÉ

Use this entry field to specify the path and file name of the editor you want
to use with the WorkFrame/2* window.

If you do not specify a path, the WorkFrame/2* product will attempt to find the
editor by using the PATH environment variable.


ΓòÉΓòÉΓòÉ 7.1.2. Editor invocation string ΓòÉΓòÉΓòÉ

Use this entry field to pass parameters to the editor. You can use substitution
variables.


ΓòÉΓòÉΓòÉ 7.1.3. Send Compiler Errors ΓòÉΓòÉΓòÉ

Select the Send compiler errors check box to let the editor receive error
messages from the compiler. You can use this option if all the following are
true:

 o The editor was started from the Monitor list box.

 o The editor is capable of receiving the messages. (Check the documentation
   that came with your editor.)

 o The compiler can send messages to the editor. (Check the documentation that
   came with your compiler.)


ΓòÉΓòÉΓòÉ 7.1.4. OK ΓòÉΓòÉΓòÉ

Select OK to confirm the changes and remove the window.


ΓòÉΓòÉΓòÉ <hidden> Tools ΓòÉΓòÉΓòÉ

Select this item to display the Configure Tools window.

Use this window to add or delete tools from the Tools pulldown. You can also
change the configuration of existing tools.

Note:  You can also add tools from a command line using the Addtool program
       supplied with the WorkFrame/2* product. Addtool lets you control where
       the tool appears in the Tools pulldown. (View the WorkFrame/2* online
       reference for more information.)


ΓòÉΓòÉΓòÉ 7.2. Configure Tools ΓòÉΓòÉΓòÉ

Use this window to add or delete tools from the Tools pulldown. You can also
change the configuration of existing tools.

Note:  You can also add tools from a command line using the Addtool program
       supplied with the WorkFrame/2* product. Addtool lets you control where
       the tool appears in the Tools pulldown. (View the WorkFrame/2* online
       reference for more information.)

 To add a tool, select the New pushbutton to display a window that lets you
 specify information about the tool.

 Note:  If the tool you want to add has similar attributes to one of the tools
        already in the Current Tools list, select the similar tool before
        selecting New. The controls in the New Tool and Change A Tool windows
        will be updated with the existing tool's attributes. If more than one
        tool is selected, the first selected tool is used.

 When you add a tool, an accelerator key is automatically assigned to it (if it
 is one of the first ten tools in the pulldown). Once you have added the tool,
 view the Tools pulldown to see which accelerator key is associated with it.

 To change tools:

  1. Select the tool you want to change from the list box. If more than one
     tool is selected, the first selected tool is used.

  2. Select the Change pushbutton to display a window that lets you change
     information about the tool.

 To delete one or more tools:

  1. Select the tools you want to delete from the list box.

  2. Select the Delete pushbutton.

 Unless you select Save settings - Profile from the File pulldown before
 closing the WorkFrame/2* window, the changes only apply to this session.

 The maximum number of tools that can be configured is 100.


ΓòÉΓòÉΓòÉ 7.2.1. Current Tools ΓòÉΓòÉΓòÉ

The Current tools list box lists the tools you have added to the WorkFrame/2*
product. Select those you want to change or delete.

If more than one tool is selected, the first selected tool is used.

The maximum number of tools that can be configured is 100.


ΓòÉΓòÉΓòÉ 7.2.2. OK ΓòÉΓòÉΓòÉ

Select OK to make the changes to the Current Tools list.

Unless you select Save settings - Profile or Save settings - Both from the File
pulldown before closing the WorkFrame/2* window, the changes only apply to this
session.


ΓòÉΓòÉΓòÉ 7.2.3. New ΓòÉΓòÉΓòÉ

To add a tool, select the New pushbutton to display a window that lets you
specify information about the tool.

Note:  If the tool you want to add has similar attributes to one of the tools
       already in the Current Tools list, select the similar tool before
       selecting New. The controls in the New Tool and Change A Tool windows
       will be updated with the existing tool's attributes. If more than one
       tool is selected, the first selected tool is used.

 When you add a tool, an accelerator key is automatically assigned to it (if it
 is one of the first ten tools in the pulldown). Once you have added the tool,
 view the Tools pulldown to see which accelerator key is associated with it.


ΓòÉΓòÉΓòÉ 7.2.4. Delete ΓòÉΓòÉΓòÉ

Use the Delete pushbutton to delete the selected tool from the Current Tools
list box.

To delete one or more tools:

  1. Select the tools you want to delete from the list box.

  2. Select the Delete pushbutton.


ΓòÉΓòÉΓòÉ 7.2.5. Change ΓòÉΓòÉΓòÉ

Use the Change pushbutton to change the settings of the first selected tool in
the Tools pulldown.

To change tools:

  1. Select the tool you want to change from the list box. If more than one
     tool is selected, the first selected tool is used.

  2. Select the Change pushbutton to display a window that lets you change
     information about the tool.


ΓòÉΓòÉΓòÉ 7.3. New Tool and Change A Tool ΓòÉΓòÉΓòÉ

This help appears for both the New Tool window and Change a Tool window.

Use the New Tool window to add a new tool to the Tools list. Use the Change A
Tool window to change the information about an existing tool.

To add or change a tool:

  1. Type in a description for the Program title.

  2. Specify the Path and file name of the tool.

  3. In the Startup directory field, indicate which directory will become the
     current directory when the tool is run.

  4. Enter any parameters you want to be part of the Invocation String.

  5. Check the Prompt required check box if you want to specify input
     parameters when the tool is run.

     If this check box is checked, you can specify the prompt you see in the
     Prompt entry field.

  6. If the tool is an OS/2* operating system command file, select the Command
     File check box.

  7. Specify the type of program with the Program type radio buttons.

  8. Choose whether the program runs in the foreground or the background with
     the Run mode radio buttons.

  9. Select OK to add or change the tool.

 Note:  You can also use projects or executable files, from the File Control
        and base project windows, as tools. Select the project or file and drag
        it to the New Tool window to update the following fields:

 o Program title

 o Path and file name

 o Startup directory

 o Run Options.

 Any change is reflected in the Tools pulldown once the window is closed. You
 can save these changes in the profile so that they will appear the next time
 you invoke the WorkFrame/2* window.


ΓòÉΓòÉΓòÉ 7.3.1. Program Title ΓòÉΓòÉΓòÉ

Use this entry field to enter a title for the tool.

The title identifies the tool in window headings, messages, pulldowns, and list
boxes. Therefore, make it meaningful and unique.

It can be up to 100 characters long.


ΓòÉΓòÉΓòÉ 7.3.2. Path and File Name ΓòÉΓòÉΓòÉ

Enter the path and file name of the tool. If the path is not fully specified,
(for example, .\my_tool.exe) the WorkFrame/2* product searches the path
specified in the PATH environment variable when the program is started. If the
program is not found, an error message displays.


ΓòÉΓòÉΓòÉ 7.3.3. Startup Directory ΓòÉΓòÉΓòÉ

Specify the path of the directory you want to use as the directory when the
tool is run.

If you want to use the directory associated with the current project when the
tool is invoked, use a single period (.).


ΓòÉΓòÉΓòÉ 7.3.4. Invocation String ΓòÉΓòÉΓòÉ

Specify the parameters to be passed to the tool when it is started. You can use
substitution variables.

You can enter up to 100 characters.


ΓòÉΓòÉΓòÉ 7.3.5. Prompt Required ΓòÉΓòÉΓòÉ

If the prompt check box is checked, you will be able to enter a string at
runtime to acquire the invocation parameters.


ΓòÉΓòÉΓòÉ 7.3.6. Prompt ΓòÉΓòÉΓòÉ

If Prompt required is checked, you can use this entry field to specify the
prompt to be displayed when this tool is started.

You can enter up to 100 characters.


ΓòÉΓòÉΓòÉ 7.3.7. Run Mode ΓòÉΓòÉΓòÉ

Indicate whether the tool is to be run in the foreground or the background.

If you select Foreground, the tool runs in the foreground. The tool will appear
in your windows list.

If you select Background, the tool runs in the background. A Monitor window
displays showing the output. Only select Background if the program does not
interact with the user once it has started.


ΓòÉΓòÉΓòÉ 7.3.8. Command File ΓòÉΓòÉΓòÉ

If the tool you are adding is an OS/2* operating system command file, select
this check box. Any options in the rest of the window that are not allowed if
the tool is a command file will be grayed out.


ΓòÉΓòÉΓòÉ 7.3.9. Program Type ΓòÉΓòÉΓòÉ

Use these radio buttons to specify the type of program:

 o Program determines

 o OS/2* full screen

 o OS/2* text windowed

 o Presentation Manager* program application

 o DOS full screen

 o DOS text windowed

 Select Program determines to run the program as specified in the header of its
 executable file. By specifying another option, you can override the
 specification in the header of the executable file. You could, for example,
 start a windowed tool as a full screen tool. Do not start an application that
 is not a Presentation Manager* program as a Presentation Manager* program or
 vice versa. If the program is a Presentation Manager* program, select Program
 determines or Presentation Manager* program.


ΓòÉΓòÉΓòÉ 7.3.10. OK ΓòÉΓòÉΓòÉ

Select OK to save any additions or changes you have made to the list of tools.


ΓòÉΓòÉΓòÉ 7.3.11. Reset ΓòÉΓòÉΓòÉ

Use the Reset pushbutton to reset the controls to their setting when the window
was opened.


ΓòÉΓòÉΓòÉ 7.3.12. Default ΓòÉΓòÉΓòÉ

Use the Default pushbutton to set the controls in the window to the default
settings of the WorkFrame/2* product.


ΓòÉΓòÉΓòÉ <hidden> Switch List ΓòÉΓòÉΓòÉ

Select this item to display the Switch list window.

Use this window to select which programs are listed under the Switch list
pulldown.


ΓòÉΓòÉΓòÉ 7.4. Configure Switch List ΓòÉΓòÉΓòÉ

Use this window to select which programs are listed under the Switch list
pulldown.

Select the programs you want to include under the Switch list pulldown. Only
sessions defined as VISIBLE are selectable by you.

Items that are currently part of the pulldown are already selected. Deselect
any of these items that you do not want included in the Switch list pulldown.

Select OK to change the Switch list pulldown and close the window.

If you do not make any changes the Switch list pulldown will display all the
sessions running when the WorkFrame/2* product was started.

Select Cancel to close the window without making any changes to the Switch list
pulldown.


ΓòÉΓòÉΓòÉ 7.4.1. Sessions ΓòÉΓòÉΓòÉ

Use this list box to select which sessions you want displayed under the Switch
list pulldown.

All sessions registered with the desktop are listed. The first column tells you
whether the the program appears in the Window List. The second column tells you
whether the program can be reached by switching among windows by repeatedly
pressing the Esc key while holding down the Alt key.


ΓòÉΓòÉΓòÉ 7.4.2. OK ΓòÉΓòÉΓòÉ

Use the  OK pushbutton to confirm and save any changes made to the Switch list.

Changes are not saved between WorkFrame/2* sessions.


ΓòÉΓòÉΓòÉ 7.5. Background ΓòÉΓòÉΓòÉ

Select Color to change the client area color of the WorkFrame/2* window.

Select Bitmap to choose a bitmap for the client area of the WorkFrame/2*
window.


ΓòÉΓòÉΓòÉ 7.6. Color ΓòÉΓòÉΓòÉ

Select Color to change the client area color of the WorkFrame/2* window.


ΓòÉΓòÉΓòÉ 7.7. Bitmap ΓòÉΓòÉΓòÉ

Select Bitmap to choose a bitmap for the client area of the WorkFrame/2*
window.


ΓòÉΓòÉΓòÉ 7.8. Configure Background Color ΓòÉΓòÉΓòÉ

Use this window to select the color you want for the client area.

  1. Select the color you want to try from the list box.

  2. Select Test to see what the client area looks like with the color you
     selected.

     Note:  Double-clicking on a color is the same as selecting the color and
            then selecting Test.

     This step is optional.

  3. If you are satisfied with the changed client area color, select OK to
     change the color for this WorkFrame/2* session. Otherwise, go back to the
     first step.

  4. If you want the changed client area color to become the default when the
     WorkFrame/2* product is started, select Save settings - Profile or
     Savesettings - Both from the File pulldown.


ΓòÉΓòÉΓòÉ 7.8.1. Colors ΓòÉΓòÉΓòÉ

Use this list box to select the color for the client area.


ΓòÉΓòÉΓòÉ 7.8.2. OK ΓòÉΓòÉΓòÉ

Select OK to change the client area to the selected color and remove the
window.


ΓòÉΓòÉΓòÉ 7.8.3. Test ΓòÉΓòÉΓòÉ

Select Test to preview the selected client area color.

This step is optional.


ΓòÉΓòÉΓòÉ 7.9. Configure Background Bitmap ΓòÉΓòÉΓòÉ

Use this window to select a bitmap for the client area of the WorkFrame/2*
window. You must close it before you can open another window.

To select a bitmap for the client area:

  1. Note the path indicated next to the Directory field.

     If this directory is not the directory you want, then use the Directories
     list box to move to the correct directory. As you use this list box, the
     Directory string shows what directory you are in. If this string becomes
     too long to fit in the field, only its first and last parts are shown.

  2. As you move from directory to directory, the Files list box refreshes to
     show what files in the directory match the File mask.

     To change the mask, type over the present mask and press Enter. The file
     mask is saved for the next WorkFrame/2* session.

  3. Once the Files list box contains the bitmap you want, select the one you
     want to try.

  4. Select Test to see what the client area looks like with the bitmap you
     selected.

     Note:  Double-clicking on a bitmap is the same as selecting the bitmap and
            then selecting Test.

     This step is optional.

  5. If you are satisfied with the changed client area bitmap, select OK to
     change the bitmap for this WorkFrame/2* session. Otherwise, try another
     bitmap.

  6. If you want the changed client area bitmap to become the default when the
     WorkFrame/2* product is started, select Save settings - Profile or
     Savesettings - Both from the File pulldown.


ΓòÉΓòÉΓòÉ 7.9.1. Bitmap File Mask ΓòÉΓòÉΓòÉ

Use this entry field to specify masks to control which files are displayed.

You can enter characters such as * or ? to list files with similar
characteristics. For example:

 *.bmp will display all files in the directory which have an extension of bmp.

 *.?ga will display all files in the directory that have an extension such as
 david.xga or matthew.vga.


ΓòÉΓòÉΓòÉ 7.9.2. Files ΓòÉΓòÉΓòÉ

Use this list box to select a bitmap for the client area.

To select a bitmap from this list, double-click on the file name.


ΓòÉΓòÉΓòÉ 7.9.3. Directories ΓòÉΓòÉΓòÉ

Use this list box to select the drive or directory that the bitmap you want is
in.

To select a drive or directory from this list, double-click on the drive or
directory.


ΓòÉΓòÉΓòÉ 7.9.4. OK ΓòÉΓòÉΓòÉ

Use the OK pushbutton to confirm and save the client area bitmap.


ΓòÉΓòÉΓòÉ 7.9.5. Test ΓòÉΓòÉΓòÉ

Use the Test pushbutton to change the client area bitmap.


ΓòÉΓòÉΓòÉ 7.10. List Box Font/Color ΓòÉΓòÉΓòÉ

Select this item to display the List box fonts and colors window.

Use this window to change the font and color of the text in the following types
of list boxes.

 o Action Log

 o Project files (a list of the files of a project)

 o Project list (a list of projects)

 o Monitor windows

 o Object display (a list box used to show details of object modules).

 Samples of these list boxes are shown in the List box samples window.


ΓòÉΓòÉΓòÉ 7.11. Configure List Box Font/Color ΓòÉΓòÉΓòÉ

Use this window to change the font and color of the text in the following types
of list boxes.

 o Action Log

 o Project files (a list of the files of a project)

 o Project list (a list of projects)

 o Monitor windows

 o Object display (a list box used to show details of object modules).

  1. Select the List box types you want to adjust.

  2. Select the color you want from the Colors list box.

  3. Select the font and size you want from the Fonts and sizes list box.

  4. Select Test to see what the client area looks like with the choices you
     selected. You can see how the text looks in the sample text line at the
     bottom of the window and in the sample list box shown in the List box
     samples window.

     This step is optional.

  5. If you are satisfied with the changes, select OK to change the color for
     this WorkFrame/2* session. Otherwise, go back to the first step.

  6. If you want the changes to become the default, select Save settings -
     Profile  from the File pulldown.


ΓòÉΓòÉΓòÉ 7.11.1. Color ΓòÉΓòÉΓòÉ

Use this list box to select the color you want.

As you select different colors and fonts, the sample text at the bottom of the
window changes accordingly.


ΓòÉΓòÉΓòÉ 7.11.2. Font/Size ΓòÉΓòÉΓòÉ

Use this list box to select the font you want to use in the items selected in
the List box type list box.

As you select different colors and fonts, the sample text at the bottom of the
window changes accordingly.


ΓòÉΓòÉΓòÉ 7.11.3. List Box Type ΓòÉΓòÉΓòÉ

Use this list box to select which of the WorkFrame/2* list boxes you want to
apply the new font, font size, or color to.

You can select one or more items.


ΓòÉΓòÉΓòÉ 7.11.4. OK ΓòÉΓòÉΓòÉ

Select OK to save the fonts and colors you have chosen.


ΓòÉΓòÉΓòÉ 7.11.5. Test ΓòÉΓòÉΓòÉ

Select Test to preview the selected font and color in the List box Samples
window.


ΓòÉΓòÉΓòÉ 7.12. List box Samples ΓòÉΓòÉΓòÉ

Use this window to preview the appearance of text in these types of list boxes.

 o Action Log

 o Project files (a list of the files of a project)

 o Project list (a list of projects)

 o Monitor windows

 o Object display (a list box used to show details of object modules).
 There are no controls in this window. Use the List box fonts and colors window
 to select the fonts and colors.


ΓòÉΓòÉΓòÉ 7.12.1. Action Log Sample ΓòÉΓòÉΓòÉ

This list box shows you what the text in the Action log will look like if you
select the Test pushbutton in the List box fonts and colors window.


ΓòÉΓòÉΓòÉ 7.12.2. Monitor Output Sample ΓòÉΓòÉΓòÉ

This list box shows you what the text in the Monitor list box will look like if
you select the Test pushbutton in the List box fonts and colors window. The
monitor list box appears when an action is selected from the Actions pulldown.


ΓòÉΓòÉΓòÉ 7.12.3. Object Display Sample ΓòÉΓòÉΓòÉ

This list box shows you what the text in the Object dump list box will look
like if you select the Test pushbutton in the List box fonts and colors window.

A monospaced font will best show the horizontal alignment of the contents.

These list boxes are part of the Library utility.


ΓòÉΓòÉΓòÉ 7.12.4. Project List Sample ΓòÉΓòÉΓòÉ

This list box shows you what the text in the Project control list box will look
like if you select the Test pushbutton in the List box fonts and colors window.


ΓòÉΓòÉΓòÉ 7.12.5. Project File Sample ΓòÉΓòÉΓòÉ

This list box shows you what the text in the Project file list box will look
like if you select the Test pushbutton in the List box fonts and colors window.

All list boxes which list the files of a project will use the font and color
selected.


ΓòÉΓòÉΓòÉ <hidden> Preferences ΓòÉΓòÉΓòÉ

Select this item to display the Preferences window.

Use this window to tailor the WorkFrame/2* window.


ΓòÉΓòÉΓòÉ 7.13. Configure Preferences ΓòÉΓòÉΓòÉ

Use the selections in this window to control the appearance of the WorkFrame/2*
window.

 Control   Meaning

 Animation
           Run the animation sequence of the Deletion Window or icon.

 Sound
           Play a tune when items are deleted.

 Capture Tools
           Start new tools so that their windows become child windows of the
           WorkFrame/2* product rather than the desktop.

 Minimize monitor
           Minimize the Monitor window that is displayed when an action is
           successfully started.

 Automatic deselection
           Deselect items after the action has been performed successfully.

 Default language
           Specify the language you want to use as the default for new
           projects.

 Unless you select Save settings from the File


ΓòÉΓòÉΓòÉ 7.13.1. Animation ΓòÉΓòÉΓòÉ

Use this check box to turn the animation sequence on or off.

If selected, the WorkFrame/2* product animates the deletion of files, tools,
object modules, and projects using bitmaps found in the directory where the
WorkFrame/2* product was installed. To create your own animation sequence,
replace the following bitmaps (located in the installation directory) with your
own:

 o SHRED1.BMP

 o SHRED2.BMP

 o SHRED3.BMP

 o SHRED4.BMP

 o SHRED5.BMP
 The new bitmaps:

 o Must have the same names as the original ones.

 o Must have the same dimensions (64 pels by 64 pels).

 Note:  Smaller bitmaps require less memory leaving more for other processes.

 If you do not want to use animation, you can delete the bitmaps.


ΓòÉΓòÉΓòÉ 7.13.2. Sound ΓòÉΓòÉΓòÉ

The WorkFrame/2* product can animate the deletion of files, tools, object
modules, and projects.

Use this check box to choose whether to play the tune accompanying the
animation.

This check box is only available if the Animation check box is selected.


ΓòÉΓòÉΓòÉ 7.13.3. Capture Tools ΓòÉΓòÉΓòÉ

Select this option to start the tool so that its window becomes a child window
of the WorkFrame/2* product rather than the desktop.

If this option is selected, the application windows of tools behave like the
WorkFrame/2*'s windows. For example, suppose you started a tool and then opened
the File Control window. With this option selected, the tool's window would
appear just behind the File Control window. Otherwise, it would be behind the
WorkFrame/2*'s application window.

An additional benefit is that, if the tool's window was minimized, its icon
would appear with the WorkFrame/2*'s application window.

This option does not affect tools that are already started.


ΓòÉΓòÉΓòÉ 7.13.4. Minimize Monitor ΓòÉΓòÉΓòÉ

Select this option to save screen space by minimizing the Monitor window that
is displayed when an action is performed.

Some actions, such as when you make a composite project, can result in several
monitor windows displaying at the same time. When this option is not selected,
the windows are cascaded from the bottom left part of the screen to the upper
right part. Otherwise, the windows are minimized and appear as icons.


ΓòÉΓòÉΓòÉ 7.13.5. Automatic Deselection ΓòÉΓòÉΓòÉ

Many actions in the WorkFrame/2* product let you select one or more items in a
list box first. The action is then performed on the selected items

If you want the items to be automatically deselected after the action is
finished, select this option.


ΓòÉΓòÉΓòÉ 7.13.6. Save Window Positions ΓòÉΓòÉΓòÉ

Select this option to save the window positions from session to session. When
you restart the WorkFrame/2* application window, the windows will be in the
same positions as when you left it.

Otherwise, the window positions will only be saved if you select Window
Positions or Both from the Save settings item in the File pulldown.


ΓòÉΓòÉΓòÉ 7.13.7. Default Language ΓòÉΓòÉΓòÉ

Use this option to specify which language you want to be automatically selected
as the default language when you are creating a new project.

The selected language is also used when creating a temporary project.


ΓòÉΓòÉΓòÉ 7.13.8. OK ΓòÉΓòÉΓòÉ

Select OK pushbutton to save the settings specified in the Preferences window
and close it.


ΓòÉΓòÉΓòÉ 8. Tools ΓòÉΓòÉΓòÉ

This pulldown lists the tools added to the WorkFrame/2* product. Tools that
came with the WorkFrame/2* product are shown above the separator; those added
with the Addtool utility or by using the Add Tools window are listed below the
separator.

To start a tool, select it from the pulldown. If the tool runs in the
background, a Monitor window shows all output from the tool. If the tool runs
in the foreground, its title appears under Sessions in the Windows pulldown. If
the tool runs in the background, its title appears under Dialogs in the Windows
pulldown.


ΓòÉΓòÉΓòÉ <hidden> Library Utility ΓòÉΓòÉΓòÉ

Select this item to display the Library utility window. Use this window to
maintain object libraries.


ΓòÉΓòÉΓòÉ 8.1. Library Utility ΓòÉΓòÉΓòÉ

Use this window to maintain object libraries. You can

 o Create a library

 o Add objects to a library

 o Delete objects from a library

 o Unload objects to any directory

 o Change the characteristics of a library

 o Generate listing files of different levels of detail

 o Display the details of object modules.

 To create a library:

  1. Enter the path and name of the library in the Library entry field. If you
     do not specify a path, the library will be located in the directory from
     which its first object module comes from in the next step.

  2. Drag object modules (or existing libraries) from a project window or the
     Files list box (under the Object Modules list box) in the Library Utility
     window.

  3. Use the Directories list box to show the list of files in the Files
     directory.

 To select an existing library to work on:

  1. Move to the directory containing the library you want to work with. The
     object module and library files in the directory appear in the Files list
     box.

  2. Drag the library name to the library entry field.

     Note:  You can also drag the name of the library from any open project
            window.


 To add object modules to a library:

  1. Move to the directory you want to copy the files from by using the
     Directories list box.

  2. Select all the files in the Files list box that you want to copy to the
     library.

  3. Drag them to the object modules list box. This will load all the selected
     objects into that library.

     You can also drag object modules from any active project windows or icons.

 If any of the items being dragged is a library, its object modules are merged
 into the target library.

 Dragging object modules to the Library utility icon is the same as dragging
 them to the Object modules list box.

 To delete object modules from a library or directory:

  1. If you want to remove object modules from a library, select those modules
     in the Object modules list box.

     If you want to remove object modules from a directory, select those
     modules in the Files list box.

  2. Drag the object modules to the Deletion Window or icon.

 To copy library object modules to a directory:

  1. Move to the directory you want to copy the objects to by using the
     Directories list box.

  2. Select the modules in the library you want to copy and drag them to the
     Files list box.

     You can also drag the objects to any active project window.

 You can control the characteristics of the library file with the controls in
 the Library options. If you want a listing of the library's contents, select
 List file and indicate what Level of detail you would like.

 To view the details of an object module, double-click with mouse button 1 on
 the module in either the Object modules or the Files list boxes. The Object
 Module Details window opens to show the details.


ΓòÉΓòÉΓòÉ 8.1.1. Object Modules ΓòÉΓòÉΓòÉ

This list box shows the objects in the library. You can use the list box
control techniques of the WorkFrame/2* window with this list box.


ΓòÉΓòÉΓòÉ 8.1.2. Directories ΓòÉΓòÉΓòÉ

This list box lets you move from directory to directory by clicking on the
directory name.


ΓòÉΓòÉΓòÉ 8.1.3. Library ΓòÉΓòÉΓòÉ

This field contains the name of the library you are working on.

You can enter the name directly into this field or drag the name from the Files
list box or an active project window.

Do not specify a path. Once the name is entered, the path of the current
directory is added to the name.


ΓòÉΓòÉΓòÉ 8.1.4. Page Size ΓòÉΓòÉΓòÉ

This entry field contains the page size of the library. When the Library
utility window is first opened, it shows the page size of the currently
selected library. Page sizes must be equal to 2 to the power of n where n is
between 4 and 15 inclusive.


ΓòÉΓòÉΓòÉ 8.1.5. Files ΓòÉΓòÉΓòÉ

The Files list box contains all the files with an extension of OBJ or LIB files
in the currently selected directory. You can use the list box control
techniques of the WorkFrame/2* window with this list box.


ΓòÉΓòÉΓòÉ 8.1.6. List File ΓòÉΓòÉΓòÉ

Check this check box to create a listing when the library changes. The listing
shows the contents and interdependencies of objects in the library.

The listing will have the name of the library but with an extension of LST. It
will be placed in the same directory as the library.


ΓòÉΓòÉΓòÉ 8.1.7. Case Sensitive ΓòÉΓòÉΓòÉ

The Case sensitive check box is initialized with the attribute associated with
the currently selected library. Linkers and other utilities can use this flag
to determine whether searches in the library for symbols should be case
sensitive.


ΓòÉΓòÉΓòÉ 8.1.8. Extended Dictionary ΓòÉΓòÉΓòÉ

The Extended Dictionary check box is initialized with the attribute associated
with the currently selected Library. The extended dictionary speeds up linking,
since it contains the interdependencies of objects within the library. When a
particular object is located in the library, all the other objects it is
dependent upon can be determined and accessed quickly.


ΓòÉΓòÉΓòÉ 8.1.9. Level ΓòÉΓòÉΓòÉ

The Level entry field refers to the detail level of the listing file. This
field is available only if the the Listing check box has been selected. There
are three levels of listings.

If you enter  1, the listing includes these items:

 o Module number

 o Module name

 o Public symbols   (listed in two columns)

 o External symbols  (listed in two columns)

 If you enter 2, the listing includes these items:

 o Everything from level 1 except that external symbols are listed in one
   column.

 o External symbols and the modules (shown by number and name) which resolve
   them.

 If you enter 3, the listing includes these items:

 o Everything from level 2.

 o Characteristics of the library:

    - Page size

    - Flags

    - Status of extended dictionary

    - Total number of modules

    - Total bytes for modules

    - Total number of symbols in dictionary

    - Maximum number of symbols in dictionary

    - Total number of pages for the dictionary.

 o Dump of the extended dictionary (if it exists). This shows which modules
   will be automatically included, in addition to the requested module, when
   the /NOE option is not used during linking.

 Examples of the different listings and details of their contents can be found
 in the WorkFrame/2* product's online reference.


ΓòÉΓòÉΓòÉ 8.1.10. OK ΓòÉΓòÉΓòÉ

Use this pushbutton to close the application window.

Note:  Any changes you made will still be in effect once the window is closed.


ΓòÉΓòÉΓòÉ 8.2. Object Module Details ΓòÉΓòÉΓòÉ

This window displays the contents of the object module selected from the
Library utility window. The following information is shown:

 o Default Library Records

 o External Definition Records

 o Common Definition Records

 o Public Definition Records

 o Segment Definition Records

 o Fixups

 o Group Definition Records

 o Import Records (Only displayed if the object module is in an import
   library.)

 o Segment Contents

 You can get more information on a list box item by double-clicking on it. Or,
 if you are using the keyboard, select the item and press Enter.

 Note:  The amount of information displayed is limited by the amount of memory
        available to the list box.


ΓòÉΓòÉΓòÉ 8.2.1. Default Library Records ΓòÉΓòÉΓòÉ

This list box displays all default library records emitted by the compiler.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.


ΓòÉΓòÉΓòÉ 8.2.2. External Definition Records ΓòÉΓòÉΓòÉ

This list box shows the external references to public symbols defined in other
object modules.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.


ΓòÉΓòÉΓòÉ 8.2.3. Common Definition Records ΓòÉΓòÉΓòÉ

This list box shows the common definition records in the object module.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.


ΓòÉΓòÉΓòÉ 8.2.4. Public Definition Records ΓòÉΓòÉΓòÉ

This list box contains all public symbols defined in the public definition
records.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.


ΓòÉΓòÉΓòÉ 8.2.5. Segment Definition Records ΓòÉΓòÉΓòÉ

This list box contains all the segments defined in the object. Each line
displays the segment's name, alignment, type, combine type, and class.

You can get more information on a list box item by double-clicking on it. Or,
if you are using the keyboard, select the item and press Enter.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.


ΓòÉΓòÉΓòÉ 8.2.6. Fixups ΓòÉΓòÉΓòÉ

This list box shows the records produced by the compiler to tell the linker
references in the object code or data that could not be resolved by the
compiler.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.


ΓòÉΓòÉΓòÉ 8.2.7. Group Definition Records ΓòÉΓòÉΓòÉ

This list box displays all groups defined in the object.

You can get more information on a list box item by double-clicking on it. Or,
if you are using the keyboard, select the item and press Enter.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.


ΓòÉΓòÉΓòÉ 8.2.8. Import Records ΓòÉΓòÉΓòÉ

This list box shows the import records of the object module. These records are
only present in import libraries. The external name is displayed in parentheses
followed by the name of the dynamic link library containing the symbol. If the
entry contains an ordinal entry point, that number is displayed following the
name of the library.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.


ΓòÉΓòÉΓòÉ 8.2.9. OK ΓòÉΓòÉΓòÉ

Select OK to close the window.


ΓòÉΓòÉΓòÉ 8.3. Group Composition ΓòÉΓòÉΓòÉ

This window displays all segments comprising the group selected on the Object
Module Details window.

You must close this window before you can work with the Object Module Details
window.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.

 Press OK to end the display.


ΓòÉΓòÉΓòÉ 8.3.1. Group Composition ΓòÉΓòÉΓòÉ

This list box shows the group composition contents for the specific segment you
selected.


ΓòÉΓòÉΓòÉ 8.3.2. OK ΓòÉΓòÉΓòÉ

Select OK to close this window.


ΓòÉΓòÉΓòÉ 8.4. Segment Contents ΓòÉΓòÉΓòÉ

This window shows all segments comprising the group selected on the Object
Module Details.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.


ΓòÉΓòÉΓòÉ 8.4.1. Segment Contents ΓòÉΓòÉΓòÉ

This list box shows all LEDATA (records of static data) and LIDATA (records of
iterative data) records associated with that segment in both hexadecimal and
ASCII format. Each record begins with an indication of its length and its
offset within the segment.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.


ΓòÉΓòÉΓòÉ 8.4.2. OK ΓòÉΓòÉΓòÉ

Select OK to close this window.


ΓòÉΓòÉΓòÉ 8.5. Processing Errors from Library Utility ΓòÉΓòÉΓòÉ

Use this window to see what errors were found during the process you started.
To get help for the message, select the message line in the list box and press
F1. The help tells you what action you can take.


ΓòÉΓòÉΓòÉ 8.5.1. OK ΓòÉΓòÉΓòÉ

Select OK to close the window.


ΓòÉΓòÉΓòÉ <hidden> Make File Creation ΓòÉΓòÉΓòÉ

Select this item to display the Make File Creation window. Use this window to:

 o Create a make file for the current project. If one already exists, you can
   replace it with a new one. The make file is compatible with the make utility
   in the OS/2* Developer's Toolkit.

 o Update the dependencies file as source code files are added or deleted.

 o Change which options are used in the make file. For example, you might want
   to include debugging information in the code at one time but not at another.
   Or, you might have changed the compile or link options and want to make a
   new make file.


ΓòÉΓòÉΓòÉ 8.6. Make File Creation ΓòÉΓòÉΓòÉ

Use this window to:

 o Create a make file for the current project. If one already exists, you can
   replace it with a new one. The make file is compatible with the make utility
   in the OS/2* Developer's Toolkit.

 o Update the dependencies file as source code files are added or deleted.

 o Change which options are used in the make file. For example, you might want
   to include debugging information in the code at one time but not at another.
   Or, you might have changed the compile or link options and want to make a
   new make file.

 The Make File Creation tool uses information in the project's control file and
 language profile including:

 o Compile options

 o Link options

 o Target file name

 o Make file name

   Note:  The Make File Creation tool creates the make file from scratch. It
          does not use information from one that may already exist. Therefore,
          rename the existing one if it contains information you want to save.

 o Name of the executable file of the compiler.

 o Name of the executable file of the linker.

   Note:  The linker specified in the language profile must use the same
          command line format as the OS/2* operating system linker.


 to build the make file.

 To create a make file:

  1. Select the actions you want done by the make file from the Actions list
     box.

  2. Select the files you want these actions performed on from the Files list
     box.

  3. If you want to specify compile options, select the Compile options
     pushbutton.

     If you want to specify link options, select the Link Options pushbutton.

     If you choose not to specify options, a default string will be used by the
     make file. You can edit the make file to change these strings later.

  4. Select  Start to create the make file.

     As the make file is created, messages are displayed beneath the Actions
     list box. Any errors are displayed in an action window.

 Note:

 There are some restrictions on preprocessor directives when creating a make
 file using the Make File Creation utility. The only preprocessor directive
 recognized is #include. All other directives (for example, #define, #if,
 #endif) are not recognized.

 This could influence the way that a #include statement is processed if it is
 used in conjunction with other preprocessor directives. For example, consider
 a source file that contains the following statements:

  #define INCLUDE_FILE "fred.h"
  #include INCLUDE_FILE

 The Make File Creation utility recognizes that an include exists, but is
 unable to determine the name because it does not process the #define
 statement. In this situation an error message is generated, indicating that an
 unknown include name was used in your source file.

 In the following example, an error message is not generated, but the results
 of the Make File Creation utility will not produce what you expected.

  #if FLAG
     #include "fred.h"
  #else
     #include "george.h"
  #endif

 The make file created has a dependency on both fred.h and george.h and not on
 one or the other as expected.

 The name of the make file is the name specified when the project was created.

 If a make file exists already, a message window will display to let you avoid
 overwriting the original file.

 After the make file has been created, you can:

 o Browse the Make file list box.

   If you want to see the dependencies related to a particular object module,
   select that object to scroll the Dependencies list box. to the appropriate
   area.

 o Browse the Dependencies list box.

 o Edit the make file.

   Double-click with mouse button 1 on any line in the Make file list box to
   edit a temporary file called makefile.tmp.

   When you have finished editing, select OK to replace the make file in the
   project directory with the new make file.

 o Edit the Dependencies list box

   Double-click with mouse button 1 anywhere in the list box to edit a
   temporary file called depend.tmp. When you have finished editing, select OK
   to copy it to your project directory with the name you specified for the
   make file.

   If you want update the Dependencies file but not overwrite the existing make
   file:

     1. Create the make file as you normally would and select OK to save the
        files.

     2. When the message window displays, select No to keep the original make
        file.


ΓòÉΓòÉΓòÉ 8.6.1. Make File ΓòÉΓòÉΓòÉ

The Make file list box displays the make file built by this process.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.

 Once the Make File Creation has created the make file, you can double-click on
 this list box to view and edit the whole file. Remember, any editing changes
 you make will not be reflected if the Make File Creation tool is used to
 replace the make file later.


ΓòÉΓòÉΓòÉ 8.6.2. Dependencies ΓòÉΓòÉΓòÉ

This list box will be used to contain the dependencies file built by this
process. This file will be imbedded into the make file.

Note:  The amount of information displayed is limited by the amount of memory
       available to the list box.

 Once the Make File Creation has created the dependencies file, you can
 double-click on this list box to view and edit the whole file. Remember, any
 editing changes you make will not be reflected if the Make File Creation tool
 is used to replace the dependencies file later.


ΓòÉΓòÉΓòÉ 8.6.3. Files ΓòÉΓòÉΓòÉ

Use this list box to select the files you want to be used to make the target
file.

Select any files you think should be part of the make file. Any selected files
which are not needed by the make file are ignored. Therefore, you can just
select all the files if you like.

Note:  You can use the list box control techniques of the WorkFrame/2* window
       with this list box.

 This list box provides a list of project files that you want analyzed to build
 the Make file and its dependencies file. You must select at least one file to
 process.


ΓòÉΓòÉΓòÉ 8.6.4. Actions ΓòÉΓòÉΓòÉ

Use this list box to select the actions which need to be part of the make file.

 Compile
           Files with an extension matching the ones specified as source code
           extensions in the language profile will be compiled into object
           modules with the extension .OBJ.

 Link
           Files with the extension .OBJ will be linked to form an executable
           file with the name specified for the target file of the project.

 Resource compile
           Files with the extension .RC will be compiled to form resource
           files.

 Message file creation
           Files with the extension .TXT will be compiled to form message
           files.

 Message file binding
           Files with the extension .MSG will be bound to the executable file
           created by linking the object modules.

 IPF compile
           Files with the extension .IPF. will be compiled to form a help files
           with the extension of .HLP.


ΓòÉΓòÉΓòÉ 8.6.5. Cancel ΓòÉΓòÉΓòÉ

Use the Cancel pushbutton to close the Make File Creation window without
creating a new make file or replacing an existing one.


ΓòÉΓòÉΓòÉ 8.6.6. OK ΓòÉΓòÉΓòÉ

Select OK to replace the make file in the project directory (if it exists) with
the new make file. If you are just updating the dependencies file, select OK
and then select No when the warning message appears about losing the original
make file.


ΓòÉΓòÉΓòÉ 8.6.7. Start ΓòÉΓòÉΓòÉ

Once you have chosen the appropriate options and actions, use the Start
pushbutton to create the make file.


ΓòÉΓòÉΓòÉ 8.7. Processing Errors from Make File Creation ΓòÉΓòÉΓòÉ

Use this window to see what errors were found during the process you started.
To get help for the message, select the message line in the list box and press
F1. The help tells you what action you can take.


ΓòÉΓòÉΓòÉ 8.7.1. OK ΓòÉΓòÉΓòÉ

Select OK to close the window.


ΓòÉΓòÉΓòÉ 8.7.2. Cancel ΓòÉΓòÉΓòÉ

Select Cancel to close the window and stop creating the make file.


ΓòÉΓòÉΓòÉ <hidden> Language Profile Management ΓòÉΓòÉΓòÉ

Select this item to display the Language profile management window.


ΓòÉΓòÉΓòÉ <hidden> User Tools ΓòÉΓòÉΓòÉ

Select this item to start the tool named in it.


ΓòÉΓòÉΓòÉ 9. Windows ΓòÉΓòÉΓòÉ

Use this pulldown to switch to other sessions or dialogs.

Windows that appear under Sessions are:

 o Tools that run in the foreground. Most tools are identified by their titles.

 o Editing sessions. Look for the name of the file being edited.

 o Windows started from the WorkFrame/2* product.
 These windows can become hidden under the WorkFrame/2* window.

 Windows that appear under Dialogs are any windows that are part of the
 WorkFrame/2* product and tools started in Background mode. These windows
 remain on top of the WorkFrame/2* window.

 When a window is selected:

 o It becomes the active window.

 o It is placed on top of all other windows.

 o If it was minimized, it is restored.


ΓòÉΓòÉΓòÉ 9.1. Sessions ΓòÉΓòÉΓòÉ

Windows that appear under Sessions are:

 o Tools that run in the foreground. Most tools are identified by their titles.

 o Editing sessions. Look for the name of the file being edited.

 o Windows started from the WorkFrame/2* product.
 These windows can become hidden under the WorkFrame/2* window.


ΓòÉΓòÉΓòÉ 9.2. Dialogs ΓòÉΓòÉΓòÉ

Windows that appear under Dialogs are any windows that are part of the
WorkFrame/2* product and tools started in Background mode. These windows remain
on top of the WorkFrame/2* window.


ΓòÉΓòÉΓòÉ 10. Switch List ΓòÉΓòÉΓòÉ

This help panel displays when you select Switch list or one of the items under
the Switch list pulldown.

Use this pulldown to see the list of programs that are currently running. By
clicking on a program, you can switch to it.

The Switch list pulldown is initialized from the Window List and is updated
when programs are closed.

Any program you select through the Switch list window appears in this pulldown.
Therefore you can tailor it to your needs.

The Switch list configuration is not saved when the WorkFrame/2* window is
closed.


ΓòÉΓòÉΓòÉ <hidden> Common windows ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ <hidden> Invocation String ΓòÉΓòÉΓòÉ

Use this window to specify the invocation parameters when you start one of the
tools in the Tools pulldown or an executable file.

  1. Enter the invocation parameters in the Enter invocation parameters entry
     field.

  2. Select OK to invoke the program with the string you have entered.

 Cancel cancels the program invocation.


ΓòÉΓòÉΓòÉ <hidden> Invocation String ΓòÉΓòÉΓòÉ

Use this entry field to enter any parameters you want to start a tool or an
executable file with.

If the tool is one that you have configured, the prompt is the one specified in
the New Tool or Change A Tool window. You can use substitution variables as
parameters.


ΓòÉΓòÉΓòÉ <hidden> OK ΓòÉΓòÉΓòÉ

Use the OK pushbutton to start the program with the invocation parameters you
specified.


ΓòÉΓòÉΓòÉ <hidden> Save Contents of List box ΓòÉΓòÉΓòÉ

Use this window to save the contents of the list box to a file or the OS/2*
operating system clipboard.

  1. Specify whether you want to save to a file or the clipboard.

     If you are saving to a file, type the path and name of the file into the
     File name entry field. If the file exists, it is replaced.

  2. Press Save to save the contents, or Cancel to remove the window.


ΓòÉΓòÉΓòÉ <hidden> Path and File Name ΓòÉΓòÉΓòÉ

If you are saving to a file, type the path and name of the file into the File
name entry field. If the file exists, it is replaced.


ΓòÉΓòÉΓòÉ <hidden> Where ΓòÉΓòÉΓòÉ

Use these radio buttons to indicate where you want to save the contents of the
list box.

 File      Save the contents in a file. If you are saving to a file, type the
           path and name of the file into the File name entry field. If the
           file exists, it is replaced.

 Clipboard Save the contents in the OS/2* operating system clipboard.


ΓòÉΓòÉΓòÉ <hidden> Save ΓòÉΓòÉΓòÉ

Use the Save pushbutton to save the contents of the Action Log list box.


ΓòÉΓòÉΓòÉ <hidden> Monitor ΓòÉΓòÉΓòÉ

The Monitor window displays whenever a tool is running in the background or
Compile, Build, Link, or Make is selected from the Actions pulldown. Output
from the action displays in the list box so you can see what is happening.

While the Monitor window list box is being updated, you can only select Stop.

Select Stop to halt the tools or action associated with the window.

If the action is completed successfully you will hear a high-pitched beep. If
the action is not successfully completed, then you will hear a low-pitched
beep.

Note:  Some tools cannot be interrupted.

 The other pushbuttons are only available if:

 o The action has stopped on its own.

 o You have pressed the Stop pushbutton and the action has stopped.

 Once the action has stopped, you can use the: Print, Save, and Cancel
 pushbuttons.

 You can double-click on a line in the Monitor window list box to edit files if
 the dynamic link library of the compiler can parse the message line into a
 file name.

 Once the editor has started, it can scroll to the line indicated in the
 message if:

 o The editor supports the communication of error messages and the Send
   compiler errors check box (in the Configure Editor window) is selected.

 o The message line matches the form of the error message template specified in
   the Compile options dynamic link library. If you are using the default
   dynamic link library for the compile options, you can specify the error
   message template. If the dynamic link library is designed for a specific
   compiler, the error message template may already be built in.

 For example, if you are using the OS/2* Enhanced Editor editor and a compiler
 which can send the line number in the message, you can use the monitor window
 to move around the editing session. Suppose you are compiling a program and
 the following messages appear in the Monitor window.

  DAVID.C(0184):Missing ';'.
  DAVID.C(1318):Wrong number of parameters.
  DAVID.C(3679):Unexpected text identifier.
 You could start the editing session by clicking on the first line. The OS/2*
 Enhanced Editor editor would not only display the file for editing but
 automatically move to line 184. After inserting a ';', you could click on the
 next message line to move to line 1318 of the file being edited.

 The feature works with most text mode editors and some editors based on the
 Presentation Manager* program.

 For example, when you are fixing errors found by a compiler, just find the
 error in the list box and select it to edit the source file.


ΓòÉΓòÉΓòÉ <hidden> Monitor ΓòÉΓòÉΓòÉ

Use this list box to see how the process you started is proceeding.

You can double-click on a line in the Monitor window list box to edit files if
the dynamic link library of the compiler can parse the message line into a file
name.

Once the editor has started, it can scroll to the line indicated in the message
if:

 o The editor supports the communication of error messages and the Send
   compiler errors check box (in the Configure Editor window) is selected.

 o The message line matches the form of the error message template specified in
   the Compile options dynamic link library. If you are using the default
   dynamic link library for the compile options, you can specify the error
   message template. If the dynamic link library is designed for a specific
   compiler, the error message template may already be built in.

 For example, if you are using the OS/2* Enhanced Editor editor and a compiler
 which can send the line number in the message, you can use the monitor window
 to move around the editing session. Suppose you are compiling a program and
 the following messages appear in the Monitor window.

  DAVID.C(0184):Missing ';'.
  DAVID.C(1318):Wrong number of parameters.
  DAVID.C(3679):Unexpected text identifier.
 You could start the editing session by clicking on the first line. The OS/2*
 Enhanced Editor editor would not only display the file for editing but
 automatically move to line 184. After inserting a ';', you could click on the
 next message line to move to line 1318 of the file being edited.

 The feature works with most text mode editors and some editors based on the
 Presentation Manager* program.

 For example, when you are fixing errors found by a compiler, just find the
 error in the list box and select it to edit the source file.


ΓòÉΓòÉΓòÉ <hidden> Automatic Scrolling ΓòÉΓòÉΓòÉ

Use this check box to scroll the monitor list box automatically as new
information becomes available.


ΓòÉΓòÉΓòÉ <hidden> Stop ΓòÉΓòÉΓòÉ

Use the Stop pushbutton to try to stop the process. You will be asked to
confirm that you want the command stopped.

Note:  Some processes may take a while to recognize the request to stop. Others
       may not accept any requests to stop.


ΓòÉΓòÉΓòÉ <hidden> Print ΓòÉΓòÉΓòÉ

Use the Print pushbutton to print the output that appears in the list box in
this window.


ΓòÉΓòÉΓòÉ <hidden> Save ΓòÉΓòÉΓòÉ

Use the Save pushbutton to save the output that appears in the list box in this
window. You can save the output to a file or to the OS/2 clipboard.


ΓòÉΓòÉΓòÉ <hidden> Cancel ΓòÉΓòÉΓòÉ

Select this pushbutton to remove the window.


ΓòÉΓòÉΓòÉ <hidden> Keys Help ΓòÉΓòÉΓòÉ

Select the specific type of Keys Help You would like :

 o General Keys Help

 o Accelerator Keys Help

 o Mouse Controls.


ΓòÉΓòÉΓòÉ <hidden> General Keys Help ΓòÉΓòÉΓòÉ

The list of keys is arranged in groups.

Use:

 o HELP KEYS to get help

 o SYSTEM KEYS to switch between programs

 o WINDOW KEYS to move around in a program window

 o POP-UP WINDOW KEYS to make a selection in a pop-up window

 o EDITING KEYS to make changes in a pop-up window.

 When two key names are joined by a plus sign (+), use these two keys together.
 Hold down the first key and press the second key.

 HELP KEYS

 F1
           Get help
 F2
           Get extended help (from within any help window)
 F9
           Go to a list of keys (from within any help window)
 F11 or Shift+F1
           Go to the help index (from within any help window)
 Esc
           Cancel help
 Alt+F4
           Close the help window
 Alt+F6
           Move among windows
 Shift+F10
           Get help for help

 SYSTEM KEYS

 Alt+Esc
           Switch to the next program, including full-screen programs
 Alt+Tab
           Switch to the next windowed program
 Ctrl+Esc
           Switch to the Task List

 WINDOW KEYS

 F10
           Go to/from the action bar
 Arrow keys
           Move among choices
 End
           Go to the last choice in a pulldown
 Esc
           Cancel a pulldown, the system menu, or window
 Home
           Go to the first choice in a pulldown
 PgUp
           Scroll the contents of the window up one page
 PgDn
           Scroll the contents of the window down one page
 Underlined letter
           Move among the choices on the action bar and select pulldown items
 Alt
           Go to/from the action bar
 Alt+F4
           Close the window
 Alt+F5
           Restore the window
 Alt+F7
           Move the window
 Alt+F8
           Size the window
 Alt+F9
           Minimize the window
 Alt+F10
           Maximize the window
 Ctrl+PgDn
           Scroll the contents of the window right one page
 Ctrl+PgUp
           Scroll the contents of the window left one page
 Shift+Esc or Alt+Spacebar
           Go to/from the system menu
 Shift+Esc or Alt
           Go to/from the system menu of a text window

 POP-UP WINDOW KEYS

 Enter
           Complete the pop-up window
 Esc
           Cancel the pop-up window
 Spacebar
           Set a check box on/off or perform the task described on the selected
           pushbutton
 Tab
           Move to the next entry field or check box

 EDITING KEYS

 Backspace (left arrow delete)
           Delete the character to the left of the cursor
 Del
           Delete the character at the cursor
 End or Ctrl+Right Arrow key
           Move to the end of a field
 Home or Ctrl+Left Arrow key
           Move to the beginning of a field.


ΓòÉΓòÉΓòÉ <hidden> Accelerator Keys Help ΓòÉΓòÉΓòÉ

The following accelerator keys are used in the WorkFrame/2* interface:

 Ctrl+P              Start Project Control window.

 Ctrl+F              Start File Control window.

 Ctrl+W              Start Deletion Window.

 Ctrl+C              Compile selected files.

 Ctrl+L              Link selected files.

 Ctrl+B              Build selected files.

 Ctrl+M              Make selected files.

 Ctrl+D              Debug selected files.

 Ctrl+R              Run selected files.

 Ctrl+I              Start Library Utility window.

 F8                  Switch between listing file names and titles in the
                     Project Control window.


ΓòÉΓòÉΓòÉ <hidden> Mouse Controls ΓòÉΓòÉΓòÉ

Several controls in the WorkFrame/2* interface have special mouse actions
associated with them. This panel lists those controls and the actions you can
perform with Mouse Button 1 and Mouse Button 2 (if applicable).

Project Control window

 o Path and name field (above list of projects)

          Mouse Button 1 - Select all projects in the list box.

          Mouse Button 2 - Deselect all projects in the list box.

 o Project Control list box

          Mouse Button 1 - Start the projects selected

 Base Project windows

 o Path and file name field

          Mouse Button 1 - Select all files in the list box

          Mouse Button 2 - Deselect all the files in the list box

 o Files list box

          Mouse Button 1 - Edit the selected files if they are source code; run
          them if they are executable code.

          Note:  Depending on the configuration of the editor, all selected
                 files or just the first selected file may be used.


 File Control window

 o Files list box

          Mouse Button 1 - Edit the selected files if they are source code; run
          them if they are executable code.

          Note:  Depending on the configuration of the editor, all selected
                 files or just the first selected file may be used.

 o Directory is field

   Mouse Button 1 - Select all files in the Files list box.

   Mouse Button 2 - Deselect all files in the Files list box.

 o Directory list box

          Mouse Button 1 - Change to the selected directory or drive

 Monitor window

 o Monitor list box

          Mouse Button 1 - Start the editor for the file on which an error
          occurred (this depends on whether the DLL shipped with the compiler
          being used supports error message parsing)

 Library Utility window

 o Object Modules list box

          Mouse Button 1 - Open object module windows for the objects selected
          in this list box

 o Files list box (located below Object Modules list box)

          Mouse Button 1 - Open object module windows for the objects selected
          in this list box

 o Path and file name

          Mouse Button 1 - Select all files in the files list box

          Mouse Button 2 - Deselect all files in the files list box

 o Object Modules list box title

          Mouse Button 1 - Select all objects in the objects modules list box

          Mouse Button 2 - Deselect all modules in the object modules list box

 o Directories list box

          Mouse Button 1 - Refresh the files list box with files in the
          selected path or drive

 Object Module Details window

 o Segment Definitions list box

          Mouse Button 1 - Display the segment dump window

 o Group Definitions list box

          Mouse Button 1 - Display the group segments window

 Make File Creation

 o Path and file name field

          Mouse Button 1 - Select all files in the files list box

 o Make file list box

          Mouse Button 1 - Edit the make file.

 o Dependencies list box

          Mouse Button 1 - Edit the dependencies file


ΓòÉΓòÉΓòÉ <hidden> List box control ΓòÉΓòÉΓòÉ

To select an item in the list box, click with the mouse button 1 on the item's
title.

To select all the items in the list box, double-click with the mouse button 1
when the mouse is positioned on the directory path name.

To deselect a item that you have already selected, click with the mouse button
1 on the item's title.

To deselect all the items in the list box, double-click with the mouse button 2
when the mouse is positioned on the directory path name.


ΓòÉΓòÉΓòÉ <hidden> Alternative View ΓòÉΓòÉΓòÉ

Some list boxes show items that have both a title (or name) and a file name
associated with them. For example, the list box in the Project Control window
can list projects by their titles or project control files.

Select Alt. View from the System Menu pulldown or press F8 to switch between
the different formats.


ΓòÉΓòÉΓòÉ <hidden> Base and composite projects ΓòÉΓòÉΓòÉ

A project is either a base project or a composite project. A base project has
the following characteristics:

 o A language profile

   The language profile lets the WorkFrame/2* know which compiler, linker,
   debugger and make utility to use for your project.

 o A title

   The project's title is used in title bars and in list boxes to identify the
   project.

 o A directory

   All files that comprise a project exist in this directory. If you want to
   have files in different directories, create a composite project.

 o A target file

   The target file is the product you want to produce from a project.
   Typically, it is either an executable file or a library.

 o A make file

   The make file is used by the make utility to create the target file from the
   other project files.

 o Options

   You can set the options used when compiling, linking, debugging, running,
   and making your project.

 A project appears within the WorkFrame/2* as a window containing a list of the
 project's files. Actions can be performed on the project as a whole or on
 individual files.

 A composite project is a collection of base projects or other composite
 projects. Therefore, you can create a hierarchy of projects. For example, you
 could create five base projects to build two executable files and three
 dynamic link libraries (DLLs). The three DLL projects could then be part of a
 composite DLL project. Finally, the DLL composite project and two base
 projects for the executable files could be part of an overall composite
 project. With this arrangement, you could:

 o Make any of the 5 base projects individually

 o Make the DLL composite project

 o Make all the projects together.


ΓòÉΓòÉΓòÉ <hidden> Current project ΓòÉΓòÉΓòÉ

The current project is the project the actions are performed on.

If a project window is active, it is the current project.

If no project window is active, the last one to be active is the current
project.


ΓòÉΓòÉΓòÉ <hidden> Dragging From a List Box ΓòÉΓòÉΓòÉ

To drag items from a list box to a target:

  1. Select the items you want to drag by single-clicking with mouse button 1.

  2. Hold down the mouse button 2 and move the mouse from the source list box
     to the target area. Release the mouse button when the mouse pointer is
     over the target area.

 Outside of valid target areas, the mouse pointer looks like a circle with a
 line through it.

 To stop the drag, release the mouse button over the source list box or outside
 a valid target area.


ΓòÉΓòÉΓòÉ <hidden> Installation directory ΓòÉΓòÉΓòÉ

The installation directory is the directory where the WorkFrame/2* product is
installed. This directory was specified from the installation program and
contains:

 o Project Control Files (which have the extension .PRJ).

 o Preference Files (which have the extension .INI).

 o Language Profiles (which have the extension .PRF).

 o Backup Files (which have the extension .BAK).

 The extensions listed above are default extensions and may be different on
 some systems.


ΓòÉΓòÉΓòÉ <hidden> Language Profile ΓòÉΓòÉΓòÉ

Each project you develop must have an associated language profile. The language
profile defines a number of things, including:

 o The executable files for the compiler, linker, debugger, and make utility to
   be used for the project.
 o The dynamic link libraries that let you specify options for the above
   programs.
 o The default invocation string (if applicable) for the make utility and
   debugger program.
 o Search paths for include files and libraries.

 If a language product is designed to be used with the WorkFrame/2* product, it
 will likely come with a language profile. However, if you have a language
 product that is not designed for use with the WorkFrame/2* product, you can
 use the Language profile management option from the Tools pulldown to create
 one. The WorkFrame/2* product also provides a default language profile that
 you can modify for use with most compilers.


ΓòÉΓòÉΓòÉ <hidden> Substitution Variables ΓòÉΓòÉΓòÉ

Substitution variables are symbols you can specify as invocation parameters.

The WorkFrame/2* product supports the following substitution variables:

 %a...%z   Will be replaced by all the file names selected in the corresponding
           listbox. The file names will be separated by the characters
           specified between the 'a' and the '%' of the %z substitution
           variable.

           For example, if the selected files are cat.obj, dog.obj, and
           bird.obj, the substitution variable %a+-%z will result in the string

                      cat.obj+-dog.obj+-bird.obj

           The only substitution variable allowed within the %a...%z
           substitution variables are %% and %d.

 %d        Will be replaced with the directory of the current project. Use this
           substitution variable to qualify the name of file as in %d\%f or
           %d\%n.%e.

 %e        Will be replaced by the extension (without the period) of the first
           selected file.

 %f        Will be replaced with the first file selected in the corresponding
           listbox.

           Specifying %f is the same as specifying %n.%e.

 %m        Will be replaced by the make file name specified when the project
           was created.

 %n        Will be replaced by the file name (without an extension) of the
           first selected file.

 %o        Will be replaced by the target file name specified when the project
           was created.

 %r        Will be replaced by the run options set for the current project.

 %%        Will be replaced by a % symbol.


ΓòÉΓòÉΓòÉ <hidden> Project directory ΓòÉΓòÉΓòÉ

The project directory is the directory where all the files of a project are
stored.


ΓòÉΓòÉΓòÉ <hidden> Subproject ΓòÉΓòÉΓòÉ

A subproject is one of the projects within a composite project.


ΓòÉΓòÉΓòÉ <hidden> Target file ΓòÉΓòÉΓòÉ

The target file is the file which will be the product of the project.
Typically, it is either an executable file or dynamic link library.

The name of the target file is first specified when the project is created.


ΓòÉΓòÉΓòÉ <hidden> Target project ΓòÉΓòÉΓòÉ

The target project is the subproject that the Debug and Run actions are
performed on a composite project.


ΓòÉΓòÉΓòÉ <hidden> Temporary project ΓòÉΓòÉΓòÉ

Temporary projects provide a quick way of creating a project. Suppose you had a
directory which contained several files that you wanted to become part of a new
project. Here's how you could create the new project.

  1. Using the File Control window, move to the directory containing the files.

  2. Select the Temporary Project

     The newly created temporary project would show up in the Project Control
     window.

  3. Select New in the Project Control window to open the New Project window.

  4. Drag the name of the temporary project from the Project Control window to
     the New Project window.

     The controls in the New Project

  5. Change the Project description and Project file name to identify the new
     project. You can also change the other options as required.

  6. Select OK

 You can also use a temporary project to manipulate the files in a directory as
 if they were part of a permanent project.


ΓòÉΓòÉΓòÉ <hidden> LIB0001E ΓòÉΓòÉΓòÉ

LIB0001E: Error: Invalid record format at offset offset in file file name.

The object has an invalid record format. offset indicates the byte offset from
the beginning of the file, where the error was detected.

Recovery

If file name is an object file, recompile the object to ensure that it is built
properly.

If file name is a library file, use the library listing file to identify and
replace the object causing the error.

If the file was provided to you, notify the source from whom the file was
received.


ΓòÉΓòÉΓòÉ <hidden> LIB0002E ΓòÉΓòÉΓòÉ

LIB0002E: Warning: Duplicate symbol symbol name in object module name in
library library name ignored.

The symbol (symbol name) in the object module (module name) already exists in
the target library (library name).

The first occurrence of the symbol in the library takes precedence when the
linker resolves the symbol.

Recovery

Remove all but one of the modules defining the symbol from the library. This
message is a warning and can be ignored.


ΓòÉΓòÉΓòÉ <hidden> LIB0003E ΓòÉΓòÉΓòÉ

LIB0003E: Error (%1): Redefinition of module module name in library library
name ignored.

The module module name already exists in the target library.

Recovery

To replace the object in the target library, delete the object from the
library, then add the new object.


ΓòÉΓòÉΓòÉ <hidden> LIB0004E ΓòÉΓòÉΓòÉ

LIB0004E: Error: Cannot locate module module name.

The Library utility cannot delete or extract the object module because it
cannot find it in the library.

Recovery

Ensure that the correct source library and object module name is specified.


ΓòÉΓòÉΓòÉ <hidden> LIB0005E ΓòÉΓòÉΓòÉ

LIB0005E: Unknown Error - All changes abandoned.

The library utility had an unexpected fatal error during the last operation.

An attempt was made to recover the original library from its backup, if it had
already existed.

Recovery

Retry the operation, and if the error persists, report the problem to the IBM
representative.


ΓòÉΓòÉΓòÉ <hidden> LIB0006E ΓòÉΓòÉΓòÉ

LIB0006E: General Failure.

The Library utility had an unexpected non-fatal error during the last
operation. The success or failure of the operation can be determined by other
messages.

Recovery

If the other messages indicate that the operation failed, then recover the
original library file from the backup file created. The backup file will exist
on the same directory as the original library and have the same name, but with
the extension "IBM".


ΓòÉΓòÉΓòÉ <hidden> LIB0007E ΓòÉΓòÉΓòÉ

LIB0007E: Error: Cannot open file file name.

The Library utility cannot open the file named in the message.

Recovery

Ensure that the file exists, and is not being used by another process.


ΓòÉΓòÉΓòÉ <hidden> LIB0008E ΓòÉΓòÉΓòÉ

LIB0008E: Error: Cannot read file file name.

The Library utility cannot read the file.

Recovery

Check the system to ensure that the file can be read successfully. Ensure that
it is a valid library or object file.


ΓòÉΓòÉΓòÉ <hidden> LIB0009E ΓòÉΓòÉΓòÉ

LIB0009E: Error: Cannot write to file file name.

The Library utility cannot write to the file.

Recovery

Check the conditions below and take the appropriate corrective action:

 o The file has the read only attribute set.

   Action: Clear the read only attribute on the file or use a different file
   name.

 o Attempted to write to a read only LAN drive.

   Action: Get write access to the drive from the LAN administrator, or use a
   different drive.

 o Attempted writing to a read only media.

   Action: Choose a different media.

 o The file is being used by another process.

   Action: Wait for the termination of the other process or cancel the other
   process using the file.

 o There is insufficient disk space.

   Action: Free up space on the target disk, or use a different target disk.


ΓòÉΓòÉΓòÉ <hidden> LIB0010E ΓòÉΓòÉΓòÉ

LIB0010E: Error: Out of Memory.  All changes abandoned.

There was insufficient available memory on the system to complete the requests.

Recovery

Free up storage by terminating one or more current processes and retry the
action.


ΓòÉΓòÉΓòÉ <hidden> LIB0011E ΓòÉΓòÉΓòÉ

LIB0011E: Error: Out of space in the extended dictionary.

A limit of 64K maximum size for the extended dictionary was reached.

Recovery

Break the library into 2 or more smaller libraries.

The library can be built without the extended dictionary. However, this will
slow down the link process.


ΓòÉΓòÉΓòÉ <hidden> LIB0012E ΓòÉΓòÉΓòÉ

LIB0012E: Error: Maximum number of pages exceeded. Redo with larger page size.

The maximum number of pages for the object modules have been exceeded. Valid
pagesizes are 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, 16384, and
32768.

Recovery

Increase the page size to the next larger valid pagesize. Retry the operation.


ΓòÉΓòÉΓòÉ <hidden> LIB0013E ΓòÉΓòÉΓòÉ

LIB0013E: Error: Object module module name does not contain an end of module
record.

Recovery

Rebuild the object file or replace the object module in the library.


ΓòÉΓòÉΓòÉ <hidden> LIB0014E ΓòÉΓòÉΓòÉ

LIB0014E: Error: Cannot access file file name.

The Library utility cannot access the file.

Recovery

Check that the file exists and is accessible.


ΓòÉΓòÉΓòÉ <hidden> LIB0015E ΓòÉΓòÉΓòÉ

LIB0015E: Error : Invalid object file object name.

The object selected is not a valid object file or library.

Recovery

Rebuild the object or library.


ΓòÉΓòÉΓòÉ <hidden> LIB0016E ΓòÉΓòÉΓòÉ

LIB0016E: Error : Unable to write to the library library name.

The Library utility cannot write to the library.

Recovery Check the conditions below and take the appropriate corrective action:

 o The library has the read only attribute set.

   Action: Clear the read only attribute on the target library or use a
   different target library name.

 o The library resides on a read only LAN drive.

   Action: Get write access to the drive from the LAN administrator, or use a
   different drive.

 o The library is being used by another process.

   Action: Wait for the termination of the other process or cancel the other
   process using the target library file.

 o There is insufficient disk space.

   Action: Free up space on the target disk, or use a different target disk.


ΓòÉΓòÉΓòÉ <hidden> LIB0017E ΓòÉΓòÉΓòÉ

LIB0017E: Error : The dictionary is out of space. Split the library and retry.

The IBM library utility supports a maximum of 509 blocks for the dictionary.
This limit has been reached.

Recovery

Break the library into 2 or more smaller libraries.  This may also improve the
library build time as well as the link times.


ΓòÉΓòÉΓòÉ <hidden> DDE6001E ΓòÉΓòÉΓòÉ

DDE6001E Internal error - DDE3MAKE parameter error

Incorrect calling sequence to DDE3MAKE.DLL

Recovery

None.  Report the error to your IBM Service Representative.


ΓòÉΓòÉΓòÉ <hidden> DDE6002E ΓòÉΓòÉΓòÉ

DDE6002E Internal error - insufficient heap.

DDE3MAKE.DLL cannot acquire enough storage to complete the make file generation

Recovery

Close other sessions, or make more room on the disk for OS/2's swap file.


ΓòÉΓòÉΓòÉ <hidden> DDE6003E ΓòÉΓòÉΓòÉ

DDE6003E Internal window I/O error.

Internal error communicating to the shell's windows.

Recovery

None.  Report the error to your IBM Service Representative.


ΓòÉΓòÉΓòÉ <hidden> DDE6004E ΓòÉΓòÉΓòÉ

DDE6004E Error calling compiler DLL

DDE3MAKE cannot successfully call a function in the compiler DLL.

Recovery

Ensure that the compiler DLL is on the LIBPATH.


ΓòÉΓòÉΓòÉ <hidden> DDE6005E ΓòÉΓòÉΓòÉ

DDE6005E Error calling linker DLL.

DDE3MAKE cannot successfully call a function in the linker DLL.

Recovery

Ensure that the linker DLL is on the LIBPATH.


ΓòÉΓòÉΓòÉ <hidden> DDE6006E ΓòÉΓòÉΓòÉ

DDE6006E Files selected are incompatible with selected actions

There are no input files selected for the actions you selected. Messages
preceding this one will detail individual problems with the actions you
selected.

Recovery

Correct the problems detailed in the preceding messages.


ΓòÉΓòÉΓòÉ <hidden> DDE6007E ΓòÉΓòÉΓòÉ

DDE6007W Action COMPILE selected, but no compiler source files are selected.

You selected the action 'COMPILE', but selected no compiler source files.  The
other actions you selected will be used to create a make file, but no compile
steps will be generated.

Recovery

Either accept the makefile 'as-is', or select compiler source files, and
re-create the makefile.


ΓòÉΓòÉΓòÉ <hidden> DDE6008E ΓòÉΓòÉΓòÉ

DDE6008E Action LINK selected, but no object files to link.

The action 'LINK' was selected, but Make File Creation cannot identify any
object files to link.  The other actions you selected will be used to create a
make file, but no link step will be generated.

Recovery

Either accept the makefile 'as-is', or do one or both of the following:

  1. Also select the action 'COMPILE' and compiler source files, and re-run
     Make File Creation.

  2. Select appropriate object files, and re-run Make File Creation.


ΓòÉΓòÉΓòÉ <hidden> DDE6009E ΓòÉΓòÉΓòÉ

DDE6009E Action RESOURCE COMPILE selected, but no .RC files selected

You selected the action 'RESOURCE COMPILE', but selected no resource compiler
source files (extension .RC).  The other actions you selected will be used to
create a make file, but no resource compile steps will be generated.

Recovery

Either accept the makefile 'as-is', or select resource compiler source files,
and re-create the makefile.


ΓòÉΓòÉΓòÉ <hidden> DDE6010E ΓòÉΓòÉΓòÉ

DDE6010E Action IPF COMPILE selected, but no .IPF files selected.

You selected the action 'IPF COMPILE', but selected no IPF compiler source
files (extension .IPF).  The other actions you selected will be used to create
a make file, but no IPF compile steps will be generated.

Recovery

Either accept the makefile 'as-is', or select IPF compiler source files, and
re-create the makefile.


ΓòÉΓòÉΓòÉ <hidden> DDE6011E ΓòÉΓòÉΓòÉ

DDE6011E Action MESSAGE FILE CREATION selected, but no .TXT files selected

You selected the action 'MESSAGE FILE CREATION', but selected no message source
files (extension .TXT).  The other actions you selected will be used to create
a make file, but no message file creation steps will be generated.

Recovery

Either accept the makefile 'as-is', or select message source files, and
re-create the makefile.


ΓòÉΓòÉΓòÉ <hidden> DDE6012E ΓòÉΓòÉΓòÉ

DDE6012E Action MESSAGE FILE BIND selected, but no .MSG files available.

You selected the action 'MESSAGE FILE BIND', but Make File Creation could not
identify any .MSG files.  Either you did not select any, or you did not select
MESSAGE FILE CREATION and appropriate .TXT files. The other actions you
selected will be used to create a make file, but no MSGBIND step will be
generated.

Recovery

Either accept the makefile 'as-is', or select .MSG files, or .TXT files and
'MESSAGE FILE CREATION' and re-create the makefile.


ΓòÉΓòÉΓòÉ <hidden> DDE6013E ΓòÉΓòÉΓòÉ

DDE6013E Action MESSAGE FILE BIND selected, but a link step cannot be created.

You selected the action 'MESSAGE FILE BIND', but did not select actions or
files for the LINK step.

Recovery

Either accept the makefile 'as-is', or correct as follows:

  1. If action LINK was selected, there will be a message giving the problem
     with the link step.  Correct that problem, and re-run the make file.

  2. If action LINK was not selected, select the LINK action, and re-create the
     makefile.


ΓòÉΓòÉΓòÉ <hidden> DDE6014E ΓòÉΓòÉΓòÉ

DDE6014E No message for DDE6014E

This message should never appear

Recovery

None.  Report the error to your IBM Service Representative.


ΓòÉΓòÉΓòÉ <hidden> DDE6015E ΓòÉΓòÉΓòÉ

DDE6015E Invalid include name include name found in file file name.

File name found on an include statement is not recognized as being a valid file
name.  It may be syntactically incorrect, although symbolic file names will
also generate this error.  Occurrences of the indicated file in the makefile
will be commented out.

Recovery

If the statement in the file is syntactically incorrect, correct the source
file, and re-run make file generation.  If the statement is syntactically
correct, you may ignore the error, and, optionally, manually correct the
generated make files.


ΓòÉΓòÉΓòÉ <hidden> DDE6016E ΓòÉΓòÉΓòÉ

DDE6016E Indeterminate include name include name found in file file name

DDE3MAKE cannot determine the name of the include file.  The source file may be
syntactically incorrect, although a symbolic file name will also generate this
error.  Occurrences of the indicated file in the makefile will be commented
out.

Recovery

If the statement in the file is syntactically incorrect, correct the source
file, and re-run make file generation.  If the statement is syntactically
correct, you may ignore the error, and, optionally, manually correct the
generated make files.


ΓòÉΓòÉΓòÉ <hidden> DDE6020E ΓòÉΓòÉΓòÉ

DDE6020E Include files nested too deeply.

Make File Creation will only accept source files nested to a depth of 30 files.
One of your source files has nested includes deeper than this.  The location of
the problem will be indicated by a copy of this message in the dependency file.

Recovery

Change your source to nest includes less deeply, or accept the makefile
'as-is'.


ΓòÉΓòÉΓòÉ <hidden> DDE6025W ΓòÉΓòÉΓòÉ

DDE6025W Main makefile window cannot display complete file.

The resulting make file is too big to fit into the display listbox. The
complete make file will be saved if you select OK.

Recovery

None - for information only


ΓòÉΓòÉΓòÉ <hidden> DDE6026W ΓòÉΓòÉΓòÉ

DDE6026W Dependency makefile window cannot display complete file.

The resulting dependency file is too big to fit into the display listbox.  The
complete dependency file will be saved if you select OK.

Recovery

None - for information only


ΓòÉΓòÉΓòÉ <hidden> DDE6027E ΓòÉΓòÉΓòÉ

DDE6027E Error writing spill file for file name

The work file used for either the make file or the dependency file could not be
written properly.

Recovery

Check that sufficient space remains on the disk containing the project.


ΓòÉΓòÉΓòÉ <hidden> DDE6028E ΓòÉΓòÉΓòÉ

DDE6028E Cannot access file file name

The indicated file could not be found.  It may exist but Make File Creation
could not open it.

Recovery

You may accept the makefile 'as-is'.  Occurrences of the indicated file in the
makefile will be commented out.  You may also correct your source and re-run
make file creation.


ΓòÉΓòÉΓòÉ <hidden> DDE6029E ΓòÉΓòÉΓòÉ

DDE6029E Cannot locate file file_name on path path

DDE3MAKE cannot find the include file specified.  A symbolic file name in the
original source file can also generate this error. Occurrences of the indicated
file in the makefile will be commented out.

Recovery

  1. Verify that the INCLUDE environment variable is set up correctly.

  2. Verify that the file exists.

  3. The error may be ignored.  The file will appear in the generated make
     files, but it will not be checked for any further include files.


ΓòÉΓòÉΓòÉ <hidden> DDE6030E ΓòÉΓòÉΓòÉ

DDE6030E Cannot open file file name.

DDE3MAKE was able to find the file, but could not open it.  Another process may
have the file open, or the file name may specify a directory.  Occurrences of
the indicated file in the makefile will be commented out.

Recovery

Halt the other process or correct the source in which this file name appears.


ΓòÉΓòÉΓòÉ <hidden> DDE6031E ΓòÉΓòÉΓòÉ

DDE6031E Error reading file file name.

DDE3MAKE encountered an error while reading the file.  If the file is on a
removable medium, you may have removed it.  If it is on a LAN, the connection
to the LAN server may have been broken.

Recovery

Retry the makefile generation.  If the problem persists, contact your IBM
Service Representative.


ΓòÉΓòÉΓòÉ <hidden> DDE6032E ΓòÉΓòÉΓòÉ

DDE6032E Action LINK selected, but project target file is not a .LIB, .EXE, or
.DLL.

You have selected the action 'Link', but the target of this project is not a
library or executable.  Libraries are identified by the extension '.LIB', and
executables by the extensions '.EXE' and '.DLL'. The other actions you selected
will be used to create a make file, but no Link or Message Bind steps will be
created.

Recovery

Either accept the makefile 'as-is', or change the project target to a linkable
target and re-create the make file.


ΓòÉΓòÉΓòÉ <hidden> DDE6033E ΓòÉΓòÉΓòÉ

DDE6033E Environment INCLUDE variable contains invalid directory dirname

The environment variable INCLUDE contains a directory name (dirname) which is
longer than allowed by the operating system.  The maximum allowed is 255
characters. Make file generation cannot proceed.

Recovery

Correct the INCLUDE environment variable and re-run make file generation.


ΓòÉΓòÉΓòÉ <hidden> DDE6034E ΓòÉΓòÉΓòÉ

DDE6034E Environment INCLUDE variable contains directory dirname which does not
exist

The environment variable INCLUDE contains a directory name (dirname) which
either does not exist, or which is not accessible. Make file generation cannot
proceed.

Recovery

Either accept the makefile 'as-is', or correct the INCLUDE environment variable
and re-run make file generation.


ΓòÉΓòÉΓòÉ <hidden> DDE6035E ΓòÉΓòÉΓòÉ

DDE6035E No message for DDE6035E

This message should never appear.

Recovery

None.  Report the error to your IBM Service Representative.


ΓòÉΓòÉΓòÉ <hidden> DDE6036E ΓòÉΓòÉΓòÉ

DDE6036E No message for DDE6036E

This message should never appear.

Recovery

None.  Report the error to your IBM Service Representative.


ΓòÉΓòÉΓòÉ <hidden> DDE6037E ΓòÉΓòÉΓòÉ

DDE6037E No message for DDE6037E

This message should never appear.

Recovery

None.  Report the error to your IBM Service Representative.


ΓòÉΓòÉΓòÉ <hidden> DDE6038E ΓòÉΓòÉΓòÉ

DDE6038E No message for DDE6038E

This message should never appear.

Recovery

None.  Report the error to your IBM Service Representative.


ΓòÉΓòÉΓòÉ <hidden> DDE6039E ΓòÉΓòÉΓòÉ

DDE6039E No message for DDE6039E

This message should never appear.

Recovery

None.  Report the error to your IBM Service Representative.


ΓòÉΓòÉΓòÉ <hidden> DDE6040E ΓòÉΓòÉΓòÉ

DDE6040E No message for DDE6040E

This message should never appear.

Recovery

None.  Report the error to your IBM Service Representative.


ΓòÉΓòÉΓòÉ <hidden> WorkFrame/2* Messages ΓòÉΓòÉΓòÉ

 WorkFrame/2* messages.


ΓòÉΓòÉΓòÉ <hidden> DDE30401 ΓòÉΓòÉΓòÉ

The bitmap cannot be loaded: return code = return code.

The bitmap cannot be loaded into memory.  Return codes are:

 1 - Could not open the file
 2 - Not a valid bitmap type
 3 - Error creating the presentation space
 4 - Memory allocation error
 5 - Unknown bitmap format

 Recovery

 Return Code 1   If the selected file is valid, verify that the file is not
                 being used by another process.

 Reason Code 2   Ensure that the file is a valid bitmap. You cannot load icons
                 or pointers in this situation.

 Reason Code 3   The problem may be heap related; close some windows or other
                 applications, and retry the loading the bitmap.

 Reason Code 4   Shut down some other processes to free memory.

 Reason Code 5   This bitmap type is not supported.  Select a different one.


ΓòÉΓòÉΓòÉ <hidden> DDE30405 ΓòÉΓòÉΓòÉ

The tool cannot be added to the tools pulldown. Maximum number of tools allowed
is 100.

The tools pulldown contains the maximum number of tools allowed.

Recovery

Remove any unused tools from the list of configured tools, then add the new
tool.


ΓòÉΓòÉΓòÉ <hidden> DDE30409 ΓòÉΓòÉΓòÉ

Creation of dependency file failed: return code = return code.

The Create make file utility cannot create either a temporary dependency file
or a permanent dependency file.

Recovery

Ensure there is enough space on the drive and that the file is not held by
another process, then retry the operation.


ΓòÉΓòÉΓòÉ <hidden> DDE30410 ΓòÉΓòÉΓòÉ

Error switching to drive or directory: return code = return code.

The WorkFrame/2* either cannot switch to the current project's working
directory or it cannot change directories. Another process may be using the
directory.

Recovery

If the drive cannot be found, it may be a redirected drive on a local area
network that is unavailable. If this is the case, you may be able to reaccess
the local area network drive. Ensure that the drive or directory is accessible,
then retry the operation.


ΓòÉΓòÉΓòÉ <hidden> DDE30414 ΓòÉΓòÉΓòÉ

The editor specified cannot be found.

The file you specified in the Current editor field cannot be found. If the name
was qualified with a drive and a directory, the file does not exist. If the
name was unqualified, the file does not exist in the directories defined by the
PATH environment variable.

Recovery

If you did not specify a path and the directory the editor resides in is not in
the PATH environment variable, include the path and select OK. Do not rely on
the WorkFrame/2* using the current directory for locating the editor.

You can also select a windowed command prompt and copy the editor files to a
directory in the path.


ΓòÉΓòÉΓòÉ <hidden> DDE30415 ΓòÉΓòÉΓòÉ

The name of the editor is missing.

The Current editor entry field is blank; it requires the name of a valid
editor.

Recovery

Enter a valid name and select OK or select Cancel to use the name of the
previous editor.


ΓòÉΓòÉΓòÉ <hidden> DDE30417 ΓòÉΓòÉΓòÉ

The tool cannot be loaded: return code = return code.

The WorkFrame/2* cannot start the tool you selected.

Recovery

Depending on the return code, you may be able to restart the action. You may
need to change the information about that tool, such as the path, in the
Configure window.


ΓòÉΓòÉΓòÉ <hidden> DDE30420 ΓòÉΓòÉΓòÉ

No file has been selected from the Files listbox.

At least one file must be selected from the Files listbox.

Recovery

Select one or more files and select Start, or select Cancel to exit from the
window.


ΓòÉΓòÉΓòÉ <hidden> DDE30422 ΓòÉΓòÉΓòÉ

The name of a file to save the listbox to is missing.

You have chosen to save the contents of a listbox to a file and selected the OK
button without entering the name of the file to save the listbox to.

Recovery

Enter a valid name and select Save or select Cancel to exit from the window
without saving the listbox.


ΓòÉΓòÉΓòÉ <hidden> DDE30425 ΓòÉΓòÉΓòÉ

Unusable language eyecatcher: eyecatcher name.

An 8-character eyecatcher identifies the language associated with a project.
The eyecatcher associated with the selected project does not correspond to an
existing language profile. A possible cause is that a language has been deleted
after projects have been created for it.

Recovery

Choose one action:

  1. If the project is no longer valid, delete it.
  2. Change the project to use a different language. Any options contained
     within the project file are lost.
  3. Use the Language profile tool to re-create the language using the same
     eyecatcher.  All the existing project options are kept.


ΓòÉΓòÉΓòÉ <hidden> DDE30429 ΓòÉΓòÉΓòÉ

Project project-name is not valid.

A file with an extension of .PRJ has been found in the home directory.  This
file is not a valid project information file.

Recovery

If the file identified by project name is not valid, switch to the home
directory and delete it. If the file is a valid project, the WorkFrame/2* may
have been in the process of writing the file but could not close it properly. A
backup copy called xxxxx.BAK is created where xxxxx is the file name indicated
in the message. Switch to the WorkFrame/2* home directory and copy xxxxx.BAK to
xxxxx.PRJ to return to the point before the operation failed.


ΓòÉΓòÉΓòÉ <hidden> DDE30430 ΓòÉΓòÉΓòÉ

Language profile: profile name cannot be accessed: return code = return code.

The indicated language profile cannot be opened or read.

Recovery

Depending on the return code from the OS/2* operating system, you may have a
sharing conflict with another process. Switch to the other session and release
the file.

If this error occurred during WorkFrame/2* initialization, end and retry the
WorkFrame/2*. Otherwise, just retry the process you were attempting.


ΓòÉΓòÉΓòÉ <hidden> DDE30431 ΓòÉΓòÉΓòÉ

The language profile profile name is not valid.

A file with an extension of .PRF has been found in the WorkFrame/2* home
directory. This file is not a valid language profile.

Recovery

If the file identified by profile name is not valid, switch to the WorkFrame/2*
home directory and delete it.

If the file is a valid language, the WorkFrame/2* may have been in the process
of writing the file but could not close it properly. A backup copy called
xxxxx.PBK is created where xxxxx is the file name indicated in the message.
Switch to the WorkFrame/2* home directory and copy xxxxx.PBK to xxxxx.PRF to
return to the point before the operation failed.

If the error occurred during startup of the WorkFrame/2*, start it again.


ΓòÉΓòÉΓòÉ <hidden> DDE30434 ΓòÉΓòÉΓòÉ

Error loading the WorkFrame/2* profile.

The WorkFrame/2* initialization cannot load the user profile IBMWF.INI from the
home directory. One of three conditions has occurred:

  1. The WorkFrame/2* cannot find the home directory by looking in OS2.INI.
  2. The profile failed to open.
  3. The file has been corrupted.

 Recovery

 Only the second case is recoverable. If the file is being held by another
 process, release it and restart the WorkFrame/2*.

 In all other situations, you will have to install the WorkFrame/2* again. The
 environment will be preserved if you specify the same home directory, but you
 will have to specify your preferences again.


ΓòÉΓòÉΓòÉ <hidden> DDE30435 ΓòÉΓòÉΓòÉ

Dynamic link library for Make file creation cannot be loaded: return code =
return code.

The WorkFrame/2* cannot load the dynamic link library for the Make file
creation tool. The name of the dynamic link library is DDE3MAKE.DLL.

Recovery

Depending on the OS/2* operating system return code, it is possible that the
dynamic link library does not exist or that the directory containing the
dynamic link library is not in the LIBPATH environment variable. If the dynamic
link library does not exist then you must install the WorkFrame/2* again. If it
does exist, copy this dynamic link library to a directory in the LIBPATH
variable or modify your LIBPATH statement in your CONFIG.SYS file. The latter
way will require you to reboot the OS/2* operating system.


ΓòÉΓòÉΓòÉ <hidden> DDE30436 ΓòÉΓòÉΓòÉ

Creation of make file failed: return code = return code.

The Make File Creation utility cannot create either a temporary make file or
the permanent make file.

Recovery

There may not be enough space on the drive, or the file may be held by another
process. Correct the action and retry the action.


ΓòÉΓòÉΓòÉ <hidden> DDE30437 ΓòÉΓòÉΓòÉ

Make file file_name already exists.  Do you want to overwrite it?

You selected the OK button from Make File Creation window. The make file
already exists. If you started the tool to maintain your dependencies list, you
probably do not want to overwrite the current make file.

Recovery

Select Yes to replace both the dependencies file and the make file.

Select No to leave your original make file left as it is. Only the dependencies
file will be replaced.

Select Cancel if you do not want to overwrite either file.


ΓòÉΓòÉΓòÉ <hidden> DDE30439 ΓòÉΓòÉΓòÉ

More than 500 items are selected.

You have selected more than 500 items in the listbox. The maximum allowed is
500.

Recovery

Reduce the number of selected items in the listbox to 500 or fewer, and retry
the action.


ΓòÉΓòÉΓòÉ <hidden> DDE30448 ΓòÉΓòÉΓòÉ

You must select at least one action from the Actions listbox.

You selected Start but no actions are selected in the Actions listbox.

Recovery

Select one or more actions, or select Cancel to exit from the window.


ΓòÉΓòÉΓòÉ <hidden> DDE30450 ΓòÉΓòÉΓòÉ

WorkFrame/2* internal error.

An unexpected situation occurred within the WorkFrame/2*. The return code
indicates the component that received the error.

Recovery

Make note of the error number listed in the message and document the tasks you
performed before receiving this message. Submit this information to a service
representative.


ΓòÉΓòÉΓòÉ <hidden> DDE30451 ΓòÉΓòÉΓòÉ

No target windows are available to copy to.

You have highlighted items in a source listbox and selected Copy, but there are
no windows to copy the items to. You can copy files to other project windows,
to windows for adding or changing tools, or to windows for creating or changing
projects.

Recovery

Start the window to be the target of the copy operation and retry copying.


ΓòÉΓòÉΓòÉ <hidden> DDE30461 ΓòÉΓòÉΓòÉ

Printer not ready.

You have asked to print the listbox, but the printer is not ready.

Recovery

Turn the printer on and select OK. Or select Cancel to stop the print
operation.


ΓòÉΓòÉΓòÉ <hidden> DDE30462 ΓòÉΓòÉΓòÉ

Printer out of paper.

Recovery

Supply the printer with paper, and select OK. Or select Cancel to stop the
print operation.


ΓòÉΓòÉΓòÉ <hidden> DDE30463 ΓòÉΓòÉΓòÉ

Dynamic link library for language profile cannot be loaded: return code =
return code.

The WorkFrame/2* cannot load DDE3PROF.DLL to change a language profile.
Depending on the OS/2* operating system return code, the dynamic link library
may not exist or the directory containing the dynamic link library is not in
the LIBPATH environment variable.

Recovery

If the dynamic link library does not exist, you must install the WorkFrame/2*
again.

If it does exist, copy the dynamic link library to a directory in the LIBPATH
variable or modify your LIBPATH statement in your CONFIG.SYS file and restart
the OS/2 operating system.


ΓòÉΓòÉΓòÉ <hidden> DDE30464 ΓòÉΓòÉΓòÉ

WorkFrame/2* profile cannot be saved: return code = return code.

Your preferences cannot be saved.

Recovery

Depending on the return code, you have either run out of space on the drive, or
the file IBMWF.INI is tied up by another process. Correct the problem and retry
the operation.


ΓòÉΓòÉΓòÉ <hidden> DDE30469 ΓòÉΓòÉΓòÉ

Error processing project file project-name return code = return code.

The indicated project file cannot be opened or read. Depending on the return
code, another process may be using the file.

Recovery

Look up the OS/2* operating system return code description for a more detailed
description of the problem. If another process is using the file, switch to the
other session and release the file. Retry the action.


ΓòÉΓòÉΓòÉ <hidden> DDE30477 ΓòÉΓòÉΓòÉ

Error writing project project name: return code = return code.

The WorkFrame/2* cannot write to the indicated project file. Depending on the
return code, another process may be using the file.

Recovery

Look up the OS/2* operating system return code description for a more detailed
description of the problem. If another process is using the file, switch to the
other session and release the file. Retry the action.


ΓòÉΓòÉΓòÉ <hidden> DDE30479 ΓòÉΓòÉΓòÉ

Do you want to cancel without saving changes?

You have modified your tools list and have selected the Cancel button.

Recovery

Select OK to exit the window without saving your changes.

Select Cancel to return to the window where you can select OK to accept your
changes. All changes are in effect for the current session only unless you save
the WorkFrame/2* profile.


ΓòÉΓòÉΓòÉ <hidden> DDE30480 ΓòÉΓòÉΓòÉ

Do you want to save the WorkFrame/2* profile?

You have chosen to end the WorkFrame/2*. Your profile has been modified, but
the changes have not been saved.

Recovery

Select Yes to save your changes. Select No to discard your changes. The
WorkFrame/2* will be closed.

Select Cancel to keep the WorkFrame/2* open.


ΓòÉΓòÉΓòÉ <hidden> DDE30481 ΓòÉΓòÉΓòÉ

Are you sure you want to end the WorkFrame/2*?

You have chosen to end the WorkFrame/2*. Confirm your request to close the
WorkFrame/2*.

Recovery

Select OK to close the WorkFrame/2*.

Select Cancel to keep the WorkFrame/2* open.


ΓòÉΓòÉΓòÉ <hidden> DDE30482 ΓòÉΓòÉΓòÉ

The object you have selected is not a valid executable file.

You can only copy an executable file or a project to this window. The object
you selected is neither.

Recovery

If you want to copy a file to be used as a WorkFrame/2* tool, ensure that the
file is a valid executable file. Retry the operation.


ΓòÉΓòÉΓòÉ <hidden> DDE30483 ΓòÉΓòÉΓòÉ

Cannot print listbox.

The contents of the listbox cannot be printed.

Recovery

Look at the OS/2* operating system return code, and determine your action. You
can also retry the print operation.


ΓòÉΓòÉΓòÉ <hidden> DDE30485 ΓòÉΓòÉΓòÉ

Cannot save listbox: return code = return code.

The listbox cannot be saved.

Recovery

Look at the OS/2* operating system return code, and determine your action. You
can also retry the save operation.


ΓòÉΓòÉΓòÉ <hidden> DDE30486 ΓòÉΓòÉΓòÉ

Error trying to select the session you asked for: return code = return code.

The session you selected cannot be started.

The item will be removed from the Switch list pulldown menu.

Recovery

Start the tool again.


ΓòÉΓòÉΓòÉ <hidden> DDE30489 ΓòÉΓòÉΓòÉ

The Switch list pulldown contains no items.

The WorkFrame/2* cannot build a list of available programs to include in the
Switch list pulldown. The operating system indicates there are no programs in
the OS/2* operating system Task List.

Therefore, you cannot use the Switch list pulldown.

Recovery

Start a tool and retry the action. Your tool should appear in OS/2* operating
system Task List.


ΓòÉΓòÉΓòÉ <hidden> DDE30490 ΓòÉΓòÉΓòÉ

A thread cannot be created: return code = return code.

A worker thread cannot be created.

If the error occurred when the WorkFrame/2* started, the WorkFrame/2* will
close. If the action occurred after the WorkFrame/2* started, the WorkFrame/2*
performance may be affected, but the WorkFrame/2* will not close.

Recovery

Too many threads may be active in the system. Try shutting down some active
programs and restart the WorkFrame/2*. Or retry the operation.


ΓòÉΓòÉΓòÉ <hidden> DDE30492 ΓòÉΓòÉΓòÉ

The title is missing.

A title must be provided before a tool can be added or changed. Your title is
missing or blank.

Recovery

Enter the title you want to use for this tool, and select OK.


ΓòÉΓòÉΓòÉ <hidden> DDE30493 ΓòÉΓòÉΓòÉ

A file name is missing.

A file name must be provided before a tool can be added or changed. Your file
name is missing or blank.

Recovery

Enter the file name of the tool, and select OK.


ΓòÉΓòÉΓòÉ <hidden> DDE30494 ΓòÉΓòÉΓòÉ

A prompt description is missing.

You have selected to have a prompt provided but have left the prompt
description area blank.

Recovery

Enter the prompt you want to use, and select OK.


ΓòÉΓòÉΓòÉ <hidden> DDE30403 ΓòÉΓòÉΓòÉ

Are you sure you want to cancel the action?

Recovery

Select OK to stop the current action; Cancel to let it continue.


ΓòÉΓòÉΓòÉ <hidden> DDE30404 ΓòÉΓòÉΓòÉ

Error occurred waiting for program to end: return code = return code.

An unexpected OS/2* operating system return code was returned while waiting for
the program to end.

Recovery

Check the OS/2* operating system documentation for the corrective action.


ΓòÉΓòÉΓòÉ <hidden> DDE30419 ΓòÉΓòÉΓòÉ

At least one file must be selected.

No file was selected from the current project window.

Recovery

Select a file from the current project window, and try the action again.


ΓòÉΓòÉΓòÉ <hidden> DDE30438 ΓòÉΓòÉΓòÉ

A project must be selected.

All the projects listed in the composite make window were deselected. At least
one project must be selected.

Recovery

Select at least one project from the window, and select the make action again.


ΓòÉΓòÉΓòÉ <hidden> DDE03442 ΓòÉΓòÉΓòÉ

String ended before matching '%z' for '%a' was found.

A %a substitution variable must be followed by a matching %z.

Recovery

Add a %z to the end of the string. Make sure the separator character or string
that is to be used between the file names is placed between the %a and %z
symbols. Or remove the %a substitution variable.


ΓòÉΓòÉΓòÉ <hidden> DDE30443 ΓòÉΓòÉΓòÉ

Only '%%', %d, or '%z' can follow '%a'.

A substitution variable other than %%, %d, or %z was found following a %a.

Recovery

Either remove the substitution variable, change it to a %%, %d, or %z, or add a
%z ahead of it.


ΓòÉΓòÉΓòÉ <hidden> DDE30444 ΓòÉΓòÉΓòÉ

Unrecognized substitution variable variable.

An unrecognized substitution variable was used. Recognized substitution
variables are %%, %a, %d, %e, %f, %m, %n, %o, %r, or %z.

Recovery

Change the substitution variable to a recognized substitution variable or
remove it.


ΓòÉΓòÉΓòÉ <hidden> DDE30445 ΓòÉΓòÉΓòÉ

String ended with a substitution variable symbol (%).

The last character was a % character. It must be followed by another character
to form a recognized substitution variable. Recognized substitution variables
are %%, %a, %d, %e, %f, %m, %n, %o, %r, or %z.

Recovery

Add the appropriate character to the end of the string to create a substitution
variable or delete the % character.


ΓòÉΓòÉΓòÉ <hidden> DDE30446 ΓòÉΓòÉΓòÉ

Option string after substitution is too big.

The size of the area needed to hold the string after substitution of the
substitution variables is so large that it cannot be used in later processing.
The size of the area after substitution cannot exceed 1024 characters.

This occurrence is often caused by selecting many files with the %a...%z
substitution sequence.

Recovery

Deselect some of the files and try again. If this solution fails, try using
fewer substitution variables in your options string.


ΓòÉΓòÉΓòÉ <hidden> DDE30447 ΓòÉΓòÉΓòÉ

'%z' can only be used following '%a'.

A %z occurred before a corresponding %a.

Recovery

Insert a %a substitution variable before the %z variable, or delete the %z
variable. Separate them by the character sequence that separates the file
names.


ΓòÉΓòÉΓòÉ <hidden> DDE30453 ΓòÉΓòÉΓòÉ

You cannot start the editor until the action has ended.

The program in the monitor has not finished running.

Recovery

Wait for the program to finish, and then start the editor.


ΓòÉΓòÉΓòÉ <hidden> DDE30454 ΓòÉΓòÉΓòÉ

Dynamic link library for compile options cannot be loaded: return code =
return code.

An error occurred when the dynamic link library for the compile options was
loaded. Depending on the OS/2* operating system return code, the dynamic link
library may not exist or the directory containing the dynamic link library is
not in the LIBPATH environment variable.

Recovery

Ensure that the name for the dynamic link library is correct in the language
profile.

Ensure that the dynamic link library is in the library path specified by the
LIBPATH variable in your CONFIG.SYS file. Copy the dynamic link library to a
directory in the LIBPATH variable or modify your LIBPATH statement in your
CONFIG.SYS file and restart the OS/2 operating system.


ΓòÉΓòÉΓòÉ <hidden> DDE30455 ΓòÉΓòÉΓòÉ

Dynamic link library for link options cannot be loaded: return code =
return code.

An error occurred when the dynamic link library for the link options was
loaded. Depending on the OS/2* operating system return code, the dynamic link
library may not exist or the directory containing the dynamic link library is
not in the LIBPATH environment variable.

Recovery

Ensure that the name for the dynamic link library is correct in the language
profile.

Ensure that the dynamic link library is in the library path specified by the
LIBPATH variable in your CONFIG.SYS file. Copy the dynamic link library to a
directory in the LIBPATH variable or modify your LIBPATH statement in your
CONFIG.SYS file and restart the OS/2 operating system.


ΓòÉΓòÉΓòÉ <hidden> DDE30456 ΓòÉΓòÉΓòÉ

Dynamic link library for run options cannot be loaded: return code =
return code.

An error occurred when the dynamic link library for the run options was loaded.
Depending on the OS/2* operating system return code, the dynamic link library
may not exist or the directory containing the dynamic link library is not in
the LIBPATH environment variable.

Recovery

Ensure that the name for the dynamic link library is correct in the language
profile.

Ensure that the dynamic link library is in the library path specified by the
LIBPATH variable in your CONFIG.SYS file. Copy the dynamic link library to a
directory in the LIBPATH variable or modify your LIBPATH statement in your
CONFIG.SYS file and restart the OS/2 operating system.


ΓòÉΓòÉΓòÉ <hidden> DDE30457 ΓòÉΓòÉΓòÉ

Dynamic link library for make options cannot be loaded: return code =
return code.

An error occurred when the dynamic link library for the make options was
loaded. Depending on the OS/2* operating system return code, the dynamic link
library may not exist or the directory containing the dynamic link library is
not in the LIBPATH environment variable.

Recovery

Ensure that the name for the dynamic link library is correct in the language
profile.

Ensure that the dynamic link library is in the library path specified by the
LIBPATH variable in your CONFIG.SYS file. Copy the dynamic link library to a
directory in the LIBPATH variable or modify your LIBPATH statement in your
CONFIG.SYS file and restart the OS/2 operating system.


ΓòÉΓòÉΓòÉ <hidden> DDE30458 ΓòÉΓòÉΓòÉ

Dynamic link library for debug options cannot be loaded: return code =
return code.

An error occurred when the dynamic link library for the debug options was
loaded. Depending on the OS/2* operating system return code, the dynamic link
library may not exist or the directory containing the dynamic link library is
not in the LIBPATH environment variable.

Recovery

Ensure that the name for the dynamic link library is correct in the language
profile.

Ensure that the dynamic link library is in the library path specified by the
LIBPATH variable in your CONFIG.SYS file. Copy the dynamic link library to a
directory in the LIBPATH variable or modify your LIBPATH statement in your
CONFIG.SYS file and restart the OS/2 operating system.


ΓòÉΓòÉΓòÉ <hidden> DDE30459 ΓòÉΓòÉΓòÉ

Dynamic link library DDE3THNK.DLL cannot be loaded: return code = return code.

An error occurred when the dynamic link library for the thunk support was
loaded. Depending on the OS/2* operating system return code, the dynamic link
library may not exist or the directory containing the dynamic link library is
not in the LIBPATH environment variable.

Recovery

Ensure that the name for the dynamic link library is correct in the language
profile.

Ensure that the dynamic link library is in the library path specified by the
LIBPATH variable in your CONFIG.SYS file. Copy the dynamic link library to a
directory in the LIBPATH variable or modify your LIBPATH statement in your
CONFIG.SYS file and restart the OS/2 operating system.


ΓòÉΓòÉΓòÉ <hidden> DDE30460 ΓòÉΓòÉΓòÉ

Pipe error trying to start program: return code = return code.

An unexpected pipe error occurred while trying to start a monitor.

Recovery

Check the OS/2* operating system documentation for the corrective action for
this error. Once the problem has been fixed, try the action again.


ΓòÉΓòÉΓòÉ <hidden> DDE30487 ΓòÉΓòÉΓòÉ

The Monitor listbox is full and the contents cannot be saved.

An error occurred while trying to save the contents of the Monitor listbox
after it had filled up. Some messages have been lost. Messages are saved to a
file with the extension .SPL in the home directory.

Recovery

Free memory by closing applications or windows. Make sure that there is
sufficient disk space on the drive where your project exists.


ΓòÉΓòÉΓòÉ <hidden> DDE30488 ΓòÉΓòÉΓòÉ

Error trying to start program.  The program cannot be found in the directory
path.

Your program cannot be started.

Recovery

Make sure that the executable file is valid and is in a directory in the path
defined by the PATH environment variable.


ΓòÉΓòÉΓòÉ <hidden> DDE30400 ΓòÉΓòÉΓòÉ

project-name is already active.

The project you wanted to act upon (select/change/delete) has already been
selected or is being changed.

Recovery

Cancel the active project, and try the action again.


ΓòÉΓòÉΓòÉ <hidden> DDE30406 ΓòÉΓòÉΓòÉ

Error copying file file name: return code = return code.

An error occurred when a file was being copied.

Recovery

Look up the OS/2* operating system return code description for a more detailed
description of the problem. The target directory may have run out of disk
space.


ΓòÉΓòÉΓòÉ <hidden> DDE30411 ΓòÉΓòÉΓòÉ

Directory does not exist.  Do you want to create it?

The directory specified does not exist.

Recovery

Select Yes to create the directory.

Select No to create the directory yourself.  You can use the Base project
change window to create the directory.

Select Cancel to enter another directory.


ΓòÉΓòÉΓòÉ <hidden> DDE30412 ΓòÉΓòÉΓòÉ

Project project name cannot be a subproject of itself.

A composite project had been selected to be added to its own subproject list.

Recovery

Select another project.


ΓòÉΓòÉΓòÉ <hidden> DDE30413 ΓòÉΓòÉΓòÉ

Subproject project name has already been added.

You cannot add this project to the subproject list because it has already been
added.

Recovery

Select another project.


ΓòÉΓòÉΓòÉ <hidden> DDE30418 ΓòÉΓòÉΓòÉ

Load of the program failed: return code = return code.

An error occurred when an executable program was being loaded. The program may
no longer exist, or it may not be an executable program.

Recovery

Look up the OS/2* operating system return code description for a more detailed
description of the problem.


ΓòÉΓòÉΓòÉ <hidden> DDE30421 ΓòÉΓòÉΓòÉ

The file name you have entered is incorrect.

The file name you have entered is incorrect for the file system.

Recovery

Check OS/2* operating system documentation for information on valid file names
for the file system you are using.


ΓòÉΓòÉΓòÉ <hidden> DDE30423 ΓòÉΓòÉΓòÉ

The path and file name cannot exceed 259 displayable characters.

You have entered a path and file name that is too long.

Recovery

Use a shorter path name.


ΓòÉΓòÉΓòÉ <hidden> DDE30424 ΓòÉΓòÉΓòÉ

Unusable directory name.

The directory you have entered is not allowed.

Recovery

Make sure all characters used in the directory are valid and all subdirectory
names are not too long.


ΓòÉΓòÉΓòÉ <hidden> DDE30440 ΓòÉΓòÉΓòÉ

More than 500 subprojects have been added.

You have added too many subprojects into the subproject list box.

Recovery

Delete some subprojects until there are 500 or fewer. Retry the operation.


ΓòÉΓòÉΓòÉ <hidden> DDE30465 ΓòÉΓòÉΓòÉ

Error creating backup of project file.  Project not changed: return code =
return code.

An error occurred when trying to copy a project file to a temporary file. The
drive may have run out of memory.

Recovery

Look up the OS/2* operating system return code description for a more detailed
description of the problem.


ΓòÉΓòÉΓòÉ <hidden> DDE30466 ΓòÉΓòÉΓòÉ

A project description is missing.

The Project description entry field is empty.

Recovery

Enter a project description.


ΓòÉΓòÉΓòÉ <hidden> DDE30467 ΓòÉΓòÉΓòÉ

Cannot create subdirectory: return code = return code.

An error occurred when trying to create a subdirectory. The drive may have run
out of memory.

Recovery

Look up the OS/2* operating system return code description for a more detailed
description of the problem.


ΓòÉΓòÉΓòÉ <hidden> DDE30468 ΓòÉΓòÉΓòÉ

The directory path is missing or not fully qualified.

The Directory entry field was not filled in, or the directory is not fully
qualified.

Recovery

Enter a fully qualified directory path.


ΓòÉΓòÉΓòÉ <hidden> DDE30470 ΓòÉΓòÉΓòÉ

This project file already exists.

The file name you have entered in the project entry field already exists.

Recovery

Choose another project name.


ΓòÉΓòÉΓòÉ <hidden> DDE30471 ΓòÉΓòÉΓòÉ

The name of the target file name is missing.

The Target file name entry field is empty.

Recovery

Enter a target file name.


ΓòÉΓòÉΓòÉ <hidden> DDE30472 ΓòÉΓòÉΓòÉ

The name of the make file is missing.

The Make file name entry field is empty.

Recovery

Enter a make file name.


ΓòÉΓòÉΓòÉ <hidden> DDE30473 ΓòÉΓòÉΓòÉ

The file mask for the project directory is missing.

The File mask entry field is empty.

Recovery

Enter a file mask.


ΓòÉΓòÉΓòÉ <hidden> DDE30474 ΓòÉΓòÉΓòÉ

The name of the project file is missing.

The entry field that requires a project file name is empty.

Recovery

Enter a project file name.


ΓòÉΓòÉΓòÉ <hidden> DDE30475 ΓòÉΓòÉΓòÉ

At least one project must be selected.

The action you have requested requires you to select a project first.

Recovery Select a project and retry the action.


ΓòÉΓòÉΓòÉ <hidden> DDE30476 ΓòÉΓòÉΓòÉ

The name you enter must be unqualified.

This entry field requires a file name without a path. You have included a path
instead.

Recovery

Enter an file name without a path.


ΓòÉΓòÉΓòÉ <hidden> DDE30478 ΓòÉΓòÉΓòÉ

Subproject project name contains the composite project.

The subproject you have asked to be added contains this composite project in
its subproject list.

Recovery

Do not add this subproject to this composite project. Or remove the composite
project from the subproject list of the subproject you want to be added.


ΓòÉΓòÉΓòÉ <hidden> DDE30407 ΓòÉΓòÉΓòÉ

Error deleting file file name: return code = return code.

An error occurred while attempting to delete the file.

Recovery

Make sure that the file is not already being used. Check that the file is not
set for read only. Look up the OS/2* operating system return code description
for a more detailed description of the problem.


ΓòÉΓòÉΓòÉ <hidden> DDE30408 ΓòÉΓòÉΓòÉ

project namecannot be deleted: return code = return code.

An error occurred while attempting to delete the project.

Recovery

Make sure that the project file associated with this project is not opened by
another process. Check that the file is not set for read only. Look up the
OS/2* operating system return code description for a more detailed description
of the problem.


ΓòÉΓòÉΓòÉ <hidden> DDE30416 ΓòÉΓòÉΓòÉ

The editor cannot be loaded: return code = return code.

An error occurred while attempting to start the WorkFrame/2* editor.

Recovery

Check that the editor specified in the Change editor window exists and can be
run from the OS/2* operating system. Look up the OS/2* operating system return
code description for a more detailed description of the problem.


ΓòÉΓòÉΓòÉ <hidden> DDE30426 ΓòÉΓòÉΓòÉ

Cannot read the library: return code = return code.

An error occurred trying to read the library specified.

Recovery

Make sure that the library entered exists and is a valid OS/2* operating system
library file.


ΓòÉΓòÉΓòÉ <hidden> DDE30427 ΓòÉΓòÉΓòÉ

The search mask cannot contain a '\\', '/' or a colon.

The file mask contains one or more characters reserved for specifying the drive
and path information. These characters may not be used in the mask.

Recovery

Fix the file mask and retry the operation.


ΓòÉΓòÉΓòÉ <hidden> DDE30428 ΓòÉΓòÉΓòÉ

project name cannot be changed; it is a temporary project.

You cannot change a temporary project.

Recovery

None.


ΓòÉΓòÉΓòÉ <hidden> DDE30432 ΓòÉΓòÉΓòÉ

Unusable Library utility dynamic link library: return code = return code.

The library manager dynamic link library (DDE3LIBT.DLL) does not contain the
required entry points.

Recovery

Contact the supplier of the Library utility tool.


ΓòÉΓòÉΓòÉ <hidden> DDE30433 ΓòÉΓòÉΓòÉ

Library file name missing.

A library file name is required.

Recovery

Enter the library file name in the Library entry field and retry the action or
command.


ΓòÉΓòÉΓòÉ <hidden> DDE30495 ΓòÉΓòÉΓòÉ

File could not be found.

Recovery

If the file was selected from a listbox, then refresh the listbox and check
that it has not been deleted by another process.


ΓòÉΓòÉΓòÉ <hidden> DDE30496 ΓòÉΓòÉΓòÉ

Drive is not ready. Insert the correct diskette and close the drive. Select
Retry when ready. Or select Cancel to change to another drive.

Check the selected drive.

Recovery

This error often occurs when accessing a diskette drive. If this is the case,
replace the diskette in your diskette drive and select Retry.


ΓòÉΓòÉΓòÉ <hidden> DDE30497 ΓòÉΓòÉΓòÉ

File path is not valid.

The file path name contains incorrect characters, or one of the components of
the path name is incorrect.

Recovery

Retype the path name using subdirectory names and drive identifiers that are
present on your system.


ΓòÉΓòÉΓòÉ <hidden> DDE30498 ΓòÉΓòÉΓòÉ

A file specification in the file mask entry field is missing.

The file mask field cannot be left blank.

Recovery

Enter a valid file mask, and retry.


ΓòÉΓòÉΓòÉ <hidden> DDE30499 ΓòÉΓòÉΓòÉ

There was an unexpected return code from a file call: return code =
return code.

An unexpected error was returned from a file call.

Recovery

See the OS/2* operating system return code for more information.


ΓòÉΓòÉΓòÉ <hidden> DDE30501 ΓòÉΓòÉΓòÉ

A base project must be selected.

To use substitution variables in the options strings for the action you
selected, you must select a base project.

Recovery

Select a base project or start one.  Retry the action.


ΓòÉΓòÉΓòÉ <hidden> DDE30507 ΓòÉΓòÉΓòÉ

No files appropriate for the Build action were selected.

None of the files selected (if any) are appropriate for the Build action.

Recovery

Make sure that at least one of the files selected is a source file, a .OBJ
file, a .RC file, or a .RES file.


ΓòÉΓòÉΓòÉ <hidden> DDE30508 ΓòÉΓòÉΓòÉ

The selected files cannot be used for the Compile action.

None of the files selected (if any) are appropriate for the Compile action.

Recovery

Make sure that at least one of the files selected is a source file.


ΓòÉΓòÉΓòÉ <hidden> DDE30509 ΓòÉΓòÉΓòÉ

The selected files cannot be used for the Link action.

None of the files selected (if any) are appropriate for the Link action.

Recovery

Make sure that at least one of the files selected is a .OBJ file.


ΓòÉΓòÉΓòÉ <hidden> DDE30521 ΓòÉΓòÉΓòÉ

Error saving listbox - disk full.

The listbox cannot be saved because the disk is full.

Recovery

Delete files from the full disk and retry the operation. Or save the listbox on
another disk.


ΓòÉΓòÉΓòÉ <hidden> DDE30608 ΓòÉΓòÉΓòÉ

Too many Object module details windows are open - close one and retry.

Recovery

Close one or more of these windows.  Retry the action.


ΓòÉΓòÉΓòÉ <hidden> DDE30609 ΓòÉΓòÉΓòÉ

Page size must be a power of 2, between 16 and 32768.

The page size must be one of the following values: 16, 32, 64, 128, 256, 512,
1024, 2048, 4096, 8192, 16384, 32768.

Recovery

Correct the page size, and retry the command.


ΓòÉΓòÉΓòÉ <hidden> DDE30610 ΓòÉΓòÉΓòÉ

Cannot load dynamic link library. Make sure it is in the LIBPATH environment
variable.

An attempt to load the dynamic link library failed.

Recovery

Make sure that the dynamic link library exists and its directory is pointed to
by the LIBPATH variable in the CONFIG.SYS file.


ΓòÉΓòÉΓòÉ <hidden> DDE30613 ΓòÉΓòÉΓòÉ

Library not found or new.

The library file name entered is incorrect, or the file does not exist.

Recovery

If the library is new, select OK and continue. Otherwise, enter the correct
library file name.


ΓòÉΓòÉΓòÉ <hidden> DDE30614 ΓòÉΓòÉΓòÉ

An object record format error was detected in object name

The library file contains an unusable module, or the file has been corrupted.

Recovery

Check that the library file is valid. Perform an operation against the library
to locate the error. Then remove the unusable object.


ΓòÉΓòÉΓòÉ <hidden> DDE30637 ΓòÉΓòÉΓòÉ

Listbox name listbox is full.

Items cannot be added to the listbox because of memory restrictions or other
errors.

Recovery

None.


ΓòÉΓòÉΓòÉ <hidden> DDE30638 ΓòÉΓòÉΓòÉ

Unusable object format.

The file is corrupt or is not an object file.

Recovery

Rebuild the object file or contact the distributor of the file.


ΓòÉΓòÉΓòÉ <hidden> DDE30651 ΓòÉΓòÉΓòÉ

Error opening file name.

An error occurred while opening the object module or library file.

Recovery

Make sure that the file requested exists and has not been opened by another
process for its exclusive use. Retry the action.


ΓòÉΓòÉΓòÉ <hidden> DDE30652 ΓòÉΓòÉΓòÉ

Error locating object name.

The object module cannot be located in the library.

Recovery

The library may have been modified by another process.

Re-enter the library name to refresh the modules listbox. This will ensure that
the listbox reflects the true state of the library. Retry the command.


ΓòÉΓòÉΓòÉ <hidden> DDE30653 ΓòÉΓòÉΓòÉ

Error reading object name.

An error occurred while reading the object module.

Recovery

Check that the object module requested is a valid object file. You may have to
rebuild the object by compiling its source code.


ΓòÉΓòÉΓòÉ <hidden> DDE30893 ΓòÉΓòÉΓòÉ

Too many projects are started.

You cannot start any more projects because the maximum number of projects have
already been started.

Recovery Close some project windows.  Retry the action.


ΓòÉΓòÉΓòÉ <hidden> DDE30899 ΓòÉΓòÉΓòÉ

A file exists with the same name specified for the directory.

The directory you entered cannot be created because a file with the same name
already exists where the directory was to be created.

Recovery

Enter another directory name or delete the file.