HP Neoware e90 Neoware Thin Clients running Microsoft® Windows&#1 - Page 101

possibilities have been tried. In the latter case the same name is sent

Page 101 highlights

TeemTalk Connection Configuration case. For example, %.3s will return the first three characters of the local host name, and %-.3s will return the last three characters. To automatically assign a new device name for each successive connection, either enter %dN% after the name, where N is a decimal value, or %xN%, where N is a hexadecimal value. Each time the host requests the device name a counter will be incremented modulus N and substituted into the device name. For example, TEST%d4% will give TEST1 on first connect, TEST2 on second, TEST3 on third, TEST0 on fourth, TEST1 on fifth and so on. TEST%d100% will give TEST1 on first connect, TEST2 on second, ... TEST99 on 99th, TEST0 on 100th, TEST1 on 101st and so on. These values are preserved over power off, so the first connection of any given power on may not be TEST1. Assume that the start point is random. In addition there is a single counter for the unit so concurrent sessions will start from subsequent values. For example, if session one uses TEST1 then session two will use TEST2. Where a device name collision occurs (i.e. the device name is already in use on the host) the host will ask again for the device name during the same connection. In this case TEST1, TEST2, ... may all be tried in one connection until the host accepts one, or all possibilities have been tried. In the latter case the same name is sent twice in succession to indicate to the host all names have been tried. If concurrent 5250 sessions are started before a previous session has negotiated an acceptable device name, it is possible that the two sessions will access the counter simultaneously and not all possible names will be tried by each session. This should not cause a problem unless the separate sessions use different modulo values (for example, session one device name TEST%d4% and session two device name ANOTHER%d100%) or are connecting to different hosts. Note: There are separate counters for the IBM 3270 and IBM 5250 emulations. TCP/IP Connection Settings 85

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228

TeemTalk Connection Configuration
TCP/IP Connection Settings
85
case. For example,
%.3s
will return the first three characters of the
local host name, and
%-.3s
will return the last three characters.
To automatically assign a new device name for each successive con-
nection, either enter
%dN%
after the name, where
N
is a decimal
value, or
%xN%
, where
N
is a hexadecimal value. Each time the
host requests the device name a counter will be incremented modu-
lus
N
and substituted into the device name.
For example,
TEST%d4%
will give
TEST1
on first connect,
TEST2
on second,
TEST3
on third,
TEST0
on fourth,
TEST1
on
fifth and so on.
TEST%d100%
will give
TEST1
on first connect,
TEST2
on sec-
ond, ...
TEST99
on 99th,
TEST0
on 100th,
TEST1
on 101st and so
on.
These values are preserved over power off, so the first connection of
any given power on may not be
TEST1
. Assume that the start point
is random. In addition there is a single counter for the unit so concur-
rent sessions will start from subsequent values. For example, if ses-
sion one uses
TEST1
then session two will use
TEST2
.
Where a device name collision occurs (i.e. the device name is
already in use on the host) the host will ask again for the device
name during the same connection. In this case
TEST1
,
TEST2
, ...
may all be tried in one connection until the host accepts one, or all
possibilities have been tried. In the latter case the same name is sent
twice in succession to indicate to the host all names have been tried.
If concurrent 5250 sessions are started before a previous session has
negotiated an acceptable device name, it is possible that the two ses-
sions will access the counter simultaneously and not all possible
names will be tried by each session. This should not cause a problem
unless the separate sessions use different modulo values (for exam-
ple, session one device name
TEST%d4%
and session two device
name
ANOTHER%d100%
) or are connecting to different hosts.
Note:
There are separate counters for the IBM 3270 and IBM 5250
emulations.