Page 1¶

COSMOS TELNET/FTP¶

Client User Guide
ND-860284.1 EN

Norsk Data Logo

ND
Norsk Data

Page 2¶

I'm sorry, it seems the page is blank, so there is no content to convert to Markdown. If there's another page or issue, please let me know how I can assist further.

Page 3¶

COSMOS TELNET/FTP¶

Client User Guide¶

ND-860284.1 EN

Page 4¶

Documentation Notice¶

The information in this manual is subject to change without notice.
Norsk Data A.S assumes no responsibility for any errors that may appear in this manual, or for the use or reliability of its software on equipment that is not furnished or supported by Norsk Data A.S.

Contact Information¶

Send all documentation requests to:

Norsk Data A.S
Graphic Centre
P.O. Box 25 - Bogerud
N-0621 Oslo 6
NORWAY

Page 5¶

Preface:¶

THE PRODUCT¶

This User Guide describes the products:

Product	Code
COSMOS TELNET/FTP Client	ND-211154
COSMOS TCP/IP Gateway for Ethernet	ND-211185

TELNET (remote terminal access) and FTP (file transfer protocol) are the network applications on the top of the TCP/IP protocols. TCP/IP is two protocols (TCP a transport protocol and IP a network protocol) which are evolving into a de facto standard within the computer industry. Both protocols are commonly used on top of local area network controllers for ETHERNET.

THE READER¶

This manual should be read by anyone using the product COSMOS TCP/IP Gateway network utility programs (COSMOS FTP and COSMOS TELNET), to communicate with other vendors computers over ETHERNET.

PREREQUISITE KNOWLEDGE¶

A general knowledge of how to use SINTRAN III or User Environment and the operating system / applications at the target computer. Knowledge of the COSMOS file name syntax rules, and host target machine file name syntax is required.

THE MANUAL¶

Chapter 1 should be read by all user categories not familiar with the COSMOS TELNET/FTP concept.

Chapter 2 describes the user procedures of COSMOS FTP, chapter 3 describes the user procedures of COSMOS TELNET.

Chapter 4 should be read by the system operator. This chapter describes how to set up a host file.

Chapter 5 describes the general end-user messages.

Page 6¶

Appendices¶

Appendixes A (FTP) and B (TELNET) provide reference documentation on the different commands/functions available in each program.

Appendix C provides reference documentation on end-user error messages coming from COSMOS FTP.

Appendix D provides reference documentation on error messages (AIP, TCP and SLIB error messages) written to the error device. This appendix should be read by the system operator.

The following manuals supply additional information about products related to the COSMOS TELNET/FTP products.

Manual	Document Number
COSMOS User Guide	ND-860163
SINTRAN III User Guide	ND-860264
User Environment Reference Manual	ND-860194
COSMOS X.29 PAD User guide	ND-860192

Page 7¶

TABLE OF CONTENTS¶

Section	Page
1 INTRODUCTION	1
1.1 Synopsis	3
1.2 What is ARPANET	3
1.3 COSMOS TCP/IP ETHERNET Communication	4
1.4 COSMOS FTP - The File Transfer Utility Program	6
1.5 The COSMOS TELNET Utility Program	6

| 2 HOW TO USE THE COSMOS FTP CLIENT PROGRAM | 7 | | 2.1 Synopsis | 9 | | 2.2 FTP Syntax Rules | 9 | | 2.3 COSMOS Syntax Rules | 10 | | 2.4 How to Start the COSMOS FTP Client Program | 11 | | 2.5 The most Important COSMOS FTP Client Tasks | 13 | | 2.5.1 How to Set up and Clear a COSMOS FTP Client Connection | 14 | | 2.5.2 How to List Files and Directories | 16 | | 2.5.3 How to Use The PWD and CD Commands | 17 | | 2.5.4 How to Use the VERBOSE Command | 18 | | 2.5.5 How to Use The STATUS Command | 18 | | 2.6 How to Transfer Files | 19 | | 2.7 How to Transfer a File FROM a Remote Host | 20 | | 2.7.1 How to Receive Several files | 21 | | 2.8 How to Transfer a File TO a Remote Host | 21 | | 2.8.1 How to Send Several Files | 22 |

| 3 HOW TO USE THE COSMOS TELNET CLIENT PROGRAM | 23 | | 3.1 Synopsis | 25 | | 3.2 TELNET Syntax Rules | 25 | | 3.3 How to Start The COSMOS TELNET Client Program | 25 | | 3.4 How to List The COSMOS TELNET Client Commands | 26 | | 3.5 How to Set Up and Clear a COSMOS TELNET Client Connection | 27 | | 3.6 How to Use The ESCAPE Command | 29 | | 3.7 How to Use The STATUS Command | 30 |

Page 8¶

Section¶

Section	Page
3.8	How to Use The CRMOD Command
4	HOW TO EDIT THE AIP-HOSTS:SYMB FILE (For the Operator)
4.1	Description
4.2	Assignment of Network Addresses
4.3	The Host File
5	END-USER MESSAGES
5.1	General Information of End-user Messages
5.2	Reply Codes

APPENDIX¶

Appendix	Page
A	THE COSMOS FTP CLIENT COMMANDS
B	The COSMOS TELNET Commands
C	END-USER ERROR MESSAGES
D	OPERATOR ERROR MESSAGES

Index 1

Page 9¶

Chapter 1¶

Introduction¶

Page 10¶

I'm sorry, I can't read the text in the image. If you could provide a clearer version or type out the content, I'd be happy to help with the conversion to Markdown.

Page 11¶

INTRODUCTION¶

1 INTRODUCTION¶

1.1 Synopsis¶

This chapter gives a brief introduction to ARPANET, and the TCP/IP (Transmission Control Protocol)/(Internet Protocol) class of products, FTP and TELNET. The COSMOS TCP/IP Gateway software package includes two network application utilities:

File Transfer Utility (COSMOS FTP) (File transfer between machines on the network)

Virtual Terminal Utility (COSMOS TELNET) (Terminal emulation)

1.2 What is ARPANET¶

ARPANET (Advanced Research Projects Agency NETwork) is a network used by the American defense organizations throughout the American continent. The project began in about 1975 and today it connects several defense institutions all over America.

A public version of ARPANET is used by universities and research institutions, in the USA as well as in Europe.

The architecture is used in both Local Area Networks (LAN's) and in Wide Area Networks (WAN's). The ARPANET model, and the protocols used, were defined before the ISO model became a standard, it has therefore been used as a de facto standard in local area networks.

Because ARPANET has been used as a de facto standard, ND has developed its own version for communication using the ARPANET architecture and protocols. This will allow ARPANET compatibility over ETHERNET as the common network.

Page 12¶

INTRODUCTION¶

ARPANET defines the standard Internet protocols:

IP (Internet Protocol) (the network-related protocol)
ICMP (Internet Control Message Protocol) (a protocol implemented in IP)
TCP (Transmission Control Protocol) (a connection-oriented protocol)
UDP (User Datagram Protocol) (which is the same logical level as TCP)

The two protocols, TCP (Transmission Control Protocol), and IP (Internet Protocol), are protocols that originally were specified for ARPANET by the US ARPA (Advanced Research Projects Agency). In terms of the ISO Open System Interconnection (OSI) model, TCP is a layer 4 transport protocol and IP is a layer 3 network protocol. This is illustrated in the figure below:


FTP	TELNET	Application layer
TCP		Transport layer
IP		Network layer
ETHERNET DIX 2.0		Physical layer

Example 1. The figure shows the layers in terms of the OSI model

1.3 COSMOS TCP/IP ETHERNET Communication¶

An increasing number of computer manufacturers are now considering the TCP/IP - ETHERNET set of datacommunication protocols as de facto industry standards for local area communication. ND's implementation is based on Berkley's 4.2 BSD UNIX standard.

Page 13¶

Introduction¶

On top of the TCP/IP protocols are the network application utilities TELNET, allowing remote terminal access, and FTP, allowing file transfer. The TELNET utility program, acronym for TELetype NETwork, was also specified for the ARPANET. It allows users on one host computer to connect to the timesharing resources of another host. The TELNET protocol specifies a standard terminal type, the so-called Network Virtual Terminal (NVT).

The FTP utility program uses the ARPA Internet standard File Transfer Protocol (FTP) to transfer files between any hosts connected to the ETHERNET network.

Norsk Data has defined ETHERNET to be the LAN for ND computers. It is clear that the TCP/IP class of products, listed below, will open up this environment so that both ND and non-ND computers can communicate within the same ETHERNET network. The products that ND supports are:

COSMOS TCP/IP Gateway for Ethernet, including the COSMOS TELNET/FTP Server software.
COSMOS TELNET/FTP Clients

The TCP software is implemented in ND-100 and the IP software is implemented in a separate controller. The COSMOS TCP/IP software runs under SINTRAN III/VSX. The COSMOS TELNET/FTP Server software, which is included in the gateway software, runs in the ND-100 part of the machine. COSMOS TELNET provides remote terminal access, and the file transfer protocol COSMOS FTP allows for file transfer.

Page 14¶

Introduction¶

The product will allow communication with other vendors computers. Digital Equipment Corp.(DEC), Honeywell Bull, Data General, Sun, Apollo, Gould, Siemens, Hewlett Packard and Unisys are among vendors for which TCP/IP is available.

NOTE!¶

Be aware of that TCP/IP is not standardized. Several different implementations of TCP/IP exists. Norsk Data's implementations is derived from the BBN (Bolt, Beranek & Newman) version of TCP/IP. This version will work with most implementations of the BSD 4.2 UNIX version.

Also NOTE that an ND host cannot be an IP (Internet) gateway, a feature that is standard in the BSD 4.2 version.

Standard protocols, including TCP/IP, FTP and TELNET are presently available on Norsk Data computers under NDIX, which is ND's implementation of the Berkeley 4.2 BSD UNIX system for ND-500 computers.

1.4 COSMOS FTP – The File Transfer Utility Program¶

The COSMOS FTP utility uses the ARPA Internet standard File Transfer Protocol(FTP) to transfer files between a local machine - your local computer - and a remote host on the Internet network.

In addition, COSMOS FTP allows you to access directories/files on a remote host and to perform common operations, such as list and change working directories, list files at various levels, and rename directories and files (in a UNIX Operating System).

1.5 The COSMOS TELNET Utility Program¶

COSMOS TELNET is a virtual terminal protocol on the ARPANET network. It uses the TELNET protocol and provides remote login capability to any machine implementing this protocol. The COSMOS TELNET Client program is an application program started from any terminal. Both the COSMOS FTP(File Transfer Protocol) and the COSMOS TELNET(TELtype NETwork) use the TCP(Transmission Control Protocol).

Page 15¶

Chapter 2¶

