18.08.2013 Views

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Product Interdependencies<br />

Installation <strong>and</strong><br />

Support Name<br />

Table B–2. Optional Product Interdependency Notes<br />

Interdependency Notes<br />

JB<strong>OS</strong>S-<strong>2200</strong> J2EE-CON-OPENDTP is required to integrate Open Distributed Transaction<br />

Processing applications with JBoss Java EE technology through a Java EE<br />

connector.<br />

J2EE-CON-<strong>OS</strong><strong>2200</strong> <strong>and</strong> CITA are required to connect JBoss applications to<br />

<strong>OS</strong> <strong>2200</strong> TIP <strong>and</strong> HVTIP programs.<br />

OLTP-TM<strong>2200</strong> is required to integrate Open Distributed Transaction Processing<br />

applications with JBoss Java EE technology or to ensure that your JBoss<br />

transactions are recoverable.<br />

RDMS <strong>and</strong> RDMS-JDBC are required to access Relational Database Server data<br />

from JBoss applications through RDMS-JDBC.<br />

DMS <strong>and</strong> DMS-RA are required to access Network Database Server data from<br />

JBoss applications through DMS-RA.<br />

Business Information Server <strong>and</strong> BIS-RA are required to access BIS data from<br />

JBoss applications through BIS-RA.<br />

JPJVM OLTP-TM<strong>2200</strong> is required to use the JPJVM in an OLTP environment.<br />

J2EE-CON-OPENDTP is required to integrate Open Distributed Transaction<br />

Processing applications with JBoss J2EE technology through a J2EE connector.<br />

RDMS <strong>and</strong> RDMS-JDBC are required to access Relational Database Server data<br />

from JBoss applications through RDMS-JDBC. DMS <strong>and</strong> DMS-RA are required<br />

to access Network Database Server data from JBoss applications through DMS<br />

RA. J2EE-CON-<strong>OS</strong><strong>2200</strong> <strong>and</strong> CITA are required to connect JBoss applications to<br />

<strong>OS</strong> <strong>2200</strong> TIP <strong>and</strong> HVTIP programs.<br />

JVM PADS is required if PADS debugging of native methods is desired, or if the<br />

debugging version of the Java launcher, javag, is used.<br />

OLTP-TM<strong>2200</strong> is required to use the JVM in an OLTP environment.<br />

J2EE-CON-OPENDTP is required to integrate Open Distributed Transaction<br />

Processing applications with JBoss J2EE technology through a J2EE connector.<br />

RDMS <strong>and</strong> RDMS-JDBC are required to access Relational Database Server data<br />

from JBoss applications through RDMS-JDBC. DMS <strong>and</strong> DMS-RA are required<br />

to access Network Database Server data from JBoss applications through<br />

DMS-RA. J2EE-CON-<strong>OS</strong><strong>2200</strong> <strong>and</strong> CITA are required to connect JBoss<br />

applications to <strong>OS</strong> <strong>2200</strong> TIP <strong>and</strong> HVTIP programs.<br />

LINK LSS is required if an object module is produced by a UCS compiler.<br />

CIFS is required to build or execute CIFSLD. If CIFS is not installed, CIFSLD will<br />

not be rebuilt.<br />

LSS Requires SFS if you want to have shared access to data files with locking <strong>and</strong><br />

recovery features.<br />

MQS<strong>2200</strong> COMAPI is required to use the MQ<strong>Series</strong> channels.<br />

OLTP-TM<strong>2200</strong> is required for participation in global transactions.<br />

BIS is required to use the basic mode interface (BMI). The basic mode interface<br />

enables BIS to access the Message Queuing Interface (MQI).<br />

MSMANAGER DPS is required to use the full screen interface.<br />

B–12 7831 0349–043

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!