Interfaces and Integration Points Best Practices › TCP/IP Terminal Interface

TCP/IP Terminal Interface

Use the TCP/IP terminal interface for short running commands that have minimal output.

The TCP/IP terminal interface uses TCP/IP to send batch commands to, and receive command output from CA7ONL. The interface can be executed from batch, from a REXX address environment, or in a program-to-program mode. Because the interface uses TCP/IP, there is no requirement for shared DASD between the MVS images where CA WA CA 7 Edition executes and where the TCP/IP interface environment executes.

TCP/IP terminals are defined in the initialization file as CAICCI terminals.

Update the initialization file on each instance of CA7ONL that is to use the TCP/IP interface. Add the following keyword to the UCC7VTAM statement:

TCPTPORT=nnnnn

where nnnnn is a number from 1 to 65535. This number is the TCP/IP port number on which CA7ONL listens for incoming messages. The port number must be registered in the profile of the running TCP started task.

Also, on the UCC7VTAM statement is the TCPTMOUT parameter. This parameter specifies the number of seconds in which to receive responses. The default is 10 seconds.

When CA7ONL starts, it recognizes the TCPTPORT keyword and the CAICCI terminal definitions. This recognition causes the TCP/IP terminal interface to initialize. You next see messages similar to the following in the SYSLOG:

CAL2T050I TCP/IP host name is USCOMP31

CAL2T051I TCP/IP host addr is 155.222.67.89

CAL2T065I TCP/IP port number is 4071

Use the following JCL to execute the TCP/IP batch interface:

//jobname JOB (user job parms) 
//JS1 EXEC PGM=CAL2X2TB,PARM='USCOMP31.CO.COM,4071,CA71'
//STEPLIB DD DISP=SHR,DSN=cai.ca7.cal2load
//SYSPRINT DD SYSOUT=* 
//ERRORS DD SYSOUT=* 
//SYSIN DD * 
..... 
(CA 7 commands go here) 
..... 
// 

The command input is in Batch Terminal Interface format.

The PARM information provided on the execute statement is positional and is required. The first position is the TCP/IP address where CA7ONL runs. The second position is the TCP/IP port number where CA7ONL listens. The third position is the name of the CA7ONL instance.

Note: Most customers run in a multiple LPAR environment and batch jobs run on different LPARs. If so, connect each LPAR using TCP/IP to the LPAR where the CA7ONL started task resides.

Business Value:

Using the TCP/IP interface lets you process short running commands using TCP/IP quickly.