Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PCTCompile - detailed connect error message #2

Closed
GoogleCodeExporter opened this issue Mar 28, 2015 · 1 comment
Closed

PCTCompile - detailed connect error message #2

GoogleCodeExporter opened this issue Mar 28, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Hi,

First of all, great idea for a project and thanks for making it available.

Trying to setup an ANT script to sample the project, I found that PCTCompile 
wasn't unable to connect, but didn't report the actual PROGRESS error message. 
I've enhanced the code in ProgressV10.properties to report the error message 
(in my case an incompatibility of -Mm parameters, I might come back on that).

Ant log:

[PCTCompile] PCTCompile - Progress Code Compiler
[PCTCompile] Unable to connect to -db dbname -pf '[...]\connect.pf'
[PCTCompile] ERROR: Server has -Mm parm 32600 and client has 1024. They must
match. (1150)

ProgressV10.properties:

ProgressV10.1=CONNECT VALUE("{0}") NO-ERROR.\n\
IF ERROR-STATUS:ERROR THEN DO:\n\
  MESSAGE "Unable to connect to {0}".\n\
  MESSAGE "ERROR:" error-status:get-message(1).\n\
  RUN returnValue(14).\n\
  QUIT.\n\
END.\n

Obviously the code to report the error messages can be enhanced further to 
report multiple error messages if the case, e.g.

define variable i as integer no-undo.
do i = 1 to error-status:num-messages :
  message "ERROR:" error-status:get-message(i).
end.

If you could please include this enhancement in would be great.

Thanks,
Dan

Original issue reported on code.google.com by dan.dra...@gmail.com on 5 Feb 2011 at 7:23

@GoogleCodeExporter
Copy link
Author

Included in build #138, thanks for your submitting your patch.
Should be available in download page soon...

Original comment by g.quer...@gmail.com on 7 Feb 2011 at 9:32

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant