msgset – offset and length in bytes or characters?

This topic has 3 replies, 2 voices, and was last updated 10 years, 4 months ago by Russ Ross.

Creator

Topic
April 11, 2014 at 10:45 pm #54156

Terence Gucwa
Participant

We’re having a dreadfully difficult time going from 5.7 to 6.0 (We never did succeed in going to 5.8), largely because of encoding issues.
Creator

Topic

Viewing 2 reply threads

Author

Replies
- April 13, 2014 at 6:33 pm #80375
  
  Russ Ross
  Participant
  
  We ran into some challenges when we went from Cloverleaf 5.6 to 6.0 with our EBCDIC interfaces because there is now an encoding choice which defaults to ASCII.
  
  Try playing around with changing the encoding settings until you get the desired outcome.
  
  NetConfig -> properties -> encoding -> binary (is what we ended up going with for EBCDIC related interfaces with SMS/Care/Invision mainframe).
  
  Russ Ross
  RussRoss318@gmail.com
- April 14, 2014 at 4:26 pm #80376
  
  Terence Gucwa
  Participant
  
  Hi Russ, I’ve read some of your posts here and found them informative.
- April 14, 2014 at 5:19 pm #80377
  
  Russ Ross
  Participant
  
  Another thing to keep in mind is to run your messages thru the actual interface and do hcihd to know for sure what is actually happening, becuase things like SMAT and the tester can give a misleading display representation of the acutal data message when it comes to characters above 128.
  
  In other words SMAT might show a 2 byte character while a hcihd of the data message is actually one byte or something like that, a little fuzzy now that some time has passed.
  
  Russ Ross
  RussRoss318@gmail.com
Author

Replies

Viewing 2 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.