Intermec DCS 300 Technical Reference Manual
  1. Manuals
  2. Brands
  3. Intermec Manuals
  4. Server
  5. DCS 300
  6. Technical reference manual
Intermec DCS 300 Technical Reference Manual

Intermec DCS 300 Technical Reference Manual

Intermec dcs300 servers: reference guide
Hide thumbs Also See for DCS 300:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual
Technical Reference Manual
P/N 067717-001
DCS 300

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the DCS 300 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Intermec DCS 300

Summary of Contents for Intermec DCS 300

  • Page 1 Technical Reference Manual P/N 067717-001 DCS 300...
  • Page 2 The information contained herein is proprietary and is provided solely for the purpose of allowing customers to operate and/or service Intermec manufactured equipment and is not to be released, reproduced, or used for any other purpose without written permission of Intermec.

  • Page 3: Table Of Contents

    Sending Hot Standby Messages 1-16 Changing from a Nonactive State to an Active State 1-17 Active Recovery Mode 1-17 About DevComms 1-18 External Intermec Controllers 1-19 Interpreting ASCII Characters 1-19 Inserting and Deleting DLEs 1-20 Sending Transactions to a Device 1-20...
  • Page 4 DCS 300 Technical Reference Manual APPC NetComms 1-23 Learning About Transactions Understanding Transaction Structures 2-3 About the Transaction Header 2-3 Transaction Data 2-7 How Transactions Are Routed 2-7 Routing Transactions From Applications 2-8 Routing Transactions From Devices 2-10 How the DCS 300 Acknowledges Transactions 2-14 How Applications Acknowledge Transactions 2-14 How Applications Receive Transactions 2-15 How Applications Send Transactions 2-16...
  • Page 5 Communicating With TCP/IP Applications Overview 3-3 Opening Connections 3-4 Opening a Requester Connection 3-4 Send Connection From DCS 300 to Application 3-5 Receive Connection From Application to DCS 300 3-5 Using TCP/IP Sockets 3-7 Establishing a Requester Connection 3-7 About Message Boundaries 3-8 Sending Data 3-9 Receiving Data 3-9 Understanding NetAck and NetError 3-11...
  • Page 6 DCS 300 Technical Reference Manual Communicating With APPC Applications Learning About APPC Applications 4-3 Allocating APPC Conversations 4-4 Receive Applications 4-4 Send Applications 4-5 Interactive Applications 4-5 Batch Applications 4-5 Learning About APPC Verbs 4-7 IMS Applications 4-8 NetComm Pairs 4-8 Verb Flow Diagrams 4-8 Creating Script Files for Screen Mapping About Script Files 5-3...
  • Page 7 About Integer Variables 5-22 Hard-Coding Integer Variables 5-23 Performing Integer Math 5-23 Using Variables to Get String Length (StrLength) 5-24 Using Variables to Concatenate Strings 5-25 Converting Variables from String to Integer (StrToInt) 5-25 Converting Variables from Integer to String (IntToStr) 5-26 Using Variables to Do a String Search (StrSearch) 5-26 Copying a String or Integer Variable 5-27 Copying the Middle Part of a String (StrCopyMid) 5-27...
  • Page 8 DCS 300 Technical Reference Manual PUT_MAPPED_TRANS 5-49 PUT_TRANS_FIELD 5-50 SEARCH_SCREEN 5-51 SEND_MESSAGE 5-52 USER_INPUT 5-53 WAIT_FOR 5-54 WAIT_FOR_LABEL_POS 5-55 WAIT_FOR_POS 5-56 Reserved Words 5-57 Working With Host Systems Overview 6-3 Connecting to a Mainframe for 3270 TE 6-3 Connecting to an AS/400 for 5250 TE 6-4 Setting Up an SDLC Connection 6-5 Setting Up a Twinaxial Connection (6140, 5394, 5494) 6-9 Setting Up a Twinaxial Connection (6050, 266C) 6-14...
  • Page 9 Sample Programs About the Sample Programs 7-3 About the VT100 Screen Mapping Demonstration 7-4 Setting Up the Sample Host Application 7-4 Downloading the Template to the TRAKKER Antares Terminal 7-6 Running the VT100 Screen Mapping Demonstration 7-6 LOOPTCP Program 7-8 TCPAPP and PICKTCP Programs 7-9 WRITETCP Program 7-9 Utility Functions for TCP/IP Communication 7-10...
  • Page 10 DCS 300 Technical Reference Manual...

  • Page 11: Before You Begin

    Intermec support services organization. In the U.S. call 1-800-755-5505, and in Canada call 1-800-688-7043. Otherwise, refer to the Worldwide Sales & Service list that ships with this manual for the address and telephone number of your Intermec sales organization. Safety Summary Your safety is extremely important.

  • Page 12: About This Manual

    DCS 300 Technical Reference Manual Warnings, Cautions, and Notes The warnings, cautions, and notes in this manual use the following format. Caution A caution alerts you to an operating procedure, practice, condition, or statement that must be strictly observed to prevent equipment damage or destruction, or corruption or loss of data.
  • Page 13 Terminology You should be aware of how these terms are being used in this manual: Term Description Server Refers to the DCS 300. Data collection Refers to the JANUS devices, TRAKKER Antares terminals, and other device devices that communicate through the DCS 300. Also called a device. JANUS device Refers to all the readers and vehicle-mount computers (VMC) in the JANUS®...
  • Page 14 DCS 300 Technical Reference Manual Other Related Manuals You may need additional information when working with the DCS 300 in an Intermec data collection network. Please visit our web site at www.intermec.com to access many of our available manuals in PDF format. Your local Intermec representative or distributor can help you order printed versions of Intermec manuals.
  • Page 15 Communicating With TCP/IP Applications...
  • Page 16 DCS 300 Technical Reference Manual...

  • Page 17: Overview

    Communicating With TCP/IP Applications This chapter describes how the DCS 300 uses TCP/IP sockets to communicate with remote applications. Overview The DCS 300 communicates with remote applications using Transmission Control Protocol/Internet Protocol (TCP/IP) sockets. TCP provides a method for creating connection-oriented, error-free, full-duplex, byte-stream communications between two processes.

  • Page 18: Opening Connections

    DCS 300 Technical Reference Manual Figure 3-1: Typical Server/Client Configuration Using Sockets Host 1 Address Family: IP Network Address: 192.5.7.9 Address family The address family (or protocol family) determines the communications protocol used to deliver the transaction and the structure of the addresses used to represent the end point of the communication.

  • Page 19: Send Connection From Dcs 300 To Application

    Communicating With TCP/IP Applications The call sequence of a requester connection using a TCP/IP Berkeley socket interface is: socket() connect() When the receive requester connection is started, the application should send its name to the server on this connection. The server will respond in one of two ways: with a network acknowledgment (NetAck) if the channel is successfully created or with a network error (NetError) that closes the connection if the channel cannot be created.
  • Page 20 DCS 300 Technical Reference Manual Intermec recommends that the application open the receive connection first to ensure that when the application sends an Inter system transaction to the server to enter an active state, the application input channel has been created. If an application receives a NetError on the receive connection after sending its name to the server, the channel may not have been created.

  • Page 21: Using Tcp/Ip Sockets

    Using TCP/IP Sockets The DCS 300 uses the standard TCP/IP protocol implemented as stream sockets to communicate with remote systems. This section outlines some implementation details that are specific to TCP/IP. Most checks for return codes have been removed from the code samples.

  • Page 22: About Message Boundaries

    (excluding the 2-byte header) is in binary form and network byte order (high to low). Intermec recommends you use the functions provided in this section to convert these values correctly. For more help, see your library documentation.

  • Page 23: Sending Data

    Communicating With TCP/IP Applications Sending Data All data must be sent using the server’s message boundary system, including the application name, when initiating the receive requester connection. First, the length of the data is converted into network byte order and written to the socket. Second, the data is written to the socket.
  • Page 24 DCS 300 Technical Reference Manual A problem can occur if a recv() is done on an abnormally disconnected socket. If the socket is in Blocking mode when recv() is called, the call will block indefinitely. If the SO_KEEPALIVE option has been set on the socket, then a timeout will occur after 10 minutes or so, depending on your platform.

  • Page 25: Understanding Netack And Neterror

    Understanding NetAck and NetError The DCS 300 uses the network acknowledgment (NetAck) to inform the application that the data was received and processed successfully. A network error (NetError) is sent when a send or receive connection failed. On the send connection, NetAck means the data was written to the IPC channel. On the receive connection, NetAck means the IPC channel was created successfully.

  • Page 26: How The Dcs 300 Communicates With Applications

    DCS 300 Technical Reference Manual How the DCS 300 Communicates With Applications To use the NetComms, you must first configure the DCS 300 for TCP/IP communications. For help, see the DCS 300 User’s Manual. Applications acknowledge the server directly by placing data in an ACK transaction and by using the Inter system transaction to control their interactivity with the server.
  • Page 27 Figure 3-2: Server NetComms Communicating With Remote Applications Remote machine Local machine Communicating With TCP/IP Applications APP1 Network ACK/NAK tcprecvl tcpsendl APP1 APP2 DCS 300 APP2 Network Network ACK/NAK Receive 300R.015 3-13...

  • Page 28: About Transaction Routing In A Tcp/Ip Network

    DCS 300 Technical Reference Manual About Transaction Routing in a TCP/IP Network The applications you create to interact with the DCS 300 function as remote applications. Figure 3-3 illustrates the programming interface for these remote applications. When your application receives a message from the server, your application must perform these steps: 1.
  • Page 29 Communicating With TCP/IP Applications Figure 3-3: Programming Interface for Remote Applications to the Server Message Standby Handler File Receive LAN_APP AUX_Q Recv Send NetComm NetComm DCS 300 Local Area Network Network Network Connection Connection 300R.016 Remote Application LAN_APP 3-15...
  • Page 30 DCS 300 Technical Reference Manual Your applications will use TCP sockets to communicate with the server across a TCP/IP network. Figure 3-3 also shows two channels that the server sets up: Receive channel The low priority Receive channel handles unsolicited transactions from data collection devices and applications, and handles system transactions from applications.

  • Page 31: Communicating Using The Direct Tcp/Ip Socket Interface

    Communicating Using the Direct TCP/IP Socket Interface The direct TCP/IP socket interface allows non-TCP/IP devices to establish a TCP/IP socket connection to the host through the DCS 300. The Intermec devices that this interface supports are: JANUS 900 MHz RF devices JANUS 2.4 GHz RF devices that communicate using UDP Plus...
  • Page 32 DCS 300 Technical Reference Manual Figure 3-4: Direct TCP/IP Socket Interface 9181 Base Radio Unit TCP/IP Network 3-18 Readers (TCP/IP clients) DCS 300 Message Handler/ DevComm Network Connection Application 300R.018 Remote...

  • Page 33: Using The Direct Tcp/Ip Socket Interface

    Communicating With TCP/IP Applications Using the Direct TCP/IP Socket Interface The TCP/IP client opens a TCP/IP socket on the host. After the client opens the socket, it can send and receive data to and from the socket. The client can also request to close the socket.

  • Page 34: About The $Ipt Transaction Id

    DCS 300 Technical Reference Manual Host Requests Close TCP/IP Client OPEN -------------> <------------- DATA -------------> <------------- <------------- Client Requests Close TCP/IP Client OPEN -------------> <------------- DATA -------------> <------------- CLOSE ------------> About the $IPT Transaction ID $IPT is a special transaction ID that contains the protocol that allows JANUS RF devices and TRAKKER Antares terminals to communicate with the DCS 300 using the direct TCP/IP socket interface.

  • Page 35: Using The $Ipt Transaction Id

    Communicating With TCP/IP Applications Using the $IPT Transaction ID These are the formats of the different commands you use to establish a direct TCP/IP socket interface. The angle brackets (< >) around a parameter mean that the parameter is required, but they are shown for reference only. Do not type the angle brackets. The square brackets ([ ]) around each parameter mean that the parameter is optional, but they are shown for reference only.

  • Page 36: Format Of Data Packet Sent From A Terminal

    DCS 300 Technical Reference Manual Format of DATA Packet Sent From a Terminal $IPT,< command >< session >< data > where: command session data Format of DATA Packet Sent From the DCS 300 < command >< session >< data > where: command session...

  • Page 37: Format Of Close Packet Sent From The Dcs 300

    Communicating With TCP/IP Applications Format of CLOSE Packet Sent From the DCS 300 < command >< session >< errorcode >[e rrortext ]< NUL > where: command 0x05 session is the 1-byte session number (0x01 to 0xFF). errorcode is the 2-byte error number. This number can be any unsigned short integer in network byte order.
  • Page 38 DCS 300 Technical Reference Manual Understanding Error Codes (continued) Error 10032 10035 10036 10037 10038 10039 10040 10041 10042 10043 10044 10045 10046 10047 10048 10049 10050 10051 10052 10053 10054 10055 10056 10057 10058 10059 10060 10061 10062 10063 10064 3-24 Definition...

  • Page 39: Sample Program For Janus 900 Mhz Rf Devices

    10100 Sample Program for JANUS 900 MHz RF Devices Intermec has provided a sample program on the DCS 300 in the \USERDATA\EXAMPLES\DRECTDEV subdirectory. This program lets you test the direct TCP/IP socket interface between JANUS 900 MHz RF devices and the host. It lets you open sessions, close sessions, and send data in the upper half of the viewport.

  • Page 40: Running The Sample Program

    Sample Program for TRAKKER Antares UDP Plus Terminals Intermec has provided a sample program on the DCS 300 in the \USERDATA\EXAMPLES\DRECTDEV subdirectory. This program lets you test the direct TCP/IP socket interface between TRAKKER Antares UDP Plus terminals and the host.

  • Page 41: Running The Sample Program

    Communicating With TCP/IP Applications 4. Load TCPCLIEN.BIN on the terminal drive C. For help, see “Using the DCS 300 to Transfer Files” in Appendix B of the DCS 300 User’s Manual. Note: The TCPCLIEN.BIN file has been converted from an executable file to a binary file using the EXE2ABS.EXE utility that comes with the TRAKKER Antares Programmer’s Software Kit (PSK) toolkit.
  • Page 42 DCS 300 Technical Reference Manual DATA Packet Example >> 4,1,test data If the connection identified by the session ID 1 is successfully opened before you send this command, you will receive the same data from the remote echo server. These lines are displayed on your device: Receive data packet Receive same data...

  • Page 43: Using The Terminal Emulation Auto-Login Feature

    Communicating With TCP/IP Applications You cannot use the echo server for this test because the command string cannot contain more than 255 characters. Also, there is a different maximum packet size for different devices. Since the echo server echoes the same data it receives, it cannot send data greater than the size of the data that the device sent.

  • Page 44: Control Characters For Auto-Login Scripts

    DCS 300 Technical Reference Manual Control Characters for Auto-Login Scripts You can also include control characters in your auto-login script. The control character must be enclosed by < > in the AUTOLOG.SCR file. Note: For VT/ANSI terminal emulation, you can also use the corresponding hexadecimal value to represent the control character.

  • Page 45: Sample Auto-Login Scripts

    VT/ANSI Control Characters (continued) Control Character <EM> <ENQ> <EOT> <ESC> <ETB> <ETX> Sample Auto-Login Scripts Listed below are example auto-login scripts. You can use these scripts as they are or use them as the starting point for creating your own auto-login files. In Example 1, the HostName command in this script will match the host the user will access.
  • Page 46 DCS 300 Technical Reference Manual In Example 2, the Input and Send commands use input variables. Input commands require a prompt string followed by a comma and a variable name to store the string in. The InputHidden command will display a “*” in place of any characters typed by the user.
  • Page 47 In Example 4, a section for the host name BigHost is added to the beginning of the script. If the user logs into any host other than BigHost, the script will start at the HostName “*” line. This script allows for different processing on each host. Example 4: Auto-Login With Variable Processing Input “Enter user name”, username # prompt for user name InputHidden “Enter Password”, password # Prompt for password...
  • Page 48 DCS 300 Technical Reference Manual 3-34...

  • Page 49: Communicating With Appc Applications

    Communicating With APPC Applications...
  • Page 50 DCS 300 Technical Reference Manual...

  • Page 51: Learning About Appc Applications

    Communicating With APPC Applications This chapter introduces APPC applications and APPC verbs. Learning About APPC Applications You can use APPC applications to communicate between the DCS 300 and any other machine on an SNA network. Before you write APPC applications, you should have some familiarity with APPC/LU 6.2 because APPC applications use APPC/LU 6.2 verbs to communicate with the server.

  • Page 52: Allocating Appc Conversations

    DCS 300 Technical Reference Manual Allocating APPC Conversations This table shows the conversation parameters that are required for any APPC application communicating with the DCS 300. The next sections describe the requirements for receive, send, interactive, and batch applications. These parameters are specified in the MC_ALLOCATE verb.

  • Page 53: Send Applications

    Communicating With APPC Applications Send Applications A remote send application sends data to the DCS 300 and devices across a network using APPC verbs. The transaction packet for a remote application consists of a transaction header and a system transaction flag: The transaction header must contain a valid destination or transaction ID.
  • Page 54 DCS 300 Technical Reference Manual The batch application initiates communications using the MC_ALLOCATE verb. It issues MC_ALLOCATE with the TP name BATCH. The host application then sends the application name as it would to a send server. When you start the DCS 300, the batch NetComm sets up the file to transfer in a series of MC_SEND_DATA verbs with buffers up to 1120 bytes in size.

  • Page 55: Learning About Appc Verbs

    The server takes care of communications on its side, but you must make sure you build the APPC verbs into your applications to handle communications on the host side. Intermec recommends that you have some familiarity with the APPC/LU 6.2 protocol.

  • Page 56: Ims Applications

    DCS 300 Technical Reference Manual IMS Applications Older IMS applications, before version 4.0, do not support the MC_CONFIRMED or MC_SEND_ERROR verbs. Since IMS applications do not support these verbs, applications must send an acknowledge transaction back to partner programs by setting the acknowledge flag in the DCS 300’s transaction header to A.

  • Page 57: Host Receive Requester With A Dcs 300 Send Server

    Communicating With APPC Applications Host Receive Requester With a DCS 300 Send Server Figure 4-1 illustrates the flow of conversation between a host receive requester and a DCS 300 send server. Figure 4-1: Host Receive Requester Talking to a DCS 300 Send Server MC_DEALLOCATE MC_SEND_ERROR MC_CONFIRMED...
  • Page 58 DCS 300 Technical Reference Manual Figure 4-2 illustrates the flow of conversation between a DCS 300 send server and a remote receive requester. Figure 4-2: DCS 300 Send Server Talking to a Remote Receive Requester MC_DEALLOCATE MC_CONFIRMED MC_RECEIVE_&_WAIT 4-10 MC_SEND_ERROR PROGRAM ERROR PURGING START ERROR...
  • Page 59 Communicating With APPC Applications Figure 4-3 illustrates the verb flow and interaction between a DCS 300 send server NetComm and a host receive requester application. Figure 4-3: DCS 300 Send Server NetComm and Host Receive Requester Application Verb Flow Host Receive Requester State Reset Reset...

  • Page 60: Host Send Requester With A Dcs 300 Receive Server

    DCS 300 Technical Reference Manual Host Send Requester With a DCS 300 Receive Server Figure 4-4 illustrates the flow of conversation between a host send requester and a DCS 300 receive server. Figure 4-4: Host Send Requester Talking to a DCS 300 Receive Server MC_CONFIRMED MC_RECEIVE_&_WAIT 4-12...
  • Page 61 Communicating With APPC Applications Figure 4-5 illustrates the flow of conversation between a DCS 300 receive server and a host send requester. Figure 4-5: DCS 300 Receive Server Talking to a Host Send Requester MC_DEALLOCATE MC_SEND_ERROR MC_CONFIRMED START ERROR RECEIVE_ALLOCATE MC_RECEIVE_&_WAIT ERROR MC_CONFIRMED...
  • Page 62 DCS 300 Technical Reference Manual Figure 4-6 represents the verb flow and interaction between a DCS 300 receive server NetComm and a host send requester application. Figure 4-6: DCS 300 Receive Server NetComm and Host Send Requester Application Verb Flow State Reset Reset...

  • Page 63: Host Batch File Transfer Application With A Dcs 300 Batch File Transfer Netcomm

    Communicating With APPC Applications Host Batch File Transfer Application With a DCS 300 Batch File Transfer NetComm Figure 4-7 illustrates the flow of conversation between a host batch file transfer application and a DCS 300 batch file transfer NetComm. Figure 4-7: Host Batch File Transfer Application Talking to a DCS 300 Batch File Transfer NetComm MC_CONFIRMED MC_DEALLOCATE...
  • Page 64 DCS 300 Technical Reference Manual Figure 4-8 illustrates the flow of conversation between a DCS 300 batch file transfer NetComm and a remote batch file transfer application. Figure 4-8: DCS 300 Batch File Transfer NetComm Talking to a Remote Batch File Transfer Application MC_DEALLOCATE MC_CONFIRM...
  • Page 65 Communicating With APPC Applications Figure 4-9 represents the verb flow and interaction between a DCS 300 batch file transfer NetComm and a host batch file transfer application. Figure 4-9: DCS 300 Batch File Transfer NetComm and Host Batch File Transfer Application Verb Flow Host Batch File Transfer Application...

  • Page 66: Host Ims Receive Requester With A Dcs 300/Ims Send Server

    DCS 300 Technical Reference Manual Host IMS Receive Requester With a DCS 300/IMS Send Server Figure 4-10 illustrates the flow of conversation for a host IMS receive requester talking to a DCS 300/IMS send server. Figure 4-10: Host IMS Receive Requester Talking to a DCS 300/IMS Send Server MC_DEALLOCATE 4-18 ERROR...
  • Page 67 Communicating With APPC Applications Figure 4-11 illustrates the flow of conversation for a DCS 300/IMS send server talking to a remote IMS receive requester. Figure 4-11: DCS 300/IMS Send Server Talking to a Remote IMS Receive Requester MC_DEALLOCATE MC_SEND_ERROR START ERROR RECEIVE_ALLOCATE ERROR...
  • Page 68 DCS 300 Technical Reference Manual Figure 4-12 represents the verb flow and interaction between an IMS send server NetComm and a host IMS receive requester application. Figure 4-12: IMS Send Server NetComm and Host IMS Receive Requester Application Verb Flow State Reset Reset...

  • Page 69: Host Ims Send Requester With A Dcs 300/Ims Receive Server

    Communicating With APPC Applications Host IMS Send Requester With a DCS 300/IMS Receive Server Figure 4-13 illustrates the flow of conversation for a host IMS send requester talking to a DCS 300/IMS receive server. Figure 4-13: Host IMS Send Requester Talking to a DCS 300/IMS Receive Server MC_DEALLOCATE Figure 4-14 illustrates the flow of conversation for a DCS 300/IMS receive server talking to a remote IMS send requester.
  • Page 70 DCS 300 Technical Reference Manual Figure 4-15 represents the verb flow and interaction between a DCS 300/IMS receive server NetComm and a host IMS send requester application. Figure 4-15: DCS 300/IMS Receive Server NetComm and Host IMS Send Requester Application Verb Flow State Reset Reset...

  • Page 71: Host Ims Batch File Transfer Application With A Dcs 300/Ims Batch File Transfer Netcomm

    Communicating With APPC Applications Host IMS Batch File Transfer Application With a DCS 300/IMS Batch File Transfer NetComm Figure 4-16 illustrates the flow of conversation for a host IMS batch file transfer application talking to a DCS 300/IMS batch file transfer NetComm. Figure 4-16: Host IMS Batch File Transfer Application Talking to a DCS 300/IMS Batch File Transfer NetComm MC_CONFIRMED...
  • Page 72 DCS 300 Technical Reference Manual Figure 4-17 illustrates the flow of conversation for an IMS batch file transfer talking to a remote IMS batch file transfer. Figure 4-17: IMS Batch File Transfer Talking to a Remote IMS Batch File Transfer MC_DEALLOCATE MC_CONFIRM 4-24...
  • Page 73 Communicating With APPC Applications Figure 4-18 represents the verb flow and interaction between a DCS 300/IMS batch file transfer NetComm and a host IMS batch file transfer application. Figure 4-18: DCS 300/IMS Batch File Transfer NetComm and a Host IMS Batch File Transfer Application Verb Flow IMS Batch File State...
  • Page 74 DCS 300 Technical Reference Manual 4-26...

  • Page 75: Creating Script Files For Screen Mapping

    Creating Script Files for Screen Mapping...
  • Page 76 DCS 300 Technical Reference Manual...

  • Page 77: About Script Files

    Creating Script Files for Screen Mapping This chapter provides background technical information you may need to manually create or modify the script files that the DCS 300 uses for screen mapping. About Script Files Screen mapping lets you send screen transactions from data collection devices to host sessions.

  • Page 78: Using The Dcs 300 To Manually Create Script Files

    DCS 300 Technical Reference Manual Using the DCS 300 to Manually Create Script Files Script files map the transactions sent from the data collection device to the host application screens. The script files also contain instructions that tell the DCS 300 how to navigate within a host application screen.

  • Page 79: Creating A Screen Mapping Session

    Creating Script Files for Screen Mapping Creating a Screen Mapping Session 1. From the main menu, choose Screen Mapping. 2. Choose Sessions. The Screen Mapping List dialog box appears. 3. To create a new screen mapping session, choose Add. The Screen Mapping Session Definition dialog box appears.

  • Page 80: Creating A Standard Script File

    DCS 300 Technical Reference Manual Creating a Standard Script File The DCS 300 comes with a utility that writes the basic description of the screen to a script file. The utility identifies all the input fields in a field-formatted screen. When you are creating the script file, you will be working with the host window and the dialog box at the same time.
  • Page 81 Standard Script File (continued) Screen Prompt Please switch to the terminal emulator session A. To define a region, place the cursor at the beginning of the region and press PF2 to mark the beginning. Place the cursor at the end of the region and press PF3 to finish the description.

  • Page 82: Sample Screen And Script File

    DCS 300 Technical Reference Manual Sample Screen and Script File This section provides an example of how to use the screen dump utility. The example refers to this sample host application screen, Work Order Add, and the script file produced by the utility. 1/26/93 12:05:27 WORK ORDER ADD...
  • Page 83 Creating Script Files for Screen Mapping A script file based on the Work Order Add screen is shown below. # This is an unedited script file ::WO_ADD2 “RMWOMM02” >INPUT_FIELDS :Field1 :Field2 :Field3 :Field4 :Field5 :Field6 :Field7 :Field8 :Field9 :Field10 :Field11 :Field12 :Field13 :Field14...

  • Page 84: Editing Script Files

    Search the screen for a particular string. Test for specific conditions and take appropriate actions. Intermec recommends that the script contain these procedures in this order: _INIT This procedure contains instructions for initializing the server and logging in to the host application. The _INIT procedure should call the _MAIN procedure.

  • Page 85: Design Considerations

    Creating Script Files for Screen Mapping Design Considerations Before you edit a script, consider these design issues on data integrity, transaction mapping efficiency, logon security, keystroke strings, run-time variables, and timing. Data integrity A transaction from the DCS 300 must be acknowledged before another transaction can be sent.

  • Page 86: Practical Advice For Editing Script Files

    DCS 300 Technical Reference Manual Script variables You can specify a number of variables in a script that set various server operating parameters. Place the run-time variables at the top of the script file. For help, see “Using Script Variables” later in this chapter. For example: START_VARIABLES RETRY=NO NORESET...
  • Page 87 Creating Script Files for Screen Mapping 3. Rename input fields. To rename the first input field, erase Field1 and type in a new name. Field names can be up to 20 characters in length and they are not case sensitive. Note that fields are numbered sequentially as Field1, Field2, and so on, according to their order in the host application screen.

  • Page 88: Skeleton Script

    DCS 300 Technical Reference Manual Skeleton Script On the following pages is a skeleton script that you can use as a model for your own script. This script is the basic script file that the DCS 300 creates. START_VARIABLES # These values mean - # RETRY _- YES, NO or a number.

  • Page 89: Sample Script 1

    Skeleton Script (continued) END_IF END_LOOP END_PROC # This is the critical exit procedure which is executed if the EmComm # encounters an unrecoverable error but the system is still available. _CRIT_EXIT # Insert reinitialization here END_PROC Sample Script 1 START_VARIABLES # These values mean - # RETRY _- YES, NO or a number.
  • Page 90 DCS 300 Technical Reference Manual Sample Script 1 (continued) MAIN_MENU “AS/400 Main Menu” >INPUT_FIELDS :Field1 MRPS “MRPS 38-S” >INPUT_FIELDS :Field1 MENU_901 “MENU 901” >INPUT_FIELDS :Field1 WORKORDER_ADD “RMWOMM02” >INPUT_FIELDS :Field1 :Field2 :Field3 :Field4 >REGIONS :MESSAGE _INIT CURRENT_SCREEN SIGNON “Joe” RTAB “juki” HOME PAUSE 3000 “Mary”...
  • Page 91 Sample Script 1 (continued) _MAIN LOOP # Get the message from Server GET_DCM_TRANS # If the Server is stopping data collection perform this sequence IF_EXIT # Insert shutdown logic here “9999” FLDEXIT EXIT END_IF CURRENT_SCREEN MENU_901 IF TRANS :“WORK_ADD_TRX” IF_SCREEN :MENU_901 “915”...

  • Page 92: Sample Script 2

    DCS 300 Technical Reference Manual Sample Script 2 This sample script is provided on the left and a detailed description of what each line does is explained on the right. # This is the template ::SIGN_ON “Sign On” >INPUT_FIELDS :USER_ID :PASSWORD ::WO_ADD1 “RMWOMM01”...
  • Page 93 Sample Script 2 (continued) _MAIN # Loop until Server shuts down. LOOP GET_DCM_TRANS IF_EXIT “9999” FLDEXIT EXIT END_IF CURRENT_SCREEN WO_ADD1 PUT_MAPPED_TRANS ENTER CURRENT_SCREEN WO_ADD2 PUT_MAPPED_TRANS PUT_TRANS_FIELD 3 DUE_DATE PUT_TRANS_FIELD 3 CUR_POS PUT_TRANS_FIELD 3 CUR_POS ENTER Creating Script Files for Screen Mapping _MAIN is the primary procedure where transaction mapping occurs.
  • Page 94 DCS 300 Technical Reference Manual Sample Script 2 (continued) IF_REGION :ERR_MSG SEND_MESSAGE “Invalid data:” + CUR_POS LOG_ERROR “Invalid data in message” + ERR_MSG :DEFAULT # We’re going back to the initial screen # to add w/o’s. The W/O number of this # transaction is at the bottom of the # screen.

  • Page 95: Checking A Script File

    Checking a Script File When you finish editing the script file, the DCS 300 can check it for correct syntax, but it cannot check the logic. You need to develop your own procedure for checking logic. To check for correct syntax 1.

  • Page 96: About String Variables

    DCS 300 Technical Reference Manual About String Variables When you declare a string variable, you enter: STRING variablename [ = string ] where: variablename string Literal strings must be enclosed in quotation marks (“”). Field labels will yield the current content of the field. Region names will yield the current content of the region. Transaction field numbers will yield a string of the numerically ordered fields of the transaction.

  • Page 97: Hard-Coding Integer Variables

    Hard-Coding Integer Variables You can assign a hard-coded number to an integer variable. Syntax IntVar = integer | hard-coded number Usage The left-hand operand takes on the value of the right-hand operand. The right-hand operand can be either a hard-coded integer or another integer variable. Example IntVar = -1 IntVar1 = IntVar2...

  • Page 98: Using Variables To Get String Length (Strlength)

    DCS 300 Technical Reference Manual Using Variables to Get String Length (StrLength) You can use this syntax to get the length of any string variable, string literal, or transaction field. Syntax integername = StrLength string | integer where integername is the name of the integer variable. Examples LenStrLiteral = StrLength “abcdefghi”...

  • Page 99: Using Variables To Concatenate Strings

    Using Variables to Concatenate Strings You can use this syntax to concatenate the contents of all strings in order. Integer variables are converted to their ASCII equivalents. Syntax StrResult = [ string | integer ] [ + string | integer ] [ + string | integer ] Examples StrResult = “abc”...

  • Page 100: Converting Variables From Integer To String (Inttostr)

    DCS 300 Technical Reference Manual Converting Variables from Integer to String (IntToStr) You can use this syntax to convert a number into its equivalent ASCII representation. Syntax StrResult = IntToStr integer Examples StrResult = IntToStr IntVar Using Variables to Do a String Search (StrSearch) You can use this syntax to look for occurrences of substring string2 in string1.

  • Page 101: Copying A String Or Integer Variable

    Copying a String or Integer Variable You can use this syntax to copy the contents of the string on the right side of the equal sign into a string on the left side of the equal sign. If the target string already contains a string, that data is lost during the copy.

  • Page 102: Copying The Left Part Of A String (Strcopyleft)

    DCS 300 Technical Reference Manual Copying the Left Part of a String (StrCopyLeft) You can use this syntax to copy an integer number of characters from the start of the source string into the target string. Syntax StrTarget = StrCopyLeft StrSource integer Examples StrTarget = StrCopyLeft StrSource IntVariable...

  • Page 103: Trimming The Left Part Of A String (Strltrim)

    Trimming the Left Part of a String (StrLTrim) You can use this syntax to trim all matching characters from the left end of the source string and copy the result into the target string. The source string and the target string can be the same variable.

  • Page 104: Comparing Two Strings, Case-Sensitive (Strcomp)

    DCS 300 Technical Reference Manual Comparing Two Strings, Case-Sensitive (StrComp) You can use this syntax to compare two strings for equality. The comparison is performed on ASCII numeric values, on a byte by byte basis. See an ASCII code chart for details.

  • Page 105: Converting A String To Uppercase (Strupper)

    Converting a String to Uppercase (StrUpper) You can use this syntax to convert the entire source string to uppercase. The source string is not altered, but it can be used as the target string, if the source string is a string variable.

  • Page 106: Other Script Variables

    DCS 300 Technical Reference Manual Other Script Variables You may want to use these standard script variables when creating script files. Script Variable CONCAT_CHAR=c MNEMONIC=c NOBATCH NOMAP NORESET RETRY = YES or NO or N TIMEOUT=X VT_WAIT=X 5-32 Description Use the character “c” for SEND_MESSAGE concatenation instead of the default “+.”...

  • Page 107: Using Keystrokes

    Using Keystrokes A keystroke can be a mnemonic or a string. The table below lists the 3270 and 5250 keystroke mnemonics supported by the DCS 300. Attention Clear Cursor Down Cursor Left Cursor Right Cursor Up Delete Enter Erase EOF Field- Field+ Field Exit...

  • Page 108: Using Audit Files

    DCS 300 Technical Reference Manual Using Audit Files Script auditing lets you record bad transactions that occur at the script processing level. The DCS 300 writes both the transaction and the explanatory transaction string to the application audit file. Some of the fields in the transaction header and the transaction data are shown between quotation marks so you can see the ends of the fields.

  • Page 109: Script Calls

    Script Calls Script calls are commands or functions that you can use in screen mapping scripts. There are four types of script calls: Actions Keystrokes If-clauses Flow control commands This section provides this information for each call: Purpose Describes the purpose of the call and cites any requirements or limitations for its use.

  • Page 110: Break

    DCS 300 Technical Reference Manual BREAK Purpose This flow control call exits the DCS 300 out of a loop or procedure. Syntax BREAK Usage Use within a loop or procedure to have the server break execution. Example In an infinite loop, BREAK provides a conditional exit. In a procedure, BREAK provides a break in execution.

  • Page 111: Capture_Pos

    CAPTURE_POS Purpose This action call captures the current host screen cursor position when the command is executed. The command stores a single positional value, where row 1 column 1 has a positional value of 1 (1*1) and row 24 column 80 has a positional value of 1920 (24*80). It also captures the positional value (CAP_POS), row value (CAP_ROW), and column value (CAP_COL) when the command is executed.

  • Page 112: Exit

    DCS 300 Technical Reference Manual EXIT Purpose This action call exits the DCS 300 and disconnects it from the emulator session. No more script calls will be executed after this one. Syntax EXIT Usage Use EXIT after you have exited the host application and logged off the session. You can use EXIT when a server shutdown occurs or when an error occurs and you want to exit.

  • Page 113: Get_Dcm_Trans

    GET_DCM_TRANS Purpose This action call gets a transaction from the message handler. Syntax GET_DCM_TRANS Usage GET_DCM_TRANS will acknowledge the previous transaction before it can get a new transaction. It is assumed that the previous transaction was successfully delivered. Compare to ACK_MESSAGE, which acknowledges the current transaction without retrieving another one.

  • Page 114: If_Exit

    DCS 300 Technical Reference Manual IF_EXIT Purpose This if-clause tests to see if the DCS 300 is shutting down so that it can shut down the host application cleanly. Syntax IF_EXIT Usage IF_EXIT is usually performed after the server receives a data transaction. Multiple calls are allowed within IF_EXIT.

  • Page 115: If_ Integercomparison

    IF_ integercomparison Purpose This if-clause evaluates a logical integer expression and performs actions based on the outcome. You can only use a single operation. You cannot use compound logical operations. Syntax IF_ integercomparison :TRUE :FALSE END_IF Usage The integer comparisons that you can use are: ==, <, >, <=, and >=. You only need to define one of the conditional branch options.

  • Page 116: If_ String | Integer

    DCS 300 Technical Reference Manual IF_ string | integer Purpose This if-clause evaluates the string or integer and compares its value to the cases given. It then performs actions based on the value. Syntax IF_ string | integer :value1 :value2 :value n :DEFAULT END_IF...
  • Page 117 IF_ string | integer (continued) In this example, various actions are called based on the value of IntVar1. If the value of IntVar1 does not match any of the choices in the IF_ clauses, then the program continues after the END_IF line. IntVar1 = (5 * IntVar2) % 5 IF_ IntVar1 CALL _SUB1...

  • Page 118: If_Region

    DCS 300 Technical Reference Manual IF_REGION Purpose This if-clause tests the specified region for one of two conditions: If the region is defined with an explicit string, test for that string at the position for known errors or success transactions. If the region is defined with a position and length, test if any text appears in that region.

  • Page 119: If_Screen

    IF_SCREEN Purpose This if-clause tests the current presentation space to see whether it matches the specified screen description identifier. Syntax IF_SCREEN Usage Use IF_SCREEN if you are not completely sure where you are or if there is a chance for variation.

  • Page 120: If_Search

    DCS 300 Technical Reference Manual IF_SEARCH Purpose This if-clause tests the true/false state of the last search result of SEARCH_SCREEN. If the state is true, the last search for a string was successful. If the state is false, the search was unsuccessful.

  • Page 121: If_Trans

    IF_TRANS Purpose This if-clause tests the current transaction in memory for the transaction types (transaction IDs). Syntax IF_TRANS Usage Cases are transaction types enclosed in quotation marks. Multiple values are allowed within a case. Each :TRUE and :FALSE case must be preceded by a colon (:). The cases are not order dependent.

  • Page 122: Log_Error

    DCS 300 Technical Reference Manual LOG_ERROR Purpose This action call logs an error to the Status Monitor and it enables you to write meaningful error messages. Syntax LOG_ERROR string where: string Example LOG_ERROR LOOP Purpose This flow control call provides unconditional looping control. Syntax LOOP number where:...

  • Page 123: Pause

    PAUSE Purpose This action call specifies the time that the DCS 300 waits. Syntax PAUSE milliseconds where: milliseconds Usage You can use PAUSE if the server needs to wait for the host to go through a series of screen changes, or if you know that a host busy period will exceed the timeout period specified in the variable section of the script file.

  • Page 124: Put_Trans_Field

    DCS 300 Technical Reference Manual PUT_TRANS_FIELD Purpose This action call puts a specified transaction field into a specified host screen field. If the DCS 300 is provided with the starting character position and field length, it can also strip off a portion of a transaction field. Use CUR_POS or CAP_POS if you want the server to write the data to a cursor position.

  • Page 125: Search_Screen

    SEARCH_SCREEN Purpose This flow control call searches for a specific object, such as a region label or message string, on the current host screen from the cursor position to the last position of the screen. The object can be in a string, a region, or a transaction field. If the object is found, then the search state is true and the current cursor position is at the first character position of the found string on the host screen.

  • Page 126: Send_Message

    DCS 300 Technical Reference Manual SEND_MESSAGE Purpose This action call sends a string from a screen region or a user-defined message string to a destination defined in the GUI. It can also send label data to a printer using any printer control characters required to format and print the label.

  • Page 127: User_Input

    SEND_MESSAGE (continued) Example An example of sending a print format and label is shown below: SEND_MESSAGE SEND_MESSAGE SEND_MESSAGE SEND_MESSAGE SEND_MESSAGE USER_INPUT Purpose This action call frees the screen so that a user at the DCS 300 can input keystrokes directly to the host application screen. Syntax USER_INPUT [UNTIL= key [NOSEND]] [FOR= number-of-keystrokes ] where:...

  • Page 128: Wait_For

    DCS 300 Technical Reference Manual WAIT_FOR Purpose This action call waits for the host to send either the specified string as identified by the string parameter or the text that is contained in the specified transaction field. If the specified events do not occur within the time-out period, this command times out and returns.

  • Page 129: Wait_For_Label_Pos

    WAIT_FOR_LABEL_POS Purpose This action call waits for the host cursor to be at the beginning of the specified region as identified by the region label parameter. If the specified events do not occur within the time-out period, this command times out and returns. Syntax WAIT_FOR_LABEL_POS waitobject time-out where:...

  • Page 130: Wait_For_Pos

    DCS 300 Technical Reference Manual WAIT_FOR_POS Purpose This action call waits for the host cursor position to get to a specific row and column position on the host screen. If the specified events do not occur within the time-out period, this command times out and returns. Syntax WAIT_FOR_POS [ originposition ] destinationrow destinationcolumn time-out...

  • Page 131: Reserved Words

    Reserved Words This table lists all the words that the script uses. You cannot use these reserved words to name variables or your script will not work. ACK_MESSAGE ENTER ATTN ERS_EOF AUDIT EXIT BACKSP FALSE BREAK FILL_FIELD CALL FLDEXIT CAP_COL FLDMINUS CAP_POS FLDPLUS...
  • Page 132 DCS 300 Technical Reference Manual 5-58...

  • Page 133: Working With Host Systems

    Working With Host Systems...
  • Page 134 DCS 300 Technical Reference Manual...

  • Page 135: Overview

    This chapter provides guidelines for connecting to and working with various host systems. The chapter assumes you are familiar with the operating systems and conventions of your hosts. Overview The DCS 300 can connect with IBM-type hosts and communicate over SDLC, twinaxial, Ethernet, token ring, or coaxial networks.

  • Page 136: Connecting To An As/400 For 5250 Te

    The AS/400 allows you to enable autocreation, which allows the system to automatically configure the connections. Intermec highly recommends that you use autocreation to set up these connections, which is easier and faster. Note: Many of the commands mentioned in this section, such as DSPNETA, WRKLIND, WRKCTLD, CRTCTLAPPC, WRKDEVD, and CRTDEVAPPC are AS/400 command language (CL) commands.

  • Page 137: Setting Up An Sdlc Connection

    Setting Up an SDLC Connection When you connect the AS/400 and the DCS 300 with a 5250 link over an SDLC network, you need to create device descriptions on the AS/400 for the server and the devices attached to the server. To set up an SDLC connection 1.
  • Page 138 DCS 300 Technical Reference Manual 2. Use the WRKLIND command to display a list of all line descriptions in the system. Select and view the line description you will use. Choose a line with the line type *SDLC. Make a note of the line description name; you will need it later in this procedure.
  • Page 139 3. To view an APPC controller description on the AS/400, use the WRKCTLD command and choose your *APPC controller from the list. You can also use the CRTCTLAPPC command to create this controller description. Display Controller Description Controller description ..: Option .
  • Page 140 DCS 300 Technical Reference Manual 4. To view an APPC device description on the AS/400, use the WRKDEVD command and choose your *APPC device from the list. You can also use the CRTDEVAPPC command to create the APPC device. Device description ..: Option .

  • Page 141: Setting Up A Twinaxial Connection (6140, 5394, 5494)

    Setting Up a Twinaxial Connection (6140, 5394, 5494) This section describes how to configure a connection between an AS/400 and a DCS 300 through a 6140, 5394, or 5494 twinaxial controller. If you enable autocreation on the AS/400, the AS/400 can autocreate the controller and device entries for you. Then you can study the procedure to understand what the AS/400 autocreated.
  • Page 142 DCS 300 Technical Reference Manual 2. Use the WRKLIND command to display a list of all line descriptions in the system. Select and view the line description you will use. Choose a line with the line type *TDLC. Make a note of the line description name; you will need it later in this procedure.
  • Page 143 Note: This example shows connection to the AS/400 via a 6140 controller. Other IBM twinaxial controllers can be used, such as the 5394 or 5494. 4. To display or create a device description for the physical device on the AS/400, use the WRKDEVD command.
  • Page 144 DCS 300 Technical Reference Manual Controller description Option Category of controller Link type Online at IPL Character code Maximum frame size Remote network identifier Remote control point name Data link role Station address Text Description of Pertinent Controller Description Parameters AS/400 Parameter Description and Value Controller...
  • Page 145 6. To view an APPC device description on the AS/400, use the WRKDEVD command and choose your *APPC device from the list. You can also use the CRTDEVAPPC command to create the APPC device. Device description Option Category of device Remote location name Online at IPL Local location name...

  • Page 146: Setting Up A Twinaxial Connection (6050, 266C)

    DCS 300 Technical Reference Manual Setting Up a Twinaxial Connection (6050, 266C) This section describes how to configure a connection between an AS/400 and a DCS 300 through a 6050 or 266C twinaxial controller. If you enable autocreation on the AS/400, the AS/400 can autocreate the controller and device entries for you.
  • Page 147 2. Use the WRKLIND command to display a list of all line descriptions in the system. Select and view the line description you will use. Choose a line with the line type *TDLC. Make a note of the line description name; you will need it later in this procedure.
  • Page 148 DCS 300 Technical Reference Manual 3. To view the workstation controller, use the WRKCTLD command. To create a workstation controller description, use the CRTCTLLWS command. Controller description Option Category of controller Controller type Controller model Resource name Online at IPL TDLC line Auto-configure controller Text...
  • Page 149 5. To view an APPC controller description on the AS/400, use the WRKCTLD command and choose your *APPC controller from the list. You can also use the CRTCTLAPPC command to create this controller description. AS/400 CONTROLLER DESCRIPTION Controller description Option Category of controller Link type Online at IPL...
  • Page 150 DCS 300 Technical Reference Manual Description of Pertinent Controller Description Parameters AS/400 Parameter Description and Value Controller Enter the controller description name you description created in Step 3. Link type The type of network connection this controller description will use: *TDLC. Switched line list or Line description name(s) that this controller Active switched line...
  • Page 151 6. To view an APPC device description on the AS/400, use the WRKDEVD command and choose your *APPC device from the list. You can also use the CRTDEVAPPC command to create the APPC device. Device description Option Category of device Automatically created Remote location name Online at IPL...

  • Page 152: Setting Up An Ethernet Connection

    If you enable autocreation on the AS/400, the AS/400 can autocreate both the controller and the attached device for a 5250 link over an Ethernet network. This section describes the manual procedure, although Intermec recommends autocreation. To set up an Ethernet connection between an AS/400 and a DCS 300 1.
  • Page 153 2. Use the WRKLIND command to display a list of all line descriptions in the system. Select and view the line description you will use. Choose a line with the line type *ELAN. Make a note of the line description name; you will need it later in this procedure.
  • Page 154 DCS 300 Technical Reference Manual 3. To view an APPC controller description on the AS/400, use the WRKCTLD command and choose your *APPC controller from the list. You can also use the CRTCTLAPPC command to create this controller description. Page 1... Display Controller Description Controller description .
  • Page 155 Description of Pertinent Controller Description Parameters AS/400 Parameter Description and Value Controller Enter the node name of the DCS 300. The description default is ACCNET. Link type The type of network connection this controller description will use: *LAN. Switched line list or Line description name(s) that this controller Active switched line attaches to.
  • Page 156 DCS 300 Technical Reference Manual 4. To view an APPC device description on the AS/400, use the WRKDEVD command and choose your *APPC device from the list. You can also use the CRTDEVAPPC command to create the APPC device. Display Device Description Device description .

  • Page 157: Setting Up A Token Ring Connection

    Setting Up a Token Ring Connection This section describes how to configure a token ring connection between an AS/400 and a DCS 300. You will make four entries on the AS/400. These entries are for the line, server, device, and subsystem descriptions. To set up a token ring connection between an AS/400 and a DCS 300 1.
  • Page 158 DCS 300 Technical Reference Manual 2. Use the WRKLIND command to display a list of all line descriptions in the system. Select and view the line description you will use. Choose a line with the line type *TRLAN. Make a note of the line description name; you will need it later in this procedure.
  • Page 159 Description of a Pertinent Line Description Parameter AS/400 Parameter Description and Value Local adapter The AS/400’s MAC address in token ring address format. 3. To view an APPC controller description on the AS/400, use the WRKCTLD command and choose your *APPC controller from the list. You can also use the CRTCTLAPPC command to create this controller description.
  • Page 160 DCS 300 Technical Reference Manual Page 2... Controller description ..: Option ....: Category of controller ..: LAN DSAP .
  • Page 161 AS/400 Parameter Description and Value LAN remote adapter The MAC address of the DCS 300 in token address ring format. Specify this address in token ring format even if the server is on an Ethernet network. To convert an address from Ethernet format to token ring format, you byte-flip the address.

  • Page 162: Understanding Lan Adapter Address Formats

    DCS 300 Technical Reference Manual Description of Pertinent APPC Device Description Parameters AS/400 Parameter Description and Value Device description Name of the device description. This name will appear on any AS/400 device list, such as the one displayed with the WRKDEVD command.

  • Page 163: Setting The Lan Remote Adapter Address On The As/400

    Setting the LAN Remote Adapter Address on the AS/400 The LAN remote adapter address is the 48-bit address of the network adapter card installed in the DCS 300. The address you specify for the LAN remote adapter address depends on whether the server and AS/400 are on the same type of network: If the server and AS/400 are on the same type of network, you specify the adapter card address in the correct order.
  • Page 164 DCS 300 Technical Reference Manual As a shortcut, you can use the next table to byte-flip addresses. The table shows what each hexadecimal digit, from 0 to F, becomes when you perform Steps 1 to 3 (from Figure 6-1). Then you must perform Step 4. Figure 6-1: Process of Byte-Flipping One Byte in an Address 0 0 1 0 0 1 0 1...

  • Page 165: Testing The As/400 Connection

    Testing the AS/400 Connection You should be able to create a 5250 terminal session on the DCS 300. Using a 5250 terminal session on the server is the best way to verify your AS/400 connectivity. Configure the server for a 5250 terminal session, save and activate your run-time configuration, and reboot the server.

  • Page 166: Configuring The Virtual Devices For 5250 Te

    DCS 300 Technical Reference Manual Configuring the Virtual Devices for 5250 TE The AS/400 creates virtual devices for each terminal that starts a session to the AS/400. If the configuration of the AS/400 does not allow for the autocreation of these virtual device descriptions, you must create them manually, as described next.

  • Page 167: Remotely Connecting The Dcs 300 To An As/400

    Remotely Connecting the DCS 300 to an AS/400 You can connect the DCS 300 to an AS/400 through a remote 5394 controller or 5494 controller. The next sections describe how to configure the connection by entering commands on the AS/400. Using a 5394 Controller The 5394 connection is identical to a local twinaxial connection.

  • Page 168: Using A 5494 Controller

    DCS 300 Technical Reference Manual To create an APPC controller description on the AS/400 Type this AS/400 CL command on one line: CRTCTLAPPC CTLD(ACCNET) LINKTYPE(*TDLC) LINE(QTDL601100) RMTCPNAME(ACCNET) STNADR(03) To create an APPC device description on the AS/400 Type this AS/400 CL command on one line: CRTDEVAPPC DEVD(ACCNET) RMTLOCNAME(ACC-NET) CTL(ACCNET) Note: You could create the 5150 device description (with a DEVD that is different than...

  • Page 169: Receiving A Cpf4128 Error

    To add an entry to the QAPPNRMT configuration list on the AS/400 1. Type the AS/400 CL command WRKCFGL and either access or create the QAPPNRMT configuration list. 2. Enter the information shown below in bold: Configuration list ..: Configuration list type .

  • Page 170: Creating The #Accnet Mode On An As/400

    DCS 300 Technical Reference Manual Creating the #ACCNET Mode on an AS/400 You can create the #ACCNET mode on the AS/400. This mode supports up to 128 sessions. The command to create a mode is CRTMODD, and the command to work with mode descriptions is WRKMODD.
  • Page 171 4. Study this example and then perform Step 5. File ..: QPDSPFD Control ..______ Find ..______________________________ Display File Description File ..... . : FILE Library .
  • Page 172 DCS 300 Technical Reference Manual End session with host ... . : ENDSSNHOST Special Host Application ... : SPCHOSTAPP Initialize Self .

  • Page 173: Configuring The Terminal Over The Network

    Configuring the Terminal Over the Network You can remotely configure a TRAKKER Antares terminal using either of these methods: Send a command from the DCS 300. Send a command from an application on the host computer. You can continue running an application on a TRAKKER Antares terminal while configuring the terminal from the server or host computer.

  • Page 174: Configuring The Terminal From The Host Computer

    DCS 300 Technical Reference Manual 4. Repeat Step 3 to add another reader or configuration command, or choose OK. 5. Choose Download to download the commands and change the run-time configuration of the terminals selected. When you remotely configure the terminal, the commands change the terminal’s run-time configuration.
  • Page 175 To set up the application Write a TCP/IP or APPC application that can communicate with the server and send transactions to the TRAKKER Antares terminal. For help, see Chapter 3, “Communicating With TCP/IP Applications” or Chapter 4, “Communicating With APPC Applications.” The application must be able to send and receive transactions that are formatted as shown in the next table.
  • Page 176 DCS 300 Technical Reference Manual Setting Each Transaction Field When Using TMF to Configure a Terminal Over the Network (continued) Field Data (continued) Configuration command Example 1 In the host application, you want to get the current values of three configuration commands from the terminal.
  • Page 177 Example 2 In the host application, you want to set the values for two configuration commands on the terminal. Send this transaction from the host application: CS$+BV4DF30 Note: The transaction header field is not included in this example. where: is a TMF Configuration Set request. is the Change Configuration reader command.
  • Page 178 DCS 300 Technical Reference Manual 6-46...

  • Page 179: Sample Programs

    Sample Programs...
  • Page 180 DCS 300 Technical Reference Manual...

  • Page 181: About The Sample Programs

    This chapter describes the sample programs that are included with your DCS 300. About the Sample Programs These sample programs are included on your DCS 300. VT100 Screen Mapping Demonstration LOOPTCP TCPAPP and PICKTCP WRITETCP Utility Functions for TCP/IP Communication 0200 ECHO Program WAITFOR Screen Mapping Demonstration Sample Programs...

  • Page 182: About The Vt100 Screen Mapping Demonstration

    DCS 300 Technical Reference Manual About the VT100 Screen Mapping Demonstration On the DCS 300, you can run a VT100 screen mapping demonstration without a physical connection to an external host. This demonstration comprises three parts: A VT/ANSI sample host application that runs locally on the server using a local Telnet connection (\NEXTGEN\DEMOHOST.EXE).
  • Page 183 2. Create a VT100 terminal session. a. From the main menu, choose Terminal Sessions and then choose Host Connection. The Terminal Session List dialog box appears. b. Choose VT/ANSI. The VT/ANSI Terminal Session Definition dialog box appears. c. In the Name field, enter a meaningful name for the terminal session. d.

  • Page 184: Downloading The Template To The Trakker Antares Terminal

    To download the template 1. Add the UDP Plus Network and identify the UDP Plus (TRAKKER Antares) terminal. For help, see Chapter 3, “Connecting to the Intermec RF Network” in the DCS 300 User’s Manual. 2. Download the template to the terminal.
  • Page 185 Once the sample host application is started, it functions as if it were on a remote host. You can scan or enter data for each field into the TRAKKER Antares terminal screen. On the next page are some sample bar codes. Scan one of the bar codes for each of the fields.

  • Page 186: Looptcp Program

    DCS 300 Technical Reference Manual LOOPTCP Program LOOPTCP is a sample DCS 300 TCP/IP requester program. It uses TCP/IP sockets to communicate with the server TCP/IP NetCommss. This program acts as an echo server; that is, any transaction that is received from the server is acknowledged with the data that was sent to LOOPTCP.

  • Page 187: Tcpapp And Picktcp Programs

    TCPAPP and PICKTCP Programs TCPAPP and PICKTCP act as a sample order picking application that demonstrates the DCS 300 NetComm communication: • TCPAPP is a DOS-based program that communicates with host applications using the Novell LAN Workplace TCP/IP protocol. • PICKTCP is a server host application that provides order details based on the order number from TCPAPP.

  • Page 188: Utility Functions For Tcp/Ip Communication

    DCS 300 Technical Reference Manual Utility Functions for TCP/IP Communication This section lists the example utility functions for TCP/IP communication with the DCS 300 via TCP/IP using Novell’s LAN WorkPlace. These are high level functions you may use to communicate with the server. This table lists the related files from the \USERDATA\EXAMPLES\TCPIP directory: Filename COMFUNCT.C...
  • Page 189 This table lists the related files from the \USERDATA\EXAMPLES\APPC\AS400 directory: Filename Description O200ECHO.CLP Interactive CLP to prompt for remote location and queue name O200ECHO.DSP Display file for O200ECHO.CLP and O200ECH3.CLP O200ECHO.ICF ICF file for communications to O200 Send Server program O200ECHO.RPG RPG loopback program O200ECH2.CLP...

  • Page 190: Wait_For Commands Screen Mapping Demonstration

    DCS 300 Technical Reference Manual WAIT_FOR Commands Screen Mapping Demonstration This program demonstrates the WAIT_FOR commands. In VT/ANSI screen mapping, you cannot automatically position the host cursor to the host screen field. However, you can program the script to wait until the cursor is at the field using the WAIT_FOR commands.
  • Page 191 WAIT_FOR Commands Screen Mapping Demonstration (continued) >REGIONS :TRX_COMPLETE "Transaction completed" :DUPLICATE "APP-19216" :BAD_EXP "Expenditure" :BAD_DATE "Date format" :PARTIAL "This is a" :TASK_NUM "TASK NUMBER" :TOO_MANY_DIGITS "Too many" :BAD_FORMAT "Format is" :RC_FIELD "Field must be entered" #### # Procedures #### #### # Startup procedure #### _INIT...
  • Page 192 DCS 300 Technical Reference Manual WAIT_FOR Commands Screen Mapping Demonstration (continued) :DEFAULT LOG_ERROR "Invalid login for Oracle mapping session, exiting" EXIT END_IF ###Get to the timecard screen "\NTE" ###Wait 30 seconds for host cursor to be at row 3 column 16 WAIT_FOR_POS 3 16 30000 IF_SCREEN :TIMECARD...
  • Page 193 WAIT_FOR Commands Screen Mapping Demonstration (continued) _TCARD_TX_LOOP IF_SCREEN :TIMECARD CURRENT_SCREEN TIMECARD PAGEDN PUT_TRANS_FIELD 1 DATE ###Check for success of implied WAIT_FOR_LABEL_POS in PUT_TRANS_FIELD IF_WAIT :TRUE SEND_MESSAGE "Implicit WAIT_FOR_LABEL_POS DATE completed successfully” SRC :FALSE SEND_MESSAGE "Implicit WAIT_FOR_LABEL_POS DATE timed-out" SRC END_IF RTAB IF_REGION :BAD_DATE...
  • Page 194 DCS 300 Technical Reference Manual WAIT_FOR Commands Screen Mapping Demonstration (continued) IF_REGION :TOO_MANY_DIGITS "\RE" PAGEUP BREAK :BAD_FORMAT "\RE" PAGEUP BREAK END_IF "\FD" PUT_TRANS_FIELD 4 PROJECT RTAB IF_REGION :PARTIAL "\RE" PAGEUP BREAK :RC_FIELD "\RE" PAGEUP BREAK END_IF PUT_TRANS_FIELD 5 TASK RTAB RTAB PAGEUP SEND_MESSAGE "Finished processing timecard transaction"...

  • Page 195: Index

    Index...
  • Page 196 DCS 300 Technical Reference Manual...
  • Page 197 Symbols #ACCNET, See ACCNET mode #INTER, See INTER mode $IPT transaction ID, 3-20 format of CLOSE packet, 3-23 format of DATA packet, 3-23 format of OPEN packet, 3-21 format of OPEN_ACK packet, 3-21 format of OPEN_NAK packet, 3-21 using, 3-21 $NGCFGRSP transaction ID for configuring terminals, 6-42 >...
  • Page 198 DCS 300 Technical Reference Manual AS/400, CL commands (continued) CRTDEVAPPC, 6-36 CRTDEVDSP, 6-35 CRTMODD, 6-38 DSPNETA, 6-5, 6-9, 6-14, 6-20, 6-25 WRKCFGL, 6-37 WRKCTLD, 6-12, 6-22, 6-27 WRKDEVD, 6-8, 6-13, 6-19, 6-24, 6-29 WRKLIND, 6-6, 6-10, 6-15, 6-21, 6-26 WRKMODD, 6-38 controller description, 6-12, 6-18, 6-23, 6-28 creating ACCNET mode, 6-38 creating APPC device descriptions, 6-36...

  • Page 199: Dcs 300 Architecture

    copying a string or integer variable, 5-27 copying the left part of a string, 5-28 copying the middle part of a string, 5-27 copying the right part of a string, 5-28 creating a script file, 5-6 creating a script file manually, 5-4 CRIT_EXIT procedure, 5-10 CRTCTLAPPC command, 6-12, 6-22, 6-27, 6-36 CRTCTLLWS command, 6-10, 6-16...

  • Page 200: Fully Interactive System

    5-8 setting terminal configuration data, 6-45 skeleton script, 5-14 special packet, 3-29 switched SDLC line, 6-3 EXIT, 5-38 external Intermec controllers, 1-20 configuration requirements, 1-19 data integrity modes, 1-11 default transmission timeouts, 1-13 Faster mode, 1-12 FIFO, 1-8, 1-11...
  • Page 201 JANUS devices, 1-4 auto-login scripts, 3-30 sample program for direct TCP/IP socket interface, 3-26 specifying a value for device, 2-23 specifying a value for parameter, 2-23 using BFT command files, 2-24 keystroke strings in script files, 5-11 keystrokes in a terminal session, 5-33 LAN local adapter address, setting, 6-30 LAN remote adapter address, 6-23, 6-29 setting, 6-31...

  • Page 202: Safer Mode

    DCS 300 Technical Reference Manual OPEN packet format (continued) using $IPT transaction ID, 3-21 open request error, 3-19 OPEN_ACK packet format, using $IPT transaction ID, 3-21 OPEN_NAK packet format, using $IPT transaction ID, 3-21 opening a requester connection, 3-4 parameter omitting, 2-24 specifying a value, 2-23 partially interactive system, 1-11...

  • Page 203: Sending Hot Standby Messages

    script files (continued) data integrity, 5-11 design considerations, 5-11 editing, 5-10, 5-12 general guidelines, 5-4 INIT procedure, 5-10 keystroke strings, 5-11 logon security, 5-11 MAIN procedure, 5-10 sample, 5-15, 5-18 script variables, 5-12 skeleton example, 5-14 special symbols, 5-12 synchronous vs. asynchronous communications, 5-3 timing, 5-12 transaction mapping efficiency, 5-11 using script variables, 5-21...
  • Page 204 DCS 300 Technical Reference Manual StrLength, 5-24 StrLower, 5-31 StrLTrim, 5-29 StrRTrim, 5-29 StrSearch, 5-26 StrToInt, 5-25 StrUpper, 5-31 successful open request, 3-19 switch setting, 6-11 switched connection, 6-7 switched line list, 6-12, 6-18, 6-23, 6-28 synchronous communications, 5-3 system fully interactive, 1-10 noninteractive, 1-11 partially interactive, 1-11...

  • Page 205: Transferring Batch Files

    transferring batch files, 1-25 trimming the left part of a string, 5-29 trimming the right part of a string, 5-29 TRLAN line type, 6-26 troubleshooting 5250 terminal sessions, 6-33 CPF4128 error, 6-37 detecting a power loss, 1-22 duplicate data from external controllers, 1-13 interrupting IBM mainframe startup, 5-12 losing power in Faster mode, 1-12 NetError, 3-11...
  • Page 206 DCS 300 Technical Reference Manual I-12...

Table of Contents