tn series of interfaces - funassetthe tn series of interfaces table of contents technical reference...

TN Series of Interfaces

TECHNICAL REFERENCE MANUALMANTN0101 - Issue 1.1

TN Series of InterfacesTechnical Reference Manual

MANTN0101 - Issue 1.1

FunAsset LimitedOrchards14 TownsendIlminsterSomersetTA19 0AUUK.

Tel: +44 (0)1460 57065Fax: +44 (0)1460 53538

Email: [email protected]

Websites: http://www.funasset.comhttp://support.funasset.comhttp://www.spoolq.com

© Copyright 1997-2002 FunAsset Limited. All rights reserved.

The TN Series and SpoolQ are trademarks of FunAsset Limited.

Products and trademarks of other companies are also acknowledged.

Changes are periodically made to this document. Technical updates will be included in subsequent editions.

TECHNICAL REFERENCE MANUAL iii

Table of Contents

Foreword 1.1

Content 1.2

Manual Conventions 1.4

Wording 1.4

Side Headings 1.4

Configuration Parameter References 1.4

Figures 1.4

Hardware Interference 1.5

Related Publications 1.6

FunAsset 1.6

Operating Systems 1.6

Source and Destination 1.6

IBM Devices 1.6

TCP/IP Protocols 1.6

Feedback 1.7

Introduction 2.1

TN Interfaces 2.2

TN3000 2.2

TN4000 2.2

TN5000 2.2

TN6000 2.3

TN8000 2.3

Supported Connections 2.4

Input Connections 2.4

Output Connections 2.4

Hardware 2.5

Installation 2.5

Specifications 2.5

Health and Safety 2.5

Maintenance 2.5

Software 2.6

TABLE OF CONTENTS THE TN SERIES OF INTERFACES

iv TECHNICAL REFERENCE MANUAL

Installation 2.6

Location 2.6

TN3000 2.6

TN4000 2.6

TN5000 2.6

TN6000 2.6

TN8000 2.6

Tasks 2.6

Operation 2.7

Configuration 2.7

Controlling and Monitoring 2.7

Additional Processing 2.7

Task Configuration Files 2.7

Multitask 2.8

Spooling Systems 2.8

Version Numbers 2.9

MS-DOS 2.9

Windows NT/2000 2.9

Filename and Directory Name Considerations 2.10

MS-DOS 2.10

Windows NT/2000 2.10

UNIX 2.10

Creating and Editing User Definable Files 2.11

MS-DOS 2.11

Creating 2.11

Editing 2.11


Creating 2.11

Editing 2.11

Shortcuts 2.13

Disk Access Errors 2.14

Year 2000 compliance 2.15

Tasks 3.1

Overview 3.2

Structure 3.3

Common Module 3.3

Input Module 3.3

Emulation 3.3

Conversion 3.3

Output Module 3.3

Conversion 3.4

Emulation 3.4

Input Pre-processing Module 3.4

Input Extra Processing Module 3.4

Output Pre-processing Module 3.4

Further Additional Processing 3.4

Internal Format 3.5

THE TN SERIES OF INTERFACES TABLE OF CONTENTS

TECHNICAL REFERENCE MANUAL v

Normal 3.5

IBM Channel 3.5

Binary 3.5

Task Names and Availability 3.6

Configuration 3.7

Loading 3.8

TN3000 3.8

TN4000 and TN5000 3.8

TN6000 3.8

TN8000 3.8

Control Screen 3.9

Content 3.9

Command Line 3.10

Command Line Prompt 3.10

Job Status 3.10

Job Description 3.10

Input Module Configuration 3.10

Output Module Configuration 3.10

Output Module Status 3.11

Trace 3.11

Communication Messages 3.11

Page Status 3.11

Displaying 3.11

TN3000 3.11

TN4000 and TN5000 3.12

TN6000 3.12

TN8000 3.12

Hiding 3.13

Dump Screen 3.14

MS-DOS 3.14


Run Mode 3.15

Starting 3.15

Halting 3.15

TN3000 3.15

TN4000 and TN5000 3.15

TN6000 and TN8000 3.15

System Fields 3.16

PRFILE 3.17

Sending a File 3.17

Halting 3.17

PRTEST 3.18

Starting 3.18

Halting 3.18

Unloading and Loading the FunAsset Hardware Driver 3.19

Unloading 3.19

Loading 3.19

Displaying Version Numbers 3.20


vi TECHNICAL REFERENCE MANUAL

MS-DOS 3.20


Exiting 3.21

TN3000 3.21

TN4000 and TN5000 3.21

TN6000 3.21

TN8000 3.21

Configuration Parameter Overview 4.1

Overview 4.2

Operation 4.3

Options 4.4

Fixed 4.4

nn 4.4

xx 4.4

Optional 4.4

IN 4.4

ICL, TCP and OUT 4.5

nn (Printer Number) 4.5

NEW 4.5

SRCE and DEST 4.6

Order of Precedence 4.7

Spooling System Printer Numbers 4.8

Input Task 4.8

Defining a New Printer Number 4.8

Storing the Printer Number 4.8

Resetting the Printer Number 4.8

Output Task 4.9

Using a Printer Number Associated with a Print Queue 4.9

