microfit 7 user's guide - bull on-line support...

Microfit 7

User's Guide

DPS

7000/XTA

NO

VASC

ALE

7000

Communications: Applications

REFERENCE47 A2 20UC 04

DPS7000/XTANOVASCALE 7000

Microfit 7User's Guide

Communications: Applications

October 1995

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

REFERENCE47 A2 20UC 04

The following copyright notice protects this book under Copyright laws which prohibit such actions as, but notlimited to, copying, distributing, modifying, and making derivative works.

Copyright Bull SAS 1991, 1995

Printed in France

Suggestions and criticisms concerning the form, content, and presentation of thisbook are invited. A form is provided at the end of this book for this purpose.

To order additional copies of this book or other Bull Technical Publications, youare invited to use the Ordering Form also provided at the end of this book.

Trademarks and Acknowledgements

We acknowledge the right of proprietors of trademarks mentioned in this book.

Intel® and Itanium® are registered trademarks of Intel Corporation.

Windows® and Microsoft® software are registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark in the United States of America and other countries licensed exclusively throughthe Open Group.

Linux® is a registered trademark of Linus Torvalds.

The information in this document is subject to change without notice. Bull will not be liable for errors containedherein, or for incidental or consequential damages in connection with the use of this material.

47 A2 20UC Rev04 iii

Preface

INTENDED AUDIENCE

This document is intended to serve as a user guide and reference manual for systemsengineers, analyst/programmers and terminal operators.

SCOPE AND OBJECTIVES

This manual describes the generation, operation and use of the MICROFIT 7 applicationfor transferring files between the DPS 7000 and the Zenith PC or QUESTAR 400.

STRUCTURE OF THIS DOCUMENT

Section 1: gives an overall view of MICROFIT 7.

Section 2: describes the types of files and their related transferparameters. It also lists the commands for managingMICROFIT 7.

Section 3: deals with preparing, generating and activating MICROFIT 7.

Section 4: lists MICROFIT 7 error messages.

Section 5: describes the configuration, logon and file transfer of theZenith PC through the MIMIC (asynchronous) connection.

Section 6: describes the configuration, logon and file transfer of theZenith PC through the ATLANTIS (synchronous) connection.

Section 7: describes the configuration, logon and file transfer of theQUESTAR 400.

Section 8: describes the integration of the MICROFIT 7 application in auser TDS.

Microfit 7 User's guide

iv 47 A2 20UC Rev04

Section 9: describes the Atlantis connection from PC327x terminals.

Section 10: describes the IRMA connection from PC327x terminals.

RELATED DOCUMENTS

TDS Documentation

TDS Concepts..................................................................................................47 A2 26UTTDS Administrator's Guide...............................................................................47 A2 32UTTDS Programmer's Guide................................................................................47 A2 33UTTDS C Programmer's Guide ...........................................................................47 A2 07 UT

47 A2 20UC Rev04 v

Table of Contents

1. Introduction ........................................................................................................... 1-1

2. Microfit 7 Functions and Operation ............................................................ 2-1

2.1 MICROFIT 7 FUNCTIONS.......................................................................................... 2-1

2.2 CONNECTING TO THE TARGET APPLICATION ..................................................... 2-1

2.2.1 Automatic Mode ........................................................................................................ 2-22.2.2 Manual Mode ............................................................................................................. 2-32.2.3 Command Mode ........................................................................................................ 2-32.2.4 Other Connection Modes ......................................................................................... 2-3

2.3 TRANSFERRING FILES ............................................................................................. 2-4

2.3.1 Abnormal Termination .............................................................................................. 2-42.3.2 File Names ................................................................................................................. 2-52.3.3 File Types ................................................................................................................... 2-62.3.4 File Transfer Parameters .......................................................................................... 2-7

2.4 BREAK HANDLING .................................................................................................... 2-7

2.5 MICROFIT 7 COMMANDS ......................................................................................... 2-8

2.5.1 BYE ............................................................................................................................. 2-82.5.2 CONNECT .................................................................................................................. 2-82.5.3 DISPLAY ..................................................................................................................... 2-102.5.4 HELP ........................................................................................................................... 2-102.5.5 QUIT............................................................................................................................ 2-102.5.6 RECEIVE..................................................................................................................... 2-112.5.7 SEND .......................................................................................................................... 2-122.5.8 SET ............................................................................................................................. 2-13

Microfit 7 User's Guide

vi 47 A2 20UC Rev04

3. Generation and Activation .............................................................................. 3-1

3.1 PREPARATION .......................................................................................................... 3-1

3.2 GENERATION ............................................................................................................ 3-2

3.3 STARTING MICROFIT 7 ............................................................................................ 3-3

4. Microfit 7 Error Messages ............................................................................... 4-1

5. Mimic Connection ............................................................................................... 5-1

5.1 TERMINAL CONFIGURATION .................................................................................. 5-1

5.2 CONNECTING TO MIMIC .......................................................................................... 5-2

5.3 CONNECTING TO DPS 7000 THROUGH DATANET ............................................... 5-4

5.4 CONNECTING TO DPS 7000 THROUGH PAD AND DATANET .............................. 5-5


5.5.1 Transferring Files from the PC to the DPS 7000 .................................................... 5-75.5.2 Transferring Files from the DPS 7000 to the PC .................................................... 5-8

Table of Contents

47 A2 20UC Rev04 vii

6. Atlantis Connection ........................................................................................... 6-1

6.1 TERMINAL CONNECTION ........................................................................................ 6-1

6.2 CONNECTING TO ATLANTIS ................................................................................... 6-2

6.3 CONFIGURATION MENU .......................................................................................... 6-2

6.3.1 Filling in the Configuration Parameters .................................................................. 6-36.3.2 Programming the Function Keys ............................................................................. 6-7

6.4 CONNECTING TO DPS 7000 THROUGH DATANET ............................................... 6-8


6.5.1 Filling in the File Transfer Initialization Form ........................................................ 6-96.5.2 Filling in the File Transfer Parameters .................................................................... 6-11

6.6 DISCONNECTING FROM ATLANTIS ........................................................................ 6-14

7. Questar 400 Connection .................................................................................. 7-1

7.1 CONNECTION TO MICROFIT 400 ............................................................................ 7-2

7.2 FILE TRANSFER ........................................................................................................ 7-4

7.2.1 Transferring Files from the DPS 7000 to the QUESTAR 400 ................................. 7-47.2.2 Transferring Files from the QUESTAR 400 to the DPS 7000 ................................. 7-57.2.3 MICROFIT 400 Parameters ....................................................................................... 7-6


viii 47 A2 20UC Rev04

8. Microfit 7 Integration ......................................................................................... 8-1

8.1 INTRODUCTION......................................................................................................... 8-1

8.2 TDS PREPARATION .................................................................................................. 8-1

8.3 IMPLEMENTATION IN TDSGEN ............................................................................... 8-1

8.3.1 MICROFIT transaction .............................................................................................. 8-28.3.2 Special transactions ................................................................................................. 8-38.3.3 Shared storage .......................................................................................................... 8-58.3.4 TDS Section Clauses ................................................................................................ 8-5

8.4 GENERATION AND ACTIVATION ............................................................................. 8-6

8.4.1 Generation ................................................................................................................. 8-68.4.2 Activation ................................................................................................................... 8-6

8.5 CONNECTION MODES.............................................................................................. 8-7

8.6 PROGRAMMING RULES ........................................................................................... 8-8

8.6.1 STARTUP Transaction .............................................................................................. 8-88.6.2 LOGON Transaction .................................................................................................. 8-88.6.3 DISCNCT Transaction ............................................................................................... 8-98.6.4 RESTART Transaction .............................................................................................. 8-10

8.7 CALL "H_MML_TRNAME" PROCEDURE ................................................................ 8-11

8.8 SPAWNING OF MICROFIT TRANSACTION ............................................................. 8-11

8.9 RESTRICTIONS ......................................................................................................... 8-12

9. Atlantis Connection from PC-327x Terminals ........................................ 9-1

9.1 TERMINAL CONNECTION ........................................................................................ 9-1

9.2 CONNECTING TO ATLANTIS ................................................................................... 9-2

Table of Contents

47 A2 20UC Rev04 ix

9.3 CONFIGURATION MENU .......................................................................................... 9-3

9.3.1 Filling in the Configuration Parameters .................................................................. 9-49.3.2 Filling in the Function Key Program Parameters ................................................... 9-8

9.4 CONNECTION TO THE HOST SYSTEM................................................................... 9-9

9.5 CONNECTION TO DPS 7000 THROUGH DATANET ............................................... 9-10


9.6.1 Filling in the File Transfer Initialization Form ........................................................ 9-119.6.2 Filling in the File Transfer Parameters .................................................................... 9-13

10. IRMA Connection from PC-327x terminals .............................................. 10-1

10.1 STARTING THE EMULATOR .................................................................................... 10-1

10.2 CONNECTING TO THE HOST SYSTEM................................................................... 10-1

10.3 CONNECTION TO DPS 7000 THROUGH DATANET ............................................... 10-2



x 47 A2 20UC Rev04

Table of Contents

47 A2 20UC Rev04 xi

Illustrations

Figures

2-1 MICROFIT operations ................................................................................................. 2-25-1 Configuration Menu..................................................................................................... 5-25-2 Rear Panel Switch Menu............................................................................................. 5-25-3 Extended Configuration Menu..................................................................................... 5-35-4 File Transfer Menu ...................................................................................................... 5-66-1 TBV Configuration Menu............................................................................................. 6-26-2 Configuration Menu..................................................................................................... 6-36-3 Function Key Programming Screen ............................................................................ 6-76-4 File Transfer Initialization Form................................................................................... 6-96-5 File Transfer Parameters Form................................................................................... 6-116-6 Transfer in Progress Screen ....................................................................................... 6-137-1 MICROFIT 400 File Transfer Menu............................................................................. 7-69-1 TDI Configuration Menu .............................................................................................. 9-39-2 TXI Configuration Menu .............................................................................................. 9-39-3 File Transfer Initialization Screen................................................................................ 9-119-4 File Transfer Parameters Form................................................................................... 9-13

Tables

7-1 MSTE 7107 Software Components............................................................................. 7-1


xii 47 A2 20UC Rev04

47 A2 20UC Rev04 1-1

1. Introduction

MICROFIT 7 is an MML (Micro-to-Mainframe Link) application which allows you to:

- transfer files between the DPS 7000 and a microcomputer- use a microcomputer to connect to host target applications on the DPS 7000.

The microcomputer can be:

• a Zenith PC or PC-like device functioning in:

- asynchronous mode by emulating a VIP7800- synchronous mode with ATLANTIS products (SCOM, UCOM and XCOM boards)

• a QUESTAR 400 functioning in synchronous mode by emulating a DKU7007.

Terminal Emulation

Terminal emulation means that the micro is seen by the DPS 7000 as a terminal.

For Zenith PC or PC-like devices:

- MIMIC offers both VIP7800 emulation as well as the file transfer facility.- TxV (where x = B, C, S or X) offers DKU7xxx emulation as well as the file transfer

facility.

For QUESTAR 400:

• MSTE offers DKU7007 emulation, while MICROFIT 400 ensures the file transfer facilitywith some TTY-like emulation.

File Transfer

Applications running on the DPS 7000 and the micros work on information contained infiles which are exchanged in both directions using the file transfer facility.

Cooperative Applications

Cooperation of applications running on both DPS 7000 and the micros is not implementedin the current release.


1-2 47 A2 20UC Rev04

47 A2 20UC Rev04 2-1

2. Microfit 7 Functions and Operation

2.1 MICROFIT 7 FUNCTIONS

The main functions of MICROFIT 7 are:

• the connection to the target applications• file transfer.

MICROFIT 7 uses a pass-through mechanism to handle sessions with target applications.This pass-through is not visible. This means that target applications connected over thepass-through are handled with the same user-visibility as those directly connected.

2.2 CONNECTING TO THE TARGET APPLICATION

Before you can transfer files, you must first connect to MICROFIT 7. Once underMICROFIT 7, the mode of connection to the target application on the DPS 7000 dependson the TDS authority code set for MML (see below). The target application is IOF or TDS.

The project under which you connect to MICROFIT 7 must include one of the following"MML/tds_authority_code"s in the APPLIST parameter of the CRP or MDP commands ofMAINTAIN_CATALOG (CATMAINT).

- MML/7FFF0000 : spawns MICROFIT 7 in manual modeprompt on connection: M:

- MML/7FFF0001 : spawns MICROFIT 7 in automatic modeprompt on connection: S:

- MML/7FFF0008 : no spawning and no administratormessage on connection: READY

- MML/7FFF000C : no spawning but administrator presentmessage on connection: READY


2-2 47 A2 20UC Rev04

If the prompt T: appears, enter "QUIT" to display message READY.

When READY appears, enter "MICROFIT" to obtain the prompt M:

Operations detailed in this manual apply at M: and S: levels.

Note: If no spawning is specified (tds_authority_code equals 7FFF000C or7FFF0008), a user name of up to 12 characters is allowed. In normal orautomatic mode, the length must not exceed 8 characters.

R E A D Y(T D S prom pt)

M :(C om m and m ode)$*$ C N M B M M L...

