PI47844: SMSRV: ENHANCE ESM TASK START API ERROR LOGIC

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer code calling the ESM Task Start API would fail with
  the return/reason code indicating that no UOW could be
  found to start. An examination of ESM via SMOF clearly shows
  that the UOWs are on the Ready Queue awaiting to be started.
  

Local fix

• Start task manually
  

Problem summary

• -
  

Problem conclusion

• PI47844 - USERS AFFECTED - ALL ESM.
            This APAR corrects an issue where the TASK START API
            failed to start its requested task(s) due to
            encountering a bad WRB (Work Request Block) which had
            a null FUOW (Functional Unit Of Work) pointer.
            With this fix on, the TASK START API will note the
            error and continue down the entire WRB list starting
            any matching task/UOW combinations.
                                                  (P20057)
  
  DOCUMENTATION:
  NOTED BELOW ARE DOCUMENTATION CHANGES INCLUDED IN THIS APA
     DOCUMENT .......... ESM V1R3 User's Guide
     DOCUMENT NUMBER ... SC31-4635-01
     CHAPTER AND PAGE .. Messages and Codes
     CHANGE ............ Add the following message:
  
     DKNSMSRV16 - TASK NOT STARTED DUE TO MISSING FUOW
  
     This message indicates that a bad Task Work Request
     Block or WRB was encountered during a Task Start API call.
     The bad WRB has no FUOW pointer. It doesn't point to a
     Unit of Work or string.
  
     This message only appears as a WTO if this condition
     occurred but other matching tasks in the WRB list have
     been successfully started. Corresponding trace information
     for the error is also written to the ESM log under
     TSKSTX16.
  
     Operator action: None
  
     Supervisor action: The supervisor should check the ESM log
     for the TSKSTX16 trace entry. Field INFIELDs will show the
     Task/Version and UOW information which had this error.
  
     The supervisor should then verify in SMOF that all such
     tasks were indeed started. If not, then a manual start
     may be needed.
  
  ACTION:
        FOR THIS APAR TO BECOME EFFECTIVE, FOLLOW THESE STEPS.
        1. APPLY APAR WITH SMP/E.
        2. RESTART CPCS.
  

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:

  UI35561

Modules/Macros

• DKNSMSRV
  

Fix information

• Fixed component name

  ENHANCED SYS. M

• Fixed component ID

  5799ESM00

Applicable component levels

• R130 PSY UI35561

     UP16/03/01 P F602

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.