> # SequeLink® Debug Log Files

> DataDirect Technologies technical support may ask you to provide a debug log file. SequeLink Server uses the following types of debug log files:

> - Session debug log file contains information related to all server processing in the context of a client session. See the following section, "SequeLink® Server Session Debug Log File" for more information.
> - Service debug log file contains information related to service-related processing-any kind of processing that occurs outside the context of a client session. See "SequeLink® Service Debug Log File" for more information.

> ### SequeLink® Server Session Debug Log File

> The SequeLink Server Session debug log file contains information related to all processing that occurs in the context of a client session. Each debug log file includes a fixed header that contains installation-specific information.

> When you consult DataDirect Technologies technical support, you may be asked for the contents of this log file. The name and location of the SequeLink Server Session debug log file depend on your SequeLink Server platform.

> The information that is logged depends on the value set for the ServiceDebugLogLevel service attribute. By default, logging is enabled for Fatal Error messages. Enabling additional logging levels uses considerable disk space and slows processing. We recommend that you enable these additional levels only while you are troubleshooting. How you turn on and off the logging option depends on your SequeLink Server platform. See "Configuring Logging" for information about setting debug levels.

> #### Session Debug Log File on Windows

> Log File Name:

> The log file name is servicename_sessionid_processid.log where:

> servicename is the name of the SequeLink service.

> sessionid is a unique numeric identifier of the session.

> processid is the numeric process identifier assigned by the operating system for the SequeLink service process.

> Log File Location:

> The ServiceDebugLogPath service attribute specifies the location of the file. For more information about specifying SequeLink service attributes, refer to the SequeLink Administrator's Guide.

> #### Session Debug Log File on UNIX, Linux, and z/OS USS

> Log File Name:

> The log file name is servicename_sessionid_processid.log where:

> servicename is the name of the SequeLink service.

> sessionid is a unique numeric identifier of the session.

> processid is the numeric process identifier assigned by the operating system for the SequeLink service process.

> Log File Location:

> The ServiceDebugLogPath service attribute specifies the location of the file. For more information about specifying SequeLink service attributes, refer to the SequeLink Administrator's Guide.

> #### Session Debug Log File on z/OS

> Log File Name:

> The log file name is Servername_Servicename_Tnnnnnnn.log where:

> Servername is the name of the SequeLink Server started task/Job.

> Servicename is the name of the SequeLink service running within the server.

> nnnnnnn is a unique numeric identifier of the session.

> Log File Location:

> The Session Debug Log Files are located in UNIX System Services hierarchical file system (HFS). The ServiceDebugLogPath service attribute specifies the HFS directory where the Session Debug log files will be created. For more information about specifying SequeLink service attributes, refer to the SequeLink Administrator's Guide.

> ### SequeLink® Service Debug Log File

> The service debug log file contains information about processing that occurs outside the context of a client session. Each debug log file includes a fixed header that contains installation-specific information.

> When you consult DataDirect Technologies technical support, you may be asked for the contents of this log file. The name and location of the SequeLink Service debug log file depend on your SequeLink Server platform.

> The information that is logged depends on the value set for the ServiceDebugLogLevel service attribute. By default, logging is enabled for Fatal Error messages. Enabling additional logging levels uses considerable disk space and slows processing. We recommend that you enable these additional levels only while you are troubleshooting. How you turn on and off the logging option depends on your SequeLink Server platform. See "Configuring Logging" for information about setting debug levels.

> #### Service Debug Log File on Windows

> On Windows, the operator logging facility is the event log. You can access the event log by clicking the Event Viewer icon in the Administrative Tools program group. SequeLink Server logging belongs to the application class, with the service name as the source name.

> The service debug log file is an operating system file called servicename_processid.log where:

> servicename is the name of the SequeLink service.

> processid is the numeric process identifier assigned by the operating system for the SequeLink service process.

> You can choose the messages that you want to view in the event log by using the Filter menu option.

> NOTE: You may need to refresh the Event window to receive the latest logging information.

> #### Service Debug Log File on UNIX and Linux

> The ServiceDebugLogPath service attribute specifies the location of the service debug log file. The service debug log file is an operating system file called servicename_processid.log where:

> servicename is the name of the SequeLink service.

> processid is the numeric process identifier assigned by the operating system for the SequeLink service process.

> Messages are sent to the syslogid infrastructure. By default, the messages are sent as USER type messages; however, you can change the message type by setting the ServiceUnixSyslogFacility service attribute. For more information about specifying SequeLink service attributes, refer to the SequeLink Administrator's Guide.

> #### Service Debug Log File on z/OS

> The Service Debug log file on z/OS records all log messages. See "z/OS Messages and Descriptions" for an explanation of these messages.

> By default, the log file is allocated to DD statement VAILOGP or VAILOGS. We recommend that you allocate the log file to a SYSOUT dataset. This allows you to view all messages online using the z/OS System Display and Search Facility (SDSF).

> 1. Use the SDSF option DA to display a list of the active jobs. Select the SequeLink job using a question mark command and press ENTER. For example:

> NP JOBNAME STEPNAME PROCSTEP JOBID OWNER

> GN00002H DUMP JOB08358 GN00002

> ? GN00002O SQLNK JOB08359 GN00002

