Listing 4‑1
SYSTEM Statement Syntax
SYSTEM,
SLEEPTIME=(sleep-min,sleep-max,sleep-delta),
OTMACLIENT=TMA
-clientname],
OTMAGROUP=
XCF-groupname]
[,OTMASECURITY={Yes|
No}]
[,MSGLEVEL={
msg-level|
4}]
[,CLIENTSHUTDOWN={Yes|
No}]
[,IDLETIMEOUT={nn|
0}]
[,DRUEXIT=exit-name|
DFSYDRU0]
[,SPARESOCKETS=nn|0]
The SYSTEM statement uses the following parameters.
Listing 4‑2
HOST Statement Syntax
HOST,TYPE=IMS,
IMSID=IMS-system-logical-identifier,
OTMANAME=
IMS-clientname,
OTMAINPIPE=
server-request-name,
OTMAOUTPIPE=
client-request-name]
[,NUMTPIPES=(nnnn|1)]
MAXRSPLEN=nnnn
The HOST statement uses the following parameters.
One or more GATEWAY TYPE=LOCAL statements must exist in the configuration file to define the local gateways. Each
GATEWAY TYPE=LOCAL statement defines a specific IP address and port number through which TMA TCP for IMS accepts inbound connection requests from remote gateways. Inbound connections are used by a remote gateway to send client requests to the IMS gateway for processing by IMS server transactions. Each local gateway (as defined by a
GATEWAY TYPE=LOCAL statement) must have a unique logical machine ID (a symbolic name used to identify a gateway).
Listing 4‑3 contains the parameter syntax for the local gateway.
GATEWAY,TYPE=LOCAL,
LMID=logical-machine-id,
PORT=
port-number,
ACCOUNT={
account-id|*},
PASSWORD={
password|*}
[,HOSTADDR=(
ip-address|hostname)]
[,MAXMSGLEN={
max-message-length|
2048}]
[,SESSIONS={(
startup-sessions,max-sessions)|
1}]
[,IDLETIMEOUT={nn|
0}]
[,MULTIPLEX={nn|
1}]
The GATEWAY TYPE=LOCAL statement uses the following parameters.
One or more GATEWAY TYPE=REMOTE statements are used in the configuration file to define remote gateways. Each
GATEWAY TYPE=REMOTE statement defines the IP address and port number that TMA TCP for IMS uses to establish an outbound connection with a remote gateway. The
GATEWAY TYPE=REMOTE statement also identifies a remote gateway by a unique logical machine ID.
The configuration file may contain multiple GATEWAY TYPE=REMOTE statements, each defining a different remote gateway. If no
GATEWAY TYPE=REMOTE statements are present, then TMA TCP for IMS cannot establish outbound connections with remote gateways, and therefore cannot process IMS client requests.
Listing 4‑4 contains the parameter syntax for the
GATEWAY TYPE=REMOTE statement.
GATEWAY,TYPE=(REMOTE,{TUX|IMS|CICS,tran-id|CICSCPT}),
LMID=logical-machine-id,
HOSTADDR=(ip-address|hostname),
PORT=port-number,
ACCOUNT={account-id,*},
PASSWORD={password,*}
[,MAXMSGLEN=max-message-length|2048]
[,SESSIONS=(min-sessions),(max-sessions)]
[,MULTIPLEX={nn|0}]
[,
IDLETIMEOUT={nn|0}]
The GATEWAY TYPE=REMOTE statement uses the following parameters.
|
|
|
|
|
|
|
TUX - The remote gateway is an TMA TCP Gateway gateway.
IMS -The remote gateway is an TMA TCP for IMS gateway.
CICS, tran-id - The remote gateway is an TMA TCP for CICS gateway. tran-id specifies the 1-4 character name of the TMA TCP for CICS transaction that is to be scheduled by CICS to handle incoming TCP/IP TMA requests. Refer to the Oracle Tuxedo Mainframe Adapter for TCP CICS User Guide for more information.
CICSCPT - The remote gateway is an TMA TCP for CICS gateway that uses the Interlink CPT product for TCP/IP access.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
One or more SERVICE TYPE=REMOTE statements are used in the configuration file to define remote services. Each
SERVICE TYPE=REMOTE statement defines the local service name (used by the IMS client transaction to request the service), the remote service name (used to invoke the service on the remote system), and the logical machine ID of a remote gateway that offers the service. There must be a corresponding
GATEWAY TYPE=REMOTE statement in the configuration file for the specified logical machine ID.
The configuration file can contain multiple SERVICE TYPE=REMOTE statements for a given (local) service name, each pointing to a different logical machine ID (that is, remote gateway). In this case, TMA TCP for IMS distributes requests for the service among the available service providers, thus maximizing throughput during busy periods.
Listing 4‑5 contains the parameter syntax for the
SERVICE TYPE=REMOTE statement.
SERVICE,TYPE=REMOTE,
NAME=(local-service-name,
remote-service-name),
LMID=
logical-machine-id
[,TIMEOUT={
timeout|
30}]
The SERVICE TYPE=REMOTE statement uses the following parameters.
Listing 4‑6 contains the parameter syntax for the
SERVICE TYPE=LOCAL statement.
|
Note:
|
SERVICE TYPE=LOCAL statements are only used when running TMA TCP for IMS as an OTMA client.
|
SERVICE,TYPE=LOCAL,
NAME=(local-service-name,
remote-service-name),
IMSID=
logical-IMS-id,
[,V21COMPAT={Yes|
No}]
[,FASTPATH={Yes|
No}]
[,SECURITY={Yes|
No}]
[,RESPONSE=
remote-service-name]
The LOCAL SERVICES statement uses the following parameters.
The TMA TCP for IMS product makes use of a configuration file that is read and processed at runtime to establish the processing environment. The configured parameters can be modified while the gateway is running. You can make the following changes to the TMA TCP for IMS gateway configuration dynamicallyby entering the commands on TCP Outstanding WTOR:
Listing 4‑9
INFILE Command Example
To stop a gateway, use the STOP GATEWAY command with the
LMID parameter. Use the
IMMED=YES parameter to stop the gateway immediately
without waiting for requests in progress to complete. Outstanding requests are sent an error message and all gateway connections are closed. Use the
IMMED=NO to allow the gateway to complete transaction processing and then shutdown. While waiting, the gateway does not accept any new requests.
IMMED=NO is the default. The example in
Listing 4‑12 stops the OS3901 gateway after transaction processing completes.
|
2.
|
Then use the MOD HOST command to change any supported parameter definitions. You must specify an IMSID for the MOD HOST command.
|
The following HOST statement parameters are modifiable with this command.
To stop a host, use the STOP HOST command with the
IMSID parameter with a value matching the
IMSID specification on the
HOST, TYPE=IMS statement. Refer to the
“Defining the Local Gateway” section. Use the
IMMED=YES parameter to stop the host immediately
without waiting for requests in progress to complete. Outstanding requests are sent an error message. (For a description of error messages, refer to the
“Error and Informational Messages” section.) Use the
IMMED=NO to allow the host to complete processing outstanding requests and then shutdown. While waiting, the host does not accept any new requests.
IMMED=NO is the default. The example in
Listing 4‑17 stops the IMS3 host after transaction processing completes.
Listing 4‑18
ADD SERVICE Command (RemoteService) Example
To stop a remote service, use the STOP SERVICE command with the
LMID and
NAME parameters. In this case, the
NAME parameter only specifies the
local name, rather than the fully qualified (
local name, remote name) syntax. Use the
IMMED=YES parameter to stop the service immediately
without waiting for requests in progress to complete. Outstanding requests are sent an error message. Use the
IMMED=NO to allow the requests to complete processing. While waiting, the gateway does not accept any new requests.
IMMED=NO is the default. The example in
Listing 4‑19 stops
ECHO on the
TUX1 gateway.
|
2.
|
Then use the MOD SERVICE command to change the service information. Use the LMID and NAME parameters to specify the service you want to modify. The TIMEOUT parameter in the SERVICE TYPE=REMOTE statement is the only parameter that can be modified with this command and is required.
|
The example in Listing 4‑20 uses the
MOD SERVICE command. In this case, the
NAME parameter only specifies the
local name, rather than the fully qualified (
local name, remote name) syntax.
Listing 4‑20
MOD SERVICE Command (Remote Service) Example
To start a service, use the START SERVICE command with the
LMID and
NAME parameters. In this case, the
NAME parameter only specifies the
local name rather than the fully qualified (
local name, remote name) syntax. The example in
Listing 4‑21 starts the
TUX1 service.
Listing 4‑22
ADD SERVICE Command (Local Service) Example
To stop a local service, use the STOP SERVICE command with the
IMSID and
NAME parameters. In this case, the
NAME parameter only specifies the
remote name, rather than the fully qualified (
local name, remote name) syntax. Use the
IMMED=YES parameter to stop the service immediately
without waiting for requests in progress to complete. Outstanding requests are sent an error message. Use the
IMMED=NO to allow the requests to complete processing. While waiting, the gateway does not accept any new requests.
IMMED=NO is the default. The example in
Listing 4‑23 stops
ECHO on the
IMS1 host.
|
2.
|
Then use the MOD SERVICE command to change any supported parameters.
|
The following SERVICE TYPE=LOCAL statement parameters can be modified with this command.
The example in Listing 4‑24 uses the
MOD SERVICE command. In this case, the
NAME parameter only specifies the
remote name, rather than the fully qualified (
local name, remote name) syntax.
To start a local service, use the START SERVICE command with the
IMSID and
NAME parameters. In this case, the
NAME parameter only specifies the
remote name, rather than the fully qualified (
local name, remote name) syntax. The example in
Listing 4‑25 starts the
ECHO service for
IMS1.
Use the STATUS command to display the status of the TMA TCP gateway. The command displays XCF status with all IMS hosts, the number of messages processed, the number of XCF messages received, message control block usage, and service counts. The following status codes for IMS hosts can result:
