PL56478: BATCH SELECT DSNECP16 X'4E0' RC00C9008E

APAR status

• Closed as user error.

Error description

• BATCH JOB DOING SELECTS HANGS. CPU USAGE RISES TO 100 PERCENT
  WHEN IT APPEARS THAT A LOCK REQUEST IS TRYING TO BE FULFILLED.
  RATHER THAN SUSPEND, LOOP IS INDICATED IN DSNECP10 OR DSNECP16
  WITH IRLM MODULE THAT PROCESSES INBOUND REQUESTS INVOLVED.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• WHEN ASKED TO RUN THE APPLICATION WITH THE DSNTRACE ACTIVE
  (DSN COMMAND WITH TEST OPTION: I.E. DSN SYSTEM(DSN) TEST(101)
  AND A DSNTRACE DD CARD SPECIFIED), THE USER FOUND THAT SOME OF
  THEIR SELECTS WERE CAUSING THE LOOPING EFFECT.  THE EXPLAIN
  OUTPUT ALSO HELPED WITH THE DISCOVERY OF THE PROBLEM.
  AS NOTICED BY THE USER:
    WHEN THEY CHANGED ONE OF THEIR SELECT STATEMENTS FROM:
      SELECT COLUMNS FROM TABLE
      WHERE PTNO||PTLOC = DFPTNO||DFPTLOC
    TO:
      WHERE PTNO=DFPTNO AND PTLOC=DFPTLOC
    THE PROGRAM RAN IN 15 MINUTES.
  IF THE CUSTOMER IS EXPERIENCING A LOOPING EFFECT IN DSNECP10,
  DSNECP19, AND DSNECP16 THE APPLICATION SHOULD BE RUN WITH THE
  DSNTRACE ACTIVE.  THE USER IN THIS CASE SAW MANY OF THE
  FOLLOWING MESSAGES:
   DSNET20I DSNETRAP BEFORE SQL CALL======================...
   DSNET20I DSNETRAP AFTER SQL CALL======================...
  WHICH LED TO THE DISCOVERY THAT THEIR APPLICATION WAS
  EXECUTING NUMEROUS SQL CALLS. CLOSING AS A USER ERROR.
  

APAR Information

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

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

Fix information

• Fixed component name

  5740 IBM DATABA

• Fixed component ID

  5740XYR00

Applicable component levels