IBM Support

Debugging OA CLEANUP Problems

Troubleshooting


Problem

This document provides information on what to examine if OA cleanup does not work properly.

Resolving The Problem

Tip: OA cleanup runs under profile QPGMR.

NOTE:
You will not see option 1. Change cleanup options unless you have *ALLOBJ, *SECADM and *JOBCTL authority for your user profile.


If it looks like jobs are running but cleanup is not running, do the following:

1.
To reset the bits in the indexes, on the operating system command line, type the following:

ENDCLNUP

Press the Enter key. (Do not prompt.)

CHGCLNUP

Press the Enter key.

STRCLNUP

Press the Enter key.

This sequence resets QIPLDATTIM.

Note: Ensure the STRCLNUP command is in the system start-up program (sysval QSTRUPPGM). This will allow cleanup to automatically restart after each IPL.

2.
To check what is in the CHGCLNUP, do the following:

CHGCLNUP (prompt using F4)
Allow cleanup *YES
Job queue QCTL (usually QCTL, but not always)
Library *LIBL

3.
To verify if QSYSSCD (the scheduler) is active, do the following:

WRKACTJOB

Is QSYSSCD running under QCTL or another subsystem? The function that is running is QEZSCNEP.

4.
If the job queue is on hold or not running, on the operating system command line type the following:

WRKJOBQ for QCTL *LIBL

where QCTL is the job queue. Press the Enter key. This must say RLS/SBS. If the job queue is on hold, you must STRSBS.

5.
Check for multiple QCTLs in different libraries. You may be using the wrong subsystem without knowing it. On the command line, type the following:

WRKOBJ QCTL

Press the Enter key.

6.
If the job queue is held on the queue, on the command line type the following:

WRKJOBD for QPGMR

Press the Enter key. On the third line, you should see Hold on job queue *NO.

7.
What is the status of QSYSSCD? On the command line, type the following.

WRKUSRJOB for QPGMR

Press the Enter key. It should say Active (Intermediate) or Running (Basic).

8.
Verify that the subsystem description for QCTL or whatever subsystem you are using looks correct. On the  command line, type the following:

WRKSBSD for QCTL

Press the Enter key.
Select Option 5, Display.
Select Option 30, All.
On first screen, maximum jobs in subsystem should say *NOMAX or some number greater than 1.
Verify all other screens look okay (compare to ours).

9.
To get OA to do an automatic power on, it must have been powered off through OA. (Check for APAR.)

10.
If you have a user-defined subsystem and you are not using QCTL, verify the following:

CHGCLNUP and press the F4 key.

Job queue entry: QCTL2 (for example).
WRKSBSD for QCTL2.
Select Option 5 display, then select Option 6 to examine the job queue entry for QCTL2 (this must match the information above).


Make sure that the job queue to which the Start Cleanup (STRCLNUP) command is submitted has the Maximum jobs parameter set to *NOMAX or a number greater than 1. Because the QSYSSCD job always runs, the other jobs that perform automatic cleanup and turn-off functions are not able to start if the Maximum jobs parameter is set to 1.
To change the Maximum jobs parameter on the job queue entry, use the Change Job Queue Entry (CHGJOBQE) command.

If need to report the issue, collect the data from MustGather: OA Cleanup document.

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CReAAM","label":"Operational Assistant"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Document Information

More support for:
IBM i

Component:
Operational Assistant

Software version:
All Versions

Operating system(s):
IBM i

Document number:
635033

Modified date:
30 July 2021

UID

nas8N1013257

Manage My Notification Subscriptions