PM05703: DXL perms relating to Discussion columns should be included in D XL Reference Manual

APAR status

• Closed as program error.

Error description

• Currently, DXL functions relating to Discussion columns are not
  documented in DXL Reference Manual. Following are the functions
  that can be used to manipulate discussion related columns, with
  an example:
  
  bool isDiscussionColumn(Column c)
  Determines whether or not a column is discussion column.
  
  void setDiscussionColumn(Column c, string filename)
  Makes a layout column into discussion column, and specifies
  which discussion DXL files it should be associated with.
  
  string dxlFilename(Column c)
  Returns the name of the discussion DXL file associated with the
  discussion column c.
  
  The above 3 functions needs documented in DXL Reference Manual -
  this is the defect.
  
  The following example finds a discussion column in the current
  view of the current module, then determines which discussion DXL
  file is being used in it (using the dxlFilename perm) before
  creating a new discussion column with the same contents in
  another module.
  
  =============================
  Column c
  for c in current Module do
  {
   if (isDiscussionColumn(c))
   {
     string s = dxlFilename(c)
  
     if (s != null)
     {
  
      Module m = edit('/ProjectPath/otherModule', true) // open a
  module, with some discussions in it.
      if (m != null)
      {
       Column cNew = insert(column 3)
       title(cNew, 'My copy Discussion')
       string home = getenv('HOME')
       string fullPath = home '\\' s ''
       string contents = readFile(fullPath)
  
       // we need to call dxl PERM on that column before setting
  discussion column,
       // because discussion column is also a modified version of
  LAYOUT dxl.
       dxl(cNew, contents)
       setDiscussionColumn(cNew, s)
       width(cNew, 100)
       refresh(m, false)
      }
     }
   }
  }
  =============================
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Currently, DXL functions relating to Discussion columns are
  not documented in DXL Reference Manual. Following are the
  functions that can be used to manipulate discussion related
  columns, with an example:
  
  bool isDiscussionColumn(Column c)
  Determines whether or not a column is discussion column.
  
  void setDiscussionColumn(Column c, string filename)
  Makes a layout column into discussion column, and specifies
  which discussion DXL files it should be associated with.
  
  string dxlFilename(Column c)
  Returns the name of the discussion DXL file associated with
  the discussion column c.
  
  The following example finds a discussion column in the
  current view of the current module, then determines which
  discussion DXL file is being used in it (using the
  dxlFilename perm) before creating a new discussion column
  with the same contents in another module.
  
  =============================
  Column c
  for c in current Module do
  {
   if (isDiscussionColumn(c))
   {
     string s = dxlFilename(c)
  
     if (s != null)
     {
  
     Module m =
  edit("/ProjectPath/otherModule", true) // open a module,
  with some discussions in it.
     if (m != null)
     {
      Column cNew = insert(column
  3)
      title(cNew, "My copy
  Discussion")
      string home = getenv("HOME")
      string fullPath = home "\\"
  s ""
      string contents =
  readFile(fullPath)
  
      // we need to call dxl PERM
  on that column before setting discussion column,
      // because discussion column
  is also a modified version of LAYOUT dxl.
      dxl(cNew, contents)
      setDiscussionColumn(cNew, s)
      width(cNew, 100)
      refresh(m, false)
     }
     }
   }
  }
  =============================
  

Problem conclusion

• The perms listed have now been documented
  

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:

Fix information

• Fixed component name

  TLOGIC DOORS

• Fixed component ID

  5724V61DR

Applicable component levels

• R920 PSN

     UP