How to Use the Cosmos FTP Client Program¶

Page 16¶

I'm unable to extract text from the provided image. Please provide a better quality image or describe the content you need in text form.

Page 17¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2 HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2.1 Synopsis¶

This chapter gives the end-user the information necessary to use the COSMOS FTP Client program from an ND computer.

In the examples in this manual, we have assumed that the remote host runs UNIX. If your remote host does not run UNIX, your output may look different from the output shown in the examples.

First we will have a look at the syntax rules.

2.2 FTP Syntax Rules¶

Commands in the COSMOS FTP Client program may be abbreviated, as long as the command name given is not ambiguous. String parameter values can also be abbreviated in the same way.

Parameter validation takes place after all the parameters have been given. This means that if you give one wrong parameter value, you will have to write the command, with all its parameter values all over again, to correct the wrong parameter value.

There is a difference between SINTRAN III and UNIX in naming of files.

SINTRAN III - filename:type
UNIX - filename(pathname).xyz

NOTE¶

SINTRAN III will not accept other than the above mentioned way of naming files. Therefore you must always specify the "local file" when you transfer files between another operating system and SINTRAN III with the PUT or GET commands. Some UNIX systems will accept both ways of naming files.

Page 18¶

2.3 COSMOS Syntax Rules¶

This section describes the COSMOS remote file access syntax. See the COSMOS User Guide for a complete description of the remote file access in SINTRAN III.

The COSMOS file access syntax is as follows:

SYSTEM(REMOTE-USER(PASSWORD)).(DIR:USER)FILE-NAME:TYPE


This tells COSMOS which system the file is on and whose access rights are being used.	This tells SINTRAN which file to access.

COSMOS file access may prove useful if you want to access (transfer) files over a COSMOS network, i.e. accessing an ND machine different from the COSMOS TCP/IP Gateway.

The example below shows how the COSMOS file syntax is used in the COSMOS FTP Client. We assume that you already have opened a connection to one ND machine, and want to transfer a file to your local machine from another ND machine. (A complete explanation of the OPEN and GET command is described later in this chapter).

Command	Example
Ftp> get ↲	remote-file: BYRON(SUE(OOF)).(PACK-ONE:SUE)INFO:OUT ↲
	local-file: information ↲
Ftp>

Example 2. COSMOS File Syntax used in FTP Client.

Page 19¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2.4 How to Start the COSMOS FTP Client Program¶

You may start the COSMOS FTP Client program from User Environment, by choosing the COSMOS FTP Client from the User Environment menu. If User Environment is not installed, see next page.

User Environment
System: MAIN
Supervisor Menu
1. SINTRAN III
2. Notis-WP
3. COSMOS FTP-Client
4. Program Editor
User: PEDER AAS
Work area: FLOPPY-USER
Task:
12.04
1987-05-13

Example 3. How to Start the COSMOS FTP Client Program from User Environment

You should note that the example above only illustrates how the menu, and the COSMOS FTP Client menu option, may look.

Page 20¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

If User Environment is not installed, or you are not using the User Environment menu system, you can start the COSMOS FTP Client directly from SINTRAN III.

@ftp-client ↵
-------- FTP client ND-211154AO
Ftp>

Example 4. How to Start the COSMOS FTP Client from SINTRAN III¶

To list all the commands available in the COSMOS FTP Client program you type the HELP or ? commands followed by ↵. On the following pages the most important commands available in the COSMOS FTP Client program are described.

Page 21¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2.5 The most Important COSMOS FTP Client Tasks¶

The commands we are going to introduce in this chapter are listed in the table below.


HELP	GET
?	MGET
OPEN	HASH
CLOSE	RECV
QUIT	PUT
BYE	SEND
LS	MPUT
DIR	APPEND
PWD
CD
VERBOSE
STATUS
ASCII
BINARY

Table 1. The most Important COSMOS FTP Client Commands

Before you start to use these commands, you must establish a connection to a remote host. On the next page you will find an example on how to set up a connection to a remote host.

Page 22¶

2.5.1 How to Set up and Clear a COSMOS FTP Client Connection¶

To set up a connection to a remote host, you may use the OPEN command after the COSMOS FTP Client program has been started. The AIP-HOSTS:SYMB file contains a list of hosts that you might connect to.

NOTE !
Host names should be written in either lower-case or upper-case letters dependent on how they are written in the AIP-HOSTS:SYMB file.
To find out which hosts you may connect to, you must read the AIP-HOSTS:SYMB file into an editor (e.g. NOTIS-WP) before you start the COSMOS FTP Client program.
( Fetch Document: (SYSTEM)AIP-HOSTS:SYMB )

@Ftp-Client↵

-------- FTP client ND-211154AO

Ftp> open dickens ↵
Connected to dickens.
220 dickens FTP server
(Version 4.4 Sat Jan 18 04:25:35 PST 1986) ready.
Username on dickens: user-name ↵
331 Password required for user-name.
password: password ↵
230 User user-name logged in.
Ftp>

Example 5. How to Set up a COSMOS FTP Client Connection

Some numbers followed by a message are displayed in the COSMOS FTP Client examples, like in the example above; '220 dickens FTP server'. Those numbers are called 'reply codes' and are explained in chapter 5; 'END-USER MESSAGES' in this manual.

On the next page, we will have a look at how to clear a connection. We will have a look at how you exit the COSMOS FTP Client program as well.

Page 23¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

If you want to clear a connection with a remote host you use the CLOSE command (the CLOSE command leaves you in the COSMOS FTP Client command interpreter). After having done that you may set up another connection to a new remote host by using the OPEN command again. Or you might exit the COSMOS FTP Client program by using the QUIT or BYE commands.

Ftp>close ↵
Ftp>quit ↵
221 Goodbye.
@

Example 6. How to Clear a COSMOS FTP Client Connection

Both the QUIT and the BYE commands exit the COSMOS FTP Client program.

NOTE !
The QUIT or BYE commands will clear any connection to a remote host before you leave the COSMOS FTP Client program.

Page 24¶

2.5.2 How to List Files and Directories¶

Simply type LS for a listing of your files or DIR to display the contents of your directory as shown in the example below.

Ftp> ls ↵
200 PORT command okay.
150 Opening data connection for /bin/ls (128.39.3.6,1046) (0 bytes).
test-1
test-1.s
test-2-s
test-3.t
226 Transfer complete.
73 bytes received.

Ftp> dir ↵
200 PORT command okay.
150 Opening data connection for /bin/ls (128.39.3.6,1047) (0 bytes), total 22
-rw-r--r-- 1 user-name wheel 2 May 15 1987 test-1
-rw-rw-rw- 1 user-name wheel 6803 May 15 1987 test-1.s
-rw-rw-rw- 1 user-name wheel 6803 Feb 7 13:01 test-2-s
-rw-rw-rw- 1 user-name wheel 6803 Feb 7 12:55 test-3.t
226 Transfer complete.
515 bytes received.

Example 7. How to List Files and Directories

If your remote operating system is UNIX you might find out whether the contents is files or directories by typing:

ls -l ↵

This listing will display a d in front of a directory, and a - in front of a file.

Page 25¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

The LS and DIR commands have two parameters:

<remote-directory> If you do not specify any directory the contents on your current remote directory will be listed.
<local-file> If you do not specify any local file the output will be sent to your terminal.

2.5.3 How to Use The PWD and CD Commands¶

The PWD command lists the name of the directory you are working on. If you want to change your current working directory you use the CD command. This is shown in the example below.

Ftp> pwd ↵
251 "/usr.MC68020/tom" is current directory.
Ftp> cd ↵
remote-directory: test-1 ↵
200 CWD command okay.
Ftp> pwd ↵
251 "/usr.MC68020/tom/test-1" is current directory.
Ftp>

Example 8. The PWD and CD Commands

As shown in the example above the PWD command lists both your new 'current' directory and the previous directory. If you are working on a UNIX operating system you may go back to the previous directory by typing:

cd .. ↵

This performs an 'undo' of the last directory change.

Page 26¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2.5.4 How to Use the VERBOSE Command¶

The VERBOSE command turns verbose mode on or off. Verbose mode on is the default, and it will give you a listing as shown in the example on the previous page when you use the LS and DIR commands. The information displayed, except from the files and the contents of the remote directory, is the responses from the remote COSMOS FTP server.

Verbose mode on will also give you information about the efficiency of a completed file transfer.

However, this listing might be a bit difficult to read when it contains this much information. To make them easier to read you might turn verbose mode off. This will reduce the amount of information listed. To do that, type VERBOSE ↵, and the mode will be automatically changed.

2.5.5 How to Use The STATUS Command¶

In the example below there is a listing of the different default status values in the COSMOS FTP Client program.

Ftp>	status ↵
	Connected to dickens
	Mode : STREAM; Type: ASCII; Format : NON-PRINT;
	Structure: FILE
	Verbose: ON; Bell: OFF; Prompting: ON;
	Hash mark printing: OFF; Use of PORT cmds: ON
	File-name ON/OFF
	Ftp>

Example 9. The Default Status Values

You change those values in the same way as we did above with the VERBOSE command. You type the wanted 'COMMAND' ↵ and the value is changed automatically.

Page 27¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2.6 How to Transfer Files¶

Before you start on a file transfer, find out whether the file is a ASCII file or a BINARY file. It is important that you assign the right file transfer mode to the file, or the file will not be readable after the transfer.

Use ASCII mode on (ASCII ON is default) before you transfer text files.

Turn on BINARY mode (by using the BINARY command) before you transfer binary files (e.g. :prog and :bpun files)

WARNING !

If you are transferring files to an ND machine, remember that file names on SINTRAN III may be abbreviated, i.e. an existing file named abc will be overwritten if you specify file named a, and a is an unambiguous abbreviation of that file.

It is not possible to transfer files with holes, in this version of the COSMOS TELNET/FTP Client. (e.g. 2-bank program files) In this version only STREAM mode is implemented.

Page 28¶

How to Use the COSMOS FTP Client Program¶

2.7 How to Transfer a File FROM a Remote Host¶

The example below shows what a file transfer might look like. In this example we have used the GET command to transfer one file from the remote host to the local machine.

The RECV command is a synonym for the GET command. This command may be used in the same way as the GET command.

Ftp> hash
Hash mark printing ON (1024 bytes/hash mark).

Ftp> get
remote-file: test-1.s
local-file: test-4:symb
200 PORT command okay.
150 Opening data connection for test-1.s (128.39.3.6,1026) (6803 bytes).
######
226 Transfer complete.
6902 bytes received.
Ftp>

Example 10. The GET Command

In the example above we have used the HASH command to turn a progress report mode ON before we started the file transfer. The mode prints out the # sign during the file transfer. This gives you a chance to see progress reports of the file transfer.

Page 29¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2.7.1 How to Receive Several Files¶

It is also possible to transfer several files from the remote host to the local machine.

If you transfer files from a machine that runs UNIX, you may turn the CONVERT-FILENAME command ON before you use the MGET command.
The MGET command will transfer the files that you specify.

The CONVERT-FILENAME command will convert the UNIX file-name to the corresponding SINTRAN III way of naming files. (e.g. a file from a UNIX host, filename{pathname}.xyz, will be converted to filename:type)

2.8 How to Transfer a File TO a Remote Host¶

In the example below we have used the PUT command to transfer one file from your local machine to the remote host.

The SEND command is a synonym for the PUT command and may be used in the same way.

Command Prompt	Output
Ftp> hash ↵	Hash mark printing ON (1024 bytes/hash mark).
Ftp> put ↵	local-file: test-4:symb remote-file: test-2-s 200 PORT command okay. 150 Opening data connection for test-2-s(128.39.3.6,1034). ####### 226 Transfer complete. 6902 bytes SENT. Ftp>

Example 11. The PUT Command

As mentioned in the example on the previous page we have also here used the HASH command to print out a hash sign # to keep track of the file transfer.

Page 30¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

The APPEND command also sends a local file to a remote host. It adds the <local-file> you are specifying to a file on the remote host you are connected to.

2.8.1 How to Send Several Files¶

It is also possible to transfer several files to the remote host from the local machine.

If you transfer files from a machine that runs UNIX, you may turn the CONVERT-FILENAME command ON before you use the MPUT command.

The MPUT command will transfer the files that you specify.

The CONVERT-FILENAME command will convert the SINTRAN filenames to match the UNIX way of naming files. (e.g. filename;type will be converted to filename(pathname).xyz on a host that runs UNIX)

Page 31¶

Chapter 3¶

How to Use the Cosmos Telnet Client Program¶

Page 32¶

I'm sorry, I can't extract any text from this image.

Page 33¶

HOW TO USE THE COSMOS TELNET CLIENT PROGRAM¶

3 HOW TO USE THE COSMOS TELNET CLIENT PROGRAM¶

3.1 Synopsis¶

This chapter gives the end-user the information necessary to use the COSMOS TELNET Client program from an ND computer.

3.2 TELNET Syntax Rules¶

The syntax rules concerning the COSMOS TELNET Client program is the same as for the COSMOS FTP Client program. To read more about the syntax rules, you should have a look at section 2.2 "FTP Syntax Rules" on page 9.

3.3 How to Start The COSMOS TELNET Client Program¶

You start the COSMOS TELNET Client program either from the User Environment menu or directly from SINTRAN III. The example below illustrates how you start the COSMOS TELNET Client program from SINTRAN III.

@telnet-client ↵
-------- TELNET client ND-211154AO
Telnet>

Example 12. How to Start the COSMOS TELNET Client Program

Page 34¶

HOW TO USE THE COSMOS TELNET CLIENT PROGRAM¶

3.4 How to List The COSMOS TELNET Client Commands¶

To list the commands available in the COSMOS TELNET Client program you use either the HELP command or you may just type ? (question mark) followed by ↵, as shown in the example below.

Telnet> ? ↵

OPEN  
CLOSE  
EXIT  
QUIT  
ESCAPE  
STATUS  
OPTIONS  
CRMOD  
HELP  
?  

Telnet>

Example 13. The COSMOS TELNET Client Commands

On the following pages the commands available in the COSMOS TELNET Client program are described.

Page 35¶

HOW TO USE THE COSMOS TELNET CLIENT PROGRAM¶

3.5 How to Set Up and Clear a COSMOS TELNET Client Connection¶

To set up a connection to a remote host, you may use the OPEN command after the COSMOS TELNET Client program has been started.

@telnet-client
-------- TELNET Client ND-211154AO

Telnet> open dickens
Trying.....
Connected to dickens
Escape character is "CTRL + @"

4.2 BSD UNIX (dickens)

login:tom
Last login: day month date 09:58:50 from local machine
SUN UNIX 4.2 Release 3.0(GENERIC) #1: Wed Jan 29 16:51:28 PST 1986
dickens%

Example 14. How to Set up a COSMOS TELNET Client Connection

On the next page it is explained how you clear a connection and how you exit the COSMOS TELNET Client program as well.

Page 36¶

How to Use the COSMOS TELNET Client Program¶

If you want to clear a connection with a remote host do as follows:

Type the escape character to get back to the COSMOS TELNET Client command mode. The default escape character is CTRL + @ (see the example on the previous page).

Type the CLOSE command and the connection is cleared.

You may now set up another connection to a new remote host by using the OPEN command again. Or you might exit the COSMOS TELNET Client program by using either the QUIT or the EXIT command.

Telnet>	close
	connection is closed.
Telnet>	quit
	@

Example 15. How to Clear a COSMOS TELNET Client Connection

The QUIT and the EXIT commands both exit the COSMOS TELNET Client program.

NOTE !

The EXIT and the QUIT commands will also clear any connection to a remote host before they leave the COSMOS TELNET Client program.

Page 37¶

HOW TO USE THE COSMOS TELNET CLIENT PROGRAM¶

3.6 How to Use The ESCAPE Command¶

When you have established a connection to a remote host you use the escape character to get back to the COSMOS TELNET Client command mode.

You may use the ESCAPE command to list the escape character, or you may use it to give the escape character a new "value".

After you have executed a command in the COSMOS TELNET Client command mode, you must type CR (carriage return) twice to get back to the remote host. (This is shown in the example below)

dickens% CTRL + @ ↵
Telnet> escape ↵
new escape character: Q ↵
Escape character is "CTRL + Q" ↵

dickens%

Example 16. The ESCAPE Command

When you are in the COSMOS TELNET command mode while you are connected to a remote host, the COSMOS TELNET Client program will automatically set you back to the remote host after you have used one of the COSMOS TELNET Client commands.

Page 38¶

HOW TO USE THE COSMOS TELNET CLIENT PROGRAM¶

3.7 How to Use The STATUS Command¶

The illustration below shows an example of what the STATUS command in the COSMOS TELNET client program looks like.

dickens% CTRL + Q ↵
Telnet> status ↵
Connected to dickens.
Escape character is "CTRL + Q".
↵
dickens%

Example 17. The STATUS Command

3.8 How to Use The CRMOD Command¶

The CRMOD command turns the carriage return mode on or off. If you turn the CRMOD command on and you for example list files on the remote host, the files will be listed in double spacing.

dickens% CTRL + Q ↵
Telnet> crmod ↵
Will map carriage return on output ↵
dickens% ls
test-1.s
test-2
dickens%

Example 18. The CRMOD Command

Page 39¶

Chapter 4¶

How to Edit the AIP-HOSTS:SYMB File (For the Operator)¶

Page 40¶

I'm sorry, I can't process the content of the image. Could you please provide a clearer version or describe the content?

Page 41¶

HOW TO EDIT THE AIP-HOSTS:SYMB FILE (For the Operator)¶

4 HOW TO EDIT THE AIP-HOSTS:SYMB FILE (FOR THE OPERATOR)¶

This chapter should be read by the system operator. Later, when the COSMOS TCP/IP Operator Guide becomes available, this will be covered there.

4.1 Description¶

The aip-hosts file contains information regarding the known hosts on the local Internet network. For each host a single line should be present with the following information:

Internet address
Official host name
Alias host names

The official host name should be unique on the local network. A host may have a number of alias host names, which need not be unique. Items are separated by any number of blanks and/or tab characters. A "#" indicates the beginning of a comment; characters up to the end of line are not interpreted by routines which search the file.

Network addresses are specified in the conventional "." notation. Host names may contain any printable character other than field delimiter, new line or comment character. This is illustrated in the example below:

| 128.39.1.2 | nd-hqrd-chaucer chaucer |

4.2 Assignment of Network Addresses¶

If you are connected to ARPANET, you must use the addresses assigned to you by ARPANET administration. If you are NOT connected to ARPANET, you are free to choose your own network addresses.

Page 42¶

HOW TO EDIT THE AIP-HOSTS:SYMB FILE (For the Operator)¶

4.3 The Host File¶

The host file is created by using a text editor with a 7-bit storage format (e.g. PED). In this file, AIP-HOSTS:SYMB, the operator specifies the hosts that the users should be able to set up a connection to. The AIP-HOSTS:SYMB file is a plain text file and must exist on user (SYSTEM). A default AIP-HOSTS:SYMB file will be copied to user (SYSTEM) with public access read by the installation program.

The host file should be placed on user system like this:

(SYSTEM)AIP-HOSTS:SYMB

The file must be given Public Read Access so that the users can look at the hosts they might establish a connection to in an editor. The following example illustrates what the host file might look like:

INTERNET-ADDRESS	OFFICIAL-HOST	ALIAS
#
#
128.39.3.6	nd-hqrd-byron	byron
128.39.3.20	dickens	dickens
128.39.3.2	nd-hqrd-steinbeck	steinbeck
128.39.3.3	nd-hqrd-milton	milton
128.39.3.4	nd-hqrd-chaucer	chaucer
128.39.3.5	nd-hqrd-bronte	bronte localhost
128.39.3.7	nd-hqrd-shelley	shelley
128.39.3.8	ericsson
128.39.3.10	ndix-isabelle	isabelle
128.39.3.21	si-sun	marvell
128.39.3.22	tools-spenser	spenser
128.39.3.23	opsys-ausren	ausren
128.39.3.30	si-f	f
128.39.3.50	hw-whitman	whitman
128.39.3.51	nd-hqrd-shakespeare	shakespeare
#
#

Example 19. Example of The Aip-Host:Symb File

Page 43¶

Page 44¶

I'm sorry, I can't convert the content from the image.

Page 45¶

END-USER MESSAGES¶

5 END-USER MESSAGES¶

This chapter describes the reply codes for the messages that may be written to the screen while you are using the COSMOS FTP Client program. See Appendix C for a listing of the end-user error messages.

5.1 General Information of End-user Messages¶

In this section we have described the number codes for the error-messages and other messages that might be written on your screen. There are five values for the first digit of the reply code:

1yz Positive preliminary reply

"1" as the first digit in the reply code means that the requested action is being started. You must expect another reply before you give another command. This reply also indicates that the command you gave was accepted. The FTP process may send at most one 1yz reply per command.

2yz Positive completion reply

"2" as the first digit in the reply code means that the requested action (your command) has been successfully completed, and you may continue with a new command.

3yz Positive intermediate reply

"3" as the first digit in the reply code means that your command has been accepted, but the requested action is being held in abeyance, waiting for more information. You should send another command specifying this information. This reply is used in command sequence groups.

4yz Transient negative completion reply

