Re: PTF 5770TC1-SI54738 and QSECOFR *USE

Brad,

There's a fixing PTF?

This isn't the SI51172 from a while back that was in error and fixed
by SI52478.
How do I find if there's a fixing PTF for SI54738? Open a PMR?



On Thu, Oct 2, 2014 at 8:24 AM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

The error is in the PTF. ESEND obviously uses the QtmmSendMail API which
was broken by a recent PTF, but is fixed by another one not included in

the

CUME.

That is an assumption of course. I remember when we were talking with

IBM

the PTF did cause the problem, but IBM also found some other ISV (I don't
think it was Help Systems) did have some invalid parameter lengths in the
call to the QtmmSendMail API.

Have you tried applying the fix PTF?

Brad
www.bvstools.com

On Thu, Oct 2, 2014 at 7:11 AM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:

I contacted HelpSystems (providers of ESEND) support. At their

suggestion

I did the following:

1) I first set QSECOFR user profile to PUBLIC *EXCLUDE (which is what

it

used to be) and left it there.

2) I removed PTF 5770-TC1 SI54738, did ENDMSF and ENDTCPSVR(*SMTP),
followed by STRMSF and STRTCPSVR(*SMTP). The email went out fine.

3) I then reapplied the PTF, did ENDMSF and ENDTCPSVR(*SMTP), followed

by

STRMSF and STRTCPSVR(*SMTP). The email errored out with the error I
originally reported.

4) To be sure, I removed the PTF again, did ENDMSF and

ENDTCPSVR(*SMTP),

followed by STRMSF and STRTCPSVR(*SMTP). The email again went out

fine.

So it definitely looks like this PTF is what caused the error. Now the
question: is the PTF in error or is ESEND not doing something right?

Awaiting their response.