RCP Command start failing all of sudden

All types of networks, network stacks, and protocols supported by OpenVMS.
Post Reply
User avatar

Topic author
jeetu.singh
Contributor
Posts: 19
Joined: Fri Jun 28, 2019 6:12 am
Reputation: 0
Status: Offline

RCP Command start failing all of sudden

Post by jeetu.singh » Fri Oct 07, 2022 3:01 pm

Hello Team,

we have centralized server which fetch files from all client/remote server using RCP and it was working till last month and all of sudden it start failing below error.

%TCPIP-F-RCP_REMOTEERR, error reported by remote system:
-CONV-F-OPENOUT, error opening !AS as output

If I do fetch any other using RCP command on same client, it works fine.
Please suggest if anyone have encountered this type of error before.


tim.stegner
VSI Expert
Contributor
Posts: 13
Joined: Wed Jul 21, 2021 9:14 am
Reputation: 0
Status: Offline

Re: RCP Command start failing all of sudden

Post by tim.stegner » Fri Oct 07, 2022 3:08 pm

Suggesting checking the remote system for R* log files to see if the error is reported on that side.


sms
Valued Contributor
Posts: 66
Joined: Fri Aug 21, 2020 5:18 pm
Reputation: 0
Status: Offline

Re: RCP Command start failing all of sudden

Post by sms » Sat Oct 08, 2022 12:11 am

Code: Select all

> [...] all of sudden it start failing below error.

   When you did what, exactly?  Actual command?

> If I do fetch any other [...]

   "any other" _what_?  File?  User?  Actual command?

> [...] using RCP command on same client, [...]

   Same server, too?  (Actual command?)

      tcpip show version

> %TCPIP-F-RCP_REMOTEERR, error reported by remote system:
> -CONV-F-OPENOUT, error opening !AS as output

   Are you sending or fetching this file?  (Actual command?)

   "CONV" suggests that someone/something is using the CONVERT
command/utilities.

      help conv

   Does this file have some attributes which require special handling?
(Does the CONVERT stuff need space is SYS$SCRATCH (or some other
place)?)


> Suggesting checking the remote system for R* log files [...]

   Yup.  I'd also look at file system quotas (or for a full disk) on the
receiving side for the user in question.  The server could get
uncooperative if it can't write a log or temp file, even if it's sending
the file.

Post Reply