Datasets:
Devilishcode
/
hacking

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.99k
The IPCF facility allows programs in a PRIME computer to exchange data with
programs in the same computer, another PRIME computer, or another vendor's
computer, assuming that that vendor supports X.25. This feature is the most
flexible and powerful one that any network software package can provide. It
basically allows an applications programmer to split up a program, so that
different pieces of the program execute on different machines a network. Each
program component can be located close to the resource (terminals, data,
special peripherals, etc.) it must handle, decode the various pieces and
exchange data as needed, using whatever message formats the application
designer deems appropriate. The programmer sees PRIMENET's IPCF as a series
of pipes through which data can flow. The mechanics of how the data flows are
invisible; it just "happens" when the appropriate services are requested. If
the two programs happen to end up on the same machine, the IPCF mechanism
still works. The IPCF offers the following advantages:
1) The User does not need to understand the detailed
mechanisms of communications software in order to
communicate.
2) Calls are device-independent. The same program will
work over physical links implemented by the local node
controller (local network), leased lines, or a packet
network.
3) Programs on one system can concurrently communicate
with programs on other systems using a single
communications controller. PRIMENET handles all
multiplexing of communications facilities.
4) A single program can establish multiple virtual
circuits to other programs in the network.
PRIMENET's ITS facility allows an interactive terminal to have access to
any machine in the network. This means that terminals can be connected into
an X.25 packet network along with PRIME computers. Terminal traffic between
two systems is multiplexed over the same physical facilities as inter-program
data, so no additional hardware is needed to share terminals between systems.
This feature is ordinarily invisible to user programs, which cannot
distinguish data entering via a packet network from data coming in over AMLC
lines. A variant of the IPCF facility allows users to include the terminal
handling protocol code in their own virtual space, thus enabling them to
control multiple terminals on the packet network within one program.
Terminals entering PRIMOS in this fashion do not pass through the usual log-in
facility, but are immediately connected to the application program they
request. (The application program provides whatever security checking is
required.)
The result is the most effective available means to provide multi-system
access to a single terminal, with much lower costs for data communications and
a network which is truly available to all users without the expense of
building a complicated private network of multiplexors and concentrators.
By utilizing PRIMENET's File Access Manager (FAM), programs running under
PRIMOS can access files on other PRIME systems using the same mechanisms used
to access local files. This feature allows users to move from a single-system
environment to a multiple-system one without difficulty. When a program and
the files it uses are separated into two (or more) systems the File Access
Management (FAM)is automatically called upon whenever the program attempts to
use the file. Remote file operations are logically transparent to the user
or program.
When a request to locate a file or directory cannot be satisfied locally,
the File Access Manager is invoked to find the data elsewhere in the network.
PRIMOS initiates a remote procedure call to the remote system and suspends the
user. This procedure call is received by an answering slave process on the
remote system, which performs the requested operation and returns data via
subroutine parameters. The slave process on the remote system is dedicated to
its calling master process (user) on the local system until released. A
master process (user) can have a slave process on each of several remote
systems simultaneously. This means that each user has a dedicated connection
for the duration of the remote access activity so many requests can be
handled in parallel.
FAM operation is independent of the specific network hardware connecting
the nodes. There is no need to rewrite programs or learn new commands when
moving to the network environment. Furthermore, the user need only be
logged-in to one system in the network, regardless of the location of the
file. Files on the local system or remote systems can be accessed dynamically
by file name within a program, using the language-specific open and close
statements. No external job control language statements are needed for the
program to access files. Inter-host file transfers and editing can be
performed using the same PRIMOS utilities within the local system by
referencing the remote files with their actual file names.
REMOTE JOB ENTRY
----------------
PRIME's Remote Job Entry (RJE) software enables a PRIME system to emulate
IBM, CDC, Univac, Honeywell and ICL remote job entry terminals over
synchronous communication lines. PRIME's RJE provides the same communications
and peripheral support as the RJE terminals they emulate, appearing to the
host processor to be those terminals. All PRIME RJE products provide three
unique benefits:
* PRIME RJE is designed to communicate with multiple
remote sites simultaneously.
* PRIME RJE enables any terminal connected to a PRIME system to
submit jobs for transmission to remote processors, eliminating the
requirement for dedicated terminals or RJE stations at each
location.