PH25974: GUI MSG ERROR OPENING FILE, AND LOGGED MESSAGE INDICATING BAD PATH AND UNKNOWN PREFIX, WHEN DIFFERENT PATH NOMENCLATURE USED

APAR status

• Closed as documentation error.

Error description

• When attempting to view the contents of an asset displayed in a
  graph, instead of the asset contents being displayed, a message
  like the following may be displayed on-screen to the Analyze
  Client user:
  "
  Error opening file:
  C:\ADProjects\Project01\MapLayouts\PDA001M\PDA001.txt;
  please check ErrorLog for details!
  "
  Also, in the log for the IBM AD File service, a message like
  the following is generated:
  "
  bad path:
  C:\ADProjects\Project01\MapLayouts\PDA001M\PDA001.txt -
  (unknown prefix)
  "
  

Local fix

• Modify the IBM AD File service's conf.yaml file to have a
  mapping with a 'remote' parameter equal to the text of the file
  share name of the asset location, as specified in the
  Properties of the  asset in IBM AD Build Client when viewing
  the project asset in the project's virtual folder for that
  asset type.
  Even if the value in the Build Client properties for the asset
  will resolve to the same location as the value specified for
  the remote parameter in the File service's conf.yaml mapping,
  if the textual representation of those two locations is not
  specified identically, the Analyze Client will fail to display
  the file.
  In other words, not only the resolved folder locations, but
  also the format/nomenclature of how those folder locations are
  written is important when configuring and using IBM AD
  components.  In most situations, the format of how a
  folder's location is specified in IBM AD Build Client when
  creating and updating a project is the same format that will be
  used by other components when trying to access that project
  folder and the folders and files within it.  Similarly, if
  using z/OS connections and retrieving source assets from a z/OS
  system using the Connect for Mainframe component, the format of
  how the Path for the retrieved members is specified in the AD
  configuration process will be used when components access
  source code and other assets retrieved from z/OS.
  
  For example, if an AD server machine has a hostname of
  addiserver5.companyabc.com, an IP address of 10.1.2.5, and has
  a projects folder that has been shared so that it can be
  referenced in your network by a UNC name of either
  \\10.1.2.5\Projects or \\addiserver5.ompanyabc.com\Projects,
  and which has been mapped by other Windows machines as drive
  P:, then whichever of those UNC names is used when creating and
  modifying the project using IBM AD Build Client will also need
  to be configured/used by most AD server components, as well as
  the AD Analyze Clients.
  Therefore, to assure that all AD components (both those running
  on the server, and those that may be running remotely such as
  IBM AD Analyze Client and IBM AD Build Client) can successfully
  access the AD projects, their sources, and other project and
  analysis assets, if \\10.1.2.5\Projects will be the format of
  the shared projects folder used when creating the project in
  IBM AD Build Client, use the same format  (and not
  \\addiserver5.mycompany.com\Projects, and not P:) when
  configuring IBM AD and/or creating remote mappings in AD's
  configuration information to refer to that folder location.
  

Problem summary

• https://www.ibm.com/support/knowledgecenter/SSRR9Q_5.1.0/IBM_AD_
  Installation_and_Configuration_Guide_OUT_KC/user_access.html
  was missing information regarding how remote mapping values in
  conf.yaml for the IBM AD File service must be specified,
  causing failures on Analyze Client when trying to view source.
  

Problem conclusion

• https://www.ibm.com/support/knowledgecenter/SSRR9Q_5.1.0/IBM_AD_
  Installation_and_Configuration_Guide_OUT_KC/user_access.html
  has been updated to provide information regarding how the
  remote parameter of mapping values in IBM AD File service's
  conf.yaml must be specified.
  

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

Applicable component levels