MPE/iX Shell and Utilities Reference Manual, Vol 2

rcs(1) MPE/iX Shell and Utilities rcs(1)

Message: There are no locks set.

Cause: You attempted to use the –u option to unlock an RCS ﬁle, but that ﬁle was not

locked by anyone.

Action: None.

Message: Unknown option "–option"

Cause: You speciﬁed an option that is not valid for rcs.

Action: Check the DESCRIPTION section of this man page for a list of valid rcs

options.

Message: unterminated string in rcs encrypt routine

Cause: The encrypted

RCS ﬁle has been truncated.

Action: Data has been lost. It might be possible to recover some data from the encrypted

RCS ﬁle, but you will not get all of it back. If a backup of the ﬁle is available,

then recover from the backup.

For a list of error messages common to all RCS

utilities, see rcserror(3).

PORTABILITY

All UNIX systems.

The –B, –F, –G, –g, –I, –K, –k, –O, –T, –Y

MPE/iX NOTES

The current

MPE/iX implementation of rcs has the following limitations:

• Due to the fact that the comma (,) is not a valid character in

MPE/iX ﬁle names, the tradi-

tional ,v naming convention is not currently implemented. This means that you must

have a subdirectory named RCS under your current directory or

RCS will not work prop-

erly.

• For compatibility with traditional MPE/iX security features, you can only rename a ﬁle in

an MPE/iX group if you own the ﬁle or if you have SM capability. Because this command

attempts to rename ﬁles to which it may not have write access, this feature can interfere

with the command’s operation. For this reason, RCS archives should not be placed in an

MPE/iX group, but rather should be located elsewhere in the hierarchical ﬁle system where

the restriction does not apply. For example, the default

RCSPATH

places the archives in a

subdirectory named RCS in the current working directory.

For more information on how the current MPE/iX implementation may affect the operation of

this utility, see Appendix A, MPE/iX Implementation Considerations.