This Dokument describes step by step how to install the Con-nect transport service for execution in batch mode using the EntireX Broker Services LU6.2 API (referred to in this section as the LU6.2 API), EntireX Broker Services APPC Adapter (referred to in this section as the LU6.2 ACI) or Remote Database Access.
Anmerkung:
As an alternative to the LU6.2 API that uses the Natural VIEW
COMMUNICATE-LU62, you can now use the LU6.2 ACI. It uses the EntireX Broker ACI
interface programs to map requests to LU6.2 verbs, which helps reduce the
network traffic. For further information, contact your EntireX Broker Services
support representative.
It is recommended that you review the Con-nect Administration documentation, section The Transport Service, sub-section Overview of the Transport Service Architecture before you begin the installation procedures.
This Dokument contains the following topics:
Before you begin the installation process, you need the following information:
If your server programs use the LU6.2 API:
The LU names which the VTAM system programmer assigned to the local and adjacent systems (see steps 3 and 4).
The VTAM log mode name which is used for APPC sessions to the adjacent systems (see steps 3 and 4).
The node number assigned to the respective LU6.2 API process (see steps 3 and 4).
The TPNs which identify the corresponding receiving programs at the adjacent nodes (see step 3).
The TPN which identifies the receiving program at the local node (see step 4).
If your server programs uses the LU6.2 ACI:
The name of the server which identifies the directory information at the local node (see step 4). The name specified must correspond with the member that exists in the dataset specified in the EntireX Broker startup parameter APISERV.
The name of the server which identifies the directory information at the adjacent node (see step 3). This name must correspond with the dataset member that specified in the EntireX Broker startup parameter APISERV.
If your server programs use remote database access:
The database ID and file numbers of the adjacent systems' Con-nect spool files (See step 3).
To configure and maintain the transport service, see the Con-nect Administration documentation, section The Transport Service.
This step is performed during the installation of Con-nect. See Installation Procedures for Con-nect.
Certain requirements must be satisfied when generating the Natural nucleus (or nuclei) which will be used by the "end user" and "server programs" applications of the transport service. The requirements for the end user application are less stringent than the requirements for the server programs application.
The following requirements are for the transport service end user application and will be performed during the installation of Con-nect:
The environment must include a fully operational Con-nect system version 3.
The environment must contain a valid reference to a Con-nect spool file. The spool file identifier number is 223. This reference can be specified in the Natural parameter module with a NTLFILE macro call, or dynamically with the Natural keyword LFILE.
Anmerkung:
Do not use Adabas passwords or ciphering for either the Con-nect
spool file or the Con-nect system file.
The transport service system programs must be loaded into the appropriate Natural system file.
The Natural keyword CSIZE which specifies the size of the Con-nect buffer, must be assigned a value of at least 20.
The CSTATIC list from the Natural parameter module must specify the module name CTMOD.
CTMOD must be linked to the Natural nucleus.
The following requirements are for the transport service server programs application:
All of the requirements for the end user application also apply to the server programs application.
The statement NTDB PROCESS, 148 must be added to the Natural parameter module. (Applicable only when the queues are serviced with the LU6.2 API.)
The Natural PROCESS auxiliary buffer, ASIZE, must reflect the requirements of Software AG's XCOM Communication Module. The recommended value is 28. (Applicable only when the queues are serviced with the LU6.2 API.)
The Natural system keywords listed below must be set as follows:
| Natural Keyword | Required Setting |
|---|---|
| WH | ON |
| MADIO | 0 |
| MAXCL | 0 |
| AUTO | OFF |
| ETID | Blank |
Tipp:
The setting ETID=` ' (blank) is recommended but not required.
However, it is important to note that if the Natural keyword ETID is set to
blank and more than one transport service server program uses the same Natural
user ID and they become active simultaneously Adabas will not issue an error
message.
Anmerkungen:
Initializing the transport service consists of two parts: defining the transport service node ID and the actual initialization. See the Con-nect Administration documentation, section The Transport Service, sub-section Initializing the Transport Service.
Anmerkung:
The next steps define the path the transport items take from
Con-nect to other nodes. If changes are made in your SNA network, you may need
to re-execute the following steps.
At least one outbound queue must be created for each adjacent node in the network. When an outbound queue is created, the attributes of the LU6.2 API, LU6.2 ACI or remote database access link between the local and the adjacent node must be defined.
If you are using LU6.2 ACI, the server name of the outbound queue must correspond with the member that exists in the dataset specified in the EntireX Broker startup parameter APISERV. This member contains specific LU6.2 information for the adjacent node. The following table lists the parameters that are used:
| Parameter | Description |
|---|---|
| DRIVER=COMMLU62 | Specifies the LU6.2 protocol. |
| TPNAME= | The TPN which identifies the corresponding
receiving programs at the adjacent node.
|
| LUNAME= | The LU name which the VTAM system programmer assigned to the adjacent system. |
| MODENAME= | Specifies the VTAM LOGMODE name used for APPC sessions to establish a communication link to the adjacent system. |
| SYNCLEVEL=Y | Specifies confirmation level synchronization is to be used. |
| TRANSLATION= | Specifies the name of the exit routine used to translate data contained in the SEND/RECEIVE buffers. |
| LOCAL-LU | Specifies the VTAM LOCAL-LU parameter. |
To create one or more outbound queue, see the Con-nect Administration documentation, section The Transport Service, section Outbound Queues.
At least one receiving queue must be created if the local node will receive transport items by means of the LU6.2 API, LU6.2 ACI or remote database access. The receiving queue is used to control the demon processes which continuously listen for transaction requests from adjacent nodes or poll an intermediate queue in the case of remote database access.
If you are using LU6.2 ACI, the server name of the receiving queue must correspond with the member that exists in the dataset specified in the EntireX Broker startup parameter APISERV. This member contains specific LU6.2 information for the local node. The following table lists the parameters that are used:
| Parameter | Description |
|---|---|
| DRIVER=COMMLU62 | Specifies the LU6.2 protocol. |
| TPNAME= | The unique name used to identify the server at the local node. It must be the same as that specified in the Server Program field in the "EntireX LU6.2 ACI Receiving Queue" screen. |
| LUNAME= | The LU name which the VTAM system programmer assigned to the local system. Omit this parameter if it is the same LUNAME as specified with the LOCAL-LU keyword or the DEFLUNAM EntireX Broker startup parameter. |
| MODENAME= | Specifies the VTAM LOGMODE name used by the adjacent system for APPC sessions to establish a communication link to the local system. |
| SYNCLEVEL=Y | Specifies confirmation level synchronization is used. |
| TRANSLATION= | Specifies the name of an exit routine used to translate data contained in the SEND/RECEIVE buffers. |
| LOCAL-LU= | Specifies the VTAM LOCAL-LU parameter. |
To create a receiving queue, see the Con-nect Administration documentation, section The Transport Service, sub-section Receiving Queues.
An application queue must be created for each application at the local node which will use the transport service. Transport items which are sent to the application are placed in these queues and remain there until they are processed by the local application.
When you create an application queue for Con-nect external mailing, specify the following on the "Application Queue" screen:
In the "Node ID" field, enter the name you specified as your transport service ID. See Initializing the transport service.
In the "Application Name" field, enter A.
In the "Application Library" field, enter SYSCNT2.
In the "Application Program" field, enter YCINITO.
To create an application queue, see the Con-nect Administration documentation, section The Transport Service, sub-section Application Queues.
When you initially test the transport service, the input status of the inbound, outbound and application queues must be set to active, and the reset status to inactive. To set the input and reset statuses of the queues, perform the following steps; they must be repeated for each of the above mentioned queues:
Select the Queue Maintenance function from the "Transport Service Administration" screen to display the "Queue Maintenance" screen.
Enter MO (modify) in the Cmd column for the appropriate queue and press ENTER. The corresponding screen is displayed. Modify the following fields:
In the "Reset Status" field, enter I (inactive).
In the "Input Status" field, enter A (active).
Mark the "Reset" field with any character and press PF9.
For further information about the "Queue Maintenance" screen, see the Con-nect Administration documentation, section The Transport Service, sub-section Queue Maintenance.
The input handler is used as an interface to the LU6.2 API, LU6.2 ACI or to read mail items which have been copied from a remote database to an intermediate queue and initiates the demon processes. When the demon processes are initiated, they listen for transaction requests from remote partner nodes. When a request is caught, the demon processes execute the TS_RECEIVE program. The input handler procedure consists of the execution of the Natural nucleus in batch mode.
The following is an example of a JCL input handler procedure in the case of the LU6.2 API or LU6.2 ACI:
//CMSYNIN DD * LOGON SYSCNT2 YIX8DEM xxxx FIN /*
where xxxx is the name of the receiving queue. To stop the input handler procedure you must set the status of the dummy queue to H (hold).
Anmerkung:
If remote database access is used, YIX8DEM is replaced with
YIX7DEM.
The queue server processes the inbound, outbound, and application queues. A queue server can be specified to handle one or a multiple of queues.
The following is an example of a JCL queue server procedure:
//CMSYNIN DD * LOGON SYSCNT2 YSCHED 2 x FIN /*
where 2 is the length of time (in minutes) between subsequent processing of the specified queues and x is the scheduling class.
The queue server processes will process all inbound, outbound and application queues whose scheduling match the value specified for x and whose output status is I (inactive). If a scheduling class has not been specified for YSCHED (i.e. x is empty), the queue server processes will process all queues.
To stop the queue server procedure you must set the statuses of all queues, specified within the procedure, to H (hold).
For each node in your network with which you want to communicate, you must define a routing entry which determines how transport items are to be routed to that node.
To define a routing entry, see the Con-nect Administration documentation, section The Transport Service, sub-section Routing Entries.
Before you can test the installation of the transport service, you must install an external mail application which is based upon the transport service. For further information, see the appropriate installation manuals.
Once an external application which uses the transport service has been installed, you can test the installation of the transport service.
The following test uses multi-node Con-nect as an example.
When testing, use the following settings for the inbound and receiving queue:
Input Status: A
Output Status: I
Reset Status: I
All other queues must be set to the following:
Input Status: A
Output Status: H
Reset Status: H
This guarantees that the queue servers will be activated only when they are started from the "Queue Maintenance" screen.
If you try to start a queue server when either the outbound or inbound queue is in the "hold" status, the queue server task will immediately exit without processing any information.
Start the input handler procedure. This activates the demon processes so that they listen for transmission requests from remote Con-nect nodes.
Send a mail item from Con-nect or another external mail application based upon the transport service method and request a delivery notification. Then check the inbound queue for the transport item.
Start the JCL server procedure for the inbound queue YSCHED program with the scheduling class. This activates the "router", which should route the transport item to the outbound queue. Since the outbound queue is set in the hold status, the transport item should remain in the outbound queue. As soon as the appropriate Natural queue server program has been started by YSCHED (in the case of the inbound queue's router program, it is YR), that program will change the output status from I to A, and, at the end of its execution, back to I (if successfully terminated) or to H (if terminated due to errors). In both cases (successful and unsuccessful termination), you can check the log records in order to obtain additional information.
Check to see if the transport item was routed to the outbound queue. (The same test procedure can be applied to the other queues as well.) Up to this point, LU6.2 or remote database access have not been involved. The following steps allow you to test sending a transport item to another node.
Set the respective outbound queue status to the following: Input Status: A Output Status: I Reset Status: I and the scheduling class to the same value as the inbound queue, thus, causing the server to process the outbound queue.
Check the log records. The log records are accessed from the Log Information Maintenance function on the "Transport Service Administration" screen. If the transport item was successfully sent, records from the TS_SEND program, YOX8000 (in the case of the LU6.2 API), YOX8000B (in the case of the LU6.2 ACI) or YOX7000 (in the case of remote data base access), are displayed.
Check for log records which were created when a status report was received from the target node. Records from the TS_RECEIVE program YIX8000 (in the case the LU6.2 API), YIX8000B (in the case of the LU6.2 ACI) or YIX7000 (in the case of remote database access) should be displayed.
Check to see whether the status report was delivered to the appropriate application queue.
If you are still experiencing problems, the following commands and functions can be useful for debugging purposes: VTAM Operator Console Commands, EntireX Broker Services Operator Commands, and the Transport Service Administration Functions.
The following functions can be performed from the Transport Service Administration Menu:
Queue Maintenance - Provides a transport item count, time stamps for recent activity, and the ability to manually start the queue server.
Log Information Maintenance - Provides information that can be helpful to you or, in the case of severe malfunctions, to Software AG, in resolving any problems you experience with the transport service.