Chapter 2   CICS Repository


iPlanet Application Server for CICS stores metadata to define the data and services available to an iPlanet Application Server servlet or EJB from a CICS system in the repository.

Repository data include two types of metadata definitions:

• Connector types define connector specific characteristics including the types of operations that are available (function object types) and the kinds of logical connections supported (service provider types).

• Data sources define a logical data source that specifies data and business functions available on a specific backend system; it is useful to think of a data source as an category of an connector type. The data source defines the actual functions that can be used (function objects) , the supported connections (service providers), as well as other information.

This chapter contains the following sections:

• Overview of Management Console

• Creating a New Data Source

• Editing a Data Source

• Data Mining

Overview of Management Console

---

The management console has two groups of functions:

• Tasks that are used to process and browse data and functions: data mining, add new data sources, and load XML into the UIF repository.

• User management that establishes relationships between the web and backend users.

The tasks performed with the management console are explained in this chapter. See iPlanet Application Server Enterprise Connector for CICS Administrator's Guide for a description of the use of the management console for user mapping.

Entering the Console from NT

1. Select Start>Programs>iPlanet Application Server 6.0>iAS for CICS Management Console
   
   .

Entering the Console from Solaris

Run: cicsconsole.sh

from <iplanet>/ias/APPS/bin

There are three tabs: Tasks, CICS User Management, and Listener Management.

• The Tasks tab contains icons for accessing screens that allow you to Create New Data sources, Edit Data sources, and do Data Mining.

• The CICS User Management tab allows you to access icons for administrative tasks. See the Administrative Guide for more details.

• Listener Management is used to manage listener jobs. See the Administrative Guide for more details.

Creating a New Data Source

---

1. Click the Create New Data Source icon to display the Create New Data Source dialog box.
   
   

2. Type in the following data:
   

   
   
   

   DataSource Name
   Applid	This field specifies a CICS program name that is to be invoked on the CICS system. In the system described below, the CICS program could be BLP1, BLP2, or BLP3.
   Applind	This field is used to indicate the conversation state status, and can be in one of the following three states: E - The conversation is inactive. The conversation has either not yet started or already ended. The E state is an ending state. To leave the E state, the client application must start a new conversation. M - In the M state, the client application has the right to send data and the service application must receive it. When in the M state the client application is in control of the conversation. S - In the S state, the service application has the right to send data and the client application must receive it. When in the S state the service application is in control of the conversation. The client starts the client application from an inactive state (E). The client application's first call to NAS for CICS identifies the service application with all conversation parameters needed. The first call starts the service application on the remote platform, if not already started. The conversation then continues until one of the applications stops it, either normally, or abnormally, at which point the conversation enters the E state.
   Conversation Type	Must contain "POOLED". The CICS connector determines if it has to conduct a pooled conversation through a relay, or a nonpooled conversation directly over APPC based on the value in the ConversationType field. The conversation becomes POOLED for a pooled conversation, and DIRECT for a direct conversation.
   LU	The Logic Unit (LU) name where the transaction specified in TranName is defined if SRVXLINK is used. This is where SRVXLINK itself resides.
   Request	This field specifies the communication operation that the Relay performs: SendAndEnd - Sends data to the server application, waits for a reply, and then ends the conversation. SendLast - Sends data to the server application and waits for a reply. Send -- Send data to the server application. Receive - Receive data from the server application. End - Ends the conversation with the server. Quit - Aborts the conversation with the server. If you do not intend to use the Server Side API, you should use the "SendLast" command. If you do intend to use the Server Side API, use the two phase commit mechanism of "SendAndEnd".
   StubRC	This is the return code from the SRVXLINK program.
   StubRequest	The StbRequest instructs SRVXLINK what to do. The following values are acceptable: COMMIT - to automatically commit the transaction upon successful execution of the BLP. EXECUTE - do not automatically commit the transaction.
   Target system ID	The system ID of the CICS in which SRVXLINK starts a program. If the program resides on the same CICS as SRVXLINK, no specification program is required.
   Transaction Name	The transaction name. In the CICS system, each transaction is identified by a four letter code, and is accessed with a program name. This tells CICS what program to start.
   Target Transaction Name	Not used in this version
   Use Stub	This determines whether you are using the SRVXLINK program or not. Values should be "Y" or "N".
   Hold Conversation	This configuration places the conversation on "hold" for the user until he wants to access it again. This option guarantees that the user accesses the same CICS transaction on its next execution of an operation, within the same user interaction.
   RC	Return Code. The return code is received by the CICS Connector during its conversation with the Relay.
   TranName	The transaction name. In the CICS system, each transaction is identified by a four letter code, and is accessed with a program name. This tells CICS what program to start.
   RelayRCl	This is the return code (RC) that the Relay received from conversations with the CICS server.

3. Press the OK button; the new Data Source is created and displayed in the Choose Data Source window.

Editing a Data Source

---

This is used to edit an existing data source.

1. Click the Edit Data Source icon to display the Choose Data Source list.
   
   

2. Select the Data Source and then click the OK button to display the Edit Data Source dialog box.

3. Type changes in the text boxes and then click the OK button.

   The changes are made in the repository.

Data Mining

---

Data mining is the search for relationships and global patterns that exist in large databases. These relationships represent valuable knowledge about the database and objects in the database.

The CICS Mining Tool, which is part of the Management Console, allows you to determine the available transactions on the CICS system and to load this metadata into the repository.

The elements of the data mining are shown in the following illustration.

Figure 2-1    Elements of the Data Mining

The user selects the COBOL files, mines these files, converts them to XML, and then loads them into the repository.

Displaying the Data Mining Selections

1. Click the Data Mining icon to display the Choose Data Source drop down menu.
   
   

The data sources are located at:

• Convert local COBOL file

• Convert remote COBOL file

• Select the location of the data source that is to be mined.
  
  

  
  

  ---

  Note	The following procedure converts a local COBOl file. See Converting a Remote File for an explanation of how to convert a remote COBOL file.

  ---

  
  

• Click the OK button to display the Open dialog box.
  
  

  Navigate to the file that is to be opened, and then click the Open button.

• A dialog box is displayed asking if you want to generate a Hint file.
  
  

• Click the OK button to generate the Hint file.

  A Hint file determines the input and output parameters. This is required when the layout of the input parameter differs from that of the output parameters. If the No button is clicked, the input and output blocks are the same.

Generating a Hint file

COBOL programs that have a redefines clause may need a hint so that the generator knows which definitions are to be used as input and which are to be used as output. The hint is stored in a Hint file.

1. Click the Yes button in the Console Question.

   The Management Console Hints Generator is shown below:
   
   

2. Select the structure or field that is to become an input or output parameter;e.g. OUTPUT-SEC.

3. From the Tools menu, select Add Input Parameter or Add Output Parameter.

   The Input and Output parameters appear in the appropriate windows as shown in the example.

4. The mining tool runs and converts the COBOL file to XML. A Message box appears informing you that the file has been correctly converted.

Converting a Remote File

Remote files can be converted to XML via FTP.

1. Select Convert Remote COBOL File from the Option chooser drop down menu box.

2. Click the OK button to display the Open dialog box.

Loading XML into Repository

1. Select the Load XML into Repository icon in the CICS Management Console to display the Input DataSource dialog box.

2. Select the Load into Repository check box.

3. Click the OK Button to load the file.

   When you load the selection into repository XML is not automatically saved. You must select the Save XML check box in order to save the function. The operation is finished when the progress indicator disappears.