http://www.bicekru.org/~ggv
I think today I'll change it a bit - will add acct-session-id to leg.x

"ничего не понятно в radius."
Can I help somehow?

"зачем у тебя имена очередей приводятся в uppercase, когда они чувствительны к регистру?"
platform - solaris.

define qlocal(My.Queue) + bla-bla-bla
radiusd -X connected correctly, queue name in uppercase. I have found that if queue name is not in uppercase - I won't connect. Probably in the doc there is something about solaris. Will check Linux/Aix

"ползователь офигеет -- это мы проходили..."
Thank - fixed.

Any other suggestions?
Thank you NewYear.
Could you have a look at http://bicekru.org/~ggv/doc ?
Any notes/suggestions are welcome.

Oops, forgot to say - file mq.c, line 138
pmo.Options |= MQPMO_SYNCPOINT;

And - it's nit for one PUT.
FreeRADIUS is multithreaded application, and each thread will serve many accounting request, each one accounting request will be a message and requires PUT and MQCMIT.

"чтобы создалась не в uppercase, нужно взять ее в кавычки -- MQSC" - got it, thanks. probably I did not read the doc carefully, but I did not remember something about queue names.
Now I may get out upper().

There is an error - one MQHCONN shared by all threads of the same instance of the module.
It means MQBACK or MQCMIT in one thread will commit/rollbak work in others.
Fixing.

Programmers guide, file csqzal09.pdf, page 91, section "Scope of MQCONN or MQCONNX"
"Within WebSphere MQ for iSeries, MQSeries for Compaq OpenVMS
Alpha, MQSeries for OS/2 Warp, WebSphere MQ on Unix systems
and WebSphere MQ for WIndows, the scope of an MQCONN or
MQCONNX call is usually the thread that issued it. That is,
the connection handle returned from the call is valid only
within the thread that issued the call.
............
If you have multiple threads in your application and each
wishes to use WebSphere MQ calls, each one must individually
issue MQCONN or MQCONNX."

page 94
"In the normal MQI environment the default value is
MQCNO_HANDLE_SHARE_NONE"

NewYear - just a simple example.

#include <stdio.h>
#include <stdlib.h>
#include <cmqc.h>
#include <pthread.h>
#include <unistd.h>

static void *dowork(void *arg){

MQHCONN mqconn;
MQLONG CompCode, Reason;

MQCNO Connect_options = {MQCNO_DEFAULT};

MQCONNX("sms", &Connect_options, &mqconn, &CompCode, &Reason);

if(CompCode != MQCC_OK){

fprintf(stderr, "Connection returned %ld\n", (long)Reason);
return NULL;

}
printf("thread %ld connected\n", (long)pthread_self());

sleep(10);
return NULL;

}

int main(){

pthread_attr_t attr;
pthread_t tid;
int i;

if(pthread_attr_init(&attr) != 0){

fprintf(stderr, "could not init attr\n");
exit(1);

}

for(i=0; i<3; ++i){

if(pthread_create(&tid, &attr, dowork, NULL) != 0){

fprintf(stderr, "Could not create thread\n");
exit(1);

}
}
sleep(15);
return 0;

}

cc -I /opt/mqm/inc/ -L /opt/mqm/lib -l mqm -mt test.c
or
gcc -Wall -I /opt/mqm/inc/ -L /opt/mqm/lib -l mqm test.c
and we got
./a.out
thread 3 connected
thread 2 connected
thread 4 connected

rlm_mq got an logical error. I have taken a logic from existing rlm_sql, and just changed SQL stuff to MQ stuff.
This was my mistake :) Ok, will fix.
but MQCONN works in threads as described in the doc.

Here how it is - two post above when I put a quotation from page 91, and I did skip very important statement.
"If it is used from a different thread, it will be rejected as invalid".
That's it. It means there is not way to make a pool of MQHCONN and use them from threads.
Actually, rlm_mq is new stuff, was not used before, before I used door_x (3door) - SUN door interface, where each request from freeradius passed to door-server, and server created a new thread, which created each own MQHCONN. But door_x () is not portable.
Anyhow, everything is clear now. Each thread has to create each own MQHCONN, otherways - Reason 2018.

s/otherways/otherwise blin