At 6:47 PM +0200 6/30/00, [EMAIL PROTECTED] wrote:
>MON MODES
>       With Perl running, 83% kernel mode, 16% user mode
>       Without Perl running, 11% user mode, 86% idle time

Hmm.  Perl doesn't do anything in kernel mode itself, I don't think, 
so this would point to getting stuck in some RTL or other.  Right? 
Could be running out of quota inside of a system service that doesn't 
properly handle it.  Any SYSGEN parameters changed recently?  Just 
another wild guess to throw in the pot.

>
>SDA> SHO PROC/ID=<process ID of hanging Perl>/CHAN
>       Channel  Window           Status        Device/file accessed
>       -------  ------           ------        --------------------
>         0010  00000000                        DKA104:
>         0020  81332E80
>DKA104:[PERL5_005_03]PERL.EXE;1
>         0030  8142C3C0
>DKA103:[SYSCOMMON.SYSLIB]DECC$SHR.EXE;2 (section file)
>         0040  8142BBC0
>DKA103:[SYSCOMMON.SYSLIB]DPML$SHR.EXE;1 (section file)
>         0050  814153C0
>DKA103:[SYSCOMMON.SYSEXE]DCL.EXE;1 (section file)
>         0060  81422740
>DKA103:[SYSCOMMON.SYSLIB]DCLTABLES.EXE;186 (section file)
>         0070  8142B540
>DKA103:[SYSCOMMON.SYSLIB]CMA$TIS_SHR.EXE;1 (section file)
>         0080  00000000                        FTA82:
>         0090  00000000                        FTA82:
>         00A0  8142A980

This is the thread library, right?  Is your Perl built with threads? 
Has that library been upgraded since Perl was built?  That shouldn't 
matter, but then what's happening shouldn't be either.

>DKA103:[SYSCOMMON.SYSLIB]LIBRTL.EXE;3 (section file)
>         00B0  8142AB80
>DKA103:[SYSCOMMON.SYSLIB]LIBOTS.EXE;1 (section file)
>         00C0  81303100
>DKA104:[PERL5_005_03]PERLSHR.EXE;1
>         00D0  81498740
>DKA103:[SYSCOMMON.SYSLIB]SECURESHRP.EXE;1 (section file)
>         00E0  814B0B40
>DKA103:[SYSCOMMON.SYSLIB]SECURESHR.EXE;1 (section file)
>         00F0  00000000                        FTA82:
>
-- 
____________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]

Reply via email to