Logging file

The logging file enables systems support to check the result of the reconstruction. This file is created under the TSOS user ID and is called SYS.SRPM.RECON.LOG.<date.time>.

It contains the following information:

• Pubsets of the user catalog that has been saved (BACKUP) or is to be reconstructed (SYSSRPM):

  PUBSET	Catalog ID
  TYPE	SM or SF pubset
  DATE	Date of the save or reconstruction
  TIME	Time of the save or reconstruction
  ENCRYPT	NO/YES: logon-password encryption
  SECOS	NO/YES: product SECOS in use

• user ID

  USERID IN SYSSRPM
  USERID	All processed user IDs
  PRESENT	NO/YES: entry in the reconstructed user catalog
  USERID IN BACKUP
  PRESENT	NO/YES: entry in the backup file
  ACTION	ADDED/REMOVED: new addition or deletion
  USERID IN TSOSCAT
  PRESENT	NO/YES: entry in TSOSCAT
  ACTION	ADDED/REMOVED: new addition or deletion
  DELETED
  FILES	Number of deleted files with SCOPE=BACKUP
  JV	Number of deleted JVs with SCOPE=BACKUP

  Depending on the command entered: IMPORT-PUBSET PUBSET=..., RECONSTRUCT-USERCAT=*BY-BACKUP(SCOPE=*ALL/*BACKUP/*TSOSCAT) the user IDs are handled differently during reconstruction.

  
  Example

 USERID IN SYSSRPM | USERID IN BACKUP  | USERID IN TSOSCAT |      DELETED      |
 USERID  | PRESENT | PRESENT | ACTION  | PRESENT | ACTION  |  FILES  |   JV    |
---------+---------+---------+---------+---------+---------+---------+---------+
USERID1  |   YES   |   YES   |         |   YES   |         |         |         |
USERID2  |   YES   |   YES   |         |   NO    | ADDED   |         |         |
USERID3  |   YES   |   NO    | ADDED   |   YES   |         |         |         |
USERID4  |   NO    |   YES   | REMOVED |   NO    |         |         |         |
USERID5  |   NO    |   NO    |         |   YES   | REMOVED |       4 |       3 |
---------+---------+---------+---------+---------+---------+---------+---------+

• SCOPE=*ALL/*BACKUP/*TSOSCAT

  USERID1 was saved in the .BACKUP file and has an entry in the TSOSCAT file catalog when reconstruction takes place.
  USERID1 is reconstructed in the SYSSRPM user catalog with the saved user attributes and retains its existing files.

• SCOPE=*ALL/*BACKUP

  USERID2 was saved in the .BACKUP file but has no entry in the TSOSCAT file catalog when reconstruction takes place.
  USERID2 is reconstructed in the SYSSRPM user catalog with the saved user attributes and is assigned an empty entry in the file catalog.

• SCOPE=*ALL/*TSOSCAT

  USERID3 was not saved in the .BACKUP file but has an entry in the TSOSCAT file catalog when reconstruction takes place.
  USERID3 is configured in the SYSSRPM user catalog with the default attributes and is assigned its existing files.

• SCOPE=*TSOSCAT

  USERID4 was saved in the .BACKUP file but is assigned no entry in the TSOSCAT file catalog when reconstruction takes place.
  USERID4 is not entered in the SYSSRPM user catalog.

• SCOPE=*BACKUP

  USERID5 was not saved in the .BACKUP file but has an entry in the TSOSCAT file catalog when reconstruction takes place.
  USERID5 is not entered in the SYSSRPM user catalog, its entry in the file catalog is deleted together with its files and JVs.

• Summary:

  LOGON PASSWORDS ENCRYPTED: NO/YES:
  The logon passwords have been encrypted

  EXPIRATION DATES UPDATED: NO/YES:
  The logon password expiry dates have been adjusted

  SECOS ATTRIBUTES RESET: NO/YES:
  The SECOS attributes have been set to their defaults

  USERIDS RECONSTRUCTED:
  Number of user IDs in the reconstructed user catalog

  USERIDS ADDED TO BACKUP:
  Number of user IDs added to the new user catalog compared with the status of the .BACKUP file; SCOPE=*ALL / *TSOSCAT

  USERIDS REMOVED FROM BACKUP:
  Number of user IDs deleted from the new user catalog compared with the status of the .BACKUP file; SCOPE=*TSOSCAT

  USERIDS ADDED TO TSOSCAT:
  Number of new user IDs added to TSOSCAT; SCOPE=*ALL / *BACKUP

  USERIDS REMOVED FROM TSOSCAT:
  Number of user IDs deleted from TSOSCAT; SCOPE=*BACKUP

Responses to errors

In the event of a system error which causes abortion of the reconstruction and therefore of import processing, the future user structure depends on the status of the reconstruction when it was aborted. This status can be determined from console messages:

• before message SRM2017
  The reconstruction has not yet begun; a new pubset import with or without reconstruction can be started.

• between messages SRM2017 and SRM2019
  The reconstruction is in full swing; only a new pubset import without reconstruction can be started. The backup file may then have to be read in again. The user structure has the old status.

• after message SRM2019
  The reconstruction is so far gone that it can no longer be undone. A new pubset import without reconstruction can be started. The user structure has the new status.