EntireX Accounting SMF Data

, ,
1

Where can I find an updated layout of the accounting data fields for EntireX V.8.0.1?
My client has discrepancies on a few fields after the SMF data were extracted, for example fields:

input @142 CLIPUID length 28

.P…ÖI…S752ENTX…ETB235 8.0.1.09MVS …@…CSTRGZ …~…m… .8

The attached document reads and displays SMF broker accounting records.

Which customer has experiences in EntireX accounting (SMF)? Please answer or contact me offline: dstorr@storrconsulting.com.

Thanks,
Dieter Storr
EntireX-Broker-SMF.txt (1.77 KB)

2

Dieter, this is the most recent documentation:

http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/wmsuite8_ga/EntireX/adminGeneral/accounting.htm#EntireX_Communicator_Accounting_Data_Fields

Does this fit would what you see in the SMF data ?

3

Hi Rolf,

Please see the attached SMF record. It’s a text file with hex translation. I selected record type 215 from the original SMF layout by using SMFUTIL.

I then compared the layout with your delivered EXXSACT example ‘SAS Sample for EntireX Conversation Accounting Records’ and also with the document you pointed out. Some fields don’t match.

Can you please shed some light on this. For example offset 142 should be the CLIPUID with 28 bytes

Other fields:

@1 OSFLAG IB1. /* OS FLAG (SHOULD BE X’1E’) /
@2 SMFTYPE PIB1. / SMF RECORD TYPE /
@ ;
IF SMFTYPE = &TYPE ;
INPUT
@3 SMFTIME SMFSTAMP8. / TIME RECORD WRITTEN TO SMF /
@11 SMFSYSID $4. / SYSTEM ID /
@15 SUBSYS $4. / SUBSYSTEM NAME /
@19 SUBTYPE IB2. / RECORD SUBTYPE: /
/ 1 - ENTIREX BROKER /
/ 2 - ENTIREX BROKER SVCS /
@21 REGIONID $32. / REGION IDENTIFIER /
@53 VERSION $8. / ENTIREX VERSION /
@61 PLATFORM $8. / RUNNING OS PLATFORM /
@69 REGSTART SMFSTAMP8. / REGION START TIME /
@77 ENTXREC $1. / ENTIREX RECORD TYPE /
/ C - CONVERSATION RECORD /
@78 CLIUID $32. / CLIENT USER ID /
@110 CLITOKEN $32. / CLIENT TOKEN /
@142 CLIPUID $28. / CLIENT PHYSICAL USER ID /
@170 CLICTYP PIB1. / CLIENT COMMUNICATION TYPE /
@173 CLIREQ IB4. / CLIENT REQUEST COUNTER /
@177 CLISBYT IB4. / CLIENT BYTES SENT /
@181 CLIRBYT IB4. / CLIENT BYTES RECEIVED /
@185 CLISMSG IB4. / CLIENT MESSAGES SENT /
@189 CLIRMSG IB4. / CLIENT MESSAGES RECEIVED /
@194 CLISUOW IB4. / CLIENT UOWS SENT /
@197 CLIRUOW IB4. / CLIENT UOWS RECEIVED /
@201 CLICOMP IB4. / CLIENT COMPLETION CODE /
@205 SRVUID $32. / SERVER USER ID /
@237 SRVTOKEN $32. / SERVER TOKEN /
@269 SRVPUID $28. / SERVER PHYSICAL USER ID /
@297 SRVCTYP PIB1. / SERVER COMMUNICATION TYPE /
@301 SRVREQ IB4. / SERVER REQUEST COUNTER /
@305 SRVSBYT IB4. / SERVER BYTES SENT /
@309 SRVRBYT IB4. / SERVER BYTES RECEIVED /
@313 SRVSMSG IB4. / SERVER MESSAGES SENT /
@317 SRVRMSG IB4. / SERVER MESSAGES RECEIVED /
@321 SRVSUOW IB4. / SERVER UOWS SENT /
@325 SRVRUOW IB4. / SERVER UOWS RECEIVED /
@329 SRVCOMP IB4. / SERVER COMPLETION CODE /
@333 CONVID $16. / CONVERSATION ID /
@349 SCLASS $32. / SERVER CLASS NAME /
@381 SSERVER $32. / SERVER NAME /
@413 SSERVICE $32. / SERVICE NAME /
@445 CIDSW $1. / CID= SWITCH /
/ N - CID=NONE /
@450 RESSW $1. / RESTART SWITCH /
/ R - OPT=RESTART /
@453 CONVST SMFSTAMP8. / CONVERSATION START TIME /
@461 CONVEND SMFSTAMP8. / CONVERSATION END TIME /
@469 CONVCPU IB4. / CONVERSATION CPU TIME /
/ IN MICROSECONDS */
Thanks,
Dieter
EntireX-Broker-SMF-hex-record.txt (2.85 KB)

4

Rolf,
Please see the attached excel list. At least the fields CLIPUID and SRVPUID doen’t fit. Do you have a newer example of EXXSACT example ‘SAS Sample for EntireX Conversation Accounting Records’ ?

Either the description is wrong or the content of the fields.

Please let me know whether I should open a service request.

Thanks,
Dieter
Copy of BrokerAccounting1.xls (155 KB)

5

Hi Dieter,

for me this looks okay :o

The CLIPUID and SRVPUID field contain the physical userid of the client/server. In general this is a binary value. Very often this is alphanumeric data in either ASCII (if the client/server runs on Win/Unix) or EBCDIC (on mainframe), but it could even be a mixture or real binary data.

6

I also have a small problem with the SMF accounting data. I activated the accounting-version=3 parameter. After I selected the written SMF-records, I was surprised to see that the field regarding RPC information like Application library and subprogram were not filled in and still contained binary zeroes.

Have I forgotten something?

7

They are only available if they are provided by the RPC Client and/or Server. So you need an up-to-date version of your RPC runtime components. In case of Natural you probably have to set the ACIVERS to 9.