S :(P ro jec t's default app lication)

B YE B YE

B YE

B YE

M IC R O FIT

C N IO F

U ser nam e < = 12

B YE

7FF F0000 (M anua l m ode)

U ser nam e < = 87FFF 0001 (A utom atic m ode)

!

Q U IT

7F FF 000C7FF F0008

U ser nam e < = 8

Figure 2-1. MICROFIT operations

2.2.1 Automatic Mode

When you connect to MICROFIT 7, you are automatically connected to the targetapplication. The application is determined by the project in the SITE.CATALOG. It mustbe the default application for the project and must have a name other than MML. If thetarget application is IOF, you get the following prompt:

"<lsys-name>:"

When you disconnect from the target application, you automatically disconnect fromMICROFIT 7.

2.2.2 Manual Mode

In manual mode you connect to MICROFIT 7 at the MICROFIT 7 command level. Theprompt "M: " appears, to which MML commands can now be entered, including "manual"connection to the target application through the CONNECT command.

Microfit 7 Functions and Operation

47 A2 20UC Rev04 2-3

When you disconnect from the target application, you remain connected to MICROFIT 7at "M: " level. To disconnect from MICROFIT 7, you must enter the command BYE.

2.2.3 Command Mode

MML commands must be submitted at "M: " level. This prompt is sent automatically viaMML when you connect to MML in manual mode.

If you are connected to a target application, for example IOF, you must prefix the firstcommand at S: level with an exclamation mark ( ! ). When the first MML command (CNexcepted) is executed, you get the "M:" prompt and can then enter the next command.The QUIT command enables you to leave the MML command processor and return to thetarget application, except in the case of manual mode with no connected targetapplication.

Note: When a target application is connected and the you leave the MML commandprocessor, the screen is not cleared but remains for the application, in the samestate as it was when you entered the MML command level.

2.2.4 Other Connection Modes

You can also connect to MICROFIT 7:

• The TDS environment, for which the message READY appears.You must enter"MICROFIT" to get the M: prompt.


2-4 47 A2 20UC Rev04

2.3 TRANSFERRING FILES

You can transfer files in between the dialog with the target application. While the transferis executing, the target application remains connected. At the end of the transfer, youreturn to the target application without any change to the application environment.

The file transfer between the micro and the DPS 7000 is launched:

• either by the Zenith PC which is always the "initiator" of the transfer through its menu :the DPS 7000 then functions as "server" for both synchronous and asynchronous links

• or by MICROFIT 7 through the following commands addressed to it in normal mode:

SEND :where the DPS 7000 is "initiator-sender" and the QUESTAR 400 is "server"

RECEIVE :where the QUESTAR 400 is "initiator-sender" and the DPS 7000 is "server".

Note that the DPS 7000 is always the point of reference for SEND and RECEIVEcommands. File transfer is in both directions. The files exchanged are character andbinary files, accessed sequentially. Database and monitor shared files are not supported.

Data records are blocked in packets. Data integrity is guaranteed by packetacknowledgment, check-sum algorithms and retries of erroneous packets.

2.3.1 Abnormal Termination

If the transfer is terminated abnormally, there is no restart mechanism. The whole filemust be retransmitted.

Abnormal termination may be due to:

- errors on the file- too many retries on "timeout"- an abort of the application- premature or abnormal disconnection- system crash.


47 A2 20UC Rev04 2-5

2.3.2 File Names

DPS 7000 File Name

the name of the file or subfile under the following circumstances:

• file name of the format efn[..subfile][:md:dvc] being:

- either requested by MIMIC for Zenith PC

- or specified in SENDs and RECEIVEs entered at MICROFIT 7 command level andat the QUESTAR 400 when setting MICROFIT 400 in "receive" and "send" modes,respectively.

• subfile name if a default library has been specified through the SET command.

CATALOGED FILES

For DPS 7000 files, private catalogs are not supported. Only files cataloged in eitherSITE.CATALOG or "auto-attach" catalogs are supported.

UNCATALOGED FILES

The volume specified in <media-name> of the file-literal must be premounted at the startof the file transfer. Otherwise the transfer aborts with the message "HOST VOLUME NOTMOUNTED".

WARNING

When transferring files from the DPS 7000 to the PC, Microfit 7 doesnot support the asterisk naming convention for GCOS 7 libraries.

Micro File Name

The name of any Zenith PC or QUESTAR 400 files.

Zenith PC/QUESTAR 400 files :

The transfer of those files created by micro text-editors to the DPS 7000 results in one ofthe following messages sent by Microfit 7 :

- NO END OF RECORD DETECTED FOR A TEXT FILE AT CLOSE TIME.The transfer, however, terminates normally.

- A MICRO COMPUTER RECORD DOES NOT FIT IN HOST RECORD. ABORT.The transfer is aborted.


2-6 47 A2 20UC Rev04

2.3.3 File Types

The following points are to be noted:

- DPS 7000 files must be accessed sequentially.- Database files are not supported.- Monitor shared files are not supported.

Character or Text Files

A character or text file corresponds to source or printable file.

On the micro, the contents of the file are in ASCII. Records are transferred in a canonicalformat. From this format, they are converted to EBCDIC by MICROFIT 7.

When the DPS 7000 is the sender, a host file of SSF format is stripped of its controlrecords and headers before transmission to the micro.

When the DPS 7000 is the receiver and the receiving file is an SL library, the subfile willbe created in SSF format. You can therefore use this subfile under the LIBMAINT TextEditor. Writing a data record larger than 256 bytes aborts the file transfer with themessage:

"A MICRO COMPUTER RECORD DOES NOT FIT IN HOST RECORD. ABORT."

Binary Files

A binary file is transmitted in transparent mode. This means that the data transferred is anexact replica of the data in the original file.

When the DPS 7000 is the sender, a host file of SSF format is stripped of its controlrecords and headers before transmission to the micro.

Logical records are blocked in packets before transmission.

When the DPS 7000 is the receiver, received packets are blocked and split into logicalrecords according to the maximum RECSIZE value of the receiving file.

As a consequence, when transferring a member of a GCOS 7 library such as CULIB,LMLIB, BINLIB, etc. from host to Micro or Micro to Host, the receiving file loses the logicalstructures of the original member. This means that it can no longer be processed bystandard GCOS 7 utilities or by applications that manage it at logical level.

You can request binary transfer in one of three ways:

• by adding ",I" to the micro file-name for MIMIC using Zenith PC.

• by specifying IMAGE=Y in the SET command before launching MICROFIT 400 usingQUESTAR 400.

• by specifying OPTION-BINAIRE=0 in the ATLANTIS file transfer menu.


47 A2 20UC Rev04 2-7

2.3.4 File Transfer Parameters

These parameters are specified in the command SET. They are applicable to allsubsequent file transfers. You can display the current values using the DISPLAYcommand.

Most of these parameters are provisions for future connections with other micros in orderto override certain parameters, when the micro configured does not strictly conform towhat is implemented by MICROFIT 7.

LIB Parameter

The LIB parameter of the SET command allows you to declare a DPS 7000 defaultlibrary, so that only the name of the subfile need be specified, whatever the method of filetransfer (MIMIC or ATLANTIS for PC-like devices, or MICROFIT 400 for QUESTAR 400).

Data Compaction

Data records are compacted before transmission, using an algorithm specific toMICROFIT 7. Although this feature is negotiable, MICROFIT 7 always proposes datacompression.

Packet Size

Data records are blocked in MICROFIT 7 packets. The maximum packet size supportedis specified by both partners. For MICROFIT 7, the maximum is 2048 bytes.

File Record Size

Maximum RECSIZE for DPS 7000 files is 2046. This is an implementation restriction ofMICROFIT 7.

2.4 BREAK HANDLING

The target application, when connected, receives the "break" entered on the micro overMICROFIT 7. The visibility of the "break" to the application is the same as that for a directconnection to IOF or TDS.

Under the MML command processor, a "break" issued at "M: " level leads to a newprompt with "M: ". A "break" entered during the execution of a file transfer leads to anabort of the file transfer.


2-8 47 A2 20UC Rev04

2.5 MICROFIT 7 COMMANDS

In this section these commands are grouped by their functions, as follows:

- BYE and CONNECT (disconnection/connection)- DISPLAY, RECEIVE, SEND, and SET (file transfer)- HELP and QUIT (non specific).

2.5.1 BYE

Function

Open a session in manual mode with a target application. If a target application isconnected, CONNECT is rejected.

BYE issued at MICROFIT 7 command level in manual mode disconnects you fromMICROFIT 7.

Syntax

BYE ;

2.5.2 CONNECT

Function:

Open a session in manual mode with a target application. If a target application isconnected, CONNECT is rejected.

Syntax

{CN | CONNECT} application_name [ USER = { char8 | char12 } ] [ PROJECT = char12 ] [ BILLING = char12 ] [ PASSWORD = char12 ] [ STATION = { MAIN | char8 } ] [ INFO = char22 ] [ SITE = char4 ]


47 A2 20UC Rev04 2-9

where:

application-name is a mandatory parameter. It must be IOF or a version ofTDS.

USER is the submitter user for the connection, used as followsIf specified, a length of up to 12 characters is allowed:PASSWORD is mandatory if USER specifies a name otherthan that associated with MICROFIT 7.If it is not specified, the default is the user associated withMICROFIT 7, in which case its length must not exceed 8characters

PROJECT is the project name for the connection. The default is theproject name:- of the user associated with MICROFIT 7- or attached to the user defined in USER.

BILLING is the billing name for the connection. The default is thebilling name:- of the user associated with MICROFIT 7- or attached to the project either explicitly defined inPROJECT or implicitly associated with the user defined inUSER.

PASSWORD is the password for the connection. PASSWORD ismandatory if USER specifies a name other than thatassociated with MICROFIT 7.

STATION is the RBF station name to which the target application willbe attached. The default value is "MAIN".

INFO is user information given at logon, to be passed to thetarget application when connected. This parameter must beentered as a protected string, if it contains items separatedby special characters functioning as delimiters.Example : CN IOF,INFO='NSTARTUP,NEW';

SITE is the site name for a connection to a remote application(IOF or TDS).If USER, PROJECT, BILLING and PASSWORD arespecified, these values are checked at the remote siteagainst its SITE.CATALOG at connection time. If no useridentification is specified, the user connected to MICROFIT7 must be cataloged with a default PROJECT and BILLINGin the SITE.CATALOG of the remote site.Note 1 : When the target application is connected, filetransfer requests are always performed between the microand the site on which the MICROFIT 7 application isrunning.Note 2 : When the target application is connected, thelength of the message transmitted between the terminaland the target application is limited to 6144 characters.


2-10 47 A2 20UC Rev04

2.5.3 DISPLAY

Function

You can use this command to display all the file transfer parameters (which can beinitialized through the SET command) with their current values.

Syntax

{D | DISPLAY};

2.5.4 HELP

Function

Using this command displays a brief description of MICROFIT 7 commands.

Syntax

{H | HELP} [command-name];

where command-name can be SET or CN.

If you do not specify a command name, a brief description of all the commands isdisplayed.

2.5.5 QUIT

Function

Leave the MICROFIT 7 command level in automatic mode. QUIT is only effective if atarget application is connected. You leave MICROFIT 7 command mode and return to thetarget application, at the point exited. The commands issued at MICROFIT 7 commandlevel and subsequent messages are not cleared from the screen.

Syntax

{QUIT | /} ;


47 A2 20UC Rev04 2-11

2.5.6 RECEIVE

Function

Use this command to transfer a file from QUESTAR 400 to the DPS 7000, initialized bythe micro in normal mode.

When RECEIVE is issued at MICROFIT 7 command level, the DPS 7000 awaits thereception of the send-init-packet from QUESTAR 400. The QUESTAR 400 must setMICROFIT 400 in "send" mode through the activation of the F9 function key.

The DPS 7000 awaits reception of the send-init-packet until the lapse-time specified byDELAY of the SET command is exhausted. If by this time the send-init-packet has notarrived, the DPS 7000 aborts the file transfer request.

Syntax

{R | RECEIVE} [efn [...subfile-name] [:md:dvc:] ;

where:

- efn [ ..subfile_name ] is the external file name- :md:dvc are the media and device class

The DPS 7000 file-literal used as follows

• if specified, it is the name of the DPS 7000 receiving file

• if not specified, the file name entered on QUESTAR 400 is taken as the name of theDPS 7000 receiving file

• when SET with LIB has been issued, only the subfile-name need be specified.

Example

RECEIVE MIT.PAUL.SLLIB..REPORT1:BR2032:MS/B10;


2-12 47 A2 20UC Rev04

2.5.7 SEND

Function:

Initialize one or several file transfers from the DPS 7000 to QUESTAR 400 in normalmode.

Syntax:

{SEND / S} { efn [ ..subfile-name ] [ :md:dvc ] | (subfile-name [,subfile-name ... ]) } ;

where:

- efn [ ..subfile_name ] is the external file name- :md:dvc are the media and device class

DPS 7000 file-literal : when SET with LIB has been issued, only the subfile_name needbe specified.

• (subfile_name [ subfile_name ... ]) is a list of up to 10 members for a multiple filetransfer in a library specified by LIB in the SET command.

SEND, submitted at MICROFIT 7 command level, is synchronized with the setting ofMICROFIT 400 in "receive" mode by QUESTAR 400. This is done by pressing F8.

The DPS 7000 awaits reception of the receive-packet until the lapse-time specified byDELAY of the SET command is exhausted. If by this time the receive-packet has notarrived, the DPS 7000 aborts the file transfer request.

Example

SEND MIT.PAUL.SLLIB..REPORT1:BR2032:MS/B10;


47 A2 20UC Rev04 2-13

2.5.8 SET

Function:

Set file transfer parameters. Most parameters provide for future connections with othermicros.

Syntax:

Numerals in brackets on the right signify the following:

(1) applicable to MIMIC(2) applicable to MICROFIT 400

SET [ BINPREF = { & | char1 }] [ COMPPREF = { ' | char1 }] [ CSET = { PLW, NATIVE, C094, C114, C118, C113, PLE }] (1) [ DELAY = { 0 | digit4 }] (2) [ EOL = { M | alpha1 }] [ ESCAPE = { ! | char1 }] [ IMAGE = { N | Y }] (2) [ LIB = efn [ : md : dvc ] ] (1) (2) [ MAXRETRY = digit2 ] [ MICRO = char20 ] [ PACKSIZE = { 94 | digit4<=2048 }] [ SOH = { A | alpha1 }] [ TIMEOUT = { 10 | digit4 }] [ TRACE = { 0 | digit1 }] (1) (2)


2-14 47 A2 20UC Rev04

where:

BINPREF: Negotiable prefix represented by an 8-bit character. Servesas an escape for MICROFIT 7 versions which accept asingle prefixing character.Default value: "&"

COMPPREF: The prefix to the data compaction algorithm.Default value: "'"

CSET: Applicable for the conversion of national charactersbetween the Bull micro character set and the GCOS 7internal character set.Use PLW : for West European characters NATIVE : for no special conversion C094 : for Chinese characters C114 : for Arabic characters C118 : for Greek characters C113 : for Cyrillic characters PLE : for East European charactersThis conversion enables both partners to have the sameediting characters.Default value : NATIVE

DELAY: In normal mode for the QUESTAR 400, this value inseconds represents the delay for starting the file transferafter SEND has been submitted to MICROFIT 7. This delayenables the user to return to MICROFIT 400 and issue aRECEIVE.Default value: 5

EOL: Applicable to the normal mode using QUESTAR 400. Thiscontrol character delimits the "end-of-line" for the sequenceof packets during the file transfer. This control charactermust also be configured on QUESTAR 400.Default value: "M" (ctrl M)

ESCAPE: A prefix to MICROFIT 7 commands. This prefix is used onentering the command when the target application isconnected. Subsequent commands are prompted with "M:". When no target application is connected, this prefix is notrequired since all prompts appear as "M: ".Default value: "!"

IMAGE: Applicable to QUESTAR 400 as followsif Y, the file is binary to be transferred in transparent mode- if N, the file is character whose contents to be transferredis only its text.This parameter is not applicable to MIMIC, sincerequesting a binary file transfer is specified with ",I"concatenated to the Zenith PC file name.Default value: "N"

LIB: identifies the DPS 7000 library in which several transfersof subfiles are to be located. When this library is specified,the user need only specify the name of the subfile fortransfer- either in the MIMIC file transfer menu using either ZenithPC or PC-like micro- or as a parameter of SENDs and RECEIVEs usingMICROFIT 400 for the QUESTAR 400.The command "SET LIB=;" cancels the library specified.


47 A2 20UC Rev04 2-15

MAXRETRY: Maximum number of retries for a non-acknowledgedpacket. The length of timeout for an abort by MICROFIT 7is the product of maxretry and the lapse-time betweenretries.

MICRO: Defines the profile of the micro attached to the DPS 7000host for implementation by MICROFIT 7. Not required forZenith PC (PC-like micro) or QUESTAR 400.

PACKSIZE: Maximum value for the size of packets received by theDPS 7000.- For MIMIC using Zenith PC, the PC equivalent can alsobe configured through the extended configuration menu.- For MICROFIT 400 using QUESTAR 400, "packet-size"can also be configured through the MICROFIT 400 menu.Default value: 94. Maximum value: 2048.

SOH: Start-of-Header control code preceding the first negotiatedpacket. Whereas the SOH cannot be negotiated forMICROFIT 400 using QUESTAR 400, the SOH can benegotiated for MIMIC using Zenith PC through a specificnon-standard dialog which precedes the file transfer dialog.It is useful for some synchronous connections for whichhexadecimal "01" is to be used for other than SOH.Default Value: "A" (ctrl A)

TIMEOUT: Maximum time in seconds between two retries attemptedby MICROFIT 7.Default value: 10.

TRACE: MICROFIT 7 trace level. This trace is created in the DPS7000 SYS.OUT system library. When it terminates, it is putin the Output Writer Queue and set to HOLD. Thisparameter may have one of the following values:0 : no trace1, 2 : trace of warnings3 : trace of data from and/or to the terminal4->9 : internal trace of MICROFIT 7Default value is 0.


2-16 47 A2 20UC Rev04

47 A2 20UC Rev04 3-1

3. Generation and Activation

3.1 PREPARATION

MICROFIT 7 is implemented as a dedicated TDS. The following job preallocates all thefiles needed for TDS generation and execution.

EJR MMLPREP,,SYS.HSLLIB VL=(dvc,md [,sw1sz | 45 ]),, [CATENAME | MML] [,QUOTA | N ] [,BLKSZ | 1024 ])

where:

• dvc and md are the device class and the media name for the TDS files

• sw1sz is the number of cylinders of the first TDS swap file (default is 45 cylinders withDVC=MS/M452; a suitable size with DVC=MS/D500 is 20 cylinders).This value has tobe adjusted according to the device class, keeping in mind that the MML swap fileneeds about 10 Mbytes.

• Quota (as from V6 release): to specify if TDS files are subject to quota or not.

• BLKSZ (as from V6 release) is the block size of the swap file.This value must beadjusted according to the data block size defined for the media used for the swap file.To optimize the number of blocks reserved for the swap file, this parameter has to begreater than or equal to the data block size.

All the TDS files will be cataloged in the MML.CATALOG file if SYSFILE=CAT andFILESTAT=CAT.

This job preallocates the TDS system files (MML.CTLM, MML.CTLN and MML.RECOV)and the standard MML files needed for TDS preparation (MML.SLLIB, MML.LMLIB,MML.COBOL, MML.EDITION) and for TDS execution (MML.DEBUG and MML.SWAP).


3-2 47 A2 20UC Rev04

3.2 GENERATION

MICROFIT 7 must be generated with the following job:

EJR MMLGEN,,SYS.HSLLIB VL=(dvc,md [,EXEC] [, CHECKSTX = {NO | YES}])

where:

• dvc and md are the device class and the media name for the TDS files

• EXEC : if specified, MMLGEN automatically launches MMLEXEC.

• CHECKSTX : if CHECKSTX = YES is specified, the syntax of the STDS subfile ischecked but only so far as is possible without jeopardizing the current MML TDS(running or not). Only MML EDITION is modified. MMLPREP must be run (the first timeonly) because it generates the JCL required for MMLGEN.

If MMLPREP is performed with SYSFILE=CAT and FILESTAT=CAT, then the VLparameter need only be specified if EXEC is specified. Otherwise, the default is NEXECand the VL parameter can be omitted.

The MML application does not need regeneration after a "system restart clean".H_MTGEN and H_COBOL must be configured (on the customer site) for this job toexecute.

A specific subfile named MMLSTDS is loaded in the library MML.SLLIB (preallocated bythe MMLPREP job). It contains a standard TDS generation source deck. Do not modifythis deck except for the following 2 parameters:

SIMULTANEITY: Number of TDS processes (default is 2).

NUMBER OFTERMINALS:

Maximum number of terminals connectable to the TDS.This number is a maximum for the sum total of effectiveconnections to MICROFIT 7 and the connections to targetapplications through MICROFIT 7 (default is 128).

Example:

TERMINAL=10 means a maximum of 5 connections to MICROFIT 7 in automatic mode.

The working set value of 350K-bytes in the $SIZE statement of the MMLEXEC JCL mustbe increased if the number of terminals exceeds 128 (see the next section).

Note: In GCOS 7 release V6, when using IBM 3270 terminals, the TDS statementUSE TERMINAL-ADAPTER must appear in the MMLSTDS subfile to improvethe IBM screen presentation. Refer to the TDS Administrator's Guide.

This presentation is not available when using MML passthrough functionalities(for example, when connecting in automatic mode).

Generation and Activation

47 A2 20UC Rev04 3-3

3.3 STARTING MICROFIT 7

After system initialization and after starting the communications session, MICROFIT 7 islaunched by the following command:

EJR MMLEXEC,,SYS.HSLLIB VL=(dvc,md,dvcj,mdj)

where:

• dvc and md only apply for the non-cataloged TDS files For cataloged TDS files,VL=(,,dvcj,mdj).

• dvcj and mdj are the device class and media name for the before journal and arespecified to avoid the need for the operator to allocate the before journal.

TDS is automatically started when the TDS job is submitted.

For all GCOS7 Releases, the command "MML M STOP STRONG" terminates.

Some outputs are created in the SYS.OUT spool, corresponding to the traces producedby MICROFIT 7 and requested through TRACE in the SET command. Release theseoutputs since they are set in the Output Writer queue to HOLD.

JCL statements in the MMLEXEC file :

$JOB TDSMML PROJECT=SYSADMIN HOLDOUT;

MVL ,,,;

$STEP MML FILE=(MML.LMLIB DVC=&1 MD=&2) REPEAT,DUMP=DATA;SIZE 350;

ASSIGN H_BJRNL,DVC=&3,MD=&4,FILESTAT=TEMPRY,NEXT,POOL;

ASSIGN DBUGFILE,MML.DEBUG,DVC=&1,MD=&2,SHARE=DIR;SYSOUT H_PR,WHEN=IMMED;DEFINE H_CTLM,JOURNAL=BEFORE;$ENDSTEP;$ENDJOB;

The statements shown (bold) are optional for directly locating the before journal.


3-4 47 A2 20UC Rev04

47 A2 20UC Rev04 4-1

4. Microfit 7 Error Messages

A MICRO COMPUTER RECORD DOES NOT FIT IN HOST RECORD.ABORT ( 0.00.0000 ) RC = 0C87OOD3 --> TP7 , CANVT (H_TP7_ STRTSP)The user has been disconnected during the previous Logon phase .MML accepts the connection and rejects the interrupted transactionAbort ACCESS RIGHT VIOLATION ON HOST FILE . FM31CONNECTION FAILED . text as follows - ACCESS RIGHTS VIOLATION - APPLICATION SATURATED - CORRESPONDENT REJECT - DUPLICATE STATION ID - DUPLICATE USER ID - MAILBOX DEACTIVATED - MAILBOX SATURATED - MAILBOX UNKNOWN - NEGOTIATION FAILED - NODE NOT OPERATIONAL - NODE SATURATED - NODE UNKNOWN - PATH NOT AVAILABLE - PRESENTATION CONTROL REJECT - SECURITY CHECKS FAILED - TIME OUTHOST ERROR OR MEMBER SPECIFIED WITH FILE THAT ISNT A LIBRARY.FM34HOST FILE ALREADY USED . FM4HOST FILE ALREADY USED . RETRY LATER . FM32HOST FILE CONTAINS BINARY CHARACTER ALTHOUGH NO PREFIX NEGOTIATEDHOST FILE DOES NOT EXIST . CHECK YOUR DEFAULT LIB . FM21HOST FILE HAS NOT BEEN SPECIFIEDHOST FILE IS ALREADY USED . RETRY LATER . FM25HOST FILE NAME DOES NOT EXIST . FM29HOST FILE NAME SUPPLIED DOES NOT EXIST . FM18HOST FILE NAME SUPPLIED IS ILLEGAL . FM22HOST FILE STILL VALID : SCRATCH NOT PERMITTED . FM30HOST INTERNAL ERROR : text as follows - TOO LONG SIZE ON PUT . FM6 - UNABLE TO CREATE SSF HEADER . FM13 - UNABLE TO UPDATE SSF HEADER . FM14HOST INTERNAL ERROR READING FILE . FM5HOST INTERNAL ERROR ON FILE . {FM11|FM15|FM16|FM19|FM23|FM33}HOST INTERNAL ERROR ON FILE DEASSIGN . FM7HOST INTERNAL ERROR WRITING FILE . FM7HOST MEMBER IS ALREADY USED . RETRY LATER . FM28HOST MEMBER NAME DOES NOT EXIST . FM35HOST MEMBER NAME NOT SPECIFIED . FM2HOST MEMBER NAME NOT PROVIDED . FM9HOST MEMBER NAME OR DEFAULT LIB NAME IS ILLEGAL . FM21HOST RESOURCE NOT AVAILABLE . RETRY LATER . FM17HOST VOLUME NOT MOUNTEDINCORRECT RIGHT TO ACCESS HOST FILE . FM26INTERRUPT RECEIVED : ABORTING CONNECTION INITIALIZATION


4-2 47 A2 20UC Rev04

LOGON TPR : text as follows - UNABLE TO GET DEFAULT APPLICATION - WRONG RIGHT FOR THE APPLICATION . SEE YOUR SYSADMIN - YOUR DEFAULT APPLICATION IS KERM AND YOU HAVE AUTOMATIC CONNECT RIGHT . SEE YOUR SYSADMIN - MDPROF FUNCTION FAILURE : UNABLE TO USE TERMINAL ADAPTER - RDPROF FUNCTION FAILURE : UNABLE TO USE TERMINAL ADAPTERMTS : WARNING : AN IFN WAS LOST . FM27NO END OF RECORD DETECTED FOR A TEXT FILE AT CLOSE TIMEPROTOCOL ERROR DURING FILE TRANSFER : FREE DATA ENCOUNTEREDSESSION REJECT : REASON : reasonTRUNCATED RECORDS ON HOST FILE . FM1UNABLE TO SPAWN : text as follows - TOO MANY TRANSACTIONS WAITING - UNKNOWN TRANSACTION - USER UNKNOWN OR ALREADY CONNECTEDWRONG ACCESS RIGHT TO HOST FILE . {FM3|FM8|FM10}YOU ARE DISCONNECTED FROM APPLICATIONa target application is already connectedapplication name is mandatoryCOMPREF and BINPREF must be differentCTRLPREF and BINPREF must be differentCTRLPREF and COMPREF must be differenterroneous passwordillegal decimal value :illegal syntax : too many parameters for < >illegal value :illegal value for {EOL|SOH}missing command delimitermissing end-delimiter for protected stringmissing file namemissing parametermissing password for user=missing value for ESCAPEmulti-command line not authorizedno target application connectedPACKSIZE must not exceed 2048parameter specified twice :please disconnect your target applicationplease wait for target application terminationsystem error in GTUSERtoo long command :too long command or keyword :too long file name :too long member name :too long parameter :too long value :too long value for < >too long value for application name :too many file namestoo many parameters for < >unable to close trace fileunknown command :unknown command or keyword :unknown keyword :

47 A2 20UC Rev04 5-1

5. Mimic Connection

5.1 TERMINAL CONFIGURATION

If the connection is through the DCC of the DPS7, the micro must be declared "PC7800"in the CNC (V2) generation.

If the connection is through the Datanet, the micro must also be declared in the DNSgeneration through the MODEL directive as follows :

PC7800 ASY -LIKE TXT7801 -TYPE X'29' -LINE 80 -PAGE 24 -ROLL

If the terminal is connected to the Datanet via PAD, the DV command of the DNS sysgenmust include a profile-name specified by the PROFIL command with the followingparameters:

PAD -DLE 1 -ECH 0 -ENV 126 -FIL 64 -PLI 0

Note: To send lower-case characters to the DPS 7000, enter the appropriatecommand as follows:

- for the Datanet connection, enter the command: $*$LC ON .- for the DCC connection, enter the command: $*$SLC .

To return to upper case:

- for the Datanet connection, enter the command: $*$LC OFF .- for the DCC connection, enter the command: $*$SUC.


5-2 Preliminary version 2 8/9/95 47 A2 20UC Rev04

5.2 CONNECTING TO MIMIC

To connect to Mimic, carry out the following steps:

1 Start the micro under MS-DOS.

2 If the connection software is on a flexible disk, put the disk in the A drive, and enterA: to change to that drive.

If the software is on the hard disk, change to the directory where it resides.

3 Enter PC7800 at the MS-DOS prompt.

The welcome screen is displayed

4 Press Alt-S to display the following Configuration Menu.

Configuration Menu Q Quit or return to exit from this menu C Color Change B Baud Rate Change R Rear Panel Switch X Extended Configuration Menu S Save Configuration L Load a Configuration File

Figure 5-1. Configuration Menu

5 Press R for the Rear Panel Switch Menu shown below, and configure it with thefollowing values:

Rear Panel Switch Menu Q Quit or return to exit from this menu A Parity (0=odd; 1=even) 1 B Parity Enabled 1 C CR/LF in Text Mode 1 D CHAR/TEXT (0=text; 1=char) 0 E Space Suppress 0 F Message Termination (0=ETX; 1=EOT) 0 G Echoplex Mode (Tx-ret if text mode) 0 H Roll Mode 1 I Hold DTR in LOCAL Mode 0 J Display all Characters 0 K Autotab (0=delayed; 1=immediate) 1 L Transmit (0=non-blocked; 1=blocked) 0 M Cursor (0=underline; 1=oblong) 0

Figure 5-2. Rear Panel Switch Menu

Mimic Connection

47 A2 20UC Rev04 5-3

6 Press Q to leave the menu.

7 Press Alt-S to get the Configuration Menu again.

8 Press X to display the Extended Configuration Menu.

Extended Configuration Menu Q Quit or return to exit from this menu A Name of transfer program on the host FTRAN B Character length (7 or 8 bits) C Delay after each line (Option C of File Transfer) D Communication port number (0 or 1) E Packet size for sending files F Packet size for receiving files

Figure 5-3. Extended Configuration Menu

Note: The packet size for file transfers can be configured.

The name of the FTRAN file must be "FTRAN". If the MIMIC extendedconfiguration menu specifies "ftran", change it to "FTRAN".

The input and output buffer sizes must be 1024 bytes.

9 Press Q to leave the Extended Configuration Menu.

10 Press Alt-S to get the Configuration Menu again.

11 Press S to save the configuration.



5.3 CONNECTING TO DPS 7000 THROUGH DATANET

Note: In the following paragraphs, "Press [Transmit]" means "Press the key that hasbeen designated as the Transmit key" (on a micro this is usually the + key onthe numeric keypad, but on other machines it may be Enter or a function key).

1 If you have just used the Configuration Menu, press [Transmit] to start the begindialog with the Datanet.

If you have just started a session without using the Configuration Menu, press[Transmit] twice to start the dialog.

Datanet displays the prompt: "DEVICE TYPE IDENTIFIER"

2 Type: PC7800 and press [Transmit] twice.

The control sequence $*$ is not recognized. To obtain the required control sequencefrom the Datanet, press Alt-126.

The Datanet login messages then appear followed by the prompt $*$ .

Now you can log on to MML at the DPS 7000 site as follows:

3a Type: CN MML<dps7-name> and press [Transmit]. This assumes thatMML<dps7-name> is a correspondent declared in the DNS generation.

Prompts for BILLING, USERID, PROJECT and PASSWORD appear one after theother. Enter the information for each one, followed by [Transmit].

3b If MML<dps7-name> has not been declared a correspondent in the DNS generation,you can still log on using the CN command, as follows:

CN -MB MML -SC <dps7-name> -USR <userid> -PW <password> [Transmit]

When the connection is successful, you receive the message YOU ARE CONNECTEDTO MML.

Depending on the authority codes declared for the MML application in the catalog, themode of connection determines which prompt appears.

Mimic Connection

47 A2 20UC Rev04 5-5

5.4 CONNECTING TO DPS 7000 THROUGH PAD AND DATANET

To connect to the DPS 7000, carry out the following steps:

1 Press Alt-C followed by H to connect first to TRANSPAC.

TRANSPAC replies with "ERROR"

2 Enter the subscriber number and press [Enter].

TRANSPAC replies with "COM"

The Datanet displays the prompt "DEVICE TYPE IDENTIFIER" (DNS-B) or "$$4200MODEL" (DNS-C)

3 Type: PC7800 and press [Enter].

The Datanet displays its banner and the prompt "$*$"

4 Press Alt-X to connect to MML in text mode.

Recommendations

When using FORMS, the PROFIL command of the DNS SYSGEN must specify a FILparameter.

Note: FIL 64 suits the line speed of 300 bauds.

When transferring files from the DPS7 to the micro:

- set TIMEOUT to 60 seconds using the MML SET command- set the "receive packet size" to 1024 bytes using the Extended Configuration Menu.

When transferring files from the micro to the DPS7, limit the "send packet size" to 94bytes using the Extended Configuration Menu.




To transfer files, carry out the following steps:

1 Press Alt-T. You can do this at any time, even within a transaction or under a systemprocessor.

MIMIC displays the File Transfer Menu.

File Transfer Menu

ASCII Capture Transfers (character mode only) Q or return to exit this menu A - Transfer file from PC to GCOS/GCOS8 B - Transfer file from GCOS/GCOS8 to PC C - Transfer file from PC to another system D - Transfer file from another system to PC

Protocol Transfers (VIP or character mode) Q or return to exit this menu E - Transfer file from PC to GCOS/GCOS8 F - Transfer file from GCOS/GCOS8 to PC G - Transfer file from PC to another system H - Transfer file from another system to PC

Select an item --

Figure 5-4. File Transfer Menu

2 Press E or F, depending on the direction of transfer you want. This starts a dialogthat requests the file names on the micro and the DPS 7000.

While the file is being transferred, the current number of packets transferred isdisplayed. When the message TRANSFER COMPLETE appears,

3a Press Alt-T to transfer another file, or

3b Press any key to return either to MICROFIT 7 command level or to the targetapplication.

Mimic Connection

47 A2 20UC Rev04 5-7

5.5.1 Transferring Files from the PC to the DPS 7000

When you press E at the File Transfer Menu, the following screen appears.

Send files to host system

Enter name of PC file - B:TESTFILE

-Append ',I' for transferring binary file transfer-

total # packets: 1 total # retries: 0

Hit BREAK to exit

1 Type the name of the PC file, for example, B:TESTFILE, and press Enter.

The text "Enter name of host file" then overwrites the message "Append ',I' for binaryfile transfer".

2 Enter the name of the file on the DPS 7000 site, for example, RFA.SLLIBLH_MML_BREAK, and press Enter.

The file transfer then starts.

The number of packets currently transferred are displayed during the transfer.

At the end of the transfer, the message "Transfer complete" appears.

Send files to host system

Enter name of PC file - B:TESTFILE Enter name of host file - RFA.SLLIB..LH_MML_BREAK

Transferring file: B:TESTFILE


Transfer complete Hit any key to continue

If the transfer is unsuccessful, an error message is displayed, for example:

HOST FILE NAME SUPPLIED DOES NOT EXIST.FM18

followed by the message:

Aborting file transfer.



5.5.2 Transferring Files from the DPS 7000 to the PC

When you press F at the File Transfer Menu, the following screen appears.

Get files from host system

Enter name of PC file - B:TESTFILE

-Append ',I' for transferring binary file transfer-


Hit BREAK to exit

1 Enter the name of the PC file, for example, B:TESTFILE, and press Enter.

The text "Enter name of host file" then overwrites the message "Append ',I' for binaryfile transfer".

2 Enter the name of the file on the DPS 7000 site, for example,RFA.SLLIB..LH_MML_BREAK, and press Enter.

The file transfer then starts.

The number of packets currently transferred is displayed during the transfer.

At the end of the transfer, the message "TRANSFER COMPLETE" appears.

Get files from host system

Enter name of PC file - B:TESTFILE Enter name of host file - RFA.SLLIB..LH_MML_BREAK

Transferring file: B:TESTFILE


Transfer complete Hit any key to continue

If the transfer is unsuccessful, an error message is displayed, for example:

INCORRECT RIGHT TO ACCESS HOST FILE. FM26

followed by the message:

Aborting file transfer.

47 A2 20UC Rev04 6-1

6. Atlantis Connection

6.1 TERMINAL CONNECTION

The micro must be declared as one of the following emulated VIP-QUESTAR terminals:

- DKU7005- DKU7007- DKU7105- DKU7107- DKU7211

• either in the CNC (V2) network generation of the DPS 7000, if the connection is throughthe DCC of the DPS 7000

• or in the DNS system generation, if the connection is through the Datanet.

Note: If you want to send lowercase characters to the DPS 7000, enter the appropriatecommand, as follows:

- for the Datanet connection, enter the command $*$LC ON

- for the DCC connection, enter the command $*$SLC


- for the Datanet connection, enter the command $*$LC OFF

- for the DCC connection, enter the command $*$SUC


6-2 47 A2 20UC Rev04

6.2 CONNECTING TO ATLANTIS

To connect to Atlantis, carry out the following steps.

1 Start the micro with MS-DOS running.

2 If the connection software is on a flexible disk, put it into the A: drive, and enter A: tochange to that drive.


3 Enter TBV (XCOM card) or TCV (UCOM card) as appropriate.

The emulator displays its welcome screen showing the word "ATLANTIS".

4 Press C to enter the configuration phase: pressing any other key followed by Enterstarts the logon phase through the Datanet (see 6-4 "Connection to DPS 7000through Datanet").

6.3 CONFIGURATION MENU

If you press C at the welcome screen, the configuration menu for TBV or TCV appears, asshown below. This enables you to change the configuration, or set it up the first time youuse the connection.

APPLICATION LAYER -----------------

TERMINAL-ADDR(00-TO-31):[ ][ ] PRN-NU(0,1,2,D-OR-.):[ ] VFU:[ ] FILE-D:[ ] SC-OPT:[ ] PR-OPT:[ ] ALPHABET-TYPE-(0-TO-9):[ ] SCREEN-TYPE(0-TO-5):[ ] SY-OPT:[ ]

NETWORK LAYER (SEE HOST CONFIGURATION) --------------------------------------

CONTROLLER-ADDRESS (0-TO-7, + OR .) : [ ]

PHYSICAL LAYER --------------

SPEED (4-TO-7):[ ] IRQ (2-TO-7):[ ] PORT-ADDRESS:[ ] TRANSMISSION-TYPE (H-->HALF/F-->FULL):[ ]

Figure 6-1. TBV Configuration Menu

Atlantis Connection

47 A2 20UC Rev04 6-3

APPLICATION LAYER -----------------

TERMINAL-ADDRESS(00-TO-31):[ ] PRN-NU(0,1,2,D-OR-.):[ ] VFU:[ ] FILE-D:[ ] SC-OPT:[ ] PR-OPT:[ ] ALPHABET-TYPE(0-TO-9):[ ] SCREEN-TYPE(0-TO-5):[ ] SY-OPT:[ ]

PHYSICAL LAYER --------------

IRQ (2-TO-7) : [ ] PORT-ADDRESS : [ ] CLUSTER-VIP/X25-(V/X) : [ ]

Figure 6-2. Configuration Menu

6.3.1 Filling in the Configuration Parameters

When filling in the parameters on this and the next menu, you can use some of the editingkeys, as follows:

Del to delete a character

Ins to insert a blank space

Tab to move to the next field

Shift-Tab to move to the previous field

Left & Right to move the cursor in a field

Note: When you press Enter, the information is stored. If you want to change nay ofthe parameters later, you can only do this by exiting to MS-DOS, starting thesoftware again, and pressing C at the welcome screen.


6-4 47 A2 20UC Rev04

Application layer parameters

• TERMINAL ADDRESS : mandatory

Enter a value from 00 through 31 corresponding to the address of the micro in the centralconfiguration.

For TBV, you can optionally enter the address of the printer in the second field.

• PRN NU (printer function number) : mandatory

Enter one of the following:

0 : parallel printer connection1 : serial printer connection via standard output2 : serial printer connection via an extension boardD : redirection to a disk file (see FILE D below) . : no printer attached to the micro

• VFU (vertical format unit) : optional

Enter up to 3 decimal digits to specify the number of lines to be advanced by verticaltabulation. If you do not have a printer, it must be filled in with "...".

• FILE D (file name) : optional, only relevant if PRN NU = D

Enter the name of the file to receive messages which would otherwise be sent to theprinter (up to 23 alphanumeric characters)

• C OPT (screen option) : optional

Enter up to 6 digits to specify the screen options. For example, if you enter 36, options 3and 6 will be used. The screen options are:

2: blocks the keyboard following transmit until the next message has been received. Inthis case the only way to unblock the keyboard when the next message has not beenreceived is to press F2.

3: The micro is to function in extended character mode: otherwise it uses 94-charactermode.

4: forces the micro to operate in SDP mode when the emulator is started.

5: emulates SIRIS 7 or 8 functionality.

6: Screen control codes for flashing text and blanking will have no effect.

7: The micro is to operate as a VIP7700 terminal; otherwise, it operates as a VIP7760terminal. For DKU7107, the equivalent function is set by switch 17.

Atlantis Connection

47 A2 20UC Rev04 6-5

• PR OPT (printer options) : optional

Enter up to 6 digits to specify the printer options. For example, if you enter 17, options 1and 7 will be used. The printer options are:

0: page throw before each screen is recopied.1: inhibits page throw after each screen is recopied. 0 and 1 can be combined.3: automatic restart after an incident on the printer.4: enables the printer to have an address different from that of the screen.6: enables characters received from the DPS 7000 to be printed "as-is", provided that the DPS 7000 sends the message in transparent mode.7: New-line function: Line feed is sent to the printer after each Carriage Return.

• ALPHABET TYPE : mandatory

Enter a single-digit to specify the national character set. The sets are:

0 : ASCII1 : German2 : Finnish3 : Norwegian4 : Spanish5 : Portuguese6 : French7 : Swedish8 : Danish9 : English (British and American)

• SCREEN TYPE : optional

Enter one digit in the range 0 through 5 to specify the visual attributes of the type ofterminal emulated. The options are:

0 : monochrome display, white against black background1 : color display, green against black background2 : color display, 4 colors and flashing (mode A DKU7211)3 : color display, 4 colors (mode B DKU7211 with underline replaced by blue)4 : color display, 7 colors (mode 7 colors DKU7211)5 : color display, 7 colors in high intensity

• ST OPT (system option) : mandatory

You must enter a full stop (.) in this field.


6-6 47 A2 20UC Rev04

Network layer parameters

These are system-level parameters, and only apply only to TBV (see Datanet SystemGeneration)

• CONTROLLER ADDRESS : optional

Enter a single character field to specify how the micro is to function. The options are:

0 - 7 : head of the cluster. : station + : allows deferred acknowledgments to messages sent to the screen (the Datanet must be configured for this purpose)

Physical layer parameters

• SPEED (applicable only to TBV) : mandatory

Enter a single digit in the range 4 through 7 to specify the speed of transmission in bits persecond (bps). The options are:

4 : 1200 bps5 : 2400 bps6 : 4800 bps7 : 9600 bps

• IRQ (interrupt level) : mandatory

Enter a single digit in the range 2 to 7 to specify the IRQ setting on theXCOM/UCOM/SCOM board.

Note: The board is factory set to IRQ 3 and 380H.

• PORT ADDRESS : mandatory

Enter the 3-hexadecimal digit base address on the XCOM/UCOM/SCOM board thatcorresponding to the actual configuration value.

• TRANSMISSION TYPE (applicable only to TBV) : mandatory

Enter F or H to specify the transmission type.

F : full-duplex for direct connection or attached through a modem operating in full duplex mode

H : half-duplex if the connection is the VIP line procedure.

• CLUSTER VIP/X25 (applicable only to TCV) : mandatory

Enter V or X to specify the type of connection between the TCU/TCS and the DPS 7000.

V: for VIP line procedureX: for X25 protocol.

When you have filled in the parameters, press Enter. The parameters are then validated.

Atlantis Connection

47 A2 20UC Rev04 6-7

6.3.2 Programming the Function Keys

The next menu to appear is for programming the function keys. This menu is optional. Ifyou do not want to program any of the keys, just press Enter to start the logon sequenceto the DPS 7000.

PROGRAMMABLE KEYS

N A M E FC1 FC2 AFF XMIT

C-F1 [$*$CN ] [ ] [ ] [X] [ ] C-F2 [$*$BRK ] [ ] [ ] [X] [X] C-F3 [$*$DIS ] [ ] [ ] [X] [X] C-F4 [$*$DIS HOLD ] [ ] [ ] [X] [X] C-F5 [ ] [ ] [ ] [ ] [ ] C-F6 [ ] [ ] [ ] [ ] [ ] C-F7 [ ] [ ] [ ] [ ] [ ] C-F8 [ ] [ ] [ ] [ ] [ ] C-F9 [ ] [s] [ ] [ ] [X] C-F10 [ ] [ ] [ ] [ ] [ ]

Figure 6-3. Function Key Programming Screen

You can program any of the function key combinations Ctrl-F1 to Ctrl-F10:

- as a string of alphanumeric characters, by typing the text in the field under NAME- or as a function code FC1 or FC2, by typing an X in the appropriate box.

If you want the text to be displayed when you press the key combination, type X in the boxin the AFF column for that key.

If you want the text to be transmitted automatically when you press the key combination,type X in the box in the XMIT column for that key.

Note: Ctrl-F9 is preprogrammed for connection to DPS4, but you can change it if youwant to.


6-8 47 A2 20UC Rev04

6.4 CONNECTING TO DPS 7000 THROUGH DATANET

The connection through the Datanet starts when the first message of the logon sequenceappears on the screen:

$$ 4200 MODEL:

This message appears when you press Enter:

- after using the configuration option (pressing C at the welcome screen)- after pressing Enter at the welcome screen.

You can now press Enter for the default DKU model that the micro has been declared.You can also enter any of the DKU models declared in the Datanet generation to overridethe default.

The Datanet login messages appear followed by the prompt $*$.

Now you can log on to MML at the DPS 7000 site by entering:

CN MML<dps7-name>

where MML<dps7-name> is a correspondent declared in the DNS generation.

Now you can log on to the DPS 7000. Prompts for BILLING, USERID, PROJECT, andPASSWORD appear consecutively. Answer each of these as appropriate, and pressEnter after each answer.

If MML<dps7-name> has not been declared a correspondent in the DNS generation, youcan still log on using the CN command syntax given below.

If a function key has been programmed for DPS 7000 logon, you need only press Ctrl andthat key to start the complete logon sequence. Such a function key would be programmedwith the following string of characters in the field on the Function Key programmingscreen:

CN -MB MML -SC <dps7-name> -USR <userid> -PW <password>

If the connection is successful, the message YOU ARE CONNECTED TO MML appears.

Depending on the authority codes declared for the MML application in the catalog, (see"Connecting the Target Application" in section 2), the mode of connection determines theresulting prompt.

Atlantis Connection

47 A2 20UC Rev04 6-9


Once the connection to MML is established, you can transfer files between the DPS 7000and the micro in either direction. To do this, you must first call up the File TransferInitialization Menu, by pressing Alt-M.

6.5.1 Filling in the File Transfer Initialization Form

FILE-TRANSFER-INITIALIZATION

FILE-PARAMETER-NAME:[ ]

UPDATING-FILE-PARAMETER-NAME:[ ]

NEW-FILE-PARAMETER-NAME:[ ]

Figure 6-4. File Transfer Initialization Form

On this screen, you must only fill in one field. The first time you use this screen, you willneed to fill in the first field, NEW-FILE-PARAMETER-NAME. This is the name of the file inwhich the actual parameters for file transfer will be saved (see 6.5.2, "Filling in the FileTransfer Parameters").

In subsequent sessions you only need to enter the name in the FILE-PARAMETER-NAME field to carry out the same transfer. This means that you do not have to fill in thefile transfer parameters every time you transfer the same file in the same direction.

You can also change the existing parameters in a subsequent session, by entering the filename in the UPDATING-FILE-PARAMETER-NAME field. The changed parameters arethen used for the transfer, and saved for later use.

Using the NEW-FILE-PARAMETER-NAME field, you can make several different files,each containing its own file transfer parameters. Then, each time you want to carry out atransfer, all you need do is enter the name of the parameter file in the FILE-PARAMETER-NAME field. For example, if you always have to transfer a particular filefrom the DPS 7000 to the micro on Monday mornings, and transfer it back again on Fridaymornings, you could make two parameter files, called MONDAY and FRIDAY. On Mondayyou just enter MONDAY in the FILE-PARAMETER-NAME field, and the file is transferredautomatically. On Friday you enter FRIDAY, and the file is transferred back again.


6-10 47 A2 20UC Rev04

When you have filled in a field in the form and you press Enter, the value in the field ischecked. If it is wrong in any way, the form remains displayed with the cursor pointing atthe field concerned, and the following message appears:

ERROR PARAMETERS --> REENTER

Correct the field in error and press Enter again.

File Transfer Initialization Parameters

• FILE-PARAMETER-NAME

Enter the name of an existing parameter file (up to 48 alphanumeric characters). PressEnter to start file transfer. The Transfer in Progress screen appears (see below).

• UPDATING-FILE-PARAMETER-NAME

Enter the name of an existing parameter file (up to 48 alphanumeric characters). PressEnter. The File Transfer Parameters Form appears (see below). You can then change theparameters you want, and press Enter to start the transfer.

• NEW-FILE-PARAMETER-NAME

Enter up to 48 alphanumeric characters to specify the name of the parameter file to becreated. Press Enter. The File Transfer Parameters Form appears, and you can fill in theparameters (see below). Pressing Enter on that screen to start the transfer.

Atlantis Connection

47 A2 20UC Rev04 6-11

6.5.2 Filling in the File Transfer Parameters

You must enter something in every field on this form. There are no default values.

FTMIC-FILE-TRANSFER

TRANSFER-DIRECTION (I-OR-O):[ ](O-TERMINAL-->HOST,I-HOST--->TERMINAL)

TERM-FILE-NAME :[ ]

HOST-FILE-NAME :[ ]

BINARY-OPTION (Y-N) :[ ] COMPACT-OPTION (Y-N) :[ ]

MODE-(N-OR-E) :[ ] CHECKSUM-TYPE (1,2,3) :[ ]

PACKET-LENGTH-MODE-E:[ ] PACKET-LENGTH-MODE-N :[ ]

MICROFIT-HOST-NAME :[ ]

S-SOH :[ ] R-SOH :[ ]

Figure 6-5. File Transfer Parameters Form

• TRANSFER-DIRECTION

Enter a single alpha character to specify the direction of the file transfer:

O : from the micro to the DPS 7000I : from the DPS 7000 to the micro

• TERM-FILE-NAME

Enter up to 56 alphanumeric characters to specify the name of the file on the micro. Ifnecessary, enter the disk letter, directory, and subdirectory path, for exampleC:\ATL\BILL\FILE

• HOST-FILE-NAME

Enter up to 56 alphanumeric characters to specify the name of the file on the DPS 7000. Ifnecessary, enter the library name followed by two full stops and then the file name, foeexample SD3.SL..PAYROLL


6-12 47 A2 20UC Rev04

• BINARY-OPTION

Enter a single alpha character to specify if the transfer is in binary, as follows:

O : if any character whose ASCII value greater than decimal 126 (7E hexadecimal) is tobe transferred or if the DPS 7000 file is in a binary (BIN) library

N : if the ASCII values of all characters to be transferred do not exceed decimal 126(7E hexadecimal) or if the DPS 7000 file is in a source (SL) library.

• COMPACT-OPTION

Enter a single alpha character specifying how the transfer is to occur :

O : by first compacting data for transmission, then decompacting at reception.

N : by transmitting data "as-is" on transmission as at reception.

• MODE

Enter a single alpha character specifying if the packet size is extended (E) or normal (N).Although the mode does not matter to the DPS 7000, E is recommended.

• CHECKSUM-TYPE

Enter a single numeric character specifying the security level to be used on the number ofcharacters used for the checksum (1, 2 or 3). 1 is recommended.

• PACKET-LENGTH-MODE- E

Enter up to 4 numeric digits to specify the maximum number of characters in the packet inEXTENDED mode. 1024 (maximum) characters is recommended.

• PACKET-LENGTH-MODE-N

Enter up to 2 digits to specify the maximum number of characters in the packet inNORMAL mode. The recommended packet size is 94 characters (bytes).

• MICROFIT-HOST-NAME

Here you must enter the keyword FTRAN MICROSYS

• S-SOH

Here you must enter an underscore ( _ ) to specify the alpha character used as the "send"SOH (Start-Of-Header).

• R-SOH

Here you must enter an underscore ( _ ) to specify the alpha character used as the"receive" SOH (Start-Of-Header).

Atlantis Connection

47 A2 20UC Rev04 6-13

Once you have filled in all the parameters, press Enter. The parameters are checked.

If any parameter is not within the range of accepted values, the menu remains on displaywith the cursor pointing at the parameter in error, and the following message is displayed:

ERROR PARAMETERS --> REENTER

Correct the parameter concerned and press Enter again.

When all parameters are correct, the Transfer in Progress screen appears.

* * * * F T M I C * * * *

F I L E T R A N S F E R

TRANSFER IN PROGRESS :

Figure 6-6. Transfer in Progress Screen

If the transfer is successfully started, this screen shows the number of packets as they arebeing transferred. The characters which follow the number of packets are not significant.

When the transfer terminates successfully, the following message appears:

TRANSFER TERMINATED SUCCESSFULLY <Alt X>

If the transfer is not successfully started, no packets are transferred and the standarderror message appears:

ERROR DURING TRANSFER <Alt X>

A further diagnostic message then appears, for example:

HOST FILE NAME DOES NOT EXIST.FM18

Press Alt-X to interrupt the process. Then press Alt-M to get the File Transfer Initializationscreen. Enter the parameter file name in the UPDATING-FILE-PARAMETER-NAME field,and correct the error on the File Transfer Parameters Form. Then press Enter to try again.

You can also press Alt-X to interrupt the transfer while it is in progress.


6-14 47 A2 20UC Rev04

6.6 DISCONNECTING FROM ATLANTIS

When you have finished transferring all the files you want, enter:

bye;

at the M: prompt. The $*$ prompt is displayed again.

Press Shift-F10 to return to MS-DOS.

47 A2 20UC Rev04 7-1

7. Questar 400 Connection

The connection with QUESTAR 400 is through a synchronous link using the followingsoftware :

• CTOS III 1.2,

• MSTE7107. Depending on the link to the host , you need several software components.Refer to Table 7-1 below and consult your Bull sales representative.

Table 7-1. MSTE 7107 Software Components

Connectionvia:

MSTE7107

VIPDriver

X25Driver

LANDriver

TGT TM STAR-ISO

VIP link X XTGT X25 link X X X

TM/X25(with STARISO)

X X X X

TM/LAN(with STARISO)

X X X X

If the Bull Questar 400 is connected through the Datanet, it must be declared "DKU7007"in the MODEL directive of the DNS generation.


7-2 47 A2 20UC Rev04

7.1 CONNECTION TO MICROFIT 400

Steps 1. and 2. are carried out at Bull Questar 400 command level. Refer to the followingmanuals:

• MSTE 7107 User Guide 82 A2 66QS,• MSTE 7107 Reference Manual 82 A2 63DL.

Steps 4. and 5. are carried out at Datanet command level.

To connect to Microfit 400, carry out the following steps:

1. Configure the Bull Questar 400. Refer to Section 2. of the MSTE User Guide.MICROFIT 400 is the implementation of the Kermit file transfer utility on the BullQuestar 400, so you will need to configure the MSTE Kermit Transfer Conf.

2. Run the MSTE 7107 emulator: refer to Section 3. of the MSTE User Guide.

A sequence of commands has to be run, depending on the connection to the host.The last command of the sequence is MSTE 7107. Fill in the necessary parameters.Press <ENTER>. In VIP or TGT mode, you are now connected to a Datanet.

4. To connect to MICROFIT 400 on the DPS 7000, type either:

CN MML<dps7-name> and press Enter.

This assumes that MML<dps7-name> is a correspondent declared in the DNSgeneration. Prompts for BILLING, USERID, PROJECT and PASSWORD appear oneafter the other. Enter the information for each one, followed by Enter.

CN -SC <dps7-name> -MB MML -USR <userid> -PW <password> and pressEnter.

This assumes that MML<dps7-name> has not been declared a correspondent in theDNS generation.

The M: prompt appears.

5. To transfer files from the DPS 7000 to the QUESTAR 400, refer to Section 7.2.1, totransfer files from the QUESTAR 400 to the DPS 7000, refer to Section 7.2.2.

Questar 400 Connection

47 A2 20UC Rev04 7-3

Note: To send lower-case characters to the DPS 7000, enter the appropriatecommand as follows:

- for the Datanet connection, enter the command $*$LC ON- for the DCC connection, enter the command $*$SLC .


- for the Datanet connection, enter the command $*$LC OFF- for the DCC connection, enter the command $*$SUC


7-4 47 A2 20UC Rev04

7.2 FILE TRANSFER

7.2.1 Transferring Files from the DPS 7000 to the QUESTAR 400

The procedure to transfer a single text file is described first. Information is given later totransfer binary files, or several files.

To transfer a single text file from the DPS 7000 to the QUESTAR 400, carry out thefollowing steps:

1. enter: SEND <dps7-file-name> where <dps7-file-name> can be either an efn, or <library>..<subfile-name>

The message SENDING ... appears on the screen.

2. To display the MICROFIT 400 file transfer menu (Figure 7-1), press:

- <CODE> + <F6> on a KBU 7410 keyboard,- <CODE> + <F7> on a KBU 7450 keyboard,- <CTRL> + <F7> on a KBU 7470 and PC-type keyboard.

4. Refer to Section 7.2.3 to enter the required parameters in the menu and press EXEC(TRANS).

The status of the file transfer is displayed under the asterisk line of the menu.

To transfer a binary file , enter the following two commands:

SET IMAGE=Y;SEND <dps7-file-name>;

When the message SENDING ... appears on the screen, proceed as before.

If the transfer is for multiple library subfiles , enter the following two commands:

SET LIB=<dps7-library>; SEND <member-list>;

When the message SENDING ... appears on the screen, proceed as before.


47 A2 20UC Rev04 7-5

7.2.2 Transferring Files from the QUESTAR 400 to the DPS 7000

To transfer a single text file from the Bull Questar 400 to the DPS 7000, carry out thefollowing steps:

1 Enter RECEIVE;

2 Press EXEC (TRANS).

The message RECEIVING... appears on the screen.

2. To display the MICROFIT 400 file transfer menu (Figure 7-1), press:

- <CODE> + <F6> on a KBU 7410 keyboard,- <CODE> + <F7> on a KBU 7450 keyboard,- <CTRL> + <F7> on a KBU 7470 and PC-type keyboard.

4. Refer to Section 7.2.3 to enter the required parameters in the menu and press EXEC(TRANS).

The status of the file transfer is displayed under the asterisk line of the menu.

When the file transfer is successfully completed, the message TRANSFER COMPLETEDCORRECTLY appears. You can then transfer another file or return to MSTE.

To return to MSTE, press <CODE> + <F6>, <CODE> + <F7> or <CTRL> + <F7>depending on your keyboard.


7-6 47 A2 20UC Rev04

7.2.3 MICROFIT 400 Parameters

+---------------------------------------------------------------------+! MICROFIT 400 FILE TRANSFER MENU !! !! LOCAL FILE NAME : !! !! REMOTE FILE NAME : !! !! TRANSFER DIRECTION (0 OR 1 / 1 = HOST -> Q400) : !! !! TRANSFER MODE (1 : BINARY, 0 : TEXT) : !! !! - ENTER PARAMETERS AND PRESS <EXEC> (<TRANS>) to validate !! - RETURN TO EMULATION / PRESS <CODE> + <F6> !! - MODIFY CONFIGURATION / PRESS <NEXT P> !! !!*********************************************************************!! ! -+! File to be received : ! !! <file-name> ! !! n packet(s) received ! ! (1)! ! !! file transfer status ! !! Transfer completed normally ! !! ! -++---------------------------------------------------------------------+

Figure 7-1. MICROFIT 400 File Transfer Menu

Local File Name

Name of the file on the Bull Questar 400. It must obey the Bull Questar 400 syntax rules.

When receiving a file from the DPS7000 (after a SEND command), the receiving file neednot exist. It will be created in the default current working directory if a directory-name isnot specified, or in the specified directory.The name of the receiving file will be in the format [<attribute>]<dps7-file-name>.

When transmitting a file to the DPS7000 (after a RECEIVE command), this file must exist.

Remote File Name

Name of the file on the DPS7000. It must obey the DPS7000 syntax rules.

When receiving a file from the Bull Questar 400 (after a RECEIVE command), this fileneed not exist.

When transmitting a file to the Bull Questar 400 (after a SEND command), this file mustexist.


47 A2 20UC Rev04 7-7

If the DPS 7000 receiving file is specified in both the RECEIVE command and "RemoteFile Name" of the MICROFIT 400 menu, the name specified in RECEIVE overrides thatgiven for "Remote File Name". The name of the DPS 7000 receiving file is determined asfollows :

Name of DPS 7000 receiving filespecified in

Resulting Name of DPS 7000receiving file

RECEIVE Remote File Name

Yes No Name specified for RECEIVEYes Yes Name specified for RECEIVENo Yes Name specified for "Remote File Name"No No Name specified for "Local File Name"

Transfer Direction

Enter 1 after a SEND command, or 0 after a RECEIVE command.

Transfer Mode

Enter 0 to transfer a text file, or 1 to transfer a binary file.

(1) Status of File Transfer

When the file is being transmitted, this information is displayed. In this example, a file istransmitted from the DPS7000 (SEND command):

- <file-name> is the name of the file to be received by the Bull Questar 400,- n is the number of packets received,- the last message indicates that the tranfer has completed normally.

When the file is transmitted to the DPS7000 (RECEIVE command), this information isslightly different:

File to be transmitted<file-name>

n packet(s) transmitted

Status of file transferTransfer completed correctly

If the transfer is unsuccessful, a message is displayed giving the reason for the failure, forexample:

• on reception, RECEIVED A LOCAL PACKET WHEN IN STATE AC3

• on sending, IMPOSSIBLE TO OPEN FILE TO BE SENT.


7-8 47 A2 20UC Rev04

47 A2 20UC Rev04 8-1

8. Microfit 7 Integration

8.1 INTRODUCTION

MICROFIT 7 Integration allows you to integrate the MICROFIT 7 application in a userTDS. This extension of the MML gives the possibility for users to execute a file transfer oruse the main MICROFIT 7 functions in their own TDS.

This integration means that some modifications must be made in the user TDS, andcertain programming rules must be followed, as explained later in this section.

8.2 TDS PREPARATION

For the preparation of the generation, see the JCL MMLPREP (invoking MTPREP) in theSYS.HSLLIB library for an example.

8.3 IMPLEMENTATION IN TDSGEN

The member MMLSTDS must be merged with the member STDS of the user application.

Note: In GCOS 7 release V6, when using IBM 3270 terminals, the TDS statementUSE TERMINAL-ADAPTER must appear in the MMLSTDS subfile to improvethe IBM screen presentation. Refer to the TDS Administrator's Guide.

This presentation is not available when using MML passthrough functionalities(for example, when connecting in automatic mode).


8-2 47 A2 20UC Rev04

8.3.1 MICROFIT transaction

Add two separate MESSAGE statements to define MICROFIT in the TRANSACTIONSECTION of the TDS user, as follows:

• The "MICROFIT" MESSAGE statement, to start the MICROFIT transaction when theREADY message appears, and to spawn the MICROFIT transaction.

• The "TRY" MESSAGE statement, to connect a user in automatic or manual mode.

• The syntax of these statements is as follows:

TRANSACTION SECTION.

MESSAGE "MICROFIT" ASSIGN TO H_MML_TPR0 IMPLICIT COMMITMENT AUTHORITY-CODES ARE 0,1,...,30,31 TRANSACTION-STORAGE MEMORY SIZE IS 19408. 01 TRANSACTION-STORAGE. 02 STORAGE OCCURS 19. 03 FILLER PIC X(1024).*END

MESSAGE "TRY" ASSIGN TO H_MML_TPR0 IMPLICIT COMMITMENT AUTHORITY-CODES ARE 0,1,...,30,31 TRANSACTION-STORAGE MEMORY SIZE IS 19408. 01 TRANSACTION-STORAGE. 02 STORAGE OCCURS 19. 03 FILLER PIC X(1024).*END

The size of the transaction-storage will be increased by the size of the private-storage ifthe user application has defined a private-storage.

Microfit 7 Integration

47 A2 20UC Rev04 8-3

8.3.2 Special transactions

The MICROFIT application uses four special transactions which must be inserted in theTRANSACTION SECTION of TDSGEN:

- STARTUP- LOGON- RESTART- DISCNCT

For each special transaction, the user TPR will be assigned at the MESSAGE statement ifone exists. Otherwise it will be the MICROFIT TPR.

The special transactions must be defined in TDSGEN according to the following rules:

- the transaction is defined with implicit commitment- authority codes are from 01 to 31- the size of transaction-storage is the size of the user special transaction, or the

MICROFIT special transaction, whichever is the larger.

It is possible to define some other special transactions in the TRANSACTION SECTION.

The syntax of the four special MICROFIT transactions is as follows:

STARTUP

TRANSACTION SECTION. MESSAGE "STARTUP" ASSIGN TO {tpruser-startup | STARTUP} IMPLICIT COMMITMENT AUTHORITY-CODES ARE 0,1,...,30,31 TRANSACTION-STORAGE MEMORY SIZE IS 19408. 01 TRANSACTION-STORAGE. 02 STORAGE OCCURS 19. 03 FILLER PIC X(1024).*END

LOGON

TRANSACTION SECTION. MESSAGE "LOGON" ASSIGN TO {tpruser-logon | LOGON} IMPLICIT COMMITMENT AUTHORITY-CODES ARE 0,1,...,30,31 TRANSACTION-STORAGE MEMORY SIZE IS 19408. 01 TRANSACTION-STORAGE. 02 STORAGE OCCURS 19. 03 FILLER PIC X(1024).*END


8-4 47 A2 20UC Rev04

RESTART

TRANSACTION SECTION. MESSAGE "RESTART" ASSIGN TO tpruser-restart IMPLICIT COMMITMENT AUTHORITY-CODES ARE 0,1,...,30,31 TRANSACTION-STORAGE MEMORY SIZE IS 19408. 01 TRANSACTION-STORAGE. 02 STORAGE OCCURS 19. 03 FILLER PIC X(1024).*END

Note: In the case of RESTART, the user must have a RESTART TPR, which will testthe name of the interrupted transaction (see the example in section 8.6).

DISCNCT

TRANSACTION SECTION. MESSAGE "DISCNCT" ASSIGN TO tpruser-discnct IMPLICIT COMMITMENT AUTHORITY-CODES ARE 0,1,...,30,31 TRANSACTION-STORAGE MEMORY SIZE IS 19408. 01 TRANSACTION-STORAGE. 02 STORAGE OCCURS 19. 03 FILLER PIC X(1024).*END

Note: In the case of DISCNCT, the user must have a DISCNCT TPR, which will testthe name of the interrupted transaction (see the example in section 8.6).

BREAK

If the TDS already has a BREAK TPR, this BREAK TPR will continue to be executed if it isdeclared in TRANSACTION SECTION by a clause:

MESSAGE "BREAK" ASSIGN TO tpruser_break

where the name tpruser_break is different from BREAK.

TRANSACTION SECTION. MESSAGE "BREAK" ASSIGN TO tpruser-break IMPLICIT COMMITMENT AUTHORITY-CODES ARE 0,1,...,30,31 TRANSACTION-STORAGE MEMORY SIZE IS 19408. 01 TRANSACTION-STORAGE. 02 STORAGE OCCURS 19. 03 FILLER PIC X(1024).*END

Otherwise, if no BREAK TPR exists, MML BREAK TPR will be automatically executed.This MML BREAK TPR continues execution of the transaction from where it wasinterrupted. This may lead to a change of visibility, particularly if before MMl integration theimplicit TDS BREAK TPR was used to activate the passive terminals or to obtain theREADY prompt. In such a case you will have to write your own BREAK TPR, including allthe necessary processing to restore the old visibility, for instance activating passiveterminals, loading "CANCELTX" in next_tpr, or doing a call "CANCELCTX".


47 A2 20UC Rev04 8-5

8.3.3 Shared storage

The MICROFIT application needs two shared-storage areas. These must be defined inthe INPUT-OUTPUT section of the user TDSGEN. The syntax is as follows:

INPUT-OUTPUT SECTION.

SHARED-STORAGE AUTOMATETABLE. 02 ELBAT PIC X(300).*END SHARED-STORAGE IFNCHARTABLE. 02 GARBAGE PIC X(10).*END

8.3.4 TDS Section Clauses

Some Clauses must be added to the TDS SECTION of TDSGEN for MICROFIT 7. If oneof these Clauses is already defined in the user TDS, then the values must be either thosedefined for the user TDS or those defined for the MICROFIT application, whichever arethe larger. The syntax is as follows:

TDS SECTION.

PROGRAM-ID . tds_name. NUMBER OF TERMINALS IS 128. SIMULTANEITY IS 2. RESERVE 1 AREAS. NUMBER OF TPR SHARABLE MODULES IS 1. MESSAGE-LENGTH IS 6144 MAXIMUM. TPR-TIME-LIMIT IS 15000 MSEC. USE H_MML_TRNAME. MAXIMUM IDLE-TIME IS 900. SERVICE-MESSAGE IMMEDIATE DELIVERY.


8-6 47 A2 20UC Rev04

8.4 GENERATION AND ACTIVATION

8.4.1 Generation

The TDS must be generated using the TDSUGEN JCL in the library SYS.HSLLIB:

EJR TDSUGEN LIB=SYS.HSLLIB VL=(dvc,md,tdsname)

where:

• dvc and md are the device class and media name for the TDS files. If the tDS files arecatalogued, these parameters may be omitted.

• tdsname is mandatory, and is identical to the PROGRAM-ID name specified in the TDSSECTION of TDSGEN.

The JCL statements look like this:

$JOB TDSUGEN;MVL ,,,TDS=&3;INVOKE MTGEN SYS.HSLLIB VALUES=(&TDS,&1,&2,LM=&TDS.LMLIB, INV1=Y,SUBF1=TDSUMODLINKTDS);$ENDJOB;

8.4.2 Activation

The TDS can be started by the following command:

EJR TDSUEXEC LIB=SYS.HSLLIB VL=(dvc,md,dvcj,mdj,tdsname);

where:

• dvc and md only apply for non-catalogued TDS files. For catalogued TDS files,VL=(,,dvcj,mdj).

• dvcj and mdj are the device class and media name for the before journal and arespecified to avoid the need for the operator to allocate the before journal.

• tdsname is mandatory, and is identical to the PROGRAM-ID name specified in the TDSSECTION of TDSGEN.


47 A2 20UC Rev04 8-7

The JCL statements look like this:

$JOB TDSUEXEC PROJECT=SYSADMIN HOLDOUT;MVL ,,,,,TDS=&5;JOBLIB SM, &TDS.SMLIB;$STEP &5 FILE=(&TDS.LMLIB DVC=&1 MD=&2) REPEAT,DUMP=DATA;SIZE=350;ASSIGN H_BJRNL,DVC=&3,MD=&4,FILESTAT=TEMPRY,NEXT,POOL;ASSIGN DBUGFILE,&TDS.DEBUG,DVC=&1,MD=&2,SHARE=DIR;SYSOUT H_PR,WHEN=IMMED;DEFINE H_CTLM,JOURNAL=BEFORE;$ENDSTEP;$ENDJOB;

Some sysouts are created in the SYS.OUT spool. They correspond to the tracesproduced by MICROFIT 7 and requested through TRACE of the SET command. Releasethese outputs since they are set in the Output Writer queue to HOLD.

Depending on the user application, some optional statements can be added, such as:

• the ASSIGN statements specify all files to be used during the TDS session

• the ASSIGN h_FORM statement must be specified if the FORM description is used.

8.5 CONNECTION MODES

The SITE.CATALOG must be updated because the MICROFIT 7 application uses the29th and 32nd TDS authority codes.

Note: These codes are reserved for MICROFIT: The user may not use them.

The connection mode is defined by the TDS authority codes (see also "Connecting to thetarget application" in Section 2):

TDS/7FFF0000 : spawns MICROFIT 7 in manual modeprompt on connection: M:

TDS/7FFF0001 : spawns MICROFIT 7 in automatic mode (in this case IOF isthe default application)prompt on connection: S:

TDS/7FFF0008 : no spawning and no administrator message on connectionprompt on connection: READY


8-8 47 A2 20UC Rev04

8.6 PROGRAMMING RULES

Some programming rules must be followed for special transactions, as described below.One general rule is as follows:

If the user TDS uses the same special transactions as MICROFIT (STARTUP, LOGON,DISCNCT, and RESTART), TDS must first execute the user TPR, and then theMICROFIT TPR.

8.6.1 STARTUP Transaction

The STARTUP transaction is activated when the TDS session has started or restartedsuccessfully.

The user STARTUP TPR calls the MICROFIT STARTUP TPR at the end by NEXT-TPR.

If no user STARTUP TPR exists, the MICROFIT STARTUP TPR will be called by TDSdirectly (by the MESSAGE STARTUP defined in TDSGEN).

Syntax

MOVE "STARTUP" TO NEXT-TPR

8.6.2 LOGON Transaction

The LOGON transaction is activated each time a correspondent connects to TDS.

The user LOGON TPR may call other TPRs in order to:

- reject the connection (transaction "BYE")- accept the connection and reject the interrupted transaction (TPR "CANCEL TX")- call the MICROFIT LOGON TPR by NEXT-TPR.

If no user LOGON TPR exists, the MICROFIT LOGON TPR will be called directly by TDS(by the MESSAGE LOGON defined in TDSGEN).


47 A2 20UC Rev04 8-9

8.6.3 DISCNCT Transaction

The DISCNCT transaction is activated when a correspondent is accidentallydisconnected.

The user DISCNCT TPR tests which transaction has been interrupted. Depending on theresult, it will either chain MICROFIT DISCNCT TPR with DISCONNECT in NEXT-TPR, orwill continue running the user DISCNCT TPR. If no user DISCNCT TPR exists, the usermust write one to carry out this test (see the example below).

Example

*************************IDENTIFICATION DIVISION.************************* PROGRAM-ID. DISCNCTS.* DISCNCT TPR*************************ENVIRONMENT DIVISION.*************************CONFIGURATION SECTION************************* SOURCE-COMPUTER. LEVEL-64. OBJECT-COMPUTER. LEVEL-64.*************************DATA DIVISION************************* WORKING-STORAGE SECTION.************************** 01 DATA-NAME-1 PIC X.* LINKAGE SECTION.************************** COPY TDS-STORAGE.* COPY CONSTANT-STORAGE.* COPY TRANSACTION-STORAGE.* PROCEDURE DIVISION USING TDS-STORAGE CONSTANT-STORAGE TRANSACTION-STORAGE.* P000. CALL "H_MML_TRNAME" USING PRIOR-TPR DATA-NAME-1. IF DATA-NAME-1 = "M" MOVE "DISCONNECT" TO NEXT-TPR GO FIN. MOVE SPACES TO NEXT-TPR.FIN. EXIT PROGRAM.

Note: The H_MML_TRNAME procedure is defined as USE procedure in TDSGEN.


8-10 47 A2 20UC Rev04

8.6.4 RESTART Transaction

The RESTART transaction is activated when a user logs on to TDS and a context alreadyexists for that user.

The user RESTART TPR tests which transaction has been interrupted. Depending on theresult, it will either chain CANCELTX TPR (MICROFIT transaction), or will resume theinterrupted (user) transaction. If no user RESTART TPR exists, the user must write one tocarry out this test (see the example below).

Example

*************************IDENTIFICATION DIVISION.************************* PROGRAM-ID. RESTARTS.* RESTART TPR*************************ENVIRONMENT DIVISION.**************************CONFIGURATION SECTION************************* SOURCE-COMPUTER. LEVEL-64. OBJECT-COMPUTER. LEVEL-64.*************************DATA DIVISION************************* WORKING-STORAGE SECTION.************************** 01 DATA-NAME-1 PIC X.* LINKAGE SECTION.************************** COPY TDS-STORAGE.* COPY CONSTANT-STORAGE.* COPY TRANSACTION-STORAGE.* PROCEDURE DIVISION USING TDS-STORAGE CONSTANT-STORAGE TRANSACTION-STORAGE.* P000. CALL "H_MML_TRNAME" USING PRIOR-TPR DATA-NAME-1. IF DATA-NAME-1 = "M" MOVE "CANCELTX" TO NEXT-TPR GO FIN. MOVE SPACES TO NEXT-TPR.FIN. EXIT PROGRAM.

Note: The H_MML_TRNAME procedure is defined as USE procedure in TDSGEN.


47 A2 20UC Rev04 8-11

8.7 CALL "H_MML_TRNAME" PROCEDURE

The H_MML_TRNAME procedure returns the name of the last transaction that has beendisconnected abnormally. It is defined in TDSGEN by the clause "USE procedure".H_MML_TRNAME is linked with TDSGEN. The compile unit is in the library SYS.HCULIB.

The COBOL interface is:

CALL "H_MML_TRNAME" USING prior-tpr data-name-1.

where:

- prior-tpr is an alphanumeric field of up to 12 characters contained in the TDS-STORAGE. It is used to return the name of the transaction concerned.

- data-name-1 is used to return one of the following values: "M" : MICROFIT transaction "O" : OTHER transaction.

8.8 SPAWNING OF MICROFIT TRANSACTION

The MICROFIT transaction can be spawned on the same terminal or on other terminals.The syntax is as follows;

CALL "SPAWN" USING data-name-1, data-name-2 data-name-3, [data-name-4].

where:

• data-name-1 is a userid of up to 8 alphanumerics, identifying the correspondent towhich the transaction is spawned. It is an input parameter.

• data-name-2 is an alphanumeric field of up to 46 characters. It must contain themessage identifying the MICROFIT transaction and its parameters, as follows:

01 DATA-NAME-2. 02 TRANSACTION-NAME pic x(8). 02 FILLER pic x. 02 CONNECT-MODE pic x. 02 FILLER pic x. 02 MLBX-NAME pic x(4). 02 FILLER pic x(31).


8-12 47 A2 20UC Rev04

Where:

- TRANSACTION-NAME is an alphanumeric field, initialized with the value"MICROFIT"

- CONNECT-MODE can be initialized with "A" for automatic connection, or "M" formanual connection.

- MLBX-NAME is the name of the target application, or spaces.

• data-name-3 is a 1-character numeric field. It is an output field that contains the statusafter the execution of th call, as follows:

0 = Successful completion1 = Number of spawns by commitment unit has exceeded the limit.2 = Unknown transaction (possible conflict of authority codes)3 = Unknown correspondent, or connection denied by correspondent or lower layers4 = No more space in TDS system file CLTM5 = Wrong priority

• data-name-4 is an input parameter. It is a single digit specifying the priority of thespawn (1 = Express, 2 = High, 3 = Medium, 4 = Low).

8.9 RESTRICTIONS

The following restrictions apply to integrated MICROFIT applications.

The following transaction names are reserved:

- STARTUP- LOGON- DISCONNECT

User TPRs can not be prefixed by "H_MML".

Authority codes 29 and 32 are reserved for MICROFIT use, and can not be used by theuser.

The DISCNCT, RESTART, LOGON, and STARTUP transactions must be defined withthe "IMPLICIT COMMITMENT" clause.

47 A2 20UC Rev04 9-1

9. Atlantis Connection from PC-327xTerminals

9.1 TERMINAL CONNECTION

The PC-like micro must be able to emulate a 327x SNA terminal. Note that PC microsemulating 327x BSC terminals, such as those directly connected to a DATANET througha BSC link, do not allow the file transfer facility.

The 327x SNA terminals must be accessible to a DSA network, through a SNA/DSA OSFGateway including the OSF Reverse Gateway (3270 RGW) facility. Terminals may eitherbe connected directly to the Reverse Gateway Datanet, or attached to a SNA networkconnected to a Reverse Gateway Datanet.

On the SNA side, the LOGMODE entry (VTAM) or the BIND image (TCAM) used for thePC327x must have the "query bit" on.

The PC-327x must support the extended data stream since the PC-327x and the hostcommunicate by means of structured fields.

VM passthrough on VM/SP IBM system cannot be used. This program does not supportthe extended streams used into the file transfer.

Note: To send lower-case characters to the DPS 7000, enter the command $*$LCON. To return to upper case, enter the command $*$LC OFF .


9-2 47 A2 20UC Rev04

9.2 CONNECTING TO ATLANTIS

To connect to Atlantis, carry out the following steps:

1 Start the micro under MS-DOS

2 If the connection software is on a flexible disk, put the TXI disk or the TDI disk indrive A:, and enter A: to change to that drive.


3 Enter TDI or TXI as appropriate at the MS-DOS prompt

The emulator displays the Atlantis welcome screen.

4 Press C to enter the configuration phase, or any other key (except [Transmit]) to startthe logon phase (see below).

Atlantis Connection from PC-327x Terminals

47 A2 20UC Rev04 9-3

9.3 CONFIGURATION MENU

If you press C at the welcome screen, the configuration menu for TDI or TXI appears, asshown below.

NIVEAU APPLICATION ------------------

ADRESSES STATION (02-33) ECRAN : [02] IMPRIMANTE : [ ] SORTIE IP(0,1,2,D,N):[N] TYPE IP(D,S):[ ] MODE IP(E,L,B,S):[ ] TYPE ALPHA (0,9) : [6] TYPE EC (0-4) : [0] FICH IMPRESSIONS : [ . ] FICH COPIES ECRAN : [ . ]

ID BLOCK : [017] ID NUMBER : [00000]

NIVEAU LIAISON (SDLC) --------------

ADRESSE CONTROLEUR : [01] FENETRE TRAME (1-7) : [/] TIME OUT CONNEXION : [30] NRZI (O/N) : [O] MODE (F/H/M) : [H]

NIVEAU PHYSIQUE ---------------

VIT (4-7) : [5] IRQ : [3] ADRESSE PORT : [380]

Figure 9-1. TDI Configuration Menu

NIVEAU APPLICATION ------------------

ADRESSES STATION (02-03) ECRAN : [02] IMPRIMANTE : [ ] SORTIE IP(0,1,2,D,N):[N] TYPE IP(D,S):[ ] MODE IP(E,L,B,S):[ ] TYPE ALPHA (0,9) : [6] TYPE EC (0-4) : [0] FICH IMPRESSIONS : [ . ] FICH COPIES ECRAN : [ . ]

PROTOCOLE LLC (P/Q) : [P] ID BLOCK:[017] ID NUMBER:[00000]

NIVEAU RESEAU (VOIR ABONNEMENT X25/X32) -------------

EMISSION APPELANT (O/N) : [N] NUMERO APPELANT: [ ] N° CV UTILISE:[01] FENETRE PAQUET [3] LONGUEUR PAQUET:[128]

NIVEAU PHYSIQUE --------------

X25 X32 (5/2):[5] VIT (0-7):[5] IRQ:[3] ADRESSE PORT:[380]

Figure 9-2. TXI Configuration Menu


9-4 47 A2 20UC Rev04

9.3.1 Filling in the Configuration Parameters

NIVEAU APPLICATION (Application Layer Parameters)

• ECRAN (Screen): mandatory.

Enter a value from 02 through 33 to define the LU number associated with the screen.

• IMPRIMANTE (Printer):

Enter a value from 02 through 33 defining the LU associated with the printer (mandatoryonly if the Host considers the printer as a LU).

• SORTIE IP (Printer connection):


0 : parallel printer connection1 : serial printer connected to port 12 : serial printer connected to port 2N : no printerD : redirection to a disk file (see FICH IMPRESSIONS and FICH COPIES ECRAN below)

• TYPE D'IP (Type of stream): Mandatory only if the Host considers the printer as a LU.


D : processed stream is 3270 Data Stream type (LU 3),S : processed stream is SNA Character String type (LU 1).

• MODE IP (Printer Mode):


L : LOCAL, the printer is not considered as a LU. Only screen copies may be printed.E : REMOTE, the printer is considered as a LU. Only messages from Host may be printed. Screen copies are not allowed.B : BRACKETS SHARING, the printer is seen as a LU. Messages from Host and screen copies may be printed. But screen copies may be rejected if the printer is in transaction (LU-LU session and In Brackets.S : SESSION SHARING, the printer is considered as a LU. Messages from Hosty and screen copies are allowed. But screen copies may be rejected if the printer is in LU-HU session.


47 A2 20UC Rev04 9-5

• TYPE ALPHA : mandatory.

Enter a single digit for the national character set.

0 : ASCII6 : French

• TYPE EC (Screen type):

Enter a digit to specify the hardware attributes of the type of terminal emulated.

0 : monochrome display, white text on black background1 to 4 : color display (2 for IBM terminals).

• FICH IMPRESSIONS (Message filename):

Enter the name and extension of the file to be used to store messages from the host (onlyapplicable if no printer, and messages are directed to disk).

• FICH COPIES ECRAN :

Enter the filename and extension of the file to be used to store screen copies (onlyapplicable if no printer, and screen copies are redirected to disk).

• PROTOCOLE : (TXI only)

P : means PSH protocol,Q : means QLLC protocol.

• ID BLOCK :

Enter three characters relative to emulated IBM product.

017 : indicates the emulation of a 3274 controller

• ID NUMBER :

Enter five characters identifying the emulated cluster (XID).


9-6 47 A2 20UC Rev04

NIVEAU LIAISON (Network Layer Parameters)

- EMISSION APPELANT : (TXI only)- NUMERO APPELANT : (TXI only)

On some X25 networks (private or foreign), it is mandatory to transmit one's own number.In this case, fill in the first field with O and the next field with the number.

• NUMERO CV UTILISE (Virtual Circuit Number) : (TXI only)

Enter the highest virtual circuit that your subscription allows.

• FENETRE PAQUET (Window Packet) : (TXI only)

Enter a value from 1 to 7 to specify the value of the window packet.

• LONGUEUR PAQUET (Packet size) : (TXI only)

Enter 128 or 256 according to the length of your subscription.

• ADRESSE CONTROLEUR (Controller Address) : (TDI only)

Enter the SDLC address of the emulated 3274 controller, in hexadecimal form.

• TIME OUT CONNECTION : (TDI only)

Enter a value expressed in seconds, representing the time during which the terminal iswaiting for the SDLC connection from the Host.

• NRZI : (TDI only)


N : NRZ codingO : NRZI coding

• MODE : (TDI only)


F : Full duplexH : Half duplexM : Multipoint (Full duplex on the central side and Half duplex on the terminal side).

Note: This parameter depends on the modem configuration.


47 A2 20UC Rev04 9-7

NIVEAU PHYSIQUE (Physical Layer Parameters)

• VIT (Transmission Speed) : mandatory

Enter a single digit from 4 through 7 to specify the speed of transmission in bits persecond (bps)

4 : 1200 bps5 : 2400 bps6 : 4800 bps7 : 9600 bps

• IRQ (Interrupt Level) : mandatory.

Enter a single digit from 2 to 7 to specify the IRQ setting on the XCOM3 board.

Note: The board is factory set at IRQ 3 and 380H.

• ADRESSE PORT (Port address) : mandatory.

Enter a 3-hexadecimal digit base address on the XCOM3 board corresponding to theactual configuration value.

When you have filled in the parameters, press Enter. The parameters are then validated.

The next menu to appear is for programming the function keys. This menu is optional. Ifyou do not want to program any of the function keys, just press Enter to start the logonsequence.


9-8 47 A2 20UC Rev04

9.3.2 Filling in the Function Key Program Parameters

It is possible to program the function keys F1 to F12 so that when you press one acommand is sent to the emulator. This saves you having to type in the command eachtime.

You can program the keys in normal mode, and also in combination with Shift, Control,and Alt. The only combinations that are fixed (i.e. non-programmable) are:

- Alt-F : Access to the file transfer menu.- Alt-X : To stop file transfer.- M mode Alt : To display a Host message, concerning the file transfer process.- H mode Alt : Display the keyboard configuration screen

At any moment, if the keyboard is not locked, it is possible to display this screen bypressing Alt-H. When you are ready, press any key to continue.


47 A2 20UC Rev04 9-9

9.4 CONNECTION TO THE HOST SYSTEM

The connection is started automatically when you leave the configuration menu, or pressa key other then C at the welcome screen. The message "CONNEXION EN COURS"appears on the screen.

If the connection is successful, the screen then goes blank. If it is not successful, thewelcome screen appears again, with one of the following messages on the bottom line:

- LU ECRAN-CLAVIER NON CONFIGUREE- LU IMPRIMANTE NON CONFIGUREE- LU ECRAN-CLAVIER DEJA DECLAREE- LU IMPRIMANTE DEJA DECLAREE- REFUS CONNEXION LIAISON- REFUS CONNEXION RESEAU C= D=- REFUS CONNEXION TRANSPORT SNA- LECTURE CONFIGURATION IMPOSSIBLE- INCIDENT FICHIER IMPRESSIONS- INCIDENT FICHIER COPIES ECRAN- NUMERO DE HOST INCORRECT- NOMBRE MAX DE LU OPEN DEPASSE- LU DEJA EN COURS DE CONNEXION

If another connection attempt is still unsuccessful, you should check the following:

• Configuration parameters : check compatibility between the server configuration andthe emulator configuration (according to the displayed message), that two terminalshave not been declared at the same address, and so on.

• Physical connections.

• Host system state.

Note: If the message "LIGNE HS" appears at any time after connection, it indicates abreak in the connection to the X25 network, the central system, or the operator.To reconnect, press Ctrl-F8.

You know that the connection to SNA network is established when the welcome pagebelonging to the site configuration appears on your screen.

In most cases, the Datanet appears as an application name, displayed amongst others ina connection menu. Just enter the application name to link to the Datanet.

If the Datanet has not been declared as an application in a connection menu, you can stilllogon using the LOGON command, as follows:

LOGON APPLID( datanet_plu_name )

where datanet_plu_name is the name of the Primary Logical Unit of the Datanet into theSNA network.


9-10 47 A2 20UC Rev04

9.5 CONNECTION TO DPS 7000 THROUGH DATANET

The connection through the Datanet starts when the first message of the logon sequenceappears on the screen :

$$ 4200 MODELE:

Press Enter for the default 327x model that micro has been declared as, or enter one ofthe 327x models declared in the Datanet generation to override the default.

The Datanet login messages then appear, followed by the prompt $*$ .

Log on to MML the DPS 7000 site as follows:

CN MML<dps7_name>


Now you can log on to the DPS 7000. Prompts for BILLING, USERID, PROJECT andPASSWORD appear consecutively. Enter the answer to each one, and press Enter.

If MML<dps7_name> has not been declared a correspondent in the DNS generation, youcan still log on using the CN command syntax give below:

CN -MB MML -SC <dps7_name> -USR <userid> -PW <password>


Depending on the authority codes declared for the MML application in the catalog,themode of connection determines the resulting prompt.


47 A2 20UC Rev04 9-11


Once the connection to MML is established, you can transfer files between the DPS 7000and the micro in either direction. To do this, you must first call up the File TransferInitialization Screen, by pressing Alt-F.

9.6.1 Filling in the File Transfer Initialization Form

INITIALISATION DU TRANSFERT

FICHIER-PARAM.(NOM) : [ ]

M.A.J.-FICHIER-PARAM.NOM:[ ]

NOUVEAU-FICHIER-PARAM.(NOM):[ ]

Figure 9-3. File Transfer Initialization Screen

On this screen, you must only fill in one field. The first time you use this screen, you willneed to fill in the first field, NOUVEAU-FICHIER-PARAM.(NOM). This is the name of thefile in which the actual parameters for file transfer will be saved (see 9.6.2, "Filling in theFile Transfer Parameters").

In subsequent sessions you only need to enter the name in the FICHIER-PARAM. (NOM)field to carry out the same transfer. This means that you do not have to fill in the filetransfer parameters every time you transfer the same file in the same direction.

You can also change the existing parameters in a subsequent session, by entering the filename in the M.A.J.-FICHIER-PARAM (NOM) field. The changed parameters are thenused for the transfer, and saved for later use.

Using the NOUVEAU-FICHIER-PARAM.(NOM) field, you can make several different files,each containing its own file transfer parameters. Then, each time you want to carry out atransfer, all you need do is enter the name of the parameter file in the FICHIER-PARAM.(NOM) field. For example, if you always have to transfer a particular file from theDPS7 to the micro on Monday mornings, and transfer it back again on Friday mornings,you could make two parameter files, called MONDAY and FRIDAY. On Monday you justenter MONDAY in the FICHIER-PARAM.(NOM) field, and the file is transferredautomatically. On Friday you enter FRIDAY, and the file is transferred back again.


9-12 47 A2 20UC Rev04

When you have filled in a field in the form and you press Enter, the value in the field ischecked. If it is wrong in any way, the form remains displayed with the cursor pointing atthe field concerned, an error message appears. Correct the field in error and press Enteragain.

File Transfer Initialization Parameters

• FICHIER-PARAM.(NOM)

Enter the name of an existing parameter file (up to 48 alphanumeric characters). PressEnter to start file transfer. The Transfer in Progress screen appears (see below).

• FICHIER-PARAM.NOM

Enter the name of an existing parameter file (up to 48 alphanumeric characters). PressEnter. The File Transfer Parameters Form appears (see below). You can then change theparameters you want, and press Enter to start the transfer.

• NOUVEAU-FICHIER-PARAM.(NOM)

Enter up to 48 alphanumeric characters to specify the name of the parameter file to becreated. Press Enter. The File Transfer Parameters Form appears, and you can fill in theparameters (see below). Pressing Enter on that screen to start the transfer.

After you have typed a name and pressed Enter, the File Transfer Parameters Formappears.


47 A2 20UC Rev04 9-13

9.6.2 Filling in the File Transfer Parameters

This form consists of two parts:

• The first part is common to the three types of host application, allowing you to entergeneral parameters for the file transfer.

• The second part, specific to each application type, allows you to enter optionalparameters. Note that it is only displayed when you enter something in the TYPE DECOMMANDE field.

TRANSFERT DE FICHIER - IND$FILE

TYPE DE COMMANDE (V=VM/CMS, T=TSO, C=CICS) : [ ]SENS DU TRANSFERT (O=TERMINAL-->HOTE, I=HOTE-->TERMINAL) : [ ]

SPECIFICATION FICHIER LOCAL : [ ]

SPECIFICATION FICHIER HOTE : [ ]

PARAMETRES OPTIONNEL DU TRANSFERT SOUS TSO.

ASCII (O/N) : [ ] CRLF (O/N) : [ ] APPEND (O/N) : [ ]RECFM (O/N) : [ ] TYPE (F/V/U) : [ ]LRECL (O/N) : [ ] TAILLE : [ ]BLKSIZE (O/N) : [ ] TAILLE : [ ]AVBLOCK (O/N) : [ ] TAILLE : [ ]SPACE (O/N) : [ ] QUANTITE : [ ] INCREMENT : [ ]TRACKS (O/N) : [ ] CYLINDERS (O/N): [ ]

PARAMETRES OPTIONNELS DU TRANSFERT SOUS VM/CMS

ASCII (O/N) : [ ] CRLF (O/N) : [ ] APPEND (O/N) : [ ]RECFM (O/N) : [ ] TYPE (F/V/U) : [ ]LRECL (O/N) : [ ] TAILLE : [ ]

PARAMETRES OPTIONNELS DU TRANSFERT SOUS CICS

ASCII (A) / BINARY (B) : [ ] CRLF (C) / NCRLF (N) : [ ]

Figure 9-4. File Transfer Parameters Form

Note: Where the answer to a prompt can only be O or N, you must type O for Yes, orN for No. The values for the other fields are explained in the followingparagraphs.


9-14 47 A2 20UC Rev04

TYPE DE COMMANDE : (Command type)

Enter a single character to specify the application on the Host system.

C : CICSV : VM/CMST : TSO

The optional parameters part of the form is then displayed.

SENS DU TRANSFERT : (Transfer direction)

The terminal is the point of reference for both Output and Input direction.Enter a single character specifying the direction of the file transfer.

I : from Host to Terminal (Input)O : from Terminal to Host (Output).

SPECIFICATION FICHIER LOCAL : (Local file name)

Enter up to 31 alphanumeric characters to specify the name of the file on the micro, in theformat:

<disk drive>\<directory>\<subdirectory>\<file_name>.<extension>

for example: c:\atl\file

SPECIFICATION FICHIER HOTE : (Host file name)

Enter up to 31 alphanumeric characters specifying the name of the file on the host, in thecorrect format for the host system.

ASCII :

Enter a single character to specify if conversion is to be made before the transfer begins.

For Output, this option causes the records to be converted from ASCII to EBCDIC beforethey are written to the file.

For Input, it causes the records to be converted from EBCDIC to ASCII before they aretransmitted to the micro.

CRLF :

For Output, this option forces the Host to delete CR (Carriage Return) and LF (Line Feed)characters at the end of each record before they are written to the file.

For Input, it forces the host application to add CR and LF characters at the end of eachrecord before they are transmitted to the micro.


47 A2 20UC Rev04 9-15

APPEND :

Used only for Output, this option causes the transferred file to be added at the end of theprevious file (if one exists).

If this option is not set, the existing file is overwritten by the transferred file. This option isnot supported by MML.

RECFM :

Used only for Output direction, this option specifies the type of records in the host file.Enter one of the following:

F : Fixed lengthV : Variable lengthU : Undefined type.

The default value is F, unless if CRLF option is set to O (Yes). In that case the defaultvalue is V. This option is not supported by MML.

LRECL :

Used only for Output, this option specifies the maximum record size of the host file. Thisvalue is by default 80. This option is not supported by MML.

BLKSIZE :

Used only for Output, this option specifies the expected blocksize of the host file. This sizemust not exceed a track capacity. This option is not supported by MML.

SPACE :

Used only for Output, this option specifies (initial size, increment) the allocated space foreach new TSO file. This option is not supported by MML.

AVBLOCK :

Used only for Output: if the Space field is set to O (Yes), this figure indicates the expectedaverage block size. This option is not supported by MML.

TRACKS :

Used only for Output: if the Space field is set to O (Yes), this figure indicates that the trackis the unit of space. This option is not supported by MML.

CYLINDERS :

Used only for Output: if the Space field is set to O (Yes), this option indicates that thecylinder is unit of space. This option is not supported by MML.


9-16 47 A2 20UC Rev04

Note: The AVBLOCK, TRACKS and CYLINDERS parameters are mutually exclusive.You can only fill in one of them.

APPEND, RECFM, LRECL, BLKSIZE, SPACE, AVBLOCK, TRACKS,CYLINDERS are not used for file transfer on DPS7.

Once you have filled in all the necessary parameters, press Enter. The parameters arechecked.

When all parameters are correct, pressing Enter starts the file transfer. The number ofbytes transmitted is displayed on the system line while the transfer is taking place.

You can stop the file transfer at any time, by pressing Alt-X.

At the end of the file transfer, the Host may send a message. In this case you will see thetext "MESS" on the system line. To display the message press Alt-M.

To disconnect:

• at M: level, enter BYE;

• at datanet prompt level, enter LOGOUT

• at VTAM-BULL level, press Shift-F10.

47 A2 20UC Rev04 10-1

10. IRMA Connection from PC-327x terminals

10.1 STARTING THE EMULATOR

For full instructions on how to start the emulator, refer to the IRMA documentation. Thefollowing is an example.

DFTSX -R

starts the emulator in SNA mode (S), without a printer ( X ) and specifies that the emulatoris to stay resident (-R).

The emulator must be started in resident mode in order to switch to DOS mode which isthe only one where files transfer can be done (see Transferring Files, below).

10.2 CONNECTING TO THE HOST SYSTEM

The connection is automatically made once the emulator has been started.

You know that the connection to SNA network is established when the welcome screen ofthe site configuration appears on the screen.

In most cases, the Datanet appears as an application name, displayed amongst others ina connection menu. Just enter the application name to link to the Datanet.

If the Datanet has not been declared as an application in a connection menu, you can stilllogon using the LOGON command, as follows:

LOGON APPLID( datanet_plu_name )

where datanet_plu_name is the name of the Primary Logical Unit of the Datanet into theSNA network.



10.3 CONNECTION TO DPS 7000 THROUGH DATANET

This procedure is independent of the emulator, and is therefore the same as the Atlantisone.

The connection through the Datanet starts when the first message of the logon sequenceappears on the screen :

$$ 4200 MODELE:

Press Enter for the default 327x model that micro has been declared as, or enter one ofthe 327x models declared in the Datanet generation to override the default.

The Datanet login messages then appear, followed by the prompt $*$ .

Log on to MML the DPS 7000 site as follows:

CN MML<dps7_name>


Now you can log on to the DPS7. Prompts for BILLING, USERID, PROJECT andPASSWORD appear consecutively. Enter the answer to each one, and press Enter.

If MML<dps7_name> has not been declared a correspondent in the DNS generation, youcan still log on using the CN command syntax give below:

CN -MB MML -SC <dps7_name> -USR <userid> -PW <password>


Depending on the authority codes declared for the MML application in the catalog, themode of connection determines the resulting prompt.

IRMA Connection from PC-327x terminals

47 A2 20UC Rev04 10-3


To transfer files to and from the micro, carry out the following steps.

1 Press Left Shift and Right Shift at the same time to switch the IRMA emulator toDOS mode.

2 Use the SEND and RECEIVE commands to transfer the files.

Note: The files SEND.EXE and RECEIVE.EXE must be in your current directory or inthe DOS path.

The terminal is always the point of reference for SEND and RECEIVEcommands.

The syntax of the SEND and RECEIVE command parameters is the same, as follows:

SEND command (Terminal to Host) :Send [d:][path] filename.ext [h:]Hostfilname [(Options)]

RECEIVE command (Host to Terminal) :Receive [d:][path] filename.ext [h:]Hostfilename [(Options)]

where:

• d: is the name of the PC drive where the file is located.

• path is the path of the subdirectory the file is in.

• filename.ext is the name of the file to be sent or received, including the extension.

• h: is the short name of the host session that you want to send the file to or receive thefile from. The default value is a:.

• Hostfilename is the name of the file on the host, in the format of the host system:

For VM/CMS : fn ft fm (filename filetype filemode)For MVS/TSO : data-set-nameFor MVS/CICS : fn (filename)

In most cases, the correct format is the last one:Directoryname.filename..subfilename



• Options:

There are various options for an IBM host running VM/CMS, MVS/TSO, or MVS/CICS, butthe only ones supported by MML are ASCII and CRLF.

ASCII : A single alpha character denoting if conversion is to be made before the transferbegins. [This does not seem to true - see the example below. Must one enter the keyworditself? Same goes for CRLF]

For Output (SEND command) , this option causes the records to be converted from ASCIIto EBCDIC before they are written to the host file.

For Input (RECEIVE), this option causes the records to be converted from EBCDIC toASCII before they are transmitted to the micro. If this option is not set, no conversion willbe done.

CRLF: for Output (SEND command), this option forces the host to delete CR (CarriageReturn) and LF (Line Feed) characters at the end of each record before they are written tothe host file.

For Input (RECEIVE command), it forces the host application to add CR and LFcharacters at the end of each record before they are transmitted to the micro.

Example

SEND C:\DOC\RAPPORT.TXT MIT.PAUL.SLLIB..RAPPORT1 (ASCII CRLF)

During the file transfer, the following progress messages are displayed:

Data Bytes: xxxxx Packets: xxx

TRANS03 File transfer complete

Data bytes: xxxxx Packets: xxxBytes/sec: xxxx Millisec/packet: xxxx Seconds: xxxxx

Technical publication remarks form

Title : DPS7000/XTA NOVASCALE 7000 Microfit 7 User's Guide Communications:Applications

Reference Nº : 47 A2 20UC 04 Date : October 1995

ERRORS IN PUBLICATION

SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION

Your comments will be promptly investigated by qualified technical personnel and action will be taken as required.If you require a written reply, please include your complete mailing address below.

NAME : Date :

COMPANY :

ADDRESS :

Please give this technical publication remarks form to your BULL representative or mail to:

Bull - Documentation Dept.

1 Rue de ProvenceBP 20838432 ECHIROLLES [email protected]

Technical publications ordering form

To order additional publications, please fill in a copy of this form and send it via mail to:

BULL CEDOC357 AVENUE PATTONB.P.2084549008 ANGERS CEDEX 01FRANCE

Phone: +33 (0) 2 41 73 72 66FAX: +33 (0) 2 41 73 70 66E-Mail: [email protected]

CEDOC Reference # Designation Qty

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

[ _ _ ] : The latest revision will be provided if no revision number is given.

NAME: Date:

COMPANY:

ADDRESS:

PHONE: FAX:

E-MAIL:

For Bull Subsidiaries:

Identification:

For Bull Affiliated Customers:

Customer Code:

For Bull Internal Customers:

Budgetary Section:

For Others: Please ask your Bull representative.

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

47 A2 20UC 04REFERENCE

microfit 7 user's guide - bull on-line support...

Documents