Initialize data base utility (online conversation)

The online conversation consists of a sequence of screens where you do the following:

• Specify the DBD for the database to be initialized, and specify the ACBLIB if it is a DEDB database.
• Specify the data set names for the database to be initialized.
• Specify batch JCL information.
• Optionally, edit the JCL generated by File-AID for IMS/ISPF to perform the initialization.
• Submit the batch job.

The batch job consists of three to eight steps for full function databases, depending on whether secondary indexes and/or logical relationships are present, and one step for DEDB databases. Following are the main steps of the batch job for full function databases:

1. Inserting a dummy root segment into each database.
2. Deleting the dummy root segments.
3. Writing a report that summarizes the results of the initialization.

The batch job for DEDB databases consists of the standard IMS DEDB initialize utility.

Initialize Database - Database Specification

The Initialize Data Base - Data Base Specification screen, shown in following image, is the first screen displayed upon entry to the Initialize function. This screen is used to specify the name of the DBD that describes the database to be initialized, the name of the DBD load library where that DBD resides, and the ACBLIB where the DBD resides if the database is a DEDB. The DBD must describe a physical database. Logical, index, HSAM, SHSAM, and MSDB databases are not supported in the Initialize function.

Initialize Data Base - Data Base Specification Screen

The presence of a highlighted plus (+) or minus (-) sign indicates data set concatenations. For more information, see Data-set-concatenation-support.

DBDLIB dataset 1 and dataset 2

Enter one or two DBD load library data set names. If you enter one DBD load library name, you can enter it on either of the dataset name lines. If you enter two DBD load library names and their block sizes are different, you must enter the library with the larger block size on the first dataset name line.

Member

Enter the DBD member name. If you enter two DBD library names, File-AID for IMS/ISPF searches the first before the second to locate the DBD member.

Terminating the Screen

Do one of the following to terminate the Initialize Data Base - Data Base Specification screen:

• Press Enter to proceed to the Data Base Dataset Specification screen.

  If you leave the DBD Member field blank, the DBD Member List screen is displayed next. If two DBD libraries are concatenated, the member list is a merged and sorted list of the members in both data sets. You can then select the DBD member from the member list.

• Enter the END or RETURN primary command or a jump command to terminate the initialization process.

Initialize data base dataset specification

The Data Base Dataset Specification screen, shown below, is used to specify the dataset names for the database you want to initialize. The database must be uninitialized, and its data sets must be empty.

INITIALIZE - Data Base Dataset Specification screen

Obtain DB dataset names from (lines 3 – 6)

The dataset name field is initially set from the name you previously used for the data set with P specified. If you specify I, the dataset name is set from the IMS dynamic allocation source. The IMS dynamic allocation source is the dynamic allocation member in DFSRESLB DD or DBRC for the IMS 7.1 HALDB databases.

If File-AID for IMS cannot retrieve the dataset name, the message NO MDA MEMBER FOR DBD is displayed in the DATASET NAME field.

The heading lines also indicate whether DBRC is in use and if used, the name of the RECON1 dataset and from where the RECON1 dataset name was obtained.

DBD

Displays the name of the primary DBD you entered on the Data Base Specification screen.

DDNAME

Displays the DD name of the first data set group in the primary DBD.

Dataset name

Enter the database dataset name to be allocated to the DD name.

There are two conventions to enter a database dataset name. If you enter every node in the dataset name, the name must be enclosed in apostrophes. If the first node of the data set matches your TSO ID, you can omit the first node and the apostrophes.

When a dataset name has a node identical to the ddname of the data set, you can substitute an asterisk for that node. If a dataset name has more than one node equal to the DD name, you can substitute an asterisk for only one of the nodes.

A separate line is displayed for each additional data set group in the primary DBD. The DBD column is blank and the DDNAME column displays the ddname for the data set group. Each line also has the database Dataset Name and Password fields.

Any external DBDs that are directly referenced by the primary DBD (such as a secondary index DBD or a logically related DBD) are shown sequentially under the primary DBD with their ddnames, Dataset Names, and Password fields. There can also be DBDs and ddnames listed that are not directly referenced by the primary DBD. These are from DBDs that are indirectly related to the primary DBD through the primary’s external references. You must enter database dataset names for all listed DD names.

Once you enter a database dataset name on the Data Base Dataset Specification screen, that dataset name is retained from session to session (see to User Profile Dataset). If you entered I in the Obtain DB Dataset Names from field, the dataset names are retained only if no dataset names exist in the user profile data set for the associated database ddnames. In subsequent sessions, File-AID for IMS/ISPF pre-formats those dataset name fields where it has saved names.

Password

Enter the password if the database dataset is OS password-protected. The password for an OS password-protected data set is not saved across sessions.

DISP

