IBM Rational Developer for System z PROC Validation

Size: px

Start display at page:

Download "IBM Rational Developer for System z PROC Validation"

Archibald Collins
6 years ago
Views:

1 RDz Workstation / Host Component Validation IBM Rational Developer for System z PROC Validation Checklist #3 Version V1.3 February 27, 2012 The home location for this document is in the RDz Server Health Checklist on IBM.com:

2 Overview The purpose of this exercise is to verify the PROCs used for the generation of compile, link and execution JCL by Rational Developer for System z (RDz). You are referred to these settings in this document when they are needed: Settings Table: Setting Link libraries Load Module Location Value EFH410.CICS.SDFHLOAD CEE.SCEELKED <Your TSO UserID>.RDZ.LOADLIB <Your TSO UserID>.RDZ.LOADLIB Example Job Card for your RDz UT System: //DBT2602F JOB (6400,GL800,999,999),'IMS', // CLASS=C,MSGCLASS=Q,REGION=8M,NOTIFY=&SYSUID Page 2 of 24

Starting out, you will normally press the Start button then navigate to here: 2.

3 Validation Steps 1. Start RDz. You may invoke RDz differently depending on your environment. Starting out, you will normally press the Start button then navigate to here: 2. Utilize the workspace created with the document named RDz Connection Confirmation check list, named \RDzWorkspaces\Workspace1 and click OK : Page 3 of 24

4 3. If you are not already connected to your System z, right click the connect identifier you set up previously (possibly DEV ) and choose Connect : 4. Enter your credentials and click the OK button: Page 4 of 24

In the upper right corner of your workspace, expand your MVS Files

5 5. Expand your Initial Local Project project, under the z/os Projects tab and your COBOL subfolder: 6. In the upper right corner of your workspace, expand your MVS Files and My Data Sets sections, under the Remote Systems tab so it is similar to this screen capture: Page 5 of 24

clicking your left mouse button on each file you want to choose) 8.

6 7. Select the COBOL programs in your Initial Local Project project, COBOL subfolder, then right click the files selected and choose Copy : (Hint: You can select multiple files by holding down the CTRL key and clicking your left mouse button on each file you want to choose) 8. On your MVS Files section under the Remote Systems tab, in the upper right of your workspace, right click your RDZ.COBOL dataset and choose Paste : Page 6 of 24

7 You see this dialog for a moment: You just copied a set of files from your local PC workspace to a PDSE on your System z. Your expanded RDZ.COBOL dataset looks like this: Page 7 of 24

You must supply the appropriate information one time.

8 9. Set up a Property Group that RDz uses to automate certain tasks for you. In some instances, RDz submits a job on your behalf, or generate JCL. You must supply the appropriate information one time. In the Property Group Manager view, right click the Dev connection and click New Property Group. A new property group opens in the Property Group editor. 10. On the Info tab, name the Property Group RDz Setup. Press Ctrl-S to save the new property group. Page 8 of 24

9 11. In the Categories tab, select these options, while clearing the BMS Settings and MFS Settings options: Page 9 of 24

10 12. In the COBOL tab, click Runtime Environments, and then select CICS. If you have CICS Transaction Server Version 3.2 at your shop, choose the level of the CICS Transaction Server for z/os appropriate for your z/os instance from the pull-down menu next to Use CICS. Page 10 of 24

11 13. Still in the COBOL tab, click Procedures and Steps. Expand the ELAXFCOC procedure name, click the line that contains the COBOL step name. When you click the COBOL step, the compile step options open in the editor. Page 11 of 24

14. Add this exact information in the COBOL step options: Debug Data Set: <HLQ>.RDZ.SYSDEBUG Copy Libraries: <HLQ>.RDZ.COBOL Select Support Error Feedback.

12 14. Add this exact information in the COBOL step options: Debug Data Set: <HLQ>.RDZ.SYSDEBUG Copy Libraries: <HLQ>.RDZ.COBOL Select Support Error Feedback. When RDz generates the JCL from these settings, <HLQ> substituted with your TSO UserID. Page 12 of 24

13 15. In the Link tab, expand ELAXFLNK and select the LINK Step Name to edit it. Page 13 of 24

14 16. On the Link Step Options page, for Link Libraries specify the libraries appearing in the Settings Table found on Page 2. Link Libraries: Specify the library appearing in the Settings Table found on Page 2. Separate each of the dataset names with a space. Substitute your actual TSO user ID for the phrase, <YOUR TSO USERID>. Load Module Location: Substitute the phrase <YOUR TSO USERID> with your actual TSO user ID. Your input dialog will look similar to the screen capture below. When you are finished with the changes, click the OK button. Page 14 of 24

