Conference turris::pca

943.0. "%RMS-E-EOF, %PCA-F-PCAERR with Ada program" by LNZALI::BACHNER (Mouse not found. Click OK to continue) Thu Jan 30 1997 13:28

A customer uses PCA V4.4-3 and Ada V3.0-7 under OpenVMS V5.5-2 and gets strange
PCA error messages:

$ada /debug TELETEST.ADA
$acs LINK/DEBUG=SYS$LIBRARY:PCA$OBJ.OBJ TELETEST
%ACS-I-CL_LINKING, Invoking the VMS Linker for VAX_VMS target
$run teletest
        PCA Collector Version V4.4-3
PCAC>
PCAC>set datafile teletest.pca
PCAC>go
%PCA-I-BEGINCOL, data collection begins
%PCA-I-DATADEFPC, defaulting to collecting PC sampling data
%RMS-E-EOF, end of file detected
%PCA-F-PCAERR, internal PCA coding error; PCA$COLLECTOR_MAIN: 0007C622
%PCA-I-ENDCOL, data collection ends
$

The same program runs fine with 

PCAC>go/nocollect

TELETEST.ADA contains only 6 Text_IO.Put_Line lines:

----------------------------------------------------------------
--
--WITH Calendar;
WITH TEXT_IO;
--WITH SYSTEM;
--
--
----------------------------------------------------------------
-- main program
----------------------------------------------------------------
--
procedure teletest is
--
--
begin
  Text_IO.Put_Line( "" );
  Text_IO.Put_Line( "    TELEGRAM TEST PROGRAM" );
  Text_IO.Put_Line( "" );
  Text_IO.Put_Line( " HELLO PCA!" );
  Text_IO.Put_Line( "" );
  Text_IO.Put_Line( "TELEGRAM TEST PROGRAM ENDED" );
end teletest;
----------------------------------------------------------------

I tried to reproduce the error in the same software environment but it works on
our internal nodes.

Any idea the end of which file is detected ?  I tried $ SET WATCH FILE but the
only file used after the 'go' command and before output is sent to the terminal
is ADARTL.EXE (and the directory file it is searched in).

IPMT time ?

Thanks for your help,
Hans.

Problem solved - the customer had a bogus ADARTL.EXE in SYS$SHARE: which was
slightly smaller (201 vs. 204 blocks) than the original one.

Removing this copy and reactivating ($INSTALL REPLACE) the old one cured the
problem. It's beyond my imagination why the program ran fine with /nocollect but
bombed out when collecting data.

Sorry for suspecting PCA !

Regards,
Hans.

Hi Hans,

Thanks for the information.

BTW: The better way to link the program with normally /DEBUG is:
 
 $ LINK/DEBUG file
 $ DEFINE LIB$DEBUG PCA$COLLECTOR
 $ RUN file  ! runs PCA collector

To return to the debugger, just deassign the logical name:
 $ DEASSIGN LIB$DEBUG
 $ RUN file  ! runs the debugger

-James