Re: PTF Cross Reference

On 06-Oct-2016 06:47 -0500, Rob Berendt wrote:

I realize that one is "just passing along" but it does make an
archive search easier if you post the problem that this PTF fixed.

The OP did post what was corrected [for them]; i.e. they were concerned with an issue for entries not able to be sent per "QtmmSendMail was hanging". That text was posted under the original/other subject "FYI: QtmmSendMail issues on 7.3" rather than under my sub-thread with the modified topic-subject redirected to be about the "PTF Cross Reference".

Sort of like:

I did this command:
ADDUSRSMTP USRPRF(DUMMY) ALIAS('dummy.person')
and I got:

TCP5323
Message . . . . : Alias characters invalid.
Cause . . . . . : The characters of the alias were invalid. Valid
characters are case insensitive and include all alpha-numeric
characters (a-z, A-Z, and 0-9), and the following special characters:
PERIOD(.), HYPHEN(-) and UNDERSCORE(_). You need to set alias before
you are able to set alias domain.
Recovery . . . : Correct the error and retry. Add alias to make the
alias domain meaningful.

From program . . . . . . . . . : QTMSADDUSR
From library . . . . . . . . : QTCP
From module . . . . . . . . : QTMSADDUSR
From procedure . . . . . . . : main
From statement . . . . . . . : 14

To program . . . . . . . . . . : QTMSWRKUSR
To library . . . . . . . . . : QTCP
To module . . . . . . . . . : QTMSWRKUSR
To procedure . . . . . . . . : display_panel__FPcRiP9msgInfo_tN21
To statement . . . . . . . . : 34

It says the period is valid.
This works:
ADDUSRSMTP USRPRF(DUMMY) ALIAS('dummy')

This message is not in the PTF cover letter but it does mention the
period.

Then again: Putting on this PTF does NOT fix the issue.
PTF
ID Status
SI61076 Temporarily applied

Just to royally honk everyone off. While I perfectly documented this
situation and stepped through it. I am not going to report it. I have
other priorities and I don't use ADDUSRSMTP.

FWiW, an APAR [and thus] PTF cover letter that was corrective for that specific issue should have contained, minimally, the symptom keyword string:
msgTCP5323 F/QTMSADDUSR T/QTMSWRKUSR

Optionally [because, although more thorough and accurate, not really necessary], additionally including the symptom string data for the ILE module and procedure; although a convention apparently never was adopted, despite some effort made to get a consensus on a consistent forming of keywords:
FM/QTMSADDUSR FP/main STMT/14 TM/QTMSWRKUSR TP/display_panel STMT/34