Troubleshooting
Problem
Same jobs are submitted to USERJOBS daily and the cleanuserjobs.sh(bat) utility does not resolve.
Symptom
Given a job launched in USERJOBS with job number 1234567890, the cleanuserjobs script returns the following:
$ cleanuserjobs.sh -dbUsr db2user -dbPwd passw0rd -jobnum 1234567890
Setting CLI environment variables....
JOBNUMBER=1234567890---
job number: 1234567890 has not been found in TAJ_TWS_TABLE
Setting CLI environment variables....
JOBNUMBER=1234567890---
job number: 1234567890 has not been found in TAJ_TWS_TABLE
The same job name with a new job number is launched in USERJOBS in the next day's plan.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSGSPN","label":"IBM Workload Scheduler"},"ARM Category":[{"code":"a8m0z0000004ColAAE","label":"Product Operations-\u003EIWS-\u003EScheduling-\u003EDA userjobs cleaning"}],"ARM Case Number":"TS015315026","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
15 March 2024
UID
ibm17116415