interNet Services V2.0 (BS2000/OSD) User...

U41096-J-Z125-2-76 1

1 PrefaceThe interNet Services product supplements the TCP/IP functionality of openNet Server withthe following standards:

– DNS Resolver and Server– DHCP Server– BOOTP Server– TFTP Server– NTP Client and Server– LDAP Server– FTP Client and Server– TELNET Client and Server

1.1 Target group

This manual is intended for BS2000/OSD users and system administrators who want to useTCP/IP-specific applications and/or services. Knowledge of the BS2000/OSD operatingsystem and the basic concepts of TCP/IP is therefore assumed.Apart from this User Guide, there is also an Administration manual for interNet Services,which contains the relevant information for system and network administrators.

2 U41096-J-Z125-2-76

Summary of contents Preface

1.2 Summary of contents

This manual is laid out as follows:

� Chapter 2: Overview

This chapter describes some basic concepts and the functionality of the individualcomponents of interNet Services.

� Chapter 3: FTP

This chapter describes the client and server functionality offered by interNet Services inBS2000/OSD from a user-oriented standpoint. It also includes detailed descriptions ofthe client commands with illustrative examples.

� Chapter 4: FTAC interface

Chapter 4 describes the use of the FTAC interface for FTP and the FTAC commandinterface.

� Chapter 5: TELNET

This chapter describes the client and server functionality of TELNET from auser-oriented standpoint. It also includes detailed descriptions of the clientcommands with illustrative examples.

� Chapter 6: FTAC messages

The Messages chapter contains a complete list of all FTAC messages.

U41096-J-Z125-2-76 3

Preface Notational conventions

1.3 Notational conventions

This manual uses the following notational conventions:

italicsdenote file names, program names, names of management windows, parameternames, menu titles and menu options as well as commands and variables in themain body of text.

<angle brackets>identify variables for which you have to enter values.

[square brackets]indicates optional input.

fixed-pitch fontdenotes input for the system, system output and file names in examples.

commandElements (names of commands and parameters) of the syntax description forcommands that must be entered unchanged are highlighted in bold.

For informative text

For warnings

References

References in the manual include the page concerned and the section or chapter asrequired. References to topics described in other manuals include the short titleof the manual. The full title can be found in the list of related publications.

i

!

4 U41096-J-Z125-2-76

Changes compared to the previous version / README file Preface

1.4 Changes compared to the previous version

� New FTP server commands mdtm, size and rest support the restart capability of the FTPserver and client.

� Batch support by FTP client

� SNMP support for FTP via a separate SNMP subagent

� New BS2000/OSD-specific FTP server functions: exec, mode, setc, sfil, exit

� New FTP client functions: jobvar, recv, reget, reput, rexit, setfile, svar

� New TELNET client functions: exit, rexit

1.5 README file

Information on any functional changes and additions to the current product versiondescribed in this manual can be found in the product-specific README file.You will find the README file on your BS2000 computer under the file nameSYSRME.TCP-IP-SV.020.E or SYSRME.TCP-IP-AP.040.E. The user ID under which theREADME file is cataloged can be obtained from your system administrator. You can viewthe README file using the /SHOW-FILE command or an editor and print it out on astandard printer using the following command:

/PRINT-DOCUMENT <filename>,LINE-SPACING=*BY-EBCDIC-CONTROL

U41096-J-Z125-2-76 5

2 Internet services in BS2000/OSDWith openNet Server, BS2000/OSD provides a set of internet services that use the transportprotocols TCP (Transmission Control Protocol) and UDP (User Datagram Protocol).openNet Server is a prerequisite for using interNet Services. The relevant internet servicesfor internet servers were defined by the Open Group in the X98PS Product Standard. Theseservices are integrated for BS2000/OSD in the interNet Services delivery unit.

The supported protocols generally work according to the client/server model, i.e. the serverprovides services which are requested and used by one or more clients. The server and theclients may run on the same system or on different systems.

Product Service group Service

openNet Server TCP/IPCommunicationsServices

TCPUDPIPv4IPv6-

Transmission Control ProtocolUser Datagram ProtocolInternet Protocol Version 4Internet Protocol Version 6Requirements for internet hosts

interNet Services File Transfer Service FTP File Transfer Protocol

Terminal Service TELNET

Name Service DNSDDNS

Domain Name ServiceDynamic DNS

Client BootingServices

DHCPBOOTPTFTP

Dynamic Host Configuration ProtocolBoot ProtocolTrivial File Transfer Protocol

Directory Service LDAP Lightweight Directory Access Protocol

Time Service NTP Network Time Protocol

interNet Value Edition Mail Services SMTPPOPIMAP

Simple Mail Transfer ProtocolPost Office ProtocolInternet Message Access Protocol

APACHE Hypertext Services HTTP HyperText Transfer Protocol

SNMP Basic AgentBS2000

Network Management SNMP Simple Network Management Protocol

6 U41096-J-Z125-2-76

FTP / TELNET Internet services in BS2000/OSD

The individual services included in interNet Services are described in detail in the sectionsbelow.

FTP

Data exchange is of central importance when combining several computers in a network.Due to the vast number of computer types available on the market, it is essential to use avendor-independent standard. FTP (File Transfer Protocol) enables data to be exchangedindependently of the structure and the operating system of the computers involved. FTP isbased directly on TCP and can transfer files of all types (e.g. text, image, sound, video orprogram files).

The user communicates with the FTP client via the user interface, and the FTP client setsup a connection to the FTP server through port 21 (control connection). The client sendscommands to the server via this connection, and the server, in turn, acknowledges thesecommands by sending corresponding messages back to the client. The FTP server thenestablishes a second connection to the FTP client using port 20 (data connection) for theactual data exchange.

BS2000/OSD provides both the server and the client functionalities of FTP. Apart from thestandard protocol, the following functions are offered:

– support for BS2000 file formats (SAM, PAM)

– selection of code conversion tables for EBCDIC to ASCII, and vice versa

– security functions via the interface to the optional security product openFTAC, whichpermits FTP transfer admissions and login authorizations to be handled separately,user-specific access profiles to be defined, and access checks to be logged.

TELNET

TELNET enables terminal sessions to be run on networked computers. It offers essentiallythe same functionality as the rlogin command in UNIX, but also includes some protocolelements specially tailored to mainframe systems. BS2000/OSD supports both the clientand the server functionality of TELNET.

U41096-J-Z125-2-76 7

Internet services in BS2000/OSD DNS

DNS

DNS (Domain Name Service) is a global network of DNS servers that map names toIP addresses. Neither the internet nor the operation of intranets would be possible withoutDNS.

DNS names have a hierarchical tree structure spanning various domain levels. The rootdomain is the starting point for all searches within the entire DNS name space. Besides thenames, the DNS also includes addresses and other information.

The Domain Name Service is a distributed and replicated database system with DNSservers and DNS clients (resolvers). The data is maintained on several DNS servers, eachof which may be responsible for one or more DNS domains. If desired, redundant DNSservers may be used for failover security. The resolvers (or clients), by contrast, do not havea local database. For each DNS query, a client may contact one or more DNS servers toobtain the information it needs.

BS2000/OSD provides its users with both the server and the resolver functionality of DNS.

Both the server and the resolver functionality were ported from the BIND coding, which isconsidered the standard implementation for DNS. This provides BS2000/OSD users withaccess to all DNS functions and services. In addition, the high availability of BS2000/OSDalso guarantees reliable access to the DNS servers on the network.

DNS server

DNS clients

What is X’s IP address?

The IP address is Y.

What is X’s IP address?

The IP address is Y.

8 U41096-J-Z125-2-76

BOOTP / DHCP / TFTP Internet services in BS2000/OSD

BOOTP / DHCP / TFTP

The following information is essential in order to communicate over a TCP/IP network: aunique IP address, a subnet mask, the responsible router, and possibly other parameters.This data can be queried from a server using BOOTP (bootstrap protocol) or DHCP(dynamic host configuration protocol) on starting up the system.

Establishing the IP address and bootfile (BOOTP, DHCP) and transferring the bootfile (TFTP)

TFTP (trivial file transfer protocol) is a simple file transfer protocol that is frequently used incombination with BOOTP to transfer boot phases or configuration data to clients withouttheir own storage.

BOOTP was developed so that workstations without a hard disk (e.g. X terminals or disklessworkstations) can be booted remotely via the network. The workstation can pick up theinformation it needs to communicate over the network and download the required bootphase from the BOOTP server without configuration. The BOOTP server maintains atable that assigns the configuration data to each hardware address of the clients that itserves.

The DHCP protocol is an extension of the BOOTP protocol that allows IP addresses to beassigned to workstations permanently or temporarily from a pool of IP addresses. Beforethe lease period of an IP address expires, it must be extended. Otherwise, the IP addresswill be assigned to another workstation.

The DHCP and BOOTP functionalities are both implemented by a DHCP server inBS2000/OSD. The TFTP functionality is provided by a TFTP server. The above figureshows the sequence of a DHCP communication.

What is my IP address?

What is the name of my boot file?

Your IP address is: 10.11.12.13 .

Your boot file is “/tftp/bootfile“.

Transfer boot file “/tftp/bootfile“.

/tftp/bootfile

Booting client

DHCP / BOOTP /TFTP server

U41096-J-Z125-2-76 9

Internet services in BS2000/OSD LDAP

LDAP

Directory services provide data on individuals, applications, services and other resourceson the network. The OSI X.500 directory standard defines the Directory Access Protocol(DAP) as the interface between Directory System Agents (DSA) and Directory User Agents(DUA). DAP is an ISO application protocol and requires the full ISO protocol stack.

The overall data maintained in a directory constitutes the Directory Information Base (DIB).The DIB has a hierarchical structure and is represented by the Directory Information Tree(DIT). Entries in the DIB form the nodes of the DIT. The entries are identified by their names.The name of an entry in the DIT consists of the relative name of its immediate predecessorand its own name component.

Sample of a Directory Information Tree

In contrast to DAP, the Lightweight Directory Access Protocol (LDAP) requires only the TCPtransport service in order to access the DIB of an X.500-type directory.

BS2000/OSD provides the LDAP client and server functionality. The directory is maintainedas a local database.

o=SIEMENS o=SBS

ou=BS2000

o=SIEMENS

c=DE c=UK

Directory Root

10 U41096-J-Z125-2-76

NTP Internet services in BS2000/OSD

LDAP client/server functionality

NTP

The Network Time Protocol (NTP) enables a reference time (Universal Coordinated Time,UTC) to be distributed within the network and also coordinates all clocks within a networkof any size.

Time servers are structured in a hierarchy, i.e. where secondary time servers receive thetime over the network from a primary time server. In order to make the UTC (Universal TimeCoordinated) available on the network, one of the servers should be equipped with aradio-controlled clock that can receive signals generated by an atomic clock. A BS2000server can perform the function of a precise time server as well as a client.

LDAP server

LDAP client

LDAP directory

LDAP

BS2000/OSD

LDAP

LDAP client

U41096-J-Z125-2-76 11

3 FTPinterNet Services includes, among other things, the TCP/IP-based application FTP. The FileTransfer Protocol is used to transfer data between computers from different vendorsindependently of the operating systems running on them. The FTP functionality has beenstandardized, i.e. the relationships between the commands (client) and the correspondingfunctions (servers) are defined in RFC 959. Note, however, that not all FTP functions aremandated in RFC 959, so different implementations may have some minor deviations,depending on the vendor.

FTP works in accordance with the client/server principle which, in turn, requires theexistence of two complementary processes. The initiator of a connection or request is calledthe client, whereas the partner who receives and responds to the request is called theserver. The server process, which is usually permanently started, is known as a daemon.The client process is generally initiated by an appropriate call, e.g. ftp.

The FTP functionality in BS2000/OSD is split into the server and client functionality.

3.1 FTP servers in BS2000/OSD

The FTP server accepts requests from FTP clients on the local network and executes them.

The use of an FTP server on a BS2000/OSD partner system is, of course, only possible,provided the FTP server has been powered up by the administrator.

12 U41096-J-Z125-2-76

FTP server FTP

FTP server in BS2000/OSD

In the sections that follow, the host with the FTP server is referred to as the remote host sothat the description of the server is consistent with that of the client (although from theviewpoint of the server, the local system is its own host).

BS2000/OSD

BS2000 computer MS-DOS computerUNIX computer

Network

FTP server

FTPclient

FTPclient

FTPclient

FTPclient

U41096-J-Z125-2-76 13

FTP FTP server

Mode of operation

For each connection request from a client (open command), the server generates aseparate BS2000 task. The data required to initiate this task (user ID, account number,password) is requested from the client. A program (FTPDC) is then initiated to execute theactual file transfer and the local file accesses initiated by the client. The DMS access rightsin BS2000/OSD (RDPASS, WRPASS, EXPASS, SHARE=YES|NO, ACCESS=READ|WRITE) aswell as the access permissions in POSIX are both taken fully into account.

When multiple clients log on to the server at exactly the same time, a connectionrequest may be rejected. If this occurs, the client must repeat the connectionrequest.

Password protection

In BS2000, individual DMS files can be protected by passwords. The FTP server in BS2000expects function calls with file names in the form

filename,C'password' or filename,X'password'.

Note, however, that this does not apply to the POSIX file system.

Example

A command is issued from UNIX (file name: ZWATON) to overwrite the BS2000 file ANTON,which is protected by a read password OTTO:

put ZWATON ANTON,C'OTTO'

Files that are protected by different passwords (e.g. RDPASS=C'OTTO' andWRPASS=C'KARL') cannot be addressed directly. At least one of the two passwords musthave been entered earlier with the site exec function of the quote command:

quote site exec PASSWORD C'KARL'

quote site exec may only be used when FTP access is not controlled with FTAC.

i

14 U41096-J-Z125-2-76

FTP server FTP

PASSIVE mode

PASSIVE mode enables a file transfer between two servers to be initiated from a client. TheFTP client in BS2000/OSD does not support this procedure. In the BS2000 FTP server, thisfunctionality is supported via the PASV server command.

In PASSIVE mode, the server is made to wait at a data port for a connection request insteadof actively setting up a connection itself. The connection is set up between the two servertasks via the first line address generated. If this line does not support connection betweenthe two servers, the connection request is refused (return code 425, can’t build dataconnection)

Scope of implementation

The functions of an FTP server are implemented in standardized protocol elements (servercommands).

The following table contains a summary of the functions of the FTP servers in BS2000/OSD.

Servercommand

Server function Servers inBS2000/OSD

(DMS) (POSIX)

Corresponding (k)/ Issuing (a) clientcommand

acct State account number + +

abor Abort file transfer + +

allo Allocate memory (+) (+)

appe Append file to existing file + + append (a)

cdup Change to the next higher workingdirectory (POSIX) or remove partialqualifier (DMS)

+ (1) + cdup (a)

cwd Change working directory (POSIX) orremove partial qualifier (DMS)

+ + cd (a)

dele Delete file + + delete (a)

help Request help + + remotehelp (a)

list List file names and directories + + dir (a)

mdtm Specify date and time of last changeto file

+ +

mkd(same asxmkd)

Make directory - +

FTP server functions

U41096-J-Z125-2-76 15

FTP FTP server

mode Define transfer mode + + mode (a,k)

nlst List file names + + ls (a)

noop No operation + +

pass State password + +

pasv Set PASSIVE mode + +

port Define data connection port + +

pwd(same asxpwd)

Show current working directory + +

quit Terminate session + + close (a)

rest Specify position in file where datatransfer is to commence

+ +

retr Retrieve a file + + get (a)

rmd(same asxrmd)

Remove directory - +

rnfr Rename a file, output old name + + rename (a)

rnto Rename a file, output new name + + rename (a)

site Forward command to remote OS orprefix for BS2000/OSD-specific FTPserver functions

+ +

size Output file size + +

stat Show server status information + + status (k)

stor Store file + + put (a)

stou Store files with unique names + + put (a)

stru Define transfer structure + + struct (a+k)

syst Show system information on theserver

+ + system (a)

type Define transfer type + + type (a+k)

user Define user ID + + user (a)

xcup(same asccup)

Change to the next higher workingdirectory (POSIX) or remove partialqualifier (DMS)

+ (1) +

Servercommand


(DMS) (POSIX)



16 U41096-J-Z125-2-76

FTP server FTP

Key

+ The function is implemented.(+) The function is implemented as a dummy function.- The function is not implemented(a) Client command issues the server command.(k) Client command has the same meaning as the server command.(a+k) Client command has the same meaning as the server command and issues the

server command.

xcwd(same ascwd)

Change working directory (POSIX) orremove partial qualifier (DMS)

+ +

xmkd Make directory - + mkdir (a)

xpwd Show current working directory + + pwd (a)

xrmd Remove directory - + rmdir (a)

(1) On the BS2000/OSD server, cdup and xcup achieve the function "Change workingdirectory" by removing a partial qualifier.

Servercommand


(DMS) (POSIX)



U41096-J-Z125-2-76 17

FTP FTP server

BS2000/OSD-specific functions of the FTP server

The following table provides an overview of the BS2000/OSD-specific functions of the FTPserver.

Key:

+ The function is implemented.(+) The function is implemented as a dummy function.

It is recommended that BS2000/OSD-specific FTP server functions always be called withthe prefix site, although these functions can still also be used for compatibility reasons at themoment with the file, ftyp, modc and setc commands without a preceding site.

However, it is strongly recommended, particularly when creating procedures, to use thecurrent form with a preceding site to prevent problems that may arise if the FTP standard isextended.

If site is not followed by any of the commands listed in the table, site is interpreted in thesame way as site exec. The string following site is then forwarded as a command to theremote operating system and is interpreted as in earlier FTP server versions.

Servercommand


(DMS) (POSIX)


exec Forward command to remoteoperating system

+ +

file Change DMS file attribute + + file (k)

ftyp Change file editing type + + ftyp (k)

modc Modify character string for switchingbetween POSIX / DMS

+ + modchar (k)

setc Change code tables + + setcode (k)

sfil Enable/disable special EOF markerfor PAM files;Enable/disable filling of blank SAMrecords

+ (+) setfile (k)

exit Define parameters for exit routines + + rexit (a)

BS2000/OSD-specific FTP server functions

18 U41096-J-Z125-2-76

FTP server FTP

Calling the FTP server functions via the FTP partner client

For most FTP server functions, there is a corresponding command call on the partner client.If a function has no corresponding command call on the client, it can be called directly viathe FTP server with the aid of the client command quote (see “quote - call server functions”on page 90).

In the case of FTP clients that do not offer any special input options for an account number(e.g. web browser), the account number can be appended to the user ID separated by acomma on the BS2000/OSD FTP server.

There is no meaningful equivalent for the "Make directory" and "Remove directory"functions in the DMS file system on BS2000/OSD. As far as the POSIX file system onBS2000/OSD is concerned, these functions are implemented within the framework of thePOSIX support. The FTP client commands mkdir and rmdir can be used to create andremove directories in the POSIX file system.

Any server function of the partner system can always be called with the client commandquote.

The server functions file, ftyp, setc, modc, sfil and exit are described in detail below. Thesefunctions exist only in the DMS file system on BS2000/OSD and must always be addressedvia the client command quote.

– The site exit function defines the parameter for the exit routines (see theinterNet Services Administrator’s Manual). The exit command can also be sent to theserver via the client command rexit (see page 96).Enter the following:

quote site exit receive:<recv-parm>

quote site exit send:<send-parm>

quote site exit receive:<recv-parm>!send:<send-parm>

e.g.: quote site exit receive:-C5!send:-D7quote site exit send:*NONE

– The site file function defines the file attributes of a DMS file to be transferred on theremote system (i.e. the system on which the FTP server is running). The site file functioncorresponds to the client command file and is described in detail on page 52.Enter the following:quote site file <remote-file,file-operand-list>e. g.: quote file file1,fcbtype=sam

U41096-J-Z125-2-76 19

FTP FTP server

– The site ftyp function defines whether the SAM files on the remote computer are to beprocessed as text or binary files The site ftyp function corresponds to the clientcommand ftyp and is described in detail on page 55.Enter the following:quote site ftyp <file-processing-type>e. g.: quote site ftyp binary

– The site modc function defines the first character in the string for switching between theDMS file system and the POSIX file system. The site modc function corresponds to theclient command modchar and is described in detail on page 79.Enter the following:quote site modc <character>e. g.: quote site modc $

– The site setc function is used to set the code tables for code conversion. The site setcfunction corresponds to the client command setcode and is described in detail on page101.Enter the following:quote site setc <EBCDIC-table> <ISO-table>e. g.: quote site setc EDF049 ISO88599

– The site sfil function defines special modes of operation for transferring files and corre-sponds to the client command setfile, which is described in detail on page 102.Enter the following:

quote site sfil datend on|offEnable/disable the special EOF marker (default: enabled).

quote site pademptyrec on|offEnable/disable filling of blank SAM records (default: disabled).

e.g.: quote site sfil datend offquote site sfil pademptyrec on

20 U41096-J-Z125-2-76

FTP server FTP

FTP server commands, which support the restart capability of the FTP client

The following FTP server commands support the restart capability of the FTP client andFTP server:

– mdtm– size– rest

mdtm - Establish the date and time of the last file change to date

The mdtm command provides the date and time of the last change to a file to date:

Message: 213 <YYYYMMDDhhmmss>

<file>File for which the mdtm command supplies the date and time of the last change.

Example

quote mdtm test file 213 20001015204331

size - Establish the size of a file

The size command specifies how many bytes were transferred via the network when this filewas transferred. The current settings for mode, type, struct and ftyp are taken into accounthere. The size command is rejected with an error code for mode <> stream.

Message: 213 <size of file (in bytes)>

<file>File for which the size command supplies the size.

mdtm

<file>

size

<file>

U41096-J-Z125-2-76 21

FTP FTP server

Example

quote size test file 213 498665

rest- Specify file position where a data transfer should begin

The rest command specifies any byte position at whose corresponding file position (insteadof file start) a file transfer initiated by a subsequent stor or recv command should begin.

<position>Byte position at whose corresponding file position the next file transfer should begin.

FTAC interface

The advantages of the FTP client lie in the fact that it is standardized and hence widelyused. When seen from a security aspect, however, it is not up to the usual standardsprevalent in BS2000/OSD. In other words, anyone who knows your login-specific data canretrieve data from your user ID, save data to your user ID, delete data and even change fileattributes.For this reason, interNet Services offers access to the FTAC interface for FTP. Accesscontrol and protection via openFT-AC has already been available for the File Transfer openFTsince quite some time.

The following features are offered by FTAC to protect the BS2000/OSD server:

– Decoupling of FTP transfer admissions and login admissions

– Access rights depending on partner systems

– User-specific access rights

– Flexible levels of access rights

– Logging of every authorization check

– Simple application

More detailed information on the FTAC support for FTP can be found in the chapter “FTACinterface” (see page 121).

rest

<position>

22 U41096-J-Z125-2-76

SNMP subagent for FTP FTP

3.2 SNMP subagent for FTP

The FTP server has its own subagent (FTP subagent), which is operated via a managementapplication, the BCAM Manager.

The "SNMP Management for openNet Server and interNet Services" manual contains infor-mation on the following topics:

– Handling the BCAM Manager– Software requirements– Installation and deinstallation– Starting up and shutting down the FTP subagent

Interaction between the FTP subagent and FTP server

The FTP server accesses the FTP subagent via the fixed port number 3237. Immediatelyafter starting up, the FTP server reports to the FTP subagent, provided this subagent is alsostarted, and provides it with the following information:

– Port number, under which the FTP subagent can access the FTP server– Server port number for the control connection to the FTP clients

Assuming a server entity with this server port number does not already exist, the FTPserver creates the relevant server entry.

Each FTP server writes its two port numbers to the SYSDAT.TCP-IP-AP.040.SNMP file atstartup. If the FTP subagent is only started subsequently, it can check theSYSDAT.TCP-IP-AP.040.SNMP file for the currently active FTP server and create therelevant data structures.

If the FTP server is terminated, it deletes its entry from the SYSDAT.TCP-IP-AP.040.SNMPfile.

U41096-J-Z125-2-76 23

FTP FTP client

3.3 FTP client in BS2000/OSD

Within BS2000/OSD, each FTP user opens his or her own FTP client task. By using theopen command, the client establishes a link to the required FTP server on the remote host.

FTP clients in BS2000/OSD

UNIX computer MS-DOS computer

FTPserver

FTPserver

FTPclient

FTPclient

FTPclient

network

local network

BS2000 computer

24 U41096-J-Z125-2-76

FTP client FTP

Starting and terminating the client

The FTP client is started by any of the following calls:

– START-FTP or FTP

– EXEC $TSOS.FTP

– START-PROGRAM ($TSOS.SYSLNK.TCP-IP-AP.040,FTP,RUN-MODE=A,PROG-MODE=ANY)

or for SR2000:

– START-PROGRAM ($TSOS.SRMLNK.TCP-IP-AP.040,FTP,RUN-MODE=A,PROG-MODE=ANY)

– EXEC $TSOS.FTP

The commands for terminating the FTP client are quit or bye.

Opening and closing a connection

Before any operation that (also) affects a remote host can be executed, a connection mustbe set up. This is done by using the open command. If an access protection mechanismexists on the remote host, FTP will first request the required entries. In BS2000/OSD, thetransfer admission (i.e. the access authorization) typically consists of the values for the userID, password and account number. These values are system-dependent, as can be seen inthe following table.

U41096-J-Z125-2-76 25

FTP FTP client

If the partner is an FTAC-protected BS2000/OSD system, the transfer admission must bespecified in accordance with the FTAC setting

The connection to the remote host can be cleared with the close command.

In interactive mode, FTP responds with a version number and the input prompt ftp>. If theauthorization entries following the open command are invalid, the connection to the remotehost is kept open, provided the task switch 1 is not set. The correct entries can then bemade via the user command. Setting task switch 1 enables a SPIN-OFF mechanism (seeFTP client commands jobvar and svar above). If the entries passed to the access protectionmechanism are invalid, the FTP client is terminated. Prompting is enabled automatically onstarting FTP in interactive mode and can be disabled with the prompt command.

In batch mode, after the open command, the authorization entries (user ID, password,account number) must be specified individually on continuation lines if they are required bythe remote host. If these entries are invalid, the FTP client terminates. In batch mode,commands are read with RDATA and must be entered in lowercase letters. Prompting isdisabled on starting FTP in batch mode.

Note that task switch 1 must be set for batch mode.

System Login name Account number Password

BS2000/OSDwithout FTACprotection

1 - 8 alphanumericcharacters

1 - 8 alphanumericcharacters

C string, 1 - 8 characters longorX string, 1 - 16 characters long

BS2000/OSDwith FTACprotection

$FTAC or relevantstring defined for serverinstallation


UNIX 1 - 32 characters UNIX does notrecognize anyaccount numberslocally

Alphanumeric characters (thelength is system dependent); adistinction is made betweenuppercase and lowercase

Windows 1 - 36 characters Windows does notrecognize anyaccount numberslocally


MVS 1 - 7 alphanumericcharacters

Max. 40 charactersincluding uppercaseletters, digits andspecial characters$, @, #

1 - 8 alphanumeric characters

i

26 U41096-J-Z125-2-76

FTP client FTP

The following commands return current information on the client and server settings,command states and on trace and debug settings:

Directories

After a connection has been successfully established, a working directory is defined on thelocal host as well as the remote host. If desired, you can obtain information on the currentlocal and remote working directories with lpwd and pwd, respectively. Existing files inthe local working directory can be listed with the command ldir or lls, and files in the remoteworking directory can be listed with dir or ls. When files are not identified by their full pathnames in commands, they are considered to be relative to the currently set workingdirectory.

Local file names must comply with the conventions of the local host, and remote file namesmust comply with the conventions of the remote host. Special attention must be paid to theuse of uppercase and lowercase characters.

Command Function Page

open Open connection to a remote host 84

close Close connection to the remote host 46

! Switch to BS2000/OSD command mode 119

bye Exit FTP 42

quit = bye 89

Commands to control FTP


help Display summary information on FTP commands 61

? = help 118

status Display FTP STATUS information 104

remotehelp Display information on functions of the remote FTP server 93

debug Enable/disable DEBUG output 47

trace Enable/disable TRACE output 111

verbose Enable/disable server responses 116

system Display information on FTP server 109

General information on FTP

U41096-J-Z125-2-76 27

FTP FTP client

BS2000/OSD can optionally work with two different file systems: the proprietary DMS filesystem and the POSIX file system (based on UNIX). In BS2000/OSD, directories areemulated by addressing groups of files using partial qualifiers. The complete or absolutepath in BS2000/OSD corresponds to the fully-qualified file name(e.g.:CATID:$USERID.FILENAME). The lpwd command can be used to check which filesystem is currently enabled on the local host. Setting the working directory enables you toswitch between the DMS file system and the POSIX file system.

In order to access files in either the DMS or POSIX file system, you must be in thecurrent working directory of the corresponding file system. It is not possibleto access POSIX files from within the DMS file system, or vice versa. This principlemust be observed for all FTP commands and functions.

Some operating systems (e.g. UNIX, MS-DOS) recognize a hierarchically organizedsystem of directories.The structure of the POSIX file system corresponds to that of theUNIX file system (UFS), i.e. is organized in a hierarchy. In the DMS file system, directoriesare emulated by addressing groups of files using partial qualifiers.


ldir Information on local file(s) 66

lpwd Output local working directory 68

lls List names of files on local host 67

Information on local files and directories


dir Information on remote file(s) 49

mdir Information on remote file names in multiple directories on theremote host

97

ls List names of files on remote host 69

mls List names of files in in multiple directories on the remote host 77

pwd Output remote working directory 88

Information on remote files and directories

i

28 U41096-J-Z125-2-76

FTP client FTP

Example

:5:$TCPTEST.AAA.FILE1:5:$TCPTEST.AAA.FILE2:5:$TCPTEST.AAA.BBB.FILE3:5:$TCPTEST.AAA.BBB.FILE4:5:$TCPTEST.AAA.CCC.FILE5:5:$TCPTEST.DDD.FILE6:5:$TCPTEST.FILE7

Here :5:$TCPTEST is the main directory containing all files. AAA and DDD are subdirectoriesof the main directory. BBB and CCC are subdirectories of AAA. The part of the filespecification consisting of the directory names is designated as the path name (forexample, :5:$TCPTEST.AAA.BBB is the path name for the files FILE3 and FILE4).

Switching between the DMS and POSIX file systems

Switching from the DMS to the POSIX file system, or vice versa, is achieved by entering thecharacter string that was set for this purpose. Note that the entry is case-sensitive.

The default string is:

%POSIX to switch to the POSIX file system%BS2000 to switch to the DMS file system

The first character in this string (% character) can be changed for the local system with theclient command modchar and for the remote system with the server function site modc. Thereis no separate client command for the server function site modc, so site modc has to beinvoked with the client command quote.

The client command for changing the file system is either lcd or cd, depending on whetheryou are in the local or remote working directory. For example, the command for switching tothe POSIX file system on the local computer is lcd %POSIX.

A switch always takes you to the HOME directory of the target file system. In the POSIX filesystem, the system administrator defines the name of the HOME directory, whereas in theDMS file system, it corresponds to :CATID:$USERID.

U41096-J-Z125-2-76 29

FTP FTP client

The following file management commands are available for local and remote filesand directories:

Metacharacters in file names

File names for local and remote files are operands in many FTP commands. In somecommands, the file name must designate only one file; in other cases, you may also specifyfile groups by entering metacharacters (e.g. * and ?).

The syntax and semantics of metacharacters are not standardized and depend on thespecial implementation. Since special implementations are, for the most part, supported byexisting operating system calls, the permitted metacharacters are identical to thosegenerally allowed in the operating system. In most situations, the FTP server determineswhether and which metacharacters are allowed, though this can also be done by the FTPclient in some cases. The following table contains an overview of the metacharactersallowed in the BS2000/OSD, UNIX and MS-DOS operating systems.


lcd Change local working directory 64

Modifying local files and directories


mkdir Create a remote working directory 76

rmdir Remove a remote working directory 73

cd Change remote working directory 43

delete Delete remote file 48

mdelete Delete multiple remote files 71

rename Rename remote file 94

cdup Change to the next higher directory (one level up) 45

Modifying remote files and directories

30 U41096-J-Z125-2-76

FTP client FTP

Backslash

Since the FTP client in BS2000/OSD strips single backslashes, any backslash thatis to be used as a directory separator, for example, must be entered twice insuccession.

File passwords

In BS2000/OSD, individual DMS files may also be protected by file passwords. TheBS2000/OSD FTP server expects function calls with file names in the form:

<filename>,C'<password>' or <filename>,X'<password>'.

This does not apply to the DMS file system.

Example

Overwrite the BS2000/OSD file ANTON protected by the read password OTTO from withinUNIX with the file name ZWATON:

put ZWATON ANTON,C'OTTO'

Function BS2000/OSD UNIX MS-DOS

DMS POSIX

Match any string (including the null string) * * * *

Match exactly one character / Noequivalent

? ?

Match the listed strings <s1,...> Noequivalent

Noequivalent

Noequivalent

Match a string that lies between stringss1 and s2 in lexical order

<s1:s2> Noequivalent

[s1-s2] (*) Noequivalent

Exclude the corresponding files -s1(only at thebeginning ofthe string)

Noequivalent

Noequivalent

Noequivalent

Metacharacters in file names(*) only single characters are permitted

i

U41096-J-Z125-2-76 31

FTP FTP client

File conversion on transfer

When transferring files from one operating system to another using FTP, two viewpointsneed to be taken into account:

– Different operating systems recognize and accept different file types. For example,BS2000/OSD recognizes SAM, ISAM and PAM files; UNIX and MS-DOS recognizeonly unstructured files.

– Different operating systems use different codes to represent characters. For example,BS2000/OSD encodes characters in EBCDIC; UNIX and MS-DOS use ASCII.

If XHCS is used, it is possible to switch between any of several ASCII/EBCDIC codeconversions. The client command for switching conversion modes is setcode. The corre-sponding server command is quote site setc (see page 90).

The type of transfer influences the conversion of file types and codes. The following applieslocally for a BS2000/OSD FTP client:

– When the transfer type is ASCII (default value), code conversion takes place fromEBCDIC to ASCII (send) or vice versa (receive). It is possible to read SAM files, ISAMfiles (without key) and PAM files (without PAMKEY). By default, a SAM file with avariable record length is generated, but this default can be changed with a command.

– When the transfer type is BINARY, no code conversion occurs. It is possible to readSAM files, ISAM files (without key) and PAM files (without PAMKEY). A PAM fileis generated by default, but this default can also be changed with a command.

– When the transfer type is EBCDIC, no code conversion occurs. It is possible to readSAM files, ISAM files (without key) and PAM files (without PAMKEY). A SAM file with avariable record length is generated.

In addition, file attributes and the processing type can be modified by using the quote site fileor quote site ftyp commands:

– quote site file:The file attributes for a file to be created can be preset by defining whether a PAM fileor SAM file is to be created. All file attributes supported by C (BS2000/OSD) forSTREAM I/O are also supported here.

32 U41096-J-Z125-2-76

FTP client FTP

– quote site ftyp:The processing type when writing a SAM file can also be preset. The processing typedetermines whether the files are to be processed as text files (i.e. organized in recordsor lines) or as binary files (stream of bytes) when they are written.

– PAMKEYs are not transferred. This means that it is not possible to interchangeexecutable files between two BS2000/OSD computers. This restriction can beovercome by packaging executable files in PLAM libraries.

– ISAM files lose their ISAM keys on transfer and must hence also be alwayspackaged in PLAM libraries before being transmitted.


user Specify user ID for remote host 114

ascii Initiate ASCII transfer type 39

binary Initiate BINARY transfer type 41

file Change DMS file attributes 52

ftyp Change or query DMS file processing type 55

modchar Modify string for switching between BS2000/OSD andPOSIX file systems

79

setcode Change code tables 101

setfile Enable/disable usage of special EOF markers and filling ofdummy records with blanks

102

tenex = binary 110

type Change or query transfer type 112

mode Change or query transfer mode 81

struct Change or query transfer structure 105

form Change or query transfer format 54

runique Set unique target file name on overwriting with get 98

sunique Set unique target file name on overwriting with put 106

Commands to control data transmission

i

U41096-J-Z125-2-76 33

FTP FTP client

Transferring files

The actual file transfer can be initiated for one or more files, regardless of the direction oftransfer. When transferring multiple files interactively, the prompt command can be used tocontrol whether or not confirmation is required for each individual file.

An abort of the file transfer initiated by the client is implemented by the FTP server via theserver command abor. In such cases, the BS2000/OSD FTP server reports a successfulabort with the messages below. Note, however, that this abort will not function if the FTPaccess occurs via FTAC.

226 Abort successful426 Transfer aborted. Data connection closed.

The FTP client in BS2000/OSD recognizes a user´s intention to abort a file transfer bypressing the K2 key. If the K2 key is pressed repeatedly, it will no longer be possible to returnto FTP.

Forwarding commands

Functions that have been implemented on the FTP server of the remote host and for whichthere are no corresponding calls on the own FTP client can be initiated directly by using thequote command. The required parameters are passed transparently, without any validationon the FTP client The remotehelp command can be used to determine which functions havebeen implemented on the FTP server of the remote host.


append Append a local file to a remote file 38

get Fetch a file 57

recv = get 91

mget Fetch multiple remote files 74

reget Fetch a file after a transfer abort 92

put Send a local file 87

send = put 99

mput Send multiple local files 82

reput Send a local file after a transfer abort 95

File transfers

34 U41096-J-Z125-2-76

FTP client FTP

One possible server function that must be initiated by using quote is site exec. In theBS2000/OSD implementation, site exec permits commands to be forwarded to the operatingsystem of the remote computer. Note, however, that site exec cannot be used in combinationwith the FTAC functionality.

Restart capability of the FTP client

With the restart capability of the FTP client, aborted FTP transfers can be resumed at theposition in the target file at which the FTP transfer was interrupted. The restart capability ofthe FTP client is implemented with the FTP client command reget (see page 92) and reput(see page 95).

Batch capability of the FTP client

The FTP client can be used in (batch) procedures. The batch capability of the FTP clientallows the procedure to establish the command for which the error occurred. The faultycommand and the error description (local error message and response from FTP server)are stored in a preciously specified job variable and/or SDF-P variable so that the callingprocedure can respond suitably. The batch capability is supported by the FTP clientcommands jobvar (see page 62) and svar (see page 107).


bell Enable/disable bell 40

hash Enable/disable transfer progress indicator 60

quote Transfer parameters to the remote FTP server 90

glob Enable/disable expansion of metacharacters 59

prompt Enable/disable prompting 86

sendport Enable/disable port command 100

settime Set timeout value for server responses 103

exit Define parameters for local exit routines 51

rexit Define parameters for remote exit routines 96

jobvar Enable/disable usage of a job variable 62

svar Enable/disable usage of an S variable (SDF-P) 107

Other FTP functions

U41096-J-Z125-2-76 35

FTP FTP client

Example of an FTP session between a PC and BS2000/OSD

"Connect" sets up the connection to BS2000/OSD.

36 U41096-J-Z125-2-76

FTP client FTP

3. The filename, which must comply with the windows conventions, is specified and marked with "ok". The file is transferred to the desired directory.

2. Inserting the mark "←" and simultaneously pressing the shift key causes the "Input" window to be opened.

1. The file to be transferred is marked.

U41096-J-Z125-2-76 37

FTP FTP client

3.4 Overview of commands (FTP client)

FTP commands may be abbreviated up to the point required for unique identification.Operands are separated by spaces.

If file names occur as operands in commands, they may be specified in full (full path name).If only a relative file name is specified, the file name is extended to include the currently setworking directory.

The following section describes the commands in alphabetical order.

38 U41096-J-Z125-2-76

append FTP

append - append a local file to a remote file

The append command transfers a file from a local host to a remote host and appends it to afile on the remote host that may already exist. In the case of DMS files of the file type SAM,the processing type can be influenced with the ftyp command.

<local-file>Name of a POSIX or DMS file on the local host that is to be transferred to the remotehost. Metacharacters are not allowed.

<remote-file>Name of a file on the remote host (metacharacters are not allowed). If the file alreadyexists, the local file is appended to it. If the file does not exist, a new file is created.If the remote-file operand is omitted, the name of the local file is used (in this case thename of the local file must correspond to the file naming conventions of the remotehost). Uppercase letters in local file names are converted into lowercase. If the remotehost is a BS2000/OSD system, the server converts lowercase characters back intouppercase.

Example

The file :5:$TCPTEST.MAN.FTP.C is transferred from the local host to the remoteBS2000/OSD host, where it is appended to the file :110:$TSOS.FTP.2. The FTP serverfunction PORT is called implicitly.

→ lpwdLocal directory is :5:$TCPTEST.MAN.

→ pwd257 ":110:$TSOS." is current directory.

→ append ftp.c ftp.2200 PORT command successful.150 Opening data connection for :110:$TSOS.FTP.2(195.1.5.3,4102).226 Transfer complete.22561 bytes sent in 0.13 seconds (160.82 Kbytes/s)

append

<local-file> [<remote-file>]

U41096-J-Z125-2-76 39

FTP ascii

ascii - set transfer type to ASCII

The ascii command sets the transfer type to ASCII. This type of transfer should always bechosen when transferring text files. On starting FTP, ASCII is set as the default value for thetransfer type.

The transfer type can also be changed by using the binary, tenex and type commands. Thecurrently set transfer type can be determined with the status and type commands. Thetransfer type is described in more detail on page 31.

1. The current transfer type is queried.

→ typeUsing binary mode to transfer files.

2. The transfer type is changed from BINARY to ASCII.

→ ascii200 Type set to A.

3. In response to the status query, the transfer type is shown as ascii.

→ statusConnected to systemd, port 21. Mode: stream; Type: ascii; Form: non-print; Structure: fileFtyp: textbin Verbose: on; Bell: off; Prompting: on; Globbing: on Filesystem is: BS2000 The character to change the filesystem is: % ISO-codetable is ISO88591, EBCDIC-codetable is EDF041 Time limit for server responses: 30 secs Store unique: off; Receive unique: off Use special EOF marker (C-DATEIENDE): on Pad empty record with blank: off Used job variable: *NONE Used SDF-P variable: *NONE Used receive selector: *NONE Used send selector: *NONE Hash mark printing: off; Use of PORT cmds: on

ascii

40 U41096-J-Z125-2-76

bell FTP

bell - enable/disable bell

The bell command has no effect in the BS2000/OSD implementation and is only includedfor compatibility reasons.

bell

U41096-J-Z125-2-76 41

FTP binary

binary - set transfer type to BINARY

The binary command sets the transfer type to BINARY. This type of transfer should alwaysbe chosen when transferring binary files. On starting FTP, ASCII is set as the default valuefor the transfer type.

The transfer type can also be changed by using the binary, tenex and type commands. Thecurrently set transfer type can be determined with the status and type commands. Thetransfer type is described in more detail on page 31.

Example

1. The current transfer type is queried.

→ type Using ascii mode to transfer files.

2. The transfer type is changed from ASCII to BINARY.

→ binary 200 Type set to I.

3. A PAM file is transferred. The FTP server function PORT is called implicitly.

→ put pamela 200 PORT command successful. 150 Opening data connection for :5:$TCPTEST.PAMELA (89.16.100.0,1164). 226 Transfer complete. 2048 bytes sent in 0.24 seconds (8.06 Kbytes/s)

4. The new transfer type is queried.

→ typeUsing binary mode to transfer files.

binary

42 U41096-J-Z125-2-76

bye FTP

bye - exit FTP

The bye command terminates the FTP program. If a connection to a remote host is stillopen, it is cleared (implicit close).The quit command can be entered as a synonym for bye.

Example

→ bye221 Goodbye.

bye

U41096-J-Z125-2-76 43

FTP cd

cd - change remote working directory

The cd command changes the current working directory on the remote host. If a connectionhas been set up to a BS2000/OSD FTP server, the cd command can be used to switchbetween the DMS and POSIX file system if a POSIX file system is available on the remotehost (see page 28). The current remote working directory can be determined using the pwdcommand. Changing the file system always takes you to the HOME directory.

.The remote directory is not changed (only provided for reasons of compatibility withother implementations).

..The last partial qualifier (on the extreme right) is removed from the name of the remoteworking directory in the DMS file system.In the POSIX file system, the directory is changed to the next higher level.

<remote-directory>Name of the new working directory.

%BS2000Change to the DMS HOME directory. If you are already in the DMS file system, the%BS2000 specification is synonymous with $HOME.

$HOMEChange to the DMS HOME directory. In order to specify $HOME, you must already bein a DMS directory.

%POSIXChange to the POSIX HOME directory.

Example

The remote host is a BS2000/OSD host with a POSIX directory.

1. Query the remote working directory.

→ pwd 257 "/home/usr/tcptest" is current directory.

cd

. | .. | <remote directory> | %BS2000 | $HOME | %POSIX

44 U41096-J-Z125-2-76

cd FTP

2. Change the working directory by adding the suffixman/sam/nach.bs2000.

→ cd man/sam/nach.bs2000 200 "/home/usr/tcptest/man/sam/nach.bs2000" is current directory now.

3. Query the new working directory.

→ pwd 257 "/home/usr/tcptest/man/sam/nach.bs2000" is current directory.

4. Change to the DMS directory.

→ cd %BS2000200 :4:$TEST is current directory now.

U41096-J-Z125-2-76 45

FTP cdup

cdup - change to next higher directory (one level up)

The cdup command changes the current working directory to the next higher directory onthe remote host. This can alternatively also be achieved by specifying the command cd .. .

cdup

46 U41096-J-Z125-2-76

close FTP

close - close connection to remote host

The close command clears the connection to the remote host.

Example

1. The status query shows that a connection to the host systemd exists.

→ statusConnected to systemd, port 21. Mode: stream; Type: ascii; Form: non-print; Structure: fileFtyp: textbin Verbose: on; Bell: off; Prompting: on; Globbing: on Filesystem is: BS2000 The character to change the filesystem is: % ISO-codetable is ISO88591, EBCDIC-codetable is EDF041 Time limit for server responses: 30 secs Store unique: off; Receive unique: off Use special EOF marker (C-DATEIENDE): on Pad empty record with blank: off Used job variable: *NONE Used SDF-P variable: *NONE Used receive selector: *NONE Used send selector: *NONE Hash mark printing: off; Use of PORT cmds: on

2. The close command clears the connection.

→ close221 Goodbye.

close

U41096-J-Z125-2-76 47

FTP debug

debug - enable/disable DEBUG output

DEBUG output is primarily used by network administrators and support staff to diagnoseproblems on the network. Users do not usually require DEBUG output.

<debug-value>Values in the range 0 through 9 are permitted.

0 No DEBUG output

1 All messages from the FTP client to the FTP server and from the FTP serverto the FTP client are output.

In addition to 1:

2 Information on file access is output.

If no operand is specified, the DEBUG output switch is toggled, i.e. if the DEBUG outputwas enabled, it is now disabled, and if it was disabled, it is now enabled. Valuesgreater than 2 are treated in the same way as 2.

debug

<debug-value>

48 U41096-J-Z125-2-76

delete FTP

delete - delete a remote file

The delete command is used to delete a file on the remote host. Partially qualified files onthe remote host can be deleted with the mdelete command.

<remote-file>Name of the file on the remote host to be deleted.

Example

1. The remote working directory is displayed.

→ pwd257 ":110:$TSOS." is current directory.

2. The file anton is deleted.

→ delete anton200 DELE command okay.

delete

<remote-file>

U41096-J-Z125-2-76 49

FTP dir

dir - show information on remote file(s)

The dir command returns information about files on the remote host. Details on remote filescan also be obtained with the mdir, ls and mls commands.

<remote-file>Name of a file on the remote host. If this operand is omitted, a list of all files in thecurrent working directory of the remote host is returned.

<local-file>Name of a local file to which the output from the command is to be written. If thisoperand is not specified, the output is sent to the terminal.

If the connection to the partner was set up via an FTAC profile, the file informationis only output relatively to the path name set in this profile.

Example

The remote host is a UNIX system.

1. The local and remote working directories are queried.


→ pwd257 "/usr/tcptest/man/sam/nach.bs2000" is current directory.

dir

[<remote-file>] [<local-file>]]

i

50 U41096-J-Z125-2-76

dir FTP

2. The files in the remote working directory are queried. The FTP server function PORT iscalled implicitly.

→ dir200 PORT command successful.150 ASCII data connection for /bin/ls (89.16.100.0,1182). (0 bytes)-rw-rw-r-- 1 tcptest 229 Sep 7 12:55 anton.1 -rw-rw-r-- 1 tcptest 229 Sep 7 12:55 anton.2 -rw-rw-r-- 1 tcptest 229 Sep 7 12:55 anton.3 -rwx------ 1 tcptest 10505 Sep 5 18:35 berta -rw-rw-r-- 1 tcptest 229 Sep 7 12:55 berta.1 -rw-rw-r-- 1 tcptest 229 Sep 7 12:55 berta.2 -rwx------ 1 tcptest 10505 Sep 5 18:19 caesar -rw-rw-r-- 1 tcptest 229 Sep 7 12:55 zwaton 226 ASCII Transfer complete. 461 bytes received in 2.54 seconds (1.58E-01 Kbytes/s)

3. Information on the remote files anton.* is written to the local file anton.prot.

→ dir anton.* anton.prot 200 PORT command okay. 150 ASCII data connection for /bin/ls (89.16.100.0,1183). 226 Transfer complete.38 bytes received in 0.04 seconds (7.57E-01 Kbytes/s)

U41096-J-Z125-2-76 51

FTP exit

exit - define parameters for local exit routine

You can set exit routines for the FTP client with the exit command.

You will find further details on the FTP exit routines in the interNet Services Administrator’sGuide.

<receive-selector><receive-selector> allows you to select the required action from several actionsavailable when receiving data. For this purpose, you supply the exit routine with a stringto which <receive-selector> points. You can decide freely the meanings that are to beattached to the individual strings. Only the strings "*" and "*NONE" have a fixedmeaning:

– If you specify "*" for <receive-selector>, the entry YAPFEXIT is selected but withoutthe more precise specification of <receive-selector>. The general FTP serversetting then applies with the -U option.

– If you specify "*NONE", the exit routine is disabled.

If you do not specify <receive-selector>, no exit routine is selected.

<send-selector><send-selector> allows you to select the required action from several actions availablewhen sending data. For this purpose, you supply the exit routine with a string to which<send-selector> points. You can decide freely the meanings that are to be attached tothe individual strings. Only the strings "*" and "*NONE" have a fixed meaning:

– If you specify "*" for <send-selector>, the entry YAPFEXIT is selected but without themore precise specification of <send-selector>. The general FTP server setting thenapplies with the -U option.


If you do not specify <send-selector>, no exit routine is selected.

exit

[receive:<receive-selector>] [!] [send:<send-selector>]

52 U41096-J-Z125-2-76

file FTP

file - define file attributes on local host

The file command specifies the file attributes of a file to be transferred from the local host.file is mapped to the BS2000/OSD FILE command. If preceded by the quote site command,this command can also be issued at the FTP server (see page 17).

<local-file>Name of the local file whose attributes are to be specified. Either a fully-qualified filename permitted in the FILE command or the "*" character must be used.

<file-operand-list>The possible operands are listed in the appropriate BS2000/OSD manuals.If a file name is specified for local-file, the file command applies only to the nextget, mget, reget or recv command that references the file name.If "*" is specified for local-file, the file command applies only to the next get, recv, reget ormget command. The file attributes are then applied to the local file name given in the get,reget, recv or mget command.

If several file commands are entered, only the entries for the last file command apply.

If no file command is specified and if the file does not exist, the usual defaultsapply, i.e.:

– For transfer type ascii (see the type or ascii command), SAM files with a variablerecord length are generated.

– For transfer type binary (see the type or binary command), PAM files aregenerated.

– If the file already exists, the attributes are taken from the catalog entry, and thefile is overwritten.

– The LINK operand must not be included in the file-operand-list, since a link nameis added automatically.

file

<local-file> <, file-operand-list>

i

U41096-J-Z125-2-76 53

FTP file

Restrictions

Only those file attributes also supported by C-RTS V2.0 for STREAM I/O (see the"C library functions for POSIX applications" manual) are supported here.

For ISAM files, only the settings KEYPOS=5 and KEYLEN=8 are supported for the keyposition and key length, respectively.

Record keys are not transmitted when ISAM files are transferred with the put command. Therecform operand is ignored. Consequently, ISAM files can only be read.

Example

1. The transfer type is set to binary.

→ type binary200 Type set to I.

2. A file command is issued for file1.

→ file file1,fcbtype=sam

3. The file file1 is created as a SAM file.

→ get file2 file1

54 U41096-J-Z125-2-76

form FTP

form - change or query transfer format

The form command sets the transfer format or returns details on the current transfer format.The currently set transfer format can also be determined with the status command.

fileSets the transfer format to FILE.If no operand is specified, details on the current transfer format are output on thescreen.

The FTP standard provides for a number of different, optional transfer formats. Ofthese only the transfer format FILE is implemented in BS2000. The form commandis included here only for compatibility with other implementations of FTP.

form

[file]

i

U41096-J-Z125-2-76 55

FTP ftyp

ftyp - specify processing type for files on local host

The ftyp command defines whether SAM files on the local host are to be processed as textor binary files.

The ftyp command applies only to SAM files of the DMS file system. PAM files arestill treated as binary files, and ISAM files as text files. POSIX files are not affectedby this restriction.

If preceded by the quote site command, this command can also be issued at the FTP server(see page 17).

The default has changed since previous FTP versions, because the transfer cannotbe restarted with ftyp=text.

textSAM files on the local host are to be processed as text files.With this setting, tabs (X’05’ in EBCDIC) are converted to a corresponding number ofblanks when writing to a file (tab stops 1, 9, 17 ...), and newline characters (X’15’ inEBCDIC) cause a line feed (record change).When reading, newline characters (X’15’) are added to each record read (see the "Clibrary functions for POSIX applications" manual).

binarySAM files on the local host are to be processed as binary files.With this setting, data is transferred unchanged when writing to a file. No conversion oftabs (X’05’) and newline characters (X’15’) occurs. When reading, no newlinecharacters (X’15’) are added.This setting enables SAM files of fixed, variable and undefined record lengthsto be written and read.For records of fixed length, the last record is padded with binary zeros (if necessary).If this is not desirable, variable length records should be used.

textbinSAM files on the local host are to be processed as binary text files.With this setting, tabs (X’05’ in EBCDIC) are not converted to blanks when writing to afile, but newline characters (X’15’ in EBCDIC) do result in a line feed (record change).When reading, a new line character (X’15’) is added to each record read.This setting is defined after FTP is started.

ftyp

text | binary | textbin

i

i

56 U41096-J-Z125-2-76

ftyp FTP

Example

1. The file processing type is set to binary.

→ ftyp binaryftyp set to binary.

2. The file file1 is created without conversion of the tab and newline characters.

→ get file2 file1

U41096-J-Z125-2-76 57

FTP get

get - fetch a file

The get command is used to transfer a file from the remote host to the local host. Files mayalso be transferred from the remote host to the local host with the commands mget and recv.A special variant of the get command, the reget command (see page 92), is now availablefor supporting restart functionality.

<remote-file>Name of a file on the remote host to be transferred to the local host.

<local-file>Name of a POSIX or DMS file on the local host. If the file already exists, it is overwrittenor, alternatively, a new file is created after adding an appropriate suffix. This behavior iscontrolled by runique. If the file does not exist, a new file is created.If the local-file operand is omitted, the name of the remote file is used (in this case, thename of the remote file must correspond to the file naming conventions on the localhost).

Example

The remote host is a UNIX host.

1. The names of the local and remote working directories are queried.

→ lpwdLocal directory is :5:$TCPTEST.MAN.VON.UNIX.

→ pwd257 /home/usr/man is current directory.

get

<remote-file> [<local-file>]

58 U41096-J-Z125-2-76

get FTP

2. The contents of the file anton (in the remote working directory) are transferred to a DMSfile of the same name (in the local working directory). The FTP server function PORT iscalled implicitly.

→ get anton200 PORT command okay. 150 ASCII data connection for anton (89.16.100.0,1189). 226 Transfer complete. 242 bytes received in 0.06 seconds (3.47 Kbytes/s)

3. The directory is changed to the POSIX HOME directory.

→ lcd %POSIXLocal directory now /home/usr

4. The remote file anton is transferred to the local host and stored in the POSIX file systemunder the name /home/usr/berta.

→ get anton berta200 PORT command okay. 150 ASCII data connection for anton (89.16.100.0,1190). 226 Transfer complete. 242 bytes received in 0.06 seconds (3.58 Kbytes/s)

U41096-J-Z125-2-76 59

FTP glob

glob - enable/disable expansion of metacharacters

The glob command enables or disables the expansion of metacharacters in local file names.On starting FTP, metacharacter expansion is enabled by default.

In the commands mget, mput, mdir, mls and mdelete, metacharacters may be specified in thelocal file names. If metacharacter expansion is enabled, the metacharacters are recognizedas such and evaluated in accordance with the rules. If metacharacter expansion is disabled,the metacharacters are not recognized as such and are interpreted as part of the file name.

Example

mget a*

If metacharacter expansion is disabled - as can be seen from the status off - FTP interpretsthe entry a* as a fully-qualified file name and issues the error message:

550 a* not a plain file or does not exist

glob

60 U41096-J-Z125-2-76

hash FTP

hash - enable/disable transfer progress indicator

The hash command enables or disables the indicator that shows the progress of a filetransfer. If the indicator is enabled, then after the transfer of each block, the # (hash)character is output on the screen.

On starting FTP, hash is disabled. When hash is enabled, the block length being used isoutput. If FTP is called in batch mode, i.e. if task switch 1 is set, then hash has no effect.

The current setting of hash can be determined with the status command.

Example

1. Query the names of local and remote working directories.

→ lpwd Local directory is :5:$TCPTEST.MAN.

→ pwd257 "/usr/tcptest/man/sam/from.bs2000" is current directory.

2. Enable the indicator. The FTP server function PORT is called implicitly with the appendcommand.

→ hashHash mark printing on (2048 bytes/hash mark).

→ append sam.to.sinix.anton.upd anton 200 PORT command okay. 150 Opening data connection for anton (89.16.100.0,1230).

3. Transfer of the file, with output of the # character after each block of 2048 bytes.

##################################################### 226 Transfer complete. 109089 bytes sent in 12.83 seconds (8.30 Kbytes/s)

hash

U41096-J-Z125-2-76 61

FTP help

help - show information on FTP commands

The help command displays a list of all FTP commands. Brief information is also availableon each of the commands.

The ? command also shows a list of all FTP commands. A list of all the functions of the FTPserver on the remote host can be obtained by using the remotehelp command.

<command>FTP command on which information is to be displayed.If no FTP command is specified, a list of all FTP commands is shown.

Example

1. Request a list of all FTP commands.

→ helpCommands may be abbreviated. Commands are:

! exit lpwd quit setfile? modchar ls quote settimeappend file mdelete recv status ascii form mdir reget struct bell ftyp mget remotehelp suniquebinary get mkdir rename svar bye glob mls reput system cd hash mode rexit tenex cdup help mput rmdir trace close jobvar open runique type delete lcd prompt send user debug ldir put sendport verbosedir lls pwd setcode

2. Request brief information on mget.

→ help mgetmget get multiple files

help

[ <command> ]

62 U41096-J-Z125-2-76

jobvar FTP

jobvar - store error information in a job variable

The jobvar command can be used to inform the FTP client as to whether the commandreturn information is to be stored in a job variable.

An alternative to the storage of error information is offered by the svar command (see page107).

If an error occurs when processing the jobvar command and if task switch 1 is set (batchoperation), the FTP client is terminated with TERMJ. The batch job or the procedure istherefore only continued after the next STEP instruction.

If the provision of a job variable is activated, the behavior of commands that execute severalindividual actions (commands mdir, mls, mget, mput, mdelete) changes. In the case of thesecommands, command processing is aborted after the first faulty action.

In contrast, the FTP client is not terminated in batch mode with TERMJ if the admission datain the open command is faulty.

The JV subsystem must be activated in order to use the jobvar command.

<jv-name>Name of job variable that is to supply the FTP client with the command return infor-mation after the jobvar command is issued. If the job variable <jv-name> does notalready exist, it is created.

*NONESpecification of *NONE causes a job variable to be no longer supplied with commandreturn information from the FTP client.

jobvar

< jv-name> | *NONE

U41096-J-Z125-2-76 63

FTP jobvar

Layout of job variables

Offset / Length Field Field description

0 / 3 Status indicator $S: Command executed successfully$E: Command has errors$T: FTP client ended normally$A: FTP client ended abnormally with errors

3 / 1 Filler Always "0"

4 / 4 TSN TSN of FTP client task

8 / 4 catid Supplied with spaces

12 / 4 Session number System sequence number

16 / 16 User command name Name of FTP client command

32 / 96 Command Parameter FTP command parameter

128 / 4 FTP protocol command Command sent from the client to the server

132 /124 FTP message Local message or server response

64 U41096-J-Z125-2-76

lcd FTP

lcd - change local working directory

The lcd command changes the current local working directory or the file system on the localhost. Changing the file system always takes you to the corresponding HOME directory. Thecurrent local working directory can be determined with the lpwd command. The remoteworking directory can be set with the cd command.

.The local working directory is not changed (included only for compatibility with otherimplementations).

..The last partial qualifier (on the extreme right) is removed from the name of the localworking directory in the DMS file system.In the POSIX file system, the directory is changed to the next higher level.

%POSIXChanges to the local POSIX HOME directory.

%BS2000Changes to the local DMS HOME directory. In the DMS file system, the %BS2000specification is synonymous with $HOME.

$HOMEChanges to the local DMS HOME directory. In order to specify $HOME, you mustalready be in a DMS directory.

<path>If a full path name (beginning with the specification of a catalog and/or user ID) isspecified in the DMS directory, the existing working directory is replaced. If thespecification of the catalog and the user ID are omitted, the old-name.path is set.

The path names are not validated in the DMS file system. In the POSIX file system,<path> may be an absolute or relative POSIX path name.

lcd

. | .. | %POSIX | %BS2000 | $HOME | <path>

U41096-J-Z125-2-76 65

FTP lcd

Example

1. Query the local working directory.

→ lpwd Local directory is :5:$TCPTEST.

2. Change the working directory by adding the partial qualifier MAN.

→ lcd man Local directory now :5:$TCPTEST.MAN.

3. Change to the POSIX HOME directory.

→ lcd %POSIX Local directory now /home/usr

4. Change the working directory to /home/usr/test.

→ lcd testLocal directory now /home/usr/test

5. Change to the DMS HOME directory.

→ lcd %BS2000 Local directory now :5:$TCPTEST.

6. Change the working directory by adding a partial qualifier.

→ lcd XXXLocal directory now :5:$TCPTEST.XXX.

7. Change the working directory by removing a partial qualifier.

→ lcd ..Local directory is :5:$TCPTEST.

66 U41096-J-Z125-2-76

ldir FTP

ldir - list information on local files

The ldir command returns information about files on the local host. Details on local files canalso be obtained by using the lls command.

<local-file>

ldir is mapped to the BS2000/OSD command FSTATUS in the DMS file system. <local-file> must be a fully or partially qualified file name permitted in the FSTATUS command.ldir is mapped to the ls -l command in the POSIX file system. <local-file> must be a legalfully or partially qualified file name.If no local file is specified, information on all files in the current working directoryis displayed.

<fstatus-operand-list>fstatus-operand-list represents any other operands permitted in the FSTATUS command.The FSTATUS command is described in the manual “User Commands (ISP Format)“.

Example



2. Display information on DMS files with the SAM file attribute in the working directory.

→ ldir ,fcbtype=sam0000003 :5:$TCPTEST.MAN.ANTON.PROT 0000003 :5:$TCPTEST.MAN.P.TRC 0000003 :5:$TCPTEST.MAN.P.USR 0000003 :5:$TCPTEST.MAN.SAM.NACH.MSDOS.ANTON.UPD 0000003 :5:$TCPTEST.MAN.SAM.NACH.MSDOS.BERTA.1 0000003 :5:$TCPTEST.MAN.SAM.NACH.SINIX.ANTON 0000006 :5:$TCPTEST.MAN.SAM.VON.SINIX.BERTA 0000003 :5:$TCPTEST.MAN.SAM.VON.SINIX.BERTA.1 0000003 :5:$TCPTEST.MAN.SAM.VON.SINIX.BERTA.2 0000006 :5:$TCPTEST.MAN.SAM.VON.SINIX.CAESAR :5: PUBLIC: 30 FILES. RES= 99, FREE= 51, REL= 0 PAGES

ldir

[<local-file>] [, <fstatus-operand-list>]

U41096-J-Z125-2-76 67

FTP lls

lls - list file names on local host

The lls command lists the file names on the local host.

<local-file>lls is mapped in the to the BS2000/OSD command FSTATUS in the DMS file system.<local-file> must be a fully or partially qualified file name that would be permitted in theFSTATUS command.In the POSIX file system, lls is mapped to the ls command. <local-file> must be a fullyor partially qualified file name.If no local file is specified, information on all files in the current working directoryis displayed.

<fstatus-operand-list>fstatus-operand-list represents any other operands permitted in the FSTATUS command.The FSTATUS command is described in the manual “User Commands (ISP Format)“.

Example

1. Query the local working directory (DMS file system).


2. Request a list of the DMS files in the local directory.

→ lls sam.nach.* SAM.NACH.MSDOS.ANTON.UPD SAM.NACH.MSDOS.BERTA.1 SAM.NACH.MSDOS.BERTA.2 SAM.NACH.SINIX.ANTON SAM.NACH.SINIX.BERTA.1 SAM.NACH.SINIX.BERTA.2 SAM.NACH.SINIX.CAESAR

lls

[<local-file>] [, <fstatus-operand-list>]]

68 U41096-J-Z125-2-76

lpwd FTP

lpwd - show local working directory

The lpwd command returns the name of the current local working directory. The localworking directory is set by means of the lcd command.

Example



2. Change the local working directory by adding the partial qualifier MAN.SAM.

→ lcd man.samLocal directory now :5:$TCPTEST.MAN.SAM.

→ lpwd Local directory is :5:$TCPTEST.MAN.SAM.

3. Change the working directory in the POSIX file system.

→ lcd %POSIXlocal directory now /home/usr/tcp.

→ lpwdlocal directory is /home/usr/tcp.

lpwd

U41096-J-Z125-2-76 69

FTP ls

ls - list file names on remote host

The ls command lists file names on the remote host. Information on remote files can alsobe obtained by using the dir, mdir and mls commands.

<remote-file>Name of a file on the remote host. If this operand is omitted, a list of all the files in thecurrent working directory of the remote host is returned.

<local-file>Name of the local file to which the output from the command is to be written. If thisoperand is not specified, the output is sent to the terminal.

Example


1. Query the name of the working directory.

→ pwd257 "/usr/tcptest" is current directory.

2. List the files in the working directory on the screen. The FTP server function PORT iscalled implicitly.

→ ls 200 PORT command okay. 150 ASCII data connection for /bin/ls (89.16.100.0,1179). FIL.files FIL.tools FTP TELNET TU man pool backup 226 Transfer complete.86 bytes received in 2.55 seconds (3.28E-02 Kbytes/s)

ls

[<remote-file>] [<local-file>]]

70 U41096-J-Z125-2-76

ls FTP

3. List the remote files designated by FIL.* and pipe the output to the local file fil.prot.

→ ls FIL.* fil.prot200 PORT command okay. 150 ASCII data connection for FIL.* (89.16.100.0,1180). 226 Transfer complete. 22 bytes received in 0.06 seconds (3.47E-01 Kbytes/s)

U41096-J-Z125-2-76 71

FTP mdelete

mdelete - delete multiple remote files

The mdelete command is used to delete files from the remote host. The prompting functionis enabled and disabled using the prompt command. The delete command can also be usedto delete files from the remote host.

<remote-file>Name of the file to be deleted from the remote host. Multiple file names may bespecified.If the prompting function is enabled, FTP checks before deleting each file whether thefile is really to be deleted.

Example


1. Query the name of the remote working directory.

→ pwd 257 "/usr/tcptest/man/sam/von.msdos" is current directory.

2. Delete the files anton.* and berta.*; the prompting function is enabled.

→ mdelete anton.* berta.* mdelete anton.2 (y/n/q)?

→ y 200 DELE command okay. mdelete anton.3 (y/n/q)?

→ n mdelete anton.upd (y/n/q)?

→ y 200 DELE command okay. mdelete berta.1 (y/n/q)?

→ y 200 DELE command okay. mdelete berta.2 (y/n/q)?

→ n

mdelete

<remote-file> [<remote-file>] [<remote-file>]

72 U41096-J-Z125-2-76

mdelete FTP

3. Disable the prompting function.

→ prompt Interactive mode off.

4. Delete the remaining files in the remote working directory; the prompting functionis disabled.

→ mdelete * 200 DELE command okay.

U41096-J-Z125-2-76 73

FTP mdir

mdir - show information on remote files

The mdir command returns information on files on the remote host. Details on remote filescan also be obtained by using the dir, ls and mls commands.

<remote-file>Name of a file on the remote host. Multiple file names may be specified in a single call.

<local-file>Name of the local file to which the output from the command is to be written.

-The information is to be displayed on the screen.If no operands are specified, they are requested interactively.

If the connection to the partner was set up via an FTAC profile, the file informationis only output relatively to the path name set in this profile.

Example




→ pwd257 "/usr/tcptest/man/sam/nach.bs2000" is current directory.

2. Output information on the remote files berta.* and anton.* to the local fileSEVERAL.PROT. The FTP server function PORT is called implicitly.

→ mdir berta.* anton.* several.prot 200 PORT command okay. 150 ASCII data connection for berta.* (89.16.100.0,1187). 226 Transfer complete. 100 bytes received in 0.71 seconds (1.36E-01 Kbytes/s) 200 PORT command okay. 150 ASCII data connection for anton.* (89.16.100.0,1188). 226 Transfer complete.150 bytes received in 1.64 seconds (8.90E-02 Kbytes/s)

mdir

[<remote-file>] [<remote-file>] [<remote-file>] ... - | <local-file>

i

74 U41096-J-Z125-2-76

mget FTP

mget - fetch multiple remote files

The mget command is used to transfer files from the remote host to the local host. Files canalso be transferred from the remote to the local host by using the get, reget and recvcommands.

<remote-file>Name of the file on the remote host to be transferred to the local host. Multiple filenames may be specified.The files are assigned the same names on the local host as they have on the remotehost. The file names must therefore comply with the rules for the local host as well aswith those of the remote host.If the prompting function is enabled, FTP requests confirmation before transferring eachfile.

Example


1. Query names of local and remote working directories.

→ lpwd Local directory is :5:$TCPTEST.MAN.SAM.VON.SINIX.

→ pwd 257 "/usr/tcptest/man/sam/nach.bs2000" is current directory.

2. All files from the remote working directory are transferred. The FTP server functionPORT is called implicitly. The prompting function is disabled in this example(see prompt).

mget

<remote-file> [<remote-file>] [<remote-file>] ...

U41096-J-Z125-2-76 75

FTP mget

→ mget * 200 PORT command okay. 150 ASCII data connection for anton (89.16.100.0,1192). 226 Transfer complete. 242 bytes received in 0.06 seconds (3.69 Kbytes/s) 200 PORT command okay. 150 ASCII data connection for anton.1 (89.16.100.0,1193). 226 Transfer complete. 242 bytes received in 0.06 seconds (3.75 Kbytes/s). .further transfers.200 PORT command okay. 150 ASCII data connection for caesar (89.16.100.0,1199). 226 Transfer complete. 10845 bytes received in 0.78 seconds (13.56 Kbytes/s)

76 U41096-J-Z125-2-76

mkdir FTP

mkdir - create a remote directory

The mkdir command is used to create a new directory on the remote host. This commandis not valid for the DMS file system.

<remote-directory>Fully qualified name of the directory on the remote host.

mkdir

<remote-directory>

U41096-J-Z125-2-76 77

FTP mls

mls - list file names in multiple directories on remote host

The mls command returns information on files on the remote host. Details on remote filescan also be obtained with the dir, mdir and ls commands.

<remote-file>Name of a file on the remote host. Multiple file names may be specified in a single call.

<local-file>Name of the local file to which the output from the command is to be written.

-The information is to be displayed on the screen.

If no operands are specified, they are requested in a dialog.

Example


1. The names of the local and remote working directories are queried.



mls

[<remote-file>] [<remote-file>] [<remote-file>] ... - | <local-file>

78 U41096-J-Z125-2-76

mls FTP

2. The files designated by berta, berta.* and anton.* are listed in the local file lists.prot. TheFTP server function PORT is called implicitly. The prompting function is disabled.

→ mls berta berta.* anton.* lists.prot200 PORT command okay. 150 ASCII data connection for berta (89.16.100.0,1184). 226 Transfer complete.6 bytes received in 0.05 seconds (9.93E-02 Kbytes/s) 200 PORT command okay. 150 ASCII data connection for berta (89.16.100.0,1185). 226 Transfer complete.16 bytes received in 0.21 seconds (7.37E-02 Kbytes/s) 200 PORT command okay.150 ASCII data connection for anton.* (89.16.100.0,1186). 226 Transfer complete.24 bytes received in 0.14 seconds (1.58E-01 Kbytes/s)

U41096-J-Z125-2-76 79

FTP modchar

modchar - modify character string

In order to switch between the local DMS file system and the local POSIX file system withthe lcd command, you need to specify a defined string (see page 64). If problems areencountered when using the standard strings %BS2000 and %POSIX (e.g. because aPOSIX directory of the same name exists), the first character of the string can be modifiedwithmodchar.

The current string can be queried with the status command.

The relevant setting can be made on a BS2000/OSD FTP server with the quote site modccommand (see page 17).

<character>Character to be substituted for the first character in the strings to switch between theDMS and POSIX file systems.

Example


→ lpwdLocal directory is :4:$TEST.

2. Switch from the DMS HOME directory to the POSIX HOME directory.

→ lcd %POSIX Local directory now /home/usr.

→ lpwdLocal directory is /home/usr.

3. The first character in the currently set string to switch between the DMS and POSIX filesystems is changed to #.

→ modchar #The prefix has been set to #.

4. Switch from the POSIX HOME directory to the DMS HOME directory.

→ lcd #BS2000

modchar

<character>

80 U41096-J-Z125-2-76

modchar FTP

Local directory now :4:$TEST.lpwdLocal directory is :4:$TEST.

U41096-J-Z125-2-76 81

FTP mode

mode - change or query transfer mode

The mode command defines the transfer mode or returns details on the currently set transfermode. If no operand is specified, the current transfer mode is displayed on the screen.Details on the currently set transfer mode can also be obtained with the status command.

The FTP standard defines a number of optional transfer modes. In BS2000, only the streamand block transfer modes have been implemented.

streamSets the transfer mode to STREAM.

blockThis operand enables files to be transferred without changing the existing recordstructure. In order to specify block, the following conditions must be satisfied:

– The transfer type must be EBCDIC or ASCII, and– the file attribute FCBTYPE=SAM must be set.

mode

[stream | block]

82 U41096-J-Z125-2-76

mput FTP

mput - send multiple local files

The mput command is used to transfer files from the local host to the remote host. Files canalso be transferred to a remote host by using the put, reput, append and send commands.

<local-file>Name of a file on the local host to be transferred to the remote host. Multiple files maybe specified in a single call.The files are assigned the same names on the remote host as on the local host. Thefile names must therefore comply with the file name conventions of the local host as wellas those of the remote host. Uppercase characters in the name of the remote file areconverted to lowercase.If the prompting function is enabled (see the prompt command), FTP requestsconfirmation before transferring each file. If a file transfer is unsuccessful, the followingfiles are also not transferred.

Example



→ lpwd Local directory is :5:$TCPTEST.MAN.SAM.NACH.SINIX.


mput

<local-file> [<local-file>] [<local-file>] ...

U41096-J-Z125-2-76 83

FTP mput

2. Transfer the files in the local directory designated by the entries anton, anton.* andberta.*. The FTP server function PORT is called implicitly. The prompting function isdisabled in this example. See the description of the prompt command on page 86.

→ mput anton anton.* berta.* 200 PORT command okay. 150 ASCII data connection for anton (89.16.100.0,1201). 226 Transfer complete.242 bytes sent in 0.03 seconds (6.05 Kbytes/s) 200 PORT command okay.150 Opening data connection for anton.upd (89.16.100.0,1202). . further transfers. 226 Transfer complete. 242 bytes sent in 0.04 seconds (5.76 Kbytes/s) 200 PORT command okay.150 ASCII data connection for berta.2 (89.16.100.0,1207). 226 Transfer complete.242 bytes sent in 0.04 seconds (5.90 Kbytes/s)

84 U41096-J-Z125-2-76

open FTP

open - open the connection to a remote host

The open command sets up a connection to a remote host. Either the name or the internetaddress of this host must be known. The host must either be part of the local network or beaccessible via a gateway. The names and addresses of the hosts that can be reached viathe open command can be obtained from the administrator of the local network.

<ipadr>Internet address of the remote host to which the connection is to be made.

<remote-host>Symbolic name of the remote host to which the connection is to be made.

local-hostSymbolic name reserved for the user’s own host (usually meaningful only for testpurposes). local-host represents the internet address through which the local host canactually be accessed on the LAN.

loopbackFor loopback, a separate internet address is generated that is not identical to theaddress of the user’s own host on the local network. This address is known only to thelocal host; other processors cannot use it.

<port>Port number of the FTP server. The FTP server is assigned port number 21 by default.The specification of a port number is required, for example, when multiple FTP serversare run on one host.

If an access control mechanism has been implemented on the remote host (for example, inBS2000/OSD and in UNIX), FTP determines the required authorization data (user ID,account number, password) interactively. Only the data that is really needed is requested(e.g. UNIX does not require an account number, so the corresponding request is omitted).

If the authorization data is entered incorrectly, the connection to the remote host remainsopen when working in interactive mode. The user command can then be used to enter theappropriate data.

open

<ipadr> | <remote-host> | [local-host | loopback] [<port>]

U41096-J-Z125-2-76 85

FTP open

If task switch 1 is set, then the required authorization data must be entered in batch modeor interactive mode on separate lines (in the correct sequence) following the opencommand. If the authorization data is invalid, the connection is cleared. FTP is terminatedwith TERMJ, i.e. the batch job or the procedure is continued only after the next STEPinstruction. See also the client commands jobvar on page 62 and svar on page 107.

The admission data must be specified in accordance with the conventions of thepartner system. Please observe the table on page 25.

If no password is required, enter ‘*NONE’ (uppercase letters).

Example


1. Call the FTP client.

/START-FTP% BLS0524 LLM 'FTP', VERSION '04.0A03' OF '2000-09-14 09:51:08' LOADED BS2000-FTP Vers V04.0A00 Sep 14 2000 00:58:34 ftp>

2. Open a connection to the host systemd.

→ open systemdConnected to systemd. 220 systemd FTP Server (Version 4.5 Wed May 13 13:19:14 MEZ 1999) ready.

3. Prompt for a user ID (name).

Name (systemd:TCPTEST):→ USERID

331 Password required for tcptest.

4. Prompt for a password.

Password (systemd:tcptest):→ PASSWORD

230 User tcptest logged in.

i

86 U41096-J-Z125-2-76

prompt FTP

prompt - enable/disable prompting

When using mdir, mget, mls, mput and mdelete, multiple file operations can be executed witha single call. If prompting is enabled, you will be asked before each file operation whetheryou really want the operation executed. The prompt command enables or disablesprompting. If prompting is enabled, it is disabled by the prompt command, and vice versa.On starting FTP, prompting is enabled by default. The current setting of the prompt optioncan be determined with the status command.

If prompting is enabled, the possible responses to the prompts are as follows:

y The action is executed.

n The action is not executed. The command is not aborted, but continues with the nextsubaction.

q The action is not executed, and the entire command is aborted.

Inputs other than n or q are interpreted as y.

Example

See the description of the mdelete command on page 71.

prompt

i

U41096-J-Z125-2-76 87

FTP put

put - send a local file

The put command is used to transfer a file from the local host to the remote host. Files mayalso be transferred to a remote host with the mput, append and send commands. A specialvariant of the put command, the reput command (see page 95), is now available forsupporting restart functionality.

<local-file>Name of a POSIX or DMS file on the local host to be transferred to the remote host.

<remote-file>Name of a file on the remote host. If the file already exists, it isoverwritten or, alternatively, a new file is created after adding an appropriate suffix. Thisbehavior is controlled by sunique. If the file does not exist, a new file is created.If the remote-file operand is omitted, the name of the local file is used (in which case thename of the local file must also comply with the file naming conventions of the remotehost). Uppercase characters in the name of the local file are converted to lowercase.

Example





2. Transfer the contents of the local file MAN.SAM.TO.SINIX.ANTON to the remote fileanton. The FTP server function PORT is called implicitly.

→ put man.sam.nach.sinix.anton anton 200 PORT command okay. 150 ASCII data connection for anton (89.16.100.0,1200). 226 Transfer complete. 242 bytes sent in 0.03 seconds (6.95 Kbytes/s)

put


88 U41096-J-Z125-2-76

pwd FTP

pwd - show remote working directory

The pwd command shows the name of the currently set remote working directory. Theremote working directory can be set by using the cd command.

Example


Query the name of the remote working directory.


pwd

U41096-J-Z125-2-76 89

FTP quit

quit - exit FTP

The quit command terminates the FTP program. If a connection to a remote host is stillopen, it is cleared (implicit close). The bye command can be entered as a synonym for quit.

Example

→ quit 221 Goodbye.

quit

90 U41096-J-Z125-2-76

quote FTP

quote - call server functions

The quote command can be used to call FTP server functions on the remote host whenthere is no corresponding FTP client command on the local host.

One example of this is the site exec function, which is available from the BS2000/OSD FTPserver, but for which there is no command in FTP. site exec can be used to execute anyBS2000/OSD commands on the server, provided the FTAC functionality is not being usedon the server.

Since the functions that can be called using quote depend on the server, a more detaileddescription cannot be offered here. The functions of the BS2000/OSD server are describedin the section “FTP servers in BS2000/OSD” (see page 11).

The functions implemented in the server can be determined by using the remotehelpcommand. The help command returns a list of the commands available on the localFTP client.

The quote site setc command can be used to change the code conversion tablesetting on the BS2000/OSD server. The command syntax is the same as for setcode(see page 101).

Example

The remote host is a BS2000/OSD host.

1. The quote CWD command is used to change the directory on the remote server.

→ quote CWD test 200 ":110:$TSOS.TEST." is current directory now.

2. The quote PWD command is used to check the current file system on the remote FTPserver.

→ quote PWD 257 ":110:$TSOS.TEST." is current directory.

quote

<argument> [<argument>] [<argument>]

i

U41096-J-Z125-2-76 91

FTP recv

recv - fetch a file

The recv command is used to transfer a file from the remote host to the local host.

See the description of the get command on page 57.

recv


92 U41096-J-Z125-2-76

reget FTP

reget - fetch a file with restart support

The reget command is a special variant of the get command (see page 57) and supports therestart functionality of the FTP client.

As with the get command, the reget command transfers a file from the remote host to thelocal host. However, the reget command checks before starting a transfer whether the targetfile (local file) already exists.

If the target file already exists, two different scenarios can be distinguished:

– Execution of the reget command assumes that the file has been partially transferred andcontinues the transfer from the point corresponding to the current end of the target file,if the following conditions are fulfilled:

– The target file is smaller and was produced later than the source file.

– The FTP server supports the server commands mdtm, size and rest (see page 20)which are required for checking and positioning.

– The transfer medium set is "stream" (see mode command on page 81).

– The ftyp setting is textbin.

– The setfile setting is datend: on, pademptyrec: off

– runique is disabled.

– Otherwise, the execution of the reget command corresponds to the execution of get, i.e.the source file is transferred completely.

<remote-file>Name of a file on the remote host, which is to be transferred to the local host.

<local-file>Name of a POSIX or DMS file on the local host. If the file does not exist, it is createdand the reget command behaves in the same way as the get command.If the local-file operand is omitted, the name of the remote file is used (in this case thename of the remote file must correspond to the file naming conventions of the localhost).

reget


U41096-J-Z125-2-76 93

FTP remotehelp

remotehelp - get help on functions of the remote FTP server

The remotehelp command returns a list of all functions implemented on the FTP server ofthe remote host. The individual server functions can be specified as an operand of thecommand. Server functions for which there are no corresponding commands on the FTPclient can be called by using the quote command. A list of all commands on the local FTPclient can be obtained with the help command.

<server-fct>FTP server function for which information is to be output.If no operand is specified, a list of all functions recognized is displayed.

Example

The remote host is a BS2000/OSD host.

List of the FTP server functions. Functions marked with an * (asterisk) are not implemented.

→ remotehelp214-The following commands are recognized (* =>'s unimplemented). USER PASV APPE MRSQ* DELE STAT XRMD SYST MODC PASS TYPE MLFL* MRCP* CWD HELP PWD REST SETC ACCT STRU MAIL* ALLO XCWD NOOP XPWD MDTM REIN* MODE MSND* RNFR LIST MKD CDUP SIZE QUIT RETR MSOM* RNTO NLST XMKD XCUP FILE PORT STOR MSAM* ABOR SITE RMD STOU FTYP 214 Direct comments to TSOS at BCAMVM06.

remotehelp

<server-fct>

94 U41096-J-Z125-2-76

rename FTP

rename - rename remote files

The rename command changes the name of a file on the remote host.

<remote-file1>Old name of the file.

<remote-file2>New name of the file.Any existing file is generally overwritten, but not in the DMS directory.

Example


1. Query the name of the remote working directory.

→ pwd257 "/usr/tcptest/man/sam/to.bs2000" is current directory.

2. Rename the remote file anton to zwaton.

→ rename anton zwaton 350 File exists, ready for destination name250 RNTO command successful.

rename

<remote-file1> <remote-file2>

U41096-J-Z125-2-76 95

FTP reput

reput - send a local file with restart support

The reput command is a special variant of the put command (see page 87) and supports therestart functionality of the FTP client.

As with the put command, the reput command transfers a file from the local to the remotehost. However, the reput command checks before starting a transfer whether the target file(file on server) already exists.

If the target file already exists, two different scenarios can be distinguished:

– Execution of the reput command assumes that the file has been partially transferred andcontinues the transfer from the point corresponding to the current end of the target file,if the following conditions are fulfilled:

– The target file is smaller and was produced later than the source file.

– The FTP server supports the server commands mdtm, size and rest (see page 20)which are required for checking and positioning.

– The transfer medium set is "stream" (see mode command on page 81).

– The ftyp setting is textbin.

– The setfile setting is datend: on, pademptyrec: off

– sunique is disabled.

– Otherwise, the execution of the reput command corresponds to the execution of put, i.e.the source file is transferred completely.

<local-file>Name of a POSIX or DMS file on the local host, which is to be transferred to the remotehost.

<remote-file>Name of a POSIX or DMS file on the remote host. If the file does not exist, it is createdand the reput command behaves in the same way as the put command.If the <remote-file> operand is omitted, the name of the local file is used (in this casethe name of the local file must correspond to the file naming conventions of the remotehost). Uppercase letters in the local file name are converted to lowercase.

reput


96 U41096-J-Z125-2-76

rexit FTP

rexit - define parameters for remote exit routines

The FTP client allows you to set BS2000/OSD FTP server exits with the rexit command(remote exit). However, this only relates to the exits for send and receive and only affects theconnection of these special FTP clients to the FTP server.

You will find further details on FTP exit routines in the interNet Services Administrator’sGuide.

<receive-selector><receive-selector> allows you to select the required action from several actionsavailable when receiving data (from the server’s perspective). For this purpose, yousupply the exit routine with a string to which <receive-selector> points. You can decidefreely the meanings that are to be attached to the individual strings. Only the strings "*"and "*NONE" have a fixed meaning:

– If you specify "*" for <receive-selector>, the entry YAPFEXIT is selected but withoutthe more precise specification of <receive-selector>. The general FTP serversetting then applies with the -U option.


If you do not specify <receive-selector>, no exit routine is selected.

<send-selector><send-selector> allows you to select the required action from several actions availablewhen sending data (from the server’s perspective). For this purpose, you supply the exitroutine with a string to which <send-selector> points. You can decide freely themeanings that are to be attached to the individual strings. Only the strings "*" and"*NONE" have a fixed meaning:

– If you specify "*" for <send-selector>, the entry YAPFEXIT is selected but without themore precise specification of <send-selector>. The general FTP server setting thenapplies with the -U option.


If you do not specify <send-selector>, no exit routine is selected.

rexit

[receive:<receive-selector>] [!] [send:<send-selector>]

U41096-J-Z125-2-76 97

FTP rmdir

rmdir - remove a remote directory

The rmdir command is used to remove an empty directory on the remote host.

<remote-directory>Fully qualified or relative name of a directory on the remote host.

Example


1. List the contents of the current working directory. The FTP server function PORT iscalled implicitly.

→ dir200 PORT command okay. 150 ASCII data connection for /bin/ls (89.16.100.0,1171)(0 bytes).-rwx------ 1 tcptest 10505 Sep 5 18:20 alaska -rw-rw-r-- 1 tcptest 229 Sep 7 13:56 anton -rw-rw-r-- 1 tcptest 229 Sep 7 13:56 anton.3 -rw-rw-r-- 1 tcptest 229 Sep 7 13:56 anton.upd -rwx------ 1 tcptest 10505 Sep 5 18:20 georgia drwxrwxrwx 2 tcptest 176 Sep 7 12:55 to.bs2000 drwxrwxrwx 2 tcptest 176 Sep 7 13:51 from.bs2000 drwxrwxrwx 2 tcptest 32 Sep 7 14:40 from.msdos 226 ASCII Transfer complete. 461 bytes received in 3.13 seconds (1.32E-01 Kbytes/s)

2. Remove the (empty) directory from.msdos.

→ rmdir from.msdos250 RMD command successful.

rmdir

<remote-directory>

98 U41096-J-Z125-2-76

runique FTP

runique - enable/disable unique storage of local files

The runique command controls the handling of files being stored on the local host, i.e. whenworking with get, mget or recv. The runique command toggles the current setting on or off andremains in effect until the next call to runique.

On starting FTP, runique is disabled by default.

runique disabled: If there is already an existing file of the same name, it is overwritten,provided the appropriate write authorization exists.

runique enabled: If the file to be transferred already exists, the existing file name isextended with a suffix (.1 to .99), and a new file is created. If thesuffixes from .1 to .99 have already been used for a particular filename, an error message is issued, and the transfer is aborted.

runique

U41096-J-Z125-2-76 99

FTP send

send - send a local file

The send command is used to transfer a file from the local host to the remote host.

See the description of the put command on page 87.

send


100 U41096-J-Z125-2-76

sendport FTP

sendport - enable/disable port command

The sendport command defines whether or not FTP should call the PORT function in theremote host’s server at the start of a file transfer. If the PORT function is enabled, thesendport command disables it, and vice versa. On starting FTP, the PORT function isenabled.

Normally the PORT function must be implemented in each server. However, there areservers which do not behave in a standardized manner and which do not have the PORTfunction implemented. Such servers will respond to a PORT command with the errormessage:

550: Command not understood

or

502: PORT command not implemented

In this case, the PORT function must be disabled.

sendport

U41096-J-Z125-2-76 101

FTP setcode

setcode - change code tables

The setcode command is used to change the current code tables with which the FTP clientconverts from EBCDIC to ISO characters (extended ASCII character set). The services ofXHCS are utilized for this purpose, so only code tables that have been entered ascompatible in XHCS may be specified here (see the "XHCS" manual). If a connection is setup between two BS2000/OSD systems, it is important to ensure that both partners use thesame code tables.

The current code table settings can be checked with the status command.Default settings: EDF041 for EBCDIC

ISO88591 for ASCII

<ebcdic-table> <iso-table>A code conversion table is generated with XHCS for conversion between EBCDIC andISO codes. This conversion table is used by the FTP client for all code conversions.

It is essential to ensure that the code tables are specified in the correct sequence;otherwise, invalid conversion tables will be created, and the file transfer will not bepossible.

Example

setcode EDF045 ISO88595

Remarks

The conversion table between the EBCDIC table EDF045 and the ISO table ISO88595 ismade available via XHCS. The usable conversion tables are defined in XHCS. From thisconversion table, the corresponding table for conversion in the opposite direction is created,and the previously valid conversion table is overwritten.

setcode

<ebcdic-table> <iso-table>

!

102 U41096-J-Z125-2-76

setfile FTP

setfile - enable/disable file marker

The setfile command allows you to define the behavior of FTP for file transfer in particularcases:

– The string "C-FILEEND" is normally used to mark the exact end of a PAM file. If the fileis then reprocessed by programs that have difficulty handling with this marking, theappending of this marker must be disabled.

– Records without content (dummy records) can be assigned a blank by FTP so that EDTaccounts for the records when they are output on the terminal.

datend on | offEnables/disable the appending of a "C-FILEEND".on is the default.

pademptyrec on | offEnables/disables the insertion of a blank in dummy records.off is the default.

If you specify setfile without parameters, FTP outputs the current settings for datend andpademptyrec.

If you want to set datend and pademptyrec on the FTP server, enter quote site sfil. The param-eters correspond to the setfile parameters.

The status (see page 87) command likewise provides information on the datend and pademp-tyrec settings.

setfile

[datend on | off] | [pademptyrec on | off]

U41096-J-Z125-2-76 103

FTP settime

settime - set time limit for server responses

The settime command can be used to modify the time limit for server responses (the defaultsetting is 30 sec). If a server response that is expected by the client is not received withinthe defined timeout, the client issues the message:

time limit for server response exceeded.

The currently set time limit can be determined with the status command.

settime <sec>

104 U41096-J-Z125-2-76

status FTP

status - display FTP status information

The status command returns information on the current connection together with details ofvarious locally set parameters. The command also displays information on the currently setcode tables, the character string for switching between the DMS and POSIX file systems,and the current file system (DMS or POSIX).

Example

→ status Connected to systemd, port 21. Mode: stream; Type: ascii; Form: non-print; Structure: fileFtyp: textbin Verbose: on; Bell: off; Prompting: on; Globbing: on Filesystem is: BS2000 The character to change the filesystem is: % ISO-codetable is ISO88591, EBCDIC-codetable is EDF041 Time limit for server responses: 30 secs Store unique: off; Receive unique: off Use special EOF marker (C-DATEIENDE): on Pad empty record with blank: off Used job variable: *NONE Used SDF-P variable: *NONE Used receive selector: *NONE Used send selector: *NONE Hash mark printing: off; Use of PORT cmds: on

status

U41096-J-Z125-2-76 105

FTP struct

struct - change or query transfer structure

The struct command defines the transfer structure or displays details of the current transferstructure. The FTP standard provides for a number of different, optional transfer structures,of which only FILE and RECORD are implemented in BS2000/OSD. If no operand isspecified, the current transfer structure is displayed on the screen.

On starting FTP, struct is set to file by default.

The currently defined transfer structure can also be determined with the status command.

fileSets the transfer structure to FILE.

recordThis entry enables files to be transferred while retaining the record structure. In order tospecify record, the following conditions must be satisfied:

– The transfer type must be EBCDIC or ASCII, and– The file attributes RECFORM=V and FCBTYPE=SAM must be set.

struct

[file | record]

106 U41096-J-Z125-2-76

sunique FTP

sunique - store remote files uniquely

The sunique command controls the handling of files being stored on the remote host, i.e.when working with put, mput or send. The sunique command toggles the current setting on oroff and the defined setting remains in effect until sunique is called again.

On starting FTP, sunique is disabled by default.

sunique disabled: If there is already an existing file of the same name, it is overwritten,provided the appropriate write authorization exists.

sunique enabled: If the file to be transferred already exists, it isrecreated by appending a suffix (.1 to .99). If thesuffixes from .1 to .99 have already been used for a particular filename, an error message is issued and the transfer is aborted.

sunique

U41096-J-Z125-2-76 107

FTP svar

svar - store error information in an SDF-P variable

You can use the svar command to inform the FTP client whether it is to store commandreturn information in an SDF-P variable.

The jobvar (see page 62) command offers an alternative to storing error information.

If an error occurs when editing the svar command and if task switch 1 is set (batch mode),the FTP client is terminated with TERMJ. The batch job or procedure is then only continuedafter the next STEP instruction.

If the provision of an S variable is activated, the behavior of commands that execute severalindividual actions (commands mdir, mls, mget, mput, mdelete) changes. In the case of thesecommands, command processing is aborted after the first faulty action. In contrast, the FTPclient is not terminated in batch mode with TERMJ if the admission data in the opencommand is faulty.

The SDF-P subsystem must be activated in order to use the svar command.

<sv-name>Name of the SDF-P variable S variable) that is to supply the FTP client with thecommand return information after the svar command is issued. This S variable iscreated again for this purpose. If an S variable with the name <sv-name> already exists,it is deleted first.

*NONEThe provision of S variables is halted by entering *NONE.

svar

<sv-name> | *NONE

108 U41096-J-Z125-2-76

svar FTP

Layout of S variables:

Element Element description

<sv-name>.STATUS $S: Command executed successfully$E: Command has errors$T: FTP client ended normally$A: FTP client ended abnormally with errors

<sv-name>.USERCMD Name of FTP client command

<sv-name>.CMDPARAM FTP command parameter

<sv-name>.PROTCMD Command sent from the FTP client to the FTP server

<sv-name>.MESSAGE Local message or server response

U41096-J-Z125-2-76 109

FTP system

system - display server information

The system command is used to request system information from the server, which thenissues the following message:

215: <operating system> <additional information>

system

110 U41096-J-Z125-2-76

tenex FTP

tenex - set transfer type to BINARY

The tenex command sets the transfer type to BINARY. This transfer type should always beselected when transferring binary files. The binary command is equivalent to the tenexcommand.

On starting FTP, the transfer type is set to ASCII by default.

tenex

U41096-J-Z125-2-76 111

FTP trace

trace - enable/disable SOCKET trace output

SOCKET trace output is primarily used by the network administrator and the Siemenssupport staff to diagnose problems on the local network. Normal users do not usually needany SOCKET trace output.

If SOCKET trace output is enabled, FTP displays various types of diagnostic information onthe screen.

<trace-value>The permitted values are in the range 0 through 9. Higher parameter values displaymore information.

0 No TRACE output (disable TRACE output).

1 - 9 Displays information on SOCKET traces.

If no operand is specified, the TRACE output setting is toggled, i.e. if TRACE output wasenabled, it is disabled, and if it was disabled, it is enabled (trace-value=1). Parameter valuesgreater than 1 imply the output of all TRACE information at the lower levels.

trace

[<trace-value>]

112 U41096-J-Z125-2-76

type FTP

type - change or query transfer type

The type command sets the transfer type (ASCII, BINARY, TENEX or EBCIDC). If nooperand is specified, the currently set transfer type is displayed on the screen.

On starting FTP, the transfer type is set to ASCII by default.

The transfer type can also be changed by using the ascii and binary commands. Thetransfer type currently set can be determined with the status command. The possibletransfer types are described in more detail from page 31. A table for ASCII/EBCDICconversion can be found in the "XHCS" manual.

When a connection is cleared and a new connection is set up, the type command must beissued again for a transfer type other than ASCII.

asciiSets the transfer type to ASCII. This transfer type should always be selected for textfiles, unless EBCDIC is in question.

binarySets the transfer type to BINARY. This transfer type should always be selected forbinary files.

ebcdicSets the transfer type to EBCDIC. This transfer type should be selected if both partnersare working with EBCDIC, i.e. of no code conversion is desired and a SAM file is to begenerated in BS2000/OSD.

tenexCorresponds to the transfer type BINARY.

type

[ ascii | binary | ebcdic | tenex ]

U41096-J-Z125-2-76 113

FTP type

Example

1. Query the transfer type.

→ typeUsing ascii mode to transfer files.

2. Set the transfer type to BINARY.

→ type binary200 Type set to I.

3. Query the transfer type.

→ type Using binary mode to transfer files.

114 U41096-J-Z125-2-76

user FTP

user - specify user ID on remote host

You can use the user command to enter the admission data at a later stage in the followingcases:

– If an access control mechanism is implemented on the remote host.

– Task switch 1 is not set or the storage of error information (commands jvar, svar) isenabled.

– The required admission data was incorrectly entered in the open command.

<userid>User ID on the remote host.

<password>Password on the remote host.Passwords are specified in accordance with the conventions of the partner system. ForBS2000/OSD partners, they may be specified as C-strings (c'...' or C'...') or ashexadecimal numbers (X'...', with X always uppercase). BS2000/OSD accepts theformats <password> and <'password'>. If no password is required, enter "*NONE".

<account>Account number on the remote host.

If any additional authorization data is required (password, account number), it isrequested in interactive mode.

user

[<userid> [password> [<account>]]]

U41096-J-Z125-2-76 115

FTP user

Example


1. Setting up a connection to systemd using the open command.

→ open systemd Connected to systemd. 220 systemd FTP Server (Version 4.5 Wed May 13 13:19:14 MEZ 1999)ready.

2. Selection of the login ID tcptest.

Name (systemd:TCPTEST): → tcptest

3. Entry of an invalid password.

331 Password required for tcptest. Password (systemd:tcptest):

→ maewest

530 Login failed. Login failed.

4. Repetition of the login.

→ user tcptest

5. Entry of the correct password; successful login.331 Password required for tcptest. Password:

→ password 230 User tcptest logged in.

116 U41096-J-Z125-2-76

verbose FTP

verbose - enable/disable server responses

The verbose command is used to enable or disable the display of responses from the FTPserver on the remote host. If the output of responses is enabled, the verbose commanddisables it, and vice versa. On starting FTP, verbose is enabled by default.

The current setting for verbose can be determined by using the status command.

Example


1. Query the name of the remote working directory with verbose enabled.


2. Transfer multiple files (with server responses). The FTP server function PORT is calledimplicitly. The prompt function is disabled.

→ mget * 200 PORT command okay. 150 ASCII data for anton (89.16.100.0,1192). 226 Transfer complete.242 bytes received in 0.06 seconds (3.69 Kbytes/s) 200 PORT command okay. 150 ASCII data for anton.1 (89.16.100.0,1193). 226 Transfer complete.150 ASCII data for caesar (89.16.100.0,1199). 226 Transfer complete.10845 bytes received in 0.78 seconds (13.56 Kbytes/s)

3. Rename a file (with server responses).

→ rename anton zwaton 350 File exists, ready for destination name200 RNTO command okay.

4. Disable the server responses.

→ verbose Verbose mode off.

verbose

U41096-J-Z125-2-76 117

FTP verbose

5. pwd, mget and rename commands without server responses:pwd mget * rename anton zwaton

118 U41096-J-Z125-2-76

? FTP

? - show information on FTP commands

The ? command returns a list of all FTP commands. It is also possible to obtain briefinformation on each of these FTP commands. The ? command is synonymous with help.

See the description of the help command on page 61.

?

<command>

U41096-J-Z125-2-76 119

FTP !

! - switch to BS2000/OSD command mode

The ! command enables you to enter BS2000/OSD commands during an FTP session. If nooperand is specified, the system switches to BS2000/OSD command mode. You can returnto FTP by issuing the BS2000/OSD command RESUME. Alternatively, if you specify ! witha BS2000/OSD command as the operand, you will be automatically returned to the FTPclient after execution of the command.

It is not possible to switch to POSIX command mode. However, POSIX commands can beentered by switching beforehand to the POSIX directory using the "lcd %POSIX" command.

<bs2000-command>Any BS2000/OSD command, except for the commands LOAD, EXEC, LOGOFF andABEND, which may not be entered either directly or indirectly, since they wouldterminate FTP or the task in which FTP is running.To avoid inconsistencies in the catalog, please make sure that you always use the FTPcommand file instead of the BS2000/OSD FILE command.

<POSIX command>Any POSIX command

Example

Issue the BS2000/OSD command sta p from FTP:

→ ! sta p NAME TSN TYPE SIZE CURR-CMD PROGRAM-NAME PETER 1447 3 DIALOG 87 EXECUTE :5:$TSOS.FTP

ftp>

→ !

x%BKPT AT xxxxxx

→ /sta p NAME TSN TYPE SIZE CURR-CMD PROGRAM-NAME PETER 1447 3 DIALOG 87 EXECUTE :5:$TSOS.FTP

/

→ resume

ftp>

!

[<bs2000 command>] | <POSIX command>

120 U41096-J-Z125-2-76

! FTP

U41096-J-Z125-2-76 121

4 FTAC interfaceThe FTAC function of openFT offers you the dual option of making your BS2000 server assecure as possible and as secure as required. FTAC stands for "File Transfer AccessControl". In order to use FTAC on a BS2000 server, openFT Version V7.0 or later withopenFT-AC is required.

4.1 FTAC functionality

The following features are offered by FTAC to protect the BS2000 server:

– Decoupling of transfer admissions and login admission– Access rights depending on the partner system– User-specific access rights– Flexible access right levels– Logging of every authorization check– Simple application

4.1.1 Features of the FTAC function

For file transfer, a distinction is made between various functions. For access protection, thefile transfer function being executed by the system is decisive. At first glance, there are onlytwo such functions:

– sending a file and– receiving a file.

Sending a file involves transmitting data from the system to be protected, while receiving afile involves the transfer of data into that system. For reasons of data security, it is, however,also important to know who requested a function on the system being protected. In FTterminology, this person is referred to as the "initiator" or "submitter" of the FT request.

122 U41096-J-Z125-2-76

FTAC functionality for FTP FTAC interface

A distinction is made in FTAC between two groups of initiators:

– initiators on the system being protected (outbound requests)– initiators on partner systems (inbound requests)

Since the functionality used by FTP is restricted to inbound requests, the following transferfunctions can be differentiated:

– Inbound send– Inbound receive

FTP partner systems (FTP clients) also have the option of using file management functionsto view directory or file attributes in their local system (BS2000 FTP server), to modify fileattributes and to delete files and directories. This results in a further function:

– Inbound file management

File management, in contrast to the other functions, includes several different requestoptions which, in turn, are partially linked to the functions Inbound send and Inbound receive:

– An FTP client can delete local files, provided the basic function Inbound receive ispermitted.

– An FTP client can display the attributes of local files, provided the basic function Inboundsend is permitted.

– An FTP client can display and delete directories, provided the basic function Inbound filemanagement is permitted.

– An FTP client can modify the attributes of local files and create and rename directories,provided both the basic functions Inbound receive and Inbound file management arepermitted.

The protection mechanisms offered by the FTAC function are primarily achieved by usingadmission sets and admission profiles.

U41096-J-Z125-2-76 123

FTAC interface FTAC functionality for FTP

4.1.2 Admission set

