|
1
|
- Jon Sayles, IBM Software Group, Rational EcoSystems Team
|
|
2
|
- © Copyright IBM Corporation 2007,2008, 2009. All rights reserved.
- The information contained in these materials is provided for
informational purposes only, and is provided AS IS without warranty of
any kind, express or implied.
IBM shall not be responsible for any damages arising out of the
use of, or otherwise related to, these materials. Nothing contained in these materials
is intended to, nor shall have the effect of, creating any warranties
or representations from IBM or its suppliers or licensors, or altering
the terms and conditions of the applicable license agreement governing the use of IBM software.
References in these materials to IBM products, programs, or services do
not imply that they will be available in all countries in which IBM
operates.
- This information is based on current IBM product plans and strategy,
which are subject to change by IBM without notice. Product release
dates and/or capabilities referenced in these materials may change at
any time at IBM’s sole discretion based on market opportunities or
other factors, and are not intended to be a commitment to future
product or feature availability in any way.
- IBM, the IBM logo, the on-demand business logo, Rational, the Rational
logo, and other IBM Rational products and services are trademarks or
registered trademarks of the International Business Machines
Corporation, in the United States, other countries or both. Other
company, product, or service names may be trademarks or service marks
of others.
|
|
3
|
- Thanks to the following individuals, for assisting with this course:
- Reginaldo Barosa/IBM
- David Bean/IBM-Rational
- Mike Wrzinski/Sentry Insurance
- Mohamed Kara/Toronto Dominion Bank
- Venkatuday Balabhadrapatruni/Santa Teresa/IBM
- Vijay U Sankar/IBM
- Virgilio Calimlim/IBM
|
|
4
|
- Audience
- This course is designed for application developers who have learned or
programmed in COBOL, and who need to do z/OS Traditional Development
and Maintenance as well as build leading-edge applications using COBOL
and Rational Developer for System z.
- Prerequisites
- This course assumes that the student has a basic understanding and
knowledge of software computing technologies, and general data
processing terms, concepts and vocabulary, as well as a working
knowledge of COBOL and z/OS.
- Knowledge of SQL (Structured Query Language) is assumed for database
access is assumed as well.
- Basic PC and mouse-driven development skills, terms and concepts are
also assumed.
|
|
5
|
- Course Name: Rational Developer
for System z
- Course Description: Learn how to
use Rational Developer for System z to do z/OS traditional development,
maintenance, support and for Enterprise Modernization of z/OS
applications
- Pre-requisites: Some experience developing COBOL applications using z/OS
is expected. A working knowledge
of SQL is also recommended.
- Course Length: ~5days – or if done in self-paced mode, at your own pace
- Topics (Agenda)
- Getting Started - installing and configuring RDz - and the course materials, and using Eclipse
- The RDz Workbench
- Code analysis tools
- Editing
- Compiling programs
- Debugging local COBOL programs
- The Data Perspective:
- Working with relational data sources
- Modifying test data
- Editing and testing SQL statements
- Working with remote system resources:
- Connecting to a mainframe
- Data management
- Accessing and editing files
- z/OS Application Development
- Creating MVS Subprojects
- Creating and customizing project properties
- Debugging z/OS Applications
- Debugging Batch Applications
- Setting Debug Tool for Online Applications
- Working with File Manager
- Creating test data
- Editing complex file-types
- Working with mainframe ABENDs using Fault Analyzer
- Creating Fault History views
- Analyzing and solving mainframe ABENDs
- Creating and modifying BMS Maps using the BMS Map Editor
|
|
6
|
|
|
7
|
- After completing this topic, you should be able to:
- Describe the use of the Remote System Perspective, the z/OS Projects
Perspective and Remote Systems View
- Define the properties necessary to connect to a z/OS machine from RDz
- Describe the different kinds of Source Control Management products that
integrate with RDz
- Connect to a remote z/OS mainframe
|
|
8
|
- & "Perspectives"
- Recall that a "Perspective" is a convenient grouping for a
collection of views organized around a given role or task
- So far in this class, you've used the:
- z/OS Projects Perspective – to
develop local COBOL applications
- Debug Perspective – to do
source-code (line-by-line) testing of your COBOL logic
- In this section we will introduce you to the Remote System Explorer
view.
- This view is a window into your z/OS environment.
- It allows you to see into and work with your mainframe assets
(programs, files, copybooks, JCL, REXX commands, etc.)
- This is all done through RDz's mainframe attachment sub-system, not TSO
- You may however for most of your work, wish to use the z/OS Projects
Perspective – which includes a Remote Systems View and contains
additional time and money-saving features
- We start with a quick peek at both
|
|
9
|
- The RDz Remote System View allows you to work with your z/OS assets and
resources (programs, data files, JCL, REXX commands, CLISTS, and Jobs)
- With the Remote System Explorer Perspective, you:
- Define connections to different systems
- Connect to different z/OS LPARs
- View lists of files and partitioned datasets
- Allocate, delete, copy and obtain statistics on datasets
- Work with PDS and PDSE files
- Create or delete members
- Compress
- Edit source - remotely
- Submit jobs
- Submit TSO/REXX and CLIST commands
- Create custom filters for:
- Searching through disparate dataset types
- Working with disparate dataset types
- ü Consider using the Remote
Systems Perspective if you are doing all (100%) of your RDz work
remotely - no offline analyze/edit/compile/debug.
|
|
10
|
- The z/OS Project Perspective by default contains a Remote Systems view, which
allows you to work with your z/OS assets and resources (programs, data
files, JCL, REXX commands, CLISTS, and Jobs) – both locally – and
remotely
- In other words, with the z/OS Project Perspective you can use the Remote
System View to essentially do everything you could do with the Remote
Systems Perspective:
- Define connections to different systems
- Connect to different z/OS LPARs
- Drag & Drop (copy) datasets between LPARs and from an LPAR to your
workstation
- View lists of files and partitioned datasets
- Allocate, delete, copy, obtain statistics on datasets
- Work with PDS and PDSE files
- Create or delete members
- Compress
- Submit jobs
- Submit TSO/REXX and CLISTs
- Create custom filters to:
- Search through disparate dataset types
- Work with disparate dataset types
|
|
11
|
|
|
12
|
- With the z/OS Perspective you also get the responsiveness, speed
and cost-savings of working
offline:
- Copy files back and forth from the mainframe to your workstation
- Customize property groups and properties for working with your projects
- Analyze applications and program code
- Edit source – offline, as well as remotely
- Debug applications – offline and remotely
- ü Recommendation: Use the
z/OS Project Perspective as your default for mainframe COBOL application
development, maintenance and support
|
|
13
|
|
|
14
|
|
|
15
|
- RDz works (integrates into) all of the common SCM products:
CA-Endevor, Serena's
Changeman, and
IBM's: SCLM, ClearCase, Rational Team Concert, etc.
- Because there are so many different products/configurations/customized
implementations, etc. instruction that included RDz and SCM is beyond
the scope of this course.
- You should consider obtaining IBM assistance in setting up, configuring,
and integrating RDz into your existing standard
- SCM process and toolset
|
|
16
|
|
|
17
|
|
|
18
|
|
|
19
|
|
|
20
|
|
|
21
|
- After you successfully login, the Remote Systems view will show your
connection …
- Which you can expand to show:
- All of the datasets "owned" by your TSO ID
- PDS/PDSE
- Individual
- Sequential files
- VSAM files
- Stored "Search Queries"
- All of the jobs you have submitted to the Job Entry Subsystem (JES)
- These resources are shown through what are called "filters"
- Filters are another topic you will learn about in the next section
- You can:
- Open remote files on your workstation
- Drag & Drop, copy, etc.
|
|
22
|
|
|
23
|
- Some libraries can grow very large.
- In excess of 20,000 members is not atypical.
- In order to speed RSEs open and search time, RDz 7.6.1 offers new
support for large PDSs.
- Features include:
- Browsing and Navigation options
- Locate
- Find members that start with…
- Hot-key support
|
|
24
|
- When the library you try to open contains more than a specified number
of entries RSE will
- List the first n entries (where n is defined in Workspace Preferences)
- Display a “…more” designation showing how many additional PDS members
are hidden from view
- Double-click the “…more” designation(S) – to scroll down or up within
the PDS by the defined scrolling # of members
|
|
25
|
- Additional options for PDS scrolling include:
- Right-click and select:
- Use the associated hot-keys
- Dynamically specify the scrolling amount è
- Right-click over the “…more” designation
- You can specify a different scrolling amount
- Note that this new scrolling amount only applies to the PDS you're browsing
|
|
26
|
- You start anywhere within a PDS by using Locate
- To do this:
- Select the PDS
- Right-click and select Locate…
- Enter the beginning Member Name text string
- Press OK
- ¤Notes
- This technique is similar to the ISPF 3.4 (DSLIST) library member list
option
- Your Locate strings are:
- Specific to a PDS
- Saved in your workspace, and available in the future from the Drop
Down selection box
|
|
27
|
- Preferences for the new v7.6.1 scrolling specifications can be found
under:
- Window
- Preferences >
- Remote Systems >
- z/OS >
- MVS Files
- Note that your new preference changes take place immediately
|
|
28
|
- Scrolling and browse preferences for an individual PDS can be specified
by:
- Selecting the PDS
- Right-click and select Properties
- Select Expansion
- Enter the number of PDS members to view
- Click OK
- Note that your PDS preference changes take place immediately
|
|
29
|
|
|
30
|
|
|
31
|
|
|
32
|
|
|
33
|
- Plan A - If you are learning RDz using your company's mainframe
computing center, and if they have successfully installed and configured
the RDz mainframe server components:
- Contact your shop's Systems Programmer staff
- Get the host-name and port#s for connecting to your z/OS machine
- Return in this section to the slides that describe how to create a new
connection (Creating a New Remote z/OS Connection)
- Follow the steps to create a connection and login to your mainframe
- Plan B - If you are intending to use the IBM Enterprise Modernization
Sandbox, now would be a good time to register (obtain a DeveloperWorks
sign-on ID) and connect
- You will not need to create a connection per se' but will use one of
the built-in connections from the virtual desktops in the Sandbox
- The Sandbox is located: http://www.ibm.com/developerworks/downloads/emsandbox/systemz_applications.html
- Your instructor will discuss more about its use during the class, and
you will want to obtain the slides named: "Getting Started with
the Sandbox", which take you through this process click-for-click
- Plan C - If you are intending to access the IBM zServerOS mainframe
directly – not through the Sandbox you will have to ensure that:
- You will need access to an IBM mainframe with the URL: zserveros.demos.ibm.com Unfortunately, you can't ping this
URL, but you'll find out if you can access it when you attempt to test
your connection.
- You'll also need access to the following Ports from your PC or
workstation: 4035, 6715
- If you are working from a home computer, most likely you'll be able to
do access zServerOS. But if you
are working from an office machine, you should check with your I/T
personnel to ensure that you have access to the above remote IP address
and the Port#s.
- Once you can connect, your instructor will give you a valid TSO
ID/Password combination for use during this class (it will be disabled
after). See the next slide for
additional Plan C help…
|
|
34
|
- Here are the New Connection screen values you can use to create a new
zServerOS connection.
- Host name (IP address):
- Ports for z/OS and MVS Files
- Port for JES
- Note that these are all the wizard defaults
|
|
35
|
- Now that you've completed this
topic, you should be able to:
- Describe the use of the Remotes System Perspective, the z/OS Projects
Perspective and Remote Systems View
- Define the properties necessary to connect to a z/OS machine from RDz
- Describe the different kinds of Source Control Management products that
integrate with RDz
- Connect to a remote z/OS mainframe
- Note that if you were not able to able to connect to your z/OS system,
you should read the Slide Notes – or access the RDz Help System, topics
on:
- Developing > Developing COBOL, PL/I, Assembler, and C++ applications
> Systems, projects, and properties > Connecting to and working
with remote systems
|
|
36
|
|
|
37
|
- After having completed this topic, you should be able to:
- Filter your z/OS (MVS) files and datasets
- Customize filters, adding new Filter strings
- Filter your JES Jobs
- Search through z/OS datasets for wildcard strings
- Map z/OS datasets to file types for the Workbench
|
|
38
|
- A filter is a set of set of wildcard qualifiers for z/OS datasets you
wish to see in the Remote Systems view
- Similar to wildcards you would enter in ISPF 3.4 or SuperC – Except
that filters persist across connected sessions, allowing you to create
subsets and supersets of files that can be managed and worked with from
a single folder
- You can create filters on a connection to any LPAR for:
- MVS Files, UNIX Files, JES Jobs
- For each z/OS connection,
Rational Developer for System z automatically creates a default filter
for your "connecting-ID's" datasets
- The default filter is called: My Data Sets (Your-TSO-id.*) – and it
lists all of the
datasets with names that begin with your TSO logon-ID's highest level qualifier
- There is also a "My Jobs" default Filter, that lists all
batch Jobs found in
JES that contain your connecting-ID as the high-level qualifier
in the job name
- As far as filters go, My Data Sets
not a bad start, it is only a start
- Filters can do a lot more for you, as we'll see
- See Slide Notes for additional Filter Best Practices and hints
|
|
39
|
- If you've worked on z/OS for any length of time you have probably seen
that the sheer quantity or number
of resources and files you use can pose an organizational challenge.
- Filters are used to:
- Organize z/OS resources
- Incorporate or isolate specific z/OS resources
- Allow you to share views of mainframe resources
- Simplify repeated dataset management work
- Copy at the filtered-folder level from one LPAR to another
- Subset (or create supersets of) files for use in source analysis
- Filter files
- Search within filtered files
- You can use Filters to better manage your:
- z/OS libraries and datasets
- JES (batch) Jobs
- USS files
|
|
40
|
|
|
41
|
|
|
42
|
|
|
43
|
|
|
44
|
|
|
45
|
|
|
46
|
|
|
47
|
- When you define a connection to a remote system, you map (associate) the
lowest level qualifier in each MVS™ data set to a file name extension
that is used for the related workstation-based file in your subprojects.
- For example, a default mapping associates the z/OS-based qualifier COBOL
to the .cbl file name extension.
- These system-wide mappings are listed in the z/OS File System Mapping
view.
- You can customize these mappings to match the naming conventions on your
remote system either through the z/OS File System Mapping view or
through the Mapping pane in the Properties window.
|
|
48
|
- Many of your z/OS datasets will likely require custom z/OS File Mapping,
in order for RDz to understand how to interact with the file (i.e. how
to download, editor to use etc.).
- 1. From the z/OS File System Map view
- From the drop-down, select the System (connection)
- Right-Click and select Add Data Set Mapping
- 2. Specify the mapping characteristics è
- Mapping Criterion:
- Each double asterisk (**) is a wildcard for a file name level
- Each single asterisk is a wildcard as part of a dataset name
- So **CUS* - means <anyHLQ>.<any2ndLevelQ>.CUS … any suffix
- Workstation file extension (as a file type label)
- The file transfer protocol:
- Text – for ASCII source files
- Binary – for test data datasets
|
|
49
|
- In this example, we have created a Mapping for all datasets
named:
- <anyHLQ>.
- <any2ndLevelQ>.
- FILES
- Ex. DDS0001.TEST.FILES
- And if the file is a PDS?
- The members inherit the mapping
- Don't forget to select your connection (System) before mapping
your dataset
- ¤ After you successfully add
a new z/OS File Mapping
for dataset, the default icon associated with file will change
|
|
50
|
|
|
51
|
- Recall from the previous unit titled, "RDz Workbench -
Introduction" we introduced the topic of project properties (see
slide titled, "Enabling Your Project for Copybooks"
- In a nutshell, properties or "resource properties", are
settings (think of them as analogous to compiler parms) that you use to
manage:
- The RDz product workflow (dialogs and options)
- How your application resources are generated, compiled and
linked
- Just the way you use compiler parms to control how the compiler
builds your executable files (what run-time
options to introduce into the machine code)
- A Property Group is an independent collection of resource properties
- Defined and maintained as a set
- Associated with one or more:
- Local (workstation) projects
- Remote Systems
- MVS Subprojects
- As an example of their use, you might define custom properties
and assign to different Property Groups for different technology
requirements
- COBOL (Batch) Subprojects
- COBOL CICS Subprojects
- COBOL DB2 (Batch) Subprojects
- COBOL DB2 CICS Subprojects
- AIX (or Windows-workstation) applications
- Web Services projects
- Projects that generate DB2 Stored Procedures
|
|
52
|
- If you are using RDz at a company, it is
likely that someone has already set up the proper RDz properties for
your work.
- However you still may be called upon to customize some of the
properties, so
let's find out how to import a property group and
see what the settings are all about
- From the Window menu, select:
- This opens the Property Group
Manager view
which lists your connections.
- Right-click over the connection you wish to create properties for, and
select Import…
- Click Browse, and select the property.xml file you wish to use
|
|
53
|
- Let's see how to customize properties to enable your z/OS project
program to do:
- Local Syntax check
- Remote Compile
- Show Dependency function (lists required copybooks)
- From the Property Group Manager view:
- Right-Click over the z/OS project connection
- Select the Property Group
- Select Edit…
- From Edit Property Group:
- Click: Next >
|
|
54
|
- This dialog shows all of the possible languages, 3270 screen
technologies and batch link and run-time options you might wish to
customize during this editing session as tabs.
|
|
55
|
- The COBOL Settings tab has several sub-tabs and options:
- Runtime Environments:
- Check for each that apply:
- Ex. CICS and DB2, or IMS and DB2
- Procedures and Steps
- Allows you to customize your compile procs (details on the next slide)
- Local Compiler Options
- Allows you to customize the
compiler settings for local COBOL (Windows executable) applications
- Local Preprocessor
- For custom COBOL in-house preprocessing (not for EXEC CICS or EXEC
SQL)
- JCL Substitution
- Allows you to over-ride (add, edit and remove custom variables) from
the default JCL generated through the wizards
- These are accessed through a SET statement
|
|
56
|
- From the Procedure and Step Table, Open ELAXFCOC, select COBOL and
customize:
|
|
57
|
- If the datasets exist for your compile outputs, you can just select,
left-click hold, drag and drop them from the Remote System view into the
appropriate Data Set name fields.
This will be more productive and help avoid JCL errors due to
typos
- When you are finished working, close the Edit Area, and save
changes
|
|
58
|
|
|
59
|
- You may need to create new Property Groups, delete them, export them for
sharing among team members, etc.
- You do this from the Property Group view
- From the Window menu, select:
- Show View >
- Other…
- From the Show View dialog, type: property group
- Select: Property Group Manager
- From there you can open your remote or local projects, and work with
their property groups
|
|
60
|
|
|
61
|
|
|
62
|
|
|
63
|
|
|
64
|
- From the menu, select Search > Remote
- Select Remote z/OS Search and enter a Search string – (with or without
wildcards)
- Click the Browse… button, and specify which connection, and within the
connection, which datasets to search within, and click OK, then click Search
|
|
65
|
- When the search completes, a new Remote z/OS Search view will appear in
Eclipse
- You can expand the entries to see individual source lines that match
your search criteria
- Double-click a line to download
and open the file in the Content Area
|
|
66
|
|
|
67
|
|
|
68
|
- Using Remote z/OS Search you can search for wildcard strings throughout
an LPAR (connection) across PDS datasets with differing high-level
qualifiers, and including offline and online content
|
|
69
|
- You can save a Remote z/OS® Search query and run it from the Remote
Systems view.
- Before you can save a search query, you must first run a remote z/OS
search and have the search results displayed in the Remote z/OS Search
view. This option is limited to a single z/OS system under the following
conditions:
- You search for files using a resource name pattern and the file content
search string is not specified.
- The search scope is for a single z/OS system. The scope can be an
entire z/OS system or multiple partitioned data sets on the same
system.
- The search scope does not include z/OS projects or MVS™ subprojects.
|
|
70
|
- In the Remote z/OS Search view, display the results of the search query
you want to save. If you have done more than one search, use the
drop-down search history list to select the search query you want to
save.
- Click the icon to save the
search query. This icon is enabled only if the search scope is limited
to a single z/OS system under the following conditions:
- You search for files using a resource name pattern and the file content
search string is not specified
- The search scope is for a single z/OS system. The scope can be an
entire z/OS system or multiple partitioned data sets on the same system
- The search scope does not include z/OS projects or MVS™ subprojects
- The Add Query to Remote Systems View window opens.
- Type a name for the query and click OK. The search query is added to
the
My Search Queries list under the MVS Files subsystem è
|
|
71
|
- After you have saved a search query, you can do the following actions:
- To run a saved query, select it in the Remote Systems view and click Run
Query from the pop-up menu.
- To edit and run a saved query, select it in the Remote Systems view and
click Edit and Run from the pop-up menu.
- This action opens the Remote z/OS Search window, which you can use to
change the search criteria and submit the search request.
|
|
72
|
- You may use Remote z/OS Search to filter large libraries.
- Steps:
- Leave the Search string empty
- Select the Search in: dataset(s)
- Specify the Library Name
- Save the Search result
- Click: Add query to My Search Queries
- You now have a persistent
"File Filter" at the PDS member name level
- Open files by double-clicking them in the Remote z/OS Search Results
view
|
|
73
|
|
|
74
|
|
|
75
|
- From the Search menu:
- Search Specifications:
- Search Results:
|
|
76
|
- After having completed this topic, you should now be able to:
- Filter your z/OS (MVS) files and datasets
- Customize filters, adding new Filter strings
- Filter your JES Jobs
- Search through z/OS datasets for wildcard strings
|
|
77
|
|
|
78
|
- After completing this topic, you should be able to:
- Allocate, delete and copy files – including:
- Sequential dataset
- PDS
- Generation Data Groups (GDGs)
- Perform typical PDS dataset management tasks:
- Compress a PDS
- Create PDS Members
- Copy PDS members – from one library to another
|
|
79
|
- Allocate:
- Sequential dataset
- PDS
- Allocate Like
- Define Generation Data Group
- Delete/Copy datasets
- For PDS datasets:
- Copy an entire PDS to your PC
- Compress a PDS
- Create PDS Members
|
|
80
|
- Windows-IDE/Simplified alternative to ISPF 3.2 delete option
- From within your LPAR Connection:
- Right-click over the file resource you wish to delete:
- Sequential dataset
- PDS
- GDG
- Select Delete…
- At the Confirm, click:
|
|
81
|
- Windows-IDE/Simplified alternative to ISPF 3.3
- From within your LPAR Connection:
- Right-click over MVS Files under the connection name
- Select Allocate Sequential Dataset…
- Name the dataset
- Note that you must have write or allocate authority against the
high-level qualifier you choose for the DSN
- Click Next >
|
|
82
|
- Three options:
- "Create like":
Copy characteristics from existing dataset
- Click: Browse
- Select the dataset to copy the file characteristics from
- Advanced
- Create by type:
- Source or a number of other common types
|
|
83
|
- Third option – completely custom characteristics:
|
|
84
|
- Windows-IDE/Simplified alternative to ISPF 3.3
- From within your LPAR Connection:
- Right-click over MVS Files under the connection name
- Select Allocate PDS…
- Name the PDS
- Note that you must have write or allocate authority against the
high-level qualifier you choose for the DSN
- Click Next >
|
|
85
|
- Same three options:
- "Create like" copy characteristics from existing
dataset
- Advanced
- Create by type:
- Source or a number of other common PDS
types
|
|
86
|
- Third option – completely custom characteristics:
|
|
87
|
- Using ISPF you probably gathered Dataset statistics in Option 3.2
- RDz makes this easier
- Click a dataset name in the Remote Systems view
- Look at the Properties view
|
|
88
|
- Creates new PDS members in a:
- From within your LPAR Connection:
- Right-click over the MVS dataset you wish to create the member in
- Select Create PDS Member…
- Name the member
- Note that you must have enough space and directory blocks available to
create new members in the PDS
- - Click Finish
|
|
89
|
- Creates new PDS members – copied from an existing library into a:
- From within your LPAR Connection and Remote Systems:
- Open the "copy-from" library
- Select any number of PDS members (press the Ctrl or Shift key to select
more than one at a time)
- Left-click, hold and drag the members to their destination library …or…
- Press the Right-mouse, and from the Context Menu select Copy
- Select the destination "copy-to" library
- Press the Right-mouse, and from the Context Menu select Paste
- Notes
- You must have enough space and directory blocks available to create new
members in the destination PDS
- You cannot copy and paste Load Modules or any files with RECFM: U
|
|
90
|
- Windows-IDE/Simplified alternative to IDCAMS
- From within your LPAR Connection:
- Right-click over MVS Files under the connection name
- Select Define Generation Data Group …
- Name the dataset
- Specify:
- Limit
- How many
generations
to retain
- Owner ID
- Defaults to
your
connection
if left blank
- How long to retain the
file
- Click OK
|
|
91
|
- Copies dataset characteristics to be used as a model for new file
- From within your LPAR Connection:
- Right-click over the MVS dataset you wish to use as the model for Allocate
Like
- Select Allocate Like…
- Name the dataset
- Note that you must have write or allocate authority against the
high-level qualifier you choose for the DSN
- Click Finish
|
|
92
|
- Windows-IDE/Simplified alternative to ISPF 3.2 rename option
- From within your LPAR Connection:
- Right-click over the file resource you wish to rename:
- Sequential dataset
- PDS
- GDG
- Select Rename…
- At the Rename Resource prompt:
- Enter your new name, and click:
|
|
93
|
- Windows-IDE/Simplified alternative to ISPF 3.1 compress option
- From within your LPAR Connection:
- Right-click over the PDS (note… not PDSE – as PDSE files do not need to
be compressed) resource you wish to compress:
- Select Compress PDS… or…
- Compress with Backup…
- & By compressing a PDS
TSO cleans up (deletes) the
"marked-for-deletion-but-not-deleted" PDS directory entries
for the PDS members
- http://publib.boulder.ibm.com/infocenter/zos/basics/index.jsp?topic=/com.ibm.zos.zconcepts/zconcepts_163.htm
|
|
94
|
|
|
95
|
|
|
96
|
|
|
97
|
- After having completed this topic, you should now be able to:
- Allocate, delete and copy files – including:
- Sequential dataset
- PDS
- Generation Data Groups (GDGs)
- Perform typical PDS dataset management tasks:
- Compress a PDS
- Create PDS Members
|
|
98
|
|
|
99
|
- After completing this topic, you should be able to:
- Submit batch JCL jobs from RDz
- Monitor jobs and view results
- Purge z/OS jobs from the JES queue
- Setup filters for specific categories of jobs
|
|
100
|
- Can submit batch jobs any one of three ways:
- Right-click over the .JCL PDS member in RSE, and select Submit
- With the JCL file opened in the RDz Content Area:
- Right-click, and from the Context Menu select Submit
- 3. Type Submit into the command prompt
|
|
101
|
- The Remote Job Monitor allows you to manage batch jobs from within RDz:
- View submitted jobs
- Select Refresh/F5 to see recently submitted jobs
- As folder/sub-folder contents
- In a table-like view
- Open job step results in the Content Area
- Cancel jobs
- Purge jobs
- Release jobs
- Into the queue when TYPRUN=HOLD
- Refresh the job status
- To find out if the job has ended
- Organize jobs by:
- Job Owner
- Job Prefix
- Job Output Class
- Job Status
- Job Class
|
|
102
|
- Expand the Job folder
- Double-click an individual job step
|
|
103
|
- Right-click over the JES icon and select: Show in Table
- Can:
- Scroll right/left to see different job summary stats
- Sort job results by all column options in the table
- This allows you to do things like, aggregate active jobs (IMS regions,
for instance) – by sorting on Job Phase
- Double-click an individual job to open the entire list dataset in the
content area
|
|
104
|
- Lock the jobs view
- Refresh the view – to see recently submitted jobs
- Go up one level – allows you to move between Filters (MVS Data Sets, My
Jobs, etc.)
- Select (subset) columns to display
- To select a subset of all jobs:
- Click the menu
(small downward-pointing triangle)
- Select Subset… è
- Specify the filtering text
- Click OK
|
|
105
|
- You can filter out columns, to simplify details
- To do this
- Click Select columns to display in the table
- Select a column
- Remove it
- Move it (up/down) within the display
- Click OK
|
|
106
|
- Select the individual job icon
- Right-click and select Show in Table
- Can sort job results by all column options in the table
- Double-click an individual job step to open in the content area
|
|
107
|
- The MVS™ Job Entry System (JES) job filters are used to define the
search that is done in JES for jobs.
- (like My Datasets) the My Jobs filter shows all jobs you have submitted
- You can create a custom JES filter, that allows you to customize your
view of jobs using filters
- JES job filter search parameters include the following:
- Job Owner
- Job Prefix
- Job Output Class
- Job Status
- Job Class
|
|
108
|
- Right-click over JES
- Select New JES Job Filter…
- Specify any custom filtering properties:
- Job Owner
- Job Name Prefix
- Job Output Class
- Job Status
- Job Class
- Click Next >
- Name the Job Filter
- Click Finish
|
|
109
|
|
|
110
|
|
|
111
|
- After completing this topic, you should be able to:
- Submit batch JCL jobs from RDz
- Monitor jobs and view results
- Purge z/OS jobs from the JES queue
- Setup filters for specific categories of jobs
|
|
112
|
|
|
113
|
- After completing this topic, you should be able to:
- Launch the TSO Command Prompt
- Issue TSO commands from RDz
- Close the TSO Command Prompt
- Launch TSO Host Emulation
- Launch the UNIX System Services (USS) Command Prompt
- Issue UNIX commands from RDz
- Close the USS Command Prompt
|
|
114
|
- Right-click TSO Commands, then select Launch TSO from the context menu.
- Enter a:
- TSO command
- CLIST
- REXX Exec
- Press 8Enter (note the up/down arrows retrieve
previous commands)
- Close the view when finished
|
|
115
|
- You may wish to know when your jobs have finished
- Or to display active IMS and CICS regions, etc.
- Steps:
- Keep a TSO Command view open
- Issue commands as if you were logged into native TSO
|
|
116
|
- Right-click over an RSE option and select Host Connection Emulator from
the context menu.
- Select your mainframe application
|
|
117
|
- From the Host Properties tab, you can change the following settings:
- Screen size
- LU name
- Code page
- Connection timeout
- Security
|
|
118
|
- You might want to setup different defaults:
- From: Window >
Preferences > Keys
- Select PF-Key
- Specify (using list-boxes):
- Click: Apply then OK - and test
out using Host Connection Emulator
|
|
119
|
- Login to TSO/ISPF on your mainframe (either your shop's, through the
Sandbox or to zServerOS)
- From the primary menu, access:
- Edit (=2)
- Browse (=1)
- View a sequential dataset
- If using zServerOS – view <HLQ>.HOSPIN.DATA
|
|
120
|
|
|
121
|
- After having completed this topic, you should now be able to:
- Launch the TSO Command Prompt
- Issue TSO commands from RDz
- Close the TSO Command Prompt
- Launch TSO Host Emulation
- Launch the UNIX System Services (USS) Command Prompt
- Issue UNIX commands from RDz
- Close the USS Command Prompt
|
|
122
|
- In order to pull together all of the edit, compile and debug techniques
described in this section, if time permits at work:
- Please go to the Enterprise Modernization Sandbox
- http://www.ibm.com/developerworks/downloads/emsandbox/systemz_applications.html
- Select and print out the following PDS
- http://download.boulder.ibm.com/ibmdl/pub/software/dw/rational/emz/Remote_IBM_zOS_application_development.pdf
- Follow the Sandbox Slides to:
- Register
- Download and install the Citrix client (first-time
only)
- Use the Sandbox
- And follow the detailed Instructions in the IBM Proof of
Technology labè
|
|
123
|
|
|
124
|
- This slide intentionally left blank
|
Notes
