Kbase P20137: Documentation examples for the Progress Debugger that are stored in procedure libraries, prodoc.pl a
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  19/05/2009 |
|
Status: Verified
SYMPTOM(s):
Documentation examples for the Progress Debugger that are stored in procedure libraries, prodoc.pl and prohelp.pl are missing in the src directory where Progress is installed
documentation examples are stored in procedure libraries, prodoc.pl and prohelp.pl in the src directory where Progress is installed according to documentation
Debugger - prodoc.pl and prohelp.pl missing for examples in tutorial
Complete installation of Debugger
FACT(s) (Environment):
Provision licenses are not installed
Typical installation of 4GL Development License
All Supported Operating Systems
Progress 9.x
CAUSE:
These libraries are not included in the Debugger License, by inference, to run these tutorials, the 4GL Development License is needed
FIX:
Update the 4GL Development License to a "COMPLETE" installation and the prodoc.pl and prohelp.pl libraries will be available under $DLC/src directory.
The issue here is whether or not the demo applications and samples are part of a typical install. The product has been structured so that a typical install would include only the mandatory features for a product. It was determined that samples were not a mandatory feature and that if someone was trying to limit the size of their install directory, e.g. performing a typical install, they would not want all of the sample code. For this reason the src/prodoc.pl and src/prohelp.pl files are included in the optional subcomponent "Demo Applications". Since the Debugger product is an add on product, you must have development environment installed with or before the debugger product, and the three development products include the Demo Applications subcomponent there is no need to included it in the debugger product.
If a user has already installed 4GL Development, ProVision or ProVision Plus and wants to access any of these demo applications or sample code they can use the Add Components feature, this provides the available to update an existing install with components that have not yet been installed. In this case a user should choose the ADE Source Code (Development) component and the Demo Applications subcomponent.