PART NUMBER VERSION NUMBER EDITION NUMBER 312564001 1.
Lifecycle Director™ DB2 Manager User Guide Version 1.
Information contained in this publication is subject to change without notice. We welcome your feedback. Please contact the Global Learning Solutions Feedback System at: GLSFS@Stortek.com or Global Learning Solutions Storage Technology Corporation One StorageTek Drive Louisville, CO 80028-3256 USA Please include the publication name, part number, and edition number in your correspondence if they are available.
Table of contents INTRODUCTION..................................................................................................................7 PRODUCT DESCRIPTION .................................................................................................8 INTRODUCTION .........................................................................................................8 PRODUCT FUNCTIONS ...............................................................................................
ENVCNTL: SMFRECID ................................................................................................35 ENVCNTL: OBJSIZE.....................................................................................................36 ENVCNTL: READTIMEOUT ........................................................................................36 ENVCNTL: WRITETIMEOUT.......................................................................................37 TAPECNTL PARAMETERS ................................
Allocation recovery........................................................................................................72 Shutdown processing .....................................................................................................73 'Resource unavailable' condition...................................................................................74 TABLE MIGRATION PROCESSING..............................................................................75 INTRODUCTION ........................
SQLIN entry specification............................................................................................102 Print reports.................................................................................................................103 Condition codes ...........................................................................................................104 Utility failure and restart considerations ....................................................................
OTD260XX – CONTROL REGION WRITER MESSAGES .............................................162 OTD270XX - CONTROL REGION HOUSEKEEPING TASK MESSAGES .........................165 DB2 MANAGER ERROR AND REASON CODES .........................................................166 CONTROL REGION RETURN CODES .........................................................................169 APPENDICES ....................................................................................................................
Introduction This Lifecycle Director DB2 Manager User Guide provides all the information required for installation, implementation and operation of the DB2 Manager product for the enabling of Lifecycle Director support for the storage and retrieval of table rows using IBM's DB2 relational database management software. For ease of reference, the product will be referred to as DB2 Manager throughout the remainder of this manual.
Product Description 1 Introduction Storage Technology's DB2 Manager software product is designed to implement Archive Manager support for storage of table rows using IBM's DB2 relational database management product. Archive Manager is a Storage Technology archival database management product, which primarily uses tape cartridge media for storage of archived objects. Archive Manager also optionally enables disk copies of objects in an Archive Manager database to be retained.
request. Standard DB2 processing then requires the use of a cursor mechanism in order to access each row from the result table, rows being retrieved via an SQL FETCH command. In cases where rows in the result table have been migrated from DB2 to Archive Manager, the resulting FETCH commands may generate one or more tape mounts in order to service the application program’s SQL request.
within the table to be released and re-used, enabling a reduction in the overall size of the DB2 tablespace used for table storage. Reduction in the tablespace size will give a corresponding reduction in the overall amount of disk space required to support DB2 database usage, and also reduce the amount of DB2 housekeeping processing (in particular, image-copy and re-organization processing) required for the database containing the table(s) enabled for DB2 Manager migration processing.
A migrated row which has been retrieved from an Archive Manager database is presented back to the calling application on reference via SQL. No indication is given to the application that the row has been retrieved from Archive Manager, and the contents of the row will be identical to those prior to migration of the row from DB2.
updated row will be stored back in the DB2 table from which it was originally migrated. All reference to the migrated copy of the row in the Archive Manager database will have been deleted, causing this row to be unreferenced. This will effectively “re-migrate” the row from Archive Manager to DB2.
Management of migrated rows A set of batch utilities is supplied with the product in order to assist in management of migrated rows. The following utilities are supplied with v1.1 of the product: • Row restore utility. This will allow migrated rows to be returned to the table from which they were migrated. Customer-specified rules, using SQL command syntax, are used to select migrated rows for restore. • Table analysis utility.
2. Primary key. This is a 4-byte (fullword) binary value, which is automatically assigned by DB2 Manager during migration processing. A primary key value of 1 will be assigned to the object containing the first row archived from a table after it has been enabled for archival. All rows within a single Archive Manager object will have the same primary key identifier. DB2 Manager will increment the primary key by 1 when creating a new object. 3. Archive date.
Rows which have a high likelihood of being updated after archival may cause a significant amount of archival and re-archival processing. A table containing rows which are likely to be updated in this manner are not suitable for migration using DB2 Manager. DB2 Manager does not impose limitations on the way in which rows are referenced from a DB2 application program. Every possible means of accessing a migrated row via SQL commands is supported, including joins and unions.
exclusive storage of migrated row stubs, and one or more partitions for storage of non-migrated rows. Database reorganization processing should not be performed on the partition containing the migrated row stubs, unless absolutely necessary. Reorganization of this partition will cause all migrated rows to be retrieved from Archive Manager.
This page is intentionally left blank DB2 Manager User Guide StorageTek Proprietary 17
Installation and Implementation 2 This section describes the activities required to install and implement DB2 Manager for use in migrating and retrieving DB2 table rows to and from Archive Manager in a host system environment. After all activities described in this section have been successfully completed, DB2 Manager will be fully installed and Archive Manager support for DB2 may then be enabled.
Install distribution libraries DB2 Manager V1.1 is distributed on a standard-labeled magnetic tape cartridge in SMP/E RELFILE format. The cartridge has a serial number of OTD110. The distribution tape will contain the following datasets: Dataset Name Description 1 SMPMCS SMP/E modification control statements for installation of the product. 2 STK.SOTD110.F1 SMP/E JCLIN file. 3 STK.SOTD110.F2 Partitioned dataset in IEBCOPY UNLOAD format containing JCL for use during product installation. 4 STK.
On completion of the above step a partitioned dataset containing JCL to be used during the remainder of the installation process will have been created. 2) Edit member SMPEDEF from the installation JCL dataset unloaded in the preceding step, as described within the dataset member itself. This job will define and initialize the SMP/E consolidated software inventory (CSI) dataset and create other SMP/E system datasets and the DB2 Manager target and distribution libraries.
After unloading the sample parameter library, review all parameter values, and amend as necessary to reflect the host system's operating environment, and your own requirements for DB2 Manager migration and retrieval processing. Refer to chapter 3 of this manual for a full description of the DB2 Manager parameter library and the format of individual parameters. Perform MVS host system modifications The following MVS system changes will be required in order to implement DB2 Manager: a.
The following is an example of how to specify the PPT entry in the appropriate SCHEDxx member of SYS1.PARMLIB: PPT PGMNAME(OTDBP200) NOSWAP KEY(7) SYST e. Update FLPA or MLPA definitions. The DB2 Manager SQL intercept module OTDBP300 from the distribution LPA library must be installed in the FLPA or MLPA.
f. Allocate DB2 Manager SMF record identifier. The DB2 Manager control region will optionally create SMF records during object retrieval processing. This option is controlled via the SMFRECID parameter in the ENVCNTL parameter library member. If it is required that DB2 Manager should create SMF records, a unique SMF user record identifier (in the range 128-255) should be assigned for DB2 Manager use. The allocated value should then be identified to DB2 Manager via the ENVCNTL SMFRECID parameter. g.
Primary or secondary DB2 Manager tape datasets will be released under the following circumstances: • The Archive Manager tape backup utility will automatically uncatalog backup datasets which are being recreated during the migration process (this will occur when objects are added to a partially-used volume during the migration process; the backup of the partially-used volume will be released).
To avoid any unnecessary and unpredictable delays due to this situation, any automated operator reply facility which is present on the host system should be configured to reply 'CANCEL' to the above message for any DB2 Manager retrieval request (ie) a request for retrieval from an Archive Manager tape dataset. DB2 Manager will handle a reply of 'CANCEL' in the following manner: 1. For row retrieval requests, a ‘resource unavailable’ response will be raised by DB2 Manager.
Resource type Resource name Access required DATABASE LCDDB2 CREATETAB TABLESPACE LCDDB2.LCDDB2TS USE OF TABLE LCDDB2.PLAN_TABLE SELECT,DELETE, INSERT,UPDATE TABLE LCDDB2.REGISTRY SELECT,DELETE,I NSERT,UPDATE Member OTDBDEF in the distributed DB2 Manager JCL library supplies a job to allocate and define this database, and to grant the above authorities. Edit this member, following the instructions at the head of the member, and submit the job.
Define Archive Manager databases DB2 Manager uses the Archive Manager component of the Lifecycle Director of DB2 product for storage and retrieval of objects. Migrated rows are held in one or more Archive Manager databases, one Archive Manager database being used per DB2 table which has been enabled for migration processing (ie) there is a one-for-one correspondence between DB2 tables and Archive Manager databases in the DB2 Manager configuration.
Data retention This entry should be allowed to default to a period value of 0 years and 0 days (ie) no automatic expiry. Archive Manager objects should not be allowed to expire. They will be explicitly deleted by the DB2 Manager database housekeeping utility when they do not contain any more active migrated rows. OTSN4300 Lifecycle Director Archive Manager V2.
OTSN4301 Lifecycle Director Archive Manager V2.6 Storage Level Definition Enter values COMMAND ===> ------------------------------------------------------------------------------Primary index name ===> OTDB.V1R1.TEST.
index definition parameters for the Archive Manager database being defined. 5. After all database definition and initialization parameters have been accepted, one or more Access Method Services (AMS) control panels will be displayed to allow customization of AMS parameters used by Archive Manager when defining system datasets for the database being defined. AMS control panels will be displayed in the following sequence: 1. OTSN4302 - the primary index AMS control panel. This panel is always displayed.
OTSN4302 Lifecycle Director Archive Manager V2.6 Access Method Services Control Enter values COMMAND ===> ------------------------------------------------------------------------------Primary index name ===> OTDB.V1R1.TEST.INDEX Primary index control: Volume serial number Unit of allocation Primary allocation value Secondary allocation value Data CI size Index CI size ===> ===> ===> ===> ===> ===> Delete before define? ===> (Y/N) Press ENTER after all details have been entered correctly.
be used for allocation of the index component of the dataset (KSDS only). This should be a valid VSAM control interval size. If omitted, a control interval size of 2k is used for the index component. Delete before Optional entry. Enter the value 'Y' if Archive define? Manager should attempt to delete the dataset before it is defined. Enter 'N' if no deletion request should be issued. Press 'ENTER' after all required entries have been made on each panel.
DB2 Manager User Guide StorageTek Proprietary 33
DB2 Manager Parameter Specification 3 DB2 Manager uses its own parameter library to allow users to control the operation of the product. This parameter library is a partitioned dataset containing the following members: ENVCNTL - used to specify general parameters relating to the DB2 Manager operating environment. TAPECNTL - used to specify controls relating to object retrieval processing by the DB2 Manager control region.
record. Individual keyword parameters may not be continued over more than one record. An asterisk ('*') in character position 1 will indicate a comment record, which will be ignored for parameter validation processing. Any departure from this general format will be indicated with individual parameter descriptions.
ENVCNTL: OBJSIZE OBJSIZE = nnnnn Requirement: Optional Default: 1000 Validation: 'nnnnn' = a 1- to 5-digit numeric value in the range 1-65535. Use: The OBJSIZE parameter is used to specify the maximum number of migrated rows to be stored per Archive Manager object.
request will be rejected with a ‘timeout’ condition. An SQL error of –652 will be returned to the requesting application. Field SQLERRD(6) in the SQLCA will contain the hexadecimal value x’0A’. ENVCNTL: WRITETIMEOUT WRITETIMEOUT = nnnn Requirement: Optional Default: 10 Validation: ‘nnnn’ = a 1- to 4-digit numeric value in the range 1-1440. Use: The WRITETIMEOUT parameter specifies the maximum number of minutes a writer task is to wait for a request, when connected to an Archive Manager database.
Use: The MAXTRDR parameter specifies the number of active tape-reader subtasks which are to be created in the DB2 Manager control region. Notes: This parameter indirectly controls the maximum number of tape drives which may be concurrently allocated by the control region.
and may improve retrieval response times. If this parameter is omitted, a default value of MAXDRDR=4 will be used. TAPECNTL: MAXTWTR MAXTWTR = nnn Requirement: Optional Default: 4 Validation: nnn = 1-3 digit numeric value in range 1 - 255 Use: The MAXTWTR parameter specifies the number of active tape-writer subtasks which are to created in the DB2 Manager control region. Notes: Each execution of the DB2 Manager table migration utility will acquire a single tape-writer subtask.
scheduler subtask introduces some processing overhead, so care should be taken to avoid over-allocation of this setting. This setting may be varied during DB2 Manager operation via the 'SET MAXSCHED’ operator command. If this parameter is omitted, a default value of MAXSCHED=4 will be used.
Requirement: Optional Default: 0 Validation: nnnn = 1-4 digit numeric value in range 0 - 1440 Use: The RETAINTAPE parameter specifies the number of minutes for which a tape is to remain mounted after all outstanding retrieval requests from that tape have been processed by the DB2 Manager control region. A tape which has not been referenced for the specified interval will be automatically dismounted.
If set to 0 (the default), no internal queuing of requests will take place in the above circumstances and the request will be rejected with a ‘resource unavailable’ reason code. If the TAPEWAIT parameter value is in the range 1-1439, requests will be queued internally until processed or until the maximum queuing time in minutes (as specified in this parameter) has been exceeded. Requests will then be rejected with a ‘resource unavailable’ reason code (as above).
This page is intentionally left blank DB2 Manager User Guide StorageTek Proprietary 43
DB2 Manager Control Region 4 All access to Archive Manager databases containing migrated rows is performed via the DB2 Manager control region. This is a started task, which must be initiated prior to performing any DB2 row migration or retrieval activities. This chapter describes the operation and control of the DB2 Manager control region. The DB2 Manager control region performs the following functions: • Enables DB2 Manager for Archive Manager database processing.
• The distributed DB2 Manager and Archive Manager load libraries must be available to this task, either via the system linklist, or from the procedure's STEPLIB concatenation. • The DB2 Manager control region must run with APF-authorization. Both the DB2 Manager and Archive Manager load libraries must therefore be APF-authorized.
Control region components The control region must be initialized in order to enable DB2 Manager to access migrated rows, and to allow migration of rows from DB2 to Archive Manager. Figure 4 illustrates the structure of the control region and the migrated row access mechanism. This also shows the MLPA/FLPA-resident SQL intercept processor OTDBP300, which must be defined as a DB2 row edit procedure for each table which is to be enabled for migration processing by DB2 Manager.
The following control region components are illustrated in Figure 4: • Control processor. This component is responsible for initiation and termination of the control region, and for processing operator requests. • Writer tasks. There will be one or more writer tasks – the number of writer tasks is controlled via the MAXTWTR initialization parameter.
Processing requests for access to migrated rows Once DB2 Manager initialization has been completed, batch, TSO, CICS or IMS programs will be able to access migrated rows using standard SQL processing, without modification. DB2 Manager implements support for access to migrated rows which is made via SQL SELECT, UPDATE and DELETE commands. Note that any rows created in a table via an SQL INSERT command will be stored in DB2.
volume. This will improve response times for subsequent requests to the same tape volume, but may cause an additional processing overhead if the tape has to be dismounted prior to the task allocating a different tape volume (as required in task selection criterion (3) above). Refer to page 40 for a description of the RETAINTAPE parameter. Note that the above retrieval processing is performed for each migrated row which is referenced via an SQL SELECT command.
SQL DELETE processing A request by an application to delete a migrated row via an SQL DELETE command will cause that row to be retrieved via the process described in the preceding section. The row will then be deleted, causing the archive stub for the row to be removed from the DB2 table. All reference to the migrated row will then have been removed, as for SQL UPDATE processing.
• Terminate the DB2 Manager control region. All messages issued by DB2 Manager in response to an operator request are documented in chapter 7 of this manual. This section specifies operator request formats, and gives examples of DB2 Manager responses to these requests. Display summary status D(ISPLAY) This request is used to produce a summary display of the status of the DB2 Manager control region processing configuration. The DISPLAY command may be abbreviated to the single character 'D'.
the status of the internal scheduler queue lock and the length of the scheduler queue, in message OTD20062. In addition, message OTD20063 will be displayed for each reader, writer and scheduler task in the system, giving the following details: Status - this field indicates the current status of the identified task. It can take the following values: NULL - the task has never been initialized. It is not available for object recall. WAIT - the task is currently waiting for work.
Tape - identifies the sequence number within Archive Manager database Lastuse - for tasks with status = WTRT, this gives the time (in format HH:MM:SS) that the last request for retrieval from this tape volume was completed. This timestamp is used by DB2 Manager to determine which tape volume will be automatically dismounted to satisfy a request for retrieval from another tape volume, when there are no spare drives on the system.
Display detail status D(ISPLAY) T(ASK = (T|D|W|S)nnn This request is used to produce a detailed display of the status of the DB2 Manager control region retrieval configuration. The DISPLAY command may be abbreviated to the single character 'D'. The TASK parameter may be abbreviated to the single character 'T'. 'nnn' is the numeric identifier of the task to be displayed (where ‘nnn’ consists of 1-3 numeric characters in the range 1-256).
Example: F LCDDB2,D T=T1 ...... OTD20063 Task T001: Status=BUSY Qlen=001 DBID=ST01 Stg_level=0 Tape=00002 OTD20066 Request 001: Type=Retrieve DBID=ST01 Jobname=WATERSGJ OTD20067 Request 001: Stg_level=0 Tape=00002 Blockid=01400005 OTD20058 Display processing completed Force purge task F(ORCE) T(ASK = (T|D|W|S)nnn The FORCE command is used to immediately terminate a tape or disk reader task, writer task or scheduler task in the DB2 Manager control region.
OTD20062 Retaintape=0001 Tapewait=0004 Objsize=00100 OTD20062 Readtimeout=0005 Writetimeout=0005 OTD20062 Maxtrdr=004 Maxdrdr=004 Maxtwtr=004 Maxqlen=100 Scheduler: Queue is unlocked; Queue Maxsched=004 length=000 OTD20063 Task T001: Status=BUSY Qlen=001 DBID=ST01 Stg_level=0 Tape=00002 OTD20063 Task T002: Status=WAIT Qlen=000 OTD20063 Task T003: Status=WAIT Qlen=000 OTD20063 Task T004: Status=WAIT Qlen=000 OTD20063 Task D001: Status=WAIT Qlen=000 OTD20063 Task D002: Status=WAIT Qlen=000 OTD20063 Task D003:
Purge task P(URGE) T(ASK) = (T|D|W|S)nnn The PURGE command is used to terminate a tape or disk reader task, a writer task or a scheduler task in the DB2 Manager control region. All outstanding requests in the task queue will be allowed to complete normally before task termination. The command may be abbreviated to a single 'P'. The TASK parameter may be abbreviated to a single 'T'.
OTD20063 Task D003: Status=WAIT Qlen=000 OTD20063 Task D004: Status=WAIT Qlen=000 OTD20063 Task W001: Status=WAIT Qlen=000 OTD20063 Task W002: Status=WAIT Qlen=000 OTD20063 Task W003: Status=WAIT Qlen=000 OTD20063 Task W004: Status=WAIT Qlen=000 OTD20063 Task S001: Status=WAIT Qlen=000 OTD20063 Task S002: Status=WAIT Qlen=000 OTD20063 Task S003: Status=WAIT Qlen=000 OTD20063 Task S004: Status=WAIT Qlen=000 OTD20058 Display processing completed ......
WRITETIMEOUT parameters. The command may be abbreviated to the single character 'S'. The values of MAXTRDR, MAXDRDR, MAXSCHED, MAXQLEN, RETAINTAPE, TAPEWAIT, OBJSIZE, READTIMEOUT and WRITETIMEOUT are initially set during DB2 Manager control region initialization from the corresponding parameters in the TAPECNTL and ENVCNTL members of the DB2 Manager parameter library.
If the value of MAXTWTR is to be increased, DB2 Manager will increase the number of initialized writer tasks, by restarting terminated tasks, and/or adding new tasks. If the value of MAXTWTR is to be decreased, DB2 Manager will terminate a number of existing writer tasks equal to the decrease in the value of MAXTWTR. These tasks will appear with the status TERM in any subsequent status display, and will not be available for object recall processing.
65535. This change will take effect the next time a database is connected for update processing by the DB2 Manager table migration utility. READTIMEOUT - DB2 Manager will alter the current setting of the READTIMEOUT parameter to the value specified in the SET command. ‘nnnn’ must be a 1-4 digit numeric value in the range 1-1440. This change will take immediate effect. WRITETIMEOUT - DB2 Manager will alter the current setting of the WRITETIMEOUT parameter to the value specified in the SET command.
OTD20063 OTD20063 OTD20063 OTD20063 OTD20063 OTD20063 OTD20063 OTD20063 OTD20063 OTD20063 OTD20063 OTD20058 Task D002: Status=WAIT Qlen=000 Task D003: Status=WAIT Qlen=000 Task D004: Status=WAIT Qlen=000 Task W001: Status=TERM Qlen=000 Task W002: Status=TERM Qlen=000 Task W003: Status=WAIT Qlen=000 Task W004: Status=WAIT Qlen=000 Task S001: Status=WAIT Qlen=000 Task S002: Status=WAIT Qlen=000 Task S003: Status=WAIT Qlen=000 Task S004: Status=WAIT Qlen=000 Display processing completed Terminate DB2 Manager
IEE600I REPLY TO 13 IS;SHUTDOWN 14 OTD20092 Do you want to proceed with shutdown (y/n)? R 14,Y IEE600I REPLY TO 14 IS;Y OTD20093 Shutdown in progress OTD20060 Task H001 has been shutdown successfully OTD25009 Tape rdr task 004 terminated OTD20060 Task T004 has been shutdown successfully OTD25009 Tape rdr task 003 terminated OTD20060 Task T003 has been shutdown successfully OTD25009 Tape rdr task 002 terminated OTD20060 Task T002 has been shutdown successfully OTD25009 Tape rdr task 001 terminated OTD20060 T
If requested, DB2 Manager will create SMF records at the following points: a. When all requests for retrieval of rows from a single tape cartridge volume have been completed by a tape reader task (ie) immediately before a busy task returns to wait status. The SMF record will contain one request section for each request processed during invocation of that reader task. b. When the limit of 100 request sections has been created by a tape reader task while processing a request queue.
4. Termination of request processing by the reader or writer task in the control region. Analysis of timestamp intervals will provide timings for the following activities: • 4-1: total time for DB2 Manager to process the request. • 2 - 1: time spent in control region scheduler queue. • 3 - 2: time spent in reader or writer task queue. • 4 - 3: time taken to retrieve object from tape or disk and locate migrated row (reader tasks) or to add migrated row to Archive Manager object (writer tasks).
Record descriptor section The SMF header section is immediately followed by the DB2 Manager record descriptor section. It has a fixed length of 38 bytes. Offset Length Format Description 18 6 bin Reserved. 24 4 bin Offset of database section. This is the offset from the start of the SMF record of the database section of the record. 28 2 bin Length of database section. This is the length in bytes of a single database section.
Offset Length Format Description 1 3 Char DB2 Manager reader/writer task number. 4 4 char Identifier of Archive Manager database being processed. 8 16 - Reserved for future use Request section The request section starts at the offset specified in the record descriptor section of the DB2 Manager SMF record. It gives information about each of the individual requests processed by the DB2 Manager reader or writer task. It has a fixed length of 96 bytes.
Offset Length Format 0 8 bin Description Request start timestamp. This gives the date and time that the request was received by the DB2 Manager edit routine. It has the format: bytes 0-3: time in hundredths of a second since midnight that request processing started. bytes 4-7: date that request processing started, in packed decimal format 0cyydddF, where F is the sign. 8 8 bin Scheduler timestamp.
Offset Length Format Description request processing ended. bytes 4-7: date that request processing ended, in packed decimal format 0cyydddF, where F is the sign. 32 2 char Return code.
Offset Length Format Description 60 2 Bin Record number within object containing stored/retrieved row 62 2 Bin Number of records containing stored/retrieved row 64 8 char Requester’s jobname 72 8 char Requester’s userid. 80 4 char Identifier of system on which request originated 84 12 - Reserved Operational considerations This section discusses miscellaneous topics relating to the operation of the DB2 Manager control region and its environment.
In a mixed operating environment which consists of both library and freestanding tape drives, the STK Host Software Component will ensure that all primary DB2 Manager tapes will be located in a library storage module. The value of MAXTRDR used in this environment should not exceed the total number of drives available in the library configuration, otherwise allocation requests for DB2 Manager tapes may be made to free-standing drives.
Rejection of a request due to the MAXQLEN value having been reached or due to the TAPEWAIT interval having been exceeded will generate an SQL – 652 error with a reason code of X'1015' in field SQLERRD(6) in the SQLCA. Use of the MAXDRDR parameter The MAXDRDR parameter is used to control the number of disk reader tasks which are active in the DB2 Manager control region.
In the DB2 Manager environment, lack of available tape drives will cause the DB2 Manager control region to enter allocation recovery. Issuing a reply of WAIT will now mean that the application issuing the SQL command which caused the tape allocation request will have to wait indefinitely for another job on the system to release a drive, before continuing. In this case, the end-user response time would be unpredictable.
• Extended CSA storage used by DB2 Manager (approximately 212k in extended subpool 241) will not be released, and will be unavailable for use by other jobs in the system until the next IPL. 'Resource unavailable' condition DB2 Manager will return a ‘resource unavailable’ condition to an SQL command which generates access to a migrated row (SQL –652 error and reason code of X'1015' set in field SQLERRD(6) in the SQLCA) in the following circumstances: 1.
Table migration processing 5 Introduction DB2 Manager provides functions to perform the migration of rows from DB2 to Archive Manager storage. These functions are provided by the DB2 Manager table migration utility, OTDBP100. The table migration utility is executed as a batch process, and should be scheduled to run at regular intervals in order to migrate rows from DB2 to an Archive Manager database.
Restrictions DB2 tables which are to be eligible for processing by DB2 Manager must adhere to the following restrictions: • Each row in the table must be indexed by a unique key. The indexing key can consist of one or multiple columns in the table. • The table must not contain large objects (LOBs), ROWID or identity columns or “distinct types”. A table which does not satisfy all the above criteria will not be processed by the DB2 Manager table migration utility.
FIELD13 TIMESTAMP , OTDBIND CHAR(1) DEFAULT '0' ) IN OTDBSYST.TAB1TS EDITPROC OTDBP300; • For existing non-partitioned tables, a new partitioning index to the new table must be created, as follows: CREATE INDEX dbname.indexname ON dbname.tabname ( OTDBIND ASC ) CLUSTER (PART 1 VALUES('0'), PART 2 VALUES('1')) .... • For existing partitioned tables, the definition of the existing partitioning index should be copied with the following modifications: CREATE INDEX dbname.indexname ON dbname.
• The contents of the existing table should be unloaded, and loaded into the new table. This will create an exact copy of the original table, with the modifications described above. • The original table should be dropped from DB2. • A view should be created of the new table. The view must have the same name as that of the original table, and should be defined as follows: CREATE VIEW dbname.tabname1 AS SELECT field1, field2, ... fieldn FROM dbname.
migration-enabled table – the last partition in this table should be removed when creating the disabled table. Alternatively, if the original tablespace used to hold the table prior to enabling it for migration processing still exists, this may be used. • • A new table must be created in this tablespace. If the original definition used to create the table prior to enabling it for migration processing exists, this should be used.
OTDBP100 - the table migration utility Migration of rows from a DB2 table to Archive Manager storage is performed using the DB2 Manager table migration utility. This is executed as a batch job, and processes a single DB2 table per execution. An SQLIN dataset entry is used to specify the selection criteria for migration of table rows. This is specified in the form of an SQL SELECT command. Refer to “SQLIN entry specification“ on page 85 for a description of the specification and usage of this entry.
Functions The table migration utility performs the following functions: • It processes and validates a series of parameters from a SYSIN file, and an object selection parameter from file SQLIN which will govern execution of the utility. A parameter specification and validation report is written to the SYSPRINT dataset. • It sequentially processes all unmigrated rows in the DB2 table identified in the SQLIN parameters and selects all rows which satisfy the migration criteria.
JCL requirements The following JCL may be used to execute the utility: //* //STEP100 EXEC PGM=OTDBP100,REGION=4096K //* //STEPLIB DD DSN=Database.Manager.load.library,DISP=SHR // DD DSN=Archive.Manager.load.library,DISP=SHR //* //SYSIN DD DSN=Execution.parameter.file,DISP=SHR //SQLIN DD DSN=Migration.criteria.file,DISP=SHR //SYSPRINT DD SYSOUT=* //* DD entries should be specified as follows: STEPLIB: Enter the names of the DB2 Manager and Archive Manager product load libraries.
to character position 71 of the record. Individual keyword parameters may not be continued over more than one record. An asterisk ('*') in character position 1 will indicate a comment record, which will be ignored for parameter validation processing. The following parameters may be specified: • LCDDBID = xxxx This is a mandatory parameter and specifies the 4-character identifier of the Archive Manager database to which rows are to be archived during execution of the utility.
• NEWTAPE=YES|NO This is an optional parameter used to cause a new tape volume in the Archive Manager database to be opened at the start of migration processing. If omitted, the default value of “NO” is used. • DB2SSID=xxxx This mandatory parameter is used to specify the subsystem identifier of the DB2 subsystem to be used during execution of the utility. The subsystem identifier ‘xxxx’ can be 1-4 characters in length.
at the first commit point (as controlled via the COMMIT parameter) after reaching this value. ‘nnnnnn’ must be a 1-6 digit numeric value in the range 0-999999. A value of 0 indicates that there is no maximum to the number of rows to be migrated during execution of the utility. If this parameter is omitted, a default value of 0 is used. • TIME=nnnn|0 This is an optional parameter specifying the maximum time for which execution of the utility is to continue.
PARMLIB requirements The following ENVCNTL parameter library entries are used by the DB2 Manager control region during table migration processing. It should be verified that these are set as required prior to the start of table migration processing.
Condition codes The table migration utility will set a condition code on completion. This code may take the following values: 0- the utility has been executed successfully. 4- a warning condition has been encountered during processing of the utility. A warning message will have been written to the SYSPRINT dataset. The utility has been executed successfully. 8- an error condition has been encountered during processing of the utility. An error message will have been written to the SYSPRINT dataset.
Further executions of the table migration job for the appropriate DB2 table may subsequently be performed as normal. Data management processing Following successful execution of a table migration process, a number of follow-up activities may be required in order to complete the management of migrated and unmigrated data.
Reorganization of other (non-migrated) partitions in the tablespace should be performed as normal. Regular reorganization will, in particular, be required for a period of time after implementation of DB2 Manager migration, in order to reclaim disk space occupied by rows which have been migrated to Archive Manager.
administration facility. The backup duplex copy is created at the same time as the backup copy. Each copy will contain a single standard-labeled dataset. The contents of each copy will be identical. The following dataset naming standards are used by Archive Manager to identify each copy in an Archive Manager tape database: ‘A’ copy: ‘hlq.Gnnnnn’ ‘B’ copy: ‘hlq.Bs.Gnnnnn’ ‘C’ copy: ‘hlq.Cs.Gnnnnn’ ‘D’ copy: ‘hlq.Ds.
Archive Manager database recovery may be required in the following circumstances: 1. loss of an individual tape volume from with an Archive Manager tape database (eg) due to media failure 2. loss of an entire Archive Manager database (eg) due to loss of data center. In both the above cases, standard Archive Manager database recovery procedures should be followed. A full description of these procedures may be found in the ‘Recovery Control Processing’ section in the Archive Manager User Manual.
If disaster recovery is being performed on another processor, all disk datasets used by DB2 Manager and Archive Manager, and all user catalog entries from the primary facility, must be restored for use on the disaster recovery facility. There is no requirement for physical recovery of any tape dataset prior to disaster recovery usage. If necessary, the primary copy of the database may be re-created using the standard Archive Manager database recovery utility (OTASP130).
DB2 Manager Utilities 6 A number of batch utility programs are supplied with DB2 Manager, for provision of a range of facilities for supporting the DB2 Manager operational environment, and for extending functional capabilities supplied with other components of the product. These utilities consist of: • OTDBP120 – the DB2 Manager row restore utility. This utility allows customers to identify migrated rows which are to be restored from Archive Manager to DB2 storage.
A print report is issued by the utility giving details of the execution parameters, the row restore selection criteria and summary information about the rows restored from Archive Manager. Functions The DB2 Manager row restore utility performs the following functions: • It will process and validate a series of execution parameters from a SYSIN file, and an SQLIN object selection parameter which will govern execution of the utility.
STEPLIB: Enter the names of the DB2 Manager and Archive Manager product load libraries. OTASxxxx: Enter the name of the primary index dataset of the Archive Manager database used for storage of objects from the DB2 table being processed by the utility. ‘xxxx’ should be set to the 4-character value used to identify the Archive Manager database in the DB2 Manager control region procedure (see “Perform MVS host system modifications” on page 21).
This mandatory parameter is used to specify the subsystem identifier of the DB2 subsystem to be used during execution of the utility. The subsystem identifier ‘xxxx’ can be 1-4 characters in length. • PLAN=xxxxxxxx This is an optional parameter which is used to specify the DB2 plan name to be used during execution of the utility, where ‘xxxxxxxx’ is the 1-8 character identifier of the plan. If omitted, a default value of OTDBL120 is used.
This is an optional parameter specifying the number of secondary extent blocks to be used during allocation of temporary dataset OTDBS120 used during execution of the utility. ‘nnnnnnn’ is a 1-7 digit numeric value in the range 1-8388607. If omitted, a default value of 10000 will be used.
Print reports The row restore utility will write a number of print reports to the SYSPRINT dataset during execution. These consist of: • Parameter specification and validation report. This will contain a list of SYSIN parameters specified (or defaulted) for execution of the utility, and a validation error report if errors are detected in parameter specification. It will also specify the SQL row restore selection statement coded in the SQLIN file. • Execution report.
the failed execution. No special actions need to be taken prior to re-starting the failed row restore job. Clean-up processing Following successful execution of the row restore utility, the storage used in the Archive Manager database for rows which have been restored to DB2 will no longer be accessible, and will be eligible for re-use. However, this space cannot be re-used until the Archive Manager object holding a restored row has been deleted from the Archive Manager database.
expiration of this time interval. Refer to the Lifecycle Director Archive Manager User Guide for information about setting pre-fetch retention periods in a database, and about executing the object management utility. Functions The DB2 Manager pre-fetch utility performs the following functions: • It will process and validate a series of execution parameters from a SYSIN file, and an SQLIN row selection parameter which will govern execution of the utility.
STEPLIB: Enter the names of the DB2 Manager and Archive Manager product load libraries. OTASxxxx: Enter the name of the primary index dataset of the Archive Manager database used for storage of objects from the DB2 table being processed by the utility. ‘xxxx’ should be set to the 4-character value used to identify the Archive Manager database in the DB2 Manager control region procedure (see “Perform MVS host system modifications” on page 21).
This mandatory parameter is used to specify the subsystem identifier of the DB2 subsystem to be used during execution of the utility. The subsystem identifier ‘xxxx’ can be 1-4 characters in length. • PLAN=xxxxxxxx This is an optional parameter which is used to specify the DB2 plan name to be used during execution of the utility, where ‘xxxxxxxx’ is the 1-8 character identifier of the plan. If omitted, a default value of OTDBL130 is used.
Contents of character positions 72-80 in each record will be ignored. A maximum of 15 records may be present in the SQLIN file. Pre-fetch rules are specified in the format of a standard DB2-compatible SQL SELECT command, which must have the general format: SELECT key1, key2, .... keyn FROM table_name WHERE pre-fetch_criteria where ‘key1’, ‘key2’, ….
o o o Primary key and archive date of the object containing the row to be pre-fetched Return and supplementary codes received from Archive Manager after processing the request The concatenated key of the DB2 row to be pre-fetched Note that there may be multiple entries in this report for the same Archive Manager object, if multiple rows within that object have been selected for pre-fetch processing. Repeated requests for pre-fetching of the same object will be ignored by Archive Manager.
After correcting the error, the utility may be rerun normally. No special actions need to be taken prior to re-starting the failed pre-fetch job. Archive Manager housekeeping processing Pre-fetched objects will be retained on disk in the Archive Manager database for the period of time specified in the definition of the database.
//* //STEPLIB // //* //OTASxxxx //SYSIN //SQLIN //SYSPRINT //* DD DD DSN=Database.Manager.load.library,DISP=SHR DSN=Archive.Manager.load.library,DISP=SHR DD DD DD DD DSN=Archive.Manager.index.dataset,DISP=SHR DSN=Execution.parameter.file,DISP=SHR DSN=Table.identification.file,DISP=SHR SYSOUT=* DD entries should be specified as follows: STEPLIB: Enter the names of the DB2 Manager and Archive Manager product load libraries.
to character position 71 of the record. Individual keyword parameters may not be continued over more than one record. An asterisk ('*') in character position 1 will indicate a comment record, which will be ignored for parameter validation processing. The following parameters may be specified: • DB2SSID=xxxx This mandatory parameter is used to specify the subsystem identifier of the DB2 subsystem to be used during execution of the utility. The subsystem identifier ‘xxxx’ can be 1-4 characters in length.
received by the utility, which will cause it to terminate with a condition code of 12. In these circumstances, the SQL statement should be corrected and the job restarted. Print reports The table analysis utility will write a number of print reports to the SYSPRINT dataset during execution. These consist of: • Parameter specification and validation report.
Figure 5: Detailed table analysis report Condition codes The table analysis utility will set a condition code on completion. This code may take the following values: 0- the utility has been executed successfully. 4- a warning condition has been encountered during processing of the utility. A warning message will have been written to the SYSPRINT dataset. The utility has been executed successfully. 8- an error condition has been encountered during processing of the utility.
migrated rows in the DB2 table will be resolved by the utility. This is required to ensure that re-organization of non-archive partitions can occur without reference to migrated rows in the Archive Manager database. The table to be processed is identified by the customer via an SQL command. Execution of the program is controlled via a series of parameters in file SYSIN.
DD entries should be specified as follows: STEPLIB: Enter the names of the DB2 Manager and Archive Manager product load libraries. OTASxxxx: Enter the name of the primary index dataset of the Archive Manager database used for storage of objects from the DB2 table being processed by the utility. ‘xxxx’ should be set to the 4-character value used to identify the Archive Manager database in the DB2 Manager control region procedure (see “Perform MVS host system modifications” on page 21).
This mandatory parameter is used to specify the subsystem identifier of the DB2 subsystem to be used during execution of the utility. The subsystem identifier ‘xxxx’ can be 1-4 characters in length. • PLAN=xxxxxxxx This is an optional parameter which is used to specify the DB2 plan name to be used during execution of the utility, where ‘xxxxxxxx’ is the 1-8 character identifier of the plan. If omitted, a default value of OTDBL170 is used.
• Parameter specification and validation report. This will contain a list of execution parameters specified (or defaulted) in file SYSIN, and a validation error report if errors are detected in parameter specification. It will also specify the table identification statement coded in the SQLIN file. • Execution report. Any errors or warning conditions encountered during execution of the utility will be identified in this report. • Summary processing report.
4- a warning condition has been encountered during processing of the utility. A warning message will have been written to the SYSPRINT dataset. The utility has been executed successfully. 8- an error condition has been encountered during processing of the utility. An error message will have been written to the SYSPRINT dataset. Execution of the utility has continued. 12 - a serious error has been encountered during processing of the utility.
utility should not be permitted, by letting the data retention period default to zero values when defining the Archive Manager database. Refer to “Define Archive Manager databases” on page 27 for information on this issue. The database maintenance procedure should be performed at regular intervals for each Archive Manager database used for storage of migrated rows by DB2 Manager, in order to recover unused space from within the database which has been freed due to object deletion.
database, a different recycle threshold may be supplied for each storage level. As Archive Manager uses a discrete set of tape cartridge volumes and disk datasets for each database, it is possible to perform the Archive Manager database maintenance procedure on multiple DB2 Manager databases concurrently. Each procedure will require a minimum of two tape cartridge drives.
This page is intentionally left blank DB2 Manager User Guide StorageTek Proprietary 117
Messages and Codes 7 DB2 Manager components communicate with the user through informational, warning and error messages. All DB2 Manager messages begin with the characters 'OTD', followed by a 5-character numeric identifier. DB2 Manager messages may be displayed on the system log or in an DB2 Manager print report.
OTD10001 OPEN failed for xxxxxxxx dataset Explanation: An attempt to open a non-VSAM dataset has failed. ‘xxxxxxxx’ identifies the filename assigned by the program to the dataset. Execution of the utility will be terminated with condition code 12. Action: Consult other available system messages for further information on the cause of the open failure. Take the appropriate corrective action and re-run the utility.
OTD10006 DB2 CAF error occurred during CONNECT |OPEN |CLOSE | DISCONNECT processing. Return Code = xxx, Reason Code = X'yyyyyyyy’ Explanation: A DB2 Call Attachment Facility error has occurred attempting to perform the type of processing identified in the message. ‘xxx’ gives the return code and ‘yyyyyyyy’ the hexadecimal reason code returned by the Call Attachment Facility. Execution of the utility is terminated with condition code 12.
Explanation: The column name identified in the message has been specified as a key field in the SQLIN file, but the column does not exist in the DB2 table. Execution of the utility is terminated with condition code 12. Action: Check that the names of the columns which uniquely index each row in the table have been specified correctly in the SQLIN file, and resubmit the job.
OTD10013 Return code ‘xx’ received during execution of TCBTOKEN | LOCASCB | ENQ macro. Explanation: An error has been received attempting to execute the system macro identified in the message. ‘xx’ is the return code received from the macro call. Execution of the utility is terminated with condition code 12. Action: Consult IBM system macro documentation for a description of the error. Take the appropriate corrective action and re-submit the job.
Explanation: The utility has been unable to obtain an DB2 Manager control region request element from ECSA storage, in order to pass a request to the control region. Execution of the utility is terminated with condition code 12. Action: This can occur if more than 1024 concurrent migrated row storage and retrieval requests are active in the system. If this is the case, reschedule the row migration job to avoid reaching this limit.
reason for the error can be identified, contact your local STK support representative. OTD10021 Insufficient storage for workareas Explanation: An attempt by the utility to allocated virtual storage has failed Execution of the utility will be terminated with condition code 12. Action: Increase the region size specified for execution of the utility and resubmit the job.
OTD120xx – row restore utility messages Messages from the DB2 Manager row restore utility will be written to the SYSPRINT dataset. OTD12000 Row Restore Utility ended with completion code xx Explanation: The DB2 Manager row restore utility has terminated. ‘xx’ gives the job completion code. This can take the following values: 0- the utility has been executed successfully. 4- a warning condition has been encountered during processing of the utility.
OTD12003 Key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx was not found in DB2 table Explanation: The column name identified in the message has been specified as a key field in the SQLIN file, but the column does not exist in the DB2 table. Execution of the utility is terminated with condition code 12. Action: Check that the names of the columns which uniquely index each row in the table have been specified correctly in the SQLIN file, and resubmit the job.
macro call. Execution of the utility is terminated with condition code 12. Action: Consult IBM system macro documentation for a description of the error. Take the appropriate corrective action and re-submit the job. If no obvious cause for the error can be determined, contact your local STK support representative. OTD12009 DB2 CAF error occurred during CONNECT | OPEN | CLOSE | DISCONNECT processing.
Explanation: Identification of objects to be restored from Archive Manager to DB2 cannot be performed via index-only processing, and a SQLIN parameter of INDEXONLY=Y has been specified (or defaulted). Execution of the utility cannot continue, and is terminated with a condition code 12. Action: Refer to a description of the INDEXONLY execution parameter on page 95 for a discussion of considerations regarding index-only processing by the row restore utility.
and re-submit the job. If no obvious reason for the error can be identified, contact your local STK support representative. OTD130xx – pre-fetch utility messages Messages from the DB2 Manager pre-fetch utility will be written to the SYSPRINT dataset. OTD13000 Batch Pre-fetch Utility ended with completion code xx Explanation: The DB2 Manager pre-fetch utility has terminated. ‘xx’ gives the job completion code. This can take the following values: 0- the utility has been executed successfully.
OTD13003 Key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx was not found in DB2 table Explanation: The column name identified in the message has been specified as a key field in the SQLIN file, but the column does not exist in the DB2 table. Execution of the utility is terminated with condition code 12. Action: Check that the names of the columns which uniquely index each row in the table have been specified correctly in the SQLIN file, and resubmit the job.
Explanation: An error has been received attempting to execute the system macro identified in the message. ‘xx’ is the return code received from the macro call. Execution of the utility is terminated with condition code 12. Action: Consult IBM system macro documentation for a description of the error. Take the appropriate corrective action and re-submit the job. If no obvious cause for the error can be determined, contact your local STK support representative.
Explanation: Identification of objects to be pre-fetch by Archive Manager cannot be performed via index-only processing, and a SQLIN parameter of INDEXONLY=Y has been specified (or defaulted). Execution of the utility cannot continue, and is terminated with a condition code 12. Action: Refer to a description of the INDEXONLY execution parameter on page 101 for a discussion of considerations regarding index-only processing by the row restore utility.
SYSPRINT dataset. The utility has been executed successfully. 8- an error condition has been encountered during processing of the utility. An error message will have been written to the SYSPRINT dataset. Execution of the utility has continued. 12 - a serious error has been encountered during processing of the utility. An error message will have been written to the SYSPRINT dataset. Execution of the utility has been terminated. Action: None. This is an informational message.
Action: Refer to page 106 of this manual for a description of SYSIN parameter formats for the table analysis utility. Correct the parameter error and re-submit the job. OTD14005 Invalid or duplicate exec | SQLIN parameter. Please refer to the DB2 Manager User Manual for valid specifications Explanation: A SYSIN parameter, or SQLIN parameter entry is invalid or has been specified more than once. Execution of the utility is terminated with condition code 12.
OTD14008 Return code ‘xx’ received during execution of TCBTOKEN | ENQ macro Explanation: An error has been received attempting to execute the system macro identified in the message. ‘xx’ is the return code received from the macro call. Execution of the utility is terminated with condition code 12. Action: Consult IBM system macro documentation for a description of the error. Take the appropriate corrective action and re-submit the job.
Action: Check that the correct DB2 table name has been specified in the SQLIN file. If not, correct the entry and re-submit the job. OTD14012 All columns in the DB2 table have been specified as KEY fields Explanation: There are no non-indexed columns in the table being analyzed. The utility requires that there be at least one non-index column in the table. Processing of the utility is terminated with condition code 12. Action: Check that the correct table name has been specified in the SQLIN statement.
OTD170xx – database housekeeping utility messages Messages from the DB2 Manager database housekeeping utility will be written to the SYSPRINT. OTD17000 Database Housekeeping Utility ended with completion code xx Explanation: The DB2 Manager database housekeeping utility has terminated. ‘xx’ gives the job completion code. This can take the following values: 0- the utility has been executed successfully. 4- a warning condition has been encountered during processing of the utility.
OTD17003 Key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx was not found in DB2 table Explanation: The column name identified in the message has been specified as a key field in the SQLIN file, but the column does not exist in the DB2 table. Execution of the utility is terminated with condition code 12. Action: Check that the names of the columns which uniquely index each row in the table have been specified correctly in the SQLIN file, and resubmit the job.
Explanation: An error has been received attempting to execute the system macro identified in the message. ‘xx’ is the return code received from the macro call. Execution of the utility is terminated with condition code 12. Action: Consult IBM system macro documentation for a description of the error. Take the appropriate corrective action and re-submit the job. If no obvious cause for the error can be determined, contact your local STK support representative.
OTD17013 Retrieval using the specified KEY fields cannot be made via INDEXONLY processing Explanation: Scanning of the table using the key fields specified in the SELECT statement in the SQLIN file cannot be performed via index-only processing. Execution of the utility cannot continue, and is terminated with a condition code 12. Action: Modify the SELECT statement in the SQLIN file to ensure that the specified columns are those used to uniquely index a row in the table, and re-submit the job.
Action: Examine other system messages for more information on the open error. Take the appropriate corrective action and restart the control region. OTD20002 Error X'xxxx' locating member ENVCNTL | TAPECNTL on SYSPARM Explanation: Hexadecimal error code 'xxxx' has been received attempting to locate the ENVCNTL or TAPECNTL member on the DB2 Manager parameter library. Control region initialization processing is aborted.
OTD20007 ENVCNTL | TAPECNTL parameters successfully processed Explanation: Validation of parameters in the ENVCNTL or TAPECNTL member of the DB2 Manager parameter library has completed successfully. Control region initialization processing continues. Action: None. This is an informational message. OTD20008 ODCT GETMAIN failure x'xxxx' Explanation: A request for virtual storage in subpool 241 of the MVS ECSA has been denied by the operating system with return code 'xx'.
If no other abnormal message is present, or the cause of the error is not apparent from any displayed message, contact your DB2 Manager product support representative. OTD20012 Return code X'xx' retrieving | creating | deleting Name/Token pair Explanation: An error has occurred retrieving, creating or deleting an OS/390 name/token pair. ‘xx’ gives the hexadecimal reason code received from the retrieve request. Execution of the utility is terminated with condition code 12.
Explanation: All sub-tasks of the type identified in the message have been successfully initialized during start-up of the DB2 Manager control region. ‘nnn’ gives the number of sub-tasks initialized. Action: None. This is an informational message. OTD20016 OTDBP300 is not in Link Pack Area Explanation: The DB2 Manager row edit routine OTDBP300 was not found in the FLPA or MLPA during control region initialization processing. The control region is terminated.
OTD20019 Error locating DB2 Manager ASCB | Jobname Explanation: An error has been detected attempting to locate the ASCB for the DB2 Manager control region, or retrieving the started task name assigned to the control region. Action: This indicates an internal error in DB2 Manager processing. Report the error to your local DB2 Manager product support representative. OTD20020 Lifecycle Director V1.
Action: A system abend has been trapped during processing of an operator request. If possible, DB2 Manager will recover from the abend. Operator requests may continue to be entered as normal. If it is not possible for DB2 Manager to recover from the abend, control region processing will be terminated abnormally. The problem should be reported to your DB2 Manager product support representative.
Explanation: ‘COMMAND=MODIFY’ is set in the Archive Manager/OAM TAPECNTL parameter library member, but an MVS command other than ‘MODIFY’ has been issued to the DB2 Manager control region. Action: Re-enter the DB2 Manager command using the standard MVS MODIFY command structure. Refer to “DB2 Manager operator interface” on page 50 for more information on entering DB2 Manager control region commands.
Explanation: An invalid operator command has been entered in response to the DB2 Manager OTD20000 message or via MODIFY command. Action: Re-enter the correct operator command in response to the OTD20000 message or via MODIFY command. OTD20051 Invalid Set operand(s) - request ignored Explanation: An invalid operand has been entered with the SET operator command. Action: Ensure that the SET command is specified correctly and re-enter the command.
OTD20055 Missing/invalid operand - request rejected Explanation: A mandatory operand is missing from an DB2 Manager operator command. Action: Re-enter the command with the correct syntax. Refer to “DB2 Manager operator interface” on page 50 for a description of operator command formats. OTD20056 Errors altering configuration – check system status Explanation: Errors have been detected attempting to alter the current DB2 Manager configuration using the operator SET command.
OTD20060 Task tnnn has been shutdown successfully Explanation: A request to purge the identified sub-task has been completed successfully. ‘t’ identifies the sub-task type (‘D’ – disk reader; ‘H’ – housekeeping; ‘S’ – scheduler; ‘T’ – tape reader; ‘W’ – writer) and ‘nnn’ gives the sub-task number. Action: None. This is an informational message. OTD20061 Invalid Display operand(s) – request ignored Explanation: An invalid operand has been entered with the DISPLAY operator command.
WAIT – the task is currently waiting for work WTSH – a shutdown request has been queued for the task BUSY – the task is currently processing requests BYSH – the task is currently processing requests, and will terminate when all requests have been processed TERM – the task has terminated ’bbb’ gives the number of requests currently queued for the task. For busy reader and writer tasks, ‘cccc’ gives the identifier of the database being processed by the subtask.
OTD20071 Invalid Purge operand(s) – request ignored Explanation: An invalid operand has been entered with the PURGE operator command. Action: Ensure that the PURGE command is specified correctly and re-enter the command. Refer to page 55 for details of the operator PURGE command.
OTD20083 Task tnnn has not been purged – request ignored Explanation: A FORCE request has been entered for task 'tnnn', where ‘t’ identifies the sub-task type (‘D’ – disk reader; ‘H’ – housekeeping; ‘S’ – scheduler; ‘T’ – tape reader; ‘W’ – writer) and ‘nnn’ gives the sub-task number, but no prior PURGE request has been entered. A PURGE request must already have been entered for a task before a FORCE request is accepted. The request is ignored. Action: Enter a PURGE request for the task.
If no apparent cause of the error can be identified, contact your DB2 Manager product support representative. The ECSA storage used for the DB2 Manager communications table in this invocation of the control region will be unavailable for allocation until after the next IPL of the system. Approximately 200 kbytes of storage are used for the communications table in extended CSA storage.
OTD22002 Scheduler initialization error: insufficient storage available for workareas Explanation: A request for virtual storage in the DB2 Manager control region has been rejected by the operating system. Control region initialization processing is aborted. Action: Allocate more virtual storage to the control region, by increasing the value of the SIZE parameter in the DB2 Manager procedure. Restart the control region.
OTD22006 Scheduler terminating because of recursive abends T=Snnn Explanation: An abend condition has been detected by a scheduler task, when attempting to recover from an earlier abend condition. ‘nnn’ identifies the scheduler task receiving the error. The scheduler task will terminate automatically and the current value of the MAXSCHED initialization parameter will be reduced by 1. Action: Examine the original abend condition, and take any corrective action required.
Explanation: An error has been received by scheduler task ‘nnn’ opening or reading the primary index dataset of Archive Manager database ‘xxxx’. ‘aa’ and ‘bb’ give the hexadecimal return and reason codes from the VSAM request. The migrated row access request being processed by the task will be rejected. Action: Refer to IBM VSAM macro documentation for an explanation of the return and reason codes displayed in the message.
OTD25003 Unable to get exclusive access to ODRE resource Explanation: A tape reader task has been unable to gain exclusive access to the scheduler request queue within 1 minute. Processing of the request continues, but request queue integrity in the DB2 Manager control region may have been compromised. Action: Examine the system log for other abnormal messages issued by the DB2 Manager control region.
Explanation: Tape reader task number ‘nnn’ has terminated processing in response to an operator command, or following an unrecoverable error condition. Action: None. This is an informational message. OTD25011 Return code xx Supp codes X'yyyyzzzz' received opening | reading | closing d/b dddd, T=Tnnn Explanation: An error has been received by tape reader task ‘nnn’ accessing the Archive Manager database with identifier ‘dddd’, for the type of processing identified in the message.
Action: Refer to IBM documentation for an explanation of the system abend code displayed in the message. If no apparent cause for the problem can be identifier, report the error to your StorageTek customer support representative. OTD254xx – control region disk reader messages Messages from DB2 Manager control region disk reader tasks are written to the system log.
Explanation: A request by a disk reader task for virtual storage in the DB2 Manager control region has been rejected by the operating system. Disk reader task initialization processing is aborted. Action: Allocate more virtual storage to the control region, by increasing the value of the SIZE parameter in the DB2 Manager procedure. Restart the control region. OTD25405 Disk rdr task nnn initialization failed Explanation: Initialization of disk reader sub-task ‘nnn’ has failed.
Action: Refer to the Archive Manager User Manual for an explanation of the return and supplementary codes displayed in the message. Take the appropriate corrective action and re-submit the request. OTD25412 Unrecoverable error condition - disk reader task nnn terminating Explanation: An error condition has been encountered during processing of a request by disk reader task ‘nnn’, and the task is unable to recover. The request will be terminated with an error condition and the reader task will terminate.
Action: Examine the system log for other abnormal messages issued by the DB2 Manager control region. If there is no apparent reason for the failure, contact your local DB2 Manager product support representative. OTD26003 Unable to get exclusive access to ODRE resource Explanation: A tape writer task has been unable to gain exclusive access to the scheduler request queue within 1 minute.
OTD26007 Tape wtr task nnn abend Sxxx intercepted Explanation: A system abend has been intercepted during operation of tape writer task ‘nnn’. The system abend code is 'xxx'. Tape writer processing will continue. Action: A system abend has been trapped during processing of a migrated row storage request. If possible, DB2 Manager will recover from the abend. If it is not possible for DB2 Manager to recover from the abend, the tape writer task will be terminated abnormally.
OTD26013 Error xx received writing SMF record Explanation: An error has been detected by a tape writer task writing a record to the SMF dataset. ‘xx’ gives the return code received from the SMFWTM macro. Tape writer task processing will continue normally. Action: Refer to IBM documentation for an explanation of the return code displayed in the message. Take the appropriate corrective action to resolve the problem.
Explanation: A request by a housekeeping task for virtual storage in the DB2 Manager control region has been rejected by the operating system. Housekeeping task initialization processing is aborted. Action: Allocate more virtual storage to the control region, by increasing the value of the SIZE parameter in the DB2 Manager procedure. Restart the control region.
communicated back to the calling program via generation of an SQL –652 error. The two bytes at character positions 6 and 7 in field SQLERRD in the SQL communication area (SQLCA) at the time of the error will contain a reason code giving additional information about the error condition. Messages giving additional error information may also be displayed in the system log by the DB2 Manager control region. This section lists reason codes set by DB2 Manager in the SQLCA.
Reason code (hex) Explanation Action: 0A00 A request has been unable to obtain exclusive access to the DB2 Manager control region scheduler lock within the time interval set in the READTIMEOUT or WRITETIMEOUT initialization parameter (depending on type of request). Action: 0B00 This is a normal condition when running an DB2 Manager utility program, and will be handled by the program. This error should not occur when executing any other type of program.
Reason code (hex) Explanation processing. Stop and restart the control region to try to clear the error condition. If this does not work, report the problem to your local DB2 Manager support representative. 10xx An error condition has been received by the DB2 Manager control region during processing of the request. The second byte of the reason code contains a two-digit hexadecimal value describing the error. Refer to page 169 for a description of possible control region reason codes.
Return code (hex value in brackets) 21 (15) Explanation No free tape reader task available to perform migrated row retrieval request, or task processing tape volume containing migrated row is currently at its maximum request level (as set by the MAXQLEN initialization parameter).
Return code (hex value in brackets) xx Explanation Any other return code issued by the control region indicates that an error has been received from an Archive Manager call. A message will be issued by the control region giving details of the call and the return and reason codes received from Archive Manager. Refer to the Archive Manager User Manual for a description of this error condition.
Appendices Appendix A: Sample JCL members Appendix A gives listings of members on the distributed DB2 Manager sample JCL library. LCDDB2 Member LCDDB2 is a sample procedure for execution of the DB2 Manager control region started task. //* //* Lifecycle Director //* DB2 Manager started task procedure. //* //* Change history: //* 19-Mar-03 GW V1.1 CREATED. //* 02-Apr-04 GW V1.1 Re-branded. //* //* Edit each of the lines marked "<===" to update: //* //* 1. Name of installed DB2 Manager load library //* 2.
OTDBDEF Member OTDBDEF creates the DB2 Manager system database. //OTDBDEF JOB //* //* DB2 Manager system database creation job. //* //* Change history: //* GW 19-Mar-03 V1.1 created //* GW 02-Apr-04 V1.1 re-branded //* //* This job creates the database manager system database. It //* includes steps to allocate files, define the database and //* grant authorities for database access.
CYLINDERS(1 1) UNIQUE ) DATA (NAME(DSN610.DSNDBD.LCDDB2.REGIX1.I0001.A001)) <=== DEFINE CLUSTER (NAME(DSN610.DSNDBC.LCDDB2.REGIX2.I0001.A001) - <=== LINEAR SHAREOPTIONS(3 3) VOLUMES(vvvvvv) - <=== CYLINDERS(1 1) UNIQUE ) DATA (NAME(DSN610.DSNDBD.LCDDB2.REGIX2.I0001.A001)) <=== //* //STEP03 EXEC PGM=IKJEFT01,DYNAMNBR=20,COND=(4,LT,STEP02) //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * DSN SYSTEM(DB2) <=== RUN PROGRAM(DSNTIAD) PLAN(DSNTIAnn) <=== LIB('DB2.runtime.
MIXOPSEQ SMALLINT VERSION VARCHAR(64) COLLID CHAR(18) ACCESS_DEGREE SMALLINT, ACCESS_PGROUP_ID SMALLINT, JOIN_DEGREE SMALLINT, JOIN_PGROUP_ID SMALLINT, SORTC_PGROUP_ID SMALLINT, SORTN_PGROUP_ID SMALLINT, PARALLELISM_MODE CHAR(1), MERGE_JOIN_COLS SMALLINT, CORRELATION_NAME CHAR(18), PAGE_RANGE CHAR(1) JOIN_TYPE CHAR(1) GROUP_MEMBER CHAR(8) IBM_SERVICE_DATA VARCHAR(254) WHEN_OPTIMIZE CHAR(1) QBLOCK_TYPE CHAR(6) BIND_TIME TIMESTAMP OPTHINT CHAR(8) HINT_USED CHAR(8) PRIMARY_ACCESSTYPE CHAR(1) ) IN LCDDB2.
OTDBPKG Member OTDBPKG creates the DB2 Manager DB2 application packages. //OTDBPKG JOB //* //* DB2 Manager DB2 package creation job. //* //* Change history: //* GW 19-Mar-03 V1.1 created //* GW 02-Apr-04 V1.1 re-branded //* GW 30-Apr-04 V1.1 OTDBL130 added //* //* This job creates the DB2 application packages //* required for DB2 Manager implementation. //* //* Amend the job as follows before submitting: //* //* 1.
KEEPDYNAMIC(YES) /* BIND PACKAGE(OTDBL130) MEMBER(OTDBL130) ACTION(REPLACE) VALIDATE(BIND) ISOLATION(CS) FLAG(E) SQLERROR(CONTINUE) RELEASE(COMMIT) EXPLAIN(NO) KEEPDYNAMIC(YES) - BIND PACKAGE(OTDBL140) MEMBER(OTDBL140) ACTION(REPLACE) VALIDATE(BIND) ISOLATION(CS) FLAG(E) SQLERROR(CONTINUE) RELEASE(COMMIT) EXPLAIN(NO) KEEPDYNAMIC(YES) - BIND PACKAGE(OTDBL170) MEMBER(OTDBL170) ACTION(REPLACE) VALIDATE(BIND) ISOLATION(CS) FLAG(E) SQLERROR(CONTINUE) RELEASE(COMMIT) EXPLAIN(NO) KEEPDYNAMIC(YES) - OTDBPLA
//* //* 2. Change the name of the DB2 subsystem (DB2) in //* the DSN statements to match the subsystem name //* in use on the host system. //* //* 3. Replace the character string 'pppppppp' with //* the name of the DB2 plan to be generated. //* //* 4. Change the plan name in the RUN statement (DSNTIAnn) //* to match the version of DB2 in use on the host //* system. //* //BIND EXEC PGM=IKJEFT01,DYNAMNBR=20 //STEPLIB DD DSN=DB2.runtime.
Index A Access Method Services, 31 allocation recovery, 74 AMS, 31 APF-authorization, 22, 46 archive date, 14 archive indicator, 10 Archive Manager, 7, 8, 13, 28 database, 13, 28, 46, 82 database administration, 28 database backup, 91 database definition, 118 database identifier, 14, 54, 55, 97, 103, 108, 113 database maintenance, 24, 50, 117 database maintenance utility, 117 database recovery, 93 database storage level, 14, 54, 55 disk copy processing, 9 journal dataset, 31, 91 object, 10, 13, 37, 91 objec
F FLPA, 23 FORCE, 56 force purge, 56 MLPA, 23 MODIFY, 43, 46, 51, 64 N new tape volume, 86 H HLQ, 28 Host Software Component, 25, 72 housekeeping failure, 117 housekeeping processing, 13 HSC, 25 I IEF238D, 25, 74, 75 IEF247I, 25 image copy, 15 implementation, 14, 19 INDEXONLY, 98, 104 installation verification, 33 L large objects, 78 LCDDB2, 175 LCDDB2 database, 26 LCDDB2.PLAN_TABLE, 26 LCDDB2.
R reader task, 72 READTIMEOUT, 37, 53, 59, 60, 62, 63, 126, 171, 173 reason codes, 170 record offset, 14 recovery status, 93 recycle threshold, 118 re-migration selection criteria, 95, 99, 102 utility failure, 101 REPLY, 46, 51, 63 request queue, 41 request queue length, 53, 72 request status, 53 resource unavailable, 42, 56, 71, 73, 74, 75, 82 response time, 74 restart processing, 85 RETAINTAPE, 42, 49, 53, 59, 60, 61, 154 retention period, 29 row deletion, 12 row migration, 9, 77 row update, 12 ROWID, 78
tape volume recycling, 117 TAPECNTL, 22, 38 TAPEWAIT, 39, 41, 42, 43, 49, 53, 59, 60, 62, 71, 73, 74, 75, 173 timestamps, 66 TSO/ISPF, 28 database housekeeping, 13, 95, 101, 112, 140 re-migration, 13, 95, 101, 128, 132 table analysis, 13, 95, 107, 136 table migration, 40, 77, 82, 121 V U unique key, 78, 87, 99, 105, 110, 115 unit name, 30 updated row, 50 user identification, 22 user SVC, 28 utilities view, 80 VIO dataset, 86, 98 W WRITETIMEOUT, 38, 53, 59, 60, 62, 88, 171, 173
Reader’s Comment Form ∎ Contact Us Submit your questions, comments, and suggestions to StorageTek’s Global Learning Solutions. We appreciate your correspondence and are committed to responding to you. Publication Information Publication Name: Publication Part Number: Questions and Comments: Note: Staples can cause problems with automated mail sorting equipment. Please use pressure sensitive or other gummed tape to seal this form.
TO COMPLY WITH POSTAL REGULATIONS, FOLD EXACTLY ON DOTTED LINES AND TAPE ------------------------------------------------------------------------------------------------------------------------------------------TO COMPLY WITH POSTAL REGULMATIONS, FOLD EXACTLY ON DOTTED LINES AND TAPE (DO NOT BUSINESS REPLY CARD FIRST CLASS PERMIT NO. 2 LOUISVILLE, CO U.S.A.
StorageTek Proprietary
NEED MORE INFORMATION? www.storagetek.com ABOUT STORAGETEK Storage Technology Corporation (NYSE: STK) is a $2 billion global company that enables businesses, through its information lifecycle management strategy, to align the cost of storage with the value of information. The company’s innovative storage solutions manage the complexity and growth of information, lower costs, improve efficiency and protect investments. For more information, visit www.storagetek.com, or call 1.800.275.4785 or 01.303.673.
