IBM C and C++ Productivity Tools for OS/390 Release 1.0 FixPack 2 README

This README file contains the latest information about installing IBM
C and C++ Productivity Tools for OS/390 Release 1.0 FixPack 1, as well as
information that was not available for our printed publications.

Note: this document prints best using an 8pt fixed-width font such as Courier.
This ensures that text formatting such as columns line up properly.

Copyright International Business Machines Corporation 1999, 2000. All rights reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted
by GSA ADP Schedule Contract with IBM Corp.


Contents

This file includes the following information:

1.0 Install
	1.1 Hardware Requirements
	1.2 Software Requirements
	1.3 Reinstalling the product
	1.4 Uninstalling the Editor
	1.5 Installing on non-English, non-Japanese Windows NT Systems

2.0 Help Issues
	2.1 Adobe Acrobat 4.0 required for Language Sensitive Help in Editor
	2.2 Adobe Acrobat Reader with Search (English language support only)
	2.3 Searching PDF Documents through a Browser (English language support only)
	2.4 Viewing Language Sensitive Help
	2.5 Bookmarks in PDF documents and Language Sensitive Help
	2.6 Versions of PDF Documents
	2.7 Browser Configuration
	2.8 Autoconfigured Proxy Settings with Netscape
	
3.0 Editor Issues
	3.1 Japanese environments and file transfer programs
	3.2 Japanese environments and the Java character set converter
	3.3 Japanese environments and mapping the Backslash character to the Yen Sign

4.0 Performance Analyzer Issues
	4.1 Workstation component limitations and known problems
	4.2 Host component limitations and known problems

5.0 Distributed Debugger Issues
	5.1 Workstation component limitations and known problems
	5.2 Host component limitations and known problems
        5.3 Japanese Strings in C/C++ Source Files
	5.4 Japanese Messages Issued by Debug Tool

6.0 Support
	6.1 OS/390 C/C++ Productivity Tools Web page
	6.2 Contacting IBM

7.0 Trademarks


---------------------------------------------------------------------------------------------


1.0 Install
---------------------------------------------------------------------------------------------
		
1.1 Hardware requirements

	C/C++ Productivity Tools' host components (Performance Analyzer and Debug Tool)
	execute on any hardware configuration supported by OS/390 Version 2 Release 4,
	or later.  See the Program Directory and memo to users for information on the
	host components.

	C/C++ Productivity Tools' workstation components (Performance Analyzer, Distributed
	Debugger and Editor) execute on the following workstation configuration:
	- Intel Pentium 200 MHz or higher, or compatible processor (333 recommended)
	- SVGA display (1024 x 768 recommended)
	- CD-ROM drive
	- Mouse or pointing device
	- Minimum of 64 MB RAM of memory (128 MB RAM recommended)
	- Disk space requirements (typical installation with online help):
	  150 MB available disk space

	See the Getting Started with OS/390 C/C++ Productivity Tools for information on the 
	workstation components.


1.2 Software Requirements

	C/C++ Productivity Tools' host components execute in the following environments:
		- OS/390 Version 2 Release 4 (5647-A01), or later which contains:
			- TCP/IP Version 3 Release 2, or later (OS/390 Base)
			- Language Environment (OS/390 Base)
			- C/C++ Compiler with Debug (OS/390 Optional Feature with Feature
			  Codes 5962, 5963 or 5712)


	C/C++ Productivity Tools' workstation components execute in the following environments:
		- Microsoft Windows NT 4.0 (Service Pack 3, or later) with the following 
		  prerequisites:
			- TCP/IP communication protocol
			- Frames capable browser required for reading HTML help information:
				- Netscape Navigator Version 4.5, or later, recommended
				- Microsoft Internet Explorer Version 5.0, or later, recommended
			- Adobe Acrobat Reader 4.0, or later, (with search) required to view, 
			  print and search PDF documents.

	For customers requiring Japanese DBCS support for remote debug of OS/390 applications
        with products such as C/C++ Productivity Tools for OS/390, and VisualAge for Java,
        Enterprise Edition, the following PTFs must be applied in conjunction with Debug
        Tool PTFs for APARs PQ30470 and PQ31829:
		PTF for APAR PQ32787 
		        UQ39553 for OS390 2.7.0 
		        UQ39554 for OS390 2.8.0 
		        UQ39555 for OS390 2.9.0 
	        PTF for APAR PQ32571 
		        UQ38327  for OS/390 2.7.0
		        UQ38328  for OS/390 2.8.0
			UQ38329  for OS/390 2.9.0  


