Debug log creating for UBEs in printqueue ( not enabled debug log in jde.ini)

[john4444]

Hi Friends,

[FONT=&quot]Debug log creating for UBEs in printqueue ( not enabled debug log in jde.ini)

Large Debug log creating in PrintQueue folder (Jdedwards/e920/PrintQueue). Security in place users not allowed to run ube with jdedebug log enabled.

Enterprise server platform Linux.


Regards,
Bab


[/FONT]
[FONT=&quot][/FONT]

 

[craig_welton]

Check the JDE.INI on the server.

[UBE]
UBEDebugLevel=6
UBESaveLogFile=1

If it's set like this, you'll get the log for every UBE. Change them to 0 and it should stop what you are seeing.

Craig

 

[john4444]

Hi Craig,

Thank for responding on this post.

Yes both these parameter set to 0.

Here is the full section on [UBE]
[UBE]
BipOutputDirectory=
BipSaveOutputOnFs=0
prtEpsonESCPCountry=0
PRTFormFeed=1
PRTLocalCodeSet=
PRTPCLUseFormFeed=0
UBEBiDi_Arabic_Enabled=TRUE
UBEBiDi_DigitsFormat=Context
UBEBOTTOMMARGIN=360
UBEDBOutputlocation=
UBEDebugLevel=0
UBEFormatXML=1
UBEIsolateSynchJobs=0
UBELEFTMARGIN=360
UBEParallelList=NONE
UBEPDFCompression=1
UBEPrintDataItems=0
UBEPrintPDFData=0
UBESaveLogFile=0
UBESendMessage=1
UBEShowPDFLink=0
UBESubsystemLimit=3
prtCSVExtension=.csv
prtCSVSeparator=;
ubePRTFormFeed=1
ubeSendMessag=1
UBETabOpt=0
BIpSaveOutputOnFs=0
BIpOutputDirectory=
UbeDBOutputlocation=
UBETOPMARGIN=360
UBEXMLVersion=2

Regards,
Bab

 

[craig_welton]

Does this happen for every UBE? Also, what is you tools release?

Craig

 

[johndanter]

Just a thought, if it's not your INI file then could it be that the UBEs are called via a launch API / BSFN somewhere and the call has logging switched on?

This guy does it

B91300C LaunchBatchApplication
UBE does not have report interconnect data structure
SuppressPrinterDialog (Y)
Launch Batch Application
"R0010P" -> szReport
"ZJDE0001" -> szVersionJDE
"1" -> cSynch
"<Zero>" -> cPrintPreview
UNDEFINED -> szDataSourceOverride
UNDEFINED <- mnServerJobNumber
UNDEFINED <- cReturn
"0" -> cJDELogging
"0" -> cTracing
"0" -> cUBELoggingLevel
"<Blank>" -> szJobQueue
The Job Number of the UBE is returned in mnServerJobNumber (Data Dictionary Alias JOBNBR)

 

[john4444]

Hi John and Craig,


This is not happening for all ube. we found one ube generating debug log called from other ube.


example : Report B is generating Debug log which called from A.


Tools realese 9.2.0.3
Regards,
Bab

 

[craig_welton]

Check the code of the calling UBE. As John said, it could be set to enable debugging in the interconnect. For that matter, UBE B could turn on debug tracing itself, if coded that way.

There is a JDE bug (16020072) for something similar, but your release is after the supposed fix.

Craig

 

[john4444]

So far we found out this might be the culprit.

[TCENGINE]
StopAfterRow=0
TraceLevel=1

Regards,
CNC