ODF Customized e-mail Subject

[rjchavez]

Hello all,
We're in need to customize the Subject line for "specific" recipient only.  The arsodf.xml comments seems to suggest that you can do this by using the <Recipient> tag under the <EmailAttachmentNotify> section.  It's not clear wether the <Name> tag should specify the RECIPIENT or RECIPIENT LIST or does it matter.  I've tried everything including the actual e-mail address in the <Name> tag under <Recipient> to no avail.  The only thing that seems to work is the "default" Subject immediately following <EmailAttachmentNotify>.

Any ideas?

[rjchavez]

Hello all,
We're in need to customize the Subject line for "specific" recipient only.  The arsodf.xml comments seems to suggest that you can do this by using the <Recipient> tag under the <EmailAttachmentNotify> section.  It's not clear wether the <Name> tag should specify the RECIPIENT or RECIPIENT LIST or does it matter.  I've tried everything including the actual e-mail address in the <Name> tag under <Recipient> to no avail.  The only thing that seems to work is the "default" Subject immediately following <EmailAttachmentNotify>.

Any ideas?

I've opened a PMR/CASE

[rjchavez]

Here's IBM response:

"There is an unreleased APAR for CMOD V10.1:

PH17448 ARSODF.XML EMAIL CUSTOMIZATION NOT WORKING FOR JAVA 8

The workaround is to point to JAVA 7."

I've tested it with JAVA 7 and it works.  I'm also requesting the ++APAR to test with V8.

[rjchavez]

I tested using JAVA V7 and it fixed the problem.  I also installed the ++APAR and tested with JAVA V8 successfully.

[scottnys]

Nice to see others are using that functionality.  That APAR was ours.  We changed Java from 7 to 8, being that it was being unsupported.  The "recipient" check was not getting hit any longer.  Glad we could expedite your implementation.  We waited 4+ months for the fix.

[rjchavez]

Nice to see others are using that functionality.  That APAR was ours.  We changed Java from 7 to 8, being that it was being unsupported.  The "recipient" check was not getting hit any longer.  Glad we could expedite your implementation.  We waited 4+ months for the fix.

Thanks for the reply.  Questions:  I take it that you are running with the ++APAR and all is OK?  How long have you been running with it?  Production?

[scottnys]

It's been in production since Christmas.  Working as we use it.  We caught it in v9.5 first.  While it was in the works at IBM we upgraded one of our instances (we support multiple CMODS on One LPAR) and the same issue was in v10.1.  IBM Tech support said that the APAR would be for both version.