Before you start
This tutorial shows COBOL developers how to improve productivity using IBM® Rational® Developer for System z™ (hereafter called Developer for System z). You see how to check the syntax of COBOL assets located on the local workstation or by remotely accessing them on z/OS.
You also see how to compile COBOL code locally on the local workstation or remotely accessing the compiler on z/OS.Y ou play through several typical scenarios, you explore both local and remote syntax checking capabilities, and you see how to configure the workstation for the various scenarios.
This tutorial covers several of many possible scenarios, including ones using COBOL with and without CICS, one with DB2 on the local workstation, and COBOL programs that access VSAM on z/OS.
Although this tutorial demonstrates various tasks using COBOL assets, you could use similar steps to work with PL/I.
When you complete this tutorial, you should know how to use Developer for System z to:
- Work with COBOL batch code and with CICS statements that access either VSAM or DB2.
- Work with COBOL/CICS/DB2 code on the local workstation.
- Work with COBOL/CICS code on z/OS.
- Check syntax of COBOL code on your local workstation.
- Compile COBOL code on your local workstation.
- Check syntax of COBOL code stored on z/OS.
- Compile COBOL code stored on z/OS.
To get the most out of this tutorial, you should be comfortable with COBOL programming on z/OS and have some familiarity with Rational Developer for System z.
On your workstation you need Rational Developer for System z Version 7.1 and IBM TXSeries for Multiplatforms Version 6.1 installed to test the examples. TXSeries is included in Rational Developer for System z V7.1. You must also have the Developer for System z components installed and configured on the mainframe because you will need to connect and submit jobs for remote execution.
You need to have already defined on your workstation a remote system and you should be connected to that system. For detailed help in s creating this connection, see the IBM Rational Developer for System z Version 7.1.1 information center.
For the scenario that uses a local database, you will also need DB2 installed on your workstation and the database name SAMPLE created. This tutorial was tested with DB2 Version 8.2, but you could use a later version, if desired.
You also will need to allocate z/OS datasets to hold the assets and a
VSAM file. This tutorial provides the sample programs, JCL, and
properties that are used. See About the
download for information about the assets provided in the
download. Table 1 shows the required datasets and their
characteristics to implement the scenarios. The high level qualifier
is
XXX. You can use the
ALLOC_PDS.jcl job (provided in the
download) to help you allocate the data sets.
Table 1. The z/OS data sets you need to allocate for the scenarios
| Data set name | Record format | Record length | Block size | Content |
|---|---|---|---|---|
XXX.POT.COBOL
|
FB
|
80
|
8000
| COBOL programs |
XXX.POT.COPYLIB
|
FB
|
80
|
8000
| COBOL copybooks |
XXX.POT.LISTING
|
FBA
|
133
|
1330
| Compiler listing |
XXX.POT.LOAD
|
U
|
0
|
6233
| Load module |
XXX.POT.OBJ
|
FB
|
80
|
3200
| Object |
XXX.GENERTED.JCL
|
FB
|
80
|
8000
| JCL |
This tutorial takes about 1 hour to complete, after you have prepared your system according to the System requirements.
The download includes code that you can use to implement the scenarios. Unzip the download file to a temporary drive, such as c:\temp. You load the code according to the instructions that follow in the scenarios below.
The download zip includes these assets:
SCENARIO#1_Project_interchange.zip – To create the project used in the scenario #1.
SCENARIO#1_PROPERTIES.xml – Properties used in the scenario #1.
SCENARIO#2_Project_interchange.zip – To create the project used in the scenario #2..
SCENARIO#2_PROPERTIES.xml – Properties used in the scenario #2.
SCENARIO#3_PROPERTIES.xml – Properties used in the scenario #3.
SCENARIO#4_PROPERTIES.xml – Properties used in the scenario #4.
ALLOC_PDS.jcl – This JCL can be used to allocate the PDS required.
DEFVSAM.jcl – To create and load the VSAM file used in the COBOL programs.
P1VSAM.cbl – COBOL program used in the scenarios without CICS and DB2.
VSAMCOPY.cpy – COBOL copybook used by P1VSAM and P4CICS programs.
P4CICS.cbl – COBOL program used in the scenarios with CICS.
COMAREA.cpy – COBOL copybook used by P4CICS program.
P43CICS.cbl – COBOL program used in the CICS scenario with copybook with EXEC CICS.
CUSTREC, CUSTIORQ and COPYCICS – COBOL copybooks used by P43CICS program..