"4" as the first digit in the reply code means that your command was not accepted, and the requested action did not take place. The error condition is temporary and the action may be requested again. You should turn to the beginning of your command sequence, if any, and try again.

Page 46¶

5yz Permanent Negative Completion Reply¶

"5" as the first digit in the reply code means that your command was not accepted and the requested action did not take place.

5.2 Reply Codes¶

This section gives a listing of the reply codes. The numbering system for those codes are described in the previous section.

Code	Description
110	Restart marker reply.
120	Service ready in nnn minutes.
125	Data connection already opened; transfer starting.
150	File status okay; about to open data connection.
200	Command okay.
202	Command not implemented, superfluous at this site.
211	System status, or system help reply.
212	Directory status.
213	File status.
214	Help message; on how to use the server or the meaning of a particular non-standard command.
215	NAME system type; where NAME is an official system name.
220	Service ready for new user.
221	Service closing control connection. Logged out if appropriate.
225	Data connection open; no transfer in progress.
226	Closing data connection. Requested file action successful (for example, file transfer or file abort).

Page 47¶

End-User Messages¶

Code	Message
227	Entering passive mode.
230	User logged in, proceed.
250	Requested file action okay, completed.
257	"PATHNAME" created.
331	User name is okay, but you need password.
332	Need account to be able to login.
350	Requested file action pending further information.
421	Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down.
425	Cannot open data connection.

Note:

When you use PUT or GET to transfer a file you may get the error message: 425 CAN'T CREATE DATA SOCKET ON SLIB WHEN RUNNING 4 COSMOS FTP CLIENTS TOWARDS THE SERVER.

If this error appears you should just wait for about 30 seconds and try to transfer the file once more.

Code	Message
426	Connection closed; transfer aborted.
450	Requested file action not taken. File unavailable (e.g. file busy).
451	Requested action aborted: Local error in processing.
452	Requested action not taken. Insufficient storage in system.
500	Syntax error, command unrecognized. This may include errors such as command line too long.
501	Syntax error in parameters or arguments.
502	Command not implemented.

Page 48¶

End-User Messages¶

Code	Message
503	Bad sequence of commands.
504	Command not implemented for that parameter.
530	Not logged in.
532	Need account for storing files.
550	Requested action not taken. File unavailable (e.g. file not found, no access).
551	Requested action aborted: page type unknown.
552	Requested file action aborted. Exceeded storage allocation (for current directory or dataset).
553	Requested action not taken. Filename not allowed.

Page 49¶

Appendix A¶

The Cosmos FTP Client Commands¶

Page 50¶

I'm unable to extract any text from this scanned page as it appears to be heavily distorted or blank. If there's a specific area or clearer section you'd like assistance with, please let me know.

Page 51¶

THE COSMOS FTP CLIENT COMMANDS¶

Command name	APPEND
No:	Parameter Name:
1	`<Local-File>`
2	`<Remote-File>`

Rules: Available to all users. The OPEN command must have been executed successfully prior to giving the APPEND command.

Related Commands: OPEN, SEND, PUT

Function: The APPEND command appends a local file to a file on the remote host. If <Remote-File> is left unspecified, the local file name is used in naming the file on the remote host. File transfer uses current settings for TYPE, FORMAT, MODE, and STRUCT.

NOTE: If you are transferring files to an ND machine, remember that files on SINTRAN III may be shortened, i.e. an existing file named 'abc' will be overwritten if you specify a file named only 'a'.

Page 52¶

The Cosmos FTP Client Commands¶

Command Name: ASCII¶

No	Parameter Name	Default Value
1	`<NO PARAMETERS>`

Rules: Available to all users.

Related Commands: BINARY, TYPE, STATUS

Function: The ASCII command sets the file transfer type to network ASCII which is the default. Use ASCII mode to transfer text files.

Command Name: BELL¶

No	Parameter Name	Default Value
1	`<NO PARAMETERS>`

Rules: Available to all users.

Related Commands: MGET, MPUT, STATUS

Function: The BELL command turns a bell on or off, and it causes a bell to be sounded after each file transfer command is completed. By default BELL is set to OFF.

Page 53¶

THE COSMOS FTP CLIENT COMMANDS¶

Command: BINARY¶

No:	Parameter Name:	Default Value:
1	`<NO PARAMETERS>`

Rules: Available to all users.

Related Commands: ASCII, TYPE, STATUS

Function: The BINARY command sets the file transfer type to support binary image transfer. You use BINARY mode when you transfer binary files.

Note: It is impossible to transfer files with holes.

Command: BYE¶

No:	Parameter Name:	Default Value:
1	`<NO PARAMETERS>`

Rules: Available to all users.

Related Commands: QUIT

Function: The BYE command terminates the FTP session with the remote server, and exits FTP command mode. The QUIT command does the same thing.

Page 54¶

THE COSMOS FTP CLIENT COMMANDS¶

Command name : CD¶

No	Parameter Name	Default Value
1	`<Remote-Directory>`

Rules: Available to all users. The OPEN command must have been executed successfully prior to giving the CD command.

Related Commands: OPEN, PWD, LS

Function: The CD command changes the current working directory on the remote host to <Remote-Directory>. It is only possible to change the directory if the remote host runs an operating system supporting this feature (e.g. UNIX).

NOTE: Remember that directory does not mean the same to SINTRAN III as it does to the other operating systems that support this feature. The CD command is therefore not supported on a machine that runs SINTRAN III.

Page 55¶

THE COSMOS FTP CLIENT COMMANDS¶

Command Name: CLOSE¶

No:	Parameter Name:	Default Value:
1	`<NO PARAMETERS>`

Rules: Available to all users. The OPEN command must have been executed successfully prior to giving the CLOSE command.

Related Commands: OPEN, BYE, QUIT

Function: The CLOSE command terminates the FTP session with the remote server but remains in the FTP command mode.

Command Name: CONVERT-FILENAME¶

No:	Parameter Name:	Default Value:
1	`<NO PARAMETERS>`

Rules: Available to all users.

Related Commands: MGET, MPUT

Function: The CONVERT-FILENAME command turns conversion of filenames ON or OFF. It converts '.' to ':' or the other way around. This is of interest if you are transferring files between ND machines and machines that run UNIX. (e.g. Norsk Data uses filename:type and UNIX filename(pathname).xyz) See chap 2, page 21 and 22.

Page 56¶

THE COSMOS FTP CLIENT COMMANDS¶

DEBUG¶

No:	Parameter Name:	Default Value:
1	`<Debug-Level>`	off

Rules:
Only for advanced users.

Function:
The DEBUG command turns debugging mode on or off. If an optional <Debug-Level> is specified it is used to set the debugging level. When debugging is on, FTP prints each command sent to the remote host, preceded by the string "-->".

DELETE¶

No:	Parameter Name:	Default Value:
1	`<Remote-File>`

Rules:
Available to all users. The OPEN command must have been executed successfully prior to giving the DELETE command.

Related Commands:
OPEN, LS, MDELETE

Function:
The DELETE command deletes a specified <Remote-File> on the remote host, with appropriate access. The file access can only be set locally on the remote host. (You might set the file access via TELNET)

Page 57¶

THE COSMOS FTP CLIENT COMMANDS¶

Command name: DIR¶

No:	Parameter Name:	Default Value:
1		current directory
2		terminal

Rules: Available to all users. The OPEN command must have been executed successfully prior to giving the DIR command.

Related Commands: OPEN, LS, PWD, CD

Function: The DIR command prints a listing of the directory contents in the directory, , and optionally, placing the output in . If no directory is specified, the current working directory on the remote host is used. If no local file is specified, or is "-", output comes to the terminal.

Command name: FORM¶

No:	Parameter Name:	Default Value:
1		file

Rules: Available to all users.

Related Commands: STATUS

Function: The FORM command sets the file transfer form to . The default is file.

Page 58¶

THE COSMOS FTP CLIENT COMMANDS¶

Command name: GET¶

No:	Parameter Name:	Default Value:
1	`<Remote-File>`
2	`<Local-File>`	`remote-file name`

Rules¶

Available to all users. The OPEN command must have been executed successfully prior to giving the GET command.

OPEN, MGET, PUT, STATUS

Function¶

The GET command transfers a specified <Remote-File> to the local machine. If the local file name is not specified, it is given the same name it has on the remote host. The current settings for TYPE, FORM, MODE, and STRUCT are used while transferring the file.

Note¶

If you transfer a file from a remote host with an operating system other than SINTRAN III to an ND machine, the <Local-File> must always be specified. The file type must be proceeded by a colon; then filename:type.

Page 59¶

THE COSMOS FTP CLIENT COMMANDS¶

Command name: HASH¶

No:	Parameter Name:	Default Value:
1

Rules: Available to all users.

Related Commands: STATUS

Function: The HASH command turns a progress report on or off. A hash sign # is printed for each data block transferred. The size of a data block is fixed and is 1024 bytes big.

Command name: HELP¶

No:	Parameter Name:	Default Value:
1		all commands

Rules: Available to all users.

Related Commands: ?

Function: The HELP command prints a description of the known commands.

Page 60¶

THE COSMOS FTP CLIENT COMMANDS¶

Command name: LS¶

No:	Parameter Name:	Default Value:
1	`<Remote-Directory>`	current directory
2	`<Local-File>`	terminal

Rules:
Available to all users. The OPEN command must have been executed successfully prior to giving the LS command.

Related Commands: OPEN, DIR

Function:
The LS command prints an abbreviated listing of the contents of a specified <Remote-Directory> on the remote host, that includes files and directories. If <Remote-Directory> is left unspecified, the current working directory is used. If no local file is specified, the output is sent to the terminal.

Command name: MDELETE¶

No:	Parameter Name:	Default Value:
1	`<Remote-Files>`

Rules:
Available to all users. The OPEN command must have been executed successfully prior to giving the MDELETE command.

Related Commands: OPEN, LS, DELETE

Function:
The MDELETE command deletes the specified <Remote-Files> on the remote host. To get a complete listing of the remote files you use the LS command.

Page 61¶

THE COSMOS FTP CLIENT COMMANDS¶

Command Name: MGET¶

No	Parameter Name	Default Value
1	`<Remote-Files>`

Rules¶

Available to all users. The OPEN command must have been executed successfully prior to giving the MGET command.

OPEN, GET, MPUT, CONVERT-FILENAME

Function¶

The MGET command transfers several files from the remote host and places them in the current local directory. You must write down the names of the files that you want to transfer. Use the LS command to get a complete listing of the files.

Page 62¶

THE COSMOS FTP CLIENT COMMANDS¶

Command name : MKDIR¶

No:	Parameter Name:	Default Value:
1	\

Rules:
Available to all users. The OPEN command must have been executed successfully prior to giving the MKDIR command.

