BlueSeries

CCSID Issues in BlueSeries mail when system values QCCSID is not set (aka set to 65535)

Anonymous — Thu, 08 Oct 2015 12:51:03 +0000

CCSID Issues in BlueSeries mail when system values QCCSID is not set (aka set to 65535)

Forums

Anonymous (not verified) Thu, 10/08/2015 - 14:51

Re: CCSID Issues in BlueSeries mail...

When the the system values QCCSID is not set, applications has difficulties determine which CCSID to use when converting to ASCII.

To deal with that issue we have introduces a data area that overrides the invalid system value.

Create the CCSID data area in the BlueSeries database library and set the values to your preferred CCSID

CRTDTAARA DTAARA(BLUEXDB/EMLCCSID)
TYPE(*DEC)
LEN(5 0)
VALUE(277)

This requires BlueSeries build 165.

Best regards,

Niels Liisberg

Modem cable

Anonymous — Mon, 20 Jul 2015 10:23:05 +0000

Modem cable

Forums

BlueSeries

Hi,

What modem cable is required for BlueFax/BlueSeries when using a MOXA box to the Multitech modem?

Best regards,

Pat

Anonymous (not verified) Mon, 07/20/2015 - 12:23

Re: Modem cable

Hi Pat;

Except for the RJ45 network connection It requires is a straight up standard PC modem cable:
DB9 female - DB25 male cable.

I think even that Multitech ships the modem with that cable.

Best regards,

Niels Liisberg

Blueseries resends mail

Tobias L — Fri, 14 Jun 2013 08:46:00 +0000

Blueseries resends mail

Forums

BlueSeries

Our Blueseries is connected to our exchange server, who relays. When sending mail from blueseries and delivery takes more than 30 seconds, Blueseries resends the mail. One mail can generate 5-8 resends. All copies of the mail is received by the recipient. Is there any way to make Blueseries not wait for the message to be delivered. Alternativly can I increase the timeout from 30 seconds?

Thanks
-Tobias

Tobias L Fri, 06/14/2013 - 10:46

Hi Tobias, The problem is not

Hi Tobias,

The problem is not BlueSeries, but your Exchange server. It should not take more than 30 seconds to send a mail.

BlueSeries is waiting to get the code '250' from the mail server. '250' means that the mail is received ok by the server. If BlueSeries does not receive this code, the mail will not be marked as 'SEND OK'. BlueSeries has to know, otherwise you will never be able to use the transmissionlog because the log will never show wether a mail is in error or it's send.

If you haven't restartet BlueSeries, you will probably be able to see this message 'Waiting for 250 but received xxx' in the EMAIL subsystem joblog. It tells that BlueSeries is expecting the code '250' but is receiving a different code. If you browse for 'SMTP error code' you will get several homepages telling you what the SMTP codes are.

Best regards

Grith Skovbølle