PM70787: IRX0044I ERROR RUNNING EMAIL, LINE 176: FUNCTION DID NOT RETURN DATA

APAR status

• Closed as fixed if next.

Error description

• When SMTPNOTE is called from a REXX exec, the following
  error msg is received:
  ********************************* TOP OF DATA
  **********************************
     176 +++ X = SMTPNOTE("TO("TO") SU("SU") DA('"MSGDSN"')
  BATCH")
  IRX0044I Error running EMAIL, line 176: Function did not return
  data
  
  
  
  
  Additional Symptom(s) Search Keyword(s):
  

Local fix

• This error message can be avoided by modifying distributed
  version of
  SMTPNOTE line 581, by adding  '0'  to the exit statement, as in
  EDIT       TCPIP.SEZAINST(SMTPNOTE) - 01.00
  000581 exit         <=====  add  '0'  here
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release(s) 10, 11, 12,    *
  *                 and 13 IP: SMTPNOTE                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: When SMTPNOTE is invoked by a REXX      *
  *                      exec and which expects a return code    *
  *                      the calling exec failed with message    *
  *                      IRX0044. SMTPNOTE did not provide an    *
  *                      exit code.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  SMTPNOTE did not set an exit code for normal completion.
  +-------------------------------------------------------------+
  + Please check our Communications Server for OS/390 homepages +
  + for common networking tips and fixes.  The URL for these    +
  + homepages can be found in Informational APAR II11334.       +
  +-------------------------------------------------------------+
  

Problem conclusion

Temporary fix

Comments

• This APAR is being closed FIN (Fixed If Next) with concurrence
  from the submitting customer. This means that a fix to this
  APAR is expected to be delivered from IBM in a release (if any)
  to be available within the next 24 months.
  
  This problem will be tracked as User Story   7967
  by Communications Server for z/OS Development.
  
  The solution for this APAR is included in
  CS for zOS Version 2 Release 1.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R1C0 PSY

     UP