Rational Developer for System z

B. Begin the flow recording

In this topic specify parameters for the New Flow Recording wizard and begin the flow recording.

To begin the flow recording:

  1. If you have not already done so, connect to the remote z/OS® system and start the CICS® example catalog application (egui) (see Step 2 in A. Prepare for the flow recording).

  2. Verify that the Main Menu application screen is displayed in the session area.

  3. Verify that the host editor is in flow mode (see Screen operations mode and flow mode):

    1. On the host editor toolbar, which is located immediately above the session area and to the left of the information area, verify that the first icon on the host editor toolbar is the Go to Screen Operations Mode icon Go to Screen Operations Mode.

    2. If the first icon on the host editor toolbar is the Go to Flow Mode icon Go to Flow Mode, then click the icon once.

    The first icon on the toolbar should now be the Go to Screen Operations Mode icon Go to Screen Operations Mode.

  4. On the host editor tool bar, click the Reload Screen Descriptions icon Reload Screen Recognitions.

    This action causes the most recently saved versions of your screen descriptions to be loaded. (You created the screen descriptions in Step 2.3: Create two screen descriptions for the Inquire Catalog application screen.)

  5. On the host editor toolbar, click the Start Flow Recording icon Start Flow Recording.

  6. The Start Recording Flow window:

    • It is possible that in the current host editor session you have worked on another recorded flow and that as a result, you have a previously recorded terminal flow loaded in the host editor as the current working flow.

    • If so then the host editor displays the Start Recording Flow window with the following message:

      Do you want to add to the working flow '<flow_name>'?
      Select "No" to create a new flow.
        
                              

    • Click No so that a new flow is created.

  7. The New Flow Recording wizard opens. This wizard prompts you for the names of resources that it needs to create before flow recording can begin.

  8. On the first and only page of the New Flow Recording wizard, titled Record a terminal flow:

    1. In the Flow field, type CheckItemAvailability.
      • The name of the new flow is CheckItemAvailability.
      • When you save the flow, the flow will be stored into the flow file CheckItemAvailability.seqflow.
    2. In the Interface Resources group, click Create all new resources. This will cause the wizard to create the following resources for the recorded flow:
      • Interface Operation:
        • The name of the port type and also the name of the interface operation of the flow is intf_CheckItemAvailability.
        • The port type and the interface operation of the flow will be stored into the file intf_CheckItemAvailability.wsdl.
        • Table 1 shows the resources associated with the interface operation:
          Note: These resources are not shown in the New Flow Recording wizard. To see these resources, open the screen operations file with the screen operations editor.
          Table 1. Resources associated with the interface operation
          Item: Function: Name:
          Port Type The port type is a container for the operation. intf_CheckItemAvailability
          Operation The operation contains the information required to invoke the flow CheckItemAvailability. intf_CheckItemAvailability
          Input The Input contains a reference to the input message of the flow (see Input Message below). A reference to i_CheckItemAvailability.
          Output The Output contains a reference to the output message of the flow (see Output Message below). A reference to o_CheckItemAvailability.
          Faults The Faults contains references to the faults messages of the flow. Not used in this flow.
      • Input Message:
        • The name of the input message of the flow is i_CheckItemAvailability.
          • The input message of the flow will be stored into the file i_CheckItemAvailability.sfmxsd.
          • The input message of a flow describes the data structure of the input parameters that are passed to the recorded flow when it is invoked.
      • Output Message:
        • The name of the output message of the flow is o_CheckItemAvailability.
          • The output message of the flow will be stored into the file o_CheckItemAvailability.sfmxsd.
          • The output message of a flow describes the data structure of the parameters that the recorded flow passes back when it returns from being invoked.
      • Variable Message:
        • The name of the variable message of the flow is v_CheckItemAvailability.
          • The variable message of the flow will be stored into the file v_CheckItemAvailability.sfmxsd.
          • The variable message of a flow contains two types of variables used by the flow:
            • Variables required by Extract actions, Insert actions, and recorded loops.
            • General-purpose variables that you use for manipulating data in the flow.

    3. Also in the Interface Resources group, select the check box Automatically expose insert and extract variables in the interface operation messages.

      Selecting this option causes the host editor during flow recording to automatically add to the input message or output message of the flow a message element corresponding to the variable that you select for a new Extract action or Insert action

    4. In the Terminal Resources group, the Screen Operations field contains the name to be used for the currently loaded screen operations file:
      • At this point the Screen Operations field should contain the same name that you specified for the Flow field at the top of the wizard page: CheckItemAvailability.
      • The screen operations file in memory will be stored into the screen operations file CheckItemAvailability.sfmxsd on the hard disk of your workstation.
      • During flow recording, as you navigate through the terminal application, your keyboard input is recorded into the currently loaded screen operations file

    5. Click Finish.

      The New Flow recording wizard creates the specified resources for the new flow.

  9. Flow recording begins.

    The host editor and the session area should now be visible again. Verify that:

    1. The Stop Flow Recording icon Stop Flow Recording is now displayed on the toolbar, indicating that flow recording is in progress.

    2. The CICS example catalog application is still displaying the Main Menu application screen.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)