Address code analysis issues

[ric-plt/lib/rmr.git] / doc / src / man / rmr_str2xact.3.xfm

diff --git a/doc/src/man/rmr_str2xact.3.xfm b/doc/src/man/rmr_str2xact.3.xfm
index 1f14cd6..e27c5f6 100644 (file)
--- a/doc/src/man/rmr_str2xact.3.xfm
+++ b/doc/src/man/rmr_str2xact.3.xfm
@@ -1,4 +1,3 @@
-
 .if false
 ==================================================================================
        Copyright (c) 2019 Nokia 
@@ -25,19 +24,8 @@
        Date            8 March 2019
 .fi
 
-.** if formatting with tfm, the roff.im will cause roff output to be generated
-.** if formatting with pfm, then pretty postscript will be generated
 .gv e LIB lib
-.if pfm
-       .im &{lib}/generic_ps.im
-.ei
-       .gv e OUTPUT_RST use_rst
-       .if .ev &use_rst 1 = 
-               .im &{lib}/rst.im
-       .ei
-               .im &{lib}/roff.im
-       .fi
-.fi
+.im &{lib}/man/setup.im 
 
 &line_len(6i)
 
@@ -60,7 +48,7 @@ The &cw(rmr_str2xact) function will copy the string pointed to by src to the
 transaction ID (xaction) field in the given message.  
 The field is a fixed length, gated by the constant &cw(RMR_MAX_XID) and if string length is larger
 than this value, then &bold(nothing) will be copied. (Note, this differs slightly from the
-behaviour of the &cw( lrmr_bytes2xact() ) function.)
+behaviour of the &cw(lrmr_bytes2xact()) function.)
 
 &beg_dlist(.75i : ^&bold_font )
 &h2(RETURN VALUE)
@@ -83,12 +71,15 @@ If the return value is not RMR_OK, then it will be set to one of the values belo
 
 
 &h2(SEE ALSO )
+.ju off
 rmr_alloc_msg(3),
 rmr_bytes2meid(3),
 rmr_bytes2xact(3),
 rmr_call(3),
 rmr_free_msg(3),
+rmr_get_meid(3),
 rmr_get_rcvfd(3),
+rmr_get_xact(3),
 rmr_payload_size(3),
 rmr_send_msg(3),
 rmr_rcv_msg(3),
@@ -103,5 +94,5 @@ rmr_ring_free(3),
 rmr_str2meid(3),
 rmr_wh_open(3),
 rmr_wh_send_msg(3)
-.qu
+.ju on