A trace log records all version control activity that takes place during a Library painter session. You can either overwrite or preserve an existing log file each time you start a Library painter session.
We set a trace file ( see document 62383) and performed the operation again and got the following information: WORKFILE DOES NOT EXIST The highlighted portion of the tracefile (Status : Adding c:\powerbuilder scctest\(whatever)\m_genapp_frame.srm ...)
The problem was traced to the settings of the TUN NFS client, which runs on the PC to establish an NFS connection to the UNIX box. There is a setting in TUN NFS called "Umask" and this had also been set to 000. This setting is not a real Unix UMask, and it represents the actual permissions with which a new file is created.
After installing Java plug-in 1.6.0 Update 29, any time the IssueLink window gets launched (whether explicitly by pressing the Associate Issues button or implicitly by performing an action that has issue association requirements) the user is returned to the Version Manager login screen. If the Java console is opened in trace level 5, an error similar to the following is seen:
This behavior has been traced back to a bug in the upgraded JRE that VM 8.5.0 ships with (Java bug 8003398 ). In lieu of a Java fix, Serena is working on changing the Version Manager code to avoid this error on systems using multiple screens.