1.3 Reinstalling the product

	If you install IBM C and C++ Productivity Tools for OS/390 into a directory, for example:
	C:\Program Files\IBM\390ProductivityTools\ and then reinstall (after an uninstall)
	into a different directory, for example: F:\CppTools\, then you will not be able to call
	Distributed Debugger help.  To fix this problem follow these steps:
		1. From the Distributed Debugger Help menu, select Change Product Context.
		2. Ensure that the IBM C and C++ Productivity Tools for OS 390 radio button is
		   selected. 
		3. Click OK.  Now you can call the help.


1.4 Uninstalling the Editor

	When uninstalling OS/390 C/C++ Productivity Tools, during the uninstall of the Editor,
	you may see a message that two uninstall processes are running.  If this occurs the 
	uninstall process will complete, but the Editor will not be uninstalled.   Remove the
	directory where the Editor was installed and remove the Editor entries from the registry.
	Reboot your workstation.  Contact IBM support for further information.


1.5 Installing on non-English, non-Japanese Windows NT Systems

	If you wish to install IBM C/C++ Productivity Tools for OS/390 on non-English,
	non-Japanese Windows NT systems, you should install the Japanese version
	of the product and select to install the product in English.  This will result
	in an English version of C/C++ Productivity Tools being installed.  However, some
	messages from the IBM Distributed Debugger may appear in the national language
	that Windows NT is using.


2.0 Help Issues
---------------------------------------------------------------------------------------------

2.1 Adobe Acrobat 4.0 required for Language Sensitive Help in Editor

	Adobe Acrobat 4.0 is the minimum level of the Adobe Acrobat Reader required 
	for Language Sensitive Help in the Editor.


2.2 Adobe Acrobat Reader with Search (English language support only)

	The English Adobe Acrobat Reader comes with a search plug-in that is
	included on the C/C++ Productivity Tools for OS/390 CD-ROM.  To search 
	the PDF documents provided you will need the Adobe Acrobat Reader
	with Search.  Look for a folder called Acrobat Reader on the C/C++ 
	Productivity Tools CD-ROM.  Inside the Acrobat Reader folder you will 
	find a self extracting executable.  To install the Reader, click on this
	self-extracting executable and follow the instructions presented.
 
	For updated Adobe Readers see http://www.adobe.com
	A Japanese Acrobat Reader with Search is not available from
	Adobe at this time.
       

2.3 Searching PDF Documents through a Browser (English language support only)

	When you install the Reader, it will automatically add the search
	plug-in to the Browser plug-in directory.  You will then be able
	to view and print PDF documents through the browser.  However, to
	search the PDF documents, you will need to open the PDF document outside
	of the browser.  This is because PDF documents that are stored on a Web-server
	require a Web-server search engine that supports the searching of PDF
	documents.  You can search PDF documents on a local workstation drive,
	a network drive or from a CD-ROM.  Look for the folder pdf390 where you
	installed with C/C++ Productivity Tools.  This folder contains the PDF documents 
	you can search outside of the browser.

	See the Adobe Acrobat Reader Readme for more information on the Reader
	and the search plug-in.


2.4 Viewing Language Sensitive Help 

	Depending on the size of the PDF document view, you may need to scroll
	the document view in order to see the selected language element.

	To view Language Sensitive Help you usually can place the cursor on the 
	language element.  However, for those language elements that have spaces, 
	such as "operator +", you need to select the entire language element including 
	the space to see the Language Sensitive Help for that element.
	
	
2.5 Bookmarks in PDF Documents and Language Sensitive Help

	All English PDF documents include bookmarks.  No Japanese PDF documents 
	contain bookmarks.  Since bookmarks are required to view Language
	Sensitive Help (LSH), LSH is provided from English PDF documents. 
	A corresponding Japanese PDF document without bookmarks is available
	from the PDF Documents selection on the C/C++ Productivity Tools Home
	Page. 


2.6 Versions of PDF Documents

	The levels of some Japanese PDF documents may not coincide with the levels of
	some English PDF documents.  When available the Japanese PDF documents will be
	refreshed to coincide with the English PDF documents.
	

2.7 Browser Configuration

	On Windows NT 4.0, the default browser is Microsoft Internet Explorer 2.0.
	C/C++ Productivity Tools for OS/390 Help will not work with this browser,
	since it does not support frames.  For help to work properly, you need to
	install a frames-capable browser before you install C/C++ Productivity
	Tools for OS/390. We recommend Netscape Navigator 4.5 or above,
	or Microsoft Internet Explorer 5.0 or above.  Other frames-capable browsers may
	work, but there are many differences in the way browsers handle certain
	HTML tags.  Consequently, Help may not appear to function properly if you
	do not use one of the recommended browsers.

	The C/C++ Productivity Tools installation program should check your browser
	configuration and offer to change it automatically.

	If you did not opt to let the installation program automatically update
	your browser settings, please follow the instructions below to access
	the HTML help system.

	For Netscape 4.x, do the following:
	  1)  Launch Netscape.
	  2)  Pull down the Edit menu and select Preferences.
	  3)  Click on the + sign to the left of Advanced in the left-hand panel.
	  4)  Click on Proxies in the resulting menu.

	If you have Direct Connection to the Internet selected, do nothing.

	If you have Automatic Proxy Configuration selected, contact your
	system administrator to ensure that 127.0.0.1 is included in your
	proxy exceptions.

	If you have Manual Proxy Configuration selected, click on the View button to
	the right of Manual Proxy Configuration.
	  a) Add localhost:49213,127.0.0.1 to your proxy exception settings.
	  b) Click OK.
	  c) Click OK.


	For Microsoft Internet Explorer 5.x, do the following:
	  1) Launch Microsoft Internet Explorer.
	  2) Pull down the Tools menu and select Internet Options.
	  3) Go to the Connections tab.
	  4) Click on the LAN Settings button.
	  5) If "Use a proxy server" is selected, do the following:
		a) Ensure that the radio button "Bypass proxy server for local
		   (intranet) addresses" is selected.
		a) Click on the Advanced button to the right of the Proxy
		   server radio button.
		c) Add "localhost:49213,127.0.0.1" to the text box under
		   "Do not use proxy server for addresses beginning with"
		d) Click OK.
		e) Click OK.
		f) Click OK.


2.8 Autoconfigured Proxy Settings with Netscape

	If you received an "Autoconfigured" warning from the installation program,
	this simply means that your proxy exceptions are autoconfigured on Netscape
	4.x.  If this is the case, please check with your system administrator to
	ensure that 127.0.0.1 is treated as a local address.



3.0 Editor Issues
---------------------------------------------------------------------------------------------

3.1 Japanese environments and file transfer programs

	In Japanese environments, certain file transfer programs convert the following
	host code points to unassigned code points on the Windows NT workstation.  The
	editor cannot read these code points and will prematurely stop reading files
	which contain these characters:

			Host code	Windows NT
			point		workstation
	  Character	Cp930	Cp939	code point
	  ---------	-----	-----	-----------
	  Cent sign	0xb1	0x4a	0x80
	  Pound sign	0x4a	0xb1	0xa0
	  Not sign	0x5f	0x5f	0xfd
	  Backslash	0xb2	0xe0	0xfe
	  Tilde		0xa0	0xa1	0xff


