Re: CPF3773 on new machine - Help!!!

[rob@xxxxxxxxx]

I think IBM's philosophy on this is the following:  If you have a program 
owned by PUTZ on one system and PUTZ has no special authority, if you 
restore it to another system PUTZ might have an inappropriate level of 
security.  Therefore it wants to flag this.  The magic pill seems to be 
ALWOBJDIF.  But, that didn't work for my output queue issue.  And, you 
need *ALLOBJ to use ALWOBJDIF.

One test to see if it is the serial number is to restore from GDIHQ to 
GDWEB.  They're on the same machine since they're just partitions on the 
one box.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





craigs@xxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/27/2004 02:48 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Fax to

Subject
Re: CPF3773 on new machine - Help!!!






We received a CPF3836 which caused a CPF3848 which caused a CPF3773.  An
authorization list was specified on the file.  The authorization on the 
new
system existed, was not locked, and the user had authority to the
authorization list.  It appears that restoring to a different system does
not always give the CPF3848.
If an authorization list is not specified on the file saved, a CPF3848 
will
not be issued if restoring to a different system.  It appears it knows it
is a different system by serial number, not system name.  I did a test of
this from our production machine to development and confirmed this.  If an
authorization list was specified on the file being saved, CPF3848 would be
issued and eventually CPF3773.  No authorization list gave the normal
restore message.  That explains why some save files issued the messages 
and
some did not.  It seems like it is a bug and should be more consistent.
Why does it matter whether there is an authorization list or not when
restoring to a different system?

** Mike wrote:
What are the other messages in the Log? I think you'll get this message if
there were authority or ownership changes on any of the Objects that were
Restored. The CPF3773 message is basically telling you that something else
happened that needs to be looked at. The Second Level Text for this 
message
even says:

The count of objects not restored may include objects that were restored
but
require some additional recovery action. Diagnostic messages were issued
for
those objects.

So set the Logging Level on the Restore so that you'll see everything and
then hunt through the log for those Diagnostic messages that will give you
some clues as to what's going on.

Mike

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.