OA55810: JES2EDS ISSUES *$HASP1523 AND STOPS MESSAGE PROCESSING DUE TO IZUG615E "ADDRESSINVALID"

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When a user submits a job with a
  //NOTIFY EMAIL=xxxx statement with an invalid target recipient,
  the SMTP server can report an error. This is surfaced to JES2 as
  a z/OSMF connection error, resulting in hilighted message
  $HASP1523 being issued and JES2EDS processing will halt.
  
  ANALYSIS:
  The current logic of the email sender task is that if any
  communication error in encountered, routine SNDSNDM issues a
  number of diagnostic    messages, followed by the communication
  error message. If the error was at the z/OSMF level (such as
  this case), then routine SNDSVDDG is used to issue message
  HASP1527 based on the content of JSON object returned by the
  z/OSMF server and then issue the main communication error
  message: HASP1523 Unable to connect to z/OSMF server.
  
  HASP1523 is a highlighted message that does not (usually) roll
  off the console screen. The sender task will DOM HASP1523 when
  it retries    communications and will reissue it if necessary.
  In this case, even if a retry ($S EDS) is issued, the message
  will never be deliverable, so we will DOM the message and then
  reissue.
  
  JES2EDS doesn't have a mechanism for differentiating between a
  "real" communication error and an error like "AddressInvalid".
  As far as JES2EDS is concerned, they are both just connection
  errors returned from z/OSMF and are handled the same way.
  
  
  KNOWN IMPACT:
  The following messages or similar will be issued:
  
   $HASP1527 500 IZUG615E: The connection to the SMTP host
   "mailhost.company.com " port  "25" failed with error type
   "AddressInvalid " , error message  "501 5.1.3 Invalid address n
   ".
   $HASP1534 z/OSMF server URI
   https://hostname.company.com:nnnnn/zosmf
   $HASP1525 Error sending z/OSMF server request.
   $HASP1535 Current message is in email queue $EDSQ003 at offset
    0000 in EMQT 02000281D101
  *$HASP1523 Unable to connect to z/OSMF server.
  
  JES2EDS email processing will stop.
  
  VERIFICATION STEPS:
  - Running JES2 V2R3
  - One of the following 3 conditions are met:
  
  1. A job is submitted with
     //NOTIFY EMAIL=xxxx where xxxx is not a valid e-mail address
  2. A job is submitted with
     //NOTIFY USER=nnnn,TYPE=EMAIL
     where the email address associated with the user nnnn in the
     security database is not a valid e-mail address
  3. An SSI 75 request is made which specifies SSNUADDR with
     invald email address
  
  - The above messages or similar are issued.
  - JES2EDS processing stops
  

Local fix

• BYPASS/CIRCUMVENTION:
  - Ensure your NOTIFY email targets are valid
  
  RECOVERY ACTION:
  - The offending email message can be purged from the EDS queue
  using '$PS($EDSQ00n),ONERROR' Where n is the queue number from
  message $HASP1535
  - JES2EDS can be restarted with $S EDS
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of HJE77B0 who may specify                         *
  * an invalid email address for use by                          *
  * JES2 Email Delivery Services.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Specifying an invalid email address                          *
  * for use by JES2 Email Delivery                               *
  * Services (EDS) may cause msgHASP1523                         *
  * and halt JES2 EDS processing.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Specifying an invalid email address for use by JES2 Email
  Delivery Services (EDS) may subsequently cause
  
    $HASP1523 Unable to connect to z/OSMF server
  
  to be issued and JES2 EDS processing to be stopped.
  
  JES2 EDS processing may be invoked in three ways:
  
    1. Via the NOTIFY JCL statement, by specifying an email
       address for the EMAIL= parameter.
  
    2. Via the NOTIFY JCL statement, by specifying TYPE=EMAIL
       and specifying a user ID for the USER= parameter for
       which the RACF database identifies an associated email
       address.
  
    3. Via the email facilities of the Notify User Message
       Service Call (SSI 75).
  

Problem conclusion

• TYPE/RESTART(WARM) IPL/REQUIRED(YES) CLPA(YES)
  
  CLPA is needed only if HASCxxxx modules currently reside in
  the pageable link pack area (PLPA).
  
  The HASCEDS (JES2 Email Delivery Services) module has been
  changed to recognize when msgIZUG615E (IZUG615E) is received
  from z/OSMF in response to an invalid email address processed
  by JES2 Email Delivery Services (EDS).  In such a situation,
  the undeliverable email message will be purged and new
  msgHASP1537,
  
    $HASP1537 Undeliverable message purged
  
  will be issued, but JES2 EDS processing will otherwise
  continue.
  
  **********************************************************
  *                                                        *
  *  You may continue to experience this problem until all *
  *  HJE77B0 members of the MAS have this fix applied.     *
  *                                                        *
  **********************************************************
  
  The information in the following JES2 manuals/publications
  is missing/incorrect:
  
    - SA32-0989-30 z/OS V2R3 JES2 Messages (for HJE77B0)
  
  In chapter 14, One-thousands, add the new $HASP1537 message:
  
    $HASP1537
  
    Explanation:
  
    >> Undeliverable message purged. ><
  
    JES2 issues this informational message to indicate that
    an undeliverable email message is purged. An example of
    an undeliverable email message is a message sent to an
    invalid email address.
  
    System action: JES2 processing continues.
  
    Operator response: None.
  
    Programmer response: None.
  
    Module: HASCEDS
  
    Routing Code: 1, 2, 10, 42
  
    Descriptor Code: 4
  
  APAR OA55810 prereq's (and sup's) for FMID HJE77B0:
  Pre's: BA52887
  

Temporary fix

Comments

APAR Information

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

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

  UA97817

Modules/Macros

• HASCEDS  HASMEDSM $EDS
  

Fix information

• Fixed component name

  JES2

• Fixed component ID

  5752SC1BH

Applicable component levels

• R7B0 PSY UA97817

     UP18/11/14 P F811

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.