IBM Support

MustGather: General Database - SLIC

Troubleshooting


Problem

This document describes what information to collect when the error messages in the job log has a TO or FROM programs begin with #db.

Resolving The Problem


For issues concerning general Database - SLIC issues this document includes the recommended data collection for debug.
General Database - SLIC issues are when the error messages in the job log has a TO or FROM programs begin with #db. 
This is by no means all inclusive; however, it is meant as a starting point for document collection.

If you encounter a General Database SLIC issue, collect the following information using either method A or method B as it is related to the issue:
Method A - QMGTOOLS
Data collection:

1. Issue ADDLIBLE QMGTOOLS

2. Issue GO MG

3. Take option 6 - Database menu

4. Take option 1- General database

5. Set the following parameters:

Failing Job Name - The fully qualified job that encountered the problem.

File Name and Library - to a known file and library name that is reporting errors.

Journal Name and Library - if the file is journaled set to journal name and library that journals the known file reporting errors.



9. Press enter

10. Put in full PMR number and specify FTP option.

Use *STDFTP for standard FTP / *BDFTP for Blue Diamond Customers / *NO to not FTP.

NOTE: if *NO is used for FTP then you must manually send data to IBM using the section in Method B below titled Direction for transferring files to IBM if MGTOOLS was NOT used.

Method B - Manual Collection

PTF information:

1. Version, release, and modification level of system (for example, V5R4M5, V6R1M0, and so on).

2. Issue WRKPTFGRP and press Enter; then press F6 to print a spooled file.

3. Issue DSPPTF OUTPUT(*PRINT)

Data Collection:

1. Issue DSPLOG PERIOD((TIME DATE) (TIME DATE)) OUTPUT(*PRTSECLVL)

Note: Replace Period with 10 minutes before and 10 minutes after the issue occurred.

2. Issue DSPJOBLOG JOB(NUMBER/QUSER/JOBNAME) OUTPUT(*PRINT)

Note: Replace Job with the job that encountered the issue.

3. Vlogs:

A. Issue the STRSST command.
B. Select Option 1. Start a service tool.
C. Select Option 5. Licensed Internal Code log.
D. Select Option 2. Dump entries to printer from the Licensed Internal Code log.
E. Select Dump Option 1 1=Header
F. Press Enter.
G. Select Dump option 3 3=Header and entire entry
H. Specify the date and time of 10 minutes before and 10 minutes after the problem occurred.
I. Press Enter.
J. Press F12 to exit.
K. Select Option 7. Display the status of the Licensed Internal Code log.
L. Refresh until Dump requests not complete is zero.
M. Press F3 three times,and exit out of service tool.Check QSYSOPR for messages.

Re-Create information to collect and how

Re-creates consist of all the necessary objects to recreate the problem on our system. This includes file network, programs, or SQL statements and instructions for re-creating the error. All objects can be saved using SAVOBJ or SAVLIB commands.

** All spool files and save file generated from above steps needs to be sent to IBM. **
 
Direction for transferring files to IBM if MGTOOLS was NOT used

Refer to DCF doc - MustGather: Instructions for Sending Data to IBM i Support - http://www.ibm.com/support/docview.wss?uid=nas8N1019224
 

[{"Product":{"code":"SWG60","label":"IBM i"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"DB2 for IBM i","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Historical Number

N1012161

Document Information

Modified date:
02 October 2020

UID

nas8N1012161