> GN00002 LOGISPF4 FBBS080I TSU08354 GN00002

> 2. Select the VAILOGP (primary) or VAILOGS (secondary) log file and press ENTER. The following example shows choosing the VAILOGP log file:

> NP DDNAME STEPNAME PROCSTEP DSID OWNER

> JESMSGLG JES2 2 GN00002

> JESJCL JES2 3 GN00002

> JESYSMSG JES2 4 GN00002

> s VAILOGP SQLNK 104 GN00002

> SYS00001 SQLNK 106 GN00002

> You will now see all SequeLink messages.

> 3. In some special cases, SAS/C runtime library routines write error information into SYSTERM. See "SAS/C Runtime Library Messages" for information on those messages. Select the SYSTERM log file and press ENTER. For example:

> NP DDNAME STEPNAME PROCSTEP DSID OWNER

> JESMSGLG JES2 2 GN00002

> JESJCL JES2 3 GN00002

> JESYSMSG JES2 4 GN00002

> VAILOGP SQLNK 104 GN00002

> S SYSTERM SQLNK 106 GN00002

> Use the SDSF option `LOG` to view the system log when you want to view messages-for example, DB2 messages related to SequeLink.

> #### Configuring Logging

> You configure logging by using the SequeLink Manager to change the ServiceDebugLogLevel service attribute. Depending on the level of logging you set, the log file can contain any of the following types of messages:

> - Fatal Errors
> - Errors
> - Warnings
> - Information
> - Debug
> - SSP Packet log (SequeLink Server Protocol packets in binary format)
> - SSP requests (decoded SSP packets)

> By default, the logging is enabled for Fatal Error messages.

> All Error and Fatal Error messages (for example, an invalid license key encountered message) are logged in a system-wide, platform-specific log facility:

> - On Windows, use the Event Viewer and look for messages in the Application Log where the Source is either SequeLink or the name of the service.
> - On UNIX and Linux, messages are sent to the UNIX or Linux syslog service. The messages will be sent by default as USER type messages (the ServiceUnixSyslogFacility service attribute can be used to change the default message type). The SequeLink administrator can edit the syslog.conf file to configure the actual destination of these messages. Refer to your UNIX or Linux documentation for more information.
> - On z/OS, the SequeLink Server log files, VAILOGP and VAILOGS, are used to log all messages. In addition to the service messages, the SequeLink Server log contains all messages from other components, such as the TCP/IP listener and the DB2 interface. Messages are sent first to VAILOGP, the primary log. When the primary log is almost full, SequeLink Server sends a message to the operator's console to alert you to switch to the secondary log file, VAILOGS.

> ### Configuring Logging Using the SequeLink® Manager Snap-in

> For information about using the SequeLink Manager Snap-in, refer to the SequeLink Administrator's Guide.

> To configure logging:

> 1. Select the service for which you want to obtain a log file.
> 2. Select the Configuration node.
> 3. Select the Service Settings node.
> 4. Select the Logging attribute category.

> 5. Change the properties for the ServiceDebugLogLevel service attribute. Selecting all check boxes on the ServiceDebugLogLevel Properties window will log all possible debug information.
> 6. Save the configuration file.

> The change will take effect for all subsequent connections.

> ### Configuring Logging Using the SequeLink® Manager Command-Line Tool

> Use the SequeLink Manager Command-Line Tool command ServiceDebugLogLevel, which has the format:

>     {ServiceDebugLogLevel | sdll} service_name
>     [ [{dis | disable}]
>     [{enall |  enableall}]
>     [{en | enable}]
>     [{ferr | fatalerror}={off | on}] |
>     [{err | errors=off | on}] |
>     [{war | warnings}={off | on}] |
>     [{info | informationals}={off | on}] |
>     [{debug | debugging}={off | on}] |
>     [{sspp | ssppackets}={off | on}] |
>     [{sspr | ssprequests}={off | on}] | ... ]

> where service_name is the service to which the session belongs. Service names can be obtained using the `ServiceList | sl` command.

> The following example turns on debug messages and turns off error messages in the debug log file for the SLOracle10 data access service:

>     sdll SLOracle10 debug=on err=off

> The change will take effect for all subsequent connections. For information about using the SequeLink Manager Command-Line Tool, refer to the SequeLink Administrator's Guide.

> ### Configuring Logging Using the SequeLink® Manager for z/OS

> For information about using the SequeLink Manager for z/OS, refer to the SequeLink Administrator's Guide.

> 1. From the server management tree, type `/` beside the Service Settings node of the SequeLink service for which you want to obtain a log file. The server management tree shows the attribute categories for the service.
> 2. Type `S` beside the Logging attribute category to select it; then, press ENTER. The AttributeList panel appears.

> NOTES:

> - Your screen may not be able to display all attributes at once. Press F7 and F8 to scroll up and down the attribute list.
> - To display help about an attribute, type `?` beside the attribute; then, press ENTER.
> 3. Type `C` beside the ServiceDebugLogLevel attribute; then, press ENTER. The Attribute Display window appears.

> 4. Type `/` beside one or multiple log options; then, press ENTER. You are returned to the AttributeList panel, and the attribute value, if valid, is changed.
> 5. Press F3 to return to the server management tree.

> The change will take effect for all subsequent connections.