Rational Developer for IBM i (RDI) Distance Learning hands-on Labs IBM Rational Developer for i. Maintain an ILE RPG application using.

Transcription

1 IBM Software Rational Developer for IBM i (RDI) Distance Learning hands-on Labs IBM Rational Developer for i Maintain an ILE RPG application using Remote System Explorer Screen Designer intro Lab Exercises Lab05 Lab 5 Page IBM Corporation

2 Copyright International Business Machines Corporation, All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Page 7 Rational Developer for i V7.5

3 Contents LAB 5 SCREEN DESIGNER INTRODUCTION OVERVIEW EXPLORING THE SCREEN DESIGNER PERSPECTIVE EXPLORING THE SCREEN DESIGNER PERSPECTIVE THE SCREEN DESIGN EDITOR CREATING NEW RECORD FORMATS CREATING A SUBFILE...38 Lab 5 Page 8

4 Lab 5 Screen Designer Introduction Important! Screen Designer is a Technology Preview. Some functions have not been completely tested or might be missing. 5.1 Overview Using an editor to create and maintain DDS source for your display files can be a frustrating and difficult task. What would be great is a graphical design tool that let s you design your screens visually and then generate the DDS source for you. Well, that s exactly what Screen Designer does for you Skill level Introductory Audience IBM i developer System requirements IBM Rational Developer for i, V7.5.1 and all software updates through the IBM Installation Manager. IBM i V5R3, V5R4, or V6R Prerequisites Basic Microsoft Windows operations such as working with the desktop and basic mouse operations such as opening folders and performing drag-and-drop operations It will also help if you understand DDS, CL and ILE RPG. This tutorial is divided into a number of modules, each with its own learning objectives. You can choose to skip modules. You can go directly to the Screen Designer module if you are only interested in that part, however you are required to complete the module LAB01 to get instructions for creating a connection to an IBM i server. Each module contains several lessons that should be completed in order for the tutorial to work as shown in this script Expected results Upon completion of this tutorial you will know how to verify/compile an IBM i application from the Remote System Explorer. You will also know how to run an interactive program using the Remote System Explorer Conventions used in this tutorial Bold font for user interface controls Mono-spaced font for user input and code blocks Italic font for variable names and glossary terms. Page 9 Rational Developer for i V7.5

5 Important! You should go through Lab01 'Create a connection and get started with RSE' before you work on this Lab. Lab01 contains the following information: Which IBM i server to connect to, Which userid to use, How to setup the correct library list for this lab. Learning objectives 1. Starting the screen designer and exploring the Screen Designer perspective. 2. Learn how to work with Screen Designer screens. 3. Creating new record formats with Screen Designer. 4. Adding constants and fields to records. 5. Adding attributes and conditioning indicators to fields. 6. Working with Screen Designer and the source editor. 7. Compiling Display File source 8. Creating subfiles with Screen Designer. 9. Working with subfile records and subfile control records in Screen Designer 10. Working with DDS keywords in Screen Designer 5.2 Exploring the Screen Designer perspective Screen Designer helps the novice DDS programmer create screens quickly and easily without worrying about the details of the DDS language, while at the same time letting the expert DDS programmer get access to all the features and power of the language. We ll now step through each part of the interface to show you how to work with our DDS based screens Open a DDS display file member using the RSE In the workbench, in the RSE perspective, use the connection that you created in Lab01. In the Remote Systems view: 1. Expand the Library List filter or if it is still expanded use it as is. 2. Expand the QDDSSRC file in library RSELAB<N> 3. Right mouse click the MSTDSP member and select: 4. Open with --> Screen Designer(Technology Preview) Lab 5 Page 10

6 The member MSTDSP will be downloaded to the workstation and opened into Screen Designer Switching to the Screen Designer perspective You are still in the RSE perspective. We suggest that you move to the Screen Designer perspective to get the correct set of views needed for designing screens. 1. Click the Perspective button. By default it is located at the top right corner of the workbench. 2. Select other Screen Designer. 3. Click the Ok button. Page 11 Rational Developer for i V7.5

7 You can see several views are open, lets go through these views to understand how to work with Screen Designer. 5.3 Exploring the Screen Designer perspective The views of the Screen Designer perspective. Besides the Screen Designer editor, the perspective also contains some additional view, which you don't see in the Remote System Explorer perspective. Before you use Screen Designer for editing, lets look at the different views in this perspective. Lab 5 Page 12

