H06.07 ReadMe

SYMPTOMS:
When using the new code coverage technology, users build an
instrumented application and then run it to create a DYN file.
A DYN file is a file whose name starts with ZZPF (on Guardian)
or ends with .dyn (on OSS). The problem is that, when the user
runs the application, a DYN file might not be created. Instead,
an error message appears in a file named ZZPELOG and indicates:
"Can’t open up file ... zpgodll".
Because the DYN file was not created, it cannot be used to
generate a code coverage report.
CONDITIONS:
When users build their system, they can choose where the
public DLLs are placed. If the public DLLs are placed into
the coldload subvolume, this problem would not occur. However,
if the public DLLs are placed somewhere else, this problem
will occur.
LIKELIHOOD:
High, because users typically place the public DLLs in a
different location than the coldload subvolume.
WORKAROUND:
Find the coldload subvolume for the running system. You can
find the coldload subvolume with "FILEINFO $SYSTEM.*.MCPDLL".
Several files named MCPDLL might be listed, but only one will
be open to indicate what the coldload subvolume is. For
example, it may be SYS00, SYS01, etc.
In the coldload subvolume, look for the file named ZREGPTR.
For example, if the coldload subvolume is SYS00, look for
$SYSTEM.SYS00.ZREGPTR.
If the ZREGPTR file is empty, it means this problem does not
exist. Otherwise, the ZREGPTR file should contain one
line. Type it out. It looks like this (for example):
DLLS SUBVOL ZDLL034A
That means that you will have a file named
$SYSTEM.ZDLL034A.ZPGODLL. (Instead of ZDLL034A, the subvolume
name may be whatever is shown in the ZREGPTR file.)
The workaround is to FUP DUP the ZPGODLL file to the coldload
subvolume. That is, in the above example:
FUP DUP $SYSTEM.ZDLL034A.ZPGODLL, $SYSTEM.SYS00.ZPGODLL
Page
2
of
2