This field displays the disposition to be used when the data set is allocated. For File-AID for IMS functions that do not update the data set such as browse and extract, the data sets are allocated with a disposition of SHR. Functions that update such as edit and load cause the data set to be allocated OLD unless the dataset name is the name registered in DBRC.

SHR LEV

This field displays the DBRC-registered share level of the data set. N indicates that the DBRC-registered level is not being used.

Terminating the Screen

Do one of the following to terminate the Data Base Dataset Specification screen:

• Press Enter to move forward in the initialize conversation. The Initialize Data Base - JCL Specification screen (here) is displayed. Any data set names you entered are saved.
• If you want to return to the beginning of the initialize conversation, enter the END command. You are returned to the Data Base - Data Base Specification screen. Any data set names you entered are saved.
• If you want to terminate the initialize conversation, enter the RETURN command. Any dataset names you entered are saved, and you are returned to the Primary Option Menu.
• When you press Enter or scroll the display, the data sets shown on the screen are allocated. Once allocated, the name cannot be updated on the screen. To change the name after it is allocated, return to the prior screen and start over. Changing the Obtain DB Dataset Names from field causes the allocated data sets to be unallocated.

Data Base Initialize Image Copy Specification

The Data Base Initialize Image Copy Specification screen is displayed as shown below, following an Initialize function, if IMS requires that any of the database data sets require an Image Copy before being used. IMS requires that all HALDB data sets be image copied following an Initialize. IMS 23.1 also requires that non-HALDB datasets be image copied following an Initialize.

Data Base Initialize Image Copy Specification Screen

Perform Image Copy

Performing the Image Copy is optional. Enter Y to perform the Image Copy as part of the load JOB and N if you do not want File-AID for IMS to perform the Image Copy as part of the Load JOB.

High Level Image Copy DSN node

You can specify the High Level node of the Image Copy data sets. The default is your user ID. For very large data sets, you may want to save and edit the JCL, modifying the space allocation for the Image Copy data sets.

If all of the data sets that would normally require an Image Copy are registered as not recoverable, then an Image Copy is not required. Therefore, the Data Base Load Image Copy Specification screen is not displayed.

However, File-AID for IMS cannot perform the Image Copy if any of the data sets that require an Image Copy are registered in DBRC using the REUSE option. DBRC GENJCL must be used to perform the Image Copy because DBRC needs to determine which Image Copy data set to use.

If any of the datasets registered with REUSE is a non-HALDB data set, the following screen is displayed.

Data Base Initialize Image Copy Specification (Informational) Screen

For more information on the Load utility, see Editing the Generated JCL.

If all of the data sets registered with REUSE are HALDB data sets, the following screen is displayed instead.

Data Base Initialize Image Copy Specification (Informational) Screen

Initialize Data Base - JCL Specification Screen

The Initialize Data Base - JCL Specification screen, shown below, is used to specify the initialization job JCL information. This screen is displayed after the Data Base Dataset Specification screen.

Initialize Data Base - JCL Specification Screen

Enter the SYSOUT class for the initialization report, the JOB statement information, and other related JCL statements (for example, /*JOBPARM and /*ROUTE statements).

File-AID for IMS/ISPF automatically allocates an IMS log data set that is deleted after the successful completion of the initialize job or cataloged if the job ends abnormally. Additional information on the IMS log data set and its usage is provided in IEFRDER DD.

Terminating the Screen

Do one of the following to terminate the Initialize Data Base - JCL Specification screen:

• Press Enter to generate the JCL, submit the initialize job for execution, and return to the INITIALIZE Data Base - Data Base Specification screen.
• Enter the JCL primary command to advance to an ISPF/PDF Edit screen where you can edit the generated JCL before submitting the job.
• Enter the END command to return to the INITIALIZE Data Base - Data Base Specification screen without submitting the initialization job.
• Enter the RETURN command to return to the Primary Option Menu without submitting the initialization job.

Editing the Generated JCL

If you entered the JCL command on the Initialize Data Base - JCL Specification screen, an ISPF/PDF Edit screen similar to the one shown in the following figure, is displayed.

ISPF/PDF Edit Screen

At this point, the ISPF/PDF editor has been invoked on the temporary data set that contains the JCL generated to perform the initialization. All ISPF edit commands are available for use. For example, to insert additional JCL statements, use the I (Insert) line command. To change the JCL, type over the data. To delete a line, use the D line command. You can use the CREATE and REPLACE primary commands to save the generated JCL into a partitioned (PDS) or sequential dataset, which enables you to submit the JCL in the future without using the online conversation screens.

Do the following after you view or edit the JCL:

• Enter the SUBMIT command to submit the initialization job for execution. The Data Base Initialization Report (here) is generated.
• Enter the END or CANCEL command to return to the INITIALIZE Data Base - Data Base Specification screen.