8 The 6 different areas and views are: 1. The screen design editor, that allows you to design the screens. 2. The screen design controls pane, which is actually part of the design editor, allows to select record formats that make up the screens. 3. The Palette, that contains the controls available in DDS. 4. The Outline view showing a tree view of the DDS source. 5. The Properties view, which allows you to work with properties of the selected control in the Design page, Source editor, or Outline view. 6. The RSE view to work with IBM i objects. Note: The first two areas are officially not considered views, instead they are parts of the editor) The Outline view Look at the outline at the lower left corner. You might want to increase its size to show more content. 1. Slide the cursor over the upper border until you see the cursor icon turn into a double arrow. 2. Click the right mouse button, hold it and slide it up to give this view more space. Page 13 Rational Developer for i V7.5

9 What you are looking at now is basically an explorer view of the DDS source. The DDS tree view displays the DDS source in its file, record, field, and keyword hierarchy. It is a familiar and intuitive way to see the overall structure of the DDS source and to navigate through it quickly. Don t worry if you re not a DDS expert, we ll explain everything you need to know. Lab 5 Page 14

10 3. Click the + beside the container DSPSIZ(24 80 *DS3). This is the container for the file level keywords. Its name is composed from all file level keywords used in the display file. You now see the file level keywords in the tree. 4. Click the + beside the record SELECT. It expands up and shows the record level controls and keywords. 5. Click the + beside the container BLINK ALARM. The name of the container consists of all record level keywords used in record SELECT. 6. To get more detail for the field EMESS, click the + beside the field EMESS. 7. Go further down in the hierarchy, click the + beside the DSPATR container. 8. Even further, click the + beside the keyword DSPATR. You can see the properties of the keyword, it is conditioned by indicator 60,. You can also see the detail information for field EMESS which shows that the field is positioned on line 21, column 16. The DDS Tree is now showing you a nice summary of the file-level keywords and of the record SELECT The Properties view. Page 15 Rational Developer for i V7.5

11 The properties page displays and allows you to edit the properties of currently selected controls. Lets have a look. 1. In the Outline view, click the display file MSTDSP node. The Properties view will display the properties for the display file. You can see that the tabs on the properties page reflect the property types for the selected control/part, in this case the display file. Feel free to click on some of the tabs to look at the existing properties for this display file. Lets see how the Properties view changes when you select the EMESS field in the Outline view. 2. In the Outline view, select field EMESS, the Properties view will change to reflect the properties available for a field. Lab 5 Page 16

12 Notice the different tabs. Feel free to explore the field properties and select different tabs in the Properties view. After looking at the Outline and Properties views, let's now explore the Screen Design editor. 5.4 The Screen Design editor You will spend most of your time creating, updating, and designing your DDS screens in the Screen Design editor. The Design page allows you to design your screens visually using an intuitive graphical user interface. The tab on top of the editor shows the source member that you are editing, the workbench allows you to open multiple members in an editor simultaneously, each open member will have a tab in the workbench editor area. Page 17 Rational Developer for i V7.5

13 You notice that the Screen Design editor has two main areas the actual Design area and the Design page screen controls. Lets look at the screen controls first Design page screen controls Notice that in the Screens list you see two entries, All records and MAIN_MENU. By default the top item All records in the screens list will be selected.. The right hand list under the Records tab shows all record formats in the source member.to see the record formats that make up the Main_Menu: 1. Select the MAIN_MENU entry in the Screens list. Lab 5 Page 18

14 Notice that the Records list on the right changes. It now contains a list of Excluded record formats and a list of Included record formats. This tells you that the MAIN_MENU screen is made out of one record format, the record format SELECT. In order to understand where MAIN_MENU came from, we need to describe the concept of a Screen. A screen is simply a collection of one or more DDS record formats that represent how a screen would be assembled at runtime. It allows you at development time to work with screens as they would appear when they get assembled by your programs at runtime. To work with screens in Screen Designer you need to tell Screen Designer which record formats belong to each screen. In this case we have done this for the screen you see in the design page. We have created a screen MAIN_MENU and Screen Designer saved this information in the DDS source in comment lines. Any screens that you create are persisted as comment lines in the DDS source member so you can re-use these screens in subsequent Screen Designer sessions. The Design page screen control area is used to manage screens: 1. Create new screens, 2. Add/remove records to/from screens, 3. Delete screens, 4. Select which screen should appear in the design area Working with Screen Designer screens. As we explained in the previous section, a screen in Screen Designer is a collection of records that reflects the runtime environment for display file records. If you are working with existing DDS, you will want to create screens that will correspond to how the Page 19 Rational Developer for i V7.5

