Copyright © Cloud Software Group, Inc. All Rights Reserved

Starting the Gateway

You can run the Gateway as either a batch job or a started task. For information on adding the Gateway tasks, refer to Adding the Gateway Tasks.

Running the Gateway as a Batch Job

If the Gateway is running as a batch job, you can access data through either the Central Version or in Local mode.

Central Version

A sample batch JCL to run the Gateway accessing data through the Central Version is located in member IDMSSJCL of the JCL data set. Customize the JCL to run with CA‑IDMS and submit it.

Local Mode

A sample batch JCL to run the Gateway in Local mode is located in member IDMSLJCL of the JCL data set. You must define each CA‑IDMS database to be used during Local mode processing in the Gateway’s JCL. If running the Gateway in Local mode, only one task is available. Customize the JCL to run with CA‑IDMS and submit it.

Running the Gateway as a Started Task

If you are running the Gateway as a started task, you can access data either through the Central Version or in Local mode as follows:

Central Version	Modify the JCL member IDMSSJCL of the JCL data set to be a JCL procedure and move it to your site PROCLIB (for example, SYS1.PROCLIB). You can then start the Gateway from the z/OS operator console using the z/OS START command.
Local Mode	Modify the JCL member IDMSLJCL of the JCL data set to be a JCL procedure and move it to your site PROCLIB (for example, SYS1.PROCLIB). You can then start the Gateway from the z/OS operator console using the z/OS START command.

See Also

TIBCO Object Service Broker Messages With Identifiers for information on messages produced by the Gateway.

Copyright © Cloud Software Group, Inc. All Rights Reserved