17. In the JCL tab, for the Job Card, specify a valid Job Card you use at your site. An example Job Card that corresponds to the standard for your site can be found in the Settings Table on Page 2.

15 17. In the JCL tab, for the Job Card, specify a valid Job Card you use at your site. An example Job Card that corresponds to the standard for your site can be found in the Settings Table on Page 2. Make sure you have specified a valid job card. For the JCL Data Set: input text box, substitute the phrase <YOUR TSO USERID> with your actual TSO user ID. 18. Press Ctrl-S to save the property group, and then close the Property Group editor. Page 15 of 24

16 19. Use the property group you have created to control what happens when you select a program for compile and link. Right click RDZ.COBOL and from the pop-up menu, select Properties. Page 16 of 24

20. In the Properties dialog, click Property Group, and then select the RDz Setup checkbox to assign this property group for use by your RDZ.COBOL PDS.

17 20. In the Properties dialog, click Property Group, and then select the RDz Setup checkbox to assign this property group for use by your RDZ.COBOL PDS. Once it is checked, click OK : Those are all the properties you change for now. Properties can be exported and imported. Although you did manual setups to allow you to experience setup steps, you can also supply a property file for import. To export your properties, you can right click MVS Files, and from the pop-up menu, select Export Properties. Do NOT export your properties; they are already exported for you. Page 17 of 24

18 Now compile and link the COBOL programs you originally imported and moved to your z/os datasets. 21. Under the Remote Systems tab, expand your RDZ.COBOL dataset. Rightclick your FUNDPROG.cbl program, and choose Generate JCL -> For Compile Link and click. Page 18 of 24

19 22. Make sure a valid job name is displayed, and your <Your TSO UserID>.RDZ.JCL dataset is identified as the dataset that the generated FUNDPROG Compile/Link JCL will write to. Press OK : 23. After a moment, a dialog similar to this screen capture is displayed, indicating your Compile/Link JCL has been generated into your dataset. Press OK : 24. Under the Remote Systems tab, expand your RDz.JCL dataset and doubleclick FUNDPROG.jcl. Page 19 of 24

An outline is provided for many types of standard files, and can be used as a

20 25. The generated JCL is placed in the RDz editor area. 26. Click on the Outline tab in the lower left-hand corner of the RDz workspace. An outline is provided for many types of standard files, and can be used as a navigational aid when files are large. 27. Click the x on the FUNDPROG.jcl tab to close the editor. Page 20 of 24

JCL dataset and right click FUNDPROG.jcl. Click Submit : 29.

21 28. Submit the JCL to compile and link your program. Under the Remote Systems tab, expand your RDZ.JCL dataset and right click FUNDPROG.jcl. Click Submit : 29. After a moment, a dialog similar to this screen capture is displayed, indicating your Compile/Link JCL has been submitted. Press OK : Page 21 of 24

Your JES listing is displayed at the bottom of the RDz workspace.

22 30. Expand the JES section under DEV in the Remote Systems tab, right click My Jobs and choose Show in Table : 31. Your JES listing is displayed at the bottom of the RDz workspace. Click the refresh button to refresh the list (Hint: Most lists can be refreshed if you do not see what you are expecting): Page 22 of 24

23 32. Double click your job under the Remote System Details tab and it is brought into the RDz editor area. Check to see for a zero (0) return code for both the Compile and Link your output might not look exactly like this: (Hint: Pressing the Ctrl and f keys at the same time displays a find dialog so you can search for strings such as COND CODE ) 33. Click the x on the tab showing your SYSOUT to close the RDz editor area. Page 23 of 24

34. Complete the compilation of the remaining

COBOL dataset, by executing steps 23-31 (you do

dataset members: Do not compile FUNDFILE.

You should see these if you expand your <Your

24 34. Complete the compilation of the remaining COBOL programs in your RDz.COBOL dataset, by executing steps (you do not need to do steps each time) for these dataset members: Do not compile FUNDFILE.cbl it is a copybook. You should see these if you expand your <Your TSO UserID>.RDz.LOADLIB dataset: 35. Click on the X in the upper right of RDz to close. Page 24 of 24

IBM Rational Developer for System z Connection

RDz Workstation / Host Component Validation IBM Rational Developer for System z Connection Checklist #1 Version V1.3 February 27, 2012 The home location for this document is in the RDz Server Health Checklist