15 records are being used at runtime. In this lab you create a new screen that is used when the user selects which employee in the payroll database to maintain. The screen consists of one record format EMPSEL. Create a new screen: 1. Click the New button in the Design page screen controls area 2. Enter EMPL_SELCT as the name for the screen 3. Click the Apply button Now add the record format to this screen. 4. Click the Records tab to select it 5. Select the EMPSEL record in the Excluded list. 6. Click the Add button to move the record format to the Included list Lab 5 Page 20

16 Notice that the design area now displays this screen and you could go and change it in the design editor. Page 21 Rational Developer for i V7.5

17 You have created a new screen from an existing record format. Now you are going to create a new record format. 5.5 Creating new record formats First let's create a standard record and then later a subfile record Creating a new Screen Designer screen In order to create a new 5250 screen and work with its record formats in the design area you need to create a Screen Designer screen first. 1. Like before click the New button in the Design page screen controls area 2. Enter the name RSNMAINT1 in the entry field on the Screens pane. 3. Click the Apply button Lab 5 Page 22

18 5.5.2 Creating a new Standard Record format The design area at this moment doesn't show anything because no record format is specified for screen RSNMAINT1. Let's change that. In the Palette view on the right side of the work bench: 1. Select the Standard Record icon by clicking it 2. Move the cursor to the design area (you don't need to drag the cursor) 3. Click in the design area to add the record format Page 23 Rational Developer for i V7.5

19 What you now see, is the design area with an empty record format. Lab 5 Page 24

20 You have created a new screen with the name RSNMAINT1, containing a new record format. Notice, that the Palette changed and now contains more controls. It shows all controls that are valid to be used at this point. New drawers in the palette containing different control types have been added: 1. Fields 2. Constants 3. Help To change the name of the record from its default name RECORD1 to something meaningful, 4. Select the record tab in the design page screen control by clicking on it 5. Select the Record1 record format in the included list Click the Properties tab in the view area underneath the screen design editor to select the Properties view. Click the Basics tab Enter RSNFMT1 in the name field. The name is changed in the record list when you click somewhere else. Page 25 Rational Developer for i V7.5

21 Now you can design your screen using the controls from the palette by adding them to the record format in the design area Adding constants to the record format. First you add some constants 1. In the Palette, click the Text constant control to select it. 2. Move the cursor onto the design area until the hover text states row 2 column 5 3. Click at this point in the design area to place the text constant onto the record format. Lab 5 Page 26

22 Notice that the Properties view has changed and reflects the properties of the currently selected control, which is the new text constant. 4. Change the constant text by changing the text entry field in the properties page. Enter PRG01. Tip: You could also type direct into the control in the design area. 5. Click somewhere else in the Properties view, for example the Description field to cause an event to be fired that will apply the change to the design area. If the constant still contains trailing blanks shorten it by following these steps: 6. Move the cursor into the design area on top of the right edge of the text constant, over the middle rectangle that indicates the border of the selected control so that the cursor changes to a two sided arrow. 7. Drag the border to the left to remove the blanks from the constant, so that only the text is shown. Notice that you can change the location of the constant on the record format by dragging it around or by using the spin button on the properties page, we will let you try these features in the next steps. Lets look at the source that got created for you. At the bottom of the screen design editor Page 27 Rational Developer for i V7.5

23 8. Click the Source tab to select it. The DDS source gets displayed in the LPEX editor. You can see the two statements the screen design editor added to the source member. We want you to create some more constants and fields on the record format. You could use the source editor, but for this exercise you will use screen design editor. Go back to the screen design editor: 9. Click the Design tab at the bottom of the editor, below the source lines. Now add another text constant. This time you will use the Properties view to position to the correct location. 10. Click the Text Constant control in the Palette view to select it 11. Position the cursor somewhere in the Design area and click to create a text constant. Lab 5 Page 28

24 To change the properties: 12. Click the Properties tab to select it, if it is not already selected. 13. Change the text to Time Reporting System. 14. Use the row spin button to move the constant to row Use the column spin button to move the constant to column 30. You need to add a couple more constants to the record: Page 29 Rational Developer for i V7.5

25 Click the Text Constant control in the palette view to select it Position the cursor somewhere in the design area and click to create a text constant. In the Properties view on the Basics page, enter the constant text Employee Master Maintenance You will now position the constant to the correct location by dragging it Lab 5 Page 30

26 19. In the design editor click the constant to select it 20. Hold the left mouse button as you select it 21. Drag it until the hover text indicates its position is row 3 column Release the mouse button to drop it If you want to practise your Screen Designer skills, you can add eight more columns to the record format by following the next steps, or you can stop after step 28 and skip to topic adding named fields You need to add eight more text constants, we will give you the text and position for these constants. You can practise your Screen Designer skills by adding them to the record format. 23. Add the following text constant to row 5, column 30: Reason Code 24. Add the following text constant to row 7, column 9: Description 25. Add the following text constant to row 9, column 31: Reason Code History 26. Add the following text constant to row 11, column 26: 27. Current Page 31 Rational Developer for i V7.5

27 28. Add the following text constant to row 12, column 27: Month 29. Add the following text constant to row 11, column 36: Year To Prior ^5 spaces 30. Add the following text constant to row 12, column 38: Date Year ^6 spaces 31. Add the following text constant to row 23, column 7: F3-End of Job 32. Add the following text constant to row 23, column 25 F4-Maintenance Selection 33. Add the following text constant to row 23, column 54: F7-Reason Code Selection. Your screen should look like this: Lab 5 Page 32

28 5.5.4 Adding Named Fields to the record. Adding fields to a record is very similar to adding constants, select the named field control in the palette and drop it onto the design area. 1. Click the Named Field control to select it. 2. Move the cursor to row 7 column 22 in the design area. 3. Click at this position to create the field To work with the field properties: Page 33 Rational Developer for i V7.5

29 Click the Properties tab On the Basics page Enter the field name RSDSC To enter the field reference information 7. Click the Reference tab 8. Select the Database Reference radio button Important! If you are using RDi or lower, the Browse button for field reference information does not work properly. You need to manually enter the reference information. Follow the instructions in steps 10 and Click the Browse... button Lab 5 Page 34

30 In the Select a field dialog, expand *LIBL. Expand library RSELABxx. Expand file RSNMST. Expand record RCRSN. Select field RSDC. Click the OK button. If the Browse button doesn't work key these values into the entry fields and follow step 10 and 11: 10. Instructions for RDi version or lower Fill in the reference information Library: RSELABxx File: RSNMST Record: RCRSN Field: RSDSC 11. Click the Apply button to save the reference information. Page 35 Rational Developer for i V7.5

31 Note: In a previous version of the RDi Screen Designer, you could drag fields from the RSE Field Table View into the design editor. This function does not work in this version. This is a known problem which will be fixed in the full release of RDi Screen Designer Notice that the Referenced field properties have been pulled in and are now shown in the Properties view. Lab 5 Page 36

32 Now you will add the Protected attribute for this field to protect it under the condition that indicator 90 is On. 1. In the Properties view, click the Attributes tab. 2. Click the Protected check box to select the Protected attribute. 3. Click the Add button on the right side of the list box. The Protected attribute is added to the list of attributes. To condition the Protected attribute: 4. Click the DSPATR(PR) entry in the attribute list 5. Click the Indicators... button on the right side of the list Enter 90 in the first white indicator box, to specify indicator 90 as the conditioning indicator for this attribute. Click the OK button Page 37 Rational Developer for i V7.5

33 The attribute list now shows indicator 90 for the Protected attribute Adding more fields Troubleshooting As mentioned before, if you are using RDi or lower, you can not use the Browse button to add reference information to the fields. You will need to add this information manually. We suggest that you create the fields in the designer, but then use the source editor and copy the reference information from field RSNDSC which you just created. Now add the reason code field to the record: 1. In the Palette view, select the Named Field control. 2. Click the design area to put this named field in row 5 column 43 Lab 5 Page 38

34 3. 4. In the Properties view, click the Basics tab and change the field name to RSCDE Change the usage to Output. Now specify the reference information later Click the Reference tab Click the Browse button Select *LIBL --> RSELABxx --> RSNMST --> RCRSN --> RSCDE. Click the OK button. Now you'll add fields for the reason code history: 9. Add another Named Field to the record at row 13 column In the Properties view, change the name to RSHRC. 11. Change usage to an Output field. 12. To add reference information, click the Reference tab 13. Click the Browse button 14. Select *LIBL --> RSELABxx --> RSNMST --> RCRSN --> RSHRC. 15. Click the OK button. 16. Add output field RSHRY and position it at row 13 column 35. Page 39 Rational Developer for i V7.5

35 17. Add the reference information 18. Add output field RSHRP and position it at row 13 column Add the reference information Now you'll put a time constant and a date constant on the screen. 20. Select the Time Constant control in the palette and position it at row 3 column Select the Date Constant control in the palette and position it at row 2 column 70. Add the Edit Code for the date constant: 22. Select the Date Constant you just added in the design area 23. In the Properties view, click the Editing tab, 24. Select the Edit code radio button as Edit type. 25. Scroll down in the Edit code list until you see Edit code Y Troubleshooting In RDi or lower the Y Edit Code doesn't show in the list of Edit Codes. Select the 'o' that shows in the list and fix the Edit code later using the source editor. One more field is needed, a message field at the bottom of the screen. Lab 5 Page 40

36 26. Select a Named Field in the Palette view and position it at row 21 column In the Properties view on the Basics page, enter EMESS as the name. 28. Change Usage to an Output field. 29. Change its length to 50. Now add the high intensity attribute and condition it with indicator 60: 30. Click the Attributes tab. 31. Select the High intensity check box. 32. Click the Add button Select the High intensity attribute in the attribute list. Click the Indicators... button. Enter 60 in the first white box on the indicator page Click the OK button. Page 41 Rational Developer for i V7.5

37 Note: If you want to negate an indicator, enter any character in the yellow field in front of it and the tool will add an N in this field. 37. Save your work by using the CTRL+ S shortcut key,or use the Save icon on the workbench tool bar. Now it is time to compile what you have created Compiling Your DDS In order to get the compile options on the workbench menu bar you need to switch to the Source editor, which by default will add the compile menu actions. 1. Click the Source tab in Screen Designer 2. In the workbench menu click the Compile action. 3. On the pull down menu click the Compile action. 4. Click the CRTDSPF action. Lab 5 Page 42

38 In the error list at the bottom of the workbench, you should see a message indicating no messages have been generated. Tip: If you get error messages in the error list, check if you get lots of reference file related messages. If that is the case, most likely your library list doesn't contain your library. Go to the RSE view, right click your library and select action Add library list entry. Compile again. If you get a few messages in the error list, double click each one. The source editor gets focus and the cursor is positioned at the line that is causing the problem. Fix the problem and compile again until the display file gets created. Tip: The Commands Log view will display the RSE job log messages. Page 43 Rational Developer for i V7.5

39 Tip: The default is to send the create command to batch. You can change this setting in the workbench Preferences dialog. In the Remote Systems Explorer area under IBM i, command execution (Window --> Preferences --> Remote Systems --> IBM i --> Command Execution) Let's look at creating a subfile with the Screen Designer next. Lab 5 Page 44

40 5.6 Creating a subfile Creating a subfile record involves using the same techniques that you have used when creating a standard record, so this should just be a breeze for you to go through Creating the subfile record A subfile requires a different record type. Instead of using the Standard record control on the palette you now use the Subfile record control. As before, first identify the screen to add the record to, or create a new screen in the Design page screen controls area. 1. In the Design page screen controls area, click the New button. 2. Enter EMPL_LIST as name. 3. Click the Apply button. 4. Click the Records tab to select the Records page. To create the subfile record, in the Palette view in the Records drawer: 5. Select the Subfile Record control by clicking it. 6. Move the cursor to the design area and click it to create the subfile record. You will notice that the Included records list in the screen control area is filled with two new records, a subfile record and a subfile control record. To work with either of these records, click one of them to bring it into focus in the Design area. Page 45 Rational Developer for i V7.5

41 Note: You can also use the Outline view to put different controls in focus. Notice that the new record names by default are SFL1 and CTL1. Most likely you want to change the names to something more meaningful. 7. Click the control record CTL1 in the Included list. Use the Properties view to change the name. 8. In the Properties view Basics page, change the name to EMPLSTCTL. Lab 5 Page 46

42 To change the subfile record name 9. In the Design page screen controls area, click the SFL1 record in the Included list 10. Change the name in the Properties view to EMPLSTSFL. Now you are ready to add some fields/columns to the subfile Adding fields/columns to a subfile You add fields to a subfile record the same way you add fields to a standard record. Page 47 Rational Developer for i V7.5

43 Make sure the EMPLSTSEL record is selected, not the EMPLSTCTL control record. The Screen Designer editor will add the fields to the record that is in focus at the moment. In the Palette view in the Fields drawer, click the Named Field control to select it Click the Design area at the row 8, column 5 position. A column will be created with the default of 6 rows. Let's change the properties of this column. In the Properties view on the Basics page : 4. Change the field name to OPCODE 5. Change the length of the field to 3 6. Change the usage of the field to Input. We want you to change the color Lab 5 Page 48

44 Select the Color tab in the Properties view. Select the Pink radio button. Click the Add button on the right hand side of the Color properties page. You will add two more columns to the subfile record. First create an employee name column: 10. Create a Named field at row 8, column Name it ENAME. 12. Change the length to Change the usage to Output. Create another named field for employee salary: Page 49 Rational Developer for i V7.5

45 14. Create a Named Field at row 8 column Name it SALARY. 16. Change usage to Output. 17. Change the type to Zoned. 18. Change Shift to Y Numeric only. 19. Change the Length to Change the decimals to 2. The edit code needs to be changed, so that the numbers will look readable and a $ sign should be added: 21. Click the Editing tab in the Properties view to select the editing DDS properties page 22. Click the Edit code radio button. 23. Click the currency symbol check box. 24. Select edit code 1 from the list of edit codes. Notice, that a sample of the formatting is displayed on the Editing page, to show you how the resulting field will look like when the selected editing is applied. This can come in handy, if you are not sure which editing code you need to use. Lab 5 Page 50

46 25. Use the Color properties page to apply the color yellow to this column. Don't forget to click the Add button on this page. You are done with the subfile record and can now go on to work with the control record Adjusting the subfile control record properties We want you to add 3 more rows to the subfile page size so that the end user sees some more data, and we want you to change the subfile size to 300. Page 51 Rational Developer for i V7.5

47 1. In the screen control area, select the sub file control record EMPLSTCTL in the Included records list to give it focus in the design editor 2. In the Properties view, select the Subfile Control tab. 3. Increase the SFLSIZ property to Increase the SFLPAG size to 9. We want you to explore some more features of the Screen Designer. One of these features is the capability to see multiple records in a screen, or to hide all records except the one that is in focus Hiding or showing records in the Design area. In this step you will toggle the transparency setting 1. In the button toolbar at the top of the Design area, click the Transparency button, it toggles between transparency and non transparency. Here is the subfile control record shown with transparency on Lab 5 Page 52

48 The subfile control record has focus, but you still can see the subfile record columns in the Design area. All records of a screen are shown, since transparency is set on. Your subfile control record doesn't have any content at the moment that is the reason it appears empty. 2. Click the Transparency button again, to hide all records except the subfile control record. Now the Design area is empty. Only content of the subfile control record is shown with the transparency Page 53 Rational Developer for i V7.5

49 setting switched off Note: In the Screen Designer, you can only work with the fields and constants of the record that has focus at the moment. These fields and constants are shown highlighted in the design area. The other controls of records not in focus are shown dimmed. Working with transparency on, gives you a better view of the impact that changes in one record have, in relation to the other record formats on the same screen. On the other hand sometimes it might be confusing to see all the fields of all records on the same screen, then transparency off might work better for you. Use the transparency setting that works best for you. For the next exercise: 3. Set transparency on so that you can easier work with the subfile control record in relation to the subfile record Switching between Multiple Records If you want to switch to a specific record to work with, go to the Design area screen controls and select the record. As you already noticed in the previous exercise, selecting a record in the Design area screen controls allows to switch focus between records. There are actually three different areas that allow you to select the record that you want to work with in the design area: 1. The Design area screen controls area. 2. The Outline view. 3. The Source editor. Yes, you can also select a record or control in the source editor and the selection will be reflected in the Screen Designer editor. Now you will add controls to the subfile control record and exploit some more of the Screen Designer features Copy and Paste We want you to provide a Position to entry in the subfile control header. Make sure that the EMPLSTCTL record is selected and in focus. 1. Add a Text Constant to it, by selecting the control on the Palette view and then position it at row 4, column Change the text of the constant by clicking it in the design area,. This gives it a blue outline. Now you directly type over the default text. Type: Position to : Notice, how the fields expands as you type. Lab 5 Page 54

50 Add an employee name input field to this heading. You could just get the Named Field control from the Palette and position it on the design area to add it to the record. Instead, use copy and paste inside the Screen Designer editor. You already have an Employee name field in the subfile record, why not re-use that field for the Position to input field. 3. Click the subfile record EMPLSTSFL in the Design page screen controls to select it. The design area now has the subfile record highlighted because it is in focus. 4. Select the top row of the second column in the subfile, the ENAME column. 5. Right click it and select the copy action. Page 55 Rational Developer for i V7.5

51 6. Now click the subfile control record EMPLSTCTL in the Design page screen controls to bring the control record into focus 7. Right click in the design area and paste the field select the Paste action. This adds the field to the control record. 8. Select the field and drag it to position row 4, column Working with the Preview Troubleshooting The Preview with indicator sets does not work in this Technology Preview. Please skip these steps and skip to topic: Adding New Keywords. Now you will work with the Preview tab in the Screen Designer to see how it can help you with your screen design tasks. To make this exercise more meaningful, you will add some conditioning to the ENAME field in the subfile control record. You will add some color and display attributes and condition these with an indicator. Then you will create an indicator set in preview mode to see how setting the indicators on or off will change the screen in preview mode. This will give you a good sense how the preview mode can help you simulate the runtime screen behavior. Lab 5 Page 56

52 Put in some error handling for the position to employee name field. If the employee name is not found in the database, the program will set on indicator 60. The screen should display the field red, reverse image and position the cursor to it. 1. Make sure the EMPLSTCTL record is in focus 2. Select the ENAME field. 3. Select the Attributes tab in the Properties view. 4. Select the Reverse Image check box. 5. Select the Position Cursor check box. 6. Click the Add button on the Attributes page. Page 57 Rational Developer for i V7.5

53 Click the DSPATR(RI PR) entry in the list of attributes, to select it. Click the Indicators... button on the right side of the Attributes page. Enter 60 in the first white input field in the Configure Indicators dialog. Click the OK button. You have now created the conditioned display attributes, next create the color attribute under condition 60. Lab 5 Page 58

54 Click the Color page in the properties view. Select the Red radio button. Select the COLOR(RED) attribute in the attributes list. Click the Indicators... button. Enter 60 in the indicators dialog Click the OK button. Now that you have these additional attributes added you can test your screen in Preview mode. You will create an indicator set that allows you to simulate a set of indicator being set on/off, the set you create will use indicator Click the Preview tab at the bottom of the Screen Designer editor. 11. In the Preview page screen controls click the Indicators tab that gets displayed in Preview mode 12. Click the New button to create a new indicator set. 13. Give it the name NotFound, Tip: You can create multiple named Indicator sets to simulate the runtime behavior of the screen. To make these most useful give the Indicator sets meaningful names that are easy to remember, in case you or somebody else needs to re-use them at a later time. 14. Select the check box for indicator 60. Page 59 Rational Developer for i V7.5

55 15. Click the Apply button Adding New Keywords If you want to add keywords to a specific control in your display file. Select the control in the design area, the Outline view, or the source editor. In the Properties view, click the Keywords tab and select the keyword you want from the list of keywords. Lab 5 Page 60

56 You can see a list of specified keywords for the selected control and a list of allowed keywords. You can remove already specified keywords or add new keywords to the control Creating the display file Now you need to re-create the display file to add your changes. As before in the previous section: 1. Switch to source editor by clicking the Source tab 2. Select the Compile --> Compile -->CRTDSP action The error list should show no error messages. This concludes the Screen Designer Lab. Page 61 Rational Developer for i V7.5

57 Congratulations! You have successfully completed the introduction to RDi Screen Designer Technology Preview. Feel free to explore the other modules in this RDi tutorial More information and material can be found at our RPG CAFE Look for the RDi hub Enjoy Rational Developer for IBM i! Lab 5 Page 62

58 Notices Copyright IBM Corporation 1992, 2009 All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this documentation in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user s responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this documentation. The furnishing of this documentation does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: Page 63 Rational Developer for i V7.5

59 Intellectual Property Dept. for WebS phere Software IBM Corporation 3600 Steeles Ave. East Markham, Ontario Canada L3R 9Z7 Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. Copyright license This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. 1992, All rights reserved Trademarks and service marks 4. The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.i5/os IBM OS/400 Rational WebSphere Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Lab 5 Page 64

60 Other company, product or service names may be trademarks or service marks of others. Page 65 Rational Developer for i V7.5