Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Installing and Using TIBCO Service Gateway for Files : Management of Service Gateway for Files

Management of Service Gateway for Files
This section describes how to start, shut down, or automatically restart Service Gateway for Files.
Startup of a Service Gateway for Files
On z/OS, you start the Service Gateway for Files by submitting JCL as that described under Sample Configuration.
Shutdown of a Service Gateway for Files
On z/OS, you shut down a Service Gateway for Files using the Data Object Broker operator command STOPSERVER. The following shows the format of the command, where ALLHURON and ALLAPI refer to servers that are either Service Gateway for Files or Peer Servers.
MODIFY dob_jobname,Stopserver=ALLHURON
MODIFY dob_jobname,Stopserver=ALLAPI
MODIFY dob_jobname,Stopserver=SRVIDserverid
MODIFY gateway_jobname,SHUTDOWN
See Also
TIBCO Object Service Broker for z/OS Installing and Operating for more information about the STOPSERVER command.
Service Gateway for Files can be shut down using their server user ID. Server user IDs are auto-generated in the following format:
@EERRRXX
where:
XX contains the two alphanumeric characters (base 6) derived from the server number for the server in the Execution Environment. An Execution Environment associates a unique identifier for each Service Gateway for Files or Peer Server it starts. Alphanumeric characters are used rather than numbers to allow for more than 99 servers. Example: @SV2WU01.
Automatic Restart of a Service Gateway for Files
If a logical error is detected during Service Gateway for Files operation and the server terminates, the Execution Environment logs the error and restarts the server.
When a Service Gateway for Files terminates normally, the server session is not restarted.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved