How to trap errors raised by OUTPUT TO statement ? - Progress Community

Loading

Skip to Main Content

How to trap errors raised by OUTPUT TO statement ?

How to trap errors raised by OUTPUT TO statement ? In particular, how to trap "** "<file-name>" was not found. (293)" for regular OUTPUT TO , and "Unable to create Printer Device Context: . (4110)" for OUTPUT TO PRINTER ? OUTPUT TO does not support NO-ERROR phrase.

Apr 4, 2016
Knowledge

Title

How to trap errors raised by OUTPUT TO statement ?

URL Name

How-to-trap-errors-raised-by-OUTPUT-TO-statement

Article Number

000184243

Environment

Product: OpenEdge Version: 10.2x, 11.x and later OS: All supported platforms

Question/Problem Description

Program running on AppServer/WebSpeed is supposed to write files to disk or to printer.
Paths written to are UNC paths ("\\<hostname>\<directories..>\<filename>").
Paths are not guaranteed to be available. (ie. path to printer can point to printer that's offline)

If path isn't available, OUTPUT TO fails with "** "<file-name>" was not found. (293)" for regular OUTPUT TO, or "Unable to create Printer Device Context: . (4110)" for OUTPUT TO PRINTER in the *.server.log file.
Error doesn't get communicated back to client.

OUTPUT TO doesn't support NO-ERROR option.
How to trap errors from this statement ?

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Resolution

While the OUTPUT TO does not support the NO-ERROR phrase, the errors can be caught using a CATCH block.
Following code fragment is an example on how this can be achieved; it re-throws the error so traditional error handling can pick it up later - from there it can be passed back to the client as desired.

PROCEDURE outputstuff:
  OUTPUT TO "\\notexistingpath\invalidname". /* This wil trigger (293) */
  PUT UNFORMATTED "This will never be written since destination is invalid.".
  OUTPUT CLOSE.
  
  CATCH e AS Progress.Lang.Error:
     UNDO, THROW e.
  END CATCH.

END PROCEDURE.

RUN outputstuff NO-ERROR.

/* insert custom error handling code as needed here, example just messages things out */
MESSAGE ERROR-STATUS:ERROR SKIP
        ERROR-STATUS:GET-MESSAGE(1) SKIP
        RETURN-VALUE VIEW-AS ALERT-BOX.

Workaround

Notes

Customers who want to see support for the NO-ERROR option added to the OUTPUT TO statement are advised to submit an Idea.

References to Other Documentation:

Progress Article(s):
How to submit an idea for a Progress product enhancement

Keyword Phrase

Last Modified Date

11/20/2020 7:24 AM

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

How to trap errors raised by OUTPUT TO statement ? - Progress Community