{"id":2281,"date":"2020-02-10T15:42:14","date_gmt":"2020-02-10T23:42:14","guid":{"rendered":"https:\/\/portal.staylinked.com\/sl\/kb\/?post_type=ht_kb&p=2281"},"modified":"2022-01-19T11:16:06","modified_gmt":"2022-01-19T19:16:06","slug":"device-group-administration","status":"publish","type":"ht_kb","link":"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/device-group-administration\/","title":{"rendered":"Administrator User Guide – Device Group Administration"},"content":{"rendered":"\n

This section describes the various\nmeans provided to define your device groups for each StayLinked server. All\nStayLinked clients that request a session through a server are assigned to a\ndevice group by that server. The device group contains many of the vital\nsettings and attributes that control the way a connected device will interact\nwith a telnet host and how it will be handled by the StayLinked server.<\/p>\n\n\n\n

Multiple device groups can be\ndefined for each server, but all servers will always have at least a \u2018Default\nDevice Group\u2019. Initially, all devices that connect to the server are assigned\nto the default group. You can configure the attributes for the default device\ngroup, but it cannot be deleted.<\/p>\n\n\n\n

You can also create and manage\n\u2018Specific Device Groups\u2019. Specific device groups allow you to manage device\nconfiguration information for express subsets of devices. Device groups are\ndefined to control devices within a specific range of IP addresses and for\nspecific device types within that IP range. When each device initiates its\nconnection request, it is assigned to a particular device group based on its\nlocal IP address and device type. The device will be assigned to, and use the\nattributes of, the device group that most closely matches the device\u2019s IP\naddress and device type. If the device is not assigned to one of the specific\ndevice groups, then the device will be assigned to, and inherit the attributes\nof the Default Device Group.<\/p>\n\n\n\n

Managing Device Groups<\/h3>\n\n\n\n

When you select Device Groups from the server tree or the Manage menu, the Device Groups list will appear in the main display panel. The Device Groups information can be sorted into ascending or descending order by clicking on any of the column headers. The currently sorted column will be indicated by an asterisk (*). Each StayLinked server will have a Default Device Group and you can add other, more specific device groups as required. Clicking the right mouse button on a device group will pop up a context menu with options to Add, Edit, Copy, Paste or Delete a group.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Maintaining Device Group Settings<\/h3>\n\n\n\n

When you add, edit, or copy a device group, the following window will appear that shows the current device group settings and allows you to make changes.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Group Description:<\/strong> This is a descriptive name for the Device Group,\ni.e.: \u201cShipping Department\u201d.<\/p>\n\n\n\n

Group IP Address Range: <\/strong>This is the range of device IP addresses\nfor this group.<\/p>\n\n\n\n

Device Type:<\/strong> This is the device type filter for this group. The combination of IP Range and Device Type are used to determine which devices will be a member of this device group. Leave this value blank to include all devices in the IP range, regardless of their Device Type.<\/p>\n\n\n\n

StayLinked Server IP:<\/strong> Added in v15.2, this hidden\/optional device type filter is typically used to split incoming connections between internal and external (internet) connections. Appearing in the space just below the device type, this area appears blank unless a special configuration option is enabled in the server configuration. This file is called espadmin.xml which can be found in the Config subdirectory of the StayLinked Server installation directory.<\/p>\n\n\n\n

Manually edit the espadmin.xml file on your server to add the 'advanced_device_groups' setting to the administration node of the espadmin.xml file. You may need to close and then re-open your Administrator to receive the configuration when connecting to a server. Your espadmin.xml should contain a line similar to the following:
<administration advanced_device_groups=\"Y\"\/><\/p>\n\n\n\n

During a connection request, the Client reports the IP address to which it is attempting to connect. This value would typically be different if the connection is internal to a network than if it was coming in from an outside source. Along with other filters, this can help split incoming connections with highly randomized IP addressing.<\/p>\n\n\n\n

Maximum Connections:<\/strong> This value will control the number of\nconnections that are allowed to use this device group. (0 or blank = unlimited\nconnections)<\/p>\n\n\n\n

Host Group:<\/strong> This is the Host Group that defines which emulation hosts will be available to devices in this device group. If the selected host group is not available at the time a device connects, then the device will automatically use the \u2018Default\u2019 host group. A special host group named \u2018Device Management Only\u2019 is also available for selection. This host group will cause the device to run a Device Management Only session. There will be no Telnet or SSH access provided in this Device Management Only session. The client software will behave much differently on the device when the client is running a Device Management Only session. The \u2018Device Management\u2019 features have been end-of-life since September, 2015.<\/strong><\/p>\n\n\n\n

Keyboard\/Suspend\/Sleep Timeout:<\/strong> This value defines how many seconds\nof inactivity will pass before the device goes into sleep mode. A value of zero\nwill cause the device to never timeout. This timeout requires that the\n\u2018Application Lockdown\u2019 Client Setting be enabled. The behavior of this timeout\nis device-dependent.<\/p>\n\n\n\n

Backlight Timeout:<\/strong> Defines the number of seconds that the backlight\nwill stay lit between keystrokes or scans on the device. A value of zero will\ncause the backlight to never timeout. This timeout requires that the\n\u2018Application Lockdown\u2019 Client Setting be enabled. The behavior of this timeout\nis device-dependent.<\/p>\n\n\n\n

Allow Connections:<\/strong> This checkbox provides the administrator with\nthe ability to determine which devices can establish sessions. This checkbox\nmust be checked in order for devices belonging to this device group to be able\nto connect to a telnet session. <\/p>\n\n\n\n

Allow Multi Sessions:<\/strong> This checkbox provides the ability to control\nwhich devices will be allowed to run Multi Sessions. This option will only have\nan effect if a Multi Session License is installed.<\/p>\n\n\n\n

Display 5250\/3270 OIA Area:<\/strong> Make sure that this checkbox is\nselected if you wish for the devices in this group to display the Operator\nIndicator Area at the bottom of the screen when running 5250 or 3270 sessions.\nThe OIA looks like this: [   ][   ][  \n][   ] and notifies you of Input Inhibit,\nKeyboard Lock, Message Waiting and Insert status. If all indicators were\ndisplayed, the area would look like this: [INH][LCK][MSG][INS]. For Version 14\nServers, you can select a \u2018Graphical Operator Indicator Area\u2019 for devices that\nsupport graphical elements. This option is configured in the \u2018Telnet Host\nEntry\u2019 by selecting the \u2018Dynamic Screen Settings\u2019 option under the \u2018Manage\u2019\nmenu.<\/p>\n\n\n\n

Debug OIA:<\/strong> This option provides an enhanced OIA at the bottom of\nthe device display that shows the standard OIA indicators as well as\nalpha\/numeric field attributes, view port origin and the current cursor\nposition. The fully-populated Debug OIA looks like this: [ILM^A 01\/001 01\/001]
\nThe Debug OIA generates much more network traffic as it is updated every time\nthe cursor is moved, so it should only be used to setup attributes like\n\u2018Viewport Locking\u2019 and Font Size settings.<\/p>\n\n\n\n

Allow Color:<\/strong> For devices that are capable of displaying color\nscreens, use this checkbox to control which devices will be allowed to display\ncolor. If this option is not checked, color-capable devices will display white\ntext on a black background.<\/p>\n\n\n\n

Auto Add DM License:<\/strong> Check this box to cause all DM-capable devices in this group to be automatically added to the Device Management database. Devices in this group will be added to the DM database only if the server is licensed for DM and if there are DM seats available to be issued to the device. (This option has been removed in v15.1 build 208 and newer.) <\/p>\n\n\n\n

Auto Add Evolve Device Access:<\/strong> (v15.3) Check this box to cause all devices in this group to be assigned an Evolve Device license seat. Devices in this group will be assigned an Evolve License seat only if the server Evolve licensing available to be issued to the device.<\/p>\n\n\n\n

Auto Add SpeechLink:<\/strong> Check this box to cause all SpeechLink-capable devices in this group to be assigned a SpeechLink license seat. Devices in this group will be assigned a SpeechLink License seat only if the server is licensed for SpeechLink and if there are SpeechLink seats available to be issued to the device.<\/p>\n\n\n\n

Auto Add Speech:<\/strong> (removed in v15.3) Check this box to cause all Speech-capable devices in this group to be assigned a Speech license seat. Devices in this group will be assigned a Speech License seat only if the server is licensed for Speech and if there are Speech seats available to be issued to the device.<\/p>\n\n\n\n

Device Name Prefix:<\/strong> The 5250 device descriptions for all RF devices\nfalling within this device group IP address range will get this prefix. For\neach RF device in this device group, the name of the device description on the\nIBM i will be this Device Name Prefix followed by a unique suffix calculated\nbased upon the IP address of the connecting device and the Suffix Octets and\nDecimal Suffix settings. If you leave this field blank, then device naming will\nnot be enabled for this device group. If you wish to create a device name with\nno prefix, use the reserved prefix \u2018NULL\u2019 which will cause the system to\ngenerate a device name using only the suffix. The device name prefix can be any\nlength up to 10 characters. If your configuration will cause a device name to\nbe generated that is longer than 10 characters, you will be notified and a\ncorrective measure will be suggested.<\/p>\n\n\n\n

If you wish to manage your device\nnames at the individual device, then you can specify [deviceid] as the Device\nName Prefix and this will cause the client software to retrieve either the\n\u2018Device Name\u2019 from the PPC\/CE.Net operating system, or use the \u2018device_id\u2019\nclient setting from the client INI file, and use that identifier as the entire\n\u2018Device Name\u2019.<\/p>\n\n\n\n

Suffix Octets:<\/strong> The maximum size of the device suffix is 6 characters. This setting allows you to control the size of the device name suffix. If you select Decimal Suffix, then each decimal octet will require 3 positions and you can select 1 or two octets. If you de-select Decimal Suffix, then each octet will require 2 positions and you can select from 1 to 3 octets. You may select 0 octets only if the Low and High IP Address Range for the group are the same IP address.<\/p>\n\n\n\n

Starting in v15.2, suffix octets can now be configured for public and private IP address use. Connections appear in the connections list with a hyphenated IP address are displaying an address reported by the Client and an address where the packets\/connection came from. Workstation names built from IP address can use either the public or private address when creating these names. Public addresses are typically used only for NAT'd network connections.<\/p>\n\n\n\n

Decimal Suffix:<\/strong> This option allows you to specify whether to use\ndecimal or hexadecimal values to build the device name suffix.<\/p>\n\n\n\n

Device Naming Examples:<\/strong><\/p>\n\n\n\n

  • Device Name Prefix = SHP_
    \nSuffix Octets = 3
    \nDecimal Suffix = Unchecked
    \nRF device IP 192.168.100.25 will be converted to IBM i Device Name SHP_A86419. <\/li>
  • Device Name Prefix = SHP_
    \nSuffix Octets = 2
    \nDecimal Suffix = Checked
    \nRF device IP 192.168.100.25 will be converted to IBM i Device Name SHP_100025. <\/li>
  • Device Name Prefix = SHP_
    \nSuffix Octets = 1
    \nDecimal Suffix = Checked
    \nRF device IP 192.168.100.25 will be converted to IBM i Device Name SHP_025.<\/li>
  • Device Name Prefix = DEVICE0001
    \nSuffix Octets = 0
    \nGroup IP Low Range = 192.168.100.25
    \nGroup IP High Range = 192.168.100.25
    \nRF device IP 192.168.100.25 will be converted to IBM i Device Name DEVICE0001. <\/li>
  • Device Name Prefix = NULL
    \nSuffix Octets = 1
    \nDecimal Suffix = Checked
    \nRF device IP 192.168.100.25 will be converted to IBM i Device Name 025.<\/li>
  • Device Name Prefix = [deviceid]
    \nPPC\/CE.Net Device Name = WHSDEV1
    \nRF device IP 192.168.100.25 will use IBM i Device Name WHSDEV1.<\/li><\/ul>\n\n\n\n

    VT Alarm ID Column:<\/strong>\nFor VT sessions, you can specify the column where the VT Alarm ID Character\nwill be found.<\/p>\n\n\n\n

    Row: For VT sessions, you can\nspecify the row where the VT Alarm ID Character will be found.<\/p>\n\n\n\n

    VT Alarm ID Char:<\/strong> For VT sessions, you can specify a character,\nwhich when found in the location defined by the VT Alarm ID Column and Row,\nwill cause the Alarm to be sounded on the device as specified in the \u2018Handle\nAlarms\u2019 setting.<\/p>\n\n\n\n

    Hide ID:<\/strong> For VT sessions, this setting will cause the VT Alarm ID\nCharacter to be hidden (non-visible) on the device.<\/p>\n\n\n\n

    Handle BELs & Alarms:<\/strong> You may select which type of audible\nindicator will be used when a 5250 display contains the ALARM DDS keyword or a\nVT BEL or VT Alarm ID is encountered. The options are None, Short Beep, Long\nBeep, Double Beep or Vibrate.<\/p>\n\n\n\n

    Handle 5250 Messages:<\/strong> You may select the method that will be used\nto display messages that appear on the message line 24 of the 5250 screen.<\/p>\n\n\n\n

    • Snap-To\nMessage:<\/strong> This method emulates IBM\u2019s Wireless Connect behavior causing the\ndevice window to snap down to the lower-left corner of the 5250 screen,\nallowing you to see the message. This method requires that you send a [RESET]\nkey if the 5250 session keyboard becomes locked.<\/li><\/ul>\n\n\n\n
      • Pop-Up\nMessage:<\/strong> This method causes a pop-up message to be displayed that contains\nthe entire text of the message. This method will automatically send a [RESET]\nkey to unlock the 5250 keyboard when appropriate.<\/li>
      • Take No\nAction:<\/strong> Select this option if you want no action taken when messages\nappear.<\/li>
      • Popup\nMsg. Location:<\/strong> You may select the area on the device screen where system\nmessages will be displayed. The choices are \u2018Top\u2019, \u2018Center\u2019 or \u2018Bottom\u2019 of the\ndevice screen. The default is to have system messages displayed at the \u2018Top\u2019 of\nthe device screen.<\/li><\/ul>\n\n\n\n

        Message Notification:<\/strong>\nYou may select which type of audible indicator will be used when a new message\nappears on the message line. The options are None, Short Beep, Long Beep,\nDouble Beep or Vibrate.<\/p>\n\n\n\n

        Manage Barcodes:<\/strong> Click this button to access a dialog that will\nallow you to configure barcode types for this device group.<\/p>\n\n\n\n

        Manage Program Calls:<\/strong> Click this button to access a dialog that\nwill allow you to configure client-side program calls for this device group.<\/p>\n\n\n\n

        Manage Printing:<\/strong> Click this button to access a dialog that will\nallow you to configure client-side printing options for this device group.<\/p>\n\n\n\n

        Manage Startup Scripts:<\/strong> Click this button to access a dialog that\nwill allow you to configure session start-up scripting options for this device\ngroup.<\/p>\n\n\n\n

        Manage Alt. Keyboards:<\/strong> Click this button to access a dialog that\nwill allow you to assign alternate keyboard maps to be used by devices that are\nmembers of this group.<\/p>\n\n\n\n

        Managing Barcodes<\/h3>\n\n\n\n

        For each device group, you may control the manner in which barcodes are scanned for that device group. The following window is presented when you click on the Manage Barcodes button on the Update Device Group window. The window contains some device group level barcode settings and a list of specific barcodes defined for this device group.<\/p>\n\n\n\n

        \"\"<\/figure>\n\n\n\n

        Enable Undefined Barcodes:<\/strong> This option works in conjunction with the\nlist of barcode types that are configured for this device group. Check this box\nif you want to allow the device to scan barcode types that are not specifically\nconfigured for this device group.<\/p>\n\n\n\n

        Append Field Exit to Short Scan (5250):<\/strong> For 5250 sessions, select\nthis option to cause a Field Exit to be automatically appended to barcodes that\nare shorter than the field into which they are being scanned. This option is\noften used to enhance scanning into display fields that cause an automatic\nend-of-record advance via the CHECK(ER) display attribute. (This setting has no\neffect for 3270 or VT emulation).<\/p>\n\n\n\n

        Append Enter on Last Field (5250 & 3270): <\/strong>For 5250 and 3270\nsessions, select this option to cause an Enter to be automatically appended to\nbarcodes that are scanned into the last field on the current application\nscreen. (This setting has no effect for VT emulation).<\/p>\n\n\n\n

        Barcode Scan Prefix:<\/strong> This feature provides for the definition of\ncharacters to be inserted as a prefix to the scanned data. Select from the\nDrop-down list, or key in your prefix characters. This setting will affect all\nbarcode symbologies unless a specific prefix is defined for a specific\nsymbology.<\/p>\n\n\n\n

        Barcode Scan Suffix:<\/strong> This feature provides for the definition of\ncharacters to be inserted as a suffix to the scanned data. Select from the Drop-down\nlist, or key in your suffix characters. This setting will affect all barcode\nsymbologies unless a specific suffix is defined for a specific symbology.<\/p>\n\n\n\n

        You may add, edit, and delete\nBarcode Type entries using the \u201cBarcode\u201d menu or by right clicking on a\nspecific Barcode Type entry in the list. When adding or editing barcode types\nfor this device group, the following window will be displayed.<\/p>\n\n\n\n

        This dialog allows you to configure specific settings for specific barcode symbologies and lengths. You can add more than one configuration for various lengths of a single symbology so long as the Minimum Length matches the Maximum Length and you do not already have a setting defined for the specific length. There can be only one setting for a symbology where the Minimum Length and the Maximum Length are different or are zero. Using these length settings, you can have different barcode settings for the same symbology where the barcode values have different lengths.<\/p>\n\n\n\n

        \"\"<\/figure>\n\n\n\n

        The following criteria are used to\ndetermine if the scanned barcode data will be affected by this particular\nbarcode setting:<\/p>\n\n\n\n

        Barcode Type:<\/strong> Use this drop-down list to select the barcode type\nthat you wish to define.<\/p>\n\n\n\n

        Minimum Length:<\/strong> Specifies the minimum value length to have this\nsetting apply.<\/p>\n\n\n\n

        Maximum Length:<\/strong> Specifies the maximum value length to have this\nsetting apply.<\/p>\n\n\n\n

        • Note:<\/strong>\nInput length restrictions for barcode types can be eliminated by setting both\nthe Minimum and Maximum parameters to zero (0).<\/li><\/ul>\n\n\n\n

          If the scanned barcode meets the\ncriteria for this barcode setting, then you can control whether the scanned\nbarcode is allowed to be processed using the following option:<\/p>\n\n\n\n

          Decode this type:<\/strong> Use this checkbox to enable the use of the\nscanned barcode in the session. If this option is checked, then the barcode is allowed,\nand the barcode data manipulation functions are applied. If this option is not\nchecked, then the scanned barcode is rejected, and the device will beep.<\/p>\n\n\n\n

          For scanned barcodes that meet the\ncriteria defining this barcode setting, the following barcode data manipulation\nfunctions will be applied in dialog order, from the top down:<\/p>\n\n\n\n

          • Trim all spaces from<\/li>
          • Substitutions<\/li>
          • Substitute embedded Control Codes<\/li>
          • Trim from Beginning\/End<\/li>
          • Use First ### digits<\/li>
          • Regular Expressions<\/li>
          • Adding Scan Prefix and Suffix.<\/li><\/ul>\n\n\n\n

            Trim all spaces from:<\/strong>\nThis option determines how leading and trailing spaces in the barcode data will\nbe handled. You can select to have spaces trimmed from neither side, the left\nside, the right side or both sides of the barcode data.<\/p>\n\n\n\n

            Substitute:<\/strong> This option allows you to specify a character or string within the barcode data to be replaced by a different character or string. Single character substitutions must be represented in the hexadecimal (0x00) format to differentiate them from string substitutions. To remove data, use [null] as the substitution string value or use 0x00 as the substitution character value. <\/p>\n\n\n\n

            Substitute all embedded Control Codes with this character: <\/strong>Allows\nyou to specify a character to be used as a substitute for all control codes\nthat are embedded in the barcode data. Control Codes are defined as characters\nwith values less than 0x20. This substitution character must be represented in\nthe hex (0x##) format. Enter a value of 0x00 to remove all control codes from\nthe barcode data.<\/p>\n\n\n\n

            Trim from Beginning:<\/strong> Specifies the number of characters to trim\nfrom the beginning of the scanned data. Type in the number of characters to\ntrim, or select the option to trim \u2018to fit field\u2019 which will trim characters\nfrom the beginning when the barcode data is longer than the field length.<\/p>\n\n\n\n

            Trim from End:<\/strong> Specifies the number of characters to trim from the\nend of the scanned data. Type in the number of characters to trim, or select\nthe option to trim \u2018to fit field\u2019 which will trim characters from the end when\nthe barcode data is longer than the field length.<\/p>\n\n\n\n

            Use First ## Digits:<\/strong> Specifies the number of characters from the\nbeginning of the scanned data to use. This value is evaluated after the \u2018Trim\u2019\nattributes have been applied. Set this value to Zero (0) to cause all of the\nremaining barcode data to be used.<\/p>\n\n\n\n

            Regular Expression Processing: <\/strong>Provides the ability to use\nsophisticated \u2018Regular Expression Processing\u2019 to manipulate barcode data. You\ncan enter one or more \u2018Expressions\u2019 that are evaluated against the barcode data.\nIf an expression matches the scanned barcode data, then the \u2018Substitution\u2019 will\nbe processed against the barcode data. Regular Expression Processing for\nbarcode data is covered in detail in the \u2018StayLinked Barcode Regular Expression\nUser Guide\u2019.<\/p>\n\n\n\n

            Scan Prefix:<\/strong> Specifies the characters to be inserted as a prefix to\nthe scanned data. Select from the Drop-down list, or key in your prefix\ncharacters. This setting will override the device group level setting for this\nspecific barcode symbology.<\/p>\n\n\n\n

            Scan Suffix:<\/strong> Specifies the characters to be inserted as a suffix to\nthe scanned data. Select from the Drop-down list, or key in your suffix\ncharacters. This setting will override the device group level setting for this\nspecific barcode symbology.<\/p>\n\n\n\n

            Notes:<\/strong> This is a convenience field that has no effect on barcode\nprocessing. It can, however, help you to organize and manage your barcode rules\nby providing a place to record why you created this symbology-specific barcode\nrule for future reference.
            <\/p>\n\n\n\n

            Managing Program Calls<\/h3>\n\n\n\n

            For each device group, you may define up to three client-side program calls that can be mapped to specific keys on your device keyboard. The following window is presented when you click on the Manage Program Calls button on the Update Device Group window. The programs that are defined in this dialog must be installed on the individual devices. These program calls are often used for printing barcodes and other functions that must be processed on the device. <\/p>\n\n\n\n

            \"\"<\/figure>\n\n\n\n

            User Message:<\/strong> This parameter allows you to display a message on the\ndevice screen during the time that the client-side program is running. If you\nleave this parameter blank, then no message is displayed.<\/p>\n\n\n\n

            Screen Dump File:<\/strong> This parameter gives you the option of dumping an\nimage of the entire current 5250 screen to a text file on the read\/write drive\non the device. The file will be written to the device before the client-side\nprogram is called. Do not specify a drive letter with the file name, as the\nStayLinked client determines what drive is available for writing, depending\nupon the device make and model. If you leave this parameter blank, then no\nscreen image is written to the device.<\/p>\n\n\n\n

            Command\/Program:<\/strong> This parameter specifies the DOS command or\nclient-side program that is to be called. If the program does not exist, no\naction will be taken, and no error message is displayed. When the program has\ncompleted its processing, the session continues normally.<\/p>\n\n\n\n

            Managing Printing<\/h3>\n\n\n\n

            For each device group, you may\nconfigure a group of settings that define how the server will identify and\nhandle client-side printing for devices that belong to that device group. For\nVT Telnet Hosts, StayLinked supports the standard VT printing pass-through\nescape sequences. <\/p>\n\n\n\n

            Additionally, StayLinked provides a facility by which printer commands can be communicated to the device by reading the printer commands from a special application display screen and transmitting those commands to the device. This special application display screen is designed by the end user and is integrated into the end-user application. When this screen is displayed and identified by the StayLinked Server, the printer commands embedded in the screen will be extracted and delivered to the device where they will be transmitted to the printer via the selected COM port settings. <\/p>\n\n\n\n

            \"\"<\/figure>\n\n\n\n

            Enable Screen-based Printing:<\/strong> This option will enable or disable\nclient-side printing for this device group for host applications where screen\nrecognition is required.<\/p>\n\n\n\n

            Display the Screen Containing Printer Data:<\/strong> This parameter\ndetermines whether or not the screen, which has been identified as containing\nprinter command, is displayed on the device.<\/p>\n\n\n\n

            Enable Print Transaction Throttling:<\/strong> Forces acknowledgments for\neach printer data packet sent. It is recommended to select this option for\nlabels or documents that contain a large amount of printer instructions.<\/p>\n\n\n\n

            Start ID Row:<\/strong> This option defines the display row where the server\nwill look for the Print Data Start ID and the Print Data Continue ID.<\/p>\n\n\n\n

            Start ID Column:<\/strong> This option defines the display column where the\nserver will look for the Print Data Start ID and the Print Data Continue ID. This\nvalue is not included in the extracted printer data.<\/p>\n\n\n\n

            Print Data Start ID:<\/strong> This option describes the string of characters\nthat, when found at the Start ID Column and Row, identifies this screen as\ncontaining a new set of printer commands.<\/p>\n\n\n\n

            Print Data Continue ID:<\/strong> This option describes the string of\ncharacters that will notify the StayLinked Server that more printing data is to\nbe expected on subsequent screens. This ID should be used at the end of a\nscreen when there will be more data displayed on the next screen. This ID\nshould also be positioned at the Start ID Column and Row of the next screen\nthat contains additional printer commands. This ID would be used when the printing\ncommands are too complex to fit on a single application display screen.<\/p>\n\n\n\n

            Print Data End ID:<\/strong> This option describes the string of characters\nthat will identify the end of the printer commands. When this ID is encountered,\nall of the collected printer data will be transmitted to the device. This value\nis not included in the extracted printer data.<\/p>\n\n\n\n

            Print CRLF ID:<\/strong> This option describes the string of characters that\nwill identify the CRLF indicators on this screen. The CRLF indicators that are\nfound in the extracted printer data will be replaced with an actual carriage\nreturn\/line feed sequence when that data is transmitted to the device.<\/p>\n\n\n\n

            Printing Completion Action:<\/strong> This option controls how the server\nwill respond when the printer attached to the device has successfully processed\nthe printer commands. The action defined here will be sent to the printing\ncommand screen. For instance, if the printer completes printing, the Enter key\ncan be sent to the screen to cause the printer command screen to be dismissed.<\/p>\n\n\n\n

            Printing Continue Action:<\/strong> This option controls how the server will\nrespond when a screen of printer data is ended with a Printing Continue ID.\nThis action would be used to trigger the display of the next screen that\ncontains the additional printer commands.<\/p>\n\n\n\n

            Printing Cancel Action:<\/strong> This option controls how the server will\nrespond when the printer attached to the device fails to process the printer\ncommands. If you cancel the printing operation on the device, then this action will\nbe sent to the printing command screen. For instance, if you cancel printing,\nthe F12 key can be sent to the screen to cause the printer command screen to be\ndismissed. The value selected for these three actions will depend upon how the\nend user application has been programmed.<\/p>\n\n\n\n

            Printer Device:<\/strong> This setting configures the StayLinked client to\nsupport Serial COM communications with printer devices. If you wish to use RF\nor Bluetooth communication protocols, you will need to configure \u2018Client\nSettings\u2019 for the StayLinked client to support your printer. In the \u2018Printing\u2019\ngroup of Client Settings, you will find the \u2018Printer Type\u2019 setting where you\ncan choose \u2018Generic RF\u2019 or \u2018Generic Bluetooth\u2019 printers. Plus, there are some\nadditional \u2018RF Printer\u2019 settings available.<\/p>\n\n\n\n

            Baud Rate:<\/strong> This option describes the Baud Rate of the printer\nconnected to the device.<\/p>\n\n\n\n

            Data Bits:<\/strong> This option describes the Data Bits setting of the\nprinter connected to the device.<\/p>\n\n\n\n

            Parity:<\/strong> This option describes the Parity setting of the printer connected\nto the device.<\/p>\n\n\n\n

            Print Timeout:<\/strong> This option defines how long the StayLinked client\nwill wait for responses from the attached printer device.<\/p>\n\n\n\n

            Stop Bits:<\/strong> This option describes the Stop Bits setting of the\nprinter connected to the device.<\/p>\n\n\n\n

            Flow Control:<\/strong> This option describes the Flow Control setting of the\nprinter connected to the device.<\/p>\n\n\n\n

            Managing Startup Scripts<\/h3>\n\n\n\n

            For each device group, you may\ndefine a startup script for each type of emulation available. The startup\nscript will be processed only when a new session is established. The script\nwill not be run when a device reconnects to an existing session. The script will\nalways be processed against the first host screen that is presented to the\ndevice, typically a logon screen. <\/p>\n\n\n\n

            Each script can be up to 255\ncharacters in length. Each script can contain any combination of characters and\nemulation mnemonic keywords. Emulation mnemonic keywords are contained within\nsquare brackets []. You can select mnemonic keywords from the \u2018Insert mnemonic\u2019\ndrop-down list, causing the selected mnemonic to be automatically inserted at\nthe current cursor location within the script textbox. Startup Scripts should\nbe carefully designed to function appropriately for the type of emulation,\ntargeted host and end-user application. Syntax errors in the script will not\ncause errors, but could cause some part of your script to be ignored by the emulation\nhost. <\/p>\n\n\n\n

            The following window is presented when you click on the Manage Startup Scripts button on the Update Device Group window. The example 5250 Startup Script below is designed to be processed against a 5250 logon screen. You profile \u2018myuserid\u2019 will be automatically typed into the first field on the screen and then the \u2018Field Exit\u2019 mnemonic will be processed, moving the cursor to the next field on the logon screen. Then, the password \u2018mypasswd\u2019 will be typed into the current field and an \u2018Enter\u2019 key mnemonic will be processed. This script would cause a user to be automatically signed onto the target IBM I emulation host.<\/p>\n\n\n\n

            \"\"<\/figure>\n\n\n\n

            5250 Startup Script:<\/strong> Enter the startup script to be used when\nconnecting to a 5250 Telnet host.<\/p>\n\n\n\n

            3270 Startup Script:<\/strong> Enter the startup script to be used when\nconnecting to a 3270 Telnet host.<\/p>\n\n\n\n

            VT Startup Script:<\/strong> Enter the startup script to be used when\nconnecting to a VT Telnet host.<\/p>\n\n\n\n

            Managing Alternate Keyboard Maps<\/h3>\n\n\n\n

            For each device group, you can\noverride the keyboard map that a device would normally use and specify a\ndifferent keyboard map to be used as an alternate. <\/p>\n\n\n\n

            Keyboard maps are used by the\nStayLinked system as a cross-reference between the many and varied device\nkeyboards and the various host types (5250, 3270, and VT). With StayLinked, you\ncan use the default keyboard map or alter it to suit the specific needs of your\ndevice users and their applications. In addition, you can create alternate\nkeyboard maps to support variations needed for a specific group of devices.<\/p>\n\n\n\n

            The following window is presented when you click on the Manage Alt. Keyboards button on the Update Device Group window.<\/p>\n\n\n\n

            \"\"<\/figure>\n\n\n\n

            In this example, when an Intermec\nCK71 Windows Mobile 6, Alpha-Numeric keypad device connects to this Host, the\nalternate keyboard map for the Intermec CK71 Windows Mobile 6, Numeric keypad\ndevice will be used instead.<\/p>\n\n\n\n

            You may add and delete these\nalternate keyboard maps using the Keyboard menu (the Add New Alternate Map\nselection window is shown above). The Original Map and Alternate Map dropdowns\nprovide a list of available keyboard maps from which to choose.<\/p>\n\n\n\n

            In case you are using Custom Device\nTypes for your devices and you want to map them to an existing standard\nkeyboard map, you may select the special value \u2018** Enter a Custom Device Type **\u2019\nas the \u2018Original Map\u2019. Then select the desired existing \u2018Alternate Map\u2019. When\nyou click OK, you will be prompted for a \u2018Custom Device Type\u2019 value that will\nbe used for the \u2018Original Map\u2019 value.<\/p>\n\n\n\n

            Select \u201cSave Changes\u201d from the \u201cFile\u201d drop-down menu to save any changes that you have made to the currently selected host group.<\/p>\n","protected":false},"excerpt":{"rendered":"

            This section describes the various means provided to define your device groups for each StayLinked server. All StayLinked clients that request a session through a server are assigned to a device group by that server. The device group contains many of the vital settings and attributes that control the way…<\/p>\n","protected":false},"author":7,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":[],"ht-kb-category":[23],"ht-kb-tag":[],"yoast_head":"\nAdministrator User Guide - Device Group Administration – StayLinked<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.staylinked.com\/knowledge-base\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Administrator User Guide - Device Group Administration – StayLinked\" \/>\n<meta property=\"og:description\" content=\"This section describes the various means provided to define your device groups for each StayLinked server. All StayLinked clients that request a session through a server are assigned to a device group by that server. The device group contains many of the vital settings and attributes that control the way...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/device-group-administration\/\" \/>\n<meta property=\"og:site_name\" content=\"StayLinked\" \/>\n<meta property=\"article:modified_time\" content=\"2022-01-19T19:16:06+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2020\/01\/UserAdminGuide_30-1024x588.jpg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"25 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/#website\",\"url\":\"https:\/\/portal.staylinked.com\/sl\/kb\/\",\"name\":\"StayLinked Knowledge Base\",\"description\":\"Partner Portal Resources and Support\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/portal.staylinked.com\/sl\/kb\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/device-group-administration\/#primaryimage\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2020\/01\/UserAdminGuide_30.jpg\",\"contentUrl\":\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2020\/01\/UserAdminGuide_30.jpg\",\"width\":1210,\"height\":695},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/device-group-administration\/#webpage\",\"url\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/device-group-administration\/\",\"name\":\"Administrator User Guide - Device Group Administration – StayLinked\",\"isPartOf\":{\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/device-group-administration\/#primaryimage\"},\"datePublished\":\"2020-02-10T23:42:14+00:00\",\"dateModified\":\"2022-01-19T19:16:06+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/device-group-administration\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/device-group-administration\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/device-group-administration\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/portal.staylinked.com\/sl\/kb\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Articles\",\"item\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Administrator User Guide – Device Group Administration\"}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/ht-kb\/2281"}],"collection":[{"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/comments?post=2281"}],"version-history":[{"count":2,"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/ht-kb\/2281\/revisions"}],"predecessor-version":[{"id":3866,"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/ht-kb\/2281\/revisions\/3866"}],"wp:attachment":[{"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/media?parent=2281"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/ht-kb-category?post=2281"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/ht-kb-tag?post=2281"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}