4 Replies Latest reply: Aug 22, 2014 10:52 AM by Daniel L RSS

    IDS not creating print files but returning success

    Daniel L

      Hi,

       

      I was wondering if anyone has run into this in the past.  We specify an output directory and unique filename for our print requests.  Occasionally when we issue a print request, IDS does not create the print files (pcl, pdf, mpm, jpg) yet it still returns success.

       

      When this occurs, the PRINTFILE and REMOTEPRINTFILE have what looks like a GUID of sorts with the file extension.  Normally, these would contain the full directory path and the unique filename we specified.

       

      The docserv.xml entry for the request and sample requests/responses are below.  Any insight you could offer would be greatly appreciated.  We're not sure the cause or how to correct this.  Because it is returning success, we end up having to manually pull the request out of the receive log and requeue it.

       

      docserv:

      <section name="ReqType:PrintWIPFormset">
      <entry name="function">atcw32-&gt;ATCLoadAttachment</entry>
      <entry name="function">atcw32-&gt;ATCUnloadAttachment</entry>
      <entry name="function">dprw32-&gt;DPRSetConfig</entry>
      <entry name="function">dprw32-&gt;DPRGetWipFormset</entry>
      <entry name="function">atcw32-&gt;ATCSendFile,DOCUMENTSTREAM,EXPORT,BINARY</entry>
      <entry name="function">dprw32-&gt;DPRUnloadExportFile</entry>
      <entry name="function">dprw32-&gt;DPRPrint</entry>
      <entry name="function">dprw32-&gt;DPRUpdateWipRecords</entry>
      </section>

       

      request:

      <?xml version="1.0" encoding="UTF-8"?>

      <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

          <SOAP-ENV:Body>

              <DSIMSG VERSION="100.023.0">

                  <CTLBLOCK>

                      <UNIQUE_ID>C5803CA8-9F58-9E42-5C50-E66B41C05180</UNIQUE_ID>

                      <REQTYPE>PrintWIPFormset</REQTYPE>

                  </CTLBLOCK>

                  <MSGVARS>

                      <VAR NAME="ALLRECIPIENTS"></VAR>

                      <VAR NAME="APP_CONTEXT">null</VAR>

                      <VAR NAME="APPENDEDEXPORT">YES</VAR>

                      <VAR NAME="CONFIG">straightthru</VAR>

                      <VAR NAME="CURRUSER">sys</VAR>

                      <VAR NAME="FILETYPE">XML</VAR>

                      <VAR NAME="GOCHANGE">YES</VAR>

                      <VAR NAME="ISPOLICY">false</VAR>

                      <VAR NAME="JSESSIONID">IDS SESSION</VAR>

                      <VAR NAME="NEWWIP1.COMPLETEDDATE">08-18-2014 09:25:34</VAR>

                      <VAR NAME="NEWWIP1.STATUSCODE">ST</VAR>

                      <VAR NAME="ORIGINAL_CONFIG">straightthru</VAR>

                      <VAR NAME="outputDir">\\ho3020c1\docprodarchive\straightthru</VAR>

                      <VAR NAME="OutputFileName">62E39573-7446-A9B1-19B9-0972DC43243F</VAR>

                      <VAR NAME="PRTTYPE">Complete</VAR>

                      <VAR NAME="RECNUM">3C3DDCC8E51E40C8A03CD74C7BA3C837</VAR>

                      <VAR NAME="ShowErrors">YES</VAR>

                      <VAR NAME="USERID">sys</VAR>

                      <VAR NAME="WIPS">1</VAR>

                      <VAR NAME="WIPS1.COMPLETEDDATE">08-18-2014 09:25:34</VAR>

                      <VAR NAME="WIPS1.RECNUM">3C3DDCC8E51E40C8A03CD74C7BA3C837</VAR>

                      <VAR NAME="WIPS1.STATUSCODE">W</VAR>

                  </MSGVARS>

              </DSIMSG>

          </SOAP-ENV:Body>

      </SOAP-ENV:Envelope>

       

       

      bad response (Note result is success despite it not creating any output):

       

      <?xml version="1.0" encoding="UTF-8"?>

      <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

          <SOAP-ENV:Body>

              <DSIMSG VERSION="100.023.0">

                  <CTLBLOCK>

                      <UNIQUE_ID>C5803CA8-9F58-9E42-5C50-E66B41C05180</UNIQUE_ID>

                      <REQTYPE>PrintWIPFormset</REQTYPE>

                      <REPLYTOQUEUE>HUB_DP_WEB_RPLY_QL</REPLYTOQUEUE>

                      <REPLYTOQUEUEMANAGER>MQGATE01</REPLYTOQUEUEMANAGER>

                  </CTLBLOCK>

                  <MSGVARS>

                      <VAR NAME="APP_CONTEXT">null</VAR>

                      <VAR NAME="APPENDEDEXPORT">YES</VAR>

                      <VAR NAME="CONFIG">straightthru</VAR>

                      <VAR NAME="CURRUSER">sys</VAR>

                      <VAR NAME="FILETYPE">XML</VAR>

                      <VAR NAME="GOCHANGE">YES</VAR>

                      <VAR NAME="IDSGUID">E54DE507-0685-433A-A6F1-1BC5A062CCDF</VAR>

                      <VAR NAME="IDSHOSTNAME">HODOCAPP03</VAR>

                      <VAR NAME="ISPOLICY">false</VAR>

                      <VAR NAME="JSESSIONID">IDS SESSION</VAR>

                      <VAR NAME="NEWWIP1.COMPLETEDDATE">08-18-2014 09:25:34</VAR>

                      <VAR NAME="NEWWIP1.STATUSCODE">ST</VAR>

                      <VAR NAME="ORIGINAL_CONFIG">straightthru</VAR>

                      <VAR NAME="outputDir">\\ho3020c1\docprodarchive\straightthru</VAR>

                      <VAR NAME="OutputFileName">62E39573-7446-A9B1-19B9-0972DC43243F</VAR>

                      <VAR NAME="PRINTFILE">E5484BD4-D7F5-3266-8767-A42373646171-2-IDS-3-.jpg</VAR>

                      <VAR NAME="PrtType">PDF</VAR>

                      <VAR NAME="RECIPIENT">PDF-OUTPUT</VAR>

                      <VAR NAME="RECNUM">3C3DDCC8E51E40C8A03CD74C7BA3C837</VAR>

                      <VAR NAME="REMOTEPRINTFILE">861D4F72-197A-A694-384D-7114E3BEC2FD-2-IDS-3-.pdf</VAR>

                      <VAR NAME="RESULTS">SUCCESS</VAR>

                      <VAR NAME="SERVERTIMESPENT">0.111</VAR>

                      <VAR NAME="ShowErrors">YES</VAR>

                      <VAR NAME="USERID">sys</VAR>

                      <VAR NAME="WIPS">1</VAR>

                      <VAR NAME="WIPS1.COMPLETEDDATE">08-18-2014 09:25:34</VAR>

                      <VAR NAME="WIPS1.RECNUM">3C3DDCC8E51E40C8A03CD74C7BA3C837</VAR>

                      <VAR NAME="WIPS1.STATUSCODE">W</VAR>

                  </MSGVARS>

              </DSIMSG>

          </SOAP-ENV:Body>

      </SOAP-ENV:Envelope>

       

      Here is a sample of the response we get once re-queued - this is what we would normally see and what is truly successful (Note the PRINTFILE and REMOTEPRINT file values as they relate to the outputDir and OutputFileName variables):

       

      <?xml version="1.0" encoding="UTF-8"?>

      <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

          <SOAP-ENV:Body>

              <DSIMSG VERSION="100.023.0">

                  <CTLBLOCK>

                      <UNIQUE_ID>C5803CA8-9F58-9E42-5C50-E66B41C05180</UNIQUE_ID>

                      <REQTYPE>PrintWIPFormset</REQTYPE>

                      <REPLYTOQUEUE>HUB_DP_APP_RPLY</REPLYTOQUEUE>

                      <REPLYTOQUEUEMANAGER>HUB01</REPLYTOQUEUEMANAGER>

                  </CTLBLOCK>

                  <MSGVARS>

                      <VAR NAME="APP_CONTEXT">null</VAR>

                      <VAR NAME="APPENDEDEXPORT">YES</VAR>

                      <VAR NAME="CONFIG">straightthru</VAR>

                      <VAR NAME="CURRUSER">sys</VAR>

                      <VAR NAME="FILETYPE">XML</VAR>

                      <VAR NAME="GOCHANGE">YES</VAR>

                      <VAR NAME="IDSGUID">EB98A936-2E53-179D-009A-C90985D8B545</VAR>

                      <VAR NAME="IDSHOSTNAME">HODOCAPP05</VAR>

                      <VAR NAME="ISPOLICY">false</VAR>

                      <VAR NAME="JSESSIONID">IDS SESSION</VAR>

                      <VAR NAME="NEWWIP1.COMPLETEDDATE">08-18-2014 09:25:34</VAR>

                      <VAR NAME="NEWWIP1.STATUSCODE">ST</VAR>

                      <VAR NAME="ORIGINAL_CONFIG">straightthru</VAR>

                      <VAR NAME="outputDir">\\ho3020c1\docprodarchive\straightthru</VAR>

                      <VAR NAME="OutputFileName">62E39573-7446-A9B1-19B9-0972DC43243F</VAR>

                      <VAR NAME="PRINTFILE">\\ho3020c1\docprodarchive\straightthru\62E39573-7446-A9B1-19B9-0972DC43243F.jpg</VAR>

                      <VAR NAME="PrtType">PDF</VAR>

                      <VAR NAME="RECIPIENT">PDF-OUTPUT</VAR>

                      <VAR NAME="RECNUM">3C3DDCC8E51E40C8A03CD74C7BA3C837</VAR>

                      <VAR NAME="REMOTEPRINTFILE">\\ho3020c1\docprodarchive\straightthru\62E39573-7446-A9B1-19B9-0972DC43243F.pdf</VAR>

                      <VAR NAME="RESULTS">SUCCESS</VAR>

                      <VAR NAME="SERVERTIMESPENT">0.345</VAR>

                      <VAR NAME="ShowErrors">YES</VAR>

                      <VAR NAME="USERID">sys</VAR>

                      <VAR NAME="WIPS">1</VAR>

                      <VAR NAME="WIPS1.COMPLETEDDATE">08-18-2014 09:25:34</VAR>

                      <VAR NAME="WIPS1.RECNUM">3C3DDCC8E51E40C8A03CD74C7BA3C837</VAR>

                      <VAR NAME="WIPS1.STATUSCODE">W</VAR>

                  </MSGVARS>

              </DSIMSG>

          </SOAP-ENV:Body>

      </SOAP-ENV:Envelope>

        • 1. Re: IDS not creating print files but returning success
          User9976623-Oracle

          I don't think OUTPUTDIR and OUTPUTFILENAME are supported vars to be sent to IDS rules and recognized. If you want to specify output you can send in PRINTFILE with path and file name together and it will take.

          It is possible older version of DPR rules sometimes returned success even in case of errors, but usually you can see some sort of error either in the output message (you put it here already), on screen where the server is running or in a log file/trace file. Check if you can locate error that is produced.

          From what you sent I can see that the two requests were processed by two different servers (physical computers), is it possible one is misconfigured? Server name is in the reply message as IDSHOSTNAME.

          • 2. Re: IDS not creating print files but returning success
            Daniel L

            Thanks for your reply.  Yes, I understand OUTPUTDIR and OUTPUTFILENAME are not recognized by IDS.  These are included for our own personal use but as you can see from the second response I included, when IDS works correctly the values match up to what is populated in PRINTFILE and REMOTEPRINTFILE.  I need to do some more digging to determine how these are set since we don't directly set them in the request, but was curious if anyone had run into the same thing.  And we've seen this error occur on all three of our servers so it doesn't appear to be an issue of just one server being misconfigured.  Whenever this occurs the PRINTFILE and REMOTEPRINTFILE values both differ but both always end in "IDS-[some one digit number]-.[extension] so I'm not sure if this ID is recognizable to anyone.   Again, thank you for your help!

            • 3. Re: IDS not creating print files but returning success
              User9976623-Oracle

              Basically when you see that name with IDS-[some one digit number]-[.extension] as you listed, it means DPR rules generated the PRINTFILE themselves because PRINTFILE was missing from input. Maybe there is some custom code that puts the two OUTPUTDIR and OUTPUTFILENAME together and sometimes it doesn't work? Or the client isn't sending PRINTFILE at all?

              Without PRINTFILE we are going to generate our own name.

              • 4. Re: IDS not creating print files but returning success
                Daniel L

                Ok great, thank you for the info - sounds like I've got to do some more digging