Addendum I have updated perl to 5.10 and now this is what I receive as an error message:
Using /var/tmp/patchdiag.xref from Aug/15/22 Day too big - 36890 > 24853 Cannot handle date (0, 0, 0, 01, 0, 2071) at ./pca line 2511 perl -V Summary of my perl5 (revision 5 version 10 subversion 1) configuration: Platform: osname=solaris, osvers=2.10, archname=i86pc-solaris uname='sunos wdpv2vilv01 5.10 generic_150401-28 i86pc i386 i86pc ' config_args='-Dcc=gcc' hint=recommended, useposix=true, d_sigaction=define useithreads=undef, usemultiplicity=undef useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef use64bitint=undef, use64bitall=undef, uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='gcc', ccflags ='-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV', optimize='-O', cppflags='-fno-strict-aliasing -pipe -I/usr/local/include' ccversion='', gccversion='3.4.6', gccosandvers='solaris2.10' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=4, prototype=define Linker and Libraries: ld='gcc', ldflags =' -L/usr/local/lib ' libpth=/usr/local/lib /usr/lib /usr/ccs/lib libs=-lsocket -lnsl -ldl -lm -lc perllibs=-lsocket -lnsl -ldl -lm -lc libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a gnulibc_version='' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib' Characteristics of this binary (from libperl): Compile-time options: PERL_DONT_CREATE_GVSV PERL_MALLOC_WRAP PERL_USE_SAFE_PUTENV USE_LARGE_FILES USE_PERLIO Built under solaris Compiled at Aug 16 2022 14:51:12 Ken > On Aug 16, 2022, at 11:47 AM, Ken Harford <kharf...@comcast.net> wrote: > > Hi All, > > This already may have been addressed but I am new here > > When running "pca -l all” on Solaris 10 I get the following error: > > Using /var/tmp/patchdiag.xref from Aug/15/22 > Cannot handle date (0, 0, 0, 01, 0, 2071) at ./pca line 2511 > > Has anybody else run into this? And if so is there a workaround? > > Thanks > Ken