RE: Migration / Recovery issues due to IBM objects being created and not restored as previous. -- MIDRANGE-L

Actually quite a few. I've been through a few full system restores, OS upgrades, etc.
Thought about sharing the code but it's got a few calls in there, etc and I'd rather not spend the time explaining it all.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Monday, April 8, 2019 3:55 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: Migration / Recovery issues due to IBM objects being created and not restored as previous.

< I have an IPL job which does
CHGATR OBJ('/tmp') ATR(*RSTDRNMUNL) VALUE(*NO)

I like that idea.

Do you force/change any other attributes?

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Monday, April 08, 2019 3:52 PM
To: Midrange Systems Technical Discussion
Subject: RE: Migration / Recovery issues due to IBM objects being created and not restored as previous.

A couple of things to check.

One: was the object ever saved? If you still have access to your old system can you check BRMS (like WRKLNKBRM) to see if it has been saved? If you didn't use BRMS can you either check last saved date and/or the media itself to see if has been saved?
/tmp on our system is flagged as not to be saved. See WRKLNK, option 8, Can be saved or CHGATR OBJ('/tmp') ATR(*ALWSAV) VALUE(*NO)

I have an IPL job which does
CHGATR OBJ('/tmp') ATR(*RSTDRNMUNL) VALUE(*NO)

If you used BRMS to do your save did you use STRBKUBRM CTLGRP(MYCTLGRP) ... OMITS(*IGNORE) Wouldn't have helped with /tmp if that *ALWSAV option is set but it may have helped it if you told BRMS to ignore output queues.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Monday, April 8, 2019 3:19 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: Migration / Recovery issues due to IBM objects being created and not restored as previous.

Another migration/recovery issue surfaced.

RNM failing with CPFA0B1 Message . . . . : Requested operation not allowed. Access problem.

The reason for this failure.
Restricted rename and unlink . . . . . : Yes

Prior to migration
Restricted rename and unlink . . . . . : No

This was on the "tmp" folder.
Tmp folder was created, not restored, thus I lost my custom settings.
https://www-01.ibm.com/support/docview.wss?uid=nas8N1014241

I found other IBM objects that are created, not restored, that also caused issues.

Outqs related to a device description.
Issue was the outqs had incorrect authority after the migration/restore.
Outqs were created with their *PUBLIC authority *USE.
Had to manually set the outq authorities back to original settings, *CHANGE.

QAUDRN Journal Receivers created in incorrect library.
Issue was the journal receiver was created in QSYS, not the custom library.
Had to create a new journal receiver in the custom library, then issue a CHGJRN.

3rd party products using system object QPMLPMGT failed.
QPMLPMGT was restored with *EXCLUDE authority.
3rd party products needed *USE authority.

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com