PQ92206: DBD0022 E EXTUSER IS AN UNDEFINED OPERAND

APAR status

• Closed as program error.

Error description

• We run a data dictionary bmp batch job which executes
  different "DELETE DATA" commands. In some cases the answer
  is "DBD0022 E SEGUSER IS AN UNDEFINED OPERAND".
  *
  First we wanted to delete the EXTUSER1 data from a XMODULE. This
  works fine.
  DD-Command:
  "DD       XMODULE  (P, ,MNS189,000)  DATA=EXTUSER1,001,999)  ;"
  Answer message:
  "DBD1901 I DATA HAS BEEN DELETED FROM P MNS189 0"
  *
  Second we tried to delete the EXTUSER2 data from the same
  XMODULE.
  This does not work.
  DD-Command:
  "DD       XMODULE  (P, ,MNS189,000)  DATA=(EXTUSER2,001,999)  ;"
  Answer message:
  "DBD0022 E EXTUSER IS AN UNDEFINED OPERAND"
  
  Then we checked whether it is possible to delete the further
  EXTUSER3, EXTUSER4 and EXTUSER5 data from the same XMODULE. All
  this worked fine like EXTUSER1. The only problem is with
  EXTUSER2.
  The same error was encountered using other structures.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: DATA DICTIONARY REL6 USERS WITH PQ56902      *
  *                 WITH IMS 8 SUPPORT                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: MSGDBD0022 E 'SEGUSER IS AN UNDEFINED   *
  *                      OPERAND' IS ISSUED AFTER A DELETE_DATA  *
  *                      COMMAND OF SEGUSER2 DATA.               *
  *                      DBD_IN FUNCTION FAILS TO INSERT CORRECT *
  *                      DATASET DATA FOR DATABASES OTHER THAN   *
  *                      FASTPATH AND HALDB.                     *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  1.MSGDBD0022 E 'XXXUSER IS AN UNDEFINED OPERAND' WAS ISSUED'
  AFTER ANY DELETE_DATA COMMAND FOR DBSUSER2, SEGUSER2, DTEUSER2,
  PSBUSER2, SYSUSER2 OR EXTUSER2 DATA SEGMENTS THAT INVOLVED A
  RANGE OF LINE DELETIONS.
  FOR EXAMPLE, DD DBS (P,P,SMPORDP1,0) DATA=(DBSUSER2,01,99).
  THE FINAL '2' OF THE SEGMENT NAME WAS OVERLAYED IN THE COMMAND
  STRUCTURE WHICH CAUSED THE INVALID OPERAND.
  2.THE DBD_IN FUNCTION FAILED TO READ IN THE SEQUENCE NUMBER
  FOR THE DBSALLOC SEGMENT. DBSALLOC CONTAINS ALL THE DATA SET
  INFO. ALTHOUGH THE DBD_IN APPEARED TO END SUCCESSFULLY, ANY
  FURTHER ACTION OR COMMANDS INVOLVING THE DATA BASE WOULD BE
  UNABLE TO FIND THE CORRECT DATA SET DATA. GARBAGE WOULD APPEAR
  IN ANY DATA SET DISPLAY FIELDS OR OTHER OUTPUT.
  BECAUSE HALDB DATA BASES HAVE NO DATASET STATEMENTS THE DBD_IN
  FUNCTION WAS NOT AFFECTED. FASTPATH DATA SETS WERE ALSO NOT
  AFFECTED.
  

Problem conclusion

• MODULE DBDLLIST, WHICH HANDLES LIST TYPE COMMANDS, HAS BEEN
  MODIFED TO CORRECTLY READ COMMANDS FOR XXXUSER2 LIST DATA.
  DDIDBD, THE MACRO THAT CONTAINS THE STRUCTURE FOR DBDLIB
  MEMBERS, HAS BEEN CORRECTED TO REFLECT THE IMS 8 MACROS.
  THE MAIN DBD_IN MODULE, DBDB0000, HAS BEEN RECOMPILED TO
  REFLECT THE CHANGE.
  DBDEDTST, THE DBD_OUT MODULE FOR DATA SET STATEMENTS, HAS ALSO
  BEEN CORRECTED TO MATCH THE DDIDBD STRUCTURE TO SKIP DEVICE
  NAME TYPES.
  

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:

  UQ91662

Modules/Macros

• DBDB0000 DBDEDTST DBDLLIST DDIDBD
  

Fix information

• Fixed component name

  OS/VS DATA DICT

• Fixed component ID

  5740XXF00

Applicable component levels

• R602 PSY UQ91662

     UP04/09/02 P F409