II08296: HOW TO RESOLVE 'TEXT NOT FOUND' msgIKJ52506I ENCOUNTERED DURING DB2 DSNTINST CLIST PROCESSING.

APAR status

• Closed as canceled.

Error description

• DB2 5740xyr00 R220 R230 R310 R410 R510
  This APAR documents how to resolve msgIKJ52506i 'Text Not
  Found' received during DSNTINST CLIST processing. The dataset
  names listed in the APAR are for V3 but the equivalent V2, V4,
  and V5 names can be substituted.
  ================================================================
  
     The 'TEXT NOT FOUND' message (IKJ52506i) received during
  DSNTINST CLIST processing indicates the IBM target libraries
  SDSNCLST or SDSNSAMP have been modified.  These two libraries
  are created when DB2 is installed.  The intention is that
  these libraries will only be modified by IBM via DSNTINST
  CLIST processing. These libraries should NOT be manually edited.
  
  During the INSTALL clist process, DSNTINST uses the TSO/E edit
  subcommand FIND or CHANGE to customize JCL and CLISTs using the
  parameters the customer supplied on the install panels.
  
  Prefix.NEW.SDSNSAMP is created during DSNTINST processing.  It
  contains the edited JCL, created from the IBM source in
  DSN310.SDSNSAMP and the customer parameters.
  Prefix.NEW.SDSNTEMP contains the edited CLISTs created from the
  IBM source in DSN310.SDSNCLST and the customer parameters.
  
  If the target libraries were modifed, it is likely DSNTINST
  will fail when it issues a CHANGE or FIND command for a
  particular character string.
  
  PSI - Problem Source Identification
  
  There are two methods to locate the cause of the 'text not
  found' error:  One will find the specific member and line that
  was changed, the other will find the member that was changed.
  The resolution to the problem is to undo the change, or refresh
  the member from the ADSNMACS library.
  
  Method 1 - Locate the specific member and line where the 'text
  not found occurs.
  
  Execute the clist as follows:  EXEC 'DSN310.SDSNCLST(DSNTINST)'
  'CONTROL(LIST)'
  
  This will produce an echo of each command the clist executes.
  Keep track of the member names as they are edited.  The clist
  will fail with the 'text not found'.  The message immediately
  preceeding the error will be the FIND or CHANGE command that
  failed.  Since you are keeping track of the member names as
  they were edited, you now have the member and line with the
  error.
  
  Go to the input PDS (SDSNCLST or SDSNSAMP) and browse the
  member.  The change may or may not be obvious.  If the customer
  recognizes the change as one he made, he can simply change it
  back.  Otherwise, the member can be copied from the ADSNMACS
  library to the target library.  After the member is restored to
  it's original state, the clist can be run again.
  
  Method 2 - Find the member that was changed, and optionally the
  line.
  
  As each member is edited, msgDSNT489i will be displayed with
  the member name.  Find the last DSNT489i message from the TSO
  messages.
  
  Find the clist where that member was edited.  It will be in one
  of the three clists:
  
  DSNTINST customizes DSNTIJUZ
  DSNTINS1 customizes DSNTIJMV, DSNTIJCA, DSNTIJIN, DSNTIJID,
                DSNTIJSU, DSNTIJDE, DSNTIJTM, DSNTIJIC, DSNTIJVC,
                DSNTIJSG, DSNTIJEX, DSNU, DSNH, DSNEMC01
  DSNTINS2 customizes DSNTIJTC, DSNTIJFV, DSNTIJFS
  
  Find the 'WRITE &T489' message for the same member.  This
  indicates the member was saved.  Immediately following the
  saving of the member will be an EDIT command.  This edit
  command contains the name of the member that failed with the
  'TEXT NOT FOUND'.
  
  ISPF Browse the appropriate IBM source library SDSNSAMP or
  SDSNCLST.  Check the ID column for the affected member.  The
  userid listed there made the change to the member.  If the ID
  field is blank, then check the CHANGED field.  A date will be
  present if the member was changed.  (It is possible the ID is
  blank, and a date is present.  This would still indicate the
  member was changed.)
  
  If it is necessary to locate the specific failing line, bring
  the member up in edit mode.  Execute the TSO commands that were
  in the clist until one fails with 'TEXT NOT FOUND'.
  
  The member needs to be restored to its original state.  If the
  customer recognizes the change, he can undo it.  Otherwise, the
  member can be copied from the distribution library ADSNMACS to
  the appropriate target library - SDSNSAMP or SDSNCLST.
  
  DSNTINST can be re-executed, and there should be no further
  problems with the clist processing.
  
  APAR PL85894 for V2.2 documents this error, but the 'text not
  found' error occurs on DB2 V2.3 or V3 for the same reason.
  
  If you are installing CICS after an installation of DB2
  for DB2 R410 and above, and receive IKJ52506I after creating
  DSNEMC01, it most probably is because your HLQ on your
  Online Help dataset names were changed.  You should use
  DB2I to change the Online Help dataset names back to
  DSNHELP.xxxx, run the Install CLIST to generate the CICS
  jobs, and then use DB2I to restore the HLQ on the Online
  Help datasets to your previous name being used.
    (HLQ is your VSAM Catalog (ICF) High Level Qualifier)
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• CLOSED FOR INTERNET VIEWING
  DB2INFO
  

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