JR35342: DSSEARCH COMMAND IS NOT NAVIGATING SUB-CATEGORIES CORRECTLY

Download Fix Pack 2 for InfoSphere Information Server Version 8.1

APAR status

• Closed as program error.

Error description

• [Problem]
  customer wants to get "Category+jobname" list. So he executed
  the following command:
  
  C:\IBM\InformationServer\Clients\Classic\dssearch -domain
  SVSWDST1_DV:9080 -user dsadm -password passw0rd -server
  SVSWDST1_DV -ljobs -matches -sub -oc D4BKDWH_UT
  
  The command returned jobnames with category, but the listed jobs
  are not all. Only the part of jobs are returned.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  dssearch does not list jobs in categories as expected
  ****************************************************************
  PROBLEM DESCRIPTION:
  The dssearch command line, when using "-ljobs -matches -sub"
  options, does not return all jobs that match the given
  criteria.
  ****************************************************************
  RECOMMENDATION:
  Apply patch JR35342.
  ****************************************************************
  

Problem conclusion

• The patch fixes a problem where the code did not corectly
  follow subcategories recursively
    - therefore the results only contained jobs that are one level
  down in the folder tree.
  
    SPECIAL NOTE: The Release Notes for release 8.1 indicate that
  the dssearch command is not supported.
    However, there are a number of distinct options in dssearch:
       1. Search for jobs by name (-ljobs -matches)
       2. Search for job sequences that use specified job (-ljobs
  -usedby)
       3. Search for jobs used in a specified job sequence (-ljobs
  -uses)
       4. Search for job using specified table definition (-ljobs
  -usesdrstable)
    This patch means that option 1, "Search for jobs by name",
  is supported as documented.
  
    The other options 2-4, however, are not fully supported,
  and will not be until some future full release of Information
  Server. They can still be used, but will only return
  information  for that subset of jobs that have been compiled in
  the project. If a job has not been compiled, it will not be
  found by dssearch using options 2-4, and if it has been edited
  since it was last compiled, out-of-date answers may be
  returned.
  

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:

Modules/Macros

• SERVER
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R801 PSY

     UP

• R810 PSY

     UP