×
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.
On the BRMS recovery report,
The recovery includes 000000000000044 objects which were not saved.
Review the "Objects Not Saved" column for the saved items on this report
and determine if recovery is possible with these missing objects.
If these missing objects are required for recovery, review the job log
of the backup to determine why these objects were not saved.
Consider using save-while-active, ending subsystems or applications
holding locks against the objects, or saving in a restricted state by
ending all subsystems to include these objects in the backup.
From BRMS system save job log, system was in restricted state.
Saved Save ----- ASP ------ Save Save Not Sequence Control Volume
Item Type Name Number Date Time Saved Saved Number Group Identifier Encrypt
---------- ------- ---------- ----- -------- -------- -------- ------ --------- ---------- ---------------------------- -------
__ *LINK *FULL *SYSBAS 00001 9/23/18 23:50:00 446512 44 33220 SAVFULL05 001369
All libraries are clean.
These are all IFS objects marked as
Can be saved . . . . . . . . . . . . . : No
They all appear in BRMS system save joblog as
CPD37C3 - Cannot save /QFPNWSSTG.
How do others in the group handle IFS items "not saved" when preparing for a P7 to P9 migration?
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/
midrange.com