The admission set contains the basic specifications of which FTP functions are allowed. Anadmission set applies to exactly one user ID in BS2000. When access is attempted underthis user ID, FTAC checks for compliance with the values given in the admission set. Ifdesired, you can also restrict or extend the specifications of the admission set by usingadmission profiles or privileges, respectively. Admission profiles enable you to permit oneor more individual inbound functions for specific partners. You can view admission sets atany time and modify them as required to meet your current needs.

Following the installation of openFT-AC, the entries in the standard admission set initiallyapply to all user IDs. As the FTAC administrator, you should modify this standard admissionset after installation so that it provides the necessary protection for the majority of user IDs.If individual user IDs need greater protection, you can, of course, also create speciallycustomized admission sets for such cases.

4.1.3 FT profile

The FT profile (also called an admission profile) defines the transfer admission and theassociated access rights. The transfer admission is the actual key to accessing the BS2000server via FTP and should therefore be treated with the same care as a password. Thetransfer admission must be specified in transfer requests instead of a login admission.Anyone who knows the transfer admission will have access to your user ID on the BS2000server, but unlike the login authorization, will not be free to do as he or she pleases. Youcan decide which functions are to be permitted by specifying the access rights for thetransfer admission. This enables you to control which files can be accessed, for example,and under what conditions. In the most extreme case, you could effectively restrict accessto your user ID so severely that only one file can be accessed via only one profile. With theappropriate settings, an FT profile could be used simultaneously for both openFT and FTP.

For each file transfer request, FTAC checks whether the entries in the request conflict withthe entries in the FT profile. If such a conflict exists, the FTP request is rejected, and ageneral error message appears on the client system. This prevents potential intruders fromdetermining the definition of the FT profile in sequential steps on a trial and error basis. Alog record that describes the precise cause of the error is created on the BS2000 server.

124 U41096-J-Z125-2-76


The following diagram illustrates the sequence for access checks with FTAC.

Access check with FTAC

FTAC transfer admission login admission

FT profile

Admission set

Access controlof the operating system

FT request

Resources and data

= FTAC components

U41096-J-Z125-2-76 125


An admission profile includes the following:

– a transfer admission. This transfer admission must be unique. If a request is to work withthe FT profile, this transfer admission must be specified. FTAC will then only permitthose access rights for the request which are defined in the FT profile. In order touniquely assign the responsibility for requests, it is recommended that a transferadmission be assigned to exactly one person.

– if necessary, specification of the partner systems that may access this FT profile.

– details of the parameters that may be used in a request and their scope. This enablesthe access rights to be restricted for each person who uses this FT profile for FTP.

– if necessary, details on whether and when the FT profile can be used.

– a file name prefix. This prefix contains a part of the path name. The user of the profilecan then only navigate below the specified path name. For example, if C:\USR\HUGO\is specified as a file name prefix on a UNIX system, the user of this profile will only begranted access to directories under the path C:\USR\HUGO\. This prevents users fromaccessing locked directories by entering ". .".

You can store many different FT profiles.

The following operations can be performed on FT profiles at any time:

– Modifyand thus adapt the profile to current requirements.

– LockIn this case, a request with the locked profile is rejected on account of the invalid transferadmission. If you want to use the profile again, you must first unlock the FT profile.

– DeleteYou should limit the number of your FT profiles by deleting profiles which you no longerneed.

– Privilege (system-dependent)In special cases, FT profiles can also utilize a function that has been locked in anadmission set. In order to do this, the FT profile must be assigned a privilege by theFTAC administrator.

You can also display information on your FT profiles at any time.

126 U41096-J-Z125-2-76


4.1.4 Effects of an FT profile

The following table shows the possible restrictions to the access rights in an FT profile inthe left column, with the entries needed for the FT request with respect to the partnersystem in the right column:

Exporting admissions

You can export complete admissions as well as individual admission sets and profiles to afile (export) and then import them from the file when required.

Entry in the FT profile Entries in the FT request

Transfer admission The transfer admission must be specified.– Enter $FTAC as the user ID or a different character string

defined by the system administrator. Use the transferadmission as the password.

– If an admission profile is defined with transfer admission"anoymousFTP", access is also possible using the user ID"FTP" or "ANONYMOUS". The password in this case mustbe a mail address. (it is then simply checked to verify if "@"is included.)

Transfer direction restricted The value specified here must be the opposite of the entry in theFT profile. If the profile contains the transfer direction “Frompartner”, the remote system may only send data to the localsystem; with “To partner”, only read access is permitted on thelocal system.

Partner systems specified The request can only be issued by partner systems entered inthe profile. This option may only be used if the names of the FTPclients are guaranteed to be no longer than 8 characters. If DNSis activated, the client name supplied by DNS is used, otherwisethe entry belonging to the IP address in the SOCKET-HOST-TABLE is relevant (see "BCAM" manual). If no correspondingentry is available, the entry in the PROCESSOR-TABLE isused. In the case of local access, "LOOPBACK" is used as thename.

Prefix for file name specified Only part of the file name is present in the request. FTACsupplements this entry with the prefix defined in the profile toobtain the complete file name. The entry of absolute file names,or exiting a directory with “..” is prohibited by FTAC.

Follow-up processing This FTAC function is reserved for openFT and is not used forFTP.

Syntax restriction The request is executed only if it does not violate this syntaxrestriction.

U41096-J-Z125-2-76 127


4.1.5 Monitoring the FTP server with FTAC

The FTAC function also checks the server commands on the BS2000 FTP server.The following table contains a list of the server commands that are checked by FTAC andthe corresponding client commands which use them.

Server command Corresponding BS2000 FTP client command

retr get, recv, mget

stor put, send (if sunique=off), mput

stou put, send (if sunique=on)

appe append

rfnr rename

dele delete, mdelete

site file quote site file

cwd cd

xcwd cd (same function as cwd)

cdup cdup

xcup cdup (same function as cdup)

list dir, mdir

nlst ls, mls, mget, mdelete

site exec quote site exec (always rejected when using FTAC)

mkd mkdir

xmkd mkdir (same function as mkd)

rmd rmdir

xrmd rmdir (same function as rmd)

pwd pwd

xpwd pwd (same function as pwd)

size quote size, reget, reput

mdtm quote mdtm, reget, reput

List of FTP server commands checked via FTAC

128 U41096-J-Z125-2-76

Command description FTAC interface

4.2 FTAC command interface

The FTAC command interface offers:

– a functional command overview provides a quick orientation of which commands areavailable for which tasks,

– information on entering commands and the command syntax,

– explanations of the return codes, outputs in OPS variables and in CSV format,

– a detailed description of all FTP commands relevant for the user in alphabetical order.

4.2.1 Functional command overview

The following overview shows the appropriate FTAC user commands for individual tasks.The use of openFT-AC for the BS2000 FTP server is a prerequisite for the use of thesecommands.

Commands for the FTAC admission sets

FTAC users can view the standard admission set and their own admission sets. They canalso modify their own admission sets and display partner systems.

Commands for the FTAC admission profiles

FTAC users can create, modify, show and delete admission profiles for their own user IDs.

Command for the logging function

Modify admission set MODIFY-FT-ADMISSION-SET Page 162

Show admission set SHOW-FT-ADMISSION-SET Page 181

Create admission profile CREATE-FT-PROFILE Page 149

Delete admission profile DELETE-FT-PROFILE Page 160

Modify admission profile MODIFY-FT-PROFILE Page 167

Show admission profile SHOW-FT-PROFILE Page 198

Show logging records SHOW-FT-LOGGING-RECORDS Page 185

U41096-J-Z125-2-76 129

FTAC interface Command description

4.2.2 Entering FTAC commands

Please remember the following when entering commands:

– You must insert commas to separate the individual operands of a command, e.g.

/TRANSFER-FILE TRANSFER-DIRECTION=TO,PARTNER-NAME=CENTRE,LOCAL-PARAMETER=...

– Quotes within quotes must be doubled. This rule applies to all value assignments thathave to be specified in quotes.

– If there is no default value marked (by underscoring) for an operand, then it must bespecified with a valid value (mandatory operand).

– You may abbreviate your entries for commands and operands, provided you ensure thatyour entries retain their uniqueness. You can also use positional parameters if you wish.Short forms and long forms can be mixed at will. Certain abbreviated forms of keywordsand a number of positional operands are guaranteed for openFT. This means that theseoptions will also be offered in the same format in later versions. To be “on the safe side”,you should therefore form the habit of entering these commands in their abbreviatedform. Make sure that you always use the guaranteed abbreviated forms in procedures,since this will ensure that they execute correctly even in subsequent versions. Therecommended abbreviations are used in the examples shown in this chapter, and thepossible abbreviations are listed in the individual command formats.

– If a structure is preceded by an introductory operand (e.g. *BS2000 is an introductoryoperand in "REM=*BS2000(...)"), then the opening parentheses must immediatelyfollow this operand. Introductory operands may be omitted if there is no risk ofambiguity.

– The asterisk preceding keywords may be omitted if there is no risk of ambiguity. Pleasenote that this is not a guaranteed abbreviation.

If positional operands are explicitly permitted in the syntax, values may be specifiedinterchangeably in both positional and keyword form.

In this case, the following rules must be observed:

– The first value specified as a positional operand is assigned to the first operand, thesecond value to the second operand, and so on.

– For each operand omitted before a positional operand, a comma must be entered.

– If one operand is assigned one value specification each in positional and keyword form,the last specification in the structural parentheses applies. This is always thespecification in keyword form, since the positional operand must always come first.

130 U41096-J-Z125-2-76

Command description FTAC interface

– The positional operands must be listed first. For the sake of clarity, duplicate valueassignments should be avoided.

– Since it is possible that the sequence of operands could be changed in later versions,only keyword parameters should be used within procedures.

U41096-J-Z125-2-76 131

FTAC interface SDF syntax representation

4.2.3 SDF syntax representation

Figure 1 shows an example of how the command syntax is represented in this manual. Thecommand format consists of a field with the command name. All operands with their legalvalues are then listed. Operand values which introduce structures and the operands thatdepend on them are listed separately.

Syntax representation of the user command HELP-SDF

This syntax description is based on SDF V4.1A. The syntax of the SDFcommand / statement language is explained in the following three tables.

Table 1: Notational conventions

The meanings of the special characters and the notation used to describe commandand statement formats are explained in Table 1.

Table 2: Data types

Variable operand values are represented in SDF by data types. Each data type representsa specific set of values. The number of data types is restricted to those described in Table 2.

The description of the data types applies to the entire set of commands/statements.Consequently, only deviations (if any) from the attributes described here are explained inthe relevant operand descriptions.

HELP-SDF Alias: HPSDF

GUIDANCE-MODE = *NO / *YES

,SDF-COMMANDS = *NO / *YES

,ABBREVIATION-RULES = *NO / *YES

,GUIDED-DIALOG = *YES (...)

*YES(...)

SCREEN-STEPS = *NO / *YES

,SPECIAL-FUNCTIONS = *NO / *YES

,FUNCTION-KEYS = *NO / *YES

,NEXT-FIELD = *NO / *YES

,UNGUIDED-DIALOG = *YES (...) / *NO

*YES(...)

SPECIAL-FUNCTIONS = *NO / *YES ,FUNCTION-KEYS = *NO / *YES

132 U41096-J-Z125-2-76

SDF syntax representation FTAC interface

Table 3: Suffixes for data types

Data type suffixes define additional input rules for data types. They contain a length orinterval specification and can be used to limit the set of values (suffix begins with without),extend it (suffix begins with with), or declare a particular task mandatory (suffix begins withmandatory). The following short forms are used in this manual for data type suffixes:

cat-id catcompletion complcorrection-state corrgeneration genlower-case lowmanual-release manodd-possible oddpath-completion path-complseparators septemporary-file temp-fileunder-score underuser-id userversion verswildcard-constr wild-constrwildcards wild

The description of the ‘integer’ data type in Table 3 contains a number of items in italics; theitalics are not part of the syntax and are only used to make the table easier to read.For special data types that are checked by the implementation, Table 3 contains suffixesprinted in italics (see the special suffix), which are not part of the syntax.

The description of the data type suffixes applies to the entire set of commands/statements.Consequently, only deviations (if any) from the attributes described here are explained inthe relevant operand descriptions.

U41096-J-Z125-2-76 133

FTAC interface SDF syntax representation

Metasyntax

Representation Meaning Examples

UPPERCASE

LETTERSUppercase letters denotekeywords. The keywords forconstant operand values beginwith *

HELP-SDF

SCREEN-STEPS = *NO

UPPERCASE

LETTERS

in boldface

Uppercase letters printed inboldface denote guaranteed orsuggested abbreviations ofkeywords.

GUIDANCE-MODE = *YES

= The equals sign connects anoperand name with the associatedoperand values.

GUIDANCE-MODE = *NO

< > Angle brackets denote variableswhose range of values is describedby data types and suffixes (seeTables 2 and 3).

SYNTAX-FILE = <filename 1..54>

Underscoring Underscoring denotes the defaultvalue of an operand.

GUIDANCE-MODE = *NO

/ A slash serves to separatealternative operand values.

NEXT-FIELD = *NO / *YES

(…) Parentheses denote operandvalues that initiate a structure.

,UNGUIDED-DIALOG = *YES (...) / *NO

[ ] Square brackets denote operandvalues which introduce a structureand are optional. The subsequentstructure can be specified withoutthe initiating operand value.

SELECT = [*BY-ATTRIBUTES](...)

Indentation Indentation indicates that theoperand is dependent on a higher-ranking operand.

,GUIDED-DIALOG = *YES (...)

*YES(...)

SCREEN-STEPS = *NO /

*YES

Table 1: Metasyntax

134 U41096-J-Z125-2-76

SDF syntax representation FTAC interface

A vertical bar identifies relatedoperands within a structure. Itslength marks the beginning andend of a structure. A structure maycontain further structures. Thenumber of vertical bars precedingan operand corresponds to thedepth of the structure..

SUPPORT = *TAPE(...)

*TAPE(...)

VOLUME = *ANY(...) *ANY(...) ...

, A comma precedes furtheroperands at the same structurelevel.

GUIDANCE-MODE = *NO / *YES

,SDF-COMMANDS = *NO / *YES

list-poss(n): The entry "list-poss" signifies that alist of operand values can be givenat this point. If (n) is present, itmeans that the list must not havemore than n elements. A list ofmore than one element must beenclosed in parentheses.

list-poss: *SAM / *ISAM

list-poss(40): <structured-name 1..30>

list-poss(256): *OMF / *SYSLST(...) /

<filename 1..54>

Abbreviation: The name that follows represents aguaranteed alias for the commandor statement name.

HELP-SDF Alias: HPSDF

Representation Meaning Examples

Table 1: Metasyntax

U41096-J-Z125-2-76 135

FTAC interface Data types

Data types

Data type Character set Special rules

alphanum-name A…Z0…9$, #, @

cat-id A…Z0…9

Not more than 4 characters;must not begin with the string PUB

command-rest freely selectable

composed-name A…Z0…9$, #, @hyphenperiodcatalog ID

Alphanumeric string that can be split intomultiple substrings by means of a period orhyphen.If a file name can also be specified, the stringmay begin with a catalog ID in the form :cat: (seedata type filename).

c-string EBCDIC character Must be enclosed within single quotes;the letter C may be prefixed; any single quotesoccurring within the string must be enteredtwice.

date 0…9Structure identifier:hyphen

Input format: yyyy-mm-dd

yyyy: year; optionally 2 or 4 digitsmm: monthdd: day

device A…Z0…9hyphen

Character string, max. 8 characters in length,corresponding to a device available in thesystem. In guided dialog, SDF displays the validoperand values. For notes on possible devices,see the relevant operand description.

fixed +, -0…9period

Input format: [sign][digits].[digits]

[sign]:+ or -[digits]:0...9

must contain at least one digit, but maycontain up to 10 characters (0...9, period) apartfrom the sign.

Table 2: Data types (section 1 of 5)

136 U41096-J-Z125-2-76

Data types FTAC interface

filename A…Z0…9$, #, @hyphenperiod

Input format:

[:cat:][$user.]

:cat:optional entry of the catalog identifier;character set restricted to A...Z and 0...9;maximum of 4 characters; must be enclosedin colons; default value is the catalogidentifier assigned to the user ID, asspecified in the user catalog.

$user.optional entry of the user ID;character set is A…Z, 0…9, $, #, @;maximum of 8 characters; first charactercannot be a digit; $ and period aremandatory;default value is the user's own ID.

$. (special case)system default ID

filefile or job variable name;may be split into a number of partial namesusing a period as a delimiter:name1[.name2[...]]namei does not contain a period and mustnot begin or end with a hyphen;file can have a maximum length of 41characters; it must not begin with a $ andmust include at least one character from therange A...Z.



filefile(no)group

group(*abs)(+rel)(-rel)

U41096-J-Z125-2-76 137


filename(continued)

#file (special case)@file (special case)

# or @ used as the first character indicatestemporary files or job variables, dependingon system generation.

file(no)tape file nameno: version number;character set is A...Z, 0...9, $, #, @.Parentheses must be specified.

groupname of a file generation group(character set: as for "file")

group

(*abs)absolute generation number (1-9999);* and parentheses must be specified.

(+rel)(-rel)

relative generation number (0-99);sign and parentheses must be specified.

integer 0…9, +, - + or -, if specified, must be the first character.

name A…Z0…9$, #, @

Must not begin with 0...9.

posix-filename A...Z0...9special characters

String with a length of up to 255 characters;consists of either one or two periods or of alpha-numeric characters and special characters.The special characters must be escaped with apreceding \ (backslash); the / is not allowed.Must be enclosed within single quotes if alter-native data types are permitted, separators areused, or the first character is a ?, ! or ^A distinction is made between uppercase andlowercase.



(*abs)(+rel)(-rel)

138 U41096-J-Z125-2-76

Data types FTAC interface

posix-pathname A...Z0...9special charactersstructure identifier:slash

Input format: [/]part1/.../partnwhere parti is a posix-filename;max. 1023 characters;must be enclosed within single quotes if alter-native data types are permitted, separators areused, or the first character is a ?, ! or ^

product-version A…Z0…9periodsingle quote

Input format:

where m, n, s and o are all digits and a is a letter.Whether the release and/or correction statusmay/must be specified depends on the suffixesto the data type (see the suffixes without-corr,without-man, mandatory-man and mandatory-corr in Table 3).product-version may be enclosed within singlequotes (possibly with a preceding C).The specification of the version may begin withthe letter V.

structured-name A…Z0…9$, #, @hyphen

Alphanumeric string which may comprise anumber of substrings separated by a hyphen.First character: A...Z or $, #, @

text freely selectable For the input format, see the relevant operanddescriptions.

time 0…9structure identifier:colon

Time-of-day entry:

Input format:

hh: hoursmm: minutesss: seconds

vsn a) A…Z0…9

a) Input format: pvsid.sequence-nomax. 6 characters

pvsid: 2-4 characters; PUBmust not be entered

sequence-no: 1-3 characters



[[C]' ][V][m]m.naso[' ]

correction status

release status

hh:mm:sshh:mmhh

Leading zeros may beomitted

U41096-J-Z125-2-76 139


b) A…Z0…9$, #, @

b) Max. 6 characters;PUB may be prefixed, but must not befollowed by $, #, @.

x-string Hexadecimal:00…FF

Must be enclosed in single quotes; must beprefixed by the letter X. There may be an oddnumber of characters.

x-text Hexadecimal:00…FF

Must not be enclosed in single quotes;the letter X must not be prefixed.There may be an odd number of characters.



140 U41096-J-Z125-2-76

Suffixes for data types FTAC interface

Suffixes for data types

Suffix Meaning

with (contd.)

-wild(n) Parts of names may be replaced by the following wildcards.n denotes the maximum input length when using wildcards.Due to the introduction of the data types posix-filename and posix-pathname, SDF now accepts wildcards from the UNIX world (referred tobelow as POSIX wildcards) in addition to the usual BS2000 wildcards.However, as not all commands support POSIX wildcards, their use for datatypes other than posix-filename and posix-pathname can lead to semanticerrors.Only POSIX wildcards or only BS2000 wildcards should be used within asearch pattern. Only POSIX wildcards are allowed for the data types posix-filename and posix-pathname. If a pattern can be matched more than oncein a string, the first match is used.

BS2000wildcards

Meaning

* Replaces an arbitrary (even empty) character string. If thestring concerned starts with *, then the * must be entered twicein succession if it is followed by other characters and if thecharacter string entered does not contain at least one otherwildcard.

Termina-ting period

Partially-qualified entry of a name.Corresponds implicitly to the string "./*", i.e. at least one othercharacter follows the period.

/ Replaces any single character.

<sx:sy> Replaces a string that meets the following conditions:– It is at least as long as the shortest string (sx or sy)– It is not longer than the longest string (sx or sy)– It lies between sx and sy in the alphabetic collating

sequence; numbers are sorted after letters (A...Z0...9)– sx can also be an empty string (which is in the first position

in the alphabetic collating sequence)– sy can also be an empty string, which in this position stands

for the string with the highest possible code (contains onlythe characters X'FF' )

<s1,…> Replaces all strings that match any of the character combina-tions specified by s. s may also be an empty string. Any suchstring may also be a range specification "sx:sy" (see above).

Table 3: Data type suffixes (section 1 of 6)

U41096-J-Z125-2-76 141

FTAC interface Suffixes for data types

with-wild(n)

(continued) -s Replaces all strings that do not match the specified string s.The minus sign may only appear at the beginning of string s.Within the data types filename or partial-filename the negatedstring -s can be used exactly once, i.e. -s can replace one ofthe three name components: cat, user or file.

Wildcards are not permitted in generation and version specifications for filenames. Only system administration may use wildcards in user IDs.Wildcards cannot be used to replace the delimiters in name components cat(colon) and user ($ and period).

POSIXwildcards

Meaning

* Replaces any single string (including an empty string). An *appearing at the first position must be duplicated if it is followedby other characters and if the entered string does not includeat least one further wildcard.

? Replaces any single character; not permitted as the firstcharacter outside single quotes.

[cx-cy] Replaces any single character from the range defined by cxand cy, including the limits of the range. cx and cy must benormal characters.

[s] Replaces exactly one character from string s.The expressions [cx-cy] and [s] can be combined into[s1cx-cys2].

[!cx-cy] Replaces exactly one character not in the range defined by cxand cy, including the limits of the range. cx and cy must benormal characters.The expressions [!cx-cy] and [!s] can be combined into[!s1cx-cys2].

[!s] Replaces exactly one character not contained in string s. Theexpressions [!s] and [!cx-cy] can be combined into [!s1cx-cys2].

Suffix Meaning


142 U41096-J-Z125-2-76


with (contd.)

-wild-constr(n)

Specification of a constructor (string) that defines how new names are to beconstructed from a previously specified selector (i.e. a selection string withwildcards). See also with-wild. n denotes the maximum input length whenusing wildcards.The constructor may consist of constant strings and patterns. A pattern(character) is replaced by the string that was selected by the correspondingpattern in the selector.The following wildcards may be used in constructors:

Wildcard Meaning

* Corresponds to the string selected by the wildcard * in theselector.

Termina-ting period

Corresponds to the partially-qualified specification of a name inthe selector;corresponds to the string selected by the terminating period inthe selector.

/ or ? Corresponds to the character selected by the / or ? wildcard inthe selector.

<n> Corresponds to the string selected by the n-th wildcard in theselector, where n is an integer.

Allocation of wildcards to corresponding wildcards in the selector:All wildcards in the selector are numbered from left to right in ascendingorder (global index).Identical wildcards in the selector are additionally numbered from left to rightin ascending order (wildcard-specific index).Wildcards can be specified in the constructor by one of two mutuallyexclusive methods:

1. Wildcards can be specified via the global index: <n>

2. The same wildcard may be specified as in the selector; substitutionoccurs on the basis of the wildcard-specific index. For example:the second "/" corresponds to the string selected by the second "/" in theselector

Suffix Meaning


U41096-J-Z125-2-76 143


with-wild-constr

(continued)

The following rules must be observed when specifying a constructor:

– The constructor can only contain wildcards of the selector.

– If the string selected by the wildcard <...> or [...] is to be used in theconstructor, the index notation must be selected.

– The index notation must be selected if the string identified by a wildcardin the selector is to be used more than once in the constructor. Forexample: if the selector "A/" is specified, the constructor "A<n><n>"must be specified instead of "A//".

– The wildcard * can also be an empty string. Note that if multiple asterisksappear in sequence (even with further wildcards), only the last asteriskcan be a non-empty string, e.g. for "****" or "*//*".

– Valid names must be produced by the constructor. This must be takeninto account when specifying both the constructor and the selector.

– Depending on the constructor, identical names may be constructed fromdifferent names selected by the selector. For example:“A/*” selects the names "A1" and "A2"; the constructor "B*" generatesthe same new name "B" in both cases.To prevent this from occurring, all wildcards of the selector should beused at least once in the constructor.

– If the selector ends with a period, the constructor must also end with aperiod (and vice versa).

Suffix Meaning


144 U41096-J-Z125-2-76


with-wild-constr(continued)

Examples:

without Restricts the specification options for a data type.

-cat Specification of a catalog ID is not permitted.

-corr Input format: [[C]' ][V][m]m.na[' ]Specifications for the data type product-version must not include thecorrection status.

-gen Specification of a file generation or file generation group is not permitted.

-man Input format: [[C]' ][V][m]m.n[' ]Specifications for the data type product-version must not include eitherrelease or correction status.

-odd The data type x-text permits only an even number of characters.

-sep With the data type "text", specification of the following separators is notpermitted: ; = ( ) < > Ë (i.e. semicolon, equals sign, left and right paren-theses, greater than, less than, and blank).

-temp-file

Specification of a temporary file is not permitted (see #file or @file underfilename).

Suffix Meaning


Selector Selection Constructor New name

A//* AB1AB2A.B.C

D<3><2> D1D2D.CB

C.<A:C>/<D,F> C.AADC.ABDC.BAFC.BBF

G.<1>.<3>.XY<2> G.A.D.XYAG.A.D.XYBG.B.F.XYAG.B.F.XYB

C.<A:C>/<D,F> C.AADC.ABDC.BAFC.BBF

G.<1>.<2>.XY<2> G.A.A.XYAG.A.B.XYBG.B.A.XYAG.B.B.XYB

A//B ACDBACEBAC.BA.CB

G/XY/ GCXYDGCXYEGCXY. 1)

G.XYC

1) The period at the end of the name may violate naming conventions (e.g. for fully-qualifiedfile names).

U41096-J-Z125-2-76 145


How are the operands described?

After the format of each command there is a detailed description of all the operands, thepossible value assignments and their functions.

Otherwise the same metasyntax is used in describing operands as in the representation ofthe command formats (see above).

without(contd.)

-user Specification of a user ID is not permitted.

-vers Specification of the version (see "file(no)") is not permitted for tape files.

-wild The file types posix-filename and posix-pathname must not contain apattern (character).

mandatory Certain specifications are necessary for a data type.

-corr Input format: [[C]' ][V][m]m.naso[' ]Specifications for the data type product-version must include the correctionstatus and therefore also the release status.

-man Input format: [[C]' ][V][m]m.na[so][' ]Specifications for the data type product-version must include the releasestatus. Specification of the correction status is optional if this is notprohibited by the use of the suffix without-corr.

-quotes Specifications for the data types posix-filename and posix-pathname mustbe enclosed in single quotes.

Suffix Meaning


146 U41096-J-Z125-2-76

Command return codes FTAC interface

4.2.4 Command return codes

The openFT-AC supply return codes that you can query when using SDF-P. Each returncode consists of a subcode1 (SC1), a subcode2 (SC2) and the maincode (MC).

Subcode1

Subcode1 represents the error class and is a decimal number.

A distinction is made between the following error classes:

– No error:the value of subcode1 is 0.

– Syntax error:the value of subcode1 is between 1 and 31, inclusive.

– Internal error (system error):the value of subcode1 is 32.

– Errors not assigned to any other class:the value of subcode1 is between 64 and 127, inclusive. If the value of subcode 1 is inthis range, the maincode must be evaluated to determine the appropriate action.

– Command cannot be executed at this time:the value of subcode1 is between 128 and 130, inclusive.

Subcode2

Subcode2 either contains information supplementary to that in subcode1 or is equal to 0.

Maincode

The maincode corresponds to the message key of the SYSOUT message. You can use the/HELP-MSG-INFORMATION command to obtain detailed information. The chapter onMessages contains details on the meanings of the messages and the actions to be taken inresponse.

See the manual "User Commands (SDF Format)" for a detailed description of the commandreturn codes.

Each command description below shows which command return codes are possible for thecommand in question and explains the meanings of the return codes.

U41096-J-Z125-2-76 147

FTAC interface OPS variables

4.2.5 OPS variables

With OPS (Output Presentation Service), you can optionally have the outputs of SHOWcommands placed in OPS variables as an alternative to or in addition to the normal outputto SYSLST/SYSOUT, provided SDF-P is installed. As the user, you will need to generatethe corresponding OPS variables with DECL-VAR. The information supplied by SHOWcommands is stored by openFT-AC in an SDF-P structure, which can be evaluated with thehelp of an SDF-P procedure. Structure elements that have not been set due to acorresponding command input are output without a value assignment.

The request to set OPS variables is implemented by integrating the FTAC command (whoseformat remains unchanged) in the BS2000 command EXEC-CMD.

Example

/EXEC-CMD (SHOW-FT-LOGGING-RECORDS),TEXT=*N,STRUCT-OUT=<variable-name>

OPS support is offered for the SHOW-FT-LOGGING-RECORDS command.

148 U41096-J-Z125-2-76

Output in CSV format FTAC interface

4.2.6 Output in CSV format

The output of some SHOW commands in openFT (BS2000) and openFT-AC (BS2000) V7.0can be optionally requested in CSV (Comma Separated Values) format. CSV is a popularformat in the PC environment, in which tabular data is defined by lines. Output in CSVformat is offered for the following commands:

– SHOW-FT-ADMISSION-SET (see page 184)

– SHOW-FT-LOGGING-RECORDS (see page 197)

– SHOW-FT-PROFILE (see page 201)

Many programs such as spreadsheets, databases, etc. can import data in CSV format. Thismeans that you can use the processing and presentation features of such programs on thedata output by the above commands.

The first line is the header and contains the field names of the respective columns. Onlythe field names are guaranteed, not the order of fields in a record. In other words, theorder of columns is determined by the order of the field names in the header line.

One example of a possible evaluation procedure is supplied as a reference template in theMicrosoft Excel format under the name $SYSFJAM.FTACCNT.XLT. You will need to firstmake a binary copy of this template on your PC. The template evaluates a CSV logging fileby means of an automatically running macro. The result shows the number of inboundrequests for all BS2000 users.

U41096-J-Z125-2-76 149

Create admission profile CREATE-FT-PROFILE

4.2.7 CREATE-FT-PROFILE - Create admission profile

Every FTAC user can create his own admission profile for his own user ID with theCREATE-FT-PROFILE command. Admission profiles predefined by the FTAC administratormust be "enabled" by the user with MODIFY-FT-PROFILE (see from page 167) before theycan be used.

If you call HELP for the SDF command syntax shown below, you may also see someoperands that are not indicated here. This is because only the operands relevant for FTPare described in this section.

CREATE-FT-PROFILE - showing operands relevant for FTP

NAME = <alphanum-name 1..8>

, PASSWORD = *NONE / <c-string 1..8 with-low> / <x-string 1..16> / *SECRET

, TRANSFER-ADMISSION = *NOT-SPECIFIED / <alphanum-name 8..32>(...) /

<c-string 8..32 with-low> (...) / <x-string 15..64>(...) / *SECRET

<alphanum-name 8..32>(...) / <c-string 8..32 with-low>(...) / <x-string 15..64>(...)

VALID = *YES / *NO

, USAGE = *PRIVATE / *PUBLIC

, EXPIRATION-DATE = *NOT-RESTRICTED / <date 8..10>

, PRIVILEGED = *NO

, IGNORE-MAX-LEVELS = *NO / *YES / *PARAMETERS(...)

*PARAMETERS(...)

, INBOUND-SEND = *NO / *YES

, INBOUND-RECEIVE = *NO / *YES

, INBOUND-MANAGEMENT = *NO / *YES

, USER-ADMISSION = *OWN / *PARAMETERS(...)

*PARAMETERS(...)

USER-IDENTIFICATION = *OWN / <name 1..8>

, ACCOUNT = *OWN / *NOT-SPECIFIED / <alphanum-name 1..8>

, PASSWORD = *OWN / <c-string 1..8> / <x-string 1..16> / *NONE / *SECRET

, INITIATOR = *REMOTE

, TRANSFER-DIRECTION = *NOT-RESTRICTED / FROM-PARTNER / TO-PARTNER

, PARTNER-NAME = *NOT-RESTRICTED / list-poss(50): <name 1..8>

, MAX-PARTNER-LEVEL = *NOT-RESTRICTED / <integer 0..100>

150 U41096-J-Z125-2-76

CREATE-FT-PROFILE Create admission profile

Operands

NAME=<alphanum-name 1..8>With NAME, the admission profile is given a name. This name must be unique among alladmission profiles on your user ID. If an admission profile with this name already exists,FTAC rejects the command with the message:

FTC0100 CMD REJECTED. FT-PROFILE ALREADY EXISTS

The command SHOW-FT-PROFILE (see page 198ff) can be used to view the alreadyexisting names. To obtain this information, the command SHOW-FT-PROFILE can beentered without operands.

PASSWORD=With PASSWORD, you enter the FTAC password which authorizes you to issue FTACcommands on your user ID, if such a password was defined in your admission set.

PASSWORD=*NONENo FTAC password is required.

PASSWORD=<c-string 1..8 with-low> / <x-string 1..16>This FTAC password is required.

PASSWORD=*SECRETThe system prompts you to enter the password. The input does not appear on the screen.

TRANSFER-ADMISSION=With TRANSFER-ADMISSION, you define transfer admission. If this transfer admission isentered in an FTP-LOGON instead of the LOGON admission, then the access rights aredefined in this admission profile apply. This transfer admission must be unique in the entireopenFT system so that there are no conflicts with other transfer admissions defined by otherFTAC users for other access rights.

If the transfer admission that you have selected has already been assigned, FTAC rejectsthe command with the message:

FTC0101 CMD REJECTED. TRANSFER-ADMISSION ALREADY EXISTS

, FILE-NAME = *NOT-RESTRICTED / *EXPANSION(...) / *POSIX(NAME=posix_pathname_1..219)

*EXPANSION(...)

PREFIX = <full-filename 1..53> / <partial-filename 2..53> / <c-string 1..220 with-low>

, FILE-PASSWORD = *NOT-RESTRICTED / *NONE / <c-string 1...4> / <x-string 1...8> /

<integer -2147483648...2147483647> / *SECRET

, WRITE-MODE = *NOT-RESTRICTED / NEW-FILE / REPLACE-FILE / EXTEND-FILE

, FT-FUNCTION = *NOT-RESTRICTED / list-poss(3):

TRANSFER-FILE / MODIFY-FILE-ATTRIBUTES / READ-DIRECTORY

U41096-J-Z125-2-76 151


TRANSFER-ADMISSION=*NOT-SPECIFIEDThis entry is used to set up a profile without a transfer admission. Such a profile remainsinaccessible until a valid transfer admission has been assigned.

TRANSFER-ADMISSION=<alphanum-name 8..32>(...) /<c-string 8..32 with-low>(...) / <x-string 15..64>(...)

The character string must be entered as the transfer admission in the FTP request. Thealphanumeric entry in stored internally in lowercase letters.

VALID=*YESThe transfer admission is valid.

VALID=*NOThe transfer admission is not valid. With this entry, users can be denied access to theprofile.

USAGE=*PRIVATEAccess to your profile is denied for security reasons if someone with another user IDmakes a repeated attempt to specify the same TRANSFER ADMISSION that you havealready used.

USAGE=*PUBLICAccess to your profile is not denied if another user happens to "discover" yourTRANSFER-ADMISSION. "Discovery" means that another user ID attempted to specifythe same TRANSFER ADMISSION twice. This is rejected for security reasons.

EXPIRATION-DATE=*NOT-RESTRICTEDThe use of this transfer admission is not subject to a time restriction.

EXPIRATION-DATE=<date 8..10>The use of the transfer admission is only possible until the given date (max.31.12. 2020). The entry must be made in the form YYYY-MM-DD or YY-MM-DD.

TRANSFER-ADMISSION=*SECRETThe system prompts you to enter the transfer admission; however, this does not appear onthe screen. The operands VALID, USAGE and EXPIRATION-DATE can also be secretlyentered in this case.

PRIVILEGED=*NOThe admission profile is not privileged.FTP requests that are processed with a privileged admission profile are not subject to therestrictions set for MAX-ADM-LEVEL in the admission set. Only the FTAC administrator isallowed to assign a privileged status to profiles.

152 U41096-J-Z125-2-76


IGNORE-MAX-LEVELS=With IGNORE-MAX-LEVELS, you can determine for which of the six basic functions therestrictions of the admission set should be ignored. The user’s MAX-USER-LEVELS can beexceeded in this way. The MAX-ADM-LEVELS in the admission set can only beeffectively exceeded with an admission profile which has been designated as privileged bythe FTAC administrator. The FTAC user can set up an admission profile for himself forspecial tasks (e.g. sending a certain file to a partner system with which he normally is notallowed to conduct an FTP transfer), which allows him to exceed the admission set. Thisprofile must be explicitly assigned a privileged status by the FTAC administrator.If you enter IGNORE-MAX-LEVELS=*YES, the settings for all the basic functions areignored. If you wish to ignore the admission set for specific basic functions, you need to dothis with the operands explained below.

IGNORE-MAX-LEVELS=*NOFTP requests that are processed with the admission profile are subject to the restrictions ofthe admission set.

IGNORE-MAX-LEVELS=*YES*YES allows you to communicate with partner systems whose security level exceeds thespecifications of the admission set. If your profile does not have privileged status, you canonly disregard the MAX-USER-LEVELS in the admission set, not the MAX-ADM-LEVELS.The current MAX-USER-LEVELS and MAX-ADM-LEVELS settings can be determined byusing the command SHOW-FT-ADMISSION-SET (see example on page 182).

IGNORE-MAX-LEVELS=*PARAMETERS(...)The following operands can be used to selectively deactivate the default settings for theindividual basic functions.

INBOUND-SEND=*NOThe maximum security level that can be reached with the basic function "inbound send"is determined by the admission set.

INBOUND-SEND=*YESFor the basic function "inbound send", you can use this admission profile to disregardthe MAX-USER-LEVELS. If your profile is privileged, you are also not held tothe restrictions of the MAX-ADM-LEVELS. In addition, the partial component "displayfile attributes" of the basic function "inbound file management" can be used.

INBOUND-RECEIVE=*NOThe maximum security level that can be reached with the basic function "inboundreceive" is determined by the admission set.

U41096-J-Z125-2-76 153


INBOUND-RECEIVE=*YESWith this profile, you can disregard your settings for "inbound receive" in theMAX-USER-LEVELS. If your profile is privileged, you are also not held tothe restrictions of the MAX-ADM-LEVELS. In addition, the following partial componentsof the basic function "inbound file management" can be used:– delete files, as long as the file attributes are set accordingly,– modify file attributes, if the basic function "inbound file management" was admitted

in the admission set or in the admission profile.

INBOUND-MANAGEMENT=*NOThe maximum security level that can be reached with the basic function "inbound filemanagement" is determined by the admission set.

INBOUND-MANAGEMENT=*YESFor the basic function "inbound file management", you can use this admission profile todisregard the MAX-USER-LEVELS. If your profile is privileged, you are also not held tothe restrictions of the MAX-ADM-LEVELS. The partial component "modify fileattributes" of the basic function "inbound file management" only functions if the basicfunction "inbound receive" was permitted in the admission set or admission profile.

USER-ADMISSION=With USER-ADMISSION, the user specifies the user ID under which the profile is to besaved. FTP requests that work with this admission profile access the given user ID in thelocal system.

USER-ADMISSION=*OWNFor USER-IDENTIFICATION and ACCOUNT, the specifications for your user ID and youraccount number are taken from your LOGON authorization. A BS2000 password is onlytaken from your LOGON authorization when an FTP request accesses the admissionprofile.

USER-ADMISSION=*PARAMETERS(...)You can also enter the individual components of the user ID. This allows you to keep FTPrequests which work with this admission profile under a different account number, forexample. Alternatively, a password can be set in the admission profile. FTP requests whichwork with this admission profile will then only function if their current LOGON passwordcorresponds to the preset password.

USER-IDENTIFICATION=*OWN / <name 1..8>With USER-IDENTIFICATION, you enter your user ID in BS2000. Both entries have thesame effect.

ACCOUNT=With ACCOUNT, you enter the account number under which an FTP request is to beaccounted when working with this admission profile.

ACCOUNT=*OWNThe account number is taken from your LOGON authorization.

154 U41096-J-Z125-2-76


ACCOUNT=<alphanum-name 1..8>An FTP request should be accounted under the account number specified when itaccesses this admission profile. You can enter any account number associated withyour user ID.

PASSWORD=With PASSWORD, you enter the BS2000 password associated with your user ID.

PASSWORD=*OWNWhen an FTP request refers to this admission profile, FTAC uses the BS2000 passwordvalid for your user ID at that moment. This prevents you from having to modify theadmission profile if the BS2000 password is changed.

PASSWORD=*NONENo BS2000 password is required for the user ID.

PASSWORD=<c-string 1..8> / <x-string 1..16>When an FTP request accesses the admission profile, the password specified iscompared with the current LOGON password. If the two do not correspond, the FTPrequest is rejected.

PASSWORD=*SECRETThe system prompts you to enter the password. The entry does not appear on thescreen.

INITIATOR=*REMOTESince FTP requests are always treated as *REMOTE, the admission profiles for FTP mustalways have the *REMOTE setting. If the same profile is also used for openFT, the setting(*LOCAL,*REMOTE) would also be allowed, for example.

TRANSFER-DIRECTION=With TRANSFER-DIRECTION, you determine which transfer direction may be used withthis admission profile. The transfer direction is always seen from the viewpoint of theBS2000 FTP server on which the admission profile was defined.

TRANSFER-DIRECTION=*NOT-RESTRICTEDWith this admission profile, data can be transferred from the client to the server, and viceversa.

TRANSFER-DIRECTION=*FROM-PARTNERWith this admission profile, data can only be transferred from the client to the server. It isnot possible to display file attributes/directories (partial components of "inbound filemanagement"), i.e. the following server commands are not permitted: cdup, xcup, cwd, xcwd,list, nlst, pwd, xpwd, retr.

U41096-J-Z125-2-76 155


TRANSFER-DIRECTION=*TO-PARTNERWith this admission profile, data can only be transferred from the server to a client system.It is not possible to modify file attributes or delete files (partial components of "inbound filemanagement"), i.e. the following server commands are not permitted: appe, dele, site file,mkd, xmkd, rmd, xrmd, rnfr, stor, stou.

PARTNER-NAME=With PARTNER-NAME, you can specify that this admission profile is to be used only forFTP requests that are processed by a certain client system.

Since the maximum length for the partner name entry is only 8 characters, and thenames of FTP clients are usually longer, it is advisable to avoid using this operand.

PARTNER-NAME=*NOT-RESTRICTEDThe scope of this admission profile is not restricted to FTP requests with certain partnersystems.

PARTNER-NAME=list-poss(50): <name 1..8>The admission profile only permits those FTP requests that are processed with thespecified client systems. A maximum of 50 client systems may be specified.

MAX-PARTNER-LEVEL=With MAX-PARTNER-LEVEL, a maximum security level can be specified. In the case ofFTP requests, the client system is always assigned a security level of 100.

MAX-PARTNER-LEVEL=*NOT-RESTRICTEDIf FTP requests are processed with this admission profile, then the highest accessiblesecurity level is determined by the admission set.

MAX-PARTNER-LEVEL=<integer 0..100>When you set MAX-PARTNER-LEVEL Î 99, you (temporarily) prevent access to theadmission profile for FTP requests.

FILE-NAME=With FILE-NAME, you determine which files or library members under your user ID may beaccessed by FTP requests that use this admission profile.

FILE-NAME=*NOT-RESTRICTEDThe admission profile permits unrestricted access to all files of the user ID.

FILE-NAME=*EXPANSION(PREFIX=<full-filename 1..53> / <partial-filename 2..53> /<c-string 1..220 with-low>)

This entry can be used to restrict access to a number of files which all begin with the sameprefix. If a file name is entered in an FTP request that uses this admission profile, FTACplaces the prefix defined with EXPANSION in front of this file name. The FTP request is thenpermitted to access the file PrefixFilename.

i

156 U41096-J-Z125-2-76


It is not possible to switch between the POSIX and DMS file systems. If the prefix containsa "/" or begins with ".", only the POSIX file system can be accessed. In all other cases, onlythe DMS file system can be accessed.

Example:

PREFIX=DAGOBERT.; an FTP request in which the file name BOURSE is specifiedaccesses the file DAGOBERT.BOURSE .

Please note that the part of a DMS file name specified in the FTP command still has to beof the type <full-filename>.

FILE-PASSWORD=With FILE-PASSWORD, you can enter a password for files into the admission profile. TheFTAC functionality then only permits access to files which are protected with this passwordand to unprotected files. When a FILE-PASSWORD is specified in an admission profile, thepassword may no longer be specified in an FTP request which uses this admission profile.This allows you to grant users on remote systems access to certain files without having todivulge the file passwords.

FILE-PASSWORD=*NOT-RESTRICTEDThe admission profile permits access to all files. If a password is set for a file, then it mustbe specified in the FTP request.

FILE-PASSWORD=*NONEThe admission profile only permits access to files without file passwords.

FILE-PASSWORD=<c-string 1..4> / <x-string 1..8> /<integer -2147483648..2147483647>

The admission profile only permits access to files which are protected with the specifiedpassword and to unprotected files. The password which has already been specified in theprofile may not be repeated in the FTP request.

FILE-PASSWORD=*SECRETThe system prompts you to enter the password. The entry does not appear on the screen.

WRITE-MODE=With WRITE-MODE, you determine the write mode that applies to this FTP request.WRITE-MODE is only effective if the receive file is on the same system on which theadmission profile was defined. In FTP commands, the write mode is not specified explicitly,but it is an implicit part of the FTP command:

appe *EXTEND-FILE

stor, rnfr, site file, dele, rmd, xrmd *REPLACE-FILE

stou *NEW-FILE

U41096-J-Z125-2-76 157


WRITE-MODE=*NOT-RESTRICTEDIn an FTP request which accesses this admission profile, all FTP write modes may be usedwithout restrictions.

WRITE-MODE=*NEW-FILEThe dele, rmd and xrmd FTP commands are not permitted.

WRITE-MODE=*REPLACE-FILEThe stou FTP command is not permitted.

WRITE-MODE=*EXTEND-FILEThe stor, stou, dele, rmd and xrmd FTP commands are not permitted.

FT-FUNCTION=This operand enables you to restrict the validity of the profile to certain FTP functions(=file transfer and file management functions).

FT-FUNCTION=*NOT-RESTRICTEDThe full scope of FTP functions is available.

FT-FUNCTION=(*TRANSFER-FILE, *MODIFY-FILE-ATTRIBUTES,*READ-DIRECTORY)

The following functions are available:

*TRANSFER-FILEThe admission profile may be used for the "transfer files", "view file attributes" and"delete files" functions.

The following server commands are not permitted:

list, nlist, pwd, xpwd, cwd, xcwd, cdup, xcup, rnfr, size, mdtm

*MODIFY-FILE-ATTRIBUTESThe admission profile may be used for the "view file attributes" and "modify fileattributes" functions.


retr, stor, appe, stou, dele, list, nlist, pwd, xpwd, cwd, xcwd, cdup, xcup, size, mdtm

*READ-DIRECTORYThe admission profile may be used for the "view directories" and "view file attributes"functions.


retr, stor, appe, stou, dele

158 U41096-J-Z125-2-76


Example

Dagobert Duck wants to create an admission profile for the following purpose:

Donald Duck, employee at the Duck Goldmine, has his own BS2000 computer. He has totransfer monthly reports on a regular basis to his boss Dagobert‘s computer, DAGODUCK,using FTP. The file needs to have the prefix MONTHLYREPORTS. Since Dagobert’sadmission set does not permit any "nbound" requests, he needs to assign the profilea privileged status (he is allowed to do this, since he is an FTAC administrator).

The command required to created such an admission profile is as follows:

/CREATE-FT-PROFILE NAME=GOLDMOBE, -/ TRANSFER-ADMISSION='monthlyreportfortheboss', -/ PRIVILEGED=*NO, -/ IGNORE-MAX-LEVELS=*YES, -/ TRANSFER-DIRECTION=*FROM-PARTNER, -/ FILE-NAME=*EXPANSION(PREFIX=MONTHLYREPORTS.), -/ WRITE-MODE=*REPLACE-FILE

The short form of this command is:

/CRE-FT-PROF GOLDMOBE,TRANS-AD='monthlyreportfortheboss', -/ PRIV=*YES,IGN-MAX-LEV=*YES,TRANS-DIR=*FROM, -/ FILE-NAME=*EXP(PREF=MONTHLYREPORTS.),WRITE=*REPL

Donald Duck, who keeps the monthly report of Goldmine on his BS2000 computer in thefile NOTHINGBUTLIES, can use the following FTP command of the BS2000 FTP client tosend it to the central computer DAGODUCK:

→ ftp> open DAGODUCKConnected to DAGODUCK, port 21.220 DAGODUCK FTP server (Version V03.0A00, Mar 12 1999 20:34:27) ready.Name (DAGODUCK:DONADUCK):

→ *$FTAC331 Send your FTAC transfer admission as passwordPassword (DAGODUCK:$FTAC):

→ *monthlyreportfortheboss230 $FTAC login ok, access restrictions apply.

→ ftp> put NOTHINGBUTLIES GOLDMINE200 PORT command successful.150 Opening data connection for GOLDMINE (139.25.24.2,4102).22595 bytes sent in 0.06 seconds (3.6e+02 Kbytes/s)226 Transfer complete.(SAM-IO)

→ ftp> bye221 Goodbye.

U41096-J-Z125-2-76 159


Command return codes:

(SC2) SC1 Maincode Meaning/Guaranteed messages

0 0 FTC0051 A user ID with the same name already exists in the system.0 0 FTC0056 Transfer admission is denied.0 64 FTC0100 An FT profile with the same name already exists.0 64 FTC0101 An FT profile with the same Transfer-Admission already

exists.0 64 FTC0150 The access password is missing.0 64 FTC0153 The owner identification entered is not the own user ID.0 64 FTC0157 No authorization to create the profile.0 64 FTC0172 The specified User Admission does not exist in the system.0 64 FTC0173 The specified Processing Admission does not exist in the

system.0 64 FTC0178 The specified partner name occurs several times.0 64 FTC0182 The maximum length for partner names has been exceeded.0 64 FTC0200 The total length of the two follow-up processing commands is

too long.0 64 FTC0255 A system error has occurred.

SC1/2 = Subcode 1/2 in decimal formMore information can be found in the “Messages” chapter.

160 U41096-J-Z125-2-76

DELETE-FT-PROFILE Delete admission profile

4.2.8 DELETE-FT-PROFILE - Delete admission profile

With the command DELETE-FT-PROFILE, you can delete all admission profiles for whichyou are the owner. You should go through your admission profiles on a regular basis anddelete all those which are no longer required so that they don’t take up memory.With SHOW-FT-PROFILE (see from page 198), you can view the profiles and decide whichones are no longer needed.


Operands

NAME=With NAME, you can access the admission profile to be deleted by its name.

NAME=*ALLWith *ALL, you can delete all admission profiles. The FTAC user can delete all of hisadmission profiles with this operand, unless he selects a special profile withSELECT-PARAMETER.

NAME=<alphanum-name 1..8>You want to delete the admission profile with the specified name.

PASSWORD=With PASSWORD, you enter the FTAC password that allows you to use FTAC commandswith your user ID.


PASSWORD=<c-string 1..8 with-low> / <x-string 1..16>Entry of the corresponding FTAC password.

DELETE-FT-PROFILE - showing operands relevant for FTP

NAME = *ALL / <alphanum-name 1..8>


, SELECT-PARAMETER = *OWN / *PARAMETERS(...)

*PARAMETERS(...)

TRANSFER-ADMISSION = *ALL / *NOT-SPECIFIED / <alphanum-name8..32> /

<c-string 8..32 with-low> / <x-string 15..64> / *SECRET

, OWNER-IDENTIFICATION = *OWN / <name 1..8>

U41096-J-Z125-2-76 161

Delete admission profile DELETE-FT-PROFILE

PASSWORD=*SECRETThe system prompts you to enter the password. The entry does not appear on the screen.

SELECT-PARAMETER=With SELECT-PARAMETER, you can enter selection criteria for the admission profiles tobe deleted.

SELECT-PARAMETER=*OWNWith *OWN, you delete your own admission profiles.

SELECT-PARAMETER=*PARAMETERS(...)With this structure, you can enter individual selection criteria.

TRANSFER-ADMISSION=With TRANSFER-ADMISSION, you can use the transfer admission of an admissionprofile as a selection criterion for deletion.

TRANSFER-ADMISSION=*ALLYou want to delete admission profiles irrespective of the TRANSFER-ADMISSION.

TRANSFER-ADMISSION=*NOT-SPECIFIEDYou want to delete admission profiles for which no transfer admission is specified.

TRANSFER-ADMISSION=<alphanum-name 8..32> /<c-string 8..32 with-low> / <x-string 15..64>

You want to delete the admission profile that is accessed with this transfer admission.The FTAC user can only enter the transfer admissions of his/her own admission profiles.

TRANSFER-ADMISSION=*SECRETThe system prompts you to enter the transfer admission.The entry does not appear onthe screen.

OWNER-IDENTIFICATION =*OWN / <name 1..8>OWNER-IDENTIFICATION permits the FTAC user to delete his/her own admissionprofiles under this user ID. Both entries have the same effect.

Command return codes

(SC2) SC1 Maincode Meaning/Guaranteed messages1 0 FTC0053 No FT profile exists with these criteria.0 64 FTC0150 The access password is missing.0 64 FTC0153 The owner identification entered is not the own user ID.


162 U41096-J-Z125-2-76

MODIFY-FT-ADMISSION-SET Modify admission set

4.2.9 MODIFY-FT-ADMISSION-SET - Modify admission set

The MODIFY-FT-ADMISSION-SET command can be used to modify the admission set foryour user ID. You may access two components of the admission set:

– You can define a password to be entered for almost all subsequent FTAC commands(exception: the /SHOW... commands). This prevents other users who are working withyour user ID from entering FTAC commands.

It is not possible to have an FTAC password output. If an FTAC user forgets his/herFTAC password, only the FTAC administrator can delete or modify the password.

– You can modify the limiting values for the maximum security levels (the MAX-USER-LEVELS) that can be accessed from your user ID. The limiting values set by the FTACadministrator (MAX-ADM-LEVELS) cannot be disabled.The MAX-USER-LEVELS only work if they are higher (i.e. more restrictive) than theMAX-ADM-LEVELS.


MODIFY-FT-ADMISSION-SET - showing operands relevant for FTP

USER-IDENTIFICATION = *OWN / <alphanum-name 1...8>

, PASSWORD = *NONE / <c-string 1...8 with-low> / <x-string 1...16> / *SECRET

, SELECT-PARAMETER = *ALL

, NEW-PASSWORD = *OLD / *NONE / <c-string 1...8 with-low> / <x-string 1...16> / *SECRET

, MAX-LEVELS = *UNCHANGED / *STD / <integer 0...100> / *PARAMETERS(...)

*PARAMETERS(...)

INBOUND-SEND = *UNCHANGED / *STD / <integer 0...100>

, INBOUND-RECEIVE = *UNCHANGED / *STD / <integer 0...100>

, INBOUND-MANAGEMENT = *UNCHANGED / *STD / <integer 0...100>

i

U41096-J-Z125-2-76 163

Modify admission set MODIFY-FT-ADMISSION-SET

Operands

USER-IDENTIFICATION=Specifies the user ID whose admission set is to be modified.

USER-IDENTIFICATION=*OWNThe admission set for the user ID under which you are currently working is to be modified.

USER-IDENTIFICATION=<alphanum-name 1..8>The admission set for this user ID is to be modified. As an FTAC user, you can only enteryour own user ID here.

PASSWORD=With PASSWORD, you enter the FTAC password which authorizes you to use FTACcommands, if such a password was defined in your admission set. An FTAC password isset with the operand NEW-PASSWORD.

PASSWORD=*NONENo FTAC password is required for this admission set.

PASSWORD=<c-string 1..8 with-low> / <x-string 1..16>This password authorizes the use of FTAC commands under the corresponding user ID.

PASSWORD=*SECRETThe system prompts you to enter the password. However, the password does not appearon the screen.

SELECT-PARAMETER=*ALLIn later FTAC versions, it will be possible to enter additional selection criteria here.

NEW-PASSWORD=With this operand, you change the FTAC password. If such an FTAC password has alreadybeen set, it must be used for almost all FTAC commands on the user ID for this admissionset (except: the SHOW...- commands). This is done using the operand PASSWORD in therespective commands.

NEW-PASSWORD=*OLDThe FTAC password remains unchanged.

NEW-PASSWORD=*NONENo FTAC password is required for the user ID associated with this admission set.

NEW-PASSWORD=<c-string 1..8 with-low> / <x-string 1..16>Enter the new FTAC password.

NEW-PASSWORD=*SECRETThe system prompts you to enter the password. The input does not appear on the screen.

164 U41096-J-Z125-2-76


MAX-LEVELS=With this operand, you determine which security level(s) can be reached with which basicfunctions from the user ID of this admission set. You may optionally set one security levelfor all basic functions or different security levels for each basic function. The MAX-USER-LEVELS for this admission set are defined by the FTAC user; the MAX-ADM-LEVELS aredefined by the FTAC administrator. FTAC runs authorization checks on the basis of thelowest specified security level in each case. FTAC users may reduce but not exceed thevalues set for them by the FTAC administrator.

MAX-LEVELS=*UNCHANGEDThe security levels defined in this admission set are to remain unchanged.

MAX-LEVELS=*STDWith this setting, you specify that the values of the default admission set are to be used forfor this admission set. This causes the admission set to be deleted from the admission file.This is possible even if the user ID has already been deleted.

MAX-LEVELS=<integer 0..100>With this value, you can set a maximum security level for all basic functions. A value Î 99means that no FTP access checked via FTAC is possible on this user ID until further notice(i.e. until the admission set is modified again).

MAX-LEVELS=*PARAMETERS(...)With this structure, you can set a maximum security level for each of the basic functions.FTP partners always have a security level of 100.

INBOUND-SEND=Sets the maximum security level for the basic function "inbound send". All partnersystems with this security level or lower can request files from the owner of theadmission set.

INBOUND-SEND=*UNCHANGEDThe value for INBOUND-SEND remains unchanged.

INBOUND-SEND=*STDFor INBOUND-SEND, the value from the default admission set is used.

INBOUND-SEND=<integer 0..100>For INBOUND-SEND, this maximum security level is entered in the admission set. Avalue of Î 99 means that INBOUND-SEND is not possible on this ID. In this case, theretr server command is not permitted.

INBOUND-RECEIVE=Sets the maximum security level for the basic function "inbound receive". All partnersystems with this security level or lower may send files to the owner of the admissionset.

INBOUND-RECEIVE=*UNCHANGEDThe value for INBOUND-RECEIVE remains unchanged.

U41096-J-Z125-2-76 165

Modify admission set MODIFY-FT-ADMISSION-SET

INBOUND-RECEIVE=*STDFor INBOUND-RECEIVE, the value from the default admission set is used.

INBOUND-RECEIVE=<integer 0..100>For INBOUND-RECEIVE, this maximum security level is entered in the admission set.A value of Î 99 means that INBOUND-RECEIVE is not possible on this ID. In this case,the following server commands are not permitted: stor, stou, appe, rnfr, dele, site file.

INBOUND-MANAGEMENT=Sets the maximum security level for the basic function "inbound file management". Allpartner systems with this security level or lower may include the modification of fileattributes and the querying of directories as part of their FTP request.

INBOUND-MANAGEMENT=*UNCHANGEDThe value for INBOUND-MANAGEMENT remains unchanged.

INBOUND-MANAGEMENT=*STDFor INBOUND-MANAGEMENT, the value from the default admission set is used.

INBOUND-MANAGEMENT=<integer 0..100>For INBOUND-MANAGEMENT, this maximum security level is entered in the admissionset. A value of Î 99 means that INBOUND-MANAGEMENT is not possible on this ID. Inthis case, the following server commands are not permitted: cwd, xcwd, list, nlst, mkd,xmkd, rmd, xrmd, pwd, xpwd, cdup, xcup, rnfr, size.

166 U41096-J-Z125-2-76


Example

Donald needs information on his admission sets:

→ /SHOW-FT-ADMISSION-SET

Short form:

→ /SHOW-FT-ADM

He receives the following output:% MAX. USER LEVELS MAX. ADM LEVELS ATTR% USER-ID OBS OBR IBS IBR IBP IBF OBS OBR IBS IBR IBP IBF % DUCKTAIL 100 100 100 100 100 100 80 80 100 100 80 100

Donald now wants to deny access to the basic function "inbound send" and thus preventfiles from being read on his user ID.

→ /MODIFY-FT-ADMISSION-SET MAX-LEVELS=*PARAMETERS(INBOUND-SEND=99)

The short form of this command is:

→ /MOD-FT-ADM MAX-LEV=(IN-SEND=99)

To verify the new setting, Donald now displays his admission again:

→ /SHOW-FT-ADM% MAX. USER LEVELS MAX. ADM LEVELS ATTR% USER-ID OBS OBR IBS IBR IBP IBF OBS OBR IBS IBR IBP IBF % DUCKTAIL 100 100 99 100 100 100 80 80 100 100 80 100


(SC2) SC1 Maincode Meaning/Guaranteed messages0 0 FTC0050 The set security level exceeds the administrator‘s limit and

will remain invalid until the administrator´s limit is raisedaccordingly.

0 64 FTC0150 Authorization password is missing.0 64 FTC0151 Only the administrator or owner is permitted to make this

modification.0 64 FTC0152 The user ID entered is not the user‘s own.0 64 FTC0175 The operand "NEW-PASSWORD" may not be entered for

*STD.0 64 FTC0176 The user ID entered does not exist in the system.0 64 FTC0255 A system error occurred.


U41096-J-Z125-2-76 167

Modify admission profile MODIFY-FT-PROFILE

4.2.10 MODIFY-FT-PROFILE - Modify admission profile

The command MODIFY-FT-PROFILE can be used by any FTAC user to modify his/heradmission profile.

In a privileged admission profile, an FTAC user can only modify the operandsTRANSFER-ADMISSION and PRIVILEGED.


MODIFY-FT-PROFILE - showing operands relevant for FTP




*PARAMETERS(...)

TRANSFER-ADMISSION = *ALL / *NOT-SPECIFIED / <alphanum-name 8..32> /

<c-string 8..32 with-low> / <x-string 15..64> /

*SECRET

, OWNER-IDENTIFICATION = *OWN / <name 1..8>

, NEW-NAME = *OLD / <alphanum-name 1..8>

, TRANSFER-ADMISSION = *UNCHANGED / *NOT-SPECIFIED / *OLD-ADMISSION(...) /

<alphanum-name 8..32>(...) / <c-string 8..32 with-low>(...) /

<x-string 15..64>(...) / *SECRET

*OLD-ADMISSION(...)

<alphanum-name 8..32>(...) / <c-string 8..32 with-low>(...) / <x-string 15..64>(...)

VALID = *YES / *NO / *UNCHANGED

, USAGE = *PRIVATE / *PUBLIC / *UNCHANGED

, EXPIRATION-DATE = *NOT-RESTRICTED / <date 8..10> / *UNCHANGED

, PRIVILEGED = *UNCHANGED / *NO

, IGNORE-MAX-LEVELS = *UNCHANGED / *NO / *YES / *PARAMETERS(...)

168 U41096-J-Z125-2-76

MODIFY-FT-PROFILE Modify admission profile

Operands

NAME=With NAME, you determine the name of the admission profile to be modified.

NAME=*ALLUse this to modify all your admission profiles at the same time.

NAME=<alphanum-name 1..8>Use this to modify the admission profile with this name.

*PARAMETERS(...)

, INBOUND-SEND = *UNCHANGED / *NO / *YES

, INBOUND-RECEIVE = *UNCHANGED / *NO / *YES

, INBOUND-MANAGEMENT = *UNCHANGED / *NO / *YES

, USER-ADMISSION = *UNCHANGED / *OWN / *PARAMETERS(...)

*PARAMETERS(...)

USER-IDENTIFICATION = *OWN / <name 1..8>

, ACCOUNT = *OWN / *NOT-SPECIFIED / <alphanum-name 1..8>

, PASSWORD = *OWN / *NOT-SPECIFIED / <c-string 1..8> / <x-string 1..16> / *NONE / *SECRET

, INITIATOR = *UNCHANGED / *REMOTE

, TRANSFER-DIRECTION = *UNCHANGED / *NOT-RESTRICTED / FROM-PARTNER / TO-PARTNER

, PARTNER-NAME = *UNCHANGED / *NOT-RESTRICTED / *ADD(...) / *REMOVE(...) /

list-poss(50): <name 1..8>

*ADD(...)

NAME = list-poss(50): <name 1..8>

*REMOVE(...)

NAME = list-poss(50): <name 1..8>

, MAX-PARTNER-LEVEL = *UNCHANGED / *NOT-RESTRICTED / <integer 0..100>

, FILE-NAME = *UNCHANGED / *NOT-RESTRICTED / *EXPANSION(...)

*EXPANSION(...)

PREFIX = <full-filename 1..53> / <partial-filename 2..53> / <c-string 1..220 with-low>

, FILE-PASSWORD = *UNCHANGED / *NOT-RESTRICTED / *NONE / <c-string 1...4> / <x-string 1...8> /

<integer -2147483648...2147483647> / *SECRET

, WRITE-MODE = *UNCHANGED / *NOT-RESTRICTED / *NEW-FILE / *REPLACE-FILE / *EXTEND-FILE

, FT-FUNCTION = *UNCHANGED / *NOT-RESTRICTED / list-poss(3):

*TRANSFER-FILE / *MODIFY-FILE-ATTRIBUTES / *READ-DIRECTORY

U41096-J-Z125-2-76 169


PASSWORD=With PASSWORD, you enter the FTAC password which authorizes you to use FTACcommands on your user ID, if such a password has been defined in your admission set.


PASSWORD=<c-string 1..8 with-low> / <x-string 1..16>This FTAC password is required.

PASSWORD=*SECRETIn interactive mode, you can use this operand to ensure that the FTAC password will notappear on the screen. The system prompts you to enter the password, but the entry doesnot appear on the screen.

SELECT-PARAMETER=With SELECT-PARAMETER, you can specify a transfer admission. You then modify theadmission profile that is accessed with this transfer admission.

SELECT-PARAMETER=*OWNUse this to modify your own admission profile.

SELECT-PARAMETER=*PARAMETERS(...)With this structure, you can specify the selection criteria for the profiles you want to modify.

TRANSFER-ADMISSION=Entering the TRANSFER-ADMISSION here makes it a selection criterion for theadmission profiles that you want to modify.

TRANSFER-ADMISSION=*ALLAll your admission profiles are modified, irrespective of the transfer admission.

TRANSFER-ADMISSION=*NOT-SPECIFIEDOnly admission profiles without a defined transfer admission are to be modified.


The admission profile with this transfer admission is to be modified.

TRANSFER-ADMISSION=*SECRETThe system prompts you to enter the transfer admission, but does not display your entryon the screen.

OWNER-IDENTIFICATION=*OWN / <name 1..8>OWNER-IDENTIFICATION permits the FTAC user to modify his/her own admissionprofile. Both entries have the same effect.

170 U41096-J-Z125-2-76


NEW-NAME=With NEW-NAME, you assign your admission profile a new name (or not).

NEW-NAME=*OLDThe name of the admission profile remains unchanged.

NEW-NAME=<alphanum-name 1..8>This is the new name of the admission profile. This name must be unique among all theadmission profiles on your user ID. If an admission profile with this name already exists,FTAC rejects the command with the following message:

FTC0100 CMD REJECTED. FT-PROFILE ALREADY EXISTS

The command SHOW-FT-PROFILE (see from page 198) can be used to obtain informationon the already assigned names. It is sufficient to enter SHOW-FT-PROFILE withoutoperands for this information.

TRANSFER-ADMISSION=With TRANSFER-ADMISSION, you can modify the transfer admission associated with anadmission profile. You must ensure that the transfer admission is unique within your openFT(BS2000) system. If the transfer admission you have selected already exists, FTAC rejectsthe command with the following message:

FTC0101 CMD REJECTED. TRANSFER-ADMISSION ALREADY EXISTS

TRANSFER-ADMISSION=*UNCHANGEDThe transfer admission remains unchanged.

TRANSFER-ADMISSION=*NOT-SPECIFIEDNo transfer admission is set, and existing transfer admissions, if any, are invalidated. Thisblocks the profile.

TRANSFER-ADMISSION=*OLD-ADMISSION(...)The transfer admission itself remains unchanged, but the options may be changed (incontrast to the entry TRANSFER-ADMISSION=*UNCHANGED). A description of thevalues in brackets (VALID=, USAGE= and EXPIRATION-DATE=) is given below.

TRANSFER-ADMISSION=<alphanum-name 8..32>(...) /<c-string 8..32 with-low>(...) / <x-string 15..64>(...)

The character string must be entered as a transfer admission in the FTP request. Thealphanumeric input is always stored in lowercase letters.

VALID=*UNCHANGEDThe value remains unchanged.

VALID=*YESThe transfer admission is valid.

VALID=*NOThe transfer admission is not valid. The profile can be blocked with this entry.

U41096-J-Z125-2-76 171


USAGE=*UNCHANGEDThe value remains unchanged.

USAGE=*PRIVATEAccess to your profile is denied for security reasons whenever another user ID makesa repeated attempt to specify the same TRANSFER ADMISSION that you have alreadyused.

USAGE=*PUBLICAccess to your profile is not denied if another user happens to "discover" yourTRANSFER-ADMISSION. "Discovery" means that another user ID tried tospecify the same TRANSFER ADMISSION twice. This is rejected for security reasons.

EXPIRATION-DATE=*UNCHANGEDThe value remains unchanged.

EXPIRATION-DATE=*NOT-RESTRICTEDThe use of this transfer admission is not subject to a time restriction.

EXPIRATION-DATE=<date 8..10>The use of the transfer admission is only possible until the given date (max.31.12. 2020). The entry must be made in the form YYYY-MM-DD or YY-MM-DD.

TRANSFER-ADMISSION=*SECRETThe system prompts you to enter the transfer admission, but does not display your entry onthe screen. The operands VALID, USAGE and EXPIRATION-DATE can also be secretlyentered in this case.

PRIVILEGED=With PRIVILEGED, the FTAC administrator can privilege the admission profile of any FTACuser. FTP requests that are processed with a privileged status are not subject to therestrictions for MAX-ADM-LEVEL in the admission set.The FTAC user can only revoke an assigned privileged status.

PRIVILEGED=*UNCHANGEDThe status of this admission profile remains unchanged.

PRIVILEGED=*NOWith *NO, you can revoke the privileged status.

172 U41096-J-Z125-2-76


IGNORE-MAX-LEVELS=With IGNORE-MAX-LEVELS, you can determine for which of the six basic functions therestrictions of the admission set should be ignored. The MAX-ADM-LEVELS in theadmission set can only be effectively exceeded with an admission profile that has beendesignated as privileged by the FTAC administrator. The FTAC user can set up anadmission profile for himself/herself for special tasks (e.g. sending a certain file to a partnersystem with which he/she is normally not allowed to conduct FTP), which allows him/her toexceed the admission set. This profile must be explicitly assigned a privileged status by theFTAC administrator.If you enter IGNORE-MAX-LEVELS=*YES, the settings for all the basic functions areignored. If you want to ignore the admission set for specific basic functions, you will need todo this with the operands explained further below.

IGNORE-MAX-LEVELS=*UNCHANGEDWith this admission profile, you can access the same security levels as before themodification (unless you have revoked the privileged status with PRIVILEGED=*NO).

IGNORE-MAX-LEVELS=*NOFTP requests that are processed with the admission profile are subject to the restrictions ofthe admission set.

IGNORE-MAX-LEVELS=*YES*YES allows you to communicate with partner systems whose security level exceeds thespecifications of the admission set. If your profile does not have privileged status,you can disregard only the MAX-USER-LEVELS in the admission set, but not theMAX-ADM-LEVELS.The current MAX-USER-LEVELS and MAX-ADM-LEVELS settings can be determined byusing the command SHOW-FT-ADMISSION-SET (see example on page 182).

IGNORE-MAX-LEVELS=*PARAMETERS(...)

INBOUND-SEND=*UNCHANGEDThe maximum security level that can be reached with the basic function"inbound send" remains unchanged.

INBOUND-SEND=*NOThe maximum security level that can be reached with the basic function"inbound send" is determined by the admission set.

INBOUND-SEND=*YESFor the basic function "inbound send", you can use this admission profile to disregardthe MAX-USER-LEVELS. If your profile is privileged, you are also not held to therestrictions of the MAX-ADM-LEVELS. In addition, the partial component "display fileattributes" of the basic function "inbound file management" can be used.

INBOUND-RECEIVE=*UNCHANGEDThe maximum security level that can be reached with the basic function"inbound receive" remains unchanged.

U41096-J-Z125-2-76 173


INBOUND-RECEIVE=*NOThe maximum security level that can be reached with the basic function"inbound receive" is determined by the admission set.

INBOUND-RECEIVE=*YESWith this profile, you can disregard your settings for "inbound receive" in theMAX-USER-LEVELS. If your profile is privileged, you are also not held to therestrictions of the MAX-ADM-LEVELS. In addition, the following partial components ofthe basic function "inbound file management" can be used:– delete files, as long as the file attributes are set accordingly,– modify file attributes, if the basic function "inbound file management" was admitted

in the admission set or in the admission profile.

INBOUND-MANAGEMENT=*UNCHANGEDThe maximum security level that can be reached with the basic function"inbound file management" remains unchanged.

INBOUND-MANAGEMENT=*NOThe maximum security level that can be reached with the basic function "inbound filemanagement" is determined by the admission set.

INBOUND-MANAGEMENT=*YESFor the basic function "inbound file management", you can use this admission profile todisregard the MAX-USER-LEVELS. If your profile is privileged, you are also not held tothe restrictions of the MAX-ADM-LEVELS. The partial component "modify fileattributes" of the basic function "inbound file management" only works if the basicfunction "inbound receive" was permitted in the admission set or admission profile.

USER-ADMISSION=With USER-ADMISSION, you enter the user ID under which the modified profile is to besaved. FTP requests using this profile access the user ID entered on the local system.If the FTAC administrator has created an admission profile for a user, the user can enter theACCOUNT and PASSWORD in the operand USER-ADMISSION by using the commandMODIFY-FT-PROFILE (since he/she is the only person who should know them) before theprofile is used (see command CREATE-FT-PROFILE, page 149).

USER-ADMISSION=*UNCHANGEDThe USER-ADMISSION of this admission profile remains unchanged.

USER-ADMISSION=*OWNFor USER-IDENTIFICATION and ACCOUNT, the specifications for your user ID and youraccount number are taken from your LOGON authorization. A BS2000 password is onlytaken from your LOGON authorization when an FTP request accesses the admissionprofile.

174 U41096-J-Z125-2-76


USER-ADMISSION=*PARAMETERS(...)You can also enter the individual components of the user ID. This allows you to keepFTP requests which use this admission profile under a different account number, forexample. Alternatively, a password can be set in the admission profile. FTP requests whichuse this admission profile will then only function if their current LOGON passwordcorresponds to the preset password.

USER-IDENTIFICATION=USER-IDENTIFICATION identifies your user ID in BS2000.

USER-IDENTIFICATION=*OWNYour user ID is taken from your LOGON authorization.

USER-IDENTIFICATION=<name 1..8><name 1..8> is the user ID with which the profile is to be associated.

ACCOUNT=With ACCOUNT, you enter the account number under which an FTP request is to beaccounted when working with this admission profile.

ACCOUNT=*OWNThe account number is taken from your LOGON authorization.

ACCOUNT=*NOT-SPECIFIEDThe account number is to be specified by the owner of the admission profile. Thisfunction enables the FTAC administrator to set up profiles for user IDs without knowingthe corresponding account numbers.

ACCOUNT=<alphanum-name 1..8>With ACCOUNT, you specify the account number under which an FTP request is to beaccounted when it accesses this admission profile. You can specify any accountnumber associated with the user ID.

PASSWORD=With PASSWORD, you enter the BS2000 password associated with your user ID.

PASSWORD=*OWNWhen an FTP request refers to this admission profile, FTAC uses the BS2000password valid for your user ID at that moment. This prevents you from having to modifythe admission profile if the BS2000 password is changed.

PASSWORD=*NOT-SPECIFIEDThe password is first specified by the owner of the admission profile. This functionpermits the FTAC administrator to set up profiles for foreign user IDs.

PASSWORD=*NONENo BS2000 password is required for the user ID.

U41096-J-Z125-2-76 175


PASSWORD=<c-string 1..8> / <x-string 1..16>When an FTP request accesses the admission profile, the specified password iscompared with the current LOGON password. If the two do not correspond, theFTP request is rejected.

PASSWORD=*SECRETThe system prompts you to enter the password. The entry does not appear on thescreen.

INITIATOR=With INITIATOR, you determine if initiators from local and/or remote systems are permittedto use this admission profile for their FTP requests.

INITIATOR=*UNCHANGEDThe settings in this admission profile remain unchanged.

INITIATOR=*REMOTESince FTP requests are always treated as *REMOTE, the admission profiles for FTP mustalways have the *REMOTE setting. If the same profile is also used for openFT, the setting(*LOCAL,*REMOTE) would also be allowed, for example.

TRANSFER-DIRECTION=With TRANSFER-DIRECTION, you determine which transfer direction may be used withthis admission profile. The transfer direction is always seen from the viewpoint of theBS2000 FTP server on which the admission profile was defined.

TRANSFER-DIRECTION=*UNCHANGEDThe settings in this admission profile remain unchanged.

TRANSFER-DIRECTION=*NOT-RESTRICTEDWith this admission profile, data can be transferred from the client to the server, and viceversa.

TRANSFER-DIRECTION=*FROM-PARTNERWith this admission profile, data can only be transferred from the client to the server. It isnot possible to display file attributes/directories (partial components of "inbound filemanagement"), i.e. the following server commands are not permitted: cdup, xcup, cwd, xcwd,list, nlst, pwd, xpwd, retr, size, mdtm.

TRANSFER-DIRECTION=*TO-PARTNERWith this admission profile, data can only be transferred from the server to a client system.It is not possible to modify file attributes or delete files (partial components of "inbound filemanagement"), i.e. the following server commands are not permitted: appe, dele, site file,mkd, xmkd, rmd, xrmd, rnfr, stor, stou.

176 U41096-J-Z125-2-76


PARTNER-NAME=With PARTNER-NAME, you can specify that this admission profile is to be used only forFTP requests that are processed by a certain client system.

Since the maximum length for the partner name entry is only 8 characters, and thenames of FTP clients are usually longer, it is advisable to avoid using this operand.

PARTNER-NAME=*UNCHANGEDAny existing PARTNER-NAME in the admission profile remains unchanged.

PARTNER-NAME=*NOT-RESTRICTEDThe scope of this admission profile is not restricted to FTP requests with certain partnersystems.

PARTNER-NAME=list-poss(50): <name 1..8>The admission profile only permits those FTP requests which are processed with thespecified client systems. A maximum of 50 client systems can be specified.

PARTNER-NAME=*ADD(list-poss(50): <name 1..8>)With this specification, you can add elements to an existing list of partner systems. Amaximum of 50 client systems can be specified.

PARTNER-NAME=*REMOVE(list-poss(50): <name 1..8>)With this specification, you can remove elements from an existing list of partner systems. Amaximum of 50 client systems can be specified.

MAX-PARTNER-LEVEL=With MAX-PARTNER-LEVEL, a maximum security level can be specified. In the case ofFTP requests, the client system is always assigned a security level of 100.MAX-PARTNER-LEVEL works in conjunction with the admission set. When non-privilegedadmission profiles are used, the access check is executed on the basis of the smallestspecified value.

MAX-PARTNER-LEVEL=*UNCHANGEDThe specification for MAX-PARTNER-LEVEL in this admission set remains unchanged.

MAX-PARTNER-LEVEL=*NOT-RESTRICTEDIf FTP requests are processed with this admission profile, then the highest accessiblesecurity level is determined by the admission set.

MAX-PARTNER-LEVEL=<integer 0..100>When you set MAX-PARTNER-LEVEL Î 99, you (temporarily) prevent access to theadmission profile for FTP requests.

FILE-NAME=With FILE-NAME, you determine which files under your user ID may be accessed by FTPrequests that use this admission profile.

i

U41096-J-Z125-2-76 177


FILE-NAME=*UNCHANGEDThe specifications for FILE-NAME in this admission profile remain unchanged.

FILE-NAME=*NOT-RESTRICTEDThe admission profile permits unrestricted access to all files of the user ID.This entry can be used to restrict access to a number of files which all begin with the sameprefix. If a file name is entered in an FTP request which uses this admission profile,depending on the currently set working directory, FTAC places the prefix defined withEXPANSION before this file name. The FTP request is then permitted to access the filePrefixFilename.

It is not possible to switch between the POSIX and DMS file systems. If the prefix containsa "/" or begins with ".", only the POSIX file system can be accessed. In all other cases, onlythe DMS file system can be accessed.

Example:

PREFIX=DAGOBERT.; an FTP request in which the file name BOURSE is specifiedaccesses the file DAGOBERT.BOURSE.

Please note that the part of a DMS file name which is specified in the FTP command stillhas to be of the type <full-filename>.

FILE-PASSWORD=With FILE-PASSWORD, you can enter a password for files into the admission profile. TheFTAC functionality then only permits access to files which are protected with this passwordand to unprotected files. When a FILE-PASSWORD is specified in an admission profile, thepassword may no longer be specified in an FTP request which uses this admission profile.This allows you to grant users on remote systems access to certain files without having todivulge the file passwords.

FILE-PASSWORD=*UNCHANGEDThe specifications for FILE-PASSWORD in this admission profile remain unchanged.

FILE-PASSWORD=*NOT-RESTRICTEDThe admission profile permits access to all files. If a password is set for a file, then it mustbe specified in the FTP request.

FILE-PASSWORD=*NONEThe admission profile only permits access to files without file passwords.

FILE-PASSWORD=<c-string 1..4> / <x-string 1..8> /<integer -2147483648..2147483647>

The admission profile only permits access to files which are protected with the specifiedpassword and to unprotected files. The password which has already been specified in theprofile may not be repeated in the FTP request.

FILE-PASSWORD=*SECRETThe system prompts you to enter the password. The entry does not appear on the screen.

178 U41096-J-Z125-2-76


WRITE-MODE=With WRITE-MODE, you determine the write mode that applies to this FTP request.WRITE-MODE is only effective if the receive file is on the same system on which theadmission profile was defined. In FTP commands, the write mode is not specified explicitly,but it is an implicit part of the FTP command:

WRITE-MODE=*UNCHANGEDThe specifications for WRITE-MODE in this admission profile remain unchanged.

WRITE-MODE=*NOT-RESTRICTEDIn an FTP request which accesses this admission profile, all FTP write modes may be usedwithout restrictions.

WRITE-MODE=*NEW-FILEThe dele, rmd and xrmd FTP commands are not permitted.

WRITE-MODE=*REPLACE-FILEThe stou FTP command is not permitted.

WRITE-MODE=*EXTEND-FILEThe stor, stou, dele, rmd and xrmd FTP commands are not permitted.

FT-FUNCTION=This operand enables you to restrict the validity of the profile to certain FTP functions (=filetransfer and file management functions).

FT-FUNCTION=*UNCHANGEDThe existing scope of file management functions remains unchanged.

FT-FUNCTION=*NOT-RESTRICTEDThe full scope of FTP functions is available.

FT-FUNCTION=(*TRANSFER-FILE, *MODIFY-FILE-ATTRIBUTES,*READ-DIRECTORY)

The following functions are available:

*TRANSFER-FILEThe admission profile may be used for the "transfer files", "view file attributes" and"delete files" functions.The following server commands are not permitted:

list, nlist, pwd, xpwd, cwd, xcwd, cdup, xcup, rnfr, size, mdtm

appe *EXTEND-FILE

stor, rnfr, site file, dele, rmd, xrmd *REPLACE-FILE

stou *NEW-FILE

U41096-J-Z125-2-76 179


*MODIFY-FILE-ATTRIBUTESThe admission profile may be used for the "view file attributes" and "modify fileattributes" functions.The following server commands are not permitted:

retr, stor, appe, stou, dele, list, nlist, pwd, xpwd, cwd, xcwd, cdup, xcup, size, mdtm

*READ-DIRECTORYThe admission profile may be used for the "view directories" and "view file attributes"functions.The following server commands are not permitted:

retr, stor, appe, stou, dele, rnfr.

Example

After Donald Duck has created an admission profile with the name profile1, which grantsother users access to his user ID with the LOGON authorization, he decides to restrictthis profile so that only FTP accesses to files which begin with the prefix BRANCH arepossible.

The required command is:

→ /MODIFY-FT-PROFILEËNAME=profile1, FILE-NAME=*EXPANSION(PREFIX=branch.)

A possible short form of this command is:

→ /MOD-FT-PROFËprofile1,FILE-N=(PRE=branch.)

This places heavy restrictions on the admission profile. The other specifications remainunchanged.

180 U41096-J-Z125-2-76



(SC2) SC1 Maincode Meaning/Guaranteed messages0 0 FTC0051 A user ID with the same name already exists in the system.0 64 FTC0053 No FT profile exists which meets the criteria specified.0 64 FTC0055 The partner restrictions were lifted.0 0 FTC0056 Transfer admission is blocked.0 64 FTC0100 An FT profile with this name already exists.0 64 FTC0101 An FT profile with this transfer admission already exists.0 64 FTC0150 The access password is missing.0 64 FTC0151 Modifications can only be made by the administrator or

owner.0 64 FTC0153 The owner ID entered is not the user´s own ID.0 64 FTC0170 The partner entered is unknown within the partner system

available for this user.0 64 FTC0171 The profile entered does not exist.0 64 FTC0172 The user admission entered does not exist in the system.0 64 FTC0173 The processing admission entered does not exist in the

system.0 64 FTC0174 The parameters "NEW-NAME" and "TRANSFER-

ADMISSION" may only used together in conjunction withunique selection criteria ("NAME" or "TRANSFER-ADMISSION").

0 64 FTC0178 The partner name entered occurs several times.0 64 FTC0179 The maximum number of partner restrictions has been

exceeded.0 64 FTC0182 The maximum length of partner names has been exceeded.0 64 FTC0200 The total length of the two follow-up processing commands is

too long.0 64 FTC0255 A system error has occurred.


U41096-J-Z125-2-76 181

Display admission sets SHOW-FT-ADMISSION-SET

4.2.11 SHOW-FT-ADMISSION-SET - Display admission sets

The command SHOW-FT-ADMISSION-SET is used to view admission sets. You canoptionally have the following information output to SYSOUT or SYSLST:

– whether the admission set is privileged (if it is, then you are the FTAC administrator).

– whether a password is required to use FTAC commands on this user ID. The passworditself is not displayed.

– the limiting values that were set by the owner of this user ID for the accessible securitylevels.

– the limiting values that were preset by the FTAC administrator for the accessible securitylevels .


Operands

USER-IDENTIFICATION=The user ID for which you want to view the admission set. FTAC users can only obtaininformation on their own admission sets and the default admission set.

USER-IDENTIFICATION=*OWNFTAC shows the admission set of your own user ID.

USER-IDENTIFICATION=*ALLFTAC shows the default admission set and the admission set of your own user ID.

USER-IDENTIFICATION=*STDFTAC only shows the default admission set.

USER-IDENTIFICATION=<alphanum-name 1..8>FTAC shows the admission set for this user ID. The operand stands for the USER-ID of thespecified user ID. FTAC users may only enter their own user IDs here.

SHOW-FT-ADMISSION-SET - showing operands relevant for FTP

USER-IDENTIFICATION = *OWN / *ALL / *STD / <alphanum-name 1...8>

, OUTPUT = *SYSOUT (LAYOUT = *STD / *CSV ) /

*SYSLST (LAYOUT = *STD / *CSV)

182 U41096-J-Z125-2-76

SHOW-FT-ADMISSION-SET Display admission sets

OUTPUT=Determines the output medium for the information requested.

OUTPUT=*SYSOUTThe output is sent to SYSOUT.

OUTPUT=*SYSLSTThe output is sent to SYSLST.

LAYOUT=*STDThe output is formatted using a standard layout that can be easily read by the user.

LAYOUT=*CSVThe output is supplied in CSV (Comma Separated Value) format. This is a widely usedtabular format, especially in the PC environment, in which individual fields areseparated by a delimiter, which is usually a semicolon ";" (see page 148).

Example

Dagobert Duck, the FTAC administrator of the Duck Bank, wants to obtain information onthe admission sets in his system. He enters the command

→ /SHOW-FT-ADMISSION-SETËUSER-IDENTIFICATION=*ALL

Short form:

→ /SHOW-FT-ADË*ALL

and receives the following output:

% MAX. USER LEVELS MAX. ADM LEVELS ATTR% USER-ID OBS OBR IBS IBR IBP IBF OBS OBR IBS IBR IBP IBF % *STD 10 10 100 100 0 0 10 10 100 100 0 0 % DAGOBERT 100 100 0 99 0* 0* 100 100 0 99 0* 0* PRIV% DAISY 50 50 99 100 50 50 50 50 100 100 50 50 PW % DANIEL 0 10 99 99 0 0 10 10 100 100 0 0 PW% DONALD 50 100 99 100* 0 0 50 100 100 100 0 0

These can be explained as follows:

The user ID of each admission set is in the column USER-ID. In this example, there is adefault admission set as well as admission sets for the user IDs DAGOBERT, DAISY,DANIEL and DONALD.

The ATTR column shows the privileged admission set. We can see that DAGOBERT is theFTAC administrator.

The ATTR column also indicates whether an FTAC password has been defined (with PW).DAGOBERT, DAISY and DANIEL have done this to prevent others from issuing any FTACcommands on their user ID that could result in changes.

U41096-J-Z125-2-76 183

Display admission sets SHOW-FT-ADMISSION-SET

The six columns under MAX-USER-LEVELS show the limiting values which the FTAC usershave set for their admission sets. The six columns under MAX-ADM-LEVELS show thelimiting values set by the FTAC administrator. The smaller of the two values indicates up towhich security level the owner of the admission set may use each basic function. The basicfunctions are abbreviated in the output as follows:

IBS = INBOUND-SEND

IBR = INBOUND-RECEIVE

IBF = INBOUND-FILEMANAGEMENT

To begin with, it must be observed that FTP users are always assigned security level 100(regardless of which security level was assigned to their systems).

The default admission set has been set up to permit FTP users to send files to the FTPserver and to retrieve files from the FTP server, but not to perform any file managementactions.

DAGOBERT does not permit any file transfer accesses from outside under his user ID(IBS=0, IBR=99, IBP=0).

The files of the user ID DAISY may not be read using FTP (IBS=99), but files may betransferred to this user ID (IBR=100). The user ID DANIEL cannot be accessed with FTP(IBS, IBR and IBF are less than 100).


(SC2) SC1 Maincode Meaning/Guaranteed messages0 64 FTC0052 The information output was interrupted.0 64 FTC0152 The user ID entered is not the user´s own ID.0 64 FTC0181 The entered FT profile name occurs several times.0 64 FTC0255 A system error occurred.


184 U41096-J-Z125-2-76

SHOW-FT-ADMISSION-SET Display admission sets

CSV outputs of SHOW-FT-ADMISSION-SET

Column Type Value

UserId string value

UserMaxObs number value

UserMaxObsStd string *YES / *NO

UserMaxObr number value

UserMaxObrStd string *YES / *NO

UserMaxIbs number value

UserMaxIbsStd string *YES / *NO

UserMaxIbr number value

UserMaxIbrStd string *YES / *NO

UserMaxIbp number value

UserMaxIbpStd string *YES / *NO

UserMaxIbf number value

UserMaxIbfStd string *YES / *NO

AdmMaxObs number value

AdmMaxObsStd string *YES / *NO

AdmMaxObr number value

AdmMaxObrStd string *YES / *NO

AdmMaxIbs number value

AdmMaxIbsStd string *YES / *NO

AdmMaxIbr number value

AdmMaxIbrStd string *YES / *NO

AdmMaxIbp number value

AdmMaxIbpStd string *YES / *NO

AdmMaxIbf number value

AdmMaxIbfStd string *YES / *NO

Priv string *YES / *NO

Password string *YES / *NO

U41096-J-Z125-2-76 185

Display logging records SHOW-FT-LOGGING-RECORDS

4.2.12 SHOW-FT-LOGGING-RECORDS - Display logging records

With FTAC functionality, you can use SHOW-FT-LOGGING-RECORDS to also display theFTAC log records of your own user ID. Even FT administrators can only display those FTAClog records which refer to their own user IDs. The FTAC administrator is the only user whocan display all FTAC log records on the system.


186 U41096-J-Z125-2-76

SHOW-FT-LOGGING-RECORDS Display logging records

SHOW-FT-LOGGING-RECORDS - showing operands relevant for FTP

SELECT = *OWN / *ALL / *PARAMETERS(...)

*PARAMETERS(...)

LOGGING-ID = *ALL / <integer 1..99999999> / *INTERVAL(...)

*INTERVAL(...)

FROM = 1 / <integer 1..99999999>

, TO = *HIGHEST-EXISTING / <integer 1..99999999>

, CREATION-TIME = *INTERVAL (...)

*INTERVAL(...)

FROM = 1970-01-01 (...) / <date 8..10> (...)

(...)

TIME = 00:00 / <time 1..8>

, TO = *TOMORROW (...) / *TODAY (...) / <date 8..10> (...)

(...)

TIME = 00:00 / <time 1..8>

, OWNER-IDENTIFICATION = *OWN / *ALL / <name 1..8>

, LOGGING-DATE = *TOMORROW / *TODAY / <date 8..10>

, LOGGING-TIME = 00:00 / <time 1..8>

, RECORD-TYPE = *ALL / *PARAMETERS(...)

*PARAMETERS(...)

FTAC = (*TRANSFER-FILE, *READ-FILE-ATTRIBUTES, *DELETE-FILE,

*CREATE-FILE, *MODIFY-FILE-ATTRIBUTES

*READ-DIRECTORY, *MOVE-FILE,*CREATE-DIRECTORY,

*DELETE-DIRECTORY,*MODIFY_DIRECTORY) / *NONE /

list-poss(7): *TRANSFER-FILE / *READ-FILE-ATTRIBUTES /

*CREATE-FILE / *MODIFY-FILE-ATTRIBUTES /

*READ-DIRECTORY / *MOVE-FILE

, INITIATOR = (*LOCAL, *REMOTE) / *REMOTE

, PARTNER-NAME = *ALL / <name 1..8>

, FILE-NAME = *ALL / <full-filename 1..54> /.<c-string 1..221 with-low> / <partial-filename 2..53> /

*DIRECTORY(...)/ *POSIX(NAME=posix_pathname_1..219)

, REASON-CODE = *ALL / *FAILURE / <text 1..4>

, NUMBER = 1 / *ALL / <integer 1..1000>

, INFORMATION = *STD / *ALL

, OUTPUT = *SYSOUT (LAYOUT = *STD / *CSV ) /


U41096-J-Z125-2-76 187


Operands

SELECT =Used to select a group of log records.

SELECT = *OWN /*ALLSelects log records under the user’s own user ID. If no other selection criteria are specified,the most recent log record under the user’s own user ID is displayed. The entries *OWN and*ALL generate the same output.

SELECT = *PARAMETERS(...)

LOGGING-ID =Specifies the number of the log record.

LOGGING-ID = *ALLThe number of the log record is not a selection criterion.

LOGGING-ID = <integer 1..99999999>Number of the log record to be output.

LOGGING-ID=*INTERVAL(...)Range of log records to be output.

FROM=<integer 1..99999999>First log record to be output.

TO=*HIGHEST-EXISTING / <integer 1..99999999>Last log record to be output.

CREATION-TIME=*INTERVAL(...)Selects a range of log records to be output by specifying a creation date.

FROM=1970-01-01(...) / < date 8..10>(...)Date in the format yyyy-mm-dd or yy-mm-dd, e.g. 1998-08-18 or 98-08-18 for the 18thof August 1998. FT then displays all log records written after the specified date andtime.

TIME=00:00 / <time 1..8>Time for the day specified with CREATION-TIME. FT displays all log recordswritten after the specified time. The time is entered in the format hh:mm:ss,e.g. 14:30:10.

TO=*TOMORROW / *TODAY(...) / <date 8..10>(...)Date in the format yyyy-mm-dd or yy-mm-dd, e.g. 1998-08-18 or 98-08-18 for the 18thof August, 1998. FT then displays all log records written up to the specified date andtime.

188 U41096-J-Z125-2-76


TIME=00:00 / <time 1..8>Time for the day specified with CREATION-TIME. FT displays all log recordswritten up to the specified time. The time is entered in the format hh:mm:ss,e.g. 14:30:10.

OWNER-IDENTIFICATION=Specifies the user ID of the user whose log records are to be displayed.

OWNER-IDENTIFICATION=*OWNShows the log records of the user’s own ID.

OWNER-IDENTIFICATION=*ALLShows the log records of all user IDs. This operand can be used by the FTACadministrator to display the FTAC log records for all user IDs.Normal FTP users receive information only on the log records of their own user IDseven if they select this entry.

OWNER-IDENTIFICATION=<name 1..8>Any user ID for which the log records are to be output.Normal FT users may only specify their own user IDs.

LOGGING-DATE=Specifies the date up to which log records are to be displayed.

LOGGING-DATE=*TOMORROWDisplays all log records written prior to the time when the command was entered.

LOGGING-DATE=*TODAYIf an exact time was specified with LOGGING-TIME, all log records written prior to thetime specified are displayed. If no time was specified, all log records written up to andincluding 24:00 hours on the previous day are displayed.

LOGGING-DATE=<date 8..10>Specifies a date in the format yyyy-mm-dd or yy-mm-dd, e.g. 1998-08-18 or 98-08-18 forthe 18th of August 1998. FT then displays all log records written prior to the timespecified with LOGGING-DATE and LOGGING-TIME. If no LOGGING-TIME isspecified, the default setting is 00:00 hours.

LOGGING-TIME=Time up to which the log records are to be output.

LOGGING-TIME=00:00If a date was explicitly specified with LOGGING-DATE, all records written prior to thedate specified are displayed. If no date was specified, all log records existing at the timethe command was entered are displayed.

LOGGING-TIME=<time 1..8>Specifies a time for the day specified with LOGGING-DATE. FT displays all log recordswritten prior to this time. The time is specified in the format hh:mm:ss, e.g. 14:30:10.

U41096-J-Z125-2-76 189


OWNER-IDENTIFICATION = *OWN / *ALL / <name 1..8>Shows the log records of the user’s own ID. All three entries have the same effect.

LOGGING-DATE =Specifies the date up to which log records are to be displayed.

LOGGING-DATE = *TOMORROWShows all log records written prior to the time when the command was entered.

LOGGING-DATE=*TODAYIf an exact time was specified with LOGGING-TIME, all log records written prior to thetime specified are displayed. If no time was specified, all log records written up to andincluding 24:00 hours on the previous day are displayed.

LOGGING-DATE=<date 8..10>Specifies a date in the format yyyy-mm-dd or yy-mm-dd, e.g. 1998-08-18 or 98-08-18 forthe 18th of August, 1998. FT then displays all log records written prior to the timespecified with LOGGING-DATE and LOGGING-TIME. If no LOGGING-TIME isspecified, the default setting is 00:00 hours.

LOGGING-TIME=Time up to which the log records are to be displayed.

LOGGING-TIME = 00:00If a date was explicitly specified with LOGGING-DATE, all records written prior to thedate specified are displayed. If no date was specified, all log records existing at the timethe command was entered are displayed.

LOGGING-TIME=<time 1..8>Specifies a time for the day specified with LOGGING-DATE. FT displays all log recordswritten prior to this time. The time is specified in the format hh:mm:ss e.g. 14:30:10.

RECORD-TYPE =Defines which type of log record is to be displayed.

RECORD-TYPE = *ALLThe record type is not a selection criterion.

190 U41096-J-Z125-2-76


RECORD-TYPE = *PARAMETERS(...)The type of the log record.

FTAC=(*TRANSFER-FILE,*READ-FILE-ATTRIBUTES,*DELETE-FILE,*CREATE-FILE,*MODIFY-FILE-ATTRIBUTES,*READ-DIRECTORY,*MOVE-FILE,*CREATE-DIRECTORY,*DELETE-DIRECTORY,*MODIFY-DIRECTORY) / *NONE /list-poss(7): *TRANSFER-FILE / *READ-FILE-ATTRIBUTES / *DELETE-FILE /*CREATE-FILE / *MODIFY-FILE-ATTRIBUTES / *READ-DIRECTORY /*MOVE-FILESpecifies whether or not FTAC log records are to be output. If yes, it can also bespecified for which FTP functions the FTAC log records are to be output. In thiscase, the following definitions apply:

*TRANSFER-FILEAll log records for the function "transfer files" are shown.This corresponds to the server commands retr, stor, stou and appe.

*DELETE-FILEAll log records for the function "delete files" are shown.This corresponds to the server command dele.

*CREATE-FILEAll log records for the function "create files" are shown.This corresponds to the server command site file.

*MODIFY-FILE-ATTRIBUTESAll log records for the function "modify file attributes" are shown.This corresponds to the server command rnfr.

*READ-DIRECTORYAll log records for the function "read directories" are shown.This corresponds to the server commands cwd, xcwd, list, nlst, pwd,xpwd, cdup, xcup, size and mdtm.

*CREATE-DIRECTORYAll log records for the function "create directory" are shown.This corresponds to the server commands mkd and xmkd.

*DELETE-DIRECTORYAll log records for the function "delete directory" are shown.This corresponds to the server commands rmd and xrmd.

U41096-J-Z125-2-76 191


INITIATOR=Selects log records by the initiator.

INITIATOR=(*LOCAL,*REMOTE)The initiator is not a selection criterion.

INITIATOR=*REMOTEThis corresponds to the default value, since FTP requests are always remote requests.

PARTNER-NAME=Client system.

PARTNER-NAME=*ALLThe client system is not a selection criterion.

PARTNER-NAME=<name 1..8>The client system for which log records are to be shown.

FILE-NAME=File name.

FILE-NAME=*ALLThe file name is not a selection criterion.

FILE-NAME=<full-filename 1..54> / <c-string 1..221 with-low>*POSIX(NAME=posix_pathname_1..219)

Fully qualified name of the files (DMS/POSIX) for which you want to view the logrecords.

FILE-NAME=<partial-filename 2..53>Partially qualified name of the files for which you want to view the log records.

REASON-CODE=Selects log records by the REASON code.

REASON-CODE=*ALLThe REASON code is not a selection criterion; all records are shown.

REASON-CODE=*FAILUREAll log records with error codes are shown.

REASON-CODE=<text 1..4>Defines which log records to be shown by specifying the error codes. Leading zerosmay be omitted (e.g. 14 for 0014).

NUMBER=The maximum number of log records to be shown.

NUMBER=1 / <integer 1..1000>The maximum permissible number of log records that can be displayed. By default, only onelog record is shown.

192 U41096-J-Z125-2-76


NUMBER = *ALLAll log records are shown.

INFORMATION=Scope of the required information.

INFORMATION=*STDOnly the standard information is shown for the log records.

INFORMATION=*ALLThe log records are shown in their entirety (long form).

OUTPUT=Determines the output medium.





U41096-J-Z125-2-76 193


Description of the output fields

Short output form of an FT log record (example)

→ /SHOW-FT-LOGGING-RECORDS NUMBER=2%TYP LOGG-ID TIME RC PARTNER INITIATOR INIT USER-ADM FILENAME%1999-03-17%PM 3283 18:26:59 0000 <G133H301 *REMOTE FT2V292 TEST2 %P 3212 11:33:53 0000 >G133H301 *REMOTE FT2V292 TEST1

Long output form (example)

→ /SHOW-FT-LOGGING-RECORDS NUMBER=2,INFORMATION=*ALL%LOGGING-ID = 00003283 RC = 0000 TIME = 1999-03-17 18:26:59% INITIATOR= *REMOTE PARTNER = G133H301 REC-TYPE = FTAC(FTP)% INIT = TRANS = FROM FUNCTION = MODIFY-FILE-ATTR% USER-ADM = FT2V292 PROFILE = Z PRIV = NO% FILENAME = TEST2

%LOGGING-ID = 00003212 RC = 0000 TIME = 1999-03-17 11:33:53% INITIATOR= *REMOTE PARTNER = G133H301 REC-TYPE = FTAC(FTP)% INIT = TRANS = TO FUNCTION = TRANSFER-FILE% USER-ADM = FT2V292 PROFILE = Z PRIV = NO% FILENAME = TEST1

194 U41096-J-Z125-2-76


Explanation

Identifier Explanation

TYP (column 1)orREC-TYPE

Indicates whether an FT or FTAC log record is involved. In the short outputform, the first column T indicates the FT log record; C indicates the FTAClog records, and P indicates the FTP-specific FTAC log record; in the longoutput form (REC-TYPE), these details are written out in full.

TYP (column 2-3)orFUNCTION

Definition of FT function:

ËCDMRCDDD

TRANSFER-FILECREATE-FILEDELETE-FILEMODIFY-FILE-ATTRIBUTESREAD-DIRECTORYCREATE-DIRECTORYDELETE-DIRECTORY

transfer filecreate filedelete filemodify file attributesread directorycreate directorydelete directory

LOGG-ID orLOGGING-ID

Number of the log record (max. 8 positions)

TIME Time when the log record was written

RC Reason Code.Indicates if a request was successfully executed, and if not, why it wasrejected or terminated. If an FTP request is rejected for "FTAC reasons"(e.g. 0014), the precise reason for the termination can be found in theFTAC log record. Further information on the reason code can be obtainedby using the BS2000 command HELP-MSG-INFORMATION.

PARTNER Returns information on the client system involved. The output shows thepossibly abbreviated symbolic name with up to eight characters.In the short form, the client system name is preceded by an identifier fromwhich you can determine the direction of the request.

PARTNER

TRANS

>orTO

The transfer direction is to the client system.This direction is specified for a

– send request

– request to view remote directories

PARTNER

TRANS

<orFROM

The transfer direction is to the local system. This direction is specified for a

– receive request

– request to modify remote file attributes

– request to delete remote files

TRANS BOTH The transfer direction is to the client system and to the local system.

INITIATOR Initiator of the request; for FTP, always *REMOTE

INIT For FTP, this field is always empty.

USER-ADM User ID referenced by the requests on the local system.

FILENAME File name on the local system

U41096-J-Z125-2-76 195



PROFILE Admission profile used

PRIV *NO Non-privileged admission profile

*YES Privileged admission profile

(SC2) SC1 Maincode Meaning/Guaranteed messages0 32 FTR0099 System error.

The SYSOUT message includes the error code as an insert.0 0 FTR0152 Command accepted. No logging records available.0 64 FTR0154 Command rejected. User not authorized for other user IDs.0 64 FTR0155 Command rejected. Logging layout incompatible.0 64 FTR0156 Command accepted. Logging information incomplete.


Identifier Explanation

196 U41096-J-Z125-2-76


OPS variables

The following table shows the OPS variables for the SHOW-FT-LOGGING-RECORDScommand with the operand INF=*ALL. The underlined values apply to the output with theINF=*STD operand.

Example

You want to view all log records created under your user ID before 01.01.98.

/SHOW-FT-LOGGING-RECORDSËSELECT=*PARAMETERS(LOGGING-DATE=1998-01-01), -/ NUMBER=*ALL

All log records entered before 00:00 on 01.01.98 are displayed.

You now want to display the first record of this output in detail.

/SHOW-FT-LOG-RECË(LOG-DATE=1998-01-01),INF=*ALL

Element Type Output

LOG-ID integer

REASON-CODE 1

1 The reason code is always given in decimal form. To determine the meaning of FTAC log recordsusing the manual, the value must be converted to hexadecimal form.

integer

LOG struct

.DATE string yyyy-mm-dd

.TIME string hh:mm:ss

INIT-USER-ID string for FTP, always *REM

INIT-TSN string empty

PARTNER-NAME string

TRANS-DIRECT string *TO-PARTNER / *FROM-PARTNER /*NOT-SPECIFIED

REC-TYPE string *FTAC

FUNC string *REPL-FILE / *DEL-FILE / *CRE-FILE /*MOD-FILE-ATTR / READ-DIR /

USER-ADMIS struct

PRIVIL 2

2 Only for REC-TYPE=*FTAC and specification of a profile

string *NO / *YES

PROF-NAME 2 string

F-NAME string

U41096-J-Z125-2-76 197


CSV outputs of SHOW-FT-LOGGING-RECORDS

Column Type Value INF =

Log-Id number value *STD / *ALL

ReasonCode string value enclosed in double quotes to preventinterpretation as a number.FTAC reason codes (in contrast to OPSvariables) are output as Hex strings asshown in the manual.

LogTime yyyy-mm-ddhh:mm:ss

value

InitUserId string value / *REM

InitTsn string value / *NONE

PartnerName string value

TransDir string *TO / *FROM / *NSPEC

RecType string *FT / *FTAC

Func string *TRANSFILE / *READ-FILE-ATTR / *DEL-FILE / *CRE-FILE / *MOD-FILE-ATTR /*READ-DIR / *MOVE-FILE / *CRE-FILE-DIR / *DEL-FILE-DIR / *MOD-FILE-DIR

UserAdmisId string value

FileName string value

Priv string *NO / *YES for FTAC logging records andspecification of an FTAC profile; otherwise,*NONE

*ALL

ProfileName string value / *NONE

ResultProcess string *NONE / *STARTED / *NOT-STARTED

StartTime yyyy-mm-ddhh:mm:ss

value

string *NONE

TransId number value

string *NONE

Write string *REPL / *EXT / *NEW / *NONE

StoreTime yyyy-mm-ddhh:mm:ss

value

string *NONE

ByteNum number value

string *NONE

198 U41096-J-Z125-2-76

SHOW-FT-PROFILE Display admission profile

4.2.13 SHOW-FT-PROFILE - Display admission profile

With the command SHOW-FT-PROFILE, FTAC users can obtain information on theiradmission profiles. Either the contents of the selected admission profile or only its name canbe displayed. It is not possible to use SHOW-FT-PROFILE to access passwords or transferadmissions defined in the profile! If a transfer admission is forgotten, a new one must bespecified with MODIFY-FT-PROFILE.


Operands

NAME=With NAME, you enter the name of the admission profile that you want to view.NAME accesses a user-wide unique name of an admission profile.

NAME=*ALLYou want to view all admission profiles under your user ID.

NAME=<alphanum-name 1..8>You want to view the admission profile with the specified name.

SELECT-PARAMETER=With SELECT-PARAMETER, you can specify selection criteria for the admission profilesyou want to view.

SELECT-PARAMETER=*OWNWith *OWN, you can view all the admission profiles of which you are the owner. This meansthat you can view all the admission profiles that are assigned to your user ID.

SHOW-FT-PROFILE - showing operands relevant for FTP



*PARAMETERS(...)

TRANSFER-ADMISSION = *ALL / *NOT-SPECIFIED / <alphanum-name 8..32> /

<c-string 8..32 with-low> / <x-string 15..64> / *SECRET

, OWNER-IDENTIFICATION = *OWN / *ALL / <name 1..8>

, INFORMATION = *ONLY-NAMES / *ALL

, OUTPUT =*SYSOUT (LAYOUT = *STD / *CSV ) /


U41096-J-Z125-2-76 199

Display admission profile SHOW-FT-PROFILE

SELECT-PARAMETER=*PARAMETERS(...)This structure contains the selection criteria with which you can access your admissionprofiles.

TRANSFER-ADMISSION=With TRANSFER-ADMISSION, you can enter the transfer admission defined in anadmission profile as a selection criterion.

TRANSFER-ADMISSION=*ALLTRANSFER-ADMISSION is not used as a selection criterion.

TRANSFER-ADMISSION=*NOT-SPECIFIEDOnly admission profiles without a defined transfer admission are displayed.


You want to view your admission profile that can be addressed with this transferadmission.

TRANSFER-ADMISSION=*SECRETThe system prompts you to enter the transfer admission, but does not display your entryon the screen.

OWNER-IDENTIFICATION =*OWN / *ALL / <name 1..8>OWNER-IDENTIFICATION authorizes the FTAC user to access his own admissionprofiles. All three entries have the same effect.

INFORMATION=With INFORMATION, you determine the scope of information desired.

INFORMATION=*ONLY-NAMESFTAC only shows the names of the admission profiles and indicates whether they areprivileged.

INFORMATION= *ALLFTAC shows the contents of the admission profile, excluding any passwords and thetransfer admission.

OUTPUT=Determines the output medium for the information requested.


200 U41096-J-Z125-2-76





Example

The FTAC administrator wants to view the admission profile PROFPROD with thecommand SHOW-FT-PROFILE to determine if this profile could compromise datasecurity. This is achieved with the following command:

/SHOW-FT-PROFILEËNAME=PROFPROD, SELECT-PARAMETER=(OWNER-IDENTIFICATION=DONALD),INFORMATION=*ALL

Short form:

/SHOW-FT-PROFËPROFPROD,(,DONALD),INF=*ALL

The output appears as follows:

%PROFPROD% IGN-MAX-LEV = (IBR)% FILE-NAME = (PREFIX=SALES.)% USER-ADM = (DONALD,M4711DON,OWN)% PROC-ADM = SAME

The first line shows the name of the admission profile. The next two lines showthe settings that were made by Donald in the command CREATE-FT-PROFILEwith the operands IGNORE-MAX-LEVELS=(INBOUND-RECEIVE=*YES) andFILENAME=(PREFIX=SALES). The values for USER-ADMISSION andPROCESSING-ADMISSION were not set by Donald, so the default valuesare being used.


(SC2) SC1 Maincode Meaning/Guaranteed messages0 64 FTC0052 The information output was interrupted.0 64 FTC0053 No FT profile that meets the specified criteria exists.0 0 FTC0054 No information exists for the specified criteria.0 64 FTC0153 The owner identification entered is not the user´s own ID.0 64 FTC0171 The specified profile does not exist.0 64 FTC0255 A system error occurred.


U41096-J-Z125-2-76 201

Display admission profile SHOW-FT-PROFILE

CSV outputs of SHOW-FT-PROFILE


ProfileName string value *ONLY-NAMES /*ALL

Priv string *YES / *NO

TransAdm string *NSPEC / *SECRET

Duplicated string *YES / *NO

LockedByImport string *YES / *NO

LockedByAdm string *YES / *NO

LockedByUser string *YES / *NO

Expired string *YES / *NO

UserAdmId string value

UserAdmAccount string value / *NSPEC / *NRES *ALL

UserAdmPass string *OWN / *NSPEC / *NONE / *YES

ExpDate yyyy-mm-dd value / *NRES

Usage string *PUBLIC / *PRIVATE / *NSPEC

IgnObs string *YES / *NO

IgnObr string *YES / *NO

IgnIbs string *YES / *NO

IgnIbr string *YES / *NO

IgnIbP string *YES / *NO

IgnIbf string *YES / *NO

Initiator string *LOC / *REM / *NRES

TransDir String *FROM / *TO / *NRES

MaxPartLev number value

string *NRES

Partners string one or more FT partner(s), separatedby commas / *NRES

FileName string value / *NRES

Library string *YES / *NO / *NRES / value

FileNamePrefix string *YES / *NO

ElemName string value / *NRES / *NONE

ElemPrefix string *YES / *NO

ElemVersion string value / *STD / *NONE

ElemType string value / *NRES / *NONE

202 U41096-J-Z125-2-76


FilePass string *YES / *NRES / *NONE

Write string *NEW / *EXT / *REPL / *NRES

ProcAdmId string value / *NRES / *SAME

ProcAdmAccount string value / *NRES / *SAME

ProcAdmPASS string *NONE / *YES / *NRES /*SAME

SuccProc string value / *NONE / *NRES / *EXPANSION

SuccPrefix string value / *NONE

SuccSuffix string value / *NONE

FailProc string value / *NONE / *NRES / *EXPANSION

FailPrefix string value / *NONE

FailSuffix string value / *NONE

TransFile string *ALLOWED / *NOT-ALLOWED

ModFileAttr string *ALLOWED / *NOT-ALLOWED

ReadDir string *ALLOWED / *NOT-ALLOWED

Text string value / *NONE


U41096-J-Z125-2-76 203

5 TELNETThis section describes both the TELNET client in BS2000/OSD and the TELNET server (asof page 227).

Basic function

When a user sets up a connection to a partner system with the TELNET program, his or herterminal behaves like a line terminal directly connected to the partner system.

TELNET enables interactive communications only in line mode. Consequently, if the partnersystem is a BS2000 computer, for example, FHS and EDOR cannot be used, and SDF andEDT may only be used in line mode. Similarly, if the partner system is a Reliant UNIXsystem, for example, CED cannot be used.

Other functions

� Information for the userIn a TELNET session, the user can obtain information on

– the available commands and their significance,

– the partner system with which the user is currently connected and the conditions(options) for data transfer.

� Monitoring functionsTrace functions corresponding to the server trace functions that can be initiated by theadministrator via /INTR command of the system console have also been implementedin the client for maintenance and diagnostic purposes.

� Interface to the local and remote operating systemAn interface to the local operating system is provided to allow the user to issue aBS2000 command without having to interrupt the program run (and first clearthe connection to the partner system).

204 U41096-J-Z125-2-76

Introduction TELNET client

5.1 TELNET client

Every TELNET user in BS2000 opens a separate client task. On issuing the open command,the client establishes a connection with the desired TELNET server on the remote host.

TELNET clients in BS2000

UNIX system

TELNETserver

BS2000 system

TELNETclient

TELNETclient

TELNETclient

TELNETserver

UNIX system

Dialogprocess

Dialogprocess

Dialogprocess

Network

U41096-J-Z125-2-76 205

TELNET client Introduction

5.1.1 Command mode and input mode

TELNET can be used in interactive mode with hosts attached to the local network. In orderto determine whether inputs are directed to the TELNET client or to the remote host withwhich a dialog is being maintained, TELNET recognizes two operating modes:

– command mode, in which commands are passed to the TELNET client.

– input mode, in which data and commands are passed to the remote interactive host.

Only line-oriented dialogs are possible with TELNET. Consequently, if the remote computeris a UNIX system, for example, the editor CED cannot be used. Similarly, if the partner is aBS2000 system, FHS cannot be used at all, and SDF and EDT can be used only in linemode.

The TELNET command ! can be used to switch from TELNET command mode to BS2000command mode.

The figure on page 206 shows the three modes for entering data and commands and thetransitions between them. (The precise behavior on switching to BS2000 command modewith the ! command and to TELNET command mode with escape characters is given in thedetailed description of the commands.)

206 U41096-J-Z125-2-76

Introduction TELNET client

Input modes

BS2000command mode

TELNETcommand mode

TELNETinput mode

START-TELNET

RESUME

! quit

open

^]Terminateprocess

EXEC $TSOS.TELNETTELNET

U41096-J-Z125-2-76 207

TELNET client Introduction

Starting TELNET

The TELNET client can be started with any of the following calls:

– START-TELNET or TELNET

– EXEC $TSOS.TELNET

– START-PROGRAM *MOD(SYSLNK.TCP-IP-AP.040,TELNET,RUN-MODE=A,PROG-MODE=ANY)

or for SR2000

– START-PROGRAM *MOD(SRMLNK.TCP-IP-AP.040,TELNET,RUN-MODE=A,PROG-MODE=ANY)

The client is terminated with the quit command.

In interactive mode, TELNET responds with a version number and the prompt telnet>. Taskswitch 1 must not be set. On starting TELNET, you will find yourself in TELNET commandmode. In this mode, you can control TELNET and also retrieve data.

The command open <ipadr> connects you to a remote host. You will now be in the TELNETinput mode and can direct any line-oriented commands to the operating system on theremote host. The connection to the remote system is cleared if the appropriate commandto terminate the current process is issued on the remote operating system.

If you want to issue a TELNET command, you can interrupt the input mode by entering theescape character. In TELNET command mode, the connection to the remote system canbe cleared by issuing the close command.

The predefined setting for the escape character is ^], but can be changed by using theescape command. The function of the {CONTROL} key on asynchronous terminals (SINIX)corresponds to the symbol ^. If the ^ character is to be transmitted, it must be entered twice.

208 U41096-J-Z125-2-76

Commands TELNET client

5.1.2 Overview of commands

TELNET commands may be abbreviated up to the point required for unique identification.Operands are separated by spaces.


open Open connection to remote host 215

close Close connection to remote host 209

! Switch to BS2000 command mode 226

crmod Enable/disable insertion of carriage returns 210

escape Change escape character 212

setcode Change code tables 221

^] Switch to TELNET command mode 224

quit Exit the TELNET client 218

send Send special commands: ao / ip / ayt / nop 220

Controlling TELNET


? Show information on TELNET commands 225

help Same as ?; returns information on TELNET commands 214

status Show TELNET status information 222

options Enable/disable display of options 217

trace Set socket trace level 223

debug Enable the TELNET trace 211

Information on TELNET

U41096-J-Z125-2-76 209

TELNET client close

close - close connection to remote host

The close command clears the connection to the remote host.

The connection to a remote host is set up by using the open command. The status commandshows the name of the host for which a connection exists.

On executing the close command, you will be placed in the TELNET command mode.

Example

1. The status query shows that a connection to systemd exists.

→ statusConnected to systemd.Escape character is '^]'.ISO-codetable is ISO88591, EBCDIC-codetable is EDF041.

2. Switch to TELNET command mode.

→ ^]

3. Close the connection to systemd.

→ closeConnection closed

close

210 U41096-J-Z125-2-76

crmod TELNET client

crmod - enable/disable insertion of carriage returns

If the remote host sends messages that contain no carriage returns, the crmod command(enable insert carriage return) can be used to instruct the TELNET client to execute a linefeed. The insertion of carriage returns is disabled by default.

Since UNIX transmits carriage returns, enabling the insertion of carriage returns will resultin to a duplication of the line feeds.

Example

The remote host is a UNIX system. Duplicate line feeds are enabled.

→ crmodWill map carriage return on output

Remarks

Duplicate line feeds are enabled.

crmod

U41096-J-Z125-2-76 211

TELNET client debug

debug - enable/disable DEBUG output

DEBUG output is primarily used by network administrators and support staff to diagnoseproblems on the network. Users do not usually require DEBUG output.

<debug-value>Values in the range 0 through 9 are permitted.

0 No DEBUG output

1 All messages from the FTP client to the FTP server and from the FTP serverto the FTP client are output.

If no operand is specified, the DEBUG output switch is toggled, i.e. if the DEBUG outputwas enabled, it is now disabled, and if it was disabled, it is now enabled. Valuesgreater than 1 are treated in the same way as 1.

debug

<debug-value>

212 U41096-J-Z125-2-76

escape TELNET client

escape - change ESCAPE character

Entering the escape character switches you from TELNET input mode to TELNETcommand mode.

The escape character consists of two elements. The first element is ^, and the secondelement can be freely selected by the user with the escape command.

Switching from input mode to TELNET command mode is described under the ^] commandon page 224.

The escape character is queried in an interactive dialog.

Example

-> escapenew escape character: @Escape character is '‘^@‘.

escape

U41096-J-Z125-2-76 213

TELNET client exit

exit - enable/disable client exit

You can set exit routines for the TELNET client using the exit command.

You will find a more precise description of the exit mechanism in TELNET and of the exitcommand in the interNet Services V2.0 Administrator’s Guide.

exit

[ receive : < selector 1 > ] [ send : < selector 2 > ]

214 U41096-J-Z125-2-76

help TELNET client

help - show information on TELNET commands

This command returns information on a specific TELNET command or on all TELNETcommands.

<command>TELNET command for which information is desired. If the operand is omitted, all thepermitted TELNET commands are listed.

Example

-> helpCommands may be abbreviated. Commands are:open connect to a siteclose close current connectionquit exit telnet! BS2000 MCLPescape set escape characterstatus print status informationoptions toggle viewing of options processingcrmod toggle mapping of received carriage returnstrace set socket trace levelhelp print help informationsetcode change the codetablessend send special commands ao/ip/ayt/nopexit set local exitrexit set remote exitdebug set telnet trace? print help information

help

[<command>]

U41096-J-Z125-2-76 215

TELNET client open

open - open connection to a remote host

The open command sets up a connection to a remote host. Either the name or the internetaddress of this host must be known. The host must either be part of the local network or beaccessible via a gateway. The names and addresses of the hosts that can be reached viathe open command can be obtained from the network administrator.

You can now log on to a remote BS2000/OSD host with LOGON. If you enter the LOGONcommand without a password, BS2000/OSD subsequently prompts the password withJMS0151. The input box for entering the password is non-displaying in TELNET.

After the connection has been correctly set up, line-oriented commands of the remoteoperating system can be entered (the user is in input mode). The connection is cleared byissuing the appropriate command to terminate the current process in the remote operatingsystem.

<ipadr>Internet address of the remote host to which the connection is to be made.

<remote-host>Symbolic name of the remote host to which the connection is to be made.

<local-host>Symbolic name reserved for the user’s own host (usually meaningful only for testpurposes).local-host represents the internet address through which the local host can actually beaccessed on the LAN.

<loopback>For loopback a separate internet address is generated that is not identical to the addressof the user’s own host on the local network. This address is known only to the local host;other processors cannot use it.

<port>Port number of the TELNET server. The TELNET server s assigned port number 23 bydefault.

open

<ipadr> | <remote-host> [<local-host> | <loopback>] [<port>]

216 U41096-J-Z125-2-76

open TELNET client

Example

The remote system is a UNIX host.

1. Open a connection to the UNIX host systemd.

-> open systemdTrying... Connected to systemd. Escape character is '^]'. ISO-codetable is ISO88591, EBCDIC-codetable is EDF041.local exits defined: receive: -, send: -remote exits defined: receive: -, send: -Host name: systemd

2. Login under the user ID guest.

→ guest guestContinue by entering RETURN or MENUE

U41096-J-Z125-2-76 217

TELNET client options

options - enable/disable display of options

A number of different options are negotiated between the TELNET client and the TELNETserver (when setting up the connection, for example). If this switch is "enabled", theseTELNET options are displayed on the screen. Options transmitted by the local client areidentified as SENT, while those received by the local client are identified as RCVD.

Options are not displayed by default.

Example

1. option command with response.

-> optionsWill show option processing.

2. open command with the options displayed. The ECHO option is negotiated herebetween the sender and receiver.

-> open systemdTrying... Connected to systemd. Escape character is '^]'. ISO-codetable is ISO88591, EBCDIC-codetable is EDF041.RCVD will ECHO (reply) SENT dont ECHO (reply) RCVD wont ECHO (don't reply)Host name: systemd

options

218 U41096-J-Z125-2-76

quit TELNET client

quit - exit TELNET

The quit command terminates the TELNET program. If a connection to a remote host is stillopen, it is cleared (implicit close).

Example

-> quitConnection closed.CPU time used 4.7232 seconds

quit

U41096-J-Z125-2-76 219

TELNET client rexit

rexit - enable/disable server exits

The client allows you to set TELNET server exits using the rexit (remote exit) command.However, this only relates to exits for send and receive and only affects the connection of thisspecial client to the server.

You will find a more precise description of the exit mechanism in TELNET and of the exitcommand in the interNet Services V2.0 Administrator’s Guide.

rexit

[ receive : < selector 1> ] [ send : < selector 2> ]

220 U41096-J-Z125-2-76

send TELNET client

send - send special commands

ao(abort output) Purges the entire output of the remote host and dumps it to the terminalof the user process currently running on the remote host.

ip(interrupt process) Interrupts the process currently running on the remote host.

ayt(are you there) Checks whether the server is still "alive". If this is the case, the serverresponds with YES.

nopSends No operation to the server.

?Returns help on the send command.

send

ao | ip | ayt | nop | ?

U41096-J-Z125-2-76 221

TELNET client setcode

setcode - change code tables

The setcode command is used to change the current code tables with which the TELNETclient converts from EBCDIC to ISO characters (extended ASCII character set).The services of XHCS are utilized for this purpose, so only the code tables that have beenentered as compatible in XHCS may be specified here (see the "XHCS" manual). If aconnection is set up between two BS2000 systems, it is important to ensure that bothpartners use the same code tables.

<ebcdic-table> <iso-table>A code conversion table is generated with XHCS for conversion between EBCDIC andISO codes. This conversion table is used by the TELNET client for all code conversions.

It is essential to ensure that the code tables are specified in the correct sequence;otherwise, invalid conversion tables will be created, and the file transfer will not bepossible.

Example

setcode EDF045 ISO88595

Remarks

Since the BS2000 TELNET server supports only simple 7-bit terminals, this command ismeaningless for connections to the BS2000 TELNET server.

setcode

<ebcdic-table> <iso-table>

!

222 U41096-J-Z125-2-76

status TELNET client

status - display TELNET status information

The status message indicates,

– whether a connection exists and to which host,– the elements of the current escape character.

The escape character is defined with the escape command.

Example

The currently set parameters of the TELNET client are shown.

-> statusNo connection.Escape character is'‘^]‘.ISO-codetable is ISO88591 , EBCDIC-codetable is EDF041local exits defined: receive: -, send: -remote exits defined: receive: -, send: -

-> statusConnected to loopback.Escape character is'‘^]‘.ISO-codetable is ISO88591 , EBCDIC-codetable is EDF041local exits defined: receive: -, send: -remote exits defined: receive: -, send: -

status

U41096-J-Z125-2-76 223

TELNET client trace

trace - enable/disable SOCKET trace output

SOCKET trace output is primarily used by the network administrator and the Siemenssupport staff to diagnose problems on the local network. Normal users do not usually needany SOCKET trace output.

If SOCKET trace output is enabled, TELNET displays various types of diagnosticinformation on the screen.

<trace-value>The permitted values are in the range 0 through 9. Higher parameter values displaymore information.

0 No TRACE output (disable TRACE output).

1 - 9 Displays information on SOCKET traces.

If no operand is specified, the TRACE output setting is toggled, i.e. if TRACE output wasenabled, it is disabled, and if it was disabled, it is enabled (trace-value=1). Parameter valuesgreater than 1 imply the output of all TRACE information at the lower levels.

trace

[<trace-value>]

224 U41096-J-Z125-2-76

^] TELNET client

^] - switch to TELNET command mode

Entering the escape character switches you from TELNET input mode to the TELNETcommand mode.

^] is the default setting for the escape character. After executing of a valid TELNETcommand, you are normally returned to the input mode. If the command is not valid,TELNET remains in command mode.

The escape command allows you to select some other character instead of ] as the escapecharacter. On executing the ? command, the TELNET command mode remains in effect.You can use the ! command to switch to BS2000 command mode. Note that the TELNETcommand mode also remains in effect on executing the close command.

^]

U41096-J-Z125-2-76 225

TELNET client ?

? - show information on TELNET commands

The ? command returns information on a particular TELNET command or all TELNETcommands.

See the description of help on page 214.

?

[<command>]

226 U41096-J-Z125-2-76

! TELNET client

! - switch to BS2000 command mode

The ! command enables you to enter BS2000 commands. If no operand is specified, thesystem switches to BS2000 command mode. You can then enter any BS2000 commandsand subsequently return to TELNET by issuing the BS2000 command RESUME. Alterna-tively, if you specify ! with a BS2000 command as the operand, you will be automaticallyreturned to TELNET after the execution of the command.

<bs2000-command>Any line-oriented BS2000 command.If a connection to a remote host exists, this command cannot be issued.The BS2000 commands LOAD, EXEC, LOGOFF and ABEND may not be entered eitherdirectly or indirectly, since they terminate TELNET or the task in which TELNET isrunning.

Example

1. Switch to BS2000 command mode.

-> !

% PROGRAM BREAK AT 0013E8, AMODE = 24

2. Enter the BS2000 command STATUS PROG.

→ STA PNAME TSN TYPE SIZE CURR-CMD PROGRAM-NAMEPETER 2726 3 DIALOG 79 STA :5:$TSOS.TELNETBRONCO 2716 3 DIALOG 87 EXECUTE :5:$TSOS.FTP

3. Return to the TELNET client.

→ R

!

[<bs2000-command>]

U41096-J-Z125-2-76 227

TELNET server Functionality

5.2 TELNET server

The TELNET server in BS2000 accepts connection requests from TELNET clients on thelocal network and forwards them to $DIALOG.

TELNET server in BS2000

Mode of operation

The server accepts connection requests and sets up a DCAM connection to $DIALOG. Asimple printer terminal is emulated with respect to $DIALOG, i.e. only a line-oriented dialogis possible. No overflow control is implemented.

BS2000 server

Dialogprocess

UNIX system MS-DOS system

Dialogprocess

Dialogprocess

TELNETserver

Network

TELNETclient

TELNETclient

TELNETclient

BS2000 system

TELNETclient

Eine Dokuschablone von Frank Flacheneckerby f.f. 1992

U41096-J-Z125-2-76 229

6 Messages

6.1 FTAC system messages

The FTAC system messages have the following structure:

FTCnnnn FTAC-BS2: message-text

FTCnnnn is the message code. The message code is 7 characters long.

message-text is the text of the message. The text appears in uppercase letters.The message text may contain what are known as inserts, e.g.(&00). These parts of the text are replaced by the current value(e.g. transfer ID) when the message is output.

In BS2000, the FTAC message file is bilingual and also includes so-called messageattributes and explanatory texts. These texts can be requested with the BS2000 commandHELP-MSG-INFORMATION (see also the manual "User Commands (SDF Format)").

In addition, command return codes which can be queried with SDF-P procedures aresupplied. A description of the command return codes can be found on page 146.The return codes for individual commands are listed at the end of each commanddescription.

Explanatory texts (bilingual)

Additional explanatory information for the message is provided under the meaning; theaction indicates what action is to be taken.

These texts are not output with the message.

However, they can be requested with the HELP-MSG-INFORMATION command asfollows:

HELP-MSG-INFORMATIONËMSG-IDENTIFICATION=*LAST

The last message is output together with the meaning/action text.

HELP-MSG-INFORMATIONËMSG-IDENTIFICATION=FTRnnnn

230 U41096-J-Z125-2-76

openFT-AC messages

The message with code FTRnnnn is output together with the meaning/action text.

EHELP-MSG-INFORMATIONË [MSG-IDENTIFICATION=FTRnnnn],LANGUAGE= D

The LANGUAGE operand (E = English and D = German) specifies the language inwhich both the message and the meaning/action text are to be displayed.

U41096-J-Z125-2-76 231

openFT-AC messages FTCCOPY

6.1.1 FTCnnnn messages

FTCCOPY COPYRIGHT (C) (&00) (&01) ALL RIGHTS RESERVED

FTCLOAD PROGRAM ’FTAC’, VERSION ’06.0A00’ OF ’1996-09-02’ LOADED

FTCSTRT PROGRAM ’FTAC’, VERSION ’06.0A00’ OF ’1996-09-02’ STARTED

FTC0001 FTAC-BS2000 VERSION (&00) ACTIVE (B) Routing code: C Weight: 99

MeaningInitiation of FTAC-BS2000 is completed.

FTC0003 (&00) LOGGING RECORDS DELETED (B) Routing code: C Weight: 99

MeaningThe given number of records in the logging file was deleted.

FTC0050 CMD ACCEPTED. WARNING: LOWER ADM-LEVEL REMAINS IN EFFECT (B) Routing code: C Weight: 99

MeaningGiven user-level exceeds the adm-level and remains ineffective until theadm-level is increased.

ResponseAsk FTAC-administrator for a higher adm-level.

FTC0051 CMD ACCEPTED. WARNING: TRANSFER-ADMISSION EXISTS AS USERID (B) Routing code: C Weight: 99

MeaningA userid with the same name exists already in the system.

ResponseMessage is only a hint to a possible confusion.

FTC0052 CMD TERMINATED. INFORMATION INCOMPLETE (B) Routing code: C Weight: 99

MeaningOutput of the information has been interrupted.

ResponseRepeat command if necessary.

FTC0053 CMD TERMINATED. NO FT-PROFILE FOUND (B) Routing code: C Weight: 99

MeaningThere exists no FT-profile according to the selection.

232 U41096-J-Z125-2-76

FTC0054 openFT-AC messages

FTC0054 CMD ACCEPTED. NO INFORMATION AVAILABLE (B) Routing code: C Weight: 99

MeaningThere exists no information according to the selection.

FTC0055 WARNING: PARTNER RESTRICTION DOES NOT LONGER EXIST (B) Routing code: * Weight: 99

FTC0056 WARNING: TRANSFER ADMISSION LOCKED (B) Routing code: * Weight: 99

FTC0070 CMD TERMINATED. SHORTAGE OF RESOURCES (B) Routing code: C Weight: 99

MeaningThe command cannot be executed because of shortage of the systemresources.

ResponseRepeat command.

FTC0071 CMD REJECTED. FTAC-BS2000 NOT ACTIVE (B) Routing code: C Weight: 99

MeaningFTAC-BS2000 is not active because FT-BS2000 has not been started

ResponseAsk system administrator for activating FT-BS2000. FTAC-BS2000 will beactivated by FT-BS2000.

FTC0100 CMD REJECTED. FT-PROFILE ALREADY EXISTS (B) Routing code: C Weight: 99

MeaningThere already exists a FT-profile with the given name.

ResponseChoose another name.

FTC0101 CMD REJECTED. TRANSFER-ADMISSION ALREADY EXISTS (B) Routing code: C Weight: 99

MeaningThere already exists a FT-profile with the given transfer-admission.

ResponseChoose the TRANSFER-ADMISSION more carefully to ensure more security.

FTC0102 FILE ALREADY EXISTS (B) Routing code: * Weight: 99

U41096-J-Z125-2-76 233

openFT-AC messages FTC0103

FTC0103 INVALID FILE CONTENT OR ACCESS TO FILE DENIED. (B) Routing code: * Weight: 99

MeaningThe file is not a FTAC export file or access to the file is not allowed.

FTC0104 ACCESS TO USERID DENIED OR USERID DOES NOT EXIST. (B) Routing code: * Weight: 99

MeaningAccess to UserId deniedAccess to cat id deniedUserId does not existcat id does not exist

FTC0105 ACCESS TO FILE DENIED (B) Routing code: * Weight: 99

FTC0106 ACCESS TO TEMPORARY FILE DENIED

FTC0150 CMD REJECTED. USER NOT AUTHORIZED FOR FTAC COMMANDS (B) Routing code: C Weight: 99

MeaningPassword for authorization is missing.

ResponseSpecify FTAC-password.

FTC0151 CMD REJECTED. USER NOT AUTHORIZED FOR THIS MODIFICATION (B) Routing code: C Weight: 99

MeaningOnly administrator or owner are authorized for this modification.

FTC0152 CMD REJECTED. USER NOT AUTHORIZED FOR OTHER USERID’S (B) Routing code: C Weight: 99

MeaningGiven userid is not own userid.

FTC0153 CMD REJECTED. USER NOT AUTHORIZED FOR OTHER OWNERID’S (B) Routing code: C Weight: 99

MeaningGiven ownerid is not own userid.

FTC0155 CMD REJECTED. USER NOT AUTHORIZED FOR DIAGNOSE (B) Routing code: C Weight: 99

MeaningOnly FT administrator and FTAC administrator are authorized for diagnose.

234 U41096-J-Z125-2-76


FTC0156 COMMAND ALLOWED FOR FTAC ADMINISTRATOR ONLY (B) Routing code: * Weight: 99

FTC0157 CMD REJECTED. AUTHORIZATION TO CREATE A PROFILE IS MISSED. (B) Routing code: * Weight: 99

MeaningThe FTAC administrator can create a profile with transfer admission for

other users, if he knows the complete user identification.

ResponseType complete user identification asuser-adm=(uid,acc,pw).

FTC0170 CMD REJECTED. GIVEN PARTNER NAME UNKNOWN (B) Routing code: C Weight: 99

MeaningThe given partner is unknown within the range of possible partners forthis user.

FTC0171 CMD REJECTED. GIVEN FT-PROFILENAME UNKNOWN (B) Routing code: C Weight: 99

MeaningFT-profile does not exist.

FTC0172 CMD REJECTED. INVALID USER-ADMISSION (B) Routing code: C Weight: 99

MeaningThe given user-admission does not exist in the system.

ResponseWrong specification of USER-IDENTIFICATION,ACCOUNT or PASSWORD.

FTC0173 CMD REJECTED. INVALID PROCESSING-ADMISSION (B) Routing code: C Weight: 99

MeaningThe given processing-admission does not exist in the system.

ResponseWrong specification of USER-IDENTIFICATION,ACCOUNT or PASSWORD.

U41096-J-Z125-2-76 235


FTC0174 CMD REJECTED. MODIFICATION INVALID FOR NOT UNIQUE SELECTION CRITERIA (B) Routing code: C Weight: 99

MeaningThe parameter "NEW-NAME" and "TRANSFER-ADMISSION" are only allowed withunique selection criteria ("NAME" or "TRANSFER-ADMISSION")

ResponseUse unique selection criterion.

FTC0175 CMD REJECTED. MODIFICATION INVALID FOR *STD (B) Routing code: C Weight: 99

MeaningThe parameter "NEW-PASSWORD" is not allowed for *STD.

FTC0176 CMD REJECTED. GIVEN USERID UNKNOWN (B) Routing code: C Weight: 99

MeaningThe given userid does not exist in the system.

FTC0177 FILE UNKNOWN (B) Routing code: * Weight: 99

FTC0178 MULTIPLE PARTNER NAME SPECIFIED (B) Routing code: * Weight: 99

FTC0179 VIOLATION OF MAXIMAL NUMBER OF PARTNER RESTRICTIONS (B) Routing code: * Weight: 99

FTC0180 MULTIPLE USERID SPECIFIED (B) Routing code: * Weight: 99

FTC0181 MULTIPLE FT PROFILE NAME SPECIFIED (B) Routing code: * Weight: 99

FTC0182 TOTAL MAXIMUM PARTNER NAME LENGTH EXCEEDED (B) Routing code: * Weight: 99

MeaningTotal maximum partner name length must not exceed 500 Char.

FTC0200 CMD REJECTED. RESULT-PROCESSING TOO LONG (B) Routing code: C Weight: 99

MeaningThe sum of length of result-processing commands is too long.

ResponseUse shorter commands (e.g. by using procedures).

236 U41096-J-Z125-2-76


FTC0206 THE EXPORT FILE COULD NOT BE CREATED (B) Routing code: * Weight: 99

FTC0250 LOAD ERROR. ERROR-CODE (&00) (B) Routing code: C Weight: 99

MeaningFTAC code could not be loaded. For detailed informations refer to messagesfrom BLS and error code.- xx is the subcode 2 and yyy in file name is for the version.- X’xx400008’ file SYSLNK.FTAC-BS2000.yyy missing.

Response- Make sure, library SYSLNK.FTAC-BS2000.yyy is installed properly and

DSSMCAT is generated properly by using SYSSSD.FTAC-BS2000.yyy orSYSSSC.FTAC-BS2000.yyy and preceding /STOP-SS is finished.

FTC0251 SYSTEM ERROR. FTAC-BS2000 SUBSYSTEM NOT FOUND (B) Routing code: C Weight: 99

MeaningFTAC-BS2000 installation incomplete.

ResponseSystem administrator has to check FTAC-BS2000 installation.

FTC0253 SYSTEM ERROR. FTAC-BS2000 CMD NOT FOUND IN SYNTAXFILE (B) Routing code: C Weight: 99

MeaningFTAC-BS2000 syntax file merged erroneously or incompletely insystem syntax file.

ResponseSystem administrator has to check the system syntax file.

FTC0254 SYSTEM ERROR. ERRORCODE (&00) (B) Routing code: C Weight: 99

MeaningA system error has occurred.

ResponseThe cause of error could be eventually detected by right part of rc via/HELP ????, otherwise create diagnostic information and inform systemservice

U41096-J-Z125-2-76 237


FTC0255 CMD TERMINATED. SYSTEM ERROR (B) Routing code: C Weight: 99

MeaningA system error has occurred.

ResponseInform the system administrator.At the same time a message with adiagnostic information is printed at the system console.

FTC100A SUBMISSION REJECTED. VIOLATION OF ELEMENT-TYPE RESTRICTION (B) Routing code: C Weight: 99

MeaningSpecification of ELEMENT-TYPE not allowed by FT-profile.

FTC100B SUBMISSION REJECTED. VIOLATION OF FILE-PASSWORD RESTRICTION (B) Routing code: C Weight: 99

MeaningSpecification of FILE-PASSWORD not allowed by FT-profile.

FTC100C SUBMISSION REJECTED. VIOLATION OF USER-IDENTIFICATION(PROCESSING-ADMISSION) RESTRICTION (B) Routing code: C Weight: 99

MeaningSpecification of USER-IDENTIFICATION in the PROCESSING-ADMISSION notallowed by FT-profile.

FTC100D SUBMISSION REJECTED. VIOLATION OF ACCOUNT(PROCESSING-ADMISSION) RESTRICTION (B) Routing code: C Weight: 99

MeaningSpecification of ACCOUNT in the PROCESSING-ADMISSION not allowed byFT-profile.

FTC100E SUBMISSION REJECTED. VIOLATION OF PASSWORD(PROCESSING-ADMISSION) RESTRICTION (B) Routing code: C Weight: 99

MeaningSpecification of PASSWORD in the PROCESSING-ADMISSION not allowed byFT-profile.

FTC100F SUBMISSION REJECTED. VIOLATION OF SUCCESS-PROCESSING RESTRICTION (B) Routing code: C Weight: 99

MeaningSpecification of SUCCESS-PROCESSING not allowed by FT-profile.

238 U41096-J-Z125-2-76


FTC1001 SUBMISSION REJECTED. INVALID TRANSFER-ADMISSION (B) Routing code: C Weight: 99

MeaningGiven TRANSFER-ADMISSION defined in no FT-profile.

FTC1002 SUBMISSION REJECTED. INVALID INITIATOR (B) Routing code: C Weight: 99

MeaningThe FT-profile is restricted to LOCAL or REMOTE.

FTC1003 SUBMISSION REJECTED. INVALID TRANSFER-DIRECTION (B) Routing code: C Weight: 99

MeaningThe FT-profile is restricted to TO or FROM.

FTC1004 SUBMISSION REJECTED. INVALID PARTNER NAME (B) Routing code: C Weight: 99

MeaningTransfers to given partner system not allowed by FT-profile.

FTC1005 SUBMISSION REJECTED. VIOLATION OF MAX-PARTNER-LEVEL (B) Routing code: C Weight: 99

MeaningThe security-level of partner system exceeds the value ofMAX-PARTNER-LEVEL in the FT-profile.

FTC1006 SUBMISSION REJECTED. SYNTAX ERROR OF FILE NAME EXPANSION (B) Routing code: C Weight: 99

MeaningSpecification of file name or file name expansion is not allowed by FTprofile.

FTC1007 SUBMISSION REJECTED. VIOLATION OF LIBRARY RESTRICTION (B) Routing code: C Weight: 99

MeaningThe specified file or library name is not allowed by FT-profile.

FTC1008 SUBMISSION REJECTED. VIOLATION OF ELEMENT RESTRICTION (B) Routing code: C Weight: 99

MeaningSpecification of ELEMENT not allowed by FT-profile.

U41096-J-Z125-2-76 239


FTC1009 SUBMISSION REJECTED. VIOLATION OF ELEMENT-VERSION RESTRICTION (B) Routing code: C Weight: 99

MeaningSpecification of ELEMENT-VERSION not allowed by FT-profile.

FTC1010 SUBMISSION REJECTED. VIOLATION OF FAILURE-PROCESSING RESTRICTION (B) Routing code: C Weight: 99

MeaningSpecification of FAILURE-PROCESSING not allowed by FT-profile.

FTC1011 SUBMISSION REJECTED. VIOLATION OF WRITE-MODE RESTRICTION (B) Routing code: C Weight: 99

MeaningGiven WRITE-MODE not allowed by FT-profile.

FTC1012 SUBMISSION REJECTED. INVALID FT-FUNCTION (B) Routing code: * Weight: 99

MeaningGiven FT function not allowed by FT profile.

FTC2001 SUBMISSION REJECTED. SYNTAX ERROR ON FILE NAME EXPANSION (B) Routing code: C Weight: 99

MeaningSyntax error on concatenation of file name and file name expansion.

FTC2002 SUBMISSION REJECTED. SYNTAX ERROR ON LIBRARY NAME EXPANSION (B) Routing code: C Weight: 99

MeaningSyntax error on concatenation of LIBRARY name and LIBRARY expansion.

FTC2003 SUBMISSION REJECTED. SYNTAX ERROR ON ELEMENT NAME EXPANSION (B) Routing code: C Weight: 99

MeaningSyntax error on concatenation of ELEMENT name and ELEMENT expansion.

FTC2004 SUBMISSION REJECTED. TOTAL LENGTH OF RESULT PROCESSING EXCEEDS 250 CHARACTERS (B) Routing code: C Weight: 99

MeaningSUCCESS and FAILURE processing including the expansions defined inFT-profile are longer than 250 characters.

240 U41096-J-Z125-2-76


FTC3001 SUBMISSION REJECTED. INVALID USER-IDENTIFICATION (B) Routing code: C Weight: 99

MeaningThe USER-IDENTIFICATION of the TRANSFER-ADMISSION or, if FT-profile isused, of the USER-ADMISSION is invalid.

FTC3002 SUBMISSION REJECTED. INVALID ACCOUNT (B) Routing code: C Weight: 99

MeaningThe ACCOUNT specification of the TRANSFER-ADMISSION or, if FT-profile isused, of the USER-ADMISSION is invalid.

FTC3003 SUBMISSION REJECTED. INVALID PASSWORD (B) Routing code: C Weight: 99

MeaningThe PASSWORD specification of the TRANSFER-ADMISSION or, if FT-profile isused, of the USER-ADMISSION is invalid.

FTC3004 SUBMISSION REJECTED. TRANSFER ADMISSION LOCKED (B) Routing code: * Weight: 99

MeaningThe transfer admission is locked. The reasons can be obtained by the meanof the /SHOW-FT-PROFILE command.

FTC3011 SUBMISSION REJECTED. VIOLATION OF USER OUTBOUND SEND LEVEL (B) Routing code: C Weight: 99

MeaningThe security level of the partner system is not permitted by the user forfunction class OUTBOUND SEND.

FTC3012 SUBMISSION REJECTED. VIOLATION OF USER OUTBOUND RECEIVE LEVEL (B) Routing code: C Weight: 99

MeaningThe security level of the partner system is not permitted by the user forfunction class OUTBOUND RECEIVE.

FTC3013 SUBMISSION REJECTED. VIOLATION OF USER INBOUND SEND LEVEL (B) Routing code: C Weight: 99

MeaningThe security level of the partner system is not permitted by the user forfunction class INBOUND SEND.

U41096-J-Z125-2-76 241


FTC3014 SUBMISSION REJECTED. VIOLATION OF USER INBOUND RECEIVE LEVEL (B) Routing code: C Weight: 99

MeaningThe security level of the partner system is not permitted by the user forfunction class INBOUND RECEIVE.

FTC3015 SUBMISSION REJECTED. VIOLATION OF USER INBOUND PROCESSING LEVEL (B) Routing code: C Weight: 99

MeaningThe security level of the partner system is not permitted by the user forfunction class INBOUND PROCESSING.

FTC3016 SUBMISSION REJECTED. VIOLATION OF USER INBOUND FILE MANAGEMENT LEVEL (B) Routing code: * Weight: 99

MeaningThe security level of the partner is not permitted by the user for functionclass INBOUND FILE MANAGEMENT

FTC3021 SUBMISSION REJECTED. VIOLATION OF ADM OUTBOUND SEND LEVEL (B) Routing code: C Weight: 99

MeaningThe security level of the partner system is not permitted by theadministrator for function class OUTBOUND SEND.

FTC3022 SUBMISSION REJECTED. VIOLATION OF ADM OUTBOUND RECEIVE LEVEL (B) Routing code: C Weight: 99

MeaningThe security level of the partner system is not permitted by theadministrator for function class OUTBOUND RECEIVE.

FTC3023 SUBMISSION REJECTED. VIOLATION OF ADM INBOUND SEND LEVEL (B) Routing code: C Weight: 99

MeaningThe security level of the partner system is not permitted by theadministrator for function class INBOUND SEND.

FTC3024 SUBMISSION REJECTED. VIOLATION OF ADM INBOUND RECEIVE LEVEL (B) Routing code: C Weight: 99

MeaningThe security level of the partner system is not permitted by theadministrator for function class INBOUND RECEIVE.

242 U41096-J-Z125-2-76


FTC3025 SUBMISSION REJECTED. VIOLATION OF ADM INBOUND PROCESSING LEVEL (B) Routing code: C Weight: 99

MeaningThe security level of the partner system is not permitted by theadministrator for function class INBOUND PROCESSING.

FTC3026 SUBMISSION REJECTED. VIOLATION OF ADM INBOUND FILE MANAGEMENT LEVEL (B) Routing code: * Weight: 99

The security level of the partner is not permitted by the administrator forfunction class INBOUND FILE MANAGEMENT

U41096-J-Z125-2-76 243

Related publicationsopenNet Server V2.0 (BS2000/OSD)BCAM V16.0A Volume 1User Guide

Target groupThe manual is intended for network planners, generators and administrators who defineBS2000 systems.ContentsBCAM Volume 1 describes BCAM itself, how it is embedded in TRANSDATA and TCP/IPand ISO networks, plus generation and administrative activities.Generation examples illustrate the description.Additionally BCAM tools for generation and diagnosis are described.

openNet Server V2.0 (BS2000/OSD)BCAM V16.0A Volume 2Reference Manual

Target groupThe manual is intended for network operators, generators and administrators who defineBS2000 systems.ContentsBCAM Volume 2 is based on Volume 1 and describes in detail the BCAM commandsrequired for generation and operation.The KOGS macros required for static generation are introduced and the BCAM messagesare listed.

openNet Server V2.0, interNet Services V2.0 (BS2000/OSD)SNMP Management for openNet Server and interNet ServicesUser Guide

Target groupThis manual is intended for network and system administrators wishing to use SNMP-basednetwork and system management.ContentsThe manuals contains detailed descriptions of the MIBs delivered with openNet Server, theFTP-MIB delivered with interNet Services, and the installation and operation of thesubagents. Operation of the BCAM Manager is described in detail in a separate chapter.

244 U41096-J-Z125-2-76

Related publications

openNet Server (BS2000/OSD)IPv6 Introduction and Conversion Guide, Stage 1User Guide

Target groupThis manual is intended for everyone responsible for deciding as to the introduction of IPv6in BS2000/OSD, as well as anyone using the IPv6 functionality on BS2000/OSDmainframes or planning to install IPv6 in BS2000/OSD.ContentsThe manual explains the commercial and technical foundations of IPv6. In addition, itdescribes the transition from IPv4 to IPv6 with the aid of examples and outlines the currentstatus of the implementation of IPv6 in BS2000/OSD. Detailed information on “IPv6addressing” and “DNS utilization” can be found in the appendix.

interNet Services V2.0 (BS2000/OSD)Administrator Guide

Target groupThis manual is intended for network planners, generators and administrators who wish touse Internet Services in BS2000/OSD.ContentsThe manual describes the functionality of the Internet ServicesBOOTP/DHCP, TFTP, DNS, FTP, LDAP and NTP in BS2000/OSD. It also covers the instal-lation, administration, operation, and logging and diagnostic options of the individualcomponents, as well as the FTP exit and the TELNET exits.

interNet Value Edition V1.0B (BS2000/OSD)User Guide

Target groupThis manual is intended for network planners, generators and administrators who wish touse Mail Service in BS2000/OSD.ContentsinterNet Value Edition is a supplement to interNet Services that is available free of charge.The manual introduces the components of interNet Value Edition and provides informationon the installation, administration and operation of Mail Service in BS2000/OSD.

CMX(BS2000)Communication Method in BS2000 User Guide

Target groupProgrammers of transport service (TS) applicationsContentsCMX (BS2000) offers application programs a uniform interface to the transport services.You can use CMX (BS2000) to create application programs which can communicate withother applications independently of the transport system.

U41096-J-Z125-2-76 245


SNMP Management V5.0SNMP Management for BS2000/OSDUser Guide

Target groupThe manual addresses network administrators/operators and system administrators whowish to integrate a BS2000 system in SNMP-based management or operate such a system.Contents

This manual describes how SBA-BS2, SSC-BS2, SSA-SM2-BS2 and SSA-OUTM-BS2 areembedded in BS2000/OSD, the installation and configuration procedures required toenable operation, and actual system operation. The Agents and their MIBs which arerequired for monitoring are dealt with in detail. Installation and configuration of the relevantmanagement applications on the Unicenter TNG, TransView SNMP and HP OpenViewmanagement platforms are also described.Further central topics of the manual are access to management information via the WorldWide Web, and the Trap Server for Solaris and Reliant UNIX.

C Library Functions (BS2000/OSD)for POSIX ApplicationsReference Manual

Target groupThis manual addresses C and C++ programmers.ContentsThe manual documents the XPG4-conformant C programming interface which is supportedby the POSIX subsystem in BS2000. This programming interface permits access to boththe POSIX file system and BS2000 files. The programming interface also incorporatesextensions which ensure compatibility with the existing C library described in a separatechapter.

XHCS(BS2000/OSD)8-Bit Code Processing in BS2000/OSDUser Guide

Target groupUsers of the DCAM, TIAM and openUTM access methods, system support staff, and usersmigrating from EHCS to XHCS.ContentsXHCS (Extended Host Code Support) is a software package of BS2000/OSD that lets youuse extended character sets in conjunction with 8-bit terminals. XHCS is also the centralsource of information on the coded character sets in BS2000/OSD. XHCS replaces EHCS.

246 U41096-J-Z125-2-76


BS2000User Commands (ISP Format)User Guide

Target groupBS2000 users (nonprivileged)Contents– All BS2000 system commands in alphabetical order with detailed explanations and

examples– The following products are dealt with: BS2000-GA, MSCF, JV, FT, TIAMApplicationsBS2000 interactive/batch mode, procedures

IMON (BS2000/OSD)Installation MonitorUser Guide

Target groupThis manual is intended for systems support staff of the BS2000/OSD operating system.ContentsThe manual describes the installation and administration of BS2000 software using theIMON installation monitor and its three components IMON-BAS, IMON-GPN and IMON-SIC. Installation (standard and customer-specific) using the component IMON-BAS forsystems with BS2000-OSD V2.0 and as of BS2000-OSD V3.0 is described in detail with theaid of examples in two separate chapters.

BS2000/OSD-BCIntroductory Guide to Systems SupportUser Guide

Target groupThis manual is addressed to BS2000/OSD systems support staff and operators.ContentsThe manual covers the following topics relating to the management and monitoring of theBS2000/OSD basic configuration: system initialization, parameter service, job and taskcontrol, memory/device/user/file/pubset management, assignment of privileges,accounting and operator functions.

U41096-J-Z125-2-76 247


Ordering RFCs

If the Requests for Comments (RFCs) referred to in the text are not included with delivery,they can be ordered in hardcopy form (copying charge) or fetched as a file from "anonymousInternet FTP" or via e-mail.

Anonymous Internet FTP: in order to fetch an RFC via the Internet from the systemnic.ddn.mil (IP address 192.67.67.20), please proceed as follows:– set up an FTP connection to the system: ftp nic.ddn.mil– you can now load the required documents from the directory rfc; a list of the available

documents can be found in the file rfc-index.txt.

e-mail:

If you do not have Internet access but can use electronic mail, you can request an RFC inthis way. The document will be sent to you in response to your Mail query.

To do this, send a mail to the user service on the system nic.ddn.mil:mail [email protected]

In the Subject field enter the number of the desired RFC, e.g.:Subject: RFC 1155

Written queries concerning RFCs should be submitted to:

DDN Network Information CenterSRI International333 Ravenswood Ave.Menlo Park, CA 94025, U.S.A.Telefon: 415-859-3695

e-mail: [email protected]

Ordering manuals

Please apply to your local office for ordering the manuals.

Eine Dokuschablone von Frank Flacheneckerby f.f. 1992

U41096-J-Z125-2-76 249

Index

! 119command (TELNET) 226

? 118TELNET command 225

^]TELNET command 224

Aabbreviated forms 129abbreviation 134access authorization 24access check

FTAC 124access control 114access protection 25, 121admission profile 167

create 149create (CREATE-FT-PROFILE) 149delete 160display 198display (SHOW-FT-PROFILE) 198modify (example) 179modify (MODIFY-FT-PROFILE) 167modify privilege 171name specification 150privileged 151remove privilege 171

admission set 123, 162, 163, 181basic functions 152display 181display (SHOW-FT-ADMISSION-SET) 181output 181

alias 134alphanum-name (data type) 135

append 38ASCII 31ascii 39ASCII/EBCDIC code conversion 31

Bbasic function 164

admission set 152limit (IGNORE-MAX-LEVELS) 152, 172

basic functionslimit (IGNORE-MAX-LEVELS) 152

batch callFTP client 25

bell 40binary 39, 41binary file processing 55binary text file processing 55BS2000/OSD

switch file system 79bye 24, 42

Ccat (suffix for data type) 144cat-id (data type) 135cd 43cdup 45change

working directory 43client, terminate 25close 25, 46

TELNET command 209code conversion 31, 101, 221

250 U41096-J-Z125-2-76

Index

code conversion tablechange 90EBCDIC 101, 221ISO 101, 221

command! 119! (TELNET) 226? 118? (TELNET) 225^] (TELNET) 224append 38ascii 39bell 40binary 39, 41bye 24, 42cd 43cdup 45close 25, 46close (TELNET) 209crmod 210crmod (TELNET) 210debug 47debug (TELNET) 211delete 48dir 49escape (TELNET) 212exit 51, 213file 52form 54ftyp 38, 55get 57glob 59hash 60help 61, 214jobvar 62lcd 64ldir 66lls 67lpwd 68ls 69mdelete 71mdir 73mdtm 20mget 74

mkdir 76mls 77modchar 28, 79mode 81mput 82open 23, 24, 84open (TELNET) 215options (TELNET) 217prompt 86put 87pwd 43, 88quit 24, 89quit (TELNET) 218quote 28, 34, 90recv 91reget 92remotehelp 33, 93rename 94reput 95rest 21return code 146rexit 96, 219rmdir 97runique 98send 99send (TELNET) 220sendport 100setcode 101setcode (TELNET) 221setfile 102settime 103size 20status 39, 104status (TELNET) 222struct 105sunique 106svar 107syntax representation 131system 109tenex 110trace 111trace (TELNET) 223type 112user 114

U41096-J-Z125-2-76 251

Index

verbose 116command overview 37command-rest (data type) 135composed-name (data type) 135constructor (string) 142control data transmission 32corr (suffix for data type) 144, 145create

admission profile 149CREATE-FT-PROFILE 149crmod 210c-string (data type) 135

Ddata type

alphanum-name 135cat-id 135command-rest 135composed-name 135c-string 135date 135device 135filename 136fixed 135integer 137name 137posix-filename 137posix-pathname 138product-version 138structured-name 138text 138time 138vsn 138x-string 139x-text 139

data types in SDF 131, 135suffixes 132

date (data type) 135debug 47DEBUG output

FTP 47TELNET 211

default admission set 181

default string%BS2000 79%POSIX 79

default value 129define

name of admission profile 150transfer admission 150transfer format 54

delete 48admission profile 160

DELETE-FT-PROFILE 160device (data type) 135diagnostics

FTP 47TELNET 211

dir 49display

admission profile 198admission profile (SHOW-FT-PROFILE) 198admission set 181admission sets (example) 182, 192, 200admission sets (SHOW-FT-ADMISSION-

SET) 181MAX-ADM-LEVELS 183MAX-USER-LEVELS 183

display (FTAC) 185DMS file system 27

Eeffects

FT profile 126enable/disable bell 40escape

TELNET command 212escape character

^] 224TELNET 212

examplelog record output 193MODIFY-FT-PROFILE 179show logging records 196SHOW-FT-ADMISSION-SET 182, 192, 200

exit 51, 213

252 U41096-J-Z125-2-76

Index

exit routine, clientTELNET 213

EXPANSION 155expansion of metacharacter 59explanatory text 229

Ffile 52

unstructured 31file management

interplay (FTAC) 122file management function

modify in admission profile 178file systems

switch 28file transfers 33file type

ISAM 31PAM 31SAM 31

FILE-NAMEoperand description 176

filename (data type) 136FILE-PASSWORD 177

operand description 156fixed (data type) 135follow-up processing

prohibited 126form 54FT profile 123

effects 126FTAC

access check 124file management 122password 163transfer admission 123

FTAC functionalitydisplay admission profile 198display admission sets 181display logging records 185modify admission profile 167

FTAC message file 229FTAC messages 229FTAC system messages 229

FTPaccess protection mechanism 25client 11, 23, 33command overview 37control 26DEBUG output 47diagnostics 47file attributes 31file names 37file transfer 33information on files and directories 26, 27input prompt 25overview of commands 37path names 26server 11, 23, 33server exits 96server function call 13, 30start 24

FTP client, batch call 25ftyp 38, 55

Ggen (suffix for data type) 144get 57glob 59global index 142

Hhash 60help 61, 214HOME directory 28

IIGNORE-MAX-LEVELS

operand description 152, 172inbound

file management 122, 153, 165, 173receive 122, 152, 164, 173send 122, 152, 164, 172

inbound request 122INBOUND-FILEMANAGEMENT 153, 165, 173INBOUND-RECEIVE 152, 164, 173INBOUND-SEND 152, 172index 142

U41096-J-Z125-2-76 253

Index

information on FTP 26INITIATOR

operand description 154, 175, 191integer (data type) 137

Jjobvar 62

Kkeyword 129

Llcd

command 64ldir 66limit

basic functions 152basic functions (IGNORE-MAX-

LEVELS) 152, 172lls 67local area network (LAN) 47log record

example (long) 193logging record 185LOGGING-DATE

operand description 188LOGGING-TIME

operand description 188login admission 123LOGON authorization 153, 173Long form 129lpwd 68ls 69

Mman (suffix for data type) 144, 145mandatory (suffix for data type) 145MAX-ADM-LEVEL 164

description of output fields 183MAX-PARTNER-LEVEL 155, 176MAX-USER-LEVEL 164

description of output fields 183mdelete 71mdir 73

mdtm 20message code 229metacharacters, FTP 29metasyntax of SDF 131metasyntax SDF 133mget 74mkdir 76mls 77modchar 28, 79mode 81modify

admission profile 167admission profile (MODIFY-FT-

PROFILE) 167admission set 162file management function in admission

profile 178local files and directories 29privilege in admission profile 171

modify files and directories 29MODIFY-FT-ADMISSION-SET 163MODIFY-FT-PROFILE 168, 198

modify admission profile 167MODIYF-FT-PROFILE

example 179mput 82

Nname

specification for admission profile 150name (data type) 137notational conventions for SDF 131

Oodd (suffix for data type) 144open 24, 84

TELNET command 215OPS variables

SHOW-FT-LOGGING-RECORDS 196options

TELNET command 217order

RFC 247outbound request 122

254 U41096-J-Z125-2-76

Index

outputadmission set 181log records 193

OWNER-IDENTIFICATIONoperand description 188

Ppartner system

specify 126PARTNER-NAME

operand description 155, 176password 162

FTAC 163PLAM library 32positional operand 129POSIX

file system 27, 43, 67files 38, 57, 92, 95switch file system 43, 64, 79, 104

POSIX file system 27posix-filename (data type) 137posix-pathname (data type) 138prefix

specify for file name 126privileged admission profile 151product-version (data type) 138prohibited follow-up processing 126prompt 86PRV 182put 87PW 182pwd 43, 88

Qquit 24, 89

TELNET command 218quote 28, 34, 90quotes 129quotes (suffix for data type) 145

RRDATA 25recv 91reget 92

remote working directorychange 43

remotehelp 33, 93remove

privileging the admission profile 171rename 94reput 95rest 21restriction

syntax 126transfer direction 126

return code commandgeneral description 146

return code, command 146rexit 96, 219RFC

order 247rmdir 97runique 98

SSDF

syntax representation 131SDF syntax representation 131security level 155, 164, 176send 99

TELNET command 220sendport 100sep (suffix for data type) 144SERVER

TELNET 227server exits

FTP 96set server exits

TELNET 219set up

transfer admission 150setcode 101

TELNET command 221setfile 102settime 103setting exit routines, TELNET client 51short form 129

U41096-J-Z125-2-76 255

Index

showFTAC logging records 185

SHOW-FT-ADMISSION-SET 181FTAC command 181

SHOW-FT-LOGGING-RECORDSexample 196FTAC command 185OPS variables 196

SHOW-FT-PROFILE 198, 200FTAC command 198

size 20SOCKET TRACE output 223specify

partner systems 126prefix for file name 126

SPIN-OFF mechanism 25statement

syntax representation 131status 39, 104

TELNET command 222struct 105structured-name (data type) 138subcode1 146subcode2 146suffixes for data types 132, 140sunique 106svar 107syntax

restriction 126syntax description 131system 109

TTELNET

client 203command mode 205, 207, 209commands 207DEBUG output 211diagnostics 211escape character 207, 212exit routine, client 213input mode 205, 206, 207mode of operation 207monitoring functions 203

overview of commands 208server 203, 227setting exit routines, client 51setting server exits 219starting the program 207trace functions 203

temp-file (suffix for data type) 144tenex 39, 110text (data type) 138text file processing 55time (data type) 138trace 111

TELNET command 223TRACE output 111TRANSDATA network 23transfer admission 24, 169, 170, 198, 199

define 150file transfer request 126FTAC 123

transfer direction 154, 175restriction 126

transfer formatdefine 54

transfer mode 81transfer structure 105transfer type 39, 112

ASCII 39EBCDIC 39

TRANSFER-ADMISSION 182, 192, 200operand description 150, 169, 199

TRANSFER-DIRECTION 154, 175type 39, 112type of transfer 31

Uunstructured files 31user 114user (suffix for data type) 145user ID 163, 181USER-ADMISSION

operand description 153UTC 10

256 U41096-J-Z125-2-76

Index

Vverbose 116vers (suffix for data type) 145vsn (data type) 138

Wwild(n) (suffix for data type) 140wild-constr (suffix for data type) 142with-constr (suffix for data type) 142without (suffix for data type) 144without-cat (suffix for data type) 144without-corr (suffix for data type) 144without-gen (suffix for data type) 144without-man (suffix for data type) 144without-odd (suffix for data type) 144without-sep (suffix for data type) 144without-user (suffix for data type) 145without-vers (suffix for data type) 145with-wild(n) (suffix for data type) 140working directory 26, 37

change 43WRITE-MODE 156, 178

XXHCS 31, 101, 221x-string (data type) 139x-text (data type) 139

U41096-J-Z125-2-76

Contents1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Summary of contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.4 Changes compared to the previous version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.5 README file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Internet services in BS2000/OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.1 FTP servers in BS2000/OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.2 SNMP subagent for FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.3 FTP client in BS2000/OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.4 Overview of commands (FTP client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

append - append a local file to a remote file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38ascii - set transfer type to ASCII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39bell - enable/disable bell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40binary - set transfer type to BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41bye - exit FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42cd - change remote working directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43cdup - change to next higher directory (one level up) . . . . . . . . . . . . . . . . . . . . . . . . . . 45close - close connection to remote host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46debug - enable/disable DEBUG output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47delete - delete a remote file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48dir - show information on remote file(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49exit - define parameters for local exit routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51file - define file attributes on local host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52form - change or query transfer format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54ftyp - specify processing type for files on local host . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55get - fetch a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57glob - enable/disable expansion of metacharacters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59hash - enable/disable transfer progress indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60help - show information on FTP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61jobvar - store error information in a job variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62lcd - change local working directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64ldir - list information on local files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

U41096-J-Z125-2-76

Contents

lls - list file names on local host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67lpwd - show local working directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68ls - list file names on remote host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69mdelete - delete multiple remote files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71mdir - show information on remote files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73mget - fetch multiple remote files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74mkdir - create a remote directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76mls - list file names in multiple directories on remote host . . . . . . . . . . . . . . . . . . . . . . . 77modchar - modify character string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79mode - change or query transfer mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81mput - send multiple local files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82open - open the connection to a remote host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84prompt - enable/disable prompting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86put - send a local file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87pwd - show remote working directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88quit - exit FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89quote - call server functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90recv - fetch a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91reget - fetch a file with restart support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92remotehelp - get help on functions of the remote FTP server . . . . . . . . . . . . . . . . . . . . 93rename - rename remote files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94reput - send a local file with restart support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95rexit - define parameters for remote exit routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96rmdir - remove a remote directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97runique - enable/disable unique storage of local files . . . . . . . . . . . . . . . . . . . . . . . . . . 98send - send a local file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99sendport - enable/disable port command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100setcode - change code tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101setfile - enable/disable file marker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102settime - set time limit for server responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103status - display FTP status information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104struct - change or query transfer structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105sunique - store remote files uniquely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106svar - store error information in an SDF-P variable . . . . . . . . . . . . . . . . . . . . . . . . . . . 107system - display server information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109tenex - set transfer type to BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110trace - enable/disable SOCKET trace output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111type - change or query transfer type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112user - specify user ID on remote host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114verbose - enable/disable server responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116? - show information on FTP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118! - switch to BS2000/OSD command mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

U41096-J-Z125-2-76

Contents

4 FTAC interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214.1 FTAC functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214.1.1 Features of the FTAC function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214.1.2 Admission set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234.1.3 FT profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234.1.4 Effects of an FT profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264.1.5 Monitoring the FTP server with FTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274.2 FTAC command interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284.2.1 Functional command overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284.2.2 Entering FTAC commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1294.2.3 SDF syntax representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314.2.4 Command return codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464.2.5 OPS variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474.2.6 Output in CSV format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484.2.7 CREATE-FT-PROFILE - Create admission profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1494.2.8 DELETE-FT-PROFILE - Delete admission profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1604.2.9 MODIFY-FT-ADMISSION-SET - Modify admission set . . . . . . . . . . . . . . . . . . . . . . . . 1624.2.10 MODIFY-FT-PROFILE - Modify admission profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674.2.11 SHOW-FT-ADMISSION-SET - Display admission sets . . . . . . . . . . . . . . . . . . . . . . . . 1814.2.12 SHOW-FT-LOGGING-RECORDS - Display logging records . . . . . . . . . . . . . . . . . . . . 1854.2.13 SHOW-FT-PROFILE - Display admission profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

5 TELNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2035.1 TELNET client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2045.1.1 Command mode and input mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2055.1.2 Overview of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

close - close connection to remote host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209crmod - enable/disable insertion of carriage returns . . . . . . . . . . . . . . . . . . . . . . . . . . 210debug - enable/disable DEBUG output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211escape - change ESCAPE character . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212exit - enable/disable client exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213help - show information on TELNET commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214open - open connection to a remote host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215options - enable/disable display of options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217quit - exit TELNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218rexit - enable/disable server exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219send - send special commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220setcode - change code tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221status - display TELNET status information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222trace - enable/disable SOCKET trace output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223^] - switch to TELNET command mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224? - show information on TELNET commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225! - switch to BS2000 command mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

5.2 TELNET server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

U41096-J-Z125-2-76

Contents

6 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2296.1 FTAC system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2296.1.1 FTCnnnn messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

U41096-J-Z125-2-76

interNet Services V2.0 (BS2000/OSD)

User Guide

Target group This manual is intended for users and network planners, generators, and administrators, who wish to use Internet Services in conjunction with BS2000/OSD.ContentsThe manual introduces the components of interNet Services. It contains a detailed descrip-tion of FTP, the FTAC interface for FTP and TELNET: Network administrators require this manual as a supplement to the Administrator Guide.

Edition: February 2001

File: iserv_bh.pdf

Copyright © Fujitsu Siemens Computers GmbH, 2001.

All rights reserved.Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respective manufacturers.

Comments on interNet Services V2.0User Guide

U41096-J-Z125-2-76

Fujitsu Siemens Computers GmbHUser Documentation81730 Munich

Fax: (++49) 0 700/ 372 00000

e-mail: [email protected]://manuals.fujitsu-siemens.com

CommentsSuggestionsCorrections

✁

Submitted by

Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Compu-ters. This new subsidiary of Fujitsu has been renamed Fujitsu Technology So-lutions.

This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed.

Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions.

Contact and support addresses will now be offered by Fujitsu Technology So-lutions and have the format …@ts.fujitsu.com.

The Internet pages of Fujitsu Technology Solutions are available at http://ts.fujitsu.com/... and the user documentation at http://manuals.ts.fujitsu.com.

Copyright Fujitsu Technology Solutions, 2009

Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seit-dem den Namen Fujitsu Technology Solutions.

Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion.

Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind.

Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Form …@ts.fujitsu.com.

Die Internetseiten von Fujitsu Technology Solutions finden Sie unter http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die Benutzerdokumentation.

Copyright Fujitsu Technology Solutions, 2009

Date post:	05-Jul-2018
Category:	Documents
Upload:	lamdat
View:	216 times
Download:	0 times

interNet Services V2.0 (BS2000/OSD) User...

Documents