Space announcements

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

REPOS DELETE statement (PTF BQU2282 applied)


The REPOS DELETE statement directs Log Master to delete rows from tables within the Repository. The maintenance level of your product determines the available options.

The following figure shows the details for the REPOS DELETE statement syntax:


    REPOS DELETE directs Log Master to delete rows from one or more of the following tables within the Repository:

    • Old Objects Table (ALPOLDO, used for overtime processing)

    • Open Unit of Recovery table (ALPURID, used for ongoing processing)

    • SYSCOPY record table (ALPSYSCP, used for completion processing)

    • HISTORY work file tables (ALPSQLF, ALPRPTF, ALPLODF, ALPDDLF, ALPCMDF, ALPADRF, ALPLOGF, ALPWHIS, ALPWLSH)

    Depending on your environment and the settings that you use to update the Repository, the size of the tables can increase more rapidly than the other tables. Use REPOS DELETE to reduce the size of only these tables.

    Be aware of the following points about the REPOS DELETE keyword:

    • When you specify REPOS DELETE, the scan range definition of the LOGSCAN statement is not required because Log Master does not read the DB2 log to delete Repository rows.

    • You can specify one or more of the following keywords in the same log scan and specify multiple repository delete objects:
      • OVERTIME
      • ONGOING
      • SYSCOPY
      • HISTORY
    • You can generate JCL to delete rows from selected Repository tables by using the Generate REPOS DELETE JCL option on the Main Menu of the Log Master online interface.

    • You can also delete or display information from ALPOLDO and ALPURID Repository tables directly through the Log Master online interface, without using JCL. Use the Delete/Display Repository Tables option on the Main Menu.

    • Work ID specification is required for ONGOING or HISTORY repository deletion.

    • Either DBAME or TSNAME specification is required for SYSCOPY repository deletion.

    • DBAME, TSNAME, or TBNAME specification is required for OVERTIME repository deletion.

    Select from the following values:

    Option Description
    REPORT ONLY Directs Log Master to report only the number of the qualified rows for each specified repository table. No records are deleted.

    OVERTIME

    (default) Directs Log Master to delete rows from the Old Objects Table of the Repository (ALPOLDO) Log Master uses this table during overtime processing.

    Rows in this table represent either compression dictionaries or instances of objects that might have been dropped or dropped and re-created. This is the default value.

    ONGOING

    Directs Log Master to delete rows from the Open Unit of Recovery table of the Repository (ALPURID) Log Master uses this table for ongoing processing.

    Rows in this table contain information about transactions (units of recovery) that were open at the end of a previous ongoing log scan and that Log Master stored for later processing.

    HISTORY

    Directs Log Master to delete rows from work output or file pointer tables Log Master saves the results of a work ID in the Repository.

    The results include both the final status of the work ID and pointers to the various files generated as the work ID runs.  These files include logical log files, SQL files, load files, report files, DDL files, command files, and drop recovery files.

    SYSCOPY Directs Log Master to delete rows from the SYSCOPY Repository table (ALPSYSCP)
    WORKID

    Directs Log Master to delete only the ALPURID or HISTORY table rows that relate to a work ID (or set of work IDs) that you specify

    To specify a set of work IDs, use wildcard characters to define a string pattern for either the userID, the workID, or both parts of the work ID name. Log Master deletes rows in the Repository table or tables that contain work IDs that match your string pattern. Use the same wildcard characters that you use when selecting log records. For more information, see WORKID statement.

    To specify multiple sets of work IDs, include an additional log scan in your job or job step (with an additional REPOS DELETE keyword).

    The WORKID option is required for ONGOING and HISTORY tables.

    DBNAME

    Directs Log Master to delete OVERTIME, SYSCOPY or both kind of rows related to the database or databases. To specify a set of databases, use wildcard characters to define a string pattern for database names.

    You can specify the DBNAME clause only once.

    The DBNAME, TSNAME, and TBNAME options are mutually exclusive

    The DBNAME option is valid only for OVERTIME and SYSCOPY tables.

    TSNAME

    Directs Log Master to delete OVERTIME, SYSCOPY or both kind of rows related to the table space or spaces.

    TSNAME consists of databaseName.tablespaceName. The default database name is DSNDB04. To specify a set of table spaces, use wildcard characters to define a string pattern for the database name, table space name, or both parts of the clause.

    You can specify the TSNAME clause only once.

    The DBNAME, TSNAME, and TBNAME options are mutually exclusive

    The TSNAME option is valid only for OVERTIME and SYSCOPY tables.

    TBNAME

    Directs Log Master to delete OVERTIME rows related to the table.

    TBNAME consists of tableOwner.tableName. The default table owner is the user ID who runs the job. To specify a set of tables, use wildcard characters to define a string pattern for either database name, table space name, or both parts of TBNAME.

    You can use the IN databaseName.tablespaceName option to identify the database and table space in which the table is located.

    You can specify the TBNAME clause only once.

    The DBNAME, TSNAME, and TBNAME options are mutually exclusive

    The TBNAME option is valid only for OVERTIME tables.

    RECORD TYPE

    Directs Log Master to delete OVERTIME rows based on the DB2 object types.

    The following values are valid:

    Value Description
    ALL (default) All types of overtime objects
    TABLE Structure definitions for instances of DB2 tables that Log Master stores in the Repository for use in overtime processing
    DICTIONARY Compression dictionaries that Log Master stores in the Repository for use with compressed table spaces
    ALL Directs Log Master to delete all rows from the Repository tables that you specify
    AGE (numOfDays)

    Directs Log Master to delete rows from your specified Repository tables that are older than a specified number of days

    Enter a number of days between 1 and 32,767.

    RBA | LRSN X 'byteString'

    Directs Log Master to delete rows from your specified Repository tables that were created before a specific RBA/LRSN

    The byte string can be up to 12 characters long. For extended RBAs/LRSNs, it can be up to 20 characters long. Use the following format: RBA X'nnnnnnnnnnnn'.

    DATE (MM/DD/YY)

    Directs Log Master to delete rows from your specified Repository tables that were created before a specified date

    Enter a date using one of the available formats, including:

    • MM/DD/YYYY (USA)

    • DD.MM.YYYY (EUR)

    • YYYY-MM-DD (ISO, JIS)

    BEFORE OLDEST ARCHIVE

    Directs Log Master to delete rows from your specified Repository tables that were created before the starting timestamp value of the oldest archive log file defined in the bootstrap data set (BSDS) of the current DB2 subsystem

    You must specify a value for the row deletion criteria (ALL, AGE, DATE, or BEFORE OLDEST ARCHIVE).


    REPOS DELETE directs Log Master to delete rows from one or more of the following tables within the Repository:

    • Old Objects Table (ALPOLDO, used for overtime processing)

    • Open Unit of Recovery table (ALPURID, used for ongoing processing)

    • SYSCOPY record table (ALPSYSCP, used for completion processing)

    • HISTORY work file tables (ALPSQLF, ALPRPTF, ALPLODF, ALPDDLF, ALPCMDF, ALPADRF, ALPLOGF, ALPWHIS, ALPWLSH)

    Depending on your environment and the settings that you use to update the Repository, the size of the tables can increase more rapidly than the other tables. Use REPOS DELETE to reduce the size of only these tables. To reduce the overall size of the Repository, use the sample REXX exec provided with the product. For more information, see Maintaining the Repository.

    Be aware of the following points about the REPOS DELETE keyword:

    • When you specify REPOS DELETE, the scan range definition of the LOGSCAN statement is not required because Log Master does not read the DB2 log to delete Repository rows.

    • You can specify one or more of the following keywords  in the same log scan, but you cannot specify the same keyword more than once.

      • OVERTIME
      • ONGOING
      • SYSCOPY
      • HISTORY
    • You can generate JCL to delete rows from selected Repository tables by using the Generate REPOS DELETE JCL option on the Main Menu of the Log Master online interface.

    • You can also delete or display information from ALPOLDO and ALPURID Repository tables directly through the Log Master online interface, without using JCL. Use the Delete/Display Repository Tables option on the Main Menu.

    • Work ID specification is required for ONGOING or HISTORY repository deletion.

    • Either DBAME or TSNAME specification is required for SYSCOPY repository deletion.

    • DBAME, TSNAME, or TBNAME specification is required for OVERTIME repository deletion.

    Select from the following values:

    Option Description
    REPORT ONLY Directs Log Master to report only the number of the qualified rows for each specified repository table. No records are deleted.

    OVERTIME

    (default) Directs Log Master to delete rows from the Old Objects Table of the Repository (ALPOLDO) Log Master uses this table during overtime processing.

    Rows in this table represent either compression dictionaries or instances of objects that might have been dropped or dropped and re-created. This is the default value.

    ONGOING

    Directs Log Master to delete rows from the Open Unit of Recovery table of the Repository (ALPURID) Log Master uses this table for ongoing processing.

    Rows in this table contain information about transactions (units of recovery) that were open at the end of a previous ongoing log scan and that Log Master stored for later processing.

    HISTORY

    Directs Log Master to delete rows from work output or file pointer tables Log Master saves the results of a work ID in the Repository.

    The results include both the final status of the work ID and pointers to the various files generated as the work ID runs.  These files include logical log files, SQL files, load files, report files, DDL files, command files, and drop recovery files.

    SYSCOPY Directs Log Master to delete rows from the SYSCOPY Repository table (ALPSYSCP)
    WORKID

    Directs Log Master to delete only the ALPURID or HISTORY table rows that relate to a work ID (or set of work IDs) that you specify

    To specify a set of work IDs, use wildcard characters to define a string pattern for either the userID, the workID, or both parts of the work ID name. Log Master deletes rows in the Repository table or tables that contain work IDs that match your string pattern. Use the same wildcard characters that you use when selecting log records. For more information, see WORKID statement.

    To specify multiple sets of work IDs, include an additional log scan in your job or job step (with an additional REPOS DELETE keyword).

    The WORKID option is required for ONGOING and HISTORY tables.

    DBNAME

    Directs Log Master to delete OVERTIME, SYSCOPY or both kind of rows related to the database or databases. To specify a set of databases, use wildcard characters to define a string pattern for database names.

    You can specify the DBNAME clause only once.

    The DBNAME, TSNAME, and TBNAME options are mutually exclusive

    The DBNAME option is valid only for OVERTIME and SYSCOPY tables.

    TSNAME

    Directs Log Master to delete OVERTIME, SYSCOPY or both kind of rows related to the table space or spaces.

    TSNAME consists of databaseName.tablespaceName. The default database name is DSNDB04. To specify a set of table spaces, use wildcard characters to define a string pattern for the database name, table space name, or both parts of the clause.

    You can specify the TSNAME clause only once.

    The DBNAME, TSNAME, and TBNAME options are mutually exclusive

    The TSNAME option is valid only for OVERTIME and SYSCOPY tables.

    TBNAME

    Directs Log Master to delete OVERTIME rows related to the table.

    TBNAME consists of tableOwner.tableName. The default table owner is the user ID who runs the job. To specify a set of tables, use wildcard characters to define a string pattern for either database name, table space name, or both parts of TBNAME.

    You can use the IN databaseName.tablespaceName option to identify the database and table space in which the table is located.

    You can specify the TBNAME clause only once.

    The DBNAME, TSNAME, and TBNAME options are mutually exclusive

    The TBNAME option is valid only for OVERTIME tables.

    RECORD TYPE

    Directs Log Master to delete OVERTIME rows based on the DB2 object types.

    The following values are valid:

    Value Description
    ALL (default) All types of overtime objects
    TABLE Structure definitions for instances of DB2 tables that Log Master stores in the Repository for use in overtime processing
    DICTIONARY Compression dictionaries that Log Master stores in the Repository for use with compressed table spaces
    ALL Directs Log Master to delete all rows from the Repository tables that you specify
    AGE (numOfDays)

    Directs Log Master to delete rows from your specified Repository tables that are older than a specified number of days

    Enter a number of days between 1 and 32,767.

    RBA | LRSN X 'byteString'

    Directs Log Master to delete rows from your specified Repository tables that were created before a specific RBA/LRSN

    The byte string can be up to 12 characters long. For extended RBAs/LRSNs, it can be up to 20 characters long. Use the following format: RBA X'nnnnnnnnnnnn'.

    DATE (MM/DD/YY)

    Directs Log Master to delete rows from your specified Repository tables that were created before a specified date

    Enter a date using one of the available formats, including:

    • MM/DD/YYYY (USA)

    • DD.MM.YYYY (EUR)

    • YYYY-MM-DD (ISO, JIS)

    BEFORE OLDEST ARCHIVE Directs Log Master to delete rows from your specified Repository tables that were created before the starting timestamp value of the oldest archive log file defined in the bootstrap data set (BSDS) of the current DB2 subsystem

    You must specify a value for the row deletion criteria (ALL, AGE, DATE, or BEFORE OLDEST ARCHIVE).

    REPOS DELETE directs Log Master to delete rows from one or more of the following tables within the Repository:

    • Old Objects Table (ALPOLDO, used for overtime processing)

    • Open Unit of Recovery table (ALPURID, used for ongoing processing)

    • (PTF BQU1717 applied) SYSCOPY record table (ALPSYSCP, used for completion processing)

    • (PTF BQU1717 applied) HISTORY work file tables (ALPSQLF, ALPRPTF, ALPLODF, ALPDDLF, ALPCMDF, ALPADRF, ALPLOGF, ALPWHIS, ALPWLSH)

    Depending on your environment and the settings that you use to update the Repository, the size of the tables can increase more rapidly than the other tables. Use REPOS DELETE to reduce the size of only these tables. To reduce the overall size of the Repository, use the sample REXX exec provided with the product. For more information, see Maintaining the Repository.

    Be aware of the following points about the REPOS DELETE keyword:

    • When you specify REPOS DELETE, the scan range definition of the LOGSCAN statement is not required because Log Master does not read the DB2 log to delete Repository rows.

    • You can specify both the OVERTIME and the ONGOING keyword in the same log scan, but you cannot specify either keyword more than one time.

    • You can generate JCL to delete rows from either or both of these Repository tables by using the Generate REPOS DELETE JCL option on the Main Menu of the Log Master online interface.

    • You can also delete (or display) information from the same two Repository tables directly through the Log Master online interface, without using JCL. Use the Delete/Display Repository Tables option on the Main Menu.

    Select from the following values:

    Option Description
    OVERTIME

    (default) Directs Log Master to delete rows from the Old Objects Table of the Repository (ALPOLDO) Log Master uses this table during overtime processing.

    Rows in this table represent either compression dictionaries or instances of objects that might have been dropped or dropped and re-created.

    ONGOING

    Directs Log Master to delete rows from the Open Unit of Recovery table of the Repository (ALPURID) Log Master uses this table for ongoing processing.

    Rows in this table contain information about transactions (units of recovery) that were open at the end of a previous ongoing log scan and that Log Master stored for later processing.

    The WORKID keyword directs Log Master to delete only the ALPURID rows that relate to a work ID (or set of work IDs) that you specify. To specify a set of work IDs, use wildcard characters to define a string pattern for either the userID, the workID, or both parts of the work ID name. Log Master deletes rows in the ALPURID table that contain work IDs that match your string pattern. Use the same wildcard characters that you use when selecting log records. For more information, see WORKID statement.

    To specify multiple sets of work IDs, include an additional log scan in your job or job step (with an additional REPOS DELETE keyword).

    ALL Directs Log Master to delete all rows from the Repository tables that you specify

    AGE (numOfDays)

    Directs Log Master to delete rows from your specified Repository tables that are older than a specified number of days

    Enter a number of days between 1 and 32,767.

    RBA | LRSN X 'byteString'

    Directs Log Master to delete rows from your specified Repository tables that were created before a specific RBA/LRSN

    The byte string can be up to 12 characters long. For extended RBAs/LRSNs, it can be up to 20 characters long. Use the following format: RBA X'nnnnnnnnnnnn'.

    DATE (mm/dd/yy)

    Directs Log Master to delete rows from your specified Repository tables that were created before a specified date

    Enter a date using one of the available formats, including:

    • MM/DD/YYYY (USA)

    • DD.MM.YYYY (EUR)

    • YYYY-MM-DD (ISO, JIS)

    BEFORE OLDEST ARCHIVE Directs Log Master to delete rows from your specified Repository tables that were created before the starting timestamp value of the oldest archive log file defined in the bootstrap data set (BSDS) of the current DB2 subsystem

    You must specify a value for the row deletion criteria (ALL, AGE, DATE, or BEFORE OLDEST ARCHIVE).

    (PTF BQU1717 not applied) If you specify REPOS DELETE without specifying either the OVERTIME or the ONGOING keywords, the default value is OVERTIME.


    Was this page helpful? Yes No Submitting... Thank you

    Comments