Troubleshooting Problems Opening JDBG Files
Issues Opening JDBG Files
Project JEDI Isn't There
When you double-click your JDBG file, you may see a dialog box from your operating system stating that it "Cannot Open This File Type". When this happens, it is commonly due to Project JEDI missing in %%os%%. The typical path of opening your JDBG with a double-click won't work because %%os%% cannot make the program connection.
Tip: Another JDBG-related program can be selected to open the file by clicking "Show Apps" and finding the application.
Outdated Project JEDI
Sometimes your installed version of Project JEDI won't support your Embedded JCL Debug Information file. Visit the Open Source website to download (or purchase) the latest version of Project JEDI. Your Embedded JCL Debug Information file was probably created by a newer release of Project JEDI than what's currently installed your computer.
Tip: You can sometimes get hints about the right program version by right-clicking on the JDBG file, selecting "Properties", and looking at the version information.
Primarily, problems experienced when opening JDBG files are due to having the incorrect version of Project JEDI installed on your computer.
Other JDBG File Opening Causes
In the majority of cases, installing the right version of Project JEDI will resolve your issue. If you are continuing to have errors with loading JDBG files, other external issues might be to blame. These other problems include (listed in order from most to least common):
- JDBG file references in the Windows Registry are broken
- The JDBG file description within the Windows Registry was removed
- Corrupt install of Project JEDI or other JDBG-related program
- File corruption affecting your JDBG file
- Past or present virus infection has affected your JDBG
- Hardware associated with JDBG has outdated drivers
- Your computer does not have the adequate system resources to open the Embedded JCL Debug Information format
Quiz: How many characters long can a filename be?
That's Correct!
The sum of the individual components of a filename (eg. subdirectory / path and the final filename) are limited to 255 characters in total.
Close, but not quite...
The sum of the individual components of a filename (eg. subdirectory / path and the final filename) are limited to 255 characters in total.