Last updated on JULY 17, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
Reported on EnterpriseOne 9.0 application release level / TR 8.98 . Windows2003 platform
Microsoft Visual Studio 2005 version 8.0.50727.762 with Microsoft .NET Framework Version 2.0.50727 SP2
Customer just upgraded to EnterpriseOne 9.0 software and their developers had issues with debugging a custom function on their Windows 2003 application server. They claim that that the "/Zi flag" should never be set in the OptimizationFlags or DebugFlags of the [BSFN Build] section of the jde.ini for a Production environment. We advised the customer that they could remove the Zi flag to suppress the creation of the pdb files on the server. They said they weren't able to properly debug either way. Customer asked for verification ("a definitive answer") on how the settings in the [BSFN BUILD] stanza should be set and what the flags do during the build. The flags are compiler settings - the package build process invokes them, but JDE does not control them.
This is how their stanza is set:
OptimizationFlags=/FD /Gz /O2 /Zi /MD /W4 /EHsc /Gy
DebugFlags=/FD /RTC1 /Gz /Od /Zi /MDd /W4 /EHsc /Gy /D "_DEBUG"
DefineFlags=/D "WIN32" /D "_WINDOWS" /D "IAMASERVER" /D "KERNEL" /D "UNICODE" /D "_UNICODE"
LinkFlags=/DLL /DEBUG /SUBSYSTEM:windows /FORCE:MULTIPLE /FORCE:UNRESOLVED /INCREMENTAL:YES /VERBOSE /WARN:3
LinkLibraries=jdekrnl.lib jdel.lib jdenet.lib jdeipc.lib owver.lib jdeunicode.lib v_verify.lib xerceswrapper.lib xmlpublisher.lib
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms