Correcting a CA View Database when the Generation Number Reaches 32768.

Document ID : KB000052849
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Guidelines for correcting a View Database when the Generation number has reached the maximum of 32768.

Solution:

In CA View 11.0 (with PTF RO00528 applied) and all higher maintenance and version levels, the following messages will begin to appear during a backup cycle when the database generation number has reached 32760:

SARBKU08 *******************************************
SARBKU08 * WARNING: The current generation number  *
SARBKU08 * is going to exceed the allowable limit. *
SARBKU08 *******************************************

The following corrective procedure should be performed before the generation number reaches 32768.

If the following message is received during a View standard backup:

SARIFP01 INVALID GROUP CONTROL RECORD ID=xxxxxxxxxxxx, GEN=32768, AND
SEQ=nnnn ENCOUNTERED, PROGRAM TERMINATED

The CA View started task (SARSTC) will stop because the maximum number of generations (32768) has been reached.

To correct the database, in reducing the generation number, you use the following steps:

  • SARDBASE UNLOAD
    //XXXXXXXX JOB
    //SARDBASE EXEC PGM=SARDBASE,PARM='VIEW.DB1' <=== Modify DB name
    //STEPLIB DD DISP=SHR,DSN=VIEW.CAILIB <=== Modify, if used
    //*
    //SARUNLD DD DSN=XXXXXX.XXXXXX.SARUNLD,
    //        DISP=(,CATLG,),
    //        DCB=(RECFM=VB,LRECL=32756,BLKSIZE=32760),
    ...
    //SYSPRINT DD SYSOUT=*
    //SYSIN DD *
    UNLOAD
    /*
    //
    Note: The SARUNLD output from above will be used in the SARDBASE MERGE below.

  • SARDBASE ADDDS
    //XXXXXXXX JOB
    //SARDBASE EXEC PGM=SARDBASE,PARM='VIEW.DB2' <=== Modify DB name
    //STEPLIB DD DISP=SHR,DSN=VIEW.CAILIB <=== Modify, if used
    //SYSPRINT DD SYSOUT=*
    //SYSIN DD *
    ADDDS DATA ...
    ADDDS DATA ...
    ...
    ADDDS INDEX ...
    ADDDS INDEX ...
    ...
    /*
    //
  • SARDBASE MERGE
    //XXXXXXXX JOB
    //SARDBASE EXEC PGM=SARDBASE,PARM='VIEW.DB2' <=== Modify DB name
    //STEPLIB DD DISP=SHR,DSN=VIEW.CAILIB <=== Modify, if used
    //*
    //SARMERG1 DD DSN=XXXXXX.XXXXXX.SARUNLD,DISP=SHR
    //SYSPRINT DD SYSOUT=*
    //SYSIN DD *
    MERGE
    /*
    //
    Note: The SARUNLD output from above is used as the one and only SARDBASE MERGE input (SARMERG1).

  • SARDBASE RENAME
    //XXXXXXXX JOB
    //SARDBASE EXEC PGM=SARDBASE,PARM='VIEW.DB1' <=== Modify DB name
    //STEPLIB DD DISP=SHR,DSN=VIEW.CAILIB <=== Modify, if used
    //SYSPRINT DD SYSOUT=*
    //SYSIN DD *
    RENAME VIEW.DB3
    /*
    //
  • SARDBASE RENAME

    //XXXXXXXX JOB
    //SARDBASE EXEC PGM=SARDBASE,PARM='VIEW.DB2' <=== Modify DB name
    //STEPLIB DD DISP=SHR,DSN=VIEW.CAILIB <=== Modify, if used
    //SYSPRINT DD SYSOUT=*
    //SYSIN DD *
    RENAME VIEW.DB1
    /*
    //

In CA View 2.0, because there was a maximum of 65,535 sysouts collected to one generation, it was sometimes necessary to run multiple standard backups in one day, so that the wrapping of sequence numbers (of sysouts in a generation) would not occur.

In CA View 11.0 and later, there is a maximum of 65,535 sysouts, for one Sysout ID, in one generation. It would then no longer be necessary to run multiple backups in one day, if it was strictly for that reason.