RE: SAV and RST commands

Thanks Chuck. I was asking for a co-worker.

He found out Friday that it seems to be an authority issue regarding the restoring folder.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Saturday, October 26, 2013 11:22 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: SAV and RST commands

On 10/24/13 12:16 PM, Stone, Joel wrote:

I am using SAV to save folderA containing several thousand files.

Then I run RST and restore to folderB.

Many of the files in folderA are NOT in folderB.

The files which get restored seem to have the "need to archive"
attribute set to Y. If this attribute is "N", the file doesn't seem
to be restored.

How can I get ALL files saved and restored so folderA and folder have
the same files?

Seems probable that the files had not been saved, rather than not
being restored. And seems likely that as an origin, given the
description of the "archive" attribute of the files, would be that a
save-changed operation was in effect; i.e. a Time period for last change
(CHGPERIOD) specification other than spanning *ALL, had limited the file
that would be included in the save. The default of the SAV command
[could and] may have 'CHGPERIOD(*LASTSAVE)'.? If so, then unless
UPDHST(*YES) had been specified [or default changed to that], then even
repeated requests to SAV would not save those files.

The help text for the "Element 1: Start date" of the CHGPERIOD
parameter shows for the special value *LASTSAVE [from v5r3]:

"*LASTSAVE

The objects that have changed since the last time they were
saved with UPDHST(*YES) specified are saved. Notes:

1. If this value is specified, the value *ALL must be
specified for all other elements of this parameter.

2. For local file systems, the AS/400 archive flag is used.
For remote file systems, the PC archive flag is used.
..."