How To Fix D3117 - Job ID &1 unknown; job probably purged on OS/390

SAP Error Message - Details

• Message type: E = Error

• Message class: D3 - CCMS - DB2 on OS390

• Message number: 117

• Message text: Job ID &1 unknown; job probably purged on OS/390

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message D3117 - Job ID &1 unknown; job probably purged on OS/390 ?

  The SAP error message D3117 indicates that a job with a specific Job ID is unknown, and it is likely that the job has been purged from the system on OS/390. This error typically occurs in environments where SAP is running on IBM's OS/390 (now known as z/OS), which is a mainframe operating system.
  Cause:
  
  Job Purging: The most common cause of this error is that the job with the specified Job ID has been purged from the job queue. This can happen due to system settings that automatically delete jobs after a certain period or after they have completed execution.
  Incorrect Job ID: The Job ID specified may be incorrect or may not exist in the system.
  Job Execution Issues: The job may have failed to execute properly, leading to its removal from the job queue.
  
  Solution:
  
  Check Job Status: Verify if the job with the specified Job ID exists in the job queue. You can do this by using transaction codes like SM37 (Job Monitoring) in SAP to check the status of jobs.
  Review Job Logs: If the job was executed but is no longer available, check the job logs for any errors or messages that might indicate why the job was purged.
  Re-run the Job: If the job is indeed purged and you need the results, you may need to re-run the job. Ensure that the job parameters are correct before re-execution.
  Adjust Job Retention Settings: If job purging is a frequent issue, consider adjusting the job retention settings in your system to retain jobs for a longer period.
  Consult System Administrator: If you are unable to resolve the issue, consult your system administrator or SAP Basis team for further assistance. They may have access to system logs and configurations that can provide more insight.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific guidance or patches related to this error message. SAP frequently updates its knowledge base with solutions for known issues.
  System Configuration: Review the configuration settings for job management in your SAP system, especially if you are experiencing this issue frequently.
  Documentation: Refer to the official SAP documentation for job scheduling and monitoring on OS/390/z/OS for best practices and troubleshooting steps.
  
  By following these steps, you should be able to diagnose and resolve the D3117 error in your SAP environment.