RE: Measuring network transmission times

I agree with you but the client is looking for objective data. The users
are complaining about response time and they want to know if changing to
a faster wireless network will help.

I wrote a test program and I have noticed a signifigent difference
between my PC using Client Access and the dumb terminal that we have for
a console. The dumb terminal is much slower, although it is still a small
fraction of a second.

Albert

  ----- Original Message -----
  From: "Jones, John (US)"
  To: "Midrange Systems Technical Discussion"
  Subject: RE: Measuring network transmission times
  Date: Thu, 25 Aug 2005 09:44:44 -0500


  In general I agree. Back in the 'good old days' when we ran BPCS on a
  B50, we commonly had 19.2Kbps leased lines that supported upwards of
  50
  devices. Maybe 5 line/barcode printers, 20 PC Support devices, with
  the
  rest being dumb terminals. Very low-bandwidth; very efficient.

  Of course, that was SNA and we prioritized the 5250 over the print
  traffic, but overall, line speed was never an issue.

  802.11b is 11Mbps or about 600 times the bandwidth of that old 19.2
  line. 802.11g is 54Mbps; even faster. Heck, my Treo using cellular
  data averages 70-110Kbps or around 4 times faster and that's only
  supporting a single 5250 session.


  --
  John A. Jones, CISSP
  Americas Information Security Officer
  Jones Lang LaSalle, Inc.
  V: +1-630-455-2787 F: +1-312-601-1782
  john.jones@xxxxxxxxxx

  -----Original Message-----
  From: midrange-l-bounces@xxxxxxxxxxxx
  [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
  Sent: Thursday, August 25, 2005 9:06 AM
  To: Midrange Systems Technical Discussion
  Subject: RE: Measuring network transmission times

  IMHO,

  You're wasting your time.

  The 5250 protocol dates back to 300 baud dial-up lines. The amount of
  data transmitted is very low. Unless you're trying to squeeze 1,000s
  of
  users onto a single wireless access point, it's highly unlikely you'd
  even come close to maxing out the wireless bandwidth.

  HTH,

  Charles Wilt
  --
  iSeries Systems Administrator / Developer Mitsubishi Electric
  Automotive
  America
  ph: 513-573-4343
  fax: 513-398-1121


  > -----Original Message-----
  > From: midrange-l-bounces@xxxxxxxxxxxx
  > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Albert York
  > Sent: Tuesday, August 23, 2005 11:14 AM
  > To: Midrange Systems Technical Discussion
  > Subject: Measuring network transmission times
  >
  >
  > I have a client who is evaluating different 5250 emulation devices
  in
  > a wireless network environment.. They would like to determine what
  > the transmission time is for each of the devices. I would like to
  > write a program which would send a screen to the device and have
  the
  > device immedatelty return a response. I do not have any ability to
  > program any of the devices so it would have to be straight 5250. I
  > have tried using the CHECK(ER) but that still requires manual
  > input. If it can't be done in DDS is there a UDDS string which
  would
  > accomplish what I need?
  >
  > Thanks,
  >
  > Albert York
  > --
  > This is the Midrange Systems Technical Discussion
  > (MIDRANGE-L) mailing list
  > To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
  > unsubscribe, or change list options,
  > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
  > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
  > take a moment to review the archives at
  > http://archive.midrange.com/midrange-l.
  >
  >

  --
  This is the Midrange Systems Technical Discussion (MIDRANGE-L)
  mailing
  list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
  unsubscribe, or change list options,
  visit: http://lists.midrange.com/mailman/listinfo/midrange-l
  or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
  a
  moment to review the archives at
  http://archive.midrange.com/midrange-l.



  This email is for the use of the intended recipient(s) only. If
  you have received this email in error, please notify the sender
  immediately and then delete it. If you are not the intended
  recipient, you must not keep, use, disclose, copy or distribute
  this email without the author's prior permission. We have taken
  precautions to minimize the risk of transmitting software viruses,
  but we advise you to carry out your own virus checks on any
  attachment to this message. We cannot accept liability for any
  loss or damage caused by software viruses. The information
  contained in this communication may be confidential and may be
  subject to the attorney-client privilege. If you are the intended
  recipient and you do not wish to receive similar electronic
  messages from us in the future then please respond to the sender to
  this effect.

  --
  This is the Midrange Systems Technical Discussion (MIDRANGE-L)
  mailing list
  To post a message email: MIDRANGE-L@xxxxxxxxxxxx
  To subscribe, unsubscribe, or change list options,
  visit: http://lists.midrange.com/mailman/listinfo/midrange-l
  or email: MIDRANGE-L-request@xxxxxxxxxxxx
  Before posting, please take a moment to review the archives
  at http://archive.midrange.com/midrange-l.