IOAGATE installation sheet

A. IOAGATE Started Tasks:

Determine the number of IOAGATEs and which client applications will be supported by each one:

IOAGATE ECAPARM

Procedure Name Suffix (PSFX) Client Applications

_____________ ___________ __D __F __O __M

A. IOAGATE Started Tasks

Decide whether a single IOAGATE will support all your IOAGATE application servers (client applications) or whether dedicated, separate IOAGATEs will support each application server. It is also possible to distribute the application servers between two or more IOAGATE started tasks without fully dedicating one IOAGATE per application server. Dedicating an IOAGATE per application is the fastest method and we recommend that this method be implemented unless it is essential to minimize address spaces.

Each IOAGATE that you start must have a unique JCL procedure that loads a unique ECAPARMx member. ECAPARMx members are distinguished by one‑character member suffixes (the x in ECAPARMx), which must be specified to IOAGATE via the EXEC PARM JCL parameter PSFX.

When specifying the application servers, and when using this planning sheet, use the following key:

D Control‑D/Page on Demand (CTD/POD)

F Control‑D/File Transfer Option (CTD/FTO)

O Control‑O (CTO)

M Control‑M Application Server (CTM)

For further details, see step 20.2 in the section titled Configure IOAGATE Parameters, and the Chapter on IOAGATE installation and configuration considerations in the INCONTROL for z/OS Installation Guide: Installing.

B. IOAGATE Application Servers and their Channels

Specify for each supported application its Channel ID

For D: Channel ID:___________

For F: Channel ID:___________

For O: Channel ID:___________

For M: Channel ID:___________

B. IOAGATE Application Servers and their Channels

If IOAGATE will be used to support CTD/POD, it is possible to start multiple application server address spaces for supporting it (cloning).

ALL CTD/POD application server address spaces can use the same channel. Address space cloning as described above is possible also for CTD/FTO.

If CTO is supported, it can share the same channel with CTD/POD.

CTD/FTO must have a dedicated channel

CTM must have a dedicated channel.

For further details, see step 20.2 in the section titled Configure IOAGATE Parameters, and the chapter on IOAGATE installation and configuration considerations in the INCONTROL for z/OS Installation Guide: Installing.

C. Channels: Specify for each channel

Channel: Channel model: ___MC ___DC

Channel protocol: ___TCP/IP ___SNA

If TCP/IP: Channel port: ____________

TCP/IP vendor: ___IBM ___CA

If CA:

Subsystem Name: ___Default ___Other:

If O is using the channel (either dedicated or shared with D):

Network Map: __________ Node ID: ___________

If SNA: Channel APPLID: ______________(MC only)

If O is using the channel (either dedicated or shared with D):

Network Map: ___________ Node ID: __________

Channel: Channel model: ___MC ___DC

Channel protocol: ___TCP/IP ___SNA

If TCP/IP: Channel port: ____________

TCP/IP vendor: ___IBM ___CA

If CA:

Subsystem Name: ___Default ___Other:

If O is using the channel (either dedicated or shared with D):

Network Map: ___________ Node ID: ___________

If SNA: Channel APPLID: ________________ (MC only)

If O is using the channel (either dedicated or shared with D):

Network Map: ___________ Node ID: ___________

C. Channels: Specify for each channel

Channels must be defined per application, as follows:

CTD/POD (D) - - - - - - - - - - - - - - - MC

CTD/FTO (F) - - - - - - - - - - - - - - - MC

CTO (O) - - - - - - - - - - - - - - - - - - MC

CTM (M) - - - - - - - - - - - - - - - - - - DC

Channel protocol can be either TCP/IP (for all applications) or SNA for Control‑O and CTD/POD, which also support SNA.

Repeat the planning definitions for each channel as necessary. Space for three channels has been provided on this planning sheet. Use additional paper if necessary.

Channel: Channel model: ___MC ___DC

Channel protocol: ___TCP/IP ___SNA

If TCP/IP: Channel port: ____________

TCP/IP vendor: ___IBM ___CA

If CA:

Subsystem Name: ___Default ___Other:

If O is using the channel (either dedicated or shared with D):

Network Map: ___________ Node ID: ___________

If SNA: Channel APPLID: ________________ (MC only)

If O is using the channel (either dedicated or shared with D):

Network Map: ___________ Node ID: ___________

D. Software Requirements and Compatibility

To use Control-M Application Server (CTMAS), Control-M/Enterprise Manager must be from the same version and release, or later, as Control-M for z/OS. The version and release are indicated by the v.r.mm format (in earlier versions) or the v.v.rr.mmm format (in more recent versions) in the product description. In this numbering format, v is version, r is release, and m is maintenance level.

In case there is a need to work with an earlier release of Control-M/Enterprise Manager, such as during a testing period, the parameters MODECTM and MODEASM in IOAPARM member must be set to the version of the Control-M/Enterprise Manager. For example, if the Control-M/Enterprise Manager is in V8 and the IOA is in V9, the setting of MODECTM=800 and MODEASM=800 must be used. Setting the value would restrict the functionality of the Control-M for z/OS to the features and parameter values that were in effect in the specified version. See the section on the parameters MODECTM/MODEASM for more detailed explanation on the values and the accompanied restrictions.

Note that BMC does not recommend that this mode be used for a long period of time, but should be limited to only upgrading and testing periods.

If you have any questions, please contact BMC Customer Support.

Parent Topic

Customized installation