(sorry for top posting)
At this point I think we need to see your perl code.
-- Alan
>
> Hi Alan
> 1> DEFINE/PROCESS FILEA full pathname (without username/password)
> $PERL TEST.PL FILEA
> filea
> Fatal VMS error (status=2312) at PERLKIT:[SOURCE]VMS.C;1, line 5962 at
> test
> .pl line 2.
> %SYSTEM-W-NOSUCHDEV, no such device available
> 2>DEFINE/PROCESS FILEA full pathname (with username/password)
> $PERL TEST.PL FILEA
> filea
> Died at test.pl line 2.
> %SYSTEM-F-NOSUCHNODE, remote node is unknown
> 3>$WRITE SYS$OUTPUT F$GETSYI("VERSION")
> V7.2-1
> 4>$PERL "-v"
> This is perl, v5.6.1 built for VMS_AXP
> 5>$show log decc*
> (LNM$PROCESS_TABLE)
> (LNM$JOB_8555B680)
> (LNM$GROUP_000410)
> (LNM$SYSTEM_TABLE)
> (LNM$SYSCLUSTER_TABLE)
> (DECW$LOGICAL_NAMES)
> %SHOW-S-NOTRAN, no translation for logical name DECC*
> Thanks Alan
> Regards,
> Samina
> On Fri, 18 Aug 2006 Alan Winston - SSRL Central Computing wrote :
> >Samina wrote:
> >
> > > I tried giving the username/password in the pathname and still the perl
> > > scipt
> > > fails.
> >
> > > In my perl script I have a command
> >
> > > open file A or die;
> >
> > > So even now, with the username/password, it still dies when it tires to
> > > open
> > > the file.
> >
> > > As I said eveything works fine from my VMS $promt.
> >
> >This is peculiar. Try
> >
> >$ DEFINE/PROCESS FILEA (fullyqualifiedfilespec)
> >
> >and then run the PERL script using "FILEA" instead of the filespec.
> >
> >But at this point we'll be past my expertise, which is more VMS than PERL.
> >
> >Do these things and show us the results:
> >
> >$ write sys$output f$GETSYI("VERSION")
> >$ PERL "-v"
> >$ show log decc*
> >
> >and maybe one of the gurus here will be able to diagnose.
> >
> >-- Alan
> >
> >
> >
> > > On Thu, 17 Aug 2006 Alan Winston - SSRL Central Computing wrote :
> > > >Samina wrote:
> > > >
> > > > > I am new to VMS and Perl.
> > > >
> > > > > I have a VMS command procedure that calls a PErl script with 2
> > > > > parameters A-
> > > > >filename of the input file B- Filename of the output file. The perl
> > > > >script
> > > > >reads the input file A, processes it (removes spaces,etc) and puts
> > > > >this data in
> > > > >file B in the CSV format.
> > > >
> > > > > When File A is on my local directory, the program works fine.
> > > >
> > > > > When file A is a file on another cluster, the program fails with the
> > > > > following error (these may not be the exact words)
> > > > > "Fatal VMS error (status=2312), PERLKIT:[SOURCE]VMS.C;1 at line 5962
> > > > > at t.perl line 5" No such device
> > > > > I give the entire pathname for file A-XY12::XYZ1:[ABC.DEF.XYZ]ASDF.CSV
> > > >
> > > > > Line 5 in t.pl is the line which tries to open file A.
> > > >
> > > > > My question is
> > > >
> > > > > Is it not possible for PErl to read a file from another cluster (cross
> > > > > cluster read)??
> > > >
> > > >Sure, it's possible provided that your process is able to read the file.
> > > >
> > > >Checking the returned status:
> > > >
> > > >$ exit 2312
> > > >%SYSTEM-W-NOSUCHDEV, no such device available
> > > >
> > > >So I'd guess that if you did, for example,
> > > >
> > > >$ TYPE (fully specified filespec of file A)
> > > >
> > > >you'd get the same error.
> > > >
> > > >It doesn't really matter whether the nodename part of that file
> > > >specification
> > > >is in another cluster or just on another node in this cluster, provided
> > > >DECnet
> > > >proxies are set up correctly.
> > > >
> > > >(That is, if you're not going to use username/password in the
> > > >fully-qualified
> > > >filespec, there needs to be a proxy set up on the other node that gives
> > > >yournode::Yourusername default access as remote-fileowner, and proxies
> > > >have to
> > > >be enabled, and both nodes have to be running DECnet.)
> > > >
> > > >The error suggests that you're using a real nodename but have put in a
> > > >bogus
> > > >device name (which, if it's really XYZ1, is probably wrong; device names
> > > >tend
> > > >to look like DKxn, DSxn, MKsn, etc, etc.
> > > >
> > > >Anyway, take PERL out of the equation, try
> > > >
> > > >$ TYPE filespec
> > > >
> > > >and if it doesn't work, debug it there. Then try PERL again, but my
> > > >sense is
> > > >that this is not a PERL error.
> > > >
> > > >-- Alan
> > > >
> > > >--
> > > >===============================================================================
> > > > Alan Winston --- [EMAIL PROTECTED]
> > > > Disclaimer: I speak only for myself, not SLAC or SSRL Phone:
> > > > 650/926-3056
> > > > Paper mail to: SSRL -- SLAC BIN 99, 2575 Sand Hill Rd, Menlo Park CA
> > > > 94025
> > > >===============================================================================
> > > >
> >
> >--
> >===============================================================================
> > Alan Winston --- [EMAIL PROTECTED]
> > Disclaimer: I speak only for myself, not SLAC or SSRL Phone:
> > 650/926-3056
> > Paper mail to: SSRL -- SLAC BIN 99, 2575 Sand Hill Rd, Menlo Park CA
> > 94025
> >===============================================================================
> >
--
===============================================================================
Alan Winston --- [EMAIL PROTECTED]
Disclaimer: I speak only for myself, not SLAC or SSRL Phone: 650/926-3056
Paper mail to: SSRL -- SLAC BIN 99, 2575 Sand Hill Rd, Menlo Park CA 94025
===============================================================================
