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.
RCP Command start failing all of sudden
-
Topic author - Contributor
- Posts: 22
- Joined: Fri Jun 28, 2019 6:12 am
- Reputation: 0
- Status: Offline
-
- VSI Expert
- Valued Contributor
- Posts: 55
- Joined: Wed Jul 21, 2021 9:14 am
- Reputation: 0
- Status: Offline
Re: RCP Command start failing all of sudden
Suggesting checking the remote system for R* log files to see if the error is reported on that side.
Re: RCP Command start failing all of sudden
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.