Basically, the title is the question. I'd like to see the code execute in our constraints to see what certain values are being pulled from where in the routings.
Thanks in advance for any leads ....

Hi,

never tried it, but found this hint to compile pcf constraints by hand for debugging in a very old posting regarding a similar question and maybe it can help you.

<
1. Run the session "Compile Constraints by Generic Item" (tipcf2201m000) ensuring the field "Delete Constraint Source" is set to "No".

2. Go to a shell and find the source file. It will be in the given in the session tipcf2201m000.

3. Run the bic6.1 compiler, e.g.
bic6.1 -l -w3 -w4 -w5 ottstpstandard FULLSOURCEPATH/SOURCEFILE -o FULLOBJECTPATH/OBJECTFILE -qe FULLSOURCEPATH/SOURCEFILE.e
where FULLSOURCEPATH and FULLOBJECTPATH are the directories used in the tipcf2201m000.

It is also interesting to compile the configurator in debug mode, I find this helps catch divide by zeros
bic6.1 -l -w3 -w4 -w5 -d ottstpstandard FULLSOURCEPATH/SOURCEFILE -o FULLOBJECTPATH/OBJECTFILE -qe FULLSOURCEPATH/SOURCEFILE.e
>

Regards,
Juergen

:cool:, thanks for the tip. I must admit I never knowingly used the Bic6.1 program or know anything about it.

I run from a Windows configuration file that has a command line at the bottom. I usually enter in dbslog type commands for debugging. Is this the same type of commands like you listed here ?

In windows environment use bic.exe instead on bic6.1 which exists in $BSE/bin in ur environment.