|Interfacing with Microsoft Transaction Server|
The IBM WebSphere Extended Edition CICS execution environment and the Net Express development environment are closely tied to enable you to use the two together. This chapter describes the support in Net Express for WebSphere, and how you use it.
The section Developing a WebSphere Application explains all you need to know to successfully create a project for a WebSphere application, and to compile, build and deploy your application. The other sections explain more about the built-in support for WebSphere.
You should also refer to your WebSphere documentation.
Creating a WebSphere application requires additional steps over a standard application:
If you create a WebSphere project in Net Express as described below, Net Express makes it easy for you by automatically handling all of these extra steps.
WebSphere COBOL sources have the extension .ccp. The Net Express project is created using these source files. Although .cbl files are created as part of the build process, you should only ever edit the .ccp files as the .cbl files are regenerated every time the project is rebuilt and any changes you make directly to them will be lost. To help you avoid mistakenly editing the .cbl files, they are marked as read-only when they are created.
Before you start, make sure that the folder opt\cics\bin is on your PATH environment variable to ensure that Net Express can find and run cicstcl.exe to translate .ccp files to .cbl files.
To create a WebSphere project in Net Express:
Net Express now sets up complete build information for each file, adding essential Compiler directives and creating a DLL from each .ccp.
You can repeat this step as often as you need, to add other source
files. If you add any non-CICS .cbl files, you must manually
add the two Compiler directives
If you want to use intermediate code for debugging instead of DLLs, see the section Creating Intermediate Code below.
Not supported for target platform.
You can ignore these.
In order to be able to debug your application you must add the Compiler
To work with WebSphere, the executable files must have the extension .cbmfnt. The following steps define the executable files that need to be renamed, and the folder they should be copied to ready for deploying.
Your project is now ready to use. You can edit the source files (.ccp), build for debugging and debug your application in the usual way.
You can add WebSphere source files (.ccp) via the source pool (right-hand pane in the Project view) now or later. However, when you drag them to the build pane, only the translation step from .ccp to .cbl will be set up for you. You will need to set up the packaging stage (to create DLLs) yourself, as follows.
For debugging, you may prefer to create intermediate code (.int) files instead of DLLs. You can do this as follows:
Now you have created a project for your WebSphere application, you should follow these steps to start debugging.
(If you don't have Net Express running when you click Yes then the process may appear to hang.)
This section explains some of the details of the support in Net Express for WebSphere applications. You do not need to read or understand this to create WebSphere applications.
The support in Net Express primarily gives:
When a program is compiled with the Compiler directive DATA-CONTEXT and it LINKS to or calls a subroutine, the program works in conjunction with WebSphere to ensure instances of COBOL Working-Storage are unique to each LINK level. The standard WebSphere compilation will automatically compile with DATA-CONTEXT set. There is nothing more for you to do. However if you have a non-CICS COBOL subprogram that is called as part of a transaction execution, you should compile that program with the DATA-CONTEXT directive set in order to ensure that its Working-Storage is managed correctly.
Standard CICS translated programs (started by a transaction code or executed by LINK or XCTL) are executed from the folder specified in the associated PPT entry (PD stanza) or are located via standard WebSphere semantics. Normal COBOL RTS load rules are not used under any circumstances for LINK and XCTL.
COBOL dynamic calls to a COBOL subroutine (those that result in the loading of a new executable) on a CICS platform will first try to resolve the call via a PPT entry (PD stanza). The PPT designated physical module must have an entry point identical to the PPT name. If there is not a matching PPT entry, the COBOL RTS will try to locate the module via its usual rules.
The environment variables can be controlled independently for each WebSphere region, if required, by adding entries to \var\cics_regions\region-name\environment. The current folder for a WebSphere region application server is normally \var\cics_regions\region--name\dumps\dir1.
Note: Any COBOL programs used within a WebSphere environment that have not been translated must have an extension of .cbmfnt, .gnt, or .int in order that the online environment can find them.
The following new Abend code is displayed when a COBOL Run-Time System error is encountered; for example, index out of range, divide by zero, module not found without CALL-RECOVERY. The text of the COBOL RTS error message is displayed on the console log.
A583 Any COBOL RTS error.
The EXTFH interface to SFS is provided with the WebSphere product and should be used if you want to run batch COBOL applications against the same files as created and updated by the WebSphere online environment.
For full details, see the WebSphere ReadMe.
Copyright © 2000 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.
|Interfacing with Microsoft Transaction Server|