5486LPAD.fm Draft Document for Review October 18, 2004
678 IBM Eserver i5 and iSeries System Handbook
CICS Transaction Server for OS/390, or CICS Transaction Server for
VSE/ESA™ or predecessor systems) or TXSeries® (which contains CICS for
AIX, CICS for HP-UX, CICS for SUN Solaris, and CICS for Windows NT) are
source compatible with CICS for iSeries. Application support is available for
applications based on either single-byte or double-byte character sets.
Basic Mapping Support (BMS) for generating character-based user interfaces
BMS maps are source compatible, provided that they use BMS commands
from the CICS minimal function architecture subset. This level provides the
functions used by most CICS applications.
CICS transactional execution models
This includes conversational and non-conversational transactions,
asynchronous transactions, and transactions based on queues or timers.
The CICS VSAM interface for access to OS/400 database files.
The CICS VSAM API is mapped to standard OS/400 database files. Standard
OS/400 commands are used to create and manage these database files.
These files are also accessible from other OS/400 applications and queries.
CICS applications can also be created using Structured Query Language
(SQL) interfaces to access OS/400 database files.
OS/400 users share data and applications with other systems using CICS
Intersystem Communications
This allows connectivity to other CICS platforms and provides access to both
applications (transaction routing and distributed program link) and data
(function shipping) on the following systems:
– CICS Transaction Server on zSeries and S/390: This includes CICS
Transaction Server for z/OS, CICS Transaction Server for OS/390, and
CICS Transaction Server for VSE/ESA and predecessor systems.
– CICS Transaction Server for iSeries and CICS for AS/400
– CICS on open systems: This includes the TXSeries products (CICS for
AIX, CICS for HP-UX, CICS for Sun Solaris, and CICS for Windows NT).
– CICS for OS/2
Data integrity ensured through the use of OS/400 two-phase commit
capability
When a CICS for iSeries application updates multiple systems, it ensures
successful updates of all files and backs out partial updates if the full
transaction is not completed.
Connectivity from CICS Clients and from the CICS Transaction Gateway
This allows standard CICS applications to be used as either client/server
applications or as Web-serving applications. CICS for iSeries provides
To Next Page
Loading...
Need help?
General