Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

RFC can't set AUDITLEVEL for detail in rz15

I'm doing BC-XOM testing.  After establishing an RFC connection, the code calls BAPI_XMI_LOGON, and BAPI_XMI_SET_AUDITLEVEL before continuing on with the SXMI_XOM_* functions of the BC-XOM callback interface.  All calls work, but for unknown reasons, either AUDITLEVEL is not being set or logged messages aren't being displayed in rz15.  All that appears in rz15 are the 'Setting audit level to 3' (or whatever level I'm requesting) and 'Logging off interface XOM' messages.  The XOM logon and all the other XOM function calls do not appear.

I'm testing against a Suse 11 Linux 720 NPL Testdrive system using the NWRFC libraries 721 Patch 38.  I've tried calling from both the SUSE system itself and an external HP-UX Itanium system.  We also have an ancient Windows minisap 7.01 NSP trial system.  It does the same thing, except it catches the BAPI_XMI_LOGON's in addition to setting auditlevel and logging off.

This feels like there is some setting on these systems that is not set correct.  I'm lazy (and not at all SAP savvy) so used the supplied NPL DEVELOPER/NSP BCUSER super user accounts for the RFC and XMI logons.  I have screen captures of audit level 3 working nicely with with the old N4S Linux trial system that we used until SAP dropped it.  Rz15 shows all functions.  That was with the classic RFC library, but running the classic library against the current systems makes no difference.

Here's a debug of the RFC calls, using a routine which is based on code from helperFunctions.c which was with the NWRFC SDK Advanced Topics articles.  Nesting is indicated by periods instead of tabs.   Rfc_invoke is my wrapper function around RfcInvoke.  It checks both rc and RFC_ERROR_INFO's code field.   I can get the rfc developer trace output too.

Mon Jan 11 18:20:39 2016 calling BAPI_XMI_LOGON ---------------------------

Mon Jan 11 18:20:39 2016 BAPI_XMI_LOGON rfc_invoke returned rc 0 code 0

Mon Jan 11 18:20:39 2016 IMPORT entries:

Mon Jan 11 18:20:39 2016 .EXTCOMPANY, RFCTYPE_CHAR[16:16]:PlusTechnologies

Mon Jan 11 18:20:39 2016 .EXTPRODUCT, RFCTYPE_CHAR[16:7]:OM PLUS

Mon Jan 11 18:20:39 2016 .INTERFACE, RFCTYPE_CHAR[3:3]:XOM

Mon Jan 11 18:20:39 2016 .VERSION, RFCTYPE_CHAR[10:3]:0.1

Mon Jan 11 18:20:39 2016 EXPORT entries:

Mon Jan 11 18:20:39 2016 .structure RETURN

Mon Jan 11 18:20:39 2016 ..TYPE RFCTYPE_CHAR[1:0]:

Mon Jan 11 18:20:39 2016 ..ID RFCTYPE_CHAR[20:0]:

Mon Jan 11 18:20:39 2016 ..NUMBER RFCTYPE_NUM[3:3]:000

Mon Jan 11 18:20:39 2016 ..MESSAGE RFCTYPE_CHAR[220:0]:

Mon Jan 11 18:20:39 2016 ..LOG_NO RFCTYPE_CHAR[20:0]:

Mon Jan 11 18:20:39 2016 ..LOG_MSG_NO RFCTYPE_NUM[6:6]:000000

Mon Jan 11 18:20:39 2016 ..MESSAGE_V1 RFCTYPE_CHAR[50:0]:

Mon Jan 11 18:20:39 2016 ..MESSAGE_V2 RFCTYPE_CHAR[50:0]:

Mon Jan 11 18:20:39 2016 ..MESSAGE_V3 RFCTYPE_CHAR[50:0]:

Mon Jan 11 18:20:39 2016 ..MESSAGE_V4 RFCTYPE_CHAR[50:0]:

Mon Jan 11 18:20:39 2016 ..PARAMETER RFCTYPE_CHAR[32:0]:

Mon Jan 11 18:20:39 2016 ..ROW RFCTYPE_INT[4:1]:0

Mon Jan 11 18:20:39 2016 ..FIELD RFCTYPE_CHAR[30:0]:

Mon Jan 11 18:20:39 2016 ..SYSTEM RFCTYPE_CHAR[10:0]:

Mon Jan 11 18:20:39 2016 .SESSIONID, RFCTYPE_CHAR[24:24]:C0A8EA2A255C569438C70046

Mon Jan 11 18:20:39 2016 calling BAPI_XMI_SET_AUDITLEVEL ---------------------------

Mon Jan 11 18:20:39 2016 BAPI_XMI_SET_AUDITLEVEL rfc_invoke returned rc 0 code 0

Mon Jan 11 18:20:39 2016 IMPORT entries:

Mon Jan 11 18:20:39 2016 .AUDITLEVEL, RFCTYPE_NUM[1:1]:3

Mon Jan 11 18:20:39 2016 EXPORT entries:

Mon Jan 11 18:20:39 2016 .structure RETURN

Mon Jan 11 18:20:39 2016 ..TYPE RFCTYPE_CHAR[1:0]:

Mon Jan 11 18:20:39 2016 ..ID RFCTYPE_CHAR[20:0]:

Mon Jan 11 18:20:39 2016 ..NUMBER RFCTYPE_NUM[3:3]:000

Mon Jan 11 18:20:39 2016 ..MESSAGE RFCTYPE_CHAR[220:0]:

Mon Jan 11 18:20:39 2016 ..LOG_NO RFCTYPE_CHAR[20:0]:

Mon Jan 11 18:20:39 2016 ..LOG_MSG_NO RFCTYPE_NUM[6:6]:000000

Mon Jan 11 18:20:39 2016 ..MESSAGE_V1 RFCTYPE_CHAR[50:0]:

Mon Jan 11 18:20:39 2016 ..MESSAGE_V2 RFCTYPE_CHAR[50:0]:

Mon Jan 11 18:20:39 2016 ..MESSAGE_V3 RFCTYPE_CHAR[50:0]:

Mon Jan 11 18:20:39 2016 ..MESSAGE_V4 RFCTYPE_CHAR[50:0]:

Mon Jan 11 18:20:39 2016 ..PARAMETER RFCTYPE_CHAR[32:0]:

Mon Jan 11 18:20:39 2016 ..ROW RFCTYPE_INT[4:1]:0

Mon Jan 11 18:20:39 2016 ..FIELD RFCTYPE_CHAR[30:0]:

Mon Jan 11 18:20:39 2016 ..SYSTEM RFCTYPE_CHAR[10:0]:

Suggestions would be greatly appreciated!

Rich

Tags:
replied

>>So would I take your answer to mean that AUDITLEVEL is pretty much useless?  (Is that the answer for this thread??)  Is it good for anything??

I can't tell for other utilization for XMI. But for XOM AUDITLEVEL is not used to get THAT information you intend to get.

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question