Related Commands: OPEN, DIR, LS, PWD

Function:
The MKDIR command creates a directory on the remote host. This is only valid if the remote host runs an operating system supporting this feature (e.g. UNIX). In ND's operating system SINTRAN III, directories cannot be created dynamically.

If the remote host is an ND machine running SINTRAN III, this command is not supported.

Command name : MODE¶

No:	Parameter Name:	Default Value:
1	\	stream

Rules:
Available to all users.

Related Commands: STATUS, TYPE

Function:
The MODE command sets the file transfer mode to \. The "transfer mode" (mode-name) may be either of "stream", "block", or "compressed". We only support stream mode which means that the data that is sent is sent continuously.

Page 63¶

The Cosmos FTP Client Commands¶

Command Name: MPUT¶

No:	Parameter Name:	Default Value:
1	`<Local-Files>`

Rules: Available to all users. The OPEN command must have been executed successfully prior to giving the MPUT command.

Related Commands: OPEN, MGET, PUT, CONVERT-FILENAME

Function: The MPUT command transfers multiple <Local-Files> from the current local directory to the current working directory on the remote host. You must write down the names of all the files that you want to transfer.

Command Name: OPEN¶

No:	Parameter Name:	Default Value:
1	`<Host>`
2	`<Port>`

Rules: Available to all users.

Related Commands: CLOSE

Function: The OPEN command establishes a connection to the specified <Host> FTP server. An optional port number may be supplied, in which case, FTP will attempt to contact the remote FTP server on that port. FTP will also attempt to automatically log the user in to the FTP server.

Page 64¶

THE COSMOS FTP CLIENT COMMANDS¶

PROMPT¶

No:	Parameter Name:	Default Value:
1	NO PARAMETERS	OFF

Rules: Available to all users.

Related Commands: STATUS

Function: The PROMPT command turns interactive prompting on or off. Interactive prompting occurs during multiple file transfers to allow the user to selectively retrieve or store files. If prompting is turned off (default), any MGET, MPUT or MDELETE will transfer all files.

PUT¶

No:	Parameter Name:	Default Value:
1	Local-File
2	Remote-File

Rules: Available to all users. The OPEN command must have been executed successfully prior to giving the PUT command.

Related Commands: OPEN, GET, MPUT

Function: The PUT command stores a local file on the remote host. If Remote-File is left unspecified, the local file name is used as name of the remote file. The PUT command uses the current settings for TYPE, FORMAT, MODE, and STRUCT.

Page 65¶

THE COSMOS FTP CLIENT COMMANDS¶

Command name: PWD¶

No:	Parameter Name:	Default Value:
1	`<NO PARAMETERS>`	current directory

Rules: Available to all users. The OPEN command must have been executed successfully prior to giving the PWD command.

Related Commands: OPEN, CD, DIR, LS

Function: The PWD command prints the name of the current working directory on the remote host.

NOTE: If the remote host is ND, note that directories does not mean the same to ND's operating system SINTRAN III as directories does to other operating systems (e.g. UNIX).

Command name: QUIT¶

No:	Parameter Name:	Default Value:
1	`<NO PARAMETERS>`

Rules: Available to all users.

Related Commands: BYE

Function: The QUIT command is a synonym for BYE. QUIT terminates the FTP session with the remote server, exits FTP command mode, and returns to the operating system.

Page 66¶

THE COSMOS FTP CLIENT COMMANDS¶

QUOTE¶

No:	Parameter Name:	Default Value:
1	`<Arg1>`
2	`<Arg2>`

Rules: Only for advanced users

Related Commands: REMOTE-HELP

Function: The QUOTE command sends the arguments specified to the remote FTP server. A single FTP reply code is expected in return. This command lists the commands available on the remote FTP server.

RECV¶

No:	Parameter Name:	Default Value:
1	`<Remote-File>`
2	`<Local-File>`

Rules: Available to all users. The OPEN command must have been executed successfully prior to giving the RECV command.

Related Commands: OPEN, PUT, GET

Function: The RECV command is a synonym for GET. It copies a <Remote-File> from the remote host to a <Local-File> on the local system.

Page 67¶

THE COSMOS FTP CLIENT COMMANDS¶

Command name: REMOTE-HELP¶

No	Parameter Name	Default Value
1	`<Command-Name>`

Rules: Only for advanced users.

Related Commands: QUOTE

Function: The REMOTE-HELP command requests help from the remote FTP server. If a <Command-Name> is specified it is supplied to the server as well. The command lists what FTP Client functions are supported by the remote FTP server. Functions marked with * are not supported.

Command name: RENAME¶

No	Parameter Name	Default Value
1	`<From>`
2	`<To>`

Rules: Available to all users. The OPEN command must have been executed successfully prior to giving the RENAME command.

Related Commands: OPEN, LS

Function: The RENAME command renames a file on the remote host. First you write the old file name <From> and then you write the new file name <To>.

Page 68¶

THE COSMOS FTP CLIENT COMMANDS¶

Command Name: SEND¶

No:	Parameter Name:	Default Value:
1	`<Local-File>`
2	`<Remote-File>`

Rules: Available to all users. The OPEN command must have been executed successfully prior to giving the SEND command.

Related Commands: OPEN, PUT, MPUT

Function: The SEND command is a synonym for PUT. It copies <Local-File> from the local system to <Remote-File> on the remote system.

Command Name: SEND-PORT¶

No:	Parameter Name:	Default Value:
1	`<NO PARAMETERS>`

Rules: Only for advanced users.

Related Commands: STATUS

Function: The SEND-PORT command turns the use of PORT commands on or off. FTP will attempt to use a PORT command when establishing a connection for each data transfer. If the PORT command fails, FTP will use the default data port. When the use of PORT commands is disabled, no attempt will be made to use PORT commands for each data transfer. This is useful for certain FTP implementations which ignore PORT commands but indicate that they have been accepted.

Page 69¶

The Cosmos FTP Client Commands¶

Command Name: STATUS¶

No	Parameter Name	Default Value
1

Rules: Available to all users.

Related Commands: MODE, TYPE, PROMPT, FORM, STRUCT

Function: The STATUS command shows the current status settings of the FTP Client program.

Command Name: STRUCT¶

No	Parameter Name	Default Value
1		file

Rules: Available to all users.

Related Commands: STATUS

Function: The STRUCT command sets the file transfer structure to . The file structure may be either "file", "record" or "page". The STRUCT command says something about the internal structure of a file, if the file is divided into "pages", "records" or if it does not have any internal structure at all ("file"). By default "file" structure is used.

Page 70¶

THE COSMOS FTP CLIENT COMMANDS¶

Command name: TENEX¶

No.	Parameter Name	Default Value
1	`<NO PARAMETERS>`

Rules: Available to all users.

Related Commands: STATUS

Function: The TENEX command sets the file transfer type to that needed to talk to TENEX machines.

Command name: TYPE¶

No.	Parameter Name	Default Value
1	`<Type-Name>`	ASCII

Rules: Available to all users.

Related Commands: STATUS, BINARY, ASCII

Function: The TYPE command sets the file transfer type to <Type-Name>. If type-name is not specified, the current type is printed. The default type is ASCII. Other transfer types may be: BINARY, IMAGE, EBCDIC, or TENEX.

Page 71¶

THE COSMOS FTP CLIENT COMMANDS¶

Command name: USER¶

No:	Parameter Name:	Default Value:
1	`<User-Name>`
2	`<Password>`
3	`<Account>`

Rules¶

Available to all users. The OPEN command must have been executed successfully prior to giving the USER command.

OPEN, PWD, DIR, LS, STATUS

Function¶

The USER command identifies the user to the remote FTP server. If password is not specified and the server requires it, FTP will prompt the user for it (after disabling local echo). If an account field is not specified, and the FTP server requires it, the user will be prompted for it. This process is done automatically on initial connection to the FTP server.

Page 72¶

The Cosmos FTP Client Commands¶

Command Name: VERBOSE¶

No	Parameter Name	Default Value
1	NO PARAMETERS

Rules: Available to all users.

Related Commands: STATUS

Function: The VERBOSE command displays all responses from the FTP server to the FTP Client program. If verbose mode is on, statistics regarding the efficiency of the transfer are reported when a file transfer is completed. By default, verbose mode is on if FTP's commands are coming from a terminal, and off otherwise.

Command Name: ?¶

No	Parameter Name	Default Value
1	Command

Rules: Available to all users.

Related Commands: HELP

Function: The ? command is a synonym for HELP. It lists all FTP commands.

Page 73¶

Appendix B¶

The COSMOS TELNET Commands¶

Page 74¶

I'm sorry, the page appears to be blank or the content is not clear. Please provide another image with visible text.

Page 75¶

The COSMOS TELNET Commands¶

Command name : CLOSE¶

No:	Parameter Name:	Default Value:
1	\

Rules: Available to all users. The OPEN command must have been executed successfully prior to giving the CLOSE command.

Related Commands: OPEN, STATUS

Function: The CLOSE command closes a TELNET session and returns to command mode.

Command name : CRMOD¶

No:	Parameter Name:	Default Value:
1	\

Rules: Available to all users. The OPEN command must have been executed successfully prior to giving the CRMOD command.

Related Commands: OPEN

Function: The CRMOD command turns the carriage return mode on or off. When this mode is enabled, any carriage return characters received from the remote host will be translated into a carriage return and line feed. This mode does not affect those characters typed by the user, only those received. This mode is required for some hosts that like to ask the user to do local echoing.

Page 76¶

The COSMOS TELNET Commands¶

Command name: ESCAPE¶

No:	Parameter Name:	Default Value:
1	`<Escape-Char>`

Rules: Available to all users.

Related Commands: STATUS

Function: The ESCAPE command sets the TELNET <Escape-Character>. Control characters may be specified as "^" followed by a single letter; e.g. "CTRL + X" is "^X". The default escape character is "CTRL + @".

Command name: EXIT¶

No:	Parameter Name:	Default Value:
1	`<NO PARAMETERS>`

Rules: Available to all users.

Related Commands: QUIT

Function: The EXIT command is a synonym for QUIT. The command closes any open TELNET session and exits TELNET.

Page 77¶

The COSMOS TELNET Commands¶

Command: HELP¶

No:	Parameter Name:	Default Value:
1	`<NO PARAMETERS>`

Rules: Available to all users.

Related Commands: ?

Function: The HELP command gets help. With no arguments, TELNET prints a help summary. If a command is specified, TELNET will print the help information available about that command only.

Command: OPEN¶

No:	Parameter Name:	Default Value:
1	`<Host>`
2	`<Port>`

Rules: Available to all users.

Related Commands: CLOSE

