Hi ,
I have a RPG program that works correctly in Green Screen.
But it bug when debugging in IBM Rational Developer
this is the screen shot
please i need help.
Message Id PUI0037 when debugging
-
- Profound User
- Posts: 21
- Joined: Fri Jun 26, 2015 7:49 am
- First Name: Fadiga
- Last Name: Mamoud
- Company Name: Allianz Africa Services
- Zip / Postal Code: 00225
- Country: Ivory Coast
- Contact:
-
- New User
- Posts: 12
- Joined: Mon Sep 21, 2015 11:45 am
- First Name: Jada
- Last Name: Williams
- Company Name: Profound Logic
- City: Dayton
- State / Province: Ohio
- Country: United States
- Contact:
Re: Message Id PUI0037 when debugging
Hi,
I'm going to open a support issue for your problem and follow up with you through email.
I'm going to open a support issue for your problem and follow up with you through email.
-
- Experienced User
- Posts: 2711
- Joined: Wed Aug 01, 2012 8:58 am
- First Name: Scott
- Last Name: Klement
- Company Name: Profound Logic
- City: Milwaukee
- State / Province: Wisconsin
Re: Message Id PUI0037 when debugging
Is it possible that you are running this with "Update Production Files = No"? PUI0037 means that can't access the "session database". The session database is a set of physical files in the PROFOUNDUI library (or whatever library you installed PUI into). We use this session database to help communicate between the various jobs used in a Profound UI session, so we are often adding/removing data from this file.
If the debugger has "update producction files = no" then it could potentially get PUI0037 when it can't update the session database.
You could try changing the PROFOUNDUI library, or wherever you installed PUI, to be a 'TEST' library to get around this problem ( such as CHGLIB LIB(PROFOUNDUI) TYPE(*TEST) ). Or else, you could run your debug job with 'Update production files = yes".
Anything that causes a problem with accessing the session database files could cause PUI0037, so I am just guessing. Let me know if this helps, or if you have a different problem. (If you're having a different problem, the job log from the debugger session would help us see where this is going wrong.)
Let me know if this helps, or if we need to look for a different problem.
If the debugger has "update producction files = no" then it could potentially get PUI0037 when it can't update the session database.
You could try changing the PROFOUNDUI library, or wherever you installed PUI, to be a 'TEST' library to get around this problem ( such as CHGLIB LIB(PROFOUNDUI) TYPE(*TEST) ). Or else, you could run your debug job with 'Update production files = yes".
Anything that causes a problem with accessing the session database files could cause PUI0037, so I am just guessing. Let me know if this helps, or if you have a different problem. (If you're having a different problem, the job log from the debugger session would help us see where this is going wrong.)
Let me know if this helps, or if we need to look for a different problem.
-
- Profound User
- Posts: 21
- Joined: Fri Jun 26, 2015 7:49 am
- First Name: Fadiga
- Last Name: Mamoud
- Company Name: Allianz Africa Services
- Zip / Postal Code: 00225
- Country: Ivory Coast
- Contact:
Re: Message Id PUI0037 when debugging
I run debug job with 'Update production files = yes".it works correctly.I can change the PROFOUNDUI library.
thinks.
thinks.
Who is online
Users browsing this forum: No registered users and 2 guests