Take Note!
Before using this User's Guide and the product it supports, be sure to read the general information under Notices.
Second Edition, December 1997
This edition applies to Version 1.1 of CA70: CICS for Windows NT link extra for Lotus Notes, and to all subsequent releases and modifications until otherwise indicated in new editions.
A form for reader's comments is provided at the back of this publication. If the form has been removed, address your comments to:
IBM United Kingdom Laboratories Transaction Systems Marketing Support (MP207) Hursley Park Hursley Hampshire, SO21 2JN, England
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. You may continue to use the information that you supply.
©Copyright International Business Machines Corporation 1996, 1997.
All rights reserved.
Note to U.S. Government Users - Documentation related to restricted rights -
Use, duplication or disclosure is subject to restrictions set forth in GSA ADP
Schedule Contract with IBM Corporation.
The following paragraph does not apply in any country where such provisions are inconsistent with local law.
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain
transactions, therefore this statement may not apply to you.
References in this publication 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 or other IBM product in this publication is not intended to state or imply that only IBM's program or other product may be used. Any functionally equivalent program that does not infringe any of the intellectual property rights may be used instead of the IBM product. 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 document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, New York 10594, USA.
The following terms are trademarks of the International Business Machines Corporation in the United States and/or other countries:
The following terms, used in this publication, are trademarks of other companies as follows:
CICS for Windows NT link extra provides CICS applications with a means of sending data to a Lotus Notes environment. This data can be used to update or add one or more documents to a Lotus Notes database. Document updates may span more than one database. The user specifies what action to take using a combination of key fields and rules.
The previous announcement of 'CICS for Windows NT link for Lotus Notes' allowed Lotus Notes users to initiate the interaction with a CICS application. The new function provided in 'CICS for Windows NT link extra for Lotus Notes' allows an application on any of the CICS platforms to initiate the sending of data to the Lotus Notes user. The CICS for Windows NT link extra allows data from non-Notes environments to be integrated into Lotus Notes. A link database provides mapping between the system application and fields defined in the Lotus Notes databases. The CICS for Windows NT link for Lotus Notes runs as a server add-in task, while the CICS for Windows NT link for Lotus Notes extra runs as an independent process.
If you install CICS in order to link to Lotus Notes, you should have Lotus Notes installed and have the documentation provided with Lotus Notes and CICS.
Note: CICS for Windows NT link for Lotus Notes is referred to as CICS link and CICS for Windows NT link extra for Lotus Notes is referred to as CICS link extra through this document.
The diagram below outlines the flow of data from a CICS
application to a Lotus Notes application.
Figure 1: CICS for Windows NT link extra for Lotus Notes
CICS for Windows NT link extra requires Lotus Notes Server Version 3.2 or later and CICS for Windows NT V2.0.1 or later.
CICS for Windows NT link extra requires Lotus Notes Server Version 4.1 or later when used with Transaction Server for Windows NT.
Please see the CICS for Windows NT link extra Overview Diagram for an explanation of how the components are integrated.
The diagram below shows how CICS for Windows NT link functions to
highlight the difference between CICS for Windows NT link and CICS for Windows NT link
extra.
Figure 3: CICS for Windows NT link for Lotus Notes Overview Diagram
This is a Lotus Notes Database that needs to be populated with entries which describe how the message data maps to fields in a given Lotus Notes document. The entry name of the Link-database document corresponds to the QUEUE information passed from the calling CICS application via the CICS START. The logical processing rules (e.g. If found Insert, Insert always, etc.) for each message retrieved are also specified in the database. The CICS link extra for Lotus Notes Link-database definition is an extension of the CICS for Windows NT link for Lotus Notes Link-database. As a result the CICS for Windows NT link extra for Lotus Notes Link-database may be used to define entries for both CICS for Windows NT link and CICS link extra.
dmdb.nsf (CICS for Windows NT link extra Link-database)
CICS for Windows NT link extra for Lotus Notes runs as an independent process. The process is started when the calling CICS application issues an EXEC CICS START command that issues a START to the defined CICS link transaction on the Notes Server.
The syntax of CICS START command used for the CICS link extra is as follows.
EXEC CICS START TRANSID(tranid) /* CICS Transaction to Start */ DATA(data) /* Data to be processed into Notes */ LENGTH(sizeof(data)) /* Size of passed data */ TERMID(termid) /* remote Term ID */ QUEUE(qname) /* link database entry field */
Note that the TERMID parameter is optional since the CICS link extra transaction may be run as a background task.
A sample Lotus Notes demonstration applications is provided
with CICS for Windows NT link extra. The CICS link extra Link-database
have entries that will allow for updating of documents contained
in the application databases. If you create your own applications,
a suitable Link-database entry must be created.
cltest1.nsf (Name Information) cltest2.nsf (Address Information)
The CICS application is a standard transaction application that passes data to the CICS system running on the Notes Server. The QUEUE data corresponds to the Link-database entry name.
An CICS sample application is provided to help you get started. This sample application is a C program designed to read messages from a provided data file. When the sample application is run, data is passed to CICS link extra that then places into the Lotus Notes sample databases as documents.
demo1.dll (CICS sample application for Windows NT Version 2) demo4.dll (CICS sample application for Transaction Server for Windows NT) demo1.dat (Sample data file)
The CICS for Windows NT link extra package is distributed as a zipped file called ca70.zip. Follow the steps below to setup the CICS for Windows NT link extra files on your hard drive.
unzip ca70.zip
CICS for Windows NT link extra includes three Lotus Notes database files which must be installed. There are two sample demonstration databases and a Link-database. The CICS for Windows NT link extra Link-database is an extension of the CICS for Windows NT link Link-database.
dmdb.nsf - CICS link extra Link-database cltest1.nsf - Name Information cltest2.nsf - Address Information
To place the Link-database in a directory other than the Notes directory, specify the directory name on the PATH statement in your config.sys.
CICS link extra supports multiple entries with the same ENTRY identifier, CICS link does not.
Transaction Code. . . . . . .LNKX Group Name. . . . . . . . . .CCLINKX Program Name. . . . . . . . .DEMO1 Task Class. . . . . . . . . .N Secure. . . . . . . . . . . .N Can Be Purged . . . . . . . .Y Use Alternate Screen Size . .N Priority. . . . . . . . . . .0 System ID . . . . . . . . . . Remote Transaction Code . . . Description . . . . . . . . .CICS link extra DEMO transaction
Transaction Code. . . . . . .CLNK Group Name. . . . . . . . . .CCLINKX Program Name. . . . . . . . .CCLINKX Task Class. . . . . . . . . .N Secure. . . . . . . . . . . .N Can Be Purged . . . . . . . .Y Use Alternate Screen Size . .N Priority. . . . . . . . . . .0 System ID . . . . . . . . . . Remote Transaction Code . . . Description . . . . . . . . .CICS link extra transaction
Program name: CCLINKX Description: CICS link extra for Notes Group: CCLINKX Program path: pathname\cclinkx4.dll
Program name: CCLXDEMO Description: CICS link extra demo Group: CCLINKX Program path: pathname\demo4.dll
where pathname is the full path of the directory in which you have placed the two executables.
Transaction name: CLNK Description: CICS link extra for Notes Group: CCLINKX First program: CCLINKX
Transaction name: LNKX Description: CICS link extra for Notes demo Group: CCLINKX First program: CCLXDEMO
Ensure that the purgeable attribute is checked for both transactions.
TDQ name: CLX3 Description: TD Queue for CICS link demo Group: CCLINKX Queue type: intrapartition Open queue: on request
Now that you have completed the set up work for Lotus Notes and CICS, you are ready to run the sample demonstration CICS and Lotus Notes applications. Two sample demonstration Lotus Notes databases are provided with CICS for Windows NT link extra. Running the sample will demonstrate how putting messages on a single triggered queue, separate documents in two different Lotus Notes database can be updated.
The LNKX transaction in the group CCLINKX should be defined. If not, go back and perform the CICS Setup procedure.
The CICS for Windows NT link extra package is distributed as a zipped binary
file. The CICS for Windows NT link extra directory contents are as follows:
\cclinkx.dll CICS link extra executable code for CICS Version 2 \cclinkx4.dll CICS link extra executable code for Transaction Server Version 4 \scclmsg.msg File containing messages used by CICS link extra \dmdb.nsf Lotus Link-Database \cltest1.nsf Lotus Demo database 1 \cltest2.nsf Lotus Demo database 2 \demo1.dll Demo executable to pass messages to the CCLINKX process (CICS V2) \demo4.dll Demo executable to pass messages to the CCLINKX process (Txn Svr V4) \demo1.dat Demo data for input into demo1.dll \demo1.ccs Demo source to load messages into CCLINKX process \demo1.mak Demo source make file for CICS Version 2 \demo4.mak Demo source make file for Transaction Server Version 4 \ca70.ps User's Guide (postscript format) \ca70.nsf User's Guide (Lotus Notes database) \ca70.htm User's Guide (html format) \ca70fig1.gif Diagram for html version of User's Guide \ca70fig2.gif Diagram for html version of User's Guide \ca70fig3.gif Diagram for html version of User's Guide
The Link-Database, DMDB.NSF, needs to be placed in the database directory on the Lotus Notes server that the Lotus client application will access. CICS link extra will read the Link-database entries to determine the Lotus Notes Documents and fields to update.
Entry: CLX3 Description: CICS link extra - Employee Name Database Database Information User Database Name: cltest1 Rule 3. If found Update, else Insert Output Offsets Map from external application to Notes Syntax: FieldName <space> Start <space> End <space> CHAR / INTEL-BINARY <KEY<Comparison>> CASE / NOCASE name 0 14 CHAR KEY CASE mname 20 34 CHAR lname 40 54 CHAR KEY CASE Additional Selection Formula (CICS link extra Only) (example: Salary > 100)
The Rule indicates how the data is processed given existing
documents in the Lotus Notes database.
There is not a default value for Rule and a Rule must be specified.
Specify search criteria to be used against the Notes database. This can be fields that are part of the database form. For example, salary > 1000. (Optional)
Note:When KEY fields are not specified and the Additional Selection Formula is blank, then the default selection will return all documents in the database.
All informational and error messages are displayed at the console
or recorded in the CICS error log.
Explanation:
User Response: None.
Explanation:
User Response: None.
Explanation: The database specified could be opened.
User Response: the database is specified correctly and is available.
Explanation: The database specified could not be opened.
User Response: Confirm that the database is specified correctly and available.
Explanation:
User Response: None.
Explanation: The database specified could be opened.
User Response: the database is specified correctly and is available.
Explanation: The database specified could not be opened.
User Response: Confirm that the database is specified correctly and available.
Explanation:
User Response: None.
Explanation:
User Response: None.
Explanation: One of the link database documents cannot be opened. It may be corrupted.
User Response: Check that all documents in the link database are correct.
Explanation: The formula was not able to be compiled by Lotus Notes.
User Response: Verify the KEY output offsets and Additional Selection Formula in the link database and retry the operation.
Explanation: A document was not found in the specified database.
User Response: Confirm the database is available and the document exists or not as appropriate. If the problem persists, contact your IBM support center.
Explanation: The CICS link extra database could not be closed.
User Response: Verify that the link database specified exists and is available to Lotus Notes.
Explanation: The database specified could not be opened.
User Response: Confirm that the database is specified correctly and available.
Explanation: The database specified could not be opened.
User Response: Confirm that the database is specified correctly and available.
Explanation: The link database mapping entry for field was specified with a BINARY type, but the width was incorrect. Correct values include 2, 4 and 8.
User Response: Correct the problem in the link database.
Explanation: One Item type was expected (most likely TEXT), and another was detected.
User Response: Check the link database and correct the field.
Explanation: No field offset mappings were specified in a document in the link database.
User Response: Check the link database.
Explanation: No field offset mappings were specified in a document in the link database.
User Response: Check the link database and correct the field.
Explanation: The database specified could not be opened.
User Response: Confirm that the database is specified correctly and available.
Explanation: The condition was meet based on the rule specified.
User Response: Examine the rule and the error log.
Explanation: The condition was meet based on the rule specified.
User Response: Examine the rule and the error log.
Explanation: The condition was meet based on the rule specified.
User Response: Examine the rule and the error log.
Explanation: The condition was meet based on the rule specified.
User Response: Examine the rule and the error log.
Explanation: The condition was meet based on the rule specified.
User Response: Examine the rule and the error log.
Explanation: Some rule other than 0-9 was specified in the link database entry.
User Response: Examine the link database and correct the invalid rule using a value of 0-9.
Explanation: The database specified could not be closed.
User Response: Confirm that the database is specified correctly and is available.
Explanation: An internal function of the product attemted to obtain storage, but there was none available.
User Response: Restart CICS link extra. If the problem persists, save the generated output files and contact your IBM support center.
Explanation: An internal function of the product attemted to obtain storage, but there was none available.
User Response: Restart CICS link extra. If the problem persists, save the generated output files and contact your IBM support center.
Explanation: A problem was encountered compiling the specified formula.
User Response: Confirm the formula is correct and retry the operation. If the problems persists, contact your IBM support center.
Explanation: A note could not be opened.
User Response: Confirm the note is available and retry the operation
Explanation: A note item could not be updated.
User Response: Confirm the note is available and retry the operation. If the problem persists, contact your IBM support center.
Explanation: A note item could not be updated.
User Response: Confirm the note is available and retry the operation. If the problem persists, contact your IBM support center.
Explanation: A note item could not be updated.
User Response: Confirm the note is available and retry the operation. If the problem persists, contact your IBM support center.
Explanation: Another error was flaged in processing and as a result the program tried to cleanup processing and failed at that as well.
User Response: retry the operation. If the problem persists, contact your IBM support center.
Explanation: An internal function of the product attemted to obtain storage, but there was none available.
User Response: Restart CICS link extra. If the problem persists, save the generated output files and contact your IBM support center.
Explanation:
User Response: None.
Explanation: An internal function of the product attemted to obtain storage, but there was none available.
User Response: Restart CICS link extra. If the problem persists, save the generated output files and contact your IBM support center.
Explanation:
User Response: None.
Explanation: No rule was defined in the meta db or is corrupted.
User Response: Check the meta db.
Explanation:
User Response: Check the meta db.
Explanation: A error was flaged in CICS processing
User Response: Check the CICS log and the SCCL log for errors.