RTIF SMAT is EBCDIC now in 5.3

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf RTIF SMAT is EBCDIC now in 5.3

  • Creator
    Topic
  • #48218
    Tom Patton
    Participant

      On v5.3 rev3 It looks like the SMAT is written after pre-write rather then at state 11 as it had been in the past.  The impact is that now the SMAT contains data in EBCDIC rather than ASCII.

      Is there a fix for this, perhaps a new RTIF, or how have you worked around this?

      Thank you.

    Viewing 6 reply threads
    • Author
      Replies
      • #58032
        Elizabeth Wilson
        Participant

          Does it make any difference in SMAT? You may display it in different formats using ENCODING drop list. What happened to me, after using the new RTIF in 5.3 was that the DEBUG in RTIF was displaying EBCDIC in the log file of command-engine output. Charlie advised me to insert the hcitpstblconvert proc before SendokSMS and that took care of it. I hope this helps.

        • #58033
          James Cobane
          Participant

            Tom,

            I believe SMAT has always saved the messages in this way.  If I recall, SMAT kicks-in just after processing the message through the protocol threads.  I’ve always had to click on EBCDIC encoding within the SMAT tool when dealing with TIF/RTIF messages.  However, there is an issue with going into EDIT mode from the Client SMAT GUI; it re-displays in EBCDIC making it essentially impossible to edit an EBCDIC message.  I don’t know if this is still the case with 5.3, but I know it was in previous Platform V versions.

            Hope this helps.

            Jim Cobane

            Henry Ford Health

          • #58034
            Tom Patton
            Participant

              We just migrated from 3.8.1 and SMAT was in ASCII for these threads on that version.  Elizabeth, I didn’t think it would matter either, but like Jim says, you lose the ability to edit.

              And wouldn’t you know it, I’m developing a new interface now and I typically use the edit function to model the msg.

            • #58035
              James Cobane
              Participant

                Tom,

                There is a work-around to allow you to edit; it’s using the old SMAT GUI (via X-windows). You need to put the attached file (remove the .tcl extension, though) into the $HCIROOT/usercmds directory (edit the first line for the appropriate path and make it executable), and then add the following line to the hci users

                .profile:

                export VISUAL=hciedit

                Hope this helps.

                Jim Cobane

                Henry Ford Health

              • #58036
                Ryan Boone
                Participant

                  Thanks to Jim last year I was able to edit from the original SMATs as well. In fact, I still exclusively use the old SMAT Tool because you can open as many as you need at once, they’re faster to load, and whenever you use the new SMAT the entire GUI hangs while you’re loading large files.

                • #58037
                  Sandy McQuay
                  Participant

                    Thanks for posting these instructions and file Jim!  Since we moved to platform 5, I too, use the “old” gui because it’s much faster.  However, I always had a problem if I needed to edit a message or if I was looking at ebcdic.

                  • #58038
                    Traci Zee
                    Participant

                      I’d like to make vi the editor for the old command line hcismat.  How do I do that for AIX 5.2?

                      hciedit doesn’t have find/replace all functions and vi does.

                      TIA,

                      Traci

                  Viewing 6 reply threads
                  • The forum ‘Cloverleaf’ is closed to new topics and replies.