320 likes | 765 Views
Application Development for IMS . 2. Agenda for this session. Rational Developer for System z (RDz) overviewLive DemoHands-on Lab. Application Development for IMS . 3. Overview. Application Development for IMS . 4. Rational Developer for System z (RDz) overview. What is RDzIDE (Integrated Develo
E N D
1. Rational Developer for System z Overview, Demo and Hands-on Evgeni Liakhovich – evgueni@us.ibm.com
2. Application Development for IMS 2 Agenda for this session Rational Developer for System z (RDz) overview
Live Demo
Hands-on Lab
3. Application Development for IMS 3
4. Application Development for IMS 4 Rational Developer for System z (RDz) overview What is RDz
IDE (Integrated Development Environment) - make developing faster and easier
Eclipse-based IDE
RDz supports development in the z/OS systems
Provides interactive access to z/OS systems
COBOL, PL/I, C, C++, HL ASSEMBLER, Java, and Web Services
Supports CICS, IMS, Batch, USS, DB2 Stored Procedure, Application Servers.
RDz supports SOA
Enables CICS and IMS applications for Web Services and SOA
Define basic concepts
What is RDz
RDz stands for Rational Development for Systems z.
RDz is an Eclipse based Integrated Development Environment or IDE.
What is an IDE
An IDE is nothing more than a program that helps developers to write programs. The entire purpose of an IDE is to make developing faster and easier. An IDE by definition must at least be able to syntax check, compile, build and test my program.
What is Eclipe
RDz is based on Eclipse. Eclipse is an IDE itself and is an open source. IBM donated this software to be used by the developer community for free. What is so special about Eclipse is the plug-in support, what this means is that software can be built on top of Eclipse and take advantage of the functions that Eclipse already provide.
Eclipse is an IDE
framework that can be extended to include functionality from various vendors. Eclipse comes with
some base features such as a Java editor and is extended by adding “plug-ins”. RDz is a collection of
plug-ins, provided by IBM, that add features to enhance the productivity of mainframe programmers.
RDz functions
RDz besides providing the basics IDE functions for COBOL, Java, PL/I
Provides interactive access to the z/OS systems. When I talk about interactive I am talking about that from RDz the user is able to create or generate JCL, submit JCL, inspect the output, browse datasets in the remote systems and other similar tasks that z/OS developers and systems programmers usually perform
Of course it supports IMS, CICS, DB2 SP
Supports SOA by enabling IMS transaction and CICS as web services
This was original in the chart:
What is RDz
Eclipse-based IDE
IDE (Integrated Development Environment) - make developing faster and easier
Eclipse is an IDE itself. Plug-in capabilities
RDz supports Enterprise Modernization
Supports common IDE for COBOL, PL/I, C, C++, HL ASSEMBLER, Java, and Web Services
Provides interactive access to z/OS for development, debug, job generation, submission, monitoring, command execution
Supports new and existing runtimes (CICS, IMS, Batch, USS, DB2 Stored Procedure, Application Servers.
Transforms UML to COBOL source code
Integration with z/OS tools
RDz supports SOA
Enables CICS and IMS applications for Web Services and SOA
Supports for J2EE, JCA, XML, Web Services
Define basic concepts
What is RDz
RDz stands for Rational Development for Systems z.
RDz is an Eclipse based Integrated Development Environment or IDE.
What is an IDE
An IDE is nothing more than a program that helps developers to write programs. The entire purpose of an IDE is to make developing faster and easier. An IDE by definition must at least be able to syntax check, compile, build and test my program.
What is Eclipe
RDz is based on Eclipse. Eclipse is an IDE itself and is an open source. IBM donated this software to be used by the developer community for free. What is so special about Eclipse is the plug-in support, what this means is that software can be built on top of Eclipse and take advantage of the functions that Eclipse already provide.
Eclipse is an IDE
framework that can be extended to include functionality from various vendors. Eclipse comes with
some base features such as a Java editor and is extended by adding “plug-ins”. RDz is a collection of
plug-ins, provided by IBM, that add features to enhance the productivity of mainframe programmers.
RDz functions
RDz besides providing the basics IDE functions for COBOL, Java, PL/I
Provides interactive access to the z/OS systems. When I talk about interactive I am talking about that from RDz the user is able to create or generate JCL, submit JCL, inspect the output, browse datasets in the remote systems and other similar tasks that z/OS developers and systems programmers usually perform
Of course it supports IMS, CICS, DB2 SP
Supports SOA by enabling IMS transaction and CICS as web services
This was original in the chart:
What is RDz
Eclipse-based IDE
IDE (Integrated Development Environment) - make developing faster and easier
Eclipse is an IDE itself. Plug-in capabilities
RDz supports Enterprise Modernization
Supports common IDE for COBOL, PL/I, C, C++, HL ASSEMBLER, Java, and Web Services
Provides interactive access to z/OS for development, debug, job generation, submission, monitoring, command execution
Supports new and existing runtimes (CICS, IMS, Batch, USS, DB2 Stored Procedure, Application Servers.
Transforms UML to COBOL source code
Integration with z/OS tools
RDz supports SOA
Enables CICS and IMS applications for Web Services and SOA
Supports for J2EE, JCA, XML, Web Services
5. Application Development for IMS 5 History of Rational Developer for System z History (Slide 4)
The intent of this chart is to show that RDz has been around since 2004. It has had four names so farHistory (Slide 4)
The intent of this chart is to show that RDz has been around since 2004. It has had four names so far
6. Application Development for IMS 6 Two Rational Developer for System z (RDz) Offerings Flavors (Slide 5)
EGL – Enterprise Language generation
Java
Either flavor of RDz provides the basic IDE capabilities for COBOLFlavors (Slide 5)
EGL – Enterprise Language generation
Java
Either flavor of RDz provides the basic IDE capabilities for COBOL
7. Application Development for IMS 7 IBM Rational Developer for System z version 7.6
8. Application Development for IMS 8 ISPF based z/OS development environment
To understand the z/OS application environment let’s talk about what a z/OS application programmer would do:
Edit source using ISPF
Exit source
Edit JCL to submit job
Submit job
Swap to SDSF
Look job output
Find error message and line number
Swap to edit session
Exit jcl
Back to 1
This is the process that RDz simplifies
---------------------------------------
To understand z/OS application development, let's take a look at what a typical z/OS application developer would do.
The Interactive System Productivity Facility or ISPF is the typical development environment that the z/OS developer uses to develop applications.
An usual scenario will be for the z/OS developer to use the ISPF editor to edit a source code, find the source line of interest, change and save it. He then switches to the JCL that is used to submit and schedule the job to be run on the z/OS system, makes the necessary changes, and submits it. He then has to switch to another application, usually something called SDSF to monitor his jobs and review the job output. If there are errors, he has to remember where the error is, switch back to an editing session to make the necessary corrections and the cycle goes on.
What we're offering with the z/OS Application Development tools of Rational Developer for zSeries is a way of simplifying this processISPF based z/OS development environment
To understand the z/OS application environment let’s talk about what a z/OS application programmer would do:
Edit source using ISPF
Exit source
Edit JCL to submit job
Submit job
Swap to SDSF
Look job output
Find error message and line number
Swap to edit session
Exit jcl
Back to 1
This is the process that RDz simplifies
---------------------------------------
To understand z/OS application development, let's take a look at what a typical z/OS application developer would do.
The Interactive System Productivity Facility or ISPF is the typical development environment that the z/OS developer uses to develop applications.
An usual scenario will be for the z/OS developer to use the ISPF editor to edit a source code, find the source line of interest, change and save it. He then switches to the JCL that is used to submit and schedule the job to be run on the z/OS system, makes the necessary changes, and submits it. He then has to switch to another application, usually something called SDSF to monitor his jobs and review the job output. If there are errors, he has to remember where the error is, switch back to an editing session to make the necessary corrections and the cycle goes on.
What we're offering with the z/OS Application Development tools of Rational Developer for zSeries is a way of simplifying this process
9. Application Development for IMS 9 RDz based z/OS development environment Common development environment for COBOL, PL/I, C/C++, and Java
With the z/OS Application Development support provided in IBM Rational Developer, the developer now makes changes in the editor, does a syntax check, double-clicks on any error and is positioned at the source statement in error. The developer can make the appropriate changes, save and syntax check, submit the JCL to compile the program, and check the results, all with a few clicks of a mouse. The development process has been simplified.
Transaction gradually
With the z/OS Application Development support provided in IBM Rational Developer, the developer now makes changes in the editor, does a syntax check, double-clicks on any error and is positioned at the source statement in error. The developer can make the appropriate changes, save and syntax check, submit the JCL to compile the program, and check the results, all with a few clicks of a mouse. The development process has been simplified.
Transaction gradually
10. Application Development for IMS 10 RDz: Alternative Interface to MVS datasets and libraries;Managed and controlled via same security and change management process
11. Application Development for IMS 11 Equivalent to g.8 to monitor jobs and 3.4 to browse datasets in ISPF. Can browse jobs and browse datasets in the sameviewEquivalent to g.8 to monitor jobs and 3.4 to browse datasets in ISPF. Can browse jobs and browse datasets in the sameview
12. Application Development for IMS 12
13. Application Development for IMS 13 Workspace - Introduction The workspace is where Application Developer stores project data files
Application Developer stores metadata about the developer’s work in the workspace
Typically a different workspace is used for different projects or for different releases When the workbench is launched the first thing you see is a dialog that allows you to select where the workspace should be located. The workspace is the directory where your work will be stored.
Your workspace is the directory on disk that contains all of your project files, as well as metadata such as preferences you may have customized.
The workspace contains a collection of resources. From the user's perspective, there are three different types of resources: projects, folders, and files. A project is a collection of any number of files and folders. It is a container for organizing other resources that relate to a specific area. Files and folders are just like files and directories in the file system.
A workspace's resources are organized into a tree structure, with projects at the top, and folders and files underneath.
A workspace can have any number of projects.
Notes from David Bean presentation:
You will be prompted to enter a workspace. In the Workspace area, type the location C:\wdzlabs\workspace.
Use the subdirectory of the wdzlabs folder. Note: This can be on a different drive, or even another location on your files system, if you intend running the exercises from a different location. In this case, when you see the above-mentioned location specified in the exercises, use that location in its place.
What is a workspace?
Your workspace is the directory on disk that contains all of your project files, as well as metadata such as preferences you may have customized.
The workspace contains a collection of resources. From the user's perspective, there are three different types of resources: projects, folders, and files. A project is a collection of any number of files and folders. It is a container for organizing other resources that relate to a specific area. Files and folders are just like files and directories in the file system.
A workspace's resources are organized into a tree structure, with projects at the top, and folders and files underneath.
A workspace can have any number of projects.
Note: You are no longer able to specify a workspace directory when starting IBM WebSphere Developer for System z from the command line. If you happen to check the Use this as the default and do not ask again box, and then you wish to point to a different workspace location, you need to do this by starting the workbench and then doing the following:
From the IBM WebSphere Developer for System z workbench menu, select Window -> Preferences.
Then expand Workbench and select Startup and Shutdown. Check the box Prompt for workspace on startup.
Alternatively, you can immediately change the workspace, using the option File -> Switch Workspace.
When the workbench is launched the first thing you see is a dialog that allows you to select where the workspace should be located. The workspace is the directory where your work will be stored.
Your workspace is the directory on disk that contains all of your project files, as well as metadata such as preferences you may have customized.
The workspace contains a collection of resources. From the user's perspective, there are three different types of resources: projects, folders, and files. A project is a collection of any number of files and folders. It is a container for organizing other resources that relate to a specific area. Files and folders are just like files and directories in the file system.
A workspace's resources are organized into a tree structure, with projects at the top, and folders and files underneath.
A workspace can have any number of projects.
Notes from David Bean presentation:
You will be prompted to enter a workspace. In the Workspace area, type the location C:\wdzlabs\workspace.
Use the subdirectory of the wdzlabs folder. Note: This can be on a different drive, or even another location on your files system, if you intend running the exercises from a different location. In this case, when you see the above-mentioned location specified in the exercises, use that location in its place.
What is a workspace?
Your workspace is the directory on disk that contains all of your project files, as well as metadata such as preferences you may have customized.
The workspace contains a collection of resources. From the user's perspective, there are three different types of resources: projects, folders, and files. A project is a collection of any number of files and folders. It is a container for organizing other resources that relate to a specific area. Files and folders are just like files and directories in the file system.
A workspace's resources are organized into a tree structure, with projects at the top, and folders and files underneath.
A workspace can have any number of projects.
Note: You are no longer able to specify a workspace directory when starting IBM WebSphere Developer for System z from the command line. If you happen to check the Use this as the default and do not ask again box, and then you wish to point to a different workspace location, you need to do this by starting the workbench and then doing the following:
From the IBM WebSphere Developer for System z workbench menu, select Window -> Preferences.
Then expand Workbench and select Startup and Shutdown. Check the box Prompt for workspace on startup.
Alternatively, you can immediately change the workspace, using the option File -> Switch Workspace.
14. Application Development for IMS 14 Uses Eclipse 3.4 - Welcome Experience The Welcome dialog is presented the first time you start a new workspace. The roles are shown next to the Enable Roles icon.
Clicking the Enable Roles icon lets you see which roles or capabilities are enabled by default as well as adding or disabling roles.
The roles which are enabled are the buttons that are “depressed”. You can see the names of each of the roles by hovering over each of the icons and the role will display above the icons.
The one that you are interested in is the z/OS Developer (traditional), which is selected or depressed by default.
Click X on the Welcome title bar to close the Welcome view and return the workbench to the z/OS Projects perspective.
The Welcome dialog is presented the first time you start a new workspace. The roles are shown next to the Enable Roles icon.
Clicking the Enable Roles icon lets you see which roles or capabilities are enabled by default as well as adding or disabling roles.
The roles which are enabled are the buttons that are “depressed”. You can see the names of each of the roles by hovering over each of the icons and the role will display above the icons.
The one that you are interested in is the z/OS Developer (traditional), which is selected or depressed by default.
Click X on the Welcome title bar to close the Welcome view and return the workbench to the z/OS Projects perspective.
15. Application Development for IMS 15 User Assistance Features Tour Multimedia addition:User Assistance Tour provides an overview of user assistance features
Embedded in the Welcome and in the Information Center
Also available from the IBM Education Assistant
Features audio and close-captioned text
Translated into 4 languages
Brazilian Portuguese
French
German
Japanese
16. Application Development for IMS 16 IBM Rational Developer for System z workbench In this context, a workbench is the IBM Rational Developer for System z software which has been started on a developer’s machine. It is the user interface of the integrated development environment.
When the workbench is launched the first thing you see is a dialog that allows you to select where the workspace should be located. The workspace is the directory where your work will be stored.
After the workspace location is chosen, a single workbench window is displayed. A workbench window offers one or more perspectives. A perspective contains editors and views, such as the z/OS Projects perspective.
Perspectives. Icons showing the currently open perspective, and some of the available perspectives.
z/OS Projects view with the list of projects which maps to the Windows file system (for local projects) and to a cached copy of remote data sets (for MVS remote projects).
Outline View provides an outline of the parts in the editor.
Remote Error List, z/OS File System, Remote System details, Debug and Search views. The Remote Error List view will list the errors, like syntax errors if they occur, when changes are made in the source editor.
Source editor. This is where the COBOL source code gets coded. Content assist using the shortcut key combination CTRL-space is available when using the source editor. Notice how the COBOL syntax is color-coded in the editor to reflect the special COBOL words. In this context, a workbench is the IBM Rational Developer for System z software which has been started on a developer’s machine. It is the user interface of the integrated development environment.
When the workbench is launched the first thing you see is a dialog that allows you to select where the workspace should be located. The workspace is the directory where your work will be stored.
After the workspace location is chosen, a single workbench window is displayed. A workbench window offers one or more perspectives. A perspective contains editors and views, such as the z/OS Projects perspective.
Perspectives. Icons showing the currently open perspective, and some of the available perspectives.
z/OS Projects view with the list of projects which maps to the Windows file system (for local projects) and to a cached copy of remote data sets (for MVS remote projects).
Outline View provides an outline of the parts in the editor.
Remote Error List, z/OS File System, Remote System details, Debug and Search views. The Remote Error List view will list the errors, like syntax errors if they occur, when changes are made in the source editor.
Source editor. This is where the COBOL source code gets coded. Content assist using the shortcut key combination CTRL-space is available when using the source editor. Notice how the COBOL syntax is color-coded in the editor to reflect the special COBOL words.
17. Application Development for IMS 17 Perspectives and Views Always ONE or MORE VIEWS in ONE PERSPECTIVE You are placed in the z/OS Projects perspective. You can tell the active perspective, by the name in the workbench title bar.
Each view also has a title bar, and the active view is colored. Views can be maximized or minimized by double-clicking the view title bar. Double-click the Welcome view, but do not try double-clicking on the ‘X’ of the Welcome title bar, as this will close the view.
You are placed in the z/OS Projects perspective. You can tell the active perspective, by the name in the workbench title bar.
Each view also has a title bar, and the active view is colored. Views can be maximized or minimized by double-clicking the view title bar. Double-click the Welcome view, but do not try double-clicking on the ‘X’ of the Welcome title bar, as this will close the view.
18. Application Development for IMS 18 1. Project is the highest-level component of the hierarchical structure. It contains its own meta data, that is, information about the project itself. The meta data is stored in an xml file, and is represented by the .project file in the tree structure.
2. Folders are simply containers for files, and can be expanded or contracted to show the files they contain.
3. Files are the artifacts which includes the actual program source, job control language, and so forth.
The two types of projects used in COBOL development are:
Workstation COBOL (Local project)
These are not associated with a system definition
Syntax checking in local projects is performed by the workstation-based compiler
z/OS Project (Remote z/OS project)
These are associated with a system definition, that is, a z/OS systemNotice that the icon for an MVS project shows that there is a system definition associated with it.
MVS subproject (Remote)
Represent the programming resources that constitute a single load module
Requires a z/OS Project
Database Application Project (Remote)
Rapidly create a COBOL CICS application that accesses a z/OS DB2 database
1. Project is the highest-level component of the hierarchical structure. It contains its own meta data, that is, information about the project itself. The meta data is stored in an xml file, and is represented by the .project file in the tree structure.
2. Folders are simply containers for files, and can be expanded or contracted to show the files they contain.
3. Files are the artifacts which includes the actual program source, job control language, and so forth.
The two types of projects used in COBOL development are:
Workstation COBOL (Local project)
These are not associated with a system definition
Syntax checking in local projects is performed by the workstation-based compiler
z/OS Project (Remote z/OS project)
These are associated with a system definition, that is, a z/OS systemNotice that the icon for an MVS project shows that there is a system definition associated with it.
MVS subproject (Remote)
Represent the programming resources that constitute a single load module
Requires a z/OS Project
Database Application Project (Remote)
Rapidly create a COBOL CICS application that accesses a z/OS DB2 database
19. Application Development for IMS 19
20. Application Development for IMS 20 Interactive access to z/OS With RDz you can also define connections for local files. You can map datasets that contain members that are of different types , as shown in the screen shot with a dataset containing both COBOL source and JCL. The flexibility of the mapping allows mapping rules not only for datasets but for members. For example, members with names starting with COBOL are mapped with the cbl extension, names starting with JCL are mapping with the jcl extension.With RDz you can also define connections for local files. You can map datasets that contain members that are of different types , as shown in the screen shot with a dataset containing both COBOL source and JCL. The flexibility of the mapping allows mapping rules not only for datasets but for members. For example, members with names starting with COBOL are mapped with the cbl extension, names starting with JCL are mapping with the jcl extension.
21. Application Development for IMS 21
22. Lab: COBOL application development in z/OS using RDz Maria Querales – querales@us.ibm.com
23. Application Development for IMS 23
24. Application Development for IMS 24 You have copied a COBOL program named CUSVSAM from your workstation to a PDS member. This is a batch program that reads a VSAM data set and display it contents. Also this program does a Dynamic call and a Static call to two other COBOL programs named REGI0B and REGI0C.The figure below shows this program architecture: You have copied a COBOL program named CUSVSAM from your workstation to a PDS member. This is a batch program that reads a VSAM data set and display it contents. Also this program does a Dynamic call and a Static call to two other COBOL programs named REGI0B and REGI0C.The figure below shows this program architecture:
25. Application Development for IMS 25 IBM® Enterprise Modernization Sandbox The Enterprise Modernization sandboxes let you evaluate the IBM Enterprise Modernization solutions
Sandboxes make it easy and fun to quickly try practical scenarios guided by self-paced exercises
You can integrate, test, and deploy applications in a live test environment
IBM provides a mix of full version software trials and "try online" hosted environments
Sandboxes are available to everyone
26. Application Development for IMS 26 Where to find EM4Z Enterprise Modernization Sandbox for System z (EM4Z)
http://www.ibm.com/developerworks/downloads/emsandbox/
ibm.com/ims
27. Application Development for IMS 27
28. Application Development for IMS 28
29. Application Development for IMS 29 Connecting to EM4Z Click Start ? All Programs ? Accessories ? Remote Desktop Connection
Remote Desktop Protocol (RDP) is a multi-channel protocol that allows a user to connect to a networked computer. Clients exist for most versions of Windows (including handheld versions), Linux/Unix, Mac OS X and other modern operating systems. Remote Desktop Protocol (RDP) is a multi-channel protocol that allows a user to connect to a networked computer. Clients exist for most versions of Windows (including handheld versions), Linux/Unix, Mac OS X and other modern operating systems.
30. Application Development for IMS 30 Connecting to EM4Z (cont.) Enter the Sandbox computer address and port number (204.90.115.210:111xx)
Click Connect:
Enter the Sandbox computer password:
31. Application Development for IMS 31