Bug in VSI-FAX subroutine

[CKilgore]

I found a bug in the Prelude code to send statements via VSIFAX.  The bug is in UF PRINT.STM.FAX.  At the end of the code, it calls SEND.FAX3.  Just prior to that call there this logic:
                IF EMAIL.DOC THEN
                                PARAM = “EMAIL”
                END

On our system this was causing an error.  Once the that variable was set to EMAIL, it persisted from one statement to the next.  This was fixed by adding:
                ELSE
                                PARAM = “”
                END

The most obvious symptom of this was VSI-FAX would send emails to the user that said "vfx: Could not fill fax envelope: Cannot access file outgoing: No such file or directory"

Edit:

The final code should be:

Code:

   IF EMAIL.DOC THEN
      PARAM="EMAIL"
   END ELSE
      PARAM=""
   END

[Tom Pellitieri]

Anything is USER-FORMS may not be standard software - the file is used primarly for customer specific forms (e.g., Statements, in your case).

Prelude considers anything in USER-FORMS to be "custom" software.

--Tom

[precisonline]

Yeah, but I confirmed the same code in a half dozen sites so it all seems to be from the same base at some point in time.

[davidkyles]

This is on our system as well and I am sure it has been like this for years.  I have not heard any complaints of users or customers not getting statements or receiving the above message.  Is there any specific routine you must go through to experience this?

[Tom Pellitieri]

I'm sorry I'm not much help here...

I suspect my PRINT.STM.FAX is from version 10... the copyright date is 1993, the file date has not been updated since we migrated from Pick to UniData in December 2000, and the letters "EM" do not appear together anywhere in the file.

We also use STM.PRINT.LASER rather than STM.PRINT.

[precisonline]

I believe the issue comes up - and Chris would have to verify - when there's a bunch of statements queued to print and one of them is slated for email and the next one should go via fax.  When the VSIFax code is run, it passes EMAIL into the subroutine which then tells the VSIFax thing to attempt to email the document rather than fax it.

[CKilgore]

Kevin:

Yes that is what appeared to be happening.  When we would run a batch of statements, everything worked until the first statement to fax after the first emailed statement.

David:

The process we run is /CSP "Customer Statement Printing"

[davidkyles]

I'll give it a run through and see what breaks.  Thanks