No need to save and/or restore /tmp.
Tmp can be cleared (while in restricted state), anything that needs to be created will be by i5/OS.
I've just recently performed this, works great.
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, August 01, 2014 7:27 AM
Subject: Save/restore of '/tmp'
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.
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
Kendallville, IN 46755
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l