× 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.



I've migrated several lpars from Power 6 to Power 8, with a few more to
go.
One thing I've noticed is that even though BRMS says it was saved it
doesn't seem to get restored on the target system. The creation date/time
Creation date/time . . . . . . . . . . : 07/29/14 12:12:28
is way before the restore of the stream files. I am guessing it was
created with the restore of the OS. So when you restore the stream file
system you will get the subdirectories underneath it but not the
attributes of '/tmp' itself. Which is a big thing if you have to run
CHGATR OBJ('/tmp') ATR(*RSTDRNMUNL) VALUE(*NO)
in order to get email attachments to work from IBM i email utilities.
Just run that again after a restore.
This is not covered in the "Recovering your system" manual.

For those of you unfamiliar with this history let's say you create an
object under '/tmp'. Even if QSECOFR signs on they are not going to
delete that object if the attribute of '/tmp' is not changed. So, you
create this object and some IBM utility, running underneath QTCP or some
such thing tries to process an email attachment in there, it may have
issues.

It's like a unix crappy way of trying to implement the QTEMP library
system. Well, maybe not quite. Let's just say it's an attempt to not get
people to always name stuff underneath '/tmp' the same and seeing that
they are getting stepped on by each other.

Rob Berendt

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.