Page Comparison

User-defined *SYSBAS and IASP Timestamps

...

1. Parameters need to be padded out with trailing blanks to have 10, 10, 10, 5, 13 characters in the respective parameters.

2. If you want to have a timestamp for *SYSBAS or IASP ASP45 for both *IFS and *QSYS types you'll need to use *ENABLE twice - once for *QSYS and once for *IFS.

3. These timestamps are independent of each other, and increment independently. *QSYS applies to libraries and objects in the IASP, and *IFS refers to all link objects in in *SYSBAS or the IASP.

4. If *QSYS and *IFS have the same timestamp, *LINK saves will be listed at the beginning of a volume when doing WRKMEDIBRM. To ensure *LINK saves are listed in file sequence number, the timestamp for *IFS should be 1 sec greater than the *QSYS timestamp.

5. Users should only enable this on the system doing the backup before each Flashcopy backup.  BRMS recommends disabling this setting before doing any further BRMS backups that are not Flashcopy related by running STRMNTBRM with parameter RUNCLNUP(*YES).

6. The BRMS Advanced Feature (57xxBR1 Option 1 (FC5102) ) is required on the system where the FLASHTIME interface is used.

7. User-defined timestamps are not used for archival backups.

8. User-defined timestamps are not used for *LINK from IASP *ALLAVL or *CURASPGRP.

9. Any SAVBRM or *LINK control group entry which saves from multiple IASP's will not use user-defined timestamps.

10. Native backups (SAVLIB, SAVOBJ, etc) are not affected.

11. If a library with the same name exists in multiple IASP's and object detail is retained, it is recommended that different user-defined timestamps be used for each IASP entry of *QSYS type.

12. Do not use timestamps later than the current system date/time.

13. *SYSBAS requires these PTFs or their superseding PTF to be applied

    • 7.3 SI65676 

    • 7.2 SI65675

    • 7.1 SI65674