beautypg.com

Pipe function -11, Using the pipe function in unix systems -11, Table 2-2) – HP XP20000XP24000 Disk Array User Manual

Page 29: Pipe function

background image

About Cross-OS File Exchange Operations

2-11

Hitachi USP V Cross-OS File Exchange User’s Guide

Table 2-2

User-Defined Code Conversion Table

Item Requirement(s)

Size 256

bytes

Format Binary

data

Code length One byte (two-byte codes cannot be converted)

File name

The following sequences of characters cannot be used in the file
name:

EA EcA EkJ No

If the file name for the code conversion table contains any of these
sequences, FCU will ignore the file and use the default table instead.

PIPE Function

This function transfers data entries from the mainframe to the application
program or the utility program for UNIX systems using a “named pipe”. When

this function is used, a mainframe dataset can be transferred to an open
system. This is a much faster way to transfer data than the Code Conversion
method.

A "named pipe" is a special file that is used to transfer data between unrelated
processes. One (or more) processes writes to it, while another process reads
from it. Named pipes are visible in the file system and may be viewed with ‘ls
like any other file. (Named pipes are also called "fifo"s; this term stands for

`First In, First Out'.) Named pipes may be used to pass data between
unrelated processes, while normal (unnamed) pipes can only connect
parent/child processes (with some exceptions). Named pipes are strictly

unidirectional, even on systems where anonymous pipes are bidirectional (full-
duplex).

Using the PIPE function in UNIX Systems

A "named pipe" is a special file that is used to transfer data between unrelated
processes. One (or more) processes write to it, while another process reads

from it. Named pipes are visible in the file system and may be viewed with `ls'
like any other file. (Named pipes are also called "fifo"s; this term stands for
`First In, First Out'.) Named pipes may be used to pass data between

unrelated processes, while normal (unnamed) pipes can only connect
parent/child processes (unless you try *very* hard). Named pipes are strictly
unidirectional, even on systems where anonymous pipes are bidirectional (full-

duplex).