Pinned topic Remote Preprocessors: Error Feedback
I am working on RDz 8.5.1.
I have defined a remote preprocessor (a Rexx on z, which invokes a generator and puts back the output).
This works fine and RDz merges the original and the generated source in a perfect way.
But: What happens if the preprocessor runs on an error? E.g. can't interprete some lines of code?
As it is a common z software, it produces a SYSPRINT file, which could be reformatted to XML or something else.
How can I feed RDz with this file? - In the settings for local preprocessors, there is a field for XML error feedback, for remote processors not! ... How can I proceed to merge the remote preprocessor error messages back into RDz and merged with other COBOL errors?
Even the "sample code walk through" in the RDz documentation has just a sample for local preprocessors...
Any Tipps orexperiences?
Re: Remote Preprocessors: Error Feedback2013-02-18T12:18:39ZThis is the accepted answer. This is the accepted answer.Ingo
What I have done was to write a postprocessor that runs after the last step that appends its output to the standard RDz ErrorFeedback, in your case, reformat the preprocessor messages into the RDz ErrorFeedback format. Although this new format is not "well-formed XML", it is tolerated by the RDz ErrFdbk processor (at least for earlier RDz versions).
Re: Remote Preprocessors: Error Feedback2013-02-20T07:45:51ZThis is the accepted answer. This is the accepted answer.Hi Tony,
thanks for the idea - that we have also discussed to do. But we think, there should be a more integrated way, as it is supported for local preprocessors as well... But if not, we have to write such kind of a post - processor.
Re: Remote Preprocessors: Error Feedback2013-02-20T13:14:30ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
Another possibility is to activate the Error Feedback checkbox for the preprocessor -> this generates the SYSXMLSD file into which you can write your messages.
Re: Remote Preprocessors: Error Feedback2013-02-20T14:32:40ZThis is the accepted answer. This is the accepted answer.Hi Tony,
would be nice - but I don't have the checkbox for remote preprocessors - see attached screenshot
Re: Remote Preprocessors: Error Feedback2013-02-20T17:30:58ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
Thanks for the clarification. The procedure I explained concerns the use of ErrorFeedback for build compilation jobs.
Re: Remote Preprocessors: Error Feedback2013-03-12T13:00:57ZThis is the accepted answer. This is the accepted answer.Looks, like we are the first guys who want to implement errorfeedback for real time syntax check with remote preprocessors... There we go.
TFQC_Jeremy_Flicker 270001TFQC13 Posts
Re: Remote Preprocessors: Error Feedback2013-05-10T19:44:22ZThis is the accepted answer. This is the accepted answer.
So for the "Identify Preprocessor Statements" using a remote preprocessor as configured in the Property Group, if i recall correctly it is true that if the preprocessor output file is not generated or downloaded due to either the preprocessor error or an error with the rexx script, i don't think any notification is given to the user that something went wrong from within the IDE, and that would make a good improvement.
The error feedback mechanism is involved in the Local or Remote Syntax Check process, and at the moment this mechanism plays no role in the Identify Preprocessor Statements behavior.
I am not sure if running Remote Syntax Check with the Error Feedback enabled will satisfy what you need, but it may be a start. The Error Feedback mechanism can be used to report errors in terms of your custom syntax, while the Real-time syntax checking will only report errors in terms of the translated cobol or pl/i output.