3.2 Japanese environments and the Java character set converter
	
	Due to a variation in the Java character set converter in Japanese environments,
	the following characters have restrictions when encountered in files opened with
	a host source encoding:
	  - emulation shift-out/shift-in (SO/SI) characters are not displayed;
	  - incorrect source-encoding code points are displayed in the Hex edit line
	    dialog:

				Windows NT
				workstation
	  Character		code point		Host code point
	  ---------		-----------		---------------
	  EM dash		0x815c			0x4260
	  Wave dash		0x8160			0x43a1
	  Double vertical line	0x8161			0x447c
	  Minus sign		0x817c			0x444a
	  Broken bar		0xfa55			0x426a


3.3 Japanese environments and mapping the Backslash character to the Yen Sign

	When you download/upload OS/390 C/C++ source files to/from the Windows environment,
	use a file transfer program which maps the Backslash (0xE0) in Host (Cp939) to the
	Yen Sign (0x5C) in Windows.  Some file transfer programs do not perform this conversion
	by default, but allow you to modify the mapping table.  In this case, modify the table
	to perform this conversion.



4.0 Performance Analyzer Issues
---------------------------------------------------------------------------------------------

4.1 Workstation component limitations and known problems

	Problem:
		Call Nesting Diagram: When you use the menu item "View->Include functions...",
		some of the connecting lines between thread switches may not look correct.
	Workaround:
		Try resizing the window to cause the graph to be redrawn. This should cause
		the lines to be drawn correctly.

	Problem:
		Call Nesting Diagram:  Using the "Find next" button or menu item repeatedly
		sometimes causes the diagram to distort or become disconnected.  The function
		call sequence does not appear to be correct.  However, if you display the Call
		Stack for the selected function, it is correct.
	Workaround:
		Scroll up in the diagram, select any function in the diagram that appears
		before the function being searched for and try the "Find next" operation again.

	Problem:
		Call Nesting Diagram:  After selecting a thread with the Include Threads dialog,
		the "Scroll item into view" menu option does not always work properly.  The
		item may be scrolled far to one side horizontally.
	Workaround:
		Scroll the item into view manually using the scroll bars.

	Restriction:
		Trace files created with the Performance Analyzer component of VisualAge C++,
		or any other VisualAge solution, cannot be analyzed with OS/390 C/C++ 
		Productivity Tools' Performance Analyzer.
	Workaround:
		Analyze the trace file with the product that created it.


4.2 Host component limitations and known problems
 
	Problem:
		Calls to assembler routines appear with a name of unknown in the function trace.
	Workaround:
		none

	Problem:
		Tracing a heavily threaded program with task (CPU) time may result in a CTV0007S
		message and an incomplete trace file. 
	Workaround:
		Try tracing the program again.  If the CTV0007S message is issued again,
		trace the multithreaded program with real time.

	Problem:
		When tracing a program that calls a function retrieved by a fetch or fetchep
		C Run-time Library call, if the function has been compiled with hooks (for 
		example: TEST(HOOK)), then there will be one instance of the function in the
		trace data for each time that it is called.  If the function is not compiled
		with hooks, the function name will not be correct (for example: it will be
		Unknown_Function or @@GETFN).             
	Workaround:
		none
 
	Problem:
		The Performance Analyzer does not support the C Runtime Library functions
		getcontext() and setcontext().  Unpredictable behavior may result if 
		the program being traced calls these functions, including a program abend.
	Workaround:
		none

	Problem:
		When tracing a long running application the dataspace used by the Performance
		Analyzer may reach its maximum size and cannot be extended.  This will result
		in one of the following messages being displayed: CTV0018E or CTV0019E.
		Tracing will stop at that point and a valid trace file will be created.
		However, the file will only contain trace data collected up to the point of 
		the failure.
	Workaround:
		Try to reduce the amount of trace data collected by compiling only selected
		files with hooks (for example: using the TEST(HOOK) option.  Select files
		that contain the functions you are interested in.  Another option is to trace
		the program with the FUNCTION=COUNTS sub-option of the PROFILE run-time option.
		Using this option, a reduced amount of data is collected and dataspaces are 
		not used.  Only function count information and the relationships between 
		functions are collected with this option.

	Problem:
		Tracing a program that calls the C Runtime Library function system()
		may cause an abend when the program is executing with the Language
		Environment runtime option POSIX(OFF).
	Workaround:
		none   

	Problem:
		When tracing a program that calls the C Runtime Library function spawn or
		spawnp, the name of the file created for the parent process (the one that
		calls spawn) will have the process ID appended to it.  The name of the file
		for the child process will not have the process ID appended to it.  As a
		result, if spawn is called more than once with the same program, the file
		will be overwritten by the second and subsequent child process.
	Workaround:
		Specify a unique file name with the __PROF_FILE_NAME environment and
		include it in the environment that is passed on each spawn call.

	Problem:
		Sometimes the Performance Analyzer will fail writing the trace file to a 
		sequential dataset if a dataset with the same name already exists.  You will
		receive a CTV0011E message if this occurs and an incomplete trace file is created.
	Workaround:
		Delete the trace file and try to trace the program again with the
		Performance Analyzer to create another trace file.

	Problem:
		When tracing DLL's located in the UNIX System Services HFS file system, the
		names of these DLL's may appear as *PATHNAM in the trace data displayed on
		the Performance Analyzer diagrams.
	Workaround:
		none
        
        Problem:
	        When tracing a C++ program that uses C++ exception handling, the trace data
                displayed on the diagrams may not accurately reflect the program function
                flow that occurs when exceptions are caught.  For example, the Call Nesting
                diagram may show more function calls than are actually executed.
        Workaround:
	        For best results, ensure the all of the program code is compiled with the
                TEST(HOOK) compile option.


5.0 Distributed Debugger Issues
---------------------------------------------------------------------------------------------

5.1 Workstation component limitations and known problems

    o Dialogs sometimes open behind the parent dialog (or workbook) 
      instead of in front of it. If the debugger appears to be hung, 
      or you hear a "beep" but see nothing happen when clicking on 
      the debugger user interface, check for hidden dialogs by 
      minimizing all other applications.

    o Port 8002 is required/reserved for multi-user communications and
      is not available as an engine port or UIDaemon port.

    o If running the user interface (idebug) results in the 
      command prompt coming back (especially on NT), then use
      the Task Manager to ensure there are no previous debugger
      "java_g" sessions still remaining. If there are, end them. 
    
    o If running the user interface (idebug) on NT results in 
      "cannot create 8002 server socket" there probably is an 
      old debugger java_g task still running. Use the task 
      manager to end it.
   
    o When a second program is loaded, some menus may be empty.
      Switching to the first program and then switching back to 
      the new program will solve the problem.
    
    o If no buttons appear on the Exception Filter Preferences Setting
      pane in the Application Preferences dialog, increase the height
      of the window so that the buttons show up in the dialog.

    o Some unicode characters, such as \u03a9, do not display correctly.  
      The debugger currently cannot tell if a given character is 
      displayable in the current user font set.

    o There is no help available for the main File - Preferences or the 
      Help - Change Product Context dialog.  Attempting to invoke help
      in these places may cause the browser and debugger to terminate,
      even on SUBSEQUENT valid help requests.
   
    o Do not change the 'File - Preferences - General' settings 
      ('Appearance','Toolbars') since that may cause erratic 
      debugger behavior.  If you do change them, and want to get back 
      to the default settings, you can delete 'Workbook*.ini' and
     'Panes.ini' in your 'DbgProf' profile directory.

    o If the source view or storage view scrolls after you have stopped
      pressing mouse button one, then press mouse button one again
      either above or below the slide to cause a single scroll once in the
      opposite direction.

    o There currently is a problem selecting 'File','Preferences',
      Debug' 'Application', and then changing settings combined 
      with the Debugger Defaults Checkbox, especially if multiple
      applications are loaded. To change the debugger defaults only
      load one application, change the settings, select the 
      Debugger Defaults Checkbox and then exit the debugger.

    o To change the debugger defaults load one application, change the
      settings, select the Debugger Defaults Checkbox and then exit the
      debugger.
     
    o The initial user environment used to start the Debugger User Interface 
      is retained.  Thus if a second command window is used to connect to 
      the initial running Debugger then that second user environment is 
      not used. Instead, the initial settings are used whenever any subsequent 
      Process Panes are added (whenever any subsequent engines are started).

    o If you catch an exception and choose to run the exception, the debugger 
      UI will no longer respond unless your application hits a breakpoint, 
      runs to completion or throws another exception. This is a known problem.

    o The shortcut for the Modules Menu has been changed from Alt-M to Alt-U.

    o The case sensitivity check box for setting function breakpoints from the
      Function Breakpoint Dialog is not enabled at this time.

    o The daemon currently does not have a default language.  When using the command
      line, you need to specify the "-qlang=cpp" option when invoking the UI Daemon.
      If you do not use -qlang, a load dialog will appear and ask you to specify a
      language.  Fill in the information and click "Load".  This option is already set
      if starting the daemon from the Start Menu or Debugger icon.

    o Source Search path will be remembered and will be used for all future S390 daemon
      connections.  If you do not want this value to be reused, either:
      1. remove the S390Default.#dtool file from your profiles directory (before
         connecting to the daemon) or
      2. load a program into the debugger, select the "Source Search Path" menu item in the
         source menu, erase or change the contents of the text field, and click OK. 
      

5.2 Host component limitations and known problems

    o For C++ programs, step-return may not return to just after the call point.

    o For C programs, step-return may not return to just after the call point.
      A work around is to compile the C code with TEST(SYM,HOOK,NOBLOCK)

    o ASCII/EBCDIC code pages are not locale sensitive.

    o Source filenames have a limit of 255 characters in length.

    o Only information for the current thread is valid.  The current thread is the
      one that had the event which gave the debugger control, such as stopping on a
      line breakpoint.  Stack information, or variables or registers seen in other 
      threads are not valid.

    o Updating an enum variable with an integer value or an enum constant may not work
      correctly.

    o Updating a register may not work correctly.

    o Monitoring an expression containing a register may not work properly.

    o Monitoring arguments of C++ template functions/methods may incorrectly interpret
      the argument types as those of another template instantiation.

    o Monitoring explicitly type cast expressions, such as (char *) v, may not work.

    o The updating of a monitored character string by overtyping the displayed string
      value is not supported.

    o Debugging code compiled with the option NOGONUMBER, an OS/390 C compiler option,
      is not recommended.  With this option the compiler does not generate enough debug
      information for you to be able to step through your code or set breakpoints in it.
      There are also known problems if you do attempt to step through such code.

5.3 Japanese Strings in C/C++ Source Files

	If you are running the Distributed Debugger on OS/390 V2R6 or a version of
        OS/390 that is below V2R6, DBCS strings in C/C++ source files being debugged
        will not be displayed correctly through the Distributed Debugger client on
        Windows NT. These strings could be in comments, or in string literals.
	
	DBCS strings in variables in programs being debugged will not be displayed
        or edited correctly through the Distributed Debugger client on Windows NT. 

