BOI Software Entwicklung und Vertrieb GmbH

Phone: +43 (0) 732 / 736423 - 0

Spazgasse 4

Email: office@boi.at

4040 Linz, Austria

www.boi.at

Generate table with callserver protocol entries

How does it work?

The SSL module $TABX4XCPR is called by the call server to write the protocol entries.

The same module can be used to create a table with the protocol entries. In this case a memory table is created from the status entries in database TABCPR. This memory table is stored with the name $_CSVPRT_$ in database TABTMP.

Preparations and program call

The creation of the table from the callserver protocol entries can be called in batch or online (TSO or Client/Server terminal). Depending on the call a corresponding JCL or call procedure is required.

Description of the call environment

  • A JCL file or call procedure similiar to the TABEX utilities
  • Sysparm specification for the call: M=$TABX4XCPR-CRTTAB
  • Required database allocations
INTMOD-Verkettung 
TABCTL-Verkettung 
OPSMSG-Verkettung 
TABCPR 
TABTMP
Result of program execution

After successful execution a table $_CSVPRT_$ is available in database TABTMP.

Possible cases at program termination:

Case

Exit code

Result table in TABTMP

Comments

Table created with rows

0

yes

message

Empty table created

4

yes

message

Error

8

no

Error message with return code and diagnosis information (contact BOI)

Structure of the generated table

(Extract from documentation BOIDOC_224)

Technical status fields

field name

type

length

content

STA_TABLE

CH

10

status name = host name of the callserver, 1st 10 characters in upper case

STA_VERSION

CH

8

status version = port number (000nnnnn stored in the format YYYYMMDD)

STA_LOAD_DB

CH

8

database name ( = „TABCPR“)

STA_USER

CH

8

user ID of the status writer ( = „BOITPSV“)

STA_DATE

CH

8

date of the status entry (format YYYYMMDD)

STA_TIME

CH

8

time of the status entry (format HH:MM.SS

Callserver identification fields

field name

type

length

content

CPR_HNAME

CH

36

host name of the callserver (36 characters max), mixed case

CPR_PORT

BF

2

port number of the call server

CPR_TSTMP

CH

26

time stamp of status creation (format YYYY-MM-DD-HH.MM.SS.FFFFFF)

Usage counters

field name

type

length

content

CPR_NLNUMACC

BF

8

Native/SSL/Other Local number of calls

CPR_NLNUMBYT

BF

8

Native/SSL/Other Local number of API parameter structure bytes

CPR_NLCONMAX

BF

4

Native/SSL/Other Local maximum number of connections

CPR_NLCONCUR

BF

4

Native/SSL/Other Local current number of connections

CPR_NRNUMACC

BF

8

Native/SSL/Other Remote number of calls

CPR_NRNUMBYT

BF

8

Native/SSL/Other Remote number of API parameter structure bytes

CPR_NRCONMAX

BF

4

Native/SSL/Other Remote maximum number of connections

CPR_NRCONCUR

BF

4

Native/SSL/Other Remote current number of connections

CPR_JLNUMACC

BF

8

Java Local number of calls

CPR_JLNUMBYT

BF

8

Java Local number of API parameter structure bytes

CPR_JLCONMAX

BF

4

Java Local maximum number of connections

CPR_JLCONCUR

BF

4

Java Local current number of connections

CPR_JRNUMACC

BF

8

Java Remote number of calls

CPR_JRNUMBYT

BF

8

Java Remote number of API parameter structure bytes

CPR_JRCONMAX

BF

4

Java Remote maximum number of connections

CPR_JRCONCUR

BF

4

Java Remote current number of connections

Overlay fields for long counters

Additional overlay fields are defined in the table structure over the fields named ...NUMACC and ... NUMBYT. This is because the table editor of pre 4.3.0 TABEX/4 versions did not support the display of binary fields of 8 bytes length. The overlay fields represent the high part and the low part of this fields, each 4 bytes long, and can also be displayed in pre 4.3.0 TABEX/4 versions. The field names of the overlay fields are ...NUMACCH and ...NUMACCL for the high and the low part of field ...NUMACC, and ...NUMBYTH and ...NUMBYTL for the high and the low part of field ...NUMBYT.

Additional fields

field name

type

length

content

CPR_FREE

CH

96

(free, for future use)

Enable protocolling

Protocolling can be turned on, but it cannot be turned off, if it is turned on in the license file. The switches are documented in BOIDOC_224 in the call parameters of the callserver:dokumentiert:

The flags "2C" in the call parameter enable connection log and access log.

Examples:

Windows / Linux / Unix: in boiparam.txt

TPSVPARM    <1998 - 2C> 

z/OS: in the JCL

// PARM=('TRAP(ON),ENVAR("TZ=CET-1CEST") / 1998 - 2C') 
Documentation

BOIDOC_224_cs_admin_en.pdf

Valid from

The protocolling callserver can be installed in the following TABEX/4 versions: Version 4.2.0 Update 2011-12-05 (also named 4.2.0A).

Since TABEX/4 version 4.3.0 the new protocolling callserver is included in the version.

Migration Packages

BOI GmbH offers migration packages for the table management systems SPITAB, TABSYS and VTAS.

 

» Migrations Packages

Success Stories

AirPlus has been using TABEX for 20 years.

Now TABEX/4 JAVA APPLICATION ENGINE has additionally been launched for audit-proof logging of the business processes by Java applications.

 

» read this success story

» more success stories