Feature allows you to view, create, change, and delete IMS databases and application views (PSBs)

Size: px

Start display at page:

Download "Feature allows you to view, create, change, and delete IMS databases and application views (PSBs)"

Nathan Mitchell
5 years ago
Views:

1 IMS Administration Tool ISPF Demo Script Key Feature: Database and Application Administration Feature allows you to view, create, change, and delete IMS databases and application views (PSBs) DBS/PSB source is generated from different sources DBDLIB/PSBLIB or ACBLIB/IMS CATALOG. New DBDs/PSBs can be modeled from existing ones Users can make updates to DBD/PSB source with the option to import COPYBOOK changes currently this is a tedious, manual, error prone process. Without the tool, users must look at the COPYBOOK and manually code the DBD macro statements or use IMS Explorer for Development(E4D). With E4D, they must pull the DBD source and COPYBOOK source down to their workstation, merge the two, then send back to the mainframe, then go through a separate process to implement the changes into DBDLIB, ACBLIB, and the IMS Catalog. The tool runs DBD/PSB GEN and can update ACBLIB/Catalog instantly or generate the JCL which the user can manually submit later. To access the feature, select #1, Database and Application Administration.

You can select DBDs or PSBs to change from this screen. After those changes are complete, you will then be able to do an online change to activate the new or changed resources.

2 You can select DBDs or PSBs to change from this screen. After those changes are complete, you will then be able to do an online change to activate the new or changed resources. You are required to enter the IMSID here or a? for a list. A? will get you this popup. If you type in the name in the filter, you will still have to move to the line and select the IMSID. This is really only helpful if you have a long list of IMSIDs.

3 If you know the name of the DBD you want to process you can enter it in the DBD Filter field. You can enter part of the name. You cannot use a wildcard as the first character of the name, it treats it as a single *. But, you can enter the first part of the name and then an * as the last character and you will limit the list that way. The Decoded Source Data Set and the Update Source Data Set do not have to exist. You can enter a dataset name and if it doesn t exist, you will be prompted later to create it. You then select the library from which you want to retrieve the DBD. These library fields are populated by Admin Tools through discovery. When you supply the IMSID, the tool uses the libraries that are active in the control region.

4 I ve specified a Decoded Source Data Set that doesn t exist. Since I had a filter for DFS* DBDs I get this list.

Since the Decode dataset didn t exist, the process now asks if I want to create it and gives me the opportunity to change some of the parameters it will use in creating it.

5 Since the Decode dataset didn t exist, the process now asks if I want to create it and gives me the opportunity to change some of the parameters it will use in creating it. When I hit enter, the dataset is created and the decoded DBD is placed as a member in it. You can then use this member in this dataset to make your changes and then import it back into Admin Tool for implementation.

6 Getting back to this screen, you ll notice various libraries that you can use for exporting the data. The only caution here is when specifying 7, or 8. You enter the names on the list on the next page(after you hit enter). Do not mix DBD and ACB libraries. The product will use all of the libraries as if they are concatenated in a job stream. DBDLIBs and ACBLIBs do not have the same structure and trying to mix them together will cause an error. Other than that, you can use all of the libraries listed. Where it says N/A managed by ACBLIBs it just means that the catalog is not accessible from this IMS region.

7 Here you see an IMS region that is managed by the catalog and you see that the ACBLIBs are -NA-

8 Moving on to #2 Application Administration (PSB), you ll see that it works the same as the DBD function, but now it is accessing PSBs. You ll see the same kinds of information and it all works basically the same with few exceptions. Since we ve already gone over most of this when we looked at DBDs I won t go over it again.

The last thing we have in this function is the IMS Resource Change. The update datasets were created when the DBDs or PSBs were selected on the previous screens.

9 The last thing we have in this function is the IMS Resource Change. The update datasets were created when the DBDs or PSBs were selected on the previous screens. That s where you were to make your changes to the DBDs or PSBs and then bring them back in use. This function then allows you to either create JCL to run a batch job that will bring the objects back into the system or to go ahead and execute the function as it is built. On this screen you will enter the libraries that were created in the other functions. From these libraries, you will select members that you want to install. You can select them by name, by filter, or by a list of all that are in the library. You can select either DBDs or PSBs or both at the same time.

10 You will also notice that there is a place for a copybook dataset and one for a copybook XREF dataset The IMS catalog allows for many new fields to be added to a DBD. Once there was a limit of 256 field names in a DBD. But to allow for SQL access to IMS databases, field names had to be known. IMS doesn t require all of the field names in a database to be specified in the DBD. All that IMS requires is that sensitive fields be specified. It had to be specified if it was going to be used for access, such as a key field or a search field. For SQL access the fields have to be specified. The new limit for number of field names allowed in a DBD is 10,000. Since it is next to impossible for anyone to be able to keep track of that many names, this function will help keep everything in sync and it will also create those new fields for you. When you specify the copybook dataset and a corresponding XREF dataset, the fields get inserted into the DBD. When you have redefined fields even at the segment level where a segment may be used for several different purposes, you can have many overlapping definitions. The XREF statements help to organize all of those in a way that is acceptable to IMS. You ll have to see the manual if you want to be able to understand all of this. Just be aware that you can do this function here or it is also available with IMS Explorer. I can t say which way is easier. With explorer, you download all the object into an application with a GUI interface and merge copybooks and DBDs and then export them back to the mainframe for assembly. Here you can do it all without recourse to a GUI application, if that appeals to you. First, I get a list of the members in the DBD update file. I select the ones I want to migrate. I hit enter and I get

11 This is the JCL that gets built for bringing those updated DBDs back into the catalog or ACBLIB that I specified. I can run this job and the objects will be replaced

CA File Master Plus for IMS

CA File Master Plus for IMS ISPF User Guide r8.5 Fourth Edition This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation