chigrrl
Member
I have set up the bsfn to toggle debug on the fly. It does update jde.ini. However, if I do the following in order:
1. log on to JDE
2. run toggle to turn debug on
3. submit local UBE - click 'logging' and set level to 6
4. job finishes, in printqueue .txt log exists BUT for the sql commands the values are missing. Ex: SELECT * FROM OBJ7333.F9860 WHERE (SIOBNM = '?').
5. log off
6 log back on - jde.ini still says Debug=FILE
7. resubmit job with logging level = 6
8. NOW I get what I expect in jdedebug.log: Ex: SELECT * FROM OBJ7333.F9860 WHERE (SIOBNM = 'R42520').
So the 1st time all of my sql statements had '?' and after logging off/on they had the real values. My toggle works, I can verify by looking at the jde.ini and by the fact that the .txt file generates in printqueue AND jdedebug'log populates. Only problem is the values in the sql statements.
chigrrl
B7333
SP22
Rev 6
NT/SQL
1. log on to JDE
2. run toggle to turn debug on
3. submit local UBE - click 'logging' and set level to 6
4. job finishes, in printqueue .txt log exists BUT for the sql commands the values are missing. Ex: SELECT * FROM OBJ7333.F9860 WHERE (SIOBNM = '?').
5. log off
6 log back on - jde.ini still says Debug=FILE
7. resubmit job with logging level = 6
8. NOW I get what I expect in jdedebug.log: Ex: SELECT * FROM OBJ7333.F9860 WHERE (SIOBNM = 'R42520').
So the 1st time all of my sql statements had '?' and after logging off/on they had the real values. My toggle works, I can verify by looking at the jde.ini and by the fact that the .txt file generates in printqueue AND jdedebug'log populates. Only problem is the values in the sql statements.
chigrrl
B7333
SP22
Rev 6
NT/SQL