Troubleshooting
Problem
There are many reasons why a scheduled job can fail within Build Forge. It can fail due to a bad selector, unavailable resources or improper scripting. But what happens when the job fails to start? What if there is no indication of an error message in the UI and or Build Forge error logs. This note should help clarify a common cause for this type of error.
Symptom
A job is scheduled within Rational Build Forge, and it fails to kick off. The job shows no signs of failing, because it never even started. There is no indication of a visible error messages or any information left behind by the job. It's is like it never happened.
[{"Product":{"code":"SSB2MV","label":"Rational Build Forge"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"General Information","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF002","label":"AIX"}],"Version":"7.1.3","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
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:
16 June 2018
UID
swg21627232