Teradata emulation – Brocade FICON Administrator’s Guide (Supporting Fabric OS v7.3.0) User Manual
Page 72
•
Optimized performance for FICON printers over distance when printers are extended through an
FCIP tunnel with FICON emulation.
•
Intermediate ending status as appropriate to prevent FlCON channel protocol timeout (PTOV)
expirations.
•
Acceptance of device status as required to prevent FICON control unit PTOV expirations.
•
Prevention of "clutching" during print jobs.
For information on configuring printer emulation, refer to
For information on displaying printer emulation status and statistics, refer to
emulation performance statistics
on page 73.
Teradata emulation
Teradata emulation reduces latency on links to Teradata Warehouse systems caused by WAN
propagation delays and bandwidth restrictions. It accomplishes this by processing selected FICON
commands for associated control, data, and status responses. FICON Teradata emulation is only
supported between FICON channels and FICON Teradata controllers.
For write commands, control and status frames are generated for the host side of the WAN in order to
pipeline write commands over the same or multiple exchanges. Such pipelined write commands and
their data are queued at the device side of the WAN for asynchronous transfer to the device.
For read operations received by the device side of the WAN, a number of anticipatory read commands
are autonomously generated and transferred to the device. The data and status associated with such
commands are sent to the host side of the WAN and queued in anticipation of host-generated read
commands.
FICON emulation for Teradata sequences over an FCIP tunnel is controlled by using FICON emulation
feature flags in the PortCfg fciptunnel command associated with the FCIP tunnel.
For information on configuring Teradata emulation or tape emulation, refer to
on page 72. For information on displaying Teradata emulation status and statistics, refer
Displaying FICON emulation performance statistics
FCIP configuration requirements for FICON extension
FICON extension uses FCIP for transport. FCIP interfaces and tunnels used for FICON extension
must be defined prior to configuring FICON emulation. Ports should remain persistently disabled until
after FICON emulation is configured. Refer to the Fabric OS FCIP Administrator's Guide for
information about configuring FCIP interfaces, tunnels, and circuits.
Configuration requirements for switches and backbones
Consider these configuration issues when an extension switch or blade is connected to a switch in a
FICON configuration:
•
If you are creating a cascaded configuration (connecting two switches or backbones with different
domain IDs), be aware of IBM requirements for high integrity fabrics.
•
In configurations with ISLs, ensure that ISL paths are properly configured to meet FICON
emulation requirements for a determinate path for FICON commands and responses.
Teradata emulation
70
FICON Administrator's Guide
53-1003144-01