× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



You guys may have saved me in the case of a real emergency.

I have been reading the other BRMS conversation half heartedly. I look at
some of our BRMS logs every day. They look good based on my
uneducated knowledge.
This conversation got me to change some of the sorts etc. I found some
messages that tell me that our S/36E data library (QS36F) is not
being encrypted, documentation clearly states that 'Q' libraries are not
encrypted. That was the main reason to use BRMS.

I asked the guy that set up BRMS about it. To quote him 'YIKES'. Then I
asked him if he had ever restored anything using BRMS. He said 'Nope, you
have, just put brm on the end of the command'. I said Nope, I have been
restoring from save files. When he set it up he just typed the commands he
was told by...

That is enough background. Working on getting both issues fixed.

I have been trying to do a restore of a library. Using the RSTLIBBRM. No
success. I get two messages of interest in the logs.
CPA4264 Found THU; expected WED on device TC. (C I R),
I took an I. for this test it was okay in my mind.
Note THU should be expired.
CPF3715 File not selected. Data encrypted or not valid.
Recovery . . . : Do one of the following and try the request again:
-- Mount the correct volume.
-- Specify a different file.
-- Provide the correct decryption key.

Questions:
Is it because it is expired or do I need to supply some sort of key?



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.