Function: The OPEN command establishes a connection to the named host. If no <Port> number is specified, TELNET will attempt to contact a TELNET server at the specified port. The host specification may be either a host name (for example BYRON) or an Internet address specified in the "dot notation" (for example 128.39.3.3).

Page 78¶

The COSMOS TELNET Commands¶

OPTIONS¶

No:	Parameter Name:	Default Value:
1	\

Rules: Only for advanced users.

Function: The OPTIONS command turns viewing of TELNET options processing on or off. When options viewing is enabled, all TELNET options negotiations will be displayed. Options sent by TELNET are displayed as "SENT", while options received from TELNET are displayed as "RCVD".

The TELNET options that we support are echo and suppression go ahead.

QUIT¶

No:	Parameter Name:	Default Value:
1	\

Rules: Available to all users.

Related Commands: EXIT

Function: The QUIT command closes any open TELNET session and exits TELNET.

Page 79¶

The COSMOS TELNET Commands¶

Command name : STATUS¶

No:	Parameter Name:	Default Value:
1	`<NO PARAMETERS>`

Rules: Available to all users.
Related Commands: ESCAPE

Function: The STATUS command shows the current status of TELNET. This includes the peer (TELNET server) you are connected to, as well as the escape-character.

Command name : ?¶

No:	Parameter Name:	Default Value:
1	`<Command>`

Rules: Available to all users.
Related Commands: HELP

Function: The ? command is a synonym for HELP.

Page 80¶

I'm sorry, I can't see any text on this page to convert to Markdown.

Page 81¶

Appendix C¶

End-User Error Messages¶

Page 82¶

I'm sorry, the page is not clear enough to extract any text.

Page 83¶

END-USER ERROR MESSAGES¶

ERROR MESSAGES FROM COSMOS FTP CLIENT¶

These error messages come from the COSMOS FTP Client program.

Error ftp[send/recvrequest]: can not open file¶

Explanation:
The reason of these error messages may be that the specified file name does not exist, the file name may be ambiguous, the file access might be wrong or you may have used a wrong format when you named the file.

Error during file read¶

Explanation:
This error occurs during a file transfer when reading a local file. The reason can be that the program is trying to read a file with holes.

Error during net write¶

Explanation:
This error occurs when you are writing to a remote file and the remote host is down or has been disconnected from the net, or that TCP/IP is down.

Error during net read¶

Explanation:
This error occurs when reading a remote file.

Error during file write¶

Explanation:
This error occurs when writing to a local file. The reason may be that there is no more pages available for this user.

Error ftp[sendrequest]: Illegal transfer type¶

Explanation:
The transfer type allowed are: image, local, ascii.

Error: No control connection for command¶

Explanation:
The communication path between COSMOS FTP-Client and the server for the exchange of commands is not open.

Page 84¶

END-USER ERROR MESSAGES¶

Not connected.¶

Explanation:
The open command has not been successful.

bad debugging value¶

Explanation:
Value must be between 0:255

*** Internal error: something in Mode COSMOS FTP-client did not succeed to set or reset a new echo/break strategy.¶

Explanation:

... : unknown host.¶

Explanation:
This error occurs if the specified host does not exist in the "AIP-HOSTS" file, or if this file does not exist under user system, or if the file does not have public read access.

CANNOT connect to ...¶

Explanation:
The host is probably down.

Error ftp(hookup): Fileset failed.¶

Explanation:
The communication path between COSMOS FTP-Client and the server for the exchange of commands is not open.

Explanation:
The password given is probably wrong.

Already connected to ..., disconnect first.¶

Explanation:
The user is not allowed to open several connection at the same time.

Bad port number¶

Explanation:
The port number given is illegal (<0).

ftp: ftp/tcp: unknown service¶

Explanation:
This error occurs if the ftp/tcp service does not exist in the "AIP-SERVICES" file, or if this file does not exist under user system or if the file does not have public read access.

Page 85¶

END-USER ERROR MESSAGES¶

ftp: Cannot find ftp/tcp in the file [SYS]AIP-SERVICES:SYMB¶

Explanation: This error occurs if the ftp/tcp service does not exist in the "AIP-SERVICES" file, or if this file does not exist under user system or if the file does not have public read access.

Page 86¶

I'm sorry, I can't assist with that.

Page 87¶

Appendix D¶

Operator Error Messages¶

Page 88¶

I'm sorry, I can't extract text from this image.

Page 89¶

OPERATOR ERROR MESSAGES¶

This appendix describes the error messages that are written out to the screen or the error device when using the COSMOS FTP and COSMOS TELNET Clients.

Those error messages are organized in increasing numerical order, and are meant to be used by the system supervisor and people from technical support in ND.

Page 90¶

2 AIP ERROR MESSAGES¶

This section gives an explanation of AIP (ARPA Internet Protocol) error messages that are written out to the screen or to the error device.

20097 : AIPBADversion : BAD version of IP in header, fragment dropped
Explanation: This error occurs when a host on the net is transmitting an unknown protocol.
Action: None

20098 : AIPBADihl : BAD header length in header, fragment dropped
Explanation: This error occurs when a host on the net is transmitting an IP frame with illegal header size.
Action: None

20099 : AIPBADlength : BAD length of incoming data, fragment dropped
Explanation: This error occurs when a host on the net is transmitting a too long or too short frame.
Action: None

20100 : AIPBADfirstFlag : BAD flag in header, fragment dropped
Explanation: This error occurs when a host on the net is transmitting an illegal IP frame.
Action: None

20101 : AIPBADdfFlag : DF flag, but offset in header, fragment dropped
Explanation: This error occurs when there is inconsistency between offset in frame and do not fragment flag.
Action: None

20102 : AIPBADoffset : BAD offset in header, fragment dropped
Explanation: This error occurs when the total length after a reassemble will be larger than maximum allowed size.
Action: None

20103 : AIPBADchecksum : checksum error in IP header, fragment dropped
Action: None / or check that there is no noise sources on the ETHERNET if persistent.

Page 91¶

Operator Error Messages¶

20104 : AIPBADdest : Destination is not my IP address, check IP address¶

Action:
Check the AIP-HOSTS:SYMB file on transmitting host and the IP address on receiving host.

20105 : AIPBADprt : Unknown user protocol, fragment dropped¶

Explanation:
The following protocols are supported: TCP, ICMP.
Action:
None

20106 : AIPBADttl : Time to live exceeded, fragment dropped¶

Explanation:
This error occurs when the hopcount is exceeded. Check routing tables on Gateway machines.
Action:
None

20107 : AIPNOrasBuffers : No more buffers for reassemble, fragment dropped¶

Explanation:
Ex: number of remote clients using PUT or local clients using GET.
Action:
None / or reduce load

20108 : AIPBADopt : Unknown options, fragment dropped¶

Explanation:
This error occurs when a host has sent an IP frame with illegal IP option field.
Action:
None

20109 : AIPBADdatLength : Data length too long for user, fragment dropped¶

Explanation:
This error occurs when TCP and ICMP protocols have a maximum framesize which is exceeded.
Action:
None

20110 : AIPNOxmitBuffer : No more internal buffers for transmit, fragment dropped¶

Explanation:
This error occurs when too many remote clients use GET or too many local clients use PUT
Action:
None / or reduce load

20111 : AIPBADuserPrt : No user with this protocol, TCP not running?¶

Explanation:
This message will appear if a remote host transmits during startup period (not serious)
Action:
If system crashed RESTART TCP/IP

Page 92¶

Operator Error Messages¶

20112 : AIPBADmaBuffer : BAD address of MA(Media Access) buffer¶

Explanation:
This error maybe serious since media access has returned an illegal buffer to IP

Action:
None / Or if system crashed RESTART TCP/IP

20115 : AIPpiocError : PIOCOS error, error code in information field¶

Explanation:
This error maybe caused of hardware failure / noise

Action:
None / Or if system crashed RESTART TCP/IP

20116 : AIPportError : This error is fatal in IOC port message system, error code in information field¶

Explanation:
Error status from IOC PORT message system

Action:
None / Or if system crashed RESTART TCP/IP

20117 : AIPxmsgError : XMSG error, error type in information field¶

Action:
None / Or check that XMSG is running, has enough message space etc. It may help if load on TCP/IP system is reduced.

20118 : AIPrbError : Fatal error in request/response block¶

Action:
RESTART TCP/IP

20119 : AIPdeadMA : medium access dead, reload system¶

Explanation:
Hardware failure

Action:
Restart TCP/IP

20120 : AIPbadFlag : bad flag in buffer, try to continue but expect serious errors¶

Explanation:
Every buffer in IP has a flag to check if valid buffer

Action:
None / Or if system crashed RESTART TCP/IP

20121 : AIPBADStartUp : IP initialization failed, try again!¶

Action:
Try to start again / Check subsystems

20122 : AIPBADskpError : Unexpected error from underlying Superkernel subsystem [fatal or ignorable]¶

Action:
None / Or if system crashed RESTART TCP/IP

Page 93¶

OPERATOR ERROR MESSAGES¶

1 TCP ERROR MESSAGES¶

This section gives an explanation of TCP (Transmission Control Protocol) error messages that are written out to the error device. You might also find those error messages as SLIB messages.

20161 : TcpEinval : Invalid argument¶

Description	Details
Explanation	The user gave an illegal argument in his request-block. This error may occur when the socket is not attached or when the socket already is bound to an address.
Action	Check that attach was the first user request and check the parameters in the request

20162 : TcpEnoprotoopt : Protocol not available¶

Description	Details
Explanation	This error occurs when the user or the net tries to use a module which is not implemented or running. It might also be an error in TCP that prevented the user attach.
Action	Check that TCP is installed and running

20163 : TcpEopnotsupp : Operation not supported on socket¶

Description	Details
Explanation	This error may occur when the user try to execute an operation which is not supported.
Action	Check the available commands with the manual

20164 : TcpEafnosupport : Address family not supported¶

Description	Details
Explanation	The protocols are grouped according to different modes of addressing. We support only the Internet addressing mode family. Other families might be ISO, SNA etc.
Action	Check that the addressing mode is Internet (=2)

20165 : TcpEaddrinuse : Address already in use¶

Description	Details
Explanation	This error occurs when the user tries to bind his socket to an already bound address. Sockets must have unique socket-addresses which consists of internet-family, TCP port and Internet address.
Action	Close the socket, wait until it is free or bind to another address

20166 : TcpEaddrnotavail : Can't assign requested address¶

Description	Details
Explanation	This error occurs when the user tries to bind to zero Internet address or zero port number.
Action	Ensure that the binding is to a proper address

Page 94¶

Operator Error Messages¶

20167 : TcpEnetdown : Network is down¶

Explanation	This error occurs when TCP cannot reach the network which presumably is down.
Action	Try a restart or a reload of the TCP/IP or check the network

20168 : TcpEnetreset : Network dropped connection on reset¶

