IBM Support

MustGather: Journal Issues

Troubleshooting


Problem

This document describes the necessary information that needs to be collected to aid in quicker resolution of IBM i journal issues.

Resolving The Problem


For issues concerning journal issues, this document includes the recommended data collection for debug. This is by no means all inclusive; however, it is meant as a starting point for document collection.

Journal issues specific MustGather information
 
If you encounter a journal 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. ADDLIBLE QMGTOOLS

2. GO MG
 
3. Option 13 - Check IBM for updated QMGTOOLS

4. Option 6 - Database menu

5. Option 3 - Journal

6. Set the journal name and library to the journal that is reporting an issue and the date and time of error.
Use DSPJOB OPTION(*DFNA) and page down once for values to use for Date format, Date separator, Time separator.

JRNINFO_panel
 

7. Press Enter to set Case information.

8. Put in full Case number and specify FTP option
 
    Anonymous is no longer allowed (GDPR) - Supported FTP options (Search for FTP Type)
 
NOTE: if *NO is used for FTP then you must manually send data to IBM via
MustGather: Instructions for Sending Data to IBM i Support

9. Press Enter to start and send data collection.
 
 
 
QMGTOOLS IFS
 
You are done if you used QMGTOOLS - update the Case that the data has been collected and sent uploaded to Case.
 
 
 
 
 
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)

4. PTF levels of the From and To program if an error message is involved:

o Look at the job log to locate the From and To program (example below).
o Issue DSPOBJD OBJ(QSYS/FromPGM) OBJTYPE(*PGM or *SRVPGM) DETAIL(*SERVICE) OUTPUT(*PRINT)
o Issue DSPOBJD OBJ(QSYS/ToPGM) OBJTYPE(*PGM or *SRVPGM) DETAIL(*SERVICE) OUTPUT(*PRINT)

Note: Change the FromPGM and ToPGM to the programs listed in the job log. Use WRKOBJ on the program to determine if OBJTYPE is *PGM or *SRVPGM.
If there is no library listed or program starts with #, skip that one.

Example:
CPD4342 - 40 02/25/10 18:30:53,112435 QQQVALID QSYS *STMT QSQRUN1 QSYS *STMT

The program QQQVALID is the FromPGM.
The program QSQRUN1 is the ToPGM.

DSPOBJD OBJ(QSYS/QQQVALID) OBJTYPE(*PGM) DETAIL(*SERVICE) OUTPUT(*PRINT)
DSPOBJD OBJ(QSYS/QSQRUN1) OBJTYPE(*SRVPGM) DETAIL(*SERVICE) OUTPUT(*PRINT)

Save of the Journal and Journal Receiver:
1. Issue CRTLIB QIBMDATA

2. Issue CRTSAVF QIBMDATA/SAVE1

3. Issue SAVOBJ OBJ(JOURNAL JOURNALRCV) LIB(LIB) DEV(*SAVF)
SAVF(QIBMDATA/SAVE1)

Data collection:
1. Issue WRKJRNA JRN(LIBNAME/JRNNAME) OUTPUT(*PRINT)

NOTE Replace JRNNAME with Journal name and LIBNAME with Library.

2. Date and time of when the problem occurred.

3. Send in API or CL command used when error is seen

4. Issue CHGJOB JOB(*) LOG(4 00 *SECLVL) LOGCLPGM(*YES)

5. Issue STRTRC SSNID(TRACE1) MAXSTG(4000000)

Note: Set the MAXSTG as large as you can.

6. Recreate the journal issue in this interactive job

7. Issue ENDTRC SSNID(TRACE1) DTALIB(QIBMDATA) PRTTRC(*YES)

8. Issue DSPJOBLOG JOB(*) OUTPUT(*PRINT)

9. QHST information (two parts)
 
DSPLOG PERIOD((*AVAIL *BEGIN)) OUTPUT(*PRTSECLVL)
MSGID(CPA705E CPF2114 CPF7013 CPF7018 CPF7019 CPF701A CPF701B CPF7020 CPF7023
CPF7024 CPF7099 CPF9803 CPI0C04 CPI70E1 CPI70E2 CPI70E3 CPI70E5 CPI70E6 CPI70E7)

 &

DSPLOG PERIOD((*AVAIL *BEGIN)) OUTPUT(*PRTSECLVL) MSGID(*ALL)



10. If an IPL has not been performed since the problem occurred, you should do the following:

A. Issue the WRKACTJOB JOB(*SYS) command.
B. Press F11 two times.
C. Write down the job numbers for each job (QDBSRV02 / QDBSRV03)
D. Issue DSPJOBLOG JOB(Job Number/QSYS/QDBSRV02) OUTPUT(*PRINT)
E. Issue DSPJOBLOG JOB(Job Number/QSYS/QDBSRV03) OUTPUT(*PRINT)

If an IPL has been performed, you should do the following:

A. Issue the WRKJOB JOB(QDBSRV02) command and select the job in OUTQ.
B. Select Option 4 and review the QPJOBLOG spooled file to determine if the problem happened during the
timeframe of the job.
C. Repeat for QDBSRV03.CHGSYSLIBL QSYS2924 (Note: Only to be run for non-English systems where
QSYS2924 exists.)

12. 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.

** All spool files and save file generated from above steps needs to be sent to IBM. **
  

Direction for transferring files to IBM if QMGTOOLS was NOT used


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


 

Document Location

Worldwide

[{"Type":"SW","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CGIAA2","label":"IBM i Db2-\u003EJournal"},{"code":"a8m0z0000000CHbAAM","label":"IBM i Db2-\u003EMustGather Database"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Version(s)"}]

Historical Number

N1012244

Document Information

Modified date:
20 November 2025

UID

nas8N1012244