![]() ![]() SAVOBJ OBJ(QODB nnnnnn) LIB(QUSRSYS) DEV(*SAVF) SAVF(YOURLIB/DBMONSAVF)ĭownload the save file to your PC by using FTP in binary format. Then, run the following command to save the DBMON output into the new save file: Replace YOURLIB with the name of the library where you want to create the SAVF. Run the following IBM i command to create a save file to store the DBMON output: From there, the file can be attached to the case or it can be uploaded to the Support Center FTP site. Create a save file, save the database monitor report to the save file, and binary FTP it to your PC. ![]() The database monitor creates an output file QUSRSYS/QODB nnnnnn where nnnnnn is the job number of the ODBC job (the job number is in the QPJOBLOG file). Step 7: Copy the DBMON output to your PC. Send the files to the IBM i Global Support Center in step 9 Click the 'OK' button to confirm the download. Select the spooled files and click 'Export as' then 'ASCII text' from the 'Actions' menu. If the trace connection was run under a different user ID, select 'Include.' from the 'Actions' menu and change the user ID to the user ID that was used to collect the trace or make the ODBC connection. The spooled files created are QPJOBLOG (debug job log), QPSRVTRC (job trace), and QPCSMPRT (connection trace). Step 6: Locate the spooled files generated by the debug job log, the TRCJOB, and the connection trace and copy them to your PC.Įxpand your system name, Basic Operations, and select Printer Output. TRCCNN SET(*OFF) TRCTBL(MYTRCTBL) FMTDTA(*CALC) To stop the trace, on the operating system command line, type the following: Step 5: End and format the TCP/IP connection trace. Step 4: Re-create the error on the test PC. TRCCNN SET(*ON) TRCTYPE(*IP) TRCTBL(MYTRCTBL) SIZE(128000) TCPDTA(*TCP () () ) To trace all TCP/IP addresses, on the i5/OS command line, type the following: Replace with the IP address of the PC or client used to re-create the problem. Note: The minimum recommended trace size is 128000 KB/128 MB. To trace a specific PC TCP/IP address, on the i5/OS command line, type the following: We recommend starting the trace from a different PC to minimize the size of the trace. To circumvent the problem, see Gathering an ODBC Traceįrom a different PC, start a PC5250 session and start a TCP/IP connection trace. The ODBC trace might fail to start for applications that run as a Windows service. Use the cwbcotrc to capture detail information as described in document, Gathering an ODBC Trace. Step 2b: Start the cwbcotrc trace with detail information. ![]() Press the Help button or the F1 key for further information. The user profile being traced must be authorized to the trace commands and to the QUSRSYS library. Select the Diagnostic tab and set the options specified by IBM support (tracing, database monitor, debug job log, and trace job). For more information about collecting client-side traces, see Gathering an ODBC Trace.Ĭontinuing in ODBC Administration, select the data source being used and press the Configure button. Click the Apply button after you set the path, then click Start Tracing Now. In the following example, the log file is set to "C:\Users\Public\Documents\SQL.LOG". On Windows Vista and newer operating systems, the equivalent path is "C:\Users\Public\Documents". Note, Windows Explorer often displays this folder as "Shared Documents". In Windows XP and older systems, the path is typically "C:\Documents And Settings\All Users\Documents". In order to be sure that Windows authorities do not prevent the trace file from being created, we recommend that you change the log file path for the trace to point to the public documents folder. Note: The user profile used for the ODBC connection must be authorized to the job trace and DBMON commands. On the PC, it starts an ODBC trace and an IBM i Access cwbcotrc trace. It starts a job trace, a debug job log, a communications trace, and a database monitor trace on IBM i. Releaseįollowing is the process for capturing the traces commonly required for ODBC problem determination. The corrective PTFs are required only when the defective PTF listed is applied. IMPORTANT: Before you start a TRCCNN or TRCINT command, ensure that you have the corrective PTFs for APAR MA48477 applied to your system. ![]()
0 Comments
Leave a Reply. |