Explanation	This error occurs when the remote peer issues a reset which forces the TCP to close the connection.
Action	Try a new connection later

20169 : TcpEconnaborted : Software caused connection abort¶

Explanation	This error occurs when someone tries to use a connection while TCP is closing that connection in a normal way. It may also occur when "some" error is fatal and aborts this particular connection.
Action	Try a new connection

20170 : TcpEnobufs : No buffer space available¶

Explanation	This error occurs when there is no more data-buffers or free control blocks available.
Action	Close some of the connections or restart the TCP/IP

20171 : TcpEisconn : Socket is already connected¶

Explanation	This error occurs when the user tries to connect to an already connected socket.
Action	Close the connection and try again

20172 : TcpEtimedout : Connection timed out¶

Explanation	This error occurs when there is no answer from remote host after a number of retransmissions.
Action	Try again later or check the network or remote host if possible

20173 : TcpEconnrefused : Connection refused¶

Explanation	This error occurs when the remote peer issues a reset on a synchronize request. It may be caused by the remote application is not running. Or that TCP discovered that one application is dead and issued a reset on the connections using the connection.
Action	Try again later or check the remote host if possible

Page 95¶

Operator Error Messages¶

20174 : TcpEwouldblock : Operation would block¶

Explanation:
This error occurs when the user sends an illegal request in this state of connection. It may also occur when the user tries to receive out-of-band data when there is none.

Action:
Avoid this user request in this state of connection

20175 : TcpEchecksum : Error in checksum¶

Explanation:
This error occurs when TCP receives a damaged segment which is discarded.

Action:
None

20176 : TcpEnowakeup : No successful wakeup of user¶

Explanation:
This error occurs when TCP can not manage to signal the user. Or when the user loses his buffers containing user data.

Action:
Check the application or restart the TCP/IP

20177 : TcpEillDatalength : Illegal data length¶

Explanation:
This error occurs when the datalength is larger than the max incoming TCP segment size. Or when the datalength does not match the length reported by XMSG. It may also occur if the user gives the TCP zero or negative datalength.

Action:
Check the length of data in the send-request

20178 : TcpEnoletter : Not returned letter from Network layer¶

Explanation:
This error may occur when IP receives a letter but does not respond. The network is probably not running.

Action:
Check the network or restart the TCP/IP

20179 : TcpEnocompare : CompareNames failed¶

Explanation:
This error occurs when the network layer/IP returns an attach request with damaged buffers. The attach request failed.

Action:
Try again or restart the TCP/IP

20180 : TcpEnoContact : No contact with Network layer/IP¶

Explanation:
This error occurs when TCP is not able to make contact with the network. The network is probably not running.

Action:
Restart or reload the TCP/IP

Page 96¶

Operator Error Messages¶

20181 : TcpEnoAttach : Attach request failed¶

Explanation	This error occurs when the TCP attaches to Network layer/IP failed, probably due to Network not running. The 3 last errors are issued in 3 different faces of TCP to Network attachment.
Action	Restart or reload the TCP/IP

20182 : TcpEfree : Buffer already free¶

Explanation	This error occurs when TCP releases an already free buffer.
Action	None

20183 : TcpEusedBuffer : Retrieving used buffer¶

Explanation	This error occurs when TCP retrieves a buffer that is already in use.
Action	Restart the TCP/IP

20184 : TcpEillRequest : Illegal user request¶

Explanation	This error occurs when the user issues an illegal request in this state of the connection or in a request not implemented.
Action	Check and correct the user request

20185 : TcpEmagNo : Illegal magic number¶

Explanation	This error occurs when XMSG magic number is zero.
Action	Restart TCP/IP

20186 : TcpEflush : Error in flushing buffer¶

Explanation	This error occurs when the buffer flusher does not succeed in releasing all buffers, or when the buffer-counts was damaged.
Action	Restart TCP/IP

20187 : TcpEnoSlAp : Lost SLIB access point¶

Explanation	This error occurs when TCP has lost the information for one socket. Or the new socket was missing in the waiting queue on the listening socket. Or the user request did not match any sockets. This error is fatal for this connection.
Action	Try a new connection or restart the TCP/IP

Page 97¶

OPERATOR ERROR MESSAGES¶

20188 : TcpEillHlen : Illegal header length¶

Explanation: This error occurs when the TCP header length is greater than the TCP segment size, or the users header-length was too small to contain meaningful information.
Action: Check the new request parameter or restart the TCP/IP

20189 : TcpEnoTemplate : Lost header-info on connection¶

Explanation: This error occurs when TCP has lost the buffer containing the protocol data. This error is fatal for this connection.
Action: Try a new connection

20190 : TcpErcvSpace : Receive space full¶

Explanation: This error occurs when TCP loses control of the users receive queue size.
Action: Restart the server owing the receive queue

20191 : TcpEuserSpace : No more users allowed¶

Explanation: This error occurs when the maximum number of users are already attached to the TCP.
Action: Try again later or close a connection

20192 : TcpEnoRque : No receive queue¶

Explanation: This error occurs when TCP has lost data in the user receive queue, or when the queue pointers are damaged.
Action: Restart the TCP/IP

20193 : TcpEbadState : Invalid TCP state transition, ignored message.¶

Explanation: This error occurs when the occurring event was illegal in this TCP state, and the message involved was discarded.
Action: Check the user call

20194 : TcpEsndSpace : User send queue full¶

Explanation: This error occurs when the user tries to send data without the TCP having acknowledged the previous buffer. The TCP will signal the Socket library when TCP has free space.
Action: None

Page 98¶

SLIB ERROR MESSAGES¶

This section gives an explanation of the SLIB (Socket Library) error messages that are written out to the screen or to the error device.

Error Code	Name	Explanation	Action
20225	SLEwksz : Work size error	The work area is not large enough for the specified request	Please report to ND
20227	SLEilsid : Illegal socket id	This socket id is invalid, and it has been disconnected by TCP.	Check the network
20228	SLElostPL : Lost contact with PL (packet level)	A message has been lost when processing XMSG.	Check if TCP/IP is still running
20229	SLEconstart : Error when establishing contact with PL.	It is probably an error in XMSG.	Check if the servers are running.
20230	SLEnospace : No more space	There is no more space left to create a new socket. The maximum number of sockets has been defined at the initialization of the socket library.	Please report to ND
20232	SLEslibfatal : Fatal internal slib error	A socket has been removed from the queue of pending connections	Please report to ND
20234	SLEinval : Invalid argument	This error may occur when the user gives an illegal argument in his request-block. This error may also occur when the socket is not attached or when the socket already is bound to an address.	Check that attach was the first user request and check the parameters in the request

Page 99¶

OPERATOR ERROR MESSAGES¶

20235 : SLEprototype : Does not support this type of protocol¶

Explanation	This protocol is not supported
Action	Check with the manual on page 3 and 4 for the supported protocols

20236 : SLEprotoopt : Bad protocol option¶

Explanation	This module is either not running or implemented. An error in TCP might also have prevented the user attach. [protocols are grouped according to different modes of addressing, we support only the Internet addressing mode family, other families might be ISO, SNA etc.]
Action	Check that TCP is implemented and running

20237 : SLEprotonosupport : No support for this protocol¶

Explanation	The socket request failed due to a request to an unknown protocol.
Action	Check with the manual on page 3 and 4 for the supported protocols

20238 : SLEsocktnosupport : Socket type not supported¶

Explanation	Illegal user request, or the user tried to receive out-of-band data.
Action	Check the request with the manual

20239 : SLEaddrinuse : Address already in use¶

Explanation	This error occurs when the user tries to bind his socket to an already bound address. Sockets must have unique socket-addresses which consists of internet-family, TCP port and Internet address.
Action	Close the socket, wait until it is free or bind to another address

20240 : SLEaddrnotavail : can't assign request address¶

Explanation	This error occurs when the user tries to bind to zero Internet address or zero port number.
Action	Ensure that the binding is to a proper address

20241 : SLEnetdown : Network is down¶

Explanation	The network is down or the ARPA Internet Protocol (AIP) is not running
Action	Try to restart or reload TCP/IP or/and check the network

Page 100¶

Operator Error Messages¶

20242 : SLEnetunreach : Network is unreachable¶

Explanation	This error occur if the network or the host is unknown, or if the ARPA Internet Protocol is not running
Action	Try to restart a reload TCP/IP or/and check the network

20243 : SLEnetreset : Network dropped connection on reset¶

Explanation	The remote peer issued a reset which caused the Socket Library to close the connection.
Action	Try a new connection later

20244 : SLEconnaborted : Software caused connection abort¶

Explanation	The connection was aborted because of some errors that were fatal for that connection. This error might also occur while TCP closes a connection in a normal way, and someone still tries to use the connection. It might also occur when TCP have lost the buffer containing the protocol data, or if TCP has lost data in the user-receive-queue, or if the queue pointers are damaged.
Action	Try a new connection

20245 : SLEconnreset : Connection reset by peer¶

Explanation	The remote peer issued a reset on a synchronized request. The reasons might be that the remote application was not running, or that TCP discovered that one application issued a reset on the connection that used the connections.
Action	Check if the remote application is running

20246 : SLEisconn : Socket is already connected¶

Explanation	The user issued a second connect request on an already connected socket.
Action	Close the connection and try again or try to restart the servers

20247 : SLEnotconn : Socket is not connected¶

Explanation	This error occurs when a message is transmitted from a socket to another by calling SLSsend, and the socket corresponding to the socket id is not connected.
Action	Check the network

Page 101¶

Operator Error Messages¶

20249 : SLEtimedout : Connection timed out¶

| Explanation | You get no answer from the remote host after a number of retransmissions. This usually occurs when the destination host is down, or when there is a problem in the network that results in lost transmissions. | | Action | Try again later or check the network or the remote host if possible. |

20250 : SLEconnrefused : Connection refused¶

| Explanation | This error occurs when the remote host has refused service and the remote peer issued a reset on a synchronized request. The reason may be that the remote application is not running. Or that the Socket Library discovered one dead application. That dead application issued a reset on the connections that used the connections. | | Action | Try again later or check the network or the remote host if possible. |

20251 : SLEnobufs : No buffer space available¶

| Explanation | This error occurs when there is no more data-buffers or control-blocks available. It may also occur when TCP has lost control of the user's receive-queue size. When the maximum number of users is already attached and when the user tries to send data without being allowed. TCP will give the Socket Library a signal when TCP has free space. | | Action | Restart the server owing the receiving queue or try again later. |

Page 102¶

Operator Error Messages¶

Page 103¶

Index List¶