5.4 Japanese Messages Issued by Debug Tool

	Note: The information in this section of the readme only applies if you are
        running the Distributed Debugger on OS/390 V2R6 or a version of OS/390
        that is below V2R6. 
        
        Japanese messages issued by the Debug Tool component of the Distributed Debugger
	will not be displayed correctly by the Distributed Debugger client on Windows NT.
	The workaround is to have Debug Tool issue English messages while running in a
	Japanese environment on OS/390.  This can be done by overriding the Debug Tool
	Japanese message file containing remote debug messages with the English mixed-case
	version.  Because Debug Tool also transmits to the debug client LE messages
	issued to the application being debugged, a similar override should be done for
	the LE message files.  

	These instructions do not affect the DTCN messages which are contained in
	a separate file. You should not follow these instructions if you wish to debug
  	using the MFI interface or versions of the IBM Distributed Debugger or IBM
        remote debuggers below Version 8.1

	Follow these instructions after installing the GA PTF for Debug Tool
	(APAR numbers PQ27247 and PQ25905) and after any other DT PTFs are applied,
	until this restriction is removed:

	DT Message File

	1. Create a partitioned data set (PDS) with the same attributes
	   (DSORG, RECFM, LRECL, BLKSIZE) as the Debug Tool SEQAMOD data set.
	2. Copy the member EQA00ER0 from the Debug Tool SEQAMOD data set to
	   the one you created in step 1.
	3. In the new data set, rename the EQA00ER0 member to EQA00ER2.
	4. Concatenate the new data set in front of the Debug Tool SEQAMOD data set
           whenever you run a remote debug session.

	LE Message Files

	1. Create a partitioned data set (PDS) with the same attributes
  	   (DSORG, RECFM, LRECL, BLKSIZE) as the LE SCEERUN data set.
	2. Copy the following members from the LE SCEERUN data set to the one you
	   created in step 1: 
	   CEEMENU0
	   CEEMENU2
	   CEEMENU3
	   CEEMENU4
	   CEEMENU5
	3. In the new data set, rename the CEEMENUx members to CEEMJPNx. 
	4. Concatenate the new data set in front of the LE SCEERUN data set whenever 
	   you run a remote debug session.        

6.0 Support
---------------------------------------------------------------------------------------------

6.1 OS/390 C/C++ Productivity Tools Web page

	Please see http://www.software.ibm.com/ad/c390/pt for fix downloads
	for the workstation components.

	Please see the Program Directory and memo to users for information about fixes for
	host components.


6.2 Contacting IBM

	Please report all problems, including problems with the workstation components,
	as S/390 problems through the S/390 Support line or equivalent in your country.
	Attempting to use workstation support could require you to purchase an additional
	support contract and cause difficulty in routing the problem to the correct
	support center.

	* United States: 1-800-237-5511 Option 4
	* Canada: 1-800-IBM-SERV (1-800-426-7378)
	  Should either number change,
	  IBM general information at 1-800-IBM-4YOU (1-800-426-4968) for both
	  the U.S. and Canada can route you to the appropriate group.
	* Elsewhere, the IBM Software Support Handbook, accessible from
	  http://www.ibm.com/support/, lists phone numbers worldwide for
	  further information on support offerings.
	  Or please phone your local IBM office.

	Submitting problems electronically:

	You can submit problems over the Internet in many countries, including the U.S.
	http://service.software.ibm.com/ points to the S/390 Technical Support Web Page.
	Please see the S/390 Technical Support page for information on submitting problems
	to IBM over the Internet in your country.

	IBMLink is also available. Consult the Program Directory for component IDs to
	assist in problem routing.


6.3 Support

	VisualAge + WebSphere Product Affinity Services Group is a core group of
	technical specialists from IBM development labs that created the IBM VisualAge
	and WebSphere products.  With access to a network of IBM product area experts,
	IBM and industry business partners, and some of the best resources in the
	industry, we can put the optimal team in place to meet the challenge of new
	technology absorption.  Our goal is to enable organizational success with
	VisualAge and WebSphere -- ensuring that our products are used effectively
	within your development team.

	For more information, visit http://www.software.ibm.com/ad/vaws-services/
	or contact the Product Affinity Services Team at:
	WebSphere_Consulting@us.ibm.com



7.0 Trademarks
---------------------------------------------------------------------------------------------

The following terms are trademarks or registered trademarks of the
IBM Corporation in the United States, other countries, or both:

IBM
IBMLink
Language Environment
OS/390
S/390
VisualAge
WebSphere

Intel and Pentium are trademarks or registered trademarks of Intel Corporation
in the United States and/or other countries.

Microsoft and Windows NT are trademarks or registered trademarks of
Microsoft Corporation in the United States and/or other countries.

Java is a trademark of Sun Microsystems, Inc. in the United States
and/or other countries.

UNIX is a registered trademark of The Open Group in the United States
and/or other countries licensed exclusively through X/Open Company Limited.

Other company, product, and service names may be trademarks or service marks of others.

THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF  ANY KIND. IBM DISCLAIMS 
ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE
IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH
RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM
GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.





