SMAT resend to file – difference between GUI and cmdline

[Peter Heggie]

I’m trying to make a script to export a message from a smat file. The messages are in ebcdic so I want one quick script to automate the entire process of exporting from smat, converting to ascii and copying the file to a non-Cloverleaf directory.

All of this work, and this posting, is concerned with incoming messages from Invision on the mainframe, coming in as EBCDIC over SNA.

Anyway, when I run the command hcismat from the command line, I get an extra line of output, vs. when I use the Smat GUI to resend to a file.

The extra line of output seems to be the ‘meta data’ prefixed to each message by SMS/Invision, except that this extra line is at the end of the message, and it is the meta data that ‘belongs’ to the NEXT message. I can tell by the ‘control number’ in that meta data – I can see that same value when I look at the Smat GUI and skip to the next message – that same value is in the prefixed meta data of the next message.

This is all happening before I get to my scripting. I just run the hcismat command from the command line:

hcismat -i -orsf

-sms 123456 -sme 123456

This may have something to do with the SNA allocate/deallocate (I’m fuzzy on this) process which sometimes results in a ‘FF’ message showing up in Smat as a 1 byte message, and other times it shows up as the first character of the message (in the Invision ‘meta data’). Also, other messages in the Smat have the Invision meta data starting with ’00’. This never seems to bother production processing, but the hcismat command seems to get confused by it, whereas the Smat GUI has no problemn with it.

So my nifty script that was going to save me time seems to be bogged down and I”ll have to go back to the GUI tool.

Any comments?

Pete

Peter Heggie
PeterHeggie@crouse.org

Topic

[Russ Ross]

Check out this URL

<a href="https://usspvlclovertch2.infor.com/viewtopic.php?t=1539&#8243; class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=1539

where I posted the code for my scripts called

  ebcdic_smat_to_nl.ksh

  len10_to_nl.pl

  ascii_smat_to_nl.ksh

that you can try to see if they improve your desired outcome.

I don’t like much having to use the EBCDIC smat output from SMS mainframe either because of all the extra junk and the 3start messages that garble the output.

Unless necessary I use the ASCII smat file from the hop_send interface I described in this post because it is nice and neat without all the unwanted garble.

<a href="https://usspvlclovertch2.infor.com/viewtopic.php?t=958&#8243; class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=958

Russ Ross
RussRoss318@gmail.com

[Author]

Replies