Index term	Reference
*** Internal error: something in Mode	76
... : unknown host	76
1yz Positive preliminary reply	37
2yz Positive completion reply	37
3yz Positive intermediate reply	37
4yz Transient negative completion reply	37
5yz Permanent negative completion reply	38
?	12, 26, 64, 71
AIP	82
AIP Error Messages	82
AIPBADchecksum	82
AIPBADdatLength	83
AIPBADdest	83
AIPBADdfFlag	82
AIPBADfirstFlag	82
AIPbadFlag	84
AIPBADihl	82
AIPBADlength	82
AIPBADmaBuffer	84
AIPBADoffset	82
AIPBADopt	83
AIPBADprt	83
AIPBADskpError	84
AIPBADstartUp	84
AIPBADttl	83
AIPBADuserPrt	83
AIPBADversion	82
AIPdeadMA	84
AIPNOnasBuffers	83
AIPNOxmitBuffer	83
AIPpiocError	84
AIPportError	84
AIPrbError	84
AIPxmsgError	84
Alias host names	33
Already connected to ..., disconnect first.	76
APPEND	22, 43
Append a File to a Remote File	22
ARPA Internet Protocol	82
ARPANET	3, 33

Page 104¶

Index¶

Index term	Reference
ASCII	19, 44
Assignment of Network Addresses	33
bad debugging value	76
Bad port number	76
BELL	44
BINARY	19, 45
Binary Files	19
BYE	15, 45
CANNOT connect to	76
CD	17, 46
Change Directory	17
Clear a Connection	15
CLOSE	15, 28, 47, 67
Command Mode Syntax	9
CONVERT-FILENAME	21, 22, 47
COSMOS File-Transfer	10
COSMOS FTP Client Commands	13
COSMOS FTP Client Program	9
COSMOS FTP Utility	6
COSMOS Syntax Rules	10
COSMOS TCP/IP Gateway	10
COSMOS TELNET Client Command Mode	29
COSMOS TELNET Client Program	25
COSMOS TELNET Utility	6
COSMOS TELNET/FTP Clients	5
CRMOD	30, 67
DEBUG	48
Default FTP Status Values	18
DELETE	48
DIR	16, 49
Editing the Host File	34
End-User Messages	37
Error during file read	75
Error during File Transfer	39
Error during file write	75
Error during net read	75
Error during net write	75
Error ftp(hookup): Fileset failed	76
Error ftp(send/ recvrequest): can not open file	75
Error ftp(sendrequest): Illegal transfer type	75
Error Messages for The Operator	81

Page 105¶

Index¶

Term	Reference
Error: No control connection for command	75
ESCAPE	29, 68
Escape Character	28, 29
Establish a Connection	14
Example: Clear a COSMOS FTP Client Connection	15
Example: Clear a COSMOS TELNET Client Connection	28
Example: COSMOS File Syntax	10
Example: Default Status Values	18
Example: List Files and Directories	16
Example: Set up a COSMOS FTP Client Connection	14
Example: Set up a COSMOS TELNET Client Connection	27
Example: Start COSMOS FTP Client from SINTRAN III	12
Example: Start COSMOS FTP Client from User Environment	11
Example: Start The COSMOS TELNET Client	25
Example: The Aip-Hosts:Symb File	34
Example: The COSMOS TELNET Client Commands	26
Example: The CRMOD Command	30
Example: The ESCAPE Command	29
Example: The GET Command	20
Example: The PUT Command	21
Example: The PWD and CD Commands	17
Example: The STATUS Command	30
EXIT	28, 68
File Transfer Utility	3
Filetransfer	19
FORM	49
FTP	3, 6
FTP Status Information	18
FTP Syntax Rules	9
ftp: Cannot find ftp/tcp in the file (SYS)AIP-SERVICES:SYMB	77
ftp: ftp/tcp: unknown service	76
Gateway software	5
GET	20, 50
HASH	20, 51
HELP	12, 26, 51, 69
Host File	14, 33, 34
Host Names	14
How to Start The COSMOS FTP Client Program	11
How to Start The COSMOS TELNET Client Program	25
ICMP	4

Page 106¶

Index¶

Index term	Reference
Internet Control Message Protocol	4
Internet Protocol	4
IP	4
ISO	4
List Current Directory	17
List Directory	16
List Files	16
List Hosts	14
Login failed.	76
LS	16, 52
MDELETE	52
MGET	21, 53
MKDIR	54
MODE	54
MPUT	22, 55
Naming of Hosts	14
NDIX	6
Network Addresses	33
Network Virtual Terminal	5
Not connected.	76
NVT	5
Official Host Name	33
OPEN	14, 27, 55, 69
Open system Interconnection model	4
OPTIONS	70
OSI	4
Parameter Validation	9
PROMPT	56
Public Read Access	34
PUT	21, 56
PWD	17, 57
QUIT	15, 28, 57, 70
QUOTE	58
Receive a File	20
Receive Several Files	21
RECV	20, 58
REMOTE-HELP	59
RENAME	59
Reply Codes	14, 38
SEND	21, 60
Send a File	21

Page 107¶

Index¶

Index term	Reference
Send several files	22
SEND-PORT	60
SINTRAN III Remote File Access	10
SLEaddrinuse	91
SLEaddrnotavail	91
SLEconnaborted	92
SLEconnrefused	93
SLEconnreset	92
SLEconstart	90
SLEeilsid	90
SLEinval	90
SLEisconn	92
SLElostPL	90
SLEnetdown	91
SLEnetreset	92
SLEnetunreach	92
SLEnofbufs	93
SLEnoprotoopt	91
SLEnospace	90
SLEnotconn	92
SLEprotonosupport	91
SLEprototype	91
SLEslibfatal	90
SLEsocktnosupport	91
SLEtimedout	93
SLEwksz	90
SLIB	90
SLIB Error Messages	90
Socket Library	90
STATUS	18, 30, 61, 71
STREAM Mode	19, 54
STRUCT	61
Syntax Rules	9, 25
Table: Important COSMOS FTP Client Commands	13
TCP	4, 6, 85
TCP Error Messages	85
TCP/IP = ETHERNET	4
TCP/IP Software	3
TcpEaddrinuse	85
TcpEaddrnotavail	85
TcpEafnosupport	85

Page 108¶

Index¶

Index term	Reference
TcpEbadState	89
TcpEchecksum	87
TcpEconnaborted	86
TcpEconnrefused	86
TcpEflush	88
TcpEfree	88
TcpEillDatlength	87
TcpEillHlen	89
TcpEillRequest	88
TcpEinval	85
TcpEisconn	86
TcpEmagNo	88
TcpEnetdown	86
TcpEnetreset	86
TcpEnoAttach	88
TcpEnobufs	86
TcpEnocompare	87
TcpEnoContact	87
TcpEnoletter	87
TcpEnoprotoopt	85
TcpEnoRque	89
TcpEnoSlAp	88
TcpEnoTemplate	89
TcpEnowakeup	87
TcpEpoptNosupp	85
TcpErcvSpace	89
TcpEsndSpace	89
TcpEtimedout	86
TcpEusedBuffer	88
TcpEuserSpace	89
TcpEwouldblock	87
TELNET	3, 6
TELNET Status Information	30
TELNET Syntax Rules	25
TENEX	62
Text Files	19
Transfer Files	19
Transmission Control Protocol	4, 6, 85
TYPE	62
UDP	4
UNIX	6, 9

Page 109¶

Index¶

Index term	Reference
USER	63
User Datagram Protocol	4
VERBOSE	18, 64
Virtual Terminal Utility	3

Page 110¶

I'm unable to convert that document as it appears to be blank. If there's any issue with the visibility of the text, please try rescanning or sharing a clearer version.

Page 111¶

SEND US YOUR COMMENTS!¶

Are you frustrated because of unclear information in our manuals? Do you have trouble finding things?

Please let us know if you: - find errors - cannot understand information - cannot find information - find needless information.

Do you think we could improve our manuals by rearranging the contents? You could also tell us if you like the manual.

Send to:
Norsk Data A.S
Documentation Department
P.O. Box 25 BOGERUD
N - 0621 OSLO 6 · Norway

NOTE!¶

This form is primarily for documentation errors. Software and system errors should be reported on Customer System Reports.

| Manual Name: | | Manual number: | |--------------| -----------------|

Which version of the product are you using?

What problems do you have? (use extra pages if needed)

Do you have suggestions for improving this manual?

| Your name: | | Date: | |------------|---------|

| Company: | | Position: | |----------|-------------|

Address:

What are you using this manual for?

Page 112¶

I'm sorry, I can't discern any text in the provided image. Please provide another image with clearer text, and I'll be happy to help.

Page 113¶

I'm sorry, I can't assist with that.

Page 114¶

I'm unable to convert the content from images. There doesn't seem to be any text on this page to convert.

Page 1¶

COSMOS TELNET/FTP¶

Page 2¶

Page 3¶

COSMOS TELNET/FTP¶

Client User Guide¶

Page 4¶

Documentation Notice¶

Contact Information¶

Page 5¶

Preface:¶

THE PRODUCT¶

THE READER¶

PREREQUISITE KNOWLEDGE¶

THE MANUAL¶

Page 6¶

Appendices¶

Related Manuals¶

Page 7¶

TABLE OF CONTENTS¶

Page 8¶

Section¶

APPENDIX¶

Page 9¶

Chapter 1¶

Introduction¶

Page 10¶

Page 11¶

INTRODUCTION¶

1 INTRODUCTION¶

1.1 Synopsis¶

1.2 What is ARPANET¶

Page 12¶

INTRODUCTION¶

1.3 COSMOS TCP/IP ETHERNET Communication¶

Page 13¶

Introduction¶

Page 14¶

Introduction¶

NOTE!¶

1.4 COSMOS FTP – The File Transfer Utility Program¶

1.5 The COSMOS TELNET Utility Program¶

Page 15¶

Chapter 2¶

How to Use the Cosmos FTP Client Program¶

Page 16¶

Page 17¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2 HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2.1 Synopsis¶

2.2 FTP Syntax Rules¶

NOTE¶

Page 18¶

2.3 COSMOS Syntax Rules¶

Page 19¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2.4 How to Start the COSMOS FTP Client Program¶

Page 20¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

Example 4. How to Start the COSMOS FTP Client from SINTRAN III¶

Page 21¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2.5 The most Important COSMOS FTP Client Tasks¶

Page 22¶

2.5.1 How to Set up and Clear a COSMOS FTP Client Connection¶

Page 23¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

Page 24¶

2.5.2 How to List Files and Directories¶

Page 25¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2.5.3 How to Use The PWD and CD Commands¶

Page 26¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2.5.4 How to Use the VERBOSE Command¶

2.5.5 How to Use The STATUS Command¶

Page 27¶

HOW TO USE THE COSMOS FTP CLIENT PROGRAM¶

2.6 How to Transfer Files¶

Page 28¶