i413678
Currently Banned
Active User
Joined: 19 Feb 2005
Posts: 112
Location: chennai
|
|
|
|
SECONDARY INDEX UTILITY
General Information
ii
SECONDARY INDEX UTILITY
General Information
SUIPMG111797
November 17, 1997
?
This document is published by the BMC Software, Inc., Information Development and Design Department.
Copyright ? 1991 ? 1997 BMC Software, Inc. All rights reserved.
BMC Software, the BMC Software logo, and all other product or service names are registered trademarks or trademarks of
BMC Software, Inc., in the USA and in other select countries. ? and ? indicate USA registration or USA trademark.
*IBM and DB2 are registered trademarks of International Business Machines Corp. Other logos and product/trade names
are registered trademarks or trademarks of their respective companies.
All third party logos and product/trade names are registered trademarks or trademarks of their respective companies.
RESTRICTED RIGHTS LEGEND
Use, distribution, or disclosure by the Government is subject to restrictions set forth in subparagraph (c)(1)(ii)
of Rights in Technical Data and Computer Software clause in DFARS 252.227-7013.
BMC Software, Inc.
2101 CityWest Blvd.
Houston, TX 77042-2827
USA
Contacting BMC Software
From anywhere in the world, you can contact BMC Software on the World Wide Web at www.bmc.com.
USA and Canada
In the USA and Canada, you can contact BMC Software by telephone or fax:
Telephone (800) 537-1813 (Product Support)
(713) 918-8800 (Houston metropolitan area)
Fax Call Product Support for the fax number of your BMC Software product support
representative.
International
Outside the USA and Canada, you can contact a BMC Software international support center:
You can also call the BMC Software office in your country, if applicable. For a complete list of all BMC Software
international offices and subsidiaries, see the BMC Software home page at www.bmc.com.
Asia/Pacific
BMC Software Pte Ltd.
One Temasek Avenue
#18-02 Millenia Tower
Singapore 039192
telephone: (65) 338 9400
fax: (65) 338 9580
Africa, Europe, Latin America, and the Middle East
BMC Software, Inc.
2101 CityWest Blvd.
Houston, TX 77042-2827
USA
telephone: (713) 918-8800
fax: (713) 918-1303
Contents iii
iv
Contents
SECONDARY INDEX UTILITY . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Creating and Maintaining Secondary Indexes . . . . . . . . . . . . . . . . . . . . . 1
Savings in Time and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Processing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Information on Index Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
About BMC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Maintenance and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
BMC Software?s 30-Day-Plus Free Trial . . . . . . . . . . . . . . . . . . . . . . . . 22
iv SECONDARY INDEX UTILITY General Information
Preface v
vi
Preface
This book provides general information about the SECONDARY INDEX
UTILITY product from BMC Software, Inc. It provides an overview of the
product and is for managers of installations running IMS, IMS database
administrators, and others who are concerned with improving IMS data
availability and conserving data management resources. Its purpose is to
help you determine whether the product can meet your data management
goals. It explains how the product can provide savings in time and resources
and summarizes the product?s features and benefits. It assumes that you are
somewhat familiar with IMS terms and concepts.
Conventions
The term IMS refers to all versions and releases of IMS/VS and IMS/ESA.
The specific product name, version, and release numbers are noted only
when this information is significant.
Other Publications
The following publications belong to the SECONDARY INDEX UTILITY
documentation set:
? SECONDARY INDEX UTILITY Reference Manual
? Database Supplemental Utilities Reference Manual
? Database Utilities General Information
? Database Utilities Installation Guide
? Database Utilities Messages Manual
vi SECONDARY INDEX UTILITY General Information
SECONDARY INDEX UTILITY 1
20
SECONDARY INDEX UTILITY
SECONDARY INDEX UTILITY performs all of the functions necessary to
either create a new secondary index for an existing database or to maintain
or rebuild an existing secondary index. It can also rebuild a primary index
for a HIDAM database.
SECONDARY INDEX UTILITY simplifies the creation and maintenance
of secondary indexes. When creating a new secondary index or rebuilding an
existing one, using SECONDARY INDEX UTILITY reduces the rather
complex six-step IMS/VS procedures into a simple one-step procedure. It
functionally replaces the following IMS utilities required to create, maintain,
and rebuild a secondary index:
? IMS Prereorganization
? HD Reorganization Unload/ Reload
? IMS Prefix Resolution
? HISAM Unload/ Reload
SECONDARY INDEX UTILITY reduces the time required to create and
maintain secondary indexes. It reduces both the personnel time required to
create and test JCL and the CPU and elapsed time required to build a
secondary index.
Creating and Maintaining Secondary Indexes
A database must be reorganized periodically to improve operating efficiency
and to implement changes. Physical reorganization involves placing each
root segment together with its dependent segments into one block on the
disk pack, or into adjacent blocks if they do not fit into a single block, so
that fewer I/O operations are needed to retrieve the root and its dependents.
Logical relationship pointers between databases must also be resolved and
updated, and any secondary indexes for the reorganized database rebuilt.
2 SECONDARY INDEX UTILITY General Information
Creating and Maintaining Secondary Indexes
As the size and complexity of the database increase, reorganization
processing time increases. Since the database must be offline during
reorganization, a sufficiently large window of down time must be found in
the database operating schedule. You may not be able to find this window of
down time, or you may not be able to take advantage of the capacity of IMS
for logical relationships because of the additional reorganization
requirements.
SECONDARY INDEX UTILITY and the other BMC Software IMS
Database Utilities approach the reorganization task with the objective of
reducing both elapsed and CPU time. The following is a description of the
typical way you would run the utilities when logical relationships and
secondary indexes have been defined.
Figure 1 illustrates the reorganization of Database B, which is logically
related to Database C and has secondary indexes.
The UNLOAD PLUS? product unloads Database B and writes the HD
Unload data set. It also scans Database C for the logical relationship
information.
The LOADPLUS? product reloads Database B from the HD Unload data set
and generates two work file (WF1) data sets, one containing logical
relationship information and the other secondary index information.
The WF1 data set containing secondary index information is processed by
SECONDARY INDEX UTILITY, which sorts the records and writes them
to the secondary index database(s).
The PREFIX RESOLUTION PLUS product sorts and processes the WF1
data sets and then updates the affected pointers in both Databases B and C.
The IMAGE COPY PLUS (ICP?) product takes an image copy of both
databases before and after the reorganization, and the POINTER CHECKER
PLUS product validates them.
Savings in Time and Resources
SECONDARY INDEX UTILITY 3
Figure 1 Reorganization with Logical Relationships and Secondary Indexes
Savings in Time and Resources
SECONDARY INDEX UTILITY improves data availability and resources.
It can create a secondary index up to ten times faster than the IMS
Reorganization Unload/Reload utilities. Because it can create or rebuild a
secondary index faster, the indexed database is offline for a shorter period of
time.
HD Unload Data Set
IMAGE
COPY PLUS
POINTER
CHECKER
PLUS
Database B
(disorganized)
Database B
(reorganized)
UNLOAD
PLUS
IMAGE
COPY PLUS
POINTER
CHECKER
PLUS
WF1
Database C
(related)
Database C
(updated)
UNLOAD
PLUS
Image Copy Data Sets
Image Copy Data Sets
WF1
Secondary
Indexes
Secondary
Indexes
WF1
PREFIX
RESOLUTION
PLUS
LOADPLUS
SECONDARY
INDEX UTILITY
4 SECONDARY INDEX UTILITY General Information
Savings in Time and Resources
To increase the speed of the unload and scan processes, SECONDARY
INDEX UTILITY makes more efficient use of VSAM I/O techniques by
passing short, fixed length records to the sort utility. This substantially
reduces the amount of space needed for the records. By doing more work in
one step, SECONDARY INDEX UTILITY avoids intermediate tape file
I/Os although the work can be divided into multiple steps to achieve step
restartability in large jobs.
Most installations take frequent, scheduled image copies of databases, even
though they seldom need to recover those databases. Since SECONDARY
INDEX UTILITY can rebuild lost or damaged indexes using only the
indexed database as input, image copies of indexes are no longer needed for
recovery. The overhead and expense of these image copies can be avoided
without compromising data recoverability.
SECONDARY INDEX UTILITY reduces the elapsed time and CPU time
required to build a secondary index. A database index can be rebuilt without
a complete reorganization, and SECONDARY INDEX UTILITY often can
be used for recreating damaged database indexes. Performance comparisons
show that SECONDARY INDEX UTILITY consistently makes more
efficient use of time and resources.
Performance Comparisons of Elapsed Time
Because the database must be offline when creating or maintaining indexes,
this reduction in elapsed time is important. It reduces the period of
unavailability and increases the production time for your database.
In benchmark tests using HISAM databases, elapsed time usage for
SECONDARY INDEX UTILITY was compared to the IMS HD
Reorganization Unload/Reload utilities, IMS Prefix Resolution utility, and
HISAM Unload/Reload utilities for creating a new secondary index for an
existing database.
Elapsed Time with a Database Reorganization
Figure 2 illustrates the difference in elapsed time between the IBM* utilities
and the BMC Software utilities when secondary indexes are rebuilt during a
database reorganization.
The IMS utilities used over 20 hours or 1,238 minutes of elapsed time while
the BMC Software utilities used only 3 hours or 181 minutes. This is a
savings of 86% in elapsed time for a reorganization.
Savings in Time and Resources
SECONDARY INDEX UTILITY 5
Figure 2 Elapsed Time with a Database Reorganization
Elapsed Time without a Database Reorganization
Using the IMS utilities, it takes a significant amount of time to load,
reorganize, or restore secondary indexes for databases. SECONDARY
INDEX UTILITY provides a more efficient way of creating and maintaining
secondary indexes: it allows you to recreate a secondary index without
having to completely reorganize your database.
Figure 3 shows the savings impact on elapsed time when creating a new
secondary index without a database reorganization. The IMS/VS utility took
530 minutes to create a new secondary index while SECONDARY INDEX
UTILITY took 175 minutes, a savings of 67%.
0
200
400
600
800
1000
1200
1400
0
200
400
600
800
1000
1200
1400
Elapsed Time
(minutes)
IBM Utilities
BMC Utilities
6 SECONDARY INDEX UTILITY General Information
Savings in Time and Resources
Figure 3 Elapsed Time without a Database Reorganization
Performance Comparisons of CPU Time
SECONDARY INDEX UTILITY also offers a great savings in processing
or CPU time. Reducing CPU time reduces operating costs and resource
usage.
Figure 4 shows the savings impact on CPU time when doing a complete
reorganization and creating a primary index. The IMS utilities used 156
minutes of processing time compared to the 43 minutes used by the BMC
Software utilities, a savings of 72%.
0
100
200
300
400
500
600
0
100
200
300
400
500
600
Elapsed Time
(minutes)
IMS/VS Utility
SECONDARY INDEX UTILITY
Features and Benefits
SECONDARY INDEX UTILITY 7
Figure 4 CPU Time with a Database Reorganization
Features and Benefits
SECONDARY INDEX UTILITY decreases database reorganization time,
CPU usage, and application program run time. SECONDARY INDEX
UTILITY is compatible with IMS and with other BMC Software products.
Simplicity and Flexibility
SECONDARY INDEX UTILITY simplifies the creation and maintenance
of secondary indexes. When creating a new secondary index or rebuilding an
existing one, using SECONDARY INDEX UTILITY reduces the rather
complex six-step IMS procedures into a simple one-step procedure (see
Figure 5).
Versatility
SECONDARY INDEX UTILITY provides versatility. In addition to its
usual functions, it can
? build multiple secondary indexes for one or more databases in the same
job step
? create empty secondary indexes to be used with empty databases
0
20
40
60
80
100
120
140
160
0
20
40
60
80
100
120
140
160
CPU Time
(minutes)
IBM Utilities
BMC Utilities
8 SECONDARY INDEX UTILITY General Information
Features and Benefits
? rebuild primary indexes for HIDAM databases
? split a DFSURWF1 data set into two or more data sets, containing the
secondary index records and the logical relationship records, which can
significantly enhance the prefix resolution process.
? eliminate the need to image copy the secondary index databases because
SECONDARY INDEX UTILITY can rebuild lost or damaged indexes
using only the indexed databases as input
? build indexes for databases that use IMS/ESA Partition DB. Databases
that use IMS/ESA Partition DB share indexes across all partitions. You
must build indexes for all partitions. WF1 records created during a
database load or reload are accepted. If you perform a database scan to
build indexes, the UNLOAD PLUS program ULPXSCAN is required
for databases that use IMS/ESA Partition DB; SIUXSCAN is not
supported.
Input and Output Options
SECONDARY INDEX UTILITY can accept output from the following
utilities:
? IMS HD Reorganization Reload utility (DFSURWF1)
? IMS Prefix Resolution utility (DFSURIDX)
? IMS HISAM Unload utility (DFSUINxx)
? BMC Software?s LOADPLUS and LOADPLUS?/EP (DFSURWF1)
? BMC Software?s UNLOAD PLUS (DFSURWF1)
? BMC Software?s PREFIX RESOLUTION PLUS (DFSURIDX)
It generates input to the following utilities:
? IMS Prefix Resolution utility
? IMS HISAM Reload utility
? BMC Software?s PREFIX RESOLUTION PLUS
This versatility of input and output frees you to use SECONDARY INDEX
UTILITY at your convenience instead of being restricted by the needs of the
other utilities. The way in which SECONDARY INDEX UTILITY
functions with the IMS utilities is illustrated in Figure 5.
Processing Functions
SECONDARY INDEX UTILITY 9
Figure 5 SECONDARY INDEX UTILITY and the IMS Utilities
Processing Functions
SECONDARY INDEX UTILITY consists of several processing functions:
the Index Scan function, the Index Load function, the BUILDALL function,
and the Work File 1(WF1) Split function.
Indexed
Database
Control
Statements
Control
Statements
DFSURGU1
Pre-Reorg CDS
Index Scan HD Reorg
Unload
DFSURWF1
SECONDARY
INDEX
UTILITY
HD Reorg
Reload
DFSURIDX
Index Load Prefix
Resolution
Index Work
SORTWORK
DFSUIN01
HISAM
Unload
Secondary
Index
Database
HISAM
Reload
Indexed
Database
SECONDARY
INDEX UTILITY IMS UTILITIES
10 SECONDARY INDEX UTILITY General Information
Processing Functions
The Index Scan Function
The Index Scan function scans an existing database, extracting the necessary
secondary index data. You would use it only when creating a new secondary
index for an existing database or replacing a damaged secondary index.
SECONDARY INDEX UTILITY can use IMS or BMC Software?s
UNLOAD PLUS to scan the indexed database. You can control which
facility it uses to perform the scan by specifying the program on the XSCAN
control statement.
If you have UNLOAD PLUS installed, SECONDARY INDEX UTILITY
can use it to perform the Index Scan function. Using UNLOAD PLUS
instead of IMS to read the indexed database significantly reduces the time
required to extract the index data.
Figure 6 is an illustration of the Index Scan function general systems flow.
Figure 6 The Index Scan Function General Systems Flow
Indexed
Database
IMS Lib
DFSURWF1
Control
Statements
Control
Statements
Control
Statements
DBDLIB
Control
Statements
PLUSLIST
SYSPRINT
PLUSLIST
SYSPRINT
xxxxxxxx
Mutually Exclusive
To Index Load
or Prefix Resolution
To Index Load
Processing Functions
SECONDARY INDEX UTILITY 11
The Index Load Function
The Index Load function is used primarily to load a primary or secondary
index database. The input to the Index Load function is a work file created
by a Load/Reload program or by the Index Scan. The Index Scan and Index
Load functions may be performed in the same job step or in separate job
steps.
Figure 7 shows the general system flow for the Index Load function.
Figure 7 The Index Load Function General System Flow
Secondary
Index
Database
SORT
DFSURWF1
SECONDARY
INDEX UTILITY
(SIUXLOAD)
PLUSLIST
SYSPRINT
DFSURIDX
From Reorg, Reload,
User Load, SIUXSCAN
From Prefix
Resolution
DFSUINnn xxxxxxxx
From HISAM
Unload
From
INDXSCAN
DBDLIB
SYSOUT
SORTWORK
01
DFSURIDX DFSUINnn xxxxxxxx
dddddddd
12 SECONDARY INDEX UTILITY General Information
Processing Functions
The BUILDALL Function
The BUILDALL function loads all secondary index databases for a primary
database. The BUILDALL command can replace the individual control
statements necessary to scan and load the secondary indexes. Therefore, it is
easier to create and maintain JCL with BUILDALL. When a new secondary
index is implemented for the primary database, you just supply the DD
statement defining the new secondary index; you do not need to modify the
SECONDARY INDEX UTILITY control statements.
The BUILDALL function can scan the primary database, or it can use the
input data set you specify with the INDD parameter. No XFLD commands
are needed before the BUILDALL command (as they are for the XSCN and
XLOD commands).
Figure 8 illustrates the general system flow for the BUILDALL function
when the input is a work file containing secondary index records.
Figure 8 The BUILDALL Function General System Flow
Secondary
Index
Database(s)
SORT
DFSURWF1
SECONDARY
INDEX UTILITY
(BUILDALL)
PLUSLIST
SYSPRINT
DFSURIDX
From Reorg, Reload,
User Load, SIUXSCAN
From Prefix
Resolution
DBDLIB
SYSOUT
or
If input is DFSURWF1
SORTWORK 01
SORTWORK 02
SORTWORK 03
Processing Functions
SECONDARY INDEX UTILITY 13
The WF1 Split Function
The WF1 Split function splits a DFSURWF1 data set into two or more data
sets, one or more containing the secondary index records and one containing
the logical relationship records. The most common usage of the WF1 Split
function is to split a DFSURWF1 data set (created during IMS HD
Reorganization Reload or an initial database load) that contains both logical
relationship and secondary index records.
The output data set(s) containing the secondary index records are passed to
the SECONDARY INDEX UTILITY Index Load function. The data set
containing the logical relationship records are passed to the IMS Prefix
Resolution utility or BMC Software?s PREFIX RESOLUTION PLUS.
Figure 8 illustrates the general system flow for the WF1 Split function.
Figure 9 The WF1 Split Function General System Flow
SECONDARY
INDEX UTILITY
(SIUSPLIT)
WF1
SECONDARY
INDEX UTILITY
(BMCSIU)
PLUSLIST
SYSPRINT
WF1
Secondary Index
Records
Logical
Relationship Record
WF1
PLUSLIST
SYSPRINT
DBDLIB
Control
Statements
(DD1) (DD2)
14 SECONDARY INDEX UTILITY General Information
Information on Index Availability
Information on Index Availability
SECONDARY INDEX UTILITY generates several comprehensive reports
for use in creating and maintaining secondary indexes.The reports provide
information about database index availability and performance.
They include statistics on the output of the Index Scan and Index Load
functions, the results of each function, and the content of both the logical
relationships and secondary index output files.The reports also provide a
listing of the frequency distribution of record types found in the WF1 input
data set, as well as the size of each record type.
The following reports can be generated:
? SYSPRINT Output from Index Scan and Index Load
? PLUSLIST Output from Index Scan and Index Load
? SYSPRINT Output from WF1 Split
Sample reports are included in this section to illustrate the type of reports
produced and the information you can obtain. You can view these reports
online or get a batch listing. SECONDARY INDEX UTILITY will retain
the reports in a PDX for online viewing so that you can analyze past
statistics without maintaining a stack of listings.
SYSPRINT Output from Index Scan and Index Load Report
Figure 10 lists the control statements and shows the output of the Index Scan
and Index Load functions. The Listing part lists the input control statements.
The Definition part shows the output of the Index Scan function. The Output
Results part shows the output of the Index Load function.
Information on Index Availability
SECONDARY INDEX UTILITY 15
LISTING OF ?PLUSIN ? CONTROL STATEMENTS:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8
BUILDALL DBD(CUSTNDX1) DBRC(N) ICNEEDED(OFF)
******************************************************************************
*** S I U ********** B M C S O F T W A R E, I N C. ********** S I U ***
******************************************************************************
S E C O N D A R Y I N D E X U T I L I T Y
IMS/VS 5.1.0 DATE=96.002 1/2/96 TIME=16:29
+--------------------------+
| GLOBAL OPTIONS IN EFFECT |
+--------------------------+
IMS ID USED............................. BMC1
GLOBAL PARAMETER BLOCK USED............. SIU@BMC1
PDX
DATASET NAME..........................
STATISTIC SET LIMIT................... 10
IF PDX UNAVAILABLE
ACTION............................. OKAY
RETURN CODE........................ 4
PRINT INDEX DEFINITIONS ON.............. SYSPRINT AND PLUSLIST
+-----------------------------------------------------+
| BUILDALL JOB=BMCSIU/SIUSTEP 1/2/96 16:29:32 |
+-----------------------------------------------------+
SCAN/LOAD OPTIONS IN EFFECT
MONITORING
FREQUENCY............................. 0
MESSAGE DESCRIPTOR CODES.............. 7
MESSAGE ROUTE CODES................... 2,7
TSO USER ID...........................
SCAN PROGRAM............................ SIUXSCAN
DL/I PARAMETER..........................
DBRC
USE DBRC INTERFACE.................... NO
"IMAGE COPY NEEDED" DEFAULT........... OFF
WORK FILE UNIT NAME..................... SYSDA
BUILDALL WORK FILES
DD NAME PREFIX........................ SIUWK
PRIMARY ALLOCATION.................... 5
SECONDARY ALLOCATION.................. 5
SECONDARY INDEX DEFINITION
SECONDARY INDEX DBD NAME................ CUSTNDX1
SECONDARY INDEX DD NAME................. CUSTNDX1
INDEXED DBD NAME........................ CUSTOMER
XDFLD NAME.............................. CFNUMBER
TARGET SEGMENT.......................... CFROOT
SOURCE SEGMENT.......................... CFROOT
SEARCH FIELD(S)
NAME.................................. CUSTNUMB
START................................ 166
LENGTH............................... 9
TYPE................................. CHARACTER
NULLVAL................................. X?40?
TYPE OF POINTER......................... SYMBOLIC
LAYOUT OF THE INDEX DATABASE RECORD
1-BYTE DELETE BYTE.................... 1 - 1
9-BYTE SEARCH FIELD(S)................ 2 - 10
14-BYTE SYMBOLIC POINTER............... 11 - 24
DDNAME ?DFSURWF1? LRECL=00900 BLKSIZE=11860
SCAN COMPLETED SUCCESSFULLY
INDEX SCAN OUTPUT RESULTS
?CFNUMBER? RECS WRITTEN TO ?DFSURWF1?... 2,926
RECORDS SUPPRESSED BY NULLVAL........... 0
LOAD COMPLETED SUCCESSFULLY
INDEX LOAD OUTPUT RESULTS
?CFNUMBER? RECS WRITTEN TO ?CUSTNDX1?... 2,926
Figure 10 SYSPRINT Output from Index Scan and Index Load Report
16 SECONDARY INDEX UTILITY General Information
Information on Index Availability
PLUSLIST Output from Index Scan and Index Load Report
The sample report shown in Figure 11 lists any error messages generated
while processing the control statements. It also lists the results of performing
the function specified in the control statements. A time stamp is included at
the start and end of each function.
******************************************************************************
*** S I U ********** B M C S O F T W A R E, I N C. ********** S I U ***
******************************************************************************
>>>> 10:27:29 PROCESSING STARTED FOR COMMAND ?XFLD?
SECONDARY INDEX DEFINITION:
-----------------------------
SECONDARY INDEX DBD NAME = CUSTNDX3
INDEXED DBD NAME = CUSTOMER
XDFLD NAME = CFCACRFN
TARGET SEGMENT = CFROOT
SOURCE SEGMENT = CFCAC01
SRCH = CACREFNO START = 1 LENGTH = 6 TYPE = C
NULLVAL = X?40?
DATABASE DDNAME = ?CUSTNDX3?
TYPE OF POINTER = SYMBOLIC
LAYOUT OF THE INDEX DATABASE RECORD:
1-BYTE DELETE BYTE
6-BYTE* SRCH FIELD(S)
14-BYTE SYMBOLIC POINTER TO TARGET SEGMENT
>>>> 10:27:29 FUNCTION COMPLETED WITH NO ERRORS
>>>> 10:27:29 PROCESSING STARTED FOR COMMAND ?XSCN?
PARM PASSED TO DFSRRC00:
DLI,SIUXSCAN,SIUPSB..
INDEX SCAN OUTPUT RESULTS:
DDNAME ?DFSURWF1? LRECL=00900 BLKSIZE=11860
NUMBER OF ?CFCACRFN? RECORDS WRITTEN TO ?DFSURWF1? = 204
NUMBER OF RECORDS SUPPRESSED BECAUSE OF NULLVAL = 0
SCAN COMPLETED SUCCESSFULLY
>>>> 10:29:08 FUNCTION COMPLETED WITH NO ERRORS
>>>> 10:29:08 PROCESSING STARTED FOR COMMAND ?XFLD?
(data omitted)
>>>> 10:29:08 FUNCTION COMPLETED WITH NO ERRORS
>>>> 10:29:08 PROCESSING STARTED FOR COMMAND ?XLOD?
INDEX LOAD OUTPUT RESULTS:
NUMBER OF ?CFCACRFN? RECORDS WRITTEN TO ?CUSTNDX3? = 204
LOAD COMPLETED SUCCESSFULLY
BMC2700 -------> DBRC PROCESS START 1/2/96 10:29:54.35
BMC2700 NOTIFY.REORG PROCESS COMPLETE FOR DATA BASE CUSTNDX3
BMC2700 NOTIFY.UIC PROCESS COMPLETE FOR DATA BASE CUSTNDX3
BMC2700 -------> DBRC PROCESS END 1/2/96 10:31:45.20
>>>> 10:31:46 FUNCTION COMPLETED WITH NO ERRORS
Figure 11 PLUSLIST Output from Index Scan and Index Load Report
Information on Index Availability
SECONDARY INDEX UTILITY 17
SYSPRINT Output from WF1 Split Report
Figure 12 shows the content of the output data when the WF1 Split function
is run. The report shows the content of both the logical relationship and
secondary index output files. It includes a frequency distribution of the
record types found in the WF1 input data set, as well as the size of each
record type.
**************************************************************************
* S I U ******** B M C S O F T W A R E, I N C. ******** S I U *
**************************************************************************
S E C O N D A R Y I N D E X U T I L I T Y (V 2.7)
IMS/VS 5.1.0 DATE=96.002 1/2/96 TIME=20:50
LISTING OF INPUT CONTROL CARDS:
....+....1....+....2....+....3....+....4....+....5....+....6....+....7
SPLIT INDD(SIUURWF1) OUTDDX(DFSURWF1) OUTDDL(LOGURWF1)
INDEX SPLIT OUTPUT RESULTS:
CONTENT OF LOGICAL DATA SET:
DBDNAME DBDNAME TYPE LENGTH COUNT
-------- -------- ---- ------ ----------
TESTDBD8 TESTDBD9 00 69 2,002
TESTDBD8 TESTDBD9 10 66 1,913
TESTDBD9 TESTDBD8 00 54 1,912
TESTDBD9 TESTDBD8 10 49 2,002
CONTENT OF INDEX DATA SET:
DBDNAME LENGTH COUNT
-------- ------ ----------
TESTDBD7 22 2,002
SPLIT COMPLETED SUCCESSFULLY
Figure 12 SYSPRINT Output from WF1 Split Report
18 SECONDARY INDEX UTILITY General Information
System Requirements
System Requirements
SECONDARY INDEX UTILITY operates on any CPU that supports any
IBM-supported version of MVS. The hardware requirements are the same as
those required by IBM?s IMS/VS or IMS/ESA Database Manager feature.
SECONDARY INDEX UTILITY supports all IBM-supported versions of
IMS and will support new versions as they become available from IBM.
SECONDARY INDEX UTILITY requires any IBM-supported version of
MVS.
Program Considerations and Restrictions
SECONDARY INDEX UTILITY currently does not completely support
shared secondary indexes. However, it may perform all index functions up to
the actual loading of a specific secondary index into the shared index
database. At that point, the HISAM Reorganization Reload utility would be
required to perform the actual loading of the shared secondary index.
However, SECONDARY INDEX UTILITY may be used to rebuild all
indexes in a shared secondary index.
SECONDARY INDEX UTILITY does not support PSB field-level
sensitivity.
Installation and Operation
SECONDARY INDEX UTILITY is simple to install. You can use the
DBU/RCU Install System or IEBCOPY to copy the SECONDARY INDEX
UTILITY and Database Utilities files from the distribution tape to a disk. To
install the optional online facility, add the Database Utilities primary menu
to an ISPF product menu and modify the TSO logon procedure of all users
requiring access to SECONDARY INDEX UTILITY, or use the LIBDEF
procedure.
SECONDARY INDEX UTILITY is simple to use. You run the unload and
scan functions with the same JCL that you used for the IMS HD
Reorganization Unload utility with few or no modifications. Typically, the
only change you would make to your existing JCL would be to add a
JOBLIB or STEPLIB DD statement to concatenate the SECONDARY
INDEX UTILITY load library ahead of the IMS/VS library.
System Requirements
SECONDARY INDEX UTILITY 19
To fully exploit all of the SECONDARY INDEX UTILITY facilities, you
may want to add a PLUSIN DD statement to your JCL or use the PDX data
set. The optional PLUSIN data set contains command parameters that define
the user-controlled options for the unload or scan process. You can also
specify the parameters through the online facility.
20 SECONDARY INDEX UTILITY General Information
System Requirements
About BMC Software 21
22
About BMC Software
BMC Software, Inc. is a leading independent vendor of system software for
IBM and IBM-compatible mainframe systems. The products developed,
marketed, and supported by BMC Software enhance operations in the IMS,
DB2*, CICS, VTAM, VSAM, and VM environments.
Maintenance and Support
BMC Software is committed to providing the best systems software products
and product support in the industry. This commitment results in superior
new products and enhancements to existing products and maintenance to
meet our customers? highest needs for performance and value.
BMC Software is committed to maintaining its products so they remain
compatible with the most current releases of IBM software and hardware.
BMC Software?s product support personnel provide fast, comprehensive
answers to questions from users. They are experts both in the BMC Software
products they support and the environment these products enhance.
Because many BMC Software products are used on 24-hour, 7-day-a-week
production systems, BMC Software?s product support staff are on call 24
hours a day, 7 days a week, 365 days a year.
22 SECONDARY INDEX UTILITY General Information
BMC Software?s 30-Day-Plus Free Trial
BMC Software?s 30-Day-Plus Free Trial
BMC Software recognizes the special needs data processing organizations
have when evaluating new software. To serve these needs, BMC Software
offers a free trial of its products at your installation.
The 30-Day-Plus Free Trial works like this:
1. Install the BMC Software product on your test system and become
familiar with its operation.
2. When you are ready, move the product to your production system and
begin the trial period.
3. At the end of the trial period, contact your BMC Software sales
representative to arrange for acquisition of the product. If the product
does not meet your needs, simply return the program tape and product
documentation to BMC Software.
BMC Software trial tapes automatically expire after the trial period.
Please understand that all BMC Software tapes and documentation are
confidential and are for your company?s exclusive use. By accepting this
free trial, you acknowledge that the product is a trade secret of BMC
Software. |
|
