This document covers the following topics:
The database must be UES-enabled for TCP/IP access. For more information, read Enabling Universal Encoding Support (UES) for Your Adabas Nucleus.
A TCP/IP link uses Entire Net-Work modules. These modules communicate using the standard ADALNK module. Translation tables can be customized and reassembled and then made available in the Adabas STEPLIB. The Adabas ADALNK module is supplied with the LNKUES module and the default translation tables ASC2EBC and EBC2ASC.
The Entire Net-Work WCPvrs and WTCvrs libraries must be defined in the STEPLIB concatenation. The sample startup job for a UES-enabled nucleus with TCP/IP support is provided in member ADANUCT. For more information, read JCL Required for UES and TCP/IP Support (z/OS).
UES-enabled databases are connected directly through TCP/IP using the Adabas standard batch or TSO link routine ADALNK. The sample job stream to link the ADALNK module with your modified translation tables is ALNKUES.
In addition, the ADALNK module must have the correct SVC set in the LNKGBLS module.
The LNKGBLS is delivered in the ADAvrs.SRCE library and its assemble job is in ADAvrs.JOBS(ASMGBLS). Use the job as a guide to assemble the LNKGBLS module with the correct SVC.
Assemble the ASCII to EBCDIC and EBCDIC to ASCII translation tables, either default or customized. Use job ALNKUES in the ADAvrs.JOBS library as a guide for customizing site-specific JCL.
It is now necessary to (re)link ADALNK with LNKUES and your customized and reassembled translation tables.
Link the ADALNK, ASC2EBC, EBC2ASC, LNKUES, and other user exit modules into a final ADALNK module that is UES-enabled. Place this load module into a "USER.LOAD" library. Sample job LNKLNK8 is provided as a guide in the ADAvrs.JOBS library.
The (re)linked ADALNK must be made available to the Adabas nucleus.
If you are calling Adabas Version 8 directly through a TCP/IP link and the correct ADALNK is not available to the Adabas nucleus or the SVC has not been set correctly, Adabas produces unexpected results, such as response code 148 (ADARSP148) and empty buffers.
To activate a direct TCP/IP link to the Adabas nucleus:
Set the ADARUN parameter TCPIP=YES.
Specify a universal resource locator (URL) in the ADARUN parameter TCPURL.
The URL is a 20-byte address that conforms to the RFC specification for URLs.
You can specify the URL required to activate the direct TCP/IP link in the ADARUN parameter TCPURL. For more information, read TCPURL Parameter: TCP/IP Universal Resource Locator, in the Adabas Operations Manual.
Optionally, you can specify the first and additional URLs using the operator command TCPIP:
TCPIP={ OPEN=url|CLOSE=url | CLOSE }
where url is the URL for the TCP/IP link you want to open or close and has the same format as the ADARUN TCPURL parameter. For more information, read TCPURL Parameter: TCP/IP Universal Resource Locator, in the Adabas Operations Manual.
The command allows you to open or close a TCP/IP link to the Adabas nucleus or to close all links. It can only be used when ADARUN TCPIP=YES and all conditions for that setting have been met. This command can be used to close the URL set in the ADARUN TCPURL parameter, or to open/close additional TCP/IP links.
TCPIP=OPEN=OES://:12216 TCPIP=CLOSE=OES://:12216 To close all open URLs: TCPIP=CLOSE