Re: Infoprint Server -- MIDRANGE-L

Thanks Sam,

When I look at the BCH job for the particular printer under QSPL using WRKACTJOB, the logging is at level-4 Severity-0 Text-*NOLIST.
Doing a 5 and 10 to view job log yields nothing that indicates error.

Looking at the message queue for the WTR job, I see the msg to notify me of incomplete print ( CPF3422 and 3433 ), but the possible causes don't seem applicable and pretty vague.

Msg log from the PDJ job yields CPF3395, another generic 'print held' msg, but nothing actionable.

Unfortunately operations is not something I get a great deal of experience with.

Sam_L <lennon_s_j@xxxxxxxxxxx> 4/5/2018 3:30 PM >>>

If you can, up the logging level of the batch jobs. In a former life I
found that you often go the real problem that way. Sometimes a Java
error was logged.

Sam

On 4/5/2018 1:16 PM, Buddy McClean wrote:

Thanks Paul,

The joblog for PDJ show the same msg for both those that sent and those that did not. But it is only the
"Print request processing has started." The detail shows the spool entry number but no indication of failure.

Plus many of the entries that get put on hold by the process, go through just fine if the same entry is released to try again. That was what gave me the impression that it was not a mapping entry. Plus my mapping entries are the simple default needed to function. The device that we use the most employs a mapping program I wrote. But it was working very well before using a distant email server.

Which led me to think that the settings for the PSF config or the printer device need to be changed for the change in timing between a local email server and a cloud one.

There have been cases of the email being rec by the recipient even though the spool entry was put on hold. But I can't say how many spool entries have been that way.

"Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx> 4/5/2018 12:31 PM >>>

Buddy,

We use InfoPrintServer heavily.

Each InfoPrintServer config has 3 jobs, BCH, WTR, PDJ.

CM_NIGHTLY QSPLJOB BCH
CM_NIGHTLY QSPLJOB WTR
CM_NIGHTLY QSPLJOB PDJ

Check the PDJ joblog, you should see both success and failures.

Print request completed processing normally.
Incorrect data was returned by mapping program (QSYS/QPQMAPEXIT).
Error detected while processing spooled file. Processing of the print
request ended.

Receiving the message "The attached PDF file could not be distributed" usually means there was not a proper PDFMAPE to for the spoolfile/PDF.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Buddy McClean
Sent: Thursday, April 05, 2018 1:10 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Infoprint Server

Good Day,

I am having issues while sending PDF attachments using Infoprint Server. Until several months ago we had our own internal email server and the process worked quite well. Then we switched to a cloud based email server and many of the spool entries are getting put on hold, and in many cases the writer is stopped. When the specific entry is put on hold, an email is generated by the system and sent to the admin mailbox indicating the PDF could not be distributed. But the logs that I can find do not indicate a cause.

Originally I suspected that the recipient email address was just not good. But many of the entries that get put on hold will send fine when tried a second time.

So, I'm suspecting a setting in the PSF config. or other device description parameters. Maybe a timing and/or response setting. Settings that may have come into play when switching from a local email server to a cloud based one. Even when I have a valid description of the settings, I don't know enough about the technical aspects to make changes.

Granted Infoprint Server is a fairly, shall we say underappreciated piece of software, but I am not quite ready to move up to a full featured package.

Just wondering if anyone has experience with this. Thanks
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD