Event trace records for System SSL

The FULL format of a component trace report is as follows:

     COMPONENT TRACE FULL FORMAT                                                
     SYSNAME(C01)                                                          
     COMP(GSKSRVR)                                                              
     **** 11/14/2005                                                            
                                                                             
     SYSNAME   MNEMONIC  ENTRY ID    TIME STAMP     DESCRIPTION                 
     -------   --------  --------  ---------------  -------------               

   1 C01       MESSAGE   00000004  20:43:45.522449  SSL_ERROR                     
                                                                               
   2   Job TCP341    Process 00020032  Thread 00000002  gsk_read_v3_record        
   3   Socket closed by 192.168.50.80.1360.

Standard IPCS header line, which includes the system name (C01), System SSL trace entry format (MESSAGE or DUMP), entry ID, time stamp, and record description.
System SSL header line with job name, process id, thread id, and function name information.
System SSL detail information. The format of this area's content is determined according to the System SSL record description located on line 1. Trace records may have 0 or more detail lines.

The standard IPCS header line MNEMONIC, ENTRY ID, and DESCRIPTION combinations are as follows:

MNEMONIC ENTRY ID   DESCRIPTION         EXPLANATION
MESSAGE  00000001   SSL_ENTRY           Entry into the function named in the following System SSL
                                        header line (i.e. line 2) occurred
MESSAGE  00000002   SSL_EXIT            Exit from the function named in the following System SSL
                                        header line occurred
MESSAGE  00000004   SSL_ERROR           Error was detected by the function named in following line 2
                                        with error description in line 3
MESSAGE  00000008   SSL_INFO            Information generated by the function named in following line 2
                                        - for example, supplied parameters
DUMP     00000010   SSL_EBCDIC_DUMP     Dump of buffer contents formatted in EBCDIC, by the function
                                        named in following line 2
DUMP     00000020   SSL_ASCII_DUMP      Dump of buffer contents formatted in ASCII, by the function name
                                        in following line 2

The System SSL header line contains the Job name, Process ID (in hex), Thread ID (in hex), and the name of the System SSL function that created the trace entry. If the trace entry is output while in SRB mode, then the Thread ID is FFFFFFFF .

The format of the System SSL detail line is similar for record descriptions SSL_ENTRY, SSL_EXIT, SSL_ERROR and SSL_INFO.

     1  C01        MESSAGE    00000001   20:43:46.694762   SSL_ENTRY

     2    Job TCP341     Process 00020032    Thread 00000004   gsk_secure_socket_read
     3    Handle 7E828198,  Size 1

     4  C01        MESSAGE    00000008  20:43:46.695013    SSL_INFO

     5    Job TCP341     Process 00020032    Thread 00000004   gsk_read_v3_record
     6    Calling read routine for 5 bytes

     7  C01        MESSAGE    00000004  20:43:46.695317    SSL_ERROR

     8    Job TCP341     Process 00020032    Thread 00000004   gsk_read_v3_record
     9    Socket closed by 192.168.50.80.1472.

    10  C01        MESSAGE    00000004  20:43:46:695478    SSL_ERROR

    11    Job TCP341     Process 00020032    Thread 00000004   gsk_secure_socket_read
    12    SSL V3 data read failed with 192.168.50.80.1472.

    13  C01        MESSAGE    00000002  20:43:46.695599    SSL_EXIT

    14    Job TCP341     Process 00020032    Thread 00000004   gsk_secure_socket_read
    15    Exit status 000001A4 (420)
    16    Length 0

1. The start of a trace record reporting that a function is entered. Not all functions create a trace record. If a function creates an SSL_ENTRY record, then it also creates a corresponding SSL_EXIT record.

2. The System SSL header record describing the job, process, thread, and function creating the record.

3. The detail for the SSL_ENTRY record. Not all trace records create a detail line. Trace records may have multiple detail lines.

4. The start of a trace record for function gsk_read_v3_record. The fact that an SSL_EXIT record is not encountered for function gsk_secure_socket_read (the previous trace record), indicates that gsk_read_v3_record is invoked either by gsk_secure_socket_read or another function invoked by gsk_secure_socket_read.

7. The start of an error trace record created by gsk_read_v3_record.

10. An error trace record created by gsk_secure_socket_read. The error occurred because of the error detected in gsk_read_v3_record.

13. The start of the trace record created by gsk_secure_socket_read on exit. It corresponds with the trace entry record on Line 1.

15. The first detail line and reports the return code returned by gsk_secure_socket_read.

16. The second detail line for the trace record. It is an example of a trace record with multiple detail lines.

The format of the System SSL detail for record descriptions SSL_EBCDIC_DUMP and SSL_ASCII_DUMP is as follows:

 1 C01       DUMP      00000020  20:43:45.724056  SSL_ASCII_DUMP                
                                                                                
 2   Job TCP341    Process 00020032  Thread 00000004  send_v3_server_messages   
 3   SERVER-HELLO message                                                       
 4     00000000: 02000046 03014373 B1011649 3E508E04   *...F..Cs...I>P..*       
       00000010: A620B42C 8422C287 8015BC54 7850C435   *. .,.".....TxP.5*       
       00000020: 540B6864 A4702000 020032C0 A8325005   *T.hd.p ...2..2P.*       
       00000030: E9000000 00000000 00000000 00000043   *...............C*       
       00000040: 73B10100 00051A00 0500                *s.........      *

Standard IPCS header line.
System SSL header line.
The first line of the System SSL detail area. It describes the contents that are dumped in the detail lines. In this example, the SERVER_HELLO message sent to the client is output in the detail lines.
The first line of the contents dump. Each dump line consists of offset, 16 bytes of data in hex, and the same 16 bytes of data output in either ASCII or EBCDIC enclosed in asterisks.