Using the Printer Number (#N) System Field 4.9

Task Configuration Files 5.1

Overview 5.2

Considerations 5.2

MS-DOS 5.2

Windows NT/2000 5.2

Location 5.3

TN3000, TN4000 and TN5000 5.3

TN6000 5.3

TN8000 5.3

Default Filenames 5.4

Creating and Editing 5.5

Structure 5.6

Remarks 5.6

MS-DOS 5.6

Windows NT/2000 5.6

Configuration Parameters 5.6

TN3000 5.6


TECHNICAL REFERENCE MANUAL vii

TN4000 and TN5000 5.7

TN6000 and TN8000 5.7

Task Filename 5.7

TN3000 5.7

TN4000 and TN5000 5.7

TN6000 and TN8000 5.7

Start-up Commands 5.7

Associating with Tasks 5.9

TN3000 5.9

TN4000 and TN5000 5.9

TN6000 5.9

TN8000 5.10

Loading 5.11

TN3000 5.11

Automatically Loading a Task Configuration File 5.11

Using Multiple Task Configuration Files 5.11

TN4000 and TN5000 5.11

TN6000 5.11

TN8000 5.12

Multitask 6.1

Overview 6.2

System Preparation 6.3

CONFIG.SYS 6.3

MS-DOS Version 5.0 6.3


AUTOEXEC.BAT 6.4



Launch File 6.6

Content 6.6

TN3000 6.6

TN4000 6.6

TN5000 6.7

Preparing the Directories 6.7

Initialising the Mouse 6.7

Assigning Task Numbers 6.7

Task Configuration File 6.8

Task 6.8

PrintQ or SpoolQ DOS 6.8

Loading Multitask 6.8

Task Configuration File 6.8

Task 6.8

PrintQ or SpoolQ DOS 6.8

Task Screen 6.9

Content 6.9

Task Windows 6.9

Log Window 6.9


viii TECHNICAL REFERENCE MANUAL

Command Line (Version 3.2) 6.10

Displaying 6.10

Accessing Tasks and PrintQ or SpoolQ DOS 6.11

Function Keys 6.11

Mouse (Version 4.2) 6.11

Displaying the Version Number 6.12

Version 3.2 6.12

Version 4.2 6.12

Exiting 6.13

Version 3.2 6.13

Version 4.2 6.13

System Fields 7.1

Overview 7.2

Identifiers and Descriptions 7.3

Defining the Content 7.5

Using Configuration Parameters 7.5

Overwriting 7.5

Clearing 7.5

Using Banner Processing 7.5

Using TCP/IP Jobs 7.5

LPR 7.6

Using Spooling Systems 7.6

Using Input Modules 7.6

Using 7.7

Defining Configuration Parameters 7.7

Defining Other System Fields 7.7

Extracting Numeric Data 7.7

Configuring Jobs Within SpoolQ 7.8

Creating Output Banners 7.8

Defining Accounting Information 7.8

Defining Notification Information 7.8

Common Module Overview 8.1

Input Module Overview 9.1

Bull PDSI (PDSI) 9.2

Associated Hardware 9.2

Task Name 9.2

Connectivity Solution 9.2


Installation 9.2

Data Handling 9.3

Print Positioning 9.3

Communication 9.3

Maintenance 9.4

Control Screen Display 9.4

Configuration Properties 9.4

Trace Codes 9.4


TECHNICAL REFERENCE MANUAL ix

Using with Multitask 9.4

Dataproducts and Centronics (DPI) 9.6


Task Name 9.6



Installation 9.6

Data Handling 9.7

Print Position 9.7

Communication 9.8

Maintenance 9.8




Trace Codes 9.9

Bit “Swapping” 9.9

Data Loss From Certain Sources 9.10

Adding Line Feeds After Carriage Returns 9.10

Adding a Form Feed to the Bottom of a Page 9.10

Dummy (DI) 9.11

Task Name 9.11

File (FILI) 9.12

IBM Channel and Siemens Type 2 (IBMI) 9.13


Task Name 9.13


Example 1 9.13

Example 2 9.13


Installation 9.13

Data Handling 9.14

Print Position 9.15

Communication 9.15

Maintenance 9.15

Siemens Type 2 9.15



Trace Codes 9.16

Ignoring Single Space Lines 9.16

Setting the FCB Channel 1 to Top of Form 9.16

ICL OSLAN (ICLI) 9.17


Features 9.17

Task Name 9.17


Example 1 9.17

Example 2 9.17



x TECHNICAL REFERENCE MANUAL

Installation 9.18

Data Handling 9.18

Print Position 9.19

Communication 9.19

Maintenance 9.20




Trace Codes 9.21

Repeating Data Problems 9.21

Retransmission of OSLAN Packets 9.21

Error Packets 9.22

Correct Configuration Parameters with LaserPack 9.22

Getting Escape Sequences to a Printer From VME 9.22

Defining the Correct Character Set 9.22

Allowing Escape Characters 9.22

Accepting a Full Line of ‘Print’ Data 9.22

Autowrap and Illegal Character Conversion 9.23

Setting Discard on a TN Interface 9.23

Correct Slow File Descriptions 9.23

Impact Printer Considerations 9.23

Non-Impact Printer Considerations 9.23

ICL OSLAN and TCP/IP (NETI) 9.24


Features 9.24

Restrictions 9.24

Task Name 9.24




ICL Peripheral Interface (FPI) 9.26


Features 9.26

Task Name 9.26



Installation 9.26

Data Handling 9.27

Print Position 9.27

Communication 9.27

Maintenance 9.28



Trace Codes 9.28

PC Serial (PCI) 9.29


Features 9.29

Task Name 9.29


TECHNICAL REFERENCE MANUAL xi



Installation 9.29

Data Handling 9.30

Print Position 9.30

Communication 9.31

Maintenance 9.31



Trace Codes 9.32

Serial Remote (SxRI) 9.33


Features 9.33

Task Name 9.33



Installation 9.34

Communication 9.34



Trace Codes 9.35

TCP/IP (TCPI) 9.36


Features 9.36

Task Name 9.36


Example 1 9.37

Example 2 9.37


Installation 9.37

Data Handling 9.38

Print Position 9.40

Print Job 9.41

Communication 9.41

Maintenance 9.41



Communications Messages 9.42

Trace Codes 9.42

Adding Output Banners 9.43

BVLR and VLR File Transfer 9.43

Passing Binary Files 9.43

Ignoring Control Codes 9.43

Unpacking Data 9.43

ASA Carriage Control Code Conversion 9.44

FTP 9.44

LPR 9.44

All Sources 9.44


xii TECHNICAL REFERENCE MANUAL

Conversion to CCWs 9.44

Novell Networks 9.45

Windows Sockets (SKTI) 9.46

Output Module Overview 10.1

Dataproducts (DPO) 10.2


Supported Destinations and Protocols 10.2

Task Name 10.2



Installation 10.3

Data Handling 10.3

Print Position 10.3

Communication 10.3

Maintenance 10.4



Status 10.4

Trace Codes 10.5

Dummy (DO) 10.6

Task Name 10.6

File Out (FILO) 10.7

IBM Channel (IBMO) 10.8


Features 10.8

Supported Printers and Protocols 10.8

Task Name 10.8


Example 1 10.9

Example 2 10.9


Installation 10.9

Data Handling 10.10

Print Position 10.10

Communication 10.11

Maintenance 10.11



Status 10.12

Trace Codes 10.12

Outputting to a Micronology MI4872 Interface in High Speed Mode 10.13

Outputting to Xerox CEP Printers 10.13

CCWs Attached to DJDEs are Discarded 10.13

Vertical Alignment Problem 10.13

Duplex Problem 10.14

PC Parallel / Serial (PCO) 10.15



TECHNICAL REFERENCE MANUAL xiii

Features 10.15

Parallel 10.15

Serial 10.15


Task Name 10.15



Installation 10.16

Data Handling 10.17


Communication 10.17

Maintenance 10.18


Configuration Properties (File / Screen) 10.18

Configuration Properties (Parallel) 10.19

Configuration Properties (Serial) 10.19

Status 10.19

Trace Codes 10.19

Genicom 440XT Print Positioning Problem 10.20

Outputting to ICL FP1500 and FP2000 Printers 10.20

Serial Remote (SxRO) 10.21


Features 10.21

Task Name 10.21



Installation 10.22

Data Handling 10.22


Communication 10.23



Status 10.23

Trace Codes 10.23

TCP/IP (TCPO) and TCP/IP Network Bridge (TIPO) 10.25


Features 10.25



Example 1 10.26

Example 2 10.26

Example 3 10.26


Installation 10.27

Data Handling 10.28


Communication 10.28

Maintenance 10.29


xiv TECHNICAL REFERENCE MANUAL

FTP 10.29

LPR 10.30

ASA 10.30



Status 10.31

Trace Codes 10.31

ASA Carriage Control Code Output 10.31

Changing ASA Carriage Control Code Values 10.32

Removing Unwanted Form Movements 10.32

Removing CRs from the End of Jobs 10.32

Outputting to the AIX Operating System 10.32

Outputting to the Sun Operating System 10.32

SunOS 4.1 10.33

SunOS later than 4.1 10.33

Outputting to the OS/2 Operating System 10.33

Missed Packet Retries 10.34

Illegal or Non-standard Data Received During Closedown 10.34


Windows NT Printer (NTPO) 10.35

Windows Sockets (SKTO) 10.36

PrintQ 11.1

Overview 11.2

Operation 11.3

Using Printer Numbers 11.3

Loading 11.4

Monitor Screen 11.5

Version Number 11.5

Features 11.6

Input Module (SPLI) 11.7

Task Name (Output Task) 11.7


General 11.7



Trace Codes 11.8

Output Module (SPLO) 11.9

Task Name (Input Task) 11.9


Installation 11.9

Data Handling 11.9

Print Position 11.9

Communication 11.10

Maintenance 11.10

System Fields 11.10




TECHNICAL REFERENCE MANUAL xv

Status 11.11

Trace Codes 11.11

Spool Files 11.13

Determining the Amount of Data to Write to Each Spool File 11.13

MAXFILESIZE 11.13

SPLITTIME 11.13

Filename Format 11.13

Name 11.13

Extension 11.14

Start Spool File (STA, STH and Pnn) 11.14

Released (STA) 11.14

Held (STH) 11.14

Outputting (Pnn) 11.14

Data Spool File (nnn) 11.14

Continuation Spool File (CON) 11.14

Continuation Start Spool File (STC) 11.15

End Spool File (END) 11.15

Error Spool File (ERR) 11.15

Hard Drive Space Management 11.15

Job Details 11.16

Description 11.16

Unknown Files and Dump Files 11.16

Job Size 11.16

Activity 11.16

Destination Identification Number 11.16

Load Sharing 11.17

Prioritising 11.18

Using System Fields 11.19

SpoolQ 12.1

Overview 12.2

Operation 12.3

Using Printer Numbers 12.3

Loading 12.4

SpoolQ DOS 12.4

SpoolQ NT/2000 12.4

Task Launch File - TASKFILE.BAT 12.5

Content 12.5

Management Screen 12.6

SpoolQ DOS 12.6

Version Number 12.6

SpoolQ NT/2000 12.6

Version Number 12.7

Features 12.8

SpoolQ NT/2000 12.8

Input Module (SQUI) 12.9

Task Name (Output Task) 12.9



xvi TECHNICAL REFERENCE MANUAL

General 12.9



Trace Codes 12.10

Output Module (SQUO) 12.11

Task Name (Input Task) 12.11


Installation 12.11

Data Handling 12.11


Communication 12.12

Maintenance 12.12

System Fields 12.12



Status 12.13

Trace Codes 12.13

Queues 12.15

Types 12.15

Host Queue 12.15

Class Queue 12.15

Group Queue 12.16

Print Queue 12.16

Number Codes 12.16

Associated Files 12.16

Content 12.16

Spool Files 12.17

Queue Start Spool File 12.17

Outputting (PRN) 12.17

Done Spool File (DUN) 12.17

Processing Jobs 12.18

Determining What Queue to Place a Job In 12.18

Holding and Releasing 12.18

RELEASE Parameter 12.18

LPR Jobs Consisting of a Data File and Control File 12.19

Banner Processing 12.19

Job Details 12.20

Identification Number 12.20

Queue Name 12.20

Description 12.21

Copies 12.21

Activity 12.21

Number of Pages 12.21

Archiving 12.22

Accounting 12.23

Notification 12.24

Using System Fields 12.25


TECHNICAL REFERENCE MANUAL xvii

Accounting 13.1

Overview 13.2

Operation 13.3

Configuration 13.4


Installation 13.4

General 13.4

Accounting Files 13.5

Location 13.5

Filename Format 13.5

File ID 13.5

Creation 13.5

Defining the Content of Accounting Files 13.6

Format Files 13.6



Commands 13.7

Character Processing 13.7

Line Movements 13.7

System Fields 13.7

Job Information 13.8

Date Format 13.8

Time Format 13.9

Elapsed Time Format 13.9

Archiving 14.1

Overview 14.2

Operation 14.3

Archive Directory (DONEDIRS) 14.4

Name Format 14.4

Name 14.4

Extension 14.4

Completed Job Limit 14.5

Displaying Completed Jobs 14.6

Notification 15.1

Output Banners 16.1

Overview 16.2

Operation 16.3

Queue Based 16.3

Job Based 16.3

Configuration 16.4


Installation (SPLI and SQUI) 16.4

Installation (SPLO and SQUO) 16.4

Data Files 16.5

Location 16.5


xviii TECHNICAL REFERENCE MANUAL


Structure 16.5

Commands 16.6

PDL Commands 16.6

Character Processing 16.6

System Fields 16.6

Accounting Details 16.6

Control Codes 16.6

Positioning 16.7

Line Movements 16.7

Remarks 16.7

Channel Control Words (CCWs) 16.7

Performance Monitor 17.1

Overview 17.2

Task Name 17.2


Status 17.2

Arabisation 18.1

Overview 18.2

Operation 18.3

Configuration 18.4


Installation 18.4

General 18.4

Character Handling 18.4

Print Position 18.5

Diagnostics 19.1

Overview 19.2

Operation 19.3

Configuration 19.4


General 19.4

Saving Data 19.5

Outputting Saved Data 19.6

Configuration Parameters Required for IBMIIBMO 19.7

AutoFilter 20.1

Overview 20.2

Operation 20.3

Configuration 20.4


Installation 20.4

Dumping 20.4

General 20.4

Parameter Files 20.6

Location 20.6


TECHNICAL REFERENCE MANUAL xix

Default Files 20.6


Structure 20.6

Remarks 20.7

Commands 20.7

Redefining Default Parameter File Characters 20.9

DELIMITER 20.9

Format 20.9

Example 20.9

Default 20.9

LENGTH 20.9

Format 20.9

Example 20.9

Default 20.9

NUMBER 20.9

Format 20.10

Example 20.10

Default 20.10

WILDCHAR 20.10

Format 20.10

Example 20.10

Default 20.10

Determining Escape Sequence Information 20.11

PDL Validation (VALIDATION) 20.11

Format 20.11

Example 20.11

Default 20.11

Character Set (CHARSETESCAPE) 20.11

Format 20.11

Example 20.11

Default 20.11

Identification Character (ESCAPE) 20.12

Format 20.12

Example 20.12

Default 20.12

Valid Control Codes (PASS) 20.12

Format 20.12

Example 20.12

Defining Escape Sequence Substitution Strings (STRING) 20.13

Format 20.13

Identification Number (nn) 20.13

Substitution String (x) 20.13

Defining Escape Sequences (IDENTIFY) 20.14

Format 20.14


Character String (x) 20.14

Multiple Escape Sequences 20.14

Indicating Data Numerals (9) 20.15


xx TECHNICAL REFERENCE MANUAL

Indicating Length Numerals and Passing Binary Data (#) 20.15

Wildcards (?) 20.15

Determining the Action to be Taken (ACTION) 20.16

Format 20.16


Action (xxxxxxxxxxxx) 20.16

Determining the Type of Data to Process 20.17

Dumping 20.18


Overview 21.2

Operation 21.3

Configuration 21.4


Installation 21.4

Dumping 21.4

Parameter Files 21.5

Location 21.5


Structure 21.5

Remarks 21.5

Commands 21.6

Defining an Identification String (STRING) 21.7

Format 21.7


Identification String (xxxxx) 21.7

Wildcard Statements 21.7

Multiple Fixed and Variable Data Statements 21.7

Determining Search Lines (BANNER / IDENTIFY) 21.9

Format 21.9


Character String (STRINGnn) 21.9

Statement Separation Character (@) 21.9

Line Number(s) (LINESaa-bb) 21.9

Defining Multiple Statements (&) 21.10

Searching Multiple Contiguous Pages (+) 21.10

Identifying the Correct Page (+) 21.11

Ensuring Efficiency 21.12

Determining the Action to be Taken (ACTION / JOBSPLIT) 21.13

Format 21.13


Data Split ([position]) 21.13

Number of Consecutive Identical Pages (MULTImm) 21.14

Printer Number (PRINTERnn) 21.16

Data Processing [task] 21.16

Defining System Fields 21.18

Determining the Variable Data to Copy 21.18

Wildcard Statements 21.18


TECHNICAL REFERENCE MANUAL xxi

Multiple Fixed and Variable Data Statements 21.18

Assigning Variable Data 21.19

Temporary System Fields 21.19

Copying Variable Data to a System Field 21.19

Increased Length System Fields 21.20

Using with SpoolQ 21.20

PCL Data 21.22

Resources 21.22

Preparing the Data 21.22

Defining Character Strings 21.22

Line Numbers 21.22

Using the ENDJOB Statement 21.22

ENDJOB@RESET 21.23

ENDJOB@NEXTBANNER 21.24

ENDJOB@NEXTBANNER/RESET 21.24

Processing IBM Channel Data and CCWs 21.25

PROCESS 21.25

Format 21.25

CCWxx 21.25

Format 21.25

Binary Value 21.25

Dumping 21.27

Example Process 21.28

Splitting the Data and Defining a System Field 21.28

Deleting the Banner Page 21.29

AutoFTP 22.1

Overview 22.2

Operation 22.3

Configuration 22.4


Installation 22.4

Communication 22.4

Data Handling 22.5


Unpacking Data 22.7

AutoRouting 23.1

Overview 23.2

Operation 23.3

Configuration 23.4


General 23.4

Telnet 23.4

LPR 23.4

FTP 23.5

Determining the Location of a Destination 23.6

Multiple Destinations 23.6


xxii TECHNICAL REFERENCE MANUAL

Determining Destination Directories and Subdirectories 23.7

Directories 23.7

Subdirectories 23.7

Determining Destination Queues 23.8

Filename Generation 23.9

UNIX Servers 23.9


Dumping 24.1

Overview 24.2

Operation 24.3

Configuration 24.4


Installation 24.4

Network 24.4

DMA 24.4

Disabling DMA 24.6

Determining the Destination 24.7

File 24.7

Screen 24.7

Printer 24.7

Additional Dump Information 24.8

AutoFilter 24.8


Output Module 24.8

Network Data 24.9

Promiscuous 24.9

Monitoring 24.9

Dump File Error 24.11

Interpretation 24.12

Bull PDSI 24.12

IBM Channel 24.13

ICL OSLAN 24.14

TCP/IP 24.15

Packet Information Excluded 24.15

Packet Information Included 24.16

DMA Switched On 24.17

Banner Processing Data 24.18

Channel Tunnelling 25.1

Overview 25.2

Configuration 25.3


Installation 25.3

CCW 25.3

General 25.4

Escape Sequence 25.5

Identification Characters (1F 4B) 25.5


TECHNICAL REFERENCE MANUAL xxiii

Channel Control Word (CCW) 25.5

Data Count (HO:LO) 25.5

Binary Data 25.5

Operation 25.6

Input Modules 25.6

IBMI 25.6

DPI, ICLI, NETI, OSI, PCI, PDSI, TCPI 25.6

Output Modules 25.7

PCO 25.7

TCPO 25.7

DPO, IBMO 25.8

Overview Table 25.8

Character Set Considerations 25.10

Input Data 25.10

Output Data 25.10


TCPO and SKTO 25.10

CCW Validation 25.11

CCW Modification 25.12

Connectivity Solutions 25.13

Example 1 25.13

Example 2 25.13

Example 3 25.13

Example 4 25.13

Example 5 25.14

Example 6 25.14

Data Tunnelling 26.1

Overview 26.2

Configuration 26.3


Installation 26.3

General 26.3


Identification Characters (0F 00) 26.4

Data Count [HO:LO] 26.4

Binary Data 26.4

Operation 26.5

APO Unpacking 27.1

Overview 27.2

Operation 27.3

Configuration 27.4


Installation 27.4

General 27.4

Output Data Format 27.5

Non-APO Data 27.5


xxiv TECHNICAL REFERENCE MANUAL

Start of Form Group and End of Form Group 27.5

Start of Form and End of Form 27.5

Field Data 27.5

Control Codes in APO Data 27.6

Slow File Descriptions 27.7

Data Formats 28.1


ACKRPTIME 29.8

ACKTIME 29.8

ADDCRATEOJ 29.8

ALLCHAR 29.8

ALWDATACHK 29.9

ANTICLOG 29.9

ANTICLOGTIME 29.10

APOCHARxx 29.10

APOUNPACK 29.10

ARABCHARxx 29.11

ARABDIRECTION 29.11

ARABIDENT 29.11

ARABLINELENGTH 29.11

ARABNUMBERS 29.12

ARABPROCESS 29.12

ARABSTRACTIONnn 29.12

ARABSTRINGnn 29.13

ARABXLATE 29.13

ARABxx 29.13

ARPRPCT 29.14

ARPRPTIME 29.15

ASACCWxx 29.15

ASACHnn 29.15

ASACR 29.15

ASADLF 29.16

ASAFF 29.16

ASAINPUT 29.16

ASALE 29.17

ASALF 29.17

ASAPROCESS 29.17

ASATLF 29.17

ASYNC 29.18

ATTENDHOLD 29.18

AUTOFTP 29.18

AUTOFTPCYCLETIME 29.18

AUTOLF 29.19

BANDID 29.19

BANNERFILE 29.19

BANNERS 29.19

BAUDRATE 29.20


TECHNICAL REFERENCE MANUAL xxv

BELT 29.20

BLKDATACHK 29.21

BLKMODE 29.21

BLKOFFLTIME 29.21

BLKONLATDMD 29.21

BLKPRTIME 29.22

BLKVREC 29.22

TCPI 29.22

Other Input Modules 29.22

BUFCLR 29.22

CACTxx 29.23

CARTRIDGE 29.23

CCDELAY 29.23

CCRPCT 29.24

CCRPTIME 29.24

CCWASAxx 29.24

CH1TOTOF 29.24

CHADDRESS 29.25

CHAR5B 29.25

CHAR7B 29.25

CHARE0 29.25

CHARSET 29.25

Arabisation 29.26

CHARSETFILE 29.26

CHARSETOUT 29.26

CHARxx 29.27

CHBLKBIN 29.27

CHTUNNEL 29.27

COMMANDCCW 29.28

COPIES 29.29

CREQLF 29.29

D7FROMPI 29.29

DATAOPTION 29.29

DATARPCT 29.30

DATARPTIME 29.30

DATATUNNEL 29.30

DATETIME 29.31

DBITS 29.31

DCHKLOAD 29.31

DCISPEED 29.32

DCMDxx 29.32

DCU 29.32

DCU1TOUT 29.32

DEFAULTCCW 29.33

DENSITY 29.33

DEPTH 29.33

DESTIPADDR 29.34

DESTIPADDRESS 29.34


xxvi TECHNICAL REFERENCE MANUAL

DESTIPFILE 29.35

DESTLANADDR 29.35

DESTPORT 29.36

DIDELAY 29.36

DIDMA 29.36

DISCONNECT 29.36

DISCTIME 29.37

DISPEED 29.37

DNAME 29.37

DOCNAME 29.38

DONELIMIT 29.38

DOSPEED 29.38

DPISPEED 29.38

DROPFFATEOJ 29.38

DROPFFATSOJ 29.39

DROPPCLRSTJOBS 29.39

DUMP 29.39

DUMPFILTER 29.39

DUMPJOBSPLIT 29.40

DUMPOUTPUT 29.40

EMULATE 29.40

EOJATEOJ 29.41

EOJTOUT 29.41

ERRTRYCT 29.42

ESCAPE 29.42

EXPTABS 29.42

FCBLOAD 29.43

FFATBELT 29.43

FFATBOP 29.43

FFATEOJ 29.44

FFATSOJ 29.44

FILTER 29.44

FILTERTHRU 29.45

FLOWCTRL 29.45

FNAME 29.46

FOLDxx 29.46

FOLDACTION 29.46

FORMADJUST 29.47

FTPDATAWAIT 29.47

FTPDIR 29.47

AutoFTP 29.47

Autorouting 29.47

FTPDIROPTN 29.48

FTPDIRTYPE 29.48

FTPFAILTIME 29.48

FTPFILEID 29.48

AutoFTP 29.48

Autorouting 29.49


TECHNICAL REFERENCE MANUAL xxvii

FTPLISTOPTN 29.49

FTPPASSWORD 29.49

AutoFTP 29.49

Autorouting 29.50

FTPSRCENAMESIZE 29.50

FTPSTRU 29.50

FTPSUBDIR 29.51

FTPUSER 29.51

AutoFTP 29.51

Autorouting 29.51

GROUPNAME 29.51

HOST 29.52

HOSTBUG 29.52

HOSTNAME 29.52

HOSTPRIORITY 29.53

HSXOPTION 29.53

IBMIDMA 29.53

IBMISPEED 29.53

IBMISTATDISP 29.54

IBMOHWTOUT 29.54

IBMOSPEED 29.54

IBMPOLLTIME 29.54

ICLBINARY 29.55

ICMDxx 29.55

IFTYPE 29.55

IGNORECTRLCODES 29.55

IGNOREEOFERROR 29.56

IGNOREIMMDATA 29.56

IGNORESINGLESPACE 29.57

IMPACTPRINTER 29.57

INFOTIME 29.57

INTERRUPTIN 29.57

IOSPEED 29.58

IPADDR 29.58

IPADDRESS 29.58

JOBDESCRIPTION 29.58

JOBNAME 29.59

JOBSPLIT 29.59

LANADDR 29.59

LINEENDS 29.59

LINELENGTH 29.60

LINK 29.60

LINKFAILTIME 29.61

LPRBANNER 29.61

LPRCLASS 29.61

LPRFILE 29.61

LPRFORMAT 29.62

LPRHOST 29.62


xxviii TECHNICAL REFERENCE MANUAL

LPRJOB 29.62

LPRPARTYPE 29.62

LPRQUEUE 29.63

LPRSOURCE 29.63

LPRUSER 29.63

LPRWIDTH 29.64

LSUNIT 29.64

MAXFILETIME 29.64

MAXLINE 29.64

ICLI, OSI, PI 29.65

TCPI (LPR) 29.65

Other Input Modules 29.65

MAXPAGE 29.65

MAXWINDOW 29.65

MCRPCT 29.65

MCRPTIME 29.66

MFFAILTIME 29.66

MONITOR 29.66

NOCOUNT 29.66

NOLPRSESSION 29.67

OFFLINEATCR 29.67

OFFSETLEFT 29.67

ONCHERR 29.68

ONDATAERR 29.68

ONESECDIV 29.68

ONPKTERR 29.68

OSDMA 29.69

OSIBOARD 29.69

OSIDMA 29.69

OSISPEED 29.69

OSSPEED 29.70

OSTATDISP 29.70

OUTPUTCRLF 29.70

OUTPUTCSUM 29.70

OUTPUTFMT 29.70

OUTPUTPAGENOS 29.71

OUTPUTTOUT 29.71

PAGEL 29.71

PARITY 29.72

PASSALL 29.72

PASSCHANNELS 29.72

PASSCLR 29.73

PASSDCHK 29.73

PASSFCB 29.73

PASSFOLD 29.73

PASSTHRU 29.74

PASSUCSB 29.74

PCIINTROUTINE 29.74


TECHNICAL REFERENCE MANUAL xxix

PCISTATDISP 29.75

PDSIADDRESS 29.75

PDSILOADER 29.75

PDSILOADERSTOP 29.75

PDSILOOPBACK 29.76

PFCCxx 29.76

PIADDMODE 29.76

PIBIT 29.77

PICMDxx 29.77

PIDELAY 29.77

PIDMA 29.78

PIDUMP 29.78

PIFIXMODE 29.78

PIFROM7 29.78

PIFROMD7 29.78

PIINPAR 29.79

PILINE 29.79

PITO7 29.79

PISPEED 29.79

PORT 29.80

PORTIN 29.80

POSTLOADFILE 29.80

PRELOADFILE 29.80

PRINTER 29.81

PRINTERnnCQ 29.82

PRINTERFB 29.83

Timeout Period 29.83

PRINTERFALLBACK 29.83

PRINTERIDNO 29.83

PRINTERNAME 29.84

PRINTERNO 29.84

PRINTONFL 29.85

PRIORITYID 29.85

PROCESS5F 29.85

PROCESS5FMODE 29.85

PROMISCUOUS 29.86

PRSENSEMASK 29.86

PRTYIPADDR 29.86

PRTYIPADDRESS 29.87

PRTYPE 29.87

PRTYWAITTIME 29.87

PSMASK 29.88

PWRCHECK 29.88

QCOLON 29.88

QUEUENAME 29.88

QUICKACK 29.89

RECVTOUT 29.89

RELEASE 29.89


xxx TECHNICAL REFERENCE MANUAL

RXBINARY 29.90

SAVE 29.90

SCBBOARD 29.90

SENSE 29.90

SESSIONTOUT 29.90

SKIPSRCH 29.91

SNACCWxx 29.91

SNAME 29.91

SOFTTIMER 29.92

SOURCENAME 29.92

SPLITCCW 29.92

SPLITLFS 29.92

SPLITTIME 29.92

SPOOLFAILTIME 29.93

SRCEIPADDR 29.93

SRCEIPADDRESS 29.93

SRCELANADDR 29.93

STOPBITS 29.94

SHOWDUMPFILES 29.94

SHOWUNKNFILES 29.94

TABACTION 29.94

TCPFINDATA 29.95

TSTRUNCATE 29.95

UCSBLOAD 29.95

UNITNO 29.95

USELFS 29.95

USERNAME 29.96

VFUCH1LINE 29.96

VFULOAD 29.96

WAITBUSY 29.97

WIDTH 29.97

XBUFSIZE 29.97

XFERWAITTIME 29.97

XMITBLKSIZE 29.98

YDELAY 29.98

ZWWTIME 29.98

Translate Tables A.1

ASCII to EBCDIC 29.2

EBCDIC to ASCII 29.3

Arabisation 29.4

ASCII (PC Arabic Code Page 720) to EBCDIC 29.4

ASCII (ASMO 449+) to EBCDIC 29.4

ASCII (ASMO 708) to EBCDIC 29.5

ICL Arabic EBCDIC to EBCDIC 29.5

ICL Arabic EBCDIC to EBCDIC 29.6

EBCDIC Ident/Join Table - Right to Left for ALIS Default 29.7

EBCDIC Ident/Join Table - Right to Left 29.7


TECHNICAL REFERENCE MANUAL xxxi

EBCDIC Ident/Join Table - Left to Right 29.8

EBCDIC Number - Arabic to Hindu 29.8

EBCDIC Number - Hindu to Arabic 29.9

EBCDIC Number - No Conversion 29.9

EBCDIC to Start 29.10

EBCDIC to Middle 29.10

EBCDIC to End 29.11

EBCDIC Special 29.11

EBCDIC Double 29.12


CCW Action 29.13

IBMO 29.14

Immediate Command Corrective for Channel Tunnelled CCWs 29.14

Data Command Corrective for Channel Tunnelled CCWs 29.14

Command Action for Specifying Special Actions for Certain Commands 29.15

PCO 29.16

Immediate Command Corrective for Channel Tunnelled CCWs 29.16

Data Command Corrective for Channel Tunnelled CCWs 29.16

TCPI 29.17

PFCC 29.17

ASA A.18

SNA A.19

TCPO 29.20

CCW to ASA 29.20


xxxii TECHNICAL REFERENCE MANUAL

TECHNICAL REFERENCE MANUAL 1.1

Section 1 Foreword

This Technical Reference Manual is for those having to configure and support the following FunAsset TN Interfaces:

• TN3000• TN4000• TN5000• TN6000• TN8000

It is current with software versions 2.1, 3.1, 3.2, and 4.2 on MS-DOS systems, and version 1.0 on Windows NT/2000, and all the above TN Interfaces.

The specifications described within are subject to change without notice.

The availability of some features will depend upon system configuration. Contact your FunAsset dealer for details.

To configure and operate the software used by TN Interfaces an underlying knowledge of MS-DOS and/or Windows NT/2000 will be required. For details, refer to the MS-DOS User Guide or Windows NT/2000 User Guide.

The following information is included:

PAGE

Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2Manual Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4Hardware Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7

FOREWORD - CONTENT THE TN SERIES OF INTERFACES

1.2 TECHNICAL REFERENCE MANUAL

Content 1

The manual contains the following sections and appendices:

• Section 1, Foreword - Describes how to use this manual.• Section 2, Introduction - Provides an introduction to the hardware and

software that forms a TN Interface.• Section 3, Tasks - Details the Task applications that are used for

emulation, data conversion and additional data processing.• Section 4, Configuration Parameter Overview - Provides an overview of

the Configuration Parameters that are used to configure the modules that make up a Task.

• Section 5, Task Configuration Files - Details the Configuration Files that are used to apply Configuration Parameters to modules that make up a Task.

• Section 6, Multitask - Details the Multitask application that is used to manage multiple Tasks and the spooling software for TN Interfaces operating under MS-DOS.

• Section 7, System Fields - Details the System Fields that are used to pass information obtained from data around a TN Interface.

• Section 8, Common Module Overview - Details the Common Module that forms the standard linking mechanism between all modules that make up a Task.

• Section 9, Input Module Overview - Details the Input Modules that form the input part of a Task.

• Section 10, Output Module Overview - Details the Output Modules that form the output part of a Task.

• Section 11, PrintQ - Details the PrintQ Spooling System that is used by the TN4000 Interface.

• Section 12, SpoolQ - Details both the SpoolQ DOS and SpoolQ NT/2000 Spooling Systems that are used by the TN5000 and TN8000 Interfaces respectively.

• Section 13, Accounting - Details the Accounting facility available to SpoolQ Spooling Systems that enables specified job information to be written to Accounting Files.

• Section 14, Archiving - Details the Archiving facility available to SpoolQ Spooling Systems that enables jobs previously output to be stored for later use or retrieval.

• Section 15, Notification - Details the Notification facility available to the SpoolQ NT/2000 Spooling System that advises users when and where their job has been output.

• Section 16, Output Banners - Details the facility available to Spooling Systems that enables user defined Output Banners to be appended to jobs.

• Section 17, Performance Monitor - Details the Performance Monitor Output Module that is used to measure data flow rates sent from a Source to a TN Interface.

• Section 18, Arabisation - Details the Arabisation Input Extra Processing Module that interprets and converts incoming left to right ‘print’ data to right to left reading Arabic output.

• Section 19, Diagnostics - Details the Diagnostics Input Extra Processing Module that is used to capture incoming data for repeated output, so that problems with Destinations can be diagnosed.

• Section 20, AutoFilter - Details the AutoFilter Input Pre-processing Module that is used to identify and manipulate escape sequences found within incoming PDL data such as PCL.

THE TN SERIES OF INTERFACES FOREWORD - CONTENT


• Section 21, Banner Processing - Details the Banner Processing Output Pre-processing Module that is used to search for specified identification strings within incoming data and once located perform various actions.

• Section 22, AutoFTP - Details the AutoFTP facility, available to TN Interfaces operating the TCP/IP Input Module, that automatically retrieves jobs from a remote network server.

• Section 23, AutoRouting - Details the AutoRouting facility, available to TN Interfaces operating various Output Modules, that routes jobs automatically to Destinations, or sets System Field values based upon the job.

• Section 24, Dumping - Details the Dumping facility that enables operations performed by a Task (including AutoFilter and Banner Processing) to be monitored and the results, along with the data as it was received and output, written to a file, screen or printer.

• Section 25, Channel Tunnelling - Details the Channel Tunnel format that is used to identify and preserve IBM Channel data and associated CCWs, as well as how to pass IBM Channel data within a TN Interface.

• Section 26, Data Tunnelling - Details the Data Tunnel format that is used to identify and preserve non-standard characters found within certain data.

• Section 27, APO Unpacking - Details the APO Unpacking facility available to TN Interfaces operating the ICL OSLAN Input Module, that converts incoming APO data into ASCII before passing it to a post processing application and then outputting to a Destination.

• Section 28, Data Formats - Details the various data formats that a TN Interface is able to receive, process and output.

• Section 29, Configuration Parameters - Details the Configuration Parameters that are used to configure the modules that make up a Task.

• Appendix A, Translate Tables - Details the hexadecimal Translate Tables for all configurations.

FOREWORD - MANUAL CONVENTIONS THE TN SERIES OF INTERFACES


Manual Conventions 1

Certain conventions are used throughout this manual.

Wording 1

The following wording is used:

• Hexadecimal values are expressed as hex FF and hh.• Decimal values are expressed as nn.• The term “TN Interface” refers to the hardware and software that provides

connectivity between a Source and Destination.• The term “Spooling System” refers to the Input Tasks, Output Tasks and

the Spool Management or Monitoring Software as a whole.• The term “Source” is where data processed by a TN Interface is input

from. Examples include a mainframe, server, PC, modem, file, spool job, or another TN Interface.

• The term “Destination” is where data processed by a TN Interface is output to. Examples include a printer, server, PC, modem, file, spool job or another TN Interface.

• The term “Input Connection” refers to the hardware found within a TN Interface that provides a connection and receives data from an external Source.

• The term “Output Connection” refers to the hardware found within a TN Interface that provides a connection and outputs data to an external Destination.

• The term “data” refers to the ‘print’ information and commands passed from a Source, processed by a TN Interface, and output to a Destination.

• The term “form feed” will appear as FF, “carriage return” as CR, and “line feed” as LF.

Side Headings 1

The following indicators are placed in the left margin to indicate warnings, cautions, notes and examples:

WARNING: Warnings are used to identify where an action or omission may cause injury or permanent damage to personnel or equipment.

CAUTION: Cautions are used to identify where an action or omission may cause damage to equipment, software or data.

NOTE: Notes provide additional information or hints intended to assist in performing a task or understanding text.

EXAMPLE: Provides an example of what has just been described.

Configuration Parameter References 1

Section 29, Configuration Parameters should be consulted for further information about any Configuration Parameter referenced within this manual.

Figures 1

All figures detailing a Source, TN Interface and Destination within this manual, assume that the flow of data is from left to right.

SOURCE DESTINATIONTN INTERFACE

DATA FLOW

SERVER PRINTERLAN ADD=hhhhhhhhhhhh

SUPPORTED CONNECTION SUPPORTED CONNECTIONxxxx xxxx

THE TN SERIES OF INTERFACES FOREWORD - HARDWARE INTERFERENCE


Hardware Interference 1

WARNING: The hardware generates, uses, and can radiate radio frequency energy and if not installed and used in accordance with the manual may cause interference to radio communications. It has been tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such interference when operated in a commercial environment. Operation of this equipment in a residential area is likely to cause interference in which case the user at their own expense will be required to take whatever measures to correct the interference.

FOREWORD - RELATED PUBLICATIONS THE TN SERIES OF INTERFACES


Related Publications 1

In addition to this manual there are a number of publications that will also be of assistance when setting up, configuring and operating TN Interfaces.

FunAsset 1

The following FunAsset publications are available:

• PrintQ Operator Guide• SpoolQ DOS Operator Guide• SpoolQ NT/2000 Operator Guide• Hardware Reference Manual• Operator guides for each TN Interface

Copies can be obtained by contacting FunAsset Limited.

Operating Systems 1

Refer to the following documentation for full details about the operating systems used by TN Interfaces:

• MS-DOS User Guide• Windows NT/2000 User Guide

Source and Destination 1

Refer to the user guides provided with the Source and Destination, for further details about the command and syntax conventions used by devices connected to a TN Interface.

IBM Devices 1

Refer to the following documentation for full details of IBM device operation:

• IBM System/360 and System/370 Interface Channel to Control Unit Original Equipment Manufacturers’ Information - GA22-6974-7.

• IBM 3211 Printer, 3216 Interchangeable Train Cartridge, and 3811 Printer Control Unit Component Description and Operator’s Guide- GA24-3543-9.

• IBM 4245 Printer Model 1 Component Description and Operator’s Guide - GA33-1541-1.

TCP/IP Protocols 1

Refer to the following documentation for full details about TCP/IP protocols:

• IP protocol - RFC791• TCP protocol - RFC793• ICMP protocol - RFC792• FTP protocol - RFC959• Telnet protocol - RFC854• LPR protocol - RFC1179

These can be obtained on the Internet or from technical suppliers.

THE TN SERIES OF INTERFACES FOREWORD - FEEDBACK


Feedback 1

Whilst every care has been taken in preparing this manual, we understand that some errors may have occurred. We would appreciate any information or comments, and have provided a feedback form at the back of this manual. Please photocopy the form and send to the address shown on the reverse.

FOREWORD - FEEDBACK THE TN SERIES OF INTERFACES



Section 2 Introduction

Since the early days of computing there has often been a problem linking one type of device to another. For example, connecting a mainframe with an ICL OSLAN connection to a printer with an IBM Channel connection is not only physically impossible, but the data sent by one cannot be understood by the other. For this reason, establishments with computing facilities are often restricted to using the same manufacturer or connection type when connecting devices.

Traditionally TN Interfaces are designed to address this problem by providing a simple means of attaching an external Source device with one type of connection, to an external Destination device with another. The hardware that makes up the TN Interface provides a physical connection between the two, while the software interprets, processes and routes the data.

Data input from multiple Sources and output to multiple Destinations can also be processed by a single TN Interface using additional hardware and software.


PAGE

TN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2Supported Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6Version Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9Filename and Directory Name Considerations . . . . . . . . . . . . . . . . . . . 2.10Creating and Editing User Definable Files . . . . . . . . . . . . . . . . . . . . . . 2.11Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.13Year 2000 compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.15

INTRODUCTION - TN INTERFACES THE TN SERIES OF INTERFACES


TN Interfaces 2

Currently there are five types of TN Interface, each characterised by the number of Source and Destinations available, the PC specification, operating system and software supplied:

• TN3000• TN4000• TN5000• TN6000• TN8000

TN3000 2

The characteristics of a TN3000 Interface are as follows:

• Connectivity Single Source to a single Destination.• Hardware Floppy disk drive.

Input and Output Connections applicable to the type of connections found on external Source andDestination devices.

• Operating System MS-DOS.• Software Single Task application applicable to the Source and

Destination *.Task Configuration File associated with the Task.

NOTE: * Multiple Tasks can be used but each have to be operated independently.

TN4000 2


• Connectivity Single Source to multiple Destinations, or multipleSource to single Destination.

• Hardware Hard drive.Input and Output Connections applicable to the type of connections found on external Source andDestination devices.

• Operating System MS-DOS.• Software Task applications applicable to the Source and

Destinations.Task Configuration File associated with each Task.Multitask.PrintQ spool monitoring software.

TN5000 2


• Connectivity Multiple Source to multiple Destination.• Hardware Hard drive.

Input and Output Connections applicable to the type of connections found on external Source andDestination devices.

• Operating System MS-DOS.• Software Task applications applicable to the Source and

Destinations.Task Configuration File associated with each Task.Multitask.SpoolQ DOS spool management software.

THE TN SERIES OF INTERFACES INTRODUCTION - TN INTERFACES


TN6000 2


• Connectivity Single Source to single Destination.• Hardware Hard drive.

Input and Output Connections applicable to the typeof connections found on external Source andDestinations.

• Operating System Windows NT/2000.• Software Single Task application applicable to the Source and

Destination.*Task Configuration File associated with the Task.

NOTE: * Multiple Tasks can cooperate but each have to be operated independently.

TN8000 2


• Connectivity Multiple Source to multiple Destinations.• Hardware Hard drive.

Input and Output Connections applicable to the typeof connections found on external Source andDestinations.

• Operating System Windows NT/2000.• Software Task applications applicable to the Source and

Destinations.Task Configuration File associated with each Task.SpoolQ NT/2000 spool management software.

INTRODUCTION - SUPPORTED CONNECTIONS THE TN SERIES OF INTERFACES


Supported Connections 2

Each TN Interface supports a wide range of Input and Output Connections.

Input Connections 2

• Bull PDSI• Centronics• Dataproducts• File• IBM Channel• ICL OSLAN• ICL Peripheral Interface• PC Serial• PC Serial (Remote)• Siemens Type 2• TCP/IP• Windows Sockets

Output Connections 2

• Dataproducts• File• IBM Channel• PC Parallel Port (Dataproducts and Centronics)• PC Serial• PC Serial (Remote)• TCP/IP• Windows NT Printer• Windows Sockets

THE TN SERIES OF INTERFACES INTRODUCTION - HARDWARE


Hardware 2

Hardware that forms a TN Interface consists of a standard PC with optional eight bit ISA Input and Output Cards and standard Serial and Parallel Ports providing the physical connections to any external Source and Destinations. For some devices, an external box is also necessary to complete the connection.

Installation 2

For details about how to setup a TN Interface and install Input Cards, Output Cards and External Boxes, refer to the Hardware Reference Manual.

Specifications 2

For details of hardware specification, refer to the documentation provided with the PC, and the Hardware Reference Manual.

Health and Safety 2

TN Interfaces are CE certified and conform to the following:

• Electrical Safety BS5850, IEC 950.• EME 82/499/EEC, EN55022 and VDE0871 Class B.• UL1950 (for the United States and Canada).• Xerox Corporate Environment Health and Safety Standard (CEHSS) 2.2.0.

Maintenance 2

TN Interfaces are self-contained and require little maintenance.

For guidance on standard maintenance procedures, refer to the documentation provided with the PC and the Hardware Reference Manual.

INTRODUCTION - SOFTWARE THE TN SERIES OF INTERFACES


Software 2

TN Interfaces are supplied with software for system configuration, input and output data interpretation and processing, spooling, and other modules for additional data processing. The software provided depends upon the type of Source and Destinations used, whether spooling is required, and the level of additional data processing needed.

Installation 2

Software used by TN Interfaces is normally pre-installed.

For details about installing the spool management or monitoring software, refer to either the PrintQ Operator Guide, SpoolQ DOS Operator Guide, or SpoolQ NT/2000 Operator Guide.

Location 2

The location of all the software is dependent upon the TN Interface used.

TN3000 2

Software associated with the TN3000 Interface is located in the Root directory of the Master Setup floppy disk.

TN4000 2

Software associated with the TN4000 Interface is located on the hard drive in the PrintQ directory. By default this is C:\PRINTQ.

For further details about the files located within the PrintQ directory, refer to the PrintQ Operator Guide.

TN5000 2

Software associated with the TN5000 Interface is located on the hard drive in the SpoolQ directory. By default this is C:\SPOOLQ.

For further details about the files located within the SpoolQ directory, refer to the SpoolQ DOS Operator Guide.

TN6000 2

Software associated with the TN6000 Interface is located on the hard drive in the TN6000 directory. By default this is C:\TN6000.

TN8000 2

Software associated with the TN8000 Interface is located on the hard drive in the SpoolQ NT directory. By default this is C:\SpoolQ NT.

The SpoolQ NT directory holds the SpoolQ application along with each of the Tasks required by the TN Interface. The CONFIG directory within is where each of the Configuration Files are located.

For further details about the files located within the SpoolQ NT directory, refer to the SpoolQ NT/2000 Operator Guide.

Tasks 2

Tasks are applications that provide data interpretation, conversion, and other additional processing required by a TN Interface. They are made up of a combination of Input, Output, Pre-processing and Extra Processing Modules that are all managed by a Common Module.

Individual Tasks are provided for each combination of Source and Destination

THE TN SERIES OF INTERFACES INTRODUCTION - SOFTWARE


that data is passed between. The Input Module within a Task relates to the Source, while the Output Module relates to the Destination.

EXAMPLE: If a TN Interface provided the connectivity between a mainframe with an ICL OSLAN connection, and a printer with an IBM Channel connection, then a Task called ICLIIBMO.EXE would be required for processing the data passed between the two.

Operation 2

The Input Module of a Task emulates a Destination that the Source recognises and converts any data that it receives into a standard Internal Format. This is then converted by the Output Module to a format recognised by the Destination.

For details, see Section 3, Tasks.

Configuration 2

The modules that make up a Task are configured using Configuration Parameters.

For details, see Section 6, Configuration Parameter Overview.

Controlling and Monitoring 2

A Control Screen provides a user interface for each Task in operation. It displays configuration details, and communications messages, as well as providing a method for entering commands and controlling a Task.

Additional Processing 2

If required, additional data processing can be performed by many of the modules that make up a Task. This extra functionality is useful when further interpretation and processing is required for special data needs, or if certain information needs to be identified within the data.

The following Pre-processing and Extra Processing Modules can be incorporated within Tasks:

• Arabisation.• AutoFilter.• Banner Processing.• Diagnostics.

Certain Input and Output Modules, along with the Common Module, are also able to perform further additional processing functions. These include:

• AutoFTP.• AutoRouting.• APO Unpacking.• Channel Tunnelling.• Data Tunnelling.• Dumping.• Output Banners.

For details about each of these functions, refer to their appropriate sections.

Task Configuration Files 2

If changes are required to the standard values used by Configuration Parameters for a Task, a Task Configuration File will be needed to apply them.

For details, see Section 4, Task Configuration Files.

INTRODUCTION - SOFTWARE THE TN SERIES OF INTERFACES


Multitask 2

TN Interfaces operating under the MS-DOS operating system that use multiple Tasks, require an additional application called Multitask to manage them. Additionally, if a spool monitoring or management application is used under MS-DOS then this is also managed by it.

For details, see Section 5, Multitask.

Spooling Systems 2

The spool monitoring or management software available to certain TN Interfaces, are simple, yet powerful applications that allow data sent from a Source and received by a Task, to be monitored and/or managed as a separate job, before being passed to another Task and output to a Destination.

The Task used by the Spooling System to receive data from a Source and place it as a job in a queue within the spool monitoring or management software, is known as an Input Task. It is made up like any other Task but contains an Output Module applicable to the spool monitoring or management software in operation.

The Task used by the Spooling System that takes a job from a queue within the spool monitoring or management software and outputs it to a Destination, is known as an Output Task. Again this is made up like any other Task but contains an Input Module applicable to the spool monitoring or management software in operation.

Currently there are three versions of the software available:

• PrintQ - An MS-DOS application used by the TN4000 Interface that allows jobs received from multiple Input Tasks to be monitored before being passed to a single Output Task, or jobs received from a single Input Task to be output to multiple Output Tasks.

• SpoolQ DOS - An MS-DOS application used by the TN5000 Interface that allows jobs received from multiple Input Tasks to be monitored and managed before being passed to multiple Output Tasks.

• SpoolQ NT/2000 - A Windows NT/2000 application used by the TN8000 Interface that allows jobs received from multiple Input Tasks to be monitored and managed before being passed to multiple Output Tasks.

NOTE: The TN3000 and TN6000 Interfaces do not feature Spooling Systems because they are designed for single Source to single Destination setups that do not require special job monitoring and management to take place.

For details about the Spooling Systems available, see Section 11, PrintQ, and Section 12, SpoolQ.

THE TN SERIES OF INTERFACES INTRODUCTION - VERSION NUMBERS


Version Numbers 2

Tasks and each of their associated modules, Multitask and the spooling software all have version numbers that are displayed in the following form:

This is Version t.m Xn(PR-Y) of Module

For details on how to display the version number for each application, refer to the appropriate section within this manual.

MS-DOS 2

The breakdown of a version number for TN Interfaces operating under MS-DOS is as follows:

• t Type:2 = Single Source to single Destination setup.3 = Banner Processing is available.4 = Mouse driven.

• m 0 = Development.1 = Single program.2 = Multitasking.

• X Module version (A-Z).• n Bug fix number.• Y Progressive release version.• Module Name of module.

Windows NT/2000 2

The breakdown of a version number for TN Interfaces operating under Windows NT/2000 is as follows:

• t Master system version.• m Master system version.• X Module version (A-Z).• n Bug fix number.• (PR-Y) Progressive release version.• Module Name of module.

INTRODUCTION - FILENAME AND DIRECTORY NAME CONSIDERATIONS THE TN SERIES OF INTERFACES


Filename and Directory Name Considerations 2

When filenames and directory names are defined, it is important that the correct format is considered for the operating system used by the TN Interface, Source or Destination.

For full details about file and directory structure, refer to the user guides provided with the operating system in use.

MS-DOS 2

• Directory names Upto eight alphanumeric characters (no spaces),followed by upto three character alphanumericextension (no spaces).

• Filenames Upto eight alphanumeric characters (no spaces), followed by upto three character alphanumeric extension (no spaces).

Windows NT/2000 2

• Directory names Upto 255 characters, including spaces, but not \ / : * ? “ < >

• Filenames Upto 255 characters, including spaces, but not \ / : * ? “ < >. The end of the filename should includea . followed by at least one character.

CAUTION: All alpha characters used in a name will be treated as uppercase.

UNIX 2

• Directory names Upto 255 characters, including spaces, but not \ / : * ? “ < >

• Filenames Upto 255 characters, including spaces, but not \ / : * ? “ < >. The end of the filename should includea . followed by at least one character.

THE TN SERIES OF INTERFACES INTRODUCTION - CREATING AND EDITING USER DEFINABLE FILES


Creating and Editing User Definable Files 2

The following user definable files used by TN Interfaces will sometimes require editing or new ones may need to be created:

• Accounting Format Files (*.AFF).• AutoFilter Parameter Files (FILTER.xxx).• Banner Processing Parameter Files (BANNER.xxx).• IP Address Lookup Files (*.IPA).• MS-DOS system files:

CONFIG.SYSAUTOEXEC.BAT

• Multitask Launch File (RUN.BAT).• Output Banner Data Files (*.BAN).• SpoolQ NT/2000 Task Launch File (TASKFILE.BAT).• Task Configuration Files (*.BAT).

How these are created and edited will depend upon what operating system the TN Interface is running under.

CAUTION: When editing existing files, it is advised that a backup copy is made before any changes are made.

MS-DOS 2

Refer to the MS-DOS User Guide supplied with the TN Interface for a complete guide to operating system commands and syntax.

Creating 2

At the MS-DOS prompt, enter EDIT NAME.EXT (where NAME is the name of the file to be created and EXT is the extension). The MS-DOS text editor Edit is loaded with an empty file. Enter the required information and save the file.

For details about valid filename structure, refer to Filename and Directory Name Considerations, above.

Editing 2

Locate the user definable file that requires editing, make a copy of it, and at the MS-DOS prompt enter EDIT NAME.EXT (where NAME is the name of the file that requires amendment and EXT is the extension). The MS-DOS text editor Edit is loaded and the existing file details displayed. Make the required changes and save the file.

Windows NT/2000 2

Refer to the Windows NT/2000 User Guide for a complete guide to operating system commands and syntax.

Creating 2

Use Notepad or a similar text editor to create new user definable files. Enter the required information and save the file with a valid name and extension.

For details about valid filename structure, refer to Filename and Directory Name Considerations, above.

Editing 2

Locate the user definable file that requires editing, make a copy, and open in

INTRODUCTION - CREATING AND EDITING USER DEFINABLE FILES THE TN SERIES OF INTERFACES


Notepad or a similar text editor. Make the required changes and save the file.

THE TN SERIES OF INTERFACES INTRODUCTION - SHORTCUTS


Shortcuts 2

All files, applications and folders within Windows NT/2000 can have icons and name references created for them that are known as shortcuts. Once created a shortcut is depicted by a small arrow in the lower-left corner of the icon, and by default, the words “Shortcut to” prefixing the icon text.

Shortcuts allow users to open files and folders or load applications from a more convenient location such as the Windows Desktop. They do not actually change their location and act only as a “pointer” to the actual item they are associated with.

Shortcuts also allow additional files to be associated with them. These are actioned when the shortcut is opened or loaded. This facility is used by TN Interfaces operating Windows NT/2000 when associating a Task Configuration File with a Task. For details, see Section 5, Task Configuration Files - Associating with Tasks.

NOTE: Deleting a shortcut will not delete the original file, folder or application it is associated with.

For further details about shortcuts, refer to the Windows NT/2000 User Guide.

INTRODUCTION - DISK ACCESS ERRORS THE TN SERIES OF INTERFACES


Disk Access Errors 2

On occasion floppy disk and hard disk access errors may occur. If this happens refer to the MS-DOS User Guide or Windows NT/2000 User Guide for details about how to rectify such problems.

THE TN SERIES OF INTERFACES INTRODUCTION - YEAR 2000 COMPLIANCE


Year 2000 compliance 2

All TN Interfaces supplied with FunAsset hardware and software after September 1996 are year 2000 compliant. Performance nor functionality are affected and all conform with BSI DISC PD 2000-1.

TN Interfaces supplied prior to October 1996 are NOT year 2000 compliant. To resolve this issue, FunAsset can supply new PC base units and Input and Output Cards. The necessity to supply new cards is due to the higher clock speeds found on newer PCs.

NOTE: All upgrades must be supplied by FunAsset to maintain a supportable product.

To verify year 2000 compliance, refer to the Hardware Reference Manual.

INTRODUCTION - YEAR 2000 COMPLIANCE THE TN SERIES OF INTERFACES



Section 3 Tasks

This section details the Task applications that are used to control emulation, perform data conversion, and provide additional processing required by TN Interfaces.


PAGE

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2

Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3

Internal Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5

Task Names and Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7

Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8

Control Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9

Dump Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.14

Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.15

System Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.16

PRFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.17

PRTEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.18

Unloading and Loading the FunAsset Hardware Driver . . . . . . . . . . . . 3.19

Displaying Version Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.20

Exiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.21

TASKS - OVERVIEW THE TN SERIES OF INTERFACES


Overview 3

Tasks are applications that provide data interpretation, conversion, and other additional processing for TN Interfaces. For each combination of Source and Destination that the data passes between, an individual Task is provided.

A user interface called a Control Screen is provided for each Task to allow certain processes and configurations to be viewed as well as providing a method for entering commands to place the Task in Run mode (RUN), output a file (PRFILE), test the output (PRTEST), view version numbers (VERSION) and for TN Interfaces operating Windows NT/2000, loading and unloading the FunAsset Hardware Driver (LOADDRIVER and UNLOADDRIVER).

THE TN SERIES OF INTERFACES TASKS - STRUCTURE


Structure 3

Tasks are made up of a combination of modules (Fig. 3.1) that perform various operations required for the correct processing of the data that passes from Source to Destination.

Fig. 3.1Task structure

Standard modules include:

• Common.• Input.• Output.

Optional additional processing modules include:

• Input Pre-processing.• Input Extra Processing.• Output Pre-processing.

Common Module 3

The Common Module is the standard linking mechanism between all modules that make up a Task. It is used to perform the functions that are common to each of the other modules, as well as initialising, starting and monitoring each of them. The routines that are used for the Dumping facility are also handled by the Common Module.

For further details, see Section 8, Common Module Overview.

Input Module 3

The Input Module provides emulation and conversion of the incoming data received by a Task from a Source.

For further details about Input Modules, see Section 9, Input Module Overview.

Emulation 3

The purpose of the emulation part of the Input Module is to satisfy the Source that the Task associated with it, is a Destination that it would normally recognise.

Conversion 3

The data received by an Input Module is converted to a standard Internal Format and held in memory before being passed to the Input Extra Processing Module, Output Module or Output Pre-processing Module for further processing.

For further details, refer to Internal Format, below.

Output Module 3

The Output Module provides conversion and emulation, and allows data previously processed by the Input Module to be passed to a Destination.

For further details about Output Modules, see Section 10, Output Module Overview.

TASK

IBM 3211 DRIVER

INPUTPRE-PROCESSING

MODULE

INPUTMODULE

INPUTEXTRA PROCESSING

MODULE

COMMON MODULE

OUTPUTPRE-PROCESSING

MODULE

OUTPUTMODULE

TASKS - STRUCTURE THE TN SERIES OF INTERFACES


Conversion 3

The data held within memory in the Internal Format is converted to a format recognised by the Destination.

Emulation 3

The purpose of the emulation part of the Output Module is to satisfy the Destination that the Task associated with it, is a Source that it recognises. It also provides the mechanism by which the data is passed to the Destination.

Input Pre-processing Module 3

The Input Pre-processing Module is an optional additional module used to interpret and process the data received by a Task, before it is passed to the Input Module.

NOTE: Only one Input Pre-processing Module can be used within a Task.

Currently the only Input Pre-processing Module available is AutoFilter. For further details, see Section 20, AutoFilter.

Input Extra Processing Module 3

The Input Extra Processing Module is an optional additional module used to further interpret and process the data before it is sent to the Output Pre-processing Module or Output Module.

NOTE: Only one Input Extra Processing Module can be used within a Task.

Currently the Input Extra Processing Modules available are Arabisation and Diagnostics. For further details, see Section 18, Arabisation, and Section 19, Diagnostics.

Output Pre-processing Module 3

The Output Pre-processing Module is an optional additional module used to examine, identify and further process the data before it is sent to the Output Module.

NOTE: Only one Output Pre-processing Module can be used within a Task.

Currently the only Output Pre-processing Module available is Banner Processing. For further details, see Section 21, Banner Processing.

Further Additional Processing 3

Certain Input and Output Modules, along with the Common Module, are also able to perform further additional processing functions. These include:

• AutoFTP.• AutoRouting.• APO Unpacking.• Channel Tunnelling.• Data Tunnelling.• Dumping.• Output Banners.

For details about each of these additional functions, refer to their appropriate sections.

THE TN SERIES OF INTERFACES TASKS - INTERNAL FORMAT


Internal Format 3

All data received from a Source by a TN Interface is converted by the Input Module to an Internal Format. This allows the Output Module to convert the data to the format required by the Destination.

For further details, refer to Structure - Input Module - conversion, above.

Data in the Internal Format comes in three forms:

• Normal.• IBM Channel.• Binary.

Normal 3

Data in the Normal Internal Format is ‘print’ data, with a character set the same as the CHARSET parameter, and line movements held as counts.

IBM Channel 3

Data in the IBM Channel Internal Format is binary as received by the Input Module (straight off the channel for IBMI, unpacked by TCPI), with an unknown character set, and line movements as CCWs attached to the data.

Binary 3

Data in the Binary Internal Format is pure binary as received by the Input Module, with an unknown character set and no CCWs or line movements.

TASKS - TASK NAMES AND AVAILABILITY THE TN SERIES OF INTERFACES


Task Names and Availability 3

The Tasks that are available to a TN Interface will depend upon the connections used by the Source and Destinations that data is passed between.

The filename of the application is made up from the combined abbreviations given to the Input and Output Modules associated with the Source and Destination used:

INPUTOUTPUT.EXE

The following table details each of the connections available to Source and Destinations and the name of the Input and Output Modules associated with them to make up the filename.

* The value x represents the communications type.

EXAMPLE: If a TN Interface provided the connectivity between a mainframe with an ICL OSLAN connection (Source), and a printer with an IBM Channel connection (Destination), then a Task called ICLIIBMO.EXE would be required for processing the data passed between the two.

EXAMPLE: Similarly if data passed from a mainframe with an ICL OSLAN connection (Source) to a TN Interface operating SpoolQ (Destination), then a Task called ICLISQUO.EXE would be required. Another, called SQUIIBMO.EXE, would then also be necessary to pass the job from SpoolQ (Source) to a printer with an IBM Channel connection.

For further details about the Input and Output Modules available to Tasks, see Section 9, Input Module Overview, and Section 10, Output Module Overview.

Connection Input Output

Bull PDSI PDSIDataproducts / Centronics DPI DPODummy DI DOFile FILI FILOIBM Channel IBMI IBMOICL OSLAN ICLI / OSIICL OSLAN & TCP/IP NETIICL Peripheral Interface FPIPC Parallel Port PCOPC Serial Port PCI PCOPerformance Monitor PMONPrintQ SPLI SPLOSerial Remote SxRI* SxRO*Siemens Type 2 IBMISpoolQ SQUI SQUOTCP/IP TCPI TCPOTCP/IP Interface Bridge TIPOWindows NT Printer NTPOWindows Socket SKTI SKTO

THE TN SERIES OF INTERFACES TASKS - CONFIGURATION


Configuration 3

For a Task to operate in any sensible way, a set of Configuration Parameters are required to describe what needs to be done and how data should be processed (i.e. an IP address when using TCP/IP, or the character set of incoming data).

Tasks default each of the Configuration Parameters available to them to a standard value. However, if changes from these defaults are required then a Task Configuration File is needed.

For further details, see Section 4, Configuration Parameter Overview, and Section 5, Task Configuration Files.

TASKS - LOADING THE TN SERIES OF INTERFACES


Loading 3

A Task can be loaded like any other application within MS-DOS or Windows NT/2000. However, if multiple Tasks are used by a TN Interface certain conventions may need to be followed.

NOTE: When a Task is loaded it must be placed in RUN mode before emulation and processing of data can commence. For further details, refer to RUN mode, below.

For details about the location of Tasks for each TN Interface, see Section 2, Introduction - Software - Location.

How a Task is loaded will depend upon the TN Interface being used.

TN3000 3

A single Task used by a TN3000 Interface can be loaded from within MS-DOS by changing to the directory it is located in and entering its filename. It is not necessary to include the EXE extension.

NOTE: If the Configuration Parameter defaults used by a Task need to be changed, a Task Configuration File will normally be required to apply them. This file can also be used to load the Task. For further details, see Section 5, Task Configuration Files.

NOTE: If the multitasking application Multitask is used, a Task is loaded in the same manner as the TN4000 and TN5000 Interfaces.

TN4000 and TN5000 3

For TN Interfaces operating the multitasking application Multitask, an MS-DOS batch file, called by default, RUN.BAT, can be used to associate the filename of each Task with a task number. Multitask, which is also loaded from within this file, uses these to load the Tasks into their own areas of memory.

For further details, see Section 6, Multitask.

TN6000 3

A Task can be loaded from within Windows NT/2000 by locating it or an associated shortcut and double clicking it. For further details about shortcuts, see Section 2, Introduction - Shortcuts.

NOTE: If a Task Configuration File has not been associated with a Task, the following message will appear:

No Batch Parameter File - Continue?

Press Y (yes) to continue the operation (which will use the default values for the Configuration Parameters used by the Task), or N (no) to exit the Task.

TN8000 3

Tasks can be loaded on a TN8000 Interface by using the same method as described for the TN6000 Interface, or by using a Task Launch File called TASKFILE.BAT, that SpoolQ NT/2000 automatically reads when it is loaded.

For further details, see Section 12, SpoolQ - Task Launch File - TASKFILE.BAT.

THE TN SERIES OF INTERFACES TASKS - CONTROL SCREEN


Control Screen 3

A Control Screen (Fig. 3.2 and Fig. 3.3) provides a user interface for each Task that is loaded. It displays Input and Output Module configuration details, Output Module page and communications status, an activity indicator, as well as providing a method for entering commands.

Fig. 3.2Task Control Screen

(MS-DOS)

Fig. 3.3Task Control Screen(Windows NT/2000)

Content 3

A Control Screen is made up of the following components:

• Command Line.• Command Line Prompt.• Job Status.• Job Description.• Input Module Configuration. *• Output Module Configuration. *• Output Module Status. *• Trace.• Communications Status.• Page Status. *

NOTE: * Status and configuration messages are displayed in three forms:

• Yellow Normal.• Flashing Non fatal error encountered (Not used by TN Interfaces

operating under Windows NT/2000).

TASKS - CONTROL SCREEN THE TN SERIES OF INTERFACES


• Red Fatal error encountered - Stop the job, check output,resolve problem.

Command Line 3

The Command Line (Fig. 3.4) is used for entering commands.

Fig. 3.4Command Line

NOTE: The Command Line is inactive while the Task is in Run mode, if PRFILE or PRTEST are in operation, or the version numbers are being viewed.

Command Line Prompt 3

Prompts for active commands are provided at the Command Line Prompt (Fig. 3.5).

Fig. 3.5 tCommand Line Prompt

Job Status 3

Job Status (Fig. 3.6) informs the user what command has been or is being performed.

Fig. 3.6Job Status

Job Description 3

The Job Description (Fig. 3.7) displays the name of the Input Module and Output Module that makes up the Task.

Fig. 3.7Job Description

Input Module Configuration 3

The Control Screen displays configuration properties (Fig. 3.8) for the Input Module associated with the Task in operation. What is displayed will differ depending upon the Input Module and the Configuration Parameter values used.

Fig. 3.8Input Module Configuration

For a complete list of configuration properties that are displa

tn series of interfaces - funassetthe tn series of interfaces table of contents technical reference...

Documents