IBM Mainframe Forum

AllardK wrote:from the protocol description I would come to this:

4,4 char,
5,2 binary, 0x01
6,4 binary, integer I , formatted as 32bit number, in little indian firmat
8,4 char
13, I char

where integer I is the lenth of the data-part

“Little indian firmat” - this is something new in Computer Science...

Looks like it has been developed in India?

These users thanked the author sergeyken for the post:

AllardK (Sat Mar 27, 2021 1:36 pm)

AllardK wrote:here is my code-snippet:

Select all

result = Calculate_Result(key)
  dl_out = length(result)
  dl_out_hex = D2X(dl_out)
  packet = 'ZBXD'||'01'x||dl_out_hex||'00'x||'00'x||'00'x||'00'x||result
  fc = SOCKET('SEND',accepted_socket,packet,'')

In my test the string resut = ‘ZOS4’
So the length of the data is 4

However when sending the packet the zabbix-server is giving an error “because message is shorter than expected 52 bytes”

So the problem must be in the wrong format of dl_out in the packet.

I hope you can help me solve this.

1) read carefully about the function D2X, and other conversion fonctions.
2) trace your conversions, each step, by using

3) think a little bit about the printed results

Since you did not do it yourself, that proves to me 100% that this is the very first program you have coded in your life, right?

what disease prevents You from reading the manuals ???

a plain dumb simple google search for "REXX D2X" returned this link
https://www.ibm.com/support/knowledgece ... x/d2x.html

if You had done a bit of homework You would not have had the need to ask

it would be useful to get the most out of the questions you ask to read and meditate on

"How to ask questions the smart way"

http://catb.org/~esr/faqs/smart-questions.html

since I am in a very good mood ( just for a few seconds ) here is a snippet to meditate on



what You need is x2c(d2x(l,2))

Hello Enrico,

I have read the manuals over and over, without any reSULT.
I am a relative newbee to REXX (2 years of exxperience) but I have been programming for about 40 years in COBOl, CICS,DB2.

The suggestions you have given are much appreciated, but if it would have been that simple I would’nt have asked for help on this expert forum. The suggestions don’t seem to work in REXX.

I know a little bit of REXX (maybe a little more than that) but this problem is a bit trickier than just reading the manual(which I did and gave me a lot of pleasure).

Here is my code:



The response from the Zabbix-servers is:

The output of the REXX program on z/OS is:

You forgot to give back just one tiny little information ..

does the message buffer You just built conform to the sequence of instructions used
and to what You are expecting you are expecting

if NO post the displays You got so that we have something to work on
show both the char format and the hex format

if YES You are writing what You built, but unfortunately what You built is wrong

I just run a quick and dirty test using rexx on my pc
to show what the buffers should look like given Your info

the script


the result


the pc is ascii the mainframe is ebcdic,
just forget the difference in the hex representation of the chars

what counts are the binary values

Like enrico-sorichetti I would like to see what the output is from one of the other implementations - in hex. Something that works, please.
Clearly your generated text is too short so something in missing.

Hello Enrico and Willy,

first of all, I really appreciate your help.

I ran the sample test program on z/OS and got the following output:

which looks good to me.

However the length field is still not in the right format foor the Zabbix-server side:

I have done some testing.

hex 01 gives datalength 1 on the side of the Zabbix-server
hex 02 gives 2
hex 03 gives 3
hex 04 gives 26
hex 05 gives 32

Still trying, reading and puzzling

Kind regards

Allard

unfortunately very little we can do on our side

I spent a bit of time researching ..
got to the zabbix manual pages with the snippets you posted
https://www.zabbix.com/documentation/cu ... er_datalen

and fortunately there was a bash snippet



and when I run it using ZOS4 as data I got the same results as the rexx snippet I gave You


as You see the last printf shows the same buffer
( it looks strange because the escape chars were lost in the code tags )

probably worth to ask on a zabbix forum

These users thanked the author enrico-sorichetti for the post:

AllardK (Sat Mar 27, 2021 1:37 pm)

Various thoughts...

In your code:

I have been stymied many times because of trailing characters or blanks. And I recall that rexx strips off the trailing blanks at times.

For that reason, for problem determination, I have used:

to add delimiters so that I could 'see' the actual length. (In your later examples, it looks like you use constants, so probably not this case)

I have used several z/OS interfaces. Sometimes the length includes itself and other prefix info and sometimes the length is only the data. (it looks like yours is only data). Please verify.

The length seems to be the problem, perhaps a hex vs. octal problem.

Is there any conversion taking place? (for example, during FTP some conversion is done from ASCII to EBCDIC)

These users thanked the author Pedro for the post:

AllardK (Sat Mar 